Hie everyone i am new here and i have an htc one m8 which is bootloader locked , s on and i dont have root access nor custom recovery installed .
All other tutorials i found here are more so related to those htc m8 devices with either bootloader unlocked or custom recovery installed and since the device is stuck on decrypt storage page i cant install an RUU firmware exe i downloaded and also i cant install a custom firmware too .
i found a tutorial on how to unlock bootloader and did got my token id from fastboot since it is the only thing working so far and am stuck with the stock recovery so i cannot get into adb mode.
when flashing the unlock code bin file in fastboot it says successfully and the warning page also appears which prompts me to choose to unlock bootloader or not . and after selecting unlock bootloader the device restarts into recovery mode i which i thought i have to factory reset for the bootloader process to be complete but still after factory reset the device boots straight to the decrypt storage page and when i reboot again into fastboot mode the bootloader is still locked like nothing happened . tried all methods to unlock bootloader and not factory reset in hope of getting better results but still its the same problem . so if there is another solution that might help me to unlock my bootloader or flash custom recovery or force it to install my RUU exe firmware without debugging i would greatly appreciate it
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Sxxxxxxxxxx
(bootloader) imei: 35xxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__016
(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: f063fb42
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
thats from getvar
and i also downloaded this firmware i dont know if it is the correct one for my device since its showing region as south africa (Region : VODA-Africa-South)
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
any help related to my problem is greatly appreciated
Just follow this ,Might help
The correct RUU for your device
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
Just follow this ,Might help
The correct RUU for your device
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
ok let me try it and update you with the results
hie when i type fastboot oem rebootRUU it reboots and boots into the system where it shows decrypt storage again . installed htc sync and uninstalled it leaving the drivers installed i dont know what is happening now , what should it display when it is in RUU MODE?
cliffordmoyo said:
hie when i type fastboot oem rebootRUU it reboots and boots into the system where it shows decrypt storage again . installed htc sync and uninstalled it leaving the drivers installed i dont know what is happening now , what should it display when it is in RUU MODE?
Click to expand...
Click to collapse
i dont know how i did it but for a moment is showed me the allow usb debug screen and i could see the device on adb devices command prompt screen then i tried to install the RUU.exe firmware but it failed and rebooted now its no longer detected on adb :crying:
cliffordmoyo said:
i dont know how i did it but for a moment is showed me the allow usb debug screen and i could see the device on adb devices command prompt screen then i tried to install the RUU.exe firmware but it failed and rebooted now its no longer detected on adb :crying:
Click to expand...
Click to collapse
The RUU.exe from your first post?
That will not work for you. That RUU is for AT&T devices. The only way you would be able to flash that would be if you were S-Off and changed you CID to 11111111 (or AT&T's CID)
Take the RUU.zip (6.12.401.4 ~ the 401 being the important part, that is the identifier for your model) and rename the .zip to 0P6BIMG.zip (that's a zero, not the letter). The best way to do rename would be to place it onto your extSD so you can see the .zip extension (it is sometimes hidden on your PC) and use a file explorer so you don't accidentally rename it to 0P6BIMG.zip.zip
Boot to bootloader after this is renamed and on extSD (formatted to FAT32), and you should be prompted to flash it by pressing vol up. When the flash is finished, you'll be prompted to press power to reboot, and you are done.
Hope this helps
xunholyx said:
The RUU.exe from your first post?
That will not work for you. That RUU is for AT&T devices. The only way you would be able to flash that would be if you were S-Off and changed you CID to 11111111 (or AT&T's CID)
Take the RUU.zip (6.12.401.4 ~ the 401 being the important part, that is the identifier for your model) and rename the .zip to 0P6BIMG.zip (that's a zero, not the letter). The best way to do rename would be to place it onto your extSD so you can see the .zip extension (it is sometimes hidden on your PC) and use a file explorer so you don't accidentally rename it to 0P6BIMG.zip.zip
Boot to bootloader after this is renamed and on extSD (formatted to FAT32), and you should be prompted to flash it by pressing vol up. When the flash is finished, you'll be prompted to press power to reboot, and you are done.
Hope this helps
Click to expand...
Click to collapse
thank you for the reply . so i did download this firmware with the 6 .12.401.4 in its original name hope it is the correct one please confirm
(0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip)
and using extsd card is the best way to flash my device than using fastboot command prompt with RUU zip file stil in pc ? hope i am getting the steps right
cliffordmoyo said:
thank you for the reply . so i did download this firmware with the 6 .12.401.4 in its original name hope it is the correct one please confirm
(0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip)
and using extsd card is the best way to flash my device than using fastboot command prompt with RUU zip file stil in pc ? hope i am getting the steps right
Click to expand...
Click to collapse
Yeah, you can also flash it in fastboot from PC. You'll probably get an "Error 90". That's the hboot pre-update and nothing to worry about. When you get it don't disconnect, just enter the flash command (fastboot flash zip "name of firmware".zip) a second time to reflash it.
xunholyx said:
Yeah, you can also flash it in fastboot from PC. You'll probably get an "Error 90". That's the hboot pre-update and nothing to worry about. When you get it don't disconnect, just enter the flash command (fastboot flash zip "name of firmware".zip) a second time to reflash it.
Click to expand...
Click to collapse
sadly i guess i have got a bigger problem than i thought , so i tried with pc using these commands fastboot oem rebootRUU and the devices reboots straight into normal mode , and i did also the extsd tutorial you gave me and the device checks the file and prompts me if i want to continue bt after pressing the vol up button the device reboots again straight into normal mode where i am having the decrypt storage issue .if only i had that usb debugging screen prompt again i guess i would have had better odds since before it failed it actually went into RUU flash mode showing only the htc logo with black background
thank you for the quick response by the way
cliffordmoyo said:
sadly i guess i have got a bigger problem than i thought , so i tried with pc using these commands fastboot oem rebootRUU and the devices reboots straight into normal mode , and i did also the extsd tutorial you gave me and the device checks the file and prompts me if i want to continue bt after pressing the vol up button the device reboots again straight into normal mode where i am having the decrypt storage issue .if only i had that usb debugging screen prompt again i guess i would have had better odds since before it failed it actually went into RUU flash mode showing only the htc logo with black background
thank you for the quick response by the way
Click to expand...
Click to collapse
You can turn on usb debugging in settings > developer options, but it shouldn't be needed for fastboot commands.
Try flashing this firmware.zip first, then run the RUU.zip again.
xunholyx said:
You can turn on usb debugging in settings > developer options, but it shouldn't be needed for fastboot commands.
Try flashing this firmware.zip first, then run the RUU.zip again.
Click to expand...
Click to collapse
tried that last firmware zip but just want to confirm if i did the correct procedure ......
i downloaded this file you linked me : M8_6.12.401.4_WWE_TWRP2870.zip renamed it to 0P6BIMG.zip , copied it to my sdcard and and rebooted into bootloader . i could see the checking progress bar but then it just doesnt give me the prompt screen for vol up to continue or vol down to cancel , its just saying press power to reboot.
then tried fastboot oem rebootRUU but the fone is just stubborn and reboots into normal mode again not in RUU mode so i cant flash the zip firmware with fastboot . Another thing i noticed is when i finish unlocking bootloader and gets the success message with continue to unlock bootloader screen and then phone reboots into recovery (stock recovery) there is a chain of errors like "cannot mount data , cannot mount emmc" too but when i repeat the bootloader unlock process again this time with an sdcard in device i get "no cw files in sdcard" message when it reboots into recovery but still the bootloader wont be unlocked despite of repeating the process several times. the phone is still brand new never opened and i think this is somehow software related for i was beginning to think that its hardware issue but an app cause this "device decrypt storage" after the phone rebooted
Any idea where i can get htc mtp device drivers as i have reinstalled my operating system and installed htc syn too but those are the only ones failling to install now am on 32bit windows os , the ones i have downloaded are not installing maybe if those install i might recieve an "allow usb debugging " screen as i did earlier on before the screen didnt want to show up again
do you have any idea what might cause device to reboot into os/normal mode when executing the fastboot reboot-bootloader same as fastboot oem rebootRUU the device quickly reboots and enter into normal mode and does not hold those command . also if have downloaded almost 17 unlockcode.bin files from htc dev i kept on requesting after the bootloader wont get unlocked , it shows unlockcode flashed successfully in command prompt but when device reboots the bootloader is still locked . i still love my htc m8 but it seems i am the only one in this enter forum who has this problem since other are successfully getting their devices fixed :crying::crying:
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 ?
My HTC one M8 system UI keeps crashing every time i boot up the phone
How i got to this position
For some reason i was not able to download anything to the phone (yes, there was space available), so i decided to factory reset the phone. unfortunately that was no help. From there i decided to use twrp recovery to wipe everything, Me being a smart guy wiped everything, including the system ( and no i did not make a back up anything ). After got a hold of a mirco sd card and flashed a version of a htc one system file i found at http://forum.xda-developers.com/showthread.php?t=2694994 . I got the phone to boot up ( not booting up from before without a system), but the system UI keeps crashing every time i boot up the phone. Found a thread in xda with the same problem, http://forum.xda-developers.com/showthread.php?t=2694994, and the solution is to get a hold of the stock recovery (not sure if it will work for me). Finally i jump over to an other thead, http://forum.xda-developers.com/showthread.php?t=2701376, saying i need to find out my cidnum. I used fast boot to get it and my version of cidnum is BS_US001 which i could not find on the list.
Long story short
Couldnt download on my phone
wiped my system by mistake (no backs)
flash android revolution hd version of kitkat
system ui keeps crashing
think stock recovery will fix it
getting a random cidnum is BS_US001 and am not sure which stock recovery to flash
Please help !!!!
thank you
Post your fastboot getvar all minus serial no. & imei no.
This will help to find the right ROM for you
ckpv5 said:
Post your fastboot getvar all minus serial no. & imei no.
This will help to find the right ROM for you
Click to expand...
Click to collapse
Please see below.
I found that there is a nandroid back up, on the below thread but how can i flash it. cannot really do anything to the phone.
looking to go stock, if possible
http://forum.xda-developers.com/showthread.php?t=2701376
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.24.21331147A1.09G
version-cpld: None
version-microp: None
version-main: 4.16.1540.8
version-misc: PVT SHIP S-ON
imei2: Not Support
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: BS_US001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 3aa067db
hbootpreupdate: 11
gencheckpt: 0
Just run RUU to have everything back to stock.
Download RUU : http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
1. put your device in bootloader/fastboot mode and connect to PC
2. relock bootloader - command fastboot oem lock
2. Right click the RUU exe that you downloaded, select "run as administrator" .. wait for it to run, later there is a dialog box, accept, next, next, update, blablabla until it finish and your device rebooted... done.
Note : this will wipe everything on your internal storage. Make a backup of important files before you proceed
ckpv5 said:
Just run RUU to have everything back to stock.
Download RUU : http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
1. put your device in bootloader/fastboot mode and connect to PC
2. relock bootloader - command fastboot oem lock
2. Right click the RUU exe that you downloaded, select "run as administrator" .. wait for it to run, later there is a dialog box, accept, next, next, update, blablabla until it finish and your device rebooted... done.
Note : this will wipe everything on your internal storage. Make a backup of important files before you proceed
Click to expand...
Click to collapse
I will give this a try in the morning
I will let you know how it goes, thanks for the help
ckpv5 said:
Just run RUU to have everything back to stock.
Download RUU : http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
1. put your device in bootloader/fastboot mode and connect to PC
2. relock bootloader - command fastboot oem lock
2. Right click the RUU exe that you downloaded, select "run as administrator" .. wait for it to run, later there is a dialog box, accept, next, next, update, blablabla until it finish and your device rebooted... done.
Note : this will wipe everything on your internal storage. Make a backup of important files before you proceed
Click to expand...
Click to collapse
I tried running the program twice, but it failed both times.
it couldnt update the system after erasing eveyrthing.
What error ?
If RUU is not an option for you
you also can fastboot flash the RUU in zip format.
Download the RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.16.1540.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_411207_signed_2-decrypted.zip from here : https://www.androidfilehost.com/?fid=95897840722644595
Rename it to RUU.zip
Download the htc_fastboot.exe here : http://forum.xda-developers.com/showthread.php?t=2735235
Put device in bootloader mode, then run command:
fastboot oem rebootRUU
htc_fastboot flash zip RUU.zip[/COLOR]
ckpv5 said:
What error ?
If RUU is not an option for you
you also can fastboot flash the RUU in zip format.
Download the RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.16.1540.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_411207_signed_2-decrypted.zip from here : https://www.androidfilehost.com/?fid=95897840722644595
Rename it to RUU.zip
Download the htc_fastboot.exe here : http://forum.xda-developers.com/showthread.php?t=2735235
Put device in bootloader mode, then run command:
fastboot oem rebootRUU
htc_fastboot flash zip RUU.zip[/COLOR]
Click to expand...
Click to collapse
"what error?" ------ not sure to be honest, it just failed while it was trying to write the system.
Tried your new suggestion and got this error
sending 'zip'... (1494067 KB) OKAY
sending time = 42.386 secs
writing 'zip'... (bootloader) zip header checking...
(bootloader) zip info parsing...
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 42(s)
Self-admitted newb here. Been reading up on FAQs and instructions on how to Root my new device and am eager to learn more to eventually fully optimize. I was able to unlock, but when attempting to flash TWRP recovery, it'll just hang forever with this message:
"sending 'recovery' (11976 KB)...".
I confirmed checksums of files downloaded, USB Debugging is flagged, Fastboot is deselected, updated the HTC drivers on my PC, and my S/N is acknowledged with the 'fastboot devices' command. I even did a Factory Reset from bootload screen, as this is a new device with no data on it yet.
Any helpful suggestions on determining next steps would be greatly appreciated!
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA12.5mv
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.109
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
You need 2.7 series..
flyera343 said:
You need 2.7 series..
Click to expand...
Click to collapse
Agreed, and I was mistakenly attempting to flash twrp-2.8.6.1-m8.img initially . I'm sorry I failed to mention that in the original post and yes, I also did erase cache several times. Re-attempting to flash twrp-2.7.0.1-m8.img is when the 'sending recovery' hang issue comes up.
bump
pill_popper said:
(bootloader) version-main: 1.54.401.109
(bootloader) modelid: 0P6B12000
(bootloader) security: off
Click to expand...
Click to collapse
You have a very old software version. Since your device is S-Off, I suggest :
1. change the MID 0P6B12000 to 0P6B10000
Follow this thread : http://forum.xda-developers.com/showthread.php?t=2708581
2. run 4.16.401.10 RUU.exe - https://docs.google.com/file/d/0B17smFr95pleeTQ5U1NzNkZzM0U/edit?pli=1
RUU will flash your entire phone back to stock including recovery
(as your device is S-Off, no need to lock/relock bootloader)
3. Now you can install the latest TWRP recovery and do whatever you want to do
Thank you for your kind words. I appreciate it. Will follow up on the points covered in your post and report back.
Ahh.. you need a rooted ROM to do that change of MID.
Without a custom recovery installed, you may not have a rooted ROM.
Reading back your problem ... the error is stuck at sending recovery, not enter recovery. This is possible if you don't have a proper fastboot/adb files.
Try this : http://forum.xda-developers.com/showthread.php?t=2317790
then try to install TWRP recovery again
ckpv5 said:
Ahh.. you need a rooted ROM to do that change of MID.
Without a custom recovery installed, you may not have a rooted ROM.
Reading back your problem ... the error is stuck at sending recovery, not enter recovery.
Click to expand...
Click to collapse
Correct, sorry if I wasn't being clear about that. I've Unlocked, but not yet rooted hence, the attempt to send TWRP. I haven't yet taken next steps though.
ckpv5 said:
This is possible if you don't have a proper fastboot/adb files.
Try this : http://forum.xda-developers.com/showthread.php?t=2317790
then try to install TWRP recovery again
Click to expand...
Click to collapse
More reading! :cyclops:
**Updated**
So I've tried using Minimal ADB tool as well. Now instead of hanging, I'm eliciting errors.
target reported max download size of 1830711296 bytes
sending 'recovery' (11976 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.023s
I'm running as Administrator in Windows 7, I can hear the PC recognize the phone when I plug it in the USB and I've also confirmed multiple times the 'fastboot devices' command recognizes my phone.
If this might be a USB related issue, how would I go about investigating in that direction? Not sure what is preventing me from simply flashing a TWRP recovery. Any thoughts on this are welcome, thank you.
*bumpity bump*
So I can see 'FASTBOOT USB' in bootloader mode, and the fastboot devices command returns my S/N, but still the adb devices command just returns the message 'list of devices' and nothing else. Attempting to flash TWRP recovery still fails. I've uninstalled all HTC stuff and manually updated the driver to 'MTP USB Device' via Device Manager per redpoint73's advice. Before I give up on this PC, are there any additional steps I can take? Any guidance from you guys would be appreciated, thanks!
First, you don't run adb command when on fastboot mode, only fastboot command will work.
Is the USB 3.0 on PC ? You need USB 2.0
Is your device properly working ?
I like to suggest to flash Dev Edition firmware to your device or simply run the Dev Edition RUU to bring the hboot/software version to the latest version before you try TWRP again.
You have MID/CID that match/fit a Dev Edition device except the software version no.
ckpv5 said:
First, you don't run adb command when on fastboot mode, only fastboot command will work.
Is the USB 3.0 on PC ? You need USB 2.0
Is your device properly working ?
I like to suggest to flash Dev Edition firmware to your device or simply run the Dev Edition RUU to bring the hboot/software version to the latest version before you try TWRP again.
You have MID/CID that match/fit a Dev Edition device except the software version no.
Click to expand...
Click to collapse
I guess what most on here would consider to be trivial are to me revelations. Thank you for your response and now I see my device S/N is recognized after running the adb devices command when the phone is running in 'normal' mode! Yes, it is properly working but sadly, all four USB ports on the PC are USB 3.0 I'll read up on your suggestions and reply with questions at that point before taking action. Again with the reading! :cyclops: My concerns here are if stock recovery would continue to work if I go down either of those paths and how the phone is supposed to respond if it's not responding when attempting to flash TWRP. Thanks again for your inputs, I appreciate it!
First .. you need to know your reason to install a TWRP. If you plan to install a custom ROM, it won't properly work because you have a very low version hboot as most custom ROMs require a hboot 3.19.0000
then .. there are other ways to achieve this (all because you have a S-Off device)
1. You can install TWRP using the external_sd (microSD) method but you can only use a lower version TWRP 2.7.x.x or better 2.8.1.0 (because you failed in fastboot method)
2. As I said earlier - install the latest firmware.zip but using the external_sd method too ... but your device may get stuck because your ROM is too low
3. The safest/fastest is install RUU but again you need a USB 2.0 (I'm not sure whether you can install RUU zip using the external_sd method).
4. Back to no. 2 - you can install the firmware.zip using the external_sd method (need to do it twice) then install TWRP again the external_sd method then you need to install a ROM or restore a backup meant for the newer hboot 3.19
ckpv5 said:
First .. you need to know your reason to install a TWRP. If you plan to install a custom ROM, it won't properly work because you have a very low version hboot as most custom ROMs require a hboot 3.19.0000
then .. there are other ways to achieve this (all because you have a S-Off device)
1. You can install TWRP using the external_sd (microSD) method but you can only use a lower version TWRP 2.7.x.x or better 2.8.1.0 (because you failed in fastboot method)
2. As I said earlier - install the latest firmware.zip but using the external_sd method too ... but your device may get stuck because your ROM is too low
3. The safest/fastest is install RUU but again you need a USB 2.0 (I'm not sure whether you can install RUU zip using the external_sd method).
4. Back to no. 2 - you can install the firmware.zip using the external_sd method (need to do it twice) then install TWRP again the external_sd method then you need to install a ROM or restore a backup meant for the newer hboot 3.19
Click to expand...
Click to collapse
If I wanted to attempt #3, please point me to the correct version as it wasn't clear to me what file to choose here:
http://forum.xda-developers.com/showthread.php?t=2701376
Thanks!
http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
1. put device on fastboot/bootloader mode
2. run the exe (select run as administrator in windows context menu
3. follow instruction - accept, next, next, blablabla until finish
ckpv5 said:
http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
1. put device on fastboot/bootloader mode
2. run the exe (select run as administrator in windows context menu
3. follow instruction - accept, next, next, blablabla until finish
Click to expand...
Click to collapse
The whole point of this exercise is to gain root so that yes, I can have the option of flashing a custom ROM. I noticed in the executable's file name you referenced model M8_UL_L50, but mine is M8_UL_CA. I also noticed its radio version differs from the one listed in my getvar all file. *edit* I've now realized this file is straight from HTC.
Since my current version is so old, is it still OK to run this to update to the latest version rather than updating to an intermediate version before updating to the latest version? Just wanted to confirm before taking any unnecessary action. Thank you again for your patience and the helpful information!
M8_UL - M8 with LTE
L50 - Android L 5.0
CA - US region
Radio version different because yours is old/lower version and this is newer/latest version and you're going to update hboot, radio and many more with this RUU. You need the update in order to install custom ROM as I mentioned before most custom ROMs work only on hboot 3.19.0000
You have S-Off device, you don't need intermediate version ... and most important RUU doesn't need intermediate version because RUU will wipe clean your device and replace all images with those come with it. (So make a backup of your important files to PC)
Sorry about any terminology...
Recently my htc one m8 stopped booting. I had rooted it a long time ago and had a ROM that was working fine for a long time. No recent changes.
On normal boot it sits on the white and green text 'htc' forever.
If I boot with power+down buttons I get to a hboot screen, but choosing 'recovery' takes me to a white screen small pink 'Entering Recovery' text. Nothing happens. To even get power+down screen to be available I had to move two zip files from root of sdcard which I guess were related to the custom rom, being 0P6BIMG.zip and M8-GPE-03-16-2015.zip
I tried reinstalling twrp after downloading the latest .img file
fastboot command
c:\twrp>fastboot flash recovery twrp-3.0.2-0-m8.img
just says <waiting for device> whether on pink text screen or white 'htc'
I can see the sdcard through a pc card reader and manipulate files. Is there any way to copy files manually so it will boot?
This is on Win 10, UK unlocked version of phone.
bt999 said:
To even get power+down screen to be available I had to move two zip files from root of sdcard which I guess were related to the custom rom, being 0P6BIMG.zip and M8-GPE-03-16-2015.zip
Click to expand...
Click to collapse
When you have a file named 0P6BIMG.zip, it will automatically try to install it every time you enter bootloader. Its an update or RUU of some sort, placed there by you, but exactly what is impossible to tell.
The other file is a ROM zip for a GPE ROM, which I would guess is the custom ROM you installed. It doesn't make a difference for this file not be on the SD card or not (bootloader will not try to install it automatically, and bootloader will function normally).
bt999 said:
I tried reinstalling twrp after downloading the latest .img file
fastboot command
c:\twrp>fastboot flash recovery twrp-3.0.2-0-m8.img
just says <waiting for device> whether on pink text screen or white 'htc'
Click to expand...
Click to collapse
Are you in bootloader-fastboot mode when you run the command (which is required)? Meaning, FASTBOOT should be highlighted in red just under the green text on the bootloader screen. If not, just select using the vol buttons, and confirm using power button.
Fastboot clarification
redpoint73 said:
When you have a file named 0P6BIMG.zip, it will automatically try to install it every time you enter bootloader. Its an update or RUU of some sort, placed there by you, but exactly what is impossible to tell.
The other file is a ROM zip for a GPE ROM, which I would guess is the custom ROM you installed. It doesn't make a difference for this file not be on the SD card or not (bootloader will not try to install it automatically, and bootloader will function normally).
Are you in bootloader-fastboot mode when you run the command (which is required)? Meaning, FASTBOOT should be highlighted in red just under the green text on the bootloader screen. If not, just select using the vol buttons, and confirm using power button.
Click to expand...
Click to collapse
Thanks for your reply.
I guess the 0P6BIMG.zip file would explain why it was always slow to boot when things were working ok, if it was being reinstalled each time. I don't recall its purpose.
I wasn't in bootloader-fastboot mode when trying the fastboot command, but have tried it again.
When connected to an Ubuntu 16.04 machine the white on red text says 'fastboot usb', but ubuntu commandline fastboot flash ... gives same 'waiting for device'. When connected to Win 10 white/red text just says 'fastboot', if that is relevant. When I installed fastboot on Win 10 from instructions at http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 there is a note to remove Google drivers before installing new ones - I did not do this, not sure if relevant, but new driver install gave no errors.
Is there a way to copy a new ROM image to the sdcard so that on 'normal' booting it gets detected and applied? Or to copy twrp somewhere manually?
Is there a log file that would show how far through the normal boot things get? I guess it is inaccessible until things work better.
bt999 said:
I wasn't in bootloader-fastboot mode when trying the fastboot command, but have tried it again.
When connected to an Ubuntu 16.04 machine the white on red text says 'fastboot usb', but ubuntu commandline fastboot flash ... gives same 'waiting for device'. When connected to Win 10 white/red text just says 'fastboot', if that is relevant. When I installed fastboot on Win 10 from instructions at http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 there is a note to remove Google drivers before installing new ones - I did not do this, not sure if relevant, but new driver install gave no errors.
Click to expand...
Click to collapse
Try going into Windows Device Manager, finding the device, and picking the option to manually select drivers, and select the generic Android MTP drivers. See if that helps fastboot connect.
Make sure you have HTC drivers (HTC Sync) installed as well. Try to re-install HTC Sync.
bt999 said:
Is there a way to copy a new ROM image to the sdcard so that on 'normal' booting it gets detected and applied? Or to copy twrp somewhere manually?
Click to expand...
Click to collapse
You can't flash a ROM, if TWRP isn't working properly. And there isn't a way to make one automatically flash upon normal boot, that I am aware.
I've seen some folks make 0P6BIMG.zip files for TWRP, which will install automatically when you boot to bootloader. But honestly, USB fastboot connectivity is a pretty vital thing to have working, and usually just a matter of right drivers and a good cable (and being in fastboot mode is a must), so shouldn't be that hard to troubleshoot.
Old twrp
redpoint73 said:
Try going into Windows Device Manager, finding the device, and picking the option to manually select drivers, and select the generic Android MTP drivers. See if that helps fastboot connect.
Make sure you have HTC drivers (HTC Sync) installed as well. Try to re-install HTC Sync.
You can't flash a ROM, if TWRP isn't working properly. And there isn't a way to make one automatically flash upon normal boot, that I am aware.
I've seen some folks make 0P6BIMG.zip files for TWRP, which will install automatically when you boot to bootloader. But honestly, USB fastboot connectivity is a pretty vital thing to have working, and usually just a matter of right drivers and a good cable (and being in fastboot mode is a must), so shouldn't be that hard to troubleshoot.
Click to expand...
Click to collapse
I have got a twrp running, unfortunately it says it is only compatible with bootloader 3.19 and above when I try to install the rom. I have 3.16.
Do you know where I can get an old twrp?
Thanks.
bt999 said:
I have got a twrp running, unfortunately it says it is only compatible with bootloader 3.19 and above when I try to install the rom. I have 3.16.
Do you know where I can get an old twrp?
Thanks.
Click to expand...
Click to collapse
https://dl.twrp.me/m8/
twrp versions
xunholyx said:
https://dl.twrp.me/m8/
Click to expand...
Click to collapse
Thanks. I have now tried
twrp-2.7.0.1-m8.img twrp-2.7.1.0-m8.img twrp-2.8.7.0-m8.img
twrp-2.7.0.2-m8.img twrp-2.8.0.0-m8.img twrp-3.0.2-0-m8.img
The oldest ones don't run the newer ones work but I still get an error on attempting to install the custom ROM. I think I may be misinterpreting the error message. I now think it is telling me the custom ROM needs bootloader 3.19, rather than twrp not being able to run, i.e. twrp knows not to install the rom.
Message 'This package supports bootloader(s): 3.19.0.0000; this device has bootloader 3.16.0.0000'
Do you know how I can update my bootloader?
bt999 said:
Do you know how I can update my bootloader?
Click to expand...
Click to collapse
Post fastboot getvar all result without serial & imei no.
Without proper info, everyone is guessing what you actually need.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(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: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I found this thread http://forum.xda-developers.com/showthread.php?t=2696282 and went through the process with a zip linked from there , but I guess it was old and turned out to still be 3.16
Shouldn't HTC be distributing these files? Or my carrier?
You need to relock bootloader if not yet done.
Command :
fasboot oem lock
fastboot reboot-bootloader
Then follow this : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Put both files in your adb/fastboot folder.
(The guide was written for system-wide adb/fastboot)
Once completed, you can re unlock boorloader and install latest TWRP and install any ROM that you like, if you want to.
I have a working phone now, htc setup screens ended up with no google account prompts or apps, so I installed cwm nightlies and open-gapps hoping I would have full functionality, however gapps was rejected for not having enough internal storage.
I don't care whether htc or cwm but need gapps/play store. Is there anything you can suggest?
/Last reply lost..]I now have a working phone with cwm nightlies. Unfortunately open-gapps wont install saying not enough space on internal drive.
Any suggestions on how to clear space or to make HTC install Google accounts/store (it did not ask)?
I have a working phone now.
RUU didn't install google app store, so I installed cwm nightlies. I got an error that there was not enough space on internal for open-gappps.
Is there a way to free up space?
bt999 said:
I have a working phone now.
RUU didn't install google app store, so I installed cwm nightlies. I got an error that there was not enough space on internal for open-gappps.
Is there a way to free up space?
Click to expand...
Click to collapse
I have no idea what cwm nightlies is ... but if you have this kind of error not enough internal space ... you need to format data (not wipe) in TWRP.
Install latest TWRP, select wipe - format data - yes ... reboot to recovery again, now you can install ROM.
Solved
ckpv5 said:
I have no idea what cwm nightlies is ... but if you have this kind of error not enough internal space ... you need to format data (not wipe) in TWRP.
Install latest TWRP, select wipe - format data - yes ... reboot to recovery again, now you can install ROM.
Click to expand...
Click to collapse
I installed a mini gapps that had just Play Store then installed other apps manually through that.
Thank you all for your help, this is a well-informed forum.
For anyone reading one thing I learned was to run fastboot from Ubuntu/Linux with 'sudo' or else it will not connect, just says 'waiting for device'
ckpv5 said:
I have no idea what cwm nightlies is
Click to expand...
Click to collapse
He means CM, not CWM. Easy mistake to make (adding one letter) but the two are completely different things (Cyanogen Mod custom ROM versus Clockwork Mod custom recovery).
Hello ..
i have htc one m8 and for some reason it's on deep freeze like on a same system restore point everytime i reboot i find the same
apps installed , pics and missed calls no matter how many times i erase all that and if i installed new apps every reboot it's
not there , and everytime i open recovery mode or factory reset it gives me black screen with red triangle (have to vol up +
power to reboot) ,tried to unlock bootloader using htc dev did all steps and when finally get to unlock bootloader screen on my
phone , i clicked yes and phone rebooted to black screen with red triangle and when i rebooted it's like nothing has been done
and still locked, i tried using official twrp from play store i managed for 1 time to open recovery mode and i wiped all data ,
erased the cache and when i rebooted it's the same issue .. tried to flash recovery using cmd still doesn't work (failed : remote
not allowed) , and also HTC sync manager doesn't recognize the phone , dk what to do , wasted alotta time trying to solve this
but no vain , plz help
*FastBoot*
*** Locked ***
M8_WHL PVT SHIP S-OFF
CID-11111111
HBOOT-3.18.0.0000
RADIO-1.08.20.0612_4
OpenDSP-v38.2.2-00542-M874.0311
OS-3.30.651.2
eMMC-boot 2048
Jul 7 2014,20:03:18.3
*getvar all*
version: 0.5
version-bootloader: 3.18.0.0000
version-baseband: 1.08.20.0612_4
version-cpld: None
version-microp: None
version-main: 3.30.651.2
version-misc: PVT SHIP S-OFF
imei2: Not Support
meid: **************
product: m8_whl
platform: hTCBmsm8974
modelid: 0P6B70000
cidnum: 11111111
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: d4c3cae5
hbootpreupdate: 11
gencheckpt: 0
Try to flash stock ruu, if isn't working it's probably a dead nand.
Devil_55 said:
Hello ..
everytime i open recovery mode or factory reset it gives me black screen with red triangle (have to vol up + power to reboot)
Click to expand...
Click to collapse
Black screen with red triangle is the stock recovery. So that is expected. Hold vol up, and press and release power button, to show the stock recovery menu options.
Devil_55 said:
tried to flash recovery using cmd still doesn't work (failed : remote not allowed)
Click to expand...
Click to collapse
That message is expected when trying to flash custom recovery with a locked bootloader. TWRP is only going to flash if the bootloader is unlocked.
Since you are s-off, you can also try the following method to unlock the bootloader: https://forum.xda-developers.com/showthread.php?t=2708571
However, I agree with the previous reply, given the random bugs and behavior, it is best to RUU to a full stock factory image. RUU will wipe the phone, but it sounds like you are trying to wipe user data, anyway. You have the Sprint version M8, and the correct RUUs are here (do not try RUU for any other M8 version! permanent damage is possible):
https://forum.xda-developers.com/showthread.php?t=2729173
You can try any of the RUUs there. But note that if you try the Marshmallow RUU, you will have to flash corresponding Marshmallow firmware.zip before the RUU will install properly (this is clearly indicated in red caps text on the linked thread).
I also agree with the previous response. The behavior is really suspicious (changes don't "stick", bootloader does not unlocked) and NAND failure is a real possibility, especially if the problems persist after RUU.
lucyr03 said:
Try to flash stock ruu, if isn't working it's probably a dead nand.
Click to expand...
Click to collapse
Thanks for your Help
redpoint73 said:
Since you are s-off, you can also try the following method to unlock the bootloader: https://forum.xda-developers.com/showthread.php?t=2708571.
Click to expand...
Click to collapse
I tried this method but still locked
redpoint73 said:
However, I agree with the previous reply, given the random bugs and behavior, it is best to RUU to a full stock factory image. RUU will wipe the phone, but it sounds like you are trying to wipe user data, anyway. You have the Sprint version M8, and the correct RUUs are here (do not try RUU for any other M8 version! permanent damage is possible):
https://forum.xda-developers.com/showthread.php?t=2729173.
Click to expand...
Click to collapse
I'm on 4.4.2 which one should i use (the non-HK i guess since my modelid is 0P6B70000) , i really want the easiest and most detailed way to flash the RUU
and sry for asking this (Do i just unzip the RUU and install or some codes are involved) cuz i downloaded RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_4.25.651.14_Radio_1.09.20.0209_NV_SPCS_1.52_003_release_426232_signed_2.exe
and installed it but nothing happened
also i wanna mention that this phone came from china and i read abt this Region\carrier codes so maybe while someone trying to fix it change it to Sprint[US] (dk if that is possible) (i'm just guessing i dk if we could use this information)
and Huge thanks to you
Devil_55 said:
I'm on 4.4.2 which one should i use (the non-HK i guess since my modelid is 0P6B70000)
Click to expand...
Click to collapse
Both HK and non-HK versions have the same model number 0P6B70000. The only different is in software/firmware.
Your OS number in getvar (3.30.651.2) leads me to believe it was originally non-HK (the "651" signifies this). But it's possible that the previous seller changed it from HK to non-HK (although I'd say that is unlikely).
Really since you are SuperCID, either RUUs will work (HK or non-HK). You can try 3.30.651.2, or the one you downloaded 4.25.651.14 is fine as well.
Devil_55 said:
i really want the easiest and most detailed way to flash the RUU
and sry for asking this (Do i just unzip the RUU and install or some codes are involved) cuz i downloaded RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_4.25.651.14_Radio_1.09.20.0209_NV_SPCS_1.52_003_release_426232_signed_2.exe
and installed it but nothing happened
Click to expand...
Click to collapse
The .exe format RUU is probably the simplest method. PC is required.
Do not unzip or do anything special to the RUU. Connect the phone to PC, with phone in bootloader mode. You should be able to just double click the exe file, and it should launch the application, which just walks you through the installation.
Are you saying you double clicked the exe file, and nothing happened? Or that it fully installed, but the phone is in the same state?
Devil_55 said:
also i wanna mention that this phone came from china and i read abt this Region\carrier codes so maybe while someone trying to fix it change it to Sprint[US] (dk if that is possible)
Click to expand...
Click to collapse
No, that isn't possible. The Sprint version M8 is different from all other versions. Trying to flash Sprint version firmware/RUU to any other M8 version results in a radio brick (no SIM, no cell service).
We see on this forum a lot of folks with the Sprint version M8 which have been made s-off and SuperCID (by seller/vendor) to unlock them for use in other countries, and to appear "unbranded" (when they are in fact, far from it).
your Help is much appriciated
redpoint73 said:
Do not unzip or do anything special to the RUU. Connect the phone to PC, with phone in bootloader mode. You should be able to just double click the exe file, and it should launch the application, which just walks you through the installation.
Are you saying you double clicked the exe file, and nothing happened? Or that it fully installed, but the phone is in the same state?).
Click to expand...
Click to collapse
It did nothing bcuz phone was on bootloader menu but when i tried RUU while phone was booted , wizard moved on to the next step ,
wizard tried to flash RUU but it's stuck on waiting for bootloader , and instead of the phone boot into bootloader it just reboot into the same restore point as if nothing happened.
-https://onedrive.live.com/?cid=AC7BFAC4E523EA2B&id=AC7BFAC4E523EA2B%21340&parId=root&o=OneUp
- it kinda does that in every process before last step (rebooot) , I tried
1-Flash Firmware via Hboot (requires micro sd card)....
-rename firmware to 0P6BIMG.zip
-copy 0P6BIMG.zip to ext_sd card
-boot into bootloader
-make sure hboot is highlighted, press power button
-it will scan your ext_sd card, then ask if you want to start the update
-press volume up & let it do it's thing...
*reboot after pressing up
2- Flash Firmware via fastboot, no ext sd card needed....
-rename firmware to firmware.zip
-copy firmware.zip to your sdk folder
-boot into bootloader
-plug in usb
-select fastboot option (screen should say fastboot usb)
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
* Reboot regularly after fastboot oem rebootRUU
3- ARUwizard to flash 3.30.651.2 stuck at same point (waiting for bootloader) then phone reboot regularly
Is there any other way to flash