Related
Hi and sorry if i'm wrong here, but i am not able to write in the dev directory, yet.
I unlocked and rooted my phone but now i am not able to update to the new OTA 39002 version.
Is there a way for a temporary unroot or something like this? Because i want to keep my root!
Thank you for help.
baxxter106 said:
Hi and sorry if i'm wrong here, but i am not able to write in the dev directory, yet.
I unlocked and rooted my phone but now i am not able to update to the new OTA 39002 version.
Is there a way for a temporary unroot or something like this? Because i want to keep my root!
Thank you for help.
Click to expand...
Click to collapse
With something like this:
https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper&hl=fr
But root should not prevent for an OTA update
Le_Poilu said:
But root should not prevent for an OTA update
Click to expand...
Click to collapse
Thanks for fast answer.
I thought the same, but when it is starting up to update in the middle it shows the "dead" android with the red "!" , you know.
after that the phone boots normaly and it says "not successfull"...
i already tried some times...
I will try the rootkeeper, thanks for that again.
baxxter106 said:
Thanks for fast answer.
I thought the same, but when it is starting up to update in the middle it shows the "dead" android with the red "!" , you know.
after that the phone boots normaly and it says "not successfull"...
i already tried some times...
I will try the rootkeeper, thanks for that again.
Click to expand...
Click to collapse
Have you change some file (like to disable camera sound ) ?
I've the same issue with OTA, and I revert all changes I've made in the past, and it work.
If you rooted your Device by changing the Kernel, you have to flash the Boot signed of the Base FW (32 i guess).
The update compares the Base Rom and the Root Exploit set you an secured Kernel, that doesn't match with the System > Problem solved.
The Root won't deny the Update. You can temp. unroot with the ported Rootkeeper (thanks to Mattlgroff) and restore the Root after the Update.
But the Boot.img must fit!
I think i did not change something. Except the kernel that came wih the rooting by mattlgroffs tool.
So i need to change the kernel with a recovery kernel via adb?
Could somebody tell me the comands? (With cwm on a SGS was it a bit easier )
Sent from my XT890 using xda app-developers app
Yes, you have to use fastboot for it (it's in the Folder of the root exploit)
Download your current FW, unpack it and copy the Boot_signed into the Root folder. Then open the cmd window, navigate to the Root Folder by cd command.
Flash the image by
Fastboot flash boot boot_signed.
Alternate you can rename it to razr_i_boot.img and overwrite the secured Kernel in the Exploit. Than just root again and it will flash the right secured Kernel.
Thank you. I will try that today. Btw. where can i find mattlgroffs root keeper? The version in the play store does...nothing?
Sent from my XT890 using xda app-developers app
http://forum.xda-developers.com/showthread.php?p=34248515
Warning: crawrj mentioned this wouldn't flash in TWRP. I use CWM, so not sure whether it's compatible with TWRP (or any other recoveries) at the moment. So, if you're not using CWM... I would suggest waiting a bit.
So as most people know, the new OTA update aims to kill root on the device and the motochopper root method. Once I received the update and saw that it removed root, I immediately set out to figure out what was causing the issue. I also noticed that I was getting the notice about an application performing unauthorized tasks, or something to that effect.
After doing a few file deletions and restores, I finally found the file (KNOXAgent.apk) that was causing the notice about unauthorized actions and needing to restart. I've been running the phone with the MDL update for a little over a week now, and I haven't had another notice. I did lose root during the update, but was able to easily root it again with the motochopper method once the KNOXAgent files were removed.
So, here are the steps I took to avoid losing my root.
1) adb shell
2) su
3) mount -o remount,rw /dev/block/platform/msm_sdcc.1/by-name/system /system
4) rm /system/app/KNOXAgent.*
5) Reboot into recovery and flash the OTA zip provided below. It's the OTA update with the KNOXAgent patches removed from the updater-script. This will allow the update to continue installing without having an error about KNOXAgent not being found on the device.
The same process may have to be done with future OTA updates once KNOXAgent is removed, but it's better than losing your root method each time an OTA comes out. As I mentioned, I've been using this phone since May 13th with this being done. I also had to take out the My Files updates as well, since I have the CyanogenMod file browser (My Files doesn't have root support).
Unfortunately, it seems XDA has problems with filtering spam and requires that you have 10 posts before being able to post external links. Since I don't have anything else to post at the moment, and can't post on the development forums to report problems to developers in order to legitimately increase my count without having to spam threads I don't care about, you'll have to copy and paste the link to get the update package.
Update link: http://d-h.st/Dkl
RogueSly said:
So as most people know, the new OTA update aims to kill root on the device and the motochopper root method. Once I received the update and saw that it removed root, I immediately set out to figure out what was causing the issue. I also noticed that I was getting the notice about an application performing unauthorized tasks, or something to that effect.
After doing a few file deletions and restores, I finally found the file (KNOXAgent.apk) that was causing the notice about unauthorized actions and needing to restart. I've been running the phone with the MDL update for a little over a week now, and I haven't had another notice. I did lose root during the update, but was able to easily root it again with the motochopper method once the KNOXAgent files were removed.
So, here are the steps I took to avoid losing my root.
1) adb shell
2) su
3) mount -o remount,rw /dev/block/platform/msm_sdcc.1/by-name/system /system
4) rm /system/app/KNOXAgent.*
5) Reboot into recovery and flash the OTA zip provided below. It's the OTA update with the KNOXAgent patches removed from the updater-script. This will allow the update to continue installing without having an error about KNOXAgent not being found on the device.
The same process may have to be done with future OTA updates once KNOXAgent is removed, but it's better than losing your root method each time an OTA comes out. As I mentioned, I've been using this phone since May 13th with this being done. I also had to take out the My Files updates as well, since I have the CyanogenMod file browser (My Files doesn't have root support).
Unfortunately, it seems XDA has problems with filtering spam and requires that you have 10 posts before being able to post external links. Since I don't have anything else to post at the moment, and can't post on the development forums to report problems to developers in order to legitimately increase my count without having to spam threads I don't care about, you'll have to copy and paste the link to get the update package.
Update link: d-h.st/Dkl
Click to expand...
Click to collapse
Nice find
travisw0204 said:
Nice find
Click to expand...
Click to collapse
Thanks. It took a bit to find, but I couldn't live without root. My battery is GAWD with the CPU limited. :3
OK I am messing around with this and providing feedback. It doesn't install on the stock recovery for obvious reasons. It doesn't install in TWRP. Gives update binary error. Have to backup my extsd so I can format to fat32 to test other recoveries.
crawrj said:
OK I am messing around with this and providing feedback. It doesn't install on the stock recovery for obvious reasons. It doesn't install in TWRP. Gives update binary error. Have to backup my extsd so I can format to fat32 to test other recoveries.
Click to expand...
Click to collapse
Weird. Flashed for me on CWM when I used it.
RogueSly said:
Weird. Flashed for me on CWM when I used it.
Click to expand...
Click to collapse
Yeah I am guessing it will work in CWM. But I have to backup and format first to test. Which recovery did you use?
crawrj said:
Yeah I am guessing it will work in CWM. But I have to backup and format first to test. Which recovery did you use?
Click to expand...
Click to collapse
I've been using http://forum.xda-developers.com/showthread.php?t=2254323. I tend to stay away from touch recoveries when there are 4 dogs in the house.
Lol, too little too late for me. :facepalm:
Ok it installed on Garwynn's CWM but it didn't install the modem. Is that your results also? Won't install with OUDhs either. Gives error 7. I can confirm that root works without knoxagent installed. That is runny really. We find out right away that knox was causing the security warning. But since the kernel was so widely talked about as being the killer of root we completely overlooked knox as being more than just the alert Thanks for figuring that out.
Edit: Also installs on Agat's recovery but doesn't install the modem.
Edit Again: Ok just as an FYI this no longer is an issue. Chainfire has done it again. His latest SuperSU 1.30 fixes the root issues on MDL. You can use the stock kernel and leave knox alone.
crawrj said:
Ok it installed on Garwynn's CWM but it didn't install the modem. Is that your results also? Won't install with OUDhs either. Gives error 7. I can confirm that root works without knoxagent installed. That is runny really. We find out right away that knox was causing the security warning. But since the kernel was so widely talked about as being the killer of root we completely overlooked knox as being more than just the alert Thanks for figuring that out.
Edit: Also installs on Agat's recovery but doesn't install the modem.
Edit Again: Ok just as an FYI this no longer is an issue. Chainfire has done it again. His latest SuperSU 1.30 fixes the root issues on MDL. You can use the stock kernel and leave knox alone.
Click to expand...
Click to collapse
Awesome! Glad to hear it's fixed. Not sure why the modem didn't install. I didn't get any errors on my device after taking out the patches for My Files and KNOXAgent, as both were missing on my system. I'll try restoring back to MDC and updating to SuperSU 1.3 to test it.
crawrj said:
Ok it installed on Garwynn's CWM but it didn't install the modem. Is that your results also? Won't install with OUDhs either. Gives error 7. I can confirm that root works without knoxagent installed. That is runny really. We find out right away that knox was causing the security warning. But since the kernel was so widely talked about as being the killer of root we completely overlooked knox as being more than just the alert Thanks for figuring that out.
Edit: Also installs on Agat's recovery but doesn't install the modem.
Edit Again: Ok just as an FYI this no longer is an issue. Chainfire has done it again. His latest SuperSU 1.30 fixes the root issues on MDL. You can use the stock kernel and leave knox alone.
Click to expand...
Click to collapse
I was going to ask an annoying question.... but decided it was annoying and did a search. here is what I found in the difference between SuperUser and SuperSU and SuperSU Pro ($2.49). Reference: http://android.stackexchange.com/qu...ruser-from-chainsdd-and-superuser-from-clockw
SuperSU improves everything about Superuser and adds more options. The free version offers faster notifications, there is possibility of disabling them for each app and a new interface, attractive and easy to handle. In addition, according to developer claims by using SuperSU you’ll enjoy higher speed from the apps that require root rights, especially on Android 4.0+. The paid version called SuperSU Pro provides the opportunity to keep root rights after a system update, which usually cancels these rights. Although the method is not guaranteed the option is very useful. We have password protection and advanced log configuration settings for each application.
You might also want to read SuperSU Brings Better SuperUser Root Permission Management to Android. Quoting from that article:
SuperSU is basically SuperUser on steroids. According to the developer, it “allows for advanced management of Superuser access rights for all the apps on your device that need root.”.
Edit: ::FacePalm:: What ever you do. Do not uninstall SuperUser after you install SuperSU. You will loose Root. LOL (Hey at least I can laugh at myself.) I am not worried about it yet... I know I will get it back eventually.
Edit 2: After reading the OP, all you have to do if you have TWRP Recovery installed is do the OTA, your update will install and you will automatically reboot into TWRP.
Go to Mount first and mount System.
Go to back to home and select Advanced.
Go to File Manager. NOTE: This can be very frustrating! Use BACK and Sort Options to reset Sorting if it keeps doing things you don't want it to do. Also (Up A Level) is handy. If you are on "/" directory, touch Sort Descending: Name and you will see System. Select Sysytem.
Now Sort Ascending you will see App. Select App.
Gentally and slowly Swipe down in the middle to reach Knox. I found 2 files. Select one at a time and delete them.
Reboot
Then rerun Motochopper Root method.
I am on Stock MDC still. So if you are on MDL I am not sure if this would work. Now follow the directions that I failed to see when you install SuperSU.
Install SuperSU. Open SuperSU and make sure SU binary is switched from SuperUser to SuperSU. Once you do that you can remove SuperUser.
Edit 3: Once you check to make sure SuperSU has Binary after a reboot... SuperSU will remove SuperUser for you. No need to do anything.
After all said and done... I am thinking that the TWRP stopped the OTA from installing. I have been extremely busy with work, so no time to read XDA lately has been stopping me from keeping up to date. I just need more time in the day.
crawrj said:
Ok it installed on Garwynn's CWM but it didn't install the modem. Is that your results also? Won't install with OUDhs either. Gives error 7. I can confirm that root works without knoxagent installed. That is runny really. We find out right away that knox was causing the security warning. But since the kernel was so widely talked about as being the killer of root we completely overlooked knox as being more than just the alert Thanks for figuring that out.
Edit: Also installs on Agat's recovery but doesn't install the modem.
Edit Again: Ok just as an FYI this no longer is an issue. Chainfire has done it again. His latest SuperSU 1.30 fixes the root issues on MDL. You can use the stock kernel and leave knox alone.
Click to expand...
Click to collapse
Well, crawrj.. I just rawly patched the modem.bin with the modem.img.p, and the baseband version and such still hasn't increased. My software version and baseband version are still showing MDC, while build number is showing MDL. The weird thing about it is the kernel also updated from its original. How does the modem not update when it's being directly flashed onto the partition? Trying to get all of my stuff over to MDL, if that's what it's supposed to be. It has the new boot sound and such, but the inconsistent version numbers make me hesitant that the update fully applied.
RogueSly said:
Well, crawrj.. I just rawly patched the modem.bin with the modem.img.p, and the baseband version and such still hasn't increased. My software version and baseband version are still showing MDC, while build number is showing MDL. The weird thing about it is the kernel also updated from its original. How does the modem not update when it's being directly flashed onto the partition? Trying to get all of my stuff over to MDL, if that's what it's supposed to be. It has the new boot sound and such, but the inconsistent version numbers make me hesitant that the update fully applied.
Click to expand...
Click to collapse
There is some kind of write protection of security that locks the modem down. I have tried 100 different ways of installing the modem and can't. It looks like the official installs are the only ones that work. So right now the ota is the only way to get the modem. But I am sure we will get it figured out in time.
Sent from my SPH-L720 using xda premium
crawrj said:
There is some kind of write protection of security that locks the modem down. I have tried 100 different ways of installing the modem and can't. It looks like the official installs are the only ones that work. So right now the ota is the only way to get the modem. But I am sure we will get it figured out in time.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
Well, that sucks. I guess I will give up trying to flash it for now. Already removed KNOXAgent again and dropped faux's kernel on here. It's showing my build as MDL, so at least I don't get pestered by the update message.
aww come on lol too late for me too. I went through hell rooting my phone when i upgraded to MDL. I flashed the stock rom like 3 times before getting my phone rooted and the last piece of the puzzle were the knox files. Instead of deleting the files i froze them using the system tuner off from the playstore after i installed shabbat's custom kernel.
Do we know of a way to avoid all these run arounds to root on MDL by keeping the stock kernel and without removing knox???
tones160 said:
aww come on lol too late for me too. I went through hell rooting my phone when i upgraded to MDL. I flashed the stock rom like 3 times before getting my phone rooted and the last piece of the puzzle were the knox files. Instead of deleting the files i froze them using the system tuner off from the playstore after i installed shabbat's custom kernel.
Do we know of a way to avoid all these run arounds to root on MDL by keeping the stock kernel and without removing knox???
Click to expand...
Click to collapse
I think there are a few posts in the development sections that will help out with getting root on MDL. If it were me, I would just pull the SuperSU apk and unzip it. Grab the su binary out of there, push it to /system/xbin/, and then install SuperSU on the phone once it restarted. Now, I can't confirm that works... because I haven't had to get that dirty with rooting my phone. Motochopper worked perfectly fine when KNOXAgent was removed, so it should work if you have KNOXAgent frozen too.
Cf autoroot
wanna make sure I understand this right. I'm gonna flash this no knox update on top of forcesrom (which has knox removed), I should be ok right? but the modern still not install this way, is that correct? and I won't be able to update my modem until a new method comes out. do I got it all right? thanks! :thumbup::what:
gershee said:
wanna make sure I understand this right. I'm gonna flash this no knox update on top of forcesrom (which has knox removed), I should be ok right? but the modern still not install this way, is that correct? and I won't be able to update my modem until a new method comes out. do I got it all right? thanks! :thumbup::what:
Click to expand...
Click to collapse
That's apparently right, for now. I'm working on figuring out why the MDM partition won't flash. I tried to patch the files manually, as mentioned previously and here, but it seems that it didn't flash as the baseband didn't change?
Hopefully figure it out soon.
Getting E:Error in /external_sd/OTA 5-13-2013 (No Knox Agent), Status 7. Any advice?
Ok so i am a retard and accidently deleted the ATT OTA update app. Any idea how to get it back or how i can update my S4 i517 when the time comes for 4.3 ?
Thanks!
(Yes i know i am an extreme noob )
Title is kinda
self explanatory, for too long reasons to explain I don't have CWM Recovery so I have ADB and want to remove AT&T bloatware. Can I do this through ADB, without root? (Well I am rooted, but I'm stuck on stock so yeah). Without root? No. But you say you are rooted, and if you are, then yes. If you can do "adb root", you can uninstall them.
re: OTA app
SkiRac3rDud3 said:
Ok so i am a retard and accidently deleted the ATT OTA update app. Any idea how to get it back or how i can update my S4 i517 when the time comes for 4.3 ?
Thanks!
(Yes i know i am an extreme noob )
Click to expand...
Click to collapse
I am assuming that your phone is rooted...................
If you already downloaded a cwm/twrp flashable custom rom then skip the next line.
Download the stock based cwm/twrp flashable zip file rom. (if you don't already have it).
-----
With your computer find whatever filename you deleted in the zip file rom which
you have or will be downloading then copy the OTA file to /system/app in your phone.
After that reboot the phone and the OTA app should be functional.
Good luck!
I'm making some progress on rooting this device. I finally managed to extract the necessary kernel addresses that will allow us to use iovyroot.
The next step is to just compile that program using the addresses which I will link to at the bottom of this post, and run it. I'm hoping that somebody else will do this step since I need a break from working on this.
Prerequisite: You must first use the instructions in this post to roll back to OI5.
The files:
kallsyms.txt
addresses.txt
(they were too big to attach)
Greek2me said:
I'm making some progress on rooting this device. I finally managed to extract the necessary kernel addresses that will allow us to use iovyroot.
The next step is to just compile that program using the addresses which I will link to at the bottom of this post, and run it. I'm hoping that somebody else will do this step since I need a break from working on this.
Prerequisite: You must first use the instructions in this post to roll back to OI5.
The files:
kallsyms.txt
addresses.txt
(they were too big to attach)
Click to expand...
Click to collapse
I am trying this will update.
Greek2me said:
I'm making some progress on rooting this device. I finally managed to extract the necessary kernel addresses that will allow us to use iovyroot.
The next step is to just compile that program using the addresses which I will link to at the bottom of this post, and run it. I'm hoping that somebody else will do this step since I need a break from working on this.
Prerequisite: You must first use the instructions in this post to roll back to OI5.
The files:
kallsyms.txt
addresses.txt
(they were too big to attach)
Click to expand...
Click to collapse
Any updates?
Also wondering if there is any updates? Would love to root this phone. Would help if I knew how to do it all.
I don't mean to be pessimistic, and I suppose it'll still be useful for those who don't want Marshmallow, but the rumor is it releases on the 18th. That's according to AT&T support, I might add. Again, keep up the great work, it isn't for nothing certainly, but I'm dying to update to Marshmallow, so this will be obsolete for me by the time you're finished.
Greek2me said:
I'm making some progress on rooting this device. I finally managed to extract the necessary kernel addresses that will allow us to use iovyroot.
The next step is to just compile that program using the addresses which I will link to at the bottom of this post, and run it. I'm hoping that somebody else will do this step since I need a break from working on this.
Prerequisite: You must first use the instructions in this post to roll back to OI5.
The files:
kallsyms.txt
addresses.txt
(they were too big to attach)
Click to expand...
Click to collapse
Got the binary compiled with thanks to @zxz0O0. It didn't work on my device but it could work on yours.
1. Download file
2. Extract
3. "adb push iovyroot /data/local/tmp
4. "adb shell"
5." cd /data/local/tmp"
6."chmod 777 iovyroot"
7."./iovyroot"
How's this going?
I've been too busy to look at this lately. Maybe I'll try it next week or the week after.
Has anyone gotten it to work?
Ok I got the files in place how do you test?
G900aucu4bof3
Instructions say i need to roll back to OI5, im on OF3.
Ppl say all around that i can't roll back or anything, because that will brick it.
If this is not true, how can i do it, in order to test this root process?
I am on OF3 Rooted. If there is a way to do it from there then I will try it. Would this help achieve root on 6.0? If not then there is no reason for this.
I have a question, can I rollback to OI5 after I flashed the 4 PA2 files (BL, AP, CP, and CSC) on my phone?
dave1977nj said:
I am on OF3 Rooted. If there is a way to do it from there then I will try it. Would this help achieve root on 6.0? If not then there is no reason for this.
Click to expand...
Click to collapse
How is that possible? Did you have 4.4? Im on 5.0 And OF3, "everyone" say i can't do anything just yet.
If I am following the discussion here, folks are trying to root 5.0 OF3.
I am rooted G900AUCU4BOF3.
Three Steps:
Downgrade Samsung Galaxy S5 from 5.0 to 4.4 KitKat ([STRIKE]http://forums.androidcentra...amsung-galaxy-s5-5-0-4-4-kitkat.html[/STRIKE])I am mistaken. This is for the Verizon version NOT AT&T
Root 4.4.4 (http://forum.xda-developers.com/showpost.php?p=62467916&postcount=5)
Upgrade 4.4.4 to 5.0 Rooted (http://www.droidviews.com/install-rooted-lollipop-on-att-galaxy-s5-sm-g900)
NOTE: If you want to add WiFi Hotspot / Tether use G900A_OF3_TetherAddOn.zip instead of G900A_OC4_TetherAddOn.zip. The G900A_OF3_TetherAddOn.zip file is found at https://www.androidfilehost.com/?w=files&flid=27720 along with many other useful files such as other ROOTED Stock ROMs for the G900A.
I am rooted and on G900AUCU4BOF3. However, I started from 4.4.4
There is no 6.0 Root Method yet. Maybe you folks here working on iovyroot will advance the cause
bardell3600 said:
If I am following the discussion here, folks are trying to root 5.0 OF3.
I am rooted G900AUCU4BOF3.
Three Steps:
Downgrade Samsung Galaxy S5 from 5.0 to 4.4 KitKat (http://forums.androidcentral.com/sa...wngrade-samsung-galaxy-s5-5-0-4-4-kitkat.html)
Root 4.4.4 (http://forum.xda-developers.com/showpost.php?p=62467916&postcount=5)
Upgrade 4.4.4 to 5.0 Rooted (http://www.droidviews.com/install-rooted-lollipop-on-att-galaxy-s5-sm-g900)
NOTE: If you want to add WiFi Hotspot / Tether use G900A_OF3_TetherAddOn.zip instead of G900A_OC4_TetherAddOn.zip. The G900A_OF3_TetherAddOn.zip file is found at https://www.androidfilehost.com/?w=files&flid=27720 along with many other useful files such as other ROOTED Stock ROMs for the G900A.
There is no 6.0 Root Method yet. Maybe you folks here working on iovyroot will advance the cause
Click to expand...
Click to collapse
Nope. Nope nope nope
Downgrading from OF3 to NCE will brick your device.
Just upgrade from OF3 to OI5 and attempt to root.
UPDATE: Tried this on my phone a couple times. Keeps hanging at "Installing func ptr". If anyone around here knows how to fix it I can send any files required from the phone to make it work (@NavSad)
AptLogic said:
Nope. Nope nope nope
Downgrading from OF3 to NCE will brick your device.
Just upgrade from OF3 to OI5 and attempt to root.
UPDATE: Tried this on my phone a couple times. Keeps hanging at "Installing func ptr". If anyone around here knows how to fix it I can send any files required from the phone to make it work (@NavSad)
Click to expand...
Click to collapse
Which file are you having trouble on?
NavSad said:
Which file are you having trouble on?
Click to expand...
Click to collapse
I pushed the file to my /data/local/tmp, chmodded 777, and ran the file, but when I ran it, the process would go so far as something like "Starting Read Service" or something like that, display "Done", and then hang. Of course, seeing iovyroot in action, I know for a fact that it didn't finish, because there would be more output and I would get a root shell.
AptLogic said:
I pushed the file to my /data/local/tmp, chmodded 777, and ran the file, but when I ran it, the process would go so far as something like "Starting Read Service" or something like that, display "Done", and then hang. Of course, seeing iovyroot in action, I know for a fact that it didn't finish, because there would be more output and I would get a root shell.
Click to expand...
Click to collapse
Someone's had this problem here:https://github.com/dosomder/iovyroot/issues/37
The easiest way to get offsets for OI5 is to ask someone who is already rooted to do this:
su
cat /proc/kallsyms
Then ask them to copy and paste that output.
NavSad said:
Someone's had this problem here:https://github.com/dosomder/iovyroot/issues/37
The easiest way to get offsets for OI5 is to ask someone who is already rooted to do this:
su
cat /proc/kallsyms
Then ask them to copy and paste that output.
Click to expand...
Click to collapse
Well, unfortunately I don't know anyone with a rooted G900A. Most people I know made the smart decision to jump ship from AT&T and go to T-Mobile instead, and only one friend of mine has an S5 (G900T)
Shame... I got really hyped for nothing (oh well :/)
I finally managed to root my SM-N960F a few weeks ago (after some trial and error).
There is a 3.4 GB file named "update.zip" in the root of my main storage. I can delete it now, right?
Any idea what this is? My memory (mine, not the phone's) is horrible...
Dougmeister said:
I finally managed to root my SM-N960F a few weeks ago (after some trial and error).
There is a 3.4 GB file named "update.zip" in the root of my main storage. I can delete it now, right?
Any idea what this is? My memory (mine, not the phone's) is horrible...
Click to expand...
Click to collapse
Quick Google Search Returned This--> Yes you can delete them as they are OTA files downloaded when updates were installed previously..
N1NJATH3ORY said:
Quick Google Search Returned This--> Yes you can delete them as they are OTA files downloaded when updates were installed previously..
Click to expand...
Click to collapse
Thank you. Must've been using the wrong search words.
I need to root it, too!
My dear friend, could you, please, share how you manage to rood it? I never had the need with this phone, but now I have accidentally deleted some important pictures, stored in the main memory and can't restore them without root. Have you managed to root without tripping the Knox? I had all my older Notes rooted, so I have some basic knowledge...
Thanks a lot!
sidney21 said:
My dear friend, could you, please, share how you manage to rood it? I never had the need with this phone, but now I have accidentally deleted some important pictures, stored in the main memory and can't restore them without root. Have you managed to root without tripping the Knox? I had all my older Notes rooted, so I have some basic knowledge...
Thanks a lot!
Click to expand...
Click to collapse
Not sure what Android version your on ? Follow this link-->https://forum.xda-developers.com/galaxy-note-9/how-to/guide-root-note-9-magisk-android-10-q-t4039783