Related
Hi All,
Been having issues with my HTC One X for the past week now and haven't been able to solve it via google or searching this forum, so was hoping one of you kind people can assist a bit.
I do apologise if this issue has already been posted and I missed it, if you can link me I'll be eternally grateful.
Basically, had a few issues annoying me with my HTC so wanted to stick a custom ROM on it. Did some searching about, eventually got a plan together to unlock and root it. All went fine, unlocked it (S-On still) got TWRP recovery on it (Chose this as the ROM I was looking at claimed to be not compatible with CWR) and was booted back into my stock droid.
First thing I did after a successful boot was to go back into recovery and make a full backup (I may have not ticked the Cache and _android.secure)
Played about with the phone again a bit, getting some of the apps back on as it had been wiped, then made a second backup (This one I know I ticked all the boxes for)
Next I tried putting CleanROM on, but could get past the white HTC screen boot loop, after various reflashing the Boot.IMG and clearing cache, so fired up TWRP and restored back to my second backup. All back to normal.
Used the phone as normal for a day or so then I tried flashing another ROM (ViperX) same thing as CleanROM (White HTC screen boot loop) and then went on to try Team Baked's ROM. Managed to get this working successfully, however the ROM was not to my liking and decided to go back to my stock backup. Here's where the issue started.
Now, when restoring the backup the phone boots as far as displaying my background and the status bar at the top, however I cannot pull the status bar down and the ring to unlock the phone with doesn't appear. It sits here for a few second and then reboots. Boot loop.
I've tried clearing cache, restoring various different ways and restoring the boot.img (though I'm not sure I have the right one) but nothing works.
The last variation I tried for restoring involved:
1. Clearing the phone via TWRP (System Restore/Clear Cache/Clear Davik/Clear System/Clear SD Card (heard this can cause issues)/Clearing Android.Secure in that order)
2. Reboot into recovery
3. Repeat step 1 (in case of locked files)
4. Reboot into Recovery
5. full restore (With MD5 check enable)
6. Clear Cache and Dalvik (Tried with just cache, also done Fastboot clear cache in another attempt)
7. Attempt to boot into OS.
As I mentioned earlier, I'm not sure if I have the right boot.IMG for my phone Model/kernal/other, to be honest I'm not entirely sure of the requirements. The details of my phone I've collected so far are:
Getvar version-main (Not sure if this is kernal or what) = 2.17.771.3
hBoot = 1.12.0000
radio = 2.1204.135.20H
CID = H3G_001
Basically, as far as I can tell from the masses of reading I've been doing, I won't be able to update to custom JB for a while so want to get back to my stock ICS and then OTA to JB when my carrier releases their version, then maybe sometime in the future when the ROM specific to my phone has been cracked consider switching to a custom.
on a final note, I've tried flashing both my backups, same result. I've also tried restoring the stock recovery and doing a system recovery with that. It appears to go through the motions (phone with green arrows? Also had the red exclamation mark, but only once of the 3 attempts) then reboots and it's still the same issue.
Thanks for reading through, any advice would be much appreciated. Used to love my phone but now can barely stand to look at it.
Cheers,
Sean
Ok, so I've now downloaded a different boot.img which should be for stock ics and after flashing that, then flashing stock recovery and doing a system restore via bootloader I will 50% of the time get the lock screen and when I unlock it I see the white HTC screen of the initial setup, then it sticks there a while and reboots. It also reboots after left at the lock screen.
To me this seems like it's doing a check or looking for a certain piece of software/file that's missing but is required to finish the start-up process. Anyone any ideas?
Even if someone can point me in the right direction for an RRU for my phone as football's RRU's seem to be the only one that has the one I need but as of 5 days before all this happened the site they're hosted on doesn't allow 500+MB downloads for free members
Cheers,
Sean
**EDIT** Just done a full device wipe then restored only the SYSTEM partition and manually flashed the boot, then when I restarted it sat on the white HTC on the device setup but eventually loaded up, allowed me to complete the device setup and then loaded into the OS. All seemed fine aside from the phone being stuck in turning off airplane mode. Rebooted it to see if that would clear it up and now I'm back to bootloops before the lock screen appears (I just get my background and status bar)
So you have a nandroid backup ! Then do this
Wipe all in recovery and i mean ALL except the sdcard obvious ! system,data,caches,dalvik cache...
Then boot back into fastboot usb mode and flash the boot.img from the nandroid. Taken with TWRP the boot.img is called something like
Emmc.boot.win (or at least similar to this)
You can flash this file with fastboot command
Fastboot flash boot name of the boot.img (.win in this case)
Then enter the recovery and full wipe if you didn't o that already !
Restore the nandroid and boot it up :thumbup:
Should work
Perfect! Thanks so much man, I never even thought to flash the .wim, thought it had to be .img. Just successfully booted fully back into my old system. Hopefully will stay stable the next hour or so but looking good!
Thanks again,
Sean
Need help!!!
I'm facing the same problem with my device, i have ulocked bootloader from HTCdev and flash TWRP recovery, was trying to flash Maximus but unfortunately after flashing Maximus in TWRP my device stuck on boot logo.
Hboot: 1.12.0000
CID: HTC__J15
version-main: 2.17.415.2
Please help.
Did you flash boot.img through fastboot?
Sent from my HTC One X
TToivanen said:
Did you flash boot.img through fastboot?
Sent from my HTC One X
Click to expand...
Click to collapse
Yes, the one came with Android_Fastboot_KIT_V12.x
And make sure you flash a 2.17 based ICS rom. You can not run the maximus JB rom on that 1.12 hboot !
Mr Hofs said:
And make sure you flash a 2.17 based ICS rom. You can not run the maximus JB rom on that 1.12 hboot !
Click to expand...
Click to collapse
Then, i have done the mistake there. Now, please guide me what i need to do to get out of this problem.
I have forget to mention my device still S-ON
Please guide, sorry for troubling.
Download a 2.17 ics Rom and copy it to the phone (mount the sdcard within the recovery as a usb disk)
Take the boot.img file from that rom and copy it to the tool you used to flash it
Then enter the recovery and wipe EVERYTHING except sdcard ofcourse !!! (Cache,dalvik cache, system and data)
Then install the Rom.zip
Mr Hofs said:
Download a 2.17 ics Rom and copy it to the phone (mount the sdcard within the recovery as a usb disk)
Take the boot.img file from that rom and copy it to the tool you used to flash it
Then enter the recovery and wipe EVERYTHING except sdcard ofcourse !!! (Cache,dalvik cache, system and data)
Then install the Rom.zip
Click to expand...
Click to collapse
Thank you so much.
No problem mate ! :thumbup:
If you're looking for a Rom, I've got hboot 1.12 as well and tried a few ROMs and only ones I got working were:
Team Baked, based on jellybean though still works with 1.12. No Sense though, and a few things weren't to my liking (to name a couple,backlights on buttons didn't work and multitask button was switched back to menu button like in older devices)
SkyDragon, ics ROM with sense. Only had this a short while but appeared to be an exact stock ROM, everything working the way it should, and with a few added extra improvements.
Good luck
Slaverty said:
If you're looking for a Rom, I've got hboot 1.12 as well and tried a few ROMs and only ones I got working were:
Team Baked, based on jellybean though still works with 1.12. No Sense though, and a few things weren't to my liking (to name a couple,backlights on buttons didn't work and multitask button was switched back to menu button like in older devices)
SkyDragon, ics ROM with sense. Only had this a short while but appeared to be an exact stock ROM, everything working the way it should, and with a few added extra improvements.
Good luck
Click to expand...
Click to collapse
Is there anyway to restore it to the backup i have made with TWRP which is still in the sdcard???
sfawad81 said:
Is there anyway to restore it to the backup i have made with TWRP which is still in the sdcard???
Click to expand...
Click to collapse
Yes.
Copy the boot.img from the backup to your PC (you can mount SD card as USB from TWRP), flash it:
fastboot flash boot boot.img
And restore backup from TWRP.
Yeah, if you follow Mr hofs 1st post on the 1st page he describes all the steps required to restore. Worked perfectly for me
Slaverty said:
Yeah, if you follow Mr hofs 1st post on the 1st page he describes all the steps required to restore. Worked perfectly for me
Click to expand...
Click to collapse
Thanks alot, got it back as it was before.
Need to clear a doubt; will I be able to update my device with the OTA, as my device is unlocked, S-ON & TWRP installed?
I hope so, I'm in the same boat as you. From what I've been reading, it should still be possible as long as you put back the stock recovery and relock the bootloader.
This website offers links to download the stock recovery
http://www.androidauthority.com/one-x-revert-stock-recovery-76854/
As for relocking the bootloader, I think the process is to run this command whilst in Fast Boot USB mode
fastboot oem lock
After it's run there should be a purple "RELOCKED" at the top of your bootloader menu.
Remember to flash the recovery BEFORE you relock the bootloader
You do not have to lock the bootloader, just the stock recovery is needed ....
Stock rom (out of the box stock)
Stock boot.img
Stock recovery
Here is the 2.17 based stock recovery for those who needs it
http://db.tt/U5CK4noo
I've done it again. I think I need to be stopped! lol
I had a perfectly fine phone running the original orange 4.1.1 software. I decided to root it or something and now I'm stuck on the white intro screen.
I can get into the hboot or whatever it's called by holding down power and vol down, but once in there everything I try just takes me back to the white screen.
Factory reset just takes me back to white screen
Recovery shows me a pic of my phone with a green arrow, then a red warning sign. Sometimes from there I can get into recovery (of sorts), but theres nowhere there for me to restore my backups
Any ideas? Thanks in advance
You should probably reflash CWM
TToivanen said:
You should probably reflash CWM
Click to expand...
Click to collapse
How can I load it in?
cblanc said:
How can I load it in?
Click to expand...
Click to collapse
did the fastboot flash recovery thing on the recovery file, it all seemed to work fine (although it only took 1.3 seconds.
I then did a fastboot reboot and it's stuck at the htc page again...
cblanc said:
did the fastboot flash recovery thing on the recovery file, it all seemed to work fine (although it only took 1.3 seconds.
I then did a fastboot reboot and it's stuck at the htc page again...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1859714
read it all the way through and follow all instructions,its a bit daunting at first.you can either use adb or there are a couple of tools on the dev page..
Hmm. I've been out for a few hours, left it on charge as when I tried the RUU it said I didn't have enough power. Now it wont start up at all....
They're is a thread somewhere that covers this problem,do a search for low battery stuck in recovery.
Sent from my EndeavorU using xda app-developers app
If you have enough power to flash this recovery
http://db.tt/K8Aoto6o
The phone charges if you leave it in this recovery
Or check this thread
http://forum.xda-developers.com/showthread.php?t=1658084
Excellent, it looks like I can now charge my phone. Hopefully once it's charged a while I can flash on a new RUU
HI all, I'm hoping I'm on the end stretch now lol..
I have a fully charged phone, but tried to install the RUU but it wasn't having any of it, saying that it was the incorrect version. I have the latest that was on the page (was about a month old) it's saying my image version is 3.16.61.6 and it wants to change it to 1.28.061.9, but then it can't
Any ideas? Cheers
Do these fastboot commands
Fastboot oem readcid
Fastboot getvar version-main
Post them here please
readcid - orang001
version main - 3.16.61.6
Thanks
Yes you need a ruu or a nandroid backup that starts with 3.16 with and orange cid ! You tried to downgrade he hboot with an older ruu and that is impossible due to not having S-OFF ......
I found this on another page, will that work do you think?
billd2439 said:
Hi Matt,
Here's the Orange UK Jellybean nandroid. Users will need the stock 3.16 recovery to complete the install
CID ORANG001 Firmware 3.16.61.6 Sense 4+ Baseband 5.1204.163R.30 build 3.16.61.6 CL 128187
https://www.dropbox.com/s/x7q0bkzv9hbnuqz/Orang001JB.rar
Should be clean with no personal info on it.
Bill
Click to expand...
Click to collapse
Sorry didn't see that one !!!! Its not in the OP yet ..... Yes use that one !!! That's exactly what you need !!!
Edit : I only checked the OP, but Matt is on holiday so the OP is not updated :thumbup:
Great stuff, do I still need to do all wiping and flashing of boot?
Cheers for this, you've been a great help
Yes do a full wipe and flash the boot.img from the nandroid with fastboot ! You got lucky mate
Lets hope so
Finally downloaded the ruu, don't want to do it wrong. What commands do I need to type?
Cheers
Its not a ruu .... its a nandroid backup and its probably a .rar file ... Unpack it and put it on the phones sd card looking like this
Sdcard\clockworkmod\backup\time and date folder\backup files
Copy the boot.img from those backup files to the fastboot folder
Flash it in fastboot usb mode
Fastboot flash boot boot.img
Fastboot erase cache
Enter the custom recovery and do a full wipe/factory reset and restore the nandroid backup from the menu backup & restore
Boot it up to see if its running !
Ah, see there's mu issue, the phone's still not getting past the HTC logo at the beginning. I can't get the backup on my phone can I?
Hi, so just yesterday i decided that I wanted to go back to my stock rom, so i read up and learnt that I needed to flash stock recovery to successfully install the OTA update. I was rooted and the update didnt work so I flashed the recovery image for sense 4.0. It then allowed me to update to sense 4.1. There was then a minor update, 1.28 mb i believe and after that i was able to download the Jellybean OTA. When I download the jellbean OTA and try to install it through my stock recovery however, it comes up with an error saying E: error in OTA_ENDEAVOR_U_JB_45_S_Optus_AU_3.14.980.27-2.17.980.6_release_299170pamoph3dsqv4al9a and then it comes up with an error saying error opening E:/sdcard/external or something like that. I really have no idea what the problem is, my phone is not bricked, im just stuck on sense 4.1. My software information is listed below
My HTC one X is an optus branded phone and its CID is OPTUS_001
android version- 4.0.4
htc sense version- 4.1
software number- 2.17.980.6
htc sdk api level- 4.2.3
kernel version- [email protected] #1SMP PREEMPT
baseband version- 2.1204.135.20
Any advice or help would be GREATLY appreciated, i cant find anyone else who has the same problem
Which recovery did u flash back .... With what number did it start with ?
Mr Hofs said:
Which recovery did u flash back .... With what number did it start with ?
Click to expand...
Click to collapse
it was a recovery for 2.17, i got it from here https://www.dropbox.com/s/wbav46spkbznovp/stock recovery 2.17.img
http://forum.xda-developers.com/showthread.php?t=2043818&page=2 the problem that is happening at the top of page 2 is exactly what is happening to me, do you know where I could find an RUU for optus?
Yeah that's the right one (my link)
Did you change anything to the rom when it was rooted .... removing apps/bloatware ?
Ow and you can't install an ota by yourself in a stock recovery so the error messagges are in place.
Did u try to check software updates in the settings menu of the phone again and try to install it again from there ?
Mr Hofs said:
Yeah that's the right one (my link)
Did you change anything to the rom when it was rooted .... removing apps/bloatware ?
Ow and you can't install an ota by yourself in a stock recovery so the error messagges are in place.
Did u try to check software updates in the settings menu of the phone again and try to install it again from there ?
Click to expand...
Click to collapse
OHHH i was worried that the error messages were meaning that my phone needed to be re-flashed or something i am redownloading the OTA update now and I will try and install it, i will re post when its done. I didnt remove any bloatware from the stock rom, it is completely stock, all that is changed is I updated it to sense 4.1 then there was a minor update that said it had a few bug fixes and some power improvements
:thumbup:
Mr Hofs said:
:thumbup:
Click to expand...
Click to collapse
i was also wondering if you might know, when i updated to sense 4.1, it completely wiped my "sd card", all my files were gone except from the default ones, was that meant to happen?
Euhm well i can't recall really, at least when i went from 4.0.4 to 4.1 it certainly did not wipe my sdcard.
And i can't really say if it wipes the phone blank because i updated from a clean stock rom without any extra apps on it
But beware the chance is big that it will indeed puts the phone to a stock JB rom
Mr Hofs said:
Euhm well i can't recall really, at least when i went from 4.0.4 to 4.1 it certainly did not wipe my sdcard.
And i can't really say if it wipes the phone blank because i updated from a clean stock rom without any extra apps on it
But beware the chance is big that it will indeed puts the phone to a stock JB rom
Click to expand...
Click to collapse
oh ok, no problem. So i just downloaded and attempted to install the OTA for jellybean, in the bootloader it got to about 1/4 then came up with the red triangle. I then pressed the volume up and power button and it showed me what happened, this is in order
finding update package...
opening update package...
verifying update package...
installing update...
copying fotaboot to /data/system for customize reload...
verifying current system...
assert failed: apply_patch_check("/system/lib/libGLESv1_CM.so". "edc4c7834196831836c73d0374529a0278c". a52756f5a63c9827632587d025ee28f67739bd97")
E:error in /interna;_sdcard/download/OTA_ENDEAVOR_U_JB_45_s_Optus_AU_3.14.980.27-2.17.980.6_release_299170pamoph3dsqv4a19a.zip
(status 7)
installation aborted.
Any ideas on whats the problem?
Hmm no don't know that error code, did you install some other boot.img (a custom one) like one with sweep to wake feature or such ?
It goes wrong at patching, so my guess its rom related
Can you do these fastboot commands
Fastboot getvar version-main
and
Fastboot oem readcid
Post them please.....
You van try this one more time, reboot the phone and check the download folder with a Explorer app like es file explorer. If there is the OTA file, delete it and try once more
Mr Hofs said:
Hmm no don't know that error code, did you install some other boot.img (a custom one) like one with sweep to wake feature or such ?
It goes wrong at patching, so my guess its rom related
Can you do these fastboot commands
Fastboot getvar version-main
and
Fastboot oem readcid
Post them please.....
You van try this one more time, reboot the phone and check the download folder with a Explorer app like es file explorer. If there is the OTA file, delete it and try once more
Click to expand...
Click to collapse
Ok my version main is 2.17.980.6 and my CID is OPTUS001, as for the boot image, it is the one that i used for my stock rom back when it was still sense 4.0
Another option is if it keeps on failing ! (Because i really am starting to think that the rom is not completely stock, wether you know it or not)
Download the corresponding nandroid backup here
http://forum.xda-developers.com/showthread.php?t=1975140
Its there i just checked.......
Flash back the custom recovery (this one)
http://db.tt/Krlm4dPs
Rename it to recovery.img and flash it with fastboot command
Fastboot flash recovery recovery.img
Fastboot erase cache
Then copy the boot.img from that nandroid and flash it also
Fastboot flash boot boot.img
Enter the recovery and do a full wipe, except sdcard
Mount the sdcard as a usb drive in the recovery and copy the nandroid to the phones sdcard looking like this
Clockworkmod\backup\date and time folder\backup files from the nandroid
Then restore the nandroid and reboot to check if the rom boots up ....
after that you flash the 2.17 stock recovery back and you can update again.
This way you are 100% stock ! :thumbup:
I'm off to bed now, going for a holiday but i will check in on how you are doing sometime in the morning......the last method i described can't go wrong ! When the update fails after that then there is something serious wrong with the phone or a longshot ..... the OTA from the carrier is corrupted somehow
Mr Hofs said:
Another option is if it keeps on failing ! (Because i really am starting to think that the rom is not completely stock, wether you know it or not)
Download the corresponding nandroid backup here
http://forum.xda-developers.com/showthread.php?t=1975140
Its there i just checked.......
Flash back the custom recovery (this one)
http://db.tt/Krlm4dPs
Rename it to recovery.img and flash it with fastboot command
Fastboot flash recovery recovery.img
Fastboot erase cache
Then copy the boot.img from that nandroid and flash it also
Fastboot flash boot boot.img
Enter the recovery and do a full wipe, except sdcard
Mount the sdcard as a usb drive in the recovery and copy the nandroid to the phones sdcard looking like this
Clockworkmod\backup\date and time folder\backup files from the nandroid
Then restore the nandroid and reboot to check if the rom boots up ....
after that you flash the 2.17 stock recovery back and you can update again.
This way you are 100% stock ! :thumbup:
I'm off to bed now, going for a holiday but i will check in on how you are doing sometime in the morning......the last method i described can't go wrong ! When the update fails after that then there is something serious wrong with the phone or a longshot ..... the OTA from the carrier is corrupted somehow
Click to expand...
Click to collapse
i did everything on the list, but when it boots up, it goes past the optus logo, then does that little HTC one x animation, then stays on theat screen
Then you didn't do a full wipe, did u also wiped the dalvik cache ?
And flashed the correct boot.img from the nandroid backup ? Did it confirm that flashing was oke
And for how long did u wait already, when it changed to that screen ? May take a while
You can't flash an OTA manually, you have to get it booting with the nandroid backup and then replace CWM with the stock recovery and then relock the bootloader to get the OTA (relock might not be needed but I would do it just in case)
EddyOS said:
You can't flash an OTA manually, you have to get it booting with the nandroid backup and then replace CWM with the stock recovery and then relock the bootloader to get the OTA (relock might not be needed but I would do it just in case)
Click to expand...
Click to collapse
Look 2 posts above and the 4th post
Mr Hofs said:
Then you didn't do a full wipe, did u also wiped the dalvik cache ?
And flashed the correct boot.img from the nandroid backup ? Did it confirm that flashing was oke
And for how long did u wait already, when it changed to that screen ? May take a while
Click to expand...
Click to collapse
ok, first i flashed the boot.img, then i did a factory reset from clockwork mod, then i wiped the cache partition, then i wiped the dalvik cache, i tried restoring it again, everything goes fine, but when i boot up it just does a bootloop, it seems theres something wron with the boot.img
Mr Hofs said:
Look 2 posts above and the 4th post
Click to expand...
Click to collapse
umm.........i just realised something..........what version of HBoot am i meant to have? or does it not matter? because mine is crrently 1.12 and ive been reading that for jellybean roms you need newer
Thats very strange ! One problem I had a while back was that the nandroid was not properly copied to the sdcard ! Can you check if the nandroid folder on the phone is the same size as the nandroid you downloaded to the computer. The nandroid actually restored itself but it also went in a bootloop......the guy was 2 days busy already to get it straight !!!
---------- Post added at 01:00 PM ---------- Previous post was at 12:51 PM ----------
When you are on HBoot 1.12 you can only flash ics roms, but i assume you are restoring the 2.17 based nandroid with the same cid as yours ? 2.17 is the ics based version that belongs to your hboot
Mr Hofs said:
Thats very strange ! One problem I had a while back was that the nandroid was not properly copied to the sdcard ! Can you check if the nandroid folder on the phone is the same size as the nandroid you downloaded to the computer. The nandroid actually restored itself but it also went in a bootloop......the guy was 2 days busy already to get it straight !!!
Click to expand...
Click to collapse
yep theyre both the same size :/ i was wondering would my bootloader have to be locked to get the OTA on my stock rom that was working? and also would trying out the RUU method http://forum.xda-developers.com/showthread.php?t=2054979 here be a good idea? that too says the bootloader should be locked
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
Hi All,
I need ur help.
After installing Beats Mode - Enhanced Beats sound V13 & OneXed Camera Mod-V3.0 | HQ Camera | Sense 4.1 & Sense 4.5 | AROMA | HQ Sound,
Now i cant acces my settings and my camera,
Als my s-on is still active, tried 100 times but cant get if off.
so i cant install an other rom.
Please help me!
Installed on my HTC ONE X are the following files.
[MODE][AROMA][JB] Beats Mode - Enhanced Beats sound V13 [15/4/13]
http://forum.xda-developers.com/showthread.php?t=1720770
[MOD] OneXed Camera Mod-V3.0 | HQ Camera | Sense 4.1 & Sense 4.5 | AROMA | HQ Sound
http://forum.xda-developers.com/showthread.php?t=1765416
Yeah.....hold your power and volume down button as long as you see the bootloader. Choose fastboot - recovery and reflash your rom.
Mr Hofs said:
Yeah.....hold your power and volume down button as long as you see the bootloader. Choose fastboot - recovery and reflash your rom.
Click to expand...
Click to collapse
Can u give me a step nu step?
Go into the recovery and wipe the cache and dalvik cache, then install the rom again that you already had installed before flashing those mods. Not much to explain about that
Mr Hofs said:
Go into the recovery and wipe the cache and dalvik cache, then install the rom again that you already had installed before flashing those mods. Not much to explain about that
Click to expand...
Click to collapse
Thx, But the problem is that i cant vind the original rom
For my htc one X, so i cant reinstall
also i cant find the original RUU.exe
Give the outcome of :
Fastboot getvar version-main
You probably did not make a nandroid backup of the stock rom, or even one before installing the mods ?
Mr Hofs said:
Give the outcome of :
Fastboot getvar version-main
You probably did not make a nandroid backup of the stock rom, or even one before installing the mods ?
Click to expand...
Click to collapse
Mr Hofs,
I forgot to make a backup before the mods, did it afterwords,
After looking to a lot of youtube vids, i tried a RUU and had to relock the device,
So my htc has been relocked,
Version info.
C:\OneXRootOneClick>Fastboot getvar version-main
version-main: 3.20.401.1
finished. total time: 0.006s
Thank u for ur help!
i will make a contribution to ur paypal!
I got a nandroid backup here for ya
https://www.dropbox.com/s/900x66ulamgon08/2013-04-22.13.59.27.rar
Unlock the bootloader and flash this custom recovery
http://db.tt/SPXdFfPw
Then unpack the nandroid to the sdcard. Flash the boot.img from the nandroid backup (its inside the backup folder) perform a full wipe in the recovery and restore the backup. At that point your phone will be back to stock. Don't relock the bootloader anymore, no problem to leave it unlocked.
Mr Hofs said:
I got a nandroid backup here for ya
Unlock the bootloader and flash this custom recovery
Then unpack the nandroid to the sdcard. Flash the boot.img from the nandroid backup (its inside the backup folder) perform a full wipe in the recovery and restore the backup. At that point your phone will be back to stock. Don't relock the bootloader anymore, no problem to leave it unlocked.
Click to expand...
Click to collapse
Mr Hofs,
These steps are taken by me but it doesnt seem to work.
Step: Unlock the bootloader
Step: Download files provided by you
Step: Place files to correct folder
Step: Connect HTC One X to the PC
Step: Boot device in fastboot mode
Step: Flash Philzrecovery.img > Fastboot flash Philzrecovery.img
Step Unzip 2013-04-22.13.59.27.rar to SD card of HTC
Step Flash boot.img
Step: full wipe
Step: Restore the backup
Device keeps booting up PhilZ Touch 5
CWM Base version 6.0.3.2
And does nothing else
What next?
''Edit The Device works! its done Thank u!''
Other question could u tell me how to place s-off?
So i can install other roms
Fa1c0n said:
Mr Hofs,
These steps are taken by me but it doesnt seem to work.
Step: Unlock the bootloader
Step: Download files provided by you
Step: Place files to correct folder
Step: Connect HTC One X to the PC
Step: Boot device in fastboot mode
Step: Flash Philzrecovery.img > Fastboot flash Philzrecovery.img
Step Unzip 2013-04-22.13.59.27.rar to SD card of HTC
Step Flash boot.img
Step: full wipe
Step: Restore the backup
Device keeps booting up PhilZ Touch 5
CWM Base version 6.0.3.2
And does nothing else
What next?
''Edit The Device works! its done Thank u!''
Other question could u tell me how to place s-off?
So i can install other roms
Click to expand...
Click to collapse
you don need s-off to install different roms.
robchongke said:
you don need s-off to install different roms.
Click to expand...
Click to collapse
Huh?
Then how can i install them?
Flash the boot.img of the new rom, perform a full wipe in recovery and install the new rom.zip !
S-OFF is not even possible !!!