Related
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 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.
Hey guys, I'm fairly new at the rooting thing but I've manage to make some progress with my old phone, the DINC2. I used the HTC developer tool to unlock the bootloader and side load superuser and CWM recovery V5.0.2.0. Currently the phone functions perfectly as far as I can tell. I can reboot into recovery and superuser appears to be working correctly. I tried the RootChecker app and it reports the phone as rooted successfully. At this point can I safely flash new ROMs? Or do I have more work to do first. Here's some info on the phone:
Android version 2.3.4
Software number 6.01.605.05 710RD
Hboot 0.98
S-on RL
Oh, BTW, I don't need to use the cellular part of the phone as I'll only be using it on WIFI.
Any help or suggestions are greatly appreciated!
Thanks,
Eric
scheirere said:
Hey guys, I'm fairly new at the rooting thing but I've manage to make some progress with my old phone, the DINC2. I used the HTC developer tool to unlock the bootloader and side load superuser and CWM recovery V5.0.2.0. Currently the phone functions perfectly as far as I can tell. I can reboot into recovery and superuser appears to be working correctly. I tried the RootChecker app and it reports the phone as rooted successfully. At this point can I safely flash new ROMs? Or do I have more work to do first. Here's some info on the phone:
Android version 2.3.4
Software number 6.01.605.05 710RD
Hboot 0.98
S-on RL
Oh, BTW, I don't need to use the cellular part of the phone as I'll only be using it on WIFI.
Any help or suggestions are greatly appreciated!
Thanks,
Eric
Click to expand...
Click to collapse
You can flash roms, but since you are HTCdev unlocked you will have to flash the boot.img in fastboot. You'll have to search around for those instructions. If you want to avoid the hassle you can go full s-off and flashing roms will be fully in recovery.
If you are using it as only a wifi device, you may want to find CondemnedSoul's thread in the development section that disables the cellular radios.
gtdtm said:
You can flash roms, but since you are HTCdev unlocked you will have to flash the boot.img in fastboot. You'll have to search around for those instructions. If you want to avoid the hassle you can go full s-off and flashing roms will be fully in recovery.
If you are using it as only a wifi device, you may want to find CondemnedSoul's thread in the development section that disables the cellular radios.
Click to expand...
Click to collapse
I'd rather just go to S-off and be done with it. Just sounds like a better way. I'll look into what to do next, to get fully unlocked.
Thanks for the info!
Good choice.
Howdy! Lemme preface all of this by saying that I'm less than a noob here....really inexperienced. Here's the background......
I rooted my DInc and I can't even remember which unrevoked tool I used. I was just reading along and punching commands and when the process was done I was rooted. I installed CWM successfully and flashed to CM7.2 which I've been running for quite some time. Lately I got an itch to try a JB ROM like infected, so when I looked into it, it clearly says I need S-off to accomplish that flash so I checked and realized I was S-on still.
At this point, I added the unrevoked-forever.zip to my sdcard root and tried to flash that ZIP by way CWM and i get these error messages:
E: unsupported radio version
E: update failed. Check/sdcard/soff.log
E: error in /sdcard/unrevoked-forever.zip (Status 42)
I am running Android version 2.3.7 and radio baseband version 2.15.10.12.20
Is this one of those things that I shouldn't be trying from CM7.2 and I should've dealt with before my initial flash to CM7.2?? Basically I'm totally freakin lost and in WAAAAY over my element, so any guidance would be duly appreciated. Thanks in advance!
Scott
Just going to leave this right here...
http://unrevoked.com/rootwiki/doku.php/public/forever
Read the page, tell me what your issue is, and we'll go from there.
PonsAsinorem said:
Just going to leave this right here...
http://unrevoked.com/rootwiki/doku.php/public/forever
Read the page, tell me what your issue is, and we'll go from there.
Click to expand...
Click to collapse
Sorry....i guess it pays to be extra thorough in the description of the problem. The link you left me is the one that I followed. I researched achieving S-Off on the DInc first and found this same page in my research. I followed the process and all went smooth right up until i started to flash the unrevoked-forever.zip from my sdcard via CWM. The aforementioned error messages came up on my phone and it said the process failed.
I thought it might be because the radio baseband versions that are list as "supported" do not match mine
smvogel73 said:
I thought it might be because the radio baseband versions that are list as "supported" do not match mine
Click to expand...
Click to collapse
Sounds good to me. With the way HTC handles S-OFF, you don't really need it. I'd go the legit way and unlock your bootloader with HTCdev.
http://www.htcdev.com/bootloader/
Edit: and for the record, you're lucky you didn't brick your device. Reading the supported requirements and ignoring them is a good way to do it.
PonsAsinorem said:
Sounds good to me. With the way HTC handles S-OFF, you don't really need it. I'd go the legit way and unlock your bootloader with HTCdev.
http://www.htcdev.com/bootloader/
Edit: and for the record, you're lucky you didn't brick your device. Reading the supported requirements and ignoring them is a good way to do it.
Click to expand...
Click to collapse
Yes thx....I'm gathering that! So this is where terminology gets so dang confusing for me. I didn't think unlocking my bootloader meant the same thing as achieving S-Off?? I already thought my bootloader was unlcoked, as I was able to flash CM7.2, which I didnt think I would be able to do if I had a locked bootloader. So wicked confused!!! And try as I miught to educate myself in these forums, I haven't located a sticky or guide that really thoroughly explains all the vernacular regarding android dev/modding/rooting/flashing/etc
So this other method will work with any radio baseband version then?? Or is it important to check compatibility there too??
What's the very top of your HBOOT say, UNLOCKED? Some more reading:
S-Off vs Unlocked, and flashing firmware
About Unlock and S-ON
PonsAsinorem said:
What's the very top of your HBOOT say, UNLOCKED? Some more reading:
S-Off vs Unlocked, and flashing firmware
About Unlock and S-ON
Click to expand...
Click to collapse
It says "UNLOCKED" and below that it says "S-ON
Thank u for the materials too!
So after looking at those two links, it sure seems like not only is S-Off a potentially dangerous thing to do, it might also not even be necessary on the long-run. I say that carefully tho, as u just got thru telling me that flashing a new ROM against spec is a very dangerous thing to do and could potentially brick mu phone.
The ROM I'm looking to flash is Infection JB 4.2.2. The instructions say that if you're coming from. A non-AOSP ROM and are S-On that you've gotta extract boot.img and fastboot it after the ROM flash......whatever the heck that means???
smvogel73 said:
So after looking at those two links, it sure seems like not only is S-Off a potentially dangerous thing to do, it might also not even be necessary on the long-run.???
Click to expand...
Click to collapse
Correct. Staying S-ON minimizes the danger. It locks your radio, and HBOOT, which are the main dangers.
smvogel73 said:
I say that carefully tho, as u just got thru telling me that flashing a new ROM against spec is a very dangerous thing to do and could potentially brick mu phone.???
Click to expand...
Click to collapse
Not really ROM flashing, but radio and HBOOT flashing, which is what unrevoked-forever tweaks.
I'd try to flash it one more time. When you do, what, if anything, are you wiping? You should be doing a factory reset, system, and boot wipe/format, then flash the ROM.
If that doesn't work (it might not, it's been awhile since I've worked with S-ON devices), then we'll move on to S-OFF (if you want).
Oh no.....I didn't even attempt to flash the Infection JB ROM specifically because I was not able to achieve S-Off. Whether it was intended or not, yea.....u sufficiently scared me about bricking the phone if I'm not to spec per the developer.
Are u saying I should wipe and then try to flash this ROM despite still being S-On?
Up to you. Personally, if it were me, I would try flashing the ROM with S-ON. The inc is a very friendly device, as long as you don't try to break the HBOOT and/or radios. It is next to impossible to break those with S-ON.
If you want to go S-OFF instead, grab the latest supported radio from http://dinc.does-it.net/ and then do the unrevoked-forever.
PonsAsinorem said:
Up to you. Personally, if it were me, I would try flashing the ROM with S-ON. The inc is a very friendly device, as long as you don't try to break the HBOOT and/or radios. It is next to impossible to break those with S-ON.
If you want to go S-OFF instead, grab the latest supported radio from http://dinc.does-it.net/ and then do the unrevoked-forever.
Click to expand...
Click to collapse
Well there you have it....I will trust your wisdom (as it is far supperior to my own) and I shall flash this ROM tonight!! I already have a nandroid backup of CM7.2 that Im running, as well as a Titanium backup of all my user apps/files.
Sincerest thanks for all your help!!
Hello. Im no expert but i think Cyanogenmod is aosp so you should be good.
I was where you were 2 yrs ago when I rooted my 1st phone: a friends froyo Dinc (ahhh...froyo). A few months ago I aquired my own and went to research how to root GB and everything has changed and is now vastly more complicated. Also I think every phone has a locked bootloader but not encrypted and I think Soff is extra security since I've only encountered it on htc phones. Anyway I've managed to get my inc to Soff but its still locked, idk how lol
Sent from my ADR6300 using Tapatalk 2
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?