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'm on 3.14 stock ruu, unlocked bootloader, amonra in the recovery
do I need to flash something like the "3.14 stock deodexxed root"
or can I just finally try to s-off?
thanks <3
Watercycle said:
I'm on 3.14 stock ruu, unlocked bootloader, amonra in the recovery
do I need to flash something like the "3.14 stock deodexxed root"
or can I just finally try to s-off?
thanks <3
Click to expand...
Click to collapse
the su binary MUST be present in the system for the S-OFF process to work correctly, so yes, you must root.
Since you have Amon ra installed, just boot into that, go to the developer menu and install the su binary, then do S-OFF
a.mcdear said:
the su binary MUST be present in the system for the S-OFF process to work correctly, so yes, you must root.
Since you have Amon ra installed, just boot into that, go to the developer menu and install the su binary, then do S-OFF
Click to expand...
Click to collapse
unguarded or super user? and thank you i didn't know about that =)
Watercycle said:
unguarded or super user? and thank you i didn't know about that =)
Click to expand...
Click to collapse
Sueperuser not unguarded
this is the most rediculous process ever! (currently trying to wire trick) I'VE USED 2 DARN TYPES OF WIRE AND A PAPERCLIP AND NONE OF THEM DO ANYTHING
oh god, whew... i was running around the house making a wire out of everything...
but after trying the paperclip for like the 8th time (which took a half hour to find) it seems to have worked
S-off is the most stressful android activity ever >XO
thanks you two <3
You did use the ics jb hboot right? Make sure you can see the sd card? And don't unlock your phone again. You would need to s-on then s-off again for it to say locked. I just woke up and saw your new posts, its been a long day but I see you got help. Welcome to the club, glad it finally worked.
sent from my Clean Rezound
I used the Hboot that came with 3.14 Ruu, if S-off took the "relocked" away then i'm happy, if it didn't, oh well, but I was unlocked when I started the process =o
As long as you don't unlock it after s-off, it will be locked again ( although it says "juopunutbear" instead of "locked" if you're using their modified boot. Just flash a stock one and it will say locked)
I'm still not to sure why people keep bringing up the Hboot, is it because if you flash S-off's it will break it?
I declined the modified version and everything appears to be working
Watercycle said:
I'm still not to sure why people keep bringing up the Hboot, is it because if you flash S-off's it will break it?
I declined the modified version and everything appears to be working
Click to expand...
Click to collapse
The patched hboot adds some advanced fast boot commands. However everything will work without the patched hboot. You don't need it its just nice to have
Watercycle said:
I'm still not to sure why people keep bringing up the Hboot, is it because if you flash S-off's it will break it?
I declined the modified version and everything appears to be working
Click to expand...
Click to collapse
The juoponut bear hboot is an eng hboot that allows for adb commands and other options most people will not need.
The h boot issue is thus......in the event you want your phone returned to stock (s on and locked in downloader), after gaining s off do NOT HTC unlock the phone.
If you don't unlock it and want to return to stock you basically run a ruu, and then write the secure flag back to s on (scotty123 has a thread how to do this). After which point you phone will be on stock Rom, recovery and h boot will say locked and s on. Just like the day you first got the phone.
If you unlock after s off (as an early adopter I did) your bootloader will only say unlocked or relocked. You can run ruus, and write secure flag to s on.....BUT your hboot will say relocked or unlocked. And to a trained eye, someone can tell you tampered with it (running Roma,etc)
In my case, I had to follow scottys thread, s on, and do the s off process all over again. Early on we thought flashing a ruu would change the hboot status from relocked to locked. However we were mistaken.
So, don't unlock after s off.
If you can't run adb commands with your h boot and don't want to flash an eng hboot, use the ph98img.zip method to flash things (ex recovery, hboots, radios).
Sent from my Rezound
ericsignals said:
The juoponut bear hboot is an eng hboot that allows for adb commands and other options most people will not need.
The h boot issue is thus......in the event you want your phone returned to stock (s on and locked in downloader), after gaining s off do NOT HTC unlock the phone.
If you don't unlock it and want to return to stock you basically run a ruu, and then write the secure flag back to s on (scotty123 has a thread how to do this). After which point you phone will be on stock Rom, recovery and h boot will say locked and s on. Just like the day you first got the phone.
If you unlock after s off (as an early adopter I did) your bootloader will only say unlocked or relocked. You can run ruus, and write secure flag to s on.....BUT your hboot will say relocked or unlocked. And to a trained eye, someone can tell you tampered with it (running Roma,etc)
In my case, I had to follow scottys thread, s on, and do the s off process all over again. Early on we thought flashing a ruu would change the hboot status from relocked to locked. However we were mistaken.
So, don't unlock after s off.
If you can't run adb commands with your h boot and don't want to flash an eng hboot, use the ph98img.zip method to flash things (ex recovery, hboots, radios).
Sent from my Rezound
Click to expand...
Click to collapse
Well everything is right but the first part, the modified hboot allows you to perform fastboot commands that would otherwise require you to unlock the bootloader
Fastboot flash, fastboot boot... Etc.
Sent from my ADR6425LVW using Tapatalk 2
superchilpil said:
Well everything is right but the first part, the modified hboot allows you to perform fastboot commands that would otherwise require you to unlock the bootloader
Fastboot flash, fastboot boot... Etc.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Forgot to add that part when I typed the adb part ....thanks for correcting me.:thumbup:
Sent from my Rezound
oh dear, so without that Hboot command prompt won't be able to fastboot into recovery and whatnot?
Watercycle said:
oh dear, so without that Hboot command prompt won't be able to fastboot into recovery and whatnot?
Click to expand...
Click to collapse
Yes, but there are ways around that
I personally just package my own ph98img.zips if I need to flash a kernel or recovery after doing something dumb
Sent from my ADR6425LVW using Tapatalk 2
If you want to add the JB Hboot, it is very simple. You can go to their site and just download the most recent hboot. You must know if you are ICS or GB. But go here: http://unlimited.io/hboot-downloads/ and download the right one, either vigor ics or vigor gb. Put that in the folder where you had put the original controlbear program and follow these instructions:
To flash the JuopunutBear hboots
Put the phone in fastboot mode, connected to the pc and enter the following commands
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip
Thats all there is to it and you can now benefit from the JB Hboot.
I thought you needed to be unlocked with htc dev to gain s-off? Now I'm hearing that I should not unlock my phone before I s-off?
Yes you need to be unlocked. It's part of the prerequisites. Please read then reread the thread in general "s-off with instructions...it's official". Understand how to avoid problems and fix them if they arise. It's very easy but it's like people half ass reading the instructions recently. Don't be that person.
sent from my Clean Rezound
th3rapist said:
I thought you needed to be unlocked with htc dev to gain s-off? Now I'm hearing that I should not unlock my phone before I s-off?
Click to expand...
Click to collapse
You have to unlock befor you s off, afterwards it's redundant to do so. But some people have
Sent from my ADR6425LVW using Tapatalk 2
doubleshot, ruby ICS, vigor ICS, holiday ICS, pyramid ICS?
which one? haha
I don't mind don't 1 more small flash that will probably be necessary in the future as long as it doesn't screw my current rom up
Alright guys, I've searched and searched and I think I have it all down, just want to lay out my steps and get verification.
I'm on T-Mo ICS, not from OTA, flashed myself
Root
S-Off
4-Ext
I'm sending my phone in and need to go back to stock. I think I would prefer to go back to GB so it's just like from factory with no OTA.
- Download the Stock GB RUU from here - HTC Ruby/Amaze 4G Stock ROMs
- The RUU I want is - PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC _30.66.550L.08D_release_228638_signed
- Following These Directions I connect via ADB and fastboot oem lock This will show it as Re-Locked, correct?
- Reboot
- Flash the stock RUU I got by placing it in the root of my external sd card and renaming it PH85IMG.zip and rebooting to bootloader. Which is Volume Down + Power? Can someone verify that?
- Then I set the security lock by doing "fastboot oem writesecureflag 3" - This will change the bootloader to show locked, not re-locked, correct? I thought you had to have root to ADB?
At that point I'm back as if I took the phone out of the box for the first time? 4ext will be replaced with Stock Recovery? Thanks in advance. Like I said, I've searched, but there are many conflicting reports. :good:
Minker17 said:
Alright guys, I've searched and searched and I think I have it all down, just want to lay out my steps and get verification.
I'm on T-Mo ICS, not from OTA, flashed myself
Root
S-Off
4-Ext
I'm sending my phone in and need to go back to stock. I think I would prefer to go back to GB so it's just like from factory with no OTA.
- Download the Stock GB RUU from here - HTC Ruby/Amaze 4G Stock ROMs
- The RUU I want is - PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC _30.66.550L.08D_release_228638_signed
- Following These Directions I connect via ADB and fastboot oem lock This will show it as Re-Locked, correct?
- Reboot
- Flash the stock RUU I got by placing it in the root of my external sd card and renaming it PH85IMG.zip and rebooting to bootloader. Which is Volume Down + Power? Can someone verify that?
- Then I set the security lock by doing "fastboot oem writesecureflag 3" - This will change the bootloader to show locked, not re-locked, correct? I thought you had to have root to ADB?
At that point I'm back as if I took the phone out of the box for the first time? 4ext will be replaced with Stock Recovery? Thanks in advance. Like I said, I've searched, but there are many conflicting reports. :good:
Click to expand...
Click to collapse
In order to flash the factory RUU you need to be either locked or relocked. Then when you flash the factory RUU it should overwrite your hboot which will reset from "relocked" to "locked" then the writesecureflasg function will turn S-ON and you'll be factory.
freakasis said:
In order to flash the factory RUU you need to be either locked or relocked. Then when you flash the factory RUU it should overwrite your hboot which will reset from "relocked" to "locked" then the writesecureflasg function will turn S-ON and you'll be factory.
Click to expand...
Click to collapse
If you're s-off you don't need to lock or relock to flash a stock ruu.
Sent from my SGH-T999 using xda app-developers app
Dark Nightmare said:
If you're s-off you don't need to lock or relock to flash a stock ruu.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Guess that does make sense, huh?
But everything looks OK then?
Update - Downloaded and renamed the RUU, rebooted into recovery and installed everything. Bootloader shows locked and I went ahead and did the ICS Update. Everything is back to factory and I'm ready to send it back.
Final Steps
Minker17 said:
Update - Downloaded and renamed the RUU, rebooted into recovery and installed everything. Bootloader shows locked and I went ahead and did the ICS Update. Everything is back to factory and I'm ready to send it back.
Click to expand...
Click to collapse
Rick. Like you, I want to bring my T-Mobile HTC Amaze back to stock so that I can upgrade to ICS. The phone was bought on eBay with GB and a custom rom. I'd like to follow your steps but it had a lot of question marks and/or needed confirmation. Will you post exactly what you did?
Your steps seems a lot easier than what I've been researching. Is it really that simple? It makes sense. Everyone else uses hasoon2000 toolkit. Thanks for your time!
TheCount01 said:
Rick. Like you, I want to bring my T-Mobile HTC Amaze back to stock so that I can upgrade to ICS. The phone was bought on eBay with GB and a custom rom. I'd like to follow your steps but it had a lot of question marks and/or needed confirmation. Will you post exactly what you did?
Your steps seems a lot easier than what I've been researching. Is it really that simple? It makes sense. Everyone else uses hasoon2000 toolkit. Thanks for your time!
Click to expand...
Click to collapse
You don't need to go back to stock you just need to download the factory ics ruu or a rom that stock like. The hasoon toolkit is more of a guide to help you with the process try to read it an maybe you can rom your cell with a better one!
Sent from my HTC_Amaze_4G using xda app-developers app
S-off
FutureAirways said:
You don't need to go back to stock you just need to download the factory ics ruu or a rom that stock like. The hasoon toolkit is more of a guide to help you with the process try to read it an maybe you can rom your cell with a better one!
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Thanks for your reply. That makes sense, too. Plus, it'll save me a step. I'm new to Android and got a lot to learn. With the help of xda-developers, I've learned a lot these past three weeks.
From what I've been reading, it's apparent that I need to have S-off before I do any flashing. Like I mentioned, I bought the phone with a custom rom. I'm guessing if it has a custom rom, then it was S-off at one time. If so, I should be able to S-off easily. Since I didn't flash the phone, I'm not sure what program is installed. Your knowledge and experience will be greatly appreciated if you can tell me if I'm able to S-off easily and how. Whenever I go into HBOOT I see the following:
***UNLOCKED***
RUBY PVT SHIP S-ON RL
HBOOT-1.90.0008
eMMC-boot
FASTBOOT
<vol up> to previous item
<vol Down> to next item
<Power>
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Hey guys. Yes I have searched, but have only found instructions so far for going back to stock gingerbread.
I need to send my amaze in to get fixed under warranty, and I'm assuming they won't like it if I send them the phone with an unlocked bootloader, rooted, and CM10 installed, and that's what I need help with. How can I reinstall stock ICS, unroot, and lock the bootloader of the amaze? And will it show as "relocked" or "locked"? Of course I plan on putting the root and unlocked bootloader and CM10 once I get it back, so I'm looking for a reversible way to do this. Thanks in advance!
Just to be clear. For your bootloader to say 'locked' you'll need to have S-Off and NOT unlock the bootloader again. But once that's done just flash the ICS ruu. Here's a link
http://forum.xda-developers.com/showthread.php?t=1647728
Double0EK said:
Just to be clear. For your bootloader to say 'locked' you'll need to have S-Off and NOT unlock the bootloader again. But once that's done just flash the ICS ruu. Here's a link
http://forum.xda-developers.com/showthread.php?t=1647728
Click to expand...
Click to collapse
Thank you. So I am S-ON right now. In order to make the bootloader say "locked" again to make HTC happy with my warranty, I'd have to be stuck with ICS and whatever updates HTC decides to give us from then on once I got it back from HTC?
No. That's the only way for it to say "locked" if you relock it it will say "relocked"
So if you really want it to say "locked" you'll need to S-Off first. Then flash the RUU.
Once you get it back you can do as you feel.
bruner1981 said:
Thank you. So I am S-ON right now. In order to make the bootloader say "locked" again to make HTC happy with my warranty, I'd have to be stuck with ICS and whatever updates HTC decides to give us from then on once I got it back from HTC?
Click to expand...
Click to collapse
What makes you think you will be stuck with anything? Everything u need to do is reversible and then re-doable.
Im just not really sure which part u think would make it stuck. Let us know and im sure we can explain the cofusion
After unlocking the bootloader with S-ON and installing a custom recovery/rom how do you revert to Stock.
I've tried relocking the bootloader, and using the AllinOneToolkit by Hanson to install the Factory RUU but it keeps failing after the HTC boot logo appears and the zip RUU file gets transferred to the phone. Keeps saying Failed with 12 signatures or something.
Then I read with S-ON that you had to use Hanson's tool and perform Fix Mainver, but that doesnt do anything either. Keeps saying, error cannot find device.
So, how do I go back to Stock?
Would appreciate any help!
Boot into fastboot, type "fastboot OEM lock" in the command prompt. Put the appropriate RUU on your external SD card and rename it PH85ING.zip and boot into bootloader.
Edit: its PH85IMG.zip. sorry about my fatty fingers. Also, make sure to check the md5 sum on the RUU. I always had trouble with the download.
Sent from my HTC Ruby using xda app-developers app
fubag said:
After unlocking the bootloader with S-ON and installing a custom recovery/rom how do you revert to Stock.
I've tried relocking the bootloader, and using the AllinOneToolkit by Hanson to install the Factory RUU but it keeps failing after the HTC boot logo appears and the zip RUU file gets transferred to the phone. Keeps saying Failed with 12 signatures or something.
Then I read with S-ON that you had to use Hanson's tool and perform Fix Mainver, but that doesnt do anything either. Keeps saying, error cannot find device.
So, how do I go back to Stock?
Would appreciate any help!
Click to expand...
Click to collapse
Fails after htc boot logo? If you are flashing an RUU, you should never see any boot screen until after its done flashing. What carrier are you on and what steps exactly r u fillowing to flash the ruu...?
aj_2423 said:
Fails after htc boot logo? If you are flashing an RUU, you should never see any boot screen until after its done flashing. What carrier are you on and what steps exactly r u fillowing to flash the ruu...?
Click to expand...
Click to collapse
its not the actual boot logo but that black screen with the HTC logo that I think is part of the stocky recovery maybe?
I have yet to try the PHS.IMG method in fastboot.
Thanks for the help!
fubag said:
its not the actual boot logo but that black screen with the HTC logo that I think is part of the stocky recovery maybe?
I have yet to try the PHS.IMG method in fastboot.
Thanks for the help!
Click to expand...
Click to collapse
Lol what do you mean you havent tried it? Flashing the PH85IMG.zip though the bootloader is the ONLY way to flash the RUU.
If you are on tmo follow this
http://forum.xda-developers.com/showthread.php?p=24294337
Sent from my
aj_2423 said:
Lol what do you mean you havent tried it? Flashing the PH85IMG.zip though the bootloader is the ONLY way to flash the RUU.
If you are on tmo follow this
http://forum.xda-developers.com/showthread.php?p=24294337
Sent from my
Click to expand...
Click to collapse
This only applies to tmobile versions? What about if we are on another carrier, I tried renaming the OTA updates but it doesnt do anything.
fubag said:
This only applies to tmobile versions? What about if we are on another carrier, I tried renaming the OTA updates but it doesnt do anything.
Click to expand...
Click to collapse
noo it has nothing to do with what carrier you're using at the moment...