Ok, so my friend tried flashing some new Rom in the Hboot and it didn't complete or something and it caused the phone to update the radio and turn S-on. So now we restored the phone since it wouldn't turn on and at the moment we are at 6.1.1 with the newest Radio_12.5 0.60.24_26.08.04.16_M, and rooted but S-on. Question is, how do we go about getting S-off?
We thought about unrooting and maybe restoring all the way back to stock but didn't know if that would allow us to even downgrade the radio? Is he just stuck? Any help would be great.
And to clarify, I didn't do it, or have any part of what happened, so comments about me flashing and not knowing what I was doing need not to be stated, I'm just trying to get some help from him as he has a 0 post count.
Thanks.
nm. problem solved
Related
well i finally rooted last week and so far all is well and i love CM6 and everything else about having root but there are just a few things ive been wondering and searching for that i cant find a straight answer for.
1. ive been reading that when i unroot my pri stays at 1.34 and doesnt update to 1.40. if i update it before i unroot does that solve my problem? or if i unroot then install the 2.2 official rom that is coming out soon will that also fix my problem?
2. rooting broke my 4g and i thought it was just cm6 but when i flashed a rom with working 4g it justs kept saying connecting to sprint will unrooting fix this?
3. and lasts i actually want to unroot because my phone is just acting a little crazy with all these roms ive been using nothing is 100% and i keep getting an error 170 and ive tried reinstalling htc sync and ruuing from fastboot and i just cant figure out what to do if anyone could help it would be greatly appreciated.
Try doing this: http://forum.xda-developers.com/showthread.php?t=715915
That should give you latest version with latest radios which might fix 4g problems. Did you flash latest radios before flashing CM6?
As far as unrooting you need to get stock 1.47 RUU and flash it. From what I read your pri will not revert to 1.40 but before you do this try the link I posted as that should make you completely stock with root. If that doesnt work I would also suggest you search for 4g fix, there are tons of threads on this. If all else fails you can unroot but it is much easier to troubleshoot your phone will its rooted. Just my opinion.
alright i did what that link said my phone is acting better but i cant tell if 4g is working since i only get it at my job my pri is still 1.34 just wondering if the pri actually affects things and if it will mess me up if unroot without pri 140 thanks for the help
Currently once you root your PRI goes to 1.34 permenatly. It shouldnt have any major effects on your phones performance. If yuo unroot your phone stays at 1.34 aain shouldnt cause any issues unless you try to exchange and find the exceptionally with it sprint rep.
Okay, I'm attempting to gain root access, basically I followed
# Arrow# [GUIDE] How to root Android 2.2 on the EVO 4G
I flashed my phone back to the 2.1 froyo version, but now I am stuck, when I reboot my phone with unrevoked it automatically selects the first option HBOOT with no input from me.
I THINK this may have to do with the fact that I can't get the HBOOT driver's installed. I can't find where the driver's should be installed when rebooted. So now I'm stuck on FROYO 2.1, with no root access. I know that getting to 2.1 is the hardest part of root, but I need to know how to get the phone rooted. Please if anyone can post info, or has had a similar problem please post here if you can help me.
Did your phone originally have 3.30 on it? If so, you need to flash the leaked 3.30 rom back, then follow the instructions about how to turn S-OFF with hboot 2.02.
http://forum.xda-developers.com/showthread.php?t=828437
Where can I find instructions on flashing 3.3 I'm not even sure how I flashed 2.1
bump, if no one can help me get my phone rooted, can you at least let me know how to get it back to normal, so I have the built-in flashlight app etc.
i never thought i would need help with rooting, but i have the same problem. i have boot .97. which should make it easy. i am stock 2.1 and i am trying to flash a pc36img.zip but it simply wont load. it goes all the way to checking, and dumps me back at the hboot. no idea what i am doing wrong. i will try some troubleshooting now. ?!?!
edit i now have .79. trying to flash rooted pc... holding 3.29 now. wish me luck
same problem. goes from checking straight back to hboot. no idea at all.
hi guys, I have tried using the search function but there are so many posts with conflicting information for different dates, I just thought i'd ask.
I need to get my DHD back to stock for now, Im running Leedroid gingerbread (2.36.405.8) which i think is formatted with ext-4 or whatever, I have eng s-off and super cid
Just want to make sure before I do any changes that what im about to do is correct or not..
Do I downgrade to the old version (1.32) and then temproot, then use the radio -s to get radio on ?
Then I can do an OTA and it'll be completely stock?
Im just confused, so a little help would be nice thanks.
Alos i'd like to know if the above method will get rid of clockwork mod recovery, or do I need to get rid of that manually?
right i've gone ahead and had the "guts" to do it without any help, i've downgraded to 1.32 and i've put radio-s back on and default CID, but still cant get OTA updates?
Why is this?
I've tried putting radio-s off again and changing the CID to vodafones one, and then radio S back on again, and diff combinations, but to no avail.. can anyone tell me why im not getting OTA update?
nvm, done it now. done a factory reset in bootloader and it's ok can get OTA now.
Hey guys,
i've updated the radio to 32.56.0032U_5.17.05.23. from this time i got hard problems. the wlan turns on and off all the time, and if i want to go in the wlan-settings the device freezes, if i install an app the device freezes too, well actually it freezes at everything lol. even a ruu cant delete the s-off.
is it bricked? or what is this?
i hope you guys could help me
Lol bricked. Such an over used word nowadays. Just flash an older radio.
yea the ruu put an older radio on, but still doesnt work.
and why doesnt the ruu remove s-off?
If you got the newer hboots then you will need the downgrader hboot to downgrade.
Swyped...
so i did a downgrade, but s-off and its hboot is still there....
i got it fixed, mods can close/delete the thread
Tell us first what you did exactly to fix your problem, that might help someone else in the future.
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?