Related
This is perhaps a general Android question and one I have not found the magic search terms to find an answer. Before I mess with this phone, I'd like stock images of boot.img, recovery.img, and the OS itself. Is this possible without root?
I did a full adb backup (including shared stuff, system) but it's unclear if that will restore the phone to a factory state including the images above.
If anyone has any direction for me, much appreciated. Not getting far on my own. Thanks!
jaymzz said:
This is perhaps a general Android question and one I have not found the magic search terms to find an answer. Before I mess with this phone, I'd like stock images of boot.img, recovery.img, and the OS itself. Is this possible without root?
I did a full adb backup (including shared stuff, system) but it's unclear if that will restore the phone to a factory state including the images above.
If anyone has any direction for me, much appreciated. Not getting far on my own. Thanks!
Click to expand...
Click to collapse
Its not possible to create a nandroid backup without root. Remember, you can always odin the stock firmware after rooting if you'd like to return to stock. Hope that helps
C.Sweat said:
Its not possible to create a nandroid backup without root. Remember, you can always odin the stock firmware after rooting if you'd like to return to stock. Hope that helps
Click to expand...
Click to collapse
If anyone has that I9505G stock firmware to flash with Odin, I'd love to have it...
C.Sweat said:
Its not possible to create a nandroid backup without root. Remember, you can always odin the stock firmware after rooting if you'd like to return to stock. Hope that helps
Click to expand...
Click to collapse
Thanks - this is what I'd like to do, but I don't have the stock images to be able to do this. Also I don't have the ability to use Odin - I'm limited to its Linux counterpart heimdall which may explain the disconnect if Odin offers that service and heimdall does not. This is my first serious foray into Samsung - I'm missing some context I think.
I did locate "S4GE_v4_422.zip" which is supposed to be the stock ROM but it's obviously de-odexed and rooted. That may be fine for my use, but not necessarily a way back to day 0.
And I'd be happy to share the stock firmware if I can locate or download it from my phone.
Thanks for your help!
ack154 said:
If anyone has that I9505G stock firmware to flash with Odin, I'd love to have it...
Click to expand...
Click to collapse
Sorry, but im not sure where to find an Odin flashable Google Edition stock firmware (I can only find the flashable rom). Good luck
jaymzz said:
Thanks - this is what I'd like to do, but I don't have the stock images to be able to do this. Also I don't have the ability to use Odin - I'm limited to its Linux counterpart heimdall which may explain the disconnect if Odin offers that service and heimdall does not. This is my first serious foray into Samsung - I'm missing some context I think.
I did locate "S4GE_v4_422.zip" which is supposed to be the stock ROM but it's obviously de-odexed and rooted. That may be fine for my use, but not necessarily a way back to day 0.
And I'd be happy to share the stock firmware if I can locate or download it from my phone.
Thanks for your help!
Click to expand...
Click to collapse
No problem at all. Heimdall, like Odin, can flash the stock firmware as well. You can find the carrier specific flashable firmwares here
I think this is it...
http://forum.xda-developers.com/showthread.php?p=43500355
Not in a position to mount from work and see if it's rooted or not, but if I were bricked I don't think I'd care!
jaymzz said:
I think this is it...
http://forum.xda-developers.com/showthread.php?p=43500355
Not in a position to mount from work and see if it's rooted or not, but if I were bricked I don't think I'd care!
Click to expand...
Click to collapse
That's as close as we have right now. And yes, it is rooted. Mine prompted for SuperSU install as soon as it booted.
ack154 said:
And yes, it is rooted. Mine prompted for SuperSU install as soon as it booted.
Click to expand...
Click to collapse
Hello everyone-
New user for the Samsung Galaxy S4 here. I used to own both the iPhone 3GS and 4S prior. My general background was writing VB in version 3.0 for AOL back in the late 90s for all you old school people, progs/punters that may remember those days. Unfortunately, even now I'm still have issues following along with new technology. So far, I have really enjoyed the android system and have made modifications through various launchers. I did use SuperSU and rooted the phone by the automated process. I realize these may be 'noob' questions, however; everyone I suppose goes through it at some point. I do have some general questions and several of them that I have read about have conflicting information. This will be somewhat long, but I do appreciate any input:
The Galaxy S4 that I have is SPH-L720, MK2, and 4.3 version.
At this point, I backed-up and installed several Google Games, Books, and Sprint ID, Sprint Worldwide, etc.....general bloatware using Titanium Back-up. Again the root method I used was SuperSU by Chainfire. I have NOT use TWRP/Clockwork Mod or flashed any custom ROMs. I just have it rooted and diabled some bloatware, installed Xposed Installer and other root only apps. I checked my phone and its status says 'custom'.
1. Given this set-up, can I still get OTA for new Android versions ? I don't care if it removes root, but I was just wondering if I can get OTA updates to get new versions for my phone. Some threads I have read say yes, others say no. If I cannot, how can I then get new updates ? I don't want to not be able to permanently update to 4.4 in the future. I know there is a way to update via Kies to the computer.
2. The root access via Chainfire SuperSU involves 2 components from what I understand. SU.apk and busybox. I was using Terminal Emulator based on the advice from this thread: http://forum.xda-developers.com/showthread.php?t=2565758
I could not get it to work when typing in the prompts on the screen, it just would not go through. I tried downloading Total Commander which allows root access. Can I instead of using Terminal Emulator to get rid of busybox, use Total Commander to get into the /system/xbin folder and manually delete all busybox files prior to using the permanent unroot of SuperSU feature in settings ? Or does the Full unroot remove everything ?
3. Maybe I still don't understand the flashing process, but it seems, you download Odin, then use the ROM file you need under the PDA selection then start the process while the phone is in download mode (home button, down volume, etc...) Is this how all custom ROMs and re-stores are performed ? Is this form of the restore different that the phone Samsung settings (back-up/restore) ? I've read about TWRP, custom recovery, Clockwork Mod, etc....but I dont understand what all these are. It seems easy enough to download files then put them via Odin then hit start....
At this point, I've refrained from doing anything other than back-up/uninstalling some bloatware and using some cool apps that supposed xposed installer. I'm worried that I might brick my expensive phone or render it unable to get anymore updates :crying:
Thanks for the input !
mikeprius said:
Hello everyone-
New user for the Samsung Galaxy S4 here. I used to own both the iPhone 3GS and 4S prior. My general background was writing VB in version 3.0 for AOL back in the late 90s for all you old school people, progs/punters that may remember those days. Unfortunately, even now I'm still have issues following along with new technology. So far, I have really enjoyed the android system and have made modifications through various launchers. I did use SuperSU and rooted the phone by the automated process. I realize these may be 'noob' questions, however; everyone I suppose goes through it at some point. I do have some general questions and several of them that I have read about have conflicting information. This will be somewhat long, but I do appreciate any input:
The Galaxy S4 that I have is SPH-L720, MK2, and 4.3 version.
At this point, I backed-up and installed several Google Games, Books, and Sprint ID, Sprint Worldwide, etc.....general bloatware using Titanium Back-up. Again the root method I used was SuperSU by Chainfire. I have NOT use TWRP/Clockwork Mod or flashed any custom ROMs. I just have it rooted and diabled some bloatware, installed Xposed Installer and other root only apps. I checked my phone and its status says 'custom'.
1. Given this set-up, can I still get OTA for new Android versions ? I don't care if it removes root, but I was just wondering if I can get OTA updates to get new versions for my phone. Some threads I have read say yes, others say no. If I cannot, how can I then get new updates ? I don't want to not be able to permanently update to 4.4 in the future. I know there is a way to update via Kies to the computer.
2. The root access via Chainfire SuperSU involves 2 components from what I understand. SU.apk and busybox. I was using Terminal Emulator based on the advice from this thread: http://forum.xda-developers.com/showthread.php?t=2565758
I could not get it to work when typing in the prompts on the screen, it just would not go through. I tried downloading Total Commander which allows root access. Can I instead of using Terminal Emulator to get rid of busybox, use Total Commander to get into the /system/xbin folder and manually delete all busybox files prior to using the permanent unroot of SuperSU feature in settings ? Or does the Full unroot remove everything ?
3. Maybe I still don't understand the flashing process, but it seems, you download Odin, then use the ROM file you need under the PDA selection then start the process while the phone is in download mode (home button, down volume, etc...) Is this how all custom ROMs and re-stores are performed ? Is this form of the restore different that the phone Samsung settings (back-up/restore) ? I've read about TWRP, custom recovery, Clockwork Mod, etc....but I dont understand what all these are. It seems easy enough to download files then put them via Odin then hit start....
At this point, I've refrained from doing anything other than back-up/uninstalling some bloatware and using some cool apps that supposed xposed installer. I'm worried that I might brick my expensive phone or render it unable to get anymore updates :crying:
Thanks for the input !
Click to expand...
Click to collapse
I can answer 1 & 3 for you.
1. No, you won't be able to take an OTA because you removed or modified system files. This will cause the update file of the OTA to abort once it encounters the modded file or can't find the file your removed. The best process to take an OTA would be to return the phone to stock before taking the OTA. The easiest method is to use Odin and install the full stock tar file that you are currently on. In your case it would be the MK2 tar file. This will return your phone to stock with the stock recovery and allow your phone to update via OTA, then you can re root.
3. Odin is used to flash things like stock tar files, modems(basebands), recoveries & firmwares. If you are installing a custom rom, that is usually done using a custom recovery like Phillz's or TWRP. These recoveries can be installed via odin or TWRP via goomanager app in playstore. Once the custom recovery is installed you copy the rom file or other mod to your sdcard and install through recovery.
cruise350 said:
I can answer 1 & 3 for you.
1. No, you won't be able to take an OTA because you removed or modified system files. This will cause the update file of the OTA to abort once it encounters the modded file or can't find the file your removed. The best process to take an OTA would be to return the phone to stock before taking the OTA. The easiest method is to use Odin and install the full stock tar file that you are currently on. In your case it would be the MK2 tar file. This will return your phone to stock with the stock recovery and allow your phone to update via OTA, then you can re root.
3. Odin is used to flash things like stock tar files, modems(basebands), recoveries & firmwares. If you are installing a custom rom, that is usually done using a custom recovery like Phillz's or TWRP. These recoveries can be installed via odin or TWRP via goomanager app in playstore. Once the custom recovery is installed you copy the rom file or other mod to your sdcard and install through recovery.
Click to expand...
Click to collapse
Thanks for the response....Does it matter what version of Odin I use if I were to restore the phone back to stock ? Also do I need to manually remove all rooted program and features, or can it be flashed back to stock ROM as is ? I have a lot of apps that I also don't want to lose and I've tried manually back up files on my SD card, but I didn't know if there was a way to back it up, so that it literally can be dumped right back in when stock is restored.
mikeprius said:
Thanks for the response....Does it matter what version of Odin I use if I were to restore the phone back to stock ? Also do I need to manually remove all rooted program and features, or can it be flashed back to stock ROM as is ? I have a lot of apps that I also don't want to lose and I've tried manually back up files on my SD card, but I didn't know if there was a way to back it up, so that it literally can be dumped right back in when stock is restored.
Click to expand...
Click to collapse
I believe if you are on MK2 you will want to use the latest version of odin which is ver3 3.09. If you are using the MK2 complete stock tar file it will rewrite everything in system and restore all the apps that were removed or modded so you don't need to manually remove root. Currently, the stock files available to us do not wipe the data partition so anything you have in that partition will remain there unless you do a factory reset. One thing you will want to make sure you are doing is backing up to the external sdcard and not the internal. You can then use TB to replace any files if you did a factory reset.
cruise350 said:
I believe if you are on MK2 you will want to use the latest version of odin which is ver3 3.09. If you are using the MK2 complete stock tar file it will rewrite everything in system and restore all the apps that were removed or modded so you don't need to manually remove root. Currently, the stock files available to us do not wipe the data partition so anything you have in that partition will remain there unless you do a factory reset. One thing you will want to make sure you are doing is backing up to the external sdcard and not the internal. You can then use TB to replace any files if you did a factory reset.
Click to expand...
Click to collapse
I'm using Kies 3 and using the data back-up feature ? I assume this is backing up to the computer then I was planning on using the 'restore data' feature once they phone is back to stock. Will this revert it back to the way it was previously customized before root ? So if I understand correctly, once I download Odin 3.0, I load the MK2 .tar file into the phone, enbable download mode, then hit start and the phone will be like it was out of the box and ready to be OTA and restored with prior data ? I may be confusing flashing the stock firmware with factory reset ?
I also noticed there is an update firmware feature on Kies 3, if I try using this while SuperSU is present and the phone is rooted, will I also have a failed update/issues ? Again, thanks for your help. Do appreciate it.
mikeprius said:
I'm using Kies 3 and using the data back-up feature ? I assume this is backing up to the computer then I was planning on using the 'restore data' feature once they phone is back to stock. Will this revert it back to the way it was previously customized before root ? So if I understand correctly, once I download Odin 3.0, I load the MK2 .tar file into the phone, enbable download mode, then hit start and the phone will be like it was out of the box and ready to be OTA and restored with prior data ? I may be confusing flashing the stock firmware with factory reset ?
I also noticed there is an update firmware feature on Kies 3, if I try using this while SuperSU is present and the phone is rooted, will I also have a failed update/issues ? Again, thanks for your help. Do appreciate it.
Click to expand...
Click to collapse
I have never used Kies and heard that it doesn't work with the MJA or MK2 software yet. I don't believe Kies will work if your status is custom but I could be wrong on that. If you odin the MK2 full tar file your phone will be back to stock but your data should still be there. You will only lose your data if you do a factory reset in recovery. Remember, a factory reset is just wiping the data partition and does not restore any software or apps.
cruise350 said:
I have never used Kies and heard that it doesn't work with the MJA or MK2 software yet. I don't believe Kies will work if your status is custom but I could be wrong on that. If you odin the MK2 full tar file your phone will be back to stock but your data should still be there. You will only lose your data if you do a factory reset in recovery. Remember, a factory reset is just wiping the data partition and does not restore any software or apps.
Click to expand...
Click to collapse
Ok, I think I have the general idea. It sounds similar to putting back on the stock 'image' nothing else.........I currently have the Odin 3.0 software, but I have been having a hard time finding the stock firmware online and downloading it. I will keep looking. Once I get the .tar and flash in download mode, will I just see all the bloatware back on, but everything else the same ? I was wondering what will happen if I kept Titanium Back-up, SuperSU, and Xposed Installer on when I do this ? Does it just render them all un-useable, but the new OTA will still install anyway ? Thanks.
mikeprius said:
Ok, I think I have the general idea. It sounds similar to putting back on the stock 'image' nothing else.........I currently have the Odin 3.0 software, but I have been having a hard time finding the stock firmware online and downloading it. I will keep looking. Once I get the .tar and flash in download mode, will I just see all the bloatware back on, but everything else the same ? I was wondering what will happen if I kept Titanium Back-up, SuperSU, and Xposed Installer on when I do this ? Does it just render them all un-useable, but the new OTA will still install anyway ? Thanks.
Click to expand...
Click to collapse
Every thing in the data partition(titanium backup) will remain and everything in the system partition (SuperSU & stuff modified via xposed installer) will be gone and replaced with the bloatware.
Sent from my SPH-L720 using Tapatalk
Ok, so it appears to have worked. I flashed the 4.3 prior version however it was hooked up to wifi and automatically downloaded the new version and removed root (not a big deal). My status says custom still, but I am assuming that I can OTA after the flash b/c it updated to the most recent 4.3 in Dec 2013. I re-rooted so it is back to prior, but I know now how to do it.
Is there anything that I may delete or uninstall that cannot be replaced by flashing the stock firmware ? For example I was thinking about getting rid of the 'help' on the phone and Titanium Back up said it is odexed or something to that extent and can only be replaced by using Titanium Backup and the exact same copy ?
I figured that I might as well just try deleting the bloatware and not back up b/c worse case scenario if something happens I can just flash back the stock ROM and all is well ?
Being able to flash the stock .tar through ODIN gives me peace of mind from screw ups, even if it removes root and takes time.
mikeprius said:
I figured that I might as well just try deleting the bloatware and not back up b/c worse case scenario if something happens I can just flash back the stock ROM and all is well ?
Click to expand...
Click to collapse
If you haven't spent much time customizing, that'll work fine. Most of us use custom recoveries (like Philz or TWRP) to make "nandroid" backups of our setups. A nandroid is like a drive image on a computer, so restoring it will restore all of the customizations you've done (accounts, apps, app data, bloatware deletions, etc). Nandroids don't back up firmware (modem, bootloader,etc), but back up the ROM completely. A Titanium backup is almost as good, but requires a bit more work.
As for deciding what apps you can delete, most of the custom ROM creators post a list of the bloatware they remove. So, if it's on their list, it's almost certainly ok to delete it on your phone too.
nobody291 said:
If you haven't spent much time customizing, that'll work fine. Most of us use custom recoveries (like Philz or TWRP) to make "nandroid" backups of our setups. A nandroid is like a drive image on a computer, so restoring it will restore all of the customizations you've done (accounts, apps, app data, bloatware deletions, etc). Nandroids don't back up firmware (modem, bootloader,etc), but back up the ROM completely. A Titanium backup is almost as good, but requires a bit more work.
As for deciding what apps you can delete, most of the custom ROM creators post a list of the bloatware they remove. So, if it's on their list, it's almost certainly ok to delete it on your phone too.
Click to expand...
Click to collapse
Thanks being able to flash the stock .tar and use ODIN gives me peace of mind of any potential screw ups. So far I'm just using stock rom and toggling some of the features with xposed installer and titanium back up.
I'd like to explore more eventually with custom ROMs and I've heard of Clockwork mod and TWRP, Nandroid, Cyanogen, etc... but I don't know what any of that means or what it is.
Is TWRP/Philz like ODIN program then you download custom ROMS like Cyanogen the same way as the stock firmware. tar ?
As you can tell I am extremely new to this.....this is also my first time owning an Android phone as well, but I never messed with jailbreaking my past 2 iPhones in the past. I just have used VB 3.0 back in the day....
mikeprius said:
Thanks being able to flash the stock .tar and use ODIN gives me peace of mind of any potential screw ups. So far I'm just using stock rom and toggling some of the features with xposed installer and titanium back up.
I'd like to explore more eventually with custom ROMs and I've heard of Clockwork mod and TWRP, Nandroid, Cyanogen, etc... but I don't know what any of that means or what it is.
Is TWRP/Philz like ODIN program then you download custom ROMS like Cyanogen the same way as the stock firmware. tar ?
As you can tell I am extremely new to this.....this is also my first time owning an Android phone as well, but I never messed with jailbreaking my past 2 iPhones in the past. I just have used VB 3.0 back in the day....
Click to expand...
Click to collapse
To me, one of the hardest parts of this whole thing is getting to the point where the basic terms make sense. I've been at this for a couple of years with an HTC Evo and now the GS4 since October, and sometimes it still makes my head spin. Here is an attempt to explain my understanding of a few things:
1. Booting...you can boot into Download mode, recovery, or system. Download mode is what you use with ODIN, you need the correct drivers on your computer (which can be found lots of places), so that ODIN and your phone can communicate. In download mode, the phone just accepts whatever ODIN sends it, so it's the easiest way to totally brick your phone. Don't mess with partitions and follow the instructions for whatever you're doing very carefully, because I think this is the only way to "hard brick" your phone.
2. Recovery - something you use to create images of your phone's ROM (nandroids), flash ROMs and mods, and restore past nandroids. The stock recovery will only flash approved updates from the carrier, so to do any of the things I listed you need a custom recovery. Most people use Philz (which is based on the ClockworkMod recovery) or TWRP. To flash the custom recovery, use ODIN and follow the instructions in the thread exactly. There is a way to flash recoveries without ODIN, but I've never done it. I was using TWRP, and switched to Philz to flash the rooted stock 4.3 update because the thread suggested it. They both seem to do the same thing, and I have been happy with both. I'm sure there are technical differences, but I couldn't explain what they are. You can switch back and forth as much as you'd like between the recoveries with ODIN. Recoveries can flash a complete ROM or just partial changes (like the hotspot mod). In a custom recovery (or the stock) you can also do factory resets and cache cleaning (most ROMs suggest you do this before flashing). Factory reset doesn't return the ROM to the factory original, it just clears out all of the user data (including user apps). A nandroid is the fastest way to restore a phone if you screw it up...I always make one before making significant changes to the phone. It takes several minutes to do, but I think it's well worth it. The operating system can't be running when you make one, that's why you need to boot into recovery mode. You create a Nandroid in Philz by selecting "backup and restore" then "backup to" which will allow backup to the internal storage or external SD card.
3. ROM - the actual operating system used by the phone when you actually use it as a smartphone. There are 2 basic flavors for the GS4...touchwiz and AOSP (Android Open Source Project). Touchwiz is Samsung's "flavor" of Android, AOSP is the "pure Google" version of Android. A lot of the things the GS4 will do rely on touchwiz (multiwindow is one example...but there are several). Some people really like the AOSP ROMs (Cyanogen is AOSP), but make sure you understand their limitations. I've never used one on the GS4. There are several touchwiz custom ROMs which have various features. I've tried a few and just settled on the stock rooted touchwiz ROM, but there are lots of options from great developers. I think most custom ROMs require you to use a custom recovery to flash them, but there might be ways to do it using ODIN. I like having a custom recovery, so I've only used ODIN for flashing modems and recoveries.
4. Firmware - as far as I can tell, there are two important parts of the firmware...the modem (sometimes called "radios" or "baseband"...find your version by looking in "about device"->"Baseband version"...the different modems are described by the last 3 letters you see) and the bootloader. The modem and the version of the ROM you flash need to match or you'll have problems with the radios in the phone (wifi seems to be the biggest problem if you have a mismatch). MF9 was the last modem version based on 4.2.2, and 4.3 has had MJA and MK2 (MK2 is the latest). The bootloader is what the phone uses to initially decide how to boot up. If you have the 4.3 version of the bootloader it will include "Knox", which will prevent you from flashing older versions of the modem, so you'll have to use a 4.3 ROM. Knox also "trips" a counter if you flash a custom ROM and Samsung claims they won't honor the warranty on a phone with the "Knox flag" tripped. If you have the 4.3 bootloader you're stuck with it (for now at least). I still have the 4.2.2 bootloader, so I don't have much more to offer on this subject. There are ways to get the 4.3 modem and ROM without the 4.3 bootloader. There is a lot here (and lots on youtube) on how to navigate the Knox minefield if you care about it. If you still have the 4.2.2 bootloader you can flash older (and newer) modems as much as you'd like without getting the updated bootloader using ODIN.
Hopefully this helps...this is a great place with lots of great people. Sometimes the scale of the amount of information here is overwhelming. But, search is your friend along with lots of time! Feel free to keep asking questions.
thanks for explaining this nobody-
The information does help quite a bit and I am still learning, however; I do enjoy the process of messing with the phone. My GS4 now runs the RAM at 750-800mg instead of a bloated 1.2GB which was happening quite a bit. I had to originally not use a lot of apps I wanted to like Facebook bc the programs themselves bloated up to accomidate the existing bloatware which was also running. I did flash my phone back with the stock firmware today and it looks like it installed all the stock software. My status said 'custom' when I looked at it however I was already connected to wifi and it went from 4.3 (Oct 2013 version which I flashed) to Dec 2013 version automatically so it appears that the OTA feature works.
I assumed if I accidently delete something from the phone that I really need to affects the phone, I can always flash the stock ROM to fix it. Losing the root is not that big of an issue, but I did lose Superuser and had to re-root the phone. I suppose I do have a few more questions, one was when I was reading another carrier provider thread.
1. Is there anything I can delete from the phone that I could not eventually recover by flashing the stock firmware ? When I uninstall for example the 'help' app on the phone Titanium Backup says this only copy can be replaced by using Titanium 5.1 and it's existing copy ? Could this just be replaced by flashing the stock firmware as well ? I like being able to flash the stockfirm ware rom at any point as a fail safe.
2. The other issue is the bootloader that I heard about ? It was on a Verizon thread where the person was able to flash the stock firmware on his phone, but then after an upgrade, he was not longer able to flash the rom b/c the carrier in the most recent upgrade he did blocked ODIN ? Is this something that I should possibly be concerned about in the future not being able to flash stock firmware via ODIN ? As you can tell, I'm pretty OCD about being able to have a failsafe for my phone. LOL. Thanks again for your help, I do appreciate it.
mikeprius said:
1. Is there anything I can delete from the phone that I could not eventually recover by flashing the stock firmware ? When I uninstall for example the 'help' app on the phone Titanium Backup says this only copy can be replaced by using Titanium 5.1 and it's existing copy ? Could this just be replaced by flashing the stock firmware as well ? I like being able to flash the stockfirm ware rom at any point as a fail safe.
Click to expand...
Click to collapse
Yes, you can always flash the stock firmware to fix whatever you do to the ROM (just to the ROM, use ODIN very carefully). In the case of the Help file, you could also back it up using Titanium, then delete the app, and restore it later using Titanium if you want it back. This is probably obvious, but use Titanium to delete the app, but don't delete the backup.
2. The other issue is the bootloader that I heard about ? It was on a Verizon thread where the person was able to flash the stock firmware on his phone, but then after an upgrade, he was not longer able to flash the rom b/c the carrier in the most recent upgrade he did blocked ODIN ? Is this something that I should possibly be concerned about in the future not being able to flash stock firmware via ODIN ? As you can tell, I'm pretty OCD about being able to have a failsafe for my phone. LOL. Thanks again for your help, I do appreciate it.
Click to expand...
Click to collapse
Sprint is a lot more friendly toward its users modifying their phones than Verizon. But, they could change their minds any time. For now, there are no issues (other than the Knox warranty issue). But, don't presume that'll always be the case. The best precaution is to not take OTA (over the air) updates. OTAs are the ones that pop up as a notification on the phone saying "system update available, tap to install". Kit Kat should become available in the next month or two, who knows what'll come along with the OTA. Threads will start here almost immediately when the update rolls out; watch those threads and don't do the update until you're comfortable with what's inside. I will wait and flash something from the development section, even if it is just the stock ROM.
nobody291 said:
Yes, you can always flash the stock firmware to fix whatever you do to the ROM (just to the ROM, use ODIN very carefully). In the case of the Help file, you could also back it up using Titanium, then delete the app, and restore it later using Titanium if you want it back. This is probably obvious, but use Titanium to delete the app, but don't delete the backup.
Sprint is a lot more friendly toward its users modifying their phones than Verizon. But, they could change their minds any time. For now, there are no issues (other than the Knox warranty issue). But, don't presume that'll always be the case. The best precaution is to not take OTA (over the air) updates. OTAs are the ones that pop up as a notification on the phone saying "system update available, tap to install". Kit Kat should become available in the next month or two, who knows what'll come along with the OTA. Threads will start here almost immediately when the update rolls out; watch those threads and don't do the update until you're comfortable with what's inside. I will wait and flash something from the development section, even if it is just the stock ROM.
Click to expand...
Click to collapse
It was good that you mentioned the Knox bootloader issue with the 4.3 upgrade. When I purchased my cell phone back in Nov, I believe it had the 4.3 (1st) version loaded, but it already had Knox features as I do recall seeing them. If I were to try and flash 4.2.2 like the version you initially had, would the phone have a bootloop error or fail to flash because there were some free wifi tethering exploits that were not yet fixed in the 4.2.2 version ? This may have been the error I read about due to the new Knox feature.
I think since my phone is currently rooted and I altered some of the bloatware system files that the update if it were made available OTA should not update anyway due to the root. Will the stock ROM/firmware .tar files eventually be posted in the developers section that can just be flashed via ODIN later on ? With that, if I were to load 4.4 and not like it, could I flash back 4.3 ? I am guessing this is the part where you mentioned that the carrier may decide differently later on.....I suppose I will just keep an eye out in the meantime.
Good good............, I'm picking up this pretty well so far.............
mikeprius said:
If I were to try and flash 4.2.2 like the version you initially had, would the phone have a bootloop error or fail to flash because there were some free wifi tethering exploits that were not yet fixed in the 4.2.2 version ?
Click to expand...
Click to collapse
I'm not sure what symptoms you'd see if you installed 4.2.2 with the 4.3 bootloader. Most likely the phone would fail to boot. ODIN will flash whatever you tell it to, I don't believe it does any compatibility checking on its own. You can still get the wifi hotspot feature to work even with Knox and the 4.3 bootloader, I don't think that was what they were trying to do with the update. There are threads discussing 4.3 and what changed, but there wasn't much obvious to the user. For now you can't go back if you're on 4.3, but there might be an exploit discovered down the road that lets you get the old bootloader and go back.
Will the stock ROM/firmware .tar files eventually be posted in the developers section that can just be flashed via ODIN later on ?
Click to expand...
Click to collapse
Yes, they won't be available immediately though. It can take some time for the community to re-obtain root too, depending on how big the changes are.
With that, if I were to load 4.4 and not like it, could I flash back 4.3 ?
Click to expand...
Click to collapse
I think you alluded to the answer already, but it depends. It took a month or two before you could flash the stock 4.3 without the 4.3 bootloader. There were custom ROMs available that used custom kernels sooner, but there was a problem trying to use the stock kernel with the 4.2.2 bootloader. So, always read and read and read some more before flashing updates.
So far i think i got the hang of it. I have been modifying the phones original touchwhiz. I ended up freezing alot of files instead of deleting them so the ability to turn them back on is there. Some of the files while there are not meant to be frozen/disabled/turned off. I tried a few methods for keeping SuperSU over an ODIN with no luck. I do have a question though. If i turned off (but did not delete) alot of system files and were to run ODIN again will all of them including the bloatware be turned back on and restored? That would be bad if i flashed, lost root, then simultaneously had all the system files disabled with no way to turn them back on......
This also a dumb question but what exactly am i flashing with ODIN? Its a 1.5 GB file with Sprint and it is a tar that restores all bloatware and turns the phone status back to official so i can get OTA updates. Am i flashing the entire stock ROM or just the firmware? Its nice that i have not lost any existing apps or data. It just restores the bloatware and removes root
Reading the above posts im guessing firmware....along the lines of the previous question will this restore system files and apps as well that have been shut off because ive been on a roll disabling and freezing a lot of files and apps and not sure what to turn back on to restore function to some of them. If the ODIN firmware flash resets all settings then that will also be very useful as well. Thanks much
mikeprius said:
Reading the above posts im guessing firmware....along the lines of the previous question will this restore system files and apps as well that have been shut off because ive been on a roll disabling and freezing a lot of files and apps and not sure what to turn back on to restore function to some of them. If the ODIN firmware flash resets all settings then that will also be very useful as well. Thanks much
Click to expand...
Click to collapse
The .tar you are flashing from sprint is what we would call stock firmware image. This is the image that shipped on the phone from the factory. I'm an avid flasher and would highly recommend installing twrp or philz touch, creating a nandroid backup and giving some debloated touchwiz roms a shot. You'll see some significant improvement in battery life and performance and some really cool upstream features. I use odin as a last resort, when I need to go back to stock for whatever reason (ie domestic sim unlock) or have fubar'd my current setup past a point of no return.
So I first rooted my phone yesterday and it went smoothly. Then, I had an option to software update and it was late at night so I just did it without thinking and now I'm missing my download app that comes stock. Also, I can't root anymore to fix it because it updated my kernel version but I still get the custom logo on the galaxy s5 splash screen. Can anyone help me with this? I have already factory reset my phone many times. BTW it's the verizon version.
fdfvh said:
I'm missing my download app that comes stock. Also, I can't root anymore to fix it because it updated my kernel version
Click to expand...
Click to collapse
Well, had you done a search, you'd already have answers to your questions. There is a wealth of information in existing threads.
Software updates almost always break root. So that is expected behaviour. You didn't give us much information about your missing download app, but if that is a system app then writing the full stock firmware image would restore that. And if you choose a pre June 3rd build of your firmware, it should be amenable to the Towel root exploit.
.
fffft said:
Well, had you done a search, you'd already have answers to your questions. There is a wealth of information in existing threads.
Software updates almost always break root. So that is expected behaviour. You didn't give us much information about your missing download app, but if that is a system app then writing the full stock firmware image would restore that. And if you choose a pre June 3rd build of your firmware, it should be amenable to the Towel root exploit.
.
Click to expand...
Click to collapse
Thing is, I don't know how to do that and I don't want to break my phone further. The app is missing from the app drawer. I can access it by downloading something off of the browser but that's the only way I can use it on stock touchwiz. I use Nova launcher and one of my backups happened to have the downloads app on my home screen so I can get to it that way but it's still missing from my app drawer. If you can, can you lead me to a trusted post so I can fix this because I don't want to screw up my phone anymore. I can't use odin to flash a stock firmware so I don't know how else I can do it.
Option 1:-
Try flashing a custom recovery first via download mode.
Then try flashing a custom rom.
Option 2:-
Download an older version of the stock rom.
Flash it via odin
Gl and I hope you can root again
la2o said:
Option 1:-
Try flashing a custom recovery first via download mode.
Then try flashing a custom rom.
Option 2:-
Download an older version of the stock rom.
Flash it via odin
Gl and I hope you can root again
Click to expand...
Click to collapse
How can I do this exactly?
uh oh... Doesn't sound too good. Sorry for the bad fortune.
Hello there,
So, I have a Samsung Galaxy S5 G900R4 with U.S. Cellular. I've heard of rooting your phone, and I decided I'd give it a try. Now, the rooting went fine, and the phone was working like a charm, until I started to have some issues. SuperSU needed to update its binary, and I allowed it to try, but it continued to tell me that it could not update it. Hence, I let it reboot when it offered. Now, for whatever reason, the phone won't boot past the U.S. Cellular 4G logo that appears, it just sits there on that screen.
Now so far, I haven't been able to find anyone that has encountered this specific problem, as most people say their soft-bricks are bootlooping and whatnot. I'm not sure if my specific case is technically a soft brick, or something else, but I wanted to just return it to stock format. I loaded up Odin again, downloaded the 1.5g firmware file, and I got the SW REV CHECK FAIL error.
I did some research, and I searched EVERYWHERE, and the closest I could find to a solution was http://forum.xda-developers.com/showthread.php?t=2798396 <-- this thread. Which makes sense, when I read it. I'm guessing the bootloader is locked on my phone, or something. The problem is that this thread is for the Galaxy S5 G900AU, and I don't have that phone.
Maybe I'm just not searching on the web enough, or I didn't search the site well enough, but I have not been able to locate a similar set of AP, CP and CSC files for my specific model.
I would really appreciate it if someone could point me in the right direction or, if the issue I'm actually having with my phone is NOT a soft-brick and there is another solution, suggest another way for me to fix the phone.
Thank you.
First off, I'd try clearing the caches from recovery
If that fails, factory reset from recovery
If that fails, (And I'm not sure about stock firmwares with ODIN & locked bootloaders) I'd try flashing stock from ODIN also
Grab stock ROMs from here
sammobile . com / firmwares / database /SM-G900R4/
Can't link it here, as SM links are not allowed - just remove the spaces
*Detection* said:
First off, I'd try clearing the caches from recovery
If that fails, factory reset from recovery
If that fails, (And I'm not sure about stock firmwares with ODIN & locked bootloaders) I'd try flashing stock from ODIN also
Grab stock ROMs from here
sammobile . com / firmwares / database /SM-G900R4/
Can't link it here, as SM links are not allowed - just remove the spaces
Click to expand...
Click to collapse
Well last night I went ahead and used recovery to clear cache, and then I did a factory reset. I just did it again, now, but I guess I'll have to download the file from SM to try. I already have a stock ROM, but I can't remember where I downloaded it from, so it may actually be a 4.4.2 ROM or something, which would explain why it won't work. I'll wait for the 5.0 ROM to download and give it a try, should take a little more than an hour and a half, then I'll report back.
Xeretius said:
Well last night I went ahead and used recovery to clear cache, and then I did a factory reset. I just did it again, now, but I guess I'll have to download the file from SM to try. I already have a stock ROM, but I can't remember where I downloaded it from, so it may actually be a 4.4.2 ROM or something, which would explain why it won't work. I'll wait for the 5.0 ROM to download and give it a try, should take a little more than an hour and a half, then I'll report back.
Click to expand...
Click to collapse
Try this link, if it works, it won't work for long
Code:
http://am4-r1f4-stor08.uploaded.net/dl/800e713b-624b-4a91-a57c-1639c6b5071e
*Detection* said:
Try this link, if it works, it won't work for long
Click to expand...
Click to collapse
It worked, it's downloading now, just have to give it some time.
nice one
*Detection* said:
nice one
Click to expand...
Click to collapse
I really hope this works, when it finishes >.>
Any idea what's happening with the phone to cause it to stay at the U.S. Cellular screen?
I never let SuperSU reboot when I let it update the binaries
Could be a number of things, possibly just corrupted a file necessary for boot, but as SuperSU has root, it could be anything
I don't know the ins and outs of how SuperSU works, but I know a few carrier specific US S5s have a locked bootloader, Verizon, AT&T etc - not sure if rebooting to allow the binary update requires an unlocked bootloader, maybe that bricked it, half assed attempt at a root process failed maybe
*Detection* said:
I never let SuperSU reboot when I let it update the binaries
Could be a number of things, possibly just corrupted a file necessary for boot, but as SuperSU has root, it could be anything
I don't know the ins and outs of how SuperSU works, but I know a few carrier specific US S5s have a locked bootloader, Verizon, AT&T etc - not sure if rebooting to allow the binary update requires an unlocked bootloader, maybe that bricked it, half assed attempt at a root process failed maybe
Click to expand...
Click to collapse
As far as I know, though, U.S. Cellular has confirmed that this device has an unlocked bootloader. And besides that, if it were locked, wouldn't that have come up as an issue when I rooted the device? I used the CWM custom recovery tool.
On a similar note, I'm not even sure if the problem was a locked bootloader. It's just that, from what I've read with other people having the same issue, they solved it by excluding the BL file from the flash and instead only using the AP, CP and CSC files.
Xeretius said:
As far as I know, though, U.S. Cellular has confirmed that this device has an unlocked bootloader. And besides that, if it were locked, wouldn't that have come up as an issue when I rooted the device? I used the CWM custom recovery tool.
On a similar note, I'm not even sure if the problem was a locked bootloader. It's just that, from what I've read with other people having the same issue, they solved it by excluding the BL file from the flash and instead only using the AP, CP and CSC files.
Click to expand...
Click to collapse
If you can flash anything custom from ODIN, bootloader is unlocked, afaik, locked bootloaders require a right mess on to get anything flashed to them
To root with a locked bootloader, is easily possible if you're on a certain KitKat ROM, and use Towelroot - other than that, (From what I've read), you need to use specific tools, so it sounds like your bootloader is indeed unlocked - which makes this next ROM flash, much more likely to work using only ODIN
Use ODIN 3.10.6 though
My experience with the S5 is with an unlocked bootloader (G900F), so I can only quote what I know about locked from what I've read, but it sounds like that doesn't matter in your case
*Detection* said:
If you can flash anything custom from ODIN, bootloader is unlocked, afaik, locked bootloaders require a right mess on to get anything flashed to them
To root with a locked bootloader, is easily possible if you're on a certain KitKat ROM, and use Towelroot - other than that, (From what I've read), you need to use specific tools, so it sounds like your bootloader is indeed unlocked - which makes this next ROM flash, much more likely to work using only ODIN
Use ODIN 3.10.6 though
My experience with the S5 is with an unlocked bootloader (G900F), so I can only quote what I know about locked from what I've read, but it sounds like that doesn't matter in your case
Click to expand...
Click to collapse
It worked! Thank you so much for the help, I really appreciate it.
Well, my warranty is now void. Is there a safer way to root the phone, or should I just leave it be?
Xeretius said:
It worked! Thank you so much for the help, I really appreciate it.
Well, my warranty is now void. Is there a safer way to root the phone, or should I just leave it be?
Click to expand...
Click to collapse
Great
Flashing a stock ROM won't void your warranty, but if it is indeed void (KNOX 0x1), then just flash this with ODIN
http://download.chainfire.eu/404/CF-Root1/CF-Auto-Root-klteusc-klteusc-smg900r4.zip
Tripping KNOX only happens when you flash something not signed by Samsung, IE: A custom recovery, ROM or Kernel etc
I have the same issue, same phone I ended up flashing a custom ROM because I luckily flashed twrp before it bricked on the us cellular screen.. How did you fix this I just want to get back to stock remove my root completely
So I got this phone a while back and I want to get rid of bloatware on it so I was going to use Titanium Backup, trouble is you need root(obviously).
I don't have much experience rooting as I've only ever rooted an Xperia E, and I only used a downloaded application on my laptop to do the work for me.
Help would be much appreciated, I will leave possibly useful info below.
Android Version : 5.1.1
Model Number : SM-G361F
Android Security Patch Level : 2016-02-01
Baseband Version : G361FXXU1APC2
Kernel Version : 3.14.27.-986474 [email protected] #1
SE for Android Status : Enforcing SEPF_SM-G361F_5.1.1_0045
Thank you and goodbye!
Hey,
Check for a pre-rooted firmware for your version available on XDA then flash it using Odin.
There are lot of tutorials to root this model over there.
brbninjaa said:
So I got this phone a while back and I want to get rid of bloatware on it so I was going to use Titanium Backup, trouble is you need root(obviously).
I don't have much experience rooting as I've only ever rooted an Xperia E, and I only used a downloaded application on my laptop to do the work for me.
Help would be much appreciated, I will leave possibly useful info below.
Android Version : 5.1.1
Model Number : SM-G361F
Android Security Patch Level : 2016-02-01
Baseband Version : G361FXXU1APC2
Kernel Version : 3.14.27.-986474 [email protected] #1
SE for Android Status : Enforcing SEPF_SM-G361F_5.1.1_0045
Thank you and goodbye!
Click to expand...
Click to collapse
Wait, you want to remove JUST bloatware?
Root can do much more than that and many guides use root and a custom recovery. But, as Atronid suggested, you can download and flash pre-rooted firmware for the device, but (ironically), to get rid of the bloat, you use the firmware, but the firmware usually comes with MORE bloat, so it's just plain stupid!
Also, I have had a major issue with this particular firmware in which the device overheats and soft-reboots constantly... I checked if it was anything else, but after switching back to stock, the issue stopped.
I am not condoning this method, it's just that I'd advise you to be careful with the overheating. It may not be an issue for you, I don't know. But here is the one I used for a bit:
https://forum.xda-developers.com/ga...re-rooted-firmwares-samsung-sm-g361f-t3207432
OR, there is another method which only works if you have a custom recovery and are ready to ditch Google.
You COULD install a custom recovery for your device and flash a SuperSU ZIP file. People may shout ''Doesn't work! He's lying! Blah! Blah! Blah!''
Well, I own the exact same phone as you and I know that method works.
But, for most things, you'll need a custom recovery anyway. It adds so much more to your device that allows you to unlock it's potential. HOWEVER, unless you are confident in Odin and how things work on a device, I'd slightly recommend that you avoid a custom recovery for now if you don't have much experience with Odin and flashing images.
BUT, if you can flash the pre-rooted firmware okay, you should be able to install a custom recovery fine.
You know what? If you want to know how, you can either PM me asking for instructions or search around the forums for a method.
MelonChickens said:
Wait, you want to remove JUST bloatware?
Root can do much more than that and many guides use root and a custom recovery. But, as Atronid suggested, you can download and flash pre-rooted firmware for the device, but (ironically), to get rid of the bloat, you use the firmware, but the firmware usually comes with MORE bloat, so it's just plain stupid!
Also, I have had a major issue with this particular firmware in which the device overheats and soft-reboots constantly... I checked if it was anything else, but after switching back to stock, the issue stopped.
I am not condoning this method, it's just that I'd advise you to be careful with the overheating. It may not be an issue for you, I don't know. But here is the one I used for a bit:
https://forum.xda-developers.com/ga...re-rooted-firmwares-samsung-sm-g361f-t3207432
OR, there is another method which only works if you have a custom recovery and are ready to ditch Google.
You COULD install a custom recovery for your device and flash a SuperSU ZIP file. People may shout ''Doesn't work! He's lying! Blah! Blah! Blah!''
Well, I own the exact same phone as you and I know that method works.
But, for most things, you'll need a custom recovery anyway. It adds so much more to your device that allows you to unlock it's potential. HOWEVER, unless you are confident in Odin and how things work on a device, I'd slightly recommend that you avoid a custom recovery for now if you don't have much experience with Odin and flashing images.
BUT, if you can flash the pre-rooted firmware okay, you should be able to install a custom recovery fine.
You know what? If you want to know how, you can either PM me asking for instructions or search around the forums for a method.
Click to expand...
Click to collapse
I have also tried (and disliked) one of those pre-rooted firmwares; it is a pity that all there is available for this device are a couple of outdated and bloated versions. I even tried to build my own firmware, but failed to create anything bootable (fortunately, I managed to not brick my device).
Then I tried the TWRP route: following a couple of guides I found here, I managed to install it, and use it to install the latest SuperSU .zip file. TWRP reported no errors, and everything seemed correct, but when the device boots there is no trace of any rooting: no SuperSU app, no "su" binary, no nothing at all...
Thus, if you could post here how you managed to make this work, I would be very grateful.
Well I own actually an outdated but fully working firmware and this got no bloats. I will re-upload it soon and give the link here.
This is not to get likes or thing like this but because I am sick of this **** to mess around with firmwares and integrate bloatwares (and spywares, everything is possible...)
Atronid said:
Well I own actually an outdated but fully working firmware and this got no bloats. I will re-upload it soon and give the link here.
This is not to get likes or thing like this but because I am sick of this **** to mess around with firmwares and integrate bloatwares (and spywares, everything is possible...)
Click to expand...
Click to collapse
Right on.
eduardo.perezesteban said:
I have also tried (and disliked) one of those pre-rooted firmwares; it is a pity that all there is available for this device are a couple of outdated and bloated versions. I even tried to build my own firmware, but failed to create anything bootable (fortunately, I managed to not brick my device).
Then I tried the TWRP route: following a couple of guides I found here, I managed to install it, and use it to install the latest SuperSU .zip file. TWRP reported no errors, and everything seemed correct, but when the device boots there is no trace of any rooting: no SuperSU app, no "su" binary, no nothing at all...
Thus, if you could post here how you managed to make this work, I would be very grateful.
Click to expand...
Click to collapse
Well, first I installed TWRP 3.0.2.0 also using the guide somewhere in the forums, then I downloaded SuperSU 2.46 .zip from the Chainfire website and flashed it using TWRP.
If the SuperSU .zip file didn't work for you, then try CF-Autoroot, whatever that is. I don't know because I have not tried it on my phone. I believe that it finds exploits and uses them somehow?
Anyway, did you flash the ZIP without extracting it? I don't see how it can't work, really. Call me stupid, but I don't know why that happened.
Anyways, good luck to all, for I am not active on these forums nowadays (as much)
MelonChickens said:
Well, first I installed TWRP 3.0.2.0 also using the guide somewhere in the forums, then I downloaded SuperSU 2.46 .zip from the Chainfire website and flashed it using TWRP.
If the SuperSU .zip file didn't work for you, then try CF-Autoroot, whatever that is. I don't know because I have not tried it on my phone. I believe that it finds exploits and uses them somehow?
Anyway, did you flash the ZIP without extracting it? I don't see how it can't work, really. Call me stupid, but I don't know why that happened.
Anyways, good luck to all, for I am not active on these forums nowadays (as much)
Click to expand...
Click to collapse
Same TWRP version, same SuperSU version, did not extract the ZIP file. It took me several attempts, but I finally managed to install TWRP and "install" SuperSU without errors. I do not doubt it worked for you, perhaps my base ROM is different, and has some type of protection that deletes any "su" file.
Will have a look to CF-Autoroot, thanks for the tip!
---------- Post added at 08:46 PM ---------- Previous post was at 08:39 PM ----------
CF-Autoroot website looked very promising, I could select a recent ROM and configure it, but the build process produced an error:
Code:
Current status: ERROR
Estimated wait: NOT APPLICABLE
Will keep investigating.
Atronid said:
Well I own actually an outdated but fully working firmware and this got no bloats. I will re-upload it soon and give the link here.
This is not to get likes or thing like this but because I am sick of this **** to mess around with firmwares and integrate bloatwares (and spywares, everything is possible...)
Click to expand...
Click to collapse
As promised I re-uploaded the original version (without bloats) of the firmware. Check this: https://forum.xda-developers.com/ga...odified-pre-rooted-firmware-sm-g361f-t3693589
MelonChickens said:
Wait, you want to remove JUST bloatware?
Root can do much more than that and many guides use root and a custom recovery. But, as Atronid suggested, you can download and flash pre-rooted firmware for the device, but (ironically), to get rid of the bloat, you use the firmware, but the firmware usually comes with MORE bloat, so it's just plain stupid!
Also, I have had a major issue with this particular firmware in which the device overheats and soft-reboots constantly... I checked if it was anything else, but after switching back to stock, the issue stopped.
I am not condoning this method, it's just that I'd advise you to be careful with the overheating. It may not be an issue for you, I don't know. But here is the one I used for a bit:
https://forum.xda-developers.com/ga...re-rooted-firmwares-samsung-sm-g361f-t3207432
OR, there is another method which only works if you have a custom recovery and are ready to ditch Google.
You COULD install a custom recovery for your device and flash a SuperSU ZIP file. People may shout ''Doesn't work! He's lying! Blah! Blah! Blah!''
Well, I own the exact same phone as you and I know that method works.
But, for most things, you'll need a custom recovery anyway. It adds so much more to your device that allows you to unlock it's potential. HOWEVER, unless you are confident in Odin and how things work on a device, I'd slightly recommend that you avoid a custom recovery for now if you don't have much experience with Odin and flashing images.
BUT, if you can flash the pre-rooted firmware okay, you should be able to install a custom recovery fine.
You know what? If you want to know how, you can either PM me asking for instructions or search around the forums for a method.
Click to expand...
Click to collapse
I flashed that same firmware before and I had the same issues. Had to download my original firmware from some site with terrible download speeds, took forever. Nice to know you found an alternative and I'm sure I would find more cool things to do with root.
brbninjaa said:
I flashed that same firmware before and I had the same issues. Had to download my original firmware from some site with terrible download speeds, took forever. Nice to know you found an alternative and I'm sure I would find more cool things to do with root.
Click to expand...
Click to collapse
So, just wondering, but I like to wrap things neatly;
Have you managed to root your device or are you still trying?
brbninjaa said:
So I got this phone a while back and I want to get rid of bloatware on it so I was going to use Titanium Backup, trouble is you need root(obviously).
I don't have much experience rooting as I've only ever rooted an Xperia E, and I only used a downloaded application on my laptop to do the work for me.
Help would be much appreciated, I will leave possibly useful info below.
Android Version : 5.1.1
Model Number : SM-G361F
Android Security Patch Level : 2016-02-01
Baseband Version : G361FXXU1APC2
Kernel Version : 3.14.27.-986474 [email protected] #1
SE for Android Status : Enforcing SEPF_SM-G361F_5.1.1_0045
Thank you and goodbye!
Click to expand...
Click to collapse
I just need the root because I have to retrieve attachments whatsapp that I deleted by mistake on the internal memory. as the software with which I should recover (dr fone) fails to do the root.