WI-FI won't work after flashing custom ROM - One (M8) Q&A, Help & Troubleshooting

Dear all,
After I flashed my HTC One M8 with a custom ROM (btw I did everything by the book according to Hasoon's All in one kit.) WI-FI doesn't work, it won't turn on.
Recovery: It was TWRP at first, but then I tried clockworkmod as well, after several flashing with other custom ROMs it still won't turn on.
Can you help me find out what the problem is?
Note: After several flashing attemps, although it was rooted at first, my phone somehow got unrooted.

Your firmware is outdated.
You need a 4.xx.xxx.x or 6.xx.xxx.x firmware to have a working wifi.
Check your bootloader, you should see the OS- no. there. If it is blank because you used an outdated recovery, see the hboot version .. must have 3.19.0000

I checked and this is what I have found:
***Tampered***
***Unlocked***
S-On
Hboot : 3.16.0.0000
OS - this area is blank
But I also checked my firmware number it starts with 6.xxxxxx

6.xx.xxx.x is not your firmware no. That's software version no. that you installed.
Your firmware no. is 1.xx.xxx.x which is removed by the outdated toolkit that you used.
Post fastboot getvar all result without serial & imei no. then we'll see what you need to do.
Basically, restore a non-rooted backup then do OTA to update firmware. Or run a RUU if there is one available.

ckpv5 said:
6.xx.xxx.x is not your firmware no. That's software version no. that you installed.
Your firmware no. is 1.xx.xxx.x which is removed by the outdated toolkit that you used.
Post fastboot getvar all result without serial & imei no. then we'll see what you need to do.
Basically, restore a non-rooted backup then do OTA to update firmware. Or run a RUU if there is one available.
Click to expand...
Click to collapse
Getvar results
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.153s
I added the getvar all results. Unfortunately I don't have the non-rooted backup :/
And I'm sorry I'm new to this all. What exactly is sn OTA or RUU and how do I do it?

ongunpitir said:
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) product: m8_ul_ca
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
Click to expand...
Click to collapse
Yours is an AT&T device. Your current firmware most probably is 1.12.502.18 or the most is 1.58.502.1 and this firmware is too low to run current custom ROM.
The only way you can update the firmware is using the RUU. And the latest RUU that available is 4.28.502.2
What you need :
1. The updated USB drivers - see this : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
2. 4.28.502.2 RUU that you can download here : http://www.htc.com/us/support/htc-one-m8-att/news/
3. Windows PC with USB2.0
How-to :
1. First make copy/backup of your important files like musics, photos & etc from the internal storage to PC
2. Relock the bootloader - put your device on fastboot mode and connect to PC then run this command from your fastboot/adb folder
fastboot oem lock
fastboot reboot-bootloader
3. Right click the RUU that you downloaded and select run as administrator then follow all the instructions .. accept, next, next, update, blablabla until it complete.
4. Reboot your device, you should be on the latest firmware.
5. unlock the bootloader again with the unlock_code.bin, accept and reboot
6. now you can install TWRP but use only the latest TWRP version.
7. now you can install custom ROM, your wifi should work.

ckpv5 said:
Yours is an AT&T device. Your current firmware most probably is 1.12.502.18 or the most is 1.58.502.1 and this firmware is too low to run current custom ROM.
The only way you can update the firmware is using the RUU. And the latest RUU that available is 4.28.502.2
What you need :
1. The updated USB drivers - see this : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
2. 4.28.502.2 RUU that you can download here : http://www.htc.com/us/support/htc-one-m8-att/news/
3. Windows PC with USB2.0
How-to :
1. First make copy/backup of your important files like musics, photos & etc from the internal storage to PC
2. Relock the bootloader - put your device on fastboot mode and connect to PC then run this command from your fastboot/adb folder
fastboot oem lock
fastboot reboot-bootloader
3. Right click the RUU that you downloaded and select run as administrator then follow all the instructions .. accept, next, next, update, blablabla until it complete.
4. Reboot your device, you should be on the latest firmware.
5. unlock the bootloader again with the unlock_code.bin, accept and reboot
6. now you can install TWRP but use only the latest TWRP version.
7. now you can install custom ROM, your wifi should work.
Click to expand...
Click to collapse
Hey. I've downloaded the RUU.exe on HTC website, but after I accept the terms of agreement, the wizard closes itself and nothing happens. I don't know whats going on!!
Could someone test if its about the file or something else?

kiuqxy said:
Hey. I've downloaded the RUU.exe on HTC website, but after I accept the terms of agreement, the wizard closes itself and nothing happens. I don't know whats going on!!
Could someone test if its about the file or something else?
Click to expand...
Click to collapse
This is usually due to your PC's configuration. Win7 and USB 2.0 for the best chance of compatibility.

I also tried to run RUU and encountered some problems at first. At first it happened exactly like what happened to you but then I noticed it wasn't working because I didn't have enough space (it requires to have something like 35 gb space on drive C), on which my operating system was installed. After cleaning enough space, it worked for me only to see another "unexpected error". After then I tried a few more times but still it was no go. I will try new RUUs then tell what happens. In the meanwhile if any you guys have any other ideas I would appreciate. By the way thank you ckpv5 for all your help.

ongunpitir said:
I also tried to run RUU and encountered some problems at first. At first it happened exactly like what happened to you but then I noticed it wasn't working because I didn't have enough space (it requires to have something like 35 gb space on drive C), on which my operating system was installed. After cleaning enough space, it worked for me only to see another "unexpected error". After then I tried a few more times but still it was no go. I will try new RUUs then tell what happens. In the meanwhile if any you guys have any other ideas I would appreciate. By the way thank you ckpv5 for all your help.
Click to expand...
Click to collapse
You don't really need 35 GB space on Drive C, my PC is only has about 3GB free space on Drive C (with the size of only 18 GB - the original SSD that come with the PC for hibernation purpose but I use it to install Windows so I get faster performance .. hehe..). What you need is the microsoft Visual C++ files installed and those needed come with the HTC Sync Manager (that's no.1 on what you need)
Here is another way :
Open your windows "run" .. on windows 10 is right click the start menu and select "run" then type %temp% to open windows temp folder .. delete all that you can and close the folder.
Run the RUU, let it open and no need to accept agreement .. just let it open
Again open "run" and type %temp% - in temp folder you'll see 2 newly created folder. In one of the folder, copy out the rom.zip and htc_fastboot.exe to your adb/fastboot folder ... after copy done, you can close the temp folder and the RUU.
option 1 :
Put the device on bootloader/fastboot mode and connect to PC
Open a command prompt from your adb/fastboot folder
run these commands
fastboot oem rebootRUU
htc_fastboot flash zip rom.zip
this should install the new RUU to your device.
option 2 :
You need a microSD
Rename the rom.zip to 0P6BIMG.zip and put this 0P6BIMG.zip on root of your microSD (not in any folder)
Boot to bootloader then select hboot ... it will scan the zip and ask you whether you want to update. Volume up to update. Once done .. reboot .. once you run setup and successfully update, delete the 0P6BIMG.zip from microSD.

ckpv5 said:
You don't really need 35 GB space on Drive C, my PC is only has about 3GB free space on Drive C (with the size of only 18 GB - the original SSD that come with the PC for hibernation purpose but I use it to install Windows so I get faster performance .. hehe..). What you need is the microsoft Visual C++ files installed and those needed come with the HTC Sync Manager (that's no.1 on what you need)
Here is another way :
Open your windows "run" .. on windows 10 is right click the start menu and select "run" then type %temp% to open windows temp folder .. delete all that you can and close the folder.
Run the RUU, let it open and no need to accept agreement .. just let it open
Again open "run" and type %temp% - in temp folder you'll see 2 newly created folder. In one of the folder, copy out the rom.zip and htc_fastboot.exe to your adb/fastboot folder ... after copy done, you can close the temp folder and the RUU.
option 1 :
Put the device on bootloader/fastboot mode and connect to PC
Open a command prompt from your adb/fastboot folder
run these commands
fastboot oem rebootRUU
htc_fastboot flash zip rom.zip
this should install the new RUU to your device.
option 2 :
You need a microSD
Rename the rom.zip to 0P6BIMG.zip and put this 0P6BIMG.zip on root of your microSD (not in any folder)
Boot to bootloader then select hboot ... it will scan the zip and ask you whether you want to update. Volume up to update. Once done .. reboot .. once you run setup and successfully update, delete the 0P6BIMG.zip from microSD.
Click to expand...
Click to collapse
I tried what you said this is what gives me;
C:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.016s]
finished. total time: 0.017s
C:\adb>htc_fastboot flash zip rom.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 4.28.502.2
found large-zip header, file count: 6
processing file 1/6...
sending 'zip' (57600 KB)...
OKAY [ 2.748s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
Process Process-1:
Traceback (most recent call last):
File "C:\Python34\lib\multiprocessing\process.py", line 254, in _bootstrap
File "C:\Python34\lib\multiprocessing\process.py", line 93, in run
File "E:\largezip\htc_fastboot\htc_flashzip.py", line 207, in _do_extract
File "E:\largezip\htc_fastboot\largezip.py", line 61, in extract
MemoryError
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 16.911s
htc_fastboot finished. total time: 18.191s
C:\adb>

BTW, i wouldnt rely on toolkits either to flash the M8, should always be done manually either thru recovery methods, RUU or Fastboot, i never use any of the avail toolkits to flash anything.

ongunpitir said:
I tried what you said this is what gives me;
FAILED (remote: 99 unknown fail)
Click to expand...
Click to collapse
Did you relock the bootloader as what I said here - http://forum.xda-developers.com/showpost.php?p=66159005&postcount=6
You need to relock bootloader first before you attempt option 1 or 2 or 3.
Have you tried the other option that I mentioned here - http://forum.xda-developers.com/showpost.php?p=66220239&postcount=10
Rename the rom.zip to 0P6BIMG.zip and put this 0P6BIMG.zip on root of your microSD then follow the rest ?
I tested the RUU myself ... no problem for me ...
I'm on Windows 10 64-bit USB 2.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When all the 3 options that I suggested don't work for you .. I have no other idea except maybe use a nandroid backup to restore and install the stock recovery then do multiple OTAs up to the latest (but you only can do this if you're on AT&T network)

ckpv5 said:
Did you relock the bootloader as what I said here - http://forum.xda-developers.com/showpost.php?p=66159005&postcount=6
You need to relock bootloader first before you attempt option 1 or 2 or 3.
Have you tried the other option that I mentioned here - http://forum.xda-developers.com/showpost.php?p=66220239&postcount=10
Rename the rom.zip to 0P6BIMG.zip and put this 0P6BIMG.zip on root of your microSD then follow the rest ?
I tested the RUU myself ... no problem for me ...
I'm on Windows 10 64-bit USB 2.0
View attachment 3711349
When all the 3 options that I suggested don't work for you .. I have no other idea except maybe use a nandroid backup to restore and install the stock recovery then do multiple OTAs up to the latest (but you only can do this if you're on AT&T network)
Click to expand...
Click to collapse
Thank you so much! After many failures, I have finally managed to make it work. After relocking my device and flashing with a RUU using command prompt option, it finally worked. Now I can use my wifi again. Now I will try to flash a custom ROM, but you said I need to update my firmware right? So how do I do that? Or have I just updated it already by flashing the latest RUU?
Thanks in advance

The RUU already updated your firmware to the latest ... but still a Lollipop as there is no Marshmallow update for AT&T yet but that should be enough for now, your wifi should work on any custom ROM.

Related

Help!! destroyed my HTC one M8

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)

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)

unroot HTC One M8 on EE (UK) network. Mac user.

I feel like I have been searching the internet for up to numerous years trying to find a solution. I only rooted my phone for some silly Snapchat hack that doesn't even exist any more. I would like to be able to update Android in the normal way. I would like to unroot my phone and start off again with the stock OS, if possible. Can someone lead me in the right direction? I would appreciate it immensely. Thank you. x
First thing - post fastboot getvar all result without serial & imei no.
then we'll see what you need
I don't know what that is but I shall figure it out and get back to you. Thank you
OK, that went easier than I imagined. Here is the information you requested.
(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-ON
(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
jonesyb said:
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-main: 4.16.401.10
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) security: on
Click to expand...
Click to collapse
There are 3 options for you :
1. Use a TWRP nandroid to return to non-rooted stock then do OTA up to the latest Marshmallow 6.12.401.4
Note : there is no need to relock bootloader
What you need :
1. Install TWRP 2.8.7.0
2. Restore the non-rooted 4.16.401.10 nandroid backup
3. Install 4.16.401.10 stock recovery.img
4. Reboot then do OTA checking and install
5. You should have two OTAs : 4.16.401.10 --> 4.16.401.13 --> 6.12.401.4
6. done
All files needed and How-To - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
2. Use a 4.16.401.10 RUU zip
Note : MUST relock bootloader
Boot to fastboot/bootloader mode then run command in terminal
fastboot oem lock (maybe ./fastboot oem lock for a Mac)
What you need :
1. a MicroSD
2. Download the 4.16.401.10 RUU zip - https://www.androidfilehost.com/?fid=24052804347796512
3. Rename the file to 0P6BIMG.zip (that's a zero not "O")
4. Put the 0P6BIMG.zip on your microSD
5. Boot your device to bootloader/fastboot then select hboot, it will scan the update zip and ask whether to update - volume up to select yes
6. Let it do its stuff
7. Once completed, reboot
8. Delete the 0P6BIMG.zip on your microSD (or remove the microSD)
9. Do OTA checking and install
10. You should have two OTAs : 4.16.401.10 --> 4.16.401.13 --> 6.12.401.4
11. done
3. Use 6.12.401.4 RUU zip
Note : MUST relock bootloader
Boot to fastboot/bootloader mode then run command in terminal
fastboot oem lock (maybe ./fastboot oem lock for a Mac)
What you need :
1. a MicroSD
2. Download the 6.12.401.4 RUU zip - https://www.androidfilehost.com/?fid=24369303960687057
3. Rename the file to 0P6BIMG.zip (that's a zero not "O")
4. Put the 0P6BIMG.zip on your microSD
5. Boot your device to bootloader/fastboot then select hboot, it will scan the update zip and ask whether to update - volume up to select yes
6. Let it do its stuff
7. Once completed, reboot
8. Delete the 0P6BIMG.zip on your microSD (or remove the microSD)
9. done
Personally, I suggest option 1 - no need to relock bootloader and no internal storage data wiped out.
For option 2 & 3 - You need to backup all important files like photos. musics & etc first as these procedure will wipe everything on Internal storage.
ckpv5 said:
There are 3 options for you :
1. Use a TWRP nandroid to return to non-rooted stock then do OTA up to the latest Marshmallow 6.12.401.4
Note : there is no need to relock bootloader
What you need :
1. Install TWRP 2.8.7.0
2. Restore the non-rooted 4.16.401.10 nandroid backup
3. Install 4.16.401.10 stock recovery.img
4. Reboot then do OTA checking and install
5. You should have two OTAs : 4.16.401.10 --> 4.16.401.13 --> 6.12.401.4
6. done
All files needed and How-To - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
2. Use a 4.16.401.10 RUU zip
Note : MUST relock bootloader
Boot to fastboot/bootloader mode then run command in terminal
fastboot oem lock (maybe ./fastboot oem lock for a Mac)
What you need :
1. a MicroSD
2. Download the 4.16.401.10 RUU zip - https://www.androidfilehost.com/?fid=24052804347796512
3. Rename the file to 0P6BIMG.zip (that's a zero not "O")
4. Put the 0P6BIMG.zip on your microSD
5. Boot your device to bootloader/fastboot then select hboot, it will scan the update zip and ask whether to update - volume up to select yes
6. Let it do its stuff
7. Once completed, reboot
8. Delete the 0P6BIMG.zip on your microSD (or remove the microSD)
9. Do OTA checking and install
10. You should have two OTAs : 4.16.401.10 --> 4.16.401.13 --> 6.12.401.4
11. done
3. Use 6.12.401.4 RUU zip
Note : MUST relock bootloader
Boot to fastboot/bootloader mode then run command in terminal
fastboot oem lock (maybe ./fastboot oem lock for a Mac)
What you need :
1. a MicroSD
2. Download the 6.12.401.4 RUU zip - https://www.androidfilehost.com/?fid=24369303960687057
3. Rename the file to 0P6BIMG.zip (that's a zero not "O")
4. Put the 0P6BIMG.zip on your microSD
5. Boot your device to bootloader/fastboot then select hboot, it will scan the update zip and ask whether to update - volume up to select yes
6. Let it do its stuff
7. Once completed, reboot
8. Delete the 0P6BIMG.zip on your microSD (or remove the microSD)
9. done
Personally, I suggest option 1 - no need to relock bootloader and no internal storage data wiped out.
For option 2 & 3 - You need to backup all important files like photos. musics & etc first as these procedure will wipe everything on Internal storage.
Click to expand...
Click to collapse
Thank you so much for this.
There are some things worth noting before I go ahead with this. I tried to unroot my phone by using the option within SuperSU, and I have deleted xposed. Will this affect anything above?
jonesyb said:
Thank you so much for this.
There are some things worth noting before I go ahead with this. I tried to unroot my phone by using the option within SuperSU, and I have deleted xposed. Will this affect anything above?
Click to expand...
Click to collapse
Doesn't matter what you have on your system now .. the above procedure will replace your system .. you'll get a device as you first bought it.
I am up to this part "3. Install 4.16.401.10 stock recovery.img"
Then this happened:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am slightly confused. Where does the .img file go? There is no path to it in the fastboot command.
So I say you follow the option 1 and you already settled the step 1 & 2
Install TWRP & restore the backup ?
To install 4.16.401.10_recovery.img is the same as you installed the TWRP 2.8.7.0
When you give command fastboot flash recovery 4.16.401.10_recovery.img, you give command to install 4.16.401.10_recovery.img to recovery partition.
I don't know much about MAC .. maybe you need to shorten the name 4.16.401.10_recovery.img to recovery.img only and try again.
How did you install TWRP ?
ckpv5 said:
So I say you follow the option 1 and you already settled the step 1 & 2
Install TWRP & restore the backup ?
To install 4.16.401.10_recovery.img is the same as you installed the TWRP 2.8.7.0
When you give command fastboot flash recovery 4.16.401.10_recovery.img, you give command to install 4.16.401.10_recovery.img to recovery partition.
I don't know much about MAC .. maybe you need to shorten the name 4.16.401.10_recovery.img to recovery.img only and try again.
How did you install TWRP ?
Click to expand...
Click to collapse
Hey, apologies for the really late reply. I am going to give this another try and see what happens.
I think this time I am going to try option 3, as it looks easier and I don't care about losing all the files on my phone. Everything is backed up and I don't mind spending a bit of time getting the phone back to how I like it.
"Note : MUST relock bootloader
Boot to fastboot/bootloader mode then run command in terminal
fastboot oem lock (maybe ./fastboot oem lock for a Mac)"
OK so to run this, would I have to change the path of the command to whatever folder the fastboot "unix executable" file is in? I am massively confused by how this works
I put the card in the phone, booted in fastboot/bootloader mode and got the following message on the screen:
"device halted due to large image update fail"
Everything is backed up, I have all the files I need and I am ready to go.
Note : MUST relock bootloader
Boot to fastboot/bootloader mode then run command in terminal
fastboot oem lock (maybe ./fastboot oem lock for a Mac)
What you need :
1. a MicroSD
2. Download the 6.12.401.4 RUU zip - https://www.androidfilehost.com/?fid=24369303960687057
3. Rename the file to 0P6BIMG.zip (that's a zero not "O")
4. Put the 0P6BIMG.zip on your microSD
5. Boot your device to bootloader/fastboot then select hboot, it will scan the update zip and ask whether to update - volume up to select yes
6. Let it do its stuff
7. Once completed, reboot
8. Delete the 0P6BIMG.zip on your microSD (or remove the microSD)
9. done
Click to expand...
Click to collapse
The reclocking bootloader part is not part of the numbered list. Do I do this first? I am mildly confused about the process. Thank you
Right. Progress. Is this right?
I don't want to move on to part 1 of the process unless it is.
jonesyb said:
I put the card in the phone, booted in fastboot/bootloader mode and got the following message on the screen:
"device halted due to large image update fail"
Everything is backed up, I have all the files I need and I am ready to go.
The reclocking bootloader part is not part of the numbered list. Do I do this first? I am mildly confused about the process. Thank you
Click to expand...
Click to collapse
It clearly says so right ? Don't think too far, it's written prior to the steps so it's necessary to do that before the steps
Mr Hofs said:
It clearly says so right ? Don't think too far, it's written prior to the steps so it's necessary to do that before the steps
Click to expand...
Click to collapse
Thank you very much. I think I have got it. Going on to the next step. Again, thank you.
Hey everyone who helped me. I just want to say thank you for your advice. I have (eventually) followed through with it all to the letter and my phone is up to date with the root access removed. Thank you

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