Related
i downloaded the razr m root package and ran the .bat file.. it said daemon was running but it just sat there for 10 mins and didnt say anything else nor did it root my phone.. so did i do something wrong?
Sent from my XT907 using Tapatalk 2
Should be real quick.
Sent from my XT907 using xda app-developers app
jco23 said:
Should be real quick.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
thanks.. ill try it on a diff. computer
Sent from my XT907 using Tapatalk 2
Sup
luciferii said:
thanks.. ill try it on a diff. computer
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
Hey lucifer, did you get your shiz rooted yet? Make sure you have your phone set to debugging through SETTINGS>DEVELOPER OPTIONS>USB DEBUGGING. This would cause your bat to freeze the way you described, I do not believe your computer was the issue.
Also, are you using the motofail2go method to root? Depending how updated the zip package was that you downloaded, your 'su' and superuser.apk files may be bunk. If this is the case you will need to download the file HERE. Unzip it, pull out the 'su' file from XBIN and the 'superuser.apk' from SYSTEM. Then put both of these files into your motofail2go folder, replacing the two original files BEFORE running the .bat file. Then you should be good to go.
If you still can't get root, there is a newer root package exploit that you can try but try my suggested changes first. Cheers.
cliMAKtic said:
Hey lucifer, did you get your shiz rooted yet? Make sure you have your phone set to debugging through SETTINGS>DEVELOPER OPTIONS>USB DEBUGGING. This would cause your bat to freeze the way you described, I do not believe your computer was the issue.
Also, are you using the motofail2go method to root? Depending how updated the zip package was that you downloaded, your 'su' and superuser.apk files may be bunk. If this is the case you will need to download the file HERE. Unzip it, pull out the 'su' file from XBIN and the 'superuser.apk' from SYSTEM. Then put both of these files into your motofail2go folder, replacing the two original files BEFORE running the .bat file. Then you should be good to go.
If you still can't get root, there is a newer root package exploit that you can try but try my suggested changes first. Cheers.
Click to expand...
Click to collapse
thanks for the info.. i havent rooted it yet tho. im sure it was the computer cuz my laptop is in the shop so i had to goto walmart and try to use the display computers lol. yeah i tried the motofail2go, but ill try your way.
Sent from my XT907 using Tapatalk 2
luciferii said:
thanks for the info.. i havent rooted it yet tho. im sure it was the computer cuz my laptop is in the shop so i had to goto walmart and try to use the display computers lol. yeah i tried the motofail2go, but ill try your way.
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
My way is still the motofail2go way, but you need to make sure both that debugging is enabled, and you need to replace the su and superuser.apk files in the motofail2go folder with the ones I linked.
cliMAKtic said:
My way is still the motofail2go way, but you need to make sure both that debugging is enabled, and you need to replace the su and superuser.apk files in the motofail2go folder with the ones I linked.
Click to expand...
Click to collapse
yeah debugging is enabled.. and i replaced the files like you said.. im going to try n root it again n the morning. ill let ya know how it goes. thanks again for the info n files.
Sent from my XT907 using Tapatalk 2
luciferii said:
yeah debugging is enabled.. and i replaced the files like you said.. im going to try n root it again n the morning. ill let ya know how it goes. thanks again for the info n files.
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
I used this one:
http://www.droidrzr.com/index.php/topic/15208-root-motochopper-yet-another-android-root-exploit/
Made sure USB debugging was turned on.
Unzipped the folder.
Plugged phone in.
Ran "run.bat" as admin.
Rooted in about 30 seconds.
No app swapping needed
I've seen apps that you have to "push" them to install them. What exactly does that mean and how do I do it?
Sent from my Nexus 4 using xda app-developers app
rmhumtex97 said:
I've seen apps that you have to "push" them to install them. What exactly does that mean and how do I do it?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
You need to use adb on a computer the command would be
adb push nameofapp.apk /system/app/
Or
You can use a file manager with root access and copy the app to /system/app and fix permission to rw-r--r-- and reboot
Sent from my Nexus 4
Or, alternatively you can use Titanium Backup to do the job.
ottoemezzo said:
Or, alternatively you can use Titanium Backup to do the job.
Click to expand...
Click to collapse
How do you get it to do it?
Sent from my Nexus 4 using xda app-developers app
Open TB
go to the backup/restore tab
find the app you want
Long press the app till a menu pops up
Find option to convert the app in the menu and follow directions
Sent from my Nexus 4 using Tapatalk 2
Well, I meant exactly like bobdarkside has just described. I think we might misunderstood you, because with TB you can only convert previously installed apks into system ones. So if you need to do it without installation go for adb or file manager method.
spaceman860 said:
You need to use adb on a computer the command would be
adb push nameofapp.apk /system/app/
Or
You can use a file manager with root access and copy the app to /system/app and fix permission to rw-r--r-- and reboot
Sent from my Nexus 4
Click to expand...
Click to collapse
Ok I copied the app to system/app now I just need to fix permission to rw-r--r-- but I don't know what that is and how I do it
Sent from my Nexus 4 using xda app-developers app
Never mind I figured it out
Sent from my Nexus 4 using xda app-developers app
My nexus 7 had slowed down recently. So I was advised by someone here to reinstall the stock rom. So I backed everything up that was on it and installed the latest version of android (4.2.2). It worked. It's not slow anymore. But there's one problem. I can't delete any files on it using es file manager. I get a message saying "cannot delete some files. Please make sure that your storage is not mounted as read-only". I don't know what that means. Can someone help me?
Sent from my Nexus 7 using xda app-developers app
You can delete unwanted files straight from TWRP Recovery. TWRP > Advanced > File Manager >SD Card > Select Items > Delete.
Well that worked. But it's too much trouble to have to go into TWRP just to delete a file. Why can't I delete it with ES file explorer like I could before I reinstalled the stock rom?
Sent from my Nexus 7 using xda app-developers app
You don't state if you're rooted....
Yes it's been rooted.
Sent from my Nexus 7 using xda app-developers app
And SU or SuperSU (whichever) is active, with root permissions being granted as needed?
Depending on where you're working you may need to ask for write and mount privileges through terminal.
For example if working in /system:
Code:
su
mount -o remount,rw /system
Caution do not do this if you are not experienced. You may damage your system.
danvee said:
And SU or SuperSU (whichever) is active, with root permissions being granted as needed?
Click to expand...
Click to collapse
Yes. I have SuperSU. It's active with root permissions granted.
TheAltruistic said:
Depending on where you're working you may need to ask for write and mount privileges through terminal.
For example if working in /system:
Code:
su
mount -o remount,rw /system
Caution do not do this if you are not experienced. You may damage your system.
Click to expand...
Click to collapse
Hmm I'm not sure I understand. I already put it in rw mode in the es file explorer app under tools/root explorer. But it still won't let me delete things.
Sent from my Nexus 7 using xda app-developers app
Guys something is definitely not right. I just noticed that I can't read or write or edit text files (.txt). When I try to open a text file with es note editor it says an error occurred while trying to open file. Why is this happening? I almost wish I never did a fresh install.
Sent from my Nexus 7 using xda app-developers app
Bryon15 said:
Guys something is definitely not right. I just noticed that I can't read or write or edit text files (.txt). When I try to open a text file with es note editor it says an error occurred while trying to open file. Why is this happening? I almost wish I never did a fresh install.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Have you looked into TWRP > Advanced > Fix Permissions?
Bryon15 said:
Guys something is definitely not right. I just noticed that I can't read or write or edit text files (.txt). When I try to open a text file with es note editor it says an error occurred while trying to open file. Why is this happening? I almost wish I never did a fresh install.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hm weird. Under the assumption that you are doing everything correctly, it should work as superuser permissions supersedes all and any limitation unless the file is open preventing it from being written to. If that's the case you will have to go through recovery as Username invalid suggested to edit the file.
Username invalid said:
Have you looked into TWRP > Advanced > Fix Permissions?
Click to expand...
Click to collapse
I just tried that. Unfortunately it didn't work. And it gets worse. It seems like I can't do anything to the file system at all. Meaning I can't create a new file or folder. And I can't edit or delete what's already there. I haven't tried to download anything yet. But that probably won't work either. This is terrible.
Sent from my Nexus 7 using xda app-developers app
Nope. Can't download nothing. I just tried to download the music video beat it by Michael Jackson from youtube using the tubemate app. It said: Error: open failed: EACCES (permission denied)
Sent from my Nexus 7 using xda app-developers app
Bryon15 said:
Nope. Can't download nothing. I just tried to download the music video beat it by Michael Jackson from youtube using the tubemate app. It said: Error: open failed: EACCES (permission denied)
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
http://stackoverflow.com/questions/15985631/open-failed-eacces-permission-denied-in-a-virtual-device
http://stackoverflow.com/questions/12415157/filenotfound-open-failed-eacces-permission-denied
Username invalid said:
http://stackoverflow.com/questions/15985631/open-failed-eacces-permission-denied-in-a-virtual-device
http://stackoverflow.com/questions/12415157/filenotfound-open-failed-eacces-permission-denied
Click to expand...
Click to collapse
I read it. It says to fix it I have to remove and recreate the virtual device and change the size. But I have no idea what that means or how to do it. Why is everything so hard?
Sent from my Nexus 7 using xda app-developers app
If you can install apps, install root explorer from the store. Its the better tool for this type of issue. Also install terminal emulator and try the command that was in one of the replies above.
How did you return to stock?
Please don't fall back on the I'm a noob thing and expect people to hold your hand. The more you do/learn yourself, the better help you can expect here.
Sent from my Nexus 7 using xda premium
ezas said:
If you can install apps, install root explorer from the store. Its the better tool for this type of issue. Also install terminal emulator and try the command that was in one of the replies above.
How did you return to stock?
Please don't fall back on the I'm a noob thing and expect people to hold your hand. The more you do/learn yourself, the better help you can expect here.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I returned to stock with the nexus 7 toolkit. It does everything for you. But it doesn't seem to help with this. Anyway I looked at those apps, and root explorer is $4.00. I don't mind paying for it. But I want to know if it's a necessity to have before I buy it.
The other app (terminal emulator) has multiple versions by different companies. How do I know which one to get? Here are some:
Android terminal emulator by jack palevich
Terminal emulator by cityapp
Shell terminal emulator by mobildev
Terminal IDE by Spartacus Rex
There are even more, those are the free ones.
Sent from my Nexus 7 using xda app-developers app
Bryon15 said:
I returned to stock with the nexus 7 toolkit. It does everything for you. But it doesn't seem to help with this. Anyway I looked at those apps, and root explorer is $4.00. I don't mind paying for it. But I want to know if it's a necessity to have before I buy it.
The other app (terminal emulator) has multiple versions by different companies. How do I know which one to get? Here are some:
Android terminal emulator by jack palevich
Terminal emulator by cityapp
Shell terminal emulator by mobildev
Terminal IDE by Spartacus Rex
There are even more, those are the free ones.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree&hl=en
https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
Username invalid said:
https://play.google.com/store/apps/details?id=com.jrummy.root.browserfree&hl=en
https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
Click to expand...
Click to collapse
Thank you. I'm going to attempt to fix it now. Wish me luck.
Sent from my Nexus 7 using xda app-developers app
Do I have to download ADB tool for my PC to use with this?
Sent from my Nexus 7 using xda app-developers app
Hi
I was changing Roms and like a fool wiped everything, all data etc so now I have no OS.
I can get into recovery just fine and have used the Nexus tool kit to push the PA rom and Omni Rom so that using TWRP file explorer can see them however it just keeps failing when I try to install.
after it skips the md5 it says
warning no file_contexts
then
error executing updater binary in zip and more texts which i can copy if important.
What can i do to get my phone backup and running please.
DESPERATE!
foxguard said:
Hi
I was changing Roms and like a fool wiped everything, all data etc so now I have no OS.
I can get into recovery just fine and have used the Nexus tool kit to push the PA rom and Omni Rom so that using TWRP file explorer can see them however it just keeps failing when I try to install.
after it skips the md5 it says
warning no file_contexts
then
error executing updater binary in zip and more texts which i can copy if important.
What can i do to get my phone backup and running please.
DESPERATE!
Click to expand...
Click to collapse
In TWRP go to Advanced and then click ADB sideload and swipe when it tells you to. Go to the folder on your computer your ROM is in and open a command prompt/ terminal. Lastly type adb sideload "filenamehere.zip" After you type this wait and you will see Success. There you go buddy.
Sent from my Nexus 4 using XDA Premium 4 mobile app
DREWHAMM974 said:
In TWRP go to Advanced and then click ADB sideload and swipe when it tells you to. Go to the folder on your computer your ROM is in and open a command prompt/ terminal. Lastly type adb sideload "filenamehere.zip" After you type this wait and you will see Success. There you go buddy.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hello mate,
thanks for your quick response although im not 100% sure i get it.
What will this acheive? Getting the rom.zip on my phone? if so I have done with using the tookit and it is when i go to install the rom i get all the errors.
If that is not what we are doing then ok... but im still lost.if i open ADB sideload and swipe the phone just sits saying 'starting adb sideload' What do i do next?
Connect phone to your PC. Then start sideload. After you swipe and it says Starting ADB Sideload open a command prompt in the folder your ROM is in and type adb sideload filename.zip. Put the file name of the Zip where I have filename.zip. This will sideload the ROM. Which means it will flash the ROM. After you do this reboot your phone and all will be good.
All sideloading does is flash a ROM that is on your PC instead of phone. It does the same as flashing one, only this way it doesn't have to be in your storage.
Sent from my Nexus 4 using XDA Premium 4 mobile app
DREWHAMM974 said:
Connect phone to your PC. Then start sideload. After you swipe and it says Starting ADB Sideload open a command prompt in the folder your ROM is in and type adb sideload filename.zip. Put the file name of the Zip where I have filename.zip. This will sideload the ROM. Which means it will flash the ROM. After you do this reboot your phone and all will be good.
All sideloading does is flash a ROM that is on your PC instead of phone. It does the same as flashing one, only this way it doesn't have to be in your storage.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok that makes more sense and i get it, although im not sure how to open a command promt in the folder where i have the rom saved. I know if i type cmd in run that opens command but thats just in the local folder, what command prompt do you mean. Sorry mate i know some stuff just cant get my head around this!
Command prompt is cmd. To open a folder in command prompt you type cd path/to/directory. The easiest way to find what directory is right click on the file and click on properties, from there copy where it says location (may say something else but its where it is located.) It will be like path/to/directory. Separated by /. Copy that and then in the cmd type cd and then paste what you copied. Then you will be in that location and will be able to do the adb sideload
Sent from my Nexus 4 using XDA Premium 4 mobile app
---------- Post added at 04:03 PM ---------- Previous post was at 04:00 PM ----------
Under the general tab in properties is where you will find the location btw
Sent from my Nexus 4 using XDA Premium 4 mobile app
DREWHAMM974 said:
Connect phone to your PC. Then start sideload. After you swipe and it says Starting ADB Sideload open a command prompt in the folder your ROM is in and type adb sideload filename.zip. Put the file name of the Zip where I have filename.zip. This will sideload the ROM. Which means it will flash the ROM. After you do this reboot your phone and all will be good.
All sideloading does is flash a ROM that is on your PC instead of phone. It does the same as flashing one, only this way it doesn't have to be in your storage.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ok getting closer, but not CMD say adb is not recognised as an internal or external command? what have i done wrong?
im typing
adb sideload pa.zip
Have you installed adb? If not go to this link, install this, and then it will work perfectly.
http://forum.xda-developers.com/showthread.php?t=2588979
Sent from my Nexus 4 using XDA Premium 4 mobile app
---------- Post added at 04:13 PM ---------- Previous post was at 04:10 PM ----------
I thought you had adb already installed. Once you do this I recommend you to learn how to use adb and fastboot, not toolkits. Toolkits get people in trouble like this right here and because you don't know how the toolkit does what it does or how to do it yourself you're stuck. Everyone needs to know those two thingd if they're doing anything to an Android phone so they can fix it if something happens. It's easy to learn and takes less than an hour to understand.
Sent from my Nexus 4 using XDA Premium 4 mobile app
---------- Post added at 04:14 PM ---------- Previous post was at 04:13 PM ----------
Be sure to go to the op in that link as well. I thought I linked the op but guess not
Sent from my Nexus 4 using XDA Premium 4 mobile app
DREWHAMM974 said:
Have you installed adb? If not go to this link, install this, and then it will work perfectly.
http://forum.xda-developers.com/showthread.php?t=2588979
Sent from my Nexus 4 using XDA Premium 4 mobile app
---------- Post added at 04:13 PM ---------- Previous post was at 04:10 PM ----------
I thought you had adb already installed. Once you do this I recommend you to learn how to use adb and fastboot, not toolkits. Toolkits get people in trouble like this right here and because you don't know how the toolkit does what it does or how to do it yourself you're stuck. Everyone needs to know those two thingd if they're doing anything to an Android phone so they can fix it if something happens. It's easy to learn and takes less than an hour to understand.
Sent from my Nexus 4 using XDA Premium 4 mobile app
---------- Post added at 04:14 PM ---------- Previous post was at 04:13 PM ----------
Be sure to go to the op in that link as well. I thought I linked the op but guess not
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No, i thought The toolkit was the best way but will definatly look into this adb once im sorted, although it has failed again.
It transfers the file over and starts to flash but i then get error.
warning no file contexts
error_metadata+recursice: some changes failed
E:Error executing updater binary in zip 'data/media/sidelaod.zip
What does this mean?
You can also flash the full frimware via Fastboot Get it here https://developers.google.com/android/nexus/images
LightingZ said:
You can also flash the full frimware via Fastboot Get it here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Thanks, thought Nexus 4 was Mako? I dont see that there.
Download a different ROM, that's a bad download
Sent from my Nexus 4 using XDA Premium 4 mobile app
DREWHAMM974 said:
Download a different ROM, that's a bad download
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Im using the same zip's that i have used before to flash the phone and all worked fine, have now tried 3 different roms and getting the same error?
I'm not sure try flashing the firmware. Also the Nexus 4 is also known as the Occam. Try the firmware.
Sent from my Nexus 4 using XDA Premium 4 mobile app
DREWHAMM974 said:
I'm not sure try flashing the firmware. Also the Nexus 4 is also known as the Occam. Try the firmware.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Downloading now and will try, thank you so much for all your help so far mate, proper fooked!!
foxguard said:
Im using the same zip's that i have used before to flash the phone and all worked fine, have now tried 3 different roms and getting the same error?
Click to expand...
Click to collapse
If you don't want to do the firmware try downloading a stock rom and side loading it. Maybe that will help. I've never had a sideload not work.
Sent from my Nexus 4 using XDA Premium 4 mobile app
DREWHAMM974 said:
If you don't want to do the firmware try downloading a stock rom and side loading it. Maybe that will help. I've never had a sideload not work.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ok just downloaded the occam file from here
https://developers.google.com/android/nexus/images#occamkot49h
does it matter if i rename it but leave as a tgz?
assume in cmd i have to change .zip to .tgz
I have done this and now i get error file is corrupt, will try another one.
ok download another version of the factory and didnt rename it this time and still getting E:zip file is corrupt
please help me im so stuck!
foxguard said:
ok download another version of the factory and didnt rename it this time and still getting E:zip file is corrupt
please help me im so stuck!
Click to expand...
Click to collapse
What are you using to extract it? Use 7-zip
Sent from my Nexus 5
jd1639 said:
What are you using to extract it? Use 7-zip
Sent from my Nexus 5
Click to expand...
Click to collapse
Do i need extract it? thought i was told to just add the zip file path?
I smashed my screen and am now trying to backup my media data from my phone to my PC. I'm having to use adb due to the fact my screen is completely dead.
I have android toolkit working fine, and it is showing my device in the connected devices section.
However, when I select the option to backup my internal storage it comes up with the message "waiting for USB debugging to be activated" and does not move any further.
How can I fix this issue? Bear in mind I have no way of getting into the phone due to my screen being completely broken.
Thanks a lot!
Try this http://forum.xda-developers.com/showthread.php?p=20868527
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Try this http://forum.xda-developers.com/showthread.php?p=20868527
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
It says to unlock phone to confirm the backup operation - I cannot do that because of no screen! Any other suggestions?
fredcorp6 said:
It says to unlock phone to confirm the backup operation - I cannot do that because of no screen! Any other suggestions?
Click to expand...
Click to collapse
You're not unlocked? If that's the case, you're screwed. You need to have the bootloader unlocked. Sorry man
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You're not unlocked? If that's the case, you're screwed. You need to have the bootloader unlocked. Sorry man
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
That's not what it means, when you do that command with a lock screen you need to unlock the screen first as a security measure.
I have got an unlocked bootloader and cwm recovery installed.
fredcorp6 said:
That's not what it means, when you do that command with a lock screen you need to unlock the screen first as a security measure.
I have got an unlocked bootloader and cwm recovery installed.
Click to expand...
Click to collapse
You don't have to unlock the screen in recovery. Out should work for you
Use adb backup -apk -shared -all
Start with adb devices. Your device should be shown. What do you get when you do that?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You don't have to unlock the screen in recovery. Out should work for you
Use adb backup -apk -shared -all
Start with adb devices. Your device should be shown. What do you get when you do that?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
My device shows up as connected in adb, but when I enter that command I get "now unlock your device and confirm the backup operation".
This is what it looks like:
C:\Program Files (x86)\WugFresh Development\data>adb devices
List of devices attached
0073b690d60fb5cf recovery
C:\Program Files (x86)\WugFresh Development\data>adb backup -apk -shared -all
Now unlock your device and confirm the backup operation.
C:\Program Files (x86)\WugFresh Development\data>
fredcorp6 said:
My device shows up as connected in adb, but when I enter that command I get "now unlock your device and confirm the backup operation".
This is what it looks like:
C:\Program Files (x86)\WugFresh Development\data>adb devices
List of devices attached
0073b690d60fb5cf recovery
C:\Program Files (x86)\WugFresh Development\data>adb backup -apk -shared -all
Now unlock your device and confirm the backup operation.
C:\Program Files (x86)\WugFresh Development\data>
Click to expand...
Click to collapse
Adb can be a pita. Why don't you try this http://forum.xda-developers.com/showthread.php?p=36499906
I haven't tried it but if it works well let me know
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Adb can be a pita. Why don't you try this http://forum.xda-developers.com/showthread.php?p=36499906
I haven't tried it but if it works well let me know
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Get the same message in that as well, doing my head in. It must be due to having a screen lock password... there must be a way round it.
Thanks for trying to help btw.
fredcorp6 said:
Get the same message in that as well, doing my head in. It must be due to having a screen lock password... there must be a way round it.
Thanks for trying to help btw.
Click to expand...
Click to collapse
Ok, here's the problem. The now unlock your device.... is telling you the backup is done, not that you have to use a screen password. I got the same thing trying to do it in recovery and a 0 byte backup file. I could backup when normally booted. But that's not going to help you with the non-functional screen. Let me play around with it a little more and see if I can figure it out.
Edit, let's backup a little bit. Do you have a custom recovery or are you on stock? If it's custom which one?
Edit, sorry man, the best I can do is use adb pull. But that requires you to know specifically where and what the file name is. And you have to do that for every file you want. Seems adb backup only works if you're booted normally and not in recovery.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Ok, here's the problem. The now unlock your device.... is telling you the backup is done, not that you have to use a screen password. I got the same thing trying to do it in recovery and a 0 byte backup file. I could backup when normally booted. But that's not going to help you with the non-functional screen. Let me play around with it a little more and see if I can figure it out.
Edit, let's backup a little bit. Do you have a custom recovery or are you on stock? If it's custom which one?
Edit, sorry man, the best I can do is use adb pull. But that requires you to know specifically where and what the file name is. And you have to do that for every file you want. Seems adb backup only works if you're booted normally and not in recovery.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for trying to help man!
I'm on cwm recovery.
I tried adb pull to copy all the stuff on my phone using the command "adb pull /" but the files copied did not include my pics or any personal media etc.
What would be the exact location of my pics inside the phone?? Also maybe it's not working because the sdcard is not mounted?
Sent from my iPhone using Tapatalk
fredcorp6 said:
Thanks for trying to help man!
I'm on cwm recovery.
I tried adb pull to copy all the stuff on my phone using the command "adb pull /" but the files copied did not include my pics or any personal media etc.
What would be the exact location of my pics inside the phone?? Also maybe it's not working because the sdcard is not mounted?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Try /sdcard/DCIM/Camera
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Try /sdcard/DCIM/Camera
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
No luck... do you know how to mount the sdcard in adb? tried googling it but none of the commands listed are working.
fredcorp6 said:
No luck... do you know how to mount the sdcard in adb? tried googling it but none of the commands listed are working.
Click to expand...
Click to collapse
Have you tried adb pull /sdcard
That should get you everything on it. It'll take a long time
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Have you tried adb pull /sdcard
That should get you everything on it. It'll take a long time
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yea I have, and I get "0 files pulled. 0 files skipped".
fredcorp6 said:
Yea I have, and I get "0 files pulled. 0 files skipped".
Click to expand...
Click to collapse
You're using cwm aren't you? Try adb pull /data/media. Or adb pull /data/media/0. Cwm is messed up on how it handles the file structure
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You're using cwm aren't you? Try adb pull /data/media. Or adb pull /data/media/0. Cwm is messed up on how it handles the file structure
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Neither work! It would be massively helpful if you could go to a camera picture on your phone and lookup where it is actually stored? Then hopefully it will be the same on mine.
fredcorp6 said:
Neither work! It would be massively helpful if you could go to a camera picture on your phone and lookup where it is actually stored? Then hopefully it will be the same on mine.
Click to expand...
Click to collapse
We tried that already. It's in /sdcard/DCIM/Camera
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
We tried that already. It's in /sdcard/DCIM/Camera
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I'm making progress! managed to get all my app data off the phone.
Originally when I did adb pull /data, it returned "0 files pulled, 0 files skipped".
Then I went into adb shell and mounted /data, exited adb shell, did the pull again and it worked!
So I'm close... all I need to know is the specific location of my pictures in the file system and I can do it.