FREE Oppo and Clones Jailbreak

Looking forward to jb_overlay that does not require bdpprog
 
Last edited:
@liwil , if you got your system back online, could you check your ubi partition with this command :

/sbin/ubinfo /dev/ubi0 --all

and output here
 
Code:
[OPPO UDP-203/root]/sbin/ubinfo /dev/ubi0 --all
ubi0:
Volumes count:                           1
Logical eraseblock size:                 253952
Total amount of logical eraseblocks:     841 (213573632 bytes, 203.7 MiB)
Amount of available logical eraseblocks: 0 (0 bytes)
Maximum count of volumes                 128
Count of bad physical eraseblocks:       3
Count of reserved physical eraseblocks:  7
Current maximum erase counter value:     27
Minimum input/output unit size:          4096 bytes
Character device major/minor:            252:0
Present volumes:                         0

Volume ID:   0 (on ubi0)
Type:        dynamic
Alignment:   1
Size:        830 LEBs (210780160 bytes, 201.0 MiB)
State:       OK
Name:        ubi_boot
Character device major/minor: 252:1
 
Liwil, your oppo 203 is a survivor !
Glad to see that you finaly solved this serious issue !
Moremodey01 what is the normal count of bad physical eraseblocks and count of reserved physical eraseblocks ?
For example, for my ubi_boot : 2 and 8.
Should be 0 and 10 ?
 
Thanks again moremodey01
Looking forward to jb_overlay that does not require bdpprog

Add these two lines to /usr/local/bin/bdpprog, is it possible to complete jb_overlay without bdpprog?
View attachment 1545053
i dont understand your question, but you can add whatever you want in /mnt/ubi_boot/bdpprog.

when testing use /mnt/ubi_boot/bdpprog_debug + touch /mnt/ubi_boot/.debugstart + reboot -f to prevent brick and mtktool reflash.

then once you got what u want put it in /mnt/ubi_boot/bdpprog
 
i dont understand your question, but you can add whatever you want in /mnt/ubi_boot/bdpprog.

when testing use /mnt/ubi_boot/bdpprog_debug + touch /mnt/ubi_boot/.debugstart + reboot -f to prevent brick and mtktool reflash.

then once you got what u want put it in /mnt/ubi_boot/bdpprog
Because the JB RU wants to return to the oppo original RU, you cannot use /mnt/ubi_boot/bdpprog, otherwise it will get stuck during the update

#934 ujb.sh needs to be renamed /mnt/ubi_boot/bdpprog, after restarting, JB RU to original RU can be completed

#4,045 In this case, you must go back to the original firmware to solve it. All jailbreaks will have problems, including JB RU65, CN65, CN60...
 
Last edited:
Liwil, your oppo 203 is a survivor !
Glad to see that you finaly solved this serious issue !
Moremodey01 what is the normal count of bad physical eraseblocks and count of reserved physical eraseblocks ?
For example, for my ubi_boot : 2 and 8.
Should be 0 and 10 ?
my guess is that those are in factory default bad block, maybe a more hardcore specialist could jump in but i think it is totally normal .
Now if they increase too much , then there is an issue

For liwil case i m not even sure he really had bad blocks, just some bugs reading the list from the nand or the ubi partition that got resolved with all those mtk format commandsm, ..
 
Because the JB RU wants to return to the oppo original RU, you cannot use /mnt/ubi_boot/bdpprog, otherwise it will get stuck during the update

#934 ujb.sh needs to be renamed /mnt/ubi_boot/bdpprog, after restarting, JB RU to original RU can be completed

#4,045 In this case, you must go back to the original firmware to solve it. All jailbreaks will have problems, including JB RU65, CN65, CN60...
use the jb_overaly no ? just put #934 script before launching real bdpprog i guess..
 
my guess is that those are in factory default bad block, maybe a more hardcore specialist could jump in but i think it is totally normal .
Now if they increase too much , then there is an issue

For liwil case i m not even sure he really had bad blocks, just some bugs reading the list from the nand or the ubi partition that got resolved with all those mtk format commandsm, ..
Thanks a lot Moremodey01.
 
use the jb_overaly no ? just put #934 script before launching real bdpprog i guess..
I just don't want to add /mnt/ubi_boot/bdpprog, only use the functions of xx.sh and bdp.
Can you help me build a customized MAIN20XCN_RU_sp.bin
 
Last edited:
this will create several version of the firmware , it is already difficult to follow like this and too confusing for newcomers, just edit the jb_overlay it will be exactly the same. put this in the beginning

[ -f /mnt/ubi_boot/.bdp?.* ] && /mnt/ubi_boot/jb_overlay/bdp/bdpprog.1 || bdpprog.1

havbing one additional file is not an issue
 
I would like to ask a question.
Before to install FIRMWARE JAILBREAK when putting the pendrive with the files, the tray opened, I had to wait 50 seconds to give the ok to continue.
In this version 1.1 just put the pendrive with the files and wait for it to finish?
Thank you for your help
 
Reynaldo, When the BD-ROM trey opens, you wait about 50 seconds and when it closes, you should press "Re-Install" firmware update button if your using the manual USB Method. If you use the Automatic USB Method, you can just sit back and watch it automatically do it for you.
 
this will create several version of the firmware , it is already difficult to follow like this and too confusing for newcomers, just edit the jb_overlay it will be exactly the same. put this in the beginning
OK! Forget it! Wait for you to post jb_overlay v2
 
Reynaldo, When the BD-ROM trey opens, you wait about 50 seconds and when it closes, you should press "Re-Install" firmware update button if your using the manual USB Method. If you use the Automatic USB Method, you can just sit back and watch it automatically do it for you.
I want to install on an Oppo 205 USA, any bugs with the FIRMWARE JAILBREAK?
 
I tried to install it on Oppo 205 by the automatic system, but it didn't work.
When going to read the FW a message appears that is incompatible.
My device uses American original FW, I used the American version of Jailbreak to install.
 
Just to be sure, please check prerequisites below :
Your current version is 20X-65-0131.
You use USA zip file and put all files present in : "jb stk bdpprog" folder into a USB drive.
USB drive contains only 2 binary files in the root :
  • UDP20X.bin
  • MAIN20XCN_RU.bin

Seems that your USB drives contains also another official firmware (for example : UDP20XEU.bin) wrongly used by oppo instead of UDP20X.bin.
 
Just to be sure, please check prerequisites below :
Your current version is 20X-65-0131.
You use USA zip file and put all files present in : "jb stk bdpprog" folder into a USB drive.
USB drive contains only 2 binary files in the root :
  • UDP20X.bin
  • MAIN20XCN_RU.bin

Seems that your USB drives contains also another official firmware (for example : UDP20XEU.bin) wrongly used by oppo instead of UDP20X.bin.
This is the original FW and these are the files on the pendrive.
I think it's correct, but it didn't work.
FW1.jpg

FW.jpg
 
Reynaldo, you can ignore the .dstore file as its macos junk. Yes, the Autoscript changes the MAIN20XCN_RU.bin to MAIN20X.bin, but its all ready to go on the manual USB Method. I await for you to try it. Im confident it will work.
 
This script is from manual installation.
I think it needs these files to work.
Russian FW has a different name.

View attachment 1547347
#934
Automatic installation of jailbroken RU65, no need to manually.
US Need UDP20X.bin and MAIN20XCN_RU.bin, no need to rename MAIN20X.bin
Renamed MAIN20X.bin only for manual use
 
Last edited:
@Reynaldo : did you try with another pendrive ?
Another question : does the message appears very quickly or several seconds after the upgrade starts ?

If the message appear several seconds after starting the upgrade :
If you didn't already used manual usb method, you should try a find/replace in jb_stk_bdpprog.sh :
replace "sleep 10s" by "sleep 20s" (thus 25s will be available for Oppo to copy decrypted files of original FW into "/tmp/UPG" instead of 15s). It's safe, no problem to do it.
 
Last edited:
A question.
For an Oppo 203 or 205 with Russian original FW, if you want to install this Jailbreak, would it just be reinstallation?
 

The latest video from AVForums

Is Home Theater DEAD in 2024?
Subscribe to our YouTube channel
Back
Top Bottom