Long story short, got a brand new Dev Edition at work. Unlocked the bootloader from Moto. Downloaded all the latest TWRP img and SUperSU zip for rooting but TWRP never installs. Here is what the output from fastboot says:
Code:
C:\Users\***********\Downloads>mfastboot flash recovery openrecovery-twrp-2.8.4.0-ghost.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'recovery' (9184 KB)...
OKAY [ 1.005s]
writing 'recovery'...
OKAY [ 0.998s]
finished. total time: 2.006s
I then select to boot into recovery right from the bootloader menu and it just boots to the system. If I "adb reboot recovery" I get stock recovery and not TWRP. I undertsand the system is overwriting my TWRP but thats due to not booting into TWRP first after flashing so it can disable it.
I have read and read and read and found numerous people with no answers other that just keep flashing it. I have flash CWM/Older TWRPs/PHiLz multiple times with the same result.
Thoughts/help/anything? (yes i have tried different ports/cables/etc, same results)
slim
UPDATE:
So I got a little bit closer, flash the recovery and then unplugged from computer, selected to boot into recovery from fastboot menu but now it just boots to black.
WTF is going on. I've had easier times with Samsung and LG products.
Sounds like you're using the power button instead of volume up to select an option in the bootloader. Reflash the recovery then select boot into recovery using volume up.
Ahhh FFS. That's it. Forgot about that. Been a while.
Cheers!
I know you said using the right keys fixed it... But I'm just adding this tip in case others come across this thread...
We've also seen where some have had to reboot-bootloader and go into recovery IMMEDIATELY after flashing recovery or it wont stick. example:
mfastboot flash recovery twrp.img
mfastboot reboot-bootloader
{then use the phone's on screen instructions to select recovery}
This has happened when flashing back to stock recovery too.
Related
I have a Streak 7 (unlocked WiFi + 3G/4G) with Stock Honeycomb. I previously Rooted it and had CWM Recovery installed (not sure which version, but I think it was 5.something). Somehow, I seem to have reverted to the stock recovery. I don't know how this happened, but I noticed it first when I tried to make a backup last week. I have tried several times to flash CWM recovery (both versions 5.0.2.7 and 5.0.2.8) but I keep getting the stock recovery when I boot to recovery. Otherwise, everything seems to operate normally.
I use fastboot to flash recovery and get the following:
C:\Android ADB Streak\Streak\Win32>fastboot flash recovery recovery.img
sending 'recovery' (4402 KB)...
OKAY [ 0.507s]
writing 'recovery'...
OKAY [ 1.355s]
finished. total time: 1.863s
On the Streak screen, I see:
Starting Fastboot USB Download Protocol
Flashing StorMgr partition recovery
Read after write partition recovery
then I reboot the Streak:
C:\Android ADB Streak\Streak\Win32>fastboot reboot
rebooting...
finished. total time: 0.002s
But when I boot into recovery, I get the stock recovery. Am I doing something wrong?
wdwray said:
I have a Streak 7 (unlocked WiFi + 3G/4G) with Stock Honeycomb. I previously Rooted it and had CWM Recovery installed (not sure which version, but I think it was 5.something). Somehow, I seem to have reverted to the stock recovery. I don't know how this happened, but I noticed it first when I tried to make a backup last week. I have tried several times to flash CWM recovery (both versions 5.0.2.7 and 5.0.2.8) but I keep getting the stock recovery when I boot to recovery. Otherwise, everything seems to operate normally.
I use fastboot to flash recovery and get the following:
C:\Android ADB Streak\Streak\Win32>fastboot flash recovery recovery.img
sending 'recovery' (4402 KB)...
OKAY [ 0.507s]
writing 'recovery'...
OKAY [ 1.355s]
finished. total time: 1.863s
On the Streak screen, I see:
Starting Fastboot USB Download Protocol
Flashing StorMgr partition recovery
Read after write partition recovery
then I reboot the Streak:
C:\Android ADB Streak\Streak\Win32>fastboot reboot
rebooting...
finished. total time: 0.002s
But when I boot into recovery, I get the stock recovery. Am I doing something wrong?
Click to expand...
Click to collapse
You press/hold +Vol button, press/hold the power button till the menu comes up. You then select option #2 and press the power button. That will take into CWM.
Thanks. I feel like a clone:cyclops:; I forgot about selecting option 2. Although it would be helpful if each Android device didn't have a different way of getting to Recovery.
Thank you very much .... But when I select option 2 "install update .... " my device freeeze on boot !!!!!!!!!!
Can you give me a solution please .. thanks
kdultimate said:
Thank you very much .... But when I select option 2 "install update .... " my device freeeze on boot !!!!!!!!!!
Can you give me a solution please .. thanks
Click to expand...
Click to collapse
You've flashed the CWM via Fastboot and your trying to boot into it now?
I would make sure you are at least 60% charge first.
Yes .... Exactly i flashed cwm via fastboot ... Writing recovery ok ... But when i tried to enter " the device freeze on install update package and i cannot make anything... Thanks
kdultimate said:
Yes .... Exactly i flashed cwm via fastboot ... Writing recovery ok ... But when i tried to enter " the device freeze on install update package and i cannot make anything... Thanks
Click to expand...
Click to collapse
There are a few different CWM versions, so it's possible that you used a version not compatiable with your ROM.
The same was happening to my streak but i installed version 3.0.x.x and it worked with that one
Sent from my LG-P999 using xda app-developers app
Hi, I have an htc one m7 verizon. I am currently running nusense 7.8. I wanted to update to v8.0. Anyway I go to recovery from the menu and the screen goes black like it is going to the team win logo but it goes back to the white screen that says entering recovery. It stays on that screen until I power plus volume down. I am confused because twrp loaded fine. I have tried cwm as well. no recovery software will load. The phone boots to nusense 7.8 fine. Anyone know what would cause recovery software not to load?
Try flashing the latest version of TWRP through Fastboot to see if the issue resolves. Make sure you use TWRP for the Verizon M7.
MarkBell said:
Try flashing the latest version of TWRP through Fastboot to see if the issue resolves. Make sure you use TWRP for the Verizon M7.
Click to expand...
Click to collapse
I agree re-flash TWRP for Verizon
http://techerrata.com/browse/twrp2/m7vzw
fastboot flash recovery openrecovery-twrp-2.8.0.1-m7wlv.img
fastboot erase cache
fastboot reboot-bootloader
Thanks for throwing up the link clsA. I was about to do that a minute ago when my phone died. Lol.
I will give twrp 2.8.0.1 a try. I have tried several versions but not that one.
fastboot flash recovery openrecovery-twrp-2.8.0.1-m7wlv.img
fastboot erase cache
fastboot reboot-bootloader[/QUOTE]
I tried the above and I am still getting stuck with the white screen green htc logo and entering recovery at the top. I am happy with nusense 7.8 except for youtube not working. I do have some backups that are useless when twrp will not load. Maybe it is time to ruu this phone.
I installed the ruu VZW.M7.5.28.605.2.PN0731IMG.zip. It installed ok. I am still s off and rooted. I used flashify to flash twrp 2.8.0.1. My phone still will not load a recovery app.......I wonder if this is a hardware issue?
Anybody have any ideas? everything on my phone works accept the ability to load the recovery software. Like I said I was able to install an RUU file with fastboot. I would really like to get twrp working so I can backup and restore again.
I think I found my issue. I am pretty sure my recovery partition is hosed. The command fastboot format recovery fails. I get this message:
Formatting is not supported for filesystem with type 'raw.
Anybody know how to rebuild a corrupted recovery partition?
vaping redhead said:
I think I found my issue. I am pretty sure my recovery partition is hosed. The command fastboot format recovery fails. I get this message:
Formatting is not supported for filesystem with type 'raw.
Anybody know how to rebuild a corrupted recovery partition?
Click to expand...
Click to collapse
recovery partition is a raw partition, the only EXT4 partitions are /system, /cache, and /data
can you copy/paste your command prompt output as you do the fastboot commands that clsA gave you.
nkk71 said:
recovery partition is a raw partition, the only EXT4 partitions are /system, /cache, and /data
can you copy/paste your command prompt output as you do the fastboot commands that clsA gave you.
Click to expand...
Click to collapse
Here you go.
c:\adb>fastboot flash recovery openrecovery-twrp-2.8.0.1-m7wlv.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9596 KB)...
OKAY [ 1.071s]
writing 'recovery'...
OKAY [ 0.862s]
finished. total time: 1.935s
c:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.511s]
finished. total time: 0.512s
c:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.041s]
finished. total time: 0.041s
I have tried flashify, and also an ruu version of twrp. still no go.
Have you tried turning s on, relocking bootloader, running RUU, doing factory reset in Stock recovery and then unlocking and installing TWRP? It is worth a shot I assure you. I had problems with TWRP about a month back and this solved it for me.
I've got a moto x '14 verizon XT1096. Tried to use fastboot to load twrp to eventually get to install Cm13. However, it threw this message:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (0 KB)...
OKAY [ 0.006s]
writing 'recovery'...
(bootloader) Invalid boot image
FAILED (remote failure)
finished. total time: 0.024s
Dumbass me thought it would be a good idea to unplug the device and simply try again. Well, what a bad decision. The phone now flashes the "no command" robot on it's back. yes, flashes. i can get back to fastboot, but after this i'm not sure what to do.
Thanks in advance. I'm fairly new at this, be easy on me.
Try this. This is my mini guide I wrote in another thread.
Well, at first I tried to flash twrp through fastboot but the original recovery override the twrp recovery.
So, what I did, instead of flashing, I just temporary booted into twrp.
adb reboot bootloader
fastboot boot twrp.img (and not fastboot flash recovery twrp.img)
Then phone booted into twrp, I flash supersu 2.46.
Then I easily downloaded twrp manager from google play and installed twrp recovery to my xt1096.
Have fun
Use this https://twrp.me/devices/motorolamotox2014.html
Click to expand...
Click to collapse
I flashed latest twrp while on MIUI 9 stable using command prompt. Booted into recovery (TWRP) using the command fastboot boot twrp.img. While in TWRP I "swiped to allow modifications" then rebooted to system. Device was stuck at MI logo with unlocked written at bottom. Also, before flashing TWRP device had pattern and fingerprint lock and bootloader was unlocked.
Next, using MIUI ROM Flashing Tool, I flashed latest MIUI fastboot developer ROM with flash all. Decided to flash TWRP again using command prompt and booted into recovery (TWRP) while the device was still in fastboot mode but this time using Volume Up + Power button. Inside TWRP selected reboot then system. Guess what? Again stuck at MI logo. Before flashing TWRP device had no pattern or fingerprint lock and bootloader was unlocked.
Code:
E:\MI5\platform-tools>adb devices
List of devices attached
3855f609 device
E:\MI5\platform-tools>adb reboot bootloader
E:\MI5\platform-tools>fastboot devices
3855f609 fastboot
E:\MI5\platform-tools>fastboot flash recovery E:\MI5\platform-tools\twrp-3.2.1-0-gemini.img
target reported max download size of 536870912 bytes
sending 'recovery' (20280 KB)...
OKAY [ 0.742s]
writing 'recovery'...
OKAY [ 0.150s]
finished. total time: 0.909s
E:\MI5\platform-tools>
Now I am again on developer ROM. Am I doing something wrong? Something else to do after flashing TWRP?
Update: Again tried to flash TWRP but this time formatted data in Wipe menu also but got stuck in bootloop again.
Just flash any rom what is ur purpose rom installation or rooting
I'm so to ask such a newb question, but I'm all out of ideas.
I unlocked the bootloader on my Mi 9 - I have the Chinese version.
I enabled developer options and turned on USB Debugging.
I downloaded TWRP.
I verified that I could push commands to my phone by rebooting it - adb reboot bootloader
That worked just fine. The phone booted to bootloader.
Then I tried to flash TWRP.
C:\Users\***\Documents\TEMP>fastboot flash recovery twrp-3.2.3-1-cepheus-mauronofrio.img
target reported max download size of 536870912 bytes
sending 'recovery' (56928 KB)...
OKAY [ 1.275s]
writing 'recovery'...
OKAY [ 0.305s]
finished. total time: 1.582s
C:\Users\***\Documents\TEMP>fastboot reboot
rebooting...
finished. total time: 0.003s
C:\Users\Brett\Documents\TEMP>
From what I can tell, the flash worked. I see no errors.
Following the instructions I see over at the Cyanogenmod forums, I held the Volume Up button.
The phone immediately went to bootloader.
I tried Volume Up and the Power button.
The phone immediately went to bootloader.
I saw somewhere that for phones that are Oreo and later, to use "recovery_ramdisk" but that partition does not exist.
It's almost like there is no recovery that I can boot up. I'm not sure what I am doing wrong.
Has anyone run into this before?
Thanks!
funmunke said:
I'm so to ask such a newb question, but I'm all out of ideas.
I unlocked the bootloader on my Mi 9 - I have the Chinese version.
I enabled developer options and turned on USB Debugging.
I downloaded TWRP.
I verified that I could push commands to my phone by rebooting it - adb reboot bootloader
That worked just fine. The phone booted to bootloader.
Then I tried to flash TWRP.
C:\Users\***\Documents\TEMP>fastboot flash recovery twrp-3.2.3-1-cepheus-mauronofrio.img
target reported max download size of 536870912 bytes
sending 'recovery' (56928 KB)...
OKAY [ 1.275s]
writing 'recovery'...
OKAY [ 0.305s]
finished. total time: 1.582s
C:\Users\***\Documents\TEMP>fastboot reboot
rebooting...
finished. total time: 0.003s
C:\Users\Brett\Documents\TEMP>
From what I can tell, the flash worked. I see no errors.
Following the instructions I see over at the Cyanogenmod forums, I held the Volume Up button.
The phone immediately went to bootloader.
I tried Volume Up and the Power button.
The phone immediately went to bootloader.
I saw somewhere that for phones that are Oreo and later, to use "recovery_ramdisk" but that partition does not exist.
It's almost like there is no recovery that I can boot up. I'm not sure what I am doing wrong.
Has anyone run into this before?
Thanks!
Click to expand...
Click to collapse
Try this dm-verity disabler
https://zackptg5.com/android.php#disverfe
What I did is like this
Flash rom
Flash dm-verity disabler
Flash magisk
Done
BTW, I don't quite understand your problem
Your phone stuck in bootloader or TWRP?
For TWRP you can try that dm-verity disabler
Thanks, this saved my life. I had problems with
"FAILED (remote: Token Verify Failed, Reboot the device)"
After i flashed the last rom i used(Pixel Experince) with this dm-verity disable it workes now !!
funmunke said:
I'm so to ask such a newb question, but I'm all out of ideas.
I unlocked the bootloader on my Mi 9 - I have the Chinese version.
I enabled developer options and turned on USB Debugging.
I downloaded TWRP.
I verified that I could push commands to my phone by rebooting it - adb reboot bootloader
That worked just fine. The phone booted to bootloader.
Then I tried to flash TWRP.
C:\Users\***\Documents\TEMP>fastboot flash recovery twrp-3.2.3-1-cepheus-mauronofrio.img
target reported max download size of 536870912 bytes
sending 'recovery' (56928 KB)...
OKAY [ 1.275s]
writing 'recovery'...
OKAY [ 0.305s]
finished. total time: 1.582s
C:\Users\***\Documents\TEMP>fastboot reboot
rebooting...
finished. total time: 0.003s
C:\Users\Brett\Documents\TEMP>
From what I can tell, the flash worked. I see no errors.
Following the instructions I see over at the Cyanogenmod forums, I held the Volume Up button.
The phone immediately went to bootloader.
I tried Volume Up and the Power button.
The phone immediately went to bootloader.
I saw somewhere that for phones that are Oreo and later, to use "recovery_ramdisk" but that partition does not exist.
It's almost like there is no recovery that I can boot up. I'm not sure what I am doing wrong.
Has anyone run into this before?
Thanks!
Click to expand...
Click to collapse
many users run into this problem, including me.
just boot to bootloader, flashing latest twrp
don't restart your phone using command, just press vol. up + power
you'll directly booting into twrp in few seconds
tawa2525 said:
Try this dm-verity disabler
https://zackptg5.com/android.php#disverfe
What I did is like this
Flash rom
Flash dm-verity disabler
Flash magisk
Done
BTW, I don't quite understand your problem
Your phone stuck in bootloader or TWRP?
For TWRP you can try that dm-verity disabler
Click to expand...
Click to collapse
I can't get TWRP to come up. I flash the image and then try to boot to recovery, but there is no recovery. When you try to get fastboot.
ain_gt said:
many users run into this problem, including me.
just boot to bootloader, flashing latest twrp
don't restart your phone using command, just press vol. up + power
you'll directly booting into twrp in few seconds
Click to expand...
Click to collapse
I tried that and got fastboot instead of TWRP
funmunke said:
I tried that and got fastboot instead of TWRP
Click to expand...
Click to collapse
So...I figured it out. You are going to laugh at me.
That version of TWRP was garbage. I switched to another version and now I'm up and running.
Thanks to everyone who responded!