So, basically, the details on the Xoom:
Android Version: 3.2.1
Build: HTK75D
Kernel: 2.6.36.3-g111d827 [email protected] #1
Bootloader is unlocked
I am trying to install Tiamat's Clockworkmod image via the ADB method. I do exactly these steps:
adb reboot bootloader
fastboot flash recovery Tiamat-*********-cwm.img
According to the adb console, it says it flashed correctly, and the fastboot also gives the same confirmation.
fastboot reboot
I boot up normally, and run:
adb reboot recovery
It then gives me the dreaded ! mark.
I've spent more than 5 hours trying to get the recovery working, and have tried re downloading the img, changing cables , and the only method that gave me a small glimpse of hope is flashing another img file (cwm 3.0.2.8 flashed) which worked once and then reverted to the ! mark.
Help? If any other info is needed, I will gladly provide.
try this:
1) Flash the recovery via bootloader and the fastboot command
2) After the flash, issue fastboot reboot to reboot the xoom
3) At the M logo during bootup, start hitting the volume down until you see Recovery on the top left corner then hit volume up to select it
That should get you into clockwork mod recovery, after you flash the root package you'll be good to go
Scsa20,
Has this been verified?
Should the offending files, (/system/recovery-from-boot.p OR
/system/etc/install-recovery.sh) be removed per Joe Ferreira's post?
I will try this fix after it has been verified (I've given you a thanks already )
Not sure if this belongs over here in Q/A as a new thread, or if I should append this to shabbypenguin's root thread. I am attempting to root my Photon Q following shabbypenguin's method. I downloaded the latest SDK bundle, installed latest Motorola drivers, successfully unlocked the bootloader.
I can't seem to get any recovery images to flash correctly at this point, though. When I run "fastboot flash recovery cwmrecovery.img" I get the following output:
Code:
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6632 KB)...
OKAY [ 0.519s]
writing 'recovery'...
OKAY [ 2.363s]
finished. total time: 2.885s
Not sure if "Variable not supported" is a normal message or not, but otherwise it appears to have completed successfully? But when I reboot into recovery mode, I always get the android with a red triangle screen, like this. I have tried flashing shabbypenguin's CWM recovery image, the latest TWRP recovery image, and the stock recovery image linked to in this thread. Same result every time; red triangle screen.
My phone is running the updated OTA build (77.8.10). Is that what is hindering my ability to flash and root successfully? Not sure where else I could have gone wrong. The only other thing I can think of is that before starting with all this, I did have encryption enabled on the phone. But before unlocking the bootloader and attempting to flash CWM recovery, I performed a factory reset to remove the encryption.
UPDATE: it doesn't actually seem like the recovery images are getting flashed at all. At first I thought something was being corrupted (given the red triangle).
But if I press the Up/Down Vol buttons on that screen, I get the Android system recovery utility menu. So if a recovery flash had occurred, this would have been overwritten, right?
I'd be grateful for any suggestions of what to try at this point.
i've never seen that bootloader message before, but it seems like your recovery might be getting flashed back to stock when you reboot. another guy had this issue, you might hopefully be able to solve it by reading this short thread here:
http://forum.xda-developers.com/showthread.php?t=2017748
edit; in short, you could try rooting with Motofail2go: http://forum.xda-developers.com/showthread.php?t=1940594, then use your SU priviledge to rename recovery-from-boot.p to recovery-from-boot.bak,(in /system), then reflash recovery of choice and it should stick.
Thanks yogi! That was indeed my problem as well. I hadn't come across that thread in my initial searching, so I really appreciate your ultra fast response and the sage solution you figured out in the earlier thread. You rock!
Ah, glad that worked for you also! I'm not sure why some people have had to do that, while I don't think I ever did(I have a file named recovery-from-boot.bak, but I don't think I actively renamed it). I am also not sure why we have have an unlockable bootloader, yet without a 3rd-party exploit, some people are getting stuck
In shabbys supersu zip the script had it rename that boot on recovery file. Maybe people are skipping that step after flashing recovery or moto changed the file location and it doesnt match shabbys original script now.
Sent from my XT897 using Tapatalk 2
Rangerbry said:
In shabbys supersu zip the script had it rename that boot on recovery file. Maybe people are skipping that step after flashing recovery or moto changed the file location and it doesnt match shabbys original script now.
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
Ah ok, i figured something was renaming that file. The thing is, is there a way to boot straight into recovery from the bootloader? I've always had to boot into the system and then adb reboot recovery.
just hold up like normal after
fastboot reboot
ah yes ok, i guess people should do that after flashing recovery so they can get SU flashed before losing their recovery. and we'll see if Shabby's SU zip still disables that recovery file. i guess that's sort of standard procedure on phones in general, but i don't think i ever did that on this device.
Nice, thanks! Yeah, I was booting back in to system and doing adb reboot recovery as well. The couple blog write-ups I was following weren't clear on that aspect, but then, using the hardware buttons to force it directly to recovery makes perfect since; wondering why I didn't think about that at the time.
Guys!
I have the same problem!
My phone version XT925:
4.1.2
unlocked bootloader
no ROOT
Phone not loading to recovery! so I can't install SU.zip, to get ROOT and rename recovery-from-boot.p.
And because my version 4.1.2 I can't use exploit to get root.
I am realy need your help!
Alex42rus said:
Guys!
I have the same problem!
My phone version XT925:
4.1.2
unlocked bootloader
no ROOT
Phone not loading to recovery! so I can't install SU.zip, to get ROOT and rename recovery-from-boot.p.
And because my version 4.1.2 I can't use exploit to get root.
I am realy need your help!
Click to expand...
Click to collapse
Have you done the hardware key method?
Power + down till phone resets than power + up will you are in recovery?
Otherwise use this command in fastboot(meaning you have SDK tools and you open a command window in platform tools folder):
adb reboot recovery
than the phone should reboot itself into recovery
let us know if you need anything else
Hinyo said:
Have you done the hardware key method?
Power + down till phone resets than power + up will you are in recovery?
Otherwise use this command in fastboot(meaning you have SDK tools and you open a command window in platform tools folder):
adb reboot recovery
than the phone should reboot itself into recovery
let us know if you need anything else
Click to expand...
Click to collapse
>Power + down till phone resets than power + up will you are in recovery?
Phone goes to boot menu.
if I select recovery, phone try to load it (green horizontal anroid logo), but after some time it start the system.
>adb reboot recovery
the same.
Alex42rus said:
>Power + down till phone resets than power + up will you are in recovery?
Phone goes to boot menu.
if I select recovery, phone try to load it (green horizontal anroid logo), but after some time it start the system.
>adb reboot recovery
the same.
Click to expand...
Click to collapse
This means you have stock recovery.
Flash a custom recovery - TWRP, CWM, OpenRecovery.
If you are having issues with recovery not sticking, there is a thread right below yours which addresses this.
Especially see this post from kabaldan.
arrrghhh said:
This means you have stock recovery.
Flash a custom recovery - TWRP, CWM, OpenRecovery.
Click to expand...
Click to collapse
Yes, I am tring, but when I do it, I have "variable not supported" message.
Console:
C:\adt-bundle-windows-x86_64\sdk\platform-tools>fastboot flash recovery twrp-hdr
ecovery.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6678 KB)...
OKAY [ 0.502s]
writing 'recovery'...
OKAY [ 1.960s]
finished. total time: 2.465s
C:\adt-bundle-windows-x86_64\sdk\platform-tools>
Alex42rus said:
Yes, I am tring, but when I do it, I have "variable not supported" message.
Click to expand...
Click to collapse
Please read the link I provided above, and see if it helps you. Or the second post in this thread...
arrrghhh said:
Please read the link I provided above, and see if it helps you. Or the second post in this thread...
Click to expand...
Click to collapse
>Stock OTA update contains /system/etc/install-recovery.sh that will re-flash the recovery to stock any time you boot the android system.
>Boot to custom recovery first before starting the android system after the update
This path realy help me! I go to recovery by presing power + up after recovery.
> and remove this script by using the console or adb shell:
adb shell not connected, and I not find console in recovery, but before reboot recovery ask me to remove "re-install recovery"
great thanks !
Had the same problem trying to flash TWRP to my XT926. Flashing multiple versions of CWM or TWRP gave the same results. (bootloader) variable not supported, but flashing would still appear to proceed ok. However the recovery was always jacked somehow. The only thing that would flash correctly (even with the error) was the stock recovery.
I was using minimal adb & fastboot. Clued in off of a thread off of droid rzr forums (cannot post url due to my new user status) I FINALLY realized I needed to replace the included AOSP binaries with the motorola ones.
Upon replacing the binaries flashing proceeded without error & TWRP was installed & running correctly.
So as this thread came up most of the time when searching for solution to my error, I hope this reply helps.
So, in short double check your version of adb fastboot (or its binaries), your usb drivers, & your recovery is appropriate/ latest update for your phone/ firmware.
Sent from my XT926 using XDA Free mobile app
4ndr01dpilot said:
So, in short double check your version of adb fastboot (or its binaries), your usb drivers, & your recovery is appropriate/ latest update for your phone/ firmware.
Click to expand...
Click to collapse
Thanks for this tip. I used the fastboot version from Motopocalypse instead of my standard ADB installation version, and the variable message stopped appearing. :highfive:
I was puzzled for days being stuck in endless "Flashing recovery ..."
In the end I decided, after saying 1 hour waiting a hypothetical "success/congrats message", NOT QUITTING the current fastboot screen, to select the recovery option in this very fastboot menu (on a Razr i : Vol- to highlight recovery item, then Vol+ to select) and bang I was in TWRP menu. What to do next once in, it is another story.
I'm stuck in a bootloop on Pixel (sailfish). I've rooted with SuperSU and installed TWRP previously. I've never had an issue applying the new updates until today.
Here's the steps I followed:
I downloaded the 7.1.2 (N2G47O, May 2017) update from the google site and verified the SHA 256 hash
I removed the -w from the "fastboot -w update" in flash-all. Then ran flash-all.bat. It completed successfully. The phone rebooted.
Next I powered down the phone and booted to fastboot.
I then tried to install TWRP by running "fastboot boot twrp-3.0.2-RC1-fastboot.sailfish.img"
It installed fine and booted to TWRP.
I opened TWRP and tried to install TWRP. It ran fine. Rebooted and here's where I went into the problem
The phone boots up and gives me the message about "Your Device software can't be checked for corruption. Please lock the bootloader". I've seen this before, so no issues.
Then the Google screen shows up with a black line through it.
Then it comes back to the previous message about the unlocked boot loader.
If I tried to hold POWER down, I get a message "[RAMDUMP] Writing to EXt 4 file" and back to the message about the unlocked boot loader.
How do I fix this ?
UPDATE: After much trying, i finally caught it when it was powered off and managed to get to boot to fastboot where I reflashed the most recent update. But.. is this still the best way to install TWRP ? Or should I do something else?
The problem is the bootloader in the N2G47O. A temporary fix is to download the N2G47E image and extract the `bootloader-sailfish-8996-012001-1702151126.img` file and then boot your phone into fastboot and run `fastboot flash bootloader bootloader-sailfish-8996-012001-1702151126.img`. Then you can boot into TWRP and install whatever you need
Abolfazl said:
The problem is the bootloader in the N2G47O.
Click to expand...
Click to collapse
Thank you very much! I've followed the temp fix and now have both TWRP and SuperSU installed.
I appreciate the quick response and help
Wow this just happened to me too. Thanks for the fish. I guess a better upgrade path is to not skip the April update ( I was coming from March to May)
Also follow the hardware process of booting to fastboot if this is happening, no need to wait for an oppurtunity. Just press Power + Vol - + etc and release to boot to fastboot.
.
THANK YOU!
Abolfazl said:
The problem is the bootloader in the N2G47O. A temporary fix is to download the N2G47E image and extract the `bootloader-sailfish-8996-012001-1702151126.img` file and then boot your phone into fastboot and run `fastboot flash bootloader bootloader-sailfish-8996-012001-1702151126.img`. Then you can boot into TWRP and install whatever you need
Click to expand...
Click to collapse
Saved my life here! I thought I was going to have to deal with Ads until the next time they updated TWRP! This worked beautifully!
Update:
I've got my phone back thanks to this post! https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
--------------------------------------[/B]-----------------------------------------------------------------------------------------------------------------------------------------------
I successfully upgraded my NXT-L29 to Oreo, using the files in this post: https://forum.xda-developers.com/mate-8/general/discussion-oreo-huawei-mate-8-t3785320
(Only difference: used another TWRP version - twrp-3.1.1-1-next.img - since the one in this post didn’t work).
Though my phone worked, it was unrooted again and I tried to solve it by flashing TWRP again. It didn’t work, so I tried flashing TWRP-3.1.0-EMUI-5.0.img. Here’s where everything went wrong.
I get:
ERROR MODE, Please update system again!"
Error! Func: NO: 11 (recovery image)
Error NO: 2 (load failed!)
Here’s what I still can do:
- Get into Fastboot – Bootloader and FRP both Unlocked
- Use ADB
- Get into eRovery
- Get into EMUI update
- Flash TWRP, SYSTEM.img and BOOT.img
What I can’t do:
- Access my phone – get or one of the two yellow messages or Error Mode or Fastboot
- Connect to HiSuite
- Acces Wipe Partion, Factory Settings
- Boot into TWRP
- Flash any Recovery (partition: (length) error, or Cannot load Recovery). No matter what command I try. Fastboot flash recovery_ramdisk RECOVERY.img doesn’t work either.
- Find a RAMDISK.img in the Update.app. Flashing the SYSTEM, CUST and BOOT.img won’t do the trick with rebooting volume up + volume down + power. EMUI update states: Software install failed!
- Use eRovery. Recovery fails every time after 7%
- Find the current Build Number, since there’s no way of getting passed the two yellow messages or Error Mode or Fastboot
I’ve been up till 5 in the morning, trying to solve this without success. Think I’ve tried a 100 commands and methods. Is there anyone who has a solution? I’m really desperate by now.
HQuinn said:
I successfully upgraded my NXT-L29 to Oreo, using the files in this post: https://forum.xda-developers.com/mate-8/general/discussion-oreo-huawei-mate-8-t3785320
(Only difference: used another TWRP version - twrp-3.1.1-1-next.img - since the one in this post didn’t work).
Though my phone worked, it was unrooted again and I tried to solve it by flashing TWRP again. It didn’t work, so I tried flashing TWRP-3.1.0-EMUI-5.0.img. Here’s where everything went wrong.
I get:
ERROR MODE, Please update system again!"
Error! Func: NO: 11 (recovery image)
Error NO: 2 (load failed!)
Here’s what I still can do:
- Get into Fastboot – Bootloader and FRP both Unlocked
- Use ADB
- Get into eRovery
- Get into EMUI update
- Flash TWRP, SYSTEM.img and BOOT.img
What I can’t do:
- Access my phone – get or one of the two yellow messages or Error Mode or Fastboot
- Connect to HiSuite
- Acces Wipe Partion, Factory Settings
- Boot into TWRP
- Flash any Recovery (partition: (length) error, or Cannot load Recovery). No matter what command I try. Fastboot flash recovery_ramdisk RECOVERY.img doesn’t work either.
- Find a RAMDISK.img in the Update.app. Flashing the SYSTEM, CUST and BOOT.img won’t do the trick with rebooting volume up + volume down + power. EMUI update states: Software install failed!
- Use eRovery. Recovery fails every time after 7%
- Find the current Build Number, since there’s no way of getting passed the two yellow messages or Error Mode or Fastboot
I’ve been up till 5 in the morning, trying to solve this without success. Think I’ve tried a 100 commands and methods. Is there anyone who has a solution? I’m really desperate by now.
Click to expand...
Click to collapse
Hi.
According to your post, you flashed TWRP-3.1.0-EMUI-5.0.img then got the problems .
Did you try to flash stock recovery by adb?
You can find it in original ROM files
afromoh said:
Hi.
According to your post, you flashed TWRP-3.1.0-EMUI-5.0.img then got the problems .
Did you try to flash stock recovery by adb?
You can find it in original ROM files
Click to expand...
Click to collapse
Yes, I've tried that about a million times. Everything worked, except flashing the (stock) recovery.
I'm really sorry for my late reply. I've been very ill. Luckily the problem is solved and I've got my phone back. Thanks to Georgian51 who suggested this post: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279.
That did the trick! Thanks for your reply
Hello all,
I bought a refurbished LG G5 (H850) from Aliexpress in order to move it to LineageOS. It has a stock LG Android 8.0.0 (V30f-EUR-XX). I unlocked the bootloader with the file unlock.bin that LG sent me and I can read in fastboot unlocked:yes.
The problem is that I cannot reboot in Recovery mode. I tried :
- when booting in the original LG Recovery: message "No command" with the resting Android robot icon
- I flashed lineage-17.1-20210110-recovery-h850.img successfully and when booting in this recovery I get only two options : Erase data or exit. Erasing data doesn't change anything: after reboot in recovery I have the same options.
- I flashed the twrp-3.5.0_9-0-h850.img recovery, it says OKAY for sending and writing it. If using a command to boot in recovery fastboot boot xxx.img it fails. And adb reboot recovery puts me in the "No command" with the resting Android robot icon
- I reflashed the same lineage recovery and adb reboot recovery puts me in the "No command" with the resting Android robot icon
- I feel that fastboot flash says OKAY but it keeps the original recovery
Has someone experienced this problem with the LG recovery boot? Does this problem come from a special security in the bootloader preventing changing the recovery?
Finally, I found a solution. The problem was that the stock ROM put in my phone was reverting systematically the recovery to its original one. The error was to reboot the system once I flashed the TWRP or the Lineage OS recovery.
What I did to install Lineage OS was to flash the recovery, disconnect the USB cable and remove the battery. Then boot directly into recovery. I backed up the current OS and installed lineage-17.1-20210110-nightly-h850-signed.zip. After reboot it works perfectly well.