This is for unrooted stock 2.11.605.19 Gingerbread users that cannot get the OTA to pull automatically and don't care if they have the new locked 1.08.0000 bootloader. You will need to go through the HTCDev bootloader unlock process which does wipe data. This guide also assumes you already have working ADB and fastboot installed and working on your computer (just search the forums if you don't.)
Get the files:
Download ota_mecha_ics_35_s_verizon_wwe_7.02.605.06-2.11.605.19_release_302982_signed.zip (Need mirrors please) (md5: 112230b7e4de0b0e982ce1d6d5) to adb/fastboot folder
Download tbolt_ics_manual_ota.zip (also attached) and extract to adb/fastboot folder
Steps:
1) Unlock bootloader at HTCDev
Follow the instructions there. Once your bootloader is unlocked, the phone will reboot into Android.
2) Turn the phone back off and reboot back into bootloader (from off, hold vol- when pressing power button)
3) Temporarily boot the phone with the unsecure boot.img you extracted to the adb folder:
Code:
C:\Android>fastboot boot mecha_605-19_unsecure_boot.img
downloading 'boot.img'... OKAY
booting... OKAY
4) Once Android starts, we need to push the OTA files and recovery command to the right directory:
Code:
C:\Android>adb remount
remount succeeded
C:\Android>adb push command /cache/recovery/command
2 KB/s (39 bytes in 0.015s)
C:\Android>adb push ota_mecha_ics_35_s_verizon_wwe_7.02.605.06-2.11.605.19_release_302982_signed.zip /cache/fumo/OTAPkg.zip
1319 KB/s (395637578 bytes in 292.765s)
5) Now we have the files where they need to go. Let's relock the bootloader so the OTA asserts pass:
Code:
C:\Android>adb reboot bootloader
C:\Android>fastboot oem lock
6) Using the volume keys, navigate to select recovery (select bootloader, then select recovery.) Once it reboots into recovery the OTA will start.
The first pass in recovery will check asserts, apply patches, then copy the FOTA skin and firmware.zip to
cache. If it looks like it hangs at the end, press vol+ and power to bring up the menu. The second reboot goes into bootloader with a skin over it. This flashes several image files including the new radio and
reboots again. It takes a while, give it time. This third reboot flashes recovery (short, just a minute or two) and the fourth reboots starts the phone normally with the new ICS updated Sense 3.5. It takes about 20 minutes from start to finish so make sure you have a full battery.
Post in the thread if you have questions BEFORE you start.
Reserved.
Just tried this out and it works.. Thanks kpetrie
only thing that you might want to update in your tutorial is that its the volume down button and power to get into the bootloader... not the vol up and power..
thanks again
Nexttonomy
Fixed, thank you for pointing that out.
Any idea if this would work for Rooted stock, with stock recovery in place and the revolutionary hboot? I rooted someone's phone with Trter10's tool, but it blocks OTAs, so I can't pull the ICS OTA, it doesn't even look for anything.
Yup, it does work. Needs Revolutionary hoot to keep from being overwritten as you stated. Proceed at your own risk and all.
Skip over the bootloader unlock and unsecure boot.img here and get the files in place however you want since you already have root. Copy and paste, adb push, dd the files - just do whatever you usually do to locations shown in the OP's adb commands.
Reboot to stock recovery and let it do it's thing. Then follow the remaining steps in my rooted stock thread from there to clean up and install superuser.
So, it did take a couple of tries, the first time it really and truly hung on the first trip through recovery, let it sit for over 30 minutes with nothing, no response to buttons or touches, had to battery pull and reboot. Second time started flashing, but trter10's tool removes a system file, which kept the flash from completing. Had to re-push the file, as well as the ota and command files, worked fine that time around.
Sent from my Sega Master System via Carrier Pigeon.
What file and can you post it as an attachment in case someone else comes across this?
I have a stock Thunderbolt off contract and I want to upgrade to ICS, What is the best way to do this?
Were you not able to check for the software update in settings and OTA normally?
I've upgraded to a new phone, so my Thunderbolt is no longer on contract and I can't download the OTA since it requires me to me on the Verizon network. The bootloader is locked with S-ON.
This would be how to do it then.
Ok, I wasn't sure If I could just put a .zip in the root of my SD card and it would flash like I've done in the past.
No, HTC made it so the command script is required. Can't just flash these like we used to.
Darn. I'll give your method a shot, thanks!
I'm getting a "no space left on device" message when trying to push the OTA zip.
How do i make some space?
Delete some apps or just factory reset.
Actually the bootloader unlock should have wiped it already... Try doing a factory reset and start back over with booting from the unsecure boot.img.
I am wondering i have 2.11.605.5 after a full reset in hopes to get the OTA. I don't want to wait and want to update now. How to I get to 2.11.605.19 so that I can update via this method you have posted?
You can flash the full RUU.
Sent from my Nexus 4 using Tapatalk 2
Can you elaborate more on this
I am stock rooted with revolutionary S-OFF with root. Can you break down the steps a bit more I willing to donate.
kpetrie77 said:
Yup, it does work. Needs Revolutionary hoot to keep from being overwritten as you stated. Proceed at your own risk and all.
Skip over the bootloader unlock and unsecure boot.img here and get the files in place however you want since you already have root. Copy and paste, adb push, dd the files - just do whatever you usually do to locations shown in the OP's adb commands.
Reboot to stock recovery and let it do it's thing. Then follow the remaining steps in my rooted stock thread from there to clean up and install superuser.
Click to expand...
Click to collapse
Related
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
SounderBruce said:
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
Click to expand...
Click to collapse
Ok! first download : http://www.4shared.com/zip/XG506hyV/icsroot-fastboot-recovey.html
just unpack, connect your device and click run.bat.....Good luck!
I ran the .bat, but I get an error saying "Device already rooted", but it is still not recognized as rooted by SuperUser.
Alternatively, is it possible to completely wipe the phone of everything (including root) so I can start over with a fresh phone?
Of course you can, and might be the best idea if you don't mind doing it.
Make sure you have the latest CWM recovery on your phone, download the FULL ROM from this thread (i'm not american so i don't know exactly, but from what i know yours is the I9020T, so get that ROM) and copy it to the SDCard. Now go into recovery, wipe system/data and dalvik cache, then flash the ROM.
Do make sure you have the right ROM though. This will get you 100% fresh and untouched 4.0.3. You can probably clear out any non-personal folders on the sdcard too, but that shouldn't do any harm anyway.
After this, use the attached file from this thread to root, and feel free to update root/superuser.
Actually, that's what I did...I can't use CWM recovery because its displaying an error of no root. So how do I wipe this or fix CWM?
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Harbb said:
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Click to expand...
Click to collapse
My bootloader is apparently unlocked and I'm trying to flash through fastboot.
Are you sure the following is satisfied:
-open padlock and google logo on boot
-fastboot (on phone) says "bootloader status: unlocked" or something of the like
-you are using: "fastboot flash recovery "C:\path\to\recovery.img""
-you are using the above command while connected to the PC via USB (with working drivers) and that you are in fastboot mode on the phone (turn off phone --> hold Vol. Up then hold Power TOGETHER for about 2 seconds, should give you reboot and recovery options)
It is necessary to be in the bootloader/fastboot interface on the phone when you run the command. Hopefully it was something simple that i said above, otherwise i'm completely lost.
1. Yes
2. Yes
3. I didn't use that method to root...
4. I'll try that.
3 is just flashing recovery, that is the code u type into cmd/terminal to reflash the recovery img. It isn't rooting the phone. 4 is how to get into the mode on the phone to use the command.
Its a bit confusing at first but makes much more sense once you do it one or two times.
Where do I go to get the recovery image?
The latest ClockWorkMod Recovery can be found on this page. Just scroll down to Nexus S and download 5.0.2.0 crespo .img. Then just direct fastboot to the folder you have it saved in while using the "fastboot flash recovery C:\path\to\recovery.img" command.
Ok. I've tried this, but in command prompt, I get the following error:
C:\Users\Bruce>fastboot flash recovery C:\Users\Bruce\Downloads\recovery.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Check out this rooting guide, however only go up to step 5 (and do NOT type "fastboot oem unlock", do everything up until that point). This will setup fastboot for you, and setup drivers for your computer. Once this is done, do what you did above and it should work successfully.
Remember to cd (change directory) in cmd to where you unzipped that folder.
There isn't a link...
Sorry, stuffed that up. I fixed the link in my previous post pointing to NexusSHacks - How to Root Nexus S.
It's worked, but when I try to go to the recovery menu, the Google/unlocked padlock screen freezes or it displays an Android with its chest compartment open and a red triangular ! symbol.
I just had a really long reply and managed to lose it by closing the page..
That's the stock bootloader you see there, it probably didnt flash or you rebooted your phone. And make sure that you are flashing the latest CWM you downloaded before.
I flashed the latest CWM, but when I try to go to recovery, my phone freezes at the Google logo with the unlocked padlock.
Have you tried flashing it again, or maybe redownloading the file? And of course making sure it is the NEXUS S version which you are downloading.
Alternatively, try just "fastboot boot recovery.img", replacing recovery.img with the full name and path of cwm.
edit: btw, i'll be gone for an hour or two Bruce so i can answer any more questions/issues when i get back
OK. So, I was going to root my wifes Mytouch slide 4g. I have rooted several phones in the past and never had an issue. I got i unlocked, I flashed clockwork, but I couldn't get s-off.
I used unrevoked, but it kept telling me it wouldn't work with the current software/update #.
I went to install CM9, everything seemed to go OK, then it wouldn't start.
Now, I have gone back to the stock images and they act like they are being applied in HBOOT....the status bar starts filling up, etc...but nothing happens. It doesn't ask if I want to apply the update, etc.
I have searched, and searched, and I am out of ideas. I really wanted to root this for her and put a decent ICS ROM on it, but at this point I would be happy simply getting the phone to come back on at all. Please help! Thanks.
When flashing CM9, did you flash the kernel separate since you couldn't get S-off?
No I didn't.
I actually tried flashing back to stock recovery and now cannot get clockwork back on there. If I remember correctly I can push it with ADB, right?
you push with (make sure you extract the boot.img from the rom and put in the same directory as your cmd windows) type:
Code:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
I'm stupid. That worked! THANKS!
no problem... also to flash cwm, DL this file and rename the file to recovery.img then put it in the same directory as your cmd window as before then type:
Code:
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot
(Method 1)
Ok so you're trying to put this really cool new custom ROM on your phone and then suddenly, your phone won't start up or go to recovery… well my friends, you have got yourself a bricked phone. The thing you worry about the entire time you're rooting, and flashing your phone, has now become reality. Well, fear no more, for I, have found a way to unbrick your device! after bricking my phone and finding different ways how to do it...
Because we are not able to swap or get the sdcard out from the phone, it makes it difficult on how to add a ROM.zip and re-install. Another issue I found is that CWM will not be able to read the sdcard if you do an adb push ROM.zip /sdcard/ROM.zip or by mounting the sdcard adb shell mount /sdcard . If you have this issue will explain later
So let's get started.
Step 1: Turning Off Your Phone and Reboot to Boot-Loader
Because you have a bricked phone, you can't just hold the power button. So if your phone is not already off then you're going to want to turn off by pressing the volume down + power button until the phone shuts off then turn on to boot-loader by pressing volume down and press for 3 seconds the power button. once in boot-loader select fastboot.
Step 2: Adb push to SD card
I assume that you have install CWM, if you don't you can download it from HERE. Once downloaded install CWM fastboot flash recovery CWM.TOUCH.5.8.3.1.img, where your done go back to boot-loader and select recovery. Once in recovery do an adb push of a ROM, in this example I used "Energy ROM" you can get the ROM from HERE. Once you have your ROM rename ROM.zip and push adb push ROM.zip /sdcard/ROM.zip, you will get a message stating the size of the the push.
If you can't do a push because you got an error message will explain later.
Step 3: Wipe The Phone
Make sure to do a Factory Reset / Wipe before installing ROM
Step 4: Reboot back to fastboot
Once you install the room you will need to make sure you have a boot.img for the ROM your using.
adb reboot bootloader
fastboot flash boot Recoveries/boot.img
YOUR DONE
If your the unlucky one's that can't do an adb push to the SD card do the following.
- Reinstall STOCK Recovery fastboot flash recovery recovery.img
- Lock OEM fastboot oem lock
- Unlock OEM fastboot flash unlocktoken Unlock/Unlock_code.bin
- Reinstall CWM Recovery fastboot flash recovery CWM.TOUCH.5.8.3.1.img
That should fix the problem on how to push back to the sdcard
If you have other methods post them below...
Sticky!!
But this won't work if you flash a wrong radio, will it? I thought that if you flashed a wrong radio, you couldn't get anything done, even not booting into bootloader, because it boots the radio first?
I'll second that this method works. Did for me and is easy to do once you take your time. Also make sure you have all the right files and you make sure to type everything word for word in ADB..
This tutorial already exists as a sticky in the Q&A section:
http://forum.xda-developers.com/showthread.php?t=1630459
Sent from my HTC VLE_U using Tapatalk 2
Nice writeup.
For every new Phone I own, the first thing I do after flashing a Custom Recovery is Making a Nandroid Backup of the stock Rom. If something goes wrong after flashing a bad rom I just restore to Stock rom.
A real life Saver for me.
snwman said:
I'll second that this method works. Did for me and is easy to do once you take your time. Also make sure you have all the right files and you make sure to type everything word for word in ADB..
Click to expand...
Click to collapse
It worked for me when I bricked my phone and had to find ways how to be able to load a ROM back to the SDcard and reflash it...
This is a combo of a tutorial cannondale wrote and one I wrote myself.
His is stickied in Q&A section, mine is in Android Dev section...
Not sure why this is here lol.
i get the error 155 when trying to install the RUU
420haxr said:
i get the error 155 when trying to install the RUU
Click to expand...
Click to collapse
Try to relock your bootloader first.
In fastboot:
fastboot oem lock
Sent from my HTC One S
Issue
Ok, still running into an issue. No errors when I push, I locked, unlocked, tried everything again. Reset everything, installed fresh CWM, tried it all over...
What's happening is that it's saying it pushed the file over, but I can't find it anywhere after it's done. This happened the first time I installed custom...I just can't remember what I did to get it to work...
Anyone has the link of stock recovery for HTC One S z560e(ville c2)?? i get error 155 when i try to install with RUU.
After i flash the cwm touch recovery I cant boot into recovery... my phone is stuck on the HTC boot logo with the red text underneath. Is it a problem with recovery or should i try install an RUU. My phone is HTC One S villec2 (S3).
Okay,
New sensation xe (Euro), CWM recovery, unlocked but not S-Off. Will only boot to HBOOT, Recovery, and its favorite, JuopunutBear. This thing will not go away. Happened when I tried the "Wire Hack". Phone boots to it unless I boot to HBOOT. Tried ....
Not ncessariliy in this order:
Wiping phone with 3 different wiping programs.
ControlBear.exe -r
Fastboot - most options
Flashing 2 different ROMs
Using Andriod Commander manually deleted every file and folder on the phone.
Others that i can't rememmber.
Two questions:
1. Is there somewhere on the file system that is totally hidden from wiping programs?
2. In the beginning, before I new what I was doing (1 week ago), I renamed a lot of files to update.zip. recovery.zip, PGxxIMG.IMG. Could I somehow be loading Juopunutbear back to the system when I reboot? If so, remedy?
Any help would really be appriciated, as I have spent days trying to work this out on my own.
Thanks!
JuopunutBear REMOVED FIXED
I got the same problem i check online and i was supposed to keep trying with the cable until it was successfull. I didnt wait that long and did exactly what you did, went to recovery and formated everything installed roms etc, none of which worked. Now as a result of all this JuopunntBear will definantly not work.
HERE IS HOW I FIXED AND GOT IT BACK UP AND RUNNING.
While trying the live CD method I downloaded a .zip file with contained the original unrooted Sprnint ROM and renamed it to PG86IMG.zip(~400mb) and placed it in the root directory of the SDCARD using CWM recovery card mount and went to fastboot menu which looked for this file and loaded the original sprint.
BEFORE YOU COPY THE FILE TO THE SD CARD YOU MUST RELOCK YOUR HBOOT you probably unlocked it while rooting the phone at some point. because if the hboot is UNLOCKED then the update will not extract and apply.
SO YOU MUST RELOCK BY: going to fast boot menu and sending the following relock command using command prompt in windows command prompt: fastboot oem lock
(this is similar to what is in the root instructions. google and find the files need to root the phone so that you can send the fastboot oem lock command (or anyother command in fastboot mode) to the phone using command prompt)(you can also use these to root the phone again once its up and running)
if in the process you cant get to the CWM recover etc you can use the command prompt and send unlock hboot and send" fastboot flash recovery xxxx.img " command to install the recovery console and access the SD card( root instructions and files http://htcevohacks.com/htc-evo-3d-hacks/how-to-root-evo-3d-2-08-651-2-and-later-htc-unlock-method/).
After this your phone will be just as if it was on the first day you got it.
HERE IS THE FILE I RENAMED AND LOADED. THERE ARE INSTRUCTIONS TO THIS
http://forum.xda-developers.com/showpost.php?p=24268786&postcount=209 <-- THIS IS THE FILE WHICH WILL FIX EVO3D CDMA FIRST FILE ON THE PAGE
http://forum.xda-developers.com/showthread.php?t=1563342 <--- i was following these
riptide355 said:
Okay,
New sensation xe (Euro), CWM recovery, unlocked but not S-Off. Will only boot to HBOOT, Recovery, and its favorite, JuopunutBear. This thing will not go away. Happened when I tried the "Wire Hack". Phone boots to it unless I boot to HBOOT. Tried ....
Not ncessariliy in this order:
Wiping phone with 3 different wiping programs.
ControlBear.exe -r
Fastboot - most options
Flashing 2 different ROMs
Using Andriod Commander manually deleted every file and folder on the phone.
Others that i can't rememmber.
Two questions:
1. Is there somewhere on the file system that is totally hidden from wiping programs?
2. In the beginning, before I new what I was doing (1 week ago), I renamed a lot of files to update.zip. recovery.zip, PGxxIMG.IMG. Could I somehow be loading Juopunutbear back to the system when I reboot? If so, remedy?
Any help would really be appriciated, as I have spent days trying to work this out on my own.
Thanks!
Click to expand...
Click to collapse
riptide355 said:
Okay,
New sensation xe (Euro), CWM recovery, unlocked but not S-Off. Will only boot to HBOOT, Recovery, and its favorite, JuopunutBear. This thing will not go away. Happened when I tried the "Wire Hack". Phone boots to it unless I boot to HBOOT. Tried ....
Not ncessariliy in this order:
Wiping phone with 3 different wiping programs.
ControlBear.exe -r
Fastboot - most options
Flashing 2 different ROMs
Using Andriod Commander manually deleted every file and folder on the phone.
Others that i can't rememmber.
Two questions:
1. Is there somewhere on the file system that is totally hidden from wiping programs?
2. In the beginning, before I new what I was doing (1 week ago), I renamed a lot of files to update.zip. recovery.zip, PGxxIMG.IMG. Could I somehow be loading Juopunutbear back to the system when I reboot? If so, remedy?
Any help would really be appriciated, as I have spent days trying to work this out on my own.
Thanks!
Click to expand...
Click to collapse
i had same problem, i took the sdcard out of my phone and put it in my moms galaxy note and formatted, then i put it back in my phone and started it up normally so i get pounutbear then i ran controlbear again on my computer and did the wire-trick right from then everything went as it should
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.