Hi All, I come begging for help after exhausting all of my options and searches for similar issues.
I have a CDMA Galaxy Nexus Stock 4.0.2 but rooted (I installed CWM).
I woke up to my phone stuck in the boot loading screen; it just kept looping over and over. I shut off the phone restarted it and the phone was practically unuseable, it ran very very slow. Now I haven't done anything recently or installed any apps. The only app I installed was a modified MMS app (one of the Inverted Black ones), but that was 2 weeks ago and everything was running fine since then. (However since I'm not on a deodexed Rom, I knew there could be issues).
Well I of course switched back to the stock MMS app that I had manually backed up and that did not help. Now my phone would load, it would get to my homescreen, but it would then say something along, "service is not working, wait, close, or ok?" I'd hit wait and within 2 minutes my phone would automatically reboot and then go into a a sort-of bootloop (it would just show the boot.img and loop).
I then tried to restore two Nandroid back-ups (which were basically bone stock and made months ago) and both worked, except it would say secure.img not found or something like that. I was still able to boot up and use these back ups, but then within 5 minutes I would get the same error and then the phone would reboot.
After retrying them I decided to to just go bone stock and wipe and do a factory reset. This worked and everything seemed fine until I went to turn on wi-fi.
I would wait for wi-fi to turn on and eventually it would just quit and then reboot the phone. I did this 3 times in a row to confirm that it was indeed wi-fi causing these rebooting issues.
Now here's the thing, right now my phone is working as I have purposely tried not to touch the wi-fi (I need to use my phone) . Data, voice, mms/sms all work. But I literally have no idea why wi-fi would be causing my OS to go crazy?
My last resort is to flash the stock toro.img but I was hoping you guys could help me before I get to that point.
As of right now even though I did a data wipe/factory restore my phone is still rooted (rooted apps all work) and my bootloader is still unlocked. (I renamed the secure.bootloader file as per the instructions when using fastboot to load CWM).
Please help me troubleshoot this, Thanks guys.
I don't know if you have tried but maybe try flashing a rom after a data wipe
angelino0919 said:
I don't know if you have tried but maybe try flashing a rom after a data wipe
Click to expand...
Click to collapse
I'm thinking about doing this as well since I will probably have to flash back to stock. I just want to make sure I can get back to stock since I am still covered by warranty and insurance (assuming they do not check to see if my phone has an unlocked bootloader).
JayBeezy802 said:
I'm thinking about doing this as well since I will probably have to flash back to stock. I just want to make sure I can get back to stock since I am still covered by warranty and insurance (assuming they do not check to see if my phone has an unlocked bootloader).
Click to expand...
Click to collapse
Well you can always relock the bootloader. I doubt you will have to go back to stock though
Help! My phone is freezing / locking up and rebooting several times a day now!
I successfully did the stock AT&T Jellybean update this week when it became available via Kies.
I had no issues with the initial upgrade…it seemed to go smooth.
After a day…or a few hours….I can’t remember…I did start noticing a few issues with Touch Wiz closing or freezing and some other apps misbehaving. I can’t even remember what exactly the issues were.
I was also having some other quirky issues with the phone on stock ICS before the JB update…so I have been meaning to do a factory reset and reinstall everything.
So with the phone being even more flakey with JB I went ahead and did a factory reset with my new JB setup.
After a few hours setting up the phone with all my apps, settings, etc I noticed two issues. Swiftkey would not remain selected as my default keyboard and AT&T Voicemail viewer would not retain any of my account settings after a reboot.
After some Googling I learned that this is a know issue with JB 4.1.1 for many apps…they don’t quite install properly and something happens during shutdown that causes the settings to be lost. The only work around seemed to be:
Root Phone
Install apps
Backup with Titanium or other backup program
Uninstall apps
Restore apps – then they somehow install properly and work
I did this…first time rooting the phone….and the root and work around worked perfectly first time.
But after continuing to install apps and tweak my phone the real problems have now begun.
The phone is completely freezing at random times…in any app or in the TW launcher. It seems to just sit there frozen until I hold down the power key long enough to force a reboot or take out the battery.
There are no force closes or other error messages and I have found no other pattern to the freezes.
So now the phone is almost totally useless. It may work for a few hours…or just a few minutes before locking up. Worse…I have no way to know this has happened if the phone is in my pocket.
I did another full factory reset using the Recovery Mode and reinstalled everything again and am having the same issues.
I fear the root somehow corrupted my phone or one of my apps is totally incompatible with JB but I have to many (~70) it will be very hard to tell which one.
The other issue I am having is the battery is draining in just 4-5 hours even with light use.
Coincidentally….4G LTE was just turned on in my area this week so that would be a factor in both the battery drain and maybe even the lockups. I have a Microcell at home…wondering if 4G LTE and my Microcell are not behaving.
There are just too many variables with a new ROM (JB), fresh rooting of the phone plus recovery app installed, plus 70+ apps, plus new 4G LTE, plus my Microcell.
I don’t know what to try next to get the phone stable or to get the battery use reasonable.
Please post any and all suggestions….
One thing I’d like to clear up or eliminate is the root issue…is there any way that is the cause of my phone’s current problems?
What a mess of a week! Instead of the total awesomeness of JB, 4G LTE, and the fresh experience of using a rooted phone...all happening for me in the same week...I get a total headache and useless phone. Sure hope I can dig my way out of this.
Thanks for reading my long post!
I'd say to flash stock rooted official jellybean from here http://forum.xda-developers.com/showthread.php?t=1968625 i'd then do a Hard Factory reset *2767*3855# then you can install apps that are compatible with jb but not the app data and see how the phone is. also, for signal issues, try using a different modem located herehttp://forum.xda-developers.com/showthread.php?t=1831898
wujiku said:
I'd say to flash stock rooted official jellybean from here http://forum.xda-developers.com/showthread.php?t=1968625 i'd then do a Hard Factory reset *2767*3855# then you can install apps that are compatible with jb but not the app data and see how the phone is. also, for signal issues, try using a different modem located herehttp://forum.xda-developers.com/showthread.php?t=1831898
Click to expand...
Click to collapse
Thanks for the ideas....had not heard of the "Hard Factory reset *2767*3855#"....how is that different from a factory restet initiated from winthing Android or from the recovery program?
Also - is there any quick / easy way to know which of my apps are supposed to be compatible with JB?
Sure will be a pain to reconfigure everything again.
Should I be safe installing my apps via Titanium backup restores? (as long as I don't restore data)
Also - what about restoring my IMs and call logs from Kies? Is that safe?
Boomer6345 said:
Thanks for the ideas....had not heard of the "Hard Factory reset *2767*3855#"....how is that different from a factory restet initiated from winthing Android or from the recovery program?
Also - is there any quick / easy way to know which of my apps are supposed to be compatible with JB?
Sure will be a pain to reconfigure everything again.
Should I be safe installing my apps via Titanium backup restores? (as long as I don't restore data)
Also - what about restoring my IMs and call logs from Kies? Is that safe?
Click to expand...
Click to collapse
Do you happen to have juice defender? I had the same problem, and noticed it only happened when I was on battery. I uninstalled that and it stopped rebooting.
stbtigerr said:
Do you happen to have juice defender? I had the same problem, and noticed it only happened when I was on battery. I uninstalled that and it stopped rebooting.
Click to expand...
Click to collapse
Nope....juice defender...
And my phone doesn't really seem to be rebooting....just freezing up. I have to force it to reboot by holding down the power button for 10 seconds.
About to try a fresh factory ROM install (pre-rooted) and a hard factory reset.
Then I'll add my apps back very slowly to see....
What a pain in the you know what!
wujiku said:
I'd say to flash stock rooted official jellybean from here http://forum.xda-developers.com/showthread.php?t=1968625 i'd then do a Hard Factory reset *2767*3855# then you can install apps that are compatible with jb but not the app data and see how the phone is. also, for signal issues, try using a different modem located herehttp://forum.xda-developers.com/showthread.php?t=1831898
Click to expand...
Click to collapse
Well...I did all that...and no luck. Still freezing up.
I could not actually do the exact *2767*3855# reset...the phone would not respond to that command. So I used CWM to format the SDCard and also did a factory reset there.
Reinstalled my apps carefully and without data restore...boom....phone is locking up all the time again after maybe 12 hours of good operation.
Either this build of JB is not working on my phone or it somehow got fubar'ed during that first upgrade.
My plan now is to restore to factory ICS un-rooted....reset the flash counter if possible....and return the phone under warranty if possible.
Any recommendations for this?
Got replacement phone - still freezing up!
Boomer6345 said:
Well...I did all that...and no luck. Still freezing up.
I could not actually do the exact *2767*3855# reset...the phone would not respond to that command. So I used CWM to format the SDCard and also did a factory reset there.
Reinstalled my apps carefully and without data restore...boom....phone is locking up all the time again after maybe 12 hours of good operation.
Either this build of JB is not working on my phone or it somehow got fubar'ed during that first upgrade.
My plan now is to restore to factory ICS un-rooted....reset the flash counter if possible....and return the phone under warranty if possible.
Any recommendations for this?
Click to expand...
Click to collapse
HELP!!!! Please!!!!!
I did a warranty RMA and got a new (refurbed) phone from AT&T. I set it up with stock ICS and it seemed to work fine. I installed CWM without rooting via ODIN and did a Nandroid backup. I then used CWM to load TWRP recovery and did a backup with that.
Then I loaded the stock JB room with root. Tweaked the phone and app settings a little and things seemed to be fine for 1/2 a day. I reinstalled TWRP since the ROM flash replaced it with stock recovery. Things still seemed fine.
So...with JB rooted and seeming to work fine....I booted into Recovery (TWRP) and did a fresh Nandroid backup since the phone was finally all configured and working (apparently).
Well after rebooting from the backup...the phone is acting all crazy again. It seemed to crash my home WiFi network....had to reboot my router. Now the phone freezes or locks up any time I disable WiFi or change WiFi settings.
I am just cursed with the GS3!
Two separate phones with stock AT&T JB with root...one running CWM Touch and the new one running TWRP and both lock up or freeze all the time.
Should I give up and try custom ROMs? Give up on rooting?
I want TouchWiz for SBeam and some of the Samsung apps that I like better than stock...would rather just stay stock with Root.
What can I do to get this phone stabilized with root and JB???
Just did another test...
If I leave my house and walk a couple hundred yards away...as soon as the phone finally loses the WiFi signal and disconnects it locks up.
Seems like all my issues (with first phone maybe too) are tied to WiFi.
Is no one else having WiFi issues with JB? Could it be tied to rooting somehow? For instance...maybe the stock rooted ROM has different modem or WiFi drivers...or different kernel than the actual stock JB ROM I first used via Kies update?
Boomer6345 said:
Just did another test...
If I leave my house and walk a couple hundred yards away...as soon as the phone finally loses the WiFi signal and disconnects it locks up.
Seems like all my issues (with first phone maybe too) are tied to WiFi.
Is no one else having WiFi issues with JB? Could it be tied to rooting somehow? For instance...maybe the stock rooted ROM has different modem or WiFi drivers...or different kernel than the actual stock JB ROM I first used via Kies update?
Click to expand...
Click to collapse
I've got the KIES JB Update, & rooted. I am not experiencing any of the issues your having. It might be helpful if you could post a list of apps & widgets that you have installed, If you have frozen or removed stock files.
It sounds like you may be experiencing some app conflict issues.
MasterDecker said:
I've got the KIES JB Update, & rooted. I am not experiencing any of the issues your having. It might be helpful if you could post a list of apps & widgets that you have installed, If you have frozen or removed stock files.
It sounds like you may be experiencing some app conflict issues.
Click to expand...
Click to collapse
I have not frozen any apps or done anything I would consider advanced or risky....
I tried running with what I thought would be just "safe" apps....no luck. I've got most all of my apps installed and did a Titanium Backup so here is a dump of all the user apps backed up:
Code:
cgeo.geocaching-20121219-204517.tar.gz
com.amazon.kindle-20121219-204309.tar.gz
com.amazon.mp3-20121219-204326.tar.gz
com.amazon.mShop.android-20121219-204301.tar.gz
com.anddoes.launcher-20121219-205011.tar.gz
com.anddoes.launcher.pro-20121219-205016.tar.gz
com.android.chrome-20121219-204524.tar.gz
com.ap.advml-20121219-204732.tar.gz
com.apksoftware.compass-20121219-204539.tar.gz
com.ArtInGames.AirAttackHD-20121219-204225.tar.gz
com.asksven.betterbatterystats-20121219-204516.tar.gz
com.att.android.uverse-20121219-204944.tar.gz
com.att.mobile.android.vvm-20121219-204953.tar.gz
com.att.um.androidvmv-20121219-204448.tar.gz
com.aws.android-20121219-204954.tar.gz
com.careerbuilder.SugarDrone-20121219-204718.tar.gz
com.devuni.flashlight-20121219-204654.tar.gz
com.dominospizza-20121219-204542.tar.gz
com.duduapps.craigslistfree-20121219-204542.tar.gz
com.ea.tetrisfree_na-20121219-204932.tar.gz
com.ebay.mobile-20121219-204552.tar.gz
com.espn.score_center-20121219-204826.tar.gz
com.evernote-20121219-204602.tar.gz
com.facebook.katana-20121219-204621.tar.gz
com.gamestar.pianoperfect-20121219-204756.tar.gz
com.google.android.stardroid-20121219-204659.tar.gz
com.greatclips.android-20121219-204659.tar.gz
com.imangi.templerun-20121219-204915.tar.gz
com.imdb.mobile-20121219-204702.tar.gz
com.instagram.android-20121219-204708.tar.gz
com.jawbone.companion-20121219-204719.tar.gz
com.joeykrim.rootcheck-20121219-204826.tar.gz
com.july.cbssports.activity-20121219-204649.tar.gz
com.kb.Carrom3D-20121219-204804.tar.gz
com.keramidas.TitaniumBackupPro-20121219-205010.tar.gz
com.lastpass.lpandroid-20121219-204723.tar.gz
com.maxmpz.audioplayer-20121219-204808.tar.gz
com.maxmpz.audioplayer.unlock-20121219-204825.tar.gz
com.meijer.rx.android-20121219-204730.tar.gz
com.melodis.midomiMusicIdentifier.freemium-20121219-204849.tar.gz
com.metago.astro-20121219-204444.tar.gz
com.mxtech.videoplayer.ad-20121219-204733.tar.gz
com.netflix.mediaclient-20121219-204744.tar.gz
com.outfit7.talkingtom-20121219-204911.tar.gz
com.pandora.android-20121219-204752.tar.gz
com.photox.touchwhiz-20121219-204212.tar.gz
com.q2e.unitedfcu5017android.ufcu.uwnmobile-20121219-204953.tar.gz
com.rovio.angrybirds-20121219-204333.tar.gz
com.rovio.angrybirdsspace.ads-20121219-204352.tar.gz
com.rovio.angrybirdsstarwarshd.premium.iap-20121219-204414.tar.gz
com.rovio.BadPiggiesHD-20121219-204449.tar.gz
com.s0up.goomanager-20121219-205017.tar.gz
com.shazam.android-20121219-204827.tar.gz
com.shotzoom.golfshot-20121219-204655.tar.gz
com.skype.raider-20121219-204832.tar.gz
com.smugmug.android-20121219-204847.tar.gz
com.spotify.mobile.android.ui-20121219-204855.tar.gz
com.thewolverine.app-20121219-204944.tar.gz
com.touchtype.swiftkey-20121219-204859.tar.gz
com.trimble.allsportle-20121219-204258.tar.gz
com.vp.alarmClockPlusDock-20121219-204255.tar.gz
com.weather.Weather-20121219-204938.tar.gz
com.yelp.android-20121219-204959.tar.gz
com.yum.pizzahut-20121219-204759.tar.gz
de.heimlich.gut.solitaire.hd-20121219-204847.tar.gz
eu.chainfire.triangleaway-20121219-204224.tar.gz
jackpal.androidterm-20121219-204224.tar.gz
la.droid.qr-20121219-204813.tar.gz
net.androgames.level-20121219-204515.tar.gz
net.zedge.android-20121219-205008.tar.gz
nl.rogro.GScriptLite-20121219-204702.tar.gz
org.wikipedia-20121219-204958.tar.gz
Having the exact same problems as you. Please help. I'm also considering giving the phone back at Best Buy and having them give me a new one with ICS and leaving ICS on there. My steps are very simple. I had the stock ICS ROM from AT&T and I used Kies to upgrade to stock JB. That's it, nothing else, no rooting, nothing.
I am seeing exactly the same behavior, when wifi switches to 4G or even sometimes when bluetooth comes on, etc I will see the lockup and hang. Have to hold down power button to restart. But I don't think this is completely the issue, because even if I turn off wifi, bluetooth and only leave on 4G, then I still will see random reboots, but a lot lot less frequent. Also, I have always had 4G and I see the battery only lasting 4-6 hrs, so I think this is normal with 4G. I saw this even with ICS.
I have not done any factory reset or anything - I would assume if you use the Kies s/w to update and it leaves your files and apps on there, then it should just work. But I will try the factory reset once I backup my contacts, etc.
I'm a little shocked that people are having this problem with a newly released ROM.
abhansali said:
Having the exact same problems as you. Please help. I'm also considering giving the phone back at Best Buy and having them give me a new one with ICS and leaving ICS on there. My steps are very simple. I had the stock ICS ROM from AT&T and I used Kies to upgrade to stock JB. That's it, nothing else, no rooting, nothing.
I am seeing exactly the same behavior, when wifi switches to 4G or even sometimes when bluetooth comes on, etc I will see the lockup and hang. Have to hold down power button to restart. But I don't think this is completely the issue, because even if I turn off wifi, bluetooth and only leave on 4G, then I still will see random reboots, but a lot lot less frequent. Also, I have always had 4G and I see the battery only lasting 4-6 hrs, so I think this is normal with 4G. I saw this even with ICS.
I have not done any factory reset or anything - I would assume if you use the Kies s/w to update and it leaves your files and apps on there, then it should just work. But I will try the factory reset once I backup my contacts, etc.
I'm a little shocked that people are having this problem with a newly released ROM.
Click to expand...
Click to collapse
After several re-flashes to stock JB with root and still more freezing with WiFi, etc....I gave up and loaded a custom ROM this morning.
I'm running BlackJelly...and after about 8 hours it seems be be running great so far. It is TW JB-based...and having very few issues with it. Battery is poor but it takes a few days of charging and use I guess to get the battery / phone / ROM calibrated. AT&T Visual Voicemail is not working and the phone shows H instead of 4G LTE...but I'm sure I can fix those issues by searching through the hundreds of thread pages on that ROM is this forum.
Give it a try before you switch to ICS or trade in the phone. You can always flash back to stock un-rooted and use Triangle Away to reset flash counter.
Good luck!
Still stuck with crashing phone!
Boomer6345 said:
After several re-flashes to stock JB with root and still more freezing with WiFi, etc....I gave up and loaded a custom ROM this morning.
I'm running BlackJelly...and after about 8 hours it seems be be running great so far. It is TW JB-based...and having very few issues with it. Battery is poor but it takes a few days of charging and use I guess to get the battery / phone / ROM calibrated. AT&T Visual Voicemail is not working and the phone shows H instead of 4G LTE...but I'm sure I can fix those issues by searching through the hundreds of thread pages on that ROM is this forum.
Give it a try before you switch to ICS or trade in the phone. You can always flash back to stock un-rooted and use Triangle Away to reset flash counter.
Good luck!
Click to expand...
Click to collapse
Well...after over a week of trying it out....BlackJelly did not help me. Still had freezes / lock-ups.
I can't tell if the phone is re-booting itself or just re-launching the Launcher (I us Nova but tried stock and Apex too). The phone appears to re-boot on it's own but the up-time under status would not reset...making it seem like not a re-boot but a launcher reload or something. Pretty much same issues as with stock JB.
So I gave up and tried CM10.1 nightlies....and wow....crashing all the time now. Whereas stock JB and BlackJelly seemed to crash when I left my home or left any WiFi network or even just when I disabled WiFi while connected....CM10.1 crashes all the time while at home seemingly at random. I can get 5 hours of great use...then have it crash 5 times in an hour. Seems to crash a lot in the settings menus.
This is with my second (replacement) phone. I am just cursed!
How do I effectively use a LogCat app or something to find out what apps or services or whatever are crashing my phone? Help!
Read through this whole thread and no where did you ever mention clearing your cache. Clear your system cache/davlik cache and reboot.
cjranucci said:
Read through this whole thread and no where did you ever mention clearing your cache. Clear your system cache/davlik cache and reboot.
Click to expand...
Click to collapse
Sorry...should have mentioned that. I've cleared the system and davlik cache many times...before and after flashing. I've done full system wipes / resets, formatted my SD card...everything I can think of.
I either have a rouge app that I seem to install right away after clean flashes....or a rouge Wifi router in my house that messes up my phone even when I leave and use other networks...or a rouge ATT&T microcell that does the same....or a rogue LTE area in West Michigan....
Or a second bad phone sent from AT&T. But no form of JB seems to work for me no matter what. Guess I could run a clean install with no apps for several days...and then add in an app a day for the next 2+ months until I find the bad app...if that is even the case.
So bummed with this mess!
My phone freeze after rotation on landscape only with JB. all kind roms of JB stock, cyanogen,, aokp.
makamobile said:
My phone freeze after rotation on landscape only with JB. all kind roms of JB stock, cyanogen,, aokp.
Click to expand...
Click to collapse
Interesting....that might be what I was experiencing....but I never thought that was it....did not notice that cause/effect.
I gave up and went back to stock / rooted ICS / TW...version LH9. Loaded it yesterday and have had 24 hours of great use...no issues.
I miss JB and Google Now...but at least my phone works!
I'm not sure for stock JB but on other ROMs, you could try changing your governor and scheduler.
BWolf56 said:
I'm not sure for stock JB but on other ROMs, you could try changing your governor and scheduler.
Click to expand...
Click to collapse
When on CM10.1 I tried bumping the minimum CPU speed to 484 and 5xx (can't remember the actual numbers)....and the maximum CPU speed to to 14xx and 13xx (again, can't remember)....and this did not help.
Not sure if that is what you meant tho.
Anyway...I gave up and went back to rooted stock ICS (LH9) and the phone is working great. I've given up on JB for now. I will wait for a new major JB release from Samsung before I try again.
copy paste from gs3 verizon forum
Q: The phone keeps freezing when I go into landscape mode.
A: This has been covered many times in the thread, but to reiterate: If you are using the AOSP lockscreen you must disable "Ripple Effect" in Settings -> Lock Screen -> Lock Screen Options
Had something really weird happen to my S3 guys.
Running teamwin and the Liquid-Smooth ROM. Been that way for 5 months since I bought it with no problems until now.
Plugged the phone up to the charger last night before bed. Woke up and wondered why the charging light was still yellow so I kicked the screen on and it was charging at an extremely slow rate (Around 40mA). Unplugged the charger and the phone made a tone I had never heard before. Noticed two small "glitches" or "artifacts" in the display rendering around the clock area on the home screen. Attempted browsing around the phone. App drawer opened and closed fine but EVERY process or app I would try to launch would crash so I rebooted, and that brings me to where I am now.
The ROM will NOT boot. The phone just sits there at the Galaxy SIII splashscreen. I can boot to Odin/recovery just fine and the internal SD filesystem appears intact and browse-able. Tried totally nuking the data section. Wiped Dalvik/Cache, did factory reset and then wiped the ROM. Tried re-installing the ROM and even re-flashing the radio and it still doesn't boot past the splashscreen.
While I was in recovery it also told me, "Your phone doesn't appear to be rooted. Would you like to install SU?", which is strange because the phone WAS rooted.
Thinking this thing mysteriously turned itself into a paperweight. Any ideas?
Please install a different Non-Liquid Rom. But for best results, First ODIN back to stock and then go from there. Use Root 66 Stock image.
agree with odin flashing root66 firmware. factory reset FIRST though. you will likely be forced to if you dont, and once stock recovery is flashed back on it will wipe internal sd.
if you still have issues after that i would suspect a hardware failure.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2
Just FYI guys I got it back about an hour after posting this.
Even after wiping both caches, performing a factory reset, fixing permissions and finally nuking the ROM it still would not boot. I then put in a spare SD, used recovery to copy everything from internal to external to save all my valuable data and only after wiping the internal SD was I able to get the phone to boot again after re-installing the ROM.
I then transferred all valuable files back to internal SD, restored from a recovery backup and then was good to go. A bit strange but I got it working again.
Eventually I might upgrade from LiquidSmooth but I like it and have no reason to change for now.
I went through from 4.1.1 to 4.1.2, no problems, phone ran fine after update. Then went to 4.3, same thing. The phone was running fine so I booted back into recovery and removed Knox as well as manually rerooted by flashing SuperSU. Rebooted after that and still no problems, phone was running great. I then make a backup so I have a restore point of stock 4.3, rooted, and without Knox. I then go on and try to flash Dandroid and get a status 7 error and the phone was acting up after I rebooted.
At this point I go back to my backup and simply restore it and reboot again. The phone boots up, so that's a good thing. The problem is the GApps will not run and it continuously has a pop-up notification. The phone is rendered unusable like this. I got lucky once and was able to try and launch ROM Manager to see if fixing permissions would work, but it also closed. I tried flashing a 4.3 GApps package with no success and even tried reflashing the 4.3 update but got a status 6 error.
I'm at a loss here, does anyone have any ideas on this?
Not sure if this will help much, but even when plugged in via USB my computer will not recognize the device. The S3 states that it is connected and it does show up in Device Manager, it just won't show up as any kind of readable memory.
Trying to ADB sideload a rooted stock 4.3 ROM now. Any advice at all would be a help.
EDIT: I took a video (https://www.youtube.com/watch?v=tJ-eaQ_9mVI) of the problem so everyone can see what I'm talking about and I also found a fix.
I'm not sure what was causing it, but after a solid day of researching it online the closest thing I got was resetting app preferences and also trying to clear any data of Google apps. This seemed to sometimes slow the popups down for me or create a longer gap before they just came right back in full force. So, going off that small success I had managed to navigate my way over to Settings -> Accounts -> Backup and reset -> Factory data reset and ran that. The first boot after that took a very long time, I'd say a solid twenty minutes but it did work. No more error and everything has been going smooth for me since. A restore of apps with Titanium Backup also did not bring the problem back up again, so the device seems to be good as new again.
I apologize if any of these is out of line, I just thought I would follow up with a solution in case anyone else has this problem and can't seem to fix it. Maybe this will help them.
Hi All,
Having some issues with my Galaxy Note 10.1 which I've had for quite a while now. It's rooted but with Android 5.0 stock rom and a custom kernel.
Just now (like 20mins ago) I tried to enable Adblock plus app, the app said it can't automatically change the settings - even though SuperSU was installed and had no issues with it previously. So like all things thought I'd give it a reboot that ought to clear it out. That didn't work, so tried clearing cache (Dalvik/ART/Cache), Still no joy.
I'm a s/w engineer, but not and android/bootloader expert, so I've tried to grab the dmesg and boot logs which I've attached, I've got some stuff on the internal SD (app data) which I'd like to keep, hence I'm not going for the full wipe.
Please take a look at the logs and see if you can determine how to fix this issue, my initial thoughts were there are some issues with the flash storage (bad sectors/partition table?), if I could grab the image and dd the image again I'd be OK - but I don't know much about about android boot loader/kernel etc so can't say.
Ok it has been fixed by wiping data - but I've lost my data and installed apps!
Is there anyway to find out which file/app is causing the boot loop so I can restore data, delete the offending file?
Well, I shall give a bump to this topic, with a little more info. Though probably not really useful.
First I had stock 5.1.1 deodex pre root etc ROM that, after I tried to insert a nano sim card (mine is a 601 3G model) that got stuck, it entered on a bootloop, I had to open it, take the sim card out, and it was still on a boot loop. Tried to install another image, still bootloop, tried to reinstall the original one I had, still bootloop, wiped data, worked fine.
Then almost 2 weeks later, everything worked fine, went to watch a video, the sound was mute, tried to turn it on but everything looked fine, decided to restart because it would probably fix the problem. Got a bootloop. Wiped the data, everything was fine again.
Now, a little more than 2 weeks later, seems like the wifi is not working, thought all my other devices are, guess it's the same problem, decided to restart it, and bootloop again. I'm currently trying to update my TWRP, and gonna try a different ROM, and wait to see if something like that happens, until then, I wonder what could be happening... I remembered an Asus Device that I had that had different firmware versions for 4.4 and 4.1, so if I tried to flash a 4.4 on a 4.1 firmware it wouldn't work, and for downgrade, the same problem happened, and wondered if Samsung has some difference between versions 4 and 5.
ssj4maiko Let me know if you find a more stable rom - I went back to pretty much stock, but with root as I wanted to use all the Samsung apps, but this constant random bootloops are annoying!