Develop Bugs

Problem after installation of custom ROM on HTC one X

Hi,
This is my first post (and sorry for my bad english)
I got a problem with my HTC one X, yesterday, I try to install the custom ROM ViperX 2.6.0 and after the installation, the ROM works but I am blocked on pin code because the touch doesn't work and the 3 buttons at the bottom to. The only buttons who work are power, vol up and down.
So, since yesterday, my HOX is bricked because I didn't make back up and I don't find good version of RUU and I can't send files on the SDcard.
How can I unbrick my phone (with the custom ROM or reset my HOX with RUU)?
My HOX's caracteristics:
cid : HTC__203
version : 3.18.401.1
HBOOT-1.39.0000
Thanks to help me. And sorry for my English ^^'

Benlado said:
Hi,
This is my first post (and sorry for my bad english)
I got a problem with my HTC one X, yesterday, I try to install the custom ROM ViperX 2.6.0 and after the installation, the ROM works but I am blocked on pin code because the touch doesn't work and the 3 buttons at the bottom to. The only buttons who work are power, vol up and down.
So, since yesterday, my HOX is bricked because I didn't make back up and I don't find good version of RUU and I can't send files on the SDcard.
How can I unbrick my phone (with the custom ROM or reset my HOX with RUU)?
My HOX's caracteristics:
cid : HTC__203
version : 3.18.401.1
HBOOT-1.39.0000
Thanks to help me. And sorry for my English ^^'
Click to expand...
Click to collapse
it is not bricked. did you flash the boot img from the rom zip? and if you did, did you fastboot erase cache after flashing the boot.img ? and did you do a full wipe, including cache and dalvik before flashing the rom

Also shouldn't you be flashing viper x 3.7.4 ?
http://forum.xda-developers.com/showthread.php?p=36407082
Oh and use mount usb storage on your custom recovery to copy the Rom to sd
Sent from my HTC One X

from ryakfar
nogotaclue said:
it is not bricked. did you flash the boot img from the rom zip? and if you did, did you fastboot erase cache after flashing the boot.img ? and did you do a full wipe, including cache and dalvik before flashing the rom
Click to expand...
Click to collapse
Yes, it is the boot.img from the rom zip and I did all the step you said.

this ersiledo
herbie13 said:
Also shouldn't you be flashing viper x 3.7.4 ?
http://forum.xda-developers.com/showthread.php?p=36407082
Oh and use mount usb storage on your custom recovery to copy the Rom to sd
Sent from my HTC One X
Click to expand...
Click to collapse
Thanks for your reply, you must be right, but I don't know how mount usb storage works.

When I select "mount USB storage" on recovery, it doesn't work and there is "E : unable to open ums lunfile (No such file or directory)"

Flash a newer recovery. Yours is outdated.
http://db.tt/t6RTcTwK
Then install the viper 3.7.4 just like you did with the 2.6. It booted so you did the correct steps.

Benlado said:
When I select "mount USB storage" on recovery, it doesn't work and there is "E : unable to open ums lunfile (No such file or directory)"
Click to expand...
Click to collapse
were you on stock ics or jellybean. that fault used to occur on stock ics when using cwm. you could flash twrp recovery or newer cwm and see if you still get the fault
beaten by @Mr Hofs

I flashed a newer cwm, flash viper x 2.7.4 and it works.
So my problem was a older version of the custom rom and I needed a newer version of recovery to mount sd card and flash with other custom rom.
We can close this topic =)
Thanks to all.

HTC One X Semi Bricked NEED HELP.

Hello,
Well, I was trying to install some new kernels but somehow my phone went into Boot Loop.
After that, I accidentally formatted my system and system memory. End Result: Their is nothing in my SD Card Right now.
I have searched in this forum and others for 2 days and still can not find a proper solution. Now, my laptop and computer does not recognize my device through adb device. I tried to insall stock rom through RUU but it gave an Boot Loader Version Error. However, I managed to install philz recovery and tried to mount memory but still no luck, I can not push files through adb as it can not recognize my device.
My CID is 02_001. I downloaded the matched CID RUU (RUU_ENDEAVOR_U_ICS_40_O2_UK_1.26.206.2_Radio_1.1204.90.13_release_251230_signed) but it didnt work. My image number of the phone (I dont know what is this actually) is like 4.xxxx and the image number of the RUU is 1.xxxx.
The HBOOT version is 1.72 S ON.
Can someone by someway, please give me the link of UPDATED RUU so that I can flash to stock rom or just help me to find a way to transfer custom rom to my phone memory so that I can flash a custom rom.
I was using VIPERX ROM 4.1.1,as the phone was draining alot of battery so over efficiently I tried to FLASH BRICKED KERNEL.
NOW I AM STUCK, HELPLESS and after losing the battle I am posting this thread.
PLEASE HELP ME WITH A SUITABLE ANSWER.
I would prefer to install stock rom but it wont work I guess because of the updated HBOOT version.

WaleedUQ said:
Hello,
Well, I was trying to install some new kernels but somehow my phone went into Boot Loop.
After that, I accidentally formatted my system and system memory. End Result: Their is nothing in my SD Card Right now.
I have searched in this forum and others for 2 days and still can not find a proper solution. Now, my laptop and computer does not recognize my device through adb device. I tried to insall stock rom through RUU but it gave an Boot Loader Version Error. However, I managed to install philz recovery and tried to mount memory but still no luck, I can not push files through adb as it can not recognize my device.
My CID is 02_001. I downloaded the matched CID RUU (RUU_ENDEAVOR_U_ICS_40_O2_UK_1.26.206.2_Radio_1.1204.90.13_release_251230_signed) but it didnt work. My image number of the phone (I dont know what is this actually) is like 4.xxxx and the image number of the RUU is 1.xxxx.
The HBOOT version is 1.72 S ON.
Can someone by someway, please give me the link of UPDATED RUU so that I can flash to stock rom or just help me to find a way to transfer custom rom to my phone memory so that I can flash a custom rom.
I was using VIPERX ROM 4.1.1,as the phone was draining alot of battery so over efficiently I tried to FLASH BRICKED KERNEL.
NOW I AM STUCK, HELPLESS and after losing the battle I am posting this thread.
PLEASE HELP ME WITH A SUITABLE ANSWER.
I would prefer to install stock rom but it wont work I guess because of the updated HBOOT version.
Click to expand...
Click to collapse
Flash Philz 5.15.9 recovery munt sd card and copy your rom to sd card after this install it and flash the boot.img from your rom archive

Thant said:
Flash Philz 5.15.9 recovery munt sd card and copy your rom to sd card after this install it and flash the boot.img from your rom archive
Click to expand...
Click to collapse
Ohkay, I tried the way you told me .
I have Philz Version 6.19.3 however now,
I am getting this error
asset failed: getprop('ro.product.device')=='endeavoru'
II getprop('ro.build.product')=='endeavoru' II
getprop('ro.product.board')=='endeavoru'

WaleedUQ said:
Ohkay, I tried the way you told me .
I have Philz Version 6.19.3 however now,
I am getting this error
asset failed: getprop('ro.product.device')=='endeavoru'
II getprop('ro.build.product')=='endeavoru' II
getprop('ro.product.board')=='endeavoru'
Click to expand...
Click to collapse
Man, @Thant trying to help and you skip his instructions?
Do what he said,flash philz 5.15.9.

WaleedUQ said:
Ohkay, I tried the way you told me .
I have Philz Version 6.19.3 however now,
I am getting this error
asset failed: getprop('ro.product.device')=='endeavoru'
II getprop('ro.build.product')=='endeavoru' II
getprop('ro.product.board')=='endeavoru'
Click to expand...
Click to collapse
witch Rom are you try to install?

[Q] Unable to flash CM12 based roms coming from sense rom

Hi XDA,
I seldomly post anything cause most of the time i can find the answer down here but this time im stuck
as the title says i'm unable to flash any cm12 based rom i always get the error below and the installation stops:
"error executing updater binary in zip"
I'm on the latest TWRP recovery 2.8.6 and run the 3.19 hboot
In the past i was able to go from sense, to GPE, CM, AOKP, etc without any problem so somethings changed
My first thought was there was an issue with the recovery or the firmware.
it wasn't the first because phil's recovery also gives the error so if its the last I need some help

Bump

oGrady said:
Hi XDA,
I seldomly post anything cause most of the time i can find the answer down here but this time im stuck
as the title says i'm unable to flash any cm12 based rom i always get the error below and the installation stops:
"error executing updater binary in zip"
I'm on the latest TWRP recovery 2.8.6 and run the 3.19 hboot
In the past i was able to go from sense, to GPE, CM, AOKP, etc without any problem so somethings changed
My first thought was there was an issue with the recovery or the firmware.
it wasn't the first because phil's recovery also gives the error so if its the last I need some help
Click to expand...
Click to collapse
Are you on the latest 4.xx firmware? CM ROM are recommended to have 4.xx firmware before flashing.
And recently CM12 builds are a bit buggy, though recovery shows "error executing updater binary in zip" but in fact the ROM is installed successfully, just reboot and all is fine.
And to proof that you didn't search totally on XDA, look here

Bobbi lim said:
Are you on the latest 4.xx firmware? CM ROM are recommended to have 4.xx firmware before flashing.
And recently CM12 builds are a bit buggy, though recovery shows "error executing updater binary in zip" but in fact the ROM is installed successfully, just reboot and all is fine.
And to proof that you didn't search totally on XDA, look here
Click to expand...
Click to collapse
He is on the 3.19 hboot, should be enough and good to go

Thanks for the replies guys this is helpful, I'll check it out after work.
I thought my firmware upgrade to the 3.19 hboot must have messed something up.
But if CM12 Builds are buggy as of right now i'm gonna wait.
@Bobbi lim: Yes i did not look that up, because i assumed it was my own doing that caused the error in the first place

[Q] Bricked with New Partition system

I bricked One x International endeavor with new BigTwrp for new partitioning layout and installed ROM with new partition support. But it only started rebooting with recovery image showing for second than rebooting again. I installed older TWRP without new partition but its still rebooting and not entering recovery.
I tried to revert it. But when i flashed latest Clockwork recovery and when i choose install zip it gives me message that it cant find /sdcard/
fastboot fives me info that i have 4.18.401.2. Problem is that there is no 4.18.401.2 RUU. Is it safe for me to flash older RUU just to fix things.

Read this and try: http://forum.xda-developers.com/htc-one-x/help/boot-to-recovery-rom-installed-t3120841

denkem said:
Read this and try: http://forum.xda-developers.com/htc-one-x/help/boot-to-recovery-rom-installed-t3120841
Click to expand...
Click to collapse
Děkuji pěkně.
This TWRP 2.8.1.0 from your link saved my week. I really appriciate it.
I lived in Czech Republic that is in Prague from 1993 to 1998. On Barrandov.

Problem in TWRP?

I was on GPe so today i changed CID to SuperCID and my model is 0P6B13000,installed new firmware by given method in convertion post,installed TWRP and had no problem,but during factory reset i get Failed to mount /system (Invalid argument).Btw,after that i was able to boot in LineageOS,but was unable to boot into S-ROM,which i tried before flashing LineageOS.Also,i was unable to flash Stock Backup.Any ideas what's going on?

Fixed it.you can delete this

No idea if the comversion post is still valid for current firmware as I don't know which one you refered to.
It' a simple process - (after SuperCID done)
1. Install 6.xx firmware
2. Install latest TWRP 3.x
3. Boot to recovery (TWRP) - select wipe, advance, select format data - type yes. Then main menu select reboot - recovery
4. Once in recovery again you can install any ROM that you like.
To revert to Gpe, same process but using Gpe firmware for no. 1 and follow the rest

ckpv5 said:
No idea if the comversion post is still valid for current firmware as I don't know which one you refered to.
It' a simple process - (after SuperCID done)
1. Install 6.xx firmware
2. Install latest TWRP 3.x
3. Boot to recovery (TWRP) - select wipe, advance, select format data - type yes. Then main menu select reboot - recovery
4. Once in recovery again you can install any ROM that you like.
To revert to Gpe, same process but using Gpe firmware for no. 1 and follow the rest
Click to expand...
Click to collapse
Well i used just the Instructions,not the old firmware.I flashed 6.xx firmware(From your collection) . Did it all but can't install S-ROM(only this one).I guess it's just ROM problem.Don't know.Btw i got stock twrp backup from your collection,but twrp doesnt recognize it(i have it on my ExSDCard,yes).Any ideas about that?

Did you do no. 3 ? That's very important.
What color is the bootloader now ? What is written on bootloader OS - xxxxxxx, any double no. ?
To restore a nandroid, you need to extract the zip and place it in right location as explained in its instruction on post #1.
In other thread you mentioned to convert it to tmob us.. why don't just use RUU ?

ckpv5 said:
Did you do no. 3 ? That's very important.
What color is the bootloader now ? What is written on bootloader OS - xxxxxxx, any double no. ?
To restore a nandroid, you need to extract the zip and place it in right location as explained in its instruction on post #1.
Click to expand...
Click to collapse
http://imgur.com/a/uNK34
I forgot making backup of only boot and then pasting your stock backup.I'll try it now .btw thats my bootloader

ckpv5 said:
Did you do no. 3 ? That's very important.
What color is the bootloader now ? What is written on bootloader OS - xxxxxxx, any double no. ?
To restore a nandroid, you need to extract the zip and place it in right location as explained in its instruction on post #1.
In other thread you mentioned to convert it to tmob us.. why don't just use RUU ?
Click to expand...
Click to collapse
Another error occured during restoration. extractTarFor() process ended with ERROR:255

Which version TWRP that you installed ?
Used to get that error due to wrong version.
You can try 2.8.7.0 but don't accept any root offered by twrp.
Also you can try RUU - http://www.htc.com/us/support/htc-one-m8-t-mobile/news/
RUU will usually fix all errors unless it's hardware problem
Another thing .. you do not answer my previous question .. did you do no. 3 when doing conversion ?

ckpv5 said:
Which version TWRP that you installed ?
Used to get that error due to wrong version.
You can try 2.8.7.0 but don't accept any root offered by twrp.
Also you can try RUU - http://www.htc.com/us/support/htc-one-m8-t-mobile/news/
RUU will usually fix all errors unless it's hardware problem
Click to expand...
Click to collapse
Version is the newest one(3.1.1.0).I'll give a try with other version.
And about the question,yes i did step 3

I'm downloading RUU now.I guess everything will be OK.

RaZaR1998 said:
To use RUU bootloader needs to be relocked,right?
Click to expand...
Click to collapse
Not needed for S-Off device.
What you need :
Windows with usb 2.0
Latest htc usb drivers installed which you can get by installing latest htc sync manager (then uninstall syc manager but leave the drivers)
A note about S.ROM - it may have alter your system partitiom & firmware because yours is S-Off. Always advisable to reflash firmware before installing other ROM. RUU will fix these.

ckpv5 said:
Not needed for S-Off device.
What you need :
Windows with usb 2.0
Latest htc usb drivers installed which you can get by installing latest htc sync manager (then uninstall syc manager but leave the drivers)
A note about S.ROM - it may have alter your system partitiom & firmware because yours is S-Off. Always advisable to reflash firmware before installing other ROM. RUU will fix these.
Click to expand...
Click to collapse
Thanks a lot,again

ckpv5 said:
Not needed for S-Off device.
What you need :
Windows with usb 2.0
Latest htc usb drivers installed which you can get by installing latest htc sync manager (then uninstall syc manager but leave the drivers)
A note about S.ROM - it may have alter your system partitiom & firmware because yours is S-Off. Always advisable to reflash firmware before installing other ROM. RUU will fix these.
Click to expand...
Click to collapse
I've just run RUU and ERROR occured around 50%.Now i'm left without everything ... Any way to get at least the stock recovery and stuff so i can get back to bootloader?

What error that you have ?
To get back to bootloader, press & hold both power & vol up buttons. When it turns black, release both buttons & press and hold vol down button only.
Also you can try to run command fastboot reboot-bootloader
Once on bootloader try to flash firmware again. (Your current bootloader has modified dsp which I believe comes from S.ROM)

I don't remember what was the number of error,but now i get htc logo with four exclamation marks(one in each corner)... when i fastboot reboot bootloader this screen appears.I ran RUU twice,same happend both times...

When you said this
but during factory reset i get Failed to mount /system (Invalid argument)
Did you do factory reset on bootloader while TWRP was installed instead of stock recovery ? AFAIK you're not supposed to factory reset on bootloader with TWRP installed unless it is stock recovery
---------- Post added at 06:02 PM ---------- Previous post was at 06:00 PM ----------
RaZaR1998 said:
I don't remember what was the number of error,but now i get htc logo with four exclamation marks(one in each corner)... when i fastboot reboot bootloader this screen appears.I ran RUU twice,same happend both times...
Click to expand...
Click to collapse
That's RUU mode .. try the buttons press & hold method to get back to bootloader

I did Factory Reset before flashing TWRP.Now as you told me i flashed firmware again.Now my bootloader seems fine.I still dont get why RUU doesn't work.I'm S-OFF with unlocked Bootloader and as you said,re-locking is not needed.I don't get what's going on here ;d

Your first post made me understand that you factory reset after TWRP was installed .. because your problem always related to that.
Maybe try a different RUU, try the Developer Edition RUU.
Before that can you try to restore nandroid backup again using twrp 2.8.7.0 and see the error 255 still there.
Also you mentioned you can install LineageOS ?
How about installing other Sense ROM (other than S.ROM), try that too.

ckpv5 said:
Your first post made me understand that you factory reset after TWRP was installed .. because your problem always related to that.
Maybe try a different RUU, try the Developer Edition RUU.
Before that can you try to restore nandroid backup again usin twrp 2.8.7.0 and see the error 255 still there.
Also you mentioned you can install LineageOS ?
Click to expand...
Click to collapse
Well yes i could install LineageOS and RessurectionRemix (honestly i dont like them).I'll try stock backup with an older TWRP.
Now i got new TWRP but it doesnt show internal storage.is this normal?

RaZaR1998 said:
I'll try stock backup with an older TWRP.
Now i got new TWRP but it doesnt show internal storage.is this normal?
Click to expand...
Click to collapse
That's not normal. This is where you need to format data in twrp then reboot to recovery again. You should see internal storage