Title sums it up. Currently on AllianceROM 5.0.1 OB7. Want to go to stock (rooted probably) so I can get MM when it (if it ever) drops. Do I need to do anything special or can I just wipe everything in TWRP, then Odin the stock zip? I get a little weary reading about bootloaders locking above OB7. What does that mean for flashing ROMs if I upgrade the bootloader? Also, does the hotspot fix work on the most recent stock ROM?
Thanks for any help. I have three little kids and no time to research this fully, otherwise I would.
If you're looking to stay OTA capable without going through Odin again to update to MM (weeks to go possibly, IDK?), you most likely wouldn't be able to add hotspot mod without losing OTA capability.
- Use the updated Chainfire Auto Root for Note 4 mostly stock with OTA capability.
*You'd use the full un-root option in SuperSU to update. It's supposed to work if no system mods or system mounting occurs but no guarantee or confirmation I'm aware of on that. You could test that with OJ6, full un-root and take OK1 OTA update if so inclined to test it.
==================================
If upgrading to the reactivation locked bootloaders, alternate ROMs really have little limitation if done without Odin downgrading (only where the ROM you seek or return to is on an older update- that applies to alliance whether you're restoring a backup or flashing a ROM zip). But that also requires Odin again at some point unless you wait and do it only when necessary. You must flash ROM zip or restore a backup and flash a 5.1 kernel like Beastmode rather using Odin to downgrade. The kernel had to be flashed in order to get it to boot. Only limitation that I'm aware of is that your screen may not auto-dim on handset call when you put phone to ear. I had that issue with OB7 ROM with 5.1 kernel; I used the power button to dim the screen but you can't have power button set as an option to dismiss call or that happens when you don't want it to.
=================================
Moar 2.1 ROM is coming soon. That may help with the anticipation of waiting long for MM. But again, that means Odin for OK1 update, then Odin for MM. There's a chance that OTA to MM could be achieved even if dm-verity gets detected in stock recovery while trying to OTA. I think you'd have to clear and download the MM OTA again but first root with Chainfire Auto Root, full un-root in SuperSU app then try the OTA again. Odin OK1 by itself may not clear the modified status but systemless root and un-root may clear it. Just thinking ahead though; no guarantees. May have to wait for MM stock tar.
If not interested in current or future Lollipop rooms, you could just wait, Odin OK1 and OTA to MM when the update is available. Easy?
To answer the Odin question, you're correct on the update though. I tried to answer any questions you might have but may confuse you. I'd need more information on direction you're considering to answer more thoroughly if that leaves more questions.
Sent from my SM-N920P using Tapatalk
I'll have to find a time when I have time and can be without a working phone for a few hours and try to play around with some of this stuff. I'm sure I'll be back on here with questions at some point. Thanks for the initial guidance.
Sent from my SM-N910P using Tapatalk
Okay. I think today is the day. I've downloaded MOAR 2.1 and am going to try this for now. I also have the OJ6 stock (I know it's not the absolute most current) downloaded and ready for standby if I so choose. Here is my plan.
1) Wipe Factory Reset in TWRP 3x's (actually include internal storage as well, correct?)
2) Install TWRP 3.0 via Odin (currently 2.8.5)
2a) Per MOAR install instructions, install stock OJ6 via Odin and activate, etc, etc. Ensure everything works, maybe take the OTA to OK1.
3) install MOAR via TWRP from micro SD card
4) Profit!
If I want to install stock, all I need to do is install the stock ROM via Odin and I will be able to update OTA since I will by default be unrooted, correct?
Thanks for the help. I plan to attempt this later today.
I don't know if the whole OTA capability appeals to you, you didn't mention it so I won't bring it up again.
You can find the link to OK1 stock tar in page 2 of that Moar thread.
I'd suggest you follow that OP closely. Particularly the recommended wipes. The developer prefers a clean approach, wiping the data and setting up as a new device. With ports, that's important.
If GPS is important, there is a bug fix release anticipated very soon. You may consider waiting for that but you can update to OK1 and back that up in TWRP while you're deciding. May not be long at all.
Sent from my SM-N910P using Tapatalk
samep said:
I don't know if the whole OTA capability appeals to you, you didn't mention it so I won't bring it up again.
You can find the link to OK1 stock tar in page 2 of that Moar thread.
I'd suggest you follow that OP closely. Particularly the recommended wipes. The developer prefers a clean approach, wiping the data and setting up as a new device. With ports, that's important.
If GPS is important, there is a bug fix release anticipated very soon. You may consider waiting for that but you can update to OK1 and back that up in TWRP while you're deciding. May not be long at all.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Well, I've got TWRP 3.0 installed. However, I've tried each stock (OJ6 and OK1) and each says that there is no update-binary in the zip files. Ideas?
edit: the zip files have a xx.tar.md5 file. Do I need to extract, rename it .tar and flash via odin?
pilotmills said:
Well, I've got TWRP 3.0 installed. However, I've tried each stock (OJ6 and OK1) and each says that there is no update-binary in the zip files. Ideas?
edit: the zip files have a xx.tar.md5 file. Do I need to extract, rename it .tar and flash via odin?
Click to expand...
Click to collapse
The stock tar is for Odin. Look for the thread in Sprint Note 4 General Forum for better direction.
You should verify the md5 against the zip, then extract only tar.md5 for Odin flash in download mode. But wipe and power down first. Use latest Odin with Odin defaults.
You'll have to install TWRP again.
Sent from my SM-N910P using Tapatalk
samep said:
The stock tar is for Odin. Look for the thread in Sprint Note 4 General Forum for better direction.
You should verify the md5 against the zip, then extract only tar.md5 for Odin flash in download mode. But wipe and power down first. Use latest Odin with Odin defaults.
You'll have to install TWRP again.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I think I need to slow down my postings . I looked around and found out basically what you just told me. Flashing the stock OK1 now, then I'll redo TWRP. Thanks for the timely replies. I'll try to keep it to only issues I run into that I can't resolve after some Google research. I really do appreciate the help.
Progress, but now I can't get the GPS to lock. Tried GPS status app, GPS Status and toolbox. Occasionally I get one or two satellites that show a signal being received, but never locking onto them. Eventually they will drop completely to zero signal. On the other hand, somewhere between OB7 and OK1, Samsung actually addressed the barometer issue that had plagued the N4 since launch where above about 3,000', it would not register anything but a sea-level pressure. Baby steps. . .
Is GPS failing to lock on stock OK1 tar update or the port? The port has GPS a release with fixes pending. But most were only reporting GPS navigation in Google Maps lagging or losing sync during navigation.
Sent from my SM-N910P using Tapatalk
Sorry, should have specified. I'm on stock OK1 now.
pilotmills said:
Sorry, should have specified. I'm on stock OK1 now.
Click to expand...
Click to collapse
Have you tried activation or data and PRL update in system update? Try those with Wi-Fi off.
Sent from my SM-N910P using Tapatalk
samep said:
Have you tried activation or data and PRL update in system update? Try those with Wi-Fi off.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
The GPS chip in this phone is horrible. I had the phone up against the window as a last resort and still nothing from the GPS. Went outside and it grabbed a lock within 30 seconds. I didn't opt for the anti-NSA snooping coating on the windows when we had them installed either. . . Backing up OK1 in TWRP now, then attempting to flash MOAR.
Thanks again. Stay tuned. . .
Got MOAR up and running. I had an activation issue the first time which was strange since I was able to send and receive texts and calls, but I kept getting an activation not complete message popping up and persisting. I did exactly as posted in the OP as well. Anyway, went back to OK1 stock and waited even longer after the data established before reflashing MOAR. Works like a charm now. Thanks for the patience and assistance!
Related
[ROM] [N910PVPS4COK1] [100% Stock, Root, Odexed&Deodexed, No KNOX/Itson] [12/15/2015]
Once again I bring to you two completely stock builds of Android TW-Lollipop 5.1.1 (N910PVPS4COK1) for the Sprint Samsung Galaxy Note 4.. Both ROMs are built from the official Samsung tar ball. The ROM will self root upon flash and it has init.d/busybox support. Knox and Sprint Itson has been removed. Both ROMs are completely stock with all of the original factory installed apps. Available in odexed and deodexed. Both ROMs are identical other than one being odexed and the other deodexed. Also included in both ROMs in this thread is the stock OK1 modem and APN patch to ensure you have the latest modem & APN's from the latest OK1 software.
Other than the removal of Knox and Sprint Itson, these roms are 100% stock in every other way. They are stock and will stay that way. Please don't ask for mods, changes, etc in this thread. These roms are intended for those people who want the stock roms in their original form with the addition of root and removal of Knox & itson, as well as other members who need a good solid base for their rom projects. I give permission for other dev's to use this rom as your base ONLY if you contact me prior to using it. If I find users using my work without proper credits I will report you and make you look like a fool I promise. Do the right thing and give credits to people for their time and work. It's a curtesy and respect thing nothing more. With that said, I highly recommend other rom chef's/dev's to use this base rom because it is bug-free and built from the official Samsung tar ball. Last but not least, if you appreciate my work please press that Thanks button, rate this thread and consider a kind donation! Enjoy!
Mods and fixes will be in post #2 below.
Important Notes: Before flashing ANY Lollipop 5.1.1 TW-based ROM, including this one, you MUST first do one of the following:
1. Take the Lollipop OK1 ota update on your phone. (Start by being on the stock unrooted OJ6 rom then take the OK1 ota update)
2. Odin flash the stock OK1 rom tar using odin on your PC. Thanks @samep
http://forum.xda-developers.com/showpost.php?p=64337077&postcount=115
Once you have correctly updated your Note 4 to Lollipop 5.1.1, software version N910PVPS4COK1 DO NOT... I repeat, DO NOT attempt to root your phone with CF-auto root or other methods. It will soft brick your phone. Instead, you ONLY need to flash the latest TWRP recovery using odin on your pc. Nothing else. The ROM zip will automatically root your phone.
If you are still on any KK or Lollipop 5.0 TW-based ROM such as NIE, NK2, OB7, OE1 , OF5, OB7 or OJ6 (including any KK AOSP/CM-based roms) then you MUST first update to Lollipop 5.1.1 OK1 by one of the two methods I mentioned above BEFORE flashing this ROM. Failure to properly update your device partitions to 5.1.1 OK1 firmware absolutely WILL cause problems. You have been warned. Please don't ask for help if you did not follow my simple instructions and warnings.
Flashing instructions: ***Before beginning the flash/setup process MAKE SURE your battery has at least 50% charge and/or connected to the charger!!!***
1. Backup anything you don't want to lose off your internal and external storage to another location just to be safe.
2. Download the rom using your pc. (downloading with your phone has a much higher risk of file corruption. Not recommended with large files).
3. VERIFY the MD5!!! Once the download has finished, compare the androidfilehost MD5 using a MD5 tool on your pc. (Google "md5 checksum windows") for a good MD5 tool for your pc.
4. Put the downloaded rom onto your internal storage or external micro sd card.
5. With phone powered off, reboot into recovery by pressing and holding volume up, power and the home button until you see the Samsung logo then release all buttons.
6. Once in recovery choose the wipe button and do a factory reset three times. Optional but recommended is to wipe "Data". This will wipe all of your user data such as google accounts so MAKE SURE you backed up first like I said in step #1 above! Next go to "advanced wipe" and select all of the partitions EXCEPT micro-sd card and internal storage. Internal storage is optional but recommended when first updating to a major software revision such as 4.3 to 4.4 or 5.0.1 to 5.1.1. The reason is to remove left-over data from previous version of Android and start with a clean slate.
7. Choose the "Install" option and select the rom "Sprint_Stock_N910PVPS4COK1_XXX" from either your internal or external micro-sd card. It will flash the rom and give a confirmation once completed.
8. Press "Reboot" then "reboot system". You will get a prompt warning about not having root. Please IGNORE IT and DO NOT allow TWRP to apply root! If you do then you MUST wipe everything and start over at step 5 above and reflash the rom in order to get rid of the traditional root system binaries. ***Please pay attention and DO NOT let TWRP install root. Ignore the "No Root" warning.***
9. Initial rom "optimization" will take several minutes for the deodexed rom while ART builds its cache (the odexed rom takes much less time for first boot). The phone will remain on the yellow Sprint Spark screen for about 10 -13 minutes during this time. Let the phone optimize for at least 13 minutes (for the deodexed rom) and the screen will eventually turn off or show the setup wizard once it finishes. When the screen turns off, simply turn it on and proceed to setup your phone.
10. Once finished with the setup wizard, wait a few moments and the phone will automatically install the Sprint apps. You must either "accept" or "disagree" with each and every google prompt for these apps or else the installs pause until you do so.. Also you will be prompted for the "connections optimizer". Quickly set it to what you want and close it. That's it! You're done!
One last bit of important information... If you allow any system update or Samsung security update to install it WILL break root. I advise everybody to disable automatic updates which is located in Settings/System update.
You can allow an update to install but you will then need to flash the beta systemless SuperSU packages located in HERE in order to regain systemless root.
Credits:@Chainfire for root and SuperSU. Without him we would not have root. Thank you!@TeamWin for TWRP recovery. http://teamw.in/project/twrp2 and here
General disclaimer:flashing anything on your device is done at your own risk. There is no way myself or any other developer can guarantee that flashing this ROM or any other file will not brick your device or otherwise cause some other type of damage. This is just a standard warning. I am not responsible for anything that you do to your device. However, all of my roms, mods, etc are pre tested by myself and other testers prior to public release.
Sprint_Stock_N910PVPS4COK1_OdexedSprint_Stock_N910PVPS4COK1_Deodexed
XDA:DevDB Information
Stock-Rooted-N910PVPS4COK1, ROM for the Sprint Samsung Galaxy Note 4
Contributors
tx_dbs_tx
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: N910PVPS4COK1
Based On: SPR-N910PVPS4COK1-20151209172046
Version Information
Status: Stable
Stable Release Date: 2015-12-15
Created 2015-12-16
Last Updated 2015-12-16
Mods & Fixes---------------------------------------------------------------------Odexed-Deodexed-N910PVPS4COK1-Hotspot-Mod (This can be flashed on odexed or deodexed OK1 roms)
N910PVPS4COK1-PrivateMode-Fix (This can be flashed on odexed or deodexed OK1 roms)
Reserved
Thanks tx. I'll take the update in the morning, and flash this. We appreciate all that you do.
Sent from my SM-N910P using Tapatalk
Nice work! Just in time!
So far so good as usual.
Interesting thing, Software OK1, Baseband OJ6, Bootloader OB7.
Thanks for this Tx. It will help the anxiety while we wait for Marshmallow. :thumbup:
Yep, didn't flash the stock tar.
Now to see about wanam xposed.
jhill110 said:
So far so good as usual.
Interesting thing, Software OK1, Baseband OJ6, Bootloader OB7.
Thanks for this Tx. It will help the anxiety while we wait for Marshmallow. :thumbup:
Yep, didn't flash the stock tar.
Now to see about wanam xposed.
Click to expand...
Click to collapse
That's interesting. You should still have the OK1 modem after flashing either of these roms because I included it in the rom zips.
tx_dbs_tx said:
That's interesting. You should still have the OK1 modem after flashing either of these roms because I included it in the rom zips.
Click to expand...
Click to collapse
I'll play with it tonight, backup and flash the stock tar. Go from there and see.
Well if you flash the OJ6 tar then take the OK1 ota update then you will definetely get the OK1 modem. No worries do as you want. I was just suprised to hear that the OK1 modem didn't stick when flashing this rom. You really should update your entire firmware, bootloader etc to latest OK1. Unles you want to run older KK and Lollipop 5.0 software.
tx_dbs_tx said:
Well if you flash the OJ6 tar then take the OK1 ota update then you will definetely get the OK1 modem. No worries do as you want. I was just suprised to hear that the OK1 modem didn't stick when flashing this rom. You really should update your entire firmware, bootloader etc to latest OK1. Unles you want to run older KK and Lollipop 5.0 software.
Click to expand...
Click to collapse
First thing in the morning. I'm all blurry eyed. ?
Thanks again Tx.
EDIT:
Flashed OK1 Tar, wiped everything, flashed this rom, restored all my apps and I picked up 9gb of internal storage. Lotta leftover junk.
Wanam xposed is working perfectly.
I rooted my daughters phone back in March and left it stock. Didn't even put TWRP. She wanted some updating... Ao I flashed back the stock tar from ANIE (which is what she had on the phone)
It downloaded 1 update. The cok1. 1.7 gb.
So that phone should be good to go...?
JohnnyEpic said:
I rooted my daughters phone back in March and left it stock. Didn't even put TWRP. She wanted some updating... Ao I flashed back the stock tar from ANIE (which is what she had on the phone)
It downloaded 1 update. The cok1. 1.7 gb.
So that phone should be good to go...?
Click to expand...
Click to collapse
Yes sir you will be good to go with this rom or any OK1 base Touchwiz rom.
I will try to start on a new custom OK1 rom soon. I gotta juggle my free time so not sure how much time i'll have to spend on it. I will have to manually redo all of the mods, etc.
Thank you, tx_dbs_tx!
I was on OJ6 when I flashed this rom and it still says that I'm on OJ6.
dbug2008 said:
I was on OJ6 when I flashed this rom and it still says that I'm on OJ6.
Click to expand...
Click to collapse
You didnt odin to the latest COK1 tar file.
Anyone else notice they patched the ability of iapps to get msl and unlock again
Sent from my 0x1 Note 4...... I love tep
I'm on your oj6 rom, my phone and pc doesn't detect sdcard but root explorer does. Is their anyway I can update to this rom without a working sdcard?
Sent from my SM-N910P using Tapatalk
allcity187 said:
I'm on your oj6 rom, my phone and pc doesn't detect sdcard but root explorer does. Is their anyway I can update to this rom without a working sdcard?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
If by detect you mean can't write to it use sdfix from the play store.
As this rom is stock without knox & itson it has the same issue with same fix.
Tx may (or not) update his rom (hybrid series) to OK1 in which case it would not be an issue.
I would suggest you Odin the stock OK1 Tar after backing up EVERYTHING including internal storage and wipe everything including internal storage. Then flash this rom.
But thats just me...
Edit.
Just reread your post...hmm pc and phone don't detect the card... Get to OK1 just the same. ..
jhill110 said:
If by detect you mean can't write to it use sdfix from the play store.
As this rom is stock without knox & itson it has the same issue with same fix.
Tx may (or not) update his rom (hybrid series) to OK1 in which case it would not be an issue.
I would suggest you Odin the stock OK1 Tar after backing up EVERYTHING including internal storage and wipe everything including internal storage. Then flash this rom.
But thats just me...
Edit.
Just reread your post...hmm pc and phone don't detect the card... Get to OK1 just the same. ..
Click to expand...
Click to collapse
I have the ok1 tar, so when I Odin to ok1, how can I install this rom without a working sdcard? Thanks for the help.
Sent from my SM-N910P using Tapatalk
kaos420 said:
Anyone else notice they patched the ability of iapps to get msl and unlock again
Sent from my 0x1 Note 4...... I love tep
Click to expand...
Click to collapse
You mean Galaxy tools? I had a hell of a time getting it to install. Ended up doing a complete wipe , flashing this rom and installing gt then restoring my apps. Took me a couple hours to figure it out. :sly:
Luv that app for easy access to hidden menu.
So the story is about 9 months ago my Galaxy note 4's USB port got messed up. I cannot charge my phone without using an external battery cradle, nor can I connect my phone to computer and sync/odin. I am stuck on a rooted BOB7 rom specifically the noterized rom stable 3. I know I cannot jump from BOB7 to COK1 etc... via flashing. I was wondering if the jump to marshmallow from lollipop would work.
Hmmm. let's see. I think you might be in a bad situation. You can't install ota updates if you're rooted and/or have a custom recovery. So those are the two biggest hurdles. You can use supersu to unroot so do that first. Next you will need to see if you can get a flashable stock OB7 recovery and flash it. Another thing that may be a problem is the debloated rom you're currently running. That may or may not cause problems with downloading and installing the ota's. I can make a flashable zip for you for the stock recovery but you first will need to download and flash my stock OB7 rom. Look for it here in the Sprint N4 forums.
Steps to success:
1. Download and flash stock rooted OB7 rom.
2. Use SuperSu app to unroot and uninstall supersu
3. Find a flashable stock OB7 recovery (I will provide if needed)
4. Do a factory reset by rebooting to the stock recovery
5. Once phone boots up, setup accounts, etc per usual and go to settings/system update and check for updates.
6. Let the update download and try to install it. You should have success. If it is successful then follow update instructions and once your phone is fully updated then you should check for updates again until you are fully updated to the latest MM 6.0 ota.
PM me if you need a flashable stock OB7 recovery or other help.
Good luck.
Thank you
Thank you very much tx_dbs_tx, you are a life saver! I have been stuck for the past 9 months.
tx_dbs_tx said:
Hmmm. let's see. I think you might be in a bad situation. You can't install ota updates if you're rooted and/or have a custom recovery. So those are the two biggest hurdles. You can use supersu to unroot so do that first. Next you will need to see if you can get a flashable stock OB7 recovery and flash it. Another thing that may be a problem is the debloated rom you're currently running. That may or may not cause problems with downloading and installing the ota's. I can make a flashable zip for you for the stock recovery but you first will need to download and flash my stock OB7 rom. Look for it here in the Sprint N4 forums.
Steps to success:
1. Download and flash stock rooted OB7 rom.
2. Use SuperSu app to unroot and uninstall supersu
3. Find a flashable stock OB7 recovery (I will provide if needed)
4. Do a factory reset by rebooting to the stock recovery
5. Once phone boots up, setup accounts, etc per usual and go to settings/system update and check for updates.
6. Let the update download and try to install it. You should have success. If it is successful then follow update instructions and once your phone is fully updated then you should check for updates again until you are fully updated to the latest MM 6.0 ota.
PM me if you need a flashable stock OB7 recovery or other help.
Good luck.
Click to expand...
Click to collapse
Is there a chance of doing the same on OG5? Using OBAR
So i am on bob7. I know a long time ago i did not uograde for a reason (dunno what that reason was now though).. so my question now is. . Is there a reason to upgrade or a reason NOT to upgrade to MM?
cheryl
Can someone confirm with me, that sending picture messages won't go through. Or is it just me?
cherylbaker said:
So i am on bob7. I know a long time ago i did not uograde for a reason (dunno what that reason was now though).. so my question now is. . Is there a reason to upgrade or a reason NOT to upgrade to MM?
cheryl
Click to expand...
Click to collapse
Sorry for the late reply Cheryl. There is no reason not to update your software to Marshmallow 6.0. Typically updates bring improved performance and battery life as well as other software optimizations which are always better than previous software builds. You should backup your photo's etc before installing any update just in case. If you're one of those who doesn't like change and is content with your phone with it's current software then you don't have to update the software as long as there isn't a critical update that would prevent something from working on your phone unless you take the update. If everything works and your happy then you can leave it as is. But if you are interested in improved battery life and overall performance as well as new security features and policies of android, then by all means update your software the first chance you get. there are no drawbacks that i have noticed or read from any other users. Marshmallow is a go! :good:
cherylbaker said:
So i am on bob7. I know a long time ago i did not uograde for a reason (dunno what that reason was now though).. so my question now is. . Is there a reason to upgrade or a reason NOT to upgrade to MM?
cheryl
Click to expand...
Click to collapse
OB7 is the newest bootloader that can be downgraded to kitkat.
on kitkat it's a lot easier to retrieve your MSL number, and at the time there was no xposed for Samsung lolly
Sterist said:
OB7 is the newest bootloader that can be downgraded to kitkat.
on kitkat it's a lot easier to retrieve your MSL number, and at the time there was no xposed for Samsung lolly
Click to expand...
Click to collapse
So that was it. You cannot downgrade to kk? I am sure at the time that was important but i havnt had any interest in downgrading b4 so doubt i will now. I know bob7 was the most popular for roms at the time also but honestly i am past my flashaholic phase and just want to havebrhe best phone i can.
Is there hot spot and root for mm? Hotspot is probably the only thing i really care about and even that isn't as important these days
cheryl
cherylbaker said:
So that was it. You cannot downgrade to kk? I am sure at the time that was important but i havnt had any interest in downgrading b4 so doubt i will now. I know bob7 was the most popular for roms at the time also but honestly i am past my flashaholic phase and just want to havebrhe best phone i can.
Is there hot spot and root for mm? Hotspot is probably the only thing i really care about and even that isn't as important these days
cheryl
Click to expand...
Click to collapse
if you don't have your MSL, and don't know where to find/how to get Galaxy Tools, and you still have a while left on contract, it wouldn't hurt to downgrade and grab your MSL first then jump straight to MM
Does anyone have a link to a stock OB7 recovery? All that I find are the odin variants.
kjtrini1 said:
Does anyone have a link to a stock OB7 recovery? All that I find are the odin variants.
Click to expand...
Click to collapse
I don't know how to extract it from a .tar but I know it can be acquired it like this:
1. full backup in TWRP
2. copy the backup to pc for safekeeping
3. odin full OB7 stock tar
4. without flashing TWRP, root using CF auto root*
5. install Flashify from Google Play
6. backup recovery
7. copy the backup to pc for uploading
*I don't know which version (if applicable) as I never use that method to root. sorry
obviously you wouldn't be able to do this yourself, you would need someone on the forum with OB7 bootloader to do this, and honestly, without knowing how to extract / find it in the.tar I still think that would take a lot less time and effort than this method lol
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
I've searched everywhere and can't seem to find a tar for PK1 can anyone tell me if there is one yet or are we still waiting on a tar? Sorry I usually don't ask questions but this one has me scratching my head lol
Sent from my SM-N910P using XDA-Developers mobile app
Still waiting it looks like,
You can always download the update and rip it from the phone and use android kitchen to make your own zip file of the tar
Invisibility said:
I've searched everywhere and can't seem to find a tar for PK1 can anyone tell me if there is one yet or are we still waiting on a tar? Sorry I usually don't ask questions but this one has me scratching my head lol
Sent from my SM-N910P using XDA-Developers mobile app
Click to expand...
Click to collapse
According to sammobile PK1 is not yet available
Though other variants have it
See more here: http://www.sammobile.com/devices/specs/SM-N910P/
Mr nerd said:
Still waiting it looks like,
You can always download the update and rip it from the phone and use android kitchen to make your own zip file of the tar
Click to expand...
Click to collapse
I want to know how to do it?
In PG1 I grabbed the update zip but I didn't know what to do with it.
anees02 said:
I want to know how to do it?
In PG1 I grabbed the update zip but I didn't know what to do with it.
Click to expand...
Click to collapse
I was able to get the pk1 update over ota
I downloaded the pj1 tar and then used oden to flash to my phone after, i didnt lose anything but backup just in case after i flashed i just took the ota update.
Then i re rooted. Using chain fire and teamwin
Mr nerd said:
I was able to get the pk1 update over ota
I downloaded the pj1 tar and then used oden to flash to my phone after, i didnt lose anything but backup just in case after i flashed i just took the ota update.
Then i re rooted. Using chain fire and teamwin
Click to expand...
Click to collapse
I mean how to convert update.zip to a flashable file either from odin or recovery or at least how to make a full tar file to flash via odin instead of downloading a large tar file.
Assume that you want to take OTA update and you successfully update your phone to the latest version then you want to make a full tar file to give it to your friend or to use it for emergency cases instead of downloading the full tar again from internet and losing your balance in download process.
You can't make a tar
But you can take a tar and make an update.zip either way they will be the same size
the only way to get the full tar is to download it when it is released
but you can take the update from the OTA if you full restore from tar of pj1 to pk1 then use that to update via recovery but youll need to be stock the OTA update zip files have file checking so it will fail if youre not stock
if you do get it PM me the link to the update.zip file I'll remove the integrity check so you can update on a rooted device
Sent from my SM-N910P using Tapatalk
I took the new update pk1 and its seems that twrp wont flash using odin on this anybody else have that problem thanks
update I odin back to pe2 and odin twrp without a problem so not sure if pk1 is user friendly or im just having problems
sliverr7x said:
I took the new update pk1 and its seems that twrp wont flash using odin on this anybody else have that problem thanks
update I odin back to pe2 and odin twrp without a problem so not sure if pk1 is user friendly or im just having problems
Click to expand...
Click to collapse
I took ota upadte to PK1 odin twrp fine.. rooted systemless.. on dr k m6 rom
I have PK1, what is the best rooted rom to use with this?
What rooted rom can i download for the note 7?
Thanks
bump...
joetarney said:
I have PK1, what is the best rooted rom to use with this?
What rooted rom can i download for the note 7?
Thanks
Click to expand...
Click to collapse
The Note7 port for Sprint by @tx_dbs_tx is currently targeting PJ1 for compatibility.
As for current suggested ROM, I believe that's subjective for now. These security updates tend to release faster than developers can port features and compatibility, IMO.
You may consider rooting PK1 or downgrading to PJ1 and rooting that for now. I can't give an ETA for the ported Note7. Other ports require additional reading, shared files and workarounds and individual effort for data and compatibility reasons. Reason is, these ROMs may also be beta and improving but also don't support Sprint's unique network.
The ROM you're asking about is in alpha or beta stages of development. tx_dbs_tx may release it in it's early alpha or beta if he feels it's stable enough for most users. Be patient; I think it'll happen soon enough.
Sent from my SM-N930P using Tapatalk
Thanks, i had the Note 5 rom but it started to act funny so i odined back to stock and took a couple of updates to PK1. All i need or want is root and Tether, what would you suggest i flash or Odin to get that being i am on PK1?
joetarney said:
Thanks, i had the Note 5 rom but it started to act funny so i odined back to stock and took a couple of updates to PK1. All i need or want is root and Tether, what would you suggest i flash or Odin to get that being i am on PK1?
Click to expand...
Click to collapse
I haven't seen a stock modified services.jar for updates after PH4. For tether, try the non modified approach in general forum. I think you have to reset that after each reboot?
For which to root and modify, I'd suggest PJ1 since that's where development is currently focused. Don't hold me to it but it appears there may not be a lot development for PK1 and up. (At least for now... that appears to be the case.)
Make a stock backup of PJ1 stock unmodified once you Odin TWRP for a possible starting point for the Note7 port install from OP instructions if it happens soon enough. That may save you a trip to Odin later as long as your bootloader and baseband remain PJ1. Just restore that instead. I recommend doing the backup before root, user applications and Google Play or Samsung updates are applied. The less of these, the better the backup for starting point is. All it would need is the completion of the setup wizard to backup with TWRP. Backup to extSdCard for safe keeping.
After TWRP backup, you can modify as needed to get by until then. Make another backup before flashing any other ROM or major mod to save time on customization duplication of effort if you should make a mistake. I prefer to keep both stock and preferred modified version of update on hand for the occasional oops or major mod trials that don't go as expected. Doesn't matter if making several backups of current ROM but I delete the ones that aren't current or relative to immediate backup restore intentions for such occasions. You never really appreciate timely application backups in titanium or helium and TWRP backups until it matters. They can save restoration time and make you feel good about the habit.
Sent from my SM-N930P using Tapatalk
It's always best to downloaded it from Samsung. I used unroot to get it but now some great guys have made it so you can again change you're status to official like you could on kitkat. Wanam Xposed and firefds work great. The first ROM in the note 4 sprint has been the dtux mod for a minute. Theirs aroma installer is quite awesome. I'm looking at am official status and I'm quite customized.
Sent from my SM-N910P using Tapatalk
I was rooted on OB7 with chainfire and the stock recovery image or whatever, it's been several years, well I used superSU and unrooted the phone and it still wouldn't let me do OTA. So tonight I downloaded the OF5 Rom and updated through Odin, Now it's telling me my device status is official and it's currently downloading the next update... The issue I am wondering about now is... Since it will OTA, I want to put UN7 on my phone and I don't want to update past PJ1, will it let me stop the updates?
Curtai said:
I was rooted on OB7 with chainfire and the stock recovery image or whatever, it's been several years, well I used superSU and unrooted the phone and it still wouldn't let me do OTA. So tonight I downloaded the OF5 Rom and updated through Odin, Now it's telling me my device status is official and it's currently downloading the next update... The issue I am wondering about now is... Since it will OTA, I want to put UN7 on my phone and I don't want to update past PJ1, will it let me stop the updates?
Click to expand...
Click to collapse
You got some OTA updates to go to get to PJ1 but there's a better way. You could get the PJ1 stock tar from the stock tar thread in general forum and upgrade through Odin again.
OTA is sequential patch updates. Stock tar is full updates. I'd recommend factory reset before flashing the marshmallow update to save time on initial boot optimization.
To answer your question about stopping the updates, turn off auto update feature in Settings when you get to PJ1. Follow the ROM OP to install once you get to PJ1- however you choose.
Note: Since your bootloader is now updated beyond OB7, keep in mind you cannot use Odin to flash full tars OB7 or lower. You cannot downgrade the bootloader but it's still possible to run older ROMs. I only recommend full stock tars no older than OG5.
Sent from my SM-N920P using Tapatalk
samep said:
You got some OTA updates to go to get to PJ1 but there's a better way. You could get the PJ1 stock tar from the stock tar thread in general forum and upgrade through Odin again.
OTA is sequential patch updates. Stock tar is full updates. I'd recommend factory reset before flashing the marshmallow update to save time on initial boot optimization.
To answer your question about stopping the updates, turn off auto update feature in Settings when you get to PJ1. Follow the ROM OP to install once you get to PJ1- however you choose.
Note: Since your bootloader is now updated beyond OB7, keep in mind you cannot use Odin to flash full tars OB7 or lower. You cannot downgrade the bootloader but it's still possible to run older ROMs. I only recommend full stock tars no older than OG5.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
So, now I am on PJ1 and I don't know how to put TWRP on my phone, I want to put tx_dbs_tx's UN7 hybrid on my phone and I am having issues both finding and putting TWRP on my phone... and I can't find a download or anything for it...
I've downloaded 2 different versions of twrp and used odin to put them on but I think I am doing something wrong because it isn't booting into twrp
Curtai said:
I was rooted on OB7 with chainfire and the stock recovery image or whatever, it's been several years, well I used superSU and unrooted the phone and it still wouldn't let me do OTA. So tonight I downloaded the OF5 Rom and updated through Odin, Now it's telling me my device status is official and it's currently downloading the next update... The issue I am wondering about now is... Since it will OTA, I want to put UN7 on my phone and I don't want to update past PJ1, will it let me stop the updates?
Click to expand...
Click to collapse
and of course I was missing a step... nobody said uncheck auto reboot and it kept keeping the bootloader locked
got it done now and I managed to get the custom rom installed... or at least I think it's working
Curtai said:
and of course I was missing a step... nobody said uncheck auto reboot and it kept keeping the bootloader locked
got it done now and I managed to get the custom rom installed... or at least I think it's working
Click to expand...
Click to collapse
Oh your talking about installing twrp? Yeah you have to not let it reboot. And when is done pull battery and boot into recovery to get it to stick. Obviously you figured it out. But just saying. I think earlier versions you didn't need to do that but now you do.
Glad you got it going. How you like the Rom? Running smooth for me.
ROM is good
Well I obviously got it going and didn't read the first couple posts after the install and didn't notice the SMS issue so I had that problem and I can't find a lot of the menu options that I had with the OB7 original I've been running for about 18 months... It's pretty smooth now and I'm wondering how fast it will fill up my internal memory I like that it's almost 20 gigs free.. for a while I was running on less than 6 I need to find an efficient way to use my external SD card... Other than that the options are neat but it seems really bloated all the extra Google apps make me sick even though I never use them... I've got titanium backup and am freezing them and will probably uninstall them soon... I want a small ROM that I can customize myself or apps that are easily removed or whatever half the apps I don't want are in ROM which is a pain to remove or I just don't know how to unless I use TB
Wow that's a novel sorry but yeah that's my ramblings for the next week I guess... Now I'm gonna hit the rack...