Database Info

[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

Karbonn A7 Star(All you need at one place)

Note:-​
This Guide is only for Karbonn A7 Star(Jelly Bean)​
This rooting guide will work for ICS/Jelly Bean Both!!
Guys i am using Karbonn A7 Star. So i am sharing some of my experience and tips for this device this is about easiest rooting of Karbonn A7 Star.​
So how to root your Karbonn A7 Star :-​
[┴]Download Latest Version of Framaroot from here Link(Framaroot) or Search for the latest Version on Google.
[┴]Now Install the Application on your Karbonn A7*
[┴]Open the APP
[┴]Select Install Super SU from the box
[┴]Now Click on Boomair
[┴]A success message will appear to you if your device has been successfully rooted.
[┴]Then restart your Phone you will see now Super Su APP installed on your device.

Installing CWM on A7 Star(Jelly Bean)
CWM for A7 Star(Jelly Bean)​
Download the CWM image file for Jelly Bean from here:- Link
Now Download MobileUncle Tool from here or Just Google IT :- Link
Put the CWM image file in you root/home directory of memory card that you have downloaded from the link provided.
Now install Mobile Uncle tool you have downloaded from above link.
Open Mobile Uncle Tool now select recovery update now choose recovery.img file and flash it.
Once done it will ask you to boot into recovery mode press Ok.
When you got boot into CWM recovery select reboot device then it will ask you for to disable stock recovery and select YES!(It is one time proceess).
Now whenever you boot into recovery it will always boot to CWM recovery not your stock recovery..
:good: :good: :good: :good: :good: :good: :good: :good: :good: :good:

CWM for A7 Star(ICS)
Here are the steps for installing CWM on ICS running A7 Star​
[1]First of all download CWM for ICS from here :- Link(ICS)
[2]Now download MobileUncle from google or download it from the given link :- Link
[3]Install Mobile Uncle in your phone that you have downloaded from the above link.
[4]Now the CWM file that you have downloaded from the above link will be in .rar format extract those files but do not use the mobileuncle.apk app which is in .rar file only extract cwm.img file and rename it with recovery.img and put this image file in the root/home directory of the Memory Card.
[5]Now open the MobileUncle APP which you have installed earlier in step-3.
[6]You will see the option recovery update choose this option and select the recovery.img and flash it.
[7]After that it will ask you to boot into recovery mode press ok and you will be successfully boot into CWM recovery mode.
[8]When you got boot into CWM recovery select reboot device then it will ask you for to disable stock recovery and select YES!(It is one time proceess).
[9]Now whenever you boot into recovery it will always boot to CWM recovery not your stock recovery..

[CTRv2]Panasonic P81[CTRv2][TOUCH BASED]

[CTR Recovery][Port][Touch Based][16 September 2014]​
Carliv Touch Recovery with Aroma File Manager Support
You must have Root access.
Installation Instructions
1. Download and place the image file on SD card.
2. Install MTK MobileUncle Tool from Play Store and open and go to Recovery Updates option
3. Select the image file to install and let it be installed automatically.
4. It will reboot into recovery.
Recovery image file Download Link
Click HERE
ClockworkMod Recovery (CWM) is a replacement recovery option for Android devices,and CTR is based on CWM and also support Touch functionality!!!!!
Please don't mirror the Recovery if anyone want to modify do take my permission.
Credits :-
===>Carliv
===>michfood
===>Me

More Recoveries Coming soon for Panasonic P81.
Keep Visting this Page.
Thanks & Regards
Shivam Bhalla
XDA.

Any custom rom or recoveries for P61

Shivam Bhalla said:
More Recoveries Coming soon for Panasonic P81.
Keep Visting this Page.
Thanks & Regards
Shivam Bhalla
XDA.
Click to expand...
Click to collapse
Hello
Any rom for p81?
Thanks

Sir how to getback my stock recovery becoz i cant restore my backup in cwm recovery
Sent from my Coolpad 7320 using XDA Free mobile app

Can i flash this CTR recovery on my CWMauto recovery directly (Panasonic p81)?

Twrp recovery

TWRP for XOLO Q3000​
Here is TWRP for xolo Q3000 .
{
"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"
}
I request
chinasa
@allan.vaz
@amrutb
@Jagadish-ravi
@qwerty.3551
@ravikumarbeniwal
@rohithdivakaran
@rufus.reynolds
@sushbabblu
@Vineet3
@smahalgavaiya
@vijay jay
m0han
@aabidhashmi
@barath anandan
 @drlalitbida
 @fort21
@nihar13
@qwerty.3551
@sanyamjain
@Sandy d Candy
@SPG30759
@ranjanshandilya
@Rishi45
 @indigo110
@rahulhacker007
@sunny76900
@patilsb
@akxolo
@xoloq3000
@ravi_21
@mhp1995
@Karan_Kapuria
@nicksaisw
@Aftab Memon
@ashuchem
@Haldar_dhruv
@rohitsinghpu
@beinglazy
@viru_192 
 @chaobuddy
@irfanjunaid
@arnabbiswasalsodeep
@Anand Ramesh
@ashishji12
ApriliaM3
Please try this recovery and report back about JB and KK rom switching.
In TWRP 2.8 u cant root with it as supersu is deleted from recovery to reduce size.
As we have other flashable zips to root it wont be an big issue.
Waiting for response from u guys.​
Credits-
@yuweng Sir this wont be possible without his tool
TWRP team 
 @hanuma for help:good:

avi3230 said:
In TWRP 2.8 u cant root with it as supersu is deleted from recovery to reduce size.
As we have other flashable zips to root it wont be an big issue.....
Click to expand...
Click to collapse
i'm on clone stock kk rom with cwm v6.0.2.8 now. i wanna have twrp v2.8 and also root. how best to go about it?
does your op imply "if twrp v2.7 is used, root is not lost"? - on rooted device having any other custom recovery.
and, what if i flash your twrp v2.8 and then flash supersu zip file from here? will i have proper root?
btw, can this be installed using flashify or mobileuncletools? or, is spftools procedure itself required?
suggest that you make the op clearer and noob-friendly. thanks.

m0han said:
i'm on clone stock kk rom with cwm v6.0.2.8 now. i wanna have twrp v2.8 and also root. how best to go about it?
does your op imply "if twrp v2.7 is used, root is not lost"? - on rooted device having any other custom recovery.
and, what if i flash your twrp v2.8 and then flash supersu zip file from here? will i have proper root?
btw, can this be installed using flashify or mobileuncletools? or, is spftools procedure itself required?
suggest that you make the op clearer and noob-friendly. thanks.
Click to expand...
Click to collapse
Make sure you flash stock rom first before flashing this recovery! When i was using Q900, it used to give variety of errors! So always begin with clean flashed device! The error that i got frequently was E: cannot mount /Data bla bla.... Always ended up with mounting errors! Then came Shikar bro who ported the recovery and after which i developed the custom first custom ROM!

irfanjunaid said:
Make sure you flash stock rom first before flashing this recovery! When i was using Q900, it used to give variety of errors! So always begin with clean flashed device! The error that i got frequently was E: cannot mount /Data bla bla.... Always ended up with mounting errors! Then came Shikar bro who ported the recovery and after which i developed the custom first custom ROM!
Click to expand...
Click to collapse
Anyone having this issue???
I didnt got it.
working correctly till now
but thanks for the info:good:

m0han said:
i'm on clone stock kk rom with cwm v6.0.2.8 now. i wanna have twrp v2.8 and also root. how best to go about it?
does your op imply "if twrp v2.7 is used, root is not lost"? - on rooted device having any other custom recovery.
and, what if i flash your twrp v2.8 and then flash supersu zip file from here? will i have proper root?
btw, can this be installed using flashify or mobileuncletools? or, is spftools procedure itself required?
suggest that you make the op clearer and noob-friendly. thanks.
Click to expand...
Click to collapse
U cant root using 2.8 recovery.
sometimes if rom is not rooted then at end of flash it ask u to root, 2.8 cant do that but 2.7 can:good:.
u cant have 2.8 with root facility as size will exceed 6mb.
u can root device using any flashble root zip.
================================================================================================
For kitkat 4.4.2 the zip in link is not at all useful.
Also it cant be rooted with supersu provided in recovery
so if u wanna use 2.8 u cant use rooting within recovery.
if u wanna root ur 4.4.2 see this post method 8 definatly works.
also if u want supersu as root app head over to this post.
For recovery flashing I always prefer sp tool method which will work 100% and u dont have to bother about properly rooted device.
if u have rooted device flashify or mobileuncle tool should work.

Hi Avi, when i tried to flash the recovery via flashify my stock recovery is gone as well as the one which i flashed twrp also gone and currently my phone is running without recovery

sushbabblu said:
Hi Avi, when i tried to flash the recovery via flashify my stock recovery is gone as well as the one which i flashed twrp also gone and currently my phone is running without recovery
Click to expand...
Click to collapse
Please try with sp tools.
if u running 4.4.2 flashify may give this type of error.

TWRP - 2.8 - 94 downloads:good::good::good:

avi3230 said:
TWRP - 2.8 - 94 downloads
Click to expand...
Click to collapse
weird graphics and touch issues were reported in 2.8.0.0. how about 2.8.2.0?
bovirus said:
TWRP released a bugfix for TWRP 2.8.1.0 . Now it's available TWRP 2.8.2.0.
Click to expand...
Click to collapse

m0han said:
weird graphics and touch issues were reported in 2.8.0.0. how about 2.8.2.0?
Click to expand...
Click to collapse
Yes Sir,
I ported 2.8.2.0 but the size is 6.54mb way too much than recovery partition.
I am trying much hard for more than 6 mb partition which can boot in recovery.
Already bricked my device several times for the same.
But still only 6 mb recovery can boot.
NOw we have two options.
Compile new kernel with less size - source codes are needed
we have bq codes - but it may not work for our device - so i am much reluctant to take chance.
we need to compile new uboot.bin which can make booting in recovery of even 11mb size
again source code and compiling.
If anyone from ur side can help in compiling that would be great- as i am just beginner for it
u can get source code for BQ here.
Thank you.

avi3230 said:
....If anyone from ur side can help in compiling that would be great.....
Click to expand...
Click to collapse
sorry. no knowledge in these matters. hope someone else would come forward.

avi3230 said:
...I ported 2.8.2.0 but the size is 6.54mb way too much than recovery partition.
I am trying much hard for more than 6 mb partition which can boot in recovery.....
Click to expand...
Click to collapse
any hope for latest version of twrp?
please see screenshots of twrp v2.8.0.0. the interface is not clear (highly pixelated). the actual display is worse than seen here. can anything be done about it?
does anyone know of any themes than work on twrp v2.8.0.0 for xolo q3000? the ones i tried didn't work although i chose the correct resolution.
also, what exactly does "repair or change file system" do?
my device gets connected as an mtp device and shows up as a separate device in "my computer". i mean, the sd cards do not get connected as separate usb drives.
i can open the device and see both my sd cards listed and also browse & carry out operations. but, any changes made are not reflected even after 'refreshing'.
if i click "disable mtp" as seen in the 3rd screenshot, will the disabling be temporary or permanent? will my sd cards get connected as separate usb drives?
i'd appreciate it if someone who has authentic knowledge about these matters responds with suggestions. thanks for any help.
btw, i hope @avi3230 is following this thread. maybe we can hope for ctr v3.0 kitkat for xolo q3000 soon.
edit: saw this thread only now . will try that and report :good:. please answer the queries in blue. thanks.

@m0han
TWRP 2.8.2.0 coming soon.
themes for 2.8.0.0
what exactly does "repair or change file system" do?
answer is here.
What's new in 2.7.1.0:
Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
Click to expand...
Click to collapse
MTP is also mentioned under 2.8.0.0
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Click to expand...
Click to collapse
I am following CTR :good::good:

avi3230 said:
....MTP is also mentioned under 2.8.0.0....
Click to expand...
Click to collapse
i'd like to know about this:
m0han said:
....if i click "disable mtp" as seen in the 3rd screenshot,
will the disabling be temporary or permanent?
will my sd cards get connected as separate usb drives?....
Click to expand...
Click to collapse
any idea about this?

BLU DASH 5.0 D410a Stock ROM Images + Root + TWRP

STOCK ROM IMAGES BLU DASH 5.0 D410a V27-GENERIC Android Kitkat 4.4.2 MT6572 Chipset (no UBIFS)
PLEASE READ THE INSTRUCTIONS BEFORE FLASHING YOUR PHONE SO THAT YOU WON'T BRICK IT.
EDIT: 14 January 2015. Updated the TWRP 2.8.2.0 download link. Fixed the problem where ADB and MTP was not functioning in TWRP. Added backup support for a few other partitions including the Baseband.
EDIT: 19 January 2015. Changed method of rooting and added flashable zip with modified kernel to add init.d support (that was tested and is functioning properly.)
STEP 1
BACKUP YOUR MEDIATEK DEVICE
Prerequisites
All of the software is for Windows.
Download and Extract the MTK USB Drivers and the SP Flash Tool found closest to the top of the list at:
http://mtk2000.ucoz.ru/
Press the play button to the right of the file to start the download.
Download MTK Droid Root & Tools
Latest version can be found by following the link of the following post.
http://forum.xda-developers.com/showpost.php?p=38320254&postcount=1
Hint: Click the show content button to see the link to another forum with the download link
Direct Download Link of MTK Droid Root & Tools if you are having problems getting the link.
http://depositfiles.com/files/ne1gnposp
You will need Winrar to extract the files.
That can be downloaded from: http://www.rarlab.com/download.htm
READ HERE ON HOW TO BACKUP: http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
Thanks to @rua1 for the instructions and software.
NOTE: I WOULD RECOMMEND BACKUPING UP THE USRDATA PARTITION AS WELL TO DO THAT USE HEX "0X96B40000" AS THE LENGTH DURING READ BACK IN SP FLASH TOOL
To flash the DASH 5.0 you need to use the Preloader to do it.
STEP 2
Installing the Preloader Driver (READ this section entirely before trying)
Open Device Manager
Start -> Run
Type:
Code:
devmgmt.msc
Press Enter
Turn off the phone until it is completely shut down with nothing plugged in the USB port. You will see the screen go black and shortly afterwards it will vibrate.
With Device Manager open, connect the USB cable to the phone without turning it on.
You will see the MT65XX Preloader appear (see image)
{
"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"
}
Quickly double click MT65XX Preloader before it disappears, if it disappered, just unplug and plug back in the cable and try again.
Under the Driver tab, click Update Driver, click Browse my computer for driver software.
Using the Browse button find the MTKUSBAll folder you extracted and click on "New inst. win 7&8x64" and click OK
Click Next
If you get the message "Windows can't verify the publisher of this driver software", just click "Install this driver software anyway"
Click Close
Click Close
After the driver is installed you can unplug the phone.
STEP 3
Uploading the image files to the phone{/B}
WARNING: The BLU-DASH-5.0_141022_BLU-D410a-V27-GENERIC_FOR_SP_FLASH_TOOL.zip file has all of the necessary images but do not flash them unless you trying to recover from a brick.
DO NOT FLASH THE PRELOADER.BIN AS IT MAY BRICK YOUR PHONE.
THE ONLY FILES I HAVE PERSONALLY TESTED ARE boot.img, factory_NONmodified_recovery.img and system.img
Download BLU-DASH-5.0_141022_BLU-D410a-V27-GENERIC_FOR_SP_FLASH_TOOL.zip from here:
http://d-h.st/3L9G
See Step 5
Extract the SP Flash Tool.
Extract the system.img and MT6572_Android_scatter.txt (and/or boot.img and factory_NONmodified_recovery.img, if you wish)
Open the SP Flash Tool
Click the Download tab
Click the Scatter-loading button and select the MT6572_Android_scatter.txt file.
Click the location of ONLY the parition(s) you are going to flash: ANDROID = SYTEM partition (system.img), BOOTIMG = KERNEL (boot.img) and RECOVERY=RECOVERY (factory_NONmodified_recovery.img or custom recovery file)
Select the image file (e.g. system.img or system_rooted.img)
MAKE SURE ALL OTHERS ARE NOT TICKED
Click the Download button.
Plug in the phone or unplug and plug it back in to start flashing the images to the phone.
Note: This can also be done with the battery removed.
Your phone will have root.
STEP 4 - Adding TWRP
First we need to rename the file recovery-from-boot.p found in the /system folder.
Using a File Manager with root permissions rename
Code:
recovery-from-boot.p
to
Code:
recovery-from-boot.bak
OR
From an adb shell, rename the file
Code:
su
cd /system
mv recovery-from-boot.p recovery-from-boot.bak
Now turn off the phone and with SP Flash Tool flash TWRP 2.8.2.0. Download link below.
NOTE: Select only the RECOVERY partition to flash. TWRP themes are supported as well as the Aroma File Manager.
http://d-h.st/aQmt
STEP 5 - Rooting and adding init.d support
Go to http://download.chainfire.eu/supersu
Download the latest SuperSU.
Go to http://d-h.st/AJQ
Download the init.d support zip file.
Boot to TWRP while connected to a PC with adb tools run the command
Code:
adb reboot recovery[/url]
OR
Hold down the power select Reboot and hold down the volume up button until you see the TWRP logo.
Via the install menu, flash the SuperSU zip and inti.d support zip.
ALL DONE!
THANKS:
[user=631273]@Chainfire[/user] for SuperSU
[user=5119815]@rua1[/user] for MTK Droid Root & Tools and instructions on how to use SP Tools
[user=4478781]@yuweng[/user] for creating the tool to make TWRP for MediaTek devices
[user=912474]@Dees_Troy[/user] for TWRP

I will give a brief explanatoin and will elaborate more when I have the time.
For Root:
Thanks to @Chainfire
I basically mounted the system.img in a Linux OS and copied the files from the SuperSU v2.36 zip file and placed them in their relevant directories added the relevant permissions, etc.
For init.d scripts
Thanks to @alireza7991
See his thread: http://forum.xda-developers.com/showthread.php?t=2287540
I modified the kernel to boot and created a flashable zip that adds busybox to /system/xbin and creates the necessary folders then flashes the modified kernel.
For TWRP:
Thanks to @yuweng
I used Easy Magic TWRP Installer for MTK. See http://forum.xda-developers.com/showthread.php?p=53752834#post53752834
It worked but changed my partition information for some reason even though the size fit my paritition size. I wiped my phone and lost my baseband and recovered it. Posted a new thread on how to do that. See http://forum.xda-developers.com/android/software-hacking/restore-baseband-mt65xx-devices-t2967949
That is why I posted the image file so no one has to face that problem too. I tested it and it is functioning without any problems.
You can follow yuweng's thread to make it smaller if your partition size is smaller than 6MB for some phones, at a cost of course.

Anyone looking for baseband files can check http://forum.xda-developers.com/android/software-hacking/restore-baseband-mt65xx-devices-t2967949
For anyone wanting to use Link2SD on this, I have created a flashable zip to use with a custom recoveery that adds init.d support, installs Link2SD as a system app and adds a modified mount script that functions properly.
Requires root and a SD card with the second partition formatted as EXT4.
Download -> http://d-h.st/Dcgh

After flash this rom only get Blu screen, wipe and cache reset and the same, trun to V14 again and power on ok, this v 27 in the 2 variants, stock and rroted not start.

jorgefar said:
After flash this rom only get Blu screen, wipe and cache reset and the same, trun to V14 again and power on ok, this v 27 in the 2 variants, stock and rroted not start.
Click to expand...
Click to collapse
What procedure did you use to flash it?

SP_Flash_Tool_exe_windows_v5.1420.00
Scatter File from V27
selected only:
Recovery: non modified...
Boot: boot.img
Android : System.img or System Rooted
Flashed OK
Only Blu screen and restar...
Im currently on V14 Ok

jorgefar said:
SP_Flash_Tool_exe_windows_v5.1420.00
Scatter File from V27
selected only:
Recovery: non modified...
Boot: boot.img
Android : System.img or System Rooted
Flashed OK
Only Blu screen and restar...
Im currently on V14 Ok
Click to expand...
Click to collapse
Your phone is a BLU Dash 5.0 D410a and NOT the 5.0+ or 5.0 Studio right?
It sounds like your kernel (boot.img) is not booting the /system partition. Try flashing the /system and recovery partitions only for now and see what happens. Do not flash the boot.img

Thanks for you le answer! Thats right, is a Blu Dash 5.0 D410a, I try on Monday the suggested and post results!!!

Hi again, flashed system and recovery only, stuck on Blu screen again, try wipe and reset cache, stuck on screen Blu,any recomendation??

Added a flashable zip to add init.d and install LInk2SD with a modified mount script to run properly on this phone, BLU DASH 5.0 D420a running V27 Android 4.4.2.
See post #3

dechronic said:
Your phone is a BLU Dash 5.0 D410a and NOT the 5.0+ or 5.0 Studio right?
It sounds like your kernel (boot.img) is not booting the /system partition. Try flashing the /system and recovery partitions only for now and see what happens. Do not flash the boot.img
Click to expand...
Click to collapse
I'm having the same problem as Jorgefar. Mine is on v24 instead of v14 though after the factory update to 4.4.2. I rooted it with kingroot, but I would like to have twrp recovery. I've done everything you instructed him, but mine gets stuck in the bootloop as well. I thought i could just flash the recovery, and did the rename on the recovery file, but that didn't work still had factory recovery. After that I did the entire procedure and got the bootloop.

Sexyr said:
I'm having the same problem as Jorgefar. Mine is on v24 instead of v14 though after the factory update to 4.4.2. I rooted it with kingroot, but I would like to have twrp recovery. I've done everything you instructed him, but mine gets stuck in the bootloop as well. I thought i could just flash the recovery, and did the rename on the recovery file, but that didn't work still had factory recovery. After that I did the entire procedure and got the bootloop.
Click to expand...
Click to collapse
After installing TWRP you need boot into TWRP before booting into Android and install the latest SuperSU. The install-recovery.sh will replace TWRP with the stock recovery on the first boot if SuperSU is not installed, which renames it.
After flashing TWRP with the Smart Phone Flash Tool, disconnect the cable, press the power button and then hold the volume up button to enter TWRP.

dechronic said:
After installing TWRP you need boot into TWRP before booting into Android and install the latest SuperSU. The install-recovery.sh will replace TWRP with the stock recovery on the first boot if SuperSU is not installed, which renames it.
After flashing TWRP with the Smart Phone Flash Tool, disconnect the cable, press the power button and then hold the volume up button to enter TWRP.
Click to expand...
Click to collapse
Cool got it and am on v27 now. thanks..... now if ony there were other roms for it ah well, at least i'm rooted again with recovery.

can i flash this on BLU Dash 5.0 D400a

dechronic said:
Anyone looking for baseband files can check http://forum.xda-developers.com/android/software-hacking/restore-baseband-mt65xx-devices-t2967949
For anyone wanting to use Link2SD on this, I have created a flashable zip to use with a custom recoveery that adds init.d support, installs Link2SD as a system app and adds a modified mount script that functions properly.
Requires root and a SD card with the second partition formatted as EXT4.
Download -> http://d-h.st/Dcgh
Click to expand...
Click to collapse
This say file no longer available..could it be downloaded elsewhere?

Does this work on 5.0+?

Stiffymeister said:
Does this work on 5.0+?
Click to expand...
Click to collapse
Don't think so but I think I have a 5.0+ image. Anything in particular you looking for? I should be able to provide it tomorrow

i have tried everything as you said but after using the flash too and b4 installing recovery it says my phone is not rooted so it wont let me rename the recovery file. should i have a rooted system image in the scatter file cause i dont see one in the files i extracted. p.s. i downloaded all the files you linked so if im missing something can someone please point me in the right direction. thanks
blu dash 5.0 d410a v27

dlongnasty said:
i have tried everything as you said but after using the flash too and b4 installing recovery it says my phone is not rooted so it wont let me rename the recovery file. should i have a rooted system image in the scatter file cause i dont see one in the files i extracted. p.s. i downloaded all the files you linked so if im missing something can someone please point me in the right direction. thanks
blu dash 5.0 d410a v27
Click to expand...
Click to collapse
I probably need to redo the steps for a couple of the posts.
Download the TWRP at http://d-h.st/aQmt
Upload it to the phone. Make sure that only recovery is ticked in the Smart Phone Flash Tool (SP Flash Tool) and select the file you downloaded. You should be able to figure out the rest based on my instructions.
Flash SuperSU which can be downloaded from http://download.chainfire.eu/supersu
It will rename the file that would put back the original recovery.
That should be it.

got it working thanks. are their any custom roms for the d410a?