Root PB00IMG.zip loading question

[crandroid]

Hey everyone, I'm new to the forums and rooting. I researched the whole rooting process and decided to try it, but I've run into some trouble while flashing PB00IMG.zip.

I put it on my SD card and put the phone into HBOOT. It went through and found it, and then told me to press volume up to continue with the update. Then it went through the same thing, only now it is taking forever to finish loading. I know that it's a large file, but it's been almost an hour and the blue bar is only about 2/3 full. What should I do?

Thanks in advance.

 

[erisuser1]

Hey everyone, I'm new to the forums and rooting. I researched the whole rooting process and decided to try it, but I've run into some trouble while flashing PB00IMG.zip.

I put it on my SD card and put the phone into HBOOT. It went through and found it, and then told me to press volume up to continue with the update. Then it went through the same thing, only now it is taking forever to finish loading. I know that it's a large file, but it's been almost an hour and the blue bar is only about 2/3 full. What should I do?

Thanks in advance.

OK. Blue Bar at EXACTLY WHAT STEP?

Please refer to a picture or step number in this post to make things clear.

Also - please report the TOP TWO LINES in the display (which is currently "stuck") in "blue bar" mode. Specifically I am interested in hearing whether you see "S-ON" or "S-OFF" in the top line, and also what HBOOT Version number you see (all digits, please).

eu1

Edit: It sounds like the step you are experiencing is during the 2nd checking step, not during flashing (that would be a red bar). That's good news, if that is the case.

 

[erisuser1]

PS: It is my impression that the phone does not charge when it is in HBOOT or FASTBOOT mode - it actually discharges, even if plugged in via a USB cable.

Do not attempt to re-flash the phone again until it is 100% charged. (You can charge the phone with it completely off; that will charge it the fastest).

eu1

 

[crandroid]

Thanks for your response.

I'm pretty sure it's the second time too. It looks like the 4th picture in your post that you linked too.

It also said S-OFF, and the HBOOT is 1.49. I think that's a good sign, I was just getting really worried because it was taking so long. Everything I've read says that it should take 5-15 minutes or so, not over an hour. I actually did a battery pull (probably really stupid of me) because I was freaking that this thing was bricked. My phone seems fine now, though (although it's still not rooted).

So you're saying I should charge my phone 100% and then try again?

 

[crandroid]

Just to make it clearer, the third screen in that thread came up. As soon as I pushed Vol up, it went black for a second and then screen #4 came up. I didn't even see any of the other screens, I suppose it's possible they were only there for a short moment.

Thanks again.

 

[erisuser1]

Thanks for your response.

I'm pretty sure it's the second time too. It looks like the 4th picture in your post that you linked too.

It also said S-OFF, and the HBOOT is 1.49. I think that's a good sign, I was just getting really worried because it was taking so long. Everything I've read says that it should take 5-15 minutes or so, not over an hour. I actually did a battery pull (probably really stupid of me) because I was freaking that this thing was bricked. My phone seems fine now, though (although it's still not rooted).

So you're saying I should charge my phone 100% and then try again?

OK, here's the good news: The most important part of the rooting process on your phone has been completed. That is exactly what happens in the 0.25 seconds right after you press the Vol-Up key and just before the screen goes black.

If the phone got stuck here:

, then it was unpacking the Zip file that had already been transferred to the phone's internal memory.

That makes me very nervous, frankly, because it means that the phone glitched when acting completely independently from the outside world.

But, it also means that you have a completely functional phone right now, just as if you had done the "battery pull" trick: your old OS is still there, and you can boot to it, even though you replaced your bootloader with the "God Mode" ("S-OFF") root bootloader.

So, I am torn, quite frankly, about telling you to continue to root. The problem you experienced might have happened if you were trying to root the phone in a partially discharged state... but it could have happened for a variety of other reasons, too.

Do you remember what % the battery was charged to before you put it in to HBOOT mode to try the rooting?

eu1


PS - The step your phone got stuck at (unpacking the Zip the 2nd time) normally takes a little bit longer than one minute. When other people talk about 5-15 minutes, they are talking about after the phone boots for the first time with the new OS - that part can take quite a long time, but the actual flashing of the phone only takes a couple minutes in total, and you see all the remainder of the shots from that other post (#5 - #9) within a few minutes.

 

[crandroid]

Do you remember what % the battery was charged to before you put it in to HBOOT mode to try the rooting?

I'm not exactly sure, but I'd estimate 50-60%.

I'll probably let it charge overnight and maybe try again in the morning (unless, of course, you think that would be a bad idea.)

 

[erisuser1]

I'm not exactly sure, but I'd estimate 50-60%.

I'll probably let it charge overnight and maybe try again in the morning (unless, of course, you think that would be a bad idea.)

Well, reading or writing to flash memory with too small a supply voltage is a very common way for memory corruption to occur - either during writing or reading. When you run the RUU procedure, for instance, it will refuse to do the flashing if your battery capacity is below 40%; I don't honestly know if the HBOOT checks the battery. I don't know how well HTC has quantified that number, but you are clearly getting close to the ragged edge. I try to never flash anything on the phone unless I am 90% or better just because I am paranoid about it.

Like I said, the way the error occurred for you - after the file had passed it's initial crypto check (so we know the file is good) - suggests something internal to the phone. That could have been a low battery condition, especially if you let the phone sit there at that prompt ("Do you want to start update?"), because the battery drains rapidly in HBOOT mode.

But the honest answer that I can give you is I don't know. I can't give you any assurances. It might be fine with a better battery charge, and it might not.

Note that the failure occurs while checking the ROM file the second time; no flashing occurs to your existing OS until the file has been thoroughly checked out. So, if it fails again a 2nd time at exactly the same place, then no harm, no foul. But, what can't be guaranteed is that your phone has something flaky going on that might make the actual flashing process fail. (Note that flashing the bootloader succeeded - but it's only 512 KB in size, and you need to flash nearly 200 MB of ROM.)

Bottom line - it's up to you. At the moment you have a working phone... (and are ever so close to having root).

eu1

 

[crandroid]

Damn. Well thanks for the help. I'll think about it.

 

[erisuser1]

Damn. Well thanks for the help. I'll think about it.

Let me know what you end up doing. My gut instinct (I've designed systems with flash memory, BTW) is that your problem is "probably" just a poorly charged battery.

OTOH, it costs me nothing to encourage you to "go ahead and run the experiment", where it could cost you a phone if things go wrong. That's why you need to be the person that makes the call.

eu1

 

[crandroid]

Let me know what you end up doing. My gut instinct (I've designed systems with flash memory, BTW) is that your problem is "probably" just a poorly charged battery.

OTOH, it costs me nothing to encourage you to "go ahead and run the experiment", where it could cost you a phone if things go wrong. That's why you need to be the person that makes the call.

eu1

Well, I took the plunge and tried with the new battery. I believe it worked, it's unzipping everything now. I'll let you know if I hit any other snags.

I think I'm going to go with Evil Eris 1.0 w/ OC.

 

[scary alien]

Well, I took the plunge and tried with the new battery. I believe it worked, it's unzipping everything now. I'll let you know if I hit any other snags.

I think I'm going to go with Evil Eris 1.0 w/ OC.

crandroid, congratulations! You certainly had the right guy (erisuser1) helping you last night. Glad it all worked out. Kudos!

 

[Frisco]

crandroid, congratulations! You certainly had the right guy (erisuser1) helping you last night. Glad it all worked out. Kudos!

+1

That link he put up to the thread with the error examples in it is another instance of how thorough Erisuser1 is.

 

[crandroid]

Thanks, I'm glad it worked too, but I've run into another problem.

I've almost installed Amon's recovery image, but I keep getting errors on the last line of code. When I enter "adb shell flash_image recovery /sdcard/recovery.img" into the command prompt, I get a bunch of errors ending in (Out of Memory), with the last error saying "error writing recovery: No space left on device".

All of the other steps went fine. I tried re-unzipping the file to the tools directory with no luck. Any suggestions?

UPDATE: I rebooted my phone and tried again, and didn't get any errors. I'm almost done!

 

[scary alien]

Thanks, I'm glad it worked too, but I've run into another problem.

I've almost installed Amon's recovery image, but I keep getting errors on the last line of code. When I enter "adb shell flash_image recovery /sdcard/recovery.img" into the command prompt, I get a bunch of errors ending in (Out of Memory), with the last error saying "error writing recovery: No space left on device".

All of the other steps went fine. I tried re-unzipping the file to the tools directory with no luck. Any suggestions?

UPDATE: I rebooted my phone and tried again, and didn't get any errors. I'm almost done!

crandroid, you were too fast . I've seen (and re-searched) posts reporting the same error that you did at the same spot. Suggested solutions were to wait a few minutes between commands and try it again and/or to reboot the device (which does impose a delay, eh?). Glad you got through it... Good luck!

 

[crandroid]

Thanks again, everyone! I'm rooted and running Evil Eris 1.0 w/ OC! You've all been a huge help. Special thanks to erisuser1. Now, to see what this phone can really do. Unfortunately, my sister is getting married today, so I might have to put some of that part off, haha.

 

[Frisco]

Yes, it is not enough to follow the directions; with this stuff it is best to take it in baby steps, going slowly and carefully.

My dear granny used to always say, "the most worthwhile things in life are done slowly."

She and grampa were happy souls, they were.

 

[crandroid]

Any recommendations for SetCPU? Right now I have it at the default 19/710, with the max down to 480 when my battery gets low or above 50 degrees C.

 

[scary alien]

Any recommendations for SetCPU? Right now I have it at the default 19/710, with the max down to 480 when my battery gets low or above 50 degrees C.

I've got 710 / 122 for my main settings. Sleep/standby is 480 / 245. Failsafe is 245 / 245 at 43 degrees.

 

[ACD168]

I run normal profile max-768/min-245.... sleep max-245/min-245