Database Users

SGH-I337M Rooted user

All set, thanks anyways guys he got the files needed

shabbypenguin said:
Hey i have a request, i need a few files dumped off the canadian variant, if someone is so kind and willing http://shabbypenguin.com/getdownload.php?file=Tools/Unbrick-Creator.zip to flash that in recovery and upload the files that would be great .
Click to expand...
Click to collapse
Bump. The community is in great need of this for the I337M device. If possible, we are looking for this dumped from someone with the latest firmware installed but anything at all will be a plus. I'll offer $10.00 to the user the produces this via PayPal. It's simple, just flash the file from the OP's post and then upload the files using any file hosting site. Then buy yourself a meal with the free $10.00...

connexion2005 said:
Bump. The community is in great need of this for the I337M device. If possible, we are looking for this dumped from someone with the latest firmware installed but anything at all will be a plus. I'll offer $10.00 to the user the produces this via PayPal. It's simple, just flash the file from the OP's post and then upload the files using any file hosting site. Then buy yourself a meal with the free $10.00...
Click to expand...
Click to collapse
In progress. can someone shoot the link to steps? I have the zip, and a rooted s4 i377m (rogers) running stock 4.2.2 .....I need to flash it to kitkat gummy rom shortly, so if someone can let me know the steps, and what this will do the device I run it on, I'll go ahead and run it, then upload the files....
ah I see. Completed successfully. uploading....
---------- Post added at 03:14 PM ---------- Previous post was at 02:32 PM ----------
Had a look at the .sh file, and I believe the paths need to be updated for the Canadian variant. ie: /sdcard/Unbrick_Files/ should actually be: /storage/sdcard/Unbrick_Files
I flashed via latest CWM, and none of the data paths were created on the sd card, yet the process said it completed.

azuziel said:
In progress. can someone shoot the link to steps? I have the zip, and a rooted s4 i377m (rogers) running stock 4.2.2 .....I need to flash it to kitkat gummy rom shortly, so if someone can let me know the steps, and what this will do the device I run it on, I'll go ahead and run it, then upload the files....
ah I see. Completed successfully. uploading....
---------- Post added at 03:14 PM ---------- Previous post was at 02:32 PM ----------
Had a look at the .sh file, and I believe the paths need to be updated for the Canadian variant. ie: /sdcard/Unbrick_Files/ should actually be: /storage/sdcard/Unbrick_Files
I flashed via latest CWM, and none of the data paths were created on the sd card, yet the process said it completed.
Click to expand...
Click to collapse
it does it all while in recovery which is linked to /sdcard so that shouldnt matter. if youre savvy with adb or terminal emulator you can just run teh dd command found in teh script and that will generate the image

shabbypenguin said:
it does it all while in recovery which is linked to /sdcard so that shouldnt matter. if youre savvy with adb or terminal emulator you can just run teh dd command found in teh script and that will generate the image
Click to expand...
Click to collapse
yep, I've flashed it to a rooted i377m with latest CWM 4 times now. I boot in to recovery, install the zip, Script says it runs, I get no errors whatsoever. Yet when I browse both internal SD, and external SD, I'm not seeing *any* folders/files created. Let me see what I can figure out.
I flashed to gummy 1.1, but I'm downloading the official 4.2.2 and 4.3 official Samsung fw and kernels now. I don't mind backing up current rom, flashing back to official fw, and then running the tool again, but I want to see if I can figure out why it wasn't able to copy on a co-orkers unit that is still running a rooted stock. Let me try and run it via terminal when my co-worker arrives with his device. Sorry for the delay. I want to dump these files as it can only help myself and other i377m users.
@connexion2005 - Not concerned with the 10 bucks. Keep it for a couple of beers while un-bricking.

update
azuziel said:
yep, I've flashed it to a rooted i377m with latest CWM 4 times now. I boot in to recovery, install the zip, Script says it runs, I get no errors whatsoever. Yet when I browse both internal SD, and external SD, I'm not seeing *any* folders/files created. Let me see what I can figure out.
I flashed to gummy 1.1, but I'm downloading the official 4.2.2 and 4.3 official Samsung fw and kernels now. I don't mind backing up current rom, flashing back to official fw, and then running the tool again, but I want to see if I can figure out why it wasn't able to copy on a co-orkers unit that is still running a rooted stock. Let me try and run it via terminal when my co-worker arrives with his device. Sorry for the delay. I want to dump these files as it can only help myself and other i377m users.
@connexion2005 - Not concerned with the 10 bucks. Keep it for a couple of beers while un-bricking.
Click to expand...
Click to collapse
So I reverted to stock today, and then restored my official Samsung backup, then watched my device apply update for i377m 4.3 jellybean.
Issue now, is that I've lost root and haven't been able to verify thru my searches wether or not the auto-root file I used on 4.2.2, would work on 4.3. Anyone know? If not, anyone know if updated files exist? Once I get them, I can re-root and get these files uploaded. Sorry for the delay guys, busy week at work this week.
edit - I'm fairly confident that the cf-auto-root method will still work, however with knox being installed, voids the warranty as triangle away wont work on this now. Which is fine, I work in IT dept and if I need a new phone, I'll just have another sent over.

azuziel said:
So I reverted to stock today, and then restored my official Samsung backup, then watched my device apply update for i377m 4.3 jellybean.
Issue now, is that I've lost root and haven't been able to verify thru my searches wether or not the auto-root file I used on 4.2.2, would work on 4.3. Anyone know? If not, anyone know if updated files exist? Once I get them, I can re-root and get these files uploaded. Sorry for the delay guys, busy week at work this week.
edit - I'm fairly confident that the cf-auto-root method will still work, however with knox being installed, voids the warranty as triangle away wont work on this now. Which is fine, I work in IT dept and if I need a new phone, I'll just have another sent over.
Click to expand...
Click to collapse
you nee dto have root and a custom kernel to prevent samsungs root blocking stuff, not sure if cf-root does all that.

knox defeated
It doesn't no, but all KNOX does from my understanding, is record the flash attempt into it, and once this happens, no triangle away or flash counter reset method will work. However, just found this method on how to root Canadian/US s4 running QUALCOMM chipsets only (LTE and most US devices).
It does require cooking the root into the official firmware, and flashing via download mode/odin 3.09. I'll try that this weekend. I would post the link, but evidently i'm not allows yet. Just google "universal-root-de-la-vega-script" for the method.
Ciao for now,
Az

connexion2005 said:
Bump. The community is in great need of this for the I337M device. If possible, we are looking for this dumped from someone with the latest firmware installed but anything at all will be a plus. I'll offer $10.00 to the user the produces this via PayPal. It's simple, just flash the file from the OP's post and then upload the files using any file hosting site. Then buy yourself a meal with the free $10.00...
Click to expand...
Click to collapse
I'm on 4.3 now. Might root later on today. Are these files still required for 4.3 JB? I do have the 4.2.2 firmware I've uploaded to TPB, however I cannot revert to 4.2.2 from what I understand. More than happy to help if you require these from 4.3 i377m RWC.

azuziel said:
I'm on 4.3 now. Might root later on today. Are these files still required for 4.3 JB? I do have the 4.2.2 firmware I've uploaded to TPB, however I cannot revert to 4.2.2 from what I understand. More than happy to help if you require these from 4.3 i377m RWC.
Click to expand...
Click to collapse
that will work just fine

shabbypenguin said:
that will work just fine
Click to expand...
Click to collapse
Care to leave manual steps? I dont rub custom recovery, as I rooted without tripping knox.
Can i run script via adb or term emulator?
Sent from my SGH-I337M

adb shell or terminal will work fine
su
dd if=/dev/block/mmcblk0 of=/sdcard/Unbrick.img bs=4096 count=50000
i would suggest zipping it up as it will cut it down drastically in size and then if you could upload that it would be awesome

shabbypenguin said:
adb shell or terminal will work fine
su
dd if=/dev/block/mmcblk0 of=/sdcard/Unbrick.img bs=4096 count=50000
i would suggest zipping it up as it will cut it down drastically in size and then if you could upload that it would be awesome
Click to expand...
Click to collapse
done and zipped. Looks like it ran no problem from elevated terminal. Not sure where to upload too, maybe TPB or a dropbox. I'll PM you the login/URL.

Hello,
Is this for a similar effort as the S3 Unbrick? http://forum.xda-developers.com/showthread.php?t=2549068
Thanks.

[Q] Safe Build for Root on SM-N900V

I'm looking to root my Note 3, and I'm curious what the safe guidelines are, I can't seem to find a definitive answer on this.
There was the OTA yesterday (maybe it was on the 6th) that went out.
If that is installed, can you still root at this current point in time?
My current details are as follows:
Model: SM-N900V
Build: JSS15J.N900VVRUBMJ7
Am I SoL?
Thanks for the help.
NOTE: I tried searching , but it seems the search function is temporarily unavailable :crying:

crizznaig said:
There was the OTA yesterday (maybe it was on the 6th) that went out.
If that is installed, can you still root at this current point in time?
Click to expand...
Click to collapse
Yes, you can either use the Kingo root tool or wait until "Root de la Vega" gets a fix.
Personally, I would wait instead of using Kingo: there is some privacy concerns with using Kingo since we don't actually know how/what it does.
DroidModderX said:
The verdict is still out as to whether Kingo App is anything other than a malicious virus ridden software, or an innocent one click root method for many devices. If you do decide to use this app you should do so at your own risk. This root method is completely close sourced so we aren't sure of everything contained with in it. If this bothers you then steer clear. If you don't mind your data potentially being at risk this method is a one click method that works for a long list of devices. It has been confirmed via an XDA thread that this method will work with the Verizon Galaxy Note 3 after the latest OTA update.
Click to expand...
Click to collapse

Yeah I've read the recent situations with Kingo and Vroot as well. I'm cool with waiting, I'd prefer to not have my IMEI data mined for root
I've waited thus far.
So basically I should be following developments on the Root de la Vega stuff.
Appreciate the response

Yeah I've read the recent situations with Kingo and Vroot as well. I'm cool with waiting, I'd prefer to not have my IMEI data mined for root
I've waited thus far.
So basically I should be following developments on the Root de la Vega stuff.
Appreciate the response

Bricked
bummer, i didnt see this yesterday, and i am now bricked and looking to restore somehow back to factory via odin or whatever

crizznaig said:
I'm looking to root my Note 3, and I'm curious what the safe guidelines are, I can't seem to find a definitive answer on this.
There was the OTA yesterday (maybe it was on the 6th) that went out.
If that is installed, can you still root at this current point in time?
My current details are as follows:
Model: SM-N900V
Build: JSS15J.N900VVRUBMJ7
Am I SoL?
Thanks for the help.
NOTE: I tried searching , but it seems the search function is temporarily unavailable :crying:
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/showthread.php?t=2498850

I also just received my Note3 with that build number. Any update yet on root?

lieutenantglorp said:
I also just received my Note3 with that build number. Any update yet on root?
Click to expand...
Click to collapse
I have MJ7 and used Kingo
http://forum.xda-developers.com/showthread.php?t=2521581

Kingo Can't Connect
I have just tested Kingo with a Note 3 Verizon (N900V Firmware MJ7) and can't connect.
Thing is, I can see it find in ADB and I can issue commands via ADB. Of course USB debugging is enabled and working fine through ADB.
I'm running the latest version of Kingo 1.1.2.1770, and it just reads "Connecting service" in the bottom-right and the big "Not Connected" in the middle.
I've also attempted to connect my G-III phone which I access via ADB with no problem, and Kingo doesn't see that either.
This is my first test with a one-click root solution. I haven't found any instructions for rooting the N900V any other way (eg directly via command line) .. Anyone have any idea what I could be doing wrong, or how to root the N900V running MJ7 without Kingo?
Thank you in advance
RKM

I would assume you can use odin with stock original firmware and pit file to downgrade your phone from MJ7, use de la vega, use supersu+ "preserve superuser" functionality, then OTA update. Using supersu+/preserve option/OTA/re-enable is how I updated and kept root.

I'd be willing to bet it's your anti-virus or firewall software and that you are doing this on either Win 7 or Win 8.
Sent from my SM-N900V using Tapatalk

Also, having just read up on the latest Kingo stuff, just use it. It's fine. The latest versions don't send your IMEI. I'd still use it if they did, personally. IMEI+serials are sent around all the time when you buy/sell phones online since you need to confirm clean IMEI before paying to be sure the phone hasn't been reported stolen. Nothing bad to worry about. It's your phone, if someone could possibly do anything weird, Verizon would swap you a new one.

bigillz said:
I would assume you can use odin with stock original firmware and pit file to downgrade your phone from MJ7, use de la vega, use supersu+ "preserve superuser" functionality, then OTA update. Using supersu+/preserve option/OTA/re-enable is how I updated and kept root.
Click to expand...
Click to collapse
Doing this will soft brick your device. You cannot go back to MI9 if you are already on MJ7. Do not try to flash back to stock MI9 if you are already on MJ7.
HAZA12D_HYPERDRIVE_NOTE3

haza12d said:
Doing this will soft brick your device. You cannot go back to MI9 if you are already on MJ7. Do not try to flash back to stock MI9 if you are already on MJ7.
HAZA12D_HYPERDRIVE_NOTE3
Click to expand...
Click to collapse
Even with the proper pit file? I was under the impression the people who were soft bricking were flashing just the rom in odin, no pit. I saw another thread where people where un-bricking by flashing the pit file in the process.

bigillz said:
Even with the proper pit file? I was under the impression the people who were soft bricking were flashing just the rom in odin, no pit. I saw another thread where people where un-bricking by flashing the pit file in the process.
Click to expand...
Click to collapse
Not positive, but I think they were having to use the pit file with MJ7 after they had tried MI9. Just flashing MJ7 wouldn't work. I've been wrong before though.

G8orDroid said:
Not positive, but I think they were having to use the pit file with MJ7 after they had tried MI9. Just flashing MJ7 wouldn't work. I've been wrong before though.
Click to expand...
Click to collapse
Yes, that's what I've read too.
I'd be willing to bet it's your anti-virus or firewall software and that you are doing this on either Win 7 or Win 8.
Click to expand...
Click to collapse
Unfortunately I don't run any AV software other than the intrinsic Win7, and I had already setup exceptions for the app, disabled, it -- and I've been running Kingo "As Administrator" explicitly in each case.
It just seems so weird that ADB works flawless, and Kingo does not. They're basically the same thing (I believe Kingo is just running everything through ADB, right?)
Ugh .. so I can't downgrade to root, and I can't get Kingo to connect despite it not being related to AV apps and ADB working fine. Leave it to tech to turn a thirty minute project into days!!
Thanks again for any ideas

bigillz said:
Even with the proper pit file? I was under the impression the people who were soft bricking were flashing just the rom in odin, no pit. I saw another thread where people where un-bricking by flashing the pit file in the process.
Click to expand...
Click to collapse
Yes, even with the pit. You cannot go back to MI9 once you update.
HAZA12D_HYPERDRIVE_NOTE3
---------- Post added at 01:50 PM ---------- Previous post was at 01:46 PM ----------
rkmFL said:
Yes, that's what I've read too.
Unfortunately I don't run any AV software other than the intrinsic Win7, and I had already setup exceptions for the app, disabled, it -- and I've been running Kingo "As Administrator" explicitly in each case.
It just seems so weird that ADB works flawless, and Kingo does not. They're basically the same thing (I believe Kingo is just running everything through ADB, right?)
Ugh .. so I can't downgrade to root, and I can't get Kingo to connect despite it not being related to AV apps and ADB working fine. Leave it to tech to turn a thirty minute project into days!!
Thanks again for any ideas
Click to expand...
Click to collapse
Do you have developer options enabled and have USB debugging enabled?
HAZA12D_HYPERDRIVE_NOTE3

haza12d said:
Do you have developer options enabled and have USB debugging enabled?
Click to expand...
Click to collapse
Absolutely, yes.
I mentioned back in the original thread, I have USB debugging enabled and successfully using ADB, which requires this along with the cert approval (required as of Android 4.2 or 4.3, can't remember now).
As a developer, I use ADB on a daily basis and have never had any issue connecting to the phones.
I've re-installed Kingo, etc -- nothing. I can even fire up a command prompt while Kingo is running and send an ADB devices to see my phone successfully connected with the (with the latest Samsung drivers, right from Kingo's site stating the requirement).
Thanks again for the ideas

rkmFL said:
Absolutely, yes.
I mentioned back in the original thread, I have USB debugging enabled and successfully using ADB, which requires this along with the cert approval (required as of Android 4.2 or 4.3, can't remember now).
As a developer, I use ADB on a daily basis and have never had any issue connecting to the phones.
I've re-installed Kingo, etc -- nothing. I can even fire up a command prompt while Kingo is running and send an ADB devices to see my phone successfully connected with the (with the latest Samsung drivers, right from Kingo's site stating the requirement).
Thanks again for the ideas
Click to expand...
Click to collapse
I agree, it doesn't make a lot of sense that Kingo wouldn't connect if you can connect manually thru ADB. I believe it does use ADB to communicate. The software will take a while to run especially on a slow connection, but I am assuming from what you've said that it never gives you a "Device Connected" status, correct?
I mentioned firewall and AV earlier because some of them will block either the app or the communication. I had Trend Micro running on one of the computers I used and it wouldn't connect until I uninstalled it.

If I didn't unfreeze SDM before unrooting...

Will it still remain frozen once I get rid of root access?
Obviously i did this already, and now when I click the Update button in settings, the phone freezes.
Also, even though I unrooted the phone, it still says "Custom" on the startup screen.
Help!

deputydog95 said:
Will it still remain frozen once I get rid of root access?
Obviously i did this already, and now when I click the Update button in settings, the phone freezes.
Also, even though I unrooted the phone, it still says "Custom" on the startup screen.
Help!
Click to expand...
Click to collapse
I am in the same boat as you, As I am a noob in the Android world as I came from the apple scent. And did the update. My phone says Custom, But I have no root access.
Also wondering what steps I need to do to fix this.

SilentKiller187 said:
I am in the same boat as you, As I am a noob in the Android world as I came from the apple scent. And did the update. My phone says Custom, But I have no root access.
Also wondering what steps I need to do to fix this.
Click to expand...
Click to collapse
I'm a newb too. In over my head on this one. Had much more success with ROM's on my N2.
I'd like to return the whole thing to stock if possible.

To take the OTA, you had to unfreeze two things, the SDM 1.0, and LocalFOTA v2_1308_1_1. Otherwise when you click software update, it crashes.
Now how did you unroot. People are taking the ota and keeping root by enabling survival mode, then clicking enable superuser so that it just turns it off. Did you do that, or did you hit full unroot and get rid of it completely?
If you just turned it off, simply hit enable superuser again and it will turn on, then unfreeze the apps and update after disabling su again. If you full unrooted, then chances are you are going to have to odin to fix it. Use the root de la vega to go back and try again...can also use the MI9 tar to go back to complete stock or just flash the MJ7 odin file but beware the only way to root once on it are questionable methods atm (ie kingo)... and once you are on the new update do not try to odin back to the old one or it will fail..
The custom icon will stay there until you have root access and the xposed framework and wanam is installed with fake status on or until you odin back to complete stock.

NeoMagus said:
To take the OTA, you had to unfreeze two things, the SDM 1.0, and LocalFOTA v2_1308_1_1. Otherwise when you click software update, it crashes.
Now how did you unroot. People are taking the ota and keeping root by enabling survival mode, then clicking enable superuser so that it just turns it off. Did you do that, or did you hit full unroot and get rid of it completely?
If you just turned it off, simply hit enable superuser again and it will turn on, then unfreeze the apps and update after disabling su again. If you full unrooted, then chances are you are going to have to odin to fix it. Use the root de la vega to go back and try again...can also use the MI9 tar to go back to complete stock or just flash the MJ7 odin file but beware the only way to root once on it are questionable methods atm (ie kingo)... and once you are on the new update do not try to odin back to the old one or it will fail..
The custom icon will stay there until you have root access and the xposed framework and wanam is installed with fake status on or until you odin back to complete stock.
Click to expand...
Click to collapse
Well the first time I pushed it, It froze. I waited 10 Minutes nothing happened. I took the battery out. and it popped up again I hit install and it did.
I did none of that as I am new to this whole android world. Root is fully gone!!!
I am a little confused about using odin. Are you saying I can gain root back by using Odin and not restoring the MJ& file. I am worried If I try to down grade following the original De Vaga instructions I will brick the phone.
Please explain more. Thanks in advance

SilentKiller187 said:
I am a little confused about using odin. Are you saying I can gain root back by using Odin and not restoring the MJ& file. I am worried If I try to down grade following the original De Vaga instructions I will brick the phone.
Please explain more. Thanks in advance
Click to expand...
Click to collapse
That is exactly what will happen. Do not try to odin back to the old software from MJ7. The only way to root MJ7 so far is with Kingo which means if youre not willing to use it you gotta wait for a new safe exploit.

NeoMagus said:
To take the OTA, you had to unfreeze two things, the SDM 1.0, and LocalFOTA v2_1308_1_1. Otherwise when you click software update, it crashes.
Now how did you unroot. People are taking the ota and keeping root by enabling survival mode, then clicking enable superuser so that it just turns it off. Did you do that, or did you hit full unroot and get rid of it completely?
If you just turned it off, simply hit enable superuser again and it will turn on, then unfreeze the apps and update after disabling su again. If you full unrooted, then chances are you are going to have to odin to fix it. Use the root de la vega to go back and try again...can also use the MI9 tar to go back to complete stock or just flash the MJ7 odin file but beware the only way to root once on it are questionable methods atm (ie kingo)... and once you are on the new update do not try to odin back to the old one or it will fail..
The custom icon will stay there until you have root access and the xposed framework and wanam is installed with fake status on or until you odin back to complete stock.
Click to expand...
Click to collapse
I went ahead and used SU to delete root status for a full unroot.
If I want to go back to complete stock... How would I go about doing that? I have ODIN but I'm assuming I would need a stock MD5 file?

NeoMagus said:
That is exactly what will happen. Do not try to odin back to the old software from MJ7. The only way to root MJ7 so far is with Kingo which means if youre not willing to use it you gotta wait for a new safe exploit.
Click to expand...
Click to collapse
Thanks again!!!
Btw can you tell me why Kango cant be talked about on these forums?

deputydog95 said:
I went ahead and used SU to delete root status for a full unroot.
If I want to go back to complete stock... How would I go about doing that? I have ODIN but I'm assuming I would need a stock MD5 file?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2483380
If you want to go back to complete stock, and you are on MI9 at the moment, you can use either file, MI9 or MJ7. Again though, if you do use MJ7 to get on the new update, there is no safe way to root it atm other than kingo. So personally, I would advise either using MI9 to start over stock, or de la vega to get root back and start again

deputydog95 said:
I went ahead and used SU to delete root status for a full unroot.
If I want to go back to complete stock... How would I go about doing that? I have ODIN but I'm assuming I would need a stock MD5 file?
Click to expand...
Click to collapse
I was going to try re-rooting it with De La Vega, but not it's saying that my MD5 is corrupt when I try to extract it from the original download. This is going from bad to worse...

SilentKiller187 said:
Thanks again!!!
Btw can you tell me why Kango cant be talked about on these forums?
Click to expand...
Click to collapse
Because when you use it it connects to some server in China to download the exploit and in the process sends them information like your IMEI, serial etc the developer is working with XDA but until they update it to not take information mods do not want it used use at your own risk

NeoMagus said:
http://forum.xda-developers.com/showthread.php?t=2483380
If you want to go back to complete stock, and you are on MI9 at the moment, you can use either file, MI9 or MJ7. Again though, if you do use MJ7 to get on the new update, there is no safe way to root it atm other than kingo. So personally, I would advise either using MI9 to start over stock, or de la vega to get root back and start again
Click to expand...
Click to collapse
Confirming this is the correct file for MI9 stock? https://hotfile.com/dl/250440026/23...14_REV03_user_low_ship_MULTI_CERT.tar.7z.html
The file title is a lot longer than what was in the XDA link. Just wanted to be safe than sorry.

Need help with proper way to update.

I have been searching both here and other forums looking for guidance on this issue. I have MF3 rooted and i would like to upgrade to 4.3. When i rooted i got a little delete happy and bkew out a lot of packages instead of freezing them as i should (i didnt have Titanium Pro, i do now) . I honestly can't remember everything i blew out but i know my phone runs a lot better without them. My issue is the OTA fails when i try to install it and with all of the issues ive read about MF3 I dont know how i should proceed. Do i need to flash back to stick MF3 with Odin? Can i factory reset, root, update and hope survival mode works?
I know this makes me look like a complete toolbag but hey, i screwed up and need a little help.
Thank you

Nizzoball said:
I have been searching both here and other forums looking for guidance on this issue. I have MF3 rooted and i would like to upgrade to 4.3. When i rooted i got a little delete happy and bkew out a lot of packages instead of freezing them as i should (i didnt have Titanium Pro, i do now) . I honestly can't remember everything i blew out but i know my phone runs a lot better without them. My issue is the OTA fails when i try to install it and with all of the issues ive read about MF3 I dont know how i should proceed. Do i need to flash back to stick MF3 with Odin? Can i factory reset, root, update and hope survival mode works?
I know this makes me look like a complete toolbag but hey, i screwed up and need a little help.
Thank you
Click to expand...
Click to collapse
Use the ODIN MF3 files....ODIN your phone back to stock. This is what I did. I also rooted MF3 via SDCard method....restored my phone to how i want it. Used Supersu to do full unroot, then go to OTA update and wait 5+ hours to download the 727 mb file from the horrible AT&T servers, then install update.
Instead of "unrooting" you can try survival mode which has been said to keep root for some, but not for others.
Good luck!

Tremulant1 said:
Use the ODIN MF3 files....ODIN your phone back to stock. This is what I did. I also rooted MF3 via SDCard method....restored my phone to how i want it. Used Supersu to do full unroot, then go to OTA update and wait 5+ hours to download the 727 mb file from the horrible AT&T servers, then install update.
Instead of "unrooting" you can try survival mode which has been said to keep root for some, but not for others.
Good luck!
Click to expand...
Click to collapse
Thank you. Thats the method i was looking into but i was hoping there was an easier way. I've never used odin on any of my phones but i'll give it a shot. I appreciate your feedback.

rooted with update
Nizzoball said:
I have been searching both here and other forums looking for guidance on this issue. I have MF3 rooted and i would like to upgrade to 4.3. When i rooted i got a little delete happy and bkew out a lot of packages instead of freezing them as i should (i didnt have Titanium Pro, i do now) . I honestly can't remember everything i blew out but i know my phone runs a lot better without them. My issue is the OTA fails when i try to install it and with all of the issues ive read about MF3 I dont know how i should proceed. Do i need to flash back to stick MF3 with Odin? Can i factory reset, root, update and hope survival mode works?
I know this makes me look like a complete toolbag but hey, i screwed up and need a little help.
Thank you
Click to expand...
Click to collapse
I was also stock rooted with MF3 and i used SuperSU survival mode to keep root after the update ... but i wasn't getting the OTA so I did a sideload of the update.

Questions and Help issues go in Q&A and Help section
Thread moved
Thanks
FNSM

JCrawMil said:
I was also stock rooted with MF3 and i used SuperSU survival mode to keep root after the update ... but i wasn't getting the OTA so I did a sideload of the update.
Click to expand...
Click to collapse
How did you sideload? Ext. SD Card or ADB.

bigube said:
How did you sideload? Ext. SD Card or ADB.
Click to expand...
Click to collapse
ADB sideload pushes the package from your laptop to your phone.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

bigube said:
How did you sideload? Ext. SD Card or ADB.
Click to expand...
Click to collapse
I did an ADB sideload

Upgraded to OA8, Downgraded to NK2. Still high battery drain.

So I decided to try the upgrade to Lollipop OA8. Immediately batter life went from over a day per charge to barely 10 hours. Disabled S Health and bloat, even completely wiped device & SD card memory without any success. I even flashed non-rooted OA8 doing a full factory reset without any success in regards to battery life.
So I downgraded back to NK2, which I was phenomenal battery life. Not this time. I'm still receiving the same horrific battery life I was receiving with OA8. Android System is the culprit in both OA8 and NK2. I just recently reflashed NK2 with a full wipe and did not reinstall any apps or updates and I'm still seeing the poor battery life. I'm currently just over 4 hours on battery (from full charge) and already at 49% with Android System using nearly 60%. I'm completely stock with no root or apps!
Has anyone else have this issue? I can't see the OA8 update physically screwing up the device, but I suppose anything's possible when VZW gets their hands on things. I thought about wiping and contacting VZW to send me a replacement but I can only assume it would be shipped with OA8, which I do not want!
Suggestions?

Nobody else having this problem?
I just don't get it. My wife's S5, which was never upgraded to Lollipop has phenomenal battery life, much like mine prior to trying OA8. She's currently at 31% at nearly 20 hours and 2.5 hours screen time. I'm at 29% with just under 7 hours and 1.5 hours screen time. I'm refusing to let her upgrade her S5 for this very reason! What could cause this? I'm really tired of being tethered to a charger. I have a second battery and it's doing it on that one as well. Nothing really stands out other than "Android System" using more battery than "Screen", which was always the case, although my wife's phone shows the same.
Verizon won't even swap the phone because they call it a software issue and a new phone will do the same thing (what?), plus their new phones, according to the CSR the new phones already have OA8 installed.
I'll tell you what, I'm done with Samsung. I wish I could say I would be done with VZW also, but they're really the only one in the area with decent coverage. AT&T is close and actually has more tower saturation, but signals stink. TMO has barely any service and no LTE, and Sprint just sucks even on a full signal.
EDIT: I tried a last-ditch effort and so far it's paying off. I decided to ODIN all the way back to NCG and let the phone update to NK2. Then rooted and installed my apps. So far so good. Overnight, even with nearly 2 hours of screen time battery is at 55% and just over 10 hours of battery life. I call that a success!
So, if you're having the same issue, be sure to ODIN all the way back to the original NCG and let the phone update to NK2 (or NK7 if you wish). The NCG ODIN .tar.md5 file contains files that are not included with the later ODIN files which also completely wipes the phone. Customize, root & install files once you reach NK2 or NK7.

I have a buddy who took OA8 OTA on a stock phone. Apparently OA8 cannot be rooted. Can we just Odin downgrade his stock, non-rooted phone?

If you read what I posted you'd see that I have successfully used Odin to perform the downgrade.
Sent from my SM-G900V using Tapatalk

knowcontrol said:
I have a buddy who took OA8 OTA on a stock phone. Apparently OA8 cannot be rooted. Can we just Odin downgrade his stock, non-rooted phone?
Click to expand...
Click to collapse
OA8 is rootable. You just have to downgrade to NCG. Root your phone, then upgrade back to OA8 using this method.
http://forum.xda-developers.com/ver...l/how-to-update-to-g900vvru1boa8-5-0-t3020546

RyanThaDude said:
If you read what I posted you'd see that I have successfully used Odin to perform the downgrade.
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
Thank you. Yes, I saw that but it wasn't clear if you were stock prior and if you were rooted prior. This is good news.
---------- Post added at 07:46 AM ---------- Previous post was at 07:43 AM ----------
Tulsadiver said:
OA8 is rootable. You just have to downgrade to NCG. Root your phone, then upgrade back to OA8 using this method.
http://forum.xda-developers.com/ver...l/how-to-update-to-g900vvru1boa8-5-0-t3020546
Click to expand...
Click to collapse
Thank you very much for the reply and link, it's difficult to find a needle in this sea of information.

knowcontrol said:
Thank you. Yes, I saw that but it wasn't clear if you were stock prior and if you were rooted prior. This is good news.
---------- Post added at 07:46 AM ---------- Previous post was at 07:43 AM ----------
Thank you very much for the reply and link, it's difficult to find a needle in this sea of information.
Click to expand...
Click to collapse
No problem. In the original post in the above link, skip down to "notes #5". This will tell you how to start from an unrooted phone.

A few quick questions.
After flashing NCG in Odin, should we flash the NCG Kernel? What about the NCG modem?
After flashing NCG, do we need to have the phone fully boot before we go back to Odin to flash NK2 or can we just stay in Odin after flashing NCG and immediately flash NK2? Same questions - what about the NCG/NK2 Kernel and modems?
Oh. Assuming I get him onto NCG and rooted, at what point do you lose root? Is that during the Odin flash or when doing a full wipe in Safestrap? Sorry, dumb question - it has just been awhile since I've done these similar steps for my own S4.

knowcontrol said:
A few quick questions.
After flashing NCG in Odin, should we flash the NCG Kernel? What about the NCG modem?
After flashing NCG, do we need to have the phone fully boot before we go back to Odin to flash NK2 or can we just stay in Odin after flashing NCG and immediately flash NK2? Same questions - what about the NCG/NK2 Kernel and modems?
Click to expand...
Click to collapse
What firmware do you want to end up on? If you do not yet have root, then In Odin you flash the NCG file located in the notes #5 as indicated above. Your phone will reboot and you will be on NCG. You should have towelroot already downloaded onto your ext SD card ( safestrap 3.75 as well). Root your phone with towelroot " make it rain". Install busy box and SuperSU from the play store if you don't already have them on your ext SD card as well. Safestrap comes last. You are now rooted on NCG. Keep in mind that all the files mentioned in the beginning of the post should already be on your computer. Go into download mode and follow the rest of the post. There are no modems to flash. Not sure if this answers your questions.

Oh. Assuming I get him onto NCG and rooted, at what point do you lose root? Is that during the Odin flash or when doing a full wipe in Safestrap? Sorry, dumb question - it has just been awhile since I've done these similar steps for my own S4.
---------- Post added at 09:40 PM ---------- Previous post was at 09:38 PM ----------
Tulsadiver said:
What firmware do you want to end up on? If you do not yet have root, then In Odin you flash the NCG file located in the notes #5 as indicated above. Your phone will reboot and you will be on NCG. You should have towelroot already downloaded onto your ext SD card ( safestrap 3.75 as well). Root your phone with towelroot " make it rain". Install busy box and SuperSU from the play store if you don't already have them on your ext SD card as well. Safestrap comes last. You are now rooted on NCG. Keep in mind that all the files mentioned in the beginning of the post should already be on your computer. Go into download mode and follow the rest of the post. There are no modems to flash. Not sure if this answers your questions.
Click to expand...
Click to collapse
I'd like to get him on the last KitKat update (which I understand to be NK2?) and get him on a good debloated custom ROM. He does not like Lollipop at all! And yes, thank you for the breakdown - those are the very steps that I'm putting into a document for him to follow. These are all very similar steps to my own S4 so it's not too unfamiliar.

knowcontrol said:
Oh. Assuming I get him onto NCG and rooted, at what point do you lose root? Is that during the Odin flash or when doing a full wipe in Safestrap? Sorry, dumb question - it has just been awhile since I've done these similar steps for my own S4.
---------- Post added at 09:40 PM ---------- Previous post was at 09:38 PM ----------
I'd like to get him on the last KitKat update (which I understand to be NK2?) and get him on a good debloated custom ROM. He does not like Lollipop at all! And yes, thank you for the breakdown - those are the very steps that I'm putting into a document for him to follow. These are all very similar steps to my own S4 so it's not too unfamiliar.
Click to expand...
Click to collapse
I'm on NI2 and it is my favorite. You don't lose root. That is what SuperSU is for. After getting root on NGC, follow these instructions.
http://forum.xda-developers.com/verizon-galaxy-s5/general/how-to-update-to-g900vnk7-4-4-4-t3037902

Update: I got my buddy downgraded, rooted and then upgraded to Optimal ROM successfully! He's loving it so far. Thanks to the both of you, I really appreciate it!