Related
So, before I start this, Yes I was a noob. I didnt make a nandroid backup from when I first rooted my phone and everything worked 100%. I didnt read, and I guess its now biting me in the ass.
The past few months Ive been having issues with Wifi, it continuously says "Unable to scan for networks". I did a factory reset about a week and a half ago and for the first time my wifi was able to connect, however it was dropping out every couple minutes. Wouldnt even stay connected to install any market updates.
I figured that it was something with my dying router(Which Ive since replaced) so I flashed in BAMF to see if I could keep my wifi connection with another rom. Ive been using VirusROM(Love it even though its out od date). I wiped and flashed in BAMF, and restarted. When I restarted, I had no wifi again. Since then, Ive been trying out different ROMS and kernels in hopes that I would find something that would fix it. Nothing did.
After this I figured that I would just do another factory reset and go from there, however with all of the times Ive done the factory resets it never actually gets reset. Does it wipe my info? Yes, but it boots back up with all of the portions of whatever ROM I had installed last. Not reset. So now Ive ended up with two problems.
1. I still have no wifi
2. I cant factory reset so that I can figure out what is going on with my wifi.
Ive wiped Cache/Batt Stats/Davlick and done a factory reset literally six times in a row to hopefully clean EVERYTHING OUT to no avail. Any help with this would be greatly appreciated. I hope Im just missing something small because Im still new to android.
Edit: I DO NOT use kernel manager and I dont use ROM manager to flash it in, I flash everything in through recovery.
McLabia said:
So, before I start this, Yes I was a noob. I didnt make a nandroid backup from when I first rooted my phone and everything worked 100%. I didnt read, and I guess its now biting me in the ass.
The past few months Ive been having issues with Wifi, it continuously says "Unable to scan for networks". I did a factory reset about a week and a half ago and for the first time my wifi was able to connect, however it was dropping out every couple minutes. Wouldnt even stay connected to install any market updates.
I figured that it was something with my dying router(Which Ive since replaced) so I flashed in BAMF to see if I could keep my wifi connection with another rom. Ive been using VirusROM(Love it even though its out od date). I wiped and flashed in BAMF, and restarted. When I restarted, I had no wifi again. Since then, Ive been trying out different ROMS and kernels in hopes that I would find something that would fix it. Nothing did.
After this I figured that I would just do another factory reset and go from there, however with all of the times Ive done the factory resets it never actually gets reset. Does it wipe my info? Yes, but it boots back up with all of the portions of whatever ROM I had installed last. Not reset. So now Ive ended up with two problems.
1. I still have no wifi
2. I cant factory reset so that I can figure out what is going on with my wifi.
Ive wiped Cache/Batt Stats/Davlick and done a factory reset literally six times in a row to hopefully clean EVERYTHING OUT to no avail. Any help with this would be greatly appreciated. I hope Im just missing something small because Im still new to android.
Edit: I DO NOT use kernel manager and I flash everything in through recovery.
Click to expand...
Click to collapse
I'm sure there's an RUU out there that will take your phone back to stock but I honestly doubt that's the issue here. What radio version are you using? Have you tried flashing different radios to see if that would fix it. You can find a list here http://forum.xda-developers.com/showthread.php?t=1045081. Also what ROM are you currently on?
When you install a ROM, it modifies the /system directory which is responsible for everything, how the rom looks, included apps, drivers etc.
When you do a factory reset, I'm guessing through recovery, it is only clearing the /data and /cache partitions.
You will have to flash a stock RUU to get it to truly go back to the day you got it.
Here are instructions on how to return to stock:
http://forum.xda-developers.com/showthread.php?t=1009423
devindpotts said:
I'm sure there's an RUU out there that will take your phone back to stock but I honestly doubt that's the issue here. What radio version are you using? Have you tried flashing different radios to see if that would fix it. You can find a list here http://forum.xda-developers.com/showthread.php?t=1045081. Also what ROM are you currently on?
Click to expand...
Click to collapse
The ROM Ive been on hasnt mattered. Ive jumped through BAMF, the new Cubed Rom, the Deodexed stock debloat and Virus' Airborne(which is my daily driver). Ive done the different radios. I was on the v2 leaked for a while, then I switched to the new 3g and old 4g to see if its worked but it hasnt. I may have to try out the original one and see if that works, but I havent had wifi since before I flashed in the leaked radio when it came out.
isdnmatt said:
When you install a ROM, it modifies the /system directory which is responsible for everything, how the rom looks, included apps, drivers etc.
When you do a factory reset, I'm guessing through recovery, it is only clearing the /data and /cache partitions.
You will have to flash a stock RUU to get it to truly go back to the day you got it.
Here are instructions on how to return to stock:
http://forum.xda-developers.com/showthread.php?t=1009423
Click to expand...
Click to collapse
Gotcha. Trying this now. I will make sure to make a nandroid this time if it works. lol.
@isdnmatt: Thanks, that got rid of my recovery problem
Still having wifi issue though. 100% out of the box stock and I get the "Unable to scan for networks
**** me, I should have read that before I did it. Now I have to reroot. Goddamnit.
Have had the same problem with WiFi before and after ADB root. It will sometimes forget both my home and work networks. I've found the problem usually occurs when I'm connected then move put of range. A reboot fixes the problem sometimes. Other times I have to re-enter my settings. I'm still on the stock Rom, nothing custom.
Sent from my ADR6400L using XDA Premium App
ILMF said:
Have had the same problem with WiFi before and after ADB root. It will sometimes forget both my home and work networks. I've found the problem usually occurs when I'm connected then move put of range. A reboot fixes the problem sometimes. Other times I have to re-enter my settings. I'm still on the stock Rom, nothing custom.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Thats a separate issue than what Im having. Im not having issues with it forgetting my networks. I cant scan for networks.
I am thinking of downgrading the radio.
EDIT: after LOTS of research here, I upgraded to MR2 and Gingervitis. All of my WiFi issues are gone.
Sent from my TBolt using XDA Premium App
After flashing a new version of CM11, i found myself in a loop upon startup where many of the core applications of android stopped working. When i reverted back to the old version that worked(I didn't have a backup saved but rather i flashed the older nightly of the rom again), I noticed that my home button, lock screen, and notification bar/toggle screen wasn't working any more. I looked into it and looked at my apps, and saw an unnamed app with the description "com.android.keyguard". upon looking this process up, i found out that when people disabled this process their home button, lock screen, and notification bar stopped working (coincidental eh?), and decided that this was the source of the problem.
Is there any way to load on a new, fresh version of "com.android.keyguard" or should i just do a factory reset? I would prefer to save my local data, but if i must do it in order to have a phone that does anything useful, i obviously will.
If I need to do a factory reset, what is the cleanest and smartest method of doing so? I know titanium backup can cause a lot of problems (and in this case i'm worried it will duplicate com.android.keyguard), but I assume there is some sort of method that makes a factory reset while retaining the bulk of user data very easy. am i correct?
Do a full wipe and flash again, check the md5 of your download.
Only use titanium for use apps, never system apps or settings. There is no easier way to change rom.
I have the same problem now..I have did the full reset.But the problem is not going at all.
What should I do?
Jahid4 said:
I have the same problem now..I have did the full reset.But the problem is not going at all.
What should I do?
Click to expand...
Click to collapse
Flash back to stock and start over.
Beamed in by telepathy.
Would like some help. I have flashed CM 11 and can't make calls. It says mobile network not available. Tried flashing AOKP rom as well and same thing. Mobile data works fine, although i have gotten a popup twice that says 'Google Play Services not supported by your device, please contact your manufacturer' (no noticible issues from this, google stuff i've tried so far works). I have included a screenshot so you can see my baseband and rom version, etc.
Now, i had a great deal of trouble getting a rom flashed to start with, CWM put me into a bootloop and TWRP wouldn't flash anything because it said it couldn't mount /storage when i tried. Used Philz advanced CWM (love it btw, will be using it from now on). Still wouldnt flash the hltespr specific CM11 version so had to use the unified hlte version (it gave me the status 7 asserts issue, but editing the asserts out just gave me a bad file error when flashing). I wiped data/cache/dalvik between each flashing. I don't know if any of that would have bearing on this problem, just including any details i can. Any advice?
Verilin said:
Would like some help. I have flashed CM 11 and can't make calls. It says mobile network not available. Tried flashing AOKP rom as well and same thing. Mobile data works fine, although i have gotten a popup twice that says 'Google Play Services not supported by your device, please contact your manufacturer' (no noticible issues from this, google stuff i've tried so far works). I have included a screenshot so you can see my baseband and rom version, etc.
Now, i had a great deal of trouble getting a rom flashed to start with, CWM put me into a bootloop and TWRP wouldn't flash anything because it said it couldn't mount /storage when i tried. Used Philz advanced CWM (love it btw, will be using it from now on). Still wouldnt flash the hltespr specific CM11 version so had to use the unified hlte version (it gave me the status 7 asserts issue, but editing the asserts out just gave me a bad file error when flashing). I wiped data/cache/dalvik between each flashing. I don't know if any of that would have bearing on this problem, just including any details i can. Any advice?
Click to expand...
Click to collapse
Have you upgraded your bootloader to NH7? I know most of the newly-updated CM-based ROMs require you to be on NH7 before flashing. That's most-likely why you weren't able to flash the htlespr ROMs. The unified ROMs no longer include the correct APNs for Sprint, so that's why you don't get service on it. I don't know why mobile data works on it.
topherk said:
Have you upgraded your bootloader to NH7? I know most of the newly-updated CM-based ROMs require you to be on NH7 before flashing. That's most-likely why you weren't able to flash the htlespr ROMs. The unified ROMs no longer include the correct APNs for Sprint, so that's why you don't get service on it. I don't know why mobile data works on it.
Click to expand...
Click to collapse
No, didnt realize that i needed to do that. I'll do some research on it because i don't have any idea how to update the bootloader. If you have a link to a good tutorial that would be wonderful! Thanks!
Ok so i tried that, found this tutorial, followed it, no luck. Tried full wipe/reset after that to see if it would let me install the hltespr versions, still no dice. Same situation, mobile data works, calls don't. Will have to wait till daylight to try texting so i don't wake anyone up but i suspect that texting won't work either. Has anyone experienced this and fixed it? Lol i really didn't drop $100 on a phone to be saddled with all the Samsung and Sprint baloney that it comes with, don't wanna unroot....
Bump
Anyone have ideas on this? Have continued to try fooling around with the udater-script file to resolve the status 7 problem so I can install the hltespr variant, still no dice. Please someone help!
Bump!
Sorry, I typically don't have access to XDA forums on the weekend, so couldn't answer your question till now.
You flashed only the baseband/modem, not the Bootloader. If you want to update the Bootloader, you need to use ODIN to flash the Complete OTA NH7 Update.
In order to update the Bootloader, you need to make sure that you use the PC ODIN (not the mobile one) and that you completely power off the phone before you enter download mode (don't access download mode by using the extended power menu when shutting down the phone). I don't think you need to do the battery pull that Freeza had in his instructions (I didn't do it when I ODIN-flashed the NH7 OTA update), but it wouldn't hurt to do it.
Thanks for that, I will try it as soon as I get home tonight! The next thing I had decided to try was to unroot, to back to stock, then try flashing that before I start with the custom recovery and ROM. Do you think I should do that first before doing the whole thing or could that work just flashing that with my phone as-is?
Verilin said:
Thanks for that, I will try it as soon as I get home tonight! The next thing I had decided to try was to unroot, to back to stock, then try flashing that before I start with the custom recovery and ROM. Do you think I should do that first before doing the whole thing or could that work just flashing that with my phone as-is?
Click to expand...
Click to collapse
Well, I always recommend a full wipe (data, system, cache, dalvik) when flashing ROMs. I haven't wiped my internal storage or external storage since I got the phone, so that's not really necessary.
I don't think that unrooting your current ROM is necessary. Flashing the ODIN OTA update will automatically remove root access, so that's not an issue. Here's the steps I took when I updated to NH7 and installed my current ROM (see my sig):
Make a Nandroid backup.
I always do this just so I have a "record" of what I left behind. It also allows me to have all of my app data that I can restore via Titanium Backup (you have to buy the Pro version in order to restore specific apps from a Nandroid backup). I always store a copy on my ext. storage and on dropbox.
Do a full wipe
As I mentioned above, I always wipe data, system, and the caches when flashing ROMs. While I have to take some time to get the new ROM exactly as I like it, it minimizes any potential FCs and errors that some people get when dirty flashing.
Install NH7 all-in-one via ODIN
I installed the NH7 via ODIN. Please note that this is the fully stock, unrooted ROM and will also install the stock recovery.
Let the phone boot and connect to Sprint. Update Profile and PRL.
I do this periodically whenever I go back to stock (from AOSP). I rarely have connection issues, but updating the PRL an profile can help with those.
Install a custom recovery using ODIN.
My recovery of choice is TWRP, but others have found just as much success with CWM and Philz. Just make sure that you're installing the correct version of the recovery (4.4.X version, not the 4.2.X version). I always reboot to the main system after installing a recovery, but that's up to you. In the rest of this post, I'll say "TWRP," but I really mean "custom recovery."
[OPTIONAL] Make a Nandroid backup of the stock ROM
I always do this, but I recognize that it's not necessary, especially since we can just ODIN back to this image at any time. I just like having the option of having a stock backup on the device (in case catastrophe strikes while I'm away from a computer).
Use TWRP to flash your AOSP ROM of choice.
If you haven't installed any apps or messed around with the settings, you shouldn't have to wipe before flashing, but (in case you haven't noticed by now), I tend to err on the side of caution, specifically: wiping everything (data, system, and the caches) before I flash anything.
Set up the ROM how you like it and [OPTIONAL] make one last Nandroid Backup
Whenever I set up a new ROM to the exact way I like it (statusbar settings, accounts set up, apps installed and configured, etc), I make a nandroid backup of my device. This allows me to go back to that "fresh" image whenever something happens to the device and I don't have to muddle around fixing those minor tweaks. Again, I tend to err on the side of wiping the phone too often and taking too many backups, but I've rarely had issues with my phone and ROMs because of it (to the point where I can spend most of my XDA time helping others with their phones), so it might be prudent to follow the advice.
Anyways, that's how I upgraded to NH7 and installed a custom ROM. Others may take a less conservative approach and you're welcome to adjust any of the optional steps.
Hope this helps!
-Topher
OK, did all that successfully, when it went back to stock stiil had the same issue. Mobile data functions, mobile network for calls/SMS doesn't. Did the whole update prl/profile and even tried reactivating from settings, still nothing. Was able to install custom recovery (Philz) and the hltespr CM11 variant instead of the unified generic version. Still has the same problem, mobile network not available. Everything else works perfectly. I did verify in settings that it still wound up as the NH7 after everything I did. Note I did a full reset before each thing that got flashed in this process, and one more for good measure after. Let it boot to the system between steps too.
Lol I've been rooting and switching between ROMs for years and have never encountered anything like this. I'm stumped....
Verilin said:
OK, did all that successfully, when it went back to stock stiil had the same issue. Mobile data functions, mobile network for calls/SMS doesn't. Did the whole update prl/profile and even tried reactivating from settings, still nothing. Was able to install custom recovery (Philz) and the hltespr CM11 variant instead of the unified generic version. Still has the same problem, mobile network not available. Everything else works perfectly. I did verify in settings that it still wound up as the NH7 after everything I did. Note I did a full reset before each thing that got flashed in this process, and one more for good measure after. Let it boot to the system between steps too.
Lol I've been rooting and switching between ROMs for years and have never encountered anything like this. I'm stumped....
Click to expand...
Click to collapse
Dumb question but are you a Verizon customer or Sprint?
Sent from my SM-G900P using Tapatalk
Sprint, I've had big red before but when they did away with unlimited data it wasn't worth paying their high rates.
Bump!
Anyone have any ideas on this? I am just confounded as to why this continues even after being reset to stock.
Same Issue!!!
I have the exact same issue and have been trying to resolve it for the last 2 days... Did you find a solution?
I have the same problem on a Samsung Mega. LTE and 3G data work but phone won't dial if LTE is active. It WILL voice dial if only 3G is active. Sprint. CM11.
I had this problem after flashing ROMs as well, but went into Settings>Connections>More Networks>Mobile Networks>Network Mode and selected LTE/CDMA....no network had been selected. That fixed me right up. Weird part is, I could still avcess the web without WiFi....but couldn't make calls or ise my bluetooth headset until I had performed the above steps. Hope that helps.
thanks forget the little things reset wifi and sprint cell extender
GAPO said:
I had this problem after flashing ROMs as well, but went into Settings>Connections>More Networks>Mobile Networks>Network Mode and selected LTE/CDMA....no network had been selected. That fixed me right up. Weird part is, I could still avcess the web without WiFi....but couldn't make calls or ise my bluetooth headset until I had performed the above steps. Hope that helps.
Click to expand...
Click to collapse
I have been running various flavors of AOKP ROM's on SG3's for several years now. I recently obtained a refurb S3 and set it up to do the usual.
It came with stock TW 4.4.
Using ROM Manager I installed CWM and made an image of the stock phone. I then installed my AOKP variant and loaded my apps, blah blah. All is good.
I've since decided I want to revert back to TW for awhile. I restored my nandroid and I get the interminable GAPPS failure messages. I have on occasion been able to get it to calm down and have a working phone, usually be uninstalling play app and clearing framework services cache. This is extraordinarily painful and doesn't always work. I've done all the usual, reinstall GAPPS, etc., and basically it is a MAJOR headache just trying to get the image to function.
But....When it does work the phone does not see my SIM card, IMEI, nothing.. I have no mobile connectivity. Restoring the AOKP nandroid brings me back to a fully functioning phone.
So my questions are:
Can anyone explain to me why the TW nandroid is giving all these GAPPS issues and how to circumvent/fix it?
Why is the system seeming to lose my IMEI/SIM info? Is there a way to fix that? Should I have done something different in my setup/nandroid creation?
Lastly - I don't quite understand how CWM works. There is a recovery image. When I do factory reset, is it resetting to this recovery image as opposed to the factory TW? I seem to think so, when I do a reset I see the android version is not what my factory one is.
Thanks all.
I updated my T-Mobile Note-8 to Oreo (CRC2) via OTA update. Ever since my "camera keeps stopping" after taking a pic.. Anybody else here with similar experience?
Things I already tried:
1. Cleared system cache, did NOT work.
2. Cleared camera app cache/data, did NOT work.
3. Cleared gallery app cache/data, did NOT work.
4. Changed to internal/phone memory storage (in the camera settings), did NOT work.
5. Tried safe mode & camera still crashed, did NOT work.
Quick google search says many other people are facing this issue (different devices). I'm surprised there is NO posts here asking about this...
My only option at this point is to do a complete factory reset. But I hate doing that because of all the setup steps involved in making it behave correctly (as I like it).
Any help appreciated.
maxie.maverick said:
I updated my T-Mobile Note-8 to Oreo (CRC2) via OTA update. Ever since my "camera keeps stopping" after taking a pic.. Anybody else here with similar experience?
Things I already tried:
1. Cleared system cache, did NOT work.
2. Cleared camera app cache/data, did NOT work.
3. Cleared gallery app cache/data, did NOT work.
4. Changed to internal/phone memory storage (in the camera settings), did NOT work.
5. Tried safe mode & camera still crashed, did NOT work.
Quick google search says many other people are facing this issue (different devices). I'm surprised there is NO posts here asking about this...
My only option at this point is to do a complete factory reset. But I hate doing that because of all the setup steps involved in making it behave correctly (as I like it).
Any help appreciated.
Click to expand...
Click to collapse
I had Samsung Experience Home keep FCing on me. Had to do a reset. Sucked. 1 other thing you might want to try is to go into Recovery mode and clear the cache there...and see if it helps you. (didn't work for me).
SiNJiN76 said:
I had Samsung Experience Home keep FCing on me. Had to do a reset. Sucked. 1 other thing you might want to try is to go into Recovery mode and clear the cache there...and see if it helps you. (didn't work for me).
Click to expand...
Click to collapse
Yeah, that's what I did in step 1. Didn't make any difference, camera still crashes...
I guess factory reset and setting up the device from scratch is my only option at this point.
Can anyone please post a working version of the stock Samsung Camera APK that works on Oreo (CRC2)?
Help appreciated... Thanks
maxie.maverick said:
I updated my T-Mobile Note-8 to Oreo (CRC2) via OTA update. Ever since my "camera keeps stopping" after taking a pic.. Anybody else here with similar experience?
Things I already tried:
1. Cleared system cache, did NOT work.
2. Cleared camera app cache/data, did NOT work.
3. Cleared gallery app cache/data, did NOT work.
4. Changed to internal/phone memory storage (in the camera settings), did NOT work.
5. Tried safe mode & camera still crashed, did NOT work.
Quick google search says many other people are facing this issue (different devices). I'm surprised there is NO posts here asking about this...
My only option at this point is to do a complete factory reset. But I hate doing that because of all the setup steps involved in making it behave correctly (as I like it).
Any help appreciated.
Click to expand...
Click to collapse
From JaguarXT inn another thread. Maybe this is why:
" Just be aware that there are problems with the current Oreo version for the Note 8. That is the reason why T-Mobile stopped sending out that version of Oreo Android to Note 8 devices right now. The last I heard of is that Samsung went to Google for help on the problems. So both Google and Samsung engineers are working on this.
You might want to wait until they send a version of Oreo Android for Note 8 that has the problems fixed."
I took the Oreo update the day it was pushed. I immediately factory reset and everything, including the camera, works perfectly. For the other Note 8 variants that recieved Oreo, and had problems; a factory reset fixed 99.9% of the issues.
rile1564 said:
I took the Oreo update the day it was pushed. I immediately factory reset and everything, including the camera, works perfectly. For the other Note 8 variants that recieved Oreo, and had problems; a factory reset fixed 99.9% of the issues.
Click to expand...
Click to collapse
Factory Data Reset is where my problems began. That end up Samsung telling this information and wanting to flash me back to Nugget until they fix this issue.
I was on OTA CRC2 Samsung stock Oreo.
rile1564 said:
I took the Oreo update the day it was pushed. I immediately factory reset and everything, including the camera, works perfectly. For the other Note 8 variants that recieved Oreo, and had problems; a factory reset fixed 99.9% of the issues.
Click to expand...
Click to collapse
Yeah, I had to factory reset as well... I used SmartSwitch to backup the phone on to my external SD card and then factory reset, wiped clean & installed CRC2 using Odin and then restored using Smart Switch app.
It sucked to do things all over again, but the phone seems reasonably behaved again!