Related
Hello All,
I have been in and out of every Dev and General forum about installing the CWM on Z8. Unfortunately I have yet to find a solid solution to the below errors when using MTM's ZV8CWMRecovery bat. I would be posting in related thread on the dev site, but I don't have enough posts to post in there. So far I have seen multiple users with this problem:
Recovery for ZV8
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Device found
Mounting Device
remount failed: Operation not permitted
Pushing Recovery
5152 KB/s (5345280 bytes in 1.013s)
Installing CWM Recovery
/dev/block/mmcblk0p14: cannot open for write: Permission denied
Remove Trash
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/recovery-from-boot.p, Read-only file system
rm failed for /data/local.prop, No such file or directory
CWM Recovery!!!
Press any key to continue . . .
I have only seen a couple answers to this that actually address the error messages. One being to manually copy the local.prop into the data folder. I have tried taking the local.prop file and moving it to /data but when I do I get the error message on my phone saying java.io.filenotfoundexception:/data/local.prop (permission denied).
I feel that this has something to do with Superuser mainly because when I have tried to use other methods like using quick boot or Rom Manager to boot into recovery, I get messages saying that Super User has denied access.
1) Is anyone else having similar Super User problems when they get the CWM installation error above?
2) Can anyone think of a correlation bewtween the super User error and the CWM installation errors?
3) Can anyone give any usefull insight into what these mean?
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/recovery-from-boot.p, Read-only file system
rm failed for /data/local.prop, No such file or directory
Any support is much appreciated.
im having same problem
williep said:
im having same problem
Click to expand...
Click to collapse
I am going to try the suggestion in this thread right now.
http://forum.xda-developers.com/showthread.php?t=1594369
I will let you know.
OK, I have decided that my main problem right now is that SuperUser is denying access to every program that could help me (Quick boot, Rom Manager, Terminal emulator). Every time I try and run any of those I get a message saying it was blocked by SU. I have set SU to allow all requests, yet it still Denies access?
Anyone with Ideas on how to stop this without starting from scratch?
Plumbert said:
OK, I have decided that my main problem right now is that SuperUser is denying access to every program that could help me (Quick boot, Rom Manager, Terminal emulator). Every time I try and run any of those I get a message saying it was blocked by SU. I have set SU to allow all requests, yet it still Denies access?
Anyone with Ideas on how to stop this without starting from scratch?
Click to expand...
Click to collapse
Sounds like the phone did not root properly. I had that problem before where i had superuser but no root access to anything. My solution was starting over from scratch, im not sure how to do it w/o starting over. If you have everything on the computer already then starting over should only take 15 mins or so. For me thats how long it took after i had all downloads and installs in place
Sent from my VS910 4G using xda premium
jimmyhawk said:
Sounds like the phone did not root properly. I had that problem before where i had superuser but no root access to anything. My solution was starting over from scratch, im not sure how to do it w/o starting over. If you have everything on the computer already then starting over should only take 15 mins or so. For me thats how long it took after i had all downloads and installs in place
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
Thanks for the info. I did end up starting from scratch and the superuser thing was definitely a root problem. However, I still have one problem preventing me from the upgrade which is that every time I try to copy any file to the /data folder i get the java.io.filenotfoundexception:/data/local.prop (permission denied) that I mentioned above... I cannot figure out what permissions I need to change or how
Plumbert said:
Thanks for the info. I did end up starting from scratch and the superuser thing was definitely a root problem. However, I still have one problem preventing me from the upgrade which is that every time I try to copy any file to the /data folder i get the java.io.filenotfoundexception:/data/local.prop (permission denied) that I mentioned above... I cannot figure out what permissions I need to change or how
Click to expand...
Click to collapse
Sorry i am unfamiliar with that one
Sent from my VS910 4G using xda premium
Plumbert said:
Thanks for the info. I did end up starting from scratch and the superuser thing was definitely a root problem. However, I still have one problem preventing me from the upgrade which is that every time I try to copy any file to the /data folder i get the java.io.filenotfoundexception:/data/local.prop (permission denied) that I mentioned above... I cannot figure out what permissions I need to change or how
Click to expand...
Click to collapse
Give this a shot:
http://forum.xda-developers.com/showthread.php?t=1594369
I was getting the same errors. If you choose option two in the .bat it will reboot you to cwm.
Sent from my VS910 4G using Tapatalk 2
Never had to do anything with the local.prop file
Sent from my VS910 4G using Tapatalk 2
MacK1ll3r said:
Never had to do anything with the local.prop file
Sent from my VS910 4G using Tapatalk 2
Click to expand...
Click to collapse
I am having this problem also, but only on my new revo (came with Zv8 my old one that came with Zv4 that is stuck in test mode worked flawlessley with MT's AIO root&Recovery App, The new one worked once i flashed TOT back to zv7 then kept root through to Zv8 but then it wouldnt install CWM or anything for that matter, All of MT's .Bats dont work no matter how many times i flash or hard reset i think something is in new software, be it LG verizon or SuperUser i dont know, but are all you people having trouble having it on Newer Phones?
Anyone know if it is possible to root a Motorola Droid 4 running Android 4.1.2? I have seen several videos and directions online for using razr_blade but they don't seem to work and I think its because my system version is XT894.
I downloaded the latest Motorola drivers and made sure USB debugging was set to on. Yet, when running the exploit, it doesn't seem to see the device. Any ideas?
Sent from my DROID4 using xda app-developers app
cities7 said:
Anyone know if it is possible to root a Motorola Droid 4 running Android 4.1.2? I have seen several videos and directions online for using razr_blade but they don't seem to work and I think its because my system version is XT894.
I downloaded the latest Motorola drivers and made sure USB debugging was set to on. Yet, when running the exploit, it doesn't seem to see the device. Any ideas?
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
Different cable? My xt894 rooted just fine with RAZR blade. :-/
Sent from my DROID4 using xda app-developers app
All you need to do is make sure you are running the JB OTA update and have the latest motorola drivers. Install motocast, moto drivers from their website, whatever you can find. Assuming the drivers are okay after that, download Razr Blade, unzip the file, run the file called "run" and follow the onscreen instructions.
check your device manager, if there is yellow triangle in front of xt894
you need to update drivers
Sent from my Clear using xda premium
Thank you both for your responces. As soon as I get somewhere with internet access I'm going to try again.
Sent from my DROID4 using xda app-developers app
i also was looking for a 4.1.2 root and found the razr_blade method
and ya it worked ;=)
used this files:
https://docs.google.com/file/d/0B_nizg6yUZ0NRjVTZlQ0d1hXVVU/edit?pli=1
any tuto?
Hey everyone!
any link with razr_blade method tutorial?
I'm also at 4.1.2 using a xt894
huhu1312 said:
i also was looking for a 4.1.2 root and found the razr_blade method
and ya it worked ;=)
Click to expand...
Click to collapse
here is a video, he is rooting a razr, but same root program
http://youtu.be/XDV_72mPt4k
Try using Linux, the mod works better in Linux and use the Droid 4 JB utility,that you can find in the D4 Development forums and that should work great for you. It rooted my D4 just fine.
Sent from my DROID4 using xda premium
Help me unf*ck myself please
Using the LinuxMacUtility...
I removed the log redirects to null and found this:
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Phase three (this will take a minute)...
failed on '/data/logger' - Permission denied
mkdir failed for /data/logger, File exists
Unable to chmod /data/logger: Operation not permitted
rm failed for /data/logger/last_apanic_console, Permission denied
link failed File exists
[*] Rebooting device...
[*] Waiting for phone to reboot.
I loaded the 4.1.2 firmware per the utlity, wiped. I tried to root, no luck. Logs show the above. Is the exploit closed?
--#
try
-Settings > Apps > Smart Actions > Clear data
-Settings > Storage > ≡ Button > USB computer connection > Select "Media device (MTP)
or run http://vulnfactory.org/public/razr_blade.zip
in windows
Error trying to root
I'm following the instructions step by step and I have tried everything to root my Droid 4 running 4.1.2, I get stuck at phase 3 and this comes up
>failed on `/data/logger’ – Permission Denied
>mkdir failed for /data/logger, File exists
>Unable to chmod /data/logger: Operation not permitted
>link failed File exists
any help would be greatly appreciated. I already tried to clear cache and data on smart tasks, Tried to connect as media device and camera with no luck, please help.
miselonez said:
I'm following the instructions step by step and I have tried everything to root my Droid 4 running 4.1.2, I get stuck at phase 3 and this comes up
>failed on `/data/logger’ – Permission Denied
>mkdir failed for /data/logger, File exists
>Unable to chmod /data/logger: Operation not permitted
>link failed File exists
any help would be greatly appreciated. I already tried to clear cache and data on smart tasks, Tried to connect as media device and camera with no luck, please help.
Click to expand...
Click to collapse
try this
DarkMatterM4 said:
I GOT ROOT! I'm going to structure this post in such a way so that it will be easily searchable by those who are having the same problem.
The issue that I was having was that the RAZR Blade exploit was giving me the following errors when trying to root:
failed on '/data/logger' - Permission denied
mkdir failed for /data/logger, File Exists
Unable to chmod /data/logger: Operation not permitted
link failed File exisits
Device: Droid 4
Network: Verizon
System: XT894
Android version: 4.1.2
What I did to solve the problem:
-Settings > Apps > Smart Actions > Clear data
-Settings > Storage > ≡ Button > USB computer connection > Select "Media device (MTP)
-Ran the exploit again. Went through with no errors. Upon reboot I had root access.
After I had root access, I went back to the USB computer connection and changed back to Mass Storage mode.
Thanks for all of the help you guys gave me. I really appreciate it!
Click to expand...
Click to collapse
sd_shadow said:
try this
Click to expand...
Click to collapse
Tried, still a no go, still getting the same error msgs at phase 3, I just don't get what i'm doing wrong here...sigh
did you check windows device manager?
see Driver Errors
Yes, it seems that drivers are all there, it comes up as ADB Interface, MOT composite ADB Interface.
xp, win 7, 8?
Win 7 Pro 32 bit, yes, I am admin and only user.
try a different usb port, if desktop, use rear rather than front
Tried that as well.
Hi, everybody!
Several days ago i've got OTA update from VERIZON. You can download it from attach.
Changelog from official Motorola site
I agreed and installed this update. After it i had 98.72.18-8 SW version.
So, i have had the trouble: i couldn't got root rights by Dan Rosenberg exploit - Motorola fixed the way, we had root on previous JB 98.72.18 and 98.72.18-2 !
After analysing install-script file from OTA update and thinking around it i decided to downgrade with RSDLite to 98.72.18 and do some manipulations with SU binary:
Start point: 98.72.18-2 installed, rooted
Code:
adb kill-server
adb start-server
sleep 5
adb shell su -c "mount -o remount,rw /system"
adb shell su -c "cd /system/bin/ && mv run-as run-as2 && mv /system/xbin/su run-as" #because of script do chmod on this file
adb reboot recovery
#turn on Sideload manually in recovery
adb sideload Blur_Version.98.72.182.XT894.Verizon.en.US.zip
sleep 400
adb kill-server
adb start-serversleep 5
adb shell run-as -c "mount -o remount,rw /system" #i used RUN-AS instead SU =)
adb shell run-as -c "cd /system/bin/ && mv run-as /system/xbin/su && mv run-as2 run-as"
adb shell su -c "chmod 6755 /system/bin/su"
this way gave me root rights for adb Shell, but applications still not getting root.
Any ideas, how to fix?))
Sorry for mistakes, i've tryed to avoid it)
way to fix
So, i fixed it!
1. At the start, we have 98.72.182 system, rooted by Dan Rosenberg exploit
2. Installing Safestrap recovery
3. Downloading on sdcard-ext latest SuperSU
4. Under Safestrap, installing UPDATE-SuperSU-v1.89.zip
5. Reboot to stock Android, bying SuperSu pro key, installing
6. Going to settings, and uncheck Screen block (set NONE)
7. Going to Superuser -> settings, install checkboxes: Survival mode, Enable su during boot, Trust system user
8. Reboot to the stock recovery, installing OTA update
9. Booting to OS.... (After booting you can return screen block )
10. Enjoy!
Orrrrrrrr update su binaries and back up root with voodoo. Temp disable root install update then voodoo. Restore root and enjoy... now I can only say because this is what worked for me without all the extra hoopla
Sent from my DROID4 using Tapatalk
rruleford said:
Orrrrrrrr update su binaries and back up root with voodoo. Temp disable root install update then voodoo. Restore root and enjoy... now I can only say because this is what worked for me without all the extra hoopla
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
I can take a video with Vodoo, which will fail with restoring root.
Before posting, i've tryed voodo ota keeper, and ota keeper function in another superuser software)
Thanks for the heads up on the update breaking root. I'll have to wipe my phone and start fresh before I do the update......unless I go kitkat.
Update.....
I tried voodoo and the OTA would not come through for me. It looks like the update will be more complicated than it's worth so the kitkat rom's will be in my near future.
Voodooo worked for me on latest O.T.A
karlsdroids said:
Thanks for the heads up on the update breaking root. I'll have to wipe my phone and start fresh before I do the update......unless I go kitkat
Click to expand...
Click to collapse
Voodooo worked for me on latest O.T.A
rruleford said:
Orrrrrrrr update su binaries and back up root with voodoo. Temp disable root install update then voodoo. Restore root and enjoy... now I can only say because this is what worked for me without all the extra hoopla
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
mercermtn said:
Voodooo worked for me on latest O.T.A
Click to expand...
Click to collapse
Voodoo worked for me too. Just got the OTA notice today from VZW. Followed rruleford's steps and it worked.
This was my first time using Voodoo, and possibly my imagination or possibly not - but something funky happned where I needed to reboot the phone and re-check enable in SuperSU, which was obscured by the fact Voodoo was stating it ~had~ root...
So, is there anything besides these bugfixes in the update? Any Android version updates or maybe a fix for the Shift key behaving like a lunatic?
Dang.
My wife already applied the update to her D4 and now I've lost root on that device. Can anyone advise me what to do? Should I use RSDLite like OP states? I am confused because Moto SBF page says "never flash an older version"...
tried using voodoo and the update wouldn't work...dono what to do.
svrnmnd said:
tried using voodoo and the update wouldn't work...dono what to do.
Click to expand...
Click to collapse
Did you disable SuperSU after you backed up w/ Voodoo?
Negative, how do I disable? NOTE I use superuser not superuserSU
Sent from my DROID4 using xda app-developers app
svrnmnd said:
Negative, how do I disable? NOTE I use superuser not superuserSU
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
Im not 100% sure w/Superuser - its probably similar: in settings uncheck 'Enable Superuser'
Also - if anyone out there has info on helping me w/ my wifes D4 here (a couple posts up) I would appreciate it...
bigmatty said:
Im not 100% sure w/Superuser - its probably similar: in settings uncheck 'Enable Superuser'
Also - if anyone out there has info on helping me w/ my wifes D4 here (a couple posts up) I would appreciate it...
Click to expand...
Click to collapse
Looks like you'll have to wait for a new method to be released orrrrr if another d4 is available that's rooted try downloading voodoo on both devices and backup root on rooted device then copy backup file to unrooted phones voodoo directory and try to restore that way and don't forget to update su binaries
Sent from my XT894 using Tapatalk
rruleford said:
Looks like you'll have to wait for a new method to be released orrrrr if another d4 is available that's rooted try downloading voodoo on both devices and backup root on rooted device then copy backup file to unrooted phones voodoo directory and try to restore that way and don't forget to update su binaries
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
Awesome - thanks for the reply! Yes, I have my D4 same as hers, working well and w/ a Voodoo backup... I had considered this, but couldn't find the Voodoo file backup location. Do you by chance know where it is?
Why are y'all struggling so much with this.
1. You don't need to unroot.
2. You don't need to unfreeze anything.
3. RAZR_BLADE root method still works. You have to clear cache and data and force close Smart Actions before re-rooting.
I've done three Droid 4's already. All had different apps/services frozen via Titanium Backup and all were of course rooted. One (mine) got the SOAK at version .188 and the other two got the roll out at version .189.
Install update, clear Smart Actions and re-root with the razr_blade method .bat files.
Simple, works and reauthorizing Titanium Backup will refreeze all the apps you had frozen before the update.
Sent from my Nexus 10 using Tapatalk
bigmatty said:
Awesome - thanks for the reply! Yes, I have my D4 same as hers, working well and w/ a Voodoo backup... I had considered this, but couldn't find the Voodoo file backup location. Do you by chance know where it is?
Click to expand...
Click to collapse
Not to sure as I deleted all mine when installing cm11 on stock ROM slot. Try above method with RAZR blade?
Sent from my XT894 using Tapatalk
tcrews said:
Why are y'all struggling so much with this.
1. You don't need to unroot.
2. You don't need to unfreeze anything.
3. RAZR_BLADE root method still works. You have to clear cache and data and force close Smart Actions before re-rooting.
I've done three Droid 4's already. All had different apps/services frozen via Titanium Backup and all were of course rooted. One (mine) got the SOAK at version .188 and the other two got the roll out at version .189.
Install update, clear Smart Actions and re-root with the razr_blade method .bat files.
Simple, works and reauthorizing Titanium Backup will refreeze all the apps you had frozen before the update.
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
On 1 & 2 - not entirely sure anyone said to unroot or unfreeze, but I did read where it was advised to 'temp disable root', and when I followed that step voodoo did work great to allow me to update and restore root.
THANK YOU for 3!! I assumed based on some of the other comments that it didn't work. I just tried it on the other phone, and it DID restore root. VERY MUCH appreciated!!
So I use voodoo to unroot I disabled superuser but the update starts and fails everytime, I don't know why, the little android starts to update, then just gets a red x through it...
Sent from my DROID4 using xda app-developers app
I have quite a few apps frozen, but apparently nothing that prevented the install from being downloaded automatically. I unrooted with Voodoo, installed the update, restored root and all is well.
After I installed OTA Update SW Version: 98.72.18-8 on my Droid 4, I lost root access. I read in another thread that RAZR_BLADE root method still works if you clear cache and data and force close smart actions before you root with RAZR. I did this and ran the DROID_4_Utility_Jellybean_XT894 which includes the RAZR_BLADE root method. On phase 2 the batch script has you open smart actions and run battery saver mode. The following came up after phase 3
failed on '/data/logger/' - Permision Denied
mkdir failed for /data/logger/ file exists
unable to chmod /data/logger: opperation not permitted
link failed File exists
Anyone know what I'm doing wrong?
I figured it out with more research. You need your phone USB in MTP mode for it to work. Hope this helps.
I'm having the same problem. Cannot get root back. I am also using the DROID_4_Utility_Jellybean_XT894_WinMacLin tool.
Note: the "Battery Saver" wasn't there, probably due to my clearing the data for the app. My solution was to create a "Battery Saver" item. This didn't seem to help. I did not encounter any errors, but on last reboot, I still don't appear to be rooted.
inspector_Gadget said:
I'm having the same problem. Cannot get root back. I am also using the DROID_4_Utility_Jellybean_XT894_WinMacLin tool.
Note: the "Battery Saver" wasn't there, probably due to my clearing the data for the app. My solution was to create a "Battery Saver" item. This didn't seem to help. I did not encounter any errors, but on last reboot, I still don't appear to be rooted.
Click to expand...
Click to collapse
Battery Saver will appear, you just have to wait for it. If you cleared data of the app (which you need to do before attempting to re-root with razr_blade), Smart Actions has to rebuild the default choices. Give it a few minutes and Battery Saver will appear. I've rooted 3 Droid 4's and 1 Droid Razr with razr_blade after this new update was pushed out (all had previously been rooted).
tcrews said:
Battery Saver will appear, you just have to wait for it. If you cleared data of the app (which you need to do before attempting to re-root with razr_blade), Smart Actions has to rebuild the default choices. Give it a few minutes and Battery Saver will appear. I've rooted 3 Droid 4's and 1 Droid Razr with razr_blade after this new update was pushed out (all had previously been rooted).
Click to expand...
Click to collapse
Yes, it did appear. so, tried again. This time, got the following:
[*] Phase three (this will take a minute)...
failed on '/data/logger' - Permission denied
mkdir failed for /data/logger, File exists
Unable to chmod /data/logger: Operation not permitted
link failed File exists
It still said "Exploit Complete" at the end, but alas, no root.
Ideas?
Thanks for your help,
--Glenn.
Clear cache and data of Smart Actions and then force close it and try again. Make sure your USB is connected as MTP and not mass storage.
Sent from my Nexus 10 using Tapatalk
tcrews said:
Clear cache and data of Smart Actions and then force close it and try again. Make sure your USB is connected as MTP and not mass storage.
Click to expand...
Click to collapse
Awesome! I have root! ok, it was the Mass Storage Mode that was killing me. I feel so stupid, because right above my first post was "must be in MTP mode". not sure how I missed that.
At any rate, thank you for your time and considerable patience! :good:
--Glenn
Last night I sideloaded the 5.1.1 update to my Droid Turbo. While playing around with it this morning, I accidentally clicked the 'Force RTL' option under accessories. Immediately after, my phone crashed, and on boot would display 'system ui has stopped working' indefinitely. The wallpaper would load, and the alert modal would appear, but clearing it just kicked up another 'system ui has stopped working' modal a few seconds later.
I cleared the cache, and now when I reboot the device, it comes up with the Recovery Andy image with 'no command' below. I don't mind doing a factory reset, but I have a LOT of data I'd lose in the process. All of my pictures are backed up to Dropbox/G+, but I have a lot of other files and backups that I neglected to save externally prior to the update ... because I'm a genius.
When I try to reapply the update, I get a message indicating "/system/app/3c_main.apk" has unexpected contents. I've tried to push from SD and from ADB, both with no luck. At this point I'm happy to just reset the device, but I want my data off first. All ADB commands with the exception of SIDELOAD return 'error: closed', so I can't even backup my files.
Ideas? Help?! ANYTHING?!
spikejnz said:
Last night I sideloaded the 5.1.1 update to my Droid Turbo. While playing around with it this morning, I accidentally clicked the 'Force RTL' option under accessories. Immediately after, my phone crashed, and on boot would display 'system ui has stopped working' indefinitely. The wallpaper would load, and the alert modal would appear, but clearing it just kicked up another 'system ui has stopped working' modal a few seconds later.
I cleared the cache, and now when I reboot the device, it comes up with the Recovery Andy image with 'no command' below. I don't mind doing a factory reset, but I have a LOT of data I'd lose in the process. All of my pictures are backed up to Dropbox/G+, but I have a lot of other files and backups that I neglected to save externally prior to the update ... because I'm a genius.
When I try to reapply the update, I get a message indicating "/system/app/3c_main.apk" has unexpected contents. I've tried to push from SD and from ADB, both with no luck. At this point I'm happy to just reset the device, but I want my data off first. All ADB commands with the exception of SIDELOAD return 'error: closed', so I can't even backup my files.
Ideas? Help?! ANYTHING?!
Click to expand...
Click to collapse
Did you use the zip from Rootjunky?
Sent from my Droid Turbo using Tapatalk
zefir738 said:
Did you use the zip from Rootjunky?
Sent from my Droid Turbo using Tapatalk
Click to expand...
Click to collapse
Yes
spikejnz said:
Yes
Click to expand...
Click to collapse
You might have to wait until the OTA is available for manual download and then flash it via RSD Lite. The way the zip works is it'll only install if you have version 21.44.12.en.us installed. You have 23.11.38 so it won't install now.
Sent from my Droid Turbo using Tapatalk
zefir738 said:
You might have to wait until the OTA is available for manual download and then flash it via RSD Lite. The way the zip works is it'll only install if you have version 21.44.12.en.us installed. You have 23.11.38 so it won't install now.
Sent from my Droid Turbo using Tapatalk
Click to expand...
Click to collapse
Yikes. OTA is supposed to drop today, so hopefully that becomes available soon thereafter. Not sure how long I can survive without my phone.
spikejnz said:
Last night I sideloaded the 5.1.1 update to my Droid Turbo. !
Click to expand...
Click to collapse
I assume you mean the 5.1 update? or did you try to use a 5.1.1 update for some other phone by mistake? if so there may be no easy solution.
I don't accept defeat. Everyone said my data was a lost cause, and that Factory Reset was my only hope. Yeah, well who's copying data off his device right now?
THIS GUY.
I downloaded the firmware, removed the "erase userdata" line from the batch file, and ran it to restore the images and partitions.
I then cleared the cache (again) and rebooted my device.
Back to the 'System UI has stopped' loop
Tried unsuccessfully to send ADB commands to the device
Opened and ADB Shell in Cerberus Dashboard, but kept getting disconnected
Sent an Unlock command in Cerberus Dashboard to my device ... voilla!
UI is still crashing, but Windows is now attempting to install drivers
After trying to manually install drivers for an extended period of time, decided to attempt it on my Mac
BOOM, FS mounts and Android File Transfer is now accessing all the files, even if my display is all jacked!
Next comes the factory reset. I knew there was a reason I installed Cerberus on my non-rooted device.
Fix RTL via ADB
I had this problem on my turbo after reading about a possible fix for snapchat image problems.
After a bit of googling, I came up with this simple fix.
This will only work if ADB Debugging is enabled and your PC is already authorized.
No need for root.
Code:
adb devices
adb shell
settings put global debug.force_rtl 0
reboot
And I suppose if you do NOT already have ADB enabled et al, you're SOL?
AnoraxAudio said:
And I suppose if you do NOT already have ADB enabled et al, you're SOL?
Click to expand...
Click to collapse
If your phone has a secure lock screen, it will not recognize a usb port for file transfer or ADB mode until the password/pin/pattern/etc. has been entered. The Cerberus method described above worked because it was able to meet this requirement. With this in mind, you have the following options depending on your lock screen situation:
1. Insecure lock screen, ADB previously enabled: use the ADB method described above.
2. Insecure lock screen, ADB disabled: Plug in the USB, transfer over your important files, reboot the phone in bootloader mode, select recovery mode, perform a factory reset.
3. Secure lock screen (all cases, assuming you can't unlock it with Cerberus or something similar): Wipe cache through recovery to see if that helps anything. If it doesn't, you can try reflashing the system image via mofo or fastboot to see if that helps anything. If not, bite the bullet and perform a factory reset. You will lose your data.
Now if you have mofo, you might be able to flash a rooted rom that can perform the adb method using a su.d script, but I'm not entirely sure about that.