Hi. I have a briked chinese phone (F7102), so I decided to dump the stock rom from a friend phone (same model) using this tutorial:
"you need a rooted device first before you can do it.
after you have rooted it. download the following app from play store called "android terminal emulator"
copy the romdump file to your sdcard and put the sdcard into your device.
copy from your tab the file to /data/local/ (use e.g. ES File Explorer (need root access))
change the permission of the romdump file (using ES File Explorer --> Hold the file --> Properties --> and change it to 755(rwxrw-rw)
open the installed android terminal emulator app
use to following command
su
/data/romdump
After you run that you can copy the whole folder in /sdcard/romdump to pc (using external sdcard, usb plug-in,...)
"
Everething was perfect, and the result of it was a folder named "romdump", it contains the following files:
config.gz 0 KB
system.info.gz 2 KB
system.tar 480 MB
checksum.md5 1 KB
My question is, how do I flash those files into my briked phone, from fastboot? ADB? and wich one of those files do I have to flash (for the size i think is "system.tar").
I hope you can helpme, please try to put the whole procedure for flashing the rom. (I am a noob on this.)
PD: sorry for my english.
Hi,
That's not a procedure many do here... But if it's your only option, maybe this guide can help.... You can ask for help here too,
> General discussion > XDA-University > [GUIDE] Making Dump Files Out of Android Device Partitions
Good luck!
Thank you. Thread closed.
Related
How to create your own ROM update.zip for the T-Mobile MyTouch 3G
Things you will need to perform this:
Java SE Dev Kit from Sun. java.sun.com
May need Cygwin with zlib0 package, from cygwin.com
This will give you Android 1.6 with all the Google applications, Root access.
I never found one place where all this information is all together, so that is why I compiled this together.
Now anyone can do this themselves.
Thanks to all the hard work others have done before this.
1.
First Root your phone and install a new Recovery image, either Amon Ra or Cyanogens Recovery image.
Instructions for one-click root: http://theunlockr.com/2009/08/22/how-to-root-the-mytouch-3g-or-g1-in-one-click/
2.
Download the Android 1.6 System image from
http://developer.htc.com/google-io-device.html
extract the contents of signed-google_ion-img-14721.zip.
3.
You now need to extract the contents of system.img using a tool called unyaffs. The source code is here:
http://code.google.com/p/unyaffs/downloads/list
Or download a prebuilt win32 version here.
http://jiggawatt.org/badc0de/android/index.html
Note you may also need cygwin1.dll and cygz.dll (zlib0 package). Found at cygwin.com
Of course if you already have Cygwin installed with the GCC packages, you can just compile it yourself. Then also
if you comment out the line 67 to "// symlink(oh->alias, full_path_name);"
then it will not create the copies of the symbolic link file, and you will not have to worry about deleting duplicate
symbolic link files later.
Now in the directory where system.img exists, create a new directory called "system"
go into the "system" directory.
type the following command:
unyaffs ..\system.img
That should extract all the files from the system.img file into the system directory.
4.
Now we just need to clean up some items. Since the system.img is a linux file system, it has symbolic
links built into it, but when we extracted it, it just created duplicate files, if you used the prebuilt unyaffs.exe.
So we can just delete the duplicates and have a script recreate the symlink on install.
So we need to delete some extra files from the system\bin directory.
Run the attached DeleteExtras.bat file from the same directory where system.img is in.
If you notice, all the files it deletes are 28 byte files, and if you open them in notepad only contain:
"!<symlink>toolbox..."
And we will remake the symbolic link when it is installed.
5.
Now from the directory where the system.img is, enter the following commands
mkdir META-INF
mkdir META-INF\com
mkdir META-INF\com\google
mkdir META-INF\com\google\android
Now copy the included file "update-script.txt" into the "META-INF\com\google\android" directory
and RENAME it to just "update-script".
This update-script gets run to recreate the symbolic links.
Not sure if these two are needed but they are in some custom ROMs here:
Copy the two files "fix_permissions" and "flash_image" to the "system\bin" directory.
6.
-- Optional --
These add root and Superuser access to the ROM, plus the Terminal Emulator application.
Copy the file "su" from Cyanogen's rom to the folder "system\bin"
Copy the file "Superuser.apk" to the folder "system\app"
Copy the file "Term.apk" to the folder "system\app"
You can also replace the "system\etc\apns-conf.xml" with a more complete one from here:
http://forum.xda-developers.com/showthread.php?t=547718
or here
http://docs.google.com/Doc?docid=0AZNbAmKkmakoZGZxZHNwMnpfMjJkaHg3ejN3eg&hl=en
Turn data roaming off by default by editing line in the build.prop file:
ro.com.android.dataroaming=false
Also to fix the Market program to show "Protected" applications change the ro.build.fingerprint line to the following:
ro.build.fingerprint=tmobile/opal/sapphire/sapphire:1.5/COC10/150449:user/ota-rel-keys,release-keys
Only phones with a fingerprint of a "released" device can access some market applications.
--------------
7.
Now we just need to create a ZIP file for the final ROM
Zip up the following file and two folders:
boot.img
META-INF
system
8.
Now sign the zip file.
See here how to sign a ZIP file for flashing it.
http://androidforums.com/developer-101/8665-how-signing-roms.html
9.
Copy it to your SD card, boot into recovery, wipe, apply the update, Reboot.
You are now running Android 1.6!
the finger print is found in build.prop is this correct and what app do you use to edit your build.prop
Yes the fingerprint is in build.prop
Make sure to use an advanced text editor like TextPad, UltraEdit, or EditPlus. It has to handle UNIX text files.
Also use this for the update_script.
how abt kernel parameters?
How would one go about customizing this with Hero? Or is that not possible at this point?
detox702 said:
How would one go about customizing this with Hero? Or is that not possible at this point?
Click to expand...
Click to collapse
Would like more info on hot to incorporate senseui
Thanks for sharing... Got nothing to do today, so I experimented on my phone... I gotta say, I'm pretty amazed w/ this feature. Was able to sort out and organize my files.
Kudos!
How does one create the system.img file once one has the system files...
What I want to do is use some of the custom roms here and put it on an AVD emulator system.
Can someone help with this please.
NOTE: I dont have linux. So if there is an alternative to mkbootimg, it will be excellent.
the ion is the 32b if I'm not mistaken?
Is there an image for the 32a or do we always have to use the ion and throw a patch over it?
Sorry if this is a stupid question
in step 5. it says
Not sure if these two are needed but they are in some custom ROMs here:
Copy the two files "fix_permissions" and "flash_image" to the "system\bin" directory.
Where do i copy the files from or download please?
thanks in advance
P.S. any tips on changing the splash screen would be much appreciated.
DeleteExtras.txt or DeleteExtras.bat doesn't work. I have to delete the extra files by myself - one by one.
codysoloman said:
DeleteExtras.txt or DeleteExtras.bat doesn't work. I have to delete the extra files by myself - one by one.
Click to expand...
Click to collapse
check this: http://forum.xda-developers.com/showthread.php?t=633246
Perhaps someone here knows or could point me to the right resources, but if the phone isn't supported by Cyanogen, how would a custom rom be made in that case?
How is a custom rom made from scratch? Since android is just linux, is it simply a matter of building it with the right drivers for the phone and installing it? How can an image be manually copied to the phone if it isn't supported by Clockwork recovery? How can it's steps be manually done?
ping pong...
Can i install my own rom on samsung ace?????
anybody knows how to make a ROM customized and make a "update.img" to run on a un-rootable device? I know when you backup a linux image for example ubuntu, this image will run on all other PCs, the image will automatically knows the new PC's drivers and adapt everything with that, is it what happening to an android too ?
---------- Post added at 08:36 AM ---------- Previous post was at 08:33 AM ----------
and pls let me know how to open/edit a "update.img" file, thnx
Question
androidcustomrom said:
How to create your own ROM update.zip for the T-Mobile MyTouch 3G
Things you will need to perform this:
Java SE Dev Kit from Sun. java.sun.com
May need Cygwin with zlib0 package, from cygwin.com
This will give you Android 1.6 with all the Google applications, Root access.
I never found one place where all this information is all together, so that is why I compiled this together.
Now anyone can do this themselves.
Thanks to all the hard work others have done before this.
1.
First Root your phone and install a new Recovery image, either Amon Ra or Cyanogens Recovery image.
Instructions for one-click root: http://theunlockr.com/2009/08/22/how-to-root-the-mytouch-3g-or-g1-in-one-click/
2.
Download the Android 1.6 System image from
http://developer.htc.com/google-io-device.html
extract the contents of signed-google_ion-img-14721.zip.
3.
You now need to extract the contents of system.img using a tool called unyaffs. The source code is here:
http://code.google.com/p/unyaffs/downloads/list
Or download a prebuilt win32 version here.
http://jiggawatt.org/badc0de/android/index.html
Note you may also need cygwin1.dll and cygz.dll (zlib0 package). Found at cygwin.com
Of course if you already have Cygwin installed with the GCC packages, you can just compile it yourself. Then also
if you comment out the line 67 to "// symlink(oh->alias, full_path_name);"
then it will not create the copies of the symbolic link file, and you will not have to worry about deleting duplicate
symbolic link files later.
Now in the directory where system.img exists, create a new directory called "system"
go into the "system" directory.
type the following command:
unyaffs ..\system.img
That should extract all the files from the system.img file into the system directory.
4.
Now we just need to clean up some items. Since the system.img is a linux file system, it has symbolic
links built into it, but when we extracted it, it just created duplicate files, if you used the prebuilt unyaffs.exe.
So we can just delete the duplicates and have a script recreate the symlink on install.
So we need to delete some extra files from the system\bin directory.
Run the attached DeleteExtras.bat file from the same directory where system.img is in.
If you notice, all the files it deletes are 28 byte files, and if you open them in notepad only contain:
"!<symlink>toolbox..."
And we will remake the symbolic link when it is installed.
5.
Now from the directory where the system.img is, enter the following commands
mkdir META-INF
mkdir META-INF\com
mkdir META-INF\com\google
mkdir META-INF\com\google\android
Now copy the included file "update-script.txt" into the "META-INF\com\google\android" directory
and RENAME it to just "update-script".
This update-script gets run to recreate the symbolic links.
Not sure if these two are needed but they are in some custom ROMs here:
Copy the two files "fix_permissions" and "flash_image" to the "system\bin" directory.
6.
-- Optional --
These add root and Superuser access to the ROM, plus the Terminal Emulator application.
Copy the file "su" from Cyanogen's rom to the folder "system\bin"
Copy the file "Superuser.apk" to the folder "system\app"
Copy the file "Term.apk" to the folder "system\app"
You can also replace the "system\etc\apns-conf.xml" with a more complete one from here:
http://forum.xda-developers.com/showthread.php?t=547718
or here
http://docs.google.com/Doc?docid=0AZNbAmKkmakoZGZxZHNwMnpfMjJkaHg3ejN3eg&hl=en
Turn data roaming off by default by editing line in the build.prop file:
ro.com.android.dataroaming=false
Also to fix the Market program to show "Protected" applications change the ro.build.fingerprint line to the following:
ro.build.fingerprint=tmobile/opal/sapphire/sapphire:1.5/COC10/150449:user/ota-rel-keys,release-keys
Only phones with a fingerprint of a "released" device can access some market applications.
--------------
7.
Now we just need to create a ZIP file for the final ROM
Zip up the following file and two folders:
boot.img
META-INF
system
8.
Now sign the zip file.
See here how to sign a ZIP file for flashing it.
http://androidforums.com/developer-101/8665-how-signing-roms.html
9.
Copy it to your SD card, boot into recovery, wipe, apply the update, Reboot.
You are now running Android 1.6!
Click to expand...
Click to collapse
Could you tell me where I can correct the fake data in the phone like the real RAM is 512 MB but it say 1GB ,can you tell me how to
correct it thanks in advance:good:
I upgraded to Cyangenmod 2.2 Froyo on my Kyros, but I decided to downgrade back to Eclair. So I wiped/factory reset. And restored my backup with 2.1 Eclair. I was able to root but I was unable to install clockworkmod recovery. And after doing more research I found that flash_image command is not in my system/bin folder so I'm unable to use the command in adb. I tried copying a flash_image.zip which i found on the forum to my sdcard so i could be able to copy it to system/bin but I can't because it's read-only. The only thing i cant think of now is change the permissions on system/bin directory and copy the flash_image file there, but how to do that??? And if that doesn't work what else can I do??
I tried downloading the update.zip from coby and copy the flash_image file into the file since coby removed the flash_image from the new update. When I tried to update from the the update.zip its giving me verification failed. So its impossible to modifiy the update the file without verification failure. And the old update file isnt working either, seems that when you update the to the new update.zip it prevents you from downgrading.
Solved!
I got it. Make sure your device is rooted, and you have SuperUser.
I downloaded Root Explorer, mounted the "system" directory as RW and then change the permissions on the directory, (I ticked everything, basically full access), then did the same for the "bin" folder. Then I copied my "flash_image" file what I got from my old backup and copied it to the "bin" folder.
I undid the permissions and flashed the recovery.img (which installs the ClockwordMod) with adb and then I was able to install the Android Market and Google Apps.
Got it solved on the same day, just didn't have the time to post it.
Please help ( i'm afraid i bricked the coby 7015)
Hi guys !!!
My coby kyros is in permanent bootloop . The only thing I can do is make it enter into recovery mode ( the original from coby stock ) . I did wipe data and cache but when I try to recover from update.zip it fails because I am using a modified version of this update that was intended for rooted devices - ( so in recovery mode it does not work since it needs the upadte from original stock )-
Is there a way to flash the correct update.zip to the coby via Windows XP ADB ( I have tried to use adb shell but it list no devices and I followed all the steps from another post to install the USB drivers for adb and it worked , but adb list no devices ) - HELP PLEASE
Thanks in advance
Gardelvis
Hi guys !!!
I resolved my problem simply rebooting the PC and adding an adb push command to copy the correct update.zip in the sdcard
Gardelvis
Hi,
i hope anybody can help me to make a Galaxy 3 Rom Backup Tool.
I made a little script for the German Forum, and it works fine but i can not flash the backupped Rom files.
Can somebody help me how i can push the backupped /data partition in datafs.rfs to the Phone without getting a Bootloop?
Here is a link to the Script http://www.multiupload.com/TAIJ9Z53J7
Sry for my english ^^
Nice work!
Will try ASAP...
And btw your english is good enough!
Ok, translated for you :
Code:
Install Total Commander and connect your Galaxy 3 to your PC in USB debugging mode
Next run Backup.bat
Your backup is finished when the window closes by itself. You can find the data in the folder backup on your SD
Copy the whole folder to your PC
Open the ROM Image.tar in total commander
Now you can flash your backup as One Package in Odin.
WARNING: please mention my name when you upload or translate the tool
Thanks for the code, I was just thinking along the same lines. You can skip the Total commander thing if you'd include something like 7zip commandline which is free. You can then call it from your batch file. Or tar it in the phone itself or is this too slow/bad for SD ?
You pull the files over with adb pull, but instruct to copy them from the SD as well.
As for why it bootloops : need to test it, but will probably wait for a fresh rom.
You can also put it back with dd ?
hmm
with which adb command i can put all 5 files in a flashable .tar file?
and how i can put the whole /data partition from the datafs.rfs in the /data folder and overwrite the files in the data folder?
Hmm, I see it's Busybox responding on my Galaxy, maybe it's not installed by default, but it was included in a custom ROM ?
Code:
BusyBox v1.18.4 (2011-03-20 15:16:04 CDT) multi-call binary.
Usage: tar -[cxtzjamvO] [-X FILE] [-f TARFILE] [-C DIR] [FILE]...
Create, extract, or list files from a tar file
Operation:
c Create
x Extract
t List
Options:
f Name of TARFILE ('-' for stdin/out)
C Change to DIR before operation
v Verbose
z (De)compress using gzip
j (De)compress using bzip2
a (De)compress using lzma
O Extract to stdout
h Follow symlinks
m Don't restore mtime
exclude File to exclude
X File with names to exclude
T File with names to include
You'd have to remount /data r/w to make any changes to it. But if you're dd-ing, it'll talk to the block device directly. Not sure how to clear it though, maybe dd does it by itself. Have a google for linux commands.
hmm ok,
and why i get a bootloop when i want to flash the files with odin?
one more question ^^
how i can pull the complete /data partition to SD card?
And Creating a .tar file with 7zip commandline works, but the File is not flashable.
you can find the info in i9000 forum
http://forum.xda-developers.com/showthread.php?t=943588
http://forum.xda-developers.com/showthread.php?t=960946
http://forum.xda-developers.com/showthread.php?t=965190
Okay i have a 1 click Rom backup now ^^
But its still the problem that i get a bootloop after flashing...
Ok, I tested it and /data was wiped, phone can't mount sd card etc. etc.
tgm28 said:
Ok, I tested it and /data was wiped, phone can't mount sd card etc. etc.
Click to expand...
Click to collapse
Use THIS from HERE.
Quoting deskjeti.
deskjeti said:
Hi,
I made a Backup & Recovery Script in the German Android Hilfe Forum for the Galaxy 3.
The Tool make a flashable Rom with 3 Clicks and Restore the Backup with one Flash and one Click.
The Script restores all Apps, app Data Google Account and Wifi key´s.
How To:
Unzip the zip file wherever you want and plug in your Phone with USB Debugging Mode.
Run the Step1 and wait, after Step1 is finished run Step2 and if Step2 finished Run Step3
In the "Alexgalaxys G3 Recovery v2 Final" Folder now is a CustomRom.tar.
Flash it as One Package.
If the Phone is started plug the Phone in Usb debugging mode and Run the Recovery.bat after it is complete you have to reboot you Phone.
Link: http://www.multiupload.com/NV0CFVYV2I
Click to expand...
Click to collapse
Although I edited the files to just be one click.
Hi All,
I'm a complete noob when it comes to Android and am having difficulty following instructions to apply a volume hack to my Samsung Galaxy S3 (Android 4.04). Please note. As a noob this was the only sub-forum I could post in.
Note: I have managed to root my phone, and have ES File explorer installed. All text in full caps is mine.
Here's the link to the full instructions http://forum.xda-developers.com/showthread.php?t=1722136
Summary
1) Download attatched file ('default_gain.conf' inside 'VolumeMods.zip')
2) Use a file manager or ADB to push it to "system/etc" (back up existing file first!) I'VE GOT THIS FAR
NEXT STEP IS THE ONE I HAVE PROBLEM WITH - HOW DO YOU DO THIS?
3) From ADB or the Terminal do: HOW/WHERE DO YOU OPEN TERMINAL?
Code:
killall mediaserver
Actually no you can post in the Q&A or the General forums for your device, just not in the Development sections...
In on other words you could of and should of posted here: http://forum.xda-developers.com/forumdisplay.php?f=1569
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.