Database Users

Verizon Pixel XL - Unlocking Discussions

So I got my pixel XL from verizon today hoping that it would be like the nexus6 where they were nice and didn't lock it down. Well I was wrong. The good part is this. They (Verizon) have just disabled fastboot commands/connection. So we need to get that changed and we "should" be good. So if anyone has any ideas where to start on this feel free to chime in.

pjgraber03 said:
So I got my pixel XL from verizon today hoping that it would be like the nexus6 where they were nice and didn't lock it down. Well I was wrong. The good part is this. They (Verizon) have just disabled fastboot commands/connection. So we need to get that changed and we "should" be good. So if anyone has any ideas where to start on this feel free to chime in.
Click to expand...
Click to collapse
Step 1: Temp root
Step 2: Change buildprop
Step 3: enable oem unlocking from settings (or enable it in buildprop)
Step 4: fastboot oem unlock(i've read somewhere that there is a new command that replaces this)
Step 5: have fun

spy4ka said:
Step 1: Temp root
Step 2: Change buildprop
Step 3: enable oem unlocking from settings (or enable it in buildprop)
Step 4: fastboot oem unlock(i've read somewhere that there is a new command that replaces this)
Step 5: have fun
Click to expand...
Click to collapse
Has this been verified as working??

spy4ka said:
Step 1: Temp root
Step 2: Change buildprop
Step 3: enable oem unlocking from settings (or enable it in buildprop)
Step 4: fastboot oem unlock(i've read somewhere that there is a new command that replaces this)
Step 5: have fun
Click to expand...
Click to collapse
The new command is
"Fastboot flashing unlock"
Hope you guys figure it out how to enable oem unlock

Gizmoe said:
The new command is
"Fastboot flashing unlock"
Hope you guys figure it out how to enable oem unlock
Click to expand...
Click to collapse
Both commands work

cwalker0906 said:
Both commands work
Click to expand...
Click to collapse
Have you tried it? Because they don't both work on the last round of nexus devices. Just curious.

spy4ka said:
Step 1: Temp root
Step 2: Change buildprop
Step 3: enable oem unlocking from settings (or enable it in buildprop)
Step 4: fastboot oem unlock(i've read somewhere that there is a new command that replaces this)
Step 5: have fun
Click to expand...
Click to collapse
So how do u temp root

Gizmoe said:
Have you tried it? Because they don't both work on the last round of nexus devices. Just curious.
Click to expand...
Click to collapse
I have just tried fastboot oem unlock and got Failed (remote: OEM unlock is not allowed)?

GhostRider5666 said:
I have just tried fastboot oem unlock and got Failed (remote: OEM unlock is not allowed)?
Click to expand...
Click to collapse
I can't even get it to send commands to it... Won't recognize it as a fastboot devices

GhostRider5666 said:
I have just tried fastboot oem unlock and got Failed (remote: OEM unlock is not allowed)?
Click to expand...
Click to collapse
Cool so they added back the old command. Good I thought fastboot flashing sounded weird. I don't get mine til tomorrow. Got the wife's Verizon one today. Not even gonna mess with it :laugh:

pjgraber03 said:
I can't even get it to send commands to it... Won't recognize it as a fastboot devices
Click to expand...
Click to collapse
Works for me no problem. USB debugging enabled and on transfer files.

GhostRider5666 said:
Works for me no problem. USB debugging enabled and on transfer files.
Click to expand...
Click to collapse
With adb or fastboot

pjgraber03 said:
With adb or fastboot
Click to expand...
Click to collapse
adb

GhostRider5666 said:
adb
Click to expand...
Click to collapse
Ya my adb works fine... But u unlock in the bootloader with fastboot

pjgraber03 said:
Ya my adb works fine... But u unlock in the bootloader with fastboot
Click to expand...
Click to collapse
I know what I did wrong.

GhostRider5666 said:
I know what I did wrong.
Click to expand...
Click to collapse
do share?

pjgraber03 said:
do share?
Click to expand...
Click to collapse
Same thing with fastboot.

GhostRider5666 said:
Same thing with fastboot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Is your pixel from verizon?

pjgraber03 said:
Is your pixel from verizon?
Click to expand...
Click to collapse
YES

GhostRider5666 said:
YES
Click to expand...
Click to collapse
ok i got it
I needed to update my drivers.....SO it all comes down to that box in developer options.

"PHONE Locked" still green in bootloader

Firstly i am using this TOOL
I did a factory reset on my phone and settings > developer options > screen lock is off, enable oem unlock is on and USB debugging is on. When i go to the bootloader the "PHONE Locked" text is STILL green!
The tool shows this when i try to unlock the bootloader, the text "FRP Unlock" is red.

Try to unlock it via fastboot. Reboot your phone to bootloader mode, connect it to pc, open fastboot on pc and type in
fastboot oem unlock (and type here your unlock code without brackets)
Odesláno z mého HUAWEI VNS-L21 pomocí Tapatalk

dc239 said:
Try to unlock it via fastboot. Reboot your phone to bootloader mode, connect it to pc, open fastboot on pc and type in
fastboot oem unlock (and type here your unlock code without brackets)
Odesláno z mého HUAWEI VNS-L21 pomocí Tapatalk
Click to expand...
Click to collapse
Its not being detected by fastboot and i have HiSuite installed, stuck on waiting for device. Writing "fastboot devices" shows up nothing

MMS21 said:
Its not being detected by fastboot and i have HiSuite installed, stuck on waiting for device.
Click to expand...
Click to collapse
Do you have the correct drivers installed? Is it at least recognised in windows device manager?

https://imgur.com/a/EaUl7

It seems that it's installed correctly. Even if you type "fastboot devices" in fastboot, it isn't recognised?
Odesláno z mého HUAWEI VNS-L21 pomocí Tapatalk

dc239 said:
It seems that it's installed correctly. Even if you type "fastboot devices" in fastboot, it isn't recognised?
Odesláno z mého HUAWEI VNS-L21 pomocí Tapatalk
Click to expand...
Click to collapse
Still isnt recognised

Hmm, Did you had any popup on the phone asking you to enable debugging from this pc (or something like that) after you connected it to the pc?

dc239 said:
Hmm, Did you had any popup on the phone asking you to enable debugging from this pc (or something like that) after you connected it to the pc?
Click to expand...
Click to collapse
USB debugging was already enabled

I mean if you had a popup like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

dc239 said:
I mean if you had a popup like this
Click to expand...
Click to collapse
How do i get that to happen again? I cannot remember if it came up.

type in adb "adb devices" and it should came up

MMS21 said:
https://imgur.com/a/EaUl7
Click to expand...
Click to collapse
Your problem isn't in adb mode. It is in fastboot mode that probably you have corrupted drivers. (like kedacom usb device).
So you need to correct it, look these pictures and try to update software drivers manually (don't reed text cause in italian but it's the same process):
1) http://prnt.sc/d0t8m1
2) http://prnt.sc/d0t9ui
3) http://prnt.sc/d0ta8h
4) http://prnt.sc/d0tatf

It looks like this now https://imgur.com/a/oRzoO, when i type fastboot into CMD it comes up with a bunch of stuff so its correctly installed. fastboot isnt recognising my phone.

MMS21 said:
It looks like this now https://imgur.com/a/oRzoO, when i type fastboot into CMD it comes up with a bunch of stuff so its correctly installed. fastboot isnt recognising my phone.
Click to expand...
Click to collapse
Do you now how to change that as in my picture?

SevenSlevin said:
Do you now how to change that as in my picture?
Click to expand...
Click to collapse
I changed it after looking at the instructions you sent me, its changed now but still doesnt work.

help
help, i'm too stucked in the samed problem, phone locked and nothing work
plz help

how to hard brick my phone to qhsusb_bulk mode??

Hello,
i have flashed the wrong bootloader and now i my bootloader is oem_locked, and i have no OS.
I cannot flash anything. how to hard brick my phone to qhsusb_bulk mode so i can flash another bootloader to fix my problem?
Can i open and short my phone somehow to be able to get into the Qualcomm Download mode?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

EDIT: mistake second post.

www(dot)droidsavvy(dot)com/unbrick-qualcomm-mobiles/
forums(dot)oneplus(dot)net/threads/fix-qhsusb_bulk-brick-on-the-opo.408420/
Check out these two pages, see if they can help you.
(I can't post outside links yet)

nlpl931 said:
www(dot)droidsavvy(dot)com/unbrick-qualcomm-mobiles/
forums(dot)oneplus(dot)net/threads/fix-qhsusb_bulk-brick-on-the-opo.408420/
Check out these two pages, see if they can help you.
(I can't post outside links yet)
Click to expand...
Click to collapse
That is the problem i don't know how to enter the QHSUSB_BULK mode on my phone because i can only accesss fastboot

Have you tried erasing about, modem, persist... partitions, and then flashing the appropriate images?

nlpl931 said:
Have you tried erasing about, modem, persist... partitions, and then flashing the appropriate images?
Click to expand...
Click to collapse
i cannot im affraid. Bootloader is locked, and i cannot unlock it.
When i try to unlock it says that i need to enable oem unlock but i have no android installed..

Actually it's not qhsusb_bulk mode that you need, you need QDloader mode which can be accessed through the qhsusb_bulk mode. If you run Windows,
#1. CMD(admin)
#2. bcdedit.exe -set load options
DDISABLE_INTEGRITY_CHECKS
bcdedit.exe -TESTSIGNING ON
#3. Reboot your computer keeping​ your phone connected to the computer
#4. On booting go to device manager
#5. You should see a new device entry with QHSUSB_BULK under Qualcomm devices(or any other Qualcomm entry)
#6. This is the QHSUSB_BULK mode that you can use to get into QDloader mode using appropriate drivers, as in the links I posted.
I'll look for more info, if I can help you?
---------- Post added at 12:11 AM ---------- Previous post was at 12:09 AM ----------
codGmer said:
i cannot im affraid. Bootloader is locked, and i cannot unlock it.
When i try to unlock it says that i need to enable oem unlock but i have no android installed..
Click to expand...
Click to collapse
Try going through the process of unlocking bootloader....and I have a feeling that it will work, since you don't need to boot your phone for unlocking the bootloader. You can find guides for that....

nlpl931 said:
Actually it's not qhsusb_bulk mode that you need, you need QDloader mode which can be accessed through the qhsusb_bulk mode. If you run Windows,
#1. CMD(admin)
#2. bcdedit.exe -set load options
DDISABLE_INTEGRITY_CHECKS
bcdedit.exe -TESTSIGNING ON
#3. Reboot your computer keeping​ your phone connected to the computer
#4. On booting go to device manager
#5. You should see a new device entry with QHSUSB_BULK under Qualcomm devices(or any other Qualcomm entry)
#6. This is the QHSUSB_BULK mode that you can use to get into QDloader mode using appropriate drivers, as in the links I posted.
I'll look for more info, if I can help you?
---------- Post added at 12:11 AM ---------- Previous post was at 12:09 AM ----------
Try going through the process of unlocking bootloader....and I have a feeling that it will work, since you don't need to boot your phone for unlocking the bootloader. You can find guides for that....
Click to expand...
Click to collapse
ill try the steps. But the unlocking is not going to work because the first step is use
Code:
fastboot oem get_unlock_data
returns this:
so i cannot unlock my phone by the official way.

Then I guess you will need to jump through all those hoops...

nlpl931 said:
Then I guess you will need to jump through all those hoops...
Click to expand...
Click to collapse
What hoops? Those steps?

#5. You should see a new device entry with QHSUSB_BULK under Qualcomm devices(or any other Qualcomm entry)
Click to expand...
Click to collapse
none of those show up, because i can only boot into fastboot not the black screen with flashing light.

Did you manage to fix it?
Did you manage to get your phone fixed? Mine is doing the same thing you said, I can not flash anything, and the "qualcomm unbrick" guides do not work for me, I dont see any Qualcom Loader in my Devices Manager, but I do see an Android Device when I plug it to my pc.
I can only get to fastboot mode, can not flash anything, my bootloader is locked, and it trhows the same error (read datablock error) when I try to unlock it.
Thanks in advance

same situation
jalbarran said:
Did you manage to get your phone fixed? Mine is doing the same thing you said, I can not flash anything, and the "qualcomm unbrick" guides do not work for me, I dont see any Qualcom Loader in my Devices Manager, but I do see an Android Device when I plug it to my pc.
I can only get to fastboot mode, can not flash anything, my bootloader is locked, and it trhows the same error (read datablock error) when I try to unlock it.
Thanks in advance
Click to expand...
Click to collapse
Could you solve the problem friend? I am also in that situation, greetings

Try to choose QCOM mode in a bootloader

I too had the same problem and solved it.
You can't reboot into bootloader so can't flash stock firmware. I had the same problem and was able to solve it using few tutorials.
Here is a youtube video to solve this problem: https://www.youtube.com/watch?v=m2NqpY6X-X4
Watch the entire video. He had a proper running device and then purposely bricked his device to bring into the same state as your device.
Then he solved it.
Here is the xda thread that was used to create the above video: https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
The above video was made using this xda thread and I am not the owner of the video or the thread.
I would suggest watch the video and follow it as its more continent.
Note: there was a step in the above mentioned thread which was to be done. I did it and faced problem (the computer then didn't even recognize the device as qhsusb_bulk and showed "usb device not recognized"). Had to reset my pc and then skipped that step. That step is also skipped in he youtube video.
These are the two lines which I skipped writing in cmd and it worked:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
---------- Post added at 08:34 AM ---------- Previous post was at 08:28 AM ----------
jalbarran said:
Did you manage to get your phone fixed? Mine is doing the same thing you said, I can not flash anything, and the "qualcomm unbrick" guides do not work for me, I dont see any Qualcom Loader in my Devices Manager, but I do see an Android Device when I plug it to my pc.
I can only get to fastboot mode, can not flash anything, my bootloader is locked, and it trhows the same error (read datablock error) when I try to unlock it.
Thanks in advance
Click to expand...
Click to collapse
Did you try unlocking the bootloader? If you are able to do that then you will be able to flash. I don't know why device is unable to flash stock firmware with locked bootloader

david_7 said:
Could you solve the problem friend? I am also in that situation, greetings
Click to expand...
Click to collapse
I had to buy another phone! I just couldn't fix it in any way.
I even took it to a guy who works fixing phones, and he said it had the motherboard bricked! And there's no solution for that, other than buying another board (expensive!!)

so confused and feeling unlucky

sorry for the long talk but i am so confused, i hope anyone can help
i tried alot of custom roms, all of them load the logo then restart and never stop, i asked before but no one could offer solution.
i felt so stupid everyone was replying thanks thanks works works works
i found in asus forum someone saying the problem is with the baseband i found (modem.bin modemst1.bin modemst2.bin) for my model and flashed a rom (OCT-N-WEEKLY-20170811-0914-Z00L.zip) somehow booted with no wifi or imei when i restarted it never boot again , flashed again as well but also never boot again
so i decided to reinstalled the stock rom again, to find no signal, wifi, imei, and Bluetooth dead, i pulled the firmware files from another device and pushed to mine, everything works now but i can only make calls but can't receive, data connection not working and imei still 0, i rooted the devices and tried to write the imei again but never worked, i tried to enable the diag mode but never enabled, tried a lot of times with diff versions of stock roms, then i tried to downgrade to stock lolipop maybe it will work (flashed successfully) but never pass boot animation.
now i am only stuck with Marshmallow can't receive calls or enable data connections !!!
any suggestions please
list of everything i tried
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Write QCN file using qpst tool
You can find about writing QCN file on YouTube.

suhailmalik said:
Write QCN file using qpst tool
You can find about writing QCN file on YouTube.
Click to expand...
Click to collapse
thanks for answering, but QPST requires enabling diag mode which i tried several times with two diff devices both rooted bootloader unlocked, debugging enabled and didn't work

Use minimal adb and fastboot tool.
Open your phone usb debugging
Enter commands
"adb shell"
"su"
(Now give root access on phone screen)
"setprop sys.usb.config diag,adb"
Diag port enabled...
Note - 1. phone must be rooted
2. Enter commands without quotes
3. After entered every commands press enter
4. Adb driver must be installed on your PC/laptop.

suhailmalik said:
Use minimal adb and fastboot tool.
Open your phone usb debugging
Enter commands
"adb shell"
"su"
(Now give root access on phone screen)
"setprop sys.usb.config diag,adb"
Diag port enabled...
Note - 1. phone must be rooted
2. Enter commands without quotes
3. After entered every commands press enter
4. Adb driver must be installed on your PC/laptop.
Click to expand...
Click to collapse
thats's wat i did exactly several times with two diff devices and diff versions of Marshmallow
please know can u tell me
what's the diff between roms ends with
secured-release.zip, secured-releaseAFT.zip, and secured-releaseAFT_QC.zip
cause i am downloading them all now and u will try all
and what is this file [firmware27]CSCimage_WW-ZE550KL-ZE600KL-1.21.2.230-fac-eng-20151116-signedAFT_QC used for cause i flashed it seems like there's nothing happened :laugh::laugh:

What is your phone module???

suhailmalik said:
What is your phone module???
Click to expand...
Click to collapse
OOOHHHHHH finally downgraded to lollipop using this rom [firmware27]WW_ZE550KL_1.17.40.1737-rel-user-20160701204733-secured-release
thanks man
i will try now enabling diag mode

my zenfone 2 leser Z00ld is stuck in fastboot mode after installing oreo is not boot
suhailit said:
Write QCN file using qpst tool
You can find about writing QCN file on YouTube.
Click to expand...
Click to collapse
plzzz help broo

[GUIDE] How to Unlock Bootloader Xiaomi Mi A2

Clarifications:
No matter the version of Android that our Smartphone has, the procedure is the same.
When unlocking the bootloadrer all our personal data and applications of the smartphone will be erased, I recommend making a backup of our personal files.
Requirements:
We will obviously need our Xiaomi Mi A2 and have a PC.
Steps:
1-Preparing the smartphone
Enable oem debugging and usb debugging:
Open Setting> System> About Phone> Press where it says "Buil Number" until you enable the developer options. Let's go back a step, and we will see that within the options of "System" a new one will appear, called "Developer options"; we enter it, and within the options we have to enable "OEM unlocking" and "USB debugging".
Then we will proceed to turn off our smartphone.
Once turned off, we will press at the same time volume - and power for about 5 seconds, until our cell phone turns on (this in order to enter the fastboot mode), if everything was done correctly, the following image will appear on your screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We connect the cell phone to the PC
2-Preparing the PC
Install Drivers
For me the best way to install the drivers is as follows (if you know a better way I accept suggestions)
Download the tool My Unlock
Extract the zip file into a new folder on our pc, double click to execute the file called "miflash_unlock", we will open the application, top right of it will be the "wheel" of settings , we click on it to enter; a new window is displayed, and where it says "My Usb Driver" we click on "Check"; a "Connect your device again" notice will appear, we disconnect and connect our cell phone to the PC again, and we will have the driver installed.
We can close, we do not need this app anymore
Install the adb tools on the PC
Download the installer
1. Run it (Require administrator privileges)
2. Press Y / Yes to install ADB and Fastboot or N / No to skip
3. Press Y / Yes to install ADB system-wide or N / No for current user only
4. Press Y / Yes to install Drivers or N / No to skip
5. Continue Driver installation
6. 15 seconds passed - finished!
3-Finally we will proceed to unlock the bootloader
Download the following folder "UNLOCK BOOTLOADER XIAOMI MI A2"
We enter in it, we will find a .bat file called "unlock auto" (we make sure to have our smartphone connected to the PC in fastboot mode) we double click to execute it.
Immediately on our cell phone will appear a warning on the screen about which we are going to unblock the bootloader. And pressing twice volume -, select the option "unlock the bootloader", then press the button "power" and our smartphone will restart a couple of times, all our information will be erased and we will have the bootloader unlocked.
Suggestion:
Once the bootloader is unlocked, I advise you to turn off your smartphone again and enter fastboot mode again, go back to the "UNLOCK BOOTLOADER XIAOMI MI A2" folder and double-click the .bat file called "flash unlock critical", this with the purpose, that when we want to restore our smartphone and flash the stock firmware we have no problems.
Here I leave a video on YouTube that is a visual guide to the procedure.

Reserved

Code:
fastboot flashing unlock
fastboot flashing unlock_critical
Works for mi a2.

Nice I will try

hi, I need help
I just want to retract the bootloader (lock it again if it's possible), I need help on this

rinyuuri said:
I just want to retract the bootloader (lock it again if it's possible), I need help on this
Click to expand...
Click to collapse
First flash stock ROM then run this command:
Code:
fastboot flashing lock

this work on PIE?

byrortiz said:
this work on PIE?
Click to expand...
Click to collapse
Why not?

S /\ E E D said:
Why not?
Click to expand...
Click to collapse
That does not answer my question.... The information was posted before Pie Update, I don't want to brick my phone...

byrortiz said:
That does not answer my question.... The information was posted before Pie Update, I don't want to brick my phone...
Click to expand...
Click to collapse
these 2 commands (flashing unlock & unlock_critical) are bootloader commands and doesn't relate to android version,
you can run it on android 8, 9, 10, ... !!

S /\ E E D said:
Why not?
Click to expand...
Click to collapse
S /\ E E D said:
these 2 commands (flashing unlock & unlock_critical) are bootloader commands and doesn't relate to android version,
you can run it on android 8, 9, 10, ... !!
Click to expand...
Click to collapse
Thanks man, That's the Answer I wanted to hear

byrortiz said:
Thanks man, That's the Answer I wanted to hear
Click to expand...
Click to collapse
No problem, anyway you can use thanks button

Does unlocking the bootloader fail safety net on this device?

Ashik_salim_ said:
Does unlocking the bootloader fail safety net on this device?
Click to expand...
Click to collapse
No

fast_retina said:
No
Click to expand...
Click to collapse
That's what i thought. But nope. It failed upon unlocking.. Re-flashed stock (from stock) and then locked bootloader, passed safety net

Ashik_salim_ said:
That's what i thought. But nope. It failed upon unlocking.. Re-flashed stock (from stock) and then locked bootloader, passed safety net
Click to expand...
Click to collapse
It passes if you flash Magisk

Corrupted file
The file is corrupted
Can u check it plz?
*edit
everything work, just bug on my computer

S /\ E E D said:
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
Works for mi a2.
Click to expand...
Click to collapse
Only this two commands or "fastboot oem unlock" too?

MattGameRPL said:
Only this two commands or "fastboot oem unlock" too?
Click to expand...
Click to collapse
fastboot oem unlock command is old, use
fastboot flashing unlock command
Then run fastboot flashing unlock_critical and you are done

I unlocked the bootloader and then It started looping
So i flushed a rom with mi flush now im stuck on android logo what can i do? ki