Help!! destroyed my HTC one M8 - One (M8) Q&A, Help & Troubleshooting

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)

Related

[Q] HTC One M8 won't boot.

Some one please help me.
I have the HTC One M8 which I updated to Android 5.0.1 through OTA updates about 2 weeks ago.
Yesterday, I successfully unlocked the bootloader and rooted my device. I also have the TWRP Recovery v.2.7.0.2 installed.
Everything was working fine until after the root when I noticed that the internal storage had some kind of write protection on it. Like even the default "DCIM , ANDROID, Downloads etc... folders weren't there". I discovered the write protection on the internal storage when I tried to download a file using Chrome on the phone and it replied with "No SD Card".
Funny thing is apps from the Play Store were installing perfectly fine.
So I booted back into TWRP recovery and did a factory reset thinking I must've messed up while rooting.
After the factory reset when I try boot up my phone the Setup Wizard constantly crashes so I can't do anything.
My HTC One M8 is the international variant Model: 0P6B100.
Someone please help
1. Install the latest TWRP 2.8.5.0 or 2.8.4.0 (2.7.0.2 is damn too old and buggy)
2. In TWRP select Wipe - Format Data (you will lose all files in internal storage)
3. Reboot - you should be able to run the setup wizard
ckpv5 said:
1. Install the latest TWRP 2.8.5.0 or 2.8.4.0 (2.7.0.2 is damn too old and buggy)
2. In TWRP select Wipe - Format Data (you will lose all files in internal storage)
3. Reboot - you should be able to run the setup wizard
Click to expand...
Click to collapse
I installed TWRP 2.7.0.2 using All in one tool v2.0 by Hasoon2000. The tool needs usb debugging to be turned on which I can't turn on because I can't get past the setup wizard because it keeps crashing.
Is there a way to install it manualy using fastboot?
I thought so ... when I see TWRP 2.7.0.2 I can guess you use some outdated Toolkit.
Press & hold Volume up and power button until the screen turn off then quickly release both buttons and press & hold volume down button. This should get you to hboot. Press power once to go to bootloader.
If you don't have a proper ADB & fastboot installed, download Minimal ADB and Fastboot and install : http://forum.xda-developers.com/showthread.php?t=2317790
Download latest TWRP : http://techerrata.com/browse/twrp2/m8
Connect to PC and open a command prompt and run command fastboot devices and see any connection with PC, it will give your device serial no. if it does.
If yes, flash the TWRP : fastboot flash recovery NameofTWRP.img then do the above that I mentioned
ckpv5 said:
I thought so ... when I see TWRP 2.7.0.2 I can guess you use some outdated Toolkit.
Press & hold Volume up and power button until the screen turn off then quickly release both buttons and press & hold volume down button. This should get you to hboot. Press power once to go to bootloader.
If you don't have a proper ADB & fastboot installed, download Minimal ADB and Fastboot and install : http://forum.xda-developers.com/showthread.php?t=2317790
Download latest TWRP : http://techerrata.com/browse/twrp2/m8
Connect to PC and open a command prompt and run command fastboot devices and see any connection with PC, it will give your device serial no. if it does.
If yes, flash the TWRP : fastboot flash recovery NameofTWRP.img then do the above that I mentioned
Click to expand...
Click to collapse
Okay I got my serial number. Now what do I do with it?
bolajiibrahim7 said:
Okay I got my serial number. Now what do I do with it?
Click to expand...
Click to collapse
If you don't feel like installing the latest TWRP as I said above ... then -> hboot -> recovery -> wipe -> format data -> type yes -> reboot
I wrote almost everything there, but read only the last paragraph ??
Read again all of my posts here.
ckpv5 said:
If you don't feel like installing the latest TWRP as I said above ... then -> hboot -> recovery -> wipe -> format data -> type yes -> reboot
I wrote almost everything there, but read only the last paragraph ??
Read again all of my posts here.
Click to expand...
Click to collapse
I did that. Then it started the "Android is upgrading - Optimizing apps splash.
After that I'm back to the Setup Wizard which keeps crashing.
Then the only choice is to restore a stock backup or RUU.
What's your software version ?
Better post result of fastboot getvar all (minus the serial no. & imei no.)
ckpv5 said:
Then the only choice is to restore a stock backup or RUU.
What's your software version ?
Better post result of fastboot getvar all (minus the serial no. & imei no.)
Click to expand...
Click to collapse
My software version is 5.0.1 Lollipop.
I don't have a stock backup. RUU is my only option.
Here's my fastboot getvar all
C:\adb>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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ***************
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.125s
C:\adb>
I do have backup for your device version here : http://forum.xda-developers.com/showpost.php?p=58499803&postcount=4076
but there is also RUU for your device.
Just follow @EddyOS thread discussion : http://forum.xda-developers.com/showthread.php?t=2735235
ckpv5 said:
I do have backup for your device version here : http://forum.xda-developers.com/showpost.php?p=58499803&postcount=4076
but there is also RUU for your device.
Just follow @EddyOS thread discussion : http://forum.xda-developers.com/showthread.php?t=2735235
Click to expand...
Click to collapse
Also for some reason. I don't have S-off. But I managed to unlock and bootloader and root.
bolajiibrahim7 said:
Also for some reason. I don't have S-off. But I managed to unlock and bootloader and root.
Click to expand...
Click to collapse
You don't need S-Off to run RUU, relocked bootloader before run RUU. Read thru that thread, there are many discussion.
Read this, this guy also doesn't have S-Off device : http://forum.xda-developers.com/htc-one-m8/help/one-m8-htc001-cid-firmware-wifi-problem-t3031656 and he managed that.
Or just restore backup that linked to you if you don't feel to relock bootloader.
You need to read all those thread. Without reading, this is going no where .. good luck
ckpv5 said:
I do have backup for your device version here : http://forum.xda-developers.com/showpost.php?p=58499803&postcount=4076
but there is also RUU for your device.
Just follow @EddyOS thread discussion : http://forum.xda-developers.com/showthread.php?t=2735235
Click to expand...
Click to collapse
What does RUU mean? and how do I use it?
Also does applying RUU restore my phone to the way it was before root as in With Android 5.0.1 and Sense 6.0?
RUU is ROM Update Utility released by HTC.
Read the thread on how to use it. Basic is put your device on bootloader/fastboot mode and relock your bootloader with command fastboot oem lock.
Then run the RUU exe in Administrator mode (select run as Administrator) from your Windows explorer.
This will wipe everything on your device and replace with new stock ROM with no root.
That RUU is lollipop 5.0.1 and Sense 6.0
Read the thread.. you will understand what it does. Good night.
ckpv5 said:
RUU is ROM Update Utility released by HTC.
Read the thread on how to use it. Basic is put your device on bootloader/fastboot mode and relock your bootloader with command fastboot oem lock.
Then run the RUU exe in Administrator mode (select run as Administrator) from your Windows explorer.
This will wipe everything on your device and replace with new stock ROM with no root.
That RUU is lollipop 5.0.1 and Sense 6.0
Read the thread.. you will understand what it does. Good night.
Click to expand...
Click to collapse
I did everything as outlined and I ended up with:
C:\Download\HTC One M8 Toolkit 2.0.2.1\adb>fastboot flash zip ruu.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1536838 KB)...
OKAY [ 42.728s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 98.981s
bolajiibrahim7 said:
I did everything as outlined and I ended up with:
C:\Download\HTC One M8 Toolkit 2.0.2.1\adb>fastboot flash zip ruu.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1536838 KB)...
OKAY [ 42.728s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 98.981s
Click to expand...
Click to collapse
Did you do fastboot oem rebootRUU before fastboot flash zip ruu.zip ?
Let's do a different way, the simplest one.
1. Re-unlock your bootloader
2. Make sure you have TWRP 2.8.4.0 or 2.8.5.0 installed (I mentioned many times about this version, right ?)
3. Download a flashable stock ROM One_M8_4.16.401.10_stock_system_dump.zip from : http://forum.xda-developers.com/showthread.php?t=2694994
4. Boot to recovery and connect to PC, In TWRP recovery select Mount and enable MTP, you should be able to open internal storage or MicroSD on your PC
5. Transfer the downloaded One_M8_4.16.401.10_stock_system_dump.zip to Internal Storage or MicroSD
6. In recovery, select Install and select One_M8_4.16.401.10_stock_system_dump.zip then swipe to install
7. Reboot
Thank You.
ckpv5 said:
Did you do fastboot oem rebootRUU before fastboot flash zip ruu.zip ?
Let's do a different way, the simplest one.
1. Re-unlock your bootloader
2. Make sure you have TWRP 2.8.4.0 or 2.8.5.0 installed (I mentioned many times about this version, right ?)
3. Download a flashable stock ROM One_M8_4.16.401.10_stock_system_dump.zip from : http://forum.xda-developers.com/showthread.php?t=2694994
4. Boot to recovery and connect to PC, In TWRP recovery select Mount and enable MTP, you should be able to open internal storage or MicroSD on your PC
5. Transfer the downloaded One_M8_4.16.401.10_stock_system_dump.zip to Internal Storage or MicroSD
6. In recovery, select Install and select One_M8_4.16.401.10_stock_system_dump.zip then swipe to install
7. Reboot
Click to expand...
Click to collapse
Thank you so much for your help. My phone is now on Lollipop and rooted and working fine.
Kinda in the same problem...
Hi ckpv5, I wonder if you can help me...having the same problems...but I need some guidance.
I'll try to give you all the info:
fastboot getvar all:
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.16.21331931.LA11G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT43TWM0xxxx
meid: 00000000000000
product: m8_ul_ca
platform: hTCBmsm8974
modelid: 0P6B12000
cidnum: CWS__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: c3d94491
hbootpreupdate: 11
gencheckpt: 0
TWRP 2.7.0.1 - I know it's old and buggy but flashing a newer one, even though it flashes ok, it wont load.
The phone is Tampered - Unlocked with S-On
After unlocking and flashing TWRP, I flashed custom ROM MaximusHD, it worked but as I didnt that it needed newer firmware, wifi wasnt working, tried to restart the phone and it entered in a boot loop.
Then flashed: http://forum.xda-developers.com/showthread.php?t=2699186
But it wont boot...
Could you please help me?
Thanks in advance
macdo said:
Hi ckpv5, I wonder if you can help me...having the same problems...but I need some guidance.
I'll try to give you all the info:
fastboot getvar all:
version-bootloader: 3.16.0.0000
product: m8_ul_ca
modelid: 0P6B12000
cidnum: CWS__001
Click to expand...
Click to collapse
You have a AT&T device.
Just relocked bootloader - fastboot oem lock
Then run RUU (select run as administrator in Windows context menu) : http://dl3.htc.com/application/RUU_...40.34.C35006.02_F_release_407726_signed_2.exe
This will update your device with stock 3.42.502.1 (4.4.4)
Thanks for the fast answer, I'll it and report back!
---------- Post added at 02:20 PM ---------- Previous post was at 02:16 PM ----------
ckpv5 said:
You have a AT&T device.
Just relocked bootloader - fastboot oem lock
Then run RUU (select run as administrator in Windows context menu) : http://dl3.htc.com/application/RUU_...40.34.C35006.02_F_release_407726_signed_2.exe
This will update your device with stock 3.42.502.1 (4.4.4)
Click to expand...
Click to collapse
After fastboot oem lock, I got this:
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.139s
And rebooted to bootloader now, it says:
Tampered
Relocked
Security Warning
Is it ok? (btw, im downloading ruu)
Thank you so much!

Can't Flash TWRP Recovery

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)

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!

HTC M8 stuck in fastboot only showing RUU

Ok this is what happened.
I had the rom Android Revolution installed on my HTC M8.
Today I installed the new ROM Revolution, Android 6.0, but when I could not turn on wifi.
After searching in google found that its a MUST to update your firmware, which I have subsequently done true the PC with mini-sdk. That did not work, and now I'm stuck in fastboot. He won't let me into recovery anymore, if i chose it, he trows me back to fastboot menu
SCREEN IN FASTBOOT:
Tampered *** ***
*** *** Relocked
M8_UL PVT SHIP S-ON
HBOOT-318.0.0000
RADIO 1.19.21331147A1.09G
OpenDSP-v38.2.2-00542-M8974.0311
OS 2.22.161.6
eMMC boat 2048MB
RUU
anyone have a solution?
Do i have to update firmware now, really don't now wich steps i should take right now.
Thanks for the effort
C:\mini-sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.161.6
(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: VODAPE17
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
C:\mini-sdk>
Mcdrug said:
After searching in google found that its a MUST to update your firmware, which I have subsequently done true the PC with mini-sdk. That did not work, and now I'm stuck in fastboot.
Click to expand...
Click to collapse
What exactly did you try to flash (full file name) and where did you get it from?
Any error messages when you tried to flash the firmware, or other outputs?
redpoint73 said:
What exactly did you try to flash (full file name) and where did you get it from?
Any error messages when you tried to flash the firmware, or other outputs?
Click to expand...
Click to collapse
download
M8_6.12.401.4_WWE_TWRP2870.zip
hboot_signedbyaa.img
pg2fs_spcustom.img
radio.img
rcdata.img
rpm.img
sbl1-8974AA-1.img
sbl1-8974AB-1.img
sbl1-8974AB-2.img
sdi.img
sensor_hub.img
splash1.nb0
tp_SYN3508.img
tp_SYN3528.img
tz.img
wcnss.img
adsp.img
android-info.txt
error message:
i thought it was something like (FAILED (remote: 12 signature verify fail). maybe have to do it again to make sure what error message i got?
Mcdrug said:
download
M8_6.12.401.4_WWE_TWRP2870.zip
i thought it was something like (FAILED (remote: 12 signature verify fail).
Click to expand...
Click to collapse
Yes, it would be signature verify fail. Its a hacked firmware (with stock recovery replaced with TWRP). You can't flash this with s-on. You can only flash signed firmware with s-on; and once its hacked, its no longer signed.
Additionally, its not the right version number for your CID. It would need to have "161" in the place of "401".
Your best bet is probably to return to full stock nandroid 2.22.161.6 and stock recovery 2.22.161.6, than OTA up to LP or MM. Instructions and required files here:
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
redpoint73 said:
Yes, it would be signature verify fail. Its a hacked firmware (with stock recovery replaced with TWRP). You can't flash this with s-on. You can only flash signed firmware with s-on; and once its hacked, its no longer signed.
Additionally, its not the right version number for your CID. It would need to have "161" in the place of "401".
Your best bet is probably to return to full stock nandroid 2.22.161.6 and stock recovery 2.22.161.6, than OTA up to LP or MM. Instructions and required files here:
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
He won't let me flash recovery twrp-2.8.1.0-m8.img
FAILsignature verify fail
FAILED (remote: signature verify fail)
Mcdrug said:
He won't let me flash recovery twrp-2.8.1.0-m8.img
FAILsignature verify fail
FAILED (remote: signature verify fail)
Click to expand...
Click to collapse
You need to unlock the bootloader again, in order to flash custom recovery.
Big relief i am in recovery again!
Actually back in my Android Revolution Rom , but without WIFI
Don't want to do anyting wrong again right now.
So next thing to do is folow the steps from your posted link #5?
Or do i have to do other things now?
Mcdrug said:
Big relief i am in recovery again!
Actually back in my Android Revolution Rom , but without WIFI
Don't want to do anyting wrong again right now.
So next thing to do is folow the steps from your posted link #5?
Or do i have to do other things now?
Click to expand...
Click to collapse
You have to follow all the steps through Step 14.
Again, the goal is to return to full stock nandroid 2.22.161.6 and stock recovery 2.22.161.6, than OTA up to LP or MM
Can't get true this step:
6(a). Reboot, connect device to PC then
open Internal Storage - TWRP/BACKUPS/SerialNo./ (if backup is set to internal storage)
open SD Card - TWRP/BACKUPS/SerialNo./ (if backup is set to MicroSD)
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)
If i make a backup from Boot he puts is in internal store TWRP/BACKUPS/SerialNo./ but when i copy the unzip files he stops, too big.
solution might be: Are you mounting the MTP in recovery mode ? It won't work this way.
You need to transfer them on a working OS (I mean you have to be on homescreen)
Try use an external sdcard.
I have put an external sdcard inside, i can put the files on the card
But then the files aren't located at the TWRP/BACKUP map.
What to do?
Mcdrug said:
If i make a backup from Boot he puts is in internal store TWRP/BACKUPS/SerialNo./ but when i copy the unzip files he stops, too big.
What to do?
Click to expand...
Click to collapse
when you select boot to backup, you can select which storage the backup goes to .. select microSD instead of internal (read all menu in the backup section on TWRP)
then you can use a card reader to mount your microsd to PC and transfer the extracted contents of the backup zip to the same folder that you made with the boot backup and replace all files when PC ask you.
All done, back in stock rom, thank you very much!!
10. In reboot menu select bootloader (when TWRP asks whether you want to root your device, select do not install)
I choose in this step do not install, but he rebooted me direct into the stock rom.
Tried some things to get into the bootloader again, volume down and power, cmd with adb fastboot, but nothing really worked.
What's the reason i can't get back to bootloader, and how do i get step 11 fixed and flash stock recovery?
To go to bootloader when on OS running ... press power button and select restart. When the screen turn black .. hold volume down button .. that will take you to hboot screen, press power once will get you to fastboot/bootloader
To go to bootloader when on OS running ... you need to enable USB debugging in settings - Developer options. To enable Developer options, go to settings - about - software information - more - click build number until the developer options is enabled.
Once usb debugging is enabled, you can run command adb reboot bootloader to get to fastboot/bootloader
It works, did the last step:
11. fastboot flash stock recovery that you downloaded - command fastboot flash recovery x.xxx.xx.x_recovery.img
but now can't entering recovery anymore, just showing a red trangle with an exclamation mark? And in some minutes he boots to OS.
Have to do step 1 again? Maybe go to a higher version? I want OTA to MM 6.0
You don't need to get into recovery after you installed stock recovery.
what you need to do ... boot to OS .. go to settings - about - software update - check for update, download and click install let the system do its stuff to update. After reboot, repeat the checking & install process.
And you need to do the checking & install, multiple times to update :
2.22.161.6 --> 4.19.161.2 --> 4.19.161.3 --> 6.12.161.4 --> done.

Getting back to stock for OTA update

Hello fellow XDA users!
I just bought my m8 and it came with Software status modified, bootloader unlocked, philz touch, S-on but Super CID.
The problem now is that i can't OTA and it is still in kitkat
So I started to work on it tonight, and I can't get it back to stock :
I have flashed TWRP, made a boot backup to create necessary folders, and downloaded a stock nandroid backup for my main version, 3.28.401.6.
Wiped the phone, restored the rom, flashed stock recovery and here in bootloader my software status is still modified, so no OTA possible.
Suppose it has something to do with superCID, but i can't modify it anymore as I'm not s-off and I don't know what is the stock CID for the phone, just bought it.
Sorry to create another boring thread about OTA updates btw, but I just can't understand what I'm doing wrong here (coming from a samsung device, but I've been reading a lot here, and still no luck about my situation.)
http://forum.xda-developers.com/showthread.php?t=2701376 this is the thread where I downloaded the Nandroid, if it has any importance... It is the one rooted but which has apparently no effect on OTA
http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845 this seems interesting as I could maybe flash a RUU of same version to become unmodified but i'll ask you before doing anything stupid
Thank you all for your future answers
EDIT : Here are info from getvar all if you need (removed serialno and imei)
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.401.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: 11111111
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.007s
WoBble12 said:
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: 11111111
(bootloader) security: on
Click to expand...
Click to collapse
With the above current CID/MID ... you can only update to Marshmallow either with T-MOB US RUU or Developer Edition RUU as both work on MID 0P6B13000
You current software 3.28.401.6 won't do any good as that is workable for OTA when your MID is 0P6B10000
So if you want a EU version, you need to spend USD25 to S-Off the device, else just go for Developer Edition RUU.
Step 1 : install 6.12.1540.4 firmware
You can get the firmware and how-to : http://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Step 2 : install 6.12.1540.4 RUU
Download : http://www.htc.com/us/support/htc-one-m8/news/
Ok, thank you for the quick reply!
I was mistaken by the back plate of the device saying OP6B100, so didn't verify the mid in the adb log...
Now for a few questions, what are the differences between the dev version and the European one? Anything related to getting signal or something?
If I just update fw and rom with your two links, it will work even with my software status says "modified"? And Will it change back to official status?
Are updates going to be better if I go s-off and european again or is it the exact same version?
1. I don't see any significant difference with EU and Dev Ed except the obvious radio config.
But both worked fine for me in Asia region.
2. You should get the official status.
3. I don't see a point to S-Off as there is no more further OTA offered by HTC.
Once you updated to Marshmallow, you can always unlock the bootloader and install any custom ROM that you like. Most important is to have Marshmallow firmware (or at least Lollipop), doesn't matter whether it is EU or Dev Ed.
Ok, thanks again for the replies! Will try dev software, and if it doesn't work I'll pay for s-off
Ok so... I tried to update firmware, followed the tutorial, but i'm stuck at flashing the RUU. I went to the link you sent me, downloaded the 1.4 GB file, and now I have a zip file and a .exe file. The .exe will just start, say me it installs installshield, ask me to agree with the terms of licence, and close.
So I searched a bit, and i tried to flash the RUU as I did for the firmware, but now rebooting just leads me to a black screen, and the RUU fails.
please tell me what I did wrong so I can fix it.
Here is the ADB output :
C:\adb>fastboot flash zip RUU.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1217690 KB)...
OKAY [ 34.178s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 79.165s
You can't use generic fastboot.exe to flash the RUU.zip, you need to use htc_fastboot.exe
Read this : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
but use your RUU.zip (not the one in the guide)
sorry to bother for this but what is my RUU.zip you are talking about?
And i've tried with HTC fastboot and no luck neither...
You mentioned these above
C:\adb>fastboot flash zip RUU.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1217690 KB)...
OKAY [ 34.178s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 79.165s​
So I thought that you have a RUU zip.
Since you can't run RUU.exe (due to either USB2.0 is not available or lack of HTC USB Drivers and some Microsoft files in your PC), you can do this :
Run the RUU.exe, when it opens where you can see the dialog box for you to accept agreement ..
Open your windows temp folder ( in windows run dialog, type %temp% )
You'll see two newly created folder, one of them has a file named rom.zip
Copy this rom.zip to your fastboot folder ... this is your RUU.zip
Can you post your current fastboot getvar result ? Need to see that you successfully installed the firmware.zip
ckpv5 said:
You mentioned these above
C:\adb>fastboot flash zip RUU.zip
target reported max download size of 1826418688 bytes
sending 'zip' (1217690 KB)...
OKAY [ 34.178s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 79.165s​
So I thought that you have a RUU zip.
Since you can't run RUU.exe (due to either USB2.0 is not available or lack of HTC USB Drivers and some Microsoft files in your PC), you can do this :
Run the RUU.exe, when it opens where you can see the dialog box for you to accept agreement ..
Open your windows temp folder ( in windows run dialog, type %temp% )
You'll see two newly created folder, one of them has a file named rom.zip
Copy this rom.zip to your fastboot folder ... this is your RUU.zip
Click to expand...
Click to collapse
Ok, just saw this at the moment on another thread, was going to try with the %temp% method, the command you made bold was the RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.zip file that I renamed to be able to flash it more easily lol, what a noob I am ^^ so i'm going to extract this rom.zip and flash it, hope it works now! all fastboot commands have to be replaced with "htc fastboot" now, or only the flashing one?
Once again, thank you! (Using the thanks button at each of your posts too, don't worry )
yes, I verified in bootloader it says OS-6.12.1540.4 !!! Win! now just estracting the Rom from the temp folder!
htc_fastboot only when flashing RUU.zip
Another method to install the RUU.zip once you copied out the rom.zip from Windows Temp folder.
1. rename the rom.zip to 0P6BIMG.zip
2. place it on root of your microsd (which is formatted to fat32)
3. boot to bootloader and select hboot
4. it will scan the file and ask whether you want to update
5. volume up to update and leave it to do its stuff until it is completed and ask you to reboot
6. after reboot, remove that 0P6BIMG.zip from your microsd (so it won't ask you again to update whenever you boot to bootloader/hboot)
ckpv5 said:
htc_fastboot only when flashing RUU.zip
Another method to install the RUU.zip once you copied out the rom.zip from Windows Temp folder.
1. rename the rom.zip to 0P6BIMG.zip
2. place it on root of your microsd (which is formatted to fat32)
3. boot to bootloader and select hboot
4. it will scan the file and ask whether you want to update
5. volume up to update and leave it to do its stuff until it is completed and ask you to reboot
6. after reboot, remove that 0P6BIMG.zip from your microsd (so it won't ask you again to update whenever you boot to bootloader/hboot)
Click to expand...
Click to collapse
I've done the 1st method, and now after a flash that went well, i'm stuck in bootloader, with os version bein written in red and showing two times the version number, second one in parenthesis.
Instead of having options to power down etc, I only have a orange RUU option which is selected but I can't validate with power button, and in ADB I did command to reboot to bootloader but not doing anything now...
When in RUU mode, you don't use adb .. use fastboot
fastboot reboot-bootloader
When you have OS written in red, that's usually means the firmware is not correctly installed.
Try to get to fastboot with the above command then reinstall firmware.zip
ckpv5 said:
When in RUU mode, you don't use adb .. use fastboot
fastboot reboot-bootloader
When you have OS written in red, that's usually means the firmware is not correctly installed.
Try to get to fastboot with the above command then reinstall firmware.zip
Click to expand...
Click to collapse
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 8.033s
that's what I get...
And in bootloader actually I only have the variables and the "RUU" option highlighted in orange :/
Connect to PC so you can hear the connect/disconnect sound
Press & hold both power & volume up till you hear the disconnect sound
Release both button and press & hold volume down button, this should get you to hboot
(remove the microsd first as you have the RUU zip there)
that's what I get...
And in bootloader actually I only have the variables and the "RUU" option highlighted in orange​
Can you use the power button to select it to get to RUU mode then fastboot reboot-bootloader or press & hold buttons method ?
ckpv5 said:
Connect to PC so you can hear the connect/disconnect sound
Press & hold both power & volume up till you hear the disconnect sound
Release both button and press & hold volume down button, this should get you to hboot
(remove the microsd first as you have the RUU zip there)
Click to expand...
Click to collapse
I don't have the rom on micro sd for the moment, but just disconnected and reconnected to PC, now I'm on the RUU screen with the green bar being completed but not doing anything. Should I try to re launch a command line and reflash the rom.zip?
WoBble12 said:
I don't have the rom one micro sd for the moment, but just disconnected and reconnected to PC, now I'm on the RUU screen with the green bar being completed but not doing anything. Should I try to re launch a command line and reflash the rom.zip?
Click to expand...
Click to collapse
Run command fastboot reboot-bootloader
to get to bootloader
check the OS now written in red or green
if red, reflash firmware.zip not rom/RUU.zip
if green .. just reboot and wait for awhile and see how it goes.
if it is stuck after 10 minutes .. reflash RUU/rom zip
I'm now on marshmallow! Tastes sweet lol!
Can't test the signal at the moment as I have to cut my micro SD to the right size, and I have no time for it. I will do this tomorrow , and reply back here to say if it worked. Anyway, couldn't have done this without you so big thanks for this and big thanks to all the XDA community!
WoBble12 said:
....I have to cut my micro SD to the right size....
Click to expand...
Click to collapse
Hehe .. I believe you wanted to say to cut SIM card, not microSD
Great to know you managed to update.
Yes of course, simcard ^^
So I can now say that the phone is working and I have signal through my card.
Only weird thing is that after installing a few apps, system is taking up 8+ gig's of storage, which seems really big to me. But hey, it's a 32gig's one so I'm not afraid

Categories

Resources