So this is my first root i ever did and i rooted my old galaxy s7 from verizon and i used this thread for the guidlines https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616 and it was successful. I restarted the phone a could times and had no issue so i proceed to download titanium backup and removed the vzw navigator, the voicemail, the verzion text message app, nfl app, amazon, breifing. I restarted the phone again and now its stuck on the verizon logo screen and hasn't moved since, i wiped the cache, restarted it, tried to boot into safe mode nothing. Can someone help get out this screen and possible help me root my device again to remove the verizon apps please
Related
I rooted my GS4 using the method you listed and successfully rooted the phone. I then downloaded an app called NoBloat from Google Play and I had removed all the AT&T programs on my phone I rebooted and now it only goes as far as the AT&T logo and the screen stays lit. I can still hear my notification ringers but screen is frozen on the AT&T logo...
After i tried
http://download.chainfire.eu/397/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltexx-smg900f.zip
on lollipop on vodafone uk, i got this error message on boot, i press ok and after reboot i got no root
Then i install superuser through twrp that i previously had and keep getting this error message on boot.
The thing is i cant get past it, its covering the whole screen no operating system ui just that in a white box and a press ok, which doesnt work until after 2 minutes.
EDIT: its just constantly saying programs has stopped responding in a loop and cant get into android system. How do i fix this, i tried fixing permission in recovery but that didnt work.
So what i can do without losing all my work on my phone.
I hope you made a backup before flashing root files
Boot into recovery, clear CACHES, reboot - see how you get on with that
If you flashed CF Auto Root, there was no need to flash SuperSU, as it comes part of CF Auto root, someone else just did that and ended up in a boot loop, had to wipe the phone and flash a stock ROM
Thats the thing i didnt, i watched a video saying it wouldnt delete your files rooting and decided not to backup.
I was stuck on samsung logo half the time and other times stick with "unfortunately MTP application has stopped." in a big white box blocking me getting into android.
I tried fix permission, clear cache and delvin cache and nothing worked.
I just system wiped and got in but lost all my work.
Fortunately Google backed up most of my photos and videos and contacts but no sms messages.
Now i gotta get all my apps back on my device and get it back to how it was and hopefully i did not mess any important texts.
Note to self: Always backup.
EDIT: i just had gaaps not working and giving server error, after trying out ways to fix that i tried all the normal stop app and clear cache, and then did fix permission in twrp, and after doing "also fix SELinux contexts" it messed me over and got me back to that white box.
so another note to self not to use "Fix SELinux contexts" as that messed up my system after getting 30 apps back installed.
HI Everyone, I am having this issue with my Note 3.
About six months ago I flashed the Lollipop software.
I backed up my S note files and could not recover them till I worked out this week they were in a zip file on my Google Drive.
Today I tried to get them back by downloading the Titanium file and restoring once I got Titanium working again.
I had to change my SuperSU too allow grant always and block Knox to allow Titanium to have root access.
Anyway, I tried restoring the file and it sat for about half an hour just saying it was restoring.
Then the phone shut off and restarted again.
Now I am constantly getting the Sorry S Note has crashed notification at 1 second intervals. I can see the phone is loading software in the background, but I cannot turn the notification off long enough to press anything else. It wont stop looping.
I have tried booting into recovery and wiping the cache and partition and factory reset. When the phone rebooted, it showed me the first setup page you see when you first start your phone for the first time, so I know the factory reset worked, but immediately the error started popping up again.
I tried booting into safe mode, and it still flashed up.
When you press ok, the notification immediately comes back again, so you have no time to do anything else.
You cannot go into settings, or press any other buttons, another notification shows up right away.
I am currently downloading a new firmware because I think this will be the only solution, has anyone else had this issue, if so how did you fix it, or will the new firmware be the only way?
Can you add screenshots pls?
*COUNCIL: S-Note use 2 folders that have to be in your internal memory: S Note Export (empty) and SnoteData (where you put your .spd files).
Hello.
My Galaxy S4 was dying so T-Mobile just replaced it with an S5. It came with:
LMY47X.G900TUVS1FOJ4
I clicked on Software updates in About device and it did whatever updates, but the version stayed the same. Then I went to autoroot [dot] chainfire [dot] eu and downloaded the correct file to root. I unzipped the file and ran Odin 3.10.6 that came with it. I was able to root the device no problem.
What seemed like a problem afterward was that I couldn't find SuperSU in the Application list. I know the phone was rooted though because I could launch Titanium Backup to restore all my stuff from the S4. I went to the Play Store to download SuperSU. It kept complaining that I needed a new binary, but it would fail every time to update. I even tried downloading the latest SuperSU zip to install in the recovery mode, but that failed too. I really wasn't too worried about this.
While looking up how to root the S5, I saw some posts where people mentioned their root access stopped after 24 hours. I just experienced this when I launched Titanium Backup to begin uninstalling bloatware. I was informed that I didn't have root access anymore.
I figured I'd try to reflash the auto-root through Odin. According to Odin, everything passed, but looking at the device, it said it's already patched and the restore failed, so it aborted.
Now the device is stuck in an infinite reboot loop. I can access both the download and recovery modes, but that's it.
I'd really really like to not have to do a factory wipe as it was a pain to get everything copied over from the S4.
Can I flash it with something else?
Once I can get back in the device, how do I keep the device rooted? Do I have to flash TWRP or CWM?
The only root program I use is Titanium Backup and would really really like to keep using it to makr regular backups.
Thanks a lot.
Try booting into recovery and wiping the CACHES
If it still won't boot, grab a stock ROM from sammobile .com for your model S5 (G900T by the looks of the ROM name) and flash it with ODIN from download mode
That won't wipe your data or anything you've restored, as long as you don't reset
If it still won't boot, you might have to suck it up and factory reset after flashing stock
Was the TiBu backup you restored, rooted? Maybe restoring the backup restored an old version of SuperSU and broke the CF AR version
Might need to go down the TWRP and SuperSU from TWRP recovery route to get it rooted properly if CF AR isn't woprking 100%, which it doesn't for a fair few people
I tried clearing the cache, but that didn't work.
Is there a way to download the stock ROM without having to create an account on the download site?
The Titanium Backup I restored was rooted. Everything was totally fine, until I went back to TB and it suddenly told me I wasn't rooted anymore.
I did try TWRP after I made the original post. I think messed up the device, but I can get in now. I flashed the latest version and booted into Recovery Mode. I clicked on Fix Permissions and possibly one other thing. It let booted farther before the infinite bootloop. It'd show my lock screen and give me 1-2 seconds before rebooting. If I swiped quickly, I could see the home screen with most of my icons gone. Clicked on Apps shows most of the apps are gone. When I removed the SIM card, I stopped getting the infinite bootloop. Here are the list of important programs I have left:
Contacts (all cleared out), Gallery (all present), Messages (all present), My Files (shows files from previously installed programs that I can no longer access), Phone (works when I put the SIM card back in), Settings
Unfortunately, TB and the Play Store are both gone. I might be able to install stuff using adb or by copying files over. I haven't tried, but it doesn't look good. I tried reflashing the CF ROM. It didn't change anything. I suspect I may be looking at a factory reset at this point. I'm happy to try any other suggestions.
Thank you.
whynoteel said:
Is there a way to download the stock ROM without having to create an account on the download site?
Click to expand...
Click to collapse
Wut? lol, just make one, it's free...
XDA does not spoon feed
I created an account and downloaded the stock ROM. I flashed the device and got most of the programs to appear again though the Play Store was still missing. I decided to cut my losses and just do a factory reset. I rooted again and put everything back in place. Now I'm experiencing the problem where I lost root after a day or so of use. I'll start a new thread.
Thanks for your help.
I've tried various root methods without success, last one worked BUT was unable to access the play store, "my files" section or the basic package installer, making it imposible to disable the knox security log for the notification issue and everytime I successfuly root it I can install busybox, supersu and root checker but beyond that I am unable to proceed further. When I restarted the phone it stays stuck in the att boot logo while vibrating from 2-3 times on a loop.
From that point on I have to wipe memory/cache and start all over again...
I Started up the phone without supersu but even that it has factory reset, there is lag from the phone.
anyone help?
I'll post device info
there's also a problem I found myself trying to fix the first problems after rooting it was a "dm-vareity verification" problem, son't know if I spelled correctly but that was basically what it said
Thanks In Advanced. :laugh: