Database Develop

[Recovery] ClockworkMod - TF701T Proxy Thread

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
THIS IS A PROXY THREAD Creator and Maintainer is pershoot
This is CWM for the ASUS Transformer Pad (TF701T – Macallan).
-You must be unlocked (use ASUS’s unlock tool to perform this)
-You must be on 10.26.1.18 bootloader (updating to ASUS’s latest 4.3 release will install this)
For complete Info and Download: VISIT HERE
***Once there, check out the Recent Entries on the right side of the page for latest updates***
-Unlock your device using the ASUS Unlock tool.
-Boot in once and execute: adb reboot bootloader
Fastboot:
To boot the recovery:
fastboot boot recovery.img
To permanently flash the recovery:
fastboot flash recovery recovery.img
Source:
https://github.com/pershoot/android_device_asus_tf701t
https://github.com/pershoot/android_kernel_asus_tf701t
https://github.com/CyanogenMod/android_bootable_recovery
Creator and Maintainer:
@pershoot

Video Tutorial
Video Tutorial Thanks @wwjoshdew

Ah just saw screenies. Nice job pershoot.
Why is the version still 6.0.4.6?

CWM 6.0.4.7
OP Updated

Feb/2 OP updated

Small question: my device is on 10.26.1.17. Updating to the latest official 4.3 will definitely wipe the CWM recovery, and probably will make some of the apps not running any more (not mentioning loosing root, etc..)
Is it possible to install the CWM on such a ROM version (10.26.1.17) ? I've just tested booting it and booting (and using it as a backup) works.

I was on 6.0.4.6 and i used flashify to update. Worked fine.

hetzbh said:
Small question: my device is on 10.26.1.17. Updating to the latest official 4.3 will definitely wipe the CWM recovery, and probably will make some of the apps not running any more (not mentioning loosing root, etc..)
Is it possible to install the CWM on such a ROM version (10.26.1.17) ? I've just tested booting it and booting (and using it as a backup) works.
Click to expand...
Click to collapse
Both cromix and cm11 will require the latest bootloader to eliminate compatibility issues it is recommended to flash to the latest asus firmware
Sent from my SGH-T889 using XDA Premium 4 mobile app

@AngryDinosaur - I made a video on how to install Custom Recovery on your Transformer Pad TF701T!
http://www.youtube.com/watch?v=3IBN1YkBp3g

wwjoshdew said:
@AngryDinosaur - I made a video on how to install Custom Recovery on your Transformer Pad TF701T!
http://www.youtube.com/watch?v=3IBN1YkBp3g
Click to expand...
Click to collapse
included in the post alongside the screenshots. Thanks a lot!!!

OP updated 2/16, installation video tutorial included. Thanks to @wwjoshdew

recovery updated with baseline build and sorted dock sd card functionality and usbdisk functionality.

@pershoot I'd love for this recovery to include touch screen drivers. That way at least aroma could use the touch screen. Any ideas how to compile with the standard drivers included?

sbdags said:
@pershoot I'd love for this recovery to include touch screen drivers. That way at least aroma could use the touch screen. Any ideas how to compile with the standard drivers included?
Click to expand...
Click to collapse
i'll look in to it...

I'm getting a weird error I've never seen before trying to flash something with fastboot. :
fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
error: cannot load 'recovery.img' : No error
Any ideas?

lortay78 said:
I'm getting a weird error I've never seen before trying to flash something with fastboot. :
fastboot flash recovery recovery.img
target reported max download size of 643825664 bytes
error: cannot load 'recovery.img' : No error
Any ideas?
Click to expand...
Click to collapse
Make sure recovery.img is in the same folder as fastboot and you are running the cmd prompt from that folder.

sbdags said:
Make sure recovery.img is in the same folder as fastboot and you are running the cmd prompt from that folder.
Click to expand...
Click to collapse
Duh, I have platform-tools in my path so I can run them from anywhere. I forgot to cd to the directory. Thanks for airing out my brain fart.

lortay78 said:
Duh, I have platform-tools in my path so I can run them from anywhere. I forgot to cd to the directory. Thanks for airing out my brain fart.
Click to expand...
Click to collapse
Very common mistake that happens to the best of us

updated.

Hi,
I spent hours trying to get this to work before discovering there are two missing steps in the OP's instructions.
There's a shell script that calls an application that restores the stock boot loader on every boot.
You have to delete it.
Steps:
1. Root.
2. Install Root Explorer.
3. Go into /etc
4. Delete install_recovery.sh
5. Go into /system
6. Delete recovery-from-boot.p
You have to delete the files. You can't just rename them or change the extension because the system actually searches the filesystem for a file whose contents matches an MD5 hash and will find it if you rename it.
After you do this, THEN follow OP's instructions.

Partitions not mounting @boot

Hey Guys,
first off i had this issue once before, but in that case i could restore a cwm backup from sd card and after sometime the problem fixed itself,
this time, i switched to bacon and i wanted to prepare the p880 for my sister to use, i downloaded zaiben, formatted my external sd card and put the rom on it, i rebooted to recovery wiped( i used the clean to install new rom in philz recovery if i remember correctly) everything and flashed the rom and exactly as last time, the flash seems to go way too fast and ofc i cant boot into android. now as i formatted my sd i have no backup to restore to. kdz flashing seems hopeless as well, as none of the tools recognize the phone when i put it in s/w upgrade mode,
for proof: i checked /system with aromafm and found it being empty after flashing a rom, i even tried extracting the rom zip on sd and moving the content from the zip to /system manually but after a recovery reboot, /system was empty again( only empty "bin" folder)
is somebody able to explain me why i have this issue and maybe how to fix it, or upload a clean cwm backup of whatever rom for me to use?
thx

Thanks for the help until now, really.......
In Further investigation i could find out that Roms ARE actually flashing properly, but /system and probably other partitions are not being mounted
At Boot or in recovery(manually mounting works Here) which is why aromafm reports an empty /system, after a manual Mount in either recovery itself of Aroma console i can See /system being filled with Rom files, now i will change the thread title accordingly, and now ASK: can i force /system to be mounted at Boot somehow? Someone pls answer this time

Okay this is ridicoulous.... why am i getting no help AT ALL?, thank you srsly.....
i investigated even further and suspected that something with fstab might be wrong, but fstab file looks fine to me:
Code:
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 rw
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 rw
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 rw
if someone bothers to answer: what do you think?
pls help........

bump
please help

What recovery are you using? Are you sure your partitions aren't formatted to F2FS? (which would explain why the (F2FS-) recovery can mount the partitions but the system cannot as it expects an ext4 formatted partition rather than a F2FS formatted one)

i'm using an older version of philz touch (i dont think it has f2fs functionality), as i had weird flickering issues with latest philz,
using cat /proc/mounts shows ext4 for /system and other partitions

~MaX~ said:
i'm using an older version of philz touch (i dont think it has f2fs functionality), as i had weird flickering issues with latest philz,
using cat /proc/mounts shows ext4 for /system and other partitions
Click to expand...
Click to collapse
Did you try to boot another ROM (Slim, nameless, whatever) or using another kernel?

laufersteppenwolf said:
Did you try to boot another ROM (Slim, nameless, whatever) or using another kernel?
Click to expand...
Click to collapse
i tried latest aospa,zaiben, pa 3.99 and iodak kernel (stock or cm according to the kind of rom i tried to boot)
thank you for helping btw, i appreciate it
EDIT: I attached an image of output of cat /proc/mounts (sorry for the size)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

~MaX~ said:
i tried latest aospa,zaiben, pa 3.99 and iodak kernel (stock or cm according to the kind of rom i tried to boot)
thank you for helping btw, i appreciate it
EDIT: I attached an image of output of cat /proc/mounts (sorry for the size)
Click to expand...
Click to collapse
hmm, can you please grab me a kmsg? (from when it is stuck)

laufersteppenwolf said:
hmm, can you please grab me a kmsg? (from when it is stuck)
Click to expand...
Click to collapse
could you give me a quick how to on using adb in recovery from pc? i put the phone in sideload mode and tried "adb shell dmesg" but the output just was "error close" and using the command in aromafm terminal gave me an endless stream of log
(Also currently need to charge the phone a bit)
EDIT: NVM kmesg incoming....
okay next question, how can i dump the output into a file and how do i know where it hangs? time in recovery is not correct anymore(i set it once but after reboot it was wrong again, also in kmesg the time again seems to be different)

does that part help? i think it has to do with boot

~MaX~ said:
does that part help? i think it has to do with boot
Click to expand...
Click to collapse
nah, I need the entire log
here's how you get it:
boot the system until it is stuck
hard reboot into recovery (don't enter sideload)
then run the following commands:
Code:
adb shell cat /proc/last_kmsg > /sdcard/last_kmsg
adb pull /sdcard/last_kmsg C:\whatever\path\you\like\last_kmsg
then post the file via pastie.com or any other online paste site

laufersteppenwolf said:
nah, I need the entire log
here's how you get it:
boot the system until it is stuck
hard reboot into recovery (don't enter sideload)
then run the following commands:
Code:
adb shell cat /proc/last_kmsg > /sdcard/last_kmsg
adb pull /sdcard/last_kmsg C:\whatever\path\you\like\last_kmsg
then post the file via pastie.com or any other online paste site
Click to expand...
Click to collapse
no such file or directory
by hard reboot you mean vol - and hold power without pulling battery after hang?

~MaX~ said:
no such file or directory
by hard reboot you mean vol - and hold power without pulling battery after hang?
Click to expand...
Click to collapse
Yes, I meant that. But no kernel log seems like your boot partition/kernel is messed up... I guess you'll have to find a way to restore your entire phone via LG tools, I can't see any other way around that..

laufersteppenwolf said:
Yes, I meant that. But no kernel log seems like your boot partition/kernel is messed up... I guess you'll have to find a way to restore your entire phone via LG tools, I can't see any other way around that..
Click to expand...
Click to collapse
two last things then: when i hold vol - and then hold power until i reboot, recovery does not start, it tries to boot android again (has always been like that)
and also: all roms except cm official show no bootanimation before hang, cm does

~MaX~ said:
two last things then: when i hold vol - and then hold power until i reboot, recovery does not start, it tries to boot android again (has always been like that)
and also: all roms except cm official show no bootanimation before hang, cm does
Click to expand...
Click to collapse
1) yeah, I know, easiest way to fix that is to simply pull the battery and then boot into recovery
2) if the bootanimation shows up, it means the kernel as well as the ramdisk have booted properly. So in this case, you should be able to grab a last_kmsg as well as a logcat

hi
today I installed that application " LG-Optimus-4XHD-Recovery-v1.0.apk "
I have selected ClockworkMod Custom Recovery.
It showed that Operation is successful.
than i clicked on "Boot Recovery" to restart my Phone in CloclworkMod Custom Recovery.
since then I am getting only Starting animation. (LG LOGO).
nothing happens.
My battery was full when i performed this procedure
any help please

Lended Phone to Friend; He Decided to "Encrypt his phone for "Google for Work"".

Lended Phone to Friend; He Decided to "Encrypt his phone for "Google for Work"".
He Decided he wanted to encrypt the phone so he could use Google for work.
Huge Mistake letting him do that, he ended up bricking the thing and now I've got a major issue.
I Cant write, mount, or read the /system Partition in TWRP no matter WHAT I do.
Anyone have any suggestions?
I Can get onto the system where it says "Enter your pattern to decrypt" He puts the correct one in and then it tells him "Decrypt unsuccessful"
When I try to wipe /system in wipe mode, it says Error: Cannot mount /system repeatedly.
Please put your input on the matter Thanks
(I still have 1 L90 that works, but both have Download mode wiped because I accidentally deleted it while unlocking boot loader to discover its already unlocked.
(Will post pictures later)

Bro, go to recovery, plug your device on USB, then from win open adb and type separate one by one in command prompt:
adb shell
recovery –wipe_data –set_filesystem_encryption=off

Nada
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also, Recovery Wont load anymore and now is "Blinking" Teamwin over and over. GG

And your system won't boot up? Nonsense, you did not wipe recovery with this command to make clear.

Vule991 said:
And your system won't boot up? Nonsense, you did not wipe recovery with this command to make clear.
Click to expand...
Click to collapse
Just to be clear, I'm was on Cyandogen Mod and he decided to Encrypt and I cant get past there.
And Recovery cant mount /system.

When you prompted to enter pasword to decrypt you enter: default_password?

Now, I cant mount /data

Jacobwitt said:
Now, I cant mount /data
Click to expand...
Click to collapse
Lets Recap, I ran your command and Now I can mount /system Great!
but Now I cant mount /data.
What would I do to fix that?
Also, How do you update TWRP from Recovery? (I'm an idiot lol)

Jacobwitt said:
Lets Recap, I ran your command and Now I can mount /system Great!
but Now I cant mount /data.
What would I do to fix that?
Also, How do you update TWRP from Recovery? (I'm an idiot lol)
Click to expand...
Click to collapse
If you can go into recovery, simple factory reset, your data must be wiped and clean install ROM, gapps, etc...
Have option to flash ZIP or IMAGE from recovery, select flash image, then flash TWRP.
You turn off encryption with my command: recovery –wipe_data –set_filesystem_encryption=off?
Tell other user for that, this will be useful.
Regards

Vule991 said:
If you can go into recovery, simple factory reset, your data must be wiped and clean install ROM, gapps, etc...
Have option to flash ZIP or IMAGE from recovery, select flash image, then flash TWRP.
You turn off encryption with my command: recovery –wipe_data –set_filesystem_encryption=off?
Tell other user for that, this will be useful.
Regards
Click to expand...
Click to collapse
Yes, I Issued your command and Now I cannot mount /data in TWRP and therefore cannot wipe it.
I will attempt to update TWRP, but as I said, without /data access I cannot do anything on any rom I install.

You do not mount data to flash, please unmount all partition, then wipe system, data, dalvik ART, cache and optionally internal card.

Ok This is going to be a mouthful, but this is how i fixed it.
I Tried many methods, but the one that worked was this:
So, You know how the D415's boot loader is unlocked by default?
What I did was Boot into TWRP, And used ADB through it
Then Through ADB, Pushed the IAF.img of the original download mode, ( I Wiped it accidentally, thinking I had to.) and then wrote the IAF to the Download mode to restore the Download Modes Official Function, To restore the phone to factory.
Then I Just used the LG Software Update Tool to re-flash to stock, and then uh oh, the encryption screen again.
This is the stupid part, So Apparently LG Stock Recovery was able to remove the encryption through a wipe and like magic took me to the setup screen. (No Encryption password request).
Then I Proceeded to root using LG root-script and used TWRP Manager to reinstall TWRP 3.0.2.0 Bam!
Then as a test (I Didn't want to bother downloading CM13) Flashed it with Orion OS and Mini Gapps.
And like Magic, it was all new again.
Lots of threads were used to figure this out especially the re-writing of the IAF image (I had no idea how to write it to the original IAF partition.
Thanks who ever decided to post about how to reinstall the original IAF file.
So, If your (Insert relation here) decides to encrypt your phone and then proceeds to unencrypt it and then brick it, your not in trouble after all!

Jacobwitt said:
I Tried many methods, but the one that worked was this:
So, You know how the D415's boot loader is unlocked by default?
What I did was Boot into TWRP, And used ADB through it
Then Through ADB, Pushed the IAF.img of the original download mode, ( I Wiped it accidentally, thinking I had to.) and then wrote the IAF to the Download mode to restore the Download Modes Official Function, To restore the phone to factory.
Then I Just used the LG Software Update Tool to re-flash to stock, and then uh oh, the encryption screen again.
This is the stupid part, So Apparently LG Stock Recovery was able to remove the encryption through a wipe and like magic took me to the setup screen. (No Encryption password request).
Then I Proceeded to root using LG root-script and used TWRP Manager to reinstall TWRP 3.0.2.0 Bam!
Then as a test (I Didn't want to bother downloading CM13) Flashed it with Orion OS and Mini Gapps.
And like Magic, it was all new again.
Lots of threads were used to figure this out especially the re-writing of the IAF image (I had no idea how to write it to the original IAF partition.
Thanks who ever decided to post about how to reinstall the original IAF file.
So, If your (Insert relation here) decides to encrypt your phone and then proceeds to unencrypt it and then brick it, your not in trouble after all!
Click to expand...
Click to collapse
So, you recover Download mode and flash stock ROM in LG Software Update Tool over encrypted CM13, and this fix you problem if I good understand?

Vule991 said:
So, you recover Download mode and flash stock ROM in LG Software Update Tool over encrypted CM13, and this fix you problem if I good understand?
Click to expand...
Click to collapse
Yes, That is exactly What I did.

Cant flash TWRP - error: device '(null)' not found in adb

Hi all.
I would not be writing this topic if everything I did havent failed.
I tried every possible solution to this I was able to find on the internet - nothing has worked so far.
I tried doing this on different PCs - same result.
I flashed Syberia ROM but didnt like it so decided to go with MIUI 9.7.10.12. I already had TWRP at that time but when I flashed MIUI everything erased, I mean everything - data, storage, TWRP everything.
System works fine but I am unable to flash TWRP with constant message: error: device '(null)' not found.
ADB device not found but fastboot works and ADB shows device connected. The phone is authorized with USB debugging turned on, drivers installed on PC, TWRP image file is correct. I am lost :/ dont know what to do.
Please help

there is no need to flash recovery via adb. twrp should be flash from fastboot. turn off your phone, hold volume down and power for few seconds and phone will boot in fastboot mode.
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
and done.

sunilromy said:
there is no need to flash recovery via adb. twrp should be flash from fastboot. turn off your phone, hold volume down and power for few seconds and phone will boot in fastboot mode.
and done.
Click to expand...
Click to collapse
Where should I type in the command if not in ADB?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I go manually to recovery (vol up + power) the phone reboots to stock recovery so the TWRP is not installed. I tried different versions of TWRP. no progress

Type
Fastboot reboot
and now you can go to twrp recovery by manually .. Power off phone, volume up + power
Or you can also do this

sunilromy said:
Type
Fastboot reboot
and now you can go to twrp recovery by manually .. Power off phone, volume up + power
Or you can also do this
Click to expand...
Click to collapse
fastboot reboot --> phone goes to system
vol up + power --> stock recovery
the problem is TWRP is not flashing :/
it is not USB debugging problem, not USB drivers problem.
The other thing is I can go to fastboot through ADB only when im on CHARGING MODE, it doesnt work on MTP MODE where it should.

brother you just flashed twrp successfully in the screenshot you posted, point is miui, dont let it stick when you boot to system and reboot.
you should, do this. go to fastboot
fastboot flash recovery twrp.img
fastboot boot twrp.img
Click to expand...
Click to collapse
you can flash other modded recovery which will stick. like zcx

sunilromy said:
brother you just flashed twrp successfully in the screenshot you posted, point is miui, dont let it stick when you boot to system and reboot.
you should, do this. go to fastboot
you can flash other modded recovery which will stick. like zcx
Click to expand...
Click to collapse
thx, that command worked

but why I cant go to TWPR using vol up + power?

fastboot boot twrp.img doesn't work for me, after it just black screen with MI logo and "Unlocked" for a long time...
can't enter twrp in any way after success flashing :crying:

Need help with this. Can't sideload with adb fastboot is working fine though.

How can I solve "FAILED (remote: This partition doesn´t exist error)"?

From TWRP > tap Advanced > Terminal > run command: mkdir -p /data/media/0/
Copy the rom to your phone internal storage from pc
Install by finding the transfered rom in the internal storage.

How to Flash the fastboot ROMs without wiping internal storage

Download the fastboot ROM that you want to flash to restore your phone unzip it and then change the flash-all.bat to flash-all.txt then open it. It will have a line that looks like this
fastboot -w update images.zip
Change it to this
fastboot update images.zip
Then close it and save. Change the file name back to flash-all.bat it will now flash the fastboot ROM without wiping internal storage. After that boot back to bootloader and boot phone to twrp and wipe only dalvikcache and data. You will keep all the files on you're phone flash twrp and flash you're new custom ROM gapps magisk the way you normally do. You will have to set you're ROM up again but everything on you're internal storage will still be there. I hope this helps people flashing on a/b devices.

Pretty sure it asks if you want to wipe the internal storage.

It never asked me if I wanted to wipe it just go straight through the process but that it doesn't reset the bootloader like the MSM tool and doesn't wipe internal storage it makes it easier to flash ROMs with the A/b partition. At the beginning when I first bought my McLaren OnePlus 6t I would have to put my music and all my files back on my phone and I have a hundred gigs of music so it was hard to flash a ROM now I can flash one everyday day or every other day. the only reason I even posted this was I couldn't find it anywhere online and then I remembered that if you erase something from the. Bat file it would not wipe so I took a look and figured it out figured I'd post it so that people with the OnePlus 6t would have this information readily handy.

DaveIsHome said:
Download the fastboot ROM that you want to flash to restore your phone unzip it and then change the flash-all.bat to flash-all.txt then open it. It will have a line that looks like this
fastboot -w update images.zip
Change it to this
fastboot update images.zip
Then close it and save. Change the file name back to flash-all.bat it will now flash the fastboot ROM without wiping internal storage. After that boot back to bootloader and boot phone to twrp and wipe only dalvikcache and data. You will keep all the files on you're phone flash twrp and flash you're new custom ROM gapps magisk the way you normally do. You will have to set you're ROM up again but everything on you're internal storage will still be there. I hope this helps people flashing on a/b devices.
Click to expand...
Click to collapse
Thank you very much about this topic. I will try this method for my OP6. I also face your problem about internal data. I have more than 100gb data in my phone and i don't want lost it's on every time i flash the phone. I hope everything ok after use this method.

AWESOME!!

Good to know.

Gonna try this on my oneplus 8 pro but the twrp is buggy atm and doesn't wipes data or even cashes, will have to find some fastboot commands to just wipe data and not internal storage, cheers

Can you please make a video tutorial, it will be great to understand...

How can I flash a Fastboot ROM with my bootloader locked? Please help.

pagan_1 said:
How can I flash a Fastboot ROM with my bootloader locked? Please help.
Click to expand...
Click to collapse
AFAIK you can't.

pagan_1 said:
How can I flash a Fastboot ROM with my bootloader locked? Please help.
Click to expand...
Click to collapse
I was able to flash while having my bootloader locked...
You should enter EDL mode by connecting two test points at the back of your A2 lite and plug the USB. It all dose the magic.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I did as follows.
Note-I was not successful with latest flash tool. Succeeded with 20160830 version at https://www.xiaomiflash.com/download/