Related
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.
I have a few questions about s-off and being in the latest OTA.
Here is the short and skinny...
When my wife got the evo when it first was released last year i tried to root it since i wanted to install a program that needed root. i had no real idea on what i was doing and think i might have gotten root, although I am not sure. I never flashed any rom nor did I ever flash that apk and just gave up since I didnt want to break her new phone. (basically got a bit scared)
As for the main screen if you reboot and hold down volume and power, it will display "s-OFF".
She did the two Gingerbread updates OTA and is now on GB 2.3.3. stock.
I noticed that the hboot is set at 2.16...and it still displays "s-off".
I just read that there are different types of "s-off".
Now, the questions are:
1. Is her phone actually rooted?
2. Can I turn on the "s-off" to "S-ON" so that we can bring the phone in for repair?
3. Is there anything that anyone here can gain from her phone being in the state that it is in for people who cant get root under the latest hboot version?
4. I just read that s-off has multiple meaning. How can i tell which one I have on her phone? ie. radio, nand??
Thanks in advance.
pretty sure sprint wont notice the s off so dont bother going s on to ttake it in, even if they do, they dont really care anymore, so long as its got the stock os at least, but they really dont care bout it being rooted anymore
but yeah, your phone basicaly kept the root
I agree with LCL22.
Unrevoked does have an S-ON tool, but I've never used it and I'm not even sure it works anymore. Just leave it S-OFF and flash one of the stock unrooted ROMs from recovery. But I've heard people take their phones back with CM6/CM7 on there, MIUI, etc. It probably depends on the store/rep to be honest.
"Rooted" means having access to the SU binary (superuser). It's a linux thing. It's like having Administrator access to a windows computer. This allows complete control over the currently installed phone software.
S-OFF means that the phones protections have been disabled and you are free to flash unsigned ROMs via the bootloader (HBOOT).
S-OFF is nice, because you can flash any ROM you want via the bootloader; there is no need for a custom recovery to be installed. Of course you can also use the bootloader to flash a custom recovery such as ClockworkMod or Amon_RA.
github said:
I agree with LCL22.
Just leave it S-OFF and flash one of the stock unrooted ROMs from recovery.
Click to expand...
Click to collapse
Will flashing the latest unroot ROM from sprint (which is already on there from the OTA update) will turn the s-off to s-on??
Also, if it says s-off, does that mean that it is fully rooted?
The reason why she is considering bringing it into sprint for repair/replace is that is having problems sending texts multiple times to the person she is texting...basically, she sends one text and the receiver gets the same text 20 times.
Either there is something wrong with the phone, the network, or the fact that it is s-off and she is running a non-rooted rom. This issue has been happening since January and on the stock Froyo.
Lastly, I just noticed that she had advanced task killer and I uninstalled it just to make sure it wasnt anything that she has running which is causing the issues.
Thanks in advance.
amart79196 said:
Will flashing the latest unroot ROM from sprint (which is already on there from the OTA update) will turn the s-off to s-on??
Also, if it says s-off, does that mean that it is fully rooted?
The reason why she is considering bringing it into sprint for repair/replace is that is having problems sending texts multiple times to the person she is texting...basically, she sends one text and the receiver gets the same text 20 times.
Either there is something wrong with the phone, the network, or the fact that it is s-off and she is running a non-rooted rom. This issue has been happening since January and on the stock Froyo.
Lastly, I just noticed that she had advanced task killer and I uninstalled it just to make sure it wasnt anything that she has running which is causing the issues.
Thanks in advance.
Click to expand...
Click to collapse
S-off only means you are nand unlocked so you can flash a custom recovery and flash a ROM. To be rooted, you have to flash a rooted rom which 99.999% of all the ROMS are rooted on XDA.
S-off just means that you can flash an alternate recovery and custom roms. It doesn't mean that it is rooted.
check in your app list and see if the Superuser app is there. If it isn't, it probably isn't rooted.
S off is perfect! Don't go s on if you can help it.
At my local repair store I chatted with the tech (after running s on tool) if they even check. The guy said not usually. They mainly check if it is stock sense like the Rosie and stuff. And even then they don't usually. They only check if someone brings in their phone with technical or software issues. With hardware they don't bother.
But that is my store.
S off and root are separate things but they kind of depend on each other. To root permanently you need s off, at least for devices with nand.
Sent from my PC36100 using Tapatalk
But since the Hboot is listed as 2.16, Should I just flash a rooted stock rom to see if this clears up the texting problems she was experiencing?
Most importantly, will flashing a odexed rooted rom work or brick it because it has the 2.16?
amart79196 said:
But since the Hboot is listed as 2.16, Should I just flash a rooted stock rom to see if this clears up the texting problems she was experiencing?
Most importantly, will flashing a odexed rooted rom work or brick it because it has the 2.16?
Click to expand...
Click to collapse
Sprint is currently having issues on their end in regards to texting. I've attached an article that you can read over.
http://m.wired.com/gadgetlab/2011/07/sprint-sms-text-problem/
ENG S-OFF
EDIT: Nevermind, I just took the risk and it paid off.
I was actually about to start a thread asking the exact same thing. I'm selling my phone and I've heard that if it's not relocked it can't be activated on the Sprint network so I've been trying to get S-ON. I have "EVT2-2 ENG S-OFF" right now.
By the sounds of this all I really need to do is flash a good PC36IMG and all should be good, right? No chance of a brick?
i will read that shortly, but i am more interested in the fact that there is a OTA update done and it now has 2.16 as the hboot. Is this now going to brick if i try to flash a rooted stock rom since she isnt into custom roms?
Now, the questions are:
1. Is her phone actually rooted?
2. Can I turn on the "s-off" to "S-ON" so that we can bring the phone in for repair?
3. Is there anything that anyone here can gain from her phone being in the state that it is in for people who cant get root under the latest hboot version?
4. I just read that s-off has multiple meaning. How can i tell which one I have on her phone? ie. radio, nand??
Thanks in advance.
Click to expand...
Click to collapse
Answers :
1. If you flash a recovery.img it will be.
2. You can't really do anything with the s-off right now because I don't think that any of the tools that would do that have been updated to work with hboot 2.16.
3. I'm not sure if anyone can use what you have but I would write up a post in a dev thread to be sure.
4. There are only two meanings that I know of when it comes to s-off. The first is accepting the OTA while rooted which will put your phone in a weird state. If you can use your phone after then I don't think this applies to you. The other is just not having a recovery installed which will render you just unlocked and not rooted.
amart79196 said:
i will read that shortly, but i am more interested in the fact that there is a OTA update done and it now has 2.16 as the hboot. Is this now going to brick if i try to flash a rooted stock rom since she isnt into custom roms?
Click to expand...
Click to collapse
No. Flashing a regular rooted odex or deodex version of the RUU won't hurt you if your s-off. I would make a nand backup using amon ra recovery before flashing anything just to be safe.
Amon Ra Recovery - http://forum.xda-developers.com/showthread.php?t=705026
Rooted OTA ROM - http://forum.xda-developers.com/showthread.php?t=1133379
amart79196 said:
But since the Hboot is listed as 2.16, Should I just flash a rooted stock rom to see if this clears up the texting problems she was experiencing?
Most importantly, will flashing a odexed rooted rom work or brick it because it has the 2.16?
Click to expand...
Click to collapse
It doesn't matter what hboot you have so long as you're s off
No bricks don't worry. Bricks usually occur during manual radio updates
Sent from my PC36100 using Tapatalk
I have a bricked evo 4g that currently only boots to bootloader, The evo says " s-off ".......I have tried flashing RA recovery thats fails, Also tried running official Sprint 2.3.3 ruu, that also fails with usb error 17. I posted some screen shoots of the bootloader and what error i get after trying to flash custom reovery.. does anyone know of a fix... any help is always much appreciated thanks!
Hey,
well I can give you the new that your phone isnt bricked if it was it would not turn on and would pretty much be a "brick" hence the name. I am not good with this but captain throwback is the man on fixing borked devices. so you might want to look to some higher ups in the forum and ask for help!
kevo3000 said:
I have a bricked evo 4g that currently only boots to bootloader, The evo says " s-off ".......I have tried flashing RA recovery thats fails, Also tried running official Sprint 2.3.3 ruu, that also fails with usb error 17. I posted some screen shoots of the bootloader and what error i get after trying to flash custom reovery.. does anyone know of a fix... any help is always much appreciated thanks!
Click to expand...
Click to collapse
Rather than running an RUU from the computer, have you tried flashing a PC36IMG.zip through HBOOT? Try this one - it's the 4.54 Gingerbread stock ROM. If that flashes successfully (you might have to do it twice), then you can try flashing a custom recovery again.
Do you happen to know what hardware version you have? I notice you appear to have flashed my 0.76 ENG HBOOT modded to read 2.10 - if you did that on a newer hardware model, that would be bad. The block sizes on the newer hardware models are different than on the older versions, so you really can't use an HBOOT version prior to 2.10 on them (the one you have is actually 0.76).
Captain_Throwback said:
Rather than running an RUU from the computer, have you tried flashing a PC36IMG.zip through HBOOT? Try this one - it's the 4.54 Gingerbread stock ROM. If that flashes successfully (you might have to do it twice), then you can try flashing a custom recovery again.
Do you happen to know what hardware version you have? I notice you appear to have flashed my 0.76 ENG HBOOT modded to read 2.10 - if you did that on a newer hardware model, that would be bad. The block sizes on the newer hardware models are different than on the older versions, so you really can't use an HBOOT version prior to 2.10 on them (the one you have is actually 0.76).
Click to expand...
Click to collapse
Yeah I think the hardware version was 003 or 004, yeah even when i use the Pc36img in your post 1. Radio_v2 ok then 2-8 Fail-PU.
Kinda the same situation, but I think easier to fix
Ok hi. So here's the deal:
My EVO can boot into bootloader, and it can get into recovery. Cool right? NO!!!
here's where the problem starts: I installed a corrupted ROMand of course, like every ROM, I wiped everything before flashing that one, and ended up not having a system to fall back on... And now the only thing I can do is get into the Bootloader and recovery.
The following issues I'm having, and the thins I have tried are:
1. I have tried putting the PC36IMG.ZIP at the root of the sd card.
- That didnt work though, and I figured that would only make sense, due to the fact that in recovery, it says "E: cant mount sd card"... So why/how would it work in bootloader?
2. It says "wrong image" when it tries to update the IMG file
3. I'm not a complete noob, I am willing to try ADB, I just dont know the commands to use :-( and IDK what to "push" or, even how to get the computer (PC, NOT a mac) to recognize the phone since it's... well, borked, I guess.
4. I' guessing that's the ONLY way to truly fix the phone and flash another ROM... is from the PC? But if so, HOW? Please help me.
I had the same thong happen to me when I first unlocked my phone all you have to do is get a computer with a card reader and put that PCI36.img
On the root of your SD card and put it back in the phone and boot into the bootloader... And if the card still cannot mount then keep pulling it and turning the phone on and let it come on in bootloader everytime and adventully the bootloader will reconigze the SD card and install the recover.. this method has worked for me a fee times
Sent from my PC36100 using XDA
Other option is sometimes I do a factory reset and reboot my phone and the very first ROM I ever flashed reinstalls... Without going into the bootloader ofcourse
Sent from my PC36100 using XDA
Oh wait I just read that you said you CAN get into recovery.. well there is a option to mount SD card.. do that and then restart
Sent from my PC36100 using XDA
monty_python said:
Oh wait I just read that you said you CAN get into recovery.. well there is a option to mount SD card.. do that and then restart
Sent from my PC36100 using XDA
Click to expand...
Click to collapse
Thanks man, but here's th thing, it KEEPS saying "E: cant mount sd card" and "No such directory found". thats my proble that I am having. If only I can get the phone to pick up the sd card, my situation would be handled.
Hello everyone, I'm running into a bit of a problem here with my sister's HTC EVO 4G.
You see her phone is a remanufactured replacement model from Sprint, and naturally it has a few minor problems with it. She wasn't thrilled with the battery life, so I rooted and flashed CM7.1 on her phone. She liked the rom and liked the extra battery life after I did some tweaking. Two Months later, for some odd reason, her phone will not connect to the data network at all. I flashed CM 7.2, same problem. Contacted sprint, where they refreshed the signal to the phone, no luck. So I concluded that it was a hardware error. Problem is, Sprint won't work on the phone without the Stock Sense Rom installed. I thought: "No big deal, I'll just flash it back to the stock sense rom" right? WRONG.
Never have I ever been so enraged by a cellphone. No matter what I do, no matter what I try, this phone absolutely REFUSES to go back to the stock rom. I've tried flashing several PC36IMG.zip files from the sdcard in HBOOT, and I have also tried several RUU updates from my PC while having the phone in Fastboot USB mode.
Quick Info:
Phone: HTC EVO 4G
Baseband: 2.15.00.12.19
HBOOT: 2.18.0001
Bootloader = Unlocked
Security = ON (S-ON)
Trying to flash PC36IMG.zip from HBOOT results in the phone loading the zip (with the little vertical progress bar on the side) and after loading completely, it just goes on it's merry way, checking for any other zip files and then HBOOT loads normally.
Running the RUU .exe files on my computer goes smoothly right up until somewhere in the update progress I get Error 155 (Unknown Error).
Now, it's my understanding that I don't need S-OFF to go back to the stock Sense rom, but I figured I should try to get S-OFF anyways. So I downloaded unrevoked and try to apply it from CWM, and it fails stating that it's not compatible with my radio version. Funny thing is, in all the radio lists for the HTC EVO 4G, I don't see 2.15.00.12.19 anywhere. In fact, 2.15.00.08.08 seems to be the newest one, unless I'm reading the lists wrong.
Either way I'm completely stuck here, and now I have a whining teenage sister screaming at me because she doesn't have a phone on a friday night. Go Figure.. Please guys, I know I'm a noobie here, but do me a solid. Please help me out, I'm stuck, frustrated, and I'm getting to the point where it's time to crack open a beer or 3 and say "f**k it".
Thanks in advance,
Alcolawl
you dont need s-off to return to stock..try the guide below in my signature to unroot and return to stock
XenonV said:
you dont need s-off to return to stock..try the guide below in my signature to unroot and return to stock
Click to expand...
Click to collapse
Does it matter which RUU version I download? (I've been extracting the rom.zips from the RUU's temporary files). I have the most current one on my computer named: "RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.15.00.12.19_NV_2.33_release_234563_signed". I usually take the Rom from that, rename it PC36IMG.zip, place it on a freshly formatted sdcard, and reboot into bootloader and hope for the best.
well, if you want the bootloader to be returned to factory stock settings then you can follow the guide below, BUT if you just want to UN ROOT, just copy a stock rom like the one you named, and flash it thru RECOVERY menu (install zip from sd card), dont install it from the bootloader (white screen)
XenonV said:
well, if you want the bootloader to be returned to factory stock settings then you can follow the guide below, BUT if you just want to UN ROOT, just copy a stock rom like the one you named, and flash it thru RECOVERY menu (install zip from sd card), dont install it from the bootloader (white screen)
Click to expand...
Click to collapse
Sounds easy enough. While messing around and waiting for Dominos to arrive, I decided to flash MikG (first time doing so, so I wasn't sure what to expect). Lo and Behold, I updated the PRL and Data Profile, and her Data works again. She also likes how Sense looks more so than CM7. Aesthetics > Functionality in her book I guess. If it comes down to having to bring the phone to the Sprint store, I'll try flashing the image through Recovery instead of Hboot.
Thanks for the help man, really appreciate it.
Alcolawl said:
Sounds easy enough. While messing around and waiting for Dominos to arrive, I decided to flash MikG (first time doing so, so I wasn't sure what to expect). Lo and Behold, I updated the PRL and Data Profile, and her Data works again. She also likes how Sense looks more so than CM7. Aesthetics > Functionality in her book I guess. If it comes down to having to bring the phone to the Sprint store, I'll try flashing the image through Recovery instead of Hboot.
Thanks for the help man, really appreciate it.
Click to expand...
Click to collapse
no problem :good::fingers-crossed:
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?