I looked around and didn't see a solution to my problem. I might have missed it because I'm kind of panicked right now.
My HOXL was dying really fast. Within a few hours, it falls from 80% to 0%. I wanted to factory reset because I heard that it helps the battery life.
So I followed the process I always have (I'm unlocked, rooted, and had pacman's evita ROM installed) and did a factory reset, wiped cache and dalvik cache. Then I re-flashed pacman's ROM and the gapps. When I rebooted though, it went to the HTC screen and in a few seconds it just went black. I think it might have still been on or something, but nothing was happening for like 30 minutes. I tried it over and over again, flashing new ROMs and kernels, but now all that's happening is that it's stuck on that very first HTC screen.
I downloaded the latest JB RUU for evita to try it out. But if I can't get past that first screen, is there a way to connect it? I can still get into TWRP's recovery. My HBoot is 1.09. I'm really starting to feel nervous about having to buy a new phone, yet I feel like there should be a way to fix this. Could flashing the stock kernel be all I need? I tried to download from Viper's hub, but the download just stops at 99% and doesn't finish.
Please, I would really, really appreciate any help!
I would run the 3.18 RUU (which you can do in fastboot).
Try a complete wipe: Factory reset, system, cache and dalvik cache in twrp or if it is not wiping correctly due to twrp version " 2.3......" is best fro our phones, try downloading and installing twrp again or use adb commands to wipe and flash rom again.
I've tried a complete wipe, but I just noticed that my TWRP version is 2.2.0. I tried the wipe like five or more times and it didn't work. My PC isn't reading the HOXL in the adb command window. I rooted a Sero Pro 7 this way, so I think I should have the drivers installed for it... I'm going to try installing the HTC Sync drivers and seeing if I can send adb commands to my HOXL. If this doesn't work, I'm going to try the 3.18 RUU. I heard that some people have bricked their HOXL completely doing this, but I didn't change my SuperCID and s-on (?), so would I be fine? Or would it be safer to just use the latest ICS one (RUU_EVITA_UL_ICS_40_S_Cingular_US_2.20.502.7_Radio _0.19as.32.09.11_2_10.105.32.25L_release_271865_si gned.exe)?
So you have no way to flash boot image separately? I would definitely try to get device recognition so adb can be used before running ruu.
Sent from my HTC One X using xda premium
Yeah, I went through the noob way of unlocking and rooting this phone, so there was no need to use adb commands. I would have liked to try that first before running RUU, but I just want to have a working phone again, even if I have to go through the whole process of unlocking and rooting.
Sent from my Nexus 7 using XDA Premium HD app
I would still try to get a good adb environment. Sometimes panic is not a good thing. Just be careful and make sure you get the proper ruu and do not let the battery die while running it. Let me know if it works.
Sent from my HTC One X using xda premium
Venomtester said:
I would still try to get a good adb environment. Sometimes panic is not a good thing. Just be careful and make sure you get the proper ruu and do not let the battery die while running it. Let me know if it works.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
This is what I'm worried about:
SERooted wrote: Note to OP: You really should add to the 1st post that it is not wise to flash the 3.18 firmware over super cid and s-on.. its not a good thing for most people to have a qhsb_dload turn their phone into a paper weight before finding out that they shouldn't have used that file to begin with. i had to find out the hard way. i would have flashed the ics firmware on my phone but decided to go with the big JB only to find out that it turns it into a paperweight. I understand this is no fault but my own, however this would greatly help people when choosing which ruu to run.
http://forum.xda-developers.com/showthread.php?t=2191477
I know what you mean lol. I would only do that as a last resort. I would try and get adb working since the phone is not bricked. It just seems to have no Rom or boot image. Have you tried one with an aroma installer?
Sent from my HTC One X using xda premium
Venomtester said:
I know what you mean lol. I would only do that as a last resort. I would try and get adb working since the phone is not bricked. It just seems to have no Rom or boot image. Have you tried one with an aroma installer?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Huh...I just tried flashing the UrDroid ROM because of its aroma installer, but it didn't happen in recovery, like I thought it would. It said it was successful, so I rebooted the system. It got past the initial screen with an AT&T boot img and htc one img. Now I'll have to see if it actually loads past this.
EDIT: It worked! I'm going to have to try to see if I can load boot img some other way than just an aroma installer.
You can use Flash GUI from the market to install boot images or get Goo Manager to install a 2.3..... Version of twrp. That may solve your problems.
Sent from my HTC One X using xda premium
Venomtester said:
You can use Flash GUI from the market to install boot images or get Goo Manager to install a 2.3..... Version of twrp. That may solve your problems.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Second Flash GUI....works like a charm
Related
I am creating this post as a tip and warning to everyone with an at&t htc one x (mostly noobs for help). If you have rom manager on your phone do not use it to flash the new recovery listed for the htc one x (gsm). I've been messing with android since 2009, but me seeing a new recovery for the one x with (gsm) next to it thought hey finally got an official clockwork recovery for our phones!!!!! Well i was wrong. Its for the international versions only not ours. The partition it writes the recovery to is on our bootloader partition, and flashing it will kill your phone. I flashed it, kept it on for hours but as soon as i rebooted the phone it turned off and would not turn on or charge. You'll pretty much be screwed and have to get a new phone unless you know how to run linux and ask for help fixing it which is harder than you think. Again do not flash the htc one x (gsm) recovery in rom manager!!!!!
Hope this helps some of you before hand and not after.
If this post isn't necessary i am sorry and please close it.
Nobody should ever use ROM Manager for anything, EVER.
Sorry for your loss.
Why would you flash a recovery for a different device and expect it to work?
When ROM manger is supported on your device its a great tool, like on the sgs2. If its not officilially supported on your device, don't mess with it.
Sent from my Nexus 7 using xda premium
nooomoto said:
Why would you flash a recovery for a different device and expect it to work?
When ROM manger is supported on your device its a great tool, like on the sgs2. If its not officilially supported on your device, don't mess with it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
it was new on there at the time and with gsm next to i i figured it was for ours, anyway point is if i knew it wasnt for my phone i wouldnt have flashed it.
rob219 said:
it was new on there at the time and with gsm next to i i figured it was for ours, anyway point is if i knew it wasnt for my phone i wouldnt have flashed it.
Click to expand...
Click to collapse
in fact, it is not really that hard to fix. Just re-lock the phone via fastboot. then run RUU package from AT&T
It should set every thing back to original.
if your phone is not respond RUU, try reboot on RUU via fastboot.
By the way, The only recovery that works now is TWRP
Use this one only
sugeraddict said:
in fact, it is not really that hard to fix. Just re-lock the phone via fastboot. then run RUU package from AT&T
It should set every thing back to original.
if your phone is not respond RUU, try reboot on RUU via fastboot.
By the way, The only recovery that works now is TWRP
Use this one only
Click to expand...
Click to collapse
The ruu has to access the boot loader to verify your version. If you end up flashing a device and it writes certain partitions of your boot loader (ICJ).... Well your left with a permabrick, until someone finds a way to JTAG the One X(AT&T). I've heard that its already been done, but the person who has performed it has kept the pinout secret.
I'm not entirely sure which partitions your ROM manager has wrote to, if you can find that out you might be able to fix it... Depending on which ones have been written too.
Sent from my One X using xda app-developers app
Zombie thread alert!
Like many of us have said before. We are not the one x. We are the one XL.
Sent from my One X using xda app-developers app
_MetalHead_ said:
Nobody should ever use ROM Manager for anything, EVER.
Sorry for your loss.
Click to expand...
Click to collapse
Sorry, but I disagree!
I've had more problem locating backup files and restoring when in TWRP, than ROM manager!
Mike
MaverickCoast said:
Sorry, but I disagree!
I've had more problem locating backup files and restoring when in TWRP, than ROM manager!
Mike
Click to expand...
Click to collapse
You must be doing something wrong then. You don't even need to locate backups with TWRP, they're found automatically. Anyway, was it really necessary to revive an 18 month old thread just to say that?
Sent from my Evita
So My phone is constantly freezing and rebooting in apps every 5-15 minutes and I am going to try going back to stock and seeing if this occurs. My question is do i have to wipe my current rom? Or do i only have to fastboot oem lock and run ruu? Help would be appreciated. Think it is getting worse..
WhatTheAndroid? said:
So My phone is constantly freezing and rebooting in apps every 5-15 minutes and I am going to try going back to stock and seeing if this occurs. My question is do i have to wipe my current rom? Or do i only have to fastboot oem lock and run ruu? Help would be appreciated.
Click to expand...
Click to collapse
Yes, just run fastbook oem lock and then run the ruu. Make sure that you have the latest drivers from HTC (use htc sync if you can). Good luck!
For ruu grab the appropriate one .... Relock your bl like you Saud and run the ruu from you bl mode ...no need to wipe anything the ruu will do that for you
Skeeterdrums said:
Yes, just run fastbook oem lock and then run the ruu. Make sure that you have the latest drivers from HTC (use htc sync if you can). Good luck!
Click to expand...
Click to collapse
and i run the command in fastboot on my htc one x? ive did it once before.
WhatTheAndroid? said:
and i run the command in fastboot on my htc one x? ive did it once before.
Click to expand...
Click to collapse
Yessir head over to gunnymans thread in general forum to clear any confusion that remains
phone is going haywire.....Not being detected..rebooting every second..cant even get into an app...got into twrp and going to charge it ill 70 and restore to a better backup then hopefully ruu...thanks for the help
WhatTheAndroid? said:
phone is going haywire.....Not being detected..rebooting every second..cant even get into an app...got into twrp and going to charge it ill 70 and restore to a better backup then hopefully ruu...thanks for the help
Click to expand...
Click to collapse
Usually, the phone doesn't get detected if the drivers aren't up to date. Is it rebooting even from bootloader? You should be able to install everything from there, hopefully meaning restarts aren't an issue.
HTC One X using CleanRom 5.1 with BeastKernel 4.4
Skeeterdrums said:
Usually, the phone doesn't get detected if the drivers aren't up to date. Is it rebooting even from bootloader? You should be able to install everything from there, hopefully meaning restarts aren't an issue.
HTC One X using CleanRom 5.1 with BeastKernel 4.4
Click to expand...
Click to collapse
finally got it recognized and successfully ruu'd.It was very odd, like the phone was progressively getting worse for some reason.i am not not getting rebooted on stock rooted so it had to do something with my settings on the rom..like i said i under clocked and overclocked it, hot rebooted it, wiped cashe and dalvik...nothing was working and it finally just kept rebooting and freezing at home screen..Maybe a bad successful flash lol.. im not really sure.. or flashing over a bad flash had something to do with it..I might wait till jellybean comes out.
Have you tried to simply factory reset?
i personally like ruu'ing. i should do the same soon just to clean house. in the end it's pretty easy to get fluent on this phone.
i would say immediately after unlocking bootloader to ruu. i noticed some differences in the 1.85 to 2.20 ota vs the 2.20 ruu. it will also clean up any mess that might of been left on the phone. im also pretty ocpd =)
also htc sync imo is useless, i just use the standalone htc drivers haven't had any issues with them.
OP... What rom/kernel combo were you running?
Only time I've seen another phone go that nuts is when my cousin flashed rohans kernel in viper lol
Sent from my One X using Tapatalk 2
InflatedTitan said:
OP... What rom/kernel combo were you running?
Only time I've seen another phone go that nuts is when my cousin flashed rohans kernel in viper lol
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Viper and beastmode. My phone was going nuts....froze at the start screen 3 times and reset it self into a bootloop, then went back to freezing when start screen appeared..one of the times all I could see is the notification bar but I couldn't drag it Down. Lots of other crazy stuff happened on it as well...to much to tell. But I heard cleanrom is pretty stable, do I have to wipe stock rooted(no custom Rom yet) trying to find a good one and do I have to flash boot IMG if I'm on 1.14 or is it Included in the cleanrom installer? Might try elemental with cleanrom..see how that works out.
So I've been more of a stalker of the XDA community for a while, never really needed to ask a question because I usually find the answers on the boards pretty handily or by some fluke things work for me without the need to post anything. But now that time has come to an end.
I had Jellybam 4.1.2 on my device flashed with whatever kernel came with it, and when my battery died yesterday the phone was stuck in a boot loop. Keep in mind that prior to that 1) It had never done this on a reboot and 2) the correct kernel had been flashed via fastboot. My hboot is 1.14. The reason I'm not posting this question in the Jellybam post in android development is because 1) I'm a n00b to posting on here and 2) this is now happening with any other rom I install (most recent is MIUI which I flashed late last night, started up normally, then got caught in a boot loop on a reboot).
I follow the normal steps of going into TWRP, flashing cache/davlik, factory wipe, system wipe, then installing, doing the gapps if necessary, or following the instructions on any aroma installers, then rebooting into fastboot and flashing the kernel so i don't get boot loops on the initial start up. I'm also doing this on a mac, but the command lines in terminal are pretty straight forward and i'm just doing normal ADB / fastboot commands.
I'm perplexed now and I can't figure out what changed or what I did differently that's causing this. Any help would be most appreciated and I apologize if this is somehow a cross or repeat post, but I couldn't find much like it.
Do you have an Evita or Endeavour phone?
Sent from my HTC One XL using xda premium
It sounds like you are doing everything correct. Also seems like you have a good grasp of what to do. My thought is even if your initial install went though. Something in the bootimg may be corrupt. Perhaps try redownloading your preferred rom? And try again.
Sent from my One X using xda premium
ToxicWaste said:
Do you have an Evita or Endeavour phone?
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Evita
subarudroid said:
It sounds like you are doing everything correct. Also seems like you have a good grasp of what to do. My thought is even if your initial install went though. Something in the bootimg may be corrupt. Perhaps try redownloading your preferred rom? And try again.
Sent from my One X using xda premium
Click to expand...
Click to collapse
I've tried a couple times with the same result. I'll try again and see if anything different happens. Maybe just by some miracle I'll get it working again
I'm not sure how it works with safari for Mac. I do know that when I download ROMs with crome it some how downloads corrupt zips. On ei9 it works fine.
Sent from my One X using xda premium
uncledoobie said:
So I've been more of a stalker of the XDA community for a while, never really needed to ask a question because I usually find the answers on the boards pretty handily or by some fluke things work for me without the need to post anything. But now that time has come to an end.
I had Jellybam 4.1.2 on my device flashed with whatever kernel came with it, and when my battery died yesterday the phone was stuck in a boot loop. Keep in mind that prior to that 1) It had never done this on a reboot and 2) the correct kernel had been flashed via fastboot. My hboot is 1.14. The reason I'm not posting this question in the Jellybam post in android development is because 1) I'm a n00b to posting on here and 2) this is now happening with any other rom I install (most recent is MIUI which I flashed late last night, started up normally, then got caught in a boot loop on a reboot).
I follow the normal steps of going into TWRP, flashing cache/davlik, factory wipe, system wipe, then installing, doing the gapps if necessary, or following the instructions on any aroma installers, then rebooting into fastboot and flashing the kernel so i don't get boot loops on the initial start up. I'm also doing this on a mac, but the command lines in terminal are pretty straight forward and i'm just doing normal ADB / fastboot commands.
I'm perplexed now and I can't figure out what changed or what I did differently that's causing this. Any help would be most appreciated and I apologize if this is somehow a cross or repeat post, but I couldn't find much like it.
Click to expand...
Click to collapse
My phone did this once too. Never figured out why but the way I stopped it was to nandroid data, then wipe everything, reinstall the Rom and restore only data. After this it never bootlooped again.
Sent from my Venom1 XL using Xparent Red Tapatalk 2
ImagioX1 said:
My phone did this once too. Never figured out why but the way I stopped it was to nandroid data, then wipe everything, reinstall the Rom and restore only data. After this it never bootlooped again.
Sent from my Venom1 XL using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
Ok, I'll give that a shot. I installed CleanRom 5.1 today, ran some reboots and that seemed to clear it up. It might be a Jellybean thing, but who knows. Thanks for all the suggestions and quick responses!
Oh yea there is some discussion about a Rev-a or rev-b that is on your box having issues with 4.2 jb not working. I think its rev-b that everyone is having issues with.
Sent from my One X using xda premium
I decided to try out PACman rom just to see the features and to see if it was for me or not. After playing with it, I decided to go back to ViperXL.
I went into recovery and flashed backup that I had saved. Phone went into boot loop. I thought well let me try this again and got the same result. After a few minutes of trouble shooting, I realized one important thing. Recovery will not hold the boot image. I flashed the boot image for Viper and phone was just as I left it. Hope this information keeps someone from making this mistake.
AT&T HTC OneX
Android 4.1.1
ViperXL
Not sure what the issue for you is. I just tried out aznrice2k4's preview ROM based on 4.22 and restored back to ViperXL with no issues.
http://forum.xda-developers.com/showpost.php?p=38227428&postcount=363
when i make backups i usually only backup data since it only takes a few moments to flash the actually rom, so i fastboot boot.img if needed, then wipe everything, reflash rom then restore data. works everytime.
i wonder if twrp backups of boot from viperxl work on everyones phone or just their own? viperxl is the rom that autogens the boot.img correct?
954wrecker said:
Not sure what the issue for you is. I just tried out aznrice2k4's preview ROM based on 4.22 and restored back to ViperXL with no issues.
http://forum.xda-developers.com/showpost.php?p=38227428&postcount=363
Click to expand...
Click to collapse
I have know idea either lol. But flashing the boot image fixed it. Just thought it would be helpful if someone else has the same problem.
AT&T HTC OneX
Android 4.1.1
ViperXL
The older version of viper did autogen. The latest one requires flash of boot image. I think I was flashing recovery on top of Pacman kernel but I'm not sure. Flashing the viper image fixed the problem and all data was intact.
Sent from my HTC One XL using xda premium
Its hard to keep track of who is and isn't s-off now, but if you aren't you should try it, maybe that will help you.
Thanks but I am not going there. I have seen way to many issues. Not advanced enough to try it. Out of my comfort zone.
Sent from my HTC One XL using xda premium
Venomtester said:
Thanks but I am not going there. I have seen way to many issues. Not advanced enough to try it. Out of my comfort zone.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Just so you know there are 100 people following the simple directions and getting S-OFF in 5 minutes for every 1 person that creates a thread asking for help.
I'll second that. I'm far from an expert and I achieved S-off easily.
Sent from my One X using Tapatalk 2
Venomtester said:
Thanks but I am not going there. I have seen way to many issues. Not advanced enough to try it. Out of my comfort zone.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
It's quite easy took me two minutes lol... I say go for it .just read the instructions it's very simple for being s off at least we don't have to do some wire trick
Don't be scared of S-Off. I'm new to all of this and I thought it was easier than rooting the phone. Your probably already familiar with most of the steps to it
Okay I did it. Reluctantly I might add but very simple. Thanks to all of you.
AT&T HTC OneX
Android 4.1.1
ViperXL
Welcome to the club
I've got an AT&T HTC One, I rooted it and installed TWRP and haven't had the down time to do much else with it, including installing a rom yet.
I don't mind the oem ATT rom but I do need the Hotspot feature to work for my wifi tablet.
I've tried to turn on the hotspot feature with a couple scripts I've found on XDA but none of them seem to work so I've come to the conclusion that I'm going to have to change rom to be able to use the hotspot so this morning I Downloaded CM10 and placed it on the "SDcard" of my phone. I then tried to install it with TWRP. everything goes well half way through the install and then it hangs up about 60% through, it eventually seems to time out after like 15-20 minutes of not doing anything.
I then reboot it and all I get is an infinite animated CM boot logo.... I let it sit for an hour just to make sure it wasn't just a slow install.
I reinstalled it three times and the outcome was the same each time so I tried to ADB sideload it with the same outcome.
I even went on CM's site and downloaded another copy of CM10 but it made no difference.
I ended up having to reinstall the backup I made prior to starting this so I had my phone as I needed to go run some errands.
Does anyone know why I had the issues I was having with installing CM10?
Something I did wrong? How do I get CM to install?
Thanks
jessepatty said:
I've got an AT&T HTC One, I rooted it and installed TWRP and haven't had the down time to do much else with it, including installing a rom yet.
I don't mind the oem ATT rom but I do need the Hotspot feature to work for my wifi tablet.
I've tried to turn on the hotspot feature with a couple scripts I've found on XDA but none of them seem to work so I've come to the conclusion that I'm going to have to change rom to be able to use the hotspot so this morning I Downloaded CM10 and placed it on the "SDcard" of my phone. I then tried to install it with TWRP. everything goes well half way through the install and then it hangs up about 60% through, it eventually seems to time out after like 15-20 minutes of not doing anything.
I then reboot it and all I get is an infinite animated CM boot logo.... I let it sit for an hour just to make sure it wasn't just a slow install.
I reinstalled it three times and the outcome was the same each time so I tried to ADB sideload it with the same outcome.
I even went on CM's site and downloaded another copy of CM10 but it made no difference.
I ended up having to reinstall the backup I made prior to starting this so I had my phone as I needed to go run some errands.
Does anyone know why I had the issues I was having with installing CM10?
Something I did wrong? How do I get CM to install?
Thanks
Click to expand...
Click to collapse
What hboot? You may have to flash boot image separately in adb or s-off.
Venomtester said:
What hboot? You may have to flash boot image separately in adb or s-off.
Click to expand...
Click to collapse
1.14
I don't do much of this stuff so I am not entirely sure how to flash the boot image separately in adb.
I didn't think there was a way to s-off the HOX.
Thanks for the reply
jessepatty said:
1.14
I don't do much of this stuff so I am not entirely sure how to flash the boot image separately in adb.
I didn't think there was a way to s-off the HOX.
Thanks for the reply
Click to expand...
Click to collapse
On 1.14 the boot image needs to be flashed separately. Flash from fastboot..
Fastboot flash boot boot.img
The boot image is inside the Rom.zip your flashing. Keep a copy of the Rom on pc and extract files with winzip or whatever you like to use. But boot.img in adb folder and type the command, reboot and it should boot.
S-off can be done but only on a sense based Rom like viperXL.
Also read the stickies... They are there for a reason..
Sent from my HTC One X using xda app-developers app
This is not true. I s-off'd with cm10. Though you need to enable ADB root in settings for it to work.
Sent from my HTC One X using xda app-developers app
jessepatty said:
1.14
I don't do much of this stuff so I am not entirely sure how to flash the boot image separately in adb.
I didn't think there was a way to s-off the HOX.
Thanks for the reply
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2136172
exad said:
This is not true. I s-off'd with cm10. Though you need to enable ADB root in settings for it to work.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Well that explains why I was having issues on cm10.
Sent from my HTC One X using xda app-developers app
Make sure you're using the cm 10 for one xl (evita) and not the one x.
http://wiki.cyanogenmod.org/w/Evita_Info
I'll check out the links, thanks.
I can see allot has changed since December when I last messed with the phone. Back in December Clockwork recovery wasn't supported on the ATT version of the HOX. I see it now is in a touch version.
apparently I am doing something wrong as I keep getting the same indefinite CM boot logo and can't get past it. It appears I do not fully understand the process to side load the rom.
With that said, I restored it from a backup and I guess I'll just wait until I can confidently install a rom. This phone is so much different then my previous phones and tabs in regards to how it was unlocked and the install of different roms. I didn't have any problem figuring those out but this one has more steps involved which is aiding to my confusion. Maybe I'll find a step by step for my Hboot that I can follow, in the meantime I'll just keep having to look for free wifi for my tablet while I'm out and about.
You'd think there would be an easier way to enable the wifi hotspot on the phone.... LoL
Thanks for the info guys.....truly appreciated.
Try this...
http://code.google.com/p/android-wifi-tether/
Sent from my HTC One X using xda app-developers app