Database Users

Update Failed and Phone Cannot Start. Only Flash Blinks When Charging, NO START/Boot?

I got an update notification. And clicked to update.
When restarted the phone, the phone went to die. I could not start my phone.
I tried these:
1) Kept my fingers on VOL Down and POWER buttons for 2 minutes (even more), but NO USE.
2) Tried to open screws but my screwdrivers could not fit for them.
I bought it 3 months back, but in Flipkat and no service center near me. Any solution for it?

What update did you flash, and what OS were you on?
What device did you have, and was it charged up when you accepted the update?

echo92 said:
What update did you flash, and what OS were you on?
What device did you have, and was it charged up when you accepted the update?
Click to expand...
Click to collapse
* I got June update I guess.
* My device is moto g4 plus 1643 model India variant.
* When I connected charger, LED light blinks that was near Fingerprint zone.
* Tried device manager software, it helped nothing.
* Tried to put my fingers on POWER and VOLUME DOWN buttons, but no use.
Really disappointed as it was a gift from my brother.

TrueUniue said:
* I got June update I guess.
* My device is moto g4 plus 1643 model India variant.
* When I connected charger, LED light blinks that was near Fingerprint zone.
* Tried device manager software, it helped nothing.
* Tried to put my fingers on POWER and VOLUME DOWN buttons, but no use.
Really disappointed as it was a gift from my brother.
Click to expand...
Click to collapse
Just to clarify - you installed the update and then rebooted or just accepted the notification to begin the update (and then rebooted, after which your device failed to boot)?
Did you have TWRP/root and were you on the stock ROM prior to flashing (or a custom stock ROM)?

echo92 said:
Just to clarify - you installed the update and then rebooted or just accepted the notification to begin the update (and then rebooted, after which your device failed to boot)?
Did you have TWRP/root and were you on the stock ROM prior to flashing (or a custom stock ROM)?
Click to expand...
Click to collapse
The update was downloaded, when installing it went blank and never started up.
* I have TWRP custom ROM before it.

TrueUniue said:
The update was downloaded, when installing it went blank and never started up.
* I have TWRP custom ROM before it.
Click to expand...
Click to collapse
Did you flash a stock recovery before attempting to update? Having TWRP might be causing the hang; try these suggestions from abhi212b https://forum.xda-developers.com/mo...date-build-t3584982/post72114657#post72114657
Can I ask which custom ROM you were on? You won't be able to flash stock OTA updates with TWRP/customised stock ROM.

echo92 said:
Did you flash a stock recovery before attempting to update? Having TWRP might be causing the hang; try these suggestions from abhi212b https://forum.xda-developers.com/mo...date-build-t3584982/post72114657#post72114657
Can I ask which custom ROM you were on? You won't be able to flash stock OTA updates with TWRP/customised stock ROM.
Click to expand...
Click to collapse
My phone is in blank screen. NO start up. No fastboot or recovery mode available. Only light blinks when charger is connected. Then how can I do your suggestions? You didn't understand my problem.

TrueUniue said:
My phone is in blank screen. NO start up. No fastboot or recovery mode available. Only light blinks when charger is connected. Then how can I do your suggestions? You didn't understand my problem.
Click to expand...
Click to collapse
My apologies - I looked through your post history and was wondering if the TWRP/rooting performed previously might have prevented your device from booting.
What is your device detected as when you plug it into your computer, is it Moto G4 or is it Qualcomm HS-USB- 9008 (or similar)?

echo92 said:
My apologies - I looked through your post history and was wondering if the TWRP/rooting performed previously might have prevented your device from booting.
What is your device detected as when you plug it into your computer, is it Moto G4 or is it Qualcomm HS-USB- 9008 (or similar)?
Click to expand...
Click to collapse
When I connected to laptop, it took detected and installed port Qualcomm HS-USB- 9008. But I didn't see special drive detecting beside my other drivers.

TrueUniue said:
When I connected to laptop, it took detected and installed port Qualcomm HS-USB- 9008. But I didn't see special drive detecting beside my other drivers.
Click to expand...
Click to collapse
Right, 2 things to try:
1) Try holding the power button down for 2-3 minutes, this may force a hard restart which might break your device out of whatever state it's in.
2)If 1 doesn't work, you may wish to look into trying a blank-flash (here: https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016 or here: https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23 ) Depending on what happened with the update, you might be lucky. You may wish to have a look at these blank-flashes too, heed the warning: https://forum.xda-developers.com/showpost.php?p=73151763&postcount=6
3)If 1 and 2 don't work, then unfortunately you'll have to locate a repair centre (or try to find a Motorola service centre) that you could send the device to, or ask Flipkart for assistance. Alternatively, save up for another device. Currently, we don't have another option, though it appears that a member is trying to patch a blankflash for the new update: https://forum.xda-developers.com/showpost.php?p=73152979&postcount=21

echo92 said:
Right, 2 things to try:
1) Try holding the power button down for 2-3 minutes, this may force a hard restart which might break your device out of whatever state it's in.
2)If 1 doesn't work, you may wish to look into trying a blank-flash (here: https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016 or here: https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23 ) Depending on what happened with the update, you might be lucky. You may wish to have a look at these blank-flashes too, heed the warning: https://forum.xda-developers.com/showpost.php?p=73151763&postcount=6
3)If 1 and 2 don't work, then unfortunately you'll have to locate a repair centre (or try to find a Motorola service centre) that you could send the device to, or ask Flipkart for assistance. Alternatively, save up for another device. Currently, we don't have another option, though it appears that a member is trying to patch a blankflash for the new update: https://forum.xda-developers.com/showpost.php?p=73152979&postcount=21
Click to expand...
Click to collapse
I got this when I clicked blankflash:
C:\Users\*****\Downloads\Compressed\blankflash1\blankflash>.\qboot.
exe blank-flash
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM3
[ 0.002] Detecting device
[ 4.009] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.009] Check qboot_log.txt for more details
[ 4.010] Total time: 4.010s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error
C:\Users\*****\Downloads\Compressed\blankflash1\blankflash>pause
Press any key to continue . . .

I think, if any one can find new blankflash, I can fix my phone. I think those blankflases are old. I'm on April update, and failed when I tried for June update.

Moto G4 plus Blank flash error --device not detecting

I was upgrading to Nougat from Marshmallow, because of low battery phone switched off while updating. Now phone LED is blinking when I am charging and I have almost done all the things which are to be done. The only response I got is the LED light stop blinking and nothing happens then. Help me please, I have already charged it for 2-3 hours but still, it is not turning on.
I tried for blank flash but it showing the error msg. [Error opening device].
[ 0.000] Opening device: \\.\COM3
[ 0.000] ERROR: device_open()->error opening device
[ 0.000] Check qboot_log.txt for more details
[ 0.000] Total time: 0.001s
[ 0.000]

1) Did you have stock Nougat previously on this device?
2)Which blankflash are you using? Is it the one from this thread? https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 I see you've already posted in that thread.
3)You may have to try the blankflash a few times for it to connect. Verify that you're using the original Motorola cable or a high quality data cable and that your device is recognised by your computer (even if it's seen as Qualcomm HS-USB 9008 or similar).

[Solved] Black screen after root attempt on XT1962-4

Yesterday I tried rooting my Moto G7 (build PPOS29.114-134-7). I managed to unlock the bootloader and install Magisk, however, I installed a wrong version for my build and got stuck in a bootloop. After being frustrated for a while by my foolishness, I managed to fix it and was able to boot it up again to OS. But instead of giving up, I decided to try once again, this time with the correct build.
I once again installed Magisk, createad the boot.img, moved it to my PC and turned the phone off, but now I cannot turn it back on. The screen is black, no matter for how long I hold the buttons, no matter the combination of them I hold, it simply doesn't respond anymore. I let it charging on a wall outlet, I let it charging on the PC, no response. It doesn't even show the battery connected or anything. The screen remais black and nothing happens.
The only sign of life it shows is when I connect it to the PC and hold the buttons - Windows plays the "hardware connected" sound, but it doesn't appear on my drive list or anything.
Is it an expensive paperweight now? Should I take it to the shop, or is there anything else I can do to try and fix this?
Thank you, and feel free to call me stupid. I feel like I deserve it.
EDIT: This issue has been resolved thanks to user EmixArian24 who messaged me with a link he found on the Telegram group regarding the G7. I attached a blankflash he sent me and by using it, I managed to boot to bootloader. I then downloaded the stock rom from Lolinet and flashed it to the phone. It then booted as normal.
Thank you very much to EmixArian24 for the magical link and everybody else who replied. I really appreciate it.
As for the G8 I bought, I chose to keep it. I will be selling my G7 as soon as possible.

AetherOmega said:
Yesterday I tried rooting my Moto G7 (build PPOS29.114-134-7). I managed to unlock the bootloader and install Magisk, however, I installed a wrong version for my build and got stuck in a bootloop. After being frustrated for a while by my foolishness, I managed to fix it and was able to boot it up again to OS. But instead of giving up, I decided to try once again, this time with the correct build.
I once again installed Magisk, createad the boot.img, moved it to my PC and turned the phone off, but now I cannot turn it back on. The screen is black, no matter for how long I hold the buttons, no matter the combination of them I hold, it simply doesn't respond anymore. I let it charging on a wall outlet, I let it charging on the PC, no response. It doesn't even show the battery connected or anything. The screen remais black and nothing happens.
The only sign of life it shows is when I connect it to the PC and hold the buttons - Windows plays the "hardware connected" sound, but it doesn't appear on my drive list or anything.
Is it an expensive paperweight now? Should I take it to the shop, or is there anything else I can do to try and fix this?
Thank you, and feel free to call me stupid. I feel like I deserve it.
Click to expand...
Click to collapse
Open device manager
How is it listed?
Likely need to use blankflash
Should be a link in my help thread
https://forum.xda-developers.com/showpost.php?p=78869857&postcount=2
Sent from my ali using XDA Labs

sd_shadow said:
Open device manager
How is it listed?
Likely need to use blankflash
Should be a link in my help thread
https://forum.xda-developers.com/showpost.php?p=78869857&postcount=2
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
It is listed as Qualcomm HS-USB QDLoader 9008. I'm trying to use the blankflash I found under one of the threads you linked in your master thread, but I'm stuck at "Waiting for firehose to get ready" now. I'm out of ideas...
EDIT: either the firehose warning or the "greeting device for command mode" followed by "FAILED (blank-flash:greet-device:error reading packet)"
EDIT2: yet another error I found:
Code:
opening device: \\.\COM3
opening device: \\.\COM3
opening device: \\.\COM3
OKAY [ 0.002s]
greeting device for command mode
OKAY [ 0.002s]
identifying device
...serial = 0x832808F5
...chip-id = 0xBA
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.006s]
finding files
...programmer = programmer.mbn
...singleimage = singleimage.bin
OKAY [ 0.005s]
validating files
OKAY [ 0.045s]
switching to download mode
OKAY [ 0.002s]
greeting device for image downloading
OKAY [ 0.001s]
sending programmer
Unexpected packet: 4. Was expecting: 3
FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)

AetherOmega said:
It is listed as Qualcomm HS-USB QDLoader 9008. I'm trying to use the blankflash I found under one of the threads you linked in your master thread, but I'm stuck at "Waiting for firehose to get ready" now. I'm out of ideas...
EDIT: either the firehose warning or the "greeting device for command mode" followed by "FAILED (blank-flash:greet-device:error reading packet)"
EDIT2: yet another error I found:
Click to expand...
Click to collapse
You could try running it in several windows at same time.
Sent from my jerry_cheets using XDA Labs

sd_shadow said:
You could try running it in several windows at same time.
Sent from my jerry_cheets using XDA Labs
Click to expand...
Click to collapse
I did. I opened 15 to 25 of the batch files at once, only one of them seemed to "carry on" with the process only to result in a "Unexpected packet: 4. Was expecting: 3
FAILED (blank-flash:sahara-transfer-image:send-image:unexpected packet)" error. I'm really out of ideas now.
Is there a possibility of a home-fix, or the chances of it are really low? I'm thinking it might an incorrect version of files or something, I'm having a hard time finding specifics for my model. I tried searching specifically for "XT1962-4 blankflash" and the sorts, but it really is not easy finding anything related to this specific model.
EDIT: Since I had so many files and batches to use, I decided to scrap everything and start over again. Much better. I went to Lolinet, downloaded the blankflash for my model by going to Firmware > Moto > River > Blankflash and fired up blankflash.bat.
But I have a question regarding that - the files inside this folder I downloaded are the only ones I need, or do I need to download the stock rom and put all the files of the ROM inside the blankflash folder as well before opening blankflash.bat? What I've been trying to do is just starting blankflash with the contents of the zip I downloaded from Lolinet, I haven't tried pasting any other files inside of it.
Also, with this blankflash, I managed to get this result:
Code:
D:\Downloads\blankflash_from_PPO29.114-4>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 0.004] ...cpu.id = 186 (0xba)
[ 0.004] ...cpu.sn = 2200439029 (0x832808f5)
[ 0.004] Opening singleimage
[ 0.004] Loading package
[ 0.006] ...filename = singleimage.pkg.xml
[ 0.007] Loading programmer
[ 0.007] ...filename = programmer.mbn
[ 0.007] Sending programmer
[ 0.291] Handling things over to programmer
[ 0.293] Identifying CPU version
[ 0.299] Waiting for firehose to get ready
[ 60.863] Waiting for firehose to get ready
[120.958] ...MSM8953 unknown
[120.959] Determining target secure state
[120.964] Waiting for firehose to get ready
[181.059] ...secure = no
[181.080] Initializing storage
[181.082] Waiting for firehose to get ready
[241.158] Configuring device...
[241.159] Waiting for firehose to get ready
[301.235] Waiting for firehose to get ready
[361.308] Waiting for firehose to get ready
[421.378] Waiting for firehose to get ready
[481.448] Initializing storage
[481.450] Waiting for firehose to get ready
[541.524] Configuring device...
[541.525] Waiting for firehose to get ready
[601.603] Waiting for firehose to get ready
[661.687] Waiting for firehose to get ready
[721.773] Waiting for firehose to get ready
[781.852] Waiting for firehose to get ready
[841.943] Configuring device...
[841.944] Waiting for firehose to get ready
[902.031] Waiting for firehose to get ready
[962.124] Waiting for firehose to get ready
[1022.213] Waiting for firehose to get ready
[1082.309] ERROR: do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
[1082.309] Check qboot_log.txt for more details
[1082.310] Total time: 1082.311s
[1082.310] There were some hiccups in backup and restore.
[1082.310] Please save the following files and see a Bootloader member.
[1082.310] 1) ./qboot_log.txt
[1082.310] 2) ./backup_0x832808F5_2020-03-23_215316.img
[1082.310]
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
D:\Downloads\blankflash_from_PPO29.114-4>pause
Pressione qualquer tecla para continuar. . .
Any ideas?

Just an update, I gave up and bought a new phone. I'll try sending the phone to a shop whenever this whole viral crisis ceases.

AetherOmega said:
Yesterday I tried rooting my Moto G7 (build PPOS29.114-134-7). I managed to unlock the bootloader and install Magisk, however, I installed a wrong version for my build and got stuck in a bootloop. After being frustrated for a while by my foolishness, I managed to fix it and was able to boot it up again to OS. But instead of giving up, I decided to try once again, this time with the correct build.
I once again installed Magisk, createad the boot.img, moved it to my PC and turned the phone off, but now I cannot turn it back on. The screen is black, no matter for how long I hold the buttons, no matter the combination of them I hold, it simply doesn't respond anymore. I let it charging on a wall outlet, I let it charging on the PC, no response. It doesn't even show the battery connected or anything. The screen remais black and nothing happens.
The only sign of life it shows is when I connect it to the PC and hold the buttons - Windows plays the "hardware connected" sound, but it doesn't appear on my drive list or anything.
Is it an expensive paperweight now? Should I take it to the shop, or is there anything else I can do to try and fix this?
Thank you, and feel free to call me stupid. I feel like I deserve it.
EDIT: This issue has been resolved thanks to user EmixArian24 who messaged me with a link he found on the Telegram group regarding the G7. I attached a blankflash he sent me and by using it, I managed to boot to bootloader. I then downloaded the stock rom from Lolinet and flashed it to the phone. It then booted as normal.
Thank you very much to EmixArian24 for the magical link and everybody else who replied. I really appreciate it.
As for the G8 I bought, I chose to keep it. I will be selling my G7 as soon as possible.
Click to expand...
Click to collapse
I have some zip folders I want to post concerning hardbrick moto g7. How do I do this? I get error. Image files only are accepted.
Please tell me how to post a jar file here? I have tried to attach one but my file manager only allows jpg and PNG files types.

moto g7 impatience and a bricked phone?

Alright. I am taking full responsibility for the stupid things I have done in the impatience of a Sunday afternoon, so I'm ready to accept that I just bricked my only phone.
So I decided that I wanted to root my phone, so without any previous experience or understandings of the systems, twrp and Magdisk.
My issues started when I tried to unlock the bootloader, and upon every single boot, it would briefly display that I had a "badkey", but I ignored that because it was still booting.
I then installed minimal ADB and fastboot and first flashed twrp, and then magdisk. Thats when the first issue started.
my phone was now stuck in a bootloop, saying something similar to my "badkey" error message, but in place of "badkey" was just "n/a"
This was bad. Really bad.
Next, I tried to fix it using my limited rushed knowledge, so I tried to flash a default moto g7 rom on to the phone. This was also a VERY big mistake.
This flash landed me into a phone that now displays absolutely nothing, and the only proof that I have that any of it even works is that, when plugged into my PC, it shows up on my COM4 port as Qualcomm HS-USB QDLoader 9008 (COM4).
Now here I am, at the mercy of the universe. If anyone has an idea or a similar experience or solution, please go ahead and share. If not, let this be a precautionary tale: Never rush; Never be impatient.

Xalllle said:
Alright. I am taking full responsibility for the stupid things I have done in the impatience of a Sunday afternoon, so I'm ready to accept that I just bricked my only phone.
So I decided that I wanted to root my phone, so without any previous experience or understandings of the systems, twrp and Magdisk.
My issues started when I tried to unlock the bootloader, and upon every single boot, it would briefly display that I had a "badkey", but I ignored that because it was still booting.
I then installed minimal ADB and fastboot and first flashed twrp, and then magdisk. Thats when the first issue started.
my phone was now stuck in a bootloop, saying something similar to my "badkey" error message, but in place of "badkey" was just "n/a"
This was bad. Really bad.
Next, I tried to fix it using my limited rushed knowledge, so I tried to flash a default moto g7 rom on to the phone. This was also a VERY big mistake.
This flash landed me into a phone that now displays absolutely nothing, and the only proof that I have that any of it even works is that, when plugged into my PC, it shows up on my COM4 port as Qualcomm HS-USB QDLoader 9008 (COM4).
Now here I am, at the mercy of the universe. If anyone has an idea or a similar experience or solution, please go ahead and share. If not, let this be a precautionary tale: Never rush; Never be impatient.
Click to expand...
Click to collapse
The bad key and n/a are normal for moto.
The Qualcomm deal is
Emergency download mode (edl)
You need to find a river blankflash
A bunch of threads on this.
There's one here
https://mirrors.lolinet.com/firmware/moto/river/blankflash/
It may work...
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
The bad key and n/a are normal for moto.
The Qualcomm deal is
Emergency download mode (edl)
You need to find a river blankflash
A bunch of threads on this.
There's one here
It may work...
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
I tried lauching blank-flash, and im getting this in response:
[ 0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 4.010] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.010] Check qboot_log.txt for more details
[ 4.010] Total time: 4.011s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
Can I get past this?

Xalllle said:
I tried lauching blank-flash, and im getting this in response:
[ 0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 4.010] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.010] Check qboot_log.txt for more details
[ 4.010] Total time: 4.011s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
Can I get past this?
Click to expand...
Click to collapse
Nevermind! I got it working by A. Trying it a billion times and B. trying it on another pc. For some reason, that made it work.

OP5 : black screen when lineage logo display + white led

Hi ! my Oneplus 5 has slightly taken rainwater in my pocket. The phone wouldn't start up again.
I changed the battery. The phone reboots, the screen displays "1+ Powered by Android", then the screen starts to display lineage Logo and turns black and a white LED lights up.
I can't access the recovery mode by pressing power button + volume down.
Would you have an idea that would allow me to fix it? (I wanted to unbrick the phone but I can't enter to recovery ...)
thank you for your help

Use an EDL flasher (commonly known as unbrick tool). You can find it here on XDA

Pierre02 said:
Use an EDL flasher (commonly known as unbrick tool). You can find it here on XDA
Click to expand...
Click to collapse
Thanks for your answer. I wanted to follow this guide (https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706) but MSM Download Tool can't see my OnePlus (I followed the instructions but my phone doesn't appear under COMs and Ports).
For your information, I can get into the fastboot. With linux, the phone is well recognized in fastboot (it is also recognized with the tool TOOL_ALL_IN_ONE_2.0.1.3).
Code:
I tried this :
Sending 'recovery' (33689 KB) OKAY [ 1.320s]
Writing 'recovery' OKAY [ 0.317s]
Finished. Total time: 1.721s
Sending 'boot.img' (33689 KB) OKAY [ 1.289s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: 00000050')
fastboot: error: Command failed

tifriis said:
Thanks for your answer. I wanted to follow this guide (https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706) but MSM Download Tool can't see my OnePlus (I followed the instructions but my phone doesn't appear under COMs and Ports).
For your information, I can get into the fastboot. With linux, the phone is well recognized in fastboot (it is also recognized with the tool TOOL_ALL_IN_ONE_2.0.1.3).
Click to expand...
Click to collapse
You have to install drivers in special mode aka non signed driver install allowed mode in windows 10.
It's num 7 in the list of advance system startup.
For some reason i didn't had to do anything as my laptop already had everything somehow, i just open tool and flashed to 7.1 to test my phone. Now back to 10.
Only think I did before was installed htc 10 drivers to unlock and have custom rom on it.

atifsh said:
You have to install drivers in special mode aka non signed driver install allowed mode in windows 10.
Click to expand...
Click to collapse
Thanks but I did it (I followed this link : https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/ and I run "bcdedit /set testsigning on" then I restarted).
Maybe I have to uninstall some drivers before because my phone doesn't appear in the category " Ports (COM & LPT) ?
Here my screen after booting : https://cncloud.zaclys.com/index.php/s/bqMF3cDzMScjzgd
Thanks for your help

Hi ! I think I managed to install the driver (I had to remove old drivers).
Now MsmDownloadTool gives me this state :
Code:
Index : 1
Com : COM3
Status of Connection : Connected
SN :
Status of Communication : Param preprocessing
I'm stuck in "Param preprocessing". Phone have green LED. Any ideas ?
Thanks to help me to save my phone

For infomation, I succeed to use MSM Download Too. I was sotck in "Param preprocessing" because my battery was too low.
However, when my OP5 reboot, it displays the 1+ logo then get stuck with the red point and white circle, then reboot.
Any ideas ?

tifriis said:
For infomation, I succeed to use MSM Download Too. I was sotck in "Param preprocessing" because my battery was too low.
However, when my OP5 reboot, it displays the 1+ logo then get stuck with the red point and white circle, then reboot.
Any ideas ?
Click to expand...
Click to collapse
This is probably an hardware fault

Thanks for your support. Do you think it's the motherboard ?
Do you know if I can buy another one ?
Thanks for all, I apprieciate !