Related
#1-"com.tmobile.pr.adapt (10001) has been granted superuser permissions for an interactive shell" pops up on my screen every 30 seconds on the bottom of my screen in a grey box.
#2- i also noticed that i can accept and recieve calls but i can not hear, nor can the other person hear me. if i use hangouts video call, skype, etc it works fine.
#3-i also tried to get rom manager to make a recovery and it says it needs to get CWD recovery to install a new software, the first thing we need to do is install a up to date version, we will begin that process now... etc.. then it says to get started you must first sset up a custom recovery, it gives two options a samsung galaxy s3 on metro pcs or a samsung previal 2 on boost mobile, or device not listed, when i click that it says "SM-G920T does not have an officially supported CWDR yet. Have you installed a CWD based recovery manually?" so im not sure what to do from there, or if i even need that. i have been a iphone user since day one went to android after reading up a lot on it, although rooting is quite different than jailbreaking it seems, i am incredibly excited to get started if i can get past these little problems and get started and figure everything out. ANY advice, or anwsers to these problems would be Greatly appreciated! thanks!
Also i went to dev options in settings and noticed the "OEM unlocking- allow the bootloader to be unlocker" was turned off, i dont know if this is necessary to root if i did something wrong by not turning it on or what, or if it may fix any problems above if i turn it on now. thanks!
I have a samsung Galaxy S6 (SM_G920T) . i Rooted and did not trip Knox, Although i did just remember that my fingerprint sensor is not working either.
Thank you guys so much this si a incredible forum i have spent hours and hours reading and researching before making this post i appreciate it so much!
#1 Freeze that ****. Use some root tool to freeze that T-mobile apk, seems u gave it root permissions at some point. I believe there are a lot of apps that you will want to do the same.
#2 ? No idea. Stock rom/kernel?
#3 What is this I don't even. Don't do that. Go to TWRP's official web, get your zeroflte (SM-GT920T) twrp and flash it via ODIN, or else get the recovery.img and use flashify. All that assuming you want a custom recovery.
You will need to unlock the bootloader if you are on 5.1.1. I believe locked will prevent changes or wiping anything on the OS partitions, even recovery (can someone confirm?)
I believe jailbraking and rooting should be pretty much similar, if not the same, as both target to grant the user root access to do whatever he pleases on the OS.
Welcome to android btw.
How did you root? Sounds like you used the modified sboot which causes no sounds in calls and nonfunctional fingerprint scanner. If so, flash back to stock and use a different rooting method. The rest, pretty much what the above poster stated
Root
I rooted using the version that I found the only one that works it seemed like, went to Odin put my phone In download mode and then put the boot loader download in BL and the. Put a something unikernel.sbin I believe, whatever the guide said also then it was done. I thought you couldn't use the twrp or custom recovery etc on tmobile one yet but I just read a thing about xtrestolite odex pure v2 which says it's for 5.1.1 and my model of phone but in the guide it says to root using CF auto root and a link there to it but the link doesn't have my phone on the list that the guide that clearly is my phone says to use I don't know if I'm missing something but I want to use it I understand most of it but I don't know if I need to unropt first and re root then use Odin and flash twrp that's supported on my phone then use that to recover the rom. Etc. The kernel that says is used in the guide is the same one I downloaded so do I need to remove it all then let it do that or?
Sorry if this didn't make sense I'm halfway there between confused and understood I have spent the last 10 hours reading and trying to figure this out though lol. Thanks guys!
Also
Sorry for adding more but also how do I flash back to stock? Search for the download to the stock image of my phone? Also I could only find one way of rooting everything else said it wasn't working yet or am I missing a big portion of something here?
Just flash the 5.1.1 firmware to return to stock. To root, flash unikernel with Odin. The other method you used was to not trip knox, but as you experienced has side effects. I had to Odin back to 5.1.1 myself. Can't have those issues
thanks!
so how do i flash back to 5.1.1? find the ling to completely stock 5.1.1 and flash through odin in the same spot and same way i flashed the kernel to root? also.. i rooted with " s6_UniKernel_v2-0003-ODIN.tar" is that not the one you were talking about?
CjetOKC said:
so how do i flash back to 5.1.1? find the ling to completely stock 5.1.1 and flash through odin in the same spot and same way i flashed the kernel to root? also.. i rooted with " s6_UniKernel_v2-0003-ODIN.tar" is that not the one you were talking about?
Click to expand...
Click to collapse
Yes, flashing to 5.1.1 works exactly like that. You need to get the version for your model (very important on this one) and then simply place that file in the AP field of ODIN while the device is in recovery mode. It is normal for ODIN to freeze for 2 minutes while verifying. Make sure to use a MD5 checker tool on the firmware before flashing.
Rooting has historically required more technical savvy and balls than jailbreaking, but PingPong made rooting the S6 brain-dead simple. CF-Auto root is still pretty painless, but you must make sure you have the right zip for your device.
Anyhoo, the quickest & easiest way to restore phone calls & fingerprint scan is to use Odin to get back to bone stock.
Next, use PingPong to root. After rooting, "com.tmobile.pr.adapt" will ask for root access. That is T-Mobile's "phone home" app and sends info about your device (probably including root status). Deny it root access and make sure you check "Remember my choice", and it won't bother you again. You will not lose any functionality by denying it root, so terminate that crap.
Don't bother with rom manager. CWM is archaic. If you want a custom recovery, use TWRP. You can install TWRP either using Odin or TWRP Manager app (it's free).
Good luck and have fun with your S6
CjetOKC said:
Sorry for adding more but also how do I flash back to stock? Search for the download to the stock image of my phone? Also I could only find one way of rooting everything else said it wasn't working yet or am I missing a big portion of something here?
Click to expand...
Click to collapse
Are you still rooted? If so, and if you are experiencing the call audio issue, go flash AOU's kernel. He has made a kernel for the tmo s6. that should eliminate your call audio issue. The finger print scanner is the only issue with flashing his kernel. Also, I rooted with the modded sboot, his TWRP and kernel, and I didn't trip knox
http://forum.xda-developers.com/tmo...recovery-twrp2-8-6-0-g925t-5-1-1-of6-t3143002
Hi all,
I have been hammering away at this one, and putting it on the back-burner, but now, it is really getting to me. Samsung Galaxy Tab Pro 10.1 SM-T520
It has been rooted with ODIN, and shows no problem, (things seem much easier now, as I have re-jigged lots of my old phones using so many more tools, I am not an expert, but can read and search without too much problems) I was very careful to choose the correct file, CF-Auto-Root-picassowifi-picassowifixx-smt520.zip, I have rechecked this step several times, as most of the instructions I found ODIN device ID:COM box should become yellow, when on newer versions it is blue I think, I wondered if I was going mad,
Root Checker Root access granted, all fine. I have Root access. n.
Installed CWM ,latest recovery for a Pro 10.1 wifi, recovery 6.0.3.1 Titanium backup-ed, all ready to go and Reboot and flash a new ROM.. No joy. .. Installed TWRP , same.
When it re-starts it ,shows the galaxy logo, flashes off, then back on, and then fails. Android dead with a red warning , standard recovery KOT49H.T520XXUANAE, all I can do is the usual options:apply update. The only thing I haven't tried is to just wipe all the data. I have a backup of my apps with Titanium Backup on the SD card,I am not that bothered really about much other data if its a pain. I just want control of my device and to try a new ,cleaner ROM(SMT520_GraveD_V3.0)
This has been bothering me for ages, I have read so many posts so am now getting really frustrated I have bought triangle away app. today although I think I sorted that issue early on anyway , but just in case...
Super SU seemed to have vanished so that is back installed
I think I searched and found the Mount/system issue and looked into an issue that lead me to the .system folder, but it is hidden, so I could not find the file it related to. I dont have the specifics to hand as I checked it out at work. I wondered if it is because I have ES file manager, not ASTRO as it said in some of the posts I found.but sure this is a red herring.
I have tried everything..I have a Mac at home and PC at work, I have tried ADB and can see &restart the device etc... so I am connected, first I got the error that it didn't recognise the sideload command. Read up on ADB , looked at the help etc. sideload isn't there as a command, very confusing. But I think I got there one I figured out paths, as of course they are different on a Mac, and possibly more so as I have 2 drives in it, which often confuses me ..grr.
I can of course get into the bootloader, with ON+VOL -, it tells me so far the system is : Official and Knox Warranty Void: 1 which I think is fine, but a chap at work suspected this, but after lots of threads I gather this is normal..
Sorry if long, just thought I should be as clear as possible. I have not really come across such an awkward issue as this , my HTC One was a breeze:crying:
*edit* Just worked out through trial and error, that to use the sideboot command I had to select send via ADB and now with the path /Desktop/SMT520_GraveD_V3.0.zip I was able to send the file but with the following messgae : E:footer is wrong and E:signature verification failed, twice.. So some progress
Thanks !
Just to say after being up waay too long on this, I discovered there is a newer firmware T520XXUANI1_T520BTUANI1_BTU which I may aswell upgrade to first, but of course I cannot do this OTA now As it recognises the device is 'tampered with' *sigh* so gun and games with Odin for Mac tonight, or JODIN3 , just to get the firmware upgrade(which seems to be a jungle of fake download links). before a Rom without bloatware..
I am also not completely clear why, as from another thread about KNOX, as I am basically running stock , without custom recovery.. According to this thread , but I am getting a bit confused now
http://forum.xda-developers.com/gal...neral/knox-warranty-void1-otas-t2996067/page2
Click to expand...
Click to collapse
however this is another story from the ROM install. Apologies
Well. No replies, but I did eventually solve this. Hopefully this can help someone. I am a tinkerer, but I really nearly gave up on this..But this was a cheap second hand tablet ( my first) and I want to see what it can do before I test drive one on my mother who is having nightmares with every Windows laptop I give her!
Once I got to a PC , I had access to Odin3, although it is not available online (apparently to Mac) I could not get it to work due to Java issues (JOdin3 online - brilliant idea but no joy for me so far)
I had the Rom I wanted ( GraveDigger- SMT520_GraveD_V3.0.zip ), the firmware update (T520XXUAOD2_T520BTUAOB1_BTU.zip(i think)) and the unlock file (CF-Auto-Root-picassowifi-picassowifixx-smt520.zip) , non of which I could install in any way , due to being locked out of using a custom Rom bootloader!
At this point I factory reset and cleared the cache( as that is the only options in the basic bootloader!) I also has ADB on the PC so attempted to install the files this way (after messing about using some software to produce the .tar and .md5 files needed for Odin. I tried everything to get this into proper 'bootloader mode' all from scrach again, including trying the adb oem unlockbootloader command, which I would never get to work as I could not get there!
With Odin, I was also again able to flash the firmware update, eventually, and of course had to unlock again. I was curious if I could now use the OTA update, and could not. At some point, in repeating this process( as I think it hung up several times and needed a hard reboot) I had at this point fully wiped the device as I know that is another reason to have glitches and an unstable ROM later.
I think I then tried to check and although T520XXUAOD2 seems to still be the firmware, at some point I managed to get online ( I think some superuser app which I have had to try several may have notified me that KNOX was reset:laugh:When I go to About>Software update it said I had the latest update! Good news!
At this point I had installed both CWM and TWRP again , and thought I would try TWRP.I had tried CWM and the same problem, like a double flash of the Samsung Logo , so I know it had reset !!
THIS TIME I used TWRP ( I thought of trying CWM touch, but its either paid, or I would have to find and ABD the file over I guess) , I managed to re-apply the Root file, Root checker confirmed this , as it had throughout this ordeal!, although apart from ACCESS GRANTED I dont really know what the rest means..Anyway although picassowifi , was still in Device name on TWRP I chose an earlier recovery version to install.- twp-2.7.0.0-picassowifi.img. When I re-booted, I was able to get the TWRP recover image, and install the ROM, I cannot remember if I re-rooted as I was so elated.
I had a few , freezing moments, reinstalling most of my apps through Titanium Backup, I think I just tried to reinstall everything which of was unnecessary, after a hard reset, all seems fine. I checked and the TWRP recovery seems to have stuck. I am not entirely sure how to check about the firmware , but for now I feel this is progress.
Good Luck if anyone found this any use.
Just to add, when you search this ( and probably many other models) you seem to get so many sites, offering exactly the same unlock information, in exactly the same way, many of the downloads seem to take you to many weird and wonderful places. So I tended to look here for downloads if possible. But I had to join SamMobile (which seems a useful site for the firmware upgrade) and trawl all over and assume similarities between other Samsung devices to fully check I was not being an idiot. But this was very odd and I could not find any posts or other workarounds that I did not try. But this new ROM feels lovely and smooth so far, and I now want to look into this tablet further
So, today I upgraded to 6.0 and had a hell of a time (took me 7 hours) and the problem was that when I installed su from twrp it'd soft brick my phone, anyway, that's not the problem, the problem is everything is saving to /storage/emulated and I can't access it without root. I noticed this when I was on OGInsta and I wanted to download a picture, it gave me an error code about how it couldn't find the directory, so I went to my file manager, everything was fine but I accidentally hit up instead of home and it brought me to an empty page. I started messing with the settings of my file manager assuming something went wrong with it, new version etc, and I found it had a root option. I clicked it and gave it root access and went back and I could see the files where I was previously. To make sure I tried to save something on kik, didn't work. I tried accessing my storage from the rar app and it wouldn't. I don't know what's going on or how it even got this way.
How did you install 6.0, what version of su did you install, and how did you fix the soft brick?
Sounds like you have very little idea what your doing and running a ton of random stuff. Probably best to do a system restore, take a step back learn what your doing and do it again properly... but if you can recount the steps you have done it may be fixable.
I like to think I have decent knowledge on what I am doing, I've been rooting phone's and made xposed apps (for myself) since kitkat. I've never had so much trouble with something. And to answer your questions, I figured using nexus root toolkit would he fine, as it always has worked before but I couldn't get it to root my phone. It would soft Brick it for an unknown reason, I left it on for about an hour at one point to make sure it was bootlooping. So then I used adb, flashed boot.img and then recovery. Went into recover and flashed SU 2.52 beta. (this is also how I solved the soft Brick the nexus toolkit was giving me)
scryan said:
How did you install 6.0, what version of su did you install, and how did you fix the soft brick?
Sounds like you have very little idea what your doing and running a ton of random stuff. Probably best to do a system restore, take a step back learn what your doing and do it again properly... but if you can recount the steps you have done it may be fixable.
Click to expand...
Click to collapse
Also, to clearly, I have 2 storage paths. One is "sdcard/" and the other is "storage/emulated/0" I'm not sure if the "storage" folder is new in 6.0, I know 4.+ and 5.+ used "sdcard/". Too see "storage/emulated/0" I need to grant root access to the file manager. And any app the does not have root, cannot access that directory.
YoureVexing said:
I like to think I have decent knowledge on what I am doing, I've been rooting phone's and made xposed apps (for myself) since kitkat. I've never had so much trouble with something. And to answer your questions, I figured using nexus root toolkit would he fine, as it always has worked before but I couldn't get it to root my phone. It would soft Brick it for an unknown reason, I left it on for about an hour at one point to make sure it was bootlooping. So then I used adb, flashed boot.img and then recovery. Went into recover and flashed SU 2.52 beta. (this is also how I solved the soft Brick the nexus toolkit was giving me)
Click to expand...
Click to collapse
you might have knowledge in making apps, but you are missing lots of knowledge when modding your phone. you are going to have to use an app like root explorer, and find where your storage was placed, then move it to the right location. or you can reflash the factory image. ive always just moved my storage back when its happened to me. anyways, flash the factory image the right way, not through a toolkit. then flash any custom kernel(if flashing marshmallow), and supersu.
YoureVexing said:
I like to think I have decent knowledge on what I am doing, I've been rooting phone's and made xposed apps (for myself) since kitkat.
Click to expand...
Click to collapse
Why are comments like this always made by people who take 7 hours to flash a factory image, and make statements like
YoureVexing said:
So then I used adb, flashed boot.img and then recovery.
Click to expand...
Click to collapse
ADB cannot flash factory images.
I didn't need your resume... Just answers to the questions I asked....
Do as simms said and flash factory image with fastboot to fix whatever you did, then a kernel and the lastest supersu.
The emulated storage folder has been there at least since kit kat. My S4 and Moto X, neither of which saw LP both had it.
scryan said:
Why are comments like this always made by people who take 7 hours to flash a factory image, and make statements like
ADB cannot flash factory images.
I didn't need your resume... Just answers to the questions I asked....
Do as simms said and flash factory image with fastboot to fix whatever you did, then a kernel and the lastest supersu.
The emulated storage folder has been there at least since kit kat. My S4 and Moto X, neither of which saw LP both had it.
Click to expand...
Click to collapse
It took me 7 hours because I could figure out what was wrong with it and why twrp kept soft bricking my device. And I'm not worried about emulated. I know that has been there. I'm saying there is 2 folders, /sdcard and /storage. Every app is trying to use the path "/storage/emulated/0/*insert app folder here" and it cannot do that without root. I'm confused as too why all the apps are trying to do that for a default location instead of /sdcard. I've already tried to reflash everything. I even looked up like 5 tutorials to make sure I was doing it right and I was.
Can't really help you with your current situation (other than to advise you to flash a factory image and start over), but if it confirms your sanity the exact same thing happened to me using the rootkit to root my Nexus 6. I should've known better than to use rootkit, but I'm not really used to fastboot having been on Samsung devices and using Odin for everything. I corrected it by flashing a factory image, flashing the modified boot image, flashing TWRP, and then SuperSU. But the whole process was quite a fiasco from what I'm used to and for what I expected from a Nexus phone.
YoureVexing said:
It took me 7 hours because I could figure out what was wrong with it and why twrp kept soft bricking my device. And I'm not worried about emulated. I know that has been there. I'm saying there is 2 folders, /sdcard and /storage. Every app is trying to use the path "/storage/emulated/0/*insert app folder here" and it cannot do that without root. I'm confused as too why all the apps are trying to do that for a default location instead of /sdcard. I've already tried to reflash everything. I even looked up like 5 tutorials to make sure I was doing it right and I was.
Click to expand...
Click to collapse
/sdcard is a simlink, its the same folder.
internetpilot said:
Can't really help you with your current situation (other than to advise you to flash a factory image and start over), but if it confirms your sanity the exact same thing happened to me using the rootkit to root my Nexus 6. I should've known better than to use rootkit, but I'm not really used to fastboot having been on Samsung devices and using Odin for everything. I corrected it by flashing a factory image, flashing the modified boot image, flashing TWRP, and then SuperSU. But the whole process was quite a fiasco from what I'm used to and for what I expected from a Nexus phone.
Click to expand...
Click to collapse
The rootkit wasn't working for me, it's been a charm for my nexus 5 and from 4.+ and nexus 6 on 5.+, on 6.0 it wasn't working so I tried to flash it on fastboot and I still got the same thing. I'll try it once more I suppose, thank you.
Please excuse me if this is a simple process, but I cannot seem to locate a thread on how to flash to -44, as I am slowly in the process of trying to root my Turbo.
Currently living off of FoxFi USB tethering, but finally would like to obtain root access since it is available as I miss having wifi tethering!
I'd like to add, that the process of rooting this phone is a bit more advanced than what I have done over the years. I'm used to plugging the phone in the PC, installing a software on the PC, then "one click" root and reboot.
Any insight or recommendations is greatly appreciated! Tethering is my main reason for root, but I'd still like the versatility of having root access.
Thanks XDA!
coconutt said:
Please excuse me if this is a simple process, but I cannot seem to locate a thread on how to flash to -44, as I am slowly in the process of trying to root my Turbo.
Currently living off of FoxFi USB tethering, but finally would like to obtain root access since it is available as I miss having wifi tethering!
I'd like to add, that the process of rooting this phone is a bit more advanced than what I have done over the years. I'm used to plugging the phone in the PC, installing a software on the PC, then "one click" root and reboot.
Any insight or recommendations is greatly appreciated! Tethering is my main reason for root, but I'd still like the versatility of having root access.
Thanks XDA!
Click to expand...
Click to collapse
THIS METHOD WILL VOID YOUR WARRANTY. But if you're on xda, chances are you knew that. It's also irreversible.
If you're not unlocked and not rooted, take the OTA that is available to get you to -44. 44 is the most recent version available, so there is no risk of updating too far.
Once you're on 44, download the Kingroot apk and install it. http://www.kingroot.net/
Then download this version of Sunshine and install it. http://forum.xda-developers.com/showpost.php?p=64027688&postcount=4064
Once both are installed, open Kingroot and follow the instructions to try and get temporary root. It doesn't always work, and sometimes you have to try multiple times. If it fails, uninstall Kingroot, reboot the phone and try again. Wiping cache in the recovery menu sometimes helps too.
After Kingroot says it is successful, run Sunshine and follow the prompts. Sunshine costs $25, so if you're not cool with that, don't try this method. If Sunshine succeeds, your phone will reboot and instead of the Motorola M that you usually see at boot, you'll see a bootloader unlocked warning message. If Sunshine fails, uninstall Kingroot, reboot, reinstall and try again.
Once your bootloader is unlocked, you need to get a custom recovery installed (TWRP), which you can get here http://forum.xda-developers.com/mot...recovery-twrp-2-8-7-0-touch-recovery-t3180308. The easiest way to flash that in my opinion is with Fastboot. The easiest way to install Fastboot is by installing this: http://forum.xda-developers.com/showthread.php?t=231779. You'll also need to make sure you have the appropriate drivers so that your PC will recognize your phone. This will ensure that: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Put the TWRP .img file that you downloaded into the folder that you installed Minimal ADB and Fastboot to, boot your phone in bootloader mode, plug it in to the computer, start Minimal ADB and Fastboot, and type the following command:
fastboot flash recovery <name of TWRP .img file>
Once you have that, the sky is the limit. If you only want to add permanent root to your phone, download this: http://forum.xda-developers.com/showthread.php?t=1538053, put it somewhere on your phone, boot into recovery mode (which will now be TWRP instead of the stock recovery), select install, navigate to the .zip file and flash it. That's it. If you want to try cyanogenmod or any other custom rom, see their respective xda threads for details.
Oh, and as for enabling tethering for free, which is only necessary if you have an unlimited data plan (if not, it's free already, just use Verizon's app to do it), find any root browser, search for a file called build.prop, open it with the browser's text editor and add this line to the end of it:
net.tethering.noprovisioning=true
Remember to save when you're done.
---------- Post added 7th December 2015 at 12:00 AM ---------- Previous post was 6th December 2015 at 11:45 PM ----------
If you need more help, this guy might explain better than I did: http://forum.xda-developers.com/droid-turbo/general/videos-tutorials-root-restoring-droid-t3076456
http://forum.xda-developers.com/showthread.php?t=2317790
Link for minimal adb and fastboot, I think this is the right one?
TheSt33v said:
THIS METHOD WILL VOID YOUR WARRANTY. But if you're on xda, chances are you knew that. It's also irreversible.
If you're not unlocked and not rooted, take the OTA that is available to get you to -44. 44 is the most recent version available, so there is no risk of updating too far.
Once you're on 44, download the Kingroot apk and install it.
Oh, and as for enabling tethering for free, which is only necessary if you have an unlimited data plan (if not, it's free already, just use Verizon's app to do it), find any root browser, search for a file called build.prop, open it with the browser's text editor and add this line to the end of it:
net.tethering.noprovisioning=true
Remember to save when you're done.
Click to expand...
Click to collapse
Sorry for the late reply as I'm having the free time to fidget with the phone.
To my understanding about taking the OTA that is available to me is not the Marshmallow update? I have a screenshot of the OTA when it pops up each night, but not sure if I'm allowed to img code it on here. But it displays "New version: 23.21.44.en.US"... I'd just like for you to confirm that this is the -44 update before I advance, thanks a bunch!
Also, I tried the buildprop edit on my current -39 version and it won't let me save the file. I take it this can be done after rooting though.
coconutt said:
Sorry for the late reply as I'm having the free time to fidget with the phone.
To my understanding about taking the OTA that is available to me is not the Marshmallow update? I have a screenshot of the OTA when it pops up each night, but not sure if I'm allowed to img code it on here. But it displays "New version: 23.21.44.en.US"... I'd just like for you to confirm that this is the -44 update before I advance, thanks a bunch!
Also, I tried the buildprop edit on my current -39 version and it won't let me save the file. I take it this can be done after rooting though.
Click to expand...
Click to collapse
Yep. That's it. The marshmallow update isn't out yet, so it cannot be the marshmallow update. Build.prop is located on the system partition, which is write-protected on a stock Turbo. Once you unlock with Sunshine (just rooting with Kingroot isn't good enough), you will be able to edit it. Also, Sunshine no longer needs Kingroot. Simply download the latest version here http://theroot.ninja/download.html and use it to unlock once you're on -44.
TheSt33v said:
Yep. That's it. The marshmallow update isn't out yet, so it cannot be the marshmallow update. Build.prop is located on the system partition, which is write-protected on a stock Turbo. Once you unlock with Sunshine (just rooting with Kingroot isn't good enough), you will be able to edit it. Also, Sunshine no longer needs Kingroot. Simply download the latest version here therootdotninja/download and use it to unlock once you're on -44.
Click to expand...
Click to collapse
Well that was easy! Bootloader unlocked!! Thanks.
Now on to the rooting process. Currently getting my Moto drivers updated on the PC, and I've also downloaded the TWRP file onto the PC as well. As for Fastboot, the link you've provided takes me to a 2005 thread! I'm sure I can find a link to Fastboot to download, but I wanna make sure I get the one I need, if that makes any sense? (Don't mind me being paranoid)
TheSt33v said:
Put the TWRP .img file that you downloaded into the folder that you installed Minimal ADB and Fastboot to, boot your phone in bootloader mode, plug it in to the computer, start Minimal ADB and Fastboot, and type the following command:
fastboot flash recovery <name of TWRP .img file>
Click to expand...
Click to collapse
For an update, I got everything I needed downloaded. I am stuck at this point though, as I can't get passed this point when I input the above command!
EDIT:
I skipped the recovery flash, and went ahead with just the build prop edit for tethering after installing King Root. Rebooted it and still have root, and tethering works. Thanks a bunch!!
coconutt said:
For an update, I got everything I needed downloaded. I am stuck at this point though, as I can't get passed this point when I input the above command!
EDIT:
I skipped the recovery flash, and went ahead with just the build prop edit for tethering after installing King Root. Rebooted it and still have root, and tethering works. Thanks a bunch!!
Click to expand...
Click to collapse
If you want twrp flashify works well.
Hi
Please help me
My device is already bootloader unlocked.
My Oxygen is 4.0.3 and stock recovery.
How to root without PC.
I don't have computer.
Please help me...
Sorry for my English.
Thank you
4.0.3 is pretty old. So I would suggest first updating to 4.1.6 first: https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
From there, you can try one of the apps to install custom recovery TWRP: official TWRP app, TWRP Manager, or Flashify (all available on the Play store). I always use fastboot to flash TWRP, so can't vouch for either of those apps working. One thing to note, is that without a PC, if you run into issues while rooting, you have less options to troubleshoot and recovery, and might get yourself in a jam.
If you succeed in installing TWRP, backup your stock ROM in TWRP. Then download SuperSU or Magisk (whichever root you prefer) right to the phone, then boot TWRP and flash it.
Chicken and egg problem. Bootloader unlocked does not necessarily mean root so unless you have root, the apps mentioned are not going​ to work. Unless you have root or TWRP installed I am afraid that you'll need a computer at least once.
https://www.amazon.com/HP-Stream-11-y020nr-Celeron-Personal/dp/B01JLCKPAC
Highly recommended. No excuse no to have at least this computer. You can even buy it for 160 dollars from a high rated amazon seller and get amazon prime. If not from here try to grab it from somewhere that sells it in your country. Using android works much better with PC. you dont have to use any experimental software to load experimental software. Its just not a good idea. Get this guy, it seems very good too, nice specs for a casual laptop computer then just use the method everyone does. It also seems extremely portable at 11 inches.
Unfortunately, there is no known way at this time to flash a custom recovery without root or access to a computer. Your best bet would be to load the adb/fastboot files and either borrow a friend's computer or use a library computer. You should be able to run access the programs directly from a flash drive without administrative privileges/installing to system.
Edit: Nevermind, forgot your needed drivers. I guess you will have to either borrow a friend's or buy a cheap computer.
Everybody Thanks
I am Myanmar.
Root is very important because Myanmar Unicode font and zawgyi font (non-standard Unicode).
Android default font is Myanmar Unicode but
100 percent of Myanmar internet users use Zawgyi for communication.
Thank you
Zawgyi and Unicode problems is here
https :// docs . google . com/document/d/1W6_Upw_fDMeiwKr1G4gQVT_bTen-CTa6DwfJixPB1rw/mobilebasic
Get a friend to help out? Surely someone you know has a pc to let you use for a couple minutes
dreinulldrei said:
Chicken and egg problem. Bootloader unlocked does not necessarily mean root so unless you have root, the apps mentioned are not going​ to work.
Click to expand...
Click to collapse
That is a good point. As I mentioned, I don't use apps like Flashify or TWRP Manager to install TWRP (but know folks like these apps) so I didn't think of that nuance. You don't need root to install TWRP by fastboot; but you will need root to do it through an app.
I think I've seen some folks (other devices) mess around with installing TWRP using terminal emulator and another Android phone attached by OTG. But not that straightforward (would need to buy an OTG cable), not sure if it will work; and probably just easier to find a friend or family member to borrow their PC for a half hour.
I'd just really get to a PC; boot TWRP, make a backup of boot, recovery and modem (IMEI) data, then flash TWRP and that's it.
Typically does not take much longer than 5 minutes...