Database Users

[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
***********************************************

[APP] DualBootPatcher for Mediatek 64 bit devices

{
"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"
}
Hi and welcome to DualBootPatcher app thread for Mediatek 64 bit devices.
It's available for any MT67xx device under two conditions:
- You compile your own version with support for your handset
- You upload your build.prop and your scatter file. I will compile it for you when I get time. SORRY, BUT I HAVE STOPPED THAT
Disclaimer:
Code:
I take no responsibility for any damage to your device or yourself because you use this app.
Keep in mind that using this app, your device may:
- Gain ability to fly
- Give birth to a dragon
- Trigger a thermonuclear explosion!
- Get you fired from your job because alarm app didn't work
- Simply die!
Downloads:
Grab the latest apk here https://snapshots.noobdev.io
How to get your device supported ?
Method 1: Port it yourself
Before you start porting it, check these info first:
Open your scatter file and make sure that the info match the ones below:
Click to expand...
Click to collapse
(For MT6735 & MT6753)
system.img is for SYS21
cache.img is for SYS22
userdata.img is for SYS23
boot.img is for SYS8
recovery.img is for SYS9
(For MT6752 and maybe MT6732)
system.img is for SYS18
cache.img is for SYS19
userdata.img is for SYS20
boot.img is for SYS8
recovery.img is for SYS9
IF ANY OF THESE INFORMATION DO NOT MATCH THE ONES IN YOUR SCATTER FILE, THEN MOVE TO METHOD 2! ELSE, FOLLOW THE STEPS BELOW.
1) Download the App and install it
2) Unpack your TWRP using Carliv Image Kitchen or any other tool
3) Edit the default.prop file in your unpacked TWRP by changing the values of the following lines to n560a (if you have MT6735 or MT6753) , for brand, set it to JIAYU. If you have MT6752 set it to h560 and the brand is the same.
ro.product.model=
ro.product.brand=
ro.product.name=
ro.product.device=
4) Now repack your TWRP and flash it.
5) Boot to your current rom, edit build.prop file and change the same values you did change on step 3. After that, reboot your device and now you are good to go.
6) If you wish to patch a zip, choose n560a - Jiayu S3 Plus for MT6735 or MT6753 (the app should detect that automatically if you did everything right). If you have MT6752, choose h560 - Jiayu S3.
Method 2: Add support for your device yourself!
If you are unlucky and your partition table didn’t match any of the above ones, then you will have to add your device manually and compile the app yourself.
1) Download the source code at https://github.com/chenxiaolong/DualBootPatcher
2) Edit jiayu.cpp file in libmp/devices and add your device’s partitions numbers. For MT6735 & MT6753, base your edit to n560a and for MT6752 base it to h560.
3) Compile it with the new changes. Your device should be supported now.
I haven’t tested for MT6795, but you may check in xiaomi.cpp file to see if you can base your port off one of the device’s configuration in it.
Click to expand...
Click to collapse
Usage:
Refer to this XDA thread to use the app http://forum.xda-developers.com/hot-2/orig-development/app-dualboot-multiboot-infinix-hot-2-t3425807
IF YOU GET BLACK SCREEN OR PHONE VIBRATES FEW TIMES AND REBOOT TO RECOVERY WHEN YOU TRY TO BOOT A SECONDARY ROM, THEN REPLACE “forceencrypt” with “encryptable” ON THE USERDATA PARTITION OF YOUR FSTAB FILE.
Old guide is below if you still need it.
Currently supported devices:
- Tecno Camon C8 (h352)
- Quantom Go 4G (Q2)
- Allview Viper X (V2_Viper_X)
- GiONEE Elife S Plus (SPlus)
- ZTE Blade V6 (Blade_V6)
Downloads:
Current realease is here => DualBootPatcher_arm64.apk mega.co.nz (16 MB)
How to use it ?
Refer to this thread of mine for Infinix HOT 2 or this one for Android One 1st gen devices.
Want to compile it ?
I encourage you to do so!
Clone either the original repo here https://github.com/chenxiaolong/DualBootPatcher and add your device in supported list by editing one of the .cpp files in libmbp/devices
Or, clone my fork of the repo here https://github.com/Nonta72/DualBootPatcher and just edit the mtk64.cpp file in libmbp/devices dir.
Bugs:
- In-app flasher doesn't work
- If you flash an Android 6.0.x rom as secondary, the ROM will show that the sdcard is corrupted even thought it really is not. So you have to install 6.0 ROMs has primary. If you only have 6.0 roms, well, I am sorry but you have to wait till I figure out what triggers the fake sd card corruption.
Credits and thanks:
All thanks go to @chenxiaolong for his awesome and incredible app!

[TOOL][OXYGEN] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)

This is the Xiaomi Mi Max 2's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Install APKs
Uninstall APKs
Take a Screenshot
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
​

mauronofrio said:
This is the Xiaomi Mi Max 2's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Install APKs
Uninstall APKs
Take a Screenshot
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
​
Click to expand...
Click to collapse
sweet! very nice contribution to our little MM2 community, much appreciated! ill be sure to add this to the index and already subscribed, of course
Sent from my Xiaomi Mi Max 2 (Oxygen) using Tapatalk

We now have all in one tool, thank you!

[RECOVERY MOD] MultiROM for Yu Yureka Black

{
"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"
}
MultiROM is Like GRUB for Android. It can boot any Android ROM. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs.
Warning!
It is dangerous because none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always. I'm not responsible for anything.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable (not working yet)
Installation Guide
Flash TWRP Recovery with multirom support (link below).
Flash Multirom Zip in Multirom supported recovery.
Flash a New rom (If you have a Pie / Oreo rom already in internal, you can skip this step, Inject boot sector later).
The rom you already have is called primary rom which should be flashed outside the multirom interface in twrp.
You can change your primary rom to any Pie / Oreo rom.
Reboot recovery, hit the hamburger menu at the top right (This is multirom menu).
In add rom ---> Select storage ---> Rom Type-Android -->Zip File -->Choose Rom zip
Don't enable system partition mode
Your rom will be now listed as secondary rom, which can be seen under list roms.
Clicking the rom under list roms allows you to perform more actions (such as flashing Gapps for the particular rom).
In multirom menu , Goto settings --> change the settings as below (This is essential!)
You can choose Auto boot settings as you wish
Finally reboot to system.
Confirmed Not working - Noughat roms
The following were not tested-Treble roms (GSI and SGSI) , Stock roms
If new-source ROM is primary then secondary roms should also be new source and if primary rom is an old-source rom, secondary roms must be old source too to avoid crashing camera apps .
Roms flashed to OTG and SD card do not work
No Encryption support
Few Precautions :
1) You cannot set lockscreen security for secondary roms , if you do and are locked out of primary rom then flash this in recovery to remove lockscreen security https://drive.google.com/open?id=1tz2vq8vzVNs2s3NhcLp0UFAwJ2SyPgOL
2) MultiROM is stable .Primary rom is the safest, do your testing on secondaries. Frequent moving of roms to and fro and modding of kernel may lead to data loss on secondary.(not reported so far)
3) Keep all pie roms, oreo is reported to have problems with magisk.
Thanks to @pritish1998 for reporting the oreo-magisk bug.
Credits
Tassadar - Creator of multirom , @nkk71 for no-kexec workaround , @vasishath other contributors of source code.
TWRP Icons by - fichls
Teamwin.
Downloads:
Twrp-Multirom
Multirom-Zip
MultiROM Uninstaller : -
MultiROM-Uninstaller
License: GPL-3.0 , MIT . source code Commits pending

Booting from internal memory
Can it boot roms from internal memory as well ?

saqibalmalik said:
Can it boot roms from internal memory as well ?
Click to expand...
Click to collapse
Yes, you can boot multiple roms from internal memory.

[SHARED] Xiaomi Mi A2 Pixel Experience 11

This is pixel experience android 11 unofficial security march 5, 2021, so don't expect any updates
pixel experience 11
Google Drive - Virus scan warning
drive.google.com
I didn't find any bugs
I think it's enough for daily
great friend, the snapdragon stock camera, the camera stock on the gcam play store is safe, stable, but i use gcam mod by unryx05 it is stable,
Supports Razer Phone2 v.3.3 Dolby Atmos Magisk Module
How to install it (via twrp recovery) and what you should definitely pay attention to is the A / B slot
twrp recovery for mi a2 always stuck logo, maybe only some unofficial twrp versions are working
{
"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"
}
twrp
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
To flash this ROM, you already know that you have to unlock the bootloader. I think it has been unlocked
the way to install this custom ROM is not difficult so it doesn't bootlop this way
What is certain is there must be a PC. Xiaomi mi a2 must be in fastboot mode, connect to PC, open the folder (mininal adb and fastboot) in C program copy twrp to the folder open cmd type command?
fastboot devices and enter (fastboot boot twrp.img)
and enter wait a moment. If you have entered TWRP, don't unplug the cable, copy the TWRP img file. to Mi A2 touch install select img, then there will be a menu option swipe down select (recovery ramdisk)
when it's finished, touch reboot, select reboot recovery, if it says the OS is not installed, just ignore it and start again to twrp recovery
tap wipe format data type (yes) and select advanced wipe dalvik / cache / data / system.
touch the reboot menu select the slot from B to A. repeat again (wipe)
When finished, touch the reboot menu, select the slot again, move to B and reboot recovery, if it says the OS is not installed, just ignore it.
If you have entered recovery again, copy the custom rom pixel experience file to mi a2 from the PC. well, we just installed it and swipe the rom, wait for it to be done and reboot the system, don't panic, when it reboots, it will return to recovery, touch reboot, select slot A, then select system
as usual just ignore it if it says OS is not installed , okay just slide it . wait if successful only 1 minute less boot flashes

Please share where you got those builds from. I hope people do not want to install random files on their phones...
Did you build the ROM yourself from sources? Did you leak some private test build? ... Give some info, so people can verify the source.
The same with the TWRP img. Where is it from? What version is it? Who built it? Is there some special reason to not just use the most actual, official one (yes it gets stuck)?

I installed mi rom for xiaomi mi A2 ( jasmine_sprout ) not for random device, . All sources are on YouTube and Google. .

Double_A_92 said:
Please share where you got those builds from. I hope people do not want to install random files on their phones...
Did you build the ROM yourself from sources? Did you leak some private test build? ... Give some info, so people can verify the source.
The same with the TWRP img. Where is it from? What version is it? Who built it? Is there some special reason to not just use the most actual, official one (yes it gets stuck)?
Click to expand...
Click to collapse
I installed mi rom for xiaomi mi A2 ( jasmine_sprout ) not for random device, . All sources are on YouTube and Google. .

I installed a rom for xiaomi mi A2 ( jasmine_sprout ) not for random devices, . All sources are on YouTube and Google. .

Djank4 said:
All sources are on YouTube and Google.
Click to expand...
Click to collapse
That's like saying all sources are on the internet ._.
Basically the problem is, how does a person that install this know that there are no hidden viruses in those files?
Is there proof that a trusted developer created them? Did you create them? Did the person on the youtube video create them? ...?