New build TWRP for only Realme Q support flash ozip

Status
Not open for further replies.

29y6145

Senior Member
Jun 7, 2013
459
258
83
Ha Noi
Hello . twrp only for realme Q stable
Link download : <Mod edit>
Link vbmeta support root , rom mod : <Mod edit>
Changelog
Modify the optimization project:
* Delete redundant languages, keep English, add Chinese language, default Chinese.

* Modify the default configuration, for example, the default time zone is East Eight Zone, default screen brightness, default vibration, default 24 hours, default return button on the right, default Chinese and so on.

* Modify the default configuration file path to reduce the possibility of conflicts with other people's compiled versions.

* Adjust and optimize the Chinese text and description, and re-edit all the items one by one to make it more accurate, understandable and humanized. Also added display mtp enable off display, file operation result display, operation page title display, permission description when modifying permissions, etc. UI text display.

* Modify the unlocking interface and adjust the height of the sliding unlocking bar, which can effectively prevent misoperation (the original unlocking bar and the operating unlocking bar are of the same height. When the unlocking is completed, the sliding may be repeated, and the corresponding action is directly operated).

* Open more partition backup and restore, such as modern baseband partition, bootloader, persist, cust and other partitions, easy to backup the underlying files before brushing, can restore the underlying files after brushing.

* Add .bin and .mbn format image files, so you don't need a zip brush package, you can write the underlying file. The original version only supports the brushing of .img format image files. (Be sure to pay attention to the right partition!!!!)

* Solve the problem of interface jam when using the simulation operation (the simulation operation is mainly for testing the theme, and no actual operation).

* Add the manual installation root function in Advanced Options > root system. Add a display root system option on this basis for manual operation.

* Added the ability to unenforce encryption, in advanced options > Unforce Encryption. You can remove the official system to force encryption and cancel the check.

* Change the built-in root mode and add magisk as the default root mode.

* Fixed button and button operations for some interfaces.

* The adb/usb debug mode is enabled by default, which is convenient for operating the phone through the computer command line in rec mode.

* MTP is enabled by default. In the rec state, you can also connect your phone to your computer to facilitate file copying.

* Modify the logo interface, modify the main interface page header, and add the display phone model and team name, author name.

* Fix some logical relationships and modify some interface displays.

* Added clear root function

* Added clear power-on password function

* Added ability to clear battery information

* Increase signature boot function

* Restore official rec function, need official boot and system system to operate successfully

* Increase the option of restarting after the automatic upgrade is completed. In the twrp setting, the default is automatic restart. If you uncheck the box, you can either not restart, and it is convenient to perform some operations after the automatic upgrade to prevent twrp from being overwritten.

* Increased avb2.0 verification function

important:

1. This rec supports data partition automatic decryption, encrypted data can be used normally under rec without formatting.

Please do not arbitrarily brush into the recue of unknown origin, it is likely that the data data can not be decrypted, and the data is completely lost.

The official default is to lock the password to encrypt the data. To enter twrp, you need to enter the lock screen password.

2. This rec supports the official original full-size ozip card brush package.

3. You must unlock the bootloader to brush the third-party rec. Please unlock the BL.

4. Built-in root system / remove root function, through the root system, can not only remove dm check, but also enable the system to obtain root privileges.

5. Built-in remove dm checksum and cancel the forced encryption function. Through certain operations, you can remove the official data forced encryption (the person who knows how to operate naturally).

6. Prevent the functions covered by the official rec (any one can be): root system, signature boot, remove dm check, cancel forced encryption, etc.

7. After the card is officially packaged, it is recommended to turn off the avb2.0 check, otherwise it may cause the boot prompt system damage due to root! ! !

8. If the boot prompt system is damaged due to root, etc., you can use the fastboot line to brush boot.img or brush the verification vbmeta to restore normal! ! !
 
Last edited by a moderator:

greenys'

Senior Member
Dec 15, 2014
816
300
93
23
Sümeg/Csepel
Sounds good. Will I be able to flash lineage os, opengapps pico and latest magisk with this recovery? I don't want anything else complex.

---------- Post added at 06:13 ---------- Previous post was at 05:59 ----------

Says failed to mount /system_root (invalid agument) error: 7 while trying to flash anything from it.
 

greenys'

Senior Member
Dec 15, 2014
816
300
93
23
Sümeg/Csepel
Contacted developer of this Chinese twrp and even he himself said that we shouldn't try to flash custom rom, magisk.zip or gapps package with it for it can't really flash anything else but stock rom and inbuilt magisk 20.0 that is embedded in twrp itself. So aside from rooting color os or installing stock rom in case of hard brick this twrp pretty much useless for custom rom development, testing, flashing or migrating.
 

555frost555

Member
Jun 17, 2011
23
0
0
Contacted developer of this Chinese twrp and even he himself said that we shouldn't try to flash custom rom, magisk.zip or gapps package with it for it can't really flash anything else but stock rom and inbuilt magisk 20.0 that is embedded in twrp itself. So aside from rooting color os or installing stock rom in case of hard brick this twrp pretty much useless for custom rom development, testing, flashing or migrating.
So, is problem so difficult to overcome that developers can't build proper twrp?
 

greenys'

Senior Member
Dec 15, 2014
816
300
93
23
Sümeg/Csepel
So, is problem so difficult to overcome that developers can't build proper twrp?
No. The developers are just lazy and most of time they're not in the mood for it for they mostly own RM5P instead of RMQ. However, @thesprintster compiled a theoretically working twrp for our RMQ devices. We're waiting for him to release so we could test it. On the other hand seemingly even roms need a few lines of change so they'll work on Realme Q. It's a huge pain in the ass but it seems RM5P roms won't work on RMQ even with proper recovery these roms need to be changed, recompiled ?*♂ So yeah. This sucks.
 
  • Like
Reactions: saifulnewton

555frost555

Member
Jun 17, 2011
23
0
0
No. The developers are just lazy and most of time they're not in the mood for it for they mostly own RM5P instead of RMQ. However, @thesprintster compiled a theoretically working twrp for our RMQ devices. We're waiting for him to release so we could test it. On the other hand seemingly even roms need a few lines of change so they'll work on Realme Q. It's a huge pain in the ass but it seems RM5P roms won't work on RMQ even with proper recovery these roms need to be changed, recompiled ?*♂ So yeah. This sucks.
God, damn it!
Not for nothing that I bought RM5P :D
"...even roms need a few lines of change..." - it means that there are differences between RM5P and RMQ. What are they like?
 

greenys'

Senior Member
Dec 15, 2014
816
300
93
23
Sümeg/Csepel
God, damn it!
Not for nothing that I bought RM5P :D
"...even roms need a few lines of change..." - it means that there are differences between RM5P and RMQ. What are they like?
Dunno. I've never successfully compiled a working
... thing in the past 10 years even though I followed step by step tutorials so I gave up on compiling Android stuff. All I can do is to bug devs to do the work instead of me but I can do that relentlessly thus it bears fruit more or less often. Ask thesprintster about it. I'm bugging him to make that flashable lineage os soon and after that I'm done for good.
 
Status
Not open for further replies.