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.
Related
After I installed the firmware update, via Odin, i can't seem to re-root my phone. I re-installed the update, renamed the zip, flashed it and no smoke. I'm kind of new with all of this so what do i do to access root at this point?
Also, I re-downloaded the superuser app from the market and it stated that there was a new version available. The app states" an error occurred and su was not updated. A zip(su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary. " I tried to flash this recieved an error message saying that the zip was "(bad)". What do I do?
did not have a problem with ryans one touch lag fix that also takes care of root
I'm having the same problem. Also new to this so I'm sure it's going to be something simple. But it's dricing me crazy. I'm sooo close. Anyone with advice it would be much appreciated.
sorry I forgot to say that I have the Epic 4g
aaconteh said:
After I installed the firmware update, via Odin, i can't seem to re-root my phone. I re-installed the update, renamed the zip, flashed it and no smoke. I'm kind of new with all of this so what do i do to access root at this point?
Also, I re-downloaded the superuser app from the market and it stated that there was a new version available. The app states" an error occurred and su was not updated. A zip(su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary. " I tried to flash this recieved an error message saying that the zip was "(bad)". What do I do?
Click to expand...
Click to collapse
The Superuser app from the market isn't going to give you superuser privileges without the phone being rooted. That's why you are rooting the phone in the first place.
As I've made a habit of experimenting with every ROM known to man I've gotten this down to a routine when it comes to flashing and re-rooting. And a big part of my routine is using TGA_Gunnman's handy One Click ROOT Windows application (also a mac version available in the same thread)...
http://forum.xda-developers.com/showthread.php?t=739300
Just use it and follow the instruction. Biggest thing is to make sure the phone has USB Debugging enabled and that the internal and external SD's are NOT MOUNTED. Just click the ROOT ME button, look in the shell window to see that the update.zip has been pushed successfully, use the vol rocker keys to select REINSTALL PACKAGES, and reboot.
It's never failed for me so far, and I've re-rooted dozens of times now.
Best of luck!
DemDonkies said:
sorry I forgot to say that I have the Epic 4g
Click to expand...
Click to collapse
The root method for the Epic4g is a tad different...and located in another forum...
http://forum.xda-developers.com/showthread.php?t=770388
Ok so I searched and read up alot but I dont find anyone with my situation, I tried several root methods for OTA gb update and even though I have no errors I still dont have root (or full root). superusers is there and terminal has access but thats it, I downloaded a root checker and titanium back up but im not seeing any root? does anyone know whats going on?
leviathanixi said:
Ok so I searched and read up alot but I dont find anyone with my situation, I tried several root methods for OTA gb update and even though I have no errors I still dont have root (or full root). superusers is there and terminal has access but thats it, I downloaded a root checker and titanium back up but im not seeing any root? does anyone know whats going on?
Click to expand...
Click to collapse
What does the Ti Backup (Root edition) say when you open it? Does it give an error, or say superuser permission granted?
A little Diag. box pops up and says: Sorry I could not acquire root privileges this app will not work yada yada yada.
Try This:
http://briefmobile.com/motorola-atrix-4g-root
or
The Second Post here:
http://forum.xda-developers.com/showthread.php?t=1138204
haven't tried any yet because I am not home, but those methods seem to be on par with the methods I tried. Hopefully different files
hmmm :\ I dont get it.. I KNOW I'm using CMD command prompts correctly but still no luck
Maybe give us the exact steps you are doing and what the cmd outputs are when you enter the commands?
I'm getting no problems when I enter the prompts everything goes as directed per guide but when I check the phone for actual root there is nothing there
Rooted now... for whatever reason I was forced to use the automated script and unlock the bootloader (something I didn't want to do), I tried all other cmd prompt methods and none worked, this might just be an enigma to me.
My friend gave me a droid razr which is rooted and has a custom rom installed on it. I was able to charge the device and boot into the OS however the phone simply will not be recognized by the computer. I've tried 3 different cables to no avail, there must be something wrong with the USB port itself.
Is there any way to unroot the device and get back to stock without having to connect the phone to the computer? I am able to put the SD card into a different phone in order to transfer files to it.
Thanks alot in advance
lysdexik said:
My friend gave me a droid razr which is rooted and has a custom rom installed on it. I was able to charge the device and boot into the OS however the phone simply will not be recognized by the computer. I've tried 3 different cables to no avail, there must be something wrong with the USB port itself.
Is there any way to unroot the device and get back to stock without having to connect the phone to the computer? I am able to put the SD card into a different phone in order to transfer files to it.
Thanks alot in advance
Click to expand...
Click to collapse
Using the app SuperSU, there's an option for "full unroot" in the settings. If you plan on keeping the ROM, I wouldn't unroot if I were you. If you DON'T plan on keeping the ROM, then you're pretty much hopeless to remove it without connecting to a computer. Are you sure the drivers are installed for the device? You say the phone charges, so I doubt it's the port. Do USB options show up in the notification tray on the phone when you plug it in to a computer?
Fracta1 said:
Using the app SuperSU, there's an option for "full unroot" in the settings. If you plan on keeping the ROM, I wouldn't unroot if I were you. If you DON'T plan on keeping the ROM, then you're pretty much hopeless to remove it without connecting to a computer. Are you sure the drivers are installed for the device? You say the phone charges, so I doubt it's the port. Do USB options show up in the notification tray on the phone when you plug it in to a computer?
Click to expand...
Click to collapse
There are no usb options that appear in the notification window, and since I posted this the phone has quit charging . I'm not sure how he went about rooting the phone because when I went into the recovery, it was still the stock recovery that was installed. I did a factory reset on the device and when I booted it back up it asked me to activate before I could go any further. I tried using my sim card from my galaxy nexus but it gave me an error. I was thinking that I might bring the phone to verizon and see if it activates with a clean sim card and then look to see if it is still rooted or not.
Also, after further digging I found out that he actually did not install a custom ROM, all he did was root the device. So if I can get into the SuperSU app I will go ahead and unroot the device.
lysdexik said:
There are no usb options that appear in the notification window, and since I posted this the phone has quit charging . I'm not sure how he went about rooting the phone because when I went into the recovery, it was still the stock recovery that was installed. I did a factory reset on the device and when I booted it back up it asked me to activate before I could go any further. I tried using my sim card from my galaxy nexus but it gave me an error. I was thinking that I might bring the phone to verizon and see if it activates with a clean sim card and then look to see if it is still rooted or not.
Also, after further digging I found out that he actually did not install a custom ROM, all he did was root the device. So if I can get into the SuperSU app I will go ahead and unroot the device.
Click to expand...
Click to collapse
From what I know, the ports on the RAZR are poorly designed and prone to break. I had issues with HDMI detection a while ago and had to send it in for repairs.
Factory resets do not unroot the device.When you get the chance to use the SuperSU app (you may have to download it from the market), it should be easy to unroot it, but it's hard to say when the method isn't known.
And as far as I know, can't you just use wi-fi to complete initial setup?
Fracta1 said:
From what I know, the ports on the RAZR are poorly designed and prone to break. I had issues with HDMI detection a while ago and had to send it in for repairs.
Factory resets do not unroot the device.When you get the chance to use the SuperSU app (you may have to download it from the market), it should be easy to unroot it, but it's hard to say when the method isn't known.
And as far as I know, can't you just use wi-fi to complete initial setup?
Click to expand...
Click to collapse
Ok, I got the device activated and yeah it appears that it is still rooted. You mentioned downloading SuperSU off of the marketplace, as only Superuser was installed on the phone.
I downloaded SuperSU and when I try to open it I am getting the error ("There is no SU binary installed, and SuperSU cannot install it. This is a problem!").
So yeah, I am not sure where to go from here, the port is still not working so I need to do something before the battery dies.
lysdexik said:
Ok, I got the device activated and yeah it appears that it is still rooted. You mentioned downloading SuperSU off of the marketplace, as only Superuser was installed on the phone.
I downloaded SuperSU and when I try to open it I am getting the error ("There is no SU binary installed, and SuperSU cannot install it. This is a problem!").
So yeah, I am not sure where to go from here, the port is still not working so I need to do something before the battery dies.
Click to expand...
Click to collapse
Try an app like Root Checker or Got Root? to make sure the device IS rooted. I have messily unrooted a device before and while it WAS unrooted, it left Superuser and Busybox behind.
If it IS rooted, find an app of your choice (System Tuner Pro, Titanium Backup...) and uninstall root apps (Superuser). Cover up root best you can. I've handed a boot-looping device in for repairs with no carrier trouble, so I'm sure you'll be fine.
If it ISN'T... Well, you're hopeless without a computer as far as I can say.
Also, it may not help, but if your device is indeed rooted, you could also go into Superuser, swipe left and try to update the binaries so you can try SuperSU again.
Fracta1 said:
Try an app like Root Checker or Got Root? to make sure the device IS rooted. I have messily unrooted a device before and while it WAS unrooted, it left Superuser and Busybox behind.
If it IS rooted, find an app of your choice (System Tuner Pro, Titanium Backup...) and uninstall root apps (Superuser). Cover up root best you can. I've handed a boot-looping device in for repairs with no carrier trouble, so I'm sure you'll be fine.
If it ISN'T... Well, you're hopeless without a computer as far as I can say.
Also, it may not help, but if your device is indeed rooted, you could also go into Superuser, swipe left and try to update the binaries so you can try SuperSU again.
Click to expand...
Click to collapse
I'm going to try Root Checker right now to see if its actually rooted like you said. I actually updated the Superuser app earlier and SuperSU still wasn't working so I'm starting to think it may have lost root somehow.
I also tried using Superuser Update Fixer and manually flashing the SU binary file from recovery but since the phone is still on stock recovery it wouldn't work.
I was also thinking that I could try and cover up root with titanium backup as you said, that was going to be my last step but since the battery is getting lower and lower I may have to go that route and hopefully not have a problem with Verizon. I guess it also helps that the stock recovery and ROM are still installed on it.
This is just a side project for me, I have a galaxy nexus myself and I have never had any trouble with it.
UPDATE: I just used both of the root checking applications you suggested and they both say that the phone is not actually rooted. Root Checker just spit out a message saying it wasn't rooted and Got Root? said that it located busybox but could not obtain root access. I'm going to try and clean things up with titanium backup.
UPDATE 2: When I installed titanium backup, the app asked me for root permissions and I hit grant. When I open superuser it shows it as giving permission to titanium backup but I can't find Superuser in the list of applications within titanium backup itself. There has to be another way to remove superuser.
UPDATE 3: I just tried to delete the superuser.apk file using root explorer and I get a pop-up saying that it won't allow me to delete that APK because my phone is not rooted. Ugh.. now I'm stuck.
lysdexik said:
I'm going to try Root Checker right now to see if its actually rooted like you said. I actually updated the Superuser app earlier and SuperSU still wasn't working so I'm starting to think it may have lost root somehow.
I also tried using Superuser Update Fixer and manually flashing the SU binary file from recovery but since the phone is still on stock recovery it wouldn't work.
I was also thinking that I could try and cover up root with titanium backup as you said, that was going to be my last step but since the battery is getting lower and lower I may have to go that route and hopefully not have a problem with Verizon. I guess it also helps that the stock recovery and ROM are still installed on it.
This is just a side project for me, I have a galaxy nexus myself and I have never had any trouble with it.
UPDATE: I just used both of the root checking applications you suggested and they both say that the phone is not actually rooted. Root Checker just spit out a message saying it wasn't rooted and Got Root? said that it located busybox but could not obtain root access. I'm going to try and clean things up with titanium backup.
UPDATE 2: When I installed titanium backup, the app asked me for root permissions and I hit grant. When I open superuser it shows it as giving permission to titanium backup but I can't find Superuser in the list of applications within titanium backup itself. There has to be another way to remove superuser.
UPDATE 3: I just tried to delete the superuser.apk file using root explorer and I get a pop-up saying that it won't allow me to delete that APK because my phone is not rooted. Ugh.. now I'm stuck.
Click to expand...
Click to collapse
Yeah... Sorry about your luck
You could try sending it into Verizon still. They may fix it. Perhaps not for free. Even if not at all, at least it's just a side project?
That's about all I can think of :/
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 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?