Related
INTRODUCING THE SAMSUNG GALAXY S3 UNIFIED TOOLKIT
SUPPORTED MODELS
INTERNATIONAL [GT-I9300] SUPPORT THREAD HERE
AUSTRALIAN MODEL GSM [GT-I9300T]
INTERNATIONAL [GT-I9305/GT-I9305N] SUPPORT THREAD HERE
AUSTRALIAN MODEL LTE [GT-I9305T]
C SPIRE MODEL LTE [SCH-L710]
AT&T US [SGH-I747] SUPPORT THREAD HERE
BELL, ROGERS, SASKTEL, TELUS [SGH-I747M] [SGH-I747M] USE AT&T SUPPORT THREAD
US CELLULAR MODEL LTE [SCH-R530] USE AT&T SUPPORT THREAD
METRO PCS MODEL LTE [SCH-R530M] USE AT&T SUPPORT THREAD
SPRINT US [SPH-L710] SUPPORT THREAD HERE
TMOBILE US [SGH-T999] SUPPORT THREAD HERE
MOBILICITY, VIDEOTRON, WIND [SGH-T999V] USE TMOBILE SUPPORT THREAD
VERIZON US [SCH-I535] SUPPORT THREAD HERE
CHINA ANYCALL CDMA MODEL [SCH-I939] USE GT-I9300 SUPPORT THREAD
Click to expand...
Click to collapse
The Unified Android Toolkit supports a multitude of Nexus and Samsung devices with more devices being added all the time. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
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.
**UPDATES AND UPDATE CHANGELOG**
This Updater file will update your Toolkit to the latest version and add the latest support the Toolkit offers. Download the below file, move the file to the Toolkit installation folder and run the file to update to the latest version.
THIS IS AN XDA EXCLUSIVE AND MUST NOT BE REDISTRIBUTED IN ANY FORM!!
IF YOU ARE PLEASED WITH HOW THE TOOLKIT WORKS DON'T BE TIGHT AND CONSIDER DONATING TO THE PRO VERSION TO SAY THANK YOU AND GET UPDATES PUSHED STRAIGHT TO YOUR TOOLKIT WITHOUT HAVING TO UPDATE MANUALLY. A LOT OF WORK GOES IN TO THE TOOLKITS AND IM ALWAYS TRYING TO MAKE THEM BETTER. THANK YOU.
**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). If you have a GT-I9300 GSM Model then you can do this from the Toolkit but if you have an LTE device then it isn't soo easy to do. If you have an LTE device you should go to *THIS* thread by lyriquidperfection and follow the information to save your IMEI/NV Data so that you are covered if anything should happen.
----------------------------------------------------------------------------
Q. Is there currently no way to root the Samsung Galaxy S3 without voiding the warranty?
All methods of rooting will void your warranty in some way as you will have superuser files on your phone that arent supposed to be there. There is a method of rooting your phone without increasing the flash counter which involves flashing a complete rom with root files already added but if anything happens and you need to send it back under warranty you will need to flash a 'proper' Stock Rom back before returning it or your warranty will be void. Flashing a custom kernel or recovery to root will increase the flash counter and also void any warranty. There is currently no method of resetting the flash counter on Snapdragon models but im pretty sure there will be some support for it soon. If you dont want to risk it or you aren't sure then you shouldnt really be flashing your phone and should just leave it alone. Its your choice .
----------------------------------------------------------------------------
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.
Changelogs from previous builds to the Unified version
ToolKit v6.0 (08th November 2012)
+Added Full Support for International LTE Model GT-I9305
+Updated root support for latest 4.1.1 builds
+Added new Builds to Model Selection Screen
+Added Hotfile links to Stock Firmware for both Models in Downloads Section
+Added choice of Superuser or SuperSU on all root procedures
+Added choice of Custom Recovery when rooting (I9300 only)
+Updated Samsung USB Drivers to v1.5.15.0 (latest version)
+Added Device Information Screen from Main Menu
+Fixed Odin Tar Creator crashing
+Disabled ICS mods being enabled on JB builds which could soft brick the device
+Added NEW ‘Quick Picks’ Donators Feature
+Re-wrote lots of procedures to incorporate the Quick Picks Feature
+Re-ordered some functions on the Main Menu
+Added solution if CWM Root boots into Stock Recovery after flash
+Fixed lots of parts to improve the Toolkit
ToolKit v5.0 (23rd August 2012)
+Added Root Support for new Jelly Bean Builds
+Added Model Selection Screen at startup for selecting different builds
+Added cwm unroot zip file for quick unroot without wiping and flashing stock firmware
+Added cwm root for Superuser or SuperSU
+Added new Stock and Insecure kernels
+Added new Stock Recovery images
+Added new Stock Firmware download method and new links to various Stock Images
+Wrote new Date/Time method to give support for non UK Regions in various functions
+Added teaser for upcoming Quick Pick function
+Added new options to Settings Screen
+Added ‘Help’ option on Model Selection Screen
+Added ‘Auto Update’ check in Settings Screen
+Checked entire code and made edits to parts
ModsSection v2.1 (23rd August 2012)
+Updated Date/Time stamp method
+Updated NAND Backup script
+Added Jelly Bean detection for mods that do not work on that build
ToolKit v4.0 (24th July 2012)
+Added Auto Update Feature (at startup)
+Added 1-Click tar file creator to flash via Odin (from upto 10 images placed in the INPUT folder)
+Added Donator Features Activation from within ToolKit
+Changed Extras Section for new Activation method
+Added CWM Touch 6.0.1.0 to ToolKit
+Added Reboot to Download + Start Odin in ‘Reboot Phone Options’ screen
+Edited backup scripts for easier operation
+Removed Sim Unlock Tool for further testing
+Various tweaks
ModsSection v2.0 (24th July 2012)
+Added NAND backup option when starting to safe guard against bad mods
+Fixed some code
ToolKit v3.0 (4th July 2012)
+Added CF-CWM Recovery (thanks to Chainfire) as option
+Added cache.img dump to backup options
+Fixed /efs backup/restore tool from previous version not working
+Added Galaxy S3 SIM Unlocker by Adam Lange
+Added Samsung Cache Ripper by Adam Lange
+Updated Odin Flash Tool to v3.07
+Added option to NAND backup to Internal or External Storage + keep/delete files on phone after completion
+Added Rename Recovery Restore files for future proofing
+Fixed CWM Rooting as it wasnt working (incorrect script)
+Lots of re-written code for better functionality
+A few minor bug fixes
+A few other things I forgot to write down
ToolKit v2.0 (22nd June 2012)
+Updated CWM Recovery to Touch v5.8.4.3
+Updated Samsung drivers to v1.5.5.0
+Added text on NAND Restore option to check free space (2GB) before starting
+Streamlined Odin flash process. Phone will now automatically reboot into Download Mode
+Added Download Mode to reboot options
+Added Download, extract, flash Stock Rom option. Everything you will ever need to know is in there
+Added Stock Boot Image option
+Added full information on Resetting flash counter
+Alot more minor stuff
ModsSection v1.0 (22nd June 2012)
+Added first version of Mods Section. 3 mods
available for now with more to be added
ToolKit v1.0 (10th June 2012)
+First version of SGS3 ToolKit released
thanks for the great app! coming form galaxy nexus (thanks god i sold it) and knowing it will work flawlessly waiting for dl link
great application
Download link posted in Post#1
Mark.
AWESOME !!
Amazing work ! Can't wait to see what the future holds for this app !!
@mskip good to see u here and congrats on becoming a MOD :0)
Coming from the Galaxy Nexus,and i used your toolkit software many many times and it worked like magic..and im sure this one will be the same
Sent from my GT-I9300 using Tapatalk 2
Hi Mark,
amazing work and very useful app,
thank you very much!
Absolutely Perfeeeeect tool
Amazing, wonderful. Damn job dude. no words at all. U all DEVS ROOOOCKS. AMAZING GUYS HERE.
sooo goood baby baby
Used your toolkit on my Gnex (so easy to use )
And now we can enjoy it on the S3 !! Thank you mskip, for your great job, and for sharring this wonderful tool !
thank you very much good business
Thank You from a fellow East Anglian S3'er
72931761ND9517718
PS: ROM Manager isnt great with Sammy devices - may want to update first post to recommend use of CWM Manager instead.
Cool look epic good work :thumbup::thumbup::thumbup::thumbup:
Sent from my GT-I9300 using xda premium
Very good work!!
I test now the backup options. I already made an efs-backup and try now to make a full backup of the internal sd-card. Till now everything work very well.
Thanks very much for the toolkit!!
subvertbeats said:
Thank You from a fellow East Anglian S3'er
72931761ND9517718
PS: ROM Manager isnt great with Sammy devices - may want to update first post to recommend use of CWM Manager instead.
Click to expand...
Click to collapse
Thank you very much
First post updated, I just took out the link to Rom Manager as I have never used CWM Manager and dont know if you can get to CWM directly from the app.
What part of East Anglia?
Mark.
hurray said:
Very good work!!
I test now the backup options. I already made an efs-backup and try now to make a full backup of the internal sd-card. Till now everything work very well.
Thanks very much for the toolkit!!
Click to expand...
Click to collapse
You're welcome
If you find any bugs or have any opinion on improvements please let me know as im working on the mods and extras section now for the next version.
Mark.
oned said:
Used your toolkit on my Gnex (so easy to use )
And now we can enjoy it on the S3 !! Thank you mskip, for your great job, and for sharring this wonderful tool !
Click to expand...
Click to collapse
Although the S3 is a bit harder to automate without fastboot flashing I hope the ToolKit can be every bit as good as for the GNex (maybe even a bit better)
There will certainly be alot more mods in the mods section
Mark.
This is only a Concept and need development.....asking For help
Code:
Xda is a great platform to share Knowledge and ideas about Mobile Processing & Communication System
or we Can called Mobile Phone
We Have Seen Different Types of recovery like Stock & Mainly CWM(& CWM Based Recovery)
One Such Highly Popular recovery is TWRP And CWM Touch Which give Touch Experience in Recovery
But What About Next...
We have seen AROMA Installer and innovative Ideas like Aroma Based File Manager and Terminal
but What Next....
A idea struck into my mind while surfing and i reached a page about Phone-block a month ago this is a
very innovative idea but i connected this idea with modular Recovery..it is not like that recovery is not
working Modular as it contain at least Some Modules but what About a new Concept
CWM/TWRP+Touch+Aroma+App = Xboot ....!
I Am Just asking about Xda Developers that it is possible to make a recovery which can be used as
a independent Functional Unit in Our Phone i come up With that idea after remembering Sony-Ericsson Walkman
Series Which Allow Phone to Boot In Music Playback Mode Only and it is possible to make some App inbuilt in Recovery
like a Music Player Or a Video Player,A file Manager (as We Seen In Aroma) Only Possible Problem
to Develop Such System is the Physical Size of Partition In Android System but here Aroma Installer Serve the Problem
by using Aroma based zip on sdcard which serve as recovery mini apps..you may ask why would to develop such recovery
while we can develop standalone aroma based app which serve the same function but these app functional does not provide integration,optimization and reliability.it is like some part of recovery is swap to sdcard space which can provide feature
(based on Aroma Based Zip Apps)
Code:
#0.Cwm based operations
1.File Manager
2.Terminal
3.Music/Video Player-If Possible
4.Browser/YouTube(With WiFi)-If Possible
5.Organizer-Calculator,Timer,Notes etc...
6.and Many more
while in aroma we trigger activation of the zip but this recovery scan for available app on sdcard and provide it on it's interface supporting
touch and save it's configuration on .log,.conf files and on touch execute apps activation as required while hiding underlying codes execution
the design of and GUI of interface is up to the developer but i imagine it as the layout used in TWRP
We can also Develop a application on play store which can install such recovery(Xboot) and ask the user to download Aroma Based apps as required on the sdcard and config the recovery automatically.you may ask this make the recovery to be modified on device which can be dangerous but again we are using aroma the recovery only read a .conf file which contain information about app location and other technical info.we can provide general structure of these app to be divided by screen resolution of phone and develop app based on it like lpdi,hdpi,xdpi
and other resolution to reduce the development time and can support multiple devices
This recovery may provide Benefits like
Code:
1. Enhanced Battery Performance (Music & Video Playback)
2.Advanced Debugging
3.& Off course CWM Based operation
4.and standalone boot-able environment with android
but taking this concept further by making this recovery to boot always on a selection screen
which ask the user to boot in recovery or Android and at last Thank for Xda Developer for understanding me
Hoping You Get My Point Please Comment About my Concept & also discuss about possibility about it...
Thank You!..
Code:
*** Disclaimer
I/XDA am/is not responsible for any kind of damage to your device,
or in case it explodes, your surroundings.
Please use it at your own risk!
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.
Phone look:
Tablet look:
Bugs :
1. Reboot->Recovery doesn't work as required. Reboots to system instead.
Please do report any, if found.
Click to expand...
Click to collapse
Download :
Recovery-TWRP_2.8.3.0u1-NK.zip
Installation :
A. With custom recovery already installed :
1. Download zip
2. Reboot to recovery
2. Install zip in recovery
3. Reboot to recovery
B. With stock recovery (Root required) :
1. Download zip & extract recovery.img
2. Move recovery.img to root of external storage
3. Open Terminal
4. (If using terminal on PC) Execute :
Code:
adb shell
5. Execute the following commands :
Code:
su
dd if=/sdcard/recovery.img of=/dev/recovery
exit
C. Through SP flash tools :
1. Install drivers for your phone using Micromax drivers.
2. Extract the Stock ROM folder and replace recovery.img with recovery.img from zip.
3. Extract and open the SP Flash Tools.
4. In SP Flash Tools, click on Scatter-Loading and the program will ask you the location of the scatter loading file for your device select mt6589 scatter file.txt of your phone.
5.Check only Recovery, Preloader and uncheck all others.
6. Switch off your phone (Remove the battery to make sure it is switched off).
7. In Flash Tool, go to Options and Click USB Mode so that it is enabled. Click options again and then go to DA Download All > Speed and finally select High Speed.
8. Click the Download option (present on the right of Firmware > Upgrade option) and the flash tool will start looking for your phone.
9. Connect your phone now. The Flash Tool will start the flashing process, the progress of which can be viewed from a yellow progress bar at the bottom of the flash tool.
Warning 1 - Don't interrupt this process as it can potentially brick your device.
Warning 2 - Make sure no power interruption takes place. (Use a laptop to ensure this).
10. After the process completes, a green ring will appear on your device signalling that the process was successful.
11. Disconnect your phone.
Sources :
Recovery : https://github.com/omnirom/android_bootable_recovery
Kernel : https://github.com/neomanu/NeoKernel-MT6589-A116
Device : https://github.com/neomanu/android_device_micromax_a116-twrp
Credits :
@suhas.holla (for original device tree)
NO PORT REQUESTS
NO QUOTING THE WHOLE OP
You will be reported!
XDA:DevDB Information
TWRP 2.8.3.0, Tool/Utility for the Micromax A116
Contributors
neomanu
Version Information
Status: Stable
Current Stable Version: 2.8.3.0u1
Stable Release Date: 2014-12-26
Created 2014-12-22
Last Updated 2014-12-29
Reserved
Changelog :
2.8.3.0u1 :
- Added F2FS tools. Can be used to format filesystems to F2FS.
- Removed SuperSU (to fit into partition)
2.8.3.0 :
- MTP will now tell the host PC that storage is removed instead of disabling MTP completely
- MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
- Update and improve fix permissions and make fixing contexts optional
- Update SuperSU in TWRP to 2.40 and update install process
- Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
- Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
- Fix kernel panic during MTP start on some devices
- Support unicode fonts on devices with True Type Font support
- Fix slider value not showing sometimes (vibration settings page)
- Toggle MTP off during adb sideload to set correct USB IDs
- Reduce library requirements for 5.0 L decrypt
2.8.2.0 :
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
Also note that you will need the latest adb binaries on your computer to sideload with this new version of TWRP.
2.8.1.0 :
- MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
- TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
- Temperature support - thanks to bigbiff
- Various other bugfixes and tweaks
2.8.0.1 :
- Fix a bug that caused weird graphics and touch issues
2.8.0.0 :
- Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
- Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
- Add support for color in the console and give error, warning, and highlight lines different colors
- Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
- Improve handling of /misc thanks to mdmower
- Improve setting of time on Qualcomm devices thanks to [NUT]
- Allow using images on slidervalue GUI objects thanks to Tassadar
- Allow using variables and addition and subtraction in variables for easier theming
- Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
- Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
- Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
2.7.1.0 :
- Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
- Various bugfixes to backup and restore
- Improvements to USB storage handling
- Added a class to search for files to make finding the correct brightness file automatic in most cases
- Various other bugfixes and tweaks
Reserved
Awsome work bro.. :thumbup::thumbup:
Thank you so much.. Downloading
good work bro!!:good::good:
thanks for compiling this !!
Can we use this to flash Android 5.0.1 by kashifmin ?? !!
and anyway to solve reboot --> recovery problem ! ?
Awsome work once again MAN!!!!! Really, very greatful to you.... Just one more request to you...... Can you just compile a new kernel for our device from this Source (a tweaked kernel) so that we can have it on cm11.... because the kernel used in cm for now is not tweaked and a bit poor performance... i would have done that work but busy with my exams... so if you can please .. or i would be back within few weeks....
Once AGAIN , NICE WORK!! Keep it UP!!
Regards
Andy
can I flash this recovery... ?? currently I'm using AOSB ROM...
Sent from my Canvas HD
vaas kr said:
can I flash this recovery... ?? currently I'm using AOSB ROM...
Sent from my Canvas HD
Click to expand...
Click to collapse
Sure... you can with mobileuncle tools... (AND RECOVERY(S) ARE MEANT FOR FLASHING )
Regards
Andy
neomanu said:
Code:
*** Disclaimer
I/XDA am/is not responsible for any kind of damage to your device,
or in case it explodes, your surroundings.
Please use it at your own risk!
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.
Phone look:
Tablet look:
Bugs :
Download :
Recovery-TWRP_2.8.3.0u1-NK.zip
Installation :
A. With custom recovery already installed :
1. Download zip
2. Reboot to recovery
2. Install zip in recovery
3. Reboot to recovery
B. With stock recovery (Root required) :
1. Download zip & extract recovery.img
2. Move recovery.img to root of external storage
3. Open Terminal
4. (If using terminal on PC) Execute :
Code:
adb shell
5. Execute the following commands :
Code:
su
dd if=/sdcard/recovery.img of=/dev/recovery
exit
C. Through SP flash tools :
1. Install drivers for your phone using Micromax drivers.
2. Extract the Stock ROM folder and replace recovery.img with recovery.img from zip.
3. Extract and open the SP Flash Tools.
4. In SP Flash Tools, click on Scatter-Loading and the program will ask you the location of the scatter loading file for your device select mt6589 scatter file.txt of your phone.
5.Check only Recovery, Preloader and uncheck all others.
6. Switch off your phone (Remove the battery to make sure it is switched off).
7. In Flash Tool, go to Options and Click USB Mode so that it is enabled. Click options again and then go to DA Download All > Speed and finally select High Speed.
8. Click the Download option (present on the right of Firmware > Upgrade option) and the flash tool will start looking for your phone.
9. Connect your phone now. The Flash Tool will start the flashing process, the progress of which can be viewed from a yellow progress bar at the bottom of the flash tool.
Warning 1 - Don't interrupt this process as it can potentially brick your device.
Warning 2 - Make sure no power interruption takes place. (Use a laptop to ensure this).
10. After the process completes, a green ring will appear on your device signalling that the process was successful.
11. Disconnect your phone.
Sources :
Recovery : https://github.com/omnirom/android_bootable_recovery
Kernel : https://github.com/neomanu/NeoKernel-MT6589-A116
Device : --to be updated--
Credits :
@suhas.holla (for original device tree)
XDA:DevDB Information
TWRP 2.8.3.0, Tool/Utility for the Micromax A116
Contributors
neomanu
Version Information
Status: Stable
Current Stable Version: 2.8.3.0u1
Stable Release Date: 2014-12-26
Created 2014-12-22
Last Updated 2014-12-26
Click to expand...
Click to collapse
I have flashed twrp recovery 2.7.00 already.. Do i need to flash it ..?
Sent from my Micromax A116
jam884 said:
I have flashed twrp recovery 2.7.00 already.. Do i need to flash it ..?
Sent from my Micromax A116
Click to expand...
Click to collapse
No, you don't.
And everyone, please refrain from quoting the whole OP, and specially no port requests.
Both will be reported immediately.
jam884 said:
I have flashed twrp recovery 2.7.00 already.. Do i need to flash it ..?....
Click to expand...
Click to collapse
neomanu said:
No, you don't. .....
Click to expand...
Click to collapse
you mean there's no tangible benefit of using v2.8.3.0u1 if one's already running v2.7.0.0?
m0han said:
you mean there's no tangible benefit of using v2.8.3.0u1 if one's already running v2.7.0.0?
Click to expand...
Click to collapse
I'm saying that if someone is going to ask such questions after such a lengthy changelog has been posted, they might as well not.
neomanu said:
I'm saying that if someone is going to ask such questions after such a lengthy changelog has been posted, they might as well not.
Click to expand...
Click to collapse
your twrp v2.8.3.0u1 seems to work ok :good:.backup got saved in /emmc/TWRP/BACKUPS/Canvas_HD. how about shortening that to A116?
on another note, i'd like to have the font you've used in your recovery, on twrp v2.8.2.0 for xolo q3000. can you help in any way? thanks.
m0han said:
on another note, i'd like to have the font you've used in your recovery, on twrp v2.8.2.0 for xolo q3000. can you help in any way? thanks.
Click to expand...
Click to collapse
The font used is the new default in TWRP, from v2.8.1.0.
Refer to this commit.
All you need to do is to unpack the ramdisk, add RobotoCondensed-Regular.ttf to /res/fonts/ and change the following in /res/ui.xml according to the required resolution.
Repack and you have the font.
neomanu said:
No, you don't.
And everyone, please refrain from quoting the whole OP, and specially no port requests.
Both will be reported immediately.
Click to expand...
Click to collapse
In my twrp 2.7.0.0 it shows wipe option with dalvik,cache,factory reset..in single swipe.. What should i do to separate them..
Sent from my Micromax A116
jam884 said:
....What should i do to separate them....
Click to expand...
Click to collapse
try clicking advanced wipe and choosing what you need....
m0han said:
try clicking advanced wipe and choosing what you need....
Click to expand...
Click to collapse
Thanx a lot friend...
Sent from my Micromax A116
@neomanu
Thanks for TWRP_2.8.3.0
I have one issue some time stuck when flash zip on TWRP_2.8.3.0u1-NK
When flash same zip in preview recovery (TWRP 2.8.0.0 hyperion70) it work fine
any news on an update to fix the boot to recovery option ??
This is my personal compiled Kernel for SM-P350.
There is so little resource for my P350,
I need a Kernel with permissive and cifs function for my daily use,
because i frequently read PDF on local network,
with CIFS mount enbled , i can open PDF directly without the need to download it to my device.
However, i search all the forums, no this kind of Kernel i can find.
That's the reason i decide to learn compiling kernel from zero and finally out this kernel.
You may use this Kernel on P350 stock MM or Fenix Rom MM.
I'm currently on Fenix MM,
I cannot guarantee it will work on you P350, so , make a nadroid backup with TWRP first !
Take your risk by yourself.
Kernel Feather:
-Full Permissive
-Cifs built-in
-NTFS enable
Requirement:
-P350 Stock Android MM or Fenix Rom MM
-Device Rooted with TWRP installed
How:
1: Make sure you have 3 files copy to you internal or external storage.
-boot.img (kernel)(extract it first)
-pronto_wlan.ko(wifi module)(extract it first)
-SuperSu.zip (you can download form net , search it)
2: use your file explorer(with root access) copy pronto_wlan.ko to /system/lib/modules/pronto.
replace the old one, chmod to 644. make sure to backup old one first , rename old one to pronto_wkan.ko.bak.
3ower off device and boot to TWRP.
4:Use TWRP to install boot.img(install as boot, DO NOT CHOOSE RECOVERY)
5:Use TWRP to install SuperSu.zp (to get root re-enable)
6:After all, reboot system, first booting time may take some time , wait , be patient.
7:After boot finsh, check your wifi and root are all functional.
8:Now you can start to use cifs function.
Don't ask me what is CIFS and how to use, search on net.
Also, don't ask me to add more function on Kernel, I'm not a developer,
all i need is Cifs enabled Kernel, no other needed.
Update:
V2: add ondemand governor for better battery life, wifi module also need to be update.
Thansk to Ashyx teaching me on Kernl building, and permissive code form he.
Thankk to cbtc helping me to solve Wifi problem and his Fenix Rom.
Nice job!
kevinchg said:
This is my personal compiled Kernel for SM-P350.
There is so little resource for my P350,
I need a Kernel with permissive and cifs function for my daily use,
because i frequently read PDF on local network,
with CIFS mount enbled , i can open PDF directly without the need to download it to my device.
However, i search all the forums, no this kind of Kernel i can find.
That's the reason i decide to learn compiling kernel from zero and finally out this kernel.
You may use this Kernel on P350 stock MM or Fenix Rom MM.
I'm currently on Fenix MM,
I cannot guarantee it will work on you P350, so , make a nadroid backup with TWRP first !
Click to expand...
Click to collapse
Hi Kevin, this is awesome!!! Thanks for posting this! I have been looking for a CIFS solution for a long time.
I have not installed this yet - just wanted to know if this removes any capability from the Fenix ROM?
Ideally I would like to have all functionality that Fenix gives me, with the ability to CIFS mount my NAS.
Just installed Fenix on the SM-P350 and its awesome (thanks heaps cbtc!)
- Matty -ArctiX
kevinchg said:
This is my personal compiled Kernel for SM-P350.
There is so little resource for my P350,
I need a Kernel with permissive and cifs function for my daily use,
because i frequently read PDF on local network,
with CIFS mount enbled , i can open PDF directly without the need to download it to my device.
However, i search all the forums, no this kind of Kernel i can find.
That's the reason i decide to learn compiling kernel from zero and finally out this kernel.
You may use this Kernel on P350 stock MM or Fenix Rom MM.
I'm currently on Fenix MM,
I cannot guarantee it will work on you P350, so , make a nadroid backup with TWRP first !
Take your risk by yourself.
Kernel Feather:
-Full Permissive
-Cifs built-in
-NTFS enable
Requirement:
-P350 Stock Android MM or Fenix Rom MM
-Device Rooted with TWRP installed
How:
1: Make sure you have 3 files copy to you internal or external storage.
-boot.img (kernel)(extract it first)
-pronto_wlan.ko(wifi module)(extract it first)
-SuperSu.zip (you can download form net , search it)
2: use your file explorer(with root access) copy pronto_wlan.ko to /system/lib/modules/pronto.
replace the old one, chmod to 644. make sure to backup old one first , rename old one to pronto_wkan.ko.bak.
3ower off device and boot to TWRP.
4:Use TWRP to install boot.img(install as boot, DO NOT CHOOSE RECOVERY)
5:Use TWRP to install SuperSu.zp (to get root re-enable)
6:After all, reboot system, first booting time may take some time , wait , be patient.
7:After boot finsh, check your wifi and root are all functional.
8:Now you can start to use cifs function.
Don't ask me what is CIFS and how to use, search on net.
Also, don't ask me to add more function on Kernel, I'm not a developer,
all i need is Cifs enabled Kernel, no other needed.
Update:
V2: add ondemand governor for better battery life, wifi module also need to be update.
Thansk to Ashyx teaching me on Kernl building, and permissive code form he.
Thankk to cbtc helping me to solve Wifi problem and his Fenix Rom.
Click to expand...
Click to collapse
YOU WILL HAVE THE FÉNIX ROM THAT YOU CAN SEND ME
Note
Before getting started, I'm not a developer and I'm not on that level yet but being an enthusiast of Android ROMs especially my favorite ROM Pixel Experience (PE). However what I can contribute (as of now) is to guide newbies and answer people who is confusing with flashing PE ROM, any custom kernels, mods, Gcam and help you out from problems while trying these things.
Tons credits to @jhenrique09, without his great effort there is no born of Pixel Experience project, and we would not have a taste of stock and pure Pixel ROM without having an actual Pixel phone.
It is good that you attempt new things and seek into the freedom of pure Android experience, and the whole world of Android development, though there's some risk when you try something new.
!!! Warning: I am not responsible for any bricked devices, it is your choice to modify your device software.
Pixel Experience ROM official thread - by Henrique Silva @jhenrique09
How to unlock bootloader?
https://xiaomiwiki.github.io/wiki/Unlock_the_bootloader.html
Official ROM downloads:
Download from Pixel Experience website
Screenshots
Check telegraph here!
Pixel Experience Official Wiki Page for Redmi K20 Pro/Mi 9T Pro - Info about raphael & raphaelin
Appreciation to
@jhenrique09, founder and lead developer of Pixel Experience, and maintainer for raphael & raphaelin (Redmi K20 Pro & Mi 9T Pro Series).
@WasikFahim, a friend of mine who assists me for creating this thread.
Thanks to all developers I have been know so far.
And all developers and original creators of the attached files below and for all of the following posts.
Special thanks to @Sandeeep Kiran (TG handle @ sandeeep, due to request from him), who has proposed the idea of creating this new thread for me.
Reserved.
Nice Thread ?
How To Flash Custom Kernels
Hello Guys Hope You're Fine, Today We're Going To Learn How To Flash Custom Kernels In Recovery, So Without Further Due Let's Jump Into It:
I'm Using PitchBlack Recovery
Prerequisite:
*Backup Stock Kernel [Boot.img & Dtbo(Optional)] Image=> 1 & 2
Steps For Flashing Custom Kernels:
1.Go To Recovery.
2.For OF(Go To Files) For TWRP/PBRP(Go To Install). Image=> 3
3.Select Kernel And Swipe to Install. Image=> 4 & 5
4.Wipe Dalvic/Cache.(Optional)
5.Reboot To System.
Enjoy!!!!!! :good::fingers-crossed:
Here Are Some Recommended Kernels:
We Use LOS FOD Implementation.
Gaming & Decent Battery = F1xy
Battery Backup & Decent Gaming = Immensity
Decent Performance + Battery = Englezos (Less gaming)
Mods tutorials
ANX Camera
ANX Camera TWRP
ANX Camera magisk
Working version of ANX magisk: 185
48MP fix for ANX camera magisk module: 181
Which ones should I download? Check attached screenshots below this post.
How to install and setup MIUI camera on PE?
* For ANX Camera TWRP
1. Save zip file to internal storage (/sdcard) and reboot to recovery.
2. For orangefox go to "files", for TWRP or Pitchblack recovery go to "install".
3. Swipe button to install.
4. Reboot to system.
5. Give all permissions to ANX camera, launch and quit app for at least 3 times.
6. You're all done.
* For ANX Camera magisk modules
1. Save both camera and 48MP fix modules to internal storage (/sdcard).
2. Open magisk manager, hamburger icon on top left corner, modules, tap on "+" icon and find ANX camera zip.
3. Same goes with 48MP fix module.
4. Reboot, give all permissions to ANX camera app, then launch & quit app for at least 3 times.
5. You're all done.
* 48MP fix is already included in ANX Camera TWRP, do NOT flash the 48MP fix magisk module.
* No root needed.
+ Credits to ANX developers and contributors, @HSgod, @nuub1k, for porting and debugging MIUI camera to AOSP ROMs.
Custom boot logo
MS drive Downloads
Head to XDA thread for more info, credits for @mouhannadsukkar creating boot logo collection.
Disable force encryption
Force Encrytion and difference compared with decrypted storage
1. All ROMs have force encryption by default for now, which should be enabled while booting the device for the first time.
2. Therefore DFE, also known as "disable force encryption", which shall force the device to be decrypted (Use #-dfe to get the DFE file).
3. If you format data, it will decrypt the encrypted storage, while everything on data partition including internal storage, also known as /sdcard directory, will be erased.
4. However if you already got a decrypted storage, simply wipe data and internal storage won't have any effects, unless you do a format.
5. To keep the storage decrypted, if you want, you will need to flash DFE for every ROM and vendor update.
6. Format data only if you flash custom ROM from stock MIUI, if you want to keep your storage decrypted or you want encrypted without flashing DFE while flashing custom ROMs and vendors (if the ROM uses MIUI vendor).
7. In short formatting data is to remove encryption for an encrypted device.
How to flash DFE?
IMPORTANT: Please make sure you perform a data FORMAT (NOT wipe) via recovery before flashing DFE, otherwise device may end up with bootloop or stuck in bootloader! Everything including all files on internal storage will lost so please backup everything to elsewhere. You have been warned, I am not responsible for data loss.
1. Go to recovery and format data (NOT wiping it, the place where you will type "yes" and confirm formatting).
2. Since internal storage is purged too, copy DFE from your PC or OTG storage etc., flash via recovery.
3. The recovery console will ask you to press volume buttons for picking options, so the recommended key combination is:
+ (vol up)
- (vol down)
- (vol down)
+ (vol up)
4. Done, reboot to system and see if storage is decrypted.
F2FS
What is F2FS?
F2FS, which stands for "Flash-Friendly File System", it was invented by Samsung coorperation, mainly focus on improving random read/write efficiency of flash storage and somewhat extends its lifespan.
Notice!!!
Currently, almost all known custom ROMs support F2FS on cache and data partitions but not system for compatibility and disk quota reasons, usually there's no writing actions to system partitions except flashing/updating ROM or using root access to modify it so keep system partition as EXT4.
How to enable F2FS?
You will lose all of your data including internal storage.
1. In recovery, convert data partition to F2FS via advanced wipe, same for cache partition (Do not convert system partition to F2FS to avoid some possible problems).
2. Flash f2fs-patched-fstab.zip (attached below) via recovery.
3. Reboot.
Note: You will have to flash patch again whenever flashing/wiping vendor, otherwise you will stuck at boot animation.
Fix low microphone problem (magisk needed)
Description
Sometimes, you might feel the microphone sensitivity isn't good enough on AOSP ROMs including Pixel Experience, this might related to device tree (or source code) of K20 Pro/9T Pro series. For instance you make or pick a phone call, using voice call of some IM apps the other side might not hear you clearly, that's the time when you can have a workaround if you have magisk installed.
How to fix?
Same as you install any magisk modules via magisk manager.
magisk_iem_mic_gain_0.3.zip attached below.
Magisk manager recovery mode
What to do if my device stuck at boot animation?
Sometimes, your device might stuck at boot animation because you flashed a buggy magisk module, for obvious reasons you have to delete that for letting your device boot into OS, so what about removing it via recovery? That's how this zip comes - Magisk Manager Recovery Mode.
How?
1. Boot your device to recovery, flash provided zip file.
2. Go to advanced => terminal.
3. Type this command to launch program:
sh /sdcard/mm
4. Type l to list all installed magisk modules, locate the one which might causes the problem.
5. Type r, enter, then the name of module name as the output shown, case-sensitive!
For example:
module[]
You should type:
module
Then enter.
6. If you see there's an X inside brackets like:
module[X]
Then you're good to go.
7. Reboot your phone and that's it.
Troubleshoot and advanced guides
Stuck at bootloader
Sometimes when you flashed ROM, custom recoveries, or updating vendor and try rebooting your device thereafter, your device does not boot into system or recovery but fall into bootloader (fastboot) screen. This is due to verified boot of our device being triggered, so flashing a custom vbmeta will usually get the problem solved.
How to flash vbmeta?
You need a working PC or laptop, USB cable and install fastboot driver if you are using Windows.
1. Download attached vbmeta file to your PC, connect your phone with USB cable, make sure PC has detected the phone and it's connected properly.
2. Open CMD (if using Windows) or terminal (Linux/Mac).
3. Type the following command:
Code:
fastboot flash --disable-verity --disable-verification vbmeta fake_vbmeta_williamfeng.img
4. Reboot your device to either recovery or system, it should work fine now.
Upgrade vendor
Note: You will not lose your data so you don't need to wipe anything, just flash vendor on top of current one, no matter if device is encrypted
1. Download right vendor zip for your device variant, see official PE wiki page.
2. Reboot your device to recovery, copy vendor zip to your internal storage.
3. On your device, select install and flash vendor zip.
4. Reboot to system.
Downgrade vendor
Note: Before you downgrade your vendor you're suggested to backup all your data (including internal storage) elsewhere in case you lose them while doing so.
If your device is decrypted (NOT encrypted), the steps are same as you upgrade vendor.
Otherwise:
1. Download right vendor zip for your device variant, see official PE wiki page.
2. Reboot your device to recovery, copy vendor zip to your internal storage.
3. On your device, select install and flash vendor zip.
4. Format data partition in your recovery (the place where you'll type "yes" and confirm formatting).
5. Reboot to system.
How to update PE ROM?
You don't need to download full zip file on PE, it gives small OTA which can be downloaded from "settings => system => system updater". After downloading simply tap on 'apply/install update', then the device will boot into recovery, update and reboot back into system.
WARNING: Make sure your device always have enough charge (30% or more is suggested) for updating process.
* The update file will be downloaded to /data/system_updates
Error 7 when updating PE
- If you see updating ROM doesn't work and the recovery shows you error 7, please make sure you update vendor to correct one first.
- Try updating your recovery (TWRP/OFOX).
If it still happens, try flashing full ROM zip of latest build instead of using built-in updater from ROM.
Miscellaneous info of Pixel Experience
Changing animation of Pixel Experience - just like you have a real Pixel device!
Power-off your phone and plug into changer, you'll see that.
Video link