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] How to unbrick Dinc?

I was Flashing the OTA 2.2 Froyo Leak a while ago and it just didnt finish for some reason. Now when I try to turn it on it Vibrates 5 times and has a green blinking light.
Also it is S-ON now for some reason as well.
I have looked everywhere and cannot find a solotion.
Any help is appreciated.
Edit* I have tried flashing other roms and still nothing, (I can access HBOOT but not Recovery) and I cannot flash recovery either. Everything but Hboot is gone. And i tried flashin Ruu and it says main system too old.

5 Vibrates is usually some kind of hardware issue, where-as 3 vibrates is usually a software issue.
BTW, if you're S-On, how are you going to flash any recovery or ROMs? You need to be S-Off before you can flash anything.

carngeX said:
5 Vibrates is usually some kind of hardware issue, where-as 3 vibrates is usually a software issue.
BTW, if you're S-On, how are you going to flash any recovery or ROMs? You need to be S-Off before you can flash anything.
Click to expand...
Click to collapse
How can I get S-OFF then? I can access Recovery but it doesnt do me any good it wont read my sd card.

I have no idea what I did, but it rebooted itself and its working

this is EXTREMELY weird. I had the phone plugged in because I wanted to root, but i was first getting the SD Card files off and when I unplugged the phone the same thing happened already....
So then I plugged the phone on again, went into HBOOT and ran the image until it told me it cant be read, and rebooted and back to normal....
Any idea what happened? I just wanna get opinions out of curiosity.

cvbcbcmv said:
cool. But no you don't want to be s-off for flashing the RUU back to stock, then you actually flash a s-on image first.
Click to expand...
Click to collapse
He said he was trying to flash recovery and other ROMs to try and get it to work though too... You can't flash custom recovery without being S-Off.
If you want to flash back the RUU, and go back to complete unrooted stock... then yeah, you want S-On.

carngeX said:
BTW, if you're S-On, how are you going to flash any recovery or ROMs? You need to be S-Off before you can flash anything.
Click to expand...
Click to collapse
Untrue, you can flash ROMs without being S-OFF. I was rooted and flashing ROMs before unrevoked released "forever."
Sent from my Droid Incredible running a random CM7 nightly.

it seems the problem is more serious then i imagined... I cant seem to use my phone.. when i connect it to the computer its unrecognizable and I cant do anything with it

SteveG12543 said:
Untrue, you can flash ROMs without being S-OFF. I was rooted and flashing ROMs before unrevoked released "forever."
Sent from my Droid Incredible running a random CM7 nightly.
Click to expand...
Click to collapse
So were the images previous to Unrevoked's S-Off patch just signed properly? I didn't get a DINC and root it until after Unrevoked had released their patch.
eljean said:
it seems the problem is more serious then i imagined... I cant seem to use my phone.. when i connect it to the computer its unrecognizable and I cant do anything with it
Click to expand...
Click to collapse
Like I said previously, 5 vibrates is usually a hardware issue, meaning you're most likely going to have to send it in for replacement. There's been a few people to recover from a 5-vibrate brick, but they had gotten lucky. You can search the forums and try to find how they fixed it (can't remember the thread off hand, just do a search for 5 vibrates and you'll get lots of results).

carngeX said:
So were the images previous to Unrevoked's S-Off patch just signed properly? I didn't get a DINC and root it until after Unrevoked had released their patch.
Click to expand...
Click to collapse
I guess so, idk tbh lol. I've had my Inc since day one, and rooted it rather early.
Sent from my Droid Incredible running a random CM7 nightly.

yeah except i bought off ebay so i cud flash to boost. and i did but then i got too curious and ended up with bad nv items on the phone fixed it, then my meid came as <not available> (which still remains and i believe is the problem) and now this... i cant unplug my fone or it will die on me...
i need to get S-OFF and i might be able to fix it... any ideas on how to do this through HBOOT

i need to flash a rom thats what i need to do, because ihave no drivers.., thats the hardware issue and my meid but thats not importatn

Try using unrevoked while the phone is plugged in and in fastboot/hboot?

k_nivesout said:
Try using unrevoked while the phone is plugged in and in fastboot/hboot?
Click to expand...
Click to collapse
How can this be possible? Can you just show me a quick summary and show me links to this method of rooting
Sent from my ADR6300 using XDA App

Just google unrevoked and download the unrevoked tool. I thought it did its thing in fastboot, but I could be wrong. Its worth a shot.
And BTW, its not really necessary to be posting multiple threads in multiple forums, it would be easier for you to just check one thread.

fixed it
http://forum.xda-developers.com/showthread.php?p=14440621

k_nivesout said:
Just google unrevoked and download the unrevoked tool. I thought it did its thing in fastboot, but I could be wrong. Its worth a shot.
And BTW, its not really necessary to be posting multiple threads in multiple forums, it would be easier for you to just check one thread.
Click to expand...
Click to collapse
Oh no is I bought 2 bricked phones from ebay as a wholesale and im trying to fix both of them which have different issues.

eljean said:
fixed it
http://forum.xda-developers.com/showthread.php?p=14440621
Click to expand...
Click to collapse
oh **** theres a fix for this lol i never knew

JoelZ9614 said:
oh **** theres a fix for this lol i never knew
Click to expand...
Click to collapse
Yeah the guide was released last month
Sent from my ADR6300 using XDA App

simi brick?

I have hw 003 hboot 2.10. I can enter hboot but not recovery. during normal boot phone just shows evo boot screen and boot loops. same thing when I try to enter recovery. I was s-off but after trying some methods in other brick threads I ended up with s-on.
I was using miui 2.2.3 when I turned it rebooted into recovery to make a nand and that is when the loops started. I have tried several ruu's with no luck on getting it to boot. was going to try the lastest ruu but not sure if I should.
I am flashed for cricket so there is not the option of bricking and returning to sprint for a replacement.
Edit: was not using twrp. Ar 2.3 was my recovery. As stated earlier I tried several ruu's in pc36img.zip.

If you can get to hboot you are not bricked. Have you tried using a pc36img of a stock rom in the hboot? This should boot you to a stock rom, thus allowing you to re-root and get your recovery back.

sitlet said:
If you can get to hboot you are not bricked. Have you tried using a pc36img of a stock rom in the hboot? This should boot you to a stock rom, thus allowing you to re-root and get your recovery back.
Click to expand...
Click to collapse
You can be bricked and still get in hboot Twrp2.0 did it to a few phones, the partitions end up screwed up and you can boot to hboot but no recovery or system not sure which partition gets borked but I think its the misc partition
We are legion, for we are many

Where is Captain_Throwback to save the day and another evo once again

Oh I am sure Captain will save the day soon as he always does.
That does not sound like fun man, sometimes the evos get crazy and there is nothing you can do about it. Did you do anything different before you had this issue? flash any files, adjust any system settings or mess with the hardware in anyway?

stevovanburen said:
Oh I am sure Captain will save the day soon as he always does.
That does not sound like fun man, sometimes the evos get crazy and there is nothing you can do about it. Did you do anything different before you had this issue? flash any files, adjust any system settings or mess with the hardware in anyway?
Click to expand...
Click to collapse
No i had been running miui for a few days and was getting prepared for the next update by doing a nand. I rebooted to recovery with the reboot option in the rom. Then bang boot loop city here i am. Just tried the newest ruu pc36img.zip and still nothing. Going to get it unlocked later and see if I can reflash .img files through fastboot.
Sent from my M865 using XDA App

You weren't using twrp2.0 were u? If you were more than likely SOL that's one of the main reasons twrp for the evo is no longer supported even tho it works great on other devices like the kindle fire and 3vo I use it on the KF which I have running cm9 which I just got running on the evo as well now I gotta get my kernel fixed for this thing, have you tried reflashing your recovery? Or using adb to push a boot.img
Sent from my PC36100 using xda premium

evo4gnoob said:
Where is Captain_Throwback to save the day and another evo once again
Click to expand...
Click to collapse
I know. Captain has become the shaman of the Evo. He needs a special title, like Honorary Genius, or something.
sent from AOKP heaven

You guys flatter me .
I don't have any experience with MIUI, though. It's the one ROM I've never tried, but if it's an AOSP ROM, then the bootloop of death is always a possibility.
We haven't had any success rescuing anyone in that scenario, unfortunately. Flashing the ENG HBOOT will allow you to run fastboot commands, though, so that's probably the first step if you want to flash stuff through fastboot.
If you can't get adb working, then there probably isn't much hope. Since you ended up S-ON, and now without a custom recovery, I don't think there's much you can do. Perhaps others with a similar issue can chime in, but as far as I know, there's no current solution. The only way I'd know for sure is having the phone in my hands personally, but I doubt that's a possibility. I haven't personally experienced this bootloop thing, but it sounds scary .

jlmancuso said:
No i had been running miui for a few days and was getting prepared for the next update by doing a nand. I rebooted to recovery with the reboot option in the rom. Then bang boot loop city here i am. Just tried the newest ruu pc36img.zip and still nothing. Going to get it unlocked later and see if I can reflash .img files through fastboot.
Sent from my M865 using XDA App
Click to expand...
Click to collapse
Ok so I have unlocked the bootloader from the htcdevelopers site and i can now use fastboot commands and have tried flashing the recovery. I see it load and write to the phone only thing is that it makes no difference. I still just get the boot loop.

Hate to say it, my friend, but I think it's the end of the road for that phone

HipKat said:
Hate to say it, my friend, but I think it's the end of the road for that phone
Click to expand...
Click to collapse
maybe but i will keep trying till the phone catches fire in my hands. I dont know the meaning of "quit". I read last night in a xda thread about a possible fix by this guy and some people said it would just brick the phone and others say it works. only thing is i have been unable to find that thread again. it had a link to some evo.docx file.

jlmancuso said:
maybe but i will keep trying till the phone catches fire in my hands. I dont know the meaning of "quit". I read last night in a xda thread about a possible fix by this guy and some people said it would just brick the phone and others say it works. only thing is i have been unable to find that thread again. it had a link to some evo.docx file.
Click to expand...
Click to collapse
I assume you're referring to this thread: http://forum.xda-developers.com/showthread.php?t=1480630
Have fun trying! Many have tried, and I think only 1 ever succeeded.

thanks captain.

capn, thanks for the link! I've had that README_EVO.docx file on my SD for god-knows-how-long and have always wondered where in the hell I got it lol (and 'why').
@jlmancuso
Good luck, but condolences as well. My $ says, if Cap'n can't fix it, it likely can't be fixed (on Evo). Seems that guy has explored every RUU, Hboot, recovery, NV, Radio, kernel etc. He could probably BUILD an Evo, HW and SW lol.
sent from AOKP heaven

Captain throwback just the person i want to see lol i have a evo with 2.18 hboot
with s-on the phone keeps boot looping wrote the wrong nv to the phone now its boot looping also used the latest ruu top no avail still boot loops now is there a way i can repair the nv please help me with your guiding light and also this phone is not rooted or no roms its all stock also says in purple at the top ***LOCKED (00w) *** what ever that means ??

fatalfury said:
Captain throwback just the person i want to see lol i have a evo with 2.18 hboot
with s-on the phone keeps boot looping wrote the wrong nv to the phone now its boot looping also used the latest ruu top no avail still boot loops now is there a way i can repair the nv please help me with your guiding light and also this phone is not rooted or no roms its all stock also says in purple at the top ***LOCKED (00w) *** what ever that means ??
Click to expand...
Click to collapse
I think someone else was able to fix this problem . . . there's a thread around here somewhere. I'll try and find it.
EDIT: This is the thread - you'll probably want to read the whole thing, and if you have issues, maybe you can PM the guy that got it working.
The potential problem I see for you is that you're S-ON and bootloader is locked. You're probably going to have to unlock your device with HTCDev.com before you can make any headway. How were you able to write NV items to the phone? Don't you have to be S-OFF to do that?

Captain_Throwback said:
I think someone else was able to fix this problem . . . there's a thread around here somewhere. I'll try and find it.
Click to expand...
Click to collapse
i remember you had them downgrade to the ENG hboot and they were able to use fastboot to change the NV ?

evo4gnoob said:
i remember you had them downgrade to the ENG hboot and they were able to use fastboot to change the NV ?
Click to expand...
Click to collapse
Yup. I updated my post above with the thread, but that guy was S-OFF, so it was actually possible. Not much you can do with S-ON and locked bootloader.

Captain_Throwback said:
Yup. I updated my post above with the thread, but that guy was S-OFF, so it was actually possible. Not much you can do with S-ON and locked bootloader.
Click to expand...
Click to collapse
use HTC dev to unlock then use your guide to downgrade then root with revolutionary then downgrade hboot ?

[Q] Radio borked? Please help!

I am at a loss of things to try with this Evo which I have no history of.
After initially being stuck at 4-triangles. I managed to flash the ENG 0.76 bootloader. Found out that:
S-OFF
Radio: 2.15.00.09.08 -some sort of Chinese radio?
I've tried it many different ways with RUUs, fastboot and PH36IMG, but RADIO_V2 repeatedly fails to flash.
I can also flash any recovery, but it fails to load, getting stuck at the Evo splashscreen, so that is also a problem. Most partitions flash nicely in fastboot. A successful system flash will result in a stuck Evo splashscreen, though.
Is there any way out of this? Perhaps by using one of the elevated commands in the ENG bootloader? I don't know how to get ADB running either, since I'm stuck in fastboot and have no idea whether USB debugging was on earlier. I do have a Linux box if that helps.
Any help would be greatly appreciated. Thanks!

Its a PC36IMG* not PH36IMG
Sent from my SPH-L710 using xda premium

Typo, sorry.
Sent from my Galaxy Nexus using xda premium

I might need to clarify a little.
I have absolutely zero history of this phone. None whatsoever.
1. Currently on ENG 0.76. I received the phone with no access to the bootloader, stuck at the HTC screen with triangles in each corner. I flashed the ENG 0.76 hboot via fastboot and that's what I'm on right now. Works fine.
2. I have no idea how it got to this radio version. Seems like a Chinese UIM radio. Got the phone from a friend who got it from an auction in Burma.
4. Flashing any radio in hboot will result in [see attachment]. Flashing in fastboot- see 2nd screenshot above. Fails either way, and I've tried multiple radios. Tried under multiple hboots, too. No dice.
5. Stock or custom recovery will flash fine but will get stuck at the white splashscreen if I try to enter it.
6. Bootloader is perfect. Works like a charm.
The only idea I can come up with is using an elevated command in fastboot oem which could reformat my radio partition somehow. I don't know whether I have ADB either. I have some experience with diag mode and JET on the HOX.
Any ideas?

Have you tried an RUU? That may work and give you an entire stock unrooted and fully working system. If not, try flashing a different radio. That one could be out of date or even corrupt.
Sent from my SPH-L710 using xda premium

death-by-soap said:
Have you tried an RUU? That may work and give you an entire stock unrooted and fully working system. If not, try flashing a different radio. That one could be out of date or even corrupt.
Click to expand...
Click to collapse
I've tried countless RUUs, both Froyo and GB, Windows exe and PC36IMG. Nothing works. All partitions flash fine BUT the radio.

temuryusuf said:
I've tried countless RUUs, both Froyo and GB, Windows exe and PC36IMG. Nothing works. All partitions flash fine BUT the radio.
Click to expand...
Click to collapse
Is it possible for you to update the hboot to something 2.10? It may be the bootloader is preventing that flash.
Sent from my SPH-L710 using xda premium

death-by-soap said:
Is it possible for you to update the hboot to something 2.10? It may be the bootloader is preventing that flash.
Click to expand...
Click to collapse
Obviously this is not the only hboot I've tried. I've gone to 2.10, even 2.18, tried there, come back down to ENG, tried again; it's just repeatedly failing. I'm not giving up hope due to the simple fact that the bootloader works and there MUST be a way out. Like I mentioned earlier I'm thinking one of the high level commands, but I have no idea what to do with them. Could anybody lead me in the right direction?

Flashing the engineering Hboot 0.76 will only work on the older Evos with the older hardware partitions without causing permanent damage. If you have one of the newer ones, then your phone is already done.
Sent from my SAMSUNG-SGH-I747 using xda premium

shortydoggg said:
Flashing the engineering Hboot 0.76 will only work on the older Evos with the older hardware partitions without causing permanent damage. If you have one of the newer ones, then your phone is already done.
Click to expand...
Click to collapse
I've only recently put 0.76 on after trying the newer Hboot versions. I found out that I was on 2.02 initially when I had the 4 triangles- I had to RUU because there was no accessible Hboot to fall back upon anyway. I then found a 2.02 img and flashed that through fastboot, which is when the bootloader actually started working. I'm using 0.76 now because it just seems to work better with commands.
What exactly does "permanent damage" imply in this case? Because the problem remains either way- RADIO_V2 fails to flash. All other partitions have not a single problem between them.
Is there a way where I can completely clear out the emmc, repartition it correctly and take steps from there?
At this point of time I'm rather certain mine is an older HW revision. How do I find out anyway?

The newer hardware started with Hboot 2.02 while the old ended with 0.97. You would never OTA to 2.02 from 0.97, but have went directly to 2.10 unless you flashed a Hboot with 2.02 or ran a RUU with that Hboot version. I actually made a post about a year and a half ago on how to tell, so if you phone ever boots again, I could point you to that post.
Right now, it's good that Hboot 0.76 seems to be doing something, but I'm afraid the radio may have been flashed with something that did not want to be there.
Sent from my SAMSUNG-SGH-I747 using xda premium

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