Database Info

[HELP] Repacking boot.img on windows

been following amon's instructions (the one that was used for cyanogen's 32a mod)... modifying them a bit for windows... downloaded strawberry perl and when i run repack-H.pl i get an error saying it can't find the mkbootimg-H file... so i was wondering where i should put this so that strawberry perl can get at it
Thanks a lot... first time developer here

I keep it in my /tools/ dir with the repack script.

ok so i've navigated to my folder with boot.img-kernel and the boot.img-ramdisk folder and i'm running the command
perl C:\Users\*my user name *\Desktop\aoeu\android\tools\repack-H.pl boot.img-kernel boot.img-ramdisk boot.img
and i'm getting 2 errors...
'cpio' is not recognized as an internal or external command, operable program or batch file (i figure this is because i'm on windows... haven't found a solution for this yet but i'm sure i can get cpio for windows somewhere)
and 'mkbootimg-H' is not recognized as an internal or external command, operable program or batch file.
would love help in any way... as i've said i'm running windows 7 with strawberry perl installed...
*edit* if this helps i'm trying to put together a rom that has hofo kernel v2 on top of jacheroski 2.1

I don't think you can repack ROM's in Windows. You can get VirtualBox and install a Linux distro using it.

hotweiss said:
I don't think you can repack ROM's in Windows. You can get VirtualBox and install a Linux distro using it.
Click to expand...
Click to collapse
damn lol i did my best to make it work... virtualbox here i come!

Phil_McRevis said:
damn lol i did my best to make it work... virtualbox here i come!
Click to expand...
Click to collapse
Install Linux Mint in virtualbox, as it has most of the things you need out of the box.
www.linuxmint.com
Download the port tools:
http://www.4shared.com/file/122118622/fd190fe1/PortTools.html
Download the Linux Android SDK.
Go into your home folder and type this in:
sudo gedit .bashrc
Click to expand...
Click to collapse
Add this line at the end:
export PATH=${PATH}:/home/phil/android-sdk-linux_x86-1.5_r3/tools
Click to expand...
Click to collapse
Copy all of the port tools in your tools directory, except the sign app.
Right-click on them and make them executable.
Repack and unpack as you please.
When you sign them, you have to copy the three signing files in the directory with the zip.
That's the most of it.
PS-VirtualBox is a bit lacking when on a Windows 7 host. Your USB devices might not be seen, and folder sharing is very difficult to set-up. So you'll most likely have to do all of your work on the Linux guest, upload it, and then download it on your Windows host.

Phil_McRevis said:
been following amon's instructions (the one that was used for cyanogen's 32a mod)... modifying them a bit for windows... downloaded strawberry perl and when i run repack-H.pl i get an error saying it can't find the mkbootimg-H file... so i was wondering where i should put this so that strawberry perl can get at it
Thanks a lot... first time developer here
Click to expand...
Click to collapse
mkbootimg-H is a linux binary, it will not run on Window$
Just install Ubuntu using wubi instead of a virtualbox.
Wubi allows you to install and uninstall Ubuntu as any other Windows application. This is a much easier approach as a slow virtualbox.

http://www.whylinuxisbetter.net/

[ADB+FASTBOOT Binaries] for OS X inclusive installer

Hello,
I couldn't find an up to date thread with this, so I decided to create it.
I uploaded the newest adb and fastboot binaries out of the Android SDK for OS X and Linux and wrote a little script, which installs it for you.
You can find the script and the binaries here: https://github.com/simmac/minimal_adb_fastboot
I will try to keep the binaries up to date! You can help me by posting an answer as an heads up, I will do the rest.
How to install:
Download the zip
unzip it
cd to the directory (probably Downloads/minimal_adb_fastboot ) *
Start the shell script with ./install.sh
*You don't longer have to do this. Since v1.1 you can call the script with /path/to/script/./install.sh . (eg Downloads/minimal_adb_fastboot-master/./install.sh )
You can either download the zip directly ( https://github.com/simmac/minimal_adb_fastboot/archive/master.zip ) or clone the repository ( https://github.com/simmac/minimal_adb_fastboot ).
[LEGACY] Installer Package! You can now install the binaries via my installer package, which simply copies the binaries to /usr/bin. Download: https://github.com/simmac/minimal_a...nload/1.1.1/Quick_ADB-Fastboot_Installer.mpkg NOTE: The package isn't supported anymore, please use the script!
NOTE: This is for OS X and Linux!
I hope I help you with this.

Changelog:
15.11.2014: Initial release with adb version 1.0.32
16.11.2014: v1.1 allows you to call the script from everywhere
23.11.2014: v1.1.1: Name changed to "Quick ADB / Fastboot installer" due to name conflict with "Minimal ADB and Fastboot"
[*]10.03.2015: v1.2: Update to Platform-Tools v22 and adjustments to the script.
13.03.2015: v1.2.1 Improved version check
14.03.2015: v2.0: Linux support! (experimental)
31.05.2015: v3.0: Major code cleanup, uninstaller and more

v1.1 release
I just released v1.1 of my script.
Changes: The script can now be called from everywhere, you don't have to navigate to the folder anymore.

Thanks! Working great for me.

Good to hear, @JennyLikesSka !

Excellent. The first link on Google didn't support sideload but this did so thanks so much!

AlecRobertson said:
Excellent. The first link on Google didn't support sideload but this did so thanks so much!
Click to expand...
Click to collapse
You are welcome!
That's exactly why I made this I couldn't find the newest Binaries anywhere, so I downloaded the whole SDK and extracted the bins.
Maybe a mod wants to pin the thread?

v 1.1.1 release notes + installer package
I just released v1.1.1, which changes the name to "Quick ADB/Fastboot installer" due to name conflict with the "Minimal ADB and Fastboot" tool.
Also, I did some cleanups in the code and made an installer package, which simply copies the binaries in /usr/bin.
Download the installer package here: https://drive.google.com/file/d/0B_i0YdEB_NoQVklSNldvRTVpZU0/view
And the normal command line installer here: https://github.com/simmac/minimal_adb_fastboot/archive/1.1.1.zip

I run accross the issue with flashing my N5 with stock 5.0 and adb needing to be updated to 1.0.32
I have downloaded and run command prompts up to where it says - Installation completed successfully! adb version 1.0.32 is now installed.
I then tried to flash again, but still get the error to update my adb?

simmac said:
I just released v1.1.1, which changes the name to "Quick ADB/Fastboot installer" due to name conflict with the "Minimal ADB and Fastboot" tool.
Also, I did some cleanups in the code and made an installer package, which simply copies the binaries in /usr/bin.
Download the installer package here: https://drive.google.com/file/d/0B_i0YdEB_NoQVklSNldvRTVpZU0/view
And the normal command line installer here: https://github.com/simmac/minimal_adb_fastboot/archive/1.1.1.zip
Click to expand...
Click to collapse
The package won't open on my mac. Just get an error message.

@dholm: How do you run adb/fastboot?
With "adb" or "./adb"?
@JennyLikesSka: Which Message?
Did you try open it with rightclick - > Open?
Which OS X version do you run?

simmac said:
@dholm: How do you run adb/fastboot?
With "adb" or "./adb"?
@JennyLikesSka: Which Message?
Did you try open it with rightclick - > Open?
Which OS X version do you run?
Click to expand...
Click to collapse
./adb

dholms said:
./adb
Click to expand...
Click to collapse
I see, that's your error.
With installing adb, you don't have to execute it with ./ before the command name, simply type in the command via "adb" .

Ha I will give that a try, thanks!

dholms said:
Ha I will give that a try, thanks!
Click to expand...
Click to collapse
Do this, please report back, also if it worked.

simmac said:
Do this, please report back, also if it worked.
Click to expand...
Click to collapse
It got passed my previous issue, but it now shows
E: footer is wrong
E: signature verification failed
Install aborted
My steps were
1. Install 5.0 (LRX21O) from here - https://developers.google.com/android/nexus/images
2. Install Android SDK from here - https://developer.android.com/sdk/index.html
3. Rename folders (1 = ota.zip and 2= android)
4. Copy ota.zip to platform-tools folder
5. Run terminal commands (cd /Users/*username*/Desktop/android/sdk/platform-tools -> adb devices -> adb reboot-bootloader -> put into recovery then hold power button and tap volume up -> install from adb -> adb sideload ota.zip

@dholms: Seems like an issue with your update.zip. Are you rooted?

simmac said:
@dholms: Seems like an issue with your update.zip. Are you rooted?
Click to expand...
Click to collapse
Lock state was unlocked to install DP of 5.0 - That was it...
Edit: seems this might be the issue - http://forum.xda-developers.com/google-nexus-5/help/e-footer-wrong-t2938236

dholms said:
Edit: seems this might be the issue - http://forum.xda-developers.com/google-nexus-5/help/e-footer-wrong-t2938236
Click to expand...
Click to collapse
Yeah, seems so, you may have to flash the image.
But my Installer worked, right?

simmac said:
Yeah, seems so, you may have to flash the image.
But my Installer worked, right?
Click to expand...
Click to collapse
Yes it did, thank you very much!

[Emulator][Root][How-To] BlueStacks 0.9.x + pre-rooted 0.9.30.4239 image

This How-To briefly describes a way to manually root recent BlueStacks without any third-party apps. All you need is a linux distro (you can use VirtualBox virtual machine) and SuperSU CWM flashable. I won't go into much details, some little linux know-how is needed, but you can always google for what you don't understand, since the required steps are fairly simple. I also share a pre-rooted BlueStacks 0.9.30.4239 image for the lazy ones
This How-To assumes you already have an installed BlueStacks you wish to root, but make sure it isn't running. So, let's get started
1. Copy over UPDATE-SuperSU-v2.46.zip and BlueStacks Root.fs to your linux box: in Windows it is typically located at "C:\ProgramData\BlueStacks\Android\Root.fs". If you're using VirtualBox, I suggest you use a shared folder to copy the image over to the guest linux OS.
2. As root, unpack UPDATE-SuperSU-v2.46.zip and mount Root.fs as a loop device.
3. Now we need to copy over (as root) some of the extracted files to the mounted Root.fs:
arm/su --> android/system/xbin/su
arm/su --> android/system/xbin/daemonsu
arm/supolicy --> android/system/xbin/supolicy
arm/libsupol.so --> android/system/lib/libsupol.so
common/Superuser.apk --> android/system/app/Superuser.apk
4. Since there's no init.d structure in BlueStacks, we need to edit android/system/etc/init.sh: at the buttom of the file find these lines:
Code:
init|"")
do_init
;;
esac
and insert one line after 'do_init':
Code:
init|"")
do_init
/system/xbin/daemonsu --auto-daemon &
;;
esac
5. Unmount the loop device and copy the modified Root.fs over to your BlueStacks Android dir (typically, "C:\ProgramData\BlueStacks\Android" in Windows). You may want to make a backup of the original file just in case.
6. Start BlueStacks and launch SuperSU via Play Store: it will prompt for upgrading su binary --- choose the normal way and restart BluseStacks upon completion.
7. That's it, you're rooted! Now you may wish to install a proper launcher (like Nova Launcher) if you have not done so already.
Now, as promised, you can grab pre-rooted BlueStacks 0.9.30.4239 Root.fs from here:
https://www.mediafire.com/folder/bc7hjf0a8lgnq/BlueStacks_Root
Stop BlueStacks, copy Root.fs over to your BlueStacks Android dir, and start BlueStacks. In case your current version is incompatible with the image, try BlueStacks-ThinInstaller_0.9.30.4239.exe from the link above. I'm not sure whether this ThinInstaller will download the proper data when newer version is released, so no guarantees here, you may still need to do it manually at some point in the future unless I maintain the Root.fs actual.

200+ people downloaded rooted image already, and not a single response yet. Some feedback would be appreciated, you know

Serkenar said:
200+ people downloaded rooted image already, and not a single response yet. Some feedback would be appreciated, you know
Click to expand...
Click to collapse
Thanks, worked perfect for me

thanks replace root.fs works for me, was using 9.27.5408

mac-duff said:
Thanks, worked perfect for me
Click to expand...
Click to collapse
netsee said:
thanks replace root.fs works for me, was using 9.27.5408
Click to expand...
Click to collapse
Great, I'm glad that it works. Thanks for the feedback!

link for zip is broken

[APP][Root][4.4 & 6+ & 7.0+ & 8.0.0] Tera - A cloud file system for unlimited storage

Tera is a cloud file system with unlimited storage size by extending the storage blocks to the cloud.
We recently released Tera ROM for Nexus 5x Post Here. However, it requires that you wipe the phone in order to install it. Not to mention that it works only on Nexus 5X.
After some serious effort, we have successfully crafted a new version that works on most Android phones without having to wipe them! All you need is root access. It is easy to install and uninstall, without the need of backing up your data, or the fear of destroying your existing files.
Changelog
2017.09.27 First release.
2017.10.03
Make phone permission is not necessary.
Support click to install in windows bat file.
2017.10.13
Add debug log for support new devices.
Improve stability for install script.
Support Android 7.0
2017.10.18
Support Android 6.0.X
solve problem with `adb push` in Windows
2017.11.02
Change adb push to push one file at once, some device don't support multiple files.
Support 32bit device.
2017.11.08
Repacking 32-bit version with correct share library
2017.11.14
Fix command issue in specific ROM
Tera-root has been tested on these devices:
Nexus 5X Android 8.0.0
Nexus 5X Android 7.1.2
Nexus 5X Android 7.1
Nexus 5X Android 7.0.0
Nexus 5X Android 6.0.1
Nexus 5X Android 6.0.0
Nexus7 Android 4.4.4
Nexus7 Android 4.4
Nextbit Robin Android 7.1.1
Samsung SM-T211 Android 4.4.2
Feature
Root-tera differs from the original LG Nexus 5X version Post Here in the following ways:
Root-tera uses a separate location (see below) to store its data so it won’t affect your existing data. Depending on the Android version, the location may be:
/sdcard/MY-TERA
/MY-TERA
/storage/MY-TERA
This directory can be accessed by any app.
Original functions that still work the same way:
Tera extends your phone storage to the cloud and makes your local storage look as big as your cloud storage.
Tera can use Google drive or Openstack Swift as backend storage. Just choose the one you want from the Tera app, and follow the setup instructions.
Guide
Reminders:
Grant the permission requests when they are shown.
If something’s not working, check the permission setting of SuperSu and the Tera app.
Installation steps:
Make sure the device is ROOTed and has SuperSu by TWRP installed.
Connect to the device through adb.
Download the Root-tera package and unzip.
Package for 7.1+ & 8.0.0 64 bit Link Here
Package for 7.1+ & 8.0.0 32 bit Link Here
Package for 6.0.x & 7.0.0 64 bit Link Here
Package for 6.0.x & 7.0.0 32 bit Link Here
Package for 4.4.X 32 bit Link Here
In root-tera directory, execute ./setup.sh install (Linux/Mac) or setup.bat install (Windows).
Grant permissions in SuperSU and wait for installation to finish. (In some cases it might fail on the first attempt. Don’t worry, just uninstall and then try install again.)
Open Tera app and grant permsssions again.
If you’re using Google Drive as your backend, you’ll be taken to a browser window and asked to log in to your Google Drive account.
Login and enjoy. Any app can use /sdcard/MY-TERA to store anything you like.
If you can’t see MY-TERA directory through MTP, go to Settings - Apps, in the “...” drop down menu on the top-right corner, select “Show System”, scroll down to select “Media Storage”, tap “Storage", then tap “CLEAR DATA” to clear the SD card directory cache. Reboot the device and wait for the system to rebuild the SD card directory cache. It may take a few minutes.
Uninstallation steps:
All data in /sdcard/MY-TERA will be DELETED, in the device and in the cloud.
Connect to the device through adb.
In root-tera directory, execute ./setup.sh uninstall (Linux/Mac) or setup.bat uninstall (Windows).
That's all.
The data on the backend are still there and need to be removed manually. If you reinstall Root-tera, you will see a fresh start on your device.
XDA:DevDB Information
Tera-AllDevice, App for all devices (see above for details)
Contributors
fineaisa
Version Information
Status: Beta
Current Beta Version: 0.11.4
Beta Release Date: 2017-11-13
Created 2017-09-27
Last Updated 2017-11-13

Reserved
I will try this when i get back to home!
btw, you said SuperSU but i use Magisk will it get Root access (i mean support Magisk)??
Thanks for this anyway
@fineaisa
I am not able to install sir
Device: Redmi Note 3 (SD kenzo)
ROM: RR Final Nougat 7.1.2
i think my device is not supported by your great tool :crying:

xN00Bx said:
Reserved
I will try this when i get back to home!
btw, you said SuperSU but i use Magisk will it get Root access (i mean support Magisk)??
Thanks for this anyway
@fineaisa
I am not able to install sir
Device: Redmi Note 3 (SD kenzo)
ROM: RR Final Nougat 7.1.2
i think my device is not supported by your great tool :crying:
Click to expand...
Click to collapse
From you screenshot, that operation is not support with direct click it.
You have to open a cmd and go to root-tera dir and type `setup.bat install`
In Root-Tera dir's address and type cmd
C:\root-tera-0.10.1-7+>setup.bat install
I think we will make setup.bat more simple in next release
Thank for your feedback,

My PC Is not working.. Can't I do this from my android device?

vraciu' said:
My PC Is not working.. Can't I do this from my android device?
Click to expand...
Click to collapse
Can you take a screenshot for your situation
and what operations you do? what kind of OS?

fineaisa said:
Can you take a screenshot for your situation
and what operations you do? what kind of OS?
Click to expand...
Click to collapse
I was just asking If I can install this without a pc. Without running that bat file from pc

vraciu' said:
I was just asking If I can install this without a pc. Without running that bat file from pc
Click to expand...
Click to collapse
Sorry my fault.
You can't install without a pc/mac and android device bridge

fineaisa said:
Sorry my fault.
You can't install without a pc/mac and android device bridge
Click to expand...
Click to collapse
I've seen the sh file and I saw that the script is pushing some files using ADB.. Can't I move those files manually?

Welp, nothing. It just fails

vraciu' said:
I've seen the sh file and I saw that the script is pushing some files using ADB.. Can't I move those files manually?
Click to expand...
Click to collapse
Yes, you can! but be careful, if you trying on a phone with your data.
Our script is tested which not affect your data and make installation as easy as possible.

xxxCrimeDogxxx said:
Welp, nothing. It just fails
Click to expand...
Click to collapse
What kind of device and ROM ?

fineaisa said:
What kind of device and ROM ?
Click to expand...
Click to collapse
Samsung Galaxy A800i, AOSP

Plz input install or uninstall:install
install
uid=0(root) gid=0(root) groups=0(root) context=u:r:su:s0
failed to copy 'files/hcfs' to 'files/hcfsapid': secure_mkdirs failed: No such f
ile or directory
Tera Install Fail
Press any key to exit...
Sony Xperia XA
Android 7.0

xxxCrimeDogxxx said:
Samsung Galaxy A800i, AOSP
Click to expand...
Click to collapse
Sorry, I forget to ask android version...
But AOSP ROM we may build it to try in emulator.
btw, this release 0.10.2 not support Android 7.0 yet.

vraciu' said:
Plz input install or uninstall:install
install
uid=0(root) gid=0(root) groups=0(root) context=u:r:su:s0
failed to copy 'files/hcfs' to 'files/hcfsapid': secure_mkdirs failed: No such f
ile or directory
Tera Install Fail
Press any key to exit...
Sony Xperia XA
Android 7.0
Click to expand...
Click to collapse
Sorry this version not support Android 7.0
but we are woking on that
next release will support!!!

fineaisa said:
Sorry, I forget to ask android version...
But AOSP ROM we may build it to try in emulator.
btw, this release 0.10.2 not support Android 7.0 yet.
Click to expand...
Click to collapse
No problem
Also for my other phone when will you release for lollipop and marshmallow

uid=0(root) gid=0(root) groups=0(root) context=u:r:su:s0
failed to copy 'files/hcfs' to 'files/hcfsapid': secure_mkdirs failed: No such file or directory
Tera Install Fail
Press any key to exit...
I have a Nexus 5x with Android 7.1.2, I tried with windows and Linux, in both I have the same fail

fineaisa said:
Sorry this version not support Android 7.0
but we are woking on that
next release will support!!!
Click to expand...
Click to collapse
Oh, no problem. I didn't read the title so I didn't saw that is not supported

Couple of Suggestions
Failed on my HTC M8 running lineageOS 14.1, but I was able to play around with your shell scripts and here are my thoughts
- not sure if you needed to keep the directory structure or not, but I changed your setup.bat to push the files in the 'files' directory on sdcard. So the directory structure is the same.
- on my OS, /sdcard does not allow executing files, so I changed your install part of setup.bat to copy all the files to /data/local/tera, so my setup.bat now has:
:START_UP
adb shell su -c "rm -rf /data/local/tera"
adb shell su -c "(cd /sdcard ;tar cf - tera |(cd /data/local; tar xvf -))"
adb shell su -c "find /data/local/tera -exec chmod 777 {} \;"
adb shell su -c "/data/local/tera/tera %UserInput%"
I also edited the tera shell script to reflect this change. All works except now the hcfsconf reports: "/data/local/tera/tera[407]: /system/hcfs/hcfsconf: not executable: 64-bit ELF file ". neither of the versions you have posted work. If I try and just run it manually I get "sh: ./hcfsconf: not executable: 64-bit ELF file
"
Looking forward to the next version
-brad

Melfloc said:
uid=0(root) gid=0(root) groups=0(root) context=u:r:su:s0
failed to copy 'files/hcfs' to 'files/hcfsapid': secure_mkdirs failed: No such file or directory
Tera Install Fail
Press any key to exit...
I have a Nexus 5x with Android 7.1.2, I tried with windows and Linux, in both I have the same fail
Click to expand...
Click to collapse
wow, Is there different model for nexus 5x?
what is build number for your device?

[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]: