Related
So I'm by no means super knowledgable with this stuff but I've rooted a few phones, played around with CM on my old evo but for the most part I enjoy rooted stock.
I have Galaxy S3 Sprint 4.3 updated OTA from a rooted (4.1.2). When I took the OTA I lost root, no big deal I used Odin and flashed the CF auto root, it said it removed knox and I had root back. Cool!
In short 4.3 sucked, wanted to downgrade back so things like TrevE mod would work again and it wouldn't be so buggy. I tried to use odin to flash "KIES_HOME_L710VPBMD4_L710SPRBMD4_1130792_REV03_user_low_ship.tar.md5" but it gave me the "Use Kies Recovery and error occured" message.
So I then used odin and flashed TWRP and my phone booted.
I'm back on 4.3 rooted.
I've tried picking through the forums and interwebz for answers but I get mixed messages and info on international versions and what not.
I'm tired of trying to figure it out and really could use some help downgrading back to 4.1.2
Thanks,
Brandon
mentorkyrom said:
So I'm by no means super knowledgable with this stuff but I've rooted a few phones, played around with CM on my old evo but for the most part I enjoy rooted stock.
I have Galaxy S3 Sprint 4.3 updated OTA from a rooted (4.1.2). When I took the OTA I lost root, no big deal I used Odin and flashed the CF auto root, it said it removed knox and I had root back. Cool!
In short 4.3 sucked, wanted to downgrade back so things like TrevE mod would work again and it wouldn't be so buggy. I tried to use odin to flash "KIES_HOME_L710VPBMD4_L710SPRBMD4_1130792_REV03_user_low_ship.tar.md5" but it gave me the "Use Kies Recovery and error occured" message.
So I then used odin and flashed TWRP and my phone booted.
I'm back on 4.3 rooted.
I've tried picking through the forums and interwebz for answers but I get mixed messages and info on international versions and what not.
I'm tired of trying to figure it out and really could use some help downgrading back to 4.1.2
Thanks,
Brandon
Click to expand...
Click to collapse
The 4.3 OTA installed a locked bootloader, which will prevent you from ODIN'ing back to a previous version. you can flash any ROM you would like from recovery, you CANNOT downgrade the bootloader. As of right now, if you have knox, you are stuck with it.
You are extremely lucky that you didn't brick your phone by using odin to flash a non-4.3 tar. I wouldnt try again.
My advice is, remain rooted with a custom recovery, and find a ROM to your liking, and flash that.
I have also heard that we cannot flash custom kernels on the knox (MK3) bootloader as well, but I havent verified that.
eletendre84 said:
The 4.3 OTA installed a locked bootloader, which will prevent you from ODIN'ing back to a previous version. you can flash any ROM you would like from recovery, you CANNOT downgrade the bootloader. As of right now, if you have knox, you are stuck with it.
You are extremely lucky that you didn't brick your phone by using odin to flash a non-4.3 tar. I wouldnt try again.
My advice is, remain rooted with a custom recovery, and find a ROM to your liking, and flash that.
I have also heard that we cannot flash custom kernels on the knox (MK3) bootloader as well, but I havent verified that.
Click to expand...
Click to collapse
Thank you for the response. Is CyanogenMod an option then? If I go to CM could I flash back a stock 4.3 rom in the future?
As an added bonus question does CM allow wifi tethering?
Again thank you for the response.
mentorkyrom said:
Thank you for the response. Is CyanogenMod an option then? If I go to CM could I flash back a stock 4.3 rom in the future?
As an added bonus question does CM allow wifi tethering?
Again thank you for the response.
Click to expand...
Click to collapse
CM is certainly an option. In fact, its what i am running now. CM11 12-24. Runs great. You can always odin the stock mk3 tar and go back to stock unrooted, at any time.
in order to flash cm11 you MUST be on TWRP 2.6.3.1 or CWM 6.0.4.5 or newer or the assert check will fail.
not sure on the tethering, but im pretty sure it definitely works on cm10.2 and i think it does on 11 as well, but dont quote me on that.
eletendre84 said:
CM is certainly an option. In fact, its what i am running now. CM11 12-24. Runs great. You can always odin the stock mk3 tar and go back to stock unrooted, at any time.
in order to flash cm11 you MUST be on TWRP 2.6.3.1 or CWM 6.0.4.5 or newer or the assert check will fail.
not sure on the tethering, but im pretty sure it definitely works on cm10.2 and i think it does on 11 as well, but dont quote me on that.
Click to expand...
Click to collapse
Tethering is available on CM11 just like it was on 10.2; would strongly recommend latest Philz Touch Recovery over either TWRP or CWM though. Although it is based on CWM, it has proven to be pretty much the superior recovery option for flashing any Android build number, plus it is highly customizable.
Philz Touch Recovery
this is how to downgrade
mentorkyrom said:
So I'm by no means super knowledgable with this stuff but I've rooted a few phones, played around with CM on my old evo but for the most part I enjoy rooted stock.
I have Galaxy S3 Sprint 4.3 updated OTA from a rooted (4.1.2). When I took the OTA I lost root, no big deal I used Odin and flashed the CF auto root, it said it removed knox and I had root back. Cool!
In short 4.3 sucked, wanted to downgrade back so things like TrevE mod would work again and it wouldn't be so buggy. I tried to use odin to flash "KIES_HOME_L710VPBMD4_L710SPRBMD4_1130792_REV03_user_low_ship.tar.md5" but it gave me the "Use Kies Recovery and error occured" message.
So I then used odin and flashed TWRP and my phone booted.
I'm back on 4.3 rooted.
I've tried picking through the forums and interwebz for answers but I get mixed messages and info on international versions and what not.
I'm tired of trying to figure it out and really could use some help downgrading back to 4.1.2
Thanks,
Brandon
Click to expand...
Click to collapse
do a factory data reset then use odin auto root from computer ok...... after boot u will get a security message supersu will be unfortunately stopping this is ok..... then u will need to download the supersu.app to root of sd then manually install this will update it and now u can turn off knox and have root... then go to market and download odin mobile then flash your .tar file u want and you will be good to go 4.1.2 doesn't have knox and has a unlocked bootloader so have fun bro this method may work for other phones
smuther22 said:
do a factory data reset then use odin auto root from computer ok...... after boot u will get a security message supersu will be unfortunately stopping this is ok..... then u will need to download the supersu.app to root of sd then manually install this will update it and now u can turn off knox and have root... then go to market and download odin mobile then flash your .tar file u want and you will be good to go 4.1.2 doesn't have knox and has a unlocked bootloader so have fun bro this method may work for other phones
Click to expand...
Click to collapse
Do you realize that this thread hasn't been used in a couple of months? I would assume the author has no more need of advice based on the inactivity. Also, once Knox is installed, it is on the phone to stay. PERIOD. NO DOWNGRADING POSSIBLE VIA ODIN. Custom ROMs of any build are fine via custom recovery, but any attempt to change the bootloader will trigger Knox and brick the phone. Dangerous info to be posting here, especially since someone else who doesn't know better might try this.
Hi guys, I just got a galaxy s4 for t mobile and it came with 4.2.2 version of android. I'm scared to brick the phone but I really want to root it. Can someone point me to the right direction? Been reading some tutorials but they are for different versions of android. How do I root my phone without bricking it or tripping Knox?
itsfredo said:
Hi guys, I just got a galaxy s4 for t mobile and it came with 4.2.2 version of android. I'm scared to brick the phone but I really want to root it. Can someone point me to the right direction? Been reading some tutorials but they are for different versions of android. How do I root my phone without bricking it or tripping Knox?
Click to expand...
Click to collapse
4.2.2 doesnt have Knox. Use CF-Auto Root by Chainfire to root.
The Sickness said:
4.2.2 doesnt have Knox. Use CF-Auto Root by Chainfire to root.
Click to expand...
Click to collapse
Thanks! Now it seems that cf auto root comes with a stock kernel and recovery. Is this changeable? Can I install a custom recovery and kernel after using cf auto root? Or should I find a different method of rooting for this? Are there any safe ones out there. It seems that a lot is outdated and I'm afraid of installing the wrong thing.
itsfredo said:
Thanks! Now it seems that cf auto root comes with a stock kernel and recovery. Is this changeable? Can I install a custom recovery and kernel after using cf auto root? Or should I find a different method of rooting for this? Are there any safe ones out there. It seems that a lot is outdated and I'm afraid of installing the wrong thing.
Click to expand...
Click to collapse
I don't know if towelroot will root 4.2.2, but it doesn't install a recovery.
Rob
itsfredo said:
Thanks! Now it seems that cf auto root comes with a stock kernel and recovery. Is this changeable? Can I install a custom recovery and kernel after using cf auto root? Or should I find a different method of rooting for this? Are there any safe ones out there. It seems that a lot is outdated and I'm afraid of installing the wrong thing.
Click to expand...
Click to collapse
You're calling a rooting method outdated while using the exact "outdated" software it was meant to root in the first place. CF-autoroot is as safe as safe can be. In fact, I know it still works for 4.3 and I THINK 4.4.2; it just trips the KNOX counter on them... still gets the job done though.
As far as your concern of installing the recovery; it first flashes its own recovery so it can use an exploit, then reverts it back to stock. I believe the kernel is untouched.
If your end goal is to move on to custom recoveries and custom ROMs you can bypass the rooting process altogether and go straight for the recovery/ROM.
lordcheeto03 said:
You're calling a rooting method outdated while using the exact "outdated" software it was meant to root in the first place. CF-autoroot is as safe as safe can be. In fact, I know it still works for 4.3 and I THINK 4.4.2; it just trips the KNOX counter on them... still gets the job done though.
As far as your concern of installing the recovery; it first flashes its own recovery so it can use an exploit, then reverts it back to stock. I believe the kernel is untouched.
If your end goal is to move on to custom recoveries and custom ROMs you can bypass the rooting process altogether and go straight for the recovery/ROM.
Click to expand...
Click to collapse
This.
You really don't need CF Auto Root at all until all you want to do is root the stock rom.
If you want to install a customer rom, use Odin to install a custom recovery and flash whatever you want from there.
lordcheeto03 said:
If your end goal is to move on to custom recoveries and custom ROMs you can bypass the rooting process altogether and go straight for the recovery/ROM.
Click to expand...
Click to collapse
That's precisely my end goal. And I guess my question is how to do this safely with the Android version I have.
I didn't mean the root method was outdated; I was talking about some of the information that's on the general forum regarding root. There is even a post on one of the stickies asking for updated info in May. This scares me because for all I know I can follow one of these methods to root or install a custom recovery/rom and end up with a brick because something is no longer compatible.
I guess my question is: what is the best (updated) method of installing a custom rom/recovery for my tmobile s4 with android 4.2.2?
Use cf autoroot and flash clockworkmod through Odin. Download rommanager. Download a rom. Hit install rom from SD card. Pick your ROM from downloads.
itsfredo said:
That's precisely my end goal. And I guess my question is how to do this safely with the Android version I have.
I didn't mean the root method was outdated; I was talking about some of the information that's on the general forum regarding root. There is even a post on one of the stickies asking for updated info in May. This scares me because for all I know I can follow one of these methods to root or install a custom recovery/rom and end up with a brick because something is no longer compatible.
I guess my question is: what is the best (updated) method of installing a custom rom/recovery for my tmobile s4 with android 4.2.2?
Click to expand...
Click to collapse
I understand your apprehension, i really do. What I've said to do has worked for me when i got the phone over a year ago, and has worked here recently when i did it again. I'm trying to tell you there is no need for an updated way of doing what you want. If you want root, use CFauto root. Like i said, that method was done specifically for MDB and MDL firmwares, there is no better choice. Newer yeah, but better? Not a chance. Your firmware is equally outdated and it's worked for millions of users without fail.
As far as a custom ROM goes, find one you want to use, put it on your SD card, pick a recovery (CWM, Philz, or TWRP), flash that in Odin, boot to recovery (power+volume up) , do a full wipe (system, data, and cache) select the ROM, and flash. No need to root at all if you want to go straight to a custom ROM.
EDIT: Obviously, you might want to perform a nandroid backup once you flash your recovery... but that's really optional as long as you have the stock Odin-flashable firmware. Totally up to you.
Sent from my SGH-M919 using XDA Premium 4 mobile app
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
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