[Q] Odin after ND8 upgrade - Sprint Samsung Galaxy S III

So this isn't really a problem for me yet, but yesterday I tried to flash MK3 with odin while on Stock ND8 because I was worried about having L710VPUDND8 which I got from here as a download, when the version Sprint is suppost to be rolling out is L710VPUCND8. Not sure why the OTA would differ from the one I got here, but anyways I tried flashing back to MK3 so I could just get the update when it was pushed to my cell and the flash failed after it got to the "aboot" part. Im wondering if this is because the version I have is higher then the version I want? And is there any way to circumvent this and go back to MK8. Also does anyone have any information about the difference between PUCND8 and PUDND8? Im worried because I want to make sure I get future updates such as 4.4.3 which Im sure they will come out with. So as you see its not really a problem right now, but could become one in the future possibly.

Ryan92394 said:
So this isn't really a problem for me yet, but yesterday I tried to flash MK3 with odin while on Stock ND8 because I was worried about having L710VPUDND8 which I got from here as a download, when the version Sprint is suppost to be rolling out is L710VPUCND8. Not sure why the OTA would differ from the one I got here, but anyways I tried flashing back to MK3 so I could just get the update when it was pushed to my cell and the flash failed after it got to the "aboot" part. Im wondering if this is because the version I have is higher then the version I want? And is there any way to circumvent this and go back to MK8. Also does anyone have any information about the difference between PUCND8 and PUDND8? Im worried because I want to make sure I get future updates such as 4.4.3 which Im sure they will come out with. So as you see its not really a problem right now, but could become one in the future possibly.
Click to expand...
Click to collapse
DO NOT ODIN MK3 IF YOU ARE ON ND8, flash a custom ROM if you wanna go to MK3, do not flash the firmware, and I doubt there will be anymore updates. This won't work because the Knox Bootloader won't let you downgrade your firmware and you can easily brick your device trying to do so.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

bilgerryan said:
DO NOT ODIN MK3 IF YOU ARE ON ND8, flash a custom ROM if you wanna go to MK3, do not flash the firmware, and I doubt there will be anymore updates
Click to expand...
Click to collapse
Okay, so just install a custom recovery and use that to flash a zipped custom rom then use odin to flash MK3?

Ryan92394 said:
Okay, so just install a custom recovery and use that to flash a zipped custom rom then use odin to flash MK3?
Click to expand...
Click to collapse
No you can't downgrade to MK3 firmware you will brick. Knox won't allow it. Install a custom recovery, flash an MK3 ROM if that's what you want, but you can't go back to factory MK3.

bilgerryan said:
No you can't downgrade to MK3 firmware you will brick. Knox won't allow it. Install a custom recovery, flash an MK3 ROM if that's what you want, but you can't go back to factory MK3.
Click to expand...
Click to collapse
Okay, then the only thing left to ask is if you know of what the difference between PUCND8 and PUDND8 is? That is really my main concern. I just wanted to go back to mk3 to get the OTA update from sprint instead of from the zip file I downloaded from here. Could it be that Sprint made a mistake on their website showing L710PUCND8 when the version is actually PUDND8?

lol I just noticed your name is Ryan <3 awesome name =-D lol we even have the same join date oct 2011. Thatd be crazy if we had the same birthdate lmao im Sept '87 was I close? lmao

Ryan92394 said:
Okay, then the only thing left to ask is if you know of what the difference between PUCND8 and PUDND8 is? That is really my main concern. I just wanted to go back to mk3 to get the OTA update from sprint instead of from the zip file I downloaded from here. Could it be that Sprint made a mistake on their website showing L710PUCND8 when the version is actually PUDND8?
Click to expand...
Click to collapse
Not sure exactly, I know N=2014, D=April, 8= 8th build of the month... Where did you see PUCND8? I took the actual OTA and it was PUDND8.

bilgerryan said:
Not sure exactly, I know N=2014, D=April, 8= 8th build of the month... Where did you see PUCND8? I took the actual OTA and it was PUDND8.
Click to expand...
Click to collapse
from here: https://community.sprint.com/baw/message/782055#782055
and alternately here: http://support.sprint.com/support/a...ndUpdateTheSoftwareVersionOnYourSamsungGalaxy

bilgerryan said:
Not sure exactly, I know N=2014, D=April, 8= 8th build of the month... Where did you see PUCND8? I took the actual OTA and it was PUDND8.
Click to expand...
Click to collapse
Any ideas?

Ryan92394 said:
Any ideas?
Click to expand...
Click to collapse
The PUC is based on Sprint's official OTA source code. PUD is based on Samsung source code for all Sprint devices (Virgin Mobile, Boost, etc). That is the only difference from what I understand.

Related

[Q] [IAMNOOB] can I flash I747UCALG1 when I'm in I747UCALH9 already?

Hello devs, I have a quick question here. I've read as many threads here as I can, but I still have this doubt before I go ahead and try to root my phone.
I just bought my Galaxy S3 I747 from AT&T yesterday, which came as I747UCALG1. Today it automatically downloaded the package from the network and updated to:
Build Number: IMM76D.I747UCALH9
Baseband Version: I747UCLH9
Kernal Version: 3.0.8-985684
My question is, since the phone is already in a newer version of firmware (I747UCALH9), can I follow mrRobinson's thread (http://forum.xda-developers.com/showthread.php?t=1739426) and flash back to ATT I747UCALG1, which is actually a relatively older version, using Odin? I ask this because I have a PS3 and I know that it is technically not allowed to perform a "downgrade", and I know that it very complicated to downgrade iPhone's baseband as well. So I don't know whether this is the case for Galaxy S3 here
I just want to get my phone rooted so far. Thanks for your patience! Please let me know your comments.
First, questions should be asked in Q&A.
Odin will flash any firmware to your phone. That's why it's important to get the right dl.
But,
Even if you flash back to LG1, you will get prompted to update again.
slinson said:
Hello devs, I have a quick question here. I've read as many threads here as I can, but I still have this doubt before I go ahead and try to root my phone.
I just bought my Galaxy S3 I747 from AT&T yesterday, which came as I747UCALG1. Today it automatically downloaded the package from the network and updated to:
Build Number: IMM76D.I747UCALH9
Baseband Version: I747UCLH9
Kernal Version: 3.0.8-985684
My question is, since the phone is already in a newer version of firmware (I747UCALH9), can I follow mrRobinson's thread (http://forum.xda-developers.com/showthread.php?t=1739426) and flash back to ATT I747UCALG1, which is actually a relatively older version, using Odin? I ask this because I have a PS3 and I know that it is technically not allowed to perform a "downgrade", and I know that it very complicated to downgrade iPhone's baseband as well. So I don't know whether this is the case for Galaxy S3 here
I just want to get my phone rooted so far. Thanks for your patience! Please let me know your comments.
Click to expand...
Click to collapse
If your just looking for root, flash CWM with ODIN and then flash superSU with recovery.http://forum.xda-developers.com/showthread.php?t=1538053 Your counter will go up but then you can install triangle away and reset the flash counter. http://forum.xda-developers.com/showthread.php?t=1494114. This should take less than 5 minutes after you have read everything.
If your completly new to this check out this thread http://forum.xda-developers.com/showthread.php?t=1903437
Read this http://forum.xda-developers.com/showthread.php?t=1802160
and pretty much read all stickies.
nakedninja42 said:
If your just looking for root, flash CWM with ODIN and then flash superSU with recovery.http://forum.xda-developers.com/showthread.php?t=1538053 Your counter will go up but then you can install triangle away and reset the flash counter. http://forum.xda-developers.com/showthread.php?t=1494114. This should take less than 5 minutes after you have read everything.
If your completly new to this check out this thread http://forum.xda-developers.com/showthread.php?t=1903437
Read this http://forum.xda-developers.com/showthread.php?t=1802160
and pretty much read all stickies.
Click to expand...
Click to collapse
thanks dude!
mrhaley30705 said:
First, questions should be asked in Q&A.
Odin will flash any firmware to your phone. That's why it's important to get the right dl.
But,
Even if you flash back to LG1, you will get prompted to update again.
Click to expand...
Click to collapse
does that mean I'll lost root after I update?
After LH9 update, maybe. After flashing the stock firmware, definitely. There is a no trip root method (won't touch your flash counter).
mrhaley30705 said:
After LH9 update, maybe. After flashing the stock firmware, definitely. There is a no trip root method (won't touch your flash counter).
Click to expand...
Click to collapse
If I understand it correctly....what mrRobinson mentioned as the following link is the no tripping method. Basically it flashes rooted official ware so the counter wouldn't be triggered, I assume? http://forum.xda-developers.com/showthread.php?t=1739426
And even if I've done that, I still need to come up with a solution when it prompts LH9 OTA again....emmmm
Thanks a lot mrhaley!:good::laugh:
If you just want to maintain root, try this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
just follow the directions in the app.
mrhaley30705 said:
If you just want to maintain root, try this:
just follow the directions in the app.
Click to expand...
Click to collapse
thanks mrhaley30705:laugh::good::good:! you are the man!
Several people who have gone back from LH9 to LG1 get an error about android.process.acore failing when they boot. If that happens, do a factory reset in recovery and reboot.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
If u t rooted just freeze the ATT update app. Will not try to update.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
lgkahn said:
If u t rooted just freeze the ATT update app. Will not try to update.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I intend on downgrading back to LG1 also being as I get horrible battery life with LH9.
Are there any other options besides freezing it? I know titanium will freeze apps, but I hate to install that app just for one thing, being as I would never use anything else in there. Plus if I remember correctly, I think you need to purchase titanium to freeze apps. Not that I'm cheap, but I'd hate to buy the app just to freeze one thing.
So I am just trying to explore other options as well. Preferably free options.

[OTA][ZIP] Kitkat ND8 full unmodified ota

Full UNMODIFIED ota. Don't take if you don't want to:
Download: http://android.clients.google.com/p...fbe72.USER_L710_SPR_MK3_to_ND8_Update_FWD.zip
I take no responsibility for your actions if you flash this.
Requirements:
1) Be on stock, odexed, unmodified MK3 rom
2) May or may not work by flashing through custom recovery, otherwise flash with stock recovery
Thanks bilgerryan for the filename
I can confirm not working with CWM 6.0.4.3.
Sent from my SPH-L710 using XDA Free mobile app
It won't work in custom recovery, guaranteed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have to say, as tempting as it would be to flash to stock 4.3 to take this update, I'm already on 4.3 bootloader and if this is knoxed and prevents me from going back to 4.3, it's definitely not worth trying to flash until the guys make it safe to do so.
Edit: I'm sure someone has already tried so let know how it goes.
Be careful here guys. If you read XDA I'd say there is a 90% chance that you DON'T want to flash this one or accept the OTA from Sprint. Wait for an update labeled "Root + deKnoxed" or similar.
Way to go CNexus for grabbing this so quick!
Give it a day or 2 and we'll have a Rooted stock deodexed. Can't wait thanks cnexus
Md4 Rooted Modded....... Flawless
I'm on stock MK3 and not interested in root at this time.
Copy to SD card, rename to update.zip and reboot?
CNexus said:
Full UNMODIFIED ota. Don't take if you don't want to:
A) Be on the new Knox bootloader
B) Be assured that you will be able to root again
Download: http://android.clients.google.com/p...fbe72.USER_L710_SPR_MK3_to_ND8_Update_FWD.zip
I take no responsibility for your actions if you flash this.
Requirements:
1) Be on stock, unmodified MK3 rom
2) May or may not work by flashing through custom recovery
Click to expand...
Click to collapse
While we wait, there are definitely Knox support files in the OTA.
Guess we'll hear eventually if the bootloader is Knoxed as well.
tpapa said:
I'm on stock MK3 and not interested in root at this time.
Copy to SD card, rename to update.zip and reboot?
Click to expand...
Click to collapse
I believe it needs to be placed in /cache, at least that's where mine was when I got the OTA this morning.
Edit: Never mind, you're not rooted
I have a Knox bootloader. 4.3 would this matter if I wanted to flash this?
mholloway said:
I have a Knox bootloader. 4.3 would this matter if I wanted to flash this?
Click to expand...
Click to collapse
No, it'll just update your bootloader to the ND8 Knox bootloader
tpapa said:
I'm on stock MK3 and not interested in root at this time.
Copy to SD card, rename to update.zip and reboot?
Click to expand...
Click to collapse
Copy to SD Card (needs to be an external SD card if I recall), rename to update.zip, power down, reboot to (stock) recovery, choose install update.zip. This will not work from a custom recovery only stock.
Keep in mind, if you don't like what you see, you will most likely not be able to return to MK3.
CNexus said:
No, it'll just update your bootloader to the ND8 Knox bootloader
Click to expand...
Click to collapse
That's cool.very tempting but I love my root.lol.i guess couldn't flash superuser zip after installing.lol .
WiFi Calling?
Can anyone who's installed ND8 confirm whether the update includes WiFi calling? Thanks in advance.
If anyone can grab the TAR I'll make some one-clicks today.
rwilco12 said:
If anyone can grab the TAR I'll make some one-clicks today.
Click to expand...
Click to collapse
Tar isn't available yet, probably in a few days once kies syncs with Samsung's servers and gets it
Plonko said:
Can anyone who's installed ND8 confirm whether the update includes WiFi calling? Thanks in advance.
Click to expand...
Click to collapse
No wi-fi calling...
Soft bricked during installation. just need to be pointed in the right direction to return to MK3 if possible. Im stuck on Samsung bootloader
Cooljb said:
No wi-fi calling...
Click to expand...
Click to collapse
Well that's just a kick in the pants, but thank you very much for confirming. I guess I'm stuck with my lousy Airave a while longer.
Plonko said:
Can anyone who's installed ND8 confirm whether the update includes WiFi calling? Thanks in advance.
Click to expand...
Click to collapse
Pretty sure Sprint won't have Wi-Fi calling for awhile, it doesn't benefit them and their major pull is unlimited data. You can always use a Wi-Fi calling app like "WiCall" or "PHONE for Google Voice" or "GrooveIP"

[Q] Moving beyond Cyanogenmod 10

I just rooted my wife's Sprint Galaxy S3 (d2spr) and managed to install Cyanogenmod 10. Back when we were on another carrier, I had installed later versions of the ROM, but only after a LOT of reading. Running the latest CWM, running the latest TWRP, doesn't matter. I cannot install later versions. The wiki says:
WARNING: Firmware update notice
CM10.1 and newer are not compatible with ICS bootloaders on this device. Update your device's firmware or you will get assert failures in recovery.
That is exactly my problem, but how do I perform this firmware update? I hope it's not an issue of reverting to stock, because Knox was enough trouble to overcome. I referred to this thread http://forum.xda-developers.com/showthread.php?t=1787677 to update the baseband, which just stopped the phone from connecting to towers.
What am I missing? Where do I get this firmware? Once updated, will I then be able to avoid further Status 7 errors? (Editing the updater-script every time seems like a hoaky band-aid when one has downloaded the exact, correct, tailor-made ROM.) Thanks a lot to the community. I've learned everything I know from these forums, and I felt like I had hit enough of a dead end to ask for help.
I think you would have to odin a stock jb .tar, NOT KITKAT and then you reroot and flash whatever rom you want. Some of your concerns might be alleviated if you use tibu and back-up apps to an external sd, as well as nandroid to an external sd.
Edit: CNexus or Freeza might have their stock .tars for jb versions around here, they even come rooted too
Edit 2: This thread might have what you need: http://forum.xda-developers.com/showthread.php?t=1910947
I suggest waiting until someone else confirms though (but if I'm right you'll want the link that says "firmware/modem/baseband update", the 5th link)
Sent from my SPH-L710 using XDA Free mobile app
sevenpioverthree said:
I think you would have to odin a stock jb .tar, NOT KITKAT and then you reroot and flash whatever rom you want. Some of your concerns might be alleviated if you use tibu and back-up apps to an external sd, as well as nandroid to an external sd.
Edit: CNexus or Freeza might have their stock .tars for jb versions around here, they even come rooted too
Edit 2: This thread might have what you need: http://forum.xda-developers.com/showthread.php?t=1910947
I suggest waiting until someone else confirms though (but if I'm right you'll want the link that says "firmware/modem/baseband update", the 5th link)
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
why not the KK stock ND8 tar?
6th_Hokage said:
why not the KK stock ND8 tar?
Click to expand...
Click to collapse
Because i have read a bit about it and i believe that flashing the firmware might wipe internal data and it comes with knox as well. And from what you posted, all you need is a jb firmware. But that's also why I said to wait until someone more knowledgeable confirms what I'm saying
Sent from my SPH-L710 using XDA Free mobile app
sevenpioverthree said:
Edit 2: This thread might have what you need: http://forum.xda-developers.com/showthread.php?t=1910947
Click to expand...
Click to collapse
Just confirming, that's the correct one.
[BATTERY] Plasma Battery! v2a ??? & wickeddecimalbarwide_colors
Charging still shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
n00b-xda-disciple's Wicked X Video review
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v5.2, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
You people are awesome!
Thank you. I will try it tomorrow, and check back. Samsung has done a lot to thwart rooting lately, and I didn't want to close any doors by installing something TouchWiz-based.
Argh!
Link #5 is broken. Crap. Back to reading...
badmojorayman said:
Link #5 is broken. Crap. Back to reading...
Click to expand...
Click to collapse
If you go to that same thread and find the spoiler under "old versions" (bottom of post #1) you can flash the "MB1 firmware/modem/baseband update" as well
Sent from my SPH-L710 using XDA Free mobile app
badmojorayman said:
I just rooted my wife's Sprint Galaxy S3 (d2spr) and managed to install Cyanogenmod 10. Back when we were on another carrier, I had installed later versions of the ROM, but only after a LOT of reading. Running the latest CWM, running the latest TWRP, doesn't matter. I cannot install later versions. The wiki says:
WARNING: Firmware update notice
CM10.1 and newer are not compatible with ICS bootloaders on this device. Update your device's firmware or you will get assert failures in recovery.
That is exactly my problem, but how do I perform this firmware update? I hope it's not an issue of reverting to stock, because Knox was enough trouble to overcome. I referred to this thread http://forum.xda-developers.com/showthread.php?t=1787677 to update the baseband, which just stopped the phone from connecting to towers.
What am I missing? Where do I get this firmware? Once updated, will I then be able to avoid further Status 7 errors? (Editing the updater-script every time seems like a hoaky band-aid when one has downloaded the exact, correct, tailor-made ROM.) Thanks a lot to the community. I've learned everything I know from these forums, and I felt like I had hit enough of a dead end to ask for help.
Click to expand...
Click to collapse
Hold the phone! (Pun intended) There are two context clues in your op that lead me to believe that you should under no circumstances flash any firmware found in that firmware thread linked here.
1
badmojorayman said:
Knox was enough trouble to overcome.
Click to expand...
Click to collapse
If you have Knox your bootloader cannot be downgraded.
2
badmojorayman said:
I referred to this thread http://forum.xda-developers.com/showthread.php?t=1787677 to update the baseband, which just stopped the phone from connecting to towers.
Click to expand...
Click to collapse
The only time I've personally witnessed this behavior is on the ND8 bootloader. If you don't know which bootloader you're on already you would be wise to find out before flashing any firmware file.
You've all given good advice, but the best advice came too late. The phone no longer powers on because of the baseband update I was attempting. I'm now waiting for a MicroSD card to show up so that I can attempt this:
http://forum.xda-developers.com/showthread.php?t=2345860&page=63

[Q] 4.4.4 NH7 No sound?

Hello everyone!
Recently I've decided to flash over to the new NH7 Update because I wanted to try out the 4.4.4 Modem. After flashing both the ROM and Modem, I no longer have any sound. I'm a "bit" new to some of this so I'm hoping I could get some help. I've flashed plenty of other ROMS and Modems before without an issue (At least issues I could fix) but I can't seem to find any information on how one would fix this problem. I'm assuming the problem is the 4.4.4 Modem?
I'm also having the lockscreen freeze up on me when I try to unlock the phone. If I let the phone set for a while it settles down but it's still really buggy. Seems to do this with any ROM I flash and random things FC on me.
Lastly, Not sure if this helps with the problem but every time I boot into recovery and go to start the phone, it tells me that I lost root and gives me the option to fix. If I choose not to fix, I still have root. No idea why it prompts me about this?
Anyway, here's some info on what I did.
Flashed this ROM and used the modem provided in the thread - http://forum.xda-developers.com/gal...-4-4-4-nh7-insane-kit-kat-v1-9-14-14-t2876946
1 Wiped Cache, Dalvik, Data, Factory reset with TWRP
2 Flashed ROM with TWRP
3 Put phone in download mode and flashed the NON-HLOS.bin
4 Restarted then booted download and flashed Modem.bin
5 Restarted normally and setup phone like normal.
6 No sound :/
Used the latest version of TWRP I could find. (2.8.1 I believe?)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyway, thanks for any help you guys can give!
Jeff
Try the double flash method (start from phone off, flash without auto reboot, pull battery, boot back to ODIN, flash again, pull battery, boot normally). Some bits may not have updated. This will fix it.
The thing about losing root is I believe a known TWRP bug in that version.
Marc
Hi Marc
I've tried the method you describe with no luck
Oh, I suppose it's worth mentioning that I'm using ODIN version 3.0.7
Thanks,
Jeff
For Sickness' 4.4.4 ROM you have to be on the NH7 bootloader for it to fully work with no issues
And also, try TWRP 2.7.0.0. I use TWRP 2.6.3.1 and never have had an issue
Kriptik210 said:
For Sickness' 4.4.4 ROM you have to be on the NH7 bootloader for it to fully work with no issues
And also, try TWRP 2.7.0.0. I use TWRP 2.6.3.1 and never have had an issue
Click to expand...
Click to collapse
Hey Kriptik210
For the bootloader I'm not exactly sure where to find it. (I have a link to what I think is a bootloader but I'm not allowed to post it until 10 posts)
If you look at my screenshot. It says Baseband Version m919uvufnh7. Isnt this the bootloader?
Sorry if I sound silly. I've never really had to update stuff like this before. It's really new to me.
Thanks,
Jeff
jeffreythe00 said:
Hey Kriptik210
For the bootloader I'm not exactly sure where to find it. (I have a link to what I think is a bootloader but I'm not allowed to post it until 10 posts)
If you look at my screenshot. It says Baseband Version m919uvufnh7. Isnt this the bootloader?
Sorry if I sound silly. I've never really had to update stuff like this before. It's really new to me.
Thanks,
Jeff
Click to expand...
Click to collapse
Baseband is the modem, build number is the bootloader. I don't see a screenshot anywhere
Ok, thank you for clarifying.
I'm going to download the 4.4.4 OTA and flash it VIA ODIN, then re-root. I've read towelroot v2 can root 4.4.4 without tripping knox.
jeffreythe00 said:
Ok, thank you for clarifying.
I'm going to download the 4.4.4 OTA and flash it VIA ODIN, then re-root. I've read towelroot v2 can root 4.4.4 without tripping knox.
Click to expand...
Click to collapse
You can't do OTA if you don't have the stock firmware already on your phone. But you can Odin.
You can use this link if you need anything...
http://www.droidviews.com/update-t-mobile-galaxy-s4-to-android-4-4-4-kitkat-and-root-it/
I got it. Sound is working now. I was apparently on the MDL bootloader. I used this thread http://forum.xda-developers.com/galaxy-s4-tmobile/help/nb4-to-nh7-firmware-upgrade-via-odin-t2880284 to get updated and re-rooted. Thanks for the help. I never would have known about the bootloader if it had not of been for this thread. I think I can handle the rest from here
Cheers!
Jeff
If you are unsure of your bootloader, there is a Phone Info Samsung app in the play store. IT will show you your boot loader version, modem baseband, etc..
Kriptik210 said:
Baseband is the modem, build number is the bootloader. I don't see a screenshot anywhere
Click to expand...
Click to collapse
Build number is the software version. It's defined in the build prop. Has nothing to do with the bootloader. Can make it say whatever you want. Unless That is Samsung is stealing mine and sickness' rom names and making bootloaders called HispAsian rom and Insane 4.4.4 haha in which I better be receiving a check
To find your bootloader version, download android terminal emulator from the playstore and type
getprop ro.bootloader
And hit enter.
ShinySide said:
Build number is the software version. It's defined in the build prop. Has nothing to do with the bootloader. Can make it say whatever you want. Unless That is Samsung is stealing mine and sickness' rom names and making bootloaders called HispAsian rom and Insane 4.4.4 haha in which I better be receiving a check
To find your bootloader version, download android terminal emulator from the playstore and type
getprop ro.bootloader
And hit enter.
Click to expand...
Click to collapse
Part of me knew this.....lol
Edit....................

Bricked ?

Got stuck with boot loop and this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I would appreciate any help....
erik077 said:
Got stuck with boot loop and this
I would appreciate any help....
Click to expand...
Click to collapse
Could you explain what you were on, what you did to get you to where you are and what was used that prompted that message?
Updated from 4.4 to Lolipop and tried to root it...
erik077 said:
Updated from 4.4 to Lolipop and tried to root it...
Click to expand...
Click to collapse
Which version of lollipop did you try to ODIN ?
This http://forum.xda-developers.com/note-4-sprint/development/romstockishno-knox-8-7-15-sprint-t3174350
erik077 said:
This http://forum.xda-developers.com/note-4-sprint/development/romstockishno-knox-8-7-15-sprint-t3174350
Click to expand...
Click to collapse
You didnt have the correct Baseband for that.
FLash this first
http://forum.xda-developers.com/note-4-sprint/general/n910p-c0g5-tar-files-return-to-stock-t3174291
then
samep said:
Just the opposite with OG5: power down Odin stock tar (auto boot enabled), Odin TWRP (auto boot disabled- pull battery and USB when done), boot recovery to flash freeza kernel, recovery flash SuperSU zip.
Click to expand...
Click to collapse
Downloading...
Just to explain: I managed to update to Lolipop but this first happened when trying to root. After root failed I tried link I provided but that restore gave me same error
erik077 said:
Downloading...
Just to explain: I managed to update to Lolipop but this first happened when trying to root. After root failed I tried link I provided but that restore gave me same error
Click to expand...
Click to collapse
Indeed, just dont forget the kernel before rooting this time and you should be good.
https://www.androidfilehost.com/?fid=24052804347789588
xxSTARBUCKSxx said:
You didnt have the correct Baseband for that.
FLash this first
http://forum.xda-developers.com/note-4-sprint/general/n910p-c0g5-tar-files-return-to-stock-t3174291
then
Click to expand...
Click to collapse
You'll love this... Now the theory is to stay on OB7 or lower bootloader, and Odin flash the OG5 modem only and then flash OG5 custom ROM to stay away from reactivation locked bootloader.
I'm not sure at what point giving up the unlocked (for reactivation) bootloader is worth keeping once updates justify waving bye to KitKat or original OB7 ROMs in favor of attaining full functionality or compatibility with updates? Sitting back a little longer to decide if update fully with tar or just bump the modem to OG5 is best. Stay tuned for more ever evolving theories, workarounds and "what the bricks?" is this.
Who knows, there may be more value in having the older bootloader if considering a near term sell to upgrade.
BTW, looks like the kernel exploit is currently only available in freeza's new OG5 stock ROM.
Sent from my SM-N910P using Tapatalk
samep said:
You'll love this... Now the theory is to stay on OB7 or lower bootloader, and Odin flash the OG5 modem only and then flash OG5 custom ROM to stay away from reactivation locked bootloader.
I'm not sure at what point giving up the unlocked (for reactivation) bootloader is worth keeping once updates justify waving bye to KitKat or original OB7 ROMs in favor of attaining full functionality or compatibility with updates? Sitting back a little longer to decide if update fully with tar or just bump the modem to OG5 is best. Stay tuned for more ever evolving theories, workarounds and what the bricks?
Who knows, there may be more value in having the older bootloader if considering a near term sell to upgrade.
BTW, looks like the kernel exploit is currently only available in freeza's new OG5 stock ROM.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
*facepalm* Werll, at least hell be able to get back on his feet from the stock tar.. and go from there....
i was actually thinking about that myself very often in the past weeks.. the resell value that is.
This whole thing is odd, people with the same hardware having to perform the same basic operations, but in different steps for the same end- result is just insane....
xxSTARBUCKSxx said:
Indeed, just dont forget the kernel before rooting this time and you should be good.
https://www.androidfilehost.com/?fid=24052804347789588
Click to expand...
Click to collapse
Should I root with "CF-Auto-Root-trltespr-trltespr-smn910p" ?
erik077 said:
Should I root with "CF-Auto-Root-trltespr-trltespr-smn910p" ?
Click to expand...
Click to collapse
This works
http://forum.xda-developers.com/showpost.php?p=55256620&postcount=1
Sent from my SM-N910P using Tapatalk
Might as well make it a useful post...
Did you at least get back on solid ground @erik077 ??
And... freeza just refreshed the exploited kernel link
https://www.androidfilehost.com/?fid=24052804347789588
Sent from my SM-N910P using Tapatalk
Thank you all, this has been resolved. I am just not sure which ROM are safe for me to flash now. Suggestions?
Making backup right now and I will experiment with some.
erik077 said:
Making backup right now and I will experiment with some.
Click to expand...
Click to collapse
Good deal. Glad youre out of that funk you were just in. Thats the best you can do at the moment. Kinda skim the end of the threads first as well as the OP before experimenting. Or experiment away! Youll have your backup.
Im hesitant to make any suggestions being on NK2 myself.
Thank you so much for your help
Last question: Can I go from OG5 to OF5 or not? If yes how.... if not I hope some room are coming soon...
erik077 said:
Last question: Can I go from OG5 to OF5 or not? If yes how.... if not I hope some room are coming soon...
Click to expand...
Click to collapse
Early reports from OTA OG5 to OF5 was no. Freeza has one and is working on custom.
Some ROMs like Sacs, Noterized or CM12 have been claimed to flash but IMO that gets away from the fixes and security that makes OG5 Android 5.1.1 I'd stay with stock or freeza OG5 stock until custom OG5 ROMs show up.
Sent from my SM-N910P using Tapatalk

Categories

Resources