Related
Dear Community
As I wanted to update my ROM to Android 5, but with working WiFi, i tried to flash a new firmware. I'm on S-ON. My HBOOT is 3.16. After relocking and booting to RUU-Mode I attempted to flash the firmware.zip (version 4.19.161.2) which leaded to failure with error code 42. My CID is VODAP110 (Swisscom). After this not working i rebooted to fastboot, unlocked the bootloader again, reflashed recovery (philZ-touch, latest version). I tried to reboot and ended in a bootloop. So I went to recovery and reflashed the OS (SlimKat 4.4.4, build 8). After rebooting i was still in bootloop. I tried already to flush the cache, but this didn't help either.
Anybody had this experience or knows what to do, for bring my phone back to working? It mustnt be Android 5, but just working, so I can make phone calls again.
Also, here is my getvar all Dump:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *****
(bootloader) imei: *****
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP110
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.339s
Click to expand...
Click to collapse
Greetings,
Michael
ppcinj said:
Dear Community
As I wanted to update my ROM to Android 5, but with working WiFi, i tried to flash a new firmware. I'm on S-ON. My HBOOT is 3.16. After relocking and booting to RUU-Mode I attempted to flash the firmware.zip (version 4.19.161.2) which leaded to failure with error code 42. My CID is VODAP110 (Swisscom). After this not working i rebooted to fastboot, unlocked the bootloader again, reflashed recovery (philZ-touch, latest version). I tried to reboot and ended in a bootloop. So I went to recovery and reflashed the OS (SlimKat 4.4.4, build 8). After rebooting i was still in bootloop. I tried already to flush the cache, but this didn't help either.
Anybody had this experience or knows what to do, for bring my phone back to working? It mustnt be Android 5, but just working, so I can make phone calls again.
Also, here is my getvar all Dump:
Greetings,
Michael
Click to expand...
Click to collapse
Delete the Serial Number and the IMEI.
UniversalKID said:
Delete the Serial Number and the IMEI.
Click to expand...
Click to collapse
Could you please point me to an tutorial how to do so?
ppcinj said:
Could you please point me to an tutorial how to do so?
Click to expand...
Click to collapse
He means from your first post - it's not wise to show the IMEI and serial number of your device as someone could clone your phone
EddyOS said:
He means from your first post - it's not wise to show the IMEI and serial number of your device as someone could clone your phone
Click to expand...
Click to collapse
Oh, ok, thanks for the correction
ppcinj said:
Anybody had this experience or knows what to do, for bring my phone back to working? It mustnt be Android 5, but just working, so I can make phone calls again.
Greetings,
Michael
Click to expand...
Click to collapse
What you need is a 2.xx.166.x 1.xx.166.x backup, but I don't have any idea on the full no.
So to have a working phone so you can make a phone call, temporarily just restore any of the 2.xx.xxx.x 1.xx.xxx.x backup from this thread : http://forum.xda-developers.com/showthread.php?t=2701376
That's only a temp solution until you can find a right backup and firmware for your hboot 3.16.0000
If you want a Android for 5.0, you need firmware 4.19.166.2 which is available but I'm not sure whether you can jump from hboot 3.16.0000 directly to 3.19.0000
Jump should be fine, so long as it goes through without an error but I've gone from 3.16.0000 to 3.19.0000 having converted back from GPe to latest Lollipop RUU
EddyOS said:
Jump should be fine, so long as it goes through without an error but I've gone from 3.16.0000 to 3.19.0000 having converted back from GPe to latest Lollipop RUU
Click to expand...
Click to collapse
I know it's ok for S-Off device, just not sure about S-On. Let's see what OP intend to do now.
ckpv5 said:
I know it's ok for S-Off device, just not sure about S-On. Let's see what OP intend to do now.
Click to expand...
Click to collapse
Yeah, good point.
It shouldn't be a problem going UP a version but going down won't work without S-OFF...
ckpv5 said:
I know it's ok for S-Off device, just not sure about S-On. Let's see what OP intend to do now.
Click to expand...
Click to collapse
Ok, but what exactly do I need now? Could you help me out finding the right file? I found backups for 2.x.161.x, but not for 2.x.166.x... And also what are the most secure steps for me to do now for avoiding a brick? Flashing the new 4.x.x.x so i can haz Android 5 or reverting to 2.x.x.x and stick with Android 4?
And also if you need some more data, screenshots, etc. feel free to ask for them
ppcinj said:
Ok, but what exactly do I need now? Could you help me out finding the right file? I found backups for 2.x.161.x, but not for 2.x.166.x... And also what are the most secure steps for me to do now for avoiding a brick? Flashing the new 4.x.x.x so i can haz Android 5 or reverting to 2.x.x.x and stick with Android 4?
And also if you need some more data, screenshots, etc. feel free to ask for them
Click to expand...
Click to collapse
I wrote "just restore any of the 2.xx.xxx.x 1.xx.xxx.x backup" means any 2.xx.xxx.x 1.xx.xxx.x including the EU WWE... this just to get your device working again. But you're stuck at 4.4.2 for awhile. This is what at least you need for now as mentioned on post #1
Restoring a nandroid backup won't brick a device.
You can't install 4.xx.xxxx.x because hboot is too low version.
Damn ... just notice I gave you wrong info. hboot 3.16.0000 you can restore only 1.xx.xxx.x backup
ckpv5 said:
I wrote "just restore any of the 2.xx.xxx.x 1.xx.xxx.x backup" means any 2.xx.xxx.x 1.xx.xxx.x including the EU WWE... this just to get your device working again. But you're stuck at 4.4.2 for awhile. This is what at least you need for now as mentioned on post #1
Restoring a nandroid backup won't brick a device.
You can't install 4.xx.xxxx.x because hboot is too low version.
Damn ... just notice I gave you wrong info. hboot 3.16.0000 you can restore only 1.xx.xxx.x backup
Click to expand...
Click to collapse
Maybe this doesn't mean anything, but my OS is Version 4.4.4. (At least, this is what they say on the official Page & in Settings)
ppcinj said:
Maybe this doesn't mean anything, but my OS is Version 4.4.4. (At least, this is what they say on the official Page & in Settings)
Click to expand...
Click to collapse
I don't know anything when it comes to AOSP ROM requirement.
What I talked about here is to get your device up and running on Sense ROM.
Anybody had this experience or knows what to do, for bring my phone back to working? It mustnt be Android 5, but just working, so I can make phone calls again.Your fastboot getvar all tells that your original Sense OS is 4.4.2
ckpv5 said:
I wrote "just restore any of the 2.xx.xxx.x 1.xx.xxx.x backup" means any 2.xx.xxx.x 1.xx.xxx.x including the EU WWE... this just to get your device working again. But you're stuck at 4.4.2 for awhile. This is what at least you need for now as mentioned on post #1
Restoring a nandroid backup won't brick a device.
You can't install 4.xx.xxxx.x because hboot is too low version.
Damn ... just notice I gave you wrong info. hboot 3.16.0000 you can restore only 1.xx.xxx.x backup
Click to expand...
Click to collapse
I've tried now to restore the zip file... I used this one: 1.54.401.5 - CWM Philz touch. After restoration process I rebooted the system and then the Slimkat logo appeared again, and it's still in bootloop.:crying:
Edit: This is one problem i noticed already some time ago: I couldn't flash any other rom than slimkat since i flashed it the first time...
Edit2: Also After I flashed philz once I couldn't go back to twrp... THen it stuck in "Entering recovery" screen.
Sorry, i was an idiot, i didn't realise, that i need to extract the zip first -.-. I will try it again now.
ckpv5 said:
I don't know anything when it comes to AOSP ROM requirement.
What I talked about here is to get your device up and running on Sense ROM.
Anybody had this experience or knows what to do, for bring my phone back to working? It mustnt be Android 5, but just working, so I can make phone calls again.Your fastboot getvar all tells that your original Sense OS is 4.4.2
Click to expand...
Click to collapse
Ok, im trying to restore now one of the downloaded Backups, however i can't manage to do so... It's always checking for img files, however it doesnt find them, and therefore doesn't restore them... Do I need to do anything special with the downloaded files?
ppcinj said:
Ok, im trying to restore now one of the downloaded Backups, however i can't manage to do so... It's always checking for img files, however it doesnt find them, and therefore doesn't restore them... Do I need to do anything special with the downloaded files?
Click to expand...
Click to collapse
I expect you know how to use a nandroid backup zip.
I want to help you but I'm not familiar with Philz recovery, only TWRP
The basic thing is, the nandroid backup zip to be extracted on PC. Then transfer the extracted the last folder that you see with its contents to recovery backup folder.
Also make sure the backup is meant for the right recovery.
What I read : philz --> Clockworkmod\Backups\
What I know : TWRP --> TWRP\BACKUPS\serialno\BackupFolderHere
For TWRP, simply make a nandroid backup of your boot, so you'll see the correct path then paste the nandroid folder that you extracted to this folder
ckpv5 said:
I expect you know how to use a nandroid backup zip.
I want to help you but I'm not familiar with Philz recovery, only TWRP
The basic thing is, the nandroid backup zip to be extracted on PC. Then transfer the extracted the last folder that you see with its contents to recovery backup folder.
Also make sure the backup is meant for the right recovery.
What I read : philz --> Clockworkmod\Backups\
What I know : TWRP --> TWRP\BACKUPS\serialno\BackupFolderHere
For TWRP, simply make a nandroid backup of your boot, so you'll see the correct path then paste the nandroid folder that you extracted to this folder
Click to expand...
Click to collapse
Ok, this worked for now and my Mobile is back in running state. Because of a strange feeling in my stomach i think that it's not possible now to simply download an OTA and get the new Android 5? What options do I have to get android 5?
ppcinj said:
Ok, this worked for now and my Mobile is back in running state. Because of a strange feeling in my stomach i think that it's not possible now to simply download an OTA and get the new Android 5? What options do I have to get android 5?
Click to expand...
Click to collapse
Not possible unless:
1. Use SunShine (paid service) to S-Off then you can flash other region ROM
or
2. Search/google around for a backup for your region device 1.xx.166.x (I have no idea the exact no.)
or
3. A risky one - flash your region 5.0 firmware 4.19.166.2 then install any 5.0 ROM .. I cannot guarantee this will work on hboot 3.16 as its a big jump from 3.16 to 3.19 .. you may brick your device.
ckpv5 said:
Not possible unless:
1. Use SunShine (paid service) to S-Off then you can flash other region ROM
or
2. Search/google around for a backup for your region device 1.xx.166.x (I have no idea the exact no.)
or
3. A risky one - flash your region 5.0 firmware 4.19.166.2 then install any 5.0 ROM .. I cannot guarantee this will work on hboot 3.16 as its a big jump from 3.16 to 3.19 .. you may brick your device.
Click to expand...
Click to collapse
You have written a second time 1.xx.166.x. Are you sure about this, and that it's not the .161 region?
ppcinj said:
You have written a second time 1.xx.166.x. Are you sure about this, and that it's not the .161 region?
Click to expand...
Click to collapse
Your fastboot getvar tells that :
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP110x.xx.166.x
modelid: 0P6B10000
cidnum: VODAP110
cidnum: VODAP120
mainver: 4.19.166.2
There is no CID VODAP110 in
x.xx.161.x
modelid: 0P6B10000
cidnum: VODAP001
cidnum: VODAP102
cidnum: VODAP405
cidnum: VODAPE17
cidnum: VODAPD18
cidnum: VODAP304
mainver: 2.22.161.6
Good luck ... got to rest now
Hello XDA-Community,
I have an HTC One M8 (M8_UL) with the following details:
Software Status: Modified
*** UNLOCKED ***
And I have Cyanogenmod installed (latest nightly build 12.1-20151118-NIGHTLY-m8 Android 5.1.1) and TWRP 2.8.7.0
Now my GPS is not working since a while now (I can't really tell if it has even started when I moved to CM or if it happened afterwards).But GPS Status never gives me a single satellite. I have read in another topic here in the board, that getting back to Sense Stock could help. Then back to CM and everything could be fine.
But here my questions start:
1) What exactly does this S-ON mean?
2) So how do I know which firmware/recovery/system (I figured out that there is some difference between all this and that now my TWRP 2.8.7.0 obviously is my Recovery Tool installed at the moment.
3) What is RUU and OTA ? As I understood its like a Operating System Update out of windows? I once downloaded a version but it always claims my battery would not be full so it would not let me update/upgrade/recover?
4) Why is my version-main info empty? (see below)
Sorry for all these questions and thanks in advance for your help
C:\Users\fsc>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.053s
Click to expand...
Click to collapse
My answers below in blue font.
damarges said:
1) What exactly does this S-ON mean?
S-on/s-off is a HTC specific security flag. S-off means "security off" and in the past meant that all security checks are bypassed. On the M8, its a little more complicated than that, some things are bypassed, some are not. But it allows you to do things like flashing modified hboots, radios, unsigned RUUs and downgrade firmware. S-off is kind of a "back door" that HTC leaves for itself. But when exploited by users, such as the devs here at XDA, is handy for some pretty useful things. S-on is the "stock" condition, and means you don't have the ability to do these things. In order to get s-off, you need to use the sunshine method, which costs $25. But s-off is not required to flash ROMs, root, or return to stock.
2) So how do I know which firmware/recovery/system (I figured out that there is some difference between all this and that now my TWRP 2.8.7.0 obviously is my Recovery Tool installed at the moment.
Firmware number is indicated by main version in getvar output, or by the "OS" number on the bootloader screen.
If you want to go back to stock recovery, you will want the stock recovery file that matches your firmware number. But for what you describe, I don't think you need or want to flash stock recovery.
System is the ROM version number, and again if you are returning to stock, you should find the nandroid that has the same number as your firmware.
Don't confuse any of the above with the software number in the phone's settings (common mistake). That number is related to the current ROM. So if you flash a custom ROM, that number just corresponds to the custom ROM, not the firmware or stock ROM number.
3) What is RUU and OTA ? As I understood its like a Operating System Update out of windows? I once downloaded a version but it always claims my battery would not be full so it would not let me update/upgrade/recover?
RUU and OTA are related, but two very different things:
RUU = ROM update utility. Its a Windows executable, normally an official HTC tool that will completely re-image your phone to stock, every single partition, and will also wipe your phone. The CID and MID of your phone need to match what the RUU is intended for. Does not require stock ROM or stock recovery to run, but has to be same or greater version number than main version (or hboot) on the phone - meaning you can't "downgrade" (unless you have s-off). Relocking the bootloader is required to RUU (again, unless you have s-off).
OTA = over the air. Its an incremental OS update, sent out by HTC. It normally requires the software number directly proceeding it, meaning you need to install them in sequence, and can't skip any. And may not be a complete image, but simply a "patch". It also requires stock recovery to be present, as well as the stock ROM. No need to relock bootloader to OTA (unlike RUU). Also, OTA will not typically wipe the phone (but you should backup before OTA to be safe, as it does sometimes wipe data).
4) Why is my version-main info empty?
Common issue. This is usually because an outdated 2.7 version of TWRP was installed at some point, wiping out the main version info (known TWRP bug).
On the bootloader screen, does it read a number after "OS" in green letter?
Click to expand...
Click to collapse
Thanks a lot for these detailed descriptions. Makes it more clear to me.
Firmware number is indicated by main version in getvar output, or by the "OS" number on the bootloader screen.
Click to expand...
Click to collapse
>> as it is empty on my getvar output I don't know which firmware/recovery to choose?
On the bootloader screen, does it read a number after "OS" in green letter?
Click to expand...
Click to collapse
>> no. its just empty "OS- " thats it.
But for what you describe, I don't think you need or want to flash stock recovery.
Click to expand...
Click to collapse
>> no actually I don't want stock recovery. I am happy with TWRP. I actually just want to have my GPS issues fixed. else I am really happy with Cyanogenmod.
>> do you have knowledge on how to fix the GPS issue? or if returning to Sense ROM could fix it maybe?
So if I don't know my firmware/OS - number? how do I choose a proper nandroid backup? and does a nandroid backup does return my phone to sense ROM?
damarges said:
I am really happy with Cyanogenmod.
>> do you have knowledge on how to fix the GPS issue? or if returning to Sense ROM could fix it maybe?
Click to expand...
Click to collapse
I'm not a CM user on this device, so I'm not too familiar with the issue.
damarges said:
So if I don't know my firmware/OS - number? how do I choose a proper nandroid backup? and does a nandroid backup does return my phone to sense ROM?
Click to expand...
Click to collapse
I believe your firmware is 4.16.401.x (possibly "8" where the "x" is), based on your CID, and hboot and radio numbers indicating you are on Lollipop firmware.
Are you sure its a nandroid that is being discussed in the "fix" and not RUU to stock? If you direct me to the thread/post that discusses the fix, maybe I can take a look and see if I can figure anything out.
But yes, a stock nandroid for 4.16.401 will return you to the Sense ROM.
redpoint73 said:
Are you sure its a nandroid that is being discussed in the "fix" and not RUU to stock? If you direct me to the thread/post that discusses the fix, maybe I can take a look and see if I can figure anything out.
Click to expand...
Click to collapse
The links I used to gather information:
https://www.reddit.com/r/cyanogenmod/comments/3gw7fm/htc_one_m8_cm121_the_gps_doesnt_work/
On http://forum.xda-developers.com/showthread.php?t=2701376 I can not find a nandroid stock backup that is working. The link to 4.16.401.10 - TWRP Thanks to sneakyghost is not working anymore on mega :/
How do I create a nandroid backup myself (after hopefully I get fixed everything)?
I could replace my Cyanogenmod with a stock nandroid backup of htc sense. but it did not fix the GPS problem. Still not a single satellite to receive :/
Even erase modemst1 and erase modemst2 did not fix anything :/
Anyone has a hint what to do?
Hi all. My Sprint M8 get error that no sim card error/ 4g sim/uicc dont work. Please insert Sprint sim/uicc. Please, help me
Similar Problem but expanded it!
Tural313 said:
Hi all. My Sprint M8 get error that no sim card error/ 4g sim/uicc dont work. Please insert Sprint sim/uicc. Please, help me
Click to expand...
Click to collapse
Hi friends, I live in India and have a HTC M8 Harman Kardon from Sprint running marshmallow (6.0) with Sense 7.0 and yesterday my phone switched off due to low battery which was normal thing for me as usual but after switching it on i had an error message "INVALID SIM CARD" saying "4G services are unavailable as the SIM/UICC is invalid. Please contact Customer Care. " .
My Bootloader speaks the following Info when I switch the phone Off and turn It on using "VOLUME DOWN" and "POWER" buttons simultaneously.
So a few details if someone could help me out regarding this above scenario :
***Software Status : Official ***
***RELOCKED***
M8_WHL PVT SHIP S-ON
HBOOT - 3.19.0.0000
RADIO - 1.09.20.1112
Open DSP - v62.2.2 - 00593- M8974_HM.1118
OS - 6.20.654.3
eMMC - boot 2048MB
Jan 27 2016, 21:06:08.90020620
THANK YOU in ADVANCE
Me too. My phone switched off to due battery and after switched on, i had a error message no sim card error, when i put on sim card, i get invalid sim card etc.
Try the RUU. For the Sprint version M8, RUUs are here: https://forum.xda-developers.com/showthread.php?t=2729173
Note that relocking the bootloader is required to RUU if you are s-on. And RUU will wipe the phone.
---------- Post added at 09:53 AM ---------- Previous post was at 09:49 AM ----------
Tural313 said:
Me too. My phone switched off to due battery and after switched on, i had a error message no sim card error, when i put on sim card, i get invalid sim card etc.
Click to expand...
Click to collapse
Sprint version also, or no?
My advice, when posting, provide all the details you can about your phone version (and if you know how, do fastboot getvar all, and post the results - delete IMEI and serial number before posting). Saying "me too" or "I have the same problem" without any giving any specific details about your phone, is never enough info for us to properly help you (usually just forces us to ask you questions about the details, before we can help).
redpoint73 said:
Try the RUU. For the Sprint version M8, RUUs are here: https://forum.xda-developers.com/showthread.php?t=2729173
Note that relocking the bootloader is required to RUU if you are s-on. And RUU will wipe the phone.
---------- Post added at 09:53 AM ---------- Previous post was at 09:49 AM ----------
Sprint version also, or no?
My advice, when posting, provide all the details you can about your phone version (and if you know how, do fastboot getvar all, and post the results - delete IMEI and serial number before posting). Saying "me too" or "I have the same problem" without any giving any specific details about your phone, is never enough info for us to properly help you (usually just forces us to ask you questions about the details, before we can help).
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I was install cm 14.1, after install i restore stock sense rom, on fastboot mode OS version is disappeared. I was install RUU before, but had get Sim card error every time.
Tural313 said:
I was install cm 14.1, after install i restore stock sense rom, on fastboot mode OS version is disappeared.
Click to expand...
Click to collapse
This is a known bug with old (obsolete) TWRP versions. OS number will reappear once the correct RUU is installed.
Tural313 said:
I was install RUU before, but had get Sim card error every time.
Click to expand...
Click to collapse
Which RUU exactly (name, version number)? There are many. And in fact, flashing the wrong (non-Sprint) RUU can cause the no-SIM problem.
redpoint73 said:
This is a known bug with old (obsolete) TWRP versions. OS number will reappear once the correct RUU is installed.
Which RUU exactly (name, version number)? There are many. And in fact, flashing the wrong (non-Sprint) RUU can cause the no-SIM problem.
Click to expand...
Click to collapse
Firmware: 6.20.651.3 Full firmware. RUU: 6.20.651.3 download from htc site
When phone is boot, don't show Sprint screen and isn't sprint sound, only HTC One logo and sound. I don't find trouble for this problem. :/
Tural313 said:
Firmware: 6.20.651.3 Full firmware. RUU: 6.20.651.3 download from htc site
Click to expand...
Click to collapse
So you flashed the firmware twice in RUU mode, then the RUU?
Did they both run to completion, with no error messages (exception, you will probably get a message first time flashing firmware to "flush again immediately" which means to flash the firmware a 2nd time - this is normal).
redpoint73 said:
So you flashed the firmware twice in RUU mode, then the RUU?
Did they both run to completion, with no error messages (exception, you will probably get a message first time flashing firmware to "flush again immediately" which means to flash the firmware a 2nd time - this is normal).
Click to expand...
Click to collapse
Yes, error message first time. Flash second time and finish. Then install RUU
redpoint73 said:
So you flashed the firmware twice in RUU mode, then the RUU?
Did they both run to completion, with no error messages (exception, you will probably get a message first time flashing firmware to "flush again immediately" which means to flash the firmware a 2nd time - this is normal).
Click to expand...
Click to collapse
Hey, what i must do now?
Tural313 said:
Hey, what i must do now?
Click to expand...
Click to collapse
So the SIM was working fine on CM, and then what did you install? You said "stock ROM" and OS number disappeared. Did you try to install anything else besides the 6.20.651.3 firmware and RUU?
redpoint73 said:
So the SIM was working fine on CM, and then what did you install? You said "stock ROM" and OS number disappeared. Did you try to install anything else besides the 6.20.651.3 firmware and RUU?
Click to expand...
Click to collapse
Sim wasn't work on CM. I'll install 6.20.651.3 firmware and RUU. But i don't know, change anything.
Tural313 said:
Sim wasn't work on CM.
Click to expand...
Click to collapse
Its very confusing, and difficult to troubleshoot, if you don't properly describe the device history. Describe step and step, and in detail the device history that led to this issue.
Did it work on CM, then you ran out of battery, and didn't work? Then you tried to flash firmware and RUU, and no change?
Did you try flashing anything else?
Did you s-off and SuperCID the phone, or was it done by previous owner or vendor?
redpoint73 said:
Its very confusing, and difficult to troubleshoot, if you don't properly describe the device history. Describe step and step, and in detail the device history that led to this issue.
Did it work on CM, then you ran out of battery, and didn't work? Then you tried to flash firmware and RUU, and no change?
Did you try flashing anything else?
Did you s-off and SuperCID the phone, or was it done by previous owner or vendor?
Click to expand...
Click to collapse
No, it was work on Leedroid M8 Rom, battery due and didn't work. Then i tried flash firmware and RUU and no change. Phone is S-Off and SuperCID.
Tural313 said:
No, it was work on Leedroid M8 Rom, battery due and didn't work. Then i tried flash firmware and RUU and no change.
Click to expand...
Click to collapse
So when was it on CM???
I asked a step by step history, you didn't provide it.
Suddenly you mention LeeDroid, which I don't think you mentioned previously. Makes me wonder what other steps you are not telling us.
It really confusing to decipher what you've done.
Tural313 said:
Phone is S-Off and SuperCID.
Click to expand...
Click to collapse
That obviously is not what I am asking. I clearly already know you have s-off and SuperCID. I asked how it got that way.
If you don't take the time to read my posts properly, or provide the information requested; why should I bother to try to help? You're making it harder for folks to help you.
redpoint73 said:
So when was it on CM???
I asked a step by step history, you didn't provide it.
Suddenly you mention LeeDroid, which I don't think you mentioned previously. Makes me wonder what other steps you are not telling us.
It really confusing to decipher what you've done.
That obviously is not what I am asking. I clearly already know you have s-off and SuperCID. I asked how it got that way.
If you don't take the time to read my posts properly, or provide the information requested; why should I bother to try to help? You're making it harder for folks to help you.
Click to expand...
Click to collapse
When i bought phone, it was S-OFF and SuperCID. I was install stock rom with RUU, then stock rooted rom with TWRP, then install Leedroid with backup TWRP ( i was installed Leedroid before stock ruu and backup it). I was work on Leedroid for 1 month and when battery due, sim card error. After i installed ruu, cm nothing change.
Tural313 said:
When i bought phone, it was S-OFF and SuperCID. I was install stock rom with RUU, then stock rooted rom with TWRP, then install Leedroid with backup TWRP ( i was installed Leedroid before stock ruu and backup it). I was work on Leedroid for 1 month and when battery due, sim card error. After i installed ruu, cm nothing change.
Click to expand...
Click to collapse
I also installed Flyme Os for sprint m8. But don't work on it, then flash RUU. I was used this rom after stock Rooted rom. I forget write it.
Have you verified the SIM works on another device?
Also, my questions in red font below:
Tural313 said:
When i bought phone, it was S-OFF and SuperCID. I was install stock rom with RUU (what RUU version exactly?), then stock rooted rom with TWRP, then install Leedroid with backup TWRP ( i was installed Leedroid before stock ruu and backup it). I was work on Leedroid for 1 month and when battery due, sim card error. After i installed ruu (did you try the SIM before installing CM?), cm nothing change.
Click to expand...
Click to collapse
redpoint73 said:
Have you verified the SIM works on another device?
Also, my questions in red font below:
Click to expand...
Click to collapse
Yes, sim work's on other device.
Hi guys, i realy need some help; can't install any working rom in my device ; i've tray a lot of solution but cant fixe problem ( no basebande no imei )
im CID 11111111 / Unlocked
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.19.0.0000
RADIO-1.29.214500021.12G
OpenDSP-v51.2.2-00593-M8974_FO.1015
OS-
eMMC-boot 2048MB
Jan 26 216,15:50:09.0
PLEASE HELP
Your post is really unclear, making it impossible to help without further info.
Did you have the issue of no SIM before, causing you to try to fix it? Or were you playing around with ROMs, and broke the baseband/SIM? In other words, what was the exact sequence of events that led to the current condition.
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Also, is the bootloader locked, unlocked or relocked?
Do you have TWRP installed? If so, what version number?
Also:
morphus3x said:
can't install any working rom in my device
Click to expand...
Click to collapse
What exactly did you try to install (file names, ROM names, version numbers - provide as much detail as possible)?
morphus3x said:
i've tray a lot of solution
Click to expand...
Click to collapse
This isn't useful statement, unless you describe exactly what you tried (again, with exact file names, version numbers, etc.) and what the specific result of each was (description of results, error messages, etc.).
i have TWRP 3.1.1-0 just installed today, unlocked s-off
getvar info :
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: *******************
(bootloader) imei: ******************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
i broke it for real
i try to install many roms , this some ones :
0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15.720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_release_469495_signed_2_4_gsmdevelopers.com
M8_UL_M60_SENSE70_MR_hTC_Asia_TW_6.20.709.2
HTC_One_M8_GPE_5.07.1700.11_MRA58K.H11_022
SkyDragonM8v4.0.0Sense8MM
I DELETE THIS OTHERS
there's no errors, just the device dont start, stock at one image and no menu, only start botton work
Your post #1 said you installed ROM but no baseband & no imei
Your post #3 said stuck on bootanimation (I guess)
So which ROM for no. 1 ?
0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15. 720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_re lease_469495_signed_2_4_gsmdevelopers.com should be correct RUU for your device.
If you can boot ROM as no.1 and no baseband & imei, try install 6.15.720.2 firmware only to see whether it can fix your problem
https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
ckpv5 said:
Your post #1 said you installed ROM but no baseband & no imei
Your post #3 said stuck on bootanimation (I guess)
So which ROM for no. 1 ?
0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15. 720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_re lease_469495_signed_2_4_gsmdevelopers.com should be correct RUU for your device.
Click to expand...
Click to collapse
**********************************************************
only GPE rom can be installed to the end , the others stuck
this one ( 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15. 720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_re lease_469495_signed_2_4) dont wont install , stuck in TWRP, it's said the file is corrumpted
morphus3x said:
**********************************************************
only GPE rom can be installed to the end , the others stuck
this one ( 0P6BIMG_M8_UHL_M60_SENSE70_MR_hTC_Asia_India_6.15. 720.2_Radio_1.29.214500021.12G_20.72.4196t.01_F_re lease_469495_signed_2_4) dont wont install , stuck in TWRP, it's said the file is corrumpted
Click to expand...
Click to collapse
That is a RUU not flashable rom zip, you can't install RUU in twrp.
You installed GPE ROM in twrp ? So I guess you didn't install GPE RUU.
Try any other Sense ROM like ICE, if can boot but no baseband & imei, install firmware as I said above.
Another thing.. your bootloader is white and not black, right ?
ckpv5 said:
That is a RUU not flashable rom zip, you can't install RUU in twrp.
You installed GPE ROM in twrp ? So I guess you didn't install GPE RUU.
Try any other Sense ROM like ICE, if can boot but no baseband & imei, install firmware as I said above.
Another thing.. your bootloader is white and not black, right ?
Click to expand...
Click to collapse
*************************************************************************
yes bootloader is white , i tried the RUU method but it's stuck to, i had some errors. and i must phone must be relocked , i lost S-off when i did it.
i tried to get a backup like u say in ur post but not working
please can u help, what's the rom i may install can u give me all tutoriel
I never say any backup to try, only the firmware.
No need to relock bootloader to install RUU and no need to change to S-On (same for installing firmware too)
Install again GPE rom as you said you can install and working but no baseband
Then after install firmware, fw_6.15.720.2.zip only
then tell if baseband is fixed or not.
morphus3x said:
i tried the RUU method but it's stuck to, i had some errors. and i must phone must be relocked , i lost S-off when i did it.
Click to expand...
Click to collapse
What format is the RUU, is it zip or exe?
If it got stuck, what was the specific error message? Only telling us it "had some errors" is not useful. I shouldn't have to be telling you this again. Provide as much detail as possible, if you expect us to help.
You don't need to relock the bootloader to RUU when you have s-off.
Relocking the bootloader does not make the device s-on. Never seen it. It just makes the bootloader RELOCKED, which restricts a lot of other things (can't flash TWRP, etc.).
ckpv5 said:
I never say any backup to try, only the firmware.
No need to relock bootloader to install RUU and no need to change to S-On (same for installing firmware too)
Install again GPE rom as you said you can install and working but no baseband
Then after install firmware, fw_6.15.720.2.zip only
then tell if baseband is fixed or not.
Click to expand...
Click to collapse
*******************************************
it's not working , no imei no basebande to
i install GPE and flashing fw_6.15.720.2_recovery.img but not working no imei no basebande ,
last error when i tray RUU.exe was 179
thanks for ur help
morphus3x said:
i install GPE and flashing fw_6.15.720.2_recovery.img but not working no imei no basebande ,
Click to expand...
Click to collapse
Firmware and recovery nor two different things. I'm skeptical if you flashed the right thing, or did it properly.
Did you get the file, and follow the instructions exactly as listed in the link that ckpv5 gave your for the firmware?
Did you flash it twice, as the instructions say?
Do fastboot getvar all, again, and post (delete IMEI and serial number before posting).
morphus3x said:
i install GPE and flashing fw_6.15.720.2_recovery.img but not working no imei no basebande ,
last error when i tray RUU.exe was 179
thanks for ur help
Click to expand...
Click to collapse
It's not easy to help you when you don't understand the suggestion.
I never say 6.15.720.2_recovery.img, no such file in the link that I gave you. Please read again the filename is fw.15.720.2.zip and you need to install it using fastboot method or ext_sd method.
https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
I have to say good night now .. it's 3.15 am here.
morphus3x said:
last error when i tray RUU.exe was 179
Click to expand...
Click to collapse
Are you sure? I can't find error code 179.
Maybe you mean Error 170, which is USB connection error. Which often just means you need to put the phone in fastboot mode. Or try another USB cable, another USB port on the PC, or re-install the HTC drivers.
ckpv5 said:
It's not easy to help you when you don't understand the suggestion.
I never say 6.15.720.2_recovery.img, no such file in the link that I gave you. Please read again the filename is fw.15.720.2.zip and you need to install it using fastboot method or ext_sd method.
https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
I have to say good night now .. it's 3.15 am here.
Click to expand...
Click to collapse
OOOOOOOOOH IT'S WORKING ? THANKS GUYS? I'M VERY THINKFUL
i miss my my phone
one more think plzzzzzzzzzz; what rom can i install; i don't like GPE
morphus3x said:
one more think plzzzzzzzzzz; what rom can i install; i don't like GPE
Click to expand...
Click to collapse
Any of the ROMs from the M8 development section should work. You will need to unlock the bootloader again, and flash TWRP to the device again (suggest current TWRP version 3.1.1-0). This is due to the fact that firmware over-wrote TWRP with stock recovery.
Most of the "ROMs" you were trying to flash before were RUUs, not TWRP-flashable ROMs. So hopefully, you won't have any issue flashing ROMs now.
redpoint73 said:
Any of the ROMs from the M8 development section should work. You will need to unlock the bootloader again, and flash TWRP to the device again (suggest current TWRP version 3.1.1-0). This is due to the fact that firmware over-wrote TWRP with stock recovery.
Most of the "ROMs" you were trying to flash before were RUUs, not TWRP-flashable ROMs. So hopefully, you won't have any issue flashing ROMs now.
Click to expand...
Click to collapse
********************************************
im confused, can u give me direct link for best roms please ; i dont wont to brake it again !!
wanna use dual cam and htc sense
thanks to all XDA's staff ; you're the BEST
morphus3x said:
********************************************
im confused, can u give me direct link for best roms please ; i dont wont to brake it again !!
wanna use dual cam and htc sense
Click to expand...
Click to collapse
I don't personally do "best ROM" recommendations for 2 main reasons:
1) There is no such thing as a "best ROM" for everyone. Each user has drastically different preferences and usage patterns. What is "best" for me, may not even be any good for you. You need to decide for yourself what is "best". If you want some ROM suggestions, there are plenty (IMO, too many) of existing threads with such discussions.
2) The notion of a "best ROM(s)" is insulting to the developers, most of whom do all this work for no compensation. If everyone kept recommending the "best" ROM(s), what point would there ever be for devs to introduce new ROMs or ideas? The variety/choice in ROMs is a good thing. Don't rob yourself of the potential "hidden gems" by being a sheep and doing what everyone else does, or just doing what a stranger tells you is "best".
You won't do anything to the phone by flashing ROMs, that isn't recoverable. We all occasionally run into bad ROM flashes, no boot situations, and other bugs. It's just part of the game. If you flash ROMs, root, or otherwise mod these phones; you have to live with the fact that sometimes things go wrong, and you have to know how to recover from those things.
If you stick with the M8 development section, and look for Sense ROMs, you will find what you seek. Don't flash any RUUs or firmware, unless you know what you are doing.
https://forum.xda-developers.com/htc-one-m8/development
thanks again, i'll tray this ont SkyDragon M8 v 9.0 Sense 7
skydragon creations are smooth and i like to use it ; not booting fast but propose all i want
Hi all.
Got a HTC one m8 in and it appears to be stuck on the HTC screen, I can get into bootloader fine, have tried to reflash via SD card but i get a CID error.
Can anyone direct me to what ROM i need to be installing? Its a UK version.
Thanks in advance.
Jabbah said:
Hi all.
Got a HTC one m8 in and it appears to be stuck on the HTC screen, I can get into bootloader fine, have tried to reflash via SD card but i get a CID error.
Can anyone direct me to what ROM i need to be installing? Its a UK version.
Thanks in advance.
Click to expand...
Click to collapse
What does it say next to "OS" in your bootloader menu?
Jabbah said:
have tried to reflash via SD card but i get a CID error.
Can anyone direct me to what ROM i need to be installing? Its a UK version.
Click to expand...
Click to collapse
Tried to flash what? Can't troubleshoot what you did wrong, unless you tell is what you tried to flash. RUU, firmware.zip, or something else? What is the version number and file name?
That is in addition to the info requested in the previous reply.
Also, if you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the device.
redpoint73 said:
Tried to flash what? Can't troubleshoot what you did wrong, unless you tell is what you tried to flash. RUU, firmware.zip, or something else? What is the version number and file name?
That is in addition to the info requested in the previous reply.
Also, if you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the device.
Click to expand...
Click to collapse
Tried to flash a stock UK rom.
I have no idea how to use that command sorry.
os is 6.12.61.4
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.61.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Jabbah said:
Tried to flash a stock UK rom.
Click to expand...
Click to collapse
Still too vague for us to have any idea what you tried to flash.
I asked some specific questions for a reason; some of which you seem to have missed or ignored. I'm not just typing to exercise my fingers!
redpoint73 said:
RUU, firmware.zip, or something else?
What is the version number and file name?
Click to expand...
Click to collapse
"Stock UK ROM" can mean a number of things. If you are talking about RUU, then calling it a "stock ROM" is not the right term (and confusing) since RUU is a complete image containing something like 41 partitions, with the ROM being only one of those partitions.
In fact, if you are referring to RUU, I don't think your version M8 (or most UK versions, for that matter) has a valid RUU. So you are likely in fact not even trying to flash a stock UK ROM. Which also explains the CID error.
On a positive note, good work figuring out how to do fastboot getvar all. If you can provide more info on what you tried to flash, we can make some progress!
redpoint73 said:
Still too vague for us to have any idea what you tried to flash.
I asked some specific questions for a reason; some of which you seem to have missed or ignored. I'm not just typing to exercise my fingers!
"Stock UK ROM" can mean a number of things. If you are talking about RUU, then calling it a "stock ROM" is not the right term (and confusing) since RUU is a complete image containing something like 41 partitions, with the ROM being only one of those partitions.
In fact, if you are referring to RUU, I don't think your version M8 (or most UK versions, for that matter) has a valid RUU. So you are likely in fact not even trying to flash a stock UK ROM. Which also explains the CID error.
On a positive note, good work figuring out how to do fastboot getvar all. If you can provide more info on what you tried to flash, we can make some progress!
Click to expand...
Click to collapse
Thanks for the replies, ive actually gotten somewhere today, Ive installed twrp, and installed the latest Lineage ROM which booted fine .
But.... Not detecting sim card
Always something haha
Another option (especially now that you have unlocked the bootloader, and installed TWRP), is restore stock TWRP backup 6.12.61.4 from here:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
No need to do Step 3, nor Steps 10 or after (only relevant to get OTA updates - which no longer applies to this device). Just reboot.
Jabbah said:
Thanks for the replies
Click to expand...
Click to collapse
There is a button for that.
Quick update, Restored stock TWRP as you suggested, performed simunlock and am now a happy chappy with a working M8
Now, Whats the best ROM to use for it ? Is it worth installing Lineage ROM?
David.
Jabbah said:
Quick update, Restored stock TWRP as you suggested, performed simunlock and am now a happy chappy with a working M8
Now, Whats the best ROM to use for it ? Is it worth installing Lineage ROM?
Click to expand...
Click to collapse
Glad the TWRP restore worked out for you.
No such thing as a "best ROM". Each individual user has different preferences and tastes. That's the reason there are different ROM choices. If there was a "best ROM", nobody would ever need anything else, right?
I am not personally a Lineage user (so good example right there how one person's opinion may not apply to you). But if you flash it again, I assume you can (or will) have the same problem with SIM not detected. I think I've seen other folks with the problem on Lineage (again, I don't really keep up with that ROM), so you should check the thread to see if there is a fix for that issue.
redpoint73 said:
Glad the TWRP restore worked out for you.
No such thing as a "best ROM". Each individual user has different preferences and tastes. That's the reason there are different ROM choices. If there was a "best ROM", nobody would ever need anything else, right?
I am not personally a Lineage user (so good example right there how one person's opinion may not apply to you). But if you flash it again, I assume you can (or will) have the same problem with SIM not detected. I think I've seen other folks with the problem on Lineage (again, I don't really keep up with that ROM), so you should check the thread to see if there is a fix for that issue.
Click to expand...
Click to collapse
Got around the sim not detected issue, the phone was simlocked to orange, it just didnt pop up with the enter unlock code dialogue.
Ill try a few see what they are like
Thanks again for your help.
Jabbah said:
Got around the sim not detected issue, the phone was simlocked to orange.
Click to expand...
Click to collapse
Understood. I would not have expected the "SIM not detected" error in that case. So thanks for clarifying.
Jabbah said:
it just didnt pop up with the enter unlock code dialogue.
Click to expand...
Click to collapse
Stock (Sense) ROM is needed to unlock SIM. Which you either figured out, or stumbled upon the solution by luck! :good: