Develop Bugs

how to put factory rom back on

can someone point me in the right direction on how to put factory recovery and rom back on my neighbors kindle fire so he can return it im not familar with kindle fire but did many android and windows before thanks

*Go here and download software http://www.amazon.com/gp/help/customer/display.html?nodeId=200790620
*Rename file to update.zip.
*Now go into twrp and do a FULL WIPE then install the file. Thats all their is to it. Ive done it before.

powerpoint45 said:
*Go here and download software http://www.amazon.com/gp/help/customer/display.html?nodeId=200790620
*Rename file to update.zip.
*Now go into twrp and do a FULL WIPE then install the file. Thats all their is to it. Ive done it before.
Click to expand...
Click to collapse
Will take off the twrp recovery as well? He wants to return it to bestbuy for refund

maxtcee said:
Will take off the twrp recovery as well? He wants to return it to bestbuy for refund
Click to expand...
Click to collapse
yes it will remove twrp make sure you do a full wipe before attempting or you could get some mild brickage requiring a factory cable. wipe factory reset,wipe cache,wipe dalvik, wipe system, flash update.zip reboot then system if prompted...

i wipe everything like you said and for some reason it boots into logo screen then a black screen and stays black i cant seem to get it back into recovery

Use adb shell and Pokey9000's rcmode (or the command line if possible) to change your bootmode to recovery and try it again. Be sure to wipe System and Factory Reset.
If you can't open a shell, you need a factory cable.

soupmagnet said:
Use adb shell and Pokey9000's rcmode (or the command line if possible) to change your bootmode to recovery and try it again. Be sure to wipe System and Factory Reset.
If you can't open a shell, you need a factory cable.
Click to expand...
Click to collapse
dont know what pokey 9000s rcmode but i tried kfu to change the bootmode to recovery but it just reboots and hangs right after the logo
can u explain pokey to me please
EDIT i d/l pokeys fbmode and replaced it in kfu and tried to change the boot mode to fastboot but still hanging am i doing anything wrong ?
any other suggestions

maxtcee said:
dont know what pokey 9000s rcmode but i tried kfu to change the bootmode to recovery but it just reboots and hangs right after the logo
can u explain pokey to me please
Click to expand...
Click to collapse
Okay let's take a step back for a second.
Open the KFU folder and "Shift" + "Right-click" on the folder containing adb.exe and fastboot.exe, and select "Open command window here".
In the window that pops up, enter: (with the device turned on)
Code:
adb shell idme ?
And copy the output here

soupmagnet said:
Okay let's take a step back for a second.
Open the KFU folder and "Shift" + "Right-click" on the folder containing adb.exe and fastboot.exe, and select "Open command window here".
In the window that pops up, enter: (with the device turned on)
Code:
adb shell idme ?
And copy the output here
Click to expand...
Click to collapse
i think my problem might be its not being recognized i keep getting waiting for device and in device manager i dont see kindle i see android adb interface

maxtcee said:
i think my problem might be its not being recognized i keep getting waiting for device and in device manager i dont see kindle i see android adb interface
Click to expand...
Click to collapse
im not seeing that option to open cmd prompt here
im using kfu 9.6 dont know if that makes a difference

maxtcee said:
im not seeing that option to open cmd prompt here
Click to expand...
Click to collapse
Shift + right-click...at the same time

soupmagnet said:
Shift + right-click...at the same time
Click to expand...
Click to collapse
im trying that but its not showing my that option
i see open and run as administrator
if i click on any of them comand prompt opens real quick and closes

maxtcee said:
im trying that but its not showing my that option
i see open and run as administrator
if i click on any of them comand prompt opens real quick and closes
Click to expand...
Click to collapse
I don't know anything about Windows, so I'm just guessing here. You're using Windows 7, correct? Do you have administrator privileges?
No matter, that's just the easy way, try...
Code:
cd /actual_path/to/kfu_folder/containing/adb
...then enter your commands.
---------- Post added at 04:59 PM ---------- Previous post was at 04:53 PM ----------
Let me reiterate, just in case it isn't clear. You don't actually type "/actual_path/to/kfu_folder/containing/adb"

maxtcee said:
i think my problem might be its not being recognized i keep getting waiting for device and in device manager i dont see kindle i see android adb interface
Click to expand...
Click to collapse
ok it says no C:\android-sdk-windows\platform-tools>adb shell idme
- exec '/system/bin/sh' failed: No such file or directory (2) -

soupmagnet said:
I don't know anything about Windows, so I'm just guessing here. You're using Windows 7, correct? Do you have administrator privileges?
No matter, that's just the easy way, try...
Code:
cd /actual_path/to/kfu_folder/containing/adb
...then enter your commands.
---------- Post added at 04:59 PM ---------- Previous post was at 04:53 PM ----------
Let me reiterate, just in case it isn't clear. You don't actually type "/actual_path/to/kfu_folder/containing/adb"
Click to expand...
Click to collapse
i know but its telling me
its not recognized

maxtcee said:
ok it says no C:\android-sdk-windows\platform-tools>adb shell idme
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
That's a bad thing. Your shell is missing or corrupt. You need the shell to change your bootmode to recovery to fix your problem. Without a shell, you need fastboot to be able to change bootmodes. But you need a shell to change the bootmode to fastboot. Darn.
The only way you get into fastboot now is with a factory cable.
http://forum.xda-developers.com/showpost.php?p=20380015

soupmagnet said:
That's a bad thing. Your shell is missing or corrupt. You need the shell to change your bootmode to recovery to fix your problem. Without a shell, you need fastboot to be able to change bootmodes. But you need a shell to change the bootmode to fastboot. Darn.
The only way you get into fastboot now is with a factory cable.
http://forum.xda-developers.com/showpost.php?p=20380015
Click to expand...
Click to collapse
thanks dude time to get drunk and worry about this in the am

Nevermind

Thepooch said:
Nevermind
Click to expand...
Click to collapse
Yeah, that page #2 is a tricky one, eh?

Yeah my bad didnt realize you were that deep yet lol

[GUIDE] Backing up a phone with broken display

I have seen several of threads asking about how to recover data from a phone that has a broken display.
Backing up a phone with broken display
Prerequisites
Rooted phone with broken display/digitizer/etc. Display is nonfunctional for whatever reason.
ADB for your platform. Downloads for Windows, Mac, and Linux can be found at my dev-host.
Drivers installed (Windows), rules file set up (Linux + Mac). Drivers for windows can be found here. Rules file for Linux can be found here.
Recovery file attached to this post. (twrp.img)
External sdcard with at least 2 GB free space inserted in your broken phone.
openrecoveryscript.txt file attached to this post.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Backing up your broken device
Extract the ADB zip somewhere convenient.
Move the twrp.img recovery file into the ADB extracted directory.
Move the openrecoveryscript.txt file into the ADB directory.
Open a command prompt / terminal window in the ADB directory.
Windows: Windows Key + R => Type in "cmd" then click "RUN".
Linux: Open a terminal window by selecting it from your applications.
ALL:
Code:
cd /path/to/ADB/directory
Pull the battery from your phone, place it back in and boot into recovery (VolUp + Home + Power).
Connect your phone to your computer
Make sure that the following command returns "XXXXXX recovery" before proceeding to the next step.
Code:
./adb devices
Expected output:
Code:
List of devices attached
XXXXXXX recovery
Now to install TWRP recovery to your device. Type the following commands ( after each line). Linux users: Make sure you prepend each command with "./", as in "./adb ...". ALL Make sure you type the commands in CAREFULLY.
Code:
adb push twrp.img /tmp/twrp.img
adb shell dd if=/tmp/twrp.img of=/dev/block/mmcblk0p18
Wait until the last command above returns an output similar to below before proceeding to the next step:
Code:
12916+0 records in
12916+0 records out
6612992 bytes (6.3MB) copied, 1.094278 seconds, 5.8MB/s
Now pull your phones battery and reboot into recovery once again.
Run the following command to make sure your phone has booted into recovery completely.
Code:
adb devices
Expected output
Code:
List of devices attached
XXXXXXX recovery
Type the following to set up a script that will backup your phone to your external sdcard.
Code:
adb push openrecoveryscript.txt /cache/recovery/openrecoveryscript
Reboot your phone once more. This time, TWRP will begin backing up your ROM.
Wait for the backup to finish. You will know it is finished when you feel your phone reboot once more.
Optionally, you can check the state of your backup by running the following command and reading the last couple lines of it's output.
Code:
adb shell cat /tmp/recovery.log
Click to expand...
Click to collapse
Click to expand...
Click to collapse
That's it! Your entire system (/system, /data, /cache, and boot) will be backed up to your external sdcard. Just pop the sdcard in your replacement phone and you're good to go.
Enjoy and donate to the TWRP devs! This would not be possible if TWRP did not use the OpenRecoveryScript scripting engine!

Hellua nice guide :thumbup:
TEAM MiK
MikROMs Since 3/13/11

Man Cnexus! You are everywhere! Lol.
Nice guide. This will save lots of people :thumbup:
------------------------
Sprint Galaxy S3 "Supernexus" Thanks To Cyanogenmod
Whiplashh Rom
Look it up.

Is this method specific to the S3? I have an old S2 that I need to recover some photos from.

Hmm...boot your S2 into recovery, then connect it to your computer, run the following command and post the output for me.
Code:
adb shell ls

Hopefully I never need this guide but I think it should be a sticky. Good job!

This seems very helpful thank you.
This is a good option as well
https://code.google.com/p/androidscreencast/

CNexus said:
I have seen several of threads asking about how to recover data from a phone that has a broken display.
Backing up a phone with broken display
Click to expand...
Click to collapse
Thanks so much for the how-to.
I have a rooted Sprint Galaxy S3 with a broken display. I'm having a problem with getting it into recovery mode.
I believe when I hold down VolUp+Home+Power and reboot, it's loading a menu that's prompting me to select one of the boot options. It otherwise just sits there and never actually boots.
I've tried to use adb to boot it into recovery mode, but it also just sits there until I press the home key, at which point it just boots into normal mode.
Is there a way I can bypass any menus or does anyone with a working system know which option I should select at the menu?
Thanks,
Alex

Is your display broken? What does "adb devices" show when you're in that mode?

[GUIDE] Backing up a phone with broken display

I have seen several of threads asking about how to recover data from a phone that has a broken display.
Backing up a phone with broken display
Prerequisites
Rooted phone with broken display/digitizer/etc. Display is nonfunctional for whatever reason.
ADB for your platform. Downloads for Windows, Mac, and Linux can be found at my dev-host.
Drivers installed (Windows), rules file set up (Linux + Mac). Drivers for windows can be found here. Rules file for Linux can be found here.
Recovery file attached to this post. (twrp.img)
External sdcard with at least 2 GB free space inserted in your broken phone.
openrecoveryscript.txt file attached to this post.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Backing up your broken device
Extract the ADB zip somewhere convenient.
Move the twrp.img recovery file into the ADB extracted directory.
Move the openrecoveryscript.txt file into the ADB directory.
Open a command prompt / terminal window in the ADB directory.
Windows: Windows Key + R => Type in "cmd" then click "RUN".
Linux: Open a terminal window by selecting it from your applications.
ALL:
Code:
cd /path/to/ADB/directory
Pull the battery from your phone, place it back in and boot into recovery (VolUp + Home + Power).
Connect your phone to your computer
Make sure that the following command returns "XXXXXX recovery" before proceeding to the next step.
Code:
./adb devices
Expected output:
Code:
List of devices attached
XXXXXXX recovery
Now to install TWRP recovery to your device. Type the following commands ( after each line). Linux users: Make sure you prepend each command with "./", as in "./adb ...". ALL Make sure you type the commands in CAREFULLY.
Code:
adb push twrp.img /tmp/twrp.img
adb shell dd if=/tmp/twrp.img of=/dev/block/mmcblk0p18
Wait until the last command above returns an output similar to below before proceeding to the next step:
Code:
12916+0 records in
12916+0 records out
6612992 bytes (6.3MB) copied, 1.094278 seconds, 5.8MB/s
Now pull your phones battery and reboot into recovery once again.
Run the following command to make sure your phone has booted into recovery completely.
Code:
adb devices
Expected output
Code:
List of devices attached
XXXXXXX recovery
Type the following to set up a script that will backup your phone to your external sdcard.
Code:
adb push openrecoveryscript.txt /cache/recovery/openrecoveryscript
Reboot your phone once more. This time, TWRP will begin backing up your ROM.
Wait for the backup to finish. You will know it is finished when you feel your phone reboot once more.
Optionally, you can check the state of your backup by running the following command and reading the last couple lines of it's output.
Code:
adb shell cat /tmp/recovery.log
Click to expand...
Click to collapse
Click to expand...
Click to collapse
That's it! Your entire system (/system, /data, /cache, and boot) will be backed up to your external sdcard. Just pop the sdcard in your replacement phone and you're good to go.
Enjoy and donate to the TWRP devs! This would not be possible if TWRP did not use the OpenRecoveryScript scripting engine!

Or you can use skip's unified toolkit.
I literally just used it. Moving the backup to my new device right now.

loserskater said:
Or you can use skip's unified toolkit.
I literally just used it. Moving the backup to my new device right now.
Click to expand...
Click to collapse
Whatever floats your boat :good:

Sorry, had to
Sent from my SGH-I747 using Tapatalk 2

Actually, this process might directly meet my needs.
You mentioned that the recovery image and script were attached to the initial post, though I must be missing something in that I don't see where they might be. Perhaps you could offer a pointer, please?
- ooofest

Ah sorry, you can find the files here
http://forum.xda-developers.com/showthread.php?t=2353828
Don't use the twrp.img from there though...go to the twrp website and download the latest .img file for your phone (d2att)
Sent from my S3 on Sense 5 (you jelly?)

CNexus said:
Ah sorry, you can find the files here
http://forum.xda-developers.com/showthread.php?t=2353828
Don't use the twrp.img from there though...go to the twrp website and download the latest .img file for your phone (d2att)
Click to expand...
Click to collapse
Thanks - I downloaded the appropriate files, but wonder if this can be used on a stock phone.
That is, I was able to push twrp.img to /tmp/twrp.img, but cannot write in the next step:
Code:
adb shell dd if=/tmp/twrp.img of=/dev/block/mmcblk0p18
/dev/block/mmcblk0p18: cannot open for write: Permission denied
This is a stock AT&T phone, in recovery mode, never been rooted.
- ooofest

You need to be rooted for this to work.

CNexus said:
You need to be rooted for this to work.
Click to expand...
Click to collapse
Ya know . . . I need to read things more carefully. Was so excited to see something that might possibly help. Sorry about that.
It's been awhile since I looked into rooting the Galaxy S III and will look around, but don't recall that this can be rooted from recovery, unfortunately. And, it seems that USB Debugging is not turned on when it boots to the lockscreen.
Hm.
- ooofest

[GUIDE] Backing up a phone with broken display

I have seen several of threads asking about how to recover data from a phone that has a broken display.
Backing up a phone with broken display
Prerequisites
Rooted phone with broken display/digitizer/etc. Display is nonfunctional for whatever reason.
ADB for your platform. Downloads for Windows, Mac, and Linux can be found at my dev-host.
Drivers installed (Windows), rules file set up (Linux + Mac). Drivers for windows can be found here. Rules file for Linux can be found here.
Recovery file attached to this post. (twrp.img)
External sdcard with at least 2 GB free space inserted in your broken phone.
openrecoveryscript.txt file attached to this post.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Backing up your broken device
Extract the ADB zip somewhere convenient.
Move the twrp.img recovery file into the ADB extracted directory.
Move the openrecoveryscript.txt file into the ADB directory.
Open a command prompt / terminal window in the ADB directory.
Windows: Windows Key + R => Type in "cmd" then click "RUN".
Linux: Open a terminal window by selecting it from your applications.
ALL:
Code:
cd /path/to/ADB/directory
Pull the battery from your phone, place it back in and boot into recovery (VolUp + Home + Power).
Connect your phone to your computer
Make sure that the following command returns "XXXXXX recovery" before proceeding to the next step.
Code:
./adb devices
Expected output:
Code:
List of devices attached
XXXXXXX recovery
Now to install TWRP recovery to your device. Type the following commands ( after each line). Linux users: Make sure you prepend each command with "./", as in "./adb ...". ALL Make sure you type the commands in CAREFULLY.
Code:
adb push twrp.img /tmp/twrp.img
adb shell dd if=/tmp/twrp.img of=/dev/block/mmcblk0p18
Wait until the last command above returns an output similar to below before proceeding to the next step:
Code:
12916+0 records in
12916+0 records out
6612992 bytes (6.3MB) copied, 1.094278 seconds, 5.8MB/s
Now pull your phones battery and reboot into recovery once again.
Run the following command to make sure your phone has booted into recovery completely.
Code:
adb devices
Expected output
Code:
List of devices attached
XXXXXXX recovery
Type the following to set up a script that will backup your phone to your external sdcard.
Code:
adb push openrecoveryscript.txt /cache/recovery/openrecoveryscript
Reboot your phone once more. This time, TWRP will begin backing up your ROM.
Wait for the backup to finish. You will know it is finished when you feel your phone reboot once more.
Optionally, you can check the state of your backup by running the following command and reading the last couple lines of it's output.
Code:
adb shell cat /tmp/recovery.log
Click to expand...
Click to collapse
Click to expand...
Click to collapse
That's it! Your entire system (/system, /data, /cache, and boot) will be backed up to your external sdcard. Just pop the sdcard in your replacement phone and you're good to go.
Enjoy and donate to the TWRP devs! This would not be possible if TWRP did not use the OpenRecoveryScript scripting engine!

Don't forget to attach your script.txt file!
Also, I was thinking if its easy enough to just edit your existing script, maybe post ones that can wipe data/factory reset and possibly some other functions available in TWRP?
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Don't forget to attach your script.txt file!
Click to expand...
Click to collapse
Ah, whoops! Files can be found here until I can get to a computer: http://forum.xda-developers.com/showthread.php?p=43332650
The Thanks button is just to avoid "THANKS" posts in threads. Nothing more. Don't defeat the purpose of why it was introduced.

DocHoliday77 said:
Also, I was thinking if its easy enough to just edit your existing script, maybe post ones that can wipe data/factory reset and possibly some other functions available in TWRP?
Click to expand...
Click to collapse
I don't want to reinvent the wheel, but there areapps that can do that I'll post a couple scripts later though :thumbup:
The Thanks button is just to avoid "THANKS" posts in threads. Nothing more. Don't defeat the purpose of why it was introduced.

CNexus said:
I don't want to reinvent the wheel, but there areapps that can do that I'll post a couple scripts later though :thumbup:
The Thanks button is just to avoid "THANKS" posts in threads. Nothing more. Don't defeat the purpose of why it was introduced.
Click to expand...
Click to collapse
Which apps? I'm currently in a position where I need to erase my phone but the screen doesn't work.

porfymartinez said:
Which apps? I'm currently in a position where I need to erase my phone but the screen doesn't work.
Click to expand...
Click to collapse
Ah. Replace the text inside the openrecoveryscript.txt with this following
Code:
wipe data
wipe cache
wipe dalvik
wipe system
Optionally, add the following (to the script I wrote above) to wipe your internal storage.
Code:
mount data
cmd rm -r /data/media
The Thanks button is just to avoid "THANKS" posts in threads. Nothing more. Don't defeat the purpose of why it was introduced.

Nexus 7 (2013) Stuck on boot loop: Android is starting - Optimizing apps.

I've used the tablet for 6 years now and suddenly ... The battery drained to 0 so after charging and powering up .. it got stuck at boot loop, as it gets to the word android after the 5 dots animation. then the android is starting - optimizing app x of 37...
I've tried disconnecting the battery cable and reconnecting them again.
Wiping cash several times.
Usb debuging is enabled.
No root or custom recovery.
The question is .. if I can solve this problem without factory reset as I would resort to that if there's nothing else ... I have some important data That I'd like to backup if I can. even IF I can backup the data then factory reset it .. that would be fine.

corabict said:
I've used the tablet for 6 years now and suddenly ... The battery drained to 0 so after charging and powering up .. it got stuck at boot loop, as it gets to the word android after the 5 dots animation. then the android is starting - optimizing app x of 37...
I've tried disconnecting the battery cable and reconnecting them again.
Wiping cash several times.
Usb debuging is enabled.
No root or custom recovery.
The question is .. if I can solve this problem without factory reset as I would resort to that if there's nothing else ... I have some important data That I'd like to backup if I can. even IF I can backup the data then factory reset it .. that would be fine.
Click to expand...
Click to collapse
if ok connect to computer then you can move files to computer

jjgvv said:
if ok connect to computer then you can move files to computer
Click to expand...
Click to collapse
jjgvv said:
if ok connect to computer then you can move files to computer
Click to expand...
Click to collapse
I can't choose file transfer as USB mode .. so I can't see the files .. even though I hear the sound of USB connecting but I can't see the device.

corabict said:
I can't choose file transfer as USB mode .. so I can't see the files .. even though I hear the sound of USB connecting but I can't see the device.
Click to expand...
Click to collapse
reboot recovery and adb pull sdcard

corabict said:
No root or custom recovery.
Click to expand...
Click to collapse
If your hardware/eMMC is not faulty, then...
If it is unlocked, flash/boot TWRP and get your data.
If it is locked, get RESTOCK and try SAFE UNLOCK...
"Unlock your device without data loss. MiFlash is described in the Unbricking Guide:
https://forum.xda-developers.com/showpost.php?p=75360854&postcount=199
Do not proceed unless you have read the unbricking guide and downloaded all components."

jjgvv said:
reboot recovery and adb pull sdcard
Click to expand...
Click to collapse
Thank you so much for your help.
I tried to do that and it returns an error
adb: error: remote object '\sdcard' does not exist
I tried to make sure the device is recognized so I used Adb devices and it returns:
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
057f2788 device
But that when it's stuck on the animation optimization loop.
If I'm in bootloader ore recovery mod ... it returns
List of devices
And it's empty. So what do you suggest.
k23m said:
If your hardware/eMMC is not faulty, then...
If it is unlocked, flash/boot TWRP and get your data.
If it is locked, get RESTOCK and try SAFE UNLOCK...
"Unlock your device without data loss. MiFlash is described in the Unbricking Guide:
https://forum.xda-developers.com/showpost.php?p=75360854&postcount=199
Do not proceed unless you have read the unbricking guide and downloaded all components."
Click to expand...
Click to collapse
Thank you so much for your help.
I used restock 1 and it downloaded the stock but after that ... I get that
Can't install .inf
because it is not better than the current drivers.
INFO: Returning with code 0x100
Device not found...
1. disconnect it from PC
2. reboot to bootloader again
3. reconnect it to PC
Press any key to continue . . .
And I can't get past that.

corabict said:
Thank you so much for your help.
I tried to do that and it returns an error
adb: error: remote object '\sdcard' does not exist
I tried to make sure the device is recognized so I used Adb devices and it returns:
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
057f2788 device
But that when it's stuck on the animation optimization loop.
If I'm in bootloader ore recovery mod ... it returns
List of devices
And it's empty. So what do you suggest.
Thank you so much for your help.
I used restock 1 and it downloaded the stock but after that ... I get that
Can't install .inf
because it is not better than the current drivers.
INFO: Returning with code 0x100
Device not found...
1. disconnect it from PC
2. reboot to bootloader again
3. reconnect it to PC
Press any key to continue . . .
And I can't get past that.
Click to expand...
Click to collapse
maybe the posts in this thread can help you
[Q] How to mount internal storage through ADB?
A few days ago I cracked my phone screen and I can't see anything, but I want to access the internal storage, can I do this through ADB command?if possible, HOW? Please! can someone help me! Thanks!
forum.xda-developers.com
on boot loop screen of course

jjgvv said:
maybe the posts in this thread can help you
[Q] How to mount internal storage through ADB?
A few days ago I cracked my phone screen and I can't see anything, but I want to access the internal storage, can I do this through ADB command?if possible, HOW? Please! can someone help me! Thanks!
forum.xda-developers.com
on boot loop screen of course
Click to expand...
Click to collapse
Sorry for bothering you ... but really I Don't know what to do.
I used ADb shell then ls ... and listed all the files and sdcard is one of them but when I try to access it it returns this error
cd: /sdcard: No such file or directory
Then tried ..
>> Adb shell ls /sdcard/sdcard
it returns the same message.
>> c:\Adb>adb shell ls /mnt
asec
expand
media_rw
obb
runtime
sdcard *******************
secure
user
c:\Adb>adb shell ls /mnt/sdcard/
/mnt/sdcard/: No such file or directory
So why this error??
Do I need root or what. ??
and if so can I flash twerp and do backup ..if you have any links,
THank you very much for your help.

corabict said:
Sorry for bothering you ... but really I Don't know what to do.
I used ADb shell then ls ... and listed all the files and sdcard is one of them but when I try to access it it returns this error
cd: /sdcard: No such file or directory
Then tried ..
>> Adb shell ls /sdcard/sdcard
it returns the same message.
>> c:\Adb>adb shell ls /mnt
asec
expand
media_rw
obb
runtime
sdcard *******************
secure
user
c:\Adb>adb shell ls /mnt/sdcard/
/mnt/sdcard/: No such file or directory
So why this error??
Do I need root or what. ??
and if so can I flash twerp and do backup ..if you have any links,
THank you very much for your help.
Click to expand...
Click to collapse
adb pull /
and see What happened
avoid adb shell as it needs root.

jjgvv said:
adb pull /
and see What happened
avoid adb shell as it needs root.
Click to expand...
Click to collapse
Yes I tried that and returns this
>>c:\Adb>adb pull /
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: warning: stat failed for path /proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/self/task/1208/root/proc/222/task/1208/fd/15: Protocol not available