I've done quite a bit of searching over the past couple days but can't quite seem to find what I'm looking for.
I'm trying to root my Azpen A700 tablet manually. I've managed to load ChainsDD's Superuser.apk and su binary to the device in the appropriate locations. I've run all the chmods on them and can use ChainsDD's su binary when I run adb shell. I know I did this backward, but I'm really just playing with this thing, flying somewhat blind, and I don't much care if I brick it, so sue me.
So I tried to run 'fastboot oem unlock' just to see what it would do/if it would work. I loaded the latest ADB Composite Driver. I think the problem is that I can't get this POS to boot into the bootloader. It only wants to boot into recovery. If I run 'adb reboot-bootloader' or 'adb reboot bootloader' it always boots up into Android. I've tried using every volume/power button combo I can think of, and no dice. I really have no idea if the bootloader can even be unlocked. Does anyone have any ideas as to how to make this work?
By the way, I also tried SuperOneClick. It warned me that my device was already rooted, I'm guessing because it knows the su binary, and asked me if I wanted to root it anyway. I said Yes, and got the "failed to set prot mask" error on Step 4.
LeonardHatred said:
I've done quite a bit of searching over the past couple days but can't quite seem to find what I'm looking for.
I'm trying to root my Azpen A700 tablet manually. I've managed to load ChainsDD's Superuser.apk and su binary to the device in the appropriate locations. I've run all the chmods on them and can use ChainsDD's su binary when I run adb shell. I know I did this backward, but I'm really just playing with this thing, flying somewhat blind, and I don't much care if I brick it, so sue me.
So I tried to run 'fastboot oem unlock' just to see what it would do/if it would work. I loaded the latest ADB Composite Driver. I think the problem is that I can't get this POS to boot into the bootloader. It only wants to boot into recovery. If I run 'adb reboot-bootloader' or 'adb reboot bootloader' it always boots up into Android. I've tried using every volume/power button combo I can think of, and no dice. I really have no idea if the bootloader can even be unlocked. Does anyone have any ideas as to how to make this work?
By the way, I also tried SuperOneClick. It warned me that my device was already rooted, I'm guessing because it knows the su binary, and asked me if I wanted to root it anyway. I said Yes, and got the "failed to set prot mask" error on Step 4.
Click to expand...
Click to collapse
Why do you think you need to get into the bootloader? The device already has root access through ADB. Just open an ADB shell and replace the su binary with one that doesn't restrict user gaining root.
BLuFeNiX said:
Why do you think you need to get into the bootloader? The device already has root access through ADB. Just open an ADB shell and replace the su binary with one that doesn't restrict user gaining root.
Click to expand...
Click to collapse
Well, that's what I thought I did. I have the ChainsDD su binary in /system/xbin with a symlink, /system/bin/su, that points to it. I ran 'chmod 06755 /system/xbin/su' on it so the setuid and setgid are applied, just like the stock su binary. But if I run Titanium Backup, it says it can't get root through /system/bin/su. And if I run su through a Terminal Emulator on the device, I get an error "explosion" of permissions errors. Is there another su binary I should be using instead? Or maybe there's something that Superuser.apk needs to do that I'm missing?
I guess the reason I'm trying to get into the bootloader is so I can unlock it and try rooting the easy way, to see what's different from what I've done so far. I didn't really understand why I needed to get into the bootloader if I was so easily able to replace the su binary, but I figured maybe there was something that needed to be done with file permissions that couldn't be done if, say, /system was mounted, or something like that. Does that idea hold any water?
Maybe using the su binary I have I can modify permissions on files where needed?
Thanks for the help!
LeonardHatred said:
Well, that's what I thought I did. I have the ChainsDD su binary in /system/xbin with a symlink, /system/bin/su, that points to it. I ran 'chmod 06755 /system/xbin/su' on it so the setuid and setgid are applied, just like the stock su binary. But if I run Titanium Backup, it says it can't get root through /system/bin/su. And if I run su through a Terminal Emulator on the device, I get an error "explosion" of permissions errors. Is there another su binary I should be using instead? Or maybe there's something that Superuser.apk needs to do that I'm missing?
I guess the reason I'm trying to get into the bootloader is so I can unlock it and try rooting the easy way, to see what's different from what I've done so far. I didn't really understand why I needed to get into the bootloader if I was so easily able to replace the su binary, but I figured maybe there was something that needed to be done with file permissions that couldn't be done if, say, /system was mounted, or something like that. Does that idea hold any water?
Maybe using the su binary I have I can modify permissions on files where needed?
Thanks for the help!
Click to expand...
Click to collapse
Do it again, but us the su binary found here: https://plus.google.com/103583939320326217147/posts/4FemP5ACLSn
BLuFeNiX said:
Do it again, but us the su binary found here:
Click to expand...
Click to collapse
That did it, thanks!
Maybe now I'll root my Nexus 4 this way...
LeonardHatred said:
That did it, thanks!
Maybe now I'll root my Nexus 4 this way...
Click to expand...
Click to collapse
No problem.
Related
So, after learning that Motorola was not going to give us a software update for the Atrix 4G, I decided to take a chance and unlock the bootloader and flash a custom rom. I flashed CyanogenMod 7 Olympus (cm-7-20120923-NIGHTLY-olympus) and I love it! I made a backup of the stock rom and then a backup of CM7 after I had it set up the way I like it for the most part.
My only problem: I lose root access randomly... without rebooting... without doing anything! SU is there, and the superuser apk is there, and they come up as granting superuser permission, but the apps say they don't have access. Even trying to update the binary says "failed" when gaining root access.
I've been scouring forums and the net looking for similar problems. Rebooting doesn't fix it. I've tried downloading and flashing SU 3.1.3 from recovery (wipe cache & dalvik cache, then install from zip), and that didn't work. I then tried the same for 3.2-RC3, and no luck there. I've ran Fix Permissions just to try, and that did not work either. Somewhere, someone posted to reflash the ROM. Instead, I just restored a backup, and it comes back for a few days... then it stops working again.
Any suggestions on how to fix this or what could cause it? I don't mind restoring the backup again, but I'd like to keep it from happening if at all possible.
twomoses said:
So, after learning that Motorola was not going to give us a software update for the Atrix 4G, I decided to take a chance and unlock the bootloader and flash a custom rom. I flashed CyanogenMod 7 Olympus (cm-7-20120923-NIGHTLY-olympus) and I love it! I made a backup of the stock rom and then a backup of CM7 after I had it set up the way I like it for the most part.
My only problem: I lose root access randomly... without rebooting... without doing anything! SU is there, and the superuser apk is there, and they come up as granting superuser permission, but the apps say they don't have access. Even trying to update the binary says "failed" when gaining root access.
I've been scouring forums and the net looking for similar problems. Rebooting doesn't fix it. I've tried downloading and flashing SU 3.1.3 from recovery (wipe cache & dalvik cache, then install from zip), and that didn't work. I then tried the same for 3.2-RC3, and no luck there. I've ran Fix Permissions just to try, and that did not work either. Somewhere, someone posted to reflash the ROM. Instead, I just restored a backup, and it comes back for a few days... then it stops working again.
Any suggestions on how to fix this or what could cause it? I don't mind restoring the backup again, but I'd like to keep it from happening if at all possible.
Click to expand...
Click to collapse
Try going in to Manage Applications and clear su data. If that doesn't work go to the Play Store and Install Superuser Update Fixer.
upndwn4par said:
Try going in to Manage Applications and clear su data. If that doesn't work go to the Play Store and Install Superuser Update Fixer.
Click to expand...
Click to collapse
Thanks for the quick reply. I cleared the cache for Superuser (couldn't believe I didn't think to do that in the first place), and now it will not prompt to grant or deny. I try to update the binary, and it stops at "Gaining root access..." and doesn't show okay or failed. I tried to run the Superuser Update Fixer, and it says that the signatures are okay. When I try to force it, it does the exact same thing as Superuser: it hangs at "Gaining root access..."
It may be worth noting that I have to force-close Superuser the first time I open it after clearing cache. After that, it opens but only does the above mentioned.
twomoses said:
Thanks for the quick reply. I cleared the cache for Superuser (couldn't believe I didn't think to do that in the first place), and now it will not prompt to grant or deny. I try to update the binary, and it stops at "Gaining root access..." and doesn't show okay or failed. I tried to run the Superuser Update Fixer, and it says that the signatures are okay. When I try to force it, it does the exact same thing as Superuser: it hangs at "Gaining root access..."
It may be worth noting that I have to force-close Superuser the first time I open it after clearing cache. After that, it opens but only does the above mentioned.
Click to expand...
Click to collapse
Open a terminal emulator and type su and hit enter. If you don't see #, you are not properly rooted.
upndwn4par said:
Open a terminal emulator and type su and hit enter. If you don't see #, you are not properly rooted.
Click to expand...
Click to collapse
Nothing happens in terminal emulator.
Now my question is, (and forgive my n00bness) since CM7 came rooted, do I follow the normal steps to re-root the phone through adb? I've never seen how to root a custom rom, but that may be because the process is exactly the same.
twomoses said:
Nothing happens in terminal emulator.
Now my question is, (and forgive my n00bness) since CM7 came rooted, do I follow the normal steps to re-root the phone through adb? I've never seen how to root a custom rom, but that may be because the process is exactly the same.
Click to expand...
Click to collapse
Nothing happens? No error ("not found" or "permission denied" or something like that)?
Go to the Play Store and download Root Checker, and check for root with that also.
I don't know the answer to your question since most users root, unlock, then flash a ROM. If it were me, I would try to root as if it were GB 236.
upndwn4par said:
Nothing happens? No error ("not found" or "permission denied" or something like that)?
Go to the Play Store and download Root Checker, and check for root with that also.
Click to expand...
Click to collapse
That is correct. I ended up having to kill the terminal emulator too. It just sits there with nothing displaying.
I ran root checker, and all I get is the loading circle in the middle that says "Please wait for Root Check to complete. System appears to be running very slow." Nothing else was running slow, so I rebooted my phone again.
I don't know what changed, but now I have root again! Many thanks upndwn4par!
My guess is clearing data in Manage Applications did the trick. Anyway, glad it is working!
Another method for checking if you are rooted properly.
EDIT: nevermind, now I see it's been discussed already. :stupid:
Off topic: I seriously want to borrow your signatures tho!
have you disabled debugging in developement settings? if you do so, SU does not work any more, or the be more precisely: You won't be able to see the "Allow"-dialog...
Sabbelknoken said:
have you disabled debugging in developement settings? if you do so, SU does not work any more, or the be more precisely: You won't be able to see the "Allow"-dialog...
Click to expand...
Click to collapse
USB Debugging stays on usually because I don't connect my phone to a computer I don't know.
When this started, I was still getting the toast messages saying access granted, but it wasn't actually working. Somewhere along the line of steps it started working again tho.
twomoses said:
Off topic: I seriously want to borrow your signatures tho!
Click to expand...
Click to collapse
Absolutely!
upndwn4par said:
Absolutely!
Click to expand...
Click to collapse
Done!
Solved: This fixed my problem!
Sabbelknoken said:
have you disabled debugging in developement settings? if you do so, SU does not work any more, or the be more precisely: You won't be able to see the "Allow"-dialog...
Click to expand...
Click to collapse
So, props to you Sabbelknoken! I suddenly lost root again the same way I had before. I came back through this thread to revisit my steps, and I found that my USB Debugging was off. (I think I turned it off so one of my computers would stop asking me for the drivers. Not important.) I turned it on and it immediately began working!
Just wanted to concur...
Thanks to Sabbelknoken!! I had this same problem with my Droid Charge running Tweaked 3.0. Nothing was getting root and everything was hanging on "Gaining root access..." I tried SuperSU, re-installing Titanium Backup, Superuser, SuperSU, Superuser Update Fixer, Root checker, I cleared data, rebooted several times...over and over.
Then sure enough, my dang "USB Debugging" was not checked. Checked it, and now I'm happily rooting again. *whew* Thought I was going to have to re-Odin my ROM. Ick.
Thank again everyone!
su losing root usb debug etc
I too get su issues from time to time. mostly with stock roms when i flash a fruitcake or gingerbread. and recently one of the leak roms. just type d su in terminal emulator an got $ instead of #. I hope that means im properly rooted . I have a couple of one click root apps on my computers just incase i need to reroot. one is superoneclick 2.33 shortfuse and the other is motofail. then i make sure to install busybox and upate the binary. i also have su update fixer, superuser elite, and supersu. as well as rootchecker.
two thing I did not know were that 1. usb debugging is not just for transferring files or connecting to the computer. I used to turn it off sometimes and then wonder why superuser had problems. 2. how to see you are rooted by typing su in terminal.
From what i understand the one click methods are not ideal as they do not always work. but I usually try them first . If they are outated and dont work i end up rooting by command prompt. some times it woul take me cloose to an hour trying different things. never knew it was usb debugging turned off that causes most root failures. Did some reading and realized that if i allow su permission for terminal emulator, then type su again i get#. good to know.
activate USB debugging
Sabbelknoken said:
have you disabled debugging in developement settings? if you do so, SU does not work any more, or the be more precisely: You won't be able to see the "Allow"-dialog...
Click to expand...
Click to collapse
Thanks for that simple tip. I was having the same problem, the "Allow" dialog didn't appear for any application request and Root Checker was only saying: "Device seems to be running really slow"
I was 2 or 3 days looking for the solution to this problem, because it is my first time rooting and I can't believe something as simple as activating USB debugging is not really explained in the rooting guide I used.
I hope that now Titanium and ROM Toolbox Pro work properly.
Hi, sorry I have really tried before asking, I am at a complete loss as to what to do.
I have used HTC Desire X All-In-One Toolkit V2.0 [1-1-2013] from http://forum.xda-developers.com/showthread.php?t=1943822
I unlocked the bootloader, and the boot menu shows the phone as 'unlocked'.
I then tried running permroot, which installed superuser, but when I try to check if my phone is rooted, (Using droidwall : I am trying to enable the firewall).
I get the message that I need a rooted phone to run droidwall .
and 'if this phone is already rooted make sure droidwall has enough permissions to execute the 'su' command'.
How do I know if my phone is rooted?
Thanks - this has been most frustrating, my backspace key has also bombed out. haha
Hello,
Try this app: https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en download it from the store and run it it will say is your phone rooted or not.
Bensmom said:
How do I know if my phone is rooted?
Click to expand...
Click to collapse
You should have a su binary residing in /system/bin/ and some sort of control app in your app drawer (probably Superuser). If you don't have these then you aren't rooted.
If you have them, an easy way to test is to use a terminal app , type 'su' and the control app should pop up asking if you want to give root privileges to terminal.
If you are having trouble getting root to work using the toolkit, try doing it manually by following nloooo's tutorial.
Ok, you all forgot about flashing recovery first.
HI,
I am unable to mount /system as r/w in root explorer or other apps. When they load it asks SpuerSU for permissions which are granted.
I am trying to install xposed installer which fails and asks (are you root?)
I originally rooted my Z2 when it was first released, then when the 4.4.4 update became available in the UK i restored stock recovery so i could update. When the Phone rebooted I found I still had root. I can get a # prompt in terminal emulator and apps like folder mount work fine.
Has something messed up somewhere? I tried reinstalling SuperSU to no avail.
Thanks
stubbadub said:
HI,
I am unable to mount /system as r/w in root explorer or other apps. When they load it asks SpuerSU for permissions which are granted.
I am trying to install xposed installer which fails and asks (are you root?)
I originally rooted my Z2 when it was first released, then when the 4.4.4 update became available in the UK i restored stock recovery so i could update. When the Phone rebooted I found I still had root. I can get a # prompt in terminal emulator and apps like folder mount work fine.
Has something messed up somewhere? I tried reinstalling SuperSU to no avail.
Thanks
Click to expand...
Click to collapse
Have you tried to downgrade to 4.4.3 and make a rooted flashable zip with 4.4.4??
Might work. Havent tried Root explorer, cuz FileCommander works fine with root...
bjorn96 said:
Have you tried to downgrade to 4.4.3 and make a rooted flashable zip with 4.4.4??
Might work. Havent tried Root explorer, cuz FileCommander works fine with root...
Click to expand...
Click to collapse
I have just run the Easyroot Tool again and this seems to have solved it. :good:
stubbadub said:
I have just run the Easyroot Tool again and this seems to have solved it. :good:
Click to expand...
Click to collapse
Hi stubbadub.......so what you are saying is that if you already have root, after the upgrade to 4.4.4 run the Easyroot Tool (Towelroot) and your root will be back to how it was.
I have just bought a Z2, selling my (stock but rooted) ZR to my sister. I rooted it, it did an OTA, I ran the tool again just be on the safe side, all good. Now I'm being prompted to run the .267 OTA update, I'm not sure whether I should hang on for a while or just go for it. I don't want to lose the advanced DRM only features of the phone like noise cancelling/high res camera so unlocking the bootloader is not an option for me (although I have backed up the TA partition anyway).
Cheers
stonegroover said:
Hi stubbadub.......so what you are saying is that if you already have root, after the upgrade to 4.4.4 run the Easyroot Tool (Towelroot) and your root will be back to how it was.
I have just bought a Z2, selling my (stock but rooted) ZR to my sister. I rooted it, it did an OTA, I ran the tool again just be on the safe side, all good. Now I'm being prompted to run the .267 OTA update, I'm not sure whether I should hang on for a while or just go for it. I don't want to lose the advanced DRM only features of the phone like noise cancelling/high res camera so unlocking the bootloader is not an option for me (although I have backed up the TA partition anyway).
Cheers
Click to expand...
Click to collapse
My bootloader came unlocked on the phone. I bought the phone when it was released. I rooted and when 4.4.4 firmware was released it initially failed to update OTA. I had to remove the dual recovery. The OTA then worked fine and i still had root. However i could not mount the /system folder as R/W/. I just ran easyroot again and this solved it.
stonegroover said:
Hi stubbadub.......so what you are saying is that if you already have root, after the upgrade to 4.4.4 run the Easyroot Tool (Towelroot) and your root will be back to how it was.
I have just bought a Z2, selling my (stock but rooted) ZR to my sister. I rooted it, it did an OTA, I ran the tool again just be on the safe side, all good. Now I'm being prompted to run the .267 OTA update, I'm not sure whether I should hang on for a while or just go for it. I don't want to lose the advanced DRM only features of the phone like noise cancelling/high res camera so unlocking the bootloader is not an option for me (although I have backed up the TA partition anyway).
Cheers
Click to expand...
Click to collapse
NC not working happened to me too. But only in niaboc79's version (and by this I mean the Russian OTA). I also tried the OTA and all was good. But after that I lost my root and tried to restore it (I ran the restore-mount script). This script messed things up. Instead of looking into that, I tried different approaches (niaboc79's / .314+root+script) except check if it was because of the the script .
If you have root now, install the dualrecovery and dirty flash for example shockss pre-rooted .267 and run the script. Stock .267, everything working but pre-rooted. Ow and 4G icon = LTE icon.
stubbadub said:
I have just run the Easyroot Tool again and this seems to have solved it. :good:
Click to expand...
Click to collapse
Thank you, this method worked for me too !
Actually I couldn't run the whole Easyroot tool (got stuck at creating vm) so I just ran the important part which is where it pushes files/installmount.sh with
Code:
adb push files/installmount.sh /data/local/tmp
And then executes it with
Code:
adb shell "su -c /data/local/tmp/installmount.sh"
pec0ra said:
Thank you, this method worked for me too !
Actually I couldn't run the whole Easyroot tool (got stuck at creating vm) so I just ran the important part which is where it pushes files/installmount.sh with
Code:
adb push files/installmount.sh /data/local/tmp
And then executes it with
Code:
adb shell "su -c /data/local/tmp/installmount.sh"
Click to expand...
Click to collapse
Mine sticks at creating the VM too. So the code you've quoted is all you need? I opened up the .bat file to have a look and those lines of code are only 2 of many, and only around half way through the file- I'm looking at it thinking there's got to be more to it than that, it can't be that simple......
stonegroover said:
Mine sticks at creating the VM too. So the code you've quoted is all you need? I opened up the .bat file to have a look and those lines of code are only 2 of many, and only around half way through the file- I'm looking at it thinking there's got to be more to it than that, it can't be that simple......
Click to expand...
Click to collapse
If you only want to fix the system not mounting then yes, it's only this. The rest of the script is an exploit to gain root and install su but you don't need it since you already have it.
If you are looking for a full root method these two lines are not enough. In this case I suggest you try another rooting tool.
pec0ra said:
If you only want to fix the system not mounting then yes, it's only this. The rest of the script is an exploit to gain root and install su but you don't need it since you already have it.
If you are looking for a full root method these two lines are not enough. In this case I suggest you try another rooting tool.
Click to expand...
Click to collapse
I still have 'some root', my Adaway still works but it won't load new/updated hosts, BusyBoxPro won't install, etc. I tried what you did, just ran the two lines of code but it said I didn't have permission when I tried to run the second line. Did you get that error? If you did, how did you get past that?
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.
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?