Hey guys....
I feel really stupid about this entire thing but I've finally decided to post here because I'm getting desperate.
The guide in question (http://forum.xda-developers.com/showthread.php?t=1563342) is fairly striaghtforward. Except the links are really scattered, at least for me. I'm on HBOOT 1.58, and I've had numerous problems even getting to the point where my phone is relocked (it's currently HTC unlocked because I use an MIUI port ROM) successfully. I would bring my problems to that thread, but I don't have 10 posts, which is a questionable rule but w/e.
Anyway, here's my problem. First, I'll tell you what I've done so far, and the problem I've come across both times.
1. Place a "2.89 RUU" or whatever onto my SD card and call it PG86IMG. This is where most of my confusion is. OP of that thread hasn't yet covered what the difference between 2.17 and 2.89 is, but my understand is that 2.17 corresponds with HBOOT 1.5 and 2.89 to 1.58. Honestly, all these numbers piss me off when there's little to no documentation of what the hell they even mean. This file is about 448 MB and my understanding was that it was a stock RUU and would make it so I could access my phone while it was still locked, which you can't do with a 3rd party ROM like the one I usually use.
2. Lock my phone's bootloader. I just did fastboot oem lock in Windows and it rebooted to *** RELOCKED *** *** Security Warning ***. Apparently this is normal, and now I need to flash said RUU.
3. Flash the RUU. This took an EXTREMELY long time, and it went through Loading PG86IMG.zip.. then to some other stage that took much less time to complete. After that it just sits in the bootloader.
Here's my concern... I can't access my SD card. Why? Because I can't even get out of the bootloader or fastboot. All it does is sit here, and since I can't remove the update file PG86IMG.zip, if I try to enter recovery (which I'm sure won't work anyway) it will try to start loading that file again. I don't really know what step I missed here, but it's probably because I'm fairly clueless when it comes to this stuff, lol.
So, I did this once, and then I waited about 6 hours for HTCdev's site to stop crashing so I could unlock my phone again. Made it through a school day with my old ROM and stuff, deleted the update files so they wouldn't run again, etc. etc.
Now, I'm doing it again today with this new 2.89 RUU or whatever and the same exact problem is happening. So now I'm at a stage where my phone is entirely useless until HTCdev.com starts actually sending e-mails. I swear, these crashes on HTCdev's part could not be more untimely.
So basically, what am I doing wrong with relocking my phone? OP implies that I should be able to start my phone (not the bootloader, but actually start it) because they ask after you've supposedly re-locked the bootloader for you to move a new PG86IMG.zip file onto your SD card, which I'm unable to do because my phone can't get out of fastboot/bootloader screen. That's the next step, which is actually doing the downgrading.
And yes, I know that it's possible for HBOOT 1.58 because someone else already did it (last post in the thread).
At this point, I don't really care when I get it to work, man. This is proving to be such a gigantic pain in the ass just to install a new Jelly Bean ROM. I JUST WANT JELLY BEAN!
If anyone can send a noob in the right direction, that'd be great. I have all week and all weekend, but I've run out of time to waste on this for today. I guess most of what I need is to know what files I'm supposed to be downloading, because I have a feeling that's most of what I'm getting wrong.
I hope I've explained my problem well enough, and thanks a ton to anyone who just suffered through reading my essay and can offer help. I'll be sending this to OP of the guide as a PM so hopefully if none of you guys can help they can.
Thanks a ton everyone, I just want to get Jelly Bean on my phone and stop dealing with MIUI :laugh:
Update: Found this thread: http://forum.xda-developers.com/showthread.php?t=1495358. I believe this will probably help me out a lot! Wish I would've seen it sooner.
TL;DR: Need better explanation of how to relock 1.58 hboot bootloader with a stock rom, and where to find the rom.
Honestly, your post was tl;dr for me, but I think you would be best served to follow ramjet's guide to s-off. It's really the easiest and includes everything you need.
http://forum.xda-developers.com/showthread.php?t=1889438
coal686 said:
Honestly, your post was tl;dr for me, but I think you would be best served to follow ramjet's guide to s-off. It's really the easiest and includes everything you need.
http://forum.xda-developers.com/showthread.php?t=1889438
Click to expand...
Click to collapse
Lol. I'm not surprised. I tend to pour my heart out on forums when I get to the point of desperation.
Gonna be honest with you, zero interest in the wire tap method. Zero. Not trying it. Not even going to think about it. Sorry, I appreciate the idea but honestly screw that.
Logic33 said:
Lol. I'm not surprised. I tend to pour my heart out on forums when I get to the point of desperation.
Gonna be honest with you, zero interest in the wire tap method. Zero. Not trying it. Not even going to think about it. Sorry, I appreciate the idea but honestly screw that.
Click to expand...
Click to collapse
Then, honestly, you are EXTREMELY limited as to what you can do. S-Off is your best bet. Good Luck.
raptoro07 said:
Then, honestly, you are EXTREMELY limited as to what you can do. S-Off is your best bet. Good Luck.
Click to expand...
Click to collapse
I don't understand how that limits me at all. I just want to use the downgrade method to hboot 1.4 and s-off. I never had any intention of staying on hboot 1.5, and certainly not hboot 1.58.
Logic33 said:
I don't understand how that limits me at all. I just want to use the downgrade method to hboot 1.4 and s-off. I never had any intention of staying on hboot 1.5, and certainly not hboot 1.58.
Click to expand...
Click to collapse
From my understanding, the downgrade method works with hboot 1.58, but you have to brick your phone twice. But it really is the more challenging method so you may want to reconsider your stance on the wire trick. I've yet to hear of an unhappy customer who followed ramjet's guide.
coal686 said:
From my understanding, the downgrade method works with hboot 1.58, but you have to brick your phone twice. But it really is the more challenging method so you may want to reconsider your stance on the wire trick. I've yet to hear of an unhappy customer who followed ramjet's guide.
Click to expand...
Click to collapse
I'm not sure.
However, this thread can be closed because I *finally* got the RUU to work properly! I was doing things in the wrong order, and not using the .exe was a silly idea. It's much easier that way. Currently have stock ROM running on a locked 1.58 hboot. Now I can continue!
Logic33 said:
I'm not sure.
However, this thread can be closed because I *finally* got the RUU to work properly! I was doing things in the wrong order, and not using the .exe was a silly idea. It's much easier that way. Currently have stock ROM running on a locked 1.58 hboot. Now I can continue!
Click to expand...
Click to collapse
Good! :thumbup:
Keep posting questions, we'll do our best to help.
coal686 said:
Good! :thumbup:
Keep posting questions, we'll do our best to help.
Click to expand...
Click to collapse
LOLJK. I swear, at this point HTC must be trolling me. It's loaded up now. Thanks for trying to help everyone! I can't wait to get Jelly Bean on here soon!
Doubt this will help, but did you remove the PG86IMG.zip from your sd card? Also, did you run the ruu.exe while in bootloader (it will say fastboot usb in red). I'm sort of grasping at straws since the ruu usually works without issue when using the exe.
coal686 said:
Doubt this will help, but did you remove the PG86IMG.zip from your sd card? Also, did you run the ruu.exe while in bootloader (it will say fastboot usb in red). I'm sort of grasping at straws since the ruu usually works without issue when using the exe.
Click to expand...
Click to collapse
I have a feeling you didn't see my update It magically decided to work. Here comes double bricking action... this should be (un)fun D:
i am on hboot 1.58 and used HTC Unlock and wire trick to get s-off. i was about to flash a JB Rom but realized that it requires hboot to be lower than 1.58. so all i do is pick the first hboot 1.40 from Here, put it in the root of SD, boot up the phone in recovery and flash that PG86IMG.zip.
once its done ill swap the SD with another one which would have the ROM i want to install, then boot again in recovery and wipe Dalvik+cache, and then flash ROM?
am i doing it right?
thank you.
chubaan said:
i am on hboot 1.58 and used HTC Unlock and wire trick to get s-off. i was about to flash a JB Rom but realized that it requires hboot to be lower than 1.58. so all i do is pick the first hboot 1.40 from Here, put it in the root of SD, boot up the phone in recovery and flash that PG86IMG.zip.
once its done ill swap the SD with another one which would have the ROM i want to install, then boot again in recovery and wipe Dalvik+cache, and then flash ROM?
am i doing it right?
thank you.
Click to expand...
Click to collapse
No, do it from the bootloader
Sent from my skz_tenderloin using xda premium
fdavila17 said:
No, do it from the bootloader
Sent from my skz_tenderloin using xda premium
Click to expand...
Click to collapse
I have the exact situation with my wife's phone? I want to install Pacman on her phone which is still stock. Is all I have to do what chubaan said?
ruckstande said:
I have the exact situation with my wife's phone? I want to install Pacman on her phone which is still stock. Is all I have to do what chubaan said?
Click to expand...
Click to collapse
Just download the hboot you want, 1.50 or below to get PACMAN to.boot, rename it as PG86IMG.zip place it on the root of your sd card, go to.the bootloader and select yes to apply update , and your done
Sent from my PG86100 using xda premium
Thank you.. that's what I did. And after you're done make sure to wipe dalvik and cache from recovery, at least in my case I had to. And then flash the rom. And that's it..
Sent from my PG86100 using XDA Premium App
Related
http://www.multiupload.com/NOLWGVUTMZ
6c4babc9c39ca1c4e92030202a4ce413 hboot_8x60-lte_2.11.2005_111221_MR2_signedbyaa.nb0
Its just a eng hboot, its not a magic key, its not a banana split, it doesn't magically give you s-off. No instructions because I have none for you. Sharing in hopes that it furthers someone else's project as well.
This is apparently debug signed, don't attempt to flash it to s-on device. Ship s-on hboots won't flash it, even if you were able to sign an RUU properly.
for the s-off users, this allows extra fastboot commands
Not to imply doubt but is this for real?
With s off and such?
Awesome
kidwolf908 said:
Not to imply doubt but is this for real?
With s off and such?
Awesome
Click to expand...
Click to collapse
Wondering the same....
does this give S-OFF?
con247 said:
does this give S-OFF?
Click to expand...
Click to collapse
If it does, I think we're about to see a bunch of computers ruined by the nerdgasms that will follow.
according to his twitter it doesn't flash but he just wants to post it anyway
jcase said:
http://www.multiupload.com/NOLWGVUTMZ
6c4babc9c39ca1c4e92030202a4ce413 hboot_8x60-lte_2.11.2005_111221_MR2_signedbyaa.nb0
Its just a eng hboot, its not a magic key, its not a banana split, it doesn't magically give you s-off. No instructions because I have none for you. Sharing in hopes that it furthers someone else's project as well.
Click to expand...
Click to collapse
Now I'm CRAVING a banana split, you rat bastard!
Careful with flashing things like this. Advanced users only please. I can see the newbs going flash crazy. Had anyone flashed yet? Thanks for this jcase. I appreciate you helping out by doing things like this even though you don't have the phone
sent from my cm7 rooted fire
pwned3 said:
Careful with flashing things like this. Advanced users only please. I can see the newbs going flash crazy. Had anyone flashed yet? Thanks for this jcase. I appreciate you helping out by doing things like this even though you don't have the phone
sent from my cm7 rooted fire
Click to expand...
Click to collapse
Finding a way to flash it to a s-on phone is what the goal would be, then we are assuming its signed with the same key as the SHIP hboots. If someone could flash it, and the key is the same (I am assuming it is, but may not be) , then it would give you s-off.
Yes, flashed it to radio s-off phones, it works fine, enables all the extended fastboot commands.
pwned3 said:
Careful with flashing things like this. Advanced users only please. I can see the newbs going flash crazy. Had anyone flashed yet? Thanks for this jcase. I appreciate you helping out by doing things like this even though you don't have the phone
sent from my cm7 rooted fire
Click to expand...
Click to collapse
I tried flashing it with fast boot but it gave me a remote not allowed error.
Thank you jcase for this file.. let's hope someone figures it out
Sent from a cellular telephone
AFAIK you cannot flash an eng hboot to an S-ON device.
Be careful of flashing this. You can hard brick your phone with hboot. Seen it done on the E3D.
Just throwing that out there.
Edit:
Useless post
scrosler said:
AFAIK you cannot flash an eng hboot to an S-ON device.
Be careful of flashing this. You can hard brick your phone with hboot. Seen it done on the E3D.
Just throwing that out there.
Click to expand...
Click to collapse
This is incorrect, as long as everything is right signature wise, it won't brick. The problem is actually getting it to flash. However people shouldn't just go around flashing things without knowing what they are doing.
Lots of phones have gotten s-off b/c of an eng hboot, particularly the thunderbolt from us.
Thanks for putting this out there jcase
Sent from my ADR6425LVW using XDA App
If it helps, I could not flash this via fast boot nor in a PH98IMG.zip
dmeadows013 said:
If it helps, I could not flash this via fast boot nor in a PH98IMG.zip
Click to expand...
Click to collapse
stock hboot doesnt support flashing hboot throught fastboot
jcase said:
This is incorrect, as long as everything is right signature wise, it won't brick. The problem is actually getting it to flash. However people shouldn't just go around flashing things without knowing what they are doing.
Click to expand...
Click to collapse
Thats the point I am making. Know what you are go doing before you do it. And yes you can brick a phone with a a signed eng hboot. I have seen it done on Evo 3D. Either way...
So... How do you flash this to an S-ON device. I would love to have eng hboot.
scrosler said:
Thats the point I am making. Know what you are go doing before you do it. And yes you can brick a phone with a a signed eng hboot. I have seen it done on Evo 3D. Either way...
So... How do you flash this to an S-ON device. I would love to have eng hboot.
Click to expand...
Click to collapse
If he knew, he'd of told us, here's to hoping someone finds a way!
cant this be flashed with ADB?? thats how it used to be done on the OG evo i had
I am beyond feeling like a ReeeTard right now. As someone who beta tests for a lot of ROM builders and knows a great deal about Android, software development etc... please don't reply to this with a smart a** remark. It helps no one and makes you look like just a jerk.
We all have our days where we simply cannot think straight, I am dealing with a great deal of stress, in my life, so forgive me for somehow not finding the answer to this question.
I updated my phone, using an RUU...My phone WAS hboot 1.40, now however it's hboot 1.50, and it's UNLOCKED (the bootloader) as well as S-Off, Am I forgetting to do something to have ROOT access?
So I am hboot 1.50 UNLOCKED and S-off
With all of those things I thought, because I cant seem to think clearly right now, that I was rooted. I however ran root checker and I am not.
Please throw me a bone and fill me in on what I am missing here. It's been a rough couple weeks for me.
Much appreciated.
quickfixguru said:
I am beyond feeling like a ReeeTard right now. As someone who beta tests for a lot of ROM builders and knows a great deal about Android, software development etc... please don't reply to this with a smart a** remark. It helps no one and makes you look like just a jerk.
We all have our days where we simply cannot think straight, I am dealing with a great deal of stress, in my life, so forgive me for somehow not finding the answer to this question.
I updated my phone, using an RUU...My phone WAS hboot 1.40, now however it's hboot 1.50, and it's UNLOCKED (the bootloader) as well as S-Off, Am I forgetting to do something to have ROOT access?
So I am hboot 1.50 UNLOCKED and S-off
With all of those things I thought, because I cant seem to think clearly right now, that I was rooted. I however ran root checker and I am not.
Please throw me a bone and fill me in on what I am missing here. It's been a rough couple weeks for me.
Much appreciated.
Click to expand...
Click to collapse
Hey! No worries man. You're almost there. All you need to do is flash a recovery now. Choose a recovery, and flash it, either a pg86img.zip or a recovery.img, and flash it. Once you have recovery flashed, either just flash a rooted ROM, or flash a su.zip. Then you should be good to go.
Sent from my PG86100 using Tapatalk
Thanks a lot man, I appreciate it. I knew I needed to flash superuser I just wanted to be sure it was just flash a recovery then su.zip
quickfixguru said:
Thanks a lot man, I appreciate it. I knew I needed to flash superuser I just wanted to be sure it was just flash a recovery then su.zip
Click to expand...
Click to collapse
You're welcome. Glad to help. Let me know if you have further questions. if you just decide to flash a su.zip, as opposed to an entire custom rom, you'd probably have the best luck looking in the old original TWRP thread for one. I know that had a su.zip posted in it. I'll see if i can find it for you real quick.
EDIT: Here's a super user zip http://techerrata.com/toastcfh/Shooter/su-2.3.6.3-efgh-fixed-unsigned.zip that I found in the 3rd post of this old thread http://forum.xda-developers.com/showthread.php?t=1192077&highlight=twrp+recovery. That's not the newest super user app, but it should work just fine, and you should be able to update it from there once you get it installed.
buckley nailed it!
i was actually unaware that updating your bootloader would still leave you s-off if you were on 1.4. that is interesting... although i would still never update.
did you know that it would still leave you with your NAND unlocked when you updated?
cobraboy85 said:
buckley nailed it!
i was actually unaware that updating your bootloader would still leave you s-off if you were on 1.4. that is interesting... although i would still never update.
did you know that it would still leave you with your NAND unlocked when you updated?
Click to expand...
Click to collapse
Yea, updating will still leave you S-off. You won't have a custom recovery anymore, and you'll be on hboot 1.5, but you still have S-off. There is pretty much no way that I know of to turn it back to S-on without going into fastboot and doing that 'fastboot setsecureflag3' command or whatever it is. The revolutionary team gave us some pretty damn permanent S-off, lol. I've seen lots of people take OTA updates, and still have S-off. You can even downgrade the hboot back to 1.4 if you wanted to, even though there really isn't a reason to. Having hboot 1.5 with S-off is just the same as having 1.4 with s-off, you don't need to do any extra stuff to flash.
OK, so I bought the Rezound used and already rooted, I have just flashed viper 1.0.3 but my radios dont match up with the latest ones and I'm not sure if that might help battery life. The phone has AmonRu, sorry if this is covered somewhere... I searched and didnt come up with anything
also current baseband version is 1.22.10.0310r, 1.22.10.0308r
u didn't search well enough cause you're new. learn to search better before you get flamed and ignored. if you knew anything about Android you'd know that only the latest ruu could upgrade your radios since you're s-on
yes run a RUU
dyetheskin said:
u didn't search well enough cause you're new. learn to search better before you get flamed and ignored. if you knew anything about Android you'd know that only the latest ruu could upgrade your radios since you're s-on
Click to expand...
Click to collapse
It's just different from other androids (D1, D2) and even the other HTC's I've had (Incredible and Thunderbolt). So, I'd need to flash the latest RUU to get the radios, but can i do that with the amon recovery ? And if so, does the latest RUU break root? Like I said the guy I bought it from rooted it, he said he used htc dev tool to root it.
eric90gt said:
It's just different from other androids (D1, D2) and even the other HTC's I've had (Incredible and Thunderbolt). So, I'd need to flash the latest RUU to get the radios, but can i do that with the amon recovery ? And if so, does the latest RUU break root? Like I said the guy I bought it from rooted it, he said he used htc dev tool to root it.
Click to expand...
Click to collapse
You should do a little research before you attempt anything. Basically, you'll need to relock the boot loader using htcdev tool which is simple to do if you follow directions. Then you'll download the latest RUU and place it on the root of your SD card and then boot into the boot loader by powering the phone down and holding vol down and power. Then it will prompt for the update-choose yes. Once update is done you'll be completely stock and you'll need to unlock again with htcdev and install a custom recovery again. After that you can root again and flash ROMs. Sounds complicated, but if you plan to tinker with this phone these are MUST LEARN procedures.
Sent from my ADR6425LVW using Tapatalk 2
dyetheskin said:
u didn't search well enough cause you're new. learn to search better before you get flamed and ignored. if you knew anything about Android you'd know that only the latest ruu could upgrade your radios since you're s-on
Click to expand...
Click to collapse
Can't you tell from this post that XDA is just a warm, welcoming community geared towards helping people?
[/sarcasm]
localceleb said:
You should do a little research before you attempt anything. Basically, you'll need to relock the boot loader using htcdev tool which is simple to do if you follow directions. Then you'll download the latest RUU and place it on the root of your SD card and then boot into the boot loader by powering the phone down and holding vol down and power. Then it will prompt for the update-choose yes. Once update is done you'll be completely stock and you'll need to unlock again with htcdev and install a custom recovery again. After that you can root again and flash ROMs. Sounds complicated, but if you plan to tinker with this phone these are MUST LEARN procedures.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
In a nutshell, a good description of what to do. Kudos, localceleb for actually answering the question without making the OP feel unwelcome.
carngeX said:
Can't you tell from this post that XDA is just a warm, welcoming community geared towards helping people?
[/sarcasm]
In a nutshell, a good description of what to do. Kudos, localceleb for actually answering the question without making the OP feel unwelcome.
Click to expand...
Click to collapse
Yeah, I could feel the love so much I got goosebumps. One question is will I have any problems relocking the bootloader with viper rom installed or do i need to relock and immediately flash the img.zip for the ruu ?
Why wouldn't you just run the S-Off and not have to worry about things like this? I just find it amazing that people will go through the headache of unlocking their bootloader but not do the S-Off routine.
*Madmoose* said:
Why wouldn't you just run the S-Off and not have to worry about things like this? I just find it amazing that people will go through the headache of unlocking their bootloader but not do the S-Off routine.
Click to expand...
Click to collapse
S-off looks like it isnt as easy as it used to be, and cant get back from it in case of a warranty return
eric90gt said:
S-off looks like it isnt as easy as it used to be, and cant get back from it in case of a warranty return
Click to expand...
Click to collapse
You can get back to s-on
eric90gt said:
S-off looks like it isnt as easy as it used to be, and cant get back from it in case of a warranty return
Click to expand...
Click to collapse
It's still fairly easy. Once I got the right kind of wire (speaker wire instead of a paperclip), it literally took just a few minutes to complete it. Got the timing right on the first try with the right wire.
And like Ashton said, you can return to S-On.
Yeah, s-off is truly easy. I know it seems intimidating and complicated, but 95% of the process is automated scripts. Once again, if you follow directions and take your time, its easy. I was surprised at how easy it was once I've completed it. Now I've done the process 5+ times and it takes less than 3 minutes from start to finish.
Sent from my ADR6425LVW using Tapatalk 2
Make your the RUU is a zip and name it PH98IMG. S-OFF seems complicated, but it's not all you have to do is make sure you are rooted and have dev unlocked your phone run ControlBear and do the wire trick when told to. If you fail just leave the phone alone and close/open ControlBear again and keep trying.
localceleb said:
Yeah, s-off is truly easy. I know it seems intimidating and complicated, but 95% of the process is automated scripts. Once again, if you follow directions and take your time, its easy. I was surprised at how easy it was once I've completed it. Now I've done the process 5+ times and it takes less than 3 minutes from start to finish.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
I will say it was a giant pain in the ass for me. I followed the timing and was pretty careful about it but it just didn't work. I was using a paperclip (uninsulated) so maybe that's why, but I eventually just spammed the other terminal and one of those times it took. haha
Bensky91 said:
I will say it was a giant pain in the ass for me. I followed the timing and was pretty careful about it but it just didn't work. I was using a paperclip (uninsulated) so maybe that's why, but I eventually just spammed the other terminal and one of those times it took. haha
Click to expand...
Click to collapse
I got it to almost work only once with a paperclip. It failed at the end though (gave still sober message). After about 20-30 minutes of fiddling with it... I got sick of it. Took off one of the wires from my home theatre (18 guage probably, and ~25 ft lol), and used that. Worked the first try lol.. So yeah, been recommending actual wire rather than paperclips if possible.
hello, everyone i had my rezound since back in December. im still S-on (yeah i know im trying to get s-off ). I had the phone for a long time but since is my girlfriend's phone i havent really played with it. Im really not up to date on the rezound rooting process. But here is my qestion is it safe to go s-off using JuopunutBear with my current state?
HBOOT 2.10
HTCdev Unlock
S-on
Amonra- recovery
running custom rom, not stock rooted
If someone can point me on the right direction I will really appreciated
http://forum.xda-developers.com/showthread.php?t=1612035
That is the s-off thread. Lots of help there.
If you get s-off, it will ask you if you want to upgrade your hboot, just select yes. Then you can flash ANY ROM you want!
It shouldn't wipe your external SD, but take it out just to be safe.
GrayTheWolf said:
http://forum.xda-developers.com/showthread.php?t=1612035
That is the s-off thread. Lots of help there.
If you get s-off, it will ask you if you want to upgrade your hboot, just select yes. Then you can flash ANY ROM you want!
It shouldn't wipe your external SD, but take it out just to be safe.
Click to expand...
Click to collapse
"Shouldn't" being the operative word there. I've done the S-OFF process on 3 Rezounds...the external SD was wiped on two of them.
shrike1978 said:
"Shouldn't" being the operative word there. I've done the S-OFF process on 3 Rezounds...the external SD was wiped on two of them.
Click to expand...
Click to collapse
Well aren't you special?
The latest shouldn't, but I said take it out because it does it sometimes, and other times it doesn't.
sorullo_xgrx said:
hello, everyone i had my rezound since back in December. im still S-on (yeah i know im trying to get s-off ). I had the phone for a long time but since is my girlfriend's phone i havent really played with it. Im really not up to date on the rezound rooting process. But here is my qestion is it safe to go s-off using JuopunutBear with my current state?
HBOOT 2.10
HTCdev Unlock
S-on
Amonra- recovery
running custom rom, not stock rooted
If someone can point me on the right direction I will really appreciated
Click to expand...
Click to collapse
Pm me I can help you with s-off or updating on s-on..
sent from my s-off reZound rockin' viperRez Rom on global ICS firmware
GrayTheWolf said:
http://forum.xda-developers.com/showthread.php?t=1612035
That is the s-off thread. Lots of help there.
If you get s-off, it will ask you if you want to upgrade your hboot, just select yes. Then you can flash ANY ROM you want!
It shouldn't wipe your external SD, but take it out just to be safe.
Click to expand...
Click to collapse
That was my only concern if I need to be on the latest hboot... It's being a while since the last time I flash a Rom on the rez. There's a lot to keep up
Sent from my ADR6400L using Tapatalk 2
famouscollin said:
Pm me I can help you with s-off or updating on s-on..
sent from my s-off reZound rockin' viperRez Rom on global ICS firmware
Click to expand...
Click to collapse
Thanks there is a lot going on here. On the thunderbolt we are barely starting picking up on new staff. I mean there is no hboot, or firmware , or bunch of new Rom on the thunderbolt ... Lol but still use it, like it and hate it sometimes
Sent from my ADR6400L using Tapatalk 2
GrayTheWolf said:
http://forum.xda-developers.com/showthread.php?t=1612035
That is the s-off thread. Lots of help there.
If you get s-off, it will ask you if you want to upgrade your hboot, just select yes. Then you can flash ANY ROM you want!
It shouldn't wipe your external SD, but take it out just to be safe.
Click to expand...
Click to collapse
It does wipe your SD card, it says so in the instructions/site. I just S-Off'd last night and I had to reformat my SD card to get it to work again, it even says so after controlbear is done running.
Sent from my Nexus 7 using Tapatalk 2
GrayTheWolf said:
Well aren't you special?
Click to expand...
Click to collapse
Why the snide remark? Wholly unnecessary stuff like this is why the Rezound forums have such a bad rep.
BBEgo said:
Why the snide remark? Wholly unnecessary stuff like this is why the Rezound forums have such a bad rep.
Click to expand...
Click to collapse
Hey, you came at me first.
I said to take it out anyway because it shouldn't, but sometimes it does. Just read the thread. Some people say it does, some don't. Take it out just to be safe.
You need a sdcard in the device to achieve S-off, if you don't have another sdcard just copy all of your stuff to your PC.
i have looked through the threads and i did not see anything about this question or anything close enough to it. I need to go back to sprint to get my phone fixed (the microphone doesn't always work. sometimes it does, sometimes it does not. i have found that it is not software related, but definitely a hardware issue.) but i do not want to get my account noted or anything. right now i am s-off (NOT htc dev unlocked), running TWRP recovery v 2.2.0, and running meanrom with a custom kernel that was installed with meanrom. i know i can run an RUU and return to stock, but i will still be s-off. i did install a custom bootloader (thanks to regaw_leinad) that makes it look like i am s-on and not tampered, but i do not know if sprint can still see if i am s-off. sorry if this is a noob question, but i have never dealt with s-off before.
http://forum.xda-developers.com/showthread.php?t=1744700
Look harder next time.... Just joking. This is what you want to read.
metalfan78 said:
http://forum.xda-developers.com/showthread.php?t=1744700
Look harder next time.... Just joking. This is what you want to read.
Click to expand...
Click to collapse
thank you! that was exactly what i was looking for! i guess i didn't look hard enough sorry.
but just to clarify, i cannot just leave my phone s-off? if i take it to sprint with s-off, but the custom bootloader that makes it look stock from regaw_leinad, will they still be able to find out that i am s-off?
I have never returned my phone to s-on in two years. I've never had a problem with the Sprint stores. It's your call though. If you do s-on it, tell them you don't want it updated. If it was me I would just have the stock rom on it and call it good
metalfan78 said:
I have never returned my phone to s-on in two years. I've never had a problem with the Sprint stores. It's your call though. If you do s-on it, tell them you don't want it updated. If it was me I would just have the stock rom on it and call it good
Click to expand...
Click to collapse
that is probably what i will do then. again, thank you!
You're welcome
ok, last question. if i run the latest ruu, will it update my hboot? i am still on 1.12 and i do not want a newer one. i downloaded the 1.13.651.1 ruu. is this fine? i am running meanrom v 4.0 if that info is needed.
I'm about to go 100% back to stock as well to try and resolve many of the problems i'm having, this thread has been particularly helpful, thanks
I think it does update your hboot, but I don't know for sure.
i have confirmed that it does indeed update your hboot.
if you have hboot 1.12, then use this ruu:
http://bit.ly/VPl2wn
it is the 1.13.651.1 ruu. it has hboot 1.12 in it.
tim.d said:
I'm about to go 100% back to stock as well to try and resolve many of the problems i'm having, this thread has been particularly helpful, thanks
Click to expand...
Click to collapse
i am glad to posted a helpful thread. but we can thank metalfan78 for supplying the information that helped us
sorry to post a third time, but i ran the ruu that i previously posted a link to and went to the sprint store (i also had to re-flash the custom bootloader from the regaw_leinad tool). they had no clue i was s-off or i had done anything to my phone. but there is one problem. if they had tried to update it and it updated the bootloader as well, it would have removed the custom one and put HTCs back on it. that wouldnt be a problem as you would still be s-off, but instead of looking stock(s-on, locked), it would now say s-off in the bootloader. so if you want to be sure that the sprint employees will not be able to tell you modded your phone, you do have to return to s-on. chances are that they wont try to update it, but its better to be safe than sorry!
Yea, true. I'm glad everything worked out.