Related
Unbrick tool by One-Team - EypCnn
First: This tool seems to be from EypCnn, One-Team. All credits to them!
EDIT2: I no longer own this device, so i will leave this thread here for people to use. But don't expect any direct support from me .
What can this tool do?:
Restore phone to Stock(International) Firmware (S048) Marshmallow (Locked & Unlocked bootloader)
Fix Lost or bad Signal / IMEI any software Problem
For who does this work?
Pretty much any Lenovo P2 Variant (Chinese and International)
Phones which can access bootloader(you have to boot into it)
Works on Locked & Unlocked Bootloader
Installation aka. Flashing-Steps
Put your phone into bootloader (which is also fastboot) mode.
Download the folder and unzip it.
Connect your phone to your pc.
Go into the unzipped folder and open "flashall - stock reco.bat"
Wait, for the process to end, your phone will reboot on its own.! A stock lenovo bootlogo will show up !
You can disconnect your phone cable from pc and plug into a wall charger, just to be safe. Once the lockscreen is showing up, you're done.
If you want to flash Custom Roms:
look below:
WHEN MOVING TO CUSTOM ROMS NOW:
1. Boot to twrp. (Make sure it is pietwrp from telegram or the official 3.2.3 or later version)
2. Select WIPE menu option
3. Select data partition
4. Change file format to f2fs or anyother.
5. Go back to Start Menu of TWRP, choose Reboot Menu Option
6.Reboot to Recovery
7. Repeat Steps 2 and 3
8. This time select EXT4 when changing file format
9. Do Step 5 and 6
10. Wipe System,Cache and Dalvik-Cache partitions
( for older twrp versions: 10.1 If you're on official twrp 3.2.3 or lower, you have to flash pietwrp or latest twrp now !)
11. Flash your Custom Rom, Gapps (optional) and latest Magisk(optional)
12. Wipe Cache and Dalvik-Cache
13. Reboot. First Boot might take a few minutes but never longer than 7minutes.
If it takes longer, you're encounter a so called bootloop.
Comment hear if that happens, containing information on your twrp-version, rom, gapps, magisk and mods(if present) you're using.
When you corrupt your internal Storage or geht TWRP Error 1001, Error 7:
1. Repeat steps 2-6
2. Repeat steps 7-8
Download(Official Link)
2nd Link(reuploaded because some couldn't download it from androidfilehost): https://drive.google.com/open?id=1wUOZiTwW8mo0IheAGONyj9-QnjimnY2M
I will help if questions arise.
Credits to One-Team & EypCnn.
Thanks a lot. You literally saved my life!
Works like Magic
Thanks a lot for saving my ass . simplest way to downgrade to mm too. Thanks again
Wait.... downgrade to MM? Does this mean you can regain your signal or did @krishnakoonala get it wrong?
I have a spare P2 lying around that I never used because the IMEI got corrupted and I couldn't flash the bootloader files since I was unlocked.
I assume this wouldn't solve my issue?
eried1 said:
Wait.... downgrade to MM? Does this mean you can regain your signal or did @krishnakoonala get it wrong?
I have a spare P2 lying around that I never used because the IMEI got corrupted and I couldn't flash the bootloader files since I was unlocked.
I assume this wouldn't solve my issue?
Click to expand...
Click to collapse
My p2 was bricked and , stuck in boot loop. I followed the above instructions, 10 mins into it , it booted with mm version, the same version when i bought and booted for 1st time. It was like a new phone to me.
So i assume if one has upgraded to noughat and want to downgrade but is worried he might brick his device, one can take a back up and try this tool. It works flawless.
No harm in trying this one if ur p2 can boot up mate. Give it a shot. Good luck
Cheers
This tool has saved my device from multiple over a span of two years soft bricks. Can confirm it to do wonders.
eried1 said:
Wait.... downgrade to MM? Does this mean you can regain your signal or did @krishnakoonala get it wrong?
I have a spare P2 lying around that I never used because the IMEI got corrupted and I couldn't flash the bootloader files since I was unlocked.
I assume this wouldn't solve my issue?
Click to expand...
Click to collapse
THis will solve your problem , Cheers.
I tried but cannot download it - do you where to find it?
can i flash this without pc?? if yes please tell how
@sm00th4f3 bro, i wanna know, does this tool flashes full ROM including modem files etc, even on unlocked bootloader?
What is the state of bootloader after using this tool?
amansehdav said:
@sm00th4f3 bro, i wanna know, does this tool flashes full ROM including modem files etc, even on unlocked bootloader?
What is the state of bootloader after using this tool?
Click to expand...
Click to collapse
It flashed everything you have when you buy a new phone. And no, it doesn't lock your bootloader.
So you can either :
- keep using MM Stock Rom S048
- Update via ota in System like you normally would do.
- Update till latest Firmware, then flash twrp- and then Custom Rom of your Choice.
Bootloader is in the same state it was before you used this tool.
sm00th4f3 said:
It flashed everything you have when you buy a new phone. And no, it doesn't lock your bootloader.
So you can either :
- keep using MM Stock Rom S048
- Update via ota in System like you normally would do.
- Update till latest Firmware, then flash twrp- and then Custom Rom of your Choice.
Bootloader is in the same state it was before you used this tool.
Click to expand...
Click to collapse
So how does it fixes corrupted modems? it cannot be flashed on unlocked P2 right?
amansehdav said:
So how does it fixes corrupted modems? it cannot be flashed on unlocked P2 right?
Click to expand...
Click to collapse
I literally just answered it above somewhere.
(Literally in thread description)
You can flash it on unlocked bootloader or locked as well.
So many thanks for bringing up tis tool for us!
This thread should be stick as the "New user" thread is, they definitely belong together.
Download source
Thanks guys, if this works I can now revive my phone. But can someone please upload the tool to another place like google drive. From android filehost it will take an eternity to download!
HkQc said:
So many thanks for bringing up tis tool for us!
This thread should be stick as the "New user" thread is, they definitely belong together.
Click to expand...
Click to collapse
I didn't bring it up, i just linked it . All Credits belong to ONE TEAM and EypCnn.
ryd3r89 said:
Thanks guys, if this works I can now revive my phone. But can someone please upload the tool to another place like google drive. From android filehost it will take an eternity to download!
Click to expand...
Click to collapse
Link updated, Cheers
Lavesh05 said:
can i flash this without pc?? if yes please tell how
Click to expand...
Click to collapse
Nah you need a Computer for this.
no signal after using "flashall - stock reco.bat", it finished successfully, but after rom setup still no signal
GPSSlovakia said:
no signal after using "flashall - stock reco.bat", it finished successfully, but after rom setup still no signal
Click to expand...
Click to collapse
If you used some other tool for imei. You are pretty much done for.
Using this tool i can go to MM version and can upgrade to S251. However after installing twrp and flashing custom rom, it goes to bootloader
So the A/B structure of the Pixel (I came from Nexus 5X) took some getting used to, not having a recovery partition was a new wrinkle, and the jimmy jammy required to unlock the bootloader (I bought a Verizon Pixel apparently) was a neat trick. So I got the Pixel bootloader unlocked, booted with TWRP, installed Lineage, rebooted to bootloader, fastboot booted to TWRP, installed TWRP and OpenGapps.. Excellent! Setup the phone, booted to TWRP and installed Magisk. eveything works! great phone!
Then, a week later there is an update to Lineage. So I copy the ZIP file to my phone, flash it and OpenGapps and reboot. Boom. all screwed up. no problem, I'll restore from the backup I made in TWRP. nope. bootloop. then I read that you restore BOOT,SYSTEM IMAGE,VENDOR IMAGE, and DATA. NOT all the partitions as I had naively thought. Turns out I boned the backup and didn't backup the DATA partition so the Restore works but all my setup stuff is gone. My fault.
I went through the entire process again. Phone is working fine. All is well. Heres the question: What is the appropriate method to upgrade Lineage when a new one is released? So that I end up with new lineage, updated OpenGapps, TWRP working, and Magisk keeping me rooted? I can just keep trying to figure it out but I dont want to keep starting at zero with my phone.
Thanks in advance. I searched diligently on the forums but it looks like not that many Pixel users use Lineage.
Cheers
d.
130 views and no one knows how you upgrade LineageOS? is anyone using Lineage on their Pixel? Really?
I just discovered Lineage OS for my VZW Pixel. What build did you use? If I can figure out how to install, I'll try playing with updating, too.
Where did you end up downloading LineageOS from? I'd be curious to try it as well.
SkinnyT said:
Where did you end up downloading LineageOS from? I'd be curious to try it as well.
Click to expand...
Click to collapse
Probably here: https://download.lineageos.org/sailfish
post-mortem said:
Probably here: https://download.lineageos.org/sailfish
Click to expand...
Click to collapse
I probably should have looked there. I didn't even realize they supported the pixel. It's been a while since I've messed with things.
I've been using LineageOS and it's great. Super stable compared to most of the other ROMs I've tested. These are the steps I take when upgrading to a newer build.
- reboot to recovery (TWRP)
- install lineage-15.1-xxx-nightly-sailfish-signed.zip (no wipe or anything beforehand)
- install twrp-pixel-installer-sailfish-xxx.zip
- return to TWRP main menu and select reboot, then Recovery (whenever it prompts me to install TWRP app I just hit "Do Not Install")
- once back in TWRP, install MindTheGapps-8.1.0-arm64-xxx.zip
- reboot to system (again, I always decline the TWRP app installation)
- once you've booted to system, reboot to recovery one last time.
- install Magisk-v17.x.zip
- reboot to system and you should be good to go.
I always have a recent backup from TitaniumBackup stored on my computer so if anything goes wrong I can do a clean install and reload all my apps.
awesome. I'll try that. I'm using 15.1 10/23/2018 version and I have backed up so I'll do it. one question, do you reboot between installing lineage zip and twrp installer?
SkinnyT said:
Where did you end up downloading LineageOS from? I'd be curious to try it as well.
Click to expand...
Click to collapse
yeah I got it from lineage website. have you managed to update using Crawdads method?
dcarrco said:
awesome. I'll try that. I'm using 15.1 10/23/2018 version and I have backed up so I'll do it. one question, do you reboot between installing lineage zip and twrp installer?
Click to expand...
Click to collapse
No. Install TWRP immediately after installing the Lineage zip, before rebooting. Otherwise when you reboot to recovery it'll be the Lineage recovery and then you'll need a computer to send any other files you want to flash.
Also, they just started releasing builds every 24 hours. You might want to check the changelog every few days to see if there is anything new that's worthwhile. Some days there may actually not be any changes at all.
@CapriciousCrawdad
well I tried it today, just as you have it written in your post (other than what I assume was a typo where you say "return to lineage" in step 4 where I think you meant TWRP) and what it looks like is my working installation is on partition A and after installing as you specified it tried to boot on B and couldnt get past the Google screen. so I finally got it to reboot into TWRP and switched back to A and got my phone going again with my old October revision. the only difference is that I use OpenGApps and not MindTheApps. so tomorrow I'll try it with those.
CapriciousCrawdad said:
No. Install TWRP immediately after installing the Lineage zip, before rebooting. Otherwise when you reboot to recovery it'll be the Lineage recovery and then you'll need a computer to send any other files you want to flash.
Also, they just started releasing builds every 24 hours. You might want to check the changelog every few days to see if there is anything new that's worthwhile. Some days there may actually not be any changes at all.
Click to expand...
Click to collapse
dcarrco said:
@CapriciousCrawdad
well I tried it today, just as you have it written in your post (other than what I assume was a typo where you say "return to lineage" in step 4 where I think you meant TWRP) and what it looks like is my working installation is on partition A and after installing as you specified it tried to boot on B and couldnt get past the Google screen. so I finally got it to reboot into TWRP and switched back to A and got my phone going again with my old October revision. the only difference is that I use OpenGApps and not MindTheApps. so tomorrow I'll try it with those.
Click to expand...
Click to collapse
Whoops. Indeed, that was a typo in step 4. I edited the post.
Not sure about your problem though... I do remember specifically reading that opengapps can cause some issues but I can't find the source of that info and I don't think that it had anything to do with updating the system. I'm on mobile now but I might have time to check it out tomorrow.
If you haven't already, I suggest you check out the official LineageOS thread for the Pixel and Pixel XL. There might be some helpful info there.
CapriciousCrawdad said:
Whoops. Indeed, that was a typo in step 4. I edited the post.
Not sure about your problem though... I do remember specifically reading that opengapps can cause some issues but I can't find the source of that info and I don't think that it had anything to do with updating the system. I'm on mobile now but I might have time to check it out tomorrow.
If you haven't already, I suggest you check out the official LineageOS thread for the Pixel and Pixel XL. There might be some helpful info there.
Click to expand...
Click to collapse
yes thats where i ended up. tried to update and got bootlooped, my backup didnt work for some reason (do i backup EFS partition also?) so i started again with the instructions in that post. i used the Gapps package from @razorloves and it all worked. setup my phone again and now it upgrades fine using the Lineage updater although i have to reinstall TWRP and reroot (using SuperSU from Lineage) when that happens. razorloves hasnt updated his google FI compatible Gapps package yet so i will see how/if i can update those when the times come. on a side note, im getting really good at setting up my pixel. got to look at the upside.
thanks for your suggestions.
TWRP has been successfully ported to the Galaxy J7 Refine (SM-J737p) (Oreo 8.0)
DISCLAIMER: THIS IS NOT AN ODIN FLASHABLE TWRP. THIS IS NOT AN OFFICIAL TWRP. THIS IS A TWRP PORT THAT HAS BEEN MADE POSSIBLE BY BOTH @Dark98 & MYSELF. IT WAS BUILT USING FILES FROM R16NW.J737PVPU1ARG3. IT MAY OR MAY NOT WORK ON DEVICES WITH A DIFFERENT BOOTLOADER VERSION
You must have root access. I am currently working on making an Odin-flashable .tar for TWRP devs. Hopefully it will be available soon. Until then, root your device with Magisk. SuperSU is dead..
There is a downside & an upside to porting TWRP. The downside is that after you flash TWRP, you will lose root. The upside is that TWRP will remain so all you need to do to regain root is flash the Magisk-v18.1.zip. It's a very delicate process & you will need to pay attention or else you will bootloop & start over.
In order to flash, you need an app that will do so without booting into recovery. Flashify is the ideal choice for this procedure. View attachment flashify.apk Flash TWRP in Flashify but do not reboot from the app. Power off your device & boot into TWRP manually.
PAY ATTENTION TO THESE NEXT FEW STEPS!!!
- Boot into TWRP for the first time
- Swipe to allow modifications
- Wipe > Format Data > type yes when prompted (this will not delete any files you have in your Internal Storage)
- Once wipe is completed, go to TWRP home screen & Reboot > Power Off
- Once device powers off, reboot back into TWRP (yes you will boot into recovery twice)
If you fail to immediately boot back into TWRP, you will brick & have to restart.First boot is to clear out the /Data partition to make room for your new recovery. Second boot is to secure it.
Now that you have secured TWRP, go ahead & make a backup of your Boot + System + Data partitions. Keep in mind that you've lost root access so the backup will be "stock" firmware with TWRP.
------------------------------------------------------------------------------------------------------------------------------
Now to get root back
(In TWRP)
You will now flash Magisk-v18.1. With the new security measures Samsung put in late 2017, you will need to flash 2 .zip files after to ensure that root sticks. YOU NEED TO FLASH THESE FILES IN ORDER. DO NOT WIPE CACHE AFTER EACH FLASH. DO NOT REBOOT AFTER EACH FLASH. FLASH EACH PACKAGE ONE AT A TIME. WAIT UNTIL THE 3RD FLASH IS COMPLETE & THEN REBOOT DEVICE. IT WILL TAKE SEVERAL MINUTES SO BE PATIENT.
In this order, flash:
- View attachment Magisk-v18.1(18100).zip
- View attachment no-verity-opt-encrypt-6.0.zip
- View attachment RMM-State_Bypass_Mesa_v2.zip
DO NOT WIPE THE CACHE
Now reboot device normally. If you do not flash the verity & RMM zip files in order, you will fυck your sh¡t up & have to start over.
PROOF OF TWRP:
View attachment 4730415
View attachment 4730414
View attachment 4730413
View attachment 4730412
When you get to your home screen, you will receive a notification to update Magisk. Update by either selecting the notification or manually through Magisk Manager. Allow Magisk to install the update, not TWRP.
Extract the .tar from the .zip > extract the twrp.img from the .tar View attachment J737P.zip
This is for the Galaxy J7 Refine (SM-J737P) (RUNNING OREO 8.0) (J737PVPU1ARG3)
Special thanks to @topjohnwu for Magisk
Special thanks to @Dark98 for working with me on this project. Probably could've done it without you bro but it would've taken longer
work for j737t and j737t1?
juniorgerman said:
work for j737t and j737t1?
Click to expand...
Click to collapse
The root method should, provided you substitute in your own patched_boot.img from your stock firmware.
TWRP however, will not. Those variants are GSM Carriers (T-Mobile network). This is for Boost, a CDMA Carrier (exynos7885)
Thank you
Thank you for this as I will give it a go.
Kireej said:
Thank you for this as I will give it a go.
Click to expand...
Click to collapse
This thread should've been deleted already as it's not the main one. I've moved it to here. Please direct any further comments or inquires here as well.
Is there a rootable method for the J737P 9.0 Android update?
LeThAiL JoKeR said:
Is there a rootable method for the J737P 9.0 Android update?
Click to expand...
Click to collapse
Hello, I have a Galaxy J7 Refine from Boost. Recently I decided to root it. There are only a few places that have ANY info on rooting SM-J737P.
Not realizing that this was an OLD thread, I basically just went along with this and a little info from somewhere else and some knowledge of rooting from back when I basically HAD to have my phone rooted.
Good news is, first try it worked for me. But I had this issue that I figured would be easy to remedy.
There is a notification when I boot the phone saying Unauthorized actions have been detected. Restart your device to undo any unauthorized changes.
Without doing any research on the notification I immediatly lept into action and caused the phone not only to boot loop, but also not be able to boot into recovery, where I had made my backup.
I tried flashing several roms/files and trying to figure out the issue, I realized that this was an old thread and the Binary Update number on my phone was 7, and here i was trying to flash 1's, 2's, 4's, 6's. Like no wonder they didnt do anything to help.
Immediately trying to search for U7, I was hitting road blocks, because it seems as though everyone's list stopped at U6.
Fortunatly for you, I would not take no for an answer and spents HOURS trying to figure out what file I needed and then locating it. Not being able to boot into OS or Recovery, figuring out what version my phone was on was a bit tricky. Cross referanced this info with that info, yada yada yada.
I found the most up to date file in case you brick your phone, but also if your still interested, I can help supply the info and files I used to accomplish this.
But as I type this, I cant stop thinking about that notification. I need to find out if its going to cause me problems or if I can just shut it up and everything will be fine.
I'll get back to you on those results. For now, im done typing. I haven't typed this much in a LONG time.
I cant stop thinking about that notification. I need to find out if its going to cause me problems or if I can just shut it up and everything will be fine.
(Disable the app called securitylogagent do no th delete will cause bootloop) I am looking to see is there new firmware u7. i have binary 6 rooted and would like to find u7 to try root?
Disable image
......fix that notification
I found out using lucky patcher to get rid of notification. Which that was the first app I was going to install anyways. So it worked out great.
As far as the u7 binary, I found it. I'll upload it to drive and share a link here shortly.
Currently uploading file to folder, but when its done you should be able to access it here.
https://drive.google.com/drive/folders/1MD3owVbiAjgSyz0-f4Q_eSATV1zcXZeZ?usp=sharing
hello i'm on the u7 binary i'm having trouble rooting can someone share a link for the patched boot for the u7 or a flashable twrp if there is one? any help is appreciated and thank u
never mind i got it thanks anyway
How do you root a Samsung Galaxy SM-J737P Version 9
PlsHelpMeRootingImBegging said:
How do you root a Samsung Galaxy SM-J737P Version 9
Click to expand...
Click to collapse
I'm on 7 but I believe all u would do is flash twrp and patch ur boot img from ur binary with magisk and follow the rest the steps listed above
weric43 said:
I'm on 7 but I believe all u would do is flash twrp and patch ur boot img from ur binary with magisk and follow the rest the steps listed above
Click to expand...
Click to collapse
But i can find my TWRP and no one click roots work i tried kingo root kingroot and SO many others none work and framaroot wont work either nothing works and my twrp idk if its compatible
PlsHelpMeRootingImBegging said:
But i can find my TWRP and no one click roots work i tried kingo root kingroot and SO many others none work and framaroot wont work either nothing works and my twrp idk if its compatible
Click to expand...
Click to collapse
I have the twrp flash file give me a few mins I'll get it to u
weric43 said:
I have the twrp flash file give me a few mins I'll get it to u
Click to expand...
Click to collapse
download files unzip files inside u will find flashable twrp
okey
PlsHelpMeRootingImBegging said:
okey
Click to expand...
Click to collapse
Did u get it?
weric43 said:
Did u get it?
Click to expand...
Click to collapse
so i installed magiska and tapped install to the tar file idk it never flashed so i tried again and it said their was no recovery.img found
Hi everyone!
Issue is pretty simple to explain - after upgrading via OTA from the latest open beta Pie (29) to open beta Android 10 (30), I can't boot into recovery.
System works normally, the only thing I'm having trouble with are the generic issues discussed on the OP community forum (autorotate and other sensors, Gboard gap...). It is recommended repeatedly that one should reboot to recovery and wipe the cache partition.
The problem is that I can only get into fastboot mode - tried the advanced boot menu, adb/fastboot and selecting recovery mode while in the fastboot mode but it always goes into fastboot.
TWRP doesn't support android 10 yet as far as I know and I've found no other reference of this issue anywhere else. Only thing that comes to mind is to wait for the next open beta and hope it will be resolved after another OTA.
Thanks for your help!
seems the open beta install was more bad for you than mine. Upgraded from op29 to op30 like you, but i had everything stock. No unlocked bootloader, no big customizations, etc. I just tried entering recovery mode via fastboot and it worked like normal for me, had to enter my pin to decrypt my data, and the rest like normal. I'd suggest to downgrade back to pie and reflash the open beta software to see if the issue is gone or not, but that's your call to do so.
HighOnLinux said:
seems the open beta install was more bad for you than mine. Upgraded from op29 to op30 like you, but i had everything stock. No unlocked bootloader, no big customizations, etc. I just tried entering recovery mode via fastboot and it worked like normal for me, had to enter my pin to decrypt my data, and the rest like normal. I'd suggest to downgrade back to pie and reflash the open beta software to see if the issue is gone or not, but that's your call to do so.
Click to expand...
Click to collapse
I think you stumbled across the answer everyone has been searching for. How did you upgrade? Did you download the whole zip and flash through updated?
This kinda makes sense. Do you remember how big the update file was? It could have been an incremental rather than a full if you weren't unlocked and thus (maybe) didn't change fastboot.
verbatim7 said:
Hi everyone!
Issue is pretty simple to explain - after upgrading via OTA from the latest open beta Pie (29) to open beta Android 10 (30), I can't boot into recovery.
System works normally, the only thing I'm having trouble with are the generic issues discussed on the OP community forum (autorotate and other sensors, Gboard gap...). It is recommended repeatedly that one should reboot to recovery and wipe the cache partition.
The problem is that I can only get into fastboot mode - tried the advanced boot menu, adb/fastboot and selecting recovery mode while in the fastboot mode but it always goes into fastboot.
TWRP doesn't support android 10 yet as far as I know and I've found no other reference of this issue anywhere else. Only thing that comes to mind is to wait for the next open beta and hope it will be resolved after another OTA.
Thanks for your help!
Click to expand...
Click to collapse
Had read somewhere that flashing stock boot.img will help restore stock recovery.. Have you tried doing that
brashmadcap said:
I think you stumbled across the answer everyone has been searching for. How did you upgrade? Did you download the whole zip and flash through updated?
This kinda makes sense. Do you remember how big the update file was? It could have been an incremental rather than a full if you weren't unlocked and thus (maybe) didn't change fastboot.
Click to expand...
Click to collapse
i grabbed the update file from this news article from xda itself: https://www.xda-developers.com/oneplus-android-10-oxygenos-beta-oneplus-6-6t/
the update zip was the full update and not incremental. i updated my device using the local device upgrader found under the system update settings to do the job for me.
Edit: this part down was meant for OP, sorry for confusion
so far when i updated last night, the auto rotate was tripping, until you mentioned that wiping the cache should do the trick (and it did do the trick thanks for that).
But back to your problem, you should try flashing the file under the link i put into this reply and if it doesn't work, just back up your data, downgrade back to pie, and flash the full update file that is present within that article and you should be back to normal
HighOnLinux said:
i grabbed the update file from this news article from xda itself: https://www.xda-developers.com/oneplus-android-10-oxygenos-beta-oneplus-6-6t/
the update zip was the full update and not incremental. i updated my device using the local device upgrader found under the system update settings to do the job for me. so far when i updated last night, the auto rotate was tripping, until you mentioned that wiping the cache should do the trick (and it did do the trick thanks for that).
But back to your problem, you should try flashing the file under the link i put into this reply and if it doesn't work, just back up your data, downgrade back to pie, and flash the full update file that is present within that article and you should be back to normal
Click to expand...
Click to collapse
Thanks for the idea. Unfortunately, it seems that having root and having recovery isn't possible for me at this point.
I've installed the OTA, got the recovery back and managed to wipe cache and everything worked - except I didn't have root. Then I've installed the magisk boot image to get back root, but then the same issues started happening and I was unable to access recovery.
Now I have to decide what's more important :crying:
Use an older version of magisk and you won't lose twrp
verbatim7 said:
Thanks for the idea. Unfortunately, it seems that having root and having recovery isn't possible for me at this point.
I've installed the OTA, got the recovery back and managed to wipe cache and everything worked - except I didn't have root. Then I've installed the magisk boot image to get back root, but then the same issues started happening and I was unable to access recovery.
Now I have to decide what's more important :crying:
Click to expand...
Click to collapse
how did u get back the recovery?
LazerH said:
how did u get back the recovery?
Click to expand...
Click to collapse
As stated above - just downloaded the OTA Android 10 update file for the right device, installed it and didn't install magisk to inactive slot and I had it back. If I tried to install magisk to keep root I didn't have the recovery mode. My guest guess is that magisk still isn't fully compatible with the new Android 10 boot changes.
verbatim7 said:
Thanks for the idea. Unfortunately, it seems that having root and having recovery isn't possible for me at this point.
I've installed the OTA, got the recovery back and managed to wipe cache and everything worked - except I didn't have root. Then I've installed the magisk boot image to get back root, but then the same issues started happening and I was unable to access recovery.
Now I have to decide what's more important :crying:
Click to expand...
Click to collapse
To me having a stable phone is much more important than a heavily modified device that's unstable at any given time. I'd say use the msm tool, flash back to a fresh build of pie, download the full open beta 30 zip, after its done flashing, reboot twice to iron out any present issues, then unlock the bootloader, and then you should be good to go. If you want root, just fastboot boot into twrp and flash the latest magisk zip and you're good to go. At the end you should have root, an unlocked bootloader, all while on the open beta android 10 build, with access to the stock recovery
Can u guys help me please, i just flashed by mistake with " fastboot flash boot" a TWRP enchilada file and now i'm stuck in fastboot and i cant boot ...i dont know how to factory reset or flash firmware from fastboot (
terrorblade23 said:
Can u guys help me please, i just flashed by mistake with " fastboot flash boot" a TWRP enchilada file and now i'm stuck in fastboot and i cant boot ...i dont know how to factory reset or flash firmware from fastboot (
Click to expand...
Click to collapse
Had the same problem. Flash this one: https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
OOS 10 Open Beta 1 Stock Boot
Schnullifax said:
Had the same problem. Flash this one: https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
OOS 10 Open Beta 1 Stock Boot
Click to expand...
Click to collapse
thanks..this is what i was looking for ...the problem is that now i'm in a boot loop , the dots keep spinning 4ever...and i did factory reset it from recovery
up1: i managed to install on slot a (i guess) Twrp.. but the whole memory is empty and i cant place anything (firmware) with pc on phone
formated data from twrp (to some format ntfc4 or smth like that ) and installed back android q and is working .
So I am not an entire noob when it comes to these things, I've flashed ROMs on phones for 8 years now, but this Moto G7 Power screwed me up good.
I tried installing CrDroid from this post. I didn't even notice the A/B part at first, I went through all the usual steps, I booted TWRP, then flashed it, rebooted into the installed TWRP, flashed CrDroid, GApps and Magisk and rebooted, hoping to start Android up. At that part it all screwed up. The phone didn't boot AT ALL, and after a while I found that blankflash zip file and managed to get into the bootloader again. The only thing I can do now is boot into TWRP, not flash, and when I boot, the touchscreen does not work.
So, where do I go from here? I now only have an unlocked bootloader to play with. What are the exact steps to flash the firmware? Why do I need to flash firmware to slot A anyway? Isn't or wasn't there firmware out of the box on the device? The guides for this phone are vague and people write really short and rambling sentences in the steps and mention certain files out of the blue without explanation or download link.
1 - Which firmware file do I need? I have an XT1955-4 bought in a Dutch shop called Belsimpel with no sim. I assume it's an international variant. Here is a download list of all the firmware variants, but how do I know which one to pick? Will it wipe things like IMEI data? The box says the type is M3C94, and it seems to be this international variant.
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
4 - The 'guide' in the CrDroid thread suddenly mentions copypartitions.zip. What is that file, and why do I need to flash it? It says I have to flash it in Slot A. Does TWRP give options to switch slots? I wish I could check but since my touch screen doesn't work in TWRP..
5 - During the actual ROM install part, the guide says Flash ROM.zip + TWRP_installer/boot.img ramdisk method Why do I need to install TWRP again? And what is the ramdisk method? How do you do that?
Can someone please explain in detail step by step what I need to do?
kerelberel said:
So I am not an entire noob when it comes to these things, I've flashed ROMs on phones for 8 years now, but this Moto G7 Power screwed me up good.
I tried installing CrDroid from this post. I didn't even notice the A/B part at first, I went through all the usual steps, I booted TWRP, then flashed it, rebooted into the installed TWRP, flashed CrDroid, GApps and Magisk and rebooted, hoping to start Android up. At that part it all screwed up. The phone didn't boot AT ALL, and after a while I found that blankflash zip file and managed to get into the bootloader again. The only thing I can do now is boot into TWRP, not flash, and when I boot, the touchscreen does not work.
So, where do I go from here? I now only have an unlocked bootloader to play with. What are the exact steps to flash the firmware? Why do I need to flash firmware to slot A anyway? Isn't or wasn't there firmware out of the box on the device? The guides for this phone are vague and people write really short and rambling sentences in the steps and mention certain files out of the blue without explanation or download link.
1 - Which firmware file do I need? I have an XT1955-4 bought in a Dutch shop called Belsimpel with no sim. I assume it's an international variant. Here is a download list of all the firmware variants, but how do I know which one to pick? Will it wipe things like IMEI data? The box says the type is M3C94, and it seems to be this international variant.
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
4 - The 'guide' in the CrDroid thread suddenly mentions copypartitions.zip. What is that file, where do I download it, and why do I need to flash it? It says I have to flash it in Slot A. Does TWRP give options to switch slots?
5 - During the actual ROM install part, the guide says Flash ROM.zip + TWRP_installer/boot.img ramdisk method Why do I need to install TWRP again? And what is the ramdisk method? How do you do that?
Can someone please explain in detail step by step what I need to do?
Click to expand...
Click to collapse
1. go to settings - system - about phone check build number, this is the firmware you'll need
2. there's a thread here regarding that matter check again
3. I'm not aware of this issue
4. you'll only need to flash that file once coming from stock rom - https://androidfilehost.com/?fid=4349826312261636295
5. because it be overwritten by lineage recovery.
ramdisk method is just another way of installing twrp back when we still dont have the installer zip
vinoxflame said:
1. go to settings - system - about phone check build number, this is the firmware you'll need
2. there's a thread here regarding that matter check again
3. I'm not aware of this issue
4. you'll only need to flash that file once coming from stock rom - https://androidfilehost.com/?fid=4349826312261636295
5. because it be overwritten by lineage recovery.
ramdisk method is just another way of installing twrp back when we still dont have the installer zip
Click to expand...
Click to collapse
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
then try another version of twrp or the unofficial orangefox recovery for our device
vinoxflame said:
then try another version of twrp or the unofficial orangefox recovery for our device
Click to expand...
Click to collapse
I tried an older version of TWRP which didn't work either. I am not aware of Orangefox, but I don't see any mention, official or unofficial for the G7 Power. There's no mention in the G7 Power forum either.
kerelberel said:
I tried an older version of TWRP which didn't work either. I am not aware of Orangefox, but I don't see any mention, official or unofficial for the G7 Power. There's no mention in the G7 Power forum either.
Click to expand...
Click to collapse
it's on the telegram group
vinoxflame said:
it's on the telegram group
Click to expand...
Click to collapse
No it is not. There's no mention of G7 Power in the search results. Only E5.
kerelberel said:
No it is not. There's no mention of G7 Power in the search results. Only E5.
Click to expand...
Click to collapse
deleted
vinoxflame said:
https://t.me/mG7Power
tell me if it is not!!!!
Click to expand...
Click to collapse
From the desktop search in this one I couldn't find it: https://t.me/OrangeFoxRecovery I didn't know there was a separate chat for each device. But thanks.
FWIW when this happened to me I did the blankflash thing to get it back to bootloader. Then I used the LMSA tool from Motorola to do a rescue/restore.
I also used LMSA to force the update to the most recent security update. In general, it seems a very useful utility.
https://www.motorola.com/us/lenovo-motorola-smart-assistant
I had this issue after blankflashing this temperamental device out of a brick. While in twrp you can do "adb shell" then "twrp install /path/to/zip" I think this has to do with new twrp versions on older firmwares
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
When i had this issue go reboot fastboot
then fastboot boot recovery.img or twrp as your boot img do what you need to do just dont flash it to boot only boot from it so you preserve your real boot should fix the touch screen part only time i had prob like this is when i flashed twrp to recovery without disabling dm verity etc. But I cant even get a stock OTA since I flashed twrp as recovery nor can I find a RETUS stock recovery.img so far if i had that I can update and keep magisk etc, then reflash twrp when im done.
---------- Post added at 06:06 PM ---------- Previous post was at 05:58 PM ----------
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
When i had this issue go reboot fastboot
then fastboot boot recovery.img or twrp as your boot img do what you need to do just dont flash it to boot only boot from it so you preserve your real boot should fix the touch screen part only time i had prob like this is when i flashed twrp to recovery without disabling dm verity etc. But I cant even get a stock OTA since I flashed twrp as recovery nor can I find a RETUS stock recovery.img so far if i had that I can update and keep magisk etc, then reflash twrp when im done. The latest stock RETUS build i can find is here https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip but if i do that i will lose all my apps AGAIN etc I am trying to just get the stock recovery img from previous version so I can install the ota in magisk you just tap uninstall tap restore images to get stock boot as well then ota should work once its done go back into magisk and install to inactive slot but you will or could need TWRP A/B retention script so that you keep it even after ota...which you will first go in magisk tap uninstall restore images, but must have stock recovery not twrp installed at this time either from what i can tell, once ota is successful install the TWRP A/B Retention script but do this before you install magisk to inactive slot from magisk manager after that it should work. But I cannot locate a stock recovery.img thus far.... and I dont wanna redownload my apps right now, so I may just wait til I see a rom i really think ill like and say screw it.
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
I also installed crDroid and after that twrp-3.3.1-2-ocean.img was not responding to touch, but twrp-3.3.1-0-ocean.img works. (btw I was doing a fastboot -w in between.)
Edit:
Ah nevermind, I have it constantly when installed, with both versions.
s33b said:
I also installed crDroid and after that twrp-3.3.1-2-ocean.img was not responding to touch, but twrp-3.3.1-0-ocean.img works. (btw I was doing a fastboot -w in between.)
Edit:
Ah nevermind, I have it constantly when installed, with both versions.
Click to expand...
Click to collapse
I've flashed another stock rom (https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-flash-to-t3927138) and it worked with twrp-3.3.1-0-ocean.img not with the newest.
kerelberel said:
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
Click to expand...
Click to collapse
You use fastboot commands in the bootloader.
The firmware contains a flash file with all fastboot commands you'll need.
kerelberel said:
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
Click to expand...
Click to collapse
TWRP has adb enabled by default. So instead of TWRP you can use
Code:
abd shell twrp --help
So you can use the basic functions like backup, install, and so on.
I had the same issue...
I'm not sure everyone is experiencing the same issue here, but I've been dealing with that exact problem the entire time I've had this phone. While this work around won't work every time, it will eventually work (for me within 3 tries). It doesn't matter if your "fastboot boot twrp.img" or running an installed version, all are the same. Even the latest 3.4.0.0.
As soon as you start recovery, start tapping the area of the screen where the "Advanced button" is in recovery. I mean tap as fast as you can, use two fingers if you need to. If it doesn't work right away, "adb reboot bootloader" and try again. I can get this to work within 3 tries. Its sucks and its stupid, but it works.
TheGuysGuysGuy said:
I'm not sure everyone is experiencing the same issue here, but I've been dealing with that exact problem the entire time I've had this phone. While this work around won't work every time, it will eventually work (for me within 3 tries). It doesn't matter if your "fastboot boot twrp.img" or running an installed version, all are the same. Even the latest 3.4.0.0.
As soon as you start recovery, start tapping the area of the screen where the "Advanced button" is in recovery. I mean tap as fast as you can, use two fingers if you need to. If it doesn't work right away, "adb reboot bootloader" and try again. I can get this to work within 3 tries. Its sucks and its stupid, but it works.
Click to expand...
Click to collapse
I getba link to one that works for u. https://t.me/CustoKernal_JavaShin_Mods/565. Fastboot boot (name of recovery)
roadkill42 said:
I getba link to one that works for u. https://t.me/CustoKernal_JavaShin_Mods/565. Fastboot boot (name of recovery)
Click to expand...
Click to collapse
Again not everyone is experiencing this same issue. A custom kernel isn't going to help when its incompatible with my ROM. My stupid workaround works for "No Touch Screen Response" in TWRP as well as OrangeFox. Its happened to me in both. Happily cruising along on Paranoid Android Quartz.
TheGuysGuysGuy said:
Again not everyone is experiencing this same issue. A custom kernel isn't going to help when its incompatible with my ROM. My stupid workaround works for "No Touch Screen Response" in TWRP as well as OrangeFox. Its happened to me in both. Happily cruising along on Paranoid Android Quartz.
Click to expand...
Click to collapse
The problem with the touch is the right driver needs to b installed that kernel I shared makes it work and stick I'm on it now go to tellagram group Moto g7 power support group both twrp and ofox there that works not the one from twrp it's self and the twrp there has some other features that one from official one has that don't work
This boot image gave me a touchscreen and allowed me to flash a regular twrp: hxxps://f.emvn.me/android-roms-and-stuff/twrp.3.4-kakarot.boot.img
Thanks to whoever made it.