I recently tried to root my phone using CF Auto Root and its now stuck in boot loop. The phone is a sm-n910p running 5.1.1. Is there anything I can do to fix it? I have been trying to use stock roms but they either fail in odin or they cause odin to freeze up without doing anything. The only error I can see is SW Rev check fail fused 4 binary 1
Thuganomics said:
I recently tried to root my phone using CF Auto Root and its now stuck in boot loop. The phone is a sm-n910p running 5.1.1. Is there anything I can do to fix it? I have been trying to use stock roms but they either fail in odin or they cause odin to freeze up without doing anything. The only error I can see is SW Rev check fail fused 4 binary 1
Click to expand...
Click to collapse
Stock ROMs getting flashed in Odin? Stock tars full and partitions from tar ball or custom recovery is all you should flash with Odin.
If you're trying to flash custom OG5 ROMs, that would require TWRP or CWM recovery flashed in Odin.
CF Auto Root was suggested until Android 5.1.1/OG5 update. Root now requires kernel exploit like Beastmode kernel by freeza plus SuperSU zip to root stock flashed in custom recovery.
Odin to flash custom recovery would be a prerequisite for rooting stock with those zips or custom ROM zip.
http://forum.xda-developers.com/showpost.php?p=62241991&postcount=56
Custom OG5 ROMs only require custom recovery to flash because they're pre-rooted with those during flash.
Sent from my SM-N910P using Tapatalk
samep said:
Stock ROMs getting flashed in Odin? Stock tars full and partitions from tar ball or custom recovery is all you should flash with Odin.
If you're trying to flash custom OG5 ROMs, that would require TWRP or CWM recovery flashed in Odin.
CF Auto Root was suggested until Android 5.1.1/OG5 update. Root now requires kernel exploit like Beastmode kernel by freeza plus SuperSU zip to root stock flashed in custom recovery.
Odin would be a prerequisite for rooting stock with those zips or custom ROM zip.
Custom OG5 ROMs only require custom recovery to flash because they're pre-rooted with those during flash.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I was able to flash the TWRP 2.8.1.1 and im able to access the menu in recovery mode however I still get stuck on the boot loop with no kernel even though I had one on the phone before starting the process
Have you flashed the Beastmode kernel and SuperSU zip linked in the post I linked you to above? Are you getting a message indicating no kernel installed? A ROM flash or those zips would get a kernel onboard.
If you're stuck, just try OBAR ROM on a clean install. You can find it in development forum.
Sent from my SM-N910P using Tapatalk
I was able to do a complete reinstall after a few hours of stock rom and it seems ok as of right now still back on 5.1.1. How do I root it but still keep everything as close to stock as possible?
And yes i have checked out the beastmode however the link is down.
Thuganomics said:
I was able to do a complete reinstall after a few hours of stock rom and it seems ok as of right now still back on 5.1.1. How do I root it but still keep everything as close to stock as possible?
And yes i have checked out the beastmode however the link is down.
Click to expand...
Click to collapse
The link is live in the post above. Scroll down to where SuperSU zip is linked as well. Flash both those in TWRP recovery.
You'll still need to freeze or remove Knox. There's some other notes that apply to stock in that post, like the build.prop edit.
Sent from my SM-N910P using Tapatalk
Thuganomics said:
I was able to do a complete reinstall after a few hours of stock rom and it seems ok as of right now still back on 5.1.1. How do I root it but still keep everything as close to stock as possible?
And yes i have checked out the beastmode however the link is down.
Click to expand...
Click to collapse
@tx_dbs_tx has 2 stock, prerooted, odexed & deodexed roms. They are completely stock excepting Knox & sprint itson and as I said are prerooted.
If that sounds like what you are looking for here is the link :
http://forum.xda-developers.com/showthread.php?t=3185274
These roms are flashed in recovery.
jhill110 said:
@tx_dbs_tx has 2 stock, prerooted, odexed & deodexed roms. They are completely stock excepting Knox & sprint itson and as I said are prerooted.
If that sounds like what you are looking for here is the link :
http://forum.xda-developers.com/showthread.php?t=3185274
These roms are flashed in recovery.
Click to expand...
Click to collapse
Thanks..i was able to get twrp 2.8.7.0 loaded on and the beastmode kernel..however the phone seems to be draining battery extremely fast even with my zerolemon extended battery..in about 5 hours I'd normally go from 90-80% with average usage where as today I barely used it and it dropped from 65-20%. If I'm trying to remain as close to stock as possible but just have root permissions with the bloatware removed which one would I want the odexed or deodexed? Do i have to flash the ALL_SPT_N910PVPU4COG5_N910PSPT4COG5_CL5303209_QB56 91107_REV00_user_low_ship_MULTI_CERT.tar.md5 before flashing one of those?
Thuganomics said:
Thanks..i was able to get twrp 2.8.7.0 loaded on and the beastmode kernel..however the phone seems to be draining battery extremely fast even with my zerolemon extended battery..in about 5 hours I'd normally go from 90-80% with average usage where as today I barely used it and it dropped from 65-20%. If I'm trying to remain as close to stock as possible but just have root permissions with the bloatware removed which one would I want the odexed or deodexed? Do i have to flash the ALL_SPT_N910PVPU4COG5_N910PSPT4COG5_CL5303209_QB56 91107_REV00_user_low_ship_MULTI_CERT.tar.md5 before flashing one of those?
Click to expand...
Click to collapse
Odexed is better for performance, deodexed is a better choice for moding. I always use deodexed as the performance of this device is outstanding.
As for the battery issues, I use GSam battery monitor (there are many others). It helps you see what is using up battery.
Go through the system settings and turn off things that aren't necessary for you. Many of them contribute to battery drain. It's a drip, drip, drip thing... Not any one thing. A process of learning what helps and what doesn't. There's no catch all answer... You've got to work at it.
Related
I may trade some one for this phone. It has the 4.3 update on it already. Can I flash a custom recovery of I don't care if Knox gets tripped or can a recovery not be flashed at all?
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
re: recovery
SkizzMcNizz said:
I may trade some one for this phone. It has the 4.3 update on it already. Can I flash a custom recovery of I don't care if Knox gets tripped or can a recovery not be flashed at all?
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sure you can, you can flash either TWRP or CWM recovery, but you need to ROOT
the phone first. Without root you cannot do much of anything except download/install
apps and games from the google play store.
Good luck!
Misterjunky said:
Sure you can, you can flash either TWRP or CWM recovery, but you need to ROOT
the phone first. Without root you cannot do much of anything except download/install
apps and games from the google play store.
Good luck!
Click to expand...
Click to collapse
I think you can still direct flash a recovery in Odin on the 4.3 firmware, can't you?
I dont' know for sure as I never tried it. But if you can still flash CF-Auto Root in Odin I'd imagine you could flash TWRP or CWM in Odin too. All CF Auto Root does is install a recovery to flash SuperUser, so I'm pretty sure you can direct flash any other Recovery.
If you are looking to flash custom ROMs this is the faster way because it eliminates a step. If you just want the stock ROM with root access, then you may as well just CF Auto Root it (which will trip the knox flag) and install a recovery later.
I have 4.3 and have tripped KNOX. I downloaded the 4.3 stock tar and tried to flash it with Odin and it just fails. The only way to get my phone to boot again is to flash TWRP with Odin and then it boot up into my 4.3 rom I installed via TWRP.
Any way to get the stock 4.3 onto the phone again?
Thanks
re: recovery/knox
I have been meaning to ask this question for about 4 days now...
Actually I was waiting for someone else to ask this question...
Why is it that on MDL 4.2.2 roms I can see all the options in the screen shot below when long pressing
a contacts names so I can edit their phone numbers and details plus a lot of other options.
Here is a screenshot of MDL 4.2.2 contact screen after long pressing contact name:
When I long press a contact name using the MK2 4.3 stock/semi stock roms I
don't even see "edit", there are only perhaps 4 options to choose from when I
long press contact names.
I have flashed 3-4 of these MK2 4.3 cwm/twrp zip file roms and they also have the
same issue. (perhaps I am really over looking something?)
Thanks!
Thank you for taking time out of your day to help.
I just got an s4 on tmobile and I have some questions. I tried rooting it and ran into an error. I found an answer online, which was to flash a stock 4.3 rom via odin, then try the CFT autoroot. So it's all good and I'm rooted. I just have some questions:
1. Why was I able to flash a rom via odin, when all the rom installation guides I see require a CWM or some other recovery?
2. When I try to boot up into recovery I think it's the stock recovery and not a custom recovery that allows me to install a zip. When I used CFT auto root, I saw it booted into a custom recovery to root, did it just get deleted after that?
3. How will my root work with the 4.4 ota? When I check for software updates it says my phone has been modified so they aren't available. So how can I get the ota? Am i better off flashing a custom 4.4 rom? I want closest to stock as possible, so if you have any recommendations for stock 4.4 roms that would be great. Or can I flash the 4.4 stock rom as I did with odin?
4. How does tethering work with root? If I have unlimited data with 2.5gb tethering data, now that I'm rooted, can tmobile tell I'm tethering if I'm using a root tethering app?
Again thank you very much for your help.
1. You did not flash a ROM with Odin, it was firmware.. Very different
2. Yes, I believe that's what cf-auto root does
3. Yes you can flash a 4.4 firmware like you did with 4.3 as long as its for your device, or flash a custom recovery and then a 4.4 ROM
4. Not too familiar with this, but it might be possible to get around it
Sent from my SGH-M919 using Tapatalk
serio22 said:
1. You did not flash a ROM with Odin, it was firmware.. Very different
2. Yes, I believe that's what cf-auto root does
3. Yes you can flash a 4.4 firmware like you did with 4.3 as long as its for your device, or flash a custom recovery and then a 4.4 ROM
4. Not too familiar with this, but it might be possible to get around it
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Awesome thank you. If I flash the official 4.4 firmware for my device, will I keep my root?
gregorina said:
Awesome thank you. If I flash the official 4.4 firmware for my device, will I keep my root?
Click to expand...
Click to collapse
No if it is an untouched fully stock rom/firmware but there will be rooted versions of the stock firmware/rom.
Stay with root, you will be better off, custom roms are usually available within a day after ota updates
Sent from my customizable brickable device
Hi everyone.
Is there any way to root the Note 2 N7100 on Samsung official firmware Kitkat without tripping Knox. ??
My bootloader is ND4
My baseband is ND3
My PDA is ND4
If there is a safe method, what is it ...
I tried TR but got that my device is not supported.
My Knox is 0x0
If there isn't & I must trip Knox to root, so what's the best & safest method for rooting my N7100?? My warranty is gone long time ago anyway.
And if I'm gonna trip Knox so I prefer to have a custom recovery, what should I use? I thought of TWRP but found some complaining that 2.8.6 caused loss of signal... What should I use??
One more question, please.
Will rooting my phone & tripping Knox prevent future OTA update to the long awaited official Samsung Lollipop??
If the answer is yes is there a way around it ?? Will I be able to flash it by Odin after getting it from any where like Sammobile ?
Sorry for being long & Thanks
zoghrob said:
Hi everyone.
Is there any way to root the Note 2 N7100 on Samsung official firmware Kitkat without tripping Knox. ??
My bootloader is ND4
My baseband is ND3
My PDA is ND4
If there is a safe method, what is it ...
I tried TR but got that my device is not supported.
My Knox is 0x0
If there isn't & I must trip Knox to root, so what's the best & safest method for rooting my N7100?? My warranty is gone long time ago anyway.
And if I'm gonna trip Knox so I prefer to have a custom recovery, what should I use? I thought of TWRP but found some complaining that 2.8.6 caused loss of signal... What should I use??
One more question, please.
Will rooting my phone & tripping Knox prevent future OTA update to the long awaited official Samsung Lollipop??
If the answer is yes is there a way around it ?? Will I be able to flash it by Odin after getting it from any where like Sammobile ?
Sorry for being long & Thanks
Click to expand...
Click to collapse
Just root it as posted in sticky thread.
You don't have warranty, so just don't bother. Use odin, root and install recovery, then rom.
You can flash stock rom via odin if you want, you can install custom roms via recovery.
I'm using TWRP for 2 years and never had any problem. You can also use Philz. For normal user it doesn't really matter.
yaro666 said:
Just root it as posted in sticky thread.
You don't have warranty, so just don't bother. Use odin, root and install recovery, then rom.
You can flash stock rom via odin if you want, you can install custom roms via recovery.
I'm using TWRP for 2 years and never had any problem. You can also use Philz. For normal user it doesn't really matter.
Click to expand...
Click to collapse
Thank you very much for your help.
Actually I found no sticky threads for rooting 4.4.2. Most of the sticky threads are dating since 2012 with 4.1.2 & 4.3.
However by searching I found 2 threads for 4.4.2, one of them is
http://forum.xda-developers.com/showthread.php?t=2767604
This one uses CF-auto-root... but no mention about any custom recovery. Will I lose root or mess things up if I install TWRP after that??
The other thread is
http://forum.xda-developers.com/showthread.php?t=2730764
This one uses the typical steps that I know, custom recovery then SuperSU. But it uses Philz recovery. Can I substitute it with TWRP??
Thank you for your help & patience.
The most important question: Why do you want to root?
If you like to flash a custom rom no need for root, any custom recovery - TWRP or CWM - flashed with Odin will do.
Androidwizzard said:
The most important question: Why do you want to root?
If you like to flash a custom rom no need for root, any custom recovery - TWRP or CWM - flashed with Odin will do.
Click to expand...
Click to collapse
I'm not planning to flash custom rom right now, may be later.
I want to root to be able to use some apps that require root. Plus, having full control over my phone.
In odin you have option to choose recovery file - AP.
After flashing recovery just install superSU via recovery.
DO a backup of your device and EFS before you flash anything.
yaro666 said:
In odin you have option to choose recovery file - AP.
After flashing recovery just install superSU via recovery.
DO a backup of your device and EFS before you flash anything.
Click to expand...
Click to collapse
Thank you for your help.
I don't know how to make a backup without recovery. So I flashed TWRP 2.8.6, took a backup then installed SuperSU via TWRP.
All went well except that I lost the signal and IMEI.
I found that I flashed TWRP t03gup while I should flashed t03g.
I reflashed the correct file then flashed the modem.bin of XXUFND3.
Everything thing is back to normal again except 2 things:
The icon of my service provider shifts place to the last app page after reboot, no matter where I place it...
The phone status shows custom (expected) but stays so even after using Triangle Away.
Is it better if I flash the stock firmware then recovery then SuperSU? ?? Or flashing the modem as I did was enough to straighten things up? ?
Thank you for your patience and help.
zoghrob said:
Thank you for your help.
I don't know how to make a backup without recovery. So I flashed TWRP 2.8.6, took a backup then installed SuperSU via TWRP.
All went well except that I lost the signal and IMEI.
I found that I flashed TWRP t03gup while I should flashed t03g.
I reflashed the correct file then flashed the modem.bin of XXUFND3.
Everything thing is back to normal again except 2 things:
The icon of my service provider shifts place to the last app page after reboot, no matter where I place it...
The phone status shows custom (expected) but stays so even after using Triangle Away.
Is it better if I flash the stock firmware then recovery then SuperSU? ?? Or flashing the modem as I did was enough to straighten things up? ?
Thank you for your patience and help.
Click to expand...
Click to collapse
It should be OK just as it is now, but if you have 30min free time, you can flash stock, root, custom rom with full wipe to make sure you have everything straighten up
yaro666 said:
It should be OK just as it is now, but if you have 30min free time, you can flash stock, root, custom rom with full wipe to make sure you have everything straighten up
Click to expand...
Click to collapse
30 min or even an hour is ok by me...
I'll do it right away. Flash stock, TWRP recovery then root with SuperSU.
As for the custom rom it'll have to wait as I didn't make up my mind which Lollipop to get... I'm kinda confused about it very much. I can't decide which to get.
I'm open for suggestions. lol
Thanks a million for your support.
If you need your phone for business don't flash lollipop. Still in beta phase, so bugs are occuring often.
I use dr. ketan's V14 and it's the most stable rom I have used
yaro666 said:
If you need your phone for business don't flash lollipop. Still in beta phase, so bugs are occuring often.
I use dr. ketan's V14 and it's the most stable rom I have used
Click to expand...
Click to collapse
My phone is for personal use not for business.
But I think I'll follow your advice & give Dr. Ketan's V14 a try.
I did flash stock firmware then flashed TWRP 2.8.6 (correct file this time.. lol) then installed root.
I did backup my phone & EFS by TWRP. All is excellent now.
Now I'll backup my contacts, sms, apps & data using Titanium back up then go for Dr. ketan's rom.
Wish me luck.
Thanks.
you will be positively surprised if youhad stock the whole time.
cheers
salute
yaro666 said:
you will be positively surprised if youhad stock the whole time.
cheers
salute
Click to expand...
Click to collapse
Wow... it's awesome. ..
Thumbs up. ..
You are right.
I'm wondering right now how did I stuck to the stock firmware all the past time.
Thanks.
I am currently running an OG5 based ROM, with the OB7 bootloader.
I had been keeping the OB7 bootloader, instead of upgrading to OE1/OF5, because it allowed me to go back to Kit Kat NK2, after evaluating the initial lollipop release.
Now that OG5 is out, I am pretty happy and can't imagine going back to KK.
So I've been trying to get Android Pay to allow me store a credit card and no fix has worked. I am thinking that it might be because my rom and bootloader don't match up (OB7 & OG5)?
I was going to give it a shot, but now wondering if there is any reason to keep OB7 bootloader, other than having the option to downgrade?
If I decide to go all OG5 (ROM and bootloader) is there any easier way than starting with the OTA?
Thanks,
Also curious about this. If you get it working please share what steps you took. To be honest, all I'd like to do in Android Pay would be to set up the loyalty cards.... seems as though you can input any until you've verified at least 1 credit or debit card
Also... any chance its possible to set up a card on Android Pay from another unrooted device then use as normal from your rooted phone once a card is added to your account? I don't have a secondary device to try
Sent from my SM-N910P using XDA Free mobile app
ch3ck3rs said:
Also curious about this. If you get it working please share what steps you took. To be honest, all I'd like to do in Android Pay would be to set up the loyalty cards.... seems as though you can input any until you've verified at least 1 credit or debit card
Click to expand...
Click to collapse
Do you also have the OB7/OG5 combo?
I wonder if anyone with OG5/OG5 has had any luck. from what I've read plenty of people with unlocked bootloaders have been successful.
FYI there is an app called Keyring that does a decent job with loyalty cards.
Yep. I have the same combo. Running Saintz OBAR
A lot of variables are at play here. Most root users of any device are hitting roadblocks when it comes to getting AP to load their cards. In my instance I am on OG5/OG5 running HybridX 3. I've explored nearly all of the 'fixes' out there short of flashing the stock build.prop. Some reports are saying it is checking against known good OS (ie: CM12 stable vs. CM12 nightly). Others are saying it is checking directory level instances of root (ex: system/bin/su or system/xbin/su). Still more are just unlucky and are hitting the wall for no explained reason (there is a reason I'm sure, the info provided isn't helping). What it is going to boil down to is some smart cookie is going to unlock the secret, and we're going to say 'you've got to be kidding, that was too easy'.
With Android Pay, it will block root users and I haven't found a way that gets around it on the Note 4, even with Root Cloak and No Device Check to mask root and custom ROM's to get it to work.
From what I saw, Android Pay does have SafetyNet built in to it to check if your device and your firmware match up. I ran into the same issue with running the OB7 bootloader and CM12.1 ROM which doesn't work. I'm assuming you are having a similar as me issue with using the 0B7 bootloader and a 0G5 ROM. Unfortunately, you will probably have to unroot and go back to stock to get it to work since none of the workarounds I've tried hasn't worked.
Sent from my SM-N910P using Tapatalk
ThatGuy94 said:
FYI there is an app called Keyring that does a decent job with loyalty cards.
Click to expand...
Click to collapse
I use beep and go, works with older infrared barcode scanners
I'm currently on 5.01 and OB7. I was able to get Android Pay to let me add a card by going into the settings menu in SuperSU and disabling Superuser. I entered the card info and Android Pay was set up. I used it at Toys R Us today and works perfect. I re-enabled Superuser in SuperSU and was able to still use Android Pay.
I have the same question as OP. What are the benefits of staying on OB7? I am getting ready to update to 5.1.1 using this link
http://forum.xda-developers.com/not...g-to-5-1-1-t3199881/post62794303#post62794303
Do I need to stay on OB7 to install custom roms? Can I install custom roms with OG5? I would like to eventually install a stockish rom that has Knox and Itson removed, along with all the bloatware.
Thanks!
Quick answer is OB7 allows you to go back to KK OG5 will not
dh350nwo said:
Quick answer is OB7 allows you to go back to KK OG5 will not
Click to expand...
Click to collapse
Thanks! No intention on going back to KK. So if I update to OG5, I can still flash a custom rom?
duongdn said:
Thanks! No intention on going back to KK. So if I update to OG5, I can still flash a custom rom?
Click to expand...
Click to collapse
Quick answer is yes but you'd be limited to OG5 ROMs if you flashed the stock OG5 tar. You may also get Noterized, sacs and CM12 custom ROMs. Your backups would be void.
If you instead chose to keep the OB7 bootloader, you could flash the OB7 to OG5 tar ball by tx_dbs_tx and still be be able to Odin the older tars to use the ROMs or backups you have now.
http://forum.xda-developers.com/showpost.php?p=62274955&postcount=1
There are some S6 ROM ports (not quite stable as stock) but it looks like there's a possible banding of developers to get the Note 5 ported to OG5. What's stable at the moment are the stock Note 4 ROMs with a few mods. tx_dbs_tx Hybrid X or stock OG5 ROMs have been getting props by users; use that if you're not into running stock rooted Odex.
I'm actually running stock Odex from the tar ball flash linked above, just Odin'd TWRP and rooted with Beastmode kernel and SuperSU zip in recovery, debloated and modified it.
Edit: The OG5 custom ROMs are pre-rooted. You'd only need to Odin TWRP and follow OP install instructions to install. I'd recommend the Beastmode kernel though. Some say adjust the volume level in Synapse but I do it with Viper4Android and leave the Dolby Atmos volume leveler enabled. It pumps the bass without volume too high or too low.
Sent from my SM-N910P using Tapatalk
duongdn said:
I'm currently on 5.01 and OB7. I was able to get Android Pay to let me add a card by going into the settings menu in SuperSU and disabling Superuser. I entered the card info and Android Pay was set up. I used it at Toys R Us today and works perfect. I re-enabled Superuser in SuperSU and was able to still use Android Pay.
I have the same question as OP. What are the benefits of staying on OB7? I am getting ready to update to 5.1.1 using this link
http://forum.xda-developers.com/not...g-to-5-1-1-t3199881/post62794303#post62794303
Do I need to stay on OB7 to install custom roms? Can I install custom roms with OG5? I would like to eventually install a stockish rom that has Knox and Itson removed, along with all the bloatware.
Thanks!
Click to expand...
Click to collapse
Sigh. I had great hopes this would help me but no luck i disabled superuser and still android pay says cannot vetify my device... any other thoughts? I am on 5.01 sttaight up rooted running alliance rom
cheryl
cherylbaker said:
Sigh. I had great hopes this would help me but no luck i disabled superuser and still android pay says cannot vetify my device... any other thoughts? I am on 5.01 sttaight up rooted running alliance rom
cheryl
Click to expand...
Click to collapse
Safetynet has to verify the Rom is original to the phone. If you're not using stock Android Pay will throw that message
Sent from my SM-N910P using Tapatalk
SafetyNet is just 1 part of the puzzle. If it was the only thing then the Xposed module 'No Device Check' would be enough to bypass. There are multiple checks taking place.
OG5 and non OG5 roms
samep said:
Quick answer is yes but you'd be limited to OG5 ROMs if you flashed the stock OG5 tar. You may also get Noterized, sacs and CM12 custom ROMs. Your backups would be void.
If you instead chose to keep the OB7 bootloader, you could flash the OB7 to OG5 tar ball by tx_dbs_tx and still be be able to Odin the older tars to use the ROMs or backups you have now.
http://forum.xda-developers.com/showpost.php?p=62274955&postcount=1
There are some S6 ROM ports (not quite stable as stock) but it looks like there's a possible banding of developers to get the Note 5 ported to OG5. What's stable at the moment are the stock Note 4 ROMs with a few mods. tx_dbs_tx Hybrid X or stock OG5 ROMs have been getting props by users; use that if you're not into running stock rooted Odex.
I'm actually running stock Odex from the tar ball flash linked above, just Odin'd TWRP and rooted with Beastmode kernel and SuperSU zip in recovery, debloated and modified it.
Edit: The OG5 custom ROMs are pre-rooted. You'd only need to Odin TWRP and follow OP install instructions to install. I'd recommend the Beastmode kernel though. Some say adjust the volume level in Synapse but I do it with Viper4Android and leave the Dolby Atmos volume leveler enabled. It pumps the bass without volume too high or too low.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
You can run any rom under OG5 if you took full OG5 update, Ive been running all sorts of ROMs that are not OG5 and they work just fine, flash everything as normal just flash beast mode kernal or emotion kernel or AEL kernel, after flashing ROM...any exploited OG5 kernel will work.
Iceburn1 said:
You can run any rom under OG5 if you took full OG5 update, Ive been running all sorts of ROMs that are not OG5 and they work just fine, flash everything as normal just flash beast mode kernal or emotion kernel or AEL kernel, after flashing ROM...any exploited OG5 kernel will work.
Click to expand...
Click to collapse
I recall reading that but couldn't recall the steps. Makes sense. Thanks.
Edit: I wouldn't recommend Odin any tar. I believe you still cannot go backwards regarding Odin. The OG5 bootloader won't allow downgrade flash.
Sent from my SM-N910P using Tapatalk
nacron said:
Safetynet has to verify the Rom is original to the phone. If you're not using stock Android Pay will throw that message
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
So your saying unless you are running stock rom and no root there is no way to get android pay to work
cheryl
In short yes. Long version is that the unit needs to be on a stock ROM with root hidden. Many users are able to get AP to work when they hide root on setup using Root Cloak and/or turning off SU. Some others have not had success doing this also. AP is checking multiple things along with root, kernel changes, Xposed installation, and other things. Safety net is only one check. Those of us that are rooted using custom ROMs with other changes are going to have to wait until a smart Dev can crack the mystery.
dh350nwo said:
In short yes. Long version is that the unit needs to be on a stock ROM with root hidden. Many users are able to get AP to work when they hide root on setup using Root Cloak and/or turning off SU. Some others have not had success doing this also. AP is checking multiple things along with root, kernel changes, Xposed installation, and other things. Safety net is only one check. Those of us that are rooted using custom ROMs with other changes are going to have to wait until a smart Dev can crack the mystery.
Click to expand...
Click to collapse
What if you went stock set it up avd than flashed back custom rom... does it do the same ssfety checks even after it is setup?
cheryl
Note 4 Bootlooping after Root attempt
Hey everyone. So I tried the Chainfire root on a Note 4 running 5.1.1. I realized afterwards how big of a mess I made. I'm still able to get the phone in download mode and have tried several different roms but I'm not able to successfully flash anything. I've tried different versions of Odin and USB cables. Any information I can provide to help I can do.
I'd suggest the OJ6 tar; quicker download was posted today. Does it boot to recovery? If not, start with a long battery pull; at least 30 seconds prior to Odin. Uncheck the auto reboot and F. Reset, flash the tar, wait until done and pull USB and battery with same wait. Boot to recovery and factory reset. Power down, pull battery and Odin again, this time with defaults.
When rooting, flash custom recovery like TWRP, either flash a custom ROM or flash Beastmode or 5.1.1 custom kernel and SuperSU zip in recovery to root. Don't use Chainfire auto root for Note 4.
If you have no success, follow this post but read the whole thread.
http://forum.xda-developers.com/showthread.php?p=63831716
Sent from my SM-N910P using Tapatalk
Samep you are a genius! Thank you so much for that. I'm wanting to strip the phone down to a really basic ROM for my father-in-law to use without all the bloatware and useless Sprint and Samsung apps. I'll be much more careful in the future.
exeterx said:
Samep you are a genius! Thank you so much for that. I'm wanting to strip the phone down to a really basic ROM for my father-in-law to use without all the bloatware and useless Sprint and Samsung apps. I'll be much more careful in the future.
Click to expand...
Click to collapse
Glad to hear. Freeza has a debloated-deodexed OJ6 rooted ROM with newer kernel for OJ6. Either use it as a guide or install per OP.
Sent from my SM-N910P using Tapatalk