I just rooted my new HTC EVO LTE phone recently because I had to get a new one. Any way, after rooting it, I imminently made a nandroid back up. Then I flashed a few different roms and recoverys. However, what I found out is after I flash a new rom, my wifi says error and won't turn on. I'm not sure what the problem is. And yes, I cleared everything out before flashing a new rom. However, what is even more interesting is I can use my recovery that I made after rooting my phone to go back to the stock rom and it has no trouble with the wifi. I'm not sure why I'm getting this error or how to fix it.
I've thought about flashing some new radios, but I've had issues in the past with this phone trying to make it S-Off, so as a result it is currently S-On. I would like it to be S-off, but after having a lot of experience with it, I've learned it is very time consuming to do and it is a pain to get it to work, it almost always bricks my phone and then I have to go unbrick it in Linux.
I'm planning on running through the rooting method again to see if that does anything, but I'm doubtful. I've also tried updating the prl, profile, firmware and HTC software with no luck. Let me know if anyone has any suggestions. Thanks.
NoClemency said:
I just rooted my new HTC EVO LTE phone recently because I had to get a new one. Any way, after rooting it, I imminently made a nandroid back up. Then I flashed a few different roms and recoverys. However, what I found out is after I flash a new rom, my wifi says error and won't turn on. I'm not sure what the problem is. And yes, I cleared everything out before flashing a new rom. However, what is even more interesting is I can use my recovery that I made after rooting my phone to go back to the stock rom and it has no trouble with the wifi. I'm not sure why I'm getting this error or how to fix it.
I've thought about flashing some new radios, but I've had issues in the past with this phone trying to make it S-Off, so as a result it is currently S-On. I would like it to be S-off, but after having a lot of experience with it, I've learned it is very time consuming to do and it is a pain to get it to work, it almost always bricks my phone and then I have to go unbrick it in Linux.
I'm planning on running through the rooting method again to see if that does anything, but I'm doubtful. I've also tried updating the prl, profile, firmware and HTC software with no luck. Let me know if anyone has any suggestions. Thanks.
Click to expand...
Click to collapse
S-OFF is really the way to go if it's still an option for you it's the only way to get the new firmware without relocking and taking the OTA then unlocking and rooting again read post 2 in the lazypanda thread found here http://forum.xda-developers.com/showthread.php?t=1737123 just go down the list and verify everything works before running lazypanda there are plenty of members that subscribe to that thread so there is plenty of help availiable
Also, rerooting won't do anything. You're already rooted? Think the problem is in the rom u installed. Possibly a bad download. Try downloading from a good connection and install it again. If it is close to stock like flex's stock w goodies just clear cache and dalvik in recovery.
And what do u mean u tried a few recoveries? Cwm doesnt work well with the evo LTE. Try twrp 2.2 and leave it alone until its updated again.
What is your hboot? What rom did you try flashing?
Sent from my lair.
Im also getting this issue and i know its not anything to do with rooting and all that since ive been rooted since i picked this up from best buy on preorder release day and ive been flashing and running the same rom and mods forever now also i was using wifi yesterday soooo yea lol
Recognized Hooker Killer
First, I don't believe I can make my phone S-off, because it has software version 2.13.651.1 710Rd on it and even though I do have a nandroid back on 1.13 hboot, for the default rom from a long time ago with my old HTC EVO LTE, I can't flash back a hboot to 1.13 so I believe I'm stuck S-On for now. Let me know if I'm wrong.
I've attempted several different roms including fresh rom 5.1.1, viper4G_1.0.0, and a jelly bean rom (cm-cfX-20120904-OFFICIAL-jewel all with the same problem. As for recoverys, I should have said I've tried restoring back to several different nandroid backups that I created in the past that were working just find with my old HTC EVO LTE.
Right now my phone is unlocked and rooted. I am running H Boot-1.19.000, I am S-On, and Radio-1.12.11.0809.
I know this problem has something to do with flashing new roms, because when I do a nandroid back up to the default rom, I don't have this problem, and the wifi is working great, I only have this problem if I try to flash any custom rom or use a nandroid backup that I made with my old HTC EVO LTE.
Again, this is not my first time around the track with an HTC EVO LTE, this just happens to be a new phone that I recently got from Sprint when they were thinking my dropped calls were caused by my phone when in fact they figured out they had a tower down. Since then, the tower is back up, so that is why I just rooted this new phone they gave me.
Let me know if you have any suggestions or if you need anymore information.
It's been while now, and I haven't gotten a real response back yet, and I was wondering if anyone knows anything that will help me out? Thanks.
Edit: Found out that I simply needed to flash the boot.img manually of what ever custom rom that I want to switch to in order to get around being S-On.
Please Help
NoClemency said:
It's been while now, and I haven't gotten a real response back yet, and I was wondering if anyone knows anything that will help me out? Thanks.
Edit: Found out that I simply needed to flash the boot.img manually of what ever custom rom that I want to switch to in order to get around being S-On.
Click to expand...
Click to collapse
Hey im having the same exact issue I however went back to my stock backup from right after I rooted. The issue I had was I flashed a CMX nightly. I had been running them fine and suddenly everything went haywire i was bootlooping but only after about 30 seconds after the rom would load up. I'd have just under a minute to fish around and the it would reboot again. it was in this short window that I saw the wifi error and that it would not connect to the sprint network at all for voice or data. Im S-On Hboot 1.15 Evo LTE. I used Flash GUI to go from Stock sense to CMX as im sure youve figured out you have to do. Since i had backups of previous CMX nightlies I tried to just restore But none of my nandroids would fix the looping issue I managed to flash the boot img from the CMX rom i was previously on through adb/fastboot and it took but still my device kept looping. Finally i found this http://forum.xda-developers.com/showthread.php?t=1917106 but I didn't have any Sense Based Roms only my Stock Nandroid back up. So i used the Boot Image Flasher Tool, it took, then Instead of rebooting the system I went straight to my custom recovery and restored my Stock Sense BackUp since the tool flashes the stock sense kernel. To my relief the phone booted right up no problem connected to the network and all but to my dissmay the wifi is STILL broken somehow it says error and will not switch on. Everything else seems to be working fine though. This is crucial there is no way I can go without wifi on my phone. I don't want to ruin anything further or permanitely but i do plan to move forward. My plan is to download a sense rom (MeanRom) which im doing now but it's taking forever on 3G. Wipe everything (using TWRP 2.2) Data Dav rom and use super wipe, and try to install MeanRom. If anyone has any other suggestions Im all ears. Also im alittle confused on the Hboot kernel limitations I know I have to use Flash GUI if Im going from a sense Rom to Aosp and vise versa but do I have to use it when say Going to a nandroid backup of a sense rom while currently on a Aosp rom because I couldnt find a boot.img file in my backup file when i used the tool to extract it. I hate S-On HTC really screwed us with this. And I hate my original evo which had S-Off for dying on me on the 15th day and me having to get this replacement with 1.15 im sorry guys I love this phone but it has become a nightmare and the Evo 3D was no walk in the park either. I apprectiate any comment from anyone this is the first time in almost 8 years of hacking I've been truely worried I may not be able to fix something.
Try this....had the same problem during one of my flashing sessions from rom to rom...this fixed it for me.
You also might want to try a different rom with its corresponding boot img. I'm currently running Venom rom with its boot img file and its working great. Right now, it sounds like your kernel is what is giving you problems like mine, so flashing the correct boot img should fix it.
vel7wil said:
Try this....had the same problem during one of my flashing sessions from rom to rom...this fixed it for me.
Click to expand...
Click to collapse
Thank you I'll be sure to try this out quick update, in TWRP recovery I had (force MD5 check on all zips?) checked now I don't remember checking it or if it came checked by default but as soon as I unchecked it I was able to run superwipe and flash MeanRom which both failed multiple times when it was checked on. Not sure if this was the cause of my problem but I agree I think I got a bad kernel in the CMX nightly. Either that or the Flash GUI app didnt exract the boot image properly. Either way I haven't been brave enough to try another AOSP rom man I hate having S-On my first Evo was perfect then I get stuck with this locked down replacement. One question though is that boot image for a stock/sense rom just wanna be sure.
vel7wil's advice worked for me I was having the same issue. Download the zip he recommends. Use flash image gui to flash the kernel and clear dalvik and cache. I just did a standard reboot after that and it said "android updating... apps x of xx" then everything was back to working.
Related
Hello all, I flashed thE Twisted Sence 1.5.1 ROM this afternoon and at about 8:30pm my phone completely froze and I could not do anything at all. Pulled the battery and all I can get is the HTC Logo on the White Background.
I can get into HBOOT and I have been trying everything I can to get the phone to work again but no dice.
Clockwork doesnt want to load for some reason but after letting my phone sit for about 15 minutes one time it did load into Clockwork. So I wiped the system partition/cache/dalvik and reloaded the ROM again.
After 12 minutes of waiting the phone finally started to load into the OS but it was so sloooooooowwwwww. It would not even recoginize any gestures on the touch screen.
So I rebooted again and it is stuck on the HTC Boot Screen again.
So I was thinking that I might be able to go back to the rooted stock so I went to http://forum.xda-developers.com/showthread.php?t=996616 and got the PG05IMG_stock.zip from there and renamed to PG05IMG.ZIP and had HBOOT load that.
Again went through a super long start up process and now the phone is at the unlock screen and again I cannot do anything at all. It has the correct time and it is only showing 1X for data nothing else and I am in a 4G LTE zone. I called myself from a landline and the phone rings but I cannot answer it since the touchscreen is un-responsive.
So is there any reason why my phone would be running super slow and doing what it is? I don't know if it is a Kernel thing or a Radio thing or what.
Maybe a stock kernel would help if anyone has it.
Any help would be much apperaicted as I have a brick that lights up basically. Phone isn't useable at all. =(
Reboot into recovery and try a different kernel. Or just restore an earlier state.
^_^_^'s tbolt
Load another ROM. Any rom you load should come with a new kernel. If that fails, try a different radio.
Sent from Phoenix, AZ running Thunderbolt rooted Das BAMF Remix 1.5
Does anyone know a way to go back to locked Stock through HBOOT or Clockwork without being able to boot the phone?
If I can get back to S-ON I will return the phone to Verizon since I am within my 30 days.
It has to be a kernel issue. The radio may be in conflict with something else, because all phones are different, but just restore a backup you've made, and try flashing the rom with a different kernel. If it was stable, something had to occur for that to change obviously.
If I had a backup to use then I would give that a shot. =( Shame on me I know.
webbyz said:
Does anyone know a way to go back to locked Stock through HBOOT or Clockwork without being able to boot the phone?
If I can get back to S-ON I will return the phone to Verizon since I am within my 30 days.
Click to expand...
Click to collapse
You can do it through ADB.
adb reboot recovery
now you know to make a nandroid backup prior to reflashing anything
/slaps OP with trout
I apologize in advance if this has been posted elsewhere. I've been looking everywhere I can possibly imagine for the past 3 hours trying to find a solution to no avail.
I'll get right to it. Whenever I try to turn on WI-FI or 4G, I get "Error". No description as to why, or what could be causing it, but heres what I've done.
I'm no noob when it comes to rooting. I had my original Evo rooted most of the time I had it with little to no problems. I've had the 3D since the day it came out, and I haven't felt the need to root. But I got to talking with my buddy earlier and decided I'm going to do it for the OC (and I gotta admit, Synergy looks pretty legit). I'm at hboot 1.5, so I went through the HTC unlock process, and the TWRP recovery process. Then I flashed Synergy, and I set it up, and I get this error.
So I try reflashing it, and that doesnt work. I'm thinking it could be the kernal. So i try 2-3 different kernals (listed on the Synergy thread), and I get the same error. I try a combination of different things for what seems like the next 10 hours (reality, it was about 2) and no matter what I try, I can not seem to get rid of this message. I clear all the cache/dalvik. Wipe back to factory. Hell, I even tried loading the stock ROM and this problem will not go away.
I have the PC86IMG ready to go about to flash back to stock and be done with this root process. The damage is done as far as warranties go, but I would really like to have something to show for it. Does anyone know a way to resolve this without reverting back to locked?
Did you flash the kernel via fastboot? If not the kernels don't flash with the 1.50 hboot, you need to grab the boot.img out of the rom zip and flash via fastboot. Check post 2 in the Synergy thread I believe there are detailed instructions there.
EDIT: Instructions are actually on post 2 of the Eternity thread.
Transformer Sent
Is it not possible to just flash using TWRP?
Edit: I did read that you would need to flash via Fastboot, but I thought that was just initially. So everytime I flash a ROM, I need to adb through fastboot?
That did it. Thanks so much! That was driving me crazy!
(made sure to click "thanks" too)
A couple weeks ago, I decided it was time to root my phone, since I missed running the custom ROMs on my Droid. So I unlocked it and rooted it and everything went all fine and dandy. I decided for my first ROM, I would flash Xtreme Outcast's ICS ROM (v2.0, I think). When I first flashed it, my data worked fine (however downloading apps from the market gave me some issues, but I think that was another problem..). However, before long, like later that day, the 4g and 3g stopped working. After it stopped working, I decided to try to restore my nandroid stock ROM, but when I went back to it, not only did the 4g and 3g not work, the wifi just said 'error' when I tried to turn it on. So after that, I tried to flash the GB OTA RUU, but that gave me some issues, but I've figured out where that went wrong (mainver error).
Anyway, what I'm trying to figure out is what I can do to try to fix the issue. My mobile data IS on, the battery cover IS on, and the SIM card is inserted and, to my knowledge, working just fine. Would flashing an RUU help? Am I just having bad luck with this ROM and need to flash a different one? Should I update to the new RUU? Any help would be fantastic, and I'd award you 456789876435974 awesome points!
Sounds like you may have had a bad ROM zip. I would try re-downloading the ROM and re-flashing making sure you wipe all/factory reset first. If that works and you are feeling adventurous, I highly recommend Scott's ROMs new CleanRom 4.1 which requires an RUU. Check out his web site and developer thread here for more info. I took the leap and love it.
woodyt74 said:
Sounds like you may have had a bad ROM zip. I would try re-downloading the ROM and re-flashing making sure you wipe all/factory reset first. If that works and you are feeling adventurous, I highly recommend Scott's ROMs new CleanRom 4.1 which requires an RUU. Check out his web site and developer thread here for more info. I took the leap and love it.
Click to expand...
Click to collapse
Thanks for the response, but do you think it was just a bad flash if it affected the stock nandroid backup too? I will try flashing a new ROM soon either way, though. Is it possible to download an older version of CleanRom? I can't find a link on the first page of the thread, though I might have just overlooked it. I'm just not sure if I want to update to the new RUU right now, but if there are no other options, I might just pull the trigger on it.
Go to Scott's ROMs web site and you can download ISCE 3.7 which is still on the old firmware so no RUU needed. His roms are pretty slick and he provides great support.
Good point on the nandroid so I'm not sure what's going on. Hopefully the new ROM flash helps.
Well, I flashed the ICS RUU, and now my data works! but now...I can't get my phone to root. Is there a guide for rooting on the new RUU?
CollinswithanS said:
Well, I flashed the ICS RUU, and now my data works! but now...I can't get my phone to root. Is there a guide for rooting on the new RUU?
Click to expand...
Click to collapse
It is just easiest to install and ICS new firmware ROM that is already rooted.
There is however a couple of thread in the development forum on rooting and there is an ICS root tool there
I've tried multiple, and I mean multiple ROMS. All of them will just randomly crash, even if I'm not doing anything! I recently had my friend help me fix my phone because CWM recovery messed up my phone and made it so I couldn't charge my batteries at all. That problem is over with and I have a new recovery (Amon RA). Everytime I flashed a ROM I immediately flashed PH98IMG.zip because I am S-ON. Every ROM I've installed said it was compatible with S-ON. My phone just resets itself at random no matter what ROM I am on. Should I go back to stock or something? I really need help, my phone is useless at the moment.
My current ROM is CleanROM Professional Edition. This is also crashing.
Please reply someone, I need my phone to work ASAP :/
are you installing any apps or overclocking?
This happened to me as well when I was running on the leak prior to the last leak before the ota. Either way... Relock and RUU again with a fresh download. That fixed it for me. Also S-off really helps with this type of stuff because it makes it super easy to flash anything at any time including hboots. Just be careful about combos. S-off was actually the pain in the ass I thought it would be. Didn't go as smoothly as people described. BUT if u do your homework before attempting it u won't be stuck having to ask questions about what to do in the event something doesn't go perfectly. So to recap, easy for now, RUU with a fresh download the ota is prob Ur best bet. Or hard for now easy for later s-off.
Sent from my ADR6425LVW using xda app-developers app
I used Hansoons all in 1 toolkit to root my rezound, I unlocked the bootloader, loaded the twrp recovery and flashed supersu. Now when my phone boots all I get is the bar across the top with the signal strength, battery level, and time. What can I do to get my phone to function again??
I had previously unlocked with the toolkit and ran a few root apps and removed some blotware. I then relocked and everything was working fine until I tried to root it again.
Are you s-on then?
Did you RUU first? Might want to do that since you had made changes before. That will bring you back to nice and fresh stock.
The latest one is here:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
IF YOU ARE S-ON... you can relock, RUU and then flash the recovery again and get root and see if that helps.
If you are s-off then await someone else's answer, but I think you run the RUU without relocking.
Ya, s-on. That looks like what I need to do, just wasn't sure what to call the process and search for... Unfortunately with my 4g internet via my phone gone, I gotta sit here and wait on the download to complete on my slower internet. Greatly appreciate the fast response!!!!
disdard said:
Ya, s-on. That looks like what I need to do, just wasn't sure what to call the process and search for... Unfortunately with my 4g internet via my phone gone, I gotta sit here and wait on the download to complete on my slower internet. Greatly appreciate the fast response!!!!
Click to expand...
Click to collapse
The answer isn't always RUU. Running an RUU will reverse everything that you just did. You will lose root. You're phone will be wiped. And you'll have to relock. What I recommend trying first is rebooting into recovery. Twrp in this case for you. You can do this by getting into bootloader (power and volume down on boot up) and hitting recovery. Once in recovery try wiping cache and dalvik. Reboot. If that fixes it... Cool. If not.. reboot into recovery again and wipe data. This time it should almost certainly work. You won't have root. But you will be stock.
Flashing a custom ROM will fix your problem as well.
There is almost nothing that you can screw up to the point of HAVING to RUU. Most people only use an RUU to update firmware and radios when new versions are released
Sent from my ADR6425LVW using Tapatalk 2
GetRipped said:
The answer isn't always RUU. Running an RUU will reverse everything that you just did. You will lose root. You're phone will be wiped. And you'll have to relock. What I recommend trying first is rebooting into recovery. Twrp in this case for you. You can do this by getting into bootloader (power and volume down on boot up) and hitting recovery. Once in recovery try wiping cache and dalvik. Reboot. If that fixes it... Cool. If not.. reboot into recovery again and wipe data. This time it should almost certainly work. You won't have root. But you will be stock.
Flashing a custom ROM will fix your problem as well.
There is almost nothing that you can screw up to the point of HAVING to RUU. Most people only use an RUU to update firmware and radios when new versions are released
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Well it's not like one should avoid RUU like the plague, geez.
As to wiping your phone, flashing a custom ROM can/will do that as well. Relocking and unlocking again are really no big deal, just a couple commands. Rerooting is simple. It's really not as bad as you make it out to be, imo. And in fact, there's a ton of threads suggesting running an RUU to solve issues and get a fresh start.
I like to run an RUU since it brings you back to a nice fresh stock install, and yes, it will update if the phone is not up to date. In this case to global, which is a bonus.
feralicious said:
Well it's not like one should avoid RUU like the plague, geez.
As to wiping your phone, flashing a custom ROM can/will do that as well. Relocking and unlocking again are really no big deal, just a couple commands. Rerooting is simple. It's really not as bad as you make it out to be, imo. And in fact, there's a ton of threads suggesting running an RUU to solve issues and get a fresh start.
I like to run an RUU since it brings you back to a nice fresh stock install, and yes, it will update if the phone is not up to date. In this case to global, which is a bonus.
Click to expand...
Click to collapse
Oh hai there.:angel:
disdard said:
I used Hansoons all in 1 toolkit to root my rezound, I unlocked the bootloader, loaded the twrp recovery and flashed supersu. Now when my phone boots all I get is the bar across the top with the signal strength, battery level, and time. What can I do to get my phone to function again??
I had previously unlocked with the toolkit and ran a few root apps and removed some blotware. I then relocked and everything was working fine until I tried to root it again.
Click to expand...
Click to collapse
It sounds like you just need a new launcher. If you're getting to that point are you able to pull it down and see the notification area?
If yes then you could use Droid Explorer to push another launcher to the phone.
If not, yeah you maybe looking at starting over. Have you tried using a different recovery? I know personally I've had issues with every launcher except for Amon Ra.
I ran RUU, and once reset to stock breezed through the process of rerooting. Unfortunately had that done before any of the other replies, because it would have been easier to just do the resetting. But I got into the mess while trying to straighten out the issue of my dialer and people app disappearing so just fully going back to stock ensured I got the entire mission accomplished. And at the point it would boot to, you couldn't pull up the notification window so a new launcher wouldn't have fixed it.
Atleast I learned a bunch through the process!!! Just getting into rooting and customization, took the first step and rooted and kinda figured out how things work. Once I figure out a little more and decide which ROM I want to try, I'd like to try a custom ROM. All stuff I'm familiar doing with computers just gotta figure out exactly how it all works on phones....
Glad you are back up and running! Sorry if my method was more involved/time consuming.
I would suggest that before you flash a custom ROM you make a nandroid of your stock set up. Then you can always flash back to that if you don't like the ROM or run into issues and avoid troubleshooting or RUUing just to fix something.
It's a good safety net and a good habit to always have a nandroid to go back to in case of issues. I usually keep one handy of stock and of any ROMs I like, and always make one before flashing a new ROM or even a theme for a ROM.