[Q] Questions about android-info.txt - EVO 4G Q&A, Help & Troubleshooting

I am interested in understanding what each of the parameters in this file are used for. The snippet below is from the android-info.txt in a PC36IMG.zip that's supposed to 'prep' a 2.02.0000 hboot (3.30.651.2 build) EVO preparatory to downgrade to .76.2000.
Code:
modelid: PC3610000
cidnum: SPCS_001
mainver: 1.32.651.6
hbootpreupdate:11
DelCache: 0
DelUserData:0
This snippet below is the android-info.txt file in the pc36img.zip that is actually flashed after the one above and it downgrades the phone to .76.2000. (this zip also contains the hboot_0.76.2000.img file)
Code:
modelid: PC3610000
cidnum: SPCS_001
mainver: 1.32.651.6
hbootpreupdate:11
DelCache: 0
DelUserData:0
So, the questions are:
a) what part does the mainver parameter play?
b) In the above scenario, is it a switch indicating the target system build version?
c) DelCache/DelUserData are pretty much straight forward; what about hbootpreupdate? I 've seen some files with a setting of 2, 3. What other options are available.
This last one is from another pc36img zip used in a rooting process (it contains the engineering hboot build + custom recovery):
Code:
modelid: PC3610000
cidnum: SPCS_001
mainver: 1.47.651.1
hbootpreupdate:2
DelCache: 1
TIA

Can anyone assist with some pointers here?
Sent from my PC36100 using XDA App

The main version is the same as the firmware version. The hbootpreupdate I am not sure about though, all I know is a large portion of the people who bricked their phones trying to root 2.02 did it by flashing a pc36img.zip with the wrong hbootpreupdate setting. I spent a long time trying to help someone use fastboot and the hboot to correct it and we couldn't get it to take anything.
A lot of googling has turned up nothing and those familiar with the eng-hboot have been unresponsive to my msgs. So I am curious about this as well.
I noticed HTC changed the hbootpreupdate setting on the new RUU when compared to the old one and found out what the CID is for but that's about it.
Ver 3.29.651.5 android-info.txt
Code:
modelid: PC3610000
cidnum: SPCS_001
mainver: 3.29.651.5
hbootpreupdate:2
DelCache: 1
Ver 3.30.651.2 android-info.txt
Code:
modelid: PC3610000
cidnum: SPCS_001
mainver: 3.30.651.2
hbootpreupdate:12
DelCache: 1
more about the cid can be found in this thread:
[Partial GUIDE] flashing Images to EVO Partitions

xHausx said:
The main version is the same as the firmware version. The hbootpreupdate I am not sure about though, all I know is a large portion of the people who bricked their phones trying to root 2.02 did it by flashing a pc36img.zip with the wrong hbootpreupdate setting. I spent a long time trying to help someone use fastboot and the hboot to correct it and we couldn't get it to take anything.
.........
Click to expand...
Click to collapse
Thanks for the feedback; I agree -- a google search yields next to nothing significant/specific on this. It also appears the hbootpreupdate setting is key because, I did try to tweak a pc36img so it flashes just the hboot eng build -without all of the other files (boot/radio/recovery/etc) inorder to downgrade from hboot .97.0000 but it wouldn't take - this is already documented here . It only flashes when the zip has other stuff (radio, wimax, recovery, etc). My hunch is hbootpreupdate setting has a part to play but I am also not in a hurry to brick my EVO yet so...... It'd be interesting to get more info on this.

dan0412 said:
Thanks for the feedback; I agree -- a google search yields next to nothing significant/specific on this. It also appears the hbootpreupdate setting is key because, I did try to tweak a pc36img so it flashes just the hboot eng build -without all of the other files (boot/radio/recovery/etc) inorder to downgrade from hboot .97.0000 but it wouldn't take - this is already documented here . It only flashes when the zip has other stuff (radio, wimax, recovery, etc). My hunch is hbootpreupdate setting has a part to play but I am also not in a hurry to brick my EVO yet so...... It'd be interesting to get more info on this.
Click to expand...
Click to collapse
An easier, and probably safer, way to do that would be to use the recovery. I've used the recovery flashable zip posted in the first few posts there and it worked as expected. Just flash a kernel afterward to link to it.

xHausx said:
An easier, and probably safer, way to do that would be to use the recovery. I've used the recovery flashable zip posted in the first few posts there and it worked as expected. Just flash a kernel afterward to link to it.
Click to expand...
Click to collapse
Yes... I have used that method as well, flashing the zip and then the kernel (or ROM). I thought a 'neater' approach was to just push (adb) the pc36img to sdcard, issue a reboot to bootloader cmd .... done.
Sent from my PC36100 using XDA App

Related

[Q] Bootloop after failed attempt to Flash new Firmware

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: VODAP110​x.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

[Q] AT&T One M8. Can't successfully flash/boot recovery image or boot to system.

So! My phone is Tampered, Unlocked, and S-ON. I don't have a usable recovery image. I've tried the most recent Snapshot Cyanogen Recovery and the most recent TWRP for the M8, neither work by trying fastboot flash recovery <thing> or fastboot boot <thing>. The TWRP one vibrated when I touched the screen in where I presume the buttons are, but neither actually showed anything on screen.
What I can do: get to the bootloader. It's unlocked, as I said. I can also stare at the Google logo, taunting me, if I try to boot to recovery or to system.
What I would like to do: get a custom recovery that works, flash a ROM that works, and get on with my life without spending $XXX on another phone.
What I have already tried: an RUU. Didn't work. Not one bit. Error'd immediately, saying it can't do anything.
Here's the bootloader header:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1.14.21331931.LA02_2G
OpenDSP-v32.2.2-00542-M8974.0213
OS-2.12.1700.1
eMMC-boot 2048MB
Jun 16, 2014,18:47:55.0
And the infodump:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.1700.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: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
BaconSupreme said:
HBOOT-3.18.0.0000
Click to expand...
Click to collapse
Your hboot is pretty old. Try an older version TWRP (old hboot does not work with current TWRP, and vice versa new hboot does not work with older TWRP).
Try TWRP 2.7.something.
Better yet, relock the bootloader and RUU to Lollipop to update the firmware (hboot, radio, etc.). Then unlock the bootloader again, and flash current TWRP 2.8.7. If your goal is to flash custom ROMs, this is what you want anyway. Lollipop custom ROMs won't function properly on your old KitKat firmware.
---------- Post added at 12:51 PM ---------- Previous post was at 12:45 PM ----------
BaconSupreme said:
What I have already tried: an RUU. Didn't work. Not one bit. Error'd immediately, saying it can't do anything.
Click to expand...
Click to collapse
Those sentences lack so much detail, as to be virtually useless in us helping you.
"An RUU" ??? What RUU did you try (exact file name)? It needs to be an RUU for AT&T M8.
What was the error message? It states the reason the RUU failed.
The latest AT&T RUU can be found at the bottom of the following webpage: http://www.htc.com/us/support/htc-one-m8-att/news/
---------- Post added at 12:53 PM ---------- Previous post was at 12:51 PM ----------
BaconSupreme said:
What I would like to do: get a custom recovery that works, flash a ROM that works, and get on with my life without spending $XXX on another phone.
Click to expand...
Click to collapse
You don't even remotely need to worry about buying a new phone yet. You're just going about a couple things wrong, easily correctable.
So!
TWRP 2.7.1.0 was successfully flashed and started. Thanks for the suggestion. Successfully flashed and booted CM 11.
In regards to the RUU, the exact one that you linked is the one I tried to use. The error code I got was 155: Unknown Error. I've never had much success with RUUs in general.
Do you know if there's a Lollipop firmware.zip floating around for my MID/CID? I tried to find one for a bit but was unsuccessful. If I understand things right, I could relock my bootloader, flash a firmware.zip matching my MID/CID, re-unlock my bootloader, and flash updated versions of TWRP/CM.
BaconSupreme said:
In regards to the RUU, the exact one that you linked is the one I tried to use. The error code I got was 155: Unknown Error. I've never had much success with RUUs in general.
Click to expand...
Click to collapse
You need to relock the bootloader to RUU. That is the common reason for Error 155.
The main reason you've "never had much success with RUUs" may be due to lack of knowledge. An RUU will run as long as:
1) Correct RUU for your CID and MID
2) Equal or later RUU version than main version on the phone (this restriction does not apply with s-off)
3) RELOCKED or LOCKED bootloader (this restriction does not apply with s-off)
4) Some glitches may arise due to USB connectivity (re-installing HTC drivers or trying a different PC will usually solve this). But if you have an error message, USB connectivity is good.
BaconSupreme said:
Do you know if there's a Lollipop firmware.zip floating around for my MID/CID? I tried to find one for a bit but was unsuccessful. If I understand things right, I could relock my bootloader, flash a firmware.zip matching my MID/CID, re-unlock my bootloader, and flash updated versions of TWRP/CM.
Click to expand...
Click to collapse
I've never seen a signed Lollipop firmware zip for AT&T. And to flash an unsigned firmware, you need s-off.
Reason signed firmware is not common, is that its easy to just run the RUU.
redpoint73 said:
You need to relock the bootloader to RUU. That is the common reason for Error 155.
The main reason you've "never had much success with RUUs" may be due to lack of knowledge. An RUU will run as long as:
1) Correct RUU for your CID and MID
2) Equal or later RUU version than main version on the phone (this restriction does not apply with s-off)
3) RELOCKED or LOCKED bootloader (this restriction does not apply with s-off)
4) Some glitches may arise due to USB connectivity (re-installing HTC drivers or trying a different PC will usually solve this). But if you have an error message, USB connectivity is good.
I've never seen a signed Lollipop firmware zip for AT&T. And to flash an unsigned firmware, you need s-off.
Reason signed firmware is not common, is that its easy to just run the RUU.
Click to expand...
Click to collapse
The bootloader was relocked when I tried. I'll try reinstalling drivers and trying again later tonight.
Another potential reason might be what was on the phone at the time I just tried again (TWRP recovery / nonfunctional CM 12). Should I flash a stock recovery/ROM before trying the RUU, or does that not matter?
BaconSupreme said:
The bootloader was relocked when I tried. I'll try reinstalling drivers and trying again later tonight.
Click to expand...
Click to collapse
I already mentioned: drivers aren't the problem if you are getting error 155.
BaconSupreme said:
Another potential reason might be what was on the phone at the time I just tried again (TWRP recovery / nonfunctional CM 12). Should I flash a stock recovery/ROM before trying the RUU, or does that not matter?
Click to expand...
Click to collapse
Was that on my list of requirements for running an RUU? No, it was not. So NO, it does not matter. RUU re-images the phone to stock. It doesn't care what ROM or recovery is on the phone.
OTA is a different story. You need stock ROM and stock recovery. But OTA and RUU are 2 completely different things.
Are you sure the RUU file is the exact same one (same file name) that my link contains? I'm a bit skeptical when I link something, and response is "yeah yeah that's the one".
Try to relock the bootloader and the file I linked. Maybe you just forgot something, or mixed something up when you did it last time.
As long as the bootloader is relocked, and you use that file, it should work fine. But you can also use this one (also Lollipop, just without the Stagefright patch): http://dl3.htc.com/application/RUU_M8[email protected]50319A_40.45.C33065.00_F_release_426617_signed_2.exe
---------- Post added at 03:37 PM ---------- Previous post was at 03:27 PM ----------
WHOA. Hold the phone (no pun intended).
I just realized your main version number (firmware) is for GPE. It seems at some point the phone was converted to GPE. Did you do that?
That is probably why the RUU is failing.
You may need to s-off the phone again to get out of the hole. I think the phone must have been s-off at some point, in order to run a GPE firmware or RUU, then made s-on again.
Did you buy this phone used?

HELP PLEASE HTC ONE M8 stuck on bootloader when flashing stock rom

Hi all,
I have installed the rom GPE with this cid and mid, S-off but i lost my carrier, sim is no unlocked. Then i try to back to stock rom. The big mistake i have do is to do no backup of my original CID and MID. So during 3 mouths i had try all solutions that i see on the web ex :
Fashing splash firmware : 1.54.401.5 with stock rom but the phone always stuck on bootloader
Then i try 1.54.401.10 , 4.16.401.5 , 4.16.401.10 and last 2.22.401.4 with there rom stock and sotck recovery but nothing change, always stuck on bootloader.
NB : i'm in super CID
I have try :
1) wirecid : supercid or HTC__001 or HTC__J15 etc...
2) Flashing firmware 1.54.401.5, 1.54.401.10, 4.16.401.5, 4.16.401.10, 2.22.401.4
3) flashing custom recovery twrp
4) format data and changing partition cache because it's always corruped after flashing new firmware
5) install rom stock with there firmware :
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417809_signed.zip
m8_4.16.401.10_AROMA.zip
One_M8_4.16.401.10_stock_system_dump.zip
insertcoin-7.1.9-REPACK-M8_UL_L50_SENSE70_MR_HTC_Europe_4.16.401.10.zip
rom_one_m8_2.22.401.4_odexed.zip revolution HD
Android_Revolution_HD-One_M8_45.0_758ff1.zip
m8_1.54.401.5_AROMA
6) reboot phone, but stuck on bootloader
7) try to flash boot.img and stock recovery on the firmware but nothing change,
8) try to enter to stock recovery but redirected in bootloader
9) try to lock bootloader
I have do this with all firmware and rom
I have try to install with ruu.exe but the application have error 155, i have change the cid and mid to match with in the androidinfo.txt.
!!! But boot with custom like CM12, Carbon rom etc... the only problem is that the simcard is not detected.
If anyone have other solution ?
My last getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.401.4
(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: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please help, i will become the master of reflashing rom and firmware on HTC ONE M8 but corrupted.
Someone can help me ?
Someone can help me ?
kimpak said:
Hi all,
I have installed the rom GPE with this cid and mid, S-off but i lost my carrier, sim is no unlocked. Then i try to back to stock rom. The big mistake i have do is to do no backup of my original CID and MID. So during 3 mouths i had try all solutions that i see on the web ex :
Fashing splash firmware : 1.54.401.5 with stock rom but the phone always stuck on bootloader
Then i try 1.54.401.10 , 4.16.401.5 , 4.16.401.10 and last 2.22.401.4 with there rom stock and sotck recovery but nothing change, always stuck on bootloader.
NB : i'm in super CID
I have try :
1) wirecid : supercid or HTC__001 or HTC__J15 etc...
2) Flashing firmware 1.54.401.5, 1.54.401.10, 4.16.401.5, 4.16.401.10, 2.22.401.4
3) flashing custom recovery twrp
4) format data and changing partition cache because it's always corruped after flashing new firmware
5) install rom stock with there firmware :
0P6BIMG_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417809_signed.zip
m8_4.16.401.10_AROMA.zip
One_M8_4.16.401.10_stock_system_dump.zip
insertcoin-7.1.9-REPACK-M8_UL_L50_SENSE70_MR_HTC_Europe_4.16.401.10.zip
rom_one_m8_2.22.401.4_odexed.zip revolution HD
Android_Revolution_HD-One_M8_45.0_758ff1.zip
m8_1.54.401.5_AROMA
6) reboot phone, but stuck on bootloader
7) try to flash boot.img and stock recovery on the firmware but nothing change,
8) try to enter to stock recovery but redirected in bootloader
9) try to lock bootloader
I have do this with all firmware and rom
I have try to install with ruu.exe but the application have error 155, i have change the cid and mid to match with in the androidinfo.txt.
!!! But boot with custom like CM12, Carbon rom etc... the only problem is that the simcard is not detected.
If anyone have other solution ?
My last getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.401.4
(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: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please help, i will become the master of reflashing rom and firmware on HTC ONE M8 but corrupted.
Click to expand...
Click to collapse
Your device is a Sprint .. you shouldn't convert it to any Intl GSM/GPE. You shouldn't change its MID.
Not sure whether this is still fixable because on Verizon I know, this conversion will kill the radio.
Change back your MID to 0P6B70000
and get the correct firmware and RUU here : http://forum.xda-developers.com/showthread.php?t=2729173
Anything you're not sure, ask in that thread or in Sprint Q&A
Hold Power + Volume Up for at-least 20secs and when screen turns black, release the buttons and hold Volume Down until you enter bootloader... which is mainly couple of seconds.
Mr_Jack_Frost said:
Hold Power + Volume Up for at-least 20secs and when screen turns black, release the buttons and hold Volume Down until you enter bootloader... which is mainly couple of seconds.
Click to expand...
Click to collapse
The OP is already in bootloader, and stuck there.
CID Numbers (Sprint only):
SPCS_001: standard Sprint M8
SPCS_004: Harman/Kardon version M8
I would try to rewrite the correct cid--> Update Hboot to 3.19-->Relock Bootloader-->Flash latest Ruu
---------- Post added at 04:07 PM ---------- Previous post was at 04:06 PM ----------
bombo_b said:
CID Numbers (Sprint only):
SPCS_001: standard Sprint M8
SPCS_004: Harman/Kardon version M8
I would try to rewrite the correct cid--> Update Hboot to 3.19-->Relock Bootloader-->Flash latest Ruu
Click to expand...
Click to collapse
Tho latest Ruu should already contain the 3.19 Hboot
bombo_b said:
I would try to rewrite the correct cid--> Update Hboot to 3.19-->Relock Bootloader-->Flash latest Ruu
Click to expand...
Click to collapse
In addition to your comment, that hboot does not need to be updated before RUU (RUU will do it):
1) Need to change MID back to Sprint MID to RUU
2) Shouldn't need to change CID, but it doesn't hurt to do so.
3) No need to relock bootloader to RUU, since OP is s-off.
But I agree, the OP should try to RUU back to Sprint stock image. (and obviously take the actions to meet the requirements to do so). After that, if is still doesn't work its probably a radio brick.
redpoint73 said:
In addition to your comment, that hboot does not need to be updated before RUU (RUU will do it):
1) Need to change MID back to Sprint MID to RUU
2) Shouldn't need to change CID, but it doesn't hurt to do so.
3) No need to relock bootloader to RUU, since OP is s-off.
But I agree, the OP should try to RUU back to Sprint stock image. (and obviously take the actions to meet the requirements to do so). After that, if is still doesn't work its probably a radio brick.
Click to expand...
Click to collapse
Error 155 is usually fixed by relocking Bootloader. Since the phone is in a funny state I would advise putting all chances on your side. Dont worry if the logic says S-off doesnt need BL relocked , you just need every chance to flash Stock ruu back to the phone
Thanks, i will try it...
So, if it's work i can unlock the phone to use another operator ?
ckpv5 said:
Your device is a Sprint .. you shouldn't convert it to any Intl GSM/GPE. You shouldn't change its MID.
Not sure whether this is still fixable because on Verizon I know, this conversion will kill the radio.
Change back your MID to 0P6B70000
and get the correct firmware and RUU here : http://forum.xda-developers.com/showthread.php?t=2729173
Anything you're not sure, ask in that thread or in Sprint Q&A
Click to expand...
Click to collapse
Amazing, it's work :highfive:
Actualy, i'm working to unlock the SIM now....
ckpv5 said:
Your device is a Sprint .. you shouldn't convert it to any Intl GSM/GPE. You shouldn't change its MID.
Not sure whether this is still fixable because on Verizon I know, this conversion will kill the radio.
Change back your MID to 0P6B70000
and get the correct firmware and RUU here : http://forum.xda-developers.com/showthread.php?t=2729173
Anything you're not sure, ask in that thread or in Sprint Q&A
Click to expand...
Click to collapse
kimpak said:
Thanks, i will try it...
So, if it's work i can unlock the phone to use another operator ?
Click to expand...
Click to collapse
All right tout marche bien
kimpak said:
Amazing, it's work :highfive:
Actualy, i'm working to unlock the SIM now....
Click to expand...
Click to collapse
kimpak said:
All right tout marche bien
Click to expand...
Click to collapse
Good to hear that it worked for you.
How do you saw that my phone is for sprint version ?
ckpv5 said:
Your device is a Sprint .. you shouldn't convert it to any Intl GSM/GPE. You shouldn't change its MID.
Not sure whether this is still fixable because on Verizon I know, this conversion will kill the radio.
Change back your MID to 0P6B70000
and get the correct firmware and RUU here : http://forum.xda-developers.com/showthread.php?t=2729173
Anything you're not sure, ask in that thread or in Sprint Q&A
Click to expand...
Click to collapse
kimpak said:
How do you saw that my phone is for sprint version ?
Click to expand...
Click to collapse
(bootloader) product: m8_whl
m8_whl is Sprint device
m8_ul is GSM device
Boot Loader Loop, Unlocked, S-Off, Rooted HTC M8 Tmobile
A year ago I believe I used HBoot and or Firewater to root my M8. I recently removed some applications that seemed to make my phone act funny, and now the phone is stuck in a boot loop, or rather just a boot and stop at the second HTC "One" screen. Not exactly a loop.
I've download ADB tool and tried the fastboot method to install TWRP but have no success because the computer does not recognize the phone while running ADB or Fastboot, therefore I cant install TWRP and am stuck in the bootloader menu. I have tried various different cables and restarted the pc several times, and installed htc sync and other drivers necessary for that process. Also uninstalled and installed different drivers later as well. Now im not sure what i have installed but I have access to the phones internal drive via explorer.
Using Hboot.
Stats:
***UNLOCKED***
M8_UL PVT SHIP S-OFF
CID-HTC__32
RADIO- 1.15.2133156
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.54.401.5
eMMc-boot 2048MB
Mar 22 2014, 00:53:32.0
Options:
HBOOT (when scanning says that all images are not found)
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMART SD
IMAGE CRC
SHOW BARCODE
Recovery leads to nothing and eventually returns to the HTC One menu stop.
Reset does nothing, acts like fast boot actually.
Ramdump under fastboot seems to works, and does produce log files.
While the phone was still active, I managed to create a full "manual" backup of the device by plugging it in and backing up/copying the entire internal memory. After screwing with the phone and every option for several hours I managed to access the files of the internal memory by switching to recovery mode via the boot menu and then plugging in the phone via usb to comp while deleting the drivers at the same time. I tried a full restoration of the internal backup i made, by copy and replace if the same method, but still nothing.
Ive attached an image of the Hboot menu with the details and options of that Hboot for those of you familiar with hboot.
The ideal situation, or what i'd like to do is restore the phone without flashing the rom and loosing the information, then id like to upgrade to lollipop or a new custom rom I found here actually, but the first step is getting back into the phone which i would be very grateful for in general.
also, not great with cmd and all that stuff, I do have sdk tools downloaded and installed but not great with that either. If there was a more simple way to replace existing files in the phone via the file manager (because im able to access the internal drive via the file manager, that would be the most ideal and easiest situation. But knowing the path and the boot files and which files are necessary for boot is what im looking for as well.
Also i know how to flash a sd and htc has a sdcard slot as well. Also i should mention that prior to the phone being screwed up I did want to delete some internal certificates because i believe someone installed a spy application on the phone, hence the reason for all of this checkup and removal anyway. In the process of trying to do that, i followed a tutorial on this forum which suggested I create a security lock pin, which I did. This could also be the cause of the problem not being recognized by the adb or fastboot script.
Who ever helps me do that gets a tip.
Please help.
---------- Post added at 05:02 PM ---------- Previous post was at 04:49 PM ----------
JamesM8 said:
A year ago I believe I used HBoot and or Firewater to root my M8. I recently removed some applications that seemed to make my phone act funny, and now the phone is stuck in a boot loop, or rather just a boot and stop at the second HTC "One" screen. Not exactly a loop.
I've download ADB tool and tried the fastboot method to install TWRP but have no success because the computer does not recognize the phone while running ADB or Fastboot, therefore I cant install TWRP and am stuck in the bootloader menu. I have tried various different cables and restarted the pc several times, and installed htc sync and other drivers necessary for that process. Also uninstalled and installed different drivers later as well. Now im not sure what i have installed but I have access to the phones internal drive via explorer.
Using Hboot.
Stats:
***UNLOCKED***
M8_UL PVT SHIP S-OFF
CID-HTC__32
RADIO- 1.15.2133156
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.54.401.5
eMMc-boot 2048MB
Mar 22 2014, 00:53:32.0
Options:
HBOOT (when scanning says that all images are not found)
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMART SD
IMAGE CRC
SHOW BARCODE
Recovery leads to nothing and eventually returns to the HTC One menu stop.
Reset does nothing, acts like fast boot actually.
Ramdump under fastboot seems to works, and does produce log files.
While the phone was still active, I managed to create a full "manual" backup of the device by plugging it in and backing up/copying the entire internal memory. After screwing with the phone and every option for several hours I managed to access the files of the internal memory by switching to recovery mode via the boot menu and then plugging in the phone via usb to comp while deleting the drivers at the same time. I tried a full restoration of the internal backup i made, by copy and replace if the same method, but still nothing.
Ive attached an image of the Hboot menu with the details and options of that Hboot for those of you familiar with hboot.
The ideal situation, or what i'd like to do is restore the phone without flashing the rom and loosing the information, then id like to upgrade to lollipop or a new custom rom I found here actually, but the first step is getting back into the phone which i would be very grateful for in general.
also, not great with cmd and all that stuff, I do have sdk tools downloaded and installed but not great with that either. If there was a more simple way to replace existing files in the phone via the file manager (because im able to access the internal drive via the file manager, that would be the most ideal and easiest situation. But knowing the path and the boot files and which files are necessary for boot is what im looking for as well.
Also i know how to flash a sd and htc has a sdcard slot as well. Also i should mention that prior to the phone being screwed up I did want to delete some internal certificates because i believe someone installed a spy application on the phone, hence the reason for all of this checkup and removal anyway. In the process of trying to do that, i followed a tutorial on this forum which suggested I create a security lock pin, which I did. This could also be the cause of the problem not being recognized by the adb or fastboot script.
Who ever helps me do that gets a tip.
Please help.
Click to expand...
Click to collapse
**** I just realized it would be more appropriate to create a new thread for my problem rather than intruding on this mans problem, please see the One (M8) Q&A, Help & Troubleshooting. And respond there*****

ADB, Recovery and some issues

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?

Update firmware version

Hello everybody!
Actually I'm using the Android Revolution HD 12 and I would like to flash the ViperOne 6.0.0 ROM. The problem is my firmware version is 2.10.401.1 and I have S-ON.
I've flashed the ROM, but, obviusly, when I turned on my phone, it booted in bootloader mode.
I downloaded the RUU from the HTC site, it detected there was an avaible update, but it didn't work (Error 112: signature error). So I decided to extract the RUU.zip (following https://forum.xda-developers.com/showpost.php?p=64299817&postcount=3), rename the file, put it in the SD card ad flash throught download mode. At that point phone shows this message: "Failed: -2, 12: fail to flash via downloadzip".
I know probably it is a silly question, but I have always used Samsung phones and I don't know what I should do. Can you give me any advice to solve my problem?
br1battaglia said:
Hello everybody!
Actually I'm using the Android Revolution HD 12 and I would like to flash the ViperOne 6.0.0 ROM. The problem is my firmware version is 2.10.401.1 and I have S-ON.
I've flashed the ROM, but, obviusly, when I turned on my phone, it booted in bootloader mode.
I downloaded the RUU from the HTC site, it detected there was an avaible update, but it didn't work (Error 112: signature error). So I decided to extract the RUU.zip (following https://forum.xda-developers.com/showpost.php?p=64299817&postcount=3), rename the file, put it in the SD card ad flash throught download mode. At that point phone shows this message: "Failed: -2, 12: fail to flash via downloadzip".
I know probably it is a silly question, but I have always used Samsung phones and I don't know what I should do. Can you give me any advice to solve my problem?
Click to expand...
Click to collapse
Thank you for taking the time to review the readme thread. It's frustrating to try to offer support to users who skip that step and expect us to re-iterate what is already offered there.
What RUU did you attempt to install? Version number is important here, as you can upgrade a certain distance via RUU and then must use the OTA after that (upgrading from firmware 3.x to 4.x requires an OTA install).
I had somewhat the same problem this weekend, I used a different RUU (with the same CID) and the flashing worked, though I wasn't trying to do the same thing as you
computerslayer said:
Thank you for taking the time to review the readme thread. It's frustrating to try to offer support to users who skip that step and expect us to re-iterate what is already offered there.
What RUU did you attempt to install? Version number is important here, as you can upgrade a certain distance via RUU and then must use the OTA after that (upgrading from firmware 3.x to 4.x requires an OTA install).
Click to expand...
Click to collapse
I'm trying to flash 4.23.617.1 version.
If I open "android-info.txt" file, I read:
Code:
modelid: 0PJA10000
cidnum: HTC__001
cidnum: HTC__J15
cidnum: HTC__031
cidnum: HTC__102
cidnum: HTC__A07
cidnum: HTC__032
cidnum: HTC__M27
cidnum: HTC__016
cidnum: HTC__002
cidnum: HTC__Y13
mainver: 1.32.401.8
aareport:1
btype:1
My CID is H3G__402. Could it be the cause of my problem? If it's affermative, should I find an RUU who supports my CID or can I change the CID and flash the zip file I already have?
br1battaglia said:
I'm trying to flash 4.23.617.1 version.
If I open "android-info.txt" file, I read:
My CID is H3G__402. Could it be the cause of my problem? If it's affermative, should I find an RUU who supports my CID or can I change the CID and flash the zip file I already have?
Click to expand...
Click to collapse
Take another look at the readme thread, particularly the post (#3) on RUUs. Your phone SKU must match the SKU of the RUU.
Follow the instructions on the thread to determine your SKU and then download the appropriate RUU.
Since you are S-ON, keep in mind that you can not jump straight to installing Android Nougat - you can flash up to Marshmallow (3.xx.xxx.xx), but will have to update via OTA to Nougat (4.xx.xxx.xx)

Categories

Resources