Develop Bugs

[Q] Victim of 5.07.651.6 update - BOOT LOOP + No Access To The Recovery Mode ! HELP

Hey Guys
My Story started from 6 days ago when i wanted to change my battery , the device now is keep restarting on White screen ( HTC EVO 4G ) and hangs whenever i press the recovery mode in bootloder menu .
I Almost tried everything and only successfully unlocked the boot loader finally using --->([HowTo] Unlock Bootloader And Root 2.3.5 HBOOT 2.18 ) "http://forum.xda-developers.com/showthread.php?t=1771755 but no chance to S-OFF the device and replace the whole ROM "
i can't root and downgrade the phone because all "bootloader: 2.18.0001 " methods need either active debugging mode or recovery menu which is not accessible !
i have access only through the fastboot - Hboot USB or SdCard .
I have tried almost all version of RUUs and it failed , says " bootloder version error " or " the main version is older "
PC36IMG Downgrade to the 4.67.651.3 which is last available version from the sd card also failed says " the main version is older "
here is the Fastboot info
INFOversion: 0.5
INFOversion-bootloader: 2.18.0001
INFOversion-baseband: 2.15.00.01.15
INFOversion-cpld: None
INFOversion-microp: 041f
INFOversion-main: 5.07.651.6
INFOserialno: ******
INFOimei: *********
INFOproduct: supersonic
INFOplatform: HBOOT-8x50
INFOmodelid: PC3610000
INFOcidnum: SPCS_001
INFObattery-status: good
INFObattery-voltage: 3981mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 4b46e889
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
by the way i figure it out that i may be able to trick the htc and change the txt file called android-info.txt inside the PC36IMG for the " Main version is older " ERROR but Unfortunately i have no permission to edit or modify my stock ruu Rom "PC36IMG " that i extracted from last available RUU version for evo4g "RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio _2.1 5.00.12.19_NV_2.33_release_234563_signed" .
Any Idea Please ?
:crying::crying::crying:

You need to install a custom recovery, which can be done from the bootloader. Search for Smelkusmod recovery here and follow the instructions on how to install it. Afterwards you can install a custom ROM
Edit: Here is the link for Smelkusmod recovery
http://forum.xda-developers.com/showthread.php?t=1661543
Once installed, place whatever ROM you want on the root of your SD card. Then you can enter recovery from the bootloader screen and flash the ROM.
I also suggest reading Hipkat's guide which can be found in the link below.
http://forum.xda-developers.com/showthread.php?t=1386911
Sent from my EVO using xda premium

FinZ28 said:
Two things, either you have a bad partition or your recovery is gone. Easiest thing to do would be to load a custom recovery onto the root of your SD card and make sure the file is named PC36IMG.zip (make sure you don't have an extra .zip extension or it won't work). Make sure the phone is powered off, then hold down the power down & volume buttons until the bootloader opens up. Hopefully the recovery will load and you'll be prompted to update. Just follow the on-screen instructions. Also, make sure you don't have any other PC36IMG's on your SD card.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
many tanks for reply xx . . .the only thing i remember aside the changing the battery was that 1 day before this happen, i removed my sd card to recover some accidentally deleted picture using RecoverMyFiles software from my computer . . . i also tried loading a custom recovery and yes i certainly ensured that the file name is PC36IMG and formatted my SD card before transferring the file . . . i also tried different SD cards ex: 2gb - 4gb - 8g etc ! All those steps you just mentioned is carefully done ! and the result is that the device skip the update from the sd card says : no or wrong image !!
aside that i have upgraded my recovery to" recovery-clockwork-5.0.2.2-supersonic " and "recovery-RA-supersonic-v2.3 " and many other available recoveries through the fastboot since my bootloader is unlocked !
but the thing is nothing is loading after all those updates !!
the only thing got my attention was that when i update those custom recoveries the device would hangs after choosing recovery from the bootloader but if i use the 5.07.651.6 version original recovery the device would keep restarting !!

FinZ28 said:
You need to install a custom recovery, which can be done from the bootloader. Search for Smelkusmod recovery here and follow the instructions on how to install it. Afterwards you can install a custom ROM
Edit: Here is the link for Smelkusmod recovery
http://forum.xda-developers.com/showthread.php?t=1661543
Once installed, place whatever ROM you want on the root of your SD card. Then you can enter recovery from the bootloader screen and flash the ROM.
I also suggest reading Hipkat's guide which can be found in the link below.
http://forum.xda-developers.com/showthread.php?t=1386911
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I just tried the Smelkusmod recovery one more time again from the Sdcard and it load the PC36IMG but hangs on " Parsing...[PC36IMG.zip] "
i was able to loaded it successfully through the fastboot method and the device hangs after i press the recovery from the boot loader menu as i expected

You need to download the .img file, not the PC36IMG.zip
Once you get the .img file, do the following (connected to PC in fastboot mode)
Code:
fastboot flash recovery <recovery_name.img>
The recovery has to be in the same directory as fastboot though

CNexus said:
You need to download the .img file, not the PC36IMG.zip
Once you get the .img file, do the following (connected to PC in fastboot mode)
Code:
fastboot flash recovery <recovery_name.img>
The recovery has to be in the same directory as fastboot though
Click to expand...
Click to collapse
Yep , i've tried " recovery-clockwork-5.0.2.2-supersonic " "recovery-RA-supersonic-v2.3 ""_ra-supersonic-4.2-smelkus-mason " and many more custom recoveries too from the fastboot command ---> ( fastboot flash recovery example.img ) . . . but whatever except the stock recovery image would result to hang the device on recovery mode . . . also it will boot loop on its own stock recovery !

Same Problem!
kimiyaiy said:
Yep , i've tried " recovery-clockwork-5.0.2.2-supersonic " "recovery-RA-supersonic-v2.3 ""_ra-supersonic-4.2-smelkus-mason " and many more custom recoveries too from the fastboot command ---> ( fastboot flash recovery example.img ) . . . but whatever except the stock recovery image would result to hang the device on recovery mode . . . also it will boot loop on its own stock recovery !
Click to expand...
Click to collapse
I purchased an HTC Evo 4G from Ebay and the hardware is perfect. My problem is exact same. Found out this thing has the 5.07 update and there is no RUU to restore it and can't go backwards with S-ON!!! Can't get S-OFF without booting as this thing won't go into recovery or boot at all. I did however **Unlocked** the bootloader and that is as far as I get. I even re-locked it to try all the RUUs! I develop roms for this device so I know what I am doing! Keep getting replies to flash custom recovery which I already tried all of them and unfortunately it will just bootloop instead of recovery. Even tried 'fastboot boot (recovery name) and fastboot flash recovery (revovery name)....Need someone to get into a RUU and modify it to by-pass the firmware version check if possible! If I can get this to boot into any rom, then I can fix this!!! Come on devs, if we can port-in beats, bravia, and all other device ports, we can solve this!

You need to relock and apply the signed firmware zip from the latest OTA. If that's the software version you were running, it *should* get you booting again.

Here's that file, if you can't find it elsewhere: http://d-h.st/3yF

Nothing working...
Captain_Throwback said:
Here's that file, if you can't find it elsewhere: http://d-h.st/3yF
Click to expand...
Click to collapse
Cool! Thank you for your input. But I put this thing aside in my computer store for awhile... I will try this zip today.. I did re-lock the bootloader before I posted earlier though and already tried re-installing the latest last known RUU but same issue... In fact, I tried all RUU available!! Also, if I can only get into recovery I can fix this thing. Hope this zip helps... Question, how do I apply this zip file if I cannot get into recovery in the first place? I'm quite sure the seller of this Evo did the latest OTA update before it crashed in middle of it and got this reboot loop in the first place. Is there a way to slipstream the extracted images of this zip into the latest RUU in the appdata hidden file while it is running on windows? lol - sorry for all this but this issue is crazy!!! NOTE: Don't get the last security OTA update for this thing!!! It's a SECURITY UPDATE alright.. LOL!

rgsgroup2005 said:
Cool! Thank you for your input. But I put this thing aside in my computer store for awhile... I will try this zip today.. I did re-lock the bootloader before I posted earlier though and already tried re-installing the latest last known RUU but same issue... In fact, I tried all RUU available!! Also, if I can only get into recovery I can fix this thing. Hope this zip helps... Question, how do I apply this zip file if I cannot get into recovery in the first place? I'm quite sure the seller of this Evo did the latest OTA update before it crashed in middle of it and got this reboot loop in the first place. Is there a way to slipstream the extracted images of this zip into the latest RUU in the appdata hidden file while it is running on windows? lol - sorry for all this but this issue is crazy!!! NOTE: Don't get the last security OTA update for this thing!!! It's a SECURITY UPDATE alright.. LOL!
Click to expand...
Click to collapse
You flash the zip through HBOOT, not recovery. Rename to PC36IMG.zip (exactly), place on sd card in no folder, and choose yes to apply update once the bootloader reads it. Again, make sure you relock first, and then hopefully the device will boot. If it doesn't, it may be normalized to the point that you can unlock and flash a custom recovery and it actually stick.

Issue continues
Captain_Throwback said:
You flash the zip through HBOOT, not recovery. Rename to PC36IMG.zip (exactly), place on sd card in no folder, and choose yes to apply update once the bootloader reads it. Again, make sure you relock first, and then hopefully the device will boot. If it doesn't, it may be normalized to the point that you can unlock and flash a custom recovery and it actually stick.
Click to expand...
Click to collapse
I have not given up! This file worked to fix another Evo but not this one... It says 'wrong image'. For what ever its worth, you may be able to see my issue by looking below. Thanks!
*** UNLOCKED ***
SUPERSONIC EVT3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.12.19
Dec 21 2011, 12:50:32

rgsgroup2005 said:
I have not given up! This file worked to fix another Evo but not this one... It says 'wrong image'. For what ever its worth, you may be able to see my issue by looking below. Thanks!
*** UNLOCKED ***
SUPERSONIC EVT3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.12.19
Dec 21 2011, 12:50:32
Click to expand...
Click to collapse
Try relocking and flash the signed firmware zip.

Attempted to no avail
Captain_Throwback said:
Try relocking and flash the signed firmware zip.
Click to expand...
Click to collapse
I tried just this, relocked and renamed, after a few seconds in Hboot, it gave several lines of 'no image', then a final 'no image or wrong image', went back to normal Hboot.
More info on my problem here.

I'm kinda have similar issue... I pulled my old Evo from box it has a-off ... When I booted up it went to home screen then just shut off by it self.. then kept bootloops .. I then tried to get to recovery it boots to HTC logo and bootloops too... I tried ruu it will still bootloops .. the reason y my phone died was because battery inside phone was bulky that's y it started.. got new battery still same problem... I'm thinking maybe ramdisk got messed up.. I can go to bootloader but that is it... What can it be? I mean if there is no solution I have another Evo I never rooted and still works...and also have Evo 4g lte. My back up phones just in case if something breaks
Sent from my 831C using XDA Premium 4 mobile app

If it boot loops after you tried a RUU, then you have bigger problems and probably need to swap to one of your backup phones.
Sent from my HTC device

Waiving the flag...
Magnum_Enforcer said:
If it boot loops after you tried a RUU, then you have bigger problems and probably need to swap to one of your backup phones.
Sent from my HTC device
Click to expand...
Click to collapse
Screw it... I'm going to order a new motherboard on Ebay with clean ESN for 42.00 lol. I give up!

HTC One X International Mounting SD Card and Flashing Issue's

Hello Everyone, pretty new to this community.
I have been fixing and flashing stuffs for pretty long time and found XDA brings out alot of help for me reading comments and guides.
I'm having problems with mounting the SD-Card, i remember i had in the past CWM recovery that i could actually mount successfully without having any drivers issues (Windows 7 Home Premium) when trying to Mount the SD-Card.
Now even the latest CWM or TWRP recoveries, i can't mount the SD-Card.
Why i want Mount it via Recovery?
Because i deleted the OS and i'm trying to put on my SD-Card a Stock Nanroid Backup for it since there is no RUU.exe out there for the HTC One X International with CID : T-MOB101 that i can flash via fastboot.
What i tried to do is, from fastboot flashing a random ROM that hopefully i will be able to mount SD-Card on that ROM.
I tried this :
fastboot flash boot boot.img (that i took out from that ROM.zip)
fastboot oem rebootRUU
fastboot flash zip ROM.zip
Don't really know if its possible doing it that way, but i gave it a try that i head in my head.
I know i'm supposed to do it via Recovery Mode, but i can't even insert files there since the HTC One X has a build memory which makes lifes harder.
That's my phone details :
Code:
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.72.0000
CPLD-None
MICROP-None
RADIO-5.1204.163U2.31
eMMC-bootmode: disabled
CPU-bootmode : disabled
HW Secure boot : enabled
MODEM PATCH : OFF
Jun 21 2014,18:24:41
CID : T-MOB101
Its a Germany Phone version if you wondering.
So i'm wondering if there is a way that i could push the files of the Nanroid backup to my phone?(Reminding again, i have no Software running. can't mount SD-Card via Recovery Mode, and SD-Card is clean.)
Or if anyone here somehow have a good old recovery CWM version that can mount the SD-Card that i could give it a shot.
I can replace the USB port though, but it won't help.
Thanks in advance.

Reich.G said:
Hello Everyone, pretty new to this community.
I have been fixing and flashing stuffs for pretty long time and found XDA brings out alot of help for me reading comments and guides.
I'm having problems with mounting the SD-Card, i remember i had in the past CWM recovery that i could actually mount successfully without having any drivers issues (Windows 7 Home Premium) when trying to Mount the SD-Card.
Now even the latest CWM or TWRP recoveries, i can't mount the SD-Card.
Why i want Mount it via Recovery?
Because i deleted the OS and i'm trying to put on my SD-Card a Stock Nanroid Backup for it since there is no RUU.exe out there for the HTC One X International with CID : T-MOB101 that i can flash via fastboot.
What i tried to do is, from fastboot flashing a random ROM that hopefully i will be able to mount SD-Card on that ROM.
I tried this :
fastboot flash boot boot.img (that i took out from that ROM.zip)
fastboot oem rebootRUU
fastboot flash zip ROM.zip
Don't really know if its possible doing it that way, but i gave it a try that i head in my head.
I know i'm supposed to do it via Recovery Mode, but i can't even insert files there since the HTC One X has a build memory which makes lifes harder.
That's my phone details :
Code:
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.72.0000
CPLD-None
MICROP-None
RADIO-5.1204.163U2.31
eMMC-bootmode: disabled
CPU-bootmode : disabled
HW Secure boot : enabled
MODEM PATCH : OFF
Jun 21 2014,18:24:41
CID : T-MOB101
Its a Germany Phone version if you wondering.
So i'm wondering if there is a way that i could push the files of the Nanroid backup to my phone?(Reminding again, i have no Software running. can't mount SD-Card via Recovery Mode, and SD-Card is clean.)
Or if anyone here somehow have a good old recovery CWM version that can mount the SD-Card that i could give it a shot.
I can replace the USB port though, but it won't help.
Thanks in advance.
Click to expand...
Click to collapse
Flash Philz recovery 5.15.9 and the sd card mounting will work but must to be 5.15.9 have many my links in the thread with this recovery seared in google drive

Thant said:
Flash Philz recovery 5.15.9 and the sd card mounting will work but must to be 5.15.9 have many my links in the thread with this recovery seared in google drive
Click to expand...
Click to collapse
After a bit pain with drivers error when mounting SD-Card with Philz recovery, that actually successfully Mounted my SD-Card
Thanks a tons for that. +1 for you.
Now i'm moving to the second step of this topic, the flashing errors.
I will post some photos here to be more clear about my steps.
I went to This Website and got my Stock Nanroid Backup to T-MOB101 cid number for CWM and TWRP just in case :
M7 CWM Nandroid Backup CID T-MOB101 1.28.111.6 2013-03-29
M7 TWRP Nandroid Backup CID T-MOB101 2.24.111.3
After i got them, i checked MD5 of course, and putted them inside the SD-Card where the backups should be.
Then i flashed CWM recovery and tried to restore the CWM Stock Nanroid Backup with an "error Flashing Boot Image" :
So i tried to do the same proccess with TWRP Recovery with an error "Unable to extract tar archive" :
Then i also tried doing it with Philz recovery, and same error as CWM :
So i saw that i got no more hope, then i tried to use an old Nanroid Backup that i have made to my phone before, so i putted inside the phone, and when i tried to restore my Nanroid backup, it actually did work, BUT, after it says "Restore Completed" :
I went to reboot my phone that hopefully i will see the phone loading up, but i guess not, bring me back to fastboot screen :
It wasn't even making a sign of loading software, when i boot my phone up, it automatically brings me to Fastboot mode.
Same with Philz Recovery :
And same story with TWRP recovery.
I was thinking its related to the boot.img that i get that error because of that file, so i also tried to replace that boot.img with the Old Nandroid Backup that it actually allow the restore process begin with it with the Stock Nandroid Backup, but same error.
Kinda feeling lost, hopefully someone can help me out with this please.

Reich.G said:
After a bit pain with drivers error when mounting SD-Card with Philz recovery, that actually successfully Mounted my SD-Card
Thanks a tons for that. +1 for you.
Now i'm moving to the second step of this topic, the flashing errors.
I will post some photos here to be more clear about my steps.
I went to This Website and got my Stock Nanroid Backup to T-MOB101 cid number for CWM and TWRP just in case :
M7 CWM Nandroid Backup CID T-MOB101 1.28.111.6 2013-03-29
M7 TWRP Nandroid Backup CID T-MOB101 2.24.111.3
After i got them, i checked MD5 of course, and putted them inside the SD-Card where the backups should be.
Then i flashed CWM recovery and tried to restore the CWM Stock Nanroid Backup with an "error Flashing Boot Image" :
So i tried to do the same proccess with TWRP Recovery with an error "Unable to extract tar archive" :
Then i also tried doing it with Philz recovery, and same error as CWM :
So i saw that i got no more hope, then i tried to use an old Nanroid Backup that i have made to my phone before, so i putted inside the phone, and when i tried to restore my Nanroid backup, it actually did work, BUT, after it says "Restore Completed" :
I went to reboot my phone that hopefully i will see the phone loading up, but i guess not, bring me back to fastboot screen :
It wasn't even making a sign of loading software, when i boot my phone up, it automatically brings me to Fastboot mode.
Same with Philz Recovery :
And same story with TWRP recovery.
I was thinking its related to the boot.img that i get that error because of that file, so i also tried to replace that boot.img with the Old Nandroid Backup that it actually allow the restore process begin with it with the Stock Nandroid Backup, but same error.
Kinda feeling lost, hopefully someone can help me out with this please.
Click to expand...
Click to collapse
I think you try to restore wrong nandroid
M7 CWM Nandroid Backup CID T-MOB101 1.28.111.6 2013-03-29
M7 TWRP Nandroid Backup CID T-MOB101 2.24.111.3
look at the red M7 I think you try to restore nandroid for HTC ONE M7 not for HTC ONE X

Thant said:
I think you try to restore wrong nandroid
M7 CWM Nandroid Backup CID T-MOB101 1.28.111.6 2013-03-29
M7 TWRP Nandroid Backup CID T-MOB101 2.24.111.3
look at the red M7 I think you try to restore nandroid for HTC ONE M7 not for HTC ONE X
Click to expand...
Click to collapse
Oh...Shame on me not paying attention to that thing.
Thanks for opening my eye's! +1
So after digging more in forums, i found out that link Nandroid Backups.
So i have tried all the RUU's and Nandroid for my Cid Number, and all of them worked except the RUU's.exe and with flashing the Nandroid Backups, my phone got into bootloops.
But there were 2 kind of Nandroid backups that actually worked which are :
1. T-Mobile DE 3.14.111.28 [CWM]
MD5: af82f0cfb8aa61b670c59e0308a55582
2. T-Mobile DE 3.14.111.27 [TWRP]
MD5: f6a67adb8ad51ca9f55760be31ed5e49
All seems good, BUT(always BUT unfortunately ) the touch screen not function at all when it loads up.
That's the reason i tried both of them, to flash with TWRP and then with CWM.
Seems like i'm able to flash correctly only the version : 3.14.111.2- , no clue why others didn't work properly.
Something i might suspect of, that it skips one of the files when flashing Nandroid backup as you can see below :
"Volume not found! Skipping restore of /sd-ext."
I also tried to get a Nandroid backup from Here and it doesn't work also.
So if i got to that point where my phone actually bootup and load the software with these :
HTML:
1. T-Mobile DE 3.14.111.28 [CWM]
MD5: af82f0cfb8aa61b670c59e0308a55582
2. T-Mobile DE 3.14.111.27 [TWRP]
MD5: f6a67adb8ad51ca9f55760be31ed5e49
The question is, how will i be able to fix the touch screen issue's?
If i will be able to fix that issue, i will run all updates until i get to the latest version of HTC One X of my Cid Number.
I think that's the last step for me for this topic, just to solve the touch problem that not function at all.
Thank alot for the help.

Reich.G said:
Oh...Shame on me not paying attention to that thing.
Thanks for opening my eye's! +1
So after digging more in forums, i found out that link Nandroid Backups.
So i have tried all the RUU's and Nandroid for my Cid Number, and all of them worked except the RUU's.exe and with flashing the Nandroid Backups, my phone got into bootloops.
But there were 2 kind of Nandroid backups that actually worked which are :
1. T-Mobile DE 3.14.111.28 [CWM]
MD5: af82f0cfb8aa61b670c59e0308a55582
2. T-Mobile DE 3.14.111.27 [TWRP]
MD5: f6a67adb8ad51ca9f55760be31ed5e49
All seems good, BUT(always BUT unfortunately ) the touch screen not function at all when it loads up.
That's the reason i tried both of them, to flash with TWRP and then with CWM.
Seems like i'm able to flash correctly only the version : 3.14.111.2- , no clue why others didn't work properly.
Something i might suspect of, that it skips one of the files when flashing Nandroid backup as you can see below :]
"Volume not found! Skipping restore of /sd-ext."
I also tried to get a Nandroid backup from Here and it doesn't work also.
So if i got to that point where my phone actually bootup and load the software with these :
HTML:
1. T-Mobile DE 3.14.111.28 [CWM]
MD5: af82f0cfb8aa61b670c59e0308a55582
2. T-Mobile DE 3.14.111.27 [TWRP]
MD5: f6a67adb8ad51ca9f55760be31ed5e49
The question is, how will i be able to fix the touch screen issue's?
If i will be able to fix that issue, i will run all updates until i get to the latest version of HTC One X of my Cid Number.
I think that's the last step for me for this topic, just to solve the touch problem that not function at all.
Thank alot for the help.
Click to expand...
Click to collapse
You are with too high HBOOT 1.72 and the tuch never will work on 3.14 base only after 3.20 base will work. The tuch work in Philz recovery but not work in your nand backup 3.14.11.x because your HBOOT is too high.Search newer nand backup for your base or install custom rom. You can see your main version with the command fastboot getvar version-main and search for nandroid with this numbers where you see after runing the command

Thant said:
You are with too high HBOOT 1.72 and the tuch never will work on 3.14 base only after 3.20 base will work. The tuch work in Philz recovery but not work in your nand backup 3.14.11.x because your HBOOT is too high.Search newer nand backup for your base or install custom rom. You can see your main version with the command fastboot getvar version-main and search for nandroid with this numbers where you see after runing the command
Click to expand...
Click to collapse
Running "fastboot getvar version-main" command results :
Code:
version-main: 4.17.111.4
finished. total time: 0.017s
After googling in 10 Pages, with search key word :
"HTC One X T-MOB101 Nandroid Backup"
I couldn't find anything higher than 3.20 except the one that i mention before that his version is :
Code:
T-Mobile DE 4.17.111.3 [TWRP]
MD5: 89c261ef42833e7515fdcec6d81a0b15
But when i flash it with TWRP recovery, it will stay stuck on HTC Screen, which brings the questions, why does TWRP Nandroid Backups doesn't have boot.img like CWM Nandroid Backups that has boot.img that i can simply take it out and go into fastboot and flash as :
fastboot flash boot boot.img , in case the phone is stuck on HTC screen.
Here is a topic i was reading and the comments that this guy seem to pretty much handle the same issue as i do atm :
Another thing that got me thinking after you told me that touch doesn't work because HBOOT doesn't match to these old versions is,
Downgrading the HBOOT, but as much as i know, you can't really downgrade your HBOOT unless you have S-OFF, which is impossible on the HTC One X International since the mmcblk file in the system, is a huge file that build in that hold the Cid Number and i can't really pull it out of the phone and modify it with Hex Editor and then put it back for changing my Cid in order to reach S-OFF.
So to downgrade my HBOOT i assume it won't work since i can't get S-OFF.
I kind of want to get back to the Stock ROM after checking some ROM's for that phone, i got the idea of it and figure out that the original is much faster and better to work comparing to the ROM's.
Can you recommend about any ROM that you had experience with, with that HTC One X ? I'm kind of curious more, since so far, i seem not to be successful bringing back my HTC One X International to Stock ROM.
So what else could come up in your mind?

Reich.G said:
Running "fastboot getvar version-main" command results :
Code:
version-main: 4.17.111.4
finished. total time: 0.017s
After googling in 10 Pages, with search key word :
"HTC One X T-MOB101 Nandroid Backup"
I couldn't find anything higher than 3.20 except the one that i mention before that his version is :
Code:
T-Mobile DE 4.17.111.3 [TWRP]
MD5: 89c261ef42833e7515fdcec6d81a0b15
But when i flash it with TWRP recovery, it will stay stuck on HTC Screen, which brings the questions, why does TWRP Nandroid Backups doesn't have boot.img like CWM Nandroid Backups that has boot.img that i can simply take it out and go into fastboot and flash as :
fastboot flash boot boot.img , in case the phone is stuck on HTC screen.
Here is a topic i was reading and the comments that this guy seem to pretty much handle the same issue as i do atm :
Another thing that got me thinking after you told me that touch doesn't work because HBOOT doesn't match to these old versions is,
Downgrading the HBOOT, but as much as i know, you can't really downgrade your HBOOT unless you have S-OFF, which is impossible on the HTC One X International since the mmcblk file in the system, is a huge file that build in that hold the Cid Number and i can't really pull it out of the phone and modify it with Hex Editor and then put it back for changing my Cid in order to reach S-OFF.
So to downgrade my HBOOT i assume it won't work since i can't get S-OFF.
I kind of want to get back to the Stock ROM after checking some ROM's for that phone, i got the idea of it and figure out that the original is much faster and better to work comparing to the ROM's.
Can you recommend about any ROM that you had experience with, with that HTC One X ? I'm kind of curious more, since so far, i seem not to be successful bringing back my HTC One X International to Stock ROM.
So what else could come up in your mind?
Click to expand...
Click to collapse
When you flash twrp run the command fastboot erase cache and try to go in twrp

Thant said:
When you flash twrp run the command fastboot erase cache and try to go in twrp
Click to expand...
Click to collapse
I was doing it via recovery before and same thing.
Also tried run the erase cache command via fastboot before flashing.
My steps :
1. fastboot erase cache
2. fastboot flash recovery twrp.img
3. fastboot erase cache
4. login into recovery and try to restore.
Results :
Stuck on white HTC Screen
What can i do else?

Reich.G said:
I was doing it via recovery before and same thing.
Also tried run the erase cache command via fastboot before flashing.
My steps :
1. fastboot erase cache
2. fastboot flash recovery twrp.img
3. fastboot erase cache
4. login into recovery and try to restore.
Results :
Stuck on white HTC Screen
What can i do else?
Click to expand...
Click to collapse
install custom rom

[Q] verizon one m8 stuck in bootload

i made a mistake transforming my one m8 to GPE with a gsm guide and my phone is verizon with gsm system too, now my device is stuck into bootloader only can flash twrp but cant intall any rom, i get error FAILED )remote not allowed) from fastboot get error can run update in zip file, Im really sad cant do anything, please somebody help me.
Reards

xrodx said:
i made a mistake transforming my one m8 to GPE with a gsm guide and my phone is verizon with gsm system too, now my device is stuck into bootloader only can flash twrp but cant intall any rom, i get error FAILED )remote not allowed) from fastboot get error can run update in zip file, Im really sad cant do anything, please somebody help me.
Reards
Click to expand...
Click to collapse
Did you use the sdcard 0P6BIMG.zip ruu method to fully convert.
Pull out your external sdcard and put it in another device so you can remove/relocate the "0P6BIMG.zip" file from sdcard.
Now boot to hboot and choose fastboot, now plug your phone in and it should state "fastboot usb" (run your commands again)

jball said:
Did you use the sdcard 0P6BIMG.zip ruu method to fully convert.
Pull out your external sdcard and put it in another device so you can remove/relocate the "0P6BIMG.zip" file from sdcard.
Now boot to hboot and choose fastboot, now plug your phone in and it should state "fastboot usb" (run your commands again)
Click to expand...
Click to collapse
Yes i download the file from here:
http://www.droidviews.com/restore-verizon-htc-one-m8-to-stock-rom-with-ruu/
When i fla**** get this via fat32 sd card
Download Factory nandroid backup, when i restore the device restore data and boot ok but restore system fail
I have a problem with the system partition, anyone know how can i fix this?
Please help

@xrodx
Did you format the sdcard using your computer?
When I formated mine I used my HTC one m8 and it formated it "vfat" so I want to recommend trying vfat

My phone its ok
I do this:
Flash firmware, boot and recovery 4.4.4 from here:
http://forum.xda-developers.com/showthread.php?t=2723159
Flash TWRP for verizon found here:
http://forum.xda-developers.com/ver...ent/ruu-m8vzw-4-4-4-s-off-onlynewest-t2914914
I flashed this ROM via TWRP, do a fulll wipe first:
http://forum.xda-developers.com/showthread.php?t=2716306
Works fine now, thanks guys for your help :good::good::laugh::laugh::laugh:

[Q] Help With Unrooting HTC One M8

Hey everyone, here's the situation that I am in right now:
I rooted my phone and flashed an Insert Coin ROM but wanted to return it back to complete stock form.
I have a HTC One M8 thats currently locked to T-Mobile. The CID is T-MOB010 and the Build Number is 2.22.401.4
There is TWRP installed on this phone, version 2.8.1.0.
The problem that I am having is this: when I boot into TWRP recovery mode, I go to restore and look for the stock ROM, but it does not show up in the menu. I looked in both internal storage and SD Card storage, but it does not show up in either. I also tried moving the files manually through TWRP, but no luck.
I looked through the phones files using the File Manager App and I see the files are there, but once again I cannot see them when I use TWRP recovery mode.
Does anyone know why this is happening?

http://forum.xda-developers.com/showthread.php?t=2701376
read that all...hint 1 : your OFFICIAL build number is NOT 2.22.401 !

Not sure I follow. I checked the build number on my phone to confirm.

MW2 said:
Not sure I follow. I checked the build number on my phone to confirm.
Click to expand...
Click to collapse
That's the ROM base (software build). What you need to know is your firmware version. Boot into your bootloader (turn off phone, then hold power + vol down). What it says under OS is your firmware version.
You can also hook up to your PC/ADB in fastboot, and issue the command fastboot getvar all. What it says under version-main is your firmware.

xunholyx said:
That's the ROM base (software build). What you need to know is your firmware version. Boot into your bootloader (turn off phone, then hold power + vol down). What it says under OS is your firmware version.
You can also hook up to your PC/ADB in fastboot, and issue the command fastboot getvar all. What it says under version-main is your firmware.
Click to expand...
Click to collapse
I have done that and the OS version is not stated.

MW2 said:
I have done that and the OS version is not stated.
Click to expand...
Click to collapse
That is caused by your recovery being out of date. It`is also reported to be caused with TWRP 2.8.1.0. Update to TWRP 2.8.0.3. There is another newer version, but 0.3 seems to be the most stable.

Updated TWRP, still no OS version listed.

In order to explain fully I need to show the process I tried using.
I followed the instructions from this site: http://theunlockr.com/2014/06/08/how-to-unroot-the-htc-one-m8-video/
I boot my phone into recovery mode and select the Restore option in TWRP. I try to find the Nandroid backup that I transferred to my phone but it does not show up. I try looking through both the internal storage and SD card but nothing shows up there either.

MW2 said:
Updated TWRP, still no OS version listed.
Click to expand...
Click to collapse
[Recovery] [RUU 2.22.531.6] [TWRP Nandroid Backups] [Radio IMGs][ OTA 3.32.531.2
Just do an RUU and get back to stock, seeing as you are T-Mobile US yes? T-MOB010 is T-Mobile US...
There you'll get RUU, recoveries, radios, nand backups and OTA's (Which contains firmware already).
I don't get what the problem is?

The problem is when I boot into TWRP Recovery and go to the Restore option, the files are not showing. I checked both internal and SD Card storage but it does not show either. I am using TWRP 2.8.0.3

MW2 said:
The problem is when I boot into TWRP Recovery and go to the Restore option, the files are not showing. I checked both internal and SD Card storage but it does not show either. I am using TWRP 2.8.0.3
Click to expand...
Click to collapse
Try making a backup of just the boot to either internal/sdcard, so that TWRP can create the directory for you. Maybe you didn't unpack it into the right directory.
Make sure you have your devices "serial number" folder and not the one from the person that backed it up(If you're using a downloaded nand). When it's unpacked you have to place just the backup folder into the directory, if they kept it "default" it'll start with the date--time--release for example: 2014-12-06--05-20-22-KTU84P release-keys The highlighted area can ofcourse change depending on the version it has backed up, as will date and time(Logically). Inside that folder you'll have plenty of files like boot.emmc.win, system.ext4.win000 (etc) data.ext4.win etc etc. You need to place that folder inside the TWRP Backups folder.
Like I said, make backup of boot so that TWRP can create the directory for you, then it'll end up something like:
/storage/ext_sd/TWRP/BACKUPS/yourserialnumberfolder/2014-12-06--05-20-22-KTU84Prelease-keys/

Thanks for the advice.
I managed to fix the issue using RUU. I don't know why TWRP was acting this way, but my I'm ok now.
Thank you everyone for the help
Here is the method I used just for future references: http://www.android.gs/downgrade-t-mobile-htc-one-m8-to-official-stock-firmware-with-ruu/

Android 6.0 1/2 Update problem

Hello XDA, hello M9 users!
So, i rooted my phone back in September just to use some simple apps like Greenify, AdAway, etc. Yesterday the official Android 6.0 update arrived and I wanted to update. So I flashed the stock recovery and relocked my bootloader aaaand that was it. Everything was going ok untill the phone got in to the recovery. When it started to update the loading bar filled like 1/4. After that the red sign appeared on my screen. After that i just hard reseted my phone and everything was working ok and tried again but the same problem persisted. I started looking here on forums but i didn't find exact answeres except one. The guy sad: "The problem was solved. It took me 6 hours to manage this. All you need to do is re flash the stock backup with TWRP. ". Sadly I don't have the stock backup from my phone. And I'm thinking to reinstall TWRP recovery and flash version 1.32.401.8* from the thread called "HTC ONE M9 Stock File Collection (RUUs, Backups, etc.) - with linked Instructions" because I think that's the most stock version of this phone. So i have this question: should I do this or not? I am kinda noob, I am definetly not a pro with these things. I only know the basics and I am kindly asking for help. I will attach photos with phone info and everything that I mentioned here in the text. (sorry for my english, I'm trying my best)
If you guys find any solution I will be pleased to hear them!
Phone status:
-Rooted
-Bootloader: Relocked
-S ON
-Stock recovery (recovery version 2.10.401.1)
-SD Card capacity: 8GB only (i don't know if this helps)
-Stock 5.1 HTC Sense 7.0 (Software nr. 2.10.401.1)
-CID number: HTC__102
Thank you in advance!

Remember any changes with system such as root will cause OTA not work well.All you need to do is flash a RUU with right version.Or you can restore from TWRP with stock backup and flash stock recovery then you can get OTA.

If you want to install that update you either need the 2.10.401.1 backup or the corresponding RUU. As soon as you flash anything via TWRP your system gets mount as read/write. OTAs check the status of your system and fail if it's modified (=uninstalled system apps, root, etc.) and/or not mounted as read-only. Unrooting is not enough. You need to reflash an untouched system image (either via RUU or TWRP). Instructions can be found in my google sheet which is linked in post #5 of the thread where you found the 1.32.401.8 backup or in my signature.
Edit: Looks like I didn't type my answer fast enough.

Flippy498 said:
If you want to install that update you either need the 2.10.401.1 backup or the corresponding RUU. As soon as you flash anything via TWRP your system gets mount as read/write. OTAs check the status of your system and fail if it's modified (=uninstalled system apps, root, etc.) and/or not mounted as read-only. Unrooting is not enough. You need to reflash an untouched system image (either via RUU or TWRP). Instructions can be found in my google sheet which is linked in post #5 of the thread where you found the 1.32.401.8 backup or in my signature.
Edit: Looks like I didn't type my answer fast enough.
Click to expand...
Click to collapse
So the only thing i need to do is download "2.10.401.1.zip" RUU from your google sheet, copy it to my SD Card and enter in download mode and just wait untill it's done? Is this working with S-On?

It needs to be renamed correctly and the SD card needs to be formatted to fat32 (as stated in the instructions above the download links ). With S-ON you can use RUUs that have the same or a higher version than your phone. You only need S-OFF if you want to flash RUUs with a lower version (=downgrade) or one with a different SKU (the three numbers behind the second dot of the firmware version) than the one your phone got shipped with.

Flippy498 said:
It needs to be renamed correctly and the SD card needs to be formatted to fat32 (as stated in the instructions above the download links ). With S-ON you can use RUUs that have the same or a higher version than your phone. You only need S-OFF if you want to flash RUUs with a lower version (=downgrade) or one with a different SKU (the three numbers behind the second dot of the firmware version) than the one your phone got shipped with.
Click to expand...
Click to collapse
I am S-On and i don't want to S-Off. I don't want a lower version of RUU and i just want to simply upgrade to Android 6.0. So am I doing the right thing?

strikercs said:
I am S-On and i don't want to S-Off. I don't want a lower version of RUU and i just want to simply upgrade to Android 6.0. So am I doing the right thing?
Click to expand...
Click to collapse
Flippy498 said:
With S-ON you can use RUUs that have the same or a higher version than your phone.
Click to expand...
Click to collapse
Your version is 2.10.401.1 and the RUU has version 2.10.401.1, too.
Re-read my last post. I never said that you should S-OFF. You wanted to know whether you can use a RUU with S-ON and I explained why S-OFF is not needed in your situation.

Flippy498 said:
Your version is 2.10.401.1 and the RUU has version 2.10.401.1, too.
Re-read my last post. I never said that you should S-OFF. You wanted to know whether you can use a RUU with S-ON and I explained why S-OFF is not needed in your situation.
Click to expand...
Click to collapse
I have downloaded and copied the file on my SD Card using an SD Card reader because it wouldn't let me copy it using USB. The SD Card is FAT32 and i renamed the file to "0PJAIMG.zip". When i boot into the download mode it just enters download mode. It doesn't ask me if i want to flash the file. Any ideas what could be wrong?

Flippy498 said:
Your version is 2.10.401.1 and the RUU has version 2.10.401.1, too.
Re-read my last post. I never said that you should S-OFF. You wanted to know whether you can use a RUU with S-ON and I explained why S-OFF is not needed in your situation.
Click to expand...
Click to collapse
I have downloaded and copied the file on my SD Card using an SD Card reader because it wouldn't let me copy it using USB. The SD Card is FAT32 and i renamed the file to "0PJAIMG.zip". When i boot into the download mode it just enters download mode. It doesn't ask me if i want to flash the file. Any ideas what could be wrong? I attached a screesnshot.

Are you sure you didn't rename it to "0PJAIMG.zip.zip". Looking at the "nmdsdcid" file I assume that file extensions aren't visible on your pc which could be the reason for your mistake.

Flippy498 said:
Are you sure you didn't rename it to "0PJAIMG.zip.zip". Looking at the "nmdsdcid" file I assume that file extensions aren't visible on your pc which could be the reason for your mistake.
Click to expand...
Click to collapse
I told you that I'm a noob. That's exactly what happened..

strikercs said:
I told you that I'm a noob. That's exactly what happened..
Click to expand...
Click to collapse
Thank you @Flippy498! Succesfully updated to Android 6.0!

So @Flippy498 saved my day with #3.
After getting to his really nice collection which can be found here and here I downloaded a TWRP Backup for my CID.
Remember fastboot getvar cid ?
Then I followed his nice tutorial until Step 5, but skipped 1 - 3.
Flippy498 said:
01. Format your SD card with a PC to exfat and put it back into your phone.
02. Boot to TWRP.
03. Create a backup on your external SD card. (Backing up "Boot" is more than enough. We only want TWRP to create the needed directories on your SD card.)
04. Download the correct backup for your firmware version. (It is stated in the line with "OS" at the beginning when you boot to download mode. The "firmware version" in "settings>about>software information>more" is only the base of the rom you are running.)
05. Unzip the downloaded backup.
06. Copy the unzipped backup folder to "TWRP/BACKUPS/<YourSerialnumber>/"on your SD card. Sometimes this is only possible if the SD card is directly connected to your PC and not put into your phone. I don't know why some M9s refuse the copy process.
Click to expand...
Click to collapse
So here was my problem, I have no external sd-card in my phone and trying to copy the 4.2 GB File via "Android Transfer" brought up the error, that files largen then 4GB are not supported to copy.
So I first made sure I prepared the following steps:
Flippy498 said:
07. I recommend wiping everything except "Micro SDcard", "USB-OTG" and "SD-Ext".
08. Check the "Mount system as read-only" box in the Mount menu.
Click to expand...
Click to collapse
Now make a folder structure like in Step 6 (if you are still in TWRP, no problem use the "mkdir <foldername>" command via the advanced tools tab. (read on, I tell you where it is)
So then, instead I copied the 2GB zip file in that folder and went to advanced tools in TWRP. There I chose the "execute command" tool, went inside the folder with the serialnumber and clicked select.
Now a command line appears and I entered "unzip" and the name of the zipfile ... well that took some time ... dont tend to klick kill ... you can make 3 coffees in that time (I advise you to drink only two :silly: otherwise you get overexcited)
After that another folder with the name of the zipfile shows up. Go back and click restore - then check that folder and three X Marks will appear, showing you that these mounts will be overwritten.
Now swipe to restore and go on:
Flippy498 said:
09. Restore the backup.
10. Boot to system (ignore the warning that no OS is installed). This process may actually take a while!
11. Congrats! Your system is now stock and able to receive and install official OTAs, again.
Click to expand...
Click to collapse
and thats's it. Worked like a charm. Thanks again @Flippy498 :highfive: !!