$111 OFF Over $111.11
V919 AIR V7 Brush tutorial _For_Android-V1.0 20150911.pdf
View File Onda Android system installation tutorial
Google Translated V919 AIR V7 Brush tutorial _For_Android-V1.0.pdf 20150911
from file : V919 AIR DualOS（64GB）_android4.4_V7_20150824.pdf
Submitter RobV Submitted 09/11/2015 Category V919 Air dual system
Hi, I'm back again with another particular guide, this time just for android, which will show how to root every V80 Plus rom, this time for real. You probably know that the other guides are not working anymore due to newer roms adding a new layer of protection against modifications. SuperSU zips can't detect this on Android 5.1 since this is something that is used in Nougat or Marshmellow
Also, I will also explain how to use newer roms updates (Like the Android V7 version) and make it work on V3 (My tablet) since there are minor hardware changes like the Wi-Fi chip and the touchscreen vendor, I will show how to port the V3 drivers on the V7 ROM which is more stable, and smoother.
Unix environment (Linux, MacOS, Cygwin/MinGW on Windows) I recommend Manjaro Linux, the AUR has all the programs we need here. ADB and Fastboot https://github.com/xpirt/img2sdat https://github.com/ggrandou/abootimg Unlocking bootloader Decent knowledge of ROM tweaking or at least in theory Basic Unix-like systems knowledge A BACKUP, you will lost all data on your device By following this guide I take no responsibility on device bricks or data loss
Common steps for both ROM tweaking and Rooting
The first thing you have to do is to unlock the bootloader, reboot your tablet from Android and press the down button to access the fastboot mode, then connect via USB the tablet to a PC, you have to enter this command in order to unlock the bootloader (You can also use this tool) also if you want to install TWRP follow his guide. ' fastboot oem unlock '
You will lose all data after oem bootloader unlocking
Now you have to extract your ROM boot.img by downloading the correct ROM image (http://onda.cn/search.aspx?keyword=v80%20plus) and using abootimg in Linux/MacOS/Cygwin/MinGW, I won't explain how to compile it.
What we have to do is basically extract the initrd and changing ro.secure=0 o ro.secure=1, which will allow for supersu to install without bootlooping and mounting system as rw, using modified system.img's and disable the protection which will put the device into a bootloop state
Type the following command to extract the boot.img (You must be on the same folder where you downloaded the boot.img)
' abootimg -x boot.img '
Now several files are created, we need to extract the initrd, put ' abootimg-unpack-initrd initrd.img '
Go into the ramdisk folder and look for default.prop, open it with a text editor
change ' ro.secure=1 ' to ' ro.secure=0 ' in the previous folder, type ' abootimg-pack-initrd initrd.modified.img '
This will create initrd.modified.img which includes your modifications, now you have to create a new boot.img with the modifications you made, with this command ' abootimg --create boot.edited.img -r initrd.modified.img -k zImage -f bootimg.cfg -c "bootsize=xxxxxx" '
Please note that in xxxx you have to put the new boot.img size, you can get the exact string by omitting the -c "bootsize=xxxxx" argument, which will give an error that will tell on the left the size you need to put, in my case it was
' abootimg --create boot.edited.img -r initrd.modified.img -k zImage -f bootimg.cfg -c "bootsize=11868160" '
for the V5 Kernel
If you have done everything correctly, we got a working boot.edited.img, to flash that into your device you need to go back to the bootloader like when we oem unlocked the device. Put this command from a PC ' fastboot flash boot boot.edited.img '
If everything went good, you just need to try to install supersu by flashing it with twrp or trying to mount as r/w the /system partition and see if it bootloops, if the rom does not even boot at all even if you just flashed the boot.img you did something wrong.
ROM Tweaking and porting Vy android firmware version to Vx tablet
Since I got really mad and frustrated by ONDA not releasing firmware also for older hardware revisions (Other may work for your older device, other may not) I decided to extract the drivers and firmware and put them to a newer rom, and it is worth the score. New firmwares are more smooth and stable.
As you know, some newer VX firmware ROM may not be compatible with your VY hardware revision device, in my example I had the V3 and I managed to use the V5 drivers (The V5 version works good with the V3 tablet hardware rev) to use the V7 firmware.
This may probably work also with a V5 tablet.
Don't know if this works with V1
Extracting drivers and files needed
Boot.img patching: In order to get drivers working, make sure you followed the steps for creating the modified boot.img kernel which works on your device, cause it is mandatory or you will get a bootloop.
Q: Can older boot.img/kernels work with newer/older firmwares?
A: Yes, they seems to be pretty similiar so in my example I used V5 boot.img in order to get drivers working for the V7 ROM which has a slightly different hardware
Without extracting the following files and firmware you will just have the touchscreen working, but not the wifi or the bluetooth, they require firmwares located into system files! And Without the boot.img you can't do anything with the new rom!
Once you downloaded every ROM you need, in my example I had the V3 Hardware revision, I will put V5 drivers which works too on V3 into the V7 ROM, this time we need to find and extract the system.img using simg2img by using this command, easier than saying it. ' simg2img system.img system.img.raw '
Now mount it as read-write with, ' mount -o rw system.img.raw /mnt '
I needed to extract the following files in order to have everything, copy them on the desktop, if unsure you could copy everything like /etc /lib/ /vendor / because I can't know if you are trying another ROM revisions, because they may require different files, find yours by yourself!
(This may be a lot of trial-and-error but the files should be the same, you could try that also with V1 to V5/v7, tell me if it works! Idk about other hardware revisions!)
--------------------------------- V5 ROM ----------------------------------------
/mnt/vendor - Other blobs needed /mnt/bin/wpa_supplicant - Needed for the wifi correctly working /mnt/etc/firmware - Proprietary blobs dirvers needed for Wifi, bluetooth and other things to work. /mnt/etc/sensor_hal_config_default.xml - Needed in order to the accelerometer to work. /mnt/build.prop - Needed if you have problems with some apps like Facebook. /mnt/lib/hw/bluetooth.so - In order to make bluetooth working
------------------------------------------------------------------------------------ System.img patching
Once you got those files, do the same simg2img command with the system.img ROM you want to put the drivers on, in my case the V7. Mount it with read-write on /mnt or everywhere you like, then patch all the files by copy-pasting the one you extracted before and replacing them on the new ROM using a file manager with root permissions like thunar, nautilus or pcmanfm
tl;dr, what I did?
Extracted the two system.img's of two different roms Copy-pasted and replaced the files I told you before from the working V5 ROM (Even owning the V3 one but that has the same hardware of V5 I suppose) to the newer V7 rom I want to use is that hard?
System.img repacking and flashing
Make sure you unmounted the system.img.raw by ' umount /mnt ' put this command ' img2simg system.img.raw system.edited.img '
Now you just need to flash it like the boot.img before, so ' fastboot flash system system.edited.img ' ' fastboot reboot system '
If everything went good , you will reboot into your fresh-new system! Stable if you compare the first sh*tty firmwares they made, there are less slowdowns and bugs like the strecthed windows in the multitasking area.
Modified V5 boot.img: https://mega.nz/#!OlgygJjK!wTv2L9yfCGsqkV7ShGX4Cub-EGdvh3ROtuZxvMzVGoM
Modified V7 system.img to make it work with V3 using V5 firmware: Soon...
If you made your own working, please tell me, I will put the links, just specify the ROM and the source drivers you used!
fastboot format system - Formats the android systems Warning: it does not reset the phone, if you reboot you won't have any android system fastboot format data - Formats the /data folders (Program files like apps data) - It does a factory reset, but the ROM will still be the same. fastboot format userdata - Formats the /sdcard folder fastboot reboot system - Reboots into Android fastboot reboot recovery - reboots into recovery From android:
' adb reboot recovery ' Reboots into TWRP ' adb reboot system ' Reboots normally 'adb reboot bootloader ' - Reboots into fastboot
Hi in short
Tablet onda v919 Ver.9 (was dualboot now only android) looking what kind of tool i can use to delete windows partitions and merge them with android partitions. or how to rewrite partitions.tlb as now i have (look at end of message)
tryed lots of them, windows cd, hirens, sergel and some other cant boot up. and i do not know where is windows where android partitions
add -b 40 -s 131072 -t efi -u C12A7328-F81F-11D2-BA4B-00A0C93EC93B -l ESP -T 0 -P 0 /dev/block/mmcblk0
add -b 131112 -s 131072 -t data -u 80868086-8086-8086-8086-FFFFFFFFFFF0 -l reserved -T 0 -P 0 /dev/block/mmcblk0
add -b 262184 -s 32768 -t data -u 80868086-8086-8086-8086-000000000100 -l boot -T 3 -P 15 /dev/block/mmcblk0
add -b 294952 -s 32768 -t data -u 80868086-8086-8086-8086-000000000101 -l recovery -T 3 -P 14 /dev/block/mmcblk0
add -b 327720 -s 32768 -t data -u 80868086-8086-8086-8086-000000000102 -l fastboot -T 3 -P 13 /dev/block/mmcblk0
add -b 360488 -s 32768 -t data -u 80868086-8086-8086-8086-FFFFFFFFFFF1 -l reserved_1 -T 3 -P 0 /dev/block/mmcblk0
add -b 393256 -s 131072 -t data -u 80868086-8086-8086-8086-000000000104 -l test -T 3 -P 12 /dev/block/mmcblk0
add -b 524328 -s 65536 -t data -u 80868086-8086-8086-8086-000000000001 -l panic -T 0 -P 0 /dev/block/mmcblk0
add -b 589864 -s 262144 -t data -u 80868086-8086-8086-8086-000000000002 -l factory -T 0 -P 0 /dev/block/mmcblk0
add -b 852008 -s 262144 -t data -u 80868086-8086-8086-8086-000000000003 -l misc -T 0 -P 0 /dev/block/mmcblk0
add -b 1114152 -s 262144 -t data -u 80868086-8086-8086-8086-000000000004 -l config -T 0 -P 0 /dev/block/mmcblk0
add -b 1376296 -s 2097152 -t data -u 80868086-8086-8086-8086-000000000005 -l cache -T 0 -P 0 /dev/block/mmcblk0
add -b 3473448 -s 524288 -t data -u 80868086-8086-8086-8086-000000000006 -l logs -T 0 -P 0 /dev/block/mmcblk0
add -b 3997736 -s 3145728 -t data -u 80868086-8086-8086-8086-000000000007 -l system -T 0 -P 0 /dev/block/mmcblk0
add -b 7143464 -s 13631488 -t data -u 80868086-8086-8086-8086-000000000008 -l data -T 0 -P 0 /dev/block/mmcblk0