[HOW-TO] Safely Switch Back To Amon From Clockwork Recovery - Droid Eris Android Development

********************DISCLAIMER********************
XDA-Developers & Myself are in no way responsible for any loss of information or damages to your device that may result from from the use (or misuse) of this process, though the process itself should not cause any such problems I feel it necessary to reinforce this fact.
********************DISCLAIMER********************​
-----Special Thanks-----
jcase
-For the methodology and providing the flash_boot and recovery image links in his eng bootloader thread-
Stick from IRC
-For his sacrifice and bringing this issue to our attention (R.I.P. sticks Eris)-
Suno and Mezy (also IRC)
-For being unwitting guinea pigs and verifying the process-
--------------------​
Overview:
It has recently come to our attention that a version of clockwork recovery included in rom manager can and has (sorry stick) caused problems for Eris. Clockwork (or more specifically this clockwork) does not play nice with the Eris and in at least one case has resulted in a corrupted userdata partition resulting in a brick. This is not necessarily going to happen in all cases but the possibility is there and as such it is better to be safe than sorry. If you are using clockwork without issue but wish to switch back to Amon Ra this thread can also help you meet that end.
NOTE: Users who cannot use Amon RA recovery due to trackball issues should attempt the usb wiggle method. there is some sort of connection between the usb housing and the trackball down sensor that makes the trackball register a down movement when the usb gets rocked in a downward motion (extra note. be gentle)
What You Need:
Android SDK for adb - (alternatively this can be done PC-less but I will cover that later)
flash_image - www.multiupload.com/KS2JCAMGBH
recovery.img - www.multiupload.com/DXQVBXB93G
su - for root permissions
Astro or Root Explorer - (For PC-Less Only)
Terminal Emulator - (For PC-Less Only)
________________________________________________
This process is relatively straightforward and I'm going to cover both the adb method and the PC-Less method in case you for some reason can't get your device recognized by your system (or don't have access to one). I have also made this very detailed for inexperienced users.
The Process:
ADB Version-
1) Download both the flash_image & recovery.img files from the links above and place them in your android-sdk tools directory
2) Open a Command Prompt (or terminal) and navigate to the tools directory.
3) Connect your device (USB Debugging Must Be Enabled) and verify the PC can see the device - type:
Code:
adb devices
4) Push both flash_image & recovery.img to /data/local on your device:
Code:
adb push flash_image /data/local
adb push recovery.img /data/local
5) Change the permissions of flash_image:
Code:
adb shell chmod 777 /data/local/flash_image
6) Flash the recovery image to recovery:
Code:
adb shell
su /*this is for those who do not get dropped into a root shell automatically remember $ = user # = root */
/data/local/flash_image recovery /data/local/recovery.img
7) Give it a few seconds to run (just give it 10 or so seconds to be safe)
8) Issue the following to reboot the device into recovery mode to verify the flash took:
Code:
adb reboot recovery
PC-Less Version-
1) Download both files to your sdcard.
2) Use Astro or Root Explorer to move both of the files to /data/local (if you run into a read only error use this command in terminal emulator and try again)
NOTE: Root Explorer users can hit the rw/ro toggle button.
Code:
su
mount -o remount,rw /
If for what ever reason you either can't get Root Explorer and ASTRO is blocking you from navigating outside your SD go to terminal emulator and issue the commands:
Code:
su
mv /sdcard/download/flash_image /data/local
3) Open terminal emulator and issue this command to set permissions:
Code:
su
chmod 777 /data/local/flash_image
4) Still in terminal emulator flash the recovery image to recovery:
Code:
/data/local/flash_image recovery /data/local/recovery.img
5) When the prompt returns issue the command:
Code:
reboot recovery
Verification:
If you completed either method you should be greeted by a green text recovery menu. If so congrats Amon RA has blessed you with it's presence. go ahead and reboot system or flash a rom if you like.
If This was Helpful I only ask that you become an active member and contribute to the community in any way possible. The OpenSource community is what it is because of people like you giving freely of themselves for the benefit of the whole.

good stuff!
i've never used clockwork... and from my observations... GOOD!
in any case... this should help many users (i personally only recommend Amon).

What was the version the caused the issue? can't you also flash amons from clockwork in rom mgr then delete rom mgr? or would that not work? thank you.

midnight assassin said:
What was the version the caused the issue? can't you also flash amons for clockwork in rom mgr then delete rom mgr? or would that not work? thank you.
Click to expand...
Click to collapse
Not sure of the exact version as I don't personally use rom manager (kinda a manual guy) but I think it has been fixed in the most recent release. As for using Rom Manager to reflash I can't say for sure either but this method is pretty simple and already resolved two cases. I believe stick may have tried it he was in IRC with us for hours and we were bouncing everything we could think of at him but he got sig verification failure in a flash using it not knowing the issue and corrupted his userdata partition.
If there are any more questions I will have to answer them when I wake up because I'm nearly sleeping in my chair right now

thanks for the answer and putting this together. I know there are a lot of noobs like myself around here lately who may benefit from this and the time you put into it. thanks for makin it simple.

Thanks for the great post.
I just have to say theres an easier/alternate way to do it
1)download rom manager.
2)at the bottom of rom manager click flash alternate recovery.
[PC WAY]
As pointed out by bftb0 the below method will only work for those on HBOOT 1.49.2000 S-OFF bootloader. (those who flashed the original root rom)
1) download amon's recovery from this thread http://forum.xda-developers.com/showthread.php?t=648025
2) (if you don't already have the android sdk, download it) If your in Windows fastboot is included in the android sdk, if your in mac or linux go here http://developer.htc.com/adp.html and scroll down a bit, click download and move fastboot to your /sdk/tools folder.
3) with your phone connected to your computer and off hold the power and send buttons at the same time until fastboot comes up on the screen.
4) open cmd/terminal and cd to your /sdk/tools folder, and type in "adb flash recovery <path to amon's recovery>"(if your in linux or mac type ./ in front of fastboot).
5)reboot your phone.
I personally use clockwork recovery and have had no problems, though I do not suggest it for anyone. (unless your trackball is as messed up as mine is, I can't even scroll down in amon's recovery)

A couple of comments.
Stick's phone
A corrupted "userdata" (/data mount point) alone might prevent the OS from booting, but that should not effect the ability to start the phone in HBOOT, FASTBOOT, or RUU (oem-78) mode. I didn't sit in on the IRC, so maybe I'm missing something, but there really are only three things which will completely brick the phone:
- screwing up a flash of the (512 kB) bootloader
- screwing up the NVRAM area
- (maybe) screwing up the misc partition
You can screw the pooch in /boot, /recovery, /system, and /data (aka "userdata") - even all four of them at the same time, if you please - and your phone should still not be bricked.
If the bootloader can not be started (in any mode), then that is absolutely a bricked device; OTOH, if you can start up the bootloader in HBOOT mode, the only thing that would prevent you from re-flashing the Leak-V3/"Official" PB00IMG.ZIP file is corruption of either the /misc partition or NVRAM. None of the dev ROMs touch those areas though. So, it is very strange that someone using any custom recovery would cause corruption of those partitions. Is Stick really bricked?
I once corrupted my /system partition which caused it to be unmountable (in Amon_RA) by doing something dumb (twice!) - but re-flashing the entire ROM (HBOOT+PB00IMG.ZIP) overcame that and gave me an earlier starting point from which to re-root and recover via Nand. There is evidence, from looking at the string data contained within the bootloader that it knows how to recreate the partition tables in flash memory - presumably this would be needed if HTC shipped a ROM which needed more space in the /system or /data partitions than existed in prior ROMs. Whether it does that for normal PB00IMG.ZIP-style ROM flashing, I can't say - but there are hints that the HTC bootloader knows how to deal with flash memory in which the entire partition table has been destroyed.
PC-based method
Step #6 in the first set of instructions will not work for rooted (dev) ROMs which do not start adbd as root (that is, "adb shell" from the PC does not launch a root shell). Most dev ROMs do that, so perhaps this is a nit-picking point. If "su" is available in the ROM, prefixing the command with "su" should work, though - just as in the PC-less example.
Use of fastboot
homewmt should probably edit his post to add the disclaimer that using fastboot for flashing of recovery will only work for folks who gained root by flashing the "Root-ROM" (or post-installing it after root was gained), which gave them the 1.49.2000 S-OFF bootloader. None of the other bootloaders will let fastboot do this. I think it is important to mention this because a lot of the new rooters are using either the "One-Click" or "Dummies" (AF) methods to install a custom recovery - and so they never touch their bootloaders.
bftb0

So as long as you can get the boot loader up (power + volume down) then you can still use the 2.1 RUU (for those with HBoot s-on) to get the phone back working?
I think people assume that since the moded recovery image is fried that means the phone is bricked since you can't get into recovery on the phone to restore a backup.
Myself I've been using Clockwork Mod Recovery for 3 months without any problems and I've flashed a lot of ROMS and restored a lot of backups. Both using the recovery console and ROM Manager. I'll never go back to Amon's as I see no point and Koush is at least updating Clockwork on a regular basis.

bftb0 said:
A couple of comments.
Stick's phone
A corrupted "userdata" (/data mount point) alone might prevent the OS from booting, but that should not effect the ability to start the phone in HBOOT, FASTBOOT, or RUU (oem-78) mode. I didn't sit in on the IRC, so maybe I'm missing something, but there really are only three things which will completely brick the phone:
- screwing up a flash of the (512 kB) bootloader
- screwing up the NVRAM area
- (maybe) screwing up the misc partition
You can screw the pooch in /boot, /recovery, /system, and /data (aka "userdata") - even all four of them at the same time, if you please - and your phone should still not be bricked.
If the bootloader can not be started (in any mode), then that is absolutely a bricked device; OTOH, if you can start up the bootloader in HBOOT mode, the only thing that would prevent you from re-flashing the Leak-V3/"Official" PB00IMG.ZIP file is corruption of either the /misc partition or NVRAM. None of the dev ROMs touch those areas though. So, it is very strange that someone using any custom recovery would cause corruption of those partitions. Is Stick really bricked?
I once corrupted my /system partition which caused it to be unmountable (in Amon_RA) by doing something dumb (twice!) - but re-flashing the entire ROM (HBOOT+PB00IMG.ZIP) overcame that and gave me an earlier starting point from which to re-root and recover via Nand. There is evidence, from looking at the string data contained within the bootloader that it knows how to recreate the partition tables in flash memory - presumably this would be needed if HTC shipped a ROM which needed more space in the /system or /data partitions than existed in prior ROMs. Whether it does that for normal PB00IMG.ZIP-style ROM flashing, I can't say - but there are hints that the HTC bootloader knows how to deal with flash memory in which the entire partition table has been destroyed.
Click to expand...
Click to collapse
Yes stick is really bricked. He had access to the recovery but got a sig failure which terminally corrupted his userdata partition and the only option available to him was fastboot which would throw a sig failure at any attempt to flash over (even tried PB00IMG and RUU at the end)
NOTE: Good catch on #6 I edited the OP to drop into a shell then su in.
kzoodroid said:
So as long as you can get the boot loader up (power + volume down) then you can still use the 2.1 RUU (for those with HBoot s-on) to get the phone back working?
Click to expand...
Click to collapse
This is inadvisable as stick tried the RUU which is what killed off his ability to enter hboot

edge.thefly said:
Yes stick is really bricked. He had access to the recovery but got a sig failure which terminally corrupted his userdata partition and the only option available to him was fastboot which would throw a sig failure at any attempt to flash over (even tried PB00IMG and RUU at the end)
Click to expand...
Click to collapse
That is truly bizarre. I don't know what Clockwork does for checks, but Amon_RA performs (in the verification step) the equivalent of a "jarsigner --verify" operation: it computes the SHA1 hash of every last file in the .zip archive, and compares those sigs to the manifest. If even a single file is wrong, it won't proceed to the install, but just bombs out on a verification failure. The upshot of that is - in the Amon_RA (or stock recovery update.zip) case - it is literally impossible to install a corrupted ROM file.
In the case of HBOOT and PB00IMG.ZIP installs, a "whole-archive" signature is performed - the individual images are not inspected, but that doesn't matter: if you touch a single bit anywhere, even in the .zip file directory, that verification step will also fail.
So - in both of those examples, the only way to burn something wrong onto the phone is if the files get corrupted internally to the phone, after they have already passed signature checks - or if they are read off the SD card differently between the verification pass and the install pass!
Do you know if Stick has a S-OFF bootloader? (i have a tricky idea, if so) I suspect he doesn't, because if fastboot passes a privilege check, I don't think there are ever any sig checks performed by the phone when the bootloader is in FASTBOOT mode - all you have to do is have a S-OFF bootloader, and you can write total crap to the phone.
bftb0

I'm almost certain he had S-ON but hes not around right now so I can't verify.
I should also note that while he can still power on the device he only has fastboot access it wont even get into bootloader or recovery at this point.

thanks edge this work like a charm

edge.thefly said:
I'm almost certain he had S-ON but hes not around right now so I can't verify.
I should also note that while he can still power on the device he only has fastboot access it wont even get into bootloader or recovery at this point.
Click to expand...
Click to collapse
Ugh. Vol-Down won't get him from FASTBOOT-USB mode to HBOOT?
Sux.
I was going to suggest - only if he had the S-OFF (1.49.0000) bootloader - that he could boot to a recovery image without ever flashing it to the device, e.g.
Code:
[B]C:\blech> [COLOR=green]fastboot boot recovery-RA-eris-v1.6.2.img[/COLOR][/B]
Even if he had S-OFF, and can get a recovery boot up on it's legs, it might still be a long uphill climb if e2fsck/mke2fs can't repair/rebuild /dev/block/mtdblock5 (for instance if the mtd device is so corrupted that the partition map got thrashed).
But that route is a no-go if he has a S-ON bootloader.
bftb0

What's the difference between Amon and Clockwork?

Good question. I personally dont use clockwork but...
the navigation interface is different (uses volume keys to select instead of trackball)
Amon_RA is far more tested and reliable on Eris
and of course the general consensus that clockwork should NOT be used on the eris.
NOTE: I am sure there are other internal differences someone like bftb0 or koush would be more apt to give a detailed explanation.

edge.thefly said:
Good question. I personally dont use clockwork but...
the navigation interface is different (uses volume keys to select instead of trackball)
Amon_RA is far more tested and reliable on Eris
and of course the general consensus that clockwork should NOT be used on the eris.
NOTE: I am sure there are other internal differences someone like bftb0 or koush would be more apt to give a detailed explanation.
Click to expand...
Click to collapse
I've been using clockwork for a while now... I haven't had issues yet. What kind of problems have people had with this, anyway? There is an option in rom manager to flash back to Amon ra...
Sent from my Buuf Froyo using XDA App

The usual, failed flashes failed nandroid backups i heard something about a random reboot issue but that could be unrelated and of course the one case of corrupted partition/inability to get into hboot or recovery resulting in a brick.
I will note some people are using clockwork without issue and for them great but it is not advisable on the Eris at this time though I do realize some people have trackball issues and have to in which case best of luck to those few brave souls.
NOTE: If you have trackball issues i advise you to attempt the usb wiggle method. there is some sort of connection between the usb housing and the trackball down sensor that makes the trackball register a down movement when the usb gets rocked in a downward motion (extra note. be gentle)

edge.thefly said:
The usual, failed flashes failed nandroid backups i heard something about a random reboot issue but that could be unrelated and of course the one case of corrupted partition/inability to get into hboot or recovery resulting in a brick.
I will note some people are using clockwork without issue and for them great but it is not advisable on the Eris at this time though I do realize some people have trackball issues and have to in which case best of luck to those few brave souls.
NOTE: If you have trackball issues i advise you to attempt the usb wiggle method. there is some sort of connection between the usb housing and the trackball down sensor that makes the trackball register a down movement when the usb gets rocked in a downward motion (extra note. be gentle)
Click to expand...
Click to collapse
maybe you should post this on OP the trackball issue that is

so...I'm not at my normal computer(and I can't get Root Explorer because my card always screws up when it converts from US to any other currency) and am trying the On-Phone method via Astro. The issue I'm having is I cannot get it to show me the /data/local folder. I can't find any tweak for it in settings or anything. There's no read only error or anything like that, so I don't think that mount command in the first post will help very much. I'm fairly new to Android hacking, so this could easily be something I just don't know yet. My gut says it's a permissions thing, and that since Astro is meant for normal users it just doesn't set itself to show the restricted stuff by default.
So I guess does anyone know how to make this folder appear in Astro?
(I've been meaning to change back to Amon_Ra for a while ever since I noticed that RomManager deleted the other recovery program. Just can't trust something that does that.)
[edit] tried the command to remount as a rewritable et all that jazz(mount -o remount, rw /) and no change.

Do you have Superuser installed? My astro sees those extra files and it isnt in my Superuser permissions list.
However if you cant get past this issue go ahead and use the terminal emulator to perform the move.
Code:
su
mv /sdcard/download/flash_image /data/local

Related

Root Nexus One on a Mac/Linux/Windows

Hi guys. I published a step by step guide for all the newbies (I had a tough time the first time. Slightly different combination but it works! Also flashed the custom recovery image!
http://ilikemygooglephone.com/2010/...-and-root-google-nexus-one-mac-windows-linux/
This tutorial on rooting and flashing the RA recovery rom is THE BOMB!
Followed all the steps and now I too have gone to the dark side, and eaten some cookies....
Nice work.
Great! Love it!
This how I REroot Android in my N1.
Needs:
1) RA recovery image v2.0
2) fastboot
3) adb
1) Set to bootloader
Code:
adb reboot-bootloader
2) Boot RA-recovery 2.0
Code:
fastboot boot /path/to/recovery-RA-nexus-v2.0.0.img
Yes, it only boot the recovery image in memory.
2a) If you have RA already, then just boot the recovery
3) RA: Mount -> mount /system
4) Change permission /system/bin/su to 4755
Code:
adb shell 'chmod 4755 /system/bin/su'
5) Reboot, and enjoy your rooted Android.
Tested, on FRG83D, FRG83G and GRI40 stocks
Good luck.
Thank you.
Does it have to be 2.0.0? or can it be any of the RA recoveries above 2.0.0?
bahathir said:
This how I REroot Android in my N1.
Needs:
1) RA recovery image v2.0
2) fastboot
3) adb
1) Set to bootloader
Code:
adb reboot-bootloader
2) Boot RA-recovery 2.0
Code:
fastboot boot /path/to/recovery-RA-nexus-v2.0.0.img
Yes, it only boot the recovery image in memory.
2a) If you have RA already, then just boot the recovery
3) RA: Mount -> mount /system
4) Change permission /system/bin/su to 4755
Code:
adb shell 'chmod 4755 /system/bin/su'
5) Reboot, and enjoy your rooted Android.
Tested, on FRG83D, FRG83G and GRI40 stocks
Good luck.
Thank you.
Click to expand...
Click to collapse
A question for you, if it's possible to simply just change the permission of the su file on the phone, why do most auto root zip's come with an su file of their own?
Could they not just run the script above?
this whole procedure thing ... do stock users like myself lose anything? Like, does it wipe data or does it simply root and nothing at all changes?
You can never tell with these procedures... half wipe the phone...
I haven't tested it, but from the steps listed above (by bahathir) you won't lose any data.
All he's doing is getting you to boot into fastboot mode (power on the phone while pressing the trackball), and then loading the custom recover into temporary memory.
Then, the system folder is mounted and the required permissions are applied to the su file. Once that's done, you reboot your phone and nothing else changes.
The question that I had above though, is that I've not seen this method used before. Most one-click root methond replace the su file (requiring you to flash a zip file from custom recovery).
ahh too bad it doesn't work. maybe a 2.3.3 thing, but I just tried unlocking my bootloader and it says I'm missing AdbWinApi.dll from my PC ... but it's clearly there.
I have the most up-to-date Android SDK packages. I've used them before to root my nexus without a hitch...
SU should be present on the system, and the method above takes it for granted. Thus it's for RErooting. Rooting methods bring the SU - they don't care if there's one on the system, assuming that there isn't.
On the other hand, I'm completely unsure that "fastboot boot recovery.img" will work on custom image and locked bootloader. If it's the case - this is the most overlooked and bulletproof rooting method for Nexus. But I doubt it's the case.
Here's a n00b question. I have an unlocked boot loader and had previously rooted my phone using superoneclick. I wiped all the data before moving to stock gingerbread since I was on CM7 nightlies before. So there is no "su" in my phone. I get the obvious error:
c:\android-sdk-windows\platform-tools>adb shell 'chmod 4755 /system/bin/su'
/sbin/sh: chmod 4755 /system/bin/su: not found
when I try to run the steps listed here. Any ideas how to get the 'su' on my phone?
I guess you're executing "rerooting guide". Well, you can stop now, since there is no SU.
Flash it on your phone. That would be the obvious solution. Running unlocked bootloader and custom recovery, not really hard to do.
When you're doing things you don't fully understand, sometimes you go in extremely awkward ways to accomplish simple tasks. Having unlocked bootloader, why are you bothering with those guides? Reboot to fastboot, flash custom recovery, flash SU package in recovery, reboot. That would be all. Hard? not really.
Jack_R1 said:
I guess you're executing "rerooting guide". Well, you can stop now, since there is no SU.
Flash it on your phone. That would be the obvious solution. Running unlocked bootloader and custom recovery, not really hard to do.
When you're doing things you don't fully understand, sometimes you go in extremely awkward ways to accomplish simple tasks. Having unlocked bootloader, why are you bothering with those guides? Reboot to fastboot, flash custom recovery, flash SU package in recovery, reboot. That would be all. Hard? not really.
Click to expand...
Click to collapse
Thanks Jack! Can you point me to an su package that I can safely flash with gingerbread?
Sent from my Nexus One using XDA App
I found the package nexus-addon-0.1-signed.zip while searching for 'su' packages to root an unlocked nexus one on this guide http://forum.xda-developers.com/showthread.php?t=636795 . Will it be safe to flash this on a stock gingerbread?
aliezad said:
I found the package nexus-addon-0.1-signed.zip while searching for 'su' packages to root an unlocked nexus one on this guide http://forum.xda-developers.com/showthread.php?t=636795 . Will it be safe to flash this on a stock gingerbread?
Click to expand...
Click to collapse
I don't think that zip would work.
I rooted by applying the su.zip provide by dsixda here: http://forum.xda-developers.com/showthread.php?t=968396 (attachment, bottom of first post)
You would need to flash this from custom recovery (I used Amon RA 2+).
Thanks Brownbay! Worked like a charm!
Jack_R1 said:
...I'm completely unsure that "fastboot boot recovery.img" will work on custom image and locked bootloader.
Click to expand...
Click to collapse
Unfortunately this won't work on a locked bootloader (at least, not on mine!), so if you've used 'super one click' to root your N1 without unlocking it (like me), this method won't work for you.
I already have had my bootloader unlocked. I'm wondering if this rooting method alone will wipe my phone?
No, it won't wipe your phone.

[Tutorial] Restoring Recovery Mode while working only Fastboot Mode*ALL METHODS HERE*

Hello!
Yesterday I found myself in a very terrible situation. I spend about 6-7 hours...
It just happened that I deleted the recovery (through fastboot), and before that deleted firmware of the phone. That is, there remained only mode HBOOT (fastboot). Around the internet and google there are no guides on how to return
recovery by the alternative methods or how to flash a new ROM through
fastboot.
Thats why i want to present to you my little guide... Coz i think it will be very useful for some ppls like me with the same trouble.
So, if you're in a situation where you do not have Recovery, and the phone is not started in boot ROM then first try a standard way to flash a new Recovery through fastboot mode
Standart way of flashing new recovery via fastboot​
1.Connect your phone with PC via USB and power off your phone (if it up).
2.Than start up in fastboot mode - (in my situation, fastboot mode is CAMERA+POWER, then button "send") in all other (as i know) this is starting the phone while pressing button BACK.
3.Open -> Start->Run->cmd (open command prompt in windows*) and write:
Code:
fastboot devices
Than you must see your device serial number like this:
Code:
H94XTGAMSHDY
and should say "fastboot".
If all right - go next. If not - check fastboot mode (is on?) and USB cable.
4.Than change directory via cmd to where you have saved your recovery image (NEW recovery.img !!! ALWAYS CHECK MD5 SUM)
5. Than type this :
Code:
fastboot flash recovery recovery.img [enter]
(while you are stay in the same dir where you saved recovery.img)
(if you got some error about previously version or smth like this you can try to use this: fastboot erase recovery and only than try to flash new recovery from step №5)
6.Check your phone's display, as recovery is being sent and flashed to your device. And check your command prompt/shell to make sure the process is over.
7.Reboot into recovery by holding Home and Power (before it power off device).
Thats all! You can use any recovery, all what you like. I use Amon_RA's recovery.
IF WHILE FLASHING YOU GOT :
Code:
sending 'recovery' <4594kb>... OKAY [ 1.734s]
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verigy fail>
finished. total time: 3.125
Use next steps (my Alternative method)
And IF you can't flash recovery by this method it is not big trouble as you think now
Alternative way of BOOTING new recovery via fastboot​ checked and founded by me
Everything here is much easier and faster!
Do not be scared as I did it yesterday
Only what you need it :
Change directory via cmd to where you have saved your recovery image (NEW recovery.img !!! ALWAYS CHECK MD5 SUM)
And than TYPE:
Code:
fastboot boot recovery recovery.img
And your phone will be rebooted about 2 seconds in RECOVERY MODE. Yes!
After this you can use your old Nand Back up (restore it) and start up your old ROM. Or you can wipe all and try to flash new ROM and many operations what you can use via recovery. When you will get working ROM and flash it - you can flash recovery via adb. Or Use Rom Manager (Not recommended!)
Why we use this method? Because if you got error while flashing - FAILED <remote: signature verigy fail> you CAN'T FLASH ANY .img. Why? I Don't know, i hope some android guru's help us with it theory
(ALL AFTER THIS LINE ALL TEXT COPYED FROM WIKI.CYANOGEN.COM CREDITS GOES TO Cyanogen. Thx you, god)
If you want to flash recovery via adb (using power on phone with working firmware) (This method working 100% but strongly need working phone with working ROM)
Working only with HTC DREAM (G1) - Attention.
adb method by cyanogen version
Restoring the custom recovery image
Download the flash_image tool (HERE LINK
Next, place the file on your desktop
Change the directory to where "flash_image" is located, e.g. in Windows: cd C:\<path-to-flash_image-location>, in Linux: cd /home/USERNAME/path/to/flash_image on a Mac: cd /Users/USERNAME/path/to/flash_image)
IMPORTANT: Turn on USB debugging. Settings -> Applications -> Development -> check the box "USB Debugging"
Open up and adb shell
With your phone booted, type the following command
s:
Code:
adb root
This will start ADB as root, or notify if it is already running as root.
Code:
adb remount
This will mount the system partition (/system) as writable, allowing the following
Code:
adb push flash_image /system/bin
This will send the flash_image script into the /system/bin, so we can use it from within the shell
Code:
adb shell chmod 0755 /system/bin/flash_image
Finally, change the permissions of the script to allow it to perform the desired action.
Now that the script is installed, we are ready to proceed with flashing the custom recovery, saved on the root of the SD card earlier:
Code:
adb shell flash_image recovery /sdcard/recovery.img
P.S. If you want i can post here method by flashing original 1.6 ADP Rom via fastboot (but as i think it is on htc dev web... But i can post here cut version of this - coz original version have many not needed things.)
Credits:
Cyanogen
all xda cool ppls
ANtiHazarD
hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance
Nice steps! man hope this gets a good stick or added to the rom bible, you do know though fastboot method is a common way to flash recovery
ilostchild said:
Nice steps! man hope this gets a good stick or added to the rom bible, you do know though fastboot method is a common way to flash recovery
Click to expand...
Click to collapse
That's what I was thinking... Seems almost pointless for a guide since there's instructions how to fastboot on every recovery thread.
Either way, nicely written guide. Someone will probably find this useful.
pablo34 said:
hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance
Click to expand...
Click to collapse
With a desire this is quite different, as it has an activated nand flash protection (s-on), so no fastboot flash recovery here. Although this should prevent you from not having a recovery at all...
* note: I don't have a desire (yet) so this is speculation *
Best is probably something similar to this http://forum.xda-developers.com/showthread.php?t=750852
I guess if you get the correct PB99IMG.zip for exactly your device/brand you will not need a goldcard, so don't follow the howto blindly (it is for the newer SLCD versions, but the basics will still be applicable to AMOLED devices). Best would be a PB99IMG.zip that still has a hboot version < 0.92, otherwise you will need to downgrade to root. If you already have 0.92, then just take the newest image, as older ones are normally not flashable.
After step 7 of the howto, you are either done, or you will need to find instructions to downgrade if you want to root.
As soon as you have a working system, with a 0.8* hboot you can just use unrevoked to root and flash a custom recovery.
Enough OT... @ANtiHazarD: Very useful overview. Thanks.
WAY WAY WAY more complicated than it should be...
It is a simple matter of:
fastboot flash recovery recovery.img
Done.
lbcoder said:
It is a simple matter of:
fastboot flash recovery recovery.img
Done.
Click to expand...
Click to collapse
Its not quite that simple,
1) if eng spl use fastboot instructions from RA recovery post (fastboot flash recovery recovery.img)
2) if older stock spl with fastboot ruu modes (1.33.000*) where the * is
lbcoder said:
WAY WAY WAY more complicated than it should be...
It is a simple matter of:
fastboot flash recovery recovery.img
Done.
Click to expand...
Click to collapse
maybe so
but i want to post here ALL known methods thats why so much text is here
why? coz it was a trouble and the method with
fastboot flash recovery recovery.img
not working! thats why - all ways is here.
(all pre-info into 1st post in the top)
pablo34 said:
hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance
Click to expand...
Click to collapse
oh... i want to give to you some advice, but don't know what exact. because i don't have desire at my hands... and can't test.
so... thats why only - sorry
maybe there is some guide in the same way in desire section?
p.s. and thanks one more time to ezterry for old support
Can you please help me,
I have stuck here with the G1 phone,
it starts up and stucks on the G! logo.
I can get into fastboot bet have the same problem :
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verigy fail>
I get into fastboot with thre android logos on skates,
even tried to restore nandroid using fastboot but I get the same error? could you help me out?
I have HTC DREAM with 1.33.0013d and radio 2.22.27.08
I am really frustrated,
I tried all you gave up here but none worked for me.
Also when I try to get into recovery I see a G1 logo with a fastboot usb written on top left in red.
behzadbayat said:
Can you please help me,
I have stuck here with the G1 phone,
it starts up and stucks on the G! logo.
I can get into fastboot bet have the same problem :
writing 'recovery'... INFOsignature checking...
FAILED
I get into fastboot with thre android logos on skates,
even tried to restore nandroid using fastboot but I get the same error? could you help me out?
I have HTC DREAM with 1.33.0013d and radio 2.22.27.08
I am really frustrated,
I tried all you gave up here but none worked for me.
Click to expand...
Click to collapse
Did you read everything before you flashed the 1.33.0013d SPL?
If yes, you would have noticed, that this SPL is not able to flash a recovery or radio using fastboot. You have to flash the orange-...nbh file to get back a full engineering SPL, but you will loose everything you have installed on the phone ...
Send from my G1 with HTCClay's UNOFFICIAL Superfly 1.6 D/S ADS using XDA App
i don't know about this spl, but all what you can do (what i know) you can use this method which named in prev. post. with RC29 or RC7 stock firmware *.nbh
after flashing all data, radio, recovery will be reflashed by a stock data. All must be fine after this... i hope
ezterry can give for your advanced advice, may be
ANtiHazarD said:
i don't know about this spl, but all what you can do (what i know) you can use this method which named in prev. post. with RC29 or RC7 stock firmware *.nbh
after flashing all data, radio, recovery will be reflashed by a stock data. All must be fine after this... i hope
ezterry can give for your advanced advice, may be
Click to expand...
Click to collapse
Don't use RC29.. its once of the most annoying NBH files to need to re-root for the dream.
If you have 1.33.0013d note the orange.nbh posted on the new radio OP post: here
ezterry said:
If you find yourself stuck without recovery!!
Dream
1) Download: orange-1.58.73.2.nbh (MD5: aca4dee0c1ece7e9773f2ecbdfbba7c0) (mirror)
2) enter fastboot and run 'fastboot flash nbh orange-1.58.73.2.nbh'
3) wait for the entire nbh to flash
4) boot into the bootloader again (it will be an engineering SPL 1.42.2000)
5) You can now re-flash the radio/hboot/recovery via fastboot that you wish to have installed.
​
Click to expand...
Click to collapse
basically if you intend to still use the new radio; after installing 1.58.73.2 you can reboot-bootloader; and use my fastboot installation steps at the top of that post
You can do this without a goldcard because I bypass various checks in 1.33.0013d
(It will let you install any other signed NBH but that will still wipe the phone completely; and if it fails to flash cleanly it will leave you without an engineering SPL thus make it harder to make android go again)
hey i tried to flash the MTD too and now i keep getting "E:cant open CACHE:recovery/log" when i go into recovery . I can flash roms but when i reboot my phone my phone stays in the G1 Logo . and when it does make it to the rom i can not get my market or gapps no matter what i do . please help me guys .
EDIT: theres times when i get past the g1 logo but itll just stay on the roms boot screen forever until the phone dies . does anyone have any ideas ?
try to 'fastboot wipe system -w'
after
wipe all (data/cache, cache, dalvik, ext, stats)
and move log to sd
ANtiHazarD said:
try to 'fastboot wipe system -w'
after
wipe all (data/cache, cache, dalvik, ext, stats)
and move log to sd
Click to expand...
Click to collapse
ive never really done fastboot tho . is there any other way ?
breezy169 said:
ive never really done fastboot tho . is there any other way ?
Click to expand...
Click to collapse
It's worth learning to use it ...
Really, especially when using the 14MB-hack or CustomMTD and it's not so difficult. There should be a tutorial on adb and fastboot here in the forum.
AndDiSa said:
It's worth learning to use it ...
Really, especially when using the 14MB-hack or CustomMTD and it's not so difficult. There should be a tutorial on adb and fastboot here in the forum.
Click to expand...
Click to collapse
i agree but i just finished reading the forum that shows how to do it but it sounds so complicated .
EDIT: i ended up flashing another recovery and that solved the problem . that was the weirdest thinq ive ever seen . and honestly i thought i bricked my phone but it was a simpleee fix lol . thanks for the advice tho
I am hanging at booting while trying to do this any ideas?

[GUIDE]DZ Hboot on the G2 - Also: Update Recovery, Radio, and More Via Fastboot!

*note this thread started out to post some general findings, and it has turned into a tutorial on fastboot, scroll through the first few posts to understand more if this first post seems confusing*
So in the past i decided to play with some sense ROMs that requires the Desire Z Hboot. last time i did this i flashed the Virtuous Team's PC10IMG.ZIP through Hboot to do this.
Of course I then had to reflash my radio and recovery and ROM of choice. Later I switched back to my G2 Hboot and again flashed radio, recovery and ROM of choice.
Well why do we have to do all these steps? For fun I decided to look around and see if i could just flash the SPL through fastboot and couldn't find an answer, so i asked a friend and got this response:
I'm not sure if you can flash the Hboot through fastboot, I don't know if anyone has tried it before.
I know the PC10IMG will work, so fastboot should as well, but can't guarantee it.
Though I would recommend removing that radio from the PC10IMG before flashing it, as it does throw up issues later on if you ever want to flash a stock PC10IMG.​
Click to expand...
Click to collapse
Well it works just fine, download the DZ Hboot in the PC10IMG.ZIP format from anywhere you want (its all over XDA) and then extracted all from the .zip.
boot your phone into fastboot and open CMD into the folder the Hboot was extracted to (if you haven't edited the path for fastboot make sure fastboot.exe is in the same folder as the Hboot) in CMD type
Code:
fastboot devices
as long as you see your phone listed here proceed (displayed as the serial #)
Code:
fastboot flash hboot hboot_7230_0.82.0000_100902.nb0
You're done! Well almost...
Code:
fastboot reboot-bootloader
now your phone should say
HBOOT-0.84.2000 (PC1010000)
and you notice your radio hasn't changed
now boot into recovery, you'll noticed it is also still intact, well mostly you should see something like this:
ATTN: recovery is in safe mode
this is because the following partition
is not accessible: "system"
Please enter the wipe menu and format system!
If you changed Hboot you should choose to
format all partitions (except SD card)​
Click to expand...
Click to collapse
so of course go ahead and do this
you probably wont be able to boot normally as your partitions have now changed so flash a ROM now via recovery, reboot and your golden
*Hope this helps someone... HAPPY FLASHING!
EDIT:
Well I have seen this question a lot lately (or at least similar questions) so I decided to clarify some things here and TO ADD A LINK
this will download the DZ Hboot from the cyanogen wiki (this is only the Hboot, not a shipped ROM)
You will be downloading a .zip format, so extract the image from here
the image will be named
hboot-eng.img
Click to expand...
Click to collapse
(in windows file extension may be hidden, take note that is important)
so when flashing via fastboot make sure if you use this to type
Code:
fastboot flash hboot hboot-eng.img
again you can name the image what you want so long as in your command you specify the file name
eg: i name the image dzhboot.84.img i would then enter the command
Code:
fastboot flash hboot dzhboot.84.img
also note these same steps can be used to flash the G2 Hboot found HERE:
just need to change the name of the image or what your command is
If any of the above links are down i have uploaded both Hboots to MY DROPBOX
*Know what you are doing* I have made a couple different PC10IMG.zip's to be flashed through your SPL. they contain the .19 radio, the rcdata for that, 4ext touch recovery v1.0.0.5RC6, and an engineering HBoot for either the G2 or the DZ. I do not recommend this method as manually flashing will teach you what you are doing and can help ensure there are no issues. If you are true s-off but do not have an engineering SPL then you may use one of these: POST 30 IN THIS THREAD
Click to expand...
Click to collapse
*If you have more questions feel free to ask here as i am not the best with tutorials
Good to hear that your experiment went out well without incidents.
Sent from my HTC Vision using xda premium
How Do You Use Fastboot?
I should learn to stop assuming everything... i understand that not everyone has used fastboot or adb before and therefore may not know how, but on the same note neither is rocket science and even a novice can figure this out quickly. Instead of teaching people on a case by case basis i decide to add some helpful tips here, i will attempt to be through without being too boring.
what is fastboot?
fastboot is a protocol designed to flash unsigned partitions to android phones directly into the phones flash memory. if you are familiar with adb think of it in the same way. if youre not, just understand it is a tool designed to help flash images such as recoveries, bootloaders, kernels, etc. to your android phone. for the most part you can not use fastboot unless you are rooted and have an engineering spl (hboot/bootloader) this is not a tutorial to root your phone so i will not explain this. but everything you need to know is here
how do i get fastboot?
fastboot.exe can be downloaded to your computer from googles sdk found
HERE download the proper package depending on what system you are using.
also
you will need the proper DRIVERS unless you already have them then you can skip this
ok i got it, whats next?
after you downloaded the sdk package to your pc (for the purpose of this tutorial i will assume you are running window 7 but most everything is the same in other windows os, linux, and apple) it should be downloaded to your pc to somewhere like
C:\android\android-sdk-windows\platform-tools
Click to expand...
Click to collapse
of course put it where youd like, just know where fastboot.exe lies
although not necessary, but to make it easier i really suggest doing these steps:
left click the windows (start) button > right click on computer > choose properties > go to advanced system settings > advanced tab > environmental variables > in the first box (user variables for _____) click new > name it
adb
Click to expand...
Click to collapse
> the value is the path from earlier
C:\android\android-sdk-windows\platform-tools
Click to expand...
Click to collapse
(yours may differ from this so double check it!) > in the second box (system variables) find a variable named
path
Click to expand...
Click to collapse
if one dosent exist make one > double click on it > at the very end of the variable value add the same line as before but with a ; in front of it. like this:
;C:\android\android-sdk-windows\platform-tools
Click to expand...
Click to collapse
alright click ok and you are done!
why did i just do all that?
well this allows you to open a command line from anywhere on your computer without changing directories to use fastboot. pretty much we told your pc that when you type
fastboot
Click to expand...
Click to collapse
or
adb
Click to expand...
Click to collapse
into a command lined, where to find it. as you learn how useful fastboot and adb are this will help a lot.
so i still dont know what to do or how to do it!
all right lets start simple, click the windows button and in the search field type
cmd
Click to expand...
Click to collapse
you will notice a window pop up that looks suspiciously like dos. View attachment 1386065here you will see a blinking cursor after your directory, lets try this type
Code:
fastboot
a whole bunch of probably unfamiliar stuff should now pop up (for the most part this is a list of commands that can be used in fastboot) if you get something like
fastboot is not recognized as internal or external command operable program or batch file
Click to expand...
Click to collapse
then we need to troubleshoot, but for now i will assume it worked.
now try typing
Code:
fastboot devices
and nothing will happen, why? because there isnt a device attached. make sure you have android debugging turned on in your phone, plug it into your computer and boot into fastboot mode. on the g2/desireZ hold volume down while powering on, if needed choose fastboot (not all phone do this the same way so if you dont know how, ask and i can help) again try typing
Code:
fastboot devices
this time you should have a list of attached devices, this is displayed as the serial number to each. being many commands will "do" things to your phone try typing
Code:
fastboot reboot
if your phone is now back and running your existing os, congratulations! you now at least have fastboot set up and working properly. now lets try a few things out and see why this can be so helpful!
do you want a new recovery? maybe 4ext?
being this is in the vision (g2/dz) forum many have clockwork recovery but have read about 4ext recovery, only they just arent sure how to get it on their mobile.
here is a quick tutorial on how to do just this, and in my opinion the easiest and the safest way.
First
download a version of 4ext recovery for the vision HERE this will be downloaded to your computer in a .zip, i suggest to put it in a folder named 4ext recovery inside whatever folder you have all your android downloads (roms, kernels, etc)
now extract the image from the .zip you will notice it has the image and the md5sum, make sure it is
d92610abb990a78c3721d9e47e60fc13
Click to expand...
Click to collapse
if not DO NOT FLASH IT, unlike flashing a bad rom, it can be very harmful to flash bad firmware to your phone, although unlikely if flashed through fastboot, it could leave you without a working recovery or even worse, hard brick your phone. im not giving the scary warning that you see in most roms as what i am telling you is safe, im just reminding you to understand what you are doing.
i get it, im ready for 4ext!
all right, lets start by finding the folder the extracted recovery is in. hold shift > right click in that folder > choose open command window here. now you will see your command line with the directory already set to this folder. at this point, if you havent already, boot your phone into fastboot mode and have it plugged in via usb. now type
Code:
fastboot devices
so long as you see your serial # go on (if you dont fix the path in environmental variables explained in the last post or just make sure fastboot.exe is in the same folder as the recovery.img)
now lets continue, type
Code:
fastboot erase recovery
it is best to start fresh so even though you can skip this command i recommend it. lets move on:
Code:
fastboot flash recovery recovery.img
the recovery image you extracted from the .zip should have been named recovery the above command should be altered if you changed the name (notice: if using windows it may appear the image is only named recovery, that would be because windows is hiding the file extension, the true file name would then be recovery.img)
all right, if it said complete your done! seriously its that easy! now type
Code:
fastboot reboot-bootloader
from here you can boot into your new recovery and play around. if coming from clockwork to 4ext on the vision for the first time you will be wowed! this has so many more features, is far more stable, and is truly worth donating to madmaxx82 for all his hard work.
if you like this recovery and want the latest and or to donate (buying the app for 2bucks in the market is a very reasonable donation and gives you a great app too!) go HERE and you will also find tips on how to use the recovery as well as links to flash a free version of his .apk or a link to download the paid. even if you cant right now, i highly suggest doing so in the future as developers may give their hard work to us for free on xda but we should understand that just because something is free doesnt mean we shouldnt pay for it.
of course this method can be used for flashing different recoveries on different phones as well. just understand what you are doing and be sure to flash the proper recovery to the proper phone.
happy flashing!
So you need to flash a new radio...
turns out this doesnt even occur to many people as an option, that is to flash a different radio to their mobile. true, when i got my g1 this was the first time i realized this was an option, prior to that i had only dumbphones and did not even know too much how cellular phones in general worked. so to clarify i am not speaking about the fm radio in your car rather flashing the proper firmware to control your cellular radio.
Everyone keeps saying the .19 radio is the best, is that true?
well yes and no, what is true for them may not be true for you. it does appear most people using a g2 or a dz in this forum find the 12.62.60.27_26.13.04.19 radio the best in terms of reception and battery life. but it is good to know that this still has to be determined on a case by case basis. what is amazing for some may be lackluster for others.
so if you feel you need to try a new one the .19 is a good place to start, but you may need to test others and usually you will need to test it for a day or so to know how good it is in comparison. usually it is better not to estimate but rather compare using apps such as Speed Test and Network Signal Info and Battery Monitor etc. just use what works for you
So i can flash a new radio via fastboot?
Yes, and its my preferred method of doing so. its fast, easy and safe. heres how:
download the .19 radio and store it on your computer in a place you can find easy.
*checking the md5sum is a good idea before flashing a rom, and a must when flashing firmware:
6CB937DD21DC2A42DEBB66190F38370F
Click to expand...
Click to collapse
turn on debugging on your phone, put in fastboot mode and plugged into computer via usb. now open cmd in the same folder as fastboot.exe
now in cmd type:
Code:
fastboot flash radio radio.img
if you downloaded multiple radios then i suggest renaming them, in this case you may need to change radio.img to something like radio19.img or whatever you named it
now again in cmd type:
Code:
fastboot reboot-bootloader
you are now in hboot and can verify it worked, congratulations! it was that easy!
for a whole list of radios for the vision go HERE there will be two forms of each radio to download, make sure you download the images only if you want to flash through fastboot. you will also find more info about the radios there.
if you are interested in more then take look HERE FOR ICS and HERE FOR GINGERBREAD edkeys has done great work and its worth at least reading up on it. again if it aint broke dont fix it, but i will say it worked well for me.
*any questions and comments are appreciated, sometimes i go into too much detail and sometimes too little so feel free to ask and/or comment
Just a thing you might want to consider adding, I generally always 'fastboot erase recovery' before flashing a new recovery. I don't think it makes much difference, but it can't hurt.
-Nipqer
cleanleness is next to...
thanks, i do as well and just overlooked/skipped it in the tutorial
although im sure it wouldnt make much of a difference if someone just flashed a new recovery over the old, but it is always best to erase as this will lessen the chance of a bad flash due to residual effects from the previous recovery. this goes with most everything in flash memory as so many peoples problems with a newly flashed rom are simply due to them not completely wiping the phone clean.
so when flashing a rom i am a firm believer in performing
Code:
fastboot -w
prior to the flash, as it is cleaner than wiping from recovery and even cleaner than most superwipe scripts. of course not every time i flash a rom or restore a backup im next to a computer. in this situation i do recommend to wipe from recovery and then flash SuperWipeG2+ext4 from recovery prior to flashing the rom or restoring a backup. of course most of the time when people flash new roms they are at a computer, in this case i recommend these quick steps prior to the flash:
put phone in fastboot mode and attach to computer
Code:
fastboot devices
just to make sure we are ready (looking for serial # here)
Code:
fastboot erase system -w
fastboot erase boot
so fresh and so clean
Code:
fastboot reboot-bootloader
from here just reboot to recovery and flash the new rom there.
*note - you can flash a rom to your phone through fastboot but i will put that in the next tutorial*
flashing a rom with fastboot
As promised... here you go!
now of course you can flash a rom through recovery, but why not have another way? maybe your recovery partition on your phone is corrupt? maybe you just want to say "i learned something new!" whatever your reason here are the simple steps:
To start:
we need to download the rom of choice to your computer. once complete find the folder that rom is in and open cmd to that directory (quickest way just hold shift and right click within that folder > open command window here) of course make sure your phone is plugged into computer and in fastboot mode.
Lets see how quick and easy this really is...
in the command line type:
Code:
fastboot devices
see your serial number and we know all is good
now lets type these commands:
Code:
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
of course replace <superawesomerom.zip> with the correct file name
and last but not least:
Code:
fastboot reboot
*its been a little while since i did this but the phone might automatically reboot after flash so no need to run the reboot command
as your phone boots into the new rom, pat yourself on the back...
can i restore a nandroid through fastboot?
of course! (why you would need to is irrelevant)
and here are the simple steps how:
well first you need to make a nandroid back up (unfortunately fastboot cant make a nandroid for you :crying: ) put it some where on your computer. personally i only keep maybe 3 or so nandroids on my phones sd card as why waste space. i do however keep almost all my nandroids on my computer separated into diffrent folders for different phones. so my path to a nandroid backup would be something like:
android/htcg2/nandroids/<nameofnandroid>
Click to expand...
Click to collapse
and the obvious stuff:
have phone plugged into pc via usb and in fastboot mode, open cmd and change directories to that folder where your nandroid is in (or again just hold shift and right click > open command window here)
once we are in:
in cmd type:
Code:
fastboot devices
all is good when serial number is displayed, now type:
Code:
fastboot erase system -w
fastboot erase boot
*this isnt 100% neccessary but im a firm believer in wiping before any flash, even a backup
Code:
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
(of course change the image names if needed)
and you did it! :good: now you are almost a pro at using fastboot!
keep playing around, you'll get the hang of it and will quickly see that this is one of the best tools in the android sdk. it makes things much faster and easier and in many cases safer than the alternatives. any questions... feel free to ask!
Happy Flashing!
*as nipqer was so kind to point out, most newer recoveries archive nandroid backups in tar format by defult. this will not work with fastboot unfortunately.
for the restoring a nandroid, you gotta make sure the backups are done in yaffs2 format don't you? fastboot doesn't work with tar's as far as I know.
Clockworkmod 3.x and lower have the yaffs2 as default, but at least 5.x (and 4ext) use tar as default, but I know 4ext has a setting so you can change it.
-Nipqer
I believe you are correct. I haven't restored a nandroid via fastboot since the g1 days but that sounds about right. looking at my g2 nandroids some are in yaffs2 and some not, ill look into it and post a better explanation.
and it looks like every nandroid i made since i flashed 4ext recovery is saving everything as tars (except the boot and recover image) when i first rooted and used clockwork 3.x ? those backups were in yaffs2. it looks like one could change the settings in the 4ext app to change from tar archives to yaffs, but if all you are doing this for is to boot a backup from fastboot that is silly :silly:
so although it still is possible, it would not be worth the effort unless you were to do it for sheer fun. or if you still have an old android device lying around and want to try it out.
also if you updated to a new recovery and your old one used yaffs2 and the new one works with tar (i think twrp uses a modified tar/ext4 image called .win?) well you cant flash those old backups in your new recovery, but you can still flash them from fastboot. and then later do a nandroid with your new recovery in the proper format. so with this i guess there still may be a reason for someone to flash a nandroid via fastboot.
thanks for the heads up nipqer! id hate to make someone think they did something wrong when they didnt!
Sent from my HTC Vision using xda premium
Some other uses...
What else can i do with fastboot?
ADB has more (but different) capabilities than fastboot, but fastboot can still be handy. Heres an example: you went through the rooting process on your Vision a while back and cant recall if you sim unlocked it or if you gained super CID. well simple, lets:
open cmd, navagate to fastboot (no other folder/files necessary here) and type:
Code:
fastboot devices
and you should see your serial number, good
Code:
fastboot getvar cid
if you are sim unlocked and (superCID) then the output should read
cid: 11111111
Click to expand...
Click to collapse
if not, and you want it, then you will have to downgrade and rerun gfree etc. or you could beg tmobile for an unlock code or you can buy one from elsewhere. any way you go about it, this will tell you if it worked.
*super CID and sim unlock are not the same thing, i am just assuming if you have super CID then you also sim unlocked. (super CID lets you flash different software and firmware to your phone that initially may be locked to a specific carrier, sim unlocked allows you to use any GSM sim card no matter the carrier. although some require specific radio bands to fully work)
And more hypotheticals?
well to get your model id you would do the same only change the command to
Code:
fastboot getvar mid
out put will be something in the lines of
mid: PC1010000
Click to expand...
Click to collapse
there are reasons to change/fake your model id, maybe for apps in the market or to tweak a kernel... im not a developer so the purposes may be many or few on this.
Get a bunch of info quick:
Code:
fastboot getvar all
this give a slue of info such as radio, bootloader, imei, cid, secure flag (on/off) and more!
Speaking of kernels...
lets say you are a developer and have worked on a new kernel for your device, a quick and easy way to test it out may be to fastboot load the kernel:
Code:
fastboot erase boot
fastboot boot kernel ramdisk
*as always replace file/image names accordingly
after testing is completed:
Code:
fastboot flash:raw boot kernel ramdisk
fastboot reboot
test it out and see how things go! good luck!
as always, if you have questions or comments feel free to leave them here!
Happy Flashing!
*im thinking about adding a simple tutorial about ADB if anyone is interested let me know
If you flash from the g2 to the dz hboot thingie and have to reformat /system does it mean time to flash a new rom? And can you reflash a ext backup back since the partition info is different?
Yeah after updating to the dzhboot you will need to reformat, this will wipe your current Rom. But most often you should have no issue taking your nanadroid made while on the g2 hboot and restoring them to you phone with the new system partitions you get with the dzhboot.
As always make a backup of current set up via recovery, follow the steps listed in the first post and then flash either a new Rom or your nandroid. Also make sure to check the md5sums.
If you need any further help feel free to ask
Happy flashing!
Sent from my Desire Z using xda premium
Umm wow that was like super easy. Thanks for the guide. Going to have to read some about the radios and see about doing that next.....
no problem, many seem to either be afraid of using adb or fastboot mostly because they dont understand it and see other options to do the things they want (recovery)
but in reality both are quite easy to get used to and it really helps with the understanding of what you are doing. so im glad this guide is helping people not just get their phone the way they like it but also help understand the process.
as for the radio its just as simple as flashing the bootloader. mind you any time you flash firmware to your phone there is potential harm (unlike with flashing roms) so its not a great idea to just flash away for no reason. but fastboot is a very safe way of flashing firmware and as long as you check md5sums your good. also make sure never to do a battery pull during a flash or if something goes wrong just dont reboot until it is fixed, knowing these few things will ensure safe flashing through fastboot and help understand why firmware shouldnt be flashed through recovery.
so if you feel you could get better reception and/or battery life with a new radio by all means go for it! i for one found the .19 radio to be the best for me along with edkeys package. it seems many feel the same but the only way to know what works for you is to try it!
Happy Flashing!
I do agree it's not that hard once you have a clue. One thing I would say you may want to be a bit clearer on (at least me and my braindead self took a while to grasp it) is that you need to be in the bootloader to use the fastboot command. I am still learning about stuff and with the crazy hours I work and with 3 kids sometimes it takes me a while to get stuff done because I want to understand it before I do it. Although with your guide once I had time to sit down and do it it was like 15 mins tops and all was done. I need to read about the radio and edkeys(whatever that is...) and see about doing it. I think I have the .15 radio and it works ok although if I understand correctly wifi calling only works with the .19 radio and who knows it may fix my mms issues when I try ics roms.....
Thanks for the suggestion, ill add that in there, I always miss some little things! Edkeys is a member here on xda who did a lot of research on radios and WiFi calling, I linked a couple of his pages in my post on flashing the radio, I definitely suggest reading up on his work as he will explain it better than I. Also note some users have issue using WiFi calling and an old sim card, if you go to a local T-Mobile outlet they'll give you a free updated sim. I think the latest is 9177? Not sure but its written on the card.
Thanks for the suggestion!
Sent from my Desire Z using xda premium
demkantor said:
Thanks for the suggestion, ill add that in there, I always miss some little things! Edkeys is a member here on xda who did a lot of research on radios and WiFi calling, I linked a couple of his pages in my post on flashing the radio, I definitely suggest reading up on his work as he will explain it better than I. Also note some users have issue using WiFi calling and an old sim card, if you go to a local T-Mobile outlet they'll give you a free updated sim. I think the latest is 9177? Not sure but its written on the card.
Thanks for the suggestion!
Sent from my Desire Z using xda premium
Click to expand...
Click to collapse
C:\Users\Pesho\Desktop\recovery>fastboot devices
SH**SRT***** fastboot
C:\Users\Pesho\Desktop\recovery>fastboot erase recovery
erasing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.001s
C:\Users\Pesho\Desktop\recovery>fastboot reboot
rebooting...
finished. total time: 0.280s
C:\Users\Pesho\Desktop\recovery>
Click to expand...
Click to collapse
USB debugging is on.
I'm running Mimicry 1.5
root access is setted to apps and adb in the developer options in settings
what is your current bootloader information? can you write down the first few lines on the top of the screen?
Sent from my HTC Vision using xda premium

[Q] Bootloop on rebooting into recovery?

I rooted through cyanogenmod method, then unrooted (went back to stock 2.2.1) with the stock P15100.zip. I had another hardware issue with my phone (microphone failing) and thought it could be software. The mic was still broken and I wanted to root again so went through cyanogen method again flashing CWM. I was able to reboot once into recovery to flash synth's ICS. When I try to fully reboot, then reboot into recovery again, I got bootloop for a minute, then eventually booted into the rom. I tried flashing 4ext and same issue. I tried flashing CWM again from app and still have the issue. I'm just guessing recovery is corrupted and it needs to be formatted and re-flashed? Anyone know how to format recovery via adb and then push cwm or 4ext?
Any help much is appreciated.
You can flash a recovery through terminal emulator. As I recall, the commands are:
su
flash_image recovery recoveryname.img
Sounds like you might be having bigger issues, though. I hope your recovery partition isn't going kaput.
Jack_R1 might have an idea.
Man, Jack_R1 is still around these parts? But as for OP, definitely sounds like your recovery is corrupt. What you want to do is if you have any fastboot/ADB knowledge is you're going to want to download the recovery.img of your choice, name it "recovery.img" then place it in your ADB folder, plug your phone in in Fastboot mode and then type in the following commands:
Code:
Fastboot devices
it should show you a number followed by "fastboot" after this type
Code:
fastboot delete recovery
it should spew out how long it took followed by "recovery deleted" or something like that.
lastly you're going to flash the recovery that you downloaded. Type
Code:
fastboot flash recovery recovery.img
That should do it! PM me if you need any other help
Yes, I still visit here
OP, what phone do you have? You're writing a wrong name for PD15IMG.
In any case, if you indeed have PD15IMG - find "root for S-OFF users" thread in Development, get the PD15IMG with CWM from there, flash it just like you flashed return-to-stock package, and boot into recovery. If it doesn't work - it means that it's not the recovery that's corrupted.
And I suspect that you're just not understanding correctly what your phone does, and/or not actually booting into recovery.
Nicgraner said:
Man, Jack_R1 is still around these parts? But as for OP, definitely sounds like your recovery is corrupt. What you want to do is if you have any fastboot/ADB knowledge is you're going to want to download the recovery.img of your choice, name it "recovery.img" then place it in your ADB folder, plug your phone in in Fastboot mode and then type in the following commands:
Code:
Fastboot devices
it should show you a number followed by "fastboot" after this type
Code:
fastboot delete recovery
it should spew out how long it took followed by "recovery deleted" or something like that.
lastly you're going to flash the recovery that you downloaded. Type
Code:
fastboot flash recovery recovery.img
That should do it! PM me if you need any other help
Click to expand...
Click to collapse
I have used adb a bit (for root with cyanogen method). I'm guessing that the delete command will reformat the recovery partition? I'll give this a go when I get home and get back to ya. Thanks for the reply! Is there a way to download the 4ext recovery img file?
Edit:
I downloaded the CWM touch img and connected to the phone in fastboot. Was able to follow your instructions, but the command is erase not delete. When I put in the delete command it came up with the instructions and was able to figure it out. Flashed recovery and I can now boot into recovery every time from fastboot, terminal, adb, and from power prompt in rom! BOOYAH! Thanks a ton!
Jack_R1 said:
Yes, I still visit here
OP, what phone do you have? You're writing a wrong name for PD15IMG.
In any case, if you indeed have PD15IMG - find "root for S-OFF users" thread in Development, get the PD15IMG with CWM from there, flash it just like you flashed return-to-stock package, and boot into recovery. If it doesn't work - it means that it's not the recovery that's corrupted.
And I suspect that you're just not understanding correctly what your phone does, and/or not actually booting into recovery.
Click to expand...
Click to collapse
Hey Jack,
I have HTC Glacier. Was a typo for the PD15IMG name. I think I have a decent understanding of the phone, and most likely have a corrupted recovery partition. Seems that instead of just flashing a recovery over a recovery, I may need to reformat the partition and then flash? I'll try flashing the file you suggest and report back. If it is not the recovery that is corrupted, what else could be the issue? Possibly an issue with the bootloader not allowing the phone to boot into recovery? Thanks for the reply.
Flashing recovery isn't copying a file. When you flash IMG through bootloader, it is flashed just like what it is - a complete image. Formatting the partition doesn't do anything, since it has no "format" - the image flashed by the bootloader contains both the structure and the data, just like a CD/DVD image does, for example.
The possible options I can think of are:
1) Your recovery partition is physically bad - unlikely.
2) Your bootloader is corrupted - could possibly lead to you being unable to enter recovery.
3) Something that prevents your phone from entering recovery - i.e. a stuck button or something - or you're doing it wrong. I'm afraid that what you're describing as "phone bootloops for a minute and then boots a ROM" isn't really a bootloop - because these phones can't get out of bootloop on their own, if booting failed once - it'll fail always. Logcat can confirm this. I believe it's just the ROM that's booting normally when you try to enter recovery, so, in this case, since you didn't specify how exactly you're trying to enter recovery - it seems like you're either doing it wrong, or when you try to enter recovery you're not getting there.
To help people help you, please write down the exact way you're using when trying to enter recovery, and if you know more than one way - try them all (from bootloader, by adb reboot recovery, directly booting without flashing by "fastboot boot", etc). And post your HBOOT version.
Jack_R1 said:
Flashing recovery isn't copying a file. When you flash IMG through bootloader, it is flashed just like what it is - a complete image. Formatting the partition doesn't do anything, since it has no "format" - the image flashed by the bootloader contains both the structure and the data, just like a CD/DVD image does, for example.
The possible options I can think of are:
1) Your recovery partition is physically bad - unlikely.
2) Your bootloader is corrupted - could possibly lead to you being unable to enter recovery.
3) Something that prevents your phone from entering recovery - i.e. a stuck button or something - or you're doing it wrong. I'm afraid that what you're describing as "phone bootloops for a minute and then boots a ROM" isn't really a bootloop - because these phones can't get out of bootloop on their own, if booting failed once - it'll fail always. Logcat can confirm this. I believe it's just the ROM that's booting normally when you try to enter recovery, so, in this case, since you didn't specify how exactly you're trying to enter recovery - it seems like you're either doing it wrong, or when you try to enter recovery you're not getting there.
To help people help you, please write down the exact way you're using when trying to enter recovery, and if you know more than one way - try them all (from bootloader, by adb reboot recovery, directly booting without flashing by "fastboot boot", etc). And post your HBOOT version.
Click to expand...
Click to collapse
Sorry if I wasn't more descriptive. I really appreciate your help and everything you have done for this community. Seems the recovery was corrupted by the 4ext app. I was able to extract the recovery.img from the 4ext download and was able to flash it via fastboot. Everything boots properly now. HBoot is 0.85.2007 FYI. Thanks again!

How to unroot the latest RUU (5.07) [GUIDE]

Here is a quick guide on how to unroot the latest RUU 5.07. It seems that quite a few people are having trouble unrooting their device or running an official RUU while being on the latest update, or a ROM based on the latest update.
The problem is that HTC has fixed the bootloader (in particular Hboot 2.18) so that it will reject any PC36IMG.zip official software or RUU files that update previous operating systems on the phone (a S-ON phone). You would usually need a RUU (I'm calling both the PC3IMG.zip file and the RUU file an RUU) that is for your current operating system. If your phone is on the latest 5.07 update or a ROM that is based on the 5.07 update, then latest RUU that exist is for the Evo with RUU Supersonic 4.67. 5.07 never came out, done intentionally by HTC I believe. So none of the RUUs which exist today will work with the 5.07 update. The problem exist because the phone's misc partition is updated whenever you accept an update or run a RUU from HTC, or even flash a ROM. There are other cases as well. The only way to run an official RUU on a phone that is not currently S-OFF is either to downgrade the phone's misc partition, or to turn the phone S-OFF (which you will still have to flash the phone's misc partition to do).
What I've done is put together a quick guide for those who need (or just insist) on unrooting their Evo. It is brief and only for a PC (not a Mac). Hopefully, someone in the future can provide further details or make it Mac friendly or even more user friendly because I don't have a Mac, nor the time to spend to make this guide perfect. I have another phone too to deal with. Remember too, that everything is done at your own risk. So if something goes wrong, well you knew the risks.
For this guide I'm going to assume that you are on Hboot 2.18, the phone is S-ON, the bootloader is unlocked (UNLOCKED), and that the phone's ROM is currently rooted. If not, then this is not the right guide for you.
1. Download this zip file. It contains the necessary files that you will need.
https://dl.dropbox.com/u/38127313/sdk.zip
2. Plug your phone into your computer. Then go to Settings/Applications and uncheck Fastboot. Then goto Development and make sure that USB debugging is now checked. If you have a custom ROM, then the locations of these settings may be slightly different.
If you need the HTC drivers, then I have also included the drivers.exe file that you must run from your computer to install the "MyHtc" drivers that you must have under the computer's device manager when the phone is plug in.
3. Next, unzip the file to a folder, preferably sdk. Rename the "PC36IMG_SuperSonic_GB_Sprint_WWE_4.54.651.1_Radio_2.15.00.0808_NV_2.15_release_220182_signed" file to PC36IMG.zip (not PC36IMG.zip.zip). Place the phone into "Disk drive, then copy the PC36IMG.zip file to your sdcard. Afterwards, don't forget to change the phone back to "Charge only".
4. Next you will need to open a command prompt at the folder where you extracted the files. If you are not familiar or uncomfortable with adb commands, then I cannot help you here.
5. Type or copy the below commands exactly as they appear.
adb push flash_image /data/local <ENTER>
(This places the file on your phone in the /data/local directory).
adb push mtd-eng.img /data/local <ENTER>
(This places the file on your phone in the /data/local directory).
adb shell <ENTER>
(You should see either a dollar sign ($) or a pound sign (#) at your prompt, depending on your ROM. If you do not then something went wrong. And, No the phone will not brick if you should stop at this point).
su <ENTER>
(You might not need this command depending on your ROM, and also you should check to see if your phone is asking for superuser permissions. If everything went Ok, you should now see a pound (#) sign at your prompt. If you do not then something went wrong. And, No the phone will not brick if you should stop at this point).
cd /data/local <ENTER>
(You need to be in the directory where you put the flash_image and mtd-eng.img files).
chmod 755 flash_image <ENTER>
(flash_image needs to be assigned permissions).
./flash_image misc mtd-eng.img <ENTER>
(This is the most critical step here).
reboot bootloader <ENTER>
(I prefer this step, as it is much faster than pulling the battery and all that other stuff that people suggest).
The phone should now reboot directly into the bootloader. Also the phone will now be locked again (LOCKED OWW) regardless of its previous state. Next hit the power button. It will then take some time to read the PC36IMG.zip file. If everything went Ok, then it should ask you whether or not you want to accept the update, which means that your misc partition was successfully downgraded, and now you can successfully run the RUU.
EDIT: I have to re-upload the sdk.zip file, because the original one had a problem with the PC36IMG.zip file. It should be available shortly. The one I added does work this time; however, the phone may have to be updated in order to bring it back to the latest bootloader and update. It's not the latest RUU 4.67, but the second latest 4.54. I cannot believe that something was wrong with that file. Also, instead of the PC36IMG.zip file that I added, you could also use any other PC36IMG.zip file or a RUU.exe file from HTC. They should work as well. I would not recommend a RUU below Supersonic 3.70. I'm going to upload some of these as well when I get a chance. I have like all of them.
Re: How to unroot the latest RUU (5.07)
You should put "[GUIDE]" in the title, right now it seems like a question
Just a thought anyway.
Sent from my PG06100 using xda premium
CNexus said:
You should put "[GUIDE]" in the title, right now it seems like a question
Just a thought anyway.
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
Thanks for the advice. I'm currently re-uploading the sdk.zip file. Something went wrong with the PC36IMG file. It should be available again in a little while.
I wonder if you can help me?
I have a problem with an Evo I got from someone, it mostly gets stuck in a bootloop but sometimes it actually boots all the way up. As your guide mentioned, I'm not able to RUU because its on the 5.0.7. I think the phone was rooted because it had a few .apk's that require root including su.apk. I did a factory reset while the phone was on a sprint account but it didn't fix the issue........ long story short, I noticed the bootlooping stopped when she got off the phone, so I figured the bootloop was caused by the data running through it or something. Today I turned the phone on and fooled around with it for about an hour before I decided to put it on my pageplus account because my verizon droid razr was stolen yesterday, as soon as I did the esn swap with the pageplus rep the phone started the bootlooping again. So I came across your post and luckily got the phone to boot up and began following your guide...... when i got to the "su" I didn't get "#" sign and permission was denied. I noticed the su.apk was not in the app draw so I downloaded it, I also installed root explorer to see if I get root access, no luck. Since then I can't get the Evo to boot up..... So finally my question, is it possible to execute your guide in fastboot or is there a way to push su through fastboot via adb?
---------- Post added at 09:12 PM ---------- Previous post was at 09:05 PM ----------
6foot5nbad said:
I have a problem with an Evo I got from someone, it mostly gets stuck in a bootloop but sometimes it actually boots all the way up. As your guide mentioned, I'm not able to RUU because its on the 5.0.7. I think the phone was rooted because it had a few .apk's that require root including su.apk. I did a factory reset while the phone was on a sprint account but it didn't fix the issue........ long story short, I noticed the bootlooping stopped when she got off the phone, so I figured the bootloop was caused by the data running through it or something. Today I turned the phone on and fooled around with it for about an hour before I decided to put it on my pageplus account because my verizon droid razr was stolen yesterday, as soon as I did the esn swap with the pageplus rep the phone started the bootlooping again. So I came across your post and luckily got the phone to boot up and began following your guide...... when i got to the "su" I didn't get "#" sign and permission was denied. I noticed the su.apk was not in the app draw so I downloaded it, I also installed root explorer to see if I get root access, no luck. Since then I can't get the Evo to boot up..... So finally my question, is it possible to execute your guide in fastboot or is there a way to push su through fastboot via adb?
Click to expand...
Click to collapse
BTW, Bootloader is still unlocked
If bootloader is unlocked, flash a recovery through fastboot
Code:
fastboot flash recovery path/to/RECOVERY_NAME_HERE
Most likely RECOVERY_NAME will end with ".img" so the command would be like this:
Code:
fastboot flash recovery /path/to/recovery-evo.img
After that, search google for a "zip" file named "su-signed-efghi.zip", look for a hit on goo.im (search "evo 4g su-signed-efghi.zip") and download and place it on your sdcard
Boot into recovery (VolDown + Power, then user volume keys to navigate and power key to select recovery)
Then choose "flash zip" and locate the "su-signed-efghi.zip" file and flash it
You should now have the su binary installed in the correct place
Sent from my PG06100
CNexus said:
If bootloader is unlocked, flash a recovery through fastboot
Code:
fastboot flash recovery path/to/RECOVERY_NAME_HERE
Most likely RECOVERY_NAME will end with ".img" so the command would be like this:
Code:
fastboot flash recovery / path/to/recovery-evo.img
After that, search google for a "zip" file named "su-signed-efghi.zip", look for a hit on goo.im (search "evo 4g su-signed-efghi.zip") and download and place it on your sdcard
Boot into recovery (VolDown + Power, then user volume keys to navigate and power key to select recovery)
Then choose "flash zip" and locate the "su-signed-efghi.zip" file and flash it
You should now have the su binary installed in the correct place
Sent from my PG06100
Click to expand...
Click to collapse
Thanks for your quick response. Been trying that but its been going into a bootloop after I select recovery from hboot. Can't boot into recovery at all I was thinking about using adb to flash a stock recovery but all the recovery.img's i come across.... seem to be for an older hboot and/or system. Also I don't want to attempt anything that will make things worse. I've rooted dozens of Evo's on hboot 2.18 and I have a good Idea of how adb works. I'm wondering if that if I can manage to get S-Off will the phone be able to take an RUU then? or is there anyway to push a older flash_image to trick RUU into updating? I guess the question I should ask is what would you do if your evo would barely boot normally and couldn't get into recovery? the only thing that does work consistently is Hboot and I can't launch recovery through adb nor hboot.
update
6foot5nbad said:
Thanks for your quick response. Been trying that but its been going into a bootloop after I select recovery from hboot. Can't boot into recovery at all I was thinking about using adb to flash a stock recovery but all the recovery.img's i come across.... seem to be for an older hboot and/or system. Also I don't want to attempt anything that will make things worse. I've rooted dozens of Evo's on hboot 2.18 and I have a good Idea of how adb works. I'm wondering if that if I can manage to get S-Off will the phone be able to take an RUU then? or is there anyway to push a older flash_image to trick RUU into updating? I guess the question I should ask is what would you do if your evo would barely boot normally and couldn't get into recovery? the only thing that does work consistently is Hboot and I can't launch recovery through adb nor hboot.
Click to expand...
Click to collapse
I found and exploit on TacoRoot that will get me temp root access without booting into recovery as long as I had an recovery log in /data/data/recovery/log (stock preferably). So I would greatly appreciate if someone can post the file here. I want to attempt to use the exploit to get temp root access then use this guide to get to the point where i can use an RUU.
---------- Post added at 01:22 AM ---------- Previous post was at 01:11 AM ----------
6foot5nbad said:
I found and exploit on TacoRoot that will get me temp root access without booting into recovery as long as I had an recovery log in /data/data/recovery/log (stock preferably). So I would greatly appreciate if someone can post the file here. I want to attempt to use the exploit to get temp root access then use this guide to get to the point where i can use an RUU.
Click to expand...
Click to collapse
Also, I would need help on how to push the recovery log file to /data/data/recovery/log if possible or would it simply be adb push log /data/data/recovery/ ?
An RUU would only work if you had a lower or equal version on your phone than the RUU
As for your actual issue....you cant use adb while its in the bootloader, phone has to be fully booted if you want to do anything with adb
The only thing you can do while in hboot is to use fastboot
Try running:
Code:
fastboot reboot recovery
And see if that gets you into recovery
Sent from my PG06100
CNexus said:
An RUU would only work if you had a lower or equal version on your phone than the RUU
As for your actual issue....you cant use adb while its in the bootloader, phone has to be fully booted if you want to do anything with adb
The only thing you can do while in hboot is to use fastboot
Try running:
Code:
fastboot reboot recovery
And see if that gets you into recovery
Sent from my PG06100
Click to expand...
Click to collapse
Yes, I've tried -fastboot reboot recovery- in fastboot, just goes into a boot loop....... I did get the phone to stay booted overnight, I think as long as the battery is fully charged it stays on, and I can use adb now. The main issue now is that I can't boot into recovery therefore, like I mentioned it just goes into a bootloop and the battery discharges if I let the phone bootloop while trying to boot into recovery. Also, I noticed that the phone won't boot normally unless I have a full charge (Green Light). I think I just need the recovery log file, my thinking is if I can put the log file in the the correct location I can trick the phone into thinking it booted into recovery. If I can get temp root access then I use this guide to relock the bootloader and be able to use an RUU. Do you think that's possible?
---------- Post added at 12:24 PM ---------- Previous post was at 11:59 AM ----------
6foot5nbad said:
Yes, I've tried -fastboot reboot recovery- in fastboot, just goes into a boot loop....... I did get the phone to stay booted overnight, I think as long as the battery is fully charged it stays on, and I can use adb now. The main issue now is that I can't boot into recovery therefore, like I mentioned it just goes into a bootloop and the battery discharges if I let the phone bootloop while trying to boot into recovery. Also, I noticed that the phone won't boot normally unless I have a full charge (Green Light). I think I just need the recovery log file, my thinking is if I can put the log file in the the correct location I can trick the phone into thinking it booted into recovery. If I can get temp root access then I use this guide to relock the bootloader and be able to use an RUU. Do you think that's possible?
Click to expand...
Click to collapse
I forgot to mention, the TacoRoot Exploit requires the recovery log file (http://rootzwiki.com/topic/13713-tacoroot-htc-universal-root-exploit-12-30-2011/) to be in /data/data/recovery/ directory, so it requires a user to boot into recovery to create the log file, and I can't boot into recovery.... so my idea is to push the recovery log file to /data/data/recovery/log cause thats where the exploit is looking for the log file. I'm hoping that will prevent me from having to boot into recovery which is where I'm getting stuck on the tacoroot exploit. With shortydoggs guide, I'm getting stuck at the "su" command cause the evo (for some reason) isn't rooted anymore. So my plan is to get me temp root with TacoRoot so I can get "#" and continue with shortydoggs guide. Not sure if that's possible but at this point its my only option since I can't get into recovery to flash su.zip nor can I RUU cause I'm on 5.0.7 which has no RUU.
I can give you the file, but it's hard to get it to work without that recovery. You have to extract out of the zip file and then push it to the /data/data/recovery directory. I tried it myself and I can adb push it, but when doing the tacoroot --root, I get an error "/data/local/tacoroot.sh: cannot create /data/local.prop: permission denied".
EDIT: I uploaded the two files that you need. You need to unzip the two files. Then push the log file to the /data/data/recovery directory, and the local.prop file to the /data/ directory. Getting them there will be up to you, as I'm not the most Linux educated person out there. I'm only able to push the files because my phone is already rooted. Hopefully you figure it out or someone more familiar with Linux (adb) commands can help you. Then, the "adb shell /data/local/tacoroot.sh --root" command is a breeze.
Code:
adb push tacoroot.sh /data/local/tacoroot.sh
adb shell chmod /data/local/tacoroot.sh
adb shell sh /data/local/tacoroot.sh --setup
#should give an error after line above, its fine because you're pushing the local.prop yourself
adb push local.prop /data/local.prop
adb shell sh /data/local/tacoroot.sh --root
If anything goes wrong or it doesnt work, run this to revert
Code:
adb shell sh /data/local/tacoroot.sh --undo
I would've posted the tacoroot.sh for you since I use it in my shift utility to root your phone, but I wasn't sure if it was universal for all HTC devices or just for the evo shift. Sorry about that.
Sent from my PG06100
Thanks!!!
shortydoggg said:
I can give you the file, but it's hard to get it to work without that recovery. You have to extract out of the zip file and then push it to the /data/data/recovery directory. I tried it myself and I can adb push it, but when doing the tacoroot --root, I get an error "/data/local/tacoroot.sh: cannot create /data/local.prop: permission denied".
EDIT: I uploaded the two files that you need. You need to unzip the two files. Then push the log file to the /data/data/recovery directory, and the local.prop file to the /data/ directory. Getting them there will be up to you, as I'm not the most Linux educated person out there. I'm only able to push the files because my phone is already rooted. Hopefully you figure it out or someone more familiar with Linux (adb) commands can help you. Then, the "adb shell /data/local/tacoroot.sh --root" command is a breeze.
Click to expand...
Click to collapse
Thank you and CNexus. I'll try it and let you know how it went. I probably will fool around with it tomorrow sometime so I'll get back to you then. Going back a little, after I pushed flash_image and mtd-eng.img to data/local/, I noticed a blue status bar while in hboot, I'm assumming its searching for the pg36img.img update...... that said, is it necessary to push those files again?? BTW, great guide and write up. Thanks for everything. http://forum.xda-developers.com/images/smilies/good.gif
---------- Post added at 10:51 PM ---------- Previous post was at 10:46 PM ----------
Thanks for your help, I'll let you know how it goes tomorrow.
CNexus said:
Code:
adb push tacoroot.sh /data/local/tacoroot.sh
adb shell chmod /data/local/tacoroot.sh
adb shell sh /data/local/tacoroot.sh --setup
#should give an error after line above, its fine because you're pushing the local.prop yourself
adb push local.prop /data/local.prop
adb shell sh /data/local/tacoroot.sh --root
If anything goes wrong or it doesnt work, run this to revert
Code:
adb shell sh /data/local/tacoroot.sh --undo
I would've posted the tacoroot.sh for you since I use it in my shift utility to root your phone, but I wasn't sure if it was universal for all HTC devices or just for the evo shift. Sorry about that.
Thanks for your help, I'll let you know how it goes tomorrow.
Sent from my PG06100
Click to expand...
Click to collapse
Hi, Just wondering if you would mind re-uploading the original files? The link is broken, and I'd really like to unroot my phone, so it would be really appreciated. Thanks heaps!

Categories

Resources