I am seeing a lot of posts with questions about the local.prop file. If any of you are having permission issues enable mass storage mode then open notepad on your computer and type " ro.kernel.qemu=1" then click save as and name it local.prop and save it in the /data folder on the phone. DO NOT wipe data after creating this file or it will be deleted. Then re-enable internet connection mode and USB debugging and proceed with the rooting process.
how bout for us guys in test mode?
You could either push it with adb or copy to the external SD with a card reader then use a file browser to copy it into the /data folder.
is this the correct way?
first flash v7 stock..then root..then make a local.prop..save it..use lgnpst to update to zv8??? then I would still be rooted?
wslguy said:
I am seeing a lot of posts with questions about the local.prop file. If any of you are having permission issues enable mass storage mode then open notepad on your computer and type " ro.kernel.qemu=1" then click save as and name it local.prop and save it in the /data folder on the phone. DO NOT wipe data after creating this file or it will be deleted. Then re-enable internet connection mode and USB debugging and proceed with the rooting process.
Click to expand...
Click to collapse
I started a thread earlier today about similar problems. I will try this when I get home tonight and let everyone know the results.
EDIT: Problem with this method is what I mention on my other thread http://forum.xda-developers.com/showthread.php?p=24741989#post24741989
I can't move files into the /data folder because the permission denied error message I get. Oddly enough, I only started getting these weird permission problems after I took the advice from keithmcelhinney (basically saying do the same code but within the terminal emulator.. which I thought I did successfully)
http://forum.xda-developers.com/showthread.php?t=1580571&highlight=ro+kernel+qemu=1
is there a tool or something that can fix permissions without CWM or moving files internally?
If you already have root you can download an app call fileslick to change permissions on the /data folder so you can paste a new local.prop in there. Although I was able to successfully change permissions and copy my local.prop file, I was still unable to get the OTA update to zv8.
Here is a snippet from another post where he is trying to OTA update from vz7 to vz8 while keeping root and reinstalling cwm: http://forum.xda-developers.com/showthread.php?t=1580987
1 - Using LGNPST, push the ZV7 .tot file.
2 - Factory reset, just in case
3 - Using the OLD AIO (Root&RecoveryAIO), root it (option 1 only!).
4 - Use Check Root app to make sure you have root
5 - Use fileslick app to Change folder permissions and move local.prop file app to
- Open fileslick, click actions, and click show root
- Swipe all the way left until you are at root and see /data folder
- Tap the data folder so it has a green check and then hit actions and select "permisions"
- Check everything in that menu (This will make it so you don't has any permission denied menus when moving the local.prop)
- Put the local.prop file from the "data" folder in the ZV7toZV8Root.zip by tapping it in fileslick, navigating back to the "/data" folder you just set permissions for, clicking "actions" and clicking "copy file to this location"
6 - Go to about this phone in the settings app and check for updates to update ZV8
7 - After reboot use ZV8CWMRecovery.bat (option 1) to install clockwork
8 - After reboot go back and use OLD AIO (Root&RecoveryAIO) to reboot to recovery (option 7)
9 - Reboot recovery and wipe data
10 - After wiping data and without exiting CWM, flash BrokenOut.
11 - DON'T WIPE DATA AFTER FLASH
I have been trying for hours to install a custom recovery in my AT&T Atrix HD (mb886) phone. Every time I go through the flashing process, no matter what recovery I try, and whether I use the stock SDK fastboot or one of alternatives, when I try to boot into recovery, I get an ominous error message about how my bootloader is unlocked, and Motorola and ATT will not honor the warranty, and so on. However - it then always boots into the normal startup. I did try holding down both volume buttons when I cycled the power button, and I briefly (about 5 seconds, maybe?) got what looked like a text-based recovery menu, but then the error message popped up again, and I'm back to ????? is going on.
Any help? I have read a number of article/forums online, but all assume that your recovery is working so you can install a custom ROM. I have done this on a couple of Android tablets in the past, so I know I'm not totally stupid, but I can't seem to get past the AT&T nanny.
How can I fix this?
Android 4.1.1
System 98.4.20.MB886.ATT.en.US
If I remember correctly, I had to rename install-recovery.sh (or something like that) by adding .bak to the end of the filename. Boot into fastboot, flash your recovery, and try to boot into recovery.
Nevadadave said:
I have been trying for hours to install a custom recovery in my AT&T Atrix HD (mb886) phone. Every time I go through the flashing process, no matter what recovery I try, and whether I use the stock SDK fastboot or one of alternatives, when I try to boot into recovery, I get an ominous error message about how my bootloader is unlocked, and Motorola and ATT will not honor the warranty, and so on. However - it then always boots into the normal startup. I did try holding down both volume buttons when I cycled the power button, and I briefly (about 5 seconds, maybe?) got what looked like a text-based recovery menu, but then the error message popped up again, and I'm back to ????? is going on.
Any help? I have read a number of article/forums online, but all assume that your recovery is working so you can install a custom ROM. I have done this on a couple of Android tablets in the past, so I know I'm not totally stupid, but I can't seem to get past the AT&T nanny.
How can I fix this?
Android 4.1.1
System 98.4.20.MB886.ATT.en.US
Click to expand...
Click to collapse
That warning you see is just the boot logo and can be gotten rid of by flashing a custom logo. Stock Moto boot logos on this platform have two images -- one for locked and another for unlocked bootloaders. It's a non issue and just confirms that the bootloader is unlocked.
You accessed that menu by powering up and holding both volumes and power. Volume down scrolls and volume up selects in there.
To install a custom recovery, boot into fastboot mode and flash it with fastboot. Mythtools, maybe BootMyHD, can do that for you if you don't have moto-fastboot binary or are unable to run "moto-fastboot flash recovery recovery.img" with your phone plugged into a rear usb port in fastboot mode with a terminal/command prompt open to the directory with the recovery image.
More questions
audit13, how do I access that file to change the name? I tried again this morning, and after doing the boot to recovery key sequence, I got a menu, and before it went away, I selected boot to recovery, but got the dead android icon. I tried several other options and it just did a normal boot. Still stumped.
skeevydude, I have tried installing a couple of custom recoveries, using fastboot, and when I do, I get a message saying all went well, but when I boot up, it either does the "failed Android" or just boots up normally. I'll try Mythtools and BootMyHD, but it seems that there is something else going on here.
Nevadadave said:
audit13, how do I access that file to change the name? I tried again this morning, and after doing the boot to recovery key sequence, I got a menu, and before it went away, I selected boot to recovery, but got the dead android icon. I tried several other options and it just did a normal boot. Still stumped.
skeevydude, I have tried installing a couple of custom recoveries, using fastboot, and when I do, I get a message saying all went well, but when I boot up, it either does the "failed Android" or just boots up normally. I'll try Mythtools and BootMyHD, but it seems that there is something else going on here.
Click to expand...
Click to collapse
Maybe something else going on. Are you flashing using the rear usb port of your PC? It really does matter.
To answer the first question about install-recovery, once you're rooted, use Root Explorer or something similar, mount /system as read/write, go to /system/etc, rename the file install-recovery.sh to install-recovery.sh.bak, and reboot.
If you have adb installed on your PC you can do
adb root
adb shell mount -o remount,rw /system
adb shell cp /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
adb shell rm /system/etc/install-recovery.sh
adb reboot
I'll try it and see what happens
skeevydude said:
Maybe something else going on. Are you flashing using the rear usb port of your PC? It really does matter.
To answer the first question about install-recovery, once you're rooted, use Root Explorer or something similar, mount /system as read/write, go to /system/etc, rename the file install-recovery.sh to install-recovery.sh.bak, and reboot.
If you have adb installed on your PC you can do
adb root
adb shell mount -o remount,rw /system
adb shell cp /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
adb shell rm /system/etc/install-recovery.sh
adb reboot
Click to expand...
Click to collapse
OK, I did not know about USB port preference. I'll try it and see what happens. Thanks!
No joy
Nevadadave said:
OK, I did not know about USB port preference. I'll try it and see what happens. Thanks!
Click to expand...
Click to collapse
Well, I tried front and back USB ports, in all cases, adb says "adb can't run as root in production builds". adb sees the phone, but about all I can do is start fastboot, but once there adb doesn't work until I reboot.
I tried running the remount command, but got a message, "Operation not permitted" I'm assuming because I could not root into the phone. Titanium backup shows that the phone is, indeed, rooted.
Stuck again...
Install Root Explorer, find the file, add .bak to the end, reboot to fastboot, install Philz, boot into recovery.
audit13 said:
Install Root Explorer, find the file, add .bak to the end, reboot to fastboot, install Philz, boot into recovery.
Click to expand...
Click to collapse
I tried that, got a "Rename failed". It appears that the file is set to read-only, and the Root Explorer doesn't seem to have a way to change that. I'm open to additional suggestions. I had thought that root access would allow me to do things like change file permissions, but I cannot do this with Root Explorer. Everything I try, I get a message that it can't be done, because the file system is read-only.
At the top of the file list, it says "mounted as r/o, but nothing shows to change that, although I see num,erous web posts that claim that there should be a "R/W" button somewhere.
Better luck
Nevadadave said:
Well, I tried front and back USB ports, in all cases, adb says "adb can't run as root in production builds". adb sees the phone, but about all I can do is start fastboot, but once there adb doesn't work until I reboot.
I tried running the remount command, but got a message, "Operation not permitted" I'm assuming because I could not root into the phone. Titanium backup shows that the phone is, indeed, rooted.
Stuck again...
Click to expand...
Click to collapse
OK, I dropped Root Explorer and loaded ES File Explorer. ES Explorer allowed me to change the file R/W permissions and rename the stock recovery file.
adb would still not allow me to get to root, so I loaded adbd insecure from the Play store, and that gave me root access. I flashed the CWR 6.0.4.4, and so far (fingers crossed) I was able to boot to CWM and I'm backing up my system now. Hopefully, the next update will be to say that I have a new ROM installed...
Nevadadave said:
OK, I dropped Root Explorer and loaded ES File Explorer. ES Explorer allowed me to change the file R/W permissions and rename the stock recovery file.
adb would still not allow me to get to root, so I loaded adbd insecure from the Play store, and that gave me root access. I flashed the CWR 6.0.4.4, and so far (fingers crossed) I was able to boot to CWM and I'm backing up my system now. Hopefully, the next update will be to say that I have a new ROM installed...
Click to expand...
Click to collapse
All you need to gain r/w access is to click on the ro button to change it to read/write.
audit13 said:
All you need to gain r/w access is to click on the ro button to change it to read/write.
Click to expand...
Click to collapse
Audit13 I'm not sure what you mean here. Root Explorer never indicated a "R/O" button or any other way to change permissions, it just kept saying that the file system was write-protected. ES File Explorer was very easily able to change this and allow me to remove the automatic recovery overwrite.
So, at this point, I have Cyanogen 10.2 running on my Atrix HD, and although I have found a few glitches, it is faster and it is now MINE!
Nevadadave said:
Audit13 I'm not sure what you mean here. Root Explorer never indicated a "R/O" button or any other way to change permissions, it just kept saying that the file system was write-protected. ES File Explorer was very easily able to change this and allow me to remove the automatic recovery overwrite.
So, at this point, I have Cyanogen 10.2 running on my Atrix HD, and although I have found a few glitches, it is faster and it is now MINE!
Click to expand...
Click to collapse
In Root Explorer, You'll see the words "Mounted as r/o". To the right will be a button that says "Mount R/W".
I went with Validus 5.1 over 10.2.
I've been trying for sometime now to install a custom rom (CM11 or anything else for that matter) on my Atrix HD. I got as far a unlocking my boot loader so now every time I reboot, I get a scary warning message saying, my phone has been tampered with.
I've made several attempts to install CWM and even though it seems to install, if I try to boot my phone by holding the power and volume down buttons at the same time, it seems to do nothing, or it will just boot normally. I did try to hold down the power and volume up and volume down buttons and that leads to a menu. One of the options was recovery. I selected that, but then a display of android robot with a red triangle.
Can anyone give me some tips on what I'm doing wrong. I'm a programmer, but I have no experience with android, so you can stay technical but not too "android specific" technical.
Thanks,
Mark
Are you installing it via fastboot? Once you flash recovery, do not allow the phone the reboot. Try and boot into recovery.
If you still can boot into cwm, boot the phone, install Root Explorer, and rename recovery.sh to recovery.sh.bak, boot to fastboot, install cwm, and boot into cwm.
audit13 said:
Are you installing it via fastboot? Once you flash recovery, do not allow the phone the reboot. Try and boot into recovery.
If you still can boot into cwm, boot the phone, install Root Explorer, and rename recovery.sh to recovery.sh.bak, boot to fastboot, install cwm, and boot into cwm.
Click to expand...
Click to collapse
These are the commands I used.
adb devices
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery.img
fastboot reboot
Where recovery.img was the CWM one.
Based on another thread, I attempted to rename ~/system/etc/install_recovery.sh, but even though I'm rooted, ES File Explorer not Root File Explore is able to rename that file.
Any help would be appreciated.
Thanks,
Mark
After renaming the file, stock recovery still comse up?
Sorry, there was a typo. I was NOT able to rename the file.
Use root explorer to do it. That's what I did.
audit13 said:
Use root explorer to do it. That's what I did.
Click to expand...
Click to collapse
I had tried that.
I had installed
ES File Explorer
Root File Explorer
Root File Manager Explorer
All seemed to either give an error or just not change the name. Is there a trick? I'm pretty sure my phone is rooted since I am prompted to ask permission to do these things. I think if I can get past this the renaming issue, I may actually be able to install a new rom. Can you help?
Thanks,
Mark
Did you change the permission in root explorer to r/w from r/o?
Can you be more specific about "root explorer" which app is it. I've used a couple of root file explorers and none of them can seem to rename /system/etc/install-recovery.sh.
I tried to use Root File Manager to change the permissions on that file to have write permissions. The problem is that it says it does, but then when I look again, it's unchecked.
I checked the /system/etc folder and it has write permissions for "owner". I tried to create a test folder in it. It said it was granted permission, but in the end, the test folder was not created.
Maybe my phone is not rooted properly?
I'm not sure at which point in the rooting process I got this, but I have an app named "#SuperSU". If I open it and check it's logs, I can now see an error message saying "SuperSU Pro is required for this feature". Did I screw up with rooting? Should I use something else. Any help to remedy this would be greatly appreciated.
Thanks,
Mark
markdemich said:
Can you be more specific about "root explorer" which app is it. I've used a couple of root file explorers and none of them can seem to rename /system/etc/install-recovery.sh.
I tried to use Root File Manager to change the permissions on that file to have write permissions. The problem is that it says it does, but then when I look again, it's unchecked.
I checked the /system/etc folder and it has write permissions for "owner". I tried to create a test folder in it. It said it was granted permission, but in the end, the test folder was not created.
Maybe my phone is not rooted properly?
I'm not sure at which point in the rooting process I got this, but I have an app named "#SuperSU". If I open it and check it's logs, I can now see an error message saying "SuperSU Pro is required for this feature". Did I screw up with rooting? Should I use something else. Any help to remedy this would be greatly appreciated.
Thanks,
Mark
Click to expand...
Click to collapse
I upgraded to SuperSU Pro. It was only $2.50. Now the log says, "Unable to chmod /system/etc/install-recovery.sh: Read-only file system"
This happened when trying to give write permissions to that file. Am I doing something wrong?
if your adb is setup and working try using this command in adb 'adb reboot recovery' and see if the phones boots to little android with its heart open given a excalmation mark there press all three buttons at the same time and recovery should open
mega_man said:
if your adb is setup and working try using this command in adb 'adb reboot recovery' and see if the phones boots to little android with its heart open given a excalmation mark there press all three buttons at the same time and recovery should open
Click to expand...
Click to collapse
I did that and when the screen you described displayed, pressed the power, and center of the volume up and down rocker switch so I can get but up and down. After a few seconds the screen went blank and I let go. The phone then just booted normally without going into recovery.
markdemich said:
I upgraded to SuperSU Pro. It was only $2.50. Now the log says, "Unable to chmod /system/etc/install-recovery.sh: Read-only file system"
This happened when trying to give write permissions to that file. Am I doing something wrong?
Click to expand...
Click to collapse
Root Explorer: https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer&hl=en
audit13 said:
Root Explorer: https://play.google.com/store/apps/details?id=com.speedsoftware.rootexplorer&hl=en
Click to expand...
Click to collapse
Thanks. I purchased that app and when I tried to set the permissions of the file it prompted to mount the volume with write permissions. Once it did that, everything else worked.
Thanks again,
Mark
Currently irate because I already typed all this then hit enter to be told I can only register once from this ip.
Any way...
Rooted vs98027a Android 4.4.2 via Stump Root
Used AutoRec which installed TWRP 2.7.00
Backed up Stock Rom
Mount button is missing
Rebooted into Stock to transfer backup to PC and place "cm-12-20150603-NIGHTLY-vs980.zip" as well as Lp gapps.
Rebooted back into TWRP
Wiped, then Installed the CM Nightly, wiped cache and rebooted.
Stuck in LG Boot loop.
Use buttons to boot back into TWRP, open Restore and It's just a blank navigation window.
TWRP just became ****ing worthless
Tried to wipe and possibly install same CM again. Still boot looping.
Tried getting to download mode, but it reboots before installing driver.
I have not a clue as to what to do next.
I can't get it to mount.
ADB Sideload Fails.
Terminal Command lets me select a blank navigation window.
And my original file structure is in like sdcard/0/0/0/0/0/0/0/0/ etc.
Please help, or at least redeem CM and TWRP's value somehow, because this is bs.
I sort of fixed it.
Restore showed up blank, because within the many /0/0/0/0/0/0/0/0 a new TWRP folder would be made or course containing nothing.
I also learned the adb is this magnificent goddess that can do things even when your phone can't.
Throughout further reading I glimpsed upon something about "loki" files that aren't compatible with specific versions of twrp or something. So If you've also been through this and still feel brave enough to flash a custom, then make sure you get the newest version of twrp...
As for the Restore issue, assuming you have a backup saved on pc, wipe everything then adb push the whole file (TWRP/BACKUPS/BLAHBLAH/BLAUGHESDIHF) to /sdcard/.... then it should show up in restore, if it doesn't then use file manager to place it in the right TWRP directory... You can also use the file manager to move the restore folder to the "correct" twrp folder if you don't have it backed up.