So, I'm having hardware issues with my phone, but before I waste time calling Sprint I want to restore my phone to stock. I followed this guide:
http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/
I got through the guide and realized after I completed it that there was an error during the process and phone is still unlocked but now S-ON. I was S-Off. I can't get the phone to lock now (I assume because I needed to lock the phone BEFORE I went back to S-ON).
Can someone offer advice? Do I need to be S-Off again before I lock the device?
Thanks,
-B
fastboot oem lock does not work?
Related
I got my phone back from repair and I'm confused ass to what to do next. I'm set to 'relocked' bootloader, but s-off without recovery or su apparently on 4.3. Every guide I find requires me to do something that causes things to come to as halt. Unless I'm doing something wrong I can't flash a recovery due to some error, then can't flash anything through recovery obviously, and I tried rumrunner but that stalls out after some point saying 'device is not rooted AND unsecure kernel'. What do I do next? Will HTCDev work? That's how I originally unlocked at release.
Really need help here, leaving the country for 3 weeks thursday morning and want to be back in business.
included pic of bootloader
yeah unlock again at htc dev then you will be able to flash a recovery
Or look here
[how to] lock/unlock your bootloader without htcdev(s-off required)
Thanks, had a feeling I needed to HTCDev again but didn't want to risk it given my limited time. Took some tinkering but looks like I'm unlocked and rooted again. Thanks BD.
OK, so I've followed the newb guide to relocking my unlocked bootloader here:
http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786/page4
I had issues getting the bootloader locked but found another guide here:
https://forums.motorola.com/posts/029f68b0a0
I used the command listed in the xml file listed at the bottom of the page, adapter to my phone of course.
After a few tried I got everything transferred with fastboot and the fastboot screen on my phone now says locked. My issue now is that the phone still boots up with the Bootloader Unlocked Warning screen.
Will I still be able to upgrade with the OTA? If not, what do I need to do to get rid of this warning screen on boot so that I can upgrade?
Any help is much appreciated, and I apologize if this has already been answered somewhere, but I've been looking for the past 3 hours with no success.
-----------------------------------------------
Nevermind, this has been solved.
I was able to upgrade even with the warning screen on boot. Hopefully this helps someone.
vapor100LL said:
OK, so I've followed the newb guide to relocking my unlocked bootloader here:
http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786/page4
I had issues getting the bootloader locked but found another guide here:
https://forums.motorola.com/posts/029f68b0a0
I used the command listed in the xml file listed at the bottom of the page, adapter to my phone of course.
After a few tried I got everything transferred with fastboot and the fastboot screen on my phone now says locked. My issue now is that the phone still boots up with the Bootloader Unlocked Warning screen.
Will I still be able to upgrade with the OTA? If not, what do I need to do to get rid of this warning screen on boot so that I can upgrade?
Any help is much appreciated, and I apologize if this has already been answered somewhere, but I've been looking for the past 3 hours with no success.
-----------------------------------------------
Nevermind, this has been solved.
I was able to upgrade even with the warning screen on boot. Hopefully this helps someone.
Click to expand...
Click to collapse
There was absolutely no reason whatsoever to "relock" your bootloader. In fact, it was very foolish to do this.
Glad you got it solved, but for future reference, there IS NO REASON TO EVER RE-LOCK THE BOOTLOADER.
Having an unlocked BL does NOT prevent you from taking OTAs.
Hey there,
my phone is broken, it won't load or do anything on the usb port while the system is up, when the phone is off/fastboot or recovery it seems to charge (very slow) and i have no problems accessing it through fastboot or adb.. but even when the battery is fully charged i cannot use it for more than an hour or so before its discharged again..thats what my problem startet with, over the night the phone won't charge and i couldn't use ADB etc while the OS was up...
i think it is a hardware problem, the last thing i did was updating the firmware, but after that i used the phone like 2 weeks or, without problems and changing anything......
first i thought about it could be a bug with the new firmware, so i downgraded to an old stock version and update it through OTA to the latest version but nothing changed..
then i thought of sending it in and i tried to lock my bootloader and restore everything before doing this but the only way to access the phone via adb was in recovery, so i did that and S-ONed the phone and locked the bootloader, not thinking about that i cannot restore the old recovery with locked BL.
since i knew that i am kind of an idiot, not thinking about what exactly i did at this point i thought i pay my rent by buying SunShine an S-On it again (i didn't find another way to root/unlock BL since i was on last HTC-Android version). and replace the recovery with the original one
now i have my phone with stock recovery and everything but i cannot lock/s-off the bootloader again because i have no adb access.
Does anyone have an idead how i can prepare my phone for sending it in?
I thought about rooting stock firmware, replace recovery with stock recovery, write a script that locks the bootloader execute it after replacing recovery and unroot the phone from within SuperSU. then S-OFF it again.
I guess this should work, but since i didn't think about everything the first time i thought i might ask here if someone has a better idea.
smokey_joe said:
Hey there,
my phone is broken, it won't load or do anything on the usb port while the system is up, when the phone is off/fastboot or recovery it seems to charge (very slow) and i have no problems accessing it through fastboot or adb.. but even when the battery is fully charged i cannot use it for more than an hour or so before its discharged again..thats what my problem startet with, over the night the phone won't charge and i couldn't use ADB etc while the OS was up...
i think it is a hardware problem, the last thing i did was updating the firmware, but after that i used the phone like 2 weeks or, without problems and changing anything......
first i thought about it could be a bug with the new firmware, so i downgraded to an old stock version and update it through OTA to the latest version but nothing changed..
then i thought of sending it in and i tried to lock my bootloader and restore everything before doing this but the only way to access the phone via adb was in recovery, so i did that and S-ONed the phone and locked the bootloader, not thinking about that i cannot restore the old recovery with locked BL.
since i knew that i am kind of an idiot, not thinking about what exactly i did at this point i thought i pay my rent by buying SunShine an S-On it again (i didn't find another way to root/unlock BL since i was on last HTC-Android version). and replace the recovery with the original one
now i have my phone with stock recovery and everything but i cannot lock/s-off the bootloader again because i have no adb access.
Does anyone have an idead how i can prepare my phone for sending it in?
I thought about rooting stock firmware, replace recovery with stock recovery, write a script that locks the bootloader execute it after replacing recovery and unroot the phone from within SuperSU. then S-OFF it again.
I guess this should work, but since i didn't think about everything the first time i thought i might ask here if someone has a better idea.
Click to expand...
Click to collapse
You have stated a lot of things but most of them are contradictory.
What is the status of your phone? Locked or Unlocked?
Are you S-ON or S-OFF?
What recovery do you have on the phone? Stock or Custom?
What specifically are you trying to accomplish?
If you have stock rom, stock firmware with stock recovery, bootloader is locked and you are S-ON then you are back to stock. However, if your bootloader states "Tampered" and/or "Relocked" then the service facility will know that you tampered with the phone. To remove those items:
Unlock bootloader
Follow the steps in nkk71's SuperGuide in my signature on:
--Gain S-OFF
--Custom recovery
--Removing "Tampered" & "Locked"
--Install stock firmware
--Gain S-ON
majmoz said:
You have stated a lot of things but most of them are contradictory.
What is the status of your phone? Locked or Unlocked?
Are you S-ON or S-OFF?
What recovery do you have on the phone? Stock or Custom?
What specifically are you trying to accomplish?
If you have stock rom, stock firmware with stock recovery, bootloader is locked and you are S-ON then you are back to stock. However, if your bootloader states "Tampered" and/or "Relocked" then the service facility will know that you tampered with the phone. To remove those items:
Unlock bootloader
Follow the steps in nkk71's SuperGuide in my signature on:
--Gain S-OFF
--Custom recovery
--Removing "Tampered" & "Locked"
--Install stock firmware
--Gain S-ON
Click to expand...
Click to collapse
thanks for your reply.
i guess i was to confused to see that i can remove the tampered and unlocked flags, then restore the stock bootloader and then s-off the phone...i thought i have to remove tampered/unlocked and then s-on the phone in the same step....i guess i have no problem when i can do it like that
I picked up a used HTC One M7 yesterday, locked to T-Mobile, thinking I could do what I usually do, buy an unlock code for $4 on eBay and use the phone.
Problem is, when I tried to get the unlock code, sellers told me they couldn't find the unlock code for the IMEI I gave them.
So I compared it to the one on the box, and it is different.
I loaded up bootloader, and saw it's unlocked, so now I know someone messed with the phone.
My problem is this:
If I want to use an official unlock code, it will only work with a stock ROM. Now, in order to change the IMEI back to the original one, I have to root (already done) and switch S-OFF. However, when I attempted to run Firewater, it told me I have to try a different kernel, because the one that's installed has an anti-firewater lock.
If I change the kernel, the ROM will no longer be stock, and then I won't be able to use the unlock code anymore, correct?
I did find another way to unlock the phone which uses a custom Config.dat file, but that's a last resort and I'm not certain if it will work or not, so I'm not really sure what I should do at this point to actually get this phone unlocked.
Originally, my plan was to unlock it and then install Cyanogenmod.
Can someone please help? I've spent hours on this today already and I'm running on empty.
Ok, I got the unlock code and tried it but it says it's invalid, so it definitely won't work with the modified IMEI (wasn't really expecting it would).
So I'm left with the challenge of reverting the IMEI back to factory. In order to do that, S-OFF needs to be set, and for that I need to run firewater, however, this is what I keep getting:
ERROR: kernel contains HTC anti-firewater patch!
****** Try again with a different kernel ******
I've tried installing the elemental kernel, and it gives me the same error.
I'm running 4.4.3, Sense 6, bootloader 1.57
Really not sure what to do next.
You won't find anything here. Changing the IMEI is illegal and not to be talked about here
Well that's lame. I'm not asking because I want to perform an illegal act, I just want to restore my phone to it's proper settings so I can actually use it.
kloan said:
Well that's lame. I'm not asking because I want to perform an illegal act, I just want to restore my phone to it's proper settings so I can actually use it.
Click to expand...
Click to collapse
Well that's the thing. Changing it in any way is an illegal act. Any tool that could help has been banned from the site for years and if no original backup was made sending it in for repair is the only option I can offer.
Yeah, I suppose if I can't figure it out I'll try to find a tech in town that can help.
But I don't necessarily need specific step by step instructions on how to modify the IMEI, just some general guidance with getting S-OFF working properly, and making sure I don't mess anything up so that when I do revert back to stock I can still use the unlock code I got.
I just re-locked the bootloader and am now installing the RUU_M7_UL_JB43_SENSE50_MR_TMOUS_3.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2(2).exe I downloaded, which I'm running in Parallels, since Mac seems to be fairly limited with some things.
After I get that installed and working, I'm going to see if I can go through the steps of unlocking the bootloader, rooting and trying firewater again.
If that doesn't work, maybe I'll try installing the latest cyanogenmod build, and trying to get firewater to set S-OFF after that.
You may have many issues if you doing all this on a mac.
Ref lashing the stock ROM has been known to help some. Not all but a few it worked on.
The IMEI change could also be a main board replacement. Then the IMEI on device would be correct and the one on the box would be wrong.
The serial number is still the same.
I re-locked the bootloader to try and install that ruu, but it got stuck and now it won't boot past hboot.
I'm running the cyanogenmod installer now because I don't know what else to do.
You could also try to S-OFF with revone, which got stuck for me at a certain point, but I went S-OFF anyway.
I tried revone because I had the same issue with firewater as you had.
Alright, I'm not going to get into all the crap I went through trying to get s-off, but suffice to say it was a colossal waste of time.
Ended up buying Sunshine and that worked like a charm when I ran it after restoring the factory T-Mobile rom.
Changing the IMEI back was ridiculously easy once I had s-off.
HOWEVER, the unlock code doesn't work! It tells me it's invalid.
What's the process for going about it? I did do a search, but didn't find anything useful. Any help would be appreciated.
Reasoning: I'm going to be upgrading and turning in the phone, so it's time to put it back to factory.
mlw4428 said:
What's the process for going about it? I did do a search, but didn't find anything useful. Any help would be appreciated.
Reasoning: I'm going to be upgrading and turning in the phone, so it's time to put it back to factory.
Click to expand...
Click to collapse
1. Go back to stock everything by following section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
2. While in bootloader mode, use the fastboot command "fastboot oem lock"
If you're turning in the phone to Verizon, this method is okay. However, don't do this if you plan on selling the phone to someone else. If they were to try and unlock the phone again, they would most likely brick it.
According to jcase relocking the bootloader it still shows a modified status code. Your warranty is permanently voided.
Are you on an Edge plan? Otherwise I don't know why you would be returning the phone to upgrade. Also not sure what their rules are on permanently modifying the software of one of these essentially "lease-to-own" devices, so might want to check the terms and conditions if this applies to you. If you are just trading it in for credit toward a new phone, I'd just sell it yourself unlocked and get a lot more for it.
Sent from my XT1254 using Tapatalk
SpyderPride said:
If you are just trading it in for credit toward a new phone, I'd just sell it yourself unlocked and get a lot more for it.
Click to expand...
Click to collapse
A bootloader unlocked, rooted XT1254 would be more valuable to a buyer than one locked down. You've already done all the hard work.
TheSt33v said:
1. Go back to stock everything by following section 0 of this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
2. While in bootloader mode, use the fastboot command "fastboot oem lock"
If you're turning in the phone to Verizon, this method is okay. However, don't do this if you plan on selling the phone to someone else. If they were to try and unlock the phone again, they would most likely brick it.
Click to expand...
Click to collapse
Heya so I'm in a serious bind.
I skipped your step 1 and locked my bootloader. I have an unlocked bootloader. I recently upgraded through the normal verizon pushed update the marshmallow update. Anyhow. I now want to return the phone for an upgrade and well... I locked the bootloader. Then turn the phone off and turned it back on and it now says locked, but it says failed to validate system image. I then got freaked out and downloaded all the step 1 files and tried to flash the stock rom (which i already had installed!) and that doesn't seem to work. Did I brick my phone? Is there any way to get it working now that it is locked with any kind of android at all?
You're probably fine @droidfun1. You just need to use the marshmallow firmware package instead of the lollipop one. Get it here: https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Yup, I tried flashing the stock 6.0.1 rom with fastboot on my mac but I got all kinds of fails.
I found a mac compatible command line version of RSDLite and it totally worked! Not sure why fastboot couldn't successfully flash the same stock rom?
Now I just need to remove the bootloader unlocked warning (my phone is now locked status 2), but not sure if I can now that it is locked.
TheSt33v said:
You're probably fine @droidfun1. You just need to use the marshmallow firmware package instead of the lollipop one. Get it here: https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Click to expand...
Click to collapse
droidfun1 said:
Yup, I tried flashing the stock 6.0.1 rom with fastboot on my mac but I got all kinds of fails.
I found a mac compatible command line version of RSDLite and it totally worked! Not sure why fastboot couldn't successfully flash the same stock rom?
Now I just need to remove the bootloader unlocked warning (my phone is now locked status 2), but not sure if I can now that it is locked.
Click to expand...
Click to collapse
Strange. As far as I understand it, RSDlite just automates fastboot, so even if you're using RSDlite, you're actually using fastboot. Whatever works though.
As for the unlocked bootloader message, see my response to that post you made.