Hi guys,
I accidentally wiped my SD-EXT and card/system/data in TWRP - basically everything was wiped. Consequently I cannot mount, it does not show up in Windows. I'm sitting in TWRP with no OS atm.
I found this fix:
- boot to twrp
- test adb with "adb devices"
- open shell -> "adb shell"
- issue "echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file"
- now the sdcard should mount to the computer
- windows will probably respond that the volume/device needs formatted before using it
- choose quick format and let it format it as fat32 block size 4096
However, my device is not being recognized under ADB. When I do adb devices, it says device not found and nothing comes up. Any ideas? The driver should be installed and under device manager it shows up as android phone. How can I get my computer to recognize adb? Thank you!
i think your pc will recognize your device as a removable drive.
help
dieandromeda said:
i think your pc will recognize your device as a removable drive.
Click to expand...
Click to collapse
Same issue except it will not recognise Fire in utility...how do I boot into TWRP, I can on Kindle but can not access shell....HELP
philbarter said:
Same issue except it will not recognise Fire in utility...how do I boot into TWRP, I can on Kindle but can not access shell....HELP
Click to expand...
Click to collapse
sounds like a separate issue...uninstall/reinstall your drivers and try again
arh2o said:
Hi guys,
I accidentally wiped my SD-EXT and card/system/data in TWRP - basically everything was wiped. Consequently I cannot mount, it does not show up in Windows. I'm sitting in TWRP with no OS atm.
I found this fix:
- boot to twrp
- test adb with "adb devices"
- open shell -> "adb shell"
- issue "echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file"
- now the sdcard should mount to the computer
- windows will probably respond that the volume/device needs formatted before using it
- choose quick format and let it format it as fat32 block size 4096
However, my device is not being recognized under ADB. When I do adb devices, it says device not found and nothing comes up. Any ideas? The driver should be installed and under device manager it shows up as android phone. How can I get my computer to recognize adb? Thank you!
Click to expand...
Click to collapse
What happens when you reboot? Stuck at boot screen? Try changing your bootmode to 4000 using fastboot and reboot to see if it boots normally. Your personall data will be gone but the OS should still load.
Sent from my Amazon Kindle Fire using xda premium
Related
I just ran a nandroid backup for my Eris which was at stock 2.1 w/ root. I first partitioned the sd to swap - 3072 MB, ext2 swap 3072 MB, and fat32 - remainder. Realizing this was stupid, I went back and changed the partition to swap - 0, ext2 - 512 MB, fat32 - remainder 7680 MB or 7.5 GB. I moved ext2 to ext3 and booted the phone. All my sd was cleared so I copied everything back on (I saved all sd contents to my computer prior to this). I went back to recovery and flashed Eris Lightning 3.02. Everything went successful and when it rebooted, I saw the droid guys, then the "quietly brilliant", then "Verizon" screens. It then began running the "quietly brilliant" and "verizon" screens over and over. I pulled the battery and powered up again but it's still running those two screens over and over. I booted into recovery and attached my phone to the computer. I opened command prompt, entered " sd C:\android-sdk-windows\tools" and then entered "adb devices". It reads "List of devices attached" but there are none. I attempted to add the driver back to my device but when I go to device manager and click "update driver" and point it to the tools directory in SDK, it says that "Windows could not find driver software for your device".
If I can't communicate with my phone via usb and it wont boot, how can I get it to recover?
Any suggestions would help, I'm scratching my head here. I really don't want to have to buy another phone.
If you can get into the recovery there is the option to connect via USB and you can install another ROM. Wipe and Flash off the SD and reboot. Hope this helps.
Just sounds like your stuck in a boot loop is all.
joshw0000 said:
I just ran a nandroid backup for my Eris which was at stock 2.1 w/ root. I first partitioned the sd to swap - 3072 MB, ext2 swap 3072 MB, and fat32 - remainder. Realizing this was stupid, I went back and changed the partition to swap - 0, ext2 - 512 MB, fat32 - remainder 7680 MB or 7.5 GB. I moved ext2 to ext3 and booted the phone. All my sd was cleared so I copied everything back on (I saved all sd contents to my computer prior to this). I went back to recovery and flashed Eris Lightning 3.02. Everything went successful and when it rebooted, I saw the droid guys, then the "quietly brilliant", then "Verizon" screens. It then began running the "quietly brilliant" and "verizon" screens over and over. I pulled the battery and powered up again but it's still running those two screens over and over. I booted into recovery and attached my phone to the computer. I opened command prompt, entered " sd C:\android-sdk-windows\tools" and then entered "adb devices". It reads "List of devices attached" but there are none. I attempted to add the driver back to my device but when I go to device manager and click "update driver" and point it to the tools directory in SDK, it says that "Windows could not find driver software for your device".
If I can't communicate with my phone via usb and it wont boot, how can I get it to recover?
Any suggestions would help, I'm scratching my head here. I really don't want to have to buy another phone.
Click to expand...
Click to collapse
I don't think you're bricked. A couple of things I noticed.
1. If you're using windows, and I assume you are, changing directory is "cd" and not "sd." It may have been a typo on your part in the post here, but that could fix things.
2. Go to the tools directory of your SDK folder and in the cmd, type "adb reboot recovery" and see what happens.
3. You can access the recovery image manually by pulling your battery and then hold the volume up button + end (red) button at the same time.
I hope this helps.
tburns said:
If you can get into the recovery there is the option to connect via USB and you can install another ROM. Wipe and Flash off the SD and reboot. Hope this helps.
Just sounds like your stuck in a boot loop is all.
Click to expand...
Click to collapse
What he said. Just boot into recovery, switch into MS mode, and load up another ROM into the root of your SD card, and then install it.
I think I've had 3 total boot loops. No big deal. the first one is always when panic mode hits. Then you realize you're still ok.
When you mentioned wiping, I remember that I didn't wipe date or dalvik-cache. I wiped them both and I'm trying to re-flash the rom to see if it will boot this time.
Also, that was a typo in my original post. I did enter "cd". I tried "adb reboot recovery" but it wouldn't see my phone. If I ever do get my phone working again (for my records) would someone give some step-by-step instructions on the commands to use to flash a recovery.
IT WORKED!!!!!!! I'M AT THE SET-UP SCREEN OF ERIS LIGHTNING!!!!
I need a beer!
Thanks for the quick responses everyone!
Nice, and enjoy!
-------------------------------------
Sent via the XDA Tapatalk App
Folks - Any help would be greatly appreciated.
I was trying to instal CM-10.1 on my U8800, copied the file downloaded from here on my SD card and used CWM to install. Forgot to make a backup (Noob mistake ).
The software didn't fully install and now the the problem is that while I can access both CWM Mod Recovery and the pink screen, I am unable to mound the external sd card (cannot write to ums lunfile) and neither are the drives showing up when I connect to the pc via USB in pink screen.
Very worried on how to install a rom as both internal and external sd cards are inaccessible by pc and phone respectively.
You can use adb push while cwm is running.
Sent from my Nexus 4 using xda premium
enemix said:
You can use adb push while cwm is running.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I'm not sure how to do that. I've just done a few google searches, not sure if I have the right results. Would you have any link/tutorial ?
If you haven't done so already, download and install the Android SDK from developer.google.com.
What you want from it is the debug driver and adb.
Then boot your device into CWM and connect it to computer, use the debug driver from the SDK.
Mount internal storage in CWM and check its mount location.
Open the folder where adb.exe is located on your computer and copy your ROM.zip to that folder.
Open a command prompt there and type "adb devices", your device should show up in the list.
Then type "adb push ROM.zip /mnt/sdcard/ROM.zip" to copy the file. (replace /mnt/sdcard if your internal storage is mounted elsewhere)
Good luck and be careful, I'm just trying to help but I'm not responsible if you do something without using some common sense.
Sent from my GT-p6800 using xda premium
Hello !
I broke the screen of my Nexus 4 last week. Before sending it to change its screen, I would like to backup the data saved in my internal SDCard (particularly the pictures...). To do that, I followed this thread http://forum.xda-developers.com/nexus-4/general/nexus-4-guide-unlock-bootloader-root-t2266654 without performing a reboot between the bootloader unlocking and the installation of the last CWM as mentionned here : http://forum.xda-developers.com/showpost.php?p=44859053&postcount=8. Now I can launch CWM and see my device with adb but when I run a "adb pull /data/media", no piece of data is saved... I logged on the device with "adb shell" and I saw that the /data/media folder seems empty. Do you have any idea about how to recover these data ?
Thanks a lot for your help
Try /data/media/0
Sent from my Nexus 5
jd1639 said:
Try /data/media/0
Sent from my Nexus 5
Click to expand...
Click to collapse
remote object '/data/media/0' does not exist...
Caradhras said:
Hello !
I broke the screen of my Nexus 4 last week. Before sending it to change its screen, I would like to backup the data saved in my internal SDCard (particularly the pictures...). To do that, I followed this thread http://forum.xda-developers.com/nexus-4/general/nexus-4-guide-unlock-bootloader-root-t2266654 without performing a reboot between the bootloader unlocking and the installation of the last CWM as mentionned here : http://forum.xda-developers.com/showpost.php?p=44859053&postcount=8. Now I can launch CWM and see my device with adb but when I run a "adb pull /data/media", no piece of data is saved... I logged on the device with "adb shell" and I saw that the /data/media folder seems empty. Do you have any idea about how to recover these data ?
Thanks a lot for your help
Click to expand...
Click to collapse
Go into Mount and Storage, then mount /data, then try pulling with adb.
Moon2 said:
Go into Mount and Storage, then mount /data, then try pulling with adb.
Click to expand...
Click to collapse
Error mounting /data. I don't really understand why...
can anyone help me please i need to retrieve msgstore.db.crypt7 from my internal memory i have rooted my phone and have omega custom rom.i accidentally deleted the whole folder using es file explorer what's app only retrieves the message back 7 days ago and i need to go back further more,i have tried undelete and digger disk both dont find the internal memory i have tried several applications but wont find my phone i have enabled usb debug mode still wont find my phone i have heard recuva works but sgs5 doesnt have usb mass storage but on my pc windows 7 it shows portable device so i can see my internal and external but not through programs can anyone help me please?
bump any help please?
If you did the smart thing i.e. turned your phone off immediately after you deleted the file, you should be able to recover it. But if you kept mucking around (in addition to not having a backup of your phone), all bets are off. You may well have overwritten the database if you continued to use the phone.
Your best bet would be to copy the area of phone memory where the database is or was. That both preserves a copy of what is recoverable and lets you avail yourself of the large number of PC based data recovery programs available.
The following terminal (CLI) commands should image (make an exact copy) of the /data and /system partitions to your external SD card. Then use a PC based data recovery program to recover the deleted file. Check these commands for typos before executing them. A typo could make a real mess of your phone's file system.
$ su
# dd if=/dev/block/mmcblk0p25 of=/extSdCard/data.img
# dd if=/dev/block/mmcblk0p23 of=/extSdCard/system.img
.
fffft said:
If you did the smart thing i.e. turned your phone off immediately after you deleted the file, you should be able to recover it. But if you kept mucking around (in addition to not having a backup of your phone), all bets are off. You may well have overwritten the database if you continued to use the phone.
Your best bet would be to copy the area of phone memory where the database is or was. That both preserves a copy of what is recoverable and lets you avail yourself of the large number of PC based data recovery programs available.
The following terminal (CLI) commands should image (make an exact copy) of the /data and /system partitions to your external SD card. Then use a PC based data recovery program to recover the deleted file. Check these commands for typos before executing them. A typo could make a real mess of your phone's file system.
$ su
# dd if=/dev/block/mmcblk0p25 of=/extSdCard/data.img
# dd if=/dev/block/mmcblk0p23 of=/extSdCard/system.img
.
Click to expand...
Click to collapse
Thanks i've tried every recovery software for android but it's not detecting any of the internal memory as sgs5 does not have usb mass storage i have enabled usb debug settings i have the samsung usb drivers but it shows up on my windows 7 as a portable device.
do you recommend any decent software or tutorial's which might help me recover it.
Thanks for your help!
xxmcvapourxx said:
i've tried every recovery software for android but it's not detecting any of the internal memory as sgs5 does not have usb mass storage
Click to expand...
Click to collapse
You didn't follow any part of what I suggested, so it's a mystery why you quoted my post. I specifically advocated using PC based data recovery software, not an android app. And at no time would you need your S5 to be in MSC (mass storage) mode.
Use the posted commands to copy your memory contents to a SD card, plug the SD card into a PC and then use a PC based data recovery app. The commands can be entered from a terminal emulator app, TWRP or an ADB shell session CLI.
Good luck
.
I was in serious trouble.
When installing a new ROM in TWRP I accidentally deleted the internal storage !!
I can not install any ROM, because it always returns to Recovery, otherwise nothing happens.
What can I do???
You can't physicaly delete internal storage using recovery, you just did format. I don't know reason why you can't install ROM though. Maybe flash stock ROM first, using this tutorial.
tarnagy said:
I was in serious trouble.
When installing a new ROM in TWRP I accidentally deleted the internal storage !!
I can not install any ROM, because it always returns to Recovery, otherwise nothing happens.
What can I do???
Click to expand...
Click to collapse
use adb shell or run it in twrp terminal
adb shell
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Thanks!!!
Hello,
Formatting internal storage is not a problem at all. Normally I do it everytime I install new ROM - format all data and cleaning all partitions (such a habit to ensure I do a clean install )
BUT...
you have to load your rom from extrnal USB stick so you need the OTG cable and make sure you have your rom and gapps (if needed) on that stick.
All you need then is to switch the phone off plug the cable with stick and launch the phone into TWRP - it will detect the USB automatically and you can access the directory. If the directory appears empty - go to mount menu and force mounting the OTG - sometimes you need to push the button twice I noticed.
Good Luck!