I just recently rooted my phone using the newest root method for the 98.30.1 build. The phone was rooted successfully, but for some reason now, the Google Play Services crashes occassionally with a message on the phone that it stopped responding. I was wondering if anyone else if experiencing any issues with Google Play Services. Although this started to happen shortly after I rooted my phone, I don't believe the issue is related and is most likely being caused by something else. Anyone have any insight or solution to this?
Also, I was wanting to restore my phone to factory default, but was wondering if after I restore the phone, will I need to rerun the root tool to re-root the phone and/or reinstall the SuperSU app? I was thinking that the su binary and busybox are stored on the /system partition, so they shouldn't be affected, but would I then just need to install the SuperSU app from the Play Store? I am wondering if I would need to re-run the root tool or just install SuperSU from the app store for the phone to be rooted properly after a factory restore. Thank you in advance
Have you tried a safe boot?
PM notification is not on by default, btw.
aviwdoowks said:
Have you tried a safe boot?
PM notification is not on by default, btw.
Click to expand...
Click to collapse
Thank you for the quick response. I haven't tried safe boot yet, but I will definitely try it. Right now, I wiped the cache partition via stock recovery and am seeing if Google Play Services crashes again.
If I do decide to do a factory reset. What are the steps I need to do to ensure I keep root or can root again? I wasn't sure if I just do a factory reset and rerun the root tool, or do I just factory reset and install SuperSU through Play Store, or do I need to user OTARootkeeper to temporarily unroot and then factory reset and restore root? Just cautious to not mess up my phone. Thanks for all your help!
ScallywagginIT said:
do I just factory reset and install SuperSU through Play Store, or
Click to expand...
Click to collapse
Or use SS Bootstrap as it gives you more options like BU before you wipe.
Related
i one click rooted my device and installed CWM . later on i unrooted my device and tried to remove CWM i factory reseted and then i started getting an "unfortunately, google play services have stopped. i tried disabling and enabling in apps settings same with google play and gmail and no dice. factory reset doesnt work either NEED HELP ASAP
Arregee173 said:
i one click rooted my device and installed CWM . later on i unrooted my device and tried to remove CWM i factory reseted and then i started getting an "unfortunately, google play services have stopped. i tried disabling and enabling in apps settings same with google play and gmail and no dice. factory reset doesnt work either NEED HELP ASAP
Click to expand...
Click to collapse
I'm new to this phone but I've had an lg in the past.. couldn't you just flash the stock firmware and start from scratch?
deadenz said:
I'm new to this phone but I've had an lg in the past.. couldn't you just flash the stock firmware and start from scratch?
Click to expand...
Click to collapse
do flash it like a regular rom through CWM. im new to CWM because i tried replacing with TWRP and where can i find the stock firmware
Arregee173 said:
i one click rooted my device and installed CWM . later on i unrooted my device and tried to remove CWM i factory reseted and then i started getting an "unfortunately, google play services have stopped. i tried disabling and enabling in apps settings same with google play and gmail and no dice. factory reset doesnt work either NEED HELP ASAP
Click to expand...
Click to collapse
You can't do an actual stock factory reset without the stock recovery installed, because the stock recovery is what does the reset process and restores your device to factory defaults, so the easiest thing to do is just flash the stock ROM then do a factory reset.
The AT&T ROM is flashed as a tot file with one LG flashing tool, where the other stock ROMs are kdz and are flashed with a different tool. Personally, I find the second method via kdz to be much simpler, and I'm not on AT&T, so I prefer to not use their ROM anyway, since it's a bit more bloated and has Carrier IQ installed.
Take a look here, and you'll get it, if you follow the steps.
http://forum.xda-developers.com/showthread.php?goto=newpost&t=2420219
http://forum.xda-developers.com/showthread.php?t=2302660
O.K. People, I kinda dropped off the map for a while and hadn't kept up with all the latest info but it appears I need some help. I'll try and drop the cliff notes version with as much data as I can here and see if anyone has some input for me:
I took the 4.3. O.T.A. and knox did just that..knocked me into the dirt. I was able to root and install custom recovery using CFAuto root and afterwards, disabled knox and reconfigured the stock ROM the way I wanted to. I reinstalled CWM and proceeded to create a backup of my 4.3 stock rooted rom. After the backup completed I proceeded to restore my backed up ROM as a sanity check to make sure all was well and it certainly wasn't.
When CWM restored my backup I rebooted, got back into the ROM w/out problems but as soon as I swiped to access the home screen I get the com process GAPPS has stopped responding....I get this over and over and over....I have to wipe caches and reset to factory default from CWM in order to get into the ROM w/out this message. Does anyone have any insight into what I might be doing wrong, i've never experienced this before and have had plenty of experience doing these backups and restores. I'm at a loss and I don't want to have to factory reset every time I want to restore the rom as I like to make changes, and customize the stock rooted rom. Please help. If you want version specifics and such let me know and I'll post them as they're needed, and thanks in advance!
P.S. Sig file needs to be updated....that's the version info from which I updated to 4.3
~Fred
gapps stops after cwm restore
Phederico said:
O.K. People, I kinda dropped off the map for a while and hadn't kept up with all the latest info but it appears I need some help. I'll try and drop the cliff notes version with as much data as I can here and see if anyone has some input for me:
I took the 4.3. O.T.A. and knox did just that..knocked me into the dirt. I was able to root and install custom recovery using CFAuto root and afterwards, disabled knox and reconfigured the stock ROM the way I wanted to. I reinstalled CWM and proceeded to create a backup of my 4.3 stock rooted rom. After the backup completed I proceeded to restore my backed up ROM as a sanity check to make sure all was well and it certainly wasn't.
When CWM restored my backup I rebooted, got back into the ROM w/out problems but as soon as I swiped to access the home screen I get the com process GAPPS has stopped responding....I get this over and over and over....I have to wipe caches and reset to factory default from CWM in order to get into the ROM w/out this message. Does anyone have any insight into what I might be doing wrong, i've never experienced this before and have had plenty of experience doing these backups and restores. I'm at a loss and I don't want to have to factory reset every time I want to restore the rom as I like to make changes, and customize the stock rooted rom. Please help. If you want version specifics and such let me know and I'll post them as they're needed, and thanks in advance!
P.S. Sig file needs to be updated....that's the version info from which I updated to 4.3
~Fred
Click to expand...
Click to collapse
I have the same issue. Did you find an answer?
psawood said:
I have the same issue. Did you find an answer?
Click to expand...
Click to collapse
NOPE...no one's said a word and I've just been rolling back to my last stock rooted ROM and then taking the O.T.A. then re-rooting whenever I do something stupid. LOL If you have an answer for me..or anyone does for that matter, I'd sure like to hear it!
P.S. sorry, gave up on this thread, so hadn't kept up on it...just now saw your post.
~Fred
I ran into this issue.
What I did is :
DL Rom Manager
Open Rom Manager
Fix Permissions
Boot into Recovery
Wipe Cache
Wipe Dalvik
Reboot
Haven't had the issue since.
@Chainfire
while trying to sideload ota 443 i encountered the following error
/system/bin/debuggerd has unexpected contents
Click to expand...
Click to collapse
I managed to fix it by flashing the factory system image from 4.4.2. A google search pointed me to http://forum.xda-developers.com/showpost.php?p=47416542&postcount=43 so a factory reset was not needed
It seems that this is a problem known to using stickmount. Is there anything you can do. I'd really like to avoid this in the future or i might have to swap to a different tool for mounting USB.
I lost root in the process with flashing the OTA but this was quickly fixed by using cf-autoroot and removing the oem unlock line then reinstalling the apk.
Ch3vr0n said:
@Chainfire
while trying to sideload ota 443 i encountered the following error
I managed to fix it by flashing the factory system image from 4.4.2. A google search pointed me to http://forum.xda-developers.com/showpost.php?p=47416542&postcount=43 so a factory reset was not needed
It seems that this is a problem known to using stickmount. Is there anything you can do. I'd really like to avoid this in the future or i might have to swap to a different tool for mounting USB.
I lost root in the process with flashing the OTA but this was quickly fixed by using cf-autoroot and removing the oem unlock line then reinstalling the apk.
Click to expand...
Click to collapse
If you install the latest StickMount from a clean setup and are using SuperSU (this is important), it shouldn't happen again.
define clean install? Factory image? Cant do that too much data on it.
In short what i did was
- restore factory 442 system image
- sideload ota
- boot su autoroot (but with the oem unlock line removed as it already is unlocked)
- reinstall SuperSU from playstore
Havent reinstalled stickmount or any similar app yet. With that being said, if i reinstall stickmount will i be safe from this happening again, or do i need to do factory reset?
Ch3vr0n said:
define clean install? Factory image? Cant do that too much data on it.
In short what i did was
- restore factory 442 system image
- sideload ota
- boot su autoroot (but with the oem unlock line removed as it already is unlocked)
- reinstall SuperSU from playstore
Havent reinstalled stickmount or any similar app yet. With that being said, if i reinstall stickmount will i be safe from this happening again, or do i need to do factory reset?
Click to expand...
Click to collapse
You stated you flashed the stock 4.4.2 image to fix the OTA problem. That means a clean install. Make sure you are using SuperSU and install the latest StickMount version from Play, it shouldn't happen again.
thx for the quick replies. I'll go ahead then and reinstall stickmount then. Dno why it happened in the first place. except root i'm full stock.
I am on rooted 51.1.1.0_user_511070220 (last rootable version), with the dcp amazon update disabled.
I would like to do a clean move to the unlocked bootloader, clockworkmod, latest rbox custom rom, and then finally playstore.
I have the following questions, and would like to get it clarified before I start the procedure.
1. In order to unlock the bootloader and then install clockworkmod I follow this:
http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/
2. I want to do a clean install. So, which things I have to wipe in clockworkmod?
3. After wipe, I install the rom using:
http://www.aftvnews.com/how-to-install-a-custom-rom-image-on-the-amazon-fire-tv/
My question is - in step 2, if I wipe everything, how do I get the rom image on to the fire tv. Or, do you recommend that a wipe is NOT necessary?
Also, in this case, do I have to do the disable dcp amazon update again?
4. Also, where can I find the latest playstore apks? I am thinking of going with this:
http://forum.xda-developers.com/fire-tv/help/help-install-google-playstore-t2933189
Thanks.
OK since no one replied I did NOT wipe.
Downgraded, unlocked boot loader, installed cwm, installed custom ROM. Works great. Thank you rbox.
My SuperSU now cannot be started. I can't uninstall/reinstall it either via apk. I read that few others have this problem as well.
Once I get that fixed, next is play store.
Thanks.
deepasadish said:
OK since no one replied I did NOT wipe.
Downgraded, unlocked boot loader, installed cwm, installed custom ROM. Works great. Thank you rbox.
My SuperSU now cannot be started. I can't uninstall/reinstall it either via apk. I read that few others have this problem as well.
Once I get that fixed, next is play store.
Thanks.
Click to expand...
Click to collapse
No one replied most likely because all your questions have been answered in the various threads about them.
And yes, currently the SuperUser can't be opened, but seems to work just fine. Do you need to go into it's settings? It shouldn't be holding you back from installing or doing anything.
nyder said:
No one replied most likely because all your questions have been answered in the various threads about them.
And yes, currently the SuperUser can't be opened, but seems to work just fine. Do you need to go into it's settings? It shouldn't be holding you back from installing or doing anything.
Click to expand...
Click to collapse
Sorry I have read almost every post and can't find info about the wipe. Anyways I will do that later as it is not important right now.
Regarding SuperSU, yes I can't open it. I only have the force stop, clear cache, clear data options for it. Obviously I can't uninstall and reinstall it either. I downloaded the SuperSU zip, but decided against flashing it in cwm.
Having said that, I do think I have root. When I type su in adb I do get root and see the message root granted on the screen. However it is not asking me whether to give su permission or not.
edit - i did clear data for supersu and then if I type su in adb, then i get the popup. so, i guess it was just remembering previous settings and granted automatically. i still can't open supersu though. thanks.
Here's the thread: http://forum.xda-developers.com/fire-tv/help/supersu-t2926119.
You can download a different version of su. (Direct download link is in the thread.) This is not the chainfire version. This version will open, allow you to set defaults, etc. Be aware that the screen is very low contrast and hard to read. You need to look carefully.
BTW, both versions seem to coexist peacefully.
Hello all,
I recently bought a LG G3 used as a Christmas present to myself. I've just set it up and noticed that SU installed fine from my playstore account, and after verifying I see that it's already rooted. Is there some way to tell if it's also been set up with a custom recovery as well? I have pending system updates and would like to go ahead and install, but not if it's going to soft brick the phone.
Or is there no way to safely install system updates with just root, and I need to completely wipe to stock anyway?
robbierob03 said:
Hello all,
I recently bought a LG G3 used as a Christmas present to myself. I've just set it up and noticed that SU installed fine from my playstore account, and after verifying I see that it's already rooted. Is there some way to tell if it's also been set up with a custom recovery as well? I have pending system updates and would like to go ahead and install, but not if it's going to soft brick the phone.
Or is there no way to safely install system updates with just root, and I need to completely wipe to stock anyway?
Click to expand...
Click to collapse
Download an app from Play store that let's you reboot in recovery mode like Quick Boot (Reboot) and check for yourself.
As for the updates you must be completely stock and unrooted if you want to install OTA Official system updates.
robbierob03 said:
Hello all,
I recently bought a LG G3 used as a Christmas present to myself. I've just set it up and noticed that SU installed fine from my playstore account, and after verifying I see that it's already rooted. Is there some way to tell if it's also been set up with a custom recovery as well? I have pending system updates and would like to go ahead and install, but not if it's going to soft brick the phone.
Or is there no way to safely install system updates with just root, and I need to completely wipe to stock anyway?
Click to expand...
Click to collapse
Download 4 way reboot app from the playstore and then use it to reboot into recovery. If it goes into TWRP you've got twrp
You might also install "root checker". Then you'll know for sure if its rooted or not.
Anadim said:
Download an app from Play store that let's you reboot in recovery mode like Quick Boot (Reboot) and check for yourself.
As for the updates you must be completely stock and unrooted if you want to install OTA Official system updates.
Click to expand...
Click to collapse
Thanks everyone for the quick knowledge. Downloaded root checker which confirmed I'm rooted, and downloaded 4 way boot which shows I have stock recovery.
Since I need to be completely stock to install OTA's, what's the recommended way to go back to stock? I would prefer not to have to do a complete wipe, but it’s not the end of the world if it’s needed.
robbierob03 said:
Thanks everyone for the quick knowledge. Downloaded root checker which confirmed I'm rooted, and downloaded 4 way boot which shows I have stock recovery.
Since I need to be completely stock to install OTA's, what's the recommended way to go back to stock? I would prefer not to have to do a complete wipe, but it’s not the end of the world if it’s needed.
Click to expand...
Click to collapse
Download your desired firmware and flash with LG Flash Tools 2014.
Follow the guide in this post : http://forum.xda-developers.com/showthread.php?t=2785089
It has options for normal flash without losing data and a CSE Flash for a fresh format. Although I strongly recommend doing the full wipe CSE Flash Option and a factory reset from stock recovery after flash so you won't have any problems - best experience. Good Luck.