Database Info

Nexus 5 stuck in bootloop with no access to E:

My phone (2nd nexus5, not my daily driver nexus) is stuck in a bootloop (stuck at the booting animation) after updating via the OTA updtes, never rooted or touched any setting in the dev options in the setting menu.
The phone stays like that for hours, doesn't even reboot on its own, just keeps playing the bootanimation for hours and hours until the battery dies.
I have access to the bootloader, and default(stock) recovery.
tried oem unlock, but it doesn't work, and shows no errors.
Tried hard reset from the stock recovery and got numerous E: Failed to mount ..... errors. (check attached photo)
All attempts to wipe or format anypart of the phone fail with the same error,
ADB side load of a custom recovery ( TWRP ) also failed with the same error.
Please help me out, data loss is not an issue as i had no imp data and used it mainly for calls and emails.
{
"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"
}

Try flashing twrp.
fastboot flash recovery (ur recovery name).img
Then unmount system from advance and flash a custom rom

pranavmali said:
Try flashing twrp.
fastboot flash recovery (ur recovery name).img
Then unmount system from advance and flash a custom rom
Click to expand...
Click to collapse
It shows an error
FAILED (remote: not supported in locked device)
Like I said, oem unlock doesn't work.
As soon as i give the oem unlock command, it will ask for conformation, after hitting yes,
it will even show LOCK STATE - unlocked.
But as soon as the phone reboots or re-enters bootloader, the phone is back to a locked bootloader.
On unlocking bootloader, flashing TWRP via fastboot, when i enter recovery mode, i am still taken back to the stock recovery.

Try Wug fresh's tool kit! To unlock bootloader

Does the give give an error message when issuing the fastboot oem unlock command?

pranavmali said:
Try Wug fresh's tool kit! To unlock bootloader
Click to expand...
Click to collapse
No effect, still stuck the same way.
below is the live log from the NRT toolkit
Live log initiated [2016-05-19]:
Analyzing factory image; please be patient...
Further extracting contents of factory image package for use in 'Force Flash Mode'...
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
04bfc514002e14ea fastboot
Connectivity Status: Fastboot Device Connected
+ Bootloader Status: Locked.
Checking ADB/FASTBOOT Connectivity
adb devices
03670030215d290e device
fastboot devices
04bfc514002e14ea fastboot
Connectivity Status: Fastboot Device Connected
+ Bootloader Status: Locked.
fastboot oem unlock
Rebooting your device...
and then suck at bootanimation loop

audit13 said:
Does the give give an error message when issuing the fastboot oem unlock command?
Click to expand...
Click to collapse
when i give the fast boot oem unlock command, it will get executed, my phone will ask for me to manually go to the yes key, hit power button to conform,
I am taken back to the bootloader screen, it shows lock state- unlocked
and the word "erasing..." flashes under it for less than 1 second and thats it...no other change what so ever, as soon as i reboot to bootloader or reboot the phone or do anything, the phone is back to the locked bootloader state.

The emmc is damaged or defective and can only be fixed with a motherboard replacement.

audit13 said:
The emmc is damaged or defective and can only be fixed with a motherboard replacement.
Click to expand...
Click to collapse
is there a sure-shot way of determining that my emmc is damaged ..?
the state that my phone is in now, it would make more sense to just buy a new device rather than replace the motherboard.
or
another option i can consider is the thread - http://forum.xda-developers.com/google-nexus-5/help/nexus-5-64gb-t3350533 for getting a new emmc and replacing, but before i take any actions i would like to know that there is no other option left.

Since you now appear to have nothing to lose, try installing the full N5 OTA image:
https://developers.google.com/android/nexus/ota#hammerhead-for-nexus-5-mobile
The instructions are on the page, or NRT has an OTA option (Advanced utilities/Sideload OTA update).
It may not work if your bootloader is genuinely locked or if the EMMC is really fried, but worst case you can't do any more damage, right?

Lenovo TB-X605F Magisk Root

"warning this will wipe your data"
"warning make sure that the tablet matches the firmware TB_X605F_USR_S200065_1905280020_Q00332_ROW
1. download adb setup https://forum.xda-developers.com/showthread.php?t=2588979
and install it
2. download the TB-X605F firmware http://www.mediafire.com/file/1uo5eu6iuzx39cd/TB_X605F_USR_S200065_1905280020_Q00332_ROW.zip/file
3. on the tablet go to settings and enable developer options
4. enable oem unlock and usb debugging
5. plug the tablet into the computer with usb cable and check the box on the tablet that allows usb debugging
6. reboot into fastboot using "adb reboot bootloader"
7. once fastboot has loaded type "fastboot oem unlock-go" to unlock the bootloader
8. then on computer extract the zip file and look for boot image "boot.img"
"make sure you have usb debugging enabled in developer options"
9. once your tablet is set up, on the android system prompt click "Charging this device via usb"
then click "Media device MTP" to access tablet storage on computer
10. download the magisk.apk file http://www.mediafire.com/file/vinf7xswbir90yi/magisk.apk/file
11. once downloaded drag the "boot.img" in firmware folder to internal storage
12. open command prompt and type adb install "the directory of the magisk apk file"
13. once magisk is installed launch the app and go to install / install / Select and Patch a File and look for the location of the boot.img
14. magisk will patch the boot image and put it in the download directory
15. go into download directory and you will see magisk_patched.img
16. on computer drag the magisk_patched.img on tablet storage to the directory where you want it to be
17. open cmd on computer type adb reboot bootloader
18. type fastboot flash boot "the directory of the magisk_patched.img"
19. once flashed type fastboot reboot
20. once booted go into magisk if it asks to update manager then update it, once the updated magisk manager is installed go to install / install / Direct Install to update root

Hi,
great job!
Do you know if it is possible to flash a recovery?
Thanks

Bootloop when trying magisk root
Hello,
I've tried your method, but since I've done "fastboot flash boot magisk_patched.img" my tablet entered in bootloop.
Impossible to flash original firmware with QFIL: I've "Switch to EDL download fail" 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"
}
I also tried Lenovo Moto Smart Assistant, but it fail too.
Many thanks for your help to rescue my tab...

justalone said:
Hello,
I've tried your method, but since I've done "fastboot flash boot magisk_patched.img" my tablet entered in bootloop.
Impossible to flash original firmware with QFIL: I've "Switch to EDL download fail" error...
I also tried Lenovo Moto Smart Assistant, but it fail too.
Many thanks for your help to rescue my tab...
Click to expand...
Click to collapse
What error did LMSA give you? The vol-up + USB-in combo is really touchy. Maybe give it a few more tries with LMSA.
Someone else had probs like this, but was able to boot into recovery using Pwr+VolUp+VolDown combo. If that works, see if you can factory reset.

justalone said:
Hello,
I've tried your method, but since I've done "fastboot flash boot magisk_patched.img" my tablet entered in bootloop.
Impossible to flash original firmware with QFIL: I've "Switch to EDL download fail" error...
I also tried Lenovo Moto Smart Assistant, but it fail too.
Many thanks for your help to rescue my tab...
Click to expand...
Click to collapse
Did you try power+vol up+vol down, 10 seconds long? It reinitialize the tab.
Good luck, neighbour

Hello,
thanks a lot for you help, LMSA stuck a 67% with error "fail to rescue".
The good solution was from my french neighbour with "power+vol up+vol down" for more than 10s. I then got acces to recovery and go to fasboot mode to flash original boot.img.
I've been then able to use LMSA to rescue my TAB and it's back to life !
I just wonder why magisk's boot generated was wrong... I'll make some other try in the weekend to root my tab.
Thanks a lot.
Merci du Var !

justalone said:
Thanks a lot.
Merci du Var !
Click to expand...
Click to collapse
De rien / you're welcome.
I had the same issue at 67% with LSMA.
Before I rooted the Tab, I upgraded it to Android 9 in Settings/System. Then everything worked fine.
I hope your house is safe despite this crazy rain.

This didnt work for me but maybe because the firmware that was on the tablet was 3 updates newer than the OP firmware.
It was stuck at the LENOVO boot image sadly
It took a long time but I got the tablet back trough a rescue.
The firmware was and again is: TB-X605F_S210126_191029_ROW
And I wonder if it will work if I get a boot.img from this firmware and patch it.

KrazyKlutt said:
This didnt work for me but maybe because the firmware that was on the tablet was 3 updates newer than the OP firmware.
It was stuck at the LENOVO boot image sadly
It took a long time but I got the tablet back trough a rescue.
The firmware was and again is: TB-X605F_S210126_191029_ROW
And I wonder if it will work if I get a boot.img from this firmware and patch it.
Click to expand...
Click to collapse
There's a magisk_patched.img for that build over on this thread.

Yahoo Mike said:
There's a magisk_patched.img for that build over on this thread.
Click to expand...
Click to collapse
Thanks a million Mike! You’re the best ?
XDA can be a jungle sometimes, I though I did research but I missed both the root thread and the TWRP thread for 605F.
That would have saved my lots of time a headache haha , but I didn’t get a heart attack so it’s all good.
Anyway, the patched Magisk worked perfectly, and all is good , finally a working YouTube Vanced since my previous Xperia 2 tablet.
The only weird thing was the link issue from Lenovo’s recovery for the latest firmware, the full one, not the ota updates.
???

twrp has problems, with screen bootlooping in twrp when trying to install zip files, the recovery is faulty and we probably need a new tree for the fix, which i was trying to look for an official tree, but i mean we already have one and when you compile it, it produced a faulty recovery image and lenovo hasn't released a kernel source or device tree yet, but i hope i can get a fully working one

turboperson123 said:
twrp has problems, with screen bootlooping in twrp when trying to install zip files, the recovery is faulty and we probably need a new tree for the fix...
Click to expand...
Click to collapse
Try this TWRP for X605F. I've been using the "update" function with no problems.
turboperson123 said:
... lenovo hasn't released a kernel source or device tree yet...
Click to expand...
Click to collapse
Have a look at this post.
There are so many hardware variants of the M10 now, it's probably impossible for Lenovo to release reliable kernel source. There's now even an M10 that uses SDM429 (rather than SDM450). ...and the second gen M10 FHD Plus (X606F) will use the MediaTek Helio P22T.

hello i have a problem i do the adb install command but it say "Missing APK file" plz help me

OnePlus 7 Pro 5G [UK Model] Bricked Please Help!

I was attempting to root my OnePlus 7 so that I could increase the volume limits (I'm hearing impaired) via TWRP and then eventually Magisk, however it seems many things went wrong along the way. I managed to get TWRP working on my phone but then it wasn't finding any of my stored memory and therefore the TWRP Zip file I needed to finally root the phone. In my efforts to correct that I have bricked my phone (not sure if it's hard bricked or soft bricked) but currently it will only boot into the fastboot menu and selecting any option brings me right back to the fastboot menu again.
I tried getting back to the TWRP but no luck when I try to boot it I get the error message FAILED (remote: Failed to load/authenticate boot image: Load 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"
}
After reading online for a bit of help I thought it might be hard bricked so I tried to use the MSM tool but again I had no luck due to Param Preload - Device not match image
I have attached screenshots for both issues, I've also tried guides for soft bricked OP7P and despite showing as successful they reboot right back into the fastboot menu as if nothing has happened.
Please I'd really appreciate some help I've been trying for days to fix this mess!

Darhk Citadel said:
I was attempting to root my OnePlus 7 so that I could increase the volume limits (I'm hearing impaired) via TWRP and then eventually Magisk, however it seems many things went wrong along the way. I managed to get TWRP working on my phone but then it wasn't finding any of my stored memory and therefore the TWRP Zip file I needed to finally root the phone. In my efforts to correct that I have bricked my phone (not sure if it's hard bricked or soft bricked) but currently it will only boot into the fastboot menu and selecting any option brings me right back to the fastboot menu again.
I tried getting back to the TWRP but no luck when I try to boot it I get the error message FAILED (remote: Failed to load/authenticate boot image: Load Error)
After reading online for a bit of help I thought it might be hard bricked so I tried to use the MSM tool but again I had no luck due to Param Preload - Device not match image
I have attached screenshots for both issues, I've also tried guides for soft bricked OP7P and despite showing as successful they reboot right back into the fastboot menu as if nothing has happened.
Please I'd really appreciate some help I've been trying for days to fix this mess!
Click to expand...
Click to collapse
How did you unlock the boot loader?

tech_head said:
How did you unlock the boot loader?
Click to expand...
Click to collapse
I enabled USB Debugging on my phone and then used "Shift + Right Click" from within the folder with twrp file and used the command "fastboot oem unlock"

Was in this situation. If you have an unlocked bootloader, try to search for the fastboot ROMs on xda. Not sure if there is a 5g version though. With a try. Best of luck.

Darhk Citadel said:
I enabled USB Debugging on my phone and then used "Shift + Right Click" from within the folder with twrp file and used the command "fastboot oem unlock"
Click to expand...
Click to collapse
Look here https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424

toonstra said:
Look here https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Click to expand...
Click to collapse
Thanks, I tried that this morning perhaps I did it wrong, but when I used the same cmd window as I did to "unlock" the bootloader nothing happened. It went through the process and finally finished with no errors and said "press any key to exit" -But as for my phone it did not reboot in fact there was no change at all, it remained on the bootloader screen as normal. When I tried to reboot for a normal load it looped back to the bootloader, when I tried to reboot to recovery it booted back to recovery. It was as if the fastboot ROM was completely ineffective.

Darhk Citadel said:
Thanks, I tried that this morning perhaps I did it wrong, but when I used the same cmd window as I did to "unlock" the bootloader nothing happened. It went through the process and finally finished with no errors and said "press any key to exit" -But as for my phone it did not reboot in fact there was no change at all, it remained on the bootloader screen as normal. When I tried to reboot for a normal load it looped back to the bootloader, when I tried to reboot to recovery it booted back to recovery. It was as if the fastboot ROM was completely ineffective.
Click to expand...
Click to collapse
So I just tried to flash a recovery.img and I got this error "failed (remote (recovery_a) no such partition)" which leads me to believe that my phone is a lot worse than I originally thought...
Any help would be greatly appreciated I fully accept that I messed this up BIG TIME!

Darhk Citadel said:
So I just tried to flash a recovery.img and I got this error "failed (remote (recovery_a) no such partition)" which leads me to believe that my phone is a lot worse than I originally thought...
Any help would be greatly appreciated I fully accept that I messed this up BIG TIME!
Click to expand...
Click to collapse
Ok so I finally managed to get to the root of the problem and my phone is now back up and running without any issues, I completely missed the correct MSM too package that I needed for my phone and region as I have a UK OnePlus Pro 7 5G I needed to use this specific package to reset my phone back to stock: [OP7PRO 5G EU][OOS 9.5.11 GM27BA]
Appreciate all the help everyone hopefully someone else can use this to avoid making the same mistake I did!

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

[solved + how i solved it] the current image(boot/recovery) have been destroyed

so, i was trying to install twrp, but i made a stupid mistake, instead of fastboot flash recovery i did fastboot flash boot, now it tells me: "the current image(boot/recovery) have been destroyed", when i go into bootloader, and attack the cable (both before and after) restarts itself.
things I tried: flash the original boot (it gave "FAILED (Write to device failed (no link))", obviously before the bootloader happened) change usb cable, flash the stock rom (obviously before the bootloader happened)), redownload adb /fastboot drivers, phone drivers, and google drivers. this is all i remember trying to do, i'm desperate, could someone help me please?

update: now i can use bootloader

update: I fixed it, in case this situation happened to you, I solved it like this: I had a windows update, while it was doing it, I connected the phone to the pc, in the end it no longer rebooted by itself (the phone) , then do fastboot flash boot (original boot), if it doesn't work, reboot the bootloader , from the bootloader, if it doesn't work, do the same thing downloading the drivers again, then do fastboot flash boot (original boot.img), if you want to download costum recovery, do fastboot flash recovery (costum recovery.img). I fixed it like this, now I have a costum recovery, costum rom and root!

Hello friend, I have a question. I closed the bootloader and when I closed it, the recovery image was destroyed.
Now I can't enter my cell phone and it stays in an infinite boot
any solution with locked bootloader

Angel1104 said:
Hello friend, I have a question. I closed the bootloader and when I closed it, the recovery image was destroyed.
Now I can't enter my cell phone and it stays in an infinite boot
any solution with locked bootloader
Click to expand...
Click to collapse
try going into the bootloader and re-unlocking it

{
"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"
}
That happened to me when I wanted to block the boot, so I think the boot was blocked and only stayed in the realme recovery like the following photo

Angel1104 said:
View attachment 5798249That happened to me when I wanted to block the boot, so I think the boot was blocked and only stayed in the realme recovery like the following photo
Click to expand...
Click to collapse
I don't understand if the recovery works or not, it's a bootloop with locked bootloader and you can go into recovery or locked bootloader without accessing recovery? you are confusing me, however, if you have access to recovery download the stock rom from the recovery, if not, try to unlock the bootloader again by doing fastboot flashing unlock, then flash the stock recovery and then download the stock rom from the recovery

And how do you enter that mode without the application?

enter bootloader and do fastboot reboot recovery, in bootloader you can't perform flashing actions and many other things (bootloader locked) but some things, like reboot should work

in case you get the same error for the recovery you have to unlock the bootloader again

Can I send you a private message?

yes

Did you solve it? I'm facing the same issue.

Gamer_Mida said:
update: I fixed it, in case this situation happened to you, I solved it like this: I had a windows update, while it was doing it, I connected the phone to the pc, in the end it no longer rebooted by itself (the phone) , then do fastboot flash boot (original boot), if it doesn't work, reboot the bootloader , from the bootloader, if it doesn't work, do the same thing downloading the drivers again, then do fastboot flash boot (original boot.img), if you want to download costum recovery, do fastboot flash recovery (costum recovery.img). I fixed it like this, now I have a costum recovery, costum rom and root!
Click to expand...
Click to collapse
I am having trouble understanding what you did exactly. I am getting this same error with a Xiaomi Mi 8 Lite.
Edit: got it working by disconnecting all usb ports and trying another port.

Angel1104 said:
Hello friend, I have a question. I closed the bootloader and when I closed it, the recovery image was destroyed.
Now I can't enter my cell phone and it stays in an infinite boot
any solution with locked bootloader
Click to expand...
Click to collapse
same as me i dont know what to do