Hey,
I purchased a Samsung Note 8 (SM-N950F) a couple of years from Amazon.de. The phone was unlocked, since then new OS releases were really slow so I decided to download the Pie update from Sammobile and updated my phone via Odin. The phone is using official firmware and has never been rooted yet when I try to activate Google Pay I receive the following error; "Couldn't finish setup to pay in shop. This phone can't be used to pay in shops. This may be because it is rooted or altered in some other way."
I spoke to Samsung and told me to check a few things and they confirmed the phone is not rooted, I spoke to Google and they told me I should ask Samsung how to unlock the bootloader but Samsung said doing this would void my warranty. I'm a bit confused as to what to do, is there a stock pie rom I can use without voiding my warranty?
Thanks a lot, appreciate any help
Regards
p4rma
The only thig i can think of is that, the phone you've got has a CSC code of a region where Google Pay is not supported, or maybe you are living in a country that do not support Google Pay.
If you think I'm wrong, flash stock pie firmware.
Flashing stock offiicial binaries doesn't need your bootloader to be unlocked.
Thanks for the quick reply I will try this. Would Samsung have their own stock pie rom? Kinda wish I just waited for the pie update rather than flashing. Its annoying I can't use Netflix either as it says my device is not compatible.
I just checked and my bootloader is N950FXXU7DSJ1
Hey there,
I also faced the same issue when using GPay. I recommend trying these steps, might workout for you (it did for me):
Before doing this I recommend Backing your phone up, sometimes phone might erase user data but I didn't lose data.
1. Goto Settings > About Phone > Software Information > Build Number (Tap this thing 7 times). It should display a toast saying Developer options has been enabled.
2. Go back to Settings > Developer Options.
3. Turn on USB Debugging first, just in case.
4. See if OEM Unlock is turn on, if it is then turn it off.
5. Try turning it back on if it is turned off, you phone will reboot if you do so. Once rebooted, go back and turn it back off.
You shall be able to use Google Pay.
Note: These are the exact same steps that I did and it started to work for me.
As for changing CSC its a little complicated (by rooting its way easier but then you will lose Samsung Pay & some other Knox features). You will need to do a couple of steps and it also leads to erasing of user data.
If you don't wanna risk anything, why not try SPay. It might be supported in your country.
Unix_Dominator said:
Hey there,
I also faced the same issue when using GPay. I recommend trying these steps, might workout for you (it did for me):
Before doing this I recommend Backing your phone up, sometimes phone might erase user data but I didn't lose data.
1. Goto Settings > About Phone > Software Information > Build Number (Tap this thing 7 times). It should display a toast saying Developer options has been enabled.
2. Go back to Settings > Developer Options.
3. Turn on USB Debugging first, just in case.
4. See if OEM Unlock is turn on, if it is then turn it off.
5. Try turning it back on if it is turned off, you phone will reboot if you do so. Once rebooted, go back and turn it back off.
You shall be able to use Google Pay.
Note: These are the exact same steps that I did and it started to work for me.
As for changing CSC its a little complicated (by rooting its way easier but then you will lose Samsung Pay & some other Knox features). You will need to do a couple of steps and it also leads to erasing of user data.
If you don't wanna risk anything, why not try SPay. It might be supported in your country.
Click to expand...
Click to collapse
Thank you Unix_Dominator!!!!!!!!! This worked, I can now use Google Pay & Netflix
p4rma said:
Thank you Unix_Dominator!!!!!!!!! This worked, I can now use Google Pay & Netflix
Click to expand...
Click to collapse
I'm glad it worked out for you too!!!
Unix_Dominator said:
I'm glad it worked out for you too!!!
Click to expand...
Click to collapse
I noticed it has stopped working again but I'll try your method again. Did you have the issue or is yours pemanently fixed?
Thanks
p4rma said:
I noticed it has stopped working again but I'll try your method again. Did you have the issue or is yours pemanently fixed?
Thanks
Click to expand...
Click to collapse
It has been permanently fixed for me, I never faced any issue with GPay after that method (I don't use Netflix though). Could you also see if you phone is updated to the latest version, if so also check if your phone has a fix for Stagefright.
To check if you are vulnerable to that exploit download this app it will tell you Click Here . If it fails, try OEM unlock as off and see, might fix it.
I really hope this issue doesn't come back for you.
Related
Hey,
So i used the SRK tool to try and root my VIE-L09C40 (P9 Plus)
Something seemed to happended during the rooting procedure and when i entered e-recovery it said it had to Download a new version, but couldnt connect to internet via wifi.
Any ways it seemed to work after a while but now i have no keyboard at all, so i cant literally start my phone.
it starts, boots the EMUI 5.0 logo and goes through the information a terms, i click the ok button and thats fine.
Next it tells me to sign in to my wifi, i select my wifi and when i go to type the password all i have is google voice as a keyboard, ive searched and searched but cannot find a way around it, also the frp has tripped on phone so i cannot log in to my google account without a keyboard.
How can i get around this?
do i have to flash parts of firmware?
any help would be great, i sent it away to hauwei and they say warranty void due to software!, can only assume something wrong was flashed?
Waiting for phone to be returned now, please help
I had the exact same issue last night as well. No keyboard and only an option to enter details with voice.
Ended up with an essentially bricked phone. Couldn't find any info on the problem online, so I have to improvise.
I'm starting from scratch after formatting etc. using stock oeminfo, recovery and rolling back to Marshmallow. (fingers crossed ADB will let me, because it was giving me errors before)
Will let you know if I'm successful and the steps I took.
=====================
tolerant said:
Hey,
So i used the SRK tool to try and root my VIE-L09C40 (P9 Plus)
Something seemed to happended during the rooting procedure and when i entered e-recovery it said it had to Download a new version, but couldnt connect to internet via wifi.
Any ways it seemed to work after a while but now i have no keyboard at all, so i cant literally start my phone.
it starts, boots the EMUI 5.0 logo and goes through the information a terms, i click the ok button and thats fine.
Next it tells me to sign in to my wifi, i select my wifi and when i go to type the password all i have is google voice as a keyboard, ive searched and searched but cannot find a way around it, also the frp has tripped on phone so i cannot log in to my google account without a keyboard.
How can i get around this?
do i have to flash parts of firmware?
any help would be great, i sent it away to hauwei and they say warranty void due to software!, can only assume something wrong was flashed?
Waiting for phone to be returned now, please help
Click to expand...
Click to collapse
dmccort said:
I had the exact same issue last night as well. No keyboard and only an option to enter details with voice.
Ended up with an essentially bricked phone. Couldn't find any info on the problem online, so I have to improvise.
I'm starting from scratch after formatting etc. using stock oeminfo, recovery and rolling back to Marshmallow. (fingers crossed ADB will let me, because it was giving me errors before)
Will let you know if I'm successful and the steps I took.
=====================
Click to expand...
Click to collapse
Good luck, i did read that it might be possible to install the base firmware back to it and then update again.
Im sure we are not the only people this has happened to and if you succesfully do this, maybe consider making a full step by step guide so to help others.
Fingers crossed
:good:
Will do my best.. So far it's been a major. I've managed to flash a working stock ROM and boot up. But there are a few things to smooth out. Such as, I have no IMEI number now and the build is C900, also the bootloader is modified.
To get it to boot I had to use DC- Phoenix to flash a factory firmware(Chinese) which I had to pay for. Then I flashed a stock vie-l09c432b181 ROM over the top.
To repair the IMEI I'll have to use HCU, which I'll have to pay for as well. But that's ok. If I can get my original IMEI back, I can use the original unlock code I got earlier this year, otherwise I'll have to get a new one based on a new IMEI.
I can repair the bootloader and region code using twrp etc. so that's not a problem.
I'm actually using the phone to write his reply, so I can at least use it.
Once I have it all 100% working I'll try to put together a full step by step.
Cheers.
Well, I have a working phone. But, it'snot stable. Having trouble with mobile connection, sms, mms, 4g etc not staying connected. So wont be doing any write-ups just yet.
Not until it's stable.
I'm wanting to return it to complete stock now. And that requires trying to find an oeminfo file for C706 (New Zealand).
Will add more as I get there. Sorry.
I had the same problems. All I did is updated the phone with the firmware you want via Twrp . Be warned that it will replace the recovery back to stock. Also clear the cache and etc.
I had a similar issue with SRK tool, bootlooping, won't flash new firmwares, lost all the stock apps and diagnostic tools.
I'm now stuck on a TEST-KEYS build with no NFC or Bluetooth.
My solution was to throw the piece of junk in a drawer, forget about it and I went and bought a Pixel XL instead - a phone that is properly supported and gets updates quickly.
After much messing and a headache I finally got to c432b370
And everything back to normal
tolerant said:
After much messing and a headache I finally got to c432b370
And everything back to normal
Click to expand...
Click to collapse
How did you succeed?
I am stuck on TEST-KEYS but I am not able to flash other roms on it. When I go to recovery, the update process stops after a while
Sent from my VIE-L09 using Tapatalk
I recently had to replace the motherboard on my Nexus 6. I could only find refurbished ones, and bought one on AliExpress, with item description clearly specifying as unlock. I installed it, and it appears it is actually locked status 2. Looks like demo version used in T-Mobile retail network. Some settings inaccessible u such as developer mode or Apps. Trying to get refund but both AliExpress and the vendor are in denial mode.
I have 7.0, NBD92G installed. Very hard to unlock as I cannot access developer mode to allow usb debug. Pressing build nr several times won't help. I get message "you're already a developer" but actually usb debug does not work.
Anybody can help?
Go download factory image from Google and flash it manually by using the command prompt.
@ShernDog: He can't as his bootloader is locked. He can however download an OTA and sideload it.
Strephon Alkhalikoi said:
@ShernDog: He can't as his bootloader is locked. He can however download an OTA and sideload it.
Click to expand...
Click to collapse
Thanks. You are right, bootloader is locked too. Would there be any instructions somewhere on your proposed solution (sorry I am rather inexperienced user).
FYBRU said:
Thanks. You are right, bootloader is locked too. Would there be any instructions somewhere on your proposed solution (sorry I am rather inexperienced user).
Click to expand...
Click to collapse
I think I figured out how to do this but the other question is whether I won't be stuck afterwards being requested to enter the only registered user's login which I do not have (I cannot register a second user, as this setting screen is locked too). Do I need to sideload the OTA corresponding to current version / build or can I sideload an older one?
Download the oldest OTA available, as long as it is a full system OTA (easily detectable by size). You're going to have to bypass Factory Reset Protection to be able to resolve this, and the older the OTA, the better.
If this doesn't work, you're going to have to fight with the place you got the motherboard from, and file a chargeback with your credit card company if need be.
Ultimately I can go for the refund, but there is no place where I can find 64 GB MBs outside China, which means I'll have to wait again for something like 3 weeks with poor backup device, and with no certainty I don't receive again a locked MB.
I tried with 6.0 OTAs (page with instructions I followed: https://developers.google.com/android/ota#shamu) and even with just older versions of 7.0, I got every time abortion after about 45% installation, with the msg that I cannot update with older versions.
I am a bit confused now, I just tried to install same build as what I had installed (https://dl.google.com/dl/android/aosp/shamu-ota-nbd92g-2b65257b.zip), it worked but it looks like absolutely nothing has changed on my phone. I thought it would have erased pretty much everything. Am I missing something?
OTA updates don't wipe system. That's why nothing changed.
Ultimately, I think you're going to have to go for the refund and take the risk that the next motherboard you get is going to be locked. Unless the version of Android you're on can have its FRP bypassed - and I don't think it can - you're stuck.
Thanks, bad news. Would it be worth trying wipe data / factory reset accessible from the recovery mode + power/volume up menu ?
You can try it, but it won't help. Doing a factory reset will cause Factory Reset Protection to kick in, meaning you'd need to know the original owner's account information.
Surprisingly it worked. I could log in with the google account I used before the reset. Everything works, but indeed I was expecting some more difficulties
@FYBRU: This is one of those times where I'm pleased to be wrong. LOL.
Glad you got it resolved.
Hi everybody, I don't know if this will help all you but this is what worked for me (Android 6.0.1):
1. On the setup wizard (after factory wipe), connect to internet (wifi/data)
2. Select "Emergency call"
3. Call to any valid number (112 for example)
4. When the calls start swipe to the left on the dialing screen and you will see message and browser displayed (in my case the message method doesn't works).
5. Select browser.
6. Go to google.
7. Search for Package Disabler Pro 9.8
8. Download it and install it.
9. Open it and search for "Samsung account".
10. Click on Clear Data and then Disable.
11. Go back to google and search for QuickShortMaker
12. Install it and open it.
13. Search for "Setup Wizard", it will expand.
14. Select the one with ".setupwizards.SetupExitActivity"
15. Done! You can now use the phone and restart.
Ok after this you can go and check that there is no Samsung account displayed (Settings>Accounts), buuuuut, you can't add it . What I did was:
1. Go back to Package Disabler Pro and enabled "Samsung Account".
2. Then go to Settings>Back up and reset
3. Factory data reset
4. Asked for Samsung account and I inserted my real account.
5. Done, now I can sync with my account.
The oooooooonly issue that I can't figure out it's the way to remove the "Reactivation lock" from Settings>Lock screen and security>Find my mobile.
Well that's all hope it works for you guys.
If this doesn't work for you, you can check out unlockjunky, they will definitely be able to do it.
Good luck!!
xxspokiixx said:
Hi everybody, I don't know if this will help all you but this is what worked for me (Android 6.0.1):
4. When the calls start swipe to the left on the dialing screen and you will see message and browser displayed (in my case the message method doesn't works).
Click to expand...
Click to collapse
when i'm calling i cannot swipe to the right. Is there anyother way to open the browser?
112
What ever you do, absolutely do not dial for example ( 112 )
Turns out 112 will connect you to your local emergency dispatch.....
Ask me how I know...
please change your number in the above post for newbies who may be trying to learn and have no clue what these phones are capable of...
Thanks
xxspokiixx said:
Hi everybody, I don't know if this will help all you but this is what worked for me (Android 6.0.1):
Click to expand...
Click to collapse
Mate, you are an absolute legend! I've been searching for 8hrs looking for a solution after hard resetting my phone and being unable to get past the Samsung Account lock afterwards (even though I had the right username & password!) About fifty useless/outdated YT videos & a few hundred websites/forums later - none of which were helpful, I finally stumbled across your post, despite it not showing up 8hrs ago when I came straight to XDA hoping to find a solution first.
I have an improved method for #2, 3 & 4 of your post and will add all relevant info soon (just need some kip now that the panic is over). I'll also expand a little on some details and include further options which worked in my particular case, but all n'all - you're an absolute legend mate and I'd be screwed & still panicking without your shared info. Huge thanks...
Nice meme dude ya got me
Nomak1835 said:
What ever you do, absolutely do not dial for example ( 112 )
Turns out 112 will connect you to your local emergency dispatch.....
Ask me how I know...
please change your number in the above post for newbies who may be trying to learn and have no clue what these phones are capable of...
Thanks
Click to expand...
Click to collapse
AGREED!!!!!!!!! DO NOT DIAL 112!!!!!! It switches to 911... not a funny joke
Nomak1835 said:
What ever you do, absolutely do not dial for example ( 112 )
Turns out 112 will connect you to your local emergency dispatch.....
Ask me how I know...
please change your number in the above post for newbies who may be trying to learn and have no clue what these phones are capable of...
Thanks
Click to expand...
Click to collapse
You have to dial an emergency number or this trick doesn't work. Its not practical for most folks but if you are worried about dialing an emergency number I'd recommend using a SIM out of a tablet that isn't phone number enabled.
its working for j7 prime bypass samsung account
Hi, First of all thanks for this thread. i made it to #8 but when i download the apk and i cant figure out how to install it to complete steps 9 and 10. Maybe i'm over looking something im not sure but i need help.
TIA
Beasy936 said:
Hi, First of all thanks for this thread. i made it to #8 but when i download the apk and i cant figure out how to install it to complete steps 9 and 10. Maybe i'm over looking something im not sure but i need help.
TIA
Click to expand...
Click to collapse
Look for Aptoide apk download it to sd card and search for package disabler in this app and install it or download and copy Pachkage disabler you your sd card and run via file explorer or download and run ES File manager as I did.
when i make the call my wifi gets turned off and wont come back on till i restart the phone. i managed to open the browser but the wifi is off so i cant do anything after that except cry.
stock 5.0
Did you get it figured out I got the edge 6 plus to work fine now it was one of the tougher ones and I've done a few on some newer models what are you stuck on?
I thought the Combination Firmware would reset the FRP lock by default after being installed.
first thank you for sharing ur experience and i want to add
that i done it step by step and it works nicely but still cant remove the reactivation
and here is how iv done it after i bypassed it using ur method
i flashed a lower modem file from stock rom N910VVRU2BOG5 which is 5.0.1
at this point my imei went off
so i went for full flash by N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME. which is 5.1.1 and did full hard reset
then i just signed in with the last Samsung account i used with ur method earlier and it passed so now i can easly remove reactivation mark , unlock and root then make it Arabic .
thx again
Did you ever post up the suggested steps to replace #'s 2-4 in the original post above? I'm not seeing them anyplace. This would be a big help. Thanks.
When I call I can't swipe to the right is there another way to open browers
I successfully used this to gain access to my phone but I believe that if I power cycle it I will be locked out again. Is there any way to remove or change the samsung account now that I am in? The options are greyed out in settings.
ADB and Root.
Hey, I have been working on these for a while keep finding new things each time I try to remove Reactivation Lock. However I was wondering if I show you guys how to enable ADB with RSA Key, and Root the device. Could someone show me how to remove the Reactivation Lock using root. I used other methods on older and newer models, but these S5's are the only ones giving me issues.
After weeks of going mad trying different solutions I've found online, here's what worked 100% for me just last night:
Login to Samsung Account on other device, select Password & Security, enter password then choose Devices. LOG-OUT of your S6 Edge if listed, confirm. Next change password - doesn't matter what, can even change it back afterwards.
Flash Lollipop (I used G925VVRU4BOK7)
Wipe Data/Cache
Boot fresh Stock firmware, enter/confirm network details, at Reactivation Lock prompt, enter user & updated password. Sign-in....
Settings -> Lock Screen & Security -> Find My Mobile. Unselect Reactivation Lock and enter password... voila!
Works for anybody else??
when i made the call the wifi turn of
Hello XDA, I hope that you could help me troubleshoot my Note 8 (N950F).
So it's been 7 days and oem unlock toggle has finally appeared.. The only issue is it is greyed out and unselectable.
When I got this device I wasn't able to see developer options by pressing build number (though I got the notification that it was enabled), I was only able to access the setting by downloading an app short cut for it via the play store and on initial launch it said developer options are disabled. But then second launch it worked. Idk if this is significant but maybe the country this is meant for disabled it? Regardless of the sim card being in/out the phone, it is still greyed out. Also, I was able to factory reset the phone through the settings after downloading an OTA (I did this in hopes of developer options being enabled about a week ago.)
I tried to boot into download mode but it seems I can't boot into it (following the steps only lead to a normal reboot, and when I select that option from the stock recovery or through adb, it only boots the phone up normally. I purchased the phone off of swappa, in brand new/like new condition. Any ideas? Thank you for your help.
Edit: added screenshots.
SM-N950F / DS here running Taiwan software BRI and I have the option maybe if you flash this firmware you'll get it.
Eddygraphic said:
SM-N950F / DS here running Taiwan software BRI and I have the option maybe if you flash this firmware you'll get it.
Click to expand...
Click to collapse
Thanks for the answer! However, I don't think I can flash firmware because I can not go into download mode, which is needed for odin to flash firmware
Negroid said:
Thanks for the answer! However, I don't think I can flash firmware because I can not go into download mode, which is needed for odin to flash firmware
Click to expand...
Click to collapse
That's weird I've never seen a Galaxy that can't enter download mode.
Eddygraphic said:
That's weird I've never seen a Galaxy that can't enter download mode.
Click to expand...
Click to collapse
Exactly. That's why I'm so concerned.
Have you logout your Samsung Account and Google account？sorry for my poor English.:crying:
Do you use any of the KNOX stuff? Did you do any factory reset?
Can you "clear data" on "settings" app? this would make the "developer option" menu hidden again. Then re-show it by tapping build number numerous time again. Hoping that OEM is now editable.
Hi, could you solve this problem? My Note 8 has the same problem and I have not found any solution :llorando:.
I would appreciate it if you can help me.
I was happily use my Note 9 N960N(Korean set) after I rooted it about a year ago. Few days ago I saw a new ver of Magisk(old ver 17.2 flashed w/TWRP) at Magisk manager and wanted to update but hesitate. I backup a few important file like whatsapp, SMS & contact list before I carry on further. Today I decided to update the Magisk and my fear was right, after it reboot my Note 9 stuck at "Samsung" logo. I let it there initially and after a while it remains at same place. I tried to switch it off by press the power button but no response. It won't switch off after I tried, 10, 20 and 30 seconds. I found out there is a way to reboot it by holding "power + volume down". I successfully got it boot to recovery to TWRP.
I thought it maybe the Magisk was corruptted during update so I download the Magisk zip v19.3. Then I booted to TWRP and installed the Magisk zip. I reboot the Note 9 after Magisk installed. Again I was stuck at Samsung logo. I thought maybe the sequence was not correct; beside the Magisk there maybe need few more so I followed the root sequence(skip root); 1. Magisk 2. no-verity-opt-encrypt-6.0 3. RMM-State_Bypass_Mesa_v2
Same problem, I stuck at Samsung logo. As early problem, I couldn't switch it off by pressed the power switch. I have to reboot to TWRP and use its interface to power off the phone. I have new problem this time; once I pressed the power button to power on the phone, it will goes to TWRP straight away. Tried few times and it remain the same problem. The last action what i did is flashed a new TWRP v3.3.1-0-crownlte and it didn't help either.
My Note 9 has 2 problems;
1. go to TWRP recovery straight after press power button to power up the phone.
2. stuck at samsung logo after user TWRP to reboot.
There is one more thing I didn't pay attention previously, the "mount" in the TWRP what is supposed to mount? It "mount" the SD card when it last to flash zip files.
Appreciated anyone can helps, thanks.
Try to flash different kernel. Then flash magisk again. Although I doubt it could help, but your phone has bricked already, so worth to try.
If it's really brick, I'll consider to flash it "pie" since my one still "oreo". Any chance just reflash it with oreo again with odin but retain data?
user109 said:
If it's really brick, I'll consider to flash it "pie" since my one still "oreo". Any chance just reflash it with oreo again with odin but retain data?
Click to expand...
Click to collapse
Phone will factory reset after flash stock regardless odin or smartswitch. Of course you can still flash oreo. But flashing stock should be the last resort.
Rosli59564 said:
Try to flash different kernel. Then flash magisk again. Although I doubt it could help, but your phone has bricked already, so worth to try.
Click to expand...
Click to collapse
You did mention to flash a different kernel, what will it be the most suitable?
I found a suggested solution to try; flash(with oreo, same ver) with odin and check files except at CSC section choose "home_csc" instead normal "csc". Reflash was succeeded, in a way.. It did break something though.. My note 9 is able to boot normal but was stopped at lock screen(pattern lock) which I was set to lock my phone. Now it's lock screen loop even though I draw the pattern correctly. It just refuses to unlock. I use Samsung "findmymobile" try to unlock it and unsuccessful; the app cannot find the phone. It prompted "offline"! It's strange, I can see my carrier and wifi are working. I can call the preset emergency numbers to call. I used another phone to call and it can receive the call. It can receive whatsapp message. I tried google and it works. The google app is able to find my phone. I have no idea why my samsung account won't work. Now I'm clueless.. :crying:
user109 said:
I found a suggested solution to try; flash(with oreo, same ver) with odin and check files except at CSC section choose "home_csc" instead normal "csc". Reflash was succeeded, in a way.. It did break something though.. My note 9 is able to boot normal but was stopped at lock screen(pattern lock) which I was set to lock my phone. Now it's lock screen loop even though I draw the pattern correctly. It just refuses to unlock. I use Samsung "findmymobile" try to unlock it and unsuccessful; the app cannot find the phone. It prompted "offline"! It's strange, I can see my carrier and wifi are working. I can call the preset emergency numbers to call. I used another phone to call and it can receive the call. It can receive whatsapp message. I tried google and it works. The google app is able to find my phone. I have no idea why my samsung account won't work. Now I'm clueless.. :crying:
Click to expand...
Click to collapse
it's a Samsung stupid lock as your Note 9 has not fully booted you will not be able to find it via my Samsung.. There is a bug even if you draw the correct pattern the phone will not unlock it's a bug this has been covered when the Note first came out as the first or second update caused this issue! i did read somewhere there is a way around it, but this was a year or so ago you need to check Samsung official forums for the pattern bug fix check Samsung forums USA it has been covered in-depth over there!
N1NJATH3ORY said:
it's a Samsung stupid lock as your Note 9 has not fully booted you will not be able to find it via my Samsung.. There is a bug even if you draw the correct pattern the phone will not unlock it's a bug this has been covered when the Note first came out as the first or second update caused this issue! i did read somewhere there is a way around it, but this was a year or so ago you need to check Samsung official forums for the pattern bug fix check Samsung forums USA it has been covered in-depth over there!
Click to expand...
Click to collapse
Hi N1NJATH3ORY, I did google around the screenlock loop problems and most of them done with 1) simple reboot 2) boot to safe mode 3) use "samsung "findmymobile". A most common solution; "wipe". A few issues raised at Samsung forum but not helpful; "call Samsung support".. There was an interesting article which suggested the problem is from google itself. Here is the link; https://www.androidpolice.com/2019/12/12/google-pixel-pin-lock-screen-loop-help/
"If the encryption of the "Synthetic Password Key blob", which needs to be decrypted in order for the unlock process to be resolved, is not able to retrieve a stored decryption key if it was corrupted." from the article. I'm not sure if this is the cause but from logic point of view it's possible. I believe the bloody Samsung knew this problem since day one but because it's not a"common" issue Samsung just swipe under the carpet.
What I did on my note 9 last action was reflash the oreo, if in the process of flashing the "Synthetic Password Key blob" has been wiped out then it may explain this screenlock loop problem, which I hope not to happen. I'll be screwed if it did. :crying:
I'll wait its battery to drain out to see what happen even though I doubt if any change..
As expected, the drained out of battery did not help, my note 9 remains locked. The only way is to try out new method and with high risk which will wipe out my data. Fortunately the new method work! Not only it overwrite the lock screen loop and also disable the google device lock.(One of the method I tried during my lockscreen loop which is useless. It creates an extra problem on top of the problem) I got all my data intact and allow me to do all backup. :highfive:
summary: update Magisk is not a full proof. The risk is 50% it will brick the phone. My advise is to backup every dan internal data before finger press the Magisk "update" especially it remaps the image! Manager APK is okay to update. I learned from the hard way and almost lost the whole dan data in my Note. You have been warned!
Gdhhs