Related
I want to find an way on how to turn my asus tf700t into a storage mass usb so that i can run a recovery data software on my laptop and hope to recover photos and videos that i accidentally lost after I did a factory reset and wiped all my info!!!
Can you guys let me know if there is another way?
If your device is rooted and you have a microSD or SD card that is at least as big as the device's internal storage, you can make a full image of the data partition and try running your data recovery software on that image. The partition to copy is /dev/block/mmcblk0p8.
I do have root access and the sd card to conduct such procedure! now I need to figure out how to get to that particular file partition and copy it into my sd card.
/dev/block/mmcblk0p8.
manga\\//Colombia said:
I do have root access and the sd card to conduct such procedure! now I need to figure out how to get to that particular file partition and copy it into my sd card.
/dev/block/mmcblk0p8.
Click to expand...
Click to collapse
Run this in adb shell:
Code:
su (if you are not already root)
dd if=/dev/block/mmcblk0p8 of=/Removable/MicroSD/data.ext4 bs=32k
For the full size SD card in the dock, adjust the output path appropriately. It will take a while, as it needs to copy almost 32 or 64 GB.
If the image is only 4 GB, that's because of a limitation in your dd commmand and you need to find a version with large file support. Of course you should not install any apps as this reduces your chance for data recovery.
Thank you for your time.! I will let you know what happens. if it works, it can help those who are in the same shoes. as of today, I havent really found an answer. Although I am not an expert on using adb shell. I see I need the SDK android install in my laptop to run a cmd and then the adb shell.
once I run the code you mentioned above. how do i manage to copy/ mirror that file into my sd card? any codes I need to know? sorry
_that said:
Run this in adb shell:
Code:
su (if you are not already root)
dd if=/dev/block/mmcblk0p8 of=/Removable/MicroSD/data.ext4 bs=32k
For the full size SD card in the dock, adjust the output path appropriately. It will take a while, as it needs to copy almost 32 or 64 GB.
If the image is only 4 GB, that's because of a limitation in your dd commmand and you need to find a version with large file support. Of course you should not install any apps as this reduces your chance for data recovery.
Click to expand...
Click to collapse
manga\\//Colombia said:
once I run the code you mentioned above. how do i manage to copy/ mirror that file into my sd card? any codes I need to know? sorry
Click to expand...
Click to collapse
The "dd" command with the given parameters copies an image of your /data partition into a file on the sd card.
help
View attachment 2478723
I am kind of lost--figuring out how to do that! sorry
I have connected my asus tablet to my laptop. I ran cmd and input the data! nothing happens..
manga\\//Colombia said:
View attachment 2478723
I am kind of lost--figuring out how to do that! sorry
I have connected my asus tablet to my laptop. I ran cmd and input the data! nothing happens..
Click to expand...
Click to collapse
Your screenshot does not show what you typed. When you run "adb shell", you should get a prompt from your TF700 where you can run the su and dd commands (type Ctrl+D or "exit" and Enter to exit).
manga\\//Colombia said:
View attachment 2478723
I am kind of lost--figuring out how to do that! sorry
I have connected my asus tablet to my laptop. I ran cmd and input the data! nothing happens..
Click to expand...
Click to collapse
You may want to check out this guide on adb and adb shell:
http://forum.xda-developers.com/showthread.php?t=2141817
_that said:
Your screenshot does not show what you typed. When you run "adb shell", you should get a prompt from your TF700 where you can run the su and dd commands (type Ctrl+D or "exit" and Enter to exit).
Click to expand...
Click to collapse
I followed the instructions..bernblb provided below... here it is a picture of what i got.
Am I supposed to run this adb shell command with a terminal emulator...install one and run the code?
manga\\//Colombia said:
I followed the instructions..bernblb provided below... here it is a picture of what i got.
Am I supposed to run this adb shell command with a terminal emulator...install one and run the code?
Click to expand...
Click to collapse
That does not look as if you have root on your tablet. Here's what it looks like when I start an adb shell on mine:
Code:
C:\android-sdk\sdk\platform-tools>adb devices
List of devices attached
C9OKAS062039 device
C:\android-sdk\sdk\platform-tools>adb shell
[email protected]:/ #
Here is where you would run the dd command.
What do you get if you type:
adb shell - then hit <enter>
su <enter>
manga\\//Colombia said:
I followed the instructions..bernblb provided below... here it is a picture of what i got.
Click to expand...
Click to collapse
You forgot to run "su" before "dd".
I do have root access!!! check out my picture....
berndblb said:
That does not look as if you have root on your tablet. Here's what it looks like when I start an adb shell on mine:
Code:
C:\android-sdk\sdk\platform-tools>adb devices
List of devices attached
C9OKAS062039 device
C:\android-sdk\sdk\platform-tools>adb shell
[email protected]:/ #
Here is where you would run the dd command.
What do you get if you type:
adb shell - then hit <enter>
su <enter>
Click to expand...
Click to collapse
okay.. after i typed su i got [email protected]:/ #... then i copy paste then dd command and i got this!!! i have a 32 gb micro sd card inserted in the asus tablet keyboard dock...
manga\\//Colombia said:
okay.. after i typed su i got [email protected]:/ #... then i copy paste then dd command and i got this!!! i have a 32 gb micro sd card inserted in the asus tablet keyboard dock...
Click to expand...
Click to collapse
It's hard to help you if you don't read carefully what I wrote:
_that said:
For the full size SD card in the dock, adjust the output path appropriately.
Click to expand...
Click to collapse
I assume you have the microSD card in a microSD to SD adapter, so you have to treat it as a full size SD card - change MicroSD to SD in the dd command line.
_that said:
Run this in adb shell:
Code:
su (if you are not already root)
dd if=/dev/block/mmcblk0p8 of=/Removable/MicroSD/data.ext4 bs=32k
For the full size SD card in the dock, adjust the output path appropriately. It will take a while, as it needs to copy almost 32 or 64 GB.
If the image is only 4 GB, that's because of a limitation in your dd commmand and you need to find a version with large file support. Of course you should not install any apps as this reduces your chance for data recovery.
Click to expand...
Click to collapse
Hello _That
I did run the command with the proper SD path! but I got 4 gb image!!
in your response--regarding to find a version with a large file support? you mean maybe a 64 gb sd card?
I am gonna try to see if I can run a data recovery on that SD card and see what I can recover from there!! what data recovery for ext4 files software do you recommend??
manga\\//Colombia said:
I did run the command with the proper SD path! but I got 4 gb image!!
in your response--regarding to find a version with a large file support? you mean maybe a 64 gb sd card?
Click to expand...
Click to collapse
No - as I wrote this is a limitation of the dd implementation. I think Busybox comes with a better dd, but you'd need to push it via adb to a temporary filesystem to avoid overwriting anything in /data. Try playing with the truncated image you have now - if you can recover any files from it, it's worth trying to make a complete image.
manga\\//Colombia said:
I am gonna try to see if I can run a data recovery on that SD card and see what I can recover from there!! what data recovery for ext4 files software do you recommend??
Click to expand...
Click to collapse
I have no experience with any data recovery tools. Try googling "recover formatted ext4" or so. Note that the software must be able to work with an image file, not only a raw partition.
Free and open source recovery software that I can recomend. http://www.cgsecurity.org/
after running a recovery data soft on that external sd card where i copy the image of that 4 gb (partition) i wasnt able to recover the data i was looking for!!!! any ideas how to do step by step pushing that partition to a temp file system via adb
manga\\//Colombia said:
after running a recovery data soft on that external sd card where i copy the image of that 4 gb (partition) i wasnt able to recover the data i was looking for!!!!
Click to expand...
Click to collapse
You have to run the recovery software on the image file, not on the card. If you can recover *any* files from the image, it makes sense to try the next steps with a complete image.
Hi, I have Sony Xperia L (C2105) with Android 4.2.2 and it is rooted. My phone should have 8 GB of internal memory. Only 5.57 GB is usable but it would not matter. 4 GB of 5.57 GB is separated and marked as "sdcard0". So I can't install applications there but I can only move data of applications there. Remaining 1.57 GB is used as internal storage and all aplications are installed to this small storage. My memory card is marked as "sdcard1". Is there any way to increase internal storage or merge internal storage and sdcard0 to one big internal storage?
Donald750 said:
Hi, I have Sony Xperia L (C2105) with Android 4.2.2 and it is rooted. My phone should have 8 GB of internal memory. Only 5.57 GB is usable but it would not matter. 4 GB of 5.57 GB is separated and marked as "sdcard0". So I can't install applications there but I can only move data of applications there. Remaining 1.57 GB is used as internal storage and all aplications are installed to this small storage. My memory card is marked as "sdcard1". Is there any way to increase internal storage or merge internal storage and sdcard0 to one big internal storage?
Click to expand...
Click to collapse
If someone could make this Guide for Xperia L!!!
http://forum.xda-developers.com/showthread.php?t=2712253
Till then you could use FolderMount if you have root access and mount obb and app data folders to external storage!
I think i got em
david pro said:
If someone could make this Guide for Xperia L!!!
http://forum.xda-developers.com/showthread.php?t=2712253
Till then you could use FolderMount if you have root access and mount obb and app data folders to external storage!
Click to expand...
Click to collapse
check this out, guys
http://forum.xda-developers.com/xperia-s/s-development/tutorial-increase-data-partition-t2821058
david pro said:
If someone could make this Guide for Xperia L!!!
http://forum.xda-developers.com/showthread.php?t=2712253
Till then you could use FolderMount if you have root access and mount obb and app data folders to external storage!
Click to expand...
Click to collapse
Please look into this post I made a few weeks ago...the thread's name it's posted in doesn't help in finfing it I must admit.
So here it is for our Xperia L:
Open a command window: CMD, then get into shell:
adb shell
Once in shell, type:
umount /storage
parted /dev/block/mmcblk0
print
This prints out the partition information of your phone's memory chip
You will see the partition numbers in the first column, partition names in the last one,
in between you have the start/end memory index and the partition size
------start---end---size
...
31---1795---3506---1711---userdata
32---3506---7818---4312---sdcardIn the above output, consider the values indicated in italic as not to be changed !
Now calculate (open a spreadsheed if you like) the new value for the end of the userdata partition,
and use the same value for the start of the sdcard partition
On your sheet it should look something like this if you added 2048 to the userdata size
------start---end---size
31---1795---5554---3759---userdata
32---5554---7818---2264---sdcard
Remove userdata and sdcard partitions:
rm 31
rm 32
Create the new userdata and sdcard partitions:
mkpartfs logical ext2 1795 5554
name 31 userdata
mkpartfs logical fat32 5554 7818
name 32 sdcard
Exit parted to go to the adb shell again:
quit
userdata partition (31) needs to have ext4 file system
The following will do the ext2->ext4 conversion:
cd /storage/sdcard1/fs-utils
tune2fs -j /dev/block/mmcblk0p31
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p31
e2fsck -fpDC0 /dev/block/mmcblk0p31
Now you can go to recovery and format the sdcard partition (default)
Then you can restore the backup you made before all this or do a clean install
I'm waiting for this phone which bought few days ago. Do we need to have firmware file for doing that? Could you please explain for dumbs the "
Now you can go to recovery and format the sdcard partition (default)
Then you can restore the backup you made before all this or do a clean install" thing??
My knowledge on this is reduced to flashtool and some root stuff. Thanks in advance
SoulFury said:
I'm waiting for this phone which bought few days ago. Do we need to have firmware file for doing that? Could you please explain for dumbs the "
Now you can go to recovery and format the sdcard partition (default)
Then you can restore the backup you made before all this or do a clean install" thing??
My knowledge on this is reduced to flashtool and some root stuff. Thanks in advance
Click to expand...
Click to collapse
That means: If you have made a backup, use the backup. If not, flash some software (and wipe cache/data == clean install)
So I connect phone to pc, do the thing using ADB, then flash it with stock firmware(for example) wiping cache,huh? Seems easy. Many thanks
I'm trying it but adb won't let me do umount /storage, it sais "invalid argument" :S
SoulFury said:
So I connect phone to pc, do the thing using ADB, then flash it with stock firmware(for example) wiping cache,huh? Seems easy. Many thanks
Click to expand...
Click to collapse
Hey man I just realized that after repartitioning you should better not flash stock firmware as I heard many cases in which the phone was bricked afterwards (with CM there is no problem)
Sent from my C2105 using XDA Free mobile app
I've read about it too, but it seems to happen randomly :S. But my first problem is the "umount" thing
Up this guys, I really would like to do this thing
Kahana82 said:
Open a command window: CMD, then get into shell:
adb shell
Once in shell, type:
umount /storage
parted /dev/block/mmcblk0
print
Click to expand...
Click to collapse
Did you do that first step?
Sent from my C2105 using XDA Free mobile app
GreyLDroid said:
Did you do that first step?
Sent from my C2105 using XDA Free mobile app
Click to expand...
Click to collapse
Did you try that with adb connected tot the phone within CWM recovery mode (not from your Android OS) ?
I've tried different ways
First of all, I have the phone with "usb debug" enabled, with my sdcard out and normally connected. If I do "adb devices" it launches daemon and show me my device connected
But when I enter the shell, if I do the same thing, devices is not showed, but I can access and do "ls" and navigate through the directories.
I can't either adb pull /dev/block/mmcblk0 mmcblk0.img, it sais that "remote object is not a file or directory", but it is.
I'm running Windows 7 SP1 with last version of Android Studio(SDK) and manually added my phone to android_winusb.inf
any idea? Thanks in advance
SoulFury said:
I've tried different ways
First of all, I have the phone with "usb debug" enabled, with my sdcard out and normally connected. If I do "adb devices" it launches daemon and show me my device connected
But when I enter the shell, if I do the same thing, devices is not showed, but I can access and do "ls" and navigate through the directories.
I can't either adb pull /dev/block/mmcblk0 mmcblk0.img, it sais that "remote object is not a file or directory", but it is.
I'm running Windows 7 SP1 with last version of Android Studio(SDK) and manually added my phone to android_winusb.inf
any idea? Thanks in advance
Click to expand...
Click to collapse
Try to navigate to the directory and then just use adb pull mmcblk0.img (without the path)
Sent from my C2105 using XDA Free mobile app
Well, something is going wrong. If I do adb devices at first, it shows my phon, but when I do adb shell, althoug I apparently have acces to my phone directories, adb devices is empty :S
SoulFury said:
Well, something is going wrong. If I do adb devices at first, it shows my phon, but when I do adb shell, althoug I apparently have acces to my phone directories, adb devices is empty :S
Click to expand...
Click to collapse
ah come on guys dont touch this if you are kinda that rookie... want to hardbrick your device?
i will explain you:
you do : adb devices
you do that ON PC
pc looks for devices and show you
then you do : adb shell
you will switch from PC to PHONE comand prompt
then you do again: adb devices
you do that ON PHONE ...
and on your phone there isnt another phone conected
Sent from my C2105 using XDA Free mobile app
Ooooook thanks. First of all, only starting to be a rookie you'll become master XDDD. Until now, I've only flashed,rooted and modded some firmware on all of my xperias since x10 mini pro, and I hope I'll learn more and more.
Next, still having the thing about the umounting of storage.I've tried with sdcard out. Even pull command(out of the shell xD) doen'ts work with dev/block/mmcblk0
SoulFury said:
Ooooook thanks. First of all, only starting to be a rookie you'll become master XDDD. Until now, I've only flashed,rooted and modded some firmware on all of my xperias since x10 mini pro, and I hope I'll learn more and more.
Next, still having the thing about the umounting of storage.I've tried with sdcard out. Even pull command(out of the shell xD) doen'ts work with dev/block/mmcblk0
Click to expand...
Click to collapse
adb devices
adb pull /dev/block/mmcblk0 c:/users/bla/mmcblk0.img
you have to do that ON PC command prompt.... dont switch to shell
Sent from my C2105 using XDA Free mobile app
That's exatcly what I do and I get always "remote object '/dev/block/mmcblk0' not a file or directory"(and I've verified that it exist)
I have a Moto G falcon and unlocked bootloader. I then installed twrp and then CM 11. I had taken pics of my childs 16th bday on the stock rom and screwed up big time.
I would like to dump the 5.5 gig partition to sd card to try and run recovery software on it to recover photos.
so far I have been given the following advice, I dont know how to implement it however.
If you don't use the phone's internal SD storage - there is still a chance you can recover the photos.
You can dump the /sdcard/ partition as a .img and use data recovery software on it.
I would make a backup of this partition asap, before attempting anything else.
To make this backup you will need a usb OTG cable and some external storage (sdcard or pen.) The .img will be around 5.5GB.
You will need root and the command is: dd if=/dev/block/platform/msm_sdcc.1/by-name/userdata of=/<external_storage>/userdata.img
Do not accidentally dump the .img onto /sdcard/ (internal storage)
After making a backup - you can explore your options.
There are undelete apps for android such as DiskDigger undelete.
Click to expand...
Click to collapse
I have my Moto G connected to PC with otg cable and a 16 gig sd card in PC and usb debugging is on. I am in fastboot
Appreciate your help. thanks
Holysmoke99 said:
I have a Moto G falcon and unlocked bootloader. I then installed twrp and then CM 11. I had taken pics of my childs 16th bday on the stock rom and screwed up big time.
I would like to dump the 5.5 gig partition to sd card to try and run recovery software on it to recover photos.
so far I have been given the following advice, I dont know how to implement it however.
I have my Moto G connected to PC with otg cable and a 16 gig sd card in PC and usb debugging is on. I am in fastboot
Appreciate your help. thanks
Click to expand...
Click to collapse
What does "I don't know how to implement it" mean, exactly?
Do you need help following the quoted instructions?
thenookieforlife3 said:
What does "I don't know how to implement it" mean, exactly?
Do you need help following the quoted instructions?
Click to expand...
Click to collapse
sadly, yes
Holysmoke99 said:
sadly, yes
Click to expand...
Click to collapse
Ah.
I'm busy with school at the moment, but I will give you in-depth instructions in a few hours.
Sound good?
thenookieforlife3 said:
Ah.
I'm busy with school at the moment, but I will give you in-depth instructions in a few hours.
Sound good?
Click to expand...
Click to collapse
absolutely!
Okay, so let's get started!
from previous post said:
If you don't use the phone's internal SD storage - there is still a
chance you can recover the photos.
You can dump the /sdcard/ partition as a .img and use data
recovery software on it.
I would make a backup of this partition asap, before attempting
anything else.
To make this backup you will need a usb OTG cable and some
external storage (sdcard). The .img will be around 5.5GB.
You will need root and the command is:
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/userdata of= <external_storage>/userdata.img
(the above is all one line)
Do not accidentally dump the .img onto /sdcard/ (internal storage)
After making a backup - you can explore your options.
Click to expand...
Click to collapse
To follow the above instructions, follow my steps:
1. Root your phone!
2. Download and install the attached terminal app.
3. Plug in your empty sdcard.
4. Open the terminal app and execute the following command:
Code:
su
5. Now, execute the command found in the quote above.
• This should create a file called userdata.img on your sdcard.
6. Eject your sdcard from your phone, plug it into your PC, and extract the userdata.img file with an archive manager (7zip, WinRAR).
7. Retrieve your photos!
Hope this helps!
thanks so much for your reply...
I am using an OTG cord. Do the same instructions apply?
Holysmoke99 said:
thanks so much for your reply...
I am using an OTG cord. Do the same instructions apply?
Click to expand...
Click to collapse
What are you using an OTG cable for?
Why do you need one?
thenookieforlife3 said:
What are you using an OTG cable for?
Why do you need one?
Click to expand...
Click to collapse
my phone doesnt have an sd slot
Holysmoke99 said:
my phone doesnt have an sd slot
Click to expand...
Click to collapse
Okay, and yes, it's the same procedure.
thenookieforlife3 said:
Okay, and yes, it's the same procedure.
Click to expand...
Click to collapse
I will report back tomorrow how this goes. thanks!
thenookieforlife3 said:
Okay, so let's get started!
To follow the above instructions, follow my steps:
1. Root your phone!
2. Download and install the attached terminal app.
3. Plug in your empty sdcard.
4. Open the terminal app and execute the following command:
Code:
su
5. Now, execute the command found in the quote above.
• This should create a file called userdata.img on your sdcard.
6. Eject your sdcard from your phone, plug it into your PC, and extract the userdata.img file with an archive manager (7zip, WinRAR).
7. Retrieve your photos!
Hope this helps!
Click to expand...
Click to collapse
do you know what to put for the red part?
dd if=/dev/block/platform/msm_sdcc.1/by-name/userdata of=/<put_correct_location_for_external_storage_here>/userdata.img
Holysmoke99 said:
do you know what to put for the red part?
dd if=/dev/block/platform/msm_sdcc.1/by-name/userdata of=/<put_correct_location_for_external_storage_here>/userdata.img
Click to expand...
Click to collapse
300TH POST! :laugh:
Yes, you put the exact directory on the USB stick you've got plugged into your OTG cable where you want to dump the .img.
thenookieforlife3 said:
300TH POST! :laugh:
Yes, you put the exact directory on the USB stick you've got plugged into your OTG cable where you want to dump the .img.
Click to expand...
Click to collapse
thanks, but how do I determine what the directory is named?
Holysmoke99 said:
thanks, but how do I determine what the directory is named?
Click to expand...
Click to collapse
You need to first be sure your USB stick is mounted on your device.
Then, you use a file explorer app to find out where the stick actually is. I don't know for sure, but try looking for a /mnt in the root of your device.
After you find where it's mounted, it's all easy from there. Just go into the stick's filesystem, and create a folder like "images".
Lastly, the directory name you put into the dd command will look something like this:
Code:
/mnt/usb/images
Please note that it may not be exactly like that.
Hey, I'm hardbricked on my tab2 (sch-i705) and so have a few others because of loading this aboot.img at http://forum.xda-developers.com/showthread.php?t=1942674
I was thinking that someone with a working bootloader could run this script:
Code:
#!/sbin/sh
mkdir -p /sdcard/Unbrick_Files/;
dd if=/dev/block/mmcblk0 of=/sdcard/Unbrick_Files/200MB.img bs=4096 count=50000;
busybox gzip /sdcard/Unbrick_Files/*;
mv /sdcard/Unbrick_Files/200MB.img.gz /sdcard/Unbrick_Files/Unbrick_IMG.gz;
chmod -R 777 /sdcard/Unbrick_Files
and post the output so we can have an unbrick image here.
Nine days have gone by and nobody has a working tab 2 of any variant? Is it possible to take a similar debrick.img and overwrite each partition with the partitions in an odin tar?
Update: Ordered a replacement motherboard so I can make one myself.
How does this solve hardbrick may I ask?
Well, the tab 2 like similar devices allows for booting from sdcard when it is partitioned the same way as the emmc, containing bootloader, SBL, etc. With this script we copy the first 200mb of the emmc to an image file. When the image file is written to sdcard the sdcard is partitioned like emmc (but not complete) so the tab boots from it but only allows entering download mode. Thus we are able to fix hardbrick caused by corrupt emmc.
I've been very busy but the replacement board came in and I installed it yesterday. So I'll have an image for y'all to test soon.
Okay, now everyone posting that they're bricked can try this...
https://drive.google.com/file/d/0B9vvBRDZ3jJFVTlVakFadF9UdHM/view?usp=sharing
Download this image and copy it to a microsd (supposed to be >8GB class 10) using dd in osx/linux or Roadkil's Disk Image in Windows http://www.roadkil.net/program.php/P12/Disk Image
If it works for you feel free to donate.
in need of help with bricked device
hi will this work for my Samsung galaxy tab 2 GT-P3110 as all it is able to do at min is show me an empty grey looking battry bar once plugged into a charger and that's it.. if so would you please help me in detail as i am new too all of this.. would be appreciated.. cheers
mudtub said:
Okay, now everyone posting that they're bricked can try this...
https://drive.google.com/file/d/0B9vvBRDZ3jJFVTlVakFadF9UdHM/view?usp=sharing
Download this image and copy it to a microsd (supposed to be >8GB class 10) using dd in osx/linux or Roadkil's Disk Image in Windows http://www.roadkil.net/program.php/P12/Disk Image
If it works for you feel free to donate.
Click to expand...
Click to collapse
Have you or anybody else used this and successfully restored an i705?
Have a hardbricked Tab 2 and am familiar with SD unbricking as Sammys are MOSTLY unbrickable. But seriously, a definitive answer here would be nice...
Last note, writing a bootable img to SD is always best done through Linux Terminal dd commands. Windows applications don't write the partition table. Roadkil only wrote the files into a folder called "image". When properly done in Linux, a windows PC won't recognize the SD card.
So any answers here please?
mudtub said:
Okay, now everyone posting that they're bricked can try this...
https://drive.google.com/file/d/0B9vvBRDZ3jJFVTlVakFadF9UdHM/view?usp=sharing
Download this image and copy it to a microsd (supposed to be >8GB class 10) using dd in osx/linux or Roadkil's Disk Image in Windows http://www.roadkil.net/program.php/P12/Disk Image
If it works for you feel free to donate.
Click to expand...
Click to collapse
I tried this method with a micro-sd 16gb class 4, used roadkil, without results, the device not turning on or going to download mode, and if i go to device settings in windows i see qloader 9008 in the com section.
Could the cause of not working be class of the sd card that it's 4 instead of 10?
Thanks in advance.
mudtub said:
Okay, now everyone posting that they're bricked can try this...
https://drive.google.com/file/d/0B9vvBRDZ3jJFVTlVakFadF9UdHM/view?usp=sharing
Download this image and copy it to a microsd (supposed to be >8GB class 10) using dd in osx/linux or Roadkil's Disk Image in Windows http://www.roadkil.net/program.php/P12/Disk Image
If it works for you feel free to donate.
Click to expand...
Click to collapse
then what? plug into charger/boot into twrp/boot into download mode?? what should i do
fhope93 said:
in need of help with bricked device
hi will this work for my Samsung galaxy tab 2 GT-P3110 as all it is able to do at min is show me an empty grey looking battry bar once plugged into a charger and that's it.. if so would you please help me in detail as i am new too all of this.. would be appreciated.. cheers
Click to expand...
Click to collapse
Even I'm getting the same problem... Do you have a solution for this?
My adoptable SD-card took a crap.
I'd like to think that I can recover the password/key (with a rooted phone), use ddrescue to make an image of the card, use the password/key to decrypt the image of the card, use fsck to fix the file-system (it's ext4, right?) then copy the repaired image back to the card and have a nice day.
Or maybe there's way to fsck the card in the phone? (after making a backup image)
Is this possible? Is there another way to un-screw a corrupted SD-card that's used as adoptable storage?
go vegan said:
My adoptable SD-card took a crap.
I'd like to think that I can recover the password/key (with a rooted phone), use ddrescue to make an image of the card, use the password/key to decrypt the image of the card, use fsck to fix the file-system (it's ext4, right?) then copy the repaired image back to the card and have a nice day.
Or maybe there's way to fsck the card in the phone? (after making a backup image)
Is this possible? Is there another way to un-screw a corrupted SD-card that's used as adoptable storage?
Click to expand...
Click to collapse
If you're trying to fix it so that it works "as-is" again, I wouldn't put too much faith in that.
You can recover the data on the sdcard by various methods, there are many methods and tools, such as these:
http://www.rescuedigitalmedia.com/retrieve-files-from-sd-card-formatted-as-internal-storage
There are more in depth and technical methods/tools also.
Once you have your data safely recovered, format the card and try replacing your data and setting up adoptable storage again the way you did originally.
Sent from my LGL84VL using Tapatalk
Using this as a guide for key recovery and data decryption - https://nelenkov.blogspot.com/2015/06/decrypting-android-m-adopted-storage.html
1- Make a backup of the card
Code:
ddrescue -n /dev/sdc bad-card.img bad-card.log
ddrescue completed in one pass with zero errors. Nice. From here, I'm working with a BACKUP of the card, NOT the card itself.
2- See what's on the card
Code:
fdisk -l bad-card.img
Output:
Code:
Disk bad-card.img: 120.3 GiB, 129116405760 bytes, 252180480 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
Device Start End Sectors Size Type
bad-card.img1 2048 34815 32768 16M unknown
bad-card.img2 34816 252180446 252145631 120.2G unknown
3- Copy the 2nd partition to a file
Code:
dd bs=512 skip=34816 if=bad-card.img of=bad-card-p2.img
* Your numbers may be different
4- Using the encryption key I found using the link, above, mount (read-only) this (2nd) copy of the card
Code:
losetup -r -f --show bad-card-fs-p2.img
cryptsetup luksOpen /dev/loop0 bad-card-fs-p2.img
dmsetup create crypt1 --table "0 252145631 crypt aes-cbc-essiv:sha256 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 0 /dev/loop0 0"
mkdir /tmp/mount1
mount -o ro -t ext4 /dev/dm-4 /tmp/mount1
* Your numbers may be different
nb, the "4" in "/dev/dm-4" can be identified by the minor device-number here:
Code:
dmsetup info crypt1
Name: crypt1
State: ACTIVE
Read Ahead: 256
Tables present: LIVE
Open count: 1
Event number: 0
Major, minor: 252, 4
Number of targets: 1
Boom! My files are there!
From here, I used dd to make an unencrypted copy (as a disk-image file) and ran fsck on it. It fixed a few things, apparently nothing catastrophic.
Yeah, recovering pictures and music and that stuff wasn't too bad (since the device is rooted and I was able to recover the encryption key) but getting back the apps and getting the phone back to the state it was in a few hours earlier is not so straightforward.
Lesson learned: Keep a backup copy of the encryption key (in a safe place) so that data can be recovered from an "adopted" SD-card even if the phone gets smashed by a rock.
Too bad there isn't a way to do a "bare metal" backup of an android.
go vegan said:
Using this as a guide for key recovery and data decryption - https://nelenkov.blogspot.com/2015/06/decrypting-android-m-adopted-storage.html
1- Make a backup of the card
Code:
ddrescue -n /dev/sdc bad-card.img bad-card.log
ddrescue completed in one pass with zero errors. Nice. From here, I'm working with a BACKUP of the card, NOT the card itself.
2- See what's on the card
Code:
fdisk -l bad-card.img
Output:
Code:
Disk bad-card.img: 120.3 GiB, 129116405760 bytes, 252180480 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
Device Start End Sectors Size Type
bad-card.img1 2048 34815 32768 16M unknown
bad-card.img2 34816 252180446 252145631 120.2G unknown
3- Copy the 2nd partition to a file
Code:
dd bs=512 skip=34816 if=bad-card.img of=bad-card-p2.img
* Your numbers may be different
4- Using the encryption key I found using the link, above, mount (read-only) this (2nd) copy of the card
Code:
losetup -r -f --show bad-card-fs-p2.img
cryptsetup luksOpen /dev/loop0 bad-card-fs-p2.img
dmsetup create crypt1 --table "0 252145631 crypt aes-cbc-essiv:sha256 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 0 /dev/loop0 0"
mkdir /tmp/mount1
mount -o ro -t ext4 /dev/dm-4 /tmp/mount1
* Your numbers may be different
nb, the "4" in "/dev/dm-4" can be identified by the minor device-number here:
Code:
dmsetup info crypt1
Name: crypt1
State: ACTIVE
Read Ahead: 256
Tables present: LIVE
Open count: 1
Event number: 0
Major, minor: 252, 4
Number of targets: 1
Boom! My files are there!
From here, I used dd to make an unencrypted copy (as a disk-image file) and ran fsck on it. It fixed a few things, apparently nothing catastrophic.
Yeah, recovering pictures and music and that stuff wasn't too bad (since the device is rooted and I was able to recover the encryption key) but getting back the apps and getting the phone back to the state it was in a few hours earlier is not so straightforward.
Lesson learned: Keep a backup copy of the encryption key (in a safe place) so that data can be recovered from an "adopted" SD-card even if the phone gets smashed by a rock.
Too bad there isn't a way to do a "bare metal" backup of an android.
Click to expand...
Click to collapse
Very nice.
Sent from my LGL84VL using Tapatalk
Same thing happened again. I knew I'd left a how-to here, so using this as a guide I fixed it much quicker, this time.
1- Power-down and remove the "corrupt" SD-card.
2- Use ddrescue to make a backup copy of the card
Code:
ddrescue -n /dev/sdg bad-card.img bad-card.log
That ran with no errors.
3- While that was backing up, I booted into TWRP and copied expand_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.key to a flash drive via OTG. That's "/data/misc/vold/expand_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.key", as per - https://nelenkov.blogspot.com/2015/06/decrypting-android-m-adopted-storage.html
4- After ddrescue was finished, I decrypted the SD-card.
Code:
blockdev --getsize /dev/sdg2
249702367
od -t x1 expand_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.key
0000000 yy yy yy yy yy yy yy yy yy yy yy yy yy yy yy yy
0000020
dmsetup create crypt1 --table "0 249702367 crypt aes-cbc-essiv:sha256 yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy 0 /dev/sdg2 0"
5- Find out what "crypt1" links to, and what it is.
Code:
file -s /dev/mapper/crypt1
/dev/mapper/crypt1: symbolic link to ../dm-5
file -s /dev/dm-5
/dev/dm-5: Linux rev 1.0 ext2 filesystem data, UUID=aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa (extents) (large files)
6- fsck /dev/dm-5.
Code:
fsck /dev/dm-5
fsck from util-linux 2.27.1
e2fsck 1.42.13 (17-May-2015)
/dev/mapper/crypt1: clean, 14314/7806976 files, 21089519/31212795 blocks (check after next mount)
7 - "Remove" the SD-card.
Code:
dmsetup remove crypt1
8- Put the card back in the Android, and it's all good.
nb - Turned out that I didn't need a copy of the card, but it's still good practice to make a backup.
go vegan said:
My adoptable SD-card took a crap.
I'd like to think that I can recover the password/key (with a rooted phone), use ddrescue to make an image of the card, use the password/key to decrypt the image of the card, use fsck to fix the file-system (it's ext4, right?) then copy the repaired image back to the card and have a nice day.
Or maybe there's way to fsck the card in the phone? (after making a backup image)
Is this possible? Is there another way to un-screw a corrupted SD-card that's used as adoptable storage?
Click to expand...
Click to collapse
You are going to big trouble if the card is not recovered.
nyckwilliams said:
You are going to big trouble if the card is not recovered.
Click to expand...
Click to collapse
Did you even read the thread? This member not only posted how they solved the issue but has had to do it twice and posted about it a second time just above the post you made.
Learn to read more than just the first few posts or first few pages of a thread.
Sent from my LGL84VL using Tapatalk
Note to self (and everyone else who finds this) to make it easier to work with image-files from SD-cards. Make use of losetup's "-P" flag to automatically create partitions.
Code:
losetup -r -f --show [B]-P[/B] bad-card.img
/dev/loop0
ls -lh /dev/loop*
brw-rw---- 1 root disk 7, 0 Aug 30 09:31 /dev/loop0
brw-rw---- 1 root disk 259, 0 Aug 30 09:31 /dev/loop0p1
brw-rw---- 1 root disk 259, 1 Aug 30 09:31 /dev/loop0p2
...
Now, the partition of interest is set up as "/dev/loop0p2" with minimum fuss.
Easy, sure and fast solution!
Hello everyone!
I'm going to give you a wonderful news!
You do not need to follow these complicated instructions that are still useful to know in case of need and thanks for this.
The solution is much easy and that's it:
Without turning off the smartphone, remove the micro SD card and reinsert it again.
That's all!
This solves your problem!
Good Android to everyone.
Android 8.1 with Lineage OS on Samsung Galaxy S5 klte and micro SD 128 GB extreme SanDisk A2 U3 V30
Future Technation said:
Without turning off the smartphone, remove the micro SD card and reinsert it again.
Click to expand...
Click to collapse
1- First, make a backup.
2- Good luck.
3- Does that work if the SD card was not unmounted/ejected properly, and the file-system is marked dirty?
go vegan said:
1- First, make a backup.
2- Good luck.
3- Does that work if the SD card was not unmounted/ejected properly, and the file-system is marked dirty?
Click to expand...
Click to collapse
Hello Vegan,
the problem mentioned is created precisely because the system has failed to mount the micro SD and identifies it as corrupt, but it is not really so.
Simply the system has not mounted it and is therefore inaccessible! (Of course, at this stage everyone takes the panic for their data :crying: ).
In my specific case the micro SD is the main memory and obviously also has all the data.
Since it is not yet mounted in the system (due to a reading error), you can not back up your data on the micro SD card.
Furthermore, since it has not yet been mounted (due to a reading error), it can be safely removed and reinserted without restarting the smartphone.
Once this is done, everything is fine.
I hope I was clear in the explanation.
Future Technation said:
Hello everyone!
I'm going to give you a wonderful news!
You do not need to follow these complicated instructions that are still useful to know in case of need and thanks for this.
The solution is much easy and that's it:
Without turning off the smartphone, remove the micro SD card and reinsert it again.
That's all!
This solves your problem!
Good Android to everyone.
Android 8.1 with Lineage OS on Samsung Galaxy S5 klte and micro SD 128 GB extreme SanDisk A2 U3 V30
Click to expand...
Click to collapse
I'm not sure this applies to the specific situation that the OP posted about.
Sent from my LGL84VL using Tapatalk
In my case, the file-system was marked "dirty" and thus could not be mounted by the OS until after it was fsck'd.
Droidriven said:
I'm not sure this applies to the specific situation that the OP posted about.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Hi Droidriven,
it's exactly the same situation, I confirm it.
---------- Post added at 12:02 PM ---------- Previous post was at 11:06 AM ----------
go vegan said:
In my case, the file-system was marked "dirty" and thus could not be mounted by the OS until after it was fsck'd.
Click to expand...
Click to collapse
Hi Vegan,
I had exactly the same problem, the filesystem was corrupt, I explained it well on my post. The micro SD works only after removal and re-insertion. There is no need for check disk. What you did was your option and choice, but in this specific case it is not necessary. You probably did not do as I described but you immediately removed the SD card for a check disk. This post can help many people. Why complicate things when the solution is so easy? Less experienced people can panic. Our job is to help and simplify the work, not to complicate it. However, I'm sure you did your best to solve your problem, but this solution has to admit that it's much easier for everyone.
Have a nice day.
Future Technation said:
Hi Droidriven,
it's exactly the same situation, I confirm it.
---------- Post added at 12:02 PM ---------- Previous post was at 11:06 AM ----------
Hi Vegan,
I had exactly the same problem, the filesystem was corrupt, I explained it well on my post. The micro SD works only after removal and re-insertion. There is no need for check disk. What you did was your option and choice, but in this specific case it is not necessary. You probably did not do as I described but you immediately removed the SD card for a check disk. This post can help many people. Why complicate things when the solution is so easy? Less experienced people can panic. Our job is to help and simplify the work, not to complicate it. However, I'm sure you did your best to solve your problem, but this solution has to admit that it's much easier for everyone.
Have a nice day.
Click to expand...
Click to collapse
Well...
You see...
I'm willing to bet that they tried that first, since it IS the first and simplest troubleshooting step for the scenario, even a noob would know to try that and they seem to be a bit more advanced than a noob. You post as if they did not try that kindergarten level troubleshooting step first, which I'm sure they probably did. But I could be wrong.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Well...
You see...
I'm willing to bet that they tried that first, since it IS the first and simplest troubleshooting step for the scenario, even a noob would know to try that and they seem to be a bit more advanced than a noob. You post as if they did not try that kindergarten level troubleshooting step first, which I'm sure they probably did. But I could be wrong.
Click to expand...
Click to collapse
Hi Droidriven,
This proves that he did not do it.
go vegan said:
In my case, the file-system was marked "dirty" and thus could not be mounted by the OS until after it was fsck'd.
Click to expand...
Click to collapse
The fear factor can always affect one's choices.
Please, review my posts well, I gave a technical and exhaustive explanation of what happened and why I did it that way.
In any case my solution is valid and working. Those who present the same problem can take advantage of this information.
Have a nice day!
Future Technation said:
Hi Droidriven,
This proves that he did not do it.
The fear factor can always affect one's choices.
Please, review my posts well, I gave a technical and exhaustive explanation of what happened and why I did it that way.
In any case my solution is valid and working. Those who present the same problem can take advantage of this information.
Have a nice day!
Click to expand...
Click to collapse
That doesn't prove that they didn't remove and reinsert the sdcard, though. That just proves that their sdcard wasn't working. Nothing in what they posted says that they didn't remove and re-insert the sdcard, you're assuming they didn't because removing and reinserting worked for you. This assumes that their sdcard was "corrupted" for the same reason that yours was and in the same way.
I'm not disagreeing that your method worked for you, I'm just saying that your scenario and their scenario are not necessarily the same.
Sent from my LGL84VL using Tapatalk
Droidriven said:
That doesn't prove that they didn't remove and reinsert the sdcard, though. That just proves that their sdcard wasn't working. Nothing in what they posted says that they didn't remove and re-insert the sdcard, you're assuming they didn't because removing and reinserting worked for you. This assumes that their sdcard was "corrupted" for the same reason that yours was and in the same way.
I'm not disagreeing that your method worked for you, I'm just saying that your scenario and their scenario are not necessarily the same.
Click to expand...
Click to collapse
Excuse me but how old are you? You are a child? This would explain all these controversies. You always want to have the reason anyway. Even if you were an adult, you behave like a child! I have no time to waste with you, but willingly with those who really need to solve the same problem! Those who are truly experts will appreciate this solution. You are spamming here. I will not answer you again. Goodbye!
--------------------------------------------------------------------------------
Hi Go Vegan,
I want to apologize with you for this little discussion, because I started quoting you. My intent is always to share something useful for others. Thank you for your intervention, because obviously if my first approach to this problem does not work for someone, yours becomes indispensable, as obviously it has already been certainly for many others.
This words are for everyone: "We must learn to really listen to others before answering".
Have a nice day!
Might also depend on the phone, the ROM, the version, etc. Might also depend on whether the card is "internal" or "external" storage.
Future Technation said:
Excuse me but how old are you? You are a child? This would explain all these controversies. You always want to have the reason anyway. Even if you were an adult, you behave like a child! I have no time to waste with you, but willingly with those who really need to solve the same problem! Those who are truly experts will appreciate this solution. You are spamming here. I will not answer you again. Goodbye!
--------------------------------------------------------------------------------
Hi Go Vegan,
I want to apologize with you for this little discussion, because I started quoting you. My intent is always to share something useful for others. Thank you for your intervention, because obviously if my first approach to this problem does not work for someone, yours becomes indispensable, as obviously it has already been certainly for many others.
This words are for everyone: "We must learn to really listen to others before answering".
Have a nice day!
Click to expand...
Click to collapse
Actually, with the way you are defending yourself when I'm just telling you the truth, that makes you appear as the child.
You have only 5 posts here and just joined a few days ago. This tells me that you probably haven't dealt with android devices enough to know there can be many different causes for the exact same issue, even on two identical devices that show the same symptoms and that what works in "this" situation on "that" device, doesn't always work the same for another device with the exact same issues.
I was just saying that there are many different details that make all the difference in the world. It's obvious, from everything that you have posted here, that you are unaware of those facts. I was just trying to tell you that you can't be so certain that what you posted is the fix for every user and every device that has this issue. Dont take it so personal.
Sent from my LGL84VL using Tapatalk