Develop Bugs

[Q] Installing Custom Rom Jelly Bean

Hi Everyone,
I'm new to the forums and Android in General.
After the Jelly Bean update, I noticed a bigger drain on my battery. On ICS I usually have an average of 24 hours on my normal usage of my HOX, but after the update, the average for the same usage just takes ~12 hours.
So I've decided to flash my HOX for a custom ROM. I really a noob in terms of rooting/flashing custom ROMs so I would like your assistance with this. I've read all the tutorials and manuals for doing things but still kinda unsure on the specific steps that I would take. Please let me know the step by step procedure that I would take in rooting/flashing a custom ROM in my HOX.
Here are the things that I've downloaded:
1. CWM Recovery 5.8.4.0
2. Fastboot
3. Firmware for CID__044 with Hboot
4. Android Revolution HD 16.0
I reckon that this would be the steps but I would like to be sure:
Preparing Your One X for Custom Roms (For Dummies)
[ROM] Android Revolution HD 16.0 | High Quality & Performance | Sense 4+ | BEST STOCK
Please let me know step by step on what I should do because I don't know specifically. Your assistance is very much appreciated. :good:
Thank you!

yes the first link is correct for you...just follow those steps carefully and everything will be fine...

mihirengg19 said:
yes the first link is correct for you...just follow those steps carefully and everything will be fine...
Click to expand...
Click to collapse
Thank you for the help! Just finished unlocking my bootloader and installed CWM. Currently doing a Nandroid backup.
I'll be installing Android Revolution HD 16.0 ROM and there's a couple of things that I do not understand.
How do I do these steps? (From the ARHD ROM thread):
Proper HBOOT version for Jelly Bean based ROM (don't know how to do this. I'm already in Jelly Bean, what do I do with the Hboot?)
Flash boot.img from the downloads section (where do I get the boot.img file?)
Thanks!

These steps
When u go to ur bootloader ur hboot version version will be given.
If its 1.31/33/36 ur good to go
I am assuming u already have the right hboot as ur on JB.
The Boot.img is given in the ARHD thread itself see properly.
Now to the flashing part.
Download the boot image and keep it in ur FAstboot folder.
Go into bootloader mode.
Select fastboot
Connect phone to pc using usb cable.
In fastboot give command fastboot flash boot boot.img
and then Fastboot erase cache
Now go to ur recovery and install the ROM.
Done

aman360elite said:
When u go to ur bootloader ur hboot version version will be given.
If its 1.31/33/36 ur good to go
I am assuming u already have the right hboot as ur on JB.
The Boot.img is given in the ARHD thread itself see properly.
Now to the flashing part.
Download the boot image and keep it in ur FAstboot folder.
Go into bootloader mode.
Select fastboot
Connect phone to pc using usb cable.
In fastboot give command fastboot flash boot boot.img
and then Fastboot erase cache
Now go to ur recovery and install the ROM.
Done
Click to expand...
Click to collapse
Thanks for the help!
I've run in to another problem again.
I've installed ARHD 16.0 custom ROM and I've already booted.
Upon checking the settings, Airplane Mode is stuck at "turning off", WiFi "error", there is no IMEI.
Hope you can help me out with this as well.
Thanks heaps!

jabr0ni said:
Thanks for the help!
I've run in to another problem again.
I've installed ARHD 16.0 custom ROM and I've already booted.
Upon checking the settings, Airplane Mode is stuck at "turning off", WiFi "error", there is no IMEI.
Hope you can help me out with this as well.
Thanks heaps!
Click to expand...
Click to collapse
all i can i say if you have installed the rom and it has already booted is to do a clean wipe again and start over....make sure you do a backup first and do a full wipe and flash the rom again my friend and see what happens..normally a full wipe would fix the problem....check also in the ARHD thread and search if anyone had the same issues as you

Reflash!
Some Other users have also faced the problem.U should have MD5 of the downloaded file but no prob.Just flash the ROM again problems will be gone
CHeers
And yeah full wipe + Dalvik Cache too!

1. go into fastboot mode from bootloader
2. flash boot.img
3. go into recovery from bootloader
4. FULL WIPE-factory reset, wipe cache partition, wipe dalvik cache..
5. reflash rom from recovery.
now there should not be any problem...
and u have done a good thing making a backup:good:
the boot.img can be found inside the rom zip file....or a specific compatible kernel(boot.img) prescribed by the dev can be flashed...

Thank you
Hi All!
Thanks for your replies! My phone is now working with the ARHD ROM!
I re-flashed the boot.img file included in the ROM and erased the cache and everything is working now!
Kudos to all of you and once again thank you for the help!

no problem...always happy to help...

[q] help me with flashing rom

hey guys, I first time unlocked my OneX and tried to flash cyanogenmod. At first I did backup, then erased cache and flashed rom. After that phone loaded with cianogen "logo", but it takes long time and I have read about boot.img thing... I flashed boot.img from cyanogen.rar and rebooted phone. It freezes now on "HTC quietly briliant" logo and do nothing. I tried do a restore, but phone freezes. After that tried flash boot.img and cyanogenmod few times in different ways, but its allways freeze on htc logo. What should I do?
***UNLOCKED***
ENDEAVORU PVT SHIP S-ON
HBOOT-1.39.0000
RADIO-5.1204.162.29

Which CM? Where did you acquire it?

TToivanen said:
Which CM? Where did you acquire it?
Click to expand...
Click to collapse
cm-10-20130203-NIGHTLY-endeavoru.zip
from cyanogenmod.org

I flashed latest RUU and now everything OK. But I wan't to flash custom ROMs. What guide is best? Is everything ok with my hboot version?

FORGET THIS. IM ON THE HOX FORUM HAHA, STILL THINKING IM BROWSING THE NEXUS FORUMS !!! MY BAD
qwertazz said:
I flashed latest RUU and now everything OK. But I wan't to flash custom ROMs. What guide is best? Is everything ok with my hboot version?
Click to expand...
Click to collapse
Easiest way,
(I'm guessing you have ADB/FASTBOOT)
Download TWRP
Download FX File Manager (OR any other file manager)
Connect Nexus to PC (Ensure USB Debugging is ENABLED)
Navigate to your Fastboot/ADB folder on PC
Open Command Prompt from there (Shift + Rightclick) (Open Command Prompt here)
adb devices (check your device is listed)
adb reboot bootloader
fastboot flash recovery openrecovery-twrp-2.4.1.0-grouper.img (this is the exact one I linked to you, so copy and pasting this will be fine)
fastboot reboot
Click to expand...
Click to collapse
You now have custom Recovery. To enter it power tablet off, hold volume down and start it up whilst holding volume down. Hello bootloader
Now, find yourself a custom rom, and the GAPPS (Google Apps) that relates to it. (Preferably newest one)
Create yourself a folder (On your Tablet, called ROM's, or Flash) etc.
Put the new ROM you downloaded into their.
Reboot to recovery again.
Click "Install"
Find the ROM.
Flash it.
Flash the GAPPS
Wipe Cache/Dalvik Cache.
Reboot.
BOOM!

Your hboot version is incompatible with CM10.
You have two choices:
1. Flash CM10 along with the boot.img that is compatible with your hboot. Unfortunately it breaks GPS.
Post 9308 in the linked thread.
2. Flash CM10.1 which is based on Android 4.2.1. No problems with newer hboots. Also in the linked thread.
Here's the link: http://forum.xda-developers.com/showthread.php?t=1786696
@ Wilks3y PULL THE LINK please!! It is for nexus devices, not our phone! He might get bricked if he flashes it. thanks
@ qwertazz Do not flash the recovery this guy linked you.

qwhttp://forum.xda-developers.com/showthread.php?t=1832891zz said:
hey guys, I first time unlocked my OneX and tried to flash cyanogenmod. At first I did backup, then erased cache and flashed rom. After that phone loaded with cianogen "logo", but it takes long time and I have read about boot.img thing... I flashed boot.img from cyanogen.rar and rebooted phone. It freezes now on "HTC quietly briliant" logo and do nothing. I tried do a restore, but phone freezes. After that tried flash boot.img and cyanogenmod few times in different ways, but its allways freeze on htc logo. What should I do?
***UNLOCKED***
ENDEAVORU PVT SHIP S-ON
HBOOT-1.39.0000
RADIO-5.1204.162.29[/QUOTE
http://forum.xda-developers.com/showthread.php?t=1832891
This may help:good:
Click to expand...
Click to collapse

[Q] Help me please!!!

Please help me I may be in some deep poop here
Hi, I recently tried to root my HTC one X from the latest firmware (jellybean) using this http://ausdroid.net/2012/04/02/how-to-root-the-htc-one-x/ method. Unfortunately it didn't work and instead put the phone into a boot loop. I managed to flash a version of CWM recovery onto it, and I downloaded the viperX http://forum.xda-developers.com/showthread.php?t=1745176 rom and used adb push to put it onto the sd card so I could install it. I installed it and select no custom kernal when it asked me and it had no effect. So i tried installing it again but I ticked custom kernal to see what it did. Big mistake - the phone tries to boot, it has the viperx snake thingy in the boot screen, it gets to the lock screen and is completely unresponsive and crashed. I tied downloading another rom (nocturnal) and installing that but it had no effect.
I've tried using a RUU to fix it but none of the ones I tried work, they get an error, wrong bootloader version. I relocked the bootloader and flashed a stock recovery onto it but still no luck.
Please please help me anyone!!!!
Some info:
CID: VODAP021
S-On
Hboot 1.36.0000 - i believe this coult be the problem why the ruu won't work
CPLD-None
Radio-5.1204.162.29
eMMC-bootmode: disabled
CPU-bootmode; disabled
hw secure boot; enabled\
modem path; off

What custom recovery do you have ? Type and version ?
First, you should be able to mount the sdcard as a usb diskdrive from within the recovery !
Second, you need to flash the boot.img file from the viper.zip (its inside the rom.zip).
Third, you need to perform a FULL wipe in the recovery before installing the actual rom.
Your hboot is not the problem. Its one or more of the things above.
And also check what is on top of your bootloader. Does it say ENDEAVORU ?

First off, thanks for your help. I've unlocked the bootloader again, flashed the boot image from the viperx zip and reinstalled viperx but it still won't boot. How do you perform a full wipe, and also in the installer for the rom it said something about flashing the kernal manually if you don't have s-off (in the botloader it says s-on).
BTW i'm using cwm recovery v6.0.1.9

Oke, first of all download the viper x 3.3.7. The JB version !
A FULL wipe ? You have to delete all data in the recovery. Wipe caches,dalvik cache, wipe data/factory reset. Format cache, data, system. Then install the Rom. And right before you install the rom you unhook the usb cable too.
The boot.img is flashed with a command like this
Fastboot flash boot boot.img
Used that before ?

Ok there's my first problem i had an old version of viperx, it was an ics one and my phone had jb on it.
Yes i'm familiar with using the fastboot flash command, its the only way I managed to get cwm on there
Also, just to be clear, I flash the new boot.img (the one in the viperx folder) before or after I install the new rom?

Yes you flash the new boot.img, perform a full wipe in the recovery, unhook the usb cable ! Then install the new rom.
Select full wipe in the installer, kernel question is answered by pressing viper x delivered.

Ok thanks, i'm trying to put the new rom onto the phone now, I've formatted system, /sdcard, ect in cwm plus cleared the caches, I've mounted sdcard and typed into adb: adb push ViperX3.3.7.zip sdcard, i'm waiting for it to finish pushing, its taking a while
Its done, by viperx delivered you mean viperx supplied right? I used that one, its installing now, fingers crossed..

Its easier to go into the mounts and storage section of the recovery and mount is as a mass storage device (diskdrive) its like inserting a usb stick

OK its booting, it had the viperx snake going across the boot screen, now its displaying the htc one boot screen...
Sucses! Its working again. I'll make sure to install cwm and make a backup straight away.
Thankyou so much for your help, i've sent you a little something for your trouble

Thanks mate, appreciate it ! have fun with Viper X JB !
CASE CLOSED !

Can't flash any JB custom ROM

So I've bought my phone secondhand a few months before, rooted and with ARHD 9.X.
Then I decided I want a JB custom ROM and tried to upgrade to ARHD 19.2 (JB), and also Viper X 3.4.0 (JB). - NO LUCK.
I,ve upgraded HBOOT to 1.39 and followed all the steps required for Jelly Bean upgrade (or so I think).
ISSUE
After flashing, my HOX managed to boot the system, even start the start up process, but after a minute or two everything froze up and restarted, again boot, restart... Some kind of a bootloop.
Then I just went to the older version of Viper X 2.7.0.
I really want a new JB custom ROM, but can't have it because I'm obviously missing something.
Please assist...
Here are some screenshoots with software information. cidnum: HTC__032
http://forum.xda-developers.com/attachment.php?attachmentid=1830866&stc=1&d=1364160760
http://forum.xda-developers.com/attachment.php?attachmentid=1830867&stc=1&d=1364160760

Did you flash the boot.img from the new viper rom ? And did you perform a FULL wipe in the recovery before you installed the new rom ?
And for additional info, can you do a fastboot command for me
Fastboot getvar version-main

AW: Can't flash any JB custom ROM
If you didn't flash the the boot img then download it from the ARHD thread. There is a bat. Which do it for you. Very easy
Sent from my HTC One X using xda premium

I did flash boot.img that was on the viperx's thread, also tried with the .bat file when I was trying to flash new ARHD ROM.
Before flashing every ROM I did factory reset/wipe, wiped cache partition and wiped dalvik cache.
Mr Hofs, I did the following command:http://forum.xda-developers.com/attachment.php?attachmentid=1832227&stc=1&d=1364214488

May i suggest you turn to stock first to check its all fine
http://bugsylawson.com/index.php/fi...-r-radio-5120416229-release-302015-signedexe/
Download the ruu, put the phone in the bootloader/fastboot usb mode ....lock the bootloader
Fastboot oem lock
Then right click the ruu and select " run as administrator"

ok, so I just installed the stock rom with your instructions and my HOX froze again... really frustrating.
do U have any more ideas what can I do?

vander4 said:
ok, so I just installed the stock rom with your instructions and my HOX froze again... really frustrating.
do U have any more ideas what can I do?
Click to expand...
Click to collapse
Hey , I have that same problem , HOX branded from Orange , unlocked bootloader , flashed recovery CWM 6.0.9.7 , full wipe , flashed rom :
[ROM] HTC One X *STOCK* ROM | 3.18.401.1 | Jelly Bean | HTC Sense 4+
Flashed boot.img from rom and phone freeze at startup logo ...
I read 61 pages in rom development and see few ppl have that same problem but no one answer nothing usefull ...
please help ...

but I actually manage to get past the startup logo and I am able to enjoy JB for a minute or two..... then freeze.
freemaind, I've read a lot of posts with the same problem as yours, but i didn't find any that actually had the "freeze" within the newly installed ROM.

vander4 said:
but I actually manage to get past the startup logo and I am able to enjoy JB for a minute or two..... then freeze.
freemaind, I've read a lot of posts with the same problem as yours, but i didn't find any that actually had the "freeze" within the newly installed ROM.
Click to expand...
Click to collapse
So you installed the ruu with succes ? If so and it still happends there is something wrong with the phone !
But on a ICS (viper x 2.7) rom you do not have this problem ?

Mr Hofs said:
So you installed the ruu with succes ? If so and it still happends there is something wrong with the phone !
Click to expand...
Click to collapse
Yes, I did.
But if something is wrong with my phone, how can I have ICS ROMs with no problem but not JB?

relock it and run ruu, get update to stock jb and flash the other rom. enjoy
Sent from my HTC One X with ARHD 19.2/XM-Kernel 273/Lyapota ModPack 5.3 with resManager 2.4 using xda premium

pisc3s1203 said:
relock it and run ruu, get update to stock jb and flash the other rom. enjoy
Sent from my HTC One X with ARHD 19.2/XM-Kernel 273/Lyapota ModPack 5.3 with resManager 2.4 using xda premium
Click to expand...
Click to collapse
What are you talking about it IS the jellybean ruu !
And if you would have read the thread you could see he already updated the hboot to be able to run JB roms, and he also did.....he has trouble starting the roms. But ICS roms work fine !

pisc3s1203 said:
relock it and run ruu, get update to stock jb and flash the other rom. enjoy
Sent from my HTC One X with ARHD 19.2/XM-Kernel 273/Lyapota ModPack 5.3 with resManager 2.4 using xda premium
Click to expand...
Click to collapse
Tried that, no go... still freezes.

Vander....
Could please write down ALL the exact steps you take with installing the new rom ?
From boot.img , recovery actions .... all used commands ... Etc etc etc

a few months ago I installed JB RUU and actualy managed to update it via software update.
That just reminded me that I was able to keep stock rom active without freezing when it was on charger. how weird is that?
anyway, this is how I did the software update. but as soon as I jacked the charger out, it froze again.
i don't know what else I can do, except stay with my current ROM. but I'm not happy with that.
any constructive suggestion or ideas would be great. thanks

Mr Hofs said:
Vander....
Could please write down ALL the exact steps you take with installing the new rom ?
From boot.img , recovery actions .... all used commands ... Etc etc etc
Click to expand...
Click to collapse
1.downloaded RUU from your link
2. fastboot mode -> cmd -> command: fastboot oem lock ->phone relocked
3. run RUU as administrator, followed steps as instructed on the installer
4. after a few minutes phone rebooted and loaded stock rom, took me to setup
5. went through setup process, then check software version, browsed through the phone a little and freeze

Sorry ..... I ment when you install a custom rom !
But now it goes well when you keep it on the charger but it goes wrong when you unplug it ?

Mr Hofs said:
Sorry ..... I ment when you install a custom rom !
But now it goes well when you keep it on the charger but it goes wrong when you unplug it ?
Click to expand...
Click to collapse
yes. but that happened only with stock rom. i tried that with ViperX JB and it didn't work.
did you ever hear of such case?
Yesterday i tried Viper X 3.4.0:
1. downloaded ROM and boot.img from http://forum.xda-developers.com/showthread.php?t=2087443
2. put ROM to SD card
3. reboot to fastboot usb mode
4. open CMD in fastboot folder - > entered: fastboot flash boot boot.img -> OKAY
5. unpluged USB from phone, went to recovery in fastboot mode
6. CWM recovery -> wipe data/factory reset -> wipe cache partition -> wipe dalvik cache
7. install zip from SD card, browsed to ViperX 3.4.0 and selected it
8. went through setup process, chosen wipe data in installation (just in case)
9. finished installation
10. HOX loaded ROM successfully, started setup, after few moments FREEZE

Oke try this :
Flash the viper x 3.4.0 boot.img
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
Unplug the cable and enter the recovery.....
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Then install the viper x 3.4.0, choose a full wipe in the aroma installer and choose kernel - viper delivered.....
Reboot after install

Mr Hofs said:
Oke try this :
Flash the viper x 3.4.0 boot.img
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
Unplug the cable and enter the recovery.....
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Then install the viper x 3.4.0, choose a full wipe in the aroma installer and choose kernel - viper delivered.....
Reboot after install
Click to expand...
Click to collapse
Tried exactly as instructed, no luck. Same problem.

[Q] HTC ONE X - Touchscreen not responding

Dear Xda'ers,
I recently bought a second hand HTC ONE X.
I was not convinced about the battery life so i decided to root the device and to flash another ROM.
Everything went fine till i had to flash the ROM. In the tutorial they showed a step where you had to boot the device into recovery mode by using the terminal "fastboot boot boot.img". Unfortunately this step didn't work out for me, it stayed stuck at the HTC LOGO. So i decided to just do it without the command and flash it from the recovery mode at the device itself. (Power + Volume down --> Recovery --> Install from zip --> ...)
Not a good idea ...
The device came in an endless bootloop and recovery mode was not accessible.
After a few hours searching at forums i finally found a solution.
I tried to instal many different Rom's but none of them would work, except for one: " LeeDrOiD_One_Xtreme_V6.4.0 ".
Again everything went fine,the phone started up as it was supposed to do.
Unfortunately when the phone was booted, the touchscreen did not respond to anything at all..
I recorded it :
youtu.be / tXnVFkzwvu0
(there is are spaces in the link, because i'm not able to post links yet.)
This is my first post on XDA, i would rather just look at existing topics, but none of them worked out. So can please somebody help me?
I guess I still have a few months warranty but the bootloader is unlocked so bye bye warrenty.
Some details from recovery mode, who might be usefull for you guys :
**** UNLOCKED ****
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.39.0000
CPLD-None
MICROP-None
RADIO-5.1204.162.29
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: off
Dec 17 2012,13:59:37
I hope somebody knows a solution, many thanks in advance!
Greetings
Thibaut

Use CWM/TWRP to flash new roms. First you need to flash the boot.img from the LeeDroidROM.zip... Since you haven't done that, it might be a reason for the non working touch screen...
Follow these steps:
1. Reboot your phone into bootloader (Power + Volumedown)
2. Go into fastboot and then connect to your PC
3. Go to your fastboot folder and open CMD over there and fire the following command:
fastboot erase cache
fastboot flash boot boot.img (You will find this in LeeDroidROM.zip)
fastboot erase cache
4. Disconnect your phone from PC and select HBOOT and the select Recovery from there.
5. Once CWM screen is shown:
Wipe Data
Cache Partition-Wipe cache
Advanced-Wipe Dalvic cache
6. Now install zip from sd: select your ROM.zip and flash it.
7. Reboot

Maybe a mismatch between the ROM(s) you are using (other than stock obviously) and your hboot version?
For example, the ROM you're using is an Ice Cream Sandwich ROM and you're running a seriously new version of hboot (1.39 is newest iirc), this is most probably creating issues. I know my hboot (1.12) for example wont let me run 4.2.x ROMs, but 4.1.x is fine as I'm running SlimBean 3.1.
DON'T TAKE MY WORD FOR IT, I'M STILL LEARNING! I'm still trying to get my head around hboot (having owned a HOX for 3 months), like knowing what changes were made or features added/removed in each hboot version...
ONLY IF you continue having problems AND no more with more experience comes to your aid (which they will btw ), flash TripNDroid's ROM here as it has unified hboot support, but isn't the most stable ROM on the face of the planet.
Just a slightly educated guess, sorry I can't be of more help.
Go with vin4yak's answer lol.

His HBOOT is 1.39... (from 1st post)
Yes, some ICS roms don't work well with upgraded firmwares/hboots... But I haven't faced any problem running ICS rom with Hboot 1.39 and 3.17xxx firmware... (Had tried ARHD)...
If it's a ROM specific issue, then he might need to try another JB Rom..

vin4yak said:
Use CWM/TWRP to flash new roms. First you need to flash the boot.img from the LeeDroidROM.zip... Since you haven't done that, it might be a reason for the non working touch screen...
Follow these steps:
1. Reboot your phone into bootloader (Power + Volumedown)
2. Go into fastboot and then connect to your PC
3. Go to your fastboot folder and open CMD over there and fire the following command:
fastboot erase cache
fastboot flash boot boot.img (You will find this in LeeDroidROM.zip)
fastboot erase cache
4. Disconnect your phone from PC and select HBOOT and the select Recovery from there.
5. Once CWM screen is shown:
Wipe Data
Cache Partition-Wipe cache
Advanced-Wipe Dalvic cache
6. Now install zip from sd: select your ROM.zip and flash it.
7. Reboot
Click to expand...
Click to collapse
Thanks for the reply vin4yak,
Unfortunately i have exact the same problem after following your steps.
mod2max said:
Maybe a mismatch between the ROM(s) you are using (other than stock obviously) and your hboot version?
For example, the ROM you're using is an Ice Cream Sandwich ROM and you're running a seriously new version of hboot (1.39 is newest iirc), this is most probably creating issues. I know my hboot (1.12) for example wont let me run 4.2.x ROMs, but 4.1.x is fine as I'm running SlimBean 3.1.
DON'T TAKE MY WORD FOR IT, I'M STILL LEARNING! I'm still trying to get my head around hboot (having owned a HOX for 3 months), like knowing what changes were made or features added/removed in each hboot version...
ONLY IF you continue having problems AND no more with more experience comes to your aid (which they will btw ), flash TripNDroid's ROM as it has unified hboot support, but isn't the most stable ROM on the face of the planet.
Just a slightly educated guess, sorry I can't be of more help.
Go with vin4yak's answer lol.
Click to expand...
Click to collapse
Also thanks for the reply,
I installed the " CM10 [JB v4.1.2] - v029 " Rom you mentioned, the phone boots perfectly but again the touch screen gives no sign of live....

If phone is off - power it on and wait for Android to fully load.
Wait for screen to turn off, then press power button to wake the screen.
You wont be able to unlock it but are the lights for the back-lighting of the hard keys at the bottom of the handset coming on? (It's just that they don't look like they are in your video)
If they're not coming on it could be a hardware problem... but I'd like someone to confirm that there aren't or are any partitions (inaccessible ones due to S-ON, or the ones that can be modified after bootloader unlock) that holds drivers for the touchscreen?

mod2max said:
If phone is off - power it on and wait for Android to fully load.
Wait for screen to turn off, then press power button to wake the screen.
You wont be able to unlock it but are the lights for the back-lighting of the hard keys at the bottom of the handset coming on? (It's just that they don't look like they are in your video)
If they're not coming on it could be a hardware problem... but I'd like someone to confirm that there aren't or are any partitions (inaccessible ones due to S-ON, or the ones that can be modified after bootloader unlock) that holds drivers for the touchscreen?
Click to expand...
Click to collapse
Yes indeed there are enlightened. I really can't believe that a touchscreen can get damaged from flashing..
It must have something to do with the drivers, but my knowledge is unfortunately a little too weak to make it out for myself.
Meanwhile i'm trying various things.. yet without succes

Likewise, my knowledge is also too weak to know if the touchscreen drivers (if there are even touchscreen drivers! Whichever partition they reside in) are exposed to damage.
My last guess if you have a faulty digitizer.
Unfortunately bud this is the limit of my help

Do the following command in fastboot
fastboot getvar version-main
fastboot getvar cid
And post the result here... May be going back to stock will work for you?

Lets start from the beginning
Lets get you back to full stock.
Boot your phone in fastboot
Give me the output of - fastboot getvar version-main
Sent from my HTC One X using xda app-developers app

I read the thread ! Strange issues here..... You are at a practical dead point so i guess you guys don't mind trying a new recovery......it even works with the latest 3.20 base including touch
http://db.tt/oGDkMlwc
Maybe it helps somewhere
And another idea i have is to get the right firmware and relock the bootloader, flash the firmware in ruu mode and unlock it again. So the whole update process will be clean from the start

Try the method of Mr Hofs first.
Sent from my HTC One X using xda app-developers app

vin4yak said:
Do the following command in fastboot
fastboot getvar version-main
fastboot getvar cid
And post the result here... May be going back to stock will work for you?
Click to expand...
Click to collapse
athulele said:
Lets start from the beginning
Lets get you back to full stock.
Boot your phone in fastboot
Give me the output of - fastboot getvar version-main
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
The results are :
version-main: 3.18.401.1
cid: HTC__E11
Thanks in advance guys !

You can grab mine here
http://forum.xda-developers.com/showthread.php?t=1975140
To get back to full stock.
If you wish to try to flash the firmware you can get that here
http://forum.xda-developers.com/showthread.php?t=1957376

outsob the
Mr Hofs said:
You can grab mine here
http://forum.xda-developers.com/showthread.php?t=1975140
To get back to full stock.
If you wish to try to flash the firmware you can get that here
http://forum.xda-developers.com/showthread.php?t=1957376
Click to expand...
Click to collapse
I think i might have some good news, i flashed the recoverymode you mentioned in a previous reaction. And there it is possible to navigate with the touchscreen, so i must be software related!
Now i'm going to use your Nandroid Back up, hopefully it works.

The touchdriver is updated for the bases :
3.16
3.17
3.18
3.19
3.20
Twrp had a recovery that worked with touch on those bases but the ums was broken. Now Phil has one that works with touch and ums ! Good man .......
On the latest bases its recommended to use cwm #6 series (non touch) and this one because its fully working. When you mount the sdcard it might take a while to pop up (up to a minute) but its working at least !

Oke the conclusion so far..
i tried flashing the following recovery mods :
- Philz touch recovery.img
- recovery-clockwork-touch-5.8.2.7-endeavoru.img
- recovery-clockwork-touch-5.8.3.1-endeavoru.img
- recovery-clockwork-touch-5.8.4.0-endeavoru.img
- CWM-6030-advwipe-jb422-nontouch-recovery-endeavoru-v1.1.img
Only with "Philz touch recovery.img" i was able to navigatie true the menu's with the touchscreen, so i has to be software related.
I tried to instal the Rom "LeeDrOiD_One_Xtreme_V6.4.0.zip" when i was installing it i could problem-free use the touchscreen to navigate true to the setup. Once it was installed the phone rebooted using the freshly installed Rom. Unfortunately once it was on the home screen, the touch stopt responding again..
i tried these Rom's :
- LeeDrOiD_One_Xtreme_V6.4.0.zip
- cm10_endeavoru-ota-eng.noeri-029.zip
- jellybam-v7.2.1_endeavoru-STABLE.zip
- Android_Revolution_HD-One_X_21.0.zip
- ...
Non of them worked with touch
Then i tried to restore using a NanDroid back up from Mr Hofs, nothing happend..
To be honest, i have no idea what to do next..
Someone else does?
Thanks for your times guys.

How did you restore my nandroid backup ? Flashed the boot.img from the nandroid backup, made a full wipe and restored it ?

Mr Hofs said:
How did you restore my nandroid backup ? Flashed the boot.img from the nandroid backup, made a full wipe and restored it ?
Click to expand...
Click to collapse
Mr Hofs, you can not believe how grateful I am to you.
I searched 2 longs days after a solution, and finally it works again. MANY MANY MANY thanks !
I forget to flash the boot.img
Guess i'll leave it like it is now.
Maybe one last question, do you have any idea what caused this problem?
Because i'm quite sure i will likely flash it again to a Clean Android look, and i rather do it correct
Many thanks for your time and advice !

A rom has always to be flashed in the same way as a nandroid backup.
Flash the boot.img, make a full wipe and install the rom.
The older roms won't work indeed because of the updated touchdrivers. Afaik only 3.14 and up roms are fully working.
So if you want to flash a new rom make sure its a JB rom based on 3.14 or higher