Develop Bugs

[Q] Can anybody help me out, please?

I've searched the forums and have not found a situation that really matches mine.
I've been running on a Cyanogen nightly build for probably two months with no problems. Out of nowhere this morning my phone reboots itself (while it was idle; I wasn't even touching it) and then gets stuck in a boot loop. I get the White HTC Evo 4G screen, then it powers off and comes back up to the white screen again. Over and over.
All I can get do is hboot. Even telling hboot to go into the recovery mode puts my back into the boot loop. Fastboot, clear storage, and hboot usb all seem to work though. I've tried downloading the PC36IMG.zip file (http://forum.xda-developers.com/showthread.php?t=780141) in that thread, but hboot loads it and tells me that it is older than my current version, and only gives me the option to reboot, or not to reboot. Doesn't load the image.
Here is the information on my hboot screen:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-0.97.0000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.09.01
Aug 19 2010, 14:29:08
Anybody have any ideas? Thanks!

you lost root, s-on
you can still start the bootloader so it's not a brick
need to get s-off before you can load recovery again and reflash your rom
have you tried the RUU? if it installs and defaults you then you can unrevoked to root

NewZJ said:
you lost root, s-on
you can still start the bootloader so it's not a brick
need to get s-off before you can load recovery again and reflash your rom
have you tried the RUU? if it installs and defaults you then you can unrevoked to root
Click to expand...
Click to collapse
Trying the RUU here now: http://forum.xda-developers.com/showthread.php?t=874091
Wish me luck!

luck has been wished

Kuhmo said:
Trying the RUU here now: http://forum.xda-developers.com/showthread.php?t=874091
Wish me luck!
Click to expand...
Click to collapse
This didn't work. Everything is still the same, except that my hboot version is now 2.10.0001. Any other thoughts?

still won't not into any rom? did you get errors?

NewZJ said:
still won't not into any rom? did you get errors?
Click to expand...
Click to collapse
No, the app on the PC said everything was successful. The progress bar on the phone progressed without errors too.

what happens when you reboot the phone not going into bootloader?

Just the HTC EVO 4G splash screen. Over and over and over...

does it show the boot animation or just stuck on splash?

Just the splash. No animation.

pull the battery, remove your sdcard, put the battery back in, see if it gets to the animation

Doh, you upgraded your hboot. It's alright though, just run the ruu one more time and your should be ok
Sent from my PC36100 using XDA App

Wrong button..

xHausx said:
Doh, you upgraded your hboot. It's alright though, just run the ruu one more time and your should be ok
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I asked my wife to check this thread from the car on the way to dinner. Saw the response. So I took my laptop inside with us and used the RUU one more time. No luck. I decided that it must be a hardware issue. I took the SD out and removed the evidence that the phone had been rooted, then took it to the sprint service center up the road. They just replaced it for me. Thanks for your time! I DO want to root my phone again, the ROMs are just so much better than the stock installation. Should I not install the OTA updates if I'm going to root it? Which guide should I follow for rooting?

never do OTA when rooted, use unrevoked to root, unrevoked.com

NewZJ said:
never do OTA when rooted, use unrevoked to root, unrevoked.com
Click to expand...
Click to collapse
Not when rooted. I meant should I update to the latest OTA UNTIL I decide to do the root again? Is the latest OTA unrootable?

Same deal.
Here is the post that I put in the wrong forum that I was about to post here until I saw this thread...
Wellp. I win.
I win a no expenses paid trip to my nearest Sprint dealer.
Ever since I used unrevoked to root my phone in November, I've been voraciously digging through these forums for tasty roms. I've been snorting lines of Cyanogen, MIUI, and a myriad of other, well-designed roms.
Using a on older version of hboot (pre 1 methinks) I was able to avoid the latest hassles with ClockworkMod (plus, I down(up?)graded to 2.6 via RomManager).
Tonight, as I was enjoying some tasty foodstuffs at my local foodstuff vendor, my phone rebooted. Then, it rebooted again. Then again. I once made the folly of flashing a new rom without running the appropriate wipes, and was no stranger to the bootloop. I patiently fired up hboot (my poor volume rocker is all but wore out) and ordered up the trusty recovery mode.
...then it rebooted again... and again... and again.
PusSidiasus: ONOES! I HAVE THE WTFBBRICKED MY PRECIOUS!
SmartAsSidiasus: Hang on for a second, let's check the internet. Try this link: tinyurl.com/4vgeyeg
PusSidiasus: ...
Unfortunately, my internal dialogues are not nearly as witty. Also, my best attempts to de-brick-ify were for naught. Fastboot gave some wacky error message when I tried to flash a new recovery, and installing via PC36IMG.zip did nothing to improve the situation. I even went so far as to install a stock image someone pulled from an RUU (with a 2.02hboot, so as to avoid wimax woes)...
Still, a whole lotta nothing. I can't do anything beyond hboot, and whatever recovery image I install (Clockworkmod, AmanRa) the machine still bootloops.
At this juncture, I've resigned to taking the phone into the sprint store and playing dumb. It is a stock rom, though I hope the attendant misses the S-OFF bit at boot. Which brings me to my proper question:
1) Has anyone run aground a similar issue and found a way out?
OR...​
2) Anyone know how to turn S-(back)ON in my current situation?​
Any insight would be greatly appreciated. Also, you can rest assured that I'll be rooting again whatever phone I walk away with, and the work that is exhibited in these forums is amazing. Keep churning out wonderful roms and guides.
Sidiasus
(Currently, Sadiasus... )

run the ruu to s-on then trade for another

NewZJ said:
run the ruu to s-on then trade for another
Click to expand...
Click to collapse
Ack, sorry... didn't mention in previous post. I fired up windows to run the RUU (I don't trust wine to that stuff) but it couldn't detect the device.

[Q] Removing a rom, fixing a mistake, and getting to normal

I really have this huge problem that's been really bugging me all week and i cant seem to concentrate with it over my head. I am new to rooting devices and i was a little ahead of myself recently... I finally rooted my phone and over my excitement i just had to add custom roms to my Evo 4g, i didnt really understand what i was doing, i mainly followed instructions to most sites, mainly cyanogen, and got the latest version of cyanogen, i had troubles starting it up at first, it was stuck on the bootup screen for cyanogen (droid on skateboard with spark flying around) and it kept going black and reloading, i didint know what to do, so i took the battery out after a hour of waiting then i wiped my drive in fear of bricking my phone (i know i wasnt thinking) i did not make a back up of my previous point of time where i actually practically running stock, and i am still upset at that mistake, after doing a factory reset from the clockwork recovery, cyanogen finally booted up, but was missing alot of things, i.e. android market and so on... im now wanting to go back to stock and i have already got Son somehow, can anyone help walk me through this, id very much appreciate it!!

acidcobra2002 said:
I really have this huge problem that's been really bugging me all week and i cant seem to concentrate with it over my head. I am new to rooting devices and i was a little ahead of myself recently... I finally rooted my phone and over my excitement i just had to add custom roms to my Evo 4g, i didnt really understand what i was doing, i mainly followed instructions to most sites, mainly cyanogen, and got the latest version of cyanogen, i had troubles starting it up at first, it was stuck on the bootup screen for cyanogen (droid on skateboard with spark flying around) and it kept going black and reloading, i didint know what to do, so i took the battery out after a hour of waiting then i wiped my drive in fear of bricking my phone (i know i wasnt thinking) i did not make a back up of my previous point of time where i actually practically running stock, and i am still upset at that mistake, after doing a factory reset from the clockwork recovery, cyanogen finally booted up, but was missing alot of things, i.e. android market and so on... im now wanting to go back to stock and i have already got Son somehow, can anyone help walk me through this, id very much appreciate it!!
Click to expand...
Click to collapse
The reason that you were missing things in Cyanogen, is because you didn't flash GAPPS (google apps), which are things like Market, Gmail etc. If you already have S-on, and you're sure you want to go back to stock, unrooted, then it shouldn't be too bad for you. One way would be to download a PC36IMG.zip, place it on the root of your sd card, boot into the bootloader (power+voldown), and it will flash the factory ROM for you. You could also run RUU, from your PC. Plug phone into PC with USB cable, and run the RUU from your computer. Either of those methods should work for you, and get you back to stock. Here are a couple links that might help you.
Complete list of factory PC36IMG.zip and RUU:
http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu
Guide on how to Unroot
http://forum.xda-developers.com/showthread.php?t=780141
Good luck.

k2buckley said:
The reason that you were missing things in Cyanogen, is because you didn't flash GAPPS (google apps), which are things like Market, Gmail etc. If you already have S-on, and you're sure you want to go back to stock, unrooted, then it shouldn't be too bad for you. One way would be to download a PC36IMG.zip, place it on the root of your sd card, boot into the bootloader (power+voldown), and it will flash the factory ROM for you. You could also run RUU, from your PC. Plug phone into PC with USB cable, and run the RUU from your computer. Either of those methods should work for you, and get you back to stock. Here are a couple links that might help you.
Complete list of factory PC36IMG.zip and RUU:
http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu
Guide on how to Unroot
http://forum.xda-developers.com/showthread.php?t=780141
Good luck.
Click to expand...
Click to collapse
Thank you so much for a quick reply, it really helps, but one more question, i tried to run pc36img, but it keeps saying it failed because a older version was present, also, sorry for asking another, but i have also wondered this other method with all these other download links, there is alot and how would i know what one to use?
also! i tried running the first download and it keeps saying that my phone isnt connected even if it is? does it need to be in debugging mode or what?

you have to flash most recent gapps for market.

acidcobra2002 said:
Thank you so much for a quick reply, it really helps, but one more question, i tried to run pc36img, but it keeps saying it failed because a older version was present, also, sorry for asking another, but i have also wondered this other method with all these other download links, there is alot and how would i know what one to use?
also! i tried running the first download and it keeps saying that my phone isnt connected even if it is? does it need to be in debugging mode or what?
Click to expand...
Click to collapse
Do you know what hboot version you have? If not, boot into the bootloader (power+voldown), and it will say hboot version at the top I believe. If you have an older hboot version, I'm pretty sure you want an older PC36IMG or RUU. If you notice, they all list different software versions (3.70, 3.30, 3.29, 3.26 etc). The 3.70 is the newest, and I believe you'd use that for the newest hboot versions (2.10 or 2.02) The older hboot's (.76, .93, .97) I believe you'd use either 3.29 or 3.30. Someone please step in and correct me if I'm wrong or misinformed. I'm also not sure if you need to be in debugging mode, I would try putting it in debugging mode for sure (I've never had to unroot, but have read up on how to do it) If you are getting the main version is older when running the PC36IMG, I would try a different PC36IMG, one with older software, 3.29 or 3.30. I've read many times of people needing to try different ones before they got it to flash. That's why there are so many on there, because different phones may require different versions, I believe.

k2buckley said:
Do you know what hboot version you have? If not, boot into the bootloader (power+voldown), and it will say hboot version at the top I believe. If you have an older hboot version, I'm pretty sure you want an older PC36IMG or RUU. If you notice, they all list different software versions (3.70, 3.30, 3.29, 3.26 etc). The 3.70 is the newest, and I believe you'd use that for the newest hboot versions (2.10 or 2.02) The older hboot's (.76, .93, .97) I believe you'd use either 3.29 or 3.30. Someone please step in and correct me if I'm wrong or misinformed.
Click to expand...
Click to collapse
It is Hboot-2.10.0001

You sir [user above me] are correct. I have linked ya to a site with a lot of RUUs, and they list the version number.
http://www.shipped-roms.com/shipped/Supersonic/
Download the RUU, boot into the bootloader [turn off then hold vol down while phone turns on] then select fastboot, then run the exe, and follow zeh instructions.

acidcobra2002 said:
It is Hboot-2.10.0001
Click to expand...
Click to collapse
Which PC36IMG or RUU did you try? (which software) You may need to try a couple different ones on there.

Unroot failed, now phone is stuck in Fastboot loop

Hi Guys, I posted this in Android Software and Hacking General, but I didn't get a reply. Probably the wrong section!
my HTC Desire GSM is stuck in Fastboot and won't boot into the ROM. The background to this issue is that I installed S-Off and then ClockworkMod and flashed Cyogenmod 7 to see if it would fix a reboot issue on the phone. The damn thing just reboots itself when the CPU is used heavily...
Anywho, after realising that Cyogen wouldn't resolve the issue I flashed the standard Virgin UK rom back over it and upgraded to 2.22.351.2 via the system update feature. The problem was that ClockwordMod was still installed and I had to get rid of it to sent the phone off for repair to Virgin!
So I did further research and found that I could flash HBoot via the AlphaRev.nl downgrader tool. I downloaded it and popped it into the root of my SD card and it flashed the bootloader back to Hboot 0.80.0000. That should have been it, but all of the sudden the phone no longer boots into the Rom. All it does is to power on and then go into Fastboot. That's it! When I try putting the standard Virgin Rom back onto the SD it tries to load it and then says "Main Version is older!" "Update Fail!".
How do I get around this now? The phone doesn't boot, so I can't re-flash S-Off and start again, not am I able to run the stock Virgin Rom within Windows because it complains about the versions.
Is there any ways around this situation? I just want to get the phone back to stock so I can send it to Virgin and get it repaired.
P.S. I *have* used the search function and spent the last 4 hours testing various things but I'm now stuck.
Cheers Guys!
Mich

Well you obviously fckd up with the Downgrader, you should have run it first BEFORE RUU. Also did you flashed Stock Hboot prior to Downgrader? (if you used CM7 earlier)
I never played around with the hboot downgrading etc. so i wont be able to help you but im sure there is some workaround...

as your returning your phone anyway why don't you try the official HTC gingerbread update from the HTC developer site (sorry I don't have a link). It should return your phone to stock and when you get it back you need to use revolutionary to get s-off back. Also, there is a sticky from user bortac which has loads of help and trouble shooting advice.

iain2510 said:
as your returning your phone anyway why don't you try the official HTC gingerbread update from the HTC developer site (sorry I don't have a link). It should return your phone to stock and when you get it back you need to use revolutionary to get s-off back. Also, there is a sticky from user bortac which has loads of help and trouble shooting advice.
Click to expand...
Click to collapse
Any advice that uses the 2.3.3 RUU to fix something is plain bad advice - it can just make your problem a LOT worse.
@OP Go onto my guide, look at RUU problems for help
What you need to do:
-Make a goldcard (there is a tutorial there)
-Flash the WWE RUU

Guys, upgrading to Gingerbread has actually brought the phone back from the dead! =) And I can now return it to Virgin to get it repaired properly. The symptoms are that while the phone is plugged in and charging, and I'm doing stuff (taxing the CPU), the phone will eventually simply rebooting itself. Just *BANG*! And it's gone. And once it starts it's a bit of a run-away thing and just keeps on doing it until you leave the phone alone for a bit. Virgin had a look at it and simply re-flashed it, thinking that they could away with that. Typical, overworked, non-creative call centre workers..... I'm well pissed off with them!
Gonna send it back next week and force them to swap the motherboard or something, cause this is a serious fault with the phone.

Please help with unroot, i messed up and and going crazy here.

Ok, I rooted with unrevoked a long time ago. Broke my screen and need to unroot. I followed the unroot unrevoked guide as closely as I could, but the rom in the link was not found. So I downloaded a different ruu.zip of factory rom, don't ask me which one, because I can't find the link anymore, but currently here is where I stand. Hboot kept saying that the img was older or something, and wouldn't flash. So I did a stupid thing and pushed the zip with clockwork. So now I'm running s-on with clockwork recovery and a stock unrooted rom. So, I tried the next thing, downloaded an 3.7 ruu .exe and tried to run that from windows, but it gives me an hboot usb connection error f*ucking **** 1 thing after another.
This is the unrooting guide I used http://forum.xda-developers.com/showthread.php?t=780141
I got s-on, and tried that pc36img but it wouldn't work, originally. Before I went on to screw things up.
I've been at this for hours, something that should have taken 10 minutes if I wasn't an idiot, or bad links, or what ever. Can someone tell me or point me in the right direction, of what to do here, preferably not to a 2 year old thread with outdated links? What should I do?`
A List of android stock RUU zips with radio, pri, recovery all in one would be great, but I give up on trying to find that, its buried or does not exist.
I found this list http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/ROMs but its just the rom not everything.
So here is where my phone stands
S-ON
Hboot .97
Clockwork recovery 2.5.0.7<<<<<<
Android version 2.2.2
Build number 4.54
PRI 1.90_003

Angrychair420 here is a stock RUU that I know is good you should be able to run the RUU from windows.
http://geekfor.me/evo/ruu/evo_ruu_1326511/

thanks, that says its img version 1.32.651.1, assume thats safe to use. I assume thats andoid 3.26 which is what came on my phone. Ugh I'm in over my head. Why did my screen have to break, i was totally happy with CM7 and everything the way it was.
what if I wipe my data and caches, remove SD card, put on a PC36IMG.zip and boot the phone into hboot, will it still give me the older version error?
edit: the link you gave me gives me the same error as the other ruu.exe:
The ROM Update Utility cannot update your android phone
Please get the correct ROM Update Utility and try again

Possibly but I did have to return mine for repair and I know that using it as a .exe file trough windows I had no problem. Not sure about making it into a PC36IMG.zip file though I have not tried it that way.

Angrychair420 said:
thanks, that says its img version 1.32.651.1, assume thats safe to use. I assume thats andoid 3.26 which is what came on my phone. Ugh I'm in over my head. Why did my screen have to break, i was totally happy with CM7 and everything the way it was.
what if I wipe my data and caches, remove SD card, put on a PC36IMG.zip and boot the phone into hboot, will it still give me the older version error?
Click to expand...
Click to collapse
It might. There are 3 PC36IMG files in the first "My Links" link in my signature. You can try them in order if you'd like, if you get the "main version is older" message, but if the first two don't work, the last one definitely will.

Thanks cpt, about to give them a try. Sigh man, this is frustratingly harder than rooting :-D If it was as easy as doing the s-on and copy the pc36img.zip to the root of sd and booting into hboot and DONE, I would of been having a much better day.

Try the latest RUUs from this link man:
http://www.filefactory.com/f/acf0b850b0f70d7b/

Have you tried this?
http://htcevohacks.com/htc-evo-hacks/how-to-unroot-your-htc-evo-4g/
You can also try this
http://www.goodandevo.net/2011/03/how-to-unroot-your-htc-evo-4g.html

I appreciate the help guys. I will keep posted. You know how much it sucks to slide on a touchscreen thats broken? lol
partyman1971 said:
Have you tried this?
http://htcevohacks.com/htc-evo-hacks/how-to-unroot-your-htc-evo-4g/
Click to expand...
Click to collapse
Yes, that's the first RUU.exe I tried. said this RUU can't update
ok i got a pc36img.zip installing from hboot right now.
edit:dang main version is older error. Trying a wipe then hboot then pc36img.zip
Same outcome, main version is older.
partyman1971 said:
Have you tried this?
http://htcevohacks.com/htc-evo-hacks/how-to-unroot-your-htc-evo-4g/
You can also try this
http://www.goodandevo.net/2011/03/how-to-unroot-your-htc-evo-4g.html
Click to expand...
Click to collapse
yes, they are basically the same method I used in my OP from xda forums.
On to captain_throwbacks second ruu.
Just to make sure, this all isn't in vain, and make you all hate me, after applying one of these successfully, my recovery should go back to factory and no longer be clockwork, right? or wrong, because I'm starting to think I am. But won't taking your device in for service with clockwork be a dead giveaway that it was rooted.
I think I'm just going to go get a new phone for a $100 deductible at this point. and replace the screen my self on my old one and keep it as a backup/test device. Thanks for all the help, but I am surrendering :-D hopefully I can reroot this thing again with unrevoked, since my hboot is still .97 and fix the screen my self.

It generally doesn't matter if its rooted. I've never unrooted since launch day. And I've had 3 screen replacements, 3 speaker rwolacements , a bezel replaced, and camera lens cover replaced (last time, I dropped it off with ICS), about to go get my 4th screen (just cracked it again lol).
Sorry for your experience/frustration.
sent from AOKP heaven

well last stupid question i promise, since i still have clockwork isntalled, i can just restore my CM7 backup, but how do i get s-off back, re unrevoked it i assume?

If your'e worried about the warranty thing, just flash a stock rooted rom, or use a phone repair service. i see three or four repair places on craigslist (granted, that you live in a large city).

yeah no worries. Got it back to S-OFF, and CM7 back on it, just going to fix the screen my self, ordered one for $15.
thread can be locked, deleted, or what ever.

Seriously. Dude, isn't there a sprint store near you?. Just take it in. Put a stockish rom on it if you're that worried about it. They should replace it for free.
sent from AOKP heaven

[Q] Stuck in a loop please help

Incrediblec XD ship S-On
Hboot-0.92.0000
microp-0417
touch panel-atmelc03_16ac
Radio-2.15.10.07.07
Jul 23 2010, 18:06:51
Hello, first thank you for an amazing and current forum, I'd been researching my issue for a while, but most things are dated around 2010. I've experience rooting and ROMing a Droid X with multiple ROMS, but I use the original Incredible as my main phone because I still love it. Well, I originally rooted my Inc with Unrevoked3 I believe. I left the ROM as stock up until a couple months ago when I put CM7.2.0 on it.
About a week ago, the phone would always have working mobile data. Yet, if I received or tried to make a call, I couldn't and then I would lose texting ability. Then, a couple days ago, I was using the Inc for wifi tethering when suddenly it went into an Incredible bootloop. I tried booting to the cyanogen recovery, but it will quickly loop out of it as well.
I went to pvillecomp.com/ and downloaded all the stock Inc software. I individually renamed files to PB31IMG.zip and tried to have HBoot pick up on them. Hboot will see the files, but then do nothing. Except, the originally ROM will get checked and come back and say that the current version is older and can't be flashed.
I've always tried the RUU software for hboot and the original ROM. I either get a usb error or a low battery error even if the battery is charged. Granted, I'm trying the RUU from the phone's bootloader screen.
Does anyone have some support they could throw this way? I use my phone for internet and everything. Thank you all.
-Nevin

BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin

NevinInc said:
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
Click to expand...
Click to collapse
did you flash any radios? Flashing radios always ends up bad.

NevinInc said:
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
Click to expand...
Click to collapse
S-off, flash TWRP (because CWM sucks) and flash a new rom. This should fix everything. Flashing a radio DOES not screw everything unless you do not know what to flash, in that case you should not be flashing radios.

I'm looking into the TWRP stuff right now since I've only experience with CWM. My only concern is that I still have S-on. How can I get S-off on my phone when I've only access to the bootloader? Sorry if this is a bit off a noob post, I've simply not the experience with the incredible to know. Thank you so much.
-Nevin
123421342 said:
S-off, flash TWRP (because CWM sucks) and flash a new rom. This should fix everything. Flashing a radio DOES not screw everything unless you do not know what to flash, in that case you should not be flashing radios.
Click to expand...
Click to collapse

Btw, no I didn't flash the radio. That was the only thing I didn't attempt to flash. Yet, when attempting to flash anything else, nothing worked. Still wondering about getting S-off before using TWRP, but hopeful to still get it working. Thank you again.
NevinInc said:
I'm looking into the TWRP stuff right now since I've only experience with CWM. My only concern is that I still have S-on. How can I get S-off on my phone when I've only access to the bootloader? Sorry if this is a bit off a noob post, I've simply not the experience with the incredible to know. Thank you so much.
-Nevin
Click to expand...
Click to collapse

BUMP/UPDATE:
Yes, I'm still at it trying to get my Dinc out of it's bootloop and up/running. It's difficult at this point to say what all I've tried. At one point I wanted to use htcdev.com to ensure the bootloader was unlocked/etc. I've had much trouble trying to get fastboot to work correctly on my pc. I've seem to get stuck on "waiting for device" which appears to be a driver error.
I gave up on that and started focusing on the RUU process. I've tried to install the entire Gingerbread 605.3 file. I fixed the error usb 170 by updated or changing htc sync software. Now I'm left with error 140 bootloader error.
I've also updated hboot using the ruu process for version 605.2. This worked on my pc and got me partially excited. Now my hboot shows up as "Locked" now at the top. I also downloaded a different Stock.img file. Hboot detected this and begun the install process. Everything came up as complete and upon reboot went right back into the white screen/incredible bootloop.
So since posting before I've updated htc sync on my pc and have officially relocked my bootloader. I don't mind RUU'ing things to stock, but now gotta get past the Error 140. Any ideas?

So I'm not sure how many are looking at this or have had ideas, but I was able to use htcdev to unlock the bootloader.
Before unlocking the bootloader I was able to RUU to image .15. After this is when I unlocked the booloader. The RUU said it was complete, but I still only bootloop on the incredible white screen. Now, some of the pb31img.zip files I've come across don't even try to install. This includes signed and unsigned .15 img files. Currently these are the new settings to the phone:
Bootloader: unlocked, s-on
hboot 1.07.0000
radio - 2.15.10.12.20
Image version: 4.08.605.15
The last option I can think of is to try using fastboot, but won't that essentially do the same thing? If you think fastboot is the way to go, can u link me or give me some basics on using it. Obviously I used it for unlocking the bootloader so it can't be that complicated.
Are there any other ideas or should I give up on my Dinc? Looking forward to hear what you think. Thanx.
-Nevin

somebody recommended you install TWRP and install a stable Jellybean ROM. Did you try that?