So I updated my D4 last week to the new build number. I kept root using the RootKeeper app. It indeed stayed rooted after, as I can still see the Superuser app in my app drawer. However, none of the privileges don't seem to work. For example, drocap2 won't take pictures and when I open Titanium, it tells me it couldn't get root access. It says "this attempt was made using the '/system/bin/su' command."
I haven't modded a phone since the OG, and I'm a bit rusty. Could someone help me solve this problem? Thanks!
AMTrombley0924 said:
So I updated my D4 last week to the new build number. I kept root using the RootKeeper app. It indeed stayed rooted after, as I can still see the Superuser app in my app drawer. However, none of the privileges don't seem to work. For example, drocap2 won't take pictures and when I open Titanium, it tells me it couldn't get root access. It says "this attempt was made using the '/system/bin/su' command."
I haven't modded a phone since the OG, and I'm a bit rusty. Could someone help me solve this problem? Thanks!
Click to expand...
Click to collapse
Stupid question but after you updated did you restore root with the Root Keeper app?
Sent from my DROID4 using XDA
Ha! No I didn't. I didn't know you had to restore it. I just saw the su app in my drawer and though I was good. This was the first time using that app. Thanks!
AMTrombley0924 said:
Ha! No I didn't. I didn't know you had to restore it. I just saw the su app in my drawer and though I was good. This was the first time using that app. Thanks!
Click to expand...
Click to collapse
Glad it was something easy!
Sent from my DROID4 using XDA
AMTrombley0924 said:
Ha! No I didn't. I didn't know you had to restore it. I just saw the su app in my drawer and though I was good. This was the first time using that app. Thanks!
Click to expand...
Click to collapse
I am having the same issue, I restored using the root keeper app however the device rooted and root permission granted check boxes never go green. When I click restore root the su.apk pops up say permission was granted.
When I try and run such via the terminal app it command not found. I did look in /system/bin and such is there but no dice
---------- Post added at 04:39 AM ---------- Previous post was at 04:29 AM ----------
jnc8651 said:
I am having the same issue, I restored using the root keeper app however the device rooted and root permission granted check boxes never go green. When I click restore root the su.apk pops up say permission was granted.
When I try and run such via the terminal app it command not found. I did look in /system/bin and such is there but no dice
Click to expand...
Click to collapse
Well it turns out a backup was dropped in /system and it was called su-backup. I was able to obtain root that way then I remounted system and copied it over to /system/bin
So, as it turns out, I did not think to backup my root with Rootkeeper, and now after the update, I still have Superuser but I'm unable to grant any apps superuser permissions. I got the Droid 4 utility .3 and tried to reroot. Unroot, then reroot, and basically everything I could think of, and still, no luck.
PS - Isn't unrooting supposed to remove superuser? It did not.
I had the same problem. Basically what has happened is you have lost root access, but the apps that use root are still there, and without root access, the unroot function is unable to remove them.
What I did, was manually push the files using adb :
adb push motofail /data/local/motofail
adb shell chmod 755 /data/local/motofail
Then I tried the running the exploit to get root:
adb shell "/data/local/motofail exploit"
but it failed... I also tried remounting the system folder as rw and it failed so I couldn't get root.
After this, I booted into fastboot/recovery and wiped my data/cache. Then, I tried the rooting process again, got read/write permission errors (did not originally), wiped data/cache again, and finally tried the unroot process.
This got rid of my superuser.apk and su binary somehow.
After all of this, the rooting utility worked. So, once you manage to get rid of those files, you should be good to go. I apologize I cannot narrow it down any better.
Well, I appreciate your response, but I'm still not having any luck.
Here is what I did:
Rooted phone few weeks back, left it alone.
Installed update
Did a factory reset, superuser still intact, but not granting permissions
Came to these forums
Booted into recovery and wiped (Holding volume buttons at boot, pressing down then up, formatting cache and data/factory reset)
Tried to root using Droid 4 Utility .3 - Did not get many errors
Waited for that process, then again, booted into recovery and wiped
Ran Droid 4 Utility .3 UNROOT option.
Recieved errors in removing superuser.apk due to read-only file system. Permission was denied to remove the app data, system/bin, etc....
Please, I know there's a lot of topics/posts around here and other sites, but I feel like I've tried everything to the best of my knowledge and refuse to give up!
I had a similar problem. I had tinkered with my framework and the update would not install. Got that fixed but forgot to unroot before running the update and got stuck just like you. Tried several things but could not get root back nor completely unroot. In a fit of frustration i tried pete's roottools that i had used for my d2g and it uninstalled the superuser and then i was able to root with the d4 utility. The phone works fine but i suppose it could have upset some other part. So try at your own risk.
can you give me some details about your uninstalled the superuser ?i use the peter's roottool and can't find how to do it...
jsnweitzel said:
I had a similar problem. I had tinkered with my framework and the update would not install. Got that fixed but forgot to unroot before running the update and got stuck just like you. Tried several things but could not get root back nor completely unroot. In a fit of frustration i tried pete's roottools that i had used for my d2g and it uninstalled the superuser and then i was able to root with the d4 utility. The phone works fine but i suppose it could have upset some other part. So try at your own risk.
Click to expand...
Click to collapse
Related
So a while back I used a 1-Click root app. Don't recall which one. Then flashed CM6. Lately I've been noticing some permissions issues.
It started when I attempted to install the new Car Home from the market and couldn't. I tried using RootExplorer to unistall the old version with no luck. I've given it SU permissions but still no dice.
Today I tried to install the new YouTube app from the market but got the same results.
So I tried through ADB and can't navigate to /system/app.
# cd /system/app -- gives "cd: can't cd to /system/app"
# su cd /system/app -- gives "Permission denied"
I've also tried fix_permissions in the terminal with no luck. (I remember this from the G1 days. don't know if it is still used)
Anyone know what could be going on?
I'm not concerned about my warranty any more so I suppose I could unlock my bootloader if anyone thinks rooting the official way would help.
Thanks for your time.
Are you mounting Root Explorer in R/W?
Edit: I had probs mounting my Root Explorer into R/W, and eventually found out I had a bad version of busybox...
Sent from my Nexus One using XDA App
danger-rat said:
Are you mounting Root Explorer in R/W?
Click to expand...
Click to collapse
Wow I feel dumb. I was forgetting to mount in R/W. Got the old apps uninstalled. Still can't get the new apps installed.. Oh well I never use either of them anyway.
BTW any reason I couldn't cd to /system/app in ADB? Probably something else stupid.
Just confirm that the apps are removed (my busybox issue sometimes made it appear like the apps were gone, but when I looked again, they were back).
Did you reboot after removing?
Sent from my Nexus One using XDA App
To upgrade system apps:
1. Uninstall the old version using Root Explorer or Titanium Backup (I've found Titanium to be easier).
2. Reboot.
3. Install the new system app from the Market.
Dude,
Did you not read the OP? He's having trouble uninstalling with Root Explorer... how does telling him to uninstall with Root Explorer help?
Sent from my Nexus One using XDA App
danger-rat said:
Dude,
Did you not read the OP? He's having trouble uninstalling with Root Explorer... how does telling him to uninstall with Root Explorer help?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Dude,
I read the op. I also read the followup where he figured out he had to remount in rw mode. I was attempting to offer the procedure that works 100% of the time for upgrading system apps.
Fair enough...
Sent from my Nexus One using XDA App
I apparently posted in the wrong section (for kindle 2 in case anyone wants to delete that one).
I rooted my 7" Kindle fire HD shortly after getting it. To my surprise there was an automated program that did it for me so I didn't have to learn a whole lot. That was ~ 5 months ago. The big thing was to add the play store and a custom launcher which I did (apex launcher in case it matters).
Yesterday the only launcher available to me was the kindle launcher. I thought perhaps an update went wrong so I uninstalled and reinstalled the apex launcher via the play store. The launcher works, but I have to access it by going to the play store and clicking "open" on the app page (where you could install/uninstall the app). I searched how to install a launcher since I remembered taking different step other than just installing from the play store. The article mentioned going to app/data and when I do it says i no longer have root access.
I tried running the root program and I got a access denied message and root failed try again.
My question ends up being did I actually loose root access or is it something else? All I really need is to have the home button take me to the apex launcher and I wouldn't know anything had changed.
It was suggested that I run root checker (Thanks mindmajick). I did and it said Sorry, no root access. My software version 7.2.3 .
Any suggestions for a next step?
OK, this is no biggie. It happened to me. So if you don't have root access, but you still have play store installed, it's just a matter of rooting it again. But one last thing to check. Go to you file explorer or root explorer and go to " \" I am supposing you know how to do that. You get there by if using es file explorer leading up when you first open it.When you get to \, then you navigate to "system ".Then look file. A folder that is called "Xbin" and open it. If you have a file called "su " in it you are still rooted and I don't know what is going on. If you don't have it, then you just uninstall all things you added from the play store that are system files (optional. If younger like me a bit OCD them you should do it.) Then uninstall superuser and apex, and then reboot. Then root the kindle fire HD again. I suppose you know how to do that.
Please give me a thanks if I helped you, and if this doesn't work, I will see what else we can do.
Sent from my KFTT using xda app-developers app
miztah1999z said:
A folder that is called "Xbin" and open it. If you have a file called "su " in it you are still rooted and I don't know what is going on. If you don't have it, then you just uninstall all things you added from the play store that are system files (optional. If younger like me a bit OCD them you should do it.) Then uninstall superuser and apex, and then reboot. Then root the kindle fire HD again. I suppose you know how to do that.
Click to expand...
Click to collapse
There was not a file called su in the Xbin folder.
So if i'm lazy/busy I can uninstall superuser, apex and then reroot it? Do you know what happened and how it was caused? Is doing as you mentioned preferable to "restoring to factory default" as far as stability with any legacy fragments that will be left?
Sorry if these are beginner questions, but I've really only learned as much as I needed to to root my kindle (which wasn't much). On a related note, is there a post limit where you don't have to keep entering the captchas to post?
Reroot your kindle. Reset to factory defaults will leave some traces, and then you try to reroot it, you get a bricked kindle. just uninstall things manually, the super user application and leave the market on there, but uninstall apex. Then root it using binary tool and qemu. Root.
edit you have to uninstall super user and apex launcher and reboot the kindle. Then you territory it using said methods.
Sent from my KFTT using xda app-developers app
miztah1999z said:
the super user application and leave the market on there, but uninstall apex. Then root it using binary tool and qemu. Root.
edit you have to uninstall super user and apex launcher and reboot the kindle. Then you territory it using said methods.
Click to expand...
Click to collapse
Apex hung on the uninstall, meaning it said uninstalling for about 10 minutes. I rebooted and i was given the option to install it in the play store so I assumed it was gone. Superuser also removed. I tried rooting it using RootQemu. It gave me an error in the second step
"Step 2 - Expoiting...
/system/bin/sh: cannot create /data/local.prop: Permission denied"
OK. I want you to installation bin4y method. You run the run me in that, and make sure adb driver is working. After. Binary method your kindle will be slow and sluggish. That's OK. Run the qemu root and follow instructiona, and you should be fine
Sent from my KFTT using xda app-developers app
---------- Post added at 12:38 AM ---------- Previous post was at 12:29 AM ----------
Ok im on my computer now, i will type better. Download the Bin4y Rooting mehtod here: http://forum.xda-developers.com/showthread.php?t=1886460
Then extract it, make sure adb is intalled by going to device manager and plug in kindel, make sure no yello or red exclamation points by Kindle fire or portable device. IMPORTANT: MAKE SURE YOU HAVE LATEST JAVA
THen run the "RunMe.bat" in the Bin4y root folder. Follow the instructions. After you are done with that, kindle will be slow and sluggish. PLug in again, and run Rootqemu method (the "bat" file" ) and follow instructions and if computer doesnt recognize the kindle after each reboot, unplug it and plug it back in. After qemu root done, check kindle for superuser app, and open your es file explorer. GO to settings, and root settings. Put a checkmark by EVERYTHING! and if a popup comes saying "Es file explorer root premission" something like that, click grant/allow. Then you are rooted!
Thanks if i helped.
Still nothing. When I ran the Bin4y is asked if I wanted to do a restore. While I was going wtf do I do now, it apparently timed out and did it anyway.
Once that was done I ran rootqemu and got the same error message: "Step 2 - Expoiting...
/system/bin/sh: cannot create /data/local.prop: Permission denied"
I appreciate your help!
Did you ever disable OTA (Over The Air) Updates? When you rooted the first time were you running 7.2.1 or 7.2.2? The updates will remove root. To me, that's what it sounds like. Someone will have an answer.... in fact, if you are willing to invest $13, you should check out both links in my signature. They would provide a permanent solution to your issue.
Good Luck!
Zuggel said:
Still nothing. When I ran the Bin4y is asked if I wanted to do a restore. While I was going wtf do I do now, it apparently timed out and did it anyway.
Once that was done I ran rootqemu and got the same error message: "Step 2 - Expoiting...
/system/bin/sh: cannot create /data/local.prop: Permission denied"
I appreciate your help!
Click to expand...
Click to collapse
Do you have ADB drivers and Java the latest version installed? Any way, keep your KFHD unlocked when you are doing the "RunME" from Bin4y ROOT many android method. If you have ADB and Java installed, and your kindle is plugged in a USB 2.0 or 3.0 slot on your computer, you run Bin4y runme and watch for a popup on your kindle that says restore in the bottom left(i think). Press restore. Then after that is done its slow etc etc (in before post) if bin4y is done correctly qemu should run fine.
Krsmqn said:
Did you ever disable OTA (Over The Air) Updates? When you rooted the first time were you running 7.2.1 or 7.2.2? The updates will remove root. To me, that's what it sounds like. Someone will have an answer.... in fact, if you are willing to invest $13, you should check out both links in my signature. They would provide a permanent solution to your issue.
No, I never disabled OTA updates, apparently I should have read a little more than I did...but it worked for a couple of months after the update. I'm in no hurry for a fix...I was going to say I could try making one, but i'm not going to take the time right now for that :silly: . I might look into ordering one just in case.
Good Luck!
Click to expand...
Click to collapse
miztah1999z said:
Do you have ADB drivers and Java the latest version installed? Any way, keep your KFHD unlocked when you are doing the "RunME" from Bin4y ROOT many android method. If you have ADB and Java installed, and your kindle is plugged in a USB 2.0 or 3.0 slot on your computer, you run Bin4y runme and watch for a popup on your kindle that says restore in the bottom left(i think). Press restore. Then after that is done its slow etc etc (in before post) if bin4y is done correctly qemu should run fine.
Click to expand...
Click to collapse
Yes the adb drivers are installed and I have the latest java. I'm not sure if it was unlocked or not. I did not press restore, when that came up I was too busy going oh sh!t, what do I do now and then it did something on it's own. I don't think it restored it since it is not running slow. I will hopefully have time tomorrow to mess with it a little more.
Zuggel said:
Yes the adb drivers are installed and I have the latest java. I'm not sure if it was unlocked or not. I did not press restore, when that came up I was too busy going oh sh!t, what do I do now and then it did something on it's own. I don't think it restored it since it is not running slow. I will hopefully have time tomorrow to mess with it a little more.
Click to expand...
Click to collapse
Be sure to click the restore next time. And it WILL be slow and sluggish. Then just remember to use QemuRoot method! THIS IS A MUST! YOU CAN"T DO SH*T ON YOUR KINDLE IF YOU DON'T DO THE QEMUROOT.
miztah1999z said:
Be sure to click the restore next time. And it WILL be slow and sluggish. Then just remember to use QemuRoot method! THIS IS A MUST! YOU CAN"T DO SH*T ON YOUR KINDLE IF YOU DON'T DO THE QEMUROOT.
Click to expand...
Click to collapse
Seems to have worked, just got done with RootQemu and it said it was done. After the restore, I didn't have an pictures (icons, screen saver) which had me a little worried, they came back after step 3 though. Superuser is back on. Now to re-remember what I need to do now (adding turn off OTA updates to the list).
Thanks a lot for your help miztah!!
Krsmqn, i ordered one of those cables just in case I need it in the future. I figure for a few $ i would rather have it than not.
Zuggel said:
Seems to have worked, just got done with RootQemu and it said it was done. After the restore, I didn't have an pictures (icons, screen saver) which had me a little worried, they came back after step 3 though. Superuser is back on. Now to re-remember what I need to do now (adding turn off OTA updates to the list).
Thanks a lot for your help miztah!!
Krsmqn, i ordered one of those cables just in case I need it in the future. I figure for a few $ i would rather have it than not.
Click to expand...
Click to collapse
No problem, I was in the same predicament as you a couple of weeks ago. Have fun with your rooted kindle! And be sure to disable Amazon OTA updates. Here is a link: (I would use method number 1 because you can use that utility for a while, and use it to fix a bricked Kindle, now that the bootloader has been cracked.) You don't really need that cable unless you are messing around with the bootloader.
http://forum.xda-developers.com/showthread.php?t=2086450
Thanks for the link. The cable is already on it's way via a slow boat from china. Figure I will have it in a month
I am now having a problem with the apex launcher. I had the regular version before and was going to try the pro this time. I installed it and when I go to run it it says "Apex launcher has stopped". When I go to the app description page, it give me the option to force stop but not to uninstall. I tried reinstalling it same thing. I moved the apk file to /system/app and gave it user R/W, group & other read only. then installed. Do i perhaps need to manually delete something?
Try completely removing it from both system /application & data/ application (if applicable), save one to your sdcard. Then instead of clicking on the application to install, long press (on the one you saved to sdcard ) and choose move (to). Move the application to system /app. Do not install. Instead, long press and choose properties (at the bottom of the long press menu ). Change permissions to rw-r-r. Save. Do not Install. Reboot. You should see "kindle is upgrading" upon rebooting. When it's ready, you should have it as a launcher option.
Good luck.
Or you could just delete the apex launcher from system. /Application and the data/app . Then reboot, install apex from play store and move from data application to system application, and change properties to rwxrxr and reboot without installing. Kinda the same thing just a little change in beginning.
Sent from my KFTT using xda app-developers app
I tried it that way you suggested Krsmqn, same thing, the error message saying apex launcher has stopped. I did not see a file to delete in the data/app folder unless it has an odd name.
miztah1999z said:
Or you could just delete the apex launcher from system. /Application and the data/app . Then reboot, install apex from play store and move from data application to system application, and change properties to rwxrxr and reboot without installing. Kinda the same thing just a little change in beginning.
Sent from my KFTT using xda app-developers app
Click to expand...
Click to collapse
Seems to be working so far....I wonder if it was an issue because I was trying to use the pro version?
2 reboots and no issues!!
Zuggel said:
Seems to be working so far....I wonder if it was an issue because I was trying to use the pro version?
2 reboots and no issues!!
Click to expand...
Click to collapse
So did you fix it my way or qrsmn way?
miztah1999z said:
So did you fix it my way or qrsmn way?
Click to expand...
Click to collapse
I followed what you had said, d/l from the app store and moving it. When I was in settings it had a message in red about going to recently used apps and removing other loaders listed. I will check when I get home and see if it is still there.
My friend who also has a moto x just got the software update for sprint. When it was downloading it turned off and whenever he turns it back on , after about 30 seconds it powers back off. Any ideas on how to fix it ???
Please help!!!
Sent from my XT1058 using xda app-developers app
KNiGHTx4 said:
My friend who also has a moto x just got the software update for sprint. When it was downloading it turned off and whenever he turns it back on , after about 30 seconds it powers back off. Any ideas on how to fix it ???
Please help!!!
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
I read something about clearing cache earlier but I can't find it now. I am looking to see if I can find it because I am not sure if that is actually what this person did.
Do a factory reset in recovery
Sent on my Moto X
In case anyone was wondering he fixed it with a ROOT browser (has to be root) and going into the root directory (/ not /root) and then going into cache and deleting the OTA. Still not sure how he is going to get the ota. And also it wouldn't even let him factory reset so that doesn't work
Sent from my XT1058 using xda app-developers app
He is probably rooted using PwnMyMoto. This hijacks the stock recovery. That's what's keeping the OTA from installing. He will need to flash the stock recovery via fastboot and then take the OTA.
Sent from my XT1058 using Tapatalk 4
I have this same problem. Stupidly installed the update today without realizing how it would work with pwnmymoto root.
Now the phone just reboots every 30 seconds. I'm not sure where to go from here. Any advice would be appreciated.
KNiGHTx4 said:
In case anyone was wondering he fixed it with a ROOT browser (has to be root) and going into the root directory (/ not /root) and then going into cache and deleting the OTA. Still not sure how he is going to get the ota. And also it wouldn't even let him factory reset so that doesn't work
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
How did he do this while his phone would reboot every 30 sec?
a17o17ymous said:
How did he do this while his phone would reboot every 30 sec?
Click to expand...
Click to collapse
I managed to do it although it was a pain.
Just like he said, install Root Browser. Just keep trying to install it from play store until it sticks. It took me 10 tries because the reboot kept happening before it was done. Then launch Root Browser and accept the allowances and allow it via SU. Again this took many attempts.
Finally once it is installed, go into Root Browser and go directly to the Cache folder off of root, you should see it right away. /Cache
Inside there are two folders, lost+found and recovery, then there is a third file which is a zip file. It's called ghost_blahblabhblah. I tried to rename the file, which just resulted in it vanishing, so I would just delete the thing.
After the file was gone my phone stopped rebooting and it is now back at the prior version.
motomesh said:
I managed to do it although it was a pain.
Just like he said, install Root Browser. Just keep trying to install it from play store until it sticks. It took me 10 tries because the reboot kept happening before it was done. Then launch Root Browser and accept the allowances and allow it via SU. Again this took many attempts.
Finally once it is installed, go into Root Browser and go directly to the Cache folder off of root, you should see it right away. /Cache
Inside there are two folders, lost+found and recovery, then there is a third file which is a zip file. It's called ghost_blahblabhblah. I tried to rename the file, which just resulted in it vanishing, so I would just delete the thing.
After the file was gone my phone stopped rebooting and it is now back at the prior version.
Click to expand...
Click to collapse
Thank you for the quick reply!
motomesh said:
I managed to do it although it was a pain.
Just like he said, install Root Browser. Just keep trying to install it from play store until it sticks. It took me 10 tries because the reboot kept happening before it was done. Then launch Root Browser and accept the allowances and allow it via SU. Again this took many attempts.
Finally once it is installed, go into Root Browser and go directly to the Cache folder off of root, you should see it right away. /Cache
Inside there are two folders, lost+found and recovery, then there is a third file which is a zip file. It's called ghost_blahblabhblah. I tried to rename the file, which just resulted in it vanishing, so I would just delete the thing.
After the file was gone my phone stopped rebooting and it is now back at the prior version.
Click to expand...
Click to collapse
This happened to mine as well. Luckily in had root explorer installed. All it took was fast fingers :silly: deleting the ota file form /cache will stop the reboot process
mar5hal said:
This happened to mine as well. Luckily in had root explorer installed. All it took was fast fingers :silly: deleting the ota file form /cache will stop the reboot process
Click to expand...
Click to collapse
So, essentially you could just boot to fastboot and run:
Code:
fastboot erase cache
?
Sent from my XT1058 using Tapatalk 4
I had the same problem on a rooted AT&T device. Had to quickly delete the zip file in the cache folder before the device rebooted itself.
Anybody know how to get the update installation done?
vr3690 said:
I had the same problem on a rooted AT&T device. Had to quickly delete the zip file in the cache folder before the device rebooted itself.
Anybody know how to get the update installation done?
Click to expand...
Click to collapse
Use rsdlite or my python script to go back to 100% stock. Then do the update. Just remember, you cannot downgrade after you update!
Sent from my XT1058 using Tapatalk 4
motomesh said:
I managed to do it although it was a pain.
Just like he said, install Root Browser. Just keep trying to install it from play store until it sticks. It took me 10 tries because the reboot kept happening before it was done. Then launch Root Browser and accept the allowances and allow it via SU. Again this took many attempts.
Finally once it is installed, go into Root Browser and go directly to the Cache folder off of root, you should see it right away. /Cache
Inside there are two folders, lost+found and recovery, then there is a third file which is a zip file. It's called ghost_blahblabhblah. I tried to rename the file, which just resulted in it vanishing, so I would just delete the thing.
After the file was gone my phone stopped rebooting and it is now back at the prior version.
Click to expand...
Click to collapse
I can't even explain how much I appreciate this. I managed to get mine working again following your steps.
Ah! OK. I get it now! The hack to enable root was flashing the kernel image to the recovery partition. Since they used the same signature. Recovery mode in aboot doesn't protect /system so you can mount it read/write.
If you are bootlooping, try just flashing the stock recovery to the recovery partition from fastboot. Next boot, the update will apply. Then flash the pwnmymoto recovery to the recovery partition again after the update and you should be good to go!
In other words... The kernel image does not have the recovery ramdisk. So flashing the stock recovery image allows recovery mode to flash the update. Then switch back to the kernel image on the recovery partition.
If you already had root, this should keep it.
Sent from my XT1058 using Tapatalk 4
mar5hal said:
This happened to mine as well. Luckily in had root explorer installed. All it took was fast fingers :silly: deleting the ota file form /cache will stop the reboot process
Click to expand...
Click to collapse
Thanks for this information, I appreciate it. I almost entirely forgot about Root Explorer. That was already installed. Crisis averted.
motomesh said:
I managed to do it although it was a pain.
Just like he said, install Root Browser. Just keep trying to install it from play store until it sticks. It took me 10 tries because the reboot kept happening before it was done. Then launch Root Browser and accept the allowances and allow it via SU. Again this took many attempts.
Finally once it is installed, go into Root Browser and go directly to the Cache folder off of root, you should see it right away. /Cache
Inside there are two folders, lost+found and recovery, then there is a third file which is a zip file. It's called ghost_blahblabhblah. I tried to rename the file, which just resulted in it vanishing, so I would just delete the thing.
After the file was gone my phone stopped rebooting and it is now back at the prior version.
Click to expand...
Click to collapse
Thanks for the advice. I tried this but I don't see any files in the /Cache folder! Any other suggestions?
THANK YOU, sheesh!
motomesh said:
I managed to do it although it was a pain.
Just like he said, install Root Browser. Just keep trying to install it from play store until it sticks. It took me 10 tries because the reboot kept happening before it was done. Then launch Root Browser and accept the allowances and allow it via SU. Again this took many attempts.
Finally once it is installed, go into Root Browser and go directly to the Cache folder off of root, you should see it right away. /Cache
Inside there are two folders, lost+found and recovery, then there is a third file which is a zip file. It's called ghost_blahblabhblah. I tried to rename the file, which just resulted in it vanishing, so I would just delete the thing.
After the file was gone my phone stopped rebooting and it is now back at the prior version.
Click to expand...
Click to collapse
LIFE saving. Stupid me. That'll teach me to root my phone for particular reason.
A little tip to get Root Browser installed: go through another device to GPlay and install it to your Moto X. During the next loop, it should download, and then install on the following loop. One more pass to enable su privilege, and one more to find the dang file in cache and terminate with prejudice.
Exhale.
mar5hal said:
This happened to mine as well. Luckily in had root explorer installed. All it took was fast fingers :silly: deleting the ota file form /cache will stop the reboot process
Click to expand...
Click to collapse
the above steps saved my arse, so thank you. I kept letting the update go, but someone used my phone today and said "oops I think I hit update".
Argh....
rockcreek_md said:
LIFE saving. Stupid me. That'll teach me to root my phone for particular reason.
A little tip to get Root Browser installed: go through another device to GPlay and install it to your Moto X. During the next loop, it should download, and then install on the following loop. One more pass to enable su privilege, and one more to find the dang file in cache and terminate with prejudice.
Exhale.
Click to expand...
Click to collapse
I typically use a PC to go to the play store. easy peasy to get anything installed.
Hi,
I have the lg optimus l90.
I used the towelroot app to root the phone. i used a terminal app to verify that i do have root. when the app opened, it displayed a $ sign but when i typed "su" and pressed enter it gave me a "#" prompt. so am i rooted?
also i was told to install the superSU app. why do i need this? can't i just uninstall the bloatware right now since i am rooted?
I installed the superSU app but it was not able to install the su binary because i did not reboot the phone after using towelroot. I uninstalled the SuperSU app. anyhow, what do I need to do now to remove those bloatware apps. there is no option to uninstall in the apps section of the android settings application.
finally, I read somewhere that i should use nobloat app to uninstall the bloatware but it is not uninstalling the bloatware. I uninstalled it.
so what do I do now?
any help would be much appreciated.
thanks.
Superuser is needed for apps to have root rights to your phone. Install superuser. Reboot phone and open app. Reboot again if needed. Rooting is useless without superuser installed
Sent from my LG-D410 using Tapatalk
helix3000 said:
Hi,
I have the lg optimus l90.
I used the towelroot app to root the phone. i used a terminal app to verify that i do have root. when the app opened, it displayed a $ sign but when i typed "su" and pressed enter it gave me a "#" prompt. so am i rooted?
also i was told to install the superSU app. why do i need this? can't i just uninstall the bloatware right now since i am rooted?
I installed the superSU app but it was not able to install the su binary because i did not reboot the phone after using towelroot. I uninstalled the SuperSU app. anyhow, what do I need to do now to remove those bloatware apps. there is no option to uninstall in the apps section of the android settings application.
finally, I read somewhere that i should use nobloat app to uninstall the bloatware but it is not uninstalling the bloatware. I uninstalled it.
so what do I do now?
any help would be much appreciated.
thanks.
Click to expand...
Click to collapse
Along with root and SuperSU, you will also need a root App manager or root file manager. I personally prefer to use ES File Explorer as it is both an application manager ( user and system ) as well as an awesome file manager.
There is no list of acceptable system apps to remove. So be very careful as to what you uninstall or you may endup with a soft bricked phone or one that spazzes out whenever it feels like it. I would recommend making backups of any app you want to remove before uninstalling it. At least you might be able to restore them if something goes wrong.
shinobisoft said:
Along with root and SuperSU, you will also need a root App manager or root file manager. I personally prefer to use ES File Explorer as it is both an application manager ( user and system ) as well as an awesome file manager.
There is no list of acceptable system apps to remove. So be very careful as to what you uninstall or you may endup with a soft bricked phone or one that spazzes out whenever it feels like it. I would recommend making backups of any app you want to remove before uninstalling it. At least you might be able to restore them if something goes wrong.
Click to expand...
Click to collapse
thank you both for the replies.
so what exactly is SuperSU for? when I opened it up I saw nothing in the apps list and I did not see anything else in the other lists within the app. also, I did not restart the phone before trying to update the su files and when I did restart the phone nothing updated. So, do I use something like ES file explorer to remove bloatware?
by the way, when I tried to surf the web after installing superSU app, the web browser was extremely slow. the webpages loaded very slowly but when after I uninstalled the superSU app, it was loading the pages fast again as normal. what's up with that?
thanks.
helix3000 said:
thank you both for the replies.
so what exactly is SuperSU for? when I opened it up I saw nothing in the apps list and I did not see anything else in the other lists within the app. also, I did not restart the phone before trying to update the su files and when I did restart the phone nothing updated. So, do I use something like ES file explorer to remove bloatware?
Click to expand...
Click to collapse
SuperSU is a binary executable that grants or denies superuser requests. Without it root is worthless.
You won't see anything in SuperSU permission list until an app asks for superuser permissions. When first opening the SuperSU app you should get prompted to update/install the su binary. Allow that action to happen.
helix3000 said:
by the way, when I tried to surf the web after installing superSU app, the web browser was extremely slow. the webpages loaded very slowly but when after I uninstalled the superSU app, it was loading the pages fast again as normal. what's up with that?
thanks.
Click to expand...
Click to collapse
That's because the su binary was never updated.
shinobisoft said:
SuperSU is a binary executable that grants or denies superuser requests. Without it root is worthless.
Click to expand...
Click to collapse
so in order to run something like the nobloat app I need to grant it permission to be a superuser? I never had to do anything like that when I ran the nobloat app and It actually worked. It still does not make sense to me what supersu is used for.
That's because the su binary was never updated.
Click to expand...
Click to collapse
I ran the towelroot app and it was successful. However, I did not reboot the phone before attempting to update the su binary and the superSU app said i should restart before updating. I restarted the phone but it never updated the su binary when I ran the superSU app again. What do I do now?
thanks.
I had my phone rooted and all working fine on Nougat. I then tried installing secure settings for Tasker and since around this time, i've lost root and if i try flashing super su in TWRP, each time i boot and check i'm not rooted. If i open Super Su app it tells me that the framework needs to be updated and to reboot, i do this and it just keeps telling me the same.
The only thing i am thinking may have broken this is i found a guide to get Secure Settings working on nougat where someone suggested creating a folder with root file explorer called 'su' in system/bin. Now when i open up Titanium Backup it tells me it could not acquire root and say the attempt was made using the "/system/bin/su" command which im thinking means it's looking somewhere there is an empty folder?
I cant now of course delete the system/bin/su folder i created as i cant enable root in File Explorer so i'm pretty stuck and not sure what i can do. I've tried the cleanup and full unroot in the supersu app and then flashing supersu in twrp again but still says no root when i check
Any suggestions?
farquea said:
I had my phone rooted and all working fine on Nougat. I then tried installing secure settings for Tasker and since around this time, i've lost root and if i try flashing super su in TWRP, each time i boot and check i'm not rooted. If i open Super Su app it tells me that the framework needs to be updated and to reboot, i do this and it just keeps telling me the same.
The only thing i am thinking may have broken this is i found a guide to get Secure Settings working on nougat where someone suggested creating a folder with root file explorer called 'su' in system/bin. Now when i open up Titanium Backup it tells me it could not acquire root and say the attempt was made using the "/system/bin/su" command which im thinking means it's looking somewhere there is an empty folder?
I cant now of course delete the system/bin/su folder i created as i cant enable root in File Explorer so i'm pretty stuck and not sure what i can do. I've tried the cleanup and full unroot in the supersu app and then flashing supersu in twrp again but still says no root when i check
Any suggestions?
Click to expand...
Click to collapse
This post was a bit more informative than your "my device unrooted itself" post in the stable thread.
Dirty flash your system or use the file manager in TWRP to remove the offending folder.
I was thinking of trying that but fixed it a different way as I just posted in the SuperSU thread. But in case anyone else ever has this problem...
I fixed my issue. By disabling SuperSU and enabling again from the app settings and it gave me root. I then deleted a created su folder in system/bin that I manually created earlier when trying to get secure settings working.