I don't want to write in Fuses' thread since they requested so, but I believe this is an important question, so I'll ask it here:
I'd like to S-OFF my phone when the exploit is ready and up, mainly to flash custom splash screens, and be ready when a supercool and stable ICS ROM with custom radio and sh*t hits the dev section, but before that I'll most likely flash the official ICS RUU when it becomes available (usually X is pretty fast uploading those) and root it, so my question is will I be able to flash such RUU if I have S-OFF, since relocking the bootloader is a must in order to do that. Or put in other words: can you relock the bootloader if it's S-OFF?
If I remember right (too lazy to recheck the thread) the s-off thread it was more of a concern if the device was unlocked to s-off it rather than locked, I don't think thats an issue
Shouldnt be a problem at all. And im pretty sure u dont need to relock to flash ruu either
Sent from my NRGized Amaze...
via xda premium
My bootloader is already htc-dev unlocked, globatron yesterday confirmed that this is not an issue and you can s-off the phone with unlocked/relocked bootloader, what I would like to know is after I s-off the phone would I face any problem flashing the stock RUU, considering the fact that HTC may find a way to kill the s-off exploit if it came out before the update (which is more likely)...
Sorry if I didnt put my question correctly in the OP.
aj, I believe bootloader has to be locked to flash RUU, at least thats what XBoarder put as a necessary step...
I still don't think it would be an issue, since from what I've heard downgrading an hboot is always a possibility, once an exploit is found for one we can always go back to that one
s-off has no bearing on whether or not you can flash the stock rom. when it drops, put it on your sd and boot into the bootloader and it will do the rest
Related
ok, so i went through the s-off process and completed it successfully. It asked me if I wanted to flash the jb-hboot.zip which I said yes. Now, when I boot into hboot it has this ugly pink bar accross the top that says "juno..." (the name of the team). I am currently on the new firmware running BAMF Evita sense 4. Is there a stock ics hboot or something i can put back in its place that will leave s-off, be compatible with new firmware and not give custom labels accross the top?
Please help....
jbeitel said:
ok, so i went through the s-off process and completed it successfully. It asked me if I wanted to flash the jb-hboot.zip which I said yes. Now, when I boot into hboot it has this ugly pink bar accross the top that says "juno..." (the name of the team). I am currently on the new firmware running BAMF Evita sense 4. Is there a stock ics hboot or something i can put back in its place that will leave s-off, be compatible with new firmware and not give custom labels accross the top?
Please help....
Click to expand...
Click to collapse
Technically, you could just reflash the leaked RUU then and you will still have S-off. Changing Hboots , won't affect S-off, Numerous threads have popped up with just radio's and Hboots to flash. Just be careful and don't mix and match Radios and Hboots to avoid trouble.
mjh68 said:
Technically, you could just reflash the leaked RUU then and you will still have S-off. Changing Hboots , won't affect S-off, Numerous threads have popped up with just radio's and Hboots to flash. Just be careful and don't mix and match Radios and Hboots to avoid trouble.
Click to expand...
Click to collapse
do I have to relock anything like when I upgraded to the new ics firmware? I was hoping for a straight forware ph98img.zip flash. i know, thats lazy but easy.
IMO, leave it. Put up with eye sore. If the flash to the stock one goes belly up, you will brick the phone. Leave it til you need to go back to an S-On device.
Snuzzo said:
IMO, leave it. Put up with eye sore. If the flash to the stock one goes belly up, you will brick the phone. Leave it til you need to go back to an S-On device.
Click to expand...
Click to collapse
Technically true, but really as long as he doesn't pull the plug while its loading the Hboot its not a great danger.
---------- Post added at 12:03 PM ---------- Previous post was at 12:00 PM ----------
jbeitel said:
do I have to relock anything like when I upgraded to the new ics firmware? I was hoping for a straight forware ph98img.zip flash. i know, thats lazy but easy.
Click to expand...
Click to collapse
I am pretty sure , their hboot is already relocked . So shouldn't have to relock , I went all the way back to GB and used the full exe RUU and relocked since I didn't know that it was locked initially and it ran just fine.
I would try without relocking , it will either run or fail before it starts doing anything.
Thank you mjh. Yes it is relocked & again leave it as is. Trust me you will thank me later. No need for unlock codes anymore and just waiting for roms to be rebased and official OTA(not for the actual OTA but for kernel source if released).
you guys know how to frustrate a guy, geez. What a great world that everyone can have their own opinion. Now, who's do I want to have?
I know exactly how you feel. Cant make up my mind what I want to do either. Currently on ICS S-OFF displaying Tampered/Locked
Do I RUU back to GB and flash the ENG Hboot?
Do I go ahead and flash jb_hboot? And which one is it actually. There have been way to many threads and posts on S-OFF and a bunch of different answers.
Do I leave it alone and wait to see what happens with the next release?
In some ways it would be nice to be back on Hboot 2.11 and have ENG S-off but is it worth it? Wont really know until the next official release comes out.
jbeitel said:
you guys know how to frustrate a guy, geez. What a great world that everyone can have their own opinion. Now, who's do I want to have?
Click to expand...
Click to collapse
I am not telling not to flash, just telling you after S-off and using their Hboot it is already locked, but you can still flash the stock RUU. I did and haven't had any issues , but I didn't realize it was already locked so relocked and unlocked by HTC dev without knowing it . I am still tempted to flash the eng hboot , but not sure if I really have a need to.
mjh68 said:
I am not telling not to flash, just telling you after S-off and using their Hboot it is already locked, but you can still flash the stock RUU. I did and haven't had any issues , but I didn't realize it was already locked so relocked and unlocked by HTC dev without knowing it . I am still tempted to flash the eng hboot , but not sure if I really have a need to.
Click to expand...
Click to collapse
whats the big deal with the engineering hboot? is it different or is that the standard one in the ruu?
Snuzzo said:
No need for unlock codes anymore
Click to expand...
Click to collapse
There is more difference than this(allows more commands to be ran in prompts) but with an ENG hboot, you can keep it locked and s-off, along with still being able to flash anything your heart desires. ALTHOUGH if you wish to go back to s-on, flash an RUU of your choice first. As when you do write secureflag and a few reboots on an ENG hboot, you could brick.
Leave the hboot they give you. The tag might be annoying but it is better than having to re-unlock to use fastboot commands.
Why is un- re locking not ideal? It takes 2 minutes.
Sent from my v6 supercharged Rezound.
AJMetal87 said:
Why is un- re locking not ideal? It takes 2 minutes.
Sent from my v6 supercharged Rezound.
Click to expand...
Click to collapse
Scotty posted earlier if your S-OFF then unlock and relock again it will alway show relocked again unless you RUU then S-ON and then S-OFF again. If you S-OFF and don't unlock it and RUU it will say locked but its best to use the patched hboots supplied to be able to use certain fastboot commands that way you don't have to unlock and not have a problem with it saying relocked.
Sent from my ICS Rezound
LakerStar25 said:
Scotty posted earlier if your S-OFF then unlock and relock again it will alway show relocked again unless you RUU then S-ON and then S-OFF again. If you S-OFF and don't unlock it and RUU it will say locked but its best to use the patched hboots supplied to be able to use certain fastboot commands that way you don't have to unlock and not have a problem with it saying relocked.
Sent from my ICS Rezound
Click to expand...
Click to collapse
Aside of the text difference on the bootloader and potential warranty comprimising, is there any other downfall?
No downfall. But again, nor needed to unlock if s-off.
Sent from my ADR6425LVW using XDA
I'm not trolling or trying to start a argument, but if that's a big deal to you to have the pink junabear banner across your hboot screen then you should have never s-off. I mean really. Who sits there and stares at the hboot screen and decides that it doesn't look good. Lmao.
Sent from my ADR6425LVW using XDA
Especially when the stock hboot uses the same color banner but says locked instead?
Via Rezound using XDA Premium
GB
Anyone who was on Gingerbread when the did S-Off does *NOT* have the Juououuoouououpnutbear logo; just standard Eng HBoot.
This would be me.
Bump. I need the stock Hboot to send back to Verizon. The GB hboot if anyone has it please.
Is there anyway to reset the Rezound to the factory locked bootloader?
http://forum.xda-developers.com/showthread.php?p=25165453
Assuming you have done the HTC Dev unlock, you must do S-off and follow the guide here to get back to reading "Locked" and "S-on" simultaneously.
Edit: Ok, so I see you are S-off at the moment, you are going to want to backup all your data in your custom recovery if you haven't done so already (still on CWM or got that straightened out?)
Going to download the latest official RUU available (the GB OTA at the moment); here is a link to the GB OTA thanks to con247: http://forum.xda-developers.com/sho...uide to S-On to restore that too if you wish.
PhantasmRezound said:
http://forum.xda-developers.com/showthread.php?p=25165453
Assuming you have done the HTC Dev unlock, you must do S-off and follow the guide here to get back to reading "Locked" and "S-on" simultaneously.
Edit: Ok, so I see you are S-off at the moment, you are going to want to backup all your data in your custom recovery if you haven't done so already (still on CWM or got that straightened out?)
Going to download the latest official RUU available (the GB OTA at the moment) and have it handy; here is a link to the GB OTA thanks to con247: http://forum.xda-developers.com/showthread.php?p=22045045
Now make sure your bootloader is Locked before running the RUU. Check this and be certain; have to do a bit of extra work if it isn't, so please say you didn't Dev Unlock again after doing S-off lol. (I did this. Had to repeat the whole S-off process to achieve a "Locked" message ultimately. Not fun.)
Ok, after making sure bootloader is Locked... Running that RUU should put the stock hboot back on, verify that after the process. And remeber to turn USB Debugging back on in the stock ROM after running that RUU lol . Then proceed with the guide on the same computer you got all those Dev tools on from doing S-off.
Click to expand...
Click to collapse
If I remember correctly if it's a patched hboot and not the stock hboot your not supposed relock it because you can brick that way. Since the phone is S-OFF just running the GB RUU will be fine then just factory reset from hboot after the RUU finishes and your good to go. Also it's ok to keep it S-OFF because some phones come stock that way but if you really want you can run the command to get S-ON.
Sent from my ICS Rezound
LakerStar25 said:
If I remember correctly if it's a patched hboot and not the stock hboot your not supposed relock it because you can brick that way. Since the phone is S-OFF just running the GB RUU will be fine then just factory reset from hboot after the RUU finishes and your good to go. Also it's ok to keep it S-OFF because some phones come stock that way but if you really want you can run the command to get S-ON.
Sent from my ICS Rezound
Click to expand...
Click to collapse
Yes, this. Didn't mean to suggest actually trying to Relock your phone post S-off. That would definitely be bad if you accepted the JuopunutBear hboot or flashed the Engineer one instead of Stock hboot.
So in any case, you should go ahead and run the RUU after backing up data, do the factory reset, and follow through with turning the security flag to ON if you're wanting the full original state (though Verizon almost certainly won't check or care, and the next user mostly benefits from S-off)
((Sorry, I was just thinking how I jumped the whole gun the hour after JuopunutBear came out. Kept my stock hboot before anybody knew why the process was wanting to push that patched hboot to the phone lol. I used the Dev unlock procedure again *after* S-off. So, at this point I would have to do this process twice to get the same result, to first get a plain Locked status by running the RUU and doing the S-off procedure again... then RUU and do S-on too. Totally forgot those custom JB hboots will say "JuopunutBear" instead of whatever lock status it may be. Edited original post.))
PhantasmRezound said:
Yes, this. Didn't mean to suggest actually trying to Relock your phone post S-off. That would definitely be bad if you accepted the JuopunutBear hboot or flashed the Engineer one instead of Stock hboot.
So in any case, you should go ahead and run the RUU after backing up data, do the factory reset, and follow through with turning the security flag to ON if you're wanting the full original state (though Verizon almost certainly won't check or care, and the next user mostly benefits from S-off)
((Sorry, I was just thinking how I jumped the whole gun the hour after JuopunutBear came out. Kept my stock hboot before anybody knew why the process was wanting to push that patched hboot to the phone lol. I used the Dev unlock procedure again *after* S-off. So, at this point I would have to do this process twice to get the same result, to first get a plain Locked status by running the RUU and doing the S-off procedure again... then RUU and do S-on too. Totally forgot those custom JB hboots will say "JuopunutBear" instead of whatever lock status it may be. Edited original post.))
Click to expand...
Click to collapse
Cool I was just trying to help out lol.
Sent from my ICS Rezound
I successfully installed Fresh Evo LTE 5.3.1 on my phone.
One of the suggestions is to update the Radio but I'm having a tough time doing that.
Here are my specs:
HBOOT 1.15.0000
S-ON
FreshEVO 5.3.1 ROM
I went to the link from the FreshEVO LTE 5.3.1 page to update the radio and have tried the following to install the Radio:
Attempt 1
Downloaded the Full Firmware zip file
Rename it "PJ75IMG"
Place it in the root of my SD card
Reboot into Bootloader
The PJ75IMG.zip file is detect but I only get 'Parsing PJ75IMG.zip' and then the Fastboot, Recovery, etc. options are displayed.
Attempt 2
From the same page where I downloaded the Full Firmware zip file, I also tried:
Download the Boot.img Only (signed) file
Flash it through the command prompt while in Fastboot ("fastboot flash boot boot.img")
Go into Bootloader
The PJ75IMG.zip is detected but still get the "Parsing..." message and nothing else happens.
Attempt 3
I have also tried going into my TWRP recovery and installing the Full Firmware zip AND the Radio 1.12.11.0809 Only.zip file but the installation fails.
Any pointers or a link to a video or a post would be much appreciated.
Thanks and sorry if this is a duplicate post but I really couldn't find any post that showed step-by-step process.
revert to stock and accept the ota, you can then fastboot recovery again and reflash. hboot 1.15 can not directly flash any firmware
edit: you may have to relock your hboot but ive seen users state they didnt. if you decide to relock the phone you will have to unlock the bootloader again to enable fastboot
om4 said:
The easiest way to update your firmware is to revert to stock and accept the ota, you can then fastboot recovery again and reflash
Click to expand...
Click to collapse
I don't have my stock backup anymore.
I've heard stuff about using RUU or something like that. Any quick guide on how to revert back to stock?
DO NOT UNROOT TO ACCEPT THE OTA OR RUU
I'd highly suggest just staying with your current radios and waiting for S-OFF before trying to update the radios. You can still flash the new ROMS in the meantime
You cannot update radios or firmware with Hboot 1.15 or 1.19------->Thats why it is suggested and not required
Rxpert said:
DO NOT UNROOT TO ACCEPT THE OTA OR RUU
I'd highly suggest just staying with your current radios and waiting for S-OFF before trying to update the radios. You can still flash the new ROMS in the meantime
You cannot update radios or firmware with Hboot 1.15 or 1.19------->Thats why it is suggested and not required
Click to expand...
Click to collapse
Thanks for the warning.
Since I'm pretty new to all this, I'll play it safe and stick to what I have.
sorry guys internet crapped out and i got stuck trying to post lol. rxpert has a point but with so much negativity about s-off never coming I'm starting to consider taking the OTA.
also you should always have a back up, its your go to solution when nothing else seems to be working since its a back up of when everything was new and working be it stock or custom
The new radios aren't worth losing the possibility, no matter how small
Sent from my EVO using Tapatalk 2
True...
om4 said:
sorry guys internet crapped out and i got stuck trying to post lol. rxpert has a point but with so much negativity about s-off never coming I'm starting to consider taking the OTA.
also you should always have a back up, its your go to solution when nothing else seems to be working since its a back up of when everything was new and working be it stock or custom
Click to expand...
Click to collapse
Just so I am clear, I too am 1.5 so if have my orginal rom, (the one after I unlocked my bootloader) i can restore it and accept the OTA without having to relock my phone? (it wont brick):good: Or do i have some other steps to take, I read the don't panic instructions, but it only mentioned what the OTA does ( relocks with a new rom) but nothing about what happens if I don't relock before I accept the OTA, I know i seem a bit slow, 4g lte isn't as interesting as OG 4g without S-off.
RamesisX said:
Just so I am clear, I too am 1.5 so if have my orginal rom, (the one after I unlocked my bootloader) i can restore it and accept the OTA without having to relock my phone? (it wont brick):good: Or do i have some other steps to take, I read the don't panic instructions, but it only mentioned what the OTA does ( relocks with a new rom) but nothing about what happens if I don't relock before I accept the OTA, I know i seem a bit slow, 4g lte isn't as interesting as OG 4g without S-off.
Click to expand...
Click to collapse
I havent yet done it myself but users have said they didnt need to relock, how ever as captain said there is no real need to update right now. If you decide to go ahead it would be a good idea to relock ( fastboot oem lock ) just to make sure, you can unlock afterwards. I neglect to mention this in my guide because most phones now are on 1.19 anyway and those still on 1.15 are holding out for soff
You will want to have the stock recovery to take the ota. Most people do this by relocking and running the ruu
Once again, I'm providing the info but I don't recommend it
Sent from my EVO using Tapatalk 2
Rxpert said:
You will want to have the stock recovery to take the ota. Most people do this by relocking and running the ruu
Once again, I'm providing the info but I don't recommend it
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I am still researching how to relock without issues. I have my orginal rom but still leary about the entire relocking process. I was hoping i could restore to orginal sense rom, then take the OTA. otherwise I am looking for the simplest way to accompish the relocking task, but frankly nothing is easy when i comes to playing around with 4g lte, except it is rather difficult to brick. With my luck i might succeed in that LMAO
:good::laugh:
RamesisX said:
I am still researching how to relock without issues. I have my orginal rom but still leary about the entire relocking process. I was hoping i could restore to orginal sense rom, then take the OTA. otherwise I am looking for the simplest way to accompish the relocking task, but frankly nothing is easy when i comes to playing around with 4g lte, except it is rather difficult to brick. With my luck i might succeed in that LMAO
:good::laugh:
Click to expand...
Click to collapse
there is no simpler method for relocking hboot, simply fastboot oem lock
om4 said:
there is no simpler method for relocking hboot, simply fastboot oem lock
Click to expand...
Click to collapse
Used that and it worked great.
Evo 4G LTE
h-boot 1.19, s-on, HTCDev unlocked
For returning purposes, how can i return my phone back to stock? Lets just say i want to go back to a stock rom and i want to install the official ICS sprint update. I no longer wish to have a rooted phone because its been going haywire on me lately (ROMs keep going unstable).
Long story short, i guess im done with rooting this phone and i dont know how do i go about returning to stock conditions. Do i need to download a RUU or are there any stock sprint .zips i can flash via recovery? Dont really what to do with RUUs. I know i can just relock it later
EDIT: im on 2.89 base and hboot 1.5 ON via HTC Unlock
All you have to do is download the latest ruu. Which is the ics 35 s 2.89 file that's found in the development section. Relock your bootloader first. Then rename ruu to PG86IMG in all caps and place it on the root of your sdcard. Power down your phone and boot into bootloader. Your phone should then detect it and ask to update your phone. Hit yes and let your phone finish updating. You'll be back on unrooted stock with stock everything.
Please hit the thank you button if I helped you in anyway. It's free.
Jsparta26 said:
All you have to do is download the latest ruu. Which is the ics 35 s 2.89 file that's found in the development section. Relock your bootloader first. Then rename ruu to PG86IMG in all caps and place it on the root of your sdcard. Power down your phone and boot into bootloader. Your phone should then detect it and ask to update your phone. Hit yes and let your phone finish updating. You'll be back on unrooted stock with stock everything.
Click to expand...
Click to collapse
He said he's S-ON so he won't be able to flash the RUU.zip from the bootloader. It's an addition he made right away because there's no timestamp for an edit on his post.
With S-ON, relock the bootloader (fastboot oem lock) and run the RUU.exe from Windows.
We all make mistakes at times, so please don't be so harsh with others on this forum, especially the new users.
ramjet73
ramjet73 said:
He said he's S-ON so he won't be able to flash the RUU.zip from the bootloader. It's an addition he made right away because there's no timestamp for an edit on his post.
With S-ON, relock the bootloader (fastboot oem lock) and run the RUU.exe from Windows.
We all make mistakes at times, so please don't be so harsh with others on this forum, especially the new users.
ramjet73
Click to expand...
Click to collapse
Thanks alot! i couldnt find a .exe but i found a.zip for 2.17 RUU... so i lock the bootloader then how do i "flash" this zip?
Razpr said:
Thanks alot! i couldnt find a .exe but i found a.zip for 2.17 RUU... so i lock the bootloader then how do i "flash" this zip?
Click to expand...
Click to collapse
Look here: http://forum.xda-developers.com/showthread.php?p=19089387
Imagika FTW... with Tapatalk 2
You can't flash the zip if you are S-ON. Use coal's link to download the RUU.exe.
Sent from my PG86100 using Tapatalk 2
ramjet73 said:
He said he's S-ON so he won't be able to flash the RUU.zip from the bootloader. It's an addition he made right away because there's no timestamp for an edit on his post.
With S-ON, relock the bootloader (fastboot oem lock) and run the RUU.exe from Windows.
We all make mistakes at times, so please don't be so harsh with others on this forum, especially the new users.
ramjet73
Click to expand...
Click to collapse
I don't think I was harsh at all. The reason I gave him that solution is from my own experience. Back when I was on gb unlocked. There were a few times I had to relock and go back to stock gb so I relocked my bootloader and ran the ruu file from my bootloader with success everytime. Honestly if my post sounded harsh it wasn't intentionally. I am certainly not questioning anybodies knowledge at all. You guys have been around longer than I have. This piece of information is new to me because I never had to run ruu.exe from a pc. Im am thankful you came in and shed some light. I was just trying to offer a solution. That's all. But thank you for teaching me something new.
Jsparta26 said:
I don't think I was harsh at all. The reason I gave him that solution is from my own experience. Back when I was on gb unlocked. There were a few times I had to relock and go back to stock gb so I relocked my bootloader and ran the ruu file from my bootloader with success everytime. Honestly if my post sounded harsh it wasn't intentionally. I am certainly not questioning anybodies knowledge at all. You guys have been around longer than I have. This piece of information is new to me because I never had to run ruu.exe from a pc. Im am thankful you came in and shed some light. I was just trying to offer a solution. That's all. But thank you for teaching me something new.
Click to expand...
Click to collapse
Actually, it really depends on the source of the RUU.zip. If it was extracted from the RUU.exe and properly signed by HTC it should work flashed through the bootloader with S-ON, but if it is modified in any way (like removing the bootloader) it will fail with S-ON. The RUU.exe is always safer for S-ON users. There were "RUU.zip" files circulating at the time of the VM leak that had all the firmware removed.
I really didn't mean your answers in this thread, but in this forum in general. As someone else pointed out, we were all new at this at some point, and it's better to not answer if you are concerned about someone asking the same question that's been answered many times before, or give the answer but point out that it could have easily been found with a search.
ramjet73
I searched for this and could not find an easy way to get an answer.
So I recently achieved S-OFF. In doing so I reverted back to an ICS RUU(3.14.605.12) after relocking the phone. After I got the phone back up and running I then set things up to run the program needed for S-OFF. Got S-OFF. Then unlocked the phone and flashed a rom I wanted.
I am thinking I would like to install the latest RUU(4.03.605.2) to get the radios and everything up to date.
Main question. Would installing the newer RUU affect the S-OFF status at all? I would hope no, but I don't know.
Second question. Do I need to go through the process of relocking the phone?
Sax1031 said:
I searched for this and could not find an easy way to get an answer.
So I recently achieved S-OFF. In doing so I reverted back to an ICS RUU(3.14.605.12) after relocking the phone. After I got the phone back up and running I then set things up to run the program needed for S-OFF. Got S-OFF. Then unlocked the phone and flashed a rom I wanted.
I am thinking I would like to install the latest RUU(4.03.605.2) to get the radios and everything up to date.
Main question. Would installing the newer RUU affect the S-OFF status at all? I would hope no, but I don't know.
Second question. Do I need to go through the process of relocking the phone?
Click to expand...
Click to collapse
The newest RUU will not effect your s-off. It will relock the bootloader, however. The only thing that this changes is the fact that you won't be able to issue fastboot commands. You can unlock with Vinylfreak's method or through htc dev again, but I find either of these to be unnecessary with s-off. You will not need to re-lock with s-off to run the ruu. Just place it on your sd card, flash in hboot, and you're good to go. Make sure after you flash the RUU to find a zip of Amon-Ra 3.15 that you can flash via hboot. Good luck!
Just to be clear. You WILL retain s-off after flashing RUU.
iamwalterwhite said:
The newest RUU will not effect your s-off. It will relock the bootloader, however. The only thing that this changes is the fact that you won't be able to issue fastboot commands. You can unlock with Vinylfreak's method or through htc dev again, but I find either of these to be unnecessary with s-off. You will not need to re-lock with s-off to run the ruu. Just place it on your sd card, flash in hboot, and you're good to go. Make sure after you flash the RUU to find a zip of Amon-Ra 3.15 that you can flash via hboot. Good luck!
Click to expand...
Click to collapse
Yea I have Amon-Ra 3.15 ready to go. Will do later on today.
Thank you.
Sax1031 said:
Yea I have Amon-Ra 3.15 ready to go. Will do later on today.
Thank you.
Click to expand...
Click to collapse
You're welcome. The AR 3.15 that you flashed through fastboot when you were setting up your phone doesn't work in hboot (just so you're aware). I don't want to be a broken record, I just want to make sure that you have everything you need. In this thread: http://forum.xda-developers.com/showthread.php?t=1615969 there is an hboot flashable of AR 3.15 in the op. It may also be useful if you have any problems after s-off.
After you achieve s-off you don't need to unlock again, even though the boot loader says that it's locked you still have access to everything. Once you are S-off you no longer need to relock to flash RUUs. From what I've seen it's not recommended to unlock via htcdev if you are s-off, I'm not sure of the reason though. To regain access to fast boot commands all you have to do is flash an unlocked/modified hboot. There is a thread in the dev section called "hex edited hboots" just download the ph from there and flash it via hboot.
brando56894 said:
After you achieve s-off you don't need to unlock again, even though the boot loader says that it's locked you still have access to everything. Once you are S-off you no longer need to relock to flash RUUs. From what I've seen it's not recommended to unlock via htcdev if you are s-off, I'm not sure of the reason though. To regain access to fast boot commands all you have to do is flash an unlocked/modified hboot. There is a thread in the dev section called "hex edited hboots" just download the ph from there and flash it via hboot.
Click to expand...
Click to collapse
The reason it's not recommended is because if you do, you'll get the relocked message if you lock again. If you don't unlock again, you'll have "locked" just like stock.
Sent from my Rezound using Tapatalk 2