Related
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.
5.1.1 [DOK2] Setup [Debloated & Systemless Root] [Viper4Android][Bettery Battery]
I have seen a few people having issues with the DOK2 update and were looking for a step by step process of how to upgrade to the new firmware and optimize it to get goo performance. this thread will guide you through that process as well as link to the appropriate threads to download and get the needed files/add ons.
*****This process will wipe your phones internal storage and give you a clean install of the new firmware.
Step 1: Download the DOK2 firmware to your PC
There are a few places you can get this from:
Sammobile: N910T Firmware
Or XDA thread: Stock TW Firmware/Bootloader/Modem N910TUVU2DOK2 UNMODIFIED Mirror
(You will need the entire firmware not just the modem and baseband)
Step 2: Download ODIN to you computer
From ODIN DOWNLOAD: ODIN 3.10.7
Step 3: Odin Flash new firmware.
The download from Sammobile or Mega should be a .zip file. you will need to unzip that file to find the .tar file which is what you will use for ODIN flashing the firmware.
If you need help using Odin to flash the firmware check out this post on Android Central: Help Thread
After you have completed the Odin Flash the phone should reboot and come to the setup screen with your new firmware.
Step 4: Odin Flash TWRP
Download TWRP to your computer: TWRP Downloads
Specifically you want this file: twrp-2.8.7.0-trltetmo.img.tar
Use Odin to flash TWRP recovery onto your device.
If you get lost you can check this tutorial: ODIN Help
Step 5: Reboot your device and setup
Once you have rebooted go ahead and set up your device. we will worry abou debloating and getting root after your device is setup.
Step 6: make a backup in TWRP
Once your device is setup make a TWRP backup of your setting
Step 7: Getting Root
*****Update: New SuperSu 2.64 beta. Works even better with Samsung phones. *******
You will need the latest SuperSU beta from the below thread.
SuperSU Beta Systemless Root
Newest version is 2.64
You will then boot into TWRP and flash that zip in recovery. This will give you "Systemless Root"
Systemless root allows you to use the stock kernel with SE LINUX enforcing, but still be able to use root apps. However this is not complete root. Some root apps that need to modify the system will not work. this is just a BETA root and is not final yet. check back to that thread for updates as they come out.
Once you have flashed the SuperSU zip reboot your device and verify your root apps are working.
Step 8: DeBloating TW.
There are 2 options for debloating TW.
Option #1: V3.90 Debloater V3.90 DeBloater
This option works on both rooted and unrooted devices. It really is a program that uases ADB to allow you to FREEZE system apps. This will not allow you to completely delete the application with Systemless Root.
The OP has a TON of detail and walks through this process of how to uses his program.
Option #2: [Script]Touchwiz De-Bloating Script and Gapps ~ 222 Apps
http://forum.xda-developers.com/not...pt-touchwiz-bloating-script-222-apps-t3258537
This Option removes 222 applications. It is a simple download and flash in recovery process.
****HOWEVER This will remove some functionality of the device READ the list of application before you flash to make sure there are not any that you use. The OP also has instructions on how to modify the script if you want some application to not be removed.
Step 9 Viper4Android on Systemless root.
Download the Viper4 Andriod/Beat installer
Viper4Android w/ Beat Audio
Flash the installer zip in TWRP and reboot your device
Download BusyBox Installer
BusyBox by Stephen (Stericson)
Install BusyBox
Reboot
install Viper$Android Drivers
Reboot
Download both the Viper4Android SU policy fixes
1.) ViPER4Android-supolicy.zip
2.) XM_V4A_Fix_by_androidexpert35.zip
Reboot into TWRP and flahs both of these. you can flash them at the same time just to them in the order above. [1 then 2]
Reboot the device and enjoy V4a.
******Also the Beat portion of the zip is a bit wonky sometimes. I have not yet been able to get it to opperate effectively, so you may want to disable it or freeze it with Titanium backup.
Disclaimer: NONE of these zips are mine. I am posting download links from my mega, because I pulled these files from 3 different threads and only one was from an OP. the main Viper4Android /beats install zip comes from here : [SUPER MOD][4.3+/6.0][ v6.2 ] XTREMEMusic™ THE SOUND THAT YOU'VE NEVER HEARD!
*************************************************************************************************************************************************************************
With this setup I have easily gotten more than a days worth of usage. I average about 5.5 hours of SOT and 24 hrs between charges. Normally I plug in around 20 hours with about 40% battery left.
*****These are all items developed by other XDA USERS. Please provide the thanks on their respective threads as well.
Thanks for taking the time for this write up. I don't have much experience with the new systemless root. I was wondering since the steps you mentioned above doesn't require any pre-rooted steps if there is any way of getting root without triggering Knox. I know in the past you can do this with Android 4.x, however since I'm currently on the latest boatloader there is no going back. I understand many don't care about Knox, but since my replacement and having Knox intact, I'd thought it might be worth my while since systemless root seems to be the future for new Android releases. Also I've been running stock for the last few months and the experience has been pretty good, though I miss some of the conveniences of having root.
James62370 said:
Thanks for taking the time for this write up. I don't have much experience with the new systemless root. I was wondering since the steps you mentioned above doesn't require any pre-rooted steps if there is anyway off getting root without triggering Knox. I know in the past you can do this with Android 4.x, however since I'm currently on the latest boatloader there is no going back. I understand many don't care about Knox, but since my replacement and having Knox intact, I'd thought it might be worth my while since systemless root seems to be the future for new Android releases. Also I've been running stock for the last few months and the experience has been pretty good, though I miss some of the conveniences of having root.
Click to expand...
Click to collapse
This method is for root only. It requires installing TWRP which is a custom recovery. That means you will have to unlock the bootloader to be able to use this method. Once you unlock the bootloader (by Odin flashing TWRP) you have already tripped Knox. Knox is no big deal from what I have heard though. I have not heard of anyone getting denied a new phone because it was tripped.
The two main reasons to use this method are:
1.) It keeps the system intact, which allows you to use apps that check for root. (eg. Android Pay, Some Bank Apps etc)
2.) It allows you to use the stock kernel from 5.1.1. Currently the only way to get root on 5.1.1 and up is to install a custom kernel. Which is fine, and there are two really great option available with Emotion and Beast Mode, but I find the stock kernel gets me the best battery life and is the most stable.
ALSO this will be the way root is done going forward. 6.0.1 has a bunch of system file locks that prevent much of the system tinkering from happening. Chainfire (dev who built SuperSU) has a nice right up about the system partition on XDA right now explaining why some of the system tweaks we were used to will not be possible in the future. so at the very least this is good practice for getting ready for the Marshmallow update.
ShrekOpher said:
Step 8: DeBloating TW.
There are 2 options for debloating TW.
Option #1: V3.90 Debloater [http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294]
This option works on both rooted and unrooted devices. It really is a program that uases ADB to allow you to FREEZE system apps. This will not allow you to completely delete the application with Systemless Root.
The OP has a TON of detail and walks through this process of how to uses his program.
Option #2: [Script]Touchwiz De-Bloating Script and Gapps ~ 222 Apps [http://forum.xda-developers.com/not...t-touchwiz-bloating-script-222-apps-t3258537]
This Option removes 222 applications. It is a simple download and flash in recoevery process.
****HOWEVER This will remove some functionality of the device READ the list of application before you flash to make sure there are not any that you use. The OP also has instructions on how to modify the script if you want some application to not be removed.
Click to expand...
Click to collapse
Witch option is the easier? :silly:
Avide said:
Witch option is the easier? :silly:
Click to expand...
Click to collapse
Option #2 is WAY easier as long as you don't want to modify the script. You just download it to you phone boot into recovery and flash it. Then reboot. Takes 5 min.
ShrekOpher said:
This method is for root only. It requires installing TWRP which is a custom recovery. That means you will have to unlock the bootloader to be able to use this method. Once you unlock the bootloader (by Odin flashing TWRP) you have already tripped Knox. Knox is no big deal from what I have heard though. I have not heard of anyone getting denied a new phone because it was tripped.
Click to expand...
Click to collapse
Appreciate your reply. I was under the impression that the boatloader is already unlocked which is why we can flash a recovery without jumping through too many hoops. I know that a custom recovery trips Knox, but if there's a way to install the latest supersu through a utility such as flashfire or mobile odin, Knox won't be tripped.
I'm not really worried about warranty, just curious to see if it's possible to retain the integrity. Unfortunately both those options I mention requires the device to already be rooted which defeats what I'm trying to accomplish.
Hopefully someone will be able to figure something out in the near future.
Is it possible to use xposed with this?
So Shrek you've made the total move over?
I am holding off, althoguh i dunno for how long , because i need darker theme colors. do you know of any options?
masri1987 said:
So Shrek you've made the total move over?
I am holding off, althoguh i dunno for how long , because i need darker theme colors. do you know of any options?
Click to expand...
Click to collapse
Unless there is a feature in 5.1.1 that you MUST have, I would wait. I don't find anything to be significantly better on 5.1.1 vs. 4.4.4, but the battery life is much worse.
chodaboy19 said:
Unless there is a feature in 5.1.1 that you MUST have, I would wait. I don't find anything to be significantly better on 5.1.1 vs. 4.4.4, but the battery life is much worse.
Click to expand...
Click to collapse
Well i'm on 5.0.1 right now pop rocks, so yeah i probably will wait since there isn't a particular feature... i'm using the DOK2 modem on COD6 rom right now.
Is there a list of apps you should disable via the debloater specific to the tmobile note4?
masri1987 said:
So Shrek you've made the total move over?
I am holding off, althoguh i dunno for how long , because i need darker theme colors. do you know of any options?
Click to expand...
Click to collapse
There is no dark theme option as of right now, really it's the only thing i miss.
Will Rickards said:
Is there a list of apps you should disable via the debloater specific to the tmobile note4?
Click to expand...
Click to collapse
The list of apps on the "Debloater Script" (Option #2) thread is a great reference.
I tried everything exactly as indicated by this great guide, but I am still getting very poor battery life. I give up, I don't know what else to do.
I have googled and tried all sorts of suggestions from others with the same problem to no avail. Google Play Services and 5.1.1 have made my phone a useless POS. I guess it's time for a new phone. LOL
chodaboy19 said:
I tried everything exactly as indicated by this great guide, but I am still getting very poor battery life. I give up, I don't know what else to do.
I have googled and tried all sorts of suggestions from others with the same problem to no avail. Google Play Services and 5.1.1 have made my phone a useless POS. I guess it's time for a new phone. LOL
Click to expand...
Click to collapse
Do you ever use power saving mode? If you are in the stock kernel it can help a bunch. The phone operates just fine on it, if you are going to play a game or something you just turn it back off, but while your phone is in your pocket or laying around idle it keeps those background running Google services in check.
I'm normally getting about 6 hrs of SOT and about 24 hrs between charges. Below is where I'm at so far today. With about 2.5 hrs of SOT.
ShrekOpher said:
Do you ever use power saving mode? If you are in the stock kernel it can help a bunch. The phone operates just fine on it, if you are going to play a game or something you just turn it back off, but while your phone is in your pocket or laying around idle it keeps those background running Google services in check.
I'm normally getting about 6 hrs of SOT and about 24 hrs between charges. Below is where I'm at so far today. With about 2.5 hrs of SOT.
Click to expand...
Click to collapse
I think I found the culprit after 2 days of googling and countless wasted hours. My specific problem was that Media process was running all the time which in turn was causing Google Play Services to run at all times.
The Media process includes 2 packages: Media Storage and Download Manager. Together they perform scanning and indexing of media files on the internal SD and external SD.
I came across this page:
http://geeknizer.com/fix-android-media-server-scanner-sdcard-cpu-battery-drain/
I did step #3 which states that having more than 1,000 files in a folder makes this process crap out. I reformatted my microSD card, then I copied back all the files to the microSD. Then finally I deleted most of the pictures so that no one folder had more than 400 images.
I rebooted my phone and it started to behave normally. The Media Process only ran for 5minutes and stopped. Google Play Services ran for 2min and stopped. I have been through 1 charge already and got 5hrs or so of screen time with heavy use, I was installing apps, configuring accounts, freezing apps with Titanium backup, etc.
Overall, it seems like I have a happy ending to my story, BUT I will post a followup if the phone craps out again.
EDIT:
How do you get it to show the time on battery?
Mine doesn't have that information:
Does anyone have any interest in me adding how to set up Viper4Android on Systemless root to this thread? Just curious if I should go through the trouble.
There is a new version of SuperSU 2.64:
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Changelog:
20.12.2015 - v2.64 - BETA
- (systemless) Detect more boot image partition names
- (systemless) Blank partitions before writing to them
- (systemless) Ask to restore boot and recovery images on full unroot
- (systemless) Implement "uninstall competing superuser apps"
- (systemless) Samsung: prevent "KERNEL IS NOT SEANDROID ENFORCING" warning
- (systemless) Cleanup system install properly if present, fixes a number of possible bootloops
- ZIP: 6.0+: Detect firmwares that can reload sepolicy from /data and use system-based root on these ("allow init kernel:security { load_policy }")
- supolicy: Additional SELinux patches for M (reduced logging only)
- Update translations
ShrekOpher said:
The list of apps on the "Debloater Script" (Option #2) thread is a great reference.
Click to expand...
Click to collapse
Link to script isn't working. ..have another?
Sent from my SM-N910T3 using Tapatalk
AlexanderBlaQ said:
Link to script isn't working. ..have another?
Sent from my SM-N910T3 using Tapatalk
Click to expand...
Click to collapse
Should be working now. Thanks for the heads up.
Hi all,
I have a AT&T Galaxy S4 i337. The WIFI doesn't work. It seems to be a very common problem as there are many fixes on the internet. I have tried them all and I don't know what to do now. It is running V. 4.3 and my baseband version is i337ucugoc4.
- Rooted. Installed Rom Manager, Terminal Emulator, SuperSU, and Reverse Tether so I could use the internet (because no wifi).
- Tried to install a new modem but could not find the exact modem file. I saw a list at http://forum.xda-developers.com/showthread.php?t=2496517 but didn't know which was good for my phone. I saw I337_UCUGOC3_Modem_RockRatt.zip but it ends in a 3 not a 4 as required for my modem.
- tried to update using the AT&T Software update. It stayed at "Checking for software updates...." and then said "Software update interrupted. No updates available. Check back in 24 hours". Don't know if that would have solved the WIFI problem anyhow.
- Tried again to install to 5.0 thru USB. Downloaded and installed it but when I rebooted, it was still 4.3
- Downloaded FXR wifi and ran it - no luck there.
- downloaded the modem file ATT_OC4_modules.zip and flashed it to the phone. It said SUCCESSFUL but there was no wifi afterwards.
- Adjusted the source code with terminal emulator as I saw in a youtube video. No success and I changed it back to the original.
- Downloaded wifi manager and tried turned off-then-on wifi.
- probably more things I have forgotten in the last three days.
I have tried everything I can find to try. It has been 3 days of trying - very frustrated. I would very much appreciate direction on this. To recap, I need to get wifi working and want to upgrade to lolipop.
Thanks so much,
Amber
amberblossom said:
Hi all,
I have a AT&T Galaxy S4 i337. The WIFI doesn't work. It seems to be a very common problem as there are many fixes on the internet. I have tried them all and I don't know what to do now. It is running V. 4.3 and my baseband version is i337ucugoc4.
- Rooted. Installed Rom Manager, Terminal Emulator, SuperSU, and Reverse Tether so I could use the internet (because no wifi).
- Tried to install a new modem but could not find the exact modem file. I saw a list at http://forum.xda-developers.com/showthread.php?t=2496517 but didn't know which was good for my phone. I saw I337_UCUGOC3_Modem_RockRatt.zip but it ends in a 3 not a 4 as required for my modem.
- tried to update using the AT&T Software update. It stayed at "Checking for software updates...." and then said "Software update interrupted. No updates available. Check back in 24 hours". Don't know if that would have solved the WIFI problem anyhow.
- Tried again to install to 5.0 thru USB. Downloaded and installed it but when I rebooted, it was still 4.3
- Downloaded FXR wifi and ran it - no luck there.
- downloaded the modem file ATT_OC4_modules.zip and flashed it to the phone. It said SUCCESSFUL but there was no wifi afterwards.
- Adjusted the source code with terminal emulator as I saw in a youtube video. No success and I changed it back to the original.
- Downloaded wifi manager and tried turned off-then-on wifi.
- probably more things I have forgotten in the last three days.
I have tried everything I can find to try. It has been 3 days of trying - very frustrated. I would very much appreciate direction on this. To recap, I need to get wifi working and want to upgrade to lollipop.
Thanks so much,
Amber
Click to expand...
Click to collapse
May I ask why is your bootloader is lollipop but your OS rom is still Jelly bean ( you said 4.3). It appears that you might have jelly bean kernel which will not work with lollipop modem and bootloader. Majority of the wifi problem is caused by the kernel and bootloader mismatched, assuming that your radio (modem) has no physical damage. Try to flash the OC4 kernel and see you still have the wifi problem.
If you want to upgrade to lollipop from Jelly bean, there are several guides on this forum explaining step by step.
I flashed the OC4 kernal - no change in wifi
sway8966 said:
May I ask why is your bootloader is lollipop but your OS rom is still Jelly bean ( you said 4.3). It appears that you might have jelly bean kernel which will not work with lollipop modem and bootloader. Majority of the wifi problem is caused by the kernel and bootloader mismatched, assuming that your radio (modem) has no physical damage. Try to flash the OC4 kernel and see you still have the wifi problem.
If you want to upgrade to lollipop from Jelly bean, there are several guides on this forum explaining step by step.
Click to expand...
Click to collapse
Thanks sway8966,
I flashed the OC4_update_from_OC3.zip file but there was no change - still no wifi. I wonder if I were to upgrade to lollipop would it automatically fix the problem because it would have the matching bootloader and OS rom? Do you think this might solve the problem?
Thanks again.
amberblossom said:
Thanks sway8966,
I flashed the OC4_update_from_OC3.zip file but there was no change - still no wifi. I wonder if I were to upgrade to lollipop would it automatically fix the problem because it would have the matching bootloader and OS rom? Do you think this might solve the problem?
Thanks again.
Click to expand...
Click to collapse
I do not know what included in the oc4 update from oc3.zip file. As I said before you could try flashing the OC4 kernel file and see whether your wifi is working or not.
Here is the link for the OC4 kernel. You need to flash it via odin.
If you do not have any particular reason to stick with Jelly bean you should upgrade to Lollipop or at least to Kit-kat.
Hi! I had an s4 variant with your problem the same, the wifi nope in none routers.
I gave this device to trash , because i discovered what "happened"
Some stock app, from samsung, masked as anything that i skipped to search (i have much precious time to loose, instead loose really, lost time BRITISH DEVICES IN EXT4 filesystem) what app exactly, is receiving data from samsung server to delete the /system/etc/wifi/bcmdhd.cal
I was obligated to reinstall this file 4 times, changed permission to r--r--r--T untill resolve. But was not sufficient, after this, my wifi, fixed again, but the phone at 8º reboot, after , received a remote conmand again to turn the phone ridiculously slower, i lost my head and crashed this device on the wall, and nevermore i will use this name. Sorry,
All this happened just exactly, after install cwm and root sucessfully, without touch anything on the firmware. Something from samsung inc, is programmed to "detect" these 2 events, and send a "tick" to begin the hell in fire on this devices GT S-Xx
Sent from my XT687 using xda premium
won't boot past the SAMSUNG screen
sway8966 said:
I do not know what included in the oc4 update from oc3.zip file. As I said before you could try flashing the OC4 kernel file and see whether your wifi is working or not.
Here is the link for the OC4 kernel. You need to flash it via odin.
If you do not have any particular reason to stick with Jelly bean you should upgrade to Lollipop or at least to Kit-kat.
Click to expand...
Click to collapse
I flashed the OC4 kernel and it won't boot past the SAMSUNG screen.
amberblossom said:
I flashed the OC4 kernel and it won't boot past the SAMSUNG screen.
Click to expand...
Click to collapse
Your phone is probably in soft-brick now. You need to flash the 4.3 firmware via odin or You need to update to full kit-kat.
If you want to go kit-kat flash this NB1 firmware via odin. It is NB1 but the kernel is NC1 so that you can use towel root to root the phone. Anyway flash that firmware and see the phone is normally booting and wifi is working.
IT WORKED!!!
sway8966 said:
Your phone is probably in soft-brick now. You need to flash the 4.3 firmware via odin or You need to update to full kit-kat.
If you want to go kit-kat flash this NB1 firmware via odin. It is NB1 but the kernel is NC1 so that you can use towel root to root the phone. Anyway flash that firmware and see the phone is normally booting and wifi is working.
Click to expand...
Click to collapse
Thank you so much. It worked. I got my phone back and the wifi is working. Pretty nice. Thanks again. Now to figure out towel root (is that the best for my phone?). You are awesome.
couple more questions
sway8966 said:
Your phone is probably in soft-brick now. You need to flash the 4.3 firmware via odin or You need to update to full kit-kat.
If you want to go kit-kat flash this NB1 firmware via odin. It is NB1 but the kernel is NC1 so that you can use towel root to root the phone. Anyway flash that firmware and see the phone is normally booting and wifi is working.
Click to expand...
Click to collapse
I rooted with towelroot (verified with root checker). I installed superuser but didn't see how to remove bloatware. There are no apps in the apps list. How do I do that? Also, now that it is rooted, is it possible to upgrade it to lollipop? Thanks again.
amberblossom said:
I rooted with towelroot (verified with root checker). I installed superuser but didn't see how to remove bloatware. There are no apps in the apps list. How do I do that? Also, now that it is rooted, is it possible to upgrade it to lollipop? Thanks again.
Click to expand...
Click to collapse
I am glad to hear that it fixes your problem. The NB1 firmware (cooked by muniz_ri) is a live saver. Keep that one. Down the line if your phone screwed up used that one to revive your phone.
Majority of bloatware are system app as such they will not show up in the app bar To remove those you need an admin rights (root) hence we need to root the phone.
To remove the bloatware there are many bloatware remove apps. However they are not written to the specific phone and OS version as such you need to be very careful when you are using them.
I use titanium backup pro to either freeze or remove the bloatware one by one. You can find the list of bloatware for each version on the net. Another way is to install the lean custom rom.
If you want to upgrade to Lollipop you can do it. If somethings screws up you can use that NB1 to come back to Kitkat.
The latest lollipop for the sgh-i337 is OK2 but OK2 gave me some problem that I could not live with it so I stay at OC4.
If you want to upgrade to OK2 or OC4 do let me know. I will point you the guide and necessary files.
CyanogenMod
sway8966 said:
I am glad to hear that it fixes your problem. The NB1 firmware (cooked by muniz_ri) is a live saver. Keep that one. Down the line if your phone screwed up used that one to revive your phone.
Majority of bloatware are system app as such they will not show up in the app bar To remove those you need an admin rights (root) hence we need to root the phone.
To remove the bloatware there are many bloatware remove apps. However they are not written to the specific phone and OS version as such you need to be very careful when you are using them.
I use titanium backup pro to either freeze or remove the bloatware one by one. You can find the list of bloatware for each version on the net. Another way is to install the lean custom rom.
If you want to upgrade to Lollipop you can do it. If somethings screws up you can use that NB1 to come back to Kitkat.
The latest lollipop for the sgh-i337 is OK2 but OK2 gave me some problem that I could not live with it so I stay at OC4.
If you want to upgrade to OK2 or OC4 do let me know. I will point you the guide and necessary files.
Click to expand...
Click to collapse
I guess I will pass on lollipop if there was a problem with it. I looked around for a rom and saw CyanogenMod. It looked pretty good but they discontinued the installer. Can I download it on my PC, move it to the ext card on the S4 and install it from there? Without any changes to my current configuration of the S4? Thanks again.
amberblossom said:
I guess I will pass on lollipop if there was a problem with it. I looked around for a rom and saw CyanogenMod. It looked pretty good but they discontinued the installer. Can I download it on my PC, move it to the ext card on the S4 and install it from there? Without any changes to my current configuration of the S4? Thanks again.
Click to expand...
Click to collapse
I did not say lollipop has a problem, what I meant was I had some problem with lollipop OK2 as such I stay with lollipop OC4.
I took it as you are talking about the CyanogenMoD for the locked bootloader .
You can install that one. You need to install the safestrap first to flash that rom, as mentioned on that link. However, the link also mentioned that you can not make a phone call with that rom as such they stop developing that rom.
sway8966 said:
I did not say lollipop has a problem, what I meant was I had some problem with lollipop OK2 as such I stay with lollipop OC4.
I took it as you are talking about the CyanogenMoD for the locked bootloader .
You can install that one. You need to install the safestrap first to flash that rom, as mentioned on that link. However, the link also mentioned that you can not make a phone call with that rom as such they stop developing that rom.
Click to expand...
Click to collapse
Oh, I didn't understand. I think I would like to try to get up to lollipop. Can you point me to the kernel for that? Also, I have been trying to install CyanogenMod but am running into roadblocks. I think I might have succeeded finally because I now have a yellow triangle and a notice about non-AT&T system software (with a tiny notice - secure fail: kernel). I also had a difficult time installing TWRP as the installer was asking for a file format that the installer didn't download. From what I gather, CyanogenMod looks like a good all around OS and was easy to install when the installer was in play. But if there is another that would suffice but is easier to install, I think that might be a better idea. Could you suggest one?
Sorry about all these questions. I don't know why this is so difficult for me. I feel like an idiot. Thanks again.
amberblossom said:
Oh, I didn't understand. I think I would like to try to get up to lollipop. Can you point me to the kernel for that? Also, I have been trying to install CyanogenMod but am running into roadblocks. I think I might have succeeded finally because I now have a yellow triangle and a notice about non-AT&T system software (with a tiny notice - secure fail: kernel). I also had a difficult time installing TWRP as the installer was asking for a file format that the installer didn't download. From what I gather, CyanogenMod looks like a good all around OS and was easy to install when the installer was in play. But if there is another that would suffice but is easier to install, I think that might be a better idea. Could you suggest one?
Sorry about all these questions. I don't know why this is so difficult for me. I feel like an idiot. Thanks again.
Click to expand...
Click to collapse
SGH-i377 has locked bootloader as such we can not install custom recovery like TWRP or CWM. The only installers we have are safestrap and flashfire. When I was in Kit-kat I used safestrap. It is very troublesome to work with safestrap in lollipop so when I upgrade to lollipop I use falshfire instead.
I have two devices that are on cyanogen mod. I like cyanogen mod but I prefer touch-wiz rom over AOSP though.
The only cyanogen mod you can install is the one that I mentioned in my previous message. You need to use safestrap to install it.
For SGH-I337 you can only install the touch-wiz rom which are written for either safestrap or flashfire. I do not see any AOSP rom written for safestrap or flashfire.
What I did was flash NB1 via odin. root with towl root and install the flashfire. Flash the OC4 rom via flashfire and flash the OC4 bootloader via odin. After my phone boot to lollipop OC4, Installed flashfire and flash the Albe95 S6 port rom. I like to use the S6 features and that custom rom is a stable one. Do you think the process is easy enough?
To upgrade to Lollipop,
I assumed that you are back on NB1 and rooted. If not do that process first. (you mentioned that you installed the cyanogenmode)
Here is the guide telling you step by step how to install lollipop from NB1.
The guide was originally written for OC4 but when OK2 came out it was updated with OK2. So if you want to go to OK2, use the files that mentioned on the guide. If you want to go to OC4 use the file I posted below instead.
I337_OC4_Stock_Rooted_ROM.zip
I337_OC4_Stock_Rooted_Deodexed_ROM
I337_OC4_Bootloader.tar.md5
The choice between using normal and deodexed_rom is your call.
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.
Here's my Cheat Sheet ! This is the same procedure I used a while back with N910VVRU2CPD1 . I just updated the thread to work with the newer package.
1. Odin SamMobile N910VVRU2BPA1
reboot and factory reset a few times if needed to remove custom icon
2. Odin hsbadr's N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar HERE
3. Unlock with the samsung_unlock_n4-fix PROCESS use SIM card for data. Wi-Fi will not work at this point.
4. Odin twrp-3.0.2-0-trltevzw.tar Uncheck Auto Reboot, Manually boot into TWRP
5. Odin hsbadr's N910VVRU2CPD1_StockRestore.tar HERE
6. TWRP BETA-SuperSU-v2.71-20160331103524, Factory Reset, boot system
7. Use FlashFire to Flash firmware package SamMobile N910VVRU2CQI2
( ! System and Cache only ! )
Your mileage may vary.
Before I install my personal apps I remove as much Verizon, Samsung and Google spyware as possible.
-------------------------------------------------------------------------------------------------
EDIT: I was able to skip the recommended rooting and unlocking of 5.1.1 and make the jump I described.
I did not do the unlock using Kingroot until step 3 and I did not permanent root with Super Su until step 6.
No matter how you get there the phone has to be on [Firmware] [MM] [6.0.1] [RetEd/DevEd] Safe Upgrade to Marshmallow [N910VVRU2CPD1] then you can use FlashFire.
Hyperlinks are in the text to most of what's needed.
Credit AstonsAndroid I found it HERE
I keep seeing people saying there is a way to just flash TWRP and Magisk and you're done. I'd like to avoid SuperSU and the other root methods if possible. How would that work with your updated guide? Thanks
My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839
RootMyNote4Please said:
My main concern is the spyware the guys on Reddit bring up. Not to use kingroot and the like. Was there any resolution to this thread you posted Dr cool? Want to unlock my bootloader and flash the MODest ROM but I want to be able to avoid spyware too. Thanks for your work.
https://forum.xda-developers.com/no...spyware-fix-fixed-lag-wi-fi-problems-t3433839
Click to expand...
Click to collapse
I'm not sure if it was spyware or what. but my phone performance better after cleaning out that folder.
Thanks doc. Is that a folder that gets overwritten when you flash a new room?
This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?
lodilovesmuffins said:
This says "Continue with sim card data because wifi wont work at this point."
What if we don't have any data right now? Will it still work?
Click to expand...
Click to collapse
Kingroot needs to connected to root. I never seen it work without a connection. N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar brakes wifi but you get it back with N910VVRU2CPD1_StockRestore.tar, I dont know why. It just works
RootMyNote4Please said:
Thanks doc. Is that a folder that gets overwritten when you flash a new room?
Click to expand...
Click to collapse
My best guess now is it's some kind of provisioning issue that is cleaned up. Some of the files deleted you may actually need some day.
does this require the developer version? btw how do i backup
I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.
RootMyNote4Please said:
I seem to lose root after I flash CPD1. Still have TWRP though and says developer mode. What could be causing this?
Edit - When I flash stock restore I mean. I get rooted on BPA/CPD and then when I go to the next step I'm losing root and Kingroot says it has no solutions. I must be doing something wrong.
Click to expand...
Click to collapse
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.
kevintm78 said:
As long as you have TWRP installed still you are in good shape. At that point, you could either flash (through TWRP) SuperSu or magisk (on certain kernels magisk install errors out in twrp). The main objective is to get the custom recovery (twrp) installed on the 6.0.1 bootloader and once that's done it's just a matter of flashing your preferred rooting method or flashing a rom that has root included.
You can use an app like this to check your bootloader to make sure it's the right one.
Click to expand...
Click to collapse
That's weird. I flashed SuperSU but it didn't show up in the apps and when I tried to use Flashfire it said I didn't have root.
Got there. SuperSU had an error message when I tried to install it the 1st time after flashing full system. So I rebooted and installed again. Now Flashfire crashes and won't open. Switched to Flashify and it seems to work ok.
Edit - Stuck here for now. Flashify can't seem to find the CQI2 file and I still haven't been able to get Flashfire to work. Tried an older version and still crashes when it checks to see if I have the pro version or not.
In case someone else has the same problem with Flashfire, it's because the program expired April 1st, 2018. Turn the date back on your phone and it will load.
Finally completed it!!!
Ok, so the things I learned from my trials and errors.
1) DON'T flash the kernal and SU after you root with the N4 fix. I did this the 1st 15 times and could never get Flashfire to work later on. So skip all of the stuff in that post after you flash TWRP. Then flash the next firmware step.
2) Uncheck auto time and date on your phone and roll it back to before 4/1/18 to get Flashfire to work.
I'm sure there are some more things and I'll add whatever else I think can help the next guy along. Good luck! And thanks for the guide doc!
Note: Did the phone icon on your lock screen disappear as well when you were done? The camera is there on the bottom right like normal, but the phone is gone on the bottom left and it displays the charging info there now.
Thanks for this - it was helpful to make clear that in my mind that despite what other guides say, there is no need to unlock a Lollipop bootloader with a Lollipop kernel + ROM first, and that we can boot a Lollipop kernel + ROM with a Marshmallow bootchain and unlock the Marshmallow bootloader from the get-go.
I tracked down the CQI2 full Odin and I made hybrid Odins that get you "rooted on N910VVRU2CQI2" in fewer steps, following hsbadr's file naming scheme:
N910VVRU2BPA1_N910VVRU2CQI2_FullFirmware.tar.md5: MM CQI2 bootchain/firmware/modem, LL BPA1 ROM/kernel/recovery
N910VVRU2CQI2_StockRestore.tar: MM CQI2 ROM/kernel (no recovery - TWRP isn't overwritten)
These should be fine as drop-in replacements for the files mentioned in steps 2 and 5 of your guide.
Using these obviously means that you are unlocking the CQI2 aboot instead of the CPD1 aboot in step 3 while temprooted, and - importantly - step 7 is unnecessary to get to a CQI2 ROM, which is good because Flashfire is now expired :3
I doubt there's much of a real benefit to being on the newer aboot, but hey, why not.
Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?
lodilovesmuffins said:
Hey, no one answered my question from a while ago. So I'll ask again, does this require the developer version of the Note 4?
Click to expand...
Click to collapse
No, this will work with both versions of the verizon note 4.
kevintm78 said:
No, this will work with both versions of the verizon note 4.
Click to expand...
Click to collapse
Ok, thank you very much. I'll try and root my phone with this tutorial now.
Please help!!!!
I followed this link because its supposed to be a way to downgrade from 6.1.0 to 5.1.1 so I can unlock boot loader. However, these instructions make no sense to me. Can someone PLEASE help me. I've been searching and searching for a way to root my note 4 (N910VVRS2CQA1) and can't seem to find a way. I've never done this before so I'm pretty clueless. When I read these instructions, I just don't understand what I'm supposed to be doing. A lot of this tech lingo means nothing to me unfortunately. I'm starting to thing I should just give up the idea of rooting this Note 4 that's getting slower and slower and just get a new one. I don't really want to though bc I love the fact that you can replace the battery. It'd be much easier to just root and upgrade.....well, easier if I actually knew how.