Hi, I recently purchased an HTC one X and I get a message with red letters saying "this build is for development purposes only do not distribute outside of htc", also my htc has been ramdomly rebooting, I want to go back to the stock ROM because I think I might have a custom one and that can be the cause of the random rebooting.
I have the 4.1 oficial firmware but I am affraid to flash it because my phone can become a brick.... The phone was rooted with SuperSU but I have uninstalled it and checked with titanium and I can no longer get superuser rights(I suppose I have succesfully unrooted my phone), I have also checked on bootlader and I have S-ON so I dont know if I am under conditions to flash the oficial firmware without risk(I dont want a brik). I want the original firmware because of the upcoming 4.2 and sense 5.0 update HTC will be releasing.
Thanks in advace for your help.
DillingerErick said:
Hi, I recently purchased an HTC one X and I get a message with red letters saying "this build is for development purposes only do not distribute outside of htc", also my htc has been ramdomly rebooting, I want to go back to the stock ROM because I think I might have a custom one and that can be the cause of the random rebooting.
I have the 4.1 oficial firmware but I am affraid to flash it because my phone can become a brick.... The phone was rooted with SuperSU but I have uninstalled it and checked with titanium and I can no longer get superuser rights(I suppose I have succesfully unrooted my phone), I have also checked on bootlader and I have S-ON so I dont know if I am under conditions to flash the oficial firmware without risk(I dont want a brik). I want the original firmware because of the upcoming 4.2 and sense 5.0 update HTC will be releasing.
Thanks in advace for your help.
Click to expand...
Click to collapse
Do s-off before you go stock or you will brick
Sent from my HTC One X using xda premium
Really just that?
31ken31 said:
Do s-off before you go stock or you will brick
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Is that all??? with S-OFF there is absolute no risk of briking??
Nonononono there's a tradeoff. Because once you supercid you brick if you ruu while s-on. So you need to s-off so as not to brick while RUUing. Technically because there are no longer security checks you have a greater amount of risk If you do something stupid.
Sent from my HTC One X using xda app-developers app
Just flash a stock rooted Rom would be my advice.. what are you gaining from ruu? Look at cleanrom, it's forsurely the most stable for this phone... Just my 2 cents cause if ya don't know what you're doing or are comfortable using adb odds are is you will booger up your new to you phone..
Sent from my HTC One X using xda premium
sinco54 said:
what are you gaining from ruu? Look at cleanrom, it's forsurely the most stable for this phone...
Click to expand...
Click to collapse
Updated firmware that is not part of the ROM. If you read the top post of CleanROM, its recommended to RUU first. Its not "required", but some folks have found it helpful to resolve some issues, like random reboots.
---------- Post added at 10:16 AM ---------- Previous post was at 10:13 AM ----------
DillingerErick said:
with S-OFF there is absolute no risk of briking??
Click to expand...
Click to collapse
Nothing you do to your phone can remove all risk of bricking when you flash. There is always a risk.
But if you have S-On and SuperCID, and try to install certain OTAs or RUUs, a brick is certain (known brick condition).
redpoint73 said:
Updated firmware that is not part of the ROM. If you read the top post of CleanROM, its recommended to RUU first. Its not "required", but some folks have found it helpful to resolve some issues, like random reboots.
---------- Post added at 10:16 AM ---------- Previous post was at 10:13 AM ----------
Nothing you do to your phone can remove all risk of bricking when you flash. There is always a risk.
But if you have S-On and SuperCID, and try to install certain OTAs or RUUs, a brick is certain (known brick condition).
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2181399
Maybe I'm mis reading it or not seeing where it says ruu is recommended..
If I've missed it my apologies but I hve never ruu'ed and I've flashed every available Rom more then once for this handset since last April...
Sent from my HTC One X using xda premium
sinco54 said:
http://forum.xda-developers.com/showthread.php?t=2181399
Maybe I'm mis reading it or not seeing where it says ruu is recommended..
Click to expand...
Click to collapse
You are confused about what CleanROM is. That is just the stock rooted ROM, not CleanROM.
This is CleanROM: http://forum.xda-developers.com/showthread.php?t=1655011
In the top post you will see under Installation: •Highly recomend lates Jellybean firmware and S-Off!
Scrosler doesn't explicitly say "RUU", but this is what he means.
redpoint73 said:
You are confused about what CleanROM is. That is just the stock rooted ROM, not CleanROM.
This is CleanROM: http://forum.xda-developers.com/showthread.php?t=1655011
In the top post you will see under Installation: •Highly recomend lates Jellybean firmware and S-Off!
Scrosler doesn't explicitly say "RUU", but this is what he means.
Click to expand...
Click to collapse
Oh ok, I didn't know that's what that meant lol, I thought it meant something entirely different. Thanks for clarifying for not only me but also the opie..
Sent from my HTC One X using xda premium
First TY all for the responses, Is not my first time flashing custom roms but this is my first HTC phone and I am a little confused with all the s-off and ruu stuff
That is my software info and I have S-on, also I have unrooted, the phone had supersu but no more, what else do I have to do and what Rom do you recomend???
I really want to be able to install oficial updates without trouble.
Sent from my HTC One X using xda app-developers app
you are currently on the latest software. I would recommend S-OFF if you plan to take official updates. If you're confused about terminology, there's a thread in my siganture "Are you ready to root?" That explains a lot of the terminology.
Sent from my Sony Tablet S using xda app-developers app
So I just need to s-off for oficial updates is that watt you are saying?? If so how can I s-off??
Sent from my HTC One X using xda app-developers app
There's a sticky in the android original dev section.
Sent from my HTC One X using xda app-developers app
DillingerErick said:
So I just need to s-off for oficial updates is that watt you are saying?? If so how can I s-off??
Click to expand...
Click to collapse
If you are S-on and SuperCID (which your phone likely is), and try to take the 3.18 Jellybean OTA, or run the 3.18 RUU, you will brick.
S-off will at least prevent bricking from this particular condition. The other option is change back to the AT&T CID.
Related
I am on my way to go and buy two At&t One x. They are currently still running 1.73 thankfully. Im not new to rooting or anything, just this device. My question is since its still on 1.73 should I unlock bootloader via HTC Dev, and will this mean i can always run a custom recovery and ROMS going forward?
Example: if bootloader is unlocked, can I then update a device to the most current (2.2 i believe) and still be able to have a custom recovery therefore run the ROM of my choice and even revert back to stock at will?
My goal is to keep it flexible and not lock myself out of an option because of an update. One of the devices is for my neice so I want her running stock for now, but would unlock the bootloader just as a safety net and to futureproof the device if we run some JB roms for her, or CM10. Any help would be greatly appreciate.
Im coming from a Nexus so Im not used to looking for exploits to run a ROM, well not since the EVO days. Thanks a plenty!
Honestly I wouldn't ever run the update on the phone. No reason to risk it as you can download the stock roms (or CleanROM) from the developers section and just flash it normally. This would be the most flexible.
Having said that, maybe someone else can chime in and answer your questions initial questions. I don't really know the answer.
Sent from my HTC One XL using xda app-developers app
Your lucky use one of the one click root methods there's some on xDA or some that I can givenu a link too.... Than go on to unlocked boot loader ...honestly of u want her to be stock put her on clean rom.
So you're saying I should root first and not use HTC boot loader unlock tool? I'm still trying to search for the answer to my questions as well. What's the best root method? I honestly would like to have a custom recovery, unlocked boot loader, and running stock 4.0.4 or better just to try it out first. Then find a good Rom . Any suggestions?
Sent from my HTC One X using Tapatalk 2
TheIowaKid said:
So you're saying I should root first and not use HTC boot loader unlock tool? I'm still trying to search for the answer to my questions as well. What's the best root method? I honestly would like to have a custom recovery, unlocked boot loader, and running stock 4.0.4 or better just to try it out first. Then find a good Rom . Any suggestions?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I would unlock your boot loader. Flash teamwin recovery project, and then flash a STOCK ROOTED rom, whether it be sense or cleanrom. This will remove the ota feature so you don't accidentally update your hboot
Using the HTC boot loader unlock method is fine, if you don't mind your warranty being void. If not try the manual version. All of these tutorials are available in the android development section.
Once your boot loader is unlocked you are good to go. Just DO NOT RUU to 2.20 or you will not be able to flash kernels and radios.
Sent from my One X using xda app-developers app
So even with an unlocked boot loader if I ota to 2.2 I'm screwed? Got it. So any suggestion on the best stock ROM and then a Jelly Bean ROM? Do the one click root methods work the best?
Sent from my HTC One X using Tapatalk 2
TheIowaKid said:
So even with an unlocked boot loader if I ota to 2.2 I'm screwed? Got it. So any suggestion on the best stock ROM and then a Jelly Bean ROM? Do the one click root methods work the best?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I was able to one click mine, however some users report they cannot use the one click method, but manual works for them.
Yes, never ruu to 2.20, even with an unlocked boot loader it will screw you over. If you ruu to 2.20 without supercid then you are just Sol completely.
As for stock ROMs, go try out Team Venoms ViperXL. Make sure you download "HTC One XL" and not "HTC One X" they are 2 different phones and flashing anything made for the One X will brick your One XL.
When it comes to jellybean, I am on MIUI because I like the iOS aspect of it. I still am a fan of Cyanogenmod, since that was the first aftermarket firmware I have used. So I would recommend CM10 unless you want a little more customization, then go with AOKP. I have never tried paranoid android, but it is a combination of CM10 and tablet display modes.
The One XL is codenamed "Evita" and the One X is codenamed "endeavour"
Sent from my One X using xda app-developers app
Are these ROMs fully functioning? Camera is important for me. I thought that CM10 wasn't quite there yet but I'm definitely going to check some of these out. I don't have a computer here so I can't do anything yet. Its killing me! Thanks again for all the suggestions, Ill take all the help I can get!
Sent from my HTC One X using Tapatalk 2
TheIowaKid said:
Are these ROMs fully functioning? Camera is important for me. I thought that CM10 wasn't quite there yet but I'm definitely going to check some of these out. I don't have a computer here so I can't do anything yet. Its killing me! Thanks again for all the suggestions, Ill take all the help I can get!
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Many of the sense ROMs are flawless.
The AOSP (Jellybean) ROMs are pretty stable, and camera does work on them.
CM10 is still in Nightly, but I think it'll be reaching a stable build soon.
absolutelygrim said:
As for stock ROMs, go try out Team Venoms ViperXL.
Click to expand...
Click to collapse
With a huge amount of awesome mods and customization options, I do not consider ViperXL to be a "stock ROM". Sense based, yes.
If the OP wants to stay strictly stock, there are flashable, pre-rooted versions of the most of the stock AT&T firmware versions.
But I think your point is a good one, that some of the custom ROMs build off of stock, while adding some optimizations and useful features, while keeping the stability of a stock ROM.
---------- Post added at 09:52 AM ---------- Previous post was at 09:43 AM ----------
TheIowaKid said:
So even with an unlocked boot loader if I ota to 2.2 I'm screwed?
Click to expand...
Click to collapse
The 2.20 hboot plugs the whole by which kernels and radios can be flashed via recovery. So flashing the kernel/boot.img requires flashing separately using adb every time you flash a ROM. Not sure about radios.
Really, there is no benefit to updating officially either by RUU or OTA. You gain nothing, and lose ability to flash kernel and radios via recovery.
Be sure to check out the index of all the resources (sticky at the top of the Development forum): http://forum.xda-developers.com/showthread.php?t=1671237
redpoint73 said:
With a huge amount of awesome mods and customization options, I do not consider ViperXL to be a "stock ROM". Sense based, yes.
If the OP wants to stay strictly stock, there are flashable, pre-rooted versions of the most of the stock AT&T firmware versions.
But I think your point is a good one, that some of the custom ROMs build off of stock, while adding some optimizations and useful features, while keeping the stability of a stock ROM.
---------- Post added at 09:52 AM ---------- Previous post was at 09:43 AM ----------
The 2.20 hboot plugs the whole by which kernels and radios can be flashed via recovery. So flashing the kernel/boot.img requires flashing separately using adb every time you flash a ROM. Not sure about radios.
Really, there is no benefit to updating officially either by RUU or OTA. You gain nothing, and lose ability to flash kernel and radios via recovery.
Be sure to check out the index of all the resources (sticky at the top of the Development forum): http://forum.xda-developers.com/showthread.php?t=1671237
Click to expand...
Click to collapse
Heh, I meant stock as in "sense based"
You know what I meant (I hope),
But he might not have, thanks for pointing that out
Sent from my One X using xda app-developers app
Yeah I knew what you meant! Like I said, not new to rooting and ROMs just knew to this device. Thanks again for the heads up on that thread. I'm going ROM crazy tonight once I root.
Sent from my HTC One X using Tapatalk 2
As said before - root, unlock bl, flash recovery and flash a rom, be it stock rooted or custom.
Don't update to 2.20 OTA.
Quick question but maybe off topic. Is the screenshot to MMS problem fixed with custom ROMs? I noticed that if I send a screen shot via MMS its so small the recipient can't see it. Maybe a bug just on 1.73? Annoying none the less!
Sent from my HTC One X using Tapatalk 2
TheIowaKid said:
Quick question but maybe off topic. Is the screenshot to MMS problem fixed with custom ROMs? I noticed that if I send a screen shot via MMS its so small the recipient can't see it. Maybe a bug just on 1.73? Annoying none the less!
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Can't answer that.. I can't send or receive MMS even though I have service and 4G LTE
But I don't think its an issue on AOSP
Sent from my One X using xda app-developers app
Sounds more like an APN issue in your case. I'd double check your APN or even delete and set it up again.
Sent from my HTC One X using Tapatalk 2
Does anybody have AT&T stock 2.20 nandroid backup? I'm trying to make my phone complete stock for a reason. I cannot flash RUU, because previously I flashed Asian 2.42 RUU, and that's why its not letting me to downgrade even with super cid. Backup would be appreciated if anybody can provide it.
Thanks in advance.
Sent from my HTC One XL using xda premium
Nandroid is not going to return you to stock like an RUU would. You would still be rooted and have custom recovery.
What you are asking for would not really have any different result than flashing a stock rooted ROM, so you can do that, if you just want to get the ROM back to stock.
redpoint73 said:
Nandroid is not going to return you to stock like an RUU would. You would still be rooted and have custom recovery.
What you are asking for would not really have any different result than flashing a stock rooted ROM, so you can do that, if you just want to get the ROM back to stock.
Click to expand...
Click to collapse
To be more specific, I want complete stock, non rooted, odexed and with AT&T bloatware backup, that some people my have as a backup.
Sent from my HTC One XL using xda premium
kaiser347 said:
To be more specific, I want complete stock, non rooted, odexed and with AT&T bloatware backup, that some people my have as a backup.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
No one is going to give you their nandroid, since that would have all their personal settings and Google password.
The 2.20 AT&T RUU should work. Are you sure you've got HTC sync installed?
iElvis said:
No one is going to give you their nandroid, since that would have all their personal settings and Google password.
The 2.20 AT&T RUU should work. Are you sure you've got HTC sync installed?
Click to expand...
Click to collapse
I'm not noob, and I pretty sure know how to run RUU. I have all the drivers installed. And currently running JB custom ROM on 2.42 ICS firmware with 1.14 bootloader. I can not run AT&T 2.20 RUU, because I will getting bootloader error. You will have same problem if you run different region RUUs with newer firmware. I don't want personal information. Some people may have clean stock nandroid without any personal stuff.
I had the same problem with my ONE S and there were people who had such nandroids, and they did help me with it.
That's why we call it community. We try to help each other as much as we can.
Sent from my HTC One XL using xda premium
kaiser347 said:
I'm not noob, and I pretty sure know how to run RUU. I have all the drivers installed.
Click to expand...
Click to collapse
Relax man. He's asking for the easy stuff first, since the best solution is very often the easiest one. Better to ask the seemingly 'obvious' question right off the bat, rather than go down some complicated road needlessly.
Re-installing HTC Sync fixes up the issue for the huge majority of people with RUU errors. Not in your case, as you are correct that trying to run the RUU with a lower hboot version number that what is already installed, will cause it to fail. But he is just trying to be helpful.
redpoint73 said:
Relax man. He's asking for the easy stuff first, since the best solution is very often the easiest one. Better to ask the seemingly 'obvious' question right off the bat, rather than go down some complicated road needlessly.
Re-installing HTC Sync fixes up the issue for the huge majority of people with RUU errors. Not in your case, as you are correct that trying to run the RUU with a lower hboot version number that what is already installed, will cause it to fail. But he is just trying to be helpful.
Click to expand...
Click to collapse
I'm relaxed, thank you for understanding me. The reason for this request is that there might be, and its might be an update from At&t in a future eventually. I'm just trying to be prepared for this, because I can not run 2.20 RUU and the only way to get this future update would be from a system setting. I like clean stock, rooted Rom with all the unneeded apps uninstalled. Once I got the update I can just unlock the bootloader and root it and install insecure kernel along.
Sent from my HTC One XL using xda premium
Here is a ruu link, hope it helps
http://forum.xda-developers.com/showthread.php?t=1671237
Sent from my HTC One XL using xda premium
I didnt't realize 2.42 contained an updated hboot. That would obviously prevent running an earlier ruu. Sorry for the confusion.
iElvis said:
I didnt't realize 2.42 contained an updated hboot. That would obviously prevent running an earlier ruu. Sorry for the confusion.
Click to expand...
Click to collapse
It seems hboot is the same 1.14 in both 2.20 and 2.42 RUUs. I think with the latter some other partitions were updated as well, which prevent downgrading.
Sent from my HTC One XL using xda premium
DESERT.TECH said:
Here is a ruu link, hope it helps
http://forum.xda-developers.com/showthread.php?t=1671237
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Thank you for the link. I do have a RUU. But can not install.
Sent from my HTC One XL using xda premium
I've been looking and have found that there is no RUU for the 3.17 Telus update, only OTA zips.
I would like to upgrade my phone to the newest firmware, and then re-unlock, and restore my rom from a nandroid backup.
Is there anyway that I can do this? Should I run the AT&T RUU and then proceed to unlock the normal way?
I am s-off before anyone yells at me.
What I did is ruu to ics, then check for updates. I have seen some 3.17 ota repack downloads but I prefer direct from the source.
Then installed twrp 2.3.x then downgraded touchscreen firmware to run AOSP. Though you don't need to do that unless you want to run AOSP.
Telus sucks at releasing RUUs, but the network here isn't as Saturated as some of the other guys
Sent from my One X using xda app-developers app
exad said:
What I did is ruu to ics, then check for updates. I have seen some 3.17 ota repack downloads but I prefer direct from the source.
Then installed twrp 2.3.x then downgraded touchscreen firmware to run AOSP. Though you don't need to do that unless you want to run AOSP.
Telus sucks at releasing RUUs, but the network here isn't as Saturated as some of the other guys
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Ya that was my next option, just wanted to see if anyone had the RUU hiding somewhere. I don't run AOSP but I'll probably downgrade just in case I want to try a rom on the fly sometime
exad said:
What I did is ruu to ics, then check for updates. I have seen some 3.17 ota repack downloads but I prefer direct from the source.
Then installed twrp 2.3.x then downgraded touchscreen firmware to run AOSP. Though you don't need to do that unless you want to run AOSP.
Telus sucks at releasing RUUs, but the network here isn't as Saturated as some of the other guys
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I forgot to add, there is no need to re-unlock as there's no need to re-lock to RUU with S-OFF. Just keep it unlocked and then flash TWRP after. nice and easy. (I have done this myself so I am 100% positive)
---------- Post added at 08:15 AM ---------- Previous post was at 08:12 AM ----------
area51avenger said:
Ya that was my next option, just wanted to see if anyone had the RUU hiding somewhere. I don't run AOSP but I'll probably downgrade just in case I want to try a rom on the fly sometime
Click to expand...
Click to collapse
I too searched high and low for the RUU. No such luck. Btw, it says your S-OFF in your signature lol
area51avenger said:
I've been looking and have found that there is no RUU for the 3.17 Telus update, only OTA zips.
I would like to upgrade my phone to the newest firmware, and then re-unlock, and restore my rom from a nandroid backup.
Is there anyway that I can do this? Should I run the AT&T RUU and then proceed to unlock the normal way?
I am s-off before anyone yells at me.
Click to expand...
Click to collapse
Nevermind
Sent from my Elemental Venomized S-off HTC One XL
I am having trouble connecting to Wifi since I've started using 4.2.2 roms. There was no trouble when I was using a 4.2.1 rom. My wifi switch will not move to on. When you click it, it says turning on wifi but nothing happens.
I am currently using [Official PACman All-in-1-ROM Ver. 22.0.1[4-3-13] .
I have Hboot 1.14, S-On. Do I need to have S-Off to connect to Wifi?
Thanks
Anybody have an idea of what's wrong? I'm running Rohan's test kernel C
I'm not sure how to fix it, my fiance's phone has the same problem. I can tell you that having s-off won't fix it though, that merely turns security checks off, it's completely unrelated.
Sent from my One XL using XDA Premium
You have to flash boot.img through fast boot
Sent from my HTC One X using xda app-developers app
You probably need to update your firmware to JB. There is a conflict between ICS firmware and the JB base that can cause your wifi to go haywire.
You do need to be s-off first, however, or you may get a brick running the RUU.
Megadoug13 said:
You have to flash boot.img through fast boot
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
i always do "fastboot flash boot boot.img", not working.
iElvis said:
You probably need to update your firmware to JB. There is a conflict between ICS firmware and the JB base that can cause your wifi to go haywire.
You do need to be s-off first, however, or you may get a brick running the RUU.
Click to expand...
Click to collapse
how can i go about upgrading the firmware?
zooobair said:
how can i go about upgrading the firmware?
Click to expand...
Click to collapse
Run the 3.17 (non-US) or 3.18 RUU (AT&T), depending on what phone you've got. You need to be s-off first or you may brick if you are supercid. You'll lose root, but getting it back is just a matter of pushing custom recovery back on and flashing superuser. You'll also need to downgrade your touchscreen firmware to use an AOSP rom; there's a thread in the Original Development forum on how to do it.
I'm not guaranteeing this will solve the problem, but I was having similar issues and this solved it.
iElvis said:
Run the 3.17 (non-US) or 3.18 RUU (AT&T), depending on what phone you've got. You need to be s-off first or you may brick if you are supercid. You'll lose root, but getting it back is just a matter of pushing custom recovery back on and flashing superuser. You'll also need to downgrade your touchscreen firmware to use an AOSP rom; there's a thread in the Original Development forum on how to do it.
I'm not guaranteeing this will solve the problem, but I was having similar issues and this solved it.
Click to expand...
Click to collapse
i figured out getting s-off. so after i run the 3.18RUU, do i have to use the following root method?http://forum.xda-developers.com/showthread.php?t=2285086? Sorry if I'm asking so many questions, just a little confused.
No. You can just flash recovery after ruu. Then either flash a rom or flash superuser if you want to stay stock rooted.
Sent from my One X using xda app-developers app
Correct, once you're s-off, you can never permanently lose root. No need for any exploits as you'll always have the ability to push a custom recovery back on and flash what you like.
iElvis said:
Correct, once you're s-off, you can never permanently lose root. No need for any exploits as you'll always have the ability to push a custom recovery back on and flash what you like.
Click to expand...
Click to collapse
I've been thinking about RUU'ing and starting over. Been having wifi and connection problems in general. Seeing as im s-off, do i need to change my cid back before running the att RUU? I seem to remember there being a conflict when the JB ota came out.
venelar said:
I've been thinking about RUU'ing and starting over. Been having wifi and connection problems in general. Seeing as im s-off, do i need to change my cid back before running the att RUU? I seem to remember there being a conflict when the JB ota came out.
Click to expand...
Click to collapse
No need to change cid
Don't need to relock bootloader, change cid or anything else if your phone is s-off, to ruu.
Sent from my One X using xda app-developers app
ronnie498 said:
No need to change cid
Click to expand...
Click to collapse
exad said:
Don't need to relock bootloader, change cid or anything else if your phone is s-off, to ruu.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Word. Weekend project.
Thanks
so i did everything mentioned, put on the 3.18RUU, installed recovery, downgraded the touchscreen firmware, flashed new rom and kernel. still no wifi working. any other ideas guys?
Sounds like a hardware fault to me if the RUU didn't fix it unfortunately.
Sent from my One XL using XDA Premium
I would think so as well, but it is working fine for me if I use 4.2.1 roms. Do you think that's still the case?
Sent from my One X using xda app-developers app
If it's working PERFECTLY on 4.2.1 then I would say it's not a hardware issue. And I'd also say I'm completely stumped as to what's causing your problem.
Sent from my One XL using XDA Premium
Damn. It's definitely working ok on both the 3.18RUU and 4.1.2 rom. Not sure what other measures I can take to try to get it right.
Sent from my One X using xda app-developers app
Which 4.2.2 ROMs have you tried so far?
Sent from my One XL using XDA Premium
Can someone tell me the benifits of hboot 1.09... I am currently on 1.14 with s-on
Sent from my HTC One XL using xda app-developers app
With hboot 1.09 and S-on, boot.img is flashed automatically from recovery anytime you flash a ROM (does not need to be flashed using fastboot). Also, radios can be flashed from recovery.
Both are possible now (with any hboot) if you are s-off. So I'd recommend s-off.
Also, this should have been posted to the Q&A forum section. So I've reported to the mods to move it.
Moved to Q&A
Wait... So can I just install cm from their website? If I flash the boot.img?
Sent from my HTC One XL using xda app-developers app
ali.allana786 said:
Wait... So can I just install cm from their website? If I flash the boot.img?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Be careful what you install from cm site. There are roms that are for the international one x and if you flash those you will brick your device. Stay on this forum and scan original android development thread, that's where you will find the correct cm roms..
Sent from my HTC One XL using xda premium
31ken31 said:
Be careful what you install from cm site. There are roms that are for the international one x and if you flash those you will brick your device. Stay on this forum and scan original android development thread, that's where you will find the correct cm roms..
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Thanks, also, what are the benefits of S-off??
You can find the answer to that if you just read. Buuuuut, it removes security checks basically, so you can really flash anything to your device.
This means you can run any RUU (for this device) without having to relock the bootloader etc, it also means that people on hboot 2.14 are able to flash kernels in recovery instead of flashing boot.img through fastboot. Plus you can downgrade touchscreen firmware, remove red text from splash screen, and edit "tampered" flags within hboot I believe.
This also comes with risks though. Because there are no security checks, it's easier to brick if you flash something that is not intended for our device (ROM / RUU).
Sent from my HTC One XL using xda premium
timmaaa said:
You can find the answer to that if you just read. Buuuuut, it removes security checks basically, so you can really flash anything to your device.
This means you can run any RUU (for this device) without having to relock the bootloader etc, it also means that people on hboot 2.14 are able to flash kernels in recovery instead of flashing boot.img through fastboot. Plus you can downgrade touchscreen firmware, remove red text from splash screen, and edit "tampered" flags within hboot I believe.
This also comes with risks though. Because there are no security checks, it's easier to brick if you flash something that is not intended for our device (ROM / RUU).
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Why would you need to downstage the touch screen firmware ??!?
Sent from my One X using xda app-developers app
ali.allana786 said:
Why would you need to downstage the touch screen firmware ??!?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
If you want to flash aosp ROMs you need to. If you want to only use Sense ROMs you don't need to. I suggest doing just so you have that freedom in future.
Sent from my Evita
ali.allana786 said:
Wait... So can I just install cm from their website? If I flash the boot.img?
Click to expand...
Click to collapse
As mentioned, its best to stay on this forum, to be sure you don't flash something not intended for this device. Check out my Index thread for links to ROMs intended for our device: http://forum.xda-developers.com/showthread.php?t=1671237
---------- Post added at 10:00 AM ---------- Previous post was at 09:57 AM ----------
timmaaa said:
You can find the answer to that if you just read. Buuuuut, it removes security checks basically, so you can really flash anything to your device.
This means you can run any RUU (for this device) without having to relock the bootloader etc, it also means that people on hboot 2.14 are able to flash kernels in recovery instead of flashing boot.img through fastboot. Plus you can downgrade touchscreen firmware, remove red text from splash screen, and edit "tampered" flags within hboot I believe.
This also comes with risks though. Because there are no security checks, it's easier to brick if you flash something that is not intended for our device (ROM / RUU).
Click to expand...
Click to collapse
All true. Plus, there is some type of bug where if your phone is SuperCID and S-on, you can brick if you try to install official the JB OTA or RUU. S-off removed this particular risk factor.
---------- Post added at 10:03 AM ---------- Previous post was at 10:00 AM ----------
ali.allana786 said:
Why would you need to downstage the touch screen firmware ??!?
Click to expand...
Click to collapse
If you install the JB OTA or RUU, it will upgrade the touch panel firmware, which is not compatible with AOSP ROMs. The touch panel firmware is independent of hboot, ROM or radio. So only a JB RUU or OTA will give you the updated touch panel firmware.
So if you for some reason end up running the RUU or OTA, and end up with the newer touch panel firmware, and want to run AOSP ROMs, you need to downgrade the touch panel firmware (S-off required).