Tried to root, now system UI has stopped - G4 Q&A, Help & Troubleshooting

I have a T-mobile LG G4 and I'm in the US. I did my research, watched videos, and read several threads about rooting... I thought I had it down. I followed the instructions in This thread exactly, to the best of my knowledge. Unfortunately, after my phone rebooted following step 10 (running the root script), it keeps saying "Unfortunately, System UI has stopped working" over and over.
I'm downloading the kdz files to return my phone to stock (hopefully--since I screwed up somehow, following the root instructions). But has anyone had this happen? Know what's causing it? Or how I can fix it besides a factory reset?
UPDATE: Ok, so I got freaked out reading about how returning to an earlier version of stock could brick your phone, so I decided to bite the bullet and do a hard factory reset. When I did, it asked if I wanted to restore from an earlier backup. I thought, "hey, no way it backed up after I just tried to root it, this backup ought to be safe!" and gave it a whirl. Well, when it finished restoring, root checker says I've successfully rooted! What the hell?! So, um... yay?

I have this exact same problem.
I have a tmobile variant and I had root previous(don't remember method I used). I installed the marshmallow rom, and thought it was too sluggish so I restored my device. But then my phone was wack...so I had to do a complete restore using flash tool. After that my phone worked fine, but I had no root. I attempted to use this new program with adb cmd. It worked but now my phone is sluggish the ui crashes, the camera doesn't work, and back buttons. I restored again... then rooted again.... same thing....so I restored AGAIN. I hope anyone can help.

Buuuuump
Bump Bump Bump... sadly this is the only known root I know of soooo #NoRoot4Meh :/

happen to me too..
just go to setting (use the notification shortcut), search for Home in apps (all apps) and then clear data and cache.
helped me to solved this problem, you will need to re-align your icons and apps on the launcher.

Related

[Q] ZVB Update Fails Every Time

I received the OTA ZVB update today, and I tried to install it using the standard OTA procedure. The device started applying the update, but it failed at about a quarter of the way through (the icon turned to a tipped over Android with a red triangle) at which point the phone rebooted and no changes were made.
I am rooted, and I have done the shutter fix (I deleted the camera_click.ogg and turned the forced shutter off in the build.prop). Besides that I haven't changed any system files. I tried replacing both files with original copies, and the update still fails. Is there anything I'm missing when it comes to updating to Jelly Bean? I was pretty sure you can update on top of root (although root will be lost) or am I mistaken and need to unroot to apply the update? Like I said, the only modifications I have done are 1. Rooting 2. build.prop edit 3. Deleted camera_click.ogg. I have reverted the build.prop and the camera_click.ogg.
Is anybody else having this problem? I searched and didn't find anything similar.
Any help would be appreciated, and if possible I would prefer not to factory reset because I have apps and things I would like to keep (I could probably back them up with Titanium though); but if that is the only option I would consider.
[You never said if you were unlocked or not, but this might be an option for you. http://forum.xda-developers.com/showpost.php?p=38558967&postcount=1
Theres a link from there to a stock zvb zip if you can use it. I'm not too sure you're gonna be able to save your stuff.
edit. If I were you, I'd unlock, run the stock zvb zip, and call it good. It's probably your best option
Ive had the same issue, tried everything including unroot. ended up reseting phone and reverting back to zv7 using lgnpst and updating software that way and it worked fine.
This is what I decided to do
stealthily said:
Ive had the same issue, tried everything including unroot. ended up reseting phone and reverting back to zv7 using lgnpst and updating software that way and it worked fine.
Click to expand...
Click to collapse
This is exactly what I'm doing right now. So far so good, I just finished installing the ZV9 update so one more to go. I'm crossing my fingers that this will work. Also, interestingly enough I didn't lose any of my files which was a huge plus!

[Q] Really need your expert help guys! SM-T800

Alright, I'll lay out what happened. My end goal is to just have a rooted tab, but at this point, I'd be willing to just have it back to how it was. Preferably without losing everything on it.
-Looked around on how to root it, and found the following, and use the files it suggested.
- Seemed easy enough, and I had rooted/installed android on my old HP Touchpad, so I dl'd the files, and gave it a shot.
- Couldn't get CWM recovery on it, so I ran verify root and it said it wasn't rooted, even though I has SuperSU. It would even ask to grant apps permission, and I'd grant it.
- I opened SuperSU, and it'd say it needed to update the binaries, but would fail on normal, so I dl'd the newest zip, booted into recovery, and tried to load it like that, but 2 lines would come up red. I think they were just verifying signatures, so I ignored it and let it reboot.
- I opened SuperSU again, and it still said it needed the binaries updated, failed on normal attempt. I decided to try again from scratch, unrooting it and all. So, I went into the SuperSU settings and did it's thing, but it still had the version of SuperSU that initially was on it (it wouldn't let me past the "update binaries" prompt).
- I found that I needed to use Odin to flash a stock firmware back on it, and dl'd both version here.
- I tried the first one, and then it wouldn't get past the "Samsung" screen (the 2nd one with just the word Samsung, if it matters).
- I can still boot into Odin and Recovery, thankfully, so I tried the 2nd stock firmware. Same issue.
- Finally, I tried the rooting process again, hoping to get it to boot, same thing. So, I tried the 2nd stock firmware again, praying something good would happen, and still stuck on the Samsung screen.
I can still boot into Odin and recovery, but I have no idea where to go from here. I still want it rooted if possible, and I'd prefer not to lose all my games and such. I just found "[ROOT][RECOVERY] [ALL IN ONE] Cf-Autoroot-twrp-T800-T805-T-700-T705" thread here, but I didn't want to try it just yet.
It's a SM-T800. I had Lollipop on it. Don't know much else to add, but please help!
Thanks all.
Cypher5235 said:
Alright, I'll lay out what happened. My end goal is to just have a rooted tab, but at this point, I'd be willing to just have it back to how it was. Preferably without losing everything on it.
-Looked around on how to root it, and found the following, and use the files it suggested.
- Seemed easy enough, and I had rooted/installed android on my old HP Touchpad, so I dl'd the files, and gave it a shot.
- Couldn't get CWM recovery on it, so I ran verify root and it said it wasn't rooted, even though I has SuperSU. It would even ask to grant apps permission, and I'd grant it.
- I opened SuperSU, and it'd say it needed to update the binaries, but would fail on normal, so I dl'd the newest zip, booted into recovery, and tried to load it like that, but 2 lines would come up red. I think they were just verifying signatures, so I ignored it and let it reboot.
- I opened SuperSU again, and it still said it needed the binaries updated, failed on normal attempt. I decided to try again from scratch, unrooting it and all. So, I went into the SuperSU settings and did it's thing, but it still had the version of SuperSU that initially was on it (it wouldn't let me past the "update binaries" prompt).
- I found that I needed to use Odin to flash a stock firmware back on it, and dl'd both version here.
- I tried the first one, and then it wouldn't get past the "Samsung" screen (the 2nd one with just the word Samsung, if it matters).
- I can still boot into Odin and Recovery, thankfully, so I tried the 2nd stock firmware. Same issue.
- Finally, I tried the rooting process again, hoping to get it to boot, same thing. So, I tried the 2nd stock firmware again, praying something good would happen, and still stuck on the Samsung screen.
I can still boot into Odin and recovery, but I have no idea where to go from here. I still want it rooted if possible, and I'd prefer not to lose all my games and such. I just found "[ROOT][RECOVERY] [ALL IN ONE] Cf-Autoroot-twrp-T800-T805-T-700-T705" thread here, but I didn't want to try it just yet.
It's a SM-T800. I had Lollipop on it. Don't know much else to add, but please help!
Thanks all.
Click to expand...
Click to collapse
Well... you said you just updated to lollipop, but in order to not stay stuck at splash screen, you have to factory reset. I saw that you don't want to lose your games and such so you probably only have one option. That option is to flash twrp and make a nandroid of your data. Simply boot into download mode, download the twrp .tar http://twrp.me/devices/samsunggalaxytabs105.html
And now go into Odin, untick autoreboot, now hit the pda/AP button and pick the twrp tar. Hit start and let it do its thing. Now after its done flashing, your gonna have to force reboot. Simply hold power+volume up and down+home button all at the same time. Wait a bit and when the screen turns black, quickly press power+volume up+ home buttons all at the same time and it should boot into twrp.
Now in twrp, hit backup and hit backup data. Hopefully that should save your apps installed. Now after its done, go into wipe and silde factory reset. It should remove installed apps from Google play store and it won't remove pictures and such. It just removes the apps you installed. Then now reboot and wait....
Hopefully this helped
-DUHA
As said you will have to factory reset, this will wipe data and cache.
You can use the link you posted above to install TWRP and root.
http://forum.xda-developers.com/galaxy-tab-s/development/root-cf-autoroot-twrp-t800-t3079488
Lollipop changes the data partition so even if you back it up and then restore it with twrp In kitkat it likely won't boot afterwards.
All you can do is wipe it and take the hit.
Alright, I have TWRP running. The size of my "data" is just over 16 gig, and my space on the sdcard is 14.9 gig, so I've been trying to delete data to knock it down. I still have 1.3 gig to go. Everything I'm deleting, in the data folder, is barely making an impact.
I see what you're saying that I probably won't be able to restore it and have it work, but I still will try. I can always factory reset it again later. Once I wipe it, though, and update back to lollipop, couldn't I restore that data backup?
I gotta take a break and knock out some real work, lol, then I'll continue, and update here. If nothing else, maybe it'll help some other poor soul like me in the future!
Once I have it booting all the way again, do I just use TWRP to install SuperSU and it's rooted? Thanks again. I appreciate it!
Not sure what youre trying to do here. Just wipe the data partition with twrp,
Sent from my SM-T805 using XDA Free mobile app
Ashyx, I was just trying to save my game data, while ending up with a rooted tab. And you were right, of course! I tried to restore the back up to no avail, haha....well, I wiped it again, and it booted up just fine, and it is rooted to boot. I can't believe it was that easy with TWRP to root it.
I'm betting this isn't going to work out, but is there anyway to extract my game data from that backup I made, and transfer just that back to my tablet? If it is possible, it'll probably be beyond my ability, I bet, but I'm just curious.
One other question. With TWRP, can I get Lollipop back on it? Or do I need something else on it first?
Now, it's off to figure out how to get my Impulse Controller to work with it so I can play my games with it!
Thanks for helping me out, regardless. I truly thought I had bricked my $600 tablet. My wife would've killed me for wasting that much money, lol!
There is an app called nandroid manager that will allow you to extract data from nandroids, you could extract your game data with that.
The better way would be to make a system and data backup of your current system, reflash lollipop then restore your lollipop data backup. Then back up your game data with titanium backup.
Restore your kitkat backup then restore your game data with tb.

Weird automatic App installation after going back to stock

Hey Guys,
ive got some serious issues with my G3 (D855) after going back to stock.
After a CM13 nightly get bootlooping my device i decided to switch to AICP MM which was really stable at first time. I ve updated AICP with the newest nightly (dirtyflash) and then i get into bootloop again, but this time something really bad happened - i was able too boot into twrp but not able to copy files onto the phone - it seems like the device get frozen after a few seconds of copying - or maybe it get too hot, i dont know what was the reason, but i thought i will going back to stock to prevent issues like this in the future.
I downloaded the needed correct .tot and .dll from here and used this method: Click
Everything worked fine and Android was booting and then after Language selection the first error like "Couldn´t start script... because of the carrier...". After closing the first steps, my phone was installing automatic bloatware (about 100 apps) which i couldn´t stop.
This is a reason why i decided to try something else: I rooted the phone and installed TWRP again, because i have a stock nandroid backup which i wanted to restore.
Everything worked fine again but the same error after the language selection and the same bloatware that will be installed automatic.
Factory reset and still this issues.
Newest stock flashed with official LG Suite - still the same issues.
Newest .kdz flashed with Flashtool - still the same issues.
It seems the code to install this bloatware is stored somewhere but i can´t find out where.
Somebody know where it hides and how to delete it?
I would prefer delete everything from the phone and install everything again clean. (Hopefully without Bloat)
Any ideas?
Really nobody knows how to completely remove everything and then clean flash stock?
Me again - seems to be my very own thread :laugh:
I´ve tried a few things (full wipe, factory reset, ..) but still these self installing apps, 4-5 freezes on stock per day, bad performance - it seems like a task is running in the background.
then after Language selection the first error like "Couldn´t start script... because of the carrier...".
Click to expand...
Click to collapse
As i mentioned above i get an error message after some start ups or after the language selection, but now i´ve found a screenshot from the error message, look here
Some ideas what else i could try to fix that issues?
thanks

Unfortunately NetworkSystemProvider has stopped (Google Play services)

I just got done taking the PG1 update and things were working fine except TitaniumBackup had the issue with the writing to SD Card. So I did some research and thought that I could modify the
Code:
/system/etc/permissions/platform.xml
, however when I rebooted the phone, I started getting the dreaded "NetworkSystemProvider" and "Google Play Services" stopped errors every few seconds. I have put the file back the way it was, rebooted, cleared cache & dalvik, but still I get the error. I really do NOT want to factory reset if I can help it.
It's frustrating even more-so because I generally run TitaniumBackups nightly and even TWRP backups pretty regularly too. I just hadn't gotten to one of the later, and ironically I was trying to fix the damn SD card write issue so that I could in fact do my TBs!! #FML
This seems like it should be something fixable no? I do have root and TWRP. I just can't find a good site that explains how to do it. I also tried to run the TWRP 'fix permissions' button too to no avail.
Can I just re-ODIN the PG1 or something worse case? And then re-root? ... without a factory reset I mean, so I keep my data and settings as they are?
I really don't understand how things go so jacked up from just changing an .xml file (and putting it back the way it was)??
Please help! Thanks!
Did you make a backup before you started modifying?
Did you try wiping cache and rebooting? Did you have a backup of the file you modified to restore? Check name and permissions?
If neither of the above help, factory reset and Odin again. Make a backup right after TWRP in case this happens again. Marshmallow is tricky and petty sometimes, unlike the earlier Android OS versions.
What you need is a PG1 modified services.jar for custom ROM. Don't recall seeing one shared for PG1. But there is a custom ROM in development forum.
Sent from my SM-N910P using Tapatalk

Help removing "dm-verity?"

Hey guys,
I've had this phone for a while; bootloader unlock/rooted a few months ago without any issues. I'm looking to sell the phone, and wanted to restore everything back to stock:
So I ODIN'd to stock CPF3. I noticed that the phone was suspiciously laggy, and found out that it's caused by spyware left behind by KingRoot, and is fixable by clearing the EFS folder from root.
So I went back to BPA1, unlcocked BL/rooted, and deleted everything from the efs folder. After reboot, phone was running good as new without any hitches.
The issue arised when I tried to ODIN flash the CPF3 full firmware provided by hsbadr. ODIN would go fine, but when the phone would reboot into the recovery, I'd get a dead Android bot saying "DRK is not installed. Please install DRK" or something along those lines. I ignored it, and the phone booted with no issues.
When I tried to factory reset from within the OS, however, I'd face the DRK and dm-verity verification failure when the phone would boot into the recovery, and it would'nt continue with the factory reset.
Now alarmed, I backed down to BPA1, and when the phone would boot back into recovery after a successful ODIN flash, the process would restart the phone when the progress bar would hit ~1/3 of completion (this happens in the recovery).
Rebooting into the recovery would show an orange "dm-verity failed," and when I try to OTA to CPD1 via external sd, It gives the "cannot update from external sd" error.
Googling the DRK keyword showed that it is KNOX being tripped that caused the issue. So far, neither Google nor the xda-forums have showed how to fix the issue on the 910-V.
I really want to restore the phone to as close-to-factory as possible, and removing this DRK issue would be a great help. Any help is greatly appreciated.
Edit #1: I have tried both this guide and this one to absolutely no avail. What am I missing? DM-Verity refuses to go away
EDIT #2: My brother also has a 910-v, and he hasn't cleared his EFS folder (stupid me for not making a back-up, eh?). Is it safe to clear mine again, and copy-paste his EFS folder into my phone? What are some adjustments I should make to avoid a corrupted IMEI? Any help is appreciated.
EDIT#3: I've tried this method, and it removes DM-verity on the first boot. It returns after factory reset. Currently trying a few different combos of flashing kernels/recoveries etc. to see if I can get it to stick. Permanently. Is it still OK to get by bro's EFS folder?
dm-verity and lagginess
HELP!!!!!!
It is annoying to see the dm-verity failed. The phone works fine but its just at the recovery boot. I am not sure what to do. I have a Galaxy S7 on Verizon. I rooted my phone using ODIN. I unrooted it already and it did not work. I did the Verizon recovery and it did not work either. However, I am not able to access to the recovery menu in my phone. I am rooted and the phone is working fine. It is just slow and it has some glitches on some apps like Snapchat... The video is so laggy it is not even funny. I am not sure if that has anything to do with the dm-verity but I need this 3 issues fixed ASAP. I will forever be grateful. I used my friends S7 that is not rooted and it was SO FAST! I am not sure if the root has anything to do with the lagginess but I doubt it because I have read here in XDA that root actually makes your phone faster.
1) Remove and fix the dm-verity
2) Fix laggy snapchat
3) Laggy phone overall.
My phone is Galaxy S7 on Verizon. SM-G930V
notsonerd said:
HELP!!!!!!
It is annoying to see the dm-verity failed. The phone works fine but its just at the recovery boot. I am not sure what to do. I have a Galaxy S7 on Verizon. I rooted my phone using ODIN. I unrooted it already and it did not work. I did the Verizon recovery and it did not work either. However, I am not able to access to the recovery menu in my phone. I am rooted and the phone is working fine. It is just slow and it has some glitches on some apps like Snapchat... The video is so laggy it is not even funny. I am not sure if that has anything to do with the dm-verity but I need this 3 issues fixed ASAP. I will forever be grateful. I used my friends S7 that is not rooted and it was SO FAST! I am not sure if the root has anything to do with the lagginess but I doubt it because I have read here in XDA that root actually makes your phone faster.
1) Remove and fix the dm-verity
2) Fix laggy snapchat
3) Laggy phone overall.
My phone is Galaxy S7 on Verizon. SM-G930V
Click to expand...
Click to collapse
You might want to go to the verizon S7 forums for that. These are the 910-V forums. Sorry for not being able to help.
Look for how to ODIN flash full stock recovery/firmware in the S7 forums. That is all I can say.
SirLaughsalot said:
You might want to go to the verizon S7 forums for that. These are the 910-V forums. Sorry for not being able to help.
Look for how to ODIN flash full stock recovery/firmware in the S7 forums. That is all I can say.
Click to expand...
Click to collapse
I have a vzw note 4 and I'm getting the dm verity verification failed when I try to a factory reset...been at this for a week so I'm pleading for help.
I posted on dr.cools attempt to fix this before I saw this post. sorry for double posting.
edit--I'm attempting the OP's number 3. will report back. Downloading BOG5 because that's what my version shows on the phonw
Question--Right now I'm stuck at BOG5. Do I need to do anything special to get to PA1 so I can start the root/unlock process again?
edit--just flashed firmware and modem and was able to do a factory reset...now back to rooting and bootloader unlock, hopefully.

Categories

Resources