Related
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.
So here's my predicament, a long while ago i had installed a rom to my phone assuming i had done everything correctly. This ROM i installed is the Bad Boys One M8 L Sense 7 v 1.0, it is currently still what I'm currently using. What I've been trying to do for days now to return my phone back to stock. My bootloader is unlocked and s-off. I have been unable to install any ROM whatsoever besides the current bad boyz rom. Also when trying to use sunshine, it seems to also encounter problems. If anyone can offer some help or a method to go about fixing this it would greatly appreciated.
Jdp2510 said:
So here's my predicament, a long while ago i had installed a rom to my phone assuming i had done everything correctly. This ROM i installed is the Bad Boys One M8 L Sense 7 v 1.0, it is currently still what I'm currently using. What I've been trying to do for days now to return my phone back to stock. My bootloader is unlocked and s-off. I have been unable to install any ROM whatsoever besides the current bad boyz rom. Also when trying to use sunshine, it seems to also encounter problems. If anyone can offer some help or a method to go about fixing this it would greatly appreciated.
Click to expand...
Click to collapse
For Sunshine to work, flash MaximumHD , or you could also flash ViperOneM8 (suggested by JCase, one of the Sunshine devs) for it to work.
If you want to go back to stock, you need to provide more info. Post the results of fastboot getvar all here (minus your IMEI and serial#), and I or someone else here will be able to give you proper directions.
xunholyx said:
For Sunshine to work, flash MaximumHD , or you could also flash ViperOneM8 (suggested by JCase, one of the Sunshine devs) for it to work.
If you want to go back to stock, you need to provide more info. Post the results of fastboot getvar all here (minus your IMEI and serial#), and I or someone else here will be able to give you proper directions.
Click to expand...
Click to collapse
I have tried the maximus hd with it getting stuck at the recovery screen. As for the other I'll do what i can to figure out that info for you
Jdp2510 said:
I have tried the maximus hd with it getting stuck at the recovery screen. As for the other I'll do what i can to figure out that info for you
Click to expand...
Click to collapse
Not much to figure out.
Hook your phone up to your PC, get into ADB/fastboot, and enter the command fastboot getvar all.
xunholyx said:
Not much to figure out.
Hook your phone up to your PC, get into ADB/fastboot, and enter the command fastboot getvar all.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0209
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.25.651.18
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 99000499318193
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0f94b3b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I've tried running the appropriate RUU; I've tried flashing other roms with no success; I just can't seem to get the correct directions on what I need to do. If anyone has any ideas it will all be very appreciated.
Jdp2510 said:
I've tried running the appropriate RUU; I've tried flashing other roms with no success; I just can't seem to get the correct directions on what I need to do. If anyone has any ideas it will all be very appreciated.
Click to expand...
Click to collapse
You are S-On, so to run the RUU successfully you'll need to re-lock your bootloader first.
In fastboot : fastboot oem lock
Then run the RUU again
I did try that but it kept failing, I'll try one more time.
Like I thought, it failed again, error 155:
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
I'm downloading the correct RUU. http://www.htc.com/us/support/rom-downloads.html - The HTC One M8.
Jdp2510 said:
Like I thought, it failed again, error 155:
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
I'm downloading the correct RUU. http://www.htc.com/us/support/rom-downloads.html - The HTC One M8.
Click to expand...
Click to collapse
Error 155 is common for MM RUUs, as there is a peculiarity with the MM RUUs, in which you can't upgrade from LP (or KK for that matter) by RUU unless you first run the MM firmware.zip.
Try flashing the full signed firmware 6.20.651.3 from the following thread (with instructions on how to flash) then run the RUU 6.20.651.3 again:
http://forum.xda-developers.com/showthread.php?t=2729173
Or your other option is to flash the 4.25.651.18 RUU (same thead) and OTA to MM.
---------- Post added at 11:10 AM ---------- Previous post was at 11:08 AM ----------
Jdp2510 said:
I have been unable to install any ROM whatsoever besides the current bad boyz rom.
Click to expand...
Click to collapse
Hard to know what you are talking about, if you don't supply the required specifics (what ROMs exactly).
But only ROMs that specifically support Sprint, will work on your phone, due to kernel differences between Sprint and most other versions of the M8.
Running the MM RUU isn't going to change this fact. It seems your goal is to be able to install other ROMs?
What kind of specifics do you need?
I haven't been able to get any other roms to work. The ruu meant for my phone keeps failing, the name of the ROM is what details my phone says,
Jdp2510 said:
What kind of specifics do you need?
Click to expand...
Click to collapse
I already asked exactly what ROMs you tried.
You say you can't get "any ROMs" to work, and only name one (that does work).
You probably are trying to flash ROMs that don't support the Sprint version M8.
---------- Post added at 10:05 AM ---------- Previous post was at 10:04 AM ----------
Jdp2510 said:
The ruu meant for my phone keeps failing, the name of the ROM is what details my phone says,
Click to expand...
Click to collapse
Yup, and it will keep failing, if you just try the same thing over and over.
Did you try to do as I suggested in my post #10 above (flash MM firmware.zip, then try the RUU again)?
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
Hello, sorry for the probably completely noob question that might have already been answered but I searched for this answer and dinn't find anything really relevant.
I'd like to check the version of the unit I received so I can install a proper ROM without killing the phone as I'm aware certain versions of the M8 (GSM/CDMA) might get into troubles if wrong roms are used.
So I bought this phone from a chinese reseller. Phone is obviously refurbished (phone was rooted "out of the box" with all bloatware removed). There is a sticker on the back of the phone with 3 barcode (P/N, S/N amnd IMEI). What's strange is IMEI is similar on sticker and "about phone" but S/N doesn't match, as if it had been tampered/manually modified... So, definitely, the motherboard or the case had been replaced and I couldn't rely on the model number wirtten on the back of the phone.
First thing I tried was using the IMEI to check version but it matches an HTC Desire 820, I wasn't aware you could modify IMEI or dupe. Anyway, I moved on to the next step, which was going into bootloader. Bootloader says CID-1111111, which is, from my understanding, a way of making the phone open to any roms, from any country. Ok, one more info that doesn't help.
So I used the fastboot getvar all and it gave me this :
Code:
(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: 4.18.708.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC******
(bootloader) imei: 35************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B6****
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I googled "0P6B6****" (it comes with the ****, I didn't replaced any digits, only hidden IMEI and S/N) and it didn't gave me any solid information. Since phone was rooted and seemingly heavily tampered, I went back to stock and possibly get OTA to get Marshmallow (current os is 4.18.708.12) but there's no more updates so I'm "stuck" with 5.0.1. I thought the phone was initially a taiwanese version since it had the Snapdragon [email protected] but there's a lot of chinese bloatware.
So I can't update to M and therefore convert the phone to GPe or even use any custom roms (unless I missed something and I'm completely wrong). Can you help me trying to figure out what I received and if there's anything I can do with it or if I'm stuck with the stock rom.
Thank you.
Your device is GSM which is good if you're not on US CDMA carrier.
0P6B6**** is SuperMID, 11111111 is SuperCID.
Depends on what you want your device to be, I suggest to change SuperMID to actual MID of your intended region.
If EU, change it to 0P6B10000, leave SuperCID as it is now then install latest Marshmallow RUU. You also can try to install RUU with SuperMID and see whether it works or not. AFAIK it should work with SuperMID.
Thank you for your quick answer. Yes, I use it in Europe so it works fine with my carrier (even if LTE B20 is missing but it's ok). I'll do as you suggested. I'm glad I got a GSM-only phone, I thought I received a hybrid unit. Thank you again.
ckpv5 said:
Your device is GSM which is good if you're not on US CDMA carrier.
0P6B6**** is SuperMID, 11111111 is SuperCID.
Depends on what you want your device to be, I suggest to change SuperMID to actual MID of your intended region.
If EU, change it to 0P6B10000, leave SuperCID as it is now then install latest Marshmallow RUU. You also can try to install RUU with SuperMID and see whether it works or not. AFAIK it should work with SuperMID.
Click to expand...
Click to collapse
Ok, so I modifed MID 0P6B10000 and then tried to install latest Marshmallow RUU 6.12.401.4 via fastboot but phone is not booting up (stuck on HTC One logo). So i restored with my previous clean Nandroid backup. I'm back to 4.18.708.12 (phone is 100% working)
First question : bootloader tells me os is 6.12.401.4 while I'm actually running 4.18.708.12. Is it a problem or not ?
Second question : in order to have a working (eu) MM rom on my phone, I guess I'm supposed to flash the firmware to the latest right (which is something I haven't done in my previous attempt to flash MM) ? But which one am I supposed to grab ? 6.12.401.4 or 6.16.708.1 ? I'll use your guide to do it (https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5). Can you confirm updating the firmware is mandatory before flashing stock MM rom when upgrading from Lollipop stock ? I can't install MM RUU, coming from LP, without flashing the fw first ?
Once firmware is updated, I can safely flash MM 6.12.401.4 ? I might as well flash to MM with TWRP and use one of your stock MM backup. Can it be done coming from my current LP rom version ?
Last question : let's say I flash the 6.12.401.4 firmware and keep the 4.18.708.12 LP rom, phone won't boot right ? Keep in mind I have a phone with a ModelID 0P6B10000 and a stock LP rom 4.18.708.12
I'm sorry for the noob questions and to bother you with these but I tried a lot of different things (and I don't want to go to fast and kill the phone) without any success, and since this is my first HTC phone, there are some novelties in the flashing process. And I recovered the phone several times so I might run out of luck next time.
Thank you again for your help.
Which RUU you tried ?
Try this - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Your bootloader now 6.12.401.4, is it written as single not double in red ? If single then it is ok
Lollipop ROM can work when firmware is MM.
Most of the time you need to install MM firmware first to install MM RUU but the above linked RUU, you don't need to.
Since your firmware already updated to 6.12.401.4 you can restore 6.12.401.4 backup available in my backup thread to have stock ROM running or install any custom ROM that you like. You don't really need to make it stock MM rom first if your plan is to install custom rom. Only you need MM firmware installed, install latest TWRP 3.x then install rom
To your last question, when you have lollipop rom running and you flash only MM firmware, it won't boot as boot.img installed now is MM and the LP rom needs LP boot.img to boot
ckpv5 said:
Which RUU you tried ?
Try this - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Your bootloader now 6.12.401.4, is it written as single not double in red ? If single then it is ok
Lollipop ROM can work when firmware is MM.
Most of the time you need to install MM firmware first to install MM RUU but the above linked RUU, you don't need to.
Since your firmware already updated to 6.12.401.4 you can restore 6.12.401.4 backup available in my backup thread to have stock ROM running or install any custom ROM that you like. You don't really need to make it stock MM rom first if your plan is to install custom rom. Only you need MM firmware installed, install latest TWRP 3.x then install rom
To your last question, when you have lollipop rom running and you flash only MM firmware, it won't boot as boot.img installed now is MM and the LP rom needs LP boot.img to boot
Click to expand...
Click to collapse
OS line is green and single so I'm good.
So if I'm understanding correctly, if OS in bootloader says 6.12.401.4, then it means firmware actually installed on phone is 6.12.401.4.
Now, when installing the RUU zip provided there (https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6), the file is corrupt, on both links. File size is correct in Windows but when I open the archive (for example to add 11111111 in android-info.txt), it says archive is corrupt and file size of the different files in this archive are way too small.
I'm gonna try Nandroid backup.
Don't do thing that is not in the instructions. No where I wrote you need to add anything to the RUU zip. It's simple process, why need to make it harder ?
RUU zip is a htc signed zip. No windows archiver such as winzip, winrar, 7-zip and etc can properly open it and you're not supposed to open it.
Read the instruction again. No need to add 11111111 to the zip as there is no such thing as SuperRUU or SuperFirmware. 11111111 is for the device which means your M8 is SuperCID and you can install the zip regardless what your device CID is.
You are absolutely right about me doing unnecessary steps. That probably explain why I didn't manage to get it working. Anyway, I used twrp to restore one the MM Nandroid backup you provided in one of your post (+ recovery) and it went smoothly. I'm now on MM and phone is working fine. I'll see if it's worth flashing a custom rom if I can find one that fits my needs.
Thank you for your answers, it did help me quite a lot. Your guides (+ all the different files you provide) are excellent, as long as you follow the instructions and don't do unnecessary steps
Have a nice day/evening.
hi,
I also have a htc m8 with modelid: 0P6B6**** and sid=1111111 which I want to use in the UK, but mine is the dual sim version of the phone
I tried following the instructions at https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
It seemed to be installing but after about 20mins it failed with the error - "(bootloader) shift signature_size for header checking...FAILED (remote: 32 header error)"
I then found another RUU which I think is the correct one but received the same error (0P6BIMG_M8_DUGL_M60_SENSE70_MR_HTC_Europe_6.16.401.1_Radio_1.24.30336021.13G_30.69.336021.00_F_release_465001_signed.zip)
btw - i tried changing the mid to 0P6B10000 but this also failed (i downloaded an app which runs in twrp to do it, is this the correct way?)
----------------- my current phone info ------------
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.30336021.13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.30.401.15
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC4BRY-----
(bootloader) imei: -----
(bootloader) imei2: ----
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B6****
(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: RUU
(bootloader) commitno-bootloader: 49d38c68
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
alanes said:
I also have a htc m8 with modelid: 0P6B6**** and sid=1111111 which I want to use in the UK, but mine is the dual sim version of the phone
Click to expand...
Click to collapse
Finally you post your question in right section instead of ROM development thread.
I read all your questions before but I ignored them as they were posted in wrong section as I don't want to clutter ROM development thread with Off-Topics.
I don't think you can update your device directly to the latest Marshmallow as your current firmware is Lollipop. In order to do that you need to install Marshmallow firmware first then RUU but I don't see Marshmallow firmware is available anywhere except the RUU.
So my suggestion is install the Lollipop RUU then do OTA to Marshmallow. You may need to do 2 or 3 OTAs to reach that level.
1. No need to change anything to your MID yet. Let it be as it is now 0P6B6****
Only when the RUU fails to install due to MID error, then you need to change it to 0P6B64000 NOT 0P6B10000
https://forum.xda-developers.com/showthread.php?t=2708581
2. Download 0P6BIMG_M8_DUGL_L50_SENSE60_MR_HTC_Europe_4.30.401.15_Radio_1.24.30336021.13G_30.69.336021.00_F__signed.zip
from here - https://easy-firmware.com/home/browse/category/id/7825/
3. Install the RUU as instructed here - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
but use the above downloaded RUU
or you can rename it to 0P6BIMG.zip and place it on your microsd and boot to bootloader to install.
Make sure you don't rename it to 0P6BIMG.zip.zip
ckpv5 said:
Finally you post your question in right section instead of ROM development thread.
I read all your questions before but I ignored them as they were posted in wrong section as I don't want to clutter ROM development thread with Off-Topics.
Click to expand...
Click to collapse
Hi,
Thanks for your reply - sorry if I posted in the wrong place etc. - I struggle as I can't get the xda search to work so find it difficult to find anything.
As you know I keep giving up on this but then end up trying again and spending all night messing about with it.....
I tried installing *0P6BIMG_M8_DUGL_L50_SENSE60_MR_HTC_Europe_4.30.401.15_Radio_1.24.30336021.13G_30.69.336021.00_F__signed.zip* but get the same error.
I am not sure if this includes the firmware or if that is separate to the RUU (as I have tried to install new firmwares so the installed one may well not be the correct one).
update: I have now installed the firmware to match (i.e. a 40mb zip file version 4.30.40 1.15) but still getting the error when i try to install the RUU
btw - I tried copying to the sd card but that gives error "device halted due to large image update fail"
---------
This I think is the info from my phone when I first received it
info on my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.18.30306251.05G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC4...............
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B6****
(bootloader) cidnum: 11111111
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6b903f73
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks again
Alan.
I guess you need to change your MID 0P6B6**** to 0P6B64000
then try again the RUU.
I already gave you link on how to do it as in item #1
ckpv5 said:
I guess you need to change your MID 0P6B6**** to 0P6B64000
then try again the RUU.1
Click to expand...
Click to collapse
I changed the MID but then when I rebooted in to fastboot I was no longer able to connect via the fastboot command on my computer (just stayed in "waiting for device" although ADB still works ok).....
But I copied the RUU to the SD card and it installed ok
I am just doing a first boot in to android and will let you know how it goes
Thanks again for your help
Alan
---------- Post added at 08:42 AM ---------- Previous post was at 08:20 AM ----------
update: Well, a partial success
The update applied ok and I booted in to the new version of android no problem
but still when I try to use fastboot it just stays in "waiting for device" on my computer (Linux) so I am now stuck as you need fastboot to be able to install twrp.
bootloader on the phone detects when I plug the pc in with "BOOTLOADER USB". This text is highlighted in red, I think this is normal?
"htc-fastboot devices" shows nothing
btw - I have tried it on another computer and is the same
alanes said:
I changed the MID but then when I rebooted in to fastboot I was no longer able to connect via the fastboot command on my computer (just stayed in "waiting for device" although ADB still works ok).....
But I copied the RUU to the SD card and it installed ok
I am just doing a first boot in to android and will let you know how it goes
Thanks again for your help
Alan
---------- Post added at 08:42 AM ---------- Previous post was at 08:20 AM ----------
update: Well, a partial success
The update applied ok and I booted in to the new version of android no problem
but still when I try to use fastboot it just stays in "waiting for device" on my computer (Linux) so I am now stuck as you need fastboot to be able to unlock the device (i.e. fastboot oem get_identifier_token)
bootloader on the phone detects when I plug the pc in with "BOOTLOADER USB". This text is highlighted in red, I think this is normal?
btw - I have tried it on another computer and is the same
Click to expand...
Click to collapse
First thing is why did you relock bootloader. I never say you need to that because your device is S-Off
I'm not familiar with linux, never see BOOTLOADER USB, only FASTBOOT USB. Do you have access to any windows PC ?
You don't really need to do fastboot oem get_identifier_token to unlock bootloader, what you need is only a flashable TWRP zip and use adb command to unlock bootloader. Later tonight when I'm home I'll upload the flashable TWRP zip and instructions on how to unlock it.
Mean time please advise the OS no. written on bootloader so I can write the same to TWRP zip.
ckpv5 said:
First thing is why did you relock bootloader. I never say you need to that because your device is S-Off
I'm not familiar with linux, never see BOOTLOADER USB, only FASTBOOT USB. Do you have access to any windows PC ?
You don't really need to do fastboot oem get_identifier_token to unlock bootloader, what you need is only a flashable TWRP zip and use adb command to unlock bootloader. Later tonight when I'm home I'll upload the flashable TWRP zip and instructions on how to unlock it.
Mean time please advise the OS no. written on bootloader so I can write the same to TWRP zip.
Click to expand...
Click to collapse
Hi,
I had assumed it had re-locked the bootloader but later realised it was still S-off
and you are right it is "FASTBOOT USB", not "BOOTLOADER USB" - sorry for the confusion
My phone shows OS-4.30.401.15
I can use a friends Windows laptop and will see if I can give it a try
On another subject, the GPS on this phone seems to be dead (it has never seen a single satellite), is this a known problem with these phones do you happen to know?
thanks
Alan
alanes said:
My phone shows OS-4.30.401.15
Click to expand...
Click to collapse
I thought you want to update to the latest so you can install LOS14 or LOS15 or any custom ROM later.
Once you successfully back on stock 4.30.401.15, you should check for OTA and install. I believe you will have 2 or 3 OTA to get to Marshmallow firmware.
Have you check for OTA & update ?
About GPS, maybe you have faulty gps cable in it. I don't have M8 dual SIM but no reason why it is not working unless it is hardware issue. I can't help when it comes to hardware.
Read this - https://forum.xda-developers.com/htc-one-m8/general/gps-harware-fix-teardown-t3023999
ckpv5 said:
I thought you want to update to the latest so you can install LOS14 or LOS15 or any custom ROM later.
Have you check for OTA & update ?
Read this - https://forum.xda-developers.com/htc-one-m8/general/gps-harware-fix-teardown-t3023999
Click to expand...
Click to collapse
Hi,
I think you are making the mistake in thinking I have some idea what I am doing - lol
I just want to get LiniageOS 14 installed - I have never done anything like this before on my phone and this is a new phone I was not at all familiar with to start with, it has so far been a bit of a nightmare.......
thanks - I will read the link you provided and see if I can get it updated then get back to you
alanes said:
Hi,
I think you are making the mistake in thinking I have some idea what I am doing - lol
I just want to get LiniageOS 14 installed - I have never done anything like this before on my phone and this is a new phone I was not at all familiar with to start with, it has so far been a bit of a nightmare.......
thanks - I will read the link you provided and see if I can get it updated then get back to you
Click to expand...
Click to collapse
I don't make mistake as I understand what you are trying to do. If you unlock bootloader and install twrp now, you're back to earlier problem.
To install LOS 14, you must have Marshmallow firmware installed. Now you're on stock 4.30.401.15. You don't need to do unlocking & install twrp yet. You need to do OTA until you get final OTA either 6.16.401.1 or 6.16.401.101 then only you proceed to unlock bootloader and install twrp and install LOS 14.
Forget about link to GPS matter for now as that require device teardown.
Most important now OTA. Without OTA it serves no purpose on what you're doing now and intend to do later.
ok - thanks, I think I now know what I need to do (how many times have I thought that in the last few days - lol)
I Just tried fastboot on a windows laptop and it works! (no idea what is going on there - but at least I can now use it again)
it now shows modelid = 0P6B640000
BTW-I think the universe has it in for me regarding this project as apart from wanting to use LineageOS, the main reason I bought a new phone is that my existing phones GPS stopped working.........
alanes said:
ok - thanks, I think I now know what I need to do (how many times have I thought that in the last few days - lol)
I Just tried fastboot on a windows laptop and it works! (no idea what is going on there - but at least I can now use it again)
it now shows modelid = 0P6B640000
BTW-I think the universe has it in for me regarding this project as apart from wanting to use LineageOS, the main reason I bought a new phone is that my existing phones GPS stopped working.........
Click to expand...
Click to collapse
In case you're not sure what OTA I'm talking about, go to settings - about - software update - check here for OTA. When there is one, download and install. Again repeat the process until it says there is no update available.
Every time you install OTA, you OS no. on bootloader will change to current firmware. You need this until the OS no. is written as 6.16.401.1 or 6.16.401.101.
Then only you unlock bootloader and install latest twrp 3.x and install LOS 14
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.