So I accidentally deleted my cache partition of my Kindle HD 6 in fastboot. What a dork!
Code:
C:\kindle>fastboot update
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
C:\kindle>fastboot erase cache
erasing 'cache'...
OKAY [ 0.086s]
finished. total time: 0.086s
C:\kindle>fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'unknown'.
FAILED ()
finished. total time: 0.022s
C:\kindle>fastboot reboot
rebooting...
finished. total time: 0.015s
C:\kindle>fastboot reboot
^Was the command I entered, and then I rebooted... Now my Kindle is just a happy paper weight that is forever booting up. Any help? I have a factory flash cable coming but I'm unsure how to recreate the cache partition. And I did attempt to, it just said it can't format an unknown filesystem.
Thank you for the help and God bless!
If I could get a dd .bin file of the cache partition that may work, then I could flash the bin back to cache with fastboot. I need some help from the community on this one.
Could I get someone with a HD6 to adb shell into their device and then
cat /proc/mounts
Then find the cache partition (from cat /proc/mounts) and copy the cache in ADB shell on the device:
dd if=/dev/block/*the cache block partition goes here* of=/sdcard/cache.img
Then upload the cache.img file to me on dropbox. Thank YOU!
Yeah, permission denied.
sorry,
miniletsmotor said:
If I could get a dd .bin file of the cache partition that may work, then I could flash the bin back to cache with fastboot. I need some help from the community on this one.
Could I get someone with a HD6 to adb shell into their device and then
cat /proc/mounts
Then find the cache partition (from cat /proc/mounts) and copy the cache in ADB shell on the device:
dd if=/dev/block/*the cache block partition goes here* of=/sdcard/cache.img
Then upload the cache.img file to me on dropbox. Thank YOU!
Click to expand...
Click to collapse
Related
Getting frustrated with the likes of:
$ fastboot flash tombstones tombstones.img.ext4
sending 'tombstones' (114688 KB)...
OKAY [ 28.674s]
writing 'tombstones'...
FAILED (remote: size too large)
finished. total time: 28.679s
I was wondering if in all failed attempts to manually make space for such using:
$ fastboot erase system/cache/data/etc.,
I wouldn't be better off doing a:
$ fastboot oem format ?!?
Your mediapad bricked now.
You need linux-pc & try to use "dd" command for restore all partitions of your pad.
I can't format my device I enter recovery --> advanced wipe check all things and when he comes to wiping data he restart. Is memory dead ? I still have warranty, but custom recovery is on it, and custom ROM, what to do ?
EDIT:
I tried to wipe one by one(internal storage, system, cache, dalvik, and last data) and he only restarts on data when data is trying to be wiped.
Thermaltake868 said:
I can't format my device I enter recovery --> advanced wipe check all things and when he comes to wiping data he restart. Is memory dead ? I still have warranty, but custom recovery is on it, and custom ROM, what to do ?
EDIT:
I tried to wipe one by one(internal storage, system, cache, dalvik, and last data) and he only restarts on data when data is trying to be wiped.
Click to expand...
Click to collapse
reboot into bootloader, and type the following:
fastboot format system
fastboot format userdata
fastboot erase chace
this should make life easier
fastboot format system give me a bunch of commands, same as userdata. Only erase cache did the thing.
I tried to enter fastboot erase data, and he gave me this:
erasing 'data'...
FAILED (remote: not allowed)
finished. total time: 0.005s
Click to expand...
Click to collapse
these are commands that he gave me :
C:\fastb>fastboot format system
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\fastb>fastboot format userdata
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
Click to expand...
Click to collapse
If I'm not wrong this works only if you are S-OFF I am S-ON
Thermaltake868 said:
fastboot format system give me a bunch of commands, same as userdata. Only erase cache did the thing.
I tried to enter fastboot erase data, and he gave me this:
these are commands that he gave me :
If I'm not wrong this works only if you are S-OFF I am S-ON
Click to expand...
Click to collapse
hmm yeah, you are right, sorry been used to my Nexus 5
I relock the phone now and trying to install stock RUU currently my image version is 2.18.401.2 and RUU is 1.17.401.1 will that work ? I mean did anyone try this already ?
There is still no android 4.2.2 RUU for one x +
Thermaltake868 said:
I relock the phone now and trying to install stock RUU currently my image version is 2.18.401.2 and RUU is 1.17.401.1 will that work ? I mean did anyone try this already ?
There is still no android 4.2.2 RUU for one x +
Click to expand...
Click to collapse
What is ur hboot version.......
if it is higher 1.35 it wont work.......
[email protected] said:
What is ur hboot version.......
if it is higher 1.35 it wont work.......
Click to expand...
Click to collapse
It's 1.72. Then how am I supposed to return my phone to stock I mean it's my only hope, I really don't know what else to do.
Thermaltake868 said:
It's 1.72 how am I supposed to return my phone to stock I mean it's my only hope. I really don't know what else to do.
Click to expand...
Click to collapse
I exactly had the same issue with my HOX+.......
I flashed TWRP formatted Internal SDCARD itself to get it working...
But Can u try these commands from fastboot
Code:
fastboot erase userdata
fastboot erase system
fastboot erase cache
reboot into ur recovery
try installing the ROM.........
[email protected] said:
I exactly had the same issue with my HOX+.......
I flashed TWRP formatted Internal SDCARD itself to get it working...
But Can u try these commands from fastboot
Code:
fastboot erase userdata
fastboot erase system
fastboot erase cache
reboot into ur recovery
try installing the ROM.........
Click to expand...
Click to collapse
Read up I already try that, can't use fastboot erase system or data, only erase cache works. I was at TWRP trying to wipe all but can't when trying to wipe data phone restarts. I successfully erase internal storage, system, cache and dalvik in TWRP.
Thermaltake868 said:
Read up I already try that, can't use fastboot erase system or data, only erase cache works. I was at TWRP trying to wipe all but can't when trying to wipe data phone restarts. I successfully erase internal storage, system, cache and dalvik in TWRP.
Click to expand...
Click to collapse
Deleted
FIXED:
By Installing cwm recovery, and in cwm he manage to wipe all, and I return to TWRP and did the same thing there, now it's all working again, something was messed up, don't know exactly what, but it's gone now.
This is a general users guide to unbrick your Transformer tablet.
This guide will help you if your Asus tablet will only boot into recovery
and the command
Code:
adb reboot-bootloader
does not work to get you booted back to bootloader screen ..
If the above command works then skip to the first fastboot command ..
WHAT YOU NEED
An Asus tablet that will only boot into recovery …
Woking adb and fastboot on your PC
Windows drivers (if using Windows)
A fully charged tablet
Asus data cable
Stock firmware blob (from Asus's web site, make sure you get the right one)
_that's bootit.ko (unzipped and placed with fastboot.exe)
Downloads
Asus Stock firmware---MAKE SURE YOU GET THE CORRECT SKU FOR YOUR TRANSFORMER TABLET
click me
_that's bootit.ko----click me
INSTRUCTIONS
Extract your stock firmware in your downloads folder twice...You will see a blob file rename it boot.blob and move it to the same folder as your fastboot.exe or if in linux to your home folder
Unzip the bootit.ko and place it wth the above blob file.
Let start with this command to make sure that your PC can see your table as an ADB device in recovery
Code:
adb devices
OUTPUT
Code:
[email protected] ~ $ adb devices
List of devices attached
015c7d7a445c260c recovery
Then lets push the bootit.ko to the root of the device like this
Code:
adb push bootit.ko /
OUTPUT
Code:
[email protected] ~ $ adb push bootit.ko /
673 KB/s (27690 bytes in 0.040s)
Then lets insmod this .ko file
Code:
adb shell insmod /bootit.ko
This should reboot the tablet into the bootloader menu, lets verifiy.
Once in the bootloader screen lets make sure your PC can see the device in fastboot.
Code:
fastboot devices
OUTPUT
Code:
[email protected] ~ $ fastboot devices
015c7d7a445c260c fastboot
So now its time to erase the misc & cache partitions, as that is most likely the partitions that is making it boot to recovery...
Code:
fastboot erase misc
OUTPUT
Code:
[email protected] ~ $ fastboot erase misc
erasing 'misc'...
OKAY [ 1.021s]
finished. total time: 1.021s
Code:
fastboot erase cache
OUTPUT
Code:
[email protected] ~ $ fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 2.096s]
finished. total time: 2.096s
Once these two command run with OKAY as the OUTPUT .
It is time to make sure we can reboot into the bootloader with the hardware buttons
So from where you are at in the bootloader screen use the VOL DOWN & POWER buttons to boot the tab back into the bootloader screen ..
Run these command in fastboot in this order
The next command is to just verify your computer can see your device
Code:
fastboot devices
OUTPUT
Code:
[email protected]:~ > fastboot devices
015d2bbce2501405 fastboot
Code:
fastboot erase system
OUTPUT
Code:
[email protected]:~ > fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.954s]
finished. total time: 2.954s
Code:
fastboot erase recovery
OUTPUT
Code:
[email protected]:~ > fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.945s]
finished. total time: 1.945s
Code:
fastboot -w
OUTPUT
Code:
[email protected]:~ > fastboot -w
erasing 'userdata'...
OKAY [ 23.188s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29618601984
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7231104
Block groups: 221
Reserved block group size: 1024
Created filesystem with 11/1810432 inodes and 157662/7231104 blocks
sending 'userdata' (139133 KB)...
writing 'userdata'...
OKAY [ 26.358s]
erasing 'cache'...
At this point it will either hangs on erasing 'cache'
Or it will give you an error, either way you will need to
reboot the tablet back into fastboot with the hardware buttons
Once that is done continue on the path
Code:
fastboot erase boot
OUTPUT
Code:
[email protected]:~ > fastboot erase boot
erasing 'boot'...
OKAY [ 1.209s]
finished. total time: 1.209s
Code:
fastboot erase misc
OUTPUT
Code:
[email protected]:~ > fastboot erase misc
erasing 'misc'...
OKAY [ 0.978s]
finished. total time: 0.978s
Code:
fastboot erase cache
OUTPUT
Code:
[email protected]:~ > fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 2.843s]
finished. total time: 2.843s
Code:
fastboot -i 0x0B05 flash system boot.blob
During the sending/writing process of this step you will get the blue bar on your screen.....
OUTPUT
Code:
[email protected]:~ > fastboot -i 0x0B05 flash system boot.blob
erasing 'system'...
OKAY [ 2.339s]
sending 'system' (800927 KB)...
OKAY [133.094s]
writing 'system'...
[OKAY [178.036s]
finished. total time: 313.469s
Code:
fastboot -i 0x0B05 reboot
OUTPUT
Code:
[email protected]:~ > fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.020s
Let it boot into stock ROM ....
Credits
@_that for his bootit.ko
TEAM CROMBi and TEAM ZOMBi-X @sbdags @hardslog
Troubleshooting
Here is some troubleshooting
Check out this thread for fasboot.exe, adb.exe and driver help ...CLICK ME
A message from _that
_that said:
Here is the original thread where the bootit module was tested for the first time -> http://forum.xda-developers.com/showthread.php?t=2291974
The problem was that the installed recovery was too old and incompatible with the bootloader and so could not access the eMMC at all. The bootloader command to boot to recovery is stored in the MSC partition (mmcblk0p3), and the recovery could not clear it. Since the bootloader checks the MSC partition before checking for volume-down, it is impossible to get to fastboot without some additional kick in the butt (aka "bootit.ko").
The correct bootit.ko file to use is the one in "bootit-bootloader.zip": http://forum.xda-developers.com/attachment.php?attachmentid=1985941&d=1369339132 - the older version turned out to be too weak. Note that this is a zipped kernel module, not a recovery-installable ZIP. You need to unzip it on your PC before adb push.
After making it to the bootloader menu and working fastboot, you can fastboot flash a current version of TWRP and install the custom ROM of your choice. No real need for the stock blob, unless you want to make sure you have the current bootloader and a known working ROM.
Here is another thread where bootit.ko didn't help, maybe it was really a hardware problem. But lots of good background info from me. -> http://forum.xda-developers.com/showthread.php?t=2437376
And here is another success story -> http://forum.xda-developers.com/showthread.php?p=47525770
Click to expand...
Click to collapse
Thx for all your help @_that
Need some help please with something that has gone wrong with my first attempt to alter Android. I wanted to install a custom recovery, root the phone and take it from there.
I have a Moto e 1st edition, xt1021, system info given below.
I unlocked the boot loader, installed Minimal ADB Fastboot 1.4.3, downloaded the latest TWRP image 3.3.1.-condor for the Moto e from the TWRP website.
I used flashboot flash recovery initially to install the TWRP image, which failed, but has wiped the stock recovery. I cannot boot into recovery or do a factory reset.
The phone will boot normally. If I try a factory reset, it boots normally. If I boot into recovery, I get the Android image on his back with a red triangle, and “no command”. If I go into system recovery from here, and try both 'update by adb sideload' or 'update from sd card', both fail.
I have tried flashboot boot recovery using a stock recovery, but the phone is stuck on the initial Moto logo.
I have also tried to install an earlier TWRP recovery, 2.7.1-condor and CWM 6.o.4.7 falcon but this has failed to install also.
I have now reached the limit of my abilities – any help much appreciated, but please spell out in words of one syllable if possible.
=========================================
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>adb devices
List of devices attached
ZX1B245XHK device
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>adb shell pm list features
feature:reqGlEsVersion=0x30000
feature:android.hardware.audio.output
feature:android.hardware.bluetooth
feature:android.hardware.bluetooth_le
feature:android.hardware.camera
feature:android.hardware.camera.any
feature:android.hardware.faketouch
feature:android.hardware.location
feature:android.hardware.location.gps
feature:android.hardware.location.network
feature:android.hardware.microphone
feature:android.hardware.screen.landscape
feature:android.hardware.screen.portrait
feature:android.hardware.sensor.accelerometer
feature:android.hardware.sensor.light
feature:android.hardware.sensor.proximity
feature:android.hardware.telephony
feature:android.hardware.telephony.cdma
feature:android.hardware.telephony.gsm
feature:android.hardware.touchscreen
feature:android.hardware.touchscreen.multitouch
feature:android.hardware.touchscreen.multitouch.distinct
feature:android.hardware.touchscreen.multitouch.jazzhand
feature:android.hardware.usb.accessory
feature:android.hardware.usb.host
feature:android.hardware.wifi
feature:android.hardware.wifi.direct
feature:android.software.app_widgets
feature:android.software.backup
feature:android.software.connectionservice
feature:android.software.device_admin
feature:android.software.home_screen
feature:android.software.input_methods
feature:android.software.live_wallpaper
feature:android.software.managed_users
feature:android.software.print
feature:android.software.sip
feature:android.software.voice_recognizers
feature:android.software.webview
feature:com.motorola.camera
feature:com.motorola.camera.chalmers
feature:com.motorola.context
feature:com.motorola.hardware.tier.
feature:com.motorola.hardware.wave.0
feature:com.motorola.smartaction2
feature:com.motorola.smartactions2_1.1
feature:com.motorola.software.bodyguard
feature:com.motorola.software.device.condor_umts
feature:com.motorola.software.fmradioservice
feature:com.motorola.software.fmrecording
feature:com.motorola.software.guideme
feature:com.motorola.software.product.condor_tescogb
feature:com.motorola.software.storageoptimizer
feature:com.motorola.software.x_line
==================================================
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>adb reboot bootloader
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>fastboot flash recovery C:
\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3\twrp-2.7.2.0-hlte-4.3.img
target reported max download size of 299892736 bytes
sending 'recovery' (10738 KB)...
OKAY [ 0.608s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) image size exceeds limit
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.686s
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>fastboot boot C:\Users\ME\
Desktop\phone\Minimal_ADB_Fastboot_v1.4.3\recovery-clockwork-6.0.4.7-falcon.img
downloading 'boot.img'...
OKAY [ 0.406s]
booting...
OKAY [ 0.499s]
finished. total time: 0.920s
========================================================
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>FASTBOOT GETVAR ALL
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing
partitions
flashing unlock unlocks the device. Allows user to
flash any partition except the ones
that are related to bootloader
flashing lock_critical Prevents flashing bootloader related
partitions
flashing unlock_critical Enables flashing bootloader related
partitions
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootlo
ader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>
Hi, i am trying to install a system.img to the system partition using fastboot using
Code:
fastboot flash system C:\Users\user\Desktop\system.img
but when i run the command i get this error:
Code:
Sending sparse 'system' 1/7 (460796 KB) OKAY [ 13.966s]
Writing 'system' FAILED (remote: 'sparse flash write failure')
fastboot: error: Command failed
i don't know if this is related to this other issue https://forum.xda-developers.com/t/...-cannot-flash-images-to-file-systems.4535981/
but i can't flash system images neither from recovery nor from fastboot (i have tried also other images).
it doesn't seem to be a memory issue because i have also used the -S option to split the image and it still doesn't work.
Help
Don't put your img file on desktop screen.Move the img file on the C drive and flash again with the right command.Hope it will be solved.
shaon121$ said:
Don't put your img file on desktop screen.Move the img file on the C drive and flash again with the right command.Hope it will be solved.
Click to expand...
Click to collapse
It still doesn't work as administrator and with the image in the C drive root.
Change your img file and try again..or download again... What is your phone model?
shaon121$ said:
Change your img file and try again..or download again... What is your phone model?
Click to expand...
Click to collapse
I have already tried different images, the phone is a Huawei P Smart FIG-LX1.
useless double posts
Can't flash system.img in TWRP - E:Cannot flash images to file systems
I am trying to install a custom ROM on a Huawei P Smart FIG-LX1. I have a system.img that i should flash to the system partition. So when i try to flash the image i have two system partitions: Ona named "System" and one named "System Image". If...
forum.xda-developers.com
Size of image is larger than the target device in TWRP
Hi, I am trying to flash a system image in TWRP. When i try flashing the system.img to the System Image partiton i get this error: Size of image is larger than target device How can i solve this error? I tried the resize partition option on the...
forum.xda-developers.com
slx23 said:
Hi, i am trying to install a system.img to the system partition using fastboot using
Code:
fastboot flash system C:\Users\user\Desktop\system.img
but when i run the command i get this error:
Code:
Sending sparse 'system' 1/7 (460796 KB) OKAY [ 13.966s]
Writing 'system' FAILED (remote: 'sparse flash write failure')
fastboot: error: Command failed
i don't know if this is related to this other issue https://forum.xda-developers.com/t/...-cannot-flash-images-to-file-systems.4535981/
but i can't flash system images neither from recovery nor from fastboot (i have tried also other images).
it doesn't seem to be a memory issue because i have also used the -S option to split the image and it still doesn't work.
Help
Click to expand...
Click to collapse
[Solved] Fastboot flash super error - FAILED (remote: 'failed to check sparse crc')
Hi, I'm getting an error trying to install stock rom from xiaomirom.com via fastboot. D:\Downloads\vili_eea_global_images_V12.5.21.0.RKDEUXM_20220224.0000.00_11.0_eea>fastboot flash super...
forum.xda-developers.com