Related
I have an HTC Incredible that i ran the first unrevoked2 update to get root on my device, then unrevoked3 to get s-off. I then was pushed the 2.2 OTA update, which when done through the phone fail. So, like an idiot of course, I ran the update.zip from clockworkmod and now my device is acting all strange (practically bricked).
After the update, the 'droid' eye loads, then goes to a white HTC page where a small dialogue box goes from 0 to 95% then reboots, repeatedly, until I interrupt this via a battery pull. I then get into my phone, but the camera, sdcard, wifi, etc are not recognized. Eventually I get a force close prompt for 'system' which I can wait or force close, either choice, my device will reboot at max 5 minutes.
I have the following showing at HBOOT
Incredible XC Ship S-ON (i ran the s-on update now)
HBOOT-0.77.0000
...
RADIO-2.15.00.07.28
I'd like to get my phone either running Froyo, or back to the stock ROM, and am in need of help. I've ran several PB31IMG.zip files located through numerous guides and dozens of searches to try and get back to stock, but I either get 'update failed' because of some kind of version check, or the update doesn't work (maybe now because I'm s-on?).
I'm in sad need of help, I found another thread where someone else was in my similar situation on another forum but its old, no one is responding, and the update worked for them and not myself. I'd really appreciate it if someone would walk me through un-screwing my device if possible. Much appreciated.
alright well if i was you i would do this.
turn security back off (s-off)
grab the PB31IMG.zip for 2.2 froyo/ or if you want the ota again grab the 2.1
then it should work fine. but i also see the your hboot is not up to date for froyo so maybe find the PB31IMG.zip for 0.92 hboot. i dont have any idea about where it is located but i have the file for 2.2. but alas, i dont have a place to upload it soo yeeaaah. anyway that is what my first choice would be. choose to follow or not.
p.s. i know i say but alot haha
BTW yes, PB31IMG's wont work because you are s-on. and the ota probably did not work because you had clockworkmod recovery instead of stock recovery. thats all i got for ya. hope my terrible explanations help
Well, this might be more promising.
I did notice that my HBOOT was quite out of date, so amongst all of the files I've downloaded, I'm pretty sure the one that might have done it for me was the RUU update file. I of course re-ran the s-off update from unrevoked-forever, then started hacking away at the RUU update. I downloaded the RUU update from Google, ran it, copied the rom.zip file from the temporary files location, renamed it to PB31IMG.zip, copied it to the root, and then poof, noticed the HBOOT was updated (looks like this could have been the root problem).
Needless to say, i'm back to setting up my device (raw), hope that I can still get to root on my device; but at least I'm back to an operating phone!
OK
Looks like I'm at HBOOT-0.92.0000 with IncredibleC XC ship S-OFF still; RADIO-2.15.00.07.28.
Doesn't look like I have a recovery mode (clockworkmod).
I'm guessing if I'm going to root my device I'll need to re-install clockworkmod? Thanks for any future help.
so you still have the reboot thing, going on
Sent from my ADR6300 using XDA App
tjamscad said:
so you still have the reboot thing, going on
Click to expand...
Click to collapse
No, my device is unbricked (so to speak). Since updating using the full RUU it successfully re-flashed everything. Only problem I have to fix now is rooting my device again.
Well I guess I have my work cut out for me searching how to get my s-off phone rooted again. Anyone got a suggestion?
Sent from my ADR6300 using XDA App
if your phone is s-off then search around for a custom recovery in the pb31img format. flash in bootloader, reboot into recovery and flash the rooted rom of your choice.
So my fix was:
1. Ensure phone is already rooted and S-OFF
2. download RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Radio_2.15.00.07.28.exe
3. Run the RUU file
4. Go to my temporary files location, sort by date, and look for the rom.zip file
5. copy that file off someplace else and rename it PB31IMG.zip, cancel RUU Update program
6. Copy PB31IMG.zip to the root of the SD Card
7. Boot my device holding volume down (HBOOT)
8. Allow the update to proceed (will reboot phone almost immediately to update HBOOT from 0.77 to 0.92)
9. Once update was completed, phone reboots final time after prompt
10. Setup phone again (RUU Update is a clean flash)
Still looking out for better instructions on how to re-root my device other than a manual one, but if I must then I must =) Was hoping that I could use unrevoked3, but the last push didn't work out.
you have to do it manually cause unrevoked doest work on newest ota
I can help you reroot if you need it. Im glad you have everythig else worked out though. Congratulations!
sent from Ioslver
ok well basically load this in bootloader and you are rerooted.
the download link for the file is here:
http://www.mediafire.com/?oj6aqi1ceqpm58g
patalo said:
ok well basically load this in bootloader and you are rerooted.
the download link for the file is here:
http://www.mediafire.com/?oj6aqi1ceqpm58g
Click to expand...
Click to collapse
So that PB31IMG.zip (renamed) will re-install the most recent clockworkmod recovery? I saw some other post which also had a 'payload-update.zip' and a 'su-2.3.2.1-ef-signed.zip' file ... not sure if I'm missing something.
Also, according to their latest release (their = unrevoked), http://unrevoked.com/rootwiki/doku.php/public/unrevoked3 - This supposedly works with all versions of supported phones. Of course, when I go to http://unrevoked.com/rootwiki/doku.php/public/unrevoked2 it says that unrevoked3 doesn't work with stock Android 2.2 phones... which I'm guessing might be my condition since I had to flash the rom.zip file from RUU_Incredible_C_Froyo_VERIZON_WWE_3.21.605.1_Radio_2.15.00.07.28_2k4k_NV_1.50_PRL58006_release_143351_signed.exe that I got from google.
Some clarification would be appreciated.
Looks like I'm back to root. Ran the PB31IMG.zip that was about 2.86mb, then payload-update.zip and the Su zip (anyone know where the most recent one is? Says there is an update).
Now to test WiFi tether again, see if I still need that evo driver still.
Sent from my ADR6300 using XDA App
You don't need the payload and stuff. After s-off all you need is the clockworkmod PB31IMG.zip to get root back
sent from Ioslver
The wifi tether has nothig to do with root. On some roms or just sometimes it wont work.
sent from Ioslver
I Have a Question, Would it be Possible to Root the Phone With a Update.zip From Android Recovery, Where it Says (Install From Update.zip)? Either That or Turn S-Off, Or Install Su, Clockwork Recovery...... Something? If Someone Can Help Please Do!! Or If Someone Can Try to Sign a Update.zip For Me With S-Off in it!! (Unrevoked.4Ever) I'd Loveto Find a Easier way that can be Done WITHOUT CONNECTING TO A (USB) PORT PC!!
Technically no. Because rooting your device is getting rid of the stock recovery so you can install rims and whatnot. But you can root through hboot easily with s-off or with s-on use unrevoked.
sent from Ioslver
So I'm wondering if the payload-update.zip was damaging in some way.
In any event, now I'm constantly being nagged about another 17.7mb update from Verizon which of course, like the Android 2.2 update, won't apply via the usual system update message.
I don't know where I can find this file, but it says this:
---
Android Update
Downloaded and verified 17.7 MB
This software update includes the installation of V CAST Apps, Slacker, and many other improvements for your DRIOD Incredible by HTC. ... blah blah blah ...
---
I don't know if this is the infamous 'November' update or not. I know that I updated my rom from the RUU file downloaded from dl.google.com, so its possible that I don't have this patching. Some clarification on what this download is, where I can find it (online or my phone), and if it is possible to apply this update and how (so I don't keep getting annoyed with it).
I have a fairly strange problem. My wife got tired of the Verizon bloatware on her Dinc2 so I offered to root and flash it to a nice rom. Her only requirements were that it work both as a phone and as a camera. After an uneventful downgrade, s-off, root and CWM, we tried aeroevan's unofficial CM9. We found that the camcorder was broken. Next we tried the MikRoms Incredible 2 HD Rls1. This worked beautifully in every respect except one: when I rebooted the phone, it went into a loop. The phone would boot to the opening lock screen.. in some cases I could even unlock it.. and then either turn off or reboot (which one seemed random). After getting back into the bootloader, I tried all the obvious things:
Wiping all partitions
Reloading the ROM
Trying a different ROM
Flashing back to a Stock ROM + root
Flashing back to stock 2.3.3.
In every case, the phone works perfectly with the new ROM up until it is rebooted, after which it goes into a loop at the lockscreen. The only ROM that DOES work is aeroevan's unofficial CM9. It reboots without any issues, but of course the camcorder and camera flash are busted there. At least it's usable as a phone again.
I've looked and looked, and either my google-fu is failing me utterly or this is a fairly unusual problem. Does anyone have the faintest idea what's going on here and how I can work at fixing it?
This is a well known issue with 605.05 software phones (and several other threads already about this). There is a PSA in Development warning this issue exists. Only guaranteed ROMs without issue are AOSP ROMs. If you want working camera, flash CM7.
I have also heard that flashing the radio packaged with the latest software may fix the issue, you can give that a try. You could also try flashing Condemned Soul's 6.xx ROM in development section.
Sent from my ADR6425LVW using Tapatalk 2
Yah, right after I posted this I saw this:
http://forum.xda-developers.com/showthread.php?t=1746490
Sorry about that. Thanks for the info!
I can confirm that flashing the radio to version 1.09.01.0312 as detailed here resolved the reboot-at-locksceen issue. Using the Incredible 2 HD Rls 1.1 ROM, we now have a working phone, a working camera, and a happy wife!
Thanks!
Verteiron said:
I can confirm that flashing the radio to version 1.09.01.0312 as detailed here resolved the reboot-at-locksceen issue. Using the Incredible 2 HD Rls 1.1 ROM, we now have a working phone, a working camera, and a happy wife!
Thanks!
Click to expand...
Click to collapse
I bet the biggest plus is the happy wife part huh?
Sent from my Incredible 2 using xda app-developers app
Verteiron said:
I can confirm that flashing the radio to version 1.09.01.0312 as detailed here resolved the reboot-at-locksceen issue. Using the Incredible 2 HD Rls 1.1 ROM, we now have a working phone, a working camera, and a happy wife!
Thanks!
Click to expand...
Click to collapse
Glad flashing the new radio got it sorted out!
fsiddique said:
Glad flashing the new radio got it sorted out!
Click to expand...
Click to collapse
Perhaps you can help me sort out an issue. I tried rooting and getting S-Off by using the tacoroot, and flashing a new radio method. I got to the radio part, and got the radio onto the root of the sdcard as per the instructions. The phone boots into fastboot, and it checks the radio file, but it says incorrect file a few times, and then returns to the fast boot menu. I didn't know if it worked, or not so i tried to reboot the phone normally but at the lock screen it reboots.
I tried pushing the radio file using adb but it doesnt seem to want to connect to the phone anymore.
I followed these instructions http://forum.xda-developers.com/showthread.php?t=1751796
After going through some fastboot options I flashed the recovery from fastboot and it booted up and stayed booted, i'm assuming i have to start over, which I don't care about, I just need some advice about what is up with the radio not wanting to flash.
wexx2504 said:
Perhaps you can help me sort out an issue. I tried rooting and getting S-Off by using the tacoroot, and flashing a new radio method. I got to the radio part, and got the radio onto the root of the sdcard as per the instructions. The phone boots into fastboot, and it checks the radio file, but it says incorrect file a few times, and then returns to the fast boot menu. I didn't know if it worked, or not so i tried to reboot the phone normally but at the lock screen it reboots.
I tried pushing the radio file using adb but it doesnt seem to want to connect to the phone anymore.
I followed these instructions http://forum.xda-developers.com/showthread.php?t=1751796
After going through some fastboot options I flashed the recovery from fastboot and it booted up and stayed booted, i'm assuming i have to start over, which I don't care about, I just need some advice about what is up with the radio not wanting to flash.
Click to expand...
Click to collapse
Check the md5sum, might be a bad download. You won't need to start over if you're S-OFF already, you can always flash an AOSP ROM to get it working and go from there.
prototype7 said:
Check the md5sum, might be a bad download. You won't need to start over if you're S-OFF already, you can always flash an AOSP ROM to get it working and go from there.
Click to expand...
Click to collapse
Thanks for the quick reply!
I don't know how to check the md5 without adb. Can I do that without communication to the phone.
How can I determine if I'm S-OFF, or flash a rom? For that matter, how do i start over if i need to.
wexx2504 said:
Thanks for the quick reply!
I don't know how to check the md5 without adb. Can I do that without communication to the phone.
How can I determine if I'm S-OFF, or flash a rom? For that matter, how do i start over if i need to.
Click to expand...
Click to collapse
You can check the md5sum from the phone, just use terminal emulator (might need busybox installed). To check if you are S-OFF, boot into the bootloader and it should say S-OFF.
Sent from my Incredible 2 using Tapatalk 2
I've noticed that I can use fastboot commands, (sorry, never had this complex of a root job before. Normally they are one-clicks) Anyway, I look at the top of the screen when its sitting in the fastboot screen and it says VIVO_W XB Ship S-ON RL I assume that means I'm not S-OFF, and its back to square one. Right?
wexx2504 said:
I've noticed that I can use fastboot commands, (sorry, never had this complex of a root job before. Normally they are one-clicks) Anyway, I look at the top of the screen when its sitting in the fastboot screen and it says VIVO_W XB Ship S-ON RL I assume that means I'm not S-OFF, and its back to square one. Right?
Click to expand...
Click to collapse
Yep. What's the hboot version?
Sent from my Incredible 2 using Tapatalk 2
prototype7 said:
Yep. What's the hboot version?
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
HBOOT 0.98.0000
in case you want this info too.
Radio - 1.09.01.1111
I tried going back to stock using the following guide http://forum.xda-developers.com/showthread.php?t=1599767
now i have ***LOCKED*** when i boot into fastboot,and i still have the crazy reboot issue when the phone displays the lock screen.
wexx2504 said:
HBOOT 0.98.0000
in case you want this info too.
Radio - 1.09.01.1111
I tried going back to stock using the following guide http://forum.xda-developers.com/showthread.php?t=1599767
now i have ***LOCKED*** when i boot into fastboot,and i still have the crazy reboot issue when the phone displays the lock screen.
Click to expand...
Click to collapse
\
I am at this exact same radio, firmware version, hboot version and situation too any help would be greatly appreciated. Trying to help a co-worker fix his wife's device.
After many hours of reading threads and trying different things, I am posting this.
I have HTC Incredible
Incredible XC Ship S-On
HBoot 0.92.0000
Radio: 2.15.10.07.07
Recovery: CWM v2.5.0.5
Was running Cyanogenmod 7
All was great with this phone (about 1 year) until it randomly started to constantly reboot 1 month ago. I tried to follow some other threads by downloading PB31IMG files, adding them to FAT32 sd card and running in HBOOT. I tried first upgrading the cyanogenmod7, then going to froyo 2.2 and a GB one. Some threads mentioned changing radio version first, tried that but nothing.
When I load PB31Img files from SD, froyo 2.2 says something along the lines of main version old.
When I try to change radio, PB31Img starts to load but does not let me continue and returns to HBoot with no new radio.
I am really not familiar with any phone and I would like to get this back to working. Any help is appreciated, but please be very clear. All I want is this phone to go back to stock, unrooted is fine. Anything to make it work.
Thanks,
griplegraple
griplegraple said:
After many hours of reading threads and trying different things, I am posting this.
I have HTC Incredible
Incredible XC Ship S-On
HBoot 0.92.0000
Radio: 2.15.10.07.07
Recovery: CWM v2.5.0.5
Was running Cyanogenmod 7
All was great with this phone (about 1 year) until it randomly started to constantly reboot 1 month ago. I tried to follow some other threads by downloading PB31IMG files, adding them to FAT32 sd card and running in HBOOT. I tried first upgrading the cyanogenmod7, then going to froyo 2.2 and a GB one. Some threads mentioned changing radio version first, tried that but nothing.
When I load PB31Img files from SD, froyo 2.2 says something along the lines of main version old.
When I try to change radio, PB31Img starts to load but does not let me continue and returns to HBoot with no new radio.
I am really not familiar with any phone and I would like to get this back to working. Any help is appreciated, but please be very clear. All I want is this phone to go back to stock, unrooted is fine. Anything to make it work.
Thanks,
griplegraple
Click to expand...
Click to collapse
Since you're s-on, it's useless to try flashing radios. You're very limited as to what you can do, as you're finding out. Your best bet would be to try the latest RUU (also known as PB31IMG.zip) from here:
http://dinc.does-it.net/Stock_Images/4.08.605.15/
You should be able to flash that through HBOOT even though you are s-on, as it is a stock image.
If you can't get any of the stock images to flash, the next line of attack would be to upgrade HBOOT and unlock the bootloader using HTCdev, as described in this guide:
http://forum.xda-developers.com/showthread.php?t=1600904
If you follow the instructions for downgrading, you will be able to flash the stock image of your choice. Then, re-lock the bootloader using HTCdev and you will be back to stock. Of course, if you follow the whole guide and get s-off, you'll have a lot more options of ways to tackle problems like this.
musical_chairs said:
Since you're s-on, it's useless to try flashing radios. You're very limited as to what you can do, as you're finding out. Your best bet would be to try the latest RUU (also known as PB31IMG.zip) from here:
http://dinc.does-it.net/Stock_Images/4.08.605.15/
You should be able to flash that through HBOOT even though you are s-on, as it is a stock image.
If you can't get any of the stock images to flash, the next line of attack would be to upgrade HBOOT and unlock the bootloader using HTCdev, as described in this guide:
http://forum.xda-developers.com/showthread.php?t=1600904
If you follow the instructions for downgrading, you will be able to flash the stock image of your choice. Then, re-lock the bootloader using HTCdev and you will be back to stock. Of course, if you follow the whole guide and get s-off, you'll have a lot more options of ways to tackle problems like this.
Click to expand...
Click to collapse
The first option above worked in my case. Phone is able to load up and seems to be working fine.
Thread moved. Please post all question threads here in Q&A in future.
Thanks
AvRS
Sent from my Nexus 4 using xda premium
griplegraple said:
Thanks for the reply. I will try the first option, but one thing I have noticed before is that when I use the adb method, I can't get "adb devices" command to work. It outputs "List of devices attached". In my device manager, I have ADB Interface ->HTC Bootloader with the android USB driver installed... Not sure if you can help on this.
Click to expand...
Click to collapse
That could be caused by having adb or the drivers improperly set up on your computer, or it could be because you didn't have USB debugging enabled in the phone's settings. You could try booting your phone into recovery and seeing if you can access it with adb from there if all else fails.
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
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?