[TWRP / CWM] [Recovery] Karbonn Titanium S5 - Karbonn Titanium S5 ROMs, Kernels, Recoveries, & O

# All Recoveries are Signed Zip Files,
# They can be installed through any recovery, including stock recovery (Factory installed recovery),
# No need of Fastboot mode.
TWRP 2.6.3.0
# Basic Themed
http://www.mediafire.com/download/g6vvs438p632om5/S5_TWRP_2.6.3.0.zip
TWRP 2.6.0.0
# Google Play Themed
http://www.mediafire.com/download/5n38cqra3x13l3n/S5_TWRP_2.6.0.0_Play.zip
# Basic Themed
http://www.mediafire.com/download/abzrn2bcux00lrj/S5_TWRP_2.6.0.0.zip
CWM 6.0.4.9
# Compiled from CM11 (4.4.4) Source Code (Works with any Rom)
http://www.mediafire.com/download/mj21m247j63t8c3/S5_CWM_6.0.4.9.zip
Note for Bloggers
# Don't Mirror the Link,
# Redirect users to this xda thread.

sahaj360 said:
All recoveries are "Free of Blur Display Bug",
All recoveries are Flashable Zips. You can flash them via Existing Recovery,
If you are flashing a recovery for the first time, then extract recovery.img from the respective zip file and flash it via FASTBOOT.
-------------------------------------------------------------------------------------------------------------------
# TWRP 2.6 (Touch Based) #
1-->Google Play Themed Interface
http://www.mediafire.com/download/6u3x0huuuyudjj7/TWRP_Play_S5.zip
2-->Basic Interface
http://www.mediafire.com/download/wt0fu46a131w4cx/TWRP_Basic_S5.zip
-------------------------------------------------------------------------------------------------------------------
# CWM 6 #
1-->New Interface (Touch does'nt work, use hardware buttons)
http://www.mediafire.com/download/ud9gn2u8vt2ltzz/CWM_New_S5.zip
2-->Basic Interface
http://www.mediafire.com/download/jwimmx7nvc01x7p/CWM_Basic_S5.zip
-------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
Good work mate

sahaj360 said:
All recoveries are "Free of Blur Display Bug",
All recoveries are Flashable Zips. You can flash them via Existing Recovery,
If you are flashing a recovery for the first time, then extract recovery.img from the respective zip file and flash it via FASTBOOT.
-------------------------------------------------------------------------------------------------------------------
# TWRP 2.6 (Touch Based) #
1-->Google Play Themed Interface
http://www.mediafire.com/download/6u3x0huuuyudjj7/TWRP_Play_S5.zip
2-->Basic Interface
http://www.mediafire.com/download/wt0fu46a131w4cx/TWRP_Basic_S5.zip
-------------------------------------------------------------------------------------------------------------------
# CWM 6 #
1-->New Interface (Touch does'nt work, use hardware buttons)
http://www.mediafire.com/download/ud9gn2u8vt2ltzz/CWM_New_S5.zip
2-->Basic Interface
http://www.mediafire.com/download/jwimmx7nvc01x7p/CWM_Basic_S5.zip
-------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
Bahut bhadiya sahaj saab....

sahaj360 said:
All recoveries are "Free of Blur Display Bug",
All recoveries are Flashable Zips. You can flash them via Existing Recovery,
If you are flashing a recovery for the first time, then extract recovery.img from the respective zip file and flash it via FASTBOOT.
-------------------------------------------------------------------------------------------------------------------
# TWRP 2.6 (Touch Based) #
1-->Google Play Themed Interface
http://www.mediafire.com/download/6u3x0huuuyudjj7/TWRP_Play_S5.zip
2-->Basic Interface
http://www.mediafire.com/download/wt0fu46a131w4cx/TWRP_Basic_S5.zip
-------------------------------------------------------------------------------------------------------------------
# CWM 6 #
1-->New Interface (Touch does'nt work, use hardware buttons)
http://www.mediafire.com/download/ud9gn2u8vt2ltzz/CWM_New_S5.zip
2-->Basic Interface
http://www.mediafire.com/download/jwimmx7nvc01x7p/CWM_Basic_S5.zip
-------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
Can someone please mirror this to Google Drive and share here so that Admin of this post can update the OP with the same?

Help!
I hope someone can point me in the right direction. I have the Blu Studio 5.0s II and I flashed the clockwordmod recovery and rebooted. When I did I no longer had service as it says "no sim in slot 1 or 2" so my sim is not being recognized by the device and the recovery image didn't seem to have flashed. I cannot reboot into CWM or even stock recovery. I attempted to flash the recovery again via fastboot and receive the error "partition recovery not support flash." Any help would be greatly appreciated.

sahaj360 said:
# All Recoveries are Flashable Zip Files,
# Install them via any Custom Recovery (if previously installed),
# If installing a Custom Recovery for the first time, extract recovery.img from the zip file and flash it via FASTBOOT.
TWRP 2.6 (Touch Based)
# Google Play Themed
http://www.mediafire.com/download/6u3x0huuuyudjj7/TWRP_Play_S5.zip
# Basic Themed
http://www.mediafire.com/download/wt0fu46a131w4cx/TWRP_Basic_S5.zip
CWM 6.0.4.9
# Compiled from CM11 (4.4.4) Source Code (Works with any Rom)
http://www.mediafire.com/download/cxdpygaosgrcw73/CWM_6.0.4.9_S5.zip
Note for Bloggers
# Don't Mirror the Link,
# Redirect users to this xda thread.
Click to expand...
Click to collapse
thanks sahaj for latest recovery

Hi,
After i flash CWM 6.0.4.9, my phone can't enter recovery. The phone will switch OFF after 'SAMSUNG' logo. This is my Samsung S+ phone.

Is it for Karbonn TitaniumS5 Plus
Guys I want recovery for flashing it via odin 3.09 to my Karbonn TitaniumS5 Plus

Karbonn titanium s5 plus recovery
BRO DOWNLOAD MTK Droid tools and install recovery

Related

[GALAXY S3 MINI TOOLKIT V3 Drivers, Backup, Root, CWM, TWRP, Flash, + MORE

IMPORTANT: THE S3 MINI MODULE SUPPORTS 4 DIFFERENT S3 MINI VARIANTS SO MAKE SURE YOU SELECT THE CORRECT MODEL FOR YOUR DEVICE IN THE MODEL SELECTION SCREEN OR INCORRECT BOOT IMAGES WILL BE DOWNLOADED WHICH COULD SOFT BRICK YOUR DEVICE.
SUPPORTED MODELS
GT-I8190 INTERNATIONAL GSM MODEL
GT-I8190N INTERNATIONAL GSM MODEL WITH NFC
GT-8190L LATIN/USA GSM MODEL
GT-8190T LTE MODEL
Click to expand...
Click to collapse
FUNCTIONS OF UNIFIED ANDROID TOOLKIT V1.3.4 [9TH JAN 2015]
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn't corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk's to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: As the exe files are not Digitally Signed with a Microsoft Certificate they 'may' get picked up as potentially harmful by Antivirus Programs and deleted on first run. If this happens restore the file and exclude it from future scans to use it. This seems to happen mostly on AVG Free and Norton which is why I switched to BitDefender which is much better.
Credits: Chainfire for SuperSU, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE YOUR DEVICE. NOTHING IS RESTRICTED.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR 'AUTO UPDATES' DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE 'QUICK PICKS' SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE "ANY BUILD" OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD (USEFUL IF YOUR BUILD IS NOT LISTED).
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
How to get into Recovery Mode
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
**FAQ**
Q. Help me I can't find my build in the Model Selection Screen
The Toolkit includes a selection of Insecure Boot Images to cover all the different builds available. As there are very many different builds it is impossible to include an image for every single build but some builds share the same Boot Image. If you have a build that isnt listed on the Model Selection Screen you can therefore use a similar build. The best way to go is up to the next available build as it should offer more compatibility with the build you are using but if that isn't available then try the next build below your one as it should still be almost identical as long as it is the same version (ie. 4.1.1).
The Model Selection Screen is there so that if a task in the ToolKit requires an insecure kernel [to perform adb root commands] and your phone doesnt already include one, a compatible boot image [with an insecure kernel included] can be flashed to provide adb root access.
If you have a Custom Rom flashed to your phone then it will most probably have an insecure kernel included so it doesn't really matter if your build is not listed on the Model Selection Screen and when asked [by certain functions] if you have an insecure kernel on your phone you can answer 'yes'. However if the function fails then your kernel may not be insecure in which case you can flash one from the ToolKit. If you need to do this make sure the right build [or closest available build] is set so you flash the right image for your phone.
----------------------------------------------------------------------------
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF like removing system apps.
----------------------------------------------------------------------------
Q. Why do I need to back up my IMEI/EFS and how do I do it?
There well protected section of your device that is virtually immune to any kind of flashing and manipulation (unless of course you know how to access it). This part of the device contains information such as IMEI (or MEID and ESN in the case of CDMA devices), programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, and a whole bunch of other things that, when not handled properly, can render a device completely useless. All of these are contained in the infamous \EFS folder. If anything messes with your EFS folder, unlike flashing a device (which could potentially lead to bricks as well) it could render your device completely useless as it will no longer be recognized by your carrier. If you are not planning on flashing anything to your device and want to stay on pure Stock then you may never have any problems but it is still advisable to backup this information just in case (better to be safe than sorry).
----------------------------------------------------------------------------
Q. Does flashing a custom image increase my flash counter?
Any image that is flashed via Odin that has been modified will increase the flash counter that can be viewed in the Download Mode on your device (if booted by holding the Volume Down, Home and Power buttons). You can reset the flash counter using an app by Chainfire called Triangles Away and can find instructions on how to use that in the Downloads section in the Toolkit.
----------------------------------------------------------------------------
Q. Will flashing Stock ROM via odin using the toolkit replace everything that was flashed before? recovery? etc?
Yes a Stock Image flashed via Odin will replace all your key partitions (boot, recovery, system) with the stock firmware. If you want to reset the phone back to an 'out of the box' state then you want to enter recovery and do a wipe first which will reformat your userdata partition.
----------------------------------------------------------------------------
Q. I flashed Custom Recovery but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on certain Stock Android Builds that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from Google Play such as ES File Explorer). Rename the files /system/recovery-from-boot.p and /system/etc/install-recovery.sh (requires root). Now when you flash Custom Recovery it will NOT be overwritten after a reboot. You can also do this via the Toolkit.
----------------------------------------------------------------------------
Q. My AntiVirus program says the Toolkit files may be harmful
The exe compiled files are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton and AVG Free) may pick it up as potentially harmful when it is not. They will pick up ANY file that doesn't contain a purchased Microsoft certificate in the same way. Just Restore the deleted file and exclude it from further scans and it will be fine. Or switch to a better AntiVirus program such as BitDefender.
----------------------------------------------------------------------------
Q. I flashed the Toolkit Boot Image, now my wifi + bluetooth won't work
The boot images are made from Stock with only needed changes made to the insecure boot images [modified adbd, default.prop and rc.local edited] and will work on all stock roms. If you flash them to a custom rom and the rom has been altered or uses a custom boot image then it will boot but certain modules may not load such as wifi or bluetooth. In this case you can use the boot image to root or perform adb root functions but will need to flash back the boot image for the custom rom to get other functions working again. This is not a fault of the Toolkit but a difference to stock in the custom rom.
----------------------------------------------------------------------------
Q. I am having trouble getting adb working with the drivers installed
Try switching your connection type from media (MTP) mode to camera mode (P2P). To do this open the notification area, click where it says connected as and change from MTP to PTP.
----------------------------------------------------------------------------
Q. I want to send my device back for warranty purposes
1. Follow the instructions to reset your flash counter with TriangleAway.
2. Download and flash a Stock Firmware image from the download section.
3. Boot into Stock Recovery and perform a wipe/factory reset
.
Your internal storage will be formatted and data and cache wiped. Your device should now be back to an out-of-the-box FULLY STOCK state with the flash counter [shown if you boot to download mode manually] reset and ready to send back.
----------------------------------------------------------------------------
Q. When connecting the phone I get 'USB Device not Recognized' and no serial number shows in the ToolKit
I actually had this problem recently and what fixed it for me was to make sure that the drivers have been installed, then shut my phone down plug the usb cable in and restart it. The phone booted up and the device was recognized and drivers installed correctly. May not work for everyone but worth trying.
***reserved if needed***
thanks developer!!!!!!!!!!!!!!!!!!!
will report feedback after tested
Great work MSKIP the safest way and easy way to root and stock your phone thank you testing in progress.
Can i have the link to the toolkit for testing? Thanks in advance
Great work.:good:
SinisterGrey said:
Can i have the link to the toolkit for testing? Thanks in advance
Great work.:good:
Click to expand...
Click to collapse
you should pm mskip he will link you a download
Re: [GALAXY S3 MINI TOOLKIT V1.0.0] Drivers, Backup, Root, CWM, TWRP, Flash, + MORE
Thanks we are waiting them...
sent from the super siii mini GT-I8190 using xda premium app.
SinisterGrey said:
Can i have the link to the toolkit for testing? Thanks in advance
Great work.:good:
Click to expand...
Click to collapse
Sending you a link to the test file.
Mark.
mskip said:
INTRODUCING THE SAMSUNG GALAXY S3 MINI TOOLKIT
IMPORTANT: THIS TOOLKIT SUPPORTS 3 DIFFERENT S3 MINI VARIANTS SO MAKE SURE YOU SELECT THE CORRECT MODEL FOR YOUR DEVICE IN THE MODEL SELECTION SCREEN OR INCORRECT BOOT IMAGES WILL BE DOWNLOADED WHICH COULD SOFT BRICK YOUR DEVICE.
SUPPORTED MODELS
GT-I8190 INTERNATIONAL GSM MODEL
GT-I8190N INTERNATIONAL GSM MODEL WITH NFC
GT-8190L LATIN/USA GSM MODEL
Now uploading files and waiting for testers
Mark.
Click to expand...
Click to collapse
would like to test, thanks
Click to expand...
Click to collapse
funiewski said:
mskip said:
INTRODUCING THE SAMSUNG GALAXY S3 MINI TOOLKIT
IMPORTANT: THIS TOOLKIT SUPPORTS 3 DIFFERENT S3 MINI VARIANTS SO MAKE SURE YOU SELECT THE CORRECT MODEL FOR YOUR DEVICE IN THE MODEL SELECTION SCREEN OR INCORRECT BOOT IMAGES WILL BE DOWNLOADED WHICH COULD SOFT BRICK YOUR DEVICE.
would like to test, thanks
Click to expand...
Click to collapse
Pm me as soon as you are available to test and I will send you the installer link. It needs to be tested on an unmodified stock rom and I would advise making a nand backup before doing any testing so you can easily get back to your previous state when you are done.
If anyone else can test as soon as possible please pm me for a link as testing is going a bit slow. I would have like to have it tested on all 3 variants and released by now but as long as I know its working on 1 variant I can release it.
Mark.
Click to expand...
Click to collapse
Works great thanks. :good: Let me know if u need a logcat (default)
Can't wait to get the Pro version and donate to the toolkit. :fingers-crossed:
Great work
Re: [GALAXY S3 MINI TOOLKIT V1.0.0] Drivers, Backup, Root, CWM, TWRP, Flash, + MORE
Would like link also please.
Sent from my GT-I8190 using xda premium
Count me in as a tester, I can spare a few minutes here and there.
Re: [GALAXY S3 MINI TOOLKIT V1.0.0] Drivers, Backup, Root, CWM, TWRP, Flash, + MORE
Me too
Sent from my GT-I8190 using xda premium
i have a variant i8910L the latin american version..stock movistar peru rom unmodify so u can send me the link to test it and see what happen
Can I ask you for the link, too, please? Thank you.
SAMSUNG GALAXY S3 MINI TOOLKIT RELEASED TO PUBLIC VERSION
The Toolkit has now been tested to my satisfaction and has been released for download in the 1st post. Please remember that this is the first release and I dont own the device so there may be some textual errors or minor bugs that need ironing out. If you find any problems please post in this thread and they will be fixed as soon as possible. Do not pm me as any pm's that should be posted in a public thread will be ignored.
Enjoy
Mark.
Re: [GALAXY S3 MINI TOOLKIT V1.0] Drivers, Backup, Root, CWM, TWRP, Flash, + MORE
Superb!!!!
Great work Mark. I'm glad to see new developers joining us.
I see an option to re-flash stock recovery but now implemented yet. If nobody provided a stock recovery for you to implement, here you go then.

[Q] Recovery mode and clockword mode

Hi,
I am new to android world. Can you please tell me the difference between recovery mode and clockword mode ??? I want to install a zip file to my galaxy ace (s5830, not rooted, Gingerbread ) but it is not working. The website says clockwork mode is required for this . Will i be able to use the recovery mode in samsung phones for this ??
I tried to update using recovery mode on ace but it doesnt seem to work.
How can i put this to work??
Please help!
Thanks in advance
rohith.gm said:
Hi,
I am new to android world. Can you please tell me the difference between recovery mode and clockword mode ??? I want to install a zip file to my galaxy ace (s5830, not rooted, Gingerbread ) but it is not working. The website says clockwork mode is required for this . Will i be able to use the recovery mode in samsung phones for this ??
I tried to update using recovery mode on ace but it doesnt seem to work.
How can i put this to work??
Please help!
Thanks in advance
Click to expand...
Click to collapse
root your device and then flash cwm ..
and this is s5830i section..so ask youe question in s5830 section
ѕєηт ƒяσм αcє-ι-cσσρєяνє
rohith.gm said:
Hi,
I am new to android world. Can you please tell me the difference between recovery mode and clockword mode ??? I want to install a zip file to my galaxy ace (s5830, not rooted, Gingerbread ) but it is not working. The website says clockwork mode is required for this . Will i be able to use the recovery mode in samsung phones for this ??
I tried to update using recovery mode on ace but it doesnt seem to work.
How can i put this to work??
Please help!
Thanks in advance
Click to expand...
Click to collapse
Recovery mode is usually the place which will allow you to flash roms, kernels, scripts, etc. By default, you have Samsung's stock recovery mode. Clockwork Mode or CWM is a custom recovery mode that offer much more option than the stock recovery mode. Now assuming that you have Samsung Galaxy Ace S5830 and not Samsung Galaxy Ace S5830i, here is the link for rooting and installing CWM 5 on Samsung Galaxy Ace,
How To Root and Unroot Samsung Galaxy Ace?
Download Root.zip from that link and place it in your sd card. Now switch off the device and boot in to recovery mode (Home+ Power button). Now select "Apply Update from SD Card" and then choose Root.zip. Done. Now you have successfully rooted the device. Follow the same steps for installing CWM too.
CWM 5.0.2.6 fix for Samsung Galaxy Ace S5830
Hope I Helped
amolgosavi said:
root your device and then flash cwm ..
and this is s5830i section..so ask youe question in s5830 section
ѕєηт ƒяσм αcє-ι-cσσρєяνє
Click to expand...
Click to collapse
Sorry I didnt check whether the forum was for s5830 or s5830i Thanks for the reply by the way
While installing CWM by terminal emulator it shows
"E:invalid command argument
E:Cant Open /tmp/recovery.log"
Code i used was
Su
Recovery -update_package=/sdcard/recovery.img
I hav done by teminal coz my volume buttons are not working so.for up-down navigation volume buttons are needed bt its not working so i tried with code bt its showing me error. And while flashing in rom install it shows "Error:cant locate recovery partion"
Please help for install zip of cwm without volume button.
Please giv me solution
Please help me.
Device: Samsung galaxy ace S5830i
Sent from my GT-S5830i using XDA Free mobile app
GalaxyAce05 said:
While installing CWM by terminal emulator it shows
"E:invalid command argument
E:Cant Open /tmp/recovery.log"
Code i used was
Su
Recovery -update_package=/sdcard/recovery.img
I hav done by teminal coz my volume buttons are not working so.for up-down navigation volume buttons are needed bt its not working so i tried with code bt its showing me error. And while flashing in rom install it shows "Error:cant locate recovery partion"
Please help for install zip of cwm without volume button.
Please giv me solution
Please help me.
Device: Samsung galaxy ace S5830i
Sent from my GT-S5830i using XDA Free mobile app
Click to expand...
Click to collapse
We have several standard method for installing/using custom Recovery console such as flashing "recovery.tar.md5" over Odin 3.07 ( single entry PDA ) >> Obviously you can not access to Download mode , because of your Volume malfunctions . However we can use ADB commands to access stock recovery and Download mode , yet again totally useless , due to critical keys malfunctions >> Android debugging bridge must be enabled inside your developer settings of your device /proper drivers installed inside your PC / USB cable ready at hands / Android SDK tools installed inside your PC or use platform tools as an alternative >> adb reboot Download << >>>adb reboot recovery <<< for accessing both modes without using traditional hardware combo keys.
2. Terminal emulator method >> Rooted phone/busybox from play store installed /correct recovery.img must be present for instance inside root of your sd card /super user or su app must be updated to preferably 3.1.3 ; su binary inside of your super user app must be 3.1.1 ( flashing this file su-bin-3.1.1-arm-signed.zip would solve the outdated binary , yet again you have key malfunctions )
after su you may try >
flash_image recovery /sdcard/recovery.img
(and press enter)
Now, normally reboot to recovery and enjoy new recovery!
if not wait for #
now type reboot recovery
or
this line after su, depends on the sd card block inside your s5830i, fill xx >>
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p<xx>
Caution : S5830i/C/M/5839i known as cooperVE do require dedicated CWM recovery console . Unless you ported your CWM image from here and you have synced the source, updated it and setup the build environment for creating your "recovery.img" ( which i highly doubt that you are capable of such things ) . Sources for your device : 1 ; 2 ; 3
There are 2 types of CWM involved in this process : 1- Temporary zip file which does not come with buit-in kernel inside , so you have to flash it every time through stock e3
2. Comes with kernel for the permanent access to custom recovery upon executing recovery command .
Be advised older temp- CWM ( 5.0.2.6 AND 5.0.2.8) are best suited for stock firmware and custom Roms based on stock firmwares, because of native support for your RFS partitions .
CWM + 6 ported for cooperVE only supports ext2/3/4 and MTD , so do not flash it on stock or the type of rom I did mention
3, Droid manager method : rooted phone/adb enabled inside your device/Net Framework 4. installed /ADB drivers installed /
This is the GUI version and will perform many things such as fie manager capabilities/manage Nandroid backups from a custom recovery/supports both of the major recoveries ClockworkMod and TWRP/fastboot and many functions.
last word , after getting into your CWM presumably how the heck you want to move without your volume keys being active LOL GET IT FIXED .
Hope I did help you and for God sake don't use your wrong recovery.img through Terminal , You will **** it up royally indeed

[flashable zip] xposed framework + disable pie in system linker

I created a modfied zip of the Xposed Installer that also installs a patched system linker to disable pie requirement on the system so you can execute any compatible arm binary. I use it on my Boost Mobile J727P Perx with system version J727PVPU1AQF5. Flash with Flashfire. ENJOY!
What do you guys think? It takes a little bit to boot on reboot cause the dalvik-cache is rebuilt. So don't get afraid, it will boot normally thereafter.
I finished up an optimized kernel boot image for the phone too . Unzip OPTBOOTIMG.zip to the root of the sdcard or internal storage and flash the BOOT image J727P.img in flashify. FOR PERX VARIANT ONLY.
I made an odin flashable tar that installs the optimized kernel boot image and also works for the latest AQI3. Directly boot into recovery by holding volume up + power button + home button at the same time and do a factory data reset. Then boot into download mode by holding volume down + power button + home button and select the odin tar in the AP tab then start the install. Install the superuser.apk attached to attain root and I recommend using flashfire to flash the latest SR5 Supersu and NOPIEXPOSED zip if you prefer Xposed, or the Suhide zip from its respective thread if you rather use that.
ODIN TAR HERE: http://www101.zippyshare.com/v/e2Ewo6QJ/file.html
anthonykb said:
I created a modfied zip of the Xposed Installer that also installs a patched system linker to disable pie requirement on the system so you can execute any compatible arm binary. I use it on my Boost Mobile J727P Perx with system version J727PVPU1AQF5. Flash with Flashfire. ENJOY!
What do you guys think? It takes a little bit to boot on reboot cause the dalvik-cache is rebuilt. So don't get afraid, it will boot normally thereafter.
I finished up an optimized kernel boot image for the phone too . Unzip OPTBOOTIMG.zip to the root of the sdcard or internal storage and flash the BOOT image J727P.img in flashify. FOR PERX VARIANT ONLY.
Click to expand...
Click to collapse
Will these two file work on the latest firmware J727PVPU2AQI3 an do that work together ? An why flash one with flashfire an the other with flashify ?
peter couniaz said:
Will these two file work on the latest firmware J727PVPU2AQI3 an do that work together ? An why flash one with flashfire an the other with flashify ?
Click to expand...
Click to collapse
I would hold off until there's a patched AQI3 boot image available but some people have said the older boot image we already have works on J727PVPU2AQI3. It's your choice in the end.
anthonykb said:
I would hold off until there's a patched AQI3 boot image available but some people have said the older boot image we already have works on J727PVPU2AQI3. It's your choice in the end.
Click to expand...
Click to collapse
True but the old boot img work but only with root may be the same with your boot img but I don't know !
Waiting for oreo
peter couniaz said:
True but the old boot img work but only with root may be the same with your boot img but I don't know !
Click to expand...
Click to collapse
I'll look into it. I'm thinking about going back to stock so I can get the Oreo update when it's released.
anthonykb said:
I'll look into it. I'm thinking about going back to stock so I can get the Oreo update when it's released.
Click to expand...
Click to collapse
Yes can get this update now if you want just go back stock QF5 firmware an if you the firmware package it on the forum ! It in guides news an Discussion under (galaxy j727p stock update) !
PS once instilled you can not backdate !!!
Virgin mobile galaxJ727P
anthonykb said:
I'll look into it. I'm thinking about going back to stock so I can get the Oreo update when it's released.
Click to expand...
Click to collapse
Yes your optimised boot img works on J727PVPU2AQI3 firmware just fine haven't tried your exposed yet but I think that should work fine too !
Update got you optimised boot img to work finally with binary update for supers 2.82 works great thanks for you good work !
Virgin mobile J727P
anthonykb said:
I created a modfied zip of the Xposed Installer that also installs a patched system linker to disable pie requirement on the system so you can execute any compatible arm binary. I use it on my Boost Mobile J727P Perx with system version J727PVPU1AQF5. Flash with Flashfire. ENJOY!
What do you guys think? It takes a little bit to boot on reboot cause the dalvik-cache is rebuilt. So don't get afraid, it will boot normally thereafter.
I finished up an optimized kernel boot image for the phone too . Unzip OPTBOOTIMG.zip to the root of the sdcard or internal storage and flash the BOOT image J727P.img in flashify. FOR PERX VARIANT ONLY.
I made an odin flashable tar that installs the optimized kernel boot image and also works for the latest AQI3. Directly boot into recovery by holding volume up + power button + home button at the same time and do a factory data reset. Then boot into download mode by holding volume down + power button + home button and select the odin tar in the AP tab then start the install. Install the superuser.apk attached to attain root and I recommend using flashfire to flash the latest SR5 Supersu and NOPIEXPOSED zip if you prefer Xposed, or the Suhide zip from its respective thread if you rather use that.
ODIN TAR HERE: http://www101.zippyshare.com/v/e2Ewo6QJ/file.html
Click to expand...
Click to collapse
Sorry to say your optimised boot img is as unstable as everything else for this phone heck we don't even have a working twrp recovery yet ! ?
Virgin mobile J727P
anthonykb said:
I created a modfied zip of the Xposed Installer that also installs a patched system linker to disable pie requirement on the system so you can execute any compatible arm binary. I use it on my Boost Mobile J727P Perx with system version J727PVPU1AQF5. Flash with Flashfire. ENJOY!
What do you guys think? It takes a little bit to boot on reboot cause the dalvik-cache is rebuilt. So don't get afraid, it will boot normally thereafter.
I finished up an optimized kernel boot image for the phone too . Unzip OPTBOOTIMG.zip to the root of the sdcard or internal storage and flash the BOOT image J727P.img in flashify. FOR PERX VARIANT ONLY.
I made an odin flashable tar that installs the optimized kernel boot image and also works for the latest AQI3. Directly boot into recovery by holding volume up + power button + home button at the same time and do a factory data reset. Then boot into download mode by holding volume down + power button + home button and select the odin tar in the AP tab then start the install. Install the superuser.apk attached to attain root and I recommend using flashfire to flash the latest SR5 Supersu and NOPIEXPOSED zip if you prefer Xposed, or the Suhide zip from its respective thread if you rather use that.
ODIN TAR HERE: http://www101.zippyshare.com/v/e2Ewo6QJ/file.html
Click to expand...
Click to collapse
Yes it turns out that your optimised boot img is quit quick !! Thanks again !!

Development [RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project

Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Redmi note 10 Global/India (sunny/mojito)
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
Send me a beer: Crypto(Preferred) | PayPal
Tree: https://github.com/TeamWin/android_device_xiaomi_mojito
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/xiaomi/xiaomiredminote10.html
Unofficial android 12 builds:
https://www.pling.com/p/1836625/
mirror: https://store.kde.org/p/1836625/
OMG.. thanks sir for helping us about that recovery..
Can someone clarify what "repacking" means in this context? Does this mean the recovery cannot be updated through flashing? When a more stable recovery becomes available, will I have to install it using fastboot?
new build with repacking support is up, installation instructions are in the OP
Nebrassy said:
new build with repacking support is up, installation instructions are in the OP
Click to expand...
Click to collapse
Can we flash Xiaomi.eu ROM using new build?
bravonova said:
Can we flash Xiaomi.eu ROM using new build?
Click to expand...
Click to collapse
If they provide recovery zips, yes
Nebrassy said:
If they provide recovery zips, yes
Click to expand...
Click to collapse
Need to inform Xiaomi.eu developers @ingbrzy Pls have a note of this.
"Advanced" does not have a choice "Install Recovery Ramdisk".
I have recovery PixelExperience.
Twrp - I'm triggering like boot (TWRP-3.5.1-mojito-Nebrassy-2.img).
Recovery Ramdisk but doesn't exist.
StaryMuz said:
"Advanced" does not have a choice "Install Recovery Ramdisk".
I have recovery PixelExperience.
Twrp - I'm triggering like boot (TWRP-3.5.1-mojito-Nebrassy-2.img).
Recovery Ramdisk but doesn't exist.
Click to expand...
Click to collapse
It does, but you can also use
Install > install image > select the image and flash it to recovery ramdisk
Thank you, i expected the button. My mistake.
no mirror available at the time writing this
Does backup and restore work? and what are the select for backup?
.
it will be great, give flashing rom instruction using this TWRP. thanks.
Thanks for your work on this.
If I want to do a standard TWRP backup, would I select data, boot and super? There's no partition called system.
Is installing TWRP to ramdisk due to this model having A and B partitions? Why do some phones have this setup and others don't?
For all those who fail to boot up a rom through TWRP....
Plz re-install TWRP into the ramdisk immediately after rom flash... it'll save your day...
I join the question: Does backup and restore work?
Can I only flash TWRP without flashing any other ROM?
I don't want to root or use a cutom ROM at this moment.
Just want to backup and restore with TWRP.
No one?
nierewa said:
I join the question: Does backup and restore work?
Can I only flash TWRP without flashing any other ROM?
I don't want to root or use a cutom ROM at this moment.
Just want to backup and restore with TWRP
Click to expand...
Click to collapse
It does work. But you need to use either sdcard to store the backup, or other storage like PC or external drive. Because switching roms will cause data format.
Ok. Thanks a lot.
I have a sdcard in the phone so I use it for storing the backup.
So I do this:
Installation:
1. fastboot boot twrp.img
2. copy that same twrp image to the device
3. go to Advanced > Install Recovery Ramdisk
4. select the image you copied
and then I can boot the Redmi without the need to flash a custom ROM?

Development [RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project

Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Mi 11i/Mi 11X Pro/Redmi K40 Pro
USB OTG will not work
Decrypting Android 12 will only work if you remove pin/password
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
thanks to : @erfanoabdi @Cozzmy13
Send me a beer: Crypto (Preferred) | PayPal
Trees:
https://github.com/TeamWin/android_device_xiaomi_haydn
https://github.com/TeamWin/android_device_xiaomi_sm8350-common
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/xiaomi/xiaomiredmik40pro.html
Thanks for sharing
Good job,but semms the Touchscreen doesn't work.
don't touch fish said:
Good job,but semms the Touchscreen doesn't work.
Click to expand...
Click to collapse
It does, wait a few seconds after boot
Nebrassy said:
It does, wait a few seconds after boot
Click to expand...
Click to collapse
I waited about five minute,and nothing happend.When I touch the screen,nothing happend or Sometimes twrp responds to the wrong touch position(for example:I touch the Cancel,It opend Language sittings).I can only use adb shell to use this recovery.
thanks,will it support flash miui rom.zip and support android 12 。。
Thank you ………………Testing now
Touch doesnt work for me either
im on xiaomi eu rom
Exodt said:
Touch doesnt work for me either
im on xiaomi eu rom
Click to expand...
Click to collapse
Pull log and send it
adb pull /tmp/recovery.log
Before flashing i removed my fingerprint and device lock Flashed successfully after 2nd step i installed twrp image via twrp recovery installed in phone in Advance - recovery ram disk -Twrp image - flash and after that i created a boot image and dtbo backup also flashed magisk zip btw my device was rooted previously with boot image method, in xiaomi eu 12.5.7.0. Touch takes time then it works … First internal storage was not showing so i go to mount and mount system and then it shows.
Maxx9 said:
Before flashing i removed my fingerprint and device lock Flashed successfully after 2nd step i installed twrp image via twrp recovery installed in phone in Advance - recovery ram disk -Twrp image - flash and after that i created a boot image and dtbo backup also flashed magisk zip btw my device was rooted previously with boot image method, in xiaomi eu 12.5.7.0. Touch takes time then it works … First internal storage was not showing so i go to mount and mount system and then it shows.
Click to expand...
Click to collapse
Can you check if fastboot booting the image has working touch?
Nebrassy said:
Can you check if fastboot booting the image has working touch?
Click to expand...
Click to collapse
Thats how i installed
Installation:
Removed Screen lock And Fingerprint
1.fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3.Go to advance system ram disk select twrp image and flash(if internal storage not showing then go to mount and mount storage)
4.after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Yes…it works for me …… when i run first command it booted but my storage wasn’t showing so i reboot to recovery and device reboted to stock recovery then i again put my device in fastboot and performed first command and it booted to twrp and touch takes 20 seconds for me to work ..
Nebrassy said:
Pull log and send it
adb pull /tmp/recovery.log
Click to expand...
Click to collapse
"adb: error: failed to stat remote object '/tmp/recovery.log': No such file or directory"
Tried it in booted twrp as well but adb doesn't work there.
Maxx9 said:
Thats how i installed
Installation:
Removed Screen lock And Fingerprint
1.fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3.Go to advance system ram disk select twrp image and flash(if internal storage not showing then go to mount and mount storage)
4.after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Yes…it works for me …… when i run first command it booted but my storage wasn’t showing so i reboot to recovery and device reboted to stock recovery then i again put my device in fastboot and performed first command and it booted to twrp and touch takes 20 seconds for me to work ..
Click to expand...
Click to collapse
It worked.
Flash Current TWRP did the trick.
I had to do a reboot.
Hold the volume up and power to go back to TWRP.
After that I could see the internal storage.
And flash Magisk.
*Do not unplug the cable. Unplugging was causing the touch to stop work on my MI11i EU 12.5.7
Thanks Maxx9!
I didn't unplugged the USB and removed the fingerprint + key as well.
But still didn't worked.
on xiaomi eu 12.5.8
Touche said:
It worked.
Flash Current TWRP did the trick.
I had to do a reboot.
Hold the volume up and power to go back to TWRP.
After that I could see the internal storage.
And flash Magisk.
*Do not unplug the cable. Unplugging was causing the touch to stop work on my MI11i EU 12.5.7
Thanks Maxx9!
Click to expand...
Click to collapse
Your welcome
Doesn't work on Indian ROM 12.5.5.0
Official Pixel Experience A12 Custom Rom For Xiaomi Redmi K40 Pro / Pro+ / Mi 11X Pro / Mi 11i is Available On Pixel Experience Official Website. ​​
on my device twrp still freeze touch screen
same problem

Categories

Resources