Announcement
Collapse
No announcement yet.
Announcement
Collapse
No announcement yet.
TWRP Recovery for Rockchip devices
Collapse
This is a sticky topic.
X
X
-
I haven't converted this to the omni-twrp 8.1 branch yet, but it should be pretty straightforward. Just note the fix for the offset to the bootloader message block.
-
I registered here specifically to say thanks for this work.
including the device tree is very helpful.
-
Originally posted by Magendanz View PostA new TWRP 3.1.1-0 build for Rockchip RK3328 is available for testing here: TWRP3_RK3328-3.1.1-0.img
On Rockchip devices, the offset to the bootloader message block in the /misc partition is 16384, rather than the usual zero or 2048. Unfortunately, support for BOARD_RECOVERY_BLDRMSG_OFFSET is broken pending a pull request that I've submitted.
Also, there are about a dozen or so command-line arguments (wipe_data, wipe_cache, update_package, etc.) defined in Recovery.cpp, but Rockchip felt the need to add a custom one of their own, "wipe_all". I had to make some tweaks to twrp.cpp after the get_args() call to support that. Remember, the Rockchip RK33 bootloader calls recovery directly with this "wipe_all" command-line argument as part of the factory setup after flashing new firmware, so this really needs to be right or you'll end up with a TWRP boot loop.
And for those brave souls who want to make changes or build for other Rockchip devices, I've provided the source on GitHub here:
Device configuration for building TWRP on Rockchip reference boards - GitHub - Magendanz/android_device_rockchip: Device configuration for building TWRP on Rockchip reference boards
If you spot any issues, please let me know via PM.
Leave a comment:
-
If done right, TWRP can install OTA updates from the OEM (including bootloader images) and do factory resets. Check the notes on my RK3328 project for TWRP, though, because Rockchip does some very unusual things with their bootloader message block offset and custom command-line argument (wipe_all).
-
Originally posted by ClarkKent View Post
Any options found out about a 3399 twrp apk?
You can already make a full backup of firmware on a PC. Don't think TWRP can flash bootloaders on Rockchip devices.
You can't root with TWRP as updating SuperSU will result in a bootloop on RK3399 and other Rockchip devices.
Overwriting the stock recovery means you won't be able to factory reset to solve problems in future.
You will also not be able to receive and install ota updates from manufacturers if they go through recovery which is 90% of the case.
Leave a comment:
-
Originally posted by Magendanz View PostA new TWRP 3.1.1-0 build for Rockchip RK3328 is available for testing here: TWRP3_RK3328-3.1.1-0.img
On Rockchip devices, the offset to the bootloader message block in the /misc partition is 16384, rather than the usual zero or 2048. Unfortunately, support for BOARD_RECOVERY_BLDRMSG_OFFSET is broken pending a pull request that I've submitted.
Also, there are about a dozen or so command-line arguments (wipe_data, wipe_cache, update_package, etc.) defined in Recovery.cpp, but Rockchip felt the need to add a custom one of their own, "wipe_all". I had to make some tweaks to twrp.cpp after the get_args() call to support that. Remember, the Rockchip RK33 bootloader calls recovery directly with this "wipe_all" command-line argument as part of the factory setup after flashing new firmware, so this really needs to be right or you'll end up with a TWRP boot loop.
And for those brave souls who want to make changes or build for other Rockchip devices, I've provided the source on GitHub here:
Device configuration for building TWRP on Rockchip reference boards - GitHub - Magendanz/android_device_rockchip: Device configuration for building TWRP on Rockchip reference boards
If you spot any issues, please let me know via PM.
Leave a comment:
-
Originally posted by Magendanz View PostA new TWRP 3.1.1-0 build for Rockchip RK3328 is available for testing here: TWRP3_RK3328-3.1.1-0.img
On Rockchip devices, the offset to the bootloader message block in the /misc partition is 16384, rather than the usual zero or 2048. Unfortunately, support for BOARD_RECOVERY_BLDRMSG_OFFSET is broken pending a pull request that I've submitted.
Also, there are about a dozen or so command-line arguments (wipe_data, wipe_cache, update_package, etc.) defined in Recovery.cpp, but Rockchip felt the need to add a custom one of their own, "wipe_all". I had to make some tweaks to twrp.cpp after the get_args() call to support that. Remember, the Rockchip RK33 bootloader calls recovery directly with this "wipe_all" command-line argument as part of the factory setup after flashing new firmware, so this really needs to be right or you'll end up with a TWRP boot loop.
And for those brave souls who want to make changes or build for other Rockchip devices, I've provided the source on GitHub here:
Device configuration for building TWRP on Rockchip reference boards - GitHub - Magendanz/android_device_rockchip: Device configuration for building TWRP on Rockchip reference boards
If you spot any issues, please let me know via PM.
Leave a comment:
-
Originally posted by ADILTON MARQUES View PostI successfully installed the TWRP Custom Recovery on my TVBOXMX9 PRO, rk3328. Follow this Video to install: https://goo.gl/WRaAGK and I used this image file, twrp.rk3328-3.1.1-0, https://goo.gl/nsbAuS. With this Official TWRP APP, https://goo.gl/S498Jq. Note My device is with Root. But the SuperSu and the Binary are outdated. Well if updating the box does not restart anymore. Enter LopInfinito. Thank you!
Leave a comment:
-
Hi, I have a max a5x with oreo 8.1
can I install the recovery mentioned in this post?
Leave a comment:
-
Originally posted by ADILTON MARQUES View PostI successfully installed the TWRP Custom Recovery on my TVBOXMX9 PRO, rk3328. Follow this Video to install: https://goo.gl/WRaAGK and I used this image file, twrp.rk3328-3.1.1-0, https://goo.gl/nsbAuS. With this Official TWRP APP, https://goo.gl/S498Jq. Note My device is with Root. But the SuperSu and the Binary are outdated. Well if updating the box does not restart anymore. Enter LopInfinito. Thank you!
Please help !
Box : Scishion AI ONE - RK3328
Leave a comment:
-
I used Flashify to flashrecovery img . I was running a rooted 7.1 img first. Loaded flashify and then flashed the twrp img and worked fine. I also use an app I like, REBOOT. Works great. I try not to use TWRP app.
Leave a comment:
What's Going On
Collapse
There are currently 2265 users online. 0 members and 2265 guests.
Most users ever online was 63,956 at 18:56 on 20 March 2025.
Leave a comment: