Database Info

Moto G XT1033 Soft Bricked, Cannot Boot To TWRP or CWM

no custom recovery loading
I am currently using moto G first generation xt1033 indian dual sim version.
I have soft bricked my phone.
WHAT I HAVE: I have access to fastboot
My bootloader is unlocked
Access to stock recovery
PROBLEM: I have tried to flash twrp , cwm and philz recovery but every time i boot into recovery mode stock recovery loads.
I cannot access USB Debugging mode since the phone is soft bricked.
I have also tried to flash stock firmware no change seen.
I would be glad if you all can help me.
@ravibhat i have read your thread and my starting problem was same as yours @lost101 please help me as well.Thank You

Ok.Post pics,videos so that we know it's the same problem.
Go to a service centre when you can and share what they've told.

did u use these steps ?
fastboot erase recovery
fastboot flash recovery ur_recover_zip_name.zip
try different versions of recovery, i suggest u use CWM V6.0.4.7
If that works, use the adb sideload feature to flash the ROM

thank you for the reply
@ankur.walia
i tried the erase recovery command this was the output
{
"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"
}
and when i tried to lock bootloader this was the ouput

mrawal031 said:
@ankur.walia
i did not try the erase recovery command but i tried to flash it directly.
ill try this and revert i hope it wouldn't pose a problem if i directly flash the .img file
Click to expand...
Click to collapse
yes, and try the version i mentioned because i was also facing the problem like u and only this specific versions worked for me

still no change
@ankur.walia @ravibhat
i tried the command you told me to. There is no change im unable to boot in flash recovery also now xD.
i also went to the service centre they said there is nothing they can do for this phone as the only thing they know is to flash the stock firmware.

mrawal031 said:
@ankur.walia @ravibhat
i tried the command you told me to. There is no change im unable to boot in flash recovery also now xD.
i also went to the service centre they said there is nothing they can do for this phone as the only thing they know is to flash the stock firmware.
Click to expand...
Click to collapse
are u not able to go in fastboot mode now?
if u are, then ls try different versions of the recoveries...
and yes...what actually is happening? are u able to see the boot logo? its stuck in bootlogo screen?..or is it struck in recovery's logo screen?
are it is not even booting itself?

ankur.walia said:
are u not able to go in fastboot mode now?
if u are, then ls try different versions of the recoveries...
and yes...what actually is happening? are u able to see the boot logo? its stuck in bootlogo screen?..or is it struck in recovery's logo screen?
are it is not even booting itself?
Click to expand...
Click to collapse
I can go to the bootloader after entering stock recovery no combination of keys can display the option.
my phone starts normally shows logo and all booting animation but after that it gets stuck on a blank screen showing nothing and no touch response. I have tried aprox 4-5 variants of custom recoveries but i can flash none of them even after trying your command and getting success written on screen.

mrawal031 said:
I can go to the bootloader after entering stock recovery no combination of keys can display the option.
my phone starts normally shows logo and all booting animation but after that it gets stuck on a blank screen showing nothing and no touch response. I have tried aprox 4-5 variants of custom recoveries but i can flash none of them even after trying your command and getting success written on screen.
Click to expand...
Click to collapse
well if u got the successful execution of recovery flashing then it should go to recovery mode, try holding powe and volume down together for quite some time (5-6 seconds by the clock) and then release it

ankur.walia said:
well if u got the successful execution of recovery flashing then it should go to recovery mode, try holding powe and volume down together for quite some time (5-6 seconds by the clock) and then release it
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B6y6POATHFhrLVhpUThNVUc1VXc/view?usp=sharing
you can see the condition even after flashing the custom recovery i get booted into stock recovery

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?

[Recovery] TWRP 3.2.1-0 for GPD XD Plus / XD+ Handheld MT8176

Update: Thread outdated. A new and working version of TWRP was posted in another Forum. Thanks.

{
"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 get this
PS: On instructions for second method you may want to mention you have to rename twrp image to recovery.img

My device is now stuck in the fastboot menu. It says I can navigate the menu using volume up and down but pressing either of those doesn't do anything and I can't seem to power off the device by holding the power button. Any suggestions on how to fix this?

laod said:
My device is now stuck in the fastboot menu. It says I can navigate the menu using volume up and down but pressing either of those doesn't do anything and I can't seem to power off the device by holding the power button. Any suggestions on how to fix this?
Click to expand...
Click to collapse
Some people have reported that touch isn't working and partitions aren't mounting properly. I tried to fix most issues and uploaded a new version. I do not own this device personally - so i can not test the fixes. Please give me feedback for the updated version.

I just got my GPD XD+ today, thanks for the TWRP build but on mine, even with the current build (2018/04/01), I can't perform any actions. Touch still seems not to work for me. I can't get past TWRP asking me "Keep System Read-only?" Let alone see if partitions are loading correctly.
Everything is in portrait mode which is awkward for this device. What about landscape? Shouldn't it be 1280x720 rather than 720x1280?
**Update**
It would appear that my touch controls are inverted... so the fix for others, seems to have inverted my own.
**Update 2***
Well... after realizing the touchscreen was reversed for me, I was able to slide the "Swipe to allow modifications" slider but after that, I chose to reboot out of recovery since the likelyhood of me hitting something by mistake with the controls reversed was high. Being very careful, I was able to tell it to reboot to system and now the system hangs at the GPD logo.. which no longer animates... I can no longer boot into anything but recovery and fastboot.
Any theories as to what has happened? Does anyone have a Clean Stock ROM of the plus model so I can start over using adb?
**Update 3**
PsyOps pointed me towards some stock images at "forum.gpd.hk/t3-the-latest-firmware-of-gpd-game-console" and I'm back in business. Had to flash more than just recovery and boot.. had to flash system as well for some reason.

Goayandi said:
Some people have reported that touch isn't working and partitions aren't mounting properly. I tried to fix most issues and uploaded a new version. I do not own this device personally - so i can not test the fixes. Please give me feedback for the updated version.
Click to expand...
Click to collapse
I have the same situation here.
It happened after unlocked the bootloader, so it's nothing to do with the recovery.
The adb commend return the error: device '(null)' not found.

I can't check the "recovery" box. It doesn't do anything. And the first methode doesn"t work
EDIT : nevermind, I did it but same problem as Busted77

laod said:
My device is now stuck in the fastboot menu. It says I can navigate the menu using volume up and down but pressing either of those doesn't do anything and I can't seem to power off the device by holding the power button. Any suggestions on how to fix this?
Click to expand...
Click to collapse
Same thing here. Now waiting for the battery to empty. What happens after that? Will it work fine and the bootloader be unlocked?

vanzan said:
Same thing here. Now waiting for the battery to empty. What happens after that? Will it work fine and the bootloader be unlocked?
Click to expand...
Click to collapse
I was being dinner and used adb commands instead of fast boot. If you have your device plugged into a computer with fastboot setup you can run "fastboot reboot" and everything should work.

vanzan said:
Same thing here. Now waiting for the battery to empty. What happens after that? Will it work fine and the bootloader be unlocked?
Click to expand...
Click to collapse
Wait for the battery runs out, then recharge, it works fine and the bootloader is unlocked, the first boot will take longer and a few reboot.
And I find that any time you issue fastboot command from you pc, the xd plus will stuck and you have to wait the battery runs out.
I installed the Magisk use fastboot method, stuck again, and need to wait for the battery runs out, recharged, and evertyhing ok then.
There's another root method on Chinese forum (flash supersu pack by recovery), since I rooted by installin Magisk, I didn't try that.
---------- Post added at 11:46 ---------- Previous post was at 11:45 ----------
laod said:
I was being dinner and used adb commands instead of fast boot. If you have your device plugged into a computer with fastboot setup you can run "fastboot reboot" and everything should work.
Click to expand...
Click to collapse
No, when I stuck in the fastboot menu, the adb command return error that no device can find, I have to unplug battery or wait for the battery runs out.

"fastboot reboot" worked perfectly for me!

Fastboot stuck
Same problem here.
I installed the drivers but got the error.
Now my device is in fastboot mode but fastboot reboot etc. don't work.. And I just can't turn it off..
Im really sad.
Windows 10 x64

So.. At least I could fix the problem, I installed the Drivers (had do disable driver signature) and installed your TWRP Mod successfully but the Screen is mirrored! U can use it but its very tricky.. I could open "Install" But if I open it, twrp could not load any data it called "0MB Space" and yeah after reboot, my GPD XD Plus DON'T start..

LeraxGER said:
So.. At least I could fix the problem, I installed the Drivers (had do disable driver signature) and installed your TWRP Mod successfully but the Screen is mirrored! U can use it but its very tricky.. I could open "Install" But if I open it, twrp could not load any data it called "0MB Space" and yeah after reboot, my GPD XD Plus DON'T start..
Click to expand...
Click to collapse
I had the same issue, could use it inverted and mirrored but after running it and not doing anything with it, I could no longer boot into system... Only into recovery. If I tried to boot into system, the boot animation would never animate and the system would hang.
See PsyOps' reply to my question of where to find a stock rom. You can either use the provided tool or you can use adb commands to reflash your system partition... At least for me I had to flash system... Flashing boot and recovery (removing TWRP) didn't work alone...
reddit.com/r/gpdxd/comments/8a50vq/gpd_xd_plus_stock_rom_available/

Busted77 said:
I had the same issue, could use it inverted and mirrored but after running it and not doing anything with it, I could no longer boot into system... Only into recovery. If I tried to boot into system, the boot animation would never animate and the system would hang.
See PsyOps' reply to my question of where to find a stock rom. You can either use the provided tool or you can use adb commands to reflash your system partition... At least for me I had to flash system... Flashing boot and recovery (removing TWRP) didn't work alone...
reddit.com/r/gpdxd/comments/8a50vq/gpd_xd_plus_stock_rom_available/
Click to expand...
Click to collapse
Thanks for the advice, I spoke with him too and he already gave me the guide how to boot into Recovery Mode and then fastboot (Hold VOL+ & On Off Untill Menu apperas, then boot into recovery, then if the android guy appears press On/Off and THEN VOL+, so you're in the normal recovery mode for all the other poor user's )
And I flashed system.img, boot and stock recovery and then it booted up..
The only thing is, that I think that the SD card won't mount correctly anytime and if I plug it to the PC, I dont see the SD card and big files (like the StockROM Update 1.10 abort before its finished).
Greetings

Contact me in discord.

Could you please close the thread and delte the download link? Not even once your TWRP worked, please don't share the file anymore. Other user's will brick their device too.

Hello how to fix a black screen caused by overheating device?i dont know how to use the stock recovery i have thr gpd boot logo but after a black screen and blue led thanks

moto g8 plus flashing-locked

it does not start and I can not put any rom
{
"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"
}

Hi, try booting with a boot.img in the same version of your phone.
First, type in CMD fastboot getvar all
Second, Look for the line which states your installed rom version.
Third, Download the same rom and extract the boot.img from the zip file
Fourth, In CMD type fastboot boot boot.img If nothing goes wrong with the download, your device should boot up. Then check to see if you can activate the OEM lock. If not, try updating phone. Does it let you you update? great do it. If it show device system integrity corrupted, wait seven days without turning phone off and try updating again. If still no dice, then you're out of luck.
I had same problem as you, and what got mine back from the dead was to keep updating till one update fixed my issue.

mrsiri said:
Hi, try booting with a boot.img in the same version of your phone.
First, type in CMD fastboot getvar all
Second, Look for the line which states your installed rom version.
Third, Download the same rom and extract the boot.img from the zip file
Fourth, In CMD type fastboot boot boot.img If nothing goes wrong with the download, your device should boot up. Then check to see if you can activate the OEM lock. If not, try updating phone. Does it let you you update? great do it. If it show device system integrity corrupted, wait seven days without turning phone off and try updating again. If still no dice, then you're out of luck.
I had same problem as you, and what got mine back from the dead was to keep updating till one update fixed my issue.
Click to expand...
Click to collapse
Friend. could you help me?
I tried this method but it did not work, i tried with the version that the getvar gives me :
(bootloader) ro.build.fingerprint[0]: motorola/doha/doha:10/QPI30.28-Q3-
(bootloader) ro.build.fingerprint[1]: 28-26-4-1/2f8cb:user/release-keys
But it still don't work, i tried every other compilation too, excluding the Android 9 ones... I also tried blankflash but did not work.
It gives me error and goes to the "Your device is corrupt. It can't be trusted and will not boot" screen:
fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.845s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 32.039s

setryky said:
Friend. could you help me?
I tried this method but it did not work, i tried with the version that the getvar gives me :
(bootloader) ro.build.fingerprint[0]: motorola/doha/doha:10/QPI30.28-Q3-
(bootloader) ro.build.fingerprint[1]: 28-26-4-1/2f8cb:user/release-keys
But it still don't work, i tried every other compilation too, excluding the Android 9 ones... I also tried blankflash but did not work.
It gives me error and goes to the "Your device is corrupt. It can't be trusted and will not boot" screen:
fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.845s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 32.039s
Click to expand...
Click to collapse
Fastboot boot won't work because locked bootloader checks for a key which don't match correctly. You should try same version as the one installed on your phone or newer. Can you boot system?
The only way is to get blankflash to work. Try other computer, preferably older ones with intel, not AMD. If system is able to boot try OTA update because it fixed on mine.

mrsiri said:
Fastboot boot won't work because locked bootloader checks for a key which don't match correctly. You should try same version as the one installed on your phone or newer. Can you boot system?
The only way is to get blankflash to work. Try other computer, preferably older ones with intel, not AMD. If system is able to boot try OTA update because it fixed on mine.
Click to expand...
Click to collapse
I know that this version (QPI30.28-Q3-28-26-4-1) is the correct one because i had flashed my phone with it before trying to lock the bootloader, and it worked. I also tried every other compilation. I got the .rar from lolinet.
I tried blankflash, it did not work... It still gives me the same error. My computer on a i7 920, so it's very old. Anyways, thanks for any help you might be able to provide.

Setryky did you find any solution? I have the same problem

Fael.exe said:
Setryky did you find any solution? I have the same problem
Click to expand...
Click to collapse
I did not

setryky said:
I know that this version (QPI30.28-Q3-28-26-4-1) is the correct one because i had flashed my phone with it before trying to lock the bootloader, and it worked. I also tried every other compilation. I got the .rar from lolinet.
I tried blankflash, it did not work... It still gives me the same error. My computer on a i7 920, so it's very old. Anyways, thanks for any help you might be able to provide.
Click to expand...
Click to collapse
You should get boot.img from rom and use command fastboot boot boot.img to boot to rom. Then try oem unlock option activating or OTA updating if first doesn't work

mrsiri said:
You should get boot.img from rom and use command fastboot boot boot.img to boot to rom. Then try oem unlock option activating or OTA updating if first doesn't work
Click to expand...
Click to collapse
i did that with every rom in lolinet... did not work. And now it is saying that my device has "no bootable a/b slot".

Does your device show up as QCOM 9008? It's the EDL state and only way to install via blank flash

mrsiri said:
Does your device show up as QCOM 9008? It's the EDL state and only way to install via blank flash
Click to expand...
Click to collapse
no, it does not. I already tried blankflash... When i do blankflash it goes back to the "your device is corrupted" screen.

setryky said:
no, it does not. I already tried blankflash... When i do blankflash it goes back to the "your device is corrupted" screen.
Click to expand...
Click to collapse
You can't do blank flash if it's not showing QCOM 9008 mode on device manager, that's the device EDL mode. I'm afraid that's you only option, aside from opening back glass plate and shorting 2 points in motherboard or using a stripped USB cable and shorting green cable to black cable

setryky said:
i did that with every rom in lolinet... did not work. And now it is saying that my device has "no bootable a/b slot".
Click to expand...
Click to collapse
No bootable a/b slot... You wiped system?

mrsiri said:
You can't do blank flash if it's not showing QCOM 9008 mode on device manager, that's the device EDL mode. I'm afraid that's you only option, aside from opening back glass plate and shorting 2 points in motherboard or using a stripped USB cable and shorting green cable to black cable
Click to expand...
Click to collapse
Idk the points in motherboard so best way is to use cable method or buy an EDL cable online or use a "box" which flashes directly through JTAG but that is expensive. Just leave the green and black cables connected for 8 seconds if nothing happens try again this time for 20 seconds

mrsiri said:
Idk the points in motherboard so best way is to use cable method or buy an EDL cable online or use a "box" which flashes directly through JTAG but that is expensive. Just leave the green and black cables connected for 8 seconds if nothing happens try again this time for 20 seconds
Click to expand...
Click to collapse
i entered in the edl mode via the pins... the blankflash did work, but not to fix my system.

mrsiri said:
No bootable a/b slot... You wiped system?
Click to expand...
Click to collapse
no, its like when i do "fastboot boot boot.img" too many times, and when i do a blankflash it goes to that your device is corrupted screen.

The EDL should have worked... Well your last bet is on the box JTAG flasher. You'll either buy it and learn how to flash or ask some professional to do it

boa tarde eu to com esse problema no meu moto g8 plus flashing- locked ...alguem pode me ajudar por favor
Mod translation via GT: good afternoon I have this problem on my moto g8 plus flashing-locked ... can someone help me please

[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