yashsingh1/xdaforums huggingface dataset:
[ASUS ZenFone 6 (2019) Questions & Answers] Monerchi:
Hi,Guys~

I can't get the bootloader unlock, Cause it keep saying like the picture shows.. Whatever fimware I use or official Unlock Device Tool(9.1.0.8-9.1.0.11) app. It can't be done. Including android P(16.1220.1909.194 &a lot of P version) to Q(17.1810.2005.153).

"An unkonw error occurs, which may be a network connection issue.please wait and try again later"

Actually network can surf totally no problem, but just can't unlock.I had try both of cyanogenmods unlock method can't work.

[IMG="As the screenshots"]https://drive.google.com/open?id=1ahIiLn6RObPPPrtEJoxNgMW9jRtZyU3u[/IMG]

There is any way back to the older(older than 16.1220.1909.194) or the first fimware? I think maybe it's the fimware 16.1220.1909.194 newer than the unlock apps...I tried the ADB but cant wrrote the older fimware...

Sry for the image...looks like it can't show out by google cloud drive.

Plz help me guys.

Thx a lot.
[ASUS ZenFone 6 (2019) Questions & Answers] shekarbasha@gmail.com:
same problem here. i tried the 1st firmware that came with it 2019 april .still same problem. this happened after i gave it service regarding a problem which is taking too much time to open gallery. they have reflashe the phone and gave to me with AndroidQ. i tried to unlock with the asus tool. it says network issue. then i downgraded to 16.1210.1904.75

and tried with no success. any help
[ASUS ZenFone 6 (2019) Questions & Answers] YandexStudio:
Did you finally solved this problem?
[ASUS ZenFone 6 (2019) Questions & Answers] HTC_FUZE:
I saw somewhere people saying to remove device pin before you try unlocking bootloader. I guess you can try that.
[ASUS ZenFone 6 (2019) Questions & Answers] silver2004:
Anyone found a solution for the bootloader unlock?
[ASUS ZenFone 6 (2019) Questions & Answers] pavelbures2:
It is not possible to unlock the bootloader, Asus disabled this function. I got confirmation from Asus Czech Republic.
[Xiaomi Mi 9 Questions & Answers] maiconjs:
I have the device that I recognized on my Windows computer at first. There was no drop of the device or drop of liquid, simply in an ordinary day the device only presents as "Device Descriptor Request Failed". I have 5 cables here, I have tested them all on several devices and it works normally but it doesn't work in Mi 9. I also connected the device in fastboot mode and I get the same message. What could have happened to cause this problem? Could the charger have damaged the input connector or could this be a problem on the board?
[Xiaomi Mi 9 Questions & Answers] Devkkaos:
I have the same problem. Stuck in boot loop. TWRP still working though but cca't get the ROM on the device.

What to do...please help !
[Huawei P20 Lite Questions & Answers] The_Kian:
The phone is just stuck on the Huawei logo, i have tried holding volume up + power and volume down + power. Nothing happens.

I managed to get into fastboot once but couldn't do anything with it
[General Questions and Answers] Light_Wing:
Does anyone know if it's possible to change the ok Google or hey Google keyword (hotword) using root (magisk) or (Ed)xposed ?
[General Questions and Answers] Droidriven:
Maybe this?

https://www.techjunkie.com/change-ok-google/
[General Questions and Answers] Light_Wing:
I already googled before asking (and found that article, I even bought the tasker app for it, and even so, I think that method isn't the best, until now I found reasons to avoid buying tasker, now I need to find the best uses for me to use it LOL), but I want a root way or even an xposed way of doing this by hooking into the source, not by getting a different app to always listen to me (and probably take more power then needed, as I think google did the work needed to make it take as little power as possible)

and I already have a rooted and exposed phone, so I thought may as well hook into whatever controls the hotword (I know it works on the phone offline, it does not need to connect to the internet to verify the hotword...) and change the local hotword...
[General Questions and Answers] Droidriven:
You could try modding the Google/Google Assistant apk. I wouldn't know where to modify it or if it can even be done.
[General Questions and Answers] Ontropy:
found any solution?
[General Questions and Answers] Mersine:
bump!
[Touch Diamond, MDA Compact IV General] LamPET:
Hi,

I'm want to hide the name of the provider on my TF3D Home screen.

Can anybody help me or show me the tread.

Thanks

Lambert
[Touch Diamond, MDA Compact IV General] akito:
And actually I want to have it visible better in bold or bigger sized letters lol.

I can't find where, it doesn't work editing the xml files or registry or whatever... or I missed the right part of them :D
[Huawei MediaPad M5  Guides, News, & Discussion] goattee:
I'm sure some of you are LastPass Premium users. Am I the only one who regularly has to reauthorize LastPass to autofill? Have any of you found a fix?

EMUI 8.0.0.200(C567)

US version
[Huawei MediaPad M5  Guides, News, & Discussion] Zel_M:
Same issue even in the 9.1, no fix at all.

Some months ago, I've switched to Bitwarden after a whole life with last.pass...
[Huawei MediaPad M5  Guides, News, & Discussion] ras1md:
Everytime i get this error lastpass hasn't even logged me in yet or the autofill switch is already on. Ditto for the allow on top switch also.
[Android Studio] yabi54:
Sorry made a mistake
[G4 Q&A, Help & Troubleshooting] benni_g4:
Hi,

since i wanted to install a custom Lineage OS ROM for my LG G4, i wanted to make a clean install of the OS according to https://xdaforums.com/showpost.php?p=79502871&postcount=2 .

I used

fastboot boot ~/Downloads/twrp.img

to boot into TWRP from my phone. I didn't install TWRP.

I chose WIPE->Advanced and selected "System" and "Cache". After that, I also used the "Format Data" function.

I rebooted the phone, but since then, only the LG logo is shown with the message "Bootloader Mode: Bootloader unlocked!"

I tried to enter fastboot mode by following these instructions from https://xdaforums.com/g4/general/unlock-unlock-lg-g4-device-usu-t3760451:

However, it doesn't work. Right now, It looks I can't use the phone for anything anymore. Can anyone help me with this?

Edit: I found out that my phone manages to enter download mode.
[G4 Q&A, Help & Troubleshooting] steadfasterX:
UsU'd or not? Sounds like an official unlocked so an advice for UsU devices will not help.

Which TWRP version do you had used?

And most importsnt what model (h815, h812..)?
[G4 Q&A, Help & Troubleshooting] benni_g4:
The model is is H815. You are right, I unlocked it the offical way. The TWRP version is 3.3.1-2.
[G4 Q&A, Help & Troubleshooting] benni_g4:
Any chance to solve this? It would be sad to throw it away because of this reason...
[G4 Q&A, Help & Troubleshooting] dat_benjie:
I think, I had the same problem a couple of years back, but I don't remember the solution. Might have been the USB cable that I used. You could try changing up the cable.

Are you able to detect the device with "adb devices"?
[G4 Q&A, Help & Troubleshooting] benni_g4:
I changed the cable, but the problem remains. As I said, the phone is also able to enter download mode when I press volume up and plug in the cable.

There is neither any output from

adb devices

nor from

fastboot devices

.

But I checked the output of

lsusb

. There is no usb entry for my phone after trying to enter fastboot mode.

BUT an entry appears after entering download mode:

Bus 002 Device 026: ID 1004:633a LG Electronics, Inc.

(but still no output from adb devices or fastboot devices)
[G4 Q&A, Help & Troubleshooting] steadfasterX:
The official TWRP is for oreo ROMs not pie. I don't believe that was the reason though , more likely because you didn't flashed TWRP and just fastboot boot'ed it.

You need to find the right combo for the h815. Just use the xda search to find it and also youtube could show good results.

The cable can be an issue as well and also the usb port ( try on usb 2 and usb 3 port).

Other then that it can differ between the bootloader stack version.

If you haven't flashed any bootloader TWRP zip then this is the last stock firmware version (the last one you had installed on your device).

Last but not least (depends on your bootloader stack version) you might be able to flash with SALT TWRP and boot it afterwards. Btw what was your reason not flashing TWRP ?
[G4 Q&A, Help & Troubleshooting] benni_g4:
To answer your question first: I didn't have a specific reason not to flash TWRP, I just read it somewhere that it was possible just to boot into TWRP. So I thought it wouldn't make a difference.

I didn't find any other key combination to enter fastboot mode.

I actually don't know what a bootloader stack is, my knowledge about android phones is limited :(.

Maybe the following information might be useful: before my attempts to install your custom ROM, I had a completely outdated ROM of the Official Lineage OS running on my LG G4. I once installed it also using TWRP. I think, back then I actually flashed TWRP, because I followed these instructions: https://wiki.lineageos.org/devices/h815/install .

I installed SALT and was able to connect with my phone. SALT seems to retrieve the correct device information. However, I don't understand how I can flash TWRP using SALT.
[G4 Q&A, Help & Troubleshooting] steadfasterX:
Share the debug log of SALT, latest version (advanced menu -> debug log -> upload button -> copy & share the link)
[G4 Q&A, Help & Troubleshooting] benni_g4:
Here you go: https://hastebin.com/yafukeyisu
[G4 Q&A, Help & Troubleshooting] benni_g4:
Hi,

sorry if I ask again. Is the debug information i posted above helpful in this case?

Thanks for your help btw!
[G4 Q&A, Help & Troubleshooting] steadfasterX:
Yes because you can use the flashing part of SALT which makes things easier.

Just start a terminal in mAid and type:

sudo ~/programs/SALT/salt --experimental

This will allow flashing.

Download latest TWRP preview(!) for P.

Choose flash folder and browse to TWRP and choose BOOT as your target partition. Let it flash . Then either choose reboot in SALT or reboot manually .

If all went fine TWRP will boot without any interaction. While in TWRP push the TWRP image to the device and then flash TWRP to the RECOVERY partition (you must use the button to show IMG files). Then choose reboot and there recovery. TWRP will show up again this time from the recovery partition. Now flash the ROM of your choice and you should be back in business.
[G4 Q&A, Help & Troubleshooting] steadfasterX:
sorry the BOOT was just in uppercase to highlight it (because it is unusual to flash a recover to the boot partition).

so simply type "boot" there (lower case) and it should work.

.-
[G4 Q&A, Help & Troubleshooting] benni_g4:
I tried it again with lower case, but the error message remains the same. Also the log output didn't really change, except that "boot" is now lower case, of course.

2020-06-11 13:44:41: F_FLASHPART: started
2020-06-11 13:44:54: F_FLASHPART: IMGDIR=/home/benjamin/Downloads/twrp_flash
2020-06-11 13:44:54: F_CHKDEVCON: started
LGLAF.py: DEBUG: product id in CR list: >LG_new<
LGLAF.py: DEBUG: Device is: 633a, LG_new. Enabling Challenge/Response!
LGLAF.py: DEBUG: Final CR detection: None / 1
LGLAF.py: DEBUG: Using endpoints 83 (IN), 02 (OUT)
LGLAF.py: DEBUG: Using Protocol version: 0x1000001
LGLAF.py: DEBUG: CR detection: 1
LGLAF.py: DEBUG: Hello done, proceeding with commands
LGLAF.py: DEBUG: Challenge: b'6ac5a97c'
LGLAF.py: DEBUG: Response: b'5cc04d128e07296b63574a3034bc7435'
LGLAF.py: DEBUG: KILO METR Response -> Header: b'4b494c4f4d455452000000000200000000000000000000002f5d0000b4b6b3b0', Body: b''
LGLAF.py: DEBUG: Header: b'EXEC' b'\0\0\0\0' b'\0\0\0\0' b'\0\0\0\0' b'\0\0\0\0' b'\0\0\0\0' b'\x1fW\0\0' b'\xba\xa7\xba\xbc'
2020-06-11 13:44:54: F_CHKDEVCON: Device seems to be connected!
2020-06-11 13:44:54: RET: 0
2020-06-11 13:44:54: F_USUVARVALID: started
2020-06-11 13:44:54: F_FLASHPART: will display all files (USUOVERRIDE=FALSE)
2020-06-11 13:44:54: F_FLASHPART: image files: twrp-3.3.1-PREVIEW-213_g4_P.img
2020-06-11 13:44:54: F_FLASHPART: created yad list: true
twrp-3.3.1-PREVIEW-213_g4_P.img
twrp-3.3.1-PREVIEW-213_g4_P
unknown-type
2
2020-06-11 13:45:12: F_FLASHPART BTNRET: 0
2020-06-11 13:45:12: choosen partitions: twrp-3.3.1-PREVIEW-213_g4_P.img:boot:unknown-type:2 -> 1
2020-06-11 13:45:12: sorted partitions: twrp-3.3.1-PREVIEW-213_g4_P.img:boot -> 1
2020-06-11 13:45:12: F_VERIFYDARB: started with /home/benjamin/Downloads/twrp_flash
2020-06-11 13:45:12: F_CDARB: started
2020-06-11 13:45:12: F_CDARB: ARB partition seems to be: sbl1
2020-06-11 13:45:13: F_CDARB: DEVARB=0, DEVARBEMPTY=0
2020-06-11 13:45:13: F_CDARB: ended
2020-06-11 13:45:13: F_VERIFYDARB: KARB: , DARB: 0:0,
CHKMRES: unknown VS. unknown
2020-06-11 13:45:13: F_ERR: started
2020-06-11 13:45:13: ERROR: 3 occurred in F_VERIFYDARB (expected 0, got 3)
2020-06-11 13:45:13: F_MSGE: started
2020-06-11 13:45:20: ERROR:
ERROR!

Device ARB or file-based ARB cannot be checked! ABORTED!!
2020-06-11 13:45:20: 0
2020-06-11 13:45:20: F_EXIT: started
2020-06-11 13:45:20: EXIT: F_VERIFYDARB->F_ERR with code 4
2020-06-11 13:45:20: F_ERR: started
2020-06-11 13:45:20: ERROR: 3 occurred in F_FLASHPART (expected 0, got 3)
2020-06-11 13:45:20: F_MSGE: started
2020-06-11 13:45:28: ERROR: Aborted on user check verification (2020-06-11 13:45:13: ERROR: 3 occurred in F_VERIFYDARB (expected 0, got 3)
0
2020-06-11 13:45:20: EXIT: F_VERIFYDARB->F_ERR with code 4)
2020-06-11 13:45:28: 0
2020-06-11 13:45:28: F_EXIT: started
2020-06-11 13:45:28: EXIT: F_FLASHPART->F_ERR with code 4
2020-06-11 13:47:05: F_ADVMENU: started with LG-H815
2020-06-11 13:47:05: F_ADVMENU: main YAD_PID is 5304
2020-06-11 13:47:07: CR setting: Auto =
2020-06-11 13:47:07: getlog script started
[G4 Q&A, Help & Troubleshooting] steadfasterX:
ah ok. just do a backup in SALT and choose custom. There select aboot and sbl1 and after the backup copy them in the same dir as the twrp image and try again.

.-
[G4 Q&A, Help & Troubleshooting] benni_g4:
Awesome!

Just installed your newest LineageOS build and everything is working again. Thanks for your help, I would never have succeeded without you!

I donated to your Account to support your work.
[Google Pixel 4 XL Questions & Answers] Purav786:
I have recently purchased a Pixel 4 XL, in order to root it I have enabled USB debugging however the option of OEM unlock is greyed out, that means I won't be able to unlock the bootloader.

I want to root my phone in order to install Substratum themes, Please help me and let me know how I can enable OEM unlock option on my phone.

I have updated my Pixel 4 XL with latest MAY20 system update.
[Google Pixel 4 XL Questions & Answers] Caltinpla:
https://xdaforums.com/pixel-4-xl/help/how-to-sim-unlock-pixel-4xl-t-mobile-t4081235
[Google Pixel 4 XL Questions & Answers] Purav786:
My phone is not network locked phone, I have a Sim unlocked phone.... Only issue is Developer option is greyed out and I want to enable it.
[Google Pixel 4 XL Questions & Answers] jljtgr:
It really depends on your carrier. If you bought it directly from Google (unlocked or Google Fi), it should be available without contacting anyone. I've heard that it might not be available until it has been activated for a few days with service. Otherwise, I've heard that you may need to fully wipe all user data before it becomes available. The process of OEM unlocking will wipe all user data as well, so you must be prepared for that eventuality.

If you did not get it from Google, the waters become murky and your success will vary.
[Google Pixel 4 XL Questions & Answers] Homeboy76:
If you bought a Pixel 4 XL with a unlockable bootloader, use this Guide to root.

Most Pixel 4 XL that are purchased from Carriers with the exception of Google Fi are not bootloader unlockable.
[Google Pixel 4 XL Questions & Answers] v12xke:
You aren't providing much useful information to solve your problem in your OP. Post a screenshot of your bootloader page, and what are the first two digits of your IMEI's. If you have already 100% WIPED your phone, skipped through setup and gone straight to dev settings with an active Wi-FI signal and get a greyed out OEM unlock , you will likely never succeed because you inadvertently purchased a bootloader locked phone.

SIM unlocked definitely does not equal BL unlockable.
[Google Pixel 4 XL Questions & Answers] Purav786:
So that means my phone is bootloader locked phone and there is no way to unlock it...
[Google Pixel 4 XL Questions & Answers] v12xke:
Remove SIM, factory reset from recovery, initiate setup enabling Wi-Fi, proceed to dev settings and check "Allow OEM unlocking". If you have completely wiped the phone and OEM unlocking is still greyed out, then your phone is bootloader locked and there is no workaround.
[Google Pixel 4 XL Questions & Answers] Letvamijeuglavi:
I downgraded my p40 lite to lowest version of emui...

which is 10.0.1.108 and oem unlock option appeared but its grayed out and I took advice from the guy in this thread that said call them and tell them you are developer and you need it to install android 11 and they were like oh ok then will figure this out and give you a call hahahahhaahahahhahah awesome dude it worked

---------- Post added at 02:39 PM ---------- Previous post was at 02:36 PM ----------

I saw there is a tool created by skyemie on github that uses bruteforce method to retrieve the unlock code so if they fix my oem grayed option then I will try that and give you all update if everything worked.
[Google Pixel 4 XL Questions & Answers] mostyle:
Just a FWIW: I bought two phones from Google directly and returned both since OEM was greyed out on both. Third try I purchased one off Swappa and it worked. Something to do with the IMEI... Search for posts started by me.. It's a looooong thread.
[Google Pixel 4 XL Questions & Answers] CoNsTaR:
If you got your pixel from Verizon, just call them and say that you're a developer and you need OEM unlocking. They'll need your IMEI and Verizon account number tho to check that you're the owner. If you got it second hand you may have to contact the person you bought it from.
[Google Pixel 4 XL Questions & Answers] V0latyle:
Do you have a source for this? The only official answer I've seen is that Verizon has no process in place to enable OEM unlocking. It's actually baked into the ROM.
[Google Pixel 4 XL Questions & Answers] CoNsTaR:
I did it. I saw someone saying that calling T-Mobile does the job so I just decided to call Verizon too and it worked.
[Google Pixel 4 XL Questions & Answers] V0latyle:
Well, that's interesting. What exactly were the circumstances, and how did you get unlocked? Such as, were you using the phone on the VZW network? Did they push a software update or something?
[Google Pixel 4 XL Questions & Answers] CoNsTaR:
From what I know, by the moment you install a Verizon SIM on your pixel, it becomes a Verizon phone. How they do this is that they'll add your phone's IMEI to their database, and until it's deleted from their database your phone will be a Verizon phone. You can check that by trying adding an eSIM, if it says anything about Verizon at the QR code step, you know it's still bound to Verizon.

I think the mechanism of checking if the phone is bound to any carrier is baked in the ROM, but not the information itself. I do see people saying that it needs time for the records to be propagated after they've removed you from their database, but YMMV.

Edit:

No, I wasn't on the VZW network.
[Google Pixel 4 XL Questions & Answers] V0latyle:
Right, and I'm asking exactly how you did it.
[Google Pixel 4 XL Questions & Answers] CoNsTaR:
The ONLY thing I did is to call them, tell them I am a developer and I need OEM unlocking, and provide the information they needed. Hope this answers your question.
[Google Pixel 4 XL Questions & Answers] bigmatt503:
I've called Verizon 6 times and talked to several reps and no idea what I'm talking about. I was even sent to 2nd tier and nothing. The 2nd tier rep said he's worked at vzw for 8 years and has never seen or heard of this happening. So I find this whole thing hard to believe.
[Google Pixel 4 XL Questions & Answers] CoNsTaR:
I am just providing my experience, and maybe someone will benefit from it. I came across this thread when I did my research so I thought I should share it here too.

If more details may help, I called them with the number 800-922-0204, on Oct 27 9:48 AM, the time I spent on the call was 36m4s (30m or so was waiting on the line), and I was on Fido network (Canadian).

When the system asked me about my area code or something like that before they connect me with a human, I both entered # key, and also chose something like I want to be a Verizon customer.

That's really all what I did, and I got it done on the first try. This was my first time calling Verizon, so I don't know much about 2nd tier or what not, but that's all I wanted to share here.
[Google Pixel 4 XL Questions & Answers] Pbsipher1:
hey guys I know I'm not in the right group but I've been looking at Any Pixel related posts to try to get OEM unlock and came across some options using dialer code *#*#0702#*#* which is ims setting, sim provisioning and a lot more in which are editable. could we find something to do with network unlock in those settings? I'm attaching screen shots of this find. I'm very limited in knowledge as this is my first pixel. oh and Btw I have the spectrum mobile variant of the Google pixel 7 pro. I have always been under the assumption that pixels were able to be flashed with official firmware without bootloader unlocked, but apparently pixel 7s have to have network unlock at least to enable OEM unlock toggle to flash official firmware even with the Android flash tool. if anybody could shine some light on this for me I would greatly appreciate it as I have never been able to come across this type of information before on any other device
[Google Pixel 4 XL Questions & Answers] yasir habib:
Is it necessary to remove sim card? As i factory reset my device but had esim downloaded not connected to network but no luck.

I am confused why option is grayed out. Can anyone also help to look for me why is my mobile bootloader locked.
[Google Pixel 4 XL Questions & Answers] v12xke:
Because you likely have a bootloader-locked variant. Do you know for certain the phone is carrier-unlocked (you can use a SIM from any carrier and it works no problem? If so you may have a chance. If the phone is carrier-locked it will also be bootloader-locked. The procedure I outlined is for a carrier-unlocked phone, forcing it to use Wi-Fi after a factory reset. If this method fails on a carrier-unlocked phone, either you have a bootloader-locked variant (EE, Verizon, etc.), or your phone has been blacklisted by IMEI (and there is no workaround).
[Google Pixel 4 XL Questions & Answers] yasir habib:
My phone is carrier unlocked as i can use any sim in my phone. And i checked on some online site for blacklisted but it showed clean. But still i have grayed out Oem unlock. Yesterday i reset my device to unlock oem but no luck.
[Google Pixel 4 XL Questions & Answers] v12xke:
Then it is more than likely you have one of the bootloader-locked variants.
[Google Pixel 4 XL Questions & Answers] yasir habib:
Is there any possibility that my phone could be a demo unit?
[Google Pixel 4 XL Questions & Answers] v12xke:
More likely you have just another bootloader-locked phone sold online as "unlocked". Buyers need to understand the difference between carrier-unlocked vs bootloader-unlocked. Sellers capitalize on buyer's misunderstanding. Bottom line is if you "need" a bootloader-unlocked phone, you need to specify/confirm that before purchase.
[Google Pixel 4 XL Questions & Answers] yasir habib:
So in this matter i can say there is no way to unlock. So sad. I never had pixel before and i had no idea there is some kind of bootloader restrictions otherwise i would have checked.