I tried rooting my device and at last I was succesfull but now I want to install the latest ROM but to install that I need to upgrade my hboot and I am not getting how to do that please somebody help me my phone is in S-ON mode and it's an At&t international version phone
sheikharfaz said:
I tried rooting my device and at last I was succesfull but now I want to install the latest ROM but to install that I need to upgrade my hboot and I am not getting how to do that please somebody help me my phone is in S-ON mode and it's an At&t international version phone
Click to expand...
Click to collapse
post the result of fastboot getvar all ( after removing serialno and mei )
sheikharfaz said:
I tried rooting my device and at last I was succesfull but now I want to install the latest ROM but to install that I need to upgrade my hboot and I am not getting how to do that please somebody help me my phone is in S-ON mode and it's an At&t international version phone
Click to expand...
Click to collapse
Your sequence is a bit mixed up. You should have updated firmware (hboot, radio, etc.) before unlocking bootloader. As you'll now have to relock the bootloader in order to update firmware. Then unlock it again, and TWRP again, to install custom ROM.
You also do not need root to flash custom ROMs (just need unlocked bootloader, custom recovery, and right firmware); unless you had another specific reason to root first?
Also, you will want all the updated firmware, not just hboot. As firmware contains a bunch of modules besides hboot, which will not play well with current ROMs (especially WiFi, Bluetooth, as well as radio and others). All the firmware installs in one zip, so it's not hard to do.
However, I agree with the previous post that we need more info on the phone. Fastboot getvar all, and post the results (delete IMEI and serial number before posting).
"At&t international version" is a contradiction. It's either one or the other, it can't be both.
redpoint73 said:
You should have updated firmware (hboot, radio, etc.) before unlocking bootloader. As you'll now have to relock the bootloader in order to update firmware.
Click to expand...
Click to collapse
Here's something I just learned recently (2 or 3 mos ago), although I haven't been able to test it myself since my M8 is S-Off.
When flashing an RUU.zip or signed firmware.zip from extSD instead of from your PC, relocking your bootloader isn't necessary.
Like I said, I haven't confirmed it myself, but the person who told me that I consider a reliable source. He was positive about it with M9, and quite sure it was the same with the M8.
redpoint73 said:
Your sequence is a bit mixed up. You should have updated firmware (hboot, radio, etc.) before unlocking bootloader. As you'll now have to relock the bootloader in order to update firmware. Then unlock it again, and TWRP again, to install custom ROM.
You also do not need root to flash custom ROMs (just need unlocked bootloader, custom recovery, and right firmware); unless you had another specific reason to root first?
Also, you will want all the updated firmware, not just hboot. As firmware contains a bunch of modules besides hboot, which will not play well with current ROMs (especially WiFi, Bluetooth, as well as radio and others). All the firmware installs in one zip, so it's not hard to do.
However, I agree with the previous post that we need more info on the phone. Fastboot getvar all, and post the results (delete IMEI and serial number before posting).
"At&t international version" is a contradiction. It's either one or the other, it can't be both.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.58.502.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.037s
redpoint73 said:
Your sequence is a bit mixed up. You should have updated firmware (hboot, radio, etc.) before unlocking bootloader. As you'll now have to relock the bootloader in order to update firmware. Then unlock it again, and TWRP again, to install custom ROM.
You also do not need root to flash custom ROMs (just need unlocked bootloader, custom recovery, and right firmware); unless you had another specific reason to root first?
Also, you will want all the updated firmware, not just hboot. As firmware contains a bunch of modules besides hboot, which will not play well with current ROMs (especially WiFi, Bluetooth, as well as radio and others). All the firmware installs in one zip, so it's not hard to do.
However, I agree with the previous post that we need more info on the phone. Fastboot getvar all, and post the results (delete IMEI and serial number before posting).
"At&t international version" is a contradiction. It's either one or the other, it can't be both.
Click to expand...
Click to collapse
Can i get what next i can do?
because i am not able to find the right firmware.Can you help me with that?
sheikharfaz said:
Can i get what next i can do?
because i am not able to find the right firmware.Can you help me with that?
Click to expand...
Click to collapse
remove serialno from the getvar result in your post above
i don't know what you want
you need the latest firmware to flash a custom rom or you need to flash the latest stock rom ( by using RUU ) ???
in all cases you need to flash the latest firmware first 6.20.502.5 ( it's the latest firmware for your AT&T device variant )
6.20.502.5 is marshmallow and it's the latest official OS for this device
note :- flashing the signed firmware will wipe your internal storage so make sure to backup your files
flash firmware
1-download this signed firmware https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU ( rename it to something short and easy if you like )
2- open a cmd window in the folder where the firmware located
3- relock the bootloader ( if it's unlocked ) by this commands
fastboot oem lock
fastboot reboot-bootloader
3- now start flashing the firmware using this commands and replace firmwarename with the actual firmware name
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
then repeat the flashing command again
fastboot flash zip firmwarename.zip
after it complete type
fastboot reboot-bootloader
flash custom rom
now you have the latest firmware if you want to flash a custom rom unlock the bootloader and flash twrp then flash the desired rom
flash stock rom using RUU.exe
if you want the latest stock rom RUU.exe it's available on htc website here http://www.htc.com/us/support/htc-one-m8-att/news/
direst link for the RUU http://dl3.htc.com.s3.amazonaws.com...70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
after flash the firmware and do all the above commands run the RUU as a normal application and follow the setup wizard
sheikharfaz said:
(bootloader) version-main: 1.58.502.1
Click to expand...
Click to collapse
As suspected, you need to update all the firmware, not just hboot. Your firmware is still on the original 2014 release of Kitkat. This will cause many issues, even if you updated hboot. For instance, you would find WiFi would be broken on just about every current custom ROM around; due to the WiFi firmware partition on the phone being outdated, and not compatible with the current ROMs.
ahmed has the process outlined well. I would recommend to follow his instructions above.
ahmed.ismael said:
remove serialno from the getvar result in your post above
i don't know what you want
you need the latest firmware to flash a custom rom or you need to flash the latest stock rom ( by using RUU ) ???
in all cases you need to flash the latest firmware first 6.20.502.5 ( it's the latest firmware for your AT&T device variant )
6.20.502.5 is marshmallow and it's the latest official OS for this device
note :- flashing the signed firmware will wipe your internal storage so make sure to backup your files
flash firmware
1-download this signed firmware https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU ( rename it to something short and easy if you like )
2- open a cmd window in the folder where the firmware located
3- relock the bootloader ( if it's unlocked ) by this commands
fastboot oem lock
fastboot reboot-bootloader
3- now start flashing the firmware using this commands and replace firmwarename with the actual firmware name
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
then repeat the flashing command again
fastboot flash zip firmwarename.zip
after it complete type
fastboot reboot-bootloader
flash custom rom
now you have the latest firmware if you want to flash a custom rom unlock the bootloader and flash twrp then flash the desired rom
flash stock rom using RUU.exe
if you want the latest stock rom RUU.exe it's available on htc website here http://www.htc.com/us/support/htc-one-m8-att/news/
direst link for the RUU http://dl3.htc.com.s3.amazonaws.com...70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
after flash the firmware and do all the above commands run the RUU as a normal application and follow the setup wizard
Click to expand...
Click to collapse
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
what does this mean ? which image should i flash?
sheikharfaz said:
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
what does this mean ? which image should i flash?
Click to expand...
Click to collapse
just do "fastboot flash zip *whatever you renamed it to*.zip" a second time without rebooting
ahmed.ismael said:
remove serialno from the getvar result in your post above
i don't know what you want
you need the latest firmware to flash a custom rom or you need to flash the latest stock rom ( by using RUU ) ???
in all cases you need to flash the latest firmware first 6.20.502.5 ( it's the latest firmware for your AT&T device variant )
6.20.502.5 is marshmallow and it's the latest official OS for this device
note :- flashing the signed firmware will wipe your internal storage so make sure to backup your files
flash firmware
1-download this signed firmware https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU ( rename it to something short and easy if you like )
2- open a cmd window in the folder where the firmware located
3- relock the bootloader ( if it's unlocked ) by this commands
fastboot oem lock
fastboot reboot-bootloader
3- now start flashing the firmware using this commands and replace firmwarename with the actual firmware name
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
then repeat the flashing command again
fastboot flash zip firmwarename.zip
after it complete type
fastboot reboot-bootloader
flash custom rom
now you have the latest firmware if you want to flash a custom rom unlock the bootloader and flash twrp then flash the desired rom
flash stock rom using RUU.exe
if you want the latest stock rom RUU.exe it's available on htc website here http://www.htc.com/us/support/htc-one-m8-att/news/
direst link for the RUU http://dl3.htc.com.s3.amazonaws.com...70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
after flash the firmware and do all the above commands run the RUU as a normal application and follow the setup wizard
Click to expand...
Click to collapse
i am not able to unlock my device back
E:\new\android-sdk-windows\platform-tools>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1826418688 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.133s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.144s
ahmed.ismael said:
remove serialno from the getvar result in your post above
i don't know what you want
you need the latest firmware to flash a custom rom or you need to flash the latest stock rom ( by using RUU ) ???
in all cases you need to flash the latest firmware first 6.20.502.5 ( it's the latest firmware for your AT&T device variant )
6.20.502.5 is marshmallow and it's the latest official OS for this device
note :- flashing the signed firmware will wipe your internal storage so make sure to backup your files
flash firmware
1-download this signed firmware https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU ( rename it to something short and easy if you like )
2- open a cmd window in the folder where the firmware located
3- relock the bootloader ( if it's unlocked ) by this commands
fastboot oem lock
fastboot reboot-bootloader
3- now start flashing the firmware using this commands and replace firmwarename with the actual firmware name
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
then repeat the flashing command again
fastboot flash zip firmwarename.zip
after it complete type
fastboot reboot-bootloader
flash custom rom
now you have the latest firmware if you want to flash a custom rom unlock the bootloader and flash twrp then flash the desired rom
flash stock rom using RUU.exe
if you want the latest stock rom RUU.exe it's available on htc website here http://www.htc.com/us/support/htc-one-m8-att/news/
direst link for the RUU http://dl3.htc.com.s3.amazonaws.com...70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
after flash the firmware and do all the above commands run the RUU as a normal application and follow the setup wizard
Click to expand...
Click to collapse
stuck in bootloop after locking the device
i accidently mistyped fastboot reboot instead of fastboot reboot-bootloader
what shall i do now
xunholyx said:
just do "fastboot flash zip *whatever you renamed it to*.zip" a second time without rebooting
Click to expand...
Click to collapse
stuck in bootloop
what can i do?please help
ahmed.ismael said:
remove serialno from the getvar result in your post above
i don't know what you want
you need the latest firmware to flash a custom rom or you need to flash the latest stock rom ( by using RUU ) ???
in all cases you need to flash the latest firmware first 6.20.502.5 ( it's the latest firmware for your AT&T device variant )
6.20.502.5 is marshmallow and it's the latest official OS for this device
note :- flashing the signed firmware will wipe your internal storage so make sure to backup your files
flash firmware
1-download this signed firmware https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU ( rename it to something short and easy if you like )
2- open a cmd window in the folder where the firmware located
3- relock the bootloader ( if it's unlocked ) by this commands
fastboot oem lock
fastboot reboot-bootloader
3- now start flashing the firmware using this commands and replace firmwarename with the actual firmware name
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
then repeat the flashing command again
fastboot flash zip firmwarename.zip
after it complete type
fastboot reboot-bootloader
flash custom rom
now you have the latest firmware if you want to flash a custom rom unlock the bootloader and flash twrp then flash the desired rom
flash stock rom using RUU.exe
if you want the latest stock rom RUU.exe it's available on htc website here http://www.htc.com/us/support/htc-one-m8-att/news/
direst link for the RUU http://dl3.htc.com.s3.amazonaws.com...70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
after flash the firmware and do all the above commands run the RUU as a normal application and follow the setup wizard
Click to expand...
Click to collapse
please send me next steps too.
sheikharfaz said:
stuck in bootloop
what can i do?please help
Click to expand...
Click to collapse
You flashed firmware first?
xunholyx said:
You flashed firmware first?
Click to expand...
Click to collapse
yes,now how do i come out of this bootloop ,there is nothing on screen except that htc logo
Okay. How long did you wait for it to boot up? I can take up to 20 mins sometimes. crazy I know
xunholyx said:
Okay. How long did you wait for it to boot up? I can take up to 20 mins sometimes. crazy I know
Click to expand...
Click to collapse
the battery got drained .so now i am able to get into bootloader .can i please get how to unloack bootloader .i have tried fastboot oem unlock and even
fastboot flash unlocktoken Unlock_code.bin
please help
sheikharfaz said:
the battery got drained .so now i am able to get into bootloader .can i please get how to unloack bootloader .i have tried fastboot oem unlock and even
fastboot flash unlocktoken Unlock_code.bin
please help
Click to expand...
Click to collapse
request another unlock_code
follow the steps to unlock the bootloader again on the hcdev website http://www.htcdev.com/bootloader/
sheikharfaz said:
can i please get how to unloack bootloader .i have tried fastboot oem unlock please help
Click to expand...
Click to collapse
This command doesn't work on the M8, it's not even worth trying. The whole point of the HTCDev.com bootloader unlock process, is due to the fact that HTC forbids unlocking the bootloader with that command. It only applies to certain devices.
You need to use the bin code command. If it doesn't work, just request a new bin code, like ahmed suggested.
Related
Hi guys,
Please help !
I've bought a new phone, htc one x, from someone. barely had time to install few apps, and got this OTA update message.
Without thinking twice - i did it. But it seems that the phone was rooted ! and as I understand now - it's a big no-no .
I've tried to figure out from the forum what to do , but - all the answers seems to include fastboot and ADB, which in turn require
the drivers of the phone to be installed. But my phone is dead ! so I can' t do it.
I'm new to roms and all, and I really need your help .
How can I make my phone work again ? I don't care which ROM , custom or stock , just to make it work .
Any help will be appreciated.
Gena
You can access Fastboot? Hold POWER and VOLUMEN - (down)..?
Sent from my HTC One X using Tapatalk 2
big noob said:
You can access Fastboot? Hold POWER and VOLUMEN - (down)..?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Hi , yes, I can access the fast boot, but even trying to restore to factory defaults didn't help.
And I can't istall the fastboot on my pc since it needs to connect to a working phone in debug mode (if I understand correctly)
Google Fastboot files
And place them on your pc..for example
On desktop..
C:\Users\Name\Desktop\
and next step go in that directory via CMD typr this
cd C:\Users\Name\Desktop\Fastboot\
And type this
Fastboot getvar cid
Then you will se your CID
go this thread and follow steps to recover your phone
http://forum.xda-developers.com/showthread.php?t=1975140
Sent from my HTC One X using Tapatalk 2
big noob said:
Google Fastboot files
And place them on your pc..for example
On desktop..
C:\Users\Name\Desktop\
and next step go in that directory via CMD typr this
cd C:\Users\Name\Desktop\Fastboot\
And type this
Fastboot getvar cid
Then you will se your CID
go this thread and follow steps to recover your phone
http://forum.xda-developers.com/showthread.php?t=1975140
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Thank you very much for your help.
I've did the steps as you say, and finally was able to "see" my phone in fastboot from PC.
but the CID I am getting is 11111111 , and there is no backup that matches it.
Can I overwrite it with some kind of rom ? I don't care to loose all the data, just to get a working phone.
Download clockwordmod recovery img file And flash it via Fastboot..
Fastboot flash recovery recoveryname.img
And then download this file:
Link!
And then access in recovery mount storage and copy that .zip file on your phone Clear and wipe everything except battery stats..And then flash that .zip file
genaddiy said:
Thank you very much for your help.
I've did the steps as you say, and finally was able to "see" my phone in fastboot from PC.
but the CID I am getting is 11111111 , and there is no backup that matches it.
Can I overwrite it with some kind of rom ? I don't care to loose all the data, just to get a working phone.
Click to expand...
Click to collapse
You are S-OFF you can install any RUU try with THIS ONE lock the bootloader and run the RUU as Administrator
post result from command fastboot getvar all and delete your S/N and IMEI from the info for any case
---------- Post added at 02:33 PM ---------- Previous post was at 02:32 PM ----------
big noob said:
Download clockwordmod recovery img file And flash it via Fastboot..
Fastboot flash recovery recoveryname.img
And then download this file:
Link!
And then access in recovery mount storage and copy that .zip file on your phone Clear and wipe everything except battery stats..And then flash that .zip file And try to flash it
Click to expand...
Click to collapse
He can't install OTA from recovery and you can't install OTA from recovery!!!!
Hi Thant, thank you for your help.
So you are saying that big noob's method won't work ?
I've downloaded the RUU, but I did not understand what you've meant by : "lock the bootloader" and when should I post the results of "fastboot getvar all" ? after I run the RUU , or before ?
You should post it before RUU..Well i tryed my method before and .zip flashed successfully..
And you can relock it with this command:
fastboot oem lock
Here's what I've got, no what should I do with it ?
>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.12.0000
(bootloader) version-baseband: 2.1204.135.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.401.2
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ461****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3821mV
(bootloader) devpower: 47
(bootloader) partition-layout: None
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.830s
You can relock your bootloader download RUU and run it as administrator
I tried to relock , but it said phone is already locked.
Then I ran RUU and got the following error :
ERROR [159] - The ROM update utility cannot update your Android phone. Please get the correct ROM Update Utility and try again .
But what is the correct for me ? and where do I get it ?
genaddiy said:
I tried to relock , but it said phone is already locked.
Then I ran RUU and got the following error :
ERROR [159] - The ROM update utility cannot update your Android phone. Please get the correct ROM Update Utility and try again .
But what is the correct for me ? and where do I get it ?
Click to expand...
Click to collapse
Try this one
And when you in bootloader what is writen up RELOCKED and ENDEAVORU XE or ENDEAVORU PVT
98552432 231
In the bootloader it says :
*** LOCKED *****
ENDEAVORU XE SHIP S-OFF RL
genaddiy said:
In the bootloader it says :
*** LOCKED *****
ENDEAVORU XE SHIP S-OFF RL
Click to expand...
Click to collapse
ENDEAVORU XE have problems with update you must manually update the firmware and after this to install RUU or custom rom.
Download THIS OTA open the zip and extract firmware.zip to your fastboot folder after this do this
Type: fastboot oem rebootRUU and wait for device to reboot you will see HTC logo
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
I want to thank you for your patience with a noob like me
I did everything till the last line.
After flashboot reboot, my phone passed the first htc logo that it was stuck on , but now it's stuck on htc one screen (the one with beats audio logo at the bottom) .
Do I need to do the flash custom rom recovery ?
genaddiy said:
I want to thank you for your patience with a noob like me
I did everything till the last line.
After flashboot reboot, my phone passed the first htc logo that it was stuck on , but now it's stuck on htc one screen (the one with beats audio logo at the bottom) .
Do I need to do the flash custom rom recovery ?
Click to expand...
Click to collapse
yes now flash custom recovery philz 5.15.x mount usb storage copy custom rom to the phone install and flash the boot.img and you will have working rom sense or no sense. Now after flash the firmware what is your hboot version 1.39? If yes you are ready to go
ok , just to make sure I understand before I do it a screw something up :
"yes now flash custom recovery philz 5.15.x mount usb storage copy custom rom to the phone install and flash the boot.img and you will have working rom sense or no sense. Now after flash the firmware what is your hboot version 1.39? If yes you are ready to go"
my hboot version is indeed 1.39
so I d/l philz custom recovery .
no I should :
fastboot flash zip philz_touch_6.07.9-endeavoru.zip
then go to the custom recovery ? (how ? ? ? )
then d/l some custom rom (any recomendations ? just a good stable one, possibly stock)
then copy it to phone using fastboot
and then , from custom recovery flash it ?
I'm sorry for all these questions, but I'm afraid to touch the damn thing already ))))
Flash the recovery (its a img file NOT a zip, take out the img if its in the zip)
Fastboot flash recovery recoveryname.img
Fastboot erase cache
Enter the recovery by selecting FASTBOOT in the bootloader and then RECOVERY (navigate with the volume buttons and confirm with the power button)
Go to the mounts and storage menu and mount the sdcard as a mass storage disk (wait a few minutes until it pops up on the pc)
Copy the rom.zip to the sdcard. Take out the boot.img and flash it via fastboot
Fastboot flash boot boot.img
Fastboot erase cache
Enter recovery again and perform a full wipe
Factory reset
Wipe cache partition
Advanced-wipe dalvik cache
Mounts and storage-format cache, data and system
Install the rom.zip
Done !
Roms....just check the android dev section. Many roms to choose and read up for yourself. It's not that difficult ...maximus and arhd are very close to stock.
Thank you for the detailed reply !
When doing Fastboot flash recovery recoveryname.img I got the messege :
FAILED <remote : not allowed>
Is the problem that my phone is locked ? (written locked at the top of fastboot screen) tried to do fastboot oem unlock but getting "Command error !" .
I saw this solution : http://forum.cyanogenmod.com/topic/74316-a-solution-to-fastboot-flash-recovery-not-allowed-error/ , but I'm not sure it will fit my phone (as it talkes about a different one) and what is a PD98IMG.zip file ?
Need some help I am having a lot of bugs with my m8. It is on bluegrass cellular. Does anyone know what ruu I can use to restore to stock. I am s off and unlocked cid LRA__001 model I'd m8 wlv
Same here.
I too am in need of it so i can return back to stock.
Ameans4 said:
Need some help I am having a lot of bugs with my m8. It is on bluegrass cellular. Does anyone know what ruu I can use to restore to stock. I am s off and unlocked cid LRA__001 model I'd m8 wlv
Click to expand...
Click to collapse
If you have a stock backup, I have a stock recovery that should work for the LRA models, PM me. Since you're S-off you might take it to Bluegrass and ask them to flash it back to stock and start over again. S-off should stay after they've flashed.
I WOULD NOT use a Verizon or other LRA carrier RUU, since the radios and radio configurations are similar, but different enough that they will likely screw up your service.
durgis said:
If you have a stock backup, I have a stock recovery that should work for the LRA models, PM me. Since you're S-off you might take it to Bluegrass and ask them to flash it back to stock and start over again. S-off should stay after they've flashed.
I WOULD NOT use a Verizon or other LRA carrier RUU, since the radios and radio configurations are similar, but different enough that they will likely screw up your service.
Click to expand...
Click to collapse
hi,
can you help me with this i've messed up with my phone, didnt know its verizon, was assuming its GSM, but was unable to flash any custom rom except SkyDragon, so i thought its a firmware issue, got s-off and updated the firmware which caused radio to stop working, then figured out its verizon, flashed firmware from verizon as well but no luck, now i am not even able to flash any ROM, only AOSP or Verizon or SkyDragon intl boots the phone but then start rebooting every few minutes, radio not working so no calls no data, i am really stuck, there is not much help about this model, if there is a way to go back to stock i would like to go with that, any help would be appreciated.
attached is the screenshot of versions i had before when running fine.
following are the versions now
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.12.20.1211
version-cpld: None
version-microp: None
version-main: 4.17.605.5
version-misc: PVT SHIP S-OFF
serialno: xxxxxxxxxxxx
imei: xxxxxxxxxxxxxxx
imei2: Not Support
meid: xxxxxxxxxxxxxxxx
product: m8_wlv
platform: hTCBmsm8974
modelid: 0P6B17000
cidnum: GOOGL001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: f2489bd1
hbootpreupdate: 11
gencheckpt: 0
Thanks
genious_t said:
version-bootloader: 3.19.0.0000
version-baseband: 1.12.20.1211
version-main: 4.17.605.5
version-misc: PVT SHIP S-OFF
modelid: 0P6B17000
cidnum: GOOGL001
Click to expand...
Click to collapse
I believe you installed wrong firmware which is a modded GPE firmware. That's why you can't install most of the ROM now.
You need to put correct CID/MID or at least change the CID to SuperCID 11111111 and MID 0P6B20000
It's not easy to fix your device now as you already installed some other region rcdata.img that come with the wrong firmware.
Anyway .. try again the correct Verizon firmware after change of CID/MID
You'll be able to install any Verizon based ROM but your data connection may still have problem.
Or better to install Verizon 4.4.4 firmware then restore LRA US 3.31.512.2 nandroid backup then do OTA if there is one. Restore the backup I believe you'll get wifi working .. after OTA .. your data connection should be restored.
Code:
ro.build.description=3.31.512.2 CL395691 release-keys
ro.build.changelist=395691
ro.build.fingerprint=htc/lra_us/htc_m8wl:4.4.4/KTU84P/395691.2:user/release-keys
ro.build.characteristics=default
ro.build.project=M8_WL_K444_SENSE60_VZW_MR:395301
ro.build.sku=LRA US
ro.product.version=3.31.512.2
ro.build.languageremove=0
ro.build.sense.version=6.0
ro.build.version.htcsdk=HTCExt:HTCExtension_Sense60_443_4;SDK:6.25;hdkbase:19.2
ro.build.description=3.31.512.2 CL395691 release-keys
ro.build.fingerprint=htc/lra_us/htc_m8wl:4.4.4/KTU84P/395691.2:user/release-keys
ckpv5 said:
I believe you installed wrong firmware which is a modded GPE firmware. That's why you can't install most of the ROM now.
You need to put correct CID/MID or at least change the CID to SuperCID 11111111 and MID 0P6B20000
It's not easy to fix your device now as you already installed some other region rcdata.img that come with the wrong firmware.
Anyway .. try again the correct Verizon firmware after change of CID/MID
You'll be able to install any Verizon based ROM but your data connection may still have problem.
Or better to install Verizon 4.4.4 firmware then restore LRA US 3.31.512.2 nandroid backup then do OTA if there is one. Restore the backup I believe you'll get wifi working .. after OTA .. your data connection should be restored.
Code:
ro.build.description=3.31.512.2 CL395691 release-keys
ro.build.changelist=395691
ro.build.fingerprint=htc/lra_us/htc_m8wl:4.4.4/KTU84P/395691.2:user/release-keys
ro.build.characteristics=default
ro.build.project=M8_WL_K444_SENSE60_VZW_MR:395301
ro.build.sku=LRA US
ro.product.version=3.31.512.2
ro.build.languageremove=0
ro.build.sense.version=6.0
ro.build.version.htcsdk=HTCExt:HTCExtension_Sense60_443_4;SDK:6.25;hdkbase:19.2
ro.build.description=3.31.512.2 CL395691 release-keys
ro.build.fingerprint=htc/lra_us/htc_m8wl:4.4.4/KTU84P/395691.2:user/release-keys
Click to expand...
Click to collapse
sorry about that MID and CID actually was planning to go GPE so changed them but then read the forum and couldn't find a single success story of wlv going GPE so changed my mind.
CID is now super and MID is my original as you mentioned 0P6B20000
the problem is that i am unable to find the correct firmware for my phone. i spent 48 hours searching for it but no luck.
and dont have nandroid as well.
btw couldn't understand the code you have sent.
can you please help me with finding the correct firmware and nandroid or whatever is needed to get this phone working regardless of the version. have no problem going to the older version as well.
Thanks
genious_t said:
sorry about that MID and CID actually was planning to go GPE so changed them but then read the forum and couldn't find a single success story of wlv going GPE so changed my mind.
CID is now super and MID is my original as you mentioned 0P6B20000
the problem is that i am unable to find the correct firmware for my phone. i spent 48 hours searching for it but no luck.
and dont have nandroid as well.
btw couldn't understand the code you have sent.
can you please help me with finding the correct firmware and nandroid or whatever is needed to get this phone working regardless of the version. have no problem going to the older version as well.
Thanks
Click to expand...
Click to collapse
This should work for you.
http://forum.xda-developers.com/showpost.php?p=63236967&postcount=2361
xunholyx said:
This should work for you.
http://forum.xda-developers.com/showpost.php?p=63236967&postcount=2361
Click to expand...
Click to collapse
Already tried this, didn't help
I am on GSM this is CDMA I guess
genious_t said:
Already tried this, didn't help
I am on GSM this is CDMA I guess
Click to expand...
Click to collapse
Didn't realize you were GSM since you are trying to flash verizon firmware with a phone that has the same MID and product version.
If your phone is GSM, you could try flashing WWE/International firmware (4.16.401.10). That's what I am using on a Telus phone. MID for WWE is 0P6B10000, Telus is 0P6B16000. It works great.
I didn't change the MID, just switched to superCID and flashed the firmware. Your product version may not let it install, but it might and it won't brick you. You'll just get errors if it won't work. My product version was M8_UL_CAN and it changed to M8_UL after flashing the WWE firmware, so it might be worth giving a shot.
genious_t said:
can you please help me with finding the correct firmware and nandroid or whatever is needed to get this phone working regardless of the version. have no problem going to the older version as well.
Thanks
Click to expand...
Click to collapse
1. Install the 4.4.4 firmware that you can find here : http://forum.xda-developers.com/showpost.php?p=52017763&postcount=2
2. Restore the LRA_001 nandroid backup that you can find here : http://forum.xda-developers.com/showpost.php?p=58438595&postcount=14
Note : this nandroid is made with CWM and CMW recovery is included in the zip.
3. After restore, boot and check for OTA. You may not have data connection but you should have wifi connection.
4. After the OTA installation, you should get your data connection back.
Good Luck
ckpv5 said:
1. Install the 4.4.4 firmware that you can find here : http://forum.xda-developers.com/showpost.php?p=52017763&postcount=2
2. Restore the LRA_001 nandroid backup that you can find here : http://forum.xda-developers.com/showpost.php?p=58438595&postcount=14
Note : this nandroid is made with CWM and CMW recovery is included in the zip.
3. After restore, boot and check for OTA. You may not have data connection but you should have wifi connection.
4. After the OTA installation, you should get your data connection back.
Good Luck
Click to expand...
Click to collapse
Thanks bro, trying this now
ckpv5 said:
1. Install the 4.4.4 firmware that you can find here : http://forum.xda-developers.com/showpost.php?p=52017763&postcount=2
2. Restore the LRA_001 nandroid backup that you can find here : http://forum.xda-developers.com/showpost.php?p=58438595&postcount=14
Note : this nandroid is made with CWM and CMW recovery is included in the zip.
3. After restore, boot and check for OTA. You may not have data connection but you should have wifi connection.
4. After the OTA installation, you should get your data connection back.
Good Luck
Click to expand...
Click to collapse
Thanks mate, managed to restore the nandroid, still there are no signals, connected wifi and downloading OTA, phone restarted itself once during the download but resumed again, will update you about it.
Edit:
rebooted 2 more time dont know if it will let the OTA download.
ckpv5 said:
1. Install the 4.4.4 firmware that you can find here : http://forum.xda-developers.com/showpost.php?p=52017763&postcount=2
2. Restore the LRA_001 nandroid backup that you can find here : http://forum.xda-developers.com/showpost.php?p=58438595&postcount=14
Note : this nandroid is made with CWM and CMW recovery is included in the zip.
3. After restore, boot and check for OTA. You may not have data connection but you should have wifi connection.
4. After the OTA installation, you should get your data connection back.
Good Luck
Click to expand...
Click to collapse
Ok so here is the update,
After about a 100 reboots the OTA was successfully downloaded. But it won't let it flash, whenever I tried to flash it just rebooted, since the firmware didn't contain boot and recovery and I was on CWM I thought its recovery issue so flashed stok firmware and boot. It still didn't work, then flashed TWRP and tried to install OTA again, got some fingerprint error, please see the attached image.
When you restored the nandroid, do you restore the stock recovery included in the zip ?
OTA will install on stock recovery not CWM & not TWRP and not even on vzn stock recovery.
Do you still have the OTA.zip in internal storage/download folder ?
Copy that to PC, open it with 7-zip and extract out firmware.zip. Open firmware.zip and extract out the recovery.img
Flash this recovery.img. As your device is S-Off you can manually install OTA with stock recovery installed. Do you know how ? If not sure, ask .. will tell you how-to when I get to my PC. Not easy to write all these on mobile.
Or you can flash this extracted firmware.zip in ruu mode, you'll solve your data connection problem.
Then you can redo OTA installation process.
ckpv5 said:
When you restored the nandroid, do you restore the stock recovery included in the zip ?
OTA will install on stock recovery not CWM & not TWRP and not even on vzn stock recovery.
Do you still have the OTA.zip in internal storage/download folder ?
Copy that to PC, open it with 7-zip and extract out firmware.zip. Open firmware.zip and extract out the recovery.img
Flash this recovery.img. As your device is S-Off you can manually install OTA with stock recovery installed. Do you know how ? If not sure, ask .. will tell you how-to when I get to my PC. Not easy to write all these on mobile.
Or you can flash this extracted firmware.zip in ruu mode, you'll solve your data connection problem.
Then you can redo OTA installation process.
Click to expand...
Click to collapse
when i restored the nandroid it didn't restore the stock recovery, i flashed the stock recovery from the firmware.zip, the OTA is still in download folder, whenever i check for update it finds the existing file verifies it and prompt to install it, i did select to install it, its still just rebooting, after a couple of attempts it once booted into recovery but then without any progress it kept rebooting into recovery, after several reboots it booted again normally.
so now i have the stock recovery installed, should i rename the firmware.zip to 0P6B2000.zip and install it via hboot?
You flashed the stock recovery from which firmware.zip ? The one from VZN won't work. The one from the OTA zip will.
No .. that's wrong to rename firmware.zip to 0P6B2000.zip
Try this first :
firmware.zip is the one from OTA zip, not VZN
Put your device on bootloader/fastboot mode and connect to PC (you should see fastboot usb highlighted in red).
Put the firmware.zip in your fastboot folder. Open a command prompt from that folder.
type below command :
fastboot reboot-bootloader (to make sure you're on fastboot mode)
fastboot oem rebootRUU (to put the device in RUU mode)
fastboot flash zip firmware.zip (flashing the firmware.zip)
You'll see : FAILED (remote: 90 hboot pre-update! please flush image again immediately)
repeat fastboot flash zip firmware.zip (to complete firmware installation)
fastboot reboot-bootloader
Check your bootloader now written OS - 4.21.512.4
Now reboot (your data connection should work now) and redo OTA process
EDIT : can you upload that OTA zip to your GDrive or Dropbox and PM me the link. That will help many people.
ckpv5 said:
You flashed the stock recovery from which firmware.zip ? The one from VZN won't work. The one from the OTA zip will.
No .. that's wrong to rename firmware.zip to 0P6B2000.zip
Try this first :
firmware.zip is the one from OTA zip, not VZN
Put your device on bootloader/fastboot mode and connect to PC (you should see fastboot usb highlighted in red).
Put the firmware.zip in your fastboot folder. Open a command prompt from that folder.
type below command :
fastboot reboot-bootloader (to make sure you're on fastboot mode)
fastboot oem rebootRUU (to put the device in RUU mode)
fastboot flash zip firmware.zip (flashing the firmware.zip)
You'll see : FAILED (remote: 90 hboot pre-update! please flush image again immediately)
repeat fastboot flash zip firmware.zip (to complete firmware installation)
fastboot reboot-bootloader
Check your bootloader now written OS - 4.21.512.4
Now reboot (your data connection should work now) and redo OTA process
EDIT : can you upload that OTA zip to your GDrive or Dropbox and PM me the link. That will help many people.
Click to expand...
Click to collapse
ok i did flash the firmware in RUU mode, i can see the latest version in bootloader mode, then rebooted the phone but now its stuck in bootloop,.
managed to get to bootloader again by holding volum and power button while it was rebooting.
cant get to home screen.
yes i will upload the OTA and share the link.
Install CWM and restore the backup again ..
After you already boot and run setup ... copy the OTA zip to root of your internal storage, not in any folder.
boot to bootloader and install the stock recovery from that LRA firmware.zip
select hboot then recovery .. you'll get black screen or red triangle .. press & hold volume up button and press power once .. this will get you to stock recovery menu
select install from phone storage
select the OTA zip
install
reboot
ckpv5 said:
Install CWM and restore the backup again ..
After you already boot and run setup ... copy the OTA zip to root of your internal storage, not in any folder.
boot to bootloader and install the stock recovery from that LRA firmware.zip
select hboot then recovery .. you'll get black screen or red triangle .. press & hold volume up button and press power once .. this will get you to stock recovery menu
select install from phone storage
select the OTA zip
install
reboot
Click to expand...
Click to collapse
ok installed CWM, restored the nandroid, still rebooting and not signals.
flashed the stock recovery (the one from OTA) tried to install the OTA again, same problem rebooting again n again, managed to get into recovery once, but then stuck in boot loop on recovery, managed to get into bootloader by the volume and power button.
There's nothing much that I can offer to help. Your rebooting problem I believe due to motherboard cannot take the heat. I want to say this earlier but let you try all the possibilities first, you may have damaged motherboard that is why previously you have restarting problem when using your device.
Let your phone to cool down ... then try again. If still the same, need to send it to repair centre.
Hello.
I am currently running ParanoidAndroid 4.6Beta5. Since PA's developement for M8 seems to be dead, I wanted to try CM12.
When I tried to install latest nightly build of CM12 I got a message that my bootloader (3.16) is not supported, and that I need to update it to 3.18 or 3.19.
I googled a bit and found out that in order to update it, I need to restore latest official ROM.
I managed to restore official ROM (3.28.401.6, based on android 4.4.4) but the WiFi wasn't working, so I couldn't do much there. I relocked bootloader and flashed official recovery, and then tried to run RUU.
RUU failed with code [315]. I ran out of ideas and google results to browse.
I unlocked my bootloader again, flashed clockworkmod recovery back, and restored my backup of ParanoidAndroid.
Right now the phone is in the same state as when I was starting.
Here is some basic info about my phone:
Model: HTC ONE M8 16GB Unlocked (purchased on amazon; network free)
CID: HTC_001
Bootloader: Unlocked
Recovery: Clockworkmod Touch v6.0.4.8
S status: S-ON
Click to expand...
Click to collapse
So the basic question is: how to flash CM12 on HTC One M8? I spent so many hours on it without any result, so this thread is my last chance.
Edit: SOLVED!
See http://forum.xda-developers.com/showpost.php?p=58859881&postcount=13 for solution.
ProTofik said:
Hello.
I am currently running ParanoidAndroid 4.6Beta5. Since PA's developement for M8 seems to be dead, I wanted to try CM12.
When I tried to install latest nightly build of CM12 I got a message that my bootloader (3.16) is not supported, and that I need to update it to 3.18 or 3.19.
I googled a bit and found out that in order to update it, I need to restore latest official ROM.
I managed to restore official ROM (3.28.401.6, based on android 4.4.4) but the WiFi wasn't working, so I couldn't do much there. I relocked bootloader and flashed official recovery, and then tried to run RUU.
RUU failed with code [315]. I ran out of ideas and google results to browse.
I unlocked my bootloader again, flashed clockworkmod recovery back, and restored my backup of ParanoidAndroid.
Right now the phone is in the same state as when I was starting.
Here is some basic info about my phone:
So the basic question is: how to flash CM12 on HTC One M8? I spent so many hours on it without any result, so this thread is my last chance.
Click to expand...
Click to collapse
Since you are S-On, you can't just flash the firmware, which is the easiest way. But you can use this method.
I'll give you an RUU to flash. But before you flash it, backup everything that is important to you, because this will wipe your phone.
Download this.
Rename it to 0P6BIMG.zip (that's a zero not the letter)
Put it onto the root of your extSD (By root of I mean just on the card and not a folder)
Boot into bootloader and choose hboot.
Follow the prompts (vol up to flash, power button to reboot when done)
Congratulations! You now have the latest lollipop firmware.
Make sure you delete the renamed zip from your extSD when you are done. If you don't delete it, it will try to update again every time you go back to hboot.
Since you are S-On, you can't just flash the firmware
Click to expand...
Click to collapse
What do you mean by firmware. Bootloader or ROM? I did 'just' flash PA without a problem.
I guess the ROM you liked is the latest official one. By installing it I will get my bootloader updated and then I will be able to flash CM12. Do I get this right? or will I get stuck on stock forever?
Edit: I just tried to flash your image using hboot but it didn't work. Check file attached.
I checked MD5 checksum just to make sure that it did download correctly and it does match with the one on the download page. However, I did notice that when I'm trying to open that zip file on my PC I'm getting an error saying that the archive is corrupted.
ProTofik said:
What do you mean by firmware. Bootloader or ROM? I did 'just' flash PA without a problem.
I guess the ROM you liked is the latest official one. By installing it I will get my bootloader updated and then I will be able to flash CM12. Do I get this right? or will I get stuck on stock forever?
Edit: I just tried to flash your image using hboot but it didn't work. Check file attached.
I checked MD5 checksum just to make sure that it did download correctly and it does match with the one on the download page. However, I did notice that when I'm trying to open that zip file on my PC I'm getting an error saying that the archive is corrupted.
Click to expand...
Click to collapse
It probably didn't work because you are S-On. The method I gave you is generally used by S-Off users to flash firmware, but since it was a signed zip, I thought it might work.
Rename the download I gave you to ROM.zip at put it into your fastboot/platform-tools folder on your PC. Then hook your phone up to your PC and fastbooot.
fastboot devices to make sure your phone and PC are properly connected. (letters and numbers/ser. #)
fastboot oem rebootRUU
fastboot flash zip ROM.zip
EDIT: If you respond here, please use the reply button, I will get a notification that way. I just stumbled back to this thread by chance.
xunholyx said:
It probably didn't work because you are S-On. The method I gave you is generally used by S-Off users to flash firmware, but since it was a signed zip, I thought it might work.
Rename the download I gave you to ROM.zip at put it into your fastboot/platform-tools folder on your PC. Then hook your phone up to your PC and fastbooot.
fastboot devices to make sure your phone and PC are properly connected. (letters and numbers/ser. #)
fastboot oem rebootRUU
fastboot flash zip ROM.zip
EDIT: If you respond here, please use the reply button, I will get a notification that way. I just stumbled back to this thread by chance.
Click to expand...
Click to collapse
Sorry, doesn't work either. I'm getting this error on 3rd command:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip ROM.zip
target reported max download size of 1830711296 bytes
error: cannot load 'ROM.zip'
Click to expand...
Click to collapse
ProTofik said:
Sorry, doesn't work either. I'm getting this error on 3rd command:
Click to expand...
Click to collapse
Okay. There must be something I am not aware of.
In fastboot: fastboot getvar all and post the readout here. But delete the serial number and IMEI for your own safety. Never post those on a public forum.
xunholyx said:
Okay. There must be something I am not aware of.
In fastboot: fastboot getvar all and post the readout here. But delete the serial number and IMEI for your own safety. Never post those on a public forum.
Click to expand...
Click to collapse
There you go:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: TOP SECRET
(bootloader) imei: TOP SECRET
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
Click to expand...
Click to collapse
ProTofik said:
There you go:
Click to expand...
Click to collapse
It should work. Try this download instead. https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view
It's pretty much the same one. Maybe the other one is screwed somehow? Try with this one instead and hopefully you can get updated.
xunholyx said:
It should work. Try this download instead. https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view
It's pretty much the same one. Maybe the other one is screwed somehow? Try with this one instead and hopefully you can get updated.
Click to expand...
Click to collapse
Didn't work but I got a different error this time
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip ROM
.zip
target reported max download size of 1830711296 bytes
sending 'zip' (1536838 KB)...
OKAY [ 43.198s]
writing 'zip'...
(bootloader) zip header checking...
FAILED (remote: 32 header error)
finished. total time: 43.510s
Click to expand...
Click to collapse
Is it not possible to just restore whatever ROM my phone came with and then just do the OTA update?
ProTofik said:
Didn't work but I got a different error this time
Is it not possible to just restore whatever ROM my phone came with and then just do the OTA update?
Click to expand...
Click to collapse
LOL!
Yes. I got caught up in this method. You will also need the stock recovery (more important than the ROM) to use the OTAs. Plus your system partition has to be unmodified. That means no Xposed modules. If you have them, delete them using Xposed framework, then uninstall that as well.
xunholyx said:
LOL!
Yes. I got caught up in this method. You will also need the stock recovery (more important than the ROM) to use the OTAs. Plus your system partition has to be unmodified. That means no Xposed modules. If you have them, delete them using Xposed framework, then uninstall that as well.
Click to expand...
Click to collapse
So if I get this right, I just need to restore my factory ROM and Recovery image, then update it through OTA to lollipop. After that I will be able to flash my custom recovery and ROMs once again, right?
Do you have any links to the ROM and Recovery to my phone?
ProTofik said:
So if I get this right, I just need to restore my factory ROM and Recovery image, then update it through OTA to kitkat. After that I will be able to flash my custom recovery and ROMs once again, right?
Do you have any links to the ROM and Recovery to my phone?
Click to expand...
Click to collapse
Yes. Sorry for the confusion I have caused.
xunholyx said:
LOL!
Yes. I got caught up in this method. You will also need the stock recovery (more important than the ROM) to use the OTAs. Plus your system partition has to be unmodified. That means no Xposed modules. If you have them, delete them using Xposed framework, then uninstall that as well.
Click to expand...
Click to collapse
Success. For future generations, here is what I did:
Using fastboot getvar all command I found out that my phone was still mentally stuck on stock rom 1.54.401.5. Using this info, I downloaded matching nandroid backup of that ROM from here and restored it using my custom recovery.
Then, downloading from the same thread, I flashed back stock recovery image using HTC One 2014 (M8) All-In-One Toolkit V2.0.
I was back on my original ROM with original recovery, so I started doing OTA updates until I got to the official android 5.0.1. These updates updated my bootloader to version 3.19.
Having the bootloader that I needed, I flashed custom recovery and installed CM12 without any problem.
Thanks for help!
Hey, I just found this as I am having the same problem. I am trying to follow your solution, but hit a road block and was wondering if you could help. I ran the command "fastboot getvar all" in fastboot and got output similar to yours. Following your advice I looked at the line (bootloader) version-main: 1.55.605.2 which is different than yours, but okay I just need to find a matching one. But when I go to the link that you had provided I can't find a backup that matches mine (or at least I think I can't). What does it mean for it to match anyway? I'm getting so close! I want cm12!!
I did it over like 6 months ago. I can't remember any more. Sorry.
Anyway, CM12 has way too many problem on HTC ONE M8 to be used as a daily driver. I am using GPE Rom now, which I can recommend.
I just need to find some way to update my bootloader so I can get lollipop up and running. Thanks tho
noo_too_droid said:
Following your advice I looked at the line (bootloader) version-main: 1.55.605.2 which is different than yours, but okay I just need to find a matching one. But when I go to the link that you had provided I can't find a backup that matches mine (or at least I think I can't). What does it mean for it to match anyway?
Click to expand...
Click to collapse
The number needs to match exactly to restore to stock and OTA update the software/firmware (and therefore update hboot).
You can try to post on the following thread, and ask if someone can post the stock nandroid for 1.55.605.2 :http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Otherwise (if you can't get a stock nandroid) you may need to resort to getting s-off in order to update hboot (actually I recommend updating all firmware, not just hboot).
ProTofik said:
Success. For future generations, here is what I did:
Using fastboot getvar all command I found out that my phone was still mentally stuck on stock rom 1.54.401.5.
Click to expand...
Click to collapse
Hi there! I have a problem with my One M8 (S-OFF) - I cant flash any ROM on it. I can restore backups from a CM11 4.4.4 and an ARHD 41.0 but can't upgrade from either. I was looking at your solution and noticed that my ROM number is blank when I run fastboot getvar all. Is this a matter of concern? How can I flash a ROM again?
raghuchary said:
Hi there! I have a problem with my One M8 (S-OFF) - I cant flash any ROM on it. I can restore backups from a CM11 4.4.4 and an ARHD 41.0 but can't upgrade from either. I was looking at your solution and noticed that my ROM number is blank when I run fastboot getvar all. Is this a matter of concern? How can I flash a ROM again?
Click to expand...
Click to collapse
Your version-main is blank because of a bug in some older TWRPs. Update to 2.8.7.0. Flashing the new recovery won't fix version-main being blank until you flash new firmware though.
Also, you probably do have to update your firmware. You say you can't flash any ROMs, but you give no details.
xunholyx said:
Your version-main is blank because of a bug in some older TWRPs. Update to 2.8.7.0. Flashing the new recovery won't fix version-main being blank until you flash new firmware though.
Also, you probably do have to update your firmware. You say you can't flash any ROMs, but you give no details.
Click to expand...
Click to collapse
Apologies, newbie here. I was looking for the correct place to place my request for help, when I found this thread and asked. I will put it up in the Q&A section.
Greetings to all of you
i need little help since i'm a new HTC User
first of all , my phone is :
S-On , Rooted , Unlocked Bootloader , TWRP & finally on stock base 1.40.709.8
CID : HTC_621
MID : 0PJA10000
now i need to update to latest base " 2.10.709.1 "
how to do so step by step ??
EDIT :
i read here on XDA " If your device is S-ON , then you cannot flash an RUU with version less than your phone's current version . The same applies for hboot version "
Amr Nasser said:
Greetings to all of you
i need little help
i'm a new HTC User , I've HTC M9
first of all , my phone is :
S-On , Rooted , Unlocked Bootloader , TWRP & finally on Lee Droid Rom base 1.40.401.8
CID : HTC_621
MID : 0PJA10000
now i need to update to latest 2.10.401.1
how to do so step by step ??
Click to expand...
Click to collapse
Either you S-OFF with sunshine (costs 25 USD) so you can flash the leaked firmware or you wait untill the official OTA gets distributed by HTC. If you choose to do the latter you need to restore your system to stock, unrooted, read-only state by flashing a RUU or restoring a stock backup and reflashing the stock recovery.
Important
Flippy498 said:
Either you S-OFF with sunshine (costs 25 USD) so you can flash the leaked firmware or you wait untill the official OTA gets distributed by HTC. If you choose to do the latter you need to restore your system to stock, unrooted, read-only state by flashing a RUU or restoring a stock backup and reflashing the stock recovery.
Click to expand...
Click to collapse
this posted yesterday :
http://forum.xda-developers.com/showpost.php?p=61995182&postcount=373
i have the same MID & CID
does it mean if i get back to stock 1.40.401.8 , i can use that OTA To get 2.10.401.1 ??
Amr Nasser said:
this posted yesterday :
http://forum.xda-developers.com/showpost.php?p=61995182&postcount=373
i have the same MID & CID
does it mean if i get back to stock 1.40.401.8 , i can use that OTA To get 2.10.401.1 ??
Click to expand...
Click to collapse
The update from the link is for the Asian SKU 709. If you go back to a stock version with the SKU 401 you can only use updates with the same SKU and the update for firmware 2.10.401.1 has not been realesed officially untill now.
Edit: Maybe I understood you wrong. What is your actual firmware version? I mean the one that is stated in the download mode in the line with "OS" at the beginning. That is the firmware you need to look for if you want to get back to stock. The one in settings>about only tells you the base of the rom you are using.
Important
Flippy498 said:
The update from the link is for the Asian SKU 709. If you go back to a stock version with the SKU 401 you can only use updates with the same SKU and the update for firmware 2.10.401.1 has not been realesed officially untill now.
Edit: Maybe I understood you wrong. What is your actual firmware version? I mean the one that is stated in the download mode in the line with "OS" at the beginning. That is the firmware you need to look for if you want to get back to stock. The one in settings>about only tells you the base of the rom you are using.
Click to expand...
Click to collapse
i will go back to stock 1.40.709.8 ?? then update to 2.10.709.1 ?? both are Asian
will this work , i think they are same SKU now ??
Amr Nasser said:
i will go back to stock 1.40.709.8 ?? then update to 2.10.709.1 ?? both are Asian
will this work , i think they are same SKU now ??
Click to expand...
Click to collapse
Your phone is S-ON so you can only go back to the stock firmware that belongs to your phones SKU. You need to look at the "OS" line in download mode if you want to know which SKU versions you can use.
Amr Nasser said:
Greetings to all of you
i need little help
i'm a new HTC User , I've HTC M9
first of all , my phone is :
S-On , Rooted , Unlocked Bootloader , TWRP & finally on Lee Droid Rom base 1.40.401.8
CID : HTC_621
MID : 0PJA10000
now i need to update to latest 2.10.401.1
how to do so step by step ??
Click to expand...
Click to collapse
Since you're s-on, you're already on .709 firmware. There is no way you could be on anything else because it would not flash. Still, you should reboot to download mode and see what it says. If it's 1.32.709 as I expect, proceed.
1. Use Titanium Backup to back up all your user data and apps to your external sdcard; remove it.
2. Relock and run the existing RUU for your phone (this will wipe everything). Link is in this thread; follow instructions in the OP.
3. Wait until the OTA shows up and install.
4. Unlock and reroot, then restore your backed up data and apps.
Important
iElvis said:
Since you're s-on, you're already on .709 firmware. There is no way you could be on anything else because it would not flash. Still, you should reboot to download mode and see what it says. If it's 1.32.709 as I expect, proceed.
1. Use Titanium Backup to back up all your user data and apps to your external sdcard; remove it.
2. Relock and run the existing RUU for your phone (this will wipe everything). Link is in this thread; follow instructions in the OP.
3. Wait until the OTA shows up and install.
4. Unlock and reroot, then restore your backed up data and apps.
Click to expand...
Click to collapse
when i entered download mode , my OS showed me 1.40.709.8
so i assume now ,
relock my bootloader , run RUU 1.32.709 then OTA from my phone till i reach 1.40.709.8 and then i use the OTA in this thread to upgrade to 2.10.709.1 :
http://forum.xda-developers.com/showpost.php?p=61995182&postcount=373
then i can Unlock again and install TWRP and so on ,, am i right ??
Amr Nasser said:
when i entered download mode , my OS showed me 1.40.709.8
so i assume now ,
relock my bootloader , run RUU 1.32.709 then OTA from my phone till i reach 1.40.709.8 and then i use the OTA in this thread to upgrade to 2.10.709.1 :
http://forum.xda-developers.com/showpost.php?p=61995182&postcount=373
then i can Unlock again and install TWRP and so on ,, am i right ??
Click to expand...
Click to collapse
Correct. Although I think there is no need to flash the last OTA manually. You can update via the OTA function until you reach 2.10.709.1 since it's been released officially.
Amr Nasser said:
when i entered download mode , my OS showed me 1.40.709.8
so i assume now ,
relock my bootloader , run RUU 1.32.709 then OTA from my phone till i reach 1.40.709.8 and then i use the OTA in this thread to upgrade to 2.10.709.1 :
http://forum.xda-developers.com/showpost.php?p=61995182&postcount=373
then i can Unlock again and install TWRP and so on ,, am i right ??
Click to expand...
Click to collapse
No. If you're on 1.40, the 1.32 RUU will not flash because you're s-on—you can't downgrade. You need to find the 1.40.709 RUU. Let me look around.
Edit: It doesn't seem to be posted anywhere I can find. You need to get back to stock to flash an OTA. I think your only option unless HTC releases a RUU for 2.10.709 may be to s-off and update manually.
iElvis said:
No. If you're on 1.40, the 1.32 RUU will not flash because you're s-on—you can't downgrade. You need to find the 1.40.709 RUU. Let me look around.
Edit: It doesn't seem to be posted anywhere I can find. You need to get back to stock to flash an OTA. I think your only option unless HTC releases a RUU for 2.10.709 may be to s-off and update manually.
Click to expand...
Click to collapse
Actually downgrading with S-ON is possible as long as the bootloader version doesn't need to be downgraded, too (source). Just checked on my phone that the aboot is even with the 2.7.401.1 firmware still on version 1.0.0.0000. So there should be no problem.
Flippy498 said:
Actually downgrading with S-ON is possible as long as the bootloader version doesn't need to be downgraded, too (source). Just checked on my phone that the aboot is even with the 2.7.401.1 firmware still on version 1.0.0.0000. So there should be no problem.
Click to expand...
Click to collapse
That's interesting, thanks. Didn't use to be that way.
Important
Flippy498 said:
Actually downgrading with S-ON is possible as long as the bootloader version doesn't need to be downgraded, too (source). Just checked on my phone that the aboot is even with the 2.7.401.1 firmware still on version 1.0.0.0000. So there should be no problem.
Click to expand...
Click to collapse
i relocked my bootloader then tried to flash RUU with these orders :
fastboot oem rebootRUU
fastboot flash zip 0PJAIMG.zip
i got this error every time :
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
and i can't flash RUU
any ideas ??
Amr Nasser said:
i relocked my bootloader then tried to flash RUU with these orders :
fastboot oem rebootRUU
fastboot flash zip 0PJAIMG.zip
i got this error every time :
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
and i can't flash RUU
any ideas ??
Click to expand...
Click to collapse
Download and use HTC_fast boot.exe instead of facebook.exe. you can find HTC_fastboot by searching the forum. Just place it on the same folder as your current fastboot.exe file.
Command are the same except instead of typing "fastboot flash..." It's "HTC_fastboot flash..."
Edit: this is because regular fastboot can't handle files over 2GB.
Important
Flippy498 said:
Actually downgrading with S-ON is possible as long as the bootloader version doesn't need to be downgraded, too (source). Just checked on my phone that the aboot is even with the 2.7.401.1 firmware still on version 1.0.0.0000. So there should be no problem.
Click to expand...
Click to collapse
jollywhitefoot said:
Download and use HTC_fast boot.exe instead of facebook.exe. you can find HTC_fastboot by searching the forum. Just place it on the same folder as your current fastboot.exe file.
Command are the same except instead of typing "fastboot flash..." It's "HTC_fastboot flash..."
Edit: this is because regular fastboot can't handle files over 2GB.
Click to expand...
Click to collapse
that's worked , but now i got this error :
C:\Users\Amr\Desktop\Squabbi's Toolkit\adb>htc_fastboot oem rebootRUU
... OKAY
Execution time is 206(ms)
C:\Users\Amr\Desktop\Squabbi's Toolkit\adb>htc_fastboot flash zip 0PJAIMG.zip
< waiting for device >
sending 'zip'... (250395 KB) OKAY
sending time = 10.592 secs
writing 'zip'... (bootloader) HOSD CL#553039
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
FAIL19: fail to flash via downloadzip
FAILED (remote: 19: fail to flash via downloadzip)
Execution time is 19(s)
i've S-On , and my bootloader is " RELOCKED " >> if this can help
Edit :
i've " Relocked " My bootloader through
reboot bootloader
then download mode
fastboot oem lock
any ideas ??
Amr Nasser said:
that's worked , but now i got this error :
C:\Users\Amr\Desktop\Squabbi's Toolkit\adb>htc_fastboot oem rebootRUU
... OKAY
Execution time is 206(ms)
C:\Users\Amr\Desktop\Squabbi's Toolkit\adb>htc_fastboot flash zip 0PJAIMG.zip
< waiting for device >
sending 'zip'... (250395 KB) OKAY
sending time = 10.592 secs
writing 'zip'... (bootloader) HOSD CL#553039
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
FAIL19: fail to flash via downloadzip
FAILED (remote: 19: fail to flash via downloadzip)
Execution time is 19(s)
i've S-On , and my bootloader is " RELOCKED " >> if this can help
Edit :
i've " Relocked " My bootloader through
reboot bootloader
then download mode
fastboot oem lock
any ideas ??
Click to expand...
Click to collapse
Main version not allowed looks like its saying you can't downgrade. Maybe the bootloader version changed.
Amr Nasser said:
that's worked , but now i got this error :
C:\Users\Amr\Desktop\Squabbi's Toolkit\adb>htc_fastboot oem rebootRUU
... OKAY
Execution time is 206(ms)
C:\Users\Amr\Desktop\Squabbi's Toolkit\adb>htc_fastboot flash zip 0PJAIMG.zip
< waiting for device >
sending 'zip'... (250395 KB) OKAY
sending time = 10.592 secs
writing 'zip'... (bootloader) HOSD CL#553039
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
FAIL19: fail to flash via downloadzip
FAILED (remote: 19: fail to flash via downloadzip)
Execution time is 19(s)
i've S-On , and my bootloader is " RELOCKED " >> if this can help
Edit :
i've " Relocked " My bootloader through
reboot bootloader
then download mode
fastboot oem lock
any ideas ??
Click to expand...
Click to collapse
Which RUU did you try to flash? As far as I know there is one for 1.32.709.6 and one for 1.36.709.3. Best case scenario would be you downloaded a wrong RUU. Worst case scenario would be that downgrading is (in contrast to the post I linked earlier) not aboot dependent and not possible if the software numbers (in your case the 40 you want to downgrade to 32 or 36) differ.
iElvis said:
No. If you're on 1.40, the 1.32 RUU will not flash because you're s-on—you can't downgrade. You need to find the 1.40.709 RUU. Let me look around.
Edit: It doesn't seem to be posted anywhere I can find. You need to get back to stock to flash an OTA. I think your only option unless HTC releases a RUU for 2.10.709 may be to s-off and update manually.
Click to expand...
Click to collapse
mY RECOMMENDATION IS TO WAIT UNTIL DE 2.10 RUU ZIP AND DO THE SCARD METHOD, IS SAFE FAST AND THEN YOU GOT A FULL STOCK CLEAN OF BLOATWARE, ALSO IYOU WILL BECOME OFFICIAL STOCK, YOU WOULD HAVE TO ROOT AGAIN AND FLASH TWRP. NO S-OFF REQUIERED.
Important
jollywhitefoot said:
Main version not allowed looks like its saying you can't downgrade. Maybe the bootloader version changed.
Click to expand...
Click to collapse
i searched the internet and found a nandroid backup which was the same stock rom my device was running
now i restored it via TWRP , everything is perfect now
so now , i've stock 1.40.709.8 base
Unlocked , TWRP Recovery , Rooted , S-On
And i got OTA Notification to update to 2.10.709.1 >> downloaded it >> but it doesn't install >> i know that i must flash stock recovery and " RELOCK " bootloader
can anyone provide me stock recovery for 1.40.709.8 ??
what is the next steps i have to do , because when i " RELOCK " my bootloader >> device start in bootloader mode and don't boot and i have to unlock it again so it can boot , what causes this ??
EDIT :
can i just flash OTA zip file via TWRP or i can't ??
Amr Nasser said:
i searched the internet and found a nandroid backup which was the same stock rom my device was running
now i restored it via TWRP , everything is perfect now
so now , i've stock 1.40.709.8 base
Unlocked , TWRP Recovery , Rooted , S-On
And i got OTA Notification to update to 2.10.709.1 >> downloaded it >> but it doesn't install >> i know that i must flash stock recovery and " RELOCK " bootloader
can anyone provide me stock recovery for 1.40.709.8 ??
what is the next steps i have to do , because when i " RELOCK " my bootloader >> device start in bootloader mode and don't boot and i have to unlock it again so it can boot , what causes this ??
EDIT :
can i just flash OTA zip file via TWRP or i can't ??
Click to expand...
Click to collapse
Flashing OTAs with TWRP isn't possible but you can use the recovery that is placed in the OTA. The OTA can be found in
Code:
/data/data/com.htc.updater/files/
Just copy it to your pc and open the zip file. The recovery can be found in one of the subfolders. Next step would be making a TWRP backup with only recovery checked. After the backup has finished you need to copy it to your pc, too. Now you need to rename the stock recovery you grabbed from the OTA to
Code:
recovery.emmc.win
and replace the recovery in the backup with the renamed file. Next you need to copy the backup back to your phone and restore it with TWRP. When you reboot now TWRP will be replaced by the stock recovery and you should be able to install the OTA. I'm not sure whether it is necessary to relock for the update with S-ON. With S-OFF it is actually not needed.
Edit: I missed the part where you stated that you're still rooted and assumed that you restored a "read-only backup". My instructions won't work until you restored a stock, unrooted and read-only system beforehand.
Hello , please help , I unlock bootloader flash TWRP 2.7.0.2 , root , after update to TWRP 3.0.0.2 , and go to recovery stays on the screen , some solution
You can't use TWRP 3.x.x.x when your hboot is lower than 3.19.0000
or lower than lollipop firmware
Install TWRP 2.8.x.x
ckpv5 said:
You can't use TWRP 3.x.x.x when your hboot is lower than 3.19.0000
or lower than lollipop firmware
Install TWRP 2.8.x.x
Click to expand...
Click to collapse
The same happens when I install 2.8.4.0 , and when I install any rom does not give me the animation start , nothing but the same screen until it comes to system
TWRP 2.8.4.0 & above is meant for firmware 4.x
If your firmware is 1.x & 2.x, use 2.8.1.0
If your firmware is 3.x, use 2.8.3.0
See simple guide here : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Can you post fastboot getvar all result (without serial & imei no.) then we'll see what is best for you.
ckpv5 said:
TWRP 2.8.4.0 & above is meant for firmware 4.x
If your firmware is 1.x & 2.x, use 2.8.1.0
If your firmware is 3.x, use 2.8.3.0
See simple guide here : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Can you post fastboot getvar all result (without serial & imei no.) then we'll see what is best for you.
Click to expand...
Click to collapse
You can restore a backup TWRP lollipop with this firmware kitkat ?Cid HTC _332 for example el 4.32.600.2,thanks
No.. you need to restore 1.12.600.20 backup and update to 4.32.600.2 then later update to Marshmallow 6.17.600.3
Install TWRP 2.8.1.0
Restore 1.12.600.20 backup
Install stock recovery 4.32.600.2
Do OTA
Everything that you need are in my backup thread that I linked above
ckpv5 said:
No.. you need to restore 1.12.600.20 backup and update to 4.32.600.2 then later update to Marshmallow 6.17.600.3
Install TWRP 2.8.1.0
Restore 1.12.600.20 backup
Install stock recovery 4.32.600.2
Do OTA
Everything that you need are in my backup thread that I linked above
Click to expand...
Click to collapse
but I 'm s -on and here in Mexico no update to MM via Ota
vences31 said:
but I 'm s -on and here in Mexico no update to MM via Ota
Click to expand...
Click to collapse
Backup and recovery flash stock you suggested , to download the update via OTA lollipop and restarts to install and stays on the white screen with HTC logo , do I have root not know if this is the error ?
Make sure you don't accept root when asked by TWRP.
After OTA is downloaded, let the system install it, no manual install. The first boot will take time.
ckpv5 said:
Make sure you don't accept root when asked by TWRP.
After OTA is downloaded, let the system install it, no manual install. The first boot will take time.
Click to expand...
Click to collapse
but the image of the phone does not appear installing the update
After you restore 1.12.600.20 backup & install 4.32.600.2 stock recovery, the phone booted fine ?
When doing restore, you wipe all cache, dalvik-cache, data & system ? And you restore all boot, data & system ?
Let's say it booted fine, then you check OTA, download & let system install, then it should boot to recovery ... but instead of going to recovery, it get stuck on white screen.. is this what happening ?
Press both power + volume up buttons to reboot the device and try redo the process.
ckpv5 said:
After you restore 1.12.600.20 backup & install 4.32.600.2 stock recovery, the phone booted fine ?
When doing restore, you wipe all cache, dalvik-cache, data & system ? And you restore all boot, data & system ?
Let's say it booted fine, then you check OTA, download & let system install, then it should boot to recovery ... but instead of going to recovery, it get stuck on white screen.. is this what happening ?
Click to expand...
Click to collapse
Yes...try again
If this is not successful .. I'll write another method later tonight.
I have to go now ... will be around after 12 hours
ckpv5 said:
If this is not successful .. I'll write another method later tonight.
I have to go now ... will be around after 12 hours
Click to expand...
Click to collapse
and because if I install a custom rom 6.0.1 does not give me the boot animation and wifi when entering the system is switched off screen,thanks for your time
vences31 said:
and because if I install a custom rom 6.0.1 does not give me the boot animation and wifi when entering the system is switched off screen,thanks for your time
Click to expand...
Click to collapse
That's because your current firmware is too low to handle a 6.0.x custom ROM
I really don't get it why you can't update. Had the same experience before with someone else but the problem was down to not following the guide accordingly.
http://forum.xda-developers.com/showpost.php?p=64730207&postcount=683
You said before, if you install TWRP 2.8.4.0, you can boot to recovery ? If yes, I'll give you another way as your intention is to install custom ROM
ckpv5 said:
That's because your current firmware is too low to handle a 6.0.x custom ROM
I really don't get it why you can't update. Had the same experience before with someone else but the problem was down to not following the guide accordingly.
http://forum.xda-developers.com/showpost.php?p=64730207&postcount=683
You said before, if you install TWRP 2.8.4.0, you can boot to recovery ? If yes, I'll give you another way as your intention is to install custom ROM
Click to expand...
Click to collapse
I want to have Android 6.0 functional either official or custom ROM , or at least spend KitKat , if there are other ways please shares , Eh understood many things thanks to you and now I understand , with other devices I've had it was easier but this has been difficult
You're on KiKat now.. I'm preparing files for you to manually update to lollipop.
Once done, I want you to try to update to Marshmallow. If no success, I'll tell how to manually update to Marshmallow after you tried system update.
This will involve relocking bootloader assuming your device is S-On (you don't give fastboot getvar all result that I asked before)
1. Install TWRP 2.8.4.0 (as you said this is the highest TWRP version that you can install and can boot to it)
2. Download the 4.32.600.2 backup and restore - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
(just follow the steps as in the guide 1-10 only, skip the rest)
3. Download fw_4.32.600.2.zip - https://sourceforge.net/projects/htconem8/files/fw_4.32.600.2.zip/download
4. Install the firmware
1. If the bootloader is UNLOCKED (for S-On device only), relock it with commands:
fastboot oem lock
fastboot reboot-bootloader
If the bootloader is LOCKED or RELOCKED, skip the above.
2. Put the device in bootloader/fastboot mode and connect to PC, run these commands
fastboot oem rebootRUU
fastboot flash zip fw_4.32.600.2.zip
you'll see ERROR/FAILED, repeat
fastboot flash zip fw_4.32.600.2.zip
fastboot reboot-bootloader
You should see the OS written 4.32.600.2 (in green color) on the bootloader.
Now reboot the device .. once the setup completed, check OTA. You should have 6.17.600.3 OTA, download and let system install.
Once the OTA installation is completed and phone rebooted to OS ... you now have a Marshmallow updated firmware & ROM.
You can unlock bootloader again with unlock_code.bin that you received from HTC or apply a new one.
Once unlocked, install TWRP 3.0.2-0, you can install any custom ROM that you like
ckpv5 said:
You're on KiKat now.. I'm preparing files for you to manually update to lollipop.
Once done, I want you to try to update to Marshmallow. If no success, I'll tell how to manually update to Marshmallow after you tried system update.
This will involve relocking bootloader assuming your device is S-On (you don't give fastboot getvar all result that I asked before)
1. Install TWRP 2.8.4.0 (as you said this is the highest TWRP version that you can install and can boot to it)
2. Download the 4.32.600.2 backup and restore - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
(just follow the steps as in the guide 1-10 only, skip the rest)
3. Download fw_4.32.600.2.zip - https://sourceforge.net/projects/htconem8/files/fw_4.32.600.2.zip/download
4. Install the firmware
1. If the bootloader is UNLOCKED (for S-On device only), relock it with commands:
fastboot oem lock
fastboot reboot-bootloader
If the bootloader is LOCKED or RELOCKED, skip the above.
2. Put the device in bootloader/fastboot mode and connect to PC, run these commands
fastboot oem rebootRUU
fastboot flash zip fw_4.32.600.2.zip
you'll see ERROR/FAILED, repeat
fastboot flash zip fw_4.32.600.2.zip
fastboot reboot-bootloader
You should see the OS written 4.32.600.2 (in green color) on the bootloader.
Now reboot the device .. once the setup completed, check OTA. You should have 6.17.600.3 OTA, download and let system install.
Once the OTA installation is completed and phone rebooted to OS ... you now have a Marshmallow updated firmware & ROM.
You can unlock bootloader again with unlock_code.bin that you received from HTC or apply a new one.
Once unlocked, install TWRP 3.0.2-0, you can install any custom ROM that you like
Click to expand...
Click to collapse
I have to let you start 4.32.xxx After restoring the device. ? , He asked that the hboot 3.16.xxx I have is only for the version of KitKat?*
Don't start after restore 4.32.600.2, only boot to bootloader to install 4.32.600.2 firmware. This will get you to hboot 3.18.0000
Only after you installed firmware then only you can restart.
If this also you cannot follow the guide, I don't know how else to help you.
My first guide should be the easiest way but you keep saying it didn't boot. I believe because the guide was not followed accordingly.
@joikep - are you still around ? If yes, maybe you can help as it seems we have language barrier here.
ckpv5 said:
Don't start after restore 4.32.600.2, only boot to bootloader to install 4.32.600.2 firmware. This will get you to hboot 3.18.0000
Only after you installed firmware then only you can restart.
If this also you cannot follow the guide, I don't know how else to help you.
My first guide should be the easiest way but you keep saying it didn't boot. I believe because the guide was not followed accordingly.
@joikep - are you still around ? If yes, maybe you can help as it seems we have language barrier here.
Click to expand...
Click to collapse
if properly flash the firmware? , or failed normal? I appear in red letters 4.32.600.2 in bootloader , but start system , signal device is connected , but disconnects wifi and on every moment
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.376s
C:\Users\mauricio\Downloads\One_M8_All-In-One_Kit_v\Data>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.031s]
finished. total time: 0.128s
C:\Users\mauricio\Downloads\One_M8_All-In-One_Kit_v\Data>fastboot flash fw_4.32.
600.2.zip
unknown partition 'fw_4.32.600.2.zip'
error: cannot determine image filename for 'fw_4.32.600.2.zip'
C:\Users\mauricio\Downloads\One_M8_All-In-One_Kit_v\Data>fastboot flash zip fw_4
.32.600.2.zip
target reported max download size of 1830711296 bytes
sending 'zip' (52971 KB)...
OKAY [ 2.455s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 8.354s
C:\Users\mauricio\Downloads\One_M8_All-In-One_Kit_v\Data>fastboot reboot-bootloa
der
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.109