Here is a good Video guide witch worked for me to unbrick my pixel
Idk if it works when you have your usb debugging off but you can still try.
If it doesn't, try to find sideload methods to unbrick your pixel.
Also keep in mind that you have to have already installed usb drivers - adb drives etc on your pc.
Don't use type c to type c cables because installation will end with a bootloop or an error.
Use onky Usb to type C ...
its NECESSARY..(S.O.S)
Noexcusses said:
Here is a good Video guide witch worked for me to unbrick my pixel
Idk if it works when you have your usb debugging off but you can still try.
If it doesn't, try to find sideload methods to unbrick your pixel.
Also keep in mind that you have to have already installed usb drivers - adb drives etc on your pc.
Don't use type c to type c cables because installation will end with a bootloop or an error.
Use onky Usb to type C ...
its NECESSARY..(S.O.S)
Click to expand...
Click to collapse
Android Flash Tool only works if both USB Debugging and OEM Unlocking are enabled. If you cannot enable OEM Unlocking, the tool will not work.
V0latyle said:
Android Flash Tool only works if both USB Debugging and OEM Unlocking are enabled. If you cannot enable OEM Unlocking, the tool will not work.
Click to expand...
Click to collapse
Of you can not enable oem unlock your doing it with side load. Is also easy
Noexcusses said:
Of you can not enable oem unlock your doing it with side load. Is also easy
Click to expand...
Click to collapse
If you're able to access bootloader and/or recovery, your device is not bricked.
V0latyle said:
If you're able to access bootloader and/or recovery, your device is not bricked.
Click to expand...
Click to collapse
I said if you can not.
Noexcusses said:
I said if you can not.
Click to expand...
Click to collapse
Then we go back to my previous post - Android Flash Tool won't work if OEM Unlocking isn't enabled, meaning sideloading an update is the only option. If that doesn't work, recovery is impossible and the device is bricked. If any of these options works, the device is not bricked.
V0latyle said:
Then we go back to my previous post - Android Flash Tool won't work if OEM Unlocking isn't enabled, meaning sideloading an update is the only option. If that doesn't work, recovery is impossible and the device is bricked. If any of these options works, the device is not bricked.
Click to expand...
Click to collapse
We have two options, soft brick and hard brick. Brick is whenever our phone cant load rom on his own and stuck to bootloader
Related
Hello, I have read about this problem but I still have some questions.
The phone was stock, not rooted or anything, a friend of mine tried to uptate the phone via OTA with only 8 percent of battery so now the phone is stuck in google screen.
I read about this here http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1 about fastboot commands but the problem is that I have not never checked the USB debugging mode.
It shows "Device is locked" and "Status code:2"
Thanks, I hope it works again.
You don't need debugging enabled to use fastboot. That's only for issuing commands while in the OS.
Nothing you can do if "Enable OEM Unlock" is not selected. Needs to be sent to Google / Motorola.
danarama said:
Nothing you can do if "Enable OEM Unlock" is not selected. Needs to be sent to Google / Motorola.
Click to expand...
Click to collapse
Thanks, but wait, I'm just wondering, I have read that every nexus has its OEM thing unlocked from the beginning, so how you asumme it is off?
espinal123 said:
Thanks, but wait, I'm just wondering, I have read that every nexus has its OEM thing unlocked from the beginning, so how you asumme it is off?
Click to expand...
Click to collapse
Almost correct. On 5.0, it seemed to work if you unlock before booting device first time without checking the setting. But won't work since 5.1
Sorry, I assumed you'd actually tried to unlock the bootloader. If you haven't, you probably should try. That will tell you once and for all whether you need to return it or not.
danarama said:
Almost correct. On 5.0, it seemed to work if you unlock before booting device first time without checking the setting. But won't work since 5.1
Sorry, I assumed you'd actually tried to unlock the bootloader. If you haven't, you probably should try. That will tell you once and for all whether you need to return it or not.
Click to expand...
Click to collapse
Thanks, So i tried to unlock it through the NRT nexus root toolkit and it says this:
fastboot devices
ZX1G22KCPZ fastboot
Connectivity Status: Fastboot Device Connected
fastboot oem unlock
Click to expand...
Click to collapse
Then it asks me to reboot and enable debugging thing, so I cannot, do you thing is unlock? Now I'm gonna try to "flash stock + unroot" on this program, I'll let you know.
Thanks.
graydiggy said:
You don't need debugging enabled to use fastboot. That's only for issuing commands while in the OS.
Click to expand...
Click to collapse
Thanks, but this guide says that you have to turn the debuggin mode on. I tried to flash, (assuming OEM is on) through the Nexus tool kit but it gave me a lot of fails.
@Evolution_Tech
Aren't you more versed in this area? Maybe you can lend a hand?
graydiggy said:
@Evolution_Tech
Aren't you more versed in this area? Maybe you can lend a hand?
Click to expand...
Click to collapse
USB debugging shouldn't matter, what matters is having the "allow OEM unlock" setting enabled.
Evolution_Tech said:
USB debugging shouldn't matter, what matters is having the "allow OEM unlock" setting enabled.
Click to expand...
Click to collapse
He is trying to use toolkit. It requires USB debug enabled as it uses both adb and fastboot. Needs to forget the toolkit and go to manual fastboot.
prdog1 said:
He is trying to use toolkit. It requires USB debug enabled as it uses both adb and fastboot. Needs to forget the toolkit and go to manual fastboot.
Click to expand...
Click to collapse
+1
That's what I was thinking. However I'm not as familiar with manual fastboot. I also don't have a computer at hand at the moment so I can't quickly get all the commands for the OP.
---------- Post added at 01:45 PM ---------- Previous post was at 01:43 PM ----------
Since it seems that there is no OEM unlock on the device, would he be able to push a factory image to the phone and install it like a regular update through recovery?
Evolution_Tech said:
USB debugging shouldn't matter, what matters is having the "allow OEM unlock" setting enabled.
Click to expand...
Click to collapse
OEM seems that is Unlock, the toolkit says this.
fastboot devices
ZX1G22KCPZ fastboot
Connectivity Status: Fastboot Device Connected
fastboot oem unlock
Click to expand...
Click to collapse
Now, that toolkit doesn´t work, so I'm trying to use fasboot thing. But it seems that I need debbuggin thing On, I'm using this guide http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1 I don't know how to do this things I just do what the guide says.
So the big question is how can I flash wihout usb debugging thing enabled.
Thanks :good:
espinal123 said:
[/COLOR]Since it seems that there is no OEM unlock on the device, would he be able to push a factory image to the phone and install it like a regular update through recovery?
Click to expand...
Click to collapse
OEM seems that is Unlock, the toolkit says this.
Now, that toolkit doesn´t work, so I'm trying to use fasboot thing. But it seems that I need debbuggin thing On, I'm using this guide http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1 I don't know how to do this things I just do what the guide says.
So the big question is how can I flash wihout usb enabled.
Thanks :good:[/QUOTE]
Flashing via fastboot does not need USB debugging enabled. If your bootloader IS unlocked, you are good to go.
If I'm not mistaken debugging is for inside the OS only... It's been like that for my Samsung devices. It's so your computer can push a command to the phone while it's completely booted. Don't worry about the toolkit from this point. I'm sorry I can't be of more assistance. Just give us a little more time and we shall get you sorted. Hopefully
Have you ever just tried entering recovery and doing a factory reset?
---------- Post added at 03:21 PM ---------- Previous post was at 03:20 PM ----------
Otherwise, from fastboot, just try: fastboot format cache
Evolution_Tech said:
Have you ever just tried entering recovery and doing a factory reset?
---------- Post added at 03:21 PM ---------- Previous post was at 03:20 PM ----------
Otherwise, from fastboot, just try: fastboot format cache
Click to expand...
Click to collapse
I cannot enter to recovery, It appears a dead android and a warning sign on his chest. But I already did through fastboot command as you say, but I don't know how to flash in fastboot i cannot find the proper guide.
I already did the command "fastboot devices" and it recognizes my device. I tried to put a new recovery but it wont let me.
espinal123 said:
I cannot enter to recovery, It appears a dead android and a warning sign on his chest. But I already did through fastboot command as you say, but I don't know how to flash in fastboot i cannot find the proper guide.
I already did the command "fastboot devices" and it recognizes my device. I tried to put a new recovery but it wont let me.
Click to expand...
Click to collapse
OK, first, when the "dead android" appears, hold power and press volume up once. That is the normal procedure for entering stock recovery.
Second, why can you not flash a custom recovery? I have a strong suspicion that your bootloader is locked and there is some communication issues here. Go to stock recovery and do a factory data reset.
Evolution_Tech said:
OK, first, when the "dead android" appears, hold power and press volume up once. That is the normal procedure for entering stock recovery.
Second, why can you not flash a custom recovery? I have a strong suspicion that your bootloader is locked and there is some communication issues here. Go to stock recovery and do a factory data reset.
Click to expand...
Click to collapse
Thanks, I cannot enter recovery mode as you said, I also cannot "fastboot oem unlock". Here's one picture.
At least it recognizes my device.(as youll see in the picture)
Does it mean my oem thing is blocked? And I cannot do anything?
If so, what about this http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
espinal123 said:
Thanks, I cannot enter recovery mode as you said, I also cannot "fastboot oem unlock". Here's one picture.
It recognizes my device, does it mean my oem thing is blocked? And I cannot do anything?
If so, what about this http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Click to expand...
Click to collapse
No, that fix does not apply here.
I'm going to try this once more.
Disconnect from your PC.
Power off your nexus.
Hold power+volume down to enter bootloader.
Once in bootloader, use volume down to select recovery mode. Press power to select it.
Once dead android appears, hold power button and press volume up once.
Once in recovery, use volume down to highlight " wipe data/factory reset "
Press power to select.
Reboot when prompted.
If the device boots up, wait patiently for the reset to completely finish. It may take as long as 20 minutes or more.
If this processes doesn't work, you have one option, RMA.
Hi,
I looked all over the place but could not find a way to unlock the bootloader of the latest version of my device. Currently running Android 6.0 H81120p and rooting this version as well!
hammy88 said:
Hi,
I looked all over the place but could not find a way to unlock the bootloader of the latest version of my device. Currently running Android 6.0 H81120p and rooting this version as well!
Click to expand...
Click to collapse
i recommend for you to KDZ 20p refurbished..
and heres the instruccions same as 20i
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
i tried but its not working as i get stuck on waiting for device after i type the command to reboot to bootloader, installed google usb drivers , lg drivers and all but nothing seemed to be fixing the issue
hammy88 said:
i tried but its not working as i get stuck on waiting for device after i type the command to reboot to bootloader, installed google usb drivers , lg drivers and all but nothing seemed to be fixing the issue
Click to expand...
Click to collapse
did you click on screen when you gave the command to go into fastboot it shows some sort of numbers and leters and asks you if you want to allow phone .??/ did you
Yes I did allow the computer to have access to the phone, when i typed the command to reboot to bootloader it did, but then when i type the command to fastboot oem unlock it gets stuck on waiting for any device. I tried doing it again just to check, after i get to bootloader, i typed adb devices it doesn't show any device thats connected
hammy88 said:
Yes I did allow the computer to have access to the phone, when i typed the command to reboot to bootloader it did, but then when i type the command to fastboot oem unlock it gets stuck on waiting for any device. I tried doing it again just to check, after i get to bootloader, i typed adb devices it doesn't show any device thats connected
Click to expand...
Click to collapse
adb reboot bootloader (phone reboots to bootloader)
fastboot oem unlock (this wipes ALL data!!)
debugging tick and unlock oen in dev options.?
raptorddd said:
adb reboot bootloader (phone reboots to bootloader)
fastboot oem unlock (this wipes ALL data!!)
debugging tick and unlock oen in dev options.?
Click to expand...
Click to collapse
I checked the oem unlock, and the USB debugging thing is checked as well. Developers Options is on but same issue. I installed the latest USB drivers, installed Google USB drivers. I went to device Manger and I can't see that my device is even connected!
hammy88 said:
I checked the oem unlock, and the USB debugging thing is checked as well. Developers Options is on but same issue. I installed the latest USB drivers, installed Google USB drivers. I went to device Manger and I can't see that my device is even connected!
Click to expand...
Click to collapse
can try another computer maybe. i use the drivers from LGUP..
am afraid i do not know how to proceed from here. am pretty sure you are not alonei gave read someting similar but.. i didnt pay attention
I tried 3 other computers , did not help resolve the issue
hammy88 said:
I tried 3 other computers , did not help resolve the issue
Click to expand...
Click to collapse
i came across this try it.
http://forum.xda-developers.com/showpost.php?p=69339003&postcount=2
Use Linux dude, also try different cables. My stock g4 came with a bad cable that only charged.
I've had exactly the same problem as hammy88. Is what is referred to as "fastboot mode" the same as download mode? I know it's relatively easy to get into download mode. But "adb reboot bootloader" doesn't work for me.
Fastboot mode ≠ Download mode
If you did tick "Enable OEM unlock" , and adb reboot bootloader doesn't work, then I guess is BL is locked now.
I tried the method , i found that Android Bootloader does not have a green light, so i went to device manager to try to update the driver but it wasn't even there, clicked on view to show the hidden items or whatever then found android device, when i clicked update the driver i could not find the Google fastboot thing to update it with, all i got was either LG usb or ADB interface even thoough i downloader google fastboot usb drivers few days ago
hammy88 said:
I tried the method , i found that Android Bootloader does not have a green light, so i went to device manager to try to update the driver but it wasn't even there, clicked on view to show the hidden items or whatever then found android device, when i clicked update the driver i could not find the Google fastboot thing to update it with, all i got was either LG usb or ADB interface even thoough i downloader google fastboot usb drivers few days ago
Click to expand...
Click to collapse
Brother, be calm. Find the fastboot drivers. And update.
You will figure it out. Just do it.
I just received moto g6 today and trying to unlock the bootloader.
I can turn on allow OEM unlocking in developer option, but it is turn off every time restarted.
What should I do to unlock the bootloader.
llaalways said:
I just received moto g6 today and trying to unlock the bootloader.
I can turn on allow OEM unlocking in developer option, but it is turn off every time restarted.
What should I do to unlock the bootloader.
Click to expand...
Click to collapse
You have to request an unlock code on the Motorola website there are instructions all over the form to do it
madbat99 said:
You have to request an unlock code on the Motorola website there are instructions all over the form to do it
Click to expand...
Click to collapse
i understand i need get an unlock code from Motorola. but i am stuck at one step before that. i cannot get the unlock information by fastboot command. as i am not able to access the phone from computer when phone is in bootloader mod.
llaalways said:
i understand i need get an unlock code from Motorola. but i am stuck at one step before that. i cannot get the unlock information by fastboot command. as i am not able to access the phone from computer when phone is in bootloader mod.
Click to expand...
Click to collapse
Did you install all the Moto drivers? Are you issuing fastboot commands?
You have ADB and fastboot installed?
Fastboot devices
Make sure you use the cord that came with the phone. Maybe try a different port on your PC
madbat99 said:
Did you install all the Moto drivers? Are you issuing fastboot commands?
You have ADB and fastboot installed?
Fastboot devices
Make sure you use the cord that came with the phone. Maybe try a different port on your PC
Click to expand...
Click to collapse
Not sure about the moto drivers. the computer recognize phone when boot on system.
is there a special driver I can install for bootloader /fastboot mod?
I have ADB and fastboot installed.
fastboot devices show nothing
I am using the cable come with the phone.
I will try on other PC later.
thanks!
I resolved the problem by install Motorola Device Manager.
madbat99 said:
Did you install all the Moto drivers? Are you issuing fastboot commands?
You have ADB and fastboot installed?
Fastboot devices
Make sure you use the cord that came with the phone. Maybe try a different port on your PC
Click to expand...
Click to collapse
llaalways said:
I resolved the problem by install Motorola Device Manager.
Click to expand...
Click to collapse
Ok. That installs the drivers for you.
With your phone on, make sure under developer options oem unlocking is allowed. . .
Then plug in the device to the computer....
Time for the fun to begin....
In ADB
Adb reboot bootloader (it takes your phone to bootloader mode)
Fastboot flashing unlock (warns you not to)
Click Yes when prompted on phone. (YAY!!!)
Please don't forget to save anything you need from ur phone , unlocking your bootloader will fully wipe your device ?
Quick question, Is it supposed to just be text on the bottom left that says fastboot mode?. I've done this on a couple of other phones but this is the first time I haven't seen a menu, also when I run fastboot flashing unlock I'm stuck on fastboot flashing unlock.
TheRedPandaSSN said:
Quick question, Is it supposed to just be text on the bottom left that says fastboot mode?. I've done this on a couple of other phones but this is the first time I haven't seen a menu, also when I run fastboot flashing unlock I'm stuck on fastboot flashing unlock.
Click to expand...
Click to collapse
Yes fastboot mode ... On the left bottom.
Do u have mediatek drivers installed ?
Did u go into developer options and click on the allow oem unlocking ?
greeneyez15o said:
Yes fastboot mode ... On the left bottom.
Do u have mediatek drivers installed ?
Did u go into developer options and click on the allow oem unlocking ?
Click to expand...
Click to collapse
I believe I have them installed but I'll try again, thanks.
TheRedPandaSSN said:
I believe I have them installed but I'll try again, thanks.
Click to expand...
Click to collapse
Edit: I've tried a couple of drivers but none seem to work.
TheRedPandaSSN said:
Edit: I've tried a couple of drivers but none seem to work.
Click to expand...
Click to collapse
https://androidmtk.com/download-mtk-driver-auto-installer
Try this
Tied all sorts of drivers but no luck. I'm stuck in fastboot <waiting for device>. Any suggestions?
USB debugging
ycgr2002 said:
Tied all sorts of drivers but no luck. I'm stuck in fastboot <waiting for device>. Any suggestions?
Click to expand...
Click to collapse
Have you enabled USB DEBUGGING?
ycgr2002 said:
Tied all sorts of drivers but no luck. I'm stuck in fastboot <waiting for device>. Any suggestions?
Click to expand...
Click to collapse
Here
fastboot does not respond to commands
brunkonjaa said:
Here
Click to expand...
Click to collapse
Same issues, run adb reboot bootloader and reboots but in funky fastboot. When sending fastboot commands such as fastboot devices nothing happens its not responding. Also if you get into fastboot via power and volume up, and connect to pc and try to run any fastboot commands no response back.
jackmaddy said:
Same issues, run adb reboot bootloader and reboots but in funky fastboot. When sending fastboot commands such as fastboot devices nothing happens its not responding. Also if you get into fastboot via power and volume up, and connect to pc and try to run any fastboot commands no response back.
Click to expand...
Click to collapse
Turn on your phone, and do not connect to pc. Revoke USB debugging authorisation. Disable USB debugging. Enable USB debugging. Now connect your phone to pc. You should get a message on your phone about allowing USB debugging from that pc. Click don't ask again and then yes.
If you don't get that message try accessing phones storage through pc , that should prompt the phone to ask you about allowing USB debugging from that pc.
So click yes.
Now you should be able to run fastboot commands without problems.
brunkonjaa said:
Turn on your phone, and do not connect to pc. Revoke USB debugging authorisation. Disable USB debugging. Enable USB debugging. Now connect your phone to pc. You should get a message on your phone about allowing USB debugging from that pc. Click don't ask again and then yes.
If you don't get that message try accessing phones storage through pc , that should prompt the phone to ask you about allowing USB debugging from that pc.
So click yes.
Now you should be able to run fastboot commands without problems.
Click to expand...
Click to collapse
No, sorry that is wrong.
ADB permission is not needed for fastboot. These are 2 different programs, with different protocals .
The fact there is no response from phone when in fastboot is a sign that pc drivers are not correctly installed, or the fastboot program needs to be updated.
mrmazak said:
No, sorry that is wrong.
ADB permission is not needed for fastboot. These are 2 different programs, with different protocals .
The fact there is no response from phone when in fastboot is a sign that pc drivers are not correctly installed, or the fastboot program needs to be updated.
Click to expand...
Click to collapse
You are absolutely right. Thanks for clarifying the issue. Spot on !!
Developer option shows bootloader as locked but after reboot bootloader shows as unlocked . twrp working but Fastboot not working so I'm afraid I might brick my device as I can't flash fastboot rom. Please help.
I wanna know what you mean by 'Fastboot not working'. Does it mean you can't boot into fastboot mode, or does it mean you can't access fastboot commands on your pc?
Also i wanna know, while unlocking Bootloader. Did you used commands
Code:
fastboot oem unlock
and
Code:
fastboot oem unlock_critical
?
The device does boot into fastboot but doesnt respond to any fastboot command
It doesn't even show up on typing fastboot device
I unlocked the bootloader using miunlocktool
But the device doesnt even show up in the tool
pythonner said:
The device does boot into fastboot but doesnt respond to any fastboot command
It doesn't even show up on typing fastboot device
I unlocked the bootloader using miunlocktool
But the device doesnt even show up in the tool
Click to expand...
Click to collapse
If it's not responding to fastboot commands I worry that if correct drivers are installed on your pc.
Plug-in ur device while in fastboot mode to your pc.
Open Mi Unlock tool(this works very first time, you don't even have to install this tool). There's a setting icon on top right corner.
A dialogue box will appear, displaying to install drivers.
Install 'em. It will ask you to remove and plug-in your device again.
Now, download the platform tools file.
Open cmd in the platform tools folder.
Now try using fastboot commands.
It's same for me.
You can ignore that safely.
eleven.co said:
If it's not responding to fastboot commands I worry that if correct drivers are installed on your pc.
Plug-in ur device while in fastboot mode to your pc.
Open Mi Unlock tool(this works very first time, you don't even have to install this tool). There's a setting icon on top right corner.
A dialogue box will appear, displaying to install drivers.
Install 'em. It will ask you to remove and plug-in your device again.
Now, download the platform tools file.
Open cmd in the platform tools folder.
Now try using fastboot commands.
Click to expand...
Click to collapse
I updated the usb driver but unlock tool can't even detect the devices and when I type fastboot devices in platform tools the device is also not detected
I'm afraid of installing custom roms because if I brick it I will not be able to even flash the official fastboot rom
VD171 said:
It's same for me.
You can ignore that safely.
Click to expand...
Click to collapse
Actually when I type fastboot devices in platform tools the device is not even detected. So I'm afraid that if I flash custom rom and brick it I will be unable to flash even the official fastboot rom.
pythonner said:
I updated the usb driver but unlock tool can't even detect the devices and when I type fastboot devices in platform tools the device is also not detected
I'm afraid of installing custom roms because if I brick it I will not be able to even flash the official fastboot rom
Click to expand...
Click to collapse
Boot your phone, connect through USB to PC. Now check in Windows File Explorer. Is your device visible there?
If not, open Device Manager and you'll find something with the name adb (You can go through this guide). In my case it was under Acer. Just update those drivers manually and see if your device is visible now.
eleven.co said:
Boot your phone, connect through USB to PC. Now check in Windows File Explorer. Is your device visible there?
If not, open Device Manager and you'll find something with the name adb (You can go through this guide). In my case it was under Acer. Just update those drivers manually and see if your device is visible now.
Click to expand...
Click to collapse
the devices shows up in file explorer and device manger when its turned on but after putting in fastboot mode the platform tools cant detect the device
pythonner said:
the devices shows up in file explorer and device manger when its turned on but after putting in fastboot mode the platform tools cant detect the device
Click to expand...
Click to collapse
This is sad. Try fiddling around. I am unable to identify what could be the possible reason behind non-detection of device over platform tools as there are many. Maybe go through this article. It has various methods to fix non - detection of device.
eleven.co said:
This is sad. Try fiddling around. I am unable to identify what could be the possible reason behind non-detection of device over platform tools as there are many. Maybe go through this article. It has various methods to fix non - detection of device.
Click to expand...
Click to collapse
Now developer options is showing as unlocked and adb is also working good
but fastboot is still not working when I type fastboot devices It returns nothing
eleven.co said:
This is sad. Try fiddling around. I am unable to identify what could be the possible reason behind non-detection of device over platform tools as there are many. Maybe go through this article. It has various methods to fix non - detection of device.
Click to expand...
Click to collapse
What could be possible explanation to adb working but fastboot not working. The usb cable is tight and bootloader is unlocked even in developer options
eleven.co said:
This is sad. Try fiddling around. I am unable to identify what could be the possible reason behind non-detection of device over platform tools as there are many. Maybe go through this article. It has various methods to fix non - detection of device.
Click to expand...
Click to collapse
I just realised that I flashed twrp using the root app flashify. Could that be the reason for root not working
VD171 said:
It's same for me.
You can ignore that safely.
Click to expand...
Click to collapse
If you're rooted and have magisk hide enabled, it's normal, Magisk spoofs locked bootloader to pass safetynet in MIUI