Hello All,
I'm not to this forum. I'm having a very strange issue. I had unlocked and flashed a scotts clean rom to my phone. This rom worked fine. It was the cleanrom standard 4.4. Everything worked fine, but I wanted to try something without sense. So I followed the instructions and ran scott's wipe program that wipes 5 times over. Then I did a wipe on the device. From there it got stuck in a loop where I would boot it into the hboot and it would try to load that weird PH89IMG file and then reboot and do the same thing.
Believe it or not I resolved this by removing the SD card then booting to recovery then slightly lifting the battery and inserting the sd card in and mounting so that I could load another rom after mounting it. Just to be safe I did perform one more wipe. I loaded the CLEANrom tapped edition. It installed and booted up just fine, only one problem. I cannot turn the wifi on.
So I cleared the cache and Dalvik cache, rebooted. still no wifi. It sits on turning on. The wifi mac address is obviously unavailable. It went to an error evetnaully, but there was no detail in it other than the word ERROR. I tried reloading the ICS kernel as well, still nothing. I didn't see anything in the forum on this issue, so I am not sure why it's isolated to my device. can you help me?
Thanks.
I know your tired of wiping and flashing but this has happened to me before on a previous Clean Rom version. Wipe then reinstall ROM. **Caution** Before you boot to Rom, boot to recovery and flash the kernel that came with the Rom. That cleared up my broken wifi. Also beware that if the Clean Rom tapped edition uses a different base ie. 3.14.605.05 or 3.14.605.10. then you have to flash the Stock Rooted RUU of 3.14.605.05 or 3.14.605.10 and then wipe and install ROM. link to stock RUU:
http://forum.xda-developers.com/showthread.php?t=1642217
I have had this issue with a couple newer ICS ROMS I have tried and it all seems to come down to reflashing the Kernel. Even after updating Nils' Roms to newer versions my rezound would load up fine and everything worked except wifi. If I went back into recovery and reflash the kernel wifi would be back to normal again. Make sure you have the correct kernel designated for that ROM as I have noticed some Kernels need to be redownloaded and reinstalled seperately. Good Luck
Hello,
I am having the same problem and I am on Rezound Pure GSM sense 3.6 rom.....I am confused whether to flash the wifi modules for the new kernel from the above link....I don't wanna take any risks as I finally got my GSM working on atnt.
Thanks!!
Related
I've tried it all folks. New kernels, factory reset, different radios, different ROMs. Every-thing. The WiFi will turn on for a quick second and I will get an error message "Unable to scan for networks" and then the Wifi will just turn on and off on and off over and over again. I've even deleted the files in the data/dhcp and data/wifi folders. Rebooted, still same issue. I've deleted the files and flashed a kernel and rebooted, still same issue.
Of course I am still in contract and will have to purchase a new phone outright from Verizon if I can't get this issue resolved......
I don't know what else to do here.....
Did you try formatting data and system before installing a new rom from recovery? If that doesn't work i would say its a hardware issue. You're not restoring system data with any backup programs are you?
Sent from my ADR6400L using Tapatalk
I've wiped pretty much everything known to man on the phone. The ROM installs are all "fresh" I haven't tried to install any APPS on the phone. Just wipe everything, factory reset / Dalvik Cache, all of it... install fresh ROM. Try to turn on Wifi, phone boot loops. No matter what ROM I install, still same issue with Wifi / boot looping.
Well guess we can close this out. I went out and paid full boat for a Samsung Nexus since I couldn't fix this issue.
I'd like to reopen this topic. I had been running Bamf Forever 1.10, but last night I decided to try another ROM because it's been running really slow for some reason.
Did a wipe (factory reset, Dalvik cache) and installed Thunderstick. Now WiFi is broken -- the exact same problem as described in the original post. I tried flashing a new kernel and new radios, and cannot get WiFi to work.
Does anyone have any suggestions? Will flashing back to stock ROM/unrooting help?
Thanks!
@ajoesq I had the same problem when i installed thunderstick thru boot manager. My wifi stopped and I could get it going on my phone rom. So i booted back into thunderstick and wifi was working. Booted back to hte phone rom then into recovery and then i flashed my phone rom again without wiping or anything (Thunbershed V1.2) and it worked fine. wifi started agian.
ajoesq said:
I'd like to reopen this topic. I had been running Bamf Forever 1.10, but last night I decided to try another ROM because it's been running really slow for some reason.
Did a wipe (factory reset, Dalvik cache) and installed Thunderstick. Now WiFi is broken -- the exact same problem as described in the original post. I tried flashing a new kernel and new radios, and cannot get WiFi to work.
Does anyone have any suggestions? Will flashing back to stock ROM/unrooting help?
Thanks!
Click to expand...
Click to collapse
Run a logcat when you try to turn wifi on. Put the output on pastebin.com and post the link. This might tell us what the problem is.
I'd make sure that the radio(s) were at least at the minimum of what the ROM called for.
Sent from my HTC ThunderBolt using XDA Premium App
ok, so i unlocked and rooted my rezound, everything was working 100%, then i start flashing diferent roms and it was conecting to wifi with no problems, however when i flashed ( or tried to flash ) a new kernel ( dont remember which one ) wifi stoped working for me, it scans but doesnt pick up any network. i went back to stock kernel and nothing, re-locked device and installed verizon factory Ruu for the rezound and Wifi still doesnt work. Im going crazy here please help, maybe im flashing the kernel wrong but re-locking and restoring to factory Ruu should have fixed it
I was also having the same issue and tried reinstalling kernals and nandroids. I was loading the kernal through Amon Ra interface directly and no matter what I did I still had issues. Sooo, I revised my recovery process and found that dummy me can't read instruction correctly. The issue was resolved after I did a factory reset on the rom (Ineffablis v1.0) then I followed the instructions for installing the kernal (I'm using the SmartassV2 kernal from dsb9938; flash from SD, then flashmethis file and finally through HBOOT, it's a process ok?), rebooted and I was able to get WiFi working again. I've had this issue whenever one of the additions I was trying did strange things to my phone and have sucessfully restored WiFi (about 10 times for this occurance). I've also had to do a hard reset (pulled the battery) and follow the process to get back to functioning. Hope this helps.
i locked the phone again, and ran the rezound stock Ruu and did factory reset, still not picking up any networks. the wifi doesnt give and error it scans and everything, but for some reason it just doesnt pickup any networks
If you read the complete directions when flashing a rom... They state you will need to flash the wifi module after a fresh install. So just flash the kernel over again and you will have wifi working.
Thanks a lot, finally got it working
Sent from my HTC REZOUND using xda premium
I'm having the same problem where my rezound won't find any networks. My bluetooth won't turn on either. How were you able to fix it?
thanks,
ron
Edit
Hi,
I recently bought an HTC Amaze. I have it rooted, bootloader unlocked. Unfortunately, its a SEA (unbranded) version. I tried S-Off so many times but failed. So, I decided to give CM10 and AOKP a try, as I had heard that they don't require S-Off to work on any set.
Firstly, I tried CM10 with TWRP. It didn't work. It was because TWRP doesn't have Smart Flash. So, I switched to 4EXT. It worked. CM10 started, showed me its beauty. Then, suddenly, restarted. And kept restarting. I restored to stock GB ROM. Then, I tried its older builds. Same thing happened. Some people said, kernel could be the issue. So, I decided to try AOKP. Same thing happened. It showed me some screens; select language, lock screen etc. And then restarted. I also tried Dark Glass 0.4, with Mk4 kernel. Same issue happened.
The steps I followed flashing the ROMs are as follows:
For CM10 and AOKP:
1. Wipe data/factory reset
2. Wipe cache/dalvik
3. Format system
For Dark Glass 0.4:
1. Format all partitions except SD
I have been facing this issue. Please help...
Found my answer...
magnum_2007 said:
Hi,
I recently bought an HTC Amaze. I have it rooted, bootloader unlocked. Unfortunately, its a SEA (unbranded) version. I tried S-Off so many times but failed. So, I decided to give CM10 and AOKP a try, as I had heard that they don't require S-Off to work on any set.
Firstly, I tried CM10 with TWRP. It didn't work. It was because TWRP doesn't have Smart Flash. So, I switched to 4EXT. It worked. CM10 started, showed me its beauty. Then, suddenly, restarted. And kept restarting. I restored to stock GB ROM. Then, I tried its older builds. Same thing happened. Some people said, kernel could be the issue. So, I decided to try AOKP. Same thing happened. It showed me some screens; select language, lock screen etc. And then restarted. I also tried Dark Glass 0.4, with Mk4 kernel. Same issue happened.
The steps I followed flashing the ROMs are as follows:
For CM10 and AOKP:
1. Wipe data/factory reset
2. Wipe cache/dalvik
3. Format system
For Dark Glass 0.4:
1. Format all partitions except SD
I have been facing this issue. Please help...
Click to expand...
Click to collapse
Sorry to disturb, I found my answer. To have a ROM based on firmware higher than GB, I need to have that firmware. And to upgrade firmware, I need S-Off. Thanks.
Hi. i own an HTC EVO V 4G (Virgin Mobile). i used the Search function but sadly didnt found exactly what i needed.
a month or so after activating the phone, i decided to Root, S-off, Flash Recovery, bootloader and a custom Rom. However, its been a while now, that when i do a fresh install i get some inconsistency problems. for example, my first Rom was Harmonia, but later on i switched to MidnightRom. there the problems started to show up. the Sense version was working fine, but then i wanted to try out the Jellybean version. and when i did (after wiping everything, of course) some apps were not working. PlayStore wouldnt let me download anything, Tethering was not working, when using "reboot" the phone would get in a bootloop, which would only go away by removing the battery. and 3D games (Shadowgun, Temple Run, etc.) were graphically laggy. more like, unplayable. the image was distorted to the point it was impossible to see what was going on. messed around with fixing permissions, deleting Cache and Dalvik, re-flashing, and the problem was still there. i tried with other Jellybean Roms (both 4.1 and 4.2) and noticed that the problems were still there. anyways, after deciding to live with the problems (running Wild For the Night). months later i decide to flash MidnightRom again and i see that all the problems are magically gone. to this day ive been running only 4.1+ Roms and i dont have many issues whatsoever. BUT. i tried a Senseless Stock-based Rom the other day (started to miss 3D camera) and it ran well, but the overall behavior of the phone was laggy. it would take longer than usual to do anything. took me about 5 re-flashes to get rid of all the problems. then just yesterday i tried a few other Roms. some worked, though DU was really laggy, and the icons would switch places by themselves at times. as i saw the problem was not going away with re-flashing, fixing permissions and whatnot, i decide to restore to my most stable Flashed Rom.
just to clarify, here is what i do every time im about to flash a new ROM:
Wipe everything except SD card
Wipe Cache and Dalvik
Flash.
Reboot
after i flashed, if something went wrong, or if im flashing something ontop:
Wipe Cache and Dalvik
Fix permissions
Reboot
so question is, is this normal? does this has to do with the phone switching from ICS to JB? or am i doing something wrong?
also, just curious... is there a way one could, say, by some weird reason be "half S-off"? because although my bootloader says S-Off, and i have been able to flash many things, i remember that when doing the Wire thing i experienced many errors, and the thing said it was successful by itself a few seconds later while i wasnt doing anything.
and also, which is the best and most stable Hboot version i could use?
My HBoot version is 1.04.2000 (PG8610000)
Radio is 1.09.00.0706
My Recovery is 4EXT latest version
Thanks in advance
I was listening to music on my Evo 3D over bluetooth today, when I put it in my pocket and paused the music. After going back to my phone, I noticed it had reboot itself, and now it's stuck on a boot loop. Does this sound familiar to anyone? I can't think of any reason why it would boot loop like this. Wiping cache+dalvik doesn't fix the boot loop. After clearing cache+dalvik and booting the phone, it does go to the screen saying that Android is updating apps, but as soon as it finishes it goes right back to the boot loop. I'd appreciate any assistance in figuring this out. Thanks!
it happened to me the other day. i was using CM10.1 Wild for the night along with Saring Gas Kernel. i managed to fix this by wiping everything manually instead of using a superwipe, and then flashing again. and then i had this issue with MidNight Rom CM10.1 where whenever i turned bluetooth on, after turning it off the phone would freeze, reboot and then bootloop. however the Dev had specified that bluetooth was broken.
if the boot loop is at the Rom's boot animation, and you cant fix this by deleting Cache, Dalvik and Data, then you will certainly have to wipe it all and flash again. hopefully you had all you data backed up.
Kite-G said:
it happened to me the other day. i was using CM10.1 Wild for the night along with Saring Gas Kernel. i managed to fix this by wiping everything manually instead of using a superwipe, and then flashing again. and then i had this issue with MidNight Rom CM10.1 where whenever i turned bluetooth on, after turning it off the phone would freeze, reboot and then bootloop. however the Dev had specified that bluetooth was broken.
if the boot loop is at the Rom's boot animation, and you cant fix this by deleting Cache, Dalvik and Data, then you will certainly have to wipe it all and flash again. hopefully you had all you data backed up.
Click to expand...
Click to collapse
Yeah, I ultimately had to restore from a backup. This is an almost stock ICS rom, deodex plus a few other apps baked into the ROM, and the stock kernel.
Now this doesn't happen every single time I turn the screen off with bluetooth turned on, or every time I turn off bluetooth. This is just a random boot loop that hits out of nowhere. Since I can't figure out what causes it, I was hoping someone who had encountered it would know.
while i cant point out the exact cause, these random bootloops happen due to file system errors, or namely the kernel. but you say you had stock kernel, so if it was not overclocked or tempered with then that cant be it.
in my case, for example, last night i overclocked my phone to 1.8GHz and set the governor to performance, I/O to vr. turned the phone off and forgot to lower the settings or to increase voltage, and then when i turned it on the phone was in a bootloop. went to recovery and it said that cache was unreadable, suggesting a full wipe. what happened here was that the kernel settings i had used were saved in cache, so when i tried to boot with such high settings without the proper power for the cpu, the phone just couldnt boot. i wiped cache and the kernel settings got restored to default. so it booted.
another example was that i flashed an update.zip that was corrupted. the phone booted and behaved normally. then when i loaded any of the apps from the update.zip the phone would freeze, reboot and boot loop.
and then theres this one, my EVO could run every ICS rom perfectly, but every single 4.1+ rom i used had bugs, lag, visual glitches, and whatnot. i tried wiping multiple times, redownloading the roms, etc. in the end nothing helped. then i tried a superwipe which checks the filesystem for errors and optimizes it. after using that superwipe, every 4.1+ rom ran smoothly, and the ICS roms i had used benchmarked better than before
so if you say you got that boot loop randomly, and using stock kernel, i can safely assume that either the rom did not flashed properly, or that your EVO has some file system errors. you could try either a new fresh install or using a superwipe and flash your Nand, but if it was me, i would use superwipe, then manually wipe everything, and fresh install the rom. if the nand backup you installed after the bootloop was from the same install as the one who gave you the bootloop, then its a safe bet that it could happen again. i would backup all my apps and data, and do as i said earlier.
hopefully this info helped you a little.
in case you would want to give it a shot, here is the superwipe i used.
like i said, just flash the file on recovery, you dont need to wipe beforehand. and after its flashed, i recommend you wipe but its not necessary. then just flash your rom, and other files if any, and boot. hope it helps.
(i was gonna link to the thread where i got the super wipe, but i forgot where i found it. anyways, credit goes to author)
Kite-G said:
while i cant point out the exact cause, these random bootloops happen due to file system errors, or namely the kernel. but you say you had stock kernel, so if it was not overclocked or tempered with then that cant be it.
in my case, for example, last night i overclocked my phone to 1.8GHz and set the governor to performance, I/O to vr. turned the phone off and forgot to lower the settings or to increase voltage, and then when i turned it on the phone was in a bootloop. went to recovery and it said that cache was unreadable, suggesting a full wipe. what happened here was that the kernel settings i had used were saved in cache, so when i tried to boot with such high settings without the proper power for the cpu, the phone just couldnt boot. i wiped cache and the kernel settings got restored to default. so it booted.
another example was that i flashed an update.zip that was corrupted. the phone booted and behaved normally. then when i loaded any of the apps from the update.zip the phone would freeze, reboot and boot loop.
and then theres this one, my EVO could run every ICS rom perfectly, but every single 4.1+ rom i used had bugs, lag, visual glitches, and whatnot. i tried wiping multiple times, redownloading the roms, etc. in the end nothing helped. then i tried a superwipe which checks the filesystem for errors and optimizes it. after using that superwipe, every 4.1+ rom ran smoothly, and the ICS roms i had used benchmarked better than before
so if you say you got that boot loop randomly, and using stock kernel, i can safely assume that either the rom did not flashed properly, or that your EVO has some file system errors. you could try either a new fresh install or using a superwipe and flash your Nand, but if it was me, i would use superwipe, then manually wipe everything, and fresh install the rom. if the nand backup you installed after the bootloop was from the same install as the one who gave you the bootloop, then its a safe bet that it could happen again. i would backup all my apps and data, and do as i said earlier.
hopefully this info helped you a little.
in case you would want to give it a shot, here is the superwipe i used.
like i said, just flash the file on recovery, you dont need to wipe beforehand. and after its flashed, i recommend you wipe but its not necessary. then just flash your rom, and other files if any, and boot. hope it helps.
(i was gonna link to the thread where i got the super wipe, but i forgot where i found it. anyways, credit goes to author)
Click to expand...
Click to collapse
Just FYI, the Wild For The Night OP specifically says do NOT use superwipes. Superwipe scripts and AOSP Roms don't always play together nicely. That's and CM Rom. Factory reset wipe in recovery is fine.
I am aware of that. But thanks for pointing it out. Althought I haven't had any problems with AOSP roms & superwipes when I wipe manually after the superwipe, only when I don't. But then again results may vary. At least in my case, I'm pretty satisfied with the results.
Sent from my HTC EVO V 4G using xda app-developers app