Database Develop

Amazon Fire 5th Gen. OS Trouble

Problem: I believe my Fire OS was accidentally deleted in the process described by the video "How to install CM12 1 on the Amazon Fire 5th gen Tablet" by Rootjunky.
I've hit a roadblock in getting my new Kindle Fire 5th Gen. up and running with Cyanogenmod. I will lay a few things out: how I got to this point and what I've tried in attempt to resolve my issue.
After I had TWRP running on my tablet I performed the back-up step, the wipe step and began the installation. During the installation TWRP reported an exception declaring that I did not have enough space to install "open_gapps-arm-5.1-stock-20151122.zip". The only difference between my setup and Rootjunky's was that I had not copied "cm-12.1-20151116-UNOFFICIAL-ford.zip", "open_gapps-arm-5.1-stock-20151122" and "SuperSU-v2.46" to my external SD card but to my internal storage. I decided that this may have been the issue and REMOVED my SD card from my tablet, copied the files to the SD card from my PC and then reinserted the card. I tried to select the .ZIP files in TWRP but it failed to recognize that the card had been reinserted. At this point I selected for the device to reboot (in hopes of it recognizing the card) and all I was met with was the "Amazon" splash screen and no continuing boot load.
To remedy this I have tried:
• To flash via Fastboot but I do not have an unlocked boot loader. When I try to flash it says "not allowed" and if I try to unlock the boot loader using either "fastboot oem unlock" or "fastboot flashing unlock" I get no results. The device is recognized, by the way.
• To upload the original Fire OS from Amazon's website and load it through the adb sideloader. This uploads successfully but the boot is stuck at the animated "Fire" splash screen.
• Attempted to perform a factory reset by using the Amazon System Recovery menu.
• Searched for over 5 hours tonight trying to find a solution.
Overall I believe the question is how do I get my device booted back up so I can restart this process and give it another shot?
Thank you all for the help in advance.
-Skye

Fixed
I decided to try to boot once more before retiring for the night and it just magically began to work.
The "Fire" splash animation displayed as the device began to install system updates.
I would say what worked was installing the Amazon Fire OS via the side loader.
However, I am new to modifying mobile technology and would like to ask a few questions for anyone to answer who should come across this thread.
• What is stored truly as ROM within the device? In other words, is it possible for me to delete enough data that the device would truly become bricked?
• Is it possible to perform a clean wipe and install from an empty storage device? I have dealt with plenty of desktop operating systems and find that a fresh hard drive is the best way to go when introducing a new Linux flavor to a growing build.
I am aware that, with root privileges and 3rd party utilities, that I could clean the system myself. However, it is easier to perform a full wipe and start from scratch.
Thank you all again.
-Skye

CieloLumine said:
I decided to try to boot once more before retiring for the night and it just magically began to work.
The "Fire" splash animation displayed as the device began to install system updates.
I would say what worked was installing the Amazon Fire OS via the side loader.
However, I am new to modifying mobile technology and would like to ask a few questions for anyone to answer who should come across this thread.
• What is stored truly as ROM within the device? In other words, is it possible for me to delete enough data that the device would truly become bricked?
• Is it possible to perform a clean wipe and install from an empty storage device? I have dealt with plenty of desktop operating systems and find that a fresh hard drive is the best way to go when introducing a new Linux flavor to a growing build.
I am aware that, with root privileges and 3rd party utilities, that I could clean the system myself. However, it is easier to perform a full wipe and start from scratch.
Thank you all again.
-Skye
Click to expand...
Click to collapse
The locked bootloader should prevent the device from getting bricked.
There are several partitions in an android device the some of them are: bootloader, recovery, system, data, cache.
System is were the rom is installed, data is your apps, settings and updated system apps.
When you install a new rom, you need to do a factory reset, which wipes data and cache.
You can wipe system, but it is usually wiped as part of the installing rom process.
Data isn't usually wiped by the rom installer, in case you are installing as an update.

Thanks
Thank you for the reply!
-Skye

Help for others
For anybody who finds themselves in a situation where you have lost your OS and you have only access to the ADB and fastboot...
You can still reboot TWRP by holding the power + volume down buttons on to power up and access Amazon's recovery mode. In recovery mode select "boot from bootloader" to enable fastboot. Connect your device to your PC and ensure you have your device driver installed and enabled. From here, use the Android SDK's fastboot.exe to send the command "fastboot boot <twrp image>". This will boot TWRP for you and enable you to give the process another go without having to reinstall the Fire OS.
You may find all commands used in these processes by referring to the scripting code of Rootjunky's batch file that helps to automate this process.
-Skye

CieloLumine said:
For anybody who finds themselves in a situation where you have lost your OS and you have only access to the ADB and fastboot...
You can still reboot TWRP by holding the power + volume down buttons on to power up and access Amazon's recovery mode. In recovery mode select "boot from bootloader" to enable fastboot. Connect your device to your PC and ensure you have your device driver installed and enabled. From here, use the Android SDK's fastboot.exe to send the command "fastboot boot <twrp image>". This will boot TWRP for you and enable you to give the process another go without having to reinstall the Fire OS.
You may find all commands used in these processes by referring to the scripting code of Rootjunky's batch file that helps to automate this process.
-Skye
Click to expand...
Click to collapse
Unbrick/Restore Stock 2015 Amazon Fire (KFFOWI/Ford) with custom recovery
Sent from my KFFOWI using Tapatalk

I think this is the one advantage of a locked boot loader. It's kinda hard to hard brick. Recovery and kernel remains intact too.

[Q] TWRP 2.8.7.1 - Cannot see files under /sdcard

Hi guys, I've been using TWRP for a long time, but this one is a bit of a head-scratcher for me. I'm running stock Android MMB29S on my N6, unlocked bootloader, and unrooted. I decided to install TWRP 2.8.7.1 and then root it with Beta supersu 2.66. The fastboot flashing of TWRP went fine the first time, and I opted to leave TWRP read-only. But I didn't install supersu right afterwards. Rather, I rebooted into system first, and downloaded supersu. When I attempted to reboot into recovery again to flash supersu, I'm finding out that stock recovery has overwritten TWRP. Ok, no problem, I re-flashed TWRP, but this time I allowed it to modify the system (instead of read-only). Now, I'm unable to see anything under /sdcard or any of the other folders when I go to flash the zip. Under the "Mount" Menu, I see that only "cache" is checked. Didn't want to mess with anything there.
Rebooting into system now gives me the "Your device is corrupted..." spiel, which I'm not concerned about, but I really do need to be able to see files in TWRP. Would re-installing TWRP be an option or even a different version of it?

mount system. if its still empty after that, use twrp to locate the right place in the filesystem. yes, like a file explorer app twrp can act

The solution to my problem was actually as simple as just removing the lockscreen passcode. I was wondering why TWRP was asking for that in the first place. Once I removed the lockscreen PIN and went back into TWRP I was able to see all the files. Happily rooted now. :good:

(Guide) Get TWRP Working with Data Access on Stock [UPDATED]

Thanks to @seadersn and @SGCMarkus, Markus's new TWRP makes things extremely simple now.
What you need:​SGCMarkus's TWRP
fstab.judypn with forceencrypt set to encryptable.
magisk
and the .magisk file​
Instructions:​
1. Follow the instructions to boot and install TWRP on SGCMarkus's TWRP thread
2. While you're still in TWRP, mount vendor and push the fstab.judypn with:
Code:
adb push path/to/fstab.judypn /vendor/etc
3. Format data via TWRP.
4. Push the .magisk to /data (For dm-verity reasons. It will restore the fstab.judypn with forceencrypt enabled) with:
Code:
adb push path/to/.magisk /data
5. Flash Magisk.
You're done! No bootloops this time. XD

i want to try this at some point. When i did before, the screen was black. Thanks for the guide!

I need to get US pie on my device but will be doing this

i got some issues..
i cant mount system_root and i saw there is no /system_root/system/priv-app folder... so i took modified LGSettings.apk to sd card and i put it to /system/system/priv-app/LGSettings... then i format userdata in fastboot,i got twrp loop.....

dreamss29 said:
i got some issues..
i cant mount system_root and i saw there is no /system_root/system/priv-app folder... so i took modified LGSettings.apk to sd card and i put it to /system/system/priv-app/LGSettings... then i format userdata in fastboot,i got twrp loop.....
Click to expand...
Click to collapse
Flash the magiskpatched boot img included in the files

I just had my bootloader unlocked. I am trying to install TWRP, but if I flash stockpiemagisk.img or TWRP-judypn-2019-07-01.img then use the buttons to choose a factory reset I just get bootloops. I select yes both times, just like normal and it loops until going to a fastboot screen. I can then flash the original magisk_patched.img I got from the guy who unlocked my bl, but no TWRP. Even he wasn't sure why this is happening. Any ideas anyone?
Also, in case its related, I lost download mode and can't get that back even by flashing an original backup of laf_b or the lgup compatible laf. I had download mode and flashed Pie before the bl unlock...
Edit: I got download mode back. Turns out when he was unlocking the bootloader he flashed abl_b incorrectly. Once I flashed it correctly DL mode works... Now for TWRP...
NVM.... found the problem...

I have an issue. After clearing the userdata procedure, this attached images is what I get. It's a reddish boot-up screen. The Active Slot also defaulted to B (as opposed to A). I have a fastboot-loop. I am wondering where I went wrong. I completed a successful procedure on another device hours ago. LGUP does not function as well. The phone defaults to Fastboot.

I am able to get to TWRP but the fastboot-loop has changed. The image attached is what I get. I suppose in my attempt to remedy, the wrong Laf files have been flashed. It's V405UA20a

Hello mister
Actually is it possible to flash this stockpie.img on a V406EBW ?
Regards
Fred

avaie said:
I have an issue. After clearing the userdata procedure, this attached images is what I get. It's a reddish boot-up screen. The Active Slot also defaulted to B (as opposed to A). I have a fastboot-loop. I am wondering where I went wrong. I completed a successful procedure on another device hours ago. LGUP does not function as well. The phone defaults to Fastboot.
Click to expand...
Click to collapse
I have exactly the situation you described (fastboot loop + pink letters screen when I try to get into DL mode). If you've managed to rectify this, can you please give me directions. Thanks.

crubbish said:
I have exactly the situation you described (fastboot loop + pink letters screen when I try to get into DL mode). If you've managed to rectify this, can you please give me directions. Thanks.
Click to expand...
Click to collapse
Hi - I eventually lost root and the system factory-reset after an attempt to boot into TWRP. I have scheduled to have VLAD reflash the entire phone. My bootloader is unlocked though but don't think much can be done. There might be other variables that might be affected.
If there is a guide to using Octoplus, it will be appreciated. It also seems telegram is the new medium for development.

avaie said:
I have scheduled to have VLAD reflash the entire phone. .
Click to expand...
Click to collapse
That's what I plan to do as well. Thanks for responding!

crubbish said:
That's what I plan to do as well. Thanks for responding!
Click to expand...
Click to collapse
All the best.

will try out to follow up this info

When I follow step 3 "Format data via TWRP", at the end of the format it says:
"Updating partition details...
...done
Full SELinux support is present.
WTP Enabled
Formatting Data using mke2fs...
Done.
You may need to reboot recovery to be able to use /
data again.
Updating partition details...
...done
UNABLE TO MOUNT STORAGE, DECRYPTION NEEDED FIRST"
I don't think that's good... Or is it?

Please Clarify/Help
I have managed to get TWRP installed and working but did not notice to do this. I went ahead and used Android already only to find that I need to do this.
I have booted into TWRP but cannot select vendor to mount it. Everything except system and vendor (and USB-OTG because there is not attached) will let me check them. But not vendor.
Do I have to go all the way back and re-install TWRP and to this before I do ANYTHING else? Do I have to do this while I am still in TWRP loaded from the image on my PC?
I realize this will loose all I have done within Android and that is the price I pay for not reading in detail. But I want to make sure this is the last time.
Thanks!

Not What I Expected - Decryption Failed!
I went ahead and re-installed TWRP from fastboot per the Markus thread After rebooting back into TWRP I then followed instructions in the 1st post here.
I could not mount vendor but I saw messages saying it was busy. So I assumed it was not unmounted and went ahead with the push to /vendor/etc. It reported successful from adb. And in TWRP file manager I can see a file named /vendor/etc and in the terminal I can cat its contents which look like what I see on my PC.
I then wiped the /data only using advanced wipe and it used makefs, not format.
I then pushed .magisk to /data and it too reported successful from adb.
I then flashed magisk and that seemed successful as well. Inside to TWRP's file manager, I was able to see the .magisk and various folders under /data. This seemed promising enough.
I finally rebooted to system and got shown what is in the attached screenshot. At that point, I had no option but to agree to the reset. When I touched that button, I was returned to TWRP. So I powered off from TWRP and tried to restart the phone. Once again I get the same decryption unsuccessful.
So I seem to be in a TWRP loop. How to proceed? Thanks

whitedavidp said:
I went ahead and re-installed TWRP from fastboot per the Markus thread After rebooting back into TWRP I then followed instructions in the 1st post here.
I could not mount vendor but I saw messages saying it was busy. So I assumed it was not unmounted and went ahead with the push to /vendor/etc. It reported successful from adb. And in TWRP file manager I can see a file named /vendor/etc and in the terminal I can cat its contents which look like what I see on my PC.
I then wiped the /data only using advanced wipe and it used makefs, not format.
I then pushed .magisk to /data and it too reported successful from adb.
I then flashed magisk and that seemed successful as well. Inside to TWRP's file manager, I was able to see the .magisk and various folders under /data. This seemed promising enough.
I finally rebooted to system and got shown what is in the attached screenshot. At that point, I had no option but to agree to the reset. When I touched that button, I was returned to TWRP. So I powered off from TWRP and tried to restart the phone. Once again I get the same decryption unsuccessful.
So I seem to be in a TWRP loop. How to proceed? Thanks
Click to expand...
Click to collapse
Well, as they say, if at first... I went through the steps here again. I made sure I hit the format button instead of wipe. And I made triple sure that everything was where it seemed to need to be and looked right. When I finally rebooted to system, I am now in Android setup as expected. To see if there is still encryption (ie, TWRP can see and backup /data) remains to be seen. Cheers

whitedavidp said:
Well, as they say, if at first... I went through the steps here again. I made sure I hit the format button instead of wipe. And I made triple sure that everything was where it seemed to need to be and looked right. When I finally rebooted to system, I am now in Android setup as expected. To see if there is still encryption (ie, TWRP can see and backup /data) remains to be seen. Cheers
Click to expand...
Click to collapse
Sadly, once finished with a minimal Android setup I went back into TWRP and /data shows nothing. In backing up, it shows /data as 0 bytes. So I presume this means I am still encrypted. Is there no way out of this hell? Thanks

whitedavidp said:
Sadly, once finished with a minimal Android setup I went back into TWRP and /data shows nothing. In backing up, it shows /data as 0 bytes. So I presume this means I am still encrypted. Is there no way out of this hell? Thanks
Click to expand...
Click to collapse
Here's the thing I would try. Load up LGUP and reload a stock kdz. Make sure that before you begin futzing with the phone, you are booting from Slot A.
Then retrace all the steps carefully. And don't set up anything on the phone until you have reached nirvana (bootloader unlocked, unencrypted, Magisk installed).
You'll get there.
[NG]Owner

Advanced advice for internal storage recovery after attempted flash to LineageOS 17

Hi everyone. Got a puzzle for you forensic data recovery guys out there. I am a fool having a bad day today. For the first time in 10 years of screwing with Android, I backed up my ROM with twrp and also backed up my sms and calls, but then managed to somehow forget to copy those files off the internal storage before trying to flash my phone to LineageOS and botching the internal storage. Here is what happened.
0) Before state: Rooted (I think) and for sure running OxygenOS 5.0.3, flashed via TWRP. TWRP version 3.2.1-0. 128 GB OnePlus 3T
1) Backed up System, data, etc to backup on internal storage via TWRP. Booted into OS and backed up SMS and calls to .xml file.
2) Wiped data, system, cache and dalvik/art cache.
3) Downloaded LineageOS w/ microG via zip in TWRP and attempted to install. Received error that I needed to update the modem to at least 9.0.3.
4) Mounted storage from TWRP and copied in Stable9.0.3+Firmware+Modem_OnePlus+3T.zip. Ran the install and was successful.
5) Installed lineage-17.1-20200826-microG-oneplus3.zip via TWRP. Left prompt to install TWRP checked and booted into OS.
6) Upon boot, saw the message: "Decryption unsuccessful" The password that you entered is correct but unfortunately your data is corrupt.
7) Rebooted back into TWRP to mount storage. Could not get anything to mount because it would not accept my decrypt passcode.
8) Figured TWRP bug, flashed twrp-3.4.0-0-oneplus3.img via fastboot. Could decrypt now with passcode but all storage read 0MB
9) Flashed modem back to OnePlus3T_5.0.3-25-05-18-FIRMWARE-flashable.zip via adb sideload method which is what I assume I was running before since that was the OS version. Rebooted
10) Booted back into TWRP, discovered I still couldn't see files. Downgraded TWRP back to 3.2.1-0 via fastboot.
11) Unable to decrypt from TWRP or even install zips. No change at any point in the OS. Flashed TWRP back to 3.4.0.0.
12) Ran adb shell twrp decrypt XXXXXX (where XXXXXX is my pin) which gave me this message:
Attempting to decrypt data partition or user data via command line.
(then it returned to shell so I assume it worked)
13) Ran an ADB pull command (adb pull /dev/block/dm-0 backup.img). There is obviously something there because it downloaded 111 GB worth of .img file (which I'm 99% certain was the amount of space I had used on the phone). Tried to open the .img file with multiple EXT4 programs and they all said the file/partition was corrupt.
14) Tried to wipe data via TWRP. Failed to wipe because it couldn't be mounted. Followed this:
https://************/how-to-fix-twrp-unable-to-mount-storage-internal-storage-0mb/
15) Ended up with MTP mount of 101 GB free space. Everything seems to be lost on the phone at present. No programs I use to recover the data off the MTP mount (just doing a raw file scrape) can see it as a OnePlus in Windows.
After finding a better guide on XDA, it sounds like this is a known issue that happens when you go from 5.0.x to 9.x on this phone where your encryption breaks and you lose all files. Unfortunately I saw that about 15 minutes after step 14...
My next thoughts would be to:
a) downgrade everything (ROM, firmware, etc) and then try to push the 111 GB .img file back to the phone via ADB, then flash a stock OnePlus 5.0.3 ROM over it to see if I could get the internal storage to mount again. Don't even need to boot into the OS--just to get the internal storage mounted again through TWRP.
--OR--
b) convert the .img file to a .raw and then possibly a .vhd and use Recuva or something to scan the image of the phone and see if I can find those .xml files and maybe a twrp backup if I'm lucky. Although if the entire .img contents is still encrypted and not actually just a corrupt android filesystem, I think I am hosed on this option.
I would prefer option a) but I didn't know if anyone had any insight on this. I thought maybe there would be a way for me to get into the filesystem via ADB maybe and clear out some botched encryption cache or keystore/etc in order to get it to mount again. I'm also not sure if you're able to downgrade the firmware or modem either from 9 to 5 (even though I never got errors on downgrade). Thoughts? Am I just royally hosed?

Tried option b. Nothing but garbage. I made a backup of the .img file this time... so still would be willing to try option a) unless anyone thinks that this is impossible.
Edit: yep... may be too late... https://forum.xda-developers.com/on...-9-0-3-5-0-8-firmware-barrier-t3941164/page18

To my knowledge the data partitions content is unrecoverable lost after the reboot from 5) to 6). The img contains the messed up (and still encrypted) dm0 container but without the enctyption footer which is "outside" the dm0 container in sda15 (aka userdata) partition. To decrypt the img you are missing the device dependent key (an encrypzed partition can be decrypted only on the device the enctyption has been done on) as well as the encryption footer (which is messed up after the reboot).
Format data (not only wipe!) and start over.

Thanks for the reply. That makes sense and is what I was afraid of.
I wonder if it would be possible to regenerate the crypto footer by doing something like this to get the HMAC keys and then flashing a rom to recreate the cryptofooter and then editing the key values to reflect the old cryptofooter values based on the KeyMaster extraction via this exploit.
http://bits-please.blogspot.com/2016/06/extracting-qualcomms-keymaster-keys.html?m=1
It might depend on how much of the cryptofooter is left and whether or not 5.0.3 is vulnerable to these CVEs...
I’m not sure if I know enough about the KeyMaster structure to know how to rebuild it even if I were able to retrieve the HMAC keys.
I also know TWRP now supports EDL so perhaps there is something with a Qualcomm tool I could yse to assist.
Obviously this would mean security issues for everyone on these older builds if I am able to regenerate the crypto footer.
Are you aware of adb commands or likewise that I could run to survey the KeyMaster damage?

As stated: to my knowledge the data is lost after the first reboot with the 9.0.x bootloader.
If you search the official los thread (don't remember if 17 or 16) you'll find some detaled postings on restoring the keys after updating the bl from 5.0.x to 9.0.x. The user, who has examined that has failed, but perhaps it helps to shine some light on your questions.

[Q] bootloop after insufficient space rooted

I have rooted my m10g using magics via twrp and also applied the "no-dm-verify" patch but I didn't notice about the "forced data encryption" patcher here so that's reason why I didn't patch it at this point! anyway the data section was mounting without any problems but after I reboot recovery I was getting error In mounting the data section I just ignore it and I was able to boot into system normally but after some days exactly after "insufficient space" I just rebooted for some reasons and after that the device won't boot anymore / stucked at bootloop...!
I was able to see the home screen/touch wiz about 4 seconds and after that it's reboots again and again (In this point I tried to delete unwanted files quickly but there's no luck).
Things I have tried:
- flashed an recovery.img extracted from combination firmware and tried the "lacking storage booting" an option from stock recovery menu the device started in safe mode (It's says something like this: please bacup your stuff and then perform factory reset) but it's still won't boot (bootloop).
- twrp decrypt (I set no password there but I just tried In hope of chance) btw twrp never asked before to decrypt my data or to enter any password.
- I did twrp backup to my ext-sd and decompiled the boot.img to see what can I do (but after magics's patch I can do nothing).
- Pulled full userdata (mmcblk0p26) section also the emmc (mmcblk0) and tried to mount via linux reader windows tool / opening via 7zip but still can't access the userdata section. also tried to open the dumped userdata via hex editor but still can't see anything(looks like encrypted).
Things I want to try next:
- Format the data section after that try to restore the dumped userdata section via dd command.
- Enable usb debug at boot time and try to adb shell stop then pull all important data from the device.
- Inject custom script in stock_recovery.img to copy all internal files to the externel-sdcard (or even delete some huge files that I'm pretty sure of their path).
Notes / just to be clear:
* Flashing the stock kernel will encrypt the userdata section and the bootloop will stop but I'll lose all my data (I know that so I was just switching from the stock recovery to twrp).
* I could just perform a format data from the recovery menu / twrp or just flash the stock firmware to fix the booting problem but first I need to all my files get back.
Looking for any help in things that I want to try next.

Finally after a lot of tries I have solved my problem...!
How?
Short answer: ClassyKitchen
Long answer:
I just started creating my first rom In ClassyKitchen and I just enabled adb and removed dm-vertify via the kitchen and after the rom has prepared I just flashed through TWRP after I reboot the phone wasn't able to boot (stucked at first samsung logo) switched the device to download mode and I flashed system only using odin... after that phone started with setup wizard! and it's was still in safe mode (the backup message was still showing also) anyway I completed the setup wizard then check the home screen and apks I have installed wasn't there...!!! I opened "My Files" and finally I was able to see my files again!
I just copied all my internal sdcard to my external sdcard...!
After the copy ends I tried to exit safe mode to get my installed apks/contacts again so I just rebooted the phone to exit from the safe mode! But after the reboot "custom binary flashed bla bla".
I flashed stock "boot.img" and "recovery.img" using odin But as I said in the first post data encryption was there...!!!
Anyway I flashed full stock firmware after that I unlocked my OEM and flashed TWRP again and I restored the emmc dump using dd after restore completed rebooted the phone and it's back to it's state...!
this time I just flashed the patched boot.img (ClassyKitchen) and after the reboot phone started normally with setup wizard as said above! Connected to wifi unlocked my OEM and I was trying to get out of safe mode I rebooted and rebooted and power off but I wasn't able to disable the safe mode...!!!
I tried to root using magics but it's failed (the boot was patched by bla unsupported something like that) also the data section was still unmount able! In the TWRP
Anyway I just stopped at this point! Because I have reach my point (Getting back my sdcard data).
Notes!:
* All thanks goes to the author of ClassyKitchen.
* TWRP I was using found here.
* Odin I have used found here.
* I was using the same firmware version (PDA) installed in my phone.
* I have unlocked my OEM using this method the first time I have used it's taked from me only 3 days!.
* The idea of taking full encrypted emmc backup was by this post (I was getting some error messages so I just used "dd if=/dev/block/mmcblk0 of=/your_external-sd/mmcblk0.img" In case of "no space left error" format your externel-sdcard to ext4 and try again).
Sorry for my bad English x).