[UK] Android Pay UK - Not available - Oppo Find 7 and 7a

Just tried to install Android pay and apparently the device is not supported!
It fits all the criteria for being supported and I was able to install it to a sony tablet so it definitely is available in the UK. I'm just wondering if me being on omni 6.0.1 is causing issues.
Any one have any luck installing it?

Nope. I'm in the same boat. Scunnered as I thought uninstalling root would be all I needed. Anyone know if it's working with Project Spectrum ROM, as I might reinstall that. But I'm not going to the bother unless I know there is a payoff at the end of it.

Tried flashing Project Spectrum via TWRP. It allowed installing the Android Pay app, which is encouraging suggesting the ROM itself is accepted as a legit OS. Got an error message after trying to press the "+" to add a card, something like "Unable to verify system is running Android..." forgot to screenshot it.
Guessing it is also looking for an unlocked bootloader/non-OEM recovery. I might try reinstalling ColorOS recovery and then flashing Project Spectrum, but I'm not sure I want to give up Marshmallow/ad blocking just for Android Pay.

Richeyman said:
Nope. I'm in the same boat. Scunnered as I thought uninstalling root would be all I needed. Anyone know if it's working with Project Spectrum ROM, as I might reinstall that. But I'm not going to the bother unless I know there is a payoff at the end of it.
Click to expand...
Click to collapse
tried it, you can install android pay, but adding a card will not work, flash android spectrum 5.1.1 with stock recovery
---------- Post added at 12:44 AM ---------- Previous post was at 12:42 AM ----------
Richeyman said:
Nope. I'm in the same boat. Scunnered as I thought uninstalling root would be all I needed. Anyone know if it's working with Project Spectrum ROM, as I might reinstall that. But I'm not going to the bother unless I know there is a payoff at the end of it.
Click to expand...
Click to collapse
and what I noticed the ROM is not rooted SPECTRUM 5.1.1 but when you check the kernel its not stock but a rooted one? i am not sure if that matters.
---------- Post added at 12:47 AM ---------- Previous post was at 12:44 AM ----------
Richeyman said:
Tried flashing Project Spectrum via TWRP. It allowed installing the Android Pay app, which is encouraging suggesting the ROM itself is accepted as a legit OS. Got an error message after trying to press the "+" to add a card, something like "Unable to verify system is running Android..." forgot to screenshot it.
Guessing it is also looking for an unlocked bootloader/non-OEM recovery. I might try reinstalling ColorOS recovery and then flashing Project Spectrum, but I'm not sure I want to give up Marshmallow/ad blocking just for Android Pay.
Click to expand...
Click to collapse
it is not unlocked bootloader and non oem recovery, it somewhere inside the system, i think it might do with the built in kernel on the PROJECT SPECTRUM. I installed the COS lite on twrp recovery with unlocked bootloader, I can used the Android Pay easily and used it too at the gas station.:good:

imna357 said:
tried it, you can install android pay, but adding a card will not work, flash android spectrum 5.1.1 with stock recovery
---------- Post added at 12:44 AM ---------- Previous post was at 12:42 AM ----------
and what I noticed the ROM is not rooted SPECTRUM 5.1.1 but when you check the kernel its not stock but a rooted one? i am not sure if that matters.
---------- Post added at 12:47 AM ---------- Previous post was at 12:44 AM ----------
it is not unlocked bootloader and non oem recovery, it somewhere inside the system, i think it might do with the built in kernel on the PROJECT SPECTRUM. I installed the COS lite on twrp recovery with unlocked bootloader, I can used the Android Pay easily and used it too at the gas station.:good:
Click to expand...
Click to collapse
Cool. Will give it a flash as I can always restore my Omni backup if I don't like it.

TWRP/COS Lite a no-go for me here
I'll just wait for a Oneplus 3.

I am running COS V2.0.8i, and my phone is unrooted.
Android Pay installs OK on my Find 7, but I can't add any bank cards as it says "Android Pay can't be used. Google is unable to verify that your device or the software running on it is Android compatible".
If I run SafetyNet Helper, it says that the CTS Profile Match is false, which is probably why Android Pay won't run on my Find 7?
So is it true that even if I install Spectrum, Android Pay still won't work?

Related

What are the chances of eventually being able to use Android Pay on custom ROM?

Losing Android Pay is really the only thing keeping me on the stock ROM. Is this something that devs are even looking into or has everyone just resigned themselves to not using it if you want a custom ROM?
goodtimes50 said:
Losing Android Pay is really the only thing keeping me on the stock ROM. Is this something that devs are even looking into or has everyone just resigned themselves to not using it if you want a custom ROM?
Click to expand...
Click to collapse
Easy enough to achieve, depends on how the developer implements root in their ROM.
I am on LeeDroids ROM and Android pay works.
chazall1 said:
I am on LeeDroids ROM and Android pay works.
Click to expand...
Click to collapse
Really?! Have you actually added a card and used it to make payments via NFC?
chazall1 said:
I am on LeeDroids ROM and Android pay works.
Click to expand...
Click to collapse
I don't believe you.
I checked the LeeDroid thread and multiple people have reported it working. I'd just be paranoid with every AP update that it will no longer work.
Speaking off android pay, can you hide the annoying NFC icon from statusbar without root? I use my mobile banking app a lot and my bank app won't work with rooted phones (found that out on my M8). I am aware that I need the NFC on for Android Pay to work but I wish it could just turn itself on when needed
Rotten Ross said:
Speaking off android pay, can you hide the annoying NFC icon from statusbar without root? I use my mobile banking app a lot and my bank app won't work with rooted phones (found that out on my M8). I am aware that I need the NFC on for Android Pay to work but I wish it could just turn itself on when needed
Click to expand...
Click to collapse
No, unfortunately you're stuck with the icon without root.
Android Pay also works on Badboyz Sprint ROM. I used it yesterday at Walgreens.....
I have been making payments for a week now. Can add delete cards
Give it a try
Great news! Thanks guys!
failedjedi said:
I don't believe you.
Click to expand...
Click to collapse
You can believe what you want, Unlocked, Rooted, S-offed on BadBoyz ROM and Android Pay works.
chazall1 said:
I have been making payments for a week now. Can add delete cards
Give it a try
Click to expand...
Click to collapse
Hi. Noob, kinda, here...
I'm on LeeDrOid r110, systemless xposed and SuperSu, but have yet to get Android Pay to work. I've even tried disabling Xposed and SuperSu, which only crashes as I try to add a credit card, specifically, once I press the "+" icon, my screen goes black, then it crashes and I get the Android Pay white loading screen. How do you have it set up?
Oh, I'm on 1.80.xxxx, S-Off...
k_l_o said:
Hi. Noob, kinda, here...
I'm on LeeDrOid r110, systemless xposed and SuperSu, but have yet to get Android Pay to work. I've even tried disabling Xposed and SuperSu, which only crashes as I try to add a credit card, specifically, once I press the "+" icon, my screen goes black, then it crashes and I get the Android Pay white loading screen. How do you have it set up?
Oh, I'm on 1.80.xxxx, S-Off...
Click to expand...
Click to collapse
Xposed breaks android pay as it modifies the system. How are you "disabling" it? Did you flash the removal .zip in recovery? If not I would try that first and see if you can get Android Pay working. If you have done that and android pay is still not working I would flash the appropriate RUU to get back to stock, unrooted, then go through the steps to root (systemless) and flash your rom, but do not install xposed. It SHOULD work after that.
BladeRunner said:
Xposed breaks android pay as it modifies the system. How are you "disabling" it? Did you flash the removal .zip in recovery? If not I would try that first and see if you can get Android Pay working. If you have done that and android pay is still not working I would flash the appropriate RUU to get back to stock, unrooted, then go through the steps to root (systemless) and flash your rom, but do not install xposed. It SHOULD work after that.
Click to expand...
Click to collapse
Hi Bladerunner.
Thanks for replying. Didn't realize how old this thread was until after posting.
I'm using the Systemless Xposed v85.7 from this thread:
http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
There's a "Disable Xposed" toggle, I guess similar to SuperSu also has a toggle. I want Xposed more than I want Android Pay. Maybe these people that are Unlocked, Rooted, S-Off, and running LeeDrOid don't have Xposed install and that's why their Android Pay is working.
Anyway, I'm just a bit OCD or unrealistic in thinking I can have it all.
And I would "Thank" you, but reached my quota today. Will make up tomorrow.
Cheers...
Android Pay works without issue on a systemless rooted stock ROM even... Just don't modify system and you're good. For now anyway.
schmeggy929 said:
You can believe what you want, Unlocked, Rooted, S-offed on BadBoyz ROM and Android Pay works.
Click to expand...
Click to collapse
Hi schmeggy.
Any chance you don't have Xposed installed? I don't see it listed in your signature. I think that's the true culprit. Beside being on different ROM, I'm on LeeDrOid which is systemless, Xposed is the only difference with your setup.
---------- Post added at 01:57 PM ---------- Previous post was at 01:55 PM ----------
EtherealRemnant said:
Android Pay works without issue on a systemless rooted stock ROM even... Just don't modify system and you're good. For now anyway.
Click to expand...
Click to collapse
Thank you for your feedback.
I've tried to maintain systemless, but still no joy. There are posts that state Android Pay works for them and my HTC 10 would be complete if I can solve this issue.
FYI...
Since I love picking at scabs, can't leave well enough alone, and have a severe case of update-itus, last one is a whole different can of worms, I followed my hunch and hope this will help anyone else curioused/interested.
I dirtied flashed my ROM, LeeDrOid, which delete/wrote-over, idk because they're the geniuses, not me, the Xposed Framework, I was able to verify via SafetyNet Helper and being able to add a credit card in Android Pay, that YES, Xposed Framework bunks Android Pay. I will try to make a purchase during lunch today and will update.
k_l_o said:
Hi schmeggy.
Any chance you don't have Xposed installed? I don't see it listed in your signature. I think that's the true culprit. Beside being on different ROM, I'm on LeeDrOid which is systemless, Xposed is the only difference with your setup.
---------- Post added at 01:57 PM ---------- Previous post was at 01:55 PM ----------
Click to expand...
Click to collapse
I see you found the issue, No I do not use Xposed.
k_l_o said:
FYI...
Since I love picking at scabs, can't leave well enough alone, and have a severe case of update-itus, last one is a whole different can of worms, I followed my hunch and hope this will help anyone else curioused/interested.
I dirtied flashed my ROM, LeeDrOid, which delete/wrote-over, idk because they're the geniuses, not me, the Xposed Framework, I was able to verify via SafetyNet Helper and being able to add a credit card in Android Pay, that YES, Xposed Framework bunks Android Pay. I will try to make a purchase during lunch today and will update.
Click to expand...
Click to collapse
Too bad we havent been able to figure out a xposed app that tricks safetynet api into thinking its all good, then we could have it all
yea, even with systemless xposed, you still need to disable xposed via the toggle switch, and then reboot to get android pay to work. I managed to get my 2gb of free verizon data for making 3 soda purchases at work. Although, on a semi related note, android pay doesnt like one of my CC's with SE chip, it likes my other 2 just fine.

Kyocera Hydro Reach C6743

I have a Reach through Boost. Nice phone except for storage issues. Currently running 5.1.1. Unlike other Kyoceras it has a developer's option to allow unlocking of bootloader. Does anyone know how to root and if there is a Android 6 rom that can be used with the Reach.
You have to go into developer mode and check OEM Unlock. KingRoot did the trick for me after that.
Is that all? Cuz it didn't change a dang thing for me, bro.
Sent from my C6743 using XDA Free mobile app
aces5150 said:
You have to go into developer mode and check OEM Unlock. KingRoot did the trick for me after that.
Click to expand...
Click to collapse
I check OEM unlock and authorized debugging and still nothing seems to be working for me. did you do anything else for your C6743
root
Kilparis87 said:
I check OEM unlock and authorized debugging and still nothing seems to be working for me. did you do anything else for your C6743
Click to expand...
Click to collapse
swicth homes bc found security in it it will lock till reset unless other wise
What do u mean by switch homes?
Yeah I can't get this phone rooted. I've taken days researching. Nothing.
I enabled OEM unlocking, installed Kingroot 5.2.1, and was able to achieve root on first try.
---------- Post added at 06:29 PM ---------- Previous post was at 06:23 PM ----------
Oops, spoke too soon, says in Kingroot, this model restricts ROOT authorization, even though it says it gained root successfully... so wtf then how did you get root if its restricted?? Tha Fuuu..
Took me like 6 times, restarting my phone after each time. Kingsroot 5.2.1
360root
activate phone
download system update
360root
root
phone reboots
root again
etc
just temp root
wait a few days
??
---------- Post added at 03:04 AM ---------- Previous post was at 02:59 AM ----------
Ggggg
successful root
I have managed to give root access to my Kyocera Hydro Reach with PermRoot in its latest version
wow
Arguzhan said:
I have managed to give root access to my Kyocera Hydro Reach with PermRoot in its latest version
Click to expand...
Click to collapse
mine was, but the company keeps blocking it and lucky patcher, i still use the phone for wi-fi but has no connection with any carriers, if you find a recovery or rom id like to have it, plus id like to connect it to my 32bit tablot if you have links to software, its not compatiable with my windows 8.1
Root Kyocera c6743
Kingroot roots device but root checker finds no root privileges...several subsequent attempts using same app actually began requesting superuser access, but eventually produced no joy all scenarios
---------- Post added at 11:13 AM ---------- Previous post was at 10:57 AM ----------
As I stated kingroot will do the job but it seems to be ONLY a temp root...grrrrr. will check adb/fastboot for manual solution
that's a nice phone, its not write/ can't be rooted, damages the core, I had (0)
---------- Post added at 03:34 PM ---------- Previous post was at 03:31 PM ----------
lexcin said:
that's a nice phone, its not write/ can't be rooted, damages the core, I had (0)
Click to expand...
Click to collapse
does anyone know how to use kitchen, I don't have a good p.c right-off hand, I need a custom recovery...
thanks
I was thinking of something so I'll just quickly say it.
1. Kingroot Temp Root
2. CWM app?
3. Magisk Root
I don't know if this will work.
Edit: Yeah no doesn't work
I think you need to flash the phone with a pre-rooted stock rom
get msl code, enable usb
use kyocera flashing tool exe
stick majisk in the boot folder and flash ?
---------- Post added at 11:51 PM ---------- Previous post was at 11:46 PM ----------
the new kyocera hydro reach are patched and won't root had a factory boost a few months ago, and it was patched won't root at all
Research
So I'll try researching a way to root this device so I'll back if I find anything
had one a few Christmas ago, got all excited, the phone and the contract, the 3g went out a month or so later... and that was about it for me, these days I'm just using a cheap phone, with insurance or warranty, still takes a few weeks to replace... I'm trying the Blu mtk veiw 1 right now 25 bucks

Obtaining Root/unlocked BootloaderU

So kinda glancing around and trying to dig, it seems if you order the phone from Google Store, you can unlock bootloader and root on any OS. If obtained from Verizon, you cannot root if it already has 7.1.1? Is this statement correct? So it seems to best order it from Google Store it seems?
bigmike35 said:
So kinda glancing around and trying to dig, it seems if you order the phone from Google Store, you can unlock bootloader and root on any OS. If obtained from Verizon, you cannot root if it already has 7.1.1? Is this statement correct? So it seems to best order it from Google Store it seems?
Click to expand...
Click to collapse
You have it exactly right.
I just came across the same consensus. If it helps, I have the Pixel XL 128 with Verizon, version 7.1.1 and my build is NOF26V.
The verizon pixel xl's are still shipping with NDE63P, which is 7.1 and still not patched against depixel8. So for the time being you can get one from either.
Sent from my Pixel XL using Tapatalk
wyrdtrtle said:
The verizon pixel xl's are still shipping with NDE63P, which is 7.1 and still not patched against depixel8. So for the time being you can get one from either.
Click to expand...
Click to collapse
Not from what I've seen. People all over are saying the Verizon units are now shipping with 7.1.1. Get it from Google if you want to be able to unlock.
I wont argue that, i received mine in early feb, the 5th i think, so it may have changed. So to be safe google is the right choice, i just couldnt pass up the chance to get it for half price, so i took a chance and it paid off. Literally.
Sent from my Pixel XL using Tapatalk
Im very disappoint and upset, I got Pixel XL came with 7.1.1 (NOF26V) VZW So, I have been research on the website and mostly They said 7.1 to 7.1.1 "early" It's seem I can't get unlock bootloader anymore, but maybe in the future could be exploit patch?
The answer is maybe, but since the guys that did it before i dont believe are even working on another, i wouldnt get your hopes up.
Sent from my Pixel XL using Tapatalk
Verizon is definitely still shipping them with only 7.1. I just got mine 4 days ago and could see it was wanting to update. I didn't take it because I was trying to unlock bootloader with depixel8. Depixel8 wasn't working i can't remember the error but it was hanging on the first step, trying to push it to /data/local/tmp. I tried rebooting to start over and when it came back up it had 7.1.1 on it and now I can no longer try unlocking or rooting. So you can still get it from Verizon, just don't let it reboot before you get it unlocked
Sent from my Pixel XL using Tapatalk
I wouldn't even take the risk at this point. Spend a lil more out of pocket and by it directly from Google if you're looking to unlock. Some vzw models are shipping with 7.1.1 now. Would kinda suck to open the box and not be able to unlock. Best bet for anyone is to buy from Google if you plan on unlocking.
Are you sure you cannot root even using the TWRP method?
I saw a post regarding TWRP then flashing SU
I just ordered mine today, I will let you know if I get it without the update
---------- Post added at 03:34 PM ---------- Previous post was at 03:31 PM ----------
http://www.theandroidsoul.com/root-pixel-xl-magisk/
This is the TWRP method I was referencing when you are on 7.1.1
---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------
msmall82 said:
Are you sure you cannot root even using the TWRP method?
I saw a post regarding TWRP then flashing SU
I just ordered mine today, I will let you know if I get it without the update
---------- Post added at 03:34 PM ---------- Previous post was at 03:31 PM ----------
http://www.theandroidsoul.com/root-pixel-xl-magisk/
This is the TWRP method I was referencing when you are on 7.1.1
Click to expand...
Click to collapse
Actually looks like you have to use depixel8 to unlock the bootloader in order to flash SU with TWRP, I am hoping I get one that has the older version on it and isn't on 7.1.1
I don't feel like kicking out 860 when I can just have it billed by 30 a month to my verizon account.
msmall82 said:
Are you sure you cannot root even using the TWRP method?
I saw a post regarding TWRP then flashing SU
I just ordered mine today, I will let you know if I get it without the update
---------- Post added at 03:34 PM ---------- Previous post was at 03:31 PM ----------
http://www.theandroidsoul.com/root-pixel-xl-magisk/
This is the TWRP method I was referencing when you are on 7.1.1
---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------
Actually looks like you have to use depixel8 to unlock the bootloader in order to flash SU with TWRP, I am hoping I get one that has the older version on it and isn't on 7.1.1
I don't feel like kicking out 860 when I can just have it billed by 30 a month to my verizon account.
Click to expand...
Click to collapse
Do not follow anything in that link, it is very out of date. And correct, you can't flash or boot TWRP until the bootloader is unlocked. And you cant root it until you get twrp running
If your Verizon phone comes with 7.1.1 or you update it to 7.1.1 before you unlock it you are done. Up to you if the gamble is worth it, just making sure you know what is what.
Well I am going to find out tomorrow when I get my pixel, is there an easy way to make sure it doesn't run the OTA update when opening it from the box? If I keep Wifi off and don't put in my SIM will that guarantee it or can you even get to the point to check the version without a SIM loaded? I am keeping my Galaxy Note ...does the Pixel come with the SIM loaded already and require activation?
I want to make sure it doesn't take the OTA update if I am lucky enough to get one without it. I use the Wifi tethering often when I am travelling as well as other root apps like Ti-Backup, Root Explorer, Ect...
msmall82 said:
Well I am going to find out tomorrow when I get my pixel, is there an easy way to make sure it doesn't run the OTA update when opening it from the box? If I keep Wifi off and don't put in my SIM will that guarantee it or can you even get to the point to check the version without a SIM loaded? I am keeping my Galaxy Note ...does the Pixel come with the SIM loaded already and require activation?
I want to make sure it doesn't take the OTA update if I am lucky enough to get one without it. I use the Wifi tethering often when I am travelling as well as other root apps like Ti-Backup, Root Explorer, Ect...
Click to expand...
Click to collapse
Don't install the SIM, skip setup, and no wifi. You may have to connect WiFi for a second or two before the slider in dev options will work.
TonikJDK said:
Don't install the SIM, skip setup, and no wifi. You may have to connect WiFi for a second or two before the slider in dev options will work.
Click to expand...
Click to collapse
Best bet would be to use the Android toolkit in the Dev area and load depixel8? I've rooted 3 phones before but this one is quite different. I've used ADB, ect...just trying to find the "right" way to do it, can't seem to find an exact proper way other than this :
https://www.xda-developers.com/root-is-now-available-for-the-google-pixel-and-pixel-xl/
---------- Post added at 06:06 PM ---------- Previous post was at 06:01 PM ----------
TonikJDK said:
Don't install the SIM, skip setup, and no wifi. You may have to connect WiFi for a second or two before the slider in dev options will work.
Click to expand...
Click to collapse
Well I obv have to get into the phone and check the version of the phone and enable Dev options and USB debugging before I can get into the phone using ADB...you're saying just skip the setup, keep wifi turned off and then *pray* it is 7.1 and then go ahead and install depixel8 and unlock...?
---------- Post added at 06:21 PM ---------- Previous post was at 06:06 PM ----------
msmall82 said:
Best bet would be to use the Android toolkit in the Dev area and load depixel8? I've rooted 3 phones before but this one is quite different. I've used ADB, ect...just trying to find the "right" way to do it, can't seem to find an exact proper way other than this :
https://www.xda-developers.com/root-is-now-available-for-the-google-pixel-and-pixel-xl/
---------- Post added at 06:06 PM ---------- Previous post was at 06:01 PM ----------
Well I obv have to get into the phone and check the version of the phone and enable Dev options and USB debugging before I can get into the phone using ADB...you're saying just skip the setup, keep wifi turned off and then *pray* it is 7.1 and then go ahead and install depixel8 and unlock...?
Click to expand...
Click to collapse
This is my plan, skip everything, get into the phone, hope to god it's 7.1, enable USB Debugging and Dev options from Settings...then use depixel8 to unlock the boot loader, then I am lost. Checked around 40 threads on here and have found 10 different ways to root...this is the XDA root :
How to Install SuperSU on your Pixel
As Chainfire mentions in his Google+ post, you will need to first download the boot-to-root images for the Pixel or Pixel XL off of his website. You can click here to download the zip for the Google Pixel, or click here to download the zip for the Google Pixel XL. After downloading the zip, you need to fastboot boot the boot-to-root image, DO NOT fastboot flash the image! In other words, the only command you’ll need for the two devices is the following:
fastboot boot boot-to-root.img
Wait a few minutes, and after a few reboots you’ll be booted up with full root access. Yay!
msmall82 said:
......then I am lost. Checked around 40 threads on here and have found 10 different ways to root...
Click to expand...
Click to collapse
There are a lot of ways because this phone was so different, so a lot of what you see is the testing and changes that can from that.
So, after it is unlocked update it to 7.1.1 and then:
Download 2.7.9 SR3 SuperUser and copy it to your phone.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Download TWRP RC3 and copy it to your fastboot folder.
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
Using other versions than above will bootloop you. Reboot the phone into bootloader mode. Power and Vol down.
fastboot BOOT twrpFilename.img Where twrpfilename.img is the name of the TWRP file you just downloaded. Note is says boot in the command, not flash.
That will boot the phone into TWRP. Select Install and install the SU zip you copied to the phone above. And reboot the phone, done.
---------- Post added at 01:06 AM ---------- Previous post was at 01:05 AM ----------
And here is the link to the proper fastboot version.
https://developer.android.com/studio/releases/platform-tools.html
The box that the phone comes in has the software version on it. So you'll know before even powering it on. I got my regular pixel last week and it had 7.1.
Best is to disable automatic OTA upon opening the box when you find that you have 7.1. So there is a better chance of getting the exploit to work even after reboots.
Pull the sim before powering it up
Sent from my Pixel XL using Tapatalk
wyrdtrtle said:
Pull the sim before powering it up
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Exactly, power on with no sim and skip any set up including wifi. No reason to do any set up as the bootloader unlock with wipe the device. Enable ADB and get to unlocking straight away. No sim and no wifi means there is zero way it can update itself on you.
Sent from my Pixel XL using Tapatalk

Attempting to get VZW Note 4 to Kitkat

Hello XDA! First post here and I’ve been reading a lot since I got my phone. I seem to have found a solution, (maybe), but I'm not clear on a few vital things.
A little back story… my dad just gave me his Verizon Note 4. It was on Marshmallow, but has since been downgraded to Lollipop 5.1.1, N910VVRU2BPA1. From what I understand it still has the locked MM bootloader (?).
I’m planning to root the phone, but only if I can further downgrade it to Kitkat 4.4.4. I’ve read through the thread “Stabilized process used to unlock Bootloader” and it seems it should unlock the bootloader. However, I’ll end up with a “Developer Edition” phone. This leads to my questions…
1) Once successfully rooted and the bootloader is unlocked, will I be able to downgrade the phone to Kitkat by just flashing the firmware in Odin? I really don’t care if I lose root, I just want Kitkat on the phone.
2) Can I just flash the “retail” version of Kitkat from Sammobile or do I need a “developer edition” Kitkat (if there even is one)?
3) Can someone advise me if what I imagine might be possible is even doable?
Any help is greatly appreciated! I’m new to this so if these are just funky questions, please excuse. Lots to learn! Thanks so much!!!
A little help please!
Someone must know this.
Can I or can't I flash the "retail" Kitkat firmware onto a "supposed" Dev Edition rooted to unlock the bootloader?
I hope someone can clarify this before I do something stupid!
Thanks!
Hey
Do you have teamviewer I can help u out
Jwazz94 said:
Do you have teamviewer I can help u out
Click to expand...
Click to collapse
Thanks, but I don't need help doing it, I just need someone to answer the questions so I don't mess up the phone.
Yes you can, make sure to unlock bootloader first. But when you flash you will loose bootloader unlock. I have a guide where I could use the lollipop bootloader and use kitkat. I really love kitkat and with root you have lots of potential for battery savings and more!
---------- Post added at 08:35 PM ---------- Previous post was at 08:32 PM ----------
If you would like to downgrade the bootloader add a twrp custom recovery and use the kitkst method I have and you can have the best phone, I also would recommend you buying a zerolemon battery and case.
But if you do just want to have full stock and have all the bloat ware on it you can like you stated unlock the bootloader and then flash the retail kitkat and your all set and downgraded
---------- Post added at 08:39 PM ---------- Previous post was at 08:35 PM ----------
https://forum.xda-developers.com/no...tkat-5-1-1-t3432452/post68903783#post68903783
codydixon said:
Yes you can, make sure to unlock bootloader first. But when you flash you will loose bootloader unlock. I have a guide where I could use the lollipop bootloader and use kitkat. I really love kitkat and with root you have lots of potential for battery savings and more!
---------- Post added at 08:35 PM ---------- Previous post was at 08:32 PM ----------
If you would like to downgrade the bootloader add a twrp custom recovery and use the kitkst method I have and you can have the best phone, I also would recommend you buying a zerolemon battery and case.
But if you do just want to have full stock and have all the bloat ware on it you can like you stated unlock the bootloader and then flash the retail kitkat and your all set and downgraded
---------- Post added at 08:39 PM ---------- Previous post was at 08:35 PM ----------
https://forum.xda-developers.com/no...tkat-5-1-1-t3432452/post68903783#post68903783
Click to expand...
Click to collapse
Thank you very much for responding! I very much appreciate it!
I don't care to keep root and just want the phone on Kitkat. In the future I may decide to root it and play around with roms and such, but not right now. I can now go ahead and attempt it with confidence. I'll let you know how it goes!
Thanks again! :good:
Well, tried all kinds of stuff and it was a no go.
Was able to get the phone rooted finally... had to use KingOroot. Kingroot failed to work no matter how many versions I tried. Once rooted, checked download mode and it indicated Developer. However, I was unable to install retail KK or KK stock restore in Odin 3.10 and 3.09. Since the flash failed, putting it into recovery ended up in an error about "Software update failed"... use a PC, blah, blah, blah. Wouldn't let me go anywhere in recovery.
Decided to try flashing LP 5.1.1 back to the phone and it flashed ok in Odin 3.09. Phone is back up, but lost root, (expected), and I'm back again at square 1. At least the phone isn't bricked! LOL!
Maybe the problem is that this phone has an MM bootloader so eventhough it's unlocked, you can't flash KK to it? Don't know, but I guess I'm back to trying to find this out.
Good experience so far eventhough this attempt didn't get me anywhere! Well... at least I know how to root it and unlock the bootloader!

[guide][noob stuck][bootloader locked][rom cant install]

Yesterday, tried to update to new 11.0.2 with an stupid mistake, you click "flash" and dont untick this crapy "clean and lock"
so it RELOCKED THE BL and cant install the fashed rom because CN and global
IT MUST BE DONE "CLEAN ALL"
phone : CN RN8P
rom : actually global 10.4.2
begonia_global_images_V11.0.2.0.PGGMIXM_20191201.0000.00_9.0_global
TOOLS NEEDED:
miflash_unlock-en-3.5.910.35
Miflash
so after hours of desperate research, found a way , here, for unlocking bootloader...oh yeah you will laughing and say "its simple"
not so the easiest way when you are in the mad state
so if you did as me, you end with bootloop and stuck to MI recover 3, no other choice to erase data or mi assistant or reboot
so fortunately the fastboot mode is still here..... so
1)reboot with volume- key and let it done to fastboot
2)at this point any "fastboot oem unlock" ends with argc 2, no unlock possible
so as listed in other topics,
3)do miflash unlock as always requested for flashing rom in tutorials and make "unlock"
4)the software will go to 100% and done the phone reboot itself and says "unlocked"
5)do "miflash " select the rom directory where its dezipped and TICK "CLEAN ALL"
6) do "flash"
7)wait 5 minutes
8) when done it reboots with success
at this point let it go and install the rom if you want stock state
for root and twrp follow here
https://forum.xda-developers.com/re...edmi-note-8-pro-guide-firmwares-twrp-t3987121
and do that
1) follow the guide to install twrp with fastboot
2) follow those points to flash magisk 20.1
Quote:
Originally Posted by Kediraksith
WOOHOO!!! SUCCESS!!! FINALLY!!!
Apparently, we just need to this extra step to avoid bootloop "10. Advanced (put 2 ticks) RM Force encrypt "
I redid everything using MiFlashTool and this is my personal guide, improved upon the above guide.
1. Download Magisk 20.1
2. Reboot to TWRP Recovery
3. Make Wipe and Format Data
4. Copy and install Magisk 20.1
5. Advanced > File Manager >system_root / system > Delete the recovery_fromboot.p file
6. Advanced (put 2 checkmarks) Close AVB2.0
7. Advanced (put 2 ticks) RM Force encrypt
11. Reboot System
12. Pass authorization, install the Magisk app-release.apk
i followed it and runs with 11.0.2 and magisk 20.1
see pics
enjoy
You tried and guaranteed to work? Last time I used guide here and bricked my phone. Paid $US29 for authorised account.
---------- Post added at 11:53 PM ---------- Previous post was at 11:47 PM ----------
I can see some of contents are copied from somewhere else in "How to Root and installing Google Pay" section.
This is NOT a completely guide. Lack of installing TWRP after rom flash. Also in installing Google Pay, why to delete old magisk? Don't have it installed at all. Also what's the purpose of install superSU?
I understand what you are talking but if someone follows your instruction, may be confused and brick the phone.
idog8818 said:
You tried and guaranteed to work? Last time I used guide here and bricked my phone. Paid $US29 for authorised account.
---------- Post added at 11:53 PM ---------- Previous post was at 11:47 PM ----------
I can see some of contents are copied from somewhere else in "How to Root and installing Google Pay" section.
This is NOT a completely guide. Lack of installing TWRP after rom flash. Also in installing Google Pay, why to delete old magisk? Don't have it installed at all. Also what's the purpose of install superSU?
I understand what you are talking but if someone follows your instruction, may be confused and brick the phone.
Click to expand...
Click to collapse
Exactly... Why both MagiskSU and SuperSU?
Hi,
TWRP and ROOT process is not my guide, i dont take credits for that, they are 2 others users work not mine.
mine is not to be bored with BL relocked with miflash
for sure it occurs in many cases....
the process for flashing is seems not to be updated, i have a CN phone with a global ROM, tutorial is initially for global phones.
it needs a new guide for CN phones and global rom
BUT
i follow the part wrote by
Originally Posted by Kediraksith
in page 10
i made that 4 times now, in my case, with my process, installed the global rom and flashed TWRP and deleted the script who delete the recovery at reboot
and so
il follown the rules in twrp
you can juste flash supersu, it is included in the rom, it install magisk 19.4 and let it go as that.
but if you want to be updated to 20.1
you can follow just flash twrp and all wipes and decrypt and avdb2.0 close
you must download magisk 20.1 manually and install it twrp
i dont have another procedure to follow, just the mix with all indicactions in the guide for begonia twrp and root
Helhound0 said:
Exactly... Why both MagiskSU and SuperSU?
Click to expand...
Click to collapse
ask that to the original writer of the guide madsponge26, perhaps it need to be updated to add CN phone and global rom case
Redmi Note 8 Pro Guide [Firmwares | ROOT CN/GLOBAL | TWRP Recovery]
3,207 posts
Thanks: 2,990
By madsponge26, Senior Member on 20th October 2019, 06:33 PM
idog8818 said:
You tried and guaranteed to work? Last time I used guide here and bricked my phone. Paid $US29 for authorised account.
---------- Post added at 11:53 PM ---------- Previous post was at 11:47 PM ----------
I can see some of contents are copied from somewhere else in "How to Root and installing Google Pay" section.
This is NOT a completely guide. Lack of installing TWRP after rom flash. Also in installing Google Pay, why to delete old magisk? Don't have it installed at all. Also what's the purpose of install superSU?
I understand what you are talking but if someone follows your instruction, may be confused and brick the phone.
Click to expand...
Click to collapse
you are lucky to have an authorized account
i asked to have one to xiaomi tech service
no answer for now
idog8818 said:
You tried and guaranteed to work? Last time I used guide here and bricked my phone. Paid $US29 for authorised account.
.
Click to expand...
Click to collapse
if not, i would not be here to answer
harmakhis said:
if not, i would not be here to answer
Click to expand...
Click to collapse
I paid on S-unlock, NOT from Mi store rep or service center. I'm sure I can get fix for free at Mi store but I don't want to wait for 2 months sending phone back to China.
I have China phone with Global rom, I bought from Mi store in China. Since I get bricked last week. I will take extra care on flash rom etc.
---------- Post added at 10:50 PM ---------- Previous post was at 10:44 PM ----------
Helhound0 said:
Exactly... Why both MagiskSU and SuperSU?
Click to expand...
Click to collapse
Spent time on it and I realised SuperSU may contains some contents that MagiskSU needs. Installing SuperSU is kind of installing old version of MagiskSU to patch boot image. Then Magisk 20.1 installation is to "upgrade", although it looks like a new installation. I also noticed it may need to uninstall old version before new 20.1 upgrade. That's why uninstaller may be necessary. No definite clue, just guessing.
idog8818 said:
I paid on S-unlock, NOT from Mi store rep or service center. I'm sure I can get fix for free at Mi store but I don't want to wait for 2 months sending phone back to China.
I have China phone with Global rom, I bought from Mi store in China. Since I get bricked last week. I will take extra care on flash rom etc.
---------- Post added at 10:50 PM ---------- Previous post was at 10:44 PM ----------
Spent time on it and I realised SuperSU may contains some contents that MagiskSU needs. Installing SuperSU is kind of installing old version of MagiskSU to patch boot image. Then Magisk 20.1 installation is to "upgrade", although it looks like a new installation. I also noticed it may need to uninstall old version before new 20.1 upgrade. That's why uninstaller may be necessary. No definite clue, just guessing.
Click to expand...
Click to collapse
Well i don't know about any of that because i rooted two days back with just magisk 20 and it works perfectly...
You DO NOT NEED TO INSTALL BOTH SUPERSU AND MAGISKSU!!! Its idiotic!!
Helhound0 said:
Well i don't know about any of that because i rooted two days back with just magisk 20 and it works perfectly...
You DO NOT NEED TO INSTALL BOTH SUPERSU AND MAGISKSU!!! Its idiotic!!
Click to expand...
Click to collapse
May I know whether you are using China variant with Global rom? And also what's your process to install the MAGISK?
idog8818 said:
May I know whether you are using China variant with Global rom? And also what's your process to install the MAGISK?
Click to expand...
Click to collapse
I'm using the global version with the global firmware. You just have to unlock the bootloader, enable OEM unlocking and USB debugging, fastboot flash lrtwrp, delete replace stock recovery on boot, disable AVB2.0 from the twrp advanced menu, and click on install root from the same menu...
Helhound0 said:
I'm using the global version with the global firmware. You just have to unlock the bootloader, enable OEM unlocking and USB debugging, fastboot flash lrtwrp, delete replace stock recovery on boot, disable AVB2.0 from the twrp advanced menu, and click on install root from the same menu...
Click to expand...
Click to collapse
This is probably why you can install everything. It seems using China variant and global rom will cause issues.
idog8818 said:
This is probably why you can install everything. It seems using China variant and global rom will cause issues.
Click to expand...
Click to collapse
Yup... I thought that was a known fact from the get go.... You'll be fine if you switch to the Chinese variant and root that instated of trying to root the global version on a Chinese device..
Helhound0 said:
Yup... I thought that was a known fact from the get go.... You'll be fine if you switch to the Chinese variant and root that instated of trying to root the global version on a Chinese device..
Click to expand...
Click to collapse
Too much Ads/app preloaded, No google etc. Mess. Use global rom is better but NFS doesn't work, No WWS/Coles touch and pay. lol
idog8818 said:
Too much Ads/app preloaded, No google etc. Mess. Use global rom is better but NFS doesn't work, No WWS/Coles touch and pay. lol
Click to expand...
Click to collapse
That sounds bad. But there are workarounds to some of those problems am i wrong? You can debloat using Szaki tools to get rid of preloaded apps, flash OpenGapps to get Google services and someone here mentioned that uninstalling MSA (Miui System Ads) and changing the region to UK might disable the ads... As for NFC, does the Chinese variant even have the hardware needed for that even if you flash the global version?
Helhound0 said:
That sounds bad. But there are workarounds to some of those problems am i wrong? You can debloat using Szaki tools to get rid of preloaded apps, flash OpenGapps to get Google services and someone here mentioned that uninstalling MSA (Miui System Ads) and changing the region to UK might disable the ads... As for NFC, does the Chinese variant even have the hardware needed for that even if you flash the global version?
Click to expand...
Click to collapse
Too much work for Ads and gapps. Flash global rom is quicker and clean.
NFC is available in Chinese variant however after unlock BL GPay won't be happy and will not allow to use this is why I need to install Magisk. However Chinese variant with global Rom means bootloops. I've paid $US29 to fix.
idog8818 said:
Too much work for Ads and gapps. Flash global rom is quicker and clean.
NFC is available in Chinese variant however after unlock BL GPay won't be happy and will not allow to use this is why I need to install Magisk. However Chinese variant with global Rom means bootloops. I've paid $US29 to fix.
Click to expand...
Click to collapse
To each his own i guess.. I would personally prefer being on the same version as the devices region if it means i'll have a more stable device on my hand.

Categories

Resources