I recently bought a note 4 DE from ebay and it came loaded with jsmine rom. I was excited none the least but i noticed the phone would get really hot after a time and decided to switch to cyanogem 13.0. The first thing i noticed wad wifi would not turn on so i twrp recovered a backup and all was good again but still getting hot so i tried to upgrade to jasmine 6.0 and once again the wifi wouldnt turn on. Restored twrp backup and now wifi will not turn back on at all. Everything else works. Factory restore doesnt fix it. What should i do?
Straman1 said:
I recently bought a note 4 DE from ebay and it came loaded with jsmine rom. I was excited none the least but i noticed the phone would get really hot after a time and decided to switch to cyanogem 13.0. The first thing i noticed wad wifi would not turn on so i twrp recovered a backup and all was good again but still getting hot so i tried to upgrade to jasmine 6.0 and once again the wifi wouldnt turn on. Restored twrp backup and now wifi will not turn back on at all. Everything else works. Factory restore doesnt fix it. What should i do?
Click to expand...
Click to collapse
I'm having the exact same issue and can't a fix anywhere.
Related
I flashed cm9 last night and everything was fine it was a nice test build but I wanted to go back to stock. I restored my backup of Virtuous beta 1 and now my wifi is trying to turn on forever.
Basically it says that "turning on wifi" but it never turns on....
Is my tablet now a very expensive paper weight? Or is there a fix for this?
Same happened to me last night, after trying a few different ROMs including CM9 as the last one. I went back to my ICS rooted via nandroid restore. Wifi would not turn on. So I just booted into CWM and flash the same ICS rooted ROM again (without wipe) Rebooted and WiFi back.
Hello everyone,
I searched the forums for awhile but could not find a satifying answer for my question. So i am hoping you guys will have an answer for me.
First of all i would like to point out that i am not looking for an answer for how to unbrick the phone. There are several guides and hopefully when i get home i will be able to fix the problem. *Fingers crossed*
I did not have my Galaxy S for long. After getting it and installing KIES and updating my firmware the battery life what terrible so I rooted the phone and then installed Gingerbread 2.3.6 JVU. it worked like a charm.
Yesterday when I was playing with the CWM application, I decided that i was going to back up the phone and backed it up using the application. This morning one of my programs was acting weird and I decided to restore the backup I have done yesterday.
Upon going into applications and CWM, I chose the restore option and started the process. Everything was going smoothly, the phone was plugged in to the charger as well.
When the phone rebooted after the initial process I am stuck at logo screen. i can go into download mode (That is why I am hoping that I will be able to unbrick it) however that is as far as the phone goes. When I try to go into CWM Recovery mode, I am once again welcomed by the phone getting stuck at logo screen.
Does anyone have any idea as to why this might have happened? To avoid future problems is there any extra steps I should have taken before using the CWM restore function?
Thanks for the help.
m_hawkmoon said:
Hello everyone,
I searched the forums for awhile but could not find a satifying answer for my question. So i am hoping you guys will have an answer for me.
First of all i would like to point out that i am not looking for an answer for how to unbrick the phone. There are several guides and hopefully when i get home i will be able to fix the problem. *Fingers crossed*
I did not have my Galaxy S for long. After getting it and installing KIES and updating my firmware the battery life what terrible so I rooted the phone and then installed Gingerbread 2.3.6 JVU. it worked like a charm.
Yesterday when I was playing with the CWM application, I decided that i was going to back up the phone and backed it up using the application. This morning one of my programs was acting weird and I decided to restore the backup I have done yesterday.
Upon going into applications and CWM, I chose the restore option and started the process. Everything was going smoothly, the phone was plugged in to the charger as well.
When the phone rebooted after the initial process I am stuck at logo screen. i can go into download mode (That is why I am hoping that I will be able to unbrick it) however that is as far as the phone goes. When I try to go into CWM Recovery mode, I am once again welcomed by the phone getting stuck at logo screen.
Does anyone have any idea as to why this might have happened? To avoid future problems is there any extra steps I should have taken before using the CWM restore function?
Thanks for the help.
Click to expand...
Click to collapse
Maybe your backup was corrupted somehow. You could have tried wiping the dalvik cache after restoring your backup (before rebooting), but its too late now. Since you can get into download mode, you can easily fix the problem (your device is just soft bricked - nothing to worry too much about).
Theonew said:
Maybe your backup was corrupted somehow. You could have tried wiping the dalvik cache after restoring your backup (before rebooting), but its too late now. Since you can get into download mode, you can easily fix the problem (your device is just soft bricked - nothing to worry too much about).
Click to expand...
Click to collapse
The phone rebooted automatically. Did not give me the chance to do anything beforehand.
As you said the phone was soft bricked so when i got home that day i just fixed it. No problem. However I am really really into getting to find out how a 1 day old back up can get corrupted.
I have an LG G2 ( d802 - International) which has some issues with wifi and Bluetooth. On my phone mac addresses(both wifi and Bluetooth) are not showing up. It happened yesterday when I was using my phone which was running cm13, all of a sudden the wifi stopped so at first I tried to turn it off and on again, which didnt seem to work because the wifi didnt turn on (I dont really need bluetooth as of my daily life). So I rebooted my phone and the problem persisted. So i decided to factory reset with TWRP ( I normally reset once every so often to speed up my phone again , and at this point my phone was getting really slow). Which I did, but then something wired happened... The upgrading android dialog box came up after the reset and it showed ~140 apps. But normally that wouldnt happen after a reset. I didnt mind that and checked to see if the wifi worked again, yet no luck. So I went for a full format of data, which also popped up with the upgrading android. So I thought maybe it was to do with the rom, and decided to try out some other rom. So i had 2 roms on my sdcard at that time, Dorimanx-V9.7-LP and the stock lg rom. At first when i tried the Dorimanx rom it didnt work and wasnt booting right so I was not bothered to fix and I went for the stock rom which worked.. and it happened again... upgrading android dialog box. So i started researching and saw it mention that this could be a cause of bootloaders not being the right version, now i do not know a lot about bootloaders so I couldnt really do anything. I tried to update twrp with auto rec ( i got the apk thru usb from pc to phone), which worked yet still no fix.
*Seen some other threads and tried the following with no success*
Deleting the contents of : /data/misc/wifi/
Factory resetting
Details:
Lg G2 (D802)
Wifi and bluetooth not working ( No mac addresses)
Running :Stock Lollipop rom for lg
Rooted
Twrp version : 2.8
Any Help would be appreciated, Thanks in advance! :good:
so about 2 moths ago I installed ressurection remix on my oneplus one. In those 2 months my phone wouldn't start up 3 times. So i see the logo to start up but he keeps loading. When i go to twrp and reboot the system it keeps loading. the only way to fix it is by installing RR again. This problem happens always when my phone was in my pocket and it turned himself off so i start it up and it keeps loading. Does anyone know a solution for this problem?
caopi0304 said:
so about 2 moths ago I installed ressurection remix on my oneplus one. In those 2 months my phone wouldn't start up 3 times. So i see the logo to start up but he keeps loading. When i go to twrp and reboot the system it keeps loading. the only way to fix it is by installing RR again. This problem happens always when my phone was in my pocket and it turned himself off so i start it up and it keeps loading. Does anyone know a solution for this problem?
Click to expand...
Click to collapse
ohh boi,how do you know the phone is "himself" or "herself"?
flash latest rr build and see if the problem persist...
caopi0304 said:
so about 2 moths ago I installed ressurection remix on my oneplus one. In those 2 months my phone wouldn't start up 3 times. So i see the logo to start up but he keeps loading. When i go to twrp and reboot the system it keeps loading. the only way to fix it is by installing RR again. This problem happens always when my phone was in my pocket and it turned himself off so i start it up and it keeps loading. Does anyone know a solution for this problem?
Click to expand...
Click to collapse
I am in the same boat as you.
I have been running RR for almost 3-4 months and it did the exact same thing you described at least 5 times. Nothing (Clearing cache / flashing new versions/ old versions/ different gapps/ twrp updates / nandroid backup restore) would fix it except letting it cool down for a day and try booting it up the next day. If you're lucky enough, it would work. I never tried resetting it because I didn't want to lose my data.
It happened again day before day yesterday and my phone's been dead ever since. Tried everything, again, but no luck this time. I have finally decided to put my lazy ass to work and take backup using MTP in TWRP and flashing stock ROM. The data is being backed up as of now.
The procedure is long & a pain in the ass but looks like there is no other option.
Labor day holiday wasted. -.-'
So to give a backstory, yesterday night, I ****ed my phone. It got corrupted, but I made a backup before. So today I tried to restore the backup. That did not go very well. So I searched up solutions and found out that it might be the os that is corupted after restoring the backup. So I side-loaded the official oxygen os 9.0.2. That worked and right now I got all my data back+my device is working kinda. After it started I saw that it's not conected to wifi. So I tryed to turn on the wifi but after like 3-4 seconds of trying to start the wifi, it automaticly turns itself off. Anyone got an idea on how to fix this?
Edit 1: My MAC adress is 02:00:00:00:00:00? Uh this does not seem right.
Mighty_Pig said:
So to give a backstory, yesterday night, I ****ed my phone. It got corrupted, but I made a backup before. So today I tried to restore the backup. That did not go very well. So I searched up solutions and found out that it might be the os that is corupted after restoring the backup. So I side-loaded the official oxygen os 9.0.2. That worked and right now I got all my data back+my device is working kinda. After it started I saw that it's not conected to wifi. So I tryed to turn on the wifi but after like 3-4 seconds of trying to start the wifi, it automaticly turns itself off. Anyone got an idea on how to fix this?
Edit 1: My MAC adress is 02:00:00:00:00:00? Uh this does not seem right.
Click to expand...
Click to collapse
I got the exact same problem. Today too. I tried booting from slot a in recovery then that is when it started.
Any solution?
I did go into twrp tried wiping system, then reflashing oos9.0.2 and it was a no go.
I then went into twrp and wiped data and it worked. Of course all data was gone and had to clean install. Hope you have a data back up in twrp.