SOLVED - THANKS!
Dear community,
Goal: I want to put a HTC One M8 device into stock. The phone used to be unlocked before and had a custom rom (think it was LineAge).
I already made it to restore it to stock by following the tutorial here in this forum.
Everything fine, but WIFI and bluetooth do not work, I cannot switch them on. I have read that this may be caused by an incompatible firmware version?
Please understand, that I am very new to the topic and have read a lot of stuff, tutorials and because of so many different information and missing experience from my side, I am not sure what to do.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***
(bootloader) imei: ***
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: f063fb42
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: -0.000s
The phone is now relocked and I cannot access TWRP anymore. Trying to reinstall it using fastboot throws out the following lines:
fastboot flash recovery twrp-3.2.3-1-m8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20168 KB)...
OKAY [ 1.810s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.528s
Think because the bootloader is locked?
I have really no clue how to proceed.
gskill150 said:
I already made it to restore it to stock by following the tutorial here in this forum.
Everything fine, but WIFI and bluetooth do not work, I cannot switch them on. I have read that this may be caused by an incompatible firmware version?
Click to expand...
Click to collapse
Probably correct, that mostly likely, you restored the wrong TWRP backup version (not compatible with the firmware on the phone - firmware is not the same thing as the ROM or TWRP backup - that part may be confusing).
What version number TWRP backup did you restore (using the guide)?
gskill150 said:
The phone is now relocked and I cannot access TWRP anymore. Trying to reinstall it using fastboot throws out the following lines:
fastboot flash recovery twrp-3.2.3-1-m8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20168 KB)...
OKAY [ 1.810s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.528s
Think because the bootloader is locked?
Click to expand...
Click to collapse
Yes, this is because you relocked the bootloader. You can't flash a custom recovery with a locked or relocked bootloader, by definition.
But relocking the bootloader is not part of the guide, in regards to restoring a TWRP backup. What exactly were you trying to accomplish the relocking the bootloader?
I took the twrp-3.2.3-1-m8.img (following this instruction out of the tutorial: recommended 2.8.7.0 or latest for 4.xx.xxx.x & 6.xx.xxx.x TWRP backup)
I relocked the bootloader because I Wanted to directly flash the stock RUU using the ruu.zip on SD-Card method.
I dont know if I am allowed to post a link to another forum. According to their Tutorial, if I am S-On and want to flash the stock ruu I Need to lock the bootloader before proceeding. Being already on firmware 4.16.401.13, I dont Need to downgrade it if I flash an image 4.16.401.10 which I found in their image directories. I would try this next. Or what do you recommend?
(bootloader) version-main: 4.16.401.13
-> is this the firmware? I am afraid that I am mixing up firmware and ROM/RUU.
Thanks and best regards
gskill150 said:
I took the twrp-3.2.3-1-m8.img (following this instruction out of the tutorial: recommended 2.8.7.0 or latest for 4.xx.xxx.x & 6.xx.xxx.x TWRP backup)
Click to expand...
Click to collapse
I probably wasn't completely clear, but I was asking: what version number backup (M8 operating system version number) you tried to restore, not the TWRP version number. In other words, which file exactly did you download from the stock backup tutorial you linked? Was it 4.16.401.13 or 6.12.401.4, etc.
gskill150 said:
I relocked the bootloader because I Wanted to directly flash the stock RUU using the ruu.zip on SD-Card method.
I dont know if I am allowed to post a link to another forum. According to their Tutorial, if I am S-On and want to flash the stock ruu I Need to lock the bootloader before proceeding. Being already on firmware 4.16.401.13, I dont Need to downgrade it if I flash an image 4.16.401.10 which I found in their image directories.
Click to expand...
Click to collapse
It would have been best to supply this information up front, all the things you have tried, and the reason for the current status. Otherwise, you see that it is very confusing that you describe for almost the entirety of your top post about trying to restore a stock TWRP backup, but don't mention trying (or intending to) to flash the RUU? Which is a completely different path.
You can't post "clickable" links yet (think you need >10 posts). But you can post the link, then obfuscate it by changing some characters, such as "dotcom", which we can then change back, and cut/paste into the browser to see where you got the file.
I'm not certain what you mean by "their image directories". Do you mean HTC (or something else)? If you mean HTC, then I don't think you have an RUU, since HTC typically does not post RUUs for your version M8. Although there are some "leaked" ones posted by users.
So it's important to know the source of the RUU(?) file you intend to try, such as a link or at least the exact file name of what you downloaded (file size in MB or GB would also be useful to tell what it is).
gskill150 said:
(bootloader) version-main: 4.16.401.13
-> is this the firmware? I am afraid that I am mixing up firmware and ROM/RUU.
Click to expand...
Click to collapse
In short, yes, that is the current version number of the firmware on the phone.
When "firmware" is discussed for this device, it does not refer to the ROM or OS number. But rather, firmware is a small file that is needed for the ROM to work and includes hboot, radio, and a number of other partitions (Bluetooth, WiFI), but does not contain the ROM itself. This is confusing, as some folks like to use the terms "firmware" and "ROM" interchangeably. At least for this device, you should wipe that notion from your mind.
Flashing a custom ROM or restoring a stock TWRP backup will not touch firmware, as flashing a ROM by TWRP will only change the system and boot.img partitions, and not touch things like hboot, radio. And flashing a ROM in TWRP will also not affect the version number reported in getvar. That number will only change if you flash firmware.zip or RUU.
RUU is a complete factory image (40+ partitions) which also includes firmware. Some folks will call the RUU the "stock ROM" but you can now see, it is much more than that.
A little confusing, right?
First of all, many thanks for your detailed help and sorry for providing incomplete information from my side. This topic is really hard to understand and confuses me a lot. Sorry for that.
redpoint73 said:
I probably wasn't completely clear, but I was asking: what version number backup (M8 operating system version number) you tried to restore, not the TWRP version number. In other words, which file exactly did you download from the stock backup tutorial you linked? Was it 4.16.401.13 or 6.12.401.4, etc.
Click to expand...
Click to collapse
I took, 4.16.401.13 out of www DOT mega DOT nz/#!X9IjVASb!bNCxQJlDbX40cLHGlmP1qk0SaYfW93lo8jicFv81B-4
It would have been best to supply this information up front, all the things you have tried, and the reason for the current status. Otherwise, you see that it is very confusing that you describe for almost the entirety of your top post about trying to restore a stock TWRP backup, but don't mention trying (or intending to) to flash the RUU? Which is a completely different path.
Click to expand...
Click to collapse
Sorry for that - as written I am new to the topic and was mixing up things that do not belong together (RUU, ROM, firmware). Again in a few words: phone used to have LineAgeOS (CustomRom) and I just wanted get rid of it and restore the original android version as if I had bought the phone completely new
I tried it through TWRP because I found this tutorial here in the forum and thought this would be the right path.
You can't post "clickable" links yet (think you need >10 posts). But you can post the link, then obfuscate it by changing some characters, such as "dotcom", which we can then change back, and cut/paste into the browser to see where you got the file.
Click to expand...
Click to collapse
As next steps and after having relocked the bootloader I was planning to perform the steps mentioned in this tutorial (sorry it is German) in the Page: www DOT handy-faq DOT de/forum/htc-one-m8-stock-rom-wiederherstellen-via-ruu-t314727/
and doing method 1 (flashing RUU using RUU.zip) with the use of a RUU 4.16.401.10 (which can be found on www DOT androidfilehost DOT com/?fid=95916177934518148
I'm not certain what you mean by "their image directories". Do you mean HTC (or something else)? If you mean HTC, then I don't think you have an RUU, since HTC typically does not post RUUs for your version M8. Although there are some "leaked" ones posted by users.
So it's important to know the source of the RUU(?) file you intend to try, such as a link or at least the exact file name of what you downloaded (file size in MB or GB would also be useful to tell what it is).
Click to expand...
Click to collapse
I meant the RUUs from the other guide I have just posted above
A little confusing, right?
Click to expand...
Click to collapse
To be honest, now it is completely clear to me thanks to your really good explanation. Thanks mate!
So I could go for the ruu.zip flashing path to achieve what I want right?
gskill150 said:
I took, 4.16.401.13 out of www DOT mega DOT nz/#!X9IjVASb!bNCxQJlDbX40cLHGlmP1qk0SaYfW93lo8jicFv81B-4
Click to expand...
Click to collapse
That is the right number stock backup to restore (same number as firmware number - version main in getvar). I don't know why you are having issues with WiFi and Bluetooth.
Might be a problem with the firmware. Flashing RUU is probably the best approach. Not only will it restore the stock ROM, but also restore stock firmware. Which hopefully will resolve your WiFi and Bluetooth issue.
gskill150 said:
As next steps and after having relocked the bootloader I was planning to perform the steps mentioned in this tutorial (sorry it is German) in the Page: www DOT handy-faq DOT de/forum/htc-one-m8-stock-rom-wiederherstellen-via-ruu-t314727/
and doing method 1 (flashing RUU using RUU.zip) with the use of a RUU 4.16.401.10 (which can be found on www DOT androidfilehost DOT com/?fid=95916177934518148
So I could go for the ruu.zip flashing path to achieve what I want right?
Click to expand...
Click to collapse
That RUU should be okay. Alternately, you can flash the Marshmallow RUU, which will not only restore you to stock image, but also have the most updated (last) version. Marshmallow RUU and instructions here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Note, that you should use the htc_fastboot as directed in the instructions, not the "generic" Google fastboot. The generic one can't handle the large RUU file size (about 1.5 GB).
redpoint73 said:
Alternately, you can flash the Marshmallow RUU, which will not only restore you to stock image, but also have the most updated (last) version. Marshmallow RUU and instructions here: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Note, that you should use the htc_fastboot as directed in the instructions, not the "generic" Google fastboot. The generic one can't handle the large RUU file size (about 1.5 GB).
Click to expand...
Click to collapse
Hi, thanks for your reply. I will give it a try! :good:
gskill150 said:
Hi, thanks for your reply. I will give it a try! :good:
Click to expand...
Click to collapse
It worked using the guide I posted (with the ruu.exe).
Issue solved. Wifi Problem fixed. Learned a lot! Appreciating this Forum and especially your help so much. Thanks!!!
gskill150 said:
It worked using the guide I posted (with the ruu.exe).
Issue solved. Wifi Problem fixed. Learned a lot! Appreciating this Forum and especially your help so much. Thanks!!!
Click to expand...
Click to collapse
You're quite welcome. Glad it worked for you.
Hello guys,
I have an HTC one m8 , I have been running a rooted device with custom rom which has been working terribly on my device...Now I want to return to stock rom, I have relocked bootloader and it's on s-on...I have tried out diverse RUU but all seems not working...I'm always getting this error in the process "rom update utility cannot update your andriod phone"" which i guess the ruu's have been using are not compatible with my phone...I would so much appreciate if anyone can get me the RUU executable file for my device that will be compatible with it........ Here is the fastboot getvar all details....Your prompt responses will be appreciated
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: S**********6
(bootloader) imei: 35*************7
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: T-MOB009
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
Jjohnson0830 said:
I have tried out diverse RUU but all seems not working...
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: T-MOB009
Click to expand...
Click to collapse
You can't just guess at which RUU and expect it to work. The RUU needs to match the CID/MID on your version M8. And your version M8, I'm pretty sure doesn't even have an RUU. So whatever you tried, was the wrong RUU.
Return to stock using the stock TWRP backup, where you also posted.
On that note, please don't post the same question to multiple threads. It won't get you help any faster. It just confuses you and those trying to help you. Do you really intend on checking and updating 3 different threads, if folks start helping you in different places? That never happens.
redpoint73 said:
You can't just guess at which RUU and expect it to work. The RUU needs to match the CID/MID on your version M8. And your version M8, I'm pretty sure doesn't even have an RUU. So whatever you tried, was the wrong RUU.
Return to stock using the stock TWRP backup, where you also posted.
On that note, please don't post the same question to multiple threads. It won't get you help any faster. It just confuses you and those trying to help you. Do you really intend on checking and updating 3 different threads, if folks start helping you in different places? That never happens.
Click to expand...
Click to collapse
Ok, pls where can i get the stock TWRP backup and how am i going to return to stock using it?
Thanks and sorry again for what happened, I mean crossing posts...I think i needed to just respond to your responses on all the 3 threads i posted...it won't repeat itself again
Jjohnson0830 said:
Thanks and sorry again for what happened, I mean crossing posts...I think i needed to just respond to your responses on all the 3 threads i posted...it won't repeat itself again
Click to expand...
Click to collapse
No, you really don't. Please.
Related
Hi,
Having issues trying to put SuperSU on my M8. Heres what I've done:
- Unlocked bootloader
- Fastbooted TWRP on the phone
- Tried Flashing the ROM, says No OS installed. Rebooting stops at Android screen
- Tried downloading RUU and going back to stock, however the RUU tells me that there's an error and it can't continue.
- Tried switching between TWRP and CWM.
- Tried sideloading from my pc with a few different versions of SuperSU
Nothing seems to work.
Can anyone point me in the right direction?
Any help will be greatly appreciated.
If there's any more information you would like me to provide, just let me know.
Thanks Again,
Nick
My responses below in red font:
varioushalifax said:
Having issues trying to put SuperSU on my M8. Are you trying to root the stock ROM, or flash a custom ROM? Because they are 2 different things, with different approaches. And your steps described below contradict each other on this matter..
Heres what I've done:
- Unlocked bootloader
- Fastbooted TWRP on the phone What version TWRP?
- Tried Flashing the ROM, says No OS installed. Rebooting stops at Android screen Which ROM exactly? Did you try another ROM? Did the ROM install properly (any error messages in TWRP when you flashed?
- Tried downloading RUU and going back to stock, however the RUU tells me that there's an error and it can't continue. What RUU (exact file name)? What was the error message and error number? These are important, as they tell you why the RUU failed.
- Tried switching between TWRP and CWM. Not recommended. CWM hasn't been updated in a long time, and can cause some problems in itself.
- Tried sideloading from my pc with a few different versions of SuperSU If you have no OS, flashing SuperSU isn't going to help matters.
Click to expand...
Click to collapse
Additonally, do fastboot getvar all, so we can see more info about the phone. Delete IMEI and serial number before posting.
Are you trying to root the stock ROM, or flash a custom ROM?
Originally I tried to put SuperSU2.37 on there, that didn't work, so I tried SuperSU2.77, which failed. I then tried to RUU to stock, which I'm having issues with also.
- What version TWRP?
3.0.2-0
- Any error messages in TWRP when you flashed?
It doesn't show any errors. After it's finished it says No OS Installed, are you sure you want to reboot?
- What RUU (exact file name)?
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
Error 155
Please get the correct RUU and try again.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks again,
Nick
redpoint73 said:
My responses below in red font:
Click to expand...
Click to collapse
your method to solve problems to the point by red font is very nice master redpoint. :good:
varioushalifax said:
Originally I tried to put SuperSU2.37 on there, that didn't work, so I tried SuperSU2.77, which failed.
Click to expand...
Click to collapse
SuperSU version 2.37 is really old. Not sure how you even came about it (old toolkit maybe?), that version probably wouldn't work on Lollipop, much less your current Marshmallow firmware.
SuperSU 2.77 should be okay, its current and updated for MM. I might suggest the latest "STABLE" version, which is 2.76 from here. But honestly, they are all pretty stable from what I've seen, and it probably wouldn't make a huge difference wither way (the version 2.77 should be ok). And it seems like the main problem is that we need to solve the "No OS" issue before proceeding.
varioushalifax said:
It doesn't show any errors. After it's finished it says No OS Installed, are you sure you want to reboot?
Click to expand...
Click to collapse
My guess, is that you did something to delete the OS, that maybe you missed when listing the steps you did. Since, I can't see how OS could be wiped/missing with what you indicated. At least up until you tried RUU, since if you relocked the bootloader to RUU (which is a requirement unless you have s-off), that wipes the OS (so maybe you just have the order of steps you tried, mixed up?).
varioushalifax said:
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
Error 155
Click to expand...
Click to collapse
That RUU isn't for your version. Maybe the "WWE" in the file name has you confused, but its actually for the US Developer's Edition. What you need would have version number with "401" instead of "1540", but you would only know that from experience or reading it somewhere on the forums.
You should be able to use the following RUU (zip format, not exe - so follow the instructions to flash): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Alternately, restore the stock TWRP backup 6.12.401.4 using the file and instructions here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Not sure whether your bootloader is currently relocked or unlocked, as you haven't indicated, either way. It needs to be relocked to RUU, or alternately it needs to be unlocked to do the TWRP stock backup method.
---------- Post added at 09:35 AM ---------- Previous post was at 09:17 AM ----------
umesh.lk said:
your method to solve problems to the point by red font is very nice master redpoint. :good:
Click to expand...
Click to collapse
Haha, I find that a good way to respond to numerous statements or questions in a previous post; rather than using multiple quotes. And red just seems to stand out well, compared to other colors! But love your observation.
Thanks so much!
I wasn't sure which files i needed for that walkthrough, until you told me which ones.
Phone is back up and working fine.
Thanks again mate
While, i dint do much. My phone showed, i have an update that could be installed. I went ahead and did so. But unfortunately it wasnt successful. Now all i have is htc logo. I can also get into fastboot mode. I tried an RUU:
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 doesnt help. I did unlock the bootloader by going to htc dev and using the hasoons tool kit.
Now the Fastboot menu says:
Software status modified
pink color: ***unlocked****
fastboot getvar all results below
C:\htc>HTC_fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 162(ms)
------------------------------------------
Also i should say i tried to copy the rom.zip from the ruu.exe (temp location). Tried flashing it, either i get a 24 parsing error or remote 32 header error. so thats a long story short. I am in India by the way. And i believe the phone is global version.
If in case you want any other info i can provide you that. Can you help me get back to the stock rom. Marshmallow
pauluthupm said:
I tried an RUU:
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 doesnt help. I did unlock the bootloader by going to htc dev and using the hasoons tool kit.
Click to expand...
Click to collapse
That RUU won't work, its not for your Euro "401" version, its for the US Developer's Version (1540). You need RUU 6.12.401.4 which can be found in .zip format here (don't know of a source for exe format): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
You also need to relock the bootloader to run the RUU. Instructions to do so, are also included on the link above.
Did you unlock the bootloader to RUU? If so, you have it backwards. RUU requires bootloader LOCKED or RELOCKED. RUU will never run with bootloader unlocked (unless you have s-off, which you don't).
Solved : Unbrick HTC M* - Revert to Stock
redpoint73 said:
That RUU won't work, its not for your Euro "401" version, its for the US Developer's Version (1540). You need RUU 6.12.401.4 which can be found in .zip format here (don't know of a source for exe format): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
You also need to relock the bootloader to run the RUU. Instructions to do so, are also included on the link above.
Did you unlock the bootloader to RUU? If so, you have it backwards. RUU requires bootloader LOCKED or RELOCKED. RUU will never run with bootloader unlocked (unless you have s-off, which you don't).
Click to expand...
Click to collapse
Thank you for the help. fortunately i did find the solution. just the way u said only. I was in office and dint have access to xda in office. Let me also put what i have done.
pauluthupm said:
While, i dint do much. My phone showed, i have an update that could be installed. I went ahead and did so. But unfortunately it wasnt successful. Now all i have is htc logo. I can also get into fastboot mode. I tried an RUU:
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 doesnt help. I did unlock the bootloader by going to htc dev and using the hasoons tool kit.
Now the Fastboot menu says:
Software status modified
pink color: ***unlocked****
fastboot getvar all results below
C:\htc>HTC_fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 162(ms)
------------------------------------------
Also i should say i tried to copy the rom.zip from the ruu.exe (temp location). Tried flashing it, either i get a 24 parsing error or remote 32 header error. so thats a long story short. I am in India by the way. And i believe the phone is global version.
If in case you want any other info i can provide you that. Can you help me get back to the stock rom. Marshmallow
Click to expand...
Click to collapse
I downloaded the correct version of Marshmallow from Android Ghost : url below.
https://www.androidfilehost.com/?fid=24369303960687057
Make sure u download the htc fastboot files: Google is ur friend.
Place the image in the same folder as the htc fastboot files are.
rename the file to 0P6BIMG.zip( remember not to add two zips at the end.,windows generally hides the extension
Now open ur command prompt.
naviagate to the htc fastboot folder , i my case, i put in c drive
so it would like c:\htc_fastboot_files
Now Voulme Down Button and then press the power button.
In my case i had to use Power+Volume up to reboot the phone . And the moment it rebooted i pressed just the vol down button.
So we would be in Bootloader. Now switch phone to fastboot mode.
Navigate using volume buttons and power button to enter.
in fast boot mode
bring up ur command prompt:
We are already in the fastboot file folder. like i mentioned before: c:\htc_fastboot_files
type fastboot get var all
look for this info: (bootloader) version-main: 6.12.401.4 ( This might be different case to case, according to this you can search for relevant ruu, just google with the version number firmware)
Now htc_fastboot oem lock ( To relock the bootloader)
htc_fastboot oem rebootRUU
htc_fastboot flash zip Firmware_xx.zip ( in my case its 0P6BIMG.zip)
Once the flash completes, you will have a window which says Flash complete. OKAY. Mind you it takes some time.
After this,
htc_fastboot reboot . Thats it. Phone will take quite some time to reboot and complete the process.
My phone was up and running from here. But in case of errors. You might want look down.
IF IT SAYS "FAILED" do not immediately reboot the device If you reboot with a FAIL It could brick! If no flash is being accepted you have to find out what is causing the malfunction before rebooting your phone. Keep it alive while trying to figure out the error. It might be your cable, your USB ports (don’t use hubs! Always direct-mainboard connections), it might be USB 3.0 which is not good yet, it might be bad configuration of your ADB and Fastboot...
The least dangerous FAILED messages are listed below and are safe to reboot (below this section you find CRITICAL errors, please observe):
Safe to reboot / Flash didn't happen Errors (if you encounter one of them, you can just reboot. Nothing changed):
- 12 signature fail (unknown yet but safe to reboot)
- 23 parsing image fail (means something wrong with the image in the zip)
- 24 android-info fail (means something wrong with android-info.txt in the zip)
- 32 header error (means the zip couldn't be read and unzipped properly)
- 41 Wrong Model ID (means it's not the right device)
- 42 Wrong Customer ID (wrong CID means you gotta swap CID first as explained below)
- 90 hboot pre-update (means it only flashed hboot and you have to run the process again immediately to flash all other partitions WITHOUT a reboot in-between).
- 99 UNKNOWN usually indicates you are S-ON, sometimes other Security related issues.
- 130 wrong model ID (seems it's the same like 41, just that it shows in the FUU as 130.
- 155 seems to indicate different things. It can mean: 1.) You need to relock bootloader (If S-ON); 2.) You cannot run the RUU/FUU because the software versions of ROM, Firmware and RUU/FUU don’t match.
- 170 Check USB - FUU won’t run because of not working ADB.
In fact, if it aborts before the "(bootloader) start image[hboot] unzipping & flushing..." line it actually didn't write anything and you can probably just reboot. If you see it flashing stuff though (the stages after that line) and then it stops with a FAILED, chances are a little higher that something is now broken. In that case do NOT reboot but do as i said above.
For Error 12 “signature fail" do:
- might indicate that a signed firmware package is required. This would only happen with S-ON phones though.
For Error 23 "parsing image fail" do:
- change image names in the zip to stock image names like “hboot.img" or “radio.img" or whatever failed there....
For Error 24 "android-info fail" do:
- check that your ZIP isn’t some HTC OTA or anything thats got no android-info.txt - those cannot be flashed with fastboot flash zip nameof.zip command.
- check that your zip has a good MD5 and is not broken, check android-info.txt etc...
For Error 32 "header error" do:
- Sorry i haven’t found the exact cause yet and don’t know a definite solution.
- Make sure there is only one . (dot) in the filename, before the extension. fastboot reads anything after the first dot it sees as the extension. If that is not zip, it fails.
- If that doesn't help, you can also try: make the zip new with recommended settings, re-run the command, check your connections...
For Error 42 "Wrong Customer ID" and: 41 "Wrong Model ID" do:
Code:
htc_fastboot getvar all
Read that output, take note of your CID and MID and then edit the "android-info.txt" in your firmware.zip accordingly (For Wrong MID change the MID in the text, for wrong CID add your CID to the text).
Alternative method for MID and CID errors:
go SuperCID. Do:
Code:
htc_fastboot oem writecid 11111111
You can change back to any desired CID after a successful firmware flash. Notice: this command only works on S-OFF phones (which you have already of course or else you wouldn't be here).
For “Error 90 hboot pre-update..." do:
- Run the same flash command again which you just ran (press arrow up on your keyboard to get to the previous command in console)
- Don’t reboot in-between! (It wouldn't brick you but it would just make you run the flash command twice again)
- This might be caused by the newer encrypted RUU's, they need their hboot to be flashed first so it can then decrypt the rest of the ROM.zip. Look at an encrypted ROM.zip from a RUU, you will notice that you can mostly extract the hboot without decrypting the ROM.zip, but you can't extract much else.)
For “Error 99 UNKNOWN" do:
- Check with other zip’s if they work!
- Check if your S-OFF is correct
- You are S-ON? Then almost definitely this means the ZIP is not signed - get an unmodified zip!
For “Error 130 wrong model ID" do:
- Please refer to Error Code 41/42.
For “Error 155 relock bootloader" do:
- Since my thread works only with S-OFF phones anyway, this error can be read as: you need to S-OFF first!
- Error 155 can mean that you need SuperCID. On a few occasions this was shown when the RUU/FUU refused to run because of a wrong region lock.
- Lately, Error 155 has occurred when a FUU was launched from within android. When encountering a FUU error 155 with the process stalling after the rebootRUU (stuck at black screen with silver HTC logo), please just restart the FUU and leave the phone in that mode, or reboot the phone, then reboot to bootloader, then do “htc_fastboot oem rebootRUU” and then launch the FUU again (thanks @anarchychris for pointing it out).
- run the fastboot command “htc_fastboot oem lock" - only applies to S-ON phones that want to update the firmware with a stock OTA package (not offered on this thread!!). Stock OTA files sometimes need a locked bootloader.
For “Error 170 Check USB" do:
- Sometimes shown when running a RUU or FUU. Indicates issues with drivers. One way to solve is to run the ARUWizard with the phone already in Fastboot mode. Else you will have to re-install HTC Sync manager. Also, avoid USB 3 ports (the blue ones) - they have a complete new driver stack and that doesn't work well currently.
NOT safe to reboot / Flash (partly) happened Errors (if you encounter one of them, DON’T reboot:
- 152 Image Error - Phone Screen shows a little triangle beside a full green bar
For “Error 152 Image Error" do:
- Error 152 is quite rare, have seen it only once with a friend’s phone and it aborted the flash nearly at the end. The flash was started by the FUU. We could resolve the matter by NOT rebooting the phone and flashing the zip again through a manual fastboot flash as outlined further up.
pauluthupm said:
I downloaded the correct version of Marshmallow from Android Ghost : url below.
https://www.androidfilehost.com/?fid=24369303960687057
Click to expand...
Click to collapse
I'm not familiar with Android Ghost. The text looks like its just copy/paste stolen from XDA (which is often what a lot of random "root" or similar websites do).
redpoint73 said:
I'm not familiar with Android Ghost. The text looks like its just copy/paste stolen from XDA (which is often what a lot of random "root" or similar websites do).
Click to expand...
Click to collapse
Yep. That's straight up stolen (copy/pasted) from @Sneakyghost's threads.
EDIT: That's probably who he meant. Just got the name wrong I would guess by looking at the "Android Ghost" name again
xunholyx said:
EDIT: That's probably who he meant. Just got the name wrong I would guess by looking at the "Android Ghost" name again
Click to expand...
Click to collapse
Yeah, hard to tell what OP is talking about, if they don't even get the name right.
Also completely unnecessary of him to clutter up the board by copy and pasting huge amounts of text when a link can be provided (or refer to a thread, if he can't link).
NEW HTC m8 on custom recovery
redpoint73 said:
That RUU won't work, its not for your Euro "401" version, its for the US Developer's Version (1540). You need RUU 6.12.401.4 which can be found in .zip format here (don't know of a source for exe format): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
You also need to relock the bootloader to run the RUU. Instructions to do so, are also included on the link above.
Did you unlock the bootloader to RUU? If so, you have it backwards. RUU requires bootloader LOCKED or RELOCKED. RUU will never run with bootloader unlocked (unless you have s-off, which you don't).
Click to expand...
Click to collapse
--------------------------------------------------------------
Hi redpoint, need your help.
i want to revert my htc m8 to stock marshmallow. i am currently running ,mi ui with twrp recovery.
i am posting getvar results below. i have a firmware with me and few stock recovery files.
FW Name : 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15.720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_release_469495_signed_2_4_gsmdevelopers.com (1)
Is this the right firmware ? i tried flashing few stock recoveries and doesnt work. can you help me ?? can u help me with which firm ware i should download and which stock recovery should i install ?
bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(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
pauluthupm said:
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
Click to expand...
Click to collapse
What's going on here, is this a different phone than what you listed in the first post?
pauluthupm said:
i have a firmware with me and few stock recovery files.
FW Name : 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15.720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_release_469495_signed_2_4_gsmdevelopers.com (1)
Click to expand...
Click to collapse
I can't tell what that is. Its not a valid file name, nor is it a valid link. Also looks like its from some random website "gsmdevelopers.com" (which I am not familiar with) so I have no idea if its a valid/safe file or not.
pauluthupm said:
Is this the right firmware ? i tried flashing few stock recoveries and doesnt work. can you help me ?? 0
Click to expand...
Click to collapse
What exactly did you try to flash (file name and source - describe the thread or obfuscate the link if you need to)?
You understand that a firmware is not a ROM, and a stock recovery is not a ROM?
You need to describe in detail, exactly what steps you have tried. Otherwise, I have no idea what you are trying to do, or how to fix it.
m8 revert to stock
redpoint73 said:
What's going on here, is this a different phone than what you listed in the first post?
Yes it is. This phone is a different device used by my sister.
I can't tell what that is. Its not a valid file name, nor is it a valid link. Also looks like its from some random website "gsmdevelopers.com" (which I am not familiar with) so I have no idea if its a valid/safe file or not.
i too think the same. i used this just to see asian ruu works or not.
What exactly did you try to flash (file name and source - describe the thread or obfuscate the link if you need to)?
First after a lot of reading, i came to knw you cannot ruu with custom recovery installed. for that i need to have stock recovery. Now i have no clue which one to flash. However, i went ahead and flashed 6.20.709.2 stock recovery. Now i tried
flashing that ruu downloaded from gsm developers. but i failed with it.
You understand that a firmware is not a ROM, and a stock recovery is not a ROM?
Being very honest, i have very little knowledge, its a new learning for me. I never knew firmware is not a rom and recovery is not a rom.
You need to describe in detail, exactly what steps you have tried. Otherwise, I have no idea what you are trying to do, or how to fix it.
Click to expand...
Click to collapse
Now to revert back i am trying to find out which ruu i should download?
Now am downloading another ruu from this link : https://www.androidfilehost.com/?fid=24391638059058090
it says : M8_UL_m60_SENSE70_MR_hTc_Asia_Tw_6.20.709.2
My device id belongs to India when i googled hence i m searching for these ruu. I wanted to try sunshine s off so that change the mid and cid to eu version and then try different ruu. Sunshine keeps giving me an error while running the initial tests it requires an non debuggable boot.img. So that doesnt help either.
do you require anymore info ? i can give u remote access if it requires.
PS: MIUI Rom is still working if i want to use my phone
pauluthupm said:
do you require anymore info ? i can give u remote access if it requires.
Click to expand...
Click to collapse
You didn't even provide any of the info I requested in my last post.
All you did was provide yet another link, with no info of how you found it. So I have no idea if its legit, signed, etc. (if its not signed, you can't flash it with s-on).
redpoint73 said:
You didn't even provide any of the info I requested in my last post.
I had answered to your questions right below it. Did u mean i dint answer with details?
All you did was provide yet another link, with no info of how you found it. So I have no idea if its legit, signed, etc. (if its not signed, you can't flash it with s-on).
Click to expand...
Click to collapse
i have No clue how i found it. I googled lot of pages and somehow i found this this link. butyes i downloaded it from http://forum.gsmhosting.com/vbb/f48...-ruu-4-x-x-6-x-x-updated-19-3-2016-a-1940130/
I am not sure its signed or not. to be honest i have no clue.
answers to what you had asked?
redpoint73 said:
You didn't even provide any of the info I requested in my last post.
All you did was provide yet another link, with no info of how you found it. So I have no idea if its legit, signed, etc. (if its not signed, you can't flash it with s-on).
Click to expand...
Click to collapse
Originally Posted by redpoint73
What's going on here, is this a different phone than what you listed in the first post?
Yes it is. This phone is a different device used by my sister.
I can't tell what that is. Its not a valid file name, nor is it a valid link. Also looks like its from some random website "gsmdevelopers.com" (which I am not familiar with) so I have no idea if its a valid/safe file or not.
i too think the same. i used this just to see asian ruu works or not.
What exactly did you try to flash (file name and source - describe the thread or obfuscate the link if you need to)?
First after a lot of reading, i came to knw you cannot ruu with custom recovery installed. for that i need to have stock recovery. Now i have no clue which one to flash. However, i went ahead and flashed 6.20.709.2 stock recovery. Now i tried
flashing that ruu downloaded from gsm developers. but i failed with it.
You understand that a firmware is not a ROM, and a stock recovery is not a ROM?
Being very honest, i have very little knowledge, its a new learning for me. I never knew firmware is not a rom and recovery is not a rom.
pauluthupm said:
First after a lot of reading, i came to knw you cannot ruu with custom recovery installed. for that i need to have stock recovery.
Click to expand...
Click to collapse
This is completely incorrect. You can RUU with custom recovery installed. You only need stock recovery to do an OTA update, which is completely different from an RUU.
pauluthupm said:
Now i tried flashing that ruu downloaded from gsm developers. but i failed with it.
Click to expand...
Click to collapse
How on earth would you ever even flash that? The file name is not an exe or a zip: 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15. 720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_re lease_469495_signed_2_4_gsmdevelopers.com (1)
Did you rename the file? If so, renamed it to what?
Did you try to flash with fastboot, or put on SD card?
When you flashed it, what was the mode of failure (what were the results, specific error messages, etc.)?
How big is the file (MB)?
---------- Post added at 10:58 AM ---------- Previous post was at 10:51 AM ----------
pauluthupm said:
Now to revert back i am trying to find out which ruu i should download?
Now am downloading another ruu from this link : https://www.androidfilehost.com/?fid=24391638059058090
it says : M8_UL_m60_SENSE70_MR_hTc_Asia_Tw_6.20.709.2
Click to expand...
Click to collapse
That RUU won't work (wrong CID and MID). You need a RUU that has version number"720" , not 709.
The number in the position x.xx.720.xx specifically refer to your version M8 (CID and MID).
EDIT: fixed a typo, the number in red in the last line should read 720.
redpoint73 said:
You didn't even provide any of the info I requested in my last post.
All you did was provide yet another link, with no info of how you found it. So I have no idea if its legit, signed, etc. (if its not signed, you can't flash it with s-on).
Click to expand...
Click to collapse
redpoint73 said:
This is completely incorrect. You can RUU with custom recovery installed. You only need stock recovery to do an OTA update, which is completely different from an RUU.
How on earth would you ever even flash that? The file name is not an exe or a zip: 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15. 720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_re lease_469495_signed_2_4_gsmdevelopers.com (1)
HTML:
[QUOTE]Yes i renamed it to 0P6BIMG.zip
[/QUOTE]
Did you rename the file? If so, renamed it to what?
Did you try to flash with fastboot, or put on SD card?
htc_fastboot oem lock
then htc_fastboot oem rebootRUU
then htc_fastboot flash zip filename.zip
When you flashed it, what was the mode of failure (what were the results, specific error messages, etc.)?
remote: 12 signature verify fail)
Execution time is 115(s)
Click to expand...
Click to collapse
How big is the file (MB)?
1.66 GB
---------- Post added at 10:58 AM ---------- Previous post was at 10:51 AM ----------
That RUU won't work (wrong CID and MID). You need a RUU that has version number"720" , not 709.
The number in the position x.xx.709.xx specifically refer to your version M8 (CID and MID).
Click to expand...
Click to collapse
Can you help me with the link i should download ? the correct ruu for my m8 ?
i can post the getvar values here if its of any help.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(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
Click to expand...
Click to collapse
pauluthupm said:
Yes i renamed it to 0P6BIMG.zip
htc_fastboot oem lock
then htc_fastboot oem rebootRUU
then htc_fastboot flash zip filename.zip
Click to expand...
Click to collapse
So the command you used was actually as follows? htc_fastboot flash zip 0P6BIMG.zip
Is so please next time be sure to tell us the actual exact command you used, not just cut/paste from instructions or whatever.
Is the bootloader currently LOCKED or UNLOCKED?
Are you the one that unlocked the bootloader, put custom recovery, and MIUI ROM on it?
redpoint73 said:
So the command you used was actually as follows? htc_fastboot flash zip 0P6BIMG.zip
Is so please next time be sure to tell us the actual exact command you used, not just cut/paste from instructions or whatever.
Is the bootloader currently LOCKED or UNLOCKED?
Bootloader is currently unlocked. Since you said i can run ruu in custom recovery also. I went and reinstalled custom recovery twrp 2.7 from Hasoons All in one Kit.
Are you the one that unlocked the bootloader, put custom recovery, and MIUI ROM on it?
Click to expand...
Click to collapse
Yes am the one who unlocked the boot loader and put MIUI on it.
I just need to add, i tried wipe dalvik cache, and factory wiped thru twrp. And the mi ui still boots with out any issues.
Sorry if you felt i copy pasted, it not . I am multi tasking between my office and phone. Apologies if i did sound so.
pauluthupm said:
Yes am the one who unlocked the boot loader and put MIUI on it.
I just need to add, i tried wipe dalvik cache, and factory wiped thru twrp. And the mi ui still boots with out any issues.
Sorry if you felt i copy pasted, it not . I am multi tasking between my office and phone. Apologies if i did sound so.
Click to expand...
Click to collapse
Sorry to bug you so much: does this ruu sounds correct?
0P6BIMG_M8_UL_K44_SENSE60_SECURITY_hTC_Asia_TW_1.54.709.4_R_Radio_1.15.2133156.UA14G_20.18n.4096.05_release_358414_signed_2_4.zip
Also, i wanted to tell if i try to relock the bootloader this is the msg i get.
htc_fastboot oem lock
... (bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [ERR] Cannot halt SPMI arbiter!!
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
Execution time is 1(s)
Click to expand...
Click to collapse
Bt when the phone reboots, i get msg " RELOCKED" in PInk COLOUR
pauluthupm said:
Yes am the one who unlocked the boot loader and put MIUI on it.
Click to expand...
Click to collapse
pauluthupm said:
Being very honest, i have very little knowledge, its a new learning for me.
Click to expand...
Click to collapse
Okay, one really important point I need to make: One should absolutely be sure to research and learn, and understand all the processes before modding any phone.
In particular, you shouldn't be modding the phone, without knowing how to return it to stock. You should always have an "escape" strategy to revert the changes you make, return to stock, etc.
Did you make a TWRP backup before flashing a custom ROM? You should always do this, its just basic good practice when modding phones. If you had done so, you would have an easy way to restore the stock, unrooted ROM.
---------- Post added at 12:17 PM ---------- Previous post was at 12:10 PM ----------
pauluthupm said:
Sorry to bug you so much: does this ruu sounds correct?
0P6BIMG_M8_UL_K44_SENSE60_SECURITY_hTC_Asia_TW_1.54.709.4_R_Radio_1.15.2133156.UA14G_20.18n.4096.05_release_358414_signed_2_4.zip
Click to expand...
Click to collapse
It won't work. You need version numbers with 720, not 709.
I see in my last post, I said you needed 720 (which is correct) then a typo which implies you need 709 (not correct). So there may have been some confusion or conflicting info there.
Also, that version is too old (software number 1.54). You can only run RUU with equal or greater version than the firmware on the phone, which in your case is 4.xx.
pauluthupm said:
]
Also, i wanted to tell if i try to relock the bootloader this is the msg i get.
Bt when the phone reboots, i get msg " RELOCKED" in PInk COLOUR
Click to expand...
Click to collapse
RELOCKED is the important part. Not sure why you got in error , but it looks to be properly relocked to run RUU.
Was it RELOCKED or UNLOCKED when you tried the RUU 6.20.709.2 and got Error 12: Signature Error?
redpoint73 said:
Okay, one really important point I need to make: One should absolutely be sure to research and learn, and understand all the processes before modding any phone.
I should have. Now i regret for messing up the phone
Click to expand...
Click to collapse
In particular, you shouldn't be modding the phone, without knowing how to return it to stock. You should always have an "escape" strategy to revert the changes you make, return to stock, etc.
Absolutely learned it. I wouldnt want mod any phones anymore. Too much of headache, since am i am noob.
Click to expand...
Click to collapse
Did you make a TWRP backup before flashing a custom ROM? You should always do this, its just basic good practice when modding phones. If you had done so, you would have an easy way to restore the stock, unrooted ROM.
Click to expand...
Click to collapse
In fact i did have twrp back up. bt i had kept this sd card in my wallet. I broke the sd card by mistake. thats how i lost it.
OP cannot install RUU 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15. 720.2 on his current firmware version.
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038He needs to install the signed 6.15.720.2 firmware first before install the RUU zip
Easier method is - install RUU_M8_UHL_L50_SENSE60_MR_hTC_Asia_India_4.18.720.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_417228_signed.exe
Download from : http://androidruu.com/?developer=M8
then OTA to 4.18.720.10 then later to 6.15.720.2
Or restore 4.18.720.10 backup & install 4.18.720.10 stock recovery (yeah .. skip a version) then OTA to 6.15.720.2
Download from : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Good luck
Hi, I made this post in the Sprint section a few days ago, but figured I'd post here as well to see if maybe this section has more traffic. If that's not allowed, I apologize in advance.
https://forum.xda-developers.com/sprint-htc-one-m8/help/stock-roms-t3669676
Basically, I'm looking for a stock rom for Sprint that would work with 1.54.651.8 firmware. All the links I can find on the forums seem to be dead.
Alternatively, a nandroid backup or way to extract the rom from the 1.54.651.8 RUU I do have (but won't successfully flash for whatever reason)
Any help would be appreciated. Thanks!
A custom ROM would need to support the Sprint M8, and be based on 4.4.2. Most any newer (newer than KitKat) ROMs will suffer major incompatibility with your ancient firmware, including extreme long boot time or no boot, and broken WiFi.
Suggest stocking with updating the firmware. Is the device s-on or s-off?
Problems with the RUU while "sending" are usually on the PC side. Try to re-install HTC drivers, try another USB port (USB 2.0 works best), and try another cable. Or even try another PC if possible.
Yeah I was able to find one custom 4.4.4 ROM (It was labelled 4.4.2, but it works so I guess it's close enough). There are just a few issues with it and I've always been more of a stock person anyway so I'd rather use a stock rom if I have the option.
As far as updating firmware, I am S-ON - I only originally rooted for a wifi hotspot app, so I didn't have a need to go S-OFF.
I guess it wouldn't hurt to give the RUUs a shot on a different computer. I'll just have to talk a friend into letting me install the drivers and giving it a go. One thing I'm not sure about - is it safe to go straight to the lastest RUU on HTC's site? I was willing to try it back when I had no rom at all, but now that I have a custom rom that mostly works, I'd rather not totally crap the bed.
Fuhcue said:
I guess it wouldn't hurt to give the RUUs a shot on a different computer. I'll just have to talk a friend into letting me install the drivers and giving it a go. One thing I'm not sure about - is it safe to go straight to the lastest RUU on HTC's site?
Click to expand...
Click to collapse
You can "skip" RUUs, and go the latest. However, you may (probably) need to update to the Marshmallow firmware anyway, before you can RUU. There is a strange limitation on most US version M8, where the RUU will fail with Error 155, if you try to go to Marshmallow from any former version (be it Kitkat or Lollipop) without first updating the firmware.
So the steps would be:
1) Relock bootloader
2) Flash to Marshmallow signed firmware (Sprint), in fastbootRUU mode
3) RUU to Marshmallow
4) Unlock bootloader again
5) Flash TWRP, root, and do whatever mods you want
Seeing as RUU will also wipe the phone. All this might be more than you want to do, if you are fairly happy with the phone as it is.
redpoint73 said:
Seeing as RUU will also wipe the phone. All this might be more than you want to do, if you are fairly happy with the phone as it is.
Click to expand...
Click to collapse
I don't so much mind the wipe, but I am a bit nervous about updating the firmware since that sounds like it could leave me in limbo if the RUU still didn't want to work for whatever reason. I guess I'll search around for where I can get that firmware and the procedure of how to do it and see how comfortable I feel with it in case I go that route.
If I knew for sure that it would all go through, I'd be fine with the reset. But that seems to take the attractive part of the RUU away in that it's no longer an "all in one" or one step process. (Not counting unlocking/relocking the bootloader since that's a quick and easy thing).
Fuhcue said:
I guess I'll search around for where I can get that firmware and the procedure of how to do it and see how comfortable I feel with it in case I go that route.
Click to expand...
Click to collapse
The firmware is posted in the same thread as the RUUs. And instructions on how to flash, as well.
https://forum.xda-developers.com/showthread.php?t=2729173
Fuhcue said:
If I knew for sure that it would all go through, I'd be fine with the reset. But that seems to take the attractive part of the RUU away in that it's no longer an "all in one" or one step process. (Not counting unlocking/relocking the bootloader since that's a quick and easy thing).
Click to expand...
Click to collapse
You can also opt for the Lollipop RUU (does not require flashing the firmware first). While not the latest, it's obviously more updated than what you presently have. And most of the current MM ROMs should work with LP firmware. There isn't much difference in the firmware it seems, for LP versus MM. Much different from KK to LP, which causes the problems I mentioned earlier (if you try to run KK firmware with LP or MM ROMs).
For maximum compatibility, matching the firmware is usually best. But I was running LP firmware with MM ROMs for a while (was simply to lazy to flash the MM firmware or RUU).
Ok so it sounds like the easiest option for me at this point is to grab a Lollipop RUU and try to flash it from a new computer with a fresh install of all the drivers. That way, at least if it fails to recognize my phone like the newest one did, I'll still be where I currently am with the stock (though outdated) firmware and custom rom.
Otherwise, I'll keep my fingers crossed that someone stumbles across this thread that has a meticulous archive of all old stock Sprint roms
Thanks so much for all your help and answering my questions so quickly. Much appreciated.
Hi
This is Sudheer from INDIA
i got Sprint HTC one M8 Harman Kardon from my friend.
after jail break it's supported Indian GSM sims there after only outgoing calls are working incoming calls are not working.
after so much of web search i unlock boot loader using HTC All in one and i enter into twrp wipe all system,cache and data. now its' hang on startup white screen not booting. yesterday i am trying to install os from following reference.
forum.xda-developers.com/showthread.php?t=2729173
finally i got 155 error Unsupported RUU. Please help me to come out with step by step guide because i am new for installing android phones.
Krishna Sudheer said:
after jail break it's supported Indian GSM sims there after only outgoing calls are working incoming calls are not working.
Click to expand...
Click to collapse
"Jail break" is a term specific to only iPhones. There is not such thing as "jail break" on an Android device. I assume you mean s-off, or some other mod? I can only guess, if you don't use the specific and proper terminology.
Krishna Sudheer said:
after so much of web search i unlock boot loader using HTC All in one and i enter into twrp wipe all system,cache and data. now its' hang on startup white screen not booting.
Click to expand...
Click to collapse
All in one Toolkit is obsolete, you shouldn't be using it. It contains a very old version of TWRP which will cause problems for many folks.
System partition is the OS/ROM. Should be obvious, that wiping the system partition results in no OS. Can't boot to an OS that isn't there any more. If you didn't know what the result would be from wiping a partition, you should be touching it in the first place!!!! Those options are listed under "Advanced" for a reason. If you aren't an advanced user, don't mess with them, unless you are following directions form an experienced user, or know what the result is going to be.
Krishna Sudheer said:
forum.xda-developers.com/showthread.php?t=2729173
finally i got 155 error Unsupported RUU. Please help me to come out with step by step guide because i am new for installing android phones.
Click to expand...
Click to collapse
Not enough info to know why the RUU failed. You linked a post with multiple RUUs, so we don't know which one you tried. We also don't know your current phone configuration.
Which version number RUU did you try? For HK version, you typically will need to flash the one that contains the digits "654". The RUU with digits "651" is for non-HK Sprint version. Assuming CID/MID has not been modified (which we don't know, if you don't provide more info).
Post specific info about your phone. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
If the phone is s-on, you need to lock it in order to RUU. I don't know if you are s-on of s--off.
You can't run a lower number (downgrade) RUU unless you have s-off. Again, I don't know what version number RUU you tried, your current version number on the phone, or whether you are s-on or s-off.
Hi Sir,
Thank you for replying. Sim Unlocked from mobile store. actually I also don't know witch method they are using to unlock. After unlocking network signals showing in GSM mode. When I am changing to LTE mode again signals disappeared. In GSM mode incoming calls are not working. SMS both incoming and outgoing working fine.
I tried to change CID and s-off but it's not working.
TWRP I used version v2.7.0.2 these recovery installed from all in one twrp (sprint). when i come back in to bootloader it will asking No OS installed are you sure you wish to reboot?
My mobile model is HTC one M8 HK (831C) Sprint Internal storage is 32GB.
I download and used to flash following files.
1. signed_6.20.654.3_firmware.zip
2.RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe
3.0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip
What was I do is
First Re-locked bootloader using with all in one and rename firmware as 0P6BIMG.ZIP then flash from SD Card Installed Successfully. Bootloader also showing OS version 6.20.654.3
Next using exe file "RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe" everything going well when the process bar reaching to 100% then it's showing error 155. I Checked the error guide provide by exe file there Unsupported RUU please try again with supported RUU.
Next using with ZIP file "0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip" flash from SD Card it will showing not enough memory but internal is full empty.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(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:
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
Kindly check and do the needful. Let me know how to install OS and where witch rom I use to install.
My responses below in red font:
Krishna Sudheer said:
After unlocking network signals showing in GSM mode. When I am changing to LTE mode again signals disappeared. In GSM mode incoming calls are not working. SMS both incoming and outgoing working fine.
LTE is difficult (maybe impossible) to get working in cases where the device is not intended for your region/carrier (which I assume is the case, that you are not located in US, on the Sprint carrier). GSM should work (as you indicated) as well as 3G (HSPA) provided that your carrier uses a band(s) supported by the Sprint version M8
I tried to change CID and s-off but it's not working. I don't know what that means "it's not working". Most folks who say they have trouble with getting s-off, are trying the hopeless waste of time, which is trying to usethe long obsolete "free" s-off method of firewater. It's never going to work.
Also, you should also be careful here, when changing CID. Only use a Sprint CID, or SuperCID with a Sprint firmware/RUU. Trying to use any other firmware or RUU will result in a radio brick (possibly permanent).
TWRP I used version v2.7.0.2 these recovery installed from all in one twrp (sprint). when i come back in to bootloader it will asking No OS installed are you sure you wish to reboot? That version is too old (over 4 years) and you should have used current TWRP. This was probably caused by using the toolkit (which I mentioned is not advised anymore). Old versions of TWRP was not compatible with Sprint M8 (it had it's own "CDMA" version TWRP) and it probably caused the wrong partition to be overwritten.
What was I do is
First Re-locked bootloader using with all in one and rename firmware as 0P6BIMG.ZIP then flash from SD Card Installed Successfully. Bootloader also showing OS version 6.20.654.3 Try flashing firmware again, the number should show up in getvar all (below) under "version-main". Flashing firmware twice is usually a good idea.
Next using exe file "RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe" everything going well when the process bar reaching to 100% then it's showing error 155. I Checked the error guide provide by exe file there Unsupported RUU please try again with supported RUU.
Error 155 is common, if flashing a US Marshmallow RUU, without being on the matching firmware. Flashing firmware again, as indicated above, may solve it.
Next using with ZIP file "0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip" flash from SD Card it will showing not enough memory but internal is full empty.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: firmware number should appear here
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
Click to expand...
Click to collapse
Hello everyone,
I'd want to sell my HTC One M8, unlocked, with recovery and with a custom ROM. I'd want to return to stock (just flash the old firmware, without lock the bootloader).
How can I flash the old original firmware (maybe no-brand firmware)?
Thank you
First, I suggest you avoid using the word "firmware" the way you are. On this device, there is a package specifically named "firmware.zip" which is a small zip (around 80 MB) that contains a few partitions necessary for the ROM to work (hboot, kernel, radio, etc.) but does not actually contain the stock ROM itself (which is much larger, about 1.5 GB).
In fact, taken literally, flashing the stock firmware (with s-on) without then flashing RUU or ROM, will render the phone unable to boot to OS.
If you mean stock ROM, say stock ROM. If you mean RUU, say RUU.
You can restore a stock TWRP backup (stock ROM) and flash stock recovery to the device (without relocking the bootloader). But if there is an RUU available for your version, it's probably easier (and a better idea) to relock bootloader and RUU back to full stock.
In any case, it's probably not a good idea to sell the phone with the bootloader unlocked, unless the buyer is specifically asking for that (and aware what that means). Leaving it unlocked, leaves them vulnerable to a variety of issues, which they may not be remotely aware of. Most folks are not tech savvy, and will have no idea what an unlocked bootloader even means.
If you want more help (finding the right TWRP backup, RUU, etc.) do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
@redpoint73 Thank you for your satisfactory answer.
So, I would want to lock bootloader and then flash a RUU.
This are the results:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: yyy
(bootloader) imei: xxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: TIM__401
(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: e2b942c6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I've found, on my backup hard disk, three files:
3.31.901.9_ckpv5.zip (with relative recovery.img) (info in attached image)
4.20.901.3_ckpv5.zip (with relative recovery.img) (info in attached image)
2.22.901.5_firmware.zip (with relative recovery.img) related to 4.4.3 - TIM__401
Could they be useful?
Thank you very much.
.Fè said:
I've found, on my backup hard disk, three files:
3.31.901.9_ckpv5.zip (with relative recovery.img) (info in attached image)
4.20.901.3_ckpv5.zip (with relative recovery.img) (info in attached image)
2.22.901.5_firmware.zip (with relative recovery.img) related to 4.4.3 - TIM__401
Click to expand...
Click to collapse
EDIT: The first 2 files you listed are TWRP backups. You can restore the backup 4.20.901.3 using the instruction listed here: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
The firmware file, as mentioned before, is not a full RUU or ROM, and will result in no boot.
redpoint73 said:
You should be able to relock the bootloader, and flash the 4.20.901.3 RUU.
3.31.901.9 will likely fail due to being a lower version number than what is on the phone (can deduce from the current radio baseband number, that the current OS number is probably 4.20.901.3). And you can't flash a lower version RUU ("downgrade") with s-on.
The firmware file, as mentioned before, is not a full RUU or ROM, and will result in no boot.
Click to expand...
Click to collapse
Thanks!
So, how can I flash the 4.20.901.3 RUU?
Thank you.
Actually, looking at the files in your screenshot, I realize those are not RUUs. They are TWRP backups.
I don't know if your version has RUU.
So you can restore the TWRP stock backup that you have (4.20.901.3 as I stated before is still correct) using the instructions in the following thread: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You can also restore stock recovery 4.20.901.4, which you can download from Post #4 of the same thread.
Do not relock the bootloader in this case. I don't know if there is a way to revert to locked/relocked bootloader, and have a working phone, since there is no RUU for your version M8, that I know of. So it would be best to inform prospective buyers that the bootloader is unlocked.
My apologies for any confusion there. I've edited my previous post, to avoid any confusion by others reading this thread.
redpoint73 said:
Actually, looking at the files in your screenshot, I realize those are not RUUs. They are TWRP backups.
I don't know if your version has RUU.
So you can restore the TWRP stock backup that you have (4.20.901.3 as I stated before is still correct) using the instructions in the following thread: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You can also restore stock recovery 4.20.901.4, which you can download from Post #4 of the same thread.
Do not relock the bootloader in this case. I don't know if there is a way to revert to locked/relocked bootloader, and have a working phone, since there is no RUU for your version M8, that I know of. So it would be best to inform prospective buyers that the bootloader is unlocked.
My apologies for any confusion there. I've edited my previous post, to avoid any confusion by others reading this thread.
Click to expand...
Click to collapse
Ok, I will use TWRP to install my stock backup.
I would want to know if it could be possible to flash a no-brand RUU, instead of the stock one? Thank you.
.Fè said:
I would want to know if it could be possible to flash a no-brand RUU, instead of the stock one? Thank you.
Click to expand...
Click to collapse
No, it's not possible to flash an RUU intended for another version M8 (another CID) unless you get s-off (need s-off to change the CID). And the only working method to get s-off is by sunshine ($25 US), and it's not worth spending money on a phone you are trying to sell.
Doing a quick Google search, there is an RUU 4.20.901.4, but you have to pay money to download it. Again, not worth it. Use the TWRP backup approach, as already described.
Hey everyone!
I just got HTC M8 from a friend, and figured out it is a demo unit. It comes with a demo app, which I am unable to get rid off. It was firstly rooted and mistakenly I removed the internal storage. After all the mayhem, researching for hours on this forum, I am finally able to get my device back running but still the demo app is there. I am unable to make any changes in developer options or through control center. I am new to all modding, HTC, Android and custom / stock roms.
I have few questions after reading a lot. After accidentally deleting the OS, and wiping internal memory - I was able to get it back, but now wants to run a custom ROM on it but not sure if I am able to do it with current status of my device.
Information about device:
HBoot: 3.16.000
S-ON
HTC__002
Unlocked Bootloader
TWRP installed (but throws error whenever I try flashing a zip file)
The question: Can I install a custom rom without getting S-OFF and if yes, which custom ROM can I use on my device? I understand there is some limitation to HBoot version, but I am unable to figure out how to update it to latest version. I would like to update my device from Android Kitkat to Marshmallow or some custom ROM which doesn't have a demo app.
P.S: A noob!
Update:
After reading lots of threads, I finally bought Sunshine license and activated S-OFF, now, I am with SuperCID 11111111 on my demo unit. Now, I want know about which Custom ROM I can run, and how can I update my Hboot to latest version?
You can use this ROM
https://forum.xda-developers.com/htc-one-m8/development/rom-resurrection-remix-v5-8-0-t3507210
Follow the directions there and you will be all right.
If you still need help contact me on :
[email protected]
HamzaSheikh said:
[*]HBoot: 3.16.000
[*]TWRP installed (but throws error whenever I try flashing a zip file)
Click to expand...
Click to collapse
Might help, if you tell us what error message TWRP gives you.
Hboot version is too old to flash most ROMs. Also, such an old hboot version, is not compatible with many TWRP versions (might be the reason zip won't flash in TWRP).
What TWRP version?
Do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
I believe @ckpv5 knows some about how to get the demo versions working or modded. The demo versions pops up infrequently enough, I can't remember the exact details.
---------- Post added at 03:39 PM ---------- Previous post was at 03:38 PM ----------
Hero_elmehrik22 said:
You can use this ROM
https://forum.xda-developers.com/htc-one-m8/development/rom-resurrection-remix-v5-8-0-t3507210
Follow the directions there and you will be all right.
Click to expand...
Click to collapse
He says TWRP gives an error flashing zips. So how is he supposed to install that ROM?
Most likely, his Hboot version is too old to support that ROM.
Yes, Hboot version is too old. I had a long fight with getting it restored. I had to try every other TWRP version and suddenly TWRP 2.8.0.0 worked for me!
Here is the output from getvar all:
Hamzas-iMac:~ hamza$ fastboot getvar all
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: removed
(bootloader) imei: removed
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(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: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.203s
Click to expand...
Click to collapse
Problem I face:
- Current TWRP is old, I am unable to make most out of it. (v2.8.0.0)
- Hboot is like hanging in stone age, I need to update it - but I have a demo unit (it comes with annoying demo app!)
- I want to run Custom ROM or at least a newer Android version.
redpoint73 said:
Might help, if you tell us what error message TWRP gives you.
Hboot version is too old to flash most ROMs. Also, such an old hboot version, is not compatible with many TWRP versions (might be the reason zip won't flash in TWRP).
What TWRP version?
Do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
I believe @ckpv5 knows some about how to get the demo versions working or modded. The demo versions pops up infrequently enough, I can't remember the exact details.
---------- Post added at 03:39 PM ---------- Previous post was at 03:38 PM ----------
He says TWRP gives an error flashing zips. So how is he supposed to install that ROM?
Most likely, his Hboot version is too old to support that ROM.
Click to expand...
Click to collapse
You should be able to disable the demo app, using the "alternative method" indicated in the following post: https://forum.xda-developers.com/showpost.php?p=59735868&postcount=10
You can update to a newer version using the RUU and instructions on the following post. You will need to relock the bootloader in order to RUU: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Be aware that RUU will wipe all data on the phone! Again, you will need to disable the demo app if you intend to stay on the Marshmallow "stock" ROM.
Updating to newer version (Marshmallow) by RUU, will also update the hboot, and other firmware (radio, WiFi, etc.). So after that you should be able to use the current version TWRP (3.1) and the current custom ROMs. Again, I'm not 100% knowledgeable on the demo model. But I don't see how the demo version CID (which is what triggers the demo app) would prevent you from doing the above. Especially if you disable the demo app, or flash a custom ROM (non-Sense) that doesn't have the demo app to begin with.
Thanks @redpoint73 for the help. Here is an update:
I finally able to get rid of demo app using SuperCID - means, now I have S-OFF device. I used Sunshine apk. Now I would like to update my device to latest Android (Marshmallow) - so should I follow the instructions on the thread you pointed me or is there something else I can try instead of locking the bootloader again?
redpoint73 said:
You should be able to disable the demo app, using the "alternative method" indicated in the following post: https://forum.xda-developers.com/showpost.php?p=59735868&postcount=10
You can update to a newer version using the RUU and instructions on the following post. You will need to relock the bootloader in order to RUU: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Be aware that RUU will wipe all data on the phone! Again, you will need to disable the demo app if you intend to stay on the Marshmallow "stock" ROM.
Updating to newer version (Marshmallow) by RUU, will also update the hboot, and other firmware (radio, WiFi, etc.). So after that you should be able to use the current version TWRP (3.1) and the current custom ROMs. Again, I'm not 100% knowledgeable on the demo model. But I don't see how the demo version CID (which is what triggers the demo app) would prevent you from doing the above. Especially if you disable the demo app, or flash a custom ROM (non-Sense) that doesn't have the demo app to begin with.
Click to expand...
Click to collapse
Meanwhile, I tried following the details on thread and got myself stuck on error:
FAILED (remote: 32 header error)
Whenever I try to flash the RUU, it gives this error!
redpoint73 said:
You should be able to disable the demo app, using the "alternative method" indicated in the following post: https://forum.xda-developers.com/showpost.php?p=59735868&postcount=10
You can update to a newer version using the RUU and instructions on the following post. You will need to relock the bootloader in order to RUU: https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Be aware that RUU will wipe all data on the phone! Again, you will need to disable the demo app if you intend to stay on the Marshmallow "stock" ROM.
Updating to newer version (Marshmallow) by RUU, will also update the hboot, and other firmware (radio, WiFi, etc.). So after that you should be able to use the current version TWRP (3.1) and the current custom ROMs. Again, I'm not 100% knowledgeable on the demo model. But I don't see how the demo version CID (which is what triggers the demo app) would prevent you from doing the above. Especially if you disable the demo app, or flash a custom ROM (non-Sense) that doesn't have the demo app to begin with.
Click to expand...
Click to collapse
HamzaSheikh said:
Meanwhile, I tried following the details on thread and got myself stuck on error:
FAILED (remote: 32 header error)
Whenever I try to flash the RUU, it gives this error!
Click to expand...
Click to collapse
1. No need to relock bootloader as you already S-Off your device
2. You got error because you don't use htc_fastboot as in the instructions.
Lots of love man! I finally got it. It worked like a charm through HTC_fastboot.exe. I was on macOS earlier and tried flashing ruu.zip through it, but after your message. I tried on Windows with HTC fastboot and wow!
I did a small mess and eventually relocked my bootloader! No issues with that, I can re-unlock it!
Thanks @ckpv5 for the final tip, and lots of love for @redpoint73 for pointing me at right direction!
Latest Getvar All:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: removed
(bootloader) imei: removed
(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!
Anything else I should be doing to make it work awesome and fast?
ckpv5 said:
1. No need to relock bootloader as you already S-Off your device
2. You got error because you don't use htc_fastboot as in the instructions.
Click to expand...
Click to collapse
HamzaSheikh said:
I did a small mess and eventually relocked my bootloader! No issues with that, I can re-unlock it!
Click to expand...
Click to collapse
Honest mistake. Relocking the bootloader is mandatory to run an RUU with s-on. So it's easy to miss the fact that the requirement (to relock the bootloader to RUU) is bypassed with s-off.
As you said, you can always unlock the bootloader again, if you want to install custom recovery, root, flash custom ROM, etc. Alternately, if you want to stay stock with no root, you can just leave it relocked.
HamzaSheikh said:
Thanks @ckpv5 for the final tip, and lots of love for @redpoint73 for pointing me at right direction!
Click to expand...
Click to collapse
You're very welcome. I wasn't sure if you wanted to pay for sunshine, so that is why I was suggesting some possible solutions with s-on. But glad to have pointed you in the right direction, regardless.
HamzaSheikh said:
Thanks [MENTION=830797]
Anything else I should be doing to make it work awesome and fast?
Click to expand...
Click to collapse
That is a very open-ended and subjective question. It's completely up to your preference, if you want to do any more mods. You can try custom ROMs, root, custom kernels, and much more. There really isn't much limit on what you can try.