Hello everybody,
There has been an confusing about the in-build root of LineAgeOS. Wether is is there or not. Well it's only available for ADB. Anyway, I have been browsing the web for a solution and I've come across this site from the Lineage Team that let you download a add-on for Lineage that enables the built-in root.
NOTE THAT THIS IS NOT CHAINFIRE'S SUPERSU ZIP.
If you want SUPERSU go to this link:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
So I'm not gonna hold you any further.
Here is the link to the site.
DOWNLOAD:
https://download.lineageos.org/extras
Have fun with Root on your unofficial Lineage ROMs and Lineage based ROMs:good:
Greetings,
Paulo
Another method to get root access is Magisk. I think the system-less root will work nicely with app like Snapchat.
serdotlinecho said:
Another method to get root access is Magisk. I think the system-less root will work nicely with app like Snapchat.
Click to expand...
Click to collapse
Thats very true. Thanks for the tip:good:
is there a root script i can use for verizon lg g3 for LOS root? supersu binary update caused my handset to lose root and will only bootloop now. :good: in advance
Why-Fi said:
is there a root script i can use for verizon lg g3 for LOS root? supersu binary update caused my handset to lose root and will only bootloop now. :good: in advance
Click to expand...
Click to collapse
Do a full unroot in SuperSU, it will reboot automatically, just in case reboot again, then install the Root add-on with TRWP or any custom recovery.
Report back if it works:good:
Why-Fi said:
is there a root script i can use for verizon lg g3 for LOS root? supersu binary update caused my handset to lose root and will only bootloop now. :good: in advance
Click to expand...
Click to collapse
That's no even related to J5 or this addon!
Try Magisk or phh's SuperUser.
American_Jesus said:
That's no even related to J5 or this addon!
Try Magisk or phh's SuperUser.
Click to expand...
Click to collapse
This thread is not only for J5. I made this so that everyone could see it.
paulo boë said:
This thread is not only for J5. I made this so that everyone could see it.
Click to expand...
Click to collapse
i really appreciate it. i've been getting sideways comments from quite a few individuals concerning this. to elaborate, since the binary update i have absolutely no access to my handset other than with adb shell via a program developed for lg g3 called dp root. the program does not detect root, and since i am boot looping into a lineage os based rom, i figured i would stay away from supersu, since that is the problem. i have to run script into the adb shell to force root. that is the only w ay i will be able to gain root. i cannot boot into recovery since my root got lost. the shell detects the vs985 and also detects android 7.1.1. the rom is octN, which is LOS based.
and to the individual that got nasty because i don't have a j5, i have been trying for days now to find a solution, and if this was j5 specific, which i saw that it was not, i would have looked elsewhere so as to avoid offending anyone for posting on the "wrong thread".
Like magisk hide, iSU can disable or hide the cm-su. Should work with app like Snapchat and Pokemon Go.
Why-Fi said:
i really appreciate it. i've been getting sideways comments from quite a few individuals concerning this. to elaborate, since the binary update i have absolutely no access to my handset other than with adb shell via a program developed for lg g3 called dp root. the program does not detect root, and since i am boot looping into a lineage os based rom, i figured i would stay away from supersu, since that is the problem. i have to run script into the adb shell to force root. that is the only w ay i will be able to gain root. i cannot boot into recovery since my root got lost. the shell detects the vs985 and also detects android 7.1.1. the rom is octN, which is LOS based.
and to the individual that got nasty because i don't have a j5, i have been trying for days now to find a solution, and if this was j5 specific, which i saw that it was not, i would have looked elsewhere so as to avoid offending anyone for posting on the "wrong thread".
Click to expand...
Click to collapse
I guess that is a no that it didnt work Cant you at all boot into recovery?
paulo boë said:
I guess that is a no that it didnt work Cant you at all boot into recovery?
Click to expand...
Click to collapse
no I can't. all I can get is:
1. firmware update screen but the code says it is a g2
or
2.official stock recovery, where, from there it would boot into recovery from factory data reset, but it bypasses that and goes to lg splash screen then boot loop for octos boot screen.
is there a way to bump with adb shell?
here is exactly what happened...
The actions that led to the boot loop were as follows:
1. clean install of rom, gapps, supersu, mr. bump through twrp (clean as in wipe system, data, cache, dalvik)
2. installed all apps backed up to google account through playstore.
3. reset all permissions.
4. verified root and busybox install through root checker app.
5. root checker suggested installation of supersu app for proper functionality
6. installed supersu pro via playstore
7. supersu pro notified of a binary update requirement, binary was updated.
8. reboot from update led to boot loop.
I believe that updating the binary through the supersu pro app without bump caused loss of root, hence the inability to access recovery. I have tried to return to stock with lg software via .tot method. The software doesn't recognize the device. It does recognize a device i have with a bad esn, so the drivers are correct. I can put the device in download mode, but the id that it gives for the device in the box at the bottom of the screen is consistent with lg g2.
I have adb shell access to the device, which is recognized as vs985 with Android 7.1.1., no root detected (dp root lg g3). What i don't have is working knowledge of adb commands and scripts.
I have posted on the supersu thread as well, but as of yet, no one has helped. I get the same "wrong thread go post somewhere else." I figured I might be able to force los root, since it doesn't need bump. I just don't know scripts and can't find any that I would be able to use.
Why-Fi said:
no I can't. all I can get is:
1. firmware update screen but the code says it is a g2
or
2.official stock recovery, where, from there it would boot into recovery from factory data reset, but it bypasses that and goes to lg splash screen then boot loop for octos boot screen.
is there a way to bump with adb shell?
here is exactly what happened...
The actions that led to the boot loop were as follows:
1. clean install of rom, gapps, supersu, mr. bump through twrp (clean as in wipe system, data, cache, dalvik)
2. installed all apps backed up to google account through playstore.
3. reset all permissions.
4. verified root and busybox install through root checker app.
5. root checker suggested installation of supersu app for proper functionality
6. installed supersu pro via playstore
7. supersu pro notified of a binary update requirement, binary was updated.
8. reboot from update led to boot loop.
I believe that updating the binary through the supersu pro app without bump caused loss of root, hence the inability to access recovery. I have tried to return to stock with lg software via .tot method. The software doesn't recognize the device. It does recognize a device i have with a bad esn, so the drivers are correct. I can put the device in download mode, but the id that it gives for the device in the box at the bottom of the screen is consistent with lg g2.
I have adb shell access to the device, which is recognized as vs985 with Android 7.1.1., no root detected (dp root lg g3). What i don't have is working knowledge of adb commands and scripts.
I have posted on the supersu thread as well, but as of yet, no one has helped. I get the same "wrong thread go post somewhere else." I figured I might be able to force los root, since it doesn't need bump. I just don't know scripts and can't find any that I would be able to use.
Click to expand...
Click to collapse
Im sorry to disappoint you. But I cannot find any scripts or anything actually to help you. Im not new to all of this but im still learning. I have been searching Google for a couple of hours but i have found nothing concerning your problem.
paulo boë said:
Im sorry to disappoint you. But I cannot find any scripts or anything actually to help you. Im not new to all of this but im still learning. I have been searching Google for a couple of hours but i have found nothing concerning your problem.
Click to expand...
Click to collapse
that in itself is a big help. thank you. it means a lot. have a good one, brother.
Why-Fi said:
that in itself is a big help. thank you. it means a lot. have a good one, brother.
Click to expand...
Click to collapse
Thanks, you too:good:
paulo boë said:
Thanks, you too:good:
Click to expand...
Click to collapse
thanks for sharing.
this root addon has no user interface.
we cannot manage the apps which can be root granted/denied in later stages once u tick remember in the pop up
@paulo boë do you have any suggestion or idea how to get a manager or UI for CM root.
reversegear said:
thanks for sharing.
this root addon has no user interface.
we cannot manage the apps which can be root granted/denied in later stages once u tick remember in the pop up
@paulo boë do you have any suggestion or idea how to get a manager or UI for CM root.
Click to expand...
Click to collapse
Isnt there in the developer options an option to manage root? Otherwise i have no idea how to manage.
paulo boë said:
Isnt there in the developer options an option to manage root? Otherwise i have no idea how to manage.
Click to expand...
Click to collapse
I'm using RR nougat
Root options not available in developers option...
Anyway I'll search for something which does the job. I'll let u know if I find something
serdotlinecho said:
Another method to get root access is Magisk. I think the system-less root will work nicely with app like Snapchat.
Click to expand...
Click to collapse
pretty much I get same result on Magisk since if I need to bypass root check I just need to disable in built root or Magisk, since Magisk doesent pass Safety net.
Related
So I have a Starmobile Quest which is a local smartphone and I rooted it using a chinese rooting program called iroot, formerly vroot, as suggested by people using the same phone. At first the superuser app(which is a Chinese one) is working fine and I could use apps requiring root access but suddenly, something happened and now it won't give root access to any of the apps. I think, maybe root was somehow removed, and downloaded the root checker app and when I ran it, it told me that I wasn't rooted.
So I unrooted my phone using iroot and it was successful and again rooted it which was again successful. I go and run root checker again and I was surprised to see that I wasn't rooted. From there I repeated the unrooting and rooting process several times and still nothing. What I did notice was that whenever iroot was checking whether my phone was rooted, a pop up would appear on my phone which is from the superuser app asking for permission to give "shell" root access and I would always say yes.
I believe that my phone is actually rooted but the superuser app isn't promting me for root access whenever I use apps that require root, plus there is no log saved except for the "shell" one. I tried changing root access manager app to supersu and when I run it it tells me that it needs to update su binary. I click yes and use the normal method(I don't have cwm) and it tells me it's installing but after awhile I receive an error saying "installation failed. try rebooting.". I reboot my phone and try updating again and it still fails.
I tried everything the internet threw at me, reroot, factory reset, clear data, clear cache, etc and nothing's working. Can someone help me here?
Note: I can't find a stock/custom rom for my device. So flashing roms isn't an option for me.
Bump.
have you tried to flash another version of superuser?
Crom4rtie said:
have you tried to flash another version of superuser?
Click to expand...
Click to collapse
How do I do that?
black_fire21 said:
How do I do that?
Click to expand...
Click to collapse
go to your recovery and go to install zip ..choose your zip ..or just download supersu from the playstore
Crom4rtie said:
go to your recovery and go to install zip ..choose your zip ..or just download supersu from the playstore
Click to expand...
Click to collapse
Do you need a custom recovery for that? Because the model of the phone doesn't have a custom recovery yet.
Also, I tried to install supersu from the play store and it didn't work.
black_fire21 said:
Do you need a custom recovery for that? Because the model of the phone doesn't have a custom recovery yet.
Also, I tried to install supersu from the play store and it didn't work.
Click to expand...
Click to collapse
yes you need a custom recovery...but if the su from the playstore didn´t work then will this also not work
Crom4rtie said:
yes you need a custom recovery...but if the su from the playstore didn´t work then will this also not work
Click to expand...
Click to collapse
Damn it. I guess I'll have to wait till they make a stock rom which I think isn't gonna happen since it's been half a year since the phone is released and there hasn't been any development.
Last question, Is it possible to flash your phone using a computer?
black_fire21 said:
Damn it. I guess I'll have to wait till they make a stock rom which I think isn't gonna happen since it's been half a year since the phone is released and there hasn't been any development.
Last question, Is it possible to flash your phone using a computer?
Click to expand...
Click to collapse
Yes absolutely. Just note that there are no rooting apps on the Play Store. Simply downloading SuperSU or Superuser will NOT root your phone. You need to be rooted first, and if the SuperSU or Superuser app isn't automatically installed, then once you root you can install SuperSU or Superuser to manage apps that require root.
Popular methods of rooting include z4root, framaroot, MTKTools and iroot (or vroot)
Z4root and framaroot are both android applications which you will need to get from their sites or XDA (just run a search). MTKtools and iroot/vroot are computer applications and use ADB. MTKTools can also create a custom recovery for your device, though I don't remember the process too well.
Once you're rooted you will either have your Superuser app installed or you'll have to install it yourself (I personally prefer SuperSU). I also recommend installing busybox as well.
Hope that helps.
Don't forget to hit the thanks button if I helped you~
SeraphSephiroth said:
Yes absolutely. Just note that there are no rooting apps on the Play Store. Simply downloading SuperSU or Superuser will NOT root your phone. You need to be rooted first, and if the SuperSU or Superuser app isn't automatically installed, then once you root you can install SuperSU or Superuser to manage apps that require root.
Popular methods of rooting include z4root, framaroot, MTKTools and iroot (or vroot)
Z4root and framaroot are both android applications which you will need to get from their sites or XDA (just run a search). MTKtools and iroot/vroot are computer applications and use ADB. MTKTools can also create a custom recovery for your device, though I don't remember the process too well.
Once you're rooted you will either have your Superuser app installed or you'll have to install it yourself (I personally prefer SuperSU). I also recommend installing busybox as well.
Hope that helps.
Don't forget to hit the thanks button if I helped you~
Click to expand...
Click to collapse
So how do I do that?
Hello my buddy so I 've read your thread, there are many apps to do root like root master, framaroot, towel root, towelpieroot. And the way to install super su is doing again the root. And after to install it again.
These apps to do root.
YAMALILLO JR said:
These apps to do root.
Click to expand...
Click to collapse
Okay so some of those do. But not all are supported anymore.
---------- Post added at 04:47 AM ---------- Previous post was at 04:11 AM ----------
black_fire21 said:
So how do I do that?
Click to expand...
Click to collapse
So MTKTools can be found scattered all over XDA, and Framaroot has a dedicated thread (which I cannot link right now as I am on my phone). If memory serves, Jellybean and below had Dev options enabled by default. If not, go to settings -> About Device and tap on the build number several times until your dev options are enabled. Then simply enable USB debugging. When you plug in your device you may need to authenticate your PC to use the Debug bridge. Just hit accept. (I'm sure that you were aware of how to enable ADB but I felt I had to explain anyway)
I assume you have the ADB drivers for your device, but if not, there is a naked USB driver installer floating around XDA (I really would only trust XDA with stuff like this)
With ADB enabled you can use the iroot and MTKTools PC applications. Both are generally straightforward but don't hesitate to ask me if you have a question.
With the APK apps you can get from XDA and abroad, you can root the device somewhat easily.
Framaroot (last time I used it) has four options for rooting (latest version is 1.9.3) you will see all info you need on that thread.
Z4 root I do not recommend. It is somewhat outdated now, though you might want to try it as a last resort
Towelroot is fairly simple as well. Simply download and run the app and you'll either get root or you won't.
My personal recommendations are MTKTools for a pc toolkit (seeing as it can compile a custom recovery too, which it did for my Lenovo S6000)
For apk rooting, I suggest Framaroot. I've never had any problems with it thus far.
I hope that explained it enough but if not, don't hesitate to ask questions. After all, you never learn if you don't ask ^-^
Nevermind guys. I downloaded a bunch of rooting programs and tried them. Root Genius worked and now I have root access. Thanks for replying to this thread.
ReInstall SuperSU and check with Android Terminal Emulator.
Ok dudes just i share this thread, cuz i like to help other dudes that they are juniors or they're beginning .
So a few months ago I bought my first Android phone in years, a ZTE Max Duo from Straight Talk. Unfortunately, since then I have found absolutely nothing about the phone on forums like this, let alone any way to root it. Has anyone managed to root this phone, and if so, how? I don't have regular access to a PC, but if the only way to root it is through a PC, I might ask for permission to use one.
I am looking for the same with this phone.. It seems like a great piece of hardware thus far bit could use some tweaks that a root could certainly take care of but no info whatsoever.. Any help with this would be great.
I figured out how to root the ZTE max duo (z963vl) via (iroot) I have the exact file and can tell u what to enable for root email me at [email protected] il send the file
Any Success?
It looks like there are a few variants of this device. I have the Imperial Max that is sold on US Cellular. Exact same phone and specs except for the radio.
ZTE MAx Duo root
Jimmy_moseley said:
I figured out how to root the ZTE max duo (z963vl) via (iroot) I have the exact file and can tell u what to enable for root email me at [email protected] il send the file
Click to expand...
Click to collapse
I would like a copy of that file if you still have it and don't mind sharing it.
Man I've been trying to find any custom ROM or something that can get me to 6.0+ or 7.0+ because I can't deal with 5.1.1
But after searching relentlessly it seems that it doesn't exist.
I've been trying to find a ROM we could port over but that's looking grim too. I made a request over at CM so hopefully someone gracious enough will make one.
Zte duo max z963vl root
figured out how to root the ZTE max duo (z963vl) via (iroot) I have the exact file and can tell u what to enable for root email me at [email protected] il send the file
I would lime a copy of that file an info if it's no bother my email is [email protected] thanks
KingRoot now roots the phone but the bootloader is still locked!
The ZTE max duo LTE (z963vl) can now be rooted via KingRoot but only temporarily. When you reboot the phone you will lose root. You can not make any system changes either still because the bootloader is still locked after root. You can not update BusyBox either. Also when you root the phone with KingRoot it says "This model restricts root authorization". To fix that error just completely close KingRoot and re-open it and it will fix the root authorization error. Dev's or anyone for that matter please help unlock this phone's bootloader please I really want to start getting custom roms and recovery for this phone plus I want to be able to write to /system. I hope this helps as much as possible and I hope the bootloader will become unlocked with all the Devs help. Also I did this with the apk version of KingRoot only because I do not have a PC.
Great news...
MarDey said:
The ZTE max duo LTE (z963vl) can now be rooted via KingRoot but only temporarily. When you reboot the phone you will lose root. You can not make any system changes either still because the bootloader is still locked after root. You can not update BusyBox either. Also when you root the phone with KingRoot it says "This model restricts root authorization". To fix that error just completely close KingRoot and re-open it and it will fix the root authorization error. Dev's or anyone for that matter please help unlock this phone's bootloader please I really want to start getting custom roms and recovery for this phone plus I want to be able to write to /system. I hope this helps as much as possible and I hope the bootloader will become unlocked with all the Devs help. Also I did this with the apk version of KingRoot only because I do not have a PC.
Click to expand...
Click to collapse
This is a good start... hopefully something comes of this... God I want this phone rooted!!!
Hmmmmm...
So I tried Mardeys method and it did root like he said... installed su superuser and root checker... they worked... busybox wouldn't install... restarted my phone and lost root... so I did it all again then just powered off my phone and started it with power button and volume up... took me to recovery screen with a few options... one being sideload with adb...
I am new at all this so don't know if that helps but would love to get this thing rooted...
bent213 said:
So I tried Mardeys method and it did root like he said... installed su superuser and root checker... they worked... busybox wouldn't install... restarted my phone and lost root... so I did it all again then just powered off my phone and started it with power button and volume up... took me to recovery screen with a few options... one being sideload with adb...
I am new at all this so don't know if that helps but would love to get this thing rooted...
Click to expand...
Click to collapse
Which superuser app are you using? The one by ChainDD just crashes when I run it, and SuperSU keeps saying the binary needs to be updated but fails when I try to do it.
Kitland54 said:
Which superuser app are you using? The one by ChainDD just crashes when I run it, and SuperSU keeps saying the binary needs to be updated but fails when I try to do it.
Click to expand...
Click to collapse
Wall here's what my whole setup was... I ran King root... It said I was rooted but didn't restart my phone... I installed superuser and ran it... This is the one I used... Supersu by chainfire... I installed busy box also but had the same problem about need to update binary files blah blah blah... I then installed a root checker and said I was rooted... Super su was found and busy box... Still no reboot... So I tried installing a few root apps... I installed a app remover for bloat were and it worked... But... When I reboot my phone I lose it all... And can redo it all again but it won't stay on there... Not tech dumb but don't know enough to figure it out... Hopefully that helps you a little as far as what my experience was... Like I said before... If I boot into recovery there is an adb sideboard option so... Just hope it gets figured out soon... Would love to have this rooted with a good room on it.... Starting to think it's a hopeless cause... One more thing to add... While rooted I installed a boot manager to see if it would go into a deeper boot recovery mode at restart but it didn't...
I honestly wish I could swap out Kinguser for something else. SCR ScreenRecorder Pro doesn't seem to realize that there is root, even after granting it permission through Kinguser, which leads me to believe either I'm not actually rooted, or KingUser is garbage.
Does anyone have the firmware for this phone?
No answers? Nothing?
Did you guys try $su reboot disemmcwp in a terminal after rooting? That's always the next step on ZTE phones.
Going to try that now... Can't find a copy of the firmware anywhere however. Worries me in case I need to reflash
I'd like to get this phone rooted too I've only been only to temproot by kingroot
Dzion said:
No answers? Nothing?
Click to expand...
Click to collapse
Hey guys I'm also new to this whole rooting thing but would very much to root this phone it's the nicest one I have ever owned and want to get all the performance and overall user control that I can out of it any news or updates would be greatly appreciated thanks fuzzy
bichofelix said:
Did you guys try $su reboot disemmcwp in a terminal after rooting? That's always the next step on ZTE phones.
Click to expand...
Click to collapse
Just tried it myself, but after it's done rebooting, the root's still gone.
Edit: I've noticed that the XDA Labs app seems to think this is a ZTE Blade. Perhaps I might have some luck there?
I know this model is new, but how do we start a section for this model? It's a great phone with plenty under the hood. It seems to have an unlock oem bootloader option in the developer options. How can I root this phone, but more importantly, are there any custom ROMs which will work with it? Can there be some ported over? Any assistance appreciated.
This is the ZTE Warp 7 N9519 for Boost Mobile
:highfive:
GrimeSyndicate said:
I know this model is new, but how do we start a section for this model? It's a great phone with plenty under the hood. It seems to have an unlock oem bootloader option in the developer options. How can I root this phone, but more importantly, are there any custom ROMs which will work with it? Can there be some ported over? Any assistance appreciated.
This is the ZTE Warp 7 N9519 for Boost Mobile
:highfive:
Click to expand...
Click to collapse
I have this phone it seems unrootable. Help?
I know i have tge same device....someone getthis phone and help us...im stuck in the same spot.
I'm on the same page. Spent a few hours on trying to find a working root method but no success. However, King root, specifically version 4.1.0.703, worked for a bit then after close to 30 minutes, the phone restarted itself and was unrooted. I decided not to try it again especially since I just got this phone yesterday.
I have this phone too... Been all over the forums, all over xda university, and im still lost... If someone could give me a little direction, custom recovery or root access... Do i have to build from source? That seems a little above my pay-grade
so has anyone found a solution for rooting?
i looked at XDA a while back when i first got the phone but nothing.
ive been doing reaserch and placing my findings in a different androidforums.(website)
since i didnt see any options to post on here.
anyone wanna help us with info?
KingRoot works after a couple of tries, root access verified, but phone will reboot anywhere from 30 seconds to 30 minutes and root access is denied upon phone start. Haven't tried anything fancy in the little time I've had root access, then again I am not sure this phone is even compatible with custom recovery nor does it have any development of custom roms.. Wondering why the phone reboots and removed root, set SELinux to permissive to no avail, maybe there's a security package or two that could be disabled/blocked to prevent the phone from removing root access?
Really good phone for the money and the specs lend well to a debloated/custom ROM.. Not giving up on these lesser loved phones, finally got my S550TL rooted thanks to the helpful members here don't want to stop now lol.
Caddykings1987 said:
KingRoot works after a couple of tries, root access verified, but phone will reboot anywhere from 30 seconds to 30 minutes and root access is denied upon phone start. Haven't tried anything fancy in the little time I've had root access, then again I am not sure this phone is even compatible with custom recovery nor does it have any development of custom roms.. Wondering why the phone reboots and removed root, set SELinux to permissive to no avail, maybe there's a security package or two that could be disabled/blocked to prevent the phone from removing root access?
Really good phone for the money and the specs lend well to a debloated/custom ROM.. Not giving up on these lesser loved phones, finally got my S550TL rooted thanks to the helpful members here don't want to stop now lol.
Click to expand...
Click to collapse
Have you tried installing the su file with SuperSu before the device rebooted. Because when I had root for less than 10 minutes I checked to see if there was a su file installed and there wasn't any. Is like if KingRoot was simulating root access and didn't install the su file.
---------- Post added at 04:07 PM ---------- Previous post was at 04:01 PM ----------
Heartseed said:
I'm on the same page. Spent a few hours on trying to find a working root method but no success. However, King root, specifically version 4.1.0.703, worked for a bit then after close to 30 minutes, the phone restarted itself and was unrooted. I decided not to try it again especially since I just got this phone yesterday.
Click to expand...
Click to collapse
You should try installing the su file with SuperSu because KingRoot doesn't really install the su file and when the device reboots it removes all root access that KingRoot was simulating. I recommend getting root access with KingRoot then installing the su file with SuperSu and see if it works.
Has any one tried adding SuperSu after temp KingRoot? Or tried adding SuperSU and replacing KingRoot with Super-Sume Pro app?
Just tried Rooting with KingRoot thru APK and didn't even temp root
shezzy83 said:
Has any one tried adding SuperSu after temp KingRoot? Or tried adding SuperSU and replacing KingRoot with Super-Sume Pro app?
Just tried Rooting with KingRoot thru APK and didn't even temp root
Click to expand...
Click to collapse
If KingRoot is not temp rooting your device just go to recovery and clear cache then it should work. Also I wanted to update the su file with SuperSU when I had temp root but I fear it might brick or something. I found out the su was located at sbin.
Are we getting anywhere on this? I really like this phone but i need to de-bloat
drgsrbad81 said:
Are we getting anywhere on this? I really like this phone but i need to de-bloat
Click to expand...
Click to collapse
Not really, I just need someone to update the su binary with SuperSU once temp rooted with KingRoot to see if after that the root doesn't remove after reboot. Or maybe moving the Su file to xbin or bin since it is at sbin.
Tried to install binary through Chainfire SuperSU app and got the "binary update failed" message.
Weird how KingRoot simulates root access without installing any SU binaries, I was able to disable a few packages and verify root access through other apps until the phone restarted.
Can you flash an SU binary through flashify or similar app without restarting to bootloader/recovery (where root access is once again revoked)?
hmmm....thinking of using this as my next phone can anyone give info on a working Fastboot Mode? if there is then we can maybe do the same method of flashing a custom TWRP recovery in order to flash SuperSU
Really like this phone, just got it yesterday. I tried the temp root with kingroot and then after 5 or 10 minutes it rebooted. I'm a bit hesitant to download Flashify and try flashing as I do not know what will happen. But its a good start we have an entry point to work with :silly:
Caddykings1987 said:
Tried to install binary through Chainfire SuperSU app and got the "binary update failed" message.
Weird how KingRoot simulates root access without installing any SU binaries, I was able to disable a few packages and verify root access through other apps until the phone restarted.
Can you flash an SU binary through flashify or similar app without restarting to bootloader/recovery (where root access is once again revoked)?
Click to expand...
Click to collapse
Actually it does install a su binary because when I go to sbin I see a su file there
I was able to confirm root after rooting with kingroot and i tried replacing it with SU but it fails and reboots. I'm very new to ZTE as this is my first phone. I wouldn't think obtaining permanent root would be super difficult since we are able to get some sort of root with king. I am no code expert either so I remain in the dark...
mycosmicmind said:
I was able to confirm root after rooting with kingroot and i tried replacing it with SU but it fails and reboots. I'm very new to ZTE as this is my first phone. I wouldn't think obtaining permanent root would be super difficult since we are able to get some sort of root with king. I am no code expert either so I remain in the dark...
Click to expand...
Click to collapse
So I noticed something very helpful that will totally or maybe allow us to have permanent root. When I rooted with KingRoot I went to Superuser and it said that su binary can't be updated because of its location /sbin/su, so that shows that the su file needs to be at /xbin or /bin. We can try moving the su file to /xbin or /bin once we have temp root to see if it becomes permanent.
---------- Post added at 09:14 PM ---------- Previous post was at 09:13 PM ----------
So I noticed something very helpful that will totally or maybe allow us to have permanent root. When I rooted with KingRoot I went to Superuser and it said that su binary can't be updated because of its location /sbin/su, so that shows that the su file needs to be at /xbin or /bin. We can try moving the su file to /xbin or /bin once we have temp root to see if it becomes permanent.
i can try tomorrow, i dont know if i'll be able to do it before a reboot though
mycosmicmind said:
i can try tomorrow, i dont know if i'll be able to do it before a reboot though
Click to expand...
Click to collapse
The average is about 5 minutes that it allows you to have root, sometimes it let's you even more but it reboots.
Huge thanks to vadosnake for discovering this !
It's been a wait of 2 years, and King root has finally achieved root on this device. This method was tested on the Lollipop firmware, and others have said it works on KitKat as well. To root the G850A, follow these steps:
1.) Download the two APKs provided below, which we'll need for later
2.) Enable Unknown Sources by going to Settings, then Security, and the option should be right there
3.) Now install KingRoot 4.81. A message will pop up saying that the app is malicious, but just click "Install Anyway"
4.) Now enter the King root app and click Root. The phone will reboot, but that is normal. Go back into the app again and the process should continue until it's complete. Voila, your phone is now rooted. However, we will be replacing KingRoot with SuperSU.
5.) Install the second APK called SuperSume. After it's done, click the big green button, give it root access, and it will replace KingRoot with SuperSU in 1 minute.
6.) Go into the Play Store and update SuperSU. After it's done updating, go into the app and it will pop up with a message saying to update the binaries. Click continue then "Normal". DO NOT CLICK TWRP/CWM, OR IT WILL SOFTBRICK YOUR DEVICE.
7.) After that., you're done. You now have root with SuperSU.
Please make sure to show this to AT&T Galaxy Alpha users. Especially developers, so we can get some roms
Did anyone try this? Why does King Root need internet access to root? I'm afraid to turn on the internet in case it tries to steal data.
PopTartKing said:
Huge thanks to vadosnake for discovering this !
It's been a wait of 2 years, and King root has finally achieved root on this device. This method was tested on the Lollipop firmware, and others have said it works on KitKat as well. To root the G850A, follow these steps:
1.) Download the two APKs provided below, which we'll need for later
2.) Enable Unknown Sources by going to Settings, then Security, and the option should be right there
3.) Now install KingRoot 4.81. A message will pop up saying that the app is malicious, but just click "Install Anyway"
4.) Now enter the King root app and click Root. The phone will reboot, but that is normal. Go back into the app again and the process should continue until it's complete. Voila, your phone is now rooted. However, we will be replacing KingRoot with SuperSU.
5.) Install the second APK called SuperSume. After it's done, click the big green button, give it root access, and it will replace KingRoot with SuperSU in 1 minute.
6.) Go into the Play Store and update SuperSU. After it's done updating, go into the app and it will pop up with a message saying to update the binaries. Click continue then "Normal". DO NOT CLICK TWRP/CWM, OR IT WILL SOFTBRICK YOUR DEVICE.
7.) After that., you're done. You now have root with SuperSU.
Please make sure to show this to AT&T Galaxy Alpha users. Especially developers, so we can get some roms
Click to expand...
Click to collapse
cqdiep said:
Did anyone try this? Why does King Root need internet access to root? I'm afraid to turn on the internet in case it tries to steal data.
Click to expand...
Click to collapse
It needs Internet access to search in their database for a root solution.
I got SuperSU to install, but it can't update the binaries. It says "Installation failed! Please reboot and try again." after trying to update the binaries. The Root Checker app did confirm that it was rooted.
PopTartKing said:
It needs Internet access to search in their database for a root solution.
Click to expand...
Click to collapse
cqdiep said:
I got SuperSU to install, but it can't update the binaries. It says "Installation failed! Please reboot and try again." after trying to update the binaries. The Root Checker app did confirm that it was rooted.
Click to expand...
Click to collapse
For now, I tend to leave the app closed, and just wait until root prompts appear for root apps
Yeah, I'm doing that too.
PopTartKing said:
For now, I tend to leave the app closed, and just wait until root prompts appear for root apps
Click to expand...
Click to collapse
No Luck
I just ran the included 4.8.1 and online 5.0.1 versions, neither worked. So I tried the 4.8.1 a few times (including restarts) and the Super-SuMe anyway, but it didn't do anything past "Preparing environment" for 20 minutes.
Additional note, the 4.8.1 seems to have problems in general. After trying to root and failing, it'll continue using 80% of my cpu on some other processes within it's directory (mostly Schrodinger).
I'm running Android 5.0.2 (G850AUCU1BOC7), Kernel 3.4.0-4486597, Build LRX22G. It's the last update ATT gave us.
zyphuris55 said:
I just ran the included 4.8.1 and online 5.0.1 versions, neither worked. So I tried the 4.8.1 a few times (including restarts) and the Super-SuMe anyway, but it didn't do anything past "Preparing environment" for 20 minutes.
Additional note, the 4.8.1 seems to have problems in general. After trying to root and failing, it'll continue using 80% of my cpu on some other processes within it's directory (mostly Schrodinger).
I'm running Android 5.0.2 (G850AUCU1BOC7), Kernel 3.4.0-4486597, Build LRX22G. It's the last update ATT gave us.
Click to expand...
Click to collapse
Same, tried both 4.8.1 and 5.0.1, neither worked. Same android and baseband version as yours.
Thanks so much for this. I'm curious exactly which version of Lollipop on the g850a this was tested and working on? Was it specifically 5.0.1 or 5.0.2 something like that? I just want to make sure I can follow it exactly so it works.
Root access was lost after a couple of days. I'm on 4.4.4.
cqdiep said:
Yeah, I'm doing that too.
Click to expand...
Click to collapse
Well this is strange, I followed this exact tutorial about 1 month ago and everything worked fine, now the app just freezes and after 5 minutes gives off a "Root Fail" message. I'm still running v4.8.1 on the app and still running on the KitKat firmware. This makes no sense at all.
Edit: The phone is no longer supported by Kingroot
Hey guys, sorry for not replying, my internet has been down for the past two weeks . It seems that everyone is having problems keeping root after a while. I might not be a developer, but here's my advice: Once root is obtained, do what you want to do (ie. change emojis or install ViperAudio), then don't touch the SuperSU app until some more skilled developers put this root to full use . I'm sorry for not being more useful, but I just want everyone to know that this device isn't dead. What we need right now is something like SafeStrap for some some-what custom roms.
Any one having issue getting this to work?
PopTartKing said:
Hey guys, sorry for not replying, my internet has been down for the past two weeks . It seems that everyone is having problems keeping root after a while. I might not be a developer, but here's my advice: Once root is obtained, do what you want to do (ie. change emojis or install ViperAudio), then don't touch the SuperSU app until some more skilled developers put this root to full use . I'm sorry for not being more useful, but I just want everyone to know that this device isn't dead. What we need right now is something like SafeStrap for some some-what custom roms.
Click to expand...
Click to collapse
Yeah, Kingroot pulled support from it after people started using supersu-me to get supersu on their devices instead of kingroot. Well, to me, it sounds like a jealousy problem on Kingroots end. It's not like everyone is buying the pro version of the app. Their main source of money is ad revenue. They also pulled support from the Galaxy S5 and many other devices mainly because of people using supersu-me. Kingroot has got to get the stick that is in it's butt right now out ASAP. A 'friend' of mine literally sold his S5 because it couldn't be rooted anymore, and i'm thinking about selling my G850A because it can't be rooted anymore.
Just to clarify this, there's absolutely no way on the internet that the G850A can be rooted, ever?
chocolatewings said:
Just to clarify this, there's absolutely no way on the internet that the G850A can be rooted, ever?
Click to expand...
Click to collapse
Not anymore. It only had root for like 1 month then Kingroot removed support, you can blame them. Unless someone is exploit something so we can have root back, there is no way to root this phone anymore. I know, it sucks, just like the Kingroot developers, but that's just life.
cqdiep said:
Root access was lost after a couple of days. I'm on 4.4.4.
Click to expand...
Click to collapse
Hi
Im doing that and 100% complete but i check root by root check not request from super user
Solution found!
Hi guys. I think I found the trick. Just disable Internet connection (Mobile data and WiFi) just before lunching kingroot app this would evade the app from "searching the best root solution" which is "nothing found".
I used the exact same files uploaded in the OP and it works great, including the supersume part.
Good luck.
I'm very lucky to root my device. waited One year and 4 months and got the fruit of patience. Now I love my device. I have patched Tethering Provision. Now I can easily open hotspot.. no need of foxfi etc... ? Congratulations to those who got there device ROOOOTED.. ?
babarjoya said:
I'm very lucky to root my device. waited One year and 4 months and got the fruit of patience. Now I love my device. I have patched Tethering Provision. Now I can easily open hotspot.. no need of foxfi etc... Congratulations to those who got there device ROOOOTED..
Click to expand...
Click to collapse
Salam. Babar bhai hamen bhi bata den k kaise root kar lia ap ne. please
I successfully rooted my HD7(4th) using Kingroot and reverted it back to 4.5.3. I disabled OTA updates via ADB (pm block com.amazon.otaverifier somethin somethin), but I am now trying to go back to stock build 5.3.6 (amz/gp/help/customer/display.html?nodeId=201596850). I cannot for the life of me figure out flashing the bin/.zip files using TWRP, PlatformTools, SuperTool, etc.
Somehow I have lost the 'update from ADB' option during recovery (only seeing 2 options now, Reboot your fire, and Reset to factory). Running bootloader doesn't do anything. Just black screen.
OTA update checker in System Updates always says Last updated failed despite turning off root, uninstalling Kingroot, unblocking OTA verifier manually in ADB, then doing factory reset, etc. Still says 4.5.3 and will not allow me to update.
Halp! Any help is appreciated. TIA.
doobius said:
I successfully rooted my HD7(4th) using Kingroot and reverted it back to 4.5.3. I disabled OTA updates via ADB (pm block com.amazon.otaverifier somethin somethin), but I am now trying to go back to stock build 5.3.6 (amz/gp/help/customer/display.html?nodeId=201596850). I cannot for the life of me figure out flashing the bin/.zip files using TWRP, PlatformTools, SuperTool, etc.
Somehow I have lost the 'update from ADB' option during recovery (only seeing 2 options now, Reboot your fire, and Reset to factory). Running bootloader doesn't do anything. Just black screen.
OTA update checker in System Updates always says Last updated failed despite turning off root, uninstalling Kingroot, unblocking OTA verifier manually in ADB, then doing factory reset, etc. Still says 4.5.3 and will not allow me to update.
Halp! Any help is appreciated. TIA.
Click to expand...
Click to collapse
If you are on 4.5.3 bootloader you can easily boot to unsigned recovery images. So install flashify and download the twrp for ariel and flash it:
https://forum.xda-developers.com/fire-hd/development/recovery-twrp-3-0-2-0-t3488768
So here you can install any zip, but when you finish, restore the correct recovery.img. For example: If you update to 5.3.6 with TWRP, then flash the 5.3.6 recovery.
But be careful of what you do, you can brick the tablet by flashing wrong bootloaders.
haha. too late. i apparently hadnt set up twrp the right way. added it, and decided to go back to the newest version OS directly from amazon without thinking. so now i am on 5.6.1, cant do anything cool, and to make it worse, opted to add supersu installer. so now i have supersu installer that i cannot remove on a locked os.
doobius said:
haha. too late. i apparently hadnt set up twrp the right way. added it, and decided to go back to the newest version OS directly from amazon without thinking. so now i am on 5.6.1, cant do anything cool, and to make it worse, opted to add supersu installer. so now i have supersu installer that i cannot remove on a locked os.
Click to expand...
Click to collapse
Wow very nice. You can use this toolbox in the next version since the dev will add support for ariel for debloat and do more things without root:
https://forum.xda-developers.com/hd8-hd10/development/official-amazon-fire-toolbox-v1-0-t3889604
thank you for the replies Rortiz2. i am going to stop tinkering and ask for advice here before i make things worse.
so with this tool, i am able to debloat, but must retain the updated OS (5.6.1)? i'm under the impression i cannot go back to anything before 5.6.1 at this point.
i can get into => Fastboot mode....can i do anything with that to reinstall a different OS and go back to 4.5.3 or something rootable? if i can undo this 5.6.1 flash i would.
or do you know if through the ADB command console i can uninstall the supersu installer? it does not allow me to install within the apps menu. i read somewhere that it is because it is considered a system program the way i installed it. i tried downloading the UPDATE-unSU-signed.zip supersu uninstaller fix, but have no way to open the zip within the kindle.
i just want to take it back to full rooted, or full oem and not some messed up thing in between.
doobius said:
thank you for the replies Rortiz2. i am going to stop tinkering and ask for advice here before i make things worse.
so with this tool, i am able to debloat, but must retain the updated OS (5.6.1)? i'm under the impression i cannot go back to anything before 5.6.1 at this point.
i can get into => Fastboot mode....can i do anything with that to reinstall a different OS and go back to 4.5.3 or something rootable? if i can undo this 5.6.1 flash i would.
or do you know if through the ADB command console i can uninstall the supersu installer? it does not allow me to install within the apps menu. i read somewhere that it is because it is considered a system program the way i installed it. i tried downloading the UPDATE-unSU-signed.zip supersu uninstaller fix, but have no way to open the zip within the kindle.
i just want to take it back to full rooted, or full oem and not some messed up thing in between.
Click to expand...
Click to collapse
Ok before trying nothing, maybe you have a chance of life and SuperSU has injected the binaries. Try installing SuperSU.apk from google and open it. If it asks for update binaries you have root and you can downgrade!
Rortiz2 said:
Ok before trying nothing, maybe you have a chance of life and SuperSU has injected the binaries. Try installing SuperSU.apk from google and open it. If it asks for update binaries you have root and you can downgrade!
Click to expand...
Click to collapse
i tried manually installing supersu.apk via adb, but when i do that, it says the install failed because it is already on the device. but it is just the installer. when i open the installer, it asks me to try and download via play, but it is no longer available, and the other option is via twrp. it downloads a file, and restarts, but nothing happens. it just starts as normal. i installed kingroot again, and it fails trying to root it since 5.6.1.
doobius said:
i tried manually installing supersu.apk via adb, but when i do that, it says the install failed because it is already on the device. but it is just the installer. when i open the installer, it asks me to try and download via play, but it is no longer available, and the other option is via twrp. it downloads a file, and restarts, but nothing happens. it just starts as normal. i installed kingroot again, and it fails trying to root it since 5.6.1.
Click to expand...
Click to collapse
Ok so try this:
Open a cmd and type:
Code:
adb shell
and then
Code:
su
what's the output of "su"?
Rortiz2 said:
Ok so try this:
Open a cmd and type:
Code:
adb shell
and then
Code:
su
what's the output of "su"?
Click to expand...
Click to collapse
PS \ADB\platform-tools_r29.0.1-windows\platform-tools> .\adb shell
[email protected]:/ $ su
1|[email protected]:/ $
this is what happens when i try to install supersu.apk manually. and the only reason i was trying to install it was so that i could remove it hah.
PS ADB\platform-tools_r29.0.1-windows\platform-tools> .\adb install supersu.apk
Performing Push Install
supersu.apk: 1 file pushed. 3.9 MB/s (6258692 bytes in 1.534s)
pkg: /data/local/tmp/supersu.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
PS ADB\platform-tools_r29.0.1-windows\platform-tools>
doobius said:
this is what happens when i try to install supersu.apk manually. and the only reason i was trying to install it was so that i could remove it hah.
PS ADB\platform-tools_r29.0.1-windows\platform-tools> .\adb install supersu.apk
Performing Push Install
supersu.apk: 1 file pushed. 3.9 MB/s (6258692 bytes in 1.534s)
pkg: /data/local/tmp/supersu.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
PS ADB\platform-tools_r29.0.1-windows\platform-tools>
Click to expand...
Click to collapse
You have the f**** root. The problem is that there's no prompt... Maybe, changing SuperSU package name helps?
Rortiz2 said:
You have the f**** root. The problem is that there's no prompt... Maybe, changing SuperSU package name helps?
Click to expand...
Click to collapse
good idea. but that failed too.
doobius said:
good idea. but that failed too.
Click to expand...
Click to collapse
So then try installing google play as in Fire 7 2015/2017.
You have two methods:
- Manual: https://forum.xda-developers.com/amazon-fire/general/how-to-install-google-play-store-fire-t3486603
- Automated tool: https://forum.xda-developers.com/amazon-fire/general/tool-amazon-fire-7-7gen-fire-os-5-6-x-t3815112
(Use install google play option).
When you logged in and setup it correctly, proceed to update supersu installer tought Play Store.
ok sir, you are on to something...
i downloaded the playstore stuff via that link you sent.
i logged in to playstore and went back to the supersu installer i already had.
i clicked play.
it took me to the same playstore suspersu program and it says it is currently unavailable.
i searched supersu and found the main updated download.
i hit open and it took me back to the installer i already have.
i went back and noticed the update option in the playstore and selected that.
it updated and is now saying that the su binary needs to be updated and is asking me to continue.
awaiting your godlike instructions.
the next screen says, "if you have a custom recovery like twrp or cwm, that can be used to (try to) install the SU binary. this is recommended for HTC devices. how would you like to install the SU binary.
normal or twrp/cwm?"
normal, right?
and now if i try the su command under adb shell, i get a popup on the kindle asking me to grant superuser request for access. are these good things?
doobius said:
and now if i try the su command under adb shell, i get a popup on the kindle asking me to grant superuser request for access. are these good things?
Click to expand...
Click to collapse
Yay!! You have root!! Now that you have root. I will recommend you to flash a working recovery.
Pinging some people that may help creating the stock recovery: @k4y0z @bibikalka
ok. what is the best method to roll back to a previous OS then? should i use that fire toolbox 5.1 and try the root process there? i just don't want to mess it up again. like i said, i either want it to look like i never touched it and go back to 100% amazon factory....or keep it rootable/rooted with an old OS and just lock the OTA updates from ever updating it.
to be honest, what i had tried to do was set it up so i could use the gps spoofer on an app. but the app doesn't like the old OS i was on. and i don't think i can do the spoofing/gps manipulation with an old OS because i don't have the ability to choose an app for fake location.
doobius said:
ok. what is the best method to roll back to a previous OS then? should i use that fire toolbox 5.1 and try the root process there? i just don't want to mess it up again. like i said, i either want it to look like i never touched it and go back to 100% amazon factory....or keep it rootable/rooted with an old OS and just lock the OTA updates from ever updating it.
to be honest, what i had tried to do was set it up so i could use the gps spoofer on an app. but the app doesn't like the old OS i was on. and i don't think i can do the spoofing/gps manipulation with an old OS because i don't have the ability to choose an app for fake location.
Click to expand...
Click to collapse
Ok. DON'T DO ANYTHING UNTIL YOU RESTORE WORKING RECOVERY.
First we need to create a working recovery image. Can you check if there's install-recovery.sh in system/etc and in system/bin please?
i dont see that, but i'm probably not looking in the right spot then. how do you suggest i check for this?