Related
Device is doesn't react anything. Do not light button. Nothing. Totally bricked. And seems to be totally erased. No data. No bootloader.
Tryed http://forum.xda-developers.com/showthread.php?t=1430038.
Device power up with usb_fix_parts_and_install_fff_twrp and Boot Shorting Trick. Loads TWRP. But what's next?
Tryed to put some firmwares to sdcard and install it - got lots of errors. And nothing.
Kindle Fire utility says:
ADB Status: Online
ADB Rooted: Yes
Boot Status: Unknown
P.S. If i press "reboot" or power down device - going to the beginning(Device is doesn't react anything.)
P.P.S. MB it's not brick, but hardware problem(flash memory died...)?How to check?
If you successfully did usb_fix_parts_and_install_fff_twrp, then either it should leave it with a working bootloader & recovery or your flash is somehow bad.
pokey9000 said:
If you successfully did usb_fix_parts_and_install_fff_twrp, then either it should leave it with a working bootloader & recovery or your flash is somehow bad.
Click to expand...
Click to collapse
It boots into twrp up after usb_fix_parts_and_install_fff_twrp(usb load).
but in terminal window i can see lots of messages: unable to mount /system /data /cache /sdcard.....
Flash is bad?
What can i do with it? Mainboard replacement only?
UPD: /usbboot aboot.bin u-boot.bin; ./fastboot flash boot 6_2_1rootboot.img
fails with:
writing 'boot'...
FAILED (remote: image too large for partition)
UPD2. Strange thing that flashing(fastboot flash...) different file sizes takes almost the same time(256kb sending 0.035s writing 1.231s, 16mb sending 4.111s writing 1.230s).
Does replacing flash memory chip unbrick it?
I tried the guide "How to root Android using Ubuntu" to root my device. It's a matter of overcome absurde limits like the otg, and stuff. My hope was to be using a step by step guide, but that's not completely true, as I sadly discovered. The procedure involves some operations with fastboot to unlock the bootloader and superuser utility to complete the task (already copied the recovery image through fastboot, of course). Now, I didn't realize, nor it was written on that <MOD EDIT-SWEARING> guide, that the su utility had to be put on the internal sdcard BEFORE to start the job.
Thus I started the job, unlocked the bootloader. Then I should have installed the zipfile (the superuser.zip) but not having it on the device, I chose to reboot from the cursor menu. The logic behind this was simple: I have unlocke the bootloader, not erased the os or whatever, thus it shoul restart; I don't have the needed file on the device, thus after a reboot I might copy it over through usb cable, enter again in recovery mode and "install the zip from sdcard".
From then on my device is stuck with the 4 merging/bouncing circles and I *cannot even turn off * it.
I'm a gentoo user, used to read and write guides "in a certain manner", everything was done under gentoo, where I'm now.
Situation now:
Code:
# lsusb
Bus 003 Device 027: ID 18d1:4ee1 Google Inc. Nexus 4 / 10
# fastboot devices
(nothing)
Before my mistake, it was:
Code:
# lsusb
Bus 003 Device 012: ID 18d1:4ee2 Google Inc. Nexus 4 (debug)
or
Code:
Bus 003 Device 014: ID 18d1:4ee0 Google Inc.
and
Code:
# fastboot devices
<myserialnumber-not-publishing-here> fastboot
The exact procedure I followed:
nexus: connected via usb to laptop
nexus: turned on in fastboot mode (hold volume-down + switch)
laptop:
Code:
#fastboot devices
<myserialnumber-not-publishing-here> fastboot
laptop:
Code:
#fastboot oem unlock -s 0a6748e5
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) Unlocking bootloader done!
OKAY [ 36.001s]
finished. total time: 36.001s
nexus: choosen to unlock the bootloader (Yes)
Cannot remember if reboot was requested, if yes i did it
nexus: choosen recovery mode (and stay there)
Code:
# fastboot devices
<myserialnumber-not-publishing-here> fastboot
Code:
# fastboot flash recovery recovery-clockwork-6.0.4.4-deb.img
sending 'recovery' (9108 KB)...
OKAY [ 0.291s]
writing 'recovery'...
OKAY [ 0.348s]
finished. total time: 0.639s
To that point I faced the fact that to continue I should have copied the superuser utility before, and rebooted with the hope to be able to copy it on the device and continue from there on. What has been proven false: I'm now stuck on the bouncing circles, any experiment to hold down the 2/3 buttons in every combinations led to nothing, and "fastboot devices" shows nothing.
only positive point, a little hope: it shows a vendor and product ID via usb:
Code:
# lsusb
Bus 003 Device 027: ID 18d1:4ee1 Google Inc. Nexus 4 / 10
Please help! :crying:
Can you go to recovery?
Edit...
You can turn it off by pressing power+volume down, same for going to fastboot/recovery...
In recovery you can flash via adb sideload...
teddy0209 said:
Can you go to recovery?
Edit...
You can turn it off by pressing power+volume down, same for going to fastboot/recovery...
In recovery you can flash via adb sideload...
Click to expand...
Click to collapse
Thank you for the tip. At first, apparently it was not working, I hadn't written that message in such a panic, otherwise. I said myself: another guy, expert on the subject is saying this... must retry again. Worked.
I fully recovered the device by flashing it under windows with the Nexus Root Toolkit, and was able to definitely root it by following a more updated guide for my linux habitat.
Given that, as a newcomer I'm not supposed to post any link, I'll give easy directions (searchable through google) to other panicked newbies like myself.
Part1: the recovery issue (windows)
The communication under windows isnt' that easy, due to the difficult coexistence/conflict between mtp an adb drivers. For the purpose of flashing we need adb drivers. The best way, shamingly overlooked by me, is to read and try (possibly understanding the concept behind) step1...step4 accessible by mean of the large button in the main windows of root toolkit.
Part2: rooting succesfully (inux)
I found a functional guide, with working links, kindly offered by Gregory Schier. Had I followed that one from the start, the process had gone smooth at first shot.
Let me add, for the linux addicted, a reference to the file-transfer-via-usb-cable topic. In my case it was easy and quick after the very short explanation on MTP found in gentoo wiki.
Thank you for your support :good:
Good for you!!!
There are actually many ways to root our device ,specially with unlocked bootloader...
I just used fatboot OEM unlock I find it easier and most definitely safer toolkits work 99.999 % of the time but when they don't you got yourself a mess
Sent from my Nexus 7 using Tapatalk
Even being a SW and HW developer for a long time, I did had to spend some time to learn all the buzzwords in the "Android rooting" world to recover my Acer A200 tablet, so I'm sharing to save other people time:
My kid tried to guess the gesture password to play in my tablet, I don't know how many times, locking my Acer A200.
I tried google recovery, but the WiFi was off (and I could'nt turn on as the tablet was locked), so I went to the web to find a solution.
Factory reset seemed like a good one (turn device ON pressing power+down vol and switching the orientation key), it boots, then shows 'erasing user data', then hangs with an error:
Code:
Unrecoverable bootloader error (0x19000008)
Now the device is not booting, it get stuck on Acer logo after animation...
So I tried to use ADB to revert the damage, as indicated in one forum, but USB debug mode was not active when I did the factory reset.
ADB installation itself is unecessarily complicated, and as I cannot find a way to list the device in linux+adb ($>platform-tools/adb devices), even adding it to: /etc/udev/rules.d/51-android.rules (obtained with lsusb)
Code:
#Acer
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", ATTR{idProduct}=="337d", MODE="0666", GROUP="plugdev"
It seems android isn't even booting to enable the debug bridge.
So I went to the "fastboot" as last resource (reboot using power+vol.down+switch.toggle), and did the command:
Code:
android-sdk-linux> platform-tools/fastboot oem unlock
I selected the "open lock" image and rebooted, now it shows: Bootloader v0.03.06-ICS(UnlockMode), but hangs in the same point.
So I downloaded a stock image from:
acertabletforum/stock-ics-recovery-image
Burned it using:
Code:
$> platform-tools/fastboot flash recovery /home/gaglocal/backup/acer/stockrecovery.img
sending 'recovery' (6144 KB)...
OKAY [ 1.882s]
writing 'recovery'...
OKAY [ 2.689s]
finished. total time: 4.571s
Same status after reboot.
So I've downloaded 'stock ROMs' from:
4shared/AcerStockROM
But when I try to write using fastboot:
Code:
error: update package has no android-info.txt or android-product.txt
So it seems this ROM is just for SDcard update (ie.: place the zip file as update.zip in the root of a fat32 sdcard, then boot using power+vol.down to perform the recovery process with it) but it fails and shows a dead android with a red triangle in the belly, not funny.
As the error that shows up when trying to issue the factory reset is after "erasing user data" I decided to do:
Code:
platform-tools/fastboot erase data
erasing 'data'...
FAILED (remote: (00030003))
finished. total time: 0.167s
This indicates this tablet has some HW misconfiguration issue. As some posted, I repeated the proccess a few times - no luck.
So I wrote the CWM 5.5.0.4 image from this forum, rebooted, and performed the sdcard recovery method again.
Same dead droid icon...
Finally I decided to erase the flash again, starting with the cache partition, using fastboot:
Code:
platform-tools/fastboot erase cache
erasing 'cache'...
OKAY [ 1.452s]
finished. total time: 1.453s
Finally, rebooted with the "factory reset" again and it worked!
At least i learned a lot without having to go to the Nvidia very-low level flashing process
A200 dead
gabriel_agm said:
Even being a SW and HW developer for a long time, I did had to spend some time to learn all the buzzwords in the "Android rooting" world to recover my Acer A200 tablet, so I'm sharing to save other people time:
My kid tried to guess the gesture password to play in my tablet, I don't know how many times, locking my Acer A200.
I tried google recovery, but the WiFi was off (and I could'nt turn on as the tablet was locked), so I went to the web to find a solution.
Factory reset seemed like a good one (turn device ON pressing power+down vol and switching the orientation key), it boots, then shows 'erasing user data', then hangs with an error:
Code:
Unrecoverable bootloader error (0x19000008)
Now the device is not booting, it get stuck on Acer logo after animation...
So I tried to use ADB to revert the damage, as indicated in one forum, but USB debug mode was not active when I did the factory reset.
ADB installation itself is unecessarily complicated, and as I cannot find a way to list the device in linux+adb ($>platform-tools/adb devices), even adding it to: /etc/udev/rules.d/51-android.rules (obtained with lsusb)
Code:
#Acer
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", ATTR{idProduct}=="337d", MODE="0666", GROUP="plugdev"
It seems android isn't even booting to enable the debug bridge.
So I went to the "fastboot" as last resource (reboot using power+vol.down+switch.toggle), and did the command:
Code:
android-sdk-linux> platform-tools/fastboot oem unlock
I selected the "open lock" image and rebooted, now it shows: Bootloader v0.03.06-ICS(UnlockMode), but hangs in the same point.
So I downloaded a stock image from:
acertabletforum/stock-ics-recovery-image
Burned it using:
Code:
$> platform-tools/fastboot flash recovery /home/gaglocal/backup/acer/stockrecovery.img
sending 'recovery' (6144 KB)...
OKAY [ 1.882s]
writing 'recovery'...
OKAY [ 2.689s]
finished. total time: 4.571s
Same status after reboot.
So I've downloaded 'stock ROMs' from:
4shared/AcerStockROM
But when I try to write using fastboot:
Code:
error: update package has no android-info.txt or android-product.txt
So it seems this ROM is just for SDcard update (ie.: place the zip file as update.zip in the root of a fat32 sdcard, then boot using power+vol.down to perform the recovery process with it) but it fails and shows a dead android with a red triangle in the belly, not funny.
As the error that shows up when trying to issue the factory reset is after "erasing user data" I decided to do:
Code:
platform-tools/fastboot erase data
erasing 'data'...
FAILED (remote: (00030003))
finished. total time: 0.167s
This indicates this tablet has some HW misconfiguration issue. As some posted, I repeated the proccess a few times - no luck.
So I wrote the CWM 5.5.0.4 image from this forum, rebooted, and performed the sdcard recovery method again.
Same dead droid icon...
Finally I decided to erase the flash again, starting with the cache partition, using fastboot:
Code:
platform-tools/fastboot erase cache
erasing 'cache'...
OKAY [ 1.452s]
finished. total time: 1.453s
Finally, rebooted with the "factory reset" again and it worked!
At least i learned a lot without having to go to the Nvidia very-low level flashing process
Click to expand...
Click to collapse
Could you list the steps you took for the last successful attempt?
I tried all method but stuck at recovery.
Also does following;
"fastboot flash:raw boot boot.img-kernel boot.img-ramdisk.gz
fastboot flash recovery recovery.img"
unable to recover stock.
My bootloader is unlocked
Before Rooting ROM:
Kernel version: 2.6.39.4+
Image version : Acer_AV041_A200_RV10RC02_WW_GEN1
Build No. : Acer_AV041_A200_1.076.00_WW_GEN1
Hello,
i have big problem wiht my D855. I'm trying to install recovery on my device via fastboot, because flashify method failed resulting in lack of recovery on my phone... When i enter "the place where recovery should be" boot certification error shows up and the only way to get rid of it is to re-insert the battery. Unfortunatelly fastboot is not working somehow. Command where it stuck while flashing says:
Code:
C:\adb\fastboot flash recovery reco.img
target reported max download size of 214743648 bytes
sending 'recovery' (15382 KB)...
OKAY [ 0.557s]
writing 'recovery'...
device:
Code:
[132740] fastboot: flash:recovery
Ive been already waiting about 40 minutes for this process to continue but of course nothing happened. After removing USB cable it says:
Code:
FAILED (status read failed (Too many links))
finished. total time: 649.362s
Other commands also do not work, they crash almost the same way but with sh.. i called "three dot bug"
Code:
C:\Users\Dom\Desktop\2>fastboot flashing unlock
...
It even dont reboot after typing:
Code:
C:\Users\Dom\Desktop\2>fastboot reboot-bootloader
rebooting into bootloader...
I have tried different cables, USB ports, different PC. I have lates LG drivers installed. What can I do. My OS is running but has many issues like not working wifi, crashing camera or random reboots (on new battery), so I cant use this phone anymore. It is impossible to revert it back to factory because recovery, which is used for this process is not working, so do fastboot...
Please help, I'm not android expert (and poor english user).
Cheers
Flash the latest TWRP onto it, it should let you boot. I had this problem a few days ago on a samsung tablet. I used odin on that. But you are going to have to match up the TWRP version and the android version you are running.
If you get TWRP working you wont have any problems, you can fix everything from there. Flash fulmics, unroot, what ever you want. Wipe the whole device ect. Make your goal trying to get TWRP on it.
Well, the problem is that I'm trying to flash TWRP now, it is the "reco.img" file, because I was trying to resolve the recovery instalation problem by changing name of file, which could be a problem somehow.
I found adb method to flash recovery:
Code:
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/yourrecovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Will it work? ADB is working fine, I already tried similar method when removing and reinstalling laf.
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?