Related
I am going to risk being told that I am an idiot here but I have to ask. I have had my 3D for almost a year now and I just can't take not rooting it yet! It is HBoot 1.5 and this the first smart phone I have ever had (the last 8) that I have not been flashing ROMs on. I just gave up that it will be possible but I have seen a bunch of forums on being able to do this.
My questions lie on the fact that I have a Mac and PC but no Linux system. I see the bootable CD options but not sure what is best. Either way it seems like a lot of work for a ROM but I just need to get a ROM on this damn phone! Is there any good videos? Where the hell do I even truly start. Way to many different options. I feel like a NOOB again even though I have flashed hundreds of ROMS and even cooked some back in my WinMob days!
Thanks guys for the help.
This is the General section. Refer to the Questions and Answers section. Just because you weren't rooting doesn't mean you can't post in the correct section.
Sent from my PG86100 using XDA
Evo3d HBoot/S-off Differences/Rooting Background Info 8-5-12
Edit: I will no longer be maintaining this post. Instead I have started a full thread to help track the changes:
http://forum.xda-developers.com/showthread.php?p=29844067#post29844067
I've had the Evo3D for a few months now and must say I really have come to like it.
If you want root, it's a bit quirky, You basically have 3 options:
(See the Hboot 1.50 HTC Unlock Guide in my signature for info & links)
1) HTCdev.com's "Bootloader Unlock":
Basically this leaves the bootloader's (Hboot 1.50) security flag on (S-On) but "unlocks the bootloader" (kinda like the phones Bios) so that you can manually flash everything except for Radios (Baseband) and Boot Logo's (Splash Screen). Kernels & roms can be flashed once a custom recovery is installed, but there are "extra" steps involved because the /boot partition (kernel/zImage) can only be set to write access from the Android OS or by initiating custom recovery from a pc's "Fastboot Command Prompt". There are workarounds, some work better than others. To flash Radio updates, you have to relock the bootloader and flash an OEM Full Stock Ruu (Rom Update Utility), kinda like Samsung's Sw Updater for the Transform. You also have to register your device with HTC and it "may void your warranty".
2) Downgrade Bootloader from Hboot 1.50 to 1.40 (to get S-Off):
This is a recent development by Unknownforce in the last few weeks. Basically involves corrupting the flashing process of the RUU by removing power in the middle of the flash and "bricking it" (more like mostly bricked). It forces the phone into a special eMMC Download mode that can only be fixed by pushing the older bootloader to the phone from a Linux pc. Good thing is that Closeone has a Linux LiveCD.iso that you copy to a USB Drive or CD and temporarily boot to a custom Linux Interface specifically set up for flashing the bootloader.
Once that's done, you rerun an earlier RUU (compatible with Hboot 1.40) to get the phone working fully, then root via "Revolutionary's site" (another fastboot/adb rooting tool) to get S-Off (Full root), load a recovery, update the radio, then you can flash roms & kernels like normal.
My current setup (keep coming back to MeanRom):
Hboot 1.40.1100 (Downgraded)
Firmware: 2.17.651.5 (Base)
Radio: 1.06.00.1216 (from 2.17 base)
Recovery: 4ext Recovery (Fully Compatible with CWM, which was a bit buggy except for v4.0.1.4)
Rom: MeanRom ICS
kernel: atx 1.9.1
Mods: LeeDroid Tweaks CDMA, ADW_Ex Launcher, Several Apps removed with SDX Stock App Remover (posted in SDX Evo3D General section).
3) Edit: Juopunutbear's S-OFF Wire Trick:
There is a similar third option now to brick (short out pins with a wire) & replace the bootloader on 1.50 with s-off but I haven't tried it. (Must HTC Unlock first & have a rooted "Stockish" rom installed)
dmdelgado said:
I wanted to share with everyone else suffering from HBoot 1.5 that if you have been using Chads ICS Firmware fix because of constant bootloops you dont need to downgrade your HBoot to 1.4. I know every time i would flash the firmware fix it would break many bugs that had already been fixed, I had to flash it to avoid getting constant boot-loops. But Juopunutbear's Wire trick to get S-Off was a miracle fix, and after it turns S-Off it asks if you would like to install a custom Juopunutbear Hboot. After this is done you are officially on HBoot 1.5 S-Off! And can flash any ICSense ROMS successfully without having bootloops! I really hope this helps someone enjoy their ROMs that much MORE because i know it feels good TO FINALLY BE FREED FROM THE CURSE OF S-ON!
Click to expand...
Click to collapse
-----------------------------------------------------------------------------------------
HBoot S-Off Background Info:
mpgrimm2 said:
To be honest I have not considered anything about the bootloader since downgrading and getting s-Off. I will point out that us "downgraders" don't have hboot 1.40 but "Revolutionary Hboot 1.40.1100".
My understanding is that it has more functions than stock hboot 1.40/1.50 but less functions than the Engineering Hboot. Kinda like your Jbear Hboot 1.50.5050, but I could be wrong. I'm sure one of the devs like Mike, Chad, Joeykrim, xhausx, freeza, Unknownforce, Closeone, etc would know.
Hboots:____________________Differences:
1.04.xxxx ? (Eng Hboot) = Extended functions .... Appear to be incompatible with newer 2.89 based kernels
1.30 (Stock Hboot with 1.07.651.1 Gb) .......... Appear to be incompatible with newer 2.89 based kernels
1.40 (Stock Hboot with 1.13.651.7 Gb) ......... Appear to be incompatible with newer 2.89 based kernels
1.40.1100 (incl. w/Revolutionary S-Off) ................. Appear to be incompatible with newer 2.89 based kernels
1.50 (Stock Hboot with 2.17.651.5 Gb) ........ 2.89 based kernels status unknown
1.50.5050 (incl. w/Jbear for GB S-Off) .................. May be compatible with newer 2.89 based kernels & prior fw/kernels (some reports)
1.57.5757 (incl. w/Jbear for ICS S-Off) ................. May be compatible with newer 2.89 based kernels & prior fw/kernels (some reports)
1.58 (Stock Hboot with 2.89.651.2 ICS) ............. Compatible with newer 2.89 based kernels (& Vm ICS Leak), not GB based (some reports)
...............................................................................edit: Some boot issues with AOSP/AOKP roms & kernels reported (ie CM9)
Click to expand...
Click to collapse
Unknownforce said:
First, keep in mind, that there are technically two S-OFF's, the hboot and the radio. This is somewhat misleading. When you're phone displays S-OFF on the hboot screen, this is actually the Radio S-OFF, not hboot S-OFF. Gaining hboot S-OFF is actually just as simple as flashing a new modified hboot. (which is why there are revo hboot and now jbear hboot, they have been modified to now have hboot S-OFF)
hboot S-OFF is almost the same as unlocking your bootloader via HTC's method. Just that HTC's method doesn't get you S-OFF and is more limited than revo/jbear S-OFF.
So a few of the the differences here are:
1.) ENG Hboot is S-OFF and offers more fastboot commands and a few more unlocked features. This is an advanced hboot that you can do serious damage to the partitions in your phone if you don't know what you're doing. It's kind of like an all access pass.
2.) The stock hboots are S-ON, they don't allow very many of the fastboot commands. These are limited to very basic fastboot commands.
3.) revo/jbear are S-OFF, they allow for many of the "standard" fastboot commands, like flashing to partitions and whatnot, but not nearly as "feature packed" as the eng hboot, these are typically enough for normal users.
As to it providing any benefit to using a newer version of hboot, the only one that provides more features is the eng hboot for more fastboot access. What this means is that there's no major feature/performance difference between 1.30 and 1.57 aside from some appearance and some security adjustments (to allow HTC Unlock and also attempt to counter the S-OFF/exploits)
As I understand it, the differences between radio S-OFF and hboot S-OFF are basically as follows:
Radio S-OFF has signature verification off, what this means is that you can flash any PG86IMG.zip and it doesn't have to be signed by HTC. This will allow it to flash just about anything from there. This is why you can revert to a lower hboot without having to do anything special when you accidentally (or purposefully) flash a new hboot over your revo or any other hboot. Radio S-OFF also doesn't check the signature of most of the current partitions (so you don't get "security warning")
hboot S-OFF allows many more of the fastboot commands to be accepted and opens up the ability to flash some of the restricted partitions from it as well.
Hope this helps clear up some confusion.
Click to expand...
Click to collapse
fergdogg23 said:
I am going to risk being told that I am an idiot here but I have to ask. I have had my 3D for almost a year now and I just can't take not rooting it yet! It is HBoot 1.5 and this the first smart phone I have ever had (the last 8) that I have not been flashing ROMs on. I just gave up that it will be possible but I have seen a bunch of forums on being able to do this.
My questions lie on the fact that I have a Mac and PC but no Linux system. I see the bootable CD options but not sure what is best. Either way it seems like a lot of work for a ROM but I just need to get a ROM on this damn phone! Is there any good videos? Where the hell do I even truly start. Way to many different options. I feel like a NOOB again even though I have flashed hundreds of ROMS and even cooked some back in my WinMob days!
Thanks guys for the help.
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/showthread.php?t=1585846
mnomaanw said:
Try this http://forum.xda-developers.com/showthread.php?t=1585846
Click to expand...
Click to collapse
I wouldnt try this.
I would first try to downgrade hboot or just unlock your hboot 1.50 and use 4ext to flash roms and flash GUI to flash kernels..
I ended up bricking my evo by using the Juopunutbear S-OFF wire trick.
fergdogg23 said:
I am going to risk being told that I am an idiot here but I have to ask. I have had my 3D for almost a year now and I just can't take not rooting it yet! It is HBoot 1.5 and this the first smart phone I have ever had (the last 8) that I have not been flashing ROMs on. I just gave up that it will be possible but I have seen a bunch of forums on being able to do this.
My questions lie on the fact that I have a Mac and PC but no Linux system. I see the bootable CD options but not sure what is best. Either way it seems like a lot of work for a ROM but I just need to get a ROM on this damn phone! Is there any good videos? Where the hell do I even truly start. Way to many different options. I feel like a NOOB again even though I have flashed hundreds of ROMS and even cooked some back in my WinMob days!
Thanks guys for the help.
Click to expand...
Click to collapse
I know exactly how you feel. I used to flash my HTC Wing all the time with Windows Mobile. Even tried my hand at cooking some roms. Coming over to Android many years later -- yeah makes you feel like a noob again.
Its not that hard really. You are already familiar with what is involved with flashing. All you have to do is take it one step at a time. Just like you did years ago with Windows Mobile. Lots of tutorials walk you right through it. After you do it, you'll look back and see how easy it really was.
You'll need to unlock your bootloader and root the phone. Once you've done that you can flash almost any rom on here. I would not go S-Off just yet. I have read that downgrading your H-Boot slows the phone way down. There really is no good way to do it with 1.5 yet. There may not ever be as Sprint stopped selling the Evo 3D and lots of people are moving on to other phones.
The night I did mine, I started at 7:00 pm and finally figured it all out and got it done it was 4:30 am.
Just have to do alot of reading. No way around that.
How does soff slow the phone?
Sent from my SPH-D710 using Tapatalk 2
patrao_n said:
How does soff slow the phone?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Just read on here, its not S-Off that slows down the phone, its the downgrade of H-Boot.
Here is the link to what I read:
http://forum.xda-developers.com/showthread.php?t=1661709
Here is what the guy says:
frexe said:
I recently downgraded to 1.4 hboot with revolutionary s off. I then updated with Freezas AIO. And running meanrom ics 1.0 now.
The problem is that my 3g speed is at slug speeds. Ping is up at 900ish download and upload is below 100.
Before I was on hboot 1.5 2.17.651.5_Radio_1.06.00.1216 and had decent speeds.
Just wondering if someone can shed some light to this problem. Or maybe I have to go back to 1.5hboot and live without a true root.
My Phone is flashed to boost.
Click to expand...
Click to collapse
iTzLOLtrain said:
I wouldnt try this.
I would first try to downgrade hboot or just unlock your hboot 1.50 and use 4ext to flash roms and flash GUI to flash kernels..
I ended up bricking my evo by using the Juopunutbear S-OFF wire trick.
Click to expand...
Click to collapse
This^
Unlock and try 4ext first it will allow you to flash roms and kernels without the need to downgrade. I downgraded to hboot 1.4 because I was getting boot loops but I read that a lot of unlocked hboot 1.5 S-On people are fine so try first before going through what can be a tricky and somewhat risky process to get S-Off.
I have experienced no slowdown from downgrading and I can't see how that would have an effect but I'll let someone more knowledgeable chime in if that is a factor or not.
I haven't seen any speed slow downs with Hboot 1.50 downgraded to 1.40 either. I have seen slow downs when sprint was working on tower upgrades that went away after a week or two (drove me nuts). I would point out that the person that reported downgrade "related" slow downs had flashed the phone to Boost mobile, so there's another factor to consider. Edit: Reading thru the rest of that thread proves it wasn't related to Hboot/S-off.
I'm a bit leary on the Juno method, but I've seen references to people shorting out the pin before in lieu of a Jtag setup, so it's pretty much as sound/risky as Unknownforce's Downgrade method. Although, the hboot downgrade has a huge number of successful attempts and the handful of permabricks where because someone got in a hurry and skipped a step/didn't pay attention to what they were doing.
mpgrimm2 said:
I'm a bit leary on the Juno method, but I've seen references to people shorting out the pin before in lieu of a Jtag setup, so it's pretty much as sound/risky as Unknownforce's Downgrade method. Although, the hboot downgrade has a huge number of successful attempts and the handful of permabricks where because someone got in a hurry and skipped a step/didn't pay attention to what they were doing.
Click to expand...
Click to collapse
Agreed.
I'll admit that the JuopunutBear (wire trick) method may look a little more risky than the HBoot 1.4 downgrade process, but I've done two Evo 3D's using a paperclip wrapped in scotch tape (not the preferred equipment) and haven't had a problem with either phone. Several of the "bricked" users have reported a USB status in Windows of "QHSUSB_DLOAD" in the HTC Unbricking Project thread and I added this post from the HTC Amaze forum to the thread which claims that status is not a real brick (if it was there wouldn't be any indication the phone was even connected in Windows) and it can be recovered using the ControlBear utility. I got no feedback from the people that were reporting that status, and the OP also indicated that the phones were probably not hard bricked.
I haven't seen any feedback from anyone with a "bricked" phone about contacting the developers via the IRC channel they advertise on their website (#juopunutbear on freenode) or PM'ing them as I suggested in the jb thread. I have only been able to identify a few users that claim to have bricked their phones via the jb method, but they seem to be posting about their negative experience with that process in many different threads.
I don't really care which method people choose to get to S-Off as they all have risks involved and it's up to each person to determine what level of risk they are willing to take. The JuopunutBear method was a lot simpler for me and I'm not convinced the risk is that high if you use the right type of wire (insulated copper wire is recommended) and follow the instructions as documented (which a lot of people don't), but that method is fairly new and I wouldn't blame people that are HBoot 1.5 S-On for waiting a little while longer to see how many more users claim to have bricked their phones with that method.
Most people can get by with HBoot 1.5 S-On using tools like 4EXT SmartFlash and Flash Image GUI, but for those that have problems with the stock ICS kernel or want to get to S-Off for other reasons, at least there are alternatives now.
ramjet73
just stay with 1.5 s-on
ive been on 1.5 for awhile with s on and it hasnt been that big of a deal. My old evo was soff and there were some nice rom switching with cwm but I uaes to use cwm to flash roms on my evo and it worked like a charm but it does not let you flash the kernal, I was having to flash kernal seperatly with flash gui which is a free download but 4xt works fine and dont have to flash kernal seperatly but eitherway is fine as I usually use specific kernals anyway. I found a routin that I am happy with and wont switch until I brick my phone or get a new one lol.
Good luck
So, coming from a Thunderbolt...rooting and getting s-off on a rezound seems like rocket science in comparison. I've read and read for the past four weeks but I'm asking for your guys' help and clarification before I proceed.
Here is what has happened so far: My buddies Rezound is currently HTC dev unlocked with a custom ICS rom on it with S-on. I want to get him s-off so flashing roms and kernels will be a piece of cake without adding a bunch more steps. I figured out how to do it and understand the process myself pretty clearly but trying to explain it to my buddy...yeah, I might as well be trying to teach him another language.
Now, I assume he is on Gingerbread firmware since I haven't flashed the leaked ICS RUU(have to install gingerbread firmware patch on his ICS roms). This already is getting complex to me. On my good old thunderbolt I just had to use revolutionary to get s-off then it was flash whatever I wanted, gingerbread or froyo and flash compatible radios.
Here's what I want to do. I figure I should get him off of gingerbread firmware since the phone will eventually be getting ICS via OTA. To do this, I believe I have to re-lock the phone and then flash the ICS ruu. After that I can proceed to get s-off using the wire trick.
My questions are these: do I have to flash a stock rom before I re-lock the phone and flash the ICS ruu, or can I just leave his current rom on there(rezrom)?
And finally, what ICS version am I supposed to flash in order to get s-off? I see conflicting reports of this will work, any one will work, or only a certain one will work with the s-off method. Could one of you be kind enough to send me a link to download said RUU? I tried downloading one but it would check it in HBOOT and after the 5 minutes it took to check it, it didn't give me the option of running it...just went to the main hboot menu(fastboot, recovery, reboot, etc.). I don't know if it's because I was UNLOCKED (i realize you can't flash ruu while unlocked), or if the file was bad.
Sorry for the long wordy post but I felt like I should be thorough. Thanks in advance.
antiseen said:
So, coming from a Thunderbolt...rooting and getting s-off on a rezound seems like rocket science in comparison. I've read and read for the past four weeks but I'm asking for your guys' help and clarification before I proceed.
Here is what has happened so far: My buddies Rezound is currently HTC dev unlocked with a custom ICS rom on it with S-on. I want to get him s-off so flashing roms and kernels will be a piece of cake without adding a bunch more steps. I figured out how to do it and understand the process myself pretty clearly but trying to explain it to my buddy...yeah, I might as well be trying to teach him another language.
Now, I assume he is on Gingerbread firmware since I haven't flashed the leaked ICS RUU(have to install gingerbread firmware patch on his ICS roms). This already is getting complex to me. On my good old thunderbolt I just had to use revolutionary to get s-off then it was flash whatever I wanted, gingerbread or froyo and flash compatible radios.
Here's what I want to do. I figure I should get him off of gingerbread firmware since the phone will eventually be getting ICS via OTA. To do this, I believe I have to re-lock the phone and then flash the ICS ruu. After that I can proceed to get s-off using the wire trick.
My questions are these: do I have to flash a stock rom before I re-lock the phone and flash the ICS ruu, or can I just leave his current rom on there(rezrom)?
And finally, what ICS version am I supposed to flash in order to get s-off? I see conflicting reports of this will work, any one will work, or only a certain one will work with the s-off method. Could one of you be kind enough to send me a link to download said RUU? I tried downloading one but it would check it in HBOOT and after the 5 minutes it took to check it, it didn't give me the option of running it...just went to the main hboot menu(fastboot, recovery, reboot, etc.). I don't know if it's because I was UNLOCKED (i realize you can't flash ruu while unlocked), or if the file was bad.
Sorry for the long wordy post but I felt like I should be thorough. Thanks in advance.
Click to expand...
Click to collapse
Just s-off on GB. You can do it on ICS or GB works the same way. Just if you RUU to ICS you will have to reunlock to soff.
Once s-off he can flash any ruu he wants in any order and keep s-off.
Also on a secondary note, you must have not had a thunderbolt when we first got s-off as getting s-off manually took about 30+ mins of constant cmd line use.
S-off on the rezound is much easier than it sounds. The only part that gives people trouble is the wire trick and mainly because it is all about timing.
Sent from my ADR6425LVW using XDA
I will say this outright: you can S-off right now using the GB package option on unlimited.io since that is the firmware you have. Answering the rest of this assuming an upgrade to ICS firmware, but that is the simplest path.
antiseen said:
Now, I assume he is on Gingerbread firmware since I haven't flashed the leaked ICS RUU(have to install gingerbread firmware patch on his ICS roms).
Click to expand...
Click to collapse
Correct. If you're patching the firmware is still Gingerbread. Check in the bootloader for "hboot 2.11" to confirm this. Only way you can update firmware and radios while S-on is to run a RUU.
antiseen said:
Here's what I want to do. I figure I should get him off of gingerbread firmware since the phone will eventually be getting ICS via OTA. To do this, I believe I have to re-lock the phone and then flash the ICS ruu. After that I can proceed to get s-off using the wire trick.
Click to expand...
Click to collapse
When a phone gets an OTA update, it is expecting you to be on the latest official release. That currently is the 2.01.605.11 Gingerbread build, the first OTA we had. That means you need to be on the GB firmware, and stock everything else, not on ICS firmware.
That said, last part is correct: You would re-lock, flash an ICS RUU, unlock again, put recovery back on, and either flash a pre rooted stock ROM based on the leaks, or root the stock ROM yourself. Then you are on ICS firmware, ready for S-off.
antiseen said:
My questions are these: do I have to flash a stock rom before I re-lock the phone and flash the ICS ruu, or can I just leave his current rom on there(rezrom)?
Click to expand...
Click to collapse
Leave the ROM. Do a nandroid backup. Re-lock and flash the RUU. You can restore the nandroid afterwards, just be sure to repatch the thing to new ICS firmware if you go that route. Check second listing in the Roll Up Sticky post in the Dev section.
antiseen said:
And finally, what ICS version am I supposed to flash in order to get s-off? I see conflicting reports of this will work, any one will work, or only a certain one will work with the s-off method. Could one of you be kind enough to send me a link to download said RUU? I tried downloading one but it would check it in HBOOT and after the 5 minutes it took to check it, it didn't give me the option of running it...just went to the main hboot menu(fastboot, recovery, reboot, etc.). I don't know if it's because I was UNLOCKED (i realize you can't flash ruu while unlocked), or if the file was bad.
Sorry for the long wordy post but I felt like I should be thorough. Thanks in advance.
Click to expand...
Click to collapse
Unlimited.io has files for GB firmware and the first three out of four ICS leaks. Note this last leak, the fourth one, is compatible with the unlimited.io files for the third leak ("5/7 leak"). So little was changed, so you're safe going with that combo if you wish.
nosympathy said:
Also on a secondary note, you must have not had a thunderbolt when we first got s-off as getting s-off manually took about 30+ mins of constant cmd line use.
Click to expand...
Click to collapse
You're actually right. I didn't get my TB til June and I spent months reading how to get s-off and finally did it in...august or september, I forget. It was MUCH easier by then.
I was familiar with the original process(only by reading, but felt confident in doing it that way) but by the time I was done learning everything about it, revolutionary method came out and I did it that way.
I know that I can get s-off right now on his gingerbread firmware, my only question is what happens when ICS does get released and all the good ROMS start to come out? I want to get him on an AOSP rom when they come out. I feel like he'll be stuck on gingerbread firmware and when it comes time to flash any of the ICS roms, he'll be clueless. I could figure out how to do it if it required an extra step or two but explaining that to him might be a bit much. I'd rather him be geared for ICS (he has no intention of going back to gingerbread, ever).
Also, I was under the impression that flashing a RUU would make it S-on. So if I ever wanted to upgrade his firmware to ICS we would have to do the wire trick again to achieve s-off once more.
Anyway, Thanks a ton guys for your feedback already. Love this community and you're both a great help. Thanks for the clarification/instructions phantasm.
antiseen said:
I feel like he'll be stuck on gingerbread firmware and when it comes time to flash any of the ICS roms, he'll be clueless. I could figure out how to do it if it required an extra step or two but explaining that to him might be a bit much. I'd rather him be geared for ICS (he has no intention of going back to gingerbread, ever).
Click to expand...
Click to collapse
Hop through S-off with the GB files from unlimited.io. Keep the stock bootloader for now rather than flashing the JuopunutBear hboot when their program asks you. (Note S-off makes the bootloader "Locked" again, but the JB files are hacked so you can use them *as if* they are Unlocked status... handy and makes it simpler to get the phone ready for warranty exchanges again. But! We want to make sure we get ICS firmware and radios first...then slap on an *ICS* JB bootloader...)
antiseen said:
Also, I was under the impression that flashing a RUU would make it S-on. So if I ever wanted to upgrade his firmware to ICS we would have to do the wire trick again to achieve s-off once more.
Click to expand...
Click to collapse
Nope. Once you achieve S-off you keep S-off. The only thing that affects S-off is turning the flag back on manually yourself with some fastboot commands.
So now you will be S-off and with a Locked stock bootloader. Download the RUU from the 6/10 leak here, rename to just PH98IMG.zip and flash it in bootloader:
http://www.androidfilehost.com/main/-Support_Files-/RUU/Vigor/RUU_Vigor_3.14.605.10_PH98IMG.zip
Then grab "[ICS][2.25][JB][5-7]PH98IMG.zip" from SuperChilPil's repository. (Note the 6/10 leak and the 5/7 leak have the same bootloaders just like the first pair of leaks did, so this is fine to use.) Rename to PH98IMG.zip and flash in bootloader:
http://www.androidfilehost.com/main/-Support_Files-/SuperChilPil/
This will make you S-off with a JuopunutBear hacked hboot, running the latest firmware and ROM available. Choose a recovery to flash, preferably TWRP or AmonRa. ClockworkMod has charging issues, there is a fix floating around thanks to NilsP and his own source if you insist. You can then proceed to flash the ICS custom ROM of your choice.
TWRP:
http://forum.xda-developers.com/showthread.php?t=1613576
AmonRa:
http://forum.xda-developers.com/showthread.php?t=1339679
CWM (fixed):
http://forum.xda-developers.com/showthread.php?t=1722989
Edit: User zhp pilot claims this version of CWM is also not functioning properly at this time, see the thread. Proceed with caution on CWM.
And don't forget to make a splash screen now that you are S-off lol, stop blinding yourself with that white HTC screen:
http://forum.xda-developers.com/showthread.php?t=1615811
~~~
Other useful files for S-off if you don't have them on the PC... The latest HTC drivers (extracted from HTC Sync so you don't have to download all of that) and an adb/fastboot mini console:
https://rapidshare.com/files/1796700693/HTCDriver_3.0.0.021.exe
http://rapidlibrary.com/files/adb-fastboot-and-other-tools-zip_ulcmnmxxtci89on.html
antiseen said:
Anyway, Thanks a ton guys for your feedback already. Love this community and you're both a great help. Thanks for the clarification/instructions phantasm.
Click to expand...
Click to collapse
Nope, thanks you for asking.
antiseen said:
So, coming from a Thunderbolt...rooting and getting s-off on a rezound seems like rocket science in comparison. I've read and read for the past four weeks but I'm asking for your guys' help and clarification before I proceed.
Here is what has happened so far: My buddies Rezound is currently HTC dev unlocked with a custom ICS rom on it with S-on. I want to get him s-off so flashing roms and kernels will be a piece of cake without adding a bunch more steps. I figured out how to do it and understand the process myself pretty clearly but trying to explain it to my buddy...yeah, I might as well be trying to teach him another language.
Now, I assume he is on Gingerbread firmware since I haven't flashed the leaked ICS RUU(have to install gingerbread firmware patch on his ICS roms). This already is getting complex to me. On my good old thunderbolt I just had to use revolutionary to get s-off then it was flash whatever I wanted, gingerbread or froyo and flash compatible radios.
Here's what I want to do. I figure I should get him off of gingerbread firmware since the phone will eventually be getting ICS via OTA. To do this, I believe I have to re-lock the phone and then flash the ICS ruu. After that I can proceed to get s-off using the wire trick.
My questions are these: do I have to flash a stock rom before I re-lock the phone and flash the ICS ruu, or can I just leave his current rom on there(rezrom)?
And finally, what ICS version am I supposed to flash in order to get s-off? I see conflicting reports of this will work, any one will work, or only a certain one will work with the s-off method. Could one of you be kind enough to send me a link to download said RUU? I tried downloading one but it would check it in HBOOT and after the 5 minutes it took to check it, it didn't give me the option of running it...just went to the main hboot menu(fastboot, recovery, reboot, etc.). I don't know if it's because I was UNLOCKED (i realize you can't flash ruu while unlocked), or if the file was bad.
Sorry for the long wordy post but I felt like I should be thorough. Thanks in advance.
Click to expand...
Click to collapse
In order to S-off the Rezound, you need to be HTCDEVunlocked, Rooted and on Stock Rom.
So I have Scott's CleanROM GBE 1.7.5 on my phone. I was wandering through my phone's settings, and accidentally hit something in the update area. I do not know what I was thinking, but I know I expected it to ask me if I was sure I wanted to update. So far it has only done the first part where it prepares the phone for the update. I do not know when the other part is coming but I assume it is automatic. I was planning on updating to a rooted ICS once I felt comfortable with it (just seemed a little harder than my original flash of rooted GB). So if it would be easier to just update to ICS some way now, I would be very willing to do that. I am s-on, I believe I installed Amon Ra, but I am not sure how to check and not sure if I have an actual recovery rom or not.
I checked around and found similar problems, but nothing really like mine since my update has not gone all the way thru yet. If anyone could help, it would be greatly appreciated. THank you.
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Ok just to make sure I know and don't mess anything else up. I relock (should be easy to.find a guide) . Then run the update on my phone? Then unlock thru HTC again, and flash the actual amon or CWM to my phone? And from there I will be able to flash any ICS Rom with more ease?
And thank you for the quick reply.
Edit: I searched the internet more for less-similar situations. I think all I have to do is re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Also,nothing I have to do as far as unrooting?
malignancyy said:
Also,nothing I have to do as far as unrooting?
Click to expand...
Click to collapse
Nope just relock the bootloader
AshtonTS said:
Nope just relock the bootloader
Click to expand...
Click to collapse
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
malignancyy said:
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Click to expand...
Click to collapse
Then you just have to press continue when it tells you to.
PS: Another way to get to the bootloader is to use adb (make sure USB debugging is enabled on your phone)
Command:
adb reboot bootloader
I find it easier than holding down buttons for a long time, but that's just my personal preference.
(Also, most custom ROMs can reboot to bootloader from within the ROM. I forget if CleanROM GBE includes the advanced power menu.)
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Good advise, and if he RUUs to ICS, then he should not even get asked to install the update because it will already be installed on his phone.
Also RUU twice. Just reboot into bootloader right away and install the RUU a second time. Then boot up normally and remove the zip file from the sdcard.
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
malignancyy said:
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
Click to expand...
Click to collapse
The jbear hboot might have failed because you are on the newest global update with 2.27 hboot, and I believe the controlbear tool still has the 2.25 hboot. (someone correct me if I'm wrong)
I think there is an unguarded 2.27 hboot somewhere, so you should flash that manually.
Sent from my NeoMax Rezound
Right now, like I said the hboot says at the top 2.27.0000
When I reboot from there, or boot it regularly it goes to a JuopunutBear, black and green writing screen.
I have tried to install this forum.xda-developers.com/showthread.php?t=1843030 ([HBOOT] HBoot 2.27 (from 4.03.605 OTA) Unlocked) from both, but cannot figure out how to do so.
edit: within JuopunutBear, wiping says "can't open" and applying update gives "failed to open loopdevice" and "failed to mount /sdcard" when I try to update.
Within the regular hboot, I get "no image" as it searches for files.
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
A little more info on this. Windows tries installing QHUSB_DLOAD driver for it when plugged in, but unsuccessfully. The charging indicator does not come on either. Have tried to turn it on plugged in with battery out, and battery in both ways.
malignancyy said:
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
Click to expand...
Click to collapse
Depending on what caused the brick, it may be recoverable.
Check out the unbricking thread in the dev section.
Sent from my NeoMax Rezound
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
malignancyy said:
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
Click to expand...
Click to collapse
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
wlmeng11 said:
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
Click to expand...
Click to collapse
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
malignancyy said:
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
Click to expand...
Click to collapse
That QA is outdated.
It was referring to using the 3.14.605.07 kernel as opposed to the then-most-recent 3.14.605.10
Back then those two builds were similar enough that they could mix n match without issues.
Between 3.14.605.12 and 4.03.605.1 is a lot of changes. (whole number change to represent it) Specifically, new hboot and radios. Therefore, it is incompatible with the older kernels.
When you're S-ON you can't touch the radios except through an official RUU.
Even with s-off I doubt you can flash radios from recovery (not sure on this one), and NeoMax doesn't have any radio files anyway. (nor does any rom I know for this phone)
If you haven't yet updated to 4.03.605.1 then I recommend that you stay on 3.14.605.12 until Neo updates the ROM.
If you already updated, it is still possible to run NeoMax. You just have to manually flash the new 4.03.605.1 kernel after installing the ROM.
Sent from my NeoMax Rezound
First, a big big thanks to Virus!! My phone info:
Sprint EVO3D CDMA
SHOOTER XC SHIP S-OFF RL
HBOOT-1.40.0000
RADIO-1.06.00.1216
eMMC-boot
Jun 8 2011, 17:20:22
TWRP v1.1.1
I previously flashed Freeza's v2.17.651.5 firmware and then the Stock ROM + root Shooter_S_Sprint_WWE_2.17.651.5_odex.zip which I'm currently running.
I've read this entire post OTA_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2-2.17.651.5 along with mpgrimm2's post Evo3d(CDMA)HBoot/S-off Differences & Rooting Background Info 8-20-12 and just want to ask before I "leap"! My steps as far as I see it:
1. Run my backups (Titanium, etc) and create a TWRP nandroid.
2. Flash the Stock 2.89.651.2-2.17.651.5 firmware
3. Install the superwipe zip (presumably install zip via TWRP recovery?)
4. Flash the Stock Rooted 2.89.651.2-2.17.651.5 ROM
5. If necessary, flash the BT fix.
At this point I should be up and running the DEODEX'd version of the Stock ICS ROM as if I'd done the ICS OTA. Question here is whether I'll hit compatibility problems with any apps I have installed? I know hard to say w/o knowing what all I've got installed, but if problems I figure just uninstall the app and find something compatible... Any other problems I could expect or should look for?
If for some reason I wanted to go back to my current GB ROM nandroid before the ICS update, I can just reflash hboot 1.40 and restore the nandroid made in my step 1? Do I need to worry about reflashing any other 2.17 firmware? It sounds like I can just restore my nandroid on hboot 1.58 but thinking I'd rather be back at hboot 1.40.
I too have run into the "remote: not allowed" error when using fastboot to flash images. From mpgrimm2's post, it's looks to be because my radio is s-off while my stock hboot 1.40 is technically not s-off? To have a fully functional fastboot via pc, I'd need to flash JBear hboot 1.40 (for GB) or JBear hboot 1.58.5858 (for ICS) from Ramjet's Pick your bootloader!, right? Seeing that I'm ok with flashing by booting into recovery, is there any other advantages (or disadvantages) to using the JBear hboots?
Sorry for the long post, but wanted to be complete... All help is greatly appreciated!
It looks like you have it right. To clarify one point, you don't need to downgrade firmware to run GB (I don't think that's even possible). Just the hboot.
Read, Search, Read again, ... Then Ask with Tapatalk 2
coal686 said:
It looks like you have it right. To clarify one point, you don't need to downgrade firmware to run GB (I don't think that's even possible). Just the hboot.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Click to expand...
Click to collapse
Thanks for the confirmation on my steps and being able to revert if I want to...I figured I would want to keep some of the updated firmware but wasn't sure what all could/should keep.
Although like the idea of being able to use fastboot fully, thinking best to just stick with the stock hboot for now...
Again thanks and if anyone has any other thoughts, they're always welcome!
I delayed doing the ICS update using the steps above, have read through the new pages/posts on the http://forum.xda-developers.com/showthread.php?t=1808150 post, and now have a few last questions before I jump in! Sorry if seem obvious, but have done the reading but now a bit confused or need clarification. I could just do it and recover if necessary, but rather ask up front.
If reading right, doing the Superwipe in step 2 will format both my phone and sdcard, cleaning out and recreating the partitions. Does this mean I'll have to use my TB Pro backups to restore all my personal apps & data? And if so, will I encounter any issues restoring such thing as my call log (or just restore the data and I'll be ok)? Reading up on Superwipe gets me thinking it deletes everything when I thought flashing this would be like an OTA update and keep my current apps, etc. Sorry again it's been awhile since flashing the stock 2.18.651.5 rooted ROM and just not remembering!
Also part way through the threads, there's mention of needing to first flash a ROM that will boot on 1.58 hboot or will get boot looping. I figure if my 2.18.651.5 GB rooted ROM won't boot after step 1, I'd just have to remove the firmware P86IMG file from the sdcard to proceed to step 2. The OP doesn't mention this - or is this a different situation than mine?
Lastly, on P.59, mpgrimm2 recommends flashing the full stock RUU to clean out all bits & pieces that might be left (I'm figuring it's the RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe) and reinstalling a custom recovery to have the stock rooted ICS. Is this a special case for one person or an alternative to the 3 step method? And it would mean I'd be reinstalling all apps and restoring all my data afterwards, right? Should I even consider this route if the three steps do an upgrade and keep my apps/data?
Thanks and sorry again for so many questions - just getting a headache keeping all straight and sorting through what's special case scenarios...oh and one last, is this Sense 3.5 or 3.6 - the OTA on HTC's site is listed as 3.6, right?
That's correct sir. It is 3.6
I created a similar thread the other day but it got so overwhelming and it was just confusing me more so I deleted it. I'm starting a fresh one so I can maybe explain myself better, not confuse anyone else and get better answers.
I just got a replacement Rezound in the mail today. My phone is currently on 4.05.605.14 710RD, LOCKED, HBOOT is 2.28.0000 & radios are 2.23.10.0123r/2.23.10.0124r.
That last time I was able to S-OFF I used the wire method and ControlBear for Windows. I went to the website Unlimited.IO and they no longer support Windows so I have no idea on how to S-OFF since I did it months ago. However, I did find ControlBear v0.1 for Windows here on the forums: http://forum.xda-developers.com/showpost.php?p=27764982&postcount=2079 My first question is will this version work for me? If you download it and open it you can see the zips contents. I wasn't sure If had to RUU back down to an earlier version for it to work? And last time I ended up being on a Juopunutbear HBOOT somehow.
So basically I want to be able to get back onto CyanogenMod 10.1 properly this time. I haven't done anything to my phone yet, still unrooted, on stock, etc.. I know my first step is too unlock it using the htcdev website but from there I'm confused, I can't remember the steps its been too long.
I need someone to please explain how I can get back to CM 10.1 and remain on the latest firmware/drivers/hboot etc. So I need help with rooting, s-off, how to get TWRP recovery back on, which to do first, etc.
I appreciate the help and I'll make sure I save this in case it ever happens again. Also, my apologies again for the previous thread, it was just too much going on, I just need simple steps.
Am not positive but i think u will need Ubuntu as that one wont work on the new 2.28 hboot. So lets start with u installing ubuntu on a drive or live cd
Sent from my Infected Rezound using xda app-developers app
xanda143 said:
Am not positive but i think u will need Ubuntu as that one wont work on the new 2.28 hboot. So lets start with u installing ubuntu on a drive or live cd
Sent from my Infected Rezound using xda app-developers app
Click to expand...
Click to collapse
ControlBear 0.1 worked for me on Windows, took a few tries but it finally pulled through. These where my steps:
1. unlocked
2. flashed recovery
3. flashed [ROM] OTA-Global-Stock-4.05.605.14 710RD-Rooted 5/1/13
4. flashed boot.img from the rom
5. did wired trick with CB 0.1
so i think im good now? just have a couple questions.
- my phone now says tampered/locked/s-off? last time i s-off it didnt have that tamper there, is this normal?
- im still on hboot 2.28.0000 & radio 2.23.10.0123r/2.23.10.0124r. is this latest hboot/firmware/radio?
- im still on that rom that i linked above. im good to go ahead and flash and jb rom now?
- last, is there anything else i need to do with my phone? fixing the mainver, etc.
xXezmacXx said:
- my phone now says tampered/locked/s-off? last time i s-off it didnt have that tamper there, is this normal?
- im still on hboot 2.28.0000 & radio 2.23.10.0123r/2.23.10.0124r. is this latest hboot/firmware/radio?
Click to expand...
Click to collapse
That's normal if you're still using an unpatched hboot. If you will still use some fastboot commands (I use fastboot boot zImage/fastboot flash zimage zImage alot) then look into vynlfreak's 2.27 patched hboot. DO NOT UNLOCK flash patched hboot instead.
xXezmacXx said:
- im still on that rom that i linked above. im good to go ahead and flash and jb rom now?
- last, is there anything else i need to do with my phone? fixing the mainver, etc.
Click to expand...
Click to collapse
Flash your rom and don't worry about mainver.
Just wanted to thank you two. I have always been hesitant about s-offing my phone. But seeing it here in a few simple steps gave me the courage to finally pull the trigger. I know I am super late to the S-Off party, but am thrilled to finally have arrived!