Motoe5(Nora) Custom recovery not installing - Moto E5 Questions & Answers

I tried to install twrp in my Moto e5 (XT1944-6) device. I flashed the latest twrp image using adb platform tools. But when I switched to recovery mode, the TWRP logo appeared for a long time.
Instead of TWRP UI, a screen came called "Mount". It told me to enter a password,and a keyboard was open. There were 2 options " cancel" and "change language".
But I wasn’t able to do anything. Touches were not working. After a few moments the screen slept.
When I clicked the power button, a complete WHITE SCREEN appeared.
I was trying to go to fastboot mode, but it was coming to recovery mode every time. After a few try, somehow I switched to fastboot mode & restart my device.
Again I went to recovery mode, but TWRP wasn’t there. It was the stock recovery and still it is. Please help!

Tawsif999 said:
I tried to install twrp in my Moto e5 (XT1944-6) device. I flashed the latest twrp image using adb platform tools. But when I switched to recovery mode, the TWRP logo appeared for a long time.
Instead of TWRP UI, a screen came called "Mount". It told me to enter a password,and a keyboard was open. There were 2 options " cancel" and "change language".
But I wasn’t able to do anything. Touches were not working. After a few moments the screen slept.
When I clicked the power button, a complete WHITE SCREEN appeared.
I was trying to go to fastboot mode, but it was coming to recovery mode every time. After a few try, somehow I switched to fastboot mode & restart my device.
Again I went to recovery mode, but TWRP wasn’t there. It was the stock recovery and still it is. Please help!
Click to expand...
Click to collapse
stock overwrites the recovery, you must change the rom to avoid it, and the password thing is called encryption and to remove it you must hit cancel, wipe format data and write yes [THAT WILL ERASE ALL YOUR DATA]

Related

[Q] Can't boot into recovery or erase recovery (TRIED ERASING CACHE)

Hi I am trying to work through the process of rooting my HTC One.
I have some experience with android as I've rooted three different phones now, the One is the only one giving me trouble :/
So I got the bootloader unlocked via the HTC Dev method, and now I'm trying to get recovery to work. I've flashed CWM, CWMT, and TWRP, and no matter which I try I can't boot into recovery via "adb reboot recovery" or via the HBOOT menu. When I try the phone just goes through a regular reboot. I can't use ROM Manager to do it either naturally since I don't have root yet (need recovery to install SuperSU).
However ROM Manager does show I have CWM and TWRP installed (both? weird) so I tried to start over by doing "fastboot erase recovery" but it says
FAILED: (remote: not allowed)
I tried "fastboot erase cache" before and after flashing a recovery and nothing at all changes.
Any ideas? Could I have missed something really simple and stupid? I'm pulling all my hair out trying to figure this out.
I heard some people got it to work by flashing the recovery to the boot partition, but until I get assurance that isn't a terrible horrible idea (like it seems) I don't want to try that.
EDIT: yes, the "fast boot" option in the power menu is already disabled.
I had the same issue. Solved it by disabling the fast boot option within the OS. Under power options.
Worth a shot.
Sent from my HTC One using xda app-developers app
ar3na said:
I had the same issue. Solved it by disabling the fast boot option within the OS. Under power options.
Worth a shot.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply but that option is already disabled
I was facing the same problem, however, what I did was turn on fast boot under settings right after I flashed the recovery.
Then, I rebooted back into the bootloader and I now had ***TAMPERED*** at the top of my screen. I afterwards selected reboot into recovery and bam, I now had TWRP on my phone.
WeegeeNumbuh1 said:
I was facing the same problem, however, what I did was turn on fast boot under settings right after I flashed the recovery.
Then, I rebooted back into the bootloader and I now had ***TAMPERED*** at the top of my screen. I afterwards selected reboot into recovery and bam, I now had TWRP on my phone.
Click to expand...
Click to collapse
Just tried that, didn't work
Also why would you have TAMPERED at the top? Did you change anything else to get that like flash a different HBOOT or fastboot or something?
I'm about to throw this thing out the window -___-
SOLVED
Hallelujah, I got it!
I did nothing differently, but eventually it worked...very weird, but at least I got it! The final iteration to get it working was this:
1. Turn off fast boot option in power menu
2. Boot into bootloader via power menu, then power + vol down
3. go into fastboot
4. from a cmd window, fastboot flash recovery recovery.img
5. fastboot erase cache
6. from the menu, boot into recovery
7. phone boots to the OS instead of recovery
8. boot back into the bootloader via power menu, power + vol down
9. TAMPERED shows up, boot into recovery and it works!
note that i never used adb reboot recovery or adb reboot bootloader, idk if that matters, but I did everything from the phone.
thanks for all your help!
For what it's worth, I use ROM Toolbox's Reboot to recovery option and it works. Though I can see where you'd need to boot to recovery from startup.
TheShadowZero said:
Hallelujah, I got it!
I did nothing differently, but eventually it worked...very weird, but at least I got it! The final iteration to get it working was this:
1. Turn off fast boot option in power menu
2. Boot into bootloader via power menu, then power + vol down
3. go into fastboot
4. from a cmd window, fastboot flash recovery recovery.img
5. fastboot erase cache
6. from the menu, boot into recovery
7. phone boots to the OS instead of recovery
8. boot back into the bootloader via power menu, power + vol down
9. TAMPERED shows up, boot into recovery and it works!
note that i never used adb reboot recovery or adb reboot bootloader, idk if that matters, but I did everything from the phone.
thanks for all your help!
Click to expand...
Click to collapse
this worked very well for me, thanks
TheShadowZero said:
Hallelujah, I got it!
I did nothing differently, but eventually it worked...very weird, but at least I got it! The final iteration to get it working was this:
1. Turn off fast boot option in power menu
2. Boot into bootloader via power menu, then power + vol down
3. go into fastboot
4. from a cmd window, fastboot flash recovery recovery.img
5. fastboot erase cache
6. from the menu, boot into recovery
7. phone boots to the OS instead of recovery
8. boot back into the bootloader via power menu, power + vol down
9. TAMPERED shows up, boot into recovery and it works!
note that i never used adb reboot recovery or adb reboot bootloader, idk if that matters, but I did everything from the phone.
thanks for all your help!
Click to expand...
Click to collapse
Thank you very much dear sir/ma'am.
This worked like a charm where nothing else had worked before!

Boot loop after TWRP

Yes I'm an idiot.
I've managed to get into a boot loop after trying to flash TWRP.
Any one have any idea what I can do? The watch just displays the boot animation over and over.
If i hold the power button it turns off and then on again.
Hope its not bricked
Boot into recovery and wipe all data & do a factory reset... should fix it.
Joe0113 said:
Boot into recovery and wipe all data & do a factory reset... should fix it.
Click to expand...
Click to collapse
How do I boot into recovery?
I managed to get into recovery by swiping the top right of the screen to the bottom left while holding the power button at boot.
I've done a factory reset in recovery mode but I still get the boot looping...
finalbillybong said:
I managed to get into recovery by swiping the top right of the screen to the bottom left while holding the power button at boot.
I've done a factory reset in recovery mode but I still get the boot looping...
Click to expand...
Click to collapse
I do believe that the first step is to unlock your bootloader..which is done by going into ADB and typing
fastboot oem unlock
Tower1972 said:
I do believe that the first step is to unlock your bootloader..which is done by going into ADB and typing
fastboot oem unlock
Click to expand...
Click to collapse
Yes I unlocked to bootloader first.
Still stuck in a bootloop. I can get into download mode, if only there was an odin flashable firmware available.
If I could get into fastboot mode I'd be able to flash TWRP again at least but I can't get the watch to respond to any ADB commands, even in recovery if I select 'sideload via ADB'.
EDIT:Just a quick FYI. I managed to get the watch to boot to three different modes. Swiping different directions on the screen. Top right to bottom left boots to a a reboot menu with download, upload mode etc. Top left to bottom right boots into fastboot mode (Yay). And finally, bottom left to top right loads some kind of debug menu.
Have reflashed boot, system and recovery and am still stuck. Ive tried both stock and twrp but it still just boot loops.
Fixed it by flashing this to system in fastboot: http://forum.xda-developers.com/gea...wear-stock-root-busybox-t2834620#post54636406
Any one still bootlooping:
I rebooted the watch into fastboot mode by holding the power button until the watch restarted, continued holding the power button while swiping TOP LEFT to BOTTOM RIGHT of the screen.
I flashed the stock boot.img from adams pulled firmware, then flashed dess_troys TWRP to recovery then this custom rom to system.
The watch booted more or less straight away.

[Q] Using fastboot to boot directly into Recovery?

Hi, my device (euro 8gb dual sim, 5.0.2 ota updated) got crazy last night with lots of FC and unresponsive behaviour.
It boots into system but even screen is off most of time. I can only access power menu before FCs appear and screen goes off.
I tried to boot into recovery but it is not possible since droid on its backs never appears. (see this thread http://forum.xda-developers.com/mot...orola-moto-g-2014-t2994311/page2#post59096800)
Is there any command to launch recovery menu via fastboot?
Furthermore, since I can access fastboot menu, I saw a "Factory" option near "Recovery" option. What is it for?
PD: If Recovery is really not accesible to perform a factory reset... Maybe flashing recovery.img for my model and firm (5.0.2) could help? Or is it better to flash a full 5.0.2 firm?
Thanks!!

Broken recovery on a nonunlocked bootloader, flashing no command

I have the "no command" screen with the android man , however it flashes in and out. when i hold down the power button and go into ap fastboot mode, i cannot go into recovery (it just shutdown the phone) and factory reset does not work. My phone is a non dev version, is there anything i can do?

Unable to enter Recovery mode after reboot from twrp or stock recovery.

Moin,
My phone was one day suddenly unable to boot into system nor Recovery, but could still enter fastboot.
Took me a while to figure out that USB Hubs let flash attempts fail too. (you can watch the drama in my older posts)
Now i was able to flash System back into a workable state and it looks like that recovery is also successful flashed.
BUT...i can enter recovery only ONCE per Vol - and Power on Button.
i have NO OTHER WAY to enter Recovery at all. i have no reboot option in system (LOS 18.1).
In fastboot/adb command and after one succsesfull reboot per keys, it always stuck after the Sony logo into a black screen. i then have to restart it into system with Vol+ and Power (one vibration) or shut down with vol+ and power for 6 seconds (three vibration) to get it either into fastboot (Vol+ and USB connect) or system again. then i have to flash it again to get into TWRP once. i tryed the latest twrp version (3.7.0) and one older version (3.3.1) that had once worked until the phone broke.
Any idea what is going wrong here. i have already try to completly wipe everything from the phone and try to fix SEL Linux in twrp. nothing seems to work. Did i miss something?
/€: Now it is again in the full broken state. recovery nor System won't boot anymore and end in a black screen.
/€²: Found the Problem: my lilca zip was polluted with altered files i forgot about.

Categories

Resources