I just got a at&t M8 from a friend its unlocked ( tampered & s-on running 4.4.2 how can i update it to lolilpop / Get all updates from At&t ...Help Me
nadir5191 said:
I just got a at&t M8 from a friend its unlocked
Click to expand...
Click to collapse
You mean SIM unlocked or bootloader unlocked. Or both?
If bootloader unlocked, you need to relock it with fastboot command: fastboot oem lock
Then you will want to run the Lollipop RUU on a PC (preferably not Win10).
Backup any personal data you want to keep before relocking bootloader and/or running RUU, as those steps will wipe all data on the phone (including internal storage).
Also, are you using AT&T as your carrier?
redpoint73 said:
You mean SIM unlocked or bootloader unlocked. Or both?
If bootloader unlocked, you need to relock it with fastboot command: fastboot oem lock
Then you will want to run the Lollipop RUU on a PC (preferably not Win10).
Backup any personal data you want to keep before relocking bootloader and/or running RUU, as those steps will wipe all data on the phone (including internal storage).
Also, are you using AT&T as your carrier?
Click to expand...
Click to collapse
My carrier is AT&T also its SIM unlock & running teamwin
where can i find the fastboot command: fastboot oem lock & Lollipop RUU on a PC (preferably not Win10).
nadir5191 said:
My carrier is AT&T also its SIM unlock & running teamwin
where can i find the fastboot command: fastboot oem lock & Lollipop RUU on a PC (preferably not Win10).
Click to expand...
Click to collapse
Code:
fastboot oem lock
is the command used with fastboot.exe
See [how to] lock/unlock your bootloader without htcdev(s-off required) by scotty1223
ROM Update Utility (RUU) is a Windows compatible executable (.exe) which will flash a complete software image to your device, including ROM, hboot, radio, stock recovery, and firmware. This is a handy method to return to (nearly) stock condition;
see [INDEX] AT&T One (M8) Resources Compilation Roll-Up (Updated 9/4/15) by redpoint73
sd_shadow said:
Code:
fastboot oem lock
is the command used with fastboot.exe
See [how to] lock/unlock your bootloader without htcdev(s-off required) by scotty1223
Click to expand...
Click to collapse
Section 1 on the above link is useful (setting up adb). But to avoid any confusion it should be noted that Section 2 (which also requires s-off) is not necessary. Section 2 method is only needed if you want to "hack" the bootloader screen to say LOCKED.
Simply setting up adb/fastboot, then opening Windows command prompt and typing command (after changing directory to the proper fastboot.exe location) fastboot oem lock will make the bootloader say RELOCKED which is sufficient to run the RUU. Also, this is possible with s-on.
Related
I have been trying to lock everything back up to return my phone I am s on but was wanting to relock the bootloader and unroot. I i could not get the ruu to work I am on the new bootloader someone told me to adb oem lock so I did now my phone says tampered locked and security warning but it wont come out of the bootloader every time I try to reboot it goes back to the bootloader even if i power down it still goes back to the bootloader. please help
as of right now all i have is fastboot
shawnten said:
I have been trying to lock everything back up to return my phone I am s on but was wanting to relock the bootloader and unroot. I i could not get the ruu to work I am on the new bootloader someone told me to adb oem lock so I did now my phone says tampered locked and security warning but it wont come out of the bootloader every time I try to reboot it goes back to the bootloader even if i power down it still goes back to the bootloader. please help
as of right now all i have is fastboot
Click to expand...
Click to collapse
If the RUU doesn't work, the other two alternatives are to attempt to flash the stock system.img and stock boot.img through fastboot .. although I'm not sure this will work with S-ON, depends on whether or not the device is locked/unlocked via HTC's official method.
Also, the second alternative, could use the PG*zip file which is stored inside the RUU. the zip file can be extracted from the RUU and placed on the root of the sdcard. Then the bootloader will grab this file and flash, essentially performing the same thing as the RUU would.
Hi
I managed to get back to stock rom (restored from a backup), flashed the stock recovery and now i'm unable to relock the bootloader (no more root/superuser)
is there a way to lock it back without htcdev?
fostazz said:
Hi
I managed to get back to stock rom (restored from a backup), flashed the stock recovery and now i'm unable to relock the bootloader (no more root/superuser)
is there a way to lock it back without htcdev?
Click to expand...
Click to collapse
run fastboot comand:
fastboot oem lock
it will give your bootloader status to "re-lock"
I got relocked status, I want locked status if possible
abusalza said:
run fastboot comand:
fastboot oem lock
it will give your bootloader status to "re-lock"
Click to expand...
Click to collapse
fostazz said:
I got relocked status, I want locked status if possible
Click to expand...
Click to collapse
unlock again using htc dev, then lock using scotty123's method posted here, http://forum.xda-developers.com/showthread.php?t=2540004
on scottys page, look at page 7, at bottom, download link for his lock/unlock tool.
I just bought a att htc one off Craig's list and it is tampered/relocked. The phone boots straight into fastboot and there is no operation system on phone. I tried to use ruu to get it back to stock but it freezes at checking hash 5percent. I also tried to fastboot the ruu zip but it had an error verify 12 signatures. Are there any other suggestions that I could try to get an os back on this phone or is this phone pretty much bricked?
Unlock bootloader, install twrp recovery, sideload a rom zip.
There are numerous existing threads that describe how to do each step, just spend a little time reading first.
cschmitt said:
Unlock bootloader, install twrp recovery, sideload a rom zip.
There are numerous existing threads that describe how to do each step, just spend a little time reading first.
Click to expand...
Click to collapse
I don't think I can unlock the relocked bootloader without the token correct? Is there any other way to unlock a locked bootloader without the htcdev token?
crazyfied said:
I don't think I can unlock the relocked bootloader without the token correct? Is there any other way to unlock a locked bootloader without the htcdev token?
Click to expand...
Click to collapse
Yes, you'll need an unlock token.
Hello,i have a htc one m7(t-mob101)...s-on,unlocked and a custom rom,how can i turn it back to stock to have software warranty?
I have tryed all methods,and no succes.
dnautzu01 said:
Hello,i have a htc one m7(t-mob101)...s-on,unlocked and a custom rom,how can i turn it back to stock to have software warranty?
I have tryed all methods,and no succes.
Click to expand...
Click to collapse
Try this site http://www.handy-faq.de/forum/htc_one_custom_roms/282822-htc_one_firmwaresammlung_ruus_otas_backups.html and look for the nandroid backup and install it. It should put you back at stock.
Since you are S-ON, you will not be able to remove "Tampered" or return to "Locked" status. You need S-OFF to accomplish that, you could follow nkk71's SuperGuide to Stock link in my signature.
and if i want to go to t-mob 010 for the us?to have more updates?i can do that?i`m new in this and i`m a little afraid,i dont want to brake the phone...and i see the site htc1guru is off
dnautzu01 said:
and if i want to go to t-mob 010 for the us?to have more updates?i can do that?i`m new in this and i`m a little afraid,i dont want to brake the phone...and i see the site htc1guru is off
Click to expand...
Click to collapse
To receive the TMOUS updates you must be on TMOUS network. If you are, then you could change your CID & MID to TMOUS. If I were in the European area, I would change the CID to an Int'l one then use the .401 software version. It get updated directly from HTC and it is not dependent on the carrier. The CID for Germany is HTC__002. Here is how you could do it:
Here are the steps to re-branding your phone to Int'l:
Unlock bootloader if not unlocked already!
Install Custom recovery
Download TWRP 2.6.3.3 from here: http://techerrata.com/browse/twrp2/m7
Achieve S-OFF, if not already!
With your hboot 1.5x use rumrunner or firewater to get S-Off: http://firewater-soff.com/ or http://rumrunner.us/
Try all options!
Change CID to the new code:
Code:
[B][I]adb reboot bootloader
fastboot oem writecid HTC__002[/I][/B] <- (CID is exactly 8 characters)
[B][I]fastboot reboot-bootloader[/I][/B]
Change MID to the new code: PN0710000 using: [TOOL] MID change without ENG HBOOT | Aroma GUI
Remove "Tampered" with the Guru Bootloader Reset Tool
Download and flash 4.19.401.9 firmware; place firmware in your fastboot/adb folder and rename to firmware.zip. Ensure you have moved all of your personal items off of your phone this firmware will wipe your phone. Open a command window in your fastboot/adb folder and type:
Code:
[B][I]adb reboot bootloader[/I][/B]
After that, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Execute http://www.htc1guru.com/dld/ruu_m7_ul_k44_sense55_mr_htc_europe_4-19-401-9_r_radio_4a-23-3263-28_10-38r-1157-04l_release_353069_signed_2-1-exe/ or RUU 4.19.401.9 which now matches your CID & MID
There is no need to lock/relock bootloader with S-OFF, and do not even THINK about going back to S-ON!!!
Now you can receive the OTAs or flash them manually.
OTA_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.11-4.19.401.9_R_release_355954met8o678uio0omu3.zip
OTA_M7_UL_K44_SENSE60_MR_HTC_Europe_5.11.401.10-4.19.401.11_release_372404wj19h95c0x6oa19n.zip
OTA_M7_UL_K443_SENSE60_MR_HTC_Europe_6.09.401.5-5.11.401.10_release_386803.zip
OTA_M7_UL_K443_SENSE60_MR_HTC_Europe_6.09.401.10-6.09.401.5_release_397712mm1f6dd6rksg0p3s.zip
Click to expand...
Click to collapse
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.