Related
I've searched the forums and have not found a situation that really matches mine.
I've been running on a Cyanogen nightly build for probably two months with no problems. Out of nowhere this morning my phone reboots itself (while it was idle; I wasn't even touching it) and then gets stuck in a boot loop. I get the White HTC Evo 4G screen, then it powers off and comes back up to the white screen again. Over and over.
All I can get do is hboot. Even telling hboot to go into the recovery mode puts my back into the boot loop. Fastboot, clear storage, and hboot usb all seem to work though. I've tried downloading the PC36IMG.zip file (http://forum.xda-developers.com/showthread.php?t=780141) in that thread, but hboot loads it and tells me that it is older than my current version, and only gives me the option to reboot, or not to reboot. Doesn't load the image.
Here is the information on my hboot screen:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-0.97.0000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.09.01
Aug 19 2010, 14:29:08
Anybody have any ideas? Thanks!
you lost root, s-on
you can still start the bootloader so it's not a brick
need to get s-off before you can load recovery again and reflash your rom
have you tried the RUU? if it installs and defaults you then you can unrevoked to root
NewZJ said:
you lost root, s-on
you can still start the bootloader so it's not a brick
need to get s-off before you can load recovery again and reflash your rom
have you tried the RUU? if it installs and defaults you then you can unrevoked to root
Click to expand...
Click to collapse
Trying the RUU here now: http://forum.xda-developers.com/showthread.php?t=874091
Wish me luck!
luck has been wished
Kuhmo said:
Trying the RUU here now: http://forum.xda-developers.com/showthread.php?t=874091
Wish me luck!
Click to expand...
Click to collapse
This didn't work. Everything is still the same, except that my hboot version is now 2.10.0001. Any other thoughts?
still won't not into any rom? did you get errors?
NewZJ said:
still won't not into any rom? did you get errors?
Click to expand...
Click to collapse
No, the app on the PC said everything was successful. The progress bar on the phone progressed without errors too.
what happens when you reboot the phone not going into bootloader?
Just the HTC EVO 4G splash screen. Over and over and over...
does it show the boot animation or just stuck on splash?
Just the splash. No animation.
pull the battery, remove your sdcard, put the battery back in, see if it gets to the animation
Doh, you upgraded your hboot. It's alright though, just run the ruu one more time and your should be ok
Sent from my PC36100 using XDA App
Wrong button..
xHausx said:
Doh, you upgraded your hboot. It's alright though, just run the ruu one more time and your should be ok
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I asked my wife to check this thread from the car on the way to dinner. Saw the response. So I took my laptop inside with us and used the RUU one more time. No luck. I decided that it must be a hardware issue. I took the SD out and removed the evidence that the phone had been rooted, then took it to the sprint service center up the road. They just replaced it for me. Thanks for your time! I DO want to root my phone again, the ROMs are just so much better than the stock installation. Should I not install the OTA updates if I'm going to root it? Which guide should I follow for rooting?
never do OTA when rooted, use unrevoked to root, unrevoked.com
NewZJ said:
never do OTA when rooted, use unrevoked to root, unrevoked.com
Click to expand...
Click to collapse
Not when rooted. I meant should I update to the latest OTA UNTIL I decide to do the root again? Is the latest OTA unrootable?
Same deal.
Here is the post that I put in the wrong forum that I was about to post here until I saw this thread...
Wellp. I win.
I win a no expenses paid trip to my nearest Sprint dealer.
Ever since I used unrevoked to root my phone in November, I've been voraciously digging through these forums for tasty roms. I've been snorting lines of Cyanogen, MIUI, and a myriad of other, well-designed roms.
Using a on older version of hboot (pre 1 methinks) I was able to avoid the latest hassles with ClockworkMod (plus, I down(up?)graded to 2.6 via RomManager).
Tonight, as I was enjoying some tasty foodstuffs at my local foodstuff vendor, my phone rebooted. Then, it rebooted again. Then again. I once made the folly of flashing a new rom without running the appropriate wipes, and was no stranger to the bootloop. I patiently fired up hboot (my poor volume rocker is all but wore out) and ordered up the trusty recovery mode.
...then it rebooted again... and again... and again.
PusSidiasus: ONOES! I HAVE THE WTFBBRICKED MY PRECIOUS!
SmartAsSidiasus: Hang on for a second, let's check the internet. Try this link: tinyurl.com/4vgeyeg
PusSidiasus: ...
Unfortunately, my internal dialogues are not nearly as witty. Also, my best attempts to de-brick-ify were for naught. Fastboot gave some wacky error message when I tried to flash a new recovery, and installing via PC36IMG.zip did nothing to improve the situation. I even went so far as to install a stock image someone pulled from an RUU (with a 2.02hboot, so as to avoid wimax woes)...
Still, a whole lotta nothing. I can't do anything beyond hboot, and whatever recovery image I install (Clockworkmod, AmanRa) the machine still bootloops.
At this juncture, I've resigned to taking the phone into the sprint store and playing dumb. It is a stock rom, though I hope the attendant misses the S-OFF bit at boot. Which brings me to my proper question:
1) Has anyone run aground a similar issue and found a way out?
OR...
2) Anyone know how to turn S-(back)ON in my current situation?
Any insight would be greatly appreciated. Also, you can rest assured that I'll be rooting again whatever phone I walk away with, and the work that is exhibited in these forums is amazing. Keep churning out wonderful roms and guides.
Sidiasus
(Currently, Sadiasus... )
run the ruu to s-on then trade for another
NewZJ said:
run the ruu to s-on then trade for another
Click to expand...
Click to collapse
Ack, sorry... didn't mention in previous post. I fired up windows to run the RUU (I don't trust wine to that stuff) but it couldn't detect the device.
This was probably asked before but I couldn't find anything on my searches...
I need to return my phone since I got a refurb'd but I'm having issues turning it back to S-ON... has anyone returned their phone with S-OFF? Did they attempt to charge your account or something to that effect? I can definitely do the RUU and return it to stock unrooted but the bootloader shows S-OFF as well as the 6.17 Hboot instead of S-ON and 2.16 Hboot...
TIA!
gqukyo said:
This was probably asked before but I couldn't find anything on my searches...
I need to return my phone since I got a refurb'd but I'm having issues turning it back to S-ON... has anyone returned their phone with S-OFF? Did they attempt to charge your account or something to that effect? I can definitely do the RUU and return it to stock unrooted but the bootloader shows S-OFF as well as the 6.17 Hboot instead of S-ON and 2.16 Hboot...
TIA!
Click to expand...
Click to collapse
Well they can't really do anything about us rooting phones since the supreme court says we can do whatever the hell we want to devices we paid for, thanks to the Apple lawsuit. However rooting voids your warranty so I suppose the question is why are you returning. If you are returning it because it's in some way physically defective, you *might* be ok. But if it has malfunctioned, it could bite you in the ass. More information would be helpful.
You should also realize that Sprint has been very inconsistent on this issue. There are those who have had warranty work/returns done and had no issues with it having S-Off and even custom roms still installed. Then there are those who have gotten caught. It should also be pointed out that this is in your contract, so please don't be one of those guys that get denied then RAGE about it on these forums. When you rooted, you clicked a box that said "Your warranty is now void" or at least read that somewhere I am certain! Anyway more info pls, or try it anyway and good luck! Worst thing they will do is give you the phone back and void your warranty totally. You could always toss it in the sink for a few hours then file insurance claim on it.
gqukyo said:
This was probably asked before but I couldn't find anything on my searches...
I need to return my phone since I got a refurb'd but I'm having issues turning it back to S-ON... has anyone returned their phone with S-OFF? Did they attempt to charge your account or something to that effect? I can definitely do the RUU and return it to stock unrooted but the bootloader shows S-OFF as well as the 6.17 Hboot instead of S-ON and 2.16 Hboot...
TIA!
Click to expand...
Click to collapse
I tried returning my Evo with S-Off, and the person who was looking at it recognized it in the bootloader. He said "I personally used Revolutionary too. Sadly, we can't return this."
I was able to find a solution, however. Download the zip file attached to this forum post, rename it to PC36IMG.zip, and place on the root of your SD card. Boot into your bootloader. You will be prompted to update. Choose yes. It should flash quick. When it asks you to reboot, choose yes and reboot back into the bootloader. It should show S-ON with 6.17 HBOOT. From there flash your RUU and you should be back to 2.16 HBOOT with S-ON!
I got a refurb a couple months ago and it arrived S-OFF, so I dunno
Thank you all for your responses. I did try to run the RUU and Captain Throwback's S-ON zip but no luck, I'll probably just unroot and RUU it back to the newest firmware and just return it like that. Since borrowedchief said he received his with S-OFF, its probably a hit or miss as most other things at Sprint...
I just sent my old phone back with S-OFF. My issue though was power cycling. Sprint even credited me the $100 premium for my insurance because they failed to replace my phone before it had water damage. I took the phone in multiple times with no luck. Finally the Tech told me I had good news and bad news. Good news, you are getting a new phone. Bad news you have to pay $100 because you have water damage. The first Rep I talked to said we should have replaced the phone the first time. Credited me the money once they received my old phone.
I just returned my phone a few days ago with the s-off but i did have the original rom on the phone. They didnt say anything to me and when i received the new phone, the s was also off.......
Obviously the official rule is that they dont take them back S-off... Some people get lucky and either get a lazy rep or a rep that wants to be nice... It's a gamble
richp1970 said:
I just returned my phone a few days ago with the s-off but i did have the original rom on the phone. They didnt say anything to me and when i received the new phone, the s was also off.......
Click to expand...
Click to collapse
I returned mine too but the terms state that they have up to 2 billing cycles to charge us for any damages or whatnot... guess we'll see...
Their policies at sprint are now that they service rooted phones meaning with S-off they just RUU back up to the latest and it usually reflashes over ENG hboot and other things meaning that it's just gonna be s-on when you get it.
I rooted my phone and is s-off too and cant get it back to s-on
gqukyo said:
This was probably asked before but I couldn't find anything on my searches...
I need to return my phone since I got a refurb'd but I'm having issues turning it back to S-ON... has anyone returned their phone with S-OFF? Did they attempt to charge your account or something to that effect? I can definitely do the RUU and return it to stock unrooted but the bootloader shows S-OFF as well as the 6.17 Hboot instead of S-ON and 2.16 Hboot...
TIA!
Click to expand...
Click to collapse
Originally Posted by Captain_Throwback
Here I will post my 2.16 hex-edited HBOOT to appear as 6.17. I'm not really a good person to put together a guide, but I can give you this file, which should at least help.
I TAKE NO RESPONSIBILITY IF YOU (SOMEHOW) BRICK YOUR DEVICE. FOLLOW THESE INSTRUCTIONS AT YOUR OWN RISK!!!
Also note that I have 0003 hardware, so there are no guarantees that this will work for you! That being out of the way, let me continue . . .
I used AndroidFlasher to flash this HBoot, as it was extremely easy (just renamed to HBOOT.img). Flashing through Fastboot (directly on the device) might also work, I guess, if you rename the file to PC36IMG, but I didn't try it that way.
I was able to do this successfully on Windows XP 32-bit (I always have issues getting anything to work on my Windows 7 machine), so I'm not sure how (or if) it'll work on Vista or 7 (or on 64-bit versions).
Note that if you're doing this with your device connected to your computer, USB Debugging MUST BE TURNED ON!!
If you want to return to stock, I first recommend flashing a stock ROM. I recommend the most recent Gingerbread update, which can be found in this post (RUU can be found here).
After successfully un-rooting your device by flashing the unrooted ROM from above, now we must re-lock NAND (set S-ON). Basically, you just flash the hboot.img from the attached zip file, and it will set your device HBOOT version to 6.17, and re-lock your NAND (S-ON). Then, you can re-flash the ROM from the above step, and it *should* overwrite the hex-edited HBOOT with the "official" version, and restore your device to stock.
Again, this worked for me, but if it doesn't work for you, don't go blaming me, and calling my method a sham.
Thanks to {ParanoiA} for posting the link to the thread where the hex-editing was mentioned, and thanks to thefredelement (from that thread) for posting a working method!
Maybe someone else can test my method and confirm it works for them & others, and then put a real guide together, for everyone else (like me) that needs to return their device for service after rooting with Revolutionary.
Thanks man! I rooted gingerbread 2.3.3 with revolutionary and try to unroot with unrevoked foreverson.zip but no luck because I didn't use there method to root. Hours and hours of research came accross your thread and all I can say thank you.
*****Very important to complete last step because if you don't you will have S-on but your HBOOT will be 6.1... For my last step I didn't flash using HBOOT I just downloaded RUU most current file because my phone came with 4.24.651.1 I just ran RUU booted back to white screen and HBOOT now shows HBOOT 2.1
Here you should use this method. It was origanally posted by captainthrowback and thanks to him now im back to s-on I was rooted and went back to stock but had s-off and I used this method to go back to s-on and it worked. My evo is on hardware v0004 and it worked fine too. Hope this method works for you to. Good Luck. Have any other questions just ask
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
Ok, I rooted with unrevoked a long time ago. Broke my screen and need to unroot. I followed the unroot unrevoked guide as closely as I could, but the rom in the link was not found. So I downloaded a different ruu.zip of factory rom, don't ask me which one, because I can't find the link anymore, but currently here is where I stand. Hboot kept saying that the img was older or something, and wouldn't flash. So I did a stupid thing and pushed the zip with clockwork. So now I'm running s-on with clockwork recovery and a stock unrooted rom. So, I tried the next thing, downloaded an 3.7 ruu .exe and tried to run that from windows, but it gives me an hboot usb connection error f*ucking **** 1 thing after another.
This is the unrooting guide I used http://forum.xda-developers.com/showthread.php?t=780141
I got s-on, and tried that pc36img but it wouldn't work, originally. Before I went on to screw things up.
I've been at this for hours, something that should have taken 10 minutes if I wasn't an idiot, or bad links, or what ever. Can someone tell me or point me in the right direction, of what to do here, preferably not to a 2 year old thread with outdated links? What should I do?`
A List of android stock RUU zips with radio, pri, recovery all in one would be great, but I give up on trying to find that, its buried or does not exist.
I found this list http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/ROMs but its just the rom not everything.
So here is where my phone stands
S-ON
Hboot .97
Clockwork recovery 2.5.0.7<<<<<<
Android version 2.2.2
Build number 4.54
PRI 1.90_003
Angrychair420 here is a stock RUU that I know is good you should be able to run the RUU from windows.
http://geekfor.me/evo/ruu/evo_ruu_1326511/
thanks, that says its img version 1.32.651.1, assume thats safe to use. I assume thats andoid 3.26 which is what came on my phone. Ugh I'm in over my head. Why did my screen have to break, i was totally happy with CM7 and everything the way it was.
what if I wipe my data and caches, remove SD card, put on a PC36IMG.zip and boot the phone into hboot, will it still give me the older version error?
edit: the link you gave me gives me the same error as the other ruu.exe:
The ROM Update Utility cannot update your android phone
Please get the correct ROM Update Utility and try again
Possibly but I did have to return mine for repair and I know that using it as a .exe file trough windows I had no problem. Not sure about making it into a PC36IMG.zip file though I have not tried it that way.
Angrychair420 said:
thanks, that says its img version 1.32.651.1, assume thats safe to use. I assume thats andoid 3.26 which is what came on my phone. Ugh I'm in over my head. Why did my screen have to break, i was totally happy with CM7 and everything the way it was.
what if I wipe my data and caches, remove SD card, put on a PC36IMG.zip and boot the phone into hboot, will it still give me the older version error?
Click to expand...
Click to collapse
It might. There are 3 PC36IMG files in the first "My Links" link in my signature. You can try them in order if you'd like, if you get the "main version is older" message, but if the first two don't work, the last one definitely will.
Thanks cpt, about to give them a try. Sigh man, this is frustratingly harder than rooting :-D If it was as easy as doing the s-on and copy the pc36img.zip to the root of sd and booting into hboot and DONE, I would of been having a much better day.
Try the latest RUUs from this link man:
http://www.filefactory.com/f/acf0b850b0f70d7b/
Have you tried this?
http://htcevohacks.com/htc-evo-hacks/how-to-unroot-your-htc-evo-4g/
You can also try this
http://www.goodandevo.net/2011/03/how-to-unroot-your-htc-evo-4g.html
I appreciate the help guys. I will keep posted. You know how much it sucks to slide on a touchscreen thats broken? lol
partyman1971 said:
Have you tried this?
http://htcevohacks.com/htc-evo-hacks/how-to-unroot-your-htc-evo-4g/
Click to expand...
Click to collapse
Yes, that's the first RUU.exe I tried. said this RUU can't update
ok i got a pc36img.zip installing from hboot right now.
edit:dang main version is older error. Trying a wipe then hboot then pc36img.zip
Same outcome, main version is older.
partyman1971 said:
Have you tried this?
http://htcevohacks.com/htc-evo-hacks/how-to-unroot-your-htc-evo-4g/
You can also try this
http://www.goodandevo.net/2011/03/how-to-unroot-your-htc-evo-4g.html
Click to expand...
Click to collapse
yes, they are basically the same method I used in my OP from xda forums.
On to captain_throwbacks second ruu.
Just to make sure, this all isn't in vain, and make you all hate me, after applying one of these successfully, my recovery should go back to factory and no longer be clockwork, right? or wrong, because I'm starting to think I am. But won't taking your device in for service with clockwork be a dead giveaway that it was rooted.
I think I'm just going to go get a new phone for a $100 deductible at this point. and replace the screen my self on my old one and keep it as a backup/test device. Thanks for all the help, but I am surrendering :-D hopefully I can reroot this thing again with unrevoked, since my hboot is still .97 and fix the screen my self.
It generally doesn't matter if its rooted. I've never unrooted since launch day. And I've had 3 screen replacements, 3 speaker rwolacements , a bezel replaced, and camera lens cover replaced (last time, I dropped it off with ICS), about to go get my 4th screen (just cracked it again lol).
Sorry for your experience/frustration.
sent from AOKP heaven
well last stupid question i promise, since i still have clockwork isntalled, i can just restore my CM7 backup, but how do i get s-off back, re unrevoked it i assume?
If your'e worried about the warranty thing, just flash a stock rooted rom, or use a phone repair service. i see three or four repair places on craigslist (granted, that you live in a large city).
yeah no worries. Got it back to S-OFF, and CM7 back on it, just going to fix the screen my self, ordered one for $15.
thread can be locked, deleted, or what ever.
Seriously. Dude, isn't there a sprint store near you?. Just take it in. Put a stockish rom on it if you're that worried about it. They should replace it for free.
sent from AOKP heaven
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?