Hi,
For 2 days my Wifi is giving an error. It says turning on but never does. I have not installed anything or changed a thing. It stopped working for some strange reason. I am on stock mobility with stock kernel, never changed it and I have s-on.
Please help,
Thanks
Try a hard reset
Sent from my HTC_Amaze_4G using xda app-developers app
Is there any way besides a hard reset?
Sent from my HTC Amaze 4G using xda premium
Are you rooted!
Sent from my HTC_Amaze_4G using xda app-developers app
Unlocked bootloader & rooted.
Sent from my HTC Amaze 4G using xda premium
Try clearing Dalvik-Cache in recovery then Fix Permissions. It should help it.
Wipe and reflash stock via hasoon's zip files.
I reset and its still the same. When I try to flash a different kernel it restarts without changing but starts with an error message to contact HTC. I'm fully rooted, unlocked bootloader and s-on and I tried flash.bat and the kernel flasher app but none can change my kernel. Does anyone have any suggestions?
Just noticed bt is not working too
Sent from my HTC Amaze 4G using xda premium
pokey77 said:
I reset and its still the same. When I try to flash a different kernel it restarts without changing but starts with an error message to contact HTC. I'm fully rooted, unlocked bootloader and s-on and I tried flash.bat and the kernel flasher app but none can change my kernel. Does anyone have any suggestions?
Sent from my HTC Amaze 4G using xda premium
Click to expand...
Click to collapse
Well if you are using 4ext recovery (which i highly recommend, best recovery ever made)then there is an option that asks if you are are s-on and you click yes because you are s-on which then allows the recovery to flash any kernel (given its compatible of course) as if you were s-off. That should work, if for some odd reason (for me 4ext never failed even when i was s-on while flashing kernels) it doesnt work then i would suggest attempt to s-off your device via wire trick but be sure to read up thoroughly before you attempt that as some people have bricked their device doing so.
Edit: also i would suggest wipe all partitions except sd card then flash rom and then flash kernel right after to avoid issues.
Could I try to flash a kernel first before flashing. I tried looking for a kernel all day and can't seem to find 1. I used the mobility ota Kernel which does not seem to work.
Sent from my HTC Amaze 4G using xda premium
pokey77 said:
Could I try to flash a kernel first before flashing. I tried looking for a kernel all day and can't seem to find 1. I used the mobility ota Kernel which does not seem to work.
Sent from my HTC Amaze 4G using xda premium
Click to expand...
Click to collapse
Hmm I haven't heard of that kernel before and there aren't many to choose from on this device. First off do you have the ICS ruu? If so just flash faux's kernel with any of theroms that are based off of sense 3.6. Here is the link that is also under the development section of the forums http://faux.androidro.ms/ruby-faux123-kernel-v017.zip for the ICS version ROMs (most of them are) I would suggest speedrom 7.5 as I found it pretty decent for a sense based rom. But you have to flash the ROM first then the kernel but if I recall 4ext recovery with the feature of s-off automatically flashes the kernel that is packaged with the rom it just ends up having to boot twice. So first just flash one of the new sense 3.6 ROMs via 4ext recovery - settings-recovery-check smartflash on and then flash the ROM kernel should automatically flash
Edit: stumbled across this in faux kernel thread might help if 4ext still doesn't work
http://forum.xda-developers.com/showthread.php?t=1359951&page=181
I also had the wifi error problem for some reason when I tried to flash Speedrom 6.5 and 7.0 coming from Supersaiyan 3. Kinda fixed itself after installing Speedrom 7.5/7.6 so maybe try these two steps and it might work for you:
1 ) Of course make a backup
2) When flashing a new or old rom I always Wipe/Factory Reset from 4ext and then just clear dalvik cache, then install whatever rom you like. Never had any probs with this method such as the wifi error you're encountering. Just never got bt error.... weird...
Btw what rom are you currently on?
+1 if this helped anyone!
Sent from my HTC Ruby using xda premium
I'm on mobility stock rom
Sent from my HTC Amaze 4G using xda premium
I switched to speed Rom and bt works but not WiFi.
Sent from my HTC_Amaze_4G using xda premium
I've tried a few roms all day and still no luck.
1. After installing a rom, it always does 1 final step before a restart. It uses a previously saved boot.img which i think is causing my issue but i could be wrong.
1. One thing i noticed is when a rom boots up, the 1st thing it does is turn on WIFI followed by an error.
Has this happened or does any of this makes sense to anyone?
Once again, please help & thanks.
pokey77 said:
I switched to speed Rom and bt works but not WiFi.
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Bro its most likely a kernel issue you are facing WiFi issues usually are due to the incorrect kernel flashed or the kernel not flashed at all with the ROM however I would suggest that you flash the stock ruu file (however you will lose both root and recovery but those are easy to reinstall using hasoons tool or various other methods) I say this because this way you will know for sure if you have a hardware or software problem for sure. WiFi should work with stock ruu from your carrier (make sure to download your carrier specific ruu).if you feel you can do s-off via wire trick and then super cid your amaze you will be able to flash any and every ROM for the amaze. I have a suspicion that the ROMs that are out are based off of T-Mobile ruu and people with mobilicity have their amaze super cid to work with any carrier.however did you try flashing cm10 via 4ext maybe since that has an aosp kernel and if flashed with smart flash option in 4ext it may work.
1. After installing a rom, it always does 1 final step before a restart. It uses a previously saved boot.img which i think is causing my issue but i could be wrong.
1. One thing i noticed is when a rom boots up, the 1st thing it does is turn on WIFI followed by an error.
Click to expand...
Click to collapse
Yea it could be the kernel because the thing you said about the 4ext recovery telling you that its loading the saved boot.img is what I always get and whenever i do get it, the rom always works perfectly. Also which version of speedrom did u try because I had the problem when I was using both 6.5 and 7.0. Try flashing the Supersaiyan 3 rom and then choose faux kernel from the AROMA INSTALLER. Then wipe as I told you in the posts before and then flash speedrom. It worked like that for me. Sorry if you still dont have luck!
What would happen if i deleted the boot.img file and flash a kernel?
Sent from my HTC_Amaze_4G using xda premium
pokey77 said:
What would happen if i deleted the boot.img file and flash a kernel?
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Well OK I really want this to work for you after you mentioned the boot.IMG issue it may be that you need to flash an insecure boot image first. Here is the link http://forum.xda-developers.com/attachment.php?attachmentid=1223086&d=1343307912 for s-on people this usually needs to be flashed via fastboot and not recovery. However since 4ext recovery seems to be an exception to almost every rule regarding recoveries it may be able to flash it. If not just flash via fastboot I posted the forum topic link that this issue has been discussed on in one of my previous posts in this thread. I'm positive this is your problem now.
---------- Post added at 12:44 AM ---------- Previous post was at 12:36 AM ----------
Read through the issue on this page http://forum.xda-developers.com/showthread.php?t=1359951&page=181 seems like this is exactly the issue you are facing. I suggest after flashing which ever ROM flash fauxs kernel it's the best for the amaze anyway hope you get this to work I have exhausted the last bit of knowledge I have regarding this issue. Hence I s-off my device to avoid stupid issues such as these once and for all.
Should I try s-off before installing the GB ruu?
Sent from my HTC Amaze 4G using xda premium
Related
I have the Evo 3d, and i flashed the meanrom ics. After i had flashed it wifi doesnt work, there is an error. I have the OTA update from sprint before i flashed it. I do not have s-off, but his thread says you do not need it. i have done a superwipe and then tryed to reflash it after i did the superwipe and still the same problem.
Did you flash the new firmware? Radios? Have you tried flashing another rom?
Yeah i did try flashing a new rom and its still the same problems, wifi doesnt work. If you know were i can find the legit stock rom ill try to download that but i cant seem to find it anywhere.
Once again, Did you flash the new firmware? Radios?
If you know were i can find the legit stock rom ill try to download that but i cant seem to find it anywhere.
Click to expand...
Click to collapse
Rooted stock roms are in the CDMA Development section.
I had the same problem. Solution I used was to flash kernel from the mean Rom using flashimagegui. Worked fine after a reboot!
Sent from my SPH-L710 using xda app-developers app
Just be very careful in which kernel you flash, s-off is required for flashing certain kernels
sent on my Evil Evo running the so called developers kernel
flashallthetime said:
Just be very careful in which kernel you flash, s-off is required for flashing certain kernels
sent on my Evil Evo running the so called developers kernel
Click to expand...
Click to collapse
OK but on his thread it says its of the 2.17 kernal so that anyone can do it no matter the gboot. But it doesnt matter anymore i finnaly got s-off to work and just super wiped it and re-flashed it again and it works.
Mclarkiin said:
OK but on his thread it says its of the 2.17 kernal so that anyone can do it no matter the gboot. But it doesnt matter anymore i finnaly got s-off to work and just super wiped it and re-flashed it again and it works.
Click to expand...
Click to collapse
As you can see from yet another success story, anybody who sees this in the future, stop fooling around with s-on. Just get s-off and be done with it. :good:
I have A solution
Mclarkiin said:
I have the Evo 3d, and i flashed the meanrom ics. After i had flashed it wifi doesnt work, there is an error. I have the OTA update from sprint before i flashed it. I do not have s-off, but his thread says you do not need it. i have done a superwipe and then tryed to reflash it after i did the superwipe and still the same problem.
Click to expand...
Click to collapse
I think i have a solution for your problem it worked for me , By the way I used 4ext touch Recovery
in recovery when you are going to flash the new Rom make sure you select { wipe data/factory reset,,wipe cach ,, wipe dalvik cach } and most important select {format all partitions (except sdcard)
after all that you are ready to install the new Rom then Reboot the device and you shall not have any problems with your WiFi But Bluetooth still wont start or work
mobi from my Nexus 5 using XDA Free mobile app
---------- Post added at 02:30 PM ---------- Previous post was at 02:28 PM ----------
my Nexus 5 using XDA Free mobile app
you
I
I flashed midnight ROM. put the AOSP theme over it. Flashed the newest MAC Kernel, and that's when it started happening.
I decided to factory reset and flash the ROM again, tried to restart. same thing.
restored a backup (after factory restting), no dice.
Wiped boot/data/system, factory resetted, wiped both caches and reflashed midnight ROM. Still nothing.
Tried to flash CM9 (after factory resetting and stuff) and it still won't go past the HTC screen no matter how long I wait.
What's wrong? Am I half bricked?
I'm using the Evo V with S OFF on downgraded HBOOT.
You need to downgrade your radios as well to flash aosp roms. Run an older RUU, which will set you back to stock, flash your recovery and then flash midnight again
Sent from my PG86100 using xda app-developers app
beneath-a-burning-turtle said:
You need to downgrade your radios as well to flash aosp roms. Run an older RUU, which will set you back to stock, flash your recovery and then flash midnight again
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
I've flashed all these ROMs with no problems before. I already have my radios upgraded (I basically turned my phone into a Evo 3D).
RedDeadDorito said:
I've flashed all these ROMs with no problems before. I already have my radios upgraded (I basically turned my phone into a Evo 3D).
Click to expand...
Click to collapse
Gotta go in the opposite direction with radios, downgrade. It'll make older roms compatible again.
Sent from my PG86100 using xda app-developers app
beneath-a-burning-turtle said:
Gotta go in the opposite direction with radios, downgrade. It'll make older roms compatible again.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
So basically, upgrade my HBOOT (since stock is on a upgraded one) again and flash a stock ROM then downgrade again?
I was thinking of doing this, but why did this problem come up in the first place?
I can't do it because I don't have an extra SD card around. If I put the hboot upgrade on my SD card, the bootloader won't start up because it gives you the option to install it or not install and either way, it turns the phone off.
Got it figured out. When I flashed a different kernel, it broke the other kernel or something. I had to flash the ROM's kernel separately. I don't know why.
I'm not sure why, but it did. Anyways, it seems to be working now!
RedDeadDorito said:
Got it figured out. When I flashed a different kernel, it broke the other kernel or something. I had to flash the ROM's kernel separately. I don't know why.
I'm not sure why, but it did. Anyways, it seems to be working now!
Click to expand...
Click to collapse
Glad that you got a solution and that you were also detailed in your response. Perhaps someone in the future that sets aside the time to research and read will be able to either get themselves out of a mess - or - possible avoid one. Cheers!
So I have been using Neo's AOSP Rage Rom since about 1.4, and haven't encountered any serious problems (besides some hiccups such as the Trebuchet FC problem in 1.7, although everyone had that). Now, after I have flashed 1.8, I am unable to turn on my Wifi. I checked my md5s, I did 3 clean flashes, and I also flashed the rom with and without the inverted gapps pack.
My Rezound is currently S-ON, and I have no plans to go S-OFF unless necessary.
I'm not sure if this is a kernel problem, or if it's the wifi module, or perhaps something else, but I figured I should ask here first to see if there were others with he same problem.
Most likely kernel, try flashing Snuzzo's kernel
Sent from my ADR6425LVW using xda app-developers app
Squirrel1620 said:
Most likely kernel, try flashing Snuzzo's kernel
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I've tried that and it didn't help. I tried both of his kernels without success. My problem may be hardware related though. I can't switch back to sense based from without bootlooping. Same thing with flashing ruu.
aftafoya said:
I've tried that and it didn't help. I tried both of his kernels without success. My problem may be hardware related though. I can't switch back to sense based from without bootlooping. Same thing with flashing ruu.
Click to expand...
Click to collapse
If your running an ruu and still boot looping, then something else is wrong. It's gotta be a hardware problem, time for an insurance return
Sent from my ADR6425LVW using xda app-developers app
Well... I figured out what I was doing wrong, which was that I forgot to re-flash the boot.img that came with the Neo's rom. I suppose I forgot to re-flash it because it never said you had to, but I remembered that the rom was intended for S-OFF, and I'm S-ON, so that never occurred to me.
So, yeah, it was basically the kernel.
After I did a clean wipe and flash of Rage again, and flashed the boot.img in the bootloader, everything worked.
Lucasonic said:
Well... I figured out what I was doing wrong, which was that I forgot to re-flash the boot.img that came with the Neo's rom. I suppose I forgot to re-flash it because it never said you had to, but I remembered that the rom was intended for S-OFF, and I'm S-ON, so that never occurred to me.
So, yeah, it was basically the kernel.
After I did a clean wipe and flash of Rage again, and flashed the boot.img in the bootloader, everything worked.
Click to expand...
Click to collapse
Glad to see it works. Yeah so go s off your phone! Lol its worth it
Sent from my ADR6425LVW using xda app-developers app
I've got the same issue. Except wifi, gps, and bluetooth won't turn on. Also, I keep getting the message that my SD card is damaged. I pulled the boot file from the ROM, zipped it, and named it PH89IMG.
So far, everything else seems to work, but this isn't really working for me. Any suggestions?
Are you on ICS firmware or GB firmware? If you are on GB still and trying to flash ICS rom, wifi and sdcard won't work until you flash the old firmware patch.
Sent from my Rezound using Tapatalk 2
Squirrel1620 said:
Glad to see it works. Yeah so go s off your phone! Lol its worth it
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I second that notion. I've been on 1.8 for a while and I feel like it's been the best version so far (I'm S-OFF). 1.9 is out now, so I'll be trying that later tonight.
Performing S-OFF isn't that bad. I thought it was fun - just follow the directions and you should be fine (like anything else).
I've tried a million and one things with my phone. All I want is to get it out like it is fresh out of the box. I can't find a RUU that works, I downloaded a recovery ROM, now there's a *security warning* on my Bootloader so I can't even get to my recovery...please help. I just want my phone back...
ADashOfCapers said:
I've tried a million and one things with my phone. All I want is to get it out like it is fresh out of the box. I can't find a RUU that works, I downloaded a recovery ROM, now there's a *security warning* on my Bootloader so I can't even get to my recovery...please help. I just want my phone back...
Click to expand...
Click to collapse
use this guide to go back to stock
http://forum.xda-developers.com/showthread.php?p=37687025
Sent from my One S using Tapatalk 2
So my phone is working because I'm using Harmonia 3.17 ROM and the only problem is the WIFI won't come on. It just says error.
ADashOfCapers said:
So my phone is working because I'm using Harmonia 3.17 ROM and the only problem is the WIFI won't come on. It just says error.
Click to expand...
Click to collapse
That is usually a kernel issue.
I would suggest using flash image GUI, and flashing a kernel, I suggest mirage.
Both downloads are in his first post here:
http://forum.xda-developers.com/showthread.php?t=2175191
Sent from my PG86100 using xda app-developers app
I tried Flash Image and it said it wasn't compatible with my phone.
ADashOfCapers said:
I tried Flash Image and it said it wasn't compatible with my phone.
Click to expand...
Click to collapse
It works, don't know why it doesn't for you.
Other things you can try is flash boot.IMG through fastboot
Or using 4ext make sure smartflash is enabled and do a fresh install of your rom
Also you can flash some kernels through recovery
Sent from my PG86100 using xda app-developers app
Hi guys,I have a problem romming my HTC Amaze 4g.
I have already unlocked bootloader and installed TWRP recovery but when i flashed official cyanogenmod the phone got bootloop.
No error messages or sg like that.
Dont know what to do please help.
Adam.
tamasicsadam said:
Hi guys,I have a problem romming my HTC Amaze 4g.
I have already unlocked bootloader and installed TWRP recovery but when i flashed official cyanogenmod the phone got bootloop.
No error messages or sg like that.
Dont know what to do please help.
Adam.
Click to expand...
Click to collapse
Off hand the most likely scenario is the kernel didn't get flashed with the rest of the ROM. This is a known issue with TWRP and CWM on devices that are s-on. Try again with ext4 recovery and enable smart flash. It seems to be the recovery with the least amount of problems with this device, especially those that are s-on, and is the solution recommended by most devs here.
Thanks, i will try this and tell you if it is solved.
Sent from my LG-P700 using xda app-developers app
Here again. I have tried what u mentioned .flashed ex4 recovery and tried to flash the rom via that smart thing enabled and when the phone booted up it rebooted when PIN was entered. After that tried to wipe dalvik but it got worse cuz phone got bootloop now. Any ideas?
When flashing by smart flash on you have to flash the kernel seprately
Sent from my HTC_Amaze_4G using Tapatalk
Or the link might have gone bad one another user is also saying the same about cm but there is one more possibility the cm roms are usually quite a lot undervolted i think sports device supports it i had this problem on cm 11 and overvolting did the job but you guys cant even get to the main screen how are you going to overvolt you might just have to edit the kernel which i have no experience of.
Sent from my HTC_Amaze_4G using Tapatalk
Muneeb Saeed said:
When flashing by smart flash on you have to flash the kernel seprately
Sent from my HTC_Amaze_4G using Tapatalk
Click to expand...
Click to collapse
If smart-flash is properly enabled the kernel will flash with the ROM. That's one of the main purposes of smart-flash.
To the OP: obviously you were able to successfully install the ROM this time since you didn't bootloop and were OK until you entered a PIN for the lockscreen. So this issue is different than the first, where you weren't even getting to the lockscreen. The first thing I would try is wiping then reinstalling CM from recovery. This time just try using it without a PIN for an hour and see if you have other issues. Only then set a PIN. If it crashes after setting a PIN, but was working fine before, you know there is a bug in that part of the ROM. If it begins crashing sooner then something else is the problem.