Related
I made this custom OG5 rom package for myself and I wanted to share it with those of you who want to stay on your older OB7 bootloader and be fully updated to Android 5.1 OG5. There is absolutely nothing changed from the stock rom/partitions except for the bootloader. This rom includes knox, itson, etc just like the official rom tar does. This simply gets you updated properly so you can proceed to root, flash recovery, flash rooted kernel, SuperSU, etc... and keep your unlocked OB7 bootloader. Please Note: If you have already taken either the OE1. OF5 or OG5 Android 5.1 ota update or odin flashed one of these official Samsung ROM rom tars, then you will not be able to go back to an older bootloader and this package will most likely not work for you. For the rest of us who where patient and who want to properly update to 5.1 and keep our unlocked OB7 bootloader then please keep reading.
The point of this odin package is very simple. Unless you flash the official 5.1 OG5 rom tar or take the 5.1 ota update from your phone then you will not be able to fully update to 5.1 the way it needs to be done. There are device partitions other than "system" and "cache" that must be written/overwritten with updated img.ext4's. Without extracting and comparing the img's there's no way to know what differences there are between the new 5.1 and the older softwares. So it goes without saying that it would be a wise choice to make sure your device has all of these carrier partitions etc updated for piece of mind. Again, I did this for my own personal use and not because I was bored. I want to share this with those of you who can benefit from it. So let's get started with the details/Instructions.
If you understand what the purpose of this odin package is then proceed: If not then do your homework or leave your phone alone. Here are the simple steps to fully update to 5.1 and retain the OB7 bootloader.
1. Install and use Odin 3.10.6
2. download and install 7zip
3. download and extract this OG5 odin rom package in a location of your choice. (VERIFY THE MD5 BEFORE YOU EXTRACT!!!)
4. Wipe your phone in your current TWRP or do a factory data reset in the stock bootloader. or proceed without wiping your partitions. (this can result in leftover data and cause issues so wipe if at all possible for a good clean slate).
5. Reboot your phone into download mode. (With phone turned of, press and hold the home, volume down and power button until the phone boots).
6. Open Odin 3.10.6 THEN connect your phone via USB and wait for it to connect.
Leave all defaults as they are and then press the big "AP" button to select the odin package you want to flash then press start. Wait for it to finish and it will let you know when all items flashed successfully. Unplug your usb and wait for first boot.
7. Setup your device as usual. Done.
You are now fully upgraded to Android 5.1 (OG5) with all partitions correctly written to your phone as per the OG5 update.
DownloadHYBRID_OB7sbl_SPT_N910PVPU4COG5
Thank you!
Out of curiosity are there plans for a deodexed version?
Sent from my SM-N910P using XDA Free mobile app
@tx_dbs_tx
Firstly I'm still on the OB7 Bootloader. I've upgraded to 5.1.1 using freezas OG5 Baseband flash & OG5 zip. Currently I am able to restore via TWRP Recovery to OG5 or Alliance (OB7) at will with no apparent problems. Now my question:
You've made reference to partitions that should be created to properly install OG5. Once this is done (you saying it needs doing is good enough for me btw) and I nand backup in TWRP can I then expect to have issues restoring an OB7 ROM from an OG5 ROM or vice-versa or will these changes be contained within the backups?
Again cannot thank you enough for all you've done for us.
thearch1tect said:
Thank you!
Out of curiosity are there plans for a deodexed version?
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
That's out of the scope of this odin package. The sole purpose for this hybrid rom tar is to properly upgrade to 5.1 without being forced upon the new secure bootloaders. After you flash this tar you can proceed to root, flash roms, kernels, etc with confidence knowing that all of your partitions have been properly updated. Any other means of going to 5.1 without updating these partitions is not a complete upgrade to 5.1. So if you want a deodexed/custom 5.1 rom you'll have to wait for some of us to build them. But in the meantime you really should flash this and get this out of the way while you're waiting for new 5.1 roms, mods, kernels, etc.
kenjesse said:
@tx_dbs_tx
Firstly I'm still on the OB7 Bootloader. I've upgraded to 5.1.1 using freezas OG5 Baseband flash & OG5 zip. Currently I am able to restore via TWRP Recovery to OG5 or Alliance (OB7) at will with no apparent problems. Now my question:
You've made reference to partitions that should be created to properly install OG5. Once this is done (you saying it needs doing is good enough for me btw) and I nand backup in TWRP can I then expect to have issues restoring an OB7 ROM from an OG5 ROM or vice-versa or will these changes be contained within the backups?
Again cannot thank you enough for all you've done for us.
Click to expand...
Click to collapse
You will have no problem flashing back and forth between roms after flashing this odin package. It will retain your OB7 bootloader and update ALL of your partitions. You will then be completely stock unrooted OG5 with the exception of having the OB7 bootloader. From there you can restore a nandroid, flash a OB7/OG5 rom, etc.
That makes sense.
Im currently running hybrid x 1.07 with NK2 bootloader. Do I need to first upgrade the bootloaderto OB7 or does this package include the OB7 bootloader?
Sent from my SM-N910P using XDA Free mobile app
thearch1tect said:
That makes sense.
Im currently running hybrid x 1.07 with NK2 bootloader. Do I need to first upgrade the bootloaderto OB7 or does this package include the OB7 bootloader?
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
Yes. This package includes the OB7 bootloader. It will replace your NK2 bootloader but if I'm not mistaken you would still be able to odin an older NK2 tar and go back to that bootloader... not that it really makes any difference. I would say that the OB7 bootloader is what you want to go with since it's more current and still unlocked. However, If you're happy with your current setup then you can just wait for the custom OG5 roms to come out and decide then if you want to flash another rom.
tx_dbs_tx said:
Yes. This package includes the OB7 bootloader. It will replace your NK2 bootloader but if I'm not mistaken you would still be able to odin an older NK2 tar and go back to that bootloader... not that it really makes any difference. I would say that the OB7 bootloader is what you want to go with since it's more current and still unlocked. However, If you're happy with your current setup then you can just wait for the custom OG5 roms to come out and decide then if you want to flash another rom.
Click to expand...
Click to collapse
Failed for me....
Edit i dont kow why the pic is sideways
Failed for me as well
I'd like to flash this rom for the reasons you named but I am on the OF5 bootloader which is also unlocked since I used CF root to root it. Question : would you do a version of this rom including the OF5 bootloader or one that would use the bootloader already installed on the note?
To the guys it failed for:
were you coming off of an OB7 bootloader or something else? I'm guessing some bootloader other OB7.
flyhighx said:
To the guys it failed for:
were you coming off of an OB7 bootloader or something else? I'm guessing some bootloader other OB7.
Click to expand...
Click to collapse
Im on ob7 bootloader... but i did flash the og5 modem and freezas rom... just wanted to do this cause he said we missed somethings with update just flashing modem...
Since this TAR has led to confusion -- I wanted to state that I am on OB7 bootloader, and the TAR worked perfectly for me.
I'm also on OB7 bootloader and had flashed OF5 bits to use another rom. This worked perfect, now on freeza's stockish.
I flashed this last night when you first posted it in your Hybrid X thread, I was on OB7 running 2.3
I Odined all the way back to NK2 then flashed OB7 again, then this one, I flashed TWRP and Freeza's Kernel then installed Super SU from playstore and I'm not having any issues whatsoever, it runs very smooth (seems like they did a good job with this update)
I'm patiently waiting for you to make a new OG5 Hybrid X rom, I didn't want to flash Freeza's rom cause I've noticed there's a few bugs and issues.
And since it's stockish I see no point of doing so until there's new OG5 roms.
Thank You Sir!! :good::good:
Just to be clear for me. After updating to this ROM, can u root it? Or do we have to wait for something other than CF Root? All my apps are backed up and no way to restore just yet, thx
Disregard, installed TWRP, then flashed Freeza Mod Kernal and SU.
twynn said:
I'd like to flash this rom for the reasons you named but I am on the OF5 bootloader which is also unlocked since I used CF root to root it. Question : would you do a version of this rom including the OF5 bootloader or one that would use the bootloader already installed on the note?
Click to expand...
Click to collapse
Sorry I have no plans to build an OF5 bootloader version. If I'm not mistaken the bootloaders starting with OE1 cant be downgraded to previous versions. Hence making it pointless to build an OF5 version. Correct me if I'm wrong.
xyojimbox said:
Failed for me....
Edit i dont kow why the pic is sideways
Click to expand...
Click to collapse
.
whiteyman24 said:
Failed for me as well
Click to expand...
Click to collapse
If it failed then you're on a newer bootloader than OB7. This package was made specifically for those of us who waited and didn't update our OB7 bootloaders. Any newer bootloader will most likely fail. In that case you might as well odin the official OG5 rom tar.
flyhighx said:
To the guys it failed for:
were you coming off of an OB7 bootloader or something else? I'm guessing some bootloader other OB7.
Click to expand...
Click to collapse
Exactly.
kbrn said:
I flashed this last night when you first posted it in your Hybrid X thread, I was on OB7 running 2.3
I Odined all the way back to NK2 then flashed OB7 again, then this one, I flashed TWRP and Freeza's Kernel then installed Super SU from playstore and I'm not having any issues whatsoever, it runs very smooth (seems like they did a good job with this update)
I'm patiently waiting for you to make a new OG5 Hybrid X rom, I didn't want to flash Freeza's rom cause I've noticed there's a few bugs and issues.
And since it's stockish I see no point of doing so until there's new OG5 roms.
Thank You Sir!! :good::good:
Click to expand...
Click to collapse
Thats exactly how you do it. Thanks for sharing your feedback.
tx_dbs_tx said:
Sorry I have no plans to build an OF5 bootloader version. If I'm not mistaken the bootloaders starting with OE1 cant be downgraded to previous versions. Hence making it pointless to build an OF5 version. Correct me if I'm wrong.
.
If it failed then you're on a newer bootloader than OB7. This package was made specifically for those of us who waited and didn't update our OB7 bootloaders. Any newer bootloader will most likely fail. In that case you might as well odin the official OG5 rom tar.
Exactly.
Thats exactly how you do it. Thanks for sharing your feedback.
Click to expand...
Click to collapse
I am pretty sure I'm on ob7 bootloader cause I just flashed the of5 baseband I didn't take Ota and didn't mess with oe1 either....
tx_dbs_tx said:
Sorry I have no plans to build an OF5 bootloader version. If I'm not mistaken the bootloaders starting with OE1 cant be downgraded to previous versions. Hence making it pointless to build an OF5 version. Correct me if I'm wrong.
.
If it failed then you're on a newer bootloader than OB7. This package was made specifically for those of us who waited and didn't update our OB7 bootloaders. Any newer bootloader will most likely fail. In that case you might as well odin the official OG5 rom tar.
Exactly.
Thats exactly how you do it. Thanks for sharing your feedback.
Click to expand...
Click to collapse
If you mean the bootloader is locked on OF5 I don't see how it could be since I rooted OF5 with CF Root. I think it's not possible to do that if the bootloader is locked
twynn said:
If you mean the bootloader is locked on OF5 I don't see how it could be since I rooted OF5 with CF Root. I think it's not possible to do that if the bootloader is locked
Click to expand...
Click to collapse
It doesn't matter if bootloader is locked I believe. You can still root but you can't downgrade with any tar if bootloader is locked.
I thought sprint never locked the bootloader?
Hey everyone,
I've been curious about upgrading my rooted Note 4 from Lollipop 5.0.1 to a custom rom in 5.1.1, but I don't want to take a risk and brick my phone because I didn't know what I was doing. I'm not sure what steps to get to 5.1.1 and I know for a fact that if I attempt to install a 5.1.1 rom onto a 5.0.1, I am sure that I'll run into some issues.
Can anyone assist me in getting to 5.1.1? I'm not too sure of the terminology, all I know is that I'm on an OB7.
GreenFire999 said:
Hey everyone,
I've been curious about upgrading my rooted Note 4 from Lollipop 5.0.1 to a custom rom in 5.1.1, but I don't want to take a risk and brick my phone because I didn't know what I was doing. I'm not sure what steps to get to 5.1.1 and I know for a fact that if I attempt to install a 5.1.1 rom onto a 5.0.1, I am sure that I'll run into some issues.
Can anyone assist me in getting to 5.1.1? I'm not too sure of the terminology, all I know is that I'm on an OB7.
Click to expand...
Click to collapse
Id download the latest noterized (from Android Development) and put that zip on your sd card.
Go to recovery and make a backup.
While in recovery go to wipe, advanced and wipe everything x3 except for Micro SD
Then go to install and flash the noterized zip file.
An Unlocked bootloader is such a terrible thing to waste.
If you dont like it, all you have to do is repeat the wiping procedures in recovery and restore backup.
Or beforehand, if you run into some bumps, use the search feature while in that thread to see if any problems youre running into have already been asked and answered.
Glad you brought that up, i meant to mention that also @ the loss of xposed on 5.1.1
You have a phone that some would rather have than one they have if the bootloader is OB7. If that is the last full update you took, it should be OB7.
If Xposed framework and modules or staying on an unlocked bootloader that allows downgrade to KitKat isn't your thing, the full update to OG5 would be OK to flash to reactivation locked bootloader. (If true, skip next paragraph)
If keeping the OB7 bootloader, there are two recommended methods to update to OG5 while retaining OB7 bootloader. One is to flash the OG5 modem then flash a OG5 ROM. See freeza ROM OP in development for his modem, kernel and ROMs for OG5. The second method is to Odin the OB7 to OG5 tar ball by tx_dbs_tx in development. Follow the OPs for instructions.
There's a guide if you just want to upgrade and root OG5. If it's a custom OG5 ROM you're looking for, you can just do the Odin flash OF5 stock tar and custom recovery. In recovery, flash a pre-rooted OG5 ROM. I'd suggest a clean install with either method.
http://forum.xda-developers.com/showpost.php?p=62241991&postcount=56
Edit: one last comment. If you do want Xposed, it's not yet available for TW 5.1.1
Sent from my SM-N910P using Tapatalk
---------- Post added at 12:22 AM ---------- Previous post was at 12:16 AM ----------
xxSTARBUCKSxx said:
Id download the latest noterized (from Android Development) and put that zip on your sd card.
Go to recovery and make a backup.
While in recovery go to wipe, advanced and wipe everything x3 except for Micro SD
Then go to install and flash the noterized zip file.
An Unlocked bootloader is such a terrible thing to waste.
If you dont like it, all you have to do is repeat the wiping procedures in recovery and restore backup.
Or beforehand, if you run into some bumps, use the search feature while in that thread to see if any problems youre running into have already been asked and answered.
Click to expand...
Click to collapse
Good advice. Posted while I was thinking somewhat on the same point of view regarding OB7.
Sent from my SM-N910P using Tapatalk
So I'm guessing once when I upgrade to OG5 I'm taking away the unlocked bootloader feature? What is OG5 technically doing to the Note 4?
GreenFire999 said:
So I'm guessing once when I upgrade to OG5 I'm taking away the unlocked bootloader feature? What is OG5 technically doing to the Note 4?
Click to expand...
Click to collapse
Reactivation lock is a theft preventative mandate. If you set it, a password is required to overwrite your locked device and account. A would be thief wouldn't be able to unlock it or flash it to become the new owner. He would brick it trying. Am I wrong? I still haven't adopted the new bootloader to see any of this first hand.
The lesser security bootloaders are blocked to Odin. Updating means you can't go back to OB7 or KitKat complete tars. Noterized can be flashed because it doesn't attempt to make your device fully compatible with OB7. But that's not making an OG5 reactivation bootloader compatible with OB7 ROMs to freely flash at will. Semi bricking occurs when users try to flash full tars or go back to KitKat. Some even make the mistake of thinking going to Noterized frees them to flash other ROMs and tars that they shouldn't. Despite some claims of success, no history of a proven method exists outside of wasted time and confusion and bricks some users couldn't figure out even with help given.
I haven't been on a reactivation bootloader but going by claims of others and reading, it appears to be something new each update. OE1 didn't get a tar so users that rooted were stuck until OF5 official tar was released. When OG5 came out, some posted OF5 backups were not flashing. OG5 also blocks root by the traditional CFAutoRoot used in prior updates for KitKat and Lollipop. It takes the exploit of kernel plus SuperSU zip to root OG5.
All this has brought the added wait until development catches up concept to update prior to taking something like an OTA if you value root. And some have reported rooting has even defeated the ability to take OTA updates as well. Add to the the latest claim that the stock OG5 kernel is required in order to Odin a fresh OG5 tar over rooted OG5 means you have to be up on current events to avoid boot loops on OG5.
No Xposed on TW 5.1.1 means I'm staying away a little longer.
Got all that? Some of it is just theory. The guide I referenced earlier also had some more advice for OG5. I believe it's as short but exhaustive as possible in a single post. It's important for newcomers to make informed decisions. Best wishes on making the right one for you. Personally, I'm on OB7 deodexed for Xposed Lollipop and Wi-Fi Calling. I chose to stay with lollipop because Wi-Fi Calling is not very good on KitKat. Otherwise, KitKat is very good but development is following the recent updates.
Sent from my SM-N910P using Tapatalk
samep said:
Reactivation lock is a theft preventative mandate. If you set it, a password is required to overwrite your locked device and account. A would be thief wouldn't be able to unlock it or flash it to become the new owner. He would brick it trying. Am I wrong? I still haven't adopted the new bootloader to see any of this first hand.
The lesser security bootloaders are blocked to Odin. Updating means you can't go back to OB7 or KitKat complete tars. Noterized can be flashed because it doesn't attempt to make your device fully compatible with OB7. But that's not making an OG5 reactivation bootloader compatible with OB7 ROMs to freely flash at will. Semi bricking occurs when users try to flash full tars or go back to KitKat. Some even make the mistake of thinking going to Noterized frees them to flash other ROMs and tars that they shouldn't. Despite some claims of success, no history of a proven method exists outside of wasted time and confusion and bricks some users couldn't figure out even with help given.
I haven't been on a reactivation bootloader but going by claims of others and reading, it appears to be something new each update. OE1 didn't get a tar so users that rooted were stuck until OF5 official tar was released. When OG5 came out, some posted OF5 backups were not flashing. OG5 also blocks root by the traditional CFAutoRoot used in prior updates for KitKat and Lollipop. It takes the exploit of kernel plus SuperSU zip to root OG5.
All this has brought the added wait until development catches up concept to update prior to taking something like an OTA if you value root. And some have reported rooting has even defeated the ability to take OTA updates as well. Add to the the latest claim that the stock OG5 kernel is required in order to Odin a fresh OG5 tar over rooted OG5 means you have to be up on current events to avoid boot loops on OG5.
No Xposed on TW 5.1.1 means I'm staying away a little longer.
Got all that? Some of it is just theory. The guide I referenced earlier also had some more advice for OG5. I believe it's as short but exhaustive as possible in a single post. It's important for newcomers to make informed decisions. Best wishes on making the right one for you. Personally, I'm on OB7 deodexed for Xposed Lollipop. I chose to stay with lollipop because it's not very good on KitKat. Otherwise, KitKat is very good but development is following the recent updates.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you for the great description. I think I will stick with OB7 a little longer until I find a better reason to change to OG5. Sounds like it would be more of a hassle trying to troubleshoot on OG5 if I do screw something up. I might just go down your route and pick up Xposed to see where that takes me.
GreenFire999 said:
Thank you for the great description. I think I will stick with OB7 a little longer until I find a better reason to change to OG5. Sounds like it would be more of a hassle trying to troubleshoot on OG5 if I do screw something up. I might just go down your route and pick up Xposed to see where that takes me.
Click to expand...
Click to collapse
For TW Lollipop, you'll need a deodexed ROM for Xposed framework.
Stable using official alpha 3 v4
xposed-v65-sdk21-arm-arter97-V5-krait.ziphttp://forum.xda-developers.com/show...20&postcount=1
arter97-V6 for Xposed-v71 is available but I haven't tried it. There are reports of boot loops on various devices; IDK if anyone else has had success with this phone yet? I'd suggest what's stable until you know otherwise.
Install Xposed Installer as sideload. (Install browsing to it with a root browser and tap file, selecting install.) Flash the arter zip in recovery. Initial boot after flash and the framework should be installed and ready for adding modules. Reboot to apply modules.
Sent from my SM-N910P using Tapatalk
Hi all.
Two weeks ago I got this device (sgh i747) was rooted and was stock 4.1.1. I installed cwm and made A backup of stock room. And flash AOKP custom kitkat rom. Now I want to downgrade back to stock. or if I cannot downgrade please suggest me a stable lollypop rom.
Things I have!
1:- rooted cwm installed (sgh i747)
Backup of stock rom 4.1.1
Please help .
Thanks
mango man said:
Hi all.
Two weeks ago I got this device (sgh i747) was rooted and was stock 4.1.1. I installed cwm and made A backup of stock room. And flash AOKP custom kitkat rom. Now I want to downgrade back to stock. or if I cannot downgrade please suggest me a stable lollypop rom.
Things I have!
1:- rooted cwm installed (sgh i747)
Backup of stock rom 4.1.1
Please help .
Thanks
Click to expand...
Click to collapse
If you are still on the original bootloader and modem you should be able to revert to stock 4.1.1 by simply restoring the backup from your recovery. Before you attempt to do so verify that you are indeed on the 4.1.1 bootloader. This can be done with the Phone Info *Samsung* app by VndNguyen (?sp) from the playstore or by a couple of terminal emulator commands:
Code:
getprop ro.bootloader
getprop | grep version.baseband
If you do not already have terminal emulator installed, it may have come with the ROM, you can get it from the Playstore. It may also be a part of CWM recovery, it is part of TWRP I know for sure.
If it turns out you are on a newer bootloader and modem then go with a stock ROM that matches the bootloader and modem on the phone. To run a lollypop rom you will need to be on at least the NE4 bootloader and modem.
Thanks for a very helpful reply. I m going to follow your instructions. Will soon replay. Thanks again.
dawgdoc said:
If you are still on the original bootloader and modem you should be able to revert to stock 4.1.1 by simply restoring the backup from your recovery. Before you attempt to do so verify that you are indeed on the 4.1.1 bootloader. This can be done with the Phone Info *Samsung* app by VndNguyen (?sp) from the playstore or by a couple of terminal emulator commands:
Code:
getprop ro.bootloader
getprop | grep version.baseband
If you do not already have terminal emulator installed, it may have come with the ROM, you can get it from the Playstore. It may also be a part of CWM recovery, it is part of TWRP I know for sure.
If it turns out you are on a newer bootloader and modem then go with a stock ROM that matches the bootloader and modem on the phone. To run a lollypop rom you will need to be on at least the NE4 bootloader and modem.
Click to expand...
Click to collapse
Okay got Samsung phone info app.
Boot loader version -------I747UCDLK3
Baseband version -----I747UCDLK3
And please explain LATEST NE4 BOOT LOADER.
Thanks
You are currently running the LK3 bootloader and modem. If I am not mistaken that's a pretty old one (original?). You will have to update to NE4 or newer firmware before you can flash any of the newer roms. They will not boot in the older ones.
Your firmware is actually the only one available for download so I recommend flashing it via Odin and factory resetting. Then update using the Software Update option in Settings > About Device.
You can download your LK3 firmware here: http://www.sammobile.com/firmwares/database/SGH-I747/
You may have to run Software update several times to fully update.
That is probably the safest and easiest course you can take.
After that, flash the latest custom recovery of your choice, then flash the rom you want.
Sent from my SGH-T999 using Tapatalk
---------- Post added at 12:17 PM ---------- Previous post was at 12:13 PM ----------
BTW, after flashing the LK3 firmware, you might want to consider using the free Sim unlock method. (Should be pretty easy to find).
Once you update past 4.3 you can no longer use it. It will allow the device to be used on other carriers networks, which can be beneficial if you ever want to sell it or switch carriers.
Sent from my SGH-T999 using Tapatalk
What DocHoliday77 suggests is probably the safest method to get what you want. After each update the system will force you to wait 24 hours before you can make the next update. That would be three days to get to NE4, the first 4.4.2 release by AT&T, which you need to run lollipop ROMs. If you want to update to the current release (NJ2) that would be two additional days.
You can shortcut the required waiting period by manually advancing the system date after each update.
In addition to not allowing you to use the free unlock, once you take the 4.3 bootloader it prevents you from downgrading bootloaders. Newer bootloaders do the same, downgrading will be a thing of the past. (I never took the official 4.3 bootloader until the stagefright scare came along and I went from my older custom ROM to a new release.)
dawgdoc said:
What DocHoliday77 suggests is probably the safest method to get what you want. After each update the system will force you to wait 24 hours before you can make the next update. That would be three days to get to NE4, the first 4.4.2 release by AT&T, which you need to run lollipop ROMs. If you want to update to the current release (NJ2) that would be two additional days.
You can shortcut the required waiting period by manually advancing the system date after each update.
In addition to not allowing you to use the free unlock, once you take the 4.3 bootloader it prevents you from downgrading bootloaders. Newer bootloaders do the same, downgrading will be a thing of the past. (I never took the official 4.3 bootloader until the stagefright scare came along and I went from my older custom ROM to a new release.)
Click to expand...
Click to collapse
1:- Okay I fully understood what I have to do to flash lolly pop . But confused a little bit . If I have original boodloader than it should be easier to restore my stock 4.1.1 . Backup (still not clear) .
2:- I am out of USA. The device in unlocked. I am using ZONG sim on it. So the question is can I still update the device via OTA.
Thanks
mango man said:
1:- Okay I fully understood what I have to do to flash lolly pop . But confused a little bit . If I have original boodloader than it should be easier to restore my stock 4.1.1 . Backup (still not clear) .
2:- I am out of USA. The device in unlocked. I am using ZONG sim on it. So the question is can I still update the device via OTA.
Thanks
Click to expand...
Click to collapse
When you say original bootloader I don't know which you have. My i747 came with 4.1.1 but before I could get it out of the clerk's hands they had taken the OTA to change it from DLK3/4.1.1 bootloader and stock rom to MG2/4.1.2 bootloader and stock rom. Even more confusing I have read reviews that state the SGS3 was originally released with android 4.0.4.
If your original bootloader was older than 4.3 (MJB) AND you have never upgraded to MJB or newer, then you can safely return to stock 4.1.1.
To get OTAs you need to be on the stock ROM, at least you do in the USA. I don't know if that holds true elsewhere.
I can confirm the S3 was originally shipped with 4.0.4! We were updated pretty quickly though.
As for the OTA'S, you do have to be full stock, not rooted. But you also have to be on AT&T network.
I don't know how far back the OTA'S are hosted around here, but enewman17 has several threads that provide the more recent ones. Hopefully someone will have the older ones. If I am not mistaken, you will have to update incrementally once you reach 4.3. (it's probably safe to jump straight to a 4.3 build if you can find the right firmware for it. But don't hold me to that as I am not 100% certain.
I'll look to see if I can find something you can use too.
Sent from my SGH-T999 using Tapatalk
dawgdoc said:
When you say original bootloader I don't know which you have. My i747 came with 4.1.1 but before I could get it out of the clerk's hands they had taken the OTA to change it from DLK3/4.1.1 bootloader and stock rom to MG2/4.1.2 bootloader and stock rom. Even more confusing I have read reviews that state the SGS3 was originally released with android 4.0.4.
If your original bootloader was older than 4.3 (MJB) AND you have never upgraded to MJB or newer, then you can safely return to stock 4.1.1.
To get OTAs you need to be on the stock ROM, at least you do in the USA. I don't know if that holds true elsewhere.
Click to expand...
Click to collapse
DocHoliday77 said:
I can confirm the S3 was originally shipped with 4.0.4! We were updated pretty quickly though.
As for the OTA'S, you do have to be full stock, not rooted. But you also have to be on AT&T network.
I don't know how far back the OTA'S are hosted around here, but enewman17 has several threads that provide the more recent ones. Hopefully someone will have the older ones. If I am not mistaken, you will have to update incrementally once you reach 4.3. (it's probably safe to jump straight to a 4.3 build if you can find the right firmware for it. But don't hold me to that as I am not 100% certain.
I'll look to see if I can find something you can use too.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thanks men for quick response.
now I m fully confused. Don't know what to do. because I don't want to stuck on this battery enemy rom. (Aokp kitkat. Custom rom )
I am not clear about boootader version (PHONE INFO SAMSUNG APP SAYS ITS i747ucdlk3 ) but I know when got this thing. It was android 4.1.1 . Which I have back a backup. As per I am out of att network and I can't get OTA,s so I don't need to revert to 4.1.1 backup. I think I have to find out 4.3. For my device. So kindly please inform me if some one knows about . Iwill be very thankful to u people.
Again thanks
DocHoliday77 said:
I can confirm the S3 was originally shipped with 4.0.4! We were updated pretty quickly though.
As for the OTA'S, you do have to be full stock, not rooted. But you also have to be on AT&T network.
I don't know how far back the OTA'S are hosted around here, but enewman17 has several threads that provide the more recent ones. Hopefully someone will have the older ones. If I am not mistaken, you will have to update incrementally once you reach 4.3. (it's probably safe to jump straight to a 4.3 build if you can find the right firmware for it. But don't hold me to that as I am not 100% certain.
I'll look to see if I can find something you can use too.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I got this while searching online. Please tell me if it is helpful for.me.
http://androidromupdate.com/att-samsung-galaxy-s3-sgh-i747-odin-stock-firmware/
Never been to that site, but it looks OK to me. Nice find in fact! All the usual firmware sites stopped getting the AT&T firmware a while back.
Anyway, just to clarify, LK3 is 4.1.1. UCDLK3 is just the build number.
If you want to get fully updated, I suggest Odin flashing the MJB (4.3) firmware. Then flash each of the OTA's until you are updated to where you want to be. (I would fully update, but that'll be up to you.) The OTA'S are intended to be flashed from stock recovery, but there is another option if you want to try it. Mobile Odin is an app by chainfire. It does require you to be rooted, but it will flash the OTA. Read his thread here on xda to learn more. It's one of my favorite apps tbh! Once you learn how to use it it makes flashing quite easy.
So my recommendation would be this:
Flash MJB with Odin.
Root using Towelroot (easiest root ever)
Install Mobile Odin and flash the OTA'S.
I hope that clears things up a bit!
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Never been to that site, but it looks OK to me. Nice find in fact! All the usual firmware sites stopped getting the AT&T firmware a while back.
Anyway, just to clarify, LK3 is 4.1.1. UCDLK3 is just the build number.
If you want to get fully updated, I suggest Odin flashing the MJB (4.3) firmware. Then flash each of the OTA's until you are updated to where you want to be. (I would fully update, but that'll be up to you.) The OTA'S are intended to be flashed from stock recovery, but there is another option if you want to try it. Mobile Odin is an app by chainfire. It does require you to be rooted, but it will flash the OTA. Read his thread here on xda to learn more. It's one of my favorite apps tbh! Once you learn how to use it it makes flashing quite easy.
So my recommendation would be this:
Flash MJB with Odin.
Root using Towelroot (easiest root ever)
Install Mobile Odin and flash the OTA'S.
I hope that clears things up a bit!
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yup! I think it is. Will try . Thanks
mango man said:
Yup! I think it is. Will try . Thanks
Click to expand...
Click to collapse
Update:- I am stock 4.1.1 now . I restored the device from custom AOKP kit kat rom using the stock 4.1.1 backup which I have made via CWM recovery. The device is running perfectly.
*****tried to run OTA but it says ur. Device in up to date . Means I cant get any OTA up date . So the question is can I get any custom lollypop rom using this older bootloader. ? (LK3)
DocHoliday77 said:
Never been to that site, but it looks OK to me. Nice find in fact! All the usual firmware sites stopped getting the AT&T firmware a while back.
Anyway, just to clarify, LK3 is 4.1.1. UCDLK3 is just the build number.
If you want to get fully updated, I suggest Odin flashing the MJB (4.3) firmware. Then flash each of the OTA's until you are updated to where you want to be. (I would fully update, but that'll be up to you.) The OTA'S are intended to be flashed from stock recovery, but there is another option if you want to try it. Mobile Odin is an app by chainfire. It does require you to be rooted, but it will flash the OTA. Read his thread here on xda to learn more. It's one of my favorite apps tbh! Once you learn how to use it it makes flashing quite easy.
So my recommendation would be this:
Flash MJB with Odin.
Root using Towelroot (easiest root ever)
Install Mobile Odin and flash the OTA'S.
I hope that clears things up a bit!
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Update:- I am stock 4.1.1 now . I restored the device from custom AOKP kit kat rom using the stock 4.1.1 backup which I have made via CWM recovery. The device is running perfectly.
*****tried to run OTA but it says ur. Device in up to date . Means I cant get any OTA up date . So the question is can I get any custom lollypop rom using this older bootloader. ? (LK3)
mango man said:
Update:- I am stock 4.1.1 now . I restored the device from custom AOKP kit kat rom using the stock 4.1.1 backup which I have made via CWM recovery. The device is running perfectly.
*****tried to run OTA but it says ur. Device in up to date . Means I cant get any OTA up date . So the question is can I get any custom lollypop rom using this older bootloader. ? (LK3)
Click to expand...
Click to collapse
To be able to run a lollipop rom you will need to update bootloader and modem. Update them together, this is important once you reach the 4.4.2 level of bootloader and modem that you will need to run lollipop roms. Once you reach 4.4.2 you will brick your phone if the bootloader and modem versions are not the same.
Before starting to flash any of the files you need to get you up and running on lollipop, I strongly suggest you download all you need from start to finish. Store the files you will need in the upgrade process either on an external sdcard or on the root of your internal sdcard. I haven't used CWM Recovery on my SGS3 since shortly after rooting it, I have been using TWRP since then, and I don't recall all of the capabilities of CWM recovery. If the CWM version you have will not let you flash from an external sdcard you will need to store the files you will use on the root of the internal card to be able to flash them. It will be easier to do this before you start, unless you are comfortable with pushing files from a computer using adb.
BEFORE DOING ANYTHING I AM SUGGESTING read enough that you thoroughly understand what I am saying. After reading, ask questions for clarification. Be sure you have no doubts.
Decide if you intend to install a rom along with the bootloader and modem at each upgrade; or if you are going to install updating only bootloader and modem until you get them to them point that you can run a lollipop ROM. Since you said you can not do OTA updates, either way will work. Whichever you decide, you can not skip directly to the bootloader and modem you need for lollipop.
If you are installing bootloader and modems without the rom:
From the stock 4.1.1 rom and bootloader you can go straight to 4.3 bootloader and modem, skipping the 4.1.2 (MG2) version. I have personally done this with no ill consequences. After 4.3, install the first bootloader and modem version for 4.4.2, that is NE4. Lollipop will run with the NE4 bootloader. As DocHoliday stated, you can go on the the current bootloader and modem. After NE4 is NJ1. After NJ1 you come to the current bootloader and modem, which is NJ2
If you plan to install the full ROM at each step.
The page you linked to should work if all of the downloads are available. Go from 4.1.1 to 4.3 to 4.4.2 (NE4). If you want the newer versions (NJ1 or NJ2) do them in sequence, do not skip any that are mentioned. Read the instructions on your linked page carefully. If you want NJ1 and then NJ2 they can be found in threads by enewman17, as can NE4 and maybe 4.3. I didn't provide the links so that you will hopefully read the pages carefully after searching and before downloading. Be sure you understand what you are downloading to flash and how it should be used.
dawgdoc said:
To be able to run a lollipop rom you will need to update bootloader and modem. Update them together, this is important once you reach the 4.4.2 level of bootloader and modem that you will need to run lollipop roms. Once you reach 4.4.2 you will brick your phone if the bootloader and modem versions are not the same.
Before starting to flash any of the files you need to get you up and running on lollipop, I strongly suggest you download all you need from start to finish. Store the files you will need in the upgrade process either on an external sdcard or on the root of your internal sdcard. I haven't used CWM Recovery on my SGS3 since shortly after rooting it, I have been using TWRP since then, and I don't recall all of the capabilities of CWM recovery. If the CWM version you have will not let you flash from an external sdcard you will need to store the files you will use on the root of the internal card to be able to flash them. It will be easier to do this before you start, unless you are comfortable with pushing files from a computer using adb.
BEFORE DOING ANYTHING I AM SUGGESTING read enough that you thoroughly understand what I am saying. After reading, ask questions for clarification. Be sure you have no doubts.
Decide if you intend to install a rom along with the bootloader and modem at each upgrade; or if you are going to install updating only bootloader and modem until you get them to them point that you can run a lollipop ROM. Since you said you can not do OTA updates, either way will work. Whichever you decide, you can not skip directly to the bootloader and modem you need for lollipop.
If you are installing bootloader and modems without the rom:
From the stock 4.1.1 rom and bootloader you can go straight to 4.3 bootloader and modem, skipping the 4.1.2 (MG2) version. I have personally done this with no ill consequences. After 4.3, install the first bootloader and modem version for 4.4.2, that is NE4. Lollipop will run with the NE4 bootloader. As DocHoliday stated, you can go on the the current bootloader and modem. After NE4 is NJ1. After NJ1 you come to the current bootloader and modem, which is NJ2
If you plan to install the full ROM at each step.
The page you linked to should work if all of the downloads are available. Go from 4.1.1 to 4.3 to 4.4.2 (NE4). If you want the newer versions (NJ1 or NJ2) do them in sequence, do not skip any that are mentioned. Read the instructions on your linked page carefully. If you want NJ1 and then NJ2 they can be found in threads by enewman17, as can NE4 and maybe 4.3. I didn't provide the links so that you will hopefully read the pages carefully after searching and before downloading. Be sure you understand what you are downloading to flash and how it should be used.
Click to expand...
Click to collapse
Thanks **** I need to be extra careful before taking any step. I am going to collect all relesed OTA,s. By now I onky need the links for ota. Thanks
Flash MJB and NE4 from the site you linked to above. Then use enewman17's thread for the NJ1 and NJ2 updates. He also has NE4, in case you want to get all the OTA'S from him. (Downloads will be a lot faster) They've all been used many times. I'll try to post a direct link in a few...
Sent from my SGH-T999 using Tapatalk
---------- Post added at 09:48 PM ---------- Previous post was at 09:39 PM ----------
NE4
http://forum.xda-developers.com/gal...are-update-t2808654/post53984772#post53984772
NJ1
http://forum.xda-developers.com/showthread.php?t=2941792
NJ1 and NJ2
http://forum.xda-developers.com/showthread.php?t=2985006
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Flash MJB and NE4 from the site you linked to above. Then use enewman17's thread for the NJ1 and NJ2 updates. He also has NE4, in case you want to get all the OTA'S from him. (Downloads will be a lot faster) They've all been used many times. I'll try to post a direct link in a few...
Sent from my SGH-T999 using Tapatalk
---------- Post added at 09:48 PM ---------- Previous post was at 09:39 PM ----------
NE4
http://forum.xda-developers.com/gal...are-update-t2808654/post53984772#post53984772
NJ1
http://forum.xda-developers.com/showthread.php?t=2941792
NJ1 and NJ2
http://forum.xda-developers.com/showthread.php?t=2985006
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I got this site having all ota, s . And is linked to the enewman17.
www.androidayos.com/samsung-galaxy-s3-stock-firmware-2/
Lol, I guess they thought they had to provide it somehow! It's a shame they didn't at least acknowledge enewman17 in their article there, but at least they direct linked to his thread.
Anyway, good luck! And if you have any other questions come up, let us know.
Sent from my SGH-T999 using Tapatalk
A month ago I needed to get an extra Note 4 I had back to 5.0.1, it was on 5.1.1. I flashed it in Odin everything worked perfectly, rooted it, phone works great. A bout 2 weeks ago, I helped someone out that needed a phone temporarily, so I let them borrow it being the phone is unlocked. The person reset the phone and updated it before giving it back to me, they thought they were being nice because I let them borrow the phone. I wasn't mad but the unlock went away, no big deal, but now I can't get it off 5.1.1, and back to 5.0.1. I tried 4.4.4 and 5.0.1 a few times now Odin keeps giving me a fail. Here is what I have done:
-Tried both Odin 10.6 & 10.7 (use as admin)
-Tried 4.4.4 and 5.0.1
-There is no Google account on the phone
-Reactivation lock is off
I had flashed this phone and 2 other same model without any issues. Like I stated I have done this a few times on the SM-N910P, not to mention I'm not an expert but have been rooting and using Odin for a few years. Any help would be greatly appreciated, and I will answer any questions as far as what I did. I'm not looking for the fix to be spoon fed to me, but maybe some other options I should look at.
"long time listener, first time caller"
If it's just a OB7 ROM that you'd like to return to, just restore either the backup + freeza Beastmode 1.0 found in general --or-- Odin the full stock tar that the bootloader is currently on + OB7 ROM zip + Beastmode kernel.
What you say about going from 5.1 back to 5.0 happening and not happening now is possible if the 5.1 update was through Odin using the tar ball OB7 to OG5 by tx_dbs_tx that retained the OB7 bootloader. Once the bootloader is updated beyond OB7, there's not a known replicated and confirmed way that I'm aware of to downgrade as you're trying to do. The old tutorials out there mostly fail to mention CF Auto Root shouldn't be used for lollipop or downgrading to KitKat or older bootloaders once updated beyond OB7 shouldn't be attempted.
The reactivation locked bootloader was intended to prevent downgrade to lower security by design.
You're not limited to just to Beastmode kernel. Any kernel with the root exploit that one has. The kernel should allow the boot but in extreme exceptions you may have to also factory reset and install clean and
_______only if needed... Ask if you have questions... Try minimum suggested effort first.
You may even have to use Philz CWM recovery for Note 4 to factory reset if you've crashed Odin or TWRP to the point it won't flash and boot a full tar or flash a ROM zip. Flashing the older tars over newer reactivation bootloader has done that some that kept trying to find a way around it.
Be careful. Wrong recovery can hose the touch screen software and have your touch way off but can rectified. Forcing the issue with Odin, outdated tutorials, and unsupported methods could soft brick or hard brick your phone. Use the compatible recoveries, latest Odin and minimum intervention to avoid that.
Sent from my SM-N910P using Tapatalk
Thanks for the quick reply
samep said:
If it's just a OB7 ROM that you'd like to return to, just restore either the backup + freeza Beastmode 1.0 found in general --or-- Odin the full stock tar that the bootloader is currently on + OB7 ROM zip + Beastmode kernel.
What you say about going from 5.1 back to 5.0 happening and not happening now is possible if the 5.1 update was through Odin using the tar ball OB7 to OG5 by tx_dbs_tx that retained the OB7 bootloader. Once the bootloader is updated beyond OB7, there's not a known replicated and confirmed way that I'm aware of to downgrade as you're trying to do. The old tutorials out there mostly fail to mention CF Auto Root shouldn't be used for lollipop or downgrading to KitKat or older bootloaders once updated beyond OB7.
The reactivation locked bootloader was intended to prevent downgrade to lower security by design.
You're not limited to just to Beastmode kernel. Any kernel with the root exploit that one has. The kernel should allow the boot but in extreme exceptions you may have to also factory reset and install clean and
_______only if needed... Ask if you have questions... Try minimum suggested effort first.
You may even have to use Philz CWM recovery for Note 4 to factory reset if you've crashed Odin or TWRP to the point it won't flash and boot a full tar or flash a ROM zip. Flashing the older tars over newer reactivation bootloader has done that some that kept trying to find a way around it.
Be careful. Wrong recovery can hose the touch screen software and have your touch way off but can rectified. Forcing the issue with Odin, outdated tutorials, and unsupported methods could soft brick or hard brick your phone. Use the compatible recoveries, latest Odin and minimum intervention to avoid that.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Yes, I need to confirm the OB7 bootloader. I'm starting to think it has to do with the bootloader, I will report back in 24-48 hours after I have tried your suggestions. I'm lost as to what happened
Alex215 said:
Yes, I need to confirm the OB7 bootloader. I'm starting to think it has to do with the bootloader, I will report back in 24-48 hours after I have tried your suggestions. I'm lost as to what happened
Click to expand...
Click to collapse
Do you recall the update it was updated to? OTA update and stock tar will upgrade the bootloader to that update version. Verify the current bootloader with galaxy tools or PhoneInfo for Samsung devices in Google Play.
If it doesn't boot to verify, you may have wiped the system. Try the backup or ROM zip plus kernel with exploit to find out.
To be clear, you shouldn't try to Odin that tar ball I mentioned once the bootloader was updated beyond OB7. It's only recommended for bootloader OB7 or older as a means to update to OG5 or compatible ROMs.
Sent from my SM-N910P using Tapatalk
samep said:
Do you recall the update it was updated to? OTA update and stock tar will upgrade the bootloader to that update version. Verify the current bootloader with galaxy tools or PhoneInfo for Samsung devices in Google Play.
If it doesn't boot to verify, you may have wiped the system. Try the backup or ROM zip plus kernel with exploit to find out.
To be clear, you shouldn't try to Odin that tar ball I mentioned once the bootloader was updated beyond OB7. It's only recommended for bootloader OB7 or older as a means to update to OG5 or compatible ROMs.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I left the phone at the shop and will be picking it up tomorrow to try to figure it out. I have a feeling it was updated beyond the OB7, I will use PhoneInfo to verify the current bootloader.
Bootloader version...
samep said:
Do you recall the update it was updated to? OTA update and stock tar will upgrade the bootloader to that update version. Verify the current bootloader with galaxy tools or PhoneInfo for Samsung devices in Google Play.
If it doesn't boot to verify, you may have wiped the system. Try the backup or ROM zip plus kernel with exploit to find out.
To be clear, you shouldn't try to Odin that tar ball I mentioned once the bootloader was updated beyond OB7. It's only recommended for bootloader OB7 or older as a means to update to OG5 or compatible ROMs.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
So I got a chance last night to look at the bootloader version and it is:
N910PVPU4COJ6
….with that being said there is no way to downgrade to 5.0.1. I think I'm out of luck, thanks for your help.
Alex215 said:
So I got a chance last night to look at the bootloader version and it is:
N910PVPU4COJ6
….with that being said there is no way to downgrade to 5.0.1. I think I'm out of luck, thanks for your help.
Click to expand...
Click to collapse
Do you have a lollipop TWRP backup? You could restore it and flash Beastmode kernel after that and it should boot.
Or flash any lollipop ROM plus the kernel. IDK, maybe you've done that already. Personally, l think the most recent updates: OJ6 and OK1 are the best we've gotten since lollipop.
Sent from my SM-N910P using Tapatalk
Thanks
samep said:
Do you have a lollipop TWRP backup? You could restore it and flash Beastmode kernel after that and it should boot.
Or flash any lollipop ROM plus the kernel. IDK, maybe you've done that already. Personally, l think the most recent updates: OJ6 and OK1 are the best we've gotten since lollipop.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
No, I need to go back to 5.0.1 for unlocking purposes. That's my whole dilemma...
Alex215 said:
No, I need to go back to 5.0.1 for unlocking purposes. That's my whole dilemma...
Click to expand...
Click to collapse
I just can't understand why it won't at least allow me to return to the stock firmware.
Alex215 said:
I just can't understand why it won't at least allow me to return to the stock firmware.
Click to expand...
Click to collapse
Are you trying to get your MSL? Or UICC unlock?
Alex215 said:
I just can't understand why it won't at least allow me to return to the stock firmware.
Click to expand...
Click to collapse
Are you Odin flashing OJ6 with verified md5 after wiping everything but extSdCard and preparing down? Use latest Odin with Odin defaults. And backup your media and downloads on internal memory before wiping it.
You run the risk of soft brick when trying to flash the older tar over the reactivation locked bootloader. Also, when you're in download mode, look for reactivation lock disabled or unlocked... Enabled would block full Odin tar or recovery ROM flash.
Sent from my SM-N910P using Tapatalk
samep said:
Are you Odin flashing OJ6 with verified md5 after wiping everything but extSdCard and preparing down? Use latest Odin with Odin defaults. And backup your media and downloads on internal memory before wiping it.
You run the risk of soft brick when trying to flash the older tar over the reactivation locked bootloader. Also, when you're in download mode, look for reactivation lock disabled or unlocked... Enabled would block full Odin tar or recovery ROM flash.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
reactivation lock is off, the current bootloader is OJ6. I need to get back to 5.0.1 for unlocking purposes. I just don't understand what is going on.
ianmb said:
Are you trying to get your MSL? Or UICC unlock?
Click to expand...
Click to collapse
MSL
Alex215 said:
reactivation lock is off, the current bootloader is OJ6. I need to get back to 5.0.1 for unlocking purposes. I just don't understand what is going on.
Click to expand...
Click to collapse
Presently, the only tars that will restore are OJ6 OK1. OK1 is on Sammobile now.
Sent from my SM-N910P using Tapatalk
---------- Post added at 10:33 AM ---------- Previous post was at 10:30 AM ----------
Alex215 said:
MSL
Click to expand...
Click to collapse
MSL doesn't change. If you had it before, it still works. If not, there is a galaxy tools version that still works. If your phone is paid in full, Sprint will release it in chat session.
Sent from my SM-N910P using Tapatalk
As the title says, just looking for a stock and rooted Marshmallow, I will go on and remove the stuff I don't want. I have not seen one or my google skills are failing...
Sent from my SM-N910V using Tapatalk
Or a quick way to go from CM 13 to rooted stock...I really don't want to have to go through the whole process....I will if that's the only way though...
Sent from my SM-N910V using Tapatalk
This might be it. Post in this thread and inquire before you do anything. You might need to flash and Unlock, again, but once you Unlock, you might be able to use it Unlocked/Rooted as-is. Again, though, inquire there.
http://forum.xda-developers.com/not...firmware-safe-upgrade-to-marshmallow-t3402727
cdrshm said:
Or a quick way to go from CM 13 to rooted stock...I really don't want to have to go through the whole process....I will if that's the only way though...
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Which CM13 version are you using? Have you upgraded the bootloader to MM yet? If you are using an older version of CM13 that was on the LP bootloader then you'll have to go through the unlocking process once more with the LP-MM hybrid firmware. If you have already done that and you have the MM bootloader then you can flash JasmineROM or PaulPizz as a close-to-stock ROM. Jasmine is probably the closest to stock.
shadeau said:
Which CM13 version are you using? Have you upgraded the bootloader to MM yet? If you are using an older version of CM13 that was on the LP bootloader then you'll have to go through the unlocking process once more with the LP-MM hybrid firmware. If you have already done that and you have the MM bootloader then you can flash JasmineROM or PaulPizz as a close-to-stock ROM. Jasmine is probably the closest to stock.
Click to expand...
Click to collapse
I did end up getting on Jasmine, i did the restore of the jasmine rom from TWRP and then flash the PartialFirmware_PatchedKernel and i am working now...
PF3 Firmware
cdrshm said:
I did end up getting on Jasmine, i did the restore of the jasmine rom from TWRP and then flash the PartialFirmware_PatchedKernel and i am working now...
Click to expand...
Click to collapse
I have a copy of PF3 firmware that's almost stock. It has busybox, deodexed, and zip-align. To root, you could flash su zip for system-less or just install su from playstore. It still has Knox and all bloat.
PF3 Firmware link