Bare with me here...My phone was an hboot 1.3 and I rooted my phone...Everything went fine then something went crazy so I reverted back to Sprints stock rom 1.1.3.651.7 and removed root (S-ON)...After doing that, my phone now has hboot 1.4...When I went to root my phone again, knowing my hboot had changed, I got a new beta key for revolutionary...I didn't want to try the original key thinking it would have caused an issue since I was hboot 1.4 instead of the 1.3 associated with my S/N...Now I guess my S/N is attached to 2 beta keys and neither work...What in the world do I do now?...
antyx said:
Bare with me here...My phone was an hboot 1.3 and I rooted my phone...Everything went fine then something went crazy so I reverted back to Sprints stock rom 1.1.3.651.7 and removed root (S-ON)...After doing that, my phone now has hboot 1.4...When I went to root my phone again, knowing my hboot had changed, I got a new beta key for revolutionary...I didn't want to try the original key thinking it would have caused an issue since I was hboot 1.4 instead of the 1.3 associated with my S/N...Now I guess my S/N is attached to 2 beta keys and neither work...What in the world do I do now?...
Click to expand...
Click to collapse
ask the devs here, http://webchat.freenode.net/?channels=revolutionary
I did...They helped me out and I am now rooted and flashed recovery...Apparently, whenever it says invalid beta key, you need to delete the revo zip and download it again and start over entering the same info to get the beta key and it will work the second time...
Good info. Thanks for sharing...most people fix their issue and never say how. No one benefits from that XD
Related
im trying to root the 2.07.605.0 gb leak and it says the first step is to flash hboot and it not working will someone help me
What are you using to root?
Sent from my HTC Thunderbolt
When I loaded the newest leak I went to HBOOT and it said locked down lol.
JBO1018 said:
What are you using to root?
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
idk i have a mac and this is my first time
When I looked at he 2.10 version it said the same thing. I didnt try anything with it once I saw that. Hope verizon doesnt mind when they get it back as a replacement.
blueis300 said:
When I looked at he 2.10 version it said the same thing. I didnt try anything with it once I saw that. Hope verizon doesnt mind when they get it back as a replacement.
Click to expand...
Click to collapse
You might just end up with the retail price of a Thunderbolt on your next bill. Really tho they will be able to take one look and see you are running leaked software.
BTW the pink "Locked" at the top of hboot has to do with having HTC's official unlock capabilities built in. You can still root that build easily.
Sent from my HTC Thunderbolt
codyh666 said:
idk i have a mac and this is my first time
Click to expand...
Click to collapse
Well I don't know of any root method where the first thing you do is flash an hboot so..... Also the only way I know of for sure to root that build is with Revolutionary but I don't think there is a mac version. Plus it makes it somewhat hard to get back to stock when you use Revolutionary.
Sent from my HTC Thunderbolt
***LOCKED*** On Bootloader
Hello All,
First of all thanks for the awesome easy guide !!
This is the first time I am rooting my HTC Tbolt and have had an issue to start with.
Used the instructions in the link below:
http://forum.xda-developers.com/showthread.php?t=1401959
After I download the 2.11.605.5 downgrade zip, I rename it, put in on the SD Card and go to HBOOT and it installs the downgrade just fine.
But at the end of this process, when I try to get the MR4 Radio onto the SD Card and install it, it simply does not happen. HBoot checks for the file, finds it, but nothing happens. I have renamed in properly and followed instructions to the dot.
I also noticed a ***LOCKED*** right on top of the screen and I think this could be an issue.
Can I go ahead and proceed with the Revolutionary Root Technique ? Would this be possible at this point ?
Is there anyway I can get Flash the MR4 Radio before I actually root ?
Also, would I be able to flash the MR4 Radio onto my device after Rooting ?
Any help is much appreciated !
Thanks in advance !
Cheers !
I just got the HTC EVO 3D, and like a tard I updated everything not really paying attention to updating system updates. Well I updated to Hboot 1.5...
Is there a way to flash back or RSD back to stock firmware and software? Or am I screwed until they come up with a way to root at hboot 1.50
Thanks for the info in advance.
Sprint HTC EVO 3D
2ndComing said:
Is there a way to flash back or RSD back to stock firmware and software?
Click to expand...
Click to collapse
Whatever we call it for Sprint...
2ndComing said:
I just got the HTC EVO 3D, and like a tard I updated everything not really paying attention to updating system updates. Well I updated to Hboot 1.5...
Is there a way to flash back or RSD back to stock firmware and software? Or am I screwed until they come up with a way to root at hboot 1.50
Thanks for the info in advance.
Click to expand...
Click to collapse
Unfortunately no, there isn't a way to downgrade. HTC makes it so you can't downgrade the bootloader (unless you were S-off). The RUU would error out at the bootloader, and tell you 'main version older' or something like that. You could use the HTC 'unlock' method and flash a recovery, but you'd still be S-on, and won't be able to flash kernels. If I were in your situation, I'd probably just hang tight for a little while and wait and see if revolutionary gets updated (because it's said that they're in the process of working on the 1.5hboot).
Yeah I just ran thru the HTC Dev unlock already. Back everything up, and flashed the recovery. I think I will try out the cleanrom for now and see if anything happens. I been up too long and I am delirious lol. Thank you for your reply. Hopefully I didn't screw anything else up hah.
2ndComing said:
I just got the HTC EVO 3D, and like a tard I updated everything not really paying attention to updating system updates. Well I updated to Hboot 1.5...
Is there a way to flash back or RSD back to stock firmware and software? Or am I screwed until they come up with a way to root at hboot 1.50
Thanks for the info in advance.
Click to expand...
Click to collapse
RSD is a Motorola term. Just putting it out there. For HTC, it's called an RUU.
R S to da haahaahaa D
Product F(RED) said:
RSD is a Motorola term. Just putting it out there. For HTC, it's called an RUU.
Click to expand...
Click to collapse
LOL Yeah I just traded AT&T today for Sprint. I was so tired of their dropped calls, and crappy service. My other phone is a Motorola Atrix. haahaa hence the RSD terms
I know it calls for s-off but ima try anyhow lol
Just an Update
http://forum.xda-developers.com/showthread.php?t=1224781
Here is an update on unlocked bootloader for 1.50 Hboot.
Confirmed it says unlocked, but seems to be some issues with s-on s-off. I was able to get recovery flashed. Now I am trying to flash cleanrom atm. As we speak booting to cleanrom. Booted...no issues thus far. Running great. Now I will try a different kernel and see if that works.
I am having a hard time with getting my voicemails sent to my evo3d as a notification for a new message.. this has been a prob for sometime now and I've always just thought that I never had ne voicemails or perhaps I haven't set up my voicemail account right or at all just yet when come to find out yesterday I had 33 msgs exceeding my inbox n lost em all.. never once had I got the notifications or alerts for any of em though. Can any one assist me in fixing this issue please? I've alrdy tried calling CricKet and having them reset my voicemail services n that didn't seem to werk either. So far that's as far as I got. Also, I can't seem to get the thumbnail photos of my contacts to show in the messaging app or whatever, not even as i am in the current conversation with sumone.. it just shows the blank pic. And they show in my contacts book/app just fine. How do I go about fixing this as well? Thanks in advance.. oh yea lemme give yu detail on my phones details to further help with the assistance. I am currently running "joeykrim's original 1.2.0 Odex" ROM which I had gottn off ROM Manager and flashed over using TWRP's 1.3 Recovery .. I might also add that i am with CricKet's slow ass service running on PRL #45512 in Colorado. And yes this ROM is the latest updated version of 2.3.4... If need more info or even a descent screenshot of my settings or info on device and image of the problems I'm having I can also provide upon request..
Sorry if this ain't the place for this question but I have searched evrywhere n did my part in th research n read rule alrdy n have found nuthn what so ever related to my concerns so please don't gimme the ol look around speech please... Thanks much in advance .. KaeDee. Please email me @ [email protected] or contact me private message with helpful or useful info thanks again..
HTC EVO 3D (CricKet & S-Off)
2ndcoming if you have the 1.5 update u cant flash any other kernal yet...from what i saw there is like 2 out right now untill they get the source code and you can only flash 2.3.4 roms..and if i remember correctly if u can flash a recovery u have s off but it will still say s on
EpicBarbecue said:
2ndcoming if you have the 1.5 update u cant flash any other kernal yet...from what i saw there is like 2 out right now untill they get the source code and you can only flash 2.3.4 roms..and if i remember correctly if u can flash a recovery u have s off but it will still say s on
Click to expand...
Click to collapse
Nah we were in this situation for awhile with the Incredible. Nand unlock or s-off lets you flash radios and hboot. . It also sticks through most updates for instance those who had s-off before the 1.5 update are able to go back if they want and are able to root without using htc unlock.
what you get with the htc unlock is a permanent root that allows custom recovery and roms. not sure about kernels as I have read conflicting posts. as always your best bet is to read up in the forums before accepting any updates from htc.
any updates fellow members security -off for the new hboot version ?
lafester said:
Nah we were in this situation for awhile with the Incredible. Nand unlock or s-off lets you flash radios and hboot. . It also sticks through most updates for instance those who had s-off before the 1.5 update are able to go back if they want and are able to root without using htc unlock.
what you get with the htc unlock is a permanent root that allows custom recovery and roms. not sure about kernels as I have read conflicting posts. as always your best bet is to read up in the forums before accepting any updates from htc.
Click to expand...
Click to collapse
I unlocked through the HTC unlock . Its correct that it doesnt allow you to get S-Off , but from my expierence flashing on the 3D is as follows . If you enter fastboot through CMD screen and fire up recovery through CMD it flashes everything . I have flashed several different roms in the past week . Boot animations change , Kernels change everything changes . Now I have not tried to flash radios and so forth . That may still be locked out I am not sure from personal expierence . I only went the HTC unlock way , mainly due to getting a new job and now getting a discount through verizon . I may (Keyword MAY) jump ship to Verizon only due to coverage issues and the Droid Prime . For the time being the coverage issues I can deal with . Also most of my family is on verizon . But back to the main point . Most of the functions that I had with S-Off I am still able to do as long as I start up recovery through CMD prompt . I have a feeling HTC did this intentionally . My theories on it is , by forcing users to go through the command promt . It "kinda" weeds out the users that know what they are doing from the ones that don't. Yes its easy to get around it and now isnt so much a problem to flash through cmd and most anyone will eventually find the way to do so . But that is how the internet works , information is passed even faster than before and like all information . The ones who really shouldnt mess with it will get access to it and others who know what they are doing have it . When I mean by users that shouldnt have access I mean the ones who have no clue what a Kernel is and just flash things to flash things and end up with a nice paperweight . Im by no means a hardcore hacker or power user , but I do spend several nights reading as much as I can and asking the correct questions before I proceed with anything on my phone since its my only form of communication (no home phone).
I unfortunately dropped my phone this last weekend and shattered the screen. I still have it (probably for only another day) and it still works. Is there any way to use this rooted, s-off, busted phone to get s-off on my new phone that came installed with 1.5?
bpdamas said:
I unfortunately dropped my phone this last weekend and shattered the screen. I still have it (probably for only another day) and it still works. Is there any way to use this rooted, s-off, busted phone to get s-off on my new phone that came installed with 1.5?
Click to expand...
Click to collapse
i dont mean to sound like a smartass but you would be screwed in that situation like me. im stuck with hboot 1.5 lol
i would say just try to get the screen replaced lol
xadidas4lifex said:
i dont mean to sound like a smartass but you would be screwed in that situation like me. im stuck with hboot 1.5 lol
i would say just try to get the screen replaced lol
Click to expand...
Click to collapse
I already have activated the new phone and the one I dropped had some scratches on the outside too. It would be too much to switch everything that was affected by the fall. Oh well. I am just going to send the phone back to asurion and move on.
bpdamas said:
I already have activated the new phone and the one I dropped had some scratches on the outside too. It would be too much to switch everything that was affected by the fall. Oh well. I am just going to send the phone back to asurion and move on.
Click to expand...
Click to collapse
All that's required is that you have access to torq drivers, and have careful hands to handle ribbon cables, and youre good to go! But being 3D when u replace the screen it's not just the glass digitizer, its a whole unit and I think its even easier to replace
What is this?
Does anyone know what this is or who is developing it?
http://www.youtube.com/watch?v=_yB1PG1ZNGs
Bump.
10char
kc_exactly said:
Does anyone know what this is or who is developing it?
http://www.youtube.com/watch?v=_yB1PG1ZNGs
Click to expand...
Click to collapse
It's yousefAK....duh....
I will call balderdash on this, as he only made a video of the GUI, which could easily be cobbled together in about 20 min. The video was uploaded over a month ago (Oct 1), and is "in development". I'm thinking the exploit referred in the description either:
A. Never existed
B. Didn't work like the vid owner anticipated
Even the yousefAK offers this response, from 3 weeks ago (around Oct 21):
"Use HTC's unlock and flash TWRP 1.1. Then flash the SU files and you have permanent root. The only thing is that you will have to flash kernels through fastboot"
Well I got myself into a real pickle here. I was trying to get the newer OTA with my unlocked rooted 3D I tried everything I have here on how to do it but now my phone just reboots itself after it get to the sprint screen sometimes it does make it to where is show the info bar at the top with the time but reboots soon after. I have tried a stock recovery and a new OTA RUU using hboot and the PG86IMG.IMG which did install at hboot but I still have the same issues. Any ideas on how to at least get back to normal?
mviars said:
Well I got myself into a real pickle here. I was trying to get the newer OTA with my unlocked rooted 3D I tried everything I have here on how to do it but now my phone just reboots itself after it get to the sprint screen sometimes it does make it to where is show the info bar at the top with the time but reboots soon after. I have tried a stock recovery and a new OTA RUU using hboot and the PG86IMG.IMG which did install at hboot but I still have the same issues. Any ideas on how to at least get back to normal?
Click to expand...
Click to collapse
What hboot are you ? Also what software are you on 2.08 ? You are CDMA I am guessing? If all else fails man boot into your recovery and wipe just not your SD card and go back to hboot relock your phone and use the latest 2.17 ruu exe.. Works every time and then root again and your set... This info is for CDMA only Not GSM>>>
THanks reaper. I was on hboot 1.5 and CDMA sorry for not stating. I ended up just taking it back to sprint and they gave me a new phone which I am actually happy about because of a few blemishes I had on the phone. I think I will wait till after ICS and see if they can get it rooted. I really only want the ability to wireless tether.
Again thanks for the reply
so my wife got a replacement evo being hers had a few. issues. came with 1.50 hboot. i did the downgrade method to 1.40 phone constantly reboots or bootloops at times. i figured well maybe was a firmware issue. so when sprints firmware leaked. i updated it all even bootloader. its now 1.58 hboot. shows locked but s-off. i still have 4ext recovery installed on it. i have tried to flash the stock rooted rom. the phone boots after sits idle for a litle while it will go into boot loops. im at my wits end here. thinking it maybe hardware now. want others opinions. before i flash stock non rooted and bring it in for service. any thought?
You could try to unroot and go back to stock to see if the bootloops stop.
Man i love FrootLoops.. oops.. crap, i read the title wrong..
ON a serious note, do what coal686 said, go back to factory stock and start from scratch. Take out as many of the variables as possible.
so how do you suggest i do that? there is no ruu for the new ota update. im on newhboot. so im lost as to how to attempt to relock to stock for service.
so i ran the pg86img for 2.17 everything down graded fine. then rat the ota update to ics. updated to ics 2.89 fine. weird thing is it still shows s-off. only thing so far sense has froze on her twice. but the reboots have stopped. waiting a day to make sure. then ill unlock if i need to.then stock rooted for her.
kaos420 said:
so i ran the pg86img for 2.17 everything down graded fine. then rat the ota update to ics. updated to ics 2.89 fine. weird thing is it still shows s-off. only thing so far sense has froze on her twice. but the reboots have stopped. waiting a day to make sure. then ill unlock if i need to.then stock rooted for her.
Click to expand...
Click to collapse
You don't need to unlock as s-off is better.
S-off > Locked with Tapatalk 2
kaos420 said:
so my wife got a replacement evo being hers had a few. issues. came with 1.50 hboot. i did the downgrade method to 1.40 phone constantly reboots or bootloops at times. i figured well maybe was a firmware issue. so when sprints firmware leaked. i updated it all even bootloader. its now 1.58 hboot. shows locked but s-off. i still have 4ext recovery installed on it. i have tried to flash the stock rooted rom. the phone boots after sits idle for a litle while it will go into boot loops. im at my wits end here. thinking it maybe hardware now. want others opinions. before i flash stock non rooted and bring it in for service. any thought?
Click to expand...
Click to collapse
I'm in the same boat the only difference is my wife's phone is completey stock no root & s-on latest ics update hboot 1.58 u know the rest. Started bootlooping out of nowhere & I don't know what to do,did a factory reset through bootloader & still bootloops like crazy! Any ideas would be helpful & thank you in advance!
Hi guys.
I was trying to do one of two things. Either get to stock ICS with the RUU or get to an older stock version so that my phone would update itself.
I ran the ICS RUU and ran into an issue. Im on Hboot 2.28 Radio 2.23.10.0123r/2.23.10.0124r
I am S-On and relocked to get run the RUU.
I got an error as it said the Hboot version is older. Now I am stuck on the Bootloader with TAMPERED, RELOCKED, and Security Warning.
I should have known that I potentially had a leaked Hboot version but it was so long ago I forgot.
What can I do? Iv been googling and searching threads without much luck. Do I have to S-off? Can I S-off from this position? The other issue I keep running into is dead file links.
brownsfan said:
Hi guys.
I was trying to do one of two things. Either get to stock ICS with the RUU or get to an older stock version so that my phone would update itself.
I ran the ICS RUU and ran into an issue. Im on Hboot 2.28 Radio 2.23.10.0123r/2.23.10.0124r
I am S-On and relocked to get run the RUU.
I got an error as it said the Hboot version is older. Now I am stuck on the Bootloader with TAMPERED, RELOCKED, and Security Warning.
I should have known that I potentially had a leaked Hboot version but it was so long ago I forgot.
What can I do? Iv been googling and searching threads without much luck. Do I have to S-off? Can I S-off from this position? The other issue I keep running into is dead file links.
Click to expand...
Click to collapse
So I think I found out what I did. 2.28 is the Global version. I must of rooted that version and flashed roms. I wanted to unroot and get back to stock software version.
Where should I go from here? Is there an RUU for the ICS Global? I can not seem to find one.
Have you tried unlocking the bootloader again?
Edit: I searched for a long time (a few days ago) but couldn't find any information on S-Off, not going back to stock for people on the latest OTA. I'm not the best person to give advice, but if you're on the current OTA, I don't think you can use the RUU.exe.
Also, you can't downgrade if you're S-On - only upgrade..
Sent from my ADR6425LVW using xda app-developers app
Thingula said:
Have you tried unlocking the bootloader again?
Edit: I searched for a long time (a few days ago) but couldn't find any information on S-Off, not going back to stock for people on the latest OTA. I'm not the best person to give advice, but if you're on the current OTA, I don't think you can use the RUU.exe.
Also, you can't downgrade if you're S-On - only upgrade..
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Yes I can unlock again and that does get me unstock from the boot screen but still cant get where I want. Hmm.
I wonder if you can fastboot-flash the older kernels, using a computer, then flash the old stock ROM, lock the bootloader, then run an RUU.. Can anyone confirm this? Sounds too simple to work on an HTC phone.
Edit: No, of course that doesn't work. Sorry, I can't really offer any more help.. I'll have to just hope that someone more knowledgeable can take over.
Sent from my ADR6425LVW using xda app-developers app
Be prepared, I get rather long winded.
If you were on the most current 4.05.605.14 with S-on which based on what you list as the radios and hboot is what it appears you were on, then you are in a difficult spot. The really bad news is the only RUU you would be able to use is the 4.05.605.14 and no one has admitted to being able to get ahold of. The most current one available is 3.14.605.12 but that is useless to you. You would have to S-off to go back to stock but would have to have a working rom to do it. It's not impossible but it aint easy. I just had to do it about a month ago when I was trying to S-off my replacement Rezound. It came with the most current stock ROM and I didn't bother reading up on the current ControlBear method. In the past, you had to have a rooted rom in order to S-off. So of course, I unlocked the bootloader, flashed AmonRa 3.15 and then used superuser to root it and then went about trying to S-off. I couldn't find my previous windows based versions of ControlBear so I went about making a live cd ubunto disk and trying to S-off. It wouldn't work. Then I read the unlimited.io site instructions and found that the current version needs the unrooted stock rom to succeed. I really never paid attention to unrooting before because if I had to do it, I could always just run the factory wipe and root would be gone but not this time. It kept showing that I was rooted. So I tried wiping data, cache, dalvik cache, and after that didn't work, I wiped the system. Very bad move on my part. Now I couldn't get past the bootloader. I thought I was done for because I knew with S-on, there was no going back and the global rom RUU was still not available.
After trying all kinds of things I ended up
1. downloading the 4.05.605.14 stock rooted rom listed HERE (Thanks MicroMod777) in the Rezound Development section.
2. Then downloaded the current firmware.zip from HERE (Thanks Flyhalf205) and then extracted the recovery.img along with the hboot .nb0 file from it.
3. I then created 2 separate custom ph98img.zip for each so I could always reinstall the stock hboot and the stock recovery.img.
4. I extracted the boot.img from the rooted rom and flashed that first. I don't remember if I did it via adb in fastboot usb or with another ph98img.zip and then
5. I made sure that my bootloader was unlocked and then installed AmonRa as the recovery
6. Then used AmonRa to flash the stock rooted zip file. I then wiped the cache 3 times and the dalkvik cache 3 times.
I let the phone reboot and I was back to a working phone.!!! Then I found out that it was rooted with SuperSu which gives you the option of doing a full permanent unroot which I did. I then put that ph98img that I had made that had the stock recovery.img on it and flashed that in the bootloader. After rebooting I now had a fully stock phone and proceeded to do the S-off. I left the bootloader unlocked as directed by the unlimited.io site. I had limited experience with ubunto but found THIS PAGE that helped walk me through it. I followed it exactly and ended up with an S-off phone. One thing that wasn't clear to me was how to open a terminal in ubunto but I figured that out after trial and error. IIRC, I clicked on the home tab on the left and then in the search box, typed terminal. The first icon that was shown was a terminal emulator and I used that for the commands.
Now I still wasn't finished. I ended up relocking the bootloader but didn't like the relocked and tampered flags that were showing. So I ended up running the most recent RUU (3.14.605.12 found HERE and I now had a ***LOCKED*** bootloader and then let the phone reboot. After it rebooted, I hit the home key and bypassed the setup. I then got into settings and then into software update and let it update. It did a small update and then had to repeat the reboot, bypass setup, and software update. This time it did the global update. I let it reboot but this time, I ran the setup. Once I was up and running, I again went into bootloader and reinstalled AmonRa and used the 3.16 version and made sure to do a nandroid before doing anything further. After that, I got ahold of SuperSu 1.51 and flashed that in the AmonRa recovery. I now had a ***LOCKED*** stock rooted Rezound and several nandroid backups of both fully stock and rooted. Which turned out to be a great idea because not even 3 weeks later after this, the phone started malfunctioning (power button) and a problem with the camera so it got replaced and I had to put it back fully stock. I was already setup for this. I unrooted, put the stock recovery back on, and made it S-on. When the replacement came, I immediately unlocked it, did the S-off (only took one try), relocked, ruu'd back to 3.14.605.12, updated to global rom, flashed AmonRa, and restored with my most recent rooted nandroid. and I am back up and running a whole lot sooner...
I hope this helps.
Very much so! Thank you. If I could hit the thanks button 10x I would.
Im sure im not the only only to have the Hboot 2.28 issue.
hey man you still around ? i need some help with a situation like this
dust906 said:
hey man you still around ? i need some help with a situation like this
Click to expand...
Click to collapse
I replied to you in your thread.
S-On Locked stock !
mikeyk101 said:
Be prepared, I get rather long winded.
If you were on the most current 4.05.605.14 with S-on which based on what you list as the radios and hboot is what it appears you were on, then you are in a difficult spot. The really bad news is the only RUU you would be able to use is the 4.05.605.14 and no one has admitted to being able to get ahold of. The most current one available is 3.14.605.12 but that is useless to you. You would have to S-off to go back to stock but would have to have a working rom to do it. It's not impossible but it aint easy. I just had to do it about a month ago when I was trying to S-off my replacement Rezound. It came with the most current stock ROM and I didn't bother reading up on the current ControlBear method. In the past, you had to have a rooted rom in order to S-off. So of course, I unlocked the bootloader, flashed AmonRa 3.15 and then used superuser to root it and then went about trying to S-off. I couldn't find my previous windows based versions of ControlBear so I went about making a live cd ubunto disk and trying to S-off. It wouldn't work. Then I read the unlimited.io site instructions and found that the current version needs the unrooted stock rom to succeed. I really never paid attention to unrooting before because if I had to do it, I could always just run the factory wipe and root would be gone but not this time. It kept showing that I was rooted. So I tried wiping data, cache, dalvik cache, and after that didn't work, I wiped the system. Very bad move on my part. Now I couldn't get past the bootloader. I thought I was done for because I knew with S-on, there was no going back and the global rom RUU was still not available.
After trying all kinds of things I ended up
1. downloading the 4.05.605.14 stock rooted rom listed HERE (Thanks MicroMod777) in the Rezound Development section.
2. Then downloaded the current firmware.zip from HERE (Thanks Flyhalf205) and then extracted the recovery.img along with the hboot .nb0 file from it.
3. I then created 2 separate custom ph98img.zip for each so I could always reinstall the stock hboot and the stock recovery.img.
4. I extracted the boot.img from the rooted rom and flashed that first. I don't remember if I did it via adb in fastboot usb or with another ph98img.zip and then
5. I made sure that my bootloader was unlocked and then installed AmonRa as the recovery
6. Then used AmonRa to flash the stock rooted zip file. I then wiped the cache 3 times and the dalkvik cache 3 times.
I let the phone reboot and I was back to a working phone.!!! Then I found out that it was rooted with SuperSu which gives you the option of doing a full permanent unroot which I did. I then put that ph98img that I had made that had the stock recovery.img on it and flashed that in the bootloader. After rebooting I now had a fully stock phone and proceeded to do the S-off. I left the bootloader unlocked as directed by the unlimited.io site. I had limited experience with ubunto but found THIS PAGE that helped walk me through it. I followed it exactly and ended up with an S-off phone. One thing that wasn't clear to me was how to open a terminal in ubunto but I figured that out after trial and error. IIRC, I clicked on the home tab on the left and then in the search box, typed terminal. The first icon that was shown was a terminal emulator and I used that for the commands.
Now I still wasn't finished. I ended up relocking the bootloader but didn't like the relocked and tampered flags that were showing. So I ended up running the most recent RUU (3.14.605.12 found HERE and I now had a ***LOCKED*** bootloader and then let the phone reboot. After it rebooted, I hit the home key and bypassed the setup. I then got into settings and then into software update and let it update. It did a small update and then had to repeat the reboot, bypass setup, and software update. This time it did the global update. I let it reboot but this time, I ran the setup. Once I was up and running, I again went into bootloader and reinstalled AmonRa and used the 3.16 version and made sure to do a nandroid before doing anything further. After that, I got ahold of SuperSu 1.51 and flashed that in the AmonRa recovery. I now had a ***LOCKED*** stock rooted Rezound and several nandroid backups of both fully stock and rooted. Which turned out to be a great idea because not even 3 weeks later after this, the phone started malfunctioning (power button) and a problem with the camera so it got replaced and I had to put it back fully stock. I was already setup for this. I unrooted, put the stock recovery back on, and made it S-on. When the replacement came, I immediately unlocked it, did the S-off (only took one try), relocked, ruu'd back to 3.14.605.12, updated to global rom, flashed AmonRa, and restored with my most recent rooted nandroid. and I am back up and running a whole lot sooner...
I hope this helps.
Click to expand...
Click to collapse
This guide was FREAKING AWESOME. It led me to finally after 2 years go S-Off (wire trick) to do RUU, etc. Have to return phone and have already got replacement. Crossed my fingers and everything looks stock stock stock !