I used a .exe RUU to get my phone 100% stock!
If you have a locked bootloader, use the command "fastboot oem lock" via Fastboot.
If you have "stuck on sending 1/8" issues, try to use the .exe on another computer! It worked for me.
Big thanks to ckpv5 and Mr Hofs for the help !
Hi guys..
So a long time ago I rooted my phone, installed a custom recovery and a custom ROM on my HTC. But then I came back to a stock ROM, stock recovery but still rooted.
Today I had an OTA official update (security fix). I installed it, but then my phone is stuck on the HTC One logo! I don't have any backups..
I don't know if I can use ADB or everything since i don't know if I can power off.
I don't know if I'm really rooted. When I wanted to unroot the phone it didn't worked, so I desactivated supersu, and automatically set supersu to "reject requests" (to root access)
S-ON
Stock recovery
Stock rom (this one: http://www.forum-generationmobiles....lection-de-roms-officielles-en-zip-htc-one-m8 )
CID= HTC_203
Unlocked bootloader
Rooter-or not
I don't know what to do, help :'( I don't want to waste 500€...
Flash a custom recovery and flash a custom rom. Then start looking for a backup with at least a working phone. There is a dedicated firmware/backup thread in the general section. Have a read there .... it's stickied so can't mis it !
That's what I wanted to do too! Okay. But thats kinda strange, I mean I installed a stock rom with a stock recovery but I can't install OTA update
LowPoly said:
That's what I wanted to do too! Okay. But thats kinda strange, I mean I installed a stock rom with a stock recovery but I can't install OTA update
Click to expand...
Click to collapse
On lollipop, OTA will fail when the stock ROM is rooted due changes in binary.
You need a pure non-rooted stock ROM. Re-unrooted a rooted stock ROM won't work either.
ckpv5 said:
On lollipop, OTA will fail when the stock ROM is rooted due changes in binary.
You need a pure non-rooted stock ROM. Re-unrooted a rooted stock ROM won't work either.
Click to expand...
Click to collapse
Okay, thats good to know.
Before I do anything, can I also re-lock the bootloader and install a RUU (exe) instead ? Will it work ? I'm probably wrong, but I think it's better since its a pure stock new ROM and not a backup..
LowPoly said:
Okay, thats good to know.
Before I do anything, can I also re-lock the bootloader and install a RUU (exe) instead ? Will it work ? I'm probably wrong, but I think it's better since its a pure stock new ROM and not a backup..
Click to expand...
Click to collapse
Yeah .. you can use RUU.exe (relock bootloader because S-On and make backup of your internal storage important data as this will wipe everything)
Some prefer to use pure stock TWRP backup because of the hassle to relock and later to re-unlock as these process will wipe data. Some prefer to keep their data intact and there is no need to relock bootloader when using a backup
ckpv5 said:
[...] because of the hassle to relock and later to re-unlock
Click to expand...
Click to collapse
By the way, if I want to re-unlock my bootloader, will I have to do this method again
http://htc-one.wonderhowto.com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444/
with HTCdev etc ? Or is there a "fastboot" method as fastboot oem lock ?
LowPoly said:
By the way, if I want to re-unlock my bootloader, will I have to do this method again
http://htc-one.wonderhowto.com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444/
with HTCdev etc ? Or is there a "fastboot" method as fastboot oem lock ?
Click to expand...
Click to collapse
Yes ... you can use the unlock_code.bin that you already have. If that doesn't work, you need to reapply to HTCDev as there is no fastboot command to unlock bootloader unless your device is S-Off.
ckpv5 said:
Yes ... you can use the unlock_code.bin that you already have. If that doesn't work, you need to reapply to HTCDev as there is no fastboot command to unlock bootloader unless your device is S-Off.
Click to expand...
Click to collapse
Okay! Thank you very much
Hi again,
I thought of something. A long time ago, white installing an Aroma-install stock ROM (link in first post), I had this problem: http://forum.xda-developers.com/htc-one-m8/help/problem-write-internal-storage-5-0-1-t3085187 . But to solve it, I need root, and for an unknown reason I couldn't uninstall root.
So since i'm not very comfortable with english, and IN CASE i have the same problem with a RUU:
if Aroma stock rom:
-> Stock rom
-> Stock recovery
-> Rooted (i can choose if i root it or not)
-> SD card problem
-> Need root to solve (terminal emulator)
-> Solve
-> No OTA update because can't uninstall root
If RUU
-> Stock rom
-> Stock recovery
-> Not rooted
-> SD Card problem
-> Need root to solve
-> Install root and solve
-> No OTA update because can't uninstall root
What will I have to do ?
Since now your current firmware is a lollipop and you need to do another OTA, don't think that problem will happen again.
But if that still happen, you only need to reunlock the bootloader and install TWRP (the latest) and reflash SuperSU.zip then follow that instructions to correct that SD problem.
(assuming you're using RUU to get back to stock)
If you want to use a backup ... read my thread on how-to : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
and all the files needed are there.
ckpv5 said:
Since now your current firmware is a lollipop and you need to do another OTA, don't think that problem will happen again.
But if that still happen, you only need to reunlock the bootloader and install TWRP (the latest) and reflash SuperSU.zip then follow that instructions to correct that SD problem.
(assuming you're using RUU to get back to stock)
If you want to use a backup ... read my thread on how-to : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
and all the files needed are there.
Click to expand...
Click to collapse
Thank you very much for all your quick answers. I did the fastboot oem lock command to lock the bootloader, but it appeared it failed:
C:\Fastboot>fastboot oem lock
... INFO[PGFS] partition_update_pgfs: pg1fs_securi
ty
INFOTZ_HTC_SVC_ENC ret = 0
INFO[PGFS] partition_update_pgfs: pg2fs_sec_recovery
INFOLock successfully...
INFOdeinit_lcd
INFOmipi display off
INFOmdp_clock_off
INFOturn off fd8c2308 failed 1 times. Try again...
INFOdisable_mmss_clk done
INFOpll1_disable done
INFOTZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
INFO[CRITICAL] SPMI write command failure: cmd_id = 0, erro
r
INFO= 4
INFO[CRITICAL] SPMI write command failure: cmd_id = 0, erro
r
INFO= 4
INFO[ERR] Cannot halt SPMI arbiter!!
INFO[INFO] Rebooting device
FAILED (status read failed (Unknown error))
finished. total time: 1.190s
but the bootloader is showing "RELOCKED" anyway. So I launched the RUU, but for more than 30min it was stuck on "1/8". The program said it was supposed to take only 10min, so I unplugged the phone and powered-it off.
For now my bootloader says "RELOCKED" and OS "4.16.401.13 (4.16.401.10)".
So I don't really know on which os version I am.
What I want to do now is:
Unlock my bootloader again;
Flash a 4.16.401.10 firmware
Install latest twrp recovery
Install a backup
Is it correct, or is there another way to fix all this ?
I hope no partition is corrupted when unplugged phone while RUU still running.
OS "4.16.401.13 (4.16.401.10) means incomplete process.
You can try those steps.
ckpv5 said:
I hope no partition is corrupted when unplugged phone while RUU still running.
OS "4.16.401.13 (4.16.401.10) means incomplete process.
You can try those steps.
Click to expand...
Click to collapse
Or I still can try another ruu exe, and wait longer, like 1 hour ?
LowPoly said:
Or I still can try another ruu exe, and wait longer, like 1 hour ?
Click to expand...
Click to collapse
You can try again to run the RUU but it should not take more than 20 mins.
You need to use USB 2.0 to avoid problem and if possible to run it on Win7 pc as some reported problem on Win8 and Win10 (personally I don't have problem on any windows version but USB 2.0)
ckpv5 said:
You can try again to run the RUU but it should not take more than 20 mins.
You need to use USB 2.0 to avoid problem and if possible to run it on Win7 pc as some reported problem on Win8 and Win10 (personally I don't have problem on any windows version but USB 2.0)
Click to expand...
Click to collapse
Some people said that they solved the problem by re-running the RUU.. Btw it was stuck on "sending". Anyway I'm gonna re-run the same RUU. If it's still stuck i'm gonna try to re-run the ruu by using a usb 2.0. And if it's still stuck I'm gonna try to flash the .10 firmware, twrp etc...
I'll keep you up to date
EDIT: or maybe the RUU isn't working because fastboot oem lock said FAILED ?
LowPoly said:
Some people said that they solved the problem by re-running the RUU.. Btw it was stuck on "sending". Anyway I'm gonna re-run the same RUU. If it's still stuck i'm gonna try to re-run the ruu by using a usb 2.0. And if it's still stuck I'm gonna try to flash the .10 firmware, twrp etc...
I'll keep you up to date
EDIT: or maybe the RUU isn't working because fastboot oem lock said FAILED ?
Click to expand...
Click to collapse
No .. not that. It's the USB connection usually.
You also can try fastboot flash RUU.zip - http://forum.xda-developers.com/showthread.php?t=2735235
but you need to use htc_fastboot.exe instead of normal google fastboot.exe
You can have all the needed files RUU.zip and htc_fastboot.exe there
Okay here's what I'm gonna do.
- Trying the exe RUU on another computer (with windows 8, but there I'm sure there's no usb problem).
- If not working, trying flashing the zip RUU you gave me on this same computer
- If not working, trying again the exe RUU but waiting a longer time (~3hours, it worked for someone).
- If not working, trying flashing a new firmware, twrp, and using a backup.
If all these steps don't work I'm gonna be sure that there's no more solution and that my phone is officialy dead uhh
EDIT: I'm definitely sure that this is an USB problem. On my first computer (with windows 7), I can't read some USB keys for no reason. They're not detected.
LowPoly said:
If all these steps don't work I'm gonna be sure that there's no more solution and that my phone is officialy dead uhh
Click to expand...
Click to collapse
There are many ways to update the phone... don't give up.
Try all the steps that you mentioned. They should work. If still not working, I'll tell you the other way that I have in mind i.e. flashing firmware and ROM without a need of PC.
Okay! I finish to install all the drivers and start to try the steps. I'll keep you updated. Thank you again by the way. Right now you're my last and only hope
Related
Hello, im having trouble getting my hox to stock to apply the new OTA
I didnt install any custom rom, but i unlocked bootloader to install CWM and rooted my phone.
I checked that my version is 2.17.707.3, WWE, unbranded, so i downloaded this file RUU_ENDEAVOR_U_ICS_40_S_hTC_Asia_WWE_2.17.707.3_Radio_2.1204.135.20_release_278245_signed
The thing is that when i run the RUU, it fails everytime, i tried installing it with android booted, usb debuggin on, using an usb 2.0.. tried booting in bootloader mode using fastbook USB and still failed.
Any ideas?
You need to relock bootloader.
Code:
fastboot OEM lock
And make sure to have battery charged <50% before RUU.
Sent from my HTC One X
TToivanen said:
You need to relock bootloader.
Code:
fastboot OEM lock
And make sure to have battery charged <50% before RUU.
Click to expand...
Click to collapse
Common wisdom would suggest greater than 50%
You can also try restoring nanroid backup.
Dont forget to flash boot.img also erase cache.
Then flashing the stock recovery.
No need to lock bootloader.
You can find the nandroid backup thread in general section.
Thanks to all!, i will try that as soon as my phone gets 100% battery
faiz02 said:
You can also try restoring nanroid backup.
Dont forget to flash boot.img also erase cache.
Then flashing the stock recovery.
No need to lock bootloader.
You can find the nandroid backup thread in general section.
Click to expand...
Click to collapse
I never installed nandroid bkp, and i dont have a "boot.img" file, are those steps are neccesary for running the RUU utility (the one that football uploaded) too?
http://www.filefactory.com/f/7cc7b2fbdd03c031/
malakoid said:
Thanks to all!, i will try that as soon as my phone gets 100% battery
I never installed nandroid bkp, and i dont have a "boot.img" file, are those steps are neccesary for running the RUU utility (the one that football uploaded) too?
http://www.filefactory.com/f/7cc7b2fbdd03c031/
Click to expand...
Click to collapse
If you have a RUU, no they aren't
i modified my platform.xml to enable w/r access for the sdcard a few months back.
there was a copy of the original, er, 'somewhere' but i cant find it now.
i have removed the line added i in before but the 4.4.4 ota update is failing because of platform.xml.
anyone have a stock unmodified platform.xml they could upload here or pm?
my M8 is a dual sim version if that makes any difference.
thanks.
You should be able to find your RUU here and extract the file in question:
http://forum.xda-developers.com/showthread.php?t=2701376
berndblb said:
You should be able to find your RUU here and extract the file in question:
http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
Nope, dont see it. is there one? (its a dual sim version)
couldnt see one on htcdev either.
i already have a signed zip file
0P6BIMG_M8_DUGL_K44_SENSE60_HTC_Europe_1.45.401.12_R_Radio_1.18.30306251.05G_30.57.306251.00L_release_381655_combined_signed.zip
but as it is signed i cannot extract anything from it
winrar always say corrupt image, is there another way?
Solved?
Did you solve the problem? I have exactly the same issue . . .
gazzacbr said:
Nope, dont see it. is there one? (its a dual sim version)
couldnt see one on htcdev either.
i already have a signed zip file
0P6BIMG_M8_DUGL_K44_SENSE60_HTC_Europe_1.45.401.12_R_Radio_1.18.30306251.05G_30.57.306251.00L_release_381655_combined_signed.zip
but as it is signed i cannot extract anything from it
winrar always say corrupt image, is there another way?
Click to expand...
Click to collapse
simonvfr said:
Did you solve the problem? I have exactly the same issue . . .
Click to expand...
Click to collapse
Hi,
not exactly. but i am on 4.4.4
i was toying with the idea of winding back to stock using nandroid, rooting and copying out platform.xml, then having another go at OTA...
but, i thought i might as well give MaximusHD 4.4.4 for dual sim a go as i was going to wipe anyway.
i flashed TWRP latest 2.8.1 and updated firmware (link is on Maximus page) and then ROM.
so thats where i am now and happy with the rom.
100% stable, no issues noticed at all and aroma removed some bloat for me as i installed.
no need to go back now.
i will wait for lollipop from HTC and all those custom roms for M8 dual sim to try out (er, joke)
gazzacbr said:
Hi,
not exactly. but i am on 4.4.4
i was toying with the idea of winding back to stock using nandroid, rooting and copying out platform.xml, then having another go at OTA...
but, i thought i might as well give MaximusHD 4.4.4 for dual sim a go as i was going to wipe anyway.
i flashed TWRP latest 2.8.1 and updated firmware (link is on Maximus page) and then ROM.
so thats where i am now and happy with the rom.
100% stable, no issues noticed at all and aroma removed some bloat for me as i installed.
no need to go back now.
i will wait for lollipop from HTC and all those custom roms for M8 dual sim to try out (er, joke)
Click to expand...
Click to collapse
Thanks. As I am rooted, with TWRP, but S-ON, I think I can't flash the new firmware. Or am I wrong on that?
I have nandroid backup from my original stock, so could go back to that and re-lock and then do the OTA, but it's a long slow way of getting to 4.4.4!
An alternative would be Cyanogenmod - but although CM11 supports multi-sim phones I can find nothing clear about whether the official builds support the M8 dual-sim.
Finding the M8 ROM situation frustrating after messing around endlessly with custom ROMs on Acer dual sim phone . . . .
simonvfr said:
Thanks. As I am rooted, with TWRP, but S-ON, I think I can't flash the new firmware...
Click to expand...
Click to collapse
you can but you have to re-lock the boot loader which will wipe your phone.
i used these instructions (I am S-OFF already) and firmware from link on Maximus site:
-------------------------------------------------------
How to flash firmware
### If you are S-ON ---> Re-lock your bootloader (this will most probably wipe content of your device)
If you are S-OFF ---> no need to re-lock the bootloader.
Copy downloaded .zip to fastboot.exe location
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol DOWN + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
### Type: fastboot oem lock (if your device is not relocked yet or in case it's S-ON)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Flash firmware.zip again just to make sure.
Type: fastboot reboot-bootloader
-------------------------------------------------------
what i am sure of is that without the new firmware you will not have wifi
i thought i flashed the firmware first but didnt do it twice and it didnt stick. after the rom was installed i had no wifi but guessed that was the problem and re flashed the firmware. then it was ok.
as for cyanogenmod, unless it states it is for M8 Dual SIM then i wouldnt bother unless youve got time to experiment and hope for updates.
i know there are many arguments as to why you dont really need S-OFF for most normal operations but it a real fail-safe when things get messed up (my 2c)
just find the $25 for sunshine, its worth it.
gazzacbr said:
you can but you have to re-lock the boot loader which will wipe your phone.
i used these instructions (I am S-OFF already) and firmware from link on Maximus site:
-------------------------------------------------------
How to flash firmware
### If you are S-ON ---> Re-lock your bootloader (this will most probably wipe content of your device)
If you are S-OFF ---> no need to re-lock the bootloader.
Copy downloaded .zip to fastboot.exe location
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol DOWN + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
### Type: fastboot oem lock (if your device is not relocked yet or in case it's S-ON)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Flash firmware.zip again just to make sure.
Type: fastboot reboot-bootloader
-------------------------------------------------------
what i am sure of is that without the new firmware you will not have wifi
i thought i flashed the firmware first but didnt do it twice and it didnt stick. after the rom was installed i had no wifi but guessed that was the problem and re flashed the firmware. then it was ok.
as for cyanogenmod, unless it states it is for M8 Dual SIM then i wouldnt bother unless youve got time to experiment and hope for updates.
i know there are many arguments as to why you dont really need S-OFF for most normal operations but it a real fail-safe when things get messed up (my 2c)
just find the $25 for sunshine, its worth it.
Click to expand...
Click to collapse
Thanks for response. In the meantime I have gone S-OFF with Sunshine, but I have not yet flashed the new firmware or the ROM.
For firmware flashing, I was going to use the process described here on XDA. Seems very simple . . .
simonvfr said:
Thanks for response. In the meantime I have gone S-OFF with Sunshine, but I have not yet flashed the new firmware or the ROM.
For firmware flashing, I was going to use the process described here on XDA. Seems very simple . . .
Click to expand...
Click to collapse
But in the end I had to use the method you suggest, as once the ROM was installed I had no firmware and was therefore stuck in bootloader. With some fiddling I managed to sort it all out, and everything is now running.
Thanks for your help
Okay so, I had a problem of having no OS and had my htc m8 on soft brick for a while but i finally got that resolved by flashing a new rom on it. ( Here it is if you want to read: http://forum.xda-developers.com/htc-one-m8/help/os-installed-transfer-files-t3018626)
Unfortunately, I wasn't getting wifi on it. I tried 2 other roms and still no dice. I read online that i needed to update my firmware to do that. To do that, I needed to relock my bootloader so I did and the firmware flashed successfully.
Now my hboot is 3.19 instead of 3.16 and my bootloader says RELOCKED.However, when i go into recovery mode, my phone shows a picture of the dead android. I can't get past the bootscreen either so my phone is stuck on bootloader mode.
I found this guide: http://forum.xda-developers.com/showthread.php?t=2497712 to help me get my phone unlocked again cause the unlock code at htc dev wont work again.
However, when i write adb devices, no serial number shows up now. adb shell says no devices connected.
I tried pushing and flashing a new recovery and rom in cmd and it said it failed.
I'm really grasping at straws at this moment since I can't really do anything.
Are you sure you are updated? In the bootloader, what does it say for "os"?
And what roms are you trying to flash? 4.4.4 or Lollipop?
And to unlock bootloader, start over at HTC Dev. See what happens. Instead of trying old code.
You can't flash a recovery with a locked bootloader.
I'm pretty sure it updated because everything looks different. Bootloader's background is black instead of white now too. When I flashed the firmware, everything seemed to be okay as well. . .
my OS says 3.11.1700.5
and i tried it at dev and generated a code, but it gave me an error and didn't give me a file. I tried to use my old file but that didnt work.
Personally, in your situation now..... I'd flash the correct RUU for your device, then use Sunshine to s-off. Then you'll be bootloader unlocked also and can flash recovery, root and all that.
You'll need the same Android version RUU that matches your firmware now.
See this thread,
http://forum.xda-developers.com/showthread.php?t=2701376
Without Sunshine... I can't say why HTC Dev isn't helping.
Darth said:
Personally, in your situation now..... I'd flash the correct RUU for your device, then use Sunshine to s-off. Then you'll be bootloader unlocked also and can flash recovery, root and all that.
You'll need the same Android version RUU that matches your firmware now.
See this thread,
http://forum.xda-developers.com/showthread.php?t=2701376
Without Sunshine... I can't say why HTC Dev isn't helping.
Click to expand...
Click to collapse
Which RUU do I download from here? I'm confused.
Shiverfire said:
Which RUU do I download from here? I'm confused.
Click to expand...
Click to collapse
Read the whole first post. It tells you how to determine that.
Any help needed after trying, you can ask there. ?
I just asked. I'm too confused.
For reference:
version-bootloader: 3.19.0.0000
version-main: 3.11.1700.5
product: m8_ul_ca
modelid:0P6B12000
cidnum: CWS__001
Shiverfire said:
I just asked. I'm too confused.
For reference:
version-bootloader: 3.19.0.0000
version-main: 3.11.1700.5
product: m8_ul_ca
modelid:0P6B12000
cidnum: CWS__001
Click to expand...
Click to collapse
Adb only works in custom recovery or OS.
If your phone shows bootloader, use fastboot to flash custom recovery
SaHiLzZ said:
Adb only works in custom recovery or OS.
If your phone shows bootloader, use fastboot to flash custom recovery
Click to expand...
Click to collapse
I can't flash a recovery because the bootloader is Relocked. I can't unlock it cause my phone wont get detected in adb devices.
I tried manually updating drivers as well. :/
Shiverfire said:
I can't flash a recovery because the bootloader is Relocked. I can't unlock it cause my phone wont get detected in adb devices.
I tried manually updating drivers as well. :/
Click to expand...
Click to collapse
Have you tried flashing a recovery using Hasoon2000 HTC one all in one ?. I had the same problem as you i flashed TWRP then I installed android revolution Hd Rom and it solved my problem but as I said try it may not work as your boot loader is locked..... You can also use the all in one too unlock boot loader might be worth a try
Sent from my HTC One_M8 using XDA Free mobile app
mikem2273 said:
Have you tried flashing a recovery using Hasoon2000 HTC one all in one ?. I had the same problem as you i flashed TWRP then I installed android revolution Hd Rom and it solved my problem but as I said try it may not work as your boot loader is locked..... You can also use the all in one too unlock boot loader might be worth a try
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Like I said, recoveries wont flash cause its stuck on Relocked mode. I cant fix that because adb devices wont see my phone.
All the other commands on the All-in-One root kit gives me this:" 'C:\Users\Admin' is not an internal or external command, operable program or batch file " regardless of where i do it. I don't understand what I'm doing wrong here.
I tried to put the 0p6bimg.zip file but it wont copy on to my sd card cause of some error saying not responding or disconnected.
I tried flashing it instead but it said the file was too large
I tried the latest firmware but it said Failed! verification error.
I tried using the RUU to update and it stopped on the 1/7 process saying Error 155: Unknown Error.
I think what i need to do and how to fix it but I just need adb devices to find my phone.
If i can do that I can unlock my bootloader, install a recovery, install a rom and be home free but I can't do that until it detects my phone. I've tried everything now including reinstalling my drivers three times now.
Please help :'(
You don't need adb devices to see the device. You need to put the phone in the bootloader and type fastboot devices.
Open the command prompt inside the folder where also the fastboot.exe file is located.
Like Mr Hofs said...The bootloader gets unlocked in bootloader/fastboot mode.
Last I remember the code to get the token was "fastboot oem get_identifier_token" and "fastboot flash unlocktoken Unlock_code.bin and not "adb oem get_identifier_token" or "adb flash unlocktoken Unlock_code.bin ...
BerndM14 said:
Like Mr Hofs said...The bootloader gets unlocked in bootloader/fastboot mode.
Last I remember the code to get the token was "fastboot oem get_identifier_token" and "fastboot flash unlocktoken Unlock_code.bin and not "adb oem get_identifier_token" or "adb flash unlocktoken Unlock_code.bin ...
Click to expand...
Click to collapse
No, you guys. I already said this. I already used the htc dev the first time to get my phone unlocked. I had to relock it to flash a firmware. Now I can't unlock it again.The token isn't working. I already used the token once and its not working for the second time. I need adb devices to use adb shell. That way I can adb push revone and unlock my bootloader, but im not sure if that would work either.
Edit: I tried htc dev by generating a code 3 times. It generated different ones, the last one worked.
Ok something is still wrong.
I flashed cwm 6.0.4.8, did a full wipe, installed supersu and installed the android revolution rom. When I reboot, it says I am not rooted, root now? I pressed yes and it reboot.
The phone goes into htc bootscreen for 2 minutes, reboots again and then goes into recovery mode. What do I do now?
Shiverfire said:
Ok something is still wrong.
I flashed cwm 6.0.4.8, did a full wipe, installed supersu and installed the android revolution rom. When I reboot, it says I am not rooted, root now? I pressed yes and it reboot.
The phone goes into htc bootscreen for 2 minutes, reboots again and then goes into recovery mode. What do I do now?
Click to expand...
Click to collapse
Try flashing the boot.img again.
Clear the Cache.
If it still doesn't work then it might be best to just flash the ROM again.
Is your bootloader still show GPE version no. ?
If yes, how do you expect to flash a Sense ROM on GPE partition ?
BerndM14 said:
Try flashing the boot.img again.
Clear the Cache.
If it still doesn't work then it might be best to just flash the ROM again.
Click to expand...
Click to collapse
just flashed the boot.img and recovery.
cleared cashe and reinstalled super su.
same thing.
ckpv5 said:
Is your bootloader still show GPE version no. ?
If yes, how do you expect to flash a Sense ROM on GPE partition ?
Click to expand...
Click to collapse
wait, how do i know if its GPE? (I didnt buy a GPE phone)
I was able to download skydragon and android revolution before, the former was stock lollipop.
So what do I do? how do i install sense roms??
I need an HTC One M8 Telus/Koodo RUU for my phone. I flashed GPE Rom and it works great but i want the 5.0 update of my carrier but i can't flash it because i am on a custom rom so i would like to revert back to stock in order to flash the 5.0 update.
Any help or suggestion would be appreciated
marawan31 said:
I need an HTC One M8 Telus/Koodo RUU for my phone. I flashed GPE Rom and it works great but i want the 5.0 update of my carrier but i can't flash it because i am on a custom rom so i would like to revert back to stock in order to flash the 5.0 update.
Any help or suggestion would be appreciated
Click to expand...
Click to collapse
Go back to stock, and take the OTAs. Then re-root and enjoy your new firmware.
Visit this thread:
http://forum.xda-developers.com/showthread.php?t=2701376
or this thread:
http://forum.xda-developers.com/showthread.php?t=2710735
I cant do that because i am not s-off
marawan31 said:
I cant do that because i am not s-off
Click to expand...
Click to collapse
Incorrect. This is the method that you use if you are not S-Off.
If you were S-Off, you would just update firmware manually, with no need to go back to stock.
thanks for your help!
ok the second link you posted led me to a canadian nandroid backup.
thanks a lot for your help man
Edit: my hboot is 3.18 and its the only one missing
what should i do?
marawan31 said:
thanks for your help!
ok the second link you posted led me to a canadian nandroid backup.
thanks a lot for your help man
Edit: my hboot is 3.18 and its the only one missing
what should i do?
Click to expand...
Click to collapse
I would suggest asking if anyone has a link to one in that thread.
I'm on Telus too, but I am running WWE firmware. I ALWAYS have the new firmware before Telus. Just sayin.
S-Off is a good thing to have. I know it seems like $25 is a lot to pay to get it, but if you think of all the hassle it saves trying to update firmware, and the other freedom it gives you (I'm using the Sprint Harman/Kardon version's audio files and ADSP) it is very reasonably priced.
xunholyx said:
I would suggest asking if anyone has a link to one in that thread.
I'm on Telus too, but I am running WWE firmware. I ALWAYS have the new firmware before Telus. Just sayin.
S-Off is a good thing to have. I know it seems like $25 is a lot to pay to get it, but if you think of all the hassle it saves trying to update firmware, and the other freedom it gives you (I'm using the Sprint Harman/Kardon version's audio files and ADSP) it is very reasonably priced.
Click to expand...
Click to collapse
i just flashed the one saying 3.x. its a 5.0 nandroid backup and all is working except wifi for some weird reason. looks like the firmware wasnt updated.
i have nothing against paying 25$ its just that sunshine never worked for me. It always said it didnt like my kernel and that i should try with a stock and i was too lazy tbh
marawan31 said:
i just flashed the one saying 3.x. its a 5.0 nandroid backup and all is working except wifi for some weird reason. looks like the firmware wasnt updated.
i have nothing against paying 25$ its just that sunshine never worked for me. It always said it didnt like my kernel and that i should try with a stock and i was too lazy tbh
Click to expand...
Click to collapse
Use 3.34.661.4 backup for 4.4.4 but wifi will not work on your device yet because you have hboot 3.18.0000
Find the 2.23.661.2 -> 3.34.661.4 - thanks @shaboobla on this thread : http://forum.xda-developers.com/showthread.php?t=2701376
Extract out firmware.zip from that OTA zip (with 7-zip)
then you can flash this firmware in RUU mode (but you need to relock bootloader because your device is S-On)
Later .. you can check software update and accept OTA to 4.20.661.2
ckpv5 said:
Use 3.34.661.4 backup for 4.4.4 but wifi will not work on your device yet because you have hboot 3.18.0000
Find the 2.23.661.2 -> 3.34.661.4 - thanks @shaboobla on this thread : http://forum.xda-developers.com/showthread.php?t=2701376
Extract out firmware.zip from that OTA zip (with 7-zip)
then you can flash this firmware in RUU mode (but you need to relock bootloader because your device is S-On)
Later .. you can check software update and accept OTA to 4.20.661.2
Click to expand...
Click to collapse
how would i flash a firmware in RUU mode? you mean like renaming it to some weird name like PG.... and placing it in root of sdcard and going in fasboot? or is it something else because tbh i have never heard of flashing something in RUU mode
thanks for your help, really appreciate it.
EDIT: I just found out i can go to RUU mode with "fastboot oem rebootRUU".
so i can flash the firmware with "fastboot flash zip firmware.zip"
thanks again for all your help guys
marawan31 said:
how would i flash a firmware in RUU mode? you mean like renaming it to some weird name like PG.... and placing it in root of sdcard and going in fasboot? or is it something else because tbh i have never heard of flashing something in RUU mode
thanks for your help, really appreciate it.
EDIT: I just found out i can go to RUU mode with "fastboot oem rebootRUU".
so i can flash the firmware with "fastboot flash zip firmware.zip"
thanks again for all your help guys
Click to expand...
Click to collapse
You found it
1. Make sure you restore the 3.34.661.4 backup first and reboot
2. Boot to bootloader
3. relock bootloader - fastboot oem lock
4. flash the firmware in RUU mode
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <---- again for the 2nd time
fastboot reboot
5. check software update
6. accept, download, install
7. done
Flash TWRP 2.8.5.0 if you want to flash a custom ROM
ckpv5 said:
You found it
1. Make sure you restore the 3.34.661.4 backup first and reboot
2. Boot to bootloader
3. flash the firmware in RUU mode
fastboot oem rebootRUU
fastboot flash zip hbootMOD3.zip
fastboot flash zip hbootMOD3.zip <---- again for the 2nd time
fastboot reboot
4. check software update
5. accept, download, install
6. done
Flash TWRP 2.8.5.0 if you want to flash a custom ROM
Click to expand...
Click to collapse
You renamed the firmware to hbootMOD3.zip? or do i also need to flash the hboot? if so which hboot do i flash?
lol sorry im easily confused
marawan31 said:
You renamed the firmware to hbootMOD3.zip? or do i also need to flash the hboot? if so which hboot do i flash?
lol sorry im easily confused
Click to expand...
Click to collapse
Ahh.. sorry ... I was in a hurry ... just copy paste from my own note that meant for my personal modded firmware. Edited the post.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <---- again for the 2nd time
fastboot reboot
ckpv5 said:
Ahh.. sorry ... I was in a hurry ... just copy paste from my own note that meant for my personal modded firmware. Edited the post.
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip <---- again for the 2nd time
fastboot reboot
Click to expand...
Click to collapse
oh ok thanks man!!
ill post back with the result
marawan31 said:
oh ok thanks man!!
ill post back with the result
Click to expand...
Click to collapse
Just don't forget to relock bootloader before flashing firmware.zip
fastboot oem lock
ckpv5 said:
Just don't forget to relock bootloader before flashing firmware.zip
fastboot oem lock
Click to expand...
Click to collapse
yea i was going to do it and also for the sake of completeness flashing the stock recovery(3.34.661.4) after the restore, just in case someone else has the same problem
You can do that but not really needed because the signed firmware.zip will restore stock recovery.
ckpv5 said:
You can do that but not really needed because the signed firmware.zip will restore stock recovery.
Click to expand...
Click to collapse
oh didnt know that, i guess i wont then
I just wanted to thank you guys for helping me out!
I did everything and now i am on android 5.0.1 (although i ran into a small problem: process com.android.phone is not responding, factory reset from recovery fixed it)
Hope this thread helps someone else with similar problems
https://photos.google.com/album/AF1QipNmb1q2tT6uldWZLHQSLD1fsauQYRMlkHmA5y1g/photo/AF1QipPXGvhZ063BpX0f30U4O7d6ZYQgTkgeowCWDywd
Sorry for reviving such an old thread, but I'm trying to get my htc one m8 up and running again. It was functioning on lineage os but wasn't very stable, couldn't find any other roms that would successfully flash on it, I decided to try and go back to stock after a few beers one night night, now the phone has been sitting in a drawer with no os or recovery on it. There doesn't seem to be any still functioning links to any Canadian RUU's that I can use. I'm not s-off, bootloader is "relocked". I'd like to go back to stock marshmallow because I only use this thing to play music and as a tv remote. I'm hoping someone might have an old RUU lying around.
I guess if not my best option is just to unlock the bootloader again and try flashing the same lineage os again. Since I relocked does that mean I have to go through the htc website to get the unlock token again like I did ages ago? They probably don't even have this phone on there anymore. Hopefully I didn't actually turn this thing into a brick.
Please see my comments in red font below:
350Rocket said:
https://photos.google.com/album/AF1QipNmb1q2tT6uldWZLHQSLD1fsauQYRMlkHmA5y1g/photo/AF1QipPXGvhZ063BpX0f30U4O7d6ZYQgTkgeowCWDywd
Photo link is coming up with 404 error for me. Better to do fastboot getvar all, then post the results (cut and paste from command prompt), so we can see all the info on the phone (delete IMEI and serial number before posting).
Sorry for reviving such an old thread, but I'm trying to get my htc one m8 up and running again. It was functioning on lineage os but wasn't very stable, couldn't find any other roms that would successfully flash on it,
If you can be more specific about which ROMs you tried (plus info about your device from getvar as noted above), then we might be able to advise why they did not flash. Did you get error messages, and if so, what exactly were they?
I decided to try and go back to stock after a few beers one night night, now the phone has been sitting in a drawer with no os or recovery on it.
What exactly did you do (step by step, with any relevant file names, etc. - more detail is better).
I presume you intentionally relocked the bootloader in attempt to run some RUU. But would like clarification on this (and where that happened in the sequence of events)
There doesn't seem to be any still functioning links to any Canadian RUU's that I can use. I'm not s-off, bootloader is "relocked". I'd like to go back to stock marshmallow because I only use this thing to play music and as a tv remote. I'm hoping someone might have an old RUU lying around.
Far as I know, Canadian versions don't have RUU.
I guess if not my best option is just to unlock the bootloader again and try flashing the same lineage os again. Since I relocked does that mean I have to go through the htc website to get the unlock token again like I did ages ago? They probably don't even have this phone on there anymore. Hopefully I didn't actually turn this thing into a brick.
One option (maybe the best one) is to restore a stock TWRP back from the collection: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You will need to unlock the bootloader to do this. You can either reuse the unlock bin code you used originally (if you still have it). Otherwise, you should be able to request a new bin code from HTCDev.com. Far as I know, that still works for this phone.
Click to expand...
Click to collapse
Hello,
so I got the HTC 10 from my brother but I can not get the latest updates via OTA. Reason: Bootload unlocked und TWRP Recovery.
Now I wanna relock the bootloader and back to the Stock Recovery in order to get the OTA upates. I found files in the thread but I do not really know how to proceed at all
Is there any step by step guide for this situation which a newbie would understand?
Some Info's to the phone itself:
Recovery: TWRP 3.03-10_Unofficial
S-On
Unlocked Bootloader
CID: HTC_034
Android 7.0, January Security update
Software: 2.41.401.4
Kernel: 3.18.31-perf-g9ec8cbc and @aabm#1 SMP PREEMPT
Baseband: [email protected]_79.07_F
Is there any way to simply flash the stock recovery again put the bootloader to locked and then get the OTA?
Any help is appreciated
(And no can not ask my brother as he is for several months abroad)
pyo[st said:
;73891974]Hello,
so I got the HTC 10 from my brother but I can not get the latest updates via OTA. Reason: Bootload unlocked und TWRP Recovery.
Now I wanna relock the bootloader and back to the Stock Recovery in order to get the OTA upates. I found files in the thread but I do not really know how to proceed at all
Is there any step by step guide for this situation which a newbie would understand?
Some Info's to the phone itself:
Recovery: TWRP 3.03-10_Unofficial
S-On
Unlocked Bootloader
CID: HTC_034
Android 7.0, January Security update
Software: 2.41.401.4
Kernel: 3.18.31-perf-g9ec8cbc and @aabm#1 SMP PREEMPT
Baseband: [email protected]_79.07_F
Is there any way to simply flash the stock recovery again put the bootloader to locked and then get the OTA?
Any help is appreciated
(And no can not ask my brother as he is for several months abroad)
Click to expand...
Click to collapse
Bootloader status does not affect ability to take OTAs.
You need two things mainly to take the OTA:
1. Stock recovery matching your current software
2. An untouched backup image of the system partition matching your current software. This is needed if you're currently rooted.
Both can probably be found in the thread you linked. The backup image is flashed from twrp. The stock recovery is then flashed from download mode using this command:
Fastboot flash recovery yourrecoveryfile.img
But even after doing that, you might still get an error when trying to take the OTA. Easiest way to take it is to start from scratch, backup your phone's contents to your pc or sd card, and then run the latest ruu for your phone. This will bring you up to date, and will also allow you to make a backup system image from twrp before rooting so that you can easily take future OTAs. The ruu will also completely wipe your phone's contents.
So you can try the first method I mentioned, and if it doesn't work go with the ruu.
As your brother may root it before so the system may got modify, in this case the best and easiest way is flash a RUU.
Try this RUU, http://dl3.htc.com/application/[email protected]_79.07_F_release_495903_signed_2.exe
A RUU will restore your HTC 10 back to stock and wipe out everything. It require a match CID or super CID, if not it will not flash.
I tried to flash RUU via sd card method as well as fastboot method. Both got failed
sd card: Header Error
fastboot: load_file: could not allocate 1950335038 bytes
error: cannot load '2PS6IMG.zip'
Im running on venom rom , S ON with oem unlocked. How can i go back to stock rom??
Mine is 2.41.401.41
DummyPLUG said:
As your brother may root it before so the system may got modify, in this case the best and easiest way is flash a RUU.
Try this RUU, LINK
A RUU will restore your HTC 10 back to stock and wipe out everything. It require a match CID or super CID, if not it will not flash.
Click to expand...
Click to collapse
This RUU worked perfectly. And no the phone was not rooted, just unlocked Bootloader and TWRP as Recovery.
After flashing the RUU I got the July Security Patch and that is what I wanted.
Thank you very much, Problem solved
$tark3 said:
I tried to flash RUU via sd card method as well as fastboot method. Both got failed
sd card: Header Error
fastboot: load_file: could not allocate 1950335038 bytes
error: cannot load '2PS6IMG.zip'
Im running on venom rom , S ON with oem unlocked. How can i go back to stock rom??
Mine is 2.41.401.41
Click to expand...
Click to collapse
It is a EXE, you should run on windows instead of using the sdcard method, as for the not enough space I am not sure about
DummyPLUG said:
It is a EXE, you should run on windows instead of using the sdcard method, as for the not enough space I am not sure about
Click to expand...
Click to collapse
Nah, i downloaded the exe and the zip file also.
Anyway fixed it. Just restored from a nandroid backup. Now back in stock
PS:In btw, anyone facing any battery drop issue??
So I run in another Problem. I got the latest OTA for Europe (July Security Patch) but now my Phone gets shown as uncertified in the google play app which means I can not download certain apps like Netflix via Appstore.
Now I already figured out why I get shown uncertified: the Bootload is still unlocked. I thought the RUU would fix this as well. And if I wanna go in to the recovery (there was an TWRP Recovery on it before) I just get a red triangle with an "!" in it. It wont boot into recovery. Had to hard reset the phone to be able to boot normally to android then.
Now I wanna flash the stock recovery and lock the Bootload again to get again the certified status from google again.
Now here I need help.
1. Can't find the matching recovery version (EU unlocked, July Securtiy Patch, 2.41.401.41). Can anyone help me find the recovery image I need?
2. How do I get the bootload locked again? My Brother unlocked it via HTCdev.com back then, that I know already. But the command fastboot oem lock does not work at all. It just does nothing.
So how can I lock the bootloader?
Thanks for the help.
If you ran the RUU you already have stock recovery...red triangle with an "!" in it.
Are you running the fastboot oem lock from bootloader or download mode?
Sloth said:
If you ran the RUU you already have stock recovery...red triangle with an "!" in it.
Are you running the fastboot oem lock from bootloader or download mode?
Click to expand...
Click to collapse
Haha well then everything is ok with the recovery ^^
I tried both (download and bootloader mode), both times nothing happens. In download mode my PC does not even recognize the phone as the command "adb devices" does not list my phone and the command "fastboot oem lock" does nothing. HTCsnyc installed and ofc adb shell, worked even as when I normally checked with adb devices when my phone was on it was recognized.
pyo[st] said:
Haha well then everything is ok with the recovery ^^
I tried both (download and bootloader mode), both times nothing happens. In download mode my PC does not even recognize the phone as the command "adb devices" does not list my phone and the command "fastboot oem lock" does nothing. HTCsnyc installed and ofc adb shell, worked even as when I normally checked with adb devices when my phone was on it was recognized.
Click to expand...
Click to collapse
Try fastboot devices
Sent from a Glade Plugin.
Sloth said:
If you ran the RUU you already have stock recovery...red triangle with an "!" in it.
Are you running the fastboot oem lock from bootloader or download mode?
Click to expand...
Click to collapse
Sloth said:
Try fastboot devices
Sent from a Glade Plugin.
Click to expand...
Click to collapse
Alright this command works and shows my device.
Now I am in bootloader (Shows Software Status: Modified; Unlocked, S-ON). Then I type in "fastboot oem lock" and I get:
FAILED (remote: unknown command)
finished. total time: 0.014s
Well at least now I get something, before just nothing happened. Any clue what I might do wrong here?
*edit*
So I am a big noob
Phone has to be in download mode then the command works and my phone shows me a message if I want to lock again. Unfortunately it will factory reset my phone as well (at least it says that) so I have to backup my data (again) first.
But thank you for your help, appreciate it.
Cheers!
So I did lock the phone again and flashed again the RUU.exe BUT again my Phone shows in Bootloader Software Status as Modified...and it shows as Relocked.
So how do I get it to official status again?
pyo[st said:
;74318325]So I did lock the phone again and flashed again the RUU.exe BUT again my Phone shows in Bootloader Software Status as Modified...and it shows as Relocked.
So how do I get it to official status again?
Click to expand...
Click to collapse
By buying sunshine S-OFF. Only way to see the bootloader back to "locked" instead of "relocked"
Mr Hofs said:
By buying sunshine S-OFF. Only way to see the bootloader back to "locked" instead of "relocked"
Click to expand...
Click to collapse
Ye found a thread to it. But seems I dont need it. My Phone gets shown as certified again at google play store so I assume just "relocking" the bootloader seems to be enough.
.....