Related
So I am as excited as everyone else about s-off. Been waiting for awhile, but in the haste of everyone rooting their phone, I haven't been able to find a thread about restoring s-on in case of warranty work. Have I over looked something?
lots of views but no comments. This is from the IRC if interested
<splayer7> sorry if this has been asked, but what about resuming s-on for warranty work?
<hyuh> splayer7: no, not available
splayer7 said:
lots of views but no comments. This is from the IRC if interested
<splayer7> sorry if this has been asked, but what about resuming s-on for warranty work?
<hyuh> splayer7: no, not available
Click to expand...
Click to collapse
Exactly what has been said. There is no unrooting or S-On restoring at this time. I would just wait if you haven't already. HTC Released their source codes today. Its only a matter of time before an easier root is available with unroot, and S-on.
Was told that we could s-on by running the RUU. Here's a link to some I've found but haven't tested any of this. http://droidangel.blogspot.com/2011/06/htc-sensation-ruushipped-roms-packaged.html
kevinliu2336 said:
Was told that we could s-on by running the RUU. Here's a link to some I've found but haven't tested any of this. http://droidangel.blogspot.com/2011/06/htc-sensation-ruushipped-roms-packaged.html
Click to expand...
Click to collapse
do we have any confirmation on this working correctly
Tried it, resets your ROM but doesn't reset s-off
Guys.. There is about a 25% chance at best that HTC will actually check the boot loader status before providing warranty service. Even if you are unlucky and they do, if you make enough noise they might make an exception and let you off the hook. I think that as long as the issue that you are trying to resolve isn't a direct result of s-off or root, it should be fine.
splayer7 said:
So I am as excited as everyone else about s-off. Been waiting for awhile, but in the haste of everyone rooting their phone, I haven't been able to find a thread about restoring s-on in case of warranty work. Have I over looked something?
Click to expand...
Click to collapse
Flash an official RUU, and the device will be S-ON! TESTED!
lge73 said:
Flash an official RUU, and the device will be S-ON! TESTED!
Click to expand...
Click to collapse
Are you sure man? Somebody else above tested and found the opposite..
If the ruu is left untampered with, the boot image will be replaced with a stock one. Boot image is where your s-off lives. So in theory it should without a doubt work. You just have to make sure the boot image is in the ruu
smoochiezz24 said:
If the ruu is left untampered with, the boot image will be replaced with a stock one. Boot image is where your s-off lives. So in theory it should without a doubt work. You just have to make sure the boot image is in the ruu
Click to expand...
Click to collapse
I used the rom.zip file included in an untouched RUU, and I checked it includes HBOOT, also saw version change when I went into HBOOT.
It does NOT reset S-OFF back to S-ON.
I dont know if when you flash it reads S-OFF so keeps it, for users who genuinely had S-OFF?
I have personally tested this, and can confirm that using HTC's stock RUU does not return the phone to S-ON. However, it did remove the top area that says revolutionary, so now it appears as though I have a factory S-OFF device
Sent from my HTC Sensation 4G using XDA App
bummer.. I really hope there is a way to reverse s-off, just in case. but then again, I do have insurance so I guess I could say it was 'stolen' if I really need to get it replaced
prank1 said:
For those worrying about warranty issues..
You can try flashing the correct RUU for your phone.
IF that doesn't get rid of -revolutionary- s-off, then you can flash the ENG HBOOT (which gets rid of -revolutionary- but gives you ENG S-OFF) then you can flash the correct RUU for your region (which will definitely get rid of ENG S-OFF, and make you official stock HBOOT S-ON)
Click to expand...
Click to collapse
Try flashing ENG HBOOT, then the RUU afterwards.
I am going to try to get my phone back to S-ON now, just to test everything
EDIT
Hmm, very odd indeed, after flashing the RUU I have 'stock' Radio S-OFF (no -Revolutionary-) , I tried fastboot oem write secuflag 1 and fastboot oem writecid HTC__001 but I am still Radio S-OFF.
Just so people know, flashing full RUUs, even HBOOTs do NOT get rid of Radio S-OFF. Thats why it is favored by people, it can only be turned S-ON specifically by tools which may be released for the Sensation in the near future. I thought these tools only sent the commands that I tried to change the Radio security status. It would appear not.
However
There is no need to worry, Radio S-OFF probably won't void your warranty (if you sent it to a HTC repair center), as long as you have the correct CID and ROM installed you should be fine.
If I remember correctly, with the past Android phones, some people randomly got S-OFF (like sensation users did) out of the box. The HTC repair center didn't care. They don't like custom ROMs, custom HBOOTs, rooted ROMs, etc
I have an HTC One X with 3.18 firmware that is rooted, SuperCID, S-OFF and unlocked. I want to return it to stock, unroot and re-lock - basically I want to get it as close to stock as possible.
I made a backup of the stock ROM prior to flashing a custom ROM onto it, so I was able to restore that.
So here is how I assume I need to go about this:
unroot - not sure how to do this, I can't RUU 3.18 can I? I'm downloading the stock OTA right now just in case.
set the bootloader back to "locked" using this: http://forum.xda-developers.com/showthread.php?t=2168578
Is this correct? Do I need to undo the SuperCID? Is it possible to undo the S-OFF?
Why are you returning it to stock?
Sent from my Sony Tablet S using xda app-developers app
exad said:
Why are you returning it to stock?
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
It's a work phone. My bosses didn't care about me rooting it, but I will need to return it eventually to exchange it for another phone and it needs to be stock in case another employee gets it.
See the problem with that is, you've rendered it to a state whereby, if you relock and S-ON and the next person who uses it runs into an issue and wants to RUU or an update comes out, the phone will brick.
But yes, essentially, you're on the right track, RUU, to change CID back "fastboot oem writecid CWS__001" Then, I can't recall how to get Security flag back to S-ON but it is mentioned on this forum, I just don't have time to look for it, being at work.
Then you can relock
But just remember that if the next person RUUs or updates they will certainly brick. I would never root a company phone, for future reference.
exad said:
See the problem with that is, you've rendered it to a state whereby, if you relock and S-ON and the next person who uses it runs into an issue and wants to RUU or an update comes out, the phone will brick.
But yes, essentially, you're on the right track, RUU, to change CID back "fastboot oem writecid CWS__001" Then, I can't recall how to get Security flag back to S-ON but it is mentioned on this forum, I just don't have time to look for it, being at work.
Then you can relock
But just remember that if the next person RUUs or updates they will certainly brick. I would never root a company phone, for future reference.
Click to expand...
Click to collapse
Ah, gotcha. I didn't know that would happen when I unlocked and rooted - thought I had read everything I needed to about it prior to rooting, but I guess I missed that.
I guess I could just RUU, change the CID back, but leave it as S-OFF. That would keep it from getting bricked, right? The chances of it being an issue would be pretty slim I imagine.
Yes but then you also leave a big security hole open aswell.
Sent from my Sony Tablet S using xda app-developers app
exad said:
Yes but then you also leave a big security hole open aswell.
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
So there's really no way to return it back to stock? That's kind of a bummer...
So I'm currently returning my phone to stock.
In some steps for returning the phone to stock I've seen them tell you to lock the bootloader prior to flashing the RUU. This doesn't sound right to me but I wanted to check. Here are the steps I'll be taking:
1. Change CID back to stock - fastboot oem writecid CWS__001
2. flash RUU
3. Lock the bootloader - fastboot oem lock
4. Set it to s-on - fastboot oem writesecureflag 3
In some sets of instructions I've seen steps 2 and 3 switched around. I just want to make sure I get these in the right order.
kimboinatl said:
So I'm currently returning my phone to stock.
In some steps for returning the phone to stock I've seen them tell you to lock the bootloader prior to flashing the RUU. This doesn't sound right to me but I wanted to check. Here are the steps I'll be taking:
1. Change CID back to stock - fastboot oem writecid CWS__001
2. flash RUU
3. Lock the bootloader - fastboot oem lock
4. Set it to s-on - fastboot oem writesecureflag 3
In some sets of instructions I've seen steps 2 and 3 switched around. I just want to make sure I get these in the right order.
Click to expand...
Click to collapse
Sometimes the ruu fails if your bootloader is locked, but if it works, then you can lock it afterwards. It should work fine since you're s-off. Also, being s-off doesn't (shouldn't) void any warranties, so that step isn't necessarily required.
RollTribe said:
Sometimes the ruu fails if your bootloader is locked, but if it works, then you can lock it afterwards. It should work fine since you're s-off. Also, being s-off doesn't (shouldn't) void any warranties, so that step isn't necessarily required.
Click to expand...
Click to collapse
Excellent, so I can just RUU and then lock. I think I may just leave it as s-off - I'm leaving a security hole, but my main concern is just getting it back to stock without root.
Also just to confirm, the RUU will set recovery back to stock as well, right?
EDIT: Crap, just realized my tampered flag is still on. The RUU doesn't fix this, right? Guess I need to remove this first.
kimboinatl said:
Excellent, so I can just RUU and then lock. I think I may just leave it as s-off - I'm leaving a security hole, but my main concern is just getting it back to stock without root.
Also just to confirm, the RUU will set recovery back to stock as well, right?
Click to expand...
Click to collapse
Yessir. Everything should be back to stock except your CID (use the writeCID command), your bootloader (fastboot oem relock), and your s-off which you can leave as is.
Edit: it should remove the tampered flag. It did when I ruu'ed. Which ruu are you running?
RollTribe said:
Yessir. Everything should be back to stock except your CID (use the writeCID command), your bootloader (fastboot oem relock), and your s-off which you can leave as is.
Edit: it should remove the tampered flag. It did when I ruu'ed. Which ruu are you running?
Click to expand...
Click to collapse
I'm using the 3.18 RUU (RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed.exe).
I found a thread that has instructions on changing RELOCKED to LOCKED here:
http://forum.xda-developers.com/showthread.php?t=2168578&highlight=lock+status+flag
Do I need to do this? My understanding is that it will forever say "RELOCKED" unless I actually set it back myself somehow, but would an RUU do this for me?
kimboinatl said:
I'm using the 3.18 RUU (RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed.exe).
I found a thread that has instructions on changing RELOCKED to LOCKED here:
http://forum.xda-developers.com/showthread.php?t=2168578&highlight=lock+status+flag
Do I need to do this? My understanding is that it will forever say "RELOCKED" unless I actually set it back myself somehow, but would an RUU do this for me?
Click to expand...
Click to collapse
When I ruu'd it set it back to locked
Sent from my HTC One XL using xda premium
31ken31 said:
When I ruu'd it set it back to locked
Click to expand...
Click to collapse
Really? RUU shouldn't have an effect on the LOCKED flag.
31ken31 said:
When I ruu'd it set it back to locked
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Are you sure? If so, did you happen to have s-off when you did this?
Yes and supercid
Sent from my HTC One XL using xda premium
kimboinatl said:
Are you sure? If so, did you happen to have s-off when you did this?
Click to expand...
Click to collapse
If he didn't (have s-off) he would have bricked.
I am also curious about this. If the combo of S-off and RELOCKED and RUU results in LOCKED, than its the first I've heard of it.
Running the RUU and UNLOCKED, I can say first hand, the result is that it still says UNLOCKED.
I went ahead and used the method here to set it back to LOCKED:
http://forum.xda-developers.com/showthread.php?t=2168578&page=3
I set the CID back to original, relocked the bootloader, set it to LOCKED with the above method, and did the RUU. Everything is now back to stock except for the s-off. I seriously doubt they'll look for it or even care really.
31ken31, I probably would have just tried what you did if this wasn't a work phone, I just didn't want to risk it.
Thanks to everyone for the help!
kimboinatl said:
the CID back to original, relocked the bootloader, set it to LOCKED with the above method, and did the RUU. Everything is now back to stock except for the s-off. I seriously doubt they'll look for it or even care really.
Click to expand...
Click to collapse
Or have any idea what S-off even means, for that matter.
And a few folks have randomly received S-off devices from the factory. So you can conceivably just claim "It was like that when I got it", if they happen to ask about it.
redpoint73 said:
Or have any idea what S-off even means, for that matter.
And a few folks have randomly received S-off devices from the factory. So you can conceivably just claim "It was like that when I got it", if they happen to ask about it.
Click to expand...
Click to collapse
Yes on both counts
I could have also claimed that I got one with super CID, I think I've read that it happens sometimes, but it was easy enough to change back so hey, why not.
I'll really miss having root though. It makes things so much better.
Hey everybody,
after updating to JB with the official RUU found here, the gps is not working properly.. i find it very annoying.
so i decided to downgrade the hboot and try to run the ICS ruu..
i read the tutorial found here - http://forum.xda-developers.com/showthread.php?t=1990043
but it says not to do that if the JB RUU was used.
the question is - is there any other way to downgrade the hboot? and which hboot version do i need?
thanks!
Yossi
You should follow these instructions for getting s-off on your phone then.
It's way more comfortable and can easily be undone than the method you linked to.
Before we had s-off I downgraded a couple of times by bricking/unbricking my device. I was successful, even after the JB OTA with super-cid, maybe I was just one of the lucky ones. Idk.
If you decide for bricking/unbricking, the downgraded bootloader version on your S4 (you're shure about that?) should not be higher but 1.06 or 1.09. Else it's useless.
rootrider said:
You should follow these instructions for getting s-off on your phone then.
It's way more comfortable and can easily be undone than the method you linked to.
Before we had s-off I downgraded a couple of times by bricking/unbricking my device. I was successful, even after the JB OTA with super-cid, maybe I was just one of the lucky ones. Idk.
If you decide for bricking/unbricking, the downgraded bootloader version on your S4 (you're shure about that?) should not be higher but 1.06 or 1.09. Else it's useless.
Click to expand...
Click to collapse
I can second that. I've downgraded and sent s off. S off wasn't as scary as I thought. It was actually easier than downgrading.
Good luck.
Sent from my HTC One S using xda app-developers app
I ran the JB RUU and my GPS isn't working right either. When I previously updated to JB via OTA, the GPS worked. Have you tried just running the RUU again? Maybe that will fix it.
thanks for your reply!
why do i need s-off? what is the next step after doing so?
and are you sure that it it is more safe than following the guide i attached?
thanks!
Yossi
You should do a search on s-off. It switches off the security flag on the phone and simply said it allows you to flash whatever you want on your phone to any partition on your phone. Bootloader version will be of no importance anymore as it simply overrides it...
Downgrading your bootloader is a complicated process, transferring a new bootloader in very little chunks on your phone via the integrated modem using linux. All clear so far?! :laugh:
Compared to all that, facepalm s-off is really easy... and much more efficient. Downgrading bootloader was/is a pain in the ass. I'm glad this is depracted by the s-off.
thanks all!
i know about S-OFFing from my old desire, but thanks for your explanation.
i guess i should try running the RUU again before.
Was on the Desire before the One S. :good:
Jep - RUU is pretty good to go. Just keep away from the TMO US JB OTA. This one might make it impossible to s-off your phone, as it might write protect the partition for s-cid.
so.. i followed the instructions - rooted my phone, changed to supercid and all..
but the S-OFF failed :\ i followed the instructions but when i rebooted to fastoot it's still "VLE PVT SHIP S-ON"
should i try to do that again? isn't it risky?
Please be more specific - what were you doing when what failed?
Else: repeat it until it works!
everything worked - i have a rooted phone with super-cid.
i followed the instructions and it seems like everything went according to the instructions. but it wasn't successful since i still see "S-ON" on fastboot.
are you sure i can do this again?
Very shure. I had some issues as well with my data connection and had to repeat that a couple of times.
yossif89 said:
i followed the instructions and it seems like everything went according to the instructions. but it wasn't successful since i still see "S-ON" on fastboot.
are you sure i can do this again?
Click to expand...
Click to collapse
At step 5 you MUST get the error 'remote 92 supercid' and not 'remote 99 unknown'.
If you get 99, the first thing to try is just power down completely, wait a few seconds, boot back into fastboot and try again. If that doesn't fix it, I don't know really but read around the facepalm thread, search for '99'.
thanks!
meanwhile i've read a lot and tried again - the problem is "error 99" and not 92..
i'm trying to fix it..
Okay so obviously to use any of the AOSP Roms with the 3.4 kernel, you have to s-off then RUU, ect.. ect...ect...
I'm on vanilla root-box 6/11 right now and it just refuses to keep apps in memory. I don't have time to really try a new ROM or learn how to s-off and stuff ATM. I plan to sometime next week., but in the mean time, I was wondering if I flash a ROM that uses the 3.4 kernel and then immediately flash a different kernel before even booting. Would that get me past the previous requirements?
kyleallen5000 said:
Okay so obviously to use any of the AOSP Roms with the 3.4 kernel, you have to s-off then RUU, ect.. ect...ect...
I'm on vanilla root-box 6/11 right now and it just refuses to keep apps in memory. I don't have time to really try a new ROM or learn how to s-off and stuff ATM. I plan to sometime next week., but in the mean time, I was wondering if I flash a ROM that uses the 3.4 kernel and then immediately flash a different kernel before even booting. Would that get me past the previous requirements?
Click to expand...
Click to collapse
Nope, you'll probably brick doing that.
kyleallen5000 said:
Okay so obviously to use any of the AOSP Roms with the 3.4 kernel, you have to s-off then RUU, ect.. ect...ect...
I'm on vanilla root-box 6/11 right now and it just refuses to keep apps in memory. I don't have time to really try a new ROM or learn how to s-off and stuff ATM. I plan to sometime next week., but in the mean time, I was wondering if I flash a ROM that uses the 3.4 kernel and then immediately flash a different kernel before even booting. Would that get me past the previous requirements?
Click to expand...
Click to collapse
You can't flash a different kernel because those ROMs require the 3.4 kernel. There are a few lucky individuals that have been able to flash the newer 3.4 ROMs without going through the s-off & RUU process but that is definitely not the norm. You could try it but you will probably end up in a boot loop just like I did. I was already s-off so I just had to run the RUU. But even doing the whole process isn't a very time consuming ordeal. I did the whole process on a friend's phone yesterday and it took around 30 minutes and was very easy.
RollTribe said:
Nope, you'll probably brick doing that.
Click to expand...
Click to collapse
Yeah i figured it was a long shot, glad i asked first lol. Thanks dude!
pside15 said:
You can't flash a different kernel because those ROMs require the 3.4 kernel. There are a few lucky individuals that have been able to flash the newer 3.4 ROMs without going through the s-off & RUU process but that is definitely not the norm. You could try it but you will probably end up in a boot loop just like I did. I was already s-off so I just had to run the RUU. But even doing the whole process isn't a very time consuming ordeal. I did the whole process on a friend's phone yesterday and it took around 30 minutes and was very easy.
Click to expand...
Click to collapse
Oh I'm sure it's not to bad, but I have no idea how to use fastboot or adb (I've lucked by without having to use either, at least to my knowledge). Plus I don't readily have a windows PC, I just want make sure I know what I'm doing before I even attempt it. I've been looking over gunnyman's adb for noobs (http://forum.xda-developers.com/showthread.php?t=1754018), I'll give it a shot sometime next week when I've worked up the courage. Thanks for the advice!
pside15 said:
There are a few lucky individuals that have been able to flash the newer 3.4 ROMs without going through the s-off & RUU process but that is definitely not the norm.
Click to expand...
Click to collapse
3.4 kernel requires only 3.18/2.14 hboot.
If you already meet those requirements there is no need to RUU to 3.18
If you don't need to RUU to 3.18, you don't need to S-OFF.
It's really just that simple.
exad said:
3.4 kernel requires only 3.18/2.14 hboot.
If you already meet those requirements there is no need to RUU to 3.18
If you don't need to RUU to 3.18, you don't need to S-OFF.
It's really just that simple.
Click to expand...
Click to collapse
I meant there are people who have gotten it to work on an older hboot. Also, you can't just update your hboot without doing the ruu. There's something else in the update that it requires. So if you were s-off and just updated your hboot to 2.14 like I tried, the 3.4 kernel ROMs still won't flash correctly. I had an 2.14 hboot and still had to run the ruu.
Sent from my One X using Tapatalk 2
pside15 said:
I meant there are people who have gotten it to work on an older hboot. Also, you can't just update your hboot without doing the ruu. There's something else in the update that it requires. So if you were s-off and just updated your hboot to 2.14 like I tried, the 3.4 kernel ROMs still won't flash correctly. I had an 2.14 hboot and still had to run the ruu.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Yes, you require all the files in the firmware zip. It's not so much the hboot that matters hence why I put 3.18 software/2.14 hboot.
The people who managed to do it with lower hboot did the 3.18 update at some point and then downgraded just the hboot using the modded hboot file.
exad said:
Yes, you require all the files in the firmware zip. It's not so much the hboot that matters hence why I put 3.18 software/2.14 hboot.
The people who managed to do it with lower hboot did the 3.18 update at some point and then downgraded just the hboot using the modded hboot file.
Click to expand...
Click to collapse
Not trying to start an argument or anything but, I have seen and responded to users that have gotten a 3.4 kernel ROM to boot on an older hboot without ever having done the 3.18 update. It's definitely not the norm and I wouldn't even recommend trying it but there are a few people that have done it successfully.
pside15 said:
Not trying to start an argument or anything but, I have seen and responded to users that have gotten a 3.4 kernel ROM to boot on an older hboot without ever having done the 3.18 update. It's definitely not the norm and I wouldn't even recommend trying it but there are a few people that have done it successfully.
Click to expand...
Click to collapse
The ones I've seen pull that off had run the 3.18 ruu then downgraded the hboot. If it was that simple I doubt the the Rom would say it was required. And even if it was pulled of it was done by not following directions. Noobs with this phone that don't know how quirky it is can brick it. So I recommend following the steps the Rom calls for. There are more bricks from people skipping steps or not following directions
Sent from my HTC One XL using xda premium
31ken31 said:
The ones I've seen pull that off had run the 3.18 ruu then downgraded the hboot. If it was that simple I doubt the the Rom would say it was required. And even if it was pulled of it was done by not following directions. Noobs with this phone that don't know how quirky it is can brick it. So I recommend following the steps the Rom calls for. There are more bricks from people skipping steps or not following directions
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I'm not saying it's that simple and yes, I agree about following the steps. That's why I said I wouldn't even recommend trying the newer ROMs without updating first. I have seen it work though. That's all I'm saying. Maybe those users were ignorant on exactly what they did but I'm just going on what I've read and responded to.
Same ken. I have not seen anyone manage without having 3.18 at some point and I chill on here and in facepalm quite often. In fact, I don't even have a physical body. I am just a conciousness who lives within a hoxl. j/k
Pside if you say you've seen it, that's cool. But it is true that I live on these forums and find it odd that I have not encountered that situation yet.
Sent from my HTC One X using xda app-developers app
exad said:
Same ken. I have not seen anyone manage without having 3.18 at some point and I chill on here and in facepalm quite often. In fact, I don't even have a physical body. I am just a conciousness who lives within a hoxl. j/k
Pside if you say you've seen it, that's cool. But it is true that I live on these forums and find it odd that I have not encountered that situation yet.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Go to my profile and look at my quoted posts or just go back a bit in the Carbon thread. You will see where I quoted someone who was s-on and on the 1.14 hboot that flashed one of the 3.4 nightlies successfully. He was wondering if his phone was going to mess up now. That's the only specific one I remember off the top of my head but I know I've seen others as well. Like I said I'm just going by what I read. They could be completely wrong, lying, or just ignorant noobs. I live on these forums as well and have absolutely no reason to make something like this up.
Sent from my One X using Tapatalk 2
Stuck...just displays the HTC logo on white screen.
I had cleanrom 5.0 final. TWRP, super SU, rooted, unlocked. Firmware 2.20.
I dropped in the new ROM, did a factory reset in TWRP, and installed new rom. I read that that would work with my current setup, but apparently not. I am unclear on the part where it says "Highly recommend latest Jellybean firmware and S-Off!" Not sure how to determine this or proceed. Things here seem to be getting increasingly more jargoned rather than step by step for those of us that do this once a year or so :/
I flashed back to 5.0 with no issues, but I would really like to try to get the cleanrom 7 working if possible. Any ideas?
It sounds like you're s-on, if so you'd need to flash the boot.img via fastboot. Is this the first ROM you've flashed? Please post your bootloader details.
Sent from my Evita
timmaaa said:
It sounds like you're s-on, if so you'd need to flash the boot.img via fastboot. Is this the first ROM you've flashed? Please post your bootloader details.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for your reply. You are correct, I am s-on. But I was able to re-load CleanROM 5. This is my second custom rom on this phone (the first being CleanROM 5). But this is only my third custom rom ever, so I am pretty much of a noober. :cyclops:
klaypigeon said:
I am unclear on the part where it says "Highly recommend latest Jellybean firmware and S-Off!" Not sure how to determine this or proceed. Things here seem to be getting increasingly more jargoned rather than step by step for those of us that do this once a year or so :/
Click to expand...
Click to collapse
The ROM threads are to inform you of the features and requirements of the ROM, not to be a step-by-step guide. There are plenty of step-by-step guides in various places, for those that care to read and look.
If you don't flash often, a good resource is my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237
My Index will at least point you to the s-off process. I intend to add some info about the 2.15 firmware (as people keep constantly asking about it), but work has been chaotic, to say the least.
Another good thing to do, is read through the more recent pages of the ROM thread, or do a search on the thread.
Thanks, I am subscribed to your index, that's where I found the ROM and what I used during my first flash.
I did the process for unlocking the 2.20 firmware about a year ago as that is what my phone came with. I assume that would have given me superCID and s-off in order to install my old ROM (CleanROM 5).
'CID Getter' says I have no CID, which I read means I have superCID.
Firmware : 2.20
SuperSU installed and functioning (I have root)
Current ROM: CleanROM 5 Final
S-ON
TWRP 2.3.1.0
So you think I need to do s-off as described here? http://forum.xda-developers.com/showthread.php?t=2155071
If I brick this phone I am using a clam-shell for a year until contract renewal :/
klaypigeon said:
I assume that would have given me superCID and s-off in order to install my old ROM (CleanROM 5).
Click to expand...
Click to collapse
You shouldn't be assuming anything. You just said the CID Getter says S-on. You can also confirm s-on or s-off by going into bootloader.
The main reason CleanROM7 will not boot, is that you forgot to extract boot.img from the ROM file, and flash it separately using fastboot. Some older versions of CleanROM didn't require this (boot.img was flashed in the AROMA installer), so that may be why you don't remember doing this.
S-off removed the requirement to flash boot.img separately (will flash in recovery automatically when you flash the ROM). It will also allow you to install hboot 2.15 and associated firmware, if you happen to suffer from signal drops or random reboots while on Sense 5 ROMs.
Further to that, CID Getter doesn't show your actual CID. The proper way to display your CID is by using the fastboot command "fastboot oem readcid". Like Redpoint said, you shouldn't be assuming anything.
Sent from my Evita
Well...its pretty much dead. I verified supercid and then I flashed the bootloader and now it is just in a slow bootloop. It shows the HTC developer splash screen and then shuts down then a few minutes later does it again and so on. Looks like I am clamshell bound.
What did you flash?
Sent from my Evita
Muahahaaha, WORKING! Had to hold down volume through 5 reboot cycles and it finally picked up bootloader. set S-OFF. Tried CleanROM every which way and flashed boo.img as well, never could get it to make it past google boot animation. Installed ViperXL and boot.img without issue. Jelly Bean 4.2.2 sweetness! I lost hope there for about an hour, glad I didn't launch phone into the woods.
timmaaa said:
Further to that, CID Getter doesn't show your actual CID.
Click to expand...
Click to collapse
Ha, that's not a very useful app, then. What is it actually reading?
---------- Post added at 09:24 AM ---------- Previous post was at 09:21 AM ----------
klaypigeon said:
Well...its pretty much dead. I verified supercid and then I flashed the bootloader and now it is just in a slow bootloop. It shows the HTC developer splash screen and then shuts down then a few minutes later does it again and so on. Looks like I am clamshell bound.
Click to expand...
Click to collapse
Do you mean "locked the bootloader" instead of "flashed"?
If you locked the bootloader, this is what is supposed to happen. Locking the bootloader assumes you will be running RUU, and renders the phone unable to boot normally.
I know you got it back up and running. But for future reference, this phone is almost never bricked, as long as the screen comes on.
---------- Post added at 09:26 AM ---------- Previous post was at 09:24 AM ----------
klaypigeon said:
Muahahaaha, WORKING! Had to hold down volume through 5 reboot cycles and it finally picked up bootloader. set S-OFF. Tried CleanROM every which way and flashed boo.img as well, never could get it to make it past google boot animation. Installed ViperXL and boot.img without issue. Jelly Bean 4.2.2 sweetness! I lost hope there for about an hour, glad I didn't launch phone into the woods.
Click to expand...
Click to collapse
Flashing boot.img manually is not necessary with s-off, it should happan automatically when you flash a ROM. I suspect you may be having trouble with CleanROM due to a buggy or outdated TWRP version. What version of TWRP are you using?
It also seems that you are pretty unclear about some of the basic concepts around flashing ROMs on this phone. It would probably benefit you to read and learn a bit more before something bad actually happens due to negligence.
I'm not sure what CID Getter is actually reading, but when I used it it came up with the incorrect CID, can't remember exactly what it was now but it was definitely incorrect because I already had SuperCID.
Sent from my Evita
Flashing boot.img manually is not necessary with s-off, it should happan automatically when you flash a ROM. I suspect you may be having trouble with CleanROM due to a buggy or outdated TWRP version. What version of TWRP are you using?
It also seems that you are pretty unclear about some of the basic concepts around flashing ROMs on this phone. It would probably benefit you to read and learn a bit more before something bad actually happens due to negligence.
Click to expand...
Click to collapse
I am using 2.3.1 TWRP. In the viperXL thread they said I may have to flash the boot.img if I had hboot 1.14 which I do. As far as read and learning, I do this once a year I am not a ROM junkie. Every time I do it I have to re-learn. I work in IT so it is a use it or lose it world in my brain - volumes of info in > volumes out
klaypigeon said:
I am using 2.3.1 TWRP. In the viperXL thread they said I may have to flash the boot.img if I had hboot 1.14 which I do. As far as read and learning, I do this once a year I am not a ROM junkie. Every time I do it I have to re-learn. I work in IT so it is a use it or lose it world in my brain - volumes of info in > volumes out
Click to expand...
Click to collapse
If you have s-off you don't need to flash the boot.img via fastboot, that's only required if you're s-on. It might be worthwhile updating your TWRP to the 2.6 version though.
What Redpoint was saying is that you need to have a firm understanding of what you're doing when it comes to modifying your phone. If you only do it once a year that's cool, but that probably means that once a year you need to brush up before making any changes to your device. Rushing in without the required knowledge is how bricks occur. This is only being suggested to help you, for your own good.
Sent from my Evita
klaypigeon said:
I am using 2.3.1 TWRP. In the viperXL thread they said I may have to flash the boot.img if I had hboot 1.14 which I do.
Click to expand...
Click to collapse
Only with hboot 1.14 or later and s-on. If s-off the protection which prevents boot.img from being written in recovery is bypassed.
I believe TWRP 2.3.1 was a pretty trustworthy version (although older). So not sure why CleanROM didn't flash. Might not be a bad idea to update to 2.6.0 (although the latest 2.6.4 seems to have some bugs).
klaypigeon said:
I do this once a year I am not a ROM junkie. Every time I do it I have to re-learn. I work in IT so it is a use it or lose it world in my brain - volumes of info in > volumes out
Click to expand...
Click to collapse
Yeah, I understand that you only do this on a seldom basis. And its a lot of esoteric knowledge to have to relearn (or take in, since things have likely changed since lasts time). However, that doesn't change the fact that not fully understanding all the concepts and steps can have dire consequences for your phone.