The wifi on my phone isnt working.
Wifi just shows an error, ive tried all the usuall fixes, but cant get it to work.
phone is rooted, but still locked.
Could be a problem with your router. Try resetting it
Usually a kernel issue, have you tried another kernel?
tomascus said:
Usually a kernel issue, have you tried another kernel?
Click to expand...
Click to collapse
stock kernel. still locked.
And i know its not a router issue.
the phone actually shows "error" when looking at wifi.
As in I can't even turn wifi out.
Really need help with this.
I'm eating through my data plan and dont have much left.
He's correct above, usually a kernel error, so since your locked on a stock rooted Rom the choice here is yours..
1. Unlock the bootloader, go thru the steps and flash a new Rom and see if the issue corrects....
2. Do a factory reset and see if the issue Is resolved, if not take it in for warranty repair or replacement.
Sent from my HTC One X+ p_type 0.91.0
18th.abn said:
He's correct above, usually a kernel error, so since your locked on a stock rooted Rom the choice here is yours..
1. Unlock the bootloader, go thru the steps and flash a new Rom and see if the issue corrects....
2. Do a factory reset and see if the issue Is resolved, if not take it in for warranty repair or replacement.
Sent from my HTC One X+ p_type 0.91.0
Click to expand...
Click to collapse
I believe i've done a factory reset since it happened and it didnt fix it.
The problem is that I rooted my phone and can't restore back to stock using the RUU because my bootloader was updated.
Look at your software version in settings>about phone..... There's a ruu for all software versions....download and run the one that corresponds to your current version
Sent from my HTC One X+ p_type 0.91.0
Did your wifi used to work? If it has never worked, could be a hardware issue too.
18th.abn said:
Look at your software version in settings>about phone..... There's a ruu for all software versions....download and run the one that corresponds to your current version
Sent from my HTC One X+ p_type 0.91.0
Click to expand...
Click to collapse
I'm on 1.73 still but my hboot was updated during a failed upate. so I can't flash the stock ruu without "hboot error" while flashing the ruu.
Flash 1.85 ruu, I would use that one preferably either way.......thing is 1.73 and 1.85 both have 1.09 Hboot, but I would try anyways or return it for warranty
Sent from my HTC One X+ p_type 0.91.0
18th.abn said:
Flash 1.85 ruu, I would use that one preferably either way.......thing is 1.73 and 1.85 both have 1.09 Hboot, but I would try anyways or return it for warranty
Sent from my HTC One X+ p_type 0.91.0
Click to expand...
Click to collapse
Thats what they want me to do.
Since i've rooted it and modified system files, im scared that they would charge me for a new phone.
There's nothing wrong with using 1.85 ruu....it is a official ruu available from HTC.
Sent from my HTC One X+ p_type 0.91.0
18th.abn said:
There's nothing wrong with using 1.85 ruu....it is a official ruu available from HTC.
Sent from my HTC One X+ p_type 0.91.0
Click to expand...
Click to collapse
So i could flash that without having my phone unlocked?
Yup, actually, if the bootloader is unlocked you need to relock it to run it. Then unlock again afterwards
Sent from my HTC One X+ p_type 0.91.0
18th.abn said:
Yup, actually, if the bootloader is unlocked you need to relock it to run it. Then unlock again afterwards
Sent from my HTC One X+ p_type 0.91.0
Click to expand...
Click to collapse
I'll try that.
thank you.
I manager to fix the wifi by updating to 1.94.
Although i was under the impression that I would get a feature that would allow me to change what the recent button did.
wifi error with viper xl 2.1.2
I'm a newbie that recently rooted the At&t One X on 2.20 firmware. I have twrp recovery 2.3.1 flashed and installed ViperXL 2.1.2 rom. After a few days I noticed that when I turn off wifi and attempt to turn it back on, it will not turn on and display an error. When I reboot, the phone would hang on a white screen until I force a shut down with the power and volume button. Once I turn the phone back on, the wifi works as normal.
Is this a kernel issue? If so, is there one recommended to work with ViperXL 2.1.2?
jzsqrd said:
I'm a newbie that recently rooted the At&t One X on 2.20 firmware. I have twrp recovery 2.3.1 flashed and installed ViperXL 2.1.2 rom. After a few days I noticed that when I turn off wifi and attempt to turn it back on, it will not turn on and display an error. When I reboot, the phone would hang on a white screen until I force a shut down with the power and volume button. Once I turn the phone back on, the wifi works as normal.
Is this a kernel issue? If so, is there one recommended to work with ViperXL 2.1.2?
Click to expand...
Click to collapse
try Elemental or Beastmode found in the android dev forum.
Do I install a custom kernal right on top of the rom via TWRP? Or do I need to do any wipes (factory reset, wipe cache, and wipe dalvik cache) first?
Related
I recently got the One X because I became to impatient for the One X+.
After flashing cm10 on it I decided to try and flash back to stock to see if i could return it to ATT because i was within 14 days.
I accidentally bricked my phone by deleting my system from the recovery and now I cant boot into recovery.
It turns on but goes as far as the "HTC quietly brilliant 'this build is for development purposes...'" screen and stops.
I can turn the phone off and on but it gets stuck at this screen.
I've tried button combos to get into recovery and I've tried adb and the one x tool kit.
I've also tried the recovery from the RUU OTA update but no dice.
Any way to fix this?
Ectosock said:
I recently got the One X because I became to impatient for the One X+.
After flashing cm10 on it I decided to try and flash back to stock to see if i could return it to ATT because i was within 14 days.
I accidentally bricked my phone by deleting my system from the recovery and now I cant boot into recovery.
It turns on but goes as far as the "HTC quietly brilliant 'this build is for development purposes...'" screen and stops.
I can turn the phone off and on but it gets stuck at this screen.
I've tried button combos to get into recovery and I've tried adb and the one x tool kit.
I've also tried the recovery from the RUU OTA update but no dice.
Any way to fix this?
Click to expand...
Click to collapse
Which ruu were you using?
Did you relock your boot loader before running ruu?
Sent from my One X using xda app-developers app
Myrder said:
Which ruu were you using?
Did you relock your boot loader before running ruu?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I used "htc_one_x_RUU_2.20.502.7_att_us_08022012" to revert back to stock because i was originally on 2.20.
I did not relock my boot loader before running RUU.
Ectosock said:
I used "htc_one_x_RUU_2.20.502.7_att_us_08022012" to revert back to stock because i was originally on 2.20.
I did not relock my boot loader before running RUU.
Click to expand...
Click to collapse
There is your problem.
Fastboot oem lock
Type that into your fastboot cmd window to ruu
Sent from my One X using xda app-developers app
Myrder said:
There is your problem.
Fastboot oem lock
Type that into your fastboot cmd window to ruu
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
still no dice
error: device not found or < waiting for device >
One thing though is the phone shows up in my device manager as Android but is an unknown and does not have the drivers.
I have the usb drivers, and android SDK installed so I dont know what drivers it is missing.
Okay I can get into the bootloader but im still getting no ADB connection
[EDIT]
from the bootloader i went into fastboot USB and relocked the bootloader
RUU is running!
Ectosock said:
Okay I can get into the bootloader but im still getting no ADB connection
[EDIT]
from the bootloader i went into fastboot USB and relocked the bootloader
RUU is running!
Click to expand...
Click to collapse
Glad you're back up and running.
I wonder if att will even take back his phone because of the relocked status, why do you want the one x + so much? You just said you couldn't wait so you tampered with it and changed your mind, but I mean the one x + is only a second faster.. you can just overclock HTC one x anyways. But I'm glad you phone is back.
Keep the Xl.
WR
Sent from my HTC One X
WhatTheAndroid? said:
I wonder if att will even take back his phone because of the relocked status, why do you want the one x + so much? You just said you couldn't wait so you tampered with it and changed your mind, but I mean the one x + is only a second faster.. you can just overclock HTC one x anyways. But I'm glad you phone is back.
Click to expand...
Click to collapse
WarRaven said:
Keep the Xl.
WR
Sent from my HTC One X
Click to expand...
Click to collapse
64gb plus better battery is enough for me to switch.
Also can the store employees actually tell if it was bootloader tampered? The last time I traded in my stock flashed Samsung Captivate for return all they did was a factory reset and took it back.
Though, better battery life is questionable.
WR
Sent from my HTC One X
They can just go into fastboot if they wanted to and just deny your return. I doubt they will do that. Although it would suck if the phone malfunctions on the next person and he returns it back to att and I guess that would be suspicious but I think your fine. I guess more space is nice on a phone but I don't think I have used that much space on my laptop haha, mabye 50 gigs of bloatware and some music and some fps games. I was just wondering why the switch. Oh and did the ruu go as planned? Oh and also if you decide to get insurance for your phone you should think about squaretrade...they protect against a lot..drops spills..and if you factory reset to stock Rom they will fix it even though you may have rooted..and they will pay you the no commitment price if they can't fix it.(drops,spills,etc)
Here in Los Angeles and surrounding cities the ATT reps are now trained to get into the boot loader to check for a tampered and unlocked device. A few months ago they were not but many devices have come back where someone screwed it up and returned it.
WhatTheAndroid? said:
They can just go into fastboot if they wanted to and just deny your return. I doubt they will do that. Although it would suck if the phone malfunctions on the next person and he returns it back to att and I guess that would be suspicious but I think your fine. I guess more space is nice on a phone but I don't think I have used that much space on my laptop haha, mabye 50 gigs of bloatware and some music and some fps games. I was just wondering why the switch. Oh and did the ruu go as planned? Oh and also if you decide to get insurance for your phone you should think about squaretrade...they protect against a lot..drops spills..and if you factory reset to stock Rom they will fix it even though you may have rooted..and they will pay you the no commitment price if they can't fix it.(drops,spills,etc)
Click to expand...
Click to collapse
The RUU worked perfectly and I returned it with no hassle; they didn't even factory reset it in front of me.
I now have the One X+ and I'm glad i switched. It runs so well I don't think I'll need a custom rom for a while.
I've been using Hassoon2000's All in one toolkit. I successfully unlocked the boot loader. I was going to install Cyanogenmod 10. I copied the boot.img into the kernals folder for the AIO toolkit. I flashed that and that's where it went south. My phone continuously rebooted at the HTC bootup screen.
After some reading I have "relocked" the bootloader. I attempted to flash what I thought was the stock RUU. I can get into fast boot, but not the recovery. ( I was using the TWRP recovery that came with the tool kit). If I try to choose factory reset, it acts like it's flashing my phone (gray screen with a progress bar, but then goes back into fastboot after about 30sec.)
Am I SOL? I'm willing to compensate via pay pal if we get this thing going. If not, I did find a site call JTag brick repair.
When you flashed the kernel, did you install the actual Rom? If your phone can turn on, its not bricked. Which ruu did you download? Why isn't it working?
Sent from my HTC One XL using xda app-developers app
area51avenger said:
When you flashed the kernel, did you install the actual Rom? If your phone can turn on, its not bricked. Which ruu did you download? Why isn't it working?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I found an ruu after some googling. I perhaps didn't get the right one. No I didn't install the rom after I flashed the kernel. I flashed the kernel first, then I was going to boot into the recovery to install the rom. The phone just hung at the HTC screen before going into recovery. In red letters it says: This build is for development purposes only... etc"
Did you hold volume down and power at the same time to boot into recovery? Also make sure you get the right ruu. Which carrier are you on and what firmware were you before you flashed? The ruu is an exe you run from your desktop while your phone is in fastboot
Sent from my HTC One XL using xda app-developers app
Here's where I'm currently at. I have the bootload unlocked again through the toolkit. I also have the TWRP installed. I CAN get into TWRP.
I have AT&T, I'll do some searching on trying to find an RUU.
Hboot-1.14.0002
Radio-0.19as.32.09.11_2
openDSP-v29.1.0.45.0622
Awesome. Now mount USB storage in twrp and plug it in to your computer. If windows asks you to format. Say yes and format fat32. Copy the cm10.zip file to your sd card. Install from twrp. You may have to flash the boot.img again in fastboot.
Sent from my HTC One XL using xda app-developers app
I get an E:Error in sdcard/cm10.zip (Status 7)
Error flashing zip
Updating partition details...
I did do a factory reset and wipe cache.
Is it the right cm10 for HTC evita
omario8484 said:
Is it the right cm10 for HTC evita
Click to expand...
Click to collapse
I'm doing endevarou. I have the HTC One X, not the XL.
You have the one xl if you have the dual core att evita. if you have the quad core international one x then it's the endeavor.
Sent from my HTC One XL
deathbyenduser said:
I'm doing endevarou. I have the HTC One X, not the XL.
Click to expand...
Click to collapse
If so, then you are in the wrong forum, and if you used the toolkit from this forum, it also explains why you are stuck in the state you are. This forum is for the Evita. Are you sure you have the quad core Tegra3 version? What carrier is your phone from?
Also, if you can get into hboot, you are nowhere near bricked. Any type of power on (even just hboot) is not that hard to recover from. The only real brick is if the screen doesn't come on at all, and no charge LED when plugged to charger. Even then, the phone can sometimes be unbricked in Linux.
redpoint73 said:
If so, then you are in the wrong forum, and if you used the toolkit from this forum, it also explains why you are stuck in the state you are. This forum is for the Evita. Are you sure you have the quad core Tegra3 version? What carrier is your phone from?
Also, if you can get into hboot, you are nowhere near bricked. Any type of power on (even just hboot) is not that hard to recover from. The only real brick is if the screen doesn't come on at all, and no charge LED when plugged to charger. Even then, the phone can sometimes be unbricked in Linux.
Click to expand...
Click to collapse
Okay. I have the One XL for LTE. I was thinking the XL meant the bigger HTC One X that was out.
deathbyenduser said:
I'm doing endevarou. I have the HTC One X, not the XL.
Click to expand...
Click to collapse
deathbyenduser said:
Okay. I have the One XL for LTE. I was thinking the XL meant the bigger HTC One X that was out.
Click to expand...
Click to collapse
Really?! You my friend should not be flashing, rooting, unlocking bootloaders until you know the process and you can do it without reading how to do so. Learn how to swim before you jump into the deep end.
This is my third my root. I had the OG Motorola Droid and HTC Sensation with Tmobile. Now this One X LTE.
I can see why you said that though. I made an honest mistake. Looking back at the HTC models what I meant to say for some stupid reason I thought the HTC One X + (new one for att) was actually the HTC One XL. So I confused myself, flashed the wrong kernel. Luckily with some confirmation from you guys I'm back on the road. My phone is working.
My phone is working with CM10. I just need to get a compatible version of Gapps on. I'll be sending someone beer money. :victory:
deathbyenduser said:
This is my third my root. I had the OG Motorola Droid and HTC Sensation with Tmobile. Now this One X LTE.
I can see why you said that though. I made an honest mistake. Looking back at the HTC models what I meant to say for some stupid reason I thought the HTC One X + (new one for att) was actually the HTC One XL. So I confused myself, flashed the wrong kernel. Luckily with some confirmation from you guys I'm back on the road. My phone is working.
My phone is working with CM10. I just need to get a compatible version of Gapps on. I'll be sending someone beer money. :victory:
Click to expand...
Click to collapse
Great to hear.
You are very lucky you didn't do it the other way around (flash an endeavor rom on an evita device), as you would be the proud owner of a very expensive paperweight.
HTC can get stuffed for naming 3 different phones almost exactly the same One X/ One XL (or AT&T One X) / One X+. It is a minefield for people new to the phone.
Regardless of how many phones you've rooted, its pretty clear that you didn't do the enough reading to know the difference between the X, XL, and X+, and to know what you own. As already mentioned, you're lucky you didn't brick.
Only flash things from our forum, and you'll be safe: http://forum.xda-developers.com/forumdisplay.php?f=1538
I messed something up while trying to install ROM so I was playing around with it to see if I could fix it. When I try to reboot TWRP says "No OS install do you wish to reboot". Phone is screwed any suggestions on how to fix?
I'm facing a similar problem I believe:
On my HTC One X I successfully unlocked bootloader and then flashed a custom recovery TWRP 2.4.1.0 using the HTC One X All in One Kit. I then tried to install the latest version of Viper XL. When the installation started I got an assert message, something like this:
assert failed: getprop("ro.product.device")=="endeavoru" ||
getprop("ro.build.product")=="endeavoru" ||
getprop("ro.product.board")=="endeavoru" ||
Afterwards my phone went into the infinite reboot cycle and I've been unable to even make it to bootloader by holding down the power and volume keys until my hands went numb. No luck, still rebooting loop to the HTC home screen.
My carrier is AT&T if that matters.
Have I bricked it? Is there a way out of this? Any help at all would be greatly appreciated!
tfig88 said:
I messed something up while trying to install ROM so I was playing around with it to see if I could fix it. When I try to reboot TWRP says "No OS install do you wish to reboot". Phone is screwed any suggestions on how to fix?
Click to expand...
Click to collapse
Download a rom. Mount usb from within twrp. copy rom. flash rom.
Sent from my One X using xda app-developers app
zkuzmanic said:
I'm facing a similar problem I believe:
On my HTC One X I successfully unlocked bootloader and then flashed a custom recovery TWRP 2.4.1.0 using the HTC One X All in One Kit. I then tried to install the latest version of Viper XL. When the installation started I got an assert message, something like this:
assert failed: getprop("ro.product.device")=="endeavoru" ||
getprop("ro.build.product")=="endeavoru" ||
getprop("ro.product.board")=="endeavoru" ||
Afterwards my phone went into the infinite reboot cycle and I've been unable to even make it to bootloader by holding down the power and volume keys until my hands went numb. No luck, still rebooting loop to the HTC home screen.
My carrier is AT&T if that matters.
Have I bricked it? Is there a way out of this? Any help at all would be greatly appreciated!
Click to expand...
Click to collapse
Quad core or dual core. Just because you have an att sim doesn't mean you have an att one x
Sent from my HTC One XL
You tried to flash a Rom for the international version (endevoru) luckily that dev put in asserts so it didn't flash and didn't brick your device. Your phone is att version (evita) only flash things in these forums
Sent from my VENOMized HoxL
tfig88 said:
I messed something up while trying to install ROM so I was playing around with it to see if I could fix it. When I try to reboot TWRP says "No OS install do you wish to reboot". Phone is screwed any suggestions on how to fix?
Click to expand...
Click to collapse
If you can boot into recovery, then you should be fine. Just mount USB and copy ROM for evita into your sdcard, then flash it.
area51avenger said:
You tried to flash a Rom for the international version (endevoru) luckily that dev put in asserts so it didn't flash and didn't brick your device. Your phone is att version (evita) only flash things in these forums
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
That sounds likely, but then what do I do to break the reboot cycle?
954wrecker said:
Quad core or dual core. Just because you have an att sim doesn't mean you have an att one x
Sent from my HTC One XL
Click to expand...
Click to collapse
I'm not sure how I could tell. It has At&t printed on the One X at the top.
You have the att dual core so just find a Rom in this forum and you won't see that endeavor error
Sent from my HTC One XL
i have that same problem and did that but i didn't get a fix
cuteyr said:
i have that same problem and did that but i didn't get a fix
Click to expand...
Click to collapse
Did you flash boot image seperately? Hboot 1.14?
AT&T HTC OneX
Android 4.1.1
ViperXL
cuteyr said:
i have that same problem and did that but i didn't get a fix
Click to expand...
Click to collapse
this is nothing like your problem, this person tried to flash a rom for the endeavor you just need to flash a rom in the first place cause you wiped your phone and didnt flash a rom. all you need to go is go to recovery flash a rom and fastboot boot.img if you arent s-off.
DvineLord said:
this is nothing like your problem, this person tried to flash a rom for the endeavor you just need to flash a rom in the first place cause you wiped your phone and didnt flash a rom. all you need to go is go to recovery flash a rom and fastboot boot.img if you arent s-off.
Click to expand...
Click to collapse
Man is he sneaky. he is all over the place.
AT&T HTC OneX
Android 4.1.1
ViperXL
How many more times are people going to flash the wrong rom because of the crappy naming convention of this phone and the mislabeling of these forums. These forums should be called HTC one x evita!
OP, if all else fails.....flash a RUU to go back to stock
Sent from my One X using xda app-developers app
Palmetto_X said:
How many more times are people going to flash the wrong rom because of the crappy naming convention of this phone and the mislabeling of these forums. These forums should be called HTC one x evita!
OP, if all else fails.....flash a RUU to go back to stock
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I have to disagree. It says AT&T HTC One X. If the people would take the time to read and study what type of phone they have, they wouldn't have these kind of issues. They just go in, say "Oh man. That looks cool. I will flash that." Every rom I have seen on here tells you if it is for evita or states "International Only." Developers do not have the time to hold there hand and flash roms for them. They have jobs and do this work in their spare time for people who complain when it doesn't work. If you can't take the time to read and learn, stay with a stock phone or ask questions "before" you flash. I would be more than happy to show the links to the right steps. It's easier than trying to show them after the fact because they have know idea what they are doing in the first place. Everything you need to know is on this sight. I found it on my own. Don't be babies.
AT&T HTC OneX
Android 4.1.1
ViperXL
Actually, when I first bought my HTC One X I didn't know there were two different models and like always I rooted my phone and tried "ice cold jelly" and erased my whole OS after flashing the boot image (from image gui no less) and got stuck...that's how I discovered viper xl which is the best Rom in my opinion, but he may not be able to mount his SD card just in case Google HTC one X error ad card not mounted...team nocturnal has a fix
Sent from my HTC One X using xda premium
My one x is having major issues since i did the S-OFF. My battery percentage is stuck at 77% and will not change, if I try to use the phone (web browsing, looking at tapatalk) it gets real slow. I have tried going all the way back to stock AT&T rom, relocked bootloader and reinstalled everything to no avail. I am now on CM10.1. Please help me if you can.
jac0b said:
My one x is having major issues since i did the S-OFF. My battery percentage is stuck at 77% and will not change, if I try to use the phone (web browsing, looking at tapatalk) it gets real slow. I have tried going all the way back to stock AT&T rom, relocked bootloader and reinstalled everything to no avail. I am now on CM10.1. Please help me if you can.
Click to expand...
Click to collapse
Sounds like the ruu is not compatible with the rom.
AT&T HTC OneX
Android4.1.1
ViperXL
Venomtester said:
Sounds like the ruu is not compatible with the rom.
AT&T HTC OneX
Android4.1.1
ViperXL
Click to expand...
Click to collapse
What do mean by that?
jac0b said:
What do mean by that?
Click to expand...
Click to collapse
Don't worry about that I don't think he read through the whole post or maybe he misunderstood.... So this was once you did the s off...and it was persistent once you ruud back?
a box of kittens said:
Don't worry about that I don't think he read through the whole post or maybe he misunderstood.... So this was once you did the s off...and it was persistent once you ruud back?
Click to expand...
Click to collapse
Yep, i think since then. I did the S-OFF and then installed the Elemental 4.5 kernel on cleanrom and its been downhill since then.
Is it taking charge? Or does it still chill at 77? Maybe you could try going back to s on and see if the problem still persists...but I can't tell you how to turn the s on flag back on maybe grim knows or beaups.... Did you majorly undervolt? And you were on clean Rom jb right? I just can't think of why your phone is acting up and how it would be software
When you use an ruu to downgrade sometimes you can get the wrong radio version. Older or something to that effect.
Was just saying to try an update your radio version or check to make sure it is the latest one. Sorry.
Sent from my HTC One X using xda premium
Venomtester said:
When you use an ruu to downgrade sometimes you can get the wrong radio version. Older or something to that effect.
Was just saying to try an update your radio version or check to make sure it is the latest one. Sorry.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I went back via RUU to 2.20 but still have the same problem.
jac0b said:
I went back via RUU to 2.20 but still have the same problem.
Click to expand...
Click to collapse
Did you try Back up data, Wipe Cache, Dalvik Cache, and reset?
AT&T HTC OneX
Android 4.1.1
ViperXL
Venomtester said:
Did you try Back up data, Wipe Cache, Dalvik Cache, and reset?
Click to expand...
Click to collapse
RUU wipes everything. It rewrites recover, radio, all firmware components, and I think hboot. What you describe would not be any more of a reset than RUU.
The fact that the problem persists after RUU is a bit surprising, and troubling.
If not for the fact that the problem arouse right after S-Off, I would say it sounds like a failing battery.
Just seeing if refresh might help. Sounds like a dirty install but not sure.
Sent from my HTC One X using xda premium
Venomtester said:
Just seeing if refresh might help. Sounds like a dirty install but not sure.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
He ruud which wipes everything so a fresh install is out of question now
So he will have to revert back to stock?
Sent from my HTC One X using xda premium
Venomtester said:
So he will have to revert back to stock?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Hmm I feel your understanding of an ruu or maybe what did is a bit jarred
Ok so he s offed wasn't doing to well then he ran the ruu which wipes everything and brings your phone back to stock... Than he reunlocked and flashed another Rom and even onstock the problem was persistent
a box of kittens said:
Hmm I feel your understanding of an ruu or maybe what did is a bit jarred
Ok so he s offed wasn't doing to well then he ran the ruu which wipes everything and brings your phone back to stock... Than he reunlocked and flashed another Rom and even onstock the problem was persistent
Click to expand...
Click to collapse
So he downgraded then upgraded. Is he running a custom rom on a lower hboot version? I think s-off you can upgrade and downgrade. S-on you can only go up. Is this correct?
---------- Post added at 04:47 PM ---------- Previous post was at 04:23 PM ----------
Venomtester said:
So he downgraded then upgraded. Is he running a custom rom on a lower hboot version? I think s-off you can upgrade and downgrade. S-on you can only go up. Is this correct?
Click to expand...
Click to collapse
I apologize for any random comments made. I have reset my passwords to stop who ever it is that has been using my account for the past few days.
AT&T HTC OneX
Android 4.1.1
ViperXL 3.2.3
redpoint73 said:
RUU wipes everything. It rewrites recover, radio, all firmware components, and I think hboot. What you describe would not be any more of a reset than RUU.
The fact that the problem persists after RUU is a bit surprising, and troubling.
If not for the fact that the problem arouse right after S-Off, I would say it sounds like a failing battery.
Click to expand...
Click to collapse
A failing battery would cause slow response on the device also?
Yes I wiped everything when I RUU'd.
jac0b said:
A failing battery would cause slow response on the device also?
Yes I wiped everything when I RUU'd.
Click to expand...
Click to collapse
I don't know. RUU pretty much controls it all. Wifi, Camera, Battery etc. I don't think battery itself would cause that sluggish of a response.
AT&T HTC OneX
Android 4.1.1
ViperXL 3.2.3
Venomtester said:
I don't know. RUU pretty much controls it all. Wifi, Camera, Battery etc. I don't think battery itself would cause that sluggish of a response.
AT&T HTC OneX
Android 4.1.1
ViperXL 3.2.3
Click to expand...
Click to collapse
I also did brick my phone previously and was able to recover it using the unbrick tool.
jac0b said:
I also did brick my phone previously and was able to recover it using the unbrick tool.
Click to expand...
Click to collapse
All the problems started after you did a RUU restore?
AT&T HTC OneX
Android 4.1.1
ViperXL 3.2.3
Venomtester said:
All the problems started after you did a RUU restore?
AT&T HTC OneX
Android 4.1.1
ViperXL 3.2.3
Click to expand...
Click to collapse
I did the S-OFF then I installed the elemental kernel on cleanrom 3.17. Thats when I started to notice the phone was sluggish and the battery percentage was not moving from 77%. So I came home and restored my phone back to stock and still had the same issue.
So, I've been trying to use this method to root by AT&T HTC One X
http://forum.xda-developers.com/showthread.php?t=1644167
Attached is the software information of my phone...
I run the .bat file and everything works and my phone reboots three times but then I try to load SuperSU but it says su binary code not installed which leads me to believe that the phone isn't rooted?
Any advice on how to get it to work?
Cheers,
What Hboot version do you have? Go into boot loader by turning the phone off, hold the volume down button and press the power button. Let us know what it says?
Sent from my One X using xda premium
subarudroid said:
what hboot version do you have? Go into boot loader by turning the phone off, hold the volume down button and press the power button. Let us know what it says?
Sent from my one x using xda premium
Click to expand...
Click to collapse
hboot-2.14.000
Did you buy that phone second hand? Is the bootloader locked? Unlocked? Relocked? Does it say s-on? Or S-off?
Sent from my One X using xda app-developers app
No, I bought it new. Its locked and s-on
akaeavaian said:
No, I bought it new. Its locked and s-on
Click to expand...
Click to collapse
Well that's odd since you're software says 1.73 but your hboot is of 3.18.
Sent from my One X using xda app-developers app
nah hboot is 2.14
Post a photo of your bootloader screen, because what you're describing is virtually impossible.
The only way you could be on hboot 2.14 and 1.73 software is if you got a refurb that was previously on 2.20 or earlier, was rooted, unlocked, s-off, had the 3.18 ruu run, then the 1.73 stock rom installed, then relocked and s-on, and no one at AT&T bothered to clean up the mess.
iElvis said:
Post a photo of your bootloader screen, because what you're describing is virtually impossible.
The only way you could be on hboot 2.14 and 1.73 software is if you got a refurb that was previously on 2.20 or earlier, was rooted, unlocked, s-off, had the 3.18 ruu run, then the 1.73 stock rom installed, then relocked and s-on, and no one at AT&T bothered to clean up the mess.
Click to expand...
Click to collapse
Lmao that's sounds exactly like what would happen.
Sent from my One X using xda premium
That sounds complicated
but here you go...
Looks like youre going to have to wait. no exploit for att on that version. Pisses me off that Rogers can still unlock and s-off. I want to say horrible things about att. Can we turn this into a AT&T bashing thread now?
Sent from my One X using xda premium
subarudroid said:
Looks like youre going to have to wait. no exploit for att on that version. Pisses me off that Rogers can still unlock and s-off. I want to say horrible things about att. Can we turn this into a AT&T bashing thread now?
Sent from my One X using xda premium
Click to expand...
Click to collapse
can telestra too? telus can aswell.
Again another reason to bash AT&T
Sent from my One X using xda premium
akaeavaian said:
That sounds complicated
but here you go...
Click to expand...
Click to collapse
I'm sorry, even seeing it, I don't believe it. I just don't see how this could be possible.
In any case, the 1.73 root method might work, but with that hboot, you can't change cid, and thus can't unlock or flash a custom recovery, which means you can't get permanent root. You're stuck where you are, wherever that is.
They don't send ota's for the hboot right? I was on 2.20 few and 1.14 hboot. And got it refurb back in December
Sent from my Carbon-ize Evita using xda-developers app
Ota does affect the hboot... Yes. But there's not an Ota that changes just the hboot. This must have been previously rooted. Most likely this phone was at some point unlocked and rooted, the person who returned it most likely updated to 3.18 after bootloader unlock/soff, had issues, Relocked and s-on, ruu to 1.73, returned to HTC where HTC fixed and repackaged without updating the software.
*edit* sorry that makes no sense.. Ruu would have downgraded the hboot too.. Just woke up -_-
We may never know what happened to thus phone lol.
Sent from my One X using xda app-developers app
exad said:
Ota does affect the hboot... Yes. But there's not an Ota that changes just the hboot. This must have been previously rooted. Most likely this phone was at some point unlocked and rooted, the person who returned it most likely updated to 3.18 after bootloader unlock/soff, had issues, Relocked and s-on, ruu to 1.73, returned to HTC where HTC fixed and repackaged without updating the software.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Aha! So it couldn't have been new. Unless he had warranty. something isn't right.
Sent from my Carbon-ize Evita using xda-developers app
Yup, he's got an ICS Rom with a locked 2.14 hboot. Now that's f'd up.
exad said:
We may never know what happened to thus phone lol.
Click to expand...
Click to collapse
I think it's possible to get that configuration:
-phone was originally on ICS
-root, unlock, and s-off
-apply 3.17 or 3.18 ruu to get 2.14 hboot. This would also remove the TAMPERED flag
-flash rooted stock 1.73 rom
-edit p3 or flash scotty's zips to relock and restore LOCKED text
-remove root
-restore s-on
-return phone to AT&T
I just don't see why anyone would do it or how it would survive the refurb process.
soo...err....is there anything I can do? I got it through Costco though...if that changes anything...