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?
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.
I already posted about this...
I still can't get root perms to work correctly. Super SU is installed. binary update fails even though superuser claims to have an updated binary named 098:SuperSU (i assume this means it is pointing to supersu. super su has superuser disabled, and whenever something asks for permissions the phone reboots.
I finally got root to work, but now some apps when requesting root re-boots my phone.
it's pissing me off lmao, I can't stand it I've looked everywhere for answers and no one has the same problem. i can install any mod or kernel but superSU is messed up lol just doesn't make sense.
theguitarhero94 said:
I already posted about this...
I still can't get root perms to work correctly. Super SU is installed. binary update fails even though superuser claims to have an updated binary named 098:SuperSU (i assume this means it is pointing to supersu. super su has superuser disabled, and whenever something asks for permissions the phone reboots.
Click to expand...
Click to collapse
When I was rooting my phone (both my original and my replacement), I flashed SuperSU and did a root check through Root Checker. And on both of the phones, it didn't work out, so i Opened up SuperSU and i got the same message as you (Need to Update, and Failed to Update).
On my first phone, i just flashed Superuser (which works fine for me, no problems yet) and i didn't use/got rid of SuperSU.
On my replacement phone (Current), i Flashed SuperSU and got the same error, so i goggled a little bit and found this (http://forum.xda-developers.com/showpost.php?p=31887507&postcount=1). I didn't try it out, because i just ended up flashing Superuser again and it has worked every since.
I was having the same thing yesterday. Then I re-flashed and when I ran SuperSU and tried to update binaries it immediately rebooted. But then programs could get root again. Now every time I go into SuperSU it wants to update the binary and if I say yes it reboots. I downloaded Superuser from the Market and ran the update su binary from there, it was successful but same results when I go back into SuperSU. I guess as long as programs can keep root permissions it's fine. Anyone else seeing this?
In regard to all fo the problems below:
theguitarhero94 said:
I already posted about this...
I still can't get root perms to work correctly. Super SU is installed. binary update fails even though superuser claims to have an updated binary named 098:SuperSU (i assume this means it is pointing to supersu. super su has superuser disabled, and whenever something asks for permissions the phone reboots.
Click to expand...
Click to collapse
wowens0822 said:
I finally got root to work, but now some apps when requesting root re-boots my phone.
Click to expand...
Click to collapse
theguitarhero94 said:
it's pissing me off lmao, I can't stand it I've looked everywhere for answers and no one has the same problem. i can install any mod or kernel but superSU is messed up lol just doesn't make sense.
Click to expand...
Click to collapse
BigRed35m said:
When I was rooting my phone (both my original and my replacement), I flashed SuperSU and did a root check through Root Checker. And on both of the phones, it didn't work out, so i Opened up SuperSU and i got the same message as you (Need to Update, and Failed to Update).
On my first phone, i just flashed Superuser (which works fine for me, no problems yet) and i didn't use/got rid of SuperSU.
On my replacement phone (Current), i Flashed SuperSU and got the same error, so i goggled a little bit and found this (http://forum.xda-developers.com/showpost.php?p=31887507&postcount=1). I didn't try it out, because i just ended up flashing Superuser again and it has worked every since.
Click to expand...
Click to collapse
eddiecanuck said:
I was having the same thing yesterday. Then I re-flashed and when I ran SuperSU and tried to update binaries it immediately rebooted. But then programs could get root again. Now every time I go into SuperSU it wants to update the binary and if I say yes it reboots. I downloaded Superuser from the Market and ran the update su binary from there, it was successful but same results when I go back into SuperSU. I guess as long as programs can keep root permissions it's fine. Anyone else seeing this?
Click to expand...
Click to collapse
Listen up guys I'm assuming most of you are bone stock and freshly unlocked the problem is the SuperSU APP it is stated in the OP for the unlock method and most of the root threads around here that currently the binaries we have for supersu that is flashed in recovery during the root process are not compatible with the SuperSU APP from the market. Downloading "superuser" from the market will fix all of your problems.
download this > https://play.google.com/store/apps/details?id=com.noshufou.android.su&feature=nav_result#?t=W10.
Until further notice this will be necessary. There are some people that have hacked in different binaries for their updates/roms just make sure you read OP's first before tryingto switch back to the SuperSU app.
Thanks for that info. I did install Superuser from the market. But when the device was in a state where programs were not getting root access, I couldn't do anything with it (update binaries, manage app permissions, etc). Since SuperSU keeps rebooting me, I can't change any settings like having Superuser manage program access. Then I re-flashed the supersu zip in recovery and apps had root permissions, then I was able to run Superuser to update the binary (maybe that was a mistake?). But programs were still asking SuperSU for rights, and since I can't get into SuperSU as it is still rebooting I'm kind of in this loop. It's not a huge deal at the moment as I don't really have anything else I need it for. So I guess I'll just wait until the supersu that is flashed is compatible with the SuperSU app.
eddiecanuck said:
Thanks for that info. I did install Superuser from the market. But when the device was in a state where programs were not getting root access, I couldn't do anything with it (update binaries, manage app permissions, etc). Since SuperSU keeps rebooting me, I can't change any settings like having Superuser manage program access. Then I re-flashed the supersu zip in recovery and apps had root permissions, then I was able to run Superuser to update the binary (maybe that was a mistake?). But programs were still asking SuperSU for rights, and since I can't get into SuperSU as it is still rebooting I'm kind of in this loop. It's not a huge deal at the moment as I don't really have anything else I need it for. So I guess I'll just wait until the supersu that is flashed is compatible with the SuperSU app.
Click to expand...
Click to collapse
Did you make a NAND b4 supersu app installed? Revert if so if not i recommend UKB in the development sections its a solid rom right now with lots of options. I'd say fix it now so it doesnt bite you later. Also you could try freezing in tibu then using tibu to uninstall SuperSU that is.
I did an uninstall updates for SuperSU to get it back to what was flashed, and I can uninstall Superuser. Haven't done a NAND yet but will. Looking at UKB, was going to stay stock for a while but after looking at that I probably won't.
Most likely flash it tonight, has some nice features. Thanks again for the input.
I have been trying to root my HTC EVO 4G LTE for days now without any luck. I have an unlocked bootloader. That was pretty easy. I originally tried the "Kingo Android Root" which unlocked the bootloader and claimed that it had rooted my phone. However, I did not have superuser privileges. I re-ran the "Kingo Anroid Root" several times. Each time it said I was rooted, yet every time I checked I was not. So, I came to the conclusion that the EVO 4G LTE was incompatible with the "Kingo" method.
So, I moved on to methods more specific to the EVO 4G LTE. I tried WinDroid, which flashed TWRP recovery and I then booted to that. However, when I installed superuser.zip, it said successful even though rebooting my phone once again left me without superuser privileges. I retried flashing superuser.zip multiple times, yet each time it failed to give me superuser access. It was around this time I noticed that while my bootloader reads "Tampered" and "Unlocked", I still have S-ON rather than S-OFF. Could this be preventing superuser.zip from giving me superuser access? I tried rumrunner to get S-OFF but that failed halfway through. Yes, I have installed both HTC and ADB drivers.
Honestly, this has just been a nightmare. I thought it would be a simple and relatively painless process, but it has become a multiple day affair that is consuming way too much of my time. I am about to either just pay someone to do this for me or give up entirely. So, any help is appreciated. Thanks in advance.
Hit up the link below and download the latest version of SuperSU, then flash in recovery. As far as the tampered warning in the bootloader, that's normal when you've unlocked the bootloader. As far as S-off goes, post your Hboot and radio (firmware) version, as that will determine which method you need to use to gain S-off.
http://forum.xda-developers.com/showthread.php?t=1538053
Also make sure that you have your superuser rights set to "ask" in the SuperSU app.
Well, I downloaded the new SuperSU.zip you posted and I rebooted to recovery. I installed it and TWRP said the install was successful. I then chose to reboot system. By the way, I don't think I mentioned this in my OP, but after the "Success Screen" and choosing to reboot I am prompted with a screen that says "No OS installed! Are you sure you want to reboot?" to which I say yes and then continue to another screen that asks if I want to "Install SuperSU. This will root your device." I swipe yes to tell it to install SuperSU even though I just installed it. Then, it kind of just sits there until rebooting normally. Just letting you know in case this changes anything. Should I try it again and choose to not install the second SuperSU? Could it be overwriting the updated one I flashed a few seconds prior?
Anyways, as you can probably guess by the nature of my disorganized post's first paragraph, the updated SuperSU did not root the phone as there is still no sign of the SuperSU app, nor any indication that I am rooted such as being able to delete the annoying bloatware installed. Any other suggestions?
Oh, and for the information you need for the S-ON problem:
HBOOT-2.09.0000
RADIO-1.13.11.0830
Magnum_Enforcer said:
Also make sure that you have your superuser rights set to "ask" in the SuperSU app.
Click to expand...
Click to collapse
Okay, but I don't currently see the SuperSU app. Isn't that supposed to come from the root or do you have to download that off the play store? I assume this post was for if updated SuperSU zip file worked.
Install the SuperSU app from the Play store, then check the permissions I previously mentioned. Also, the Rumrunner method should work fine but you can also try the Firewater method. Try Rumrunner a few times first, though.
Installing the SuperSU app off the play store and then running it only gives me a prompt that says, "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
Any ideas on how to fix this?
Install the SuperSU zip in recovery again. Then reboot.
Magnum_Enforcer said:
Install the SuperSU zip in recovery again. Then reboot.
Click to expand...
Click to collapse
Okay, I tried it again, but it isn't installing. I flash the UPDATE-SuperSU-2.02.zip file and then reboot. Then I go to the SuperSU app that I got off the Play store and it still brings up the same prompt followed by the app closing. Any ideas why the SuperSU.zip won't flash in TWRP?
M3TLGMR said:
Okay, I tried it again, but it isn't installing. I flash the UPDATE-SuperSU-2.02.zip file and then reboot. Then I go to the SuperSU app that I got off the Play store and it still brings up the same prompt followed by the app closing. Any ideas why the SuperSU.zip won't flash in TWRP?
Click to expand...
Click to collapse
Try an older version like 1.94.
Okay, I tried the 1.94 version. Same result as all the other versions of SuperSU I have tried.
I did notice something odd that somehow slipped past me. I copied the zip file to my root directory on my PC, yet when I launch into TWRP I find the file in the "/data" directory. Could this be the problem? That the zip files aren't in the root when in TWRP? Anyway, can I move the files up a level while in recovery? Because the files are in the root directory of my phone when I copy them on my PC. They aren't in the "data" folder...
Not sure what to tell you at this point. The location of the zip file shouldn't matter, though. Putting it on the root of your internal or external storage makes it easier to flash when it comes time to install, but it can be flashed even if it's in a folder somewhere. I'd suggest making sure that you have the latest version of TWRP on your phone (2.7.1.0) and starting over with a clean install of a rooted ROM, like MeanBean, since it is fairly easy to install while still being S-on. Link can be found below:
http://forum.xda-developers.com/showthread.php?t=2048229
I was having a similar issue to this a week ago. What is TWRP showing when you flash the file?
Hello, I have a Fire HD6 Running Fire OS 5.0.0. I am trying to use the file for 5.2.2u2 to update. When I go to settings>>device options>>system updates>>check now, it says there are no updates. If I put the file at /sdcard using a computer and turn on airplane mode, I can hit the update button and it looks like it is going to update, but when it reboots, it says i am still on 5.0.0. ADB works, but adb reboot recovery just boots normally. I had TWRP until I updated to 5.0.0. I really need help. Thanks in advance.
See if you can push file to /cache. It should upgrade from there. If you are (or once were) rooted, first reverse any pm commands you did to block OTA (pm enable com.amazon.dcp and/or pm enable com.amazon.otaverifier). If commands fail, use gatesjr Debloater tool (from here on xda) to make sure packages are enabled. Since the upgrade will break root anyway, you may be able to get OTA upgrade by turning on wifi and doing "check now."
DoLooper said:
See if you can push file to /cache. It should upgrade from there. If you are (or once were) rooted, first reverse any pm commands you did to block OTA (pm enable com.amazon.dcp and/or pm enable com.amazon.otaverifier). If commands fail, use gatesjr Debloater tool (from here on xda) to make sure packages are enabled. Since the upgrade will break root anyway, you may be able to get OTA upgrade by turning on wifi and doing "check now."
Click to expand...
Click to collapse
Is there any way to get TWRP and Root at 5.2.2u2 and get play store, or am I doomed to have an unrooted device forever? Will update in a few minutes about things you said to try.
Update: adb push 5.2.2u2file /cache results in permission denied. Trying to enable packages via adb also results in permission denied. Debloater says no packages are blocked. I would really appreciate it if I could get root and playstore on this thing. Thanks in advance.
Well, since you're unrooted without recovery you may have to go the replacement route. But first see if @bibikalka has an alternative.
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.