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.
Related
Missing paid and some nonpaid apps?
This will revert your build fingerprint (its safe and pre-tested by me) so that they show up again.
Install it like any update.zip type install. Backup to be safe, and yes, you must be rooted.
fingerprint.zip
MD5 is d9524d4b9a45486f0b317404e79bcb10.
adrynalyne said:
Missing paid and some nonpaid apps?
This will revert your build fingerprint (its safe and pre-tested by me) so that they show up again.
Install it like any update.zip type install. Backup to be safe, and yes, you must be rooted.
fingerprint.zip
MD5 is d9524d4b9a45486f0b317404e79bcb10.
Click to expand...
Click to collapse
cool been thx alot for this
I installed the zip while in recovery but I still cannot find some apps. Two examples are Tapatalk Pro, and Windfinder Pro. They both have updates being shown available in Appbrain but they cannot be found, 'The requested item could not be found.'
How about in the regular market?
Both show up for me. This change may not be instant. Check back in a few hours. Unless you want to hard reset your phone. I believe it has to do with the frequency that your gmail account syncs with the market.
Well I can search for them in Appbrain fine but when I click them it says 'The requested item could not be found.' I will late a little while.
Thanks
All just showed up after I rebooted the phone again.
Simply installing one new app made all of my apps reappear on the marketplace downloads page.. not sure if will work for others
JTC, this worked for me. Installed a quick free app, then everything else showed up. Thank you both.
I have sky raider's froyo rom and this froze my restart. is there another way?
Er...I don't recall this being for Froyo....
blastek said:
I have sky raider's froyo rom and this froze my restart. is there another way?
Click to expand...
Click to collapse
You can restore a nandroid system backup if you have one recently. Always make one before you do anything that changes your phone. That way when failures happen from messing with system files you can restore.
You can possibly open his rom, then go to the system folder within it.
look for the build.prop file there. Copy it to your tools folder where ADB is.
Then do this
reboot phone into recovery
go to command prompt
type adb push build.prop /system/
This should solve the issue if you can get the build.prop off his phone or just do a nandroid restore from this rom.
TNS201 said:
You can restore a nandroid system backup if you have one recently. Always make one before you do anything that changes your phone. That way when failures happen from messing with system files you can restore.
You can possibly open his rom, then go to the system folder within it.
look for the build.prop file there. Copy it to your tools folder where ADB is.
Then do this
reboot phone into recovery
go to command prompt
type adb push build.prop /system/
This should solve the issue if you can get the build.prop off his phone or just do a nandroid restore from this rom.
Click to expand...
Click to collapse
I still want to fix the market though. Can I edit the build file
installed this .zip file about an hour ago. no change yet. I'll check it in the morning. Hope it works, as these missing apps are beginning to bother me.
i feel like an idiot after this but here it is. I tried replacing the android market with the new version. I placed the file, renamed Vending.apk, into system/apps. prior to that I removed the old market apk and placed it in another folder. needless to say the new version didn't work after a reboot, and I then tried reverting back with the old apk, and of course that doesn't work now either. so now I'm marketless
please don't tell me have to flash back to stock and reroot. it has to be a simple fix, right?
any help as always is appreciated
I used the non-themed one from this thread: http://www.droidforums.net/forum/te...05022-who-going-re-revisited-vending-apk.html
If I recall, I opened Astro and installed it with that app's installer. I think it even came up with an option to install, update or uninstall. If it wasn't Astro, it was Root Explorer as those are the only two apps I use to install apks.
Good luck.
Geezer Squid said:
I used the non-themed one from this thread: http://www.droidforums.net/forum/te...05022-who-going-re-revisited-vending-apk.html
If I recall, I opened Astro and installed it with that app's installer. I think it even came up with an option to install, update or uninstall. If it wasn't Astro, it was Root Explorer as those are the only two apps I use to install apks.
Good luck.
Click to expand...
Click to collapse
Thanks. I'm using root explorer, and installation fails. It goes through the installation process, but just fails at the end. So I still don't know exactly what the problem is.
Well, in the world of android phones, it seems that usually means there's a version of vending.apk somewhere on the phone that needs to be removed.
Also, take a long look at this thread: http://forum.xda-developers.com/showthread.php?t=872621
Just copying the Vending.apk in /system/app is normally fine.
Did you check the file permissions of the new file?
Needs to be at least rw-r--r--
After reboot you should see the market in your apps.
Sent from my LogicPD Zoom2 using XDA App
2alex said:
Just copying the Vending.apk in /system/app is normally fine.
Did you check the file permissions of the new file?
Needs to be at least rw-r--r--
After reboot you should see the market in your apps.
Sent from my LogicPD Zoom2 using XDA App
Click to expand...
Click to collapse
I checked permissions and all is set up correctly, and it is installed after all. However, when I open the market, it hangs for a moment and then closes.
I had the exact same thing happen a couple weeks ago... There may have been a solution, but I just did a Titanium backup, reset to factory settings, re-rooted, and restored Titanium. The whole process probably took less than what you've spent asking for a solution in this thread
wvcachi said:
I had the exact same thing happen a couple weeks ago... There may have been a solution, but I just did a Titanium backup, reset to factory settings, re-rooted, and restored Titanium. The whole process probably took less than what you've spent asking for a solution in this thread
Click to expand...
Click to collapse
it'll probably take me a bit longer than you to go through the rooting process again, but I guess it'll give me a chance to update my Nc to 1.01.
I'll still give it time for someone to come up with an answer that doesn't require rerooting
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
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.
Hello, I bought my Nexus 6 from Amazon (US version) unlocked. I joined Project Fi which requires installation of the Project Fi app. Now I am leaving Project Fi going back to Verizon but I cannot remove the Project Fi app. I'm only able to uninstall all updates, and disable the app. Clearing the cache, disabling the app with SIM removed, rebooting with no SIM, etc. Nothing removes it. I also tried to remove it via the Play Store by holding on it and removing it with the X at the upper right. Well there is no way to select it in the play store, it can only be "enabled".
Project Fi support is of course useless. I know this app did not come on my phone unless it was hidden in a system partition until activation?
Any ideas on how to remove this app totally? I want to get it removed so I can get back on Verizon without it causing issues trying to interact with the SIM. Thank you
wats6831 said:
Hello, I bought my Nexus 6 from Amazon (US version) unlocked. I joined Project Fi which requires installation of the Project Fi app. Now I am leaving Project Fi going back to Verizon but I cannot remove the Project Fi app. I'm only able to uninstall all updates, and disable the app. Clearing the cache, disabling the app with SIM removed, rebooting with no SIM, etc. Nothing removes it. I also tried to remove it via the Play Store by holding on it and removing it with the X at the upper right. Well there is no way to select it in the play store, it can only be "enabled".
Project Fi support is of course useless. I know this app did not come on my phone unless it was hidden in a system partition until activation?
Any ideas on how to remove this app totally? I want to get it removed so I can get back on Verizon without it causing issues trying to interact with the SIM. Thank you
Click to expand...
Click to collapse
sure, its very easy, but you need root to remove it, since its a system app. just use a root file explorer to find it in /system/app/, then delete it and reboot. when you boot up, it'll be gone. or, you can perform a factory reset, then boot up first time with your Verizon sim in the phone. then the app will go back into hiding in your system partition.
simms22 said:
sure, its very easy, but you need root to remove it, since its a system app. just use a root file explorer to find it in /system/app/, then delete it and reboot. when you boot up, it'll be gone. or, you can perform a factory reset, then boot up first time with your Verizon sim in the phone. then the app will go back into hiding in your system partition.
Click to expand...
Click to collapse
Thank you sir. Just so that I am clear: I need to obtain root via this guide: http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
which will wipe the device. I can then use any root file explorer app to delete the system/app/folder
It's been a while since I've worked on phone but I've been rooting/flashing since the OG DROID. I just want to be very clear before I wipe my device. Thank you again for any clarification.
wats6831 said:
Thank you sir. Just so that I am clear: I need to obtain root via this guide: http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
which will wipe the device. I can then use any root file explorer app to delete the system/app/folder
It's been a while since I've worked on phone but I've been rooting/flashing since the OG DROID. I just want to be very clear before I wipe my device. Thank you again for any clarification.
Click to expand...
Click to collapse
well.. yes and no. root has slightly changed since 6.0.1. and i mean slightly.
1. unlock your bootloader(which will wipe your device, so move what you need to your computer). boot up once after this as well.
2. flash the twrp recovery to your phone via fastboot.
3. flash any nexus 6 custom kernel with twrp(new step)
4. flash the latest SuperSU zip(for root)
5. reboot.
the custom kernel will let you obtain root, its needed in there as of 6.0.1. oh, then don't delete the /system/app/ folder, delete the google fi app folder with its apk inside. otherwise you'll delete all your system apps.
simms22 said:
well.. yes and no. root has slightly changed since 6.0.1. and i mean slightly.
1. unlock your bootloader(which will wipe your device, so move what you need to your computer). boot up once after this as well.
2. flash the twrp recovery to your phone via fastboot.
3. flash any nexus 6 custom kernel with twrp(new step)
4. flash the latest SuperSU zip(for root)
5. reboot.
the custom kernel will let you obtain root, its needed in there as of 6.0.1. oh, then don't delete the /system/app/ folder, delete the google fi app folder with its apk inside. otherwise you'll delete all your system apps.
Click to expand...
Click to collapse
Ok. So do I still obtain root with the fastboot procedure linked in the FAQ? If not, can you link to a current guide for unlocking the bootloader and flashing the TWRP. I'm also not sure where to get a custom kernal, or which one. After that I think I got it. Thanks.
wats6831 said:
Ok. So do I still obtain root with the fastboot procedure linked in the FAQ? If not, can you link to a current guide for unlocking the bootloader and flashing the TWRP. I'm also not sure where to get a custom kernal, or which one. After that I think I got it. Thanks.
Click to expand...
Click to collapse
you can always check if you have root by downloading and installing a terminal emulator app from the play store, then open it and type su. if you have root, it'll return a #
simms22 said:
you can always check if you have root by downloading and installing a terminal emulator app from the play store, then open it and type su. if you have root, it'll return a #
Click to expand...
Click to collapse
I don't have root, I've never touched this phone. I'm just trying to make sure I understand the correct way to obtain root in 6.0.1. Your post made it sound like maybe that guide I linked wasn't the current way?
wats6831 said:
I don't have root, I've never touched this phone. I'm just trying to make sure I understand the correct way to obtain root in 6.0.1. Your post made it sound like maybe that guide I linked wasn't the current way?
Click to expand...
Click to collapse
no, it is the correct way. I just added that a kernel has to be flashed as well. but chainfire might have fixed that, I heard that a few hours ago. if he did, then the method is correct. I rooted over a year ago, my n6. so its been a while :angel:
I understand. Thank you for making that clear. I can't even root due to USB driver issues...not sure why. I followed the steps exactly.
I've switched to SuperSU 2.66, so I've just checked it, and you don't need a custom kernel for it anymore, just flash ir frim TWRP.
Sent from my Nexus 6 running cyosp using Tapatalk
simms22 said:
sure, its very easy, but you need root to remove it, since its a system app. just use a root file explorer to find it in /system/app/, then delete it and reboot. when you boot up, it'll be gone. or, you can perform a factory reset, then boot up first time with your Verizon sim in the phone. then the app will go back into hiding in your system partition.
Click to expand...
Click to collapse
So I unlocked, and rooted with Wugster and SUperSU. I booted first time with my Verizon SIM and project Fi app is still there. I can see it in my apps list, but i can't see it in the system/app/ any clue where it is? thanks.
It's in #/data/user/0/com.google.android.apps.tycho
somewhere but i can't find it
wats6831 said:
So I unlocked, and rooted with Wugster and SUperSU. I booted first time with my Verizon SIM and project Fi app is still there. I can see it in my apps list, but i can't see it in the system/app/ any clue where it is? thanks.
It's in #/data/user/0/com.google.android.apps.tycho
somewhere but i can't find it
Click to expand...
Click to collapse
it has a weird name, not fi. its like tycho or something similar. if you look into that folder, its there.
simms22 said:
it has a weird name, not fi. its like tycho or something similar. if you look into that folder, its there.
Click to expand...
Click to collapse
ok looking in that folder, i see nothing in any subfolder except for a file called "Switching.xml"
Should I delete the whole tycho folder?
The ProjectFi app is "Tycho"
You can also remove GCS (Google Connectivity Services). Only ProjectFi uses it for joining open wifi networks and the Google VPN, among other things. Totally useless unless you're a Fi'er.
Gandalf said:
The ProjectFi app is "Tycho"
You can also remove GCS (Google Connectivity Services). Only ProjectFi uses it for joining open wifi networks and the Google VPN, among other things. Totally useless unless you're a Fi'er.
Click to expand...
Click to collapse
So to be clear should I delete the whole Tycho folder? I don't want the app to show up at all in my app list.
Can GCS be removed or does it have to be deleted in /system/app? thanks.
wats6831 said:
So to be clear should I delete the whole Tycho folder? I don't want the app to show up at all in my app list.
Can GCS be removed or does it have to be deleted in /system/app? thanks.
Click to expand...
Click to collapse
You can delete it but I would recommend either Disabling it in Settings > Apps or using Titanium Backup to freeze it. Assuming you're running stock, mounting system rw will cause issues with verity