Related
Boy oh boy, I had a really tough few days trying to flash a custom rom. I was pretty heavy into flashing roms from the G1 days until I got my sensation on the day it was released. I then took a long break. Well 2 days ago I decided to Unlock my Bootloader through the HTC website. Everything went well. I did notice the ******UNLOCKED****** in the bootloader I also noticed the S-ON(security was still on). I didn't think this mattered. Was I ever wrong. With that S-On you cannot flash new radio's. I have never been able to flash a PG58IMG.zip file from hboot/fastboot. I can however flash recovery's from fastboot using (fastboot flash recovery recovery.img).
Seems as if every single rom I tried needs the Security-OFF to work correctly. I was able to put clockwork mod 5.0 on my phone, and install super wipe, and several roms, the problem I ran into is I would get a error under the switch for wifi. Wifi would not work on any of the 5 roms I tried before this one. I was wanting to give up and go back to stock for several hours. I tried the RUU to bring me back to build 1.27 and build 1.29 both were unsuccessful. I was stuck at build 1.73.401.2 and no way possible to get back to stock. And picture this living in a area with tmobile that is still using the edge network(2 ****ing g) OMFG I was so mad trying to even boot a new rom without wifi is a nightmare, took me literally 20 minutes to download rom manager. Anyway's this rom was the last one I tried before busting my phone into pieces.
Rom's I tried:
1. Android Revolution 3.6.1, and 4.1 (3.6.1 booted but had no wifi)
2. RCMix 3.5 v04 (bootloop)
3. LeeDroid booted fine (no wifi)
4. I believe there was one other I tried. NO GO
5. Then I flashed this one late last night, and to my surprised it worked.
I was so happy I almost pissed myself.
Oh yeah I tried many irc channels, one was the revolutionary.io irc channel, I was able to successfully run the rev.io tool and it showed as a success however my S-was still ON. I talked to these guys for about 45 minutes looking for other ideas. They pretty much told me I was screwed and that it had never been tested after you unlocked through HTC. And it simply might never work.
Anyway I guess what I am getting at. For anyone else that might have to go through what I did.
1. How in the world can you get you phone back to complete stock?
2. Why is this happening?
3. Why is my wifi not working with any other rom? And everyone else's is?
4. How do I go about getting my S-OFF?
5. Does anyone know if you can RELOCK your bootloader through HTC so that I can turn the SECURITY-OFF and "then" unlock the bootloader.
I probably have more question's. I just wanted to see if I might be able to get a few answers from you fine people. Help me understand what in the world is going on and how many other people are dealing with what I am dealing with.
droiddv said:
Boy oh boy, I had a really tough few days trying to flash a custom rom. I was pretty heavy into flashing roms from the G1 days until I got my sensation on the day it was released. I then took a long break. Well 2 days ago I decided to Unlock my Bootloader through the HTC website. Everything went well. I did notice the ******UNLOCKED****** in the bootloader I also noticed the S-ON(security was still on). I didn't think this mattered. Was I ever wrong. With that S-On you cannot flash new radio's. I have never been able to flash a PG58IMG.zip file from hboot/fastboot. I can however flash recovery's from fastboot using (fastboot flash recovery recovery.img).
Seems as if every single rom I tried needs the Security-OFF to work correctly. I was able to put clockwork mod 5.0 on my phone, and install super wipe, and several roms, the problem I ran into is I would get a error under the switch for wifi. Wifi would not work on any of the 5 roms I tried before this one. I was wanting to give up and go back to stock for several hours. I tried the RUU to bring me back to build 1.27 and build 1.29 both were unsuccessful. I was stuck at build 1.73.401.2 and no way possible to get back to stock. And picture this living in a area with tmobile that is still using the edge network(2 ****ing g) OMFG I was so mad trying to even boot a new rom without wifi is a nightmare, took me literally 20 minutes to download rom manager. Anyway's this rom was the last one I tried before busting my phone into pieces.
Rom's I tried:
1. Android Revolution 3.6.1, and 4.1 (3.6.1 booted but had no wifi)
2. RCMix 3.5 v04 (bootloop)
3. LeeDroid booted fine (no wifi)
4. I believe there was one other I tried. NO GO
5. Then I flashed this one late last night, and to my surprised it worked.
I was so happy I almost pissed myself.
Oh yeah I tried many irc channels, one was the revolutionary.io irc channel, I was able to successfully run the rev.io tool and it showed as a success however my S-was still ON. I talked to these guys for about 45 minutes looking for other ideas. They pretty much told me I was screwed and that it had never been tested after you unlocked through HTC. And it simply might never work.
Anyway I guess what I am getting at. For anyone else that might have to go through what I did.
1. How in the world can you get you phone back to complete stock?
2. Why is this happening?
3. Why is my wifi not working with any other rom? And everyone else's is?
4. How do I go about getting my S-OFF?
5. Does anyone know if you can RELOCK your bootloader through HTC so that I can turn the SECURITY-OFF and "then" unlock the bootloader.
I probably have more question's. I just wanted to see if I might be able to get a few answers from you fine people. Help me understand what in the world is going on and how many other people are dealing with what I am dealing with.
Click to expand...
Click to collapse
Personally i would just do the normal s-off method as it gives you a little more freedom compared to HTC unlocking method.
My wifi is dead too, but i have no way of fixing it at all, i've got a thread called "wifi is dead" in the q+a section of the sensation forum.
Let me know if you get yours working, i imagine that if you revert your phone back to stock again and then use the alpha rev method that you will have better luck.
1. You can Relock your bootloader using HTC site but this time u will see Relocked instead of Locked
2. No idea
3. Did you try resetting your router? Works for me. Also try flashing a different radio.
4. No idea
5. You can relock bootloader on HTC site but have no idea of you can unlock it with Revolutionary again.
Try write secureflag command, just search for.the correct one on xda. Also, try flashing your RUU and then s-offing via revo.
Sent from my HTC Sensation Z710e using XDA App
tinky1 said:
Try write secureflag command, just search for.the correct one on xda. Also, try flashing your RUU and then s-offing via revo again. You might need eng s-off, pm EddyOS, he should be able to help, I believe he's done it before.
Sent from my HTC Sensation Z710e using XDA App
Click to expand...
Click to collapse
Sent from my HTC Sensation Z710e using XDA App
[ Solved ] WiFi error , Radio flash Problem , and revert back to any Custom Rom
droiddv said:
Well 2 days ago I decided to Unlock my Bootloader through the HTC website. Everything went well. I did notice the ******UNLOCKED****** in the bootloader I also noticed the S-ON (security was still on). I didn't think this mattered. Was I ever wrong. With that S-On you cannot flash new radio's. I have never been able to flash a PG58IMG.zip file from hboot/fastboot. I can however flash recovery's from fastboot using (fastboot flash recovery recovery.img).
Seems as if every single rom I tried needs the Security-OFF to work correctly. I was able to put clockwork mod 5.0 on my phone, and install super wipe, and several roms, the problem I ran into is I would get a error under the switch for wifi. Wifi would not work on any of the 5 roms I tried before this one. I was wanting to give up and go back to stock for several hours. I tried the RUU to bring me back to build 1.27 and build 1.29 both were unsuccessful. I was stuck at build 1.73.401.2 and no way possible to get back to stock.
Oh yeah I tried many irc channels, one was the revolutionary.io irc channel, I was able to successfully run the rev.io tool and it showed as a success however my S-was still ON. I talked to these guys for about 45 minutes looking for other ideas. They pretty much told me I was screwed and that it had never been tested after you unlocked through HTC. And it simply might never work.
5. Does anyone know if you can RELOCK your bootloader through HTC so that I can turn the SECURITY-OFF and "then" unlock the bootloader.
.
Click to expand...
Click to collapse
[Solved ] WiFi error , Flash Radio Problem , Install any Custom Rom without errors , Wrong S-on Brick
this is Solved and the wifi error is because of kernel included in Boot.img
you can use the following solution to install any custom rom without wifi errors
first read " how htc dev works " to have an understanding why this happened to you and why you are still S-on and why you can't flash Radio . link is here " Solve WiFi Errors , Radio Flashing Problem , Caused by htc Dev Unlock Method "
the solution itself is in the following link , Read title " Custom Rom Flash " and "[FONT="][ Implementation ][/FONT][FONT="] Successful S-OFF using my above method " . [/FONT]link is here " Successful S-OFF after brick (wrong S-ON) for ICS or GB , Downgrade OTA firmware "
this also solve wrong S-on Brick , hope that helps
Press the thanks Button for this Post
Hey guys,
There's a discussion going on one of the CleanROM threads, and since I'm still new to the Android world, I wanted to ask you guys what your experience was.
I flashed directly to the 1.85-based CleanROMs without ever updating via the 1.85 RUU, once the CleanROMs had been updated to allow this. Was this a mistake? Would it have made more sense to update to the official 1.85 RUU before flashing the ROM?
I'm trying to figure out if it's worth my time to go ahead and do that now, or if I should just wait for the next RUU leak and the next ROMs built around that base?
I'm thinking that if it isn't broke, I shouldn't fix it, but another part of me wants to make sure all my firmware is as up-to-date as possible, so I'd appreciate any feedback you guys could offer.
Thanks!
Silellak said:
Hey guys,
There's a discussion going on one of the CleanROM threads, and since I'm still new to the Android world, I wanted to ask you guys what your experience was.
I flashed directly to the 1.85-based CleanROMs without ever updating via the 1.85 RUU, once the CleanROMs had been updated to allow this. Was this a mistake? Would it have made more sense to update to the official 1.85 RUU before flashing the ROM?
I'm trying to figure out if it's worth my time to go ahead and do that now, or if I should just wait for the next RUU leak and the next ROMs built around that base?
I'm thinking that if it isn't broke, I shouldn't fix it, but another part of me wants to make sure all my firmware is as up-to-date as possible, so I'd appreciate any feedback you guys could offer.
Thanks!
Click to expand...
Click to collapse
I answered this in the ROM thread but I'll put it here in case anyone else is wondering.
Way way back (a month ago) to install a ROM you had to be on the base the ROM was based on. The reason for this is it was thought at the time that we couldn't flash boot.img, which is the kernel from recovery, beacuse we didn't have S-off. It has since been discovered that we can indeed flash boot.img from recovery, so now ROMS include it.
When you flash a ROM unless the dev says otherwise, you have to manually wipe /data with a factory wipe in recovery.
The reason for this I imagine is for people doing incremental upgrades between versions won't have to set everything up again since the Dev didn't write their install script to wipe /data.
The installer script takes care of everything else /system gets formatted, kernel gets installed and the ROM gets put on the phone.
The build version you see in /about/firmware is derived from whatever the Dev put in Build.prop, it's just a text string.
When you install a ROM there shouldn't be any remnants of your previous ROM except the Radio.
First android phone it's a AT&T One X, i'll be using it on the Bell network. Got a good deal on Kijiji and I didn't ask enough questions apparently, lol.
The phone is clearly not stock, took me several hours to piece that together. I get it, I'm a noob. I can tell it's running Cleanrom 4.5. I want to get it back to something close to stock. I plan to learn all about rooting/roms but I want to do it from a vanilla phone so that I get to actually do it myself.
I googled and found a tutorial (link). I deleted the 'su' file and superuser.apk. I followed the rest of the steps and it didn't seem to do anything, just rebooted back into cleanrom.
I kept googling and now I'm following this guide: http://forum.xda-developers.com/showthread.php?t=1859714
I guess i'm going to flash from an RUU now ? My CID is 11111111, so I've read that means I have superCID and any RUU will work. I want to get to JB eventually, so can I just flash direct to the Europe 3.14 JB from HTCRUU? Or go with one of the ICS versions?
Am I doing this right?
No no no!
Edit: still writing but wanted to say don't flash that ruu
If you want completely stock you need to use fast boot and boot into hboot and run fastboot OEM lock
(You may need to search around to learn how do that)
Then run this ruu. http://beta.androidfilehost.com/?fid=9390077933525139511
Sent from my One X using Tapatalk 2
that is for the wrong phone
only place you should look at is here AT&T, Rogers HTC One X, Telstra One XL
Its good your asking the questions now if you want to go completely stock run an ruu which means relicking the bootloader and running it ill link you to some guides in a sec
---------- Post added at 07:43 AM ---------- Previous post was at 07:43 AM ----------
Oh and like others said don't use that ruu! We have the one XL
cleanrom 4.5 is pretty good and close to stock but adds quick settings, debloated, power menu and some other tweaks. i would keep it how it is and just learn about how custom roms work. you can learn how to use twrp in its current state and maybe learn how to use some root apps.
just so you know your phone is the evita not the endeavoru.
Thanks for the replies.
I haven't tried flashing anything yet so don't worry. I'm taking it slow.
I've already been into fastboot. Figured that out because it was a required step in the guides I said I was trying to use. I have all the drivers installed and I'm able to talk to the phone via fastboot at the comand prompt.
LOL, thanks for letting me know my phone is Evita. I guess I can delete the 600mb RUU I downloaded
I'm a little unclear about HBOOT vs. fastboot. I can get into the bootloader and go to the fastboot USB mode... is this analogous to HBOOT?
So my steps right now are:
1) Download correct RUU, Evita 2.20 ICS - I've also seen people discussing 1.85 vs 2.20, why chose one over another?
2) fastboot oem lock
3) Install RUU while phone is in bootloader mode
That right?
I would strongly suggest to slow down, and learn more about what root is and means, before going back stock. Root is just a change in permissions. You gain absolutely nothing by unrooting, and lose quite a bit. You lose the ability to do all sorts of mods to your phone, flash custom ROMs, use apps that require root like Adaway and Titanium Backup (and many others), remove carrier bloatware, activate tethering, and much more.
People have gone through great pains to find root methods for our device (and other Android devices). Many come on here looking for these root methods, for the awesome benefits that root means. I've seen very few, if any, people before you that have said "crap I accidentally got a rooted device, and don't want root". Think about that one for a while.
Plus, CleanROM 4.5 is already based on a more updated firmware version than any of the official AT&T RUUs. Plus it includes a lot of cool features and optimizations. Again, going from CleanROM to stock is a step backwards, not forwards, and you are gaining nothing, and losing quite a bit. Another thing about CleanROM, is that it is devoid of the AT&T bloatware (and there is a lot). Keep in mind that on the stock AT&T ROM, the bloat is not removable without root, so you are stuck with quite a few crappy apps that you will never use. That alone is a huge reason to have a rooted device. Also bear in mind that stock AT&T does not allow tethering (unless you have a data plan that allows it) and has other stock HTC apps (like FM radio) disabled. These cannot be enabled unless you have root.
Another thing, is that you will not get Jellybean any faster on stock than rooted. While its true that rooted, this phone will not be able to take the OTA when it rolls out (hasn't happened yet). But a stock rooted JB firmware will almost certainly be posted here on XDA, that is safely flashable on a rooted device. This often happens within a couple days of the OTA starting to roll out, if not faster. Sometimes even before the OTA, as sometimes the official RUUs get leaked before the OTA. All it takes is for a dev to get his hands on the files, apply root, and upload it here. Learning how to flash such a file to your device is very simple. Not much more than: download the file to your phone, boot into recovery, and press "install". So yet again, stock gains nothing over being rooted.
While its true that root is not for everyone. But if you've already found this place, and learned what things like RUU, bootloader, and fastboot are, then you probably already know more than most folks do about Android. You may feel in over your head, but it really just takes a few hours of reading to learn the fundamentals. And with that knowledge, you can do so much more with your phone than you can without root.
redpoint73 said:
I would strongly suggest to slow down, and learn more about what root is and means, before going back stock. Root is just a change in permissions. You gain absolutely nothing by unrooting, and lose quite a bit....
Click to expand...
Click to collapse
I appreciate the advice, thanks. To be clear, eventually I will probably bring the device back to where it is now. I've used linux before so I have an understanding of the permissions system and the added benefits of root.
My goal here is to get the phone back to stock so that I can learn the rooting/flashing process from the start, not the end. I understand why that might seem counterintuitive but I'm a very hands on person and I'll learn more of the theory by walking through the process than reading about how somebody else hacked this device to get where it is now.
Sure I'm making extra work for myself but I know what im getting into.
Sent from my HTC One X using xda app-developers app
echoboomer said:
I appreciate the advice, thanks. To be clear, eventually I will probably bring the device back to where it is now. I've used linux before so I have an understanding of the permissions system and the added benefits of root.
My goal here is to get the phone back to stock so that I can learn the rooting/flashing process from the start, not the end. I understand why that might seem counterintuitive but I'm a very hands on person and I'll learn more of the theory by walking through the process than reading about how somebody else hacked this device to get where it is now.
Sure I'm making extra work for myself but I know what im getting into.
Click to expand...
Click to collapse
You should have said so from the start, then. This pretty much negates everything I just typed above.
Its admirable that you want to learn the process from scratch, and its the opposite attitude of most n00bs here.
My advice, as another mentioned above, is stick to XDA, and don't follow instructions from random Googled sites. Most of those sites don't clearly delineate between our phone (Snapdragon S4) and the international (Tegra3) version, and following instructions for the international version is a great way to brick your phone.
Other than that, lock the bootloader, run the RUU, and have fun. Also check your hboot version. If its anything but 1.14, don't run the 2.20 RUU. You will want the 1.73 or 1.85 RUU instead, as the 2.20 RUU will update the hboot to 1.14, which plugs the holes by which boot.img and radios can be flashed from recovery. Unless you want to create ever MORE work for yourself, as the hboot can be downgraded using a Linux computer, lol!
Be sure to check out my index thread, as most anything you will need is here: http://forum.xda-developers.com/showthread.php?t=1671237
Thanks, sounds like I'm on the right track.
Also check back to my OP, I did say that I wanted to learn the whole process but I wanted to do it from stock. sorry you typed all that out but in sure it will help some other noob down the line.
Last thing, 1.85 vs 2.20?
Sent from my HTC One X using xda app-developers app
ChummyDays said:
2.20 has the new hboot, and that means that you have to extract the boot.IMG out of the ROM and flash it through fast boot. With 1.85 you just flash the ROM.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Cool thanks, I found a tutorial last night on how to extract boot.IMG from the ruu exe. I think I'm good to go.
Sent from my HTC One X using xda app-developers app
You might be confused. You shouldn't have to pull a boot.img from an RUU typically, only from a custom ROM zip. And only if you are on boot 1.14.
Sent from my HTC One X using xda app-developers app
Probably confused. Here's what I see in the boot loader.
***
Tampered
Unlocked
Evita PVT Ship S-ON RL
HBOOT-1.09.0000
Radio-0.19as.32.09.09_L
OpenDSP-v28.1.0.32.0504
eMMC-boot
***
Sent from my HTC One X using xda app-developers app
echoboomer said:
HBOOT-1.09.0000
Click to expand...
Click to collapse
This is what you want to see, and why you need to be sure to use the 1.85 RUU.
I have a HTC one XL (s-on, hboot 1.14) with magio rom (4.2) installed. Suddenly my phone stopped getting a network signal. At first I thought its a hardware issue but then I found out it with the software plus its a common issue. Im not an experienced user.
So far I've found out the solutions are
1) Updating the firmware - I have no idea about this. Do I have to install the stock and root again? Is this installing the stock RUU? My CID is all ones, something like 1111111. Will I brick my phone? Do I have to install both th rom and firmware?
2) Beastmod - I feel dumb after reading this thread because it doesnt say what are the requirements to install this. Never installed a kernal before.
http://forum.xda-developers.com/showthread.php?t=2165880
3) Market app - network speed boost - I tried this, workd like a charm in the first.Sent a few texts but as soon as I made a call I lost the network
Due to my lack of knowledge on the subject I'm sacared to experiment because there is a chance of bricking the phone. I understand the issue is related with android 4.2 so a noob proof guide will help everyone who have the issue.
(example - http://forum.xda-developers.com/showthread.php?t=1787148)
kind regards
Whether you decide to update the firmware or install the Beastmode kernel, you will need s-off. You'll find the s-off thread here. You'll almost definitely need to change ROMs temporarily as it seems to be virtually impossible to achieve on a Sense 5 Android 4.2.2 ROM.
The kernel is s-on friendly but many people who are s-on have had trouble installing it. The 2.15 firmware can be found in the first post of this thread, along with instructions on how to flash it. It has nothing to do with returning to stock or RUUs and you don't need to modify your phone other than getting s-off first.
Sent from my Evita
dragz said:
So far I've found out the solutions are
1) Updating the firmware - I have no idea about this. Do I have to install the stock and root again? Is this installing the stock RUU? My CID is all ones, something like 1111111. Will I brick my phone? Do I have to install both th rom and firmware?
Click to expand...
Click to collapse
The firmware package being discussed (for resolving signal drop issues on Sense 5 ROMs) and linked by timmaaa above is not an RUU, but just the hboot, radio, boot.img, media and WiFi modules that came with the "official" Sense 5 OTA. It will only overwrite the modules I named, not the ROM. Nothing else needs to be done (you will still have your current ROM, root, etc.).
You must be s-off to install this.
timmaaa said:
Whether you decide to update the firmware or install the Beastmode kernel, you will need s-off. You'll find the s-off thread here. You'll almost definitely need to change ROMs temporarily as it seems to be virtually impossible to achieve on a Sense 5 Android 4.2.2 ROM.
The kernel is s-on friendly but many people who are s-on have had trouble installing it. The 2.15 firmware can be found in the first post of this thread, along with instructions on how to flash it. It has nothing to do with returning to stock or RUUs and you don't need to modify your phone other than getting s-off first.
Sent from my Evita
Click to expand...
Click to collapse
thank you, it worked
My request is very simple, but the story behind my phone might be lengthy. Here we go.
I bought a my HTC one x Evita on Amazon.com. The listing said it was new but it wasn't. How i got to know that when I tried to update the phone. I had considerable trouble doing so. Up to now I have not been able to do this.
I contacted xda- Developers.com and by providing details of the phone, they were able to identify that the phone wasn't new. The phone came with a h/boot of 0.08 very weird. I had extreme difficulty with flashing a custom ROM. But the good folks at xda got me thru again.
Here is my stress now. I tried to upgrade my phone using the latest RUU for it 3.18 after many tries. I will not install, kept failing saying cannot connect to phone try plugging phone back into PC, my but when I try it with RUU2.17 it works just fine so it's not the cable.
I got fed up with this, and decided to flash custom ROM.I flashed Viper XL with great success, then tried Cleanrom which is what I am currently on. By the way I have noticed something familiar with both Flashed Roms. They keep losing service and restarting the phone on its' own. Is this a h/boot issue or a Rom issue? Also I am thinking of installing the CM11 nightly ROM for my phone, please be reminded I am currently on H/Boot 1.14.
I tried flashing cm11 no success.
The signal drops and reboots (and the solution to those problems) have been mentioned literally dozens of times in both of those ROM threads. Please search properly before posting, it's rule #1 here on XDA.
The reason you can't flash cm11 is because your firmware is too old. I know you said the 3.18 RUU didn't work but that's what you need to do to flash any recent aosp ROM. The 4.4 ROMs also require a modify version of TWRP to flash.
Sent from my Evita.
timmaaa said:
The signal drops and reboots (and the solution to those problems) have been mentioned literally dozens of times in both of those ROM threads. Please search properly before posting, it's rule #1 here on XDA.
The reason you can't flash cm11 is because your firmware is too old. I know you said the 3.18 RUU didn't work but that's what you need to do to flash any recent aosp ROM. The 4.4 ROMs also require a modify version of TWRP to flash.
Sent from my Evita.
Click to expand...
Click to collapse
Thanks alot , great. Just one more question. I am supercid and s-off. Do I need to relock to boot-loader in order to run RUU3.18?
No you don't need to relock it.
Sent from my Evita.