Database Info

G6-L11 Stuck in Fastboot & Rescue mode

My brothers Huawei G6-L11 suddenly rebooted yesterday in fastboot / recovery mode. It says to connect it to a PC with Hirsute installed. Tried it, also installed Fastboot, ADB and drivers but the program didn't find the phone. Then i tried looking for the recovery image because it says: "recovery image verify failed" before it get's into this mode. I found it and tried to flash it using Fastboot but failed, I think this is because the phone is locked? So i Googled for an unlock code and found out Huawei has a website for it but i need a product ID wich I can't find if the phone can't boot. Anyone an idea on what i should try next?

Skoshy-007 said:
My brothers Huawei G6-L11 suddenly rebooted yesterday in fastboot / recovery mode. It says to connect it to a PC with Hirsute installed. Tried it, also installed Fastboot, ADB and drivers but the program didn't find the phone. Then i tried looking for the recovery image because it says: "recovery image verify failed" before it get's into this mode. I found it and tried to flash it using Fastboot but failed, I think this is because the phone is locked? So i Googled for an unlock code and found out Huawei has a website for it but i need a product ID wich I can't find if the phone can't boot. Anyone an idea on what i should try next?
Click to expand...
Click to collapse
Did you find a solution?

Skoshy-007 said:
My brothers Huawei G6-L11 suddenly rebooted yesterday in fastboot / recovery mode. It says to connect it to a PC with Hirsute installed. Tried it, also installed Fastboot, ADB and drivers but the program didn't find the phone. Then i tried looking for the recovery image because it says: "recovery image verify failed" before it get's into this mode. I found it and tried to flash it using Fastboot but failed, I think this is because the phone is locked? So i Googled for an unlock code and found out Huawei has a website for it but i need a product ID wich I can't find if the phone can't boot. Anyone an idea on what i should try next?
Click to expand...
Click to collapse
Have you try to flash a defoult ROM?
Example B118? http://consumer.huawei.com/kh/support/products/downloads/detail/ascend-g6-4g-kh.htm?id=25971
than extract dload folder and copy to sd card, press vol +, vol - and power at same time, and can be one of this 2 way:
1º - HOLD IT, the phone boots but don´t release any key, let boot 2x, relase only power in next boot than vols when flash starts
or
2º - HOLD IT, but the phone dont boot, don´t release any key, 3 seconds and release only power than vols when starts the flash.

persona78 said:
Have you try to flash a defoult ROM?
Example B118? http://consumer.huawei.com/kh/support/products/downloads/detail/ascend-g6-4g-kh.htm?id=25971
than extract dload folder and copy to sd card, press vol +, vol - and power at same time, and can be one of this 2 way:
1º - HOLD IT, the phone boots but don´t release any key, let boot 2x, relase only power in next boot than vols when flash starts
or
2º - HOLD IT, but the phone dont boot, don´t release any key, 3 seconds and release only power than vols when starts the flash.
Click to expand...
Click to collapse
Hi, i try this way, but nothing happens, always go to "fastboot&rescue mode".
No way to see Device ID to try unlock bootloader.
I think is dead phone.

(Hi, i try this way, but nothing happens, always go to "fastboot&rescue mode".
No way to see Device ID to try unlock bootloader.
I think is dead phone.)
i totally agree with this person please help me already in trouble with my phone from 2 week cant find any solution even not connected to my laptop

wajihafatima said:
(Hi, i try this way, but nothing happens, always go to "fastboot&rescue mode".
No way to see Device ID to try unlock bootloader.
I think is dead phone.)
i totally agree with this person please help me already in trouble with my phone from 2 week cant find any solution even not connected to my laptop
Click to expand...
Click to collapse
Hi,
i had the same issue (locked bootloader) for my Huawei G6-L33, but I used a program called "Huawei Product ID Generator.exe " and my phone is already unlocked. The tricky with this program was to select as a huawei model "HUAWEI Y300-0100" even if your phone model is different. Also at the huawei web page for unlocking devices (https://emui.huawei.com/en) you have to enter the same tricky model "HUAWEI Y300-0100". All the rest info of your phone is the same, i.e. IMEI, SERIAL NUMBER.
I hope it could help you

Very thanks!!!
doowa said:
hi,
i had the same issue (locked bootloader) for my huawei g6-l33, but i used a program called "huawei product id generator.exe " and my phone is already unlocked. The tricky with this program was to select as a huawei model "huawei y300-0100" even if your phone model is different. Also at the huawei web page for unlocking devices (https://emui.huawei.com/en) you have to enter the same tricky model "huawei y300-0100". All the rest info of your phone is the same, i.e. Imei, serial number.
I hope it could help you
Click to expand...
Click to collapse

Anyone can post the Link to the current bootloader unlocking page ? as the posted one is not working.
and any chance someone could upload the Application to generate the Product ID somewhere ?
bufank said:
Very thanks!!!
Click to expand...
Click to collapse

[FIX] Orange State Bootloop on OUKITEL K6000 Plus - HOW TO FIX

Hello,
After unlocking the bootloader and installing TWRP on my OUKITEL K6000 Plus I was trying to install madOS, but unfortunately my phone went into Orange State bootloop. I could not enter fastboot anymore, and at some point even Recovery stopped to work. My phone was almost dead. I was looking for solutions but actually there was no clear guide how to revive a patient. I found that many people have similar issue so when I finally managed to resurrect my K6000 with original stock ROM I decided to share my solution.
Here's the fix:
1. Google for 'Techprolonged MediaTek MT65xx USB VCOM Drivers'. Using the guide you will find install MediaTek DA USB VCOM Port Drivers via Device Manager (step 5). Do this even if you already previously installed MediaTek USB VCOM Drivers. This is very important to install this DA version of drivers, otherwise you may have problems with uploading stock ROM via SP Flash Tool.
2. Install SP Flash Tool if you don't have it yet. You can find it easily with google.
3. Download original stock K6000 Plus ROM V6.0. You can find it easily on needrom website (NOTE: you have to create an account on needrom if you don't have it yet). Unpack it.
4. Launch SP Flash Tool, go to Options->Option... in Connection settings change USB speed to Full speed and Battery to with battery. Close Option window.
5. In SP Flash Tool go to Download tab, click on choose right next to Scatter-loading file field, navigate to the folder where you unpacked previously downloaded stock K6000 Plus ROM V6.0. Open MT6750_Android_scatter.txt file.
6. In open menu choose Download Only if it's not selected by default. All fields below should have tick enabled. I mean for 'preloader', for 'recovery', etc...
7. Unplug your phone from PC if it's connected. Shut down your phone by clicking and holding for approx 10 secs ALL THREE BUTTONS: VOL UP + VOL DOWN + POWER. If you do this properly, your phone should not self-boot into Orange State anymore.
8. In SP Flash Tool click Download icon (the one with green arrow), all the fields should become inactive.
9. Using one hand only click and hold at the same time VOL UP + POWER button.
10. Now, while you still hold these buttons, you have to connect your phone to PC (plug in micro USB cable into your phone). VERY IMPORTANT: If you have STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003) error after you connect it means you don't have DA version of MediaTek driver properly installed (step no. 1).
11. Your phone should start to flash up and you should see the progress in SP Flash Tool status bar. You can release VOL UP and POWER button now. The process may take long time, for me it was more than 1 hour. The longest part was flashing up the [system]. The good thing is you can observe the progress during whole process.
12. When flashing process is end you will see a small window with the information about completion. Now you can unplug your phone, and launch it with POWER button. You should still see the Orange State message but right after that your phone should boot up into normal mode with freshly uploaded original stock ROM. Congratulations!
Hopefully this will also fix your K6000 Plus and maybe even other models.
I'm really sorry I don't provide any direct links, but I haven't posted 10 posts yet and my XDA account is still limited.
Regards,
Slavedriver

Please help I have error 4032 (BROM ERROR S_FT_ENABLE_DRAM_FAIL)

1. Google for 'Techprolonged MediaTek MT65xx USB VCOM Drivers'. Using the guide you will find install MediaTek DA USB VCOM Port Drivers via Device Manager (step 5). Do this even if you already previously installed MediaTek USB VCOM Drivers. This is very important to install this DA version of drivers, otherwise you may have problems with uploading stock ROM via SP Flash Tool.
this should solve that

STATUS_BROM_CMD_SEND_DA_FAIL
persists even after installing correct drivers?
Solution: Choose
Download Agent as DA-PL in SP flash tools. And follow the same guide.

Thank you so much for this post, just saved an Oukitel K6000 Plus. Just finished process, rebooting normally for first use. It's been stressfull hours, what a relieve.

slavedriver83 said:
9. Using one hand only click and hold at the same time VOL UP + POWER button.
10. Now, while you still hold these buttons, you have to connect your phone to PC (plug in micro USB cable into your phone). VERY IMPORTANT: If
Click to expand...
Click to collapse
this helped me a lot with my ulefone armor 2, thanks

Fixed the orange state, thanks a lot for this guide.
Do you think I shall try again to upgrade to Android 8 anymore?

slavedriver83 said:
9. Using one hand only click and hold at the same time VOL UP + POWER button.
Click to expand...
Click to collapse
Thank you very much for the advice
I thought I put my phone in the trash when I read this.
But in point 9 I had to push only the VOL UP if I press the two buttons, the AP returns an error.

You saved mine as well, slavedriver!
And it is a Teclast Tpad A10S!
I had given it up.
Thanks a lot!

It works also on U20 plus. I had to select DA_SWSEC as Download Agent. Thank you so much!

Guide worked Perfectly for me.
My mobile was bricked in the same Bootloop. The guide worked perfectly for me. Thanks a lot for useful and detailed help.

I understand this thread is almost 1 year old. I tried this procedure and everything went well. The only problem the phone does not boot. It does turn on but nothing comes up. No boot menu no logo just a few flickering lights and a very dark background. Does anyone have any ideas?
OK6000 Plus

pvkid said:
I understand this thread is almost 1 year old. I tried this procedure and everything went well. The only problem the phone does not boot. It does turn on but nothing comes up. No boot menu no logo just a few flickering lights and a very dark background. Does anyone have any ideas?
OK6000 Plus
Click to expand...
Click to collapse
Tried this guide but SP shows the following messagge "STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060005) " (so it doesn't end with 3 but with 5)

Pyandroid said:
1. Google for 'Techprolonged MediaTek MT65xx USB VCOM Drivers'. Using the guide you will find install MediaTek DA USB VCOM Port Drivers via Device Manager (step 5). Do this even if you already previously installed MediaTek USB VCOM Drivers. This is very important to install this DA version of drivers, otherwise you may have problems with uploading stock ROM via SP Flash Tool.
this should solve that
Click to expand...
Click to collapse
Bro I got a different error just looks like:
ERROR STATUS_SEC_AUTH_FILE_NEEDED (0xc0030012)
Please help me out...I use "tecno spark 4 kc2"

slavedriver83 said:
Hello,
After unlocking the bootloader and installing TWRP on my OUKITEL K6000 Plus I was trying to install madOS, but unfortunately my phone went into Orange State bootloop. I could not enter fastboot anymore, and at some point even Recovery stopped to work. My phone was almost dead. I was looking for solutions but actually there was no clear guide how to revive a patient. I found that many people have similar issue so when I finally managed to resurrect my K6000 with original stock ROM I decided to share my solution.
Here's the fix:
1. Google for 'Techprolonged MediaTek MT65xx USB VCOM Drivers'. Using the guide you will find install MediaTek DA USB VCOM Port Drivers via Device Manager (step 5). Do this even if you already previously installed MediaTek USB VCOM Drivers. This is very important to install this DA version of drivers, otherwise you may have problems with uploading stock ROM via SP Flash Tool.
2. Install SP Flash Tool if you don't have it yet. You can find it easily with google.
3. Download original stock K6000 Plus ROM V6.0. You can find it easily on needrom website (NOTE: you have to create an account on needrom if you don't have it yet). Unpack it.
4. Launch SP Flash Tool, go to Options->Option... in Connection settings change USB speed to Full speed and Battery to with battery. Close Option window.
5. In SP Flash Tool go to Download tab, click on choose right next to Scatter-loading file field, navigate to the folder where you unpacked previously downloaded stock K6000 Plus ROM V6.0. Open MT6750_Android_scatter.txt file.
6. In open menu choose Download Only if it's not selected by default. All fields below should have tick enabled. I mean for 'preloader', for 'recovery', etc...
7. Unplug your phone from PC if it's connected. Shut down your phone by clicking and holding for approx 10 secs ALL THREE BUTTONS: VOL UP + VOL DOWN + POWER. If you do this properly, your phone should not self-boot into Orange State anymore.
8. In SP Flash Tool click Download icon (the one with green arrow), all the fields should become inactive.
9. Using one hand only click and hold at the same time VOL UP + POWER button.
10. Now, while you still hold these buttons, you have to connect your phone to PC (plug in micro USB cable into your phone). VERY IMPORTANT: If you have STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003) error after you connect it means you don't have DA version of MediaTek driver properly installed (step no. 1).
11. Your phone should start to flash up and you should see the progress in SP Flash Tool status bar. You can release VOL UP and POWER button now. The process may take long time, for me it was more than 1 hour. The longest part was flashing up the [system]. The good thing is you can observe the progress during whole process.
12. When flashing process is end you will see a small window with the information about completion. Now you can unplug your phone, and launch it with POWER button. You should still see the Orange State message but right after that your phone should boot up into normal mode with freshly uploaded original stock ROM. Congratulations!
Hopefully this will also fix your K6000 Plus and maybe even other models.
I'm really sorry I don't provide any direct links, but I haven't posted 10 posts yet and my XDA account is still limited.
Regards,
Slavedriver
Click to expand...
Click to collapse
Solution?
for:
ERROR STATUS_SEC_AUTH_FILE_NEEDED (0xc0030012)
"Tecno spark 4 kc2"

slavedriver83 said:
Hello,
After unlocking the bootloader and installing TWRP on my OUKITEL K6000 Plus I was trying to install madOS, but unfortunately my phone went into Orange State bootloop. I could not enter fastboot anymore, and at some point even Recovery stopped to work. My phone was almost dead. I was looking for solutions but actually there was no clear guide how to revive a patient. I found that many people have similar issue so when I finally managed to resurrect my K6000 with original stock ROM I decided to share my solution.
Here's the fix:
1. Google for 'Techprolonged MediaTek MT65xx USB VCOM Drivers'. Using the guide you will find install MediaTek DA USB VCOM Port Drivers via Device Manager (step 5). Do this even if you already previously installed MediaTek USB VCOM Drivers. This is very important to install this DA version of drivers, otherwise you may have problems with uploading stock ROM via SP Flash Tool.
2. Install SP Flash Tool if you don't have it yet. You can find it easily with google.
3. Download original stock K6000 Plus ROM V6.0. You can find it easily on needrom website (NOTE: you have to create an account on needrom if you don't have it yet). Unpack it.
4. Launch SP Flash Tool, go to Options->Option... in Connection settings change USB speed to Full speed and Battery to with battery. Close Option window.
5. In SP Flash Tool go to Download tab, click on choose right next to Scatter-loading file field, navigate to the folder where you unpacked previously downloaded stock K6000 Plus ROM V6.0. Open MT6750_Android_scatter.txt file.
6. In open menu choose Download Only if it's not selected by default. All fields below should have tick enabled. I mean for 'preloader', for 'recovery', etc...
7. Unplug your phone from PC if it's connected. Shut down your phone by clicking and holding for approx 10 secs ALL THREE BUTTONS: VOL UP + VOL DOWN + POWER. If you do this properly, your phone should not self-boot into Orange State anymore.
8. In SP Flash Tool click Download icon (the one with green arrow), all the fields should become inactive.
9. Using one hand only click and hold at the same time VOL UP + POWER button.
10. Now, while you still hold these buttons, you have to connect your phone to PC (plug in micro USB cable into your phone). VERY IMPORTANT: If you have STATUS_BROM_CMD_SEND_DA_FAIL (0xC0060003) error after you connect it means you don't have DA version of MediaTek driver properly installed (step no. 1).
11. Your phone should start to flash up and you should see the progress in SP Flash Tool status bar. You can release VOL UP and POWER button now. The process may take long time, for me it was more than 1 hour. The longest part was flashing up the [system]. The good thing is you can observe the progress during whole process.
12. When flashing process is end you will see a small window with the information about completion. Now you can unplug your phone, and launch it with POWER button. You should still see the Orange State message but right after that your phone should boot up into normal mode with freshly uploaded original stock ROM. Congratulations!
Hopefully this will also fix your K6000 Plus and maybe even other models.
I'm really sorry I don't provide any direct links, but I haven't posted 10 posts yet and my XDA account is still limited.
Regards,
Slavedriver
Click to expand...
Click to collapse
Hi, do I need my phone to be rooted to do this.
I unlocked bootloader in my gionee f205 from fastboot and now it is in orange state bootloop.
I haven't rooted my phone before doing it.

LG V20 F800K bricked

Please help... I'm trying to update v20 f800k to v30e pie using uppercut but something went wrong... To cut it all short, My phone is no longer connection to pc in download mode and not visible in device manager
I have tried to uninstall and reinstall all neccessary lg drivers.
All i get is the korean text
"waiting for connection"
Unknown B92 "now on B61 after numerous battery pullout"
Unknown / E / L / RO

yemkoid said:
Please help... I'm trying to update v20 f800k to v30e pie using uppercut but something went wrong... To cut it all short, My phone is no longer connection to pc in download mode and not visible in device manager
I have tried to uninstall and reinstall all neccessary lg drivers.
All i get is the korean text
"waiting for connection"
Unknown B92 or B93 or B94
Unknown / E / L / RO
https://drive.google.com/open?id=1AD4MVQfzADgdoH80xb6-zxNNID0tTU2f
Click to expand...
Click to collapse
put this .dll in the common folder, let's see if it happened by chance. https://mega.nz/#!qV9WzQSQ!Z0Zkpm-m3LJ01tLthzfE9puNmYlbsOoZR5N-f2VS_mw extract and rename LGUP_common.dll

bernavaldiesel1 said:
Does lgup recognize it? What drivers do you have installed? Let's see if I can help.
If you remove the battery and put it back, does the phone turn on?
Click to expand...
Click to collapse
Thanks for the reply. From all my problem descriptions, and with picture of the phone still turning on to download mode...
I installed,
LGUP_Install_Ver_1_14_3
LGMobileDriver_WHQL_Ver_4.4.2
LGBridge_Setup
UPPERCUT_1.0.0.0
...and despite changing to different usb c, the phone is not any visible to pc nor lgup or device manager.

The main problem i'm facing now are the errors on download mode.
Unknown B92
Unknown / E / L / RO

yemkoid said:
The main problem i'm facing now are the errors on download mode.
Unknown B92
Unknown / E / L / RO
Click to expand...
Click to collapse
put this .dll in the common folder, let's see if it happened by chance. https://mega.nz/#!qV9WzQSQ!Z0Zkpm-m3LJ01tLthzfE9puNmYlbsOoZR5N-f2VS_mw extract and rename LGUP_common.dll
if it works, install the latest version of android 8 for your model with lgup not with uppercut, run the lgup exe.
https://forum.xda-developers.com/v20/how-to/guide-lg-v20-to-life-t3827732/amp/

bernavaldiesel1 said:
put this .dll in the common folder, let's see if it happened by chance. https://mega.nz/#!qV9WzQSQ!Z0Zkpm-m3LJ01tLthzfE9puNmYlbsOoZR5N-f2VS_mw extract and rename LGUP_common.dll
if it works, install the latest version of android 8 for your model with lgup not with uppercut, run the lgup exe.
https://forum.xda-developers.com/v20/how-to/guide-lg-v20-to-life-t3827732/amp/
Click to expand...
Click to collapse
I already placed the common dll for f800k prior to flashing oreo which is the same file and oreo kdz i used to update from nougat.
still, pc isn't making any sound of connection of phone been connected
Also the LGflashtool from the second link i already tried earlier. COM41 is not recognised since the phone doesnt communicate with the ports, so not visible to Device manager

yemkoid said:
I already placed the common dll for f800k prior to flashing oreo which is the same file and oreo kdz i used to update from nougat.
still, pc isn't making any sound of connection of phone been connected
Also the LGflashtool from the second link i already tried earlier. COM41 is not recognised since the phone doesnt communicate with the ports, so not visible to Device manager
Click to expand...
Click to collapse
If you remove the battery and put it back, is the phone still the same? The cell phone cannot be turned on, so it is a brick. I will go looking for possible solutions, and consider the possibility of using another PC or try to install updates for your PC if it is not already installed.

When i remove and reinsert and then using the vol- & power button combo the phone is still entering download mode with the Unknown / E / L / RO error

Maybe i'll try another pc and give back reply soonest Thanks

I think I have a similar problem that I solved. I wanted to try to flash the root on 9 android, but it didn’t work, the smartphone stopped showing in download mode and in the device manager, but it was detected in fastboot mode. I'm not sure that I showed the same errors, since the stripes on the screen did not allow me to examine the text. Flash recovery https://androidfilehost.com/?fid=11410932744536982447 through fastboot mode, and in recovery-> format data, flash firmware in zip format from 995 https://forum.xda-developers.com/v20/development/vs995-verizon-lg-v20-stock-oreo-rooted-t3845669. After that, the smartphone was detected in download mode and I reflashed it. (I have f800l)

I guess i'm quiet unlucky now in my own case because i am not rooted and no fastboot stuff.
I'm only able to get to Factory Reset menu using the VOL- and POWER BUTTON and releasing the power button and press again POWER BUTTON once lg logo appears.
Also I'm able to get to a SELECT MENU that contains MA-USB(WIFI) DL, POWER OFF, PHONE INFO, BACK by tapping the VOL- or POWER BUTTON like 6 to 7 times repeatedly while in download mode.
Neither of those helping the situation

yet the value of B kept on decreasing now on B59. May that is for the battery? Unknown BATTERY59

HUAWEI P40 Lite Soft brick

Model:Huawei p40 lite
Hello, recently I flashed most propably bad firmware version and now the device seems to be soft bricked.
Black screen, no vibration while pressing power button, nothing.
However when I connect phone to PC, it does detect a device, I download HiSuite and device gets detected as Sooner ADB interface, but via HiSuite shows that recovery is not supported within the model.
ADB is also installed but devices show no devices at all.
When I press power button and volume down it seems to enter another state but device name/driver is the same. No fastboot.
It seems like it is not dead at all but I would have to use somekind of flash tool.
Any ideas would be appreciated
Thanks

Hi, is there a solution?

I need a solution to. Someone?

I am in the same situation. Is there someone to help?

Realme C21Y HardBrick - It says USB Device is faulty but disappears after 2 seconds - I can't enter download mode

I corrupted my phone's root/system/etc files and when I restarted it, it wouldn't turn on and got stuck on the realme logo. i hold my phone vol+ and - and power key and when the realme logo comes up, i release the power key, i think download mode opens, but it usb device is faulty for 1-2 seconds and disappears immediately, meanwhile in device manager it shows unknown device for 1-2 seconds and disappears. After 10-15 seconds there is a usb connection sound but nothing happens. I can send adb commands but I have to confirm the confirmation window but I cant.
Please help me, how can I fix it?

Does adb devices say "unauthorized"?
Are you sure that it's ADB and not fastboot or EDL that is appearing?
You can use usblog.exe to see what's popping up and down. Just run it.

Install Unisoc/Spreadtrum drivers and then see if your device is recognised as a SPD USB device under device manager and let me know here

Renate said:
Does adb devices say "unauthorized"?
Are you sure that it's ADB and not fastboot or EDL that is appearing?
You can use usblog.exe to see what's popping up and down. Just run it.
Click to expand...
Click to collapse
Yes, I get the unauthorized message as below. If I can somehow authorize it, I will be able to enter fastboot mode and flash the stock rom.
mvikrant97 said:
Install Unisoc/Spreadtrum drivers and then see if your device is recognised as a SPD USB device under device manager and let me know here
Click to expand...
Click to collapse
Okay, I'm trying

mvikrant97 said:
Install Unisoc/Spreadtrum drivers and then see if your device is recognised as a SPD USB device under device manager and let me know here
Click to expand...
Click to collapse
Please try a different usb port on your computer.
Don't use USB 3.0 port.
If nothing works then either the phone's usb is malfunctioning or your PC.
Don't use USB extension to connect your phone, plug directly to your computer port.
Also update your PC drivers using driver booster free software and then set restart and try again

mvikrant97 said:
Please try a different usb port on your computer.
Don't use USB 3.0 port.
If nothing works then either the phone's usb is malfunctioning or your PC.
Don't use USB extension to connect your phone, plug directly to your computer port.
Also update your PC drivers using driver booster free software and then set restart and try again
Click to expand...
Click to collapse
I updated with Driver Booster, no luck.
I only tried the front USB ports, do I need the back ones? There are 2 2.0 and 1 3.0 port on the front
The computer is new so I don't think it's defective, the phone is charging and I was using it before it went brick.

I also modified the boot file to install a new GSI and used the following guide.
Spoiler
First, you need to unlock fastbootd:
1. Download the stock ROM version 91: Download and extract the .pac file Link
2. Install the SPD research tool and drivers: GDrive
3. Open it
4. Click on the single gear icon
5. Select the .pac file of the stock rom
6. Wait until it loads
7. Click on the two gear icon
8. Find BOOT in the list
9. Right-click on the path next to it
10. Download here and select boot_r1.img
11. Click OK and then click the arrow icon
12. Turn off your phone
13. Press and hold Power + VolumeDown until you see the text "Downloading"
14. Release the buttons after seeing
15. Wait until you see the text "Passed"
16. Click on the Stop icon, disconnect your phone and turn it on
[/ISPOILER]

@leanord Can you help me?

The 0000/0002 is standard Linux goofiness when you enable USB gadget but you don't initialize anything or add any functions.
This often pops up during boot sequences. It means nothing. It does cause Windows to say "Invalid device".
The 22d9/2769 appears to be normal ADB and since you're getting "unauthorized" shows that everything is fine.
Are you in recovery or regular Android?
Stock recovery usually is ADB secure and you don't have the keys for it.

Renate said:
The 0000/0002 is standard Linux goofiness when you enable USB gadget but you don't initialize anything or add any functions.
This often pops up during boot sequences. It means nothing. It does cause Windows to say "Invalid device".
The 22d9/2769 appears to be normal ADB and since you're getting "unauthorized" shows that everything is fine.
Are you in recovery or regular Android?
Stock recovery usually is ADB secure and you don't have the keys for it.
Click to expand...
Click to collapse
I don't fully understand your question, but I have the stock recovery, I didn't install TWRP, and I installed dotOS 5.2 as GSI. I think I corrupted the fastboot, download mode boot files in the root files. I will take it to the service center, but if you have a solution, you can write, I don't want to give money.

It's gone to stock recovery and you don't have keys.
You need to try buttons to get it into bootloader (fastboot). Or did they disable that?

Renate said:
It's gone to stock recovery and you don't have keys.
You need to try buttons to get it into bootloader (fastboot). Or did they disable that?
Click to expand...
Click to collapse
It may have been disabled or because I corrupted system files.

Wanted? I came, to flash the phone, you do not need to press anything except the volume keys, the power button is only a catalyst, you need to hold it down until the screen goes out, and then just Keep the volume - and flash as usual, the main thing is to keep it immediately plugged into the PC with a ready-made flasher

What I have done:
1. The screen is off
2. I hold down the volume - and power button.
3. The phone vibrates and as soon as the realme logo appears, I plug the usb into the phone and release the power button.
4. The computer receives the message "USB Device not recognized, malfunctioning" and the unknown device is added to the device manager (It doesn't come anymore, I don't know what happened, I installed a lot of drivers.)
5. After 20 seconds, the USB connection sound is heard and the name of my phone is added to the "universal serial bus devices" section of the device manager.

Luuukie said:
What I have done:
1. The screen is off
2. I hold down the volume - and power button.
3. The phone vibrates and as soon as the realme logo appears, I plug the usb into the phone and release the power button.
4. The computer receives the message "USB Device not recognized, malfunctioning" and the unknown device is added to the device manager (It doesn't come anymore, I don't know what happened, I installed a lot of drivers.)
5. After 20 seconds, the USB connection sound is heard and the name of my phone is added to the "universal serial bus devices" section of the device manager.
Click to expand...
Click to collapse
Why are you doing it? You should sit in the flash driver, and not watch how the device is connected, Windows will not have time to see exactly what is connected until you start flashing

leanord said:
Why are you doing it? You should sit in the flash driver, and not watch how the device is connected, Windows will not have time to see exactly what is connected until you start flashing
Click to expand...
Click to collapse
SP Flash Tool doesn't see my device so I can't flash it. If you mean Fastboot, I can't get into it.

By the way, that font that's showing up in my UsbLog is UGLY.
I readjusted things, you can download a new copy that is prettier.

Oh, this is a Unisoc.
I know a lot about Qualcomm, some about Mediatek and almost nothing about Unisoc.
Surely there is some way to get this into Unisoc ROM bootloader mode?
There are either test points or you can disable the eMMC?
If you could pull recovery and mod ro.adb.secure=0 you'd have recovery with ADB at least.

Renate said:
Oh, this is a Unisoc.
I know a lot about Qualcomm, some about Mediatek and almost nothing about Unisoc.
Surely there is some way to get this into Unisoc ROM bootloader mode?
There are either test points or you can disable the eMMC?
If you could pull recovery and mod ro.adb.secure=0 you'd have recovery with ADB at least.
Click to expand...
Click to collapse
I'm sorry, I don't know that much. But if you tell me the steps how to do it, I can do it.

@leanord when installing GSI, I flashed boot_r1.img from your Realme C21Y GSI installation guide, did you disable fastboot or something?