Database Develop

OEM Unlock in CRGA / CRG8 Without Wait 7 Days

Friends,
How fix OEM Unlock without wait the seven days after security patch 01/08?
I tested various trips and in rare case, the OEM Unlock appear for me, but, in reboot, fastboot and flash the TWRP, the task fail and when returned in Developer Settings the OEM unlock disapear and dont show anymore.
Someone can help me, please?

Normally it should be enough to flash a patched kernel directly after you flashed TWRP.
Don't be afraid to hit the "Thanks" button if someone helped you. It don't hurts

The 7 days bypass still works with the August patch but require multiple tries. https://forum.xda-developers.com/galaxy-note-8/how-to/oem-unlock-quick-fix-highly-recommend-t3791984
Last time I got it to work was by -
1. Factory reset the system
2. Setup fresh device - only wifi and Samsung account (date doesn't matter once connected to internet date will reset
3. Change date to at least 7 days earlier (it doesn't work after all the steps try 7 days later)
4. Disable auto update then manual update (usual steps)
5. Airplane mode before the reboot (keeps the date after reboot)
6. Reset date to default, and manual update + reboot
7. If oem unlock doesn't show, go to recovery and clear cache (this worked for me, it popped up after reboot~)
Well, I got it to work sometimes without clear cache. This might not work for you, it might be more promising to wait for another 7 days.
I found RMM-State_Bypass_Mesa.zip fix to not work anymore. There is a later version v2 on the web.
Note: I was on CRG1

bluecub1st said:
The 7 days bypass still works with the August patch but require multiple tries. https://forum.xda-developers.com/galaxy-note-8/how-to/oem-unlock-quick-fix-highly-recommend-t3791984
Last time I got it to work was by -
1. Factory reset the system
2. Setup fresh device - only wifi and Samsung account (date doesn't matter once connected to internet date will reset
3. Change date to at least 7 days earlier (it doesn't work after all the steps try 7 days later)
4. Disable auto update then manual update (usual steps)
5. Airplane mode before the reboot (keeps the date after reboot)
6. Reset date to default, and manual update + reboot
7. If oem unlock doesn't show, go to recovery and clear cache (this worked for me, it popped up after reboot~)
Well, I got it to work sometimes without clear cache. This might not work for you, it might be more promising to wait for another 7 days.
I found RMM-State_Bypass_Mesa.zip fix to not work anymore. There is a later version v2 on the web.
Note: I was on CRG1
Click to expand...
Click to collapse
Dont work for me. SAD!

Diexmax said:
Dont work for me. SAD!
Click to expand...
Click to collapse
Try a factory reset, first remove the sim card.
Skip wifi and logging into accounts, when the time and date option pops up set it back 14 days (usually what I do) Hopefully then OEM will appear. :fingers-crossed:

stonedpsycho said:
Try a factory reset, first remove the sim card.
Skip wifi and logging into accounts, when the time and date option pops up set it back 14 days (usually what I do) Hopefully then OEM will appear. :fingers-crossed:
Click to expand...
Click to collapse
Friend, i tested with various methods and dont work. 7 Days back, 14, 20, 60 days back and nothing.
Wait seven pain days

stonedpsycho said:
Try a factory reset, first remove the sim card.
Skip wifi and logging into accounts, when the time and date option pops up set it back 14 days (usually what I do) Hopefully then OEM will appear. :fingers-crossed:
Click to expand...
Click to collapse
Need internet for try update, no?

Diexmax said:
Need internet for try update, no?
Click to expand...
Click to collapse
Not sure, but i think without internet Connection we can dupe the Sammy system to activate more quickly the Oem option. Maybe im right maybe i m wrong

Diexmax said:
Need internet for try update, no?
Click to expand...
Click to collapse
It's worked that way for me the last 3 times. It definitely works sometimes when logging into accounts and checking the update, thats what I used to do, this just skips all of that. Just another method you can try, some work for some, other's do not.

thanks, going to try this after work today.

Google Pay not working - Phone not rooted

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.

Galaxy Note 9 stuck at bootloop after update Magisk

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

Flicking Lock Screen after update to latest Android 11 OTA update

I just saw an update notification that Android 11 had been released. Since my phone was running Android 10, I proceeded the update without hesitation (and without backup). The phone is running stock rom without root (I guess I did unlock the bootloader but couldn't confirm since this new rom version cannot boot into fastboot mode). After update, the lock screen keeps flicking and I cannot unlock the phone. I tried booting into safe mode but got the same flicking lock screen.
The rollback pack has flagged 'ota-downgrade=yes' so data will always be wiped.
Code:
... "ota-downgrade=yes" will be set in the package metadata file. A data wipe will always be enforced when using this flag...
I guess my last hope is that
Option 1) Wish I really did unlock the boot loader and some gurus found a way to boot into fastboot mode and flash the customer recovery/android 10 so I can pull my photos/videos by adb.
Option 2) Tried booting into recovery but no new OTA update available. Wait for new OTA update
Option 3) Some found a way to
a) boot into EDL/Download mode and
b) flash TWRP/Android 10 using QPST/QFIL (Not possible currently since Qualcomm QPST/QFIL tools did not work and official realme flash (MSMDownloadTool) ALWAYS wipe your data!)
Option 4) Someone got the private key so we can sign our customized-made update_pack and copy photos/videos to OTG USB Drive under Recovery.
Option 5) Someone share a rollback pack with 'override_timestamp=yes' instead of "ota-downgrade=yes" so data will NOT be wiped
Any comments are welcome
Spoiler: Button Combos for Booting into Other Mode
Vol Up + Power (hold for 10s)= Force Shut Down
Vol Down + USB Charging = Recovery
Vol Down when booting = Safe mode
depth testing.apk = Fast Boot (https://c.realme.com/in/post-details/1244859266402091008)
? = EDL/Download Mode
Latest Official Roms
软件升级
软件升级
www.realme.com
https://download.c.realme.com/osupdate/RMX1931_11_OTA_1340_all_2QCxQYdkxpql.ozip
Bootloader Unlock Guide
realme Community
Welcome to realme Community, your virtual playground to learn the latest tech news, win exclusive prizes, or simply chat about realme!
c.realme.com
Spoiler: OTA Update Pack
https://download.c.realme.com/osupdate/RMX1931_11_OTA_0150_all_oDfL8HoMZ5HW.ozip
https://download.c.realme.com/osupdate/RMX1931_11_OTA_1220_all_Dx2plLOdGTD4.ozip
https://download.c.realme.com/osupdate/RMX1931_11_OTA_1280_all_4zs7Gcdyxm3V.ozip
https://download.c.realme.com/osupdate/RMX1931_11_OTA_1250_all_H8peW44p7GS0.ozip
https://download.c.realme.com/osupdate/RMX1931_11_OTA_1300_all_QzFVhQQieINQ.ozip
https://download.c.realme.com/osupdate/RMX1931_11_OTA_1330_all_sgVacScUYMkf.ozip
https://download.c.realme.com/osupdate/RMX1931_11_OTA_1340_all_2QCxQYdkxpql.ozip
Spoiler: OTA Rollback Pack
RMX1931_11_OTA_0170_all_VEio9eM857gn.ozip
RMX1931_11_OTA_1330_all_19781_downgrade.ozip

Did you have any luck getting your phone back to normal?

aiben16 said:
Did you have any luck getting your phone back to normal?
Click to expand...
Click to collapse
No.
I want my data back and waiting for next update seems to be the only hope. Reported to realme but get no response.
If you have similar issue and don't care your data, you can do factory reset.

Am on the same boat here, Bluetooth devices still get automatically connected, USB works (mouse and keyboard) but still haven't found a way past the flicking login screen.
Happened overnight and last backup was quite a few months ago, definitively need to get the data back.
- Edit: Booting to safe-mode doesn't help either.
- Edit2: Can't attempt any update because the device is not accepting my lockscreen password either.

Mywk said:
Am on the same boat here, Bluetooth devices still get automatically connected, USB works (mouse and keyboard) but still haven't found a way past the flicking login screen.
Happened overnight and last backup was quite a few months ago, definitively need to get the data back.
- Edit: Booting to safe-mode doesn't help either.
- Edit2: Can't attempt any update because the device is not accepting my lockscreen password either.
Click to expand...
Click to collapse
If you disabled or uninstalled the coloros calendar package via ADB, enable or reinstall it again via ADB, the new System UI in the Android 11 update relies on it

This really sucks.
Any solution yet? Would be happy if I could just get access to my photos...
BTW for future reference, I'm on a Realme X Lite. I actually was positively surprised with this phone (up and running perfectly for over 2 years), but this policy is quite shocking...

Phil_123 said:
If you disabled or uninstalled the coloros calendar package via ADB, enable or reinstall it again via ADB, the new System UI in the Android 11 update relies on it
Click to expand...
Click to collapse
Just wonder if there is any way to sideload apk via adb since I can't even go to the home screen and accept adb connection.

Almost one year passed but no progress. No firmware update either.

damonxd said:
Just wonder if there is any way to sideload apk via adb since I can't even go to the home screen and accept adb connection.
Click to expand...
Click to collapse
I forgot what I exactly did to get out of the situation. From what I very vaguely remember, it might have involved tapping where the Allow button would be very quickly before the whole UI crashes. Then, depending on whether you disabled or uninstalled the weather package, you either enable or "install-existing" the package name.
How to install / get back uninstalled Apps (APKs) with ADB.
A lot of people searched for a way to uninstall bloat or APKs using ADB because a lot of OEMs don't allow uninstalling many of preinstalled apps. Tested on Pie and Oreo. BUT most of the articles if not all of them ( couldn't find any article...
forum.xda-developers.com

Phil_123 said:
I forgot what I exactly did to get out of the situation. From what I very vaguely remember, it might have involved tapping where the Allow button would be very quickly before the whole UI crashes. Then, depending on whether you disabled or uninstalled the weather package, you either enable or "install-existing" the package name.
How to install / get back uninstalled Apps (APKs) with ADB.
A lot of people searched for a way to uninstall bloat or APKs using ADB because a lot of OEMs don't allow uninstalling many of preinstalled apps. Tested on Pie and Oreo. BUT most of the articles if not all of them ( couldn't find any article...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the tips. It seems my situation is a bit difference. I can't even see the unlock pattern screen to let me unlock the phone before I can tap "allow" for USB connection and entering ADB commands. Maybe yours have the screen lock disabled before updating.

Phone locked (6084) - please help me

Hello, I rooted my s20 FE 4g and uninstalled bloatware with Lucky Patcher. I always freeze the apps first to check if it works. Then I froze the "Device Services" app and my smartphone is now locked. Unfortunately, I also disabled USB debugging. Luckily I was able to connect the smartphone to the PC because I was fast enough to set up the data transfer. The smartphone still starts normally, but after about 5 seconds the message "Phone blocked (6084)" appears. "Your phone is blocked because Device Services was uninstalled without authorization." As I said, I just froze the app. Fortunately, in the 5 seconds before the message came, I was able to connect my smartphone to the PC to save data. How can I unlock my smartphone now? Please help me I'm desperate! Thanks!
Is there a way, a tool or something similar to unfreeze the app? It would probably be possible with ADB, but unfortunately, as I said, I disabled USB debugging.

a factory reset will bring device services back. or a less extreme method would be doing an install command for the correct package name for device services from ADB.

Factory reset check on this video if you can't boot into recovery.