[HELP] Straight Talk OF4 baseb, build root? - Galaxy S 4 Q&A, Help & Troubleshooting

I was wondering if there was an accurate, safe root method for the OF4 baseband and build?
It's a Straight Talk Samsung Galaxy S4 SM-S975L straight from the local WalMart.
The strange thing is, the kernel version is dated Tuesday, June 16th.
It looks like this thing comes fresh without NB1 (which I'm not sure will work with this hardware configuration, so hesitant to Odin flash).
Bootloader says WRITE PROTECTION ON. It's obviously locked. But it's been made aware of a different firmware flash will trip knox. (Will Triangle Away fix?)
Towelroot v3 says "not supported" so: does not work with override code 1337 0 1 7380 4 0 (or something, I Googled it, eh...)
Towelroot v1 stops responding on "Make it ra1n" tap.
VRoot failure trick, then Towelroot at the bugged out rebooted OS with the error message makes Towelroot v1 reboot the phone, but alas, no root. This is one step further.
Kingroot does not work.
VRoot can get Towelroot to reboot the phone, but nothing happens.
Again, this seems to be a very recent baseband and build. Dated June 16th, 2015.
I can attempt an Odin flash if that is theoretically possible from Download mode but it will trip Knox and set the warranty bit.
Suggestions and safe STOCK ROM to flash?
If not an exploit, that's easier. Thanks. Looks like this new kernel's been patched.

LupineDream said:
I was wondering if there was an accurate, safe root method for the OF4 baseband and build?
It's a Straight Talk Samsung Galaxy S4 SM-S975L straight from the local WalMart.
The strange thing is, the kernel version is dated Tuesday, June 16th.
It looks like this thing comes fresh without NB1 (which I'm not sure will work with this hardware configuration, so hesitant to Odin flash).
Bootloader says WRITE PROTECTION ON. It's obviously locked. But it's been made aware of a different firmware flash will trip knox. (Will Triangle Away fix?)
Towelroot v3 says "not supported" so: does not work with override code 1337 0 1 7380 4 0 (or something, I Googled it, eh...)
Towelroot v1 stops responding on "Make it ra1n" tap.
VRoot failure trick, then Towelroot at the bugged out rebooted OS with the error message makes Towelroot v1 reboot the phone, but alas, no root. This is one step further.
Kingroot does not work.
VRoot can get Towelroot to reboot the phone, but nothing happens.
Again, this seems to be a very recent baseband and build. Dated June 16th, 2015.
I can attempt an Odin flash if that is theoretically possible from Download mode but it will trip Knox and set the warranty bit.
Suggestions and safe STOCK ROM to flash?
If not an exploit, that's easier. Thanks. Looks like this new kernel's been patched.
Click to expand...
Click to collapse
Maybe this thread can give you references.
http://forum.xda-developers.com/galaxy-s4/general/guide-sm-s975l-twrp-4-4-2-custom-roms-t3009757

Thank you! Looks like most of the T-Mobile ROMS work. But hesitant to install them. Good to know you can do this from the OF4 build! Flash to Odin Fenny ROM, flash Safestrap for T-Mobile variant, then flash any T-Mobile ROM that works. I need to make a backup of my modem, though after the Odin flash. Just in case.
I hope this helps others.
Too bad about the warranty bit, though.

Also would like to add you gotta flash the kernel over the ROMs. Koontsz kernel. Otherwise you get a brick

LupineDream said:
Thank you! Looks like most of the T-Mobile ROMS work. But hesitant to install them. Good to know you can do this from the OF4 build! Flash to Odin Fenny ROM, flash Safestrap for T-Mobile variant, then flash any T-Mobile ROM that works. I need to make a backup of my modem, though after the Odin flash. Just in case.
I hope this helps others.
Too bad about the warranty bit, though.
Click to expand...
Click to collapse
You don't need safestrap. That's not for your phone. It's only for the T-mobile phone. Also just flash the TWRP and then the rom you want. You don't need to first flash that Fenny rom.

Related

[Q] I have checked google. so I came here.

Hi there new to the android scene, I have been using a jailbroken iPhone since the 3G iPhone.
I now have a Samsung Galaxy S5 and I have had so many attempts on my own to get root installed but each time I fail. :crying:
I used Odin to install toms touchwiz and this is installed correctly, I have managed to install 3 different ROMS but each has failed when I try to install metamod or anything else that wishes for /system to be RW.
SuperSu gets installed and it says it is ok, but when I try to make a folder in /system (root file explorer and other file explorers) it just says RW is required.:silly:
So to confirm I have a British Smasung s5 on vodophone.
Model - SM-G900F
I also PHREAKED out knox, so my warranty is VIOD too. :good:
I tried towelroot today, but it says that my device is not supported, I have tried the metakeys, but they do not work, they either crash the app, or it just sits there doing nothing.
How long should towelroot take to install or do its job.
What to do poeple?
WOW, THE LAST TIME I BUMPED SOMETHING WAS OVER 2 YEARS AGO?
Would anyone like to help me out here?
I am about to try and start all over again with a new nightly build of cyangenmod.
DO I NEED TO USE ODIN AGAIN OR CAN I JUST USE THE NEW NIGHTLY BUILD USING TOUCHWIZ?
WarezRonin said:
Hi there new to the android scene, I have been using a jailbroken iPhone since the 3G iPhone.
I now have a Samsung Galaxy S5 and I have had so many attempts on my own to get root installed but each time I fail. :crying:
I used Odin to install toms touchwiz and this is installed correctly, I have managed to install 3 different ROMS but each has failed when I try to install metamod or anything else that wishes for /system to be RW.
SuperSu gets installed and it says it is ok, but when I try to make a folder in /system (root file explorer and other file explorers) it just says RW is required.:silly:
So to confirm I have a British Smasung s5 on vodophone.
Model - SM-G900F
I also PHREAKED out knox, so my warranty is VIOD too. :good:
I tried towelroot today, but it says that my device is not supported, I have tried the metakeys, but they do not work, they either crash the app, or it just sits there doing nothing.
How long should towelroot take to install or do its job.
What to do poeple?
Click to expand...
Click to collapse
Here's what you can do:
1. Back up all your data
2. Go to Sammobile and download the appropriate firmware
3. Flash it with Odin
4. Download and install CF-Root.
This will root your phone properly. You can also try Phillz Touch Recovery if you want.
Always remember: When you screw up anything best option is to restore stock firmware
Hope that helped...
First of all, using CF Root WILL void your warranty......It trips knox and there is no return from that.
Second, check your build date (in settings under about phone/device)
If the build date is after June 2014, towelroot won't work. You'll have to odin flash an older kernel, towelroot it then flash your pre - existing kernel back. Full instructions can be found here......
http://forum.xda-developers.com/showthread.php?t=2699648
This method will NOT trip knox so your warranty remains intact.
And you can't flash CM until you have root anyway.....For info, flashing CM or a custom kernel will trip knox too.....
Edit.....just re read your post......forget everything I said about knox......lol
Sent from my rooted kn0x0 SM-G900F S5

Need help flashing stock S5 G900R4

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

How to Root G900A OA2 plz plz

I've been searching for a straight forward up to date guide but have failed. So I'm hoping to find a way that works and spread the info around in detail.
INFO:
Model: SM-G900A
Baseband: G900AUCU2AOA2
Kernel: 3.4.0-3116194
Not sure if the security enhancements have an effect.
I've tried Towelroot bUT not supported even when at 4.4.2
One-click-root seems like a scam, does say it's rootable but with no post about success only failure not about to waste S40.
Also why doesn't towelroot work? I tried it the second I got my phone so I took the update to 4.4.4. Well not by choice. It started the install when i was sleeping... Not cool Do I have to use Odin to flash to NCE?
So please help, I want to get this rooted before it updates to 5.0 without my approval
You can't, needed to be rooted on KK, if you took the official update you're SOL
Sent from my Tw5ted SM-G900A using Tapatalk
This exact same thing happened to me despite the fact that I thought that I had frozen the updates. I was able to root OA2 and prevent updating to 5.0, though. Here's how I did it.
Basically, just follow this guide: http://forum.xda-developers.com/att...to-root-g900aucu2aoa1-4-4-4-2-3-2015-t3021120
Even though I was on OA2, flashing down to ND3 via Odin and then running Towelroot anyway successfully rooted my phone. I couldn't find the OA2 kernel at the time, so I just flashed up to the OA1 kernel instead (yes, alongside the OA2 basebands) and didn't see any problems with it. I am still using the OA1 kernel this way now.
I don't know if there is anything actually different between the OA1 and OA2 kernel, but I have been running with this configuration for about a month and a half with no real problems -- but your mileage may vary. (Your phone may burst into flames and start chanting versus from the Necronomicon. You have been warned.)
While I'm still on the OA1 kernel, I happened to do a quick search and found the OA2 kernel floating around here: https://www.androidfilehost.com/?fid=24052804347799283 -- but flashing this thing is not something that I have personally tried (although now I am tempted to).
So if you do flash this one, good luck -- but again, I can't be held responsible for any damage to your phone (or psyche, in the event of demonic possession).
I've tried those instructions but when I tried flashing in odin it froze at boot.img forcing me to power off my cell. Luckily it didn't affect anything. I was surprised about the size of the file only being around 10Mbs and that the link takes you to the S4 files section. I'll try it again tomorrow to see if it works this time.

WIFI not working - tried everything - very frustrated

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.

I think I goofed... bad. Sm-n900v 5.0 stock

Well the title says alot... let me explain..
I've got a note 5 and LG g5. This note 3 is an extra phone. So I figured I would root and rom it.
I started on 4.4.2 and it wouldn't boot...
Ran Odin 3.09 and loaded pl1...couldn't root.
Ran Odin 3.09 again with ob6. Root success.
I then followed instructions for unlock_n3 for the bootloader and also installed twrp.
Last night I went on a spree with roms trying to find a working rom with data... no success... I felt like I was doing something wrong so I went back to Odin and ran ob6 again which is where I'm at now.
In the process I dev'd my phone... and now I cannot get root and lost twrp in the process.
Did I eff up?
What's next from here? I don't care about Knox and like I said I've got 2 other phones both working and paid off. This is my "car phone". I use it for music and that's about it. That being said I would rather have working data instead of using my note 5 with Hotspot mode.
My device is now hlte... not hltevzw... I think I did something very wrong. Please halp.
If it helps I did take pictures along the way when running the unlock_n3 over adb. I've got the original emmc ID but I'm not sure if this step is reversable.
I also made a backup with twrp... but it seems my SD card was wiped at some point last night.
Please don't flame... I admit this was my stupidity and I'm sure I'm not the only one who makes mistakes. At this point I'll be happy with anything 5.0 and root. As I said above if Knox is a concern I don't really care. Phones paid off... and I've got a note 5 and when that dies I'll get a 7. Also have LG g5 as a backup.
What are my options now oh wise xda gods?
Edit: I ran arabictool again, and got a 5.0 not found error. Decided to try kingoroot, and it says succeeded, however upon running root checker, it says "Sorry! Root access is not properly installed on this device"
Edit2: After trying edit 1... im now im a bootloop, and I check vol+, home, and power and twrp is indeed gone.
When I get home I plan to Odin OB6 again, as it worked, and since i've already done it once I assume I cant do any further damage :\
Edit3: I've successfully flash back to OB6, and as expected, ive finally tripped knox. Damn near 5 years with a note 3, and JUST tripped it. Not bad if I do say so my self... although, theres still more work to be done :\
GGRRRR, I wont give up so easily! But I could use some advice
tbonedude said:
Well the title says alot... let me explain..
I've got a note 5 and LG g5. This note 3 is an extra phone. So I figured I would root and rom it.
I started on 4.4.2 and it wouldn't boot...
Ran Odin 3.09 and loaded pl1...couldn't root.
Ran Odin 3.09 again with ob6. Root success.
I then followed instructions for unlock_n3 for the bootloader and also installed twrp.
Last night I went on a spree with roms trying to find a working rom with data... no success... I felt like I was doing something wrong so I went back to Odin and ran ob6 again which is where I'm at now.
In the process I dev'd my phone... and now I cannot get root and lost twrp in the process.
Did I eff up?
What's next from here? I don't care about Knox and like I said I've got 2 other phones both working and paid off. This is my "car phone". I use it for music and that's about it. That being said I would rather have working data instead of using my note 5 with Hotspot mode.
My device is now hlte... not hltevzw... I think I did something very wrong. Please halp.
If it helps I did take pictures along the way when running the unlock_n3 over adb. I've got the original emmc ID but I'm not sure if this step is reversable.
I also made a backup with twrp... but it seems my SD card was wiped at some point last night.
Please don't flame... I admit this was my stupidity and I'm sure I'm not the only one who makes mistakes. At this point I'll be happy with anything 5.0 and root. As I said above if Knox is a concern I don't really care. Phones paid off... and I've got a note 5 and when that dies I'll get a 7. Also have LG g5 as a backup.
What are my options now oh wise xda gods?
Edit: I ran arabictool again, and got a 5.0 not found error. Decided to try kingoroot, and it says succeeded, however upon running root checker, it says "Sorry! Root access is not properly installed on this device"
Edit2: After trying edit 1... im now im a bootloop, and I check vol+, home, and power and twrp is indeed gone.
When I get home I plan to Odin OB6 again, as it worked, and since i've already done it once I assume I cant do any further damage :\
Edit3: I've successfully flash back to OB6, and as expected, ive finally tripped knox. Damn near 5 years with a note 3, and JUST tripped it. Not bad if I do say so my self... although, theres still more work to be done :\
GGRRRR, I wont give up so easily! But I could use some advice
Click to expand...
Click to collapse
You need to go thru your original steps again, root, unlock and then TWRP make sure it is the hltevzw version,
Sent from my SM-N900V using Tapatalk
donc113 said:
You need to go thru your original steps again, root, unlock and then TWRP make sure it is the hltevzw version,
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply, as of edit 3, I am back on OB6, and cannot seem to get root. Are my chances better with OF1?
Ive tried yemen tools (says 5.0 not found)
I've tried kingo root (says successful, never reboots, and shows "this phone root isnt properly setup" when checking with root checker from joey kilm (think thats his name)
Does it matter my emmc ID is ending with 43100?
https://cdn.discordapp.com/attachments/221482708063223809/378367914388094981/image.png <- image from unlock_n3 after success, emmc checker shows same value AFTER odin ob6 (this held, nothing else did)
Edit: After taking donc's recommendation of OF1, I am now able to run yemen tools. As a side note, I seem to have more bars of service with OF1... coincidence?
Edit2: I HAVE ROOT! on OF1 using yemen tools (downgraded from PL1 to OB6 finally to OB1 and it worked.) Now to re-unlock bootloader. Thanks guys for the support thus far, this is a journey and having qualified accomplices makes this SOOOO much easier.
So heres where im at now.. as a recap for personal use, and anyone else who may be on a similar path.
Start to finish, this is what I did, where im at now, and where I want to be by tonight
Got phone, 4.4.2 with bootloop, couldn't find 4.4.2 firmware online
Flashed 5.0 (PL1), no root available.
Flashed 5.0 (OB6) rooted, unlocked boot loader, twrp, played with roms, got frustrated, re-flashed OB6 and couldn't root again (seems flimsy)
Flashed 5.0 (OF1) rooted, unlocked boot loader, verified several times root is working. Installed SuperSu and busybox.
This is where im at now, about to install twrp since i've done this already with ob6, and was working fine (though, I would prefer to have philz, and multi rom slots)
This entire process i've been using Odin 3.09, Twrp 3.0.2-1. My note 3 has been changed to a dev ID ending in 3100 (see above posts) this seems to have held through entire process with multiple recoveries.
I am going to make a full backup (again...) and unlike last time... store this copy onto my PC instead of SDcard alone... this was my mistake, and I need to learn from it.
For the @dev's out there, is there anything I can provide to help this overall process and community in general? I'm fairly literate in adb/linux and have no issues running commands, uploading files, or anything similar.
Shout out to @donc113 above for stating the obvious (since i failed to search and find the proper methods) as well as giving me the kick in the pants I needed to push onwards and succeed. Thanks brotha. :good:
tbonedude said:
So heres where im at now.. as a recap for personal use, and anyone else who may be on a similar path.
Start to finish, this is what I did, where im at now, and where I want to be by tonight
Got phone, 4.4.2 with bootloop, couldn't find 4.4.2 firmware online
Flashed 5.0 (PL1), no root available.
Flashed 5.0 (OB6) rooted, unlocked boot loader, twrp, played with roms, got frustrated, re-flashed OB6 and couldn't root again (seems flimsy)
Flashed 5.0 (OF1) rooted, unlocked boot loader, verified several times root is working. Installed SuperSu and busybox.
This is where im at now, about to install twrp since i've done this already with ob6, and was working fine (though, I would prefer to have philz, and multi rom slots)
This entire process i've been using Odin 3.09, Twrp 3.0.2-1. My note 3 has been changed to a dev ID ending in 3100 (see above posts) this seems to have held through entire process with multiple recoveries.
I am going to make a full backup (again...) and unlike last time... store this copy onto my PC instead of SDcard alone... this was my mistake, and I need to learn from it.
For the @dev's out there, is there anything I can provide to help this overall process and community in general? I'm fairly literate in adb/linux and have no issues running commands, uploading files, or anything similar.
Shout out to @donc113 above for stating the obvious (since i failed to search and find the proper methods) as well as giving me the kick in the pants I needed to push onwards and succeed. Thanks brotha. :good:
Click to expand...
Click to collapse
You're welcome. Just an FYI, the ending of the CID doesn't matter, it's the first 2 numbers that count, and they MUST be 15
I used Flashify (available on Google Play) to load TWRP... worked great (but you must have root and busybox installed to use it to flash TWRP)
Sent from my SM-N900V using Tapatalk

Categories

Resources