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 ??
Related
[TOOLKIT] UNIFIED ANDROID TOOLKIT - SAMSUNG GALAXY S4 MINI - Drivers, Root, Recovery + MORE
INTERNATIONAL GSM MODEL [GT-I9190] [Supported up to 4.2.2]
INTERNATIONAL LTE MODEL WITH NFC [GT-I9195] [Supported up to 4.2.2]
DUAL SIM GSM MODEL [GT-I9192] [Supported up to 4.2.2]
LATIN LTE MODEL [GT-I9195L] [Supported up to 4.2.2]
LTE MODEL [GT-I9195T] [Supported up to 4.2.2]
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. Hold down the 'HOME' + 'VOLUME UP' + 'POWER' buttons for about 5-15 seconds until you see the Samsung logo on the screen.
3. Release all buttons straight away to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Hold down the 'HOME' + 'VOLUME DOWN' + 'POWER' buttons for about 2-15 seconds until a WARNING! Screen appears.
3. 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.
----------------------------------------------------------------------------
Q. "Superuser/SuperSU has stopped" message after rooting
After updating Samsung device to newer builds of Android [4.3 and later] which contains the new security from Samsung "Samaung KNOX", you might face a problem if you tried to root your device.
This might happen because of KNOX security, it blocks/disables the Superuser app and you will see this notification after the first boot:
"Unfortunately, SuperSU has stopped" or "Unfortunately, Superuser has stopped" depending on the root method you used.
The easiest way to fix this problem is by installing the superuser apk file. Select option 6 from the Rooting Section and the Toolkit will attempt to extract the superuser.apk file from the root zip file in the Root folder and if successful it will then be installed. You can then run the app [Superuser or SuperSU] from the apps list. A warning message will pop up saying Samsung KNOX has been detected and ask if you want to try and disable it. Click OK, KNOX should be disabled and your device should now be properly rooted.
There is more Information/Help at http://www.skipsoft.net/?page_id=1269
**VIDEOS**
**UPDATES**
Amazing! Thanks!!
Tapatalk-kal küldve az én GT-I9195-el
Glad to see this. I've got the toolkit for my 2012 Nexus 7, it is very useful.
hi !
i have a question about full backup/restore of roms ,but nobody can answer to me .
=> http://forum.xda-developers.com/showthread.php?t=2697516
what do you think about ?
thank in advance !
Loulou-13 said:
hi !
i have a question about full backup/restore of roms ,but nobody can answer to me .
=> http://forum.xda-developers.com/showthread.php?t=2697516
what do you think about ?
thank in advance !
Click to expand...
Click to collapse
If you have a backup made in custom recovery then you can boot to custom recovery and restore it. This will take you back to the exact state when you made the backup. The /data/media/ (internal storage) is not backed up by custom recovery but this will not affect the backup in any way.
If you wipe data from recovery after the flash then all installed apps (apart from the stock ones) will be deleted so if you want to wipe the /data/media folder then do so before restoring the backup. Also make sure the backup is on your external storage (micro sdcard) or it will be deleted when you perform a wipe.
Mark.
hi !
thank you very much for your answer !
when i have made a backup of a stock rom (rooted) , i have tested CM10.1.2 ...and after that, i go to recovery for to restore my previous backup ( with wipe data-factory +cache + dalvik before restoring my stock rooted rom ) ====> i had lots of bigs FCs !!!! hard to switch off the phone (too much FCs)
why ??? where is the problem ?
( to solve it in emergency ,i had to do the 3 wipes agains ,switch-off the phone and flash stock firmware via odin ... )
mskip said:
**UPDATES**
Click to expand...
Click to collapse
Could you by any chance provide a full firmware for I9195 and the others I9190, I9192?
(meaning PIT, CSC, BOOTLOADER files for Odin)
I want to provide a free mirror for my unbrick thread
Deleted....
Sorry this should have been posted on here a while ago.
The device module has just been updated and i'm trying to update all the threads.
Toolkit Update
+Updated Toolkit base to v1.3.4
+Added support for the latest available builds on all device modules
+Updated SuperSU [Chainfire] root app to latest version v2.45
+Added SuperSU Beta [Chainfire] root app to flash if required latest version v2.42
+Updated Busybox installer by Stephen Erickson to v25
+Updated Root Checker by Burrows Applications to v3.68
+Added Install EFS/Partition Backup/Restore app by Wanam v1.33
+Added an any build option to the build menu [pro users only] to root any build
+Updated root procedures for better operation
+Toolkit will now notify you a new public version is available and download the installer for you
+Fixed unroot zip file to properly unroot your device
+Updated a lot of the code
Supported models/builds list: http://www.skipsoft.net/?page_id=1203
Download from: http://www.skipsoft.net/?page_id=1069
If you have already downloaded the new Toolkit and have the v3 module for the S3 Mini then delete the ConfigGalaxyS3Mini.exe from the tools folder and the Unroot-UninstallBusybox-CwmManager.zip from the root folder. Download the new unroot zip file from http://skipsoft.net/download/fileupdates/Unroot-UninstallBusybox-CwmManager.zip and move it to the root folder, start the Toolkit and select the Galaxy S3 Mini from the list. The Toolkit will then download new module files.
Mark.
AutoUpdate Available for Samsung Galaxy S4 Mini module (Ultimate/Pro Users)
CHANGELOG:
BIG UPDATE [sorry its not been updated in a while]
+Updated models to support latest builds [including any build option]
+Added futureproof support with the new custom support loader option
+no-verity-opt-encrypt zip file [downloads to tools folder after device selection]
+Added latest Magisk zip file [downloads to root folder after device selection]
+Added NEW ULTIMATE FEATURE to add build support for any supported Toolkit device from download link, firmware or boot/recovery images. More Info at skipsoft.net
+Added completely new much improved detection routine for adb/recovery modes and integrated it in Toolkit procedures so automatic detection/rebooting works better
+Updated Toolkit base for NEW ULTIMATE FEATURE. Toolkit will update any device module to latest main module version even if an AutoUpdate is not ready yet
+Updated some root functions and removed SuperUser by CWM from root selection
+Added VerifiedBootSigner zip file to use in the Toolkit on newer builds if needed
+Integrated flashing verifiedbootsigner in to root procedures if ever needed
+Toolkit will disable all server pings if they cause any trouble with downloads
+Made some routines work better with more checks to make sure files exist
+Updated Drivers section with new options and adb check tool
+Updated Firmware section with better firmware support. Added Updato.com links
+Improved some Main Menu functions
+Updated app/file versions to latest
+Bug fixes and more I probably forgot to write down
If you find any of this useful PLEASE donate to a device project. You can do it through the Toolkit (after selecting the device at startup) or from the link at https://www.skipsoft.net/?page_id=703 so you get the right code fast and can update to the latest version. You can also go ULTIMATE mode and unlock ALL device modules for the lifetime of the Toolkit. Follow us on twitter at https://twitter.com/mskipxda for posts/updates.
Enjoy.
FIRST EVER Team Win Recovery project TWRP 2.7.0.0 Compiled From Source for Canvas HD with Full Kitkat 4.4.2 Support Courtesy of Kash Kernel [21 May 2014]
About TWRP:
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. 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.
Click to expand...
Click to collapse
Sources :
Team Win Recovery Of Omni Source
Device Tree For Micromax A116
Modified Kernel Source of A116
Download: Check Download Tab
Instructions for flashing in your phone:
1.Download the recovery and Put it in root of your SDCARD
2.Open Mobile uncle tools and select Recovery Update
3.Flash recovery file
4.Done
5.Enjoy
Bugs: No Bugs..You can Report If found
Instructions for flashing using SP Flash Tools:
1. Install drivers for your phone using Micromax drivers.
2. Extract the Stock ROM folder and replace recovery.img with twrp recovery.
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
5.Check only recovery.img, 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.
Disclaimer: By Downloading and flashing the Recovery may void your Warranty ..Ill not be Responsible for any harm .Do it on your own Risk
Please do give Feedback about My recovery So that others can Judge if its stable or not :fingers-crossed: and also it encourages me to do stuffs like this :good:
Credits:
@michfood For his Repacking Tools
@yuweng For his help
Team Win Recovery Project
@kashifmin for his Kernel
XDA:DevDB Information
TWRP 2.7 Full Touch Recovery , Tool/Utility for the Micromax A116
Contributors
suhas.holla
Version Information
Status: Stable
Current Stable Version: 2.7.0.0
Stable Release Date: 2014-05-21
Created 2014-05-21
Last Updated 2014-05-22
Reserved
What's new in 2.7.0.0:
Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
Allow sideloading from /tmp on encrypted devices
Check for a crypto footer before asking for a password to prevent user confusion
Additional checks for validity to auto generated backup names
Text wrap in the console output
Proper caps lock support in the keyboard
Mouse support via USB OTG for devices with a broken digitizer
Improve scanning of storage locations for OpenRecoveryScript
Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions
Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
Update SuperSU to 1.93 and improve installation process
Added selinux contexts restoration to fix permissions
Load RTC offset on Qualcomm devices to fix the date/time in recovery
USB Mass Storage fixes Add SELinux support checking
Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
Add 4.4 AOSP decrypt support
Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
Various SELinux fixes and bug fixes
Thanks bro, #reapect
suhas.holla said:
FIRST EVER Team Win Recovery project TWRP 2.7.0.0 Compiled From Source for Canvas HD[21 May 2014]
Click to expand...
Click to collapse
the op here may also be updated - for info of first-time/casual visitors.
We can use the mobile uncle method too right??
Ok sorry about that just read the op
Sent from my Micromax Canvas HD using XDA Premium 4 mobile app
Uhm, where is the download tab? Am i blind? :what:
GroovyG said:
Uhm, where is the download tab? Am i blind? :what:
Click to expand...
Click to collapse
http://forum.xda-developers.com/devdb/project/?id=4259#downloads
Cheers mate, found it in a normal browser. In the XDA app it's inaccessible, weird...
140+ Downloads Not Even a single reported about the Recovery..Plz do report regarding your experience with this recovery
It's brilliant, backup and flashing happens a lot faster than with previous builds.
No issues encountered so far, great job!
Thanks for the best recovery. Please add screen shots if you can?
Sent from my C2305 using XDA Premium 4 mobile app
Thanks for the Recovery. Updated the Recovery through mobile uncle tool. Was able to make a back up without md5. Generation. But could Not restore the backup inspite of disabling md5 verfication. Does anyone face such issue. Flashing a rom, wiping data, system etc works fine
Sent from my C2305 using XDA Premium 4 mobile app
suhas.holla said:
....TWRP 2.7.0.0.... for Canvas HD with Full Kitkat 4.4.2 Support Courtesy of Kash Kernel
Please do give Feedback .....So that others can Judge if its stable or not ....encourages me to do stuffs like this
Click to expand...
Click to collapse
tried this. things look fine. :good:
review after brief testing:
'auto-generate-name' and 'custom-name' backups both restored fine.
settings get saved & retained over reboots.
rom installs are also fine.
taking screenshots is a breeze, thanks to "adb-enabled in recovery".
check out my screenshots here.
Can we turn off the vibrate on touch??
Sent from my Micromax Canvas HD using XDA Premium 4 mobile app
tandevilz said:
Can we turn off the vibrate on touch?
Click to expand...
Click to collapse
go to settings --> vibration duration and lower values to zero or whatever.
and, while you're in recovery, take the time to explore all menus.
Does anyone face problem in restoring a back up made by disabling the md5 verification option. The system gives error message
Sent from my C2305 using XDA Premium 4 mobile app
baskye said:
...problem in restoring a back up made by disabling the md5 verification option. ....
Click to expand...
Click to collapse
backups with these settings restored fine.
Recovery is great, feels solid and stable while using! All setting etc working properly, nandroid backups are a LOT faster and smaller than any recovery yet, .zip installation time is noticibely faster, adb working flawlessly, USB mount I havent checked yet but sure that it will work too!
All-in-all the best recovery yet. And thanks to you @suhas.holla for it! :good::beer:
deepesh.tickoo said:
....USB mount I havent checked yet but sure that it will work too!
Click to expand...
Click to collapse
didn't work for me. please check & report (with steps/how-to). @suhas.holla too. thanks.
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:
CHANGELOG for 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.
CHANGELOG for 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
CHANGELOG for 2.8.0.1:
-Fix a bug that causes weird graphics glitches and touch issues
CHANGELOG for 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.
CHANGELOG for 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
DOWNLOAD:
TWRP Builds
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
INSTALLATION:
* Download MoDaCo Mod for MOJO Here . This zip contains the adb and fastboot binaries for Linux, Mac , and Windows. If you have windows install the drivers inside the zip if not continue.
* Place the downloaded image in the root of the r3-mojo-superboot-mmm folder
* Enter fastboot mode by unplugging the device and connecting the male A to male A usb cable to the device and the computer and plugging in the power adapter. Once in fastboot follow the below commands.
* To exit fastboot mode remove the male A to male A usb cable and plug in the power adapter to start a normal boot.
WINDOWS - open cmd prompt in the root of the r3-mojo-superboot-mmm folder
To install the image to device:
Code:
fastboot-windows.exe -i 0x0738 flash recovery openrecovery-twrp-2.8.2.0-mojo.img
To boot the image:
Code:
fastboot-windows.exe -i 0x0738 boot openrecovery-twrp-2.8.2.0-mojo.img
MAC - Open a terminal in the root of the r3-mojo-superboot-mmm folder
Code:
chmod +x fastboot-mac
Code:
./fastboot-mac -i 0x0738 flash recovery openrecovery-twrp-2.8.2.0-mojo.img
To boot the image:
Code:
./fastboot-mac -i 0x0738 boot openrecovery-twrp-2.8.2.0-mojo.img
LINUX - Open a terminal in the root of the r3-mojo-superboot-mmm folder
Code:
chmod +x fastboot-linux
To install the image to device:
Code:
./fastboot-linux -i 0x0738 flash recovery openrecovery-twrp-2.8.2.0-mojo.img
To boot the image:
Code:
./fastboot-linux -i 0x0738 boot openrecovery-twrp-2.8.2.0-mojo.img
USING TWRP:
* You must have a usb mouse installed. Alternatively you can use the C.T.R.L.R in mouse mode to navigate the UI.
@gwaldo @Sir Jaxxy I have posted a new build . The name of the image is exactly the same so it matches the instructions so make sure you delete the previous image. The issue was a file was missing landscape.xml and the reason mine didn't fail is because I had a custom theme applied which included this file. Enjoy!!
Top notch work
Unjustified Dev said:
@gwaldo @Sir Jaxxy I have posted a new build . The name of the image is exactly the same so it matches the instructions so make sure you delete the previous image. The issue was a file was missing landscape.xml and the reason mine didn't fail is because I had a custom theme applied which included this file. Enjoy!!
Click to expand...
Click to collapse
It's booting, but I'm not getting no display (No DVI-D Cable is displayed on monitor)
Also, ALT+SYSREQ+I doesn't re-init the display.
At the end of the recovery.log
I:Copying file /cache/recovery/log to /cache/recovery/last_log
tw_get_context got selinux context: ubject_r:unlabeled:s0
I:Got default contexts and file mode for storage files.
I:Attempt to load settings from settings file...
I:Loading settings from '/data/media/0/TWRP/.twrps'.
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/15C40C1C30400000012FC8380'
I:Copying file /etc/recovery.fstab to /cache/recovery/recovery.fstab
I:Version number saved to '/cache/recovery/.version'
__bionic_open_tzdata: couldn't find any tzdata when looking for CST6CDT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
I:TWFunc::Set_Brightness: Setting brightness control to
I:Cannot find file
I:Switching packages (TWRP)
I:Skipping screen timeout threads: TW_NO_SCREEN_TIMEOUT is set
I:Starting command line thread
Click to expand...
Click to collapse
gwaldo said:
It's booting, but I'm not getting no display (No DVI-D Cable is displayed on monitor)
Also, ALT+SYSREQ+I doesn't re-init the display.
At the end of the recovery.log
Click to expand...
Click to collapse
This is very strange as it seems to be displaying ok for me and another guy. Try flashing the image first then using an app such as Quick reboot to boot into recovery and see if it loads. That error is there because there is no backlight as the device has no display I see that error when flashing or wiping. I've also disabled screen timeout because it's kind of useless for it to be implemented on a device such as this one.
Unjustified Dev said:
This is very strange as it seems to be displaying ok for me and another guy. Try flashing the image first then using an app such as Quick reboot to boot into recovery and see if it loads. That error is there because there is no backlight as the device has no display I see that error when flashing or wiping. I've also disabled screen timeout because it's kind of useless for it to be implemented on a device such as this one.
Click to expand...
Click to collapse
nope
I've used the newest img, can you upload the original, that one had a resolution issue not a display, issue for me.
Flashed it,
booted normally,
bootmenu reboot, rebooted into recovery
Same 'No DVI-D cable'
I tryied pluging in the HDMI cable at different times before boot/after boot, but same.
I'll try on the TV later today, but i'm not optimistic :/
I guess it's not using the mojo's kernel right?
the keyboard ALT+SYSREQ+B and O don't work (reboot, shutdown)
How's the another guy?
Maybe he was being nice?
gwaldo said:
nope
I've used the newest img, can you upload the original, that one had a resolution issue not a display, issue for me.
Flashed it,
booted normally,
bootmenu reboot, rebooted into recovery
Same 'No DVI-D cable'
I tryied pluging in the HDMI cable at different times before boot/after boot, but same.
I'll try on the TV later today, but i'm not optimistic :/
I guess it's not using the mojo's kernel right?
the keyboard ALT+SYSREQ+B and O don't work (reboot, shutdown)
How's the another guy?
Maybe he was being nice?
Click to expand...
Click to collapse
He's already running cyanogenmod. Try deleting that theme you placed in the sdcard. I'm not sure the exact error but I too end up with no signal only if the TV was powered off before recovery booted or if I turn the TV off and try to turn it back on. I can used adb devices and it still shows it's in recovery not sure the exact cause of that issue.
is there a way to enter recovery (or reboot to recovery) from the mojo itself ? that is without the need of an usb cable, a computer and typing the "fastboot... boot" command.
I tried the 'reboot to recovery' function of this app: https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager but it didn't work
kgersen said:
is there a way to enter recovery (or reboot to recovery) from the mojo itself ? that is without the need of an usb cable, a computer and typing the "fastboot... boot" command.
I tried the 'reboot to recovery' function of this app: https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager but it didn't work
Click to expand...
Click to collapse
Did you fastboot flash the image? It won't stick if you don't flash it. You can type adb reboot recovery via wireless adb. You can also try the quick reboot app
Sent from my LGMS395 using Tapatalk
kgersen said:
is there a way to enter recovery (or reboot to recovery) from the mojo itself ? that is without the need of an usb cable, a computer and typing the "fastboot... boot" command.
I tried the 'reboot to recovery' function of this app: https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager but it didn't work
Click to expand...
Click to collapse
I use this app and it works great
https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot
Sir Jaxxy said:
I use this app and it works great
https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot
Click to expand...
Click to collapse
Yeah that's the app. [emoji3]
Sent from my LGMS395 using Tapatalk
kgersen said:
is there a way to enter recovery (or reboot to recovery) from the mojo itself ? that is without the need of an usb cable, a computer and typing the "fastboot... boot" command.
I tried the 'reboot to recovery' function of this app: https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager but it didn't work
Click to expand...
Click to collapse
You need to flash the recovery to mojo once, then yes it *should* work.
I don't have a display which can handle the initial display and need a keyboard to do a ALT+PrtScn+I to reinitialize before seeing it.
Sir Jaxxy said:
I use this app and it works great
https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot
Click to expand...
Click to collapse
yeah that one worked, thx.
Just letting you guys know that I was able to successfully flash the recovery using this app. Worked without issue and it's an option for those without a USB cable.
Unjustified Dev said:
He's already running cyanogenmod. Try deleting that theme you placed in the sdcard. I'm not sure the exact error but I too end up with no signal only if the TV was powered off before recovery booted or if I turn the TV off and try to turn it back on. I can used adb devices and it still shows it's in recovery not sure the exact cause of that issue.
Click to expand...
Click to collapse
2.8.2.0 works for me using the HDMI capture... Haven't tried on a TV yet.
It pairs with the CTRLR (blue light comes on) but doesn't work, keyboard doesn't work either, mouse is the only working input.
gwaldo said:
2.8.2.0 3:30Am works for me using the HDMI capture... Haven't tried on a TV yet.
It pairs with the CTRLR (blue light comes on) but doesn't work, keyboard doesn't work either, mouse is the only working input.
Click to expand...
Click to collapse
Are you in mouse mode seems like it's the only mode that works for us.
Unjustified Dev said:
Are you in mouse mode seems like it's the only mode that works for us.
Click to expand...
Click to collapse
Yip, i switched to all modes didn't work...
I'll trying booting with it on mouse mode
gwaldo said:
Yip, i switched to all modes didn't work...
I'll trying booting with it on mouse mode
Click to expand...
Click to collapse
Have you tried switching USB ports?
This TWRP supports encryption (no need to wipe data) , OTA update (TWRP persist), & also it can root within itself.
The root is achieved with Magisk 17.1, no need to flash any encryption disabler or anything, it simply works!!
I present you: [LR. Team] TWRP
Credits to original devs & authors, not me.
Download link by LR. Team: https://yun.baidu.com/s/1jj0NE1pqeF1ejiNAsm1qUw
Download password: jjfd
Mirror by me: https://www64.zippyshare.com/v/HQdMlIDX/file.html
FEATURES said:
* Delete redundant languages, keep English, add Chinese language, default Chinese.
* Modify the default configuration, for example, the default time zone is East Eight Zone, default screen brightness, default vibration, default 24 hours, default return button on the right, default Chinese and so on.
* Modify the default configuration file path to reduce the possibility of conflicts with other people's compiled versions.
* Adjust and optimize the Chinese text and description, and re-edit all the items one by one, which is more accurate, understandable and humanized. Also added display mtp enable off display, file operation result display, operation page title display, permission description when modifying permissions, etc. UI text display.
* Modify the unlocking interface and adjust the height of the sliding unlocking bar, which can effectively prevent misoperation (the original unlocking bar and the operating unlocking bar are of the same height. When the unlocking is completed, the sliding may be repeated, and the corresponding action is directly operated).
* Open more partition backup and restore, such as modern baseband partition, bootloader, persist, cust and other partitions, easy to backup the underlying files before flashing, can restore the underlying files after flashing.
* Add .bin and .mbn format image files, so you don't need a zip brush package, you can write the underlying file. The original version only supports the flashing of .img format image files. (Be sure to pay attention to the selected partition!!!!)
* Solve the problem of interface jam when using the simulation operation (the simulation operation is mainly for testing the theme, and no actual operation).
* Add the manual installation root function in Advanced Options > root system. Add a display root system option on this basis for manual operation.
* Added the ability to unenforce encryption, in advanced options > Unforce Encryption. You can remove the official system to force encryption and cancel the check.
* Change the built-in root mode and add magisk as the default root mode.
* Fixed button and button operations for some interfaces.
* The adb/usb debug mode is enabled by default, which is convenient for operating the phone through the computer command line in rec mode.
* MTP is enabled by default. In the rec state, you can also connect your phone to your computer to facilitate file copying.
* Modify the logo interface, modify the header of the main interface page, and add the display phone model and team name, author name.
* Fix some logical relationships and modify some interface displays.
* Added clear root function
* Added clear power-on password function
* Added clear battery information function
* Added signature boot function
* Added restore official rec function
Click to expand...
Click to collapse
CHANGELOG said:
2018.10.02
1. Support pt, to be tested.
2. Add the remove dm checksum and cancel the forced encryption function.
3. Built-in root and clear root changed to Magisk v17.1
4. Repair automatic decryption data
Click to expand...
Click to collapse
FLASHING PROCEDURE said:
1. Working brain
2. Common sense
3. Common knowledge of flashing via fastboot
4. UNLOCK THE MI 5S PLUS
5. Use cmd line: fastboot flash recovery [name of the file]
6. First reboot to recovery: fastboot boot [name of the file]
IF TOUCHSCREEN IS NON-RESPONSIVE ON FIRST RECOVERY BOOT, FORCE REBOOT IT USING [VOL UP + POWER].
After flashing, if you encounter Chinese UI, press Language then select English.
Root menu is in the [Advanced] .
Click to expand...
Click to collapse
Enjoy!!
Crescendo Xenomorph said:
This TWRP supports encryption (no need to wipe data) , OTA update (TWRP persist), & also it can root within itself.
The root is achieved with Magisk 17.1, no need to flash any encryption disabler or anything, it simply works!!
I present you: [LR. Team] TWRP
Credits to original devs & authors, not me.
Download link by LR. Team: https://yun.baidu.com/s/1jj0NE1pqeF1ejiNAsm1qUw
Download password: jjfd
Mirror by me: https://www64.zippyshare.com/v/HQdMlIDX/file.html
Enjoy!!
Click to expand...
Click to collapse
this twrp support flashing to android pie pixel ex, cyberian os etc?
mustofal said:
this twrp support flashing to android pie pixel ex, cyberian os etc?
Click to expand...
Click to collapse
yes...
Thanks, works great, apart from
- Touchscreen works only after second start using power + volume up (as described by you already above)
- but ROOT does not seem to work under ... however it performs the Magisk v17.1. Installer without error.
- I noticed, that after startup, a 'decrypt data' passwort is requested, which I just cancelled away -> what is this used for and could it affect the non-rooting issue? - Do I need to format data first?
Figured out that it was all about formatting the data partition.
add turkish language ?
Work like a charme on my mi 5s plus. Thank you so much. Root work well too. I flashed with fastboot but It doesn't work. Than i tried to boot instead flash and It work well. Thanks again
_Ayhan_ said:
add turkish language ?
Click to expand...
Click to collapse
you can make a request to original devs... I'm only sharing....
Crescendo, pleeease give us more detailed instructions. Some of us are 'casual users' and have forgotten things. My last flashing was almost 2y ago
Crescendo Xenomorph said:
yes...
Click to expand...
Click to collapse
Regret i using this TWRP flash "RR-O-v6.0.0-20180222-natrium-Unofficial" i get "error 7" in TWRP but i flash "Viper-natrium-20171018-Coral-v3.1.1-Final-N" ROM it no problem... Any idea ?
[RECOVERY] TWRP 3.5.0-0 - 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.
flame Device Config: https://github.com/bigbiff/android_device_google_coral
DOWNLOAD:
Please go to https://twrp.me to download the device image.
A11 Testing:
https://build.twrp.me/test/flame/twrp-3.6.0-0-test1-flame.img- updated for lineage-18.1 booting
Old info:
Hello, this is a test build for flame users (will work on coral crosshatch/blueline later). The image is pretty safe for backing up now.
So far I have decryption working, touch, adb and backup and restore seems to work. Super partition volumes can be mounted, and the super partition can be backed up.
Not working: sideload and fastbootd
May FW Date https://build.twrp.me/test/flame/twrp-3.3.1-0-test1-flame.img
June FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test1-flame.img
July FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test2-flame.img
July FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test4-flame.img
- fix super partition restore
- fix persist partition restore
July FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test5-flame.img
- allow repacking of TWRP boot.img
- magisk currently doesn't work
August FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test6-flame.img
August FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test7-flame.img
- fix repacking TWRP with magisk
August FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test8-flame.img
- multiuser decryption support
- fastbootd support
3.5.0-0: Android 11 bringup
https://build.twrp.me/test/flame/twrp-3.5.0-0-test1-flame.img
https://build.twrp.me/test/flame/twrp-3.5.0-0-test2-flame.img
- Titan M Wipe working on Format Data
- Apex fixes for flattened directories
- Credit to @Freak07 https://github.com/freak07/FLORAL - using his kernel as a Coral/Flame TWRP base
http://twrp.me
What to backup
* super
* data
* persist
* boot
* any other partition desired
What to restore
* super
* data
* boot - depending on ROM support
Please just restore persist if you have a failed partition. I do not recommend restoring backups from phone to phone unless you know what you are doing.
Repacking TWRP into Boot partition
To repack TWRP into the boot partition to override stock recovery when rebooting to recovery, perform the following steps
1. adb push <latest_boot.img> /sdcard/
2. reboot to bootloader and fastboot latest boot.img of TWRP
3. Go to Install
4. Touch Install Image
5. Select your boot.img from /sdcard
6. Swipe to confirm flash
7. Reboot to recovery and android to verify installation
TWRP won't Boot?
Make sure you have a kernel that supports the R DTBO and LZMA ramdisk starting with test5 such as https://forum.xda-developers.com/pi...nel-kirisakuraq-1-0-0-pixel-4-xl-aka-t3992213
Is this just for flame? Or both coral and flame? Reason I ask is because the 2 devices have significant differences, and if it's just for flame, you'll want to throw it in the regular Pixel 4 subforum
This is for flame as described. I will work on coral next.
They share the same device tree btw.
Weird I thought I chose pixel 4 forum. Asking for this thread to be moved.
bigbiff said:
Weird I thought I chose pixel 4 forum. Asking for this thread to be moved.
Click to expand...
Click to collapse
Ah man lol got me all excited!
Thanks long awaited :good:
Will try later..
ok fastboot boot boots fine to TWRP but decryption wont work for me
https://paste.omnirom.org/view/e9536f05
Can confirm this works for flashing. Booted the image and then ADB pushed magisk and kernel and both flashed successfully!
Will try removing lockscreen security next attempt to gain access to internal storage which should likely work.
Great work to see, we are finally not tied to magisk for flashing things now
Mrcactuseater said:
Will try removing lockscreen security next attempt to gain access to internal storage which should likely work.
Click to expand...
Click to collapse
wont work to @my end
2WildFirE said:
Thanks long awaited :good:
Will try later..
ok fastboot boot boots fine to TWRP but decryption wont work for me
https://paste.omnirom.org/view/e9536f05
Click to expand...
Click to collapse
Can you paste logcat output too?
Please guys don't just say it doesn't work. I need recovery.log and logcat so I can debug issues.
2WildFirE said:
wont work to @my end
Click to expand...
Click to collapse
Can you please post recovery.log and logcat?
bigbiff said:
Can you please post recovery.log and logcat?
Click to expand...
Click to collapse
Yep
Is ADB logcat -l the correct one?
2WildFirE said:
Yep
Is ADB logcat -l the correct one?
Click to expand...
Click to collapse
I usually do in adb shell
logcat > /tmp/logcat.txt
Then adb pull /tmp/logcat.txt
OK here logcat https://paste.omnirom.org/view/9caa8b33
And recovery.log https://paste.omnirom.org/view/3c26a706
hope it helps
2WildFirE said:
OK here logcat https://paste.omnirom.org/view/9caa8b33
And recovery.log https://paste.omnirom.org/view/3c26a706
hope it helps
Click to expand...
Click to collapse
Can you tell me your android build version?
bigbiff said:
can you tell me your android build version?
Click to expand...
Click to collapse
qq3a.200605.001
just to thank you a lot bigbiff for putting so much work and efforts on this, you are great. hope you can sort this out, best luck!! (a p3 user) :fingers-crossed::good: sorry for the ot
2WildFirE said:
qq3a.200605.001
Click to expand...
Click to collapse
There was an update to the platform version, please test https://build.twrp.me/test/flame/twrp-3.4.0-0-test1-flame.img
bigbiff said:
There was an update to the platform version, please test https://build.twrp.me/test/flame/twrp-3.4.0-0-test1-flame.img
Click to expand...
Click to collapse
Thanks will try :good:
@bigbiff
yeah decryption works fine now
@bigbiff
Sorry for dump questions, but if I want to backup, is it enough to backup super and data partition?