Database Users

Rockchip TV Sticks - RK3xxx Firmware Tools

Here is RK3xxx_firmware_tools, works better than wendal tools.
It can depackage/repackage Rockchip update.img, system.img, boot.img & recovery.img
'h**p://***.multiupload.nl/M5CKMYFBSW'
Instructions to use
Split ROM file
1. Firmware Image Tools - Select Img
Select your ROM.img file eg. a rom made by lewy20041
Select Extract - It will extract the rom into: boot.img, kernel.img, recovery.img & system.img
Now you can replace the kernel.img(to get wifi working for a rom that is not for your device) or recovery.img.
Extracting System.img or Boot.img
2. Go to the System or Boot frame on the program and select 'Extract'.
The contents of the System.img in step 1 is now extracted to the 'temp' folder and you can edit the files.
- You can now edit build.prop file to tweak the rom or change default settings like the default language of the rom.
- You can also change the boot animation of the device by going to system/media/bootanimation.zip
- You can also add additional wifi adaptor files for your device by going to system/lib/modules and adding eg. 8188eu.ko wifi module. Remember to depmod -a in a terminal to apply changes.
When you are satisfied with your changes click 'Build' to put the files together again as an *.img file.
The files are stored as eg system_new.img in the programs main directory. Rename this file/files to eg system.img without the 'new' and copy it to the temp folder to replace the old file.
You can then click Build in the Firmware Image Tools frame at the top to make a complete *.img file again to flash to your device.
If you use Finless Bob Roms, click on 'Single tools' at the bottom to only modify one file at a time eg the system.img file.
The same usage can be applied as above as for a lewy20041 or stock rom.
This tool will help a lot of people that don't have custom roms for their devices to create their own one or use a different devices's rom that is almost identical to theirs and only replace the kernel to get wifi/bluetooth working.
This tool can also flash roms to your device.
Previously you needed linux to repackage a system.img file and couldn't depackage a boot.img or recovery.img easily.
Thanks to user SergioPoverony for putting this app together on 4pda forum.
Hope people find this useful.

Great, thanks. I'll give it a try.

sounds like this should be useful. i bought a minix x7 mini by accident. non mini roms run fine with the exception of wifi and bt

burnitdown said:
sounds like this should be useful. i bought a minix x7 mini by accident. non mini roms run fine with the exception of wifi and bt
Click to expand...
Click to collapse
http://www.freaktab.com/showthread.php?8825-NEO-X7-MINI-Neomode-Custom-Rom-Version-1 Give it a try, i think it's the first custom rom for the X7 Mini

PlutoDelic said:
http://www.freaktab.com/showthread.php?8825-NEO-X7-MINI-Neomode-Custom-Rom-Version-1 Give it a try, i think it's the first custom rom for the X7 Mini
Click to expand...
Click to collapse
tried it already, it's buggy. the quickshot rom for the mini seems to run alright so far

Thanks for posting this here! Exactly what I was looking for.

Thank you very much for this useful tool.
I use RK3xxx_firmware_tools 4.2.22.0.
Any firmware I try to Extract (your step 1 [Split ROM]) bring that same error:
{
"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"
}
Could you tell what goes wrong? I tried this on EQUANCY's CS968 Exclusive MODDED ROM EQS-v2.0M 1080p and with CS968 Android 4.4 based ROMs from freaktab's Tech1.

It will work on Allwinner softwares? ...

Raddub said:
It will work on Allwinner softwares? ...
Click to expand...
Click to collapse
No, it's for Rockchip devices.

Monster M7 HefferRom
Hey Guys. A buddy asked me to fix his M7 so i cooked up this little "rom" for it. This is the latest firmware from monster that gives you full nand storage for apps and whatnot. None of that seperate partition BS.
I went ahead and debloated this img of most of the preinstalled chinaware apps. There are a few remaining that can be disabled in settings>apps such as facebook, movie studio, skype, and mwidget. I didn't have enough time to find them all. Root is not included.
It has solid explorer, open camera(I left the stock cam as well), and nova launcher. Rename the file to update.img and place on external sd card. It will flash from internal but you'll only have about 1 GB total storage, so don't do that.
It definately seems a little snappier than bone stock.
Uploaded to my Drive, Enjoy.
https://drive.google.com/file/d/0B0KjDbYxIBLwcy16WUhqdnM5cDQ/view?usp=drivesdk

thank you for your help
thank you for your help

[RECOVERY] TWRP 2.8.x.x for Walton Primo S2

Team Win Recovery Project 2.x or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"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"
}
VIEW LATEST CHANGELOG HERE: Official Changelog Site
Fixes for Primo S2:
- Take Nandroid on your Internal or External SD Card
- Flash Zip From Both of your SD Card
XDA:DevDB Information
Walton Primo S2 Development, Tool/Utility for all devices (see above for details)
Contributors
OdSazib, tuxboy, Rohan Taneja, Syed Md Moinuddin
Source Code: https://github.com/TeamWin/Team-Win-Recovery-Project/
Version Information
Status: Stable
Current Stable Version: 2.8.5.0
Stable Release Date: 2015-02-21
Beta Release Date: 2014-04-19
Created 2015-02-04
Last Updated 2015-02-21

Instructions & old files
Old Recoveries:
★PrimoS2-TWRP-2.8.4.0.7z - 10.47 MB
★New Bugless Recovery With SELinux Enabled
★Based on Stock Kernel-Bugless, No SELinux Support
★Based on CM11 Kernel-Buggy, SELinux Support
Flashing Instructions:
You Can use Flashifyapp from Playsrore to flash this withing your device if it's rooted
How to use Flashify?
-Download app by clicking the big word 'Flashify' from above
-Download Recovery File from avobe link.
-Extract files with 7z or ES File Explorer
-Copy twrp-recovery.img/recovery.img to root of your phone storage
-Open Flashify and grant root acces for it
-Click Flash recovery>chose file from sd card
-Select twrp-recovery.img/recovery.img and flash
-Reboot into recovery, Done
→CM Kernel based recovery is fully stable when you are on 4.4.4 based rom, u can use it while on stock rom but delete batterystat.bin before booting to stock rom, that will resolve issue before boot. Cz different kernel write different stat file.
→I suggest to download stock kernel based as you are on stock kernel, Cz cm kernel write different batterystat.bin which generates problem with battery calibratio. Though it you will happg to use CM recovery after getting stable CM
OR, follow flashing scripts writen by @tuxboy
WINDOWS
-Make sure you have the drivers installed.
-Download and extract the zip file linked above.
-Connect your phone to you PC via USB cable, make sure USB --Debugging is switched on.
-Double click on the "flash-windows" (located inside the extracted folder) file.
Done!
Mac OS X
-Make sure you have the drivers installed.
-Download and extract the zip file linked above.
-Connect your phone to you PC via USB cable, make sure USB --Debugging is switched on.
-Open your Terminal app, drag and drop the "flash-mac.sh" file (located inside the extracted folder) on to your terminal.
Done!
LINUX
-Make sure you have the drivers installed.
-Download and extract the zip file linked above.
-Connect your phone to you PC via USB cable, make sure USB --Debugging is switched on.
-Open your Terminal, drag and drop the "flash-linux.sh" file (located inside the extracted folder) on to your terminal.
Done!
ATTENTION:
After First boot into recovery please select your storage either Internal Disk or External Disk, Don't Select Internal Storage. In default you should find it Internal Storage which you r suggested changing to Internal/External Disk

Amazing!
Good going bro! You will get cm stable soon

Rohan Taneja said:
Good going bro! You will get cm stable soon
Click to expand...
Click to collapse
Hoping soo Bro
Actually I have less resources and time to work

Good work! Thank you very much!!

Needed badly. Thanks to the devs

Great job guys
:good: Great job Sazib vai & everyone.
***********************************************
Current Device: Walton Primo S2
SOC: Qualcomm Sanpdragon 400 MSM8228
Root Access: Yes
***********************************************

[GUIDE] How To Port CWM Recovery on Marvell Devices PXA988/PXA1088

How To Port CWM Recovery on Marvell Devices PXA988/PXA1088​
This Guide working is only tested on PXA1088 Devices, But Maybe Work on PXA988 and and others Marvell Powered Devices too.
The Guide Provided by Marcone Noise / @marcone093 if you copy give a proper credits.​
NOTE:
Code:
Do This At Your Own Risk!
Remember, Am not Responsible for Any bricked devices, Wars and explosions, or because you simply lost your girlfriend's nudes,
be aware that YOU are doing the procedure on your own, if you do not know what you are doing give up now, in case something goes wrong my hands are tied
Requirements:
Android Image Kitchen Tool. -You can download here
Your Stock or Base recovery.img - Which is functional on your device.
The Port recovery.img - CWM or any other recovery you want to port.
Notepad++
A brain and patience.
let's start?
- Extract Your Base/Recovery
- Extract the recovery you want to port - (on different folders obviously)
You will now have two folders: BASE And PORT Folders.
{
"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 split_img on both folders and copy & replace recovery.img-zImage from base to port.
Now go to ramdisk folder and then copy from BASE to PORT:
-ueventd.rc
-ueventd.goldfish.rc
Aand other files you don't have in the PORT / ramdisk folder
Compare The Fstab.PXAxxx
-if your port recovery don´t have like me, copy from base to port
-in your base recovery don´t have, just ignore or checks and set your mount points.
Now You Need To compare default.prop, Just replace these lines From the BASE to the PORT.
ro.product.model=
ro.product.brand=
ro.product.name=cm_ here maintain the cm_ and set with your device codename
ro.product.device=
ro.product.board=
ro.product.manufacturer=
ro.build.product=
ro.board.platform=
ro.cm.device=
And search more codename and replace with your codename on some lines of default.prop like this:
Now go to /randisk/etc folder then compare recovery.fstab, replace your mountpoints from BASE to PORT.
NOW REPACK PORT RECOVERY AND TEST IT
DONE
I successfully ported a CWM to the Galaxy S3 slim using this method
sorry for my bad English
HIT THE THANKS BUTTON IF I HELPED YOU

What about the "libs" folder and "sbin" ?
i need help to understand that, the stock img don't contains too many files on sbin and the port img contain's a lot of files onto sbin folder, my phone is not booting on recovery, kitkat based device

[SLOT A/B devices] Universal A/B-cloner

I DO NOT TAKE RESPONSIBILITY FOR YOUR DEVICE BREAKING
THIS /WILL/ COPY YOUR BOOTLOADER FROM ONE SLOT TO ANOTHER
IF YOU DO THAT WITH A BOOTLOADER THAT IS OLDER THAN THE SLOT YOURE OVERWRITING YOUR DEVICE MIGHT BRICK
Ok, thats over with
INFO:
This is just a simple script, in a simple ZIP, designed to clone all the devices ACTIVE slots in /dev/block/bootdevice/by-name to the INACTIVE ones
it does nothing more, nothing less.
For me, this solved some issues with lineage and custom roms on my device and keeps my mild ocd... well.. mild.
This will not touch any partition with the word logo in it (lowercase only for now, oops)
BASIC HOW-TO:
0) have basic knowledge of how android works, dont be stupid
1) flash rom
2) run AB-Cloner-test
3) If the test runs normal rename it to AB-Cloner.zip ( remove the word "test" from the zip name)
4) run AB-Cloner
5) ???
6) profit!
Tested devices:
Successful tests:
Motorola Z² Force
(report your success below)
Unsuccessful tests:
PLEASE report below, so no one else endangers their phones
Known Bugs/Issues:
currently the word test must be lowercase in the filename, if any letter is not lowercase in the word test IT WILL RUN THE ACTUAL COMMANDS. this will be fixed in RC2/Normal releases
You tell me ?
TODO:
add VOL key detection to cancel zip/ make choices
update detection: figure out which slot is newer, flash that one to older
aroma? probably not tho
You tell me?
C+ slots? if theres a device that needs it
Pictures:
{
"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"
}
Download:
RC1: here (GDrive)

Ae3NerdGod said:
I DO NOT TAKE RESPONSIBILITY FOR YOUR DEVICE BREAKING
THIS /WILL/ COPY YOUR BOOTLOADER FROM ONE SLOT TO ANOTHER
IF YOU DO THAT WITH A BOOTLOADER THAT IS OLDER THAN THE SLOT YOURE OVERWRITING YOUR DEVICE MIGHT BRICK
Ok, thats over with
This is just a simple script, in a simple ZIP, designed to clone all the devices ACTIVE slots in /dev/block/bootdevice/by-name to the INACTIVE ones
it does nothing more, nothing less
for me, this solved some issues with lineage and custom roms on my device
BASIC HOW-TO
0) have basic knowledge of how android works, dont be stupid
1) flash rom
2) run AB-Cloner-test
3) If the test runs normal Rname it to AB-Cloner ( remove the word test from the zip name)
4) run AB-Cloner
5) ???
6) profit!
Known Bugs/Issues:
- currently the word test must be lowercase in the filename, if any letter is not lowercase in the word test IT WILL RUN THE ACTUAL COMMANDS. this will be fixed in RC2/Normal releases
- You tell me ?
TODO:
- add VOL key detection to cancel zip/ make choices
- update detection: figure out which slot is newer, flash that one to older
- aroma? probably not tho
- You tell me?
- C+ slots? if theres a device that needs it
Download:
RC1: here (GDrive)
Click to expand...
Click to collapse
This is good work
([emoji3590]09-09-18[emoji3590])

PoochyX said:
This is good work
([emoji3590]09-09-18[emoji3590])
Click to expand...
Click to collapse
thank you!

FYI I just ran this on my G7 Power (Ocean) and it seemed to work just fine. I had a good Resurrection Remix install on Slot A (active) and some weird borked stuff on Slot B.
I loaded and ran the .zip via adb sideload, it copied everything over, and it all seems to work just fine now, and identical on both slots.
FYI when running it this way (adb sideload) the name included "-test" but there was no test. It just ran--luckily it seemed to work OK.

Oneplus 8 5G UW (IN2019) did not work

[Recovery or Magisk] Universal BootLogo Changer [ Exynos ] [ One LOGO for All Screen Resolutions ]

{
"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"
}
UNIVERSAL EXYNOS PARAM CHANGER
SUPPORT: TELEGRAM CHANNEL - TELEGRAM GROUP - SUPPORT ME
ABOUT THIS:​You can design a BootLogo for any Exynos device, the images adapt to the resolution of the device's screen (based on Dynamic Installer with ImageMagick Plugin)
Features:
The images are adapted to the resolution of the device on which they are installed, One BootLogo for All devices
You dont necessarily need to use .jpg, even if you use .png in the process its transformed to .jpg, the only important thing is the name of the images
Only apply images that exist on the device, you can add images from new devices without fear of being inserted into old devices
Installation:
The installation can be done by Magisk or some custom Recovery, if it is done by Magisk you will be able to uninstall the module and after 2 reboots you will return to your previous BootLogo
HOW DO I USE IT?​
Code:
1. Unzip the template
2. Inside the "param" folder add your designs with valid names ( U can se the example)
3. Zip again
4. Install by Recovery or Magisk (Recommended)
5. Share it with any Exynos device !
CREDITS TO:​
Me @BlassGO (Developer of Universal Exynos Param Changer and Dynamic Installer)
Universal Exynos Param Changer
ZeroTwo Example
Share your designs!​

..

Thanks a lot for creating this very helpful magisk module
Working superb on my A51 and also my Note 20 Ultra Exynos.
Here i share bootlogo for A51
I edited in photoshop for A51 added
as attached
https://imgur.com/KXCLOPy

kingwicked said:
Thanks a lot for creating this very helpful magisk module
Working superb on my A51 and also my Note 20 Ultra Exynos.Here i share bootlogo for A51
I edited in photoshop for A51
attached as zip file
https://imgur.com/KXCLOPy
Click to expand...
Click to collapse
Huh you are from tg, I feel happy that it worked correctly for you, regards

Some Bootsplash images made for Note 20 Ultra 5G.
@BlassGO :The white background images turns to black background is that normal.

Hello Can you help me with this this im using Samsung Galaxy A10 i was able to change the logo.jpg inside the parm file i tried to flash it with twrp and magisk but when booting up it doesn't change the logo same as usual but when you see it in /dev/block/by-name/param and /dev/block/mmcblk0p12 it already change i need help asap!.

Jeylo01_ said:
Hello Can you help me with this this im using Samsung Galaxy A10 i was able to change the logo.jpg inside the parm file i tried to flash it with twrp and magisk but when booting up it doesn't change the logo same as usual but when you see it in /dev/block/by-name/param and /dev/block/mmcblk0p12 it already change i need help asap!.
Click to expand...
Click to collapse
Does this patch works on s22 ultra snapdragon processors?

mrjoy said:
Does this patch works on s22 ultra snapdragon processors?
Click to expand...
Click to collapse
I was going to ask the same because someone linked it to this thread haha, but anyways I don't think so because thread says Exynos only...

Jeylo01_ said:
Hello Can you help me with this this im using Samsung Galaxy A10 i was able to change the logo.jpg inside the parm file i tried to flash it with twrp and magisk but when booting up it doesn't change the logo same as usual but when you see it in /dev/block/by-name/param and /dev/block/mmcblk0p12 it already change i need help asap!.
Click to expand...
Click to collapse
I also have the same problem in A20 and A30 did anyone now how to fix that ?

Hi,
The installation of the new boot image works well but, unfortunately, it is badly resized, much too small for the screen ; the original image is at the maximum size (.jpg 1440x2560).
Anyway, I did the installation through magisk and the possibility to go back to the old image by simply deactivating the module is really convenient.
Samsung Galaxy S7 (SM-G930F)