A guy I work with dropped his phone and the screen is unresponsive. It does not display anything (but does not appear cracked). At any rate, he's getting the phone replaced on warranty. He's saved all his videos / photos to the internal storage and not the sd-card. I can get the phone to go in to download mode (it is detected in Heimdall).
Is there any way for me to be able to dump the contents of the internal storage via heimdall/odin? I was looking at heimdall dump:
Action: dump
Arguments: --chip-type <NAND | RAM> --chip-id <integer> --output <filename>
Description: Attempts to dump data from the phone corresponding to the specified chip type and chip ID.
I don't know the interal chip-id.
Any suggestions on how to save his files?
Thanks!
If you can get into download then you can probably get into recovery. If you can get into recovery you can use adb shell to pull anything off the sdcard you want.
Sent from my SAMSUNG-SGH-I777 using XDA Premium HD app
dayv said:
If you can get into download then you can probably get into recovery. If you can get into recovery you can use adb shell to pull anything off the sdcard you want.
Sent from my SAMSUNG-SGH-I777 using XDA Premium HD app
Click to expand...
Click to collapse
He is stock and not rooted. Does the stock recovery have adb? Can I use a reboot to recovery command from download mode?
Sent from my Galaxy Nexus using xda app-developers app
yes adb does work with stock recovery. No I think reboot recovery command will work from download mode. But if the phone will boot up (I know the screen will be dark) but as long as it boots you can just use the adb shell from there. Or you can try the button combo and just try to time out when it boots into recovery.
But like I said if the phone will boot up normally you can just use adb shell from there to pull anything you want.
Sent from my SAMSUNG-SGH-I777 using XDA Premium HD app
dayv said:
yes adb does work with stock recovery. No I think reboot recovery command will work from download mode. But if the phone will boot up (I know the screen will be dark) but as long as it boots you can just use the adb shell from there. Or you can try the button combo and just try to time out when it boots into recovery.
But like I said if the phone will boot up normally you can just use adb shell from there to pull anything you want.
Sent from my SAMSUNG-SGH-I777 using XDA Premium HD app
Click to expand...
Click to collapse
Good call! After a few tries I was able to get in to adb. I think the issue now is the fact he's not rooted. I cannot access /sdcard or /sdcard1 and I cannot mount anything because I do not have permission (no su). I think I may need to root him, get the files off then go back to stock for his warranty replacement.
If debugging is not checked on I don't know if you can get what you need with adb. Although I thought you should still be able to access the /sdcard folder. I know you can't access root but maybe you can't get to the /sdcard either without debugging on.
I don't know if someone knows how to turn on debugging without being able to see what you are doing.
Sent from my SAMSUNG-SGH-I777 using XDA Premium HD app
Just an update for anyone interested....
I managed to get everything off the internal storage. Without root I could not mount the storage so I was basically stuck. I ended up blindly button mashing and got back into Download mode. Using Heimdall I rooted then button mashed until I got in to recovery. From there I was able to get the internal storage mounted and "adb pull" everything I needed. I then un-rooted and the phone is set for warranty return.
Thanks everyone for the help and suggestions.
Impressive!
Lost Dog said:
Just an update for anyone interested....
I managed to get everything off the internal storage. Without root I could not mount the storage so I was basically stuck. I ended up blindly button mashing and got back into Download mode. Using Heimdall I rooted then button mashed until I got in to recovery. From there I was able to get the internal storage mounted and "adb pull" everything I needed. I then un-rooted and the phone is set for warranty return.
Thanks everyone for the help and suggestions.
Click to expand...
Click to collapse
Good job man!
Glad you got it.
Sent from my SAMSUNG-SGH-I777 using XDA Premium HD app
Mad props
Sent from my SGH-I777 using xda app-developers app
Related
Have a Galaxy S2 that I broke the screen on moving heavy equipemnt at the weekend. It is insured, but I want to try and get my data off before replacing it.
The phone appears to work, but obviously there is nothing on the screen. When I connect it to the PC it keeps asking me to enter the password on the phone. I had a numerical password setup (not the slider).
How can I get around this in Kies? Anyone got any ideas? The phone wasnt rooted.
Thanks.
i reckon you could try my way :
1) root ur phone
2) go into CWM > mouths and storage > mouth usb storage
3) copy whatever files you want to PC
4) done !!
those steps is done without touching a screen
If you've used Samsung Dive, you could try the Unlock My Screen function there.
http://www.samsungdive.com
Can you access your phone via adb? If yes, you can install a VNC server in the phone and then you can have a remote screen on your computer, which allow you enter the password by computer keyboard.
I haven't ever installed a VNC server, so I don't know whether your phone needs to be rooted.
kobellza said:
i reckon you could try my way :
1) root ur phone
2) go into CWM > mouths and storage > mouth usb storage
3) copy whatever files you want to PC
4) done !!
those steps is done without touching a screen
Click to expand...
Click to collapse
Problem is that his screen cant display anything so how could he navigate on cwm? Let alone booting into recovery..
I might had a solution, I once messed up with chainfire's night mode and it makes my screen go blank *duh* so i use android commander to copy my precious data before restoring the fw.. its a decent app and it could access your phone without having to mount it to usb storage.. (i think root is required) give it a shot!
Sent from my GT-I9100 using xda premium
1.You can blind boot into CWM, and connect the mobile to PC, then you can use the adb commands to copy your data.
2.Specify the kernel you are using, so that others having the same kernel can tell you the number of blind press needed and the direction to mount it in your pc.
Theres some good ideas here, i am liking it! Will put some to the test.
Thanks everyone.
I dropped my phone and the screen is toast. With the latest version of Kies(2.0.3) there is an option to "View in Explorer". Both internal and external memory is accessible.
To get there, click on you phone in the left pane and you will see basic information about your phone with the "View in Explorer" buttons next to the bars showing how your internal and external memory is allocated.
Good luck, I was able to back everything up to my hard disk.
How can you break Gorrila Glass?
Sent from my GT-I9100 using XDA App
hammief said:
How can you break Gorrila Glass?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Quite easy my friend....it's not break proof.
delete me
Currently trying to back up all the data from my phone after dropping it in the pool a week ago.
took my 10 tries to get adb working. I've backed up my SMS/MMS messages from telephony but I want to dump my internal sdcard as well.
I tried doing adb pull /sdcard but it told me that it's not a valid directory.
Help please?
randomafk said:
Currently trying to back up all the data from my phone after dropping it in the pool a week ago.
took my 10 tries to get adb working. I've backed up my SMS/MMS messages from telephony but I want to dump my internal sdcard as well.
I tried doing adb pull /sdcard but it told me that it's not a valid directory.
Help please?
Click to expand...
Click to collapse
First why use adb? If you don't have one get an adapter its cheap and very usefull.However if you want to go via adb try using QtADB. Also your problem might be fixed if you put /mnt/sdcard/ instead of just /sdcard/
Sent from my Optimus Me using xda premium
nerot said:
First why use adb? If you don't have one get an adapter its cheap and very usefull.However if you want to go via adb try using QtADB. Also your problem might be fixed if you put /mnt/sdcard/ instead of just /sdcard/
Sent from my Optimus Me using xda premium
Click to expand...
Click to collapse
oof. forgot to mention, this is internal storage, not an SD card.
/sdcard/ is where the external sdcard is mounted. If by internal sdcard you mean "the memory that resides on my phone", that should just be / (i.e. the root directory). I am not sure what your device is, so my understanding of your situation might be off, but give that a try instead.
If you tell us what phone you have it will help us a lot
Sent from my Optimus Me using xda premium
As has already been mentioned there are probably better ways to do this but if it is necessary to use adb for this task you might want to try using the "adb shell" command just log in directly to the device so you can interrogate the file system.
Since I don't have an actual device I can't really tell you where your "internal memory" storage is located. I believe everything that is user specific is located under the system directory (i.e. /system).
I wouldn't advise this however if you're not familiar with navigating Linux from the command line.
Hello XDA peeps going to attempt to unlock, root and flash a Rom for the first time tonight...any tips, suggestions and knowledge thrown my way would be greatly appreciated. Already looked around threads for "how to" I think I got good idea but knowledge is power haha
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
Hello XDA peeps going to attempt to unlock, root and flash a Rom for the first time tonight...any tips, suggestions and knowledge thrown my way would be greatly appreciated. Already looked around threads for "how to" I think I got good idea but knowledge is power haha
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
unlocking is easy now with the new method, as long as htc's website is working.
then just install a recovery via fastboot and flash a rom. Id recommend viperdna
Bigandrewgold said:
unlocking is easy now with the new method, as long as htc's website is working.
then just install a recovery via fastboot and flash a rom. Id recommend viperdna
Click to expand...
Click to collapse
Im having issues with the new method. I feel like I have followed every bit of instructions yet my computer can seem to either recognize my device or does not find "fastboot" as internal or external storage.
It seems so easy too...
KevC90 said:
Im having issues with the new method. I feel like I have followed every bit of instructions yet my computer can seem to either recognize my device or does not find "fastboot" as internal or external storage.
It seems so easy too...
Click to expand...
Click to collapse
That just means you didn't correctly install the android sdk, or whatever its called.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
That just means you didn't correctly install the android sdk, or whatever its called.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Been meaning to ask this now but when it comes to downloading the new method APK file and hasoons toolkit v2.1 for the dna do I have to install them both through my phone or do I download them on to my computer and transfer the files through there.
Sorry if I ask a lot. I have just been reading so much and every time I thought I figured it out it shows the same message.
KevC90 said:
Been meaning to ask this now but when it comes to downloading the new method APK file and hasoons toolkit v2.1 for the dna do I have to install them both through my phone or do I download them on to my computer and transfer the files through there.
Sorry if I ask a lot. I have just been reading so much and every time I thought I figured it out it shows the same message.
Click to expand...
Click to collapse
Apk file just install on your phone. And I never used a toolkit so idk.
Sent from my GT-P7510 using xda app-developers app
Bigandrewgold said:
Apk file just install on your phone. And I never used a toolkit so idk.
Sent from my GT-P7510 using xda app-developers app
Click to expand...
Click to collapse
Are you using a windows vista comp or apple? Originally I just installed the apk, ran it, rebooted my phone (manually, ive seen a video where the phone rebooted itself and he manually booted it into bootloader), ran cmd "fastboot oem readcid" and nothing... it almost makes me want to return the phone.
KevC90 said:
Are you using a windows vista comp or apple? Originally I just installed the apk, ran it, rebooted my phone (manually, ive seen a video where the phone rebooted itself and he manually booted it into bootloader), ran cmd "fastboot oem readcid" and nothing... it almost makes me want to return the phone.
Click to expand...
Click to collapse
Did you select fastboot in bootloader.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Did you select fastboot in bootloader.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yes I did.
Installed apk through my phone
Ran the apk
Manuel reboot into bootloader (should I have fastboot check on in app>settings>battery?)
Hit the power button on fastbook
Open up CMD script and type "fastboot oem readcid"
and....
nothing... =[
Should my usb settings be set to anything in particular?
KevC90 said:
Yes I did.
Installed apk through my phone
Ran the apk
Manuel reboot into bootloader (should I have fastboot check on in app>settings>battery?)
Hit the power button on fastbook
Open up CMD script and type "fastboot oem readcid"
and....
nothing... =[
Should my usb settings be set to anything in particular?
Click to expand...
Click to collapse
What does your cmd prompt say after you press enter.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
What does your cmd prompt say after you press enter.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
'fastboot' is not recognized as an internal or external command, operable programs or batch file.
KevC90 said:
'fastboot' is not recognized as an internal or external command, operable programs or batch file.
Click to expand...
Click to collapse
That's because you're doing it out of a regular ol' command prompt.
There's two things you an do to alleviate that problem.
1) Follow this:
Right click on the My Computer icon and select the properties tab.
Select Advanced and click the Environment Variables button.
In the new dialog box double-click on Path (located under System Variables) and type in the full path location to the tools directory.
So essentially if your directory for ADB and fastboot are under C:\<SDK FOLDER NAME>\tools or C:\<SDK FOLDER NAME>\platform-tools, add those to the Path.
2) Go to the directory where ADB/Fastboot, hold SHIFT and then right click. It'll give you the option to open up a command prompt from that directory with should allow you to run those specific commands.
Also, getting back to the Paths. Make sure when you go to add a new path that you put a ; IMMEDIATELY after the very last one. Then absolutely no spaces right after that ;. So.... example coming up..
Let's say a path was C:\banana\peel, and you want to add your ADB folder. So it'll be typed like so, C:\banana\peel;C:\<SDK FOLDER>\tools and then you repeat the same exact thing for the next folder.
I really hope this helps!
Shamrock13 said:
That's because you're doing it out of a regular ol' command prompt.
There's two things you an do to alleviate that problem.
1) Follow this:
Right click on the My Computer icon and select the properties tab.
Select Advanced and click the Environment Variables button.
In the new dialog box double-click on Path (located under System Variables) and type in the full path location to the tools directory.
So essentially if your directory for ADB and fastboot are under C:\<SDK FOLDER NAME>\tools or C:\<SDK FOLDER NAME>\platform-tools, add those to the Path.
2) Go to the directory where ADB/Fastboot, hold SHIFT and then right click. It'll give you the option to open up a command prompt from that directory with should allow you to run those specific commands.
Also, getting back to the Paths. Make sure when you go to add a new path that you put a ; IMMEDIATELY after the very last one. Then absolutely no spaces right after that ;. So.... example coming up..
Let's say a path was C:\banana\peel, and you want to add your ADB folder. So it'll be typed like so, C:\banana\peel;C:\<SDK FOLDER>\tools and then you repeat the same exact thing for the next folder.
I really hope this helps!
Click to expand...
Click to collapse
Following the first method (thanks alot for the help too man, I appreciate it).
Ive found the PATH section you told me about, but I dont understand what you mean by "the full path location to the tools directory".
2) Where is the ADB/Fastboot directory?
New member here as well and was my first rooting and not as hard or challenging as you might think unless things go wrong.
Talk about noob on my part haha I didn't have any files (adb and sdk) well in my defense when I rooted my razr I had some program I downloaded that basically did everything for me so I guess haha thanks for these tips people keep them coming well attempt this again tonight or weekend
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
Talk about noob on my part haha I didn't have any files (adb and sdk) well in my defense when I rooted my razr I had some program I downloaded that basically did everything for me so I guess haha thanks for these tips people keep them coming well attempt this again tonight or weekend
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Its okay. I was confused on this too because i ran the fastboot and it said it didn't recognize it. So i realized that fastbook has to be a program that i have to install. Eventually i figured out it was from the android sdk, but all the guides assume you have android sdk installed. They might want to consider adding something like "make sure you have android sdk installed and your Path set" in their guides. I know that would have saved me some trouble haha. ^_^
Yea that would have saved me some sleep haha I still can't get it to work though when I do CID exploit command prompt says no recognized ADB devices I think it might be cause I can't install HTC drivers (I hope cause I'm getting frustrated) haha will try again in next couple days
Sent from my HTC6435LVW using xda app-developers app
I was trying to modify build.prop to get Play Store to work which bricked the device. Tried factory reset and now it's totally not being recognized by the computer and ADB not working. Any solution or help.
Android Cowboy said:
I was trying to modify build.prop to get Play Store to work which bricked the device. Tried factory reset and now it's totally not being recognized by the computer and ADB not working. Any solution or help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2491057 Try this. It might at least get recognized in adb and then you can try factory reset in fastboot.
johnnydowngrief said:
http://forum.xda-developers.com/showthread.php?t=2491057 Try this. It might at least get recognized in adb and then you can try factory reset in fastboot.
Click to expand...
Click to collapse
I can't get into the safe mode either. I can get into recovery mode to factory reset but that's it. ADB still not recognized.
Android Cowboy said:
I can't get into the safe mode either. I can get into recovery mode to factory reset but that's it. ADB still not recognized.
Click to expand...
Click to collapse
Then maybe this. http://forum.xda-developers.com/showthread.php?t=1379875 But I'm just guessing here. I dont want to spam this thread. Maybe someone more experienced can help you.
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
GSLEON3 said:
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I will try that. If I could just push a new build.prop to overwrite the old one I put probably be okay. How did restore system files using ADB.
GSLEON3 said:
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Do you think you can pull a system.img for me in case I can get ADB working then I can try and flash. Lots of other people are bricking as well after root so it might be useful to many people. Thanks.
GSLEON3 said:
I did same thing. Strange but I COULD finally use adb, but only from the Android SDK base folder & only after uninstalling all devices & using USB deview to remove all adb, mtp & other android related USB devices.
So far, it looks like Amz actually keeps a partial firmware backup on the device, which they can use via mayday when things get really messed up. I would bet, they can also see system mods. It may even function automatically in some instances, I goofed mine pretty bad restore HD system files with TB & after a couple resets, it seemed it restored the system files.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
That didn't work for me, I've also trying factory resetting again multiple times through recovery, but no dice.
I got my fastboot cable working, and was able to get the device recognized as "Qualcomm USB modem converter"
I opened a thread about it, any help is appreciated!
Android Cowboy said:
Do you think you can pull a system.img for me in case I can get ADB working then I can try and flash. Lots of other people are bricking as well after root so it might be useful to many people. Thanks.
Click to expand...
Click to collapse
I am on the road right now, but I will see what I can do when I get home. You could try DL the firmware bin from Amazon. It is on their site & if you have ADB, pushing a file may be easiest, particularly since nobody has has any luck with flash or boot commands yet. At any rate, I'll do it as soon as I can, but seriously, start with just trying to push the build.prop so you still have SU & root level shell access.
GSLEON3 said:
I am on the road right now, but I will see what I can do when I get home. You could try DL the firmware bin from Amazon. It is on their site & if you have ADB, pushing a file may be easiest, particularly since nobody has has any luck with flash or boot commands yet. At any rate, I'll do it as soon as I can, but seriously, start with just trying to push the build.prop so you still have SU & root level shell access.
Click to expand...
Click to collapse
Even with the fastboot cable ADB/fastboot is not working. The Kindle finally gets recognized but as a Qualacomm device and can't find the right drivers that can make it recognize ADB. I actually have a replacement coming today so I might just let this one go. I was hoping to figure it out so I could help others in the same situation. But the factory rest really messed this thing up and Amazon is not making it easy.
Android Cowboy said:
Even with the fastboot cable ADB/fastboot is not working. The Kindle finally gets recognized but as a Qualacomm device and can't find the right drivers that can make it recognize ADB. I actually have a replacement coming today so I might just let this one go. I was hoping to figure it out so I could help others in the same situation. But the factory rest really messed this thing up and Amazon is not making it easy.
Click to expand...
Click to collapse
Did you try either of these drivers:
http://www.4shared.com/rar/kRIFBtGe/qualcomm_hsusb_device_drivers.html
http://drivers.softpedia.com/progDo...dows-7-x64-Windows-8-x64-Download-179130.html
So I actually had a similar thing happen today. build.prop mod caused my 7" to boot loop. It makes it to the first kindle screen and then the screen goes black. Based on what I've read I shouldn't try to factory reset it, because that will make it worse. I ordered a fastboot cable that should be in on Monday. Only issue is, I don't have much experience with fastboot. Would I be able to adb push a stock build.prop file to fix it if it's recognized by my computer?
S_transform said:
So I actually had a similar thing happen today. build.prop mod caused my 7" to boot loop. It makes it to the first kindle screen and then the screen goes black. Based on what I've read I shouldn't try to factory reset it, because that will make it worse. I ordered a fastboot cable that should be in on Monday. Only issue is, I don't have much experience with fastboot. Would I be able to adb push a stock build.prop file to fix it if it's recognized by my computer?
Click to expand...
Click to collapse
Since you didn't factory reset, does it show up on adb devices at all while it's trying to boot ?
S_transform said:
So I actually had a similar thing happen today. build.prop mod caused my 7" to boot loop. It makes it to the first kindle screen and then the screen goes black. Based on what I've read I shouldn't try to factory reset it, because that will make it worse. I ordered a fastboot cable that should be in on Monday. Only issue is, I don't have much experience with fastboot. Would I be able to adb push a stock build.prop file to fix it if it's recognized by my computer?
Click to expand...
Click to collapse
Try to use adb with root to push a new build.prop file. That's your best bet for recovery.
Sent from my Nexus 5 using Tapatalk
So currently its not showing up on adb while its booting, but that's probably because I haven't updated adb in a while. I'm going to update when I get home from work and report back.
EDIT: So I update ADB, which isn't recognizing it, but oddly enough, my computer can see it even after the screen shuts off as an android device. My only guess then is I'm missing a driver or something. Any suggestions?
Android Cowboy said:
Try to use adb with root to push a new build.prop file. That's your best bet for recovery.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
So I finally got ADB to recognize the device, and I can adb shell and everything, but its saying I don't have permission to adb push /system/build.prop. Also I thought that was where build.prop was located but I can't find it in adb shell. I have tried su and it hangs up, like its asking supersu for permission and I can't respond. What can I do?
S_transform said:
So I finally got ADB to recognize the device, and I can adb shell and everything, but its saying I don't have permission to adb push /system/build.prop. Also I thought that was where build.prop was located but I can't find it in adb shell. I have tried su and it hangs up, like its asking supersu for permission and I can't respond. What can I do?
Click to expand...
Click to collapse
Try adb root to reload it with root permission. Otherwise you'll need to chmod to make the system RW so you can push the build.prop file. And yes it's in the system folder. If you have the Android SDK then you can use the file manager in Monitor.bat file under "tool" folder to see to see all the files.
Android Cowboy said:
Try adb root to reload it with root permission. Otherwise you'll need to chmod to make the system RW so you can push the build.prop file. And yes it's in the system folder. If you have the Android SDK then you can use the file manager in Monitor.bat file under "tool" folder to see to see all the files.
Click to expand...
Click to collapse
When I try adb root it tells me I can't do that on consumer devices or something like that. what would the chmod command be? I dont think I've used it before. Also thank you so much for helping me.
S_transform said:
When I try adb root it tells me I can't do that on consumer devices or something like that. what would the chmod command be? I dont think I've used it before. Also thank you so much for helping me.
Click to expand...
Click to collapse
When you ADB shell, are you seeing a "#" which means you are rooted. I'm not the world's expert on ADB but this should help. Once you are shell and rooted you can just chmod 644 or 777 on /system and see if that works. http://gizbeat.com/2103/how-to-change-file-permissions-through-adb/
i am rooted and unlocked and ran a rom well in twrp i accidentally wipe everything internal now i have to way to get zips back to flash them my backup and all is gone and i have zips on ext card but twrp wont mount it please help
I pretty much just need a way to get my zips back to internal storage
Sent from my SCH-I605 using xda app-developers app
trinitystudio said:
i am rooted and unlocked and ran a rom well in twrp i accidentally wipe everything internal now i have to way to get zips back to flash them my backup and all is gone and i have zips on ext card but twrp wont mount it please help
Click to expand...
Click to collapse
while in recovery, you can use ADB to transfer files to prime from PC via data cable. look for ADB PUSH here on forums
qery said:
while in recovery, you can use ADB to transfer files to prime from PC via data cable. look for ADB PUSH here on forums
Click to expand...
Click to collapse
thanks ill give it a try and get back with you
ok i found and did what it says it sees my prime but im getting this error now failed to write data 'protocal fault <no status>' *3%
now this
i am runnung this command - adb push pac_tf201_4.3.Build-1_20131003.zip /sdcard/ ..all i get is a protocol failure not sure what that means but i need help bad wiped internal and stuck in twrp recovery
trinitystudio said:
i am runnung this command - adb push pac_tf201_4.3.Build-1_20131003.zip /sdcard/ ..all i get is a protocol failure not sure what that means but i need help bad wiped internal and stuck in twrp recovery
Click to expand...
Click to collapse
You need to make sure sure you have all the Android files installed on your PC which I am sure you do. Also, you need to specify where the pac_tf201 build is located. This is what I did to push the version onto my TF201 in Recovery:
adb push c:/pac_tf201_4.3.Build-1_20131003.zip /sdcard/
I did the same with gapps but I made sure that both zip files (rom and gapps) were directly on my C drive and not anywhere else. Let me know if you need anymore help as I just barely did this a few days ago. Took me hours to get it but I have learned quite a bit from it. :good:
Edit: Make sure your directory is pointed to your sdk platform-tools folder as well in CMD.
alias4ever said:
You need to make sure sure you have all the Android files installed on your PC which I am sure you do. Also, you need to specify where the pac_tf201 build is located. This is what I did to push the version onto my TF201 in Recovery:
adb push c:/pac_tf201_4.3.Build-1_20131003.zip /sdcard/
I did the same with gapps but I made sure that both zip files (rom and gapps) were directly on my C drive and not anywhere else. Let me know if you need anymore help as I just barely did this a few days ago. Took me hours to get it but I have learned quite a bit from it. :good:
Edit: Make sure your directory is pointed to your sdk platform-tools folder as well in CMD.
Click to expand...
Click to collapse
i have done that all but putting it on the c:\ drive ....yes im pointed to that folder ill try c and get back to you thanks
edit: try c drive thing still a no go still getting protocol failure
Hardbricked!!!!!!!!!!!!!!
Well im hardbricked now asus wants $324 to fix so NOT!!!!!! Guess its time to go shopping lol
trinitystudio said:
Well im hardbricked now asus wants $324 to fix so NOT!!!!!! Guess its time to go shopping lol
Click to expand...
Click to collapse
Can you boot into fast boot at all? Or are you stuck at the Asus screen?
---------- Post added at 07:40 AM ---------- Previous post was at 07:39 AM ----------
alias4ever said:
Can you boot into fast boot at all? Or are you stuck at the Asus screen?
Click to expand...
Click to collapse
What would you plan on doing or what does anyone do with a hardbricked Prime as I am curious? Sorry to hear it.
It happens I have done roms for years from droid one to note2 never had a issue till now it was my own mistake so... I guess nothing to do but trash it prob going today to get Samsung note 8 or 10.1
Sent from my SCH-I605 using xda app-developers app
Do you by any chance have Asus sync running on your pc? It seems that this can interfere with adb.
Try killing all asus related programs on your pc through task manager and then try adb push again.
Sent from my SO-04E using xda app-developers app
This is what I'm curious about too. If there were photos on this SD card before you put it in the device, they will remain intact after a security wipe.
This is unclear to me based on the OP: You got the Bold as a graduation gift and would like to start using it i assume. (I also got this bold a couple days ago after my HTC One S died, bringing me to Blackberry after years of faithful service on Android. The 9900 is a great phone)
When you tried to use the phone, you were prompted to input your BBID credentials, which subsequently failed repeatedly. The phone has since been security wiped due to too many failed attempts. Upon opening the phone, the microSD that you had in there is gone.