Develop Bugs

[Q] RUU problem

Hey! I screwed up my root on my One X and now I am trying to apply an RUU update.
I downloaded the latest one I could find on androidruu.com
When it was about halfway done it aborted automatically and I got this message:
ERROR [158]: IMAGE ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
My current version is 4.18.771.4 and it wanted to update/downgrade to 3.14.401.31 which is nowhere near my current version so the RUU must be wrong?
It said it was released 2013-01-30 15:48:53 and that's the latest one on that website, maybe there are other websites with more recent RUUs?
Here is also my "getvar" info
version: 0.5a
version-bootloader: 1.72.0000
version-baseband: 5.1204.167.31H
version-cpld: None
version-microp: None
version-main: 4.18.771.4
serialno: ************
imei: ***************
product: endeavoru
platform: HBOOT-T30S
modelid: PJ4610000
cidnum: H3G__G04
battery-status: good
battery-voltage: 3765mV
devpower: 39
partition-layout: None
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
Please ask if you need more information!

KakisHLoLz said:
Hey! I screwed up my root on my One X and now I am trying to apply an RUU update.
I downloaded the latest one I could find on androidruu.com
When it was about halfway done it aborted automatically and I got this message:
ERROR [158]: IMAGE ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
My current version is 4.18.771.4 and it wanted to update/downgrade to 3.14.401.31 which is nowhere near my current version so the RUU must be wrong?
It said it was released 2013-01-30 15:48:53 and that's the latest one on that website, maybe there are other websites with more recent RUUs?
Here is also my "getvar" info
version: 0.5a
version-bootloader: 1.72.0000
version-baseband: 5.1204.167.31H
version-cpld: None
version-microp: None
version-main: 4.18.771.4
serialno: ************
imei: ***************
product: endeavoru
platform: HBOOT-T30S
modelid: PJ4610000
cidnum: H3G__G04
battery-status: good
battery-voltage: 3765mV
devpower: 39
partition-layout: None
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
Please ask if you need more information!
Click to expand...
Click to collapse
You are S-ON you can't downgread from 4.18 to 3.14 you can use only nandroid backup to restore stock rom or flash custom

You can,only use the ruu for your main version/cid
Gesendet von meinem HTC One X mit Tapatalk
---------- Post added at 06:38 PM ---------- Previous post was at 06:38 PM ----------
Why or unlocking bootloader flash a custom recovery and a custom Rom...
Gesendet von meinem HTC One X mit Tapatalk

KakisHLoLz said:
version-bootloader: 1.72.0000
Click to expand...
Click to collapse
RUU will not work on HBOOT above 1.39

meat_hooligan said:
RUU will not work on HBOOT above 1.39
Click to expand...
Click to collapse
Yes it will, if you manage to get your hands on a 4.18 ruu

Thant said:
You are S-ON you can't downgread from 4.18 to 3.14 you can use only nandroid backup to restore stock rom or flash custom
Click to expand...
Click to collapse
The problem is that I can not boot into OS.
I am stuck on the Cyanogenmod boot logo.
I don't know what went wrong, I unlocked the device and flashed with TWRP.
Then I got the problem where the touch did not work so I had to flash an older version of TWRP which fixed that.
Then I flashed my Cyanogenmod ROM and wiped both the dalvik and regular cache.
When I tried to boot it just stuck on the boot logo.
I tried to wipe the data but I managed to somehow mix up two different wipe options and obviously I wiped both the backup and everything on my sdcard. I'm screwed...
I used the adb tool to push over Cyanogenmod to TWRP and flashed the ROM ones again to see if that might fix the problem.
I still couldn't boot into OS and so I tried to follow Cyanogenmod's guide on how to root One X.
I flashed the recovery with Clockwork recovery and everything went fine until I try to flash a ROM from Clockwork recovery... I can't mount my sdcard?!?!
I tried to flash back to TWRP but when I try to boot into recovery from bootloader it just reboots back into HBOOT...
So now here I sit and think how much life sucks.

I never see you mentioning flashing the boot.img from CM ?
But if you start to flash this recovery
https://www.dropbox.com/s/yqzlpqo8illa53j/Philz recovery 5.15.9.img
It has touch and you can also mount the sdcard

Mr Hofs said:
Yes it will, if you manage to get your hands on a 4.18 ruu
Click to expand...
Click to collapse
I think RUU 4.18 will not

meat_hooligan said:
I think RUU 4.18 will not
Click to expand...
Click to collapse
I know its not available, but i am just saying......if it would be then it would work

Mr Hofs said:
I never see you mentioning flashing the boot.img from CM ?
But if you start to flash this recovery
It has touch and you can also mount the sdcard
Click to expand...
Click to collapse
My phone is currently charging, I will try to flash that file as soon as the battery is high enough

KakisHLoLz said:
My phone is currently charging, I will try to flash that file as soon as the battery is high enough
Click to expand...
Click to collapse
Take Action

meat_hooligan said:
Take Action
Click to expand...
Click to collapse
It seems that my phone won't charge, it's been charging for 4hr+ and it still says too low to flash...

Mr Hofs said:
I never see you mentioning flashing the boot.img from CM ?
But if you start to flash this recovery
It has touch and you can also mount the sdcard
Click to expand...
Click to collapse
Okay so I managed to flash PhilZ Touch 5, now you say I should flash boot.img, is that the file inside the cyanogenmod zip or is it a separate download?

I got everything to work, I flashed the boot.img and I am now a happy owner of a rooted One X
Thanks for your help! Cred to Mr Hofs!

Nice !
CASE CLOSED !

Please help .might really be bricked

I unlocked and installed twrp and 4.4.3 gpe rom on an att m8. Then tried to update to 4.4.4 and my phone went into bootloop. I booted to bootloader and now its a black screen and hboot 3.18.0.0000. Now when I try to load recovery , the twrp image comes up blinks a couple times and goes into boot loop. I've tried reflashing recovery but it doesn't seem to help.
I cant seem to get anything to work. All I can do is play around with the bootloader and fastboot
help please

this is my getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

I also cant run the 1.58 ruu because my hboot is 3.18 and my cid is cws__001.
this totally sucks

First of all delete your serial and IMEI asap. And try this fastboot command :
Fastboot erase cache
Then enter the recovery

Mr Hofs said:
First of all delete your serial and IMEI asap. And try this fastboot command :
Fastboot erase cache
Then enter the recovery
Click to expand...
Click to collapse
failed remote not allowed
any other ideas

Failed remote not allowed is in most cases an indication that the bootloader is locked/relocked

First unlock your phone . Download a compatible kernel for your att m8 4.4.x.
Extract kernel.zip and flash boot.img with adb in fastboot.

Mr Hofs said:
Failed remote not allowed is in most cases an indication that the bootloader is locked/relocked
Click to expand...
Click to collapse
its unlocked, I was able to install phillz recovery but it still bootloops. I do have enough time to wipe/format real quick. any ideas?

amirsardari said:
First unlock your phone . Download a compatible kernel for your att m8 4.4.x.
Extract kernel.zip and flash boot.img with adb in fastboot.
Click to expand...
Click to collapse
I am unlocked and I downloaded a att 1.58 rom and flashed the boot.img . it took but im still boot looping

Try this
http://forum.xda-developers.com/showthread.php?p=54200899
Sent from my HTC One_M8 using Tapatalk
---------- Post added at 08:34 AM ---------- Previous post was at 08:32 AM ----------
I use it to completely restore to stock again. Just read the ENTIRE INSTUCTIONS, i am on at&t also.
Sent from my HTC One_M8 using Tapatalk

joshzdad2013 said:
Try this
http://forum.xda-developers.com/showthread.php?p=54200899
Sent from my HTC One_M8 using Tapatalk
---------- Post added at 08:34 AM ---------- Previous post was at 08:32 AM ----------
I use it to completely restore to stock again. Just read the ENTIRE INSTUCTIONS, i am on at&t also.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
thanks. but fails after signature check. I think this is done for

I'm thinking without s-off, having a 3.18 hboot and cws__001 cid this phone is going in the garbage today

hugebulge said:
I'm thinking without s-off, having a 3.18 hboot and cws__001 cid this phone is going in the garbage today
Click to expand...
Click to collapse
If cwm Philz is working take another Rom and flash it...what's the problem? Or all recoveries are broken? There are also complete stock Roms take one of them root it and s-off...if Firewater doesn't work use sunshine, it's really worth it to pay 25$ if you say that phone is going into garbage...means you want to buy another one...except try to s-off it and yea...also if you want to update the Rom via official ota you need always the stock recovery otherwise it will never work...

One-M8-Master said:
If cwm Philz is working take another Rom and flash it...what's the problem? Or all recoveries are broken? There are also complete stock Roms take one of them root it and s-off...if Firewater doesn't work use sunshine, it's really worth it to pay 25$ if you say that phone is going into garbage...means you want to buy another one...except try to s-off it and yea...also if you want to update the Rom via official ota you need always the stock recovery otherwise it will never work...
Click to expand...
Click to collapse
philz works for 8 seconds then bootloops and twrp just blinks then bootloops. I cant flash any rom so their is no chance of firewater or sunshine. thanks for the 25$ offer but I think ill call htc and pay to have the motherboard replaced or just smash it to pieces and buy another phone.
Is their any way of changing the cid without s-off? I think I remember getting supercid on the m7 without s-off

hugebulge said:
philz works for 8 seconds then bootloops and twrp just blinks then bootloops. I cant flash any rom so their is no chance of firewater or sunshine. thanks for the 25$ offer but I think ill call htc and pay to have the motherboard replaced or just smash it to pieces and buy another phone.
Is their any way of changing the cid without s-off? I think I remember getting supercid on the m7 without s-off
Click to expand...
Click to collapse
No other way...but you can try something.....I think there are different twrp or Philz images because of the different variants of the phone...so try to get the real one for your device..maybe that should be the problem...if not try fastboot erase cache ..but I think it's more because of the wrong image..
All those things are user issues so no need to bash HTC or the phone because you are doing things wrong

One-M8-Master said:
No other way...but you can try something.....I think there are different twrp or Philz images because of the different variants of the phone...so try to get the real one for your device..maybe that should be the problem...if not try fastboot erase cache ..but I think it's more because of the wrong image..
All those things are user issues so no need to bash HTC or the phone because you are doing things wrong
Click to expand...
Click to collapse
I 100% agree with you that it is completely my fault and not HTC. Im not bashing HTC at all, I'm going to buy another m8. Smashing would just make me happy after spending 9 hours so far trying every possibility over and over.
It is totally bricked though. I had another m8 before this phone and upgraded the same way but it was s-off and I didn't have this problem. Firewater didn't work on this phone. The problem is that something is corrupted and their is no correct ruu for 3.18 hboot with CWS__001.

[Q] Pls help - HTC One X stuck on quietly brilliant screen and won't restore

Hi Friends,
First things first - I have looked up and tried several things that other folks facing similar issues have tried. None of it has worked for me.
Coming to the problem now.
It all began when I decided to unroot and install a custom ROM on my stock HTC One X and downloaded a stable build from http://wiki.cyanogenmod.org/w/Install_CM_for_endeavoru.
I followed the tutorials and unlocked my device and started off with CWM recovery 5.8.2.7. Did some experiemenation with backup and recovery. So far, so good.
I decided to use the 4.4 ROM and as per some information available it needed me to update to CWM 6.0.4.8. I did so but when I tried to go in recovery, the screen went blank. Tried it multiple times without luck.
Then I switched over to TWRP 2.7.1 and used it to install the cm-11-20141112-SNAPSHOT-M12-endeavoru.zip. It failed with status 7. Assert checks on bootloader ver failed (as per checks it would need anything 1.28 or higher). I am on hboot 1.12. I extracted the boot.img from the rom zip and flashed it from fastboot. It showed no change in hboot version (maybe this is where I faulted). It still won't install rom zip as I would expect.
Now the phone won't go beyond "Quietly Brilliant" screen on power on. Recovery to saved backup says its successful but it still gets stuck at same screen on reboot.
Would appreciate help and pointers from anyone who could help.
Thanks in advance,
Kunal

koolvirgo said:
Hi Friends,
First things first - I have looked up and tried several things that other folks facing similar issues have tried. None of it has worked for me.
Coming to the problem now.
It all began when I decided to unroot and install a custom ROM on my stock HTC One X and downloaded a stable build from http://wiki.cyanogenmod.org/w/Install_CM_for_endeavoru.
I followed the tutorials and unlocked my device and started off with CWM recovery 5.8.2.7. Did some experiemenation with backup and recovery. So far, so good.
I decided to use the 4.4 ROM and as per some information available it needed me to update to CWM 6.0.4.8. I did so but when I tried to go in recovery, the screen went blank. Tried it multiple times without luck.
Then I switched over to TWRP 2.7.1 and used it to install the cm-11-20141112-SNAPSHOT-M12-endeavoru.zip. It failed with status 7. Assert checks on bootloader ver failed (as per checks it would need anything 1.28 or higher). I am on hboot 1.12. I extracted the boot.img from the rom zip and flashed it from fastboot. It showed no change in hboot version (maybe this is where I faulted). It still won't install rom zip as I would expect.
Now the phone won't go beyond "Quietly Brilliant" screen on power on. Recovery to saved backup says its successful but it still gets stuck at same screen on reboot.
Would appreciate help and pointers from anyone who could help.
Thanks in advance,
Kunal
Click to expand...
Click to collapse
give me the result from command fastboot getvar version-main. And after this we will see haow to upgrade your hboot you are with too low hboot version

Thant said:
give me the result from command fastboot getvar version-main. And after this we will see haow to upgrade your hboot you are with too low hboot version
Click to expand...
Click to collapse
Hi,
Thanks pal ! Here is the output of fastboot getvar version-main
version-main: 0.0.0.178434
thanks,
Kunal

Ok.....so as I mentioned in my first post, I did play around with CWM 5.8.2.7 at the beginning and had made a backup. So I flashed CWM again and was able to restore my device.
Now, I need to update to CM11 ROM and would need help with that please. I guess what I already have is there in the first post I put in this thread. Here's the dump of fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.12.2000
(bootloader) version-baseband: 2.1204.135.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 0.0.0.178434
(bootloader) serialno: HT22WW100191
(bootloader) imei: 3591*********75
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ461****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4217mV
(bootloader) devpower: 100
(bootloader) partition-layout: None
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
thanks again in advance,
Kunal

koolvirgo said:
Ok.....so as I mentioned in my first post, I did play around with CWM 5.8.2.7 at the beginning and had made a backup. So I flashed CWM again and was able to restore my device.
Now, I need to update to CM11 ROM and would need help with that please. I guess what I already have is there in the first post I put in this thread. Here's the dump of fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.12.2000
(bootloader) version-baseband: 2.1204.135.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 0.0.0.178434
(bootloader) serialno: HT22WW100191
(bootloader) imei: 3591*********75
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ461****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4217mV
(bootloader) devpower: 100
(bootloader) partition-layout: None
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
thanks again in advance,
Kunal
Click to expand...
Click to collapse
No problem you are S-OFF Download this RUU relock your bootloader or if it's locked leave it locked and run the RUU this will upgrade your phone to 3.14.401.31 then upgrade to latest 4.18.401.4 after this you can unlock the bootloader and flash custom recovery latest TWRP or CWM or Philz and flash what you want

Thant said:
No problem you are S-OFF Download this RUU relock your bootloader or if it's locked leave it locked and run the RUU this will upgrade your phone to 3.14.401.31 then upgrade to latest 4.18.401.4 after this you can unlock the bootloader and flash custom recovery latest TWRP or CWM or Philz and flash what you want
Click to expand...
Click to collapse
Hi Thant,
Thanks for your tip. I will give this a try (though I will be able to try it out someone later this week only and provide update how it went).
Having said that, I have one question though - the link to RUU you specified looks like for unlocked HTC Europe version. I'm from India and I found that there might be one with same radio for India here.
Not doubting your advice, but just want to know what is the basis for knowing what RUU one must use ?
Also, can I choose the one for India (RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_India_3.14.720.24_Radio_5.1204.162.29) ?
thanks,
Kunal

koolvirgo said:
Hi Thant,
Thanks for your tip. I will give this a try (though I will be able to try it out someone later this week only and provide update how it went).
Having said that, I have one question though - the link to RUU you specified looks like for unlocked HTC Europe version. I'm from India and I found that there might be one with same radio for India here.
Not doubting your advice, but just want to know what is the basis for knowing what RUU one must use ?
Also, can I choose the one for India (RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_India_3.14.720.24_Radio_5.1204.162.29) ?
thanks,
Kunal
Click to expand...
Click to collapse
yes if you want, most of the people like European version not Asian. It is your choice you are S-OFF and you can flash what you want on your phone. And the radio is the same

Thant said:
yes if you want, most of the people like European version not Asian. It is your choice you are S-OFF and you can flash what you want on your phone. And the radio is the same
Click to expand...
Click to collapse
Hi Thant,
I did try the RUU you told me to use but update failed with error 159.
There are some RUUs for Indian models at http://www.androidruu.com/?developer=Endeavor and http://forum.xda-developers.com/showthread.php?t=2189048 but none for JB.
I have provided the getvar dump earlier but can't seem to find what I need to use (sorry for being a noob here). Please suggest what I can do more.
Merry Christmas and a Happy New Year.
thanks,
Kunal

koolvirgo said:
Hi Thant,
I did try the RUU you told me to use but update failed with error 159.
There are some RUUs for Indian models at http://www.androidruu.com/?developer=Endeavor and http://forum.xda-developers.com/showthread.php?t=2189048 but none for JB.
I have provided the getvar dump earlier but can't seem to find what I need to use (sorry for being a noob here). Please suggest what I can do more.
Merry Christmas and a Happy New Year.
thanks,
Kunal
Click to expand...
Click to collapse
are you charge your phone before run the RUU are you reloack the bootloader before run the RUU???

Thant said:
are you charge your phone before run the RUU are you reloack the bootloader before run the RUU???
Click to expand...
Click to collapse
Yes, I did both !!

koolvirgo said:
Yes, I did both !!
Click to expand...
Click to collapse
Are your phone say Endeavoru PVT in bootloader or say Endeavoru XE?

I have the same issue, I used the WinDroid toolkit but somehow I got stuck in the boot. I can go in recovery. My phone says endeavoru pvt. I also have the S-on.
INFOversion: 0.5a
INFOversion-bootloader: 1.72.0000
INFOversion-baseband: 5.1204.167.31
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 4.18.401.4
INFOserialno: HT23NW107620
INFOimei: 359188041361783
INFOproduct: endeavoru
INFOplatform: HBOOT-T30S
INFOmodelid: PJ4610000
INFOcidnum: HTC__405
INFObattery-status: good
INFObattery-voltage: 3660mV
INFOdevpower: 3
INFOpartition-layout: None
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: None
INFOhbootpreupdate: 2
INFOgencheckpt: 0
Click to expand...
Click to collapse
What I have to do?? Thanks for the help you are saving me!!

lollerz46 said:
I have the same issue, I used the WinDroid toolkit but somehow I got stuck in the boot. I can go in recovery. My phone says endeavoru pvt. I also have the S-on.
What I have to do?? Thanks for the help you are saving me!!
Click to expand...
Click to collapse
Okay I solved my problem, my issue was the boot.img that was different from the one inside the custom rom! Hope this helps

Thant said:
Are your phone say Endeavoru PVT in bootloader or say Endeavoru XE?
Click to expand...
Click to collapse
It says Endeavoru XE

koolvirgo said:
It says Endeavoru XE
Click to expand...
Click to collapse
Than this is bad news try to download ICS Asian RUU and restore it, then try to update to latest Asian rom if this not work you maust to update your hboot manualy the XE variant have a lot of problems with the update but first try to run ICS Asian RUU then check for update and then update Try this RUU

Thant said:
Than this is bad news try to download ICS Asian RUU and restore it, then try to update to latest Asian rom if this not work you maust to update your hboot manualy the XE variant have a lot of problems with the update but first try to run ICS Asian RUU then check for update and then update Try this RUU
Click to expand...
Click to collapse
Hi Thant,
I have not yet tried tried the ICS RUU you suggested. But before I go ahead, here's some more info.
The Android version, HTC Sense version both say "Protected"
Software number is "Unknown"
HTC SDK API level is 4.23
Kernel is 2.6.39.4-g7ecc196
Baseband version is 2.1204.135.20
Build no. is 0.1.0.0 (20130509 EndeavorU_Generic_WWE#178434)
Boot loader says -
ENDEAVORU XE ENG S-OFF RH
CID-11111111
HBOOT- 1.12.2000 (PJ461****)
CPLD-None
MICROP-None
RADIO-2.1204.135.20
Now, should I go ahead with the ICS RUU ?
How do I know what Android version I'm on ? Why would it say protected ? Any command I can fire from fastboot/adb ?
[getvar says (bootloader) version-main: 0.0.0.178434]
Thanks for all your time & help,
Kunal

koolvirgo said:
Hi Thant,
I have not yet tried tried the ICS RUU you suggested. But before I go ahead, here's some more info.
The Android version, HTC Sense version both say "Protected"
Software number is "Unknown"
HTC SDK API level is 4.23
Kernel is 2.6.39.4-g7ecc196
Baseband version is 2.1204.135.20
Build no. is 0.1.0.0 (20130509 EndeavorU_Generic_WWE#178434)
Boot loader says -
ENDEAVORU XE ENG S-OFF RH
CID-11111111
HBOOT- 1.12.2000 (PJ461****)
CPLD-None
MICROP-None
RADIO-2.1204.135.20
Now, should I go ahead with the ICS RUU ?
How do I know what Android version I'm on ? Why would it say protected ? Any command I can fire from fastboot/adb ?
[getvar says (bootloader) version-main: 0.0.0.178434]
Thanks for all your time & help,
Kunal
Click to expand...
Click to collapse
You are S-OFF you can run any RUU but your problem is that your phone say XE not PVT the XE edition have problem with the update hboot

Thant said:
You are S-OFF you can run any RUU but your problem is that your phone say XE not PVT the XE edition have problem with the update hboot
Click to expand...
Click to collapse
Hi Thant,
I tried it and failed Needless to say I made sure all the prerequisites were met.
Can you please tell me how to manually update hboot ?
thanks,
Kunal

koolvirgo said:
Hi Thant,
I tried it and failed Needless to say I made sure all the prerequisites were met.
Can you please tell me how to manually update hboot ?
thanks,
Kunal
Click to expand...
Click to collapse
fastboot oem lock - relock the bootloader
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip (AGAIN)
fastboot reboot-bootloader
fastboot flash unlocktoken Unlock_code.bin
then like normal flash recovery and then rom
You can find firmware.zip from OTA on the page with the RUU choice one OTA and flash it try with this one in attachment

Thant said:
fastboot oem lock - relock the bootloader
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip (AGAIN)
fastboot reboot-bootloader
fastboot flash unlocktoken Unlock_code.bin
then like normal flash recovery and then rom
You can find firmware.zip from OTA on the page with the RUU choice one OTA and flash it try with this one in attachment
Click to expand...
Click to collapse
Hi Thant,
Before trying what you suggested (for manual update) I tried the ICS RUU once again. It went through fine this time not sure why, then I did an OTA upgrade and now I'm on Android 4.0.4 hboot 1.12 (same as before but on 2.17.720.2). There are no more OTA updates available, though HTC india website says there is one available for 3.14.720.24 which is JB version and should automatically update my hboot which I can then hopefully use to update to 4.4 ROM. Do you think what I think is going to work ?
But I can't find the OTA firmware for 3.14.720.24. There was one available here but no more.
There's one here but not sure about the authenticity of this.
I have downloaded the firmware zip you shared but it seems the file is corrupt.
Thanks,
Kunal

Custom ROM causes boot loop

OK here is the situation - I have Sense 6/Lolipop 5.0.1 stock ROM( installed via OTA update) on the phone which works.
I have got root and got latest SuperSU and TWRP installed.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.26.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: zzzzzzzzzzz
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__039
(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: ba1d7a63
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
However every time I install a custom ROM I get stuck in boot loop and the only way to fix it is to go back to stock ROM
Any ideas??

petrjanda said:
OK here is the situation - I have Sense 6/Lolipop 5.0.1 stock ROM( installed via OTA update) on the phone which works.
However every time I install a custom ROM I get stuck in boot loop and the only way to fix it is to go back to stock ROM
Any ideas??
Click to expand...
Click to collapse
You need to manually flash the boot.img file in the custom ROM via ADB while in Fastboot mode, unless you have S-Off. Oh the quirks of HTC phones...

Capt'n Mal said:
You need to manually flash the boot.img file in the custom ROM via ADB while in Fastboot mode, unless you have S-Off. Oh the quirks of HTC phones...
Click to expand...
Click to collapse
Wrong info. Even on s-on M8 phones the boot.img is flashed automatically so that's not it.
@ O.P
Sure you full wiped before installing the new rom. Can you give an example of what roms you tried ?
And DELETE your imei and serial !

Capt'n Mal said:
You need to manually flash the boot.img file in the custom ROM via ADB while in Fastboot mode, unless you have S-Off. Oh the quirks of HTC phones...
Click to expand...
Click to collapse
I dont get it. This wasnt happening before the upgrade to lolipop. It also happens with multirom. Maybe its time to S-off.

Mr Hofs said:
Wrong info. Even on s-on M8 phones the boot.img is flashed automatically so that's not it.
@ O.P
Sure you full wiped before installing the new rom. Can you give an example of what roms you tried ?
And DELETE your imei and serial !
Click to expand...
Click to collapse
Tried ViperOne, Android Revolution HD, SkyDragon.
Yes every installation, I selected I want to wipe.

petrjanda said:
Tried ViperOne, Android Revolution HD, SkyDragon.
Yes every installation, I selected I want to wipe.
Click to expand...
Click to collapse
Hmmm, well i can suggest to make a full wipe manually in TWRP and don't select that in the rom's aroma installer. Then continue to install the full basic rom. Don't delete or modify apps in the installer.

Just flash the correct Lollipop firmware and you're good to go.
Cheers

shirreer said:
Just flash the correct Lollipop firmware and you're good to go.
Click to expand...
Click to collapse
OP is already on LP firmware, based on hboot and radio numbers.
---------- Post added at 09:07 AM ---------- Previous post was at 09:06 AM ----------
Capt'n Mal said:
You need to manually flash the boot.img file in the custom ROM via ADB while in Fastboot mode, unless you have S-Off. Oh the quirks of HTC phones...
Click to expand...
Click to collapse
This only applies to older HTC devices, and has never been true for the M8 (as another already stated). I don't understand why folks keep propagating this incorrect info.
---------- Post added at 09:08 AM ---------- Previous post was at 09:07 AM ----------
petrjanda said:
I have got root and got latest SuperSU and TWRP installed.
Click to expand...
Click to collapse
What version number of TWRP exactly? I ask, since once in a while, folks say they are on the "latest" but then it turns out they are looking in the wrong place, and its actually an older version (and the cause of their issue).
What ROMs specifically did you try?

I did a full wipe(system,data etc except sdcard) in TWRP 2.8.7, and then the install of ViperOne went good.

M8_UL can't install any rom

A friend gave me this spare M8, when he gave it to me it would only boot to (what I guess is) the bootloader screen.
Currently it says:-
TAMPERED
UNLOCKED
M8_UL PVT SHIP S-ON
HBOOT-3.16.0.0000
RADIO-1.14.2133156.UA13G
OpenDSP-v26.2.2-00538-M8974.0106
OS-eMMC-boot 2048MB
Feb 27 2014,01:29:50.0
I had several goes at install TWRP but the only one that would work is one that actually had UL in the name, so currently I can go into TWRP v2.7.0.3
In TWRP if I click on mount it will let me select:
Cache
System
Micro SDcard
It will not let me select:-
Data
USB-OTG (unsurprising)
If I go to Install
up to /
into external_sd
select cm-11-20141112-SNAPSHOT-M12-m8.zip
swipe to confirm flash
I get this
E: Unable to mount '/data'
many times
Rebooting the phone causes it do the Cyanogenmod arrow and it gets extremely hot. After 30 mins I turned it off.
I think that what I really want is Google Edition but for that I need to do S-off and for that I need a working ROM so that I can install something to do S-off; right?
Anyway I guess that all of this is because of the Unable to mount /data
How do I fix this please?
thanks, DNJ

This "Any ROM" must be a really good one. You are the 2nd person today that is complaining that they want it, but can't install it.
Seriously, this is the 2nd post saying "can't install any ROM", but then only stating one ROM that was attempted. Did you try others?
One problem I can see: your firmware (hboot, radio, etc.) is ancient, and won't work with current ROMs. CM11, I'm not sure, but CM12 won't even flash unless you are on hboot 3.19. Current Sense ROMs will flash, but will have severe problems (extreme long boot time or no boot, broken WiFi) and GPE ROMs also will have severe bugs, I believe.
I would advise updating the firmware, but the method to do so depends on your CID. Please do a fastboot getvar all, and post the output. Be sure to delete IMEI and serial number, as these are personal info.
dieselnutjob said:
I think that what I really want is Google Edition but for that I need to do S-off and for that I need a working ROM so that I can install something to do S-off; right?
Click to expand...
Click to collapse
That depends. Do you mean flashing a GPE ROM? For that, NO you do not need s-off.
However, if you want to do a full conversion by RUU to GPE, YES that requires s-off. The reasons to do full conversion are to get future "official" OTA updates, and the GPE partition scheme (smaller system partitions means larger user-accessible storage); but also means you need to "convert back" if you want to go back to Sense.

Ok I only tried two, and I can't do GPE because I can't meet the prequisites. My point is that my problem is not with a specific ROM.
I would like to do a full conversion with the OTA updates if possible please.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.14.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(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: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks for any help

My suggested steps would be:
1) Go into TWRP, select Wipe, and choose the option to format the internal storage, and see if that solve your "can't mount data" issue. If so:
2) Restore the stock nandroid backup for your CID from the following thread: http://forum.xda-developers.com/showthread.php?t=2701376
Only Philz recovery nandroid is available for your CID, so unless TWRP has the option to install a Philz/CWM file, you will need to flash Philz recovery. Then restore the appropriate nandroid with Philz.
That should get the phone back up and running.
3) From there, run the sunshine app ($25) to get s-off: http://theroot.ninja/
4) Then run the GPE RUU (Marshmallow, no less!): http://forum.xda-developers.com/showthread.php?t=2708589
Alternately, save yourself $25 (with the sacrifice of no official GPE OTAs), and after step 2 above:
3a) Flash the appropriate 1.54 stock recovery
4a) OTA update to current Lollipop firmware
5) Install current TWRP and just flash the GPE ROM.

the format data option worked.
I just booted into CM.
There are two links in the thread that you suggested for CID ORANG001, unfortunately both links are dead.

Do I actually need a stock ROM if I have CM running? Can I just purchase Sunshine and run it from CM, and then go straight to GPE?
thanks

just tried it
It says
Sunshine enountered problems with your rom. Please flash a stock, or more near stock rom and try again.

then one seems to work and (if I can root it) will allow sunshine
http://forum.xda-developers.com/showthread.php?t=2694994

I am now S-OFF.
Will a full RUU GPE conversion also sort out all of my firmware issues? or do I need to solve that first?
thanks, DNJ

dieselnutjob said:
the format data option worked.
Click to expand...
Click to collapse
Nice!
This doesn't always seem to work when folks have internal storage corruption. So I'm glad to see it worked.
---------- Post added at 09:29 AM ---------- Previous post was at 09:28 AM ----------
dieselnutjob said:
Do I actually need a stock ROM if I have CM running? Can I just purchase Sunshine and run it from CM, and then go straight to GPE?
Click to expand...
Click to collapse
As you've already figured out, CM is not nearly stock enough to run sunshine.
---------- Post added at 09:31 AM ---------- Previous post was at 09:29 AM ----------
dieselnutjob said:
I am now S-OFF.
Click to expand...
Click to collapse
Again, nice work! Did you use the stock ROM dump you linked previously, and rooted it, in order to run sunshine?
dieselnutjob said:
Will a full RUU GPE conversion also sort out all of my firmware issues? or do I need to solve that first?
Click to expand...
Click to collapse
The RUU will update the firmware, shouldn't be a need to do that seperately.

redpoint73 said:
Did you use the stock ROM dump you linked previously, and rooted it, in order to run sunshine?
Click to expand...
Click to collapse
Yes. It was the one in the link above.
The ROM has an option to root, which downloads a zip file, but I could not figure out where it had saved it to. I found the same zip file using google, saved it to SD card, and then flashed it using TWRP.
Sunshine crashed the first time but the second time it worked.
Thanks for the help.

Google Play Edition is now installed from RUU and working nicely.