Related
So I just got my Z3C and have been happily loading my apps when I read that rooting wipes the device and I might be wasting my time. Is it still the case that you need to use the exploit to root?
I had to pretty much re-root and do the whole shibang shibang again. Not only that, but I've also been struggling to get xposed to work on 5.1.1. Didn't have any trouble getting it to work on 5.0.2. So far, it seems like most people are getting xposed to work by using an older zip, which has been annoying to track down. It's a v67 version of xposed, but it's a specific one. Also, had to flash an additional zip just to get the notification bar to align correctly, and there's some additional new bloat.
Won't lie. Was pretty happy with 5.0.2., and it's taking me quite some time to get my phone back to how customized I had it in 5.1.1
mnguyen127 said:
I had to pretty much re-root and do the whole shibang shibang again. Not only that, but I've also been struggling to get xposed to work on 5.1.1. Didn't have any trouble getting it to work on 5.0.2. So far, it seems like most people are getting xposed to work by using an older zip, which has been annoying to track down. It's a v67 version of xposed, but it's a specific one. Also, had to flash an additional zip just to get the notification bar to align correctly, and there's some additional new bloat.
Won't lie. Was pretty happy with 5.0.2., and it's taking me quite some time to get my phone back to how customized I had it in 5.1.1
Click to expand...
Click to collapse
This is your best bet to find out exactly what Xposed version you need for your Rom and for your phone. You will have 5.1.1 working better than ever in a couple steps. Hope it helps.
http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
flamand said:
So I just got my Z3C and have been happily loading my apps when I read that rooting wipes the device and I might be wasting my time. Is it still the case that you need to use the exploit to root?
Click to expand...
Click to collapse
To answer your question - you only TRULY have to wipe your device when changing from KK to LP or vice-versa; however, everything just works better when you wipe. During the rooting process, I believe you'll have to downgrade to an old KK firmware, then once you've obtained root, you'll have to install a pre-rooted 5.1.1 LP firmware. At that point, you can choose to either wipe or not.
Hi there,
It's exciting that Android pay supports Australian bank. However, when I downloaded it and was adding card, it shows "Google is unable to verify the device..." I rooted my p9, but I unchecked superuser before adding credit card. It still doesn't work on my phone. Does anyone know about this?
Cheers.
You have to reflash a stock ROM.
nuttzo33 said:
You have to reflash a stock ROM.
Click to expand...
Click to collapse
Thanks mate. I'll have a try today.
If you have an eva-l09 model then flash paulobriens stock rom here
http://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818
Then unlock bootloader and flash twrp.
Then flash this zip file in twrp
http://forum.xda-developers.com/p9/development/c432-oeminfo-flash-twrp-t3384903
Then reflash the stock rom again and you will have Android pay back and bootloader will be relocked.
Actually if you already have twrp installed you could probably just flash the custom OEM and then flash the stock rom.
Do a twrp backup first though
I decided that Android Pay isn't worth it for me. I use Xposed way more than I would use Android Pay. Plus Commonwealth Banks tap to pay works with root blocker in Xposed. So my main bank works for NFC payments. Although Westpac, my other bank is pretty much the worst with tech support. They did some deal with Samsung where only Samsung devices are supported for NFC payments - it's the freaking worst. They insist that it's to do with security, but it's a load of crap.
nuttzo33 said:
Actually if you already have twrp installed you could probably just flash the custom OEM and then flash the stock rom.
Do a twrp backup first though
Click to expand...
Click to collapse
Thanks a lot! Appreciate it.
bunnybash said:
I decided that Android Pay isn't worth it for me. I use Xposed way more than I would use Android Pay. Plus Commonwealth Banks tap to pay works with root blocker in Xposed. So my main bank works for NFC payments. Although Westpac, my other bank is pretty much the worst with tech support. They did some deal with Samsung where only Samsung devices are supported for NFC payments - it's the freaking worst. They insist that it's to do with security, but it's a load of crap.
Click to expand...
Click to collapse
All right. But unfortunately my bank is ANZ. I was really surprised cuz it support Android pay now. I really like using the app from Google, that's why I want to have a try. Anyway, I'll restore my phone and have a try again.
Hi Guys, I've managed to get through every stage of this until it gets to reflashing the stock rom at the end. For some reason it just goes back into TWRP when rebooting. Is that supposed to happen and if so what next?
I'm guessing I may have gone wrong somewhere along the lines?!
I'm no stranger to development here but have been out for a while. I just got a new car with a touch screen and continued to add Android Auto app for navigation etc. I was still on kitkat lol due to difficulty of going back and horror stories of poor batter life on lollipop/marshmallow. So... I went ahead to latest stock marshmallow. it works fine and AA is nice. As soon as I decided to root with permissive kernel, auto app stops working. Apparently, it's beastmode kernel. The question is, does anyone know if a particular rom or kernel works well with android auto for the t910? Does old school root (non systemless) work with just a stock kernel? Thanks for any help, fellas!
Well, I got it working if anyone's interested or was stuck in the same position as me. Apparently, systemless root isn't too bad once you figure out how to do everything. Just follow this threads directions. https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268 Install the TWRP recovery via Odin, flash SU systemless root, install the xposed installer from that thread, install magisk manager, flash the zip magisk provides after letting it auto select the position in recovery, then install the systemless root version of xposed via xposed installer. It sounds a bit daunting but if you know how to use Odin well enough you can always recover if you get stuck in a bootloop. It's not as nice as old style root (there do seem to be some limitations but at least Android Auto works and your phone isn't so limited as stock. I got AdAway to work, YouTube Background Playback module, and SD card fix for marshmallow. Maybe this is known to many people already but our sub-forum seems to be dead since our phones are so old now.
On a final note, there aren't many new phones to choose from if you want a higher-end phone with a removable battery. The only one that seems worth it is the LG V20. It seems like the G6 and V30 won't have removable batteries. Samsung seems like they're making a new Note but I doubt it will have a removable battery. They seem to be disappearing. If they had used one on the last Note.... The exploding battery issue could have been fixed rather easily and way less embarrassingly.
I hope this helps someone!
A More Simple Solution
This post is for anyone who ran into this same issue recently just as I have. There is a simpler way to resolve it. I installed a new Kenwood navigation unit into my 2000 Nissan Maxima. I'm on a custom ROM with BeastMode kernel. All I did to resolve the issue was replaced BeastMode kernel with Emotion kernel version r26. Now I'm able to use Android Auto with my new navigation unit. If you find yourself in this situation, go to the link below and download the latest kernel from Emotion.
Emotion thread: https://forum.xda-developers.com/note-4/orig-development/tw-kernel-emotroid-team-t2990557
Has anyone been able to get android pay working after flashing 8.0 firmware and rooting? If so could you talk through how you did it?
bot_rosco said:
Has anyone been able to get android pay working after flashing 8.0 firmware and rooting? If so could you talk through how you did it?
Click to expand...
Click to collapse
I have working Android Pay with Android One stock rooted firmware. I'm running the XT1900-1 Retail Edition. What have you done so far?
Sent from my moto x4 using Tapatalk
@jiggyman - Are you on Nougat or Oreo?
Neffy27 said:
@jiggyman - Are you on Nougat or Oreo?
Click to expand...
Click to collapse
I'm running the Android One Oreo firmware.
Sent from my moto x4 using Tapatalk
Just today a new magisk update was released which has allowed me to use Google pay . Anyone else who has been having issues and is using root (magisk) ensure you are using version 16
I OTA'd to 8.0 (I have the X4 Retail/Non-Fi version) and Android Pay is broken. It was working just fine on Nougat. Any pointers? TIA.
smmankad said:
I OTA'd to 8.0 (I have the X4 Retail/Non-Fi version) and Android Pay is broken. It was working just fine on Nougat. Any pointers? TIA.
Click to expand...
Click to collapse
Are you using Magisk for your root? If not, that's what you need. So remove your other root method like SUPERSU or whatever, then use the systemless root like magisk.
It is working for me.
edufur said:
Are you using Magisk for your root? If not, that's what you need. So remove your other root method like SUPERSU or whatever, then use the systemless root like magisk.
It is working for me.
Click to expand...
Click to collapse
Thank you - I was considering Magisk, but I'm not rooted at all (I'm on stock, re-locked bootloader - I re-flashed stock after playing around with unlocking the bootloader, TWRP, etc.). Is it because of the re-flash? I am able to OTA successfully, but Root Checker says "CTS Profile Match: Failed" for Safety Net. I suspect that's the issue, but have no clue about solving it. Googling isn't much help either (all answers point to Magisk - I'm okay with that, if that's a guaranteed solution, as I'm dreading having to lose data when I unlock the bootloader to install TWRP and Magisk). I'm pretty certain I'm missing something as it looks as though I am one of the few whose Pay isn't working. I even tried the Fi ROM, with same problem (OTA works, but Pay doesn't. Same CTS Profile Match error). This issue is driving me insane (Everything else works great and I love this device!)
smmankad said:
Thank you - I was considering Magisk, but I'm not rooted at all (I'm on stock, re-locked bootloader - I re-flashed stock after playing around with unlocking the bootloader, TWRP, etc.). Is it because of the re-flash? I am able to OTA successfully, but Root Checker says "CTS Profile Match: Failed" for Safety Net. I suspect that's the issue, but have no clue about solving it. Googling isn't much help either (all answers point to Magisk - I'm okay with that, if that's a guaranteed solution, as I'm dreading having to lose data when I unlock the bootloader to install TWRP and Magisk). I'm pretty certain I'm missing something as it looks as though I am one of the few whose Pay isn't working. I even tried the Fi ROM, with same problem (OTA works, but Pay doesn't. Same CTS Profile Match error). This issue is driving me insane (Everything else works great and I love this device!)
Click to expand...
Click to collapse
Going back to stock and relocking the bootloader should have google pay back up and running with no issues. If you are having issues, I would be concerned that the return to stock did not work. In any case, if you want to return to a rooted rom, you obviously need to unlock the bootloader and then just make sure you choose Magisk as your option for root. But for me personally, I would not go this route until you can get a factory rom with locked bootloader working again. Otherwise, even if you go the magisk route, it might not work due to your current situation.
edufur said:
Going back to stock and relocking the bootloader should have google pay back up and running with no issues. If you are having issues, I would be concerned that the return to stock did not work. In any case, if you want to return to a rooted rom, you obviously need to unlock the bootloader and then just make sure you choose Magisk as your option for root. But for me personally, I would not go this route until you can get a factory rom with locked bootloader working again. Otherwise, even if you go the magisk route, it might not work due to your current situation.
Click to expand...
Click to collapse
The funny thing is that the re-flash was done using 7.1.1 stock ROM found here - https://mirrors.lolinet.com/firmware/moto/payton/official/RETAIL/ (I used the 26.83-34-0-1 and then OTA'd up to 8.0/March 2017 from there). Pay was working on 7.1.1. Right after the last 8.0 OTA, it broke. I used the standard fastboot flash and flashed all files in the right order. What stumps me is that there was no issue in 7.1.1... Only after OTA did it break. Can you point me to the ROM I should use just to make sure I didn't pick a bad one? (I tried so many in my attempt to solve this that I really need a second set of eyes to tell me if I'm going wrong somewhere).
---------- Post added at 03:32 AM ---------- Previous post was at 03:17 AM ----------
edufur said:
Going back to stock and relocking the bootloader should have google pay back up and running with no issues. If you are having issues, I would be concerned that the return to stock did not work. In any case, if you want to return to a rooted rom, you obviously need to unlock the bootloader and then just make sure you choose Magisk as your option for root. But for me personally, I would not go this route until you can get a factory rom with locked bootloader working again. Otherwise, even if you go the magisk route, it might not work due to your current situation.
Click to expand...
Click to collapse
PS: Also, is there a way I can start from a clean slate, I mean, phone ? Some way I can do a hard wipe and then flash stock? I'm sure something is mucked up currently, so a clean flash would be best.
edufur said:
Going back to stock and relocking the bootloader should have google pay back up and running with no issues. If you are having issues, I would be concerned that the return to stock did not work. In any case, if you want to return to a rooted rom, you obviously need to unlock the bootloader and then just make sure you choose Magisk as your option for root. But for me personally, I would not go this route until you can get a factory rom with locked bootloader working again. Otherwise, even if you go the magisk route, it might not work due to your current situation.
Click to expand...
Click to collapse
My investigation here: https://forum.xda-developers.com/mo...ware-stock-7-1-1-t3693145/page13#post76610643
Hey there guys,
I just received my s21 ultra (G998B) and planning to root it. I had a few questions since I’m new to this and wanted some clarifications:
1) If I root the phone can I update it OTA through the settings or do I have to update it by another method? Will I lose root/data/apps if I do that?
2) If I lose root when updating it, can I just root again and be all set? Or do I have to follow another procedure for that?
3) I am planning to debloat a few apps and services that I won’t be using, if I update the system/software will the stuff that I debloated come back and will I have to do the debloat again?
Thank you for all the help.
paul_cherma said:
Hey there guys,
I just received my s21 ultra (G998B) and planning to root it. I had a few questions since I’m new to this and wanted some clarifications:
1) If I root the phone can I update it OTA through the settings or do I have to update it by another method? Will I lose root/data/apps if I do that?
2) If I lose root when updating it, can I just root again and be all set? Or do I have to follow another procedure for that?
3) I am planning to debloat a few apps and services that I won’t be using, if I update the system/software will the stuff that I debloated come back and will I have to do the debloat again?
Thank you for all the help.
Click to expand...
Click to collapse
1- Probably not usually the root or recovery will block OTA updates from installing, even if they download.
2- If you lose root, you can USUALLY re-root assuming the same root method wasnt patched. If it was patched, a new root method (though probably still through magisk) will be needed. If this is the case, its up to the dev to find that method, you might be without root for a while.
3-if you debloat, and receive an OTA, your will probably need to de-bloat again, thought I havent personally had experience with this.
Why are you rooting? Just to de-bloat? If so, root isn't really necessary...
As someone who's been in the rooting stage for many years, i can answer your questions.
1. You can not update your phone through OTA updates after rooting the device, as the device was modified in an unauthorized way. And since you own a galaxy phone, the e-fuse within the motherboard will blow and knox will be permanently blown. You can no longer use samsung pay, google pay, and any other app that uses the safetynet api, even after you unroot the device.
2. You will lose root every time you update. You will need ODIN on your PC in order to properly update your firmware and to re-root your device by following the procedure again that you used to root your device, unless samsung patched the method you used to root your device. You can always check what bootloader version you're on within the firmware. For example, on the galaxy S8, the firmware version is N950U1UES5CRG9. The 5th to last number of the firmware will tell you. In this case, N950U1UES5CRG9 is the 5th bootloader version. Keep this in mind once samsung starts to update your phone often.
3. You will have to debloat again from scratch. In order to fully update your device through ODIN, you need to download the full firmware file containing an AP (Firmware), BL (Bootloader) , CP (Modem), and CSC (Carrier File) and manually flash them.
Do keep in mind, it is possible to soft brick or even hard brick your device, so back up your data frequently if you decide to tinker with your device.
Thank you for the detailed answer. I just updated my software to the latest official one by Samsung (April 1st security patch) but I am not rooted yet. I guess I could live with the fact that I can root the phone now and stay on this software version/security patch until I upgrade, since I would have to go through a lot of hassle to set-up the phone the way I wanted. But the main reason why I want to get the official updates is because of the camera improvements that Samsung does, since the main reason of me getting this phone is the camera. And there are some root-required tweaks that I absolutely need such as Viper, and some xposed tweaks also. I like the Stock ROM of Samsung, it really has come a long way at least imo throughout the years, as I have been a Samsung user since day 1 but:
Would it be a good idea to install a custom ROM then? I am reading the description of a few custom ROMs and it seems like I can “retain everything” by simply dirty flashing the ROM and following the dev’s instructions on how to retain root whenever the developer updates it. Is that a better route to take you think? I can keep my device rooted, and still get the updates through a custom ROM.
paul_cherma said:
Thank you for the detailed answer. I just updated my software to the latest official one by Samsung (April 1st security patch) but I am not rooted yet. I guess I could live with the fact that I can root the phone now and stay on this software version/security patch until I upgrade, since I would have to go through a lot of hassle to set-up the phone the way I wanted. But the main reason why I want to get the official updates is because of the camera improvements that Samsung does, since the main reason of me getting this phone is the camera. And there are some root-required tweaks that I absolutely need such as Viper, and some xposed tweaks also. I like the Stock ROM of Samsung, it really has come a long way at least imo throughout the years, as I have been a Samsung user since day 1 but:
Would it be a good idea to install a custom ROM then? I am reading the description of a few custom ROMs and it seems like I can “retain everything” by simply dirty flashing the ROM and following the dev’s instructions on how to retain root whenever the developer updates it. Is that a better route to take you think? I can keep my device rooted, and still get the updates through a custom ROM.
Click to expand...
Click to collapse
That really varies depending on the custom rom you go for. Usually when you dirty flash a rom, you would need to re root your device, but some (not all) roms are persistent with root after system updates. Do keep in mind if you switch to a custom rom, your system might be more buggy and crash more often. One thing i will say though is that xposed is outdated. The last android version xposed officially supported was either 8 or 9. When it has to come down to certain mods you'd wish to have with root, take that into consideration too, as it might make your device really unstable if it's too outdated or if there's a buggy port available. I've dealt with that issue too many times on my phones.
HighOnLinux said:
That really varies depending on the custom rom you go for. Usually when you dirty flash a rom, you would need to re root your device, but some (not all) roms are persistent with root after system updates. Do keep in mind if you switch to a custom rom, your system might be more buggy and crash more often. One thing i will say though is that xposed is outdated. The last android version xposed officially supported was either 8 or 9. When it has to come down to certain mods you'd wish to have with root, take that into consideration too, as it might make your device really unstable if it's too outdated or if there's a buggy port available. I've dealt with that issue too many times on my phones.
Click to expand...
Click to collapse
if xposed is outdated, what is the new thing the comunity is migrating to? All the privacy, security, and customizability tools available through xposed must go somewhere, right?
Twodordan said:
if xposed is outdated, what is the new thing the comunity is migrating to? All the privacy, security, and customizability tools available through xposed must go somewhere, right?
Click to expand...
Click to collapse
There's buggy ports thats flashable on magisk. While you still can get xposed, it'll be an unofficial version, and more likely to run into issues within your rom and daily use into your device.
HighOnLinux said:
There's buggy ports thats flashable on magisk. While you still can get xposed, it'll be an unofficial version, and more likely to run into issues within your rom and daily use into your device.
Click to expand...
Click to collapse
I mean xprivacy on xposed was the must have killer feature for any android device to turn your device into anything other than a privacy nightmare. If we can't do that any more we are f'd.
[EDIT] Looks like the new version of xprivacy, xprivacyLua is still supported for android 11, with magisk and EdXposed or LSPosed:
[CLOSED][APP][XPOSED][6.0+] XPrivacyLua - Android privacy manager [UNSUPPORTED]
XPrivacyLua Really simple to use privacy manager for Android 6.0 Marshmallow and later (successor of XPrivacy). Revoking Android permissions from apps often let apps crash or malfunction. XPrivacyLua solves this by feeding apps fake data...
forum.xda-developers.com
XPrivacyLua/README.md at master · M66B/XPrivacyLua
Really simple to use privacy manager for Android 6.0 Marshmallow and later - XPrivacyLua/README.md at master · M66B/XPrivacyLua
github.com