My N910p arrives with MM on PC1 and I flashed it to PD1, but it seems it reboot by itself a lot. I'm not sure it's the MM or the hardware. I used to have a N910T on KK which is very stable. I wonder if there is a way to downgrade from MM to KK or LP. TIA.
You can Odin stock tars that are Android 5.1 but no less. I believe that's no lower than OG5, so OG5 and up are good.
If you were running a custom kernel or stock ROM in marshmallow and factory reset, you may have had ItsOn in /carrier/ItsOn try to initiate the ItsOn bootstrapper setup. If you have an arm file as first entry in /data/dalvik that refers back to /carrier/ItsOn/...apk, that's likely the issue. Note: freeza's ROM won't do this because there's a script to prevent that now.
You could ensure ItsOn is removed (delete the arm file in dalvik-cache and ItsOn folder in /carrier) or go back to Lollipop 5.1
If you go beck to Lollipop, I'd suggest one of tx_dbs_tx Note 5 ports. Wipe everything but extSdCard, factory reset, Odin OK1 stock tar and follow the OP closely.
Sent from my SM-N910P using Tapatalk
samep said:
You can Odin stock tars that are Android 5.1 but no less. I believe that's no lower than OG5, so OG5 and up are good.
If you were running a custom kernel or stock ROM in marshmallow and factory reset, you may have had ItsOn in /carrier/ItsOn try to initiate the ItsOn bootstrapper setup. If you have an arm file as first entry in /data/dalvik that refers back to /carrier/ItsOn/...apk, that's likely the issue. Note: freeza's ROM won't do this because there's a script to prevent that now.
You could ensure ItsOn is removed (delete the arm file in dalvik-cache and ItsOn folder in /carrier) or go back to Lollipop 5.1
If you go beck to Lollipop, I'd suggest one of tx_dbs_tx Note 5 ports. Wipe everything but extSdCard, factory reset, Odin OK1 stock tar and follow the OP closely.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I believe you can go back to any version. I went back to KitKat a couple of times. The problem is every time you upgrade again you lose ram. I only have 2.7 available now. I want to know if there is a way to clear it?
You can change versions forward with OTA but to go back you have to Odin stock firmware. You can get any version here.
Note 4
SM-N910P
http://www.sammobile.com/firmwares/database/SM-N910P/
planb234 said:
I believe you can go back to any version. I went back to KitKat a couple of times. The problem is every time you upgrade again you lose ram. I only have 2.7 available now. I want to know if there is a way to clear it?
You can change versions forward with OTA but to go back you have to Odin stock firmware. You can get any version here.
Note 4
SM-N910P
http://www.sammobile.com/firmwares/database/SM-N910P/
Click to expand...
Click to collapse
Thanks for sharing. Mind telling the lastest version that you have been on before you go back to kk? I heard that once it pass a certain version then it can't go back.
planb234 said:
I believe you can go back to any version. I went back to KitKat a couple of times. The problem is every time you upgrade again you lose ram. I only have 2.7 available now. I want to know if there is a way to clear it?
You can change versions forward with OTA but to go back you have to Odin stock firmware. You can get any version here.
Note 4
SM-N910P
http://www.sammobile.com/firmwares/database/SM-N910P/
Click to expand...
Click to collapse
My RAM is the same. Haven't noticed if reserved RAM varies or if developers tweak this but I believe you're seeing reserved RAM deducted from total as shown here:
{
"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"
}
There is a way to go back to KitKat from Android 5.1 or 6.0 but not through Odin of full tar. But, if you're one of the ones that retained OB7 bootloader without flashing full tar updates, then it's also possible to Odin back to KitKat.
But once you update the bootloader via OTA, you'll see it in the update notes that downgrade of bootloader is no longer possible due to the increased security of newer bootloader. Odin would be the same but you wouldn't see the update notes.
Sent from my SM-N910P using Tapatalk
samep said:
There is a way to go back to KitKat from Android 5.1 or 6.0 but not through Odin of full tar.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Can you show the way?
shadowcliffs said:
Thanks for sharing. Mind telling the lastest version that you have been on before you go back to kk? I heard that once it pass a certain version then it can't go back.
Click to expand...
Click to collapse
The last time I went back was from bob7. I have not tried it from 6.0. If someone can tell me how to clear out the RAM I will test it out. I think the KitKat is by far the best version for the note excepting for how vulnerable it leaves you to the molesters.
---------- Post added at 09:25 AM ---------- Previous post was at 09:16 AM ----------
shadowcliffs said:
Thanks for sharing. Mind telling the lastest version that you have been on before you go back to kk? I heard that once it pass a certain version then it can't go back.
Click to expand...
Click to collapse
planb234 said:
The last time I went back was from bob7. I have not tried it from 6.0. If someone can tell me how to clear out the RAM I will test it out. I think the KitKat is by far the best version for the note excepting for how vulnerable it leaves you to the molesters.
Click to expand...
Click to collapse
Actually thinking about it, I took my S4 back from 5.1 to 4.1 last week. So I know for sure that you can do it if your still on 5. I asked Samsung support about it a while ago and he said yes but that was still during lollipop. According to Chainfire you can not take a bootloader back but Odin decides what version you will get anyways. So as long as you go back with a stock boot loader intact it will be fine.
---------- Post added at 09:47 AM ---------- Previous post was at 09:25 AM ----------
planb234 said:
The last time I went back was from bob7. I have not tried it from 6.0. If someone can tell me how to clear out the RAM I will test it out. I think the KitKat is by far the best version for the note excepting for how vulnerable it leaves you to the molesters.
---------- Post added at 09:25 AM ---------- Previous post was at 09:16 AM ----------
Actually thinking about it, I took my S4 back from 5.1 to 4.1 last week. So I know for sure that you can do it if your still on 5. I asked Samsung support about it a while ago and he said yes but that was still during lollipop. According to Chainfire you can not take a bootloader back but Odin decides what version you will get anyways. So as long as you go back with a stock boot loader intact it will be fine.
Click to expand...
Click to collapse
I also found out for sure you don"t want to change versions with any thing but stock firmware and odin. I accidentally (stupidly) had Kitkat and lollipop backed up in the same folder and tried restoring from 5 to 4 and cried for a couple of months trying to get it working again. After a lot of trying I was able to use my phone off one back up I had and using the Plasma kernel. I didn't enjoy my phone much until Samsung put out the COJ6. I'm guessing the issue I caused was in the bootloader and until there was a whole new version out there was nothing I could do. I noticed on my S4 and my Note 4 if you want to keep KitKat you have to get it off official status quickly. When they start up on KitKat Samsung pushes the update before you even get through set up and they will install the update with out your permission.
---------- Post added at 10:28 AM ---------- Previous post was at 09:47 AM ----------
samep said:
My RAM is the same. Haven't noticed if reserved RAM varies or if developers tweak this but I believe you're seeing reserved RAM deducted from total as shown here:
There is a way to go back to KitKat from Android 5.1 or 6.0 but not through Odin of full tar. But, if you're one of the ones that retained OB7 bootloader without flashing full tar updates, then it's also possible to Odin back to KitKat.
But once you update the bootloader via OTA, you'll see it in the update notes that downgrade of bootloader is no longer possible due to the increased security of newer bootloader. Odin would be the same but you wouldn't see the update notes.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you. That Ram thing helps. My Phone says 273 reserved also. I thought I was losin it each time. I took my phone back to KitKat using Odin twice. Both times from Lollipop. I got the update OTA once. Chainfire explains it well, as always. He said that you can not ever go back a version of boot-loader and there is no way to choose your bootloader. Odin decides what firmware it will run.
samep said:
My RAM is the same. Haven't noticed if reserved RAM varies or if developers tweak this but I believe you're seeing reserved RAM deducted from total as shown here:
There is a way to go back to KitKat from Android 5.1 or 6.0 but not through Odin of full tar. But, if you're one of the ones that retained OB7 bootloader without flashing full tar updates, then it's also possible to Odin back to KitKat.
But once you update the bootloader via OTA, you'll see it in the update notes that downgrade of bootloader is no longer possible due to the increased security of newer bootloader. Odin would be the same but you wouldn't see the update notes.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
My mistake, I was right bot the loss of RAM. You can see that each time you upgrade from KitKat it locks op 20mb. I guess it doesn't cost to jump from 5 to 6. Does anyone know how to free it back up? I want to down grade for awhile but it seems to costly.
shadowcliffs said:
Can you show the way?
Click to expand...
Click to collapse
I posted a known method in the general forum's tar thread
http://forum.xda-developers.com/showpost.php?p=68456368&postcount=149
Another thread you may find helpful is below. Refer to post 22 for recommended links.
http://forum.xda-developers.com/showthread.php?p=63882755
When reading that thread, take into account the OP started on KitKat but wanted to go back after updating to Marshmallow.
Sent from my SM-N910P using Tapatalk
samep said:
I posted a known method in the general forum's tar thread
http://forum.xda-developers.com/showpost.php?p=68456368&postcount=149
Another thread you may find helpful is below. Refer to post 22 for recommended links.
http://forum.xda-developers.com/showthread.php?p=63882755
When reading that thread, take into account the OP started on KitKat but wanted to go back after updating to Marshmallow.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
So with OK1 bootlosder/baseband + customer LP kernel + pre-rooted KK rom itb can work on a phone currently on PD1? I want to give it a try but I'm kinda afraid of bricking it.
shadowcliffs said:
So with OK1 bootlosder/baseband + customer LP kernel + pre-rooted KK rom itb can work on a phone currently on PD1? I want to give it a try but I'm kinda afraid of bricking it.
Click to expand...
Click to collapse
I know this worked on Lollipop and I know you can go beck to Lollipop from Marshmallow.
If you really want to try it, I'd suggest TWRP backup, wipe everything but extSdCard, power down and Odin back to OK1 full stock tar. Let that auto boot and complete the setup wizard.
Odin TWRP. Backup. Factory reset, wipe everything but extSdCard. Flash the ROM and kernel before booting. TWRP backup if you like the result or before you modify anything, just in case (it may save some hassle down the road).
I can't guarantee you won't have any issues. If you do, restore the OK1 backup or restore your PD1 baseband and bootloader and restore PD1.
Save backups to extSdCard and verify all your md5 sums. Download twice and compete where no md5 is given. Keep flashables on extSdCard too. I'd also recommend setting up as new device to avoid issues. You could also delete the Android folder on your extSdCard as part of your wipes.
Sent from my SM-N910P using Tapatalk
samep said:
I know this worked on Lollipop and I know you can go beck to Lollipop from Marshmallow.
If you really want to try it, I'd suggest TWRP backup, wipe everything but extSdCard, power down and Odin back to OK1 full stock tar. Let that auto boot and complete the setup wizard.
Odin TWRP. Backup. Factory reset, wipe everything but extSdCard. Flash the ROM and kernel before booting. TWRP backup if you like the result or before you modify anything, just in case (it may save some hassle down the road).
I can't guarantee you won't have any issues. If you do, restore the OK1 backup or restore your PD1 baseband and bootloader and restore PD1.
Save backups to extSdCard and verify all your md5 sums. Download twice and compete where no md5 is given. Keep flashables on extSdCard too. I'd also recommend setting up as new device to avoid issues. You could also delete the Android folder on your extSdCard as part of your wipes.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I just had time to give it a try today. Unfortunately, it kept bootlooping after flashing the pre-rooted KK rom and BeastModeKernel. It booted up OK with OK1 tar though.
shadowcliffs said:
I just had time to give it a try today. Unfortunately, it kept bootlooping after flashing the pre-rooted KK rom and BeastModeKernel. It booted up OK with OK1 tar though.
Click to expand...
Click to collapse
Sorry that didn't work.
Did you factory reset and wipe everything but extSdCard?
It has worked before with the original OG5 Beastmode kernel but I didn't think a newer Android 5.1 would make any difference.
Sent from my SM-N910P using Tapatalk
samep said:
Sorry that didn't work.
Did you factory reset and wipe everything but extSdCard?
It has worked before with the original OG5 Beastmode kernel but I didn't think a newer Android 5.1 would make any difference.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Yes, wiped everything except for extsdcard x3. The kk rom used is N910PVPU1ANK2_Bonsai_Deodex_v0.0.3. Should I try other rom/kernel combination?
shadowcliffs said:
Yes, wiped everything except for extsdcard x3. The kk rom used is N910PVPU1ANK2_Bonsai_Deodex_v0.0.3. Should I try other rom/kernel combination?
Click to expand...
Click to collapse
Did you start with an Android 5.1 stock tar? Which one? What bootloader and baseband are you running? That would suggest OG5 stock tar. One post even called for OB7 baseband (but understand that you cannot Odin the full stock tar). But his phone was stuck with no means to restore stock due to absence of updates when bootloader initially got the reactivation lock that blocked downgrade.
Looking back through some history, success may be dependent on earlier updates. There is an OB7 baseband Odin flash available but I'd try OG5 stock tar first.
The kernel is here.
https://www.androidfilehost.com/?fid=24052804347789588
The ROM is OK but personally I'd prefer an Odexed ROM if you can find one. You're not limited to deodexed ROM for Xposed and Xposed uses the official Xposed framework for KitKat.
Did you have a question about Moar ROM? I'd totally understand if you went with that and didn't attempt any further with this KitKat method.
Edit: despite the lack of doze on Lollipop, battery was about the same between Moar and latest PG1 Marshmallow. I prefer the Smart Manager we had from Note 5 on Moar ROM to the Note 4 one we have on PG1. Smarter.
Sent from my SM-N910P using Tapatalk
samep said:
Did you start with an Android 5.1 stock tar? Which one? What bootloader and baseband are you running? That would suggest OG5 stock tar. One post even called for OB7 baseband (but understand that you cannot Odin the full stock tar). But his phone was stuck with no means to restore stock due to absence of updates when bootloader initially got the reactivation lock that blocked downgrade.
Looking back through some history, success may be dependent on earlier updates. There is an OB7 baseband Odin flash available but I'd try OG5 stock tar first.
The kernel is here.
https://www.androidfilehost.com/?fid=24052804347789588
The ROM is OK but personally I'd prefer an Odexed ROM if you can find one. You're not limited to deodexed ROM for Xposed and Xposed uses the official Xposed framework for KitKat.
Did you have a question about Moar ROM? I'd totally understand if you went with that and didn't attempt any further with this KitKat method.
Edit: despite the lack of doze on Lollipop, battery was about the same between Moar and latest PG1 Marshmallow. I prefer the Smart Manager we had from Note 5 on Moar ROM to the Note 4 one we have on PG1. Smarter.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
As mentioned in the first post, this Note 4 arrived with PC1, then I ondined it to PD1 beofre this. Then ondined OK1, wiped all, then kk rom and beastmode kernel. It's currently on MOAR. Still testing to see if it's stable for me.
Related
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
I tried to root and flash a room onto my Sprint Note 4 (N910P) and ended up in a weird bootloop. No biggie I've done this before with my S3 and S4 and a few S6 Phones.
NOPE!! I have NO OS installed.
I would post photos but since I am new here I cant. I have TWRP intalled (v.2.8.7.0) and it says "No OS installed! Are you sure you wish to reboot?" I only wiped dalvik cache and regular cache. and factory reset per instructions for rom. (Rom that was being installed was AllianceROM©N910P
I was running on Android version 5.0.1 not the latest OTA 5.1.1 I didnt update it to that since I never had a good time with OTA's and rooting.
Any assistance would be helpful as i just got the phone and now I dont have a working one at all
Thanks!
Do you know what release of Android 5.0.1 you had? Alliance is only compatible with the OB7 release.
Without much detail of what actually happened, I'd suggest rebooting the recovery and trying that flash again or another ROM like Noterized that should flash over the other builds.
Did you uber wipe or wipe everything but ExtSdCard maybe? If you used Odin, what did you flash and did you get any error messages?
Sent from my SM-N910P using Tapatalk
samep said:
Do you know what release of Android 5.0.1 you had? Alliance is only compatible with the OB7 release.
Without much detail of what actually happened, I'd suggest rebooting the recovery and trying that flash again or another ROM like Noterized that should flash over the other builds.
Did you uber wipe or wipe everything but ExtSdCard maybe? If you used Odin, what did you flash and did you get any error messages?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I actually found that I had the the one before OB7 Just spent 10 hours of trial and error and fixed my problem Basically just installed the OF5 stock rom and got rid of the other roms that wernt working.
Thank you for replying and assisting me :good:
Ninja Danny said:
I actually found that I had the the one before OB7 Just spent 10 hours of trial and error and fixed my problem Basically just installed the OF5 stock rom and got rid of the other roms that wernt working.
Thank you for replying and assisting me :good:
Click to expand...
Click to collapse
Good. FYI, OF5 came after OB7. It's important to know for a few reasons. Custom ROMs are limited for OF5 (Noterized and CM12 mostly; maybe some stock ones available also).
That OF5 (including OE1 and OG5) bootloader is reactivation locked to the point that Odin of a previous tar like OB7 or KitKat is going to cause a lot problems trying to flash something that actually boots again.
For some reason, a few have complained of inability to Odin latest OG5 from OF5 but had to first Odin OF5 and OTA update to OG5.
But if you want a custom ROM there's newer development going on in OG5. I'd try KIES or Odin OG5 stock tar if wanting to go that way. I think most on OF5 were able to Odin OG5 but not positive on that. Sorry to say that Alliance is not for you with that bootloader.
Sent from my SM-N910P using Tapatalk
samep said:
Good. FYI, OF5 came after OB7. It's important to know for a few reasons. Custom ROMs are limited for OF5 (Noterized and CM12 mostly; maybe some stock ones available also).
That OF5 (including OE1 and OG5) bootloader is reactivation locked to the point that Odin of a previous tar like OB7 or KitKat is going to cause a lot problems trying to flash something that actually boots again.
For some reason, a few have complained of inability to Odin latest OG5 from OF5 but had to first Odin OF5 and OTA update to OG5.
But if you want a custom ROM there's newer development going on in OG5. I'd try KIES or Odin OG5 stock tar if wanting to go that way. I think most on OF5 were able to Odin OG5 but not positive on that. Sorry to say that Alliance is not for you with that bootloader.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I would like to root and get a rom on my note soon but I haven't run a big problem like this in my years of modding (mind you its here and there modding and nothing fancy) for now im gonna stick with bloated stock until a decent non-buggy rom is released for the OF5 bootloader. I didnt know which was which since im new to the Note Family. Been in the S2-4 series most of my time.
Looking for a good stable rom with no bloat and adblocking, nothing fancy
Thanks again.
Ninja Danny said:
I would like to root and get a rom on my note soon but I haven't run a big problem like this in my years of modding (mind you its here and there modding and nothing fancy) for now im gonna stick with bloated stock until a decent non-buggy rom is released for the OF5 bootloader. I didnt know which was which since im new to the Note Family. Been in the S2-4 series most of my time.
Looking for a good stable rom with no bloat and adblocking, nothing fancy
Thanks again.
Click to expand...
Click to collapse
I would suggest @tx_dbs_tx 's Hybrid x 3.0. You can unzip it and remove whatever you don't want re-zip and then flash it.
Find it here :
http://forum.xda-developers.com/showthread.php?t=2956667
Read the OP carefully and you'll be good to go.
jhill110 said:
I would suggest @tx_dbs_tx 's Hybrid x 3.0. You can unzip it and remove whatever you don't want re-zip and then flash it.
Find it here :
http://forum.xda-developers.com/showthread.php?t=2956667
Read the OP carefully and you'll be good to go.
Click to expand...
Click to collapse
Would that work for my phone thats running OG5? android version 5.1.1 ?
*Edit*
I am going to try to flash this and see if it works. I will update on progress.
Ninja Danny said:
Would that work for my phone thats running OG5? android version 5.1.1 ?
*Edit*
I am going to try to flash this and see if it works. I will update on progress.
Click to expand...
Click to collapse
I will repeat this (not with condescension) read the OP carefully... And you will be good.
jhill110 said:
I would suggest @tx_dbs_tx 's Hybrid x 3.0. You can unzip it and remove whatever you don't want re-zip and then flash it.
Find it here :
http://forum.xda-developers.com/showthread.php?t=2956667
Read the OP carefully and you'll be good to go.
Click to expand...
Click to collapse
jhill110 said:
I will repeat this (not with condescension) read the OP carefully... And you will be good.
Click to expand...
Click to collapse
It worked fine, phone runs like a dream. Only issue is the stock camera is very poor quality so I might mod that next.
I got the note 4 I am on kit kat N2K. I want to root but wanted to know the best way to go about it. Root on kitkat, then flash a rom to get on lollipop? Or accept the lollipop update, and then root and flash? Please advise thank you !
You'd have to decide what you want the most.
With Lollipop you get improved Sprint Wi-Fi Calling and latest security and bug fixes. The battery usage is notoriously higher in Lollipop and the fabled material theme is ugly to many.
KitKat has better battery and theme. Until the recent Android 5.1.1 updates, Lollipop bugs had many utilizing fixes to make Lollipop more like KitKat. The thing most important to consider is that if you upgrade to Android 5.1.1, the bootloader will inhibit you from Odin'g back to KitKat unless you use a specific Odin tar for OB7 to OG5 but it doesn't support the most recent OJ6 update. It's said you could just update the modem to OJ6 but I'd think you have to at least Odin the OB7 lollipop tar before doing that.
I wouldn't recommend rooting and then flashing a ROM outside of the base you're running. Use Odin to update to the equivalent base. OJ6 would be the latest but bootloader inhibits downgrade to KitKat.
I'd suggest rooting KitKat and trying it or a custom NK2 ROM. Next you could try OB7 to see if Lollipop is to your liking. Then you could decide if the latest is what you prefer.
Developer support is currently at OG5 and OJ6; Android 5.1.1 Keep in mind that Android 5.1.1 stock requires kernel with root exploit and SuperSU zip flashed in custom recovery to root. The updates prior can be rooted with CF Auto Root or just Odin custom recovery and flashing custom ROM or SuperSU zip to root stock.
What to flash? You'd have to ask a specific question once you have a better idea of what you prefer or direction you're starting at.
Sent from my SM-N910P using Tapatalk
Thank you for taking the time to type all that up for me! I am going to stay stock until the 14 days incase the phone has some problems before rooting but my brother and dad have note 4 also and both on 5.1.1 and phones are way smoother than mine on kit kat so I would want to be on the latest and have root. I also saw there is a note 5 rom which looks great as well. So is it cool if I PM you in a week or so to help me? I know there are threads but I dunno where to begin . Appreciate it!
Thank you,
Indels
Yes, you could PM. Are the other Note 4 phones rooted or plain stock?
Currently, the Note 5 port is one update behind latest. Maybe it will update.
You don't have to stay with KitKat. Updating won't void your return exchange. But I would recommend a factory reset before making the jump to Lollipop. You can take incremental updates over the air; KIES or Odin stock tar OJ6 from general forum would get you updated to latest in one session.
Just don't Odin custom recovery if you're concerned about Knox trip during your return period.
To get started you'll need the Samsung driver for your PC to use with KIES or Odin. You'll find that here:
http://www.samsung.com/us/support/owners/product/SM-N910PZWESPR# Run the .exe file on PC to install.
Here's a link to TWRP for Note 4:
https://dl.twrp.me/trltespr/twrp-2.8.7.0-trltespr.img.tar
Download Odin (below) and make a folder for it and put the TWRP file and stock tar in it. Find the latest tar in general forum and check the md5.
http://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
You can also download the zip for ROM you wish to install. Typically, you'd flash the tar that corresponds to the ROM you wish to run for maximum compatibility so you could wait on the tar and zip. Any of these could change but preparation wouldn't hurt.
Sent from my SM-N910P using Tapatalk
Yeah the other 2 notes are on 5.1.1 stock. I am still on kitkat, update notification for lollipop is annoying tho I can't find a way to get rid of it lol. I get good battery on Kitkat is the phone still good on 5.1.1? Is root out for 5.1.1 as well? I would assume so. Thank you for the links! !
Ind3lible said:
Yeah the other 2 notes are on 5.1.1 stock. I am still on kitkat, update notification for lollipop is annoying tho I can't find a way to get rid of it lol. I get good battery on Kitkat is the phone still good on 5.1.1? Is root out for 5.1.1 as well? I would assume so. Thank you for the links! !
Click to expand...
Click to collapse
Battery life for initial Lollipop was not so good until Beastmode kernel came out starting in OG5. I've heard OJ6 is even better but I haven't tried it.
Like I said, KitKat has better battery but worse Wi-Fi Calling feature.
Touchwiz 5.1.1 is rooted with custom kernel and SuperSU zip or any custom ROM is pre-rooted. Just don't use Chainfire auto root for Note 4 on that.
Sent from my SM-N910P using Tapatalk
"But I would recommend a factory reset before making the jump to Lollipop."
So I should factory reset on kit kat and then go to lollipop if I understand this part correctly? I have to notification to go to 5.0 right now. I can odin twrp once I go to lollipop too right? Sorry for so many questions just confused. I have not rooted a phone in quiet some time :fingers-crossed:
Correct. You shouldn't have any problem rooting once you update, even latest update.
You'll have to reapply TWRP after update. OTA updates are incremental but Odin or KIES will allow you to jump to latest update available. Currently, that's OJ6.
Sent from my SM-N910P using Tapatalk
samep said:
Correct. You shouldn't have any problem rooting once you update, even latest update.
You'll have to reapply TWRP after update. OTA updates are incremental but Odin or KIES will allow you to jump to latest update available. Currently, that's OJ6.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
So it updated on its own to lollipop.. lame so I am on 5.0.1.. the nofication was there since day 1. Now my question is can I go back to Kit kat from here? I searched google and could not find a definite answer. :crying:
I was happy on kitkat everything worked as it should and battery was great!
Ind3lible said:
So it updated on its own to lollipop.. lame so I am on 5.0.1.. the nofication was there since day 1. Now my question is can I go back to Kit kat from here? I searched google and could not find a definite answer. :crying:
I was happy on kitkat everything worked as it should and battery was great!
Click to expand...
Click to collapse
OTA updates are incremental so if you catch it before it updates beyond OB7, you can still Odin back to KitKat. You should go into app manager and disable software update package in all apps and turn off auto update.
You'll need to factory reset before going back to KitKat. If you've updated past OB7, it's too late.
If you're able to jump back check out this post and follow the links:
http://forum.xda-developers.com/showpost.php?p=62620747&postcount=3
Sent from my SM-N910P using Tapatalk
JUST A QUICK WORD OF ADVICE TO THE op @Ind3lible FOR YOUR SAKE DONT UPDATE BOOTLOADER BEYOND THE OB7 UPDATE TARBALL BECAUSE OF ROOT RESTRICTIONS THAT ARE TROUBLESOME TO GET AROUND... yOU CAN STILL TAKE ADVANTAGE OF 5.1.1 LOLLI ROMS WITH THE OG5 BASEBAND MADE AVAILABLE BY @tx_dbs_tx
samep said:
OTA updates are incremental so if you catch it before it updates beyond OB7, you can still Odin back to KitKat. You should go into app manager and disable software update package in all apps and turn off auto update.
You'll need to factory reset before going back to KitKat. If you've updated past OB7, it's too late.
If you're able to jump back check out this post and follow the links:
http://forum.xda-developers.com/showpost.php?p=62620747&postcount=3
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you so much ! I was able to ODIN BACK! I am gonna stay on KK for the time being. Just gotta root it, I have TWRP and ODIN Downloaded now. Is there is thread for KK root? I see the 5.1.1.
Ind3lible said:
Thank you so much ! I was able to ODIN BACK! I am gonna stay on KK for the time being. Just gotta root it, I have TWRP and ODIN Downloaded now. Is there is thread for KK root? I see the 5.1.1.
Click to expand...
Click to collapse
If you plan to root stock KitKat, use Chainfire auto root in Odin and then Odin TWRP; custom ROMs are already rooted, just Odin TWRP.
http://forum.xda-developers.com/showpost.php?p=55865427&postcount=1
Download for SM-N910P is in third post.
Sent from my SM-N910P using Tapatalk
samep said:
If you plan to root stock KitKat, use Chainfire auto root in Odin and then Odin TWRP; custom ROMs are already rooted, just Odin TWRP.
http://forum.xda-developers.com/showpost.php?p=55865427&postcount=1
Download for SM-N910P is in third post.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you good sir! You've been of most help!!
alwright1980 said:
JUST A QUICK WORD OF ADVICE TO THE op @Ind3lible FOR YOUR SAKE DONT UPDATE BOOTLOADER BEYOND THE OB7 UPDATE TARBALL BECAUSE OF ROOT RESTRICTIONS THAT ARE TROUBLESOME TO GET AROUND... yOU CAN STILL TAKE ADVANTAGE OF 5.1.1 LOLLI ROMS WITH THE OG5 BASEBAND MADE AVAILABLE BY @tx_dbs_tx
Click to expand...
Click to collapse
Thank you for this.. Not sure how I missd your post but I did already update to Ok1 and am very happy with it battery is great and it is super smooth !
I havent keard of a firmware ending ok1 for the SM-N910P
---------- Post added at 02:37 PM ---------- Previous post was at 02:36 PM ----------
Ind3lible said:
Thank you for this.. Not sure how I missd your post but I did already update to Ok1 and am very happy with it battery is great and it is super smooth !
Click to expand...
Click to collapse
These are the ones I know for Sprint Note 4
N910PVPU...
. . .ANIE . . .ANK2. . .BOB7*. . .BOF5** . . . COG5***...COJ6**
Android
[<==K I T K A T==>][<=======L O L L I P O P=========>] [^^<===4.4.4==>^^][^^<==5.0.1==>^^][^^<==5.1.1==>^^]
*No Locked Bootloader/Mininmal Root Restrictions
**May or May Not have locked Bootloader/minimal root restrictions
***Locked Bootloader/Strict Root RestrictionsAll of them have there benefits. I have had people tell me that they will not leave kit kat 4.4.4 because of development is more.... well.... developed! BOB7 was the last bootloader that was a necessary component for loading a lollipop rom, AND didn't have Heavy duty root restrictions and either it or its progeny three months later was the last to not have a locked bootloader. That is where once you have their bootloader you cannot flash back to a previous one. For sure it was off by COG5 and has we all know they instituted some root restrictions that took a long time to get around and even longer time to do so with an "apparent" seandroid enforcing kernel.
All that is to say again, that, whatever you actually are on, if it is still BOB7 or earlier, then when it comes time that you want a 5.1.1 rom custom stock or otherwise, flash the appropriat baseband version of the bootloader that @tx_dbs_tx puts out it will keep you able to do the same things but without locking you into a change you cannot undo. I don't know if this will be an option for marshmallow when the note 4 gets it. If so great if no wait & update late.
My 2cents
alwright1980 said:
---------- Post added at 02:37 PM ---------- Previous post was at 02:36 PM ----------
These are the ones I know for Sprint Note 4
N910PVPU...
. . .ANIE . . .ANK2. . .BOB7*. . .BOF5** . . . COG5***...COJ6**
Android
[<==K I T K A T==>][<=======L O L L I P O P=========>] [^^<===4.4.4==>^^][^^<==5.0.1==>^^][^^<==5.1.1==>^^]
*No Locked Bootloader/Mininmal Root Restrictions
**May or May Not have locked Bootloader/minimal root restrictions
***Locked Bootloader/Strict Root RestrictionsAll of them have there benefits. I have had people tell me that they will not leave kit kat 4.4.4 because of development is more.... well.... developed! BOB7 was the last bootloader that was a necessary component for loading a lollipop rom, AND didn't have Heavy duty root restrictions and either it or its progeny three months later was the last to not have a locked bootloader. That is where once you have their bootloader you cannot flash back to a previous one. For sure it was off by COG5 and has we all know they instituted some root restrictions that took a long time to get around and even longer time to do so with an "apparent" seandroid enforcing kernel.
All that is to say again, that, whatever you actually are on, if it is still BOB7 or earlier, then when it comes time that you want a 5.1.1 rom custom stock or otherwise, flash the appropriat baseband version of the bootloader that @tx_dbs_tx puts out it will keep you able to do the same things but without locking you into a change you cannot undo. I don't know if this will be an option for marshmallow when the note 4 gets it. If so great if no wait & update late.
My 2cents
Click to expand...
Click to collapse
SO been a while! I am now on 6.0.1 and I had a question. Is it possible still to go back to 4.4.4? I know the bootloader has changed since as mentioned in your earlier post but I wanna know if it is possible. I wanna test something on kitkat for my tech channel! I know I have to flash the old bootloader and modem as well but not sure if it will actually work!! :highfive:
Ind3lible said:
SO been a while! I am now on 6.0.1 and I had a question. Is it possible still to go back to 4.4.4? I know the bootloader has changed since as mentioned in your earlier post but I wanna know if it is possible. I wanna test something on kitkat for my tech channel! I know I have to flash the old bootloader and modem as well but not sure if it will actually work!! :highfive:
Click to expand...
Click to collapse
I don't think it would have been possible to have gon from KK - LP - MM while preserving a KK Bootloader, and if I am correct in that you won't bee able to Odin back to KK unles you can get reliable instructions on how to seperately flash bootloader, which might be a risky venture, I simply don't know there. You also may be able to get a custom rom which is KK based but I would discuss trying to use it on a phone that has been updated to MM with the DEV if they still offer support. Whatever you do be cautious and well informed before proceeding and know your risks, otherwise it can get expensive.
---------- Post added at 01:57 PM ---------- Previous post was at 01:54 PM ----------
I would have thought that it would have been impossible to flash 2 a lollipop and then a marshmallow ROM from a KitKat ROM while preserving the KitKat bootloader. If I'm correct in this then you will not be able to Odin Flash from your marshmallow ROM back to stock KitKat firmware. That is unless you know of a way to separately and reliably Flash your bootloader. You may be able to use a custom rom that incorporates KitKat, but I would be careful about deploying around like that after having updated to marshmallow firmware, and I would discuss it with the developer if they're still offering support for it. Whatever you do be cautious and well informed before moving forward otherwise it can get expensive!
Ind3lible said:
SO been a while! I am now on 6.0.1 and I had a question. Is it possible still to go back to 4.4.4? I know the bootloader has changed since as mentioned in your earlier post but I wanna know if it is possible. I wanna test something on kitkat for my tech channel! I know I have to flash the old bootloader and modem as well but not sure if it will actually work!! :highfive:
Click to expand...
Click to collapse
It can be done but not as you would think. The KK bootloader wouldn't flash but read the instructions in this post.
http://forum.xda-developers.com/showpost.php?p=68456368&postcount=149
Edit: if you still have that KK backup, you could restore that instead of the KK ROM but still need the Lollipop custom kernel and Lollipop bootloader.
Sent from my SM-N910P using Tapatalk
Like I said I don't know anything about bootloader switching betweem KK -LP -MM. So I cannot comment effectively on whether or not it would besafe or what you might lose or gain by these methods. Just don't know.
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
Hello all,
I am currently on 6.0.1 fully stock. I want to go back to 5.1.1 can I just ODIN Ok1 with odin and be good to go? It is my only phone and would prefer not to brick it . Please advise.
Thank you!
Ind3lible said:
Hello all,
I am currently on 6.0.1 fully stock. I want to go back to 5.1.1 can I just ODIN Ok1 with odin and be good to go? It is my only phone and would prefer not to brick it . Please advise.
Thank you!
Click to expand...
Click to collapse
Yes you can odin back to 5.1.1. Just make sure you flash the correct tar.
Ind3lible said:
Hello all,
I am currently on 6.0.1 fully stock. I want to go back to 5.1.1 can I just ODIN Ok1 with odin and be good to go? It is my only phone and would prefer not to brick it . Please advise.
Thank you!
Click to expand...
Click to collapse
Better not. You can go up in version , but not down.
yes
Iv'e had to do it several times because Ive had trouble with viper4android in 6.01. Just get the right tar file and flash in odin. Grab an updated twrp recovery while you are at it.
chrisresponsibility said:
Iv'e had to do it several times because Ive had trouble with viper4android in 6.01. Just get the right tar file and flash in odin. Grab an updated twrp recovery while you are at it.
Click to expand...
Click to collapse
Viper works fine on MM. Either flash viper installation zip than the subpolicy zip from here, http://forum.xda-developers.com/showthread.php?t=3355270 .Or a permissive kernel like beastmode, from here http://forum.xda-developers.com/showthread.php?t=3284505 .
chrisresponsibility said:
Iv'e had to do it several times because Ive had trouble with viper4android in 6.01. Just get the right tar file and flash in odin. Grab an updated twrp recovery while you are at it.
Click to expand...
Click to collapse
Awesome, thank you so much!! So OK1 was the last lollipop right? I have the TAR but where is the twrp. I have not rooted the note 4 ever. So don't know much how to get TWRP on it yet.
Ind3lible said:
Awesome, thank you so much!! So OK1 was the last lollipop right? I have the TAR but where is the twrp. I have not rooted the note 4 ever. So don't know much how to get TWRP on it yet.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=66903690
Sent from my SM-N910P using Tapatalk
samep said:
http://forum.xda-developers.com/showthread.php?p=66903690
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks brotha!
i Have a bootloop when flash OK1 From PD1...... On What Version may Downgrade From PD1?
michael_0302 said:
i Have a bootloop when flash OK1 From PD1...... On What Version may Downgrade From PD1?
Click to expand...
Click to collapse
You flashed the full stock tar OK1 and got a bootloop? Just a guess but since Lollipop and Marshmallow differ on app optimization, I think you have to wipe data to get it to boot. Factory reset in stock recovery or wipe data in custom recovery.
If that's the case, you can take data to marshmallow (it seems to anticipate that but may still need factory reset adb ItsOn completely removed after root for some rooted users but also factory reset seemed to apply to PC1 OTA for un-rooted users). But maybe you can't take optimized apps back to Lollipop? Confirm that if it works.
Lollipop may be trying to rebuild the dalvik-cache but gets tripped up by the odex files in the oat folders of every app in data partition. Result could be bad boot. Loops.
Sent from my SM-N910P using Tapatalk
Thread moved to correct forums.
samep said:
You flashed the full stock tar OK1 and got a bootloop? Just a guess but since Lollipop and Marshmallow differ on app optimization, I think you have to wipe data to get it to boot. Factory reset in stock recovery or wipe data in custom recovery.
If that's the case, you can take data to marshmallow (it seems to anticipate that but may still need factory reset adb ItsOn completely removed after root for some rooted users but also factory reset seemed to apply to PC1 OTA for un-rooted users). But maybe you can't take optimized apps back to Lollipop? Confirm that if it works.
Lollipop may be trying to rebuild the dalvik-cache but gets tripped up by the odex files in the oat folders of every app in data partition. Result could be bad boot. Loops.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Did you get this working? I still have not flashed but am scared now lol =(
Ind3lible said:
Did you get this working? I still have not flashed but am scared now lol =(
Click to expand...
Click to collapse
Not sure of your question but in context, what I did was flash the OK1 bootloader, factory reset and restore Lollipop TWRP backup. I suggested to the user I quoted that his boot loop was caused by app optimization of MM. He could confirm that by factory resetting and attempt to boot. I didn't get a confirmation.
The advice I would give is to first backup and then make a clean break with Marshmallow data if intent is to temporarily go back to Lollipop. The bootloader method is ideal for users with Lollipop backup to restore but for those without the Lollipop backup, I think the full tar is best.
But remember to make sure reactivation lock in Settings/Security is disabled before flashing and remove fingerprints before backups or restore to avoid issues with those features. If you follow the forums, you can verify that it is possible to go back to Android 5.1 from Android 6.0 using Odin full tar.
I've been on MM since PD1 update. Currently on PE1 Odexed with Xposed framework.
Edit: didn't realize you were the OP. Sorry. I'd just recommend the factory reset but first disable reactivation lock and delete fingerprints and make a backup. If you have the Lollipop TWRP backup to restore, the OK1 bootloader is in the development forum for Sprint Note 4 in a thread by freeza: baseband and bootloader thread.
Sent from my SM-N910P using Tapatalk
samep said:
Not sure of your question but in context, what I did was flash the OK1 bootloader, factory reset and restore Lollipop TWRP backup. I suggested to the user I quoted that his boot loop was caused by app optimization of MM. He could confirm that by factory resetting and attempt to boot. I didn't get a confirmation.
The advice I would give is to first backup and then make a clean break with Marshmallow data if intent is to temporarily go back to Lollipop. The bootloader method is ideal for users with Lollipop backup to restore but for those without the Lollipop backup, I think the full tar is best.
But remember to make sure reactivation lock in Settings/Security is disabled before flashing and remove fingerprints before backups or restore to avoid issues with those features. If you follow the forums, you can verify that it is possible to go back to Android 5.1 from Android 6.0 using Odin full tar.
I've been on MM since PD1 update. Currently on PE1 Odexed with Xposed framework.
Edit: didn't realize you were the OP. Sorry. I'd just recommend the factory reset but first disable reactivation lock and delete fingerprints and make a backup. If you have the Lollipop TWRP backup to restore, the OK1 bootloader is in the development forum for Sprint Note 4 in a thread by freeza: baseband and bootloader thread.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I don't have any finger print and I am not sure what reactivation lock it. But I am fully stock PE1 at the moment. I would go back to lollipop for good. MM doesn't have anything that lollipop does for me at least.
Ind3lible said:
I don't have any finger print and I am not sure what reactivation lock it. But I am fully stock PE1 at the moment. I would go back to lollipop for good. MM doesn't have anything that lollipop does for me at least.
Click to expand...
Click to collapse
Reactivation Lock is in Settings/Security. Uncheck it before flashing.
No TWRP backup? Then I would suggest backing up what you want to keep, factory reset in TWRP and wipe internal memory and power down.
Odin OK1 stock tar in Odin and disable automatic updates in Settings/System update. Install TWRP, follow OP; make sure auto update remains disabled. If you don't disable auto updates stock enough, the update becomes persistent; you'll have to Google how to stop the persistent update notice if that happens.
One additional step I recommend after flashing custom ROM is to search your root folder for itson; delete what your search results. You may find a leftover folder at /carrier/ItsOn and a dalvik-cache belonging to an application in that folder in /data/dalvik-cache; that can cause a lot if persistent reboot demands after a factory reset despite the ROM not having ItsOn- this is a trace residue left in internal memory that gets added when you flash the stock tar in Odin. Enjoy Lollipop.
Personally, I think you'll want to come back to Marshmallow despite not seeing anything you want right now. You could make that TWRP backup and save TWRP folder to PC, just in case. To come back, all you would need to do is update the bootloader and baseband, factory reset and restore the backup.
Marshmallow is stricter but still manageable. Just takes some getting accustomed to. Once the tools and methods are achieved with proven compatibility, there may soon be custom ported ROMs for Note 4 on Marshmallow. At the moment it's thought to be a matter of when, not if. Time will tell if that thought is true.
Sent from my SM-N910P using Tapatalk