WiFi will not turn on - Kindle Fire Q&A, Help & Troubleshooting

Howdy. Was hoping someone here could help me out. Sorry if this is in the wrong section.
So a friend sold me his kindle because he was having troubles, and I thought I could fix it.
He gave it to me with the stock OS, and it appeared the WiFi was stuck on the on position. But no WiFi networks would show up. Also could not access the device settings. I rooted it, installed TWRP, and tried a factory reset. That didn't work, so I tried installing different ROMs. None that I tried fixed it. Only tried AOKP and CM10 with the firmware updates. Now on the settings, the WiFi instantly turns off after swiping it to the on position.
Has anyone else experienced this problem?
Is my WiFi completely shot or is there a fix for this?
Sent from my phone.

How to flash a rom:
1. Transfer Rom zip and matching gapps zip to sdcard.
2. Enter recovery.
3. Create a backup.
4. Wipe factory reset.
5. Wipe cache.
6. Wipe dalvik.
7. Wipe system.( unless same Rom, same system, same developer)
8. Flash Rom zip.
9. Flash gapps zip.
10. Select reboot, then system if prompted.
11. Enjoy!
If you are doing all this and still no wifi It could be hardware or the wifi you are trying to connect to or router.

Related

[HELP] Constant Boot Loops after Radio Flash

I have always had random reboots with the phone, however they were mostly infrequent.
Fastforward to yesterday, I was running the latest stable version of CM7 (7.0.3.1 or something to that effect). Everything was working out okay, and so I decided to flash the latest WiMAX and Radio updates. First I did the WiMAX, everything went fine and the phone rebooted and I used it without issue for a couple hours. At this point I flashed the latest radio from Caulkin's thread. After rebooting, the phone makes it through the splash screen, and into the rom splash screen, then once actually booting the rom it boot loops. If I get lucky, and manage to turn the phone into Airplane mode before the boot loop, I can prevent it from occurring.
So I have tried to re-download and reflash this version and the last version of the radio many times, without success in stopping the boot loops. I have reflashed the ROM as well as gone back into old Sense nandroid backups and the problem persists. I have flashed the FORMAT_ALL.zip file and the problem still persists! I have tried to update PRL and Profile, and the problem still persists!
Any help would be greatly appreciated.
Do the following in order:
1. Download and flash the PC36IMG.zip for amon RA v2.3 from the bootloader screen. You can download it from http://forum.xda-developers.com/showthread.php?t=705026
2. After amon RA is flashed, connect your device to your computer, reboot into your new recovery, select the MS-USB option and copy a freshly downloaded radio, PRI and NV over to your SD card. Do not use the combo zip. This is also a good time to transfer a freshly downloaded stock rom. You can get the radio stuff from http://forum.xda-developers.com/showthread.php?t=715485 and the rooted stock odexed rom from http://forum.xda-developers.com/showthread.php?t=874251
3. After you've transferred the above items over to your SD card, select the MS-USB option again to unmount your card.
4. Go to the wipe menu and wipe EVERYTHING in it except the SD card itself. Afterwards, do not reboot.
5. Go to the flash menu and flash the PRI. Be patient. When it is complete, you will automatically reboot into recovery and see the words "clearing cache". Go to the wipe menu and wipe the dalvik. Afterwards, flash the radio and NV. Remember to wipe the dalvik between flashes.
6. Flash the rom. Do not flash any kernels, themes or mods. Afterwards, reboot. Be patient because the initial boot will take a while. When you've entered your homescreen, update your profile in the settings menu. If all went well and no reboots, go into recovery, wipe cache and dalvik and then create a nandroid backup. After that, if you want to flash CM7, wipe Everything in the wipe menu except the SD card and flash it. Hopefully, this will work for you.
posting & replying via the XDA Premium app.
I followed each of your instructions without success. Before I could even set up the phone fully, it rebooted. But this did help lead to a new theory I have. It didn't reboot until I got to the "location" settings, once I hit next allowing Google to use location settings it rebooted. So after 5 or 6 boot loops I managed to get back in to the OS long enough to turn off location settings. For the last 30 minutes or so I haven't had a reboot as long as the GPS and other location methods are off. Just a theory, we'll see if something changes... Meanwhile I wonder what the real issue is. *Edit* Scratch that, just boot looped.
dougjamal said:
Do the following in order:
1. Download and flash the PC36IMG.zip for amon RA v2.3 from the bootloader screen. You can download it from http://forum.xda-developers.com/showthread.php?t=705026
2. After amon RA is flashed, connect your device to your computer, reboot into your new recovery, select the MS-USB option and copy a freshly downloaded radio, PRI and NV over to your SD card. Do not use the combo zip. This is also a good time to transfer a freshly downloaded stock rom. You can get the radio stuff from http://forum.xda-developers.com/showthread.php?t=715485 and the rooted stock odexed rom from http://forum.xda-developers.com/showthread.php?t=874251
3. After you've transferred the above items over to your SD card, select the MS-USB option again to unmount your card.
4. Go to the wipe menu and wipe EVERYTHING in it except the SD card itself. Afterwards, do not reboot.
5. Go to the flash menu and flash the PRI. Be patient. When it is complete, you will automatically reboot into recovery and see the words "clearing cache". Go to the wipe menu and wipe the dalvik. Afterwards, flash the radio and NV. Remember to wipe the dalvik between flashes.
6. Flash the rom. Do not flash any kernels, themes or mods. Afterwards, reboot. Be patient because the initial boot will take a while. When you've entered your homescreen, update your profile in the settings menu. If all went well and no reboots, go into recovery, wipe cache and dalvik and then create a nandroid backup. After that, if you want to flash CM7, wipe Everything in the wipe menu except the SD card and flash it. Hopefully, this will work for you.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Very interesting, indeed. Good catch, by the way......Since you are using CM7, you may have to apply a GPS fix of some sort. Does the smell thing occur with other AOSP roms like Salvage-Mod? What about Sense-based roms?
posting & replying via the XDA Premium app.
/bin/bash said:
I followed each of your instructions without success. Before I could even set up the phone fully, it rebooted. But this did help lead to a new theory I have. It didn't reboot until I got to the "location" settings, once I hit next allowing Google to use location settings it rebooted. So after 5 or 6 boot loops I managed to get back in to the OS long enough to turn off location settings. For the last 30 minutes or so I haven't had a reboot as long as the GPS and other location methods are off. Just a theory, we'll see if something changes... Meanwhile I wonder what the real issue is. *Edit* Scratch that, just boot looped.
Click to expand...
Click to collapse
You're installing it fresh, with the gapps, correct. And it only reboots when you use the location settings?
teh roxxorz said:
You're installing it fresh, with the gapps, correct. And it only reboots when you use the location settings?
Click to expand...
Click to collapse
I haven't put CM back on the device, as directed above I put on a stock rooted rom to "bug track", so gapps is installed, yes, but by default in Sense / HTC.
From the last two hours or so it still reboots after location settings are off, but less frequently than if they are on. Perhaps this is a heat issue? The more radios and things on the quicker it overheats into bootloop?
Also, stressing the phone in any way, such as running linpack, triggers a reboot.

cm9 and gapps?

so i loaded cm9 ics on my fire and everything worked great. then i flashed the gapps zip and when i turn on the fire the prompt screen comes on that comes on everytime you buy a new device, the one where you are prompted to touch the android and then you will enter your info and stuff. well, everytime i touch the android, it says "unfortunately the setup wizard has stopped" with a force close button. any ideas how to get gapps on?
May not have wiped everything properly, or flashed a corrupt gapps zip.
Either way, you can get around the issue from TWRP by deleting the file /system/app/SetupWizard.apk using the built-in file manager or ADB.
Dasanko said:
May not have wiped everything properly, or flashed a corrupt gapps zip.
Either way, you can get around the issue from TWRP by deleting the file /system/app/SetupWizard.apk using the built-in file manager or ADB.
Click to expand...
Click to collapse
Agreed, first try to wipe again. Factory reset (2x) for good measure, wipe cache, wipe Dalvik, Flash ROM, flash Gapps, boot. May even wipe cache/dalvik again after flashing. Not usually needed, but sometimes KF can get stubborn.
chemo1191 said:
Agreed, first try to wipe again. Factory reset (2x) for good measure, wipe cache, wipe Dalvik, Flash ROM, flash Gapps, boot. May even wipe cache/dalvik again after flashing. Not usually needed, but sometimes KF can get stubborn.
Click to expand...
Click to collapse
Question...I am too having this issue. Only difference is something happened to my USB and my computer can't install the device files anymore so I'm flashing the ROMs thru ROM manager now since I can't connect my phone to the computer. I know I'm using the right gapps but if I delete the apk for the setup wizard how will i be able to sign into my google account?

Stuck in boot loop after flashing CM7

Hi all, hoping this is a stupidly simple fix. I wanted to update to latest stable CM7 and so downloaded and flashed it from CWRecovery,
I also ran the factory reset, and cleared the cache.
When I boot, it shows the blue loading screen, then comes to the "Welcome to ADR6300" and reverts to the CyanogenMod7 loading screen..
Then, it keeps bouncing back and forth between these two screens until I pull the battery...
You didn't mention the order of what you did. Assuming you have no valuable data, I would just start over.
Reboot into recovery
Wipe system
Factory reset
Flash ROM
Flash GAPPs (if desired)
Reboot into ROM
Also, ensure you're on the latest CWM, first.
[Solved]
PonsAsinorem said:
You didn't mention the order of what you did. Assuming you have no valuable data, I would just start over.
Reboot into recovery
Wipe system
Factory reset
Flash ROM
Flash GAPPs (if desired)
Reboot into ROM
Also, ensure you're on the latest CWM, first.
Click to expand...
Click to collapse
Worked perfectly! Thank you!!
Apparently the problem was having the wrong version of GAPPs. I was reinstalling but Wiping system was the step I had skipped!

CM13 not booting

After flashing TWRP with Odin, I boot into recovery and wipe the dalvik cache. I then go to install the CM13 zip file, and it works. I wipe Dalvik again and reboot in the os. This is where it just shows the CM boot screen infinitely. Nothing else. What is up. I am using the latest TWRP and CM13 release.
Try this:
1. Wipe cache, dalvic cache, data, system
2. Install CM13 again, along with your gapps(google apps if you didn't know, custom ROMs never come with them, optional)
3. Boot it, it should work
You cannot switch ROMs without wiping data. Bad things happen.
You must clean flash when:
1. Switching between a stock ROM to a custom ROM
2. Downgrading Android versions (5.1 to 5.0)
3. Switching custom ROMs (I.E. CM13 to AICP)
4. When the ROM's thread warns to (switching keys)
5. Switching between nightly builds and stable.
When you're updating nightlies, you shouldn't have to though.
RDChase said:
Try this:
1. Wipe cache, dalvic cache, data, system
2. Install CM13 again, along with your gapps(google apps if you didn't know, custom ROMs never come with them, optional)
3. Boot it, it should work
You cannot switch ROMs without wiping data. Bad things happen.
You must clean flash when:
1. Switching between a stock ROM to a custom ROM
2. Downgrading Android versions (5.1 to 5.0)
3. Switching custom ROMs (I.E. CM13 to AICP)
4. When the ROM's thread warns to (switching keys)
5. Switching between nightly builds and stable.
When you're updating nightlies, you shouldn't have to though.
Click to expand...
Click to collapse
Just did it, it still seems to be booting like it previously was. Wiped cache, dalvic, data, and system and then installed CM13 and gapps. Still booting as I write this.
Since that failed, check your download, make sure nothings bad. If its bad, redownload, if not, idk.
If you post your recovery logs, or what the console says, that will help me figure out what's going on.
Also, is your phone the triband model (l710t)?
Are you flashing anything else at the same time?
The more info you give, the better.
RDChase said:
Since that failed, check your download, make sure nothings bad. If its bad, redownload, if not, idk.
If you post your recovery logs, or what the console says, that will help me figure out what's going on.
Also, is your phone the triband model (l710t)?
Are you flashing anything else at the same time?
The more info you give, the better.
Click to expand...
Click to collapse
I've kind of given up at this point. Even CM12 doesn't work. The only thing that seems to work is the stock rom. My phone is the regular SPH-L710 model. I didn't even know the L710t was a thing.
I have the same problem, and sometimes it boot in the system setup mode, but the sensor is not working, i can turn on airplane mode, reboot or power off, and sensor works, what happend i dont know((
ovil101 said:
After flashing TWRP with Odin, I boot into recovery and wipe the dalvik cache. I then go to install the CM13 zip file, and it works. I wipe Dalvik again and reboot in the os. This is where it just shows the CM boot screen infinitely. Nothing else. What is up. I am using the latest TWRP and CM13 release.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2755793
helped)))
1vankill1 said:
http://forum.xda-developers.com/showthread.php?t=2755793
helped)))
Click to expand...
Click to collapse
That just seems to be a stock rom.
yes it stock rom, after it was installed, I was able to install 13 cm

Need help to install custom rom

Hello,
I don't know why my lg g3 phone doesn't want boot on custom rom.
I have the LG G3 d855 model, 16gb memory and here are my procedure to install every custom rom :
1. Flash Stock ROM using LGUP (the version of the firmware is not important but the possibility to root is)
2. Install KingRoot and get root
3. Install AutoREC and enter to the recovery
8. Flash Recovery TWRP 3.1.0-2
9. Reboot to the new recovery
10. ADVANCED WIPE (wipe cache, dalvik cache, data and SYSTEM)
11. Flash baseband 21C
12. Flash CUSTOM rom
13. Wipe cache and dalvik cache
14. Flash Gapp
15. Wipe cache and dalvik cache
16. Reboot
I think I did nothing bad...
but the phone does not start and it stays at the initial logo screen (not the LG logo, but the custom rom logo). I waited over 10 minutes to boot but nothing. Even though I install the identical rom again or install an anoter rom, each time the same issue.
This happens with all custom rom (xenonhd, resurrection remix, and now lineageOS)
I can use and boot on stock rom but each time I want to install a custom rom, my phone doesn't want to boot. The phone display stays at the initial rom logo screen.
It seems that I am alone to have this problem.
I don't know why and I search everywhere to find out the solution...
PS : My phone never restart by itself. I never have bootloop with my phone when I using stock rom and same with custom rom..
The problem is the boot with a custom rom. The phone don't want to boot and stay on logo loading...
Any suggestion may be help.
Thank you.
1. Once you installed TWRP you don't have to go back to stock to switch roms. From then on you can just download zips and flash them.
2. You need to delete everything (including system) except internal and external storage ( so you can still flash the zip for xceed, otherwise you will delete it). Remember that you will lose all your apps including your data with it. You can backup them with titanium backup tho. Pictures and video's will still be there as they are stored on the internal or external storage.
3. You also need to flash the GAPPS package after flashing rom, for xceed (7.1.1), pick nano (ARM)
4. Wipe cache and dalvik after flashing and reboot.
5. Make a backup before you do so !!!!!!
Good luck.
Jornwitt said:
1. Once you installed TWRP you don't have to go back to stock to switch roms. From then on you can just download zips and flash them.
2. You need to delete everything (including system) except internal and external storage ( so you can still flash the zip for xceed, otherwise you will delete it). Remember that you will lose all your apps including your data with it. You can backup them with titanium backup tho. Pictures and video's will still be there as they are stored on the internal or external storage.
3. You also need to flash the GAPPS package after flashing rom, for xceed (7.1.1), pick nano (ARM)
4. Wipe cache and dalvik after flashing and reboot.
5. Make a backup before you do so !!!!!!
Good luck.
Click to expand...
Click to collapse
Hello,
1. I think that but with specific rom, some people tell us to flash stock rom before flashing a custom rom. eMMC bug related ?
2. Deleting the system changes nothing because the system is wiped when I flash the rom, right ?
3. if the rom boot first then I will install Gapps. Else, I don’t install because the rom doesn’t want to boot.
1. Well .. I've been switching between fulmics,xceed,rr, .. etc without any problem so no, there is no need to go back to stock everytime.
2. Try it, you won't be able to boot until you flash a new rom, but it could help. That's why you take a backup in the first place. It is more 'clean' and if you don't try it you won't know.
3. Sometimes you have to flash gapps directly after the rom or you will be in for a bad time if you do afterwards.
Once you have TWRP recovery installed it's the easiest thing ever to flash a new rom. Make sure your zip files are downloaded okay. Download the MD3 to check it. Try to download via MEGA app or so, because browsers downloads tend to have errors sometimes.
Apart from that. Don't root via kingroot. They have had some suspicious cases where malware was installed on the phone when rooting.
If nothing's works. Go back to full stock through KDZ, root wit your PC, install TWRP via autorec, go to recovery, wipe everything, install modem 21C, install rom and gapps, wipe cache, reboot. Don't try anything other than that.
I have the same problem
Jornwitt said:
1. Well .. I've been switching between fulmics,xceed,rr, .. etc without any problem so no, there is no need to go back to stock everytime.
2. Try it, you won't be able to boot until you flash a new rom, but it could help. That's why you take a backup in the first place. It is more 'clean' and if you don't try it you won't know.
3. Sometimes you have to flash gapps directly after the rom or you will be in for a bad time if you do afterwards.
Once you have TWRP recovery installed it's the easiest thing ever to flash a new rom. Make sure your zip files are downloaded okay. Download the MD3 to check it. Try to download via MEGA app or so, because browsers downloads tend to have errors sometimes.
Apart from that. Don't root via kingroot. They have had some suspicious cases where malware was installed on the phone when rooting.
If nothing's works. Go back to full stock through KDZ, root wit your PC, install TWRP via autorec, go to recovery, wipe everything, install modem 21C, install rom and gapps, wipe cache, reboot. Don't try anything other than that.
Click to expand...
Click to collapse
Hello,
I have a question.
Can you give me a gapp 100% compatible with all custom rom with android 7.1.2, because i think opengapp are not reliable. Maybe the gapp will cause my issue and the rom won't boot.
Can i use this one https://forum.xda-developers.com/on...isited-slim-gapps-6-0-7-0-unofficial-t3462088 ?
I always use PICO version of gapp
Thank

Categories

Resources