Related
Ok, for the background:
I rooted with: http://forum.xda-developers.com/showthread.php?t=829045 And I have tried unrooting with the method there.
Unrooting with: http://forum.xda-developers.com/showthread.php?t=780141 (and I have tried others).
The problem is that if I run Unrevoked S-on, none of the PC36IMG's will load and give the error "main version is older". I can run the PC36IMG (and I have tried MANY different versions of that) with S-off, but then since there is no longer a recovery, I am unable to flash Unrevoked S-on. I have tried many RUU's but if S-on, they won't load..only with S-off.
So I've tried doing this with recovery, without recovery, with S-on and off, flashing PC36IMG's, flashing RUU's....nothing works. I'm running out of time to mail this phone back and I'm pretty much out of ideas.
If I were to rename Unrevoked S-on to PC36IMG would that work in the bootloader, or would the phone flash the data to the wrong area and brick the phone for good?
I have searched through many threads and I think I haven't gotten any advice because people generally aren't looking through those threads if they are already rooted, or already good with unrooting.
Ok, I think that's about it. I have Hboot 2.02, hardware 0003.
Thank you So much, in advance!
The PC36IMG in that thread is most likely outdated. Run the s-on tool and then grab the latest RUU from HERE and run it from your desktop and you should be in the clear.
Thanks, I'll give it a try. I haven't downloaded RUU's from that site I know for sure.
That's just a mirror site that drmacinyasha set up for files and such.
_MetalHead_ said:
That's just a mirror site that drmacinyasha set up for files and such.
Click to expand...
Click to collapse
Well it is nice that each one has an MD5 to check. Odds are that I've already tried these RUU's, but I'll give it a shot anyway.
That RUU doesnt even see the phone.
Well I tried a 3.7 PC36IMG file before, and went ahead and tried it again. For some reason this time, it actually worked. So there must have been some issue with the original rooting...or the file transfer before. I have no idea. Whatever, it actually worked and it's back to stock again.
Thanks for your help!
I really have this huge problem that's been really bugging me all week and i cant seem to concentrate with it over my head. I am new to rooting devices and i was a little ahead of myself recently... I finally rooted my phone and over my excitement i just had to add custom roms to my Evo 4g, i didnt really understand what i was doing, i mainly followed instructions to most sites, mainly cyanogen, and got the latest version of cyanogen, i had troubles starting it up at first, it was stuck on the bootup screen for cyanogen (droid on skateboard with spark flying around) and it kept going black and reloading, i didint know what to do, so i took the battery out after a hour of waiting then i wiped my drive in fear of bricking my phone (i know i wasnt thinking) i did not make a back up of my previous point of time where i actually practically running stock, and i am still upset at that mistake, after doing a factory reset from the clockwork recovery, cyanogen finally booted up, but was missing alot of things, i.e. android market and so on... im now wanting to go back to stock and i have already got Son somehow, can anyone help walk me through this, id very much appreciate it!!
acidcobra2002 said:
I really have this huge problem that's been really bugging me all week and i cant seem to concentrate with it over my head. I am new to rooting devices and i was a little ahead of myself recently... I finally rooted my phone and over my excitement i just had to add custom roms to my Evo 4g, i didnt really understand what i was doing, i mainly followed instructions to most sites, mainly cyanogen, and got the latest version of cyanogen, i had troubles starting it up at first, it was stuck on the bootup screen for cyanogen (droid on skateboard with spark flying around) and it kept going black and reloading, i didint know what to do, so i took the battery out after a hour of waiting then i wiped my drive in fear of bricking my phone (i know i wasnt thinking) i did not make a back up of my previous point of time where i actually practically running stock, and i am still upset at that mistake, after doing a factory reset from the clockwork recovery, cyanogen finally booted up, but was missing alot of things, i.e. android market and so on... im now wanting to go back to stock and i have already got Son somehow, can anyone help walk me through this, id very much appreciate it!!
Click to expand...
Click to collapse
The reason that you were missing things in Cyanogen, is because you didn't flash GAPPS (google apps), which are things like Market, Gmail etc. If you already have S-on, and you're sure you want to go back to stock, unrooted, then it shouldn't be too bad for you. One way would be to download a PC36IMG.zip, place it on the root of your sd card, boot into the bootloader (power+voldown), and it will flash the factory ROM for you. You could also run RUU, from your PC. Plug phone into PC with USB cable, and run the RUU from your computer. Either of those methods should work for you, and get you back to stock. Here are a couple links that might help you.
Complete list of factory PC36IMG.zip and RUU:
http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu
Guide on how to Unroot
http://forum.xda-developers.com/showthread.php?t=780141
Good luck.
k2buckley said:
The reason that you were missing things in Cyanogen, is because you didn't flash GAPPS (google apps), which are things like Market, Gmail etc. If you already have S-on, and you're sure you want to go back to stock, unrooted, then it shouldn't be too bad for you. One way would be to download a PC36IMG.zip, place it on the root of your sd card, boot into the bootloader (power+voldown), and it will flash the factory ROM for you. You could also run RUU, from your PC. Plug phone into PC with USB cable, and run the RUU from your computer. Either of those methods should work for you, and get you back to stock. Here are a couple links that might help you.
Complete list of factory PC36IMG.zip and RUU:
http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu
Guide on how to Unroot
http://forum.xda-developers.com/showthread.php?t=780141
Good luck.
Click to expand...
Click to collapse
Thank you so much for a quick reply, it really helps, but one more question, i tried to run pc36img, but it keeps saying it failed because a older version was present, also, sorry for asking another, but i have also wondered this other method with all these other download links, there is alot and how would i know what one to use?
also! i tried running the first download and it keeps saying that my phone isnt connected even if it is? does it need to be in debugging mode or what?
you have to flash most recent gapps for market.
acidcobra2002 said:
Thank you so much for a quick reply, it really helps, but one more question, i tried to run pc36img, but it keeps saying it failed because a older version was present, also, sorry for asking another, but i have also wondered this other method with all these other download links, there is alot and how would i know what one to use?
also! i tried running the first download and it keeps saying that my phone isnt connected even if it is? does it need to be in debugging mode or what?
Click to expand...
Click to collapse
Do you know what hboot version you have? If not, boot into the bootloader (power+voldown), and it will say hboot version at the top I believe. If you have an older hboot version, I'm pretty sure you want an older PC36IMG or RUU. If you notice, they all list different software versions (3.70, 3.30, 3.29, 3.26 etc). The 3.70 is the newest, and I believe you'd use that for the newest hboot versions (2.10 or 2.02) The older hboot's (.76, .93, .97) I believe you'd use either 3.29 or 3.30. Someone please step in and correct me if I'm wrong or misinformed. I'm also not sure if you need to be in debugging mode, I would try putting it in debugging mode for sure (I've never had to unroot, but have read up on how to do it) If you are getting the main version is older when running the PC36IMG, I would try a different PC36IMG, one with older software, 3.29 or 3.30. I've read many times of people needing to try different ones before they got it to flash. That's why there are so many on there, because different phones may require different versions, I believe.
k2buckley said:
Do you know what hboot version you have? If not, boot into the bootloader (power+voldown), and it will say hboot version at the top I believe. If you have an older hboot version, I'm pretty sure you want an older PC36IMG or RUU. If you notice, they all list different software versions (3.70, 3.30, 3.29, 3.26 etc). The 3.70 is the newest, and I believe you'd use that for the newest hboot versions (2.10 or 2.02) The older hboot's (.76, .93, .97) I believe you'd use either 3.29 or 3.30. Someone please step in and correct me if I'm wrong or misinformed.
Click to expand...
Click to collapse
It is Hboot-2.10.0001
You sir [user above me] are correct. I have linked ya to a site with a lot of RUUs, and they list the version number.
http://www.shipped-roms.com/shipped/Supersonic/
Download the RUU, boot into the bootloader [turn off then hold vol down while phone turns on] then select fastboot, then run the exe, and follow zeh instructions.
acidcobra2002 said:
It is Hboot-2.10.0001
Click to expand...
Click to collapse
Which PC36IMG or RUU did you try? (which software) You may need to try a couple different ones on there.
Hi, I have posted this before but it got deleted because I very stupidly posted it in the wrong place.
My question has been answered before due to searching but no one else happens to be in my EXACT situation and I don't want to mess up my phone.
Basically my Desire HD is rooted etc and I want to flash the Android Revolution ROM, but I havent flashed any ROM's since my OLD G1 and now everyone talks about S-OFF etc and I don't understand these, on my G1 it was simply rooting and flashing a Recovery and then flashing a ROM, so basically what do I need to flash this ROM
My situation:
I am running the stock ROM (permroot on 1.32.405.6)
I have stock radio
I have Clockwork mod 3.0.0.6
and Buzz Sense 1.3 + OC (OC'd 1.6Ghz) kernel.
(+Ever since I downgraded from 1.72 I have lost wi-fi, it connected to my wi-fi but I get no internet access through it, its definitely a problem with the phone and nothing else because I have tested my router etc, all my other devices have connectivity through my router)
We all were in your exact situation. The Desire HD employs an extra level of security to prevent users messing with their handsets, S-ON.
You need to turn this off, Ideally ENG (Engineering) S-OFF, before you can make persistent changes to your system.
Have a read through the very helpful guides in the Dev section. They also contain the tools you need. Turning S-OFF should be a one time process only, i.e once you've done it there is no need to repeat it to flash another ROM.
Hope that helps.
andyharney said:
We all were in your exact situation. The Desire HD employs an extra level of security to prevent users messing with their handsets, S-ON.
You need to turn this off, Ideally ENG (Engineering) S-OFF, before you can make persistent changes to your system.
Have a read through the very helpful guides in the Dev section. They also contain the tools you need. Turning S-OFF should be a one time process only, i.e once you've done it there is no need to repeat it to flash another ROM.
Hope that helps.
Click to expand...
Click to collapse
Sorry I forgot to mention that I have SHIP S-OFF and I'm unable to get ENG S-OFF because when I used the Easy S-OFF tool it can only give me SHIP S-OFF for some reason, I cant do anything now since its incompatible with my kernel as well. Can I flash a ROM with just SHIP S-OFF? I don't want to flash any radios because I bricked my G1 about 4 million times when flashing radios.
It you run a 1.32 WWE RUU and revert back to stock you can then reapply ENG S-OFF. A bit of a ball ache I know.
Most ROMs will work just fine with SHIP S-OFF but ENG is usually preferred.
To flash a radio you need Radio S-OFF another beast entirely. However there is a very good too to do it with. No bricks so far and your DHD will then have super CID and be SIM unlocked.
didge3 said:
Sorry I forgot to mention that I have SHIP S-OFF and I'm unable to get ENG S-OFF because when I used the Easy S-OFF tool it can only give me SHIP S-OFF for some reason, I cant do anything now since its incompatible with my kernel as well..
Click to expand...
Click to collapse
Just tick the "I have radio s-off" box and it becomes compatible with everything.
follow my guide in the sig and skip to eng s-off and radio s-off part, or skip to whatever comes next if you've already done them
Tried that, I get a "Connection Error", I have made sure its fully connected as "Disk Drive" and I allow the Super User request when I do it, but it still doesn't work, plus the radio tool just says "Incompatible kernel" - or something like that.
I mainly want to know, can I flash Android Revolution in my current situation, can I flash with just SHIP S-OFF and my current kernel, or do I have to go back to stock kernel, flash the ROM and then flash my kernel back?
and why should I have ENG S-OFF, if it makes a lot of difference I will give it ago, but I mainly want to just flash this ROM to see if it fixes my wifi issue and my camera doesn't drop so many frames! (known issue in 1.32, fixed in 1.7X)
Disk Drive. Yeah, read the guide again more carefully, mate... And change the tool, why are you using easy radio tool!? It won't give you ENG S-OFF. My ENG S-OFF tool will give you that. And it most definitely will not say incompatible kernel if you just tick the box I talked about.
You can flash ARHD now. Do not mess around with it's kernel after flashing, because it comes with the best kernel out there. The kernel has been made to fit ARHD's needs.
jkoljo said:
Disk Drive. Yeah, read the guide again more carefully, mate... And change the tool, why are you using easy radio tool!? It won't give you ENG S-OFF. My ENG S-OFF tool will give you that. And it most definitely will not say incompatible kernel if you just tick the box I talked about.
You can flash ARHD now. Do not mess around with it's kernel after flashing, because it comes with the best kernel out there. The kernel has been made to fit ARHD's needs.
Click to expand...
Click to collapse
I get the same as every other time, downloads the Easy S-OFF tool, "Pushing stuff to SD" Phone says "Unknown has been granted su access" and then the tool says "Error: Connection Problem!" - I get this every time, I have tried re-downloading this software every time, removing the "Unknown" in super user and then re-allowing it when it asks, I still get the same error...
Does it matter that I'm using Windows 7 64-bit?
EDIT: I think I've done it now, I downloaded the latest 2.3 SDK (I had 2.2) which updated my ADB drives, I didn't get the error this time, will boot into H-BOOT and check now.
Are you still using that disk drive mode? Because you should not.
THANKS
I have thanked everyones post, I can confirm my H-BOOT Now says PVT ENG S-OFF, one last thing, I'm all good to flash now? I can just put the ROM (sense version) on my SD card and flash it in CWM, with my current kernel, even though it will over write it with the one included for Android Revolution, I dont have to go back to stock kernel or anything first right?
Thanks again
Have you flashed ClockworkMod Recovery yet? If not download ROM Manager from the Market and flash it from there.
Once that is complete, download ROM, put on SD Card, Recovery, Wipe, Flash, Enjoy.
didge3 said:
Hi, I have posted this before but it got deleted because I very stupidly posted it in the wrong place.
My question has been answered before due to searching but no one else happens to be in my EXACT situation and I don't want to mess up my phone.
Basically my Desire HD is rooted etc and I want to flash the Android Revolution ROM, but I havent flashed any ROM's since my OLD G1 and now everyone talks about S-OFF etc and I don't understand these, on my G1 it was simply rooting and flashing a Recovery and then flashing a ROM, so basically what do I need to flash this ROM
My situation:
I am running the stock ROM (permroot on 1.32.405.6)
I have stock radio
I have Clockwork mod 3.0.0.6
and Buzz Sense 1.3 + OC (OC'd 1.6Ghz) kernel.
(+Ever since I downgraded from 1.72 I have lost wi-fi, it connected to my wi-fi but I get no internet access through it, its definitely a problem with the phone and nothing else because I have tested my router etc, all my other devices have connectivity through my router)
Click to expand...
Click to collapse
andyharney said:
Have you flashed ClockworkMod Recovery yet? If not download ROM Manager from the Market and flash it from there.
Once that is complete, download ROM, put on SD Card, Recovery, Wipe, Flash, Enjoy.
Click to expand...
Click to collapse
Note the very first post "Clockword mod 3.0.0.6" so in answer, yes.
Your good to go then, happy flashing.
I am in desperate need of unrooting my phone now, but due to it being almost 2 years that I've owned this phone I can't remember how I rooted it in the beginning. Any way to figure this out?
Need to know your Hboot version and radio, and also is the phone S-ON or S-OFF (power off, then volume down and power buttons simultaeously).
HBOOT-2.18.0001
RADIO-2.15.00.12.19
Phone is S-OFF
Thanks for your help.
On a side note, my phone is in an infinite boot loop that only loads to the white evo screen, I can't flash custom recoveries, roms, or RUU. I think the problem is the fact that it says LOCKED in the pink label at the top of my bootloader. I tried using the command fastboot oem lock and it says it's already locked and doesn't unlock it or anything of the sort. If you know any way to aid my problem I thank you for the help.
Most infinite bootloops are never fixed, however;
The best advice that I can give you right now is to download these two files.
http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
http://goo.im/stock/supersonic/ruu/...15.00.12.19_NV_2.33_release_234563_signed.exe
Connect your phone to your computer, then boot into your bootloader and click on FASTBOOT. The phone should be in FASTBOOT USB. Install the HTCDrivers exe file to your computer. Then try to run the RUU file with the phone still in FASTBOOT USB.
If that doesn't work, then the phone may already be permanently bricked. Interestingly, the phone was rooted nearly 2 years ago, but you have the latest everything. I hope you did not do that with OTA updates.
Thanks shortyydoggg, unfortunately I've tried that method with those exact files already and had no such luck. My last resort is that if I can change the LOCKED pink label to RELOCKED or UNLOCKED, I'll be able to flash through the bootloader again, and temporarily use my phone once more until i can get the EVO LTE. Also, there is basically no way to tell now which root method I used?
Yea, Unlocking the bootloader was going to be my other suggestion after trying the RUU. It's not much else you can do after that.
Sent from my PC36100 using xda premium
Ya the RUU unfortunately goes through successfully but then the phone restarts again. I can't help but feel this is all because my bootloader says LOCKED. The problem now is fastboot oem lock command doesn't work for me, and says the phone is locked and doesn't change the label to RELOCKED or anything else like it should? Do you know why this command isn't unlocking my bootloader or any other commands or ways to do this?
djs415 said:
Ya the RUU unfortunately goes through successfully but then the phone restarts again. I can't help but feel this is all because my bootloader says LOCKED. The problem now is fastboot oem lock command doesn't work for me, and says the phone is locked and doesn't change the label to RELOCKED or anything else like it should? Do you know why this command isn't unlocking my bootloader or any other commands or ways to do this?
Click to expand...
Click to collapse
That's the wrong command. You need to go to the htcdev site (www.htcdev.com), register, and unlock the bootloader. Since you're already S-OFF, have you tried running a PC36IMG file for a custom RECOVERY. You might not need to be unlocked to do that.
I'm almost positive I tried to flash a custom recovery through the bootloader and it didn't work... however, you were right and my bootloader is now unlocked so THANK YOU! Will post back after flashing the recovery you attached.
To answer your previous question about which root method you used, unrevoked-forever was used at some point to S-OFF the phone, since you are on Hboot 2.18 and still S-OFF and not on the old Engineering S-OFF Hboot. Whether the phone was rooted with Unrevoked, Toast Method 2, Simple Root or AutoRoot, there is no exact way to tell right now, but it can be guesstimated that it might have been Unrevoked.
Now for the confusion if you dare to read:
AutoRoot is Toast Method 1, unrevoked-forever, and a custom ROM inside a program, and Simple Root is Toast Method 1 and a custom ROM inside a program along with the engineering S-OFF bootloader. Unrevoked is uh, Unrevoked and Unrevoked forever inside a program. Toast method 2 is just a custom ROM flashed along with the same S-OFF bootloader as SimpleRoot. If you used Toast Method 2, then you did everything AutoRoot did in order to S-OFF the phone. You just needed unrevoked-forever to keep it S-OFF for any other and your bootloader. Toast Method 1 alone does not S-OFF the phone. If you used SimpleRoot, which does not use unrevoked-forever, you needed unrevoked-forever at some point again to keep the phone S-OFF on any other Hboot (your 2.18). So again, you would have done everything AutoRoot did.
So that brings it down to AutoRoot and Unrevoked, since everything else you did is the same thing that AutoRoot does. Since you rooted nearly 2 years ago, and Unrevoked-forever is inside AutoRoot, AutoRoot has to be newer than unrevoked-forever to contain it inside its program. Also Unrevoked is newer than AutoRoot and already contained Unrevoked-forever. So the likely-hood that you used Unrevoked is very great, but not for sure. It is also the easier method and the one that nearly everyone else used at that time.
Somehow, still no luck. Flashed that file you linked and it goes through successfully, asks to reboot and then back to white screen boot loop. How can this be possible at this point, with the bootloader unlocked it goes through with the process but the actual writing of the data seems to fail. Trying the RUU one last time now that it is unlocked, but if this doesn't work I'm stumped.
I thought the whole beauty of the the bootloader, and more importantly being able to reach it, was that it meant your phone couldn't be bricked. Last try, will report back.
Bootloader unlocked, RUU flashed this time through PC. Nothing, and completely out of ideas here.
Shortydoggs been doing a lot of help around here for similar situations. There have been cases (maybe a dozen I've seen) where people get into a situation like yours where bootloader is accessible , but that is about it. And from what I've read, in those cases, when the phone tries to boot, it does 4 or 5 short vibrates before going back to bootloader.
Your situation is also strange in that, you rooted 2yrs ago, but don't have S-off, a locked bootloader. Hboot 2.18, which is the latest but is unlockable thru HTC dev, but no S-off available for it yet. And your radios are latest, too (mostly irrelevant).
First there was toasts root for baseband 1.37 (which downgraded you to 1.17 with eng hboot to get s-off before bringing you back up to 1.37). Then there was simple root by jiqqaman, which worked for people who took the baseband 1.47 OTA. Then when froyo came out, anyone who took that OTA (baseband 3.25, or 3.26, I forget) had to wait for unrevoked to be developed. I think hboot at that point was 2.08 and 2.10. Unrevoked forever worked on that, and gave you S-off.
I know none of that info helps you necessarily. It's just puzzling how you rooted 2yrs ago, bit have the latest hboot with S-on. Maybe you didn't finish toasts part 2 S-off guide, then sometime recently updated your radio and hboot? No. You need S-off to flash radio. Were you recently on a stock rooted ROM and took an OTA (is that even possible) when you were still S-on (from not finishing toasts guide)?
Sorry, I know it's not a lot of help. Just trying to figure out how things could not match up so much, and if that's how you ended up in this situation (that could be helpful info for others). I hope you don't have the bootloop of death and can get it sorted. Between shortydogg and captain throwback, I HAVE seen some phones saved.
sent from 2yr old Evo on ICS
Yea, I'm not going to waste your time any further. There's not much else to do.
Ya unfortunately I'm quite confused myself... however, if this information helps you at all... For starters, I have S-OFF and until recently (2 weeks or so since my phone started acting up like this) I was running a ROM perfectly fine until one day it restarted into this never ending boot loop. I'm not sure how my HBOOT is the most up to date, seeing as I was always very careful not to do something stupid like change my HBOOT for no reason. The interesting thing is that I had never seen that pink label before on my bootloader saying unlocked or locked OOW until the problem started occuring 2 weeks ago.
Also something I'm realizing... are you telling me that the HBOOT I have does not have S-OFF yet, and therefore you can't flash roms or custom recoveries... but my bootloader still says I am S-OFF. So the problem is I am S-OFF for the most recent HBOOT which can't be changed to S-OFF yet? Could downgrading hboots work?
He did not realize that you were S-OFF. Your phone is set to stay S-OFF regardless of what Hboot you have or how that Hboot usually comes.
Also, your phone appears to have a hardware, and not software issue, so, changing Hboots, might not hurt to try, but may not help much. In case I'm wrong, do not try anything below Hboot 2.10. Here is one for 2.16.
What rom were you running up until the time the bootloops started happening? This sounds alot like the cyanogen mod bootloop of death which no one has ever fixed I believe.
I believe I was using some version of SOS or a sense rom, but I'm leaning more towards SOS.
Just tried using that HBOOT thought it's still not working. Would going to the engineering hboot make any difference?
What could be the hardware problem causing this?
I see that shortydogg is in here taking good care of you .
The bottom line is, if you can't flash/get into recovery from HBOOT, you're probably in an unrecoverable situation.
It's unclear after my review of the thread, but you have tried flashing a recovery through HBOOT using a PC36IMG.zip file, right? And then after flashing, you choose not to reboot, but to boot into Recovery?
If you can get into recovery, then we can resolve your issue (if in fact it is software related).
If the problem is bad NAND blocks on your recovery or boot partitions, then there's nothing that can be done.
Also, the watermark on your bootloader (LOCKED, UNLOCKED, etc) has nothing to do with your issue. That's just connected to the version you were running. As long as you're S-OFF, that's irrelevant.
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?