Related
Hey all,
***ISSUE*** I can only boot into recovery or a ROM once. ***ISSUE***
I recently replaced my EVO through Sprint, and rooted. (unsuccessfully with unRevoked, but successfully with AutoRoot). After I used unRevoked (but before using AutoRoot) this issue started popping up.
I can flash a recovery image via Bootloader/Hboot or PARTICULAR ROMs, Sprint Lover's seems to be the most reliable, CM7 does not seem to work at all, and be able to access them once, and upon reboot I get the white "htc EVO 4G" screen and it hangs there until I reboot. Once that happens I cannot access recovery or boot into the ROM until I reflash from a PC36IMG.zip in Hboot/bootloader.
Here's my hardware info:
SUPERSONIC EVT2-3 ENG S-OFF
HBOOT-0.76.2000 (PC3610000)
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.11.19
Hardware Revision #3
My Evo was originally on HBOOT 2.10, but I flashed an eng-PC36IMG.zip that let me install the ENG bootloader on it, which has made it so things flash more reliably.
Anyone have any advice? It seems really odd to me that software would work once and not again. Any suggestions would be appreciated.
There could be something from the rooting process that's affecting your phone somehow, although that's really strange. I would suggest unrooting, getting fully back to stock, & rooting again. If you're not going to be able to reboot your phone without reflashing, which seems like a pain, it might be best to redo it.
Other than that, I'm baffled :/
Sent from my badass HTC Supersonic (Evo 4g) using XDA Premium App
Thanks for the reply, plainjane!
I am in the process of unrooting now to see if that works. I installed the unrevoked-son via ClockworkMod Recovery 3.0.0.5, but I still had S-OFF when I went to HBoot. I'm not sure, but I think I remember somewhere that the ENG bootloader does that.
Regardless, I'm installing the latest (3.70) RUU now and will see what that does.
RandomViolence said:
Thanks for the reply, plainjane!
I am in the process of unrooting now to see if that works. I installed the unrevoked-son via ClockworkMod Recovery 3.0.0.5, but I still had S-OFF when I went to HBoot. I'm not sure, but I think I remember somewhere that the ENG bootloader does that.
Regardless, I'm installing the latest (3.70) RUU now and will see what that does.
Click to expand...
Click to collapse
Yea, im pretty sure the. 76 eng hboot is permanently s off. Also, I was unaware that hboot version 2.1 was downgradeable, I thought it wasn't able to be changed. Interesting. Maybe that's part of your problem, im really not sure. Sounds annoying though. Hopefully unrooting and starting fresh will help.
Sent from my PC36100 using XDA App
Thanks for the reply k2buckley!
I've now run the S-ON tool and used the 3.70 RUU to unroot my Evo. After the RUU completed its process my EVO rebooted and has not left the white "HTC EVO 4G" screen. (EDIT: I checked in Hboot and am now S-ON and on the 2.10 bootloader.) I've let it run for about ten minutes now and I'm not hopeful.
Now that I have it in a state where I can return it to Sprint I don't think I'm going I'm going to mess with it any more. It's such a shame. My first Evo was wonderful until an odd software glitch bricked it, and now this. It's been a really frustrating couple of weeks.
After this experience I don't think I'll be using unrevoked again. I loved having the speed and features of CM7 on my first Evo, but I'm debating rooting at all at this point.
RandomViolence said:
Thanks for the reply k2buckley!
I've now run the S-ON tool and used the 3.70 RUU to unroot my Evo. After the RUU completed its process my EVO rebooted and has not left the white "HTC EVO 4G" screen. (EDIT: I checked in Hboot and am now S-ON and on the 2.10 bootloader.) I've let it run for about ten minutes now and I'm not hopeful.
Now that I have it in a state where I can return it to Sprint I don't think I'm going I'm going to mess with it any more. It's such a shame. My first Evo was wonderful until an odd software glitch bricked it, and now this. It's been a really frustrating couple of weeks.
After this experience I don't think I'll be using unrevoked again. I loved having the speed and features of CM7 on my first Evo, but I'm debating rooting at all at this point.
Click to expand...
Click to collapse
If you do, root it manually - save yourself from all these headaches of the autoroot programs.
Thanks for the advice Heaterz16!
I'd love to root manually to ensure everything goes well. The guide that I saw indicating how to manually root was taken down and linked to AutoRoot as the way to go. Could you point me towards a guide for manual rooting?
Take it back to Sprint. I had one that would rarely boot, it would take 20 or so tries. When it finally did boot, the screen would freeze up & I'd have to pull the battery. They gave me a new one, no questions asked & I had it the next day. That phone was never rooted, it was only two weeks old. I have insurance, so all of my replacements have been free. I had the one before that 3-4 weeks before the usb port gave out. I got my third one three months ago, rooted it, and have had no problems since. I hated the Evo for about a month when mine kept breaking.
I would also suggest manually rooting. The "one-click" methods are easy to do but difficult to troubleshoot. Manual methods are a little more difficult to do but cause far less problems.
Just remember to delete any evidence of rooting from your sd card or just remove it entirely before taking the phone to Sprint. I hope everything works out for you!
Sent from my badass HTC Supersonic (Evo 4g) using XDA Premium App
plainjane said:
Take it back to Sprint. I had one that would rarely boot, it would take 20 or so tries. When it finally did boot, the screen would freeze up & I'd have to pull the battery. They gave me a new one, no questions asked & I had it the next day. That phone was never rooted, it was only two weeks old. I have insurance, so all of my replacements have been free. I had the one before that 3-4 weeks before the usb port gave out. I got my third one three months ago, rooted it, and have had no problems since. I hated the Evo for about a month when mine kept breaking.
I would also suggest manually rooting. The "one-click" methods are easy to do but difficult to troubleshoot. Manual methods are a little more difficult to do but cause far less problems.
Just remember to delete any evidence of rooting from your sd card or just remove it entirely before taking the phone to Sprint. I hope everything works out for you!
Sent from my badass HTC Supersonic (Evo 4g) using XDA Premium App
Click to expand...
Click to collapse
Thanks for the advice. I plan to just go to Sprint without my SD card and tell them the situation.
If you could point me towards a good guide for manual rooting I'd be grateful. After this last experience I'd much rather just do it myself and ensure it goes correctly.
Unrevoked gives issues like this. Try to start with autoroot this time.
Do not try to downgrade your bootloader this time. Make sure you nandroid back up and flash different ROMs and ensure things are working before you set anything up. Also make sure you are wiping everything. I suggest using Caulkin's Format All and flashing that in recovery.
sekigah84 said:
Unrevoked gives issues like this. Try to start with autoroot this time.
Do not try to downgrade your bootloader this time. Make sure you nandroid back up and flash different ROMs and ensure things are working before you set anything up. Also make sure you are wiping everything. I suggest using Caulkin's Format All and flashing that in recovery.
Click to expand...
Click to collapse
Thanks for chiming in, sekigah84.
The reason I tried downgrading my bootloader last time was that the issue appeared consistently with the 2.10 bootloader (tried flashing various recoveries, ROMs, radio versions, etc, over four days on that bootloader) and I thought reverting to ENG 0.76 might help correct the problem. I was very careful about doing nandroid backups and wiping cache, dalvik before installing ROMs, etc. when I could access recovery. Restoring from a backup was never possible because upon reboot I'd simply get the white HTC screen.
The problem seemed to start immediately after using unrevoked and didn't go away regardless of what I flashed or how many times I RUUed.
I definitely won't use unrevoked again. I'd consider using AutoRoot, but I'd prefer just to do a manual root process, or maybe not root at all.
RandomViolence said:
Thanks for the advice. I plan to just go to Sprint without my SD card and tell them the situation.
If you could point me towards a good guide for manual rooting I'd be grateful. After this last experience I'd much rather just do it myself and ensure it goes correctly.
Click to expand...
Click to collapse
Here's a link for you. As you said, this post has been retired, and it links you to xhausx's autoroot, however it still contains all of the info and instructions, and that method will still work for you. It's not outdated yet. So if you want to run it manually, follow Zikronix's instructions within the first post of this thread. Have fun!
http://forum.xda-developers.com/showthread.php?t=829045&highlight=root
Ok guys, first of all I'll explain everything from the start.
Back in November I used AAHK to root, ENG S-OFF etc. my phone so that I could flash a custom rom. Installed Android Revolution HD.
A month ago or so I found the IceColdSandwich rom so I NAND-ed my AR and fresh installed that. And I kept switching between the 2 of them from time to time.
Found that there's a free download of clockworkmod touch on their website, but I couldn't flash it via fastboot. Gives me this:
sending 'recovery' (3554 KB) ... OKAY [0.641s]
writing 'recovery' ... FAILED (remote: not allowed)
Same thing happened when I tried to flash a new radio.
Stupid me, I reinstalled the recovery from ROM Manager again in the process as a last resort (dunno why I thought it would work >.< ).
Now the problems start, I was running AR 6.3.1 last night and I wanted to update the ICS rom, so I made a backup to AR rom and wanted to restore the ICS one. Told me the md5 wasn't correct or something. I instantly thought "GAH, probably because I reinstalled recovery." so I decided to finally install the clockworkmod touch if I had allready ****ed it up. Got the same bloody error:
"FAILED (remote: not allowed)"
So what did stupid old me think then? "Yeah, maybe I didn't ace hack it right the first time..." so I decided to use AAHK again. Logged in Linux, started the kit. All fine and well, said there "Rebooting, please wait". I was like "MMkay, I guess it will take a bit, I'm gonna go do something else" and forgot about it for a couple of hours. 2 hours later, same message in terminal, my phone still had the white background with HTC logo on it.
Ok, don't panic, what to do, what to do...disconnected my phone, pulled out the battery, rebooted into h-boot, hit recovery. The horror of it not being there
Rebooted into bootloader again, tried to flash recovery again, still the same message.
While I was there, desperately tried "Factory Reset", shows me a screen with a loading bar or something and next to it a micro sd card with upload download arrows on it (up and down arrows). Afterwords it proceeds to rebooting my phone 3 times and then it dies. Do I need some kind of file on my SD card for it to work or something?
I think I bricked it. :-<
Sorry for the long post.
Any kind of help is apreciated. Thanks guys
PS: H-BOOT says:
ACE PUT SHIP S-OFF RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.03.02.26_M
eMMC-boot
Apr 12 2011, 00:55:45
Hey dude.
Just a quick post, you have not bricked your phone so don't panic.
More in a mo.
Greg.
Sent from my Desire HD using Tapatalk
Search this forum for a stock PD98IMG.Zip ideally a 1.32 one.
Copy this to your sd card, then boot into hboot.
Hopefully hboot will recognise the image and install it on your phone.
Can anyone qualify/dispute this?
Cheers.
Greg
Sent from my Desire HD using Tapatalk
Thanks Greg. I'll find the image and tell you in a min if it worked
It has to be an RUU that fits your phone. Do NOT flash a froyo RUU on a phone that was shipped with stock gb. An RUU will revert the phone to stock. After that you should have no probs running AAHK again to gain s off.
Sent from my HTC Desire HD with Beats Audio using XDA App
Bought my phone in December 2010, it was shipped with Froyo 2.2. I updated it myself to Gingerbread (only later I found out how dumb that was) so I guess it's okay if I flash a 1.32, right?
Good Guy Greg, I love you man I can use my phone again, thank you so very much!
I have just a question though. Is it by any chance possible to create a PD98IMG.Zip to revert my phone to something more recent? Can I use it to create something like a NAND backup?
dragancla said:
Good Guy Greg, I love you man I can use my phone again, thank you so very much!
I have just a question though. Is it by any chance possible to create a PD98IMG.Zip to revert my phone to something more recent? Can I use it to create something like a NAND backup?
Click to expand...
Click to collapse
Glad to help dude.
I think that as long as your phone turns on, even if it bootloops etc... you haven't bricked it.
I think it is possible, but I'm not totally sure how to create a PD98IMG.ZIP.
But I'd suggest is you want something more recent, just flash a new ROM.
Once you are back to stock (this may have broken root) check to see if you're still rooted, if not re root and use CWM Recovery to flash whatever ROM you want.
Regards.
Greg.
Sent from my Desire HD using Tapatalk
Thanks again, mate I used the AAHK again and I flashed my old rom back, but I still can't flash a different radio or the touch recovery...same error: "writing 'recovery' ... FAILED (remote: not allowed)"
Oh well, glad to have my phone back :>
You can't flash a radio with the way you are doing it (ie fastboot) unless you have the engineering bootloader (Eng soff). For.those of us with just soff we flash them via a pd98img formatted zip. Much easier in.my opinion as you can flash a radio without a PC.
One thing to note is that if your phone cane shipped with gb, DO NOT install the engineering bootloader as it will mess you up big time and cause your phone to.take30 min to boot up. Its fixable but its a pita
dragancla said:
Thanks again, mate I used the AAHK again and I flashed my old rom back, but I still can't flash a different radio or the touch recovery...same error: "writing 'recovery' ... FAILED (remote: not allowed)"
Oh well, glad to have my phone back :>
Click to expand...
Click to collapse
Why not buy the Touch upgrade from ROM Manager?
Greg.
Sent from my Desire HD using Tapatalk
TeamDraven said:
Why not buy the Touch upgrade from ROM Manager?
Greg.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
It's not fun if I don't do it myself It's like saying "Yeah, you ****ed up your phone, better take it to the local repair guy" but thanks to you I learned how to downgrade my phone back to stock and start over, even if I dont have recovery installed any more. I consider learning from trial and error better than having people do it for you...that and I've always wanted to learn to flash .img files like recovery, radios, 4ext themes etc. But I'm glad to report that I have ENG S-OFFed my phone since then and flashed all I need :>
Thanks again, Greg :>
I get what you are saying dude.
But there's no harm in supporting a developer.
Cheers dude.
Greg.
Sent from my Desire HD using Tapatalk
Desire HD brick
Hi, I have similar problem as dragancla with small differences.
I did root my Desire HD too, but in Ace advanced hack kit. I di mSD card as goldcard, next a put PD98IMG.zip (1.32.X) on sdcard. Then I started with root first three steps going well. After succesfully installing root, clockworkmod and first radio start next step flash new radio and here was the problem. Connection with PC fell and flashing was stoped. Now I have only black background without any mark of starting of device. Only orange LED flashes.
I tryed to remove battery and wait 10 minutes but without any succes.
Please can you help me with this problem?
That sounds like a hard brick.
And what can I do with it?
DO you know?
Brick DHD
Today I have a small changes in the device settings.
When I pushed it to recharger then device start to recovery but only for a few seconds. I can install retore or update but I have so short time for it, then every installation ends in black screen.
If somebody know something about this problem, please help me.
Eltahrel said:
Today I have a small changes in the device settings.
When I pushed it to recharger then device start to recovery but only for a few seconds. I can install retore or update but I have so short time for it, then every installation ends in black screen.
If somebody know something about this problem, please help me.
Click to expand...
Click to collapse
Have you used a froyo RUU and your device was shipped with Gingerbread?? if you did that then you have messed your hboot....you need to fix that in order to have a normal phone!!
It's kinda hard to know what's going on with the information provided, but you can come and hit the Hack Kit IRC Channnel to see if we can help...
Well i've been working for the past 9 hours trying ever possible thing i could find trying to fix my issue without any progress. How do i get back to stock so i can start over?!
Supersonic EVT1 ENG s-off
hboot-2.10.0001 (pc36*****)
microp-041f
touch panel-atmelc03_16ac
radio-2.15.00.05.02
mar 30 2010, 11:24:04
I was rooted with unrevoked after reverting back from the newest OTA using a guide from the XDA forums. everything was working wonderfully but my dumbass had to try and downgrade to an ancient ENG Hboot. using thefredelement's guide to get back to ENG .76. NOT NOTICING i shouldn't try it with HW version 003/004. unfortunately my phone is HW 003. idk what i need to do to get this fixed or if i bricked my phone. I've got a warranty still so i can always just report it lost pay the 50 and restore from my backup sd card.
anyways, my computer is able to see my phone with fastboot but not adb. i get errors when trying to flash new recoveries or anything but radios (such as fail PU, image update error, data length too large, etc) Trying to do anything with adb shell just says "device not found" (yes, i have the correct drivers installed) I CANNOT get into recovery (i had CWM 5.0.2.2) it just reboots back to hboot or the screen with the three droids skateboarding when i try. sorry ahead of time if this is posted in the wrong section/i just killed some brain cells with my stupidity and lack of experience. thanks in advance for any help and advice i can get! (sorry for the double post, idk how to delete postings)
Xexus said:
Well i've been working for the past 9 hours trying ever possible thing i could find trying to fix my issue without any progress. How do i get back to stock so i can start over?!
Supersonic EVT1 ENG s-off
hboot-2.10.0001 (pc36*****)
microp-041f
touch panel-atmelc03_16ac
radio-2.15.00.05.02
mar 30 2010, 11:24:04
I was rooted with unrevoked after reverting back from the newest OTA using a guide from the XDA forums. everything was working wonderfully but my dumbass had to try and downgrade to an ancient ENG Hboot. using thefredelement's guide to get back to ENG .76. NOT NOTICING i shouldn't try it with HW version 003/004. unfortunately my phone is HW 003. idk what i need to do to get this fixed or if i bricked my phone. I've got a warranty still so i can always just report it lost pay the 50 and restore from my backup sd card.
anyways, my computer is able to see my phone with fastboot but not adb. i get errors when trying to flash new recoveries or anything but radios (such as fail PU, image update error, data length too large, etc) Trying to do anything with adb shell just says "device not found" (yes, i have the correct drivers installed) I CANNOT get into recovery (i had CWM 5.0.2.2) it just reboots back to hboot or the screen with the three droids skateboarding when i try. sorry ahead of time if this is posted in the wrong section/i just killed some brain cells with my stupidity and lack of experience. thanks in advance for any help and advice i can get! (sorry for the double post, idk how to delete postings)
Click to expand...
Click to collapse
Remain calm. Let's see if we can get you fully functional.
First, let's upgrade that HBOOT. That by itself might fix you up, if it'll flash through the bootloader. Try the PC36IMG.zip attached to this post. It's for HBOOT 2.15.
If it flashes successfully, it should reboot the bootloader for you. If it doesn't, choose the fastboot option that does, and when it comes back up, try getting into recovery. If you can get into recovery, the next thing you should do is retire CWM and flash RA-supersonic.
thx capt. I actually just filed a clain through asurion, and for my $100 deductible i've getting a brand new evo3d xD so jumping the gun for the replacement actually worked out for me this time!
Xexus said:
thx capt. I actually just filed a clain through asurion, and for my $100 deductible i've getting a brand new evo3d xD so jumping the gun for the replacement actually worked out for me this time!
Click to expand...
Click to collapse
A shame to send back a perfectly fine OG . But I'm glad it worked out for you. Personally I like the challenge of trying to rescue a soft-bricked device. But I guess we'll never know if it was possible, now . . .
i would have loved to have found out myself. but being on probation and in the process of finding a job I just didnt have the time to mess with it i've still got it so once i get some time i'm going to attempt to unbrick it still. although its useless now that it's been deactivated lol
I wanted to root and flash my VM Wildfire S, now the only thing I can get after executing HBOOT Recovery or Factory Reset is white screen with HTC logo. How can I proceed.
Before I started the process, I had a LOCKED.
*** LOCKED ***
MARVEL C PVT SHIP S-ON RL
HBOOT- 1.10.0001
And, I have/had (?) Android 2.3.4
I successfully unlocked the bootloader using HTC Dev site/process. I validated that I had (and still have) "UNLOCKED" on HBOOT screen.
Being a noob, I was really happy with this result. In fact, I was so happy, I wanted to continue on to Root the phone. Upon hours of search in xda, I found "One Root for WFS 1.5", read the thread, and even watched the youtube vid- man, it looked easy!
Unfortunately, all did not go well. See attachment to get idea of what happened..
I am now at a softbrick (I think that is what it is called). I can get the HBOOT Menu, but when I try fastboot, I see things like:
PG76DIA.zip
no image or wrong file
PG76DIA.nbh
no image or wrong file
And, if I try HBOOT Recovery or Factory Reset, I get green HTC logo on white screen (I tried waiting 20min to see if it goes away, but didn't work). Did I mention being a noob?
I have spent many hours looking through this forum and others on how to fix. It seems sometimes they say RUU (this didn't work at all- I can turn phone on, but only see HBOOT screen). Others say, just flash another ROM. I don't think I flashed one, so it doesn't make sense.
Others say Recovery. I did not actually do a backup, but I think I understand that you can use a Recovery file to flash. That kind of makes sense.
And, frankly, now I am really confused. Seems some threads that look like they might work have dead links, or updated in Jan 2012 (I don't know if it is still valid).
Please help so my daughter stops laughing at me. Any help will be greatly appreciated (and thanked!)
Back from the dead, but...
Only 2 additional hours of searching and trying... and I got the phone to come back from the White Screen with green HTC. (Yes, my daughter stopped laughing)
I tried a couple of things, but this one worked (flashed Alquez's Unoffical 5.0.2.6 ClockworkMod recovery):
http://forum.xda-developers.com/showthread.php?t=1436501
I installed Rom Manager as suggested, but it wouldn't work ("an error occurred while trying to run privileged commands"). I am guessing that I am actually not rooted??
I am happy for now, but back to searching for next step, unless I can get a hint or two from this forum? please.
It would be best if you ask in the Wildfire S section. They might know more.
Sent from my Ainol Novo7 Elf using xda premium
Good suggestion
Thanks for suggestion. I moved it to wildfire s q&a ...
http://forum.xda-developers.com/showthread.php?p=27435254#post27435254
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?