Hi,
A few weeks ago my M8 developed a serious problem - basically all calling functionality stopped working. The android basic dialer get's stuck dialing a number and eventually the system presents the standard 'Dialer is not responding' message, calling my number from another phone always gets an engaged tone, Skype and Whatsapp calling fails without any error messages. Also data connection fails, text messaging fails intermittently, music player fails to play through speakers and fails intermittently through Bluetooth.
This didn't occur after the install of any apps and the phone didn't experience any physical shocks, but seemed to happen after a Skype call.
Naturally, I tried factory reset first, but to no avail.
As the phone is now out of warranty I rooted it and installed the Android Revolution ROM onto it. (PS thanks to everyone for the wealth of help and guides to carrying this out.) I was hoping a new ROM would fix the problem, but it hasn't.
So, I'm assuming the problem is at a very low level, with some device driver(s).
My question is, does the ROM include all of the device drivers? Do I need to do something else to get the basic device drivers reinstalled? I note the download site for the Android Revolution ROM also has links to firmware downloads - should I also install the firmware download?
Any help would be much appreciated.
usmhot
I'd try RUU, if you M8 version has one. Otherwise, yes, I'd try to flash firmware, than re-install stock or custom ROM onto the phone. I don't think the AR firmware collection is very current. I'd use the stock, signed firmwares from ckpv5's thread (post #5): https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
If you need help determining if your version has RUU, or what firmware number to use, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
redpoint73 said:
I'd try RUU, if you M8 version has one. Otherwise, yes, I'd try to flash firmware, than re-install stock or custom ROM onto the phone. I don't think the AR firmware collection is very current. I'd use the stock, signed firmwares from ckpv5's thread (post #5): https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
If you need help determining if your version has RUU, or what firmware number to use, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
Mine's an Irish (so I assume international) variant - so I'm not sure if there's an RUU available (some google result seemed to imply HTC only release RUUs for the States??)
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.29.214500021.12G
version-cpld: None
version-microp: None
version-main: 6.13.771.4
version-misc: PVT SHIP S-ON
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: H3G__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 76df2b54
hbootpreupdate: 11
gencheckpt: 0
Bump. Can anyone tell me if there is an RUU available for my variant?
usmhot said:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.29.214500021.12G
version-cpld: None
version-microp: None
version-main: 6.13.771.4
version-misc: PVT SHIP S-ON
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: H3G__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 76df2b54
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
usmhot said:
Mine's an Irish (so I assume international) variant - so I'm not sure if there's an RUU available (some google result seemed to imply HTC only release RUUs for the States??)
Click to expand...
Click to collapse
Some other versions (besides US) have RUU, but unfortunately I don't think your version (H3G) is one of those.
One idea, which I touched upon before, is to flash the firmware (since you don't think flashing the ROM alone won't help - the firmware is basically the "lower level drivers" you are talking about), then restore a stock TWRP backup (ROM). Its as close to a RUU "factory image" as you'll get, since there is no RUU (that I am aware of).
To do this, you'll need to relock the bootloader, and flash the 6.13.771.4 from Post #5 of the following thread:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Then you'll need to unlock the bootloader again, install TWRP back to the phone (flashing the firmware overwrites TWRP with stock recovery). Then flash the stock TWRP backup 6.13.771.4 from Post #3 of the same thread, using instructions in Post #1.
redpoint73 said:
To do this, you'll need to relock the bootloader, and flash the 6.13.771.4 from Post #5 of the following thread:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Then you'll need to unlock the bootloader again, install TWRP back to the phone (flashing the firmware overwrites TWRP with stock recovery). Then flash the stock TWRP backup 6.13.771.4 from Post #3 of the same thread, using instructions in Post #1.
Click to expand...
Click to collapse
I've had a go at relocking the bootloader following the instructions in http://www.droidviews.com/how-to-reset-unlocked-status-to-locked-on-htc-one-m8/
i.e. using the following sequence of commands
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
exit
exit
Click to expand...
Click to collapse
but it's not working for me - it still shows as *** Unlocked ***
Couple of things:
1. if I issue the command adb devices (after a full reboot to system) first I get an error message "adb server version (31) doesn't match this client (36)" and my device id is listed anyway, but if I reissue the command I get my device id listed without the error. Do I need a different version of adb?
2. do I need to unroot as well as relock? (If so, is there a guide somewhere?)
usmhot said:
I've had a go at relocking the bootloader following the instructions in http://www.droidviews.com/how-to-reset-unlocked-status-to-locked-on-htc-one-m8/
Click to expand...
Click to collapse
You're making much harder on yourself than need be.
The process to relock the bootloader is in the instructions for flashing the firmware, which I already directed you to (Post #5 of the previously linked thread). Near the bottom of that post, below all the download links (so maybe you missed seeing the instructions).
Relocking the bootloader is a single, easy fastboot command:
fastboot oem lock
This will make the bootloader say RELOCKED, which is sufficient to flash the firmware.
The guide you linked is to make it say LOCKED (versus RELOCKED) and the only reason to do that is to fool HTC into thinking it was never UNLOCKED for warranty purposes. You don't need to do this, and you can't since the guide clearly says s-off is required, which you do not have (you are s-on).
Sorted :good:. And it did indeed fix the core problem with the dialer etc. I know have an apparently fully working phone again.
Many many thanks for this.
usmhot said:
Sorted :good:. And it did indeed fix the core problem with the dialer etc. I know have an apparently fully working phone again.
Many many thanks for this.
Click to expand...
Click to collapse
Glad it worked. You're quite welcome, and happy to have helped!
Related
Hello, I've been a long time xda lurker (Never thought I could really add much anyhow) since I had my Dell Streak and I think for the first time since I got my M8 I need a bit of help.
They rolled out the lollypop OTA update here in Ireland and figured It was time to update to a stock ROM from here or a slightly improved one but ever since then I have lost my WiFi completely.
Sorry If this makes no seance- at all I'm a little burnt out trying to solve this on my own but even going back to 4.4.3 ROMs I still have no WiFi at all and any help at all would be greatly appreciated.
This is all the info I took from fastboot and the bootloader I thought would be needed
Bootloader Info
*** Tampered ***
*** Unlocked ***
M8_UL PVT SHIP S-ON
HBOOT - 3.18.0.0000
RADIO - 1.19.21331147A1.09G
OpenDSP - v38.2.2-00542-M8974.0311
OS - 2.22.401.4
Fastboot Getvar All Info
version: 0.5
version-bootloader: 3.18.0.0000
version-baseband: 1.19.21331147A1.09G
version-cpld: None
version-microp: None
version-main: 2.22.401.4
version-misc: PVT SHIP S-ON
serialno: xxx
imei: xxx
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: HTC__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 5e4b24e4
hbootpreupdate: 11
gencheckpt: 0
Thanks again for even looking!
First - remove the serial no. & imei no. as those are sensitive info.
The details that you have does not show that you did OTA. You are still two versions behind.
Restore your stock ROM, flash a matching stock recovery (no custom recovery) then do OTA ... multiple OTAs up to the latest 4.16.410.10
If you're willing to set the phone up from scratch you can just update straight to Lollipop using the RUU available on here. If you want to go that route then you can following this guide I wrote:
http://forum.xda-developers.com/showthread.php?t=2735235
Basically, step 3 covers what you need to do as step 1 and 2 are already done and at least once that's done if you still have issues you know it's not the software on the phone
ckpv5 said:
First - remove the serial no. & imei no. as those are sensitive info.
The details that you have does not show that you did OTA. You are still two versions behind.
Restore your stock ROM, flash a matching stock recovery (no custom recovery) then do OTA ... multiple OTAs up to the latest 4.16.410.10
Click to expand...
Click to collapse
Thank you I didn't even think of that I edited them out.
EddyOS said:
If you're willing to set the phone up from scratch you can just update straight to Lollipop using the RUU available on here. If you want to go that route then you can following this guide I wrote:
http://forum.xda-developers.com/showthread.php?t=2735235
Basically, step 3 covers what you need to do as step 1 and 2 are already done and at least once that's done if you still have issues you know it's not the software on the phone
Click to expand...
Click to collapse
I will try that right away thank you for your help I'll post back here when I'm done
No luck, kept getting error 99 with the 'htc_fastboot" from the thread and with my normal fastboot it gives me the error 32 'header error' I only noticed the thread was for s-off phones, I don't care about my phone saying tampered, unlocked or anything but I'm assuming that's stopping the flash from happening.
You must relock your device first ... then try again with flash the ruu.zip
Isotopes said:
You must relock your device first ... then try again with flash the ruu.zip
Click to expand...
Click to collapse
Haha yeah that worked now, ignoring the guide at the start and just leaving it with the relocked warning it's flashing now via the RUU
Thanks to the both of you for your help.
So I got all greedy and wanted Lollipop sooner than when my provider did an OTA.
I tried a bunch of roms and found that Cyanogen was able to work for my phone (a lot of others gave me that issue where the Wifi wouldn't work, I subsequently worked out this was a firmware issue).
In an effort to try and fix a number of bugs I've been attempting to get S-Off. I downloaded Sunshine but Sunshine told me my ROM wasn't close enough to stock for it. So I put another Rom on it, but then mysteriously I lost root access.
So I did a hard wipe.
And now I find myself unable to install any ROMs on it at all (I'm trying to find a stock Kitkat one that will hopefully run).
So I can't get S-Off. I'm not even sure if it's still rooted (though I do have Philz installed and that loads when I put it into recovery mode). And so I'm not even remotely sure what I should do.
Yay!
Bricked mine too!
RuminatorNZ said:
So I got all greedy and wanted Lollipop sooner than when my provider did an OTA.
I tried a bunch of roms and found that Cyanogen was able to work for my phone (a lot of others gave me that issue where the Wifi wouldn't work, I subsequently worked out this was a firmware issue).
In an effort to try and fix a number of bugs I've been attempting to get S-Off. I downloaded Sunshine but Sunshine told me my ROM wasn't close enough to stock for it. So I put another Rom on it, but then mysteriously I lost root access.
So I did a hard wipe.
And now I find myself unable to install any ROMs on it at all (I'm trying to find a stock Kitkat one that will hopefully run).
So I can't get S-Off. I'm not even sure if it's still rooted (though I do have Philz installed and that loads when I put it into recovery mode). And so I'm not even remotely sure what I should do.
Yay!
Click to expand...
Click to collapse
I just joined this forum, so I don't know if I should be posting here or on a new thread, so let me know I can delete this, move it if I'm out of line.
I'm in the same boat. Just softbricked my girlfriend's Samsung Galaxy S5 (SM-G900a)
Her phone was unlocked AT&T and it auto updated to 5.0 Lollipop update OTA about a week ago.
It's been running like **** so I thought I'd downgrade it to 4.2.2 via ODIN
ODIN (failed) trying to install
G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.gz
I read in one of these forums that downgrading wouldn't work but they found a work around
http://forum.xda-developers.com/showthread.php?t=2785363
Oh yeah and then my phone bricked so there is that, my GF is being really understanding but I'm hoping I can recover this!!!!
Edit: My problem was resolved here
http://forum.xda-developers.com/att...-2-bricked-t3093826/post60397413#post60397413
RuminatorNZ said:
So I got all greedy and wanted Lollipop sooner than when my provider did an OTA.
I tried a bunch of roms and found that Cyanogen was able to work for my phone (a lot of others gave me that issue where the Wifi wouldn't work, I subsequently worked out this was a firmware issue).
In an effort to try and fix a number of bugs I've been attempting to get S-Off. I downloaded Sunshine but Sunshine told me my ROM wasn't close enough to stock for it. So I put another Rom on it, but then mysteriously I lost root access.
So I did a hard wipe.
And now I find myself unable to install any ROMs on it at all (I'm trying to find a stock Kitkat one that will hopefully run).
So I can't get S-Off. I'm not even sure if it's still rooted (though I do have Philz installed and that loads when I put it into recovery mode). And so I'm not even remotely sure what I should do.
Yay!
Click to expand...
Click to collapse
your mistake is using CWM recovery, Sense custom roms require TWRP recovery, so you need to start by flashing the latest version of that.
once flashed, go in and do a full wipe. dont forget after wiping to reboot back into recovery for the changes to take effect, when you go to reboot it will say something like you have no OS installed, are you sure you want to reboot, just say yes, and select DO NOT INSTALL to SuperSU, the rom you falsh will be pre rooted.
TWRP latest version supports MTP, so when your in recovery main window, plug your phone into the computer and your sdcard and internal storage will open on your computer, just copy a rom to your sdcard, once copied, unplug your phone and install it.
use something like ARHD 41 or Maximus HD, they are close enough to stock for sunshine to work.
have a look here for a rom, dont download anything too modded or fancy as you'll be coming away from stock then http://forum.xda-developers.com/htc-one-m8/development
Seanie280672 said:
your mistake is using CWM recovery, Sense custom roms require TWRP recovery, so you need to start by flashing the latest version of that.
once flashed, go in and do a full wipe. dont forget after wiping to reboot back into recovery for the changes to take effect, when you go to reboot it will say something like you have no OS installed, are you sure you want to reboot, just say yes, and select DO NOT INSTALL to SuperSU, the rom you falsh will be pre rooted.
TWRP latest version supports MTP, so when your in recovery main window, plug your phone into the computer and your sdcard and internal storage will open on your computer, just copy a rom to your sdcard, once copied, unplug your phone and install it.
use something like ARHD 41 or Maximus HD, they are close enough to stock for sunshine to work.
have a look here for a rom, dont download anything too modded or fancy as you'll be coming away from stock then http://forum.xda-developers.com/htc-one-m8/development
Click to expand...
Click to collapse
Brilliant, thank you - I'll give this a whirl.
RuminatorNZ said:
Brilliant, thank you - I'll give this a whirl.
Click to expand...
Click to collapse
on a slightly different note, you dont need s-off to flash a firmware or RUU depending on your current firmware, can you post your fastboot getvar all without your imei and serial number please.
Seanie280672 said:
on a slightly different note, you dont need s-off to flash a firmware or RUU depending on your current firmware, can you post your fastboot getvar all without your imei and serial number please.
Click to expand...
Click to collapse
I sure can (thank you for your help):
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.16.2133156.UA15_2G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B11000
cidnum: HTC__039
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: ab0efa49
hbootpreupdate: 11
gencheckpt: 0
RuminatorNZ said:
I sure can (thank you for your help):
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.16.2133156.UA15_2G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B11000
cidnum: HTC__039
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: ab0efa49
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
your going to need s-off and convert your phone im sorry, doesnt seem to be anything about for your phone, firmware or RUU's.
You'll need to convert to get the latest firmware on your phone, unless you have it via an OTA or something like that ? convert to WWE 401 or Dev Edition 1540, currently your on 980 Austraillia Unbranded.
once you get s-off, convert is easy, all you need to do is change your CID number with a fastboot command, change your MID number, flash the firmware for Dev Ed or WWE, and then run the RUU.
Seanie280672 said:
on a slightly different note, you dont need s-off to flash a firmware or RUU depending on your current firmware, can you post your fastboot getvar all without your imei and serial number please.
Click to expand...
Click to collapse
I've got a sneaking suspicion that the ARHD and Maximus ROMS I'm finding won't mesh with the firmware I've got. I think.
Seanie280672 said:
your going to need s-off and convert your phone im sorry, doesnt seem to be anything about for your phone, firmware or RUU's.
You'll need to convert to get the latest firmware on your phone, unless you have it via an OTA or something like that ? convert to WWE 401 or Dev Edition 1540, currently your on 980 Austraillia Unbranded.
once you get s-off, convert is easy, all you need to do is change your CID number with a fastboot command, change your MID number, flash the firmware for Dev Ed or WWE, and then run the RUU.
Click to expand...
Click to collapse
yeah it's getting S-Off that struggling with.
RuminatorNZ said:
I've got a sneaking suspicion that the ARHD and Maximus ROMS I'm finding won't mesh with the firmware I've got. I think.
Click to expand...
Click to collapse
they should still install and run, your may have a few problems like wifi, but it should effect them installing and booting, try this one insted, its stock for your firmware version, https://www.androidfilehost.com/?fid=95916177934516545
You just need to make sure you flash with TWRP not CWM. http://dl.twrp.me/m8/
Seanie280672 said:
they should still install and run, your may have a few problems like wifi, but it should effect them installing and booting, try this one insted, its an older version of ARHD http://www.androidrevolution.org/do...oid_Revolution_HD-One_M8_34.6.zip&hash=3703c7
You just need to make sure you flash with TWRP not CWM. http://dl.twrp.me/m8/
Click to expand...
Click to collapse
Right, off I go to download these files on New Zealand's rubbish internet. I'll report back in many many hours
Thank you for all your help so far. Really appreciate it.
RuminatorNZ said:
Right, off I go to download these files on New Zealand's rubbish internet. I'll report back in many many hours
Thank you for all your help so far. Really appreciate it.
Click to expand...
Click to collapse
use this rom instead: https://www.androidfilehost.com/?fid=95916177934516545 its full stock rom, flash in TWRP still, and closest matching to your firmware, its KitKat not Lollipop.
Seanie280672 said:
they should still install and run, your may have a few problems like wifi, but it should effect them installing and booting, try this one insted, its stock for your firmware version, https://www.androidfilehost.com/?fid=95916177934516545
You just need to make sure you flash with TWRP not CWM. http://dl.twrp.me/m8/
Click to expand...
Click to collapse
Just keeping you updated, finished dowloading the above rom, flashed it and it seems to be working (mind you, my wifi still ain't working with that ROM, but I can live with that). Sunshine is now S-Off-ing as we speak so this is as much progress as I've made in 2 days!!
What should my next step be after getting S-Off?
RuminatorNZ said:
Just keeping you updated, finished dowloading the above rom, flashed it and it seems to be working (mind you, my wifi still ain't working with that ROM, but I can live with that). Sunshine is now S-Off-ing as we speak so this is as much progress as I've made in 2 days!!
What should my next step be after getting S-Off?
Click to expand...
Click to collapse
easiest thing for you to do is change your cid first, change it to WWE HTC__001 the command is fastboot oem write cid HTC__001 (thats 2 underscores, CID number is always 8 characters long)
so with your phone in the bootloader fastboot usb mode and plugged into the computer, run these3 commands
fastboot oem write cid HTC__001
fastboot erase cache
fastboot reboot-bootloader
next is to change you mid, so enter recovery and put this file on your SDcard http://forum.xda-developers.com/showthread.php?t=2779524
install it like you would with a rom, and follow the instructions on screen, when given the options to select mid to change to, select the one for WWE international.
when you have finished those 2 things, post your fastboot getvar all again please, should be a new and updated one, again without imei and serial number
Seanie280672 said:
easiest thing for you to do is change your cid first, change it to WWE HTC__001 the command is fastboot oem write cid HTC__001 (thats 2 underscores, CID number is always 8 characters long)
so with your phone in the bootloader fastboot usb mode and plugged into the computer, run these3 commands
fastboot oem write cid HTC__001
fastboot erase cache
fastboot reboot-bootloader
next is to change you mid, so enter recovery and put this file on your SDcard http://forum.xda-developers.com/showthread.php?t=2779524
install it like you would with a rom, and follow the instructions on screen, when given the options to select mid to change to, select the one for WWE international.
when you have finished those 2 things, post your fastboot getvar all again please, should be a new and updated one, again without imei and serial number
Click to expand...
Click to collapse
Is what you've suggested better than the Super-CID - 11111111 ?
RuminatorNZ said:
Is what you've suggested better than the Super-CID - 11111111 ?
Click to expand...
Click to collapse
I never bother with superCID, always seems to cause me more headaches than good.
the 2 best cid's to go for in my books are HTC__001 WWE (world wide engish) or BS_US001 Dev edition, they get the fastest updates.
Seanie280672 said:
I never bother with superCID, always seems to cause me more headaches than good.
the 2 best cid's to go for in my books are HTC__001 WWE (world wide engish) or BS_US001 Dev edition, they get the fastest updates.
Click to expand...
Click to collapse
Brilliant. I'll take your advice. You've got it all right so far.
See this guiy here did the same thing, but he is complaining that he's not got the next update yet, it because he hasnt changed his cid number, he needs to be on HTC__001, everytrhing else is done right, this is from the Australlian thread: http://forum.xda-developers.com/showpost.php?p=60272806&postcount=662
your fastboot getvar all should look like his when your done, only yours should say HTC__001 for the cid.
---------- Post added at 11:50 AM ---------- Previous post was at 11:42 AM ----------
RuminatorNZ said:
Brilliant. I'll take your advice. You've got it all right so far.
Click to expand...
Click to collapse
sorry my bad, no space between wite and cid so the command is fastboot oem writecid HTC__001
Seanie280672 said:
See this guiy here did the same thing, but he is complaining that he's not got the next update yet, it because he hasnt changed his cid number, he needs to be on HTC__001, everytrhing else is done right, this is from the Australlian thread: http://forum.xda-developers.com/showpost.php?p=60272806&postcount=662
your fastboot getvar all should look like his when your done, only yours should say HTC__001 for the cid.
---------- Post added at 11:50 AM ---------- Previous post was at 11:42 AM ----------
sorry my bad, no space between wite and cid so the command is fastboot oem writecid HTC__001
Click to expand...
Click to collapse
Righto, so far so good ... I think:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.24.21331147A1.09G
version-cpld: None
version-microp: None
version-main: 4.16.1540.8
version-misc: PVT SHIP S-OFF
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B11000
cidnum: HTC__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 3aa067db
hbootpreupdate: 11
gencheckpt: 0
RuminatorNZ said:
Righto, so far so good ... I think:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.24.21331147A1.09G
version-cpld: None
version-microp: None
version-main: 4.16.1540.8
version-misc: PVT SHIP S-OFF
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B11000
cidnum: HTC__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 3aa067db
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
just MID to change, just wondering, have you flashed some firmware ??? how did you get on this 4.16.1540.8 ??? this is dev edition firmware.
Hey guys, if somebody could help me resolve my problem i´ll be eternally gratefully. A couple of days before i bought an international version of the htc m8 (0P6BIMG100), it had kitkat 4.4.4, and i want to upgrate the sistem to marshmallow, so, reading in the multiple forums i found a tread in this site that teaches how to convert the phone to google edition, when i started the fastboot it was locked (i unlocked it) and S-off with supercid 11111111 (the phone came rooted). I follow the instructions step by step and after the installation of the RUU finished, the phone boots in to the black google screen and enter in fastboot. So, i tried reversing the process and go to the sense version again, a friend (who happen to have an htc m8) help me do it and we manage to restore de backup that i made in TWRP. After that, he toldme to install a custom rom, i decide to install the Insert Coin Enhaced "ice-8.2.2_M8_UHL_MM60_SENSE80GP_HTC_WWE_6.12.401.4". And for my surprise, it worked!! However, the phone didn´t recognice de wifi antena, the sim, the front camera, etc and the imei, baseband, and all that stuff said "not available", after a few minutes, the phone began to reboot. Looking through different XDA forums many said it was the kernel, so i let my friend flash the google edition kernel (i still don´t know why i let him do that). After that, the phone simply reboots in the fastboot screen, so again reading in the forums i found that maeby was not a kernel issue, but a firmware thing. So, i been installing a hell of firmwares and one by one trying to install the rom, but it jus´t don´t work. The last upgrate that i did via "ext_card" (i rename it 0P6BIMG) end saying in red letters "device halted due to large image update fail" (i wipe de data of the microsd, i change the microsd for ahother one, and nothing) and a red flag appeared saying "image update fail!". After this, no matter which firmware i try to install it, i cant find the right one, besides, now in the fastboot getvar all command the "version-main: " is blank, it shows nothing. I also found the RUU.exe trends and i tried some of them, but they get stock in the "sending information 0/7 screen". After a while i enter again in the fastode screen with the abd command. So if anybody could help me i´ll be glad to invite the beers, i need the phone for work and it´s been a hell of 5 straight days without resolving this issue, these are the specs that are showed in the fastboot mode screen:
*** Software status official ***
*** UNLOCKED ***
M8_WLV PVT SHIP S-OFF
CID - 11111111
HBOOT-3.19.0.0000
RADIO-1.25.214500021.06G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-
eMMC-boot 2048MB
------------------------------------
These are the specs in the "fastboot getvar all":
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.25.214500021.06G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: HT445SF02290
imei: ***************
imei2: Not Support
meid: **************
product: m8_wlv
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: 11111111
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 3aa067db
hbootpreupdate: 11
gencheckpt: 0
Does anyone know what can i do? Apologies for the language, i´m not a native english speaker
Your device is not International GSM (m8_ul or m8_uhl) but it is a Verizon CDMA device (m8_wlv).
Those ROMs you tried are for m8_ul or m8_uhl, won't work on your device.
Read this on how to fix it - https://forum.xda-developers.com/htc-one-m8/help/m8-bricked-flash-rom-neither-restore-t3535671
Well...
ckpv5 said:
Your device is not International GSM (m8_ul or m8_uhl) but it is a Verizon CDMA device (m8_wlv).
Those ROMs you tried are for m8_ul or m8_uhl, won't work on your device.
Read this on how to fix it - https://forum.xda-developers.com/htc-one-m8/help/m8-bricked-flash-rom-neither-restore-t3535671
Click to expand...
Click to collapse
But if is a CDMA why does the phone have a nanosim entry?
I follow the given istructions but none of them works, after keep reading other answers in other post i found the 1.57.114.2 firmware sugestion, i rename it to "0P6BIMG.ZIP" and was able to run it in the HBOOT menu, now these are the specs that are showed in the bootloader screen:
M8_WLV PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.2133156.UA10G
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.57.114.2
eMMC-BOOT 2048MB
Apr 10 2014, 01:18:21.1
----------------------------------------------------------------
These are the specs showed in the ´fastboot getvar all´ command:
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.16.2133156.UA10G
version-cpld: None
version-microp: None
version-main: 1.57.114.2
version-misc: PVT SHIP S-OFF
serialno: HT445SF02290
imei: ***************
imei2: Not Support
meid: ***************
product: m8_wlv
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: 11111111
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: c3d94491
hbootpreupdate: 11
gencheckpt: 0
--------------------------------------------------
I tried to install again the Insert Coin Enhaced "ice-8.2.2_M8_UHL_MM60_SENSE80GP_HTC_WWE_6.12.401.4", for my surprise the TWRP flashed it quick, but after the reboot it was stuck in the white screen with the HTC logo in green color, so...., i wipe it all, reinstall de "1.57.114.2.zip" and well, i´m still reading posts about the subject, any idea of what can i do sir?. By the way, thank you very much for the orientation
No matter what GSM firmware that you install, they won't work on your CDMA device.
You can install those GSM firmware like 1.57.114.2 because the MID is 0P6B10000
If you ever successful install a ROM on these firmware, you won't get any signal, your SIM won't work. Flashing these GSM firmware on CDMA device may brick your radio permanently.
What you need to do :
1. Change back the MID 0P6B10000 to original 0P6B20000
read this - https://forum.xda-developers.com/showpost.php?p=70504345&postcount=35
2. Install correct firmware to fix the radio first
https://forum.xda-developers.com/showpost.php?p=70502435&postcount=31
3. Install Marshmallow firmware which already include TWRP - https://www.androidfilehost.com/?fid=24438995911973227
4. Install your custom ROM that you want.
GPE - install this and select Verizon while in Aroma - https://forum.xda-developers.com/ve...ment/rom-vzw-stock-gpe-5-1-lmy47o-h9-t3212413
Or you can install any ROM in this section - https://forum.xda-developers.com/verizon-htc-one-m8/development
Or you can install some ROM with Verizon support in this section - https://forum.xda-developers.com/htc-one-m8/development
And I believe all the Nougat ROM support Verizon too.
lalomayen said:
But if is a CDMA why does the phone have a nanosim entry?
Click to expand...
Click to collapse
When we say "CDMA version" M8, it means it supports CDMA in addition to GSM and LTE networks. Mainly, so Verizon customers can use other carrier nanoSIMs while travelling to foreign countries.
The presence of the nanoSIM slot does not make it the "GSM" variant of the M8.
You have the Verizon CDMA version M8. There is not question about it.
lalomayen said:
I follow the given istructions but none of them works, after keep reading other answers in other post i found the 1.57.114.2 firmware sugestion
Click to expand...
Click to collapse
There is no reason to believe this firmware will work with your device.
You need to follow the advice given by ckpv5, he knows what he is talking about. If you get stuck with the process, tell us specifically what step, what the specific results were, error messages, etc. (just saying it didn't work, isn't goo enough) If you got stuck, it was likely pilot error; and we can probably troubleshoot, and see what went wrong, and properly advise you.
Ok, so i am in a somewhat similar situation to you. There are a few differences though. The first is that the phone has S-on. The owner said that the phone never had the bootloader unlocked, neither was it rooted. When the phone is turned on, it says:
*** Software status: Modified ***
*** Locked ***
***Security Warning ***
M8QL_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
[email protected]
OS-2.10.771.1
eMMC-boot 2048MB
Apr 22 2016,12:28:26.0
When i connected it to the pc and ran fastboot getvar all, I got:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.771.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *
(bootloader) imei: *
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: H3G__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: 0b9a12e3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
Any ideas what steps to take? Thanks in advance
ze410t said:
Ok, so i am in a somewhat similar situation to you. There are a few differences though. The first is that the phone has S-on. The owner said that the phone never had the bootloader unlocked, neither was it rooted.
Click to expand...
Click to collapse
Respectfully, your situation bears little, if any, similarity to the OP. His is s-off, with custom recovery, and trying to install custom ROMs. Further, he has the Verizon version (which as a lot of unique peculiarities versus other variants), with botched install of another version's firmware; which on the Verizon version in particular, results in broken radio (no SIM).
You have a very different M8 version, and a very different situation (close to stock - although I think root was at least attempted). And you haven't actually described what your question or issue is. The OP's problem is the wrong firmware, and custom ROMs don't work; but those issues don't apply to you.
I see you've started another thread here. I'd suggest sticking to that thread, rather than posting to this one. There are too many differences between your phone and situation to the OPs. Further discussion here (while also helping the OP in parallel) will probably result in unnecessary confusion.
redpoint73 said:
Respectfully, your situation bears little, if any, similarity to the OP. His is s-off, with custom recovery, and trying to install custom ROMs. Further, he has the Verizon version (which as a lot of unique peculiarities versus other variants), with botched install of another version's firmware; which on the Verizon version in particular, results in broken radio (no SIM).
You have a very different M8 version, and a very different situation (close to stock - although I think root was at least attempted). And you haven't actually described what your question or issue is. The OP's problem is the wrong firmware, and custom ROMs don't work; but those issues don't apply to you.
I see you've started another thread here. I'd suggest sticking to that thread, rather than posting to this one. There are too many differences between your phone and situation to the OPs. Further discussion here (while also helping the OP in parallel) will probably result in unnecessary confusion.
Click to expand...
Click to collapse
Oh ok :/ sorry about that. This was the only post that i found that i thought was similar. My apologies. Carry on!
ze410t said:
Oh ok :/ sorry about that. This was the only post that i found that i thought was similar. My apologies. Carry on!
Click to expand...
Click to collapse
No worries. I posted in the thread you started, and will try to help you there.
Stuck
ckpv5 said:
No matter what GSM firmware that you install, they won't work on your CDMA device.
You can install those GSM firmware like 1.57.114.2 because the MID is 0P6B10000
If you ever successful install a ROM on these firmware, you won't get any signal, your SIM won't work. Flashing these GSM firmware on CDMA device may brick your radio permanently.
What you need to do :
1. Change back the MID 0P6B10000 to original 0P6B20000
read this - https://forum.xda-developers.com/showpost.php?p=70504345&postcount=35
2. Install correct firmware to fix the radio first
https://forum.xda-developers.com/showpost.php?p=70502435&postcount=31
3. Install Marshmallow firmware which already include TWRP - https://www.androidfilehost.com/?fid=24438995911973227
4. Install your custom ROM that you want.
GPE - install this and select Verizon while in Aroma - https://forum.xda-developers.com/ve...ment/rom-vzw-stock-gpe-5-1-lmy47o-h9-t3212413
Or you can install any ROM in this section - https://forum.xda-developers.com/verizon-htc-one-m8/development
Or you can install some ROM with Verizon support in this section - https://forum.xda-developers.com/htc-one-m8/development
And I believe all the Nougat ROM support Verizon too.
Click to expand...
Click to collapse
Ohh, ok, got it now, i don´t know if 0P6B20000 was the original, but i follow the instructions in step 1, the TWRP 2.8.7.0 didn´t started in my phone, the 2.0.7.2 version did (i don´t know why), i follow the instructions: boot to recovery
Mount - system
then open command prompt from your adb/fastboot folder
then type
adb shell
follow by comand: echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x32\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
i get an error message ""dd" no se reconoce como un comando interno o externo, programa o archivo por lotes ejecutable." ("Dd" is not recognized as an internal or external command, Program or executable batch file")
redpoint73 said:
When we say "CDMA version" M8, it means it supports CDMA in addition to GSM and LTE networks. Mainly, so Verizon customers can use other carrier nanoSIMs while travelling to foreign countries.
The presence of the nanoSIM slot does not make it the "GSM" variant of the M8.
You have the Verizon CDMA version M8. There is not question about it.
There is no reason to believe this firmware will work with your device.
You need to follow the advice given by ckpv5, he knows what he is talking about. If you get stuck with the process, tell us specifically what step, what the specific results were, error messages, etc. (just saying it didn't work, isn't goo enough) If you got stuck, it was likely pilot error; and we can probably troubleshoot, and see what went wrong, and properly advise you.
Click to expand...
Click to collapse
I see, i´m new in this subject, thanks for the observations, i´ll submint the issues in the order that they appear
lalomayen said:
I see, i´m new in this subject, thanks for the observations
Click to expand...
Click to collapse
No problem. The Verizon version is pretty peculiar, so its easy to get confused by it. In fact, for this reason I typically do not recommend anyone buy this or the Sprint variant, unless they are located in the US actually using that particular carrier (Verizon or Sprint).
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.