Database Users

[Q] Bootloop after flashing, TWRP not available..

Hello guys,
Frank is writing. Sorry for disturbing, but i´m in big trouble right now. I made a Factory reset, wipe Dalvik etc. and flashed the PA Aosp Mako 4.0 + latest Gapps.. Nothing special so far, but now my Nexus is still in a bootloop. If i go to the recovery mode, i have no access to TWRP just have the possibility to choose between Start, Start bootloader, Power off, or Recovery Mode. But if i go to the recovery mode the bugdroid is there and nothing happens further. After connecting the device to my mac there is a message on the screen that it´s in download mode?! i didn´t seen this before.. So if you have any solution, it would be great. a factory reset to if possible or even necessary.
Right now I am at my wits end. May someone has an advice for me what to do? i can´t imagine christmas without my beloved smartphone.. ;(
Thanks for your attention!
cheers
Frank

You need fastboot working on your computer, not sure of the exact steps for a mac, but if you download the Android SDK it will be in there. Then you can directly flash a factory image for your phone from the fastboot screen. (The one you describe with start, start bootloader, etc)
You can download the factory images here https://developers.google.com/android/nexus/images#occam
Android sdk for mac http://dl.google.com/android/android-sdk_r22.3-macosx.zip

hey.. thank you for your reply. i downloaded the required files but how to get the access with terminal when it´s still not possible to start the phone? If i type in ./adb devices in terminal just following popped up but nothimg else:
-bash: /Users/frankherrmann/Desktop/adt-bundle-mac-x86_64-20131030: is a directory
do u know what to do now?

At the dead android screen, hold the power button and press vol+. Does it get you to stock recovery?

unfortunately nothing happens the screen turns off, that´s all... ;(

You should try flashing a stock 4.4.2 occam image using fastboot. This would return you to stock and you can then root and install TWRP or CWM.

endxpen tyrants
ok, thanks...meanwhile i did a factory reset with in the recovery mode, but after reboot the same thing happens, still bootloop.. now i just downloaded the adt bundle with sdk inside and the latest factory image. but anyway, it seems that i can´t get the access to the phone. if i go in the adt folder and use the command adb services in the terminal my device will not be recognized.
Frank-iMac:adt-bundle-mac frankherrmann$ ./adb devices
List of devices attached
Frank-iMac:adt-bundle-mac frankherrmann$
Do i type in something wrong? maybe it´s just a thinking error by myself
thanks againfor your help!

FrankHPunkt said:
ok, thanks...meanwhile i did a factory reset with in the recovery mode, but after reboot the same thing happens, still bootloop.. now i just downloaded the adt bundle with sdk inside and the latest factory image and put it in the same folder that i named as adroid tools. i got the access to the folder and after type in the command ./fastboot devices my devices has been recognized and the number too. but if i try to flash the stock image it will not work. i typed in ./fastboot flash and the image name but the failure message -bash: ./flash: No such file or directory
so... i suggest that it´s been just a problem that i typed not the correct command, isn´it?
Franks-MacBook-Pro:Android Tools leherman$ ./fastboot flash /Users/leherman/Desktop/android\ tools/image-occam-kot49h.zip
unknown partition '/Users/leherman/Desktop/android tools/image-occam-kot49h.zip'
error: cannot determine image filename for '/Users/leherman/Desktop/android tools/image-occam-kot49h.zip'
Franks-MacBook-Pro:Android Tools leherman$
Click to expand...
Click to collapse

Sorry, I can't help you with flashing on Mac. Do you have access to a PC?

FrankHPunkt said:
FrankHPunkt said:
ok, thanks...meanwhile i did a factory reset with in the recovery mode, but after reboot the same thing happens, still bootloop.. now i just downloaded the adt bundle with sdk inside and the latest factory image and put it in the same folder that i named as adroid tools. i got the access to the folder and after type in the command ./fastboot devices my devices has been recognized and the number too. but if i try to flash the stock image it will not work. i typed in ./fastboot flash and the image name but the failure message -bash: ./flash: No such file or directory
so... i suggest that it´s been just a problem that i typed not the correct command, isn´it?
Click to expand...
Click to collapse
Yes you got 2 options,run the flash-all script or flash the files manually for example typing fastboot flash recovery recovery.img or fastboot flash radio radio.img, you didn't specified the partition to flash
Click to expand...
Click to collapse

Hey Frederico,
thanks for your reply i did it as you told me and typed this in terminal : as you can see something should work, but it was not possible to flash the image.
Franks-MacBook-Pro:android tools leherman$ ./fastboot flash radio-mako-m9615a-cefwmazm-2.0.1700.98.img radio-mako-m9615a-cefwmazm-2.0.1700.98.img
sending 'radio-mako-m9615a-cefwmazm-2.0.1700.98.img' (45537 KB)...
OKAY [ 1.715s]
writing 'radio-mako-m9615a-cefwmazm-2.0.1700.98.img'...
FAILED (remote: partition table doesn't exist)
finished. total time: 1.718s
Franks-MacBook-Pro:android tools leherman$ ./fastboot flash image-occam-kot49h.zip image-occam-kot49h.zip
sending 'image-occam-kot49h.zip' (429746 KB)...
OKAY [ 15.845s]
writing 'image-occam-kot49h.zip'...
FAILED (remote: partition table doesn't exist)
finished. total time: 15.848s
do u have an idea whats still not right. Seems to be on the right way!
thank you very much so far!
Federico_96 said:
FrankHPunkt said:
Yes you got 2 options,run the flash-all script or flash the files manually for example typing fastboot flash recovery recovery.img or fastboot flash radio radio.img, you didn't specified the partition to flash
Click to expand...
Click to collapse
Click to expand...
Click to collapse

FrankHPunkt said:
Hey Frederico,
thanks for your reply i did it as you told me and typed this in terminal : as you can see something should work, but it was not possible to flash the image.
Franks-MacBook-Pro:android tools leherman$ ./fastboot flash radio-mako-m9615a-cefwmazm-2.0.1700.98.img radio-mako-m9615a-cefwmazm-2.0.1700.98.img
sending 'radio-mako-m9615a-cefwmazm-2.0.1700.98.img' (45537 KB)...
OKAY [ 1.715s]
writing 'radio-mako-m9615a-cefwmazm-2.0.1700.98.img'...
FAILED (remote: partition table doesn't exist)
finished. total time: 1.718s
Franks-MacBook-Pro:android tools leherman$ ./fastboot flash image-occam-kot49h.zip image-occam-kot49h.zip
sending 'image-occam-kot49h.zip' (429746 KB)...
OKAY [ 15.845s]
writing 'image-occam-kot49h.zip'...
FAILED (remote: partition table doesn't exist)
finished. total time: 15.848s
do u have an idea whats still not right. Seems to be on the right way!
thank you very much so far!
Click to expand...
Click to collapse
The right command is ./fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.98.img, so it is ./fastboot flash <generic name of partition> <exact name of the file> hope this will work, but my suggestion is to run the flash-all script,it will do it authomatically for you, if you want do it manually,here at step D there are all the commands

Thanks a lot, you made may day! the phone is rebooting....
merry christmas!
cheers
Frank

[Solved] Bricked and can't write system

I erased everything in an attempt to unbrick it but that was a mistake. What I have tried and results:
-twrp recovery tried to install the latest stock firmware but got error with mounting system.
-fastboot flash update update.zip didn't solve it
-fastboot seperatly flashing each image, extracted by the update extractor tool. Result:
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (451240 KB)...
OKAY [ 23.882s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 23.958s​-fastboot -w to reformat and try again. Result:
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.012s​OEM is unlocked, I have tried updating from the SD and using the three buttons but I get the wrong format error. Downloaded the MM version as well but I get the incompatible error. Can't download from the erecovery or Hi-Suite. Help please

Have you tried flashing the original oeminfo and then installing with dload? Or maybe try fastboot update method

d0nefufe said:
Have you tried flashing the original oeminfo and then installing with dload? Or maybe try fastboot update method
Click to expand...
Click to collapse
Which original one though? I've been trying and downloaded any Full firmware I could find using a firmware finder, for my VNS-L31 but using the force update method in download so far all of them return an error: Incompatible with current version. I have also tried the fastboot update and separately flashing each file in the update.app . None work so far. I keep trying.

Badwolf9 said:
Which original one though? I've been trying and downloaded any Full firmware I could find using a firmware finder, for my VNS-L31 but using the force update method in download so far all of them return an error: Incompatible with current version. I have also tried the fastboot update and separately flashing each file in the update.app . None work so far. I keep trying.
Click to expand...
Click to collapse
If you're on Nougat, try flashing it's files through fastboot. It worked for me, MM system.img gave me an error, but nougat flashed fine.

I believe ur in nougat beta... Just flash oem info and flash again the nougat from there you can start again and downgrade peacefully

your bootloader is locked

Sh0m1 said:
If you're on Nougat, try flashing it's files through fastboot. It worked for me, MM system.img gave me an error, but nougat flashed fine.
Click to expand...
Click to collapse
Thank you! I followed the instructions here with a slight variation. Because trying to install the update.zip file always gave me errors I extracted the update.APP with the update extractor tool and flashed cache,system,boot with fastboot. Then I opened the custom recovery, installed the other zip file and continued as instructed.

mjz2cool said:
your bootloader is locked
Click to expand...
Click to collapse
No it wasn't. This was my first thought as well.

Badwolf9 said:
No it wasn't. This was my first thought as well.
Click to expand...
Click to collapse
how did you check if it was unlocked? if it says so in fastboot mode it can be incorrect, even when you relock the bootloader it still says unlocked

mjz2cool said:
how did you check if it was unlocked? if it says so in fastboot mode it can be incorrect, even when you relock the bootloader it still says unlocked
Click to expand...
Click to collapse
fastboot oem device-info
Also if it was locked I wouldn't be able to flash anything.

d0nefufe said:
Have you tried flashing the original oeminfo and then installing with dload? Or maybe try fastboot update method
Click to expand...
Click to collapse
where can I find the oeminfo file?

islandman75 said:
where can I find the oeminfo file?
Click to expand...
Click to collapse
This is the L21 - SingleSIM:
https://www.dropbox.com/s/97uad8vc3pwppnq/oeminfoORIGINAL.img?dl=0
And the L21 - DualSIM:
https://www.dropbox.com/s/fq99atzszg2sq1y/oeminfoDUAL.img?dl=0

How to get OTA update with my tablet rooted? My tablet is yoga tab 3 plus.

My tablet is Lenovo yoga tab 3 plus, I have rooted my tablet, and after downloading the update, an error occured, and here is the log:
Supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Source: Lenovo/YT-X703F/YT-X703F:6.0.1/S100/YT-X703F_S000691_161121_PRC:user/release-keys
Target: Lenovo/YT-X703F/YT-X703F:6.0.1/S100/YT-X703F_S000728_170211_PRC:user/release-keys
Verifying current system...
"EMMC:/dev/block/bootdevice/by-name/boot:31655208:db7b430aac30b324daddf17bcdb14201a6468700:31655208:4de06d70f69d35ffa0a0aa0c6975385a3c937030" has unexpected contents.
E:Error in @/cache/recovery/block.map
(Status 7)
Installation abroated.
E:failed to mount /data (Invaild argument)
I think if we can bypass verification, we can install update while the device is rooted.
Any can help us?

zkn1021 said:
My tablet is Lenovo yoga tab 3 plus, I have rooted my tablet, and after downloading the update, an error occured, and here is the log:
Supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Source: Lenovo/YT-X703F/YT-X703F:6.0.1/S100/YT-X703F_S000691_161121_PRC:user/release-keys
Target: Lenovo/YT-X703F/YT-X703F:6.0.1/S100/YT-X703F_S000728_170211_PRC:user/release-keys
Verifying current system...
"EMMC:/dev/block/bootdevice/by-name/boot:31655208:db7b430aac30b324daddf17bcdb14201a6468700:31655208:4de06d70f69d35ffa0a0aa0c6975385a3c937030" has unexpected contents.
E:Error in @/cache/recovery/block.map
(Status 7)
Installation abroated.
E:failed to mount /data (Invaild argument)
I think if we can bypass verification, we can install update while the device is rooted.
Any can help us?
Click to expand...
Click to collapse
So the easiest way is to restore the boot and system partition to the original S000725 version using fastboot and then install the update, but only if you are on S000725 now. If you are sure that you didn't modify the system partition (any root app installed system less) then the boot partition is sufficient. Flashing these two partitions will not delete your apps and settings.
Here is what to do:
Download the factory image S000725 for your tablet (see first post of TWRP thread) and make sure your current software version is S000725
Extract it and get the boot.img and system.img files
restart into fastboot mode (e.g. via adb reboot bootloader, or restart the tablet with volume up key pressed)
Execute fastboot on your PC connected to the tablet with the following command:
Code:
fastboot flash boot boot.img
If the system partition was modified you will have to do the same for system
Code:
fastboot flash system system.img
If TWRP is flashed you also have to restore the recovery partition
Code:
fastboot flash recovery recovery.img
You can also install the factory image via the supplied flash tool. But we're not 100% sure it is safe wrt. DRM keys
Sometimes the flashing of such large partitions as the system partitions can fail in which case you have to do it again until it works. If you run into a bootloop after flashing the boot.img your system partition is not original and you have to flash the system.img again
EDIT: Ok I see you are on S000691 in which case you need a factory image of that version

matshias said:
So the easiest way is to restore the boot and system partition to the original S000725 version using fastboot and then install the update, but only if you are on S000725 now. If you are sure that you didn't modify the system partition (any root app installed system less) then the boot partition is sufficient. Flashing these two partitions will not delete your apps and settings.
Here is what to do:
Download the factory image S000725 for your tablet (see first post of TWRP thread) and make sure your current software version is S000725
Extract it and get the boot.img and system.img files
restart into fastboot mode (e.g. via adb reboot bootloader, or restart the tablet with volume up key pressed)
Execute fastboot on your PC connected to the tablet with the following command:
Code:
fastboot flash boot boot.img
If the system partition was modified you will have to do the same for system
Code:
fastboot flash system system.img
You can also install the factory image via the supplied flash tool. But we're not 100% sure it is safe wrt. DRM keys
Sometimes the flashing of such large partitions as the system partitions can fail in which case you have to do it again until it works. If you run into a bootloop after flashing the boot.img your system partition is not original and you have to flash the system.img again
EDIT: Ok I see you are on S000691 in which case you need a factory image of that version
Click to expand...
Click to collapse
Thank you！
I'm wondering whether I have to root again after restoring the boot and system partitions.

I got the OTA update package, can I flash it directly via recovery? I have rooted my tablet.

zkn1021 said:
Thank you！
I'm wondering whether I have to root again after restoring the boot and system partitions.
Click to expand...
Click to collapse
zkn1021 said:
I got the OTA update package, can I flash it directly via recovery? I have rooted my tablet.
Click to expand...
Click to collapse
Well first unroot by flashing boot and system, then install update in Lenovo recovery. Yes it's possible to do that. Then when the update installed successfully you can root again with TWRP and SuperSU.

brothers, I skipped system verifying by editing updater-script, but the OTA still failed because signature verifying failed.
Anyone knows how to skip signature verifying?
If we can skip that, we may install ota update package manually while the device is rooted.

matshias said:
the easiest way is to restore the boot and system partition .
...
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
hi! how can i make a backup of my currently partitions (before rooting and so on) to make possible flash them back with "fastboot flash ..."?
is the command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
makes the image compatible with "fastboot flash ..." command? or i have to convert it somehow?
P.s. yes i know about restoring with command "dd if=/sdcard1/system.img of=/dev/block/bootdevice/by-name/system", but i want to have other ways to retreat

DGolovin said:
hi! how can i make a backup of my currently partitions (before rooting and so on) to make possible flash them back with "fastboot flash ..."?
is the command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
makes the image compatible with "fastboot flash ..." command? or i have to convert it somehow?
P.s. yes i know about restoring with command "dd if=/sdcard1/system.img of=/dev/block/bootdevice/by-name/system", but i want to have other ways to retreat
Click to expand...
Click to collapse
In TWRP (via adb or TWRP terminal) you can use the command that you listed to make backups of existing partitions. The system partition is a bit special though. The dd command will give you the raw partition image. Fastboot, however, expects the system partition in sparse format. To convert you need the tool "img2simg".
The other partitions are expected in raw format by fastboot.
Unless you have a special firmware version you don't have to create these backups since we have factory images which contain exactly these partition images. Boot, recovery and system partitions are the same for all devices with the same device variant and software version.

matshias said:
In TWRP (via adb or TWRP terminal) you can use the command that you listed to make backups of existing partitions. The system partition is a bit special though. The dd command will give you the raw partition image. Fastboot, however, expects the system partition in sparse format. To convert you need the tool "img2simg".
The other partitions are expected in raw format by fastboot.
Unless you have a special firmware version you don't have to create these backups since we have factory images which contain exactly these partition images. Boot, recovery and system partitions are the same for all devices with the same device variant and software version.
Click to expand...
Click to collapse
Thanks for eхplain. I have downloaded your backups of 734th firmware for Lenovo Yoga 3 Plus F already but new knowlege will not be redundant

Hello,
Tried "adb reboot bootloader" but it only stuck with Lenovo logo. So I tried to flash boot.img using app.
Now stuck with boot loop. Manage to go into Recovery Mode - Is there any way I could restore anything from Recovery? .zip
Thank you

Hi guys,
I got n OTA update. I only did the root process from https://forum.xda-developers.com/th...ta-twrp-root-disable-encryption-yoga-t3538017 before.
After doing the "fastboot flash boot boot.img" to allow the OTA update from this thread, I got a reboot loop (soft brick right?) when I try to go to recovery, i got this
https://photos.google.com/share/AF1QipMLfvQnTcKCr4lJ6ImnPHsb9_s5aR_ERj_k_oIuhhg_k6aGD2yNen8H9y7tdhPLOA?key=T2FYdmZSZ204OFczejB0dXpGOGlRdG1aNXBvckln
any help? sadly, I'm a noob u.u
thxs

NtahX said:
Hello,
Tried "adb reboot bootloader" but it only stuck with Lenovo logo. So I tried to flash boot.img using app.
Now stuck with boot loop. Manage to go into Recovery Mode - Is there any way I could restore anything from Recovery? .zip
Thank you
Click to expand...
Click to collapse
The fastboot mode (bootloader) only shows the Lenovo logo. So this is expected. If you get a bootloop you also have to flash system.img via fastboot. So do the adb reboot bootloader again and use fastboot tool on the PC to do the flashing
---------- Post added at 10:51 PM ---------- Previous post was at 10:47 PM ----------
dasinflames said:
Hi guys,
I got n OTA update. I only did the root process from https://forum.xda-developers.com/th...ta-twrp-root-disable-encryption-yoga-t3538017 before.
After doing the "fastboot flash boot boot.img" to allow the OTA update from this thread, I got a reboot loop (soft brick right?) when I try to go to recovery, i got this
https://photos.google.com/share/AF1QipMLfvQnTcKCr4lJ6ImnPHsb9_s5aR_ERj_k_oIuhhg_k6aGD2yNen8H9y7tdhPLOA?key=T2FYdmZSZ204OFczejB0dXpGOGlRdG1aNXBvckln
any help? sadly, I'm a noob u.u
thxs
Click to expand...
Click to collapse
Same thing. Your system partition is not original that's why you have the boot loop. You have to flash the original version via fastboot.

matshias said:
The fastboot mode (bootloader) only shows the Lenovo logo. So this is expected. If you get a bootloop you also have to flash system.img via fastboot. So do the adb reboot bootloader again and use fastboot tool on the PC to do the flashing
---------- Post added at 10:51 PM ---------- Previous post was at 10:47 PM ----------
Same thing. Your system partition is not original that's why you have the boot loop. You have to flash the original version via fastboot.
Click to expand...
Click to collapse
Code:
c:\adb>fastboot flash system system_yt_x703f_s000734.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.626s]
sending sparse 'system' (516880 KB)...
OKAY [ 18.443s]
writing 'system'...
OKAY [ 7.726s]
sending sparse 'system' (507198 KB)...
OKAY [ 18.163s]
writing 'system'...
OKAY [ 7.812s]
sending sparse 'system' (511833 KB)...
OKAY [ 18.332s]
writing 'system'...
OKAY [ 7.876s]
sending sparse 'system' (514911 KB)...
OKAY [ 18.410s]
writing 'system'...
OKAY [ 7.345s]
sending sparse 'system' (514937 KB)...
OKAY [ 18.282s]
writing 'system'...
OKAY [ 7.369s]
sending sparse 'system' (511997 KB)...
OKAY [ 18.328s]
writing 'system'...
OKAY [ 22.033s]
sending sparse 'system' (156572 KB)...
OKAY [ 5.703s]
writing 'system'...
OKAY [ 17.717s]
finished. total time: 194.195s
c:\adb>fastboot flash recovery recovery_yt_x703f_s000734.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.078s]
writing 'recovery'...
OKAY [ 0.829s]
finished. total time: 2.907s
Since I already flashed boot.img yesterday, continue with system & recovery. I didn't know that Download mode will only shows Lenovo logo. Normally it will shows what running on the background. Did as told and manage to recover. Sadly I've wiped cache & data in Recovery yesterday, now back to square 1. But at least better than bricked device. Thank you.

matshias said:
The fastboot mode (bootloader) only shows the Lenovo logo. So this is expected. If you get a bootloop you also have to flash system.img via fastboot. So do the adb reboot bootloader again and use fastboot tool on the PC to do the flashing
---------- Post added at 10:51 PM ---------- Previous post was at 10:47 PM ----------
Same thing. Your system partition is not original that's why you have the boot loop. You have to flash the original version via fastboot.
Click to expand...
Click to collapse
the only way that my tablet can to be recognized in my computer is with sideload. I'll try with that method.
thxs!!
PS: I used at the end the Multiflashtool and now my tablet works perfectly
if someone has the parallel problem, here is the solution: http://www.mediafire.com/download/58upc51o93ux2f4/Archivo+StargetDawn.rar
just install and execute the multiflash program.
greetings

matshias said:
So the easiest way is to restore the boot and system partition to the original S000725 version using fastboot and then install the update, but only if you are on S000725 now. If you are sure that you didn't modify the system partition (any root app installed system less) then the boot partition is sufficient. Flashing these two partitions will not delete your apps and settings.
Here is what to do:
Download the factory image S000725 for your tablet (see first post of TWRP thread) and make sure your current software version is S000725
Extract it and get the boot.img and system.img files
restart into fastboot mode (e.g. via adb reboot bootloader, or restart the tablet with volume up key pressed)
Execute fastboot on your PC connected to the tablet with the following command:
Code:
fastboot flash boot boot.img
If the system partition was modified you will have to do the same for system
Code:
fastboot flash system system.img
If TWRP is flashed you also have to restore the recovery partition
Code:
fastboot flash recovery recovery.img
You can also install the factory image via the supplied flash tool. But we're not 100% sure it is safe wrt. DRM keys
Sometimes the flashing of such large partitions as the system partitions can fail in which case you have to do it again until it works. If you run into a bootloop after flashing the boot.img your system partition is not original and you have to flash the system.img again
EDIT: Ok I see you are on S000691 in which case you need a factory image of that version
Click to expand...
Click to collapse
I'm sorry to bother you again.
Someone made a backup via twrp, and got these files:
boot.emmc.win
boot.emmc.win.md5
recovery.log
system.ext4.win000
system.ext4.win000.md5
system.ex4.win001
system.ext4.win001.md5
system.info
How to continue with these files?
Thank you!

zkn1021 said:
I'm sorry to bother you again.
Someone made a backup via twrp, and got these files:
boot.emmc.win
boot.emmc.win.md5
recovery.log
system.ext4.win000
system.ext4.win000.md5
system.ex4.win001
system.ext4.win001.md5
system.info
How to continue with these files?
Thank you!
Click to expand...
Click to collapse
Well it seems you have to request the backup again. system.ext4 is a file based backup. This will not restore to a 100% original system image. The person who provided this for you has to run it again and select "system image" instead of "system" when creating the backup. This will then be a binary copy of the system partition.
Once you have that you should create a backup using TWRP on your own device with boot and system image selected onto an external SD card. Don't forget to boot TWRP with system left read only. Then you replace the *.win* files (also the .md5 files) on you SD card with ones you get from this person files. Then reinsert the SD card into the tablet and select restore in TWRP. Then the two partitions should be original if the person you got them from didn't modify it somehow.
I am not sure which format TWRP uses to store these partition images but if the above doesn't work we'll figure out how to extract it.

matshias said:
Download the factory image S000725 for your tablet (see first post of TWRP thread) and make sure your current software version is S000725
EDIT: Ok I see you are on S000691 in which case you need a factory image of that version
Click to expand...
Click to collapse
hello iam on s000689 and i have a hard time trying to find that recovery image... can i just you S000725 and then not have OTA updates?

VNS-L31 P9 Lite Bricked

Hi here !
I own a VNS-L31
Bootloader is unlocked
I tried to update to Android 7, but I bricked it because of the recovery was a TWRP for Android 6
Now, the device is bricked to the loading screen.
So, I tried with fastboot to flash files.
fastboot flash boot BOOT.img -> OK
fastboot flash recovery RECOVERY.img -> OK
but :
fastboot flash system SYSTEM.img -> I get the same error :
target reported max download siez of 471859200 bytes
sending sparse 'system' <451240 KB>
OKAY ( 20.390s)
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. Total time: 20.720s
Click to expand...
Click to collapse
I tried with the toolkit to flash the 4 images, but I always get the same answer : no device detected! blabla
However, the drivers are installed. I installed HISuite before all these...
What I can do now with myt brick :
boot to fastboot mode
boot to eRecovery (but no way to download anything, I doesn't work...)
nothing else.
I read this forum and all posts relative to P9 Lite brick, but I can't do anything until the SYSTEM.img file is written to the phone
Thank you for reading me

1. Download adb drivers...search on Google adb all in one installer it's on xda forums.
2. Download adb minimal package also search on Google and it's also on xda.
Try those 2first .

Kcetin20 said:
1. Download adb drivers...search on Google adb all in one installer it's on xda forums.
2. Download adb minimal package also search on Google and it's also on xda.
Try those 2first .
Click to expand...
Click to collapse
Hi
ADB drivers are already installed, by the method you given.
I can use ADB, the P9 is recognized.
The problem occurs always and only with the toolkit. My device is not recognized with it...
I can flash recovery, I was able to use dload, I pushed a Nougat firmware, and now, I have a TWRP recovery, but the phone is always blocked.
With the recovery, I noticed another problem. As you can see on the picture, partitions cannot be mounted. I don't know why...
https://goo.gl/photos/BPb6AHnDMD11gXSS6

Gnubox said:
Hi
ADB drivers are already installed, by the method you given.
I can use ADB, the P9 is recognized.
The problem occurs always and only with the toolkit. My device is not recognized with it...
I can flash recovery, I was able to use dload, I pushed a Nougat firmware, and now, I have a TWRP recovery, but the phone is always blocked.
With the recovery, I noticed another problem. As you can see on the picture, partitions cannot be mounted. I don't know why...
https://goo.gl/photos/BPb6AHnDMD11gXSS6
Click to expand...
Click to collapse
This device is really hard to flash some firmwares....
if you're out of options you can try to use DC Phoenix it cost 10-15$ i believe : https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial

I would try to re-flash Nougat by the dload method first. You could also try to flash VNS-L31C432B160. For some reason it is more readily accepted by a bricked VNS-L31 than other full firmware.
If that fails, I'd resort to DC Phoenix.

Partition table doesn't exist

Hi, I try to flash a new boot.img, and it's printed the message Partition table doesn't exit.
Anyone have a solution for this.
Now, my mobile have a infinite bootloop
Thanks

Which boot.img did you try to flash?

cafernan said:
Hi, I try to flash a new boot.img, and it's printed the message Partition table doesn't exit.
Anyone have a solution for this.
Now, my mobile have a infinite bootloop
Thanks
Click to expand...
Click to collapse
Also show which command exactly did you use. "Partition table doesn't exist" error is shown when you try to flash partition which..doesn't exist - usually a typo in command. Also there are some "fake" Mi A1 being sold (Mi 5x with A1 ROM), verify that you have really A1 here https://www.mi.com/verify/#imei_en

Hey man Mi A1 has dual partition. You have to specify which partition you are flashing.
fastboot flash boot_a boot.img
(boot_a or boot_b depending upon your current slot)

mearjunsha said:
Hey man Mi A1 has dual partition. You have to specify which partition you are flashing.
fastboot flash boot_a boot.img
(boot_a or boot_b depending upon your current slot)
Click to expand...
Click to collapse
I was getting that error trying to flash my own personal backed up boot.img. I was using the
Code:
fastboot flash boot_a boot.img
command as well as trying slot b.
I got jack of it and just used MiFlash and flashed the rom without overwriting storage. Problem solved.

ludditefornow said:
I was getting that error trying to flash my own personal backed up boot.img. I was using the
Code:
fastboot flash boot_a boot.img
command as well as trying slot b.
I got jack of it and just used MiFlash and flashed the rom without overwriting storage. Problem solved.
Click to expand...
Click to collapse
thanks, problem solved

Need help also, where do you fill in code (fastboot flash boot_a boot.img)?
Can someone explain the given answer above with the two partition?

juby2 said:
Need help also, where do you fill in code (fastboot flash boot_a boot.img)?
Can someone explain the given answer above with the two partition?
Click to expand...
Click to collapse
wait for this answer too,

juby2 said:
Need help also, where do you fill in code (fastboot flash boot_a boot.img)?
Can someone explain the given answer above with the two partition?
Click to expand...
Click to collapse
What do mean, adb&fastboot ? You need it if you don't
want to flash with miflash or twrp.
https://forum.xda-developers.com/showthread.php?t=2317790
The mi a1 has two partition a and b, if you want to flash separately, but you don't have to or what is your question exactly ?
Edit: on one partition a or b you use your current system, the other one is for updating in the background like ota update.

I have custom ROM installed but after using OTA update i lost TWRP, now i have to flash it to certain partition A or B.
How do i know to which partition to flash it, A or B and how to check for that ???

i have that type of problem too
when i write fastboot system system.img it says
C:\platform-tools>fastboot flash system system.img
Sending sparse 'system' 1/38 (131056 KB) OKAY [ 5.453s]
Writing 'system' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed

godsavesmeeverytime said:
i have that type of problem too
when i write fastboot system system.img it says
C:\platform-tools>fastboot flash system system.img
Sending sparse 'system' 1/38 (131056 KB) OKAY [ 5.453s]
Writing 'system' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
Click to expand...
Click to collapse
Did you figure out how to solve it?

Zato83 said:
Did you figure out how to solve it?
Click to expand...
Click to collapse
no but i did recovered my phone using spflash you can do it too

godsavesmeeverytime said:
no but i did recovered my phone using spflash you can do it too
Click to expand...
Click to collapse
hell yeah hahahaha I get recover it back, but my goal gonna figure out how Install TWRP on my phone, thank for reply

wh
Zato83 said:
hell yeah hahahaha I get recover it back, but my goal gonna figure out how Install TWRP on my phone, thank for reply
Click to expand...
Click to collapse
hey where I can get the scatter-loading file for mi a1