Develop Bugs

Plz help : Boot loop, recovery gone, no system, no recognization ...

Hello all,
I've got a big problem after resetting my LG G4 to default settings.
But let's start chronologically :
My LG G4 (bootloader unlocked, rooted, TWRP, Freedom Rom V7.5) should have been reset for being used by another person.
I started TWRP, did a factory reset and a full wipe and restarted it.
By then, the phone only started in TWRP... REBOOT SYSTEM also caused a TWRP restart.
I tried to fix this by flashing CWM recovery via adb and then reinstall an image.
Connecting via adb succeeded, flash recovery succeeded .....
But now, there isn't any recovery anymore. Entering recovery by POWER /VOL DOWN causes the
same boot loop as starting the system. The LG logo appears and it restarts immediately.
I only can start in download mode via POWER UP / CONNECT, but the phone isn't recognized in adb
or in odin anymore.
Doing a complete STOCK FLASH via LGUP TOOL can't be done due to the tool telling me that the
model is unknown....
Is there any way to bring the phone back to life again ? I'm totally clueless ... Thanks in advance !

Fredelbert said:
Hello all,
I've got a big problem after resetting my LG G4 to default settings.
But let's start chronologically :
My LG G4 (bootloader unlocked, rooted, TWRP, Freedom Rom V7.5) should have been reset for being used by another person.
I started TWRP, did a factory reset and a full wipe and restarted it.
By then, the phone only started in TWRP... REBOOT SYSTEM also caused a TWRP restart.
I tried to fix this by flashing CWM recovery via adb and then reinstall an image.
Connecting via adb succeeded, flash recovery succeeded .....
But now, there isn't any recovery anymore. Entering recovery by POWER /VOL DOWN causes the
same boot loop as starting the system. The LG logo appears and it restarts immediately.
I only can start in download mode via POWER UP / CONNECT, but the phone isn't recognized in adb
or in odin anymore.
Doing a complete STOCK FLASH via LGUP TOOL can't be done due to the tool telling me that the
model is unknown....
Is there any way to bring the phone back to life again ? I'm totally clueless ... Thanks in advance !
Click to expand...
Click to collapse
You tried xdadevelopers search box ?

RuedasLocas said:
You tried xdadevelopers search box ?
Click to expand...
Click to collapse
Not yet actually . Can't find it under TOOLS . Is this available yet ?

RuedasLocas said:
You tried xdadevelopers search box ?
Click to expand...
Click to collapse
Sorry, I misunderstood your answer ...
Searching for related posts using the keywords 'boot loop' or 'recovery gone' really doesn't help me ...
As I said, I can't use
- Recovery
- adb
- FlashTool
- odin
anymore in any way . All posts I've found suggest things related to them ...
Most bootloop topics recommend using one of them in different ways ...
Is there a tool not mentioned yet that will help me with my problem ?
As I said, thre search function does'nt bring me to a clue

Fredelbert said:
Sorry, I misunderstood your answer ...
Searching for related posts using the keywords 'boot loop' or 'recovery gone' really doesn't help me ...
As I said, I can't use
- Recovery
- adb
- FlashTool
- odin
anymore in any way . All posts I've found suggest things related to them ...
Most bootloop topics recommend using one of them in different ways ...
Is there a tool not mentioned yet that will help me with my problem ?
As I said, thre search function does'nt bring me to a clue
Click to expand...
Click to collapse
Connect your device to the computer and see how is detected by "Windows Device Manager".
If not as it should, try to uninstall all related hardware drivers, like modem, adb device, whatever...
Reinstall "LGMobileDriver_WHQL_Ver_4.2.0"
Reinstall "LGUSBModemDriver_Eng_WHQL_Ver_4.9.4_All"
Reinstall "Minimal ADB and Fastboot"
Reboot your computer and reconnect yout device. It should work.

RuedasLocas said:
Connect your device to the computer and see how is detected by "Windows Device Manager".
If not as it should, try to uninstall all related hardware drivers, like modem, adb device, whatever...
Reinstall "LGMobileDriver_WHQL_Ver_4.2.0"
Reinstall "LGUSBModemDriver_Eng_WHQL_Ver_4.9.4_All"
Reinstall "Minimal ADB and Fastboot"
Reboot your computer and reconnect yout device. It should work.
Click to expand...
Click to collapse
When I go to the download mode (the only one starting) it is shown as
LGE AndroidNet USB Serial Port (COM11)
My other LG G4 is working fine with all of the tools and the drivers on my PC (Win 10 64)
and also on my notebook (WIN 10 64) and so did the other one before my attempt of changing the recovery ...

Fredelbert said:
Hello all,
I've got a big problem after resetting my LG G4 to default settings.
But let's start chronologically :
My LG G4 (bootloader unlocked, rooted, TWRP, Freedom Rom V7.5) should have been reset for being used by another person.
I started TWRP, did a factory reset and a full wipe and restarted it.
By then, the phone only started in TWRP... REBOOT SYSTEM also caused a TWRP restart.
I tried to fix this by flashing CWM recovery via adb and then reinstall an image.
Connecting via adb succeeded, flash recovery succeeded .....
But now, there isn't any recovery anymore. Entering recovery by POWER /VOL DOWN causes the
same boot loop as starting the system. The LG logo appears and it restarts immediately.
I only can start in download mode via POWER UP / CONNECT, but the phone isn't recognized in adb
or in odin anymore.
Doing a complete STOCK FLASH via LGUP TOOL can't be done due to the tool telling me that the
model is unknown....
Is there any way to bring the phone back to life again ? I'm totally clueless ... Thanks in advance !
Click to expand...
Click to collapse
What modem and bootloader (is it v29a nougat beta?)
FWUL is good (https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755) as it avoids any driver issues - it is a bootable linux distro with LG tools built in.
In there, SALT can tell you what your bootloader stack is. Let me know as the version depends on the steps you should take next

ThePiGuy said:
What modem and bootloader (is it v29a nougat beta?)
FWUL is good (https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755) as it avoids any driver issues - it is a bootable linux distro with LG tools built in.
In there, SALT can tell you what your bootloader stack is. Let me know as the version depends on the steps you should take next
Click to expand...
Click to collapse
OK, it will take some time downloading and trying it. I'll be back when having results
THANX

ThePiGuy said:
What modem and bootloader (is it v29a nougat beta?)
FWUL is good (https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755) as it avoids any driver issues - it is a bootable linux distro with LG tools built in.
In there, SALT can tell you what your bootloader stack is. Let me know as the version depends on the steps you should take next
Click to expand...
Click to collapse
I've started it and also I've found SALT.
Starting SALT and connecting in Download Mode gives me following informations ( haven't found informations about bootloader stack) :
{
"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"
}

Fredelbert said:
I've started it and also I've found SALT.
Starting SALT and connecting in Download Mode gives me following informations ( haven't found informations about bootloader stack) :
Click to expand...
Click to collapse
Good enough for me
Look at the system one - It says v29a.
So what I want you to try now. Power off your phone. Then, hold power and volume up and hopefully it will boot into the bootloader (at which point you can reflash twrp from twrp.me - cwm is completely outdated)

Fredelbert said:
When I go to the download mode (the only one starting) it is shown as
LGE AndroidNet USB Serial Port (COM11)
My other LG G4 is working fine with all of the tools and the drivers on my PC (Win 10 64)
and also on my notebook (WIN 10 64) and so did the other one before my attempt of changing the recovery ...
Click to expand...
Click to collapse
Mine when I connect to PC (USB2), option "Only Charge" on the phone and turn ON, is shown in Device manager as "Android device/ Android Sooner Single ADB Interface"
Also as "Device/G4"
After change the option "Only Charge" to "Multimidia Devica (MTP)", is shown as "Android Device/LGE Mobile ADB Interface".
Also as "Portable Device/G4", and, "Modems/LGE Mobile USB Modem".
In "Firmware Update" mode, comes as "LGE AndroidNet USB Serial Port (COM4)" and also as "Modems/ LGE AndroidNet USB Modem".
If the phone had v29a installed, you need v20p.kdz and respective "8994.dll", you can extract it from the .kdz. Than you can use LGUP.

ThePiGuy said:
Good enough for me
Look at the system one - It says v29a.
So what I want you to try now. Power off your phone. Then, hold power and volume up and hopefully it will boot into the bootloader (at which point you can reflash twrp from twrp.me - cwm is completely outdated)
Click to expand...
Click to collapse
Unfortunately it doesn't ... Same as normal start :
I did
REMOVE / INSERT BATTERY
POWER / VOL UP same time
then
short flash of BOOTLOADER STATE : BOOTLOADER UNLOCKED including LG Logo, then immediate reboot

Fredelbert said:
Unfortunately it doesn't ... Same as normal start :
I did
REMOVE / INSERT BATTERY
POWER / VOL UP same time
then
short flash of BOOTLOADER STATE : BOOTLOADER UNLOCKED including LG Logo, then immediate reboot
Click to expand...
Click to collapse
Strange. Sounds like you may have a mixture of v29 and v20
Try pulling the battery. Then put it back in, hold vol down and plug in the usb cable and keep holding vol down.

ThePiGuy said:
Strange. Sounds like you may have a mixture of v29 and v20
Try pulling the battery. Then put it back in, hold vol down and plug in the usb cable and keep holding vol down.
Click to expand...
Click to collapse
Look at the firmware(laf): v20g
That's his bootloader stack
He flashed freedom ROM which has v29a as base that's why system shows v29a.
Sent from my LG-H815 using XDA Labs

ThePiGuy said:
Strange. Sounds like you may have a mixture of v29 and v20
Try pulling the battery. Then put it back in, hold vol down and plug in the usb cable and keep holding vol down.
Click to expand...
Click to collapse
That has no effect, same behaviour as before

RuedasLocas said:
Mine when I connect to PC (USB2), option "Only Charge" on the phone and turn ON, is shown in Device manager as "Android device/ Android Sooner Single ADB Interface"
Also as "Device/G4"
After change the option "Only Charge" to "Multimidia Devica (MTP)", is shown as "Android Device/LGE Mobile ADB Interface".
Also as "Portable Device/G4", and, "Modems/LGE Mobile USB Modem".
In "Firmware Update" mode, comes as "LGE AndroidNet USB Serial Port (COM4)" and also as "Modems/ LGE AndroidNet USB Modem".
If the phone had v29a installed, you need v20p.kdz and respective "8994.dll", you can extract it from the .kdz. Than you can use LGUP.
Click to expand...
Click to collapse
Sorry, as I mentioned, LGUP can't be used because the tool reject the phone selection because it's "unknown"

Fredelbert said:
Sorry, as I mentioned, LGUP can't be used because the tool reject the phone selection because it's "unknown"
Click to expand...
Click to collapse
Do you have the right "8994.dll" ???
Because to get out from v29a you need the v20p.kdz and the ""8994.dll"" from it. Thats probably why your phone is "unknown"

RuedasLocas said:
Do you have the right "8994.dll" ???
Because to get out from v29a you need the v20p.kdz and the ""8994.dll"" from it. Thats probably why your phone is "unknown"
Click to expand...
Click to collapse
That might be... But how can I make neccessary modifications, when I get no access to the phone at all...

Fredelbert said:
That might be... But how can I make neccessary modifications, when I get no access to the phone at all...
Click to expand...
Click to collapse
You just need the right "8994.dll" on the folder "C:\Program Files (x86)\LG Electronics\LGUP\model\8994", replace the one that you have there with the one extracted from the v20p.kdz.
After that run LGUP.

RuedasLocas said:
You just need the right "8994.dll" on the folder "C:\Program Files (x86)\LG Electronics\LGUP\model\8994", replace the one that you have there with the one extracted from the v20p.kdz.
After that run LGUP.
Click to expand...
Click to collapse
OK, then I will search for the mentioned Kdz file and download it. I will be able to continue tomorrow. Thanks to everybody so far. I will post the result as fast as I can

The current image(boot/recovery) have been destroyed and can not boot.

Hello.
I tried to lock back the bootloader, and after executing
PHP:
fastboot flashing lock
got an 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"
}
Then I faced a similar problem described in this topic https://forum.xda-developers.com/re...-3-pro-boot-recovery-destroyed-t3938481/page3
When you turn on the phone an error pops up for 20 seconds and then phone reboots and everything goes in a circle.
If you press the power button once, the reboot process stops and the phone turns off.
I tried to enter fastboot mode by pressing the power + volume button -
But I didn't succeed.
Can you tell me what I'm doing wrong ?

You should have return the stock fully before locking.
Try to unlock again and then flash original firmware fully

kkffiirr said:
You should have return the stock fully before locking.
Try to unlock again and then flash original firmware fully
Click to expand...
Click to collapse
Thanks for the answer, but unfortunately due to this error fastboot does not load.
If you can tell me how I can flash the phone I will be very grateful.
I would not like to contact an unofficial service...

I guess you don't have recovery as well...
Well, we need to dig in Chinese forums to find edl option, since I don't see any other way.

kkffiirr said:
I guess you don't have recovery as well...
Well, we need to dig in Chinese forums to find edl option, since I don't see any other way.
Click to expand...
Click to collapse
Before lock, I installed TWRP, but idk if it's still there.
UMF cable will help me ?

Me i too i got same your problem i bricked my realme x2 i still didnt find the solution to flash it again

Maybe contact service center

Try booting with both VolUp and VolDown pressed. The screen should be black, but computer should see 9008 device (Qualcomm Download mode). If it works, search through Internet for Snapdragon 730G programmer and proper boot files.
Another option is devices alike Medusa Box; they seem to have underground connections with manufactors, they may provide a solution too.
EDIT. Thanks to the clarification from @T1MOXA, you can enter EDL mode by holding VolUp and VolDown and plugging the switched off phone to a computer.

first confirm that your device is fully turn off and connect a usb cable to the PC by pressing Vol (-) at the same time and you will be in fastboot mood.

yakovpol said:
Try booting with both VolUp and VolDown pressed. The screen should be black, but computer should see 9008 device (Qualcomm Download mode). If it works, search through Internet for Snapdragon 730G programmer and proper boot files.
Another option is devices alike Medisa Box; they seem to have underground connections with manufactors, they may provide a solution too.
Click to expand...
Click to collapse
I've tried this option before, but it led me to the same error screen.
I turned off the phone with a single press of the power button, then pressed all the buttons at the same time.

razu031 said:
first confirm that your device is fully turn off and connect a usb cable to the PC by pressing Vol (-) at the same time and you will be in fastboot mood.
Click to expand...
Click to collapse
I just got the same error.
When you connect the cable, the phone boots with the same error.

narshi shukla said:
Maybe contact service center
Click to expand...
Click to collapse
Unofficial ?
They too bad in my country.
They can easily make it worse.

I can buy a UMF cable, but whether it will help me I do not know.
What do you think ?

Good news...
My phone is defined on the PC as "Qualcomm HS-USB QDLoader 9008 (COM 5)" by connecting and pressing all the volume keys.
Only I don't know if it gives me anything and what to do next...

T1MOXA said:
Good news...
My phone is defined on the PC as "Qualcomm HS-USB QDLoader 9008 (COM 5)" by connecting and pressing all the volume keys.
Only I don't know if it gives me anything and what to do next...
Click to expand...
Click to collapse
Most phones will be able to flash in this mode using qfil tool,
But first you need to find necessary firmware, idk if stock rom downloaded from official site will work or not, maybe fastboot one will work.
This mode is called emergency download mode (edl).
But pls do a lil research as its a newly launched device and you can easily mess it up.
BTW exact same error(boot recovery destroyed) is common error on realme Phones and it can be fixed by flashing vbmeta.img using fastboot.

See attached image for reference only
The 1kb vbmeta is modified to bypass boot verification.
Idk if such vbmeta is available for x2.
If not then flashing stock vbmeta might work.

T1MOXA said:
Hello.
I tried to lock back the bootloader, and after executing
PHP:
fastboot flashing lock
got an error
Click to expand...
Click to collapse
I have the same problem. On 4pda there is a firmware for MsmDownload Tool and the tool itself, but it requires a username and password. Are there alternative options to restore your phone?

Problem: The current image have been destroyed and can not boot
Dear friends, I'm using Realme X2.
Last day, I try bootloader unlock my device. Bootloader unlocked successfully and twrp also successfully installed.. but after I'll try boot, but the is not boot.
The pop-up message shows "THE CURRENT IMAGE HAVE BEEN DESTROYED AND CAN NOT BOOT".. so please me how to solve this problem .
My mobile model number : RMX1992
please help me

Iamsanthoshravi said:
Dear friends, I'm using Realme X2.
Last day, I try bootloader unlock my device. Bootloader unlocked successfully and twrp also successfully installed.. but after I'll try boot, but the is not boot.
The pop-up message shows "THE CURRENT IMAGE HAVE BEEN DESTROYED AND CAN NOT BOOT".. so please me how to solve this problem .
My mobile model number : RMX1992
please help me
Click to expand...
Click to collapse
Look friend i had the same problem and i fix it u have to download the firmware RMX1991 not ozp file then u have to buy the password of the firmware there are sone website they ask you to install teamviewer because thet gonna flash your phone online ok friend i did as i mentioned and i fixed so there is no other way to fix it i cant put the link of firmwares because last time xda warned me

I got same
Hey bro can you fix your phone?
Today I experience same.
What can I do now?

Problem Oneplus 5T ... stop work and I can't install any ROM.

Good afternoon people,
I'm having problems with my wife's Oneplus 5T phone.
He thinks it has undergone some updating because she said it stopped working out of nowhere.
1 - The cell phone performs the initialization boot and remains only with this light on and the black screen.
View attachment 5053157 View attachment 5053159 View attachment 5053161
2 - I can't access ADB to install TWRP or even enter the root folder to put the ROM and install it directly.
I don't think I had the developer options enabled:
* Enable USB debugging
* OEM Unlocking
3 - I tried to install the ROM of the Oneplus website through ADB Sideload. Completes 100%, but has the same problem does not start and keeps this light on.
OnePlus5TOxygen_43_OTA_054_all_2002242025_81ae0ff9d1c34a3f.zip
Acesse only by ADB Sideload
View attachment 5053165
100% Concluded
View attachment 5053167
Pleas could you help me how can I solve this problem?

Hey there!
I had exactly the same thing with Paranoid Android.
What i did is go to TWRP, save everything in a folder on my PC, and then factory reset the phone.
After doing that, i could install OxygenOS and Paranoid Android (PA requires OxygenOS vendor but who cares, you just want to install OxygenOS) and boot without this annoying LED.

XavNotFound said:
Hey there!
Hi @XavNotFound
I had exactly the same thing with Paranoid Android.
What i did is go to TWRP, save everything in a folder on my PC, and then factory reset the phone.
After doing that, i could install OxygenOS and Paranoid Android (PA requires OxygenOS vendor but who cares, you just want to install OxygenOS) and boot without this annoying LED.
Click to expand...
Click to collapse
I don't have the TWRP installed. And my wife didn't do this:
I don't think I had the developer options enabled:
* Enable USB debugging
* OEM Unlocking
I tried erase the data, wipe everything and don't boot. Continue in this black screen and only one light open.
How can I acess or instal TWRP? Please help!
Could you help me?

marciohanderson said:
I don't have the TWRP installed. And my wife didn't do this:
I don't think I had the developer options enabled:
* Enable USB debugging
* OEM Unlocking
How can I acess or instal TWRP? Please help!
I tried erase the data, wipe everything and don't boot. Continue in this black screen and only one light open.
Click to expand...
Click to collapse
I misread the fact that you don't have the developer options enabled, sorry about that.
You could unlock the bootloader of her phone, but she'll lose her data.
Have you tried some of the unbrick tools ?
Cheers.

XavNotFound said:
I misread the fact that you don't have the developer options enabled, sorry about that.
You could unlock the bootloader of her phone, but she'll lose her data.
Have you tried some of the unbrick tools ?
Cheers.
Click to expand...
Click to collapse
I have already try to erase .... She don't have this problem. She only needs that the cell phone works again.
I don't know how to unlock the bootloader, since she didn't have the developer opions enabled. Could you help me?
I don't have this unbrick tools :crying: .... I try everything that I saw on You Tube.
1 - Hard Reset OnePlus 5T
2 - Use ADB (don't work because i don't have the developer acess, and ADB only give me option ADB SIDELOAD as I post on the pictures).
3 - Only acess fast boot ... but is locked as the photos.
PLEASE HELP ME .... I don't know what to do ! :crying:

marciohanderson said:
I have already try to erase .... She don't have this problem. She only needs that the cell phone works again.
I don't know how to unlock the bootloader, since she didn't have the developer opions enabled. Could you help me?
I don't have this unbrick tools :crying: .... I try everything that I saw on You Tube.
1 - Hard Reset OnePlus 5T
2 - Use ADB (don't work because i don't have the developer acess, and ADB only give me option ADB SIDELOAD as I post on the pictures).
3 - Only acess fast boot ... but is locked as the photos.
PLEASE HELP ME .... I don't know what to do ! :crying:
Click to expand...
Click to collapse
Don't worry, i've seen cases that are much worse than this!
I don't know if you have adb and fastboot drivers on your pc but if you don't, install them here: Adb and fastboot installer
Then, restart your phone in fastboot mode, connect it to your pc, start the command line on the computer and try to do the command "fastboot oem unlock"
If it works, maybe try to install TWRP by downloading it on the official website and doing "fastboot flash recovery [path-to-file]" and then boom, you can install roms on it.
If i doesn't work, you should try the unbrick tools there: Unbrick Tools. There's videos to help you on how to unbrick, and it will install an old update but you can update to Pie or 10 after it's done.

XavNotFound said:
Don't worry, i've seen cases that are much worse than this!
I don't know if you have adb and fastboot drivers on your pc but if you don't, install them here: Adb and fastboot installer
Then, restart your phone in fastboot mode, connect it to your pc, start the command line on the computer and try to do the command "fastboot oem unlock"
If it works, maybe try to install TWRP by downloading it on the official website and doing "fastboot flash recovery [path-to-file]" and then boom, you can install roms on it.
If i doesn't work, you should try the unbrick tools there: Unbrick Tools. There's videos to help you on how to unbrick, and it will install an old update but you can update to Pie or 10 after it's done.
Click to expand...
Click to collapse
I'm so dumb I can't install the Qualcom drivers. I don't know why. As you can see in the photo.
View attachment 5054141
1 - I don't have this options able:
* Enable USB debugging
* OEM Unlocking
2 - I install the ADB and minimal_adb_fastboot_v1.4.3_setup
The cell open in ADB SIDELOAD
{
"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"
}
View attachment 5054147 View attachment 5054149 View attachment 5054151
3 - I'm trying to download the Unbricking Toll .... but if I can't see the Qualcomm drivers installed I can't use.
3 - Could you help me? :crying: I don't know if you can help online on Skype. Please say YES :angel:
I only want the phone work again. Because I don't know what to do now.
I saw a lot of videos tutorias on YT and nothing.

marciohanderson said:
I'm so dumb I can't install the Qualcom drivers. I don't know why. As you can see in the photo.
View attachment 5054141
1 - I don't have this options able:
* Enable USB debugging
* OEM Unlocking
2 - I install the ADB and minimal_adb_fastboot_v1.4.3_setup
The cell open in ADB SIDELOAD
View attachment 5054145 View attachment 5054147 View attachment 5054149 View attachment 5054151
3 - I'm trying to download the Unbricking Toll .... but if I can't see the Qualcomm drivers installed I can't use.
3 - Could you help me? :crying: I don't know if you can help online on Skype. Please say YES :angel:
I only want the phone work again. Because I don't know what to do now.
I saw a lot of videos tutorias on YT and nothing.
Click to expand...
Click to collapse
Don't worry, you're not dumb, you're just new to this
Put your phone in fastboot mode by pressing volume up and the power button at the same time, and while your phone is connected to your pc, launch "fastboot oem unlock " from the command line.
Report here what happens after that.
I'll explain a little bit later what you need to do with Qualcomm drivers as they tend to be annoying.
Also, i don't use Skype, sorry about that.

XavNotFound said:
Don't worry, you're not dumb, you're just new to this
Put your phone in fastboot mode by pressing volume up and the power button at the same time, and while your phone is connected to your pc, launch "fastboot oem unlock " from the command line.
Report here what happens after that.
I'll explain a little bit later what you need to do with Qualcomm drivers as they tend to be annoying.
Also, i don't use Skype, sorry about that.
Click to expand...
Click to collapse
I tried to execute the commands in both ADB and Minimal ADB and was not successful according to the photos.
If I had TWRP installed I would have already solved it.
You can help me through TeamView, Zoom or any other tool ... even a smoke signal ... see the level of my despair :crying: heheh

marciohanderson said:
I tried to execute the commands in both ADB and Minimal ADB and was not successful according to the photos.
View attachment 5054179View attachment 5054181 View attachment 5054183
If I had TWRP installed I would have already solved it.
You can help me through TeamView, Zoom or any other tool ... even a smoke signal ... see the level of my despair :crying: heheh
Click to expand...
Click to collapse
Sorry, can't do. I can send you a homing pigeon if you want to.
Just to be sure, have you restarted your computer with driver verification turned off so you can install qualcomm drivers ? (there's a tutorial on how to do it there: Unbricking tool).
It's the most hardcore thing to do, but it's also the most effective one, so be sure to follow every step carefully.
If that doesn't work, i don't know how to help you further than that and i'll let my fellow xda comrades help you.

XavNotFound said:
Sorry, can't do. I can send you a homing pigeon if you want to.
Just to be sure, have you restarted your computer with driver verification turned off so you can install qualcomm drivers ? (there's a tutorial on how to do it there: Unbricking tool).
It's the most hardcore thing to do, but it's also the most effective one, so be sure to follow every step carefully.
If that doesn't work, i don't know how to help you further than that and i'll let my fellow xda comrades help you.
Click to expand...
Click to collapse
1 - I try to do the process to install the Qualcomm Drivers.
I found this installer QDLoader HS-USB Driver_64bit_Setup
2 - I don't know what happened, the cell phone doesn't turn on now and I can't get into the Bootloader .... pressing Vol + and Power ..... nor FAST Boot ... pressing VOL - and Power.
Have you seen anything like this? What should I do?

marciohanderson said:
1 - I try to do the process to install the Qualcomm Drivers.
I found this installer QDLoader HS-USB Driver_64bit_Setup
2 - I don't know what happened, the cell phone doesn't turn on now and I can't get into the Bootloader .... pressing Vol + and Power ..... nor FAST Boot ... pressing VOL - and Power.
Have you seen anything like this? What should I do?
Click to expand...
Click to collapse
I don't really think that's the good drivers, and that never happened to me.
Try to press power for 10 seconds and your phone will restart, maybe retry the unbrick tool after that. If it doesn't restart, i don't know.

XavNotFound said:
I don't really think that's the good drivers, and that never happened to me.
Try to press power for 10 seconds and your phone will restart, maybe retry the unbrick tool after that. If it doesn't restart, i don't know.
Click to expand...
Click to collapse
I tried everything and now nothing ... before open that two options FAST BOOT and Bootloader.
Tried:
1 - press power for 10 seconds
2 - press power for 10 seconds and VOL +
3 - press power for 10 seconds and VOL -
I'm so sad :crying::crying::crying::crying::crying:
Because is a very good phone and give this headache.
If someone could help .... I'll thank you very much.

Someone could HELP ME?

How To Guide [CLOSED] Unbrick your phone with EDL mode (no access to fastboot)

Hello guys
Today I'm going to tell you about how to bring your phone back to life when it is bricked and also you don't have access to fastboot.
few days ago when I wanted to turn back to Xiaomi EU weekly ROM from HOS, the fastboot script which is provided by Xiaomi EU team in order to flash the ROM gave me to many errors when it was trying to flash "super" partition and mistakenly I had rebooted my phone and then I realized the the phone is dead, it didn't show any sign of life (I mean no vibration, no fastboot and no screen light, literary nothing at all).
After some research I found out that Qualcomm powered devices have something called EDL which is stand for (Emergency Download mode) and it is there to flash fastboot ROMs when you don't have access to fastboot (as matter of fact EDL mode is one level lower than fastboot and let you to access the phone when it is dead and also it cannot be erased with fastboot).
Important: with this tutorial you can fix your phone by yourself and also there will be no need to pay anyone with authorized xiaomi account to connect to your personal computer and do the flash for you.
Lets head to tutorial:
Requirements:
1- A windows system
2- EDL drivers which can be found here
3- Original USB cable
4- Xiaomi pro tool which can be found here <Moderator Edit>: warning, comes up as Trojan:Script/Wacatac.B!ml in Windows Defender.
5- Fastboot ROM for your phone which can be found here
method:
1- first you need to boot your phone into EDL mode (you can do this by holding volume up button and connect your phone with its USB cable and check "device manager" on windows to check if your PC recognized your phone or not. you should see "Qualcomm HS-USB QDLoader 9008" under "ports" section (look at below picture)
{
"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"
}
If it didn't showed up follow this tutorial to install drivers
2- then open the Xiaomi pro tool,register on it then change the "select model" to your phone model (in this case POCO F3(Alioth)) and next change port to EDL booted device (should be like this: Qualcomm HS-USB QDLoader 9008)
3- <Moderator Edit>: not allowed
4- go to "xiaomi firmware flasher" page on xiaomi pro tool app and locate the downloaded ROM (you should locate "image" folder (downloaded ROM/images)) after that you will see that it loaded files correctly.
5- Disconnect your phone and hold power button for 15 second then press and hold volume up button and connect your phone with its USB cable to boot to EDL mode again and check thee "ports" on the tool app again (it should be same as step 2)
6- Click on flash device which is on the bottom right of the xiaomi pro tool app then it will ask for using your credits in order to flash device that you should click on "yes" button and after that you will see that flash processing is going on.
7- The tool will reboot your phone automatically but if you find your phone completely dead after the flashing process(not responding to anything and not going to EDL mode again (which was my case)) just don't panic, your phone maybe out of charge so just connect your phone to a charger and wait, after some minutes you will see the battery icon on your device.
8- hooray, you made it. you can enjoy your phone now

This is sweet, how much are the credits?

11214 said:
This is sweet, how much are the credits?
Click to expand...
Click to collapse
It depends on your country but it is about 1 US dollar per credit

raminta said:
It depends on your country but it is about 1 US dollar per credit
Click to expand...
Click to collapse
That's great, much better than the €25 I had to pay.
Thanks for the guide.

raminta said:
Hello guys
Today I'm going to tell you about how to bring your phone back to life when it is bricked and also you don't have access to fastboot.
few days ago when I wanted to turn back to Xiaomi EU weekly ROM from HOS, the fastboot script which is provided by Xiaomi EU team in order to flash the ROM gave me to many errors when it was trying to flash "super" partition and mistakenly I had rebooted my phone and then I realized the the phone is dead, it didn't show any sign of life (I mean no vibration, no fastboot and no screen light, literary nothing at all).
After some research I found out that Qualcomm powered devices have something called EDL which is stand for (Emergency Download mode) and it is there to flash fastboot ROMs when you don't have access to fastboot (as matter of fact EDL mode is one level lower than fastboot and let you to access the phone when it is dead and also it cannot be erased with fastboot).
Important: with this tutorial you can fix your phone by yourself and also there will be no need to pay anyone with authorized xiaomi account to connect to your personal computer and do the flash for you.
Lets head to tutorial:
Requirements:
1- A windows system
2- EDL drivers which can be found here
3- Original USB cable
4- Xiaomi pro tool which can be found here
5- Fastboot ROM for your phone which can be found here
method:
1- first you need to boot your phone into EDL mode (you can do this by holding volume up button and connect your phone with its USB cable and check "device manager" on windows to check if your PC recognized your phone or not. you should see "Qualcomm HS-USB QDLoader 9008" under "ports" section (look at below picture)
View attachment 5547309
If it didn't showed up follow this tutorial to install drivers
2- then open the Xiaomi pro tool,register on it then change the "select model" to your phone model (in this case POCO F3(Alioth)) and next change port to EDL booted device (should be like this: Qualcomm HS-USB QDLoader 9008)
View attachment 5547333
3- You need to buy at least 5 credits in order to flash ROM on your device you can buy it on the internet just google "credits for xiaomi pro tool" (Iranian users can use this site to buy credits)
4- go to "xiaomi firmware flasher" page on xiaomi pro tool app and locate the downloaded ROM (you should locate "image" folder (downloaded ROM/images)) after that you will see that it loaded files correctly.
View attachment 5547349
5- Disconnect your phone and hold power button for 15 second then press and hold volume up button and connect your phone with its USB cable to boot to EDL mode again and check thee "ports" on the tool app again (it should be same as step 2)
6- Click on flash device which is on the bottom right of the xiaomi pro tool app then it will ask for using your credits in order to flash device that you should click on "yes" button and after that you will see that flash processing is going on.
7- The tool will reboot your phone automatically but if you find your phone completely dead after the flashing process(not responding to anything and not going to EDL mode again (which was my case)) just don't panic, your phone maybe out of charge so just connect your phone to a charger and wait, after some minutes you will see the battery icon on your device.
8- hooray, you made it. you can enjoy your phone now
Click to expand...
Click to collapse
that's absolutely i done but for those people who don't have access to buy credit can search patched hose but till now no one has patched for our device poco f3. for patching it requires reverse engineering skill which i don't have.

why are the credits needed? this program is going to be likely used by desperate users that destroyed the phone and they even have to pay? i get the developers need money but its just bad...

pedrosantosobral said:
why are the credits needed? this program is going to be likely used by desperate users that destroyed the phone and they even have to pay? i get the developers need money but its just bad...
Click to expand...
Click to collapse
The only other option is paying €25 to a random person on the net to tunnel into your PC and do the job for you.

Nice

It's difficult to trust these random programs, but desperate users with bricked phones don't have many other options...
I had to pay 25€ to get mine running again. The fact that you have to pay sucks. It shouldn't be like that.

I paid more than $30 to random person I found on youtube and I still had to disassemble my phone myself to put it on EDL mode (was it really necessary? - since my phone has an unlocked bootloader).

WARNING! Xiaomi Tools Pro contains a backdoor virus
Win32/Bladabindi!ml - Virus​
This will allow the hacker to gain control of your computer and potentially draining your bank accounts/bitcoin.
you have been warned.
I have always bought Xiaomi Products but after reading all the trouble that you have to go through and zero customer support with most software infected by ****ty backdoors, I have to go back to some oneplus or pixel or mainstream phones.

Hello everyone,
I just wanted to say I followed the instructions above and it worked fine. I paid 10€ for 10 credits at <Moderator Edit>: (removed) and I used the tool and everything went smooth with my poco f3. Just like it says in the tutorial, if it does not reboot automatically, just charge your phone for a few minutes and voilá. Just wanted to leave my input in here, so if anyone is in this situation, you CAN fix your phone.

<Moderator Edit>: Thread closed. @raminta look for my PM shortly.

Question [HELP] Unbrick an almost completely bricked phone.

Hey.
This post is my last faith in this device.
So basically I was about to flash partitions, but when I tried to go into fastbootd to flash the critical stuff, after the "fastboot reboot fastboot" command my phone was completely got bricked. I already tried every type of key combinations, the screen was black the entire time, and the phone won't even vibrates.
The only signal of it's being alive, when I plug it and press pwr + vol up, windows gives the sound of a connected/disconnected device, and the MsM tool shows that too. At this point, i was sure about the MsM tool and didn't panicked, I knew that I can almost always unbrick the phone with that... Hmm... This time it was different, because every time I get an error: "Sahara communication failed", or "Param preload", and I cant even do anything. Currently the phone was completely dead.
If you have any idea how to fix that Please let me know! 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"
}

pmppm said:
Hey.
This post is my last faith in this device.
So basically I was about to flash partitions, but when I tried to go into fastbootd to flash the critical stuff, after the "fastboot reboot fastboot" command my phone was completely got bricked. I already tried every type of key combinations, the screen was black the entire time, and the phone won't even vibrates.
The only signal of it's being alive, when I plug it and press pwr + vol up, windows gives the sound of a connected/disconnected device, and the MsM tool shows that too. At this point, i was sure about the MsM tool and didn't panicked, I knew that I can almost always unbrick the phone with that... Hmm... This time it was different, because every time I get an error: "Sahara communication failed", or "Param preload", and I cant even do anything. Currently the phone was completely dead.
If you have any idea how to fix that Please let me know! Thanks.
View attachment 5788047
Click to expand...
Click to collapse
From the image you posted, it looks like you are using the wrong MSM version. "Device not match image".......

TheGhost1951 said:
From the image you posted, it looks like you are using the wrong MSM version. "Device not match image".......
Click to expand...
Click to collapse
I used this exact version on this phone like 2 days ago, I dont think it is a version problem, but thanks for the help!

And it is pretty interesting.. As far as i know EDL connection only alive for 5-10 sec, but currently MsM tool shows Connected until my phone was plugged in (even after refreshing it)

pmppm said:
I used this exact version on this phone like 2 days ago, I dont think it is a version problem, but thanks for the help!
Click to expand...
Click to collapse
Just like the other posted said. If it says that error, it means that your device ID is different. Did you possibly use the India MSM which would change your device ID and not allow you to use the one you were using before? You can also try unchecking sha265check and check use lite firehose and see if it works that way.

TheSayaMan said:
Just like the other posted said. If it says that error, it means that your device ID is different. Did you possibly use the India MSM which would change your device ID and not allow you to use the one you were using before? You can also try unchecking sha265check and check use lite firehose and see if it works that way.
Click to expand...
Click to collapse
Okay so basically, you're both right. I got the Global version, but with the correct MsM version for that did not worked. The solution was to use the Indian version to unbrick it, then ofc switch back to the global. I took this idea from this post, It's seemed so idiot to do it that way, but I had nothing to lose. Thanks again!

pmppm said:
Okay so basically, you're both right. I got the Global version, but with the correct MsM version for that did not worked. The solution was to use the Indian version to unbrick it, then ofc switch back to the global. I took this idea from this post, It's seemed so idiot to do it that way, but I had nothing to lose. Thanks again!
Click to expand...
Click to collapse
Once you used the Indian MSM, then to go global you have to install the updater tool from Google Play store to choose the version you want and install it that way. I believe.....

TheGhost1951 said:
Once you used the Indian MSM, then to go global you have to install the updater tool from Google Play store to choose the version you want and install it that way. I believe.....
Click to expand...
Click to collapse
I don't believe it's available in play store, have to Google search for it but otherwise your right, once you use the India MSM, your device ID is permanently changed and can no longer use the reg MSM for the device.

TheSayaMan said:
I don't believe it's available in play store, have to Google search for it but otherwise your right, once you use the India MSM, your device ID is permanently changed and can no longer use the reg MSM for the device.
Click to expand...
Click to collapse
Would this not work?

I am not sure how OnePlus implements it, but many devices have a Qualcomm USB mode or "Emergency Download Mode" for performing a low level reflash of basic firmware such as the bootloader. Most often, when a device screen doesn't come on, but it vibrates and a PC shows a connected device, this is the case - the PC has detected the QUSB mode.
Unfortunately, Qualcomm does not make their Qualcomm Product Support Tool available to the public, and most OEMs do not provide the necessary binaries to restore the bootloader. The device cannot be repaired or restored without these tools, unless the mainboard is replaced. Unfortunately in this case, I believe that is your only option.

V0latyle said:
I am not sure how OnePlus implements it, but many devices have a Qualcomm USB mode or "Emergency Download Mode" for performing a low level reflash of basic firmware such as the bootloader. Most often, when a device screen doesn't come on, but it vibrates and a PC shows a connected device, this is the case - the PC has detected the QUSB mode.
Unfortunately, Qualcomm does not make their Qualcomm Product Support Tool available to the public, and most OEMs do not provide the necessary binaries to restore the bootloader. The device cannot be repaired or restored without these tools, unless the mainboard is replaced. Unfortunately in this case, I believe that is your only option.
Click to expand...
Click to collapse
It is called the MSM Download Tool. And it is device specific and ready available.

TheGhost1951 said:
It is called the MSM Download Tool. And it is device specific and ready available.
Click to expand...
Click to collapse
Oh, specifically for the OnePlus. Good to know. I suppose I'm of absolutely no help here

Odin is for flashing Samsung devices. Samsung and now OnePlus are the only two devices I have worked with.

pmppm said:
Hey.
This post is my last faith in this device.
So basically I was about to flash partitions, but when I tried to go into fastbootd to flash the critical stuff, after the "fastboot reboot fastboot" command my phone was completely got bricked. I already tried every type of key combinations, the screen was black the entire time, and the phone won't even vibrates.
The only signal of it's being alive, when I plug it and press pwr + vol up, windows gives the sound of a connected/disconnected device, and the MsM tool shows that too. At this point, i was sure about the MsM tool and didn't panicked, I knew that I can almost always unbrick the phone with that... Hmm... This time it was different, because every time I get an error: "Sahara communication failed", or "Param preload", and I cant even do anything. Currently the phone was completely dead.
If you have any idea how to fix that Please let me know! Thanks.
View attachment 5788047
Click to expand...
Click to collapse
India device or global devices
And tip
Reboot to edl
Power off the phone
And press and hold pressed the voll up and voll down
And putt in the usb cable and hold pressed the voll up and voll down
And try msm tool

V0latyle said:
Oh, specifically for the OnePlus. Good to know. I suppose I'm of absolutely no help here
Click to expand...
Click to collapse
Not only specific to OnePlus but also specific to OOS versions.

Might try to uninstall Qualcomm drivers, make sure PC driver signing is disabled. Reboot PC, then re-install latest Qualcomm drivers, re-boot PC and try again with MSM tool. The windows sound when plugging in before is the sound of a device plugged in but couldn't recognize it and threw it out of device manager. That was the reason for the TWO sounds you heard. Also try holding down on vol + - and pressing power and holding it down to try to boot into fastboot mode. If it does, flash boot boot TWRP.img and then boot into edl from there with phone connected to PC and MSM tool in start mode ready to flash as soon as device is connected.