Database Info

[RECOVERY][TOUCH] TeamWin Recovery Project (TWRP) 2.3.2.1 [UPDATE!]

{
"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"
}
Are you tired of scrolling through huge lists of files in ClockworkMod with the volume rocker?
Don't you wish there was a recovery with a graphical interface and controlled using the touchscreen?
Team Win Recovery is just that!
Built by TeamWin from the ground up based on AOSP recovery, it has a themeable GUI with touch interface, file manager, keyboard, terminal emulator and much much more...
NEW VERSION 2.3.2.1!
Note: A few devices experience random reboots/shutdowns in recovery with the latest version. If this is the case for you, use version 2.2.1 which is completely stable.
Features
Graphical touchscreen interface with buttons and drag-to-scroll!
Compressed backups that can save you up to 50% disk space
Ability to choose which partitions to back up and which to restore
Custom names for backups, rename and delete backups inside recovery
Integrated Terminal Emulator
Install queues allow you to install multiple zips in one go (e.g. CM9 zip together with gapps zip)
Easy one-button cache & dalvik cache clearing after an installation
Recovery settings are saved to the sdcard and persist through reboots
File Manager that allows you to move, copy, delete and rename files and change their permissions
Battery percentage indicator, charging indicator and clock (set your timezone in settings!)
Reboot into download mode (bootloader)
ADB support
Sideloading for automated ROM install: http://teamw.in/ADBSideload
Detailed logfile
Themeable
Download
2.3.2.1 as installable zip
http://www.mediafire.com/?6i91q2lvez9bj9p
Click to expand...
Click to collapse
Install by copying the zip file to your sdcard, booting into recovery (VolumeUp+Power) and then using "install zip from sdcard" ("apply update form sdcard" on stock recovery) to install it.
2.3.2.1 as flashable image file
http://www.mediafire.com/?ji7z7yznh25zjjp
Click to expand...
Click to collapse
Flash using broodplank's Quickflasher. Connect phone via USB, start sgsflasher_x86.exe, activate "Flash a new Recovery", select the twrp2.2.1-recovery.img and press "Start Now".
Please pay particular attention to this:
Some zips may no longer work in TWRP 2.3 if the developer is using an out-of-date update-binary. If this is a problem for you, please use TWRP 2.2.1 (download link in post below)! Zips can be fixed by replacing their old update-binary with this one.
Click to expand...
Click to collapse
FAQ
I installed this but my phone keeps booting into recovery over and over again.
You need to re-flash your bootloader as described here.
Click to expand...
Click to collapse
Can I use TWRP to restore my CWM backups?
No. The only way is to convert your uploads like this: flash CWM, restore a backup, flash TWRP, create new backup, repeat.
Click to expand...
Click to collapse
Where is my external SD card?
The external SD is under /emmc (as is standard for all CyanogenMod-based ROMs). The internal SD is under /sdcard.
Click to expand...
Click to collapse
What is the size vs speed tradeoff for compressed backups?
For my test, compression shrunk the total backup size by 43% and took 1.4 times longer.
Click to expand...
Click to collapse
Can I use this to flash CyanogenMod9?
Yes!
Click to expand...
Click to collapse
Can I use this to flash XYZ ROM?
Yes!
Click to expand...
Click to collapse
The clock shows the wrong time!
You need to set your timezone under Settings -> Time Zone. The setting is saved in a config file on your sd card so you only have to do this once.
Click to expand...
Click to collapse
My .zip file won't install!
Turn off signature verification!
Click to expand...
Click to collapse
Can I mount my SD cards on my PC in recovery?
Yes, but only one at a time. Go into the Mount menu and select which card to mount with the "Use external SD" or "Use internal storage" radio buttons. Connect your USB cable and press "Mount USB storage".
Click to expand...
Click to collapse
How can I restore single apps (and/or their data) from a TWRP backup?
Use TitaniumBackup, it supports TWRP! In Titanium Backup, open up the menu and select "Extract from Nandroid backup...". It will list all your TWRP and CWM backups and allow you to restore as many apps and their data as you want.
Even though all TWRP backup files carry the extension .win, they are either tar archives or filesystem images. System, data, cache and .android_secure are backed up as tar archives or gnu-zipped tar archives if compression is enabled. You can rename those .win files to .tar (.tar.gz if compressed) and extract them like a regular archive. Boot and recovery partitions are backed up as .img files using dd.
Click to expand...
Click to collapse
I have tried to test all recovery features and they all seem to work. I successfully flashed several different ROMs and performed backups and restores. However, there could still be bugs lurking somewhere - if you find one please report it!
Screenshots
Credits
TeamWin - Everything here is their work, I only provide a precompiled binary for our device. Particular thanks to Dees_Troy from TeamWin for his help.
arco - For the config files for our device.
Disclaimer
Do not install this if you don't know what you are doing. Incorrect flashing of a recovery can lead to a hard brick! Bugs in the recovery could result in data loss so always have a backup! I am in no way responsible for anything you do to your phone and offer no guarantees.
For Developers
TWRP has an optional companion app called GooManager. It offers a frontend for the goo.im archive which hosts ROMs and the gapps. Unlike CWM and ROM Manager, it is completely free, developers can upload their ROMs to goo.im and users can easily flash them with GooManager. It would be awesome if developers started uploading their ROMs there!
To take screenshots inside the running recovery, use adb to dump the framebuffer and then use ffmpeg to convert the raw image to a jpeg like this:
adb pull /dev/graphics/fb0
ffmpeg -vframes 1 -vcodec rawvideo -f rawvideo -pix_fmt rgba -s 480x800 -i fb0 -f image2 -vcodec mjpeg fb%d.jpg
Click to expand...
Click to collapse
Sources:
- TWRP2 github
- arco github with BoardConfig.mk etc. for I9001/ariesve
- Configuration parameters for TWRP in BoardConfig.mk:
Code:
DEVICE_RESOLUTION := 480x800
TW_INTERNAL_STORAGE_PATH := "/sdcard"
TW_INTERNAL_STORAGE_MOUNT_POINT := "sdcard"
TW_EXTERNAL_STORAGE_PATH := "/external_sd"
TW_EXTERNAL_STORAGE_MOUNT_POINT := "external_sd"
TW_DEFAULT_EXTERNAL_STORAGE := true
TW_FLASH_FROM_STORAGE := true
This is a straight, unmodified compile of TWRP2 sources. TWRP2 is made available under the Apache License 2.0.

Over 27000 downloads as of November 17th! Rock on!
Changelog:
2.3.2.1
- Small bugfixes
2.3.1.1
- Fixed keyboard not working for backup rename bug
2.3.0.3
- Faster boot
- Much faster permission repair
- Charging indicator (only updates once a minute)
- Major code rewrite to C++ and Jelly Bean base
- ADB Sideload functionality - for automated ROM installs, see http://teamw.in/ADBSideload
- USB storage mounting now mounts both internal and external sd cards simultaneously
2.2.1
- Small bugfixes
- Trying to fix the random shutdown bug that happens on some devices
2.2.0
- Integrated Keyboard
- Set custom backup name
- Terminal emulator
- Rename files in file manager
- Set file permissions using octal notation in file manager
- Rename and delete backups
- Restore menu has switch for internal/external SD
- Fixed timezone names
- Wipe external SD option
- Wipe battery stats and rotation data options removed (Google says it's unnecessary. You can still do it manually/with apps if you want.)
- Fixed themes not loading bug
2.1.8-fix
- Fixed USB storage mounting
2.1.8
- Initial release for the Galaxy S Plus
Old Downloads:
2.3.1.1 as installable zip
http://www.mediafire.com/?l78dskdap2xghd7
2.3.1.1 as flashable image file
http://www.mediafire.com/?hhqmgmqq3a37q7s
2.3.0.3 as installable zip
http://www.mediafire.com/?ld9iupspojsdmq2
2.3.0.3 as flashable image file
http://www.mediafire.com/?zqwou2f353n945p
2.2.1 as installable zip
http://www.mediafire.com/?0ufe8dcv5kkajay
2.2.1 as flashable image file
http://www.mediafire.com/?aknf6rjpxj16wrv
2.2.0 as installable zip
http://www.mediafire.com/?6nb6clnwn9w1247
2.2.0 as flashable image file
http://www.mediafire.com/?7afs5n39nbkop22
2.1.8 as installable zip
http://www.mediafire.com/?9bh66rw6uqbt9tm
2.1.8 as flashable image file
http://www.mediafire.com/?km077vhodky7rsb

Cm9 compatible ?

UpGado said:
Cm9 compatible ?
Click to expand...
Click to collapse
Yes!

no problem in cm9？ example.. wifi .BT....because arco recovery fixed some problem in cm9
Sent from my GT-I9001 using XDA

Ezekiel1998 said:
no problem in cm9？ example.. wifi .BT....because arco recovery fixed some problem in cm9
Click to expand...
Click to collapse
This is a Recovery, not a ROM!
A recovery is a small bootable operating system on a seperate partition on your device. Changing your recovery does not in any way affect your running system. And when booted in the recovery you don't have access to WiFi or Bluetooth anyway.
The reason FeaMod does not work with CM9 is because it was compiled with a wrong list of partition sizes. I compiled this using arco's CM9 repository, so it has exactly the same settings, kernel config etc. as the CM9-compatible CWM that arco compiled.

looks awssum shall try flashing an xperimental.zip
Sent from my GT-I9001 using Tapatalk 2

Is this somewhat related to cmw touch recovery ?

Awsome work!!!
Sent from my GT-I9001 using XDA

In restore it is showing nothing....can anybody else confirm it?
Sent from my GT-I9001 using Tapatalk 2

You must make a backup with teamwin recovery. Maybe you can copy your CWM Backup into the Teamwin recovery folder for restore your backup.
Sorry for my english.
Gesendet von meinem GT-I9001 mit Tapatalk

Awesome thanks for your work
Sent from my GT-I9001 using Tapatalk

wow...nice recovery... thanks for your work!!

This is RECOVERY it has nothing to do with any of the ROMS !!! RESTORING BACKUP from other RECOVERIES is not recommended, it will end up bricking your phone! NEVER RESTORE BACKUP WITH DIFFERENT VERSIONS OF RECOVERY, EVEN IF IT IS MADE FROM SAME SOURCE.
RECOVERY cannot be "compatible" or "incompatible" with ANY of ROM distro's.
Restoring someone's nandbackup (CM9 with arco recovery, for example) on own phone is other story.

BzArEx said:
Is this somewhat related to cmw touch recovery ?
Click to expand...
Click to collapse
No, it was developed from scratch by TeamWin. It is also open source and completely free unlike CWM touch which you have to buy.
You can read more at the official project website: http://teamw.in/project/twrp2

F**k the system . AMAZING WORK!!!!!!

Yay!
Awesome work! I was waiting for a touch recovery!
btw, can we flash CWM over this afterwards, just in case i want to restore a CWM backup later on?

Awesome work bro....
Sent from my GT-I9001 using xda premium

sidsweb said:
btw, can we flash CWM over this afterwards, just in case i want to restore a CWM backup later on?
Click to expand...
Click to collapse
Yes, you can change recoveries without a problem.
For arco's CWM flash this zip file and then reboot the recovery. Later in CWM you can just flash the TWRP zip, reboot recovery and you're in TeamWin Recovery again.
This is also how I suggest people migrate their backups (if really necessary): Install and reboot into CWM, restore a CWM backup, install and reboot into TWRP, perform a backup, repeat.

Works great, just installed Arcos build 4 with your Recovery.
Awesome!

CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1

CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1
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://docs.google.com/uc?id=0B5c3gpyMBJusXzRMMG1tLUxRMWM&export=download
aromafm_beni.zip (v1.91)
https://drive.google.com/uc?id=0B5c3gpyMBJusc204SHRZdTBucHc&export=download
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.
XDA:DevDB Information
PhilZ Touch Recovery for Galaxy Fit, Tool/Utility for the Samsung Galaxy Fit GT 5670
Contributors
Bhargav97, chraso, Phil3759
Version Information
Status: Stable
Current Stable Version: 6.40.1
Stable Release Date: 2014-05-04
Created 2014-05-07
Last Updated 2014-05-07

: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.

NEW: Now you can enjoy the full version of the recovery! Thanks to @Phil3759 for uploading necessary
commits for armv6. And, everything is expected to be bug-free. Please report the bug here if you find any.
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

i tried your recovery by creating a zip update
you should work more on it because the graphic in some aroma installer or aroma file manager doesnt work too good!
and just feels the normal CWM and not Philz recovery !
But any way, Good Job!

Rminsh said:
i tried your recovery by creating a zip update
you should work more on it because the graphic in some aroma installer or aroma file manager doesnt work too good!
and just feels the normal CWM and not Philz recovery !
But any way, Good Job!
Click to expand...
Click to collapse
Aroma File Manager has no LDPI resources. If you want it for LDPI, you can do it, it's an Artist's work. I'm not gonna do it.
Please read the first post carefully. It has no GUI options: So, no themes and all that.
It's not at all like normal CWM in terms of functions. It has got many important functions, atleast for me.
Most important part:
I've worked on this advanced only version for 20-25 days already and made it fully stable.
And...I've worked for almost 2 months on FULL VERSION. Discussed a lot with Phil3759 and finally came to conclusion that it won't work on armv6 unless it's (libtouch_gui) specially compiled for armv6, Which Phil3759 didn't have time and resources for.
So, Be happy with this recovery. No one can give you better philz recovery than this, atleast at present.

Installed your recovery.
Selected clean install ROM option.
Installed a ROM.
Selected Reboot System.
Phone rebooted into your recovery.
Tried various ROMS all rebooted into your recovery and not to the newly installed ROM.
Flashed CWM 6.0.4.6 and installed a ROM and rebooted to installed ROM successfully.
Any ideas what is wrong?
I do like the Aroma FM.
jemail

jemail said:
Installed your recovery.
Selected clean install ROM option.
Installed a ROM.
Selected Reboot System.
Phone rebooted into your recovery.
Tried various ROMS all rebooted into your recovery and not to the newly installed ROM.
Flashed CWM 6.0.4.6 and installed a ROM and rebooted to installed ROM successfully.
Any ideas what is wrong?
I do like the Aroma FM.
jemail
Click to expand...
Click to collapse
Yep...you're correct.
It won't boot into system.
I finally figured out that it is a problem in androidarmv6 sources. You can see change #6205 if you want.
It was maybe fixed just 4-5 days ago by androidmeda and I'll be again making the recovery and give you all for testing.
This is not only problem of your device but it is also there in: tass, gio and beni.

Bhargav97 said:
Aroma File Manager has no LDPI resources. If you want it for LDPI, you can do it, it's an Artist's work. I'm not gonna do it.
Please read the first post carefully. It has no GUI options: So, no themes and all that.
It's not at all like normal CWM in terms of functions. It has got many important functions, atleast for me.
Most important part:
I've worked on this advanced only version for 20-25 days already and made it fully stable.
And...I've worked for almost 2 months on FULL VERSION. Discussed a lot with Phil3759 and finally came to conclusion that it won't work on armv6 unless it's (libtouch_gui) specially compiled for armv6, Which Phil3759 didn't have time and resources for.
So, Be happy with this recovery. No one can give you better philz recovery than this, atleast at present.
Click to expand...
Click to collapse
i read that!
pay attention: the aroma that use in every CWM works fine
but in your recovery it has a bad graphic and kind of blue!
i mean before you create this Philz recovery we had a older version that works perfect!
http://forum.xda-developers.com/showthread.php?t=2483327

Rminsh said:
i read that!
pay attention: the aroma that use in every CWM works fine
but in your recovery it has a bad graphic and kind of blue!
i mean before you create this Philz recovery we had a older version that works perfect!
http://forum.xda-developers.com/showthread.php?t=2483327
Click to expand...
Click to collapse
It works perfect just in the sense: It reboots to system successfully. It lacks Aroma file manager also. And, Aroma file manager with that original green colour doesn't come with armv6 sources nor it will come if you download from original thread.
I'll be fixing reboot to system soon.
That recovery doesn't even have Touch, GUI options and all that.

UPDATE:
-Updated PhilZ sources to 6.23.9 (26.03.2014).
-CM-OTA compatibility fixes.
-Reboot to system bug fixed.
Download link updated in first post.

Bhargav97 said:
UPDATE:
-Updated PhilZ sources to 6.23.9 (26.03.2014).
-CM-OTA compatibility fixes.
-Reboot to system bug fixed.
Download link updated in first post.
Click to expand...
Click to collapse
Thanks for this.
Reboot system is working
Aroma File manager is working
I will test and report any bugs if find them.
Does this version reformat ext4 partitions as ext3 when doing a restore?
jemail

jemail said:
Thanks for this.
Reboot system is working
Aroma File manager is working
I will test and report any bugs if find them.
Does this version reformat ext4 partitions as ext3 when doing a restore?
jemail
Click to expand...
Click to collapse
It reformates the partition to the state in which it was in your backup file. The working of this PhilZ Recovery will be the same way as your CWM 6.0.4.7 works. Nothing different except features.

Tested, worked fine with aroma file manager. Flashed cm 11 has no error.
Keep your work
Here is temporary flashable zip file

As I reported previously in another Clockworkmod thread here, this version also does not restore SD-Ext Ext4 formatted partitions correctly. SD-Ext Ext4 partitions are restored as Ext3 not Ext4.
You can verify this by
1. Create an Ext4 partition on your sdcard using MiniTool Partition Wizard.
2. In CWM create a nandroid backup.
3. Immediatley restore the backup.
4. Check sdcard partition structure in MiniTool Partition Wizard, you will find the partition you created as Ext4 is now reported as Ext3.
Can you confirm this?
Can you remove all background images from your release, maybe except the ClockworkMod Logo. Background images make reading the output from operations difficult.
jemail

jemail said:
As I reported previously in another Clockworkmod thread here, this version also does not restore SD-Ext Ext4 formatted partitions correctly. SD-Ext Ext4 partitions are restored as Ext3 not Ext4.
You can verify this by
1. Create an Ext4 partition on your sdcard using MiniTool Partition Wizard.
2. In CWM create a nandroid backup.
3. Immediatley restore the backup.
4. Check sdcard partition structure in MiniTool Partition Wizard, you will find the partition you created as Ext4 is now reported as Ext3.
Can you confirm this?
Can you remove all background images from your release, maybe except the ClockworkMod Logo. Background images make reading the output from operations difficult.
jemail
Click to expand...
Click to collapse
1) I don't have your device but in my Galaxy 5 it works fine. I make backup (have an sd-ext and has some stuff also inside) and then restore it and everything is still fine. Link2sd still detects it as ext4. Even if it's a bug, it is not related to my PhilZ Recovery but to the androidarmv6 sources and I maybe can't do anything for it (don't have time to submit a patch for review...maybe I don't have that expertise too).
2) Which logo you mean? The one with Big Green Android? I would prefer to keep it that way...don't wanna make it lean more towards an unofficial build. However, I won't be able to do it (even if I want to) right now because my PC is busy and I can't compile on it right now.
Once I get my PC free, I'll make TWRP for your device and provide a final (final for some time) update for PhilZ Recovery (less probability though for PhilZ update).

When I was flashing a rom with aroma (miui v4 to be precise) its showed me get.prop errors.
Saying that my device is not beni and not 5670
And this happened only on this recovery and only with roms with aroma installer, rest of the roms work fine.
And for the TWRP version, TWRP cannot flash memory scripts (like cronmod's int2ext)
Can something be done for that?

Harpratap said:
When I was flashing a rom with aroma (miui v4 to be precise) its showed me get.prop errors.
Saying that my device is not beni and not 5670
And this happened only on this recovery and only with roms with aroma installer, rest of the roms work fine.
And for the TWRP version, TWRP cannot flash memory scripts (like cronmod's int2ext)
Can something be done for that?
Click to expand...
Click to collapse
Aroma installer's dev OR miui rom's dev is lazy to update the update-binary. KitKat requires new update-binary because Google changed the way getprop worked uptil Jellybean.
TWRP? I don't think I've made a TWRP for Galaxy Fit yet.
I wanna tell you only one thing: You are using everything from latest KK branch: PhilZ Recovery and TWRP (maybe you're talking about the one of Galaxy Mini), so please take some time to read on: What all Google changed in recovery with KitKat. Your int-ext script is suffering from old update-binary for sure.

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/file/d/0B5c3gpyMBJusVmZUN2UxdHFtaWs/edit?usp=sharing

Awesome!
All gui and touch functions work properly.
Flashed a zip and everything works fine except reboot system and power off.
Both of them simply reboot into recovery.
Will report other bugs if found.
And nice job :good:

A little bug. Fixed it.
https://drive.google.com/file/d/0B5c3gpyMBJusSk41Q002c3lneUk/edit?usp=sharing
Give me feedback. Everything else like: screenshot double-tap shortcut for aroma fm (read first two posts to understand), GUI options, etc are especially needed for testing. Post some screenshots also.

[RECOVERY][GUIDE][i9305]--CWM/PHILZ/TWRP latest versions+Odin v3.09 Guide--25-04-2016

Here are the latest versions of the most popular recovery's for our device
----------------------------------------------------------------------------------------------------------
FLASHABLE RECOVERY'S TO USE WITH ODIN OR CUSTOM RECOVERY
----------------------------------------------------------------------------------------------------------
CWM:
● Recovery flashable: Cwm recovery touch 6.0.4.7 ---> here
● Odin flashable: Cwm recovery touch 6.0.4.7 ---> here
-----------------------------------------------------------------------------------------------------
PHILZ:
Compiled by Pheoxy:
● Recovery flashable: Philz recovery touch 6.59.0 ---> here
● Odin flashable: Philz recovery touch 6.59.0 ---> here
Changelog ---> here
--------------------------------------------------
● Recovery flashable: Philz recovery touch 6.48.4 ---> here
● Odin flashable: Philz recovery touch 6.48.4 ---> here
Official Philz thread ---> here
Older versions:
● Recovery flashable: Philz recovery touch 6.48.1 by JustArchi ---> here
● Odin flashable: Philz recovery touch 6.48.1 by JustArchi ---> here
-----------------------------------------------------------------------------------------------------
TWRP:
Compiled by SdtBarbarossa:
● Recovery flashable: Twrp openrecovery homebuild 2.8.7.0 - v1.6 ---> here
● Odin flashable: Twrp openrecovery homebuild 2.8.7.0 - v1.6 ---> here
--------------------------------------------------
● Recovery flashable: Twrp openrecovery 3.0.2-1 F2FS ---> here
● Odin flashable: Twrp openrecovery 3.0.2-1 F2FS ---> here
● Recovery flashable: Twrp openrecovery 3.0.2-0 ---> here
● Odin flashable: Twrp openrecovery 3.0.2-0 ---> here
Older versions:
● Recovery flashable: Twrp openrecovery 3.0.1-0 ---> here
● Odin flashable: Twrp openrecovery 3.0.1-0 ---> here
● Recovery flashable: Twrp openrecovery 3.0.0-0 ---> here
● Odin flashable: Twrp openrecovery 3.0.0-0 ---> here
● Recovery flashable: Twrp openrecovery 2.8.7.3 ---> here
● Odin flashable: Twrp openrecovery 2.8.7.3 ---> here
● Recovery flashable: Twrp openrecovery 2.8.5.0 ---> here
● Odin flashable: Twrp openrecovery 2.8.5.0 ---> here
● Recovery flashable: Twrp openrecovery 2.7.0.0 ---> here
● Odin flashable: Twrp openrecovery 2.7.0.0 ---> here
● Recovery flashable: Twrp openrecovery 2.6.3.0 ---> here
● Odin flashable: Twrp openrecovery 2.6.3.0 ---> here
----------------------------------------------------------------------------------------------------------------------------------------------------
Note: no need to unpack anything from the archives above for flashing with Odin, just select it in AP and flash
----------------------------------------------------------------------------------------------------------------------------------------------------
Latest ODIN flashtool for Samsung Mobile Phones:
● Flash with ODIN ---> download latest View attachment 3472321
● For official samsung firmware downloads go here OR here you need to create an account if you want to download from sammobile!
Latest Samsung usb drivers for Windows:
● View attachment SAMSUNG_USB_Driver_for_Mobile_Phones_1.5.51.0.zip
Installation: 1. uninstall previous driver via control panel / 2. reboot pc / 3. install new driver / 4. reboot pc / 5. done
CF-Auto-Root:
● I9305 - View attachment CF-Auto-Root-m3-m3zh-gti9305.tar.zip
● I9305T - View attachment CF-Auto-Root-m3-m3dv-gti9305t.tar.zip
● I9305N - View attachment CF-Auto-Root-m3-m3swexx-gti9305n.tar.zip
● View attachment Superuser.apk v2.65 ---> for more info and changelog see SuperSU thread
Noob friendly guide for rooting / flashing custom recovery / flashing official samsung firmware with odin
IMPORTANT: you cant blame me if you do screw things up with your device! all these instructions are based on my own experience only with my i9305 LTE. i cant guarantee that this will work with every samsung galaxy device there is! but on most of them it should work. you need to do your own research for odin compatibility and or instructions on how to flash if they differ from these steps below!
IMPORTANT!!!!: fellow i9305 users! if you have never flashed android 4.3 and above before and you are on 4.1.2 or older, you have the old bootloader without KNOX, which is good :good: but if you do flash 4.3 and above stock official you will get new bootloader with KNOX and we all know that sucks!! so flash only stock 4.1.2 if you dont want the new KNOX bootloader!! more info about KNOX here
NOTE: these 3 operations --> rooting / flashing custom recovery / flashing official samsung firmware should be done separately, you cant do all 3 at the same time !! if you need to perform all 3 operations, the logical flashing order would be like this: 1st. official samsung firmware / 2nd. rooting / 3th. custom recovery
NOTE: please ensure that samsung KIES software is not running in the background while using Odin, because KIES and ODIN dont go along!
NOTE: these instructions can be performed for other samsung galaxy devices as well, using the device specific files ofcourse
ATTENTION: warranty will be void hereby!! steps to root device / flash custom recovery / flash official samsung firmware in this order:
1. download Odin3 v3.09 from the link above and unzip, then right click odin3 v3.09 and ''open as administrator'' on your pc
2. download CF auto root / custom recovery / official samsung firmware from the links above and extract/unzip where needed to get .tar md5 file
3. in Odin, in the ''option'' section you should check the boxes of auto reboot / f. reset time and uncheck re-partition!!
4. enable usb debugging in your device in developer options, if you dont see developer options, go to ''about phone'' and tap the buildnumber 7 times and developer options should be visible now (this part is not strictly necessary, just in case if your device is not recognized by pc or odin. generally it is recommended to enable usb debugging with file transfers between device and pc)
5. turn off device now, and put it in odin downloadmode by pressing and holding VOLUME DOWN - HOME - POWER buttons at the same time till you see the black screen with white ''samsung galaxy sIII GT-i9305'' text, then you let go the buttons, now press VOLUME UP and it will boot into downloadmode
6. in odin, click AP button and select the CF auto root / custom recovery / official samsung firmware .tar md5 file that you have extracted/unzipped earlier (in odin under message box, it should say blablabla.tar md5 file is valid!)
7. now connect your i9305 to pc with usb cable (in odin under message box, it should say added!)
8. now your ready to hit START button, after finished (in odin under message box, it should say removed!) your device will reboot and will be rooted / installed custom recovery / installed official samsung firmware in the left upper corner you should see a green box saying PASS, you can disconnect from pc now
This is how you boot into recovery to check it after you have flashed/installed it: press and hold VOLUME UP - HOME - POWER buttons at the same time till you see the black screen with white ''samsung galaxy sIII GT-i9305'' text, then you let go the buttons and it will boot into recovery
To make sure you are rooted, download root checker app from playstore
After rooting, there is a chance that after reboot some message like ''supersu has stopped'' will popup, DONT worry read further...
After you have rooted the device, there will be a app called ''SuperSU'' among your apps, but its a older version of the app and its ''SU binary'' needs to be updated. go to playstore and under my apps search for supersu, it should state that it needs to be updated, do that and restart your phone. you can also flash this UPDATE-SuperSU-v2.65-20151226141550.zip in your recovery if you prefer so, both do the same. Configure the settings of supersu after the reboot as you like. for those who got the KNOX bootloader, while updating SU binary, supersu should ask you to deactivate KNOX, just accept and proceed
Congratulations that's all !!
Useful info and important tips for flashing with Odin or your recovery:
- first of all, dont flash any custom rom/stock firmware/custom recovery/custom kernel other then what is made specifically for our i9305!
- it is generally recommended to make a nandroid backup in recovery before taking any action!
- before using odin, make sure your device has at least 50-60% battery level. why? because, if your phone goes off suddenly while installing a custom ROM, flashing an official firmware update or installing mods etc. your phone might get bricked or go dead permanently. no one wants that, right?
- flashing ONLY official stock firmware will not raise the flash counter! and you will not void warranty
- do NOT turn your device off or pull the battery while flashing!!
- any problems, try these few things: update usb drivers, and restart your pc; different cables; different usb ports. other solutions may include redownloading the file
- full .tar md5 files are very large and can take as long as 15 minutes to complete. smaller files such as recoveries normally only takes 10 to 20 seconds
- if you are currently rooted and intend to flash a stock firmware, you will loose root!
- always READ instructions carefully! RESEARCH before posting your questions! refer to i9305 Q&A thread for questions and answers / additional info / assistance, if you need to...
Steps in pictures:
{
"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"
}
ODIN buttons explanation:
BL refers to the bootloader
AP refers to the build version of the software/firmware
CP refers to the baseband/modem version
CSC is the consumer software customisation and is specific to geographical region and carriers. it contains the software packages specific to that region, carrier branding and also APN settings for data connection, MMS etc for your service provider
CSC has nothing to do with what languages the firmware supports and it will not add keyboard language support either
PIT refers to the Partition Information Table you only need it if you screw up your partition table or if the firmware specifically requires it because of a change in the partition table layout. its very likely you may never have to use this, at least i hope so however KEEP IN MIND there is a HIGH chance of bricking your device with a bad partition table if you do this wrong!! dont forget to check the box re-partition if youre gonna use it! Thanks @lyriquidperfection for the pit file here
if the package only contains one .tar md5 file then it will have everything, AP+BL+CSC+CP, in one file
a stock firmware downloaded from sammobile or samsung updates will contain all of these in one .tar md5 file
if it has multiple .tar md5 files then:
the .tar md5 with modem/CP in the name is the phone/baseband part of the package
the .tar md5 with CSC/multi-csc in the name is the csc part of the package
the .tar md5 with code/AP in the name is the AP part of the firmware package
the .tar md5 with BL in the name is the bootloader part of the package
if this is the case you will need to put these .tar md5 files in the specific areas of odin to flash the update/stock rom
Step 5.
I am and will not be responsible for any kind of damage to your device, flash at your own risk !!!
All credit and thanks goes to @Chainfire - @Dees_Troy - @Phil3759 - @JustArchi - @Pheoxy - @SdtBarbarossa Thanks a LOT !!

Does TWRP still has a bug with backups?

peniu said:
Does TWRP still has a bug with backups?
Click to expand...
Click to collapse
I dont use twrp so i dont know, however i think since this is the latest version it should be fixed if there is a bug like youre saying
Try it out and find out for your self..
Sent from my GT-I9305 using XDA Premium 4 mobile app

works, but lacking in options make copies recovery. so if it is to be bugs?
Wysłane z mojego GT-I9305 przy użyciu Tapatalka

Personally i recommend cwm
Sent from my GT-I9305 using XDA Premium 4 mobile app

hi there
i've got a question why CWM Touch 6.0.4.7 is not a "zip" file? Then how to flash it in recovery mode...?
thanks

queer~dude said:
i've got a question why CWM Touch 6.0.4.7 is not a "zip" file? Then how to flash it in recovery mode...?
thanks
Click to expand...
Click to collapse
you have to flash it with odin. download odin from OP
if you dont know how to use odin then google about it..

Isn't CWM 6.0.4.7 the version built for CyanogenMod ??
I'd personally still leave a link for the original 6.0.2,9 because not all CWM .zip files work with the newer version.
I've personally used TWRP for a long time now and it just got better with the app they released to go alongside it (search for TWRP on google play)

djb77 said:
Isn't CWM 6.0.4.7 the version built for CyanogenMod ??
I'd personally still leave a link for the original 6.0.2,9 because not all CWM .zip files work with the newer version.
I've personally used TWRP for a long time now and it just got better with the app they released to go alongside it (search for TWRP on google play)
Click to expand...
Click to collapse
this one is the original release, not all are the version build for CM. im sure it will work for most of the peeps here
ive been using cwm now for some time, working top!

Updated Philz touch CWM advanced edition to 6.25.0 !!

philz touch 6.26.6 !!

Philz touch 6.41.6!
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9305

chongc1996 said:
Philz touch 6.41.6!
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9305
Click to expand...
Click to collapse
haha i forgot all about this thread which i created good finding chong :good:

nice look on Philz Touch Recovery...but does it work with CM11 based ROM's or is still useless?
CWM worked perfect every damn time.

spiderman07 said:
nice look on Philz Touch Recovery...but does it work with CM11 based ROM's or is still useless?
CWM worked perfect every damn time.
Click to expand...
Click to collapse
of course works mate, works with me every damn time :laugh:

Question, on my Note n7000 i have CWM 6.0.4.8 and it's rather nice in the way that the touch works. It's not touch enabled like Philz, the screen acts more like a touchpad.
You swipe up for up, down for down. It's not one swipe, one slot, it's more like scroll, like the touch device on the N1, or the original Desire.
You swipe right for "Enter", left for back.
Can we have this?

daedric said:
Question, on my Note n7000 i have CWM 6.0.4.8 and it's rather nice in the way that the touch works. It's not touch enabled like Philz, the screen acts more like a touchpad.
You swipe up for up, down for down. It's not one swipe, one slot, it's more like scroll, like the touch device on the N1, or the original Desire.
You swipe right for "Enter", left for back.
Can we have this?
Click to expand...
Click to collapse
would like to help you, but im no developer nor im a programmer, you could ask a dev. to do this

time to update.. SuperSu v1.99 !

Bump

Could you guys explain why you prefer each recovery ? I prefer TWRP because it's more ergonomic and easy to use , you can select multi Zip flashing , the "format /system" is in wipe settings , you can do multiple wipes in one click , it's a true time gain

Xolo Q3000 - recovery collection

XOLO Q3000 RECOVERY COLLECTION​
Hiii All XOLO Q3000 users,
I bring to you collection of recoveries for our beloved XOLO Q3000.
STOCK RECOVERY​
Jelly Bean
JB 4.2.1 S003
JB 4.2.1 S011
KitKat
Kitkat 4.4.2 S007 version
======================================================================================================
CUSTOM RECOVERY FOR ANDROID JELLY BEAN​
Carliv Touch Recovery BASED​
Carliv Touch Recovery v2.1
Carliv Touch Recovery v2.2
Carliv Touch Recovery v2.4
Carliv Touch Recovery v2.5
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​ClockworkMod- CWM- BASED​
CWM 5.5.0.4
CWM 6.0.2.8
CWM 6.0.3.2
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​TeamWin Projects - TWRP BASED​
TWRP 2.7.1.0
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​PhilZ Touch - TWRP BASED​
PhilZ Touch 6.4.7.7
====================================================================================================​
CUSTOM RECOVERY FOR ANDROID KITKAT​
ClockworkMod- CWM- BASED​CWM based 6.0.2.8
ClockworkMod 6.0.3.3 Recovery (CWM) Non-touch
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​
Carliv Non-Touch Recovery BASED​
Modified Carliv CWM (non-touch) CWM 6.0.4.4
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​
Carliv Touch Recovery BASED​
Carliv Touch recovery 3.0
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​
PhilZ Touch BASED​[CWM Advanced Edition] PhilZ Touch 6.56.2 - cwm 6.0.5.0
[CWM Advanced Edition] PhilZ Touch 6.56.2 - cwm 6.0.5.0 aroma fixed
[CWM Advanced Edition] PhilZ Touch 6.576.9 - cwm 6.0.5.1
[CWM Advanced Edition] PhilZ Touch 6.576.9 - cwm 6.0.5.1 aroma fixed
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​
TeamWin Projects - TWRP BASED​
TWRP 2.7.0.0
TWRP 2.8.0.0
TWRP 2.8.1.0
TWRP 2.8.2.0
TWRP 2.8.4.0
TWRP 2.8.4.0 rev 2
TWRP 2.8.5.0
====================================================================================================​
So dont get confused which one to use from all above.
THE BEST CUSTOM RECOVERY​
For JELLY BEAN ​Carliv Touch Recovery v2.5
For KitKat- use anyone​
[CWM Advanced Edition] PhilZ Touch 6.576.9 - cwm 6.0.5.1
TWRP 2.8.5.0
Test and report.
If you have any other working recovery please PM me.
HOW TO USE/FLASH CUSTOM RECOVERY.​
CREDITS​Credit goes to all involved in making them. (CWM team, TWRP team, PhilZ team, Carliv,yuweng)
hadiyalkishan- for JB & KK stock & testing
m0han - for ctr 2.5, for JB testing
rufus.reynolds - for KK testing
Jagadish-ravi - for JB & KK testing
vijay jay - for TWRP 2.7 testing
@Santhosh M - for TWRP 2.8.1.0
Thank You... Share Your Views...​

Many users dont know how to flash a custom recovery.
so i am making this thread which will guide u to flash a custom recoveries present in above thread.
​
If ur phone is rooted (supersu/superuser app is present in app drawer).
Method 1
Download and install flashify app from playstore
download custom recovery from above post.
Open flashify.
Backup current recovery.
{
"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"
}
goto flash
recovery image
Choose downloaded recovery.img (it may have different name)
Now u can reboot.
To boot into recovery
press vol up button, keep it pressed.
press power on button till u see boot logo.
release power button.
after going into recovery release vol up button.
Method 2
Mobile uncle tool
1. Download Mobileuncle Tools APK.
2. Install the apk.
3. Copy the recovery.img extracted from to the sdcard.
4. Run MobileUncle Tools
5. Click on "Recovery Update".
6. You will see recovery.img on top. Install it.
7. Use MobileUncle to reboot into recovery..
If ur phone is not rooted
What's needed:
USB data cable
MediaTek USB VCOM drivers thanks to @smokerman sir
SP Flash Tool
First of all, make sure that you have MediaTek DA USB VCOM drivers installed.
Install spflash tools
download recovery.
rename it to recovery.img
download scatter file.
Put scatter file and recovery image in same folder.
open SP Flash Tool, then click Scatter-loading button to load the scatter file
(MT6589_Android_scatter_emmc.txt) and ignore any message that may appear.
The tool will immediately show a warning because not all parts are selected, but you should continue anyway. Safely press Yes to continue.
Press download button.
attach ur switched off phone with usb cable.
The download of the chosen partition image will start and after the yellow bar is complete, the popup with the green circle should appear.
Attention: Please follow the instructions carefully. I will not take any responsibility on whatever may happen with your phone.
PLEASE PRESS THANKS BUTTON IF THIS HELPS​

This just keeps getting better and better.....thanks millions....Avi....well collated recovery thread.....its has everything we need....

Thanks for this post, man. I'll try the Stock Recovery for the OTA I've been getting since months. Because I've read somewhere that OTA only works on Stock recoveries.
Edit: The Stock recoveries here are S003 and S011. Mine is S009. Which one should I try?
Sent from my Q3000 using XDA Premium 4 mobile app

Vineet3 said:
Thanks for this post, man. I'll try the Stock Recovery for the OTA I've been getting since months. Because I've read somewhere that OTA only works on Stock recoveries.
Edit: The Stock recoveries here are S003 and S011. Mine is S009. Which one should I try?
Sent from my Q3000 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Save ur recovery and try S011.:good:

CTR 2.5 can be used to flash both JB & KK ROMs.
but backup & restore is not possible.
Thanks to @Jagadish-ravi

stuck at download mode
i have kitkat 4.4.2, Kernel 3.4.67, software version s003_15072014, non-rooted
i have installed mtk vcom, sp flash and tried to port cwm, but sp flash tool used to stuck at download mode....any help?
i have attached the screeshot for the reference....
Thanks in advance...

Sagar_Patel said:
i have kitkat 4.4.2, Kernel 3.4.67, software version s003_15072014, non-rooted
i have installed mtk vcom, sp flash and tried to port cwm, but sp flash tool used to stuck at download mode....any help?
i have attached the screeshot for the reference....
Thanks in advance...
Click to expand...
Click to collapse
First thing is
Please dont quote whole post.
it is posted by me only and just few post above on same page.
Ur screenshot is very poor cant see anything please re upload with good resolution.
after pressing that download button u need to connect ur phone in switched off condition.
r u doing this as instructed.??
Please explain the process ur following?
Ur porting cwm means??
Or u mean to say flashing/installing??
which cwm ur using please specify.?

ow! sorry for the way i had posted the thing but thanks for the way you replied- it was quite Quick!!
so, herewith i have attached the zip file (for the better resolution) and jpg file as well (size i could manage within the limitation of this forum) of screenshot where i stuck...View attachment 083.zip
yes, i connected my phone in switched off condition after pressing download button...
i had followed exactly the same way as you have explained for the non-rooted device....
and it was newbie thing that i had written "porting cwm" instead of "installing/flashing cwm"...yes, i was trying to flash/install cwm...
recovery i tried to install is:- [CWM Advanced Edition] PhilZ Touch 6.56.2 - cwm 6.0.5.0
Thanks for helping me...

sorry i had just forgotten to mention the scatter file i had used....obviously yes, it is the same as you have uploaded as:-
avi3230 said:
Install spflash tools
download recovery.
rename it to recovery.img
download scatter file.
Put scatter file and recovery image in same folder.
open SP Flash Tool, then click Scatter-loading button to load the scatter file
(MT6589_Android_scatter_emmc.txt) and ignore any message that may appear.
Click to expand...
Click to collapse
however, i had to rename it as MT6589_Android_scatter_emmc.txt as the scatter file i had downloaded had have the name as attachment.php
also note that i had put zip file of recovery [CWM Advanced Edition] PhilZ Touch 6.56.2 - cwm 6.0.5.0 and that scatter file in same folder as well....
kindly check if i had done any mistake there...
i have attached the scatter file to which i had renamed...

sp flash tool stuck at download mode?
ok may be i have found the mistake while posting just above the procedure i had done!!!
sp flash tool stuck at the download mode may be because i had done mistake (if it is?! ok, i cant confirm it until i can get xolo q3000 back to me or until someone here can confirm that yes, this was the mistake) as below:_
i had downloaded zip file of recovery
then i had downloaded scatter file of xolo q3000 as mentioned in my previous post
i had renamed the scatter file i had downloaded as MT6589_Android_scatter_emmc.txt as the scatter file i had downloaded had have the name as attachment.php (may be silly newbie thing here!!!)
i had put both those files in same folder
and did rest of the procedure as mentioned by avi3230 (OP) here in same thread for non-rooted xolo q3000 just a few posts above...
...and what should i have done?
i should have downloaded only the zip file of desired recovery and then if i extracted it, i could find that there are all the necessary files including recovery.img and scatter_file within the extracted folder!!!
i would like to attach screenshot of wrong thing i had done:- image named as "wrong"
and what i should have done is may be here:- image named as "may be"
i think i was trying to install zip file instead of recovery.img that should be there in extracted folder of recovery.zip along with the scatter_file as well...so, here now i have got where and why i had confused
Put scatter file and recovery image in same folder.
Click to expand...
Click to collapse
ok, if zip file of recovery has properly zipped, has properly downloaded and if it has properly extracted then you should find both the recovery.img and scatter_file within extracted folder....if not so, then you should put (get together) the scatter file and recovery image in "same folder" means in extracted folder....
confused? then i can only say sorry for my english but why i had posted the whole thing here? may be because someone can find that what kind of silly things those can be done by newbies....and if so, they can help....

Sagar_Patel said:
ok may be i have found the mistake while posting just above the procedure i had done!!!
.
Click to expand...
Click to collapse
OK dont worry about ur English or anything wrong u doing.
just follow these steps
this is considering ur running kitkat on ur phone (S003 or S007 build no)
download
1. SP_Flash_Tool
2. philz recovery - this or this
3. drivers - from here
extract drivers folder- mtkusball 0.9.2
open smartphone driver folder - x86/x64 according to ur windows os and install drivers.
or just select from autoinstall folder
connect ur phone in switch off condition to pc.
when asked fro drivers use MT65xx preloader drivers.
when u connect switched on phone and if asked for drivers use - android winusb drivers.
(please check in device manager after connecting ur phone in each case whether drivers are installed or any red triangle is ther)
restart ur computer.
extract sp tools in folder
extract philz recovery in a folder (it is in 7z or rar format just extratc in folder in winrar)
in philz folder u have scatter file, recovery.img boot.img and lk,bin files
start sp flash tools
select scatter loading
select scatter file from philz folder
deselect uboot and bootimg
press download button
connect ur switched off phone to usb cable.
flashing will be done
confirmed by green circle.
boot in recovery by pressing power + vol up button.
Reply if any issues.

avi3230 said:
OK dont worry about ur English or anything.....
....Reply if any issues.
Click to expand...
Click to collapse
just to add.... tip1: use usbdeview (g00gle) to remove all usb devices before adding your mobile device.
tip2 (based on my experience): try a previous (older) clean version of w!nd0ws also before giving up.

avi3230 said:
TeamWin Projects - TWRP BASED
TWRP 2.7.1.0
PhilZ Touch - TWRP BASED
PhilZ Touch 6.4.7.7
THE BEST CUSTOM RECOVERY
For JB
Carliv Touch Recovery v2.5
For KK
[CWM Advanced Edition] PhilZ Touch 6.56.2 - cwm 6.0.5.0
Click to expand...
Click to collapse
please do a twrp that'd work flawlessly on both jb & kk. thanks.
i suppose you're aware of this.

m0han said:
please do a twrp that'd work flawlessly on both jb & kk. thanks.
i suppose you're aware of this.
Click to expand...
Click to collapse
Yeah already seen that no support for philz now.
TWRP is bigger in size and u need to change partition size of recovery.
which is another headache for TWRP.
I already have it but again u need to flash whole stock rom again as whole
preloader boot recovery will change.

avi3230 said:
....TWRP is bigger in size and u need to change partition size of recovery.....
....I already have it but again u need to flash whole stock rom again as whole preloader boot recovery will change.
Click to expand...
Click to collapse
is it fully working on both bases - jb and kk? does it allow jb/kk rom switching? what are the drawbacks of flashing whole stock rom again?
what if we make full backup of data (call log/sms/mms/dictionary etc.) and also apps+apps-data using my backup app......
....... - can those be restored in the new setup and be up & running? if so, i don't foresee much troubles. do you?
you being much more experienced, please elaborate. thanks.

m0han said:
is it fully working on both bases - jb and kk? does it allow jb/kk rom switching? what are the drawbacks of flashing whole stock rom again?
what if we make full backup of data (call log/sms/mms/dictionary etc.) and also apps+apps-data using my backup app......
....... - can those be restored in the new setup and be up & running? if so, i don't foresee much troubles. do you?
you being much more experienced, please elaborate. thanks.
Click to expand...
Click to collapse
As TWRP is larger in size most of the time it wont boot in recovery.
also backing up of recovery wont work on 7mb recovery partition in any cwm based recovery.
So i feel we should stick to philz.

avi3230 said:
.....i feel we should stick to philz.
Click to expand...
Click to collapse
just in case you haven't seen this yet. this too.
wish you (or someone else) can do some magic!

m0han said:
just in case you haven't seen this yet. this too.
wish you (or someone else) can do some magic!
Click to expand...
Click to collapse
I already have twrp made for device which is easy.
its size is more than 6mb which is the issue.
u can change size of recovery to almost 11mb but then it wont boot in recovery specifically on 6589 chipsets. then whats t use.
to make it boot in recovery we need to change values in preloader.bin which is difficult task.
if anyone working on ubuntu please make an kernel with drivers files from this source.
if using this kernel twrp is less than 6mb then everything will be fine.

[RECOVERY][N9005] CWM, PhilZ, TWRP Materialized - Dark / Light / Play

TWRP Recovery
{
"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"
}
DISCLAIMER
Code:
/*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
Features
Recovery gone App: Designed to mimic the look and feel of an Android app.
Customisable UI: 15 different accent colors, center clock option, different navbar button layouts...
Added functionality: ability to flash image files (recovery, radio, boot), ability to change the recovery splash screen, bookmark function for file lists, Aroma File Manager support, theme changer...
Availability and Compatibility
Supported TWRP versions: 2.8.7.X.
Supported screen resolutions: 1080x1920 (Note 3).
The theme stays compatible with new versions of TWRP until TWRP changelog says otherwise.
DOWNLOAD:
TWRP 2.8.7.0 (N9005)
TWRP Themes and Splashes
SCREENSHOTS
Don't get confused as Recovery version in Screenshots is 2.8.0.0. This is because these themes are also available for other version of TWRP here.
SPECIAL THANKS
@z31s1g for all of his Work.
@TWRP for their Recovery.
INFO
Original Thread
Code:
What’s new in 2.8.7.0:
Initial ground work for software drawn keyboard (_that)
Fix handling of wiping internal storage on datamedia devices (xuefer)
Allow DataManager to set and read values from the system properties (xuefer)
Fix crash when taking screenshots on arm64 devices (xuefer)
Fix error message after an ORS script completes (Dees_Troy)
Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
Add system read only option – more details below (Dees_Troy)
Add resize2fs and GUI option to run resize2fs (Dees_Troy)
Fix crash loop caused by empty lines in AOSP recovery command file (_that)
Prevent duplicate page overlays such as multiple lock screens (mdmower)

How to
Install Recovery:
Simply flash the .tar file by odin.
OR
Extract the recovery.img file from .tar file and flash it using Flashify.
Install the theme:
The theme zips are not flashable. First installation has to be done manually:
Download the theme of your choice and rename it to "ui.zip".
On SD card (if device has internal and external storage, use the internal) open TWRP folder and create a folder called "theme", without capital letters.
Copy ui.zip to theme folder.
Restart to recovery.
Change the theme:
In Materialised settings, select CHANGE THEME.
Select the theme zip you want to use.
Confirm the change.
Remove the theme:
In Materialised settings, select the delete icon on the app bar.
Confirm the removal.
Alternatively, delete the ui.zip from /sdcard/TWRP/theme with a file explorer.
Change the recovery splash screen
In order to change the splash, one must unpack the recovery image, replace the splash and then repack the image.
General prerequisites:
Make sure the splash screen you want to use is in .jpg format and matches your screen resolution (e.g. 1920x1080).
Download a stock TWRP recovery image for your device.
Samsung users have to download .img files or pull them from the .tar files. Repacking .tar files won't work.
Change the splash while in recovery:
Download the AIK-Mobile-Installer.
Flash the AIK zip in recovery.
This will install the required scripts and binaries to \data\local\AIK-mobile.
In Materialised settings, select CHANGE SPLASH.
Select the stock TWRP .img file.
Select the .jpg file you want to use as splash screen.
Set options:
Make Sure
If Automatically install... is unchecked, the repack will only be created and saved to the same folder as the stock TWRP image.
If checked, the repacked recovery will also be installed on your device.
If Include current theme... is checked, the theme in its current state (accent color) will be included in the repack, replacing the stock TWRP ui.
The ui.zip will automatically be deleted from /sdcard/TWRP/theme, as it is no longer required.
Be aware that changing the accent color won't be possible with an integrated theme.
In general, I'd recommend to not include the theme into the repack. By keeping the ui.zip, there's always the stock ui as a fallback option in case there's something wrong with the theme.
Start repacking/flashing with a swipe.
During the process, Repacking in progress... will be shown.
Install image files while in recovery:
The theme currently utilises the Flashify script by @osm0sis to install boot, radio and recovery images.
The script comes with the theme and will automatically be installed to /sdcard/TWRP/flashify if required.
On the Install page, tap on Install Zip.
Select Install Image.
Select the .img file you want to flash.
Select the image type.
This selection determines the target partition. Make sure not to flash a radio.img to the boot partition...
Start flashing with a swipe.
Use the AROMA File Manager:
AROMA File Manager is not part of the theme.
The theme just contains a "shortcut" for directly starting AROMA FM, rather than going through the "install > flash zip" procedure.
Download this Flashable zip.
Flash the zip in recovery.
This will copy the Aroma FM package to \TWRP\aromafm.
In Materialised settings, tick the option to use Aroma FM.
From the main menu, the theme will now start Aroma FM instead of the TWRP file manager.
Resolve common issues
When I reboot to recovery, the theme isn't applied. Any ideas?
This is most likeley due to wrong naming of the theme folder or the ui.zip.
Make sure the folder is named "theme", without capital letters.
Also check if you accidentally renamed the downloaded zip to "ui.zip.zip" (common pitfall when renaming the zip in windows explorer).
When I reboot to recovery, I get a "recovery bootloop". Is my phone broken?
Nope, this is most likeley due to a bad download.
Please download the theme again using another browser or app.

PhilZ Recovery
PhilZ Touch 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.
It also adds a full touch interface a completely configurable GUI.
Download
PhilZ 6.48.4 (N9005)
PhilZ 6.48.4 (Flashible via Recovery)
How to
Install Recovery:
Simply flash the .tar file by odin.
OR
Extract the recovery.img file from .tar file and flash it using Flashify.
CWM Recovery
ClockworkMod Recovery (CWM) is a replacement recovery option for Android devices, made by Koushik "Koush" Dutta. It is based on the Android 2.1 (Eclair) recovery image (updated to Kitkat and Lollipop). Features include Nandroid backup, adb shell, advanced update.zip options (ignore asserts and signature checks), and file browser for choosing update.zips
Download
CWM 6.0.4.7 (N9005)
How to
Install Recovery:
Simply flash the .tar file by odin.
OR
Extract the recovery.img file from .tar file and flash it using Flashify.
SPECIAL THANKS
@Phil3759 for Philz Recovery
@xiaolu

Very good works now i try it
Inviato dal mio SM-N9005 utilizzando Tapatalk

Nice mate !

somebody upload a Video Review and Guide to install Themes and Splashes so i include it in OP as some users will definitely ask for it

Cool....first ever :good:

Hi !
Very nice and work !
Existing for philz recovery ?
Thanx !

stootie said:
Hi !
Very nice and work !
Existing for philz recovery ?
Thanx !
Click to expand...
Click to collapse
FYI: philz and CWM does not support theme support like TWRP

INFO
PhilZ and CWM recovery added

screenshot updated

deleted
posted wrongly

uzairabdulmajeed said:
deleted
posted wrongly
Click to expand...
Click to collapse
I know the thread is entitled [RECOVERY][N9005]
But i would like to hear the answer directly from you bro if I could flash the Philz recovery on my N900S N3?
And also, if the theme for TWRP is available or would take effect when flashed on my n900S?
Thank you so much!!!

jamespanget19 said:
I know the thread is entitled [RECOVERY][N9005]
But i would like to hear the answer directly from you bro if I could flash the Philz recovery on my N900S N3?
And also, if the theme for TWRP is available or would take effect when flashed on my n900S?
Thank you so much!!!
Click to expand...
Click to collapse
just flash TWRP if available for N900S
then use themes and Splashes in OP

Thanks you very much ! You save my day with a bootloop ! Thanks !

Just wonder can I just flash any of these over my existing cmw recovery?

beyondim said:
Just wonder can I just flash any of these over my existing cmw recovery?
Click to expand...
Click to collapse
yes you can providing its for your phone model .

JJEgan said:
yes you can providing its for your phone model .
Click to expand...
Click to collapse
It's a note 3 smn9005. I think this is right. I'm thinking of switching from cwm to TWRP. So flash it thru Odin then.

beyondim said:
It's a note 3 smn9005. I think this is right. I'm thinking of switching from cwm to TWRP. So flash it thru Odin then.
Click to expand...
Click to collapse
You have the choice to move to TWRP or Philz if you want...

rayman95 said:
You have the choice to move to TWRP or Philz if you want...
Click to expand...
Click to collapse
The only thing that is holding me back atm is that I have some CWM backups I need to sort out first. Once I switch recovery they will render them useless.