Develop Bugs

[Guide]Running BackTrack5(Ubuntu Lucid v10.04) On Your ET4G!!!

-Found this little gem posted in this thread, located under the AT&T Samsung Galaxy S II Android Development Forum. So I decided to installed it on my phone and SURPRISE SURPRISE, turns out it works great on our Epic Touch 4G too !
-Anyways, you can follow the instructions which I've quoted right below, and they are also found in the link above. This installation/setup takes all but 5-10minutes if not less!!! Hardest part, if you wanna call it that(its really just the longest part), is downloading the required files. Once you've downloaded all 10 7zip files into a single location, just open ONE OF THEM and extract it by double clicking it and then dragging the bt.img file to your computer. AND you only have to do this to ONE of the downloaded files, no need to open each of them and drag out the bt.img 10 different times, BUT you do need to have all 10 of them copied into the same folder in order for the full image to extract correctly!
-Also, the instructions stated to run the following command:
Code:
su
cd /sdcard/bt
sh installbt.sh
startbt
bt
but they were made for the AT&T version, so on our phones you need to either:
a)copy the bt folder off of /sdcard/external_sd to /sdcard instead; or
b)use the following commands instead:
Code:
su
[B]cd /sdcard/external_sd/bt[/B]
sh installbt.sh
startbt
bt
-If you make use of it, please be sure to thank the originator of it, anantshri, on his thread here, and DooMLoRD on his thread here for assisting in porting it over from the Xperia10 to the SGSII! Good things!
{
"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"
}
DooMLoRD said:
\\----[ Announcement ]----//
[12/July/2011] Updated with new package (bt5_sgs2_shell_scripts_v2.zip) containing shell scripts & busybox
//----[ Announcement ]----\\
hi guys DooMLoRD & anantshri present to u:
BACKTRACK 5 on SGS2
all the work was done by anantshri, i mostly assisted by testing it on my SGS2 and modding it slightly so that it will work properly for SGS2... dont forget to thank him!
i will try n keep it short and simple...
for more details u can read the original thread at X10 sub-forums...
[DEV] BACKTRACK 5 on Xperia X10 chroot
[ Screenshots ]
on startup (shell):
in GUI:
phone + BT5 GUI:
[ Requirements ]
rooted device with busybox installed, if u are using CF-root kernel then u already have busybox installed
Some apps from Android Market:
Android Terminal Emulator
androidVNC
[optional] highly recomended keyboard: Hacker's Keyboard
7zip (for PC), for extracting the files
around 3.3 GB free on internal sdcard (/sdcard/)
[ How To : File Setup ]
u need to do this only once
download the files from the links provided in this thread
extract the files using 7zip to a temporary folder (needs 3.3GB free on that drive)
connect ur SGS2 to PC and mount USB storage
create a folder named 'bt' (without quotes) in the root of ur sdcard and copy the bt.img in that folder
also place the file bt5_sgs2_shell_scripts_v2.zip in root of sdcard, this file has to be flashed via recovery
once u verify that the above is correct then un-mount usb storage
reboot into recovery and flash the file bt5_sgs2_shell_scripts_v2.zip stored in root of sdcard (or if u are using CWM app then just select the file for flashing and the app will do the rest )
once ur phone reboots into OS just check the /sdcard/bt folder
final directory structure should look like this:
/sdcard/bt/bt
/sdcard/bt/bt.img
/sdcard/bt/installbt.sh
/sdcard/bt/startbt
/sdcard/bt/stopbt
once u verify that the above is correct then u can proceed
[ How To : Launch BT ]
start Terminal Emulator app on ur SGS2 and enter the following commands step by step (accept/allow any SuperUser request/popup that u may receive)
su
cd /sdcard/bt
sh installbt.sh
startbt
bt
now u are in BackTrack5 shell
to launch GUI (vncserver) enter the following command
ui
now note the number N shown localhost:N
e.g. as u can see from the above image that "New 'X' desktop is localhost:1", so N=1
the vncserver is running at (5900 + N, N=1 ; so server port is 5901)
now launch androidVNC app on phone and fill in the detials as follows
Nick : bt
Address : 127.0.0.1
Port : 5901
Password : 12345678
Username : <leave it blank>
Color Format : 24-bit color (4 bpp)
inside vnc window select input mode (i personally recommend the following)
TouchPad (here your screen works like a big touchpad use it to navigate mouse.)
and then press connect... now u are in BackTrack GUI!
if u want to exit/close BT5 then u need to follow these steps:
close the androidVNC app (Menu -> Disconnect)
go back into Terminal Emulator app and enter the following commands
u should be at this shell [email protected]:~#
killui
exit
now u will get back to this shell> #
now enter the following commands to stop bt and exit
stopbt
exit
exit
u can now exit the Terminal Emulator app
i would also recommend that u reboot ur phone
[ Important Info ]
root password is 12345678
[ Download Links ]
update.zip package containing shell scripts, busybox (which gets installed to temporary location) [to be flashed via recovery]
this will not disturb/conflict with busybox of ur ROM/CF-Root kernel
bt5_sgs2_shell_scripts_v2.zip (~800KB)
main bt.img
these links are 7zip archives split into 50mb files, u will need to download the following:
total size: 486MB
bt.7z.001 (50 MB)
bt.7z.002 (50 MB)
bt.7z.003 (50 MB)
bt.7z.004 (50 MB)
bt.7z.005 (50 MB)
bt.7z.006 (50 MB)
bt.7z.007 (50 MB)
bt.7z.008 (50 MB)
bt.7z.009 (50 MB)
bt.7z.010 (36 MB)
also uploading to mediafire for mirroring...
Mediafire Folder: http://www.mediafire.com/?f9gk3p3t9wip5
md5 hashes:
Code:
bt.7z.001 f19e769bf42b44867c8bb1d9bb9c5d44
bt.7z.002 a4dd26a98d2c6925d871fb108fb5fadb
bt.7z.003 ecca5a5d72c449117b1d3dbc23aeb1a2
bt.7z.004 8ad487a01e4d149f0247ad9288201f32
bt.7z.005 adab9cb3778cd8ac89ccc0e21997c3d7
bt.7z.006 ba6a28de70a1115dc316f45cea508215
bt.7z.007 f59757e891631607e1a35abadb231b3b
bt.7z.008 cdb8c28a1fbd03657bb42e8d69f0600b
bt.7z.009 426d892f872679e3d53d0ebb0376e138
bt.7z.010 c7d2957bc65340d967b9dd3646d7cb39
ENJOY!
Click to expand...
Click to collapse

ScreenShots

does injection and/or wep hacking works?

leond said:
does injection and/or wep hacking works?
Click to expand...
Click to collapse
Unfortunately it does not...I know the main purpose running BackTrack is being able to use its Networking Security Tools, but it is based on Ubuntu Lucid, v10.04 LTS, so you're still able to run a fully functional operating system on your mobile phone! ATM its more of a novelty than a practicality but Im hoping they find a way to turn the tables soon !

Double Post

Triple Post

Nice thanks for trying it and sharing it!

Question the 10 files that you say to download they can not be extracted? i tryed or am i doing it wrong and when i run commands it fails at bt and says chroot cant execute bin/bash no such file or directory help please!

can you still txt and make calls with this?? looks awesome tho

kyhassen said:
can you still txt and make calls with this?? looks awesome tho
Click to expand...
Click to collapse
It side loads it, so you still get all your notifications and phone calls, and if you just hit the home button it'll take you back to the android OS, it doesn't NOT replace it
donnyevo4g said:
Question the 10 files that you say to download they can not be extracted? i tryed or am i doing it wrong and when i run commands it fails at bt and says chroot cant execute bin/bash no such file or directory help please!
Click to expand...
Click to collapse
They ALL have to be downloaded into the same location before you can successful extract it. ie, if you have bt.7z.001 - bt.7z.009 and are missing bt.7z.010, it will not work....did you download and flash the zip? There's more steps than just extracting the bt image(10 7zip files), also just a heads up, when flashing the zip make sure to clear both cache and dalvik, or you may get an installation error...let me know if you need additional help

all ten of the files i downloaded and put into a folder called bt and i flashed the zip and did not get any error message i have 7zip on my pc and it does not even give me the option to extract what am i doing wrong when i right click on the files and go to properties the file type is not a unzippable file

donnyevo4g said:
all ten of the files i downloaded and put into a folder called bt and i flashed the zip and did not get any error message i have 7zip on my pc and it does not even give me the option to extract what am i doing wrong when i right click on the files and go to properties the file type is not a unzippable file
Click to expand...
Click to collapse
Gotcha! wasn't really sure what kind of error you were having but if that is it, all you need to do is double click on any one of the files, I used the bt.7z.001, and when it opens, just drag the bt.img file to your desktop, and let it extract! Its not really a zip so thats why it doesn't have an option to extract it in the menu but again just double click on anyone of them and you'll be all good broda!

ok i got the one file to extract but the others wont now what do i do once i have that image file do i put it in the bt folder and then run commands?

donnyevo4g said:
ok i got the one file to extract but the others wont now what do i do once i have that image file do i put it in the bt folder and then run commands?
Click to expand...
Click to collapse
-Yup you got it! They way 7z file work is that it evenly breaks a larger file down into multiple smaller .7z files.
-In this example, the bt.img file is about 486MB. So, 9/10 of the bt.7z files are 50MB each and then the 10th file, holding the remain bytes, is 36MB. So once you have them all downloaded into the same location, you can open ANY one of them and drag its content to the hard drive, and it will extract the entire 486MB, using all of the files. And you only have to do this ONCE, you DON'T have to open each of them and drag all of their content out.
-So yea, now copy the bt.img file to the bt folder located in the /sdcard/external_sd folder, and then copy the entire bt folder to the /sdcard folder instead(Im guessing the ATT version doesn't have an external sd card, cuz the cd /sdcard/bt command is for the /sdcard location and not /sdcard/external_sd, which is where flashing the zip places the bt folder). So in the end you're going to use this /sdcard/bt folder and not /sdcard/external_sd/bt...EDITED..and don't quote me on the .7z file sizes from above, not really sure how large they are cuz looking at the file now in my phone its 3.26GB, I was using 50MB for an easy explanation and arguments sake only, thx...and Im actually gonna update OP w/ the step needing to copy the bt folder from the /sdcard/external_sd location to /sdcard instead

now im getting a chroot error when i type bt it says chroot execute bin/bash innput/output error? HELPPPPP

donnyevo4g said:
now im getting a chroot error when i type bt it says chroot execute bin/bash innput/output error? HELPPPPP
Click to expand...
Click to collapse
post exactly what you have done so far and what commands you are able to enter successfully and at what command you are getting the error, thx

Posting now stay online

Heres the error im getting look towards the bottom

donnyevo4g said:
Heres the error im getting look towards the bottom
Click to expand...
Click to collapse
ok and where's the rest of the info I asked for?

i can only fit so much in the screen shot what else you looking for

[Guide] Root Oppo F1s(A1601) + SuperSU without custom recovery or unlocked bootloader

EDIT: This root method has been outdated, see the newer guide instead https://forum.xda-developers.com/android/general/tutorial-root-oppo-f1s-flashtool-6-0-t3651220
Why I made this tutorial:
Recently some members claimed that KingRoot is not working for Oppo F1s(A1601) anymore, I assume it's because Kingroot uses cloud based root method, means Kingroot downloads root package and command from cloud and execute on your phone. Maybe the problem was caused by the change of their server, some configuration has been replaced? At this time, I still have a working root method working now, so I would like to share it with everyone Also, you can follow this guide to get rid of the superuser App from those android root exploit app and use SuperSU.
In short, this tutorial tells:
1.How to Root Oppo F1s(A1601) with KingoRoot.(Though cloud based root App Kingroot is not working at this period but KingoRoot the offline one is still working)
2.Though KingoRoot prevent you to switch to other superuser App, we can still replace it with SuperSU with few steps, no custom recovery needed.
****NOTE****
There're various version of KingoRoot apk over the Internet, use the APK version I provided at attachment can guarantee there're no unexpected errors.
The script to replace kingo root was based on the one here but with a little modification, I've added a infinite loop for the script because KingoRoot cause a force reboot(soft reset) right after you delete root from the app, I assume its because KingoRoot want to prevent you to replace it. A infinite loop can make sure the file copying action has been done before your phone reboot.
Steps to Root F1s and Install SuperSU:
1.Install android terminal from Google Play: https://play.google.com/store/apps/details?id=jackpal.androidterm
2.Download the attachment, extract the zip archive, you get an APK "KingoRoot.apk" and a folder "rmkingo", copy the APK and the folder to your Internal storge(Sdcard)
3.Use any file management App to open KingoRoot.apk and install KingoRoot.apk
4.Open KingoRoot and click "one click root" then wait it to obtain root
5.After root succeeded, Open previous installed "Terminal Emulator for Android" and type
Code:
su
. Now KingoRoot's Superuser should pop up and ask you if you want to grant root access, allow it.
6.Now change terminal directory to the script folder, terminal type
Code:
cd /sdcard/rmkingo
7.Now execute the first script, terminal type
Code:
sh step0.sh
8.If there's no error on the previous action, Now proceed to execute the second script which is an infinite loop, you might see infinite error message after you executed it, terminal type
Code:
sh step1.sh
9.Now make sure the Terminal emulator is still open and the script is still running in background, just open SuperUser(installed by KingoRoot), find and click "Remove root" in the option of the App.
10.Your phone should be forced reboot now, after reboot, install SuperSU from google play: https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=zh_TW
11.Open SuperSU and update su binary file with normal mode and wait, it should finish in 2-3 minutes.
12.Hit thanks(My pleasure)
{
"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"
}
above method has been confirmed working with the latest rom from my region,(date 2017/02/12 still working)
Rom: A1601_TW_11_A.17_161003

I am on build a1601ex_11_a27_170111
its currently letest update in india

sagargjasani264 said:
I am on build a1601ex_11_a27_170111
its currently letest update in india
Click to expand...
Click to collapse
Wow, Taiwan haven't receive any update since October........Looks like the rom of our region is terribly outdated,lol
A lot of people complaint on oppo forum of our region why there're no updates........
Is it method work for the rom from india?

evilhawk00 said:
wow, taiwan haven't receive any update since october........looks like the rom of our region is terribly outdated,lol
a lot of people complaint on oppo forum of our region why there're no updates........
Is it method work for the rom from india?
Click to expand...
Click to collapse
kingoroot is on 90% since last 20min
---------- Post added at 12:22 PM ---------- Previous post was at 12:10 PM ----------
sorry bro but kingoroot faild...

Sorry kingoroot failed error code : 0x196514

Lyes2 said:
Sorry kingoroot failed error code : 0x196514
Click to expand...
Click to collapse
Hi, I assume you have to downgrade your rom. Find a older version of your rom, flash it via OPPO stock recovery and this method will work.
In my region, Taiwan's newest rom date is 2016 October, so this method work. OPPO might fixed this CVE exploit in their new rom.
The rom I currently use can be downloaded from OPPO Taiwan website, however I'm not sure if it can work on your device, so you might need to find an older version of your region
You can try to get root with older firmware, flash twrp recovery with root app, such as rashr,then once you have twrp recovery, you can flash the new OTA update package, but be sure to modify the update package so you will not loose root after update. However, I think just stick with older firmware will be easier

Failed
Directory not found bro

evilhawk00 said:
Hi, I assume you have to downgrade your rom. Find a older version of your rom, flash it via OPPO stock recovery and this method will work.
In my region, Taiwan's newest rom date is 2016 October, so this method work. OPPO might fixed this CVE exploit in their new rom.
The rom I currently use can be downloaded from OPPO Taiwan website, however I'm not sure if it can work on your device, so you might need to find an older version of your region
You can try to get root with older firmware, flash twrp recovery with root app, such as rashr,then once you have twrp recovery, you can flash the new OTA update package, but be sure to modify the update package so you will not loose root after update. However, I think just stick with older firmware will be easier
Click to expand...
Click to collapse
what kind of modification do you exactly need to do to the update package to not loose root after update?

ngoralph said:
what kind of modification do you exactly need to do to the update package to not loose root after update?
Click to expand...
Click to collapse
I made one and got root with A27 , all you need is a twrp and a twrp flashable firmware zip.
Here's what I did,first I found that the TWRP by @BouyaPK did not have the same device model settings in comparison with the stock recovery, so I made a little modification to his TWRP image, now the offical firmware zip can pass Device detection test.
!!Before doing it , make sure you have flashed the modified recovery(the one from attachment) to your phone, official firmware is only flashable via this modified recovery and stock recovery
Download here
View attachment OPPO_F1s_twrp3.0_modified_devicemodel.zip
this is the example with the ota update package (A19 to A27 upgrade package around 150mb via coloros update manager app)
Now lets start to modify official firmware, follow my steps:
1.extract the newest official firmware zip.
2.now open the extracted folder, navigate to \META-INF\com\google\android\
3.find the file updater-script and open it with text editor( I suggest NotePad++)
4.you'll find a lot of lines start with apply_patch(xxxxx), remove the one with this file "/system/recovery-from-boot.p"
5.(if needed) also remove boot image sha1 check, in my case I have magisk installed, my boot image do not have the same sha1 value with stock boot image, so I found the line that checkes boot.img and remove it
6.done the file edit and save the file
7.repack it back to a zip file and sign the package with test keys
How to sign?
1.Download the sign package from attachment
2.have Java installed on your PC
3.Open a terminal at the same location with the keys and signapk.jar
4.terminal type
Code:
java -jar signapk.jar -w platform.x509.pem platform.pk8 my_modified_firmware.zip my_modified_firmware-signed.zip
8.install with twrp and you still have twrp exist, flash supersu zip or magisk zip
above is the way to modify a PATCH zip ota file, if you are modifying a full package, which may be easier,
the full package's update script write full image to phone instead, so you just need to modify the image in the ota package.
all you just have to make sure the new firmware do not replace twrp with stock recovery, so
1.try to extract the image in the package and modify the image file, remove files such as "recovery-from-boot.p" from the image then rebuild the image and calculate the new sha1 value of the new image(CarlivImageKitchen is a good tool to rebuild image)
2.replace the old sha1 hash in updater-script, repack and sign the zip.
3.flash with twrp
4.flash superSu zip or magisk zip after the firmware flash with twrp can get root.

evilhawk00 said:
I made one and got root with A27 , all you need is a twrp and a twrp flashable firmware zip.
Here's what I did,first I found that the TWRP by @BouyaPK did not have the same device model settings in comparison with the stock recovery, so I made a little modification to his TWRP image, now the offical firmware zip can pass Device detection test.
!!Before doing it , make sure you have flashed the modified recovery(the one from attachment) to your phone, official firmware is only flashable via this modified recovery and stock recovery
Download here
this is the example with the ota update package (A19 to A27 upgrade package around 150mb via coloros update manager app)
Now lets start to modify official firmware, follow my steps:
1.extract the newest official firmware zip.
2.now open the extracted folder, navigate to \META-INF\com\google\android\
3.find the file updater-script and open it with text editor( I suggest NotePad++)
4.you'll find a lot of lines start with apply_patch(xxxxx), remove the one with this file "/system/recovery-from-boot.p"
5.(if needed) also remove boot image sha1 check, in my case I have magisk installed, my boot image do not have the same sha1 value with stock boot image, so I found the line that checkes boot.img and remove it
6.done the file edit and save the file
7.repack it back to a zip file and sign the package with test keys
How to sign?
1.Download the sign package from attachment
2.have Java installed on your PC
3.Open a terminal at the same location with the keys and signapk.jar
4.terminal type
8.install with twrp and you still have twrp exist, flash supersu zip or magisk zip
above is the way to modify a PATCH zip ota file, if you are modifying a full package, which may be easier,
the full package's update script write full image to phone instead, so you just need to modify the image in the ota package.
all you just have to make sure the new firmware do not replace twrp with stock recovery, so
1.try to extract the image in the package and modify the image file, remove files such as "recovery-from-boot.p" from the image then rebuild the image and calculate the new sha1 value of the new image(CarlivImageKitchen is a good tool to rebuild image)
2.replace the old sha1 hash in updater-script, repack and sign the zip.
3.flash with twrp
4.flash superSu zip or magisk zip after the firmware flash with twrp can get root.
Click to expand...
Click to collapse
Can you send me a stock recovery for Oppo F1s or Color Os 3.0 version
[email protected]
I want ask to my friend to build the custom rom with latest version of TWRP.

Ananaqil12 said:
Can you send me a stock recovery for Oppo F1s or Color Os 3.0 version
[email protected]
I want ask to my friend to build the custom rom with latest version of TWRP.
Click to expand...
Click to collapse
If you want stock recovery image, check my reply here https://forum.xda-developers.com/showpost.php?p=71006625&postcount=26

evilhawk00 said:
I made one and got root with A27 , all you need is a twrp and a twrp flashable firmware zip.
Here's what I did,first I found that the TWRP by @BouyaPK did not have the same device model settings in comparison with the stock recovery, so I made a little modification to his TWRP image, now the offical firmware zip can pass Device detection test.
!!Before doing it , make sure you have flashed the modified recovery(the one from attachment) to your phone, official firmware is only flashable via this modified recovery and stock recovery
Download here
View attachment 4137856
this is the example with the ota update package (A19 to A27 upgrade package around 150mb via coloros update manager app)
Now lets start to modify official firmware, follow my steps:
1.extract the newest official firmware zip.
2.now open the extracted folder, navigate to \META-INF\com\google\android\
3.find the file updater-script and open it with text editor( I suggest NotePad++)
4.you'll find a lot of lines start with apply_patch(xxxxx), remove the one with this file "/system/recovery-from-boot.p"
5.(if needed) also remove boot image sha1 check, in my case I have magisk installed, my boot image do not have the same sha1 value with stock boot image, so I found the line that checkes boot.img and remove it
6.done the file edit and save the file
7.repack it back to a zip file and sign the package with test keys
How to sign?
1.Download the sign package from attachment
2.have Java installed on your PC
3.Open a terminal at the same location with the keys and signapk.jar
4.terminal type
Code:
java -jar signapk.jar -w platform.x509.pem platform.pk8 my_modified_firmware.zip my_modified_firmware-signed.zip
8.install with twrp and you still have twrp exist, flash supersu zip or magisk zip
View attachment 4137905
above is the way to modify a PATCH zip ota file, if you are modifying a full package, which may be easier,
the full package's update script write full image to phone instead, so you just need to modify the image in the ota package.
all you just have to make sure the new firmware do not replace twrp with stock recovery, so
1.try to extract the image in the package and modify the image file, remove files such as "recovery-from-boot.p" from the image then rebuild the image and calculate the new sha1 value of the new image(CarlivImageKitchen is a good tool to rebuild image)
2.replace the old sha1 hash in updater-script, repack and sign the zip.
3.flash with twrp
4.flash superSu zip or magisk zip after the firmware flash with twrp can get root.
Click to expand...
Click to collapse
There are no lines that say apply patch

diosdetiempo said:
[/HIDE]
There are no lines that say apply patch
Click to expand...
Click to collapse
As I mentioned, only the small OTA Update package(smaller than 300MB) extracted from Built in update manager App has the line apply patch.
You are using a full package which is another situation.
If you have the full ota firmware downloaded from official website, you can try the follow steps
1.first make a nandroid backup of the old 5.1, make sure you can always restore your phone with backup
2.flash the official firmware zip with the twrp I attach( if any error occurred,do not reboot ,restore your phone with nandroid backup, also write down the error, and see which image file does not have the match SHA1, calculate and modify the sha1 of that line)
3.if step 2 succed ,do not reboot flash superSU zip file
4reboot, you may have superSU and your twrp may be replaced by stock recovery, use rashr flash twrp back again since you have root

evilhawk00 said:
As I mentioned, only the small OTA Update package(smaller than 300MB) extracted from Built in update manager App has the line apply patch.
You are using a full package which is another situation.
If you have the full ota firmware downloaded from official website, you can try the follow steps
1.first make a nandroid backup of the old 5.1, make sure you can always restore your phone with backup
2.flash the official firmware zip with the twrp I attach( if any error occurred,do not reboot ,restore your phone with nandroid backup, also write down the error, and see which image file does not have the match SHA1, calculate and modify the sha1 of that line)
3.if step 2 succed ,do not reboot flash superSU zip file
4reboot, you may have superSU and your twrp may be replaced by stock recovery, use rashr flash twrp back again since you have root
Click to expand...
Click to collapse
It worked!
Here's a little guide
1) Put your TWRP, SuperSU and Android 6.0 Oppo F1S ROM onto SD card
2) Use Flashify to flash TWRP
3) Reboot into TWRP recovery
4) Flash Android 6.0 F1S ROM
5) Flash SuperSU
6) Reboot phone and you should be good to go

evilhawk00 said:
As I mentioned, only the small OTA Update package(smaller than 300MB) extracted from Built in update manager App has the line apply patch.
You are using a full package which is another situation.
If you have the full ota firmware downloaded from official website, you can try the follow steps
1.first make a nandroid backup of the old 5.1, make sure you can always restore your phone with backup
2.flash the official firmware zip with the twrp I attach( if any error occurred,do not reboot ,restore your phone with nandroid backup, also write down the error, and see which image file does not have the match SHA1, calculate and modify the sha1 of that line)
3.if step 2 succed ,do not reboot flash superSU zip file
4reboot, you may have superSU and your twrp may be replaced by stock recovery, use rashr flash twrp back again since you have root
Click to expand...
Click to collapse
update: the only issue i find is that SIM card isn't recognized

diosdetiempo said:
update: the only issue i find is that SIM card isn't recognized
Click to expand...
Click to collapse
sim card not recognized!? Sorry I can't really understand the reason of that because I don't have this problem.
Just a thought, maybe you lost baseband? Can you see your phone's IMEI number in settings? If you found null IMEI, that means you have lost your baseband, otherwise that's just something else maybe a small unknown issue, may also be the access point and protocol was not included in the 6.0 rom
If you lost your IMEI, I assume you already did the nandroid backup before, in twrp backup of NVRAM is the IMEI part, you should be able to recover your IMEI with that nvram backup

evilhawk00 said:
sim card not recognized!? Sorry I can't really understand the reason of that because I don't have this problem.
Just a thought, maybe you lost baseband? Can you see your phone's IMEI number in settings? If you found null IMEI, that means you have lost your baseband, otherwise that's just something else maybe a small unknown issue, may also be the access point and protocol was not included in the 6.0 rom
If you lost your IMEI, I assume you already did the nandroid backup before, in twrp backup of NVRAM is the IMEI part, you should be able to recover your IMEI with that nvram backup
Click to expand...
Click to collapse
have you tested with 6.0?

evilhawk00 said:
I made one and got root with A27 , all you need is a twrp and a twrp flashable firmware zip.
Here's what I did,first I found that the TWRP by @BouyaPK did not have the same device model settings in comparison with the stock recovery, so I made a little modification to his TWRP image, now the offical firmware zip can pass Device detection test.
!!Before doing it , make sure you have flashed the modified recovery(the one from attachment) to your phone, official firmware is only flashable via this modified recovery and stock recovery
Download here
View attachment 4137856
this is the example with the ota update package (A19 to A27 upgrade package around 150mb via coloros update manager app)
Now lets start to modify official firmware, follow my steps:
1.extract the newest official firmware zip.
2.now open the extracted folder, navigate to \META-INF\com\google\android\
3.find the file updater-script and open it with text editor( I suggest NotePad++)
4.you'll find a lot of lines start with apply_patch(xxxxx), remove the one with this file "/system/recovery-from-boot.p"
5.(if needed) also remove boot image sha1 check, in my case I have magisk installed, my boot image do not have the same sha1 value with stock boot image, so I found the line that checkes boot.img and remove it
6.done the file edit and save the file
7.repack it back to a zip file and sign the package with test keys
How to sign?
1.Download the sign package from attachment
2.have Java installed on your PC
3.Open a terminal at the same location with the keys and signapk.jar
4.terminal type
Code:
java -jar signapk.jar -w platform.x509.pem platform.pk8 my_modified_firmware.zip my_modified_firmware-signed.zip
8.install with twrp and you still have twrp exist, flash supersu zip or magisk zip
View attachment 4137905
above is the way to modify a PATCH zip ota file, if you are modifying a full package, which may be easier,
the full package's update script write full image to phone instead, so you just need to modify the image in the ota package.
all you just have to make sure the new firmware do not replace twrp with stock recovery, so
1.try to extract the image in the package and modify the image file, remove files such as "recovery-from-boot.p" from the image then rebuild the image and calculate the new sha1 value of the new image(CarlivImageKitchen is a good tool to rebuild image)
2.replace the old sha1 hash in updater-script, repack and sign the zip.
3.flash with twrp
4.flash superSu zip or magisk zip after the firmware flash with twrp can get root.
Click to expand...
Click to collapse
ok got it to work for a full firmware package here's what i did
1 . downloaded a27 (still 5.1 since 6.0 is not stable according to some)
2. using the twrp above flashed a27
3. flashed magisk
4. flash the twrp image again to make sure that incase it was overwritten by the update
NOTE: i did get an error like unable to mount dev/block/platform/...... it was fine for me

ngoralph said:
ok got it to work for a full firmware package here's what i did
1 . downloaded a27 (still 5.1 since 6.0 is not stable according to some)
2. using the twrp above flashed a27
3. flashed magisk
4. flash the twrp image again to make sure that incase it was overwritten by the update
NOTE: i did get an error like unable to mount dev/block/platform/...... it was fine for me
Click to expand...
Click to collapse
6.0 would work if the sim card issue could be fixed. i can't work it out :/

diosdetiempo said:
6.0 would work if the sim card issue could be fixed. i can't work it out :/
Click to expand...
Click to collapse
did you try restoring the nvram using twrp as stated before?
and did you wipe your data before flashing?? i think the transition from 5.1 to 6.0 may have broke some things read about it somewhere that wiping was necessary for LP to MM

[GUIDE] Flash 'fastboot ROMs' for Lenovo Z6 Pro

Disclaim
All steps described here have been many times tested and proved to be safe but, you may know that sometimes in life unexpected things happen. I'm not responsible for any damage in your devices, do things at your own risk.
Introduction
Thanks to xda user @alexeei we can install almost every Z6 Pro stock ROMs using the Fastboot Mode. You always should check the package content and the installation script(s) to be sure that you know exactly what is gonna be installed. You can find all the ROMs listed and linked in this index.
Let's go with the guide.
0. Pre-requirements
- The Bootloader must be unlocked.
- Lenovo drivers installed in your computer. You can download them here . Thanks @benjieb
1. Download and extract the ROM
You cand find many of them here. Extract the downloaded file and a folder will be created with these contents:
- All the files required for the installation in Fastboot Mode.
- The ROM files.
- The .bat file(s) which contain(s) all the actions that will be performed during the installation.
{
"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"
}
You always should check the content of the .bat file(s). Read post #2 to get more info about this.
2. Reboot your device in Fastboot Mode
Shut down your device and boot it holding pressed both Volume Down + Power buttons until the Fastboot Mode menu appears. You can navigate in the Fastboot Mode menu with volume buttons to choose the options and the Power button to confirm, but at this point you don't need to do any action in this menu.
3. Connect the device to the computer with USB cable
4. Execute the .bat file
Just execute the .bat file with a double click and a CMD window will be opened and the installation will start. Only a few lines will appear at the beginning and then nothing will happen, it will seem to be stopped but actually it's not, just be patient because this screen could last around ten minutes. So despite of the 'Invalid sparse file format at header magic", keep the faith and don't do anything but wait.
The device will reboot once the installation is done.
5. Errors in the log. No voice in calls.
Some errors may appear in the CMD window during the installation, this is because some partitions are 'critical' and we're not allowed to modify them via fastboot. Usually this is not a problem because these "small partitions" don't prevent the new ROM to work normally, except if you're installing Android 10 from Android 9. If you change Android version with this method you will find that your micro doesn't work in calls. You can fix it installing these "small partitions" from TWRP.
Any correction, info or advise about this post will be very welcome.

About the .bat file(s):
You always should check the content of these files before doing any installation, specially with recent fastboot installers including several .bat files for diferent uses. Just open the .bat file with right click and select Edit to view the actions included in the file.
None of Alexei's fastboot installers have never included any command to erase Data, but I'd say it's mandatory to check twice the .bat file to be sure that you're not going to affect an undesired partition. In case e.g. the .bat file includes the line 'fastboot flash system system.img' but you don't want System partition to be installed, just delete this line from the file and Save before closing it.
Maybe you want to edit the file to include in the batch any other thing, a custom recovery for instance. Just drop your custom recovery file in the rom folder (the fastboot installer folder) and make sure that the line in the .bat file regarding the recovery matchs with your recovery file name.
Also you can notice that recent fastboot installers include more than one .bat file. They are named in a descriptive way like "UpdateZUI.bat" or "UpsateAOSP", but you should check them anyways. Let's say you're using any of the Q aosp-based custom ROMs (they include Boot and System partitions) and you want to update the vendor and/or the firmware. You should check the .bat files to find which of them suits better with your needs.

descarao81 said:
About the .bat file(s):
You always should check the content of these files before doing any installation, specially with recent fastboot installers including several .bat files for diferent uses. Just open the .bat file with right click and select Edit to view the actions included in the file.
None of Alexei's fastboot installers have never included any command to erase Data, but I'd say it's mandatory to check twice the .bat file to be sure that you're not going to affect an undesired partition. In case e.g. the .bat file includes the line 'fastboot flash system system.img' but you don't want System partition to be installed, just delete this line from the file and Save before closing it.
Maybe you want to edit the file to include in the batch any other thing, a custom recovery for instance. Just drop your custom recovery file in the rom folder (the fastboot installer folder) and make sure that the line in the .bat file regarding the recovery matchs with your recovery file name.
Also you can notice that recent fastboot installers include more than one .bat file. They are named in a descriptive way like "UpdateZUI.bat" or "UpsateAOSP", but you should check them anyways. Let's say you're using any of the Q aosp-based custom ROMs (they include Boot and System partitions) and you want to update the vendor and/or the firmware. You should check the .bat files to find which of them suits better with your needs.
Click to expand...
Click to collapse
Thanks for your instruction. Will this method work on other lenovo devices. I have a lenovo tablet running android 10 chinese stock rom, now I would like to flash global stock rom

hilary trump said:
Thanks for your instruction. Will this method work on other lenovo devices. I have a lenovo tablet running android 10 chinese stock rom, now I would like to flash global stock rom
Click to expand...
Click to collapse
It depends on the rom package. The packages made to be installed using fastboot are usually very similar, but you should check the .bat files. I could take a look if you provide a link.

descarao81 said:
It depends on the rom package. The packages made to be installed using fastboot are usually very similar, but you should check the .bat files. I could take a look if you provide a link.
Click to expand...
Click to collapse
Thanks. The rom has not released yet. I just pre-ordered a chinese variant tablet P11 pro TB-J706F

descarao81 said:
It depends on the rom package. The packages made to be installed using fastboot are usually very similar, but you should check the .bat files. I could take a look if you provide a link.
Click to expand...
Click to collapse
I found the link as follows
mirrors.lolinet.com/firmware/lenovo/ Tab_P11_Pro/TB-J706F/TB-J706F_S210002_201015_ROW.zip
But inside the package there is no BAT file though

How To Guide Flash stock ROM or downgrade ColorOS 12 on OPPO Reno6 5g(CPH2251-MT6877 chip) by using free MTK client GitHub tool.

Hey Guys,
After color OS 12 (and android 12) upgrade on OPPO reno6 5G device, users were facing issues like third part apps not working(Intune company portal work profile, Ritam news app etc),battery draing very rapidly,always on display not working and many more.
So, here I have come up with a method to flash stock ROM or downgrade color OS 12 and switch back to Color OS 11.3 which have android 11. So without wasting time lets start
Note: Data will be erased in this method so please take backup of you data on phone.
This has been tested on Indian version, I am not sure if it will work for other countries.
I strongly recommend to take full firmware backup using method below before proceeding
Backup full firmware(ROM) of any MediaTek device using MTK client| Oppo reno6 5G | MT6877
Hello Guys, Many times we encounter a situation where we need to do some software update, flash custom ROM, install stock ROM etc, so it is advisable to take full firmware/ROM backup of your device. If required then you can flash this backup to...
forum.xda-developers.com
Step1: Pre-requisite -Installing required drivers and setup
From links below download and install drivers and setup.
Install mediaTek driver.
Install python (during installation of python please select "install for all user" from customization and tick add path to system variable).
install usbdk.
download extarct Mtk client tool.
go to folder where you extract mtk client
{
"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"
}
open cmd here and run below command
cd mtkclient
pip3 install -r requirements.txt
In default setting it takes 2 hour to flash but after change it takes 13 min only. So, If you want to increase flashing speed then open mtk_daxflash.py file from library folder, search "dsize = min(length, 0x200)" and replace it with "dsize = min(length, 0x2004)" , save and close the file.
You need to close the command prompt and reopoen it in order to take effect of change.
Reference(https://github.com/bkerler/mtkclient/issues/271)
New Qcom Mtk Driver V3.0.5.1.rar | by TUSER HP for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Download Python
The official home of the Python Programming Language
www.python.org
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
Releases · daynix/UsbDk
Usb Drivers Development Kit for Windows. Contribute to daynix/UsbDk development by creating an account on GitHub.
github.com
Step2: Download and extract the stock firmware
CPH2251_A.13_ColorOS11.3_Android11_Latest.rar
drive.google.com
Step3: Flash the firmware
on cmd type below command to flash the firmware
python mtk wl "stock ROM location full path"
it will wait for devices.. Power off the phone, wait 10 sec then press vol up + vol down together and then plug the usb cable.
Once device detected , it will display devices information and start flashing
While flashing it will dump the preloader, this file is very important so, please keep this file safely. this file may require in future.
Step4: Boot the phone
Once flashing completed, press vol up + power button together for 30 sec. Wait for device to boot.
Step5: Flashing the preloader.bin (only if required)
In case, even after flashing completed successfully but some time device does not boot, only black screen, no charging sign either then don't panic, device has entered into emergency download mode, if you face the same then it's time to flash preloader.bin file. Follow below steps
1) download SP flash tool specific version v5.2148. (https://androidmtk.com/smart-phone-flash-tool)
2) download attached preloader.bin, scatter file and auth file from link below and place all these files at same folder.
MT6877_flashing_preloader.zip
drive.google.com
3) open sp flash tool, select download agent files from mtk folder as shown on image and load scater file and auth files respectively.
4) In cmd run command "python mtk payload". Now press and hold vol+ vol- or all the buttons together, it should show payload sent successfully.
5) Now in sp flash tool click on Download button, it should flash the preloader successfully.
6) once preloader is flash successfully you can turn on the phone by pressing vol+ and power button together for 20 sec. If attached preloader does't flash then you can try flashing your device backup preloader.bin created/shown on step3.
So by this way we flashed stock firmware on oppo reno6 5G.
Tips: If due to some reason flashing did not completed successfully then please press vol up and power button together for 30-40 sec to boot the phone (exit the brom mode).
Disclaimer: I have tested this method on my phone, it's 100% working but I will not responsible if damage any damage happens to your device while doing this. So do it at your own risk.

It's work sir
Many thanks
Nand kumar said:
Step1: Pre-requisite -Installing required drivers and setup
Install MediaTek drivers, in windows 10 you need to disable driver signature enforcement.
Install paython, usbdk.
download extarct Mtk client tool.
go to folder where you extract mtk client
open cmd here and run below command
cd mtkclient
pip3 install -r requirements.txt
Click to expand...
Click to collapse
In this step the command should be
pip install -r requirements.txt
it's will work

killian07 said:
It's work sir
Many thanks
In this step the command should be
pip install -r requirements.txt
it's will work
Click to expand...
Click to collapse
Did you also took firmware back using my method or you just flashed the ROM?

Thanks for your work

You are welcome sir.

Edit : Comment removed it can create confusion

Edit : Comment removed it can create confusion

Thank you

Edit : Comment removed it can create confusion

Edit : Comment removed it can create confusion

Thank you sir

Edit : Comment removed it can create confusion

Thank you

Edit : Comment removed it can create confusion

Edit : Comment removed it can create confusion

Nand kumar said:
Hey Guys,
After color OS 12 (and android 12) upgrade on OPPO reno6 5G device, users were facing issues like third part apps not working(Intune company portal work profile, Ritam news app etc),battery draing very rapidly,always on display not working and many more.
So, here I have come up with a method to flash stock ROM or downgrade color OS 12 and switch back to Color OS 11.3 which have android 11. So without wasting time lets start
Note: Data will be erased in this method so please take backup of you data on phone.
I strongly recommend to take full firmware backup using method below before proceeding
Backup full firmware(ROM) of any MediaTek device using MTK client| Oppo reno6 5G | MT6877
Hello Guys, Many times we encounter a situation where we need to do some software update, flash custom ROM, install stock ROM etc, so it is advisable to take full firmware/ROM backup of your device. If required then you can flash this backup to...
forum.xda-developers.com
Step1: Pre-requisite -Installing required drivers and setup
Install MediaTek drivers, in windows 10 you need to disable driver signature enforcement.
Install paython, usbdk.
download extarct Mtk client tool.
go to folder where you extract mtk client
View attachment 5541629
open cmd here and run below command
cd mtkclient
pip3 install -r requirements.txt
Windows+10_MTK+VCOM+USB+Preloader+Drivers.zip | by karimovic44 for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Download Python
The official home of the Python Programming Language
www.python.org
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
Releases · daynix/UsbDk
Usb Drivers Development Kit for Windows. Contribute to daynix/UsbDk development by creating an account on GitHub.
github.com
Step2: Download and extract the stock firmware
View attachment 5541657
CPH2251_A.13_ColorOS11.3_Android11_Latest.rar
drive.google.com
Step3: Flash the firmware
on cmd type below command to flash the firmware
python mtk wl "stock ROM location full path"
it will wait for devices.. Power off the phone, wait 10 sec then press vol up + vol down together and then plug the usb cable.
Once device detected , it will display devices information and start flashing
View attachment 5541639
View attachment 5541641
View attachment 5541645
While flashing it will dump the preloader, this file is very important so, please keep this file safely. this file may require in future.
View attachment 5541661
Step4: Boot the phone
Once flashing completed, press vol up + power button together for 30 sec. Wait for device to boot.
so by this way we flashed stock firmware on oppo reno6 5G.
Tips: If due to some reason flashing did not completed successfully then please press vol up and power button together for 30-40 sec to boot the phone (exit the brom mode).
Disclaimer: I have tested this method on my phone, it's 100% working but I will not responsible if damage any damage happens to your device while doing this. So do it at your own risk.
Click to expand...
Click to collapse
Thank you sir, it's working.
I followed this method and now I have successfully downgraded my ColorOs 12 to ColorOs 11.3 on my oppo reno6 5g.

How To Guide Backup full firmware(ROM) of any MediaTek device using MTK client| Oppo reno6 5G | MT6877

Hello Guys,
Many times we encounter a situation where we need to do some software update, flash custom ROM, install stock ROM etc, so it is advisable to take full firmware/ROM backup of your device. If required then you can flash this backup to restore your device.
We will use MTK client Github tool for this backup process and using same tool we can flash the backup firmware.
This method has been tested on OPPO Reno6 5G which is powered by MediaTek MT6877 chip. Backup size was approx 12 GB. Using this method you can backup firmware of any other supported MediaTek chip in this tool. In this method I don't backup userdata because this tool backups entire partition size irrespective of actual data stored.
Step1: Pre-requisite -Installing required drivers and doing setup
Install MediaTek driver.
Install python(during installation of python please select "install for all user" from customization and tick add path to system variable).
install usbdk.
download extarct Mtk client tool.
go to folder where you extract mtk client
View attachment 5541629
open cmd here and run below command
cd mtkclient
pip3 install -r requirements.txt
Windows+10_MTK+VCOM+USB+Preloader+Drivers.zip | by karimovic44 for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Download Python
The official home of the Python Programming Language
www.python.org
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
Releases · daynix/UsbDk
Usb Drivers Development Kit for Windows. Contribute to daynix/UsbDk development by creating an account on GitHub.
github.com
Step2: Create a new folder/directory in your computer to store the backup files.
{
"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"
}
Step3: Run full firmware backup
In cmd run command below, please skip userdata partition only because of very huge size.
python mtk rl --skip userdata "<full path to store the backup files>"
Once all the partitions dumped it will show message "All dumped partitions success"
During backup process it will dump the device preloader, this file is very important so, please keep this file safely. this file may require in future.
Step3: Reboot the phone
Once backup is done, you can restart your phone by pressing vol up and power button together for 30 sec.
Step4: How to Restore (if required)
Backup process might have created approximately 58 files but we do not need to flash all those files.
We only need to flash below files, so create a new folder and copy all these 33 files from original backup to your newly created folder.
audio_dsp.bin
boot.bin
cam_vpu1.bin
cam_vpu2.bin
cam_vpu3.bin
cdt_engineering.bin
dpm_1.bin
dpm_2.bin
dtbo.bin
gpt_backup.bin
gpt_main.bin
gz1.bin
gz2.bin
lk.bin
lk2.bin
logo.bin
mcupm_1.bin
mcupm_2.bin
md1img.bin
oplusreserve2.bin
pi_img.bin
recovery.bin
scp1.bin
scp2.bin
spmfw.bin
sspm_1.bin
sspm_2.bin
super.bin
tee1.bin
tee2.bin
vbmeta.bin
vbmeta_system.bin
vbmeta_vendor.bin
open cmd and type below command
python mtk wl "<full path where 33 files are stored>"
Backup should be restored on same device from which it was taken else device may brick.
Thanks and Regards
Nand,

thanks a lot why only 33 files restored ?

Please please, i have a question. can i use that firmware on oppo reno4 z 5G, has a model CPH2065
if not where i can find one for my device?
please i have oppo reno4 z 5G and model number CPH2065

jason__ said:
Please please, i have a question. can i use that firmware on oppo reno4 z 5G, has a model CPH2065
if not where i can find one for my device?
please i have oppo reno4 z 5G and model number CPH2065
Click to expand...
Click to collapse
No. you can NOT use.

Nand kumar said:
No. you can NOT use.
Click to expand...
Click to collapse
please where can i find fireware for my model. i searched everywhere and i can't find it.

jason__ said:
please where can i find fireware for my model. i searched everywhere and i can't find it.
Click to expand...
Click to collapse
Try this. I think You need to buy unlock tool license to flash the firmware. Search unlock tool.net in google.
https://oppostockrom.com/oppo-reno-4-z-5g-cph2065

Nand kumar said:
Try this. I think You need to buy unlock tool license to flash the firmware. Search unlock tool.net in google.
https://oppostockrom.com/oppo-reno-4-z-5g-cph2065
Click to expand...
Click to collapse
is it country neutral? what does that PU stand for?
i appreciate your time so much for trying to help me out.

jason__ said:
is it country neutral? what does that PU stand for?
i appreciate your time so much for trying to help me out.
Click to expand...
Click to collapse
Firmware size is 8 gb so I think it support all countries. You will get drop down list to select country while flashing. Download and extract and see if it has ofp file

okay sir, i'll get back to you when it's downloaded.

Nand kumar said:
Firmware size is 8 gb so I think it support all countries. You will get drop down list to select country while flashing. Download and extract and see if it has ofp file
Click to expand...
Click to collapse
Sorry for being late sir.
Yeah it has that file. but i installed realme flash, and some drivers were available in the package. then when i try to fastboot my phone (down volume key + power key) i find that my phone is not accessible.
i download every possible driver that i could find online and nothing.
also, when i try to fastboot my phone, i enter recovery mode. are they the same?
Please help me.

jason__ said:
Sorry for being late sir.
Yeah it has that file. but i installed realme flash, and some drivers were available in the package. then when i try to fastboot my phone (down volume key + power key) i find that my phone is not accessible.
i download every possible driver that i could find online and nothing.
also, when i try to fastboot my phone, i enter recovery mode. are they the same?
Please help me.
Click to expand...
Click to collapse
i think you need to enter EDL mode aka download mode and not fastboot for that tool...

Nand kumar said:
Hello Guys,
Many times we encounter a situation where we need to do some software update, flash custom ROM, install stock ROM etc, so it is advisable to take full firmware/ROM backup of your device. If required then you can flash this backup to restore your device.
We will use MTK client Github tool for this backup process and using same tool we can flash the backup firmware.
This method has been tested on OPPO Reno6 5G which is powered by MediaTek MT6877 chip. Backup size was approx 12 GB. Using this method you can backup firmware of any other supported MediaTek chip in this tool. In this method I don't backup userdata because this tool backups entire partition size irrespective of actual data stored.
Step1: Pre-requisite -Installing required drivers and doing setup
Install MediaTek driver.
Install python(during installation of python please select "install for all user" from customization and tick add path to system variable).
install usbdk.
download extarct Mtk client tool.
go to folder where you extract mtk client
View attachment 5541629
open cmd here and run below command
cd mtkclient
pip3 install -r requirements.txt
Windows+10_MTK+VCOM+USB+Preloader+Drivers.zip | by karimovic44 for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Download Python
The official home of the Python Programming Language
www.python.org
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
Releases · daynix/UsbDk
Usb Drivers Development Kit for Windows. Contribute to daynix/UsbDk development by creating an account on GitHub.
github.com
Step2: Create a new folder/directory in your computer to store the backup files.
View attachment 5543511
Step3: Run full firmware backup
In cmd run command below, please skip userdata partition only because of very huge size.
python mtk rl --skip userdata "<full path to store the backup files>"
View attachment 5543497
View attachment 5543501
Once all the partitions dumped it will show message "All dumped partitions success"
During backup process it will dump the device preloader, this file is very important so, please keep this file safely. this file may require in future.
Step3: Reboot the phone
Once backup is done, you can restart your phone by pressing vol up and power button together for 30 sec.
Step4: How to Restore (if required)
Backup process might have created approximately 58 files but we do not need to flash all those files.
We only need to flash below files, so create a new folder and copy all these 33 files from original backup to your newly created folder.
audio_dsp.bin
boot.bin
cam_vpu1.bin
cam_vpu2.bin
cam_vpu3.bin
cdt_engineering.bin
dpm_1.bin
dpm_2.bin
dtbo.bin
gpt_backup.bin
gpt_main.bin
gz1.bin
gz2.bin
lk.bin
lk2.bin
logo.bin
mcupm_1.bin
mcupm_2.bin
md1img.bin
oplusreserve2.bin
pi_img.bin
recovery.bin
scp1.bin
scp2.bin
spmfw.bin
sspm_1.bin
sspm_2.bin
super.bin
tee1.bin
tee2.bin
vbmeta.bin
vbmeta_system.bin
vbmeta_vendor.bin
open cmd and type below command
python mtk wl "<full path where 33 files are stored>"
Backup should be restored on same device from which it was taken else device may brick.
Thanks and Regards
Nand,
Click to expand...
Click to collapse
Can I ask how much time will it take to backup without userdata

hi i want this backup

idk why but my hanshake keeps failing.
i installed drivers as mentioned,but no coms showing up on device manager.
i think that when we install all drivers it usually shows like mtk device in devmgr,but it doesnt.
also i cant go to preloader mode easily.when i switch off phone and connect usb,it automatically turns back on.
why does it keep failing please help.are there any other methods for backup.like using sp flashtool.
pls help someone.

mohdsha said:
View attachment 5695877
idk why but my hanshake keeps failing.
i installed drivers as mentioned,but no coms showing up on device manager.
View attachment 5695881
i think that when we install all drivers it usually shows like mtk device in devmgr,but it doesnt.
also i cant go to preloader mode easily.when i switch off phone and connect usb,it automatically turns back on.
why does it keep failing please help.are there any other methods for backup.like using sp flashtool.
pls help someone.
Click to expand...
Click to collapse
ihave the same issue, did you find any solution to going into preloading?

mamomia said:
ihave the same issue, did you find any solution to going into preloading?
Click to expand...
Click to collapse
no bro.. im still trying .. i use a 5a cable..maybe we need og cable to coonect.idk i will try some troubleshooting.if successfull ,i will let you know.

Nand kumar said:
python mtk wl "<full path where 33 files are stored>"
Backup should be restored on same device from which it was taken else device may brick.
Click to expand...
Click to collapse
can a backup of the 33 files be applied to a new device which is exactly the same model without bricking it? (ie. a rom transfer to create a clone onto second device)

Hello and thank you so much for your guide. I was able to get everything setup for the most part, but I am held up by two problems, I'm sure they are simple but I would appreciate any help if anyone knows the answer.
Problem number one, is the correct vcom driver, the preloader one as shown in this
Spoiler: PIC
Or should I be using another?
My other question is, what is the correct terminology for what we are trying to achieve by getting the phone to register in the MTK client? Like, are we trying to get it to "boot into preloader mode"?
Spoiler: PIC
I am unable to get my phone to register or show in device manager or with the mtk client, to get it to post into the "preloader" mode. Since I do not know how to adequately describe what I am trying to do, I am having a hard time even searching on google for more help. If anyone can give me any help in grammer google search or direct knowledge on this simple part i would appreciate it

The answer to the driver question is to install all of them not just one. This discussion on reddit has some comments which go into more discussion of the bootrom protection and other github repos to achieve this. So to answer my main question about the phone not being detected by the MTK client it seems there is one more step for myself and other folks in this condition.
Spoiler: show link
https://www.reddit.com/r/androidroot/comments/wj6zrv
This guide explains how the MTK devices load the preloader. It is only up for 1 second apparently
Spoiler: show link
https://www.reddit.com/r/Smartphoneforensics/comments/xwd562

thanks a lot!!!! i have installed easily mtk client on garuda linux, and works very well (used for restore stook boot and solve a bootloop that seems impossible to solve). this guide is what i'm searching from some week. a way to do a full backup of my phone, userdata included
my suggestion for install mtkclient and other android tool is switch to garuda linux. if you try linux, you will never use windows again. garuda app manager with chaotic-aur have all software that you need. try to believe