Database Users

[Q] Samsung Galaxy S4 AT&T root for I337UCUGOC3

I'm looking to root my s4, I just upgraded to lollipop and love it but there are some things I would like to do that require root. Hoping that someone can walk me through the process. Thanks in advance

Interested in this as well. Just need a point in the right direction. Thanks

I may be incorrect, but at the moment root for I337UCUGOC3 is only available via Flashfire.
http://forum.xda-developers.com/gal...-to-update-to-i337oc3-5-0-1-keeproot-t3075814

motobiz said:
I may be incorrect, but at the moment root for I337UCUGOC3 is only available via Flashfire.
http://forum.xda-developers.com/gal...-to-update-to-i337oc3-5-0-1-keeproot-t3075814
Click to expand...
Click to collapse
So there is no straight root from 5.0.1 at the moment?

Aranace said:
So there is no straight root from 5.0.1 at the moment?
Click to expand...
Click to collapse
No. You have to downgrade to 4.4.2 first, root, then flash up to 5.0
Sent from my SAMSUNG-SGH-I337

Bumping an older thread.
I've been searching around the forums for a guide to downgrade and a link to the Stock 4.4.2 ROM. AT&T Upgrade happened inadvertently. I either wasn't paying attention or it happened automatically.
Found plenty of post saying the same thing but no trustworthy guide on how to downgrade effectively from 5.0.1 on the i337 to 4.4.2. Normally I'd be up for experimenting but a newborn has me a little sleep deprived and looking for an idiot guide.
TIA

smtelegadis said:
Bumping an older thread.
I've been searching around the forums for a guide to downgrade and a link to the Stock 4.4.2 ROM. AT&T Upgrade happened inadvertently. I either wasn't paying attention or it happened automatically.
Found plenty of post saying the same thing but no trustworthy guide on how to downgrade effectively from 5.0.1 on the i337 to 4.4.2. Normally I'd be up for experimenting but a newborn has me a little sleep deprived and looking for an idiot guide.
TIA
Click to expand...
Click to collapse
Are you trying to get back to 4.4.2 then attempt to upgrade too 5.0.1 root?

Yes, but it sounds like from the tone of that question that I might be screwed.

You can flash back to nb1, root with towelroot, and go to lollipop with the keeproot method. Look in the general forum for [GUIDE]Odin to Stock, Updating, Rooting, and Installing Safestrap by guut13 and [How-To] Update to I337_OC3 - 5.0.1 and KeepRoot (4/7/2015) by muniz_ri.

schhy said:
No. You have to downgrade to 4.4.2 first, root, then flash up to 5.0
Click to expand...
Click to collapse
I also have a I337UCUGOC3 running 5.0.1.
Unfortunately yesterday my phone got messed up (I'll spare you all the details) and I had to do a factory reset. I am really unhappy about this because I wasn't able to backup properly with Titanium Backup since I'm not rooted. As a result, I now need to spend a bunch of hours getting my phone back to the way I like it. I am honestly not interested in flashing custom ROMs. I simply want to root so I can run Titanium Backup.
Based on your experience, how long might it typically take for a root guide to come out for this model? I'm trying to decide whether I should try to wait it out with my phone feeling "unfamiliar" to me - or if I should just go ahead and give up the idea of rooting / backing up.
Also, is there one site or forum (this thread???) where I would be able to find out how to root this model when it comes out? If so, where?
I would very much appreciate your advice!
Eliezer

EliezerB said:
I also have a I337UCUGOC3 running 5.0.1.
Unfortunately yesterday my phone got messed up (I'll spare you all the details) and I had to do a factory reset. I am really unhappy about this because I wasn't able to backup properly with Titanium Backup since I'm not rooted. As a result, I now need to spend a bunch of hours getting my phone back to the way I like it. I am honestly not interested in flashing custom ROMs. I simply want to root so I can run Titanium Backup.
Based on your experience, how long might it typically take for a root guide to come out for this model? I'm trying to decide whether I should try to wait it out with my phone feeling "unfamiliar" to me - or if I should just go ahead and give up the idea of rooting / backing up.
Also, is there one site or forum (this thread???) where I would be able to find out how to root this model when it comes out? If so, where?
I would very much appreciate your advice!
Eliezer
Click to expand...
Click to collapse
There is no way to root on OC3 at the moment. No clue on how long it'll take if a method even gets found. I recommend downgrading to NB1 using Odin then following the steps on herehttp://forum.xda-developers.com/showthread.php?t=3075814
. All downgrade file are on there too. Read through all steps and warning to prevent any problems
Sent from my SAMSUNG-SGH-I337

smtelegadis said:
Bumping an older thread.
I've been searching around the forums for a guide to downgrade and a link to the Stock 4.4.2 ROM. AT&T Upgrade happened inadvertently. I either wasn't paying attention or it happened automatically.
Found plenty of post saying the same thing but no trustworthy guide on how to downgrade effectively from 5.0.1 on the i337 to 4.4.2. Normally I'd be up for experimenting but a newborn has me a little sleep deprived and looking for an idiot guide.
TIA
Click to expand...
Click to collapse
FWIW my wife noted the user interface on her S4 suddenly completely changed. Looking at it when I got a chance I saw it was 5.0.1 (OC3). I actually don't know what it was previously. So AT&T is definitely pushing out the update.

Already on 5.0.1
I bought this ATT phone used, unlocked, and already on 5.0.1. We use it on the GoSmart Mobile network (owned/operated by T-Mobile). Today (a few weeks after the purchase), I get this message saying that there's an ATT software update available. How can ATT push an update to a phone not on their network? Will this update screw anything up? Will it re-network-lock it? I don't want to update this phone and, since it's my wife's phone, I don't want to risk a brick (I am in a similar situation with a baby and am quite sleep deprived). Previously, she had an HTC First (ATT phone use on GoSmart) and it notified us of an available update, but would not actually update (thank goodness). Do I actually have anything to worry about with this ATT update? Or is the notification just an annoyance? Thanks in advance.
>Joe

joeskippyxda said:
I bought this ATT phone used, unlocked, and already on 5.0.1. We use it on the GoSmart Mobile network (owned/operated by T-Mobile). Today (a few weeks after the purchase), I get this message saying that there's an ATT software update available. How can ATT push an update to a phone not on their network? Will this update screw anything up? Will it re-network-lock it? I don't want to update this phone and, since it's my wife's phone, I don't want to risk a brick (I am in a similar situation with a baby and am quite sleep deprived). Previously, she had an HTC First (ATT phone use on GoSmart) and it notified us of an available update, but would not actually update (thank goodness). Do I actually have anything to worry about with this ATT update? Or is the notification just an annoyance? Thanks in advance.
>Joe
Click to expand...
Click to collapse
The latest update, from 5.0.1, OC3 to 5.0.1 OC4 is a security update which is believed to be a response to the stagefreight bug. The update is relatively small, and should not "screw anything up." It will not affect network unlock.
As to why you're getting it on a non AT&T network, I'd guess that the update server determines the phone is an SGH-I337 and pushes the correct update for the phone.

How to root
Okay, so I have 5.0.1 with i337ucugoc3 and finally rooted it quite easily (after many failures).
I used WonderShare's MobileGo.
The process was actually very simple, but it was very confusing as to what the software actually wanted from me.
To make it easy, here's all you need:
1. Go to Settings->more->About Device
2. Tap on "Build number" seven (or more) times quicly
-- this will unlock the developer tools
3. Tap the back arrow
4. Tap "Developer options"
5. Tap on "USB debugging" to enable
6. Go to wondershare.com, download MobileGo, install
7. Run MobileGo
8. Connect your phone to your computer with a USB cable.
9. In MobileGo, click on the "One-Clock Root" button
You should be rooted quickly.
Not only that, it only installs SuperSU, and no malware.
10. Uninstall MobileGo if you don't want to keep it.

LoonCraz, thank you for your post. I have two questions about what you wrote:
looncraz said:
Okay, so I have 5.0.1 with i337ucugoc3 and finally rooted it quite easily (after many failures).
Click to expand...
Click to collapse
Would this work also for i337ucugoc4?
When you say "after many failures" - were there ever any negative consequences (something broken or bricking, etc.) from one of those failures - or just not getting root?
Thanks,
Eliezer

EliezerB said:
LoonCraz, thank you for your post. I have two questions about what you wrote:
Would this work also for i337ucugoc4?
When you say "after many failures" - were there ever any negative consequences (something broken or bricking, etc.) from one of those failures - or just not getting root?
Thanks,
Eliezer
Click to expand...
Click to collapse
I don't know, but supposedly it works very well with most versions.
None of my failed attempts left any bad effects, this program worked first shot :good:

Does the phone get wiped in the process - or does everything stay intact / in place?

The Wondershare MobileGo One-Click Root process successfully rooted my unlocked GS4 i337 (OC4) today, and confirmed by Root Checker. So easy!

looncraz said:
Okay, so I have 5.0.1 with i337ucugoc3 and finally rooted it quite easily (after many failures).
I used WonderShare's MobileGo.
The process was actually very simple, but it was very confusing as to what the software actually wanted from me.
To make it easy, here's all you need:
1. Go to Settings->more->About Device
2. Tap on "Build number" seven (or more) times quicly
-- this will unlock the developer tools
3. Tap the back arrow
4. Tap "Developer options"
5. Tap on "USB debugging" to enable
6. Go to wondershare.com, download MobileGo, install
7. Run MobileGo
8. Connect your phone to your computer with a USB cable.
9. In MobileGo, click on the "One-Clock Root" button
You should be rooted quickly.
Not only that, it only installs SuperSU, and no malware.
10. Uninstall MobileGo if you don't want to keep it.
Click to expand...
Click to collapse
this worked just fine....
I did it in my S4 i377 with 5.0.1 OC3
just download the trial and root it...
thanks!!!

Any custom ROMs available yet for the H915 Canadian Version (Freedom Mobile)?

LTE band 66 service and OTA updating is disabled through the DirtySanta root exploit on the stock build when rooted. I was hoping that there would be a ROM or two for the Canadian version of this device. Need something relatively stable, with nightly updates, and with support for AWS 3/Band 66 connectivity
Any leads are are appreciated. Thanks!

Considering the 915 isn't even a supported device no. If someone has gotten the 915 please let me know.

Until FREEDOM Mobile allows the LG V20 LOCKED bootloader to be UNlocked, there will be no FREEDOM to have a custom ROM anytime soon
That is what I got the T-mobile version with the unlockable bootloader which works great on NON-freedom.
lumberguy1028 said:
LTE band 66 service and OTA updating is disabled through the DirtySanta root exploit on the stock build when rooted. I was hoping that there would be a ROM or two for the Canadian version of this device. Need something relatively stable, with nightly updates, and with support for AWS 3/Band 66 connectivity
Any leads are are appreciated. Thanks!
Click to expand...
Click to collapse

Well i have a theory about getting root and signal on the 915 but it involves losing recovery afterwards. If anyone wants to discuss it let me know

markbencze said:
Well i have a theory about getting root and signal on the 915 but it involves losing recovery afterwards. If anyone wants to discuss it let me know
Click to expand...
Click to collapse
Actually very interested. I have the LGUP tool on Windows with Uppercut drivers installed, so I can unbrick my device even without recovery. Living without a rooted device is causing me extreme stress and trauma.

lumberguy1028 said:
Actually very interested. I have the LGUP tool on Windows with Uppercut drivers installed, so I can unbrick my device even without recovery. Living without a rooted device is causing me extreme stress and trauma.
Click to expand...
Click to collapse
Ok so here's my theory.
Basically we can root and have twrp but the problem is that signal ceases to exist afterwards which we assume is caused by the bootloader. Someone posted that they fixed their signal issues using the hidden menu features. But they didn't elaborate if they were rooted at the time and that was the direct reason for losing it in the first place. Nor have they replied. So that part is unknown. It may or may not be an option. The other question I had was is it just wind users who lose signals or does it affect wind devices that are unlocked but being used on other networks like bell, etc.
Anyway those are the unknown things that I'd like some clarification on. But in the meantime here's a theory I have that may or may not work if the above signal fix doesn't work.
So if the above fixing signal doesn't work via that hidden menu then we should be able to confirm the bootloader is the issue. What that means is that we need to have stock bootloader in order for everything to work.
But you cannot have stock bootloader with twrp unless you've "bumped" your recovery which we cannot do.
So my theory was to follow the whole root method and once your phone is booted up with root and twrp you would extract the stock recovery and stock bootloader from the restore file. Then you would flash them via flashfire which I'm told can be done. I'm told that flashing the bootloader does wipe your device which would eliminate root since it's the systemless method. So in theory you'd be back to pure stock again. That's not what we want to have. So we would have to use an alternative root like phh's root method flashed instead of supersu from twrp during the initial root process here. My theory is that you would be restored to stock again but you would have root at least.
So you would at least be able to tinker just not flash stuff. But I believe you can flash a few things from flashfire and still have root for general tinkering or ad block etc.
Of course there is also the possibility that with the locked bootloader (stock) that your phone may not even boot due to new security features in 7.0
But like I said this is just a theory that may or may not work. I haven't had time to try it because I'm constantly busy working and testing themes but if I do ever get time I would consider trying it if we can confirm that we are able to 100% restore to stock. At least with that confirmation we know that if it doesn't work we can get back to how things were.
Hopefully that makes sense.

markbencze said:
Ok so here's my theory.
Basically we can root and have twrp but the problem is that signal ceases to exist afterwards which we assume is caused by the bootloader. Someone posted that they fixed their signal issues using the hidden menu features. But they didn't elaborate if they were rooted at the time and that was the direct reason for losing it in the first place. Nor have they replied. So that part is unknown. It may or may not be an option. The other question I had was is it just wind users who lose signals or does it affect wind devices that are unlocked but being used on other networks like bell, etc.
Anyway those are the unknown things that I'd like some clarification on. But in the meantime here's a theory I have that may or may not work if the above signal fix doesn't work.
So if the above fixing signal doesn't work via that hidden menu then we should be able to confirm the bootloader is the issue. What that means is that we need to have stock bootloader in order for everything to work.
But you cannot have stock bootloader with twrp unless you've "bumped" your recovery which we cannot do.
So my theory was to follow the whole root method and once your phone is booted up with root and twrp you would extract the stock recovery and stock bootloader from the restore file. Then you would flash them via flashfire which I'm told can be done. I'm told that flashing the bootloader does wipe your device which would eliminate root since it's the systemless method. So in theory you'd be back to pure stock again. That's not what we want to have. So we would have to use an alternative root like phh's root method flashed instead of supersu from twrp during the initial root process here. My theory is that you would be restored to stock again but you would have root at least.
So you would at least be able to tinker just not flash stuff. But I believe you can flash a few things from flashfire and still have root for general tinkering or ad block etc.
Of course there is also the possibility that with the locked bootloader (stock) that your phone may not even boot due to new security features in 7.0
But like I said this is just a theory that may or may not work. I haven't had time to try it because I'm constantly busy working and testing themes but if I do ever get time I would consider trying it if we can confirm that we are able to 100% restore to stock. At least with that confirmation we know that if it doesn't work we can get back to how things were.
Hopefully that makes sense.
Click to expand...
Click to collapse
Im not sure how much you followed with me but... In my attempts to find a return to stock method i reflashed my stock aboot(bootloader). This bricked me. There is no way to use the stock bootloader once its been replaced that i have found.

me2151 said:
Im not sure how much you followed with me but... In my attempts to find a return to stock method i reflashed my stock aboot(bootloader). This bricked me. There is no way to use the stock bootloader once its been replaced that i have found.
Click to expand...
Click to collapse
Thanks for clearing that up. So then my next question was did you attempt that signal fix method and were you using yours on wind or was it an unlocked wind used on another network?
here's the link to this signal fix https://forum.xda-developers.com/showpost.php?p=70328080&postcount=3
and here is a post about someone saying they used it to fix their signal but they wouldn't elaborate on anything else.
https://forum.xda-developers.com/showpost.php?p=70571563&postcount=12

markbencze said:
Thanks for clearing that up. So then my next question was did you attempt that signal fix method and were you using yours on wind or was it an unlocked wind used on another network?
here's the link to this signal fix https://forum.xda-developers.com/showpost.php?p=70328080&postcount=3
and here is a post about someone saying they used it to fix their signal but they wouldn't elaborate on anything else.
https://forum.xda-developers.com/showpost.php?p=70571563&postcount=12
Click to expand...
Click to collapse
Lol Im the dirtysanta dev. I have a LS997. Not a 915.

me2151 said:
Lol Im the dirtysanta dev. I have a LS997. Not a 915.
Click to expand...
Click to collapse
Well I knew you had worked on ds. I wasn't sure however if you had a 915 or not. So then at this point it seems that if that signal fix is in fact valid that it is the only method to get things operational and I would presume it's a stretch given the user who posted about it doesn't seem to have any credibility to go by.

markbencze said:
Well I knew you had worked on ds. I wasn't sure however if you had a 915 or not. So then at this point it seems that if that signal fix is in fact valid that it is the only method to get things operational and I would presume it's a stretch given the user who posted about it doesn't seem to have any credibility to go by.
Click to expand...
Click to collapse
Thanks for this. Yeah DirtySanta may have been developed for LS997, but it seems to work on H915 minus the modem issue.

lumberguy1028 said:
Thanks for this. Yeah DirtySanta may have been developed for LS997, but it seems to work on H915 minus the modem issue.
Click to expand...
Click to collapse
Correct but it's useless to use since the phone doesn't function properly afterwards. If there was a confirmed way to have data and signal working then that would be great but there is nothing confirmed to work yet.

I've just moved to a V20 from a Note 4. All my Note4 ROMS were T-Mobile versions. I believe Rogers/Fido phones are basically the same as T-Mobile, which uses freq. channel 66 as well.
Has anyone tried a T-Mobile (918) ROM on the 915 yet? Might just work...

no root yet for freedom????/

whats the method
whats the method to root the lg h915

diehard2013 said:
no root yet for freedom????/
Click to expand...
Click to collapse
The 'Freedom' name becomes a bit ironic for the LG V20 H915 variant it seems. Not a lot of freedom when one can't unlock and root it. Just got one the other day as somehow my Note 4 stopped functioning as a phone, after a couple of months of fun running through loads of Lineage and other nightlies. Loved that phone, but I'll come to love the V20 I'm sure. Already like it a lot. But root seems essential. I haven't had an unrooted phone for more than a few hours in years. Adaway and just general user control of the file system seems essential. Getting rid of bloatware and such. I mean... I disabled a lot of that nonsense, but it's still there, existing in MY phone, which makes me mad. I want to dump a few custom notification sounds into root directories but can't. It's frustrating. So yeah, commenting to subscribe, and hoping a developer with a V20 in Canada decides to get excited enough to remedy the situation, whenever that becomes possible. Otherwise it seems I'll just have to get used to the odd ad and the other limitations.

GerardSamija said:
The 'Freedom' name becomes a bit ironic for the LG V20 H915 variant it seems. Not a lot of freedom when one can't unlock and root it. Just got one the other day as somehow my Note 4 stopped functioning as a phone, after a couple of months of fun running through loads of Lineage and other nightlies. Loved that phone, but I'll come to love the V20 I'm sure. Already like it a lot. But root seems essential. I haven't had an unrooted phone for more than a few hours in years. Adaway and just general user control of the file system seems essential. Getting rid of bloatware and such. I mean... I disabled a lot of that nonsense, but it's still there, existing in MY phone, which makes me mad. I want to dump a few custom notification sounds into root directories but can't. It's frustrating. So yeah, commenting to subscribe, and hoping a developer with a V20 in Canada decides to get excited enough to remedy the situation, whenever that becomes possible. Otherwise it seems I'll just have to get used to the odd ad and the other limitations.
Click to expand...
Click to collapse
Why Wouldent you just use the secret # in the hidden menu to change bands to get signial. Also you could try searching for exsisting bands that are near by, this dont require the hidden menu.
Sent from my [device_name] using XDA-Developers Legacy app

Not understanding what you are suggesting. I tried lots of hidden menu options to get the SIM recognized in the Note 4, but it appears the slot died on that phone. It just won't be a phone any more, no matter which ROM i flash.
If you mean the LG V20 I'm even more puzzled. How would changing hands help with rooting the phone?

GerardSamija said:
Not understanding what you are suggesting. I tried lots of hidden menu options to get the SIM recognized in the Note 4, but it appears the slot died on that phone. It just won't be a phone any more, no matter which ROM i flash.
If you mean the LG V20 I'm even more puzzled. How would changing hands help with rooting the phone?
Click to expand...
Click to collapse
Oops my bad i was sleeping while i read that. You can fix your sim card reader just use a soder tool. Also there maybe a root for this phone but i don't think it is safe enough yet.
Sent from my [device_name] using XDA-Developers Legacy app

XT1575 Need advice - Relock bootloader, failure

Ok, I unlocked bootloader and rooted. No issues at all.
Now, I was curious on relocking the bootloader & load stock rom.
The method that I used to flashed the firmware was the Autoflash, something like that.
Now what I did was extracted all the files within that folder. And click the autoflash, mijiggy. Lol
But I believe the most current firmware was MPH24.49-18
BUT I had MPHS24.49-16 - from what I can recall.
Pretty sure that was the latest on the site.
After flashing the phone, it successfully with any issues. The root is no longer present.
But no matter how many times that I add "fastboot oem lock" which does say okay - finished.
I still get that bootloader is unlocked, after it told me it was finished, no errors....
The other issue is upgrading the software OTA, failed!
As far as the radio part, I hope it still works. I don't have an extra Sprint sim card. But I'm pretty sure it will be ok.
Appreciate your help and time to read my crazy thread..lol
Sent from my Portable

PassatSport15 said:
Ok, I unlocked bootloader and rooted. No issues at all.
Now, I was curious on relocking the bootloader & load stock rom.
The method that I used to flashed the firmware was the Autoflash, something like that.
Now what I did was extracted all the files within that folder. And click the autoflash, mijiggy. Lol
But I believe the most current firmware was MPH24.49-18
BUT I had MPHS24.49-16 - from what I can recall.
Pretty sure that was the latest on the site.
After flashing the phone, it successfully with any issues. The root is no longer present.
But no matter how many times that I add "fastboot oem lock" which does say okay - finished.
I still get that bootloader is unlocked, after it told me it was finished, no errors....
The other issue is upgrading the software OTA, failed!
As far as the radio part, I hope it still works. I don't have an extra Sprint sim card. But I'm pretty sure it will be ok.
Appreciate your help and time to read my crazy thread..lol
Click to expand...
Click to collapse
A few problems here... First off, you likely had MPHS24.49-18-16 not just 16 (I don't think there is such a version) and the one your using MPHS24.49-18 is really old, it's the original MM firmware from Moto's website (the one on Moto's site is very old and dated incorrectly). We don't have the 18-16 image yet, so you cannot relock or even effectively fix this.
Also, you used a tool to flash, so when pieces failed to flash, you didn't even know it... And now you are in a mixed state with a ROM that is partially -18 and part 18-16, which is why an OTA won't take.
When you relock a Moto device, you don't just enter "fastboot oem lock" like a Nexus device, there is a process where you start with "fastboot oem lock begin" then flash a complete, signed factory image, wipe, and end with "fastboot oem lock" in one process.
Many parts to this process went wrong... Right now you are just kind of stuck.
BTW, relocking the bootloader has no effective gains except security... You will still be able to see in a glance it was unlocked from the bootloader screen or a fastboot command and the unlocked bootloader warning screen will still be there (you have to flash a custom logo to make it go away).

Did you make a backup of your stock ROM with TWRP prior to rooting? Restoring the backup with TWRP along with stock recovery is usually going to be the simplest and easiest way to go back to full stock.
As acejavelin stated, there really is no benefit to relocking the bootloader except from a security standpoint. As long as the stock ROM and recovery are restored to preroot condition with no system mods, you can take OTAs regardless of bootloader status.

acejavelin said:
First off, you likely had MPHS24.49-18-16 not just 16 (I don't think there is such a version) and the one your using MPHS24.49-18 is really old
Click to expand...
Click to collapse
My apologies for giving the incorrect info.
When I had purchased the phone about 3 weeks ago.
I upgraded the latest software update via Sprint OTA.
acejavelin said:
And now you are in a mixed state with a ROM that is partially -18 and part 18-16, which is why an OTA won't take.
Click to expand...
Click to collapse
What would be the best route for me to learn.?
The phone is not going anywhere. It is a backup phone, current have a Note 5. So I might as well take advantage of the opportunity.
Being that I'm mixed with 16 - 18 firmware, should I get the latest MM? Or am I just Fubarred..lol
Now what is the latest MM that I can download? Only because I would like to do an OTA when Nougat comes out.
I guess my goal is to start fresh again which seems impossible for now..
Any advice would be greatly appreciated! Thank you again!
Sent from my Portable

PassatSport15 said:
My apologies for giving the incorrect info.
When I had purchased the phone about 3 weeks ago.
I upgraded the latest software update via Sprint OTA.
What would be the best route for me to learn.?
The phone is not going anywhere. It is a backup phone, current have a Note 5. So I might as well take advantage of the opportunity.
Being that I'm mixed with 16 - 18 firmware, should I get the latest MM? Or am I just Fubarred..lol
Now what is the latest MM that I can download? Only because I would like to do an OTA when Nougat comes out.
I guess my goal is to start fresh again which seems impossible for now..
Any advice would be greatly appreciated! Thank you again!
Click to expand...
Click to collapse
I think 18-12 is the latest we have so far, but trying to flash it would not help... Your best bet at this point is either custom ROM or wait until we can get the image for 18-16. The problem here is Moto's don't support downgrading, it can be done but it often leaves you in a mixed state.
You could try flashing the latest version we have available manually (don't use a tool) and it might be close enough to able to OTA from there. You have some though, rumor has it initial surveys for an upgrade on the Pure just went out to MFN users this week, assuming it is the Nougat upgrade trial then once it starts you have 4-6 weeks barring any problems they encounter before public release. Assuming of course that history repeats itself and Lenovo follows the same path as Moto has previously.
So basically I'm saying have patience... We don't know when (or really if) we will get the current firmware image, sometimes it's quick and sometimes it takes months.

Update on my xt1575, that I could not take an OTA, it gave me an error - unsuccessful.
My original software was MPHS24.49-18-16, December update, latest software.
Well, I went ahead unlocked the bootloader, installed TWRP, then rooted....
Days later I had decided to unroot, so I would be able to take the OTA.
While I unrooted my device, it was successful, but could not take the updates at all.
Now I reflashed again, in this order below.
Autoflash Script with MPHS24.49-18-8.
Reboot the phone, checked if it was unrooted (No root)
Now I went to software update, and the phone did it's upgrade, like last time. Did the update, device rebooted and it was SUCCESSFUL!
I am finally back to the original software MPHS24.49-18-16
Which was December 2016 update.
Sent from my Portable

SM-G900V on 442 - want to upgrade without losing root

Hi. Couple years back, I used Towelroot to mindlessly root my SM-G900V on version 4.4.2 (no CWM, stock bootloader, locked, thanks Verizon!). Google Now crashes the minute I open it and I figure it's time to update from 4.4.2 to 5 or whatever is stable these days. I'm paranoid to do this without running it by you gurus here, because I don't want to lose root, brick my phone, or turn it into a flaming fireball of doom. Can someone point me to a thread I overlooked or just type a few easy-to-follow steps with link to ROM so I can upgrade my Galaxy S5?
Is a downgrade back to 4.4.2 possible if I don't like the upgrade?
Thanks in advance!

androidman807 said:
Can someone point me to a thread I overlooked
Click to expand...
Click to collapse
https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529

Thanks. I've spent a couple of hours and am on post 171 of the thread. I'm a CID 11 that needs to follow those steps on post 3. Regardless, this seems to be designed to take me from Kitkat to Marshmallow, skipping me right past the land of Lollipop. I haven't tried it yet, but 2 questions:
1) once in Marshmallow, can I get back to Lollipop or Kitkat?
2) the intro to the steps say that CID=11 needs SafeStrap or Flashfire, but the actual steps never mention Flashfire (only safestrap). Is it truly either/or, or is there an advantage to SS?
Thanks!
bbsc said:
https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Click to expand...
Click to collapse

1. Lollipop - yes, Kitkat - no.
2. You still can use SS on MM. It's a little tricky but still possible.
Flashfire requires root so it will not work on MM for CID 11.
This thread may also be useful for understanding the things: https://forum.xda-developers.com/ve...al/guide-painiacs-essential-guide-to-t3319848

I'll check out that thread (thank you for that), but I'm confused by something you wrote: "Flashfire requires root so it will not work on MM for CID 11." My Kitkat currently has root. Are you suggesting that when I throw Marshmallow on it I'll lose it?
And if you all will allow me to hijack my own thread, is Marshmallow really worth the upgrade from Lollipop? Heck, is Lollipop that much better than Kitkat? I've got a (mostly) working rooted system now, and it sounds like I can go up to 6 and back down to 5, but never again back to 4, hopefully keeping root the whole journey.
Thanks for reading and helping a new guy out. I figure others will find this information helpful down the road, as 4.4.2 was easy to root.... but where (if anywhere) from here?
bbsc said:
1. Lollipop - yes, Kitkat - no.
2. You still can use SS on MM. It's a little tricky but still possible.
Flashfire requires root so it will not work on MM for CID 11.
This thread may also be useful for understanding the things: https://forum.xda-developers.com/ve...al/guide-painiacs-essential-guide-to-t3319848
Click to expand...
Click to collapse

androidman807 said:
My Kitkat currently has root. Are you suggesting that when I throw Marshmallow on it I'll lose it?
Click to expand...
Click to collapse
Yes.
You say your phone has CID11. For SM-G900V it means it has a locked bootloader that cannot be unlocked (currently, but most likely - never).
Locked bootloader is called so because it's locked to boot only certain digitally signed kernel (aka boot.img)
Root on MM requires a modified kernel which cannot be booted by a locked bootloader.
That's why you cannot have root on MM and will lose it when upgrading.
androidman807 said:
is Marshmallow really worth the upgrade from Lollipop?
Click to expand...
Click to collapse
Only you can answer for yourself.
What are you using root for?
I have 4 or 5 S5s (G900V) here running MM and only one (mine) is rooted. No claims so far They just work.
BTW, all of them are running Devbase-4.2 from Alexndr.
If you're on Verizon you may like one of stock debloated ROMs which can be found in this section.

Thanks for all your help.
Reading the first few posts here really helped a lot to get a background. Then I attempted the steps here you provided on post 3 for my 11.
I thought I could pick my build after reading painiac's post, and was shy about going all the way up to PB1, but all the ones I chose wouldn't TowelRoot. I really did have to follow the instructions as written and use the COMBINATION EMMC ROM provided there. It freaked me out at first that it ended me up in Kitkat, but the final step brought up Lollipop and completed the process well.
The one scary point is after I ran Titanium getting ready to put some apps back on and used the "restore previous ID" it gave a panic, took me back to recovery and froze... required removing the battery, where normally that just causes a reboot. I did read the part in Painiac's post where he says don't restore system app (I had to export and import my contacts using the phone app to SD card and not Titanium - that worked). I hope my "restore previous ID" didn't go against his advice.
Other than that, things seem to be working smoothly now. I'm on Lollipop PB1 and not sure I even need Marshmallow. Thanks for all your help.
bbsc said:
Yes.
You say your phone has CID11. For SM-G900V it means it has a locked bootloader that cannot be unlocked (currently, but most likely - never).
Locked bootloader is called so because it's locked to boot only certain digitally signed kernel (aka boot.img)
Root on MM requires a modified kernel which cannot be booted by a locked bootloader.
That's why you cannot have root on MM and will lose it when upgrading.
Only you can answer for yourself.
What are you using root for?
I have 4 or 5 S5s (G900V) here running MM and only one (mine) is rooted. No claims so far They just work.
BTW, all of them are running Devbase-4.2 from Alexndr.
If you're on Verizon you may like one of stock debloated ROMs which can be found in this section.
Click to expand...
Click to collapse

A couple of months back, I updated from Kitkat to Lollipop using the instructions below, and ever since, I've had two persistent problems, and I'm wondering if anyone else has:
1) Wi-fi cuts out every few days requiring a reboot fix. This seems to be related to DNS.
2) Receiving picture texts (MMS) show up as "Message size: 2KB Expires: (date)" with no way to download or view. I see no workaround other to tell friends to email me pictures instead of texting them.
I've tried a factory reset, but haven't gone back to Odin yet to try to put PB1 on again (or a different ROM?). The good news is SafeStrap recovery is on the phone now. What can I try next to resolve these two problems? I can live with them with the reboot and avoiding MMS, but they are not trivial.
Thanks for any guidance or advice. Please help.
androidman807 said:
Thanks for all your help.
Reading the first few posts here really helped a lot to get a background. Then I attempted the steps here you provided on post 3 for my 11.
I thought I could pick my build after reading painiac's post, and was shy about going all the way up to PB1, but all the ones I chose wouldn't TowelRoot. I really did have to follow the instructions as written and use the COMBINATION EMMC ROM provided there. It freaked me out at first that it ended me up in Kitkat, but the final step brought up Lollipop and completed the process well.
The one scary point is after I ran Titanium getting ready to put some apps back on and used the "restore previous ID" it gave a panic, took me back to recovery and froze... required removing the battery, where normally that just causes a reboot. I did read the part in Painiac's post where he says don't restore system app (I had to export and import my contacts using the phone app to SD card and not Titanium - that worked). I hope my "restore previous ID" didn't go against his advice.
Other than that, things seem to be working smoothly now. I'm on Lollipop PB1 and not sure I even need Marshmallow. Thanks for all your help.
Click to expand...
Click to collapse

Up to date guide on bypassing factory reset protection on Nougat?

I've tried several guides from August and earlier but none of them work because they are outdated. I remember reading somewhere that you can downgrade from Nougat to Marshmallow in order to use old vulnerabilities, but now I can't find a guide telling me how to do this in order to bypass FRP.
Could someone point me to a working method to bypass FRP, whether I have to downgrade (if it is still possible) or not?

Latiken said:
I've tried several guides from August and earlier but none of them work because they are outdated. I remember reading somewhere that you can downgrade from Nougat to Marshmallow in order to use old vulnerabilities, but now I can't find a guide telling me how to do this in order to bypass FRP.
Could someone point me to a working method to bypass FRP, whether I have to downgrade (if it is still possible) or not?
Click to expand...
Click to collapse
any luck??? I am in a similar position

andrewrvincent said:
any luck??? I am in a similar position
Click to expand...
Click to collapse
I actually was able to bypass FRP on this phone. I can't tell you exactly how I did it since it was a long time ago and I forgot the steps, but what I do remember doing is flashing several versions of old Marshmallow updates using a modified version of Odin. It took me several tries and honestly I'm not even sure why it worked.
Something that could potentially help you is intentionally soft bricking the phone. I think I accidentally flash the wrong file to the phone, which soft bricked it, but I was able to correctly flash the software after that soft brick.
I'm sorry I can't be of any more help, but I can confirm that it is (or was) possible to bypass FRP on the latest Nougat update the day I posted here.

Latiken said:
I actually was able to bypass FRP on this phone. I can't tell you exactly how I did it since it was a long time ago and I forgot the steps, but what I do remember doing is flashing several versions of old Marshmallow updates using a modified version of Odin. It took me several tries and honestly I'm not even sure why it worked.
Something that could potentially help you is intentionally soft bricking the phone. I think I accidentally flash the wrong file to the phone, which soft bricked it, but I was able to correctly flash the software after that soft brick.
I'm sorry I can't be of any more help, but I can confirm that it is (or was) possible to bypass FRP on the latest Nougat update the day I posted here.
Click to expand...
Click to collapse
Thank you for the prompt reply. I just found a video with a tutorial and a tool bit it's late in NH do I'm off to bed. I'll try next change I get.

results
andrewrvincent said:
Thank you for the prompt reply. I just found a video with a tutorial and a tool bit it's late in NH do I'm off to bed. I'll try next change I get.
Click to expand...
Click to collapse
any results? Im lost