Develop Bugs

Updated radio issue - phone not booting

I had success with the unrevoked root, so I decided to give the 2.2 upgrade a shot. I successfully reverted to a fresh stock unrooted 2.1, using the PB31IMG.zip file. This also took away my Clockwork Mod. Next I moved to the step of loading the dinc_ota.zip. After the 3 cycles it went to the HTC incredible boot screen and didnt move. I waited 15 minutes and nothing changed. I decided to pull the battery but no luck, still hangs on the white screen when i turn the phone on. I can still get into HBoot, which shows my radio as the updated 2.05 and my hboot is .79.
I've tried the RUU but I cannot boot the phone past the white htc screen so it wont work. I've also tried to load the PB31IMG.zip file from the sdcard agian, which doesnt. I get an error saying its too old.
Is there a way to restore my phone from Hboot?
Do you have any suggestions of threads I could read for the answer?
Thanks

Try the image again, then try the ota.
Sent from my ADR6300 using XDA App

i would not try the radio update again, that's pretty much a sure fire way to brick. I would wait for the opinions of others first.
PB31IMG.zip doesn't roll the radio back does it? It reverts to stock recovery and ROM, but does it roll the radio back too?
I thought you had to follows this to roll the radio back, http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html

k_flan said:
i would not try the radio update again, that's pretty much a sure fire way to brick. I would wait for the opinions of others first.
PB31IMG.zip doesn't roll the radio back does it? It reverts to stock recovery and ROM, but does it roll the radio back too?
I thought you had to follows this to roll the radio back, http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
Click to expand...
Click to collapse
Sorry, my bad. DONT APPLY THE UPDATE AGAIN!
Sent from my ADR6300 using XDA App

Try a clear storage.

jdkoreclipse said:
Try the image again, then try the ota.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I tried the image again, same error, it reads:
Main Version is older!
Update Fail!
Do you want to reboot device?
vol up yes
vol down no
I tried the reboot and it still hangs at white screen.
k_flan said:
i would not try the radio update again, that's pretty much a sure fire way to brick. I would wait for the opinions of others first.
PB31IMG.zip doesn't roll the radio back does it? It reverts to stock recovery and ROM, but does it roll the radio back too?
I thought you had to follows this to roll the radio back, http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
Click to expand...
Click to collapse
As for the radio update, I agree that it would be a bad idea to try to reaplly it, especially since my HBoot shows it as the updated radio.
I also saw the thread you pointed out to me but that requires clockwork mod to be installed and that was removed when i reverted to stock.
Any helpful ideas are greatly appreciated.

Does it show up on adb?
Sent from my ADR6300 using XDA App

jdkoreclipse said:
Does it show up on adb?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I did try to clear the storage, but it still hangs.
Also tried adb devices in hboot, at the htc incredible white screen, and in the fastboot menu, all with no luck. When I try to boot to recovery it hangs at the same white screen. Might just have to bring it to Verizon tomorrow, I'm beginning to think I may be holding a brick.

To revert your radio back to the original 1.x, you need to have access to adb and pushing to your data directory
Long story short, you dun goofed by pulling the battery
HTC Incredible, rooted w/ modified Sense 2.1

I think its a brick
Sent from my ADR6300 using XDA App

ilinfinityil said:
To revert your radio back to the original 1.x, you need to have access to adb and pushing to your data directory
Long story short, you dun goofed by pulling the battery
HTC Incredible, rooted w/ modified Sense 2.1
Click to expand...
Click to collapse
Once the radio update completed, the white htc inc screen came up and hung there for 15 minutes, I didnt think I had much of a choice.
In that situation what should I have done?

aaman137 said:
Once the radio update completed, the white htc inc screen came up and hung there for 15 minutes, I didnt think I had much of a choice.
In that situation what should I have done?
Click to expand...
Click to collapse
When i did the ota, it took about 7-10 min total. Yours hung on that incredible boot screen for 15 min. You did the right thing.
Sent from my ADR6300 using XDA App

I appreciate all the help, this is why I came to xda. As for my Incredible, I guess its going back to Verizon tomorrow to see what they can do for me. I'm sure I'll be waiting a good week or two until I have my Incredible back, DOH!

I wouldn't think it's bricked if you can still get into the bootloader. Bricked generally comes about when you can't even power the device on. While I have nothing to add in the way of help, I'd say don't give up on the phone yet. I'm betting one of the *real* devs may be able to help you.

Ruoh said:
I wouldn't think it's bricked if you can still get into the bootloader. Bricked generally comes about when you can't even power the device on. While I have nothing to add in the way of help, I'd say don't give up on the phone yet. I'm betting one of the *real* devs may be able to help you.
Click to expand...
Click to collapse
It may be a soft brick.
Sent from my ADR6300 using XDA App

i brick it this morning, called around dinner time, and they dispatched a replacement to me. overnight free shipping!!!

Its not bricked. I had the same issue. You need to follow this guide. Basically you have to redo it to get it to work, and this is the only way that I could do it.
http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
(This was the most important part of the guide for me. Solve that: error saying its too old. All glory to Adrynalyne)
Having troubles with the RUU giving connection errors? Do this.
Go to start, and in the search/run box, type
%temp%
Delete all that you can. Make sure the RUU is not running in the background.
Now run the RUU again. Once it starts to the first screen, it has extracted the files to the temp directory. You can then copy them to a safe place. It will be a long winded numbered folder, with a similar subfolder.
Once you have copied it to a safe place, you can then copy adb.exe, fastboot.exe, and adbwinapi.dll from the latest SDK into it, overwriting the older copies. Then start the RUU by executing ARUWizard.exe. This fixed the problem for me.
You can also rename the rom.zip contained within the extracted files to PB31IMG.zip and put it on your sd card. Booting to HBOOT will scan it and offer to install.

HolyGrail said:
Its not bricked. I had the same issue. You need to follow this guide. Basically you have to redo it to get it to work, and this is the only way that I could do it.
http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
(This was the most important part of the guide for me. Solve that: error saying its too old. All glory to Adrynalyne)
Having troubles with the RUU giving connection errors? Do this.
Go to start, and in the search/run box, type
%temp%
Delete all that you can. Make sure the RUU is not running in the background.
Now run the RUU again. Once it starts to the first screen, it has extracted the files to the temp directory. You can then copy them to a safe place. It will be a long winded numbered folder, with a similar subfolder.
Once you have copied it to a safe place, you can then copy adb.exe, fastboot.exe, and adbwinapi.dll from the latest SDK into it, overwriting the older copies. Then start the RUU by executing ARUWizard.exe. This fixed the problem for me.
You can also rename the rom.zip contained within the extracted files to PB31IMG.zip and put it on your sd card. Booting to HBOOT will scan it and offer to install.
Click to expand...
Click to collapse
This only works if he can get to recovery.

TNS201 said:
This only works if he can get to recovery.
Click to expand...
Click to collapse
Your point? He can get into stock recovery, which is all he needs to start over.

HolyGrail said:
Your point? He can get into stock recovery, which is all he needs to start over.
Click to expand...
Click to collapse
His tutorial says you need clockwork, so he might not be ok. You need the ability to push files to your data directory which is why he needs clockwork, unless he can do it the old way when we first got root by the time attack method. I do not know how much functionality adb would have if he was able to access ADB with stock recovery.
This is all his fault for his failure to read. From what I read in the OP, he did this
1. He downgraded with the RUU image.
2. He tried to apply the OTA
He failed to do this or at least didn't acknowledge that he did this, but he didn't install the original OTA which you will get after you RUU back to stock. If you boot your phone back up it should download the OTA from VZW and then you apply the leaked OTA. So sounds like this is the reason for his brick/semi-brick. Failure to read or understand what youre doing leads to FAIL>

major problem. Need some help. Loopbooting

So I'm at work and go to look at my phone and notice its rebooting which it never does. I watch it and notice its loopbooting at the white Evo screen. Ive never as much as had a random reboot before. I try to boot into recovery and can get to hboot but as soon as I try to select recovery it loop boots at the same point. I tried pulling the battery and that didn't help either. I'm running cm6.1 rc1 with stock kernel and no over or under clocking. I haven't made any changes in a while. Not even any new apps.
Any ideas?

I just went through and read every thread with loop in the title and it seems like with everyone else they had this issue while rooting or flashing or making some sort of change. Nor just on an idle phone

You may need to RUU your phone and start over if you arent able to get into any type of recovery mode...
Sent from my froyo using the xda app

I can get into hboot but that's about it

Just got home finally.. Gonna try to get this bs fixed. I wish I knew what caused it. I can't have this randomly happening again.

I was able to run RUU app and install the update from here;
http://forum.xda-developers.com/showthread.php?t=747319
It just finished and I'm still in a boot loop. Ugh.
I've been searching for hours now and I'm not finding much help

Ugh.. I'm giving up for the night. Been searching for hours and can't find anything that seems to work. And of course today is Thanksgiving and there's no chance of me even getting a new phone.

did you try a 3.29 ruu i'm surprised that sync let you flash a 3.26 if your phone updated to newer that might help also if you used unrevoked you need to flash thier s-on tool

Jbcarrera said:
did you try a 3.29 ruu i'm surprised that sync let you flash a 3.26 if your phone updated to newer that might help also if you used unrevoked you need to flash thier s-on tool
Click to expand...
Click to collapse
The only RUU I was able to flash with the RUU app was the 3.26 one I posted. I downloaded like 10 others and RUU app doesn't see them for some reason.
Also, how can I send a file to the phone with fastboot? I've searched and searched and I'm not sure of the exact syntax to use.
I had S-OFF and was fully rooted untill I ran RUU app.

Any other suggestions? I'm really trying to avoid getting a new phone.

Grabbed a card reader and adapter and trying some other RUU's I found now.. Hopefully something works.

thenags said:
Grabbed a card reader and adapter and trying some other RUU's I found now.. Hopefully something works.
Click to expand...
Click to collapse
i was going to suggest that but you beat me to it have been away all day

thenags said:
Any other suggestions? I'm really trying to avoid getting a new phone.
Click to expand...
Click to collapse
Jbcarrera said:
i was going to suggest that but you beat me to it have been away all day
Click to expand...
Click to collapse
Right now I'm just downloading another RUU to use with RUUApp. Do you have any other suggestions if this doesn't work?
Attempting the .exe found here;
http://forum.xda-developers.com/showthread.php?t=819771&highlight=mirror&page=3

thenags said:
Right now I'm just downloading another RUU to use with RUUApp. Do you have any other suggestions if this doesn't work?
Attempting the .exe found here;
http://forum.xda-developers.com/showthread.php?t=819771&highlight=mirror&page=3
Click to expand...
Click to collapse
Just finished installing that RUU and no change. Still the same boot loop.

Downloading the following RUU now and going to try again.
RUU_SuperSonic_S_Sprint_WWE_3.30.651.3_Radio_2.15.00.09.01_NV_1.77_003_release_157088_signed.exe
And for anyone looking for stock RUU's and having a hell of a time. Here's a good link I found with a bunch of them;
http://shipped-roms.com/shipped/Supersonic/

That one didn't work either.. Still just loop booting. Looks like this thing is just completely eff'd and I need a new one. Damn.

Well, just got home with a brand new phone. It's got hboot 2.20.. Time to get rooting. Ugh.

Just search for a pc3600.img file that is rooted and put on sd and boot to bootloader and flash
sent from my white w/ red trim Evo

krazydude4g said:
Just search for a pc3600.img file that is rooted and put on sd and boot to bootloader and flash
sent from my white w/ red trim Evo
Click to expand...
Click to collapse
I did that as well.. Nothing was working on that thing. Got a new phone now and just finished rooting it and getting it all set up.

Problem with free mytouch slide i got.

so a friend of mine basically gave me this mytouch and i have no idea whats wrong with it and how to fix it.
i have some pictures attached below.
it boots up, then when im on the lockscreen and slide down, i get a force close and the my touch logo....then it reboots its self.
please help.
thanks

dapoharoun said:
so a friend of mine basically gave me this mytouch and i have no idea whats wrong with it and how to fix it.
i have some pictures attached below.
it boots up, then when im on the lockscreen and slide down, i get a force close and the my touch logo....then it reboots its self.
please help.
thanks
Click to expand...
Click to collapse
This happened to me when I deleted some widgets that Sense was using, but I was getting an HTC Sense force close. Not this. Are you rooted? If you don't know, download clockworkmod recovery for the slide and put it on the root of your SD card as update.zip and flash it via recovery. (you get to recovery through the bootloader, selecting recovery with the volume down key, and the power key to select it), and if it gives you a signature verification failure, then you are not rooted. If it succeeds, then flash CR_Mod OTA 1.35.xxx (forgot the exact number, it's in the dev section), and that should fix your problem.

MusicMan374 said:
This happened to me when I deleted some widgets that Sense was using, but I was getting an HTC Sense force close. Not this. Are you rooted? If you don't know, download clockworkmod recovery for the slide and put it on the root of your SD card as update.zip and flash it via recovery. (you get to recovery through the bootloader, selecting recovery with the volume down key, and the power key to select it), and if it gives you a signature verification failure, then you are not rooted. If it succeeds, then flash CR_Mod OTA 1.35.xxx (forgot the exact number, it's in the dev section), and that should fix your problem.
Click to expand...
Click to collapse
thanks for the reply sir.
i am about to try that now, just have no clue where to download clockwork recovery from. is there a specific one for just the mytouch?
thanks

dapoharoun said:
thanks for the reply sir.
i am about to try that now, just have no clue where to download clockwork recovery from. is there a specific one for just the mytouch?
thanks
Click to expand...
Click to collapse
Yeah, I attached the file you need, seems the clockwork site is temporarily down.

MusicMan374 said:
Yeah, I attached the file you need, seems the clockwork site is temporarily down.
Click to expand...
Click to collapse
ok so im not rooted, because i got a verification error. picture attached below.
whats next sir?

dapoharoun said:
ok so im not rooted, because i got a verification error. picture attached below.
whats next sir?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=754020
Follow that guide to root your phone, and then flash this: http://forum.xda-developers.com/showthread.php?t=747002
That will give you rooted stock as well as re-update your radio, since rooting downgrades your radio image. Let me know how that all goes

MusicMan374 said:
http://forum.xda-developers.com/showthread.php?t=754020
Follow that guide to root your phone, and then flash this: http://forum.xda-developers.com/showthread.php?t=747002
That will give you rooted stock as well as re-update your radio, since rooting downgrades your radio image. Let me know how that all goes
Click to expand...
Click to collapse
will try, but is it possible to root the phone when it wont turn on?

Any body?
please

dapoharoun said:
will try, but is it possible to root the phone when it wont turn on?
Click to expand...
Click to collapse
No, not that I know of
Sent from my T-Mobile myTouch 3G Slide

so if this beautiful phone broken for good!?!?!?

bump.......

dapoharoun said:
ok so im not rooted, because i got a verification error. picture attached below.
whats next sir?
Click to expand...
Click to collapse
Try the wipe data/factory reset option

agentg1001 said:
Try the wipe data/factory reset option
Click to expand...
Click to collapse
tried that....no luck

Try downloading the original ESPRING and put it on root of SD card the. Update it by turning on the phone using volume down and power
Sent from my T-Mobile myTouch 3G Slide using XDA App

Actually I revise that. It should be possible. Your phone isn't totally screwed, it boots at least. Look through the guide, I can't at the moment, and see if it actually requires your phone to be booted. I think you can do all of it through hboot and recovery, using adb and ESPRIMG.zip. I really don't remember though, read the guide, try to root your phone.
Sent from my T-Mobile myTouch 3G Slide

MusicMan374 said:
Actually I revise that. It should be possible. Your phone isn't totally screwed, it boots at least. Look through the guide, I can't at the moment, and see if it actually requires your phone to be booted. I think you can do all of it through hboot and recovery, using adb and ESPRIMG.zip. I really don't remember though, read the guide, try to root your phone.
Sent from my T-Mobile myTouch 3G Slide
Click to expand...
Click to collapse
yeah ALMOST!!!!!!
i was going thru the steps well, but then adb wont recognize the phone in the command prompt becasue it is on "diskdrive" not "chargeonly"....witch i cant change. if only i could change it

purple1 said:
Try downloading the original ESPRING and put it on root of SD card the. Update it by turning on the phone using volume down and power
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
ESPRIMG.zip... Why does everyone think it's ESPRING?
dapoharoun said:
yeah ALMOST!!!!!!
i was going thru the steps well, but then adb wont recognize the phone in the command prompt becasue it is on "diskdrive" not "chargeonly"....witch i cant change. if only i could change it
Click to expand...
Click to collapse
You can use ADB while in recovery mode, try doing the commands in recovery mode, using clockwork recovery. Although that may not work because it requires toggling wifi. See if you can find and try other rooting methods? There a few different ones out there. Your phone boots into the OS.
I googled around, found that account syncs were causing com.htc.bg to crash. I also noticed that your phone was booting without a sim card in it? Might be a stupid question, but you HAVE tried booting it WITH a sim card right? I also noticed that your hboot date is march 23rd, almost a year ago..?

http://forum.xda-developers.com/showthread.php?t=746577
Do that. Will completely restore your phone.

migueltherocker said:
http://forum.xda-developers.com/showthread.php?t=746577
Do that. Will completely restore your phone.
Click to expand...
Click to collapse
thanks...i tried that but i got and error...pic below

dapoharoun said:
thanks...i tried that but i got and error...pic below
Click to expand...
Click to collapse
That's odd, never seen that one before. My only suggestion would be to try and re-download the zip file, see if it was just a bad download. Otherwise I've got nothing.

[Q] Need Help!! First time EVO Root/CM6 gone bad...

OK....long story short...finally decided to delve into rooting and custom roms. Flashed CM6 yesterday and everything was going great. Then suddenly yesterday evening as I was swiping between home screens on my device everything froze, and I have been trying to recover ever since.
Anything I flash now just freezes, and i have a touch panel-fail so even when i do get a rom to boot i cant actually get into set it to usb mode or anything.
using bootloader i can not get it to connect using the adb driver so that I can push via adb.
about an hour ago I was successfully able to run the latest RUU and it ran successfully, but device is still way laggy (takes 15 minutes to boot) and no touch screen.
Any help would be greatly appreciated!!! don't know where to go from here. From what I have read its not bricked because I can get into Bootloader and Recovery???

Just a shot in the dark here, but it sounds like since you're stock now it's an actual hardware failure.

lil-dice said:
Just a shot in the dark here, but it sounds like since you're stock now it's an actual hardware failure.
Click to expand...
Click to collapse
Is there way I can verify that the RUU did indeed flash *EVERYTHING* back to stock?

It seen like you have a HARDWARE issues, Re-Boot the Stock Rom. Call Sprint and explain what's going on with your phone, please *DO NO'T MENTION YOU ROOTED YOUR PHONE* Tell them you try to wipe your phone and it was really laggy before you wipe, since you gonna Re-Boot the stock rom the phone is going to get UNROOTED, I know this cause I work at Sprint... So good luck...

jalexishg said:
It seen like you have a HARDWARE issues, Re-Boot the Stock Rom. Call Sprint and explain what's going on with your phone, please *DO NO'T MENTION YOU ROOTED YOUR PHONE* Tell them you try to wipe your phone and it was really laggy before you wipe, since you gonna Re-Boot the stock rom the phone is going to get UNROOTED, I know this cause I work at Sprint... So good luck...
Click to expand...
Click to collapse
I definitely wont rule out hardware issues...this is a refurb device i just swapped my original EVO for on Monday. I guess I just want to rule out any software issues for sure.
You mention that re-booting the stock rom will UNROOT the phone...however I hav no way to currently re-boot the rom??

Also looks like i can not get into recovery now, when I select the option in the bootloader it just takes me to the screen with a picture of a device and a red triangle

azkevman said:
I definitely wont rule out hardware issues...this is a refurb device i just swapped my original EVO for on Monday. I guess I just want to rule out any software issues for sure.
You mention that re-booting the stock rom will UNROOT the phone...however I hav no way to currently re-boot the rom??
Click to expand...
Click to collapse
Get a Memory Card adapter for PC or use anything that will let you connect your SD card to your computer... As soon as you put the *ORIGINAL STOCK ROM* in your SD card your phone will do everything by itself...

jalexishg said:
Get a Memory Card adapter for PC or use anything that will let you connect your SD card to your computer... As soon as you put the *ORIGINAL STOCK ROM* in your SD card your phone will do everything by itself...
Click to expand...
Click to collapse
ok, going to try this now...
I assume I need to load it onto my sd card as the pc36IMG.zip so that i can load it from the bootloader?

you got it...just put it on the root of sdcard and good luck.
Sent from my PC36100 using Tapatalk

azkevman said:
ok, going to try this now...
I assume I need to load it onto my sd card as the pc36IMG.zip so that i can load it from the bootloader?
Click to expand...
Click to collapse
Yeah... Good luck... Let me know how everything went..

OK, so I loaded this ROM: http://forum.xda-developers.com/showthread.php?t=874091 onto my sd card as PC36IMG.zip
It loads the zip then says parsing for about 1 second then just reverts back to the HBOOT option ???
Doesn't ask me if i want to install????

Looks like I grabbed only the OTA update rom that was posted on that page. I am going to try the odexed version on this page: http://forum.xda-developers.com/showthread.php?t=874251

azkevman said:
Looks like I grabbed only the OTA update rom that was posted on that page. I am going to try the odexed version on this page: http://forum.xda-developers.com/showthread.php?t=874251
Click to expand...
Click to collapse
I can upload the version I use... Give a sec.(Uploading)

OK here you go !! http://www.megaupload.com/?d=EKDYV9I5 I hope this help you !

jalexishg said:
OK here you go !! http://www.megaupload.com/?d=EKDYV9I5 I hope this help you !
Click to expand...
Click to collapse
Thanks, I will let you know how it goes.

is nand unlocked on the phone?

asafegous said:
is nand unlocked on the phone?
Click to expand...
Click to collapse
I think so, on the bootloader it still shows "S-off" ...doesn't that indicate it is still unlocked?

OK, so I was able to flash the file in the bootloader. It looks like it won't load past the 'HTC EVO 4g' splash screen.
ARGGGGGGGGGGGGGG!!!!!!!!!!!!

But the Installation finish without problems ?

jalexishg said:
But the Installation finish without problems ?
Click to expand...
Click to collapse
yeah, as far as i can tell. It said it completed and gave me the option to press the power button to reboot.
It did finally load up...after about 15 minutes, but touchscreen is still erroring out and not funtional.

unstable notice after 4.08.605.15 update

Ok,my mom has a Dinc just like me. However,her's is completely stock except an unlocked bootloader. She installed the update and everything ran smooth. With the occasional freeze. But today she turned it to go to school and turned it back on and she was prompted that her Dinc has become unstable. Can anyone explain this or tell me how to fix it?

ironside2011 said:
Ok,my mom has a Dinc just like me. However,her's is completely stock except an unlocked bootloader. She installed the update and everything ran smooth. With the occasional freeze. But today she turned it to go to school and turned it back on and she was prompted that her Dinc has become unstable. Can anyone explain this or tell me how to fix it?
Click to expand...
Click to collapse
Something got corrupted during the update it sounds like. You can first try a factory reset from hboot, if that dosent work you can do an ruu. However there is no 4.08.605.15 ruu and im not sure if it will let you flash an older version. If it dosent let you do the ruu, your only option would be to try to root and hope you can get a working rom on there.

oh boy
cmlusco said:
Something got corrupted during the update it sounds like. You can first try a factory reset from hboot, if that dosent work you can do an ruu. However there is no 4.08.605.15 ruu and im not sure if it will let you flash an older version. If it dosent let you do the ruu, your only option would be to try to root and hope you can get a working rom on there.
Click to expand...
Click to collapse
I figured those would be my only options. But why would Verizon send out a corrupted update to a phone?

ironside2011 said:
I figured those would be my only options. But why would Verizon send out a corrupted update to a phone?
Click to expand...
Click to collapse
Not really a corrupt update my self and many others had no issues. It is more likley that it was just one of those rare times that things just mess up.

ah
cmlusco said:
Not really a corrupt update my self and many others had no issues. It is more likley that it was just one of those rare times that things just mess up.
Click to expand...
Click to collapse
What shame! Seems like this phone is just on its last leg and can't handle updates of any kind since Froyo