Database Info

Tried to unroot, now Pixel won't go past 'Device is corrupt' screen

Hi all,
I tried to unroot and relock the bootloader for my Pixel through SuperSU (settings, unroot, restore stock recovery etc). However, now when I turn the phone on it gets to the 'your device is corrupt' screen (https://lh3.googleusercontent.com/-Avr7yNnXOpY/VjGcdDK9iHI/AAAAAAAGCf0/LLwjhkLX1yk/w666-h2518/15+-+1) and then just switches off. Is there anything I can do? Bootloader is currently locked (EE Pixel)
{
"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"
}

Just want to make sure I understand you, you said you re-locked your bootloader?

kornesque said:
Just want to make sure I understand you, you said you re-locked your bootloader?
Click to expand...
Click to collapse
Yup.
So did the SuperSU thing. Then went into fastboot to relock. That seemed successful so I tried to restart and this happened..
And I can't get into recovery >.<

My ability to post is intermittent, don't know what's up but if this doesn't get through then...well, i guess you won't know.
Did you take any 7.1.1 updates or sideload anything? Do you have a VZW variant? And can you get to the bootloader to issue fastboot/adb commands? Hopefully you're not hosed, we'll see what we can do and hopefully a guru shows up here too.

Try to unlock the bootloader again. If you can. Download the full system image from Google and flash that. Then re-lock it.
Sent from my Pixel using Tapatalk

brpqzme said:
Yup.
So did the SuperSU thing. Then went into fastboot to relock. That seemed successful so I tried to restart and this happened..
And I can't get into recovery >.<
Click to expand...
Click to collapse
What happens when you boot to recovery?

bobby janow said:
What happens when you boot to recovery?
Click to expand...
Click to collapse
It boots into the bootloader. Then I choose the RECOVERY option and the 'YOUR DEVICE IS CORRUPT' screen shows up again. It stays on that for a few seconds then the device turns off, exactly like how it does when I try to boot into the phone normally. So I can't get into recovery either..
kornesque said:
My ability to post is intermittent, don't know what's up but if this doesn't get through then...well, i guess you won't know.
Did you take any 7.1.1 updates or sideload anything? Do you have a VZW variant? And can you get to the bootloader to issue fastboot/adb commands? Hopefully you're not hosed, we'll see what we can do and hopefully a guru shows up here too.
Click to expand...
Click to collapse
So this is an EE variant (similar to the VZW one, but UK-based). I can get into the bootloader (holding down power+ vol down) but ADB DEVICES doesn't list anything. I didn't update it to 7.1.1. I used SuperSU to UNROOT, clicked YES when it asked to restore stock recovery and image. Booted into fastboot and relocked bootloader.
Though if I use the SkipSoft toolkit it does detect it in Fastboot mode

Electroz said:
Try to unlock the bootloader again. If you can. Download the full system image from Google and flash that. Then re-lock it.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Can't unlock without dePixel8, and can't use that unless I boot into Android itself so that I can push the files..

brpqzme said:
Can't unlock without dePixel8, and can't use that unless I boot into Android itself so that I can push the files..
Click to expand...
Click to collapse
Have you tried a regular fastboot unlock?
Sent from my Pixel using Tapatalk

Electroz said:
Have you tried a regular fastboot unlock?
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Yup, tried that through SkipSoft (because normal ADB doesn't detect my phone so using SkipSoft). It says 'failed' when I tried

No idea what skipsoft is. I mean did you load up a command prompt and run the "fastboot OEM unlock" command. This has nothing to do with ADB. You need to be in fastboot mode to run it. To make sure your device shows, run fastboot devices. Again, adb will not help with the bootloader locked.
Sent from my Pixel using Tapatalk

Electroz said:
No idea what skipsoft is. I mean did you load up a command prompt and run the "fastboot OEM unlock" command. This has nothing to do with ADB. You need to be in fastboot mode to run it. To make sure your device shows, run fastboot devices. Again, adb will not help with the bootloader locked.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Ah I see. OK so yes, 'FASTBOOT DEVICES" shows my device. FASTBOOT OEM UNLOCK fails though. Which I guess I expected, because it's an EE/VZW locked phone..

brpqzme said:
Ah I see. OK so yes, 'FASTBOOT DEVICES" shows my device. FASTBOOT OEM UNLOCK fails though. Which I guess I expected, because it's an EE/VZW locked phone..
Click to expand...
Click to collapse
OK. So even in recovery mode you can't get adb devices to show the phone? It sounds like you're out of luck.
Sent from my Pixel using Tapatalk

Electroz said:
OK. So even in recovery mode you can't get adb devices to show the phone? It sounds like you're out of luck.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
UPDATE: OK so if I type "Fastboot continue" and it boots into a fresh copy on Android.. however, each time I restart it from there, it shows the red 'CORRUPT' screen and turns off. So then I used dePixel8 after booting into the 'fresh' Android to unlock the bootloader again. If anyone else is stuck - FASTBOOT CONTINUE boots into a 'fresh' copy of Android that's on a different partition, from what I understand (could be wrong).
This seems to have worked in the sense that I know have an unlocked bootloader and it boots into the OS again and into recovery!
The odd thing is TWRP is still the main recovery, even though SuperSU was supposed to have removed it. Will try to manually flash stock recovery from an image now.
The main reason I need to relock my bootloader is to get Android Pay working.
Thanks for the help guys!

brpqzme said:
UPDATE: OK so if I type "Fastboot continue" and it boots into a fresh copy on Android.. however, each time I restart it from there, it shows the red 'CORRUPT' screen and turns off. So then I used dePixel8 after booting into the 'fresh' Android to unlock the bootloader again. If anyone else is stuck - FASTBOOT CONTINUE boots into a 'fresh' copy of Android that's on a different partition, from what I understand (could be wrong).
This seems to have worked in the sense that I know have an unlocked bootloader and it boots into the OS again and into recovery!
The odd thing is TWRP is still the main recovery, even though SuperSU was supposed to have removed it. Will try to manually flash stock recovery from an image now.
The main reason I need to relock my bootloader is to get Android Pay working.
Thanks for the help guys!
Click to expand...
Click to collapse
If you want to go back to stock and relock the bootloader, flash the entire system image from google first. Don't only do half of it or you'll end up in the same spot. Nice find on the fastboot Continue though!
Sent from my Pixel using Tapatalk

Ah thanks for the info. So best option - flash the image direct from Google, then relock the bootloader?
Electroz said:
If you want to go back to stock and relock the bootloader, flash the entire system image from google first. Don't only do half of it or you'll end up in the same spot. Nice find on the fastboot Continue though!
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse

brpqzme said:
Ah thanks for the info. So best option - flash the image direct from Google, then relock the bootloader?
Click to expand...
Click to collapse
Yes sir
Sent from my Pixel using Tapatalk
---------- Post added at 07:14 PM ---------- Previous post was at 07:13 PM ----------
brpqzme said:
Ah thanks for the info. So best option - flash the image direct from Google, then relock the bootloader?
Click to expand...
Click to collapse
But go with the 7.1.0 image just in case. So you can depixel8 again if need be.
Sent from my Pixel using Tapatalk

brpqzme said:
UPDATE: OK so if I type "Fastboot continue" and it boots into a fresh copy on Android.. however, each time I restart it from there, it shows the red 'CORRUPT' screen and turns off. So then I used dePixel8 after booting into the 'fresh' Android to unlock the bootloader again. If anyone else is stuck - FASTBOOT CONTINUE boots into a 'fresh' copy of Android that's on a different partition, from what I understand (could be wrong).
This seems to have worked in the sense that I know have an unlocked bootloader and it boots into the OS again and into recovery!
The odd thing is TWRP is still the main recovery, even though SuperSU was supposed to have removed it. Will try to manually flash stock recovery from an image now.
The main reason I need to relock my bootloader is to get Android Pay working.
Thanks for the help guys!
Click to expand...
Click to collapse
If you truly are still unlocked, I would use Google's flashall bat file so you reflash both partitions correctly.
And I really wouldn't relock it. You got lucky, it would seem that your attempt to relock failed. If it had worked you would have been out of luck.
Without any mods other than unlocked I am pretty sure Android pay works fine.
Did you change anything else, like root or maybe system mods?
Edit. I'm wrong, unlocked trips safteynet. So you flash a kernel that fixes that. Franco does, I think Elemental does and this one does:
http://forum.xda-developers.com/pix...l-stock-kernel-safetynet-patch-t3516596/page5

Yea I don't get people. What's the point of relocking..

aholeinthewor1d said:
Yea I don't get people. What's the point of relocking..
Click to expand...
Click to collapse
You're assuming everybody stays up all night and day following these forums like you and me. We're the pathetic ones. LOL.

(Im sorry) Cannot for the life of me get my phone up and running again.

I've tried like heck to find the answer before asking but to no avail. I'll keep it short:
- Phone will not boot, comes up to blue Honor boot screen, shuts off and immediately comes back on, off, on, off
- Can get to Fastboot (blurry image attached)
{
"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"
}
- device is locked, usb debugging is off (was attempting return to stock)
- CMD shows fastboot device but won't perform any flash or unlock commands (failed: remote command not allowed)
- have yet to get to recovery or erecovery
Is this trick in the button combos? I've tried them all repeatedly, is there a single instant I have to hit them/let them go?
Sorry for yet another help me thread, but I'm lost.

Which model do u have?
Depending on which model u have u can try using this guide:
https://forum.xda-developers.com/honor-8/how-to/restoring-relocking-bricked-frd-l04-t3666360
Sent from my Honor 8 using XDA Labs

ayush rao said:
Which model do u have?
Depending on which model u have u can try using this guide:
https://forum.xda-developers.com/honor-8/how-to/restoring-relocking-bricked-frd-l04-t3666360
Click to expand...
Click to collapse
Fr04. I'll give the guide a shot but I don't think I can flash anything via fastboot. I already said screw it and bought a moto so I'm in no hurry. Maybe this weekend. Thank you for the guidance .

Have tried the dload method? Flash full firmware via dload

The dload might work but idk if it will cus the phone is in a kernal panic it looks like. :crying:
---------- Post added at 06:52 AM ---------- Previous post was at 06:50 AM ----------
Did you have TWRP installed as your recovery?

I did but removed it while attempting to get back to stock.

dolorousbrann said:
I did but removed it while attempting to get back to stock.
Click to expand...
Click to collapse
You can reinstall

shashank1320 said:
You can reinstall
Click to expand...
Click to collapse
Given the description in my original post I don't know how to do that, sorry.

dolorousbrann said:
Given the description in my original post I don't know how to do that, sorry.
Click to expand...
Click to collapse
Download the full firmware for your model.
Extract the zip. Copy the contents (with update.app) to dload folder on sd card.
Power off the phone( it is already off i think)
Press vol up+ vol down+power key
It should start flashing the stock firmware

shashank1320 said:
Download the full firmware for your model.
Extract the zip. Copy the contents (with update.app) to dload folder on sd card.
Power off the phone( it is already off i think)
Press vol up+ vol down+power key
It should start flashing the stock firmware
Click to expand...
Click to collapse
Is done that a few times at never had it work. Either one got the wrong firmware (though it came straight from the Honor site) or in doing wondering wrong. I'll give it another go this weekend and try it back. Thanks

dolorousbrann said:
Is done that a few times at never had it work. Either one got the wrong firmware (though it came straight from the Honor site) or in doing wondering wrong. I'll give it another go this weekend and try it back. Thanks
Click to expand...
Click to collapse
Good luck. Hope for the best

Not that anyone is still here but the dload method will not work. The phone won't leave the boot loop and go into recovery. Tried every button combo and timing I could to no avail. I have given up.

You should be able to remotely factory reset it through Google Find My Device

Try DC Unlocker I had this issue and it worked

Rommco05 said:
Which is your problem. You can boot to fastboot and PC recognize your phone?
Click to expand...
Click to collapse
I can boot into fastboot and it says "relocked". At Command Prompt "fastboot devices" shows the phone but any command (flash, update, oem unlock) all give me an error of "remote command not allowed".

Rommco05 said:
Try reinstall HiSuite and again connect phone to pC
Click to expand...
Click to collapse
HiSuite doesn't recognize that a device is connected.

Rommco05 said:
Try reinstall HiSuite, this will reinstall the drivers
Click to expand...
Click to collapse
Ok, ill try it tomorrow. Thank you.

[UPDATED][GUIDE] UNLOCK/RELOCK BOOTLOADER UNOFFICIALLY FOR ZenFone 3

Make sure you’ve backed up all of your IMPORTANT DATA before unlocking/relocking bootloader because this process WILL DELETE ALL OF YOUR IMPORTANT DATA !
I am not responsible for bricked devices and dead SD cards. YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
This process will not void the device warranty & you will get OTAs
First and foremost, please install ZenFone 3 Drivers via Device Manager (Download drivers on ASUS Support Website)
1) Download the Factory RAW ROM here:
ZE520KL:
ZE552KL:
2) Download ASUS Flash Tool here:
3) Flash the firmware via ASUS Flash Tool by entering FASTBOOT MODE (Power Button + Volume Up) & DO NOT WIPE DATA!
Note: This firmware can only boot into FASTBOOT Mode. So, don’t panic
Note: If you flash RAW firmware via ASUS Flash Tool and received an error (FRP request error), just IGNORE the error.
4) Download Bootloader Kit for ZenFone 3 here:
5) Enter FASTBOOT mode (Power Off + Volume Up)
UNLOCKING​
6) Unzip the files and click on Install adb-setup-1.4.3.exe (You can find this in Bootloader Kit)
Hold Shift and Right Click on any area in the folder (click on ”Open Powershell window/Open Command Window)
Now copy and paste this: fastboot devices
If it shows serial number of your ZenFone 3, you are good to go
Now copy and paste this: fastboot oem unlock
After that, copy and paste this: fastboot reboot bootloader
Congratulations, your device has been unlocked unofficially. (You can see the "Device State" on FASTBOOT splash screen)
RELOCKING​
6) Unzip the files and click on Install adb-setup-1.4.3.exe (You can find this in Bootloader Toolkit)
Hold Shift and Right Click on any area in the folder (click on ”Open Powershell window/Open Command Window)
Now copy and paste this: fastboot devices
If it shows serial number of your ZenFone 3, you are good to go
Now copy and paste this: fastboot oem lock
After that, copy and paste this: fastboot reboot bootloader
Congratulations, your device has been locked (You can see the "Device State" on FASTBOOT splash screen)
P.S: If you unlocked officially and you want to relock your bootloader, OTA does not work because your Serial Number has been recorded by ASUS.
7) After that, download the stock Oreo RAW ROM here and flash it via ASUS Flash Tool (FASTBOOT Mode) (DO NOT WIPE DATA):
ZE520KL:
ZE552KL:
If anything, contact me via Telegram
MOD EDIT: LINK REMOVED
The distribution of social media links is no longer allowed on XDA. Please refer to the thread linked below:
Telegram and Whatsapp Channels - Going Forward
Note: If you flash RAW firmware via ASUS Flash Tool and received an error (FRP request error), just IGNORE the error.
Note: If it asks for PIN after booting up, just wipe data & cache via Recovery Mode (Power Button + Volume Down).

How to delete the start message in Zenfone 3 ZE552KL after officially unlocking Bootloader?

AnAn. said:
How to delete the start message in Zenfone 3 ZE552KL after officially unlocking Bootloader?
Click to expand...
Click to collapse
I think it's impossible

AnAn. said:
How to delete the start message in Zenfone 3 ZE552KL after officially unlocking Bootloader?
Click to expand...
Click to collapse
To remove it, simply relock the bootloader.

Ok so this time it worked ! Thanks @ZenFone_3
Now I'm on the latest oreo update (1801) with bootloader unlocked.
But no twrp yet. For some reason the flashing process of the twrp img finishes, but it is still the stock recovery that boots. I tried multiple times and downloaded the twrp img again but no luck. I'll try to figure that out.

If I do this unlocking method I'm gona keep my warranty if I have any issue and need to relock to send to the Asus? Or It can be detected?

ehbm said:
If I do this unlocking method I'm gona keep my warranty if I have any issue and need to relock to send to the Asus? Or It can be detected?
Click to expand...
Click to collapse
Just relock and send it to service centre. ASUS won't know

ZenFone_3 said:
Just relock and send it to service centre. ASUS won't know
Click to expand...
Click to collapse
Thanks

hi i get this error
{
"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"
}
can open file gzya etc. and wont continue to flash

gio14 said:
can open file gzya etc. and wont continue to flash
Click to expand...
Click to collapse
Just ignore the error.

do i need to reflash the firmware after relocking bootloader ? now im on oreo and using stock recovery

kuranzi said:
do i need to reflash the firmware after relocking bootloader ? now im on oreo and using stock recovery
Click to expand...
Click to collapse
Read my main post properly. Yes, you need to flash Factory RAW to relock bootloader. After relocking, flash Oreo RAW to return back to stock ROM.

ZenFone_3 said:
Read my main post properly. Yes, you need to flash Factory RAW to relock bootloader. After relocking, flash Oreo RAW to return back to stock ROM.
Click to expand...
Click to collapse
Just little confused here, do i need start from step 1 or i just skip to step 6 ? Cause i only need relocking...

kuranzi said:
Just little confused here, do i need start from step 1 or i just skip to step 6 ? Cause i only need relocking...
Click to expand...
Click to collapse
Whole Steps ( Skip the unlocking part)

i have doing untill step 3. now im going to step 6 for locking bootloader, but adb didnt find my devices, what should i do ?

kuranzi said:
i have doing untill step 3. now im going to step 6 for locking bootloader, but adc didnt find my devices, what should i do ?
Click to expand...
Click to collapse
Install drivers via Device Manager (Drivers are in the Bootloader Kit Folder)

Contact me via Telegram.
MOD EDIT: LINK REMOVED
The distribution of social media links is no longer allowed on XDA. Please refer to the thread linked below:
Telegram and Whatsapp Channels - Going Forward

ZenFone_3 said:
Contact me via Telegram.
MOD EDIT: LINK REMOVED
The distribution of social media links is no longer allowed on XDA. Please refer to the thread linked below:
Telegram and Whatsapp Channels - Going Forward
Click to expand...
Click to collapse
icant use telgram it need verification sent to my phone, i just have 1 phone.... what should i do now ? i try adb on recovery and it detect my phone, but in fastboot it not detect anymore

kuranzi said:
icant use telgram it need verification sent to my phone, i just have 1 phone.... what should i do now ? i try adb on recovery and it detect my phone, but in fastboot it not detect anymore
Click to expand...
Click to collapse
Do you have TeamViewer? If not, install it and PM me

With this method the Warranty is not void?

[HELP] POCO M3 system has been destroyed

Hi guys, I need a little help, what happens is that I went to the settings to unlock the bootloader and then proceeded to flash a rom, but after this I got the error "system has been destroyed" Does it mean that to fix it I need to wait for my bootloader to unlock? I forgot that I had to wait a week and I'm not sure what this is because of not waiting or another error, I would also like to know if after time I can fix it since using the MI unlock tool from xiaomi tells me that wait for the time and use the my flash tool to install the stock rom it drops the error "erase is not allowed in lock state"
(EDIT) finish the timer for the unlock bootloader, and after that i just flash a stock rom, thanks for everyone who support me

Re-flash Stock ROM

Tell the problem clearly what issues you are facing??

aaashzz said:
Tell the problem clearly what issues you are facing??
Click to expand...
Click to collapse
This is the problem, I wanted to go back to a previous version of MIUI, so I added my account to unlock the bootloader and immediately used the XiaomiToolV2 tool to flash this ROM, everything seemed to go well until the end of the device I started with the error "Systen has been destroyed "I read that flashing the stock ROM would solve it but when doing it in the MIflashtool tool it would give me the error" erase is not allowed in lock state "
{
"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"
}

Syxnetrax said:
This is the problem, I wanted to go back to a previous version of MIUI, so I added my account to unlock the bootloader and immediately used the XiaomiToolV2 tool to flash this ROM, everything seemed to go well until the end of the device I started with the error "Systen has been destroyed "I read that flashing the stock ROM would solve it but when doing it in the MIflashtool tool it would give me the error" erase is not allowed in lock state "
View attachment 5198249
Click to expand...
Click to collapse
Yes tha'ts right you can not flash rom with a locked boot loader. there is only way to recover your phone is via edl mode. Flashing the rom via edl mode requires an edl account. The edl account is not available for everyone it's only available for the developer's and services center's. So it's better you take your phone to a service center. Because this problem most probably can't solved by user because everyone May not have a edl account authorised by xiaomi. And the with miflash tool you cannot unlock your phone there is an entirely different tool for unlocking the bootloader "miunlock tool" they are entirely different tools the miflash is only for flash mi rom and for lock your phone. And the other side the miunlock tool is for unlocking the bootloader!

aaashzz said:
Yes tha'ts right you can not flash os with a locked boot loader. there is only way to recover your phone is via edl mode. Flashing the rom via edl mode requires an edl account. The edl account is not available for everyone it's only available for the developer's and services center's. So it's better you take your phone to a service center. Because this problem most probably can't solved by user because everyone May not have a edl account authorised by xiaomi.
Click to expand...
Click to collapse
But the unlocking has already started, even the xiaomi tool tells me that I have 41 hours left until it is unlocked, according to me after that I can repair it myself by flashing the ROM, or am I wrong?

Syxnetrax said:
But the unlocking has already started, even the xiaomi tool tells me that I have 41 hours left until it is unlocked, according to me after that I can repair it myself by flashing the ROM, or am I wrong?
Click to expand...
Click to collapse
Is the bootloader is unlocked, do you able boot the phone into fastboot mode?

aaashzz said:
Is the bootloader is unlocked, do you able boot the phone into fastboot mode?
Click to expand...
Click to collapse
i can access the fastboot, and the unlock will finish in the time mencioned

Syxnetrax said:
i can access the fastboot, and the unlock will finish in the time mencioned
Click to expand...
Click to collapse
To check whether Fastboot is really dealing with phone's bootloader, you run
Code:
fastboot devices
If you don't see fastboot in second line of command's output phone isn't booted into bootloader mode
To check whether phone's bootloader is unlocked, you run
Code:
fastboot getvar secure
If YES is returned then bootloader isn't unlocked.

jwoegerbauer said:
To check whether Fastboot is really dealing with phone's bootloader, you run
Code:
fastboot devices
If you don't see fastboot in second line of command's output phone isn't booted into bootloader mode
To check whether phone's bootloader is unlocked, you run
Code:
fastboot getvar secure
If YES is returned then bootloader isn't unlocked.
Click to expand...
Click to collapse
bootloader is working fine, i get a yes because i need to wait 40 hours more for the bootloader to unlock, my understanding is that after the time i can flash the stock rom, can anyone confirm?

Syxnetrax said:
bootloader is working fine, i get a yes because i need to wait 40 hours more for the bootloader to unlock, my understanding is that after the time i can flash the stock rom, can anyone confirm?
Click to expand...
Click to collapse
To flash a phone's Stock ROM it's not required that phone's bootloader is unlocked.
You flash phone's Stock ROM as shown next
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>

flashing stock rom does not require bootloader to be unlocked.
just flash the rom using adb or fastboot
i will recommend using fastboot because it's reliable but some time it requires unlocked bootloader so just try fastboot after adb has failed.

jwoegerbauer said:
To flash a phone's Stock ROM it's not required that phone's bootloader is unlocked.
You flash phone's Stock ROM as shown next
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
Click to expand...
Click to collapse
adb reboot sideload starts a bootloop of the same screen "ths system has been destroyed"

bro, just go to recovery and type adb devices if any device is listed then give command adb sideload <drag file for its location> and press enter if it work tell me

Bhanu8082 said:
bro, just go to recovery and type adb devices if any device is listed then give command adb sideload <drag file for its location> and press enter if it work tell me
Click to expand...
Click to collapse
this happend, idk if im doing something wrong

Syxnetrax said:
View attachment 5198725
this happend, idk if im doing something wrong
Click to expand...
Click to collapse
Rename Stock ROM's .ZIP-fie to stock-rom.zip,, then it it should work

jwoegerbauer said:
Rename Stock ROM's .ZIP-fie to stock-rom.zip,, then it it should work
Click to expand...
Click to collapse
after this the same error repeats and start to bootloop with the system has been destroyed screen

bro problem might be your version of adb just use latest version or try version
Android Debug Bridge version 1.0.32
version 1.0.32 is reliable for me as it works

Syxnetrax said:
after this the same error repeats and start to bootloop with the system has been destroyed screen
Click to expand...
Click to collapse
Fix for "The system has been destroyed" Redmi note 8/8T
Fix for "The system has been destroyed" Redmi note 8/8T This will only work for unlocked bootloader...this guide will help you recover from the System has been destroyed when trying to install custom rom or recovery or maybe some other actions...
forum.xda-developers.com

Syxnetrax said:
But the unlocking has already started, even the xiaomi tool tells me that I have 41 hours left until it is unlocked, according to me after that I can repair it myself by flashing the ROM, or am I wrong?
Click to expand...
Click to collapse
Hey did you fixed the phone ??

How To Guide Lock+Unlock Bootloader - Xiaoxin Pad Pro 2021 [TB-J716F]

How To Lock and Unlock Bootloader - Xioaxin Pad Pro 2021 - TB-J716F
Since I found out that the Tablet supports Project Treble I'm trying to get a GSI-ROM running on it.
Currently with many trial and error I got LiR-ROM to boot.
The first step is to unlock the Bootloader so I thought I will share the process here.
Your data will be deleted while unlocking, try it at your own risk.
Unlock Bootloader manually
Requirement: PC with ADB Fastboot
1. Go to Settings -> System -> About Phone, tab on it until developer settings are enabled.
2. Go to Developer Settings and enable "USB Debugging" and "OEM Unlocking".
3. Open Console and enter "adb devices". Allow USB-Debugging if tablets asks.
4. Enter command "adb reboot bootloader".
5. Write down the serial number shown on the bootloader screen
You can either get the unlock image via this link "http://cdn.zui.lenovomm.com/developer/tabletboot/[your sn number]/sn.img" or via the webseite
5. Go to the ZUI Unlock Website and request the unlock image
{
"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"
}
6. You should get a mail where you can download a file called "sn.img".
7. Flash the image with fastboot "fastboot flash unlock sn.img"
8. Enter command "fastboot oem unlock-go", bootloader will unlock now.
9. Restart with "fastboot reboot".
Done, your bootloader should be unlocked now.
Lock and Unlock Bootloader with Batchscript
I recently found a batch script for lenovo devices in an chinese forum and translated it.
It's easy and convenient to use. For unlocking you still need the sn.img from the ZUI Unlock Website.
Download BatchScript​

Thanks a lot for your contribution! Mine was unlocked when I received it but it's good to see some guides here.

What is the opposite process, to close the bootloader? Does Widevine L1 recover after closing the bootloader? In the case of doing so, can the bootloader be opened again?

@sakun-ice Sorry, I can't tell you that, sind I haven't tried it now. But I think it should be possible.
Currently I'm trying to get a Custom ROM running, if it doesn't work, I will try to install Stock ROM and lock bootloader again. If it happens, I will post it here.

Tropaion said:
@sakun-ice Sorry, I can't tell you that, sind I haven't tried it now. But I think it should be possible.
Currently I'm trying to get a Custom ROM running, if it doesn't work, I will try to install Stock ROM and lock bootloader again. If it happens, I will post it here.
Click to expand...
Click to collapse
Thank you very much, I hope you can install a custom rom and this tablet will not be forgotten, since it is one of the most powerful compact tablets.

@sakun-ice I got LineageOS to run on it today, but it still has 2-3 bugs.

Helloi received one unlocked with a globaoe fw without ota's and i flashed the cn one and took the boot.ipg and patched it with pagisk for root and when flashing it via fastboot the device reboots to fastboot everytipe 1nd had to reflash the fw via edl , i did flashed vbmeta img with the known command o disable verification but no success same thing again. Can anyone plz tell me how to root that crap , it was intended to root use only and took over xiaomi pad pro just because the xiaomi needs 7 days of waiting before unlocking , plz help guys .thx so much i can buy a couple beers for the helper

I'm able to flash back to China stock rom but i can't lock the bootloader.
i have placed the sn.img in both the batchscript folder and platform tools
Tried the batch script :
"
Please select your device status:
1. Fully booted
2. Fastboot mode
Status: 2
Start locking bootloader, don't disconnect device from PC!
FAILED (remote: Command not supported in default implementation)
Finished. Total time: 0.016s
FAILED (remote: Unrecognized command flashing lock)
Finished. Total time: -0.000s
If prompt says "OKAY", locking was successfull.
Use the volume keys to select "LOCK BOOTLOADER", press power key to confirm.
Done!
Press any key to continue . . .
"
Powershell :
"
PS C:\Users\weeteck\Downloads\platform-tools_r31.0.3-windows\platform-tools> ./fastboot flash lock sn.img
Sending 'lock' (5 KB) OKAY [ 0.000s]
Writing 'lock' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
"

@zeroflame15 Did install the driver correctly? For locking you don't need the sn.img, only for unlocking. And did you use the LockBootloader Script?

hmm..i'm not sure if i install the driver correctly. what should be shown in device manager? i did follow PHRS guide and installed the ADB driver but there is this !Android under Other Devices.
Any other driver that i need to install?
And should i be in bootloader mode or fastboot mode to run the command? I run the command at fastboot moder i will get the error above. If i run at bootloader mode will stuckedd at <waiting for device>

@zeroflame15 You have to be in bootloader mode. <waiting for device> is propably the driver.

Tropaion said:
@zeroflame15 You have to be in bootloader mode. <waiting for device> is propably the driver.
Click to expand...
Click to collapse
i have installed all the ADB driver mentioned in this section. Is there a lenovo driver? or any settings within the tablet need to be set to?
thanks for the help

zeroflame15 said:
i have installed all the ADB driver mentioned in this section. Is there a lenovo driver? or any settings within the tablet need to be set to?
thanks for the help
Click to expand...
Click to collapse
Try to connecting in another usb port with other usb cable.

zeroflame15 said:
i have installed all the ADB driver mentioned in this section. Is there a lenovo driver? or any settings within the tablet need to be set to?
thanks for the help
Click to expand...
Click to collapse
Check out this post:
Post in thread '[Solved] Re-locking bootloader - no fastboot commands working' https://forum.xda-developers.com/t/...stboot-commands-working.4330019/post-85755663
It can be a bit tricky to get the commands working because it's not always clear if you need to be in fastboot or bootloader.
This worked for me:
Reboot to bootloader by entering "adb reboot bootloader"
After that try "fastboot flashing lock"

Thanks @zxcv88
After installing the lenovo USB driver, the !Android in Other devices was updated.
LenovoUsbDriver_v1.1.34
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Boot into bootloader mode and "fastboot flashing lock" runs without any issue
Appreciate all for the advise and help! Appreciate ~

zeroflame15 said:
Thanks @zxcv88
After installing the lenovo USB driver, the !Android in Other devices was updated.
LenovoUsbDriver_v1.1.34
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Boot into bootloader mode and "fastboot flashing lock" runs without any issue
Appreciate all for the advise and help! Appreciate ~
Click to expand...
Click to collapse
sorry zeroflame15..... 2 question.... from (fake) global to china stock :
1 flash china
2 lock bootloader
right?
and most important.....lock bootloader is a "must" or is a choice?
if i dont lock bootloader i haven not ota and L1 ? im interested only in OTA updates....not l1 widevine...
thanks

fazioso said:
sorry zeroflame15..... 2 question.... from (fake) global to china stock :
1 flash china
2 lock bootloader
right?
and most important.....lock bootloader is a "must" or is a choice?
if i dont lock bootloader i haven not ota and L1 ? im interested only in OTA updates....not l1 widevine...
thanks
Click to expand...
Click to collapse
Sort of yes.
Initially after flash to stock china rom, i was able to OTA. But subsequent check for updates will get error saying devices is rooted.
After locked bootloader, tried OTA again and indeed there is another new updates.
Saw some chinese video for those who wanted the rooted status and also to perform OTA updates, they are using magdisk to hide the root.

zeroflame15 said:
Sort of yes.
Initially after flash to stock china rom, i was able to OTA. But subsequent check for updates will get error saying devices is rooted.
After locked bootloader, tried OTA again and indeed there is another new updates.
Click to expand...
Click to collapse
thanks!
its seems most difficult to lock/unlock bootloader that flash rom.....
but you need ZUI Unlock Website also for lock? cause seems need only for unlock...right?

No need for lock. Like what others have mentioned. Just a single line command and it works as long you got the right drivers installed.

Tropaion said:
How To Lock and Unlock Bootloader - Xioaxin Pad Pro 2021 - TB-J716F
5. Go to the ZUI Unlock Website and request the unlock image
View attachment 5432885
6. You should get a mail where you can download a file called "sn.img".​
Click to expand...
Click to collapse
my friend ....i have a unlocked bootloader ,cause for now i have the fake global....want to change in china stock....
but i ask anyway to the zui unlock website the sn.img in case i need in future.....
just a question.... after many hours or days i will receive the sn.img file? pass 10 minutes and nothing yet