Related
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.
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]:
Hi, i tried so many ways to edit my gps.conf without success.
What i do:
1. copy my gps.conf to /sdcard/
2. boot to twrp
3. mount /system and /vendor with write permissions
4. cp /sdcard/gps.conf /system/vendor/etc/gps.conf
5. cp /sdcard/gps.conf /system/etc/gps.conf
5. reboot
6. nothing changed!! WTF??
Phone: xiaomi Mi 5
ROM: Miui global dev 8.8.23
TWRP: twrp-3.2.3-0-gemini
Others things i tried
1. install magisk
2. go to solid explorer and copy my gps.conf to the system files
3. uninstall magisk
4. gps.conf system files reverted!! WTF?
Also i tried to push my gps.conf with adb without succes.
So i think the easiest way is with twrp right?
pd: i dont have root because i play Pokemon Go
pd2: sorry for my bad english
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
I was in the process of rooting when the update was trying to run. Now I keep getting an install failure and can't seem to get any way to fix it.
Where is this update stored so I can delete it or can I get some advice on how to clear it so I can get it to try again?
I can't find the update for download anywhere :/
Not thing about file/cache. Incremental OTA need unroot frist.
Looking for the full installer package file for
11.0.8.12.KB05AA.
rezapatel said:
Looking for the full installer package file for
11.0.8.12.KB05AA.
Click to expand...
Click to collapse
Same let me know if you find it lol
OK good news I got myself sorted!
1. What I did was use "Oxygen OS updater" (can be found on playstore) with advanced mode enabled and downloaded the latest OS (11.0.8.11.)
2. Use local upgrade under settings to install 11.0.8.11 and restart. This will remove root but not user data or settings.
3. Check for and install update 11.0.8.12 under settings and it should install fine no issues.
4. Re root using your chosen method.
5. Done!
Interesting. How did you get the boot file for x.12? Isn't that required for rooting..
rezapatel said:
Interesting. How did you get the boot file for x.12? Isn't that required for rooting..
Click to expand...
Click to collapse
Boot modified recovery with ADB function, dump boot_a or boot_b, Magisk patch.
ULTRAJC said:
Boot modified recovery with ADB function, dump boot_a or boot_b, Magisk patch.
Click to expand...
Click to collapse
What they said
ULTRAJC said:
Boot modified recovery with ADB function, dump boot_a or boot_b, Magisk patch.
Click to expand...
Click to collapse
Any guide for this?
DroidFreak32 said:
Since we don't have TWRP yet for our 8T, having ADB enabled on the stock recovery can be really helpful if you are unlocked and rooted.
For example, removing problematic magisk modules.
I tried to install the EdExposed module and ended with a boot loop. To get back I had to flash the stock boot.img again and reconfigure all my modules again.
Having ADB enabled in OOS recovery will let us delete the problematic module at /data/adb/modules without having to delete the working modules.
Credit goes to @s3axel for the Post in Oneplus 8 forums
Quoting the procedure to create the modified recovery.img :
Installation Procedure:
Pre-patched files for the lazy (upto 11.0.4.5):
To find your model and build:
Code:
adb shell getprop ro.product.model
KB2001
adb shell getprop ro.build.version.ota
OnePlus8TOxygen_15.I.16_GLO_0160_2010150110
KB2000 / KB05?? - Chinese Variant
11.0.1.2 Hydrogen_15.H.16_OTA_0160_all_2010150101_4101
STOCK recovery.img
adb patched recovery
KB2001 / KB05DA - Indian Variant
11.0.1.2 - OnePlus8TOxygen_15.I.16_GLO_0160_2010150110
STOCK recovery.img
adb patched recovery
11.0.2.3 - OnePlus8TOxygen_15.I.17_OTA_0170_all_2010240047
STOCK recovery.img
adb patched recovery
11.0.3.4 - OnePlus8TOxygen_15.I.18_OTA_0180_all_2011010208
STOCK recovery.img
adb patched recovery
11.0.4.5 - OnePlus8TOxygen_15.I.19_OTA_0190_all_2011101438_3032f.zip
STOCK recovery.img
adb patched recovery
KB2003 / KB05BA - EU Variant
11.0.1.2 - OnePlus8TOxygen_15.E.17_GLO_0170_2010150108
STOCK recovery.img
adb patched recovery
11.0.2.3 - OnePlus8TOxygen_15.E.18_OTA_0180_all_2010240038
STOCK recovery.img
adb patched recovery
11.0.3.4 - OnePlus8TOxygen_15.E.19_OTA_0190_all_2011010157
STOCK recovery.img
adb patched recovery
11.0.4.5 - OnePlus8TOxygen_15.E.20_OTA_0200_all_2011101442_ed5dc.zip
STOCK recovery.img
adb patched recovery
KB2005 / KB05AA - International Variant thanks to @card13
https://drive.google.com/drive/folders/1-i4P8sWPfyqwgYvBsKWAAftQW7m66Z70?usp=sharing
KB2007 / KB05CB - T-Mobile Variant
¯\_(ツ)_/¯
Code:
❯ adb devices
List of devices attached
75317573 recovery
❯ adb shell
# df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 3648448 40396 3608052 2% /
tmpfs 3837328 1160 3836168 1% /dev
tmpfs 3837328 0 3837328 0% /mnt
tmpfs 3837328 0 3837328 0% /apex
tmpfs 3837328 4 3837324 1% /linkerconfig
tmpfs 3837328 24 3837304 1% /tmp
/dev/block/sda11 491464 140484 350980 29% /mnt/vendor/op2
/dev/block/sda20 11760 164 11596 2% /metadata
/dev/block/dm-3 1516540 1511956 4584 100% /vendor
/dev/block/sda2 27632 10452 17180 38% /mnt/vendor/persist
/dev/block/dm-7 110397292 6627020 103770272 7% /data
Click to expand...
Click to collapse
Mpolo87 said:
CAVEAT
I've only tested this on my device (KB2005 / KB05AA), but it should be universally helpful as it's using your own boot.img so there's no need to find a matching package for your variant and os version.
CREDIT
The steps were buried across a few threads, I'm posting this so it'll be easier for others to find the information. All credit goes to xb360, FullOfHell, and TheUnkn0wn.
INFOThe basic rundown is:
Use the semi-broken TWRP package to give yourself temporary su access through adb.
Extract the boot.img your phone is currently using to your pc.
Reboot to OxygenOS, copy over the boot.img you just extracted and then use Magisk to patch it.
Copy the boot.img back to your pc and use adb to temporarily boot your phone with it, giving you root access until reboot.
Use your temporary root access to allow Magisk to patch your internal as-yet unmodified boot.img to give you permanent root.
There seems to be some confusion in the thread, I'll try to clear up what's happening and why:
The primary issue at hand is that you can't root your device without already having root privileges, for security reasons. Without a custom recovery like TWRP, there are a few more steps than usual (but mostly simple stuff).
Because we don't flash anything with this guide, it shouldn't cause any permanent bootloops if you use the wrong boot.img, if you get stuck in one just power cycle your phone.
Updating with OTAs should be the same process as the other guides here.
Because of changes in Android, devices that launched with Android 10 and above will not allow you to modify the system partition, even with root. This is not a fault of this rooting method.
Prerequisites:
ADB and Fastboot installed.
An unlocked bootloader and USB debugging enabled.
________________________________________________________
STEPS:
1. Connect your phone to your pc and boot it into fastboot mode. You can leave it connected throughout this guide.
2. On your computer open a terminal/cmd prompt. Set the directory (on your pc) you want to work from, I'm using the desktop:
for Windows, type cd C:\Users\Yourname\Desktopfor Mac, type cd desktop or cd /Users/yourname/Desktop
Spoiler: How to set up adb and fastboot properly
To usb adb and fastboot commands outside of the folder those programs are located in, you'll need to add their location to the PATH list so your terminal can still find them when it's pointing to a different folder. If you want to skip this step, set the directory to the folder that contains adb instead of the desktop.
3. Next, use the terminal to check which A/B partition is active on your phone:
Code:
fastboot getvar all
a. You'll find it on this line: (bootloader) current-slot:a/bb. For simplicity I'll be referring to boot_a.img throughout the guide, make sure to use boot_b.img if that's the one marked as active on your device.
4. Download the semi-broken TWRP package to your desktop. We'll be using it to extract a copy of your active boot_a.img. It will give you temporary su access via adb, but there won't be a gui. Only boot from it, DO NOT FLASH IT:
Code:
fastboot boot recovery.img
adb shell
dd if=/dev/block/by-name/boot_a of=/sdcard/boot_a.img
exit
adb pull /sdcard/boot_a.img boot_a.img
adb reboot
5. Copy the extracted boot_a.img file to a user accessible area of your phone, like your downloads folder.
6. Install the latest Magisk Canary apk on your phone. Open it and:
a. Select the Install option.b. Use Select and Patch a File on boot_a.img
7. Copy the patched magisk_patched_a.img file back to your computer. In terminal, type adb reboot bootloader to get back to fastboot mode.
8. Temporarily boot with the patched image that corresponds to the active partition, DO NOT FLASH IT:
Code:
fastboot boot magisk_patched_a.img
Spoiler: Why we're booting and not flashing.
You could flash this boot.img, but it's safer to temporarily boot from it without overwriting your existing image in case anything went wrong along the way. The effect is that you still get root access without modifying your device, and then you can use the much safer Magisk direct install option, which has some safeguards in place.
9. By booting with the patched image, you now have temporary root access. To make it permanent open Magisk:
a. Select the Install option.b. Use Direct Install (Recommended) to root your internal boot.img
10. Reboot and verify it worked.
Click to expand...
Click to collapse
Are you guys aware of the zip file @osm0sis created that lets you add ADB to the stock recovery? You'll need to be rooted to use it.
[TWRP][3.4.0-14][instantnoodle]Unofficial TWRP for OnePlus 8/8 Pro Unified(Stable)
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
It works really well - I've used it on 11.0.8.11 and .12
Thank you sir. I took the plunge and have been rewarded. Appreciate it!
shadowtuy said:
OK good news I got myself sorted!
1. What I did was use "Oxygen OS updater" (can be found on playstore) with advanced mode enabled and downloaded the latest OS (11.0.8.11.)
2. Use local upgrade under settings to install 11.0.8.11 and restart. This will remove root but not user data or settings.
3. Check for and install update 11.0.8.12 under settings and it should install fine no issues.
4. Re root using your chosen method.
5. Done!
Click to expand...
Click to collapse
This looks like a great app but it won't work if you need to downgrade. The current release (11.0.8.12.KB05AA) is so bad (look at OnePlus forums) that OnePlus has even taken it down and is no longer available for download. The current one is the previous one (11.0.8.11.KB05AA). Because I have already installed the "12" release, the OxygenOS System Update will not let me downgrade to the "11" release. It gives a "to avoid booting up failure, downgrading is not allowed" message.
Can I sideload/flash this "11" zip file via ADB and accomplish my goal of downgrading? Or could I change the active slot to the inactive one, reboot and get back to "11" that way?
zzjea said:
This looks like a great app but it won't work if you need to downgrade. The current release (11.0.8.12.KB05AA) is so bad (look at OnePlus forums) that OnePlus has even taken it down and is no longer available for download. The current one is the previous one (11.0.8.11.KB05AA). Because I have already installed the "12" release, the OxygenOS System Update will not let me downgrade to the "11" release. It gives a "to avoid booting up failure, downgrading is not allowed" message.
Can I sideload/flash this "11" zip file via ADB and accomplish my goal of downgrading? Or could I change the active slot to the inactive one, reboot and get back to "11" that way?
Click to expand...
Click to collapse
Well I tried switching slots but the inactive slot was corrupted from earlier. So I do not have an "11" in the other slot.
zzjea said:
Well I tried switching slots but the inactive slot was corrupted from earlier. So I do not have an "11" in the other slot.
Click to expand...
Click to collapse
Since OP 8T OxygenOS does not have a recovery, ADB sideload will not work.
Now that 11.0.8.13 is out and I'm on 11.0.8.12 right now, and so far I haven't come across a full zip for 13 yet. Not sure, if this will work .. but I'm thinking, I will uninstall magisk via the app. Restart to ensure, I'm unrooted and then do an OTA to 13. After the OS has been upgraded, follow the steps to root the boot dump file. Anyone tried this method and if would work? The 2 things I'm worried about are - 1) if I uninstall Magisk via the app, does it fully unroot and allows OTA, 2) will the broken twrp shared above work on the latest OOS x.13?
Thanks!
rezapatel said:
Now that 11.0.8.13 is out and I'm on 11.0.8.12 right now, and so far I haven't come across a full zip for 13 yet. Not sure, if this will work .. but I'm thinking, I will uninstall magisk via the app. Restart to ensure, I'm unrooted and then do an OTA to 13. After the OS has been upgraded, follow the steps to root the boot dump file. Anyone tried this method and if would work? The 2 things I'm worried about are - 1) if I uninstall Magisk via the app, does it fully unroot and allows OTA, 2) will the broken twrp shared above work on the latest OOS x.13?
Thanks!
Click to expand...
Click to collapse
For anyone who's interested. This worked!
Hey little bit of an add in! Keep a backup of your non Rooted boot.img!! It is actually easier to flash the non rooted and update just to reroot again.