My sister has a Sprint GS3, SPH-L710 and recently installed the 4.4.2 OTA (L710VPUDND8) not realizing that her apps will no longer be allowed to write/backup to her External SD card after the OTA (thanks google ). Anyway, I told her I could probably fix that problem by rooting it and making a few tweaks to restore the ability to write to the external SD card. Does rooting this phone require unlocking the bootloader (can you even unlock the bootloader anymore?) or can I get root without unlocking the bootloader? If so, what is the best/simplest method to use? She doesn't plan to be installing any custom ROMs, won't need a custom recovery and I'd like to root it without wiping her phone if possible. Thanks
This phone doesn't have a locked bootloader, to root just odin the tar for Philz recovery, boot directly into the recovery (uncheck auto reboot in odin, pull battery then boot to recovery) then flash the su.zip in recovery... Then boot the phone and you're rooted... Easy as pie
flastnoles11 said:
This phone doesn't have a locked bootloader, to root just odin the tar for Philz recovery, boot directly into the recovery (uncheck auto reboot in odin, pull battery then boot to recovery) then flash the su.zip in recovery... Then boot the phone and you're rooted... Easy as pie
Click to expand...
Click to collapse
Thank you. Sry for my ignorance, obviously I'm not very familiar with the GS3. Can you direct me to step by step instructions? And will I be able to root her phone without wiping it? I want to keep this a simple as possible and not have to mess with restoring everything on her phone.
I found this on another thread: http://forum.xda-developers.com/showpost.php?p=52610162&postcount=2. Will this procedure work?
Thanks again
It's worked for some people.
Sent from my Sprint Samsung Galaxy SIII with M.O.A.R. v9.0, dkp kernel dated 3/20/2014 and TWRP v2.7.0.0.
I can verify that the method in post #3 above did work. However, after reboot, SuperSU sent a message that it had stopped working. I checked and it was installed. I went and updated SuperSU to the latest version (v1.94) via the market. I then went to SuperSU settings and installed it into the system. I now had root access and SuperSU was running properly. I then installed NextApp SDFix from the market and enabled writing to the external sd card. All is good now, her phone has root access and her apps can now write to the external SD Card. Thanks to all for your help.
Related
Hello...anyone have stock kernel for ATT i927? Thanks.
2.3.6 upgrage is only on AT&T i believe..
and only available through OTA...
So if you are an AT & T Customer swtich back to AT&T Stock kernel and ROM and do an upgrade..
I just installed this kernel http://forum.xda-developers.com/attachment.php?attachmentid=806478&d=1323125030 and tried the update and it still didn't work. Is this the stock ATT kernel?
I think the problem lies in the recovery image. The update may be relying on the original recovery being intact (not ClockworkMod or any other). Thus, it may not be possible to update without having the original recovery in place. I have CWM recovery and the rooted kernel installed and cannot install the over-the-air updates. When I restart the phone after it's downloaded, my phone reboots into CWM and that's it. Rebooting into the OS afterwards gives me the message that the update failed.
While in recovery, I delved a bit into the filesystem using ADB and saw that the update files are there (this thread has a bit of what I'm talking about), but I don't think CWM knows what to do with them, therefore the update fails.
Are people without CWM having this problem? Furthermore, is there any way to return to the stock recovery if this is, in case, the problem?
Could you not use Odin and remove the CWM? Reflash a kernal without the CWM?
dudejb said:
Could you not use Odin and remove the CWM? Reflash a kernal without the CWM?
Click to expand...
Click to collapse
I never installed or used CWM. Is CWM something that gets installed with the rooted ROM? The only app I noticed installed with the rooted ROM was superuser and I deleted it. When I run AVG I still get the warning that my device is rooted, but when I type "su" in the emulator it says denied...is there something else I'm missing? Thanks.
CWM Recovery is what's installed if you have ever followed this guide. It's separate from the kernel and the ROM. On most phones, it's installed from ClockworkMod's ROM Manager, but we have to flash it via Odin. It replaces the stock recovery, but offers more features (such as the ability to flash ROMs from the phone itself, instead of having to use Odin on a PC, as well as allowing for full, or nandroid, backups of the phone).
I am ATT and I updated after I rooted with no problems. Some people reported that the update will fail if you're battery isn't mostly charged.
CWM won't be there unless you specifically installed it.
I would be interested in this too. I have been unable to get the update to go through after having flashed another ROM.
Hey people. I'm seriously pulling my hair out for the last five days. I didn't want to post but you guys are my last hope. I'm not knew to rooting and have flashed many roms on my beloved s3 but this one is killing me.
I've read literally hundreds of threads and watched youtube videos on how to disable/remove this knox app and it's just causing so much grief.
Here's what I have and what i've tried.
Galaxy S3 D2att (on Bell In canada)
Currently running Stock 4.2.2 KOT49H.I747MVLUF0B1
Not rooted (This is my first issue as nothing I've tried will let me root)
Goal is to install Cyanide 5.1 rom or equivalent.
- I've tried uninstalling the knox app from with the app (Settings>About Uninstall) there is no about or uninstall option.
- Odin - Installed the latest openrecoverty-twrp-2.8.5.0 Although it appears to install fine, it won't allow me to mount anything and the console shows many errors in red.
-Samsung's default recovery - gives me an error. No Command with the dead android logo. This does mount the external and internal sd cards and I can flash items, but they all give errors.
_tried flashing a few De-samsungizer scripts, knox removal scripts, Latest SuperSU all unsuccessful. I get the following error.
E:footer is wrong
E: Signature verification failed
(no way to disable signature verification)
Tried un-installing the Knox package with different apps people say works including a few pay apps that I purchased and promptly refunded after they didn't work.
The phone boots up fine with stock so it's not bricked.
Any help would be greatly appreciated. I am unable to even downgrade to 4.1.1 as no recovery will allow me to flash a zip successfully.
:crying:
Flash an rom image that has Knox already removed that what I did I use this guide
http://forum.xda-developers.com/showthread.php?p=28019751
There is no need to disable Knox, root, or enable debugging to install a custom rom.
Use Odin to flash a custom recovery such as twrp or philz. Boot to custom recovery, do a full wipe, flash custom rom.
I have tried put the latest TWRP on via odin and although odin reports no errors, when I boot into recovery, twrp is unable to mount any internal or external sd cards. Gives errors so i am unable to flash any files via recovery.
Try Philz touch for the d2lte of twrp doesn't work.
You're flashing the latest twrp for the d2lte?
Im flashing the latest twrp for d2att. Im at work now . Will give philz twrp when i get home and report back.
Philz should work. After flashing recovery, you can wipe and flash a new rom.
If you want to remove Knox on your existing rom, flash supersu from recovery, reboot, open supersu, and let supersu disable Knox.
audit13 said:
Philz should work. After flashing recovery, you can wipe and flash a new rom.
If you want to remove Knox on your existing rom, flash supersu from recovery, reboot, open supersu, and let supersu disable Knox.
Click to expand...
Click to collapse
Hey Audit, thanks for your help.. Am I correct that I am getting the 'd2lte' version of Philz? This will work with my galaxy S3 on Bell (SGH-I747M)? Im just used to getting a d2att version of roms.
Development for the d2lte and d2att were unified under the d2lte moniker.
Anything designed for the d2lte should work on the d2can and d2att. If something is labelled specifically for a d2can or d2att, this leads me to believe the item is old. That being said, TWRP still uses the d2att labelling scheme for its recovery for the d2lte.
audit13 said:
Development for the d2lte and d2att were unified under the d2lte moniker.
Anything designed for the d2lte should work on the d2can and d2att. If something is labelled specifically for a d2can or d2att, this leads me to believe the item is old. That being said, TWRP still uses the d2att labelling scheme for its recovery for the d2lte.
Click to expand...
Click to collapse
Thanks.. I figured that labeling out after I sent my previous message and let me also say Major thanks for helping me out. Philz worked like a charm.. Was able to install Super SU and disable Knox. Not to decide with 5.1 rom I wanna install.
Hello, XDA Developers. I was having some trouble with the TWRP Recovery. I have the latest version of ODIN and I have rooted my Galaxy S6 before and all. I'm running 6.0.1 on the g920p model. When I went to flash the recovery. It said it passed and was successful (I used the AP option). Then when I go to put it in recovery mode, it is the stock recovery and not the custom one. Is there anything I did wrong? I've tried other recoveries but non seemed to work. Also I've tripped my KNOX but I don't know if that affects it. Thanks for your help.
Unless you root your phone, it stock recovery will overwrite TWRP.
Flash TWRP again, but do not allow it to auto-reboot through ODIN. (Uncheck that box.) Reboot into Recovery, then flash SuperSU to gain root. Then reboot and TWRP will be there.
Follow the instructions here: http://forum.xda-developers.com/spr...ide-how-to-root-marshmallow-sm-g920p-t3338694
I have an older Galaxy S3 that I would like to flash Cyangenmod 13 on. It has the new Kernel, so Towelroot doesn't work. I'm planning to use Kingroot, on device (not ideal), as I hope to do this whole process without a pc (not a necessity, but just preference). Assuming this root works, I'm am going to install TWRP via TWRP manager, and then download the Cyangenmod 13 nightly (will I have to install a certain file manager to place the .img file in the root of the phones root or is it simply putting it in the same place as SD Card and Internal storage Work?). After this, I will boot into recovery, create a Nanadroid backup, then flash Cyangenmod. Will this plan work and are there any major flaws? Thank you!!!!
From my experience with the i747m, if you have access to a pc, search and download cf autoroot for your android version and flash with odin to get root. Its been a few months, but kingroot wouldn't work for my canadian sgs3.
It seems like I don't have complete root with magisk? App says root access and it passes safetynet. TiBu fully works. System update detects modification.. Is this because I used twrp to flash magisk12 and the recovery stuck? Will twrp allow you to install while selecting "keep read only"? At what point does Samsung block ota updates if I'm not flashing supersu into system?
I figured since I have twrp now I'd try hotspot initdv6 and it didn't work. I'm confused here! Anyone have magisk fully working and not tripping anything like ota's? Or snap chat.
lootbooper said:
It seems like I don't have complete root with magisk? App says root access and it passes safetynet. TiBu fully works. System update detects modification.. Is this because I used twrp to flash magisk12 and the recovery stuck? Will twrp allow you to install while selecting "keep read only"? At what point does Samsung block ota updates if I'm not flashing supersu into system?
I figured since I have twrp now I'd try hotspot initdv6 and it didn't work. I'm confused here! Anyone have magisk fully working and not tripping anything like ota's? Or snap chat.
Click to expand...
Click to collapse
If you put a custom recovery on, like TWRP which you use to flash Magisk, you lose the ability to update via OTA.
So am I able to flash stock recovery or too late? Guess I'm just trying to achieve the impossible lol. I understood magisk can maintain true stock ROM, but as you stated twrp botches it. What gets me now is hotspot patch won't work but it flashes fine.
From my understanding, you cant have root without a custom recovery and boot image (and with magisk, you wouldnt want to, since you often need to reflash the magiskv12.zip
(the stock recovery is what actually processes ota updates if im not mistaken)
If you want to go back to stock, just odin the latest tar file. If you do it dirty (without wiping data/system/cache/etc first) it usually turns out alright and you get to keep all your apps and stuff, but youll lose root and custom recovery.