Related
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?
********************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
Edit: "Rom Development" is only meant for very advanced technical discussion directly related to ROM development activity and the delivery of actual ROMs and ROM components ONLY. Nothing else goes in here. Moved thread to "General." Please refer to "[REF] STOP! Read before posting!" ~TheRomMistress
Not able to get ROM manager to flash Clockwork for recovery. It shows successful but then when I reboot to recovery, it shows this image of red triangle over a cellphone, probably meaning recovery does not function.
Any ideas? I already have S-OFF done...
BriEE said:
Not able to get ROM manager to flash Clockwork for recovery. It shows successful but then when I reboot to recovery, it shows this image of red triangle over a cellphone, probably meaning recovery does not function.
Any ideas? I already have S-OFF done...
Click to expand...
Click to collapse
This is how I got it to work:
Step 1 - run Visionary R12 to get perm root.
Step 2 - Push the files from page 1 to phone via adb
./adb push [path to file]/wpthis-Z.ko /data/local/wpthis-Z.ko
./adb push [path to file]/hboot_7230_0.84.2000_100908.nb0 /data/local/hboot-eng.img
(as you can see above, I renamed the HBOOT file on the phone just to be consistent)
note: I'm not sure if you HAVE to put them in /data/local of if you can just run this from /sdcard - but I didn't want to experiment
Run the commands below as root via adb shell or from a terminal on your phone.
Step 3 -
insmod /data/local/wpthis-Z.ko
Step 4 -
dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
Step 5 -
sync
Step 6 - Wait two minutes and then run clockwork and try to install recovery - do not reboot your phone.
Worked for me. Good luck.
I already have S-OFF and perm root though, why do it again?
So you're saying the WP isn't perm and neither is S-OFF? Is our root perm even lol?
Just reflash clockwork from rom manager. Same thing happened to me.
foxfire235 said:
Just reflash clockwork from rom manager. Same thing happened to me.
Click to expand...
Click to collapse
Same here, just reflash clockwork a second time and it should work.
Sent from my HTC Vision using XDA App
I had to flash CW twice as well. It seems successful after the first try but booting into recovery would show a black screen with a small phone icon.
codf4ther said:
I had to flash CW twice as well. It seems successful after the first try but booting into recovery would show a black screen with a small phone icon.
Click to expand...
Click to collapse
Did you just flash it twice, or did you follow the complete instructions twice?
OK first of all:
1 - I am a total noob
2 - Because of #1, I shouldnt have been doing this!
I unlocked my bootloader and was in the process of rooting my phone and when it booted up, I am stuck at the google screen with the unlocked lock at the bottom...any help here?
i CAN take out battery and load into the mode where I press volume up and power at the same time...if that helps.
When I do take out the battery, put it back in, then press the power and volume up buttons, then select recovery, I get a triangle with the "!" in it...dont know if that means anything to anyone or not.
When u get to the triangle part, Hold Power then press volume up. This will get you into recovery.
BUT you need to flash ( or re-flash) clockwork recovery via fast-boot ( follow the root guides) because looks like you didn't flash it.
Since you were attempting to root anyway, may I suggest you head over to the rooting guide, flash clockworkmod recovery and get a pre-rooted stock nandroid?
It lets me reboot the phone from there, but freezes on the google logo with the unlocked lock screen.
I cant seem to get the recovery img...like the link is bad....where else can i get it?
I googled and got the file, but when I type the command "fastboot flash recovery recovery.img" it says it cannot load "recovery.img" any help here?
chuckenfoot said:
I googled and got the file, but when I type the command "fastboot flash recovery recovery.img" it says it cannot load "recovery.img" any help here?
Click to expand...
Click to collapse
have android 2.3.X sdk set up properly? recovery.img needs to be in /sdk/tools/
zephiK said:
have android 2.3.X sdk set up properly? recovery.img needs to be in /sdk/tools/
Click to expand...
Click to collapse
Im sure I have it in the correct folder...what else?
wrong place
10char
Are you on a mac or a PC?
If you're on a mac I would suggest Kenvan19's rooting guide. It works great!
http://android.modaco.com/content/g...-colour-revert-superboot-rooting-the-nexus-s/
Chuckenfoot, Go to Paul's site Android Modaco see link above. I could'nt get fast boot commands to work and I almost gave up. His superboot method is absolutely the easiest method to get root and then you can install CWM. Follow his instructions and you'll be golden. Good Luck.
GFam4 said:
Chuckenfoot, Go to Paul's site Android Modaco see link above. I could'nt get fast boot commands to work and I almost gave up. His superboot method is absolutely the easiest method to get root and then you can install CWM. Follow his instructions and you'll be golden. Good Luck.
Click to expand...
Click to collapse
Superboot does make kernel modifications FYI. If you want to be completely stock and rooted so you can still get OTA superboot will prevent that.
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!