Develop Bugs

Can not fix Splash screen, System Formatted- ERROR 140/Main Version Older

Hello. Can ANYONE please please help?
I started Rooting process- total Newbie but undergoing a BAPTISM OF FIRE!!
UNLOCKed BL, CWM 5.0.2.8. Then, with no back-up made- System Format!
I have been trying to restore my soft-bricked (stuck on Splash screen), but I have hit an issue. I can not find a 100% match for an RUU. Phone will not accept RUU.exe NOR any ROM.zip
I tried custom ROMS from here via SD card initially
Then, I've tried to flash (Bootloader RELOCKED, CWM installed) via:
RUU_Marvel_S_HTC_Europe_2.13.401.3_Radio_47.23c.35.3037_7.54.39.28M_release_236989_signed.exe
99.9% ROM match- it is 401.3, (I recorded mine in written notes as 401.2); BUT 0% radio match- I have 7.57.39.10.
My ROM 2.13.401.2/ my software- 2.26.401.3/ my radio: 7.57.39.10M- a combo of RUU 2.13's ROM & RUU 2.26's software & radio (OTA updated at some point perhaps?)
It looked as though it would work, BUT, I got:
HTC Android ROM Update Utility 1.0.3.2011
ERROR [140]: BOOTLOADER VERSION ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again
As software is 2.26.401.3 I tried: RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed.exe.
0% ROM match but 100% match of software id & 100% radio match
With this:
1) Tried to flash exe direct. Got: "ERROR [140]: BOOTLOADER VERSION ERROR".
2) Retried to flash RUU after ripping recovery.img from ROM.zip & placed in folder with the adb files. Got: Same result.
3) I tried microSD card flash with ROM.zip, (BL UNlocked) taken from RUU_Marvel_S_2.26........route. Got "Error: Main Version is older!"
Tried PG76IMG from [ROM][HTC][WILDFIRE S A510e][EUROPE][2.3.5][PG76IMG.ZIP] To Flash From Hboot, "Installation aborted; bad!"- multiple downloads, multiple tries- file is 152 MB & I keep getting 148 MB (151,553KB).
I also tried to flash PG76IMG_Marvel_HTC_Europe_2.13.401.2_Radio_47.23a.35.3035H_7.53.39.03M_release_225747_signed.zip from shipped-roms
[100% ROM match & 0% radio] via SD card.
Got it wrong!! At least all it did was wipe CWM & did not full-brick! So now my Recovery was back to default: Android system recovery <3e> but I could un-unlock/ re-lock BL & put CWM back, no probs.
So I read multiple threads/ sites over the past week on both "Error 140" & "Main version is older", & can not find an answer. They are mostly either other-Model related or unresolved amongst other things.
,
I decided to quit while I'm ahead [just Slash screen with UN/RE lockable BL & able to CWM] & post this in hope of knowledgeable assistance. Surely, this IS self-fixable? What am I doing/ not doing?
My options, as far as I can tell, from shipped-roms.com are:
RUU_Marvel_S_HTC_Europe_2.13.401.3_Radio_47.23c.35.3037_7.54.39.28M_release_236989_signed.exe OR.......
Marvel_S_HTC_Europe_2.13.401.3_Radio_47.23c.35.3037_7.54.39.28M_release_236989_signed_ROM.zip
Both are 99.9% ROM match- they are 401.3, I recorded mine as 401.2; BUT 0% radio match- I have 7.57.39.10.
Can not see it being RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed.exe?
Q; (1) Why RUU/ROM.zips are not flashing/ which & version to use??
Q: (2) Do I need to downgrade something? If so what & how?
Q. (3) Any thoughts, anyone anything?
FULL HANDSET STATS:
Wildfire S A510E
***RELOCKED***
Marvel PVT SHIP S-ON RL
MICROP-0451
Radio 7.57.39.10M
Android: 2.3.5
ROM: 2.13.401.2
Software: 2.26.401.3
Kernal: 2.6.35.10
HBoot: 1.09.0099
HTC Sense Version: 2.1
Carrier: Unlocked
fastboot getvar all (with serial/ imei #s edited):
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0099
(bootloader) version-baseband: 7.57.39.10M
(bootloader) version-cpld: None
(bootloader) version-microp: 0451
(bootloader) version-main: 19.26.401.3
(bootloader) serialno: ############
(bootloader) imei: ###############
(bootloader) product: marvel
(bootloader) platform: HBOOT-7227
(bootloader) modelid: PG7610000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4073mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 510e562c
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s
Thanks.

I was looking for an exact RUU.exe for my ROM: 2.13.401.2 NOT .3 as offered by shipped-roms & others.
After trawling Google I found this: tsar3000.com/Joomla. Clicked downloads tab along the top, chose HTC & scanned down the list. I picked #42 (HTC WildeFire S A510E / A510c / MetroPCS - Marvel / C Stock Roms)
Looking down it I found RUU_Marvel_S_HTC_Europe_2.13.401.2_Radio_47.23a.35.3035H_7.53.39.03M: an EXACT RUU.exe match for my ROM.
<clicked RUU link> took me to a file share website: fileom.com.
Created account, & after verifying by clicking link & email, downloaded RUU.
Then:
1) RELOCKED BootLoader- cmd prompt & typed: fastboot oem lock
The tried a straight RUU.exe flash. This returned the ERROR 140: BOOTLOADER VERSION ERROR etc.
2)Started RUU; went NO FURTHER.
Clicked START on PC. Searched for %temp% folder. Found the two created when RUU is run.
To do this- call up the temp folder. Kill the RUU. Restart the RUU.
Keep doing this and you begin to notice 2 folders will appear when RUU is started & disappear when RUU is stopped.
Checked both to find a .zip called "ROM.zip".
Took it to a new folder so it did not interfere with anything. Unzipped it.
Copied 3 of the revealed files to the \Android folder (my folder containing my ROOTing files- adb/ BootLoader unlock file from HTC/ etc.)
The 3 are recovery.img, boot.img & system.img
Then:
RE-UnLocked BootLoader- opened cmd prompt & typed cd \Android; as my HTCdev Unlock file was still in \Android
Then typed fastboot flash unlocktoken Unlock_code.bin.
Agreed the pop-up on the handset. It booted itself to the Splash screen. I disconnected USB & pulled/ replaced battery.
Booted into HBOOT>Fastboot & connected USB
I proceeded to flash the 3 .img files by typing in cmd prompt:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Just for good measure I relocked the BootLoader, as I knew it would restart the phone in Normal boot without me having to interfear with the handset.
I typed: fastboot oem lock in cmd prompt
WHAT HAPPENED NEXT????
Phone reboots
Black screen with double arrows in circle, stays for 30 secs, then...
White htc screen as before EXCEPT THIS TIME I got "quietly brilliant" written underneath & do-di-do-do-do-do jingle.
Phone paused on "quietly brilliant" screen for one-and-a-half minutes......then......the standard phone set-up screens & ON!!!!!!!
YESSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Handset is working, has all the apps etc as before. The only change is the "about phone" section of settings. It is a bit more basic with the info it yeilds, as software is older than what I had.
I suppose this will change as OTA updates come in. I can live with that for now!!
PHONE IS RESTORED!!!!!!!!!!!!!!!!!!!!!

GERJDOY said:
I was looking for an exact RUU.exe for my ROM: 2.13.401.2 NOT .3 as offered by shipped-roms & others.
After trawling Google I found this: tsar3000.com/Joomla. Clicked downloads tab along the top, chose HTC & scanned down the list. I picked #42 (HTC WildeFire S A510E / A510c / MetroPCS - Marvel / C Stock Roms)
Looking down it I found RUU_Marvel_S_HTC_Europe_2.13.401.2_Radio_47.23a.35.3035H_7.53.39.03M: an EXACT RUU.exe match for my ROM.
<clicked RUU link> took me to a file share website: fileom.com.
Created account, & after verifying by clicking link & email, downloaded RUU.
Then:
1) RELOCKED BootLoader- cmd prompt & typed: fastboot oem lock
The tried a straight RUU.exe flash. This returned the ERROR 140: BOOTLOADER VERSION ERROR etc.
2)Started RUU; went NO FURTHER.
Clicked START on PC. Searched for %temp% folder. Found the two created when RUU is run.
To do this- call up the temp folder. Kill the RUU. Restart the RUU.
Keep doing this and you begin to notice 2 folders will appear when RUU is started & disappear when RUU is stopped.
Checked both to find a .zip called "ROM.zip".
Took it to a new folder so it did not interfere with anything. Unzipped it.
Copied 3 of the revealed files to the \Android folder (my folder containing my ROOTing files- adb/ BootLoader unlock file from HTC/ etc.)
The 3 are recovery.img, boot.img & system.img
Then:
RE-UnLocked BootLoader- opened cmd prompt & typed cd \Android; as my HTCdev Unlock file was still in \Android
Then typed fastboot flash unlocktoken Unlock_code.bin.
Agreed the pop-up on the handset. It booted itself to the Splash screen. I disconnected USB & pulled/ replaced battery.
Booted into HBOOT>Fastboot & connected USB
I proceeded to flash the 3 .img files by typing in cmd prompt:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
Just for good measure I relocked the BootLoader, as I knew it would restart the phone in Normal boot without me having to interfear with the handset.
I typed: fastboot oem lock in cmd prompt
WHAT HAPPENED NEXT????
Phone reboots
Black screen with double arrows in circle, stays for 30 secs, then...
White htc screen as before EXCEPT THIS TIME I got "quietly brilliant" written underneath & do-di-do-do-do-do jingle.
Phone paused on "quietly brilliant" screen for one-and-a-half minutes......then......the standard phone set-up screens & ON!!!!!!!
YESSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Handset is working, has all the apps etc as before. The only change is the "about phone" section of settings. It is a bit more basic with the info it yeilds, as software is older than what I had.
I suppose this will change as OTA updates come in. I can live with that for now!!
PHONE IS RESTORED!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
I am glad that your nightmare has ended :victory:

ukyo_tachibana said:
I am glad that your nightmare has ended :victory:
Click to expand...
Click to collapse
THANK YOU!
Yes, so am I. Just really really pleased that I could fix this & not have to rely on professional repair. Also, I am learning SO MUCH about software repair & rooting in the process that it's brillant!
Just waiting for the O.T.A. Updates to come through. I have already had 1 that has upgraded my software from 401.2 to .3. I do a "Check for Update" every 20 minutes or so,
Once this is done, I can reinstall CWM (as I have read that CWM can affect the installation of O.T.A.U.s ). Once I am back to, say 2.26.401.3 software, I will re-install CWM, do A BACK-UP (Hahaha!) & proceed to install SU app./ Custom ROM etc.
Thanks.

can you send me the file ruu......? please
GERJDOY said:
THANK YOU!
Yes, so am I. Just really really pleased that I could fix this & not have to rely on professional repair. Also, I am learning SO MUCH about software repair & rooting in the process that it's brillant!
Just waiting for the O.T.A. Updates to come through. I have already had 1 that has upgraded my software from 401.2 to .3. I do a "Check for Update" every 20 minutes or so,
Once this is done, I can reinstall CWM (as I have read that CWM can affect the installation of O.T.A.U.s ). Once I am back to, say 2.26.401.3 software, I will re-install CWM, do A BACK-UP (Hahaha!) & proceed to install SU app./ Custom ROM etc.
Thanks.
Click to expand...
Click to collapse
can you send me the file ruu......? please

Rogue One X

Ok - so I acquired a "bricked" One X.
When I got it, it supposedly had a boot loop - occasionally booted into the Sense ROM that was installed - but whenever it got there, it hung.
So I couldn't tell properly, if it had USB debugging activated.
But - I do appear to have been able to unlock the device - because when you go into the Boot Loader, it does say UNLOCKED.
However - all of my attempts so far to chuck a new ROM on it have failed.
I did try at one point to put the proper nandroid backup on the device (it comes back saying it's CID is VODAP001).
But my attempts to do that failed. (I seem to recall something about wrong MD5 sum or something like that).
I have been able to put clockworkmod 5.8.4.0 on it
HBOOT 1.72.0000 is on it.
So - I tried installing CM10 - flashes the boot.img ok - but installing the ROM fails.
Initially with a Status 7 error (and then after I tried the "trick" to remove the "assert" line from the updater-script, it just failed, with no error number displayed).
I tried also with CM11 - and it fails too. (Status 7)
I've tried a few things to find out about the device - I can get the CID as above - but can't pull the MID (using Automated Fastboot Commands V2.3 by Team Hex)
When I try "adb devices" no devices are listed.
But it can mount as USB storage - I can copy files to the devices.
But I'm stuck.
So - I'm wondering - what can I do here?
Anything?
PS - though it might sound from the above that I know a wee bit about this stuff - that's it - I know a wee bit.
I managed to fix my own phone recently (another One X) which is now running CM11 - but that was a painful experience too.
So - any guidance please be patient with me!!!
Any help is really appreciated though.

subharmonic said:
Ok - so I acquired a "bricked" One X.
When I got it, it supposedly had a boot loop - occasionally booted into the Sense ROM that was installed - but whenever it got there, it hung.
So I couldn't tell properly, if it had USB debugging activated.
But - I do appear to have been able to unlock the device - because when you go into the Boot Loader, it does say UNLOCKED.
However - all of my attempts so far to chuck a new ROM on it have failed.
I did try at one point to put the proper nandroid backup on the device (it comes back saying it's CID is VODAP001).
But my attempts to do that failed. (I seem to recall something about wrong MD5 sum or something like that).
I have been able to put clockworkmod 5.8.4.0 on it
HBOOT 1.72.0000 is on it.
So - I tried installing CM10 - flashes the boot.img ok - but installing the ROM fails.
Initially with a Status 7 error (and then after I tried the "trick" to remove the "assert" line from the updater-script, it just failed, with no error number displayed).
I tried also with CM11 - and it fails too. (Status 7)
I've tried a few things to find out about the device - I can get the CID as above - but can't pull the MID (using Automated Fastboot Commands V2.3 by Team Hex)
When I try "adb devices" no devices are listed.
But it can mount as USB storage - I can copy files to the devices.
But I'm stuck.
So - I'm wondering - what can I do here?
Anything?
PS - though it might sound from the above that I know a wee bit about this stuff - that's it - I know a wee bit.
I managed to fix my own phone recently (another One X) which is now running CM11 - but that was a painful experience too.
So - any guidance please be patient with me!!!
Any help is really appreciated though.
Click to expand...
Click to collapse
If you have CM11 on your sd card flash TWRP 2.8.1 and then install it and flash the boot.img. If you don't have any rom on the sd card flash Philz 5.15.9 then mount sd card copy what you need on your sd card then flash TWRP2.8.1 then install the rom and flash the boot.img

Does TWRP 2.8.1.0 work on the One X?
The unit is an Endevour... ie Tegra 3 based International version...

Ok - so I tried installing several versions of TWRP - only TWRP 2.4.0.0 would let me do anything (ie Touch was activated).
None of them would let me install the ROMs due to the MD5 thing again.
I reverted to the clockworkmod 5.8.4.0 - and this let me install CM10 - but it doesn't get out of boot - I just see the white HTC screen and it hangs.
I did the flash at 66% battery though - could that be the problem?
PS - given that I couldn't actually check at any stage to see if USB debugging was enabled - is it likely to be the case that it is - given that I've been able to unlock the device and flash various recoveries?

Still no further forward...

So to recap...
I've can flash recoveries.
Everytime I try to put on CM10 or 11, I get a Status 7 error - or, it says I have an MD5 mismatch - or it just says installation aborted.
It seems that I can flash boot.img ok.
Whenever I try to flash - I clear the cache, and Dalvik cache - and before reboot just to make sure, I flash the boot.img again.
Each time I just get the white HTC screen.
My device has CID VODAP001.
Any suggestions? (apologies for the bump).

Still stuck with this thing.
Fastboot works ok - here's the getvar all
version: 0.5a
version-bootloader: 1.72.0000
version-baseband: 5.1204.164D3.31
version-cpld: None
version-microp: None
version-main: 4.17.161.3
serialno:
imei:
product: endeavoru
platform: HBOOT-T30S
modelid: PJ4610000
cidnum: VODAP001
battery-status: good
battery-voltage: 4157mV
devpower: 100
partition-layout: None
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
adb devices doesn't show any devices attached though?
Any ideas what I could try?
I keep getting a Status 7 error on installing CM10, or CM11 or even GAPPS for 4.4.3 - eg
set metadata_recursive: some changes failed
Error in /sdcard/ROMS/... etc (Status 7)
Flashing some recoveries don't work - ie recoveries which are supposedly meant to work (ie clockworkmod recovery 6.0.4.8 - the one recommended by CM to install before trying to flash CM11 - doesn't even run properly).

Not sure if this is relevant, but when in recovery, the phone is listed when adb devices is run.
ie
SH25.......... recovery

Just tried to ADB sideload CM11.
*failed to write data 'protocol fault (no status)'*
So that didn't work either...

subharmonic said:
Just tried to ADB sideload CM11.
*failed to write data 'protocol fault (no status)'*
So that didn't work either...
Click to expand...
Click to collapse
PS - tried the ADB sideload - this time it did work - but on installation of the package, it failed again.
Same error but different location this time?
set_metadata_recursive: some changes failed
E: Error in /tmp/update.zip
Status 7
Installation aborted

Did I mention that I'm a noob?
Didn't realise that ADB only works when in recovery - and not when in bootloader.
Oh well.
Does that mean I might be able to flash an RUU then?
I'd rather not to be honest - I don't want stock - esp given that it was originally a Vodafone One X.
I'd rather go with CM11 if possible.
It just doesn't want to install it though.
I do have Philz 5.11.2 - HTC One X installed, and it seems to do most things I'm finding handy right now - ie charging when in recovery - mounting drives etc.

[Help] Restoring to Stock

So I just got my new cell phone, my first time with Android, and a few days ago I messed up. I followed this video to try and root my device : Sakitech's video on 'How to Root your HTC One M9 (Full Guide) - sorry can't post links
It ended up in a bootloop, I tried a few things and ended up installing Android HD Revolution 20.0 as my OS. I did it, but I had one problem : I didn't have any service with my provider anymore
So I panicked, tried a few things and ended up relocking my phone, while still being S-ON. I tried more stuff, without really knowing exactly what I was doing, and now my ADB cannot recognize my phone anymore. (when I do cmd adb devices it doesn't show up) I tried everything : re-installing all the drivers I could, pdaNet, changing environment variables, nothing works. It also cannot go in recovery mode anymore, so it is impossible for me to install the TWRP backup I found which is an exact match to my phone and provider (videotron) :
kernel: lk
product: htc_himaulatt
version: 1.0
version-main: 3.38.1530.2
version-baseband: 01.01_U11440801_96.01.51207G_F
version-bootloader: 1.0.0.0000
mid: 0PJA11000
cid: VIDEO001
Went ahead and bought a micro sd card to try and install a stock rom. The microSD card works because I tried to flash a rom and it gave me the error that I didn't have the right version. I have no stock rom to work with, unless there is a way I can flash the TWRP backup with an sd card.
Again, I cannot
-turn my phone on (softbrick)
-enter recovery mode
-adb devices : list of devices attached empty
-put my phone s-off
-the device also is NOT rooted
I can
-enter download mode
-enter fastboot commands
-enter bootloader mode
-i have a working microsd card
When I go into download mode it's showing :
*** RELOCKED ***
htc_himaulatt PVT S-ON
LK-1.0.0.0000
RADIO-01.01_U11440801_96.01.51207G_F
OpenDSP-15.6.1.00522.8994_1026
OS-3.38.1530.2
Flashing a stock rom seems to be my only option left. Or is it? Please help me, guide me ! I have been working 20+ hours on this thing and it is driving me crazy!
Thanks a lot

Hi, try google: OS-3.38.1530.2...
Then open the last result from freelatestmovies, download the file where you find VIDEO001...
Sorry for my bad English!

Galli97 said:
Hi, try google: OS-3.38.1530.2...
Then open the last result from freelatestmovies, download the file where you find VIDEO001...
Sorry for my bad English!
Click to expand...
Click to collapse
Your English is fine! and thank you for the reply. But as I mentioned in the post, I already downloaded it, but it is a TWRP recovery file. There is no way (I believe) I can use it because I can't get into recovery mode.

max120 said:
Your English is fine! and thank you for the reply. But as I mentioned in the post, I already downloaded it, but it is a TWRP recovery file. There is no way (I believe) I can use it because I can't get into recovery mode.
Click to expand...
Click to collapse
What about this 1.32.1530.7 video001
http://androidruu.com/index.php?developer=M9

Mr Troop said:
What about this 1.32.1530.7 video001
Click to expand...
Click to collapse
I tried that one too, gave me error that it was wrong version. D:
EDIT: I guess I will give the full error code too!
19 RU_MAIN_VER_FAIL os-version in android-info missing or i
19 RU_MAIN_VER_FAIL os-version in android-info missing or i
FAIL19 RU_MAIN_VER_FAIL os-version in android-info missing or i
Again, I think I still have Android Revolution HD 20.0 Custom Rom installed on my phone.

max120 said:
I tried that one too, gave me error that it was wrong version. D:
EDIT: I guess I will give the full error code too!
19 RU_MAIN_VER_FAIL os-version in android-info missing or i
19 RU_MAIN_VER_FAIL os-version in android-info missing or i
FAIL19 RU_MAIN_VER_FAIL os-version in android-info missing or i
Again, I think I still have Android Revolution HD 20.0 Custom Rom installed on my phone.
Click to expand...
Click to collapse
Have you checked this?TWRP Backups
https://docs.google.com/spreadsheets/d/15K6xhb6wtosp9j8yu4xHBZ6n9v5OaFSW6ZVWxC4u_qc/pubhtml#

Mr Troop said:
Have you checked this?TWRP Backups
https://docs.google.com/spreadsheets/d/15K6xhb6wtosp9j8yu4xHBZ6n9v5OaFSW6ZVWxC4u_qc/pubhtml#
Click to expand...
Click to collapse
The main problem is that I cannot boot into recovery mode. My PC also doesn't recognize my phone so no way of doing adb commands. (can still boot in fastboot though)
I have the perfect matching TWRP recovery! I just don't know how to install it...

HELP! Soft bricked S-ON re-locked bootloader with no system or recovery partitions!

Hi, I am having some serious issues with my HTC One M9 and am wondering if anyone could lend a hand...
A bit of background
Originally, I set out on the task to update to the latest CyanogenMod version, but was having trouble as none of the nightly releases were installing (I was using TWRP and was constantly getting error messages). After much research, I found some instructions to unroot my phone, reinstall the stock image, and then download the OTA update. After this, it said that I would be able to install the latest CyanogenMod build. I went to the HTC ROM download support forum and downloaded the HTC One M9 version 3.35.617.12 ROM, and then proceeded to run the executable. I downloaded the Unlocked/Developer version because I live in Australia and none of options were my carrier (Telstra). This turned out to be a mistake, as after I got half way through the installation, I received the following:
Code:
error 131: customer id error
The main issue was, that the installer already went through the wiping phase, so my system was completely empty!
Where I messed up...
After my system being wiped, I read several forum posts as to why this error was occurring. I was following the instructions on one of the posts, which said to re-lock my boot loader... So, i ran:
Code:
fastboot oem lock
This turned out to be a huge mistake, as not only did it not fix the issue, but I cant even access my recovery partition.
Where I am at now
Currently, I can not access anything on my phone. I only have access to the boot loader (which is locked and is S-ON), as well as download mode. I tried to unlock the boot loader again with:
Code:
fastboot flash unlocktoken Unlock_code.bin
but after completing the steps and rebooting, the phone is still in a re-locked state. I tried to flash twrp back onto the recovery partition, or the stock ROM extracted from the RUU executable, but I would constantly get one of the two errors:
Code:
FAILED (status read failed (Unknown error))
FAILED (data transfer failure (Too many links))
So, I have a soft bricked phone that is S-ON, has a re-locked boot loader, and has no system or recovery partitions. All of the data was backed up, so I am literally open to anything to get it to a working state again.
Extra info about the phone
Code:
htc_himauhl PVT S-ON
LK-1.0.0.0000
RADIO-01.04_U11440601_71.02.50709G_F
OpenDSP-v29.2.6-00492-M8994_0702
OS-2.9.81.5
Sep 30 2015,12:34:35(573756)
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: 358509062058233
(bootloader) version-main: 2.9.841.5
(bootloader) boot-mode: RUU
(bootloader) version-baseband: 01.04_U11440601_71.02.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: TELST001
Thank you anyone who can lend a hand
- Alex

ABorrello said:
Hi, I am having some serious issues with my HTC One M9 and am wondering if anyone could lend a hand...
A bit of background
Originally, I set out on the task to update to the latest CyanogenMod version, but was having trouble as none of the nightly releases were installing (I was using TWRP and was constantly getting error messages). After much research, I found some instructions to unroot my phone, reinstall the stock image, and then download the OTA update. After this, it said that I would be able to install the latest CyanogenMod build. I went to the HTC ROM download support forum and downloaded the HTC One M9 version 3.35.617.12 ROM, and then proceeded to run the executable. I downloaded the Unlocked/Developer version because I live in Australia and none of options were my carrier (Telstra). This turned out to be a mistake, as after I got half way through the installation, I received the following: The main issue was, that the installer already went through the wiping phase, so my system was completely empty!
Where I messed up...
After my system being wiped, I read several forum posts as to why this error was occurring. I was following the instructions on one of the posts, which said to re-lock my boot loader... So, i ran: This turned out to be a huge mistake, as not only did it not fix the issue, but I cant even access my recovery partition.
Where I am at now
Currently, I can not access anything on my phone. I only have access to the boot loader (which is locked and is S-ON), as well as download mode. I tried to unlock the boot loader again with: but after completing the steps and rebooting, the phone is still in a re-locked state. I tried to flash twrp back onto the recovery partition, or the stock ROM extracted from the RUU executable, but I would constantly get one of the two errors:
So, I have a soft bricked phone that is S-ON, has a re-locked boot loader, and has no system or recovery partitions. All of the data was backed up, so I am literally open to anything to get it to a working state again.
Extra info about the phone
Thank you anyone who can lend a hand
- Alex
Click to expand...
Click to collapse
You need to request a new unlock token as the old one won't work again so go through the htcdev steps again to get your new token and see if that works, then you can install TWRP again.
Sent from my HTC 10 using XDA Labs

Tried getting a new unlock token
squ89r97 said:
You need to request a new unlock token as the old one won't work again so go through the htcdev steps again to get your new token and see if that works, then you can install TWRP again.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Ok, I just gave that a shot with out any luck. I was sent a new Unlock_code.bin, but I diff'd the two files and found they were the same. After I ran the command to flash unlocktoken, the screen popped up for me to say 'Yes' or 'No' to unlocking the bootloader. I clicked yes, but then after the restart, my phone booted back into the bootloader saying that it was still in the ***RELOCKED*** state.

Finally was able to unlock the bootloader
squ89r97 said:
You need to request a new unlock token as the old one won't work again so go through the htcdev steps again to get your new token and see if that works, then you can install TWRP again.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Finally I have managed to unlock the bootloader. For some reason, when the phone booted, the bootloader was not "official"?? The software status was modified. To fix it, from the bootloader, I rebooted into download mode; from download mode I booted back into the bootloader (now official); and then rebooted back into download mode. From there, I flashed unlocktoken with Unlock_code.bin and this time after I went through the prompts, the bootloader was unlocked and my phone booted into twrp. I tried to boot into cyanogenmod again, but it is in a boot loop (assumed because the system partition was wiped). I will now look to put stock HTC Sense, download the OTA update, and then upgrade to the newest build of cyanogenmod.

M9 in bootloop with working download mode. S-ON, trying to restore

Hey guys,
I trying to help out with a friend’s HTC M9, which suddenly wouldn’t boot into Android. We can still access the bootloader and download mode.
The bootloader shows:
Software status: Modified
Locked
S-ON
Security Warning
I got it into download mode and tried fastboot getvar all, the relevant output is:
product: htc_himauhl
version 1.0
version-main: 3.35.206.13
mid: 0PJA10000
cid: o2___102
I had a look in the readme thread. My friend wanted to try to save the files but it seems impossible since we can’t get adb to work and can’t boot a recovery image, since that would require unlocking the bootloader which wipes the data anyways. Is that correct?
So afterwards, we tried to re-flash the official RUU. The phone is the o2 version, and the most recent RUU I could find was
Code:
0PJAIMG_HIMA_UHL_M60_SENSE70_MR_O2_UK_3.35.206.13_Radio_01.01_U11440792_93.00.51117G_F_release_464855_signed.zip
I tried flashing the file using htc_fastboot flash zip, which failed with error 12 and some output on the phone complaining about the locked bootloader, as well as ARUWizard which resulted in the same error. Sorry I don’t have a screenshot, since I had to try it remotely.
Am I correct in thinking, that the file I downloaded should be usable to reflash the original software? It’s signed and has the same version code and was downloaded correctly with the same hash.
Not quite sure what happened there, since I don’t physically have the device. Should we try the SD-card method next?
Thanks!

at RUU Section just do sdcard method
here the link:
https://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
thanks to me and to them