bricked?? - One (M8) Q&A, Help & Troubleshooting

Hello, i am having a big trouble here
I was trying to format my phone but the bootloader's screen does not appear, it's been a while, when I enter the bootloader screen is just black, but the options work , I entered on recovery screen and went wipe, ticked all the options and I wipe , now my phone does not show anything, only black screen.
When i press power+up for 15 seconds, the cell shakes, i can flash recovery using fastboot by cmd, i can use anything with fastboot, but if i try something with adb, it says that i dont have adb devices. Can i solve my problem using fastboot option? i already flash a recovery by fastboot, but i cant enter on recovery, i can enter on fastboot reboot-bootloader for example.
Someone can help me plz?
Thx for attention. And sorry for bad english hehehe

Tirania_br said:
but if i try something with adb, it says that i dont have adb devices.
Click to expand...
Click to collapse
This is normal, and as it should be. adb command only work within OS and recovery, adb command do NOT work in bootloader.
I've seen a few reports of this issue (black screen in bootloader, although the options work if you select them "blindly"). If an RUU exists for your version, I would try to run that RUU, and see if that helps.

redpoint73 said:
This is normal, and as it should be. adb command only work within OS and recovery, adb command do NOT work in bootloader.
I've seen a few reports of this issue (black screen in bootloader, although the options work if you select them "blindly"). If an RUU exists for your version, I would try to run that RUU, and see if that helps.
Click to expand...
Click to collapse
thx, i found a RUU for my phone but very old, and found another current version here, but not for my version.
i have s-off on phone, these the information
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.709.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) cidnum: HTC__621
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I dont have any acess on cellphone screen, all i can do is fastboot code on my pc.
I have 2 questions.
How can i flash this RUU in my situation?
Is better use the old RUU of my version or the new of another version? i can use because i am s-off, or am i wrong?
thx for help

Tirania_br said:
I dont have any acess on cellphone screen, all i can do is fastboot code on my pc.
I have 2 questions.
How can i flash this RUU in my situation?
Click to expand...
Click to collapse
RUU is ideal to flash in fastboot mode. So being in fastboot mode (even if you can't see the screen) is a good thing.
Tirania_br said:
Is better use the old RUU of my version or the new of another version? i can use because i am s-off, or am i wrong?
Click to expand...
Click to collapse
Either should work under the proper conditions below:
1) Older RUU for your version may fail with Error 155. Going back to pre-MM by RUU usually requires flashing the older fimrware.zip, then RUU in order to bypass Error 155.
2) S-off alone is not enough to flash another version's RUU. You need to change the CID, and possibly the MID (if its different from what the RUU requires). But those aren't difficult with s-off.
Now, whether either one of those will help your issue (blank screen on bootloader) is the big question. But I'd say RUU is your best bet at a fix.

redpoint73 said:
RUU is ideal to flash in fastboot mode. So being in fastboot mode (even if you can't see the screen) is a good thing.
Either should work under the proper conditions below:
1) Older RUU for your version may fail with Error 155. Going back to pre-MM by RUU usually requires flashing the older fimrware.zip, then RUU in order to bypass Error 155.
2) S-off alone is not enough to flash another version's RUU. You need to change the CID, and possibly the MID (if its different from what the RUU requires). But those aren't difficult with s-off.
Now, whether either one of those will help your issue (blank screen on bootloader) is the big question. But I'd say RUU is your best bet at a fix.
Click to expand...
Click to collapse
Hi, before i do all steps i want to know if i will do everyting ok
my cell's information again
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.709.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
i didnt get RUU of my version. I got 4.17.1540.9 - HTC One U.S. Developer Edition.
The steps
fastboot oem writecid BS_US002
fastboot reboot-bootloader
fastboot oem lock - i really need to do this?
fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip OR Double-click the file and run it as any other executable program.
Its alright?

Tirania_br said:
i didnt get RUU of my version. I got 4.17.1540.9 - HTC One U.S. Developer Edition.
The steps
fastboot oem writecid BS_US002
fastboot reboot-bootloader
fastboot oem lock - i really need to do this?
fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip OR Double-click the file and run it as any other executable program.
Its alright?
Click to expand...
Click to collapse
Just changing the CID is not enough to run that RUU, you need to match the Dev Edition MID as well. Instructions here: http://forum.xda-developers.com/showthread.php?t=2708581
The 4.17.1540.9 RUU is Lollipop. So it will probably fail with Error 155 as I already point out (Item 1 in my last post) forcing you to flash the firmware seperately, then RUU again. You're adding more complexity than needed (for no good reason). Therefore, I'd suggest the Dev Edition MM RUU 6.12.1540.4, if you are going to convert to Dev Edition (CID, MID, etc.). RUU 6.12.1540.4 linked at the bottom of the following: http://www.htc.com/us/support/htc-one-m8/news/
No need to relock the bootloader. This isn't required to RUU since you are s-off (only required to RUU when s-on). And I also do not recommend to lock the bootloader. There is no benefit to doing so in your case (since its not required to RUU) and an unlocked bootloader gives you more options if you run into more issues (you can flash custom recovery, etc.). So locking the bootloader is a waste of steps and time, and limits your options.

redpoint73 said:
Just changing the CID is not enough to run that RUU, you need to match the Dev Edition MID as well. Instructions here: http://forum.xda-developers.com/showthread.php?t=2708581
The 4.17.1540.9 RUU is Lollipop. So it will probably fail with Error 155 as I already point out (Item 1 in my last post) forcing you to flash the firmware seperately, then RUU again. You're adding more complexity than needed (for no good reason). Therefore, I'd suggest the Dev Edition MM RUU 6.12.1540.4, if you are going to convert to Dev Edition (CID, MID, etc.). RUU 6.12.1540.4 linked at the bottom of the following: http://www.htc.com/us/support/htc-one-m8/news/
No need to relock the bootloader. This isn't required to RUU since you are s-off (only required to RUU when s-on). And I also do not recommend to lock the bootloader. There is no benefit to doing so in your case (since its not required to RUU) and an unlocked bootloader gives you more options if you run into more issues (you can flash custom recovery, etc.). So locking the bootloader is a waste of steps and time, and limits your options.
Click to expand...
Click to collapse
thank you! i am almost there!
now the steps i have to do:
adb shell
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
adb reboot bootloader
fastboot getvar all //see if change mid
fastboot fastboot reboot-bootloader
fastboot oem writecid BS_US002
fastboot reboot-bootloader
fastboot getvar all //see if change cid
fastboot oem rebootRUU //need do this? if my Ruu is .exe
Double-click the file and run it as any other executable program. Follow the instructions by the program.
I have only one big problem now, the first command, i cant use adb, i can only use with fastboot, don't know why. adb device cant find, i have the drivers, the pc does a sound when i connect the phone, if i press power button on black screen bootloader i enter in fastboot mode and this commands i can do.
there is a command to do this with fastboot?

Tirania_br said:
I have only one big problem now, the first command, i cant use adb, i can only use with fastboot, don't know why. adb device cant find, i have the drivers, the pc does a sound when i connect the phone, if i press power button on black screen bootloader i enter in fastboot mode and this commands i can do.
Click to expand...
Click to collapse
adb command don't work in bootloader, as I already stated.
Do you still have TWRP custom recovery (its not clear, based on your descriptions so far). If so, boot into recovery, and try adb commands.

redpoint73 said:
adb command don't work in bootloader, as I already stated.
Do you still have TWRP custom recovery (its not clear, based on your descriptions so far). If so, boot into recovery, and try adb commands.
Click to expand...
Click to collapse
I did not have more , when I tried to enter on recovery mode the cell came into loop , I downloaded a new version of the recovery , for my surprise it worked! got access to recovery , now everything was much easier! thank you for help and understanding. Now I have my phone back ! haha

Tirania_br said:
I did not have more , when I tried to enter on recovery mode the cell came into loop , I downloaded a new version of the recovery , for my surprise it worked! got access to recovery , now everything was much easier! thank you for help and understanding. Now I have my phone back ! haha
Click to expand...
Click to collapse
i thinked my problem was gone, but when i try to run the Ruu i get always error 155.
i think is because my cellphone is cdma, from taiwan...
I took back my old cid and mid, restored a nandroid and now is ok.
The bootloader still with black screen, but i can live with it.
Thank u for attention, u help me a lot

Tirania_br said:
i thinked my problem was gone, but when i try to run the Ruu i get always error 155.
i think is because my cellphone is cdma, from taiwan...
I took back my old cid and mid, restored a nandroid and now is ok.
The bootloader still with black screen, but i can live with it.
Thank u for attention, u help me a lot
Click to expand...
Click to collapse
First .. your device is not a CDMA device, it is a GSM.
What you can try to fix that bootloader with black screen ... flash full signed 6.20.709.2 firmware.zip.
You can get the full signed firmware in my thread (post #5) : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

Related

help with get back stock rom from custom rom

hi, i have this htc one x.
this is fastboot info (fastboot getvar all)
Code:
(bootloader) version: 0.5a
(bootloader) [COLOR="Red"]version-bootloader: 1.39.000[/COLOR]0
(bootloader) version-baseband: 5.1204.164.30H
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) [COLOR="Red"]version-main: 3.14.771.34[/COLOR]
(bootloader) serialno: HT23TW126661
(bootloader) imei: 359188042590570
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) [COLOR="Red"]cidnum: H3G__G04[/COLOR]
(bootloader) battery-status: good
(bootloader) battery-voltage: 4179mV
(bootloader) devpower: 100
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.826s
actually it has running cyanogen rom, but i wanna get back to stock rom.
as info, i haven't nandroid backup or anything else.
i have downloaded latest ruu from Hutchison, but i don't find exactly rom. H3G__G04 (H3G_SWE)
i have downloaded rom from H3G from UK. and i tried flash this rom, but i get bootloader error.
i almost forget it. i was locked bootloader to run RUU, and i have read many threads from forum.
anybody can help me to get back to stock rom please?
hyber_99 said:
hi, i have this htc one x.
actually it has running cyanogen rom, but i wanna get back to stock rom.
as info, i haven't nandroid backup or anything else.
i have downloaded latest ruu from Hutchison, but i don't find exactly rom. H3G__G04 (H3G_SWE)
i have downloaded rom from H3G from UK. and i tried flash this rom, but i get bootloader error.
i almost forget it. i was locked bootloader to run RUU, and i have read many threads from forum.
anybody can help me to get back to stock rom please?
Click to expand...
Click to collapse
What sense version do you want in result: 4+ or 5?
Did you update your phone via OTA earlier?
Post bootloader error here, please. Looks like your bootloader is updated and do not match requirements to flash RUU from Hutchison.
1.- i dont know what is better, if 4+ or 5.
2.- in fact the phone was updated by other person, i don't know what he did :/
3.- let me flash ruu again and post bootloader error.
if it's usefull, it has Team Win Recovery Project v2.4.1.0 installed.
thanks for reply
genocide_ru said:
What sense version do you want in result: 4+ or 5?
Did you update your phone via OTA earlier?
Post bootloader error here, please. Looks like your bootloader is updated and do not match requirements to flash RUU from Hutchison.
Click to expand...
Click to collapse
Error 140, error with bootloader version.
and if i try with Europe RUU i got Error with Carrier ID.
hyber_99 said:
Error 140, error with bootloader version.
and if i try with Europe RUU i got Error with Carrier ID.
Click to expand...
Click to collapse
Well, looks like firmware\hboot was updated and latest RUU for your CID requires older firmware\hboot.
So, you can't use old RUU to go back to stock.
You need to flash stock ROM for 1.39 hboot from recovery
Try to find ROM like this one, but older: http://forum.xda-developers.com/showthread.php?t=1546970&highlight=*stock*
I guess you need to search 3.18 or 3.20 version, don't remember wwich one will work with 1.39
ok, i'll search it.
thank you sir, i'll let you know the results.
one more question, can i use this method posted here? http://forum.xda-developers.com/showthread.php?t=1927048
exactly this:
Nand for H3G__106 - thanks to Jackster88
Part 1
Part 2
Quote:
Instructions:
***For this nand to work you need HBOOT 1.39 and cwm***
1) go into fastboot and enter "fastboot oem lock" - the device will reboot
2) go into fastboot again and enter "fastboot oem rebootRUU" - there will be a black screen with a silverish HTC logo
3) enter "fastboot flash zip firmware.zip" (you need the firmware.zip from page 1 for this)
3a) enter the same again, the green bar under the logo should go to 100% (either after the first or second time)
4) enter "fastboot reboot-bootloader" to go back to your fastboot
5) unlock your device again with the unlock code ("fastboot flash unlocktoken Unlock_code.bin")
6) Restore your old boot.img (fastboot flash boot name_of_boot_file.img) and recovery (fastboot flash recovery name_of_recovery_file.img), make sure you copied them from the nandroid backup folder we created earlier into the folder that contains the fastboot.exe you're using.
7) Reboot and you should now have Hboot 1.39 with your old boot and recovery.
(8) If it won't work we still have the backup ready to restore the old system, Hboot isn't changeable right now on S-ON devices outside of the RUU routine - so even if you restore your nandroid you should still have Hboot 1.39 now)
Confirmed working with H3G__001, H3G__003, H3g__G04
Click to expand...
Click to collapse
hyber_99 said:
one more question, can i use this method posted here? http://forum.xda-developers.com/showthread.php?t=1927048
exactly this:
Click to expand...
Click to collapse
yes, you can try this method
except, I guess you need not flash firmware, because you are already on 1.39
genocide_ru said:
yes, you can try this method
except, I guess you need not flash firmware, because you are already on 1.39
Click to expand...
Click to collapse
thank you very much.
after all i solve my problem installing RENOVATE Final 4 Rom ------ http://forum.xda-developers.com/showthread.php?t=1705334&highlight=3+20
after installing rom, we need flash kernel manually i flashed stock kernel.
my problem was that with cyanogen 10.1 this phone cann't accept unlocking code,
but now with renovate rom, code was accepted and phone now is sim unlocked
thank you very much for your time
hyber_99 said:
thank you very much.
my problem was that with cyanogen 10.1 this phone cann't accept unlocking code,
but now with renovate rom, code was accepted and phone now is sim unlocked
thank you very much for your time
Click to expand...
Click to collapse
No problem, man!
Glad I helped you with this :good:

[Q] Current FW version?

I just went S-OFF on my device.
I'm looking for what my current firmware version is... Before i start updating roms.
Anyone knows where i can find it, or what the command is trough ADB? If i need to check main-version to see the fw version i am screwd i guess... Since that is blank!
What software build are you on at the moment? e.g. 1.54.401.10?
Yes, ARHD 7.0 was based on that i believe.
I am on that software version, never flashed that firmware.zip though since it came out with ARHD 8.
EDIT: I just checked the phone and ROM Version is indeed 1.54.401.10.
You find the firmware version in Settings > About > Software Information
Latest is 1.55.605.2
Niorun said:
Yes, ARHD 7.0 was based on that i believe.
I am on that software version, never flashed that firmware.zip though since it came out with ARHD 8.
EDIT: I just checked the phone and ROM Version is indeed 1.54.401.10.
Click to expand...
Click to collapse
OK, if you're now on a custom ROM then it won't actually be the version you were originally on. Boot the phone into fastboot and then type the following command:
fastboot getvar all
and then post the results (deleting the IMEI and serial number). We'll then be able to confirm the FW build on your device
EddyOS said:
OK, if you're now on a custom ROM then it won't actually be the version you were originally on. Boot the phone into fastboot and then type the following command:
fastboot getvar all
and then post the results (deleting the IMEI and serial number). We'll then be able to confirm the FW build on your device
Click to expand...
Click to collapse
Doesn't getprop give the same results? getprop ro.build.description should give the version number 1.54.401.10 blahblahblah release-keys and ro.aa.romver shows it as well, ok given, y ou need a terminal emulator to check it...?
BerndM14 said:
Doesn't getprop give the same results? getprop ro.build.description should give the version number 1.54.401.10 blahblahblah release-keys and ro.aa.romver shows it as well, ok given, y ou need a terminal emulator to check it...?
Click to expand...
Click to collapse
Possibly, I've always just done the getvar command as it gives everything in one hit...
EddyOS said:
Possibly, I've always just done the getvar command as it gives everything in one hit...
Click to expand...
Click to collapse
Yeah I know and it's a bit more organised etc. Just figured that doing getprop would make it easier, instead of rebooting and hooking up etc etc just open an emulator and type the simple command. Of course getprop dumps the entire build.prop file in the emulator so you get to see all the same info as well, CID, MID, Version number so forth...
Where does getvar get the info from? Also from the build.prop file?
EddyOS said:
OK, if you're now on a custom ROM then it won't actually be the version you were originally on. Boot the phone into fastboot and then type the following command:
fastboot getvar all
and then post the results (deleting the IMEI and serial number). We'll then be able to confirm the FW build on your device
Click to expand...
Click to collapse
(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAPE17
(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
all: Done!
finished. total time: 0.017s
I've posted above information before with Serial # and IMEI... (I've already editted those posts though) What could be done with them?
OK, still doesn't show it BUT it does show you have a Vodafone Netherlands handset
(bootloader) cidnum: VODAPE17
So the FW you'd need would be one from their OTA update, but you're not currently on the latest FW as the latest radio is 1.16 and you're still on 1.15. I'll see if I can find it for you but can't promise anything...
EddyOS said:
OK, still doesn't show it BUT it does show you have a Vodafone Netherlands handset
(bootloader) cidnum: VODAPE17
So the FW you'd need would be one from their OTA update, but you're not currently on the latest FW as the latest radio is 1.16 and you're still on 1.15. I'll see if I can find it for you but can't promise anything...
Click to expand...
Click to collapse
I already mentioned that if you're looking for 'version-main' it'd be blank but still... There should be a way to find out, right?
I've already looked for a newer Radio and Firmware version on XDA but were unable to locate the correct one. I also opened a thread about that earlier... (see: http://forum.xda-developers.com/showthread.php?t=2765454) But no response from anyone though.
Thanks in advance anyway searching for it.
EDIT: I could always change my CID to SuperCID i believe, but i haven't read up on it alot though. And since i am S-OFF now i would like to be 100% sure before flashing anything from now on...
BerndM14 said:
Yeah I know and it's a bit more organised etc. Just figured that doing getprop would make it easier, instead of rebooting and hooking up etc etc just open an emulator and type the simple command. Of course getprop dumps the entire build.prop file in the emulator so you get to see all the same info as well, CID, MID, Version number so forth...
Where does getvar get the info from? Also from the build.prop file?
Click to expand...
Click to collapse
That is the other thing to keep in mind. The build.prop in your device is going to be whatever the developer made it be. They often times change version numbers, or use a common model number, so it may not be accurately reflecting anything about the device in it's original state.
Considering you are in fastboot when running this, I would say it is not pulling it from the build.prop, but rather one of the registers or from the bootloader itself.
Niorun said:
I already mentioned that if you're looking for 'version-main' it'd be blank but still... There should be a way to find out, right?
I've already looked for a newer Radio and Firmware version on XDA but were unable to locate the correct one. I also opened a thread about that earlier... (see: http://forum.xda-developers.com/showthread.php?t=2765454) But no response from anyone though.
Thanks in advance anyway searching for it.
EDIT: I could always change my CID to SuperCID i believe, but i haven't read up on it alot though. And since i am S-OFF now i would like to be 100% sure before flashing anything from now on...
Click to expand...
Click to collapse
As you're S-OFF you could set the phone to HTC__001, flash the 1.54.401.10 FW and then you're all up-to-date, yes
EddyOS said:
As you're S-OFF you could set the phone to HTC__001, flash the 1.54.401.10 FW and then you're all up-to-date, yes
Click to expand...
Click to collapse
What about MID in that case? That does not match.
Niorun said:
What about MID in that case? That does not match.
Click to expand...
Click to collapse
All European devices have the same MID so no worries there
EddyOS said:
All European devices have the same MID so no worries there
Click to expand...
Click to collapse
Alright, any specific FW I need or can I download 1.54.401.10 from ARHD's site and flash that with adb fastboot after i've changed my CID.
That would also update my Radio to the current version if i am not mistaken.
Niorun said:
Alright, any specific FW I need or can I download 1.54.401.10 from ARHD's site and flash that with adb fastboot after i've changed my CID.
That would also update my Radio to the current version if i am not mistaken.
Click to expand...
Click to collapse
The 1.54.401.10 package on the ARHD site is fine
EddyOS said:
The 1.54.401.10 package on the ARHD site is fine
Click to expand...
Click to collapse
I am on CID HTC__001 now, still got a question about to procedure below.
First of all it states that the bootloader needs to be relocked, then it says if you are S-OFF it doesn't need to be relocked. While following the steps you need to relock it. And the last step is to unlock it again...
I am quite confused here, does the bootloader needs to be locked or unlocked while being S-OFF?
How to flash?
(bootloader needs to be relocked)
If you are S-ON ---> Re-lock your bootloader (this will most probably wipe content of your device)
If you are S-OFF ---> no need to re-lock the bootloader.
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem lock (if your device is not relocked yet or in case it's S-ON)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
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.
Click to expand...
Click to collapse
If you're S-OFF...
1. Boot into fastboot
2. fastboot oem rebootRUU
3. fastboot flash zip <filename>.zip
4. fastboot flash zip <filename>zip (again, just in case)
5. fastboot reboot-bootloader
6. Confirm version in fastboot
7. Reboot phone
EddyOS said:
If you're S-OFF...
1. Boot into fastboot
2. fastboot oem rebootRUU
3. fastboot flash zip <filename>.zip
4. fastboot flash zip <filename>zip (again, just in case)
5. fastboot reboot-bootloader
6. Confirm version in fastboot
7. Reboot phone
Click to expand...
Click to collapse
Thanks a million EddyOS for helping me once again! While i were at it, updated TWRP and ARHD as well. Maybe a little note i was only able to see my firmware version one time. (step 6.) Any other boot to the bootloader is showing an empty OS field again, also from the fastboot getvar all command the main-version is showing an emtpy entry again.
Still struggling with my backup though, somehow TitaniumBackup isn't displaying my backup. Unknown sources are allowed.

[Solved] No OS, No Recovery HELP please HTC One (M8) Unlocked

I have a US HTC One M8 that I bought direct unlocked from htc's site direct in January 2015.
I rooted my device, and was running Paranoid Android 5.1 with TWRP recovery and decided to switch back to stock so I could sell the device.
I downloaded the RUU for my device from htc's site (ruu 6.12.1540.4 for unlocked/developer htc one m8).
I plugged in my device, typed in "fastboot oem lock" until the top of the bootloader said "Software status: modified" and "RELOCKED."
Then I ran the RUU but got Error 155 saying it was the wrong RUU. My device now had a silver HTC logo stuck in the middle. I pressed the power + volume down and got to the bootloader.
But now there is no option for "Recovery" in the bootloader, and the "Reboot" option just takes me straight back to the bootloader.
Here is what it says at the bootloader now:
***Software status: Modified***
*** RELOCKED***
***Security Warning ***
It says OS-4.16.1540.8
In addition, I can't charge without the screen being on. I plug in my phone and it shows the battery icon for a few seconds and then goes back into the booloader with "fastboot ac"
Please help me get my device working & back to stock. Any information or tips will help. I can take photos and provide with any additional information if needed.
Thanks.
AeroPeg said:
I have a US HTC One M8 that I bought direct unlocked from htc's site direct in January 2015.
I rooted my device, and was running Paranoid Android 5.1 with TWRP recovery and decided to switch back to stock so I could sell the device.
I downloaded the RUU for my device from htc's site (ruu 6.12.1540.4 for unlocked/developer htc one m8).
I plugged in my device, typed in "fastboot oem lock" until the top of the bootloader said "Software status: modified" and "RELOCKED."
Then I ran the RUU but got Error 155 saying it was the wrong RUU. My device now had a silver HTC logo stuck in the middle. I pressed the power + volume down and got to the bootloader.
But now there is no option for "Recovery" in the bootloader, and the "Reboot" option just takes me straight back to the bootloader.
Here is what it says at the bootloader now:
***Software status: Modified***
*** RELOCKED***
***Security Warning ***
It says OS-4.16.1540.8
In addition, I can't charge without the screen being on. I plug in my phone and it shows the battery icon for a few seconds and then goes back into the booloader with "fastboot ac"
Please help me get my device working & back to stock. Any information or tips will help. I can take photos and provide with any additional information if needed.
Thanks.
Click to expand...
Click to collapse
Are you S-Off? Is your device Developer Edition?
Sent from my HTC One_M8 using Tapatalk
AeroPeg said:
I have a US HTC One M8 that I bought direct unlocked from htc's site direct in January 2015.
I rooted my device, and was running Paranoid Android 5.1 with TWRP recovery and decided to switch back to stock so I could sell the device.
I downloaded the RUU for my device from htc's site (ruu 6.12.1540.4 for unlocked/developer htc one m8).
I plugged in my device, typed in "fastboot oem lock" until the top of the bootloader said "Software status: modified" and "RELOCKED."
Then I ran the RUU but got Error 155 saying it was the wrong RUU. My device now had a silver HTC logo stuck in the middle. I pressed the power + volume down and got to the bootloader.
But now there is no option for "Recovery" in the bootloader, and the "Reboot" option just takes me straight back to the bootloader.
Here is what it says at the bootloader now:
***Software status: Modified***
*** RELOCKED***
***Security Warning ***
It says OS-4.16.1540.8
In addition, I can't charge without the screen being on. I plug in my phone and it shows the battery icon for a few seconds and then goes back into the booloader with "fastboot ac"
Please help me get my device working & back to stock. Any information or tips will help. I can take photos and provide with any additional information if needed.
Thanks.
Click to expand...
Click to collapse
about error 155, try the following
1. Lock your bootloader through by booting into hboot and then going into fastboot and issuing the command "fasboot oem lock".
2. Once locked, reboot your system.
3. Open RUU and follow onscreen instructions.
Should work. Best of luck
How do I flash a new recovery?
SergioRmz, My device is S-ON, not developer edition, just factory unlocked from htc
Rawfire, I can't flash a RUU. The RUU just gives me an error after a few seconds from starting it - it says try again with a different RUU / wrong RUU (error 155).
Also, could you help me flash a new recovery? Could I flash a new recovery, then flash someone's stock nandroid backup & recovery to get my device to stock? Can I do all of this with a RELOCKED & S-ON device?
I have no idea how to flash a new recovery so instructions would be very very helpful
One final question - Can you tell me the best way in my current sitatution to get my device to stock without S-OFF? I'm willing to try anything (except S-off) to get my device to stock so I can sell it / trade it in.
AeroPeg said:
SergioRmz, My device is S-ON, not developer edition, just factory unlocked from htc
Rawfire, I can't flash a RUU. The RUU just gives me an error after a few seconds from starting it - it says try again with a different RUU / wrong RUU (error 155).
Also, could you help me flash a new recovery? Could I flash a new recovery, then flash someone's stock nandroid backup & recovery to get my device to stock? Can I do all of this with a RELOCKED & S-ON device?
I have no idea how to flash a new recovery so instructions would be very very helpful
One final question - Can you tell me the best way in my current sitatution to get my device to stock without S-OFF? I'm willing to try anything (except S-off) to get my device to stock so I can sell it / trade it in.
Click to expand...
Click to collapse
I can suggest couple of things, unlock the bootloader to install custom recovery and then you can flash any compatible rom,
Or to suggest some exact RUU, what's your device's exact model?
rawfire said:
about error 155, try the following
1. Lock your bootloader through by booting into hboot and then going into fastboot and issuing the command "fasboot oem lock".
2. Once locked, reboot your system.
3. Open RUU and follow onscreen instructions.
Should work. Best of luck
Click to expand...
Click to collapse
Just tried this, said "Device was already locked!"
Then tried RUU again, still said Error 155 "please get the correct RUU and try again"
When I unplug the phone it says error zip file with RUU written under it, and I had to press power + volume down to get it to the bootloader again.
Thanks for your continued help rawfire.
AeroPeg said:
Just tried this, said "Device was already locked!"
Then tried RUU again, still said Error 155 "please get the correct RUU and try again"
When I unplug the phone it says error zip file with RUU written under it, and I had to press power + volume down to get it to the bootloader again.
Thanks for your continued help rawfire.
Click to expand...
Click to collapse
Considering your firmware, I would suggest you to try THIS RUU & flash...
Device info
Thanks rawfire, downloading it now...
My phone says os-4.16.1540.8
Is there any other device info you need?
AeroPeg said:
Thanks rawfire, downloading it now...
My phone says os-4.16.1540.8
Is there any other device info you need?
Click to expand...
Click to collapse
try this one out, I'm sure it'll work.
Can't open
rawfire said:
try this one out, I'm sure it'll work.
Click to expand...
Click to collapse
Windows says invalid file, can't open.
7 zip can't extract either. I've tried both mirrors
Any other RUU suggestions?
AeroPeg said:
Thanks rawfire, downloading it now...
My phone says os-4.16.1540.8
Is there any other device info you need?
Click to expand...
Click to collapse
Is that os-4.16.1540.8 written on the bootloader ? If yes, you have a Dev Ed device, the other RUU meant for EU won't work for you.
Post fastboot getvar all (without serial & imei no.) then we know the actual device version
If it is indeed a Dev Ed device, what you need to do :
1. flash the 6.12.1540.4 firmware
See this : http://forum.xda-developers.com/showpost.php?p=64407841&postcount=2862
How-to, see this : http://forum.xda-developers.com/showpost.php?p=64416322&postcount=2864
2. Run RUU 6.12.1540.4 after the firmware is installed
Or the easy way is :
find 4.16.1540.8 RUU and install this then after, do OTA to 4.17.1540.9 then 6.12.1540.4
Edit : here is the direct HTC link for 4.16.1540.8 RUU - http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
Fastboot getvar all
ckpv5 said:
Is that os-4.16.1540.8 written on the bootloader ? If yes, you have a Dev Ed device, the other RUU meant for EU won't work for you.
Post fastboot getvar all (without serial & imei no.) then we know the actual device version
If it is indeed a Dev Ed device, what you need to do :
1. flash the 6.12.1540.4 firmware
See this : http://forum.xda-developers.com/showpost.php?p=64407841&postcount=2862
How-to, see this : http://forum.xda-developers.com/showpost.php?p=64416322&postcount=2864
2. Run RUU 6.12.1540.4 after the firmware is installed
Or the easy way is :
find 4.16.1540.8 RUU and install this then after, do OTA to 4.17.1540.9 then 6.12.1540.4
Edit : here is the direct HTC link for 4.16.1540.8 RUU - http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
Click to expand...
Click to collapse
Here's what I got when I typed fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.1540.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.035s
Update: just googled 0P6B12000 is Dev edition, my bad. Going to try easy method of installing the 4.16.1540.8 RUU. Thanks ckpv5. Will post with results.
AeroPeg said:
Here's what I got when I typed fastboot getvar all:
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-main: 4.16.1540.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8_ul_ca
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
Click to expand...
Click to collapse
Then it is confirmed that you have a Dev Ed device.
Go with the easy way that I posted above. Install RUU 4.16.1540.8 then do OTA to the latest, done.
Additional - as you mentioned you're going to sell this device, I suggest after the last OTA 6.12.1540.4 is done, run RUU 6.12.1540.4 to remove all the OTA leftovers in device. You'll have a clean device after the last RUU.
4.16.1540.8 RUU stuck
ckpv5 said:
Then it is confirmed that you have a Dev Ed device.
Go with the easy way that I posted above. Install RUU 4.16.1540.8 then do OTA to the latest, done.
Additional - as you mentioned you're going to sell this device, I suggest after the last OTA 6.12.1540.4 is done, run RUU 6.12.1540.4 to remove all the OTA leftovers in device. You'll have a clean device after the last RUU.
Click to expand...
Click to collapse
4.16.1540.8 RUU has been stuck at "Updating.. (0/7) Sending....." for 20+ minutes now. Phone is showing just the silver htc logo, no progress bar or anything else.
Should I try flashing the 6.12.1540.4 firmware now? Thanks for the help so far ckpv5
Also, is the phone charging while connected to the computer & updating? Just asking since I can't see the battery percent (no OS) and don't want the phone to die while flashing.
AeroPeg said:
4.16.1540.8 RUU has been stuck at "Updating.. (0/7) Sending....." for 20+ minutes now.
Click to expand...
Click to collapse
This show you have USB/PC connection problem. To run RUU you need Windows PC with USB2.0 and the latest HTC USB drivers installed.
See the How-To linked above for the HTC Sync Manager download page, install it as it will install the USB Driver, then uninstall the Sync Manager but leave the driver
While flashing .. charging is minimal, won''t be enough if you don't have at least 70% battery
ckpv5 said:
This show you have USB/PC connection problem. To run RUU you need Windows PC with USB2.0 and the latest HTC USB drivers installed.
See the How-To link above.
While flashing .. charging is minimal, won''t be enough if you don't have at least 70% battery
Click to expand...
Click to collapse
Thanks for the info, going to reinstall HTC Sync Manager and try again. Does it need to be USB 2.0, or can it be USB 3.0?
Also, how long can I charge without having the screen burn because when I plug in the phone to the wall or the the computer, it shows the bootloader screen. It stays in that screen while charging so I don't want to charge for extended periods otherwise screen will burn. Can you tell me if I am right on this?
AeroPeg said:
Thanks for the info, going to reinstall HTC Sync Manager and try again. Does it need to be USB 2.0, or can it be USB 3.0?
Also, how long can I charge without having the screen burn because when I plug in the phone to the wall or the the computer, it shows the bootloader screen. It stays in that screen while charging so I don't want to charge for extended periods otherwise screen will burn. Can you tell me if I am right on this?
Click to expand...
Click to collapse
You must use USB2.0
When in bootloader, choose power down then charge it, you'll see the progress and there will be no screen burn.
If you don't have a USB2.0 - other options :
Option 1:
Clean your PC temp folder - just select "run" then type %temp% and clear all that your can.
Run the RUU again (not necessary to connect to phone), when the RUU dialog open, check in %temp% you should see two new folders are created. Find ROM.zip in one of the folder, copy out the ROM.zip to your desktop. You can close the RUU dialog box.
Rename the RUU.zip to 0P6BIMG.zip (that's a zero not "O") then put it on your microSD.
boot to bootloader then select hboot or boot to hboot - it's your choice
hboot will scan the file and ask to volume up to update
volume up
finish, press power to reboot and do all the setup stuff
remove 0P6BIMG.zip from your microSD
now you have ROM installed then can proceed with OTA and the rest.
Option 2:
Re unlock your bootloader again with your unlock_code.bin that you got from HTC.
Install TWRP 2.8.7.0
Restore a clean non-rooted 4.16.1540.8 nandroid backup and its stock recovery
Reboot.. setup.. OTA..OTA.. done.
You can get all the needed files in the link shown in my signature
So now .. you have 3 options to choose.
1. RUU method
2. 0P6BIMG.zip method
3. Nandroid method
I got to go now ... good luck
SOLUTION - see ckpv5's 3 solutions
ckpv5 said:
You must use USB2.0
When in bootloader, choose power down then charge it, you'll see the progress and there will be no screen burn.
If you don't have a USB2.0 - other options :
Option 1:
Clean your PC temp folder - just select "run" then type %temp% and clear all that your can.
Run the RUU again (not necessary to connect to phone), when the RUU dialog open, check in %temp% you should see two new folders are created. Find ROM.zip in one of the folder, copy out the ROM.zip to your desktop. You can close the RUU dialog box.
Rename the RUU.zip to 0P6BIMG.zip (that's a zero not "O") then put it on your microSD.
boot to bootloader then select hboot or boot to hboot - it's your choice
hboot will scan the file and ask to volume up to update
volume up
finish, press power to reboot and do all the setup stuff
remove 0P6BIMG.zip from your microSD
now you have ROM installed then can proceed with OTA and the rest.
Option 2:
Re unlock your bootloader again with your unlock_code.bin that you got from HTC.
Install TWRP 2.8.7.0
Restore a clean non-rooted 4.16.1540.8 nandroid backup and its stock recovery
Reboot.. setup.. OTA..OTA.. done.
You can get all the needed files in the link shown in my signature
So now .. you have 3 options to choose.
1. RUU method
2. 0P6BIMG.zip method
3. Nandroid method
I got to go now ... good luck
Click to expand...
Click to collapse
Thanks a TON ckpv5. I followed your instructions & reinstalled HTC Sync Manager, then connected the cable to a USB 2.0 port instead of 3.0. The RUU method you originally suggested worked like a charm. I now have stock HTC software, stock recovery just like I wanted. I then did an OTA to the latest software. When I sell my device in a few days, I'll be sure to follow your tip and run the latest 6.12.1540.4 RUU to clear off all the old OTA files.
Many thanks again for your help - hopefully others will see the 3 solutions you posted.
Hi. my mid and bootlader Can i flash 4.16.1540.8 my device gets updated
Thanks..
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(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.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT44LWM05174
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
ceylin45 said:
Hi. my mid and bootlader Can i flash 4.16.1540.8 my device gets updated
Click to expand...
Click to collapse
Yes ... just follow what is written on top post above.

Completely erased Android using TWRP "advanced wipe". HOWTO install the OS again?

Completely erased Android using TWRP "advanced wipe". HOWTO install the OS again?
Hi
As the title says I completely erased my phone. The file structure seems to be there still from a fairly old ARHD 4.4.4 install. I did a Nandroid before doing this and it is backed up on my computer. Because it is an older (KK) ROM I'm on TWRP 2.8.1.0. I've tried to do
1 ADB pushed a version of that over to the device and tried to install with TWRP but it wouldn't install.
2 an ADB sideload of the latest GPE ("blues") by lyapota, but it didn't install. Does this take a super long time, as I'm trying it a second time. First time I cancelled after about 10 mins of no activity.
So, I'm in a bit deep here. At this point I'm even afraid to unplug the phone from the computer as I fear I'll never get it to boot again. Can I still access the phone by turning it on via booting into download mode/recovery?
If generous, can you walk me through step by step? Otherwise, is there a good guide that will step by step me through the process? A 2014 version of this thread referred the poor guy to the FAQ, but it doesn't cover this case.
If you can get/boot to recovery, just enable mtp in mount menu then you can browse your storage on PC.
Transfer your backup to restore or transfer a custom rom zip and install. But most custom rom work on lollipop and marshmallow firmware. As you said yours is a kitkat, there will be problem.
Or while on fastboot/bootloader see what is the hboot no. and the OS no or better to run command fastboot getvar all and post here the result without serial & imei no.
ckpv5 said:
If you can get/boot to recovery, just enable mtp in mount menu then you can browse your storage on PC.
Transfer your backup to restore or transfer a custom rom zip and install. But most custom rom work on lollipop and marshmallow firmware. As you said yours is a kitkat, there will be problem.
Or while on fastboot/bootloader see what is the hboot no. and the OS no or better to run command fastboot getvar all and post here the result without serial & imei no.
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA14G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(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
all: Done!
finished. total time: 0.050s
Should I start looking for a stock kitkat ROM or RUU?
Is there a thread you know of, or a good google search term I can start my learning on?
And most importantly, will anything I do ever eliminate my s-off?
That's a very old firmware that you have there.
It is 1.54.709.12 where the current one is 6.20.709.2; means you already missed 5 or 6 updates.
You can read post #1 on how-to, get the 1.54.709.12 backup on post #2 and the 1.54.709.12 stock recovery.img on post #4 then do multiple OTAs to the latest 6.20.709.2
See my thread : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Noted that you have a S-Off device ... do you have a good reason why the device is S-Off ? Let say the reason was you wanted to make it EU WWE Intl GSM ... then there is another approach to this :
1. You need to change the MID from 0P6B11000 to 0P6B10000
http://forum.xda-developers.com/showthread.php?t=2708581
2. You install EU WWE Intl GSM RUU zip 6.12.401.4
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
ckpv5 said:
That's a very old firmware that you have there.
It is 1.54.709.12 where the current one is 6.20.709.2; means you already missed 5 or 6 updates.
You can read post #1 on how-to, get the 1.54.709.12 backup on post #2 and the 1.54.709.12 stock recovery.img on post #4 then do multiple OTAs to the latest 6.20.709.2
See my thread : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Noted that you have a S-Off device ... do you have a good reason why the device is S-Off ? Let say the reason was you wanted to make it EU WWE Intl GSM ... then there is another approach to this :
1. You need to change the MID from 0P6B11000 to 0P6B10000
http://forum.xda-developers.com/showthread.php?t=2708581
2. You install EU WWE Intl GSM RUU zip 6.12.401.4
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
Sounds OK, will that install a less effective radio, or are radios not affected? I have S-off for exactly this kind of this instance, but i guess it could be construed as the cause too.... The main reason is getting bloat off the ROM though.
Should be fine. As far as I can remember, both TWN and EU have same radio.
The different is slightly on rcdata... but that another story, won't affect anything at where you are now.
Being a S-Off device you can change the OS version at any time that like.
Weird, I downloaded minimal adb fastboot, and I can fastboot devices and get my serial, but adb devices returns device null. Am I missing something? The phone is in bootloader mode. Should I be in TWRP?
I got adb devices by going into TWRP, but now I do adb shell and it returns ~ # <[6n I'm guessing that means I need to be a super user...how? Every time I reboot TWRP it asks me if I want SU, but the process hangs.
Can the HTC utility restore a phone in this state, and not lose s-off? I put the external SD in the phone, with the nandroid I did today, and am trying to transfer it into the bare file system, where should I put it. Why can't TWRP just see the nandroid on the external? WIll the nandroid be of any value to me at this point?
When I try to do this:
6(b). For those with no OS, connect device to PC. In TWRP recovery go to mount, make sure MTP is enabled.
Then you can open Internal Storage - TWRP/BACKUPS/SerialNo./ (if backup is set to internal storage)
7. Transfer the extracted x.xx.xxx.x folder (not x.xx.xxx.x_ckpv5 folder) and its content to the backup path on your device, so it looks like this :
TWRP/BACKUPS/SerialNo./x.xx.xxx.x
it tells me "cannot copy system.ext4.win000" "it's file size is larger than the device limit"
So do I need to re partition somehow? How would I do that? How can I find, and post, what the filesystem layout is now if more info is needed?
I have the TWRP backup on the external SD, but restore won't see it either.
Or what about the Hasson2000 toolkit to push an RUU to it?
Sorry guys, I still need help. I try to do adb shell, but can't seem to get root (su) . Because of this I am afraid of moving forward. I have changed my CID to GOOGL001 using HASOON2000's toolkit as I've decided I might as well go full goog since I'm at this point. I think my MID 0P6B11000 is OK, as it's mentioned in graffixnyc/Enewman17's GPE thread, correct? I've downloaded the MM H11 and it's waiting, but I'm afraid to move forward with the root problem better explained in the post above. Am I overly worried?
downwiththebanksters said:
I got adb devices by going into TWRP, but now I do adb shell and it returns ~ # <[6n I'm guessing that means I need to be a super user...how?
Click to expand...
Click to collapse
No .. while in TWRP you just run adb shell, no need SU because while in TWRP it's already rooted ..
so
adb shell
~ # <[6n
then paste in the code to change MID then type exit, exit
If you want to run the EU WWE RUU that I linked above, you also need to change the CID .. I suggest a SuperCID 11111111 then later you can run anything that you like as long has you have the correct MID for the RUU that you're going to install.
Now .. since you changed the CID to Google CID and intended to install a GPE RUU .. read through the thread that you linked .. can't help much .. maybe someone else will help you for the GPE conversion.
Still I suggest, instead of running a Google CID ... change it to SuperCID so you don't have to every time change the CID when you decide to run other RUU.
EDIT :
I just remember something .. there is a RUU zip for Taiwan HTC__621 that you can use (but you need to put back the CID to HTC__621 (the original CID) or make it SuperCID 11111111
The steps are the same as I posted before. You need to use htc_fastboot.exe and follow those fastboot commands to install a RUU zip.
Or if you have a microSD card, you can rename the RUU zip to 0P6BIMG.zip and put it on your microsd. On fastboot, select hboot .. it will scan the 0P6BIMG.zip and ask whether you want to update, volume up to update. Once completed, remove this 0P6BIMG.zip from your microsd.
Later you can do all the OTA to the latest.
Download 0P6BIMG_M8_UL_K44_SENSE60_SECURITY_hTC_Asia_TW_1.54.709.4_R_Radio_1.15.2133156.UA14G_20.18n.4096.05_release_358414_signed_2_4.zip here : http://androidruu.com/?developer=M8
Well as I said above I decided to try the full GPE RUU, so I followed these instructions. I used hasoon2000's toolkit to change the CID, my MID was compatible with the GPE. I then fastboot bootloader and:
Method 1
*ADB / Fastboot*
First, make sure you have the path to adb and fastboot setup in your system environment variables
When you open a command prompt, open it in the folder the zip is in. Hold shift, Left Mouse click, open command prompt here.
1. Rename the RUU.zip to something short and easy like RUU.zip
2. adb reboot bootloader "press enter" Wait till phone reboots into fastboot
3. fastboot oem rebootRUU "press enter" Wait till the phone is in RUU mode (black screen with HTC logo)
4. fastboot flash zip RUU.zip "press enter"
*You will get the following message: FAILED (remote: 90 hboot pre-update! please flush image again immediately)
*RUU mode will reboot,
*Now run the same command again,
5. fastboot flash zip RUU.zip "press enter"
6. fastboot reboot-bootloader "press enter"
7. Select hboot, Do a factory reset in recovery. To enter the recovery menu when greeted by the Android with an exclamation, Hold Power button and click Volume UP.
8. Done, reboot system.
It took a long time for the ROM to install, but I was happy to see the Google splash screen rolling along.
Overall a bit scary as I worried about potential partition issues, but I could see the naked filesystem poking around in TWRP, and knew it wasn't a brick because I got the HTC splash screen and TWRP. I'm not totally in love with the GPE right now, as I miss the Nova launcher layout (fixable, installing now), and I can't toggle data with a homescreen widget (unfixable, now 3 clicks with dropdown...first world problems!!). Bottom line, be careful with what you wipe in TWRP! Thanks to you ckpv too!

try to root htc m8 i ahve red text on screen

when i tery root and s-off let the info and picture to explan more " sory for my english"
this all info
:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
bootloader) version: 0.5
bootloader) version-bootloader: 3.19.0.0000
bootloader) version-baseband: 1.29.214500021.12G
bootloader) version-cpld: None
bootloader) version-microp: None
bootloader) version-main:
bootloader) version-misc: PVT SHIP S-ON
bootloader) serialno: SH469WM04000
bootloader) imei: 357871051160565
bootloader) imei2: Not Support
bootloader) meid: 00000000000000
bootloader) product: m8_ul
bootloader) platform: hTCBmsm8974
bootloader) modelid: 0P6B10000
bootloader) cidnum: HTC__J15
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: 76df2b54
bootloader) hbootpreupdate: 11
bootloader) gencheckpt: 0
ll: Done!
inished. total time: 0.137s
​and the phone now like this
​on phon screnn
software status modified
m8-ul-pvt ship- s-on
hboot-3.19.0.000
radio-1.29.214500021.126
opendsp-v51.2.2.00593-m8974-f001015
os- ---------------------------nothing here
emmc-boot 2048mb
dec 17 2015,14.15.48.27717
So the info on the bootloader screen is actually in red? And the phone won't boot to OS?
What exactly did you do when trying to root. Describe, step by step, and in as much detail as possible, with file names, versions, etc. How far did you get, what worked, where did you get stuck, with specific results, error messages, etc.
OS number blank usually means you used a really old and obsolete version TWRP.
redpoint73 said:
So the info on the bootloader screen is actually in red? And the phone won't boot to OS?
What exactly did you do when trying to root. Describe, step by step, and in as much detail as possible, with file names, versions, etc. How far did you get, what worked, where did you get stuck, with specific results, error messages, etc.
OS number blank usually means you used a really old and obsolete version TWRP.
Click to expand...
Click to collapse
thanks for replay
i am not sure what exactly happend i receved th phone like as say befor
but once power on the phone appear red text on down screen and stop
i am enter the recover
1- s-off
2- twrp is installed
3- i use androiad one toolkit and relock again s-on
4- wipe phone
5- now cannot enter recovery again
6- can enter fastboot
7= itry to flash the phone by ruu more an version but all trying is Failed
The steps you posted cleared up the issue, quite a bit. However, I have some additional questions about these steps, below in red font:
amira77 said:
but once power on the phone appear red text on down screen and stop
i am enter the recover
1- s-off how exactly did you try to s-off?
2- twrp is installed Did you also try to root at this point? Did you get stuck (no OS)?
3- i use androiad one toolkit and relock again s-on Why did you relock the bootloader?
4- wipe phone
5- now cannot enter recovery again
6- can enter fastboot
7= itry to flash the phone by ruu more an version but all trying is Failed You phone will only run one RUU that matches your CID/MID, you can't just run any one you want.
Click to expand...
Click to collapse
Being stuck in fastboot is an expected result of relocking the bootloader, as it expects RUU to be run.
Additionally, you should stop using the toolkit. It hasn't been updated for over 2 years, and therefore contains files (TWRP and SuperSU) which are horribly obsolete, and will cause multiple problems. The OS number being blank is one known issue with old versions TWRP (old versions TWRP are also not compatible with your phone's current firmware).
The toolkit doesn't accomplish anything, that can't be done with simple fastboot commands. And if you can't handle fastboot commands, you should not be trying to modify the phone, in the first place.
redpoint73 said:
The steps you posted cleared up the issue, quite a bit. However, I have some additional questions about these steps, below in red font:
Being stuck in fastboot is an expected result of relocking the bootloader, as it expects RUU to be run.
Additionally, you should stop using the toolkit. It hasn't been updated for over 2 years, and therefore contains files (TWRP and SuperSU) which are horribly obsolete, and will cause multiple problems. The OS number being blank is one known issue with old versions TWRP (old versions TWRP are also not compatible with your phone's current firmware).
The toolkit doesn't accomplish anything, that can't be done with simple fastboot commands. And if you can't handle fastboot commands, you should not be trying to modify the phone, in the first place.
Click to expand...
Click to collapse
okay thanks for replay again
can help me by send ruu compatible with this phone?
iwas use this ruu befor
1- RUU_M8_[email protected]41216A_40.34.C35006.02_F_release_407726_signed_2.exe
2-GQbYQWPsDSOxW4-6y5SiHg/1499132695/24369303960687057/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
The first stopped at 3%
And the second did not accept the phone
write on the back of phone 0P6B100
amira77 said:
okay thanks for replay again
can help me by send ruu compatible with this phone?
iwas use this ruu befor
1- RUU_M8_[email protected]41216A_40.34.C35006.02_F_release_407726_signed_2.exe
2-GQbYQWPsDSOxW4-6y5SiHg/1499132695/24369303960687057/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
The first stopped at 3%
And the second did not accept the phone
write on the back of phone 0P6B100
Click to expand...
Click to collapse
The 1st RUU you listed won't work. It's for the AT&T version M8.
The 2nd one should work, but I don't know what you mean when you say it did not accept the phone. What exactly happened, and what was the error message? It needs to be flashed in fastboot-RUU mode, and with HTC fastboot drivers. What commands did you use to flash it? Cut and paste the command prompt inputs and outputs.
Also, I asked a number of questions in my last post in red font which you either ignored or missed. Please answer them, as it would help me understand what you did, and why.

Categories

Resources