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>

[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.

Semi-bricked Incredible?

So I flashed Skyraider tonight, wiped data, installed the ROM, and booted up the phone. I was halfway through setting up my Google account when the phone froze and rebooted. Except, it didn't boot back up. It did the "vibrate five times and flash the LED" thing. Didn't think it was a big deal, so I pulled the battery, tried to boot it back up. But it does the same thing.
I can get into the hboot menu, and if the phone is plugged into the computer, it'll boot up into Skyraider, but it can't read the SD card or the internal storage. So, essentially, a pretty screwy phone. I also cannot boot back into recovery. It just does the vibrating thing when I try. My computer doesn't detect the SD card or storage, either. (The SD card is fine, though. I put it in another phone and everything is still there.)
I have no idea what happened with it. I don't know if this is some random hardware damage, or if I should find an RUU and try to fix it or what.
I've had the worst luck with phones these past few weeks.
Any suggestions?

What version of CM Recovery do you have?
I would go back to stock and redo everything again. Download this file
http://www.fourty.net/~berzerker/stockstuff/PB31IMG_3.26.605.1_RUU.zip
Rename it PB31IMG.zip and put it on the root of your SD card, boot into the bootloader and let the update run its course. This will bring you back to a completely stock 2.2. From there you can re-root and do as you please.

I was on CW 2.5.1.2. But everytime I try to get into the recovery, the phone just vibrates five times and the LED flashes green. I'm also not sure that hboot is seeing my SD card. I'm going to try it, though.

Here is the RUU if you need it
http://shipped-roms.com/index.php?category=android&model=Incredible
The bottom one on that page is the Stock 2.2 build.

g00s3y said:
Here is the RUU if you need it
http://shipped-roms.com/index.php?category=android&model=Incredible
The bottom one on that page is the Stock 2.2 build.
Click to expand...
Click to collapse
I appreciate it, but hboot isn't recognizing the SD card.
I'm really thinking there's some hardware damage.

godsmacked4653 said:
I appreciate it, but hboot isn't recognizing the SD card.
I'm really thinking there's some hardware damage.
Click to expand...
Click to collapse
I'm not sure if it works, but can you boot into hboot and run the RUU from there and update. I don't think you need to have a working SD Card in order to do that, but I could be wrong. At least then it will be stock and no worries if you take it to verizon.

g00s3y said:
I'm not sure if it works, but can you boot into hboot and run the RUU from there and update. I don't think you need to have a working SD Card in order to do that, but I could be wrong. At least then it will be stock and no worries if you take it to verizon.
Click to expand...
Click to collapse
Do you mean running the Windows RUU? I tried that last night, but it could never find the device. ADB recognizes it, though, so idk what the problem was.

godsmacked4653 said:
Do you mean running the Windows RUU? I tried that last night, but it could never find the device. ADB recognizes it, though, so idk what the problem was.
Click to expand...
Click to collapse
If you have the unrevoked USB drivers installed I believe that is what causes it. You have to have the "stock" drivers for the phone installed on the PC for it to work, that was a problem I was having when trying to run the RUU.

g00s3y said:
If you have the unrevoked USB drivers installed I believe that is what causes it. You have to have the "stock" drivers for the phone installed on the PC for it to work, that was a problem I was having when trying to run the RUU.
Click to expand...
Click to collapse
I do have the stock drivers. I used unrevoked on Linux, and I've tried the RUU in Windows. But still no go.
I'm probably just going to take it up to Verizon today. If it can't boot, they really can't see that I've changed anything, right?

very true, good luck

g00s3y said:
very true, good luck
Click to expand...
Click to collapse
yes, good luck let us know ho it goes....

Kent_Davis said:
yes, good luck let us know ho it goes....
Click to expand...
Click to collapse
The sales rep looked at it for two minutes, and they're overnighting another Incredible to me.
So on one hand, I'm pretty happy about how easy it was.
On the other hand, I'd rather keep the AMOLED screen.
Does anybody know if I'm going to get a refurb, or will I get a new SLCD model?

If you had AMOLED first and they give you an SLCD, you can ***** at them and they have to give you an AMOLED one. Cuz that's what you payed for.
Sent from my ADR6300 using XDA App

dpwhitty11 said:
If you had AMOLED first and they give you an SLCD, you can ***** at them and they have to give you an AMOLED one. Cuz that's what you payed for.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
^ that. I just had to have a new one sent to me, its coming today. When I called tech support I asked them about what one I would be getting. They said that because I bought an AMOLED, I would be getting an AMOLED replacement.

g00s3y said:
^ that. I just had to have a new one sent to me, its coming today. When I called tech support I asked them about what one I would be getting. They said that because I bought an AMOLED, I would be getting an AMOLED replacement.
Click to expand...
Click to collapse
Yep. I got my replacement today. It's an AMOLED. As far as I can tell, all the hardware is working like it should.
This is probably the easiest time I have EVER had with Verizon.
But for future reference, five vibrations + blinking green LED = replacement.

I had same problem yesterday, five vibr.+ green blinks, but I had access into bootloader. I decided to reflash stock rom. Finally fixed problem
Sent from my ADR6300 using XDA Premium App

s 0n

Having a hell of a time getting my evo 4g to change to s on. I have successfully unrooted it but the s off remains there. I need to take it back to sprint for repairs.
I have tried several with the recent unrevoked 3. But my results are after flashing "waiting 5 seconds because windows hates" message and the other says waiting to reboot" (both freezes forever). Any direction would be appreciated.
Thanks you.

Newsflash. I've never heard one story of Spring checking a bootloader to make sure a phone is S-On.
Flash A stock ROM and you;ll be good, although there have been posts that say Sprint will work on Rooted phones now.

rosario04 said:
Having a hell of a time getting my evo 4g to change to s on. I have successfully unrooted it but the s off remains there. I need to take it back to sprint for repairs.
I have tried several with the recent unrevoked 3. But my results are after flashing "waiting 5 seconds because windows hates" message and the other says waiting to reboot" (both freezes forever). Any direction would be appreciated.
Thanks you.
Click to expand...
Click to collapse
Ignore this, double post. Next post.

rosario04 said:
Having a hell of a time getting my evo 4g to change to s on. I have successfully unrooted it but the s off remains there. I need to take it back to sprint for repairs.
I have tried several with the recent unrevoked 3. But my results are after flashing "waiting 5 seconds because windows hates" message and the other says waiting to reboot" (both freezes forever). Any direction would be appreciated.
Thanks you.
Click to expand...
Click to collapse
You have to have a custom recovery to do that (Amon-RA or Clockwork). You need to reinstall Amon-Ra Recovery by putting this in the root of your SDCard and rename it "PC36IMG.zip": http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=PC36IMG.zip
Then flash this: http://downloads.unrevoked.com/forever/current/unrevoked-forever-son.zip
After that just run an RUU from here: http://goo-inside.me/supersonic/ruu
In case the RUU won't work from your computer, download one of the ZIP ones, put it in the root of your SDCard and rename it "PC36IMG.zip". That always works.

I am not sure what you mean by "Spring checking but I have flashed the stock rom PC36IMG.zip onto the root of the sd. My understanding that once your successful doing this you basically revert to the original rom. I have done that thanks to this site. But, I cannot for the life of me get the s on back on. Rooting my phone with three different custom roms were easier. Not all Spring stores like rooted phones. Id rather revert to original with the s on to be sure. product F thanks for the reply I will try that..perhaps I missed something. Thank You.

HipKat said:
Newsflash. I've never heard one story of Spring checking a bootloader to make sure a phone is S-On.
Flash A stock ROM and you;ll be good, although there have been posts that say Sprint will work on Rooted phones now.
Click to expand...
Click to collapse
That plus the leaked document from the sprint employee forums that said that sprint supports rooted devices means we don't have to fret over s-on for service just make sure that your phone is running a sense rom when it is taken in otherwise they can't use the diagnostic commands from the dialer to fully support the device.
Sent from my PC36100 using Tapatalk

s on
Well I think my biggest problem is that i unrooted my phone because Clocwork will not work for me to flash forever s on because it is unrooted. Is this correct? Thanks

rosario04 said:
Well I think my biggest problem is that i unrooted my phone because Clocwork will not work for me to flash forever s on because it is unrooted. Is this correct? Thanks
Click to expand...
Click to collapse
If you're using Clockwork, you have to disable Signature Verification.

s on
Product F(RED) said:
You have to have a custom recovery to do that (Amon-RA or Clockwork). You need to reinstall Amon-Ra Recovery by putting this in the root of your SDCard and rename it "PC36IMG.zip": http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=PC36IMG.zip
Then flash this: http://downloads.unrevoked.com/forever/current/unrevoked-forever-son.zip
After that just run an RUU from here: http://goo-inside.me/supersonic/ruu
In case the RUU won't work from your computer, download one of the ZIP ones, put it in the root of your SDCard and rename it "PC36IMG.zip". That always works.
Click to expand...
Click to collapse
But to get clockwork to work you have to be rooted...correct?
Thank you

Yes but you're still s-off so follow those instructions.
Sent from my PG86100 using XDA Premium App

Thanks for staying with me. Appreciate it.
Here is how I wasable to get to recovery to get to the root directory for choosing zip from sd.
STEP 9: TURN OFF DEVICE
Power down the device by holding the Power Button for 2 seconds. Allow it to shutdown completely. Wait about 10 seconds before next step.
STEP 10: RECOVERY MODE
Hold down VOL DOWN + POWER until device boots into a White Screen.
Move to RECOVERY by using the VOL DOWN toggle and select by using POWER button.
STEP 11: TRANSFER PC36IMG.zip TO SDCARD
Connect the MICRO USB Cord. There is an option for this in both the Amon RA and Clockwork recovery.
Transfer the PC36IMG.zip to the ROOT of your SDCard.[/SIZE][/SIZE]
It was the connection and discnnection of th usb cable. Everything was in green. Is that normal.
So, my next step was to flash the forever s on zip. The results were unsupported radio version. Update failed. The current version I have is 2.15.00.05.02. on the new update on my evo. I tried it first by removing the pc36img.zip nd then tried it with it on...same results.
So I found this radio version (EVO_Radio_2.15.00.05.02_WiMAX_27243_PRI_NV_2.15_003), but I am not sure if this is what version is needed. Anyways, I apologize for this long everyone, but I am trying to provide as much info and hopefully I can minimize your time. Thanks alot.

rosario04 said:
.
...
So, my next step was to flash the forever s on zip. The results were unsupported radio version. Update failed. The current version I have is 2.15.00.05.02. on the new update on my evo. I tried it first by removing the pc36img.zip nd then tried it with it on...same results.
So I found this radio version (EVO_Radio_2.15.00.05.02_WiMAX_27243_PRI_NV_2.15_003), but I am not sure if this is what version is needed. Anyways, I apologize for this long everyone, but I am trying to provide as much info and hopefully I can minimize your time. Thanks alot.
Click to expand...
Click to collapse
The radio package you mention is the same radio you already have, so you'll want an older version. I'm not exactly sure of the version number, but I do know that is not the correct one.
Remember when you flash radios to not pull the battery. It'll flash, then upon rebooting it'll finish. You'll see a screen that you probably haven't seen before, it'll most likely be an arrow pointing down to a phone or an Android in a box... or something like that. Regardless of what you see after the flash, don't freak out and pull the battery - you'll end up bricking your phone. It's one of the few ways to guarantee a real brick, the phone will never turn on again. You may already know this, or it may be in whatever guide you're using, but it's good to know.
Anyway, I'll see if I can find the correct radio for you, and good luck!
Edit: I read somewhere that someone used this one to get s-on: http://www.mediafire.com/?v0ymbhaa0ltcvyy
However, you may need to do some trial and error. It should work, but here's a link to all of them: http://forum.xda-developers.com/showthread.php?t=715485
These are from Calkulin, so if they're PC36IMG files you'll be fine, but I'm pretty sure you flash them in recovery. Sorry, it's late & I'm lazy. Anyway, I think Calkulin still uses amend scripting, which will render them incompatible with ClockworkMod. You'll either need to switch to Amon Ra to flash them or find a different flashable zip. I think you'll only need to flash the radio, not all of them, but I could be wrong.
Sent from my PC36100 using Tapatalk

You don't need S-OFF to have sprint work on your phone for repair. My cousin just got an insurance replacement Evo 4g because he washed his phone with his clothes. He brought it over to me to be rooted and the phone he got was already S-OFF and that is an Insurance REFERB. also with the leaked forum of how Sprint will infact work on Rooted phones gives it away that you dont need S-OFF

Plainjane. Thanks for the info. I downloaded the zip from the first site you showed here and it ran well with the exception that it got stuck on formatting cache. So, I rebooted. s off still on. I will try the next one here in a few. Thanks everyone.

s on
well. While I continue to try and solve this puzzle I will attempt to attach this link on how to flash a radio to evo. i take no credit.

well i am happy to say i have finally go the s on back on. I believe the problem was that i left the recovery supersonic ra image on the root directory of the sd. i deleted that and flashed the supersonic s on image and voila!!! Everythin crumbled under the rosario wrath and s on is on. Thats Boricua power. My next problem is flashing sense back on. Khilbron, I wasnt ignoring your post on sense, it was just I was trying to get the other things done. So can you please expand on the sense. Thanks to everyone who took out the time even you kipkat with your kind of unfriendly comments. Dueces.

s on
rosario04 said:
well i am happy to say i have finally go the s on back on. I believe the problem was that i left the recovery supersonic ra image on the root directory of the sd. i deleted that and flashed the supersonic s on image and voila!!! Everythin crumbled under the rosario wrath and s on is on. Thats Boricua power. My next problem is flashing sense back on. Khilbron, I wasnt ignoring your post on sense, it was just I was trying to get the other things done. So can you please expand on the sense. Thanks to everyone who took out the time even you kipkat with your kind of unfriendly comments. Dueces.
Click to expand...
Click to collapse
i took my phone back to sprint and they replaced both speakers. now to root again.
Again. Want to thank everyone for their help.

[Q] bricked

hate to ask for help bc u can usually find the answer somwhere....if my phone IS really bricked would love someone to tell me that so i can move on. seemed to have read that if it comes on then its not bricked..idk. ive rooted, flashed new roms and flashed it back completely stock.
i bricked it by attemting to flash it to boost...wrote nv items and zero'd out the meid. was looking for the esn so i could do the same, got a few of em.....phone fell battery flew..now i cant get past the first white htc screen...now this is where things get funky. a step of the guide i was following required root so i did n i saw cwm.. wen i got the bootloop i wasnt really worried at first bc i kne i could try a few things. well that didnt last long. booted into hboot n it said s-on..? then it wouldnt let me in recovery, just rebooted to the bootloop. i tried runnig unrevoked agn even tho i couldnt boot...couldnt read the phone. put the pb13img on sd card and it went thru its updating process n asked to reboot. reboots in same bootloop. next i tried runnig RUU..it runs and reboots my phone to the same bootloop...is there anyway to restore the ORIGINAL nv items and meid/esn...since these are the only things other than running unrevoked that ive changed i think thats where my problem lies. any help would be greatly appreciated.

Which radio is currently flashed on your phone? I had this issue once, I had to flash back to the 7.28 radio to get my phone to boot.

damn when i saw this post, i thought it was my post! i did almost the exact same thing and its acting almost the same as your phone. i did the ruu and it worked on the one posted in my thread, ran through and all but nothing. how would i done grade the radio?

i never flashed a radio...hboot says 2.15.00.07.28..
lol waxworks i saw ur post also... started reading and we pretty much did the same thing on pretty much the same step of flashing to boost...mad as hell too stuck with this incognito for awhile smh..
is there anyway to flash a nandroid without being able to get into cwm? idk man jus not looking good.

Reading your post not sure if you used the stock image and tried to update using the hboot menu.There is a thread 5 vibe fix that may help you get a rom image back to your phone

Vernox701 said:
Reading your post not sure if you used the stock image and tried to update using the hboot menu.There is a thread 5 vibe fix that may help you get a rom image back to your phone
Click to expand...
Click to collapse
Do you happen to have link? I'm on tapatalk and there no search

waxworkz said:
Do you happen to have link? I'm on tapatalk and there no search
Click to expand...
Click to collapse
I believe this is what you're looking for:
http://forum.xda-developers.com/showthread.php?t=1110865

no fix for this?...anyway to get s-off only being able to use fastboot?

strive53 said:
no fix for this?...anyway to get s-off only being able to use fastboot?
Click to expand...
Click to collapse
I think we have bricks! I tried to do some other method that involved running a script and cmd prompts. Didn't do anything as I am also "S" on. I think all the fixes are for "S" off.