Hello, so even though I'm fairly new to the world of custom ROM's I feel as though this website has provided me with more than sufficient information for me to keep on flashing. I've flashed a few ROM's in the past but I'm currently stuck as for what I should do next. I currently have an S4 ATT MF3 which I would like to upgrade to MK2 so that I can put a 4.4.2. ROM via Safestrap using the Deadly Venom method.
Based on the guide (http://forum.xda-developers.com/showthread.php?t=2573080) I need to boot into the stock recovery and flash stock MF3 then MK2 which I can then root and safestrap. When I added my first ROM on this device I replaced the stock ROM (I have a hatred for TouchWiz) and replaced with a GPE ROM.
My phone can no longer boot into the stock Samsung recovery, it merely just bootloops instead, but I can still flash via Safestrap. So what should I do? Can I get the stock recovery back? Would I have any issues if I flash the MK2 update via Safestrap instead of the stock recovery? Will flashing the MF3 stock tar via Odin be all that I need to do? Any advice would be appreciated!
DarthVayda said:
Hello, so even though I'm fairly new to the world of custom ROM's I feel as though this website has provided me with more than sufficient information for me to keep on flashing. I've flashed a few ROM's in the past but I'm currently stuck as for what I should do next. I currently have an S4 ATT MF3 which I would like to upgrade to MK2 so that I can put a 4.4.2. ROM via Safestrap using the Deadly Venom method.
Based on the guide (http://forum.xda-developers.com/showthread.php?t=2573080) I need to boot into the stock recovery and flash stock MF3 then MK2 which I can then root and safestrap. When I added my first ROM on this device I replaced the stock ROM (I have a hatred for TouchWiz) and replaced with a GPE ROM.
My phone can no longer boot into the stock Samsung recovery, it merely just bootloops instead, but I can still flash via Safestrap. So what should I do? Can I get the stock recovery back? Would I have any issues if I flash the MK2 update via Safestrap instead of the stock recovery? Will flashing the MF3 stock tar via Odin be all that I need to do? Any advice would be appreciated!
Click to expand...
Click to collapse
If you don't mind losing your user data (back up anything you want from internal storage) just flash the MK2 full ODIN. Otherwise, there is a thread somewhere with just the MF3 recovery image and if you have root you could use an app to manually flash that (don't remember the app).
DeadlySin9 said:
If you don't mind losing your user data (back up anything you want from internal storage) just flash the MK2 full ODIN. Otherwise, there is a thread somewhere with just the MF3 recovery image and if you have root you could use an app to manually flash that (don't remember the app).
Click to expand...
Click to collapse
The app is flashify
Sent from my Nexus 5 using XDA Free mobile app
Possible to restore stock recovery?
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
pravus87 said:
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
Click to expand...
Click to collapse
I would flash in Odin the stock mf3 tar file, but out will wipe the device. All his apps and data. If you can find the mf3 recovery image file you could try to flash that in flashify, if you're rooted
Edit, found this. I didn't download the file but I'm guessing it's a .img file. You could flash that in flashify or use the dd command
Sent from my Nexus 5 using XDA Free mobile app
pravus87 said:
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
Click to expand...
Click to collapse
In addition to the above post from jd, the CM installer will not work on our device as our bootloader is locked. There is no way to run any AOSP based ROM once your phone is on MF3 firmware or higher.
DarthVayda said:
Hello, so even though I'm fairly new to the world of custom ROM's I feel as though this website has provided me with more than sufficient information for me to keep on flashing. I've flashed a few ROM's in the past but I'm currently stuck as for what I should do next. I currently have an S4 ATT MF3 which I would like to upgrade to MK2 so that I can put a 4.4.2. ROM via Safestrap using the Deadly Venom method.
Based on the guide (http://forum.xda-developers.com/showthread.php?t=2573080) I need to boot into the stock recovery and flash stock MF3 then MK2 which I can then root and safestrap. When I added my first ROM on this device I replaced the stock ROM (I have a hatred for TouchWiz) and replaced with a GPE ROM.
My phone can no longer boot into the stock Samsung recovery, it merely just bootloops instead, but I can still flash via Safestrap. So what should I do? Can I get the stock recovery back? Would I have any issues if I flash the MK2 update via Safestrap instead of the stock recovery? Will flashing the MF3 stock tar via Odin be all that I need to do? Any advice would be appreciated!
Click to expand...
Click to collapse
pravus87 said:
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
Click to expand...
Click to collapse
Here is the MF3 stock recovery, flash in PDA slot in Odin(AP in Odin v3.09+): https://mega.co.nz/#!klcz1B4J!BVAno0CcaJ7aXc9tHgUtpQ0vy_NF5ceh7RogLR6JBTU
muniz_ri said:
Here is the MF3 stock recovery, flash in PDA slot in Odin(AP in Odin v3.09+): https://mega.co.nz/#!klcz1B4J!BVAno0CcaJ7aXc9tHgUtpQ0vy_NF5ceh7RogLR6JBTU
Click to expand...
Click to collapse
Thanks to everyone for all the information, and thank you especially for sharing the link. I am staying with my parents short-term in a very rural area with awful internet and I was dreading downloading the 2+GB stock firmware file just to get recovery back. This is perfect. Thanks again!
Related
Hey there, I've recently made the purchase of a samsung galaxy S4 1337m
Once i got it home, the first thing i did was root it via Chainfires Root, and downloaded
rom manager, and installed CWM, and backed up my original OS with the original root
to a SD Card, once i did that I installed Odexed Andriod 4.3 for US and CAN, when i discovered
there was Chainsfire root guide for this version in particular, i tried to install it, what i did was attempt
to flash the latest root onto 4.3 via oden, after which i would flash the modded software to work for 4.3
however, in the process i ended up losing CWM, and the root all together, so i was wondering if anyone
was willing to lend me a hand getting the root onto my 4.3, so i can get my CWM back on.
Thanks!
DeathSentinels said:
Hey there, I've recently made the purchase of a samsung galaxy S4 1337m
Once i got it home, the first thing i did was root it via Chainfires Root, and downloaded
rom manager, and installed CWM, and backed up my original OS with the original root
to a SD Card, once i did that I installed Odexed Andriod 4.3 for US and CAN, when i discovered
there was Chainsfire root guide for this version in particular, i tried to install it, what i did was attempt
to flash the latest root onto 4.3 via oden, after which i would flash the modded software to work for 4.3
however, in the process i ended up losing CWM, and the root all together, so i was wondering if anyone
was willing to lend me a hand getting the root onto my 4.3, so i can get my CWM back on.
Thanks!
Click to expand...
Click to collapse
I haven't used 4.3 but from what I've read I believe you just flash the .zip chainfire provided from recovery.
So now you will have to ODIN back to stock if you lost your recovery, re-root, install recovery (recommend TWRP instead), re-flash 4.3, flash the .zip provided from chainfire in his post here:
https://plus.google.com/u/0/113517319477420052449/posts/WqS2E9kkN1L
blyndfyre said:
I haven't used 4.3 but from what I've read I believe you just flash the .zip chainfire provided from recovery.
So now you will have to ODIN back to stock if you lost your recovery, re-root, install recovery (recommend TWRP instead), re-flash 4.3, flash the .zip provided from chainfire in his post here:
https://plus.google.com/u/0/113517319477420052449/posts/WqS2E9kkN1L
Click to expand...
Click to collapse
Do you know whether or not I'm able to re-flash with oden using the recovery created by CWM?
Or do i need to download the stock rom for my phone, which i imagine I would do a factory wipe
then boot into download mode then flash the stock rom?
DeathSentinels said:
Do you know whether or not I'm able to re-flash with oden using the recovery created by CWM?
Or do i need to download the stock rom for my phone, which i imagine I would do a factory wipe
then boot into download mode then flash the stock rom?
Click to expand...
Click to collapse
He means Odin the stock ROM
DeathSentinels said:
Do you know whether or not I'm able to re-flash with oden using the recovery created by CWM?
Or do i need to download the stock rom for my phone, which i imagine I would do a factory wipe
then boot into download mode then flash the stock rom?
Click to expand...
Click to collapse
The backup created from CWM should be a .zip that is flash-able only from recovery afaik. You will need your stock firmware .tar file and flash with ODIN. This is only if you surely cannot boot into recovery. If you manage to boot to CWM you can flash your backup of course.
Your STOCK firmware can be downloaded here:
http://forum.xda-developers.com/showthread.php?t=2269304
blyndfyre said:
The backup created from CWM should be a .zip that is flash-able only from recovery afaik. You will need your stock firmware .tar file and flash with ODIN. This is only if you surely cannot boot into recovery. If you manage to boot to CWM you can flash your backup of course.
Your STOCK firmware can be downloaded here:
http://forum.xda-developers.com/showthread.php?t=2269304
Click to expand...
Click to collapse
I currently did a factory wipe on my device, and flashed using odin with my stock
rom, things are looking good thus far, will keep posted if anything goes not as planned!
i installed safestrap and tried updating to oudhs recovery through recovery.
it says it installs but when i reboot its still safestrap.
also tried installing twrp thorugh android emulator still have safestrap.
any suggestions?
You can't flash a recovery. You're going to have to return to stock
Edit how can someone with so many posts know so little about their device. If you're on ss you have to use the recovery that comes with it. Read the stickies
but before i flashed ss, i was already using oudhs.
the reason why i flashed ss i have no idea
bstylz911 said:
but before i flashed ss, i was already using oudhs.
the reason why i flashed ss i have no idea
Click to expand...
Click to collapse
So if you are on MDB or MDL (You must have been if you have the AT&T S4 and custom recovery) just Odin back to stock firmware and re-install whichever custom recovery you want (as long as it is for this phone and LOKId). Make sure you get the custom recovery on the phone before it tries to update to a firmware that you can't do anything (other then Safestrap) with. Search and read to find the information you need if you don't understand what I am telling you. And don't do anything to your phone until you do. Good luck.
I am currently on the unlocked MDL bootloader, and I am running KANGAKAT 7.0, which is a KitKat 4.4 ROM. My phone is also encrypted, which means that I cannot flash updates due to CWM/TWRP not supporting encryption.
The solution proposed by other users has been to ODIN the stock MK2 recovery onto my phone, use the stock recovery to factory reset my device, then re-flash TWRP and then my new ROM.
However I'm having a problem with these steps. I am able to successfully ODIN the stock MK2 recovery to my device, however whenever I try to boot into recovery, I get the yellow triangle screen stating that I'm running software that is not authorized by AT&T, and stating something to do with my kernel in the top left of the screen.
Is there a step that I am missing? I followed the instructions @ http://forum.xda-developers.com/showthread.php?t=1506697
It looks like that file is for the s2 skyrocket, not the s4. You'll probably have to flash the complete mdl firmware in Odin
Edit, if you're still rooted try flashing twrp 2.8.3.0 image file in flashify from the play store. http://techerrata.com/browse/twrp2/jflteatt
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
It looks like that file is for the s2 skyrocket, not the s4. You'll probably have to flash the complete mdl firmware in Odin
Edit, if you're still rooted try flashing twrp 2.8.3.0 image file in flashify from the play store. http://techerrata.com/browse/twrp2/jflteatt
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, they're instructions for the S2 Skyrocket, but I just used the general procedure and not the file, I used the stock recovery listed here http://forum.xda-developers.com/showpost.php?p=49687791&postcount=3
You make an interesting point though, if I ODIN the entire stock MDL ROM, that could work. I'm just going to write over it with another ROM anyways, so what I restore to shouldn't matter. I know this is probably a dumb question, but flashing the stock MDL ROM isn't going to affect my MDL bootloader is it?
I can get TWRP 2.8.3.0 with or without Flashify, but that app is very convenient, thank you for the tip =)
ChrisG683 said:
Yeah, they're instructions for the S2 Skyrocket, but I just used the general procedure and not the file, I used the stock recovery listed here http://forum.xda-developers.com/showpost.php?p=49687791&postcount=3
You make an interesting point though, if I ODIN the entire stock MDL ROM, that could work. I'm just going to write over it with another ROM anyways, so what I restore to shouldn't matter. I know this is probably a dumb question, but flashing the stock MDL ROM isn't going to affect my MDL bootloader is it?
I can get TWRP 2.8.3.0 with or without Flashify, but that app is very convenient, thank you for the tip =)
Click to expand...
Click to collapse
Flashing the mdl firmware in Odin will still give you the mdl bootloader. But it'll want to update after you flash so flash another custom rom or freeze the update files before it does so.
Sent from my Nexus 5 using XDA Free mobile app
@ChrisG683 Be sure to turn your wi-fi off and remove your SIM card, that way it can't update. You can put any apps you think you might need on an SD card and install them without having to go to the play store. Once you get things frozen or removed then you'll be good to go. :good:
Thanks guys, I'll be sure to keep that in mind once I get things sorted out.
The newest thing I've figured out is that the MDL stock recovery does not give me the "yellow triangle" error, and it presents me with the option to wipe my device. (I grabbed it from here http://forum.xda-developers.com/showthread.php?t=2429406)
Now I'm just making sure I have a stock MDL ROM ready to ODIN in case I screw up my device =). Hopefully this all works out.
Edit:
Looks like everything went beautifully. The MDL stock recovery wiped my /data partition perfectly, and I was able to reboot into a fresh and clean copy of KANGAKAT 6.0. Then I was able to use a terminal to flash TWRP, did a factory reset, flashed KANGAPOP 1.4, and now you can add me to the list of proud Lollipop users =)
Hello
First let it be known that i have searched my butt off and tried many different things. The best i could get was a rooted phone and a non working safestrap install.
Can someone please give clear instructions here in this thread to either a) install safestrap on 4.4.2 nc4 or b) let me know if it's possible to install verizons stock lollipop firmware using odin (no recovery required).
I would love to get a working custom recovery to try different roms. Failing that, id love to know if it's possible to just flash stock lollipop firmware on this device.
I'm sorry to make such a request, as my first post.. But have been rooting and roming and xdaing since the Samsung vibrant. I'm just tired of trying to make this locked bootloader work. I must've tried a hundred different things.
As of right now ive odind back to 4.4.2 stock with nc4 kernel and said root, busybox, and supersu.
I'm familiar with odin, flashing, all the terminology, and can find the files on my own.
scottayy said:
Hello
First let it be known that i have searched my butt off and tried many different things. The best i could get was a rooted phone and a non working safestrap install.
Can someone please give clear instructions here in this thread to either a) install safestrap on 4.4.2 nc4 or b) let me know if it's possible to install verizons stock lollipop firmware using odin (no recovery required).
I would love to get a working custom recovery to try different roms. Failing that, id love to know if it's possible to just flash stock lollipop firmware on this device.
I'm sorry to make such a request, as my first post.. But have been rooting and roming and xdaing since the Samsung vibrant. I'm just tired of trying to make this locked bootloader work. I must've tried a hundred different things.
As of right now ive odind back to 4.4.2 stock with nc4 kernel and said root, busybox, and supersu.
I'm familiar with odin, flashing, all the terminology, and can find the files on my own.
Click to expand...
Click to collapse
Yes..you can flash stock firmware for 5.0 via Odin. You will lose root and as of this time....can not root 5.0
once on 5.0, you can only odin back to 4.4.4 which is also unrootable.
simplyeorange said:
Yeah you can go back to 4.4.4 I've read post of people on this forum saying they were able to get back to 4.4.4 you need to download the stock tar. Which you can find on sammobile than boot into download mode and then open Odin flash the stock tar. After its done flashing Then boot into stock recovery and do factory data reset. Wait about 5-10mins and should boot you into 4.4.4
Click to expand...
Click to collapse
Sent from my Note 3 via Tapatalk
Thanks for that. I'm sorry about the aggressive tone of my original post. I was just quite frankly mad at how much verizon locked the note 3 down. I own it, you know? Lol.
I wanted custom recovery mostly for the nandroid backups. If i flash the nc2 kernel on 4.4.2 with nc4 kernel... Supposedly this is supposed to make safestrap work with one rom slot (stock). I tried this but it soft bricked. Is there a custom nc2 kernel I'm supposed to flash?
Also if i odin the stock 5.0 files will this keep all user apps and data? I suppose i could use titanium backup for that but I'm not sure if it will be compatible from 4.4.2 to 5.0?
I guess i have to debate whether i want nandroid backup abilities or lollipop.
I have a Galaxy S4 AT&T i377 UCSGOK3 5.01. I have been fiddling with it and broke the recovery mode. When I select "reboot system now" it reboots, BUT has numerous "Unfortunately...has stopped" errors, finally resulting in unresponsive blank screen. I then have to factory reset and rebuild again. I CAN use recovery mode, IF I remove the battery instead of "reboot system now".
Here are the chain of events leading up this this:
- successfully rooted with Kingroot and replaced with Super SU
- attempted to install TWRP with "Official TWRP App" (I know, should not have done that)
- before attempting TWRP install, made backup of recovery.img (original one) with Official TWRP App
- tried to reinstall original recovery.img with Official TWRP App, Odin, and Flashify. Not working, does not boot into recovery mode.
- installed extracted NB1 recovery.img. From "AT&T Galaxy S4 SGH-I337 UCUFNB1 (Android 4.4.2)" with Odin. This one works, but has the reboot error problem.
Questions:
Is there a Stock AT&T OK3 firmware I can get a recovery.img from or will it still be a NB1 recovery?
Would it be helpful to do a complete re-install of stock firmware? Which one?
Can I install Safestrap on OK3?
Is there a fix for the numerous "Unfortunately...has stopped errors" after recovery reboot?
Thanks in advance,
Todd K.
The bootloader on the phone is locked and cannot run any version of TWRP or any custom ROM that is not based off a stock Samsung ROM.
The reboot problem may be due to a mismatch between the bootloader and recovery.
There is no stock OK3 ROM because AT&T never released a Odin-flashable version of the ROM. OK3 was only offered as an OTA update.
I suggest going back to stock OK3. This thread may help: https://forum.xda-developers.com/showthread.php?t=2616221
The S4 is a great phone and I still have one as my backup phone.
audit13 said:
I suggest going back to stock OK3. This thread may help:
Click to expand...
Click to collapse
Thanks Audit13. just to clarify, Do you suggest sticking with stock OK3 instead of safestrapping to some compatible custom ROM?
For some people, a rooted and no-bloat stock ROM is the most suitable as it's pretty stable and works with many apps.
You can try a custom ROM with safestrap but they'll all be based off a stock ROM which may not run the apps you need.
audit13 said:
For some people, a rooted and no-bloat stock ROM is the most suitable as it's pretty stable and works with many apps.
You can try a custom ROM with safestrap but they'll all be based off a stock ROM which may not run the apps you need.
Click to expand...
Click to collapse
Thanks, I got it to Stock OK3 rooted after a couple of tries. 1st time, I installed the rootable NB1, rooted with towelroot. It wouldn't take the upgrade zips to get from NB1 to OK3. I started over with the plain Stock NB1 ROM, then upgraded in steps from NB1 to OK3, no problem. Then kingrooted and replaced with SuperSU using root.sh script.
I then de-bloated with "System app remover (ROOT)" I wasn't sure what was safe to remove and was afraid of bricking it and having to start over, but it seems to be OK as I was conservative.
Which method do you recommend to de-bloat?
Finally is there a way to do a complete system, app, data, settings backup without CWM/TWRP? Safestrap? ADB? I have Titanium Backup but I don't think it will restore settings and ONLY the apps I want without the bloatware.
Thanks,
Todd K.
I have never owned the sgh-i337 as I'm in Canada and the sgh-i337m (unlocked bootloader, works with TWRP) is the version carried by Canadian carriers.
When dealing with bloatware, I either manually freeze or remove it with Titanium Backup.
toddk63 said:
Thanks, I got it to Stock OK3 rooted after a couple of tries. 1st time, I installed the rootable NB1, rooted with towelroot. It wouldn't take the upgrade zips to get from NB1 to OK3. I started over with the plain Stock NB1 ROM, then upgraded in steps from NB1 to OK3, no problem. Then kingrooted and replaced with SuperSU using root.sh script.
I then de-bloated with "System app remover (ROOT)" I wasn't sure what was safe to remove and was afraid of bricking it and having to start over, but it seems to be OK as I was conservative.
Which method do you recommend to de-bloat?
Finally is there a way to do a complete system, app, data, settings backup without CWM/TWRP? Safestrap? ADB? I have Titanium Backup but I don't think it will restore settings and ONLY the apps I want without the bloatware.
Thanks,
Todd K.
Click to expand...
Click to collapse
I use the mybackup app (formerly called my backup root) to debloat/freeze bloat. It's sort of like titanium backup. You can use flash fire on the play store to do a system backup without safe strap, just using safe strap is better and probably faster.