[Q] Unable to boot on TWRP - Moto E Q&A, Help & Troubleshooting

My Moto E Hangs when I try to boot a TWRP image
Attempted procedure:
(After booting into stock fastboot)
Code:
fastboot boot twrp-2.7.1.0-condor.img
A reboot to that TWRP was expected instead. But it freezes on bootloader.
TWRP used on the attempt:
dl.twrp.me/condor/twrp-2.7.1.0-condor.img.html
I don't want to flash a different recovery or anything else, just a clean root.
Moto E XT1025 DTV Dual BR
4.4.4
21.12.40.condor_retbr_tv_ds.retvr.en.BR.retbr

LucasBS1 said:
My Moto E Hangs when I try to boot a TWRP image
Attempted procedure:
(After booting into stock fastboot)
Code:
fastboot boot twrp-2.7.1.0-condor.img
A reboot to that TWRP was expected instead. But it freezes on bootloader.
TWRP used on the attempt:
dl.twrp.me/condor/twrp-2.7.1.0-condor.img.html
I don't want to flash a different recovery or anything else, just a clean root.
Moto E XT1025 DTV Dual BR
4.4.4
21.12.40.condor_retbr_tv_ds.retvr.en.BR.retbr
Click to expand...
Click to collapse
Sometimes booting recovery doesn't work...You will have to flash it. Perhaps you can flash the stock recovery after successful root? though i am not sure that will work
Also try booting into CWM

Tried the same method with CWM.img
Same result: fastboot frozen (volume buttons not responsive, and PC no longer sends commands)
To flash the stock recovery I would need to back it up first
But guess what's needed to backup ?
Yes, a temporary flashed bootloader with ZIP support
Would you know someone, who knows someone, who knows an master from MTI or Hogwarts or Narnia that knows an alternative ?
I would flash a mod right away if I could backup the original first...
(Unless, as I don't know exactly how this works, the ROM might come with the bootloader (?) Because the stock ROM I can download easily anywhere (already did))

LucasBS1 said:
Tried the same method with CWM.img
Same result: fastboot frozen (volume buttons not responsive, and PC no longer sends commands)
To flash the stock recovery I would need to back it up first
But guess what's needed to backup ?
Yes, a temporary flashed bootloader with ZIP support
Would you know someone, who knows someone, who knows an master from MTI or Hogwarts or Narnia that knows an alternative ?
I would flash a mod right away if I could backup the original first...
(Unless, as I don't know exactly how this works, the ROM might come with the bootloader (?) Because the stock ROM I can download easily anywhere (already did))
Click to expand...
Click to collapse
Hi,
Did you managed it to work? I have exactly the same problem. If I even flash twrp or cwm I still can't boot into it, there is only "no command" message.
I can't get any help anywhere, it makes me crazy. Do you have any custom recovery that worked for you after flashing?? I'm even starting to think that my device is broken somehow.

giaur said:
Hi,
Did you managed it to work? I have exactly the same problem. If I even flash twrp or cwm I still can't boot into it, there is only "no command" message.
I can't get any help anywhere, it makes me crazy. Do you have any custom recovery that worked for you after flashing?? I'm even starting to think that my device is broken somehow.
Click to expand...
Click to collapse
I did NOT flash the recovery yet
I'm trying to run the recovery without flashing it, to avoid problems like yours
You said you flashed both CWM and TWRP ?
And Neither one of them worked ?
I'm screwed too, then...
:crying:
See if you can find the stock recovery somewhere
And NOT here
This forum is not good for it
It's too much phone specific... too narrow... and we get no attention; specially with our "not-mainstream" phone
Generic instruction could work
If you take any action, or find any forum you find helpful, let me know

@giaur @LucasBS1
I too have tried booting the recovery ,but it doesn't work. You will have to flash it
if you are seeing 'no command' message it means that you still have stock recovery and the custom recovery wasn't flashed successfully.
try this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2971601
or this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879

LucasBS1 said:
I did NOT flash the recovery yet
I'm trying to run the recovery without flashing it, to avoid problems like yours
You said you flashed both CWM and TWRP ?
And Neither one of them worked ?
I'm screwed too, then...
:crying:
See if you can find the stock recovery somewhere
And NOT here
This forum is not good for it
It's too much phone specific... too narrow... and we get no attention; specially with our "not-mainstream" phone
Generic instruction could work
If you take any action, or find any forum you find helpful, let me know
Click to expand...
Click to collapse
None of them worked. I'm going to resign, because there is nothing I can do. Seems you have exactly the same problem as me. What I tried:
- fastboot boot recovery.img. Phone hangs on bootlogo
- flash recovery, then use go to recovery option in fastboot menu. In this case, 2 possibilities: with usb cable connected, it boots normally to system, not to recovery. With usb cable disconnected, screen goes black and phone looks like powered off. You will need to power it on and it will boot to system.
- On running system with usb debugging enabled. If you type "adb reboot recovery", you will end with dead robot and "no command" error. You can however press VolUP +Power on this screen and you will see Android 3e recovery.
If you have the same problem as me, you are completly lost and it's impossible to intall recovery on your device. I'm close to resign and say "**** this ****ty phone" because (as you already mentioned), there is no any attention on my questions, twrp support was dropped long time ago etc.
Flashing recovery should not wipe your data, so once you try to flash twrp or cwm, please let me know about your results. I'm sure I will never able to solve this problem, but I will feel better knowing that I'm not alone whit it
---------- Post added at 06:05 PM ---------- Previous post was at 06:00 PM ----------
mepsilon2 said:
@giaur @LucasBS1
I too have tried booting the recovery ,but it doesn't work. You will have to flash it
if you are seeing 'no command' message it means that you still have stock recovery and the custom recovery wasn't flashed successfully.
try this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2971601
or this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879
Click to expand...
Click to collapse
Still the same, I'm on stock recovery. In console, no errors:
Code:
[email protected]:~/android/DO_MOTOROLI/twrp/2.8.5$ fastboot flash recovery twrp2.8.5.0-recovery.img
target reported max download size of 299892736 bytes
sending 'recovery' (9046 KB)...
OKAY [ 0.312s]
writing 'recovery'...
OKAY [ 0.860s]
finished. total time: 1.172s
But "adb reboot recovery" - "No command". Damn it...
---------- Post added at 06:26 PM ---------- Previous post was at 06:05 PM ----------
Ok, I'm finished. It's not possible. F U C K Motorola and good night. My advice: don't waste your time if you have the same problem. You will get nothing, except wasted time. It's good that it's not my phone (I own OnePlus One). But I was asked to install CM12.1 on my friend's phone. It's impossible, so I will need to tell him I was failed with that.

mepsilon2 said:
@giaur @LucasBS1
I too have tried booting the recovery ,but it doesn't work. You will have to flash it
if you are seeing 'no command' message it means that you still have stock recovery and the custom recovery wasn't flashed successfully.
try this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2971601
or this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879
Click to expand...
Click to collapse
I see people complaining about bugs or not-working features on the first link
Are you sure it's safe ?
It's not the official TWRP (apparently)
When I google for this bootloader the official page shows version 2.7.1.0
Whereas on your second link they are on the 2.8.2.0
Which one should I trust ?
And to anyone who might answer:
Trough PC is the only/safest way to flash these recoveries ?
Seeing giaur on that situation puts me stepping back...

LucasBS1 said:
I see people complaining about bugs or not-working features on the first link
Are you sure it's safe ?
It's not the official TWRP (apparently)
When I google for this bootloader the official page shows version 2.7.1.0
Whereas on your second link they are on the 2.8.2.0
Which one should I trust ?
And to anyone who might answer:
Trough PC is the only/safest way to flash these recoveries ?
Click to expand...
Click to collapse
I tested both: latest official 2.7 and linked 2.8. So they are safe. Official support for Moto E was dropped long time ago.

giaur said:
I tested both: latest official 2.7 and linked 2.8. So they are safe. Official support for Moto E was dropped long time ago.
Click to expand...
Click to collapse
Cool
Regarding to safety
Should I flash CWM or TWRP ? Why ?
Regarding the method
Flash through usb->Fastboot or through Apk (like CWM)
Or a third method ?
And why
Between TWRP 2.7 and 2.8, which one is safer ?
And of course...why ?
And a last question, before I leave you guys alone:
Did you manage to root the phone, despite the poblems occurring to you, giaur ?

Once you succesfuly flash twrp, you need to flash supersu then and you are rooted. If you don't have your current system rooted, the only way to flash custom recovery is to flash via fastboot. TWRP is recommended, because it's way better
I can't say anything more, because my moto e is not flashable, so I can't replace stock recovery.

Yo !
Flashed TWRP
But wiped things I shouldnt
How to put the ROM back via USB ?
EDIT:
NEVERMIND
Found how to use SD to do that

giaur said:
Once you succesfuly flash twrp, you need to flash supersu then and you are rooted. If you don't have your current system rooted, the only way to flash custom recovery is to flash via fastboot. TWRP is recommended, because it's way better
I can't say anything more, because my moto e is not flashable, so I can't replace stock recovery.
Click to expand...
Click to collapse
I was also struggling a lot many days into getting twrp and cw loaded on to a Moto E. The problem was that I was pressing the Power button to activate the recovery menu and that will not activate the recovery option. You got to press the UP button instead of power after executing
Code:
fastboot.exe flash recovery twrp-2.8.1.0-condor.img
. This is quite counter intuitive but described well in most posts, but as experts we assume up button is to go up the menu.
Sunish Issac

Related

Need Help - Stuck

Hey guys, I'm facing an issue right now.
I had a rooted OPX with TWRP and Lolipop. I downloaded the new OOS 3.1.3 from OnePlus site, flashed it. There was an error, fixed it by updating updater-script. Flashed the zip, then just after that flashed SuperSU zip and TWRP image over recovery. I don't know why I did that but that's the order. Then I forgot to wipe Dalvik/Cache and rebooted into recovery...It stuck in OnePlus Logo screen with powered by android written at bottom. Then I tried to boot into System by pressing the power button, it got stuck in the boot animation (The new one in Marshmallow update). It just keeps rotating infinitely (I think). I have waited for about 30 minutes on that screen, no luck.
What should I do? Is there a way that fastboot mode would be recognized by my PC and I can boot into recovery via image? Or any way for factory reset? Data is all backed up, so no issue about that. Just need it to get running asap.
Please reply asap.
Thanks for reading.
Did you try booting into recovery or fastboot manually ?
For recovery - hold all 3 keys, when OnePlus logo comes, then leave Vol Up key and hold the other 2.
Do the same but leave the Vol Down key for fast boot.
If either of this works then you can recover easily.
Joshwin Aranha said:
Did you try booting into recovery or fastboot manually ?
For recovery - hold all 3 keys, when OnePlus logo comes, then leave Vol Up key and hold the other 2.
Do the same but leave the Vol Down key for fast boot.
If either of this works then you can recover easily.
Click to expand...
Click to collapse
Just as I mentioned, booting into recovery doesn't work. Stuck at the OnePlus Logo Screen if I do that manually.
Though I can boot into fastboot. But after doing that, when I connect the phone to the PC, fastboot devices command returns an empty line.
We get so caught up in custom recovery and such that we forget about what people would normally do who don't mod. Simplest safest way to upgrade bootloader or downgrade is by using original stock recovery. Now your gonna probably need to go through the hard brick guide.
Exodusche said:
We get so caught up in custom recovery and such that we forget about what people would normally do who don't mod. Simplest safest way to upgrade bootloader or downgrade is by using original stock recovery. Now your gonna probably need to go through the hard brick guide.
Click to expand...
Click to collapse
Yeah, I did for the first time.
I think I now know what went wrong. For future viewers -
Do NOT ever Flash Recovery Image through your recovery. Always use fastboot.
Something weird happened. I managed to flash recovery, update to OOS 3.1.3. Then for rooting, I downloaded TWRP and SuperSU zip from the links here http://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830.
But as soon as I flashed SuperSU, I got stuck in Bootanimation again. Why is this happening??
choubeyaakash77 said:
Yeah, I did for the first time.
I think I now know what went wrong. For future viewers -
Do NOT ever Flash Recovery Image through your recovery. Always use fastboot.
Something weird happened. I managed to flash recovery, update to OOS 3.1.3. Then for rooting, I downloaded TWRP and SuperSU zip from the links here http://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830.
But as soon as I flashed SuperSU, I got stuck in Bootanimation again. Why is this happening??
Click to expand...
Click to collapse
You have to use the modded SuperSU. You can find it in the many guides posted for oos3.

Flashing a ROM

Hello,
I started on a quest last week to try and make my long forgotten Xperia tablet z LTE SGP321 more user friendly.
I stopped using it after being frustrated by the bloatware and its lack of customisation.
So I thought flashing a custom rom might help and wanted a bit of a technological challenge. Boy do I feel like I've got one.
I used kingroot, which worked fine. I tried to install SuperSu but it wont update the binaries.
I've managed to unlock the bootloader (forgot to do the backup TA woops!).
I downloaded TWRP app, flashed pollux_windy to recovery. Now there doesn't seem to be a combination of keys that I can find to boot the sony xperia tablet Z into recovery?? Power and volume up or down or jamming both keys...nothing seems to work. I've found one forum post suggesting it isnt possible and that I need to flash a kernel which is where I'm getting stuck.
SO this is where I am now and was wondering if I should use CWM instead or if there is another way to open recovery?
My main aim is to completely clear the tablet hard drive and start again with a custom rom.
Thanks!
>>>>>>
NEW info
So i've managed to use the ADB to reboot into the boatloader. All that happens is a black screen. I want to try and flash CWM or TWRM but it doesnt seem to work.
Im beginning to think there's something strange about the sony xperia tablet z in that it doesnt have a bootloader in its stock firmware. i've seen something about using a Kernel approach but the guides are unclear.
Any help on flashing a CWM or TWRM into recovery would be much appreciated!!
harpix42 said:
Hello,
I started on a quest last week to try and make my long forgotten Xperia tablet z LTE SGP321 more user friendly.
I stopped using it after being frustrated by the bloatware and its lack of customisation.
So I thought flashing a custom rom might help and wanted a bit of a technological challenge. Boy do I feel like I've got one.
I used kingroot, which worked fine. I tried to install SuperSu but it wont update the binaries.
I've managed to unlock the bootloader (forgot to do the backup TA woops!).
I downloaded TWRP app, flashed pollux_windy to recovery. Now there doesn't seem to be a combination of keys that I can find to boot the sony xperia tablet Z into recovery?? Power and volume up or down or jamming both keys...nothing seems to work. I've found one forum post suggesting it isnt possible and that I need to flash a kernel which is where I'm getting stuck.
SO this is where I am now and was wondering if I should use CWM instead or if there is another way to open recovery?
My main aim is to completely clear the tablet hard drive and start again with a custom rom.
Thanks!
>>>>>>
NEW info
So i've managed to use the ADB to reboot into the boatloader. All that happens is a black screen. I want to try and flash CWM or TWRM but it doesnt seem to work.
Im beginning to think there's something strange about the sony xperia tablet z in that it doesnt have a bootloader in its stock firmware. i've seen something about using a Kernel approach but the guides are unclear.
Any help on flashing a CWM or TWRM into recovery would be much appreciated!!
Click to expand...
Click to collapse
Flash boot.img of any latest custom ROM with TWRP integrated.
Rootk1t said:
Flash boot.img of any latest custom ROM with TWRP integrated.
Click to expand...
Click to collapse
Thanks for your help. I thought I'd start simple and just try and flash TWRP to recovery.
i downloaded the latest TWRP pollux windy img and then used the command fastboot flash recovery twrp.img
It says FAILED (remote: command not allowed)
adb fastboot devices displays my tablet
(by the way in configuration in service info it says bootloader unlocked: Yes)
>>>>>>UPDATE
so i managed to flash a cyanogenmod img using "fastboot flash boot boot.img"
The device then soft bricked and went into a boot loop. Is this because I used the wrong version of cyanogenmod?? Any other I can try that work?
I panicked a bit, mamanged to get the tablet into fastboot somehow andthen flashed a TWRM img to the boot using the same command above which now loads TWRM.
fastboot reboot now caused the device to go into TWRP but its in recovery mood
How can i undo that step i did when I flashed the boot img of the cyanogen mod. I want to put the old boot.img back!
Rootk1t said:
Flash boot.img of any latest custom ROM with TWRP integrated.
Click to expand...
Click to collapse
also can I ask another quick question of you, what do you do to boot into recovery on your xperia tablet Z device?
Thanks!
Sorry about all the updates.
I decided to see what you had installed on your signature and tried resurrection remix. Version 5.8 caused Error 7??
So i went for version 6.9 which i installed successfully.
Only way i know how to get into recovery is to use adb terminal command "adb reboot recovery"
Also before I installed resurrection remix would you recommend a complete wipe of everything or does it not really matter?
Thanks and hopefully that's me all sorted!
Use VOL+ or VOL- on boot to enter recovery.
harpix42 said:
what do you do to boot into recovery on your xperia tablet Z device?
Click to expand...
Click to collapse
2 way for me:
- usually you can set an "advanced reboot menu" under developer option or the ROM customization panel (depends on which ROM do you use)
- turn off your tablet, now push the power button until your screen just turn on, leave the power button and start pressing vol+ and vol- alternately until you boot into recovery

Stuck in TWRP on nougat

I currently have this problem that when I flash a version of TWRP(have tried both 3.0.2 and 3.1.0) I cannot reboot my current OS(have tried both stock 376 and 378). Simply pressing the power button will result in recovery mode. Stranger still, when i flashed a ROM as a zip out of twrp, it actually booted up, but then I could no longer return to recovery mode, despite fiddling around mith multiple button combinations.
Seems as though i am missing something obvious, as i have not found a thread regarding a similar issue. Anybody have a clue as to what it might be?
macjagger said:
I currently have this problem that when I flash a version of TWRP(have tried both 3.0.2 and 3.1.0) I cannot reboot my current OS(have tried both stock 376 and 378). Simply pressing the power button will result in recovery mode. Stranger still, when i flashed a ROM as a zip out of twrp, it actually booted up, but then I could no longer return to recovery mode, despite fiddling around mith multiple button combinations.
Seems as though i am missing something obvious, as i have not found a thread regarding a similar issue. Anybody have a clue as to what it might be?
Click to expand...
Click to collapse
it seems like u dint have an proper boot.img
try flashing ftf
I've been flashing the stock firmware(s) as ftf using flashtool (newest version) and xperifirm, that's why I think it's so odd. Before flashing TWRP, the stock ROM boots up and everything works as it should. After flashing TWRP, it only boots up into recovery.
macjagger said:
I've been flashing the stock firmware(s) as ftf using flashtool (newest version) and xperifirm, that's why I think it's so odd. Before flashing TWRP, the stock ROM boots up and everything works as it should. After flashing TWRP, it only boots up into recovery.
Click to expand...
Click to collapse
hmmm do u flash an kernel that has dm variety fix
---------- Post added at 08:32 AM ---------- Previous post was at 08:32 AM ----------
also what firmware ur are on
altvolt74 said:
hmmm do u flash an kernel that has dm variety fix
---------- Post added at 08:32 AM ---------- Previous post was at 08:32 AM ----------
also what firmware ur are on
Click to expand...
Click to collapse
Yes, I've been flashing kernels with that fix.
I managed to get stock 378 DE running using only flashtool with jutphaas' boot.img of this thread: https://forum.xda-developers.com/z5-compact/general/32-3-0-378-pushed-xperifirm-t3559906/page4
I've also had 376 DE and 376 AU firmware working with this ROM: https://forum.xda-developers.com/z5-compact/development/rom-stock-z5c32-3-0-376r2dau-t3570248
In this case I was able to flash the ROM .zip out of TWRP and boot into the ROM. Afterwards I could no longer enter TWRP though.
In both cases, after (re)flashing TWRP, I'd get stuck in recovery.
macjagger said:
Yes, I've been flashing kernels with that fix.
I managed to get stock 378 DE running using only flashtool with jutphaas' boot.img of this thread: https://forum.xda-developers.com/z5-compact/general/32-3-0-378-pushed-xperifirm-t3559906/page4
I've also had 376 DE and 376 AU firmware working with this ROM: https://forum.xda-developers.com/z5-compact/development/rom-stock-z5c32-3-0-376r2dau-t3570248
In this case I was able to flash the ROM .zip out of TWRP and boot into the ROM. Afterwards I could no longer enter TWRP though.
In both cases, after (re)flashing TWRP, I'd get stuck in recovery.
Click to expand...
Click to collapse
try flash e5823 lates nougat e5823_32.3.A.0.376_R2R_AU instead of (e5803) firmware
also to enter flash the rom using kernel partition
off phone . ...hold vol down and power release power when see sony keep holding volume down all the way till recovery
format system
flash zip
i will update intrustions since theres people having issues while flashing an rom using e5823 on e5803 or probably ur flashing it wrong using the recovery that is integrated to the boot.img
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
also sorry for late reply been cooking xperia xz rom to our z5 compact also finish is uploading it now
I'll give it a try in a couple of days. Need my phone as a daily driver currently. Appreciate your help
macjagger said:
In both cases, after (re)flashing TWRP, I'd get stuck in recovery.
Click to expand...
Click to collapse
To me it seems like you are just flashing twrp to the wrong partition.
How do you flash it?
You have to flash it with command:
Fastboot flash recovery "twrp.img"
macjagger said:
I currently have this problem that when I flash a version of TWRP(have tried both 3.0.2 and 3.1.0) I cannot reboot my current OS(have tried both stock 376 and 378). Simply pressing the power button will result in recovery mode. Stranger still, when i flashed a ROM as a zip out of twrp, it actually booted up, but then I could no longer return to recovery mode, despite fiddling around mith multiple button combinations.
Seems as though i am missing something obvious, as i have not found a thread regarding a similar issue. Anybody have a clue as to what it might be?
Click to expand...
Click to collapse
oh hai
just wanted to link you in on this:
https://forum.xda-developers.com/z5...m-fix-twrp-t3560135/post71433741#post71433741
Hey fellas, I'm back. Excuse my absence, currently busy with exams.
It seems as though @Gewiz was correct. I was trying to flash twrp over "Flashtool>fastboot mode>select kernel to flash", which probably targets the wrong partition. Instead I now used "Flashtool>fastboot mode>reboot into fastboot mode via fastboot" and flashed it using the standard cmd window line ("fastboot flash recovery twrp.img") and it seems to have worked.
Thanks to everyone on this thread!
macjagger said:
Hey fellas, I'm back. Excuse my absence, currently busy with exams.
It seems as though @Gewiz was correct. I was trying to flash twrp over "Flashtool>fastboot mode>select kernel to flash", which probably targets the wrong partition. Instead I now used "Flashtool>fastboot mode>reboot into fastboot mode via fastboot" and flashed it using the standard cmd window line ("fastboot flash recovery twrp.img") and it seems to have worked.
Thanks to everyone on this thread!
Click to expand...
Click to collapse
Have you tried to do a restore yet?
Just wanted to ask so I can isolate twrp with rootkernel

Upgrade to Nougat. Unlock Bootloader -> TWRP -> Root -> Safetynet Pass

Updated for more serious reference. Hope this info helps you!
Procedure:
Once you have updated to Nougat, you would have to unlock your bootloader
The APK that unlock the bootloader works (Even though is marked as M version). (Remember that this will wipe your device!) For ULBL -> Version UnlockTool_2017_0803(android M) (FROM ASUS) https://www.asus.com/us/Phone/ZenFone-3-Zoom-ZE553KL/HelpDesk_Download/
Zenfone will reboot and you will able to see a new splash screen that informs you that your device is unlocked giving you boot options Don't press anything. (You will see this everytime you reboot). The next screen will show an erase process. Phone will reboot.
Once booted enable developer options and adb via usb.
You can find TWRP builds right here: https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w (Special thanks to: @shakalaca) Use the latest one.
Go to fastboot mode and install TWRP. (fastboot flash recovery (nameoffile).img)
Let fastboot do it's magic, once you finish press volume buttons till you find reboot recovery press power button to select. It will boot again to the first splash. Do not press anything, let it work. It will boot TWRP in a whistle.
Once in TWRP make a backup. You know it's necessary, and will save your ass in case of a softbrick.
Flash latest magisk (Current Ver: 13.3) Magisk thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Reboot, check drawer for magisk manager, magisk and root should be enabled.
Voila. Safetynet test passed :good:
what version was twrp are you using and what steps did you take to get magisk to work.
smariob said:
So today finally I got my Asus Zenfone 3 Zoom. I couldn't contain myself to start playing with it.
My very first surprise was that the phone requested for an update. I've done it. I ended with a stock 7.1.1 AZ3Z.
This is my experience:
The APK that let you unlock bootloader works. (Remember that this will wipe your device)
After auto reboot I cheched safetynet. At this point test failed (Little bit obvious)
I was able to go to fastboot mode and install TWRP (The same you can find right here at the forum)
Let fastboot do it's magic, press volume buttons till you find reboot recovery. It will boot TWRP in a whistle.
Once in TWRP I made a backup. You know if necessary.
The next step was a crossfinger procedure. Just flashed latest magisk Beta (13)
Reboted checked for magisk manager on drawer.
It was there and root also. Enabled magiskhide, and voila. Safetynet test passed :good:
Hope this Info help you.
Click to expand...
Click to collapse
Do you know if this works with Android Pay?
magicmanfk said:
Do you know if this works with Android Pay?
Click to expand...
Click to collapse
It should work with it, im able to login intoy bank account with no problem with this method, I will give it a try for you though.
mr573162 said:
what version was twrp are you using and what steps did you take to get magisk to work.
Click to expand...
Click to collapse
magicmanfk said:
Do you know if this works with Android Pay?
Click to expand...
Click to collapse
It's twrp 3.1.0
It should work as it passes CTS profile and Basic Integrity I can't test it myself because I live in Mexico and Android Pay is not avialable here yet.
Will edit OP
Just a question as I'm having difficulty booting into TWRP.
My device is unlocked and when flashing TWRP using the command "fastboot flash recovery twrp.img" and trying to boot into it nothing happens other than my device going into the bootloader. I have tried flashing both the most recent TWRP 3.1.1 and 3.1.0 yet I keep on coming to the same problem. Can anyone provide help? thanks in advance.
GarGarStinks said:
Just a question as I'm having difficulty booting into TWRP.
My device is unlocked and when flashing TWRP using the command "fastboot flash recovery twrp.img" and trying to boot into it nothing happens other than my device going into the bootloader. I have tried flashing both the most recent TWRP 3.1.1 and 3.1.0 yet I keep on coming to the same problem. Can anyone provide help? thanks in advance.
Click to expand...
Click to collapse
Everytime you reboot the pone starts into boot loader. It has a countdown to boot into whatever is commanded.
Once you flashed succesfully the recovery img you just have to select option to boot recovery with vol keys and power.
Phone will reboot into bootloader agin let it boot on contdown (don't press any key)
Then it will boot into twrp.
Hello, on nougat i am trying to install the twrp, I downloaded the official bootloader release program (after installing the message "unlocked device") but trying to install the twrp via fastboot me by an error message. ... but I think the problem is the unlocking of the bootloader (if I turn the ze553kl in fastboot mode I see my device is "locked") ... there is another version of the bootloader release software? The one available on asus site would look for android M ... maybe there is one for Nougat? Thanxs
Wop. I used the M version apk on Nougat. It worked with no issues, the unlock of boot loader is successful when all the content of your smartphone is wiped.
For reference: https://www.youtube.com/watch?v=hg77b8o8Jk4 Min 1:29
Thank you! But running the software, does not run any wipe, it only displays an "unlocked" message without having to restart anything else. I also tried to make a "factory reset" and repeat lab process but the result does not change ...
TWRP tip!!
smariob said:
Go to fastboot mode and install TWRP. You can find TWRP and how to install it right here: https://forum.xda-developers.com/zenfone-3-zoom/how-to/twrp-zenfone-3-zoom-t3624551
:
Click to expand...
Click to collapse
If you follow that link and flash the recommended version, TWRP might load upside down and mirrored, impossible to use. I flashed the latest version from the MEGA link (3.1.1) and it was back to normal. Just a head's up for future reference, you might want to update your post.
---------- Post added at 09:39 PM ---------- Previous post was at 09:32 PM ----------
smariob said:
Go to fastboot mode and install TWRP. You can find TWRP and how to install it right here: https://forum.xda-developers.com/zenfone-3-zoom/how-to/twrp-zenfone-3-zoom-t3624551
:
Click to expand...
Click to collapse
If you follow that link and flash the recommended version, TWRP might load upside down and mirrored, impossible to use. I flashed the latest version from the MEGA link (3.1.1) and it was back to normal. Just a head's up for future reference, you might want to update your post.
Updated, never had mirror issues but is always better to have latest recovery.
Edit. Jimbo, I got an anwer from the source it notes: "please use 'fastboot flash recovery' instead of 'fastboot boot' to avoid up side down screen"
I've also tried installing from scratch with Asus flash tool, but I still can not unlock bootloader ... Anyone know if there is also an unofficial method for unlocking the bootloader?
@bizzino what model of Z3Z are you using?
Maybe Unlock bootloader app is intended for specific models... Let me do a little bit of research
Double posted... (Don't know for what reason this is happenning)
smariob said:
@bizzino what model of Z3Z are you using?
Maybe Unlock bootloader app is intended for specific models... Let me do a little bit of research
Click to expand...
Click to collapse
Ze553kl. WW_Z01H
bizzino said:
Ze553kl. WW_Z01H
Click to expand...
Click to collapse
Couldn't find another unlock tool than 2017_0803 ...
What info gives you fastboot mode?
smariob said:
Couldn't find another unlock tool than 2017_0803 ...
What info gives you fastboot mode?
Click to expand...
Click to collapse
Locked
Works just fine, thank you
But how would I go about setting the phone back to stock if needed in the future? (Removing Magisk, and replacing TWRP with the original recovery software).
@bizzino No news for you i wasn't able to find more info I'm sorry. Maybe change it for warranty? @subsector you should flash original recovery via fastboot and then sideload the stock rom

Recovery Mode Stuck On One+ Logo...

hey all!
So this is a first for me... I've been rooting and playing with android for a very long time (going back to the g1 days) and this is the first time I've ever seen this.
So I was on an old version of CM and decided it was time to update finally. I had unrooted a long time ago, but was still running cm perfectly fine. I went to install a new version of recovery (so I could update) and now when I try to boot into recovery I just get the oneplus logo. Here's the strange part, the phone isn't soft bricked... I can still boot into android no problem.
Anyone else every seen this problem? Do I need to start over (unlock bootloader, root, recovery, rom)?
Anyone else ever seen this happen on Oneplus One or any other phone for that matter?
Thanks in advance!
Same Problem Here
I am having the same exact issue with my OPX: I wanted to update my old CyanogenMod and for that I needed to update my TWRP. After I flashed it successfully when trying to boot into Recovery it stucks on the 1+ Logo forever.
If I boot into OS it works (the same old CM since I haven't been able to upgrade), Fastboot as well, it's Recovery that doesn't work.
I found some post for the OP3 that state:
WHY AM I STUCK ON THE TWRP SPLASH SCREEN FOR 8 HOURS?
Be patient, wait another 8 hours.
Just kidding, try this while stuck on the loading screen:
adb shell wipe_misc; adb shell reboot recovery
Some devices might somehow get a flag set in misc that tells the bootloader to ignore the android boot image command line.
This results in the kernel not receiving the hardware name (qcom), which then confuses recovery and causes it to wait forever. FOREVER.
Click to expand...
Click to collapse
I tried it and I got the following error:
/system/bin/sh: wipe_misc: not found
Click to expand...
Click to collapse
I don't know what else to do now. Please help.
janc_z said:
I am having the same exact issue with my OPX: I wanted to update my old CyanogenMod and for that I needed to update my TWRP. After I flashed it successfully when trying to boot into Recovery it stucks on the 1+ Logo forever.
If I boot into OS it works (the same old CM since I haven't been able to upgrade), Fastboot as well, it's Recovery that doesn't work.
I found some post for the OP3 that state:
I tried it and I got the following error:
I don't know what else to do now. Please help.
Click to expand...
Click to collapse
I'm guessing we need to do a full wipe, and go back to the begining (root, reflash reocvery, reflash rom), but hoping not...
zbt1985 said:
I'm guessing we need to do a full wipe, and go back to the begining (root, reflash reocvery, reflash rom), but hoping not...
Click to expand...
Click to collapse
I guess you were right! Here's what I did:
- Tried to reflash TWRP using adb. It did flashed it but couldn't boot it and throws error "dtb not found".
- I found this post that first suggested to use the Blue Spark version of the TWRP. I tried adb-ing it and got the same error.
- In a later comment the following video was suggested: https://www.youtube.com/watch?v=kTdKmceC5xU.
- I the downloaded the stock recovery and the stock ROM from this page: https://devs-lab.com/download-oneplus-official-stock-rom.html. Be sure to find the OnePlus X section.
- Using adb I flashed the stock recovery, did a full wipe, rebooted and copied the stock ROM to my SD card.
- Reboot to Recovery, flash from local, selected the Stock ROM zip and let it do its thing.
- Again, from Fastboot I flashed the latest TWRP. I didn't get any errors now!
- Downloaded the Tesla ROM and flashed it using TWRP.
Everything is working fine now!
janc_z said:
I guess you were right! Here's what I did:
- Tried to reflash TWRP using adb. It did flashed it but couldn't boot it and throws error "dtb not found".
- I found this post that first suggested to use the Blue Spark version of the TWRP. I tried adb-ing it and got the same error.
- In a later comment the following video was suggested: https://www.youtube.com/watch?v=kTdKmceC5xU.
- I the downloaded the stock recovery and the stock ROM from this page: https://devs-lab.com/download-oneplus-official-stock-rom.html. Be sure to find the OnePlus X section.
- Using adb I flashed the stock recovery, did a full wipe, rebooted and copied the stock ROM to my SD card.
- Reboot to Recovery, flash from local, selected the Stock ROM zip and let it do its thing.
- Again, from Fastboot I flashed the latest TWRP. I didn't get any errors now!
- Downloaded the Tesla ROM and flashed it using TWRP.
Everything is working fine now!
Click to expand...
Click to collapse
Lucky you!
I on the other hand can't connect via adb, only fastboot...

Categories

Resources