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

My XIAOMI MI A2 went to 0% and now it has a bootloop android one

I was playing normally the phone discharged turned off, and when I connect it only shows the android one screen over and over, the led that shows that it's charging doesn't turns on, I have nothing weird installed, didn't even knew about fastboot or roms, or anything like that until 15 minutes ago, so the fastboot options are not and cannot be activated, does it have a solution? do I just let it be connected for a few hours and try again, or what, i'm a noob on this matters so I don't know what to do. Thanks

maybe try holding vol down and power for 10 or more seconds. it should vibrate. it reboots and shows fastboot icon, you can flash stock rom again, let us know

loop4444 said:
maybe try holding vol down and power for 10 or more seconds. it should vibrate. it reboots and shows fastboot icon, you can flash stock rom again, let us know
Click to expand...
Click to collapse
The fastboot screen shows, but I can't do anything, and if I connect it to my PC after watching somethings like going to CMD and trying some commands the console doesn't even recognize those commands, maybe I have to install something for it to read it? I don't know, if this helps in anyway, I appreciate it.

M4N4GM said:
The fastboot screen shows, but I can't do anything, and if I connect it to my PC after watching somethings like going to CMD and trying some commands the console doesn't even recognize those commands, maybe I have to install something for it to read it? I don't know, if this helps in anyway, I appreciate it.
Click to expand...
Click to collapse
connect phone in fastboot mode and flash stock rom trough MiFlash, but remember to take backup of internal memory. I'll release all except external sd.

pawelik said:
connect phone in fastboot mode and flash stock rom trough MiFlash, but remember to take backup of internal memory. I'll release all except external sd.
Click to expand...
Click to collapse
Can you do the backup even if the phone can't start? does de MiFlash has that option? and thanks i'll try

M4N4GM said:
Can you do the backup even if the phone can't start? does de MiFlash has that option? and thanks i'll try
Click to expand...
Click to collapse
It seems that you didn´t enable USB debugging before, maybe? Did you solve it?

SubwayChamp said:
It seems that you didn´t enable USB debugging before, maybe? Did you solve it?
Click to expand...
Click to collapse
No I didn't enable the USB debugging, and no I haven't been able to do it, the mi flash program needs extra installations but always sends an error message and closes, I really don't know how to do this kind of things, I tried with a program called MiFlash Unlock, but it needs a Xiaomi account connected with the number and I don't have one, I really don't know what to do from here, plus I've read that I need the rom to install and don't know where can I find it and which one is the one that I need to install.
Once again thanks and if someone can help me further than this is appreciated

M4N4GM said:
No I didn't enable the USB debugging, and no I haven't been able to do it, the mi flash program needs extra installations but always sends an error message and closes, I really don't know how to do this kind of things, I tried with a program called MiFlash Unlock, but it needs a Xiaomi account connected with the number and I don't have one, I really don't know what to do from here, plus I've read that I need the rom to install and don't know where can I find it and which one is the one that I need to install.
Once again thanks and if someone can help me further than this is appreciated
Click to expand...
Click to collapse
Anyway you can't do many things although you should have enabled USB debugging atleast you decided to unlock device but fastboot is (almost) useless for device with locked boatloader.
The first thing I do no matter I don't think to root or modify my device is enabling USB debugging just to have more options to recover from an eventual brick.
Now try to do the next before to go to the other option; try to enter to recovery from device off, using volume up + power for some seconds then format/factory reset and let us know what happened.

SubwayChamp said:
Anyway you can't do many things although you should have enabled USB debugging atleast you decided to unlock device but fastboot is (almost) useless for device with locked boatloader.
The first thing I do no matter I don't think to root or modify my device is enabling USB debugging just to have more options to recover from an eventual brick.
Now try to do the next before to go to the other option; try to enter to recovery from device off, using volume up + power for some seconds then format/factory reset and let us know what happened.
Click to expand...
Click to collapse
That option didn't work, volume up + power just tried to start the phone

M4N4GM said:
That option didn't work, volume up + power just tried to start the phone
Click to expand...
Click to collapse
Ok, I supposed it, some partitions get corrupted while device fails to reboot.
Your last solution is using EDL mode, you will find many tutorials on YouTube to put device in this mode using test point method, then flashing the official stock rom through MiFlash tool.
To take in account MiFlash tool doesn´t work while in fastboot mode on devices with locked bootloaders so you have to use it in EDL (Emergency DownLoad) mode, no other workaround known on that. (for this model)
As reference I´ll put the basis of the links that you need to take a look in:
- Test Point method:
https://www.google.com/url?sa=t&rct...=XzknDcBovWw&usg=AOvVaw3gCAHutdqhO0Ukszyz-XJ-
- Drivers for unbrick qualcomm devices:
https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/
- Xiaomi Flash Tool:
https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
- Fastboot images, you can use the latest:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871

SubwayChamp said:
Ok, I supposed it, some partitions get corrupted while device fails to reboot.
Your last solution is using EDL mode, you will find many tutorials on YouTube to put device in this mode using test point method, then flashing the official stock rom through MiFlash tool.
To take in account MiFlash tool doesn´t work while in fastboot mode on devices with locked bootloaders so you have to use it in EDL (Emergency DownLoad) mode, no other workaround known on that. (for this model)
As reference I´ll put the basis of the links that you need to take a look in:
- Test Point method:
https://www.google.com/url?sa=t&rct...=XzknDcBovWw&usg=AOvVaw3gCAHutdqhO0Ukszyz-XJ-
- Drivers for unbrick qualcomm devices:
https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/
- Xiaomi Flash Tool:
https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
- Fastboot images, you can use the latest:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Click to expand...
Click to collapse
Thanks i'll try if it works

SubwayChamp said:
Ok, I supposed it, some partitions get corrupted while device fails to reboot.
Your last solution is using EDL mode, you will find many tutorials on YouTube to put device in this mode using test point method, then flashing the official stock rom through MiFlash tool.
To take in account MiFlash tool doesn´t work while in fastboot mode on devices with locked bootloaders so you have to use it in EDL (Emergency DownLoad) mode, no other workaround known on that. (for this model)
As reference I´ll put the basis of the links that you need to take a look in:
- Test Point method:
https://www.google.com/url?sa=t&rct...=XzknDcBovWw&usg=AOvVaw3gCAHutdqhO0Ukszyz-XJ-
- Drivers for unbrick qualcomm devices:
https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/
- Xiaomi Flash Tool:
https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
- Fastboot images, you can use the latest:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Click to expand...
Click to collapse
You should try the official and safer fastboot image.
http://c.mi.com/oc/miuidownload/detail?device=1700353

Little Hill said:
You should try the official and safer fastboot image.
http://c.mi.com/oc/miuidownload/detail?device=1700353
Click to expand...
Click to collapse
Wrongly quoted.

Question Nokia G10 and G20 -- How to enter Recovery Mode?

Nokia G10 and G20 -- How to enter Recovery Mode?
Does anyone know how to enter the recovery mode on these two Nokia's model G10, and G20????
Normally, it should be a combination between Volume+/- and Power Button...
However, none of these work apparently.
It only enters fastboot mode and nothing else.
I had tried using adb command "adb devices", it shown connected.
But when I tried "adb reboot recovery", nothing happened so far.
I also digging down some searches for the whole evening.
There were only fake instructions which did not work at all.
Does anyone have any thought about this?

{
"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"
}

mvikrant97 said:
View attachment 5444049
Click to expand...
Click to collapse
You can see in the above screenshot that I have successfully entered recovery mode. My device is Nokia G20 TA-1365.

mvikrant97 said:
You can see in the above screenshot that I have successfully entered recovery mode. My device is Nokia G20 TA-1365.
Click to expand...
Click to collapse
At last, Thank you so much for your tutorial Here.
It worked so far...
After reading your tutorial, it seems to me to be an usual and familiar procedure. I was still wondering what step I did wrong.
So I tried once again, the first time still not success. Then I managed to update the drivers, "usb_driver_r13-windows", and "platform-tools_r31.0.3-windows". On my second attempt, it success.
Thank you again, I appreciate your help and time devoting.

mvikrant97 said:
You can see in the above screenshot that I have successfully entered recovery mode. My device is Nokia G20 TA-1365.
Click to expand...
Click to collapse
Hi, I manage to get to the "android logo with exclamation mark No command text right below it." part. But when I continue to the 11th step "Keep holding Power key and press Volume up once and you will enter recovery mode. Release the keys.", nothing happens. I have been trying the Power + Volume Up combination for about 15 minutes, in all varieties, and nothing happened. I also tried other button combinations, and nothing worked. I just can't get from the android logo into the recovery mode. I have definitely hit the combination that should be right at least once in those million tries. Any ideas?

emge2116 said:
Hi, I manage to get to the "android logo with exclamation mark No command text right below it." part. But when I continue to the 11th step "Keep holding Power key and press Volume up once and you will enter recovery mode. Release the keys.", nothing happens. I have been trying the Power + Volume Up combination for about 15 minutes, in all varieties, and nothing happened. I also tried other button combinations, and nothing worked. I just can't get from the android logo into the recovery mode. I have definitely hit the combination that should be right at least once in those million tries. Any ideas?
Click to expand...
Click to collapse
Which device do you use?
Simply hold power button and then press the Volume up key once, that's it.

mvikrant97 said:
Which device do you use?
Simply hold power button and then press the Volume up key once, that's it.
Click to expand...
Click to collapse
Nokia G10. I did exactly what you said at least 100 times, and it did not work.

mvikrant97 said:
Which device do you use?
Simply hold power button and then press the Volume up key once, that's it.
Click to expand...
Click to collapse
Does this work?
VID_20211108_165558
Visit this link to play the video:
files.fm
I tried all different possibilities... push both at once, hold both at once, hold one, push the other, and then switch and try again, different holding periods.... only clicks, holding for one second, more seconds,.... everything! I just can't get into the recovery mode.

emge2116 said:
Nokia G10. I did exactly what you said at least 100 times, and it did not work.
Click to expand...
Click to collapse
Begin from start and once you get the Android logo with exclamation mark with No command text then remove USB cable from your phone and then hold power key and press volume key once.

mvikrant97 said:
Begin from start and once you get the Android logo with exclamation mark with No command text then remove USB cable from your phone and then hold power key and press volume key once.
Click to expand...
Click to collapse
I also tried that multiple times already. So, with cable and without cable inserted. But generally I took some other procedure to get to the Android logo, could that be the problem? But even with that procedure, there were a lot of people that were satisfied with the solution, and it worked for them. I used TFM Tool Pro 2.0.0.

emge2116 said:
I also tried that multiple times already. So, with cable and without cable inserted. But generally I took some other procedure to get to the Android logo, could that be the problem? But even with that procedure, there were a lot of people that were satisfied with the solution, and it worked for them. I used TFM Tool Pro 2.0.0.
Click to expand...
Click to collapse
Even if you use TFM Tool Pro 2.0.0 the tool sends the same command fastboot reboot recovery, so it should not matter. You should get to the recovery mode.

mvikrant97 said:
Even if you use TFM Tool Pro 2.0.0 the tool sends the same command fastboot reboot recovery, so it should not matter. You should get to the recovery mode.
Click to expand...
Click to collapse
Ok, thank you. Well, if you do think of anything else that would be stopping it, or if you have any other idea it would be very appreciated. Thanks again!

emge2116 said:
Ok, thank you. Well, if you do think of anything else that would be stopping it, or if you have any other idea it would be very appreciated. Thanks again!
Click to expand...
Click to collapse
If you use any other device please make a video call so that I can better judge your problem. You can PM me to contact on my Google Duo or any other video chat enabled app.

mvikrant97 said:
If you use any other device please make a video call so that I can better judge your problem. You can PM me to contact on my Google Duo or any other video chat enabled app.
Click to expand...
Click to collapse
Please PM me. I think I may have found solution to your problem.

Hi mvikrant97 was there a solution to this problem that emge2116 was experiencing ? I have the same issue, I can successfully get G10 to recovery mode "no command" screen but then no matter what I try I cannot get the phone into the recovery mode menu. Any help appreciated. thanks

stevesydney2126 said:
Hi mvikrant97 was there a solution to this problem that emge2116 was experiencing ? I have the same issue, I can successfully get G10 to recovery mode "no command" screen but then no matter what I try I cannot get the phone into the recovery mode menu. Any help appreciated. thanks
Click to expand...
Click to collapse
Hello even my Nokia G20 is having same issue after the latest update.

ninetitle said:
Nokia G10 and G20 -- How to enter Recovery Mode?
Does anyone know how to enter the recovery mode on these two Nokia's model G10, and G20????
Normally, it should be a combination between Volume+/- and Power Button...
However, none of these work apparently.
It only enters fastboot mode and nothing else.
I had tried using adb command "adb devices", it shown connected.
But when I tried "adb reboot recovery", nothing happened so far.
I also digging down some searches for the whole evening.
There were only fake instructions which did not work at all.
Does anyone have any thought about this?
Click to expand...
Click to collapse
Hello. Can you check whether you can still access the recovery mode by this method? because now even I'm stuck on No command window after the latest update.

mvikrant97 said:
Hello. Can you check whether you can still access the recovery mode by this method? because now even I'm stuck on No command window after the latest update.
Click to expand...
Click to collapse
Hello, did you manage to solve the problem with entering the menu?

filimonArz said:
Hello, did you manage to solve the problem with entering the menu?
Click to expand...
Click to collapse
No success. Maybe Nokia has changed the way we access the recovery mode in latest update. Hope it comes with a fix in December Security Patch.

hey guys! dont own the phone but a sister does so i was roaming xda for fun and do have an experience with a nokia phone myself heh
see since this phone launched with android 11 so its guaranteed to have userspace fastboot implementation, which is called fastbootd so i do have an idea on forcing ur way into recovery
while ur phone is in the => FASTBOOT MODE...
(not fastbootd)
type this command into ur terminal:
fastboot reboot fastboot
hopefully that command will kick ur phone into fastbootd and then u can just exit out of it and back into recovery

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.

Question How to unlock device state on “brick”

I just unboxed new OnePlus 9 Pro, then i was installing an update and during update phone’s case held power off button, so phone turned off and showing current error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can’t boot in Android and in Recovery mode. Everything working is Fastboot mode. I was trying to “unbrick” phone, installing Fastboot ROM( files like boot.img, recovery.img and so on),but in cmd on my pc shows while using commands like: “fastboot flash boot boot.img” or fastboot -w“, only error “Failed (remote:’Erase is not allowed in Lock State’)”.
Now i want to unlock device state if it is possible.
Remind that phone was just unboxed, so it doesn’t have enabled lever OEM unlocking.

try 'fastboot --set-active=other' or unbrick with MSM Download tool or https://github.com/bkerler/edl

chizari said:
I just unboxed new OnePlus 9 Pro, then i was installing an update and during update phone’s case held power off button, so phone turned off and showing current error.
View attachment 5813705
I can’t boot in Android and in Recovery mode. Everything working is Fastboot mode. I was trying to “unbrick” phone, installing Fastboot ROM( files like boot.img, recovery.img and so on),but in cmd on my pc shows while using commands like: “fastboot flash boot boot.img” or fastboot -w“, only error “Failed (remote:’Erase is not allowed in Lock State’)”.
Now i want to unlock device state if it is possible.
Remind that phone was just unboxed, so it doesn’t have enabled lever OEM unlocking.
Click to expand...
Click to collapse
bro just use the msm tool. there's a tool for every variant of the 9 pro (LE2120-2125). Look for the post on our Device xda and use it.

aIecxs said:
try 'fastboot --set-active=other'
Click to expand...
Click to collapse
cmd says: fastboot: unknown option -- set-active=other
I think it doesn’t understand what‘s --, maybe ’cause i dont have libraries or drivers

ishansnp said:
bro just use the msm tool. there's a tool for every variant of the 9 pro (LE2120-2125). Look for the post on our Device xda and use it.
Click to expand...
Click to collapse
i know about msm tool, but i cant enter in qualcomm emergency mode, cause when i connect phone to pc, it starts charging and when phone starts charging it can’t load “charge image” and gives same error as in the attachment

chizari said:
i know about msm tool, but i cant enter in qualcomm emergency mode, cause when i connect phone to pc, it starts charging and when phone starts charging it can’t load “charge image” and gives same error as in the attachment
Click to expand...
Click to collapse
turn off the phone fully, press volume up and down fully for 3 seconds then while still holding those buttons, plug in the phone with MSM open on your laptop. it should immediately detect the device. the phone screen will still be black and thats normal. once device is shown as connected, just select target O2 and start

disconnect usb, let battery drain, ensure it is really powered off, press both volume keys, connect usb

chizari said:
I just unboxed new OnePlus 9 Pro, then i was installing an update and during update phone’s case held power off button, so phone turned off and showing current error.
View attachment 5813705
I can’t boot in Android and in Recovery mode. Everything working is Fastboot mode. I was trying to “unbrick” phone, installing Fastboot ROM( files like boot.img, recovery.img and so on),but in cmd on my pc shows while using commands like: “fastboot flash boot boot.img” or fastboot -w“, only error “Failed (remote:’Erase is not allowed in Lock State’)”.
Now i want to unlock device state if it is possible.
Remind that phone was just unboxed, so it doesn’t have enabled lever OEM unlocking.
Click to expand...
Click to collapse
MSM Tool time. What model do you have?

aIecxs said:
disconnect usb, let battery drain, ensure it is really powered off, press both volume keys, connect usb
Click to expand...
Click to collapse
ok, i ll try

TheGhost1951 said:
MSM Tool time. What model do you have?
Click to expand...
Click to collapse
LE2123

chizari said:
LE2123
Click to expand...
Click to collapse
Get the MSM tool for LE2123 from this thread....
How To Guide OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)​

Does somebody know how long it takes to let battery drain from 100%?
And maybe, Are there some advices how to let battery drain faster?

You will also need to 1) disable driver signature see this https://www.techpout.com/disable-driver-signature-enforcement/ then reboot computer 2) install latest OnePlus USB drivers then 3) install latest Qualcomm driver then reboot PC 4) start the MSM Tool uncheck 256 and check use lite firehose the click start. 5) start phone in edl mode with button sequence.... MSM should automatically start flashing!

As for edl mode, check to see if you can get to fastboot by holding vol + and - and power buttons down and hold them to see if fastboot loads. This is if you cannot get to edl the button wat as described above.

TheGhost1951 said:
As for edl mode, check to see if you can get to fastboot by holding vol + and - and power buttons down and hold them to see if fastboot loads. This is if you cannot get to edl the button wat as described above.
Click to expand...
Click to collapse
Fastboot menu loads
Now i need to wait few days to let battery drain…
Maybe you know any advices how to let it drain faster?

chizari said:
Fastboot menu loads
Now i need to wait few days to let battery drain…
Maybe you know any advices how to let it drain faster?
Click to expand...
Click to collapse
No need to wait.... Do you have the latest platform-tools installed on PC?

TheGhost1951 said:
No need to wait.... Do you have the latest platform-tools installed on PC?
Click to expand...
Click to collapse
Yeah, i installed it with android studio

chizari said:
Yeah, i installed it with android studio
Click to expand...
Click to collapse
Good now download this file and save it to the platform-tools folder and change the name to twrp.img.... https://dl.twrp.me/lemonadep/twrp-3.7.0_11-0-lemonadep.img make sure the phone is connected to PC in fast boot mode if you have already installed all the drivers....

TheGhost1951 said:
You will also need to 1) disable driver signature see this https://www.techpout.com/disable-driver-signature-enforcement/ then reboot computer 2) install latest OnePlus USB drivers then 3) install latest Qualcomm driver then reboot PC 4) start the MSM Tool uncheck 256 and check use lite firehose the click start. 5) start phone in edl mode with button sequence.... MSM should automatically start flashing!
Click to expand...
Click to collapse
here you mentioned qualcomm drivers, you mean Qualcomm HS-USB QDLoader 9008 Drivers

chizari said:
here you mentioned qualcomm drivers, you mean Qualcomm HS-USB QDLoader 9008 Drivers
Click to expand...
Click to collapse
Yes