Database Info

[Q] Flashing kernel in flash tool

How do I flash a kernel in flashtool to get CWM recovery on the phone thanks

ferrari35 said:
How do I flash a kernel in flashtool to get CWM recovery on the phone thanks
Click to expand...
Click to collapse
Download Extended stock kernel.zip or Vengence kernel.zip from the threads.
Now extract it to you desktop.
1)Move the kernel(boot.img) to Flashtool/firmwares
2)Open flashtool
3)Press the Thunder button.
4)Choose "Fastboot Mode"(A new window will popup.Its called "Fastboot Toolbox")
5)Turn off your device
6)Now connect your device to fastboot mode
7)On Fastboot Toolbox click on "Select kernel to Flash".
8)search for the boot.img file if you are on stock kernel.
8)Wait to complete and you are READY
Once the phone is rebooted in normal mode if you want to go into recovery then you can switch of the device and once you see the bootanimation keep pressing the volume down key your phone will vibrate and you will be taken to the CWM recovery mode. :laugh:

neville20_dabreo said:
Download Extended stock kernel.zip or Vengence kernel.zip from the threads.
Now extract it to you desktop.
1)Move the kernel(boot.img) to Flashtool/firmwares
2)Open flashtool
3)Press the Thunder button.
4)Choose "Fastboot Mode"(A new window will popup.Its called "Fastboot Toolbox")
5)Turn off your device
6)Now connect your device to fastboot mode
7)On Fastboot Toolbox click on "Select kernel to Flash".
8)search for the boot.img file if you are on stock kernel.
8)Wait to complete and you are READY
Once the phone is rebooted in normal mode if you want to go into recovery then you can switch of the device and once you see the bootanimation keep pressing the volume down key your phone will vibrate and you will be taken to the CWM recovery mode. :laugh:
Click to expand...
Click to collapse
Not sure its working
29/014/2013 22:14:31 - INFO - Device disconnected
29/016/2013 22:16:52 - INFO - Device connected in fastboot mode
29/018/2013 22:18:04 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\boot.img
29/018/2013 22:18:04 - INFO - Flashing selected kernel
29/018/2013 22:18:04 - INFO - sending 'boot' (11212 KB)...
29/018/2013 22:18:04 - INFO - OKAY [ 0.366s]
29/018/2013 22:18:04 - INFO - writing 'boot'...
29/018/2013 22:18:04 - INFO - FAILED (remote: Command not allowed)
29/018/2013 22:18:04 - INFO - finished. total time: 0.368s
29/018/2013 22:18:04 - INFO - FASTBOOT Output:
sending 'boot' (11212 KB)...
OKAY [ 0.366s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.368s
Log for check device status
29/036/2013 22:36:02 - INFO - (FastBootToolBoxJob.java:190) - Please check the log before rebooting into system
29/036/2013 22:36:13 - DEBUG - (ProcessBuilderWrapper.java:92) - ZH8000M80Q fastboot
29/036/2013 22:36:13 - DEBUG - (AdbUtility.java:415) - Testing if device is connected
29/036/2013 22:36:13 - DEBUG - (ProcessBuilderWrapper.java:92) - List of devices attached
29/036/2013 22:36:13 - DEBUG - (ProcessBuilderWrapper.java:92) - ZH8000M80Q fastboot
29/036/2013 22:36:13 - INFO - (FastBootToolBoxJob.java:84) - Device Status: FASTBOOT mode
After I unlocked boot loader I flashed to stock central europe rom this was before I tried to flash exstended stock kernel kernel

Update
Uninstalled flash tool,re installed flash tool and the flash drivers(flashtool does not recognise that the drivers are installed and I can only get them installed by putting phone into flash/fastboot and the phone installs them) and flashed stock UK Rom and rooted phone everytime I try to flash a custom kernel I get an error (as in my last post) re locking and unlocking does not change it
I think it's some sort of read write error question does anyone know what file/folder it's getting pushed to on the phone and could I make it writeable with root explorer?
Sent from my C2105 using XDA Premium 4 mobile app

[Q] Help regarding OnePlus One for root

Hi,
After searching a lot in the Google, in this forum and other places, I think its time to write here.
Here it is what I have and want to know/help please : I am gonna to root the device but not able to root it.
Model name : A0001
Cyanogen OS version : 12.0-YNG1TAS213
Android version : 5.0.2
E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot devices
49a6b9bb fastboot
E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.016s
E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.016s
E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot devices
49a6b9bb fastboot
E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot oem unlock
...
OKAY [ 0.031s]
finished. total time: 0.031s
E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.031s]
finished. total time: 0.031s
E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.016s
E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot devices
49a6b9bb fastboot
E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot flash recovery openrecovery-twrp-2.8.1.0-bacon.img
target reported max download size of 1073741824 bytes
sending 'recovery' (12588 KB)...
OKAY [ 0.530s]
writing 'recovery'...
OKAY [ 0.125s]
finished. total time: 0.655s
E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot format cache
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.047s]
sending 'cache' (10432 KB)...
OKAY [ 0.421s]
writing 'cache'...
OKAY [ 0.125s]
finished. total time: 0.608s
E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.000s
E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>
Questions :
1. Still I don't have TWRP recovery when I Volume Down+Power button, there is Cyanogen recovery menu.
2. Is it not possible to flash supersu.zip in Cyanogen recovery ?
3. If yes, then please give me the download link for it.
4. What else more required after unlock the bootloader to root the device with Cyanogen recovery.
5. Will having TWRP recovery void device warranty ?
Regards
Girish Sharma

1. The answer to this question lies within my guide thread and also within my FAQ thread
2. No.
3. See above.
4. See above.
5. No. See FAQ thread linked above.
A little searching on your part would have had your problem solved long ago.

I am really thankful to you for your reply.
I followed exactly your thread to move to root the device.
By looking above steps can you please tell me what next I should download/do to root the device ?
In your steps you have mentioned about TWRP recovery to flash the supersu.zip but I am not able to have TWRP recovery, and I guess this is the place where my rooting procedure is going to stuck.
One more confusion :
I requested to :
2. Is it not possible to flash supersu.zip in Cyanogen recovery ?
You replied
No
So, I am confused this "No".
If it is not possible to flash the supersu.zip then please tell me how do I proceed further.
Kindly help me.
Regards
Girish Sharma

I rooted my OPO successfully (it seems me like that) :
1.Downloaded twrp-2.8.7.0-bacon.img. Renamed it to twrp.img and placed it platform-tools folder.
fastboot devices
It showed me my OPO's connection.
E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot flash recovery twrp.img
target reported max download size of 1073741824 bytes
sending 'recovery' (10368 KB)...
OKAY [ 0.437s]
writing 'recovery'...
OKAY [ 0.109s]
finished. total time: 0.546s
E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot reboot
pressed enter key and immediately power down button of the device. After few second I got TWRP recovery menu and now its path to root the device by flashing the UPDATE-SuperSU-v2.46-1.zip and bingo... device rooted.
I got this clue from this link :
"Type fastboot reboot to reboot your phone, but hold volume down as soon as your phone buzzes so that it boots into recovery instead of the OS. You have to do this or TWRP may not work."
https://forums.oneplus.net/threads/...lashing-recovery-roms-kernels-rooting.291274/
Regards
Girish Sharma

GirishSharma said:
I am really thankful to you for your reply.
I followed exactly your thread to move to root the device.
By looking above steps can you please tell me what next I should download/do to root the device ?
In your steps you have mentioned about TWRP recovery to flash the supersu.zip but I am not able to have TWRP recovery, and I guess this is the place where my rooting procedure is going to stuck.
One more confusion :
I requested to :
2. Is it not possible to flash supersu.zip in Cyanogen recovery ?
You replied
No
So, I am confused this "No".
If it is not possible to flash the supersu.zip then please tell me how do I proceed further.
Kindly help me.
Regards
Girish Sharma
Click to expand...
Click to collapse
GirishSharma said:
I rooted my OPO successfully (it seems me like that) :
1.Downloaded twrp-2.8.7.0-bacon.img. Renamed it to twrp.img and placed it platform-tools folder.
fastboot devices
It showed me my OPO's connection.
E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot flash recovery twrp.img
target reported max download size of 1073741824 bytes
sending 'recovery' (10368 KB)...
OKAY [ 0.437s]
writing 'recovery'...
OKAY [ 0.109s]
finished. total time: 0.546s
E:\Users\serverroom\AppData\Local\Android\sdk\platform-tools>fastboot reboot
pressed enter key and immediately power down button of the device. After few second I got TWRP recovery menu and now its path to root the device by flashing the UPDATE-SuperSU-v2.46-1.zip and bingo... device rooted.
I got this clue from this link :
"Type fastboot reboot to reboot your phone, but hold volume down as soon as your phone buzzes so that it boots into recovery instead of the OS. You have to do this or TWRP may not work."
https://forums.oneplus.net/threads/...lashing-recovery-roms-kernels-rooting.291274/
Regards
Girish Sharma
Click to expand...
Click to collapse
Ok, but I don't think you did follow my giude exactly. There's an underlined section at the bottom of the section that deals with the exact problem you were having:
Please note, if you have taken the stock Lollipop update please read the following:
For some reason CM12S doesn't respect the on/off toggle for the "update CM recovery" option in Developer Options, it just replaces whatever custom recovery you've flashed with the CM recovery regardless of whether that option is unelected.
Flash your custom recovery again, but after flashing don't do a normal reboot. After the flash has succeeded disconnect the usb cable, then power down the phone by holding the power button down, once it's powered off use the power + volume down button combo to boot directly into recovery. This first forced reboot into recovery somehow subverts what was keeping it from staying flashed and all subsequent normal reboots into recovery will boot into the custom recovery of your choice.
Click to expand...
Click to collapse
There's also a question in the FAQ thread that addresses this issue:
Q22: I've updated to CM12S and now I have flash a custom recovery, why?
For some reason CM12S doesn't respect the on/off toggle for the "update CM recovery" option in Developer Options, it just replaces whatever custom recovery you've flashed with the CM recovery regardless of whether that option is unelected.
Flash your custom recovery again, but after flashing don't do a normal reboot. After the flash has succeeded disconnect the usb cable, then power down the phone by holding the power button down, once it's powered off use the power + volume down button combo to boot directly into recovery. This first forced reboot into recovery somehow subverts what was keeping it from staying flashed and all subsequent normal reboots into recovery will boot into the custom recovery of your choice.​
Click to expand...
Click to collapse
I gave you links to both of those threads in my first reply to you, so there was no need to go to the OnePlus forums, the answer was right here all along.

Ok. Thanks again for reply. Earlier I failed to understand your underlined text so, I was bit confused about CM12 and CM12S, since I having CM12 so was bit confused.
At this moment, everything looks fine i.e. unlocked bootloader, installed TWRP, superuser (an app from F-droid open source repository) app, but it is saying "The Superuser binary (su) must be updated. Please choose an installation method. Recovery mode installation is recommended for HTC devices. And there are two button Cancel , Recovery Install. When I clickes Recovery install, I gets TWRP menu, and when I installs UPDATE-SuperSU-V2.46-1.zip, it gets installed successfully and when I reboot the device there is only "Cynaogen" logo on the screen, nothing more.
So, can you tell me how do I remove "The Superuser binary (su) must be updated. " message on every reboot the device.
Regards
Girish Sharma

GirishSharma said:
Ok. Thanks again for reply. Earlier I failed to understand your underlined text so, I was bit confused about CM12 and CM12S, since I having CM12 so was bit confused.
At this moment, everything looks fine i.e. unlocked bootloader, installed TWRP, superuser (an app from F-droid open source repository) app, but it is saying "The Superuser binary (su) must be updated. Please choose an installation method. Recovery mode installation is recommended for HTC devices. And there are two button Cancel , Recovery Install. When I clickes Recovery install, I gets TWRP menu, and when I installs UPDATE-SuperSU-V2.46-1.zip, it gets installed successfully and when I reboot the device there is only "Cynaogen" logo on the screen, nothing more.
So, can you tell me how do I remove "The Superuser binary (su) must be updated. " message on every reboot the device.
Regards
Girish Sharma
Click to expand...
Click to collapse
No you don't have CM12, you have Cyanogen OS 12 (CM12S). You can get the proper SuperSU zip from here. Flash that with TWRP, wipe cache and dalvik cache, reboot.

Thank you so much for your great help.
I shall open another thread for next/forthcoming question(s) regarding :
1.Will I get OTA updates easily, if I have unchecked "Update recovery with system updates" in developer option. (Particularly in mine case/above setup(s))
2.How it is good to use other ROMs like 12.1 NIghtly.
3.What benefits, features I can enjoy on this OPO rooted device.
4.How do I now restrict the apps to use my mobile data without my permission/wish (This was the main purpose to root the device). I am going to install AFWall app (F-droid repository app) to see how it will work.
5.Anything special which you would like to suggest me to have/have not, do/do not.
6.etc.
Regards
Girish Sharma

GirishSharma said:
Thank you so much for your great help.
I shall open another thread for next/forthcoming question(s) regarding :
1.Will I get OTA updates easily, if I have unchecked "Update recovery with system updates" in developer option. (Particularly in mine case/above setup(s))
2.How it is good to use other ROMs like 12.1 NIghtly.
3.What benefits, features I can enjoy on this OPO rooted device.
4.How do I now restrict the apps to use my mobile data without my permission/wish (This was the main purpose to root the device). I am going to install AFWall app (F-droid repository app) to see how it will work.
5.Anything special which you would like to suggest me to have/have not, do/do not.
6.etc.
Regards
Girish Sharma
Click to expand...
Click to collapse
There's no need to open a new thread, we can discuss those questions here.
1. Yes, you should still receive OTA updates even with that setting disabled.
2. It comes down to personal choice. Custom ROMs usually offer more features and optimisations. I use the Exodus ROM, which has nice features and great battery life.
3. There are many benefits to having root access. You can run root apps like Titanium Backup, Greenify, BetterBatteryStats, and many more. You can also access and modify system files, care should be taken with this though because doing the wrong thing can end up with a phone that won't boot.
4. The unsure about this as I don't restrict any apps from using mobile data.
5. Use Titanium Backup to make sure you have backups of your user apps (and their data), the pro version also allows you to backup call logs and sms/mms. You can use Greenify to stop apps from running in the background when you don't want them to, this will save battery life.

There's no need to open a new thread, we can discuss those questions here.
Yes, we can discuss here, but I think if I opens another thread; then other visitors will also be benefited by your valuable replies.
1. Yes, you should still receive OTA updates even with that setting disabled.
I will see, how I shall get OTA of Exodus as well, because at present I am seeing a long list of OTAs, so I have just downloaded and applied 20150704 version directly.
2. It comes down to personal choice. Custom ROMs usually offer more features and optimisations. I use the Exodus ROM, which has nice features and great battery life.
I have ported Exodus Version 5.1-20150704-NIGHTLY-bacon and now my Android version is 5.1.1_r6. Its really pretty cool to use this first time.
3. There are many benefits to having root access. You can run root apps like Titanium Backup, Greenify, BetterBatteryStats, and many more. You can also access and modify system files, care should be taken with this though because doing the wrong thing can end up with a phone that won't boot.
Fully agree and thanks for your reply.
4. The unsure about this as I don't restrict any apps from using mobile data.
F-droid is also another best open source repository for android. I uses its apps very much, more than Google play store (ad, and pro version)
5. Use Titanium Backup to make sure you have backups of your user apps (and their data), the pro version also allows you to backup call logs and sms/mms. You can use Greenify to stop apps from running in the background when you don't want them to, this will save battery life.
Yes, I have installed Titanium Backup, BetterBatteryStat and Greenify. Now looking into their features and how they works.
Regards
Girish Sharma

GirishSharma said:
There's no need to open a new thread, we can discuss those questions here.
Yes, we can discuss here, but I think if I opens another thread; then other visitors will also be benefited by your valuable replies.
1. Yes, you should still receive OTA updates even with that setting disabled.
I will see, how I shall get OTA of Exodus as well, because at present I am seeing a long list of OTAs, so I have just downloaded and applied 20150704 version directly.
2. It comes down to personal choice. Custom ROMs usually offer more features and optimisations. I use the Exodus ROM, which has nice features and great battery life.
I have ported Exodus Version 5.1-20150704-NIGHTLY-bacon and now my Android version is 5.1.1_r6. Its really pretty cool to use this first time.
3. There are many benefits to having root access. You can run root apps like Titanium Backup, Greenify, BetterBatteryStats, and many more. You can also access and modify system files, care should be taken with this though because doing the wrong thing can end up with a phone that won't boot.
Fully agree and thanks for your reply.
4. The unsure about this as I don't restrict any apps from using mobile data.
F-droid is also another best open source repository for android. I uses its apps very much, more than Google play store (ad, and pro version)
5. Use Titanium Backup to make sure you have backups of your user apps (and their data), the pro version also allows you to backup call logs and sms/mms. You can use Greenify to stop apps from running in the background when you don't want them to, this will save battery life.
Yes, I have installed Titanium Backup, BetterBatteryStat and Greenify. Now looking into their features and how they works.
Regards
Girish Sharma
Click to expand...
Click to collapse
You don't need to create a new thread, just discuss it here. People can find it just as easily here anyway. I don't use the built in OTA updater, I just go to the Exodus download page and get them manually, that way I can check the md5 of the file. Anyway, in the built in updater it shows you the latest update available so it's probably best just to use that one.
XDA Moderator
Transmitted via Bacon

Thanks for allowing me to continue to ask the question(s).
Sometime (in fact many time), when I am scrolling something on this device OPO (Same OS and everything same), the device responds like I have clicked on that option, i.e. suppose I am scrolling developer option and there are check/uncheck options only, so it changes its value from earlier one when I am just scrolling the option. Can you please tell me is it a bug in the OS or I have to do some setting in the device ?
Regards
Girish Sharma

Is it something related to :
cat /sys/class/input/input0/baseline_test
https://jira.cyanogenmod.org/browse/BACON-55
When I run above command (Terminal Emulator), it worked successfully, 0 error(s). All test passed.
I don't know I am addressing correctly in this touch issue.
Regards
Girish Sharma

GirishSharma said:
Thanks for allowing me to continue to ask the question(s).
Sometime (in fact many time), when I am scrolling something on this device OPO (Same OS and everything same), the device responds like I have clicked on that option, i.e. suppose I am scrolling developer option and there are check/uncheck options only, so it changes its value from earlier one when I am just scrolling the option. Can you please tell me is it a bug in the OS or I have to do some setting in the device ?
Regards
Girish Sharma
Click to expand...
Click to collapse
GirishSharma said:
Is it something related to :
cat /sys/class/input/input0/baseline_test
https://jira.cyanogenmod.org/browse/BACON-55
When I run above command (Terminal Emulator), it worked successfully, 0 error(s). All test passed.
I don't know I am addressing correctly in this touch issue.
Regards
Girish Sharma
Click to expand...
Click to collapse
It's a touchscreen problem that's plagued some of these devices from the very beginning. I have TWRP and neither have this problem though. The latest update that came supposedly fixed this issue.

Yes, I too have TWRP and Exodus 5.1-20150704-NIGHTLY-bacon, Android version : android-5.1.1_r6, but I am having the touchscreen problem (may it be a specific this device issue). Can you please tell me above cat baseline_test is something related to this issue or not or Exodus developer community will look into the bug (if any).
Regards
Girish Sharma

GirishSharma said:
Yes, I too have TWRP and Exodus 5.1-20150704-NIGHTLY-bacon, Android version : android-5.1.1_r6, but I am having the touchscreen problem (may it be a specific this device issue). Can you please tell me above cat baseline_test is something related to this issue or not or Exodus developer community will look into the bug (if any).
Regards
Girish Sharma
Click to expand...
Click to collapse
Sorry, that was a typo on my part, it should have read:
I have two and neither have this problem though.
I have no idea about that test. I highly doubt whether the Exodus devs would spend any time on it because it isn't related to Exodus. You were already on the latest stock firmware so you should be fully up to date in terms of firmware but if you want to be fully sure you could do the following:
1. Use TWRP to make a nandroid backup of your current setup.
2. Download the latest CM12.1 nightly.
3. Fully wipe (system, data, cache, dalvik cache).
4. Install the nightly, boot the phone up once (no need to install gapps).
5. Boot back into TWRP and fully wipe again.
6. Restore the nandroid backup you made in the first step.
This will ensure that you're on the latest firmware available.

[GUIDE / ROOT] OPPO R7 & R7 Plus - One-Click Root [17 Sep 2015] by dead5loth

It is a copy/paste from the original post created by dead5loth in OPPO forums: http://community.oppo.com/en/forum.php?mod=viewthread&tid=40709&extra=&page=1
Disclamer
1. Rooting your device may void your warranty!
2. Please note that I'm 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 applying this modification and remember, 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. A lot.
Notice
1. OPPO Tools claims to support both the R7 and R7 Plus (check the about tab) but I have only tested it with the OPPO R7g! If you are using a different varaient- PLEASE LEAVE FEEDBACK!
2. USING THIS TOOL IS YOUR RESPONSIBILITY, UPON DOWNLOADING AND USING THIS TOOL YOU AGREE THAT YOU MAY DAMAGE YOUR DEVICE AND MAY NEVER BE ABLE TO RECIEVE OTA UPDATES. (Side note: You will still have access to manual updates.)
Compatability
1. Please check below and see if this method is safe and works on your device.
2. Working - OPPO R7g on ColorOS v2.1 / Android 5.1.1
3. Working - OPPO R7f on Unspecified - (Thanks @bbgt2)
4. Working - OPPO R7 Plus M (Chinese Version w/ international 3G & 4G (FDD)) on ColorOS 2.1 / Android 5.1.1 (Thanks @jensehuk)
5. Partition / Possible Bricking Issues - OPPO R7 Plus F on Unspecified - (Thanks @ait-Solutions)
Requirements
1. OPPO R7 / R7 Plus on ColorOS (using this on custom ROMs may cause issues)
2. OPPO Tools v1.6.3 (or higher) - GitHub Project Page | Direct APK Download
3. Stock Recovery - USING TWRP OR ANY OTHER CUSTOM RECOVERY WILL NOT WORK
4. 50% or more remaining battery - THIS IS IMPORTANT
Steps
1. Download and Install the latest OPPOTools.apk ( https://github.com/wuxianlin/OppoTools/raw/server/OppoTools.apk ).
2. Launch OPPO Tools (check the About tab and verify that your device is listed)
3. Go to the Common tab and select ROOT.
4. An application install prompt will appear for "OppoToolsPlugin", Install it.
5. Once complete, re-open OPPO Tools and select ROOT once again.
6. One Key Root will open, Select the One Key Root button to start the ROOT process.
7. Your device will restart multiple times, just be patient.
8. If the installation was successful, you will notice SuperSU has been installed.

Phone: R7 Plus f (International version)
ColorOs Version: V2.1.0i
Compilation number: R7plusfEX_11:150902
Status: It works correctly!

Thanks, I think your post is missing the .apk so there it is: https://github.com/wuxianlin/OppoTools/raw/server/OppoTools.apk

There's been an update yesterday for the F version 'R7PlusfEX_11_150916' I'm unsure if it changes anything or adds any problems with rooting.

Unlock Bootloader/Backup/Root/Viper4Android
Unlock Bootloader/Backup/Root/Viper4Android
Tested myself on latest stock rom version R7PlusfEX_11_150916
Do it at your own risk, I am not responsible for any damage to your phone, your computer nor your cat.
1. You must have right ADB drivers installed. Please follow this guide (Prerequisites part)
You must end up with this:
Code:
C:\sdk\platform-tools>adb version
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android
Before I have installed SDK my R7+ was showing as Marshall London bootloader interface:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Correct drivers installed:
2. Maybe not needed but go to developers options and allow USB debugging
3. Power off your phone (wait, sometimes it take long time, it will vibrate when done)
4. Hold power button + volume UP to enter fastboot mode
5. Connect USB cable
6. Go to folder where your fastboot.exe is and press shift + right mouse and click on "Open command window from here"
7. Type
Code:
fastboot devices
- It should return your device serial number, if not you need to make sure your drivers are installed correctly.
8. Type
Code:
fastboot oem device-info
and see if your bootloader is locked (some phones comes with bootloader unlocked). You should see this:
Code:
C:\sdk\platform-tools>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.005s]
finished. total time: 0.006s
9. To unlock bootloader type
Code:
fastboot oem unlock
You should see this:
Code:
C:\sdk\platform-tools>fastboot oem unlock
...
OKAY [ 0.004s]
finished. total time: 0.005s
To check type again
Code:
fastboot oem device-info
You should see this:
Code:
C:\sdk\platform-tools>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.005s]
finished. total time: 0.006s
pic:
10. You are unlocked and your DATA are NOT wiped, congrats :highfive:
TWRP Recovery:
We are not going to flash twrp, because there is a risk of damage partition in the moment, so instead of flash, we only boot to it which is all we need!
1. Download this TWRP recovery (MIRROR) and put the file into the folder where your fastboot.exe is!
2. With phone in fastboot mode type
Code:
fastboot boot recovery.img
You should see this:
Code:
C:\sdk\platform-tools>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.865s]
booting...
OKAY [ 3.639s]
finished. total time: 4.506s
3. Wait, it can take 30 seconds to boot into TWRP!
Backup:
With TWRP running first of all I recommend you to backup all partitions and after backup is complete, restart phone and COPY the backup files from phone to your computer!
Root:
1. When still connected to computer copy SuperSU file to phone`s memory
2. Disconnect usb cable, power phone off, enter fastboot mode and connect the usb cable.
3. BOOT into TWRP recovery again and flash the SuperSU and reboot.
4. Check if you are rooted:
Viper4Android:
1. First we need to change the SElinux to permissive
2. Download SELinuxModeChanger-v3.2-release.apk here and place it to phone`s memory.
3. Install the app (unknown sources must be allowed in settings)
4. Run the app, grand root rights, click on permissive and I recommend tick "show notification after mode changed"
5. Go to Security center, Privacy Permission, scroll down and click Auto-run Management and ALLOW SELinuxModeChanger to start automatically after restart.
6. Reboot phone and see if SELinuxModeChanger starts - you should see the notification. If everything is fine, you can disable the notification by untick it in app.
7. Download Viper4Android and copy to phone.
8. BOOT into TWRP recovery again and simply flash the downloaded zip and reboot.
9. Click on Viper4Android app to install its drivers, grand root rights and reboot phone.
10. Now run app and enable it for headphones and you are ready to enjoy great sound.
11. I recommend to disable "Dirac HD Sound" in Music app settings to not interfere with Viper4Android.
Does everything work as you want now? Go back to TWRP and make a new backup!!!
That`s it! Hopefully someone will find this guide helpful! Enjoy!!!

Hello,
I have Oppo R7 plus mediatek version
R7Plus_11_A.06_OTA_006_all_201509030909_wipe.zip
When i use the Oppo tools v1.6.2 my phone is stuck at the Oppo logo screen.
I have already try Iroot, kingroot, kingoroot and shuameroot do not work
Can anybody help me root the device.
Thank you.

Has anyone installed xposedframework after root yet ?

Guys anyone have oppotools saved anywhere?

Osleg said:
Guys anyone have oppotools saved anywhere?
Click to expand...
Click to collapse
I dont, but use oppotools with chinesse version of phone only or there is a high chance you`ll brick your phone.

Works with oppo r7 lite (r7kf)?

Anyone got Oppotools anywhere?

OppoTools1.6.3
mikejasonsmith said:
Anyone got Oppotools anywhere?
Click to expand...
Click to collapse
https://github.com/asshadiqi/OppoTools/blob/server/OppoTools.apk
Click "view the full file" to download.

titanium_gld said:
https://github.com/asshadiqi/OppoTools/blob/server/OppoTools.apk
Click "view the full file" to download.
Click to expand...
Click to collapse
Your a star!
Does this work on a chinese phone?

I just updated my R7 Plus to R7PlusfEX_11_151225. Oppotools 1.6.5 can be installed but the root button doesn't do anything. Is this a known issue and will this be fixed in a new version of Oppotools?

Hi all FYI rooting method for R7plus using the OppoTools v1.6.5 is no longer supported on R7PlusfEX_11_151225.
So to root it just use the old method.
Just install/flash the UPDATE-SuperSU-v2.46.zip via TWRP
That's all. Cheers!

noodlecore said:
Hi all FYI rooting method for R7plus using the OppoTools v1.6.5 is no longer supported on R7PlusfEX_11_151225.
So to root it just use the old method.
Just install/flash the UPDATE-SuperSU-v2.46.zip via TWRP
That's all. Cheers!
Click to expand...
Click to collapse
Would anyone be able to provide a copy of 1.6.5? I'm still on 1.6.3... Thanks.

Nexus5-32GB said:
Unlock Bootloader/Backup/Root/Viper4Android
Tested myself on latest stock rom version R7PlusfEX_11_150916
Do it at your own risk, I am not responsible for any damage to your phone, your computer nor your cat.
1. You must have right ADB drivers installed. Please follow this guide (Prerequisites part)
You must end up with this:
Code:
C:\sdk\platform-tools>adb version
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android
Before I have installed SDK my R7+ was showing as Marshall London bootloader interface:
Correct drivers installed:
2. Maybe not needed but go to developers options and allow USB debugging
3. Power off your phone (wait, sometimes it take long time, it will vibrate when done)
4. Hold power button + volume UP to enter fastboot mode
5. Connect USB cable
6. Go to folder where your fastboot.exe is and press shift + right mouse and click on "Open command window from here"
7. Type
Code:
fastboot devices
- It should return your device serial number, if not you need to make sure your drivers are installed correctly.
8. Type
Code:
fastboot oem device-info
and see if your bootloader is locked (some phones comes with bootloader unlocked). You should see this:
Code:
C:\sdk\platform-tools>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.005s]
finished. total time: 0.006s
9. To unlock bootloader type
Code:
fastboot oem unlock
You should see this:
Code:
C:\sdk\platform-tools>fastboot oem unlock
...
OKAY [ 0.004s]
finished. total time: 0.005s
To check type again
Code:
fastboot oem device-info
You should see this:
Code:
C:\sdk\platform-tools>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.005s]
finished. total time: 0.006s
pic:
10. You are unlocked and your DATA are NOT wiped, congrats :highfive:
TWRP Recovery:
We are not going to flash twrp, because there is a risk of damage partition in the moment, so instead of flash, we only boot to it which is all we need!
1. Download this TWRP recovery (MIRROR) and put the file into the folder where your fastboot.exe is!
2. With phone in fastboot mode type
Code:
fastboot boot recovery.img
You should see this:
Code:
C:\sdk\platform-tools>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.865s]
booting...
OKAY [ 3.639s]
finished. total time: 4.506s
3. Wait, it can take 30 seconds to boot into TWRP!
Backup:
With TWRP running first of all I recommend you to backup all partitions and after backup is complete, restart phone and COPY the backup files from phone to your computer!
Root:
1. When still connected to computer copy SuperSU file to phone`s memory
2. Disconnect usb cable, power phone off, enter fastboot mode and connect the usb cable.
3. BOOT into TWRP recovery again and flash the SuperSU and reboot.
4. Check if you are rooted:
Viper4Android:
1. First we need to change the SElinux to permissive
2. Download SELinuxModeChanger-v3.2-release.apk here and place it to phone`s memory.
3. Install the app (unknown sources must be allowed in settings)
4. Run the app, grand root rights, click on permissive and I recommend tick "show notification after mode changed"
5. Go to Security center, Privacy Permission, scroll down and click Auto-run Management and ALLOW SELinuxModeChanger to start automatically after restart.
6. Reboot phone and see if SELinuxModeChanger starts - you should see the notification. If everything is fine, you can disable the notification by untick it in app.
7. Download Viper4Android and copy to phone.
8. BOOT into TWRP recovery again and simply flash the downloaded zip and reboot.
9. Click on Viper4Android app to install its drivers, grand root rights and reboot phone.
10. Now run app and enable it for headphones and you are ready to enjoy great sound.
11. I recommend to disable "Dirac HD Sound" in Music app settings to not interfere with Viper4Android.
Does everything work as you want now? Go back to TWRP and make a new backup!!!
That`s it! Hopefully someone will find this guide helpful! Enjoy!!!
Click to expand...
Click to collapse
Also Working on latest R7+ build R7plusfEX_11_151225. :good::laugh:

Hello,
I did the following step:
"2. With phone in fastboot mode typeCode:
fastboot boot recovery.img
You should see this:Code:
C:\sdk\platform-tools>fastboot boot recovery.imgdownloading 'boot.img'...OKAY [ 0.865s]booting...OKAY [ 3.639s]finished. total time: 4.506s"
However it did not go to TWRP. the phone rebooted and wet back to normal.
I turn the phone off and went to recovery but it was still OPPO's recovery.
Any help?

Omg ... I Use latest oppo tool 5 min job done
---------- Post added at 08:08 PM ---------- Previous post was at 08:05 PM ----------
Oppo tool V1.6.5
https://drive.google.com/file/d/0B-aJHtkQl-HNT2E3RnNzb1o4dU0/view?pref=2&pli=1

Successfully rooted Oppo R7s with Oppotools 1.6.5

Levovo TB-X606F Rooting Issue

I have a Levovo Tab M10 FHD Plus TB-X606F running android 10.
After having the device for several months and reading everything I coul dfind on rooting it or previous versions. I decided to attempt. (Note: I have route plenty of phone and tablets before)
Steps and Results
Enable USB debugging
Install Magisk 8.0.7
Download Factory ROM
Copy boot.img to device via adb
Run Magisk and patch img.
Copy patched img to PC via ADB
fastboot flashing unlock (fasboot oem unlock erros)
fastboot boot patched_boot.img
Sending 'boot.img' (32768 KB) OKAY [ 1.512s]
Booting OKAY [ 0.063s]
Finished. Total time: 2.807s
Device rebooted on its own.
Rebooted into fastboot.
fastboot flash boot_a patched_boot.img
fastboot: error: cannot get boot partition size
fastboot flash boot_b patched_boot.img
fastboot: error: cannot get boot partition size
fastboot flash boot patched_boot.img
Sending 'boot' (32768 KB) OKAY [ 1.158s]
Writing 'boot' OKAY [ 0.445s]
Finished. Total time: 1.621s
DeviceDevice reboots on its own and boot loops
Use SP Flash Tool to reinstall factory image.
Device boots normally.
Use SP Flash to flash patched boot image.
Device boot loops.
Thoughts? Looks to me that the patched boot.img is invalid. Not sure how to verify or how else to get patched boot.img.

I also tried
fastboot boot patched_boot.img
Device reboots twice and then comes up with stock boot.img.

snickle said:
...
fastboot flash boot patched_boot.img
Sending 'boot' (32768 KB) OKAY [ 1.158s]
Writing 'boot' OKAY [ 0.445s]
Finished. Total time: 1.621s
DeviceDevice reboots on its own and boot loops
...
Thoughts? Looks to me that the patched boot.img is invalid. Not sure how to verify or how else to get patched boot.img.
Click to expand...
Click to collapse
Try installing Magisk using TWRP.
The patched boot.img method is only usually used when TWRP is unavailable.
Make sure you flash the stock boot.img (or the whole stock ROM) before installing TWRP and Magisk.

Got it working using canary version of magisk manager.

Hi, i just wanted to share the exact steps i took to root this tablet.
Funnily enough (for me at least), this was the easiest android device i've rooted out of all the ones i've previously owned. Thanks in part to OP of this thread!
The tablet i have is the following version:
TB-X606F_S300429_211101_BMP
unlock bootloader preparations
1. on tablet: go to Settings->System->About and press "Build number" 7 times to enable Developer Options.
2. go to Settings->System->DeveloperOptions.
3. Turn on: "OEM unlocking" and "USB debugging".
flash/root/recovery preparation
1. install latest: https://developer.android.com/studio/releases/platform-tools#downloads
2. install MTK_Android_USB_Driver
3. download TWRP for Lenovo Tab M10 Plus x606 (put it in the platform-tools directory)
4. reboot computer
5. run CMD command in the platform-tools directory:
fastboot flashing unlock
6. accept the conditions on the tablet screen
7. turn off tablet
8. turn on tablet into recovery mode with: Vol Up + Vol Down + Power (hold steady for several seconds after it vibrates)
9. choose "boot into bootloader" in the menu = now youre in fastboot mode
10. connect USB cable to computer
11. run CMD commands (wait for each commadn to finish ffirst of course):
fastboot flash recovery [TWRP you downloaded].img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot reboot recovery
now youre in TWRP again:
1. finish the decryption in TWRP. (same pin as regular android encryption pin code if you chose one before)
2. do NOT keep read only
3. go to backup tab and make a backup (boot, system, vendor, data)
4. advanced wipe -> wipe "data"
Time to flash root/magisk
1. download Magisk-v23.0.apk
2. rename to zip
3. place the zip in tablet storage via USB cable
4. go to "install" in TWRP
5. select the magisk zip
6. flash magisk
7. reboot into system
8. enable installation of untrusted apk sources in android settings
9. start magisk manager just to check that things are OK
10. download root checker and verify root
11. reboot tablet a bunch of times to see that root is sticking
12. enable developer options again [for some reason it resets this during the flashing/wiping from above steps]

skribb said:
Hi, i just wanted to share the exact steps i took to root this tablet.
Funnily enough (for me at least), this was the easiest android device i've rooted out of all the ones i've previously owned. Thanks in part to OP of this thread!
The tablet i have is the following version:
TB-X606F_S300429_211101_BMP
unlock bootloader preparations
1. on tablet: go to Settings->System->About and press "Build number" 7 times to enable Developer Options.
2. go to Settings->System->DeveloperOptions.
3. Turn on: "OEM unlocking" and "USB debugging".
flash/root/recovery preparation
1. install latest: https://developer.android.com/studio/releases/platform-tools#downloads
2. install MTK_Android_USB_Driver
3. download TWRP for Lenovo Tab M10 Plus x606 (put it in the platform-tools directory)
4. reboot computer
5. run CMD command in the platform-tools directory:
fastboot flashing unlock
6. accept the conditions on the tablet screen
7. turn off tablet
8. turn on tablet into recovery mode with: Vol Up + Vol Down + Power (hold steady for several seconds after it vibrates)
9. choose "boot into bootloader" in the menu = now youre in fastboot mode
10. connect USB cable to computer
11. run CMD commands (wait for each commadn to finish ffirst of course):
fastboot flash recovery [TWRP you downloaded].img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot reboot recovery
now youre in TWRP again:
1. finish the decryption in TWRP. (same pin as regular android encryption pin code if you chose one before)
2. do NOT keep read only
3. go to backup tab and make a backup (boot, system, vendor, data)
4. advanced wipe -> wipe "data"
Time to flash root/magisk
1. download Magisk-v23.0.apk
2. rename to zip
3. place the zip in tablet storage via USB cable
4. go to "install" in TWRP
5. select the magisk zip
6. flash magisk
7. reboot into system
8. enable installation of untrusted apk sources in android settings
9. start magisk manager just to check that things are OK
10. download root checker and verify root
11. reboot tablet a bunch of times to see that root is sticking
12. enable developer options again [for some reason it resets this during the flashing/wiping from above steps]
Click to expand...
Click to collapse
What ADB driver did you use? I cant get a good driver to load in Windows.

@be_the_shooter
Not 100% sure but I think it was Universal ADB Driver 1.0.4 from ClockworkMod. I'm on win7 x64.

How To Guide Rog 5 CN convert to Global Fota update 8030...81

- China tencent version converted to WW
- Download Global Rom and copy to internal stogare :
* WW-18.8030.2101.75 Here 15/03/21
* WW-18.8030.2101.81 Here 23/03/21
- Reboot phone and install
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Does this work on RPG Phone 2 please ?

gushterica said:
Does this work on RPG Phone 2 please ?
Click to expand...
Click to collapse
same with rog 2 firmware

so you don't need any bootloader unlock? I'm on cn rom right now, do I need to factory reset?

Guys, can someone explain simple how to put this rog phone 5 to rog phone 2 please ?
I will be very greatfull.

squaregene said:
so you don't need any bootloader unlock? I'm on cn rom right now, do I need to factory reset?
Click to expand...
Click to collapse
Hey, if you manage to run this, can you please help me out ? Please.

gushterica said:
Hey, if you manage to run this, can you please help me out ? Please.
Click to expand...
Click to collapse
Why are you trying to run a ROG Phone 5 firmware on ROG Phone 2? Isn't there already a WW rom for Rog phone 2?

squaregene said:
Why are you trying to run a ROG Phone 5 firmware on ROG Phone 2? Isn't there already a WW rom for Rog phone 2?
Click to expand...
Click to collapse
The hardware is completely different, so it would not work 99% in my opinion.

squaregene said:
The hardware is completely different, so it would not work 99% in my opinion.
Click to expand...
Click to collapse
I didnt try to run it, i just want ROG 5 ultimate live wallpaper
I hope soon XDA guys will manage to extract them.
Thank you for your answer.

Anyone have same problem as me ? when i try to put the firmware a popup say "update failed" When i check Software Information : RKQ1.201022.002.WW_Phone-18.0810.2101.95
But in the box that say CN version
And in the notifications i have HardwareStub Services that says Warning The installed firmware does not match the device origin...
Anyone have solution ?

michaellock said:
Anyone have same problem as me ? when i try to put the firmware a popup say "update failed" When i check Software Information : RKQ1.201022.002.WW_Phone-18.0810.2101.95
But in the box that say CN version
And in the notifications i have HardwareStub Services that says Warning The installed firmware does not match the device origin...
Anyone have solution ?
Click to expand...
Click to collapse
I also met. I installed Notifications Off from the Play Store and hide the notification
The screen frequency of ROG 3 will be locked, but the screen frequency of ROG 5 is not locked. I don't know if there are other questions.

QiuDer said:
I also met. I installed Notifications Off from the Play Store and hide the notification
The screen frequency of ROG 3 will be locked, but the screen frequency of ROG 5 is not locked. I don't know if there are other questions.
Click to expand...
Click to collapse
I have unlock bootloader / factory reset, after that the Warning disappears and no update available

michaellock said:
I have unlock bootloader / factory reset, after that the Warning disappears and no update available
Click to expand...
Click to collapse
1.First use the 18.0810.2101.95 raw package to flash into the international version
* Suggest enter Recovery mode execute Wipe data/factory reset Make sure the system can enter the desktop
2.Then enter fastboot mode
3.rog5 tool ,PC Use fastboot tool
4.fastboot flash boot root-boot.img
5.Restart the phone
6.Enter the phone system installation Magisk-v22.0 + Root_Explorer-v4.8
7.use Root_Explorer Switch to root Viewer
8.path vendor/factory/COUNTRY Find file open
9.Edit file content Change CN to WW Save
10.This should be able to update the file normally

QiuDer said:
1.First use the 18.0810.2101.95 raw package to flash into the international version
* Suggest enter Recovery mode execute Wipe data/factory reset Make sure the system can enter the desktop
2.Then enter fastboot mode
3.rog5 tool ,PC Use fastboot tool
4.fastboot flash boot root-boot.img
5.Restart the phone
6.Enter the phone system installation Magisk-v22.0 + Root_Explorer-v4.8
7.use Root_Explorer Switch to root Viewer
8.path vendor/factory/COUNTRY Find file open
9.Edit file content Change CN to WW Save
10.This should be able to update the file normally
Click to expand...
Click to collapse
First, Thank for Help
I have install android Studio with Android Driver, Set Variable for SDK Platform (ADB, Fastboot)
Active USB Debugging in developper option, running cmd in Admin, plug USB on the side for fastboot
1.
Using Flashall_AFT.cmd
"FAILED, fastboot.exe flash all WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46_Phone-user.raw failure, EXIT!"
--
Using fastboot.exe flash all WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46_Phone-user.raw
get cpu id fail
FAILED (remote: 'Unknown variable')
get cid fail
FAILED (remote: 'Unknown variable')
get project fail
FAILED (remote: 'Unknown variable')
...
fastboot: error: project name () mapping the wrong raw id (0x33)
--
Using fastboot flash all WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46_Phone-user.raw\WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46_Phone-user.raw
Invalid sparse file format at header magic
...
Sending sparse 'all' 1/27 (251089 KB) error: write_sparse_skip_chunk: don't care size 6834756804 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 6834756804 is not a multiple of the block size 4096
OKAY [ 5.834s]
Writing 'all' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
2.
Ok
3.
Ok, with SDK Platform
4.
Sending 'boot_a' (98304 KB) OKAY [ 2.198s]
Writing 'boot_a' OKAY [ 1.269s]
Finished. Total time: 3.479s
5.
Ok
6.
Install Magisk Pass..
Run Magisk, when popup say to reboot Pass..
Install Root Viewer Pass..
7.
Ok
8.
Ok there is CN in the file
9.
Done replace CN with WW
10.
Placing UL-ASUS_I005_1-ASUS-18.0830.2101.81-1.1.64-user.zip in root of Internal Storage
Then reboot
They work !
I have another question...
Can i re-lock the bootloader ?
I have try :
fastboot oem asus-csc_lk
and
fastboot flashing lock
fastboot flashing lock_critical
fastboot oem lock
fastboot oem lock_critical
fastboot flash !frp-partition! default_key.bin
nothing work
Thanks, and i hope this thread will serve for everyone

michaellock said:
First, Thank for Help
I have install android Studio with Android Driver, Set Variable for SDK Platform (ADB, Fastboot)
Active USB Debugging in developper option, running cmd in Admin, plug USB on the side for fastboot
1.
Using Flashall_AFT.cmd
"FAILED, fastboot.exe flash all WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46_Phone-user.raw failure, EXIT!"
--
Using fastboot.exe flash all WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46_Phone-user.raw
get cpu id fail
FAILED (remote: 'Unknown variable')
get cid fail
FAILED (remote: 'Unknown variable')
get project fail
FAILED (remote: 'Unknown variable')
...
fastboot: error: project name () mapping the wrong raw id (0x33)
--
Using fastboot flash all WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46_Phone-user.raw\WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46_Phone-user.raw
Invalid sparse file format at header magic
...
Sending sparse 'all' 1/27 (251089 KB) error: write_sparse_skip_chunk: don't care size 6834756804 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 6834756804 is not a multiple of the block size 4096
OKAY [ 5.834s]
Writing 'all' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
2.
Ok
3.
Ok, with SDK Platform
4.
Sending 'boot_a' (98304 KB) OKAY [ 2.198s]
Writing 'boot_a' OKAY [ 1.269s]
Finished. Total time: 3.479s
5.
Ok
6.
Install Magisk Pass..
Run Magisk, when popup say to reboot Pass..
Install Root Viewer Pass..
7.
Ok
8.
Ok there is CN in the file
9.
Done replace CN with WW
10.
Placing UL-ASUS_I005_1-ASUS-18.0830.2101.81-1.1.64-user.zip in root of Internal Storage
Then reboot
They work !
I have another question...
Can i re-lock the bootloader ?
I have try :
fastboot oem asus-csc_lk
and
fastboot flashing lock
fastboot flashing lock_critical
fastboot oem lock
fastboot oem lock_critical
fastboot flash !frp-partition! default_key.bin
nothing work
Thanks, and i hope this thread will serve for everyone
Click to expand...
Click to collapse
If it is locked again, it seems that the original system must be used, otherwise it may cause a crash
And may not be unlocked....Unless EDL mode is used, the lock is forced to open
No EDL unlock tool is currently released
Now that there is too little information, I dare not rush to find a way to lock it

empty.cad said:
- China tencent version converted to WW
- Download Global Rom and copy to internal stogare :
* WW-18.8030.2101.75 Here 15/03/21
* WW-18.8030.2101.81 Here 23/03/21
- Reboot phone and install
View attachment 5256725
Click to expand...
Click to collapse
So simple like that sir?? No need unlock bootloader?

Hi there,
Can I reinstall the Chinese firmware after this procedure ? If so, how ?

How to change fingerprint to WW without root access?

yopadato said:
Hi there,
Can I reinstall the Chinese firmware after this procedure ? If so, how ?
Click to expand...
Click to collapse
Hello
Here CN-18.0830.2101.81

michaellock said:
Hello
Here CN-18.0830.2101.81
Click to expand...
Click to collapse
The system won't install this FW once you've installed a WW rom, you need to use a fastboot rom for CN. I found it on another website but unfortunately I had to pay for it.