I have been trying to root my ASUS ROG Phone 1 for almost a month now. I already opened the bootloader, however, I am struggling in finding the right TWRP image. I tried too many images some of which locked the phone (the phone starts to ask for a password after rebooting and I had to reset factory). Other images do nothing, i.e., when I run fastboot boot twrp_Z01QD..img, the CMD shows that the boot was successful, but the phone does not reboot into TWRP. Lately, I used an image that indeed reboots the phone into the TWRP recovery, however, TWRP asks for a decryption password. I use no password for my phone. I tried the "default_password" password. None of them worked. After that, I removed the data encryption totally from my phone by running the following commands: fastboot format userdata; fastboot format cache; fastboot reboot. However, this did not solve the problem.
I think that the problem might be in the version of TWRP I am using. Any help in locating the right image to be used will be highly appreciated. Also, if you have any clue how to go around the password, please let me know.
If there is anything not clear in my request, please let me know.
Thank you in advance.
You should try porting twrp recovery
Just search on google how to port twrp recovery.
Hey Dreto, thank you for your help. I googled how to port TWRP recovery, and I felt that it is a time-consuming process so I decided to keep it as my last resort. So before trying it, I tried to flash the image without the help of TWRP and it worked out. The phone is now rooted.
Again, thank you for your help.
AliMazloum said:
Hey Dreto, thank you for your help. I googled how to port TWRP recovery, and I felt that it is a time-consuming process so I decided to keep it as my last resort. So before trying it, I tried to flash the image without the help of TWRP and it worked out. The phone is now rooted.
Again, thank you for your help.
Click to expand...
Click to collapse
No problem
Related
Hello guys,
I have a problem, I hope you can help me with.
I used to have an EOS ROM. I decided to do factory reset and thats when my problems started. It didn't boot up anymore. After entering recovery I noticed it couldn't mount System partition. I tried reinstalling the ROM, but no success. Everytime I entered recovery, the System checkbox wasnt marked. So I decided to go back to stock, using http://androidforums.com/threads/return-your-xoom-to-stock.653230/. Now it is stuck at Logo screen and can't enter Recovery. (Goes to Reading ODM fuse, but not any further). I can still enter Fastboot and my laptop detects the tablet, when hooked up to it.
Please help me push the Recovery, cuz I'm getting "device not found" from ADB. I'm kinda lost here... Any help would be appreciated!
Update
I managed to install TWRP, but still can't mount System Partition. On wipe I get "Failed"when trying to clean the system part. I have tried Clockwork, it didn't help either.
Cmon guys! I don't want to JTAG it yet.
HexBox said:
Cmon guys! I don't want to JTAG it yet.
Click to expand...
Click to collapse
I am not very knowledgable about flashing, but one suggestion has come to my mind: if you can now get into TWRP (it wasn't clear whether you could based on your last post), try flashing a ROM without trying to clean the system partition. Just make sure the ROM matches the TWRP (i.e., big part ROM with big part TWRP).
Oh - another thought - folks in a number of threads have stated you need to explicitly follow both the recovery and ROM instructions for the XOOM. If you miss a step, people have had issues.
So I had my Honor 8 (FRD L04) unlocked, rooted and running stock just fine. Then I decided to flash the unofficial Lineage rom. After doing so I got a prompt to enter a password to decrypt, while booting into Lineage and even into TWRP, I never set the password so I wasn't sure what to do. I tried a few things then eventually reflashed TWRP and got rid of the password problem then tried to restore my back up but it didn't work. Now I'm stuck. I can access fastboot, TWRP and eRecovery. eRecovery always fails to get package info. And whenever I try to do anything in TWRP it says it failed to mount cust, vendor and product. I've tried a lot of different solutions I've seen on here the dload method always goes to 5% then fails. I've flashed stock boot, recovery and system.img but didn't change anything. And I can't seem to get it to boot to stock recovery to format/wipe that way.
If there's anything anyone knows that I can do it'd be appreciated.
Got my issue solved thanks to the thread above. Not sure how to mark this as solved or closed.
Rommco05 said:
Good to know if you want rename thread u can, but I know how to do it only in phone XDA app
Click to expand...
Click to collapse
Just found how to do it on the app. Name offically changed. Thanks again for the help.
Hello all, this is my first post so I apologize if anything isn't right.
I recently flashed my Mate 9 to stock Nougat B19x through a method I found on this site and then decided I wanted root. Bootloader was already unlocked so I flashed TWRP and then tried to flash a couple different root methods that all failed... So I factory reset through TWRP and tried again but they still failed so on the initial boot everything worked except the screen was blank except for the soft keys. I rebooted and the same again so I put it in fastboot and tried to re-install Nougat through the same method that worked before. It went through the whole process seemingly fine and finished with 'Update should start automatically' but then the phone boot into error mode. I've looked through everything I can find here and done everything I can think of myself but nothing has worked. I can boot into to fasboot but nothing else, not even after flashing any recoveries or stock images extracted from UPDATE.app.
Func no is 14 and error no is 1.
It's a MHA-L09 and I really need to fix it as I can't really afford anything else right now. Any help would be really appreciated and I'm happy to add more info if I've missed anything.
Thanks guys!!!
BUMP
Sorry if it's not very concise, just really need help!
What commands are you using to flash the stock files?
CandyFoxJ said:
What commands are you using to flash the stock files?
Click to expand...
Click to collapse
Standard fastboot flash recovery/system/boot
Not sure if I'm flashing all the right files or if huawei needs different commands.
Follow this guide.
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Thanks for your help. That's the one that I used in the first place but everytime I try again, TWRP either doesn't flash even though it says success or I can't get into recovery.
Everytime I try to access recovery using the hardware keys it boots to error mode so is there another way??
I've been looking into this some more and have found it could be a motherboard issue. Is this correct? And if so how much would that kind of repair cost and would it even be possible considering I've unlocked the bootloader?
Thanks again.
Apologies for being a member of this forum for so long and making this my first post. Regardless of this being my first post, these forums have been a life saver many times, and I would like to thank the very knowledgeable people who frequent these forums for all the time, effort, and patience that the put into new development and answering questions for those like me, who have a lot to learn yet.
Now to my issue...
I have had my OnePlus 7 Pro (Global) for a couple weeks now. It is on Android Pie, and I intend on keeping it on Pie for a while. I rooted it straight out of the box with Magisk 19.3 and TWRP 3.3.1-4 (Guacamole)(Installed by zip to both partitions) and it has been working great. No problems at all.
Two things have changed today, so I'm not sure which is the issue, if either are. One is that I updated to Magisk 20, and the other is that I tried to boot into recovery with and OTG cable attached with a 256g sansdisk flash drive attached to that. This is when it booted into bootloader instead of TWRP.
I disconnected the OTG cable and rebooted into system. I still had root from Magisk, so I attempted to reboot into recovery again, only to find that I booted into the bootloader again. Now I figured that I had lost TWRP, so I hooked my phone up to my windows 10 computer to flash custom recovery once again. I had read that it is possible to install TWRP to the ramdisk now through advanced settings, so I booted into temporary TWRP and selected the TWRP.img file to install to ramdisk. The command line said it was a success, so I backed out of that screen and rebooted into recovery. Once again, I was booted into the bootloader.
I disconnected my phone and booted into system. I still had root and everything was working as usual, so I reconnected my phone again and tried to install TWRP to both partitions as I did originally. The terminal went through the process rather quickly (usually it takes a minute or so to install TWRP), but claimed it was a success and that I lost root, like it should. I backed it up a screen, reboot to recovery.. no dice.
I've tried to take Magisk back to 19.4, but it didn't effect whether TWRP would stick.
I have a TWRP backup that I took of everything a couple days ago. I thought about trying to restore and see if that works, but I wanted to run it by you all to see if maybe somebody else has had this issue.
Could the attempt at rebooting into recovery while connected to OTG have done this?
Thank you all in advance for the assistance. I'm aware that this post is long winded, but I am also aware that you all like as much info as possible.
Thanks.
##############################################
Update
##############################################
My phone is working now, but not before I massacred it. I attempted to restore with that twrp backup I had while temporarily booted into twrp, through the twrp.img, through adb. I had it on the phone, so I figured I could use it.
I don't know if it was a corrupted backup, or if the process wasn't orthodox enough, but the restore crashed in the twrp terminal. I tried to boot into system and found that I had bricked the phone.
I ended up having to use the msm-downloadtool that I found here on xda. It was a lifesaver for sure.
Anyway, I figured that I'd update this thread. My phone is completely reset, bootloader unlocked, rooted, with custom recovery once again. I'm not sure what the cause was for the initial issue. I would still be interested to hear of any theories.
(I've searched around quite a bit in this forum and have not been able to answer the below question. Any assistance would be very appreciated.)
I am attempting to take a recovery/backup of a Pixel 3 using TWRP. I do not need to flash TWRP, just boot from it to perform the backup. Meaning, I don't care if TWRP is installed permanently.
The problem I am running into is that I need to unlock the bootloader before I can boot TWRP. And if I unlock the bootloader, the data on the device will be erased.
My question is: If I unlock the bootloader, will I be able to boot back into fastboot mode, and thus boot into TWRP, before the erasure occurs? And if to, how do I perform this? (I presume that if I hold the volume down button it will before rebooting it will go back into fastboot mode.)
I would rather not erase the phone. But if there is no other way I at least need the backup before the erasure occurs.
Thanks in advance for any assistance provided.
UPDATE: I found this thread, possibly it might work for a Pixel 3?
I am sorry I am of no help.... I only chimed in to say I could never get a working version of TWRP when I went to look for it on blueline. All I could get was Lineage Recovery so I have no idea if there is a way to backup before the wipe...