HI
So I have installed latest Revolution with Android 5 version. However the WIFI is not turning on. I found that ideally you also need to update firrmware and in the meantime I have S-OFFed phone using Sunshine.
I am quite confused which firmware I need to install to try to solve WIFI issue. My bootloader info is the following
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__002
(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: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Can someone point me to the correct firmware. I tried to also open web page where there are latest firmware but I was very confused the one I need to install.
You need to install 6.12.401.4 firmware.
You can find them on most custom ROMs thread but make sure to use only a full firmware because your current one is too low.
I can only guide you with a signed firmware that you can get from my thread : http://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
put your device to bootloader/fastboot mode :
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip fw_6.12.401.4.zip
you'll error
repeat again fastboot flash zip fw_6.12.401.4.zip
fastboot reboot-bootloader
reflash latest TWRP 3.0.2-0 - https://dl.twrp.me/m8/
reinstall ROM
done
ckpv5 said:
You need to install 6.12.401.4 firmware.
Click to expand...
Click to collapse
Great thanks let me try to find it then
newera said:
Great thanks let me try to find it then
Click to expand...
Click to collapse
You need to install full firmware ... see my edit above.
thanks for detailed instructions. i will be trying now to install
newera said:
thanks for detailed instructions. i will be trying now to install
Click to expand...
Click to collapse
hi so what exactly is this? TWRP 3.0.2-0 and how to install such image?
also where exactly shall i put .zip firmware on sd or on phone?
Oh man ... I don't expect that come from you with a S-Off device ...
To install TWRP : fastboot flash recovery twrp-3.0.2-0-m8.img
all these require you to have adb/fastboot installed (you should already have one, if not how did you get that fastboot getvar all result ?)
and those firmware.zip & twrp-3.0.2-0-m8.img put them in your adb/fastboot folder.
put the device on bootloader/fastboot mode, open a command prompt from your adb/fastboot folder then run those commands.
ckpv5 said:
Oh man ... I don't expect that come from you with a S-Off device ...
To install TWRP : fastboot flash recovery twrp-3.0.2-0-m8.img
all these require you to have adb/fastboot installed (you should already have one, if not how did you get that fastboot getvar all result ?)
and those firmware.zip & twrp-3.0.2-0-m8.img put them in your adb/fastboot folder.
put the device on bootloader/fastboot mode, open a command prompt from your adb/fastboot folder then run those commands.
Click to expand...
Click to collapse
Yeah sorry... I have not updated my phone for the past 2 years... so yes sorry for being a rookie in this...
I restart the mobile into fastboot and then i used mini-sdk on Windows with command prompt so that is why I could not understand where to put the zip file.
newera said:
Yeah sorry... I have not updated my phone for the past 2 years... so yes sorry for being a rookie in this...
I restart the mobile into fastboot and then i used mini-sdk on Windows with command prompt so that is why I could not understand where to put the zip file.
Click to expand...
Click to collapse
Thanks sorry I did not realize I don't need to put the file on mobile. Yeah I made a big mistake in this hehe .... i thought the command was running on mobile and not on PC. it being flashed right now.
newera said:
Yeah sorry... I have not updated my phone for the past 2 years... so yes sorry for being a rookie in this...
I restart the mobile into fastboot and then i used mini-sdk on Windows with command prompt so that is why I could not understand where to put the zip file.
Click to expand...
Click to collapse
You can try this - http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
With this adb/fastboot installer, install it as system-wide.
You can put the firmware.zip & TWRP anywhere that you like, let say your PC desktop. Then open a command prompt from desktop (after connecting device to PC on fastboot mode), type fastboot devices .. if you get serial no. then the connection is good. Now you can proceed with firmware flashing.
Related
Hello,
I am trying to fix my issue and have done a ton of reading but can't figure out where to go from here. I've had my phone rooted for months and tried to flash a newer custom ROM today and it ended up locking my phone into a boot loop. I was able to get out of it and had to re install a recovery tool (have installed both CWM and TWRP and they work fine). But I can't actually get a ROM back onto my phone because I don't have one on the SD card and I can't get one to it. I just want to put a stock ROM back onto it at this point.
I can't boot into windows to access the SD card because whenever I boot the phone normally it just goes back to boot looping. I have tried ADB push when in recovery to put a ROM on the SD card and I continually get permission denied when I try to do that. I have tried ADB sideloader and I can't get that to work either. How can I go about getting a ROM to my phone so I can flash it via CWM/TWRP?
Fastboot works fine and I can flash recoveries no problem. ADB appear to work but I can't understand why I can't just get push to work. Any help would be greatly appreciated.
HTC One M7 on Verizon.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 1.12.42.0731
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.10.605.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:xxx
(bootloader) imei: xxx
(bootloader) meid: xxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97af273845
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
If you type "adb devices" from a Command Prompt, do you see your phone listed?
Try powering off your phone, then holding Power+VolDown until you get to HBOOT. From there, enter recovery (TWRP is my preferred). ADB push does not require anything to be done prior to using it, so assuming you can see your phone with "adb devices", proceed like this:
Rename the ROM you want to flash to ROM.zip
Type "adb push ROM.zip /sdcard/" No quotes
If the ROM is around 1GB, this will take 5-10 minutes.
Once done, use TWRP file manager (under Advanced) to verify the file is there.
Reboot back into recovery and verify it's still there. If it is, install it. If it's not, you will have to RUU back to stock and go through the unlock process again.
NotATreoFan said:
If you type "adb devices" from a Command Prompt, do you see your phone listed?
Try powering off your phone, then holding Power+VolDown until you get to HBOOT. From there, enter recovery (TWRP is my preferred). ADB push does not require anything to be done prior to using it, so assuming you can see your phone with "adb devices", proceed like this:
Rename the ROM you want to flash to ROM.zip
Type "adb push ROM.zip /sdcard/" No quotes
If the ROM is around 1GB, this will take 5-10 minutes.
Once done, use TWRP file manager (under Advanced) to verify the file is there.
Reboot back into recovery and verify it's still there. If it is, install it. If it's not, you will have to RUU back to stock and go through the unlock process again.
Click to expand...
Click to collapse
No it isn't showing up when I do that while in recovery.
C:\Users\Mat\Desktop\adb>adb devices
List of devices attached
factor00 said:
No it isn't showing up when I do that while in recovery.
C:\Users\Mat\Desktop\adb>adb devices
List of devices attached
Click to expand...
Click to collapse
What about fastboot?
NotATreoFan said:
What about fastboot?
Click to expand...
Click to collapse
Yes fastboot is working. I can see the phone info still. You said I can just RUU. I didn't realize I could do that. That's fine with me I have no issue with that.
I just re-lock the boot loader and then run the RUU from windows? Would this be the appropriate file? RUU Zip M7 WL JB 50 VZW 1.10.605.10 Decrypted from HTC1 Guru.com (I can't post the actual link do to the forum rules.) The CID and model id match what my phone says.
Thanks for all your help!
factor00 said:
Yes fastboot is working. I can see the phone info still. You said I can just RUU. I didn't realize I could do that. That's fine with me I have no issue with that.
I just re-lock the boot loader and then run the RUU from windows? Would this be the appropriate file? RUU Zip M7 WL JB 50 VZW 1.10.605.10 Decrypted from HTC1 Guru.com (I can't post the actual link do to the forum rules.) The CID and model id match what my phone says.
Thanks for all your help!
Click to expand...
Click to collapse
I haven't done anything RUU in a while, so I don't want to steer you wrong. But I believe you can use decrypted to get everything up and running. Check the general forum for a guide on returning to stock.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Just remember to keep s-off while running the ruu
Hello everyone! glad to be a new member of this amazing community! I am a new member with a tough problem, would love if I get ideas on how to solve it.
So After flashing stock unrooted GPe rom as per the most common methods circulating around (changing CID, MID, S-Off, etc), I was thrilled to see the boot splash screen change into google's except that it keeps booting into the bootloader; for some reason I could not get into recovery either (but I flashed TWRP again and it works now)
So as it stands now I have the following:
S-Off
Unlocked
Software status: Official
Working TWRP (which keeps saying NO OS IS INSTALLED)
Unable to mount /data (whatever that means) + "error: closed" when attempting to sideload the RUU roms via ADB
I did not install any firmware or kernels
and whenever I try to boot the OS I get put back in bootloader over and over.
As far as im concerned this phone seems bricked for me, but im also new so I wouldn't know, having said that, I am open for the most radical of options and procedures to get this working.
Thank you all in advance!
Flash it again via adb, the flashing command must be executed twice.
I get an error "E:Unable to mount '/Data'" as soon as I open up the sideload option. when attempting to sideload I get "error: closed". I am starting to sense I have a problem with my storage. what to do next?
Thank you so much for your reply!
Megaliths said:
I get an error "E:Unable to mount '/Data'" as soon as I open up the sideload option. when attempting to sideload I get "error: closed". I am starting to sense I have a problem with my storage. what to do next?
Thank you so much for your reply!
Click to expand...
Click to collapse
That unrooted GPE was for dual sim? I see you have a dual sim.
Make a screenshot.
Details about the ROM would help.
Do a fastboot getvar all command also.
Actually I don't know if the Rom is for dual sim or not, I figured as long as I get CID and MID right it should fit? pardon my ignorance on the matter. ill post a screenshot as soon as possible!
Getvar all:
C:\Users\Megalith\Desktop\One_M8_All-In-One_Kit_v\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: GOOGL001
(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: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
Megaliths said:
Getvar all:
C:\Users\Megalith\Desktop\One_M8_All-In-One_Kit_v\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: GOOGL001
(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: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
Click to expand...
Click to collapse
Delete the IMEI.
OP - Do you want it back to Sense?
EddyOS said:
OP - Do you want it back to Sense?
Click to expand...
Click to collapse
I really prefer to get GPE working but sense is better than a bricked phone.
Also, thanks for the replies!
EddyOS said:
OP - Do you want it back to Sense?
Click to expand...
Click to collapse
Come to think about it now, I'd rather go to stock now if it all possible.
Megaliths said:
I really prefer to get GPE working but sense is better than a bricked phone.
Also, thanks for the replies!
Click to expand...
Click to collapse
Megaliths said:
Come to think about it now, I'd rather go to stock now if it all possible.
Click to expand...
Click to collapse
OK. First things first, did the GPe ROM ever work? The reason I ask it was designed for the single-SIM M8 so don't know if it worked with the dual-SIM version. If not, we should be OK to get back to stock...
EddyOS said:
OK. First things first, did the GPe ROM ever work? The reason I ask it was designed for the single-SIM M8 so don't know if it worked with the dual-SIM version. If not, we should be OK to get back to stock...
Click to expand...
Click to collapse
It never booted up correctly no. I'd love if you can help me go to stock with such a messed up state my phone had gotten into.
We should be able to sort things out, but I'll need to get to a proper PC and get links together
EddyOS said:
We should be able to sort things out, but I'll need to get to a proper PC and get links together
Click to expand...
Click to collapse
Thank you so much!
OK, this isn't particularly straight forward but should hopefully work...
Download the following files and place in your fastboot folder:
- Dual-SIM RUU - https://drive.google.com/file/d/0B17smFr95pleaW9iTFBiSUE2OVE/view?usp=sharing (rename to anything you want but I'd recommend ruu.zip, not ruu.zip.zip obviously!)
- htc_fastboot - https://www.androidfilehost.com/?fid=95897840722646249
- Sense FW - https://www.androidfilehost.com/?fid=23329332407589439 (again, rename to anything but I'd recommend firmware.zip)
1. First things first, boot into fastboot and set your CID to Super CID - fastboot oem writecid 11111111
2. Once done, reboot the bootloader and confirm it's done - fastboot reboot-bootloader
3. Assuming it's done, boot the phone into RUU mode - fastboot oem rebootRUU
4. Once in RUU mode, flash the firmware package - fastboot flash zip firmware.zip
5. It'll fail the first time and reboot. Do the exact same command again once back in RUU mode - fastboot flash zip firmware.zip
6. Once finished, reboot back to the bootloader to confirm it's on the white 'Sense' version - fastboot reboot-bootloader
7. Assuming it's done, reboot into RUU mode again - fastboot oem rebootRUU
8. Now flash the RUU using the HTC fastboot version - htc_fastboot flash zip ruu.zip
9. This will go through a few passes but once finished reboot to the bootloader - fastboot reboot-bootloader
10. Once back at the bootloader, disconnect the phone and go into stock recovery
11. Once in stock recovery, hold power and press volume up and once the menu appears do a factory reset
12. Once complete, reboot the phone
It should now boot back into the normal Sense ROM. Now if you changed your MID to the GPe one you'll need to re-root your phone and change it back using the guide by @scotty1223 HERE but if you didn't change it then you're good to go!
EddyOS said:
OK, this isn't particularly straight forward but should hopefully work...
Download the following files and place in your fastboot folder:
- Dual-SIM RUU - https://drive.google.com/file/d/0B17smFr95pleaW9iTFBiSUE2OVE/view?usp=sharing (rename to anything you want but I'd recommend ruu.zip, not ruu.zip.zip obviously!)
- htc_fastboot - https://www.androidfilehost.com/?fid=95897840722646249
- Sense FW - https://www.androidfilehost.com/?fid=23329332407589439 (again, rename to anything but I'd recommend firmware.zip)
1. First things first, boot into fastboot and set your CID to Super CID - fastboot oem writecid 11111111
2. Once done, reboot the bootloader and confirm it's done - fastboot reboot-bootloader
3. Assuming it's done, boot the phone into RUU mode - fastboot oem rebootRUU
4. Once in RUU mode, flash the firmware package - fastboot flash zip firmware.zip
5. It'll fail the first time and reboot. Do the exact same command again once back in RUU mode - fastboot flash zip firmware.zip
6. Once finished, reboot back to the bootloader to confirm it's on the white 'Sense' version - fastboot reboot-bootloader
7. Assuming it's done, reboot into RUU mode again - fastboot oem rebootRUU
8. Now flash the RUU using the HTC fastboot version - htc_fastboot flash zip ruu.zip
9. This will go through a few passes but once finished reboot to the bootloader - fastboot reboot-bootloader
10. Once back at the bootloader, disconnect the phone and go into stock recovery
11. Once in stock recovery, hold power and press volume up and once the menu appears do a factory reset
12. Once complete, reboot the phone
It should now boot back into the normal Sense ROM. Now if you changed your MID to the GPe one you'll need to re-root your phone and change it back using the guide by @scotty1223 HERE but if you didn't change it then you're good to go!
Click to expand...
Click to collapse
That is amazing thank you, ill try it and get back to you asap.
I have two questions:
Will I still get OTAs even if I don't have the original CID and MID? (I remember the original CID which is J15 but I can't remember the mid).
Also, I am currently on custom recovery and in your guide above I do not see anything about flashing stock recovery, should I do that first?
Thank you again!
The RUU flashes everything stock, so it'll overwrite it all
I'd change the CID back to stock once it's all working again but the MID I'm not sure on so I'll see if I can find out for you
At step 8 I get an error "DNS server not authoritative for zone", how to resolve that?
Nvm I resolved the DNS thin, but now I get error 41 model id check fail. It is probably because of bad MID isn't it?
Thank you again for helping me, I hope it is not much trouble.
Hi,
I have an HTC One M8 on Sprint. I have it rooted "S-On". I would like to install the OTA package but I need to restore to the stock recovery. I know I should have created a stock recovery before I rooted, but that time has passed. So now I am trying to gather my information so I can download one.
From the ToolKit:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.08.20.0916
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: XXXXXXXXXXXX
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_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: 8a0f02ff
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.007s
From this information I cannot find a stock recovery (no version-main). Has anyone ran into this issue with a blank version-main, or have a stock recovery file for CIDnum SPCS_001?
Any other recommendations or ideas would be greatly appreciated! If you need more information, please let me know.
Thanks!
Check Sprint thread - http://forum.xda-developers.com/showthread.php?t=2700666
ckpv5 said:
Check Sprint thread - http://forum.xda-developers.com/showthread.php?t=2700666
Click to expand...
Click to collapse
Thank you for the link, it was a great read. Also it had some information for me to find Sprint stock recovery files. However due to not having a version main number I am unable to identify which one to use.
So i'll ask the dumb question, does this matter? If not I was thinking of going with the newest one Stock_3.30.651.2
The .img files from this link: "Stock Recoveries for the Sprint M8 (All stock recoveries including HK)"
http://forum.xda-developers.com/showthread.php?t=2698394
Stock_1.12.651.17
Stock_1.54.651.8
Stock_1.54.651.10
Stock_2.16.651.4
Stock_3.30.651.2
Thank you!
That or 4.20.651.10, depending on what OTA that you have. Your hboot version suggests 3.30.651.2 is correct.
If you're no sure, the simplest way is:
Download OTA, select install later. Copy OTA zip from internal storage/Download to PC.
Open OTA zip with 7-zip, open firmware.zip, extract out recovery.img
Use this extracted recovery.img then continue OTA
ckpv5 said:
That or 4.20.651.10, depending on what OTA that you have. Your hboot version suggests 3.30.651.2 is correct.
If you're no sure, the simplest way is:
Download OTA, select install later. Copy OTA zip from internal storage/Download to PC.
Open OTA zip with 7-zip, open firmware.zip, extract out recovery.img
Use this extracted recovery.img then continue OTA
Click to expand...
Click to collapse
Thanks for all the help!
I did the following after I obtained the recovery.img file from the OTA I downloaded and extracted from internal storage/Downloads
1. Boot device into FASTBOOT mode (device should show FASTBOOT USB)
2. Extract recovery.img from the zip file and place recovery file to be flashed into folder with fastboot.
3. Open a command prompt from the folder where fastboot resides.
4. Run the following command:
fastboot flash recovery recovery.img
After this I selected HBOOT and RECOVERY, once it is rebooting I get a black screen with a phone in the middle that has a red "!".
This has become quit the process.
UPDATE: I rebooted the phone and tried Stock_3.30.651.2 instead of the one from the OTA. It has gone through its cycles and is at the "Android is upgrading - Optimizing app XX of XX".
The black screen with the red ! IS the stock recovery. How do people still not know this!
AtlasStone said:
Thanks for all the help!
I did the following after I obtained the recovery.img file from the OTA I downloaded and extracted from internal storage/Downloads
1. Boot device into FASTBOOT mode (device should show FASTBOOT USB)
2. Extract recovery.img from the zip file and place recovery file to be flashed into folder with fastboot.
3. Open a command prompt from the folder where fastboot resides.
4. Run the following command:
fastboot flash recovery recovery.img
After this I selected HBOOT and RECOVERY, once it is rebooting I get a black screen with a phone in the middle that has a red "!".
This has become quit the process.
UPDATE: I rebooted the phone and tried Stock_3.30.651.2 instead of the one from the OTA. It has gone through its cycles and is at the "Android is upgrading - Optimizing app XX of XX".
Click to expand...
Click to collapse
You can also use the recently published sprint M8 lollipop RUU process if you re-lock your boot loader first:
I can't post links yet for whatever reason but if you google search "htc-one-m8-sprint/news" it's the first result and includes instructions.
Sprint 5.0.1 RUU - http://dl3.htc.com/application/RUU_..._NV_SPCS_1.52_003_release_418488_signed_2.exe
Sprint Harman Kardon Edition 5.0.1 RUU - http://dl3.htc.com/application/RUU_..._NV_SPCS_1.52_003_release_418492_signed_2.exe
I was on GPE and I tried to switch to viperone Rom. Long story short, after flashing the firmware I got on a bootloop and I cant even access that white background page where you can fastboot & Hboot....I can only hold the volume up and power button get to this "Android system recovery" which gives me a few options:
Reboot System Now
Apply from SD card
Apply from Phone storage
Apply from Cache
Wipe data/factory reset
Wipe cache partition
I cant seem to adb or fastboot from my computer while doing this. Help.
fifaman said:
I was on GPE and I tried to switch to viperone Rom. Long story short, after flashing the firmware I got on a bootloop and I cant even access that white background page where you can fastboot & Hboot....I can only hold the volume up and power button get to this "Android system recovery" which gives me a few options:
Reboot System Now
Apply from SD card
Apply from Phone storage
Apply from Cache
Wipe data/factory reset
Wipe cache partition
I cant seem to adb or fastboot from my computer while doing this. Help.
Click to expand...
Click to collapse
well your story is pretty incomplete ... how did you end up with stock recovery ? What firmware did you flash ?
Flashing viper rom won't return you to stock recovery
To get to the normal bootloader from the above screen choose reboot System now and hold Volume Down as soon as the screen goes off
I flashed 1.54.401.5-W_splash.zip
Also your instructions worked! Any idea how I can fix this now?
clsA said:
well your story is pretty incomplete ... how did you end up with stock recovery ? What firmware did you flash ?
Flashing viper rom won't return you to stock recovery
To get to the normal bootloader from the above screen choose reboot System now and hold Volume Down as soon as the screen goes off
Click to expand...
Click to collapse
I flashed 1.54.401.5-W_splash.zip
Also your instructions worked! Any idea how I can fix this now?
fifaman said:
I flashed 1.54.401.5-W_splash.zip
Also your instructions worked! Any idea how I can fix this now?
Click to expand...
Click to collapse
well with the stock recovery your back to step one
is your bootloader still unlocked ? If yes flash custom recovery (TWRP) and Flash a Rom that matches the firmware your on
If your bootloader is relocked may as well update to the latest firmware the unlock and flash TWRP / Rom
Theirs also this RUU you can use
RUU_3.28.401.6_M8_WWE_Stock.exe
https://www.androidfilehost.com/?fid=95784891001609293
Zip
https://drive.google.com/file/d/0B4sLrKlVs0CPY29yV09MQURsd0k/view
Just saw this post >> http://forum.xda-developers.com/showpost.php?p=58773324&postcount=9
You can use that also Thanks to @EddyOS
clsA said:
well your story is pretty incomplete ... how did you end up with stock recovery ? What firmware did you flash ?
Flashing viper rom won't return you to stock recovery
To get to the normal bootloader from the above screen choose reboot System now and hold Volume Down as soon as the screen goes off
Click to expand...
Click to collapse
clsA said:
well with the stock recovery your back to step one
is your bootloader still unlocked ? If yes flash custom recovery (TWRP) and Flash a Rom that matches the firmware your on
If your bootloader is relocked may as well update to the latest firmware the unlock and flash TWRP / Rom
Click to expand...
Click to collapse
So im bootloader Unlocked and S-off. I cant seem to do adb commands but fastboot works. Is there any way I can check my firmware? When I flashed the firmware it all went to hell
fifaman said:
So im bootloader Unlocked and S-off. I cant seem to do adb commands but fastboot works. Is there any way I can check my firmware? When I flashed the firmware it all went to hell
Click to expand...
Click to collapse
I edited my post above just use one of the 2 RUU's
clsA said:
I edited my post above just use one of the 2 RUU's
Click to expand...
Click to collapse
Sigh* I tried to flash the TWRP and now its stuck in the "entering recovery" page.
EDIT: Still stuck
fifaman said:
Sigh* I tried to flash the TWRP and now its stuck in the "entering recovery" page
Click to expand...
Click to collapse
Are you using the instructions here ?
http://forum.xda-developers.com/showthread.php?t=2733523
was your phone always .401
clsA said:
I edited my post above just use one of the 2 RUU's
Click to expand...
Click to collapse
clsA said:
Are you using the instructions here ?
http://forum.xda-developers.com/showthread.php?t=2733523
You mention your phone is T-mobile is that true ? or was your phone always .401
Click to expand...
Click to collapse
No my phone is the GSM one from Canada....I dont know how to get out of this "entering recovery" page =/
fifaman said:
No my phone is the GSM one from Canada....I dont know how to get out of this "entering recovery" page =/
Click to expand...
Click to collapse
hold power + volume up till the phone shuts off
then switch to power + volume down
Post fastboot getvar all and remove your serial no and IMEI
fifaman said:
Sigh* I tried to flash the TWRP and now its stuck in the "entering recovery" page.
EDIT: Still stuck
Click to expand...
Click to collapse
You can't use TWRP 2.8.4.0 or 2.8.5.0 when your hboot is lower than 3.19.0000
You should run RUU 4.16.401.10 first then only flash TWRP.
No point to flash TWRP at current stage.
clsA said:
hold power + volume up till the phone shuts off
then switch to power + volume down
Post fastboot getvar all and remove your serial no and IMEI
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(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
Im also on Mac so I cant use EXE files, only can fastboot zip files
fifaman said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(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
Im also on Mac so I cant use EXE files, only can fastboot zip files
Click to expand...
Click to collapse
follow the instructions here > > http://forum.xda-developers.com/showpost.php?p=58773324&postcount=9
and your phone should be fine
clsA said:
hold power + volume up till the phone shuts off
then switch to power + volume down
Post fastboot getvar all and remove your serial no and IMEI
Click to expand...
Click to collapse
clsA said:
follow the instructions here > > http://forum.xda-developers.com/showpost.php?p=58773324&postcount=9
and your phone should be fine
Click to expand...
Click to collapse
Thanks, Im doing this now. Do I HAVE to relock the bootloader? Unlocking it in the first place was a plain
Relock bootloader only for S-On
S-Off no need to do that
You may need to change your MID to EU one if that RUU zip fails.
ckpv5 said:
Relock bootloader only for S-On
S-Off no need to do that
You may need to change your MID to EU one if that RUU zip fails.
Click to expand...
Click to collapse
It failed, how do I change my MID to EU?
fifaman said:
It failed, how do I change my MID to EU?
Click to expand...
Click to collapse
Do you really want to convert everything to EU version instead of original Canada version ?
How to change MID to EU in your case :
1. Install TWRP 2.8.1.0 - http://techerrata.com/browse/twrp2/m8
command fastboot flash recovery openrecovery-twrp-2.8.1.0-m8.img
2. Boot to recovery
3. Run these command
adb shell
then copy & paste this command
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
then
fastboot reboot-bootloader
4. flash that RUU zip after put your device in RUU mode
fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip
Wait ... you have a Mac, need to find correct fastboot file for your Mac version
ckpv5 said:
Relock bootloader only for S-On
S-Off no need to do that
You may need to change your MID to EU one if that RUU zip fails.
Click to expand...
Click to collapse
ckpv5 said:
Do you really want to convert everything to EU version instead of original Canada version ?
How to change MID to EU in your case :
1. Install TWRP 2.8.1.0 - http://techerrata.com/browse/twrp2/m8
command fastboot flash recovery openrecovery-twrp-2.8.1.0-m8.img
2. Boot to recovery
3. Run these command
adb shell
then copy & paste this command
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
then
fastboot reboot bootloader
4. flash that RUU zip after put your device in RUU mode
Click to expand...
Click to collapse
I would prefer the canadian one but I was only asking on your recommendation =/
fifaman said:
I would prefer the canadian one but I was only asking on your recommendation =/
Click to expand...
Click to collapse
It is easier for Canada version, you just need to flash the TWRP either 2.8.1.0 or 2.8.3.0 then transfer the nandroid backup and restore then do OTA to the latest.
The only thing is do you remember which Canada version is yours ? ROGERS, BELL, TELUS or GLOBAL or SASKT ?
Hi All,
I've been a member here for a long time, but now with a new account.
I have a real problem, and I do not know what to do.
Firstly, I am pretty computer literate, but I am lost with phone technology a little. I have a bit of experience flashing ROMS, but I really do not know where to begin.
I bought a HTC ONE M8 for my daughter from eBay (I know... ) and today it seems to have tried an update. This has resulted in bricking my phone. The M8 was (I thought) new, but whatever has happened has screwed things up.
Can someone help me recover from this update failure? I can provide all information from the BOOT screens for you, but as yet, I don't even know what to supply.
Thanks chaps - I know this is the only place that will be able to help as you are all expert.
Simon
Edit: I have installed Android Studio as I have read that this is what I need initially.
Edit: Bootloader Information
*** Software status: Official ***
*** Locked ***
M8_UL PVT SHIP S-OFF
OS-6.12.401.4
So, here are my thoughts. I think that this is a Chinese HTC and it has tried up update to a Europe Marshmellow ROM. Can anyone confirm this might be causing the problem?
Can I "roll-back"?
Ratzz2 said:
Edit: Bootloader Information
*** Software status: Official ***
*** Locked ***
M8_UL PVT SHIP S-OFF
OS-6.12.401.4
So, here are my thoughts. I think that this is a Chinese HTC and it has tried up update to a Europe Marshmellow ROM. Can anyone confirm this might be causing the problem?
Can I "roll-back"?
Click to expand...
Click to collapse
M8_UL is not a Chinese HTC. I guess your problem is root or previously a rooted device and that is the reason the update failed.
To get to know better about your device, post here fastboot getvar all result minus serial & imei no.
Then we'll see what you need to do ... either roll-back or moving forward with a new Marshmallow stock ROM
Hi, thanks for replying.
I see, I didn't know that M8_UL is not a Chinese HTC - shows how much I know about this kind of stuff!
I will look up how to post the fastboot getvar all information, but if I don't get back to this first, I am assuming (from what I have already read) that I can do this via a CMD window? I am not 100% what I need to download to access my HTC, but will look into it now.
Many thanks again - you have given me a glimmer of hope!
Assuming you have a Windows PC ...
What you need is fastboot/adb, install this : http://forum.xda-developers.com/showthread.php?t=2588979
-when install the adb installer, select Y for system-wide and N for drivers
-you can open Command Prompt from any where that you like when it is system-wide.
HTC USB drivers - Install HTC Sync Manager - http://www.htc.com/us/support/software/htc-sync-manager.aspx
- it will install the needed drivers then uninstall the HTC Sync Manager but leave the drivers.
Open a command prompt then type fastboot getvar all
copy the output but delete serial & imei no.
Here we go ...
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(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: 0P6B10000
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.102s
First - you need this : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
If the bootloader is UNLOCKED (for S-On device only), relock it with commands:
fastboot oem lock
fastboot reboot-bootloader
Since the bootloader is LOCKED, what you can do :
1. Download the RUU zip here : https://www.androidfilehost.com/?fid=24369303960687057
2. Download htc_fastboot.exe here : https://drive.google.com/file/d/0B8L4pkbzdlR3eTlJSjdKVEdHX1U/view
Make a folder say "RUU" on your desktop and put both RUU zip and htc_fastboot.exe in this RUU folder
Then follow these :
Rename the RUU zip to RUU.zip (make sure you don't hide the windows extension so you won't make mistake and rename it to RUU.zip.zip)
put your device on bootloader/fastboot mode (as you get the getvar) and connect to PC
Open a command prompt from RUU folder then run below commands:
fastboot reboot-bootloader (reboot to bootloader to ensure the connection is good)
fastboot oem rebootRUU (put the device in RUU mode)
htc_fastboot flash zip RUU.zip (to install RUU)
Once complete - fastboot reboot
It should boot, then you run setup .. done.
(Only thing is you will lose all data in internal storage as RUU will give you out of the box state - at least better than a non-working phone)
NOTE : other methods to install RUU zip - http://forum.xda-developers.com/showpost.php?p=67314040&postcount=1749
Thank-you my friend, am downloading now.
Not worried about the data loss - I'd pretty much written the phone off anyway, so loss of data is a very small price to pay.
Will update you once all done.
If possible use PC with USB2.0
I'm on mobile for 6 hours.
If the above fails, I'll give you another method later.
I don't see a reason it would fail.
Thank you buddy - you are indeed, a GOD! :good::good::good::good::good::good:
It has re-booted and is just updating the apps. I will make sure I turn off the 'auto update' option so this won't happen again.
Just out of interest, if I wanted ever to upgrade the OS are there any good resources I could read?
I really appreciate your time in this - I know it's not easy to see a bit of a newbie type "Bricked" in the title!
Thanks again...
Simon
Great :good:
If you don't plan to root the device, there is no need to turn off auto update. It will success for future update when there is one.
Don't think there will be another OS update for M8, this Marshmallow is the last major OS update. If there is any further update, it will be some patches/small update.
Thanks again, you have been a massive help ...
Hi, I am new to this forum and have the same problem. Everything has been working until the step 'htc_fastboot flash zip RUU.zip (to install RUU)'. It tells me that 'htc_fastboot is not recognized as an internal or external command, operable program or batch file. Any assistance on this? I am not stuck with a black screen just written htc But thanks for your help so far...I have a little hope this will be sorted
PavM3 said:
Hi, I am new to this forum and have the same problem. Everything has been working until the step 'htc_fastboot flash zip RUU.zip (to install RUU)'. It tells me that 'htc_fastboot is not recognized as an internal or external command, operable program or batch file. Any assistance on this? I am not stuck with a black screen just written htc But thanks for your help so far...I have a little hope this will be sorted
Click to expand...
Click to collapse
You probably failed to perform one of these steps:
ckpv5 said:
2. Download htc_fastboot.exe here : https://drive.google.com/file/d/0B8L4pkbzdlR3eTlJSjdKVEdHX1U/view
Make a folder say "RUU" on your desktop and put both RUU zip and htc_fastboot.exe in this RUU folder
Open a command prompt from RUU folder then run below commands:
Click to expand...
Click to collapse
Note that the part I've highlighted in red is really important. If your command prompt is not opened in the right folder (where htc_fastboot.exe is located) it won't work; even if you did all the other steps correctly.
A shortcut to open CMD prompt in the correct directory, is to open the RUU folder, then with your cursor inside the RUU folder window: Shift-right mouse button click, then select "Open command window here".
I did open the command prompt from within the RUU folder (which I saved on the desktop) so the path is c:\user\user\desktop\RUU hence the command looked like this c:\user\user\desktop\RUU\htc_fastboot flash zip RUU.zip and that is what gave me the error.
I had typed the first two commands ' Fastboot reboot-bootloader' and 'fastboot oem rebootRUU' not from within the RUU folder but from c:\program files\Minimal ADB and Fastboot>. These commands worked, but not now when I try the two from within RUU where I keep getting an error.
What I see is lack of interaction between Minimal ADB and Fastboot (Which I saved under C:\program files) and RUU saved on the desktop. Should I have saved them in the same folder? I have tried moving RUU to the same path as Minimal ADB and Fastboot but that doesn't work either.
Yes, I had I downloaded the files from the links provided and opened that command prompt from within RUU (holding down shift button and right clicking to get 'open command window here'. I have never done this sort of thing before so pardon my lack of knowledge on the basics....I am just determined to have my HTC m8 working again since there is no care centre in Kenya, where I come from. Thanks for the prompt response - wish I noticed it earlier.
redpoint73 said:
You probably failed to perform one of these steps:
Note that the part I've highlighted in red is really important. If your command prompt is not opened in the right folder (where htc_fastboot.exe is located) it won't work; even if you did all the other steps correctly.
A shortcut to open CMD prompt in the correct directory, is to open the RUU folder, then with your cursor inside the RUU folder window: Shift-right mouse button click, then select "Open command window here".
Click to expand...
Click to collapse
PavM3 said:
I did open the command prompt from within the RUU folder (which I saved on the desktop) so the path is c:\user\user\desktop\RUU hence the command looked like this c:\user\user\desktop\RUU\htc_fastboot flash zip RUU.zip and that is what gave me the error.
I had typed the first two commands ' Fastboot reboot-bootloader' and 'fastboot oem rebootRUU' not from within the RUU folder but from c:\program files\Minimal ADB and Fastboot>. These commands worked, but not now when I try the two from within RUU where I keep getting an error.
What I see is lack of interaction between Minimal ADB and Fastboot (Which I saved under C:\program files) and RUU saved on the desktop. Should I have saved them in the same folder? I have tried moving RUU to the same path as Minimal ADB and Fastboot but that doesn't work either.
Click to expand...
Click to collapse
Can you confirm the RUU folder contains a file htc_fastboot.exe? You didn't rename this at all, did you?
Try to copy the RUU.zip and htc_fastboot.exe in the Minimal ADB and Fastboot folder, and see if that helps.
Yes. The RUU folder contains the file htc_fastboot.exe as well as RUU.zip (which was renamed to this from the initial long name it had when I downloaded). I had already tried copying both RUU.zip and htc_fastboot.exe in the Minimal ADB and Fastboot folder and have just retried and I get the error message 'preprocess_file: Cannot read header len bytes. Also I had tried and just retried copying the RUU folder (as opposed to the two separately)in the Minimal ADB and Fastboot folder and now it says 'Fastload is not recognized as an internal or external command, operable program or batch file.'
redpoint73 said:
Can you confirm the RUU folder contains a file htc_fastboot.exe? You didn't rename this at all, did you?
Try to copy the RUU.zip and htc_fastboot.exe in the Minimal ADB and Fastboot folder, and see if that helps.
Click to expand...
Click to collapse
Can you do a screen capture of the RUU folder contents?
And also of the CMD window, when you try the command to flash the RUU zip (from RUU folder - let's concentrate there).
Is this solution applicable to this problem ? -> http://forum.xda-developers.com/htc-one-m8/help/htc-m8-boots-recovery-mode-t3303826
PandaDNB said:
Is this solution applicable to this problem ? -> http://forum.xda-developers.com/htc-one-m8/help/htc-m8-boots-recovery-mode-t3303826
Click to expand...
Click to collapse
If the RUU matches your phone's CID, yes.
Well i can currently see on the phone screen CID-11111111 and the 1.6 gig file(which is the RUU ?) is still downloading.
When i ran the fastboot 1.3.1 i got the same output as the OP.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(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: 0P6B10000
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0