Related
So in my efforts to update my phone, I downloaded the July 2010 OTA radio. I also tried flashing the sprint radio 2.42.02.10.29
To my surprise, neither of them worked. It's like I am permanently unable to flash a radio. I can flash roms, themes, boot animations and everything else, just not radios. If anyone has any suggestions for this I greatly appreciate it. Here are the radios I've tried to flash and where I got them from.
2.42.01.04.27 from http://forum.xda-developers.com/showthread.php?t=728529
2.42.02.10.29 from http://forum.xda-developers.com/showthread.php?t=853868
Haven't seen anyone else on here ever have this issue except for 1 person and when I checked his post, no one had replied to it and it was almost a year old lol. Any help with this at all ?
spc_hicks09 said:
2.42.02.10.29 from http://forum.xda-developers.com/showthread.php?t=853868
Haven't seen anyone else on here ever have this issue except for 1 person and when I checked his post, no one had replied to it and it was almost a year old lol. Any help with this at all ?
Click to expand...
Click to collapse
So you are saying that you followed those instructions exactly and it did not flash?
In other words, you:
- copied that 2.42.02.10.29.zip file to the root of your SD card;
- you checked the MD5 of that file to make sure that it was fully downloaded;
- restarted in recovery and flashed that .zip file;
- you rebooted the phone and a very different screen appeared;
- it went back to Recovery with a message at the bottom saying "formatting cache..."
- you waited about a minute (it says 5 seconds, but I waited longer) and then rebooted the phone
And your radio baseband version did not update?
That's exactly what I'm saying. I flashed both radios and waited 10-15 on both of them and neither one of them did anything !?! So confused
Sent from my Ginger Tazz using XDA App
Well, if it's any consolation I haven't noticed anything different about that radio. People report that they get more "bars", but that's just a display thing - it doesn't mean that they get better performance or signal from the radio version.
You can try unrooting with btfb0's Flashback21 ROM - there is a version that flashes the current Verizon radio - and then re-root after that and see if it updates the radio for you.
http://forum.xda-developers.com/showthread.php?t=792026
Take the version of that with the radio, obviously.
What bootloader (version) and recovery (version) are on the phone when you perform the flashing operation?
What is the version # of the radio firmware which doesn't get removed/overflashed?
When you complete the flashing operation, are you using the reboot menu item? (I'm presuming you are not pulling the battery or something unusual like that, but thought I would ask for completeness sake)
bftb0
PS If you have the engineering bootloader on your phone (1.49.2000 S-OFF), you can just flash the radio with fastboot from the PC:
Code:
fastboot flash radio radio.img
bftb0 said:
What bootloader (version) and recovery (version) are on the phone when you perform the flashing operation?
What is the version # of the radio firmware which doesn't get removed/overflashed?
When you complete the flashing operation, are you using the reboot menu item? (I'm presuming you are not pulling the battery or something unusual like that, but thought I would ask for completeness sake)
bftb0
PS If you have the engineering bootloader on your phone (1.49.2000 S-OFF), you can just flash the radio with fastboot from the PC:
Code:
fastboot flash radio radio.img
Click to expand...
Click to collapse
At work now but I will check it out when I get home. Im not sure how to check some of the stuff you're talking about so I will need your guidance later if possible.
Sent from my Ginger Tazz using XDA App
bftb0 said:
What bootloader (version) and recovery (version) are on the phone when you perform the flashing operation?
What is the version # of the radio firmware which doesn't get removed/overflashed?
When you complete the flashing operation, are you using the reboot menu item? (I'm presuming you are not pulling the battery or something unusual like that, but thought I would ask for completeness sake)
bftb0
PS If you have the engineering bootloader on your phone (1.49.2000 S-OFF), you can just flash the radio with fastboot from the PC:
Code:
fastboot flash radio radio.img
Click to expand...
Click to collapse
Recovery Version
RA-eris-v1.6.2
On HBOOT screen I see this:
PB00100 XC SHIP S-ON
HBOOT-1.49.0000 (PB0010000)
MICROP-0111
TOUCH PANEL-MELFAS_45_17
RADIO-2.42.00.04.12
FEB 8 2010, 00:08:56
Radio that will not change or anything is:
2.42.00.04.12 which is the pre July 2010 OTA update Radio
Yes you presumed right, I am "rebooting" through the recovery menu as opposed to pulling the battery or anything else.
Executive summary: just get the engineering bootloader (1.49.2000 S-OFF) installed on your phone, and flash radios using fastboot (being very very careful to verify MD5 signatures). If you are going to be flashing stuff to your phone frequently, you really want the S-OFF bootloader on your phone for disaster recovery reasons anyway.
OK, I ran a fairly long experiment on your behalf, and it went like this:
- flash 2.42.02.10.29.zip from Amon_RA (succeeded; bootloader was 1.49.2000 S-OFF)
- flashed older radio (2.42.00.04.12) image file back into place using fastboot (not Amon_RA)
- Downgraded my bootloader to 1.49.000 S-ON using fastboot
- flash 2.42.02.10.29.zip from Amon_RA (failed; bootloader was 1.49.0000 S-ON)
- Upgraded my bootloader using "erisengspl.zip" + Amon_RA **** back to 1.49.2000 S-OFF
- flash 2.42.02.10.29.zip from Amon_RA (failed; bootloader was 1.49.2000 S-OFF)
- rebooted once (into OS) and then booted into recovery
- flash 2.42.02.10.29.zip from Amon_RA (succeeded; bootloader was 1.49.2000 S-OFF)
So, I was expecting to see that your trouble had something to do with your bootloader version - especially after seeing the first failure that I observed ... but then I was able to get it to both succeed and fail using the same S-OFF (1.49.2000) bootloader - and the only thing which changed was that I rebooted once between the trial that succeeded, and the trial which failed.
At that point, I did not go back and re-run any trials with the 1.49.0000 S-ON bootloader to see if I could get it to suceed - because it was evident that something else was going on.
Some of this is not entirely unexpected. When you flash either of the firmware images (either the radio or the bootloader image files), it is actually the bootloader that does the flashing, not the recovery boot: that's why the recovery tells you to "reboot .... to complete the installation". What the recovery does is to "stage" the image file (in /cache, I suspect), and then write some instructions into the "misc" partition that tell the bootloader what to do the next time the phone resets.
That's why - when things work correctly - the phone momentarily goes dark, you see a graphic image on the screen (that suggests that flashing is taking place), and then the phone reboots again ... and ends up back in the recovery boot !! (You will have to take my word for it, if you don't remember what it looks like). That "flashing" graphic image is put up on the screen by the bootloader; when it finishes up, it chains back to the recovery boot ... and communicates to the recovery (via the either the misc partition or the cache partition), "hey, wipe the /cache partition as soon as you start up". (Note the implications - the next OS reboot will need to rebuild the dalvik-cache(s))
The thing is, "misc" gets written to every time the phone shuts down or boots up - whether we are talking about starting from the OS, from the recovery boot, from fastboot mode, or from RUU mode - and how many different ways are there to reboot?
- battery pull
- fastboot reboot-recovery
- fastboot reboot
- adb shell reboot bootloader
- adb shell reboot recovery
- reboot Amon_RA from menu
- (cold start) -> fastboot mode -> hboot mode -> recovery
- (cold start) -> hboot mode -> recovery
- (cold start) -> recovery
In any event, if you want to tease this all out, with some experimenting around with the way that you get into the recovery boot, you can probably get the flashing method to work. ( For instance, you could probably use an adb shell session with Amon_RA running to "flash_image misc misc.img", where "misc.img" is the image file from jcase's "Flash Any RUU post" - and then use the flashable radio .zip file from within Amon_RA. )
But, as I mentioned above, it is a lot easier to just punt and install radios using fastboot and the S-OFF bootloader. Just be sure you have triple-checked everything before you hit the Enter key.
bftb0
**** EXTREMELY DANGEROUS UNLESS THE EXISTING BOOTLOADER IS 1.49.0000 - "erisengspl.zip" has hard-bricked phones that had 1.46.0000 bootloaders!
I really appreciate all the work man ! I did a search in the forums though and can't find the S-OFF bootloader. As soon as I read your question about the bootloader I was seriously wondering if it was because I have the S-ON bootloader. However, since you got both a success and a fail with the S-ON i'm not sure now what to think. I would like to get the S-OFF bootloader though so if you got a link to that, it would be greatly appreciated. Also again, thank you for the hard work and the time you put into all this man. Your knowledge never ceases to amaze me !
This would be what I want correct ?
http://forum.xda-developers.com/showthread.php?t=725047
Seems like a lot of work to get 1.49.2000 S-OFF
Also, do I have to go back to stock to do this ?
spc_hicks09 said:
I really appreciate all the work man ! I did a search in the forums though and can't find the S-OFF bootloader. As soon as I read your question about the bootloader I was seriously wondering if it was because I have the S-ON bootloader. However, since you got both a success and a fail with the S-ON i'm not sure now what to think. I would like to get the S-OFF bootloader though so if you got a link to that, it would be greatly appreciated. Also again, thank you for the hard work and the time you put into all this man. Your knowledge never ceases to amaze me !
This would be what I want correct ?
http://forum.xda-developers.com/showthread.php?t=725047
Seems like a lot of work to get 1.49.2000 S-OFF
Also, do I have to go back to stock to do this ?
Click to expand...
Click to collapse
You don't need to go back to stock to do that. That post will work. Slightly more effort than necessary, though.
You probably ought to familiarize yourself with the "old-fashioned" method of flashing a PB00IMG.ZIP file (see this post on AF (lots of pictures) for some background). All Eris RUUs, OTAs, and PB00IMG.ZIP files can be found at this XDA post
Because you have the 1.49.0000 S-ON bootloader, your phone would previously have been referred to as a "Leaker" phone. The only thing which stood in the way of "Leakers" applying any PB00IMG.ZIP file is that the "misc" partition contains a version number in it which blocks that from happening. jcase's method in that post you provided a link to is to "patch" the misc image with an older version number, and then you can proceed with any PB00IMG.ZIP file installation after you have patched the "misc" partition.
There is another option available to you, though, but I am reluctant to suggest it to you: because you have the 1.49.0000 bootloader, the "erisengspl.zip" flash method of installing the bootloader should work for you. (IT HAS BRICKED A 1.46.0000 PHONE, and there have been only a few people that have used it - I did it one hour ago, but hey, that's my phone, and there's a huge difference between doing something to your own phone and telling other people to do it).
If you want to try an alternative method, which should be:
- less effort than the URL link you provided
- safer than using "erisengspl.zip"
I could whip up a flashable version of "misc.img" - that way you don't need to fool around with adb commands - you would just flash a zip file that patches misc.img (instead of doing that manually with adb), and then after that just install the Root PB00IMG.ZIP ROM by putting it on the root folder of your SD card and powering up your phone (after you have made Nandroid backups and fully charged your phone, of course).
Say the word and I'll cobble that together.
bftb0
Here you go...
Introducing...
ErisMiscReset_v0.9.zip :
Size: 53,784 bytes
MD5: aeb8f3d9b2ab39379b8ee563c76efee0
Credits: jcase (for the misc.img file); Amon_RA (for the flash_image binary - from his v1.6.2 Eris recovery)
This doesn't do anything special - it just flashes the embedded "misc.img" file (jcase) to the "misc" partition. It could be done the hard way (with adb and the command line), but this makes life a little easier.
bftb0
bftb0 said:
You don't need to go back to stock to do that. That post will work. Slightly more effort than necessary, though.
You probably ought to familiarize yourself with the "old-fashioned" method of flashing a PB00IMG.ZIP file (see this post on AF (lots of pictures) for some background). All Eris RUUs, OTAs, and PB00IMG.ZIP files can be found at this XDA post
Because you have the 1.49.0000 S-ON bootloader, your phone would previously have been referred to as a "Leaker" phone. The only thing which stood in the way of "Leakers" applying any PB00IMG.ZIP file is that the "misc" partition contains a version number in it which blocks that from happening. jcase's method in that post you provided a link to is to "patch" the misc image with an older version number, and then you can proceed with any PB00IMG.ZIP file installation after you have patched the "misc" partition.
There is another option available to you, though, but I am reluctant to suggest it to you: because you have the 1.49.0000 bootloader, the "erisengspl.zip" flash method of installing the bootloader should work for you. (IT HAS BRICKED A 1.47.0000 PHONE, and there have been only a few people that have used it - I did it one hour ago, but hey, that's my phone, and there's a huge difference between doing something to your own phone and telling other people to do it).
If you want to try an alternative method, which should be:
- less effort than the URL link you provided
- safer than using "erisengspl.zip"
I could whip up a flashable version of "misc.img" - that way you don't need to fool around with adb commands - you would just flash a zip file that patches misc.img (instead of doing that manually with adb), and then after that just install the Root PB00IMG.ZIP ROM by putting it on the root folder of your SD card and powering up your phone (after you have made Nandroid backups and fully charged your phone, of course).
Say the word and I'll cobble that together.
bftb0
Click to expand...
Click to collapse
Ok quick question. After doing some digging, I found a post where jcase was working on a flashable zip that would give 1.49.2000 S-OFF. Someone noted that he no longer had an Eris and abandoned the project after pulling it. Well someone else "drewrobinso" picked up where jcase left off and finished the zip and in the post, starting at post 32 he posted that he fixed jcase's file and people after that say it "works perfectly." So I was wondering what your opinion is on this method. It can be found here.
http://forum.xda-developers.com/showthread.php?t=742735&highlight=engineering+bootloader&page=4
Here are the instructions they give for the hboot1492.zip
1) Download hbootupdate.zip
2) Placed it on root of sdcard
3) booted Recovery
4) nand backup
5) flashed hbootupdate.zip
6) rebooted (with menu) after the install of the hboot.zip
7) waited untill it came back to the recovery screen with " formatting cache..." at the bottom.
8) Waited for a few min then pressed reboot from the menu again.
9) waited for it to boot up and rebooted in to hboot as S-OFF was there
10) enjoyed it
spc_hicks09 said:
So I was wondering what your opinion is on this method. It can be found here.
Click to expand...
Click to collapse
Probably equivalent to the "erisengspl.zip" file (I haven't used it or looked at it) - you can find both, unpack them, and compare the differences. They should be extremely similar. I think the reason that jcase pulled his effort is because someone ended up with a brick - but I can't be 100% certain of that.
The thing you should be aware of is the lack of testing that goes into stuff on XDA. That "erisengspl.zip" floated around on XDA for months, and a few people in fact used it successfully. Those few people happened to be "Leakers" (with 1.49.0000 S-ON) on their phones.
The first person to try it with the 1.46.0000 S-ON bootloader on his phone hard-bricked his phone.
I suppose that it will work for you - but, flashing the bootloader is the most dangerous thing you can do to your phone. I prefer to be conservative about it.
LOL, I just realized that I said that after flashing it three times today.
PS we posted 60 seconds apart - look up above your post for a "misc" flasher .zip
bftb0 said:
PS we posted 60 seconds apart - look up above your post for a "misc" flasher .zip
Click to expand...
Click to collapse
Oh lol, sorry about that. Ok so if I use the misc flashable zip, which PB00IMG.ZIP would I want for the S-OFF, Leak 3 or the Root one ? I'll just use the method you're suggesting but I have no idea which PB00IMG.ZIP to use.
Nevermind lol obviously it would be the Root one since it's the only one with the Engineering Bootloader. Ok so if I downloaded the misc reset file and the PB00IMG.ZIP, do I flash the misc reset zip then the PB00IMG or what ?
bftb0 said:
If you want to try an alternative method, which should be:
- less effort than the URL link you provided
- safer than using "erisengspl.zip"
I could whip up a flashable version of "misc.img" - that way you don't need to fool around with adb commands - you would just flash a zip file that patches misc.img (instead of doing that manually with adb), and then after that just install the Root PB00IMG.ZIP ROM by putting it on the root folder of your SD card and powering up your phone (after you have made Nandroid backups and fully charged your phone, of course).
Say the word and I'll cobble that together.
bftb0
Click to expand...
Click to collapse
Nevermind LOL ! I swear as I get older I forget more and more stuff ! You gave me the directions right in your other post hahahaha. Ok so i'm going to charge my phone up then follow the instructions in this post and hopefully a couple hours from now I'll have the S-OFF bootloader. I'll definitely keep you updated once I start the process and hopefully we can get this resolved !!!
Flashed the zip and got the PB00IMG loading now. So far so good !
Now saying 1.49.2000 S-OFF !!!! Now it's going through and loading the system, recovery, radio_v2. Everything says -OK so far !
Rebooting now.......on the Verizon splash screen.............now it's not going anywhere just stuck on the Verizon logo !
Nevermind it booted ! Just took a while to load up !!!! Soon as everything is done loading I will check and see what the HBOOT screen says now.
Software Info:
Firmware - 2.1
Baseband - 2.40.00.01.22
Kernel - 2.6.29-5898f66b [email protected] #1
Build Number - 2.19.605.1 CL123435 test keys
Software Number - 2.19.605.1
Browser Version - WebKit 3.1
PRI Version - 2.11_002
PRL Version - 52219
ERI Version - 5
Rooting now with Eris 1 Click and will post HBOOT info in a few minutes.
spc_hicks09 said:
Nevermind LOL ! I swear as I get older I forget more and more stuff ! You gave me the directions right in your other post hahahaha. Ok so i'm going to charge my phone up then follow the instructions in this post and hopefully a couple hours from now I'll have the S-OFF bootloader. I'll definitely keep you updated once I start the process and hopefully we can get this resolved !!!
Click to expand...
Click to collapse
- Get the Root PB00IMG.ZIP file from this XDA post
- Verify it's size and MD5 signature on the copy you transferred to the root folder on your SD card.
- Put your phone on a charger.
- While it is charging, read through this post on AF (lots of pictures)
- Wait until fully charged, and
- Boot into recovery and make a Nandroid backup.
- (Optional: wipe data/factory reset)
- Flash the ErisMiscReset_v0.9.zip
- Power the phone off
- Boot the phone into HBOOT mode (Vol-Down+End)
- Follow the instructions in that Android Forums thread (PB00IMG.ZIP install)
Note that if you do not do the battery-pull trick, you will be overwriting everything on the phone. (That's OK because you have a backup, right?). If you did the "battery pull trick", you are done.
You can re-root the "root ROM" at that point, or, just skip that and use fastboot on your PC to directly flash the recovery to your phone. Put the phone in fastboot mode (cold-start with Send+End), and then test connectivity to the PC with:
Code:
fastboot devices
You should see your phone ID number if you are communicating correctly. Then,
Code:
fastboot flash recovery recovery-RA-eris-v1.6.2.img
Then, boot into Amon_RA directly by cold-starting the phone with Vol-Up+End, and "wipe data/factory reset" and restore your Nandroid backup.
Finally, you can flash a radio image directly at this point. (Note that we are not talking about a zip file, but the individual "radio.img" file that you would dig out of the 2.42.blahblahblah.zip file). Restart the phone in Fastboot Mode (Send+End) and
Code:
fastboot flash radio radio.img
Don't forget to remove the PB00IMG.ZIP file from the root folder of your SD card - otherwise you will forget about it and the next time you boot into HBOOT mode, the bootloader will start loading it up again.
HTH
bftb0
This explains a lot... Thanks.
I've not been able to figure out why my radio won't update until now.
And it allllllllll WORKED !!!!
HBOOT Info:
PB00100 XC ENG S-OFF
HBOOT-1.49.2000 (PB0010000)
MICROP-0111
TOUCH PANEL-MELFAS_45_17
RADIO-2.40.00.01.22
Jan 24 2010, 22:35:57
Dude you are a frickin genius !!!!! LOL
So now I should be able to update my Radio with either fastboot or adb or just by flashing right ?
You should make a main topic in Developement about your new method to get S-OFF. That was so much more simple than ANYTHING else I found !
Where do I need to have the Radio.img file because I have it in the ADB folder right now, trying to flash through fastboot but it keeps saying "error cannot load radio.img"
spc_hicks09 said:
And it allllllllll WORKED !!!!
Click to expand...
Click to collapse
You've now experienced "old school Eris root".
spc_hicks09 said:
So now I should be able to update my Radio with either fastboot or adb or just by flashing right ?
Click to expand...
Click to collapse
You certainly should be able to do it with fastboot. As I said before, I'm not precisely sure what was causing your Amon_RA installs to fail.
Just make sure you always, always, always verify file MD5 sigs of image files before flashing them with fastboot.
bftb0
I just acquired a Droid Eris from my buddy of mine, when you turn it on it just stays at the screen with the 3 androids on skateboard(if I turn it on with it plugged into usb It makes the connection noise though). I can Also get into hboot and recovery but no matter what I do it will not install anything, everything just fails. Also its say its S-ON. Any help would be great, thanks.
glitch666 said:
I just acquired a Droid Eris from my buddy of mine, when you turn it on it just stays at the screen with the 3 androids on skateboard(if I turn it on with it plugged into usb It makes the connection noise though). I can Also get into hboot and recovery but no matter what I do it will not install anything, everything just fails. Also its say its S-ON. Any help would be great, thanks.
Click to expand...
Click to collapse
Well, you didn't really say what "everything just fails" means. How about giving us an error message?
While you are at it, what version of recovery is on the phone - Amon_RA v1.6.2, or some version of Clockwork?.
Same deal for the bootloader - how about an exact version number - 1.49.0000, 1.47.0000, or other?
Because your phone is already "soft-bricked", and you got it for free, and because your recovery boots up, you can try flashing "ErisMTDNuke_v0.9.zip". You can find it at this post:
http://forum.xda-developers.com/showpost.php?p=11651122&postcount=21
It has an an assert() in it that tries to block it from running on ClockworkMod, but depending on what version of recovery you have, that may not matter. Let me know if you get any errors running it. If it runs, you should be back in business; it leaves the /system, /data, and "boot" partitions of the ROM blank, so you will need to flash a ROM afterwards. Also, if you have ClockworkMod recovery on the phone, you should consider getting it off of there, and putting one of the two Amon_RA recovery variants on there.
You might find the entire thread that contains the above post very useful, as it describes a method for installing the S-OFF bootloader using the "SoSickWiTiT" rooting method, as well as other tricks such as using fastboot to soft-load recoveries without writing them to flash; that full thread is here:
http://forum.xda-developers.com/showthread.php?p=11652502
Please provide full details on what works / doesn't work, particularly with "ErisMTDNuke_v0.9.zip" - it has only been used on 3 phones so far (worked on all three, though).
cheers
bftb0
I dont think the phones been rooted(my friend has no idea what that even is). It has hboot 1.49.0000, and the recovery is not a custom one, its Android recovery 2e. If I try to Install an update through recovery its says installation aborted. Also if I use pb00img.zip it loads in hboot but says previous version is older and to reboot.
glitch666 said:
I dont think the phones been rooted(my friend has no idea what that even is). It has hboot 1.49.0000, and the recovery is not a custom one, its Android recovery 2e. If I try to Install an update through recovery its says installation aborted. Also if I use pb00img.zip it loads in hboot but says previous version is older and to reboot.
Click to expand...
Click to collapse
OK, that is completely different. It is impossible to load a dev ROM using the stock recovery <2e>
Did you try the "wipe data/factory reset procedure" of the recovery menu, or have you already done that and then the phone hangs at the three droids?
bftb0
If the stock ( <2e> ) recovery factory reset does not work, then the method of last resort is going to be to try and get the S-OFF bootloader onto the phone using the "SoSickWiTiT" rooting method.
Generally what happens - if you have corrupted flash memory partitions - is that parts of this install will fail, but getting the engineering bootloader (1.49.2000 S-OFF) onto the phone will succeed - and from there you can leverage the behaviors of the S-OFF bootloader to get a custom recovery running (by using fastboot). Once that happens, you can run the ErisMTDNuke_v0.9.zip flash to erase the /system, /data, and "boot" partitions, so that a subsequent ROM flashing operation will succeed (probably, no guarantees).
The way the "SoSicWiTiT" rooting method works, you run the "Official 2.1 RUU" Utility on the PC - but just before it is ready to start writing to the phone (after it has unpacked all it's temporary files and installed drivers for you), you take the "Root PB00IMG.ZIP" file, rename it to "rom.zip", and replace the "rom.zip" file unpacked in the temporary file area of the RUU. This gets the S-OFF bootloader installed (at a minimum, possibly the whole rom if your problem is not flash memory page corruption).
The thread I mentioned above has more details; ask questions if you don't understand something.
bftb0
PS You should be doing all of these operations with a well charged battery - 100% is a good place to start. Don't let the phone sit in HBOOT or FASTBOOT mode for extended periods of time - the battery will discharge rapidly, even if the phone is plugged in to the charger.
Thank you for the quick and to the point replies, I will try this later tonight and will post and let you know if it works out. I have tried the factory reset and it doesn't work, but hey it was free if I screw it up Its no big issue lol. Im not new to rooting its just I have no experience with this particular phone, so thank you =].
glitch666 said:
Thank you for the quick and to the point replies, I will try this later tonight and will post and let you know if it works out. I have tried the factory reset and it doesn't work, but hey it was free if I screw it up Its no big issue lol. Im not new to rooting its just I have no experience with this particular phone, so thank you =].
Click to expand...
Click to collapse
OK. Good luck.
The Root PB00IMG.ZIP and the "Official 2.1 RUU" can be found here:
Consolidated HTC RUU, Leak, and OTA Downloads
Amon_RA's original (v1.6.2) recovery is located here
If you don't have a version of fastboot on your PC/workstation already, you can find different platform versions of it a short distance down the HTC's developer page for the ADP.
If you can get the S-OFF bootloader onto the phone, then you can flash Amon_RA's recovery from the PC with a single command:
Code:
fastboot flash recovery recovery-RA-eris-v1.6.2.img
If you don't already have USB drivers installed on your PC, the RUU utility should be able to do it for you automatically (although ymmv depending on your Xp/Vista/Win7/x32/x64 variety).
Let me know how things go.
bftb0
PS It is worth repeating - make sure your phone is well charged when you are doing any flashing.
Yeah I know fastboot like the back of my hand(g1 and other phones that I love dearly but no longer have), im giving this a shot right now, thank bud.
glitch666 said:
Yeah I know fastboot like the back of my hand(g1 and other phones that I love dearly but no longer have), im giving this a shot right now, thank bud.
Click to expand...
Click to collapse
Standing by.
No matter what the official 2.1 RUU gives me a bootloader mismatch error 140 with either the actual rom.zip or the root rom renamed to rom.zip and placed in the temp folder, let me try some more things. Edit RUU says Im going from 2.37.605.4 to 2.36.605.1. Ok so this leads me to believe it has the 4th OTA on it right?
PS -
I might have mentioned it in that other thread, but anyway: the RUU utility will get the phone to cooperate if the phone is put into fastboot mode (or RUU mode). Normally it is expected that the phone will be booted normally when you start up the RUU... but that (obviously) isn't an option for a soft-bricked phone.
cheers
glitch666 said:
No matter what the official 2.1 ruu gives me a bootloader mismatch error 140 with either the actual rom.zip or the root rom renamed to rom.zip and placed in the temp folder, let me try some more things.
Click to expand...
Click to collapse
Rats. Does that happen immediately after the RUU starts up, or only when you tell it to begin the flashing operation?
Here's another wild straw to grasp at.
If you plug the phone into your PC, and then cold-start it (normal boot), do you hear 2 USB sequences at about 5 and 9 seconds, respectively? If the kernel is alive, but looping on something.... and the prior user had USB debugging enabled, and it's a 2.1 ROM, we can probably still root it by hand across ADB.
does "adb devices" give you anything 15 or more seconds after boot-up, or does your (Windows) device manager indicate a "Composite Interface"?
bftb0
Edit RUU says Im going from 2.37.605.4 to 2.36.605.1. Ok so this leads me to believe it has the 4th OTA on it right?
Click to expand...
Click to collapse
Sure sounds that way. Normally that info (the "Main Version") is stored in the misc partition, and it rather surprises me that an OTA install would cause that to happen; but I can't argue with what you are seeing.
That might mean that neither RUU nor PB00IMG.ZIP installs will work without being able to modify the RUU program to ignore version checks.
How about the adb angle - does anything come up on the USB when the 3 skating droids are showing?
No it goes all the way to the flashing processes after the phone goes into bootloader mode. then stops and gives me the error, now with adb when I turn the phone on I hear one chime and then get a device not recognized and no output from adb. Did you see my last post on the other page I edited it about the bootloaders, its says its going from 2.37.605.4 to 2.36.605.1. Sorry you posted before me so ignore this last tid bit.
Long shot, but check your HBOOT screen again - is it still S-ON (1.49.0000) ?
BTW, when you say "bootloader mode" - do you mean FASTBOOT or RUU mode? (The RUU mode is just a graphic with the HTC logo in the middle of the screen, sometimes with small arrows in each of the 4 corners of the screen. FASTBOOT mode says either "FASTBOOT" or "FASTBOOT USB" right on the screen).
I would think that you are starting the process with the phone in FASTBOOT mode, right?
bftb0 said:
Sure sounds that way. Normally that info (the "Main Version") is stored in the misc partition, and it rather surprises me that an OTA install would cause that to happen; but I can't argue with what you are seeing.
That might mean that neither RUU nor PB00IMG.ZIP installs will work without being able to modify the RUU program to ignore version checks.
How about the adb angle - does anything come up on the USB when the 3 skating droids are showing?
Click to expand...
Click to collapse
I am not getting anything from adb.
bftb0 said:
Long shot, but check your HBOOT screen again - is it still S-ON (1.49.0000) ?
Click to expand...
Click to collapse
Yup it stayed the same.
bftb0 said:
Long shot, but check your HBOOT screen again - is it still S-ON (1.49.0000) ?
BTW, when you say "bootloader mode" - do you mean FASTBOOT or RUU mode? (The RUU mode is just a graphic with the HTC logo in the middle of the screen, sometimes with small arrows in each of the 4 corners of the screen. FASTBOOT mode says either "FASTBOOT" or "FASTBOOT USB" right on the screen).
Click to expand...
Click to collapse
First I put the phone into fastboot mode, then fire up RUU and it kicks the phone to a black screen with an htc logo in the middle and trys to flash it(the RUU says its putting the phone into bootloader mode so I guess thats what its in when it restarts to the htc logo).
Don't Quote me but I know the Eris is Almost like my Hero, and with the Hero there's a way to Get it into the Fastboot I Think by Holding Volume Up and Powering on the Phone! Then you Should be Able to Run the Latest RUU for the Eris... Hopefully that will get you back Right!!
Good Luck!
Sent from my Hero using XDA App
Phone: Evo 3D
Android Version: 2.3.4
Software number: 2..08.651.3
Hboot: 1.50
S-On
Done:
1) HTC boot unlock (http://htcdev.com/bootloader)
2) http://forum.xda-developers.com/showthread.php?t=1239821
-was able to push flies over to phone, but command line "fastboot flash recovery recovery.img" resulted in errors
3) tried to downgrade Hboot using RUU and got an error telling me that my current version was most up to date
Common Threads:
1) http://forum.xda-developers.com/showthread.php?t=1388740
-I downloaded Superuser, titanium back up, and a random program that claimed to verify rooting -- all said I was NOT rooted
2) http://forum.xda-developers.com/showthread.php?t=1307982
-My true goal is to install wifi teathering and titanium backup, I don't care much for custom roms
Forum Confusion:
Unlocking the boot loader does not seem to be the same as rooting, but when I've search through the forums people offer one as a solution to the other.
I'd really appreciate any feedback
thanks guys,
-Nave
navenine said:
Phone: Evo 3D
Android Version: 2.3.4
Software number: 2..08.651.3
Hboot: 1.50
S-On
Done:
1) HTC boot unlock (http://htcdev.com/bootloader)
2) http://forum.xda-developers.com/showthread.php?t=1239821
-was able to push flies over to phone, but command line "fastboot flash recovery recovery.img" resulted in errors
3) tried to downgrade Hboot using RUU and got an error telling me that my current version was most up to date
Common Threads:
1) http://forum.xda-developers.com/showthread.php?t=1388740
-I downloaded Superuser, titanium back up, and a random program that claimed to verify rooting -- all said I was NOT rooted
2) http://forum.xda-developers.com/showthread.php?t=1307982
-My true goal is to install wifi teathering and titanium backup, I don't care much for custom roms
Forum Confusion:
Unlocking the boot loader does not seem to be the same as rooting, but when I've search through the forums people offer one as a solution to the other.
I'd really appreciate any feedback
thanks guys,
-Nave
Click to expand...
Click to collapse
Try this, starting over. You shouldnt run into any hiccups.
tailsthecat3 said:
Try this, starting over. You shouldnt run into any hiccups.
Click to expand...
Click to collapse
I received Error [155] Unknown Error
Display From Phone:
***Unlocked***
Shooter XC ship S-ON RL
HBoot-1.50.0000
eMMC-boot
Aug 7 2011, 10:21:40
RUU
Security fail!
Update Fail!
when it rebooted after recovery I still had all of my user data
navenine said:
I received Error [155] Unknown Error
Display From Phone:
***Unlocked***
Shooter XC ship S-ON RL
HBoot-1.50.0000
eMMC-boot
Aug 7 2011, 10:21:40
RUU
Security fail!
Update Fail!
when it rebooted after recovery I still had all of my user data
Click to expand...
Click to collapse
Ive been through this. Relock(lock) it, run the RUU, then proceed with the instructions I linked.
I was never able to run the RUU while the device was 'unlocked'.
tailsthecat3 said:
Ive been through this. Relock(lock) it, run the RUU, then proceed with the instructions I linked.
I was never able to run the RUU while the device was 'unlocked'.
Click to expand...
Click to collapse
I've been trying to lock it back through the CMD, I wrote a little batch file (and I've manually typed it):
cd c:\android
fastboot oem lock
but after it runs a line shows up as follows:
< waiting for device >
I have USB debugging mode on, and I've tried it with the sd card both mounted and unmounted, I have all the drivers, and adb commands are effective...
do you know what I'm missing?
Thanks again for the help,
-Evan
hey im trying to use the ruu to get back to stock , just re locked the phone , and im STILL getting errors with ruu, its saying Update Failed : Hboot version is older , im on hboot 1.5000 .........Im losing my mind trying to get this thing back to stock and out of htc screen logo bootlooping.........any ideas?
navenine said:
I've been trying to lock it back through the CMD, I wrote a little batch file (and I've manually typed it):
cd c:\android
fastboot oem lock
but after it runs a line shows up as follows:
< waiting for device >
I have USB debugging mode on, and I've tried it with the sd card both mounted and unmounted, I have all the drivers, and adb commands are effective...
do you know what I'm missing?
Thanks again for the help,
-Evan
Click to expand...
Click to collapse
That tells me that youre not in fastboot on your device. I can dupe the same message with my phone disconnected from the pc, then I plug it in in fastboot, and all is good.
Please reinstall the drivers needed but it sounds like youre good. On occasion, I wont be able to flash some things or a file cant load. A reboot of the pc fixes those rare cases for me. Also, refreshing the folders where the files are located.
I also had issues using fastboot, flashing things to the evo because I had my nexus connected for a tether.
If I could do it for you, I would. Hopefully I can help.
tailsthecat3 said:
That tells me that youre not in fastboot on your device. I can dupe the same message with my phone disconnected from the pc, then I plug it in in fastboot, and all is good.
Please reinstall the drivers needed but it sounds like youre good. On occasion, I wont be able to flash some things or a file cant load. A reboot of the pc fixes those rare cases for me. Also, refreshing the folders where the files are located.
I also had issues using fastboot, flashing things to the evo because I had my nexus connected for a tether.
If I could do it for you, I would. Hopefully I can help.
Click to expand...
Click to collapse
this just got even worse, I uninstalled the drivers, and now I can't reinstall them. I can't find them. My computer wont recognize my phone at all. I've tried to goto the device manager and find them online automatically, and I've tried the google USB drivers from the extra folder from the SDK Manager...
if you can point me toward the USB drivers that'd be great, but regardless, what your saying is I need to connect my phone while its in the bootloader? not once its booted? or are you saying I need to boot my phone through the bootloader selecting "fastboot" first?
thanks again
-Nave
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
tailsthecat3 said:
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
Great, I have all the drivers, my phone is relocked, and I'm running the RUU prog now, I'll post in a few minutes to say what happens
thanks for all the help so far, I really do appreciate it!
-Nave
navenine said:
Great, I have all the drivers, my phone is relocked, and I'm running the RUU prog now, I'll post in a few minutes to say what happens
thanks for all the help so far, I really do appreciate it!
-Nave
Click to expand...
Click to collapse
Good. Ive done the process on two different 3D's, a few times. If you follow the instructions, its almost as easy to root as my nexus s was.
tailsthecat3 said:
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
I pushed everything over, got it into the fastboot USB and then typed the "fastboot flash recovery recovery.img" command line
my script was:
sending 'recovery' <5068 KB>...
Okay [ 1.207s]
writing 'recovery'...
<bootloader> signature checking...
FAILED <remote:signature verify fail>
finished. total time: 1.855s
any ideas?
tailsthecat3 said:
Good. Ive done the process on two different 3D's, a few times. If you follow the instructions, its almost as easy to root as my nexus s was.
Click to expand...
Click to collapse
Great! thank you soooo much I finally have everything working the way I want it!
haha it seems so much easier now that I know what I was supposed to do
navenine said:
Great! thank you soooo much I finally have everything working the way I want it!
haha it seems so much easier now that I know what I was supposed to do
Click to expand...
Click to collapse
Where were you going wrong? And what'd you do to correct it? So everyone knows, in case they encounter the same issues.
Sent from my Google Nexus S 4G via XDA Premium
Good Idea:
Problem 1)
The RUU wouldn't run
I had this problem because I had already unlocked the the bootloader
I had to re-lock it in order to fix it
Problem 2)
Then The Recovery.img would push through because I forgot to re-unlock the phone
what I did that made it easier:
I wrote a little batch file to run the scripts - a batch file is a command prompt command list set. you open a notepad, type in the the command lists and save it with a .bat file extension...
so I would install all the files and then make a batch file with the following:
cd C:\android
adb push recovery.img /sdcard/
adb push su-2.3.6.3.zip /sdcard/
adb reboot bootloader
pause
fastboot flash recovery recovery.img
change the C:\andriod to whatever your directory set was
and when the batch program runs
anyway good luck to anyone who ends up here, and thanks again tailsthecat3 for the great help
navenine said:
Good Idea:
Problem 1)
The RUU wouldn't run
I had this problem because I had already unlocked the the bootloader
I had to re-lock it in order to fix it
Problem 2)
Then The Recovery.img would push through because I forgot to re-unlock the phone
what I did that made it easier:
I wrote a little batch file to run the scripts - a batch file is a command prompt command list set. you open a notepad, type in the the command lists and save it with a .bat file extension...
so I would install all the files and then make a batch file with the following:
cd C:\android
adb push recovery.img /sdcard/
adb push su-2.3.6.3.zip /sdcard/
adb reboot bootloader
pause
fastboot flash recovery recovery.img
change the C:\andriod to whatever your directory set was
and when the batch program runs
anyway good luck to anyone who ends up here, and thanks again tailsthecat3 for the great help
Click to expand...
Click to collapse
I appreciate that, thank you.
The release by HTC of an unlockable bootloader (v 1.51.0000) for the Droid Eris has created a potential opportunity for rescue of some soft-bricked Eris handsets.
Are you an owner of one of these units? There is a decent chance of recovery back to a working state!
(Props go to Android Forums user "scotty85" for figuring this out.)
This (v 1.51.0000) bootloader is rather quirky - it does not allow direct flashing of individual partitions using fastboot - but it does allow flashing of zip files containing recovery, boot, and system partitions via fastboot with the phone in "RUU mode" once the bootloader is unlocked with a procedure from HTC.
If your phone can be booted into its' bootloader (HBOOT, FASTBOOT, or RUU mode), but can not successfully boot all the way up - or it gets stuck in a bootloop during booting, and you only have a stock recovery on the phone, this might be the approach for you.
Rather than write up the whole method to begin with, I'll just ask for responses to see if anyone is interested. And then take it from there if I get some nibbles.
If you think you have a phone you want to try to rescue, speak up - and say a few words about whether the phone can get into different bootloader modes, which bootloader version you have on the phone, and so forth.
Note: at the moment, getting this to work requires getting the fastboot program running on your PC - it is not a phone-only method. The amount of effort at the command line is minimal, but you will need to be able to get your PC talking to your phone to do this.
bftb0
I have a friend who is in this exact situation. Any help you can provide would be great.
Yatyas said:
I have a friend who is in this exact situation. Any help you can provide would be great.
Click to expand...
Click to collapse
Take your time, and read and understand this whole post before you begin.
[size=+2]Files Needed:[/size]
Collect all the files you will need, get them on to the root folder of your SD card, and verify their MD5 signatures (the copy that makes it to your SD card, not the copy on your computer) :
"rom.zip" - the 1.51.0000 bootloader install payload - here **
MD5: daab6bcbe78c41938a95c4963c5c44e8
custom recovery - either Amon_RA's ("recovery-RA-eris-v1.6.2.img"), or scary alien's trackball-free derivatives here (e.g. the New 1.7.1 version)
"ErisMiscReset_v0.9.zip" here
"MTD_Inspect_v0.9.zip" here
"ErisMTDNuke_v0.9.zip" here (also, please see disclaimer here)
"Eris_RootROM_v2.19.605.1_PB00IMG.zip" from shipped-roms.com. Note that this (also) is renamed to PB00IMG.zip at the appropriate time. **
A custom (dev) ROM, or even a fully stock ROM such as the HTC Eris March 2011 OTA Stock ROM - v2.41.605.6
[size=+2]Installation Method:[/size]
Note:
A less thorough method than what is described here, but shorter, is reported here. Even though I built the "ErisMTDNuke_v0.9.zip" repair tool, I do not advocate using it unless it is confirmed to be absolutely necessary. Moreover, in almost every case, having the Eris S-OFF bootloader on a rooted phone is an advantage, and (also) having the "misc" partition "MainVer" value reset back to a low value after fooling with RUUs or PB00IMG.zip installs is a good idea to prevent future disasters. The short method does not document either of these two steps.
Note #2: In any of these procedures, it is important to do so with A FULLY CHARGED PHONE. Do not let the phone sit idle for long periods of time in HBOOT, FASTBOOT, or RUU modes - even with the Eris plugged in to a USB port, in those modes it will discharge very rapidly - about two hours or so. That little green light is your friend.
- get fastboot on a PC working and communicating with the phone in its' current state (with the phone in fastboot mode or RUU mode). Doubtful if I will reply to inquiries about Windows and driver installs - it's covered in gory detail all over the place. Same goes with getting a copy of "fastboot.exe" for windows. (Google is your friend).
- Install the "rom.zip" file for the 1.51.0000 bootloader, (Rename to PB00IMG.zip and install it by booting the phone into HBOOT mode**)
- register with htcdev.com for unlocking this new Eris bootloader & follow the bootloader unlocking instructions (you can skip downloading & running the RUU, as you have installed the bootloader already)
- create a zip file with a custom recovery image in it (named "recovery.img"), and an "android-info.txt" file with MainVer set to 2.42.0000 (see step #3 of this XDA post).
- using fastboot and the phone in RUU mode, flash this zip file ("fastboot flash zip zipfilename.zip") Again, see step #3 of the link above.
- power off the phone and boot into the custom recovery and flash the ErisMiscReset_v0.9.zip file (watch for any errors - stop if you see errors!).
- in the same recovery session flash the MTD_Inspect_v0.9.zip file and determine if you have massive (bad block) corruption in any of /boot, /system, or /data. (See instructions here)
- If the above mentioned partitions only have one or two bad blocks, skip the next step.
- Flash (in recovery) ErisMTDNuke_v0.9.zip
- Re-lock the 1.51.0000 bootloader (phone in fastboot mode) with "fastboot oem lock"
- Flash the Eris Root ROM (from shipped-roms.com), using the HBOOT+PB00IMG.zip install method. The objective of this step is primarily to get rid of the 1.51.0000 bootloader, and install the 1.49.2000 S-OFF bootloader. Note this will stomp on your custom recovery (unless you use the battery pull trick), but that's OK.**
- get the custom recovery back onto the phone - using either the standard Eris rooting tools (Dummies or One-Click), or simply flash it using fastboot (e.g. "fastboot flash recovery recovery-RA-eris-v1.6.2.img")
- one last time: in the custom recovery, flash the ErisMiscReset_v0.9.zip file
- Install a ROM and be happy.
** after using any PB00IMG.zip file, it is a really good idea to rename it ASAP, so that you don't accidentally re-install it by inadvertently powering up the phone in HBOOT mode.
bftb0
not much to add. if the notion of downloading the sdk,installing fastboot,adb,etc. is a bit overwhelming you can use this file: http://www.mediafire.com/?hzf1u4bowjewhdq it contains adb and fastboot,and a utility called md5sums,and the needed files to make them work.
simply download,extract(unzip),and place the extracted folder onto the root of the C drive on your PC.
open a command window in windows 7 by clicking the start bubble,and type "command" in the search box. i believe xp is the same,or similar.
once you have a small,black command window open,you can change to the "mini-adb" directory by typing this command:
Code:
cd c:\mini-adb
you can call that folder anything you want,but when you "cd" to it,you must type the exact name the folder is called.
for drivers to get the eris recognized by the PC,you can install htc sync,or use these modified htc drivers from revolutionary public wiki
just holler if you have any questions with any of the above
i got several stuck at 1.49.000000 s on . i dont know if they have the stock recovery on them or not . does have fastbootusb though and hboot
highhacker said:
i got several stuck at 1.49.000000 s on . i dont know if they have the stock recovery on them or not . does have fastbootusb though and hboot
Click to expand...
Click to collapse
Hopefully we can fix them. Do you have any questions to get started?
wrong nv items wont boot or boot into recovery
Hey guys this phone is on an endless bootloop. I installed the 1.51. hboot unlock the bootloader, flash aman recovery 1.6.2 via Ruu successfully but when I try to boot into recover it continues to bootloop. I already install recovery via hboot but no success. I am willing to try anything with this phone for educational purposes for I dont need the phone but is something that I started over a year ago when I did the mistake with the wrong NV items. I can successfully follow all the step until step 4 but when is time to boot recovery it simply wont or any other file. Tried via regular FASTBOOT recovery.img but no luck. I Still have the S-ON on hboot 1.51. Any suggestions????
@obonilla30
obonilla30 said:
Any suggestions????
Click to expand...
Click to collapse
I started a reply and then saw that you were communicating with the right folks over on Android Forums. I was going to send you to exactly the same thread that you found.
If I may make a suggestion - both your posts here and also over there at AF leave quite a bit open to interpretation. For instance, when you mention "bootlooping", you didn't say whether this was for entering recovery from a coldstart (Vol-Up+End/Power), or via navigating from either Fastboot mode (Send+End/Power) or HBOOT mode (Vol-Down+End/Power), and then traversing the menus there to boot the recovery partition. It might be that you tried all three - but you didn't say so. Slow down a little bit and fill in as much detail as you can.
There are TWO methods suggested over in that AF thread - one is to flash (w/ unlocked 1.51 bootloader in RUU mode) a custom recovery to the recovery partition, and the other is to flash a stripped-down version of the (custom) recovery to the boot partition. (You could actually do both in the same flashing operation if you wanted - but note that you can't just rename one of the custom recovery images to "boot.img", because they are too big. But scary alien and scotty85 over there on AF put together something that will fit into the boot partition). That gives you two different ways to get a privileged execution environment running.
cheers
bftb0
PS Not to rehash old painful memories, but do you recall what exactly it was you did when you "did the mistake with the wrong NV items"?
S###
scotty1223 said:
Hopefully we can fix them. Do you have any questions to get started?
Click to expand...
Click to collapse
Well these "steps" got me no where . First step was put the hboot on my sd card and boot into hboot . still have Hboot 1.49.0000 (PB0010000) S-ON ((( That don't work . I got a box full of eris all 1.49.0000 s-on that show some kind of semi recovery on them where i can flash an update.zip and clear to factory .etc.. Still all stuck on three green androids.. Not very good with adb on pc but tried it in fastbootusb mode on phone and gave the command fastboot flash zip zipfilename.zip (my zip) and said remote not allowed . I have 15 tabs up on firefox and is just too much back and forth . is there a Dummy guide
highhacker said:
Well these "steps" got me no where . First step was put the hboot on my sd card and boot into hboot . still have Hboot 1.49.0000 (PB0010000) S-ON ((( That don't work . I got a box full of eris all 1.49.0000 s-on that show some kind of semi recovery on them where i can flash an update.zip and clear to factory .etc.. Still all stuck on three green androids.. Not very good with adb on pc but tried it in fastbootusb mode on phone and gave the command fastboot flash zip zipfilename.zip (my zip) and said remote not allowed . I have 15 tabs up on firefox and is just too much back and forth . is there a Dummy guide
Click to expand...
Click to collapse
You will always get "remote not allowed" with a S-ON bootloader, or with the 1.51.000 bootloader in the locked state. And you will probably also get that error even with a 1.51.0000 bootloader in an unlocked state if you try putting a "boot.img" or "recovery.img" file in the zip. Don't bother using fastboot with a 1.4x.00 S-ON bootloader - it doesn't ever work for anything useful.
Note also that the steps given above need to be performed in sequence and each step needs to succeed. There is no point in doing a 2nd or 3rd step if the first step fails.
As for the PB00IMG.zip install of the 1.51.0000 bootloader, when you boot the phone into HBOOT mode, you should see SOMETHING different happen - even if it is a failure of some sort - than how HBOOT behaves when there is no PB00IMG.zip file on the SD card. If the phone behaves identically whether or not you have the SD card in place, then that means you mis-spelled the name of the PB00IMG.zip file, or didn't put it in the top-level folder of the SD card. Even in the case where it is there on the card, but corrupted, you will see a different behavior of the HBOOT from when there is no PB00IMG.zip file present.
Unfortunately, your post above gives no details about this. That means that anybody that is willing to try and help you is forced to guess about what you are seeing your phone do.
bftb0
defiantely the first step is to get 1.51 onto the phone. in addition to the above,make sure that your sd card is formatted FAT32. i cant remember if this is important for the eris,but it is crucial for other dervices..
what you should see when a properly named PB00IMG file is placed on the root of the sd card,is a quick flash of green writing,then status bars on the upper right corner of the screen as the phone finds and checks the file,followd by a "do you want to update" prompt.
another common error with a PxxxIMG file on any devices,is that the decive must see PxxxIMG.zip. in the case of the eris,the file on the phone must be "PB00IMG.zip". the common error part comes from naming the file with windows. lots of folks will type in the .zip,forgetting that windows naturally adds and hides the file extension. therefore,typing in "PB00IMG.zip" actually names the file to "PB00IMG.zip.zip" in rarer cases,not typing in the ".zip" with windows if configured differently may end up in the file just being "PB00IMG" wish will not be found either.
so to recap
-check sd card for FAT32
-check the name of PB00IMG on the sd card. try adding or removing the ".zip"
-make sure PB00IMG is on the top level of the sd,not hidden inside a folder.
let us know how that goes
once you get the 1.51 hboot onto the phone,the next step is to unlock it. just holler if you have questions on htcdev's directions.
One of the simple mistakes that people make is when they rename the "rom.zip" file, they rename it as
PBOOIMG.zip (PB "oh-oh" IMG.zip)
instead of the correct spelling
PB00IMG.zip (PB "zero-zero" IMG.zip)
As scotty and I both pointed out, if you have a correctly named file on there in the top-level folder, you will see *something* different happen, even if the file is corrupted.
If you don't see something different happen, then the problem is the SD card format, a mis-spelling of the file name (I recall some people transferring files from their PCs, ending up with a file named "PB00IMG.zip.zip"), or the file is not in the top-level folder of the SD card.
bftb0 said:
You will always get "remote not allowed" with a S-ON bootloader, or with the 1.51.000 bootloader in the locked state. And you will probably also get that error even with a 1.51.0000 bootloader in an unlocked state if you try putting a "boot.img" or "recovery.img" file in the zip. Don't bother using fastboot with a 1.4x.00 S-ON bootloader - it doesn't ever work for anything useful.
Note also that the steps given above need to be performed in sequence and each step needs to succeed. There is no point in doing a 2nd or 3rd step if the first step fails.
As for the PB00IMG.zip install of the 1.51.0000 bootloader, when you boot the phone into HBOOT mode, you should see SOMETHING different happen - even if it is a failure of some sort - than how HBOOT behaves when there is no PB00IMG.zip file on the SD card. If the phone behaves identically whether or not you have the SD card in place, then that means you mis-spelled the name of the PB00IMG.zip file, or didn't put it in the top-level folder of the SD card. Even in the case where it is there on the card, but corrupted, you will see a different behavior of the HBOOT from when there is no PB00IMG.zip file present.
Unfortunately, your post above gives no details about this. That means that anybody that is willing to try and help you is forced to guess about what you are seeing your phone do.
bftb0
Click to expand...
Click to collapse
Well that was agood guess. The first step change rom.zip to PB00IMG.ZIP (I ASSUME THAT IS ZERO ZERO ) . it does somthing fast and i can see no image somthing like
Loading .....(PB00DIA0.zip)
no image
loading ......(PB00DIA3.zip)
no image
loading ......(PB00DIA2.ZIP)
no image or wrong image
. i have to keep flipping between fastboot and hboot to try and read what it says . basically it goes for another 5 or 6 lines with no image or wrong image ..
tried re downloading rom.zip and renaming it againg . same srrors..
have you tried renaming "PB00IMG" without the zip?
you can also try flashing it as an RUU,wich eliminates the sd card,and the name of the file from the equation.
place rom.zip(for 1.51 hboot) into the folder containing fastboot and hboot..
-place the phone in fastboot.
-assuming you leave rom.zip named "rom.zip",open a cmd window and enter the following:
fastboot oem rebootRUU
fastboot flash zip rom.zip
it will do some stuff on the screen,then say "finished". then:
fastboot reboot-bootloader
thaT should boot you back into fastboot,where you should see 1.51.0000 locked hboot.
if you get a "failed" error instead of the above results,let us know what that error is and we can hopefully figure out what to do to make the flash work
if you get the 1.51 hboot,next step is to unlock it
highhacker said:
Well that was agood guess. The first step change rom.zip to PB00IMG.ZIP (I ASSUME THAT IS ZERO ZERO ) . it does somthing fast and i can see no image somthing like
Loading .....(PB00DIA0.zip)
no image
loading ......(PB00DIA3.zip)
no image
loading ......(PB00DIA2.ZIP)
no image or wrong image
. i have to keep flipping between fastboot and hboot to try and read what it says . basically it goes for another 5 or 6 lines with no image or wrong image ..
tried re downloading rom.zip and renaming it againg . same srrors..
Click to expand...
Click to collapse
The behavior you describe is EXACTLY how HBOOT mode behaves ... when there is no file named PB00IMG.zip on the root folder of the SD card. When I said "you will see something different happen", what I meant is something in addition to that list of file names rapidly scrolling by.
No doubt you are finding this frustrating.
In the past, there were two other reasons why this occurred:
1) People were using Windows Explorer on the PC. By default, it has an option turned on which is something like "hide file name extensions of known file types". With this (default) behavior, it is possible to rename the file PB00IMG.zip.zip, and yet what would be seen on-screen in Windows Explorer would only be "PB00IMG.zip". Turn that option off, or just use the DIR command from a command prompt to see if that is what happened.
2) Other users reported banging their heads into this without any luck, and then mysteriously solving the problem by formatting the SD card some other way than they previously had done. I don't have any further insight into the details here, other than this: the SD card should NOT be partitioned. If you got a box of phone which were previously rooted, it is possible you have a partitioned card (esp. if the phone had a 2.1 dev ROM on it)
The method scotty details above should allow you to side-step this problem, although you will have to get fastboot communicating with the phone (PC driver installs, etc).
To re-iterate though: if HBOOT discovers a file on the SD card named PB00IMG.zip, you will see something happen in addition to that list of file names rapidly scrolling by and disappearing. If you don't see anything additional - then HBOOT is not finding the file (for some reason or another).
bftb0
I am having an issue getting Amon recovery on my soft-bricked Eris.
I have the 1.51 bootloader unlocked but when I go to run the commands I get the following:
C:\adb>fastboot.exe flash zip recovery.zip
sending 'zip' (3817 KB)...
OKAY [ 0.827s]
writing 'zip'...
FAILED (remote: not allow)
finished. total time: 0.842s
If I try the RUU method it just sits at parsing:
C:\adb>fastboot oem rebootRUU
...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 2.980s]
finished. total time: 2.980s
C:\adb>fastboot flash zip recovery.zip
sending 'zip' (3817 KB)...
OKAY [ 0.842s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
Also running the RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed_with_driver.exe and replacing the rom.zip did not work or trying to flash Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP
The version it says I have it 2.42.0.0
Any ideas?
Thanks!
sorry it took me a couple days to reply to this. i believe the prollem your having is due to the android info document,specifically the hboot pre-update value. i had the same prollem starting in this post.
the android info i was using that was hanging at 'parsing' was:
Code:
ModelID: DESI****
ModelID: PB001****
ModelID: PB00100
CIDNUM: 11111111
CIDNUM: VZW__001
hbootpreupdate: 3
MainVer: 2.42.0.0
i pulled the one from the rom.zip extracted from the 1.51 hboot ruu and it worked fine.heres what it looked like:
Code:
CIDNUM:11111111
modelid: PB0010000
cidnum: VZW__001
cidnum: UTSI_001
mainver: 2.42.0.0
hbootpreupdate:12
try repacking your recovery with that android info,if its not what youre allready using.
zmanzbo,
What were the contents of the "recovery.zip" file you were trying to flash? (specifically, were there any .img files contained in it?)
Even when the 1.51.0000 bootloader is in the unlocked state, the flash will be disallowed if you have certain .img files in there (radio.img or recovery.img iirc - but don't quote me on that, I would need to go and re-read scotty's notes over in the AF thread).
Apologies for the vagueness - I'm afk at this time and am typing this from my phone.
bftb0
Well I got it working. I went to the link Scotty posted and downloaded tiny rescue recovery flashed that and then was able to run the various files listed in the original post bu bftb0. After that I was able to flash Eris_RootROM_v2.19.605.1_PB00IMG.zip. I am back in business now.
What was weird is that the contents of my recovery.zip were just the recovery.img and android-info.txt. The android-info.txt file had the same info as the 2nd one Scotty posted.
Thanks alot for the help here. Really appreciate it!
Cheers!
cool.
I'm glad you put the 1.49.2000 S-OFF bootloader on the phone afterward. It is always a good idea to have that bootloader (rather than the 1.51.0000 "unlockable" bootloader) installed, as the ways in which rescue/repair can be performed are more numerous (in case anything goes wrong in the future).
bftb0
So I've explored different options on XDA's site for returning to stock and I guess this is why I'm here. I screwed the hell up. I posted this on Phaded's How-To page, but I figured it would also be best to post this in the general Help & Troubleshooting page.
Here's the best way I can explain my issue. Someone please help.
1. My phone is COMPLETELY formatted. No OS now. Zero data.
2. TWRP is installed as my recovery.
3. I can fastboot and adb (only from the recovery obviously)
4. I moonshined the phone in order to S-Off
5. I tried the method to remove S-Off by Phaded
adb devices (verify device ID is listed)
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
exit
Click to expand...
Click to collapse
When I ran the RUU, I got that error 158 problem. I couldn't flash the HBOOT. downloaded it several times and tried.
6. I flashed it with an AOSP rom and tried the RUU again. No luck.
Now I'm stuck. u_u I tried
adb push "file name" "file directory"
Click to expand...
Click to collapse
so I can drop a zip file in the phone, but it seems to not work. Idk if I did it right. I was hoping to flash a ROM by doing that. smh.
Let me know if there's any other info I can provide. Considering the phone still turns on and I can still get to fastboot and adb, I don't think I'm a lost cause.
Thanks everyone!
UPDATE
I sideloaded a ROM (Carbon) and now I'm up and running. But I still can't RUU it! Figured this detail will help.
I'll keep reading and researching, posting my progress.
Thanks!
Its ok that your'e formatted the main concern would be 1. To be able to turn the phone on and 2. Boot into bootloader and recovery . It sounds like you are able to do both so the term "bricked" doesn't apply here.Okay so first obvious question did you obtain s-off also what bootloader are you on. Also what are you trying to achieve moving forward, going to stock or staying with custom roms, sense or aosp. There is only 1 ruu available for DNA and you need to be relocked to run and have fastboot drivers installed ala HTC sync manager.
Sent from my HTC6435LVW using Tapatalk 4 Beta
xlxcrossing said:
Its ok that your'e formatted the main concern would be 1. To be able to turn the phone on and 2. Boot into bootloader and recovery . It sounds like you are able to do both so the term "bricked" doesn't apply here.Okay so first obvious question did you obtain s-off also what bootloader are you on. Also what are you trying to achieve moving forward, going to stock or staying with custom roms, sense or aosp. There is only 1 ruu available for DNA and you need to be relocked to run and have fastboot drivers installed ala HTC sync manager.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
1. I obtained s-off with moonshine. I used the above command suggested by Phaded and when I put in
fastboot oem lock
Click to expand...
Click to collapse
(or something like that) it says my phone is locked.
2. What do you mean what bootloader? I guess moonshine, cause that's what comes up when I go to my bootloader screen.
3. I trying flashing the ruu and I get this (see image attached) which the suggested fix for error 158 was to flash the hboot 1.15 (or something). But I can't seem to flash it correctly. I can't even find straight forward instructions on how to do it.
Thanks for responding.
The reason I asked about the bootloader version and I'm not 100% sure about this so someone else may need to chime in is that when you ruu you are flashing firmware which includes hboot so if you upgraded hboot before doing s-off or otherwise went up a version then I'm pretty sure the ruu won't downgrade your hboot airgo the error message. Again this might not be true. At this point all that matters is that your s-off and NOT bricked so instead of toying with an ruu I would choose a stock Rom .zip to flash if its truly stock that you want. Your firmware should be up to date if you took 2.06. There is no ruu for 2.06.
Sent from my HTC6435LVW using Tapatalk 4 Beta
What is s-off?
Sent from my Galaxy Nexus using xda premium
93fuelslut said:
What is s-off?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It means you can write to any partition of your nand (internal memory). This means customs roms, kernels, splash screens, firmware, etc. When you are s-on it is more difficult, I can't get into why too many words it just is. If you're not s-off and you like flashing stuff look into it.
---------- Post added at 12:51 AM ---------- Previous post was at 12:41 AM ----------
xlxcrossing said:
It means you can write to any partition of your nand (internal memory). This means customs roms, kernels, splash screens, firmware, etc. When you are s-on it is more difficult, I can't get into why too many words it just is. If you're not s-off and you like flashing stuff look into it.
Click to expand...
Click to collapse
I'm not finding a solid explanation for error 158 which is disheartening - the best offerings are to change USB ports or restart the ruu. Like I said before you are fine on the software end, you can verify you have up to date firmware by comparing the latest below with what you have.
Baseband (radio) 1.01.04.0308
PRI 2.44_002
As for the hboot, how are you trying to flash it? In recovery?
The hboot needs to match the RUU. You need to find the original hboot . It is in a thread with hboot versions and radio versions.
Link to HBOOT please? and answering your questions
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was:
fastboot flash "file name.zip"
Click to expand...
Click to collapse
and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
ibthevivin said:
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was: and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
Click to expand...
Click to collapse
Moonshine isn't working because you are still s-off.
My thread has the original hboot and instructions to flash it. You do not flash in recovery. You do not put it on your phone at all. Do not push the file in recovery. Read and follow the instructions in the stock thread.
---------- Post added at 02:04 PM ---------- Previous post was at 02:02 PM ----------
You're doing the command wrong or you renamed it PL83IMG.zip.zip
Please, go in my thread, read each step perfectly and follow. It's really quite simple.
Difference
Is s-off/s-on and being locked/unlocked two different things?
Screenshot
Also here Phaded. I tried different variants of flashing the hboot. I renamed it from PL83IMG.zip to HBOOT.zip. It's not HBOOT.zip.zip cause I know Windows 8 automatically appends the end of the file name with the type extension. As you can see, I boot to fastboot, then run rebootRUU, then I'm trying to flash from there. I got frustrated and tried different things, even unpacking the .zip and trying to flash the .img file.
Thanks for your contribution to the community Phaded.
ibthevivin said:
Could someone provide a link for the hboot instructions and flashing?
I think my problem is that moonshine screwed up my phone. I relocked my phone, but when trying to run moonshine again, it doesn't unlock the phone. It just says "WTF: What are you dong" and then it just stops and tells me to hit Enter to exit and the phone is still locked, hence why I think I can't flash HBOOT.
I try and flash HBOOT through recovery. I tried doing fastboot to flash it. Recalling from memory, I think the command was: and then it says it can't open the file, unknown error. But I can't find any help guides or how-to's that explain the fix for this.
Thanks! Keep asking questions, cause I don't know what info is relevant.
Click to expand...
Click to collapse
Strike.
From my S-Off BadSeed DNA
ibthevivin said:
Also here Phaded. I tried different variants of flashing the hboot. I renamed it from PL83IMG.zip to HBOOT.zip. It's not HBOOT.zip.zip cause I know Windows 8 automatically appends the end of the file name with the type extension. As you can see, I boot to fastboot, then run rebootRUU, then I'm trying to flash from there. I got frustrated and tried different things, even unpacking the .zip and trying to flash the .img file.
Thanks for your contribution to the community Phaded.
Click to expand...
Click to collapse
You need to cd to the directory the file is in, which should be where fastboot.exe is
So if it's in say C:\sdk\
Type cd C:\sdk\
Then run command to fastboot
BOOM!
Alright. Worked. I'll keep you all posted. No one really mentioned in any of the tutorials and how-to's that it is VERY important to make sure to CD to the directory. Like there are developers who say just add it to the PATH in Environment Variables. I figured it was enough, but hey, I was wrong.
Live and learn right?
Thank you Phaded.
So basically my problem was, calling the hboot.zip file is not included under Environmental Variables. I have to intentionally CD to that directory.
Hmm, I must have missed putting in the cd step for the hboot. I'll go edit it.