Related
I have a rooted, bootloader unlocked Pixel from Google Play. I am currently on 7.1 (NDE63V) November 5th security patch. I have stock recovery and would like to keep it that way if possible.
Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader? I used adb and boot-to-root for my current root method if it matters.
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
spook2022 said:
I have a rooted, bootloader unlocked Pixel from Google Play. I am currently on 7.1 (NDE63V) November 5th security patch. I have stock recovery and would like to keep it that way if possible.
Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader? I used adb and boot-to-root for my current root method if it matters.
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
Click to expand...
Click to collapse
You will lose root, but you can re-root easily enough. Bootloader doesn't relock on its own. Plus, you have the Google Store version, so it's easy to unlock BL anyway. To me, the cleanest and easiest method is to use the flash-all method, with the -w switch removed. Download the 7.1.1 image from the Google developers site and go at it. You can search for 'flash-all google pixel' here or on the web in general to get directions. It's easy as pie.
quangtran1 said:
You will lose root, but you can re-root easily enough. Bootloader doesn't relock on its own. Plus, you have the Google Store version, so it's easy to unlock BL anyway. To me, the cleanest and easiest method is to use the flash-all method, with the -w switch removed. Download the 7.1.1 image from the Google developers site and go at it. You can search for 'flash-all google pixel' here or on the web in general to get directions. It's easy as pie.
Click to expand...
Click to collapse
I've got an unlocked Verizon Pixel running the non Verizon stock ROM (I know the bootloader won't relock itself with the non-Verizon ROM, right?). what if you are using a computer that can't use the ./flash-all.sh script? My only 2 computers are a Chromebook (1GB RAM) and a Raspberry Pi 3 (again, 1GB RAM). The flash-all script always gives an error saying it can't allocate enough memory, and with my old Nexus 6P, before I started using Custom ROMs, I'd just extract the image zip and manually flash the .img files inside it. With the Pixel however, there are a lot of img files (aboot.img, apdp.img, etc) and I'm not sure if I should try flashing these or not. I've read a couple less than reliable guides out there that basically said to just flash the same .img files as the Nexus 6P used, but I feel that those other ones are probably their for a reason and might need to be flashed too.
Also, should I flash both _a and _b partitions when updating, or just whichever is active? Seems that there is an _a and _b for almost every single partition on it.
lightmastertech said:
I've got an unlocked Verizon Pixel running the non Verizon stock ROM (I know the bootloader won't relock itself with the non-Verizon ROM, right?). what if you are using a computer that can't use the ./flash-all.sh script? My only 2 computers are a Chromebook (1GB RAM) and a Raspberry Pi 3 (again, 1GB RAM). The flash-all script always gives an error saying it can't allocate enough memory, and with my old Nexus 6P, before I started using Custom ROMs, I'd just extract the image zip and manually flash the .img files inside it. With the Pixel however, there are a lot of img files (aboot.img, apdp.img, etc) and I'm not sure if I should try flashing these or not. I've read a couple less than reliable guides out there that basically said to just flash the same .img files as the Nexus 6P used, but I feel that those other ones are probably their for a reason and might need to be flashed too.
Also, should I flash both _a and _b partitions when updating, or just whichever is active? Seems that there is an _a and _b for almost every single partition on it.
Click to expand...
Click to collapse
I have a ChromeBook but I've never used it to fastboot my phones. Sorry but I'll refrain from giving instructions on something with which I'm not familiar. I can say that the bootloader won't relock by itself. And the boot.img image should be all you need. Those points are universal. Also, you can just flash the 7.1.1 OTA, which is only 260mb.
quangtran1 said:
I have a ChromeBook but I've never used it to fastboot my phones. Sorry but I'll refrain from giving instructions on something with which I'm not familiar. I can say that the bootloader won't relock by itself. And the boot.img image should be all you need. Those points are universal. Also, you can just flash the 7.1.1 OTA, which is only 260mb.
Click to expand...
Click to collapse
If it rooted, and has modified system, doesn't the OTA update method fail?
And I actually use the Raspberry Pi for fastboot. Easier than trying to get my Chromebook's chroot to talk to talk to my phone's bootloader.
Hi
Whats about Flashfire? Can i download the Factory Image, deselect Boot and Recovery in Flashfire and flash it?
After this, can i flash the the SuperSU.zip with TWRP?
spook2022 said:
<snip>
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
Click to expand...
Click to collapse
Have you any idea how many threads there are regarding this? How many duplicate posts and the same question about 2 dozen times all in separate threads? And now we have another? Even if you can't search XDA for some unknown reason, here you go.
https://www.google.com/search?q=root+on+unlocked+pixel+7.1.1&ie=utf-8&oe=utf-8
Search terms from your OP ... root. on unlocked pixel 7.1.1
Can we please put an end to this question already?
bobby janow said:
Have you any idea how many threads there are regarding this? How many duplicate posts and the same question about 2 dozen times all in separate threads? And now we have another? Even if you can't search XDA for some unknown reason, here you go.
Search terms from your OP ... root. on unlocked pixel 7.1.1
Can we please put an end to this question already?
Click to expand...
Click to collapse
I went back and read my post again just to make sure I wasn't crazy, and sure enough I couldn't find where I asked how to root 7.1.1...
I did however ask "Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader?" So, posting a Google search on how to root 7.1.1 isn't exactly the help I was after. Regardless of your disgruntled, condescending reply to the whole matter, I did manage to achieve the end result I was originally after.
spook2022 said:
I went back and read my post again just to make sure I wasn't crazy, and sure enough I couldn't find where I asked how to root 7.1.1...
I did however ask "Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader?" So, posting a Google search on how to root 7.1.1 isn't exactly the help I was after. Regardless of your disgruntled, condescending reply to the whole matter, I did manage to achieve the end result I was originally after.
Click to expand...
Click to collapse
As far as I know you can not update without losing root.. You can however update without losing data and reroot just like you did the first time.
@spook2022 It's just so frustrating to see the same question over and over. It wasn't that condescending, but yes, it was disgruntled. I just like to search for these things myself because I learn a lot along the way. Might take me an hour or so for the answer but then I learned an hours worth of stuff. I do agree though that there should be a sticky like the Heisenberg thread in the n5x forum that gives step by step for everything. One thing I will say that perhaps a few people don't know is that the Pixel and the XL are basically the same regarding root, unlocking and updating. So if you don't find the answers here you might want to head over to that forum. There seems to be a dearth of information here.
Someone suggested that the forums be combined with separate sections for things specific to each device like battery life and display as well as Verizon vs Google brand differences. I originally thought not but I'm changing my mind. Nonetheless, take the frustration from whence it came. I'm sorry I insulted you, that was not my intention. If you found a link to your solution perhaps you can post it for others. There is bound to be a similar question within a day. (oh oh there I go again..)
edit: This is what I was talking about regarding the Pixel vs the XL forums. Anything by Chainfire regarding root is a must read if you are rooted and even if you are not as I am. http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156
Download the 7.1.1 NMF260 image from Google.
Extract the zip file into the adb folder on the PC.
Edit the flash-all.bat file to remove the -w switch so user data won't be deleted. You'll find this -w switch easily enough.
Put your Pixel into fastboot mode, using either power+volume down or via adb command.
Plug phone to PC if not already done so. Execute the flash-all batch file.
When that's done, you have 7.1.1 on your phone, along with new radio and new kernel. (actually, I'm not sure if Google even put out a new kernel.)
Then you can go back to re-root with whatever method you used previously.
Konfuzion said:
Download the 7.1.1 NMF260 image from Google.
<snip>
Click to expand...
Click to collapse
Why not the OTA coming from 7.1? Stock recovery according to the OP. Why go thru all the hassle unless you want a dirty flash? I know you say reroot after the install. I haven't been rooted in a few months now but I always used to unroot first for some reason before flashing a new image whether it be full image as you describe or an OTA. I'm sure it's not needed at this point, I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Konfuzion said:
Download the 7.1.1 NMF260 image from Google.
Extract the zip file into the adb folder on the PC.
Edit the flash-all.bat file to remove the -w switch so user data won't be deleted. You'll find this -w switch easily enough.
Put your Pixel into fastboot mode, using either power+volume down or via adb command.
Plug phone to PC if not already done so. Execute the flash-all batch file.
When that's done, you have 7.1.1 on your phone, along with new radio and new kernel. (actually, I'm not sure if Google even put out a new kernel.)
Then you can go back to re-root with whatever method you used previously.
Click to expand...
Click to collapse
Thank you so much.
bobby janow said:
...I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Click to expand...
Click to collapse
That right there is why I always unlock my bootloader's and hack Verizon's phones to have unlocked bootloaders. Always great to have the assurance that you can easily fix it if something ever breaks.
Sorry if that's a little off topic.
bobby janow said:
Why not the OTA coming from 7.1? Stock recovery according to the OP. Why go thru all the hassle unless you want a dirty flash? I know you say reroot after the install. I haven't been rooted in a few months now but I always used to unroot first for some reason before flashing a new image whether it be full image as you describe or an OTA. I'm sure it's not needed at this point, I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Click to expand...
Click to collapse
He's on 7.1.0...63V..he can't apply the latest ota to 63V..he would have to apply each ota in order of their release.
kyle4269 said:
He's on 7.1.0...63V..he can't apply the latest ota to 63V..he would have to apply each ota in order of their release.
Click to expand...
Click to collapse
I don't believe that to be correct. I think the 7.1.1 is cumulative. I'll double check though and edit later.
edit: You can go directly to the latest without incremental OTA flashes. Just sideload the OTA from recovery. Easy, peasy.
---------- Post added at 03:50 PM ---------- Previous post was at 03:22 PM ----------
lightmastertech said:
That right there is why I always unlock my bootloader's and hack Verizon's phones to have unlocked bootloaders. Always great to have the assurance that you can easily fix it if something ever breaks.
Sorry if that's a little off topic.
Click to expand...
Click to collapse
I always, always unlocked first thing I did. I even unlocked the unlockable S4 before the VZW firmware update. But lately I've been running locked. I have a banking app that will not run without passing SafetyNet. I know there are a couple of kernels that will bypass that check but I believe they will close that too eventually. The only thing I miss at this point is what you describe above. But the Pixel even from vzw, which I now have with the O update and therefore totally locked for now, is not full of bloat and runs rather well. So although I do root around these threads (no pun intended) it's merely for entertainment now and general knowledge.
bobby janow said:
I don't believe that to be correct. I think the 7.1.1 is cumulative. I'll double check though and edit later.
edit: You can go directly to the latest without incremental OTA flashes. Just sideload the OTA from recovery. Easy, peasy.
.
Click to expand...
Click to collapse
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
bobby janow said:
I always, always unlocked first thing I did. I even unlocked the unlockable S4 before the VZW firmware update. But lately I've been running locked. I have a banking app that will not run without passing SafetyNet. I know there are a couple of kernels that will bypass that check but I believe they will close that too eventually. The only thing I miss at this point is what you describe above. But the Pixel even from vzw, which I now have with the O update and therefore totally locked for now, is not full of bloat and runs rather well. So although I do root around these threads (no pun intended) it's merely for entertainment now and general knowledge.
Click to expand...
Click to collapse
Luckily I'm with USAA and they are too slow with adopting new technology, just got chip debit cards 2 months ago, and they'd till don't have Android Pay, lol. If they did start using SafetyNet, I'd use the kernel patch in a heartbeat. It'll be a long time before Google fixes that since there's still a lot of devices that can't use verified boot, and Google doesn't want to become the new Apple, abandoning old device just to suit them.
Wife got the Verizon version of the Pixel as an early Xmas present from my parents, and I wouldn't let the Verizon sales person activate it for fear of getting 7.1.1 before I could unlock bootloader. Wouldn't let wife turn it on for a couple hours till I had the bootloader unlocked and had flashed Google's version of Android to keep Verizon from screwing with it. Viper4Android and all the awesome rooted featured are too good to give up. She'll be really happy when Xposed or custom ROMs start coming out for it cuz even the little features are great, like holding power button with screen off to turn on flashlight. (She's been stuck with locked phones for a while while I've had my Nexus 6P and is glad to finally get a rootable phone).
kyle4269 said:
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
Click to expand...
Click to collapse
Yep, that's about it. Personally I'd reboot right after the OTA flash then go back to bl and do the root process. Probably not needed though.
Sent from my Pixel using XDA-Developers mobile app
kyle4269 said:
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
Click to expand...
Click to collapse
How is that better or different than flashing the full image by using fastboot to flash bootloader and radio (if updated), then using
Code:
fastboot update <image>.zip
and leave off the -w to keep it from wiping.
Also, correct me if I'm wrong, but doesn't OTA updates fail if you've modified the system partition, like installing Viper4Android or other mods? I know that flashing the whole system image works no matter what which is why I use that method.
I was messing with a bunch of stuff like supersu me, trying to replace kingroot with supersu in terminal emulator, but I don't think that had anything to do with it. I re-ran kingroot today, and now, even if I power it off all the way, or reboot, it still holds root! Permanent root is a big step, but I always want more. lol. I'm hoping there will be a way to replace it with supersu soon, and get flashfire working. On 5.1.1 BOH4 Good luck everyone!
Edit: I have no idea how I was able to keep a permanent root, but alas, I had to go messing with $#!+, and end result was having to flash stock firmware and not be able to get permanent root again. I'm not sure if things I was messing with played a strange part, or if somehow kingroot magically went through that one time, but it sucks to have lost it. I can replace kingroot with supersu using a Replace_Kinguser_with_SuperSU-v2.4 zip file, flashing it in terminal emulator, then using a power menu for root app to soft reboot before kingroot fail errors start to pop up. Sadly, if hard reboot or power off and on are done, root with supersu are wiped. If you do this, don't update the su binary or you'll hang at at&t logo in a softbrick.
whats wrong with twrp?
thelous said:
whats wrong with twrp?
Click to expand...
Click to collapse
Not sure what you mean. TWRP doesn't work on most samsung devices 5.0 & up. Also, Kingroot is limited, so as of now, flashfire doesn't work. What I'm hoping is, the supersu me app will be updated to replace the current kingroot with supersu, which should fix the flashfire problem. If flashfire works, I'm pretty sure custom roms can be flashed after that. Busybox is installable.
thelous said:
whats wrong with twrp?
Click to expand...
Click to collapse
the bootloader is locked
xjimmy said:
Not sure what you mean. TWRP doesn't work on most samsung devices 5.0 & up. Also, Kingroot is limited, so as of now, flashfire doesn't work. What I'm hoping is, the supersu me app will be updated to replace the current kingroot with supersu, which should fix the flashfire problem. If flashfire works, I'm pretty sure custom roms can be flashed after that. Busybox is installable.
Click to expand...
Click to collapse
if i remember right theres some files thst you need to delete to prevent "unroot" in boot...... similar to stock recovery flashing back on some devices after installing twrp or cwm
My rooting experience with kingroot has been temp root, with reboots causing soft brick, an update to kingroot making reboots possible without bricking, but causing unroot, and the latest update where it retains root after reboot. So whatever they did, it's working now. It is limited, however, as I doubt cwm or twrp is flashable, and flashfire doesn't work with kingroot.
What I don't want is for people to doubt me. It's easy to download the latest kingroot and try it. The lp fix boot.tar is still available, but you'll see, you won't need it. And the stock firmware .tar is available so you really have nothing to lose. What I'm hoping is, more people do it so we can move forward. I'd like to see a new version of supersu me, and flash fire working. Get to a point where we see some custom roms.
Which version of KingRoot did you use? 5.0.0 or 5.0.1?
Tried KingRoot v5.0.1 app and root doesnt stick after reboot. It actually took much longer to root then it takes with 5.0.0 version.
There is also two versions of KingRoot from different KingRoot websites; a 13.7mb and 18.5mb version. Large version, has ads and nagging notifications.
KGB7 said:
Tried KingRoot v5.0.1 app and root doesnt stick after reboot. It actually took much longer to root then it takes with 5.0.0 version.
There is also two versions of KingRoot from different KingRoot websites; a 13.7mb and 18.5mb version. Large version, has ads and nagging notifications.
Click to expand...
Click to collapse
If you're talking about the actual apk app for android, there is no version 5.0 or 5.0.1, the latest version is 4.9.2
You need to make sure you're going to Kingroot's actual website, otherwise you're going to end up on weird websites claiming to have the newest version and all that, end up with "ads and nagging notifications." lol. I bet if you opened up the kingroot app you downloaded, hit the options button (3 dots) in the top right corner and selected "about app," you'd see a different version of kingroot than 5.0, 5.0.1, or 4.9.2
If you're referring to the pc method, then I'm not sure what version that is. It pops up in a foreign language, and you might want to look up how to follow the steps accordingly. I'd be willing to bet that the pc version works just as well, though. Hope you figure out where you went wrong. Good luck.
xjimmy said:
If you're talking about the actual apk app for android, there is no version 5.0 or 5.0.1, the latest version is 4.9.2
You need to make sure you're going to Kingroot's actual website, otherwise you're going to end up on weird websites claiming to have the newest version and all that, end up with "ads and nagging notifications." lol. I bet if you opened up the kingroot app you downloaded, hit the options button (3 dots) in the top right corner and selected "about app," you'd see a different version of kingroot than 5.0, 5.0.1, or 4.9.2
If you're referring to the pc method, then I'm not sure what version that is. It pops up in a foreign language, and you might want to look up how to follow the steps accordingly. I'd be willing to bet that the pc version works just as well, though. Hope you figure out where you went wrong. Good luck.
Click to expand...
Click to collapse
The app i downloaded is version 5.0.1.392 165 from Kingroot.net
Su Version 3.64.
KGB7 said:
The app i downloaded is version 5.0.1.392 165 from Kingroot.net
Su Version 3.64.
Click to expand...
Click to collapse
Well I'll be damned. I just downloaded it and you're right. I just hate eating crow. I apologize. I will say that the reason I was insistent on it being the latest update is because that's what I did, was have my version kingroot (4.9.2 143) check for updates and it says it's up to date. I downloaded it from the official site, tried it, and had success the same day I posted this thread. My kernel version says v4.8.0 67, and my Su version says v3.61
I would be interested, if you were willing, to hear your results after trying version 4.9.2. Also, did you try it on the pc to see the difference? If none of this works, is there a developer that I could somehow give a system dump to, maybe to see how I have root still, including after reboots? I'm not making this up, and would be willing to show you on skype if you pm me. I'm afraid to unroot it now and try it again. lol
xjimmy said:
Well I'll be damned. I just downloaded it and you're right. I just hate eating crow. I apologize. I will say that the reason I was insistent on it being the latest update is because that's what I did, was have my version kingroot (4.9.2 143) check for updates and it says it's up to date. I downloaded it from the official site, tried it, and had success the same day I posted this thread. My kernel version says v4.8.0 67, and my Su version says v3.61
I would be interested, if you were willing, to hear your results after trying version 4.9.2. Also, did you try it on the pc to see the difference? If none of this works, is there a developer that I could somehow give a system dump to, maybe to see how I have root still, including after reboots? I'm not making this up, and would be willing to show you on skype if you pm me. I'm afraid to unroot it now and try it again. lol
Click to expand...
Click to collapse
I tried the PC app twice but, it was annoying having to read the instructions on their site because they didnt translate it. The root did stick once with PC app. Not sure what made it unstick. I think its because i cleared cache in the recovery mode but, i didnt test that theory, i switched to apk.
The manual update option in the apk doesn't work properly, each time it tells me that current version is up to date. So the auto update is also useless.
I'll test the 4.92 version of KingRoot apk on the tablet and get back to you with the results. At the end of the day, i have no need for permanent root after I debloated the tablet.
KingRoot has its own thread here on the forums. You can ask them directly if you have any questions.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
edit:
Here are all the builds of KingRoot you can download for you to play with.
http://forum.xda-developers.com/devdb/project/?id=9793#downloads
update;
Ran kingroot apk 4.9.2 and the root doesnt stick. Either you got lucky or you did something with supersu.
.
KGB7 said:
I tried the PC app twice but, it was annoying having to read the instructions on their site because they didnt translate it. The root did stick once with PC app. Not sure what made it unstick. I think its because i cleared cache in the recovery mode but, i didnt test that theory, i switched to apk.
The manual update option in the apk doesn't work properly, each time it tells me that current version is up to date. So the auto update is also useless.
I'll test the 4.92 version of KingRoot apk on the tablet and get back to you with the results. At the end of the day, i have no need for permanent root after I debloated the tablet.
KingRoot has its own thread here on the forums. You can ask them directly if you have any questions.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
edit:
Here are all the builds of KingRoot you can download for you to play with.
http://forum.xda-developers.com/devdb/project/?id=9793#downloads
update;
Ran kingroot apk 4.9.2 and the root doesnt stick. Either you got lucky or you did something with supersu.
.
Click to expand...
Click to collapse
I replied to this comment a while ago, so I thought. lol. You ever reply to something, hit submit, and come back later to find it not posted? grrr. Thank you for at least trying again. It wouldn't seem likely that by simply clearing the cache, root would get wiped. I almost want to try it myself. What I wrote was that I would, if possible, love to do a system dump, or whatever they call it, so a developer could take a look at how and why I have permanent root. That would be to say that a developer would be interested at all. Supersu just froze in the process, and I read it's because kingroot now patched it so it wouldn't remove their root. Would be cool to get supersu on it and maybe get a custom rom or two.
Get bootloader unlocked
toolhas4degrees said:
the bootloader is locked
Click to expand...
Click to collapse
How would you go about getting the bootloader unlocked for the samsung galaxy tab 4 sm-t337a in order to flash a twrp file?
nd4400 said:
How would you go about getting the bootloader unlocked for the samsung galaxy tab 4 sm-t337a in order to flash a twrp file?
Click to expand...
Click to collapse
Ask at&t nicely.
According to what I've seen on a SM-G900A thread, the NewKingrootV4.81_C136_B245_xda_release_2016_02_29_105243.apk was the last revision that didn't block supersume from working properly.
bbc581 said:
According to what I've seen on a SM-G900A thread, the NewKingrootV4.81_C136_B245_xda_release_2016_02_29_105243.apk was the last revision that didn't block supersume from working properly.
Click to expand...
Click to collapse
I read that too, but you know what, it still doesn't work. I've found a zip file called Replace_Kinguser_with_SuperSU-v2.4 that works. What you do is install a power menu for root users first, then root with kingroot. Next, you install the replace kinguser zip using terminal emulator, which there are instructions online and on youtube on how to do it. Once you've replaced kingroot with supersu, quickly use the power menu app to do a soft reboot, as to avoid kingroot failure errors. DO NOT update the su binary. Only problem is, if you do regular reboot, or power off the tab, then power it back on, root is lost again. I have no idea how I got permanent root with kingroot, but I've lost it now while messing with things. I wish I would've tried to replace it with supersu this way when I had it just to see if it woul've still retained permanent root as well. Now what?!?! lol
I'll test the 4.92 version of KingRoot apk on the tablet and get back to you with the results. At the end of the day, i have no need for permanent root after I debloated the tablet.
KingRoot has its own thread here on the forums. You can ask them directly if you have any questions.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
edit:
Here are all the builds of KingRoot you can download for you to play with.
http://forum.xda-developers.com/devdb/project/?id=9793#downloads
update;
Ran kingroot apk 4.9.2 and the root doesnt stick. Either you got lucky or you did something with supersu.
.[/QUOTE]
Hey man, old stuff, I know, but I thought this was interesting:
http://androidforums.com/threads/tutorial-how-to-root-the-sm-t337a-lollipop-with-kingroot.1100261/:
I'm not sure if he's saying to keep rebooting, and re-rooting until root sticks permanently, or to leave kingroot running without rebooting for a long time, and permanent root will sink in eventually. I think he means the second one, too leave it running without rebooting. On a sidenote, I have been able to use a replace kingroot with superuser 2.74 via terminal emulator with success, even after rooting with latest version kingroot. Updating supersu binary results in softbrick on reboot though. If you don't update user binary, and you reboot, you just lose root, is all. And sometimes the zip doesn't work, and it takes reboot, re-root with kingroot, then re-run terminal emulator. Flashfire doesn't like kingroot, but it opens up with supersu after this method. Not sure if it can actually flash zips though. Just thought I'd share my latest findings.
xjimmy said:
I'll test the 4.92 version of KingRoot apk on the tablet and get back to you with the results. At the end of the day, i have no need for permanent root after I debloated the tablet.
Thanks for the info. An interesting discovery! After going back and reading that guy's article again, I noticed that he posted a link to download kingroot. I was curious what version he used. It was 4.8.1 . When I tried downloading 4.8.1 from the xda link you gave me, it kept popping up with a network error. This time I downloaded 4.8.1 somewhere else and tried it. After root, I kept closing kingroot, swiping it clear in task manager, and re-opening it until it gave me the notice that it deployed itself as a system app. I then rebooted (not soft reboot) and it partially kept a permanent root this time. If I went into root checker, it would tell me no root, but other apps were popping up the grant permission tab. I'm sure I'll get root to stick permanently again, then I'll try to install supersu over it again, see if I can't get that as a permanent root. It's not the end of the world to me either, but it just drove me nuts not knowing how the hell I got it. Also, it's just fun to mess with stuff. lol. So in the chain of updates, 4.8.1 is right before 4.9.2, so I'm guessing that I probably got permanent root from 4.8.1 and then updated it, or possibly that I ran 4.8.1, updated, and maybe optimizing or running root again with 4.9.2 finished the job. Anyway, thanks for writing back!
Click to expand...
Click to collapse
I've made this thread to teach T337A owners how to root their device with SuperSU. Please note that this is a system-less root, meaning it's temporary, but can be re-applied. Rooting only takes about 5-7 minutes and brings numerous tweaks and advantages to your device. Just remember that every time you reboot or shut the device down, you will need to repeat the rooting process. This tutorial was designed for Lollipop 5.1.1, but it should work on KitKat as well.
Before beginning, you will need to download the following file, unzip it on your pc, then transfer it to your device's internal storage/external sd card.
T337AUCU2BOH4 (Lollipop) firmware can be found here
Root Files can be found here
Lets start!
1) Install both the APK files in the file on your device, If prompted, allow installation from unknown sources.
2) Make sure your device is connected to WiFi, then open Kingroot.
3) Once Kingroot is "Done searching for the best root strategy", click the "Try Now" button and wait about 3 minutes for KingRoot to give you a "Root Successfully" message.
4) This is where it gets kinda tricky, immediately after receiving the root success message, go into SuperSU-me, and grant root permissions when prompted.
5) Click on the big blue button in the middle of the frame and wait about 1 minute for the process to complete. DO NOT UPDATE THE SUPERSU BINARY, IT WILL CAUSE YOUR DEVICE TO BOOTLOOP.
6) IMMEDIATELY after the process has completed, go into Settings and make sure KingRoot or Purify is not installed! This is an important step because Kingroot and Kingroot adware tends to install itself in the system partition which can cause problems and frustration.
7 - Recommended) Download a root file explorer (such as ES File Explorer) and search "King" under /data and /system to ensure that the KingRoot app and its bloatware has been wiped from the system. This is to ensure that Kingroot still works properly after a reboot.
8) Enjoy root access!
If this tutorial helped you please be sure to hit the :good: button. If you had any issues or troubles during this process please feel free to let me know down below.
Cheers!
@KingOfTheNet
will flashfire work? bc it wont with kingroot
also, could itit.d be enabled and run these off of a script for example on startup so we don't have to do this after each reboot/shutdown
but i believe you would have to capture kingroots data somehow in the process of rooting
toolhas4degrees said:
@KingOfTheNet
will flashfire work? bc it wont with kingroot
also, could itit.d be enabled and run these off of a script for example on startup so we don't have to do this after each reboot/shutdown
but i believe you would have to capture kingroots data somehow in the process of rooting
Click to expand...
Click to collapse
FlashFire does work on SuperSU, I've tested that for myself. It does not work with KingRoot.
For the second question, I'm not sure. I haven't looked through that file myself and I might look through it later but right now, I would just avoid rebooting the tablet if you wanna keep root without repeating the process over and over again. It's what I do, repeating the process over and over again can get very tedious and annoying.
Cheers!
I assume you're talking about 5.1.1? It won't work with kingroot versions higher than 4.8. Also, flashfire will load, but if you try to flash a zip you're screwed. You can actually use replace kingroot with supersu zip in terminal emulator on any version kingroot. Same deal with su binary, don't update it. Wish I could figure out how I had permanent for with kingroot. I had to go messing with things and lost it. Nothing really special about this method, unless there's a dev out there that can do something with it.
xjimmy said:
I assume you're talking about 5.1.1? It won't work with kingroot versions higher than 4.8. Also, flashfire will load, but if you try to flash a zip you're screwed. You can actually use replace kingroot with supersu zip in terminal emulator on any version kingroot. Same deal with su binary, don't update it. Wish I could figure out how I had permanent for with kingroot. I had to go messing with things and lost it. Nothing really special about this method, unless there's a dev out there that can do something with it.
Click to expand...
Click to collapse
Sorry for the late response. Yes, somethings I forgot to mention in the original post:
1)Updating the SU Binary will put your device in a bootloop
2)Flashing anything with flashfire (based on what I've seen) results in a soft brick
3) I know you can replace kingroot with SuperSU in terminal, but when you reboot, you're unrooted again.
4) I'm trying to figure out how I could altar the boot.img so we can get permanent SuperSU on this thing the same way Chainfire did it with the US and Qualcomm Samsung Galaxy S7's.
Cheers!
Hi, @KingOfTheNet, thanks for helping out with this device, i rooted my device on KK nk2 build and now updated to 5.1.1, thanks to you! now i would like to root 5.1.1 (am aware it is a temp. root)
i have superSu Pro, do i need Super Sume for this to work?
KingOfTheNet said:
Sorry for the late response. Yes, somethings I forgot to mention in the original post:
1)Updating the SU Binary will put your device in a bootloop
2)Flashing anything with flashfire (based on what I've seen) results in a soft brick
3) I know you can replace kingroot with SuperSU in terminal, but when you reboot, you're unrooted again.
4) I'm trying to figure out how I could altar the boot.img so we can get permanent SuperSU on this thing the same way Chainfire did it with the US and Qualcomm Samsung Galaxy S7's.
Cheers!
Click to expand...
Click to collapse
Somehow I had it permanently rooted with kingroot a while back. I had the 4.9.6 apk on my tab at the time, is all I know. I could've updated from an earlier version, and maybe that was the cause. I've tried so many different versions of kingroot with no luck, but one peculiar occurrence; if I open kingroot, get into the settings and uninstall kingroot without saving a backup of root, then delete all the files in the tablet's main directory, and reinstall kingroot version 4.8.0, it somehow retains a partial permanent root. At least on my T337A running 5.1.1 BOH4 it will, as long as I get a fresh install of 4.8.0, let it root, then hit the optimize button right after. Then wait until it finally tells me that kingroot has been deployed as a system app. After that, when I try to open any root apps, the screen will darken as it does when the root permission tab pops up, but it never pops up. The app just freezes. I can kill it in the task manager screen to just go back to using my tablet. After I restart the tab, sometimes it'll tell me an app has been granted superuser permissions. If I open up terminal emulator, type in the 'su' command and hit enter, the screen will turn dark again like it's going to ask me to allow or deny superuser permission, but it just freezes like that again. I've tried all kinds of stuff with 4.8.0, but I still can't get it to stick. If you don't hit the optimize button in kingroot right after rooting, and just wait for kingroot to install as a system app, the allow/deny prompt comes up without freezing, but the partial permanent root glitch doesn't remain. ugh, tired of messing with it though. lol
Edit: I may be wrong. It might need to be rooted with 4.8.0, optimized, then rebooted right away for the partial root. I'll try to do it again and let you know what I find.
bklyndiaz said:
Hi, @KingOfTheNet, thanks for helping out with this device, i rooted my device on KK nk2 build and now updated to 5.1.1, thanks to you! now i would like to root 5.1.1 (am aware it is a temp. root)
i have superSu Pro, do i need Super Sume for this to work?
Click to expand...
Click to collapse
I'm happy to help out! You'd need king root installed, root the tab with king root, then use SuperSU me to replace the kingroot binaries with the SuperSU ones. It is an automatic process and should only take about 30 seconds or less. Pro version of SUPERSUme is not required, free version should work just fine.
Cheers!
xjimmy said:
Somehow I had it permanently rooted with kingroot a while back. I had the 4.9.6 apk on my tab at the time, is all I know. I could've updated from an earlier version, and maybe that was the cause. I've tried so many different versions of kingroot with no luck, but one peculiar occurrence; if I open kingroot, get into the settings and uninstall kingroot without saving a backup of root, then delete all the files in the tablet's main directory, and reinstall kingroot version 4.8.0, it somehow retains a partial permanent root. At least on my T337A running 5.1.1 BOH4 it will, as long as I get a fresh install of 4.8.0, let it root, then hit the optimize button right after. Then wait until it finally tells me that kingroot has been deployed as a system app. After that, when I try to open any root apps, the screen will darken as it does when the root permission tab pops up, but it never pops up. The app just freezes. I can kill it in the task manager screen to just go back to using my tablet. After I restart the tab, sometimes it'll tell me an app has been granted superuser permissions. If I open up terminal emulator, type in the 'su' command and hit enter, the screen will turn dark again like it's going to ask me to allow or deny superuser permission, but it just freezes like that again. I've tried all kinds of stuff with 4.8.0, but I still can't get it to stick. If you don't hit the optimize button in kingroot right after rooting, and just wait for kingroot to install as a system app, the allow/deny prompt comes up without freezing, but the partial permanent root glitch doesn't remain. ugh, tired of messing with it though. lol
Edit: I may be wrong. It might need to be rooted with 4.8.0, optimized, then rebooted right away for the partial root. I'll try to do it again and let you know what I find.
Click to expand...
Click to collapse
Kingroot does allow your device to retain permanent root after a certain time. However, Kingroot is not as powerful as SuperSU, is very limited in terms of what It can do, and has it's own 'bloatware' titled Purify. I'd honestly stick with SuperSU because it's (probably) the most powerful and efficient way to root your phone. I'd also suggest avoiding having to reboot the tablet at all with temp root because you would have to take 5 minutes to install it again, which was a pain in the butt for me.
As for the kingroot app freezing, that's usually the result of a bad download or a bad root. Plus kingroot is very limited in terms of what you can do on your kingrooted device. SUPERSU is the equivalent of an IOS jailbreak. SUPERSU gives you full control of your device, with no bloatware and limits, unlike kingroot.
Kingroot does sometimes delete the su binaries upon rebooting, which is another reason I don't like it all that much.
Another theory I thought of is that it's not Kingroot that's deleting the binaries, it's actually something that's set to happen when the device boots up. Either the actual Android os or the bootloader searches for and deletes the su binaries to prevent root.
I don't know for sure, I've kinda slowed down work on this device mainly because of a project I've been working on with the Samsung Galaxy S7 AT&T (SM-G930A). I'll look into these things when I get the chance.
Cheers!
I understand the limitations of Kingroot, and certainly supersu by all means is better. In the case of flashfire with supersu in this scenario, it's merely the difference of being able to open and run it just enough to work improperly and brick your device vs. Kingroot not being able to open it at all. I posted in a thread long before this one, how to replace kingroot with supersu, only I use the zip file in terminal emulator. Pretty sure I went over flashfire as well. The terminal emulator method works with new versions of kingroot, unlike supersu me. Are you suggesting that the T337A running 5.1.1 BOH4 can achieve permanent root via kingroot after "a certain amount of time"? Because I'm the only one I've seen on xda who's ever posted that they had permanent root from kingroot, but I didn't know how I did it. After I messed with things, i softbricked and had to flash back to stock, which, no offense, the stock file was available way before you posted it. Anyway, it's not the kingroot app freezing per se, i was talking about after rebooting, and without re-rooting, when trying to use rooted apps, they actually start to engage in the kingroot request superuser permissions pop-up. So, no, it's not a bad download, etc. I believe an older version of kingroot somehow permanently rooted my tab, perhaps with the help of something I was messing with at the time, perhaps not. I've intentionally rebooted my tab an unimaginable amount of times, testing to see if I possibly regained permanent root to no avail, so I know how that works. And it's not about having a hard time deciding on kingroot or supersu for a temproot, it's the interest in permanent root, the possibility off something like safestrap, and/or flashing custom roms, etc. When people say temproot is better or safer, i say boo. How many custom roms include a root toggle in the settings? Anyway I wish I could've gotten hold of a developer while I had permanent root. Maybe I could've done a system dump, or even try replacing the permanent kingroot with supers and drying out that could've stuck. You say you slowed down on this device, do you mean you were pursuing permanent root for it? Are you a developer? I have the AT&T S7 Edge (G935A). What's your project on the 930? Is it something for rooted S7's? I still have my edge running the engboot with the echoRom. Anyway, thanks for your reply.
---------- Post added at 01:01 AM ---------- Previous post was at 12:51 AM ----------
https://forum.xda-developers.com/tab-4/help/t337a-temp-root-bootlp-fix-tar-official-t3473737
*https://forum.xda-developers.com/tab-4/general/permanent-root-t337a-5-1-1-kingroot-t3518334
A couple of threads I started a long time ago that may be of interest to you.
xjimmy said:
I understand the limitations of Kingroot, and certainly supersu by all means is better. In the case of flashfire with supersu in this scenario, it's merely the difference of being able to open and run it just enough to work improperly and brick your device vs. Kingroot not being able to open it at all. I posted in a thread long before this one, how to replace kingroot with supersu, only I use the zip file in terminal emulator. Pretty sure I went over flashfire as well. The terminal emulator method works with new versions of kingroot, unlike supersu me. Are you suggesting that the T337A running 5.1.1 BOH4 can achieve permanent root via kingroot after "a certain amount of time"? Because I'm the only one I've seen on xda who's ever posted that they had permanent root from kingroot, but I didn't know how I did it. After I messed with things, i softbricked and had to flash back to stock, which, no offense, the stock file was available way before you posted it. Anyway, it's not the kingroot app freezing per se, i was talking about after rebooting, and without re-rooting, when trying to use rooted apps, they actually start to engage in the kingroot request superuser permissions pop-up. So, no, it's not a bad download, etc. I believe an older version of kingroot somehow permanently rooted my tab, perhaps with the help of something I was messing with at the time, perhaps not. I've intentionally rebooted my tab an unimaginable amount of times, testing to see if I possibly regained permanent root to no avail, so I know how that works. And it's not about having a hard time deciding on kingroot or supersu for a temproot, it's the interest in permanent root, the possibility off something like safestrap, and/or flashing custom roms, etc. When people say temproot is better or safer, i say boo. How many custom roms include a root toggle in the settings? Anyway I wish I could've gotten hold of a developer while I had permanent root. Maybe I could've done a system dump, or even try replacing the permanent kingroot with supers and drying out that could've stuck. You say you slowed down on this device, do you mean you were pursuing permanent root for it? Are you a developer? I have the AT&T S7 Edge (G935A). What's your project on the 930? Is it something for rooted S7's? I still have my edge running the engboot with the echoRom. Anyway, thanks for your reply.
---------- Post added at 01:01 AM ---------- Previous post was at 12:51 AM ----------
https://forum.xda-developers.com/tab-4/help/t337a-temp-root-bootlp-fix-tar-official-t3473737
*https://forum.xda-developers.com/tab-4/general/permanent-root-t337a-5-1-1-kingroot-t3518334
A couple of threads I started a long time ago that may be of interest to you.
Click to expand...
Click to collapse
No offence taken on the firmware post, I was simply trying to spread the fact that the firmware for the device does exist but is very hard to find and is often posted on shady websites for money, unless you're looking in the right places. It only took me 5 minutes on Google to find one of those sites.
You asked if I was saying that the Tab 4 BOH4 firmware allows you to retain permanent root after some time, and yes, that's exactly what I was saying. I rooted my tablet with Kingroot 4.8.0 a while back and after about 4 - 5 reboots (I counted how many times I rebooted it, but the numbers could vary), It retained root. All I do today is avoid rebooting the tablet at all costs. I prefer SuperSU because, like we've said, there are almost no limitations of what you can do in terms of being rooted. I'm trying to find out how I can make root permanent on the tab with SuperSU by using the eng-boot method used to root all Qualcomm variants of the Galaxy S7, but that may take a while. Since my S7 has the eng-boot root method, I can reboot it all I want and it stays rooted with SuperSU. But at this point, It's just an Idea. I mainly need to find out whether or not the bootloader or the os is wiping the binaries on boot. Some older and newer versions of kingroot can retain root after reboot, but I have yet to find a version of the app that can do so.
Actually, some versions of Cyanogenmod and other custom roms had root pre-installed (not like SuperSU, but close enough), and like CM specifically, there was a section in the settings app for this pre-baked root. Even if I still used CM today, I still would've flashed SuperSU. But on a small number of devices, temp root really is better. However, most of those devices that would be on that list have very little to no development on them. Thus, they are not yet (and may never be) supported for permanent root.
I am partially on the road to becoming a developer, but I don't know how far that's gonna go (my prediction is not that far at all). I was doing research on how I could make an eng-boot for the Tab 4, but I became interested in my Galaxy S7 (AT&T). By that, I mean I wanted to make my own custom version of the stock Marshmallow rom ("Custom but stock OS"). To shorten it up, I wanted to create a .zip flashable "super package" which included SuperSU v2.79, Viper4Android, Overclock tools, and other stuff. I've kinda been on and off in terms of motivation to make this idea a reality, primarily because most of the things I wanted to include in this "package", can easily be installed by you in like 3 minutes, or maybe less. The original motive behind the idea was to lessen the work for power users who wanted to free their device "from the shackles". I've been on and off on work between both devices, but It's hard for me to continue the work without proper motivation. These projects are merely just an Idea at this point, but some drafts and copies do exist on my computer.
Creating a custom Android rom straight from my own head is basically an impossible task for me, considering most of the devices I work with have locked bootloaders. I am still learning Java and other Android programming languages in some of my free time but, again, the motivation to continue is something I struggle to find.
Cheers!
Upgrading OS and rooting
I am currently running my t337a on 4.4.2 with build NK2. I was able to root with towel root awhile ago. I want to upgrade my os to 5.1.1 and root after but would like to make sure I go about it the right way.
Any help would be greatly appreciated. Thanks in advance!
loc626 said:
I am currently running my t337a on 4.4.2 with build NK2. I was able to root with towel root awhile ago. I want to upgrade my os to 5.1.1 and root after but would like to make sure I go about it the right way.
Any help would be greatly appreciated. Thanks in advance!
Click to expand...
Click to collapse
You can root on the latest Lollipop firmware, but it's systemless supersu/temporary, meaning it will go away if you shutdown or reboot the device (you can re-root it, of course, but It can be annoying). The option to upgrade is up to you, and once you do upgrade, you can't downgrade (Locked bootloader & different bootloader versions. Lollipop has the new bootloader.) If you are going to upgrade, you can flash the Lollipop firmware via Odin or upgrade via OTA. If upgrading, I recommend taking it over the air, mainly because I'm still working up Odin packages for them. The Odin packages that I do have available are the BOH4 (the previous and the initial Lollipop update) ones, so if you upgrade OTA, it'll take away one step in the upgrade process, making your life a tad bit easier. Reply back if you need further help or have any more questions.
Cheers!
KingOfTheNet said:
You can root on the latest Lollipop firmware, but it's systemless supersu/temporary, meaning it will go away if you shutdown or reboot the device (you can re-root it, of course, but It can be annoying). The option to upgrade is up to you, and once you do upgrade, you can't downgrade (Locked bootloader & different bootloader versions. Lollipop has the new bootloader.) If you are going to upgrade, you can flash the Lollipop firmware via Odin or upgrade via OTA. If upgrading, I recommend taking it over the air, mainly because I'm still working up Odin packages for them. The Odin packages that I do have available are the BOH4 (the previous and the initial Lollipop update) ones, so if you upgrade OTA, it'll take away one step in the upgrade process, making your life a tad bit easier. Reply back if you need further help or have any more questions.
Cheers!
Click to expand...
Click to collapse
I'm highly considering an upgrade for the feel and hopefully a better performance. Also, a few apps I have need updates but only compatible on Android 5 and up. I have the OTA ready to go. Would I need to unroot before upgrading the OS?
loc626 said:
I'm highly considering an upgrade for the feel and hopefully a better performance. Also, a few apps I have need updates but only compatible on Android 5 and up. I have the OTA ready to go. Would I need to unroot before upgrading the OS?
Click to expand...
Click to collapse
It would be best to unroot before installing to avoid any issues during the installation. Other then that, you're in the clear! Just remember, you cannot downgrade after the install!
Cheers!
KingOfTheNet said:
4) I'm trying to figure out how I could altar the boot.img so we can get permanent SuperSU on this thing the same way Chainfire did it with the US and Qualcomm Samsung Galaxy S7's.
Click to expand...
Click to collapse
I have always been under the assumption that the boot.img for the locked BL on the s7 was literally an engineering kernel from Samsung, and not something Chainfire created. The reason Im saying this is because if Chainfire created a boot image that can get around a locked bootloader, then logic should state that he cracked Sprint/ATT's signature for the BL. So my way of thinking is the success of even one locked boot loader ... it should apply across the board for all, correct? Or am I waaaaay off? lol
leeboski44 said:
I have always been under the assumption that the boot.img for the locked BL on the s7 was literally an engineering kernel from Samsung, and not something Chainfire created. The reason Im saying this is because if Chainfire created a boot image that can get around a locked bootloader, then logic should state that he cracked Sprint/ATT's signature for the BL. So my way of thinking is the success of even one locked boot loader ... it should apply across the board for all, correct? Or am I waaaaay off? lol
Click to expand...
Click to collapse
(1st question) Actually yeah, lol. It was an engineering kernel, he didn't make it . I'm assuming that was used during the development of the phone so Samsung and AT&T could construct the OS without running into any issues with the phones locked bootloader. At the time, I thought that Chainfire thought of some "mad science" to altar the boot.img so that it wont check the signatures of any of the files on boot.
Now I'm thinking:
1) He found a way to obtain all the phones signatures so that way he knows what signature the desired files (like a build of TWRP, or instance) would have to have so it can flash and boot properly.
--OR--
2) He somehow obtained or reproduced the engineering kernel that, like I said, was most likely used during software development for the phone (constructing the OS and the rest of the software).
I've done a little research on what engineering kernels actually do and why they are so useful now (to most people, the name is enough, lol). Apparently, they completely skip some of the signature checks on boot, primarily for /SYSTEM (The OS), which is why we were able to achieve permanent root the Qualcomm Galaxy S7 & S7 edge models. I do not think they skip signature checks for /RECOVERY or /BOOT, but we know that if we either reproduce or obtain the engineering kernel for this tablet, we can achieve permanent root the exact same way. I could be wrong, as I do not know for certain the Ins and outs of engineering kernels and how to get them, but It is very possible.
(2nd question) Now, I do not have much knowledge of bootloaders and signature checks, but I would go to the best assumption that since Sprint & AT&T, for example, are 2 completely different companies and are not affiliated (as of writing this), their bootloaders and updates would not have the same signatures. If they did, then Sprint would have to go to AT&T to sign their updates and such, and AT&T would have to do the same thing for Sprint. It just wouldn't really make sense. Lets think of it this way, If Target wants to sell a product in their stores that's already sold at Walmart, then should Target have to go to Walmart to get that approved? Or if Walmart wanted to sell something that's already sold at Target, then should Walmart have to go to Target for approval? Absolutely not, that wouldn't make any sense. Once again, I could be wrong, but it would make the most sense.
Please, anyone, correct me if I'm wrong.
Cheers!
KingOfTheNet said:
(1st question) Actually yeah, lol. It was an engineering kernel, he didn't make it . I'm assuming that was used during the development of the phone so Samsung and AT&T could construct the OS without running into any issues with the phones locked bootloader. At the time, I thought that Chainfire thought of some "mad science" to altar the boot.img so that it wont check the signatures of any of the files on boot.
Now I'm thinking:
1) He found a way to obtain all the phones signatures so that way he knows what signature the desired files (like a build of TWRP, or instance) would have to have so it can flash and boot properly.
--OR--
2) He somehow obtained or reproduced the engineering kernel that, like I said, was most likely used during software development for the phone (constructing the OS and the rest of the software).
I've done a little research on what engineering kernels actually do and why they are so useful now (to most people, the name is enough, lol). Apparently, they completely skip some of the signature checks on boot, primarily for /SYSTEM (The OS), which is why we were able to achieve permanent root the Qualcomm Galaxy S7 & S7 edge models. I do not think they skip signature checks for /RECOVERY or /BOOT, but we know that if we either reproduce or obtain the engineering kernel for this tablet, we can achieve permanent root the exact same way. I could be wrong, as I do not know for certain the Ins and outs of engineering kernels and how to get them, but It is very possible.
(2nd question) Now, I do not have much knowledge of bootloaders and signature checks, but I would go to the best assumption that since Sprint & AT&T, for example, are 2 completely different companies and are not affiliated (as of writing this), their bootloaders and updates would not have the same signatures. If they did, then Sprint would have to go to AT&T to sign their updates and such, and AT&T would have to do the same thing for Sprint. It just wouldn't really make sense. Lets think of it this way, If Target wants to sell a product in their stores that's already sold at Walmart, then should Target have to go to Walmart to get that approved? Or if Walmart wanted to sell something that's already sold at Target, then should Walmart have to go to Target for approval? Absolutely not, that wouldn't make any sense. Once again, I could be wrong, but it would make the most sense.
Please, anyone, correct me if I'm wrong.
Cheers!
Click to expand...
Click to collapse
No that makes perfect sense and thanks for clearing it up.
The whole thing about the signature being the means by which the bootloader is locked is important. Atleast to me it is, so thank you for clearing that up. :good: And so, it makes sense that the System partitions Signature check being skipped IS what allows access to root. But where my opinion differs on this is the Boot and Recovery implementation of the Signatures. I believe that it IS the carriers implementation that does not allow the Recovery and Boot partitions to be modified. If it were Samsungs then how is Samsung going to incorporate a Universal bootloader that knows how to load all carriers data, policy, etc?
And possibly this is what you were saying above and I am misreading it...
***EDIT*** I see you said that the signatures would NOT be the same between carriers, so I am in line with your theory there as well.
leeboski44 said:
No that makes perfect sense and thanks for clearing it up.
The whole thing about the signature being the means by which the bootloader is locked is important. Atleast to me it is, so thank you for clearing that up. :good: And so, it makes sense that the System partitions Signature check being skipped IS what allows access to root. But where my opinion differs on this is the Boot and Recovery implementation of the Signatures. I believe that it IS the carriers implementation that does not allow the Recovery and Boot partitions to be modified. If it were Samsungs then how is Samsung going to incorporate a Universal bootloader that knows how to load all carriers data, policy, etc?
And possibly this is what you were saying above and I am misreading it...
***EDIT*** I see you said that the signatures would NOT be the same between carriers, so I am in line with your theory there as well.
Click to expand...
Click to collapse
I'm glad I could be of help, however I don't see where I stated that the signature implementations on the BOOT and RECOVERY partitions was Samsung's idea not the carriers, if you could point that out for me that would be great.:good:
The engineering kernels skip SOME signature checks, both when flashing and booting into partitions, but I do not know exactly which ones they skip. We know it skips some of the signatures for /SYSTEM, but it does not do the same for the 2 other main ones, those being /BOOT & /RECOVERY. We know because "one of our own" attempted to flash their own build of TWRP recovery to the device (SM-G930A to be specific) only to get a signature check fail when booting the phone, which of course means that the phone has a locked bootloader and that the signatures for the /RECOVERY partition are still checked, but I do not know for certain about /BOOT. If I had to assume I'd say that /BOOT isn't checked, given the fact that if your phone is rooted then you would have had to flash the engineering kernel, which, like I said, skips some signature checks.
I hope I've cleared most things up for you.
Cheers!
KingOfTheNet said:
I've made this thread to teach T337A owners how to root their device with SuperSU. Please note that this is a system-less root, meaning it's temporary, but can be re-applied. Rooting only takes about 5-7 minutes and brings numerous tweaks and advantages to your device. Just remember that every time you reboot or shut the device down, you will need to repeat the rooting process. This tutorial was designed for Lollipop 5.1.1, but it should work on KitKat as well.
Before beginning, you will need to download the following file, unzip it on your pc, then transfer it to your device's internal storage/external sd card.
Root File: https://mega.nz/#!74Jl0ZqY!knlHuexbYGFkk1f4wHxq16u3L38EtfR9scQ0H7hISTA
Lets start!
1) Install both the APK files in the file on your device, If prompted, allow installation from unknown sources.
2) Make sure your device is connected to WiFi, then open Kingroot.
3) Once Kingroot is "Done searching for the best root strategy", click the "Try Now" button and wait about 3 minutes for KingRoot to give you a "Root Successfully" message.
4) This is where it gets kinda tricky, immediately after receiving the root success message, go into SuperSU-me, and grant root permissions when prompted.
5) Click on the big blue button in the middle of the frame and wait about 1 minute for the process to complete. DO NOT UPDATE THE SUPERSU BINARY, IT WILL BOOTLOOP.
6) IMMEDIATELY after the process has completed, go into Settings and make sure KingRoot or Purify is not installed! This is an important step because Kingroot and Kingroot adware tends to install itself in the system partition which can cause problems and frustration.
7 - Recommended) Download a root file explorer and search "King" under /data and /system to ensure that the KingRoot app and its bloatware has been wiped from the system.
8) Enjoy root access!
If this tutorial helped you please be sure to hit the :good: button. If you had any issues or troubles during this process please feel free to let me know down below.
Need T337A firmware? Check out my thread here: https://forum.xda-developers.com/tab-4/general/download-sm-t337a-lollipop-firmware-t3536509
Cheers!
Click to expand...
Click to collapse
The firmware you provided saved my sm-t337A tablet from being soft bricked. Although I was able to gain temp root from this method, king root tried to disable the SELinux on my device and after trying to temp root again caused the app to implant itself as bloatware into the /systems folder and was non functional when using the app. Do you happen to know of a custom recovery (TWRP or CWM) which would work for this device?
EDIT: Yes! follow this guide! https://forum.xda-developers.com/ma...e-9-magisk-t3666540/post75359033#post75359033 (twrp has to be on 3.0.1 and use the strike-through magisk zip if you encounter problems. My HW zip also threw up errors but seems to have worked anyways)
Is Root currently available on Oreo?
I feel like the answer should be obvious but I can't seem to get a straight answer. The keywords just pull up old nougat root methods.
The rollback threads make it sound like the answer is no, you need to rollback to get root back.
If there is a method and you can point me to one, ideally something like magisk to bypass safetynet. Magisk's current zip (15.3) which claims to be generic fails throwing the error ! Unable to detect boot image; I don't know what's magisk's end and what's the mate 9 community's responsibility right now.
I'm sorry if this is right under my nose and I'm not seeing it.
Hey everyone -
I have a Fire HD 10 (2017 model) that is successfully rooted with SuperSU. I am wondering if anyone has figured out how to gain root access with Magisk? All the tutorials I have found regarding the switch from SuperSU to Magisk involve flashing some zips in TWRP, which we can't do. Has anyone figured it out?
Ultimately, I'm trying to get DirecTV Now to work, but it doesn't play nicely with rooted devices. The Hide My Root app used to work, but it has stopped. If we can't get Magisk to work, I'd at least be happy if someone has advice on getting DirecTV Now working again!
I tried flashing Magisk 16.0 with 15.3 installer today and got stuck in bootloop. It flashed but would just boot to amazon logo over and over. Have a Ti Backup but it sucks. I'm sure there's a way through adb. I'm still learning. I wanna know the best way to flash any zip in general cause without FF TWRP or some other custom recovery im lost. I'm assuming you'd have to uninstall SuperSu anyhow. My 2 cents. Rebuilding new ROM now, I love spending hours doing the same thing ?. In hindsight I get better each time and find new hacks tricks etc.
You might be able to use tasker with a variation of the code in this thread https://forum.xda-developers.com/apps/magisk/microsoft-intune-company-portal-t3611588/page12
btonetbone said:
Hey everyone -
I have a Fire HD 10 (2017 model) that is successfully rooted with SuperSU. I am wondering if anyone has figured out how to gain root access with Magisk? All the tutorials I have found regarding the switch from SuperSU to Magisk involve flashing some zips in TWRP, which we can't do. Has anyone figured it out?
Ultimately, I'm trying to get DirecTV Now to work, but it doesn't play nicely with rooted devices. The Hide My Root app used to work, but it has stopped. If we can't get Magisk to work, I'd at least be happy if someone has advice on getting DirecTV Now working again!
Click to expand...
Click to collapse
Hide Rooting V1.7 is working for me. I rooted yesterday then realized Dtv now stopped working and had to scramble to fix it. So far that's the answer.
chris_dubs said:
I tried flashing Magisk 16.0 with 15.3 installer today and got stuck in bootloop. It flashed but would just boot to amazon logo over and over. Have a Ti Backup but it sucks. I'm sure there's a way through adb. I'm still learning. I wanna know the best way to flash any zip in general cause without FF TWRP or some other custom recovery im lost. I'm assuming you'd have to uninstall SuperSu anyhow. My 2 cents. Rebuilding new ROM now, I love spending hours doing the same thing . In hindsight I get better each time and find new hacks tricks etc.
Click to expand...
Click to collapse
Sorry for any revival, but is that really possible? I don't really think so, because Magisk, is by definition Systemless, meaning that it doesn't affect the system in any way, but modifies the boot.img. And modifying the boot.img even a tiny bit results in a bootloop, because it fails signature verification. I would be glad to hear any ideas because when we manage to get our Amazon tablet rooted, I would prefer Magisk over anything as I always did, because it is open source and systemless.
Today I successfully rooted my HD8 2016 with SuperSu permanently. Install Magisk Manager but hesitate to install Magisk as afraid of boot loop. Is there any solution to "flash" audio mods zip files without Magisk or TWRP?
lifegap said:
Today I successfully rooted my HD8 2016 with SuperSu permanently. Install Magisk Manager but hesitate to install Magisk as afraid of boot loop. Is there any solution to "flash" audio mods zip files without Magisk or TWRP?
Click to expand...
Click to collapse
This is an unrelated question.
btonetbone said:
Hey everyone -
I have a Fire HD 10 (2017 model) that is successfully rooted with SuperSU. I am wondering if anyone has figured out how to gain root access with Magisk? All the tutorials I have found regarding the switch from SuperSU to Magisk involve flashing some zips in TWRP, which we can't do. Has anyone figured it out?
Ultimately, I'm trying to get DirecTV Now to work, but it doesn't play nicely with rooted devices. The Hide My Root app used to work, but it has stopped. If we can't get Magisk to work, I'd at least be happy if someone has advice on getting DirecTV Now working again!
Click to expand...
Click to collapse
So far no. But don't worry. The HD 10 can be unlocked, it's just a matter of its done. Unfortunately, we don't have it easy. The HD 10 is built sorta convoluted. It's 64 but in some cases, 32 in the rest. Something's can't pick up on it. I have a thing or two I am working on. Unfortunately I am dead in the water PC wise until after 10 am. I need a new mouse. And I don't have a spare.
If anyone wants to help... mediatek uses their own fastboot executable, mtboot.exe. I still need to gather all the files to build it and or the binary (they aren't in the right places at all). But it would be nice if the mtboot.exe could be located somewhere on the web.
Also in the Amazon source code for the kernel, they left a potential honey pot. Datool, also known as fbtool. They left the module in their source, and I can't figure out why. In the source it lists some usb props, vendor and product IDs and lists three boot modes: unknown, brom, and preloader. It's also tied into sp flash tool somehow. When you compile the datool at the mediatek source, it will put the tablet into preloader mode. So prehaps it can also put it in brom. But if we can get datool to do a proper dump, we might be able to get SP flash tool working.
That's been my findings the past few days.
Now when I get a mouse, hopefully I will have the first test rom built today.
lifegap said:
Today I successfully rooted my HD8 2016 with SuperSu permanently. Install Magisk Manager but hesitate to install Magisk as afraid of boot loop. Is there any solution to "flash" audio mods zip files without Magisk or TWRP?
Click to expand...
Click to collapse
Sorry, this might be a stupid question. I am new to Magisk Manager.
Did you install both SuperSU and Magisk Manger on HD8 2016? Which one is managing the root access of APPs? How does it work?
Dan_firehd said:
Sorry, this might be a stupid question. I am new to Magisk Manager.
Did you install both SuperSU and Magisk Manger on HD8 2016? Which one is managing the root access of APPs? How does it work?
Click to expand...
Click to collapse
The only thing we have available at the moment for flashing is flash fire, on the HD 10. I have magisk on a few devices. It's pretty cool once you get the hang of it. It's different and took me a while to get to the point of liking it. I think it will be amazing on the HD 10 because the hardware is great. I haven't tried it on my fire 7 yet. I don't have a rooted HD 8.
Sent from my MotoG3 using XDA Labs
DragonFire1024 said:
... The HD 10 is built sorta convoluted. It's 64 but in some cases, 32 in the rest. Something's can't pick up on it.
Click to expand...
Click to collapse
No, it's not. Same way many (arguably most) 64-bit devices behave in a 32/64 hybrid world. Someday 'everything' Android will be 64-bit or greater with 32-bit being religated to history - much 8/16-bit is today. Not there yet, especially on economy devices using older hardware. Amazon is not doing anything weird.
Dan_firehd said:
Sorry, this might be a stupid question. I am new to Magisk Manager.
Did you install both SuperSU and Magisk Manger on HD8 2016? Which one is managing the root access of APPs? How does it work?
Click to expand...
Click to collapse
Only SuperSu manage the root access. Magisk manager without Magisk installed is only an app.
Dan_firehd said:
Sorry, this might be a stupid question. I am new to Magisk Manager.
Did you install both SuperSU and Magisk Manger on HD8 2016? Which one is managing the root access of APPs? How does it work?
Click to expand...
Click to collapse
The SuperSu do the root management. Magisk manager is great on my phone, but it creates disaster on my HD 8 when testing the Magisk installing from the Manager. It made my HD8 boot loop at Amazon logo, no way to boot. I have to sideload the stock ROM then rooting again.
DragonFire1024 said:
If anyone wants to help... mediatek uses their own fastboot executable, mtboot.exe. I still need to gather all the files to build it and or the binary (they aren't in the right places at all). But it would be nice if the mtboot.exe could be located somewhere on the web.
Also in the Amazon source code for the kernel, they left a potential honey pot. Datool, also known as fbtool. They left the module in their source, and I can't figure out why. In the source it lists some usb props, vendor and product IDs and lists three boot modes: unknown, brom, and preloader. It's also tied into sp flash tool somehow.
Click to expand...
Click to collapse
Wondering if your still looking into fbtool - I think your right about its potential in fixing bricks/installing roms. Got a link to the mtboot source still?
Brainstorming how to unbrick patched Fire 7's here:
Fire 7 (2019, mustang) unbrick, downgrade, unlock & root
Make sure to read this guide completely before starting. You will lose all data on the tablet, make a backup of important data before you start. What you need: - a Linux installation. Don't use a VM! Use a live USB, if you don't have Linux...
forum.xda-developers.com
Currently thinking about fbtool and a custom lineage compile, with hacked secureboot, fastboot enabled lk.bin and a preloader which skips rpmb. Further info on mtk's fastboot implementation would be useful.