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
Related
The phone is unlocked and is working fine but out of the sudden it is hung at boot up screen.
Now i cannot even access the RA-nexus recovery gui. It will hang at the screen with the 'X' logo.
I tried to re-flash the recovery but got the below error when i try to do a fastboot.
"
D:\Downloads\Nexus One\android-sdk-windows\tools>fastboot devices
123456789012 fastboot
D:\Downloads\Nexus One\android-sdk-windows\tools>fastboot flash recovery recover
y-RA-nexus-v1.7.0.img
sending 'recovery' (3948 KB)... OKAY
writing 'recovery'... FAILED (remote: not allowed)
D:\Downloads\Nexus One\android-sdk-windows\tools>
"
Another weird output when i ran the 'fastboot-windows.exe devices -s'
"
C:\1>fastboot-windows.exe devices -s
123456789012 fastboot
"
Seems like i need a GoldCards for Nexus One but i don't know how to make it since my only Nexus One is not accessible now.
Any help on this??
Are to you doing this to enter recovery from bootloader mode (vol down, power)
try flashing the stock recovery image...
jerrycycle said:
Are to you doing this to enter recovery from bootloader mode (vol down, power)
Click to expand...
Click to collapse
Cannot enter the recovery from bootloader too. After selecting the 'recovery' option, it will stuck with the 'X' nexus icon.
craigacgomez said:
try flashing the stock recovery image...
Click to expand...
Click to collapse
Where can i find the stock recovery image?
If you used superboot to root try these instructions.
http://theunlockr.com/2010/01/08/how-to-load-a-custom-rom-on-the-nexus-one/
When i try to run the command, i will hit the 'FAILED (remote: not allowed)' error.
'
>fastboot flash recovery recovery-RA-nexus-v1.7.0.img
sending 'recovery' (3948 KB)... OKAY
writing 'recovery'... FAILED (remote: not allowed)
'
jerrycycle said:
If you used superboot to root try these instructions.
http://theunlockr.com/2010/01/08/how-to-load-a-custom-rom-on-the-nexus-one/
Click to expand...
Click to collapse
Did you save the recovery image to the superboot folder?
jerrycycle said:
Did you save the recovery image to the superboot folder?
Click to expand...
Click to collapse
Yup.
D:\Downloads\Nexus One\ROM\1.0-EPE54B-nexusone-insecure>fastboot-windows.exe flash recovery recovery-RA-nexus-1.7.0.img
sending 'recovery' (3948 KB)... OKAY
writing 'recovery'... FAILED (remote: not allowed)
Just try this. I know with the mt3g it worked a few time. Try to erase the recovery partition (IE: fastboot erase recovery). This will erase the recovery image. THEN immediately after reflash the recovery (IE: fastboot flash recovery <PATH TO Amon_RA1.0.7>)....Report back your findings
I AM NOT RESPONSIBLE FOR FURTHER PROBLEMS!!!! YOU UN-LOCKED AND ARE PERFORMING THIS AT YOUR OWN RISK!!!
Hi,
Still hitting the 'FAILED (remote: not allowed)' error.
"
>fastboot erase recovery
erasing 'recovery'... FAILED (remote: not allowed)
"
martin0285 said:
Just try this. I know with the mt3g it worked a few time. Try to erase the recovery partition (IE: fastboot erase recovery). This will erase the recovery image. THEN immediately after reflash the recovery (IE: fastboot flash recovery <PATH TO Amon_RA1.0.7>)....Report back your findings
I AM NOT RESPONSIBLE FOR FURTHER PROBLEMS!!!! YOU UN-LOCKED AND ARE PERFORMING THIS AT YOUR OWN RISK!!!
Click to expand...
Click to collapse
no clue then man. I mean you said your un-locked and all, ARE YOU POSITIVE? In fastboot it says "Un-locked"?? Just first time i've seen this on here.....not sure what it could be....+ I have limited android skills (sadly).....
acidash said:
Where can i find the stock recovery image?
Click to expand...
Click to collapse
When my recovery went bonkers, I used a stock recovery image to fix the issue.
http://autisticpig.com/android/roms and flashes/PASSIMG_Passion_/recovery.img
Give that a try and see if things aren't more normal.
I guess it somehow lost its root access and now my nexus one is useless until i can get hold of a goldcards.
;(
martin0285 said:
no clue then man. I mean you said your un-locked and all, ARE YOU POSITIVE? In fastboot it says "Un-locked"?? Just first time i've seen this on here.....not sure what it could be....+ I have limited android skills (sadly).....
Click to expand...
Click to collapse
Thanks. It hit the 'FAILED (remote: not allowed)' error again.
deprecate said:
When my recovery went bonkers, I used a stock recovery image to fix the issue.
http://autisticpig.com/android/roms and flashes/PASSIMG_Passion_/recovery.img
Give that a try and see if things aren't more normal.
Click to expand...
Click to collapse
acidash said:
Where can i find the stock recovery image?
Click to expand...
Click to collapse
You can pull out the recovery from the stock passion image... http://forum.xda-developers.com/showthread.php?t=642811
If you can't flash the stock recovery as well, try a complete restore to stock... rename the zstock passion image zip to PASSIMG.zip, copy to the SD card,, boot into bootloader and when it asks, apply the update...
One more thing, you could try Koush's Clockwork recovery image from http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html (direct link http://koush.romraid.com/recoveries/recovery-clockwork-passion.img)
craigacgomez said:
You can pull out the recovery from the stock passion image... http://forum.xda-developers.com/showthread.php?t=642811
If you can't flash the stock recovery as well, try a complete restore to stock... rename the zstock passion image zip to PASSIMG.zip, copy to the SD card,, boot into bootloader and when it asks, apply the update...
One more thing, you could try Koush's Clockwork recovery image from http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html (direct link http://koush.romraid.com/recoveries/recovery-clockwork-passion.img)
Click to expand...
Click to collapse
+1 for this
Tried the 'PASSIMG.zip' method, and it says Update Partition Fails.
Now i cannot even power it up.
craigacgomez said:
You can pull out the recovery from the stock passion image... http://forum.xda-developers.com/showthread.php?t=642811
If you can't flash the stock recovery as well, try a complete restore to stock... rename the zstock passion image zip to PASSIMG.zip, copy to the SD card,, boot into bootloader and when it asks, apply the update...
One more thing, you could try Koush's Clockwork recovery image from http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html (direct link http://koush.romraid.com/recoveries/recovery-clockwork-passion.img)
Click to expand...
Click to collapse
Try getting a warranty/RMA for your device. There is something larger going on here than the fact the phone is unlocked...you should be able to flash recovery even if that partition is hosed.
actually, does anyone know a means to format just the partition recovery resides?
Oh wait..you said it won't power on...
Give HTC a ring; it may be your only recourse unless you can get your phone back on.
yup. Since i cannot even power it on, HTC is my only option.
Thanks all for all the guides.
deprecate said:
Try getting a warranty/RMA for your device. There is something larger going on here than the fact the phone is unlocked...you should be able to flash recovery even if that partition is hosed.
actually, does anyone know a means to format just the partition recovery resides?
Oh wait..you said it won't power on...
Give HTC a ring; it may be your only recourse unless you can get your phone back on.
Click to expand...
Click to collapse
HELP ME! I cannot get this recovery image to flash for the life of me. here's the story. I have what was a ere27 build N1. 2 weeks ago I did the manual update to Google's prerelease of Froyo. Now my phone is a FRF50 build. As everyone else found out it's buggy as hell and GPS does not work. I searched for weeks to try and find a fix and I couldn't find anything other than to unlock the bootloader root the device and flash a different rom onto the phone. So I unlocked the BL from instructions here. Then in downloaded Pauls 1.0 FRF50 superboot. I tested the root with torch and it works, so the unlock and root must have worked. This is the first time I have ever used the cmd window and I have tried everything under the sun to get this thing to work so I can flash Pauls froyo and have working GPS again.
I followed the instructions found here, but I keep getting this error.
Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.
cd C:\fastboot
C:\fastboot>fastboot-windows devices
HT9C*******8 fastboot
C:\fastboot>fastboot-windows flash recovery C:\fastboot\recovery-RA-nexus-v1.6.2
sending 'recovery' (3954 KB)... FAILED (remote: not allowed)
have you done 'fastboot-windows oem unlock' ?
Yessir. Unlocked padlock on startup.
Try this:
fastboot devices
fastboot flash recovery recovery.img
C:\fastboot>fastboot flash recovery C:\fastboot\recovery-RA-nexus-v1.6.2
sending 'recovery' (3954 KB)... OKAY [ 0.641s]
writing 'recovery'... OKAY [ 1.563s]
finished. total time: 2.203s
so it worked once, then it went back to the stock recovery...
Hyper4mance2k said:
C:\fastboot>fastboot flash recovery C:\fastboot\recovery-RA-nexus-v1.6.2
sending 'recovery' (3954 KB)... OKAY [ 0.641s]
writing 'recovery'... OKAY [ 1.563s]
finished. total time: 2.203s
so it worked once, then it went back to the stock recovery...
Click to expand...
Click to collapse
I'm having the EXACT same problem.
Did you apply root before flashing recovery? Flash Paul's superboot, then install AmonRA recovery.
ATnTdude said:
Did you apply root before flashing recovery? Flash Paul's superboot, then install AmonRA recovery.
Click to expand...
Click to collapse
The OP says he is rooted. I am rooted as well. We both have had success in fastboot, but our recovery is defaulting to the standard android one, and not the custom one that we flash.
Hyper4mance2k said:
C:\fastboot>fastboot flash recovery C:\fastboot\recovery-RA-nexus-v1.6.2
sending 'recovery' (3954 KB)... OKAY [ 0.641s]
writing 'recovery'... OKAY [ 1.563s]
finished. total time: 2.203s
so it worked once, then it went back to the stock recovery...
Click to expand...
Click to collapse
All you need to do is
Fastboot flash recovery recovery-ra.img
Or whatever the image name needs to be.
I think I figured out the problem. I was running a rooted version of FRF72, and for whatever reason, no matter how I tried to flash the recovery, it would not stick. I could use clockwork's app to flash and reboot into the custom recovery, but if I rebooted again, it would always default to the stock android recovery.
I now have the custom recovery working for me at all times. Here is what I did (Keep in mind, I take no responsibility if you brick your phone into oblivion...):
First: Make sure that you have an unlocked bootloader, and are rooted. I used Paul's Superboot for the FRF50 build on my FRF72 build, and it worked flawlessly.
1. Find a custom ROM such as the MoDaCo MCR18 or 19 build if you want something close to the OTA builds.. or whichever one you'd like to flash. Make sure it is not a stock/rooted OTA build! I personally used Paul's MCR18 build over at MoDaCo.
2. Download it, and then rename the rom to update.zip and transfer to your SD card's main directory
3. Download the clockwork ROM Manager app from the android Market and run it.
4. Flash ClockworkMod Recovery from the app
5. Use the feature in the app to "Reboot into Recovery"
6. You should now be in the ClockworkMod recovery
7. Do a nandroid backup!! (that may reboot your phone normally.. if so, repeat steps 4 & 5 to reboot back into custom recovery)
8. If your rom requires you to wipe prior to install, then wipe cache partition from the main menu, and then go to advanced and wipe Dalvik cache prior to the next step. I did not have to wipe, so if this rebots your phone normally, repeat steps 4 &5 to get back into custom recovery.
9. Select the option to "apply sdcard:update.zip"
It will then flash the custom ROM onto your Nexus One
10. Once your phone has been rebooted, download the ClockworkMod Rom Manager from the market again (if it is not already on your phone), and re-flash the custom recovery. It should now always boot into the custom recovery.
Hope that helps!!
hii ...
i have HTC butterfly s phone is boot looping ,,,
issue :
when entering OS i can see the lock screen for 3 seconds then reboot.
solutions tried :
1- tried to wipe from TWRP recovery when it reaches /data >>> reboot.
2- tried to install another ROM without wiping >>>> reboot
3- tried to install CWM recovery , it says completed in fastboot (CMD) but recovery is not changing.
4- tried to lock the boot loader again , it says no such file or directory .
5- tried to boot in safemode but i see the lock screen for 3 seconds then reboot
iam stuck ... please help
thank you
hello
it happened to me the same, I just download it stock rom that is here, you have to see the version of your phone to know which is for yours.
greetings and good luck
all credits to the creator of the post
http://forum.xda-developers.com/showthread.php?t=2663295
GAVANA said:
hello
it happened to me the same, I just download it stock rom that is here, you have to see the version of your phone to know which is for yours.
greetings and good luck
all credits to the creator of the post
http://forum.xda-developers.com/showthread.php?t=2663295
Click to expand...
Click to collapse
hi .. thanks for reply ,,,
i downloaded stock rom 2.21 and tried to flash it from recovery when it tries to install the rom when it reaches to writing /data phone reboots
you mean something else ?
thanks ...
i want to add one thing ,,,
i have TWRP recovery 2.6.0.0 and i want to change it to CWM , i try to install from fastboot and it says successful but when i go into recovery its not changed !!!!!!
recovery recovery.img
sending 'recovery' (12364 KB)... OKAY [ 1.794s]
writing 'recovery'... OKAY [ 0.983s]
finished. total time: 2.777s
hwoarang626 said:
i want to add one thing ,,,
hello
at first I was the same with the recovery, but install this and it worked well, and use that version of android stock for now
but if you want to upgrade later (OTAS), you would have to have stock recovery and unroot your device, saludos
http://forum.xda-developers.com/showthread.php?t=2730482 .
i have TWRP recovery 2.6.0.0 and i want to change it to CWM , i try to install from fastboot and it says successful but when i go into recovery its not changed !!!!!!
recovery recovery.img
sending 'recovery' (12364 KB)... OKAY [ 1.794s]
writing 'recovery'... OKAY [ 0.983s]
finished. total time: 2.777s
Click to expand...
Click to collapse
hello
at first I was the same with the recovery, but install this and it worked well, and use that version of android stock for now
but if you want to upgrade later (OTAS), you would have to have stock recovery and unroot your device
regards
http://forum.xda-developers.com/showthread.php?t=2730482
its the same ,,, i tried to install the recovery you gave me but it did not install the recovery , Iam still stuck with a recovery that is not doing anything .
thanks
one more point ,,, i noticed that my /system is empty ...
hwoarang626 said:
one more point ,,, i noticed that my /system is empty ...
Click to expand...
Click to collapse
Since no one else is really helping you I will.
So what I gathered is your Rom bootloops and you've tried installing stock Rom but still no luck so you want to switch recoveries but you can't get twrp to flash...?
1. Are you S-Off or S-On? If you are s-on you must flash boot.img with this command
Code:
fastboot flash boot boot.img
2. To flash a recovery made for your device you must place it in fastboot and enter this
Code:
fastboot flash recovery recovery.img
3. Place Rom on internel storage if you choose cwm because it doesn't support external sdcard like twrp. For latest twrp, message @kairi_zeroblade... If you can't place on internal with cwm then you must do a sideload with the Rom same goes for twrp.
Want to support InsertCoin? Just get our donate key
xXminiWHOOPERxX said:
Since no one else is really helping you I will.
So what I gathered is your Rom bootloops and you've tried installing stock Rom but still no luck so you want to switch recoveries but you can't get twrp to flash...?
1. Are you S-Off or S-On? If you are s-on you must flash boot.img with this command
Code:
fastboot flash boot boot.img
2. To flash a recovery made for your device you must place it in fastboot and enter this
Code:
fastboot flash recovery recovery.img
3. Place Rom on internel storage if you choose cwm because it doesn't support external sdcard like twrp. For latest twrp, message @kairi_zeroblade... If you can't place on internal with cwm then you must do a sideload with the Rom same goes for twrp.
Want to support InsertCoin? Just get our donate key
Click to expand...
Click to collapse
thank you for your help ,,,
im S-ON
fastboot flash boot boot
.img
< waiting for device >
sending 'boot' (6104 KB)...
OKAY [ 0.830s]
writing 'boot'...
OKAY [ 0.590s]
finished. total time: 1.420s.
fastboot flash recovery
cwm6.0.4.5.img
sending 'recovery' (12364 KB)...
OKAY [ 1.430s]
writing 'recovery'...
OKAY [ 0.990s]
finished. total time: 2.420s
i did what you said but nothing changed im still on TWRP recovery 2.6.0.0 and my room is boot looping
hwoarang626 said:
thank you for your help ,,,
im S-ON
fastboot flash boot boot
.img
< waiting for device >
sending 'boot' (6104 KB)...
OKAY [ 0.830s]
writing 'boot'...
OKAY [ 0.590s]
finished. total time: 1.420s.
fastboot flash recovery
cwm6.0.4.5.img
sending 'recovery' (12364 KB)...
OKAY [ 1.430s]
writing 'recovery'...
OKAY [ 0.990s]
finished. total time: 2.420s
i did what you said but nothing changed im still on TWRP recovery 2.6.0.0 and my room is boot looping
Click to expand...
Click to collapse
Not sure if you can enter this command without a-off but try
Code:
fastboot erase cache
Then repeat the previous post....
If that doesn't work I'd try firewaters universal s-off tool and obtain s-off and try that command or see if it fixes your issues with your device. if that fails your best bet would be to ruu.. if you can't do that either you got a useless device till s-off exploit Is found if that's the reason why it's messing up.... Or donate it to someone who could fix it (me)
Want to support InsertCoin? Just get our donate key
xXminiWHOOPERxX said:
Not sure if you can enter this command without a-off but try
Code:
fastboot erase cache
Then repeat the previous post....
If that doesn't work I'd try firewaters universal s-off tool and obtain s-off and try that command or see if it fixes your issues with your device. if that fails your best bet would be to ruu.. if you can't do that either you got a useless device till s-off exploit Is found if that's the reason why it's messing up.... Or donate it to someone who could fix it (me)
Want to support InsertCoin? Just get our donate key
Click to expand...
Click to collapse
i tried this and no luck ,,,
actually i tried every thing but the problem is that the data does not change in the phone ,, i even formated (real format fsck) to /data and it was showing its empty but after reboot everything went back ,,, iam fixing android phones since htc desire but never faced anything like this ,,,
thank you for your help ,, and what you mean by donate and get it fixed ?
hwoarang626 said:
i tried this and no luck ,,,
actually i tried every thing but the problem is that the data does not change in the phone ,, i even formated (real format fsck) to /data and it was showing its empty but after reboot everything went back ,,, iam fixing android phones since htc desire but never faced anything like this ,,,
thank you for your help ,, and what you mean by donate and get it fixed ?
Click to expand...
Click to collapse
Seem like you fried your "/data" partition from what you just mentioned above. The only way I could see you fix is ruu. Cause HTC won't fix it if you send it in with a custom recovery at which you can't change.
And what I meant is since the device is rendered completely useless, unless you can get a run to ruu. You'd donate it to me this way i could try and fix it...
Sent from my HTC0P4E1 using Tapatalk
xXminiWHOOPERxX said:
Seem like you fried your "/data" partition from what you just mentioned above. The only way I could see you fix is ruu. Cause HTC won't fix it if you send it in with a custom recovery at which you can't change.
And what I meant is since the device is rendered completely useless, unless you can get a run to ruu. You'd donate it to me this way i could try and fix it...
Sent from my HTC0P4E1 using Tapatalk
Click to expand...
Click to collapse
i think im facing the same problem here, do u know where we can find the RUU, I searched the whole internet and i could not find, im ready to donate if u fix my problem and provide me with the RUU.
Regards
mr_wehbe said:
i think im facing the same problem here, do u know where we can find the RUU, I searched the whole internet and i could not find, im ready to donate if u fix my problem and provide me with the RUU.
Regards
Click to expand...
Click to collapse
There is no RUU for this phone, as far as I know. The closest thing to RUU is flashing everything by hand, but this seems to have failed in this case, unfortunately.
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.
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!