Database Info

Testing ROM Images in the SDK Emulator!

I started looking at Android Development and got the whole Dev kit and the Eclipse enrionment setup and working fine.
The question I have is that I would try different apps I develop on the different ROMs available.
How do I get any of the new ROMs, like the HERO ROM ZIP files I can download to run in the emulator or is it even possible?
Im assuming that the system.img file in the SDK id the file I need to replace or re-create, but how is this done?
I am a noob to the develop stuff so step by step instructions would be much appreciated.
I also think this would be great for other developers and ROM makers to be able to test in this way.
Thanks
Simon

Hopefully THIS one dont get closed, it IS asking a development question...anyway,
I would like to know this as well. I would like to test things myself (getting better at manipulating them), and would like to know what he is asking as well.
Thanks.

I don't think this would work, as the ROMs are hardware depending, me thinks. Or at the least the kernel and drivers are.

maybe this will help, maybe not, just an emulator primer, so maybe people can jump on board with this
under <sdk path>/tools
to list out your AVD(android virtual device)
android list targets
will return:
Available Android targets:
id:1
Name: Android 1.1
Type: platform
API level: 2
Skins: HVGA (default), HVGA-L, HVGA-P, QVGA-L, QVGA-P
id:2
Name: Android 1.5
Type: platform
API level: 3
Skins: HVGA (default), HVGA-L, HVGA-P, QVGA-L, QVGA-P
id:3
Name: Google APIs
Type: add-on
Vendor: Google Inc.
Description: Android + Google APIs
Based on Android 1.5 (API level 3)
Libraries:
* com.google.android.maps (maps.jar)
API for Google Maps
Skins: HVGA (default), HVGA-L, QVGA-P, HVGA-P, QVGA-L
from here we choose our integer target, lets say 2
creating an AVD:
android create avd -n your_chosen_name_here -t 2
When you create an AVD, the android tool creates a dedicated directory for it on your development computer. The directory contains the AVD configuration file, the user data image and SD card image (if available), and any other files associated with the device. Note that the directory does not contain a system image — instead, the AVD configuration file contains a mapping to the system image, which it loads when the AVD is launched.
By default, the android tool creates the AVD directory inside ~/.android/avd/ (on Linux/Mac), C:\Documents and Settings\<user>\.android\ on Windows XP, and C:\Users\<user>\.android\ on Windows Vista
Click to expand...
Click to collapse
to run your newly created AVD:
emulator -avd your_chosen_name_here
maybe this will help, but I'm guessing everyone here already knows all of this.
references:
http://developer.android.com/guide/developing/tools/emulator.html#starting

Yeah, I understand that you can specify the AVD.
The only thing now is to edit the AVD to point to a different image. This is easy!
The system image file is a *.img file.
So how do we get our ROM images compiled into the IMG file format?
There must be a tool, but I cant find anything.
And what hardware does the emulator, emulate? Maybe it ignores the hardware specific calls throu an API so the ROM image target hardware shouldn't matter.

I just started messing around with rom's and after I build one I put system.img userdata.img and ramdisk.img from my /mydroid/out folder into the sdk's image folder and start the and it uses the new rom when I start the emulator

thats the easy part
do a nandroid backup
copy the sdk/platforms/android-1.5
to something like sdk/platforms/MINE
go to your AVD directory AVD/whateveryoucalledit
open up the config.ini
edit:
skin.name=HVGA
skin.path=platforms\MINE\skins\HVGA
image.sysdir.1=platforms\MINE\images\
go to your nandroid backup on your sdcard
copy system.img
go to sdk/platforms/MINE/images/
and paste the nandroid system.img
now run your AVD and it will boot that system.img
im running CyanogenMod rom right now in the emulator
hint* number pad 7 with numlock off in the emulator is how to open up the hardware keyboard

Awesome. I'll be giving this a try later.
One question: The apps are in the system.img file on the SDK images as far as I can tell. What do you do with all the apps in the new ROMs?

whatever you want to do with them, they're all there, even android market works perfectly

And where are you guys getting the system.img file from?
The ROM zip files dont have them.
Sorry....Im noob to this. LOL

ggolemg said:
whatever you want to do with them, they're all there, even android market works perfectly
Click to expand...
Click to collapse
OK, Im confused. Can you just unzip the ROM files and place in the folder that you point using the same folder structure?
OR
Do you have to have a system.img ?

Another thought:
I dont want to have to install all the ROMs just to create a Nandroid backup to get the images. There must be a way to create the images from the raw files in the ZIP files.
Any ideas?
UPDATE: The same technology used by Nandroid itself!

The google android emulator included in the google android sdk is limited. Although you can use 'adb push' to upload more tools, but one has to do it again next time. Follow the steps to create a enhanced system.img:
1. system.img is yaffs2 flash file system, so firstly you need the mkfs.yaffs2 tool, download it in the following link: Release Android Yaffs2 Tool (Both X86 And ARM). One has to be a registered user to download the tools.
2. use the 'adb push' to upload tools to android emulator, executables in /system/bin/, libraries in /system/lib, one can also create folder. One need change the file mode necessary.
3. upload the ARM mkfs.yaffs2 tool, use the following command to create system.img: # mkfs.yaffs2 /system /system.img
4. download the system.img to local with command 'adb pull', replace the system.img in your emulator folder/tools/lib/images/
Click to expand...
Click to collapse
so it seems like it would be just as much fun doing a nandroid backup
*edit*
so now the real question is, how do we go about ripping out the nandroid functionality to be able to do this locally?
*edit 2*
it is the mkfs.yaffs2 tool
Usage:
mkfs.yaffs2 yourdir yourimage
Ohsaka said:
NANDROID - CYGWIN DIRECTIONS (not not not, I repeat, not fully tested and verified yet)
Changes so far if you are using cygwin:
1) Make sure you have the 'netcat' and 'gcc' packages, else just run cygwin.exe again and get them.
You can test if you have them by running 'which nc' and 'which gcc', both commands should return /usr/bin/<command>
2) Compile the mkyaffs2image executable.
Inside the extracted nandroid archive directory, goto the tartools\yaffs2\utils\ directory (inside a cygwin prompt) and type 'make'.
This should generate a file named "mkyaffs2image.exe" which you need to place somewhere on your path.
(Hint: If you haven't downloaded the Android SDK, abort now. Wait for more explicit directions... Else, place the .exe where adb is, since it should be on your path already)
3) Edit the nandroid.sh script. (else you get a permission denied error when the script tries to run the dump_image-arm file)
Find the line:
adb push ./$tool /cache/$tool
Add the following line after it:
adb shell chmod 777 /cache/$tool
4) Make a managed mount named /tmp (else windows will puke on the long unix filenames with colons, etc)
mkdir /tmp
mount -o managed c:/cygwin/tmp /tmp (Note: change c:/cygwin to be the directory cygwin was installed to, you can find it by typing 'cd /' and then 'explorer .')
5) Follow the standard "tar + mkyaffs2image" directions to generate the last three .img files. They refer to the /tmp directory which you created in the previous step.
Viola! Looks like I have a complete backup image now...
$ ls -l
total 117504
-rw-r--r-- 1 Osaka None 2621440 Jun 12 21:31 boot.img
-rw------- 1 Osaka None 737088 Jun 12 22:07 cache.img
-rw------- 1 Osaka None 53570880 Jun 12 22:06 data.img
-rw-r--r-- 1 Osaka None 262144 Jun 12 21:31 misc.img
-rw-r--r-- 1 Osaka None 5242880 Jun 12 21:31 recovery.img
-rw------- 1 Osaka None 57885696 Jun 12 22:06 system.img
Now I just need to drink up the courage to test it on my phone!
Click to expand...
Click to collapse

ggolemg said:
so it seems like it would be just as much fun doing a nandroid backup
*edit*
so now the real question is, how do we go about ripping out the nandroid functionality to be able to do this locally?
*edit 2*
it is the mkfs.yaffs2 tool
Usage:
mkfs.yaffs2 yourdir yourimage
Click to expand...
Click to collapse
Is this for Linux (which I don't have) and if so, is there a Windows version?

short answer: yes its only for linux
long answer is a plea for help i posted in the nandroid thread about it:
I was wondering if there was a method to use the yaffs3 command to make a system.img from an unzipped rom placed on the sdcard through ADB, from what I've seen nandroid is almost exactly what I'm after.
The issue of why I can not just do this through linux, i can. I just want to be able to do it through windows some way without loading the entire rom on the phone and nandroiding the system.img out.
Either the aforementioned method, or the ability to mount a portion of my computers hard drive as a recognizable mountable partition within android running on the usb connected phone, loading the rom on that partition, unzipping it there, running ADB and making the system.img. But this way seems to bring up more problems than it's worth.
Or.. running the make yaffs3 command through ADB running the emulator with the rom unzipped on the virtual sdcard. This would actually be the best option as it would not require an actual phone.
I hope someone can help. Thank you very much.
Click to expand...
Click to collapse
hopefully someone knows the answer, I'm still trying though.
so on windows we would adb push the update.zip to the sdcard on the emulator
unzip it on the sdcard, there are apps for that
adb shell mkfs.yaffs2 sdcard/<extractedzipfilename>/system/ sdcard/system.img
adb pull the newly created system.img and proceed to load it in the emulator
i know im missing a ton here, please someone correct me

I'd love to be able to run these images in the emulator on windows!

ggolemg said:
thats the easy part
do a nandroid backup
copy the sdk/platforms/android-1.5
to something like sdk/platforms/MINE
go to your AVD directory AVD/whateveryoucalledit
open up the config.ini
edit:
skin.name=HVGA
skin.path=platforms\MINE\skins\HVGA
image.sysdir.1=platforms\MINE\images\
go to your nandroid backup on your sdcard
copy system.img
go to sdk/platforms/MINE/images/
and paste the nandroid system.img
now run your AVD and it will boot that system.img
im running CyanogenMod rom right now in the emulator
hint* number pad 7 with numlock off in the emulator is how to open up the hardware keyboard
Click to expand...
Click to collapse
Hm, the emulator just hangs on the ANDROID.. message, similar to when the standard system.img was in.

anyone figure out how to do this on a mac?
thanks if anyone can.

johnnylicious said:
anyone figure out how to do this on a mac?
thanks if anyone can.
Click to expand...
Click to collapse
I found this somewhere else and take no credit for it. I did shorten the steps.
Of course this is once you have the sdk installed on your mac
1. Run Terminal, and change to the 'tools' directory of the SDK (or add the tools directory to the path settings in ~/.profile).
2. Type './android list target'
3. Note the 'id' number of the '1.5' target (in my case it's '2')
4. Type './android create avd -n enhanced -t 2' (substitute 2 with the target number determined above if required)
5. You will be prompted to create a hardware profile. {You can leave as default no}
6. Use nandroid to create a backup then copy system.img
7. Copy file to ~/.android/avd/enhanced.avd/system.img
8. You're ready! Type './emulator -avd enhanced' to run! Note: inital boot may take a few minutes!

Can anyone post up the
Android Yaffs2 Tool (Both X86 And ARM)
for download? The above link doesn't work. I did a google search and all the D/L links are referring to the same location.
thanks!

Root Remix OS for PC

This guide is to root Remix OS for PC
You will need Ubuntu for Rooting (You can download and run it in live CD)
If you are experienced with linux systems don't read whats written in bracket
1. Download and Extract RemixRoot.zip
2. Copy system.img from your pendrive or hdd wherever you have installed Remix Os to this folder (ie RemixRoot folder it should be alongside Readme.txt)
3. Open Terminal (Ctrl+Alt+T)
4. Type
Code:
sudo -i
5. Enter your password (If you are running in live cd then no password)
6. Change directory to RootRemix folder (Goto tmp folder, right click and goto properties and copy location, this is your <dir> replace it in command below )
Code:
cd <dir>
7. If you did it right next line of terminal will end with RemixRoot# followed by blinking cursor
8. Now run rootx.sh script by typing
Code:
sh rootx.sh
9. If everything goes right there wont be any error message and you will get a root.img in your RemixRoot folder
10. Rename it to system.img and copy to your pendrive/hdd replacing previous system.img
11. Reboot and go to RemixOS and update SuperSU binaries
12. That's it! you are now rooted
Thanks to Chainfire & hackarchive

I tried it but i got no system.img, i got r/w access to system (choosen by install) so i tried to symlink it to my system directory and commented out all image mounted related things from script and then tried it.
but after that i cannot boot android anymore, i think the problem is app_process linking to daemonsu, since i set back to original it boots like normal but no superuser access. SuperSU said theres is no superuser installed.
Any suggestion?

Silly question but will I lose root access if I update to the newest version by flashing the new image over the top?

Yes a silly question.... Deserves a silly answer. It will still be underneath, but good luck trying to retrace it!

any other method for rooting, without using ubuntu?
#tested with ubuntu live, and it works like a charms. Thank you..
Sent from my C46G using XDA Premium 4 mobile app

ninharp said:
I tried it but i got no system.img, i got r/w access to system (choosen by install) so i tried to symlink it to my system directory and commented out all image mounted related things from script and then tried it.
but after that i cannot boot android anymore, i think the problem is app_process linking to daemonsu, since i set back to original it boots like normal but no superuser access. SuperSU said theres is no superuser installed.
Any suggestion?
Click to expand...
Click to collapse
same problem here.

Hope same other method can solved

I modified the original script to work with the system folder installation and i removed all app_processX dependend things from script (dunno if it affects the root in any way, cannot find any issue by now) Read the Readme.txt for further installation instructions. The link you find on the reddit sub that GoPal has posted! I cannot post links right now.
Try this
kretex said:
Hope same other method can solved
Click to expand...
Click to collapse

ninharp said:
I tried it but i got no system.img, i got r/w access to system (choosen by install) so i tried to symlink it to my system directory and commented out all image mounted related things from script and then tried it.
but after that i cannot boot android anymore, i think the problem is app_process linking to daemonsu, since i set back to original it boots like normal but no superuser access. SuperSU said theres is no superuser installed.
Any suggestion?
Click to expand...
Click to collapse
You will get root.img file you will have to rename it to system.img

masdeco said:
same problem here.
Click to expand...
Click to collapse
Me too [emoji25]
Envoyé de mon E5333 en utilisant Tapatalk

I've just installed RemixOS 2.0 onto a partition on my Lenovo X200T. I followed the instructions and all was good until I tried to run SuperSU. When it tried to update via the normal method the install failed and asked for a reboot. Any suggestions.

ninharp said:
I modified the original script to work with the system folder installation and i removed all app_processX dependend things from script (dunno if it affects the root in any way, cannot find any issue by now) Read the Readme.txt for further installation instructions. The link you find on the reddit sub that GoPal has posted! I cannot post links right now.
Try this
Click to expand...
Click to collapse
the answer is replace the system folder. this is my methode :
1. copy the system img from the extracted remix iso to somewhere
2. then run the script
3. unpack the system img that already rooted and copy all the content to the system folder of the remix (replace)
4. done. Remix os rooted.

Guys, I installed Remix to ext4 partition (in order to use all free space), so there's no "system.img" on it (but there's "system" folder). How to modify the script or to root Remix other way?
masdeco, thanks for the idea! How do you unpack img file, btw?

4ezahernya said:
Guys, I installed Remix to ext4 partition (in order to use all free space), so there's no "system.img" on it (but there's "system" folder). How to modify the script or to root Remix other way?
masdeco, thanks for the idea! How do you unpack img file, btw?
Click to expand...
Click to collapse
after root the system img then mount it, copy all the content to the system folder of your remix.
since I am a linux user so I use this command :
mount -o loop system.img tmp

this is so cool cool

Works Lenovo Yoga 2 11
Installed to a partition on my HD:
Downloaded RemixOS iso
extracted contents of iso
created temp, data and system folders
ran this tool to root the system.img (now root.img)
renamed root.img back to system.img
mounted system.img to temp folder
copied contents of temp folder to system folder
added entry in grub
now I am triple booting Windows, Linux and RemixOS 2.0 Android with ROOT
Thank You!!!

here is a xdelta3 for patching system.img for those using Remix OS 2 from a USB stick and run windows

GizmoTheGreen said:
here is a xdelta3 for patching system.img for those using Remix OS 2 from a USB stick and run windows
Click to expand...
Click to collapse
can you please explain its usage?

the_poolee said:
can you please explain its usage?
Click to expand...
Click to collapse
me too!
Please

the_poolee said:
can you please explain its usage?
Click to expand...
Click to collapse
dariett said:
me too!
Please
Click to expand...
Click to collapse
it shouldn't be too hard to figure out, put the files in your folder of choice with the system.img from your usb stick, run the batfile. it should create a file named rooted system image, now just replace system.img on your usb stick with that and run...
ofcourse I am assuming your system.img is identical to the one I had, which it should be if it was the 2.0 dev preview which is the only thing you can get today, right?

Root+Custom ROM Onda V10 Pro

Hi everybody,
i try to find tutorial to root my onda v10 pro tablet and then install a custom rom on it but i found nothing. Did someone change the official ROM, if yes can i have some help?
Thanks a lot.

locss said:
Hi everybody,
i try to find tutorial to root my onda v10 pro tablet and then install a custom rom on it but i found nothing. Did someone change the official ROM, if yes can i have some help?
Thanks a lot.
Click to expand...
Click to collapse
I also need to root in my v10 pro wave, and find custom rom, have if someone helps us, thanks

impossible to root or unlock
berti hispano said:
I also need to root in my v10 pro wave, and find custom rom, have if someone helps us, thanks
Click to expand...
Click to collapse
Hello, i also need to root this tablet, i want to enable remote control because i will give it to my grand mother. Any help on how to unlock bootloader or root the tablet will be apreciate ! THank you !
I found this thread : 4pda.ru / forum / index.php?showtopic=819301&st=80#entry64752617
They say to do the following command but i have "permission denied on all commands" !
Process:
- Unpack Magisk-v13.6 (1360) .zip
- In the unpacked folder, load the file boot-verified.img from the firmware and rename it to boot.img . And also rename the arm64 folder to magisk_inject
- Once again we make sure that the following folders and files are in the prepared folder: META-INF, boot.img, common, magisk_inject .
- Open the terminal from this folder (for win7 holding the shift, call the context menu and select Open command window here) and enter 5 lines of commands, one at a time (I used to copy-paste):
adb shell "rm -rf / data / local / tmp / *"
adb push META-INF / com / google / android / update-binary common magisk_inject boot.img / data / local / tmp
adb shell "cd / data / local / tmp / magisk_inject; mv ../common/*.; chmod 755 *; sh ../update-binary indep boot_patch.sh ../boot.img; mv ../bin/busybox busybox "
adb pull / data / local /tmp/magisk_inject/new-boot.img
adb shell "cd / data / local / tmp; rm -rf * .img magisk_inject / *. img update-binary bin common"
THank You !

ekirock said:
Hello, i also need to root this tablet, i want to enable remote control because i will give it to my grand mother. Any help on how to unlock bootloader or root the tablet will be apreciate ! THank you !
I found this thread : 4pda.ru / forum / index.php?showtopic=819301&st=80#entry64752617
They say to do the following command but i have "permission denied on all commands" !
Process:
- Unpack Magisk-v13.6 (1360) .zip
- In the unpacked folder, load the file boot-verified.img from the firmware and rename it to boot.img . And also rename the arm64 folder to magisk_inject
- Once again we make sure that the following folders and files are in the prepared folder: META-INF, boot.img, common, magisk_inject .
- Open the terminal from this folder (for win7 holding the shift, call the context menu and select Open command window here) and enter 5 lines of commands, one at a time (I used to copy-paste):
adb shell "rm -rf / data / local / tmp / *"
adb push META-INF / com / google / android / update-binary common magisk_inject boot.img / data / local / tmp
adb shell "cd / data / local / tmp / magisk_inject; mv ../common/*.; chmod 755 *; sh ../update-binary indep boot_patch.sh ../boot.img; mv ../bin/busybox busybox "
adb pull / data / local /tmp/magisk_inject/new-boot.img
adb shell "cd / data / local / tmp; rm -rf * .img magisk_inject / *. img update-binary bin common"
THank You !
Click to expand...
Click to collapse
Thank you for your post, but where can we find some custom rom for this tablet?
Thank you.

android 6.0
reddit.com/r/androidtablets/comments/6v4szs/onda_v10_pro_play_store_doesnt_work_out_of_the/
haven't tried yet but attempting tonight

Thanks Gregory, but is it possible to install a custom rom based on android 7?

system.img is corrupt for all . Has anyone successfully been able to flash this firmware to their devices so far??
Edit: my bad, cannot use 7 zip to extract, use ext4 extractor instead

Success!
Hi there
I tried dozen of methods to root this device and always failed.
I was ready to give up when I decided to give a last chance to me.
I have tried the Hovatek's brilliant fastboot way with magisk manager but always stucked on the critical last point.
OK, follow these intructions
#extrack Magisk 13 on a PC folder
# copy the files in common folder on sdcard in your device
#copy the original boot.IMG of your firmware on the sdcard
#open your device install and run Magisk manager app
#under this app install Magisk and chose .img
#go to sdcard and select your boot.img for patching
#look at the terminal if the job is done
#find the patched image in the Magisk folder at the main storage
#flash it with sp flash tool
#enjoy and forgive me for my basic English
PS. I'm looking for twrp or cwm for this device.
Please inform me if you know something about.

cosbrav said:
Hi there
I tried dozen of methods to root this device and always failed.
I was ready to give up when I decided to give a last chance to me.
I have tried the Hovatek's brilliant fastboot way with magisk manager but always stucked on the critical last point.
OK, follow these intructions
#extrack Magisk 13 on a PC folder
# copy the files in common folder on sdcard in your device
#copy the original boot.IMG of your firmware on the sdcard
#open your device install and run Magisk manager app
#under this app install Magisk and chose .img
#go to sdcard and select your boot.img for patching
#look at the terminal if the job is done
#find the patched image in the Magisk folder at the main storage
#flash it with sp flash tool
#enjoy and forgive me for my basic English
PS. I'm looking for twrp or cwm for this device.
Please inform me if you know something about.
Click to expand...
Click to collapse
Just did it. it works, though it was horrible. magisk 13 is too old and I could not find how to patch the boot.img option.
so I managed to do with the common files from 18.1 and the patching complete.
then I re-flashed everything and unfortunately it reset the tablet, but worked and I'm rooted now.
As you, waiting to the confirmation twrp exist, and if so what version.
cheers

cosbrav said:
Success!
Hi there
I tried dozen of methods to root this device and always failed.
I was ready to give up when I decided to give a last chance to me.
I have tried the Hovatek's brilliant fastboot way with magisk manager but always stucked on the critical last point.
OK, follow these intructions
#extrack Magisk 13 on a PC folder
# copy the files in common folder on sdcard in your device
#copy the original boot.IMG of your firmware on the sdcard
#open your device install and run Magisk manager app
#under this app install Magisk and chose .img
#go to sdcard and select your boot.img for patching
#look at the terminal if the job is done
#find the patched image in the Magisk folder at the main storage
#flash it with sp flash tool
#enjoy and forgive me for my basic English
PS. I'm looking for twrp or cwm for this device.
Please inform me if you know something about.
Click to expand...
Click to collapse
Followed the same but with latest Magisk and SP flash tools. It works and now my Onda V10 pro is rooted.
If you guys need latest google play services to be running on Onda V10 Pro. Please use LuckyPatcher after installing Magisk to install latest google play services(arm64-v8a).
Install LuckyPatcher and provide super user access.
1. Uninstall existing google play services using LuckyPatcher.
2. Download arm64-v8a compatible latest google play services and install as a system app using LuckyPatcher. After that it will ask for reboot and after rebooting it will show android apps updating loader for few mins.
3. Then you can use any apps that require latest google play services. For me youtube was not working before but now its working.

[FASTBOOT] [daisy] Xiaomi Mi A2 Lite FASTBOOT Images

Disclaimer
I am not responsible for bricked devices or anything like that. YOU are choosing to make these modifications, and if you point your finger at me for messing up your device, I will laugh at you.
Here are the current fastboot links for the Xiaomi Mi A2 Lite (daisy):
Fastboot Images:
Android 10.0 [V11.0.9.0.QDLMIXM]:
https://bigota.d.miui.com/V11.0.9.0....QDLMIXM_20200805.0000.00_10.0_e1ea175e5b.tgz
Android 10.0 [V11.0.7.0.QDLMIXM]:
https://bigota.d.miui.com/V11.0.7.0....QDLMIXM_20200617.0000.00_10.0_7d0ffb82ac.tgz
Android 10.0 [V11.0.5.0.QDLMIXM]:
https://bigota.d.miui.com/V11.0.5.0....QDLMIXM_20200518.0000.00_10.0_64aa05498c.tgz
Android 10.0 [V11.0.4.0.QDLMIXM]:
https://bigota.d.miui.com/V11.0.4.0....QDLMIXM_20200404.0000.00_10.0_88297a8e92.tgz
Android 9.0 [V10.0.20.0.PDLMIXM]:
https://bigota.d.miui.com/V10.0.20....0.PDLMIXM_20200327.0000.00_9.0_2baf524aaf.tgz
Android 9.0 [V10.0.18.0.PDLMIXM]:
https://bigota.d.miui.com/V10.0.18....0.PDLMIXM_20200109.0000.00_9.0_a7b709656c.tgz
Android 9.0 [V10.0.17.0.PDLMIXM]:
https://bigota.d.miui.com/V10.0.17....0.PDLMIXM_20191209.0000.00_9.0_8a03587b9f.tgz
Android 9.0 [V10.0.16.0.PDLMIXM]:
https://bigota.d.miui.com/V10.0.16....0.PDLMIXM_20191108.0000.00_9.0_8454506408.tgz
Android 9.0 [V10.0.13.0.PDLMIXM]:
https://bigota.d.miui.com/V10.0.13....0.PDLMIXM_20190813.0000.00_9.0_5d0d486f04.tgz
Android 9.0 [V10.0.12.0.PDLMIXM]:
https://bigota.d.miui.com/V10.0.12....0.PDLMIXM_20190717.0000.00_9.0_59368ef014.tgz
Android 9.0 [V10.0.10.0.PDLMIXM]:
https://bigota.d.miui.com/V10.0.10....0.PDLMIXM_20190613.0000.00_9.0_f1adc81d8e.tgz
Android 9.0 [V10.0.9.0.PDLMIXM]:
https://bigota.d.miui.com/V10.0.9.0...0.PDLMIXM_20190514.0000.00_9.0_f9d0c739e0.tgz
Android 9.0 [V10.0.7.0.PDLMIXM]:
https://bigota.d.miui.com/V10.0.7.0...0.PDLMIXM_20190318.0000.00_9.0_442d4f503e.tgz
Android 9.0 [V10.0.3.0.PDLMIXM]:
https://bigota.d.miui.com/V10.0.3.0...0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz
Android 9.0 [V10.0.2.0.PDLMIFJ]:
https://bigota.d.miui.com/V10.0.2.0...0.PDLMIFJ_20181221.0000.00_9.0_fed1fcdf5d.tgz
Android 8.1.0 [V9.6.11.0.ODLMIFF]:
https://bigota.d.miui.com/V9.6.11.0...0.ODLMIFF_20181112.0000.00_8.1_8028e3bf1c.tgz
Android 8.1.0 [V9.6.10.0.ODLMIFF]:
https://bigota.d.miui.com/V9.6.10.0...0.ODLMIFF_20181030.0000.00_8.1_141b42a73d.tgz
Android 8.1.0 [V9.6.9.0.ODLMIFF]:
https://bigota.d.miui.com/V9.6.9.0....0.ODLMIFF_20181010.0000.00_8.1_baf840279a.tgz
Android 8.1.0 [V9.6.6.0.ODLMIFF]:
https://bigota.d.miui.com/V9.6.6.0....0.ODLMIFF_20180816.0000.00_8.1_c1d890dd75.tgz
Android 8.1.0 [V9.6.4.0.ODLMIFF]:
https://bigota.d.miui.com/V9.6.4.0....0.ODLMIFF_20180724.0000.00_8.1_4afd3431a2.tgz
Use
Code:
fastboot flashing unlock
to unlock the bootloader.
You may also need to unlock the critical partitions by typing:
Code:
fastboot flashing unlock_critical
You can flash factory images using the batchfile in the firmware archive or using MiFlash. You can also flash in Snapdragon EDL-(Emergency Download) Mode (bootloader unlocked is necessary) by typing:
Code:
fastboot oem edl
(Instructions about flashing and download links can be found here [PC only!]) https://c.mi.com/oc/miuidownload/detail?guide=2

Reserved

Reserved

Niktendo said:
Here are the fastboot links for the Xiaomi Mi A2 Lite:
Fastboot Images:
Android 8.1.0 [V9.6.4.0.ODLMIFF]: http://bigota.d.miui.com/V9.6.4.0.O...0.ODLMIFF_20180724.0000.00_8.1_4afd3431a2.tgz
Instructions about flashing can be found here: http://en.miui.com/a-234.html
Click to expand...
Click to collapse
Thanks for this .
downloaded and doing the same step to flash boot.img with Magisk Patch . I am using the same step as flashing with Jasmine , instead using Jasmine.img im using the daisy.img that you have attached here.
magisk is up and running .
gcam is running (for rear camera)
i cant get Selfie / Front Cam to work for this device * tried few version . front cam wont work .
thanks !

mytowyn said:
Thanks for this .
downloaded and doing the same step to flash boot.img with Magisk Patch . I am using the same step as flashing with Jasmine , instead using Jasmine.img im using the daisy.img that you have attached here.
magisk is up and running .
gcam is running (for rear camera)
i cant get Selfie / Front Cam to work for this device * tried few version . front cam wont work .
thanks !
Click to expand...
Click to collapse
which apk from gcam did you try? (download link?)

Deleted

Can you show me how I can flash my Xiaomi Mi A2 Lite. Please with a guide and download links.

Abstauber08 said:
Can you show me how I can flash my Xiaomi Mi A2 Lite. Please with a guide and download links.
Click to expand...
Click to collapse
http://en.miui.com/a-234.html

For installing ROM with fastboot in Linux (Ubuntu 18.04)
Download platform-tools for Linux from here:
https://developer.android.com/studio/releases/platform-tools
open terminal:
Code:
sudo su
cd to/platform-tools.zip/directory
cp platform-tools_VERSION-linux.zip /opt
cd /opt
unzip platform-tools_VERSION-linux.zip
cd ~
nano .bashrc
Add this line to end of .bashrc:
Code:
export PATH="/opt/platform-tools:$PATH"
And save it, now enter:
Code:
source .bashrc
Connect your phone to PC and continue:
(Make sure USB debugging enabled in developr options)
Code:
adb reboot bootloader
cd to/rom/directory
./flash_all.sh
That's it! Wait until flash process complete.

S /\ E E D said:
For installing ROM with fastboot in Linux (Ubuntu 18.04)
Download platform-tools for Linux from here:
https://developer.android.com/studio/releases/platform-tools
open terminal:
Code:
sudo su
cd to/platform-tools.zip/directory
cp platform-tools_VERSION-linux.zip /opt
cd /opt
unzip platform-tools_VERSION-linux.zip
cd ~
nano .bashrc
Add this line to end of .bashrc:
Code:
export PATH="/opt/platform-tools:$PATH"
And save it, now enter:
Code:
source .bashrc
Click to expand...
Click to collapse
Isn't easier to extract the zip file with the mouse right click, and then simply sudo-copy the extracted content to usr/local/bin ?

BubuXP said:
Isn't easier to extract the zip file with the mouse right click, and then simply sudo-copy the extracted content to usr/local/bin ?
Click to expand...
Click to collapse
There is a directory in the zip (platform-tools), so you have to add /usr/local/bin/platform-tools to your PATH envvar ?

S /\ E E D said:
There is a directory in the zip (platform-tools), so you have to add /usr/local/bin/platform-tools to your PATH envvar ?
Click to expand...
Click to collapse
So you can copy the content of the platform-tools folder into /usr/local/bin/ and no need to set any path (that folder is already included)

BubuXP said:
So you can copy the content of the platform-tools folder into /usr/local/bin/ and no need to set any path (that folder is already included)
Click to expand...
Click to collapse
I think it's a bit dirty solution because the content of the directory may change in next updates, how ever feel free to do it but i prefer my way.

S /\ E E D said:
I think it's a bit dirty solution because the content of the directory may change in next updates, how ever feel free to do it but i prefer my way.
Click to expand...
Click to collapse
No, the system packages will be installed in the /usr/ directory. If you check, you will find that /usr/local/ is empty, because it's there only to host files that doesn't have a package (like the platform-tools zip) and can be used by all users. No package will ever write anything in /usr/local/.
An example: you find some fonts on the internet, but they are not packaged, just regular .ttf files. You want to share those fonts with all the users in the system, but you can't put them in /usr/share/fonts/ because they could conflict with some fonts installed by system packages. So what you will do? Copy them to each user?
The cleanest solution is to put them in /usr/local/share/fonts/, that is like putting them in /usr/share/fonts/ but without interfering with the package system.
You can surely use /opt/ instead, but using /usr/local/bin/ will save you from manually setting the path variable, because /usr/local/bin/ is already included in the path variable by default by the OS.
But we're going a bit off-topic, better stop here or if you're interested, we can continue via P.M.

I have to ask. Is this MIUI or the proper Android One stock ROM?

It's a vanilla Android stock rom.

Sorry for interrupting, but can anyone explain what is use for those fastboot images?

Thank you so much for this @Niktendo
this saved me so much

can we install ota updates with miflash after extract system.img boot.img etc .. from zip file by replace it with old img's ?

Hello. Will the image of the Fastboot Android 8.1.0 [V9.6.11.0.ODLMIFF]:

Best way to update webview on custom ROM

Hi everyone
I would like to ask how do you update the android webview in your custom rom (in my case lineageOS) since it is a problem that I expect should be widespread but of which I hear little,
I know 3 possible solutions, but all 3 have limitations:
AOSP webview: comes pre-installed with the rom, if the rom is mantained usually the update is also included,
but if I want to update the webview even without updating the rom, or if the rom is no longer updated due to the age of the device, is it possible to do it? (even using root if necessary, where can I found an apk with a compatible signature? can it be replaced in /system/product/app/webview without causing bad behavior?)
google android webview: you can install and update it from the play store, but it requires non-pico gapps and the trichrome library, is there no way to install it with pico-gapps? (or even better, without using gapps at all)
bromite webview: this is easyer to get than AOSP webview, but the rom must support its signature among the allowed-systemwebview-packages (see https://github.com/bromite/bromite/...View#verifying-allowed-systemwebview-packages), tring to install it without this causes bootloop
How do you deal with this?
NOTE: i'm talking about android 10+, I specify this because in the old versions it was possible to fix it using xposed, but now that we have to deal with safetynet it's not that easy anymore
EDIT - extra useful info I've found:
It seems someone was able to install the bromite webview correctly in 2020 https://forum.xda-developers.com/t/solved-installing-webview-rooted-stock-rom.4083237/
AOSP webview is still updated to a very old version https://android.googlesource.com/platform/external/chromium-webview/+/refs/heads/master/prebuilt/ (chrome 95, while bromite & google webview are at version 104)

since no one has been able to give a solution and I HATE finding dead threads with OP that was able to fix but didn't describe how to anyone, I leave you MY solution here (I managed to install bromite webview)
You can still suggest better solutions if you know any
PREMISES:
I am not responsible if following these steps do not get the desired result, please backup everything before trying!
By doing this you will probably lose safetynet pass, in my case all of my apps that need safetynet pass are checking it only on first installation so I simply do this after installing them and while having a backup of them made with titanium
I've tested this in lineageOS 17 with TWRP recovery and root, I cannot guarantee it will work in other cases as well
What do you need:
ON DEVICE:
rooted device
magisk (may not be needed if you find a different way of making an app system app)
recovery that let you move files inside /system partition (In my case TWRP)
ON PC:
linux-based system (I think you can do the same thing even on windows or macos but you need to do extra steps in order to install tons of missing commands)
adb installed
aapt installed
java installed (seems like both oracle and openjdk are good enough), for debian-based system you can use sudo apt install default-jdk
PART 1 - ON YOUR PC:
install apktool, istructions here https://ibotpeaches.github.io/Apktool/install/
move apktool in /usr/local/bin in order to be able to call it with apktool command
(these 2 commands are launched from the download folder)
sudo mv apktool /usr/local/bin/apktool
sudo mv apktool_VERSION.jar /usr/local/bin/apktool.jar
attach device to pc via usb, activate usb debug mode in order to be able to use adb
to avoid mixing files with other things it's better to make a custom folder for the next sequence of operations, but do as you like (this is just a suggestion, if you want to do it differently just adjust the commands accordingly):
mkdir ~/bromite_ww_framework_res && cd ~/bromite_ww_framework_res
pull your device "framework-res.apk" (KEEP it as BACKUP to restore in case you do something wrong!)
adb pull /system/framework/framework-res.apk
cp framework-res.apk framework-res_ORIGINAL_BACKUP.apk
decode your "framework-res.apk" using apktool
apktool if framework-res.apk
apktool d framework-res.apk
edit the decoded "config_webview_packages.xml" and add Bromite WbView signature
(you can use the editor you like, in my example there is nano to avoid people crying about not being able to exit vim)
nano framework-res/res/xml/config_webview_packages.xml
BE VERY CAREFUL TO PASTE THINGS CORECTLY IF YOU DON'T LIKE BOOTLOOPS!
XML:
<webviewprovider availableByDefault="true" description="Bromite WebView" packageName="org.bromite.webview">
<signature>MIIDbTCCAlWgAwIBAgIEHcsmjjANBgkqhkiG9w0BAQsFADBmMQswCQYDVQQGEwJERTEQMA4GA1UECBMHVW5rbm93bjEPMA0GA1UEBxMGQmVybGluMRAwDgYDVQQKEwdCcm9taXRlMRAwDgYDVQQLEwdCcm9taXRlMRAwDgYDVQQDEwdjc2FnYW41MCAXDTE4MDExOTA3MjE1N1oYDzIwNjgwMTA3MDcyMTU3WjBmMQswCQYDVQQGEwJERTEQMA4GA1UECBMHVW5rbm93bjEPMA0GA1UEBxMGQmVybGluMRAwDgYDVQQKEwdCcm9taXRlMRAwDgYDVQQLEwdCcm9taXRlMRAwDgYDVQQDEwdjc2FnYW41MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtakjGj0eTavbBB2vWXj8KBixWn4zgXAKc+yGFu3SLEGF1VB5aJWwcMHxVI55yH/8M2eNnJP0BkSidfKgPVcm1sk/GrNEs9uk5sWod9byO5M5QWQmGP2REeTd6J0BVVVaMp2MZnqeR3Su3pwFzrSwTqIGyf8dkPSEz7ifj792+EeRNrov4oRQK7lIfqInzwc4d34wU069Lrw6m7J7HM0KbRYISsWMiYj025Qg+dTrtdWt7jbdcj7htW0eYyJoLd90+s43RWnOpENmWpcWv1EVPxUD4mCdV9idYwoHRIESpSu9IWvqDZp1VoRc43nLgsNfNBwmYdTkIaPiz1m7TBcr7QIDAQABoyEwHzAdBgNVHQ4EFgQUuWoGd7W7wMyQ1pOdjiMv10YHTR0wDQYJKoZIhvcNAQELBQADggEBAA7iw6eKz+T8HIpKDoDcX1Ywjn9JUzuCFu20LnsLzreO/Pog1xErYjdLAS7LTZokfbAnitBskO9QhV9BYkDiM0Qr5v2/HsJTtxa1mz9ywCcI36jblMyuXFj8tuwQI9/t9i+Fc3+bOFBV3t7djPo9qX1dIK0lZ6s8HcIhaCNdqm65fH+nWhC/H9djqC6qOtrkTiACKEcHQ4a/5dfROU0q0M4bS4YuiaAQWgjiGbik4LrZ8wZX1aqJCLt0Hs7MzXyyf0cRSO11FIOViHwzh6WTZGufq2J3YBFXPond8kLxkKL3LNezbi5yTcecxsbKQ6OS46CnIKcy/M8asSreLpoCDvw=</signature>
</webviewprovider>
rebuild the apk with the modified "config_webview_packages.xml"
apktool b framework-res --use-aapt2
create a simple apk from the build folder generated by apktool
Bash:
cd framework-res/build/apk && \
zip -r ../../../framework-res_EDITED_BROMITE.apk * && \
cd ../../..
check that the new apk has the correct config_webview_packages.xml (search 'org.bromite.webview' in the output)
aapt d xmltree framework-res_EDITED_BROMITE.apk res/xml/config_webview_packages.xml | grep bromite
replace new `config_webview_packages.xml` in the original apk (you DON'T want to use the new apk! just replace the config_webview_packages.xml file in the original one!)
Bash:
mkdir res && \
mkdir res/xml && \
cp framework-res/build/apk/res/xml/config_webview_packages.xml res/xml/config_webview_packages.xml && \
zip -u framework-res.apk res/xml/config_webview_packages.xml && \
rm -rf res
(if you have trouble running those last commands just do it manually via 7-zip or similar programs)
place the modified `framework-res.apk` in the device
PART 2 - ON DEVICE:
Reboot device in recovery
Mount /system partition
Move the new framework-res.apk you generated to replace the old one in /system_root/system/framework/framework-res.apk
I've wiped dalvik cache (I don't know if it's needed, but just in case...)
Reboot device and check if all is still working
If everything is ok you can proceed, otherwise return to recovery and just put the original `framework-res.apk` again
Install Bromite WebView apk from official site https://www.bromite.org/system_web_view
Now you need to make Bromite WebView system apps, to do it I've installed the magisk module app-systemizer and rebooted device
[MODULE][Terminal] App Systemizer v17.3.1
[Terminal] App Systemizer Terminal App Systemizer systemizes Apps systemlessly! This is inspired by App Systemizer by stangri. I then decided to make a script/UI in Terminal emulator for it to make 'app systemizing' easier. How to use...
forum.xda-developers.com
On pc with adb shell or in terminal emulator you can launch su -> systemize
and following the instructions you can move the bromite webview in system/apps
I rebooted and everything works, the bromite webview is selectable from the developer settings
In the meantime, an update of the webview has also been published and installing it like any other apk it applies correctly
thanks to lost101 for inspiring part of this guide with this other guide https://forum.xda-developers.com/t/...ut-breaking-animations-in-stock-roms.3455024/ (I made some changes to its steps but the idea behind it is the same)