Develop Bugs

[ROM] [ODIN] [HYBRID_OB7sbl_SPT_N910PVPU4COG5] [8/10/15]

I made this custom OG5 rom package for myself and I wanted to share it with those of you who want to stay on your older OB7 bootloader and be fully updated to Android 5.1 OG5. There is absolutely nothing changed from the stock rom/partitions except for the bootloader. This rom includes knox, itson, etc just like the official rom tar does. This simply gets you updated properly so you can proceed to root, flash recovery, flash rooted kernel, SuperSU, etc... and keep your unlocked OB7 bootloader. Please Note: If you have already taken either the OE1. OF5 or OG5 Android 5.1 ota update or odin flashed one of these official Samsung ROM rom tars, then you will not be able to go back to an older bootloader and this package will most likely not work for you. For the rest of us who where patient and who want to properly update to 5.1 and keep our unlocked OB7 bootloader then please keep reading.
The point of this odin package is very simple. Unless you flash the official 5.1 OG5 rom tar or take the 5.1 ota update from your phone then you will not be able to fully update to 5.1 the way it needs to be done. There are device partitions other than "system" and "cache" that must be written/overwritten with updated img.ext4's. Without extracting and comparing the img's there's no way to know what differences there are between the new 5.1 and the older softwares. So it goes without saying that it would be a wise choice to make sure your device has all of these carrier partitions etc updated for piece of mind. Again, I did this for my own personal use and not because I was bored. I want to share this with those of you who can benefit from it. So let's get started with the details/Instructions.
If you understand what the purpose of this odin package is then proceed: If not then do your homework or leave your phone alone. Here are the simple steps to fully update to 5.1 and retain the OB7 bootloader.
1. Install and use Odin 3.10.6
2. download and install 7zip
3. download and extract this OG5 odin rom package in a location of your choice. (VERIFY THE MD5 BEFORE YOU EXTRACT!!!)
4. Wipe your phone in your current TWRP or do a factory data reset in the stock bootloader. or proceed without wiping your partitions. (this can result in leftover data and cause issues so wipe if at all possible for a good clean slate).
5. Reboot your phone into download mode. (With phone turned of, press and hold the home, volume down and power button until the phone boots).
6. Open Odin 3.10.6 THEN connect your phone via USB and wait for it to connect.
Leave all defaults as they are and then press the big "AP" button to select the odin package you want to flash then press start. Wait for it to finish and it will let you know when all items flashed successfully. Unplug your usb and wait for first boot.
7. Setup your device as usual. Done.
You are now fully upgraded to Android 5.1 (OG5) with all partitions correctly written to your phone as per the OG5 update.
Download​HYBRID_OB7sbl_SPT_N910PVPU4COG5​

Thank you!
Out of curiosity are there plans for a deodexed version?
Sent from my SM-N910P using XDA Free mobile app

@tx_dbs_tx
Firstly I'm still on the OB7 Bootloader. I've upgraded to 5.1.1 using freezas OG5 Baseband flash & OG5 zip. Currently I am able to restore via TWRP Recovery to OG5 or Alliance (OB7) at will with no apparent problems. Now my question:
You've made reference to partitions that should be created to properly install OG5. Once this is done (you saying it needs doing is good enough for me btw) and I nand backup in TWRP can I then expect to have issues restoring an OB7 ROM from an OG5 ROM or vice-versa or will these changes be contained within the backups?
Again cannot thank you enough for all you've done for us.

thearch1tect said:
Thank you!
Out of curiosity are there plans for a deodexed version?
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
That's out of the scope of this odin package. The sole purpose for this hybrid rom tar is to properly upgrade to 5.1 without being forced upon the new secure bootloaders. After you flash this tar you can proceed to root, flash roms, kernels, etc with confidence knowing that all of your partitions have been properly updated. Any other means of going to 5.1 without updating these partitions is not a complete upgrade to 5.1. So if you want a deodexed/custom 5.1 rom you'll have to wait for some of us to build them. But in the meantime you really should flash this and get this out of the way while you're waiting for new 5.1 roms, mods, kernels, etc.
kenjesse said:
@tx_dbs_tx
Firstly I'm still on the OB7 Bootloader. I've upgraded to 5.1.1 using freezas OG5 Baseband flash & OG5 zip. Currently I am able to restore via TWRP Recovery to OG5 or Alliance (OB7) at will with no apparent problems. Now my question:
You've made reference to partitions that should be created to properly install OG5. Once this is done (you saying it needs doing is good enough for me btw) and I nand backup in TWRP can I then expect to have issues restoring an OB7 ROM from an OG5 ROM or vice-versa or will these changes be contained within the backups?
Again cannot thank you enough for all you've done for us.
Click to expand...
Click to collapse
You will have no problem flashing back and forth between roms after flashing this odin package. It will retain your OB7 bootloader and update ALL of your partitions. You will then be completely stock unrooted OG5 with the exception of having the OB7 bootloader. From there you can restore a nandroid, flash a OB7/OG5 rom, etc.

That makes sense.
Im currently running hybrid x 1.07 with NK2 bootloader. Do I need to first upgrade the bootloaderto OB7 or does this package include the OB7 bootloader?
Sent from my SM-N910P using XDA Free mobile app

thearch1tect said:
That makes sense.
Im currently running hybrid x 1.07 with NK2 bootloader. Do I need to first upgrade the bootloaderto OB7 or does this package include the OB7 bootloader?
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
Yes. This package includes the OB7 bootloader. It will replace your NK2 bootloader but if I'm not mistaken you would still be able to odin an older NK2 tar and go back to that bootloader... not that it really makes any difference. I would say that the OB7 bootloader is what you want to go with since it's more current and still unlocked. However, If you're happy with your current setup then you can just wait for the custom OG5 roms to come out and decide then if you want to flash another rom.

tx_dbs_tx said:
Yes. This package includes the OB7 bootloader. It will replace your NK2 bootloader but if I'm not mistaken you would still be able to odin an older NK2 tar and go back to that bootloader... not that it really makes any difference. I would say that the OB7 bootloader is what you want to go with since it's more current and still unlocked. However, If you're happy with your current setup then you can just wait for the custom OG5 roms to come out and decide then if you want to flash another rom.
Click to expand...
Click to collapse
Failed for me....
Edit i dont kow why the pic is sideways

Failed for me as well

I'd like to flash this rom for the reasons you named but I am on the OF5 bootloader which is also unlocked since I used CF root to root it. Question : would you do a version of this rom including the OF5 bootloader or one that would use the bootloader already installed on the note?

To the guys it failed for:
were you coming off of an OB7 bootloader or something else? I'm guessing some bootloader other OB7.

flyhighx said:
To the guys it failed for:
were you coming off of an OB7 bootloader or something else? I'm guessing some bootloader other OB7.
Click to expand...
Click to collapse
Im on ob7 bootloader... but i did flash the og5 modem and freezas rom... just wanted to do this cause he said we missed somethings with update just flashing modem...

Since this TAR has led to confusion -- I wanted to state that I am on OB7 bootloader, and the TAR worked perfectly for me.

I'm also on OB7 bootloader and had flashed OF5 bits to use another rom. This worked perfect, now on freeza's stockish.

I flashed this last night when you first posted it in your Hybrid X thread, I was on OB7 running 2.3
I Odined all the way back to NK2 then flashed OB7 again, then this one, I flashed TWRP and Freeza's Kernel then installed Super SU from playstore and I'm not having any issues whatsoever, it runs very smooth (seems like they did a good job with this update)
I'm patiently waiting for you to make a new OG5 Hybrid X rom, I didn't want to flash Freeza's rom cause I've noticed there's a few bugs and issues.
And since it's stockish I see no point of doing so until there's new OG5 roms.
Thank You Sir!! :good::good:

Just to be clear for me. After updating to this ROM, can u root it? Or do we have to wait for something other than CF Root? All my apps are backed up and no way to restore just yet, thx
Disregard, installed TWRP, then flashed Freeza Mod Kernal and SU.

twynn said:
I'd like to flash this rom for the reasons you named but I am on the OF5 bootloader which is also unlocked since I used CF root to root it. Question : would you do a version of this rom including the OF5 bootloader or one that would use the bootloader already installed on the note?
Click to expand...
Click to collapse
Sorry I have no plans to build an OF5 bootloader version. If I'm not mistaken the bootloaders starting with OE1 cant be downgraded to previous versions. Hence making it pointless to build an OF5 version. Correct me if I'm wrong.
xyojimbox said:
Failed for me....
Edit i dont kow why the pic is sideways
Click to expand...
Click to collapse
.
whiteyman24 said:
Failed for me as well
Click to expand...
Click to collapse
If it failed then you're on a newer bootloader than OB7. This package was made specifically for those of us who waited and didn't update our OB7 bootloaders. Any newer bootloader will most likely fail. In that case you might as well odin the official OG5 rom tar.
flyhighx said:
To the guys it failed for:
were you coming off of an OB7 bootloader or something else? I'm guessing some bootloader other OB7.
Click to expand...
Click to collapse
Exactly.
kbrn said:
I flashed this last night when you first posted it in your Hybrid X thread, I was on OB7 running 2.3
I Odined all the way back to NK2 then flashed OB7 again, then this one, I flashed TWRP and Freeza's Kernel then installed Super SU from playstore and I'm not having any issues whatsoever, it runs very smooth (seems like they did a good job with this update)
I'm patiently waiting for you to make a new OG5 Hybrid X rom, I didn't want to flash Freeza's rom cause I've noticed there's a few bugs and issues.
And since it's stockish I see no point of doing so until there's new OG5 roms.
Thank You Sir!! :good::good:
Click to expand...
Click to collapse
Thats exactly how you do it. Thanks for sharing your feedback.

tx_dbs_tx said:
Sorry I have no plans to build an OF5 bootloader version. If I'm not mistaken the bootloaders starting with OE1 cant be downgraded to previous versions. Hence making it pointless to build an OF5 version. Correct me if I'm wrong.
.
If it failed then you're on a newer bootloader than OB7. This package was made specifically for those of us who waited and didn't update our OB7 bootloaders. Any newer bootloader will most likely fail. In that case you might as well odin the official OG5 rom tar.
Exactly.
Thats exactly how you do it. Thanks for sharing your feedback.
Click to expand...
Click to collapse
I am pretty sure I'm on ob7 bootloader cause I just flashed the of5 baseband I didn't take Ota and didn't mess with oe1 either....

tx_dbs_tx said:
Sorry I have no plans to build an OF5 bootloader version. If I'm not mistaken the bootloaders starting with OE1 cant be downgraded to previous versions. Hence making it pointless to build an OF5 version. Correct me if I'm wrong.
.
If it failed then you're on a newer bootloader than OB7. This package was made specifically for those of us who waited and didn't update our OB7 bootloaders. Any newer bootloader will most likely fail. In that case you might as well odin the official OG5 rom tar.
Exactly.
Thats exactly how you do it. Thanks for sharing your feedback.
Click to expand...
Click to collapse
If you mean the bootloader is locked on OF5 I don't see how it could be since I rooted OF5 with CF Root. I think it's not possible to do that if the bootloader is locked

twynn said:
If you mean the bootloader is locked on OF5 I don't see how it could be since I rooted OF5 with CF Root. I think it's not possible to do that if the bootloader is locked
Click to expand...
Click to collapse
It doesn't matter if bootloader is locked I believe. You can still root but you can't downgrade with any tar if bootloader is locked.

I thought sprint never locked the bootloader?

Rooted 5.0.1 to 5.1.1 Custom Rom

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

Just got note 4 still on KITKAT

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 Restrictions​All 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 Restrictions​All 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.

Odin (fail! auth) Note 4 SM-N910P

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

So I was rooted and had a custom recovery...

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...