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]:
Related
Sorry English my "BAD"
Ground facebook: https://www.facebook.com/groups/1697660883795443/
Guide will support install rom international for Meizu MX4 , MX5 , MX4 pro Version A , U , C ......and more devices Meizu
Advantages: rather safe method, no Chinese applications, default Google Play Services, more supported languages i-rom in the near future.
Disadvantage: OTA-update not possible, (but you can always update manually).
Note: Here's how to do safe , You do not have to worry
Request:
+Rooted
+Busybox
+Driver ADB for PC because run you need command ADB
How to instal driver ADB for Meizu Devices
Note:Because English not good , pls see Guide Tks to @abaggie Meizufan
Step 1 : Enable Usb debug and Allow mock locations
Step 2: connect devices PC and choose connect CD/Rom
You can see CD driver , you install driver adb equal file in folder Usb driver
Step 3: at c: \ Users \ your name \ .android \
Creat or edit file adb_usb.ini
add a line
Code:
0x2a45
Step 4: check driver
Code:
adb kill-sever
Code:
adb devices
if cmd current "offline" you need install again driver
Step 4: download and copy file rom .img to storage
Step 5: run CMD and type command:
Code:
adb shell
Code:
su
Code:
dd if=/sdcard/system-i.img of=/dev/block/platform/xxxxx/by-name/system
Note : xxxxx leaves partition system
example : MX4pro (cpu exynos) : /dev/block/platform/15540000.dwmmc0/by-name/system
M2 note,mx4,m1note (cpu MTK) : /dev/block/platform/mtk-msdc.0/by-name/system
MX5:/dev/block/mmcblk0p18 or you can use dev/block/platform/mtk-msdc.0/by-name/system
We expect the end of the command (about 5 min . ) . After the download of the image will be prompted to enter a new team in the form of the sign '#' ;
Due to the fact that the section is replaced by a system hang smartphone . This is normal. Restart it long hold the power button , and wait for download smartphone. If your smartphone is not loaded within 15 minutes , you need to reset the settings of recovery stock ( volume down button + power button ) .
Step 6 : Now you need to reset your smartphone to factory settings. Settings - About phone - memory - factory reset . Put two checkboxes, and click " Start cleaning " .
Or reboot recovery stock and clear data
DOWNLOAD
Rom 4.5.4i for MX4 Pro: google driver
Rom 4.5.4i MX4pro use TWRP flash rom:Google driver
Rom 4.5.5i for MX4pro:Google driver
Meizu pro5 stock mod version I
4.5.4.2i: Download
M1 note: Download
MX5:Google driver
FW 4.5.2.7i Stable: Download
M2 note : Google driver
FW 4.5.3i :Link Mega
MX4 folder download: google driver
Folder run command ADB:Google driver
Meizu M1 note :Google driver
==================================================
Update tools One click auto converter system support creat system.img for meizu devices
Link download : Driver google
How to use:
Step1: Copy system.new.dat and system.transfer.list to folder "in"
Step2: Run System-conVERTER.dat
===============================
PS: Get link download max speed vietnam host Fshare: get link
Good idea!
update MX4 link rom
doesn't work... Says Permission denied.
this is the string:
[email protected]:/ $ su
su
enter main
start command :am start -a android.intent.action.MAIN -n com.android.settings/co
m.android.settings.root.RootRequestActivity --ei uid 2000 --ei pid 6904 > /dev/n
ull
[email protected]:/ # dd if=/sdcard/system-i.img of=/dev/block/platform/15540000.dwmm
c0/by-name/system
dcard/system-i.img of=/dev/block/platform/15540000.dwmmc0/by-name/system <
dd: /sdcard/system-i.img: Permission denied
I solved with the terminal emulator
ucb83 said:
I solved with the terminal emulator
Click to expand...
Click to collapse
you need flash on PC
no terminal emulator
Sent from my MX4 Pro using Tapatalk
I succeeded even with the terminal emulator. I finally managed to install via PC, great job, everything works.
Hum great... seem good new....
Envoyé de mon X98 Air 3G(C8J7) en utilisant Tapatalk
i will update rom version I use TWRP flash for mx4pro
Sent from my MX4 Pro using Tapatalk
what ROM? I don't understand how to do after the end of the command. What must i write? "#"?
TARAS88 said:
what ROM? I don't understand how to do after the end of the command. What must i write? "#"?
Click to expand...
Click to collapse
This is what i do but after when i see the sharp i reboot the smartphone and i see only the recovery.
Very great method...it worke great! Only issue is that I do not see Contacts for my google account....Any clue?...
THANKS IN ADVANCE!
popo72 said:
Very great method...it worke great! Only issue is that I do not see Contacts for my google account....Any clue?...
THANKS IN ADVANCE!
Click to expand...
Click to collapse
hi
you can install contacts google ...use file apk
i will update file apk app center
Sent from my MX4 Pro using Tapatalk
Really thanks....
What is the difference beentween the international version and the Chinese version? I'm using my phone in Norway, will this rom support Norwegian?
And if this rom is installed, will ota updates still work?
Thanks
I get "Permission denied" when trying to enter the last command in adb.
[email protected]:/ # dd if=/sdcard/system-i.img
c0/by-name/system
dcard/system-i.img of=/dev/block/platform/15
dd: /sdcard/system-i.img: Permission denied
HabueN said:
I get "Permission denied" when trying to enter the last command in adb.
[email protected]:/ # dd if=/sdcard/system-i.img
c0/by-name/system
dcard/system-i.img of=/dev/block/platform/15
dd: /sdcard/system-i.img: Permission denied
Click to expand...
Click to collapse
Install supersu or try with terminal emulator or try with twrp method.
ucb83 said:
Install supersu or try with terminal emulator or try with twrp method.
Click to expand...
Click to collapse
Will do that. But is there any advantages of installing the I ROM instead of A ROM?
Thanks for answers
stuck at step 4.
where i can find rom.img for meizu m2 note.?
only can find update.zip for international version
---------- Post added at 09:37 AM ---------- Previous post was at 09:27 AM ----------
ok found it. thanks
penyapu79 said:
stuck at step 4.
where i can find rom.img for meizu m2 note.?
only can find update.zip for international version
---------- Post added at 09:37 AM ---------- Previous post was at 09:27 AM ----------
ok found it. thanks
Click to expand...
Click to collapse
link download #1
Gửi từ MX4 Pro của tôi bằng cách sử dụng Tapatalk
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?
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.
This Guides are for People with Treble 8.1 ROM with SU from Treble Thread.
It's super simple and easy to Google out, but I'll write here for sum-up.
Magisk Root and Stock Camera is seperate GUIDE, you don't need to do both.
Magisk Root
1. download the patched_boot.zip I uploaded below and unzip, and jump to 3.
2. Fastboot flash ramdisk patched_boot.img
Q&A
Q. Why 'Patch Boot Image File' method?
A. Bcuz TWRP for Oreo is for 8.0 only or buggy for 8.1 at this point.
Q. What's the point of this guide?
A. Bcuz you may not know which file to patch, where to flash since huawei renamed BOOT to RAMDISK
TWRP for 8.1 GSI is there, you can use it with Magisk 16.7
For 9.0, There is no working TWRP so flash Magisk 16.7 from 8.0/8.1 before you go to 9.0 GSI.
if you having problems with certain apps at 9.0 GSI, It probably bcuz of which su, so use symbolic link.
open up adb, type
adb shell
su
mount -o bind /sbin/su /system/xbin/su
Q&A
Q. why mount -o? why not ln -s?
A. Bcuz ln -s did not worked, at least for me.
Q. will it last?
A. No. reboot will remove mount -o command so you need to do it again if you reboot.
stock Camera
1. Download the Stocam.zip file I uploaded below and unzip.
(source : https://forum.xda-developers.com/pr.../huawei-stock-camera-app-treble-roms-t3735169)
2. Install Zipsigner from Playstore and re-sign the apk file with auto-test
3. put .so files to vendor\lib64, re-signed .apk file to prive-app\HwCamera2, all permission 644 (rw-r-r)
Q&A
Q. What's the point of this guide?
A. Bcuz Honor 9 + 8.1 has quite a lot of things to do, and it's quite tough to read all the thread down to find out what to do.
Q. It's still not working.
A. Download OldDroid's files from the link below, copy-paste the files from system\lib64 and system\lib (not vendor\ !).
(https://mega.nz/#!7hQDhQAK!p2s7jQp9-nhp2-O1U2s2GrBB9UVBhgKDtFfHTq_CHvI)
for 9.0, there is no proper working stock camera port. you can try P20pro camera port mod.
it's Magisk module but not working, so you need to unzip and put HwCamera2 folder into /system/priv-app manually.
https://forum.xda-developers.com/honor-9/themes/app-port-p20-pro-camera-mod-root-t3777920
Modifying Android x86 rooted with Magisk
This thread is about android x86 from official website: https://www.android-x86.org/ and it's about rooting and modifying android x86.
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
Please continue this thread writting your ideas, guides, questions of modifying android x86.
Hello everyone!
Are you bored of stock su? Here you have instructions how to install magisk on android x86 pie (9)
In this post I'd like to share what I found on this website: https://asdasd.page/2018/02/18/Install-Magisk-on-Android-x86/ it's about installing magisk on android x86.
It's not my work, I just have rewritten it to XDA to be easier somebody to find information.
Also I checked is it working with newer version (for now 20.4) - yes
I have to admit, that on my android x86 modules aren't working.
Just superuser permissions management for other apps are ok. Don't know how to fix it and want community to help I'll share screenshots in close future and logs if someone can help me.
Prerequisite:
1. Linux environment
2. Partition r/w Android x86
3. Installed official Magisk Manager if I'm not wrong official project is here: https://github.com/topjohnwu/Magisk
Follow this steps to root your device with Magisk:
1. On Linux install android-tools-mkbootimg abootimg using command:
Code:
sudo apt install android-tools-mkbootimg abootimg
2. Open Android x86 folder with root permissions and copy the kernel and ramdisk.img file from the partition of the Android x86 to the created work folder on linux.
3. Open terminal as root in that folder
3. The following command will pack the boot.img of Android x86.
Code:
mkbootimg --kernel kernel --ramdisk ramdisk.img --output boot.img
4. Copy the extracted boot.img to the Android folder e.g downloads or documents
5. Reboot to android x86
6. In Magisk Manager choose Install ==> select patch to boot.img and click boot.img file.
7. After the operation, there should be a patched_boot.img or similarly named file in the same directory.
8. Reboot to linux
9. Open Android x86 folder with root permissions and copy patched_boot.img to another created folder on your linux. Open there terminal with root permissions.
10. Extract kernel and ramdisk from patched_boot.img file using the following command:
Code:
abootimg -x patched_boot.img
11. There should appear 3 new files in the folder after this operation.
12. Rename zImage to kernel and overwrite the one in the Android x86 partition. REMEMBER ABOUT the original permission
13. Rename initrd.img to ramdisk.img and overwrite the one in the Android x86 partition. REMEMBER ABOUT the original permission
14. Done! Reboot to Android and check if Magisk is installed in Magisk Manager app.
[Q]How to hide navigation bar in android x86 pie?
Hi everyone,
I tried to truly hide navigation bar in android x86 pie by editing build.prop located on system and vendor partitions adding line:
Code:
qemu.hw.mainkeys=1
The problem is it's not working.
Can you help me?
Important Update
I drop this subject as now I'm more interested in true Linux itself but I'll leave this thread open as closing needs messaging moderators and thre's no need to do the mess
@BigBrother84
I found a way to patch correctly, but I only tested it in VirtualBox.
https://github.com/shakalaca/MagiskOnEmulator
Thanks
HemanthJabalpuri said:
@BigBrother84
I found a way to patch correctly, but I only tested it in VirtualBox.
https://github.com/shakalaca/MagiskOnEmulator
Thanks
Click to expand...
Click to collapse
I tried before but failed
Where can I get the magisk.zip file for version 23.0 ?
NOTE: the used method I installed magisk.apk and then change the extension to .zip and I applied these codes but In the final result I got initrd.img (0kb) and ramdisk.img (1.82MB)
@HemanthJabalpuri please send me a guide on how to install magisk on android-x86_64-9.0-r2 in VirtualBox
to me too, please!!
If I installed android x86 with system writeable, there is no ramdisk.img and kernel file in the Android x86 partition.
So how where can I put these files to make the Magisk?
JuanLv said:
If I installed android x86 with system writeable, there is no ramdisk.img and kernel file in the Android x86 partition.
So how where can I put these files to make the Magisk?
Click to expand...
Click to collapse
Solved.
Mount the sda* (the partition you installed the Android x86), and the image file is there.
Ref: https://github.com/shakalaca/MagiskOnEmulator
BigBrother84 said:
Hello everyone!
Are you bored of stock su? Here you have instructions how to install magisk on android x86 pie (9)
In this post I'd like to share what I found on this website: https://asdasd.page/2018/02/18/Install-Magisk-on-Android-x86/ it's about installing magisk on android x86.
It's not my work, I just have rewritten it to XDA to be easier somebody to find information.
Also I checked is it working with newer version (for now 20.4) - yes
I have to admit, that on my android x86 modules aren't working.
Just superuser permissions management for other apps are ok. Don't know how to fix it and want community to help I'll share screenshots in close future and logs if someone can help me.
Prerequisite:
1. Linux environment
2. Partition r/w Android x86
3. Installed official Magisk Manager if I'm not wrong official project is here: https://github.com/topjohnwu/Magisk
Follow this steps to root your device with Magisk:
1. On Linux install android-tools-mkbootimg abootimg using command:
Code:
sudo apt install android-tools-mkbootimg abootimg
2. Open Android x86 folder with root permissions and copy the kernel and ramdisk.img file from the partition of the Android x86 to the created work folder on linux.
3. Open terminal as root in that folder
3. The following command will pack the boot.img of Android x86.
Code:
mkbootimg --kernel kernel --ramdisk ramdisk.img --output boot.img
4. Copy the extracted boot.img to the Android folder e.g downloads or documents
5. Reboot to android x86
6. In Magisk Manager choose Install ==> select patch to boot.img and click boot.img file.
7. After the operation, there should be a patched_boot.img or similarly named file in the same directory.
8. Reboot to linux
9. Open Android x86 folder with root permissions and copy patched_boot.img to another created folder on your linux. Open there terminal with root permissions.
10. Extract kernel and ramdisk from patched_boot.img file using the following command:
Code:
abootimg -x patched_boot.img
11. There should appear 3 new files in the folder after this operation.
12. Rename zImage to kernel and overwrite the one in the Android x86 partition. REMEMBER ABOUT the original permission
13. Rename initrd.img to ramdisk.img and overwrite the one in the Android x86 partition. REMEMBER ABOUT the original permission
14. Done! Reboot to Android and check if Magisk is installed in Magisk Manager app.
Click to expand...
Click to collapse
Just an FYI to all that this still works with Android-x86-9.0-r2. I did this on a Dell 3185 with Debian 11 installed. Thanks a million, OP!
Check out another simple and convenient way. If you got any error, please give feedback!
GitHub - HuskyDG/initrd-magisk: Integrate Magisk into Android-x86 project
Integrate Magisk into Android-x86 project. Contribute to HuskyDG/initrd-magisk development by creating an account on GitHub.
github.com