★★★[RECOVERY] Latest TWRP 2.7.0.0 touch recovery★★★
Note : This TWRP is no longer Supported Use the Stable TWRP posted here
★★★Team Win Recovery project TWRP 2.7.0.0 Port for Canvas HD[19 March 2014]★★★
It took me nearly 20 hrs to figure out the problems occured while porting ..Hit Thanks if you really like my Work..It encourages me to do some more stuffs like this
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.
Screenshot(v2.5.0.0):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download: Latest TWRP 2.7.0.0 for Micromax Canvas HD
Download TWRP 2.6.3.0
Sources : http://yadi.sk/d/fmIOi_ee6ADpi
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
Bugs/Disabled:
1.Auto root,ADB and symbols keyboard from TWRP disabled to reduce recovery size
2.If u find any bugs..Bring it to my notice
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
Credits:Dees_Troy For base Recovery
@michfood For his Repacking Tools
@yuweng For his base recovery and help
@tEaM Win Recovery Project
@myself for porting
Changelog Of TWRP
Updatelog:
19-3-2014- Updated TWRP V2.7.0.0
6-12-2013- Fixed USB Storage Mount Option
1-12-2013- Fixed Compression Backup option
23-11-2013- Released TWRP v2.6.3.0
Changelog Of TWRP:
CHANGELOG for 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 thanks to Samer Diab
-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 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
What's new in 2.6.3.0:
Proper backup and restore of SELinux contexts (thanks to Tassadar)
Pull in some ROM information for backup name generation
Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
Add 1200x1920 theme (thanks to Tassadar)
A few other fixes and tweaks
What's new in 2.6.1.0:
Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
Initial support for f2fs file system formatting (Moto X)
Update SuperSU install for 4.3 ROMs
Fixed a permissions bug on files created during backup
Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
Ignore lost+found folder during backup and size calculations
Various other minor bug fixes and tweaks
What's new in 2.6.0.0:
Special Note: If you are running a custom theme, some of the changes in 2.6.0.0 will likely not be visible with your custom theme.
Can encrypt a backup to prevent theft of private data from your backup files
Updated graphics / icon courtesy of shift
Updated exFAT to latest commits
Fixed a problem with Samsung TouchWiz decryption
Update SuperSU binary
Fixed saving of backup partitions list
Fixed saving of last used zip install folder
Fixed backup of datadata on devices that use a separate partition for datadata
Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
Fixed some problems with partitioning a SD card
Various other bug fixes and tweaks
Looks nice. could you please port same to C4? I'm dying for one
Waiting for it!!! Can I just flash it using mobile uncle tools??
Sent from my S39h using xda app-developers app
Please make a zip file for all those who are already rooted
Many thanks!! you did it...
Wow gonna try it for sure....
---------- Post added at 10:05 PM ---------- Previous post was at 09:50 PM ----------
I knew that our loving Dev @suhas.holla will cooking something...:good::good:
Flashed using MobileUncle & flashed Fonts from Ex-Sd Card... Till now looking Perfect..
Tnks for New Recovery Bro...
Expecting more from u always....
:victory::good::fingers-crossed:
Looks cool bro keep it up..I wanna flash now
Sent from my Micromax A116 using Tapatalk
Bro, recovery always comes with .img format which is to be restored to the "Recovery" partition.
vismaiy said:
Waiting for it!!! Can I just flash it using mobile uncle tools??
Sent from my S39h using xda app-developers app
Click to expand...
Click to collapse
Yes... You can Flash it through mobile uncle tools
It seems it's missing nvram partition backup....
Sent from my S39h using xda app-developers app
suhas.holla said:
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 cwm twrp recovery.
.........................................
Click to expand...
Click to collapse
. that apart, good job, buddy!
---------- Post added at 10:56 PM ---------- Previous post was at 10:56 PM ----------
deeplyyoung said:
.....Flashed using MobileUncle & flashed Fonts from Ex-Sd Card... Till now looking Perfect.....
Click to expand...
Click to collapse
look again. new file uploaded 2013-11-23 10:30:29.
m0han said:
. that apart, good job, buddy!
---------- Post added at 10:56 PM ---------- Previous post was at 10:56 PM ----------
look again. new file uploaded 2013-11-23 10:30:29.
Click to expand...
Click to collapse
Code:
[COLOR="red"]Size: (6248448 bytes)
MD5 Sum: 29e3fe35f6a791d6cd25e46b22ea44b2[/COLOR]
Edit: MD5 Sum is same
deeplyyoung said:
previous one
MD5 Sum: 29e3fe35f6a791d6cd25e46b22ea44b2
new one
MD5 Sum: 29e3fe35f6a791d6cd25e46b22ea44b2
Click to expand...
Click to collapse
same md5?!!!!! so, have you flashed the new one too?
m0han said:
same md5?!!!!! so, have you flashed the new one too?
Click to expand...
Click to collapse
Just Chked & sorry both r same files have mentioned wrong Sz.
vismaiy said:
It seems it's missing nvram partition backup....
Sent from my S39h using xda app-developers app
Click to expand...
Click to collapse
Just uploaded the new recovery with NVRAM backup option...Download the new TWRP file and flash it
U will get nvram backup option
suhas.holla said:
Just uploaded the new recovery with NVRAM backup option...Download the new TWRP file and flash it
U will get nvram backup option
Click to expand...
Click to collapse
M on it
Edit: Flashed & found nvram partition backup...tnks
Well I downloaded the new one but I still can't find it...
Sent from my S39h using xda app-developers app
withou auto root
Twrp without auto root that was the feature that i liked most in twrp and will the old version work correctly on flashing any kind of roms?
Currently i m on TWRP 2.5
@suhas.holla Bro today have tried to take Backup using TWRP 2.6.3.0 but getting error:-
pls look into this & solve it...
Code:
[COLOR="Red"][BACKUP STARTED]
*Backup folder: /sdcard/TWRP/BACKUPS/Micromax_A116/2013-11-24--11-03-31....
E:Unable to create folder: /sdcard/TWRP/BACKUPS/Micromax_A116/2013-11-24--11-03-31....
E: Failed to make backup folder.[/COLOR]
Related
What is 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
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Changelogs
[RECOVERY][OFFICIAL] TWRP 2.6.0.0 touch recovery [2013-07-23]
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.
Phone look:
Tablet look:
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
CHANGELOG for 2.5.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.5.0.0 as your custom theme will likely not be compatible with the new changes!
-Added scrollable partition lists for mount, backup, restore, wipe, and storage selection
-Add new SliderValue GUI element for selecting brightness and screen timeout (thanks to Tassadar)
-Re-work AOSP and TWRP code to improve license compatibility between GPL and Apache
-Added official theme for 1080x1920 portrait devices (HTC One m7, HTC DNA, HTC Butterfly, Oppo Find 5, Sony Xperia Z, etc)
-Fixed a problem with directory permissions on split archive backups (backups usually restored with no app data)
-Fixed a problem with md5 verification of backups
-Added a search function to libtar (thanks to kokotas)
-Improve handling of XML errors (fix permissions)
-Fixed handling of subpartitions
-Improvements to recovery.fstab flags
-Fixed a problem with decryption not being able to locate the decryption key in some situations
CHANGELOG for 2.4.4.0:
-Added another libtar hardlink workaround to fix restore of some backups (usually related to Ubuntu Touch)
-More fixes for the file selector
-Switched from using busybox md5sum to a direct C function call
-Fixed capturing the exit status of tar based backups/restore - TWRP will display that there was an error if there was one again
-Update exFAT to latest commits
-Added a build flag to disable using the ioctl for screen blanking
CHANGELOG for 2.4.3.0:
-Fixed 2 bugs related to restore, one dealing with mknod failures (by bigbiff) and one dealing with restoring hardlinks (by Dees_Troy)
NOTE: If your backups weren't restoring correctly in earlier 2.4.x versions they should restore correctly now. Hopefully you didn't delete those backups. If you're still having problems, run the restore, go to advanced and copy log, then give us the log. Complaints without logs will be rightfully ignored.
-Added a scroll bar to file selectors and listboxes courtesy of Tassadar
-Added libblkid for more accurate detection of file systems and can now detect exFAT properly thanks to bigbiff
-Added a screen dim effect 2 seconds before screen off on some devices
-Finally fixed file selector crash (one of the joys of working with multi-threaded software)
-Fixed loading of screen timeout setting during startup
-Improvements and bugfixes to screen timeout code
-Fixed persistence of the 24 hour / military time setting
CHANGELOG for 2.4.2.0:
-Add screen timeout - screen will turn off automatically after 60 seconds, saves battery and prevents screen burn-in especially on AMOLED devices
-Add a brightness setting (requires device specific setup and only some devices have been added)
-Add a root checker and offer to install SuperSU if the device isn't already rooted
-Add a write buffer to libtar backups, significant improvements to speeds when backing up to exFAT target, minor improvements for other file systems
-Check and offer to fix root permissions if broken
-Add an option for a 24 hour clock display instead of AM/PM (aka military time)
-Move stock recovery reflash check to occur during the reboot cycle
-Add support for some MTK6xxx devices
-Change libtar to vfork to help prevent memory problems
-Add a "clicked" effect to most buttons, file selector, and listbox
-Improve timezone listbox to be more like file selector (per pixel kinetic scrolling, etc)
-Remove some no longer used settings (Forced MD5 sum on zips, size checking on image backups)
-Other minor bugfixes and improvements
CHANGELOG for 2.4.1.0:
-Fixed a problem with mkdosfs that formatted sdcards to 2GB
-Fixed handoff between vfat and exFAT on devices where blkid didn't detect vfat (fixes some issues with mounting sdcards)
-Fixed problems with changing working directory on MD5 creation/checking that may have prevented unmounting
-Backups will now store a copy of the backup log after the backup is completed (only if backup is successful)
CHANGELOG for 2.4.0.0:
-Using libtar instead of busybox's tar for better control over tar file creation and breaking the 2GB barrier that busybox imposes (thanks to bigbiff)
-Support for exFAT formatted sdcards (also thanks to bigbiff)
-Support for decrypting Samsung TouchWiz encrypted devices including internal and external storage (special thanks to a3955269 for figuring it out)
-Improvements to OpenRecoveryScript including displaying a proper GUI while the script is running
-Added wipe cache and dalvik after ADB Sideload
-Replaced many system calls with their native C counterparts
-Fixed bugs in file manager where it would display an empty list after moving or deleting a folder
-Fixed AOSP recovery commands to run after decryption on encrypted devices
-Improvements for building TWRP in CM10.1
-Other minor bugfixes and improvements
NOTE: 2.4.0.0 is, as always, still compatible with your older backups!
Click to expand...
Click to collapse
I don't have this device but I build this for this great community.
Test and report.
Also,if something doesn't work,give me a recovery log.
Downloads :
Test Build #1 - http://d-h.st/Wne
Test Build #2 - http://d-h.st/Nhf
Test Build #3 - http://d-h.st/EGP
Click to expand...
Click to collapse
Source code : https://github.com/oblikas/android_device_motorola_ghost
Credits:
@mattlgroff for his device tree
Good luck :good:
mattlgroff said:
Good luck :good:
Click to expand...
Click to collapse
Thanks mate
Can you give it a shot?
oblikas said:
Thanks mate
Can you give it a shot?
Click to expand...
Click to collapse
I would if I had a Moto X to try it out on. :fingers-crossed:
mattlgroff said:
I would if I had a Moto X to try it out on. :fingers-crossed:
Click to expand...
Click to collapse
Oh sorry,I didn't know lol
Fun fun fun! I'll try this when I get back.
Sent from my XT1058 using Tapatalk 4
hidea said:
Fun fun fun! I'll try this when I get back.
Sent from my XT1058 using Tapatalk 4
Click to expand...
Click to collapse
Nice,thanks
Flashed ok, but it just hangs on boot loader unlocked warning screen
Sent on my Moto X
flashallthetime said:
Flashed ok, but it just hangs on boot loader unlocked warning screen
Sent on my Moto X
Click to expand...
Click to collapse
can you take a last_kmsg or something?
Sent from my Nexus 4 using xda app-developers app
oblikas said:
can you take a last_kmsg or something?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Also insert your data cable in your device and see how is it recognized in device manager.
Sent from my Nexus 4 using xda app-developers app
You're going to want to read this guide on how to compile TWRP, your source code doesn't have the modified init.rc required for TWRP to even boot.
[DEV]How to compile TWRP touch recovery by Dees_Troy
mattlgroff said:
You're going to want to read this guide on how to compile TWRP, your source code doesn't have the modified init.rc required for TWRP to even boot.
[DEV]How to compile TWRP touch recovery by Dees_Troy
Click to expand...
Click to collapse
Oops,my mistake
Sent from my Nexus 4 using xda app-developers app
mattlgroff said:
You're going to want to read this guide on how to compile TWRP, your source code doesn't have the modified init.rc required for TWRP to even boot.
[DEV]How to compile TWRP touch recovery by Dees_Troy
Click to expand...
Click to collapse
Also we don't have the RECOVERY INITRC line in BoardConfig.
Sent from my Nexus 4 using xda app-developers app
oblikas said:
Also we don't have the RECOVERY INITRC line in BoardConfig.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Of course not, that's from my CWM device tree, which doesn't require an Init.rc file.
Also, be aware that TWRP does not support F2FS yet, so /data/ probably won't backup and restore without fixing it on your side or pull requesting changes to their source.
mattlgroff said:
Of course not, that's from my CWM device tree, which doesn't require an Init.rc file.
Also, be aware that TWRP does not support F2FS yet, so /data/ probably won't backup and restore without fixing it on your side or pull requesting changes to their source.
Click to expand...
Click to collapse
Also,I think the ramdisk offset is wrong,it's different in stock image.
Sent from my Nexus 4 using xda app-developers app
oblikas said:
Also,I think the ramdisk offset is wrong,it's different in stock image.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Works fine for my TWRP test?
http://batakang.com/ftp/recovery/ghost/twrp_test_touch69.img
Sent from my SGH-M919 using Tapatalk 2
New test build
Link : https://d-h.st/OZm
oblikas said:
New test build
Link : https://d-h.st/OZm
Click to expand...
Click to collapse
Give it a try again, cross my fingers and toes
Sent from my XT1058 using XDA Premium 4 mobile app
Main thread + Features + Dev support
http://forum.xda-developers.com/showthread.php?t=2201860
CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1
PhilZ Recovery is a CWM Advanced Edition that adds all the features you could ever miss in CWM.
It is a well proven recovery for many phones.
Please give your feedback, what works, and any bug you could encounter.
Read the features at the Main thread, and check if you are missing something.
To take a screen shot, just slide left!
And don't forget to read about powerful aroma file manager integration and double-tap shortcut (in FAQs).
How to install recovery?
From download link below, you'll get a 'recovery.img' file. Put that recovery.img file at root directory of your
sdcard. (means not in any folder)
Now, go to terminal emulator.
Give command:
Code:
su
You'll be asked to grant superuser permissions, grant it.
Now, give the following command:
Code:
flash_image recoveryonly /sdcard/recovery.img
Wait until it executes the command (4-5 seconds), it is installing the recovery.
Now, normally reboot to recovery and enjoy new recovery!
Download links
Latest version can be found here:
recovery.img (v6.40.1)
https://drive.google.com/uc?id=0B5c3gpyMBJusSGlpMW9UenZORW8&export=download
aromafm_galaxy5.zip (v1.91)
http://www.mediafire.com/?p5pdelpib6w8px
Click to expand...
Click to collapse
Special thanks to:
@Phil3759 : For this awesome open source recovery.
@chraso: For hosting and compatible flags.
AndroidARMv6 Team: For keeping this device alive.
Cyanogenmod Team: For making all these possible.
:FAQs:
Q: Wanna know about Aroma File manager?
Visit the aroma file manager main thread for more info---> Aroma file manager main thread
Aroma file manager is a touch file manager which can be used while in recovery. It has options for copy, paste, delete,
change permissions and many others. Also, it has a Terminal inside. So, if you forgot to give correct permissions to any
file you can do that directly from recovery. This file manager has got many themes, font, icons, etc. options and it's UI
is fully customizable.
Q: How to start this File manager in Recovery?
Rename the downloaded file to 'aromafm.zip'.
Create a folder 'aromafm' inside 'Clockworkmod' folder on your sdcard.
Now, move that 'aromafm.zip' file to the 'aromafm' folder.
We're ready now, when you want to use it in recovery just double tap anywhere OR go to "philz Settings" and select
"Aroma File Manager" and it will start up.
If you also want to browse /data, /system and /sd-ext then mount them in the "mounts & storage" option in recovery.
Q: Problems with Aroma file manager startup?
After doble-tapping OR selecting 'Aroma file Manager' option under 'philz settings' if recovery gives error: 'aromafm.zip
not found at /clockworkmod/aromafm' then, wait for 4-5 seconds and again select 'Aroma file Manager', because it maybe
busy mounting sdcard.
If still doesn't work, you've made mistakes in steps mentioned in first post, please do again carefully.
Q: Does your phone every time reboots to recovery?
This happens very rare when you flash the recovery using any bad app or via any wrong (not proper) method. What you can do
is:
-If you've made a backup of your current ROM then just restore only it's "boot" and then select 'reboot to system'.
OR
-You don't have a backup? Then just flash the ROM which you are using currently again and wipe 'dalvik-cache'. Then reboot
to system. Booting process will take time.
SCREENSHOTS:
Main menu and PhilZ Settings
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
GUI Preferences: all is applied live (no reboot). Up to 14 menu height settings, scroll sensitivity, touch accuracy...
27 color settings + 5 alpha transparency levels for every GUI element
Change background image with a custom png (of your device resolution), a solid color (27 presets) or revert to original
cwm image
User configurable touch gestures (feel free to request for new actions)
Setup your time-zone + 30mn offset, super wipe option to install a new ROM
Backup and Restore any partition in a complete freedom, include modem (.img + .bin) and efs (.img + .tar)
Custom backups can also be restored by original CWM Advanced Restore Menu
TWRP Backup and Restore Support + md5 + single/multivolume format
Support multi-cpu compression, md5 check toggle and custom .android_secure path
Choose ors backup volume target
Flash multiple zip files in a raw
Aroma File Manager + Terminal Emulator: launch with a gesture action (double tap is default)
Full Wipe to Install a new ROM (sdcard is preserved)
Free Browse Mode to install zip files: select a default folder to start with and browse up to the root
XDA:DevDB Information
PhilZ Touch Recovery : galaxy5, Tool/Utility for the Samsung Galaxy 5 I5500
Contributors
Bhargav97, chraso, Phil3759
Version Information
Status: Stable
Current Stable Version: 6.40.1
Stable Release Date: 2014-05-07
Created 2014-07-12
Last Updated 2014-07-12
Very good recovery. :good:
Everyone should check it out.
I haven't found any bugs as of now.
UPDATE:
Changelog:
-Updated PhilZ sources to 6.23.8 (26.03.2014).
-Updated androidarmv6 sources. So, you'll be able to flash cm-ota without any Signature Verification error.
Below is the recovery.img file, flash using Terminal Emulator method:
recovery.img
Need feedback. If everything is fine, I'll add it to first post.
Will work on g900t t-mobile s5
Sent from my SM-G900T using XDA Premium 4 mobile app
jpeps said:
Will work on g900t t-mobile s5
Sent from my SM-G900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Don't try it until the developer says so!
MAJOR UPDATE:
PhilZ Recovery updated to 6.27.9.
PhilZ Recovery FULL VERSION now enabled (Touch, GUI options and everything!).
CWM updated to 6.0.4.8.
Ready for official support!
I seriously want feedback on this version. If it is working, we can now get our phone in "officially supported devices" list.
Download link:
https://drive.google.com/uc?id=0B5c3gpyMBJusSGlpMW9UenZORW8&export=download
Doesn't flash for me from terminal... on i5500. Just says "flash_image not found"?
RobsX2 said:
Doesn't flash for me from terminal... on i5500. Just says "flash_image not found"?
Click to expand...
Click to collapse
Yes. Sorry to say that this method (of terminal emulator) doesn't work on Stock ROMs.
What you can do is:
-Download my recovery.img
-Search google: Make an odin flashable .tar for recovery.img
-There are many tools out there. Get one and make an odin flashable tar.
-Now flash that tar using odin and enjoy the recovery.
Bhargav97 said:
Yes. Sorry to say that this method (of terminal emulator) doesn't work on Stock ROMs.
What you can do is:
-Download my recovery.img
-Search google: Make an odin flashable .tar for recovery.img
-There are many tools out there. Get one and make an odin flashable tar.
-Now flash that tar using odin and enjoy the recovery.
Click to expand...
Click to collapse
Thank you for the fast reply.
I shall try that now and let you know how i get on.
Many thanks!
---------- Post added at 12:18 PM ---------- Previous post was at 12:00 PM ----------
Ok ive made a flashable .tar.
Tried flashing wih odin, everything went ok, but recovery does not boot.... I dont know if it worked.
I used "one package" in odin plus the ops file
EDIT: Recovery has flashed and does work. Thanks!
RobsX2 said:
Thank you for the fast reply.
I shall try that now and let you know how i get on.
Many thanks!
---------- Post added at 12:18 PM ---------- Previous post was at 12:00 PM ----------
Ok ive made a flashable .tar.
Tried flashing wih odin, everything went ok, but recovery does not boot.... I dont know if it worked.
I used "one package" in odin plus the ops file
Click to expand...
Click to collapse
Then there is another simple solution.
-Install any CWM recovery (through ODIN).
-Now download any zip file of cwm recovery (use madteam.co if you don't find at xda).
-Open the zip and replace the recovery.img inside with this (PhilZ Recovery) one.
-Now, flash this modified zip file with the current cwm recovery (which you installed using odin).
hi again
ok now ive just tried flashing bluedroidmod, went through the flash fine, clicked reboot. I know get a blac screen that just says "android" in the middle of the screen and nothing else happens.. Do you know what could have gone wrong?
RobsX2 said:
hi again
ok now ive just tried flashing bluedroidmod, went through the flash fine, clicked reboot. I know get a blac screen that just says "android" in the middle of the screen and nothing else happens.. Do you know what could have gone wrong?
Click to expand...
Click to collapse
Have you done all the wipes?
Vagelis1608 said:
Have you done all the wipes?
Click to expand...
Click to collapse
Yessir
RobsX2 said:
Yessir
Click to expand...
Click to collapse
Did you pulled the battery to turn the device off when it hunged (at the "Android" screen)?
Have you tried booting up again?
Also, contact me via PM so that I will help you fix the issue. Let's not spam this thread .
UPDATE:
Updated PhilZ Touch sources to 6.40.1.
Fixed the misbehaviour of hardware keys in the new full version recovery.
In this version, I especially need feedback on:
-Hardkeys. Test all of them if they are correctly working or not.
-Change the 'Menu Background' to 'PhilZ Default' and 'Koush Default' (from PhilZ Settings > GUI options > Menu Background) and tell me if which of them is working. (ofcourse, reboot recovery after changing the background)
Download link:
https://drive.google.com/file/d/0B5c3gpyMBJuseDJ5VDZBeTlmQ2M/edit?usp=sharing
deleted
Bhargav97 said:
UPDATE:
Updated PhilZ Touch sources to 6.40.1.
Fixed the misbehaviour of hardware keys in the new full version recovery.
In this version, I especially need feedback on:
-Hardkeys. Test all of them if they are correctly working or not.
-Change the 'Menu Background' to 'PhilZ Default' and 'Koush Default' (from PhilZ Settings > GUI options > Menu Background) and tell me if which of them is working. (ofcourse, reboot recovery after changing the background)
Download link:
https://drive.google.com/file/d/0B5c3gpyMBJuseDJ5VDZBeTlmQ2M/edit?usp=sharing
Click to expand...
Click to collapse
ALL HARDKEYS WOORK FINE!
I just have one doubt.
When i reset to "Koush default" it gave me a netted grey background..
Whereas :"Philz default" gave a complete black background..
Is this supposed to happen.
Maybe I am too stupid
But where is on goo.im the PhilzTouch for this little jewel called galaxy5?
wrong post
TWRP 3.0.0 has now been released for all devices that are currently supported and comes packed full of new features and a completely new look.
changes included in version 3.0.0 are:
True Terminal Emulator – Includes arrow keys, tab and tab completion, etc. (by _that)
Language translation – Languages that require large font files like Chinese & Japanese won’t be available on most devices. Some languages may only be partially translated at this time. Translations are welcome over at OmniROM’s Gerrit. (mostly by Dees_Troy)
Flashing of sparse images – On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
Adopted storage support for select devices – TWRP can now decrypt adopted storage partitions from Marshmallow
Reworked graphics to bring us more up to date with AOSP – includes support for adf and drm graphics (by Dees_Troy)
SuperSU prompt will no longer display if a Marshmallow ROM is installed
Update exfat, exfat fuse, dosfstools (by mdmower)
Update AOSP base to 6.0
Many, many minor fixes and tweaks
ScreenShots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Requirements: Rooted Phone with MobileUncle Tools Installed
How to Flash:
1. Download TWRP 3.0.0 from below given link.
2. Rename it "recovery.img" without " ".
3. Paste the recovery in root of your internal stoarge i.e. outside all folders.
3. Install Mobileuncle Tools from Play Store.
4. In Mobileuncle Tools click on "Recovery Update" It will show recovery.img file on top under Recovery Card in SD Card Title.
5. Select it, phone will ask "Are you sure Flash Recovery" Click yes.
6. Grant SuperUser permisssions if ask.
7. Again it will ask to Reboot in Recovery mode. Click ok.
All Done!!!
Enjoy TWRP 3.0.0
Download Links::
1. TWRP 3.0.0
2. MobileUncle Tools (Play Store)
puns546 said:
TWRP 3.0.0 has now been released for all devices that are currently supported and comes packed full of new features and a completely new look.
changes included in version 3.0.0 are:
True Terminal Emulator – Includes arrow keys, tab and tab completion, etc. (by _that)
Language translation – Languages that require large font files like Chinese & Japanese won’t be available on most devices. Some languages may only be partially translated at this time. Translations are welcome over at OmniROM’s Gerrit. (mostly by Dees_Troy)
Flashing of sparse images – On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
Adopted storage support for select devices – TWRP can now decrypt adopted storage partitions from Marshmallow
Reworked graphics to bring us more up to date with AOSP – includes support for adf and drm graphics (by Dees_Troy)
SuperSU prompt will no longer display if a Marshmallow ROM is installed
Update exfat, exfat fuse, dosfstools (by mdmower)
Update AOSP base to 6.0
Many, many minor fixes and tweaks
ScreenShots:
Requirements: Rooted Phone with MobileUncle Tools Installed
How to Flash:
1. Download TWRP 3.0.0 from below given link.
2. Rename it "recovery.img" without " ".
3. Paste the recovery in root of your internal stoarge i.e. outside all folders.
3. Install Mobileuncle Tools from Play Store.
4. In Mobileuncle Tools click on "Recovery Update" It will show recovery.img file on top under Recovery Card in SD Card Title.
5. Select it, phone will ask "Are you sure Flash Recovery" Click yes.
6. Grant SuperUser permisssions if ask.
7. Again it will ask to Reboot in Recovery mode. Click ok.
All Done!!!
Enjoy TWRP 3.0.0
Download Links::
1. TWRP 3.0.0
2. MobileUncle Tools (Play Store)
Click to expand...
Click to collapse
Unable to restore backups. Thn tried after wiping restore successful but mobile stuck at "starting apps"
Thn did a fresh install of rom and made new backup. Same issue after restoring. Mobile just keeps loading on starting apps screen. Cm12.1. A311
Sahilsinghlodhi said:
Unable to restore backups. Thn tried after wiping restore successful but mobile stuck at "starting apps"
Thn did a fresh install of rom and made new backup. Same issue after restoring. Mobile just keeps loading on starting apps screen. Cm12.1. A311
Click to expand...
Click to collapse
Hi bro. The recovery has been tested by one of my friend on A311, but he flash a kk based rom. We have not tested it on cm based rom. Flash a KK based rom.. sorry for the inconvenience. I'll post the a311 recovery separately if any such issue is found
Edit : go in mount and mark system, data , cache (everything) then Reboot
installed as you said bro but still it shows twrp version 2.8.6
any help mate
puns546 said:
Hi bro. The recovery has been tested by one of my friend on A311, but he flash a kk based rom. We have not tested it on cm based rom. Flash a KK based rom.. sorry for the inconvenience. I'll post the a311 recovery separately if any such issue is found
Edit : go in mount and mark system, data , cache (everything) then Reboot
Click to expand...
Click to collapse
Yeah i'll try stock rom later today on nitro.
---------- Post added at 04:43 AM ---------- Previous post was at 04:42 AM ----------
karthik4 said:
installed as you said bro but still it shows twrp version 2.8.6
any help mate
Click to expand...
Click to collapse
Try toolhero.
karthik4 said:
installed as you said bro but still it shows twrp version 2.8.6
any help mate
Click to expand...
Click to collapse
Put in internal sd not in external
Sahilsinghlodhi said:
Yeah i'll try stock rom later today on nitro.
.
Click to expand...
Click to collapse
Also for cm roms try unmounting data then Reboot.
I flashed it as instructed ..I think everything is fine .Was using twrp 2.8.7.0 material design before this ...Iam Using CM12.1
Thanks for the recovery
puns546 said:
Put in internal sd not in external
Also for cm roms try unmounting data then Reboot.
Click to expand...
Click to collapse
Bro still same issue on canvas nitro a311 stock rom.
When I restore it without wiping it get stuck on restoring system. And if restore after wiping data and system the phone's not starting. Stuck on optimizing apps screen.
Sahilsinghlodhi said:
Bro still same issue on canvas nitro a311 stock rom.
When I restore it without wiping it get stuck on restoring system. And if restore after wiping data and system the phone's not starting. Stuck on optimizing apps screen.
Click to expand...
Click to collapse
Dont use then. I'll post separate recovery for A311. Till then use old recoevry
puns546 said:
Dont use then. I'll post separate recovery for A311. Till then use old recoevry
Click to expand...
Click to collapse
Yeah! Thanks.
Didnt works for Himax Polymer Octa...
Blank dark screen, then just boot to normal
Bro @puns546 ...Any Updates On 3.0 Recovery ..
..Installation Worked Fine..But Can't Able to Flash Any ROM zip..Error Is Coming.. As u Said 3.0 is Just Tested in KK ROM ., & Not Tested On CM12.1 ROMs ..Any Updates On CM ROMs ? ..
Sent using XDA One
LoverBoy2415 said:
Bro @puns546 ...Any Updates On 3.0 Recovery ..
..Installation Worked Fine..But Can't Able to Flash Any ROM zip..Error Is Coming.. As u Said 3.0 is Just Tested in KK ROM ., & Not Tested On CM12.1 ROMs ..Any Updates On CM ROMs ? ..
Sent using XDA One
Click to expand...
Click to collapse
Sorry but I cannot provide support for this as I am busy in my job interviews.
puns546 said:
Sorry but I cannot provide support for this as I am busy in my job interviews.
Click to expand...
Click to collapse
No Prob Brother..Just Asked Any Updates for This ..& All The Best For Your Job Brother ..
Sent Using Tapatalk
Closed at OP's request. He is unable to provide support or keep this updated...
TWRP RECOVERY FOR GALAXY J7 PRIME
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DO THIS AT YOUR OWN RISK. I AND XDA AND NOT RESPONSIBLE FOR BRICKS. FOLLOW THE STEPS CORRECTLY.
WARNING: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
What's new in 3.1.0-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
Instructions:
Flash with ODIN in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOADS:
twrp3.1.0-0
Use Odin to flash.
You can find a zip containing Odin as well as a link to Samsung's Mobile drivers page here:
https://idlekernel.com/flash-tools/
IMPORTANT! This device enforces dm-verity. ANY modifications or even mounting system will put the device into a bootloop. To prevent this TWRP will ask at first boot to if you want to keep system 'Read only' or 'Allow modifications to system'. If you choose to keep 'Read only' you will have to flash TWRP at every boot to recovery. If you choose to 'Allow' then SuperSU needs to be flashed to disable dm-verity.
To Root:
Flash the latest SuperSU:
http://www.supersu.com/download#zip
To disable forced encryption, mount internal storage(DATA) and disable dm-verity:
(Note this MUST be flashed before SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install modded kernel from below.
5. Reboot
Modded Kernel:
https://mega.nz/#!tJ5XVa4I!_kMCzV7kOMvEdvJwB3ZUDPZjGUNIuuzK6RSLHMiZG4M (Thanks to maxx35000)
NOTE: NO NEED TO FLASH MODDED KERNEL IF YOU ARE USING ANY CUSTOM ROM
HIT THANKS IF I HELPED YOU:good:
is this oficial ?
Mounting internal is working?
Not work on last update from samsung, with update AQC4 recovery not incompatible
Janeslejade said:
Mounting internal is working?
Click to expand...
Click to collapse
Yes. Read the thread on how to do this.
hoangphuc057 said:
Not work on last update from samsung, with update AQC4 recovery not incompatible
Click to expand...
Click to collapse
It's working. I'm on AQC4
Not working on G610Y.
---------- Post added at 09:23 AM ---------- Previous post was at 09:11 AM ----------
Guys, i want to go back to stock recovery, questions.... Is it safe to flash this stock recovery??
SM-G610F/M_stock_recovery
My unit is G610Y.
Up... Please help, i need the SM-G610Y_stock_recovery... Please someone help or advise if SM-G610F/M_stock_recovery is okay to flash on G610Y??
Help guys! I tried to root my phone but no success. It says need adb 1.3 or newer. What should i do?
External sd mounting?
Thanks for the update, working on G610M
4. Install modded kernel from below.
Click to expand...
Click to collapse
how to do this?
Ephesis said:
how to do this?
Click to expand...
Click to collapse
Flash through odin in AP
Siddhant NAik said:
Flash through odin in AP
Click to expand...
Click to collapse
how about rooting? flash via odin too?
---------- Post added at 09:52 AM ---------- Previous post was at 09:40 AM ----------
Flash through odin in AP
Click to expand...
Click to collapse
Odin wont read it since its a zip file not a tor file.
inamie said:
External sd mounting?
Click to expand...
Click to collapse
This is the essential question!
thank
trinaldi said:
This is the essential question!
Click to expand...
Click to collapse
not working.
Anyone tried this on G6100 ?
Please update aqc4 mod kernel
Thank you bro. Haha :d :d
With this tool is possible resize the system partition.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Precautions and warnings:
This procedure will erase your ROM. Internal storage will also be erased, including photos, videos, music and backups.
Increasing the size of the system will decrease the internal storage in the same proportion, when using previous backup consider this, if the backup is too large it may not fit in the new partitioning.
To prevent bootloop, use a permanent installation of TWRP, do not use temporary boot.
I am not responsible for bricked devices or dead SD cards.
Use at your own risk
Instructions:
Part 1
1- Copy zip installer to external SD card, otherwise installation will be canceled. do not forget to also copy the custom rom and the gapps.
2- The installer uses Aroma ui, it is possible to choose several size for the system partition: 1GB, 1.25GB, 1.5GB, 1.75GB, 2GB, 2.25GB and 2.5GB.
3- Optionally it is possible to create a new partition, the vendor partition, it is required in the project treble and only used with treble roms and vendor partition compatible with Redmi 2.
4- The installer also creates a backup of some changed partitions and restores them automatically, a copy(110MB) is sent to the external SD card if an emergency restore is required.
5- After choosing all the options select Start, if all the requirements have been fulfilled the repartitioning will happen, otherwise it will be interrupted before any alteration. Then press the Reboot button to end.
Part 2
The most recent rom installer comes with the system inside an image file, it has the default size, and after installing the rom it is necessary to expand the file system so that it can see the new size.
This can be done with Twrp in the wipe advaced menu, but to make it easier I did an additional installer to do this task.
So summarizing:
1- Install 1Resize-System-Redmi2.zip (only when changing system size partition).
2- install your Custom-Rom.zip
3- install 3Expand-filesystem-Redmi2.zip (always required after installing custom rom and before gapps, this releases new size to use).
4- install gapps.zip
5- done !
Thanks the creators of content, for sharing knowledge:
@jsidney96 thread, @freeshared thread, @mirfatif thread, @osm0sis thread, @amarullz thread
.
Sorry my English.
.
[update]
v1.01: added reboot(recovery) after installation.
v1.03: (experimental) added option to create vendor partition and auxiliary zip installer.
Looks very cool! Have you heard of @Lanchon's RePIT? Similar idea but without the GUI. Perhaps you guys could collaborate? https://forum.xda-developers.com/android/software-hacking/tool-lanchon-repit-data-sparing-t3358036
Edit: sorry it did not work. only the internal storage got reduced but the system partition remained the same.
log file attached below.
interesting
athish said:
Edit: sorry it did not work. only the internal storage got reduced but the system partition remained the same.
log file attached below.
Click to expand...
Click to collapse
Edit 2: So i was able to re-partition the system using the above script (i mean the script works). But after i installed lineageos 15.1 the system partition returned back to 1gb. Can anyone give me a solution for this? i tried the resize system after rom install but it failed. :crying:
screenshots below:
athish said:
Edit 2: So i was able to re-partition the system using the above script (i mean the script works). But after i installed lineageos 15.1 the system partition returned back to 1gb. Can anyone give me a solution for this? i tried the resize system after rom install but it failed. :crying:
screenshots below:
Click to expand...
Click to collapse
With me it works, but twrp only displays new size after exiting the wipe menu.
Then return to the main menu and enter the wipe menu again.
Error message appears if you press the "resize file system" button twice in a row.
Cecell3000 said:
With me it works, but twrp only displays new size after exiting the wipe menu.
Then return to the main menu and enter the wipe menu again.
Error message appears if you press the "resize file system" button twice in a row.
Click to expand...
Click to collapse
nope i press the "resize file system" only once and still gives the error.
can please explain what to do after installing a ROM (to get back the full size). And thank you for the making a zip installer:good:
Edit:
So after re-partiton of system to 2gb, i restored twrp backup and system remained 2gb :victory: :highfive:
@Cecell3000 Flash EDL mode rom miui, restores partition size?????????
xander21 said:
@Cecell3000 Flash EDL mode rom miui, restores partition size?????????
Click to expand...
Click to collapse
yes, edl / fastboot restore partition size.
But prefer reinstall the zip file by selecting (default) option.
Cecell3000 said:
yes, edl / fastboot restore partition size.
But prefer reinstall the zip file by selecting (default) option.
Click to expand...
Click to collapse
Im reinstall partition zip file and flash fastboot Rom. It can be like this?
xander21 said:
Im reinstall partition zip file and flash fastboot Rom. It can be like this?
Click to expand...
Click to collapse
yes, it's safer.
[update]
v1.01: added reboot(recovery) after installation.
v1.03: (experimental) added option to create vendor partition for project treble and auxiliary zip installer.
summary installation instructions:
1- Install 1Resize-System-Redmi2.zip (only when changing system size partition).
2- install your Custom-Rom.zip
3- install 3Expand-filesystem-Redmi2.zip (always required after installing custom rom and before gapps, this releases new size to use).
4- install gapps.zip
5- done !
Cecell3000 said:
With this tool is possible resize the system partition.
The installer uses Aroma ui
Click to expand...
Click to collapse
Is it possible to use this to only use Aroma's Remove stock apps functionality, without having to download and install the full Aroma? Can it be done without reinstalling/wiping the rom?
intresting
Where can I download this apps for other mobiles?
I need it for the Xiaomi Mi8.
Is it compatible?
Can I flash other ROMs such as Xiaom.eu if I have resized the partitions ?
Thanks
---------- Post added at 01:05 AM ---------- Previous post was at 12:58 AM ----------
What about resizing the data and cache partitions?
What partition is the culprit of the error of insuficient size when installing new apps?
Once resized will it remain 2gb forever or will it revert back to 1 gb as soon as I flash a custom rom?
I want to flash treble rom and then android p gsi files. So I need the vendor partition right?
thanks, it works for me
Which twrp to use to flash this installer?
hengkidermawan said:
thanks, it works for me
Click to expand...
Click to collapse
you can record on video? pleasee!!
Christian - Cuba said:
you can record on video? pleasee!!
Click to expand...
Click to collapse
the OP says clearly, bro..
1- Install 1Resize-System-Redmi2.zip (only when changing system size partition).
2- install your Custom-Rom.zip
3- install 3Expand-filesystem-Redmi2.zip (always required after installing custom rom and before gapps, this releases new size to use).
4- install gapps.zip
5- done !
---------- Post added at 03:27 PM ---------- Previous post was at 03:24 PM ----------
Paleskin said:
Which twrp to use to flash this installer?
Click to expand...
Click to collapse
the latest twrp, and the important thing is permanent twrp that OP said