Due:
Please help me.
my kindle fire Unbricking,i need kindle fire system.img to fastboot IT.
i have Factory Cable.
so i need system.img.who can help me ?
THX.a
http://www.megaupload.com/?d=7QY56FGA system.img
Do you made this cable by yourself?
Do you made this cable by yourself?[/QUOTE]
THX.I just buy it.i'm chinese.
DUE:
system.zip Unexpected end of archive:
This system.img was posted somewhere on the forum ... There are no instructions recovery device using fastboot mode. No experience of successful recovery Kindle Fire.
It would be nice if someone made a instructions on how to restore the unit if you have access to Fastboot.
Not sure, but I believe it would be:
fastboot update <filename.zip> -w
You should be able to download the entire update from Amazon.com, rename it update.zip, then run that, effectivly reloading the entire system, boot, and recovery. the -w at the end wipes all user data, so use at own risk.
Fastboot Commands
Here are the commands you can run on your host after fastboot has been started on a device connected via USB. This is a paste directly from the fastboot binary's "--help" command:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash 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
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
MayfairDROID said:
Not sure, but I believe it would be:
fastboot update <filename.zip> -w
You should be able to download the entire update from Amazon.com, rename it update.zip, then run that, effectivly reloading the entire system, boot, and recovery. the -w at the end wipes all user data, so use at own risk.
Fastboot Commands
Here are the commands you can run on your host after fastboot has been started on a device connected via USB. This is a paste directly from the fastboot binary's "--help" command:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash 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
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
Click to expand...
Click to collapse
Tried it yesterday. Returns:
archive does not contain 'android-infor.txt'
archive does not contain 'android-product.txt'
archive does not contain :android-info.txt"
Although I suppose I could create dummy txt files and see what happens...
MayfairDROID said:
Not sure, but I believe it would be:
fastboot update <filename.zip> -w
You should be able to download the entire update from Amazon.com, rename it update.zip, then run that, effectivly reloading the entire system, boot, and recovery. the -w at the end wipes all user data, so use at own risk.
Click to expand...
Click to collapse
Yeah IN RECOVERY yes, if fastboot no. You cannot go and flash the update.zip from amazon in recovery. You need to create a system.img and flash that properly in fastboot. If you go google the directions for fastboot, it will tell you how.
yareally said:
Yeah IN RECOVERY yes, if fastboot no. You cannot go and flash the update.zip from amazon in recovery. You need to create a system.img and flash that properly in fastboot. If you go google the directions for fastboot, it will tell you how.
Click to expand...
Click to collapse
Yes but that's the problem, at least with with my level of expertise. This is kind of a catch 22 situation. We really need someone with a rooted and operable device to make available a backup of a stock system.img. Once that's avail. it's as simple as plugging in the factory cable to enable fastboot and entering the command.
kfuller said:
Yes but that's the problem, at least with with my level of expertise. This is kind of a catch 22 situation. We really need someone with a rooted and operable device to make available a backup of a stock system.img. Once that's avail. it's as simple as plugging in the factory cable to enable fastboot and entering the command.
Click to expand...
Click to collapse
No you don't.
You just need to grab the update file from amazon
Create a system.img from the /system folder
flash in fastboot
done
yareally said:
No you don't.
You just need to grab the update file from amazon
Create a system.img from the /system folder
flash in fastboot
done
Click to expand...
Click to collapse
Thanks. I've had the update file for some time and I do understand that it can be done, but the creation of the system.img from files seems quite involved for my level of skills and a windows box. I have googled it. On the other hand, the task appears much simpler on a working android machine and I was hoping that someone had already done it in this forum and could ease the pain. But, I'll get there if not. Sooner or later.
kfuller said:
Thanks. I've had the update file for some time and I do understand that it can be done, but the creation of the system.img from files seems quite involved for my level of skills and a windows box. I have googled it. On the other hand, the task appears much simpler on a working android machine and I was hoping that someone had already done it in this forum and could ease the pain. But, I'll get there if not. Sooner or later.
Click to expand...
Click to collapse
Need to do it in linux because it has to be ext4.
I would do it, but I don't have time right now (packing for a trip this weekend).
I'm running ubuntu, so could do it if someone posts up instructions.....
Sent from my Kindle Fire using Tapatalk
MayfairDROID said:
I'm running ubuntu, so could do it if someone posts up instructions.....
I see this tool that may work http://android.podtwo.com/romdump/ but looking for a tut that shows more detail of what you get..
OK, this looks most promising. Here is a link showing using the rkdump utility: http://wiki.archosfans.com/index.ph...m_rom#Dump_partitions_the_easy_way_via_rkdump
Dump partitions from your Home Tablet
You can't dump partitions the normal way with cat/dd command as you might be used to on linux/unix/macOSX. The /dev/mtd/mtd* is useless on RK28xx devices.
You can use the /dev/block/mtd* devices, but in this case you can read beyond the end of the partition if you set the blocksize too large (or you can read not enough if you set it too small).
For the next steps you need to be rooted. A softrooted device is sufficient.
To softroot your device download z4root and some terminal apk and install them.
In the terminal you first issue the command "su" to get to superuser mode. note: as mentioned above: all numbers and sizes, partitions and partition sizes are based on the original 1.0.0 firmware of the A7 HT Version 2.
To get a list of the available partitions type:
# cat /proc/mtd
dev: size erasesize name
mtd0: 00002000 00000010 "misc"
mtd1: 00004000 00000010 "kernel"
mtd2: 00002000 00000010 "boot"
mtd3: 00004000 00000010 "recovery"
mtd4: 00030000 00000010 "system"
mtd5: 0003a000 00000010 "backup"
mtd6: 0003a000 00000010 "cache"
mtd7: 00100000 00000010 "userdata"
mtd8: 00cbc000 00000010 "user"
mtd9: 00020000 00000010 "pagecache"
mtd10: 00020000 00000010 "swap"
The update.img to restore your A7HT is identical to the backup partition.
With this information we can dump our original update.img or create dumps from e.g. the system.img. There are 2 ways to do this:
- The easy way via the rkdump utility.
- The hard way via dd (in case you really want to know the ins and outs).
Dump partitions the easy way via rkdump
The rkdump utility is an Android command line utility and needs to be run from your tablet. Unzip the rkdump utility from the downloaded zip file. Copy it to your tablet, either via the "normal" USB copy way or via ADB push. Copy it onto your /data partition and not on your /sdcard partition or the SD-card itself (it needs to be run from an ext3 partition, not a vfat partition). If neccessary do a "chmod 771 rkdump" to give it the correct attributes. Now from a rooted terminal you can dump the update.img. Our update.img is equal to the backup.img which, in this case, is located on mtd5. To get our update.img we now type in the (rooted) terminal.
# /data/rkdump /dev/block/mtdblock5 /sdcard/update.img
This will dump the update.img to the internal memory of the tablet. It will immediately save it in the correct size. There are no "post dump" actions required to the image as it has the right size and the 4-byte crc set.
Sooo, looks like you can simply substitute system.img in the above tutorial to create the system.img which can then be pulled off the kindle with adb. Does this sound ok?
Click to expand...
Click to collapse
I command you to rise from your grave and rescue my... Kindle. (10 points if you can name the reference).
I'm suffereing the same issue. I've managed to get my SD Card, recovery, boot, and boot loader partitions working, but I need a system.img and any other img files I haven't listed. I thought there was another one, but I cant't find my notes on it. I would be indebted to you. Thanks.
vampyrex13 said:
I command you to rise from your grave and rescue my... Kindle. (10 points if you can name the reference).
I'm suffereing the same issue. I've managed to get my SD Card, recovery, boot, and boot loader partitions working, but I need a system.img and any other img files I haven't listed. I thought there was another one, but I cant't find my notes on it. I would be indebted to you. Thanks.
Click to expand...
Click to collapse
Well... since nobody else answered you... Is there a reason you are trying to do it this way? If you have access to recovery and SD Card, you can just flash whatever you want in recovery.
kinfauns said:
Well... since nobody else answered you... Is there a reason you are trying to do it this way? If you have access to recovery and SD Card, you can just flash whatever you want in recovery.
Click to expand...
Click to collapse
I have an issue with the mmcblk0 partition not having a label (gpt). I tried yaff'ing up the current Kindle Fire update and fastbooted it over, but that didn't work. I even deleted mmcblk0 and then fastbooted the update over and it recreated the partition, but had the same issue still. My only other avenues available are to try an actual stock img (in case I was missing something when I yaff'ed my copy) or completely recreate all the partitions from scratch. I would much rather fastboot the system image though.
vampyrex13 said:
I have an issue with the mmcblk0 partition not having a label (gpt). I tried yaff'ing up the current Kindle Fire update and fastbooted it over, but that didn't work. I even deleted mmcblk0 and then fastbooted the update over and it recreated the partition, but had the same issue still. My only other avenues available are to try an actual stock img (in case I was missing something when I yaff'ed my copy) or completely recreate all the partitions from scratch. I would much rather fastboot the system image though.
Click to expand...
Click to collapse
Whoah.... You'd better be careful with those partitions. If something goes bad with the first two partitions, you might be looking at opening up your case. If you need to write your partition table back to stock, it's much easier and safer to use "fastboot oem format" in FFF 1.1 or later. It will write a stock partition table for you.
Even if you did manage to make a system.img (I think I looked into this before, but couldn't find a good reference), I doubt fastboot will flash it for you. I think I tried this too and it was too big for fastboot to hold it in memory before it attempted to write it out to the partition.
I think your best bet is to download the software update from Amazon, rename it as a zip file, then use TWRP to flash the whole thing. The only bad thing about it is that you will lose your custom bootloader and recovery and you'd have to jump through some hoops to get them back again.
Alternatively, I've been experimenting with the idea of using "adb push" to copy the /system directory from the software update package over onto the device. I've "ported" the set of commands in the updater-script that creates the symbolic links and changes owner/permissions of all the files over to a shell script that can be run through adb. It should pretty much be equivalent to how the system files get installed through recovery. If you want to give it a try, send me a PM.
Ofastboot oem format fails and i've already opened the case to do the usb trick.
vampyrex13 said:
Ofastboot oem format fails and i've already opened the case to do the usb trick.
Click to expand...
Click to collapse
You're probably using an older version of FFF... you need v1.1 or later. If you used the shorting method, that probably means you have Firekit somewhere. I believe the u-boot.bin in there is FFF v1.2 or search the development section for one of the later versions. Flash one of them and try again.
Related
Hey guys, I'm a new member to XDA but I've been browsing on it for a while. I figured you guys could help. I rooted my Kindle Fire a couple months ago and had Clockwork Recovery(TWRP is better). I decided I didn't want it rooted so I restored the Kindle thinking it would remove the root, it actually bricked it. Now all that comes up is the Kindle Fire boot screen with the android bot over top of it, it doesn't glimmer or flash, that's all. It isn't recognized by ADB or Windows(and Device Manager). I haven't found a thread exactly like mine so I figured I'd post one. Please help guys, I miss Minecraft PE and Netflix!
Assuming you know how to access recovery...
Download the latest version of FireFireFire and either "adb push" it to your sdcard or use the mount function in recovery and transfer it.
FireFireFire 1.4 can be found here. It comes in a .zip file for flashing in recovery. DO NOT install the .zip file with the "fastboot flash bootloader" command or you will brick your device.
When installed reboot and use your power button at the kindle fire screen as if you were trying to enter recovery. At some point some options will show up on the bottom. Use the power button to select "Normal Boot".
@soupmagnet
what do you mean by ADB Push? Recovery as in turning the kindle on and then holding the power button again until it turns orange?
mrpike9416 said:
@soupmagnet
what do you mean by ADB Push?
Click to expand...
Click to collapse
Actually, it would be easier to explain how to mount your sdcard.
Recovery as in turning the kindle on and then holding the power button again until it turns orange?
Click to expand...
Click to collapse
Yes. While in recovery, there will be a mount to USB function that will mount the sdcard partition to your computer as if it were an external drive, such as a USB thumb drive.
Good thing I know that, however, I can't access recovery..
I think I might've reformatted the system folder while in recovery..
mrpike9416 said:
Good thing I know that, however, I can't access recovery..
I think I might've reformatted the system folder while in recovery..
Click to expand...
Click to collapse
Recovery is in a separate partition from the system files and cannot be formatted while in recovery. I'm not sure why you wouldn't be able access recovery so you'll probably need to reinstall it.
How comfortable are you with using command prompt?
A little experienced, how hard can entering commands be?
mrpike9416 said:
A little experienced, how hard can entering commands be?
Click to expand...
Click to collapse
OMG Don't EVER say that.
Do you have adb and fastboot on your computer? If yes...Is it from AndroidSDK or KFU?
Hahahahha my mistake.
I do have ADB but I don't think I have fastboot(I probably do).
I do have fastboot.
mrpike9416 said:
I do have fastboot.
Click to expand...
Click to collapse
Okay, make sure the you have TWRP version 2.1 and place it in the same folder as fastboot. It would be wise to rename it to something manageable like "twrp.img"
In your command prompt, enter:
fastboot flash recovery twrp.img
Note: version 2.0 will not work with this command
And while you're at it:
fastboot oem idme bootmode 4000
fastboot reboot
[Edit:] That will likely fix your problem (barring driver issues) but you should still install FFF1.4
I just tried a different cable and the computer recognizes my kindle in device manager as Android ADB Interface... the twrp 2.1 cmd thing you told me to do was a no go but I assume we have more options now now that device manager recognizes it?
(EDIT)
It is now recognized on device manager as "Unknown Device" and no longer as Android ADB Interface..
1. What happens when you enter:
Code:
fastboot devices
2. What error message, if any, did you receive when entering the "twrp 2.1 cmd thing"?
"fastboot" is not recognized as an internal or external command, operable program or batch file.
That happened for both instances.
mrpike9416 said:
"fastboot" is not recognized as an internal or external command, operable program or batch file.
That happened for both instances.
Click to expand...
Click to collapse
Do you have fastboot and what folder is it in?
Yeah its an .exe file i believe... under the "Files and Tools" folder when I downloaded ADB from Android SDK.
Better yet...fastboot and adb are programs with a certain set of commands associated with them. Those commands only work with each individual program. In order to issue a certain command that isn't associated with "shell" or "DOS" you have to include an "identifier" so the computer knows from which program to run the commands. In this case it is "fastboot" because you are using the fastboot program. In order issue commands this way, the program you are using must either be listed in your "PATH" or be in the directory from which you are issuing the commands.
The easiest way to do this in Windows is to shift+right click on the folder containing the program and select "Run in Command". The command window that opens is were you will be entering your commands.
error: cannot load "twrp.img"
I typed "fastboot devices!" (out of frustration I must admit).
This is what came up:
C:\Users\Nick\Documents\KindleRoot\tools>fastboot devices!
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
reboot reboot device normally
reboot-bootloader reboot device into bootloader
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
Turn your device off then enter the command. When it says "waiting for device" turn it back on.
Fastboot commands only work in fastboot mode. If you have a modified bootloader installed, the first few seconds of the boot process is a temporary fastboot mode which will accept fastboot commands.
If it just hangs at "waiting for device", you need to fix your drivers.
soupmagnet said:
Turn your device off then enter the command. When it says "waiting for device" turn it back on.
Fastboot commands only work in fastboot mode. If you have a modified bootloader installed, the first few seconds of the boot process is a temporary fastboot mode which will accept fastboot commands.
If it just hangs at "waiting for device", you need to fix your drivers.
Click to expand...
Click to collapse
what command am I entering?
So coming from MDA89E, I was not receiving the OTA for MDB08I that others around me had received so I decided to go the old "./flash-all.sh" route. I already had performed "fastboot oem unlock" to change build.prop for the hotspot provisioning flag.
However, there was something wrong with the image-bullhead-mdb08i.zip (correct MD5 of the overall package) or my setup, and I received the message "FAILED (remote: data too large)" on the "fastboot -w update image-bullhead-mdb08i.zip" step.
This lead down to long path of frustration until I ran into this post: http://forum.xda-developers.com/showpost.php?p=57272090&postcount=25
After extracting bullhead-mdb08i.zip and manually formatting/erasing and flashing the files individually, I was able to boot as normal.
This error can also be a result of using an out-of-date fastboot binary. Just an FYI.
ahhh didn't think of that.
Time flies.. It's probably time to update. Thanks
EDIT: I use fastboot/adb on Linux Mint 17 Qiana and the package manager says both android-tools-adb and android-tools-fastboot are up-to-date. So whether or not that is actually the case is to be determined, but my OP regarding this issue occurred on the "latest" version of fastboot available via the package manager.
Ugh, I'm running into this issue and I've updated all my ADB/Fastboot files/binaries. I can't, for the life of me, figure out how to get the system.img to flash properly. I've tried everything using Fastboot commands and it just won't work. I updated all my SDK files and I imagine that it updated my ADB/Fastboot binaries. Not sure how to update the Fastboot binaries manually.
Anyone else still running into this?
sn0warmy said:
Ugh, I'm running into this issue and I've updated all my ADB/Fastboot files/binaries. I can't, for the life of me, figure out how to get the system.img to flash properly. I've tried everything using Fastboot commands and it just won't work. I updated all my SDK files and I imagine that it updated my ADB/Fastboot binaries. Not sure how to update the Fastboot binaries manually.
Anyone else still running into this?
Click to expand...
Click to collapse
Try:
fastboot -S 512M flash system system.img
Sent from my HTC One M9 using Tapatalk
efrant said:
Try:
fastboot -S 512M flash system system.img
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I ended up getting it to work. I uninstalled all instances of ADB/SDK/Fastboot from my mac, rebooted and reinstalled the full SDK tools again and re-setup ADB. After doing that I was able to flash everything, including system.img with no issues. Looks like I was just missing some fastboot binaries afterall.
efrant said:
Try:
fastboot -S 512M flash system system.img
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
this command does not work. I get this as a response when I run this command.
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
format <partition> format 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
when i try to flash files individually, I get stuck in erasing recovery, do you know why? I can't go further than that, I haven't disconnect it yet because I'm afraid it gets ****ed.
---------- Post added at 09:58 AM ---------- Previous post was at 09:39 AM ----------
peon1-9 said:
So coming from MDA89E, I was not receiving the OTA for MDB08I that others around me had received so I decided to go the old "./flash-all.sh" route. I already had performed "fastboot oem unlock" to change build.prop for the hotspot provisioning flag.
However, there was something wrong with the image-bullhead-mdb08i.zip (correct MD5 of the overall package) or my setup, and I received the message "FAILED (remote: data too large)" on the "fastboot -w update image-bullhead-mdb08i.zip" step.
This lead down to long path of frustration until I ran into this post: http://forum.xda-developers.com/showpost.php?p=57272090&postcount=25
After extracting bullhead-mdb08i.zip and manually formatting/erasing and flashing the files individually, I was able to boot as normal.
Click to expand...
Click to collapse
I did this, it has shown everything ok, from flashing system and rebooting but I am stuck in Google logo now. I flashed bullhead-mtc20k-factory-4a950470, do I have to wait for it to boot or I'll have to heat the processor now?
---------- Post added at 10:00 AM ---------- Previous post was at 09:58 AM ----------
ferdeenandxda said:
when i try to flash files individually, I get stuck in erasing recovery, do you know why? I can't go further than that, I haven't disconnect it yet because I'm afraid it gets ****ed.
---------- Post added at 09:58 AM ---------- Previous post was at 09:39 AM ----------
I did this, it has shown everything ok, from flashing system and rebooting but I am stuck in Google logo now. I flashed bullhead-mtc20k-factory-4a950470, do I have to wait for it to boot or I'll have to heat the processor now?
Click to expand...
Click to collapse
It has rebooted 2 times already i think it didn't work.
efrant said:
Try:
fastboot -S 512M flash system system.img
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I can't reflash htc desire 700 even with the -S option. It shows the same error (data too large) also in RUU mode. I found the firmware on Hardreset.info in their htc firmware database. If you need firmware, then no problem, though I'm without a computer now, but from my iPhone. I did not download the firmware there (and I'm too lazy to wait for the download, for a long time). Please, help!
Hi everyone ! (I apologyze for my english)
I cant flash anything on my Pixel C because of this:
C:\Users\ykant\Desktop\Minimal ADB and Fastboot>fastboot flash recovery TWRP_dragon_3.0.2-23.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
finished. total time: -0.000s
Click to expand...
Click to collapse
No system to boot on and my TWRP is wiped !!
--> Cant do this:
fwtool vbnv write dev_boot_fastboot_full_cap 1
Click to expand...
Click to collapse
Is my pixel C bricked now ?
regards !
Did you unlock your device first with "fastboot oem unlock"?
redukt said:
Did you unlock your device first with "fastboot oem unlock"?
Click to expand...
Click to collapse
Yes i did this before, i was running on Remix OS
I don't know if this is of relevance but there were new fastboot commands introduced from Android M (?) and I have recollection about "partial unlock" - two flags required to be set and if only one was set it could be reported that the bootloader was unlocked but fastboot saw it as locked. Above may be totally wrong.
Here's the difference between old and current fastboot commands. Note the new lock/unlock commands
Code:
************************ OLD **************************************
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
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> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] 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
************************ NEW **************************************
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> Reflash device from update.zip.
Sets the flashed slot as active.
flashall Flash boot, system, vendor, and --
if found -- recovery. If the device
supports slots, the slot that has
been flashed to is set as active.
Secondary images may be flashed to
an inactive slot.
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
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.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
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.
set_active <slot> Sets the active slot. If slots are
not supported, this does nothing.
boot <kernel> [ <ramdisk> [ <second> ] ] Download and boot kernel.
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ]
Create bootimage and flash it.
devices [-l] List all connected devices [with
device paths].
continue Continue with autoboot.
reboot [bootloader] Reboot device [into bootloader].
reboot-bootloader Reboot device into bootloader.
help Show this help message.
-Yazh- said:
Hi everyone ! (I apologyze for my english)
I cant flash anything on my Pixel C because of this:
C:\Users\ykant\Desktop\Minimal ADB and Fastboot>fastboot flash recovery TWRP_dragon_3.0.2-23.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
finished. total time: -0.000s
Click to expand...
Click to collapse
No system to boot on and my TWRP is wiped !!
--> Cant do this:
fwtool vbnv write dev_boot_fastboot_full_cap 1
Click to expand...
Click to collapse
Is my pixel C bricked now ?
regards !
Click to expand...
Click to collapse
Hi, I'm just wondering if you were able to fix your tablet. I ran into the same problem as you here and am not able to find a solution to it.
Hi !!
Sorry for bad news, but i didn't found any solution since my Pixel C was bricked. Maybe there is a solution, but I dropped it before finding it.
I hope you find something to fix it !
@viii_xvi Are you using "Minimal ADB and Fastboot" as shown in the post you quoted by -Yazh- ? The current (?) version that I can find is 1.4.3 and that looks to be "2015".
For the current versions of adb and fastboot and the revision history, 12 since October 2016, see https://developer.android.com/studio/releases/platform-tools.html
peterk-1 said:
Are you using "Minimal ADB and Fastboot" as shown in the post you quoted by -Yazh- ? The current (?) version that I can find is 1.4.3 and that looks to be "2015".
Click to expand...
Click to collapse
No. I used the 15 second ADB and Fastboot installer. I'm pretty sure it works fine as I can use fastboot commands.
peterk-1 said:
For the current versions of adb and fastboot and the revision history, 12 since October 2016, see https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
I don't really know what to do with the files found in the zip. If I'm doing it wrong, can you tell me what I should be doing?
viii_xvi said:
No. I used the 15 second ADB and Fastboot installer. I'm pretty sure it works fine as I can use fastboot commands.
I don't really know what to do with the files found in the zip. If I'm doing it wrong, can you tell me what I should be doing?
Click to expand...
Click to collapse
There are Youtube videos on installing Android Platform Tools and a web search for installing Android Platform Tools with your o/s will find many hits. You need to know you are installing just the platform tools - some of the guides assume you are installing or have installed the full Android Software Development Kit (SDK).
Assuming you are using Windows then the simplest method is to copy the contents of the zip file into the current location of your "15 second" files. This ensures that you can run the new version of fastboot with the folder path you have used previously. In file manager "find" fastboot.exe and that will give you the folder to unzip ALL of the platform tools files. You will know if you have done it correctly if you get requests to overwrite existing files when you unzip the files.
peterk-1 said:
There are Youtube videos on installing Android Platform Tools and a web search for installing Android Platform Tools with your o/s will find many hits. You need to know you are installing just the platform tools - some of the guides assume you are installing or have installed the full Android Software Development Kit (SDK).
Assuming you are using Windows then the simplest method is to copy the contents of the zip file into the current location of your "15 second" files. This ensures that you can run the new version of fastboot with the folder path you have used previously. In file manager "find" fastboot.exe and that will give you the folder to unzip ALL of the platform tools files. You will know if you have done it correctly if you get requests to overwrite existing files when you unzip the files.
Click to expand...
Click to collapse
I've followed the instructions so I'm confident I did it correctly. Despite this, nothing has improved. I still can't flash the stock ROM or a custom recovery in fastboot.
What I've noticed from updating the fastboot version are some new commands I found when I entered "fastboot -h"
Code:
fastboot -h
commands:
reboot [bootloader|emergency]
stage <infile>
get_staged <outfile>
options:
--skip-secondary
--skip-reboot
--disable-verity
--disable-verification
--unbuffered
--version
From what I've tried, all the commands in options returns
fastboot: usage: no command
Click to expand...
Click to collapse
viii_xvi said:
I've followed the instructions so I'm confident I did it correctly. Despite this, nothing has improved. I still can't flash the stock ROM or a custom recovery in fastboot.
What I've noticed from updating the fastboot version are some new commands I found when I entered "fastboot -h"
Code:
fastboot -h
commands:
reboot [bootloader|emergency]
stage <infile>
get_staged <outfile>
options:
--skip-secondary
--skip-reboot
--disable-verity
--disable-verification
--unbuffered
--version
From what I've tried, all the commands in options returns
Click to expand...
Click to collapse
Hi, Did you tried to flash with the oldest stock rom of the pixel C ? Because it uses older version of fastboot so maybe it will work. I has also the same problem as you but hopefully twrp still worked so i could flash another system image.
rhmanoa said:
Hi, Did you tried to flash with the oldest stock rom of the pixel C ? Because it uses older version of fastboot so maybe it will work. I has also the same problem as you but hopefully twrp still worked so i could flash another system image.
Click to expand...
Click to collapse
I have now tried to flash the earliest factory image and am disappointed to say the bootloader did not flash and so I wasn't able to complete the flashing.
I don't think the problem is the fastboot version. It may be the bootloader itself. I've read someone describe this problem as "Broken fastboot (bootloader) security." I think the problem is that, when unlocked, the bootloader would return the same messages as if it was locked. The security of the bootloader still thinks it's locked and not allow flashing of any images. Also that locking and reunlocking does not improve the situation. This would explain why, when bootloader is unlocked, I get "remote: unsupported command" and "remote: image verification failed", the same as when I try the same commands when the bootloader is locked.
viii_xvi said:
I have now tried to flash the earliest factory image and am disappointed to say the bootloader did not flash and so I wasn't able to complete the flashing.
I don't think the problem is the fastboot version. It may be the bootloader itself. I've read someone describe this problem as "Broken fastboot (bootloader) security." I think the problem is that, when unlocked, the bootloader would return the same messages as if it was locked. The security of the bootloader still thinks it's locked and not allow flashing of any images. Also that locking and reunlocking does not improve the situation. This would explain why, when bootloader is unlocked, I get "remote: unsupported command" and "remote: image verification failed", the same as when I try the same commands when the bootloader is locked.
Click to expand...
Click to collapse
Just bought today, same issue, have you solved it?
mansonstein said:
Just bought today, same issue, have you solved it?
Click to expand...
Click to collapse
No, I didn't manage to fix it.
did you found a solution yet？
I got a same problem,cant flash anything but ordinary using.
I got the problem caused by flashed twrp3.2.3,cant get into system,just always get into twrp.
cant flash any official firmware with "flash-all.bat",no matter which platform tool or firmware.but the twrp were installed before can flash anything.
finally,I flashed newest OTA firmware,then device can be booted. but got the unsupported command
richardwia said:
did you found a solution yet？
I got a same problem,cant flash anything but ordinary using.
I got the problem caused by flashed twrp3.2.3,cant get into system,just always get into twrp.
cant flash any official firmware with "flash-all.bat",no matter which platform tool or firmware.but the twrp were installed before can flash anything.
finally,I flashed newest OTA firmware,then device can be booted. but got the unsupported command
Click to expand...
Click to collapse
I'm assuming you have the latest version of TWRP installed. IIRC, there should be "Fix Fastboot" in advanced options. If indeed you have the same problem I had, pressing this should fix the problem. I don't know anything beyond this as I never got to find out what happens afterwards.
viii_xvi said:
I'm assuming you have the latest version of TWRP installed. IIRC, there should be "Fix Fastboot" in advanced options. If indeed you have the same problem I had, pressing this should fix the problem. I don't know anything beyond this as I never got to find out what happens afterwards.
Click to expand...
Click to collapse
really？where I can find the“fix fastboot in advanced options”？
richardwia said:
really？where I can find the“fix fastboot in advanced options”？
Click to expand...
Click to collapse
I believe I'm not qualified to help you as I disposed of my tablet months ago. All the advice I've given is off of memory and may not be accurate. That being said, I won't help you anymore in fear of giving inaccurate information that may lead to bricking of your tablet.
I have a pixel C, flashed with latest 3-rd pixel experience before, someday i tried to flash back to factory image, hit the same trouble like this topic, i came here several times before, no solution, today, i found another article about this , it's solved my trouble.
sorry i am new here, i couldn't share the outside article link.
would like to share what i did on my pixel c.
1. root your pixel c
2. adb shell //this command could be executed under recovery mode too.
3. su
4. fwtool vbnv write dev_boot_fastboot_full_cap 1
5. adb reboot fastboot
then you could flash anything you want.
I had this just now - I finally got fed up of my Pixel C being so laggy and also chrome opening up as blank pages (I switched to brace to fix this, but it's abit crashy).
Anyhow I found that after
adb reboot bootloader
that
fastboot flash recovery twrp.img
was failing for me in the "Writing" stage
I discovered that the fix was to use
adb flashing unlock
then it will ask you a question (power button to confirm and one of teh volume keys to cancel).
after this it spins with erasing for a while and then comes back to fastboot after which
fastboot flash recovery twrp.img
Worked, after this you get an annoying 30s delay for each restart, I think that can be fixed by
adb flashing lock
I'll verify this when I've finished flashing a usable ROM to my Pixel C...
Been searching here and Google. No luck.
Do we have a decent list of all the fastboot commands, especially all the ones that pertain to dual partitions?
I want to switch the active partition to make sure all is OK on that side.
@TonikJDK,
This is the only thing I've seen > https://forum.xda-developers.com/pixel-xl/how-to/pixel-xl-fastboot-commands-t3490080
TonikJDK said:
Been searching here and Google. No luck.
Do we have a decent list of all the fastboot commands, especially all the ones that pertain to dual partitions?
I want to switch the active partition to make sure all is OK on that side.
Click to expand...
Click to collapse
If you just type "fastboot" without any switch, you'd get a complete list of switches, right? Then it's really easy to output that to a text file. I'll get one for you shortly.
For now, to answer your end question, you can use "fastboot --set-active=_a" (or _b). It's ten times faster than going through twrp, providing you have access to a PC.
Got it, thanks gang. I looked at the fastboot output and that link before posting. Never saw set_active. Think I will have some more coffee before I dig into why my other slot bootloops.
TonikJDK said:
Been searching here and Google. No luck.
Do we have a decent list of all the fastboot commands, especially all the ones that pertain to dual partitions?
I want to switch the active partition to make sure all is OK on that side.
Click to expand...
Click to collapse
This copy and paste is lousy since it screws up spacing, so I attached the syntax list here.
View attachment 3991598
commands:
update <filename> Reflash device from update.zip.
Sets the flashed slot as active.
flashall Flash boot, system, vendor, and --
if found -- recovery. If the device
supports slots, the slot that has
been flashed to is set as active.
Secondary images may be flashed to
an inactive slot.
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
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.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request
.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
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.
set_active <slot> Sets the active slot. If slots are
not supported, this does nothing.
boot <kernel> [ <ramdisk> [ <second> ] ] Download and boot kernel.
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ]
Create bootimage and flash it.
devices [-l] List all connected devices [with
device paths].
continue Continue with autoboot.
reboot [bootloader] Reboot device [into bootloader].
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 erase partition before
formatting.
-s <specific device> Specify a device. For USB, provide ei
ther
a serial number or path to device por
t.
For ethernet, provide an address in t
he
form <protocol>:<hostname>[ort] whe
re
<protocol> is either tcp or udp.
-p <product> Specify product name.
-c <cmdline> Override kernel commandline.
-i <vendor id> Specify a custom USB vendor id.
-b, --base <base_addr> Specify a custom kernel base
address (default: 0x10000000).
--kernel-offset Specify a custom kernel offset.
(default: 0x00008000)
--ramdisk-offset Specify a custom ramdisk offset.
(default: 0x01000000)
--tags-offset Specify a custom tags offset.
(default: 0x00000100)
-n, --page-size <page size> Specify the nand page size
(default: 2048).
-S <size>[K|M|G] Automatically sparse files greater
than 'size'. 0 to disable.
--slot <slot> Specify slot name to be used if the
device supports slots. All operations
on partitions that support slots will
be done on the slot specified.
'all' can be given to refer to all sl
ots.
'other' can be given to refer to a
non-current slot. If this flag is not
used, slotted partitions will default
to the current active slot.
-a, --set-active[=<slot>] Sets the active slot. If no slot is
provided, this will default to the va
lue
given by --slot. If slots are not
supported, this sets the current slot
to be active. This will run after all
non-reboot commands.
--skip-secondary Will not flash secondary slots when
performing a flashall or update. This
will preserve data on other slots.
--unbuffered Do not buffer input or output.
--version Display version.
-h, --help show this message.
TonikJDK said:
Got it, thanks gang. I looked at the fastboot output and that link before posting. Never saw set_active. Think I will have some more coffee before I dig into why my other slot bootloops.
Click to expand...
Click to collapse
If you can't use the set_active or --set-active switch, you don't have the latest adb/fastboot binary from Android SDK. Besides the --set-active parameter, the more important one is 'slot' with which you can establish where to flash. You can issue "fastboot --ver" and check the version number. It should start with a '3'.
quangtran1 said:
If you don't see the set_active or --set-active switch, you don't have the latest adb/fastboot binary from Android SDK. Besides the --set-active parameter, the more important one is 'slot' with which you can establish where to flash. You can issue "fastboot --ver" and check the version number. It should start with a '3'.
Click to expand...
Click to collapse
I'm good, got it. This entire thread is due to my poor reading comprehension today.
TonikJDK said:
I'm good, got it. This entire thread is due to my poor reading comprehension today.
Click to expand...
Click to collapse
Read? Who's got time for that?
quangtran1 said:
Read? Who's got time for that?
Click to expand...
Click to collapse
Yea, no time to read cuz I'm too busy posting about what I should have read.
The device appears to be soft-bricked. Boot hangs at the logo screen. I can access the Fastboot Menu and the Recovery menu. I have the ROM backup created with Lenovo Smart Assistant.
What I've already tried:
1. Using Lenovo Smart Assistant. That only gets so far and then it expects the tablet to be able to boot enough to get to the USB options, which it can't.
2 Since the device will talk to a computer while at the fastboot menu, I did fastboot flash boot boot.img and the outcome was the same.
3. I would have tried to restore just the system.img, but the ROM has 30 system img files, system_1.img, system_2.img, system_3.img, et cetera. I tried to combine them using:
- 3a. simg2img system* newsystem.out but got the error "build_directory_structure: can't set android permissions - built without android support"
- 3b. packsparseimg which gave me a "raw" system file. I could not find a way to convert this to a single system.img file.
4. fastboot flashall, but I don't know what to set $ANDROID_PRODUCT_OUT to just to make that work. I'm also not sure if this requires the ROM directory to be zipped?
What is there to try next?
jeb.jr said:
The device appears to be soft-bricked. Boot hangs at the logo screen..........
Click to expand...
Click to collapse
I don't have this device myself but, I had performed a quick search and found the following thread where the most recent post may be helpful for what you are looking for that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3508508
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
Thanks, but Lenovo Smart Assistant only gets to the screen where it prompts me for USB debugging, but my tablet won't boot that far. The Device Manager in Windows doesn't come up with a triangle for anything.
However, I tried something else and got myself stuck at the fastboot menu:
There is no flash_all script in the ROM directory, but one was created by typing python createFlashTool.py. Then flash_all.sh, flash_factory.sh, and flash_all_except_storage.sh. I ran flash_all.sh and it said "Missmatching image and device". Oddly enough, flash_all is looking for MSM8953 and I have MSM8909. This must be the correct ROM because it was the one that downloaded from Lenovo Smart Assistant with my tablet number and hardware versions. So, I modified the first line of flash_all, replacing MSM8953 with MSM8909. When I entered ./flash_all.sh this time, it flashed all the img files, giving me OKAY messages over the next several minutes. Update: I suspect there's a bug in here, because it looks like system is just being overwritten 30 times instead of actually being built up.
Now, booting from power up kicks into the fastboot menu. I can reach the recovery menu, but that's it. Fortunately I can power the device down (press and hold power for exactly 3 sec) but if I try to charge it, I just get the fastboot menu again.
Update: popped the cover and removed and reinstalled the battery. still stuck in fastboot! aaauugghh...
Latest Update: I used packsparseimg again to combine all the system img files, and then fastboot flash system system.combined. Now it just reboots in a continuous loop until I power it off. Something different, but no fixy. Here's my thought: I have the uncompressed system files, now if there's a way to make an img file out of them, that would be great!
jeb.jr said:
Thanks, but Lenovo Smart Assistant only gets to the screen where it prompts me for USB.........
Click to expand...
Click to collapse
I wish that I could be more helpful to you as I only have a limited working knowledge of only a handful of the Lenovo devices.
Maybe someone like @Droidriven or @SubwayChamp could provide some guidance or someone who can help you out a bit further.
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
jeb.jr said:
Thanks, but Lenovo Smart Assistant only gets to the screen where it prompts me for USB debugging, but my tablet won't boot that far. The Device Manager in Windows doesn't come up with a triangle for anything.
However, I tried something else and got myself stuck at the fastboot menu:
There is no flash_all script in the ROM directory, but one was created by typing python createFlashTool.py. Then flash_all.sh, flash_factory.sh, and flash_all_except_storage.sh. I ran flash_all.sh and it said "Missmatching image and device". Oddly enough, flash_all is looking for MSM8953 and I have MSM8909. This must be the correct ROM because it was the one that downloaded from Lenovo Smart Assistant with my tablet number and hardware versions. So, I modified the first line of flash_all, replacing MSM8953 with MSM8909. When I entered ./flash_all.sh this time, it flashed all the img files, giving me OKAY messages over the next several minutes. Update: I suspect there's a bug in here, because it looks like system is just being overwritten 30 times instead of actually being built up.
Now, booting from power up kicks into the fastboot menu. I can reach the recovery menu, but that's it. Fortunately I can power the device down (press and hold power for exactly 3 sec) but if I try to charge it, I just get the fastboot menu again.
Update: popped the cover and removed and reinstalled the battery. still stuck in fastboot! aaauugghh...
Latest Update: I used packsparseimg again to combine all the system img files, and then fastboot flash system system.combined. Now it just reboots in a continuous loop until I power it off. Something different, but no fixy. Here's my thought: I have the uncompressed system files, now if there's a way to make an img file out of them, that would be great!
Click to expand...
Click to collapse
Have you tried fastboot flashing the individual img files(i.e. fastboot flash system, fastboot flash boot, etc..)? It might be easier to flash each img by itself instead of all together.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Have you tried fastboot flashing the individual img files(i.e. fastboot flash system, fastboot flash boot, etc..)? It might be easier to flash each img by itself instead of all together.
Click to expand...
Click to collapse
Yes, I have. Looking at the flash_all.sh script (that was generated earlier with python createFlashTool.py) it's a list of fastboot commands. I ran the script, but I also tried running each command individually. The cyclical reboot stopped, but I'm back to booting only to fastboot mode.
I might also mention this, although it still doesn't work, it might be a lead if someone else wants to investigate:
As mentioned before, the system images are split into 30 image files. Using packsparseimg.exe and its companion imgextract.exe (or something similar) to get the uncompressed system files in their proper directory structure. Those are Windows command-line executables, but then I booted my PC back into Linux, and entered the following (this is partially from memory so it might not be 100%):
dd if=/dev/zero of=~/sys.img bs=1M count=1850 (the 1850 was found by trial and error)
mkfs.ext4 -O '^64bit' -b 4096 sys.img (that means 'not' 64bit, the target device is only 32-bit)
sudo mkdir /mnt/x
sudo mount -t ext4 -o loop sys.img /mnt/x
sudo chmod 777 /mnt/x
cp -r ~/system_folder /mnt/x (where the system folder contains the files to go into the virtual drive)
sudo umount /mnt/x
img2simg sys.img system.img
fastboot flash system system.img
UPDATE: strike this stuff because it didn't work and something else did (see below).
jeb.jr said:
Yes, I have. Looking at the flash_all.sh script (that was generated earlier with python createFlashTool.py) it's a list of fastboot commands. I ran the script, but I also tried running each command individually. The cyclical reboot stopped, but I'm back to booting only to fastboot mode.
I might also mention this, although it still doesn't work, it might be a lead if someone else wants to investigate:
As mentioned before, the system images are split into 30 image files. Using packsparseimg.exe and its companion imgextract.exe (or something similar) to get the uncompressed system files in their proper directory structure. Those are Windows command-line executables, but then I booted my PC back into Linux, and entered the following (this is partially from memory so it might not be 100%):
dd if=/dev/zero of=~/sys.img bs=1M count=1850 (the 1850 was found by trial and error)
mkfs.ext4 -O '^64bit' -b 4096 sys.img (that means 'not' 64bit, the target device is only 32-bit)
sudo mkdir /mnt/x
sudo mount -t ext4 -o loop sys.img /mnt/x
sudo chmod 777 /mnt/x
cp -r ~/system_folder /mnt/x (where the system folder contains the files to go into the virtual drive)
sudo umount /mnt/x
img2simg sys.img system.img
fastboot flash system system.img
Click to expand...
Click to collapse
Usually for large sized images fastboot splits them and send the image by parts to our device, I don´t think that you need to do other additional procedure for this if the image is for your device. Can you upload some screenshot of your folder to see which files it contains and the sizes, also a link to the firmware that you are using.
Try erasing by fastboot cache, userdata, data; try them one by one in this order and try to boot.
Code:
boot.img system_18.img userdata_2.img
cache_1.img system_19.img userdata_3.img
cmnlib.mbn system_1.img userdata_4.img
createFlashTool.py system_20.img userdata_5.img
emmc_appsboot.mbn system_21.img userdata_6.img
gpt_backup0.bin system_22.img userdata_7.img
gpt_both0.bin system_23.img userdata_8.img
gpt_main0.bin system_24.img userdata_9.img
keymaster64.mbn system_25.img vendor_10.img
MD5_DATA.xml system_26.img vendor_11.img
mdtp.img system_27.img vendor_12.img
NON-HLOS.bin system_28.img vendor_13.img
partition_vb.xml system_29.img vendor_14.img
partition.xml system_2.img vendor_15.img
patch0.xml system_30.img vendor_16.img
persist_1.img system_3.img vendor_17.img
prog_emmc_firehose_8909_ddr.mbn system_4.img vendor_18.img
ramdisk.img system_5.img vendor_19.img
ramdisk-recovery.img system_6.img vendor_1.img
rawprogram0.xml.bak system_7.img vendor_20.img
rawprogram_unsparse_upgrade.xml system_8.img vendor_21.img
recovery.img system_9.img vendor_2.img
rpm.mbn tzbsp_no_xpu.mbn vendor_3.img
sampleapp.mbn tz.mbn vendor_4.img
sbl1.mbn userdata_10.img vendor_5.img
sec.dat userdata_11.img vendor_6.img
splash.img userdata_12.img vendor_7.img
system_10.img userdata_13.img vendor_8.img
system_11.img userdata_14.img vendor_9.img
system_12.img userdata_15.img vendor.img
system_13.img userdata_16.img widevine.mbn
system_14.img userdata_17.img zeros_1sector.bin
system_15.img userdata_18.img zeros_33sectors.bin
system_16.img userdata_19.img
system_17.img userdata_1.img
Try erasing by fastboot cache, userdata, data; try them one by one in this order and try to boot.
Click to expand...
Click to collapse
Code:
$ fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.023s]
finished. total time: 0.023s
$ fastboot erase userdata
******** Did you mean to fastboot format this ext4 partition?
erasing 'userdata'...
OKAY [ 0.192s]
finished. total time: 0.192s
$ fastboot erase data
erasing 'data'...
FAILED (remote: Partition table doesn't exist
)
finished. total time: 0.004s
Still boots to fastboot.
Update: I just did something else and I might just have it working. More details to follow....
Before, I had used Packsparseimg from this page:
https://forum.xda-developers.com/android/software-hacking/easy-unpack-systemxx-img-firmware-t3583543
to pack all the system*.img files into one system.raw. The part that I overlooked was this:
img2simg system.raw system.img
file system.img (read the output make sure it's an android image)
fastboot flash system system.img
fastboot reboot
I saw the Lenovo logo, then a big circle with the word "erasing", then the Lenovo logo again, then the logo becomes animated and then back to static. After several minutes of nervous waiting...
Prompts for license agreement! Hooray!
Then something odd: It updated its ROM to the lastest version automatically, and then tried to update to the same version again. When it rebooted, I got the Error with the downed robot. I thought, darn...but it proceeded to boot normally. I'll have to run it through its paces before I declare it working, but I'm glad to be back on track.
Hi, guys...This tablet is making me crazy. It came bootlooping. After i tried wrong firmware and i softbricked it. I flash the right firmware but now i can just go to fastboot mode, recovery mode and edl mode.
I flashed it with different dongles and QFIL. Device state is locked. If I flash the firmware its bootlooping. After flash if ill go to recovery mode and wipe data its going to animated logo the a white bar is going for a while then freezes and the tablet reboots.After this reboot is bootlooping again until ill wipe data. HELP!
Edit: I can't flash through fastboot as tablet is in locked state.
FAILED (remote: Partition flashing is not allowed)
i second that (me too!)
i had re-locked mine and now after doing all these things, still nothing.
quite sad, if anyone would know how to help that would be so nice and i hope nobody else has this problem
:crying:
jeb.jr said:
Before, I had used Packsparseimg from this page:
https://forum.xda-developers.com/android/software-hacking/easy-unpack-systemxx-img-firmware-t3583543
to pack all the system*.img files into one system.raw. The part that I overlooked was this:
img2simg system.raw system.img
file system.img (read the output make sure it's an android image)
fastboot flash system system.img
fastboot reboot
I saw the Lenovo logo, then a big circle with the word "erasing", then the Lenovo logo again, then the logo becomes animated and then back to static. After several minutes of nervous waiting...
Prompts for license agreement! Hooray!
Then something odd: It updated its ROM to the lastest version automatically, and then tried to update to the same version again. When it rebooted, I got the Error with the downed robot. I thought, darn...but it proceeded to boot normally. I'll have to run it through its paces before I declare it working, but I'm glad to be back on track.
Click to expand...
Click to collapse
Could you share those 2 files you got from that link? It doens't seem to available anymore (asks for some password to download I don't have).
I'm in the same shoes as you, would love to get back on track with this tablet!
Thanks in advance!
Edit: Never mind, found it elsewhere!
jeb.jr said:
Before, I had used Packsparseimg from this page:
https://forum.xda-developers.com/android/software-hacking/easy-unpack-systemxx-img-firmware-t3583543
to pack all the system*.img files into one system.raw. The part that I overlooked was this:
img2simg system.raw system.img
file system.img (read the output make sure it's an android image)
fastboot flash system system.img
fastboot reboot
I saw the Lenovo logo, then a big circle with the word "erasing", then the Lenovo logo again, then the logo becomes animated and then back to static. After several minutes of nervous waiting...
Prompts for license agreement! Hooray!
Then something odd: It updated its ROM to the lastest version automatically, and then tried to update to the same version again. When it rebooted, I got the Error with the downed robot. I thought, darn...but it proceeded to boot normally. I'll have to run it through its paces before I declare it working, but I'm glad to be back on track.
Click to expand...
Click to collapse
Hi, I am in the same situation as you. I can only start bootloader and recovery. I can't flash system.img from twrp and when I try to flash it from fastboot it returns the error:
fastboot: error: cannot load 'system.img': Permission denied
Anybody has a hint on how can I solve this?