Database Users

[RECOVERY] CWM/TWRP/PHILZ/STOCK [DB][ALL i8190 Models]

Here you'll find a collection of all available recoveries for i8190 (all models) at one place.
Some zip/tars made by others and some by me.
All recoveries available in:
*.zip (to use with custom recovery)
*.tar.md5 (to use with Odin)
*.img (to use with "dd" command)
TWRP Recovery 2.6.3.0
TWRP Recovery 2.6.1.0
CWM Recovery 6.0.2.7
CWM Touch Recovery 6.0.2.7
Stock Recovery
I've also made a "black edition" of CWM touch. Flashable zip, and you'll find it in the DB as well.
View attachment 2318221
RECOVERY DATABASE i8190
Link to TWRP 2.7.1.0 by @Android-Andi [RECOVERY] TWRP 2.7.1.0
Link to PhilZ Touch Recovery by @Android-Andi [RECOVERY] CWM Advanced Edition / PhilZ Touch Recovery
[RECOVERY] ClockworkMod Recvery 6.0.4.9 (CWM-BASED)
[GT-I8190]Clockworkmod Recovery v6.0.2.8 touch]
Here is also Link to SuperSu thread where you always find latest SuperSu.zip for root.
Flash it with your custom recovery when you've installed one with Odin, and you will be rooted

thanks for your great work (Y)
Iam not familiar with that .. please could you post the command
thx in advance
i should post that command in the terminal emulator right??
Sent from my GT-I8190 using xda app-developers app

andr0id_n00b said:
thanks for your great work (Y)
Iam not familiar with that .. please could you post the command
thx in advance
i should post that command in the terminal emulator right??
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Yes it's with terminal emulator.
Have a look here for the command to use.
It can be used with any recovery.img, but you'll need root for the command to work.

tys0n said:
Yes it's with terminal emulator.
Have a look here for the command to use.
It can be used with any recovery.img, but you'll need root for the command to work.
Click to expand...
Click to collapse
i have to change only the name of the recovery.img and use same command right ??
btw this wont make my status costum or increase my CBC as I think
Sent from my GT-I8190 using xda app-developers app

andr0id_n00b said:
i have to change only the name of the recovery.img and use same command right ??
btw this wont make my status costum or increase my CBC as I think
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
That's correct
Sent through time and space from my s3mini.

can stock recovery flash this and how???

natsu93 said:
can stock recovery flash this and how???
Click to expand...
Click to collapse
no stock recovery can´t flash custom recovery, but custom recovery can flash stock recovery
@ tys0n "I'll make updates when new version gets available." the last version of cwm recovery touch for GT-I8190 is v6.0.2.8 .... i found it here and its working on my s3mini ClockworkMod Recovery v6.0.2.8 touch [UPDATE]

Dehuu said:
no stock recovery can´t flash custom recovery, but custom recovery can flash stock recovery
@ tys0n "I'll make updates when new version gets available." the last version of cwm recovery touch for GT-I8190 is v6.0.2.8 .... i found it here and its working on my s3mini ClockworkMod Recovery v6.0.2.8 touch [UPDATE]
Click to expand...
Click to collapse
it's not official.. who made the recoveries is not tys0n.. he is only make and providing the flashable zips and ODIN-flashable MD5s.. the official is made by CWM team..

wow..thanks for great work pals, i looking for this... +rep

Just to be on the safe side: the stock recovery is the same for N/L/T etc?
How would I make a backup of my stock recovery if I wanted to?

Stock recovery is the same for N L T version ...
Sent from my GT-I8190 using xda app-developers app

rcoacci said:
Just to be on the safe side: the stock recovery is the same for N/L/T etc?
How would I make a backup of my stock recovery if I wanted to?
Click to expand...
Click to collapse
yes, all same. use "Terminal Emulator" app from Play Store by Jack Palevich, you need root and busybox. open it, type "su" then enter, and then type again "dd if=/dev/block/mmcblk0p21 of=/storage/sdcard0/stockrecovery.img".. then an image file of your backuped recovery was created in your sdcard.. you can change the path of the "of"
HEY TYS0N!! THIS IS MY REPORT: I've flashed your "NON TOUCH CWM - the md5 file" with ODIN 3.07 and I got ONLY the external sd card shown in recovery but labeled as internal (I TRIED REBOOT but still same).. I was panicing.. then I flashed root with it.. and change my recovery as soon as it finished boot with "dd" command with the official one. I reboot to the *official* recovery, then got it all worked..
to the point: does the files that you provided is different?? or any damage in your files? do you got it with your phone working? if there's any, please change.. what's dangerous that people using your files and get their device brick.
thanks for read... greets

IvanKurnia said:
yes, all same. use "Terminal Emulator" app from Play Store by Jack Palevich, you need root and busybox. open it, type "su" then enter, and then type again "dd if=/dev/block/mmcblk0p21 of=/storage/sdcard0/stockrecovery.img".. then an image file of your backuped recovery was created in your sdcard.. you can change the path of the "of"
HEY TYS0N!! THIS IS MY REPORT: I've flashed your "NON TOUCH CWM - the md5 file" with ODIN 3.07 and I got ONLY the external sd card shown in recovery but labeled as internal (I TRIED REBOOT but still same).. I was panicing.. then I flashed root with it.. and change my recovery as soon as it finished boot with "dd" command with the official one. I reboot to the *official* recovery, then got it all worked..
to the point: does the files that you provided is different?? or any damage in your files? do you got it with your phone working? if there's any, please change.. what's dangerous that people using your files and get their device brick.
thanks for read... greets
Click to expand...
Click to collapse
Yeah, that sounds kind of dangerous!
Thanks for the report. I'll take it down for now and have a look at it.
Re-up when is't sorted out.

tys0n said:
Yeah, that sounds kind of dangerous!
Thanks for the report. I'll take it down for now and have a look at it.
Re-up when is't sorted out.
Click to expand...
Click to collapse
okay thx. I need to explain what I mean, there's no "flash zip from external sd card". Only "install zip from sd card". But after selecting "install zip from sd card" (this is must be internal right?), it displays my external sd, not internal.

IvanKurnia said:
okay thx. I need to explain what I mean, there's no "flash zip from external sd card". Only "install zip from sd card". But after selecting "install zip from sd card" (this is must be internal right?), it displays my external sd, not internal.
Click to expand...
Click to collapse
All CWM-files replaced now. Downloaded from official CWM site and made new *.tar.md5
Hope it works now.

Updated "i8190_stock_recovery.tar.md5" with one that doesn't increase custom binary count.:good:

+1 for this thread, this is what the doctor order for my friends I8190..Thanks tyson..

So dude, if I install this stock he would return to the status of "official"? For my is appearing "modify". I tried to put it and still has not changed. You have the stock for the GT-I8190L? I need a lot. Thank you.

HantraXz said:
So dude, if I install this stock he would return to the status of "official"? For my is appearing "modify". I tried to put it and still has not changed. You have the stock for the GT-I8190L? I need a lot. Thank you.
Click to expand...
Click to collapse
Recovery is the same for all versions. Using triangle away might help get your official status back if you triggered the custom binary count by flashing recovery through Odin.
Depends on what you've done to get your status modified.

tys0n said:
Recovery is the same for all versions. Using triangle away might help get your official status back if you triggered the custom binary count by flashing recovery through Odin.
Depends on what you've done to get your status modified.
Click to expand...
Click to collapse
Then I installed the clockwork recovery 6.0.2.7 to get root.

Install CWM on Locked Bootloader

Can i install CWM on locked bootloader?

Ben Ling said:
Can i install CWM on locked bootloader?
Click to expand...
Click to collapse
Yes.
An 'exploit' has recently become available for ROOTING the Nexus 7 without unlocking the BOOTLOADER.
This 'exploit' works... I have tested it myself.
Until recently, I believed that because FASTBOOT wasn't an option (as a result of a LOCKED BOOTLOADER), there was no way of FLASHING anything.
Happily, I was disabused of this notion by bftb0... and I can confirm, you can indeed install CWM (or TWRP) with a locked BOOTLOADER.
-----------------------------
Here's how...
First, you need to run this 'exploit' to acquire ROOT.
Upon reboot, you should now be rooted, with Chainfires SuperSU package and associated SU binary installed.
It's important that you are ROOTED before you proceed.
Next, get Android Terminal Emulator from PlayStore.
Download a CUSTOM RECOVERY .img of your choice... either CWM (Both 'Grouper' and 'Tilapia' variants are available)...
...or TWRP for 'Grouper' (N7 WiFi) or TWRP for 'Tilapia' (N7 3G).
Rename it to recovery.img... and copy it to the root of the Nexus 7's internal storage (emulated SD card).
In Terminal Emulator, run the following command...
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
Upon completion of this command, shutdown and reboot your device into the BOOTLOADER, and from there, boot into your CUSTOM RECOVERY... in pretty much the same way had you FASTBOOT FLASHED it.
-----------------------------
You are now free to flash whatever ROMs or kernels you like.
However, a word of caution... because the BOOTLOADER remains locked, FASTBOOT is strictly off limits; it simply won't work.
So the first thing you should do after flashing TWRP or CWM is...
*** MAKE A NANDROID BACKUP ***
If the device becomes 'wedged/bootlooped' as a result of some ROM flash gone wrong, then you will have no choice but to unlock the BOOTLOADER (with full wipe) in order to fix it.
But if you have a NANDROID backup... piece of cake... just restore.
-----------------------------
Credits and kudos must go to XDA members, nhshah7, who made this 'exploit' available and bftb0, whose post pointed me in the right direction, with regard to the 'dd' command.
-----------------------------
I can confirm all of this works... my Nexus 7 is currently rooted, running a custom recovery (TWRP), with a custom ROM and Kernel (see sig) installed - all sitting behind a LOCKED BOOTLOADER.
...no Factory Reset (wipe) required...
...and no Unlocked Padlock Symbol upon boot.
Rgrds,
Ged.

Previously I installed cwm and can boot,just 1 time.
I tried to boot into but nothing.
What to do?
Sent from my Sony Xperia™ sola using XDA Premium App

@GedBlake well it works for the first time for me as well,.,., used the TWRP latest..,.,.
afterwards it says "no command"

SSyar said:
@GedBlake well it works for the first time for me as well,.,., used the TWRP latest..,.,.
afterwards it says "no command"
Click to expand...
Click to collapse
This is really peculiar... I had a few problems myself, initially... but I just assumed I made a typo mistake in TE - but I never had a "no command" message. It took me two or three goes before I got it to work.
And it works fine now, without problems.
I recall reading, a while ago, you had to delete a file from /system called recovery-from-boot.p after flashing a custom recovery in order to get the custom recovery to stick. I never had to do this myself, maybe 'cos I'm running a custom ROM.
Are you on stock, or running a custom ROM?
Rgrds,
Ged.

GedBlake said:
This is really peculiar... I had a few problems myself, initially... but I just assumed I made a typo mistake in TE - but I never had a "no command" message. It took me two or three goes before I got it to work.
And it works fine now, without problems.
I recall reading, a while ago, you had to delete a file from /system called recovery-from-boot.p after flashing a custom recovery in order to get the custom recovery to stick. I never had to do this myself, maybe 'cos I'm running a custom ROM.
Are you on stock, or running a custom ROM?
Rgrds,
Ged.
Click to expand...
Click to collapse
I'm on stock JB 4.2.2 JDQ39 Wi-Fi & 3G version,so what to do now?
Sent from my Asus Google Nexus 7 using XDA Premium

Ben Ling said:
I'm on stock JB 4.2.2 JDQ39 Wi-Fi & 3G version,so what to do now?
Sent from my Asus Google Nexus 7 using XDA Premium
Click to expand...
Click to collapse
Have you tried running the dd command again?... As I previously mentioned, it took two or three attempts, before it 'stuck' on my N7.
Now I have no problem booting into TWRP... similarly, I have tested this procedure with CWM - and again no problems.
With a root capable file manager, you could try deleting (or renaming) the file recovery-from-boot.p which can be found in /system, and then try again.
Rgrds,
Ged.

GedBlake said:
Have you tried running the dd command again?... As I previously mentioned, it took two or three attempts, before it 'stuck' on my N7.
Now I have no problem booting into TWRP... similarly, I have tested this procedure with CWM - and again no problems.
With a root capable file manager, you could try deleting (or renaming) the file recovery-from-boot.p which can be found in /system, and then try again.
Rgrds,
Ged.
Click to expand...
Click to collapse
How to boot into cwm?press volume button?
Sent from my Google Nexus 7 using XDA Premium App

Ben Ling said:
How to boot into cwm?press volume button?
Sent from my Google Nexus 7 using XDA Premium App
Click to expand...
Click to collapse
Shut down the tablet completely.
Press and hold the VOL DOWN button... whilst holding, press the POWER button.
This will boot you into the BOOTLOADER.
Using the VOL buttons, navigate to RECOVERY.
Press the POWER button to select.
Rgrds,
Ged.

Just tested this method... again... (using dd to install a Custom Recovery)... with both CWM and TWRP... and in both instances, the installations survived a reboot. So I'm puzzled why there seems to be a problem here.
---------------------------------
I have semi-automated the process in order to avoid typing long complicated commands into Android Terminal Emulator. A process, which, by it's nature, is subject to typographical error.
Here's how...
Download the Custom Recovery of your choice to your Nexus 7.
Rename it to recovery.img
Copy it to the root of the emulated SD card (internal storage).
---------------------------------
Download this script file...
writerecovery.zip
Unzip and copy it to the root of the emulated SD card (internal storage).
(Alongside the recovery.img).
---------------------------------
Install Script Manager from Google Playstore.
Open Script Manager and locate the script file writerecovery.sh on the root of the emulated SD card.
Press ENTER on it...
Select OPEN AS... Script/Executable...
Select SU (root) from the toolbar...
Select Run...
The script will now execute the following command...
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
...writing the recovery.img to the recovery partition.
See attached thumbnails for the sort of thing you should expect to see.
---------------------------------
I have tested this method several times... switching between CWM and TWRP. And performing multiple reboots, to ensure that the Custom Recovery 'stuck' in each instance.
---------------------------------
Hope this works... if it doesn't... then I'm at a loss to explain why.
Maybe somebody with more technical knowledge can assist.
All I know, is it works for me... on my Nexus 7.
Rgrds,
Ged.

well i installed recovery using goo manager ,.,. got this response from other thread and is working for me ,.,., goo manager also has the option to restart in recovery so really good for me

Help with my Condition
OK, I need help with the following Scenario with Nexus 7 2012 Wifi
My USB Port is damaged. Managed to charge batter with external wires. After that I was able to:
> Root my Nexus7 with KingRoot app (several tries does the trick)
> Install CWM (non-touch) with ROM Manager
> Boot into CWM and do a dummy Flash of Update-SuperSU.zip file just to see if it works on Locked Bootloader. It was successful.
Now I came across your thread, What I need help with is:
WILL I BE ABLE TO FLASH A CUSTOM ROM + GAPPS on a Locked Bootloader via CWM ?
This is going to be a one way ride for me, if I brick I have a paperweight.
(I have however a Backup from CWM, which I can restore if the tablet manages to boot into CWM after bricking)
Need assistance, opinions, strategy with this. Response Awaited.

junisheikh said:
OK, I need help with the following Scenario with Nexus 7 2012 Wifi
My USB Port is damaged. Managed to charge batter with external wires. After that I was able to:
> Root my Nexus7 with KingRoot app (several tries does the trick)
> Install CWM (non-touch) with ROM Manager
> Boot into CWM and do a dummy Flash of Update-SuperSU.zip file just to see if it works on Locked Bootloader. It was successful.
Now I came across your thread, What I need help with is:
WILL I BE ABLE TO FLASH A CUSTOM ROM + GAPPS on a Locked Bootloader via CWM ?
This is going to be a one way ride for me, if I brick I have a paperweight.
(I have however a Backup from CWM, which I can restore if the tablet manages to boot into CWM after bricking)
Need assistance, opinions, strategy with this. Response Awaited.
Click to expand...
Click to collapse
Hi, junisheikh...
To answer your question...
junisheikh said:
"WILL I BE ABLE TO FLASH A CUSTOM ROM + GAPPS on a Locked Bootloader via CWM ?"
Click to expand...
Click to collapse
Yes, you should be able to.
---
The bootloader lock state is irrelevant when it comes to flashing stuff via a Custom Recovery (such as CWM or TWRP).
All an unlocked bootloader does, is it allows the device to accept fastboot flash commands from a connected PC or Mac, and which is the usual way of flashing a Custom Recovery, and then subsequently rooting it.
I would, however, advise against using CWM. ClockWorkMod Recovery is old and hasn't been updated for quite some time, and may cause problems.
Instead, you should take a look at TWRP (TeamWin Recovery Project). This Custom Recovery has a better user interface, and is less likely to cause you problems.
---
Although your bootloader is locked, you have managed to acquire root via KingRoot... which means you can flash a Custom Recovery with the Flashify app...
https://play.google.com/store/apps/details?id=com.cgollner.flashify
This app allows you to flash Recoveries and Boot images (stock and custom) directly from the device itself, providing the device is rooted. The free version of Flashify has a limit of 3 flashes per day. This shouldn't be a problem though... Custom Recoveries aren't something you generally flash on a regular basis.
(See my attached screenshots for a flavour of how Flashify works.)
---
You can find the latest version of TWRP for the Nexus 7 WiFi model here...
http://techerrata.com/browse/twrp2/grouper
Download to your Nexus 7, and use the Flashify app to flash.
And then download whatever Custom ROM+GAPPS you like, and flash via TWRP.
Incidentally, the NANDROID backup you've already created with CWM is NOT compatible with TWRP. So you'll need to create a new NANDROID backup, should you choose to flash TWRP.
---
junisheikh said:
This is going to be a one way ride for me, if I brick I have a paperweight.
Click to expand...
Click to collapse
This is possible, because you don't have access to fastboot (due to your broken USB port) you won't be able to fastboot flash back to Google Factory stock should you not be able to boot Android (for whatever reason) after flashing some Custom ROM. But providing you have a NANDROID backup and a Custom Recovery (CWM or TWRP) installed, you **should** be able to recover from softbricks such as bootloops. But having said that, I would tread carefully.
Hope this helps, and good luck.
Rgrds,
Ged.

(Q) Unable to flash custom rom via CWM

Hi first time I am having a problem of not able to flash custom rom via recovery CWM, here's the problem, I am using Philz recovery whenever I flash zip, the process of flashing went ok, but when all done flashing I press Reboot System Now, recovery takes me to screen that give me a message Root Access is Missing - Root device, then YES -- Root Device (/system/xbin/su) I click YES..then reboot when to Samsung GS4 splash screen then just black afterward instead of seeing boot animation..and after 1 minute when back to recovery..that's it..I know I already double check that I have root access also using root checker everything is ok, I even flash stock firmware through odin no problem and re-root but still doesn't help..do you think I have a problem in /system/xbin/su folder..please help how to fix this..thank you soo much..

Trek55 said:
Hi first time I am having a problem of not able to flash custom rom via recovery CWM, here's the problem, I am using Philz recovery whenever I flash zip, the process of flashing went ok, but when all done flashing I press Reboot System Now, recovery takes me to screen that give me a message Root Access is Missing - Root device, then YES -- Root Device (/system/xbin/su) I click YES..then reboot when to Samsung GS4 splash screen then just black afterward instead of seeing boot animation..and after 1 minute when back to recovery..that's it..I know I already double check that I have root access also using root checker everything is ok, I even flash stock firmware through odin no problem and re-root but still doesn't help..do you think I have a problem in /system/xbin/su folder..please help how to fix this..thank you soo much..
Click to expand...
Click to collapse
Which root method u are using
If possble use CF ROOT
Sent from my GT-I9500 using xda premium

123hiten said:
Which root method u are using
If possble use CF ROOT
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
I am using CF Root .. I never seen a problem like this ever since my S3

Trek55 said:
I am using CF Root .. I never seen a problem like this ever since my S3
Click to expand...
Click to collapse
Well it's a rare case but if possible put stock again reset the device from inside and do cf root and philz recovery all be well
There must be some bad system file or app causing this
Sent from my GT-I9500 using xda premium

solved**
Ok..I format my internal memory..then flash rom seems to be working for the first time, but then when I try to flash different custom rom..have the same problem again..hemm confused...

same here any fix ?

I have the same issue with my s3.

Trek55 said:
Hi first time I am having a problem of not able to flash custom rom via recovery CWM, here's the problem, I am using Philz recovery whenever I flash zip, the process of flashing went ok, but when all done flashing I press Reboot System Now, recovery takes me to screen that give me a message Root Access is Missing - Root device, then YES -- Root Device (/system/xbin/su) I click YES..then reboot when to Samsung GS4 splash screen then just black afterward instead of seeing boot animation..and after 1 minute when back to recovery..that's it..I know I already double check that I have root access also using root checker everything is ok, I even flash stock firmware through odin no problem and re-root but still doesn't help..do you think I have a problem in /system/xbin/su folder..please help how to fix this..thank you soo much..
Click to expand...
Click to collapse
Hi there mate , If you already have root or any recovery suddenly ask you "You want too change/install root/recovery" you choose no cuz u dont wanna loose ur root after.

same problem in galaxy grand
Bro! I am currently on cm11 on i9082
I flashed it using cwm 6.0.4.5
Now I want to flash another custom ROM.
When installing custom ROM I press at "reboot system now"
It shows error:
"root access missing,root device?"
No...
Yes(root device)...
When I press any one of above then device get stucked at start screen.
The root checker app shows...
You device has root access...etc
Please solve the issue...

Can no longer get into recovery boot

First, thank you for any help!
I did look threw the forums, as best I could... I did see any solutions here that worked for me... saw some one another site.. they did not work.
I can no longer get into ANY recovery boot... Every time I do the buttons, to go into recovery... it show "booting into recovery" blinks, vibrates... and then boots into the phone in normal mode....
I recently had to flash it to stock with Odin.... which lost my root.... I tried to install TWRP , so I could root it... did not work... then used KINGOROOT, to root it, which it claims DID work (the rooting) , after two tries... and then it did allow me to go into "stock recovery" mode...
...so i then flashed TWRP with Odin... and ... now, again, I get not get ANY recovery mode to come up.
ARGH!!!!!!!
Please help??
I have a N900T.
Android 5.0
Baseaband: N900TUVUFOL1
I believe it is rooted now

As long as you're flashing the correct file, it should work.
Sent from my SM-N920C

Rosli59564 said:
As long as you're flashing the correct file, it should work.
Sent from my SM-N920C
Click to expand...
Click to collapse
I am flashing TWRP 2.8.7.0 which is the SAME file I used when I flashed it... a year ago?
I know that there is a new version of TWRP... but I have heard there are problems with the newer TWRP flashing ROM's....
On another site, someone said that the problem was that if you flash back to stock, the new (stock) bootloader has a line it it, to check that you can only use stock recovery file... ... >sigh<....
My "simple" project... to upgrade my phone... has become a night mare.....

2.8.7.0-hltetmo?
If it doesn't work, try cwm.
Sent from my SM-N920C

Got it fixed!!
Figured I would say how, in case someone else has the same problem.
I had already rooted the phone with "Kingoroot" , when I was trying to put TWRP on...
By downloading and running "TWRP MANAGER" from the play store, it was able to install it on my phone, and I am now able to boot into recovery.
Good luck!!
Danny

BLU Studio 5.0 C (D536U)- Root, ROMs, Recovery

Hello again XDA, I just got my hands on a BLU Studio 5.0 C (D536U) and I just thought I'd share my contributions here. I don't have the device for long so whatever I post here was only tested by me for a short period of time.
While, there's already a rooting method for this phone, it's done with Kingroot which I do not like. So I ported CTR recovery and flashed SuperSU to get my root.
RESOURCES
Adbd Insecure
Mediatek Preloader Drivers
ADB Driver
ADB access anywhere
MTK Droid Tools
SP Flash Tool (SPFT)
Generate scatter file
Create backup with SPFT
SP Flash Tool ROM Flashing Guide
Credits
Chainfire
Snoop05

Backup stock ROM
There are many ways to back up your phone. Some are better than some but you can decide which you want to use. I recommend using SPFT.
Using custom recovery
Flash any custom recovery of your choice
Go to backup and backup all partitions.
Reboot when completed.
NOTE: If you want to reduce backup size, for TWRP enable compression and for CTR, set default backup type to tar+gzip.
Using SPFT
https://forum.hovatek.com/thread-526.html
Using MTK Droid Tools
http://www.gizmochina.com/2014/07/0...ackup-using-mtk-droid-tools-and-then-unbrick/
NOTE: You would need to be rooted and have Adbd Insecure installed and enabled.

Root
DISCLAIMER:
Rooting your phone and using custom Recoveries and ROM's have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledge about the phone and phone utilities also.
Make sure that whatever you do, you are doing it at your own responsibility.
Using SPFT
Requirements:
PC running Windows 7/8/8.1/10
USB cable
Any custom recovery
Procedure
Download SuperSU and place it on your external_sdcard.
Power off your phone and wait 1 minute for it to completely turn off.
Press vol+ and vol - and power. Press vol + to boot to recovery.
Go to install > install zip from sdcard > select UPDATE-SuperSU-v2.46.zip.
Reboot and enjoy root without Kingroot.
Credits
Chainfire

ROMs
Stock ROMs
Flashable by SPFT
Studio C D536U V08 5.0 Generic Stock Rom
OTAs
Flashable OTAs via stock recovery
BLU_D536U_V11_GENERIC
BLU_D536U_V14_GENERIC
Custom ROMs
Credits
@alakentu

Recovery
Stock recovery
Stock_V08_D536U
ClockWorkMod Touch Recovery
cwmv6blu_d536u.img
Carliv Touch Recovery
ctr3.3_blu_d536u.img
TeamWinTouchRecovery
twrpv2.6blu_d536u.img
twrpv2.8blu_d536u.img
Philz Touch Recovery (Advanced CWM 6.x)
philzv6blu_d536u.img
Credits
Dees_Troy
yuweng
carliv
Phil3759

"Flashable by SPFT" link down

kirito9 said:
DISCLAIMER:
Rooting your phone and using custom Recoveries and ROM's have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledge about the phone and phone utilities also.
Make sure that whatever you do, you are doing it at your own responsibility.
Using SPFT
Requirements:
PC running Windows 7/8/8.1/10
USB cable
Any custom recovery
Procedure
Download SuperSU and place it on your external_sdcard.
Power off your phone and wait 1 minute for it to completely turn off.
Press vol+ and vol - and power. Press vol + to boot to recovery.
Go to install > install zip from sdcard > select UPDATE-SuperSU-v2.46.zip.
Reboot and enjoy root without Kingroot.
Credits
Chainfire
Click to expand...
Click to collapse
How does one remove the nag about removing harmful app kingoroot ?

Why is the save blocks map button disabled in MTK droid tools 2.5.3 ?

Jhoanchb said:
"Flashable by SPFT" link down
Click to expand...
Click to collapse
Thanks, I'll try to get a mirror.

rwilcher said:
How does one remove the nag about removing harmful app kingoroot ?
Click to expand...
Click to collapse
Kingoroot?

rwilcher said:
Why is the save blocks map button disabled in MTK droid tools 2.5.3 ?
Click to expand...
Click to collapse
What android version do you have?

kirito9 said:
What android version do you have?
Click to expand...
Click to collapse
Android 4.4.2 . Also had to enable auto play on the device under Windows 10 before its seen. Minor thing but drove me nuts 4 a while. Thanks for responding

Yikes. I have the recovery image, spflashtool and have flashed stock ROM
On my studio 5.0 C e. Just can't get passed
flashing the recovery image. Am using it to
send this. Is maddening. Has to be something simple because it works. Should
not be this difficult. Just don't get it.

rwilcher said:
Yikes. I have the recovery image, spflashtool and have flashed stock ROM
On my studio 5.0 C e. Just can't get passed
flashing the recovery image. Am using it to
send this. Is maddening. Has to be something simple because it works. Should
not be this difficult. Just don't get it.
Click to expand...
Click to collapse
Just can't get passed what?

How to flash recovery image. Not afraid of bricking. Have bricked and recovered about 3 times. Used to splash tool etc.

rwilcher said:
How to flash recovery image. Not afraid of bricking. Have bricked and recovered about 3 times. Used to splash tool etc.
Click to expand...
Click to collapse
Flash your stock ROM, boot it. Root with Kingroot (older version, like 4.5.0) and flash your recovery with Rashr or Flashify. After flashing your recovery, remove Kingroot with SuperSuMe and flash SuperSU.

kirito9 said:
Flash your stock ROM, boot it. Root with Kingroot (older version, like 4.5.0) and flash your recovery with Rashr or Flashify. After flashing your recovery, remove Kingroot with SuperSuMe and flash SuperSU.
Click to expand...
Click to collapse
Thanks . On to flashing stock for the 5 time. Thanks for your help.

Can someone please help me with flashing a rom on my Blu Studio M5 Plus LTE On 7.0. I have tried everything. Please help.