i am getting ready to send my device back for a warranty exchange. in following the steps, like i have done twice before, i accidentally jumped ahead....
I did the Fastboot oem writesecureflag 3 BEFORE i flashed the lock bootloader zip. The phone still boots and functions normally, but i can't flash the lock bootloader zip, it fails, even though it says unlocked tampered.
Anyone have any suggestions?? I am at a loss, and not sure if there is a command i can run to revert this all back.
My wife was nagging me and i scrolled down and jumped ahead like a total noob. thanks for any help!
And yes everything is accessible still, cwm, adb, the phone itself, etc etc. it functions fine...
Run s-off. After that follow guide in order
Since you're unlocked still face palm should work. Just follow after the point you unlock.
If not any new method will work
Unlocking the bootloader automatically voids your warranty....
thayl0 said:
Unlocking the bootloader automatically voids your warranty....
Click to expand...
Click to collapse
Thank you for an incredibly unhelpful reply.
thayl0 said:
Unlocking the bootloader automatically voids your warranty....
Click to expand...
Click to collapse
Ehhh. It says may. Plus there is a way to get it back to an s-on **LOCKED** state. HTC's unlock tool doesn't log your device ID and IMEI and remote void your warranty like Asus' unlock util does.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Related
So guys I really wanna unlock the bootloader and flash some roms but this is my third atrix. Im using the 14 day grace period very very graciously. Anyways first atrix kept locking up- exchanged. Second one I tried to unlock it with pudding. Did the rsd thing with the. Sbf file and I was doing it. Then toward the end it failed. Complete brick- exchanged.
Anyways is there something else I should do, possibly a different route? Im using an AT&T atrix. Thanks.
Wait for official release and get it officially unlocked?
Sent from my MB860 using XDA Premium App
tsouza said:
Wait for official release and get it officially unlocked?
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
I can wait for the release, but are they unlocking it with it. For sure?
Well, IMO better hope for it than risk another brick...
Sent from my MB860 using XDA Premium App
tsouza said:
Well, IMO better hope for it than risk another brick...
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
True. Very true.
magicriggs said:
So guys I really wanna unlock the bootloader and flash some roms but this is my third atrix. Im using the 14 day grace period very very graciously. Anyways first atrix kept locking up- exchanged. Second one I tried to unlock it with pudding. Did the rsd thing with the. Sbf file and I was doing it. Then toward the end it failed. Complete brick- exchanged.
Anyways is there something else I should do, possibly a different route? Im using an AT&T atrix. Thanks.
Click to expand...
Click to collapse
I think you might have returned the first 2 prematurely.
1st one probably could have factory reset or flashed a new sbf
2nd one was probably a fixable soft brick.
So I'd say you're safe, but up to you as there's always a risk.
Here is what I did.
1. If you were to update to the OTA 4.5.91. Or already on the OTA 4.5.91 you can still unlock your bootloader.
2. Flash pudding only SBF so you can unlock the bootloader. http://diamantephoto.com/fastboot.rar direct link. Flash this one.
http://forum.xda-developers.com/showthread.php?t=1136261 Original Post about pudding.
It will go to a text only 14 option screen and say something like boot failed 0x1000. Don't freak out and tell me you bricked you phone blah blah blah. You still have to unlock the bootloader by choosing fastboot from your phone and connecting it to the computer via usb. Make sure you have ADB with fastboot tools installed on you computer.
Open command prompt from you computer and type fastboot oem unlock. It'll display warning about voiding warranty and a unique device id. Type again fastboot oem unlock ############. The # are the unique device numbers. Don't type # it wont work. The instructions are posted on the pudding thread if you would like to read more about it.
Then type fastboot reboot to reboot. Unlock should be displayed on top left of screen and it'll take 5 long mins to boot up.
3.Then you need to install CWM and root.
You'll find instructions in the developers form. But if your lazy here is the CWM link. http://forum.xda-developers.com/showthread.php?t=1138541 follow the instructions or every time you reboot you will loose CWM. For root there are two available for gingerbread. http://forum.xda-developers.com/show....php?t=1140110 I used this one and got root.
http://forum.xda-developers.com/show....php?t=1138204 I hear this works too.. Haven't tested read the post if you want to use this method.
As always don't blame me for bricking if you happen to do so. DO IT AT YOUR OWN RISK. these are the steps I took to unlock and everything works great. Absolutely no problems with my phone after wards.
One thing unlocking your bootloader will format/erase data. Basically a factory data reset so make sure you backup everything with titanium or you favorite app. I would not restore system apps as i've had a few problems with email and motoblur force closes.
Sent from my MB860 using Tapatalk
magicriggs said:
I can wait for the release, but are they unlocking it with it. For sure?
Click to expand...
Click to collapse
not sure. i got a leaked 4.5.91 build, it's not unlocked (although early beta does). you still have to flash the pudding img yourself.
delect this post
The returns were genuine. I did a factory reset on the first one and it still kept locking up, on the wake up. Had to pull battery out to turn back on. Multiple times. Second one was a complete brick. I couldn't get into rsd, wouldn't turn on and computer didn't recognize it in any mode. Im pretty familiar with rsd, used it with OG and X but this one got me walking om egg shells.
magicriggs said:
The returns were genuine. I did a factory reset on the first one and it still kept locking up, on the wake up. Had to pull battery out to turn back on. Multiple times. Second one was a complete brick. I couldn't get into rsd, wouldn't turn on and computer didn't recognize it in any mode. Im pretty familiar with rsd, used it with OG and X but this one got me walking om egg shells.
Click to expand...
Click to collapse
hmm you are very unlucky then. You're the only one to hard brick from pudding. Probably advise you not to do anything with your phone.
Jnewell05 said:
Here is what I did.
1. If you were to update to the OTA 4.5.91. Or already on the OTA 4.5.91 you can still unlock your bootloader.
Click to expand...
Click to collapse
im on build number 4_1.8.3 and i check for updates and it says my device is up to date. any
ideas?
magicriggs said:
im on build number 4_1.8.3 and i check for updates and it says my device is up to date. any
ideas?
Click to expand...
Click to collapse
4.1.83 is a great point to unlock the bootloader. DO NOT install the 4.5.91 OTA udpate, too risky to hard brick if you flashed an sbf. Of course, you don't have to sbf back anymore, but I would steer way clear of that when there are perfectly good options available. Only use customized ones like Kenneth's or the CherryBlur ROM. More will start flowing soon.
So what your advising is not to even unlock it. All I really want is volume wake.
magicriggs said:
So what your advising is not to even unlock it. All I really want is volume wake.
Click to expand...
Click to collapse
That's the exact opposite of what I'm advising. I knew I was taking some level of risk when I unlocked, but it's a risk well worth taking. Very, very low failure rate. Recoverable. But I can't accept the risk for your phone.
OSNPA said:
That's the exact opposite of what I'm advising. I knew I was taking some level of risk when I unlocked, but it's a risk well worth taking. Very, very low failure rate. Recoverable. But I can't accept the risk for your phone.
Click to expand...
Click to collapse
Oh gotcha. Thanks for the info.
Jnewell05 said:
Here is what I did.
1. If you were to update to the OTA 4.5.91. Or already on the OTA 4.5.91 you can still unlock your bootloader.
2. Flash pudding only SBF so you can unlock the bootloader. http://diamantephoto.com/fastboot.rar direct link. Flash this one.
http://forum.xda-developers.com/showthread.php?t=1136261 Original Post about pudding.
It will go to a text only 14 option screen and say something like boot failed 0x1000. Don't freak out and tell me you bricked you phone blah blah blah. You still have to unlock the bootloader by choosing fastboot from your phone and connecting it to the computer via usb. Make sure you have ADB with fastboot tools installed on you computer.
Open command prompt from you computer and type fastboot oem unlock. It'll display warning about voiding warranty and a unique device id. Type again fastboot oem unlock ############. The # are the unique device numbers. Don't type # it wont work. The instructions are posted on the pudding thread if you would like to read more about it.
Then type fastboot reboot to reboot. Unlock should be displayed on top left of screen and it'll take 5 long mins to boot up.
3.Then you need to install CWM and root.
You'll find instructions in the developers form. But if your lazy here is the CWM link. http://forum.xda-developers.com/showthread.php?t=1138541 follow the instructions or every time you reboot you will loose CWM. For root there are two available for gingerbread. http://forum.xda-developers.com/show....php?t=1140110 I used this one and got root.
http://forum.xda-developers.com/show....php?t=1138204 I hear this works too.. Haven't tested read the post if you want to use this method.
As always don't blame me for bricking if you happen to do so. DO IT AT YOUR OWN RISK. these are the steps I took to unlock and everything works great. Absolutely no problems with my phone after wards.
One thing unlocking your bootloader will format/erase data. Basically a factory data reset so make sure you backup everything with titanium or you favorite app. I would not restore system apps as i've had a few problems with email and motoblur force closes.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
i used update.zip ..did not flash back to 1.83...update.zip (blur 1.83 etc etc) was from leaked moto servers...i have new bootloader cause my andriod recovery is different...of course BL is locked....can i still unlock??
I have rooted, but my bootloader never had "unlocked" text, I say it this way and not just "my bootloader isn't unlocked" because I'm not sure if it is unlocked or not.
Is my warranty void already? If so I'm giong to unlock the bootloader and add AOKP rom!
In my country (Turkey) rooting the device voids the warranty. In case someone needs to send his phone to service, he needs to unroot first.
Also you need to go into recovery by holding power + volume down buttons together at startup, and see which recovery you have installed. Is it the CWM or the moto recovery? If CWM, you're already unlocked. Unlocking bootloader obviously voids warranty, no hesitation about it.
Sent from my MB860 using xda premium
Unrooting your device is really easy, so no worry about that. If you flashed a sbf file to your device, your bootloader is unlocked
Lirannl said:
I have rooted, but my bootloader never had "unlocked" text, I say it this way and not just "my bootloader isn't unlocked" because I'm not sure if it is unlocked or not.
Is my warranty void already? If so I'm giong to unlock the bootloader and add AOKP rom!
Click to expand...
Click to collapse
Technically, your warranty is void. But if you just delete the Superuser app it is doubtful anyone will notice.
If you don't see "unlocked" on your splash screen, then your bootloader is locked.
ticiano_arraes said:
Unrooting your device is really easy, so no worry about that. If you flashed a sbf file to your device, your bootloader is unlocked
Click to expand...
Click to collapse
You can flash an sbf with a locked bootloader. Remember, that is how we unlock the bootloader.
i want to send my phone back to handtec to replace my phone with new one that work fine with no issues like my phone...
and my phone is rooted and unlocked....
there is any easy or noob way to make it fully stock agin?
install a RUU makes all Stock
skdubg said:
install a RUU makes all Stock
Click to expand...
Click to collapse
First you have to use the all in one toolkit to relock your bootloader, then you can run the ruu. Just FYI at the top of Hboot it will now say relocked, not locked. In other words HTC will know you tampered with it.
yes, but a relocked bootloader has nothing to do with warranty (in europe)...
Hi everyone, i 'm going to be concise. I own an HTC onex+ international version (it should be no brand) and i would like to unroot it and reset to factory for a warranty issue. I'm extremely noob so i would like, if it's possibile, the fastest, easyest and safest way to do so.
On internet i found several guides about it as http://onexroot.com/one-x-unroot/how-to-unroot-rooted-htc-one-x/ or http://theunlockr.com/2012/12/28/how-to-unroot-the-htc-one-x-2/ BUT i found also an xda tool http://forum.xda-developers.com/showthread.php?t=1870652&nocache=1 that sounds appropriate to me; i read on other forum that i need some kind of extra instrument like boot.img
There are some things to take note of. The boot.img and HBoot image flashing requires users to get their own files as those are device specific and aren’t included
Click to expand...
Click to collapse
actually i have no idea where get it and how use it. I would be very gratefull if some of you could explain to me step by step how to do the unroot.
ps. i just rooted and put inside the cmw under the instruction of friend of mine but i don't really understand how i did it.
thank you in advance.
relock bootloader and install RUU and you are back on Stock
but would you be back on stock for a warranty issue, you didn't must do that.
warranty has nothing to do with your firmware or root or bootloader unlock.
they would be erase all at your phone and flash the RUU
skdubg said:
relock bootloader and install RUU and you are back on Stock
Click to expand...
Click to collapse
thank you for your reply but the problem is that actually i don't know how to relock booloader and what RUU is; that's why i was lokking for a step by step guide. I may follow and understand a little the guide of before but i'm not safe that it works with htc onec+ too.
but would you be back on stock for a warranty issue, you didn't must do that.
warranty has nothing to do with your firmware or root or bootloader unlock.
Click to expand...
Click to collapse
really? i belived that an "unlocked" phone was an enough reason to invalidate the warranty isn't it?
kadakar said:
really? i belived that an "unlocked" phone was an enough reason to invalidate the warranty isn't it?
Click to expand...
Click to collapse
if you dont touch the bootloader it says: LOCKED
if you unlocked bootloader it says: UNLOCKED
if you relocked bootloader it says: RELOCKED
we can never go back to LOCKED (RELOCKED is technical the same like LOCKED, but it shows as RELOCKED) all people can see that the bootloader was touched by the user
so it cant the reason for that
to relock:
boot into bootloader
and execute this command in fastboot:
fastboot oem lock
now you can install your latest RUU (RUU is the Stock Firmware from HTC as *.exe to install from Windows [depends on your CID])
Hi everyone.
I'm S-off, SuperCID, 4.16.401.9 firmware, and I re-locked my bootloader while troubleshooting an adb problem.
Is there a simple fastboot command that'll unlock my bootloader again?
I can flash recoveries via the Flashify app, but I can't do much via adb anymore.
Thanks!
How did you unlock it the first time? HTC Dev Im assuming,should still have the unlock token bin file...thats run from bootloader via fastbootusb command...This should be in Questions and Answer forum...??
BBEgo said:
Hi everyone.
I'm S-off, SuperCID, 4.16.401.9 firmware, and I re-locked my bootloader while troubleshooting an adb problem.
Is there a simple fastboot command that'll unlock my bootloader again?
I can flash recoveries via the Flashify app, but I can't do much via adb anymore.
Thanks!
Click to expand...
Click to collapse
Wonders_Never_Cease said:
How did you unlock it the first time? HTC Dev Im assuming,should still have the unlock token bin file...thats run from bootloader via fastbootusb command...This should be in Questions and Answer forum...
Click to expand...
Click to collapse
That's weird.... I thought I posted this in the Q&A forum. I was just in there looking for it and I thought it'd gotten deleted or something. Oh well.
Mods, please feel free to correct my goof.
I didn't use HTCDev to unlock. I just did Sunshine and it handled everything. S-off, unlock, and root - Talk about painless! After that I installed a custom recovery (Philz) and I was off to the races.
So I decided to SuperCID my phone so I can install whatever I want. No problem.
Then I tried to install 5.0.1 firmware (4.16.1540.8) so I could run SkyDragon, but the firmware posted on page 1 in the thread would not install- 4.16.1540.8
Kept giving me "FAILED (REMOTE:24 parsing android-info fail)"
I was able to install 4.16.401.9 with no major headaches, once I found a sensible upgrade path. That one is working fine, but I don't understand why 4.16.1540.8 would not install.
After googling the error, I found a post from Scotty a while back that said the phone wanted to see a stock recovery, locked. So I thought I'd throw the old recovery back on and do the 'fastboot oem lock' command . I didn't think it would impact the phone's operation since it is S-off. Well, the command worked, but I still wasn't able to flash the dang firmware I wanted to my phone.
So now I'm S-off, locked bootloader, PhilZ recovery (put it back on with Flashify), SuperCID, on Lollipop, and I guess everything is ok. But I still don't understand why the phone wouldn't take the firmware.
Any ideas? Thanks in advance.
If you ran sunshine on it,you can run it again i believe on that same device. It should unlock it again,if not then can try htcdev as it also uses fastboot to unlock as long as you can get adb to show needed code.
BBEgo said:
After googling the error, I found a post from Scotty a while back that said the phone wanted to see a stock recovery, locked. So I thought I'd throw the old recovery back on and do the 'fastboot oem lock' command . I didn't think it would impact the phone's operation since it is S-off. Well, the command worked, but I still wasn't able to flash the dang firmware I wanted to my phone.
Click to expand...
Click to collapse
In the past (at least on my One X EVITA) my understanding was that s-off meant that all security was bypassed. Meaning that bootloader check was effectively bypassed.
This isn't the case for the M8. From what I can tell a LOCKED bootloader still prevents you from flashing anything that isn't signed (anything "unofficial") even if s-off.
However, having an UNLOCKED bootloader doesn't seem to affect anything while s-off. Meaning you can do things like RUU when UNLOCKED (which normally needs to be LOCKED or RELOCKED if s-on).
In short, I don't ever recommend relocking the bootloader if s-off on this device. There isn't any reason to, as far as I can tell. Meaning, having an UNLOCKED bootloader doesn't prevent you from doing anything. However, a RELOCKED bootloader does (even when s-on) prevent some things.