yashsingh1/xdaforums huggingface dataset:
[Droid Eris Q&A, Help & Troubleshooting] obonilla30:
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????
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
@obonilla30

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"?
[Droid Eris Q&A, Help & Troubleshooting] highhacker:
S###

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:)
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
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
[Droid Eris Q&A, Help & Troubleshooting] scotty1223:
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" :eek: 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.
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
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.
[Droid Eris Q&A, Help & Troubleshooting] highhacker:
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..
[Droid Eris Q&A, Help & Troubleshooting] scotty1223:
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 :)
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
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
[Droid Eris Q&A, Help & Troubleshooting] zmanzbo:
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!
[Droid Eris Q&A, Help & Troubleshooting] scotty1223:
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:

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:

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.
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
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
[Droid Eris Q&A, Help & Troubleshooting] zmanzbo:
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!
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
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
[Droid Eris Q&A, Help & Troubleshooting] scotty1223:
awsome! im glad we were able to help you :cool:
[Droid Eris Q&A, Help & Troubleshooting] scary alien:
Awesome! Happy to have helped for my small part.

(and this get's me subscribed in a proper way so I can keep an eye on this thread, too :) ;)).

Cheers!
[Droid Eris Q&A, Help & Troubleshooting] lan005:
A problem

After I Flash the new Custom Recovery, I still cant boot into the custom Ra Recovery, when I try to go into it appears the loop of the 3 Android Skaters and a short while after that a reboot, can anyone help me? :(
[Droid Eris Q&A, Help & Troubleshooting] highhacker:
MY ERIS'S

Ok i am stuck again . to recapp and start on these eris AGAIN , I got the first step done Finally by reformatting on another compuert the sd card to FAT32 . Then is was able to flash the 1.51.0000 "locked" bootloader . from there is the problem cause every time i sign in to HTC to unlock the loader is tells me to download the PB0010000_DesireC_VERIZON_WWE_hboot_1.51.0000.exe which i have and have tried to run even though you said it was not nessasary being i have already did that step and it craps out showing phone is not plugged in , IS the phone supposed to be in any certin state like OFF or in hboot or fastboot or what ? Also i guess i am SOL cause when i try to got to the next step it just logs me out and then back to logong in and selecting the eris and then the first steop again . if i select continue it logs me out . i csnt get to the next step so i am locked wirth 1.51.0000 still .

EDIT . ok got to step where i have the three files and do windows cdm and type fastboot oem get_identifier_token but i get the response C:\adb>fastboot oem get_identifier_token

... FAILED (command write failed (Unknown error))

finished. total time: 0.719s

i tried to pull battery and then got : C:\adb>fastboot oem get_identifier_token

... FAILED (status read failed (Too many links))

finished. total time: 0.000s

so any ideas . ?
[Droid Eris Q&A, Help & Troubleshooting] scotty1223:
are you using the "fastboot flash" command to flash the recovery? and not getting errors? how are you trying to boot to recovery? does your phone boot fully? your post makes it appear so.

do you get a reply from "fastboot devices"? have you installed drivers? you may want to follow these directions,so youll ahve adb and an md5 sums utility as well,from post 4:

after that,you need drivers. some suggest htc sync,and if youve done that,and get your serial number back from "fastboot devices" then youre fine. if not i might suggest using these modified htc drivers from revolutionary

dont worry,youre not SOL yet :)
[Droid Eris Q&A, Help & Troubleshooting] lan005:
Answer

First, yes Im using "fastboot flash zip zipfilename.zip" command to flash the recovery and I dont get any error. Im trying to boot the recovery pressing Vol up + power, but when I do that is stuck on the screen of the Android skaters. I should try to flash another recovery like ClockworkMod?:confused:
[Droid Eris Q&A, Help & Troubleshooting] scotty1223:
ok,if youve got a good recovery image packed up,and and it flashes with no error,yet you still cant get to it,i think its time to try flashing the tiny rescue recovery that mister scary alien has come up with.

refer to this post: http://androidforums.com/eris-all-t...loader-unlock-support-yawn-2.html#post3992372

download the eris rescue recovery,and flash as an ruu as you have been. after the ruu finishes, fastboot reboot should take you to recovery(its actually flashing in the boot partition). at this time,you can flash the ErisMiscReset_v0.9.zip file,and continue on with the directions in the OP. pick up the directions here:

- 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)

holler if you have questions :)
[Droid Eris Q&A, Help & Troubleshooting] lan005:
mmmm maybe I doing something bad...

Bad post xd
[Droid Eris Q&A, Help & Troubleshooting] lan005:
Another issue

Ok look what I Do.

1. I download the recovery Image

2. Renamed "boot", then I packed it up with the android info document from the original "rom.zip" for the 1.51 hboot

3. Installed it as an RUU in fastboot

4. Then I put fastboot reboot and it simply keeps bootlooping

I have a Screenshot of the CMD and the android info doc of the rom.zip that I put in the boot.zip, but since I new cant post a link xD

​
[Droid Eris Q&A, Help & Troubleshooting] scotty1223:
what recovery image did you download?

if you use this link: http://www.mediafire.com/?31e9m1shu5lw0s7 (from the post i linked above) you dont need to repack or rename anything. just flash as an ruu.

if you downloaded a regular recovery image and tried to rename it to boot,that is prolly why its bootlooping,as its too large to fit the boot partition :eek: scary alien had to make a special image that fit the partion size,so try it again with the tiny rescue recovery. :)
[Droid Eris Q&A, Help & Troubleshooting] lan005:
Not work

beforehand Thanks for the Help, I really appreciate it...

Well I Flash that tiny recovery over 10 time but when I try to reboot, Its going to looping arround again :( Look what I the CMD Log

C:\mini-adb>fastboot oem rebootRUU

... OKAY [ 0.029s]

finished. total time: 0.029s

C:\mini-adb>fastboot erase cache

< waiting for device >

erasing 'cache'... OKAY [ 3.018s]

finished. total time: 3.019s

C:\mini-adb>fastboot flash zip PB00IMG-rescue-recovery.zip

sending 'zip' (2523 KB)... OKAY [ 3.375s]

writing 'zip'... INFOzip header checking...

INFOzip info parsing...

INFOchecking model ID...

INFOchecking custom ID...

INFOchecking main version...

INFOstart image[boot] unzipping & flushing...

INFO[RUU]UZ,boot,0

INFO[RUU]UZ,boot,42

INFO[RUU]UZ,boot,94

INFO[RUU]UZ,boot,100

INFO[RUU]WP,boot,0

INFO[RUU]WP,boot,40

INFO[RUU]WP,boot,80

INFO[RUU]WP,boot,100

OKAY [ 2.153s]

finished. total time: 5.529s

C:\mini-adb>fastboot oem rebootRUU

... OKAY [ 0.029s]

finished. total time: 0.029s

Any other Idea :confused:
[Droid Eris Q&A, Help & Troubleshooting] scotty1223:
at the end,have you tried simply "fastboot reboot" ? the command your entering above is putting the phone back into fastboot ruu mode,wich may be casueing issue.

also,you can pull the battery for a few seconds,then just turn the phone on normally. since the recovery is in the boot partition,just turning the phone on should launch the rescue recovery... no button combos or commands,just plain old fashioned push the power button :)
[Droid Eris Q&A, Help & Troubleshooting] lan005:
Yes I Do it but not work

at the end, I put the command "Fastboot reboot" but nothing happens it keep looping, after that I pull the battery for a few seconds and nothing happens again.
[Droid Eris Q&A, Help & Troubleshooting] scotty1223:
i assume that this meand that your boot partition has some bad blocks in it as well,preventing the rescue recovery from booting.

i am,unfortunately about out of ideas... i will ponder it today,and the reread everything later.

maybe eu1 has some other ideas...
[Droid Eris Q&A, Help & Troubleshooting] doogald:
Can the phone boot into HBOOT by holding VolDn? If so, does it get to Recovery by pressing VolUp when prompted in HBOOT?

If not, I suppose it would not hurt to try fastboot flash zip recovery.zip one more time with the attached recovery.zip, to see if you can get Amon_RA Recovery (using either booth with VolUp, which you said a few posts ago, or the method I list above.) I have tried the attached recovery.zip with my phone and it flashed Amon_RA just fine.

Hoping this works, from there you can try flashing ErisMTDNuke (I think we can assume that there are bad blocks without running the report first. The phone is borked anyway.)

(MD5 of recovery.zip is 89b4aac3a92b46d288f6ddbb95c88965)
[Droid Eris Q&A, Help & Troubleshooting] lan005:
What Happens?

What Happens if I use fastboot erase recovery and then I flash a new recovry?

Im trying to use fastboot oem partition_test recovery [1] to get the errors of the partition but he throws me this

... INFO[ERR] Command error !!!

OKAY [ 0.010s]

finished. total time: 0.011s
[Droid Eris Q&A, Help & Troubleshooting] ZionCorps:
Oooh, my gosh. I would like to say that this very thread is the reason for my migration over to xda-developers.

Thank you so much for making this happen, especially bftb0. And scotty1223 as well, because there are a few times when replies to another problem helped me out too. x3

Overall this was an.. Easy fix, actually. I had a little trouble at first with my phone not really wanting to whatever I renamed to PB00IMG, but I did a complete reformat of the card and started over. I also had problems running the Bootload Unlocker from HTCdevs.com between both Firefox and Chrome; for some reason it liked Explorer 9 the best.

Just a little patience is the key to a beautifully working little device<3
[Droid Eris Q&A, Help & Troubleshooting] scotty1223:
awsome! im sure i speak for bftb0 as well when i say im glad you got it going :cool:
[Droid Eris Q&A, Help & Troubleshooting] parkouras:
hey guys, i have big trouble with my Chinese android and im hoping very much that u can help me. I ha a HDC galaxy s2 A9100D and yesterday i have rooted my phone , i did it successfully and everything went just perfect, until i decided to download ROM manager so i downloaded it and went to system recovery through the app and accidentally pressed wipe cache partition it just sayd that i did it successfully so i thought like whatever and i think i did a wrong thing i reboot my android and after that i had stuck on start-up with writing "ANDROID" i have so freaked out now i don't know what to do. i had kept over all night by trying to turn on but when i woke up i found it just as left its still stuck. and i don't have any shortcuts to access my system recovery again. i have screwed everything up. sorry for my bad English :P. so if someone could help me i would be very thankful. please someone help me out to fix this problem :crying::crying::eek::(:(
[Droid Eris Q&A, Help & Troubleshooting] tobiascrystal:
First, wiping the cache partition should not cause any real problems as most of the stuff that I know is in there can be regenerated by just a restart. You may try pulling your battery and letting it try to restarting again.

Second, you are in the Droid Eris forum so most of the people here are probably not going to be able to give you phone specific help like how you access your recovery to attempt a reflash which would be your next step.