Develop Bugs

[Q] rooting SGH-T999 with Skipsoft

I've read as much as I can and I just need a little more help. I want to be able to root my T-Mobile Galaxy S3, SGH-T999.
1. Is there any other way to pull files from /data/data without rooting?
2. Can I just do a simple root and then later root with CWM or TWRP using another option?
3. I thought rooted was rooted, what is the need for "insecure boot"? Is that the only way to get a file image backup of my partitions?
4. None of the rooting options in the Skipsoft Android Toolkit wipe the device, correct?
5. Is the only way to be able to "recover" back to stock by installing a "custom recovery"?
All of the options include "custom recovery". What if I just want to root the device and install a custom recovery later? Or it custom recovery included in all the options so I can get back to stock if I mess up? Thanks!

I am not sure why you'd need to go to such extent.
By your question on Insecure Kernel, I assume, you have Stock 4.3 update. If so, please flash SuperSU Zip via Custom Recovery. You can Also flash Root66 of 4.3 (UVUEMJC ) to get Root as well. None of these methods are destructive and make you loose your data.
As to your other questions, /data/data should be accessible read only to Good File explorers such as ES File Explorer. My Backup Pro should be able to backup those files too. Insecure boot is needed to root as SELINUX Enforcing will not let you have Stable Root. Best Flash ATT Insecure Kernel Posted on this sub forum. I don't understand what you mean by "Recover to Stock".

can't do anything without root
I tried ES File explorer and 2 others, they show /data/data as blank. Most everywhere I've looked says you have to have root

In that case please post your Current Android version and what you see under Baseband. What step we take next depends on this information.

rooting galaxy
perseus71 said:
in that case please post your current android version and what you see under baseband. What step we take next depends on this information.
Click to expand...
Click to collapse
4.3, t999uvuenc2

fdecker said:
4.3, t999uvuenc2
Click to expand...
Click to collapse
Root 66 Will not work you will need Auto Root, CWM/TWRP and Update SuperSU for a complete root.
CF-Auto-Root-d2tmo-d2tmo-sght999.tar
openrecovery-twrp-2.7.0.0-d2tmo
UPDATE-SuperSU-v1.93
DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V1.0
For a suceed root and Knox remove.

Thanks!
jmberumenb said:
Root 66 Will not work you will need Auto Root, CWM/TWRP and Update SuperSU for a complete root.
CF-Auto-Root-d2tmo-d2tmo-sght999.tar
openrecovery-twrp-2.7.0.0-d2tmo
UPDATE-SuperSU-v1.93
DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V1.0
For a suceed root and Knox remove.
Click to expand...
Click to collapse
Thanks, this is great. I rooted the same model phone that was on OS 4.1.2 by uploading root66 with Odin and it worked in one step. I see now that root66 is not the way to go on the 4.3 phone just yet. I will follow your tips. I see too that I have to get rid of Knox and make sure the recovery partition does not get reset. Think I should put busybox out there too, or with TWRP and SuperSU do I have all I need?
Thank you very much for your help!

fdecker said:
Thanks, this is great. I rooted the same model phone that was on OS 4.1.2 by uploading root66 with Odin and it worked in one step. I see now that root66 is not the way to go on the 4.3 phone just yet. I will follow your tips. I see too that I have to get rid of Knox and make sure the recovery partition does not get reset. Think I should put busybox out there too, or with TWRP and SuperSU do I have all I need?
Thank you very much for your help!
Click to expand...
Click to collapse
I used the TWRP and SuperSU method no problems so far.

TWRP and SuperSU
jmberumenb said:
I used the TWRP and SuperSU method no problems so far.
Click to expand...
Click to collapse
I'll give that a try then.

busybox?
One last question: Would you load busybox as well?

fdecker said:
One last question: Would you load busybox as well?
Click to expand...
Click to collapse
Nah I wouldn't unless its required by your Rom or something.

[Q] new tablet

Hi
Im just get this tablet today and have some questions about it
The model is p600 wifi
1. If i want to root just flash the cf auto root and then remove the knox apps with titanium backup?
2. After the root to flash another rom just install the goomanager and with that the recovery installs by itself or thats not the way to do it?
3. To flash another rom is necessary or recomended to flash another kernel?
Thx for the help

Masterchivo said:
Hi
Im just get this tablet today and have some questions about it
The model is p600 wifi
1. If i want to root just flash the cf auto root and then remove the knox apps with titanium backup?
2. After the root to flash another rom just install the goomanager and with that the recovery installs by itself or thats not the way to do it?
3. To flash another rom is necessary or recomended to flash another kernel?
Thx for the help
Click to expand...
Click to collapse
1-flash CF auto root then install SuperSu and it will delete knox automatically
2-you should flash TWRP recovery by odin then download any rom from here and flash it with the recovery
3-nop not necessary
Press thanks if i help you

If you wanted to keep your warranty intact you can also try towel root if you haven't updated yet. Can't flash custom roms that way but may not need to thanks to the xposed framework
Sent from my SM-N9005 using Tapatalk

dr.m0x said:
If you wanted to keep your warranty intact you can also try towel root if you haven't updated yet. Can't flash custom roms that way but may not need to thanks to the xposed framework
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
He mentioned p600 so towelroot will NOT work on his device and flashing CFautoroot will triggered Knox.

buhohitr said:
He mentioned p600 so towelroot will NOT work on his device and flashing CFautoroot will triggered Knox.
Click to expand...
Click to collapse
Yeah I need to stop reading xda while I'm on the can.
Sent from my SM-N9005 using Tapatalk

SuperSU Error after cf-auto

Hi friendly xda android enthusiasts. I have, after many issues, finally rooted my gt-n5110 using odin and cf-auto. Workered without a hitch. Odin passed, tab rebooted, and BAM, "superSU has stopped working". I immediately navigated myself over to the playstore to reinstall SuperSU and for the first time i have ever seen it wouldnt allow me to. It only gave me a choice to open. No update no uninstall. Going into my apps list it was not present on downloads but was available on device list. Clucked it and no option to uninstall, only to force stop or turn off. So it is incorporated as a system with no access to it. This has me stumped. I have only seen old threads with answers to this and they are temp fixes. Need to know what i can do to fix this on a permanent basis and if someone could help me understand how and why this issue occured it would give me a better understanding and possibly prevent further issues. Thanks in advance guys.

Try the flashable version in this post after you install a custom recovery with odin.
ramjet73

ramjet73 said:
Try the flashable version in this post after you install a custom recovery with odin.
ramjet73
Click to expand...
Click to collapse
This may be a very stupid question but i have to be sure. As i stated the odin DID pass the auto root and tab rebooted. But along with the superSU error i ran root checker and was unable to obtain root. Im assuming its because supersu is not embedded. So with that said is it still ok to attempt to flash a recovery to the tab?

mattdiehl83 said:
This may be a very stupid question but i have to be sure. As i stated the odin DID pass the auto root and tab rebooted. But along with the superSU error i ran root checker and was unable to obtain root. Im assuming its because supersu is not embedded. So with that said is it still ok to attempt to flash a recovery to the tab?
Click to expand...
Click to collapse
Yes. Recovery is independent of whether or not you are rooted. You can install it from Android using tools like Flashify once you are properly rooted, but Odin works fine as long as you have a version of recovery in that format.
Flashing SuperSU from a custom recovery once it is installed should fix the superuser problems you are having.
ramjet73

ramjet73 said:
Yes. Recovery is independent of whether or not you are rooted. You can install it from Android using tools like Flashify once you are properly rooted, but Odin works fine as long as you have a version of recovery in that format.
Flashing SuperSU from a custom recovery once it is installed should fix the superuser problems you are having.
ramjet73
Click to expand...
Click to collapse
Doing now. Thankyou. Fingers crossed.

I had the same issue on my 5110. The flashable root only worked for me until I rebooted, then it would lose root. What ultimately worked for me was to unroot with Kingo. Then with USB debugging enabled, re-rooted with Kingo (which took around 10 min).
Sent from my AT&T Galaxy Note 3 using Tapatalk®

andygev35 said:
I had the same issue on my 5110. The flashable root only worked for me until I rebooted, then it would lose root. What ultimately worked for me was to unroot with Kingo. Then with USB debugging enabled, re-rooted with Kingo (which took around 10 min).
Click to expand...
Click to collapse
If flashing SuperSU from recovery doesn't result in a successful rooted system someone should let @Chainfire know. I've never had a problem rooting a stock ROM that way but let's see what @mattdiehl83 reports.
ramjet73

OS X
ramjet73 said:
If flashing SuperSU from recovery doesn't result in a successful rooted system someone should let @Chainfire know. I've never had a problem rooting a stock ROM that way but let's see what @mattdiehl83 reports.
ramjet73
Click to expand...
Click to collapse
Not near pc. Only have OS X available now. Can anybody walk me through using OS X to flash?

mattdiehl83 said:
Not near pc. Only have OS X available now. Can anybody walk me through using OS X to flash?
Click to expand...
Click to collapse
The recovery? I don't know if there is an OS X version of Odin.
ramjet73

ramjet73 said:
The recovery? I don't know if there is an OS X version of Odin.
ramjet73
Click to expand...
Click to collapse
I am wondering what flashing tool to use with OS X. Odin is for windows. I know of heimdall but that requires ALOT to flash anything. Wondering if there is another odin like tool for OS X

You could try this: http://forum.xda-developers.com/showthread.php?t=2598203
Sent from my AT&T Galaxy Note 3 using Tapatalk®

done.
Hi guys sorry for the delay in update. I ended up using VM ware and it allowed to operate as windows on OS X. I installed TWRP, went into the file manager in TWRP and removed the superSU, i then flashed superSU and rebooted. Once back to the tablet i went and restored services to superSU and went into the play store. And finally the playstore gave me the option the update the superSU. And then the rest was all normal installation of superSU. Hope this thread helps anybody dealing with these issues.

Glad you got it working. :good:
This post in the CF-Autoroot thread might be helpful as well.
ramjet73

there is a easy way to fix it!
download supersu 2.02 and install ta da and it works
2.01 does not work with n5110 well if you flash cf auto root

hmmmm.....
Bordo_Bereli51 said:
there is a easy way to fix it!
download supersu 2.02 and install ta da and it works
2.01 does not work with n5110 well if you flash cf auto root
Click to expand...
Click to collapse
Tada..your a genius. Oh wait i believe i stated it didnt have that option it was disabled. Yes i decided scarcasm would be fitting due to the fact it says ALL OVER xda to please read before you post.

mattdiehl83 said:
Tada..your a genius. Oh wait i believe i stated it didnt have that option it was disabled. Yes i decided scarcasm would be fitting due to the fact it says ALL OVER xda to please read before you post.
Click to expand...
Click to collapse
I read all the post and didnt found something
YOU DONT NEED TO DELETE SUPERSU 2.0.1
Install 2.02 apk and go to supersu, then to settings and push to /system
This is the easiest way. the one you found: go to recovery delete that and this. download supersu 2.0.2 apk and install it not the recovery zip i mean the APK! i didnt say the flashable supersu zip.
oh wait, yes you are a intelligent boy, you know everything.

mattdiehl83 said:
I am wondering what flashing tool to use with OS X. Odin is for windows. I know of heimdall but that requires ALOT to flash anything. Wondering if there is another odin like tool for OS X
Click to expand...
Click to collapse
That's a bit of a dilemma.
Unfortunately Samsung does not support using fastboot and bootloader mode (they call it download mode) so that standard SDK tool Google provides for Windows, Linux and MAC OS X isn't applicable. Your best bet would be to find a Windows PC that you can use to flash the recovery with Odin since that is the most common and best documented method.
Edit: NVM, somehow I responded to an old post of yours.
ramjet73

Is it possible to root the OP3 without a custom recovery?

I don't really need a custom recovery (I don't know of any features custom recovery will give me I really need?) and for now I'm fine running stock roms (I always give stock a few weeks just as a baseline before I start custom roms) but I was wondering, how would one go about rooting the OP3 without installing a custom recovery?
Is it possible / easily doable? Or am I better off just to flash some custom recovery and ditch the stock one?
The reason I don't want to go away from stock just yet is I know oneplus is still updating the rom and custom recoveries, historically, have made OTA updates problematic.

Rooting will also mess up Ota too, but if u install a custom recovery, now that we have stock recovery it will be very easy to revert back for OTAs, there should be a way to root without a custom recovery but I am not sure how though, but with how oneplus makes it so easy to unlock bootloader and flash customers stuff there is really no need to stay stock

You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked

pileot said:
I don't really need a custom recovery (I don't know of any features custom recovery will give me I really need?) and for now I'm fine running stock roms (I always give stock a few weeks just as a baseline before I start custom roms) but I was wondering, how would one go about rooting the OP3 without installing a custom recovery?
Is it possible / easily doable? Or am I better off just to flash some custom recovery and ditch the stock one?
The reason I don't want to go away from stock just yet is I know oneplus is still updating the rom and custom recoveries, historically, have made OTA updates problematic.
Click to expand...
Click to collapse
As far as I know, you'd have to have TWRP to get root.
I don't think getting it rooted will mess up the OTA updates, other users sprovide flashable zips for the OTA anyway.. so you can still flash the zips manually with TWRP to keep you updated.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app

To get root yes, you would need TWRP to flash to certain partitions but to keep root no. Your phone will operate just fine with root and stock recovery. Check what the user a few posts above mine said about temporary flashing TWRP to achieve your short term goals

AcmE85 said:
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
Click to expand...
Click to collapse
So have you actually done this by temporary booting twrp and then using the systemless root and still have stock recovery? Also how do I root systemless? Really wanna know because wanna keep stock recovery and have root

TheSvensson said:
So have you actually done this by temporary booting twrp and then using the systemless root and still have stock recovery? Also how do I root systemless? Really wanna know because wanna keep stock recovery and have root
Click to expand...
Click to collapse
Yes, I have the stock recovery and it is rooted.
The recovery partition has nothing to do with all the other partitions except that it can read and write them.
This is the zip I flashed to get systemless root:
https://www.androidfilehost.com/?fid=24591000424939898
Some users reported that some Root-apps are not supported this way.
I am using Titanium Backup, Adaway, Trimmer and Root Explorer without issues.
Keep in mind that I did not get any OTA so far since running this setup, so I am not sure if official OTAs will or will not work.
All I did was manually flash OxygenOS 3.1.3 in TWRP (not flashed but booted) and reflash the root package afterwards.

AcmE85 said:
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
Click to expand...
Click to collapse
I have an unlocked bootloader and tried this on my PC:
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.709s]
booting...
OKAY [ 0.373s]
finished. total time: 1.092s
Nothing happens, bootloader start screen stays frozen. Until I hold down the power button. Might you know why?

AcmE85 said:
You can simply connect your OP3 to a PC and boot to TWRP without flashing it:
fastboot boot twrp.img
Then do a backup with twrp before rooting. I use the above method with systemless root
and also don't really need a custom recovery at this point. This might change once CM13 matures on the OP3...
OTAs might work this way in the future. If they don't, restore your system + boot (kernel) partition
and try the OTA again.
edit: implying your bootloader is already unlocked
Click to expand...
Click to collapse
i tried to boot into twrp recovery with above command, but the phone seems to be stuck in the bootloader and not responding. Any ideas?
edit: comment above describes exact same behaviour, sorry for double post

Sorry, don't know. Booting takes a couple seconds on my device though.
I am using this recovery img: http://www6.zippyshare.com/v/iK6tCE6D/file.html
Got it from XDA, but unfortunately don't know anymore who build it.

AcmE85 said:
Sorry, don't know. Booting takes a couple seconds on my device though.
I am using this recovery img: http://www6.zippyshare.com/v/iK6tCE6D/file.html
Got it from XDA, but unfortunately don't know anymore who build it.
Click to expand...
Click to collapse
Thanks, that twrp img worked for me. The one I was using didnt allow me to boot to it.

AcmE85 said:
Keep in mind that I did not get any OTA so far since running this setup, so I am not sure if official OTAs will or will not work.
Click to expand...
Click to collapse
Any chance you know if you get OTA by now?
I really like the Op3 and dont wont to change anything except i would like to habe root access. Your method seems to be the best way to achieve that.

hahamuntz said:
Any chance you know if you get OTA by now?
I really like the Op3 and dont wont to change anything except i would like to habe root access. Your method seems to be the best way to achieve that.
Click to expand...
Click to collapse
The updater will recognize root on your device and download the full 1.3 gb Rom file.
But after updating root will be gone, so you will have to reflash root after each ota.

AcmE85 said:
The updater will recognize root on your device and download the full 1.3 gb Rom file.
But after updating root will be gone, so you will have to reflash root after each ota.
Click to expand...
Click to collapse
Thanks for the quick answer
Just to make sure, if I root using this method nothing will change, except I have root access, my bootloader is unlocked and the updates will be big, but I can update the normal way, I will just lose the root access? Is that correct or am I missing something?

hahamuntz said:
Thanks for the quick answer
Just to make sure, if I root using this method nothing will change, except I have root access, my bootloader is unlocked and the updates will be big, but I can update the normal way, I will just lose the root access? Is that correct or am I missing something?
Click to expand...
Click to collapse
One more thing:
If you have TWRP, automatically installing the big OTA will remove it and go back to the stock recovery.
I always manually move the downloaded ota from android/data/com.oneplus.ota/files/.OnePlusOta
to my download folder, boot into TWRP and flash it + SuperSU on my own.

AcmE85 said:
One more thing:
If you have TWRP, automatically installing the big OTA will remove it and go back to the stock recovery.
I always manually move the downloaded ota from android/data/com.oneplus.ota/files/.OnePlusOta
to my download folder, boot into TWRP and flash it + SuperSU on my own.
Click to expand...
Click to collapse
So you have TWRP installed? I thought you won't get OTAs if you have a custom recovery? So i could just flash TWRP and root and still get OTAs?

hahamuntz said:
So you have TWRP installed? I thought you won't get OTAs if you have a custom recovery? So i could just flash TWRP and root and still get OTAs?
Click to expand...
Click to collapse
Yes, OTAs will come and because of Root you will get the full OTA regardless, which does not cause any issues with TWRP.
I tried my previous method and the regular OTA would fail because of root which changes the kernel or the system partition.
OnePlus reacted to this and introduced the full rom OTAs at some point.
So with root on my device this is how I do OTAs now:
- get the OTA notification for the full rom
- download but don't install
- move the downloaded zip from android/data/com.oneplus.ota/files/.OnePlusOta to my download folder
- manually boot into twrp and flash full rom zip + SuperSU

AcmE85 said:
Yes, OTAs will come and because of Root you will get the full OTA regardless which does not cause any issues with TWRP.
Click to expand...
Click to collapse
Okay, thanks so much for your help

recovery is not seandroid enforcing

I keep having this problem. I just tried both KINGROOT and CF-AUTO ROOT.
After doing this whole process through ODIN. I then try to flash the latest TWRP from their website : dl.twrp.me/jfltetmo/twrp-3.2.0-0-jfltetmo.img.tar.html
Then after that finishes, I try to boot into recovery and it gives me the message: recovery is not seandroid enforcing and just sits there.
I have a tmobile s4.
and I also checked if I am indeed rooted by using an app from the play store to check root and it shows Im rooted.
Any help would be great.

Root isn't needed to flash a twrp.
Tried flashing the latest stock rom and twrp without rooting the phone?

audit13 said:
Root isn't needed to flash a twrp.
Tried flashing the latest stock rom and twrp without rooting the phone?
Click to expand...
Click to collapse
Yup didn't work after trying it all the only thing that did work was SkipSoft Unified Android Toolkit and it was the easiest thing I ever used.

Krappa420 said:
Yup didn't work after trying it all the only thing that did work was SkipSoft Unified Android Toolkit and it was the easiest thing I ever used.
Click to expand...
Click to collapse
I have the exact problem, can you kindly explain in details how you went about it? I already downloaded SkipSoft.

Same issues here, buddy.
I tried to work on solving it out for approximately 8 hours and still no sign of success. Tried to reflash stock OS back on the phone via ODIN and it went successful. Tried CF-Auto-root file and it went through successful. But when it only came to the TWRP file, it went successful onto flashing on ODIN's side, but now something is interfering with the boot up process onto TWRP now. Hopefully there's a alternative towards this issue, since i've been wanting to reflash a Nougat OS onto the device.
Edit: I give credit to @Krappa420 for the mention of "SkipSoft Unified Android Toolkit" because i just installed the program on my laptop now and it went successful. But since i already had other materials pre-installed, some others with ODIN and ADB installed can just download this TWRP version here: https://dl.twrp.me/jfltexx/twrp-2.7.0.0-jfltexx.img.html
Edit #2: Seems that the TWRP version is too old to flash some of the newer OS's, such as nougat itself. Will find a way to update TWRP without breaking the boot up process, like the past attempts
Edit #3: After fiddling with TWRP versions 2.7.0.0 and up, i managed to get it capped up to 3.1.1 any future versions will most likely not work, so you're capped at 3.1.1 Here's the link for flashing it with ODIN: https://dl.twrp.me/jfltexx/twrp-3.1.1-0-jfltexx.img.tar.html

So you twrp 3.1.1 and it will work right
I having the same issue
Thank you

so do i need to install cf-auto root first or the twrp 3.11
what are the steps to install
Thank you for helping a disabled veteran

timj3371 said:
so do i need to install cf-auto root first or the twrp 3.11
what are the steps to install
Thank you for helping a disabled veteran
Click to expand...
Click to collapse
It wouldn't really matter what order you're using.
You can use CF-Auto-Root to root it for you while you have stock recovery still, and after you can flash to TWRP and use a custom recovery afterwards
Or you can flash TWRP first and flash a SuperSU zip file afterwards and it'll give you root while maintaining to have TWRP installed.
But to sum it up, it wouldn't matter what order you choose. Help yourself

Trwp
What version of twrp I need to use
Thank you

timj3371 said:
What version of twrp I need to use
Thank you
Click to expand...
Click to collapse
TWRP version 3.1.1

Thank you for the help I have lineage installed. Wow so fast. How ever when trying to root it I get a error says binary occupied. If I uninstall I get no root available. How do I install root ? Thank you so much
A disabled veteran

timj3371 said:
Thank you for the help I have lineage installed. Wow so fast. How ever when trying to root it I get a error says binary occupied. If I uninstall I get no root available. How do I install root ? Thank you so much
A disabled veteran
Click to expand...
Click to collapse
Before anything, try to install the SuperSU app over on the play store, if it says you're not rooted, you may have to restart the whole process within TWRP and reflash the SuperSU Zip file.

Thank you
Says the binary is occupied in su
Where do I find su zip
Should I use the chain fire auto zip
Thanks

timj3371 said:
Says the binary is occupied in su
Where do I find su zip
Should I use the chain fire auto zip
Thanks
Click to expand...
Click to collapse
Try this one: https://download.chainfire.eu/696/supersu/
If it keeps on persisting, I'll have to find another way

I tried that file and it just sits in booting. I left it be then reinstated the ROM. Still no root its OK tight not to have root
Thank you

timj3371 said:
I tried that file and it just sits in booting. I left it be then reinstated the ROM. Still no root its OK tight not to have root
Thank you
Click to expand...
Click to collapse
Yeah try to re-flash the ROM again but this time flash magisk through TWRP since SuperSU is being trippy on your S4

Thank you for the help
Dummy me I found out from reading other forums you have to go in to tools and enable root after going in to recovery and flash the root file in the extra section.
Every thing works
Thank you so much
Disabled veteran