I did Bootloader unlock using the code fron HTEDev, and it showed "Unlocked" . Then I flashed 4Ext recovery and unrooted. However, when I did "S-off", the bootloader shows"Locked" again with the text "S-off".
Anyone have the same issue? Should I do the unlock again using the code? or I can just ignore it and go ahead install other custome ROM.
Edit: Educated by dark nightmare.
Sent from my HTC Vision using xda app-developers app
Just unlock it back using the unlock file you got.
Would unlocking again serve any real purpose?
Sent from my HTC Vision using xda app-developers app
death4u said:
Would unlocking again serve any real purpose?
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
Leave it locked and you'll see, .
sent from a galaxy you'll never see.
Dark Nightmare said:
Just unlock it back using the unlock file you got.
Click to expand...
Click to collapse
I have several questions here:
1. Is my bootloader re-locked after S-off, or it is still unlocked but just show a Irrelevant text " locked" ?
2. How could I check if the real bootloader's status: "Locked" or Unlocked", not just from the text show in the fastboot page?
2. If the "bootloader is relocked", it should show "Relocked", not "Locked", isn't it?.
3. If it IS re-locked and I don't re-unlock it, will it affect the installation of custom ROM?
If the "Locked" after S-off does not affect the installation of custom ROM, I would like to leave it that way which will be easy to roll back to complete stock for warranty.
Brightxda said:
I have several questions here:
1. Is my bootloader re-locked after S-off, or it is still unlocked but just show a Irrelevant text " locked" ?
2. How could I check if the real bootloader's status: "Locked" or Unlocked", not just from the text show in the fastboot page?
2. If the "bootloader is relocked", it should show "Relocked", not "Locked", isn't it?.
3. If it IS re-locked and I don't re-unlock it, will it affect the installation of custom ROM?
If the "Locked" after S-off does not affect the installation of custom ROM, I would like to leave it that way which will be easy to roll back to complete stock for warranty.
Click to expand...
Click to collapse
It is locked you need to un lock it again so you can flash custom recovery
sent from my NRGized Amaze,
powered by faux kernel v.16
aj_2423 said:
It is locked you need to un lock it again so you can flash custom recovery
sent from my NRGized Amaze,
powered by faux kernel v.16
Click to expand...
Click to collapse
If he had a custom recovery before s-off it's still there, but you see the thing about "locked" or "relocked" bootloaders people don't understand is that even with s-off, once it's locked, writing anything at all isn't possible via custom recoveries, that itself is the first level of security we bypass to customize our devices.
By the way to the op, it is currently locked the way it was before you unlocked via htcdev, not relocked, that text on the hboot is the verification.
sent from a galaxy you'll never see.
Dark Nightmare said:
If he had a custom recovery before s-off it's still there, but you see the thing about "locked" or "relocked" bootloaders people don't understand is that even with s-off, once it's locked, writing anything at all isn't possible via custom recoveries, that itself is the first level of security we bypass to customize our devices.
By the way to the op, it is currently locked the way it was before you unlocked via htcdev, not relocked, that text on the hboot is the verification.
sent from a galaxy you'll never see.
Click to expand...
Click to collapse
Thank you all very much for clearing my questions. I will unlock it again.
One more question: How could it relocked during the S-off? Is it the normal thing for all of S-off or it just happens in a few cases?
Brightxda said:
Thank you all very much for clearing my questions. I will unlock it again.
One more question: How could it relocked during the S-off? Is it the normal thing for all of S-off or it just happens in a few cases?
Click to expand...
Click to collapse
It happens to all of us, once you don't install JB hboot after s-off it locks your bootloader, I guess the entire process resets a few security levels since it turns the main security lock off.
Dark Nightmare said:
It happens to all of us, once you don't install JB hboot after s-off it locks your bootloader, I guess the entire process resets a few security levels since it turns the main security lock off.
Click to expand...
Click to collapse
You are right. I skipped the last step, installing JB hboot during the S-off. I thought my Amazer came with the new ICS pre-installed which might not need other hboot. It should not be any problem, right?
Brightxda said:
You are right. I skipped the last step, installing JB hboot during the S-off. I thought my Amazer came with the new ICS pre-installed which might not need other hboot. It should not be any problem, right?
Click to expand...
Click to collapse
Na it's just a custom hboot, not needed, you can always flash that or the ENG hboot later if you wanna change your splash screen, that's probably the only thing it's useful for.
Dark Nightmare said:
Na it's just a custom hboot, not needed, you can always flash that or the ENG hboot later if you wanna change your splash screen, that's probably the only thing it's useful for.
Click to expand...
Click to collapse
Thank you again, I reunlocked the bootloader, flashed Energy™ ROM and it works great now.:victory:
Related
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
if my boot loader is unlocked and i i have s-on can i use an ruu to go back to stock?
zebo34 said:
if my boot loader is unlocked and i i have s-on can i use an ruu to go back to stock?
Click to expand...
Click to collapse
No, your going to have yo re-lock.
Sent from my ADR6425LVW using xda app-developers app
To run an RUU, you will need to relock or get S-Off.
If you relock, you will, of course, need to reunlock after the RUU if you want root. If you get S-Off, you will never need to unlock, relock, S-On, or S-Off again.
Max725 said:
To run an RUU, you will need to relock or get S-Off.
If you relock, you will, of course, need to reunlock after the RUU if you want root. If you get S-Off, you will never need to unlock, relock, S-On, or S-Off again.
Click to expand...
Click to collapse
i relocked and now i it says security warning, is that bad
zebo34 said:
i relocked and now i it says security warning, is that bad
Click to expand...
Click to collapse
No. You can ignore that iirc. Someone else can chime in as well, it's been a while for me, but I remember this coming up a long time ago - it happened to me too. It's happened to many people. You just relocked so you're still going to run the RUU? Should go away after you do.
Here's a post with the answer:
http://forum.xda-developers.com/showpost.php?p=22723792&postcount=6
con247 said:
you get a security warning if you are relocked but don't have the official RUU installed. So if you flashed an ICS rom and relocked, the rom would work fine but you would have a security warning because it isn't HTC's official rom.
Click to expand...
Click to collapse
feralicious said:
No. You can ignore that iirc. Someone else can chime in as well, it's been a while for me, but I remember this coming up a long time ago when I used to read everything on this forum, before s-off happened.
Here's a thread about it from April:
http://forum.xda-developers.com/showthread.php?t=1618013&highlight=security+warning
It's happened to many people. You just relocked so you're still going to run the RUU? Should go away after you do.
Click to expand...
Click to collapse
can i run the ruu from hboot?
zebo34 said:
i relocked and now i it says security warning, is that bad
Click to expand...
Click to collapse
Your phone won't boot with the security warning.. you have to run a full ruu now. Yes from hboot name it to PH98IMG and put it on your sd and boot to bootloader. It'll find it automatically and prompt you to run the update.
Sent from my ADR6425LVW using xda app-developers app
zebo34 said:
can i run the ruu from hboot?
Click to expand...
Click to collapse
Yes, as famous said above. (But according to Con you should still be able to boot now. I don't remember if I ever booted with that warning, I doubt it as I was probably relocking just to run the RUU and had no need to boot up.)
I edited my post above, you must have quoted me before that showed up. Once you run the RUU the security warning should be gone, then you can unlock again and flash a custom ROM if you like.
can someone take a look at this and tell me if this device is truly unlocked. it says s-off, but there is no **UNLOCKED** banner at the top of the bootloader.
been through a world of crap with this device and dont want to do it again. Thanks in advance
drlzanej said:
can someone take a look at this and tell me if this device is truly unlocked. it says s-off, but there is no **UNLOCKED** banner at the top of the bootloader.
been through a world of crap with this device and dont want to do it again. Thanks in advance
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1889438&page=3 take a look at this
In other words with s-off an unlocked bootloader is irrelevant unless you still want to flash a recovery through fastboot. You can flash twrp recovery bootloader method, gain root and flash 4ext recovery through the app (highly recommended). Also should you need to have your phone serviced, it is essential to have your phones bootloader in "locked" state.
drlzanej said:
can someone take a look at this and tell me if this device is truly unlocked. it says s-off, but there is no **UNLOCKED** banner at the top of the bootloader.
been through a world of crap with this device and dont want to do it again. Thanks in advance
Click to expand...
Click to collapse
This almost seems like a troll thread lol, The OP is a senior member, with hundreds of thanks and has something to do with Bad Seed Customs, And has an S-off'd device, Asking such a sily question lol
It's all good though, Knowledge for the community [=
drlzanej said:
can someone take a look at this and tell me if this device is truly unlocked. it says s-off, but there is no **UNLOCKED** banner at the top of the bootloader.
been through a world of crap with this device and dont want to do it again. Thanks in advance
Click to expand...
Click to collapse
You can't really tell from the bootloader screen with the engineering hboot installed.
All the custom bootloaders (ENG, Revolutionary, JBear) hide the locked/unlocked/relocked status on the first line of the bootloader screen since they enable the fastboot commands that would normally require unlocking the stock bootloaders. There are two ways to determine the current status:
1. Flash a stock bootloader (1.4, 1.5, 1.58)
2. Run the "query_bootloader.zip" script from this post in recovery
A lot of users get confused about the difference between unlocking the bootloader (hboot S-OFF) and gaining radio S-OFF. I was confused myself until the light went on as explained in this post. It used to be that the only way to get the stock "locked" status back after doing the htcdev unlock was to do the wire trick, but now you can "flash" the "lock_bootloader.zip" file from the post linked in the #2 option above which uses a modified version of update-binary to reset the flag in the firmware.
ramjet73
Can't_Live_Without_My_Evo said:
This almost seems like a troll thread lol, The OP is a senior member, with hundreds of thanks and has something to do with Bad Seed Customs, And has an S-off'd device, Asking such a sily question lol
It's all good though, Knowledge for the community [=
Click to expand...
Click to collapse
ok thatbeing said, Let me clarify. The device is my wifes which i rooted and unlocked and handed over to her to do with what she will and havent really looked at it since so whatever she done to it , I have no idea. She borked something at some point so i decided I was going install another rom. was going to install an ICS rom, went to flash the firmware and found the bootloader in the state it was in. The last time i looked at that boot loader it said **REVOLUTIONARY**(I think it was revolutionary I dont remember) anyway, It wasnt the way it was before. So not being very familiar with this device Im not a person who will idioticaly flash something without asking first. Thank you for your reply tho.
ramjet73 said:
You can't really tell from the bootloader screen with the engineering hboot installed.
All the custom bootloaders (ENG, Revolutionary, JBear) hide the locked/unlocked/relocked status on the first line of the bootloader screen since they enable the fastboot commands that would normally require unlocking the stock bootloaders. There are two ways to determine the current status:
1. Flash a stock bootloader (1.4, 1.5, 1.58)
2. Run the "query_bootloader.zip" script from this post in recovery
A lot of users get confused about the difference between unlocking the bootloader (hboot S-OFF) and gaining radio S-OFF. I was confused myself until the light went on as explained in this post. It used to be that the only way to get the stock "locked" status back after doing the htcdev unlock was to do the wire trick, but now you can "flash" the "lock_bootloader.zip" file from the post linked in the #2 option above which uses a modified version of update-binary to reset the flag in the firmware.
ramjet73
Click to expand...
Click to collapse
Thank you sir for your response, Exactly what I was looking for. Later,,,,,,
unable to lock bootloader
ramjet73 said:
You can't really tell from the bootloader screen with the engineering hboot installed.
All the custom bootloaders (ENG, Revolutionary, JBear) hide the locked/unlocked/relocked status on the first line of the bootloader screen since they enable the fastboot commands that would normally require unlocking the stock bootloaders. There are two ways to determine the current status:
1. Flash a stock bootloader (1.4, 1.5, 1.58)
2. Run the "query_bootloader.zip" script from this post in recovery
A lot of users get confused about the difference between unlocking the bootloader (hboot S-OFF) and gaining radio S-OFF. I was confused myself until the light went on as explained in this post. It used to be that the only way to get the stock "locked" status back after doing the htcdev unlock was to do the wire trick, but now you can "flash" the "lock_bootloader.zip" file from the post linked in the #2 option above which uses a modified version of update-binary to reset the flag in the firmware.
ramjet73
Click to expand...
Click to collapse
guys will the same work on my htc desire v , i am unable to reset from relocked to locked. i need to apply for warranty as my phone gets restarted every now and then and the htc service center guys are telling that i have void the warranty
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...
I just unlocked, rooted and S-OFFed a Rezound. I then put my sim in it and it wanted to update. Will that mess anything up if I let it?
joeymagnus1 said:
I just unlocked, rooted and S-OFFed a Rezound. I then put my sim in it and it wanted to update. Will that mess anything up if I let it?
Click to expand...
Click to collapse
It won't remove s-off, the update won't install unless your locked and running stock recovery.
Sent from my ADR6425LVW using Tapatalk 2
Cool. I think I'll just drop a different ROM on it anyways. My B-I-L gave it to me. Said the ear-piece wasn't working and he couldn't hear people talking. After I did the above, I tested it with my sim and calling my house phone and I could hear myself clearly.
mjones73 said:
It won't remove s-off, the update won't install unless your locked and running stock recovery.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
You can stay s-off, just keep a locked boot loader and you can install the new RUUs.
GrayTheWolf said:
You can stay s-off, just keep a locked boot loader and you can install the new RUUs.
Click to expand...
Click to collapse
That's what I said isn't it?
mjones73 said:
That's what I said isn't it?
Click to expand...
Click to collapse
You made it seem like you had to relock everything.
To be clear: if you're S-OFF, the update will install (keeping S-OFF intact) regardless of your lock status. I've received more than one OTA update without issue on my S-OFF, unlocked Rezound--after which it remained both S-OFF and unlocked.
S-ON/unlocked is the only permutation of the two that would prevent an OTA update from working properly. That is, if you were S-ON, you would need to be either locked or relocked.
If you're rooted, on the other hand, the OTA will most likely fail. And it definitely will if you have a custom recovery (Amon Ra, TWRP, CWM).
El Schisne said:
To be clear: if you're S-OFF, the update will install (keeping S-OFF intact) regardless of your lock status. I've received more than one OTA update without issue on my S-OFF, unlocked Rezound--after which it remained both S-OFF and unlocked.
S-ON/unlocked is the only permutation of the two that would prevent an OTA update from working properly. That is, if you were S-ON, you would need to be either locked or relocked.
If you're rooted, on the other hand, the OTA will most likely fail. And it definitely will if you have a custom recovery (Amon Ra, TWRP, CWM).
Click to expand...
Click to collapse
Mostly true....however the latest ruu will give you the 2.28 hboot in locked status. S-off will remain so you'll have to flash vinylfreaks modded 2.27 hboot from hboot using a ph98img or simply unlock again.
I've done a handful of these lately and always ended up with a locked hboot even if I was unlocked or using a modded hboot prior.
Sent from my Nexus 7 using Tapatalk HD