hi, i bought used and "broken" htc one x, previous owner said it has bad battery and ROM because it swich on and after 10s restart in infinity loop. So i replace the battery and yesterday it swich on only in recovery mode and i dont know what to do. I thnik battery have still small capacity, maybe it is another hardware issue. Today it shows only black screen and when i want turn it off the bottom "buttons" flash three times.
jesus-pd said:
hi, i bought used and "broken" htc one x, previous owner said it has bad battery and ROM because it swich on and after 10s restart in infinity loop. So i replace the battery and yesterday it swich on only in recovery mode and i dont know what to do. I thnik battery have still small capacity, maybe it is another hardware issue. Today it shows only black screen and when i want turn it off the bottom "buttons" flash three times.
Click to expand...
Click to collapse
have you tried to flash another recovery? try Philz one (the best version depends on the rom you want to try), connect to pc, mount usb as storage, copy a rom on the phone and flash it if it is bootloop maybe it's a bad kernel flash or a missing kernel flashing process
im not an expert or something but...how can i mount usb storage and copy rom when it won´t turn on?
jesus-pd said:
im not an expert or something but...how can i mount usb storage and copy rom when it won´t turn on?
Click to expand...
Click to collapse
no, if it's off you can't, but as buttons blink three times, maybe you can enter fastboot and so you can try to update recovery...
sorry, mine are only guesses as i've never faced such a condition, but if you can enter fastboot maybe you can recover the device
now it again turn on in recovery (if it is even recovery, i really dont know ). It shows this screen and i really know what to do, can you write it step by step? or post some link?
it's not recovery, it's fastboot
do this way: try to download again the unlock.bin from htcdev.com if you haven't got it, unlock the bootloader and flash the recovery i told you before, then enter recovery, connect to pc and select mount usb storage... then copy a rom zip on phone, reboot to bootloader and flash rom kernel, enter again recovery, wipe everything to flash a new rom and flash the zip.. you should be fine
search this threads for guides, there are many and i can't give you all the links
http://forum.xda-developers.com/showthread.php?t=2069904
http://forum.xda-developers.com/showthread.php?p=50374931
please fell free to ask me if you have any question/issue
p.s. before unlocking the bootloader again, update hboot to at least 1.39.0000
lukes91 said:
it's not recovery, it's fastboot
do this way: try to download again the unlock.bin from htcdev.com if you haven't got it, unlock the bootloader and flash the recovery i told you before, then enter recovery, connect to pc and select mount usb storage... then copy a rom zip on phone, reboot to bootloader and flash rom kernel, enter again recovery, wipe everything to flash a new rom and flash the zip.. you should be fine
search this threads for guides, there are many and i can't give you all the links
http://forum.xda-developers.com/showthread.php?t=2069904
http://forum.xda-developers.com/showthread.php?p=50374931
please fell free to ask me if you have any question/issue
p.s. before unlocking the bootloader again, update hboot to at least 1.39.0000
Click to expand...
Click to collapse
better idea is to keep it locked and get a ruu for him, you only need his main number :
fastboot getvar version-main
Mr Hofs said:
better idea is to keep it locked and get a ruu for him, you only need his main number :
fastboot getvar version-main
Click to expand...
Click to collapse
you're right Mr Hofs, but i really don't like stock rom and i've never used a RUU, so i fear i would have given wrong infos
anyway your way is the easiest one
Maybe he flashed the recovery as a kernel, so when he installs ROM and reboots it just boots recovery again.
Sent from my One X using XDA Premium 4 mobile app
i hope not.....but all methods work, just thinking along
Mr Hofs said:
better idea is to keep it locked and get a ruu for him, you only need his main number :
fastboot getvar version-main
Click to expand...
Click to collapse
sorry but im noob...so what do I need? what is RUU? what to do with main number? Im lost
jesus-pd said:
sorry but im noob...so what do I need? what is RUU? what to do with main number? Im lost
Click to expand...
Click to collapse
RUU is Rom Update Utility, so a tool that you run on pc with the device connected that restores devices "as new"...
you need to find a ruu that matches the main number you get with the command Mr Hofs posted before
lukes91 said:
ruu that matches the main number you get with the command Mr Hofs posted before
Click to expand...
Click to collapse
where is my main number? where am i suppost to write command?
if it is like: in fastboot select getvar select version-main, then i cant do it, as you can see i havent got getvar in my fastboot menu
No, you have to install fastboot on your pc and run the command there... Search a guide about how to setup fastboot on pc...
Sent from my HTC One X using XDA Premium 4 mobile app
Related
Hi Gentlemen,
I am new to rooting Androind phones since been using iphone all this years. Right now, I think my HTC One X is bricked. This is what I've done to cause it in this situation:
1) After installing Clockwork Recovery and Super SU. I installed the super wipe.
2) Run super wipe and proceeded to install Android Revolution ROM but the installation was unsuccessful. Not much reason was stated. So I proceeded to reboot the phone and now it just hang at the splash screen.
I've done alot of read up and research the forum how to unbrick my phone but I'm clueless and don't know what to do anymore. I can still get to bootloader screen and that's the furthest I can go.
Pleasse help me.
try to install a stock rom: http://forum.xda-developers.com/showthread.php?t=1546970
Did u do a backup first? Iff not
1) Flash stock recovery:
Grab it from here: http://forum.xda-developers.com/showthread.php?t=1579797
Then Boot in bootloader >> Fastboot and issue the following command (assuming that the offical recovery is named recovery.img): fastboot flash recovery recovery.img
2) Relock Bootloader:
Boot in bootloader >> Fastboot and issue the following command: fastboot oem lock
3) Find and run/flash the RUU for your device, find it here: http://forum.xda-developers.com/showthread.php?t=1543604
Mod or Die
snowwhite007 said:
Did u do a backup first? Iff not
1) Flash stock recovery:
Grab it from here: http://forum.xda-developers.com/showthread.php?t=1579797
Then Boot in bootloader >> Fastboot and issue the following command (assuming that the offical recovery is named recovery.img): fastboot flash recovery recovery.img
2) Relock Bootloader:
Boot in bootloader >> Fastboot and issue the following command: fastboot oem lock
3) Find and run/flash the RUU for your device, find it here: http://forum.xda-developers.com/showthread.php?t=1543604
Mod or Die
Click to expand...
Click to collapse
After doing step 2, I receive this respond:
... INFOLock successfully...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
Is it something wrong?
amigo_s said:
try to install a stock rom: http://forum.xda-developers.com/showthread.php?t=1546970
Click to expand...
Click to collapse
I did try doing that but this error pops out:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Pls help me
I take it you did the right thing and made sure you have the right RUU for your phone before you attempted to root?
Hmmm managed to get myself stuck in the same situation here a well as wouldnt go back into recovery. Have relocked bootloader but whn I try to reflash RUU it wont recognise the phone even though it shows in device manager correctly and I can control via fastboot commands but doesnt show when using adb devices.
Any ideas whey RUU cant see the phone?
it defo the correct Ruu?
Mod or Die
Hi.My problem is when I want flash stock terminal give something like that sending 'recovery' (5786 KB)... FAILED (remote: (00120000))
whats the problem?
ps1
right now its
sending 'recovery' (5786 KB)... OKAY
writing 'recovery'... FAILED (remote: battery low)
MacBook-Pro-xxx:fastboot xxx$
when i try to charge phone automaticlly starts
snowwhite007 said:
it defo the correct Ruu?
Mod or Die
Click to expand...
Click to collapse
I presume so as is EUROPE RUU of which I can only find 2, hav the other one downloading currently, but the dialogue it comes up with says about no connection via USB and surely even the incorrect RUU would dectect the phone but fail on authentication wouldn't it?
snowwhite007 said:
Did u do a backup first? Iff not
1) Flash stock recovery:
Grab it from here: http://forum.xda-developers.com/showthread.php?t=1579797
Then Boot in bootloader >> Fastboot and issue the following command (assuming that the offical recovery is named recovery.img): fastboot flash recovery recovery.img
2) Relock Bootloader:
Boot in bootloader >> Fastboot and issue the following command: fastboot oem lock
3) Find and run/flash the RUU for your device, find it here: http://forum.xda-developers.com/showthread.php?t=1543604
Mod or Die
Click to expand...
Click to collapse
sounds awfully familiar... http://forum.xda-developers.com/showpost.php?p=24775692&postcount=3 lol
Remember to Flash Stock Recovery before relocking your bootloader.
wen you are done whit that enter bootloader and press Fastboot then run the RUU file...
DaDoctor!
ya i was one of the first to say that lol but i dont care anymore hehe im just trying to help ppl but sometimes ill get wen seeing ppl posting that exact same thing you have done to alot of pll
Managed to get the RUU to recognise my phone, needed HTC Sync installed even though everything else was working ok without, but although I can now flash RUU's I get a customer number error which I guess Im getting as my phone was a branded T-Mobile one.
Therefore am I correct in saying that unless I can get RUU 1.26.110.5, which is the RUU I need, or get recovery working again by some mircale then Im screwed and now have a rather expensive paper weight?
I manage to boot to cwm recovery. And now the question is, how can I transfer the stock rom or the android revo hd rom to my sdcard from fastboot since i cant boot up my phone cos it stuck at the flash screen. Since I had done the superwipe before all this and now its empty.
Thanks for all the tips given so far.
I FOUND THE SOLUTION !!!!!!!!!!!!!
First Sorry for my French !
So, flash stock recovery first, lock the recovery.
Go to fastboot, and click on the Power Off, screen goes black and the phone is OFF.
Put the charger and the usb on the phone, WAIT 1 or 2hours, led still red, DON'T POWER ON !
When is done, go fastboot, launch RUU, IT'S DONE, battery is good !
Works for me
Swannsin said:
I manage to boot to cwm recovery. And now the question is, how can I transfer the stock rom or the android revo hd rom to my sdcard from fastboot since i cant boot up my phone cos it stuck at the flash screen. Since I had done the superwipe before all this and now its empty.
Thanks for all the tips given so far.
Click to expand...
Click to collapse
Cool well done for getting back into recovery....how did you manage it? As for getting rom back did you not do a backup of the previous rom before wiping? If not you may be stumped for the time being as USB mount does not work on any of the custom recoveries so far.
I fastboot the boot.img and also flash the CWM recovery. This steps enable me to get back to recovery.
But my mistake was i did not any back up on the previous rom and now i cant do a normal boot up as it will stuck at the htc white screen. So i believe the reason it cant boot up is because there is no rom at all.
So now, the only way i can flash rom from recovery is to send file to my sdcard via fastboot. but i don't know the command needed for it, so I need help with the command. i have with me now is the stock rom and also ARHD rom. but i cant access my sdcard to transfer the file.
I have tried to download the stock RUU but unfortunately it says that my CID is imcompatible. My set is from Singapore and now I will try to download this RUU RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.26.708.2_Radio_1.1204.90.13_release_251215_signed.exe.
If all else fails, final option is to send back my set to HTC service center and have it repaired and pay the charges
Swannsin said:
I fastboot the boot.img and also flash the CWM recovery. This steps enable me to get back to recovery.
But my mistake was i did not any back up on the previous rom and now i cant do a normal boot up as it will stuck at the htc white screen. So i believe the reason it cant boot up is because there is no rom at all.
So now, the only way i can flash rom from recovery is to send file to my sdcard via fastboot. but i don't know the command needed for it, so I need help with the command. i have with me now is the stock rom and also ARHD rom. but i cant access my sdcard to transfer the file.
I have tried to download the stock RUU but unfortunately it says that my CID is imcompatible. My set is from Singapore and now I will try to download this RUU RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.26.708.2_Radio_1.1204.90.13_release_251215_signed.exe.
If all else fails, final option is to send back my set to HTC service center and have it repaired and pay the charges
Click to expand...
Click to collapse
Ok managed to get mine booting back into CWM Recovery as well now but dont think about sending back to HTC as the CWM guys are working on USB Mount & ADB as we speak so dont think it will be to long. Ill look into fatboot commands now and see if there isnt soemthing we can use.
There's always a way..........
DaDoctor said:
sounds awfully familiar... http://forum.xda-developers.com/showpost.php?p=24775692&postcount=3 lol
Click to expand...
Click to collapse
Yeah shud have a sticky ull notice the other 6 ppl that i copy pasted for i quoted ure username aha i really wonder why ppl want to flash stuff without fuly charging and then having audacity to not backup ahha
Mod or Die
snowwhite007 said:
Yeah shud have a sticky ull notice the other 6 ppl that i copy pasted for i quoted ure username aha i really wonder why ppl want to flash stuff without fuly charging and then having audacity to not backup ahha
Mod or Die
Click to expand...
Click to collapse
Backups are only half of the story. When you cant get into recovery to restore the backups that you HAD made and then when trying to reflash the RUU to resotre your phone it then wipes the backups but then allows you back into recovery where you now have no backups nor the ability to mount USB or push anything to the SD so and still in the same siutation just with nice blue writing now thats just plain sods law......LOL!
---------- Post added at 09:24 PM ---------- Previous post was at 09:16 PM ----------
Swannsin said:
I fastboot the boot.img and also flash the CWM recovery. This steps enable me to get back to recovery.
But my mistake was i did not any back up on the previous rom and now i cant do a normal boot up as it will stuck at the htc white screen. So i believe the reason it cant boot up is because there is no rom at all.
So now, the only way i can flash rom from recovery is to send file to my sdcard via fastboot. but i don't know the command needed for it, so I need help with the command. i have with me now is the stock rom and also ARHD rom. but i cant access my sdcard to transfer the file.
I have tried to download the stock RUU but unfortunately it says that my CID is imcompatible. My set is from Singapore and now I will try to download this RUU RUU_ENDEAVOR_U_ICS_40_hTC_Asia_HK_1.26.708.2_Radio_1.1204.90.13_release_251215_signed.exe.
If all else fails, final option is to send back my set to HTC service center and have it repaired and pay the charges
Click to expand...
Click to collapse
Think we are fairly screwed until either USB/ADB is working in recovery or S-Off is available in which case any RUU should work I believe. Worth hanging on rather than paying HTC in my opinion.
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?
Right here goes!
I've scoured the threads and I think I've tried everything so far to solve my problem, but still to no avail!
I woke up one morning and my phone was in hboot, wasn't plugged in, and was unresponsive. I tried charging but it wouldn't take it. I'm running stock JB 4.1 via OTA from Vodafone (UK). I had a new battery, and managed to replace the old one. I checked the old one and it had 2.8v output with the new one being 3.8V. I then ran that .bat file to loop the phone in a sort of charge mode to make sure I had sufficient charge. Phone still wouldn't boot. I then tried to do various things listed on this forum, but still have same symptoms. I just need the damn thing to work!
My current version is 3.14.161.27, an I managed to find this RUU. Download consisted of boot.img, rcdata.img and recovery.img
I'm in CMD....with the phone in unlocked mode connected via fastboot usb. Clear chache, run the boot.img and then I run hboot_1.36.0000_.img but error comes up saying cannot load 'hboot_1.36.0000_.img' : unknown error
If i re-lock the phone and do the same thing I get access not allowed in cmd.
what am I doing wrong here? any ideas? I can't find a .exe file for my original ROM either.
recovery doesn't work...just hangs on the HTC screen. factory reset doesn't work wither, same thing happens
I would be happy to try a custom ROM or anything that might get the phone booting again.
Please point me in a 'direction' or offer some help, I will be very grateful!
Did you do the command
Fastboot erase cache
with the phone in the bootloader ?
And then try to enter the recovery.....but do it with unlocked bootloader
Sent from my GT-P5110 using xda app-developers app
Mr Hofs said:
Did you do the command
Fastboot erase cache
with the phone in the bootloader ?
And then try to enter the recovery.....but do it with unlocked bootloader
Sent from my GT-P5110 using xda app-developers app
Click to expand...
Click to collapse
Unlocked it again just now, erased cache but then just hangs in the HTC screen after selecting recovery. Eventually reboots.
Hmm did you reflashed the recovery ?
And also do these fastboot commands
Fastboot getvar version-main
Fastboot oem readcid
Sent from my GT-P5110 using xda app-developers app
Mr Hofs said:
Hmm did you reflashed the recovery ?
And also do these fastboot commands
Fastboot getvar version-main
Fastboot oem readcid
Sent from my GT-P5110 using xda app-developers app
Click to expand...
Click to collapse
I think I have, how would I flash it? By running fastboot flash recovery recovery.img?
version-main gives: 3.14.161.27
CID: VODAP001
gwyndavies said:
I think I have, how would I flash it? By running fastboot flash recovery recovery.img?
version-main gives: 3.14.161.27
CID: VODAP001
Click to expand...
Click to collapse
Downloaded these files from the site earlier: the VODAP001
http://forum.xda-developers.com/showthread.php?p=33308420&highlight=vodap001#post33308420
Did you use that to upgrade the hboot ! After upgrading the hboot you can reflash a custom recovery
Fastboot flash recovery recovery.img
Fastboot erase cache
Enter recovery and perform a full wipe, then mount the sdcard as a usb mass storage device and copy the rom.zip over .... flash the boot.img in fastboot
Fastboot flash boot boot.img
Enter recovery and install the rom.zip
Mr Hofs said:
Did you use that to upgrade the hboot ! After upgrading the hboot you can reflash a custom recovery
Fastboot flash recovery recovery.img
Fastboot erase cache
Enter recovery and perform a full wipe, then mount the sdcard as a usb mass storage device and copy the rom.zip over .... flash the boot.img in fastboot
Fastboot flash boot boot.img
Enter recovery and install the rom.zip
Click to expand...
Click to collapse
my hboot was already version 1.36 so didn't need to. Flashed recovery, and erased cache. CMD...saying successful. Then I unplug usb and go into recovery...but still it just hangs on the HTC screen.
I'm honestly suspecting a hardware fault now tbh.
Hmm this is odd ! Do this
Fastboot erase recovery (if i recall the command)
Then flash this one
http://db.tt/Krlm4dPs
Mr Hofs said:
Hmm this is odd ! Do this
Fastboot erase recovery (if i recall the command)
Then flash this one
http://db.tt/Krlm4dPs
Click to expand...
Click to collapse
I've tried a few commands now and get the same error. I did flash the recovery 5.8.4.0 anyway but got an 'unknown error'. I have to stay I'm stumped now! I've been scratching my head for a while. I did all this wile the phone was in *UNLOCKED* mode too.
The recovery has to be without spaces. Change it to just recovery.img
The remote not allowed seems in place when the bootloader is locked
Mr Hofs said:
The recovery has to be without spaces. Change it to just recovery.img
The remote not allowed seems in place when the bootloader is locked
Click to expand...
Click to collapse
Flashed the recovery 5.8.4.0 and it seemed to take it fine...see PGN. However when I click recovery on my phone, it goes to the HTC screen again, and just hangs. It seems its just fed up of being a phone, wants to change its career path and become a paperweight
Also did a
Fastboot erase cache
Afterwards the flash ?
Mr Hofs said:
Also did a
Fastboot erase cache
Afterwards the flash ?
Click to expand...
Click to collapse
still nothing I'm afraid.
Hmm I'm pretty out of answers at this point. What if you start all over.....install the RUU to get back to stock, or flash the right firmware again. And then reflash the custom recovery
gwyndavies said:
I've tried a few commands now and get the same error. I did flash the recovery 5.8.4.0 anyway but got an 'unknown error'. I have to stay I'm stumped now! I've been scratching my head for a while. I did all this wile the phone was in *UNLOCKED* mode too.
Click to expand...
Click to collapse
try to update stock karnel and stock karnel mods
Nope won't help.....I was on teamviewer tonight with a similar issue ....in no way we could acces the recovery while flashing went fine ! He had to run the batt script to charge the phone and then perform the ruu. I hope to hear good news from him tomorrow.....
Mr Hofs said:
Nope won't help.....I was on teamviewer tonight with a similar issue ....in no way we could acces the recovery while flashing went fine ! He had to run the batt script to charge the phone and then perform the ruu. I hope to hear good news from him tomorrow.....
Click to expand...
Click to collapse
Thank's for your time on this issue. I've tried every trick in the book and had to give up. I'm putting it down to some hardware issue. I have another phone on the way via insurance, but gutted I couldn't get my data back! learnt my lesson...back everything up regularly!
Thanks again
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 just bought this phone and for some reason it comes with the bootloader unlocked and a custom software. I was unable to update my phone so i was searching here and over there. Mr Hofs from this forum gave me some advices which i will quote.
My phone data is readcid: HTC__622
Fastboot getvar version-main : 3.14.708.28
He suggested me to: 1: download this RUU RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_HK_3.14.708.28_Radio_5.1204.162.29_release_299865_signed.exe
2: charge the battery to 100%
3: put the phone in the bootloader and relock it (if it is unlocked)
Fastboot oem lock
4: keep the phone in the relocked bootloader
5: right click on the ruu and select "run as administrator"
6: follow on screen info (phone and pc)
7: fingers crossed
8: back to stock it is
But the procces failed, it said i had to dowload the proper version and signed. Now my phone is stuck in the bootloader which is relockked. Please help me getting this back to life.
Thanks in advanced.
By some reason I can't explain, the phone came with the software called Android Revolution 6 by mike1986 :/
Try running this RUU from a different PC, it should work if your bootloader is locked! This is the correct RUU for your phone!
However, if you still can't get to your OS, then restore a nandroid backup via recovery!
Download this nandroid backup : https://docs.google.com/file/d/0BwEZB8sRo0DSdTRrN3FSSk5fUE0/edit?pli=1
Recovery : http://htcfanboys.com/download/seadersn/?action=list&file=4944
Now firstly unlock your bootloader
Code:
fastboot flash unlocktoken unlock_code.bin
Now flash the recovery you had just downloaded...(rename it to recovery.img)
Code:
fastboot flash recovery recovery.img
fastboot erase cache
Now boot into recovery and go to mounts and storage and mount USB. Copy the files of the nandroid backup zip to /clockworkmod/backup/ and paste it there...
Transfer the boot.img into the fastboot folder, boot into fastboot USB and flash the boot.img
Code:
fastboot flash boot boot.img
fastboot erase cache
Now go back to recovery and wipe data/cache partition/dalvic
Now go to Back up and restore and restore the nandroid backup you had just copied to your phone! and then REBOOT!
---------- Post added at 01:01 PM ---------- Previous post was at 12:58 PM ----------
If you want to go full stock to receive OTA updates, then you also need to flash the stock recovery.. Download this : https://www.dropbox.com/s/ms7vd18vb9watr8/stock recovery 3.14.img
boot into fastboot mode and flash the recovery and then lock your bootloader!
Thanks for your reply, but which RUU? Seems like you forgot the link.
My bootloader doesnt say locked, it say relocked. Is the same?
Thanks so much for your help.
By the way. I have downloaded the Android SDK but it wont install at all.
Edited: I've tried with the same ruu in other PC and nothing.
Maybe its because it had a custom rom? It came with Android Revolution 6 or someting
CM17X said:
Thanks for your reply, but which RUU? Seems like you forgot the link.
My bootloader doesnt say locked, it say relocked. Is the same?
Thanks so much for your help.
By the way. I have downloaded the Android SDK but it wont install at all.
Edited: I've tried with the same ruu in other PC and nothing.
Maybe its because it had a custom rom? It came with Android Revolution 6 or someting
Click to expand...
Click to collapse
I meant to say that the RUU given by Mr Hofs is correct one for your device! It should work...
Yes, relocked = locked bootloader...
Don't download the whole android sdk... you just need the fastboot folder and HTC Sync Manager (for the drivers) to run fastboot commands:
Here are the links:
Fastboot folder: http://d-h.st/8Jr
HTC Sync Manager: http://www.htc.com/www/support/software/htc-sync-manager.aspx
Nope, regardless of the rom your currently on, the RUU will work.. Don't know why your not able to finish it... Hmmm
I dont know. It just wont work
Im finishing downloading the files you suggestted me but i have a doubt in the step when you say to wipe the cache. How? From the phone or by deleting its contect on PC?
I'm a dumb, i know :/
Thanks for help me
vin4yak said:
I meant to say that the RUU given by Mr Hofs is correct one for your device! It should work...
Yes, relocked = locked bootloader...
Don't download the whole android sdk... you just need the fastboot folder and HTC Sync Manager (for the drivers) to run fastboot commands:
Here are the links:
Fastboot folder:
HTC Sync Manager:
Nope, regardless of the rom your currently on, the RUU will work.. Don't know why your not able to finish it... Hmmm
Click to expand...
Click to collapse
CM17X said:
I dont know. It just wont work
Im finishing downloading the files you suggestted me but i have a doubt in the step when you say to wipe the cache. How? From the phone or by deleting its contect on PC?
I'm a dumb, i know :/
Thanks for help me
Click to expand...
Click to collapse
Go to your custom recovery(CWM) and select
Wipe Cache Partion>Wipe Cache
Wipe Data/factory reset>Wipe data
Advanced>Wipe dalvic cache>Wipe dalvic
In the first step, it says "cant upload unlock_code.bin" Where is that file?
What i did was place the recovery.img into the fastboot folder
CM17X said:
In the first step, it says "cant upload unlock_code.bin" Where is that file?
What i did was place the recovery.img into the fastboot folder
Click to expand...
Click to collapse
Oh ohkk You got your phone with bootloader unlocked right? Skip that step! Go on with the next one!
If your bootloader is locked then you will have to go to htcdev.com and register there and follow the steps to unlock your bootloader. You will get a file via email (unlock_code.bin)... flash that to unlock your bootloader!
vin4yak said:
Oh ohkk You got your phone with bootloader unlocked right? Skip that step! Go on with the next one!
If your bootloader is locked then you will have to go to htcdev.com and register there and follow the steps to unlock your bootloader. You will get a file via email (unlock_code.bin)... flash that to unlock your bootloader!
Click to expand...
Click to collapse
Kinda late. I managed to get the unlocker.bin file and i unlocked it again and my phone is back to life. HOW CAN I KISS YOU?
I will wait for it to charge at 100 and then i will follow the steps.
What should i do next? THANKS SO MUCH FOR YOUR HELP (Also Mr Hofs)
CM17X said:
Kinda late. I managed to get the unlocker.bin file and i unlocked it again and my phone is back to life. HOW CAN I KISS YOU?
I will wait for it to charge at 100 and then i will follow the steps.
What should i do next? THANKS SO MUCH FOR YOUR HELP (Also Mr Hofs)
Click to expand...
Click to collapse
ah! Great! Your phone is booting to OS now right? ARHD? or have you back on stock??
vin4yak said:
ah! Great! Your phone is booting to OS now right? ARHD? or have you back on stock??
Click to expand...
Click to collapse
Is into the OS right now. Ill follow the steps for put it back to stock with the nandroid backup. May i?
Hi guys ! Don't know what's happening with the ruu's these days. Getting a lot of issues with people who run them. Its a driver/HTC sync problem somewhere !
But yeah try the nandroid backup thing. That should work
Say a prayer for me, please, gonna try!
Mr Hofs said:
Hi guys ! Don't know what's happening with the ruu's these days. Getting a lot of issues with people who run them. Its a driver/HTC sync problem somewhere !
But yeah try the nandroid backup thing. That should work
Click to expand...
Click to collapse
CM17X said:
Say a prayer for me, please, gonna try!
Click to expand...
Click to collapse
Burning a candle
CM17X said:
Is into the OS right now. Ill follow the steps for put it back to stock with the nandroid backup. May i?
Click to expand...
Click to collapse
Yes you may... :silly:
Mr Hofs said:
Burning a candle
Click to expand...
Click to collapse
loolllllllll
Something is wrong.
I have placed the files which are into the nadroid backup into clockwork/backup, not the package itself, and after wip the cache and stuff, i tried to restore but nothing happens, it just put me back in the sme menu.
Now the phone is locked in the Android logo :/ What should i do?
Mr Hofs said:
Hi guys ! Don't know what's happening with the ruu's these days. Getting a lot of issues with people who run them. Its a driver/HTC sync problem somewhere !
But yeah try the nandroid backup thing. That should work
Click to expand...
Click to collapse
vin4yak said:
Yes you may... :silly:
loolllllllll
Click to expand...
Click to collapse
The folder on the sd should look like this
Clockworkmod\backup\*time and date folder*\all separate backup files
By time and date you mean 2013-01-08.00.15.16 3.14.708.28_cwm_root ?
I messed it up, i did Clockworkmod\backup\all separate files.
Now the phone is stuck in android logo. What should i do?
Mr Hofs said:
The folder on the sd should look like this
Clockworkmod\backup\*time and date folder*\all separate backup files
Click to expand...
Click to collapse
Ah go back into the recovery
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache,data,system
Then restore the nandroid
Haha, sorry for the noob questions, I had to learn android stuff in 2 hours due the rush thinking I was getting a brick.
The phone is working now, thank you so much, guys.
Only strange things are that I don't have more languages than Taiwanese and English, not Spanish (system language); also the nandroid was rooted and I have root now, and the splash screen says "HTC one" lol
Again, you're the best. Thanks for help me out, ill see you around while learning
Sent from my HTC One X using Tapatalk 2