Hello All,
I have tried to follow all these tutorials, but my issues is not listed yet.
Original rom was on Vodafone, tried to gain S-OFF, but it failed saying that is not possible for my device yet? So I was kind of stuck with Tampered, Unlocked but S-ON
By mistake I have wipe everything through customer recovery as I have left myself with No OS. Tried different RUU, latest one isRUU_M8_TMOUS_1.57.531.7, but can't go anywhere and always stuck on Signature check 132 Error or 150 error
I did reboot boot loader and I did relock.
Tried also a Sideload rom, comes up with the error that is either insufficient space, can not read sideload. cant't push through adb either comes with error
Also is there a way to gain S-OFF in the bootloader only?
Looking forward to your thoughts and possible solution.
Many thanks
Also: when i run the relock command this one comes up.
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.153s
Answer me this quickly, if you have a Vodafone, S-ON, why on God's green earth would you flash a RUU for T-Mobile US?
arnasx69 said:
Hello All,
I have tried to follow all these tutorials, but my issues is not listed yet.
Original rom was on Vodafone, tried to gain S-OFF, but it failed saying that is not possible for my device yet? So I was kind of stuck with Tampered, Unlocked but S-ON
By mistake I have wipe everything through customer recovery as I have left myself with No OS. Tried different RUU, latest one isRUU_M8_TMOUS_1.57.531.7, but can't go anywhere and always stuck on Signature check 132 Error or 150 error
I did reboot boot loader and I did relock.
Tried also a Sideload rom, comes up with the error that is either insufficient space, can not read sideload. cant't push through adb either comes with error
Also is there a way to gain S-OFF in the bootloader only?
Looking forward to your thoughts and possible solution.
Many thanks
Also: when i run the relock command this one comes up.
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.153s
Click to expand...
Click to collapse
Flash a custom ROM. Put the firmware and gapps on your sdcard.
I think he should just restore his phone to stock ROM after he flashed a custom ROM. If he doesn't know the difference between Vodafone and T-Mobile then I don't know... To make matters worst he knows he has no OS on his device and then he goes to try and lock the bootloader, in the hopes of achieving what?
Put a ROM on a SD card, flash it through custom recovery, download a stock ROM for your device from the Collection thread in General section. Restore the device back to stock and rather leave the flashing until you read up on the basics and get a better understanding of these things before you really mess up mate.
Thank guys,
I have tried T-mobile because i found somewhere in the forum. I thought it was a bit strange.
Customer roms don't work either. comes up with errors, can not mount cache.
I don't really know where to start any help would be much appreciated.
Never had issues with other android phones but this one is tough.
arnasx69 said:
Thank guys,
I have tried T-mobile because i found somewhere in the forum. I thought it was a bit strange.
Customer roms don't work either. comes up with errors, can not mount cache.
I don't really know where to start any help would be much appreciated.
Never had issues with other android phones but this one is tough.
Click to expand...
Click to collapse
Make sure bootloader is UNLOCKED, and keep it unlocked (only relock if you need to return phone to HTC)
What custom rom did you try? what custom recovery do you have?
RossMacgill said:
Make sure bootloader is UNLOCKED, and keep it unlocked (only relock if you need to return phone to HTC)
What custom rom did you try? what custom recovery do you have?
Click to expand...
Click to collapse
Clockwork Recovery
tried all sort of roms, just tried to put android_revolution_HD, aroma installer went fine which was an improvement. but still stuck on HTC one logo again.
UPDATE: OK managed to get in the stock rom working. But no WIFI is not working. Tried to update to the newest firmware and it comes up with incorrect model ID.
arnasx69 said:
Clockwork Recovery
tried all sort of roms, just tried to put android_revolution_HD, aroma installer went fine which was an improvement. but still stuck on HTC one logo again.
UPDATE: OK managed to get in the stock rom working. But no WIFI is not working. Tried to update to the newest firmware and it comes up with incorrect model ID.
Click to expand...
Click to collapse
wifi is not working because you have installed the newest version, use the version you had before, like 4.4.2/4.4.3 etc that way you can then update to latest firmware.
arnasx69 said:
Clockwork Recovery
tried all sort of roms, just tried to put android_revolution_HD, aroma installer went fine which was an improvement. but still stuck on HTC one logo again.
UPDATE: OK managed to get in the stock rom working. But no WIFI is not working. Tried to update to the newest firmware and it comes up with incorrect model ID.
Click to expand...
Click to collapse
RossMacgill said:
wifi is not working because you have installed the newest version, use the version you had before, like 4.4.2/4.4.3 etc that way you can then update to latest firmware.
Click to expand...
Click to collapse
Also, your MID (model id) and CID must match the firmware you are flashing since you are not S-off, and therefore not superCID.
In fastboot and hooked up to your PC in ADB, type fastboot getvar all. The output it gives you will tell you your CID and MID(modelid).
Then look for firmware that matches those.
Or get S-off with sunshine (best $25 you will spend on your phone), and go superCID to flash firmware from any carrier.
Thank you guys for your support. my version list is bellow. So which is the correct firmware version am I looking for?
Got confused again about MID and CID matching numbers
Thank you
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxx
(bootloader) imei: xxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP001
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
arnasx69 said:
Thank you guys for your support. my version list is bellow. So which is the correct firmware version am I looking for?
Got confused again about MID and CID matching numbers
Thank you
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxx
(bootloader) imei: xxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP001
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
This is your MID modelid: 0P6B10000
THIS IS your CID cidnum: VODAP001
Check those guides http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
http://http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
http://forum.xda-developers.com/showthread.php?t=2736921
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048 And for the record, HTC phones are not tough to work on( s-off,firmware,recovery,etc) if you can read the guides before you do anything.
Gunman84 said:
This is your MID modelid: 0P6B10000
THIS IS your CID cidnum: VODAP001
Check those guides http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
http://http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
http://forum.xda-developers.com/showthread.php?t=2736921
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048 And for the record, HTC phones are not tough to work on( s-off,firmware,recovery,etc) if you can read the guides before you do anything.
Click to expand...
Click to collapse
Thank you for your sarcastic reply. I went through all guides before posting this. But in non of the guides explains how to match these numbers to get a "matching firmware"
Thank you
also éven if he would try on s-on a T-Mobile RUU von vodafone cid it would never work
if you really don't know how to Flash custom roms etc properly please Keep your phone stock!
If you got the stock Rom working i would go S-Off with Sunshine and go Super CID (11111111) with Sunshine.
Then you can flash what ever Rom you want.
arnasx69 said:
Thank you for your sarcastic reply. I went through all guides before posting this. But in non of the guides explains how to match these numbers to get a "matching firmware"
Thank you
Click to expand...
Click to collapse
I'm sorry but you probably missed something. What i would is, S-off, Super CID(fastboot oem writecid 11111111) Super CID "allows you to flash ANY ROM to the device regardless of the carrier" (taken straight from the S-OFF sticky). You can certainly S-OFF, install custom recovery, and begin flashing custom ROMs without Super CID, but you will be limited in your choice of ROMs to those that are the same carrier as you have
CID is the Country Identifier, a code which is stored on your phone and software uses to determine which country or region the phone is for. HTC updates, for example, use it to determine (among other things) which languages to install.
SuperCID is a special code, 11111111, which means that software from any region can be installed. Last, flash recovery and flash new rom
Gunman84 said:
I'm sorry but you probably missed something. What i would is, S-off, Super CID(fastboot oem writecid 11111111) Super CID "allows you to flash ANY ROM to the device regardless of the carrier" (taken straight from the S-OFF sticky). You can certainly S-OFF, install custom recovery, and begin flashing custom ROMs without Super CID, but you will be limited in your choice of ROMs to those that are the same carrier as you have
CID is the Country Identifier, a code which is stored on your phone and software uses to determine which country or region the phone is for. HTC updates, for example, use it to determine (among other things) which languages to install.
SuperCID is a special code, 11111111, which means that software from any region can be installed. Last, flash recovery and flash new rom
Click to expand...
Click to collapse
Actually, CID is Carrier ID, not country identifier.. That's why his says VODAP001 (his carrier being Vodafone) and not his country (whichever of the 21 countries Vodafone is available in)
arnasx69 said:
Thank you guys for your support. my version list is bellow. So which is the correct firmware version am I looking for?
Got confused again about MID and CID matching numbers
Thank you
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP001
Click to expand...
Click to collapse
Why don't you do the easy way :
1. Flash TWRP - link in my sig
2. Download the stock nandroid backup for your CID/MID - software version no. 2.22.161.6
http://forum.xda-developers.com/showpost.php?p=55302130&postcount=1884
3. Restore that nandroid backup
4. Fastboot flash the stock recovery for 2.22.161.6 - link as above
5. Do OTA to 4.4.4 - software version no. 3.29.161.5
6. Once complete - then you decide whether you want keep it stock or flash custom ROM.
7. If you want to flash custom ROM
a- flash the TWRP again
b- install any GSM based 4.4.4 ROM of your choice - everything should work including wifi
Note : on any case above - no need and don't relock bootloader
ckpv5 said:
Why don't you do the easy way :
1. Flash TWRP - link in my sig
2. Download the stock nandroid backup for your CID/MID - software version no. 2.22.161.6
http://forum.xda-developers.com/showpost.php?p=55302130&postcount=1884
3. Restore that nandroid backup
4. Fastboot flash the stock recovery for 2.22.161.6 - link as above
5. Do OTA to 4.4.4 - software version no. 3.29.161.5
6. Once complete - then you decide whether you want keep it stock or flash custom ROM.
7. If you want to flash custom ROM
a- flash the TWRP again
b- install any GSM based 4.4.4 ROM of your choice - everything should work including wifi
Note : on any case above - no need and don't relock bootloader
Click to expand...
Click to collapse
Best answer I could ever get. Thank you to all who helped me to solve by it looks very simple issue.
And last one is there a way to go back to LOCKED with S-ON, from what I see Firewater is not supporting my phone.
Thanks
arnasx69 said:
Best answer I could ever get. Thank you to all who helped me to solve by it looks very simple issue.
And last one is there a way to go back to LOCKED with S-ON, from what I see Firewater is not supporting my phone.
Thanks
Click to expand...
Click to collapse
No only with sunshine possible, made by same devs but costs 25$ but will 100% s-off your device
Sent from my HTC One m8 with lollipop and Dolby Mobile Plus!
One-M8-Master said:
No only with sunshine possible, made by same devs but costs 25$ but will 100% s-off your device
Sent from my HTC One m8 with lollipop and Dolby Mobile Plus!
Click to expand...
Click to collapse
Not true, not 100 %. Maybe V3 will do that. Keep in mind that the version of sunshine that is now on the market is not working with all the devices.
Related
How do I go back to stock sense?
After rooting my device, I downloaded a few roms and none of them worked except Skydragon.
I'm getting kinda tired of the stock lollipop and want to go back to sense but I cant. The other roms get me stuck on bootloader.
I tried downloading the RUU 0p6bimg.zip to revert back to stock but I wasnt able to transfer it to my SD card. I then downloaded it directly to my sdcard and went into hboot.
hboot says the file is too big and wont let me do anything.
I'm S-ON
Unlocked
version-bootloader: 3.19.0.0000
version-main: 3.11.1700.5
product: m8_ul_ca
modelid:0P6B12000
cidnum: CWS__001
also if it matters, I was on TWRP 2.7.0.2 but now im on CWM 6.0.4.8
help pls.
Its exactly the same as it was on your HOX. Get a matching nand backup to restore. You know the basics, how to do it and such.....been coverering that before
http://forum.xda-developers.com/showthread.php?t=2701376
Here you have some info
Mr Hofs said:
Its exactly the same as it was on your HOX. Get a matching nand backup to restore. You know the basics, how to do it and such.....been coverering that before
http://forum.xda-developers.com/showthread.php?t=2701376
Here you have some info
Click to expand...
Click to collapse
I'm at my wits end. I really dont understand this. Ive tried everything I know how. Can you just point to which things I need to download cause im working on trial and error here. :||||||
Can you post your entire fastboot getvar all output (minus the IMEI and S/N) please? Looks like you are running the GPe ROM
EddyOS said:
Can you post your entire fastboot getvar all output (minus the IMEI and S/N) please? Looks like you are running the GPe ROM
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-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: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s\
Heres all I have tried so far:
1) flashing different firmwares but they keep failing. (yes, I ran it twice, sometimes more) Im not sure whether getting the right firmware will help, I saw somewhere it does. Am I using the wrong ones?
2) I tried RUUs as well, but it fails at 1/7. The last one I checked said it would update to 4.16.1540.8, then said please get the right RUU. :S
I'm not sure which that is.
3) several different recovery files as well, including stock ones and running Sense-based roms and supersu after. The phone reboots back into recovery mode.
1. It will fail if you don't use the one originally for your devices CID
2. There aren't any RUUs for the M8_UL_CA
3. You need to find the one that matches your CID
Shiverfire said:
Heres all I have tried so far:
1) flashing different firmwares but they keep failing. (yes, I ran it twice, sometimes more) Im not sure whether getting the right firmware will help, I saw somewhere it does. Am I using the wrong ones?
2) I tried RUUs as well, but it fails at 1/7. The last one I checked said it would update to 4.16.1540.8, then said please get the right RUU. :S
I'm not sure which that is.
3) several different recovery files as well, including stock ones and running Sense-based roms and supersu after. The phone reboots back into recovery mode.
Click to expand...
Click to collapse
It looks like your device is originally AT&T
1. If you want to try to flash firmware only, you need to relock bootloader
download the signed firmware here : http://forum.xda-developers.com/att-htc-one-m8/general/att-4-4-4-firmware-signed-encrypted-t3031703
fastboot oem rebootRUU
fastboot flash zip ATT444firmware.zip
fastboot flash zip ATT444firmware.zip .....( again for the 2nd time)
fastboot reboot-bootloader
see whether you can successfully flash this firmware. If yes, you can try option 2.
2. RUU - still you need to relock bootloader and run this RUU (run as Administrator)
http://forum.xda-developers.com/showpost.php?p=58949364&postcount=36
3. You need to revert your partition to Sense partition then only you can restore/flash Sense based ROMs/backup
Means you need that option 1 or option 2
They're S-ON, so it's not a full conversion
Based on android-info.txt for GPE
modelid: 0P6B10000
modelid: 0P6B11000
modelid: 0P6B12000
modelid: 0P6B13000
modelid: 0P6B11000
modelid: 0P6B15000
modelid: 0P6B16000
modelid: 0P6B17000
cidnum: GOOGL001
cidnum: 11111111
cidnum: CWS__001
cidnum: T-MOB010
mainver: 3.11.1700.5
Any device with CID/MID as OP has, can run a signed GPE RUU with S-On
I don't know whether OP can revert to Sense from GPE when the signed firmware has same CID/MID ... and no harm to try as OP has a S-On device. Maybe can because same hboot version 3.19.0000 and maybe cannot because of software version (cannot downgrade from lollipop to 4.4.4)
okay so basically i need to relock my bootloader, flash a different firmware and then I can install a Sense Rom, correct?
Am I understanding this correctly? Relock bootloader, flash firmware, unlock bootloader again, install rom.
Will the firmware you linked above (http://forum.xda-developers.com/att-htc-one-m8/general/att-4-4-4-firmware-signed-encrypted-t3031703) be able to install a ROM like the latest Viper or the latest Android Revolution? Im only assuming it would be like this:
Also, can someone tell me what I needed to write to relock the bootloader please?
Before we talk about flashing other ROM, you need to try whether you can successfully flash the signed firmware or not. If successful, this will take you to Sense 4.4.4 not lollipop. If fails, then you need a lollipop firmware for your device version. Don't you remember anything about your original software before GPE ... or your device is original GPE ? Which is which now ? If it is original GPE, then nothing you can do to convert to Sense without S-Off (I assume original is not GPE because you first question is "How do I go back to stock sense?")
You need the one that said "Stock signed/encrypted (includes stock boot and recovery)"
My device was originally Sense. I installed Skydragon and Android Revolution back then but wasn't getting wifi. I updated my firmware, but only Skydragon seemed to be working after I did so. I havent been able to go to any Sense ROMs since.
I guess so ... you wrongly flashed a signed GPE firmware. That is why you can only install a GPE ROM.
So.. can't you remember at all what device that you have ?
Try that option 1 and see how it goes.
ckpv5 said:
I guess so ... you wrongly flashed a signed GPE firmware. That is why you can only install a GPE ROM.
So.. can't you remember at all what device that you have ?
Try that option 1 and see how it goes.
Click to expand...
Click to collapse
Okay, I relocked and flashed the firmware.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.42.502.1
(bootloader) version-misc: PVT SHIP S-ON
(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: 56f9ae32
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s
what do I do now?
Shiverfire said:
Okay, I relocked and flashed the firmware.
what do I do now?
Click to expand...
Click to collapse
This means your device is AT&T .. now your partition is back to Sense partition.
But this is only a 4.4.4 firmware because there is no lollipop 5.0.1 for AT&T yet for now.
If you want to revert everything to stock Sense, do option 2. Remember your first question is "How do I go back to stock sense?" and your thread title "Returning to stock sense" .... I help you to achieve this. More than this, I'm not so sure as I'm not familiar with AT&T device.
If you want to try any lollipop base custom ROM, you need to re-unlock the bootloader and flash TWRP - use 2.8.3.0 (not sure whether 2.8.4.0 & 2.8.5.0 can work on 4.4.4 or not), most important never ever use your old TWRP 2.7.0.2
then you can install that custom ROM .. and see any problem with wifi or not. I cannot help on custom ROM matter as I don't use one.
I suggest you do option 2, re-unlock, flash TWRP and make a backup of your stock ROM before you try that custom lollipop ROM..
ckpv5 said:
This means your device is AT&T .. now your partition is back to Sense partition.
But this is only a 4.4.4 firmware because there is no lollipop 5.0.1 for AT&T yet for now.
If you want to revert everything to stock Sense, do option 2. Remember your first question is "How do I go back to stock sense?" and your thread title "Returning to stock sense" .... I help you to achieve this.
If you want to try any lollipop base custom ROM, you need to re-unlock the bootloader and flash TWRP - use 2.8.3.0 (not sure whether 2.8.4.0 & 2.8.5.0 can work on 4.4.4 or not), most important never ever use your old TWRP 2.7.0.2
then you can install that custom ROM .. and see any problem with wifi or not. I cannot help on custom ROM matter as I don't use one.
I suggest you do option 2, re-unlock, flash TWRP and make a backup of your stock ROM before you try that custom lollipop ROM..
Click to expand...
Click to collapse
Ok so, let me understand. Option 2 means I need to relock and run the RUU as administrator. After that I can run any Sense ROM even if its the new Lolipop sense roms? Or can only 4.4.4 roms work?
If its the ladder, can I simply relock and install a 4.4.4 custom sense ROM? Will that work?
If you want to run custom ROM, then no need option 2.
As I said earlier ...you need to re-unlock the bootloader and flash TWRP - use 2.8.3.0 (not sure whether 2.8.4.0 & 2.8.5.0 can work on 4.4.4 or not), most important never ever use your old TWRP 2.7.0.2
You can try lollipop. If it is not running perfect for your device then any Sense custom base 4.4.4 ROM should work. (e.g.- http://forum.xda-developers.com/showthread.php?t=2748588)
the lollipop roms worked! thank you!!
I have tried to install a new custom ROM on my HTC One M8.
It has a unlocked bootloader, it's unlocked, rooted, and i've had InsertCoin and Paranoid Android, and CyanogenMod on it.
My device is S-ON.
However, lately I have not been able to update to any of the newer roms.
The ROMs that I have tried to install are:
HTC_One_(M8)_-_MaximusHD_11.0.0
insertcoin-m8_5.0.3_ART
ViperOneM8_4.2.0_v2
And none of them work except for
pa_m8-4.45-20140729
which is always my go-to ROM right now when the others fail so I don't soft brick it.
I do have a Nandroid in case everything goes to hell.
But my question is, what is wrong with my device and why can't I update to another ROM? It gets stuck at the HTC White Logo screen every single time with every ROM that fails.
Thanks!
technocrat7 said:
But my question is, what is wrong with my device and why can't I update to another ROM? It gets stuck at the HTC White Logo screen every single time with every ROM that fails.
Thanks!
Click to expand...
Click to collapse
You have old hboot and firmware version.
All the newer Sense based ROM require hboot no less than 3.19.0000
What's your fastboot getvar all - post here minus serial no. & imei no.
Maybe lollipop OTA already available for your device region.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA24G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.57.531.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Here is my information on my phone, so it would seem that I am outdated. How would I get back up to date?
Here is the RUU for your device version : http://forum.xda-developers.com/showpost.php?p=58771521&postcount=4593
This will update your device to the latest lollipop 4.20.531.4
1. put your device in bootloader/fastboot mode and connect to PC
2. run command to relock bootloader
fastboot oem lock
fastboot reboot-bootloader
3. Right click the RUU exe that you downloaded, select "run as administrator" .. wait for it to run, later there is a dialog box, accept, next, next, update, blablabla until it finish and your device rebooted... done.
Note : this will wipe everything on your internal storage. Make a backup of important files before you proceed.
Then if you want to install custom ROM again, re-unlock bootloader & install any custom recovery that you like.
Thanks! I did what you said, then this happened:
C:\adb>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.127s
Is this supposed to happen?
it says RELOCKED at the top though
technocrat7 said:
Is this supposed to happen?
it says RELOCKED at the top though
Click to expand...
Click to collapse
Yep ... just proceed to install RUU (step 3)
Okay thank you, Also I wanted to ask you, how exactly did you find my RUU?
I saw the cidnum was TMOBO010 or whatever it was, but how exactly did you use that to find my RUU?
Thanks again for the help, much appreciated
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
These are the 3 items that important to check what you need.
I don't really need to search for it because I'm always around in this thread : http://forum.xda-developers.com/showthread.php?t=2701376
and it happens that I just helped other person there with more or less same problem as yours.
BTW ... please remove those sensitive data (serial no. & imei no.) from your post above.
I did what you asked.
And okay I will keep that in mind
**EDIT**
Also, do I need to "re unlock" my phone? Or can I just do "fastboot oem unlock" because I have once before unlocked it?
This IS a relock right?
technocrat7 said:
Also, do I need to "re unlock" my phone? Or can I just do "fastboot oem unlock" because I have once before unlocked it?
This IS a relock right?
Click to expand...
Click to collapse
No .. you need to unlock it with the unlock_code.bin that you received from HTCDev when you first unlock your device.
If you don't have it, reapply a new one.
I see, okay I unlocked it again.
While I'm at it, I wanted to ask one final question that's been bugging me for a while now.
When I got to my Philz recovery and do "factory wipe" why doesn't it actually wipe my data?
I want ALL of my data, ROM, apps, everything to be gone, but it doesn't do that.
Is there an alternative?
Is there no way to remove all user data/apps?
I don't use Philz recovery so not sure how to help you. Maybe try an older version 6.26.6
I use only TWRP and now your device already updated to 5.0.1; you need to use TWRP 2.8.4.0 or the latest 2.8.5.0
Okay I am on TWRP, how do I do a factory reset on TWRP?
and what exactly will it do?
I just hope it'll actually wipe everything when I factory reset it. Or else I don't see a point of even having a factory reset option
It's all depends on what you want to do.
Factory reset - to prepare your device to install next ROM, it wipes user data, cache, dalvik cache
I always prefer - wipe menu - advance - select data, cache, dalvik, system - this wipe everything except internal storage.
To wipe data and internal storage - wipe menu - advance - format data - yes
I got to go now ... bed time
Thank you that's all I needed to know.
I appreciate the help, goodnight!
technocrat7 said:
Thank you that's all I needed to know.
I appreciate the help, goodnight!
Click to expand...
Click to collapse
No problem ... and it's already good day here
Haha I see.
Do you know any information on the OnePlus?
I made a post there, however it's not a very active forum.
Sent from my HTC One_M8 using XDA Free mobile app
No idea about any other brand phone ... I use only HTC since 2008 when I first registered with XDA with my first HTC Elf
Haha interesting, I started with the Droid DNA being my first HTC device, and that thing was so bad it almost never make me want to go HTC again. But I got my M7
And staying on topic... If you have a different kernel on your device, would you still be able to RUU it? Or would you have to revert the kernel back?
Sent from my HTC One_M8 using XDA Free mobile app
RUU - no need
OTA - need to revert to stock kernel/modules if modules are changed. If modules are stock, then no need
Helllo there!
I'm making a new thread because I couldn't find anyone with the exact same problem and don't want to brick my phone or such.
Now to the problem: every time I try to update my HTC one m8 (Europe) it stops when installling and tells me this:
Code:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
L50QCT.01.101.007
Package expects build fingerprint of htc/htc_europe/htc_m8:4.4.4/KTU84P/389838.9:user/release-keys
or htc/htc_europe/htc_m8:5.0.1/LRX22C/448934.10:user/release-keys;
this device has htc/htc_europe/htc_m8:4.4.4/KTU84P/389838.6:user/release-keys.
Installation aborted.
Write host_mode 0 done
getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__102
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
The phone is rooted, the bootloader unlocked, it has the stock recovery, it's s-on and it says "software status: modified".
The only thing I can see in the error is that this nine:
Code:
htc/htc_europe/htc_m8:4.4.4/KTU84P/389838.[B][U]9[/U][/B]:user/release-keys
is a six
Code:
htc/htc_europe/htc_m8:4.4.4/KTU84P/389838.[B][U]6[/U][/B]:user/release-keys
on mine.
I am pretty new here still, so i don't know how to fix it, and i don't want to break it.
Best regards
Schmix
Root phone
vinayluck said:
Root phone
Click to expand...
Click to collapse
What are you trying to say?
Schmix said:
What are you trying to say?
Click to expand...
Click to collapse
You should post your getvar all (deleting your imei number and S./N ) there is a post here but it is in german with the same problem which points to an incorrect recovery!
http://www.android-hilfe.de/wiederh...ge-expects-build-fingerprint-fingerprint.html
Shepps
vinayluck said:
Root phone
Click to expand...
Click to collapse
Being rooted or not has no bearing on OTA update.
Also, it seems that you are trying to tell the OP to root (not completely clear, with the 2 word post), when he clearly states he is already rooted.
Getvar info added!
By the way, the other guy had a different problem.
Has anyone got an idea of whats wrong?
Schmix said:
Helllo there!
I'm making a new thread because I couldn't find anyone with the exact same problem and don't want to brick my phone or such.
Now to the problem: every time I try to update my HTC one m8 (Europe) it stops when installling and tells me this:
Code:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
L50QCT.01.101.007
Package expects build fingerprint of htc/htc_europe/htc_m8:4.4.4/KTU84P/389838.9:user/release-keys
or htc/htc_europe/htc_m8:5.0.1/LRX22C/448934.10:user/release-keys;
this device has htc/htc_europe/htc_m8:4.4.4/KTU84P/389838.6:user/release-keys.
Installation aborted.
Write host_mode 0 done
getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__102
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
The phone is rooted, the bootloader unlocked, it has the stock recovery, it's s-on and it says "software status: modified".
The only thing I can see in the error is that this nine:
Code:
htc/htc_europe/htc_m8:4.4.4/KTU84P/389838.[B][U]9[/U][/B]:user/release-keys
is a six
Code:
htc/htc_europe/htc_m8:4.4.4/KTU84P/389838.[B][U]6[/U][/B]:user/release-keys
on mine.
I am pretty new here still, so i don't know how to fix it, and i don't want to break it.
Best regards
Schmix
Click to expand...
Click to collapse
Download and run the 3.28.401.10 RUU first (a quick search here and you'll find it), then run this one.
Schmix said:
Getvar info added!
By the way, the other guy had a different problem.
Has anyone got an idea of whats wrong?
Click to expand...
Click to collapse
Wrong stock recovery image.
OTA needs stock recovery 3.28.401.9 (389838.9) or 4.16.401.10 (448934.10)
but you installed 3.28.401.6 (389838.6)
Get the right recovery image, OTA will proceed.
I have one here - 3.28.401.9_recovery.img : http://sourceforge.net/projects/htconem8/files/Recovery/3.28.401.9_recovery.img/download
ckpv5 said:
Wrong stock recovery image.
OTA needs stock recovery 3.28.401.9 (389838.9) or 4.16.401.10 (448934.10)
but you installed 3.28.401.6 (389838.6)
Get the right recovery image, OTA will proceed.
I have one here - 3.28.401.9_recovery.img : http://sourceforge.net/projects/htconem8/files/Recovery/3.28.401.9_recovery.img/download
Click to expand...
Click to collapse
Okay thank you so far!
But now it comes up with a different error; It says "/system/xbin/nc has unexpected contents".
Let me tell you the whole story:
Some time ago i installed busybox, xposed and xprivacy (and luckypatcher) and used it normaly.
Then the Lollipop update came around and since it wasnt working (giving out the unexpected contend error) i thought it would be a good idea to just do a factory reset.
It didnt work afterwards either, so i went here to ask what the problem was, and i was told it was because of xposed.
However, xposed wasn't installed anymore (the app), and (i think) the newer versions installed it somewhere else, so installing and then uninstalling (the button in the app) it didnt delete the old directory. (Btw. in an last attempt i tried installing the stick recovery and got the wrong one apparently)
So yeah, i have no idea on how to fix this problem, but i would be okay with having to reset my phone.
Schmix said:
But now it comes up with a different error; It says "/system/xbin/nc has unexpected contents".
So yeah, i have no idea on how to fix this problem, but i would be okay with having to reset my phone.
Click to expand...
Click to collapse
That's expected
There are a few methods to solve your problem.
The easiest one is RUU it back to stock.
Follow this thread : http://forum.xda-developers.com/showthread.php?t=2735235
You need to relock bootloader and also make a backup of your internal storage files/pic/music or whatever you like to keep.
The RUU will update your device to the latest
ckpv5 said:
That's expected
There are a few methods to solve your problem.
The easiest one is RUU it back to stock.
Follow this thread : http://forum.xda-developers.com/showthread.php?t=2735235
You need to relock bootloader and also make a backup of your internal storage files/pic/music or whatever you like to keep.
The RUU will update your device to the latest
Click to expand...
Click to collapse
But i don't have S-Off... is that a problem?
And are the files correct?
Schmix said:
But i don't have S-Off... is that a problem?
And are the files correct?
Click to expand...
Click to collapse
You don't have S-Off - that's why you need to relock bootloader
That's the only difference - read the thread thoroughly.
First step - relock bootloader with command fastboot oem lock
then follow the step 3 onwards
Also note you need to use htc_fastboot.exe not the usual fastboot.exe
Anything you need to ask, you can ask there. I believe @EddyOS will gladly help you
ckpv5 said:
You don't have S-Off - that's why you need to relock bootloader
That's the only difference - read the thread thoroughly.
First step - relock bootloader with command fastboot oem lock
then follow the step 3 onwards
Also note you need to use htc_fastboot.exe not the usual fastboot.exe
Anything you need to ask, you can ask there. I believe @EddyOS will gladly help you
Click to expand...
Click to collapse
Keep meaning to add a few bits that can be done with S-ON, been super busy of late!
ckpv5 said:
You don't have S-Off - that's why you need to relock bootloader
That's the only difference - read the thread thoroughly.
First step - relock bootloader with command fastboot oem lock
then follow the step 3 onwards
Also note you need to use htc_fastboot.exe not the usual fastboot.exe
Anything you need to ask, you can ask there. I believe @EddyOS will gladly help you
Click to expand...
Click to collapse
Thank you very much, I got it to work now!
Have a good day!
ckpv5 said:
Wrong stock recovery image.
OTA needs stock recovery 3.28.401.9 (389838.9) or 4.16.401.10 (448934.10)
but you installed 3.28.401.6 (389838.6)
Get the right recovery image, OTA will proceed.
I have one here - 3.28.401.9_recovery.img : http://sourceforge.net/projects/htconem8/files/Recovery/3.28.401.9_recovery.img/download
Click to expand...
Click to collapse
I have the same issue with my htc desire 820n can you help me pleas
ammarhigh said:
I have the same issue with my htc desire 820n can you help me pleas
Click to expand...
Click to collapse
I believe you do know this is M8 thread and not HTC Desire 820n
But .. this is what you can do to fix your problem ...
Check for OTA as usual, download OTA then select install later.
Connect your device to PC then copy the OTA zip from internal storage\download folder to PC
Open the OTA zip with 7-zip, you'll see firmware.zip. Open firmware.zip and extract out recovery.img <--- this is the one that you need.
Boot your device to bootloader
Fastboot flash this extracted recovery.img
Reboot, check for OTA again, this time select install now
Done
I'm sorry for posting here but i did it and it's not working when i'm flashing the recovery i tooked it from the OTA it's give me error when flashing it the update is lollipop and i'm on kitkat 4.4.4
Sent from my HTC Desire 820 using XDA Free mobile app
Forget this sorted it all out, now running SRom ported lollipop with sense 7 from the M9. Hboot no red text and faux locked/original/son. Super CID.
For the record, it's always a firmware/dalvic cache problem (98%)
Hi Guys so Im rooted running Android Revoluton HD ROMs on an international O2 phone S-on
I thought I would wipe the entire phone, bleach it like a PC and reinstall.
Not a problem except various elements dont work.
I installed Stock ROM (I think KitKat)
I installed ARHD 22. (Kit Kat) everything worked
I installed ARHD 34.(Jellybean Sense 6) no wifi
I installed ARDH 40.(Jellybean Sense 7) no HTC TV
I installed ARHD 41.(Jellybean Sense7) no images in Blinkfeed?
I know its probably because I wiped the misc folder but up until I did a clean wipe I could use all of these roms without a glitch.
So is it firmware?
What do I need to put back on my phone for them all to work
I am S-on at the moment and I know that isnt whats stopping these roms working.
Any suggestions?
eskimosound said:
Hi Guys so Im rooted running Android Revoluton HD ROMs on an international O2 phone S-on
I thought I would wipe the entire phone, bleach it like a PC and reinstall.
Not a problem except various elements dont work.
I installed Stock ROM (I think KitKat)
I installed ARHD 22. (Kit Kat) everything worked
I installed ARHD 34.(Jellybean Sense 6) no wifi
I installed ARDH 40.(Jellybean Sense 7) no HTC TV
I installed ARHD 41.(Jellybean Sense7) no images in Blinkfeed?
I know its probably because I wiped the misc folder but up until I did a clean wipe I could use all of these roms without a glitch.
So is it firmware?
What do I need to put back on my phone for them all to work
I am S-on at the moment and I know that isnt whats stopping these roms working.
Any suggestions?
Click to expand...
Click to collapse
It's firmware. You most probably have kitkat firmware and lolipop based roms will mess up your wifi and stuff. Take an ota or stay on kitkat.
Thanks will try
Do I just flash the zip file?
Im sure I probs do
eskimosound said:
Thanks will try
Do I just flash the zip file?
Im sure I probs do
Click to expand...
Click to collapse
If you are S-ON don't flash firmware. Just don't. You can flash rom zips, recoveries, kernels. You can write on these partitions with s-on: recovery, boot, system and data.
I've just used Sunshine to get S-off, what a joy to use!
So now I can just flash them right?
I've got my cid number matched it up with the ota and bingo?
Right?
eskimosound said:
I've just used Sunshine to get S-off, what a joy to use!
So now I can just flash them right?
I've got my cid number matched it up with the ota and bingo?
Right?
Click to expand...
Click to collapse
well im come from HTC One M7, and as long as the M8 is pretty much the same, you dont need s-off to flash the same firmware which your already on, or the next one step up, after all, this is exactly what an OTA does for you.
However, now your s-off anyway, you canflash any RUU or firmware you like, just make sure cid and mid match first. :good:
EDIT: there ia also no need to lock or re-lock the bootloader to flash anything now that your S-off, leave it unlocked all the time for everything, its a common problem on the M7 forums at the moment, people who are s-off or even s-on, locking bootloaders with custom rom's or recovery's on thier phones.
Thanks, so with the ota there are two for O2 my cid is O2___001 am I right that I can take the 001 OR the 002?
eskimosound said:
Thanks, so with the ota there are two for O2 my cid is O2___001 am I right that I can take the 001 OR the 002?
Click to expand...
Click to collapse
in all honesty, I would of thought the CID 001 and 002 were in the same ota, have you checked the android-info.txt file within the OTA itself, its just a zip file.
possible to post your fastboot getvar all without imei and serial number please, also a link to the OTA's your downloading would be good.
Well I've just tried to flash both....I enter recovery instal zip right?
It's giving me an error.
Will tell you that info in a minute when I get on my pc
eskimosound said:
Well I've just tried to flash both....I enter recovery instal zip right?
It's giving me an error.
Will tell you that info in a minute when I get on my pc
Click to expand...
Click to collapse
personnaly, if your just trying to get to Lollipop, I would change my CID to HTC__001 (thats 2 underscores, CID is always 8 digits)
Change MID if required.
and then flash the WWE International Lollipop full RUU, piece of cake. http://forum.xda-developers.com/htc-one-m8/general/htc-one-m8-european-signed-ruu-0p6bimg-t2911563
But if the original isn't flashing what hope have I got with an HTC one. It's interesting to know though that I can change it.
So what next?
Oh hang on I will post my stats
OK Guys,
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.206.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: O2___001
(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: dcdaa6e0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.028s
eskimosound said:
But if the original isn't flashing what hope have I got with an HTC one. It's interesting to know though that I can change it.
So what next?
Oh hang on I will post my stats
Click to expand...
Click to collapse
Flashing an OTA manually is a different kettle of fish, its just an OTA not a full RUU, and you would still have to be full stock in order for it to succeed.
however, if you just require the firmware in order to use a custom LP rom, then just pull the firmware.zip out of the OTA and flash it.
you would then have to put a custom recovery back on your phone, copy a rom to your sdcard, and flash it from within TWRP recovery.
And im trying to flash O2 OTA
for here
http://forum.xda-developers.com/showthread.php?t=2701376
eskimosound said:
OK Guys,
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.206.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: O2___001
(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: dcdaa6e0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.028s
Click to expand...
Click to collapse
you already have the latest firmware on your phone !!!
I installed ARHD 41.( Sense7) no images in Blinkfeed? ------ pulled from your first post, this is a common problem, if you mean its face ache, there is a fix for it on playstore.
OK is tere an RUU for O2 uk?
So im extracting the firmware at the mo, then I will flash it then I will try and install ARHD 41....
Im right that the O2___002 is an upgraded version of the 001 and its what I need right?
Otherwise im just replacing like for like.
eskimosound said:
OK is tere an RUU for O2 uk?
So im extracting the firmware at the mo, then I will flash it then I will try and install ARHD 41....
Im right that the O2___002 is an upgraded version of the 001 and its what I need right?
Otherwise im just replacing like for like.
Click to expand...
Click to collapse
nope O2___002 is a different cid, you need to use the 001 files, however, its the same as you already have on your phone.
CID is just carrier ID, so O2___001 will be something like O2 UK and 002 might be something like O2 france, no difference in files, just different regions.
Seanie280672 said:
nope O2___002 is a different cid, you need to use the 001 files, however, its the same as you already have on your phone.
Click to expand...
Click to collapse
So if its the same and ive got a problem its not the firmware right?
Or is it just an update.
I will tell you this is really easy but telling people how to do it is confusing
eskimosound said:
So if its the same and ive got a problem its not the firmware right?
Or is it just an update.
I will tell you this is really easy but telling people how to do it is confusing
Click to expand...
Click to collapse
nope its not your firmware, just checked a cid list, 002 is O2 DE, 001 is O2 UK http://forum.gsmhosting.com/vbb/f485/archive-htc-cid-list-1604812/
Make sure of a couple of things when flashing a custom ROM, check for problems other are having with it, by reading some of the later posts is what I always do, just a few pages, also and this is a must, read the OP's flashing instructions, so many people bypass this step, the most important step is to make sure your using the dev's recommended custom recovery for flashing.
I always full wipe before flashing anything, so in TWRP first factory reset, and then goto wipe - advanced - select everything except your internal storage and SDcard, and then always reboot back into recovery after the wipes before flashing the rom, it will nag you and say you have no OS installed, ignore it and Do Not Intall to SuperSU, the custom rom flash will do that for you.
During the rom installation, again I always select full wipe when given the option, you then know you have a clean slate to build the rom on.
eskimosound said:
So if its the same and ive got a problem its not the firmware right?
Or is it just an update.
I will tell you this is really easy but telling people how to do it is confusing
Click to expand...
Click to collapse
Your firmware is already current, and should work with latest ARHD. Blinkfeed not showing image is a known issue reported by others.
No need to mess with RUUs or firmware zips.
Hello I bought M8 from somebody, it is unbranded European model i think, phone is rooted and carrier unlocked as im using it in asia. it comes with android 5.0.1, I want to update to stock marshmallow for this variant. I have been trying to do on my own but it only confused me more. Im not sure if i have custom rom or if because im rooted, because At the time moment it doesnt offer any software updates from the main menu.
Some info abt phone.
Its model id at back is Op6B100,
Android version 5.0.1
Software number 4.18.708.12
Build number 4.18.708.12
In the bootloader menu I have
Software status: Official
Locked ( i think it means bootloader)
M8_UL PVt SHIp s-off
Cid-11111111 (but if I check with cidgetter it says t-mob010). So it confused me because according to its model its supposed to be european model but in fastboot it says 11111111.
HBoot 3.19.0.0000
I dont have twrp installed.
So please tell me where to go from here. I want to either from here go direct to stock android 6 for this M8 variant or go back to stock condition and get ota update. I prefer to lose the root. So please tell me which stock firmware I need, and do I need to change cid, remove root, before that? Also i would like not to brick my device in process.. Thanks.
Also my device is carrier unlocked at the moment so Im hoping this shouldn't affect that. Thanks
.??
Post fastboot getvar all result (delete serial & imei no. before posting) then someone will be able to help.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.708.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000 ( on the back its 0P6B100)
(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
all: Done!
I would like to install htc marshmallow update, kindly tell me how I can do that.
First you need to change MID to EU
Then install EU marshmallow RUU
Follow this guide - https://forum.xda-developers.com/showpost.php?p=70575580&postcount=12
Do i need twrp to change MId? And do I need to unlock bootloader before flashing RUU.
Kashi88 said:
Do i need twrp to change MId?
Click to expand...
Click to collapse
Yes as said in the guide unless you're running a rooted ROM.
Kashi88 said:
And do I need to unlock bootloader before flashing RUU.
Click to expand...
Click to collapse
No
ckpv5 said:
Yes as said in the guide unless you're running a rooted ROM.
No
Click to expand...
Click to collapse
ok thanks , I keep getting this error in the adb fastboot when flashing ruu zip . target reported max download size ( shows some big number bytes) .
Read the guide again .. you need htc_fastboot not normal fastboot.
At the end of the guide it shows 2 other methods on how to install RUU zip. Pick one thar you think it is easier for you.
ckpv5 said:
Read the guide again .. you need htc_fastboot not normal fastboot.
At the end of the guide it shows 2 other methods on how to install RUU zip. Pick one thar you think it is easier for you.
Click to expand...
Click to collapse
thank you so much i installed it with the micro sd method, and everything worked out smooth. just one last question, if in future i have to reset my phone from settings menu or from bootloader menu (volume down key), will I go back to android lollypop version or remain on this 6.0. thanks again
remain on this 6.0
ckpv5 said:
remain on this 6.0
Click to expand...
Click to collapse
hi..i am suffering from black bootloader issue..cant see any option..is there any solution?
dr.estiack said:
hi..i am suffering from black bootloader issue..cant see any option..is there any solution?
Click to expand...
Click to collapse
Please don't post the same question to multiple threads. It clutters up the forum, and makes it confusing for those trying to help you. Your post is also not related to the topic of this particular thread.