Develop Bugs

[Q] Questions about android-info.txt

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

Help HTC Desire HD Vodafone (stuck): flashing custom rom after unlocking bootloader

Hi,
I need your kind advice in fixing my issue. I have DHD Vodafone 3.13.161.3 GB 2.3.5.
I unlocked the phone using HTC official method, phone got restored to factory default and I tried to flash a custom rom without knowing that I need to change the CID.
The phone starts but get stuck on HTC logo, I have EXT4 recovery installed already.
Tried wiping and factory reset but it seems that its of no use. I can boot to hboot, it says unlocked (highlighted) and s-on.
I did try to make a goldcard, put the sdcard in another phone and used the goldcard helper app then went to the site and submitted the CID and downloaded the image and followed the steps.
(got mmc0 and mmc1, I took mmc1 by manually writting it)
I copied another official rom PD98IMG.ZIP downloaded from the net for WWE and ARA versions copied them to SDcard and got into hboot but after loading it says wrong image and goes back to hboot.
I deseparate to get it fixed, would you plz provide some guidance on how to fix it since I was not able to get Vodafone RUU or any other mechanism to fix!
Appreciate your assistance and efforts..
*** Unlocked **
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MICROP-0438
RADIO-26.14.04.28_oot
eMMC-

If you unlocked from HTCdev you have to flash kernel in fast boot rename boot.IMG to pd98img.zip and accept update. Then remove or rename to pd98img.zip.bak so it doesn't keep updating. It's because of s-on you should be able to downgrade hboot and s-off.
Sent from my Inspire 4G using XDA

sammael1069 said:
If you unlocked from HTCdev you have to flash kernel in fast boot rename boot.IMG to pd98img.zip and accept update. Then remove or rename to pd98img.zip.bak so it doesn't keep updating. It's because of s-on you should be able to downgrade hboot and s-off.
Sent from my Inspire 4G using XDA
Click to expand...
Click to collapse
Thanks for your response Sammael,
Just some background info about my case:
I have DHD from Vodafone UK which was on the latest rom from Vodafone 2.3.5, I did bootloader unlock using HTCDev then flashed Ext4 recovery.
I tried flashing a custom rooted rom based on WWE version using the recovery mode (install zip from sdcard) after which I got the phone stuck on HTC logo screen everytime I try to power it on.
I tried using WWE RUUs with fastboot usb but got err155, I downloaded Vodafone PD98IMG.zip from that was uploaded by a guy in another forum but copying it to the sdcard and loading it using hboot gave me wrong image/rom message. I tried running WWE RUU then copying the PD98IMG.zip to the temp folder and renaming it to rom.zip after deleting the original rom.zip but again I got err155.
I need at least to get back on Vodafone stock rom and fix the problem, I am not sure if I need to relock the bootloader and if I must flash back the stock recovery.
Can anyone help with this as I have been trying different options for the last 4 days and all the tools that were mentioned need to have a functional phone to do usb debugging and charge only mode!
*** Unlocked***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Dec 22 2011,14:28:19

First will cover the obvious you should have unlocked via HTC dev. The hack kit is the way to go about things
Now for the fix.
Download a custom rom on PC, have androidsdk setup
Boot into recovery and reinstall your custom from.(remember to full wipe).
Once complete plug phone into PC and run adb reboot bootloader.
Once in boot loader select fast boot if its not already selected.(should read fast boot USB)
Now in the custom rom you download open it and take out the boot.img and put it wherever you have adb/fast boot folders
Then type the command
Fastboot flash boot boot.img
Fastboot reboot
You will have to do this every time you flash a new rom, since you HTC dev unlocked. I would search into relocking boot loader and using the hack kit
Sent from my Desire HD using XDA

marsdta said:
First will cover the obvious you should have unlocked via HTC dev. The hack kit is the way to go about things
Now for the fix.
Download a custom rom on PC, have androidsdk setup
Boot into recovery and reinstall your custom from.(remember to full wipe).
Once complete plug phone into PC and run adb reboot bootloader.
Once in boot loader select fast boot if its not already selected.(should read fast boot USB)
Now in the custom rom you download open it and take out the boot.img and put it wherever you have adb/fast boot folders
Then type the command
Fastboot flash boot boot.img
Fastboot reboot
You will have to do this every time you flash a new rom, since you HTC dev unlocked. I would search into relocking boot loader and using the hack kit
Sent from my Desire HD using XDA
Click to expand...
Click to collapse
Hi marsdta,
I sort of worried about doing what you suggested as my device still show the CID as VODAP001. Its on Ship S-On and the problem I got into was by flashing a custom rom through CWM.
Just to provide more info, I got the below details by running fastboot command getvar all. I also tried to run a WWE RUU with the goldcard plugged into my DHD but got this error message version-main failed status malformed 1 bytes!!
C:\windows\system32>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 2.00.0029
INFOversion-baseband: 26.14.04.28_M
INFOversion-cpld: None
INFOversion-microp: 0438
INFOversion-main: 3.13.0.0
INFOserialno: HT0C9RX00000
INFOimei: XXXXXXXXXX
INFOproduct: ace
INFOplatform: HBOOT-7230
INFOmodelid: PD9810000
INFOcidnum: VODAP001
INFObattery-status: good
INFObattery-voltage: 4174mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: fcef1579
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOregion-id: 0
all: Done!
finished. total time: 0.008s

I had some progress, relocked the bootloader and copied the PD98IMG.ZIP to sdcard. The phone starts loading the PD98IMG and then running the check, it fails on some point which I think might be the PD98IMG I got is older than the software raido/hboot installed on my phone. Below are the details.
Checking PD98IMG.zip
Main version older!
update failed
Press <Power> to reboot
The PD98IMG.zip has an android-info.txt that contains the following:
*********
modelid: PD9810000
cidnum: VODAP001
cidnum: VODAP102
cidnum: VODAP304
cidnum: VODAPE17
mainver: 2.50.161.3
hbootpreupdate:12
*********
When powering the phone with vol-down I see the following info
***Relocked***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Dec 22 2011,14:28:19
I think I may need the latest PD98IMG.zip to reflash the phone back to Vodafone stock software, plz correct me if I am wrong?
The PD98IMG.zip which was provided a vodafone uk phone owner seems to check the version of my phone's current state hboot/radio.
Is there any place where I can get the latest PD98IMG.zip even if I have to pay for it?

yabdali said:
I had some progress, relocked the bootloader and copied the PD98IMG.ZIP to sdcard. The phone starts loading the PD98IMG and then running the check, it fails on some point which I think might be the PD98IMG I got is older than the software raido/hboot installed on my phone. Below are the det
I think I may need the latest PD98IMG.zip to reflash the phone back to Vodafone stock software, plz correct me if I am wrong?
The PD98IMG.zip which was provided a vodafone uk phone owner seems to check the version of my phone's current state hboot/radio.
Is there any place where I can get the latest PD98IMG.zip even if I have to pay for it?
Click to expand...
Click to collapse
I haven't been able to find the newest ruu for your branded device. Best I can say is keep looking. But if you can't find it your going to have to flash a from how I suggested to get a working phone.
Or maybe wait and see if anyone has other ideas to try
Sent from my Inspire 4G using XDA

marsdta said:
I haven't been able to find the newest ruu for your branded device. Best I can say is keep looking. But if you can't find it your going to have to flash a from how I suggested to get a working phone.
Or maybe wait and see if anyone has other ideas to try
Sent from my Inspire 4G using XDA
Click to expand...
Click to collapse
Hi marsdta,
Thanks for your contribution..
I have relocked my bootloader, tried flashing the PD98IMG.zip but I got main version is older message.
I unzipped the PD98IMG.zip and tried flashing the radio and the boot in fastboot USB mode but signature failed!
Do you have any suggestion or insights about what else I should do?
D:\htctest\files>Fastboot flash radio radio.img
sending 'radio' (24960 KB)... OKAY [ 4.556s]
writing 'radio'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 7.792s
D:\htctest\files>Fastboot flash boot boot.img
sending 'boot' (2764 KB)... OKAY [ 0.502s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.864s

Did you try getting S-OFF via the Advanced Ace Hack Kit? I got a Vodafone DHD on release in Aus and was prompted to make a gold card, eventually managed S-OFF without one.

You get the main version older because your son. And you get the failed remote because your relocked the bootloader. Personally at this point I would unlock the boat loader again, flash cwr then a from and then its boot.img to get a working phone. Then if the pd98img/ruu that you need comes available go back and root properly. But for now I would say to at least get it in a useable state
Sent from my Inspire 4G using XDA

marsdta said:
You get the main version older because your son. And you get the failed remote because your relocked the bootloader. Personally at this point I would unlock the boat loader again, flash cwr then a from and then its boot.img to get a working phone. Then if the pd98img/ruu that you need comes available go back and root properly. But for now I would say to at least get it in a useable state
Sent from my Inspire 4G using XDA
Click to expand...
Click to collapse
Hi marsdta,
Thanks again. Just a quick clarification, which boot.img do you suggest I should flash after unlocking the bootloader and flashing cwm?

yabdali said:
Hi marsdta,
Thanks again. Just a quick clarification, which boot.img do you suggest I should flash after unlocking the bootloader and flashing cwm?
Click to expand...
Click to collapse
Depends on what rom you want to install.
So let's say you want to flash cm. Download the rom on your pc. Place a copy of it on your SD card as well. Boot into cwr and flash as usual. Once complete boot into the boot loader.(using adb reboot boatlader is convenient, but you could do it manually by pulley battery and powering up with volume down+power button)
Then take out the boot.img of cm zip and flash as you tried earlier(fastboot flash boot boot.img)
Then reboot phone
Sent from my Inspire 4G using XDA

marsdta said:
Depends on what rom you want to install.
So let's say you want to flash cm. Download the rom on your pc. Place a copy of it on your SD card as well. Boot into cwr and flash as usual. Once complete boot into the boot loader.(using adb reboot boatlader is convenient, but you could do it manually by pulley battery and powering up with volume down+power button)
Then take out the boot.img of cm zip and flash as you tried earlier(fastboot flash boot boot.img)
Then reboot phone
Sent from my Inspire 4G using XDA
Click to expand...
Click to collapse
Thankssssssssssssssssssssssssssssssssssssssss
That did the trick, my phone is now up and running smoothly. You are the man, big THANK YOU.

NOPE Help me ! hurry up
MY DEVICES IS TURNED ON.BUT ACCIDENTALLY TURNED OFF.
NOW i can't push recovery.
my recovery (touch clock work mod) can't flash rom and hang on flashing boot.img and give error (status 7).
my device don't accept pd98img.
cant flash boot.img in fastboot : (remote not allowed)
can't write cid 11111111 or HTC__001
dont accept xtc clip.
dont accept goldcard.
dont accept boot.img renamed to pd98img.zip
just can lock and unlock with fastboot.
Note : when i'm going to clock work mod say E:Can't open /cache/recovery/log
E:can't open /cache/recovery/lat_log
just cry
Plz Help Me

Hi.
I have the same problem as described here. But my desire HD is the spanish vodafone version.
I found the original RUU here: https://docs.google.com/file/d/0B7S5vzd6Qvh9SDR4cmRwTGZWaXc/edit?usp=sharing
- I will start renaming the file to PD98IMG.zip in the SD card
- Start in bootloader mode
- Push vol+ to start the flashing

Humano, did it work?
Sent from my ATRIX HD

[SOLVED] Bricked and can't find a matching RUU... please help!

Please help! I recently acquired a phone that was supposed to be an Inspire 4g (ATT, unlocked) but turned out to be a Desire HD (I know they are essentially the same) that is soft-bricked with firmwarez 3.13.161.5. It would appear based on the .161. that this is (maybe) a Vodafone branded phone.
Here are some stats from Hboot:
ACE PVT SHIP S-ON RL
HBOOT-2.00.0027
MICROP-0438
RADIO-26.14.52.27
eMMC-boot
sEP 7 2011,19:06:24
When I tried to run the latest vodafone RUU that I could find, the numbers were smaller than 3.13 and the RUU failed.
I thought to try and downgrade the Hboot to see if that worked, but ADB doesn't work, and being soft-brick, I can't enable USB debugging.
There is some software with the correct firmware #s on HTC's dev support page, but the downloadable files are neither RUU.exe or PD98IMG.zip format.
I'm stuck. If anybody has any methods that might help, or knows where I can get a 3.13.161.5 RUU I would be so very grateful.
Thanks,

Have you looked at www.shipped-roms.com?
Sent from my HTC Desire HD using xda app-developers app

ranger4740 said:
Have you looked at www shipped-roms com?
Click to expand...
Click to collapse
Yeah, I have but it seems the shipped-roms webpage seems to be constantly offline. I have been scouring the web, and www androidfiles org/ruu/?developer=Ace is the best resource I've found. They have nothing that will work for me.
I'm looking for a downgrade method that doesn't require a fully bootable phone, or an RUU that is 3.13.161.5 or higher. I can use fastboot, but not adb.
Is shipped-roms working for everybody else?

boot your phone to fastboot USB then just type fastboot oem rebootRUU.
Run the RUU and then go hunting in the temp folder just run in run box %temp%. there should be a file called rom.zip copy that to the same dir as fastboot if you can then simply run fastboot flash zip rom.zip then it should work. Make sure you have a goldcard though as you'll need that.

hacktrix2006 said:
boot your phone to fastboot USB then just type fastboot oem rebootRUU.
Run the RUU and then go hunting in the temp folder just run in run box %temp%. there should be a file called rom.zip copy that to the same dir as fastboot if you can then simply run fastboot flash zip rom.zip then it should work. Make sure you have a goldcard though as you'll need that.
Click to expand...
Click to collapse
Did what you said. Figured out that I needed to run the RUU , find rom.zip in %temp%, cancel RUU. I hope I did that right.
got this:
sending 'zip'
okay
writing 'zip"
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote:43 main version check fail)
I'm guessing this is a goldcard issue. I will try again with a fresh goldcard later tonight..
If anybody has any helpful comments, that would be wonderful....

umopapisdn said:
Did what you said. Figured out that I needed to run the RUU , find rom.zip in %temp%, cancel RUU. I hope I did that right.
got this:
sending 'zip'
okay
writing 'zip"
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote:43 main version check fail)
I'm guessing this is a goldcard issue. I will try again with a fresh goldcard later tonight..
If anybody has any helpful comments, that would be wonderful....
Click to expand...
Click to collapse
Sent you a PM mate.

hacktrix2006 said:
Sent you a PM mate.
Click to expand...
Click to collapse
Thanks again hacktrix2006 for all your wizardry. Got it working better than ever!
Devs, Close please?

Not a problem mate, glad to help. Maybe editing the Title to show [SOLVED] might help.
Enjoy S-Off'd phone mate. Try out CM10.1 and Sense 4+ roms when you have time.

hacktrix2006 said:
Not a problem mate, glad to help. Maybe editing the Title to show [SOLVED] might help.
Enjoy S-Off'd phone mate. Try out CM10.1 and Sense 4+ roms when you have time.
Click to expand...
Click to collapse
Great idea. I guess I just assumed that mods (not devs, silly me) read through everything... duh.
Doesn't [solved] imply that there is a solution in here somewhere? contact you, I guess was the solution. Thanks again!

[Q] Can't flash RUU firmware htc one m9

Hey guys, so I tried to flash RUU Firmware on my htc one m9. I downloaded the firmware, minimal adb flashboot, and htc sync manager. Problem is when I open command prompt via minimal adb flashboot and I type 'adb reboot downloader' it says:
adb server is out of date. killing...
* daemon started successfully *
error: device '(null)' not found
Am I missing something here? What should I do?

any chance you run a virtual android, genymotion or something of the like? And I would like to think aside from the drivers for HTC, the sync manager is best tucked safely away in the garbage

MrLizm said:
any chance you run a virtual android, genymotion or something of the like? And I would like to think aside from the drivers for HTC, the sync manager is best tucked safely away in the garbage
Click to expand...
Click to collapse
alright now I can get it to works however it says failed at the end.
C:\adb>adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
error: device unauthorized. Please check the confirmation dialog on your device.
C:\adb>adb reboot bootloader
C:\adb>fasboot oem rebootRUU
'fasboot' is not recognized as an internal or external command,
operable program or batch file.
C:\adb>fastboot oem rebootRUU
...
OKAY [ 0.048s]
finished. total time: 0.048s
C:\adb>fastboot flash zip 0PJAIMG.ZIP
target reported max download size of 800000000 bytes
sending 'zip' (61661 KB)...
OKAY [ 4.842s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] Not allow flash image except boot/recov
(bootloader) ery/system
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 14
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 14
(bootloader) [email protected]
FAILED (remote: 14: fail to flash via downloadzip)
finished. total time: 8.598s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.002s
C:\adb>
any idea how to make it successful?

Have to ask, you s-off?
This line makes me wonder,
(bootloader) ERR [SD_UPDATE_ERR] Not allow flash image except boot/recov
(bootloader) ery/system

MrLizm said:
Have to ask, you s-off?
This line makes me wonder,
(bootloader) ERR [SD_UPDATE_ERR] Not allow flash image except boot/recov
(bootloader) ery/system
Click to expand...
Click to collapse
How do i check it? Sorry I'm totally new in this kind of things

kamocheng said:
How do i check it? Sorry I'm totally new in this kind of things
Click to expand...
Click to collapse
if you boot to bootloader, should be up top there. from a booted phone just 'adb reboot bootloader' if it says s-on thats your problem. My guess is since you do not know your s-on/off you are probably s-on.

kamocheng said:
How do i check it? Sorry I'm totally new in this kind of things
Click to expand...
Click to collapse
No it says:
*** Software status: Modified ***
*** Unlocked ***
*** S-ON ***

so this is your problem, S-ON is the last piece of security for you. Without S-OFF you are unable to flash RUU the way your are attempting.
There is an app, Sunshine. Cost 25$ I am pretty sure and that will get you s-off. or you can wait until your carrier pushes the OTA and do a "Back To Stock" method. Well the app is free, it runs a check and makes sure it can get s-off. then it wants money.

MrLizm said:
so this is your problem, S-ON is the last piece of security for you. Without S-OFF you are unable to flash RUU the way your are attempting.
There is an app, Sunshine. Cost 25$ I am pretty sure and that will get you s-off. or you can wait until your carrier pushes the OTA and do a "Back To Stock" method. Well the app is free, it runs a check and makes sure it can get s-off. then it wants money.
Click to expand...
Click to collapse
Good to know, any idea how to get the app for free? Kinda tight on budget here. Thanks!

kamocheng said:
Good to know, any idea how to get the app for free? Kinda tight on budget here. Thanks!
Click to expand...
Click to collapse
Okay hold on, I remember when I rooted my phone it was S-Off. So to get it back to original factory version I need to S-on it?

kamocheng said:
Okay hold on, I remember when I rooted my phone it was S-Off. So to get it back to original factory version I need to S-on it?
Click to expand...
Click to collapse
No not at all, S-OFF makes it easier to get back to stock. If you were S-OFF at some point I am not too sure why the bootloader is reporting S-ON now. I am cheap and I revert to stock to get my OTAs to get the latest roms.. this is a huge pain. S-OFF is ideal once you have it you should keep it.

@kamocheng: Since I don't have much time at the moment I'm keeping it short:
1. Your zip is corrupted (look at the output). Re-download it and compare the MD5 checksums.
2. If you're s-on you need to be relocked for running RUUs.
3. You never mentioned your firmware version nor your CID so no one can verify whether you use the correct RUU.
4. There is no free version of sunshine since its a free app with in-app purchasement. But there is no need to s-off if you use the correct RUU.

Make sure htc sync isn't running on your computer.
Sent from my 0PJA10 using Tapatalk

Flippy498 said:
@kamocheng: Since I don't have much time at the moment I'm keeping it short:
1. Your zip is corrupted (look at the output). Re-download it and compare the MD5 checksums.
2. If you're s-on you need to be relocked for running RUUs.
3. You never mentioned your firmware version nor your CID so no one can verify whether you use the correct RUU.
4. There is no free version of sunshine since its a free app with in-app purchasement. But there is no need to s-off if you use the correct RUU.
Click to expand...
Click to collapse
Hello there, thanks for replying my thread
1. I'm sorry I dont quiet understand, do you mean zip in my PC or zip in my phone?
2. My firmware version is 1.32.617.30, how do i check my CID?
Correct me if I'm wrong but there are 2 options for me to return to original stock? First, S-off my phone and flash RUU firmware? Second, relocked my phone then run original stock? Since I didnt backup my original stock, I need to find untouched one?
Sorry this is my first android phone so if I'm total noob, I'm so sorry

What if i unrooted then relocked my phone, will i be able to take OTA then?

kamocheng said:
Hello there, thanks for replying my thread
1. I'm sorry I dont quiet understand, do you mean zip in my PC or zip in my phone?
2. My firmware version is 1.32.617.30, how do i check my CID?
Correct me if I'm wrong but there are 2 options for me to return to original stock? First, S-off my phone and flash RUU firmware? Second, relocked my phone then run original stock? Since I didnt backup my original stock, I need to find untouched one?
Sorry this is my first android phone so if I'm total noob, I'm so sorry
Click to expand...
Click to collapse
I'm talking about the zip you tried to flash in post 3. If you are using firefox as a browser I would recommend using an addon like DownThemAll! to verifiy the md5 checksum after the download has finished. Files can get corrupted during a download.
No, its one and the same way. You run the RUU either way. The only difference is that you can flash any firmware version with s-off and you don't need to relock while the versions you can flash with s-on have to match your current version (that means same version or newer) and your CID. Firmware versions with x.xx.617.xx are the developers editions if I'm not mistaking. (As far as I know AndroidRUU doesn't have any corresponding files. So I assume you downloaded it from clsA's personal collection of developer edition files since google didn't find any other sources for these files.) As said before redownload the file and compare the downloaded file's checksum with the one mentioned next to the download link (428582cef691c2e37053a0e19e9d738e). If they match the file should be flashable.
I prefer flashing RUUs using the sd-card method instead of fastboot so here are some instructions how I would continue:
Be sure to backup everything important like contacts, sms, etc. (I'm using MyPhoneExplorer for this step)
Get a SD-card that is not bigger than 32 gb and formatted to fat32 (I've always been using the formatting function of the m9 for this step).
Rename the RUU to "0PJAIMG.zip".
Copy that file into the root direction of your SD-card.
Relock your bootloader.
Put the card back into your phone.
Be sure that your phone is charged enough (more than 50 %).
Boot into download mode.
Follow the instructions on the screen.
Wait some minutes.
Done.

Flippy498 said:
I'm talking about the zip you tried to flash in post 3. If you are using firefox as a browser I would recommend using an addon like DownThemAll! to verifiy the md5 checksum after the download has finished. Files can get corrupted during a download.
No, its one and the same way. You run the RUU either way. The only difference is that you can flash any firmware version with s-off while the versions you can flash with s-on have to match your current version (that means same version or newer) and your CID. Firmware versions with x.xx.617.xx are the developers editions if I'm not mistaking. (As far as I know AndroidRUU doesn't have any corresponding files. So I assume you downloaded it from clsA's personal collection of developer edition files since google didn't find any other sources for these files.) As said before redownload the file and compare the downloaded file's checksum with the one mentioned next to the download link (428582cef691c2e37053a0e19e9d738e). If they match the file should be flashable.
I prefer flashing RUUs using the sd-card method instead of fastboot so here are some instruction how I would continue:
Be sure to backup everything important like contacts, sms, etc. (I'm using MyPhoneExplorer for this step)
Get a SD-card that is not bigger than 32 gb and formatted to fat32 (I've always been using the formatting function of the m9 for this step).
Rename the RUU to "0PJAIMG.zip".
Copy that file into the root direction of your SD-card.
Relock your bootloader.
Put the card back into your phone.
Be sure that your phone is charged enough (more than 50 %).
Boot into download mode.
Follow the instructions on the screen.
Wait some minutes.
Done.
Click to expand...
Click to collapse
So by doing that way, I dont have to S-off my phone to have it return to original stock?

kamocheng said:
So by doing that way, I dont have to S-off my phone to have it return to original stock?
Click to expand...
Click to collapse
Correct.
Edit: I just saw that you asked more or less the same question twice. jollywhitefoot's solution works the same way as the one I described. The only difference is that you are using fastboot instead of a sd-card.

Flippy498 said:
Correct.
Edit: I just saw that you asked more or less the same question twice. jollywhitefoot's solution works the same way as the one I described. The only difference is that you are using fastboot instead of a sd-card.
Click to expand...
Click to collapse
Alright, thank you for your guidance.

kamocheng said:
Alright, thank you for your guidance.
Click to expand...
Click to collapse
So my method in your other thread didn't work? Where are you running into problems?

Recover Softbricked HTC One (M7) Verizon after MobileIron on 6.22.605.3 S-ON Locked

Trying to recover an HTC One (M7) Verizon m7wlv for a friend of mine.
He wasn't trying to do anything "developery" to the phone. He said he installed some app off the market, and after a reboot it was softbricked.
UPDATE The App he tried installing was MobileIron which is a corporate app designs to encrypt the phone for corporate security needs. It was a requirement of the company he is working for.
So if you had this issue after installing MobileIron, then this is a good thread for you to read.
It comes up to the OS and complains, in blue:
Encryption unsuccessful
Encryption was interrupted and can't
complete. As a results, the data on your
phone is no longer accessible.
To resume using your phone, you need to
perform a factory reset. When you set up
your phone after the reset, you'll have an
opportunity to restore any data that was
backed up to your Google Account.
>Reset Phone<
When I click Reset Phone, the "Factory data reset" window open, then the phone reboots.
For a moment, it loads an upgrading phone screen(I believe)
And then hits recovery, and has the following errors at the bottom:
E: missing bitmap oem_unlock_bg
(Code -1)
E: missing bitmap oem_unlock_bg_yes
(Code -1)
E: missing bitmap oem_unlock_bg_no
(Code -1)
E: missing bitmap icon_ruu
(Code -1)
Backup necessary files in data partition
E:failed to mount /data (Invalid argument).. try emmc mount
Data wipe failed.
From the error screen, I am able to work my way to setting, by pressing home twice, and then, the ... menu in the top right, then Running Apps, then I can use the arrow left at the top left of the screen to reach the rest of the system menus.
I can get to build version, enable dev mode, enable usb debugging, and access adb shell.
Version information:
Android version: 5.0.2
Software number: 6.22.605.3
I can also get in to fastboot, and here is a fastboot getvar all:
INFOversion: 0.5
INFOversion-bootloader: 1.61.0000
INFOversion-baseband: 1.13.41.1209
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 6.22.605.3
INFOversion-misc: PVT SHIP S-ON
INFOserialno: XXXXXXXXXXX
INFOimei: XXXXXXXXXXXXXX
INFOmeid: XXXXXXXXXXXXXX
INFOproduct: m7_wlv
INFOplatform: HBOOT-8064
INFOmodelid: PN0731000
INFOcidnum: VZW__001
INFObattery-status: good
INFObattery-voltage: 4324mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-0e2a13e5
INFOhbootpreupdate: 11
INFOgencheckpt: 0
This is S-ON and Locked, so in theory, I can't flash an RUU unless it's a current or greater version, but I haven't seen an unmodded RUU for 6.22.605.3 or greater.
Any help would be appreciated.

nkk71 requested the getvar all above. Any further help is greatly appreciated.

mugendai said:
INFOversion-main: 6.22.605.3
INFOversion-misc: PVT SHIP S-ON
INFOproduct: m7_wlv
INFOplatform: HBOOT-8064
INFOmodelid: PN0731000
INFOcidnum: VZW__001
This is S-ON and Locked, so in theory, I can't flash an RUU unless it's a current or greater version, but I haven't seen an unmodded RUU for 6.22.605.3 or greater.
Any help would be appreciated.
Click to expand...
Click to collapse
the signed RUU you mentioned earlier: http://forum.xda-developers.com/verizon-htc-one/help/exe-ruu-vzw-m7-4-4-3-s-users-t2919442
should work
reboot to bootloader screen, and try running it again, check the log in C:\ruu_log\ folder if it get's stuck
EDIT: don't interrupt the ruu process, if the .exe doesnt work we'll switch to .zip

Alright thanks, I'll go give it a shot now

Tried it, and got further than before. Not sure if it's because I ran the utility while in rebootRUU mode, or if it's because I found a different driver, but it did at least try, before it failed.
The RUU is trying to flash to:
5.28.605.2
The phone is at: 6.22.605.3
I think it's failing because of the version number.
It gives this error in the GUI:
Code:
ERROR [140]: BOOTLOADER VERSION ERROR
The Firmware Update Utility cannot update your Android phone.
Please get the correct Firmware Update Utility and try again.
And here is what I believe is the relevant section of the ruu logs:
Code:
<T144720><DEBUG><OUT>(bootloader) checking main version...</OUT>
</DEBUG></T144720>
<T144720><DEBUG><OUT>Execution time is 9(s)</OUT>
</DEBUG></T144720>
<T144720><DEBUG><OUT>FAIL43 main version check fail</OUT>
</DEBUG></T144720>
<T144720><DEBUG><OUT>FAILED (remote: 43 main version check fail)</OUT>

mugendai said:
The RUU is trying to flash to:
5.28.605.2
The phone is at: 6.22.605.3
<T144720><DEBUG><OUT>FAIL43 main version check fail</OUT>
</DEBUG></T144720>
<T144720><DEBUG><OUT>FAILED (remote: 43 main version check fail)</OUT>[/CODE]
Click to expand...
Click to collapse
the zip should work

mugendai said:
Tried it, and got further than before. Not sure if it's because I ran the utility while in rebootRUU mode, or if it's because I found a different driver, but it did at least try, before it failed.
The RUU is trying to flash to:
5.28.605.2
The phone is at: 6.22.605.3
I think it's failing because of the version number.
It gives this error in the GUI:
Code:
ERROR [140]: BOOTLOADER VERSION ERROR
The Firmware Update Utility cannot update your Android phone.
Please get the correct Firmware Update Utility and try again.
And here is what I believe is the relevant section of the ruu logs:
Code:
(bootloader) checking main version...
Execution time is 9(s)
FAIL43 main version check fail
FAILED (remote: 43 main version check fail)
Click to expand...
Click to collapse
I have that version uploaded. Let me dig up the link.
Edit..
https://www.androidfilehost.com/?fid=24052804347761412
Rename it to rom.zip and copy it into the exe folder.
Sent from my HTC6535LVW using Tapatalk

nkk71 said:
the zip should work
Click to expand...
Click to collapse
The zip won't work if the mainver is older since he is s-on.
Sent from my HTC6535LVW using Tapatalk

dottat said:
The zip won't work if the mainver is older since he is s-on.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
the zip flashed just fine, proper, LargeZip, proper signature/encryption, proper, version
Code:
[B][email protected][/B]....³êÖ..nQ#£ÕêH%$SX............³éÖ.Mƒz £g™%‚Nh.ø.m.................„’{)................................................................................................................................................................................–A?úû.#q.Nê«uEB.ã...2½ØÒ¬ä:hêesº‚}.Ô8»=¿…ô.VËõhM.¼÷ą̃XèFý±€¬.¿N..}V¤.¦Ü...ÅFŒ$p«<›Ø³.Ž.{NV..žÐ®KÒtÈî§ùV...)7f9±ÿ´.7.•§5Æ<Sð£.f˜š*(g*å·ž..âÒ¡ÁK計•‹;H.Ê.[’..Õó*.ˆ“ƒÔµ0.Ù.-.y.ƒ“.V‡/B·«xÆês.”A:m},³æœæ~.V*.õdô[email protected]Í….¬¯9ìl°.ÿ..v-o8rFhÕÔä*·•=.¨µ·E%.i0.ˆ±_Šc.è[email protected]$.“.ÿÿÿÿÿÿÿÿÿÿ[B][COLOR="Blue"]6.22.605.3[/COLOR][/B]
edit: didnt seem to have solved the encryption thingy... maybe that's in misc... just guessing

nkk71 said:
the zip flashed just fine, proper, LargeZip, proper signature/encryption, proper, version
Code:
[B][email protected][/B]....³êÖ..nQ#£ÕêH%$SX............³éÖ.Mƒz £g™%‚Nh.ø.m.................„’{)................................................................................................................................................................................–A?úû.#q.Nê«uEB.ã...2½ØÒ¬ä:hêesº‚}.Ô8»=¿…ô.VËõhM.¼÷ą̃XèFý±€¬.¿N..}V¤.¦Ü...ÅFŒ$p«<›Ø³.Ž.{NV..žÐ®KÒtÈî§ùV...)7f9±ÿ´.7.•§5Æ<Sð£.f˜š*(g*å·ž..âÒ¡ÁK計•‹;H.Ê.[’..Õó*.ˆ“ƒÔµ0.Ù.-.y.ƒ“.V‡/B·«xÆês.”A:m},³æœæ~.V*.õdô[email protected]Í….¬¯9ìl°.ÿ..v-o8rFhÕÔä*·•=.¨µ·E%.i0.ˆ±_Šc.è[email protected]$.“.ÿÿÿÿÿÿÿÿÿÿ[B][COLOR="Blue"]6.22.605.3[/COLOR][/B]
edit: didnt seem to have solved the encryption thingy... maybe that's in misc... just guessing
Click to expand...
Click to collapse
You sent him to my thread for 4.4.3 signed zip....which is I posted the zip for 5.0.2 (6.22.605.3).
So I'm guessing you got the zip for 6.22.605.3 from somewhere else.
Sent from my HTC6535LVW using Tapatalk

dottat said:
You sent him to my thread for 4.4.3 signed zip....which is I posted the zip for 5.0.2 (6.22.605.3).
So I'm guessing you got the zip for 6.22.605.3 from somewhere else.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
yours as well from here: https://www.androidfilehost.com/?fid=24052804347761412

nkk71 said:
yours as well from here: https://www.androidfilehost.com/?fid=24052804347761412
Click to expand...
Click to collapse
I just put two and two together from Zanzibar asking me about it earlier.
OK. So let's get the op to try this while booted to fastboot.
Fastboot oem task 28
Fastboot oem task 29
Then flash ruu zip and cross fingers.
Sent from my HTC6535LVW using Tapatalk

dottat said:
Fastboot oem task 28
Fastboot oem task 29
Click to expand...
Click to collapse
I'm curious now what are those , i've only dealt with a few [usually not used] oem commands as a [possibly sloppy] workaround for the misc partition fix, but never posted them openly due to my lack of knowledge of what they actually do :angel:

nkk71 said:
I'm curious now what are those , i've only dealt with a few [usually not used] oem commands as a [possibly sloppy] workaround for the misc partition fix, but never posted them openly due to my lack of knowledge of what they actually do :angel:
Click to expand...
Click to collapse
so 28 will wipe /data from fastboot
29 will format binary file system for /cache /data /system (system only on an s-off phone).
and I should add that most of the time if the phone doesn't have EMMC issues these commands will fix being locked out due to encryption issues.

dottat said:
so 28 will wipe /data from fastboot
29 will format binary file system for /cache /data /system (system only on an s-off phone).
and I should add that most of the time if the phone doesn't have EMMC issues these commands will fix being locked out due to encryption issues.
Click to expand...
Click to collapse
oh boy, you do realize i'm gonna run those (and bad encryption) on my m7 tomorrow

dottat said:
I have that version uploaded. Let me dig up the link.
Edit..
https://www.androidfilehost.com/?fid=24052804347761412
Rename it to rom.zip and copy it into the exe folder.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
I tried this zip, and it DID flash, however, I got errors during the flash:
Code:
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Restart the same procedure with "hboot-preupdate" response for (FA37HS903177)...
< waiting for device >
sending 'zip'... (46522 KB) OKAY
writing 'zip'... (bootloader) adopting the signature contained in this image...
The flash did not stop there, it kept going all the way through.
I tried running it a second time, and got the same error.
I tried rebooting, but the phone is still in the same state with the encryption error, and can't wipe /data
So close, totally expected the RUU to fix this.
You posted some other things to try, below, I will test those and reply.
Thanks for your time!

mugendai said:
I tried this zip, and it DID flash, however, I got errors during the flash:
Code:
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Restart the same procedure with "hboot-preupdate" response for (FA37HS903177)...
< waiting for device >
sending 'zip'... (46522 KB) OKAY
writing 'zip'... (bootloader) adopting the signature contained in this image...
The flash did not stop there, it kept going all the way through.
I tried running it a second time, and got the same error.
I tried rebooting, but the phone is still in the same state with the encryption error, and can't wipe /data
So close, totally expected the RUU to fix this.
You posted some other things to try, below, I will test those and reply.
Thanks for your time!
Click to expand...
Click to collapse
Yes. That is a normal flash.
Let us know the results of the added commands
Sent from my HTC6535LVW using Tapatalk

I did OEM 28 only, and did a reboot, and have a very promising "Android is upgrading..."
Will update you when it gets through the 278 apps...

Phone is back up and running. I suspect that this command alone would have resolved the origional problem.
Thank you very much for your help. I'll update the OP tonight with the solution.

mugendai said:
Phone is back up and running. I suspect that this command alone would have resolved the origional problem.
Thank you very much for your help. I'll update the OP tonight with the solution.
Click to expand...
Click to collapse
good deal....back from the land of despair.