For the past few days i had been postponing a 40mb security update that came on my Moto G4 Plus. Finally today i decided to do it and it was downloaded as usual and the phone rebooted and it started installing the update. It was all going fine but as the progression bar filled all the way through the phone black screened and has not yet booted up. When connected to a computer the white notification LED light keeps blinking continuously. Please help.
Hyp3rVen0m said:
For the past few days i had been postponing a 40mb security update that came on my Moto G4 Plus. Finally today i decided to do it and it was downloaded as usual and the phone rebooted and it started installing the update. It was all going fine but as the progression bar filled all the way through the phone black screened and has not yet booted up. When connected to a computer the white notification LED light keeps blinking continuously. Please help.
Click to expand...
Click to collapse
Please give more details,.. Have a look at here https://forum.xda-developers.com/mo...-question-noob-friendly-t3526598/post73395955 and read ahead!
He bricked his phone and its also blinking. Did you do the same with your phone?
If your phone had been modified in any shape, then that's the result. You need to start by flashing a standard ROM in fastboot (or rdslite if fastboot mode is not working), maybe directly the last one:
https://forum.xda-developers.com/moto-g4-plus/how-to/install-official-firmware-soak-test-t3531296
Details
SoNic67 said:
If your phone had been modified in any shape, then that's the result. You need to start by flashing a standard ROM in fastboot (or rdslite if fastboot mode is not working), maybe directly the last one:
https://forum.xda-developers.com/moto-g4-plus/how-to/install-official-firmware-soak-test-t3531296
Click to expand...
Click to collapse
The phone was fully functioning before the small official update. The bootloader is unlocked. It's running the official Android N for Moto G4 Plus. There is no custom recovery installed.
Boot issue
strongst said:
Please give more details,.. Have a look at here https://forum.xda-developers.com/mo...-question-noob-friendly-t3526598/post73395955 and read ahead!
He bricked his phone and its also blinking. Did you do the same with your phone?
Click to expand...
Click to collapse
My issue is somewhat similar but whenever i connect the phone to a computer and hold the power button or any other combination for few seconds the computer recognizes the device for few seconds and then it disconnects due to unsuccessful boot.
Even a custom logo will trow a stick in the wheel.
Try to enter fast boot first. If that doesn't work, tray the RDSLite path.
SoNic67 said:
Even a custom logo will trow a stick in the wheel.
Try to enter fast boot first. If that doesn't work, tray the RDSLite path.
Click to expand...
Click to collapse
I visited the local service center for Lenevov/Motorolla and they have checked the phone and come to a conclusion that the motherboard indeed has malfunctioned hence the battery power and the software isn't working properly. I've been asked to replace the motherboard. Thanks for your help.
Hyp3rVen0m said:
I visited the local service center for Lenevov/Motorolla and they have checked the phone and come to a conclusion that the motherboard indeed has malfunctioned hence the battery power and the software isn't working properly. I've been asked to replace the motherboard. Thanks for your help.
Click to expand...
Click to collapse
It means that your battery is not functioning well. In case if it is not a hardware problem
Try the below step.
Plug in a charger of another phone with current output greater then 1. And then press volume down key and power key simultaneously. If the device woke up in fastboot mode then you are lucky. If this does not work leave the phone in charging for at least one and half hour. Then try the button combination again.
Battery working fine
ADITYA_KUMAR said:
It means that your battery is not functioning well. In case if it is not a hardware problem
Try the below step.
Plug in a charger of another phone with current output greater then 1. And then press volume down key and power key simultaneously. If the device woke up in fastboot mode then you are lucky. If this does not work leave the phone in charging for at least one and half hour. Then try the button combination again.
Click to expand...
Click to collapse
The guy said the battery and rest of the parts are functioning well and do not need replacement and i don't think using another charger is gonna do anything in this case. Thanks anyway.
i faced exactly same pbm today. ditto. i just gave it to service centre, hope ghost screen n boot both be fixed
Today same issue happen to my moto g4 plus as well after downloading security phone went for installation and never turned on after that.. anyone solved this issue or service center is the only option??
c.bedi said:
Today same issue happen to my moto g4 plus as well after downloading security phone went for installation and never turned on after that.. anyone solved this issue or service center is the only option??
Click to expand...
Click to collapse
Have you read the whole tread already? There are solutions provided. Or which issue you are meaning exactly?
c.bedi said:
Today same issue happen to my moto g4 plus as well after downloading security phone went for installation and never turned on after that.. anyone solved this issue or service center is the only option??
Click to expand...
Click to collapse
Did you downgrade or flash an older stock ROM at any point? Which update was this, and what stock firmware did you previously have on your device?
If you plug your device into your computer, is it still recognised or is it detected as a Qualcomm HS-USB 9008 or similar? If so, you may have hard bricked your device. Try this blankflash in the following link to repair your device bootloader and then flash the latest stock ROM (September 2017 patch) to fully repair your device. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 for the blank flash, https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 for the September 2017 stock ROM.
c.bedi said:
Today same issue happen to my moto g4 plus as well after downloading security phone went for installation and never turned on after that.. anyone solved this issue or service center is the only option??
Click to expand...
Click to collapse
In my case the phone didn't turn on because the motherboard died for some unknown reason while the update. I did take it to authorized service center and he told me it was the motherboard and would require replacement.
Thanks for the reply guys.. Today my phone turned on automatically.. magic and then notification came unable to install update, no changes made...phone still showing new system software available..
Related
i tried going back to stock firmware using the method in general section but i always seem to get an error at 49%. can someone explain how to get passed this.
i using the t-mobile d801.
also my recovery seemed to have gotten erased because i cant boot into twrp anymore.
LG G2 Stuck @ 49%
El Killer said:
i tried going back to stock firmware using the method in general section but i always seem to get an error at 49%. can someone explain how to get passed this.
i using the t-mobile d801.
also my recovery seemed to have gotten erased because i cant boot into twrp anymore.
Click to expand...
Click to collapse
HEY! I'm on the d801 as well and I've been where you're at a number of times, unfortunately. But I've always gotten out. Here's the conclusion I've reached. Trying to flash directly back to stock without wiping all the partitions first is what makes the RDTool get stuck. It's like the phone runs out of memory and can't host a full Gig+ of data since your last ROM is in the way. Sorry if I'm wrong but I'm only assuming you didn't wipe everything except the Internal storage. The good thing every time this has happened to me is that your recovery partition should be intact. Mine always is, and we're on the same variant. Another thing, booting back into recovery is not impossible. It's all in the timing it takes from the first time you see the LG logo while holding volume - and the power button, but don't let go. What worked for me was to let the phone cycle between off and boot power states twice until the phone is completely off again. You may even notice the LED indicator flash red. Release your keys if the phone stays off and immediately hold the combo down again until the phone tries to boot again just don't let go of the buttons. Once it powers down again, leave the phone alone for a few minutes. Come back and this time get ready to boot into recovery. The combo button press will initiate boot but don't let go until the next time you see the LG logo flash, then quickly release and depress the vol down power up combo and hold. May take a minute longer than usual but the reset menu should pop up thereafter. Tap power 2 more times and you should back into recovery. It's worked every time for me. Let me know if you're good and whether this helped!
Good Luck,
tinydynamite00
try with x86
El Killer said:
i tried going back to stock firmware using the method in general section but i always seem to get an error at 49%. can someone explain how to get passed this.
i using the t-mobile d801.
also my recovery seemed to have gotten erased because i cant boot into twrp anymore.
Click to expand...
Click to collapse
i had exact same issue that progress stucked on 49%. if you are using 64bit OS, try to flash it with 32bit(x86) OS
good luck
tinydynamite00 said:
HEY! I'm on the d801 as well and I've been where you're at a number of times, unfortunately. But I've always gotten out. Here's the conclusion I've reached. Trying to flash directly back to stock without wiping all the partitions first is what makes the RDTool get stuck. It's like the phone runs out of memory and can't host a full Gig+ of data since your last ROM is in the way. Sorry if I'm wrong but I'm only assuming you didn't wipe everything except the Internal storage. The good thing every time this has happened to me is that your recovery partition should be intact. Mine always is, and we're on the same variant. Another thing, booting back into recovery is not impossible. It's all in the timing it takes from the first time you see the LG logo while holding volume - and the power button, but don't let go. What worked for me was to let the phone cycle between off and boot power states twice until the phone is completely off again. You may even notice the LED indicator flash red. Release your keys if the phone stays off and immediately hold the combo down again until the phone tries to boot again just don't let go of the buttons. Once it powers down again, leave the phone alone for a few minutes. Come back and this time get ready to boot into recovery. The combo button press will initiate boot but don't let go until the next time you see the LG logo flash, then quickly release and depress the vol down power up combo and hold. May take a minute longer than usual but the reset menu should pop up thereafter. Tap power 2 more times and you should back into recovery. It's worked every time for me. Let me know if you're good and whether this helped!
Good Luck,
tinydynamite00
Click to expand...
Click to collapse
still no luck
El Killer said:
still no luck
Click to expand...
Click to collapse
OK. So tell me, what ROM were you on, which recovery version and name are you using, why were you flashing back to stock, i.e. were you having problems, what kind. Explain as much as you can in detail. Need to retrace your exact steps to best get you fixed up!
tinydynamite00
tinydynamite00 said:
OK. So tell me, what ROM were you on, which recovery version and name are you using, why were you flashing back to stock, i.e. were you having problems, what kind. Explain as much as you can in detail. Need to retrace your exact steps to best get you fixed up!
tinydynamite00
Click to expand...
Click to collapse
i was using pa4.0 and wanted to go back to stock because i preffered the lg ui. i had twrp 2.6.3.5 i restored my back up of stock but when i rebooted i got into fastboot mode.
twrp wasnt working after i had restored my back up go straight to fastboot was stuck in fastboot until i found a thread explaining how to get out of fastboot and restore download mode.
managed to get download mode working and tried to flash stock with mobile support tool and got the 49 percent error,
my phone never really displayed any progress just says download mode with a white box and blue dots
El Killer said:
i was using pa4.0 and wanted to go back to stock because i preffered the lg ui. i had twrp 2.6.3.5 i restored my back up of stock but when i rebooted i got into fastboot mode.
twrp wasnt working after i had restored my back up go straight to fastboot was stuck in fastboot until i found a thread explaining how to get out of fastboot and restore download mode.
managed to get download mode working and tried to flash stock with mobile support tool and got the 49 percent error,
my phone never really displayed any progress just says download mode with a white box and blue dots
Click to expand...
Click to collapse
K, now if you're only seeing the blue dots when you attach by USB your phone to PC, then you're not fully in DL mode to process the kdz. You should see a white wheel in the center of the screen when you connect and a viewing mirror near the base of your phone with ROOTED in red directly below that. And you're sure your PC is detecting your phone? You've the drivers installed? Because when RDT tells you to run the tool, you'll see some binary code in the viewing window I spoke of, the white wheel will turn and below it will be shown the COM port to which you're connected and a solid thin red bar will begin to fill a space in the viewer showing you the progress.
Also, be sure when attempting the first steps I gave you to boot into recovery that you are not USB connected. It won't work.
And, try to remember if your phone was well enough charged, should have been at least 80% full. It happened to me once that I couldn't boot recovery and my phone would go to fastboot like yours until I left it alone to charge and then I repeated the stepsvi laid out to get back into recovery. This part is paramount!
Please READ CAREFULLY
I used to be in your same situation. I thought I had bricked my phone for good. I finally figured it out. Here is my solution from my Thread.
Esteef said:
Okay, after 12+ hours of trying every method possible on XDA I finally resolved my issue. I will update the first post just incase any others care or fall into the same dilemma I was in.
The LG Mobile Support tool would not download the firmware and it would NOT ask me for my IMEI to download it either.
So my solution....
***
Installed LG Mobile Support Tool then Installed the LG Drivers. (FROM HERE http://forum.xda-developers.com/showthread.php?t=2471370
BEFORE I connected the phone to the computer. I opened the LG Mobile support tool clicked (Options on the top right).
When the dropped down opened, I clicked the (Upgrade Recovery) option. THEN, is when the prompt opened to ask me what my IMEI is.
Before I entered my IMEI, I connected my phone to the computer in download mode, then proceeded to enter my IMEI and hit OK.
This is when the LG Mobile Support tool SUCCESSFULLY downloaded the latest official LG firmware and installed it.
*** BE AWARE, with the phone connected to the PC, the prompt NEVER appeared to enter my IMEI.
*** But with the phone disconnected, the prompt came up every time. This might be the trick for some people.
*** with the IMEI prompt opened, I then connected the phone , entered the IMEI, then hit OK. BOOM HERPES....
Well I'll polish this up more later. I hope this works for every LG G2 Variant and not just the T-Mobile one (D801)
-Esteef
Click to expand...
Click to collapse
THIS WILL WIPE YOUR PHONE COMPLETELY...
tinydynamite00 said:
K, now if you're only seeing the blue dots when you attach by USB your phone to PC, then you're not fully in DL mode to process the kdz. You should see a white wheel in the center of the screen when you connect and a viewing mirror near the base of your phone with ROOTED in red directly below that. And you're sure your PC is detecting your phone? You've the drivers installed? Because when RDT tells you to run the tool, you'll see some binary code in the viewing window I spoke of, the white wheel will turn and below it will be shown the COM port to which you're connected and a solid thin red bar will begin to fill a space in the viewer showing you the progress.
Also, be sure when attempting the first steps I gave you to boot into recovery that you are not USB connected. It won't work.
And, try to remember if your phone was well enough charged, should have been at least 80% full. It happened to me once that I couldn't boot recovery and my phone would go to fastboot like yours until I left it alone to charge and then I repeated the stepsvi laid out to get back into recovery. This part is paramount!
Click to expand...
Click to collapse
yeah my computer does recognize my phone. but i cant run adb or fastboot anymore. all drivers are installed also.
i never got the while wheel or any progress indicator. so i guees im not really in download mode.
i let my phone charge for a few hours and try your method again and let you know what happens
El Killer said:
yeah my computer does recognize my phone. but i cant run adb or fastboot anymore. all drivers are installed also.
i never got the while wheel or any progress indicator. so i guees im not really in download mode.
i let my phone charge for a few hours and try your method again and let you know what happens
Click to expand...
Click to collapse
Sounds good. A full charge can make all the difference. I learnt the hard way! One or more of us will be along should you need further help.
I do hope you get this sorted! I've come back from the brink too many times to not believe you won't.
tinydynamite00
Do as esteef recommended..
Sent from my LG-D802 using XDA Premium 4 mobile app
Falaco147 said:
Do as esteef recommended..
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
im trying but i get a battery to low error. i guess i need to charge it longer
i owe you all a million thanks for helping me unbrick my phone. i really thought i was left with a paper weight and then i tried esteefs method again i really owe you guys thank you for the support
El Killer said:
i owe you all a million thanks for helping me unbrick my phone. i really thought i was left with a paper weight and then i tried esteefs method again i really owe you guys thank you for the support
Click to expand...
Click to collapse
You are welcome... The first time I did it too my battery was at 28% and I panicked since I got the low battery error.
I could of sworn that my phone officially became a paper weight. My heart dropped.
I'm glad you are up and running with the rest of us!
-Esteef
1732359994
hey !
I have the same problem, but... I can't acces to the recovery :/ i tried to install CWM (with Freegee) over Team win recovery and... boot loop :
The rom 4.2.2 flex was gone, no boot animation
-When i pres volum down + power, i have the reset menu, but after that, there is a black screen and it's written at the top left "started usb_start Fastboot Mode ()"
Please, i need your help, i'm so afraid !!
Thx !
Esteef said:
I used to be in your same situation. I thought I had bricked my phone for good. I finally figured it out. Here is my solution from my Thread.
THIS WILL WIPE YOUR PHONE COMPLETELY...
Click to expand...
Click to collapse
I know this thread is a bit old, but it saved my butt. Your method worked perfectly. Thank you for this post.
My LG F460 was bricked (error 570), only download mode was working. Esteef method works fine even my pictures and programs was saved. Thanks!
Hello, i have a blackberry Priv that is stuck on logo and just keeps on restarting and doesnt go to the main screen....how to solve this problem? CAn i solve it by flashing with autoloader
Also, i cant turn on the phone to main screen,
How do i know if it is version:
STV100-1,
STV100-2,
STV100-3,
STV100-4 OR
STV100-5
I downloaded autoloader for STV100-1 and installed drivers too. Now i put phone in fastboot mode by pressing power key and vol - key. I connect phone to pc and run autoloader but window appears and disappears. How to flash this phone and repair this phone....someone pls help
thanks
andrew21 said:
Hello, i have a blackberry Priv that is stuck on logo and just keeps on restarting and doesnt go to the main screen....how to solve this problem? CAn i solve it by flashing with autoloader
Also, i cant turn on the phone to main screen,
How do i know if it is version:
STV100-1,
STV100-2,
STV100-3,
STV100-4 OR
STV100-5
I downloaded autoloader for STV100-1 and installed drivers too. Now i put phone in fastboot mode by pressing power key and vol - key. I connect phone to pc and run autoloader but window appears and disappears. How to flash this phone and repair this phone....someone pls help
thanks
Click to expand...
Click to collapse
Hi,
If you don't know the model #, then don't flash...
I read that Hard Reset of the device is needed, by pressing and holding the volume up and down keys simultaneously for at least 10 seconds, when you reach the error screen
Charkatak said:
Hi,
If you don't know the model #, then don't flash...
I read that Hard Reset of the device is needed, by pressing and holding the volume up and down keys simultaneously for at least 10 seconds, when you reach the error screen
Click to expand...
Click to collapse
I tried to hard reset, enter bootloader mode, enter recovery mode but its all in vain. Moment phone goes to bootloader mode for enter into fastboot it restarts.
By pressing Volume up + Power it takes me to recovery mode there it shows error and again restarts.
Even its not getting connected to pc cause it restarts continuously and in this situation how can I know which model it is and how can I flash new version.
All this happened after Marshmallow update.
Please come up with some solution else this is just a paper weight.
I have the same issue, after Marshmellow update my Priv keep restarting and continuous doing that until the batTrey drain. The phone also heats up and can't find a solution. Tried all kind of reboots but nothing works.
Hoping for a solution before the phone dies completely.
Same issue since 2 days ago
Hello,
I also have the same issue with the PRIV. I spoke with BB Support. They told they will contact me by after 24 hours. I don't know if there won't be any valid warranty since it is an unlocked phone.
Have you find any solution for this?
Please someone help!!
this is because of a wrong flash, you need to use the autoloader appropiate for your unit, with device in fastboot mode run the autoloader, if you do not know your version download all available and flash them, if it is not valid for your unit it wont flash or it wont work, if you swap files to try to bypass and install mm on ll device like att it wont work neither, i have tested this and it works no matter if you swapped files from other autoloaders or not as long you use the correct one your device will be back to life
Same error here...
But if I try to enter fastboot mode (vol-), it reboots after 2-3 seconds...tried also 32 seconds of power on button....any idea?
Thank you,
Chuck26
nicromant said:
this is because of a wrong flash, you need to use the autoloader appropiate for your unit, with device in fastboot mode run the autoloader, if you do not know your version download all available and flash them, if it is not valid for your unit it wont flash or it wont work, if you swap files to try to bypass and install mm on ll device like att it wont work neither, i have tested this and it works no matter if you swapped files from other autoloaders or not as long you use the correct one your device will be back to life
Click to expand...
Click to collapse
Thanks for the tip,
I tried to flash it with one autoloader days ago. It just didn't succeed. The screen went black with unceasing blinking green light.
I kept the contact wit BB Support. They just washed their hands. They told me to go to the Rogers Store where I just bought the PRIV to ask them for a replacement. This is kind of impossible, since I live in Mexico and when the device was bought was on a trip to Vancouver. Yesterday I just plugged in my laptop the phone with the autoloader running hoping something happens. So I left it at home for several hours. When I came back, it was just as before, restarting over and over and over until fastboot menu. So I just gave another try to the autoloader, but it just happened again. Now it remains in black screen and with the green led light blinking. I tried several button combinations over and over just to get to the fastboot menu with no success.
I can't make it to bring up the loading screen and neither fastboot menu.
I guess it was because picking a wrong autoloader for flashing the PRIV. I downloaded another autoloader for trying.
Please help with this.
My PRIV is the STV100-3.
The first autoloader I tried is the Rogers Canada or Orange Slovakia – STV100-3 & STV100-4 - AAF057 Software Version
The second I want to try is the BlackBerry common SW for generic STV100-1, STV100-3 & STV100-4 devices - AAF518 Software Version
This is the link where I got them:
http ://ca.blackberry.com/content/blackberry-com/en_ca/support/smartphones/blackberry-PRIV/reload.html
Thanks in advance!!
nicromant said:
this is because of a wrong flash, you need to use the autoloader appropiate for your unit, with device in fastboot mode run the autoloader, if you do not know your version download all available and flash them, if it is not valid for your unit it wont flash or it wont work, if you swap files to try to bypass and install mm on ll device like att it wont work neither, i have tested this and it works no matter if you swapped files from other autoloaders or not as long you use the correct one your device will be back to life
Click to expand...
Click to collapse
Thanks for the tip,
I tried to flash it with one autoloader days ago. It just didn't succeed. The screen went black with unceasing blinking green light.
I kept the contact wit BB Support. They just washed their hands. They told me to go to the Rogers Store where I just bought the PRIV to ask them for a replacement. This is kind of impossible, since I live in Mexico and when the device was bought was on a trip to Vancouver. Yesterday I just plugged in my laptop the phone with the autoloader running hoping something happens. So I left it at home for several hours. When I came back, it was just as before, restarting over and over and over until fastboot menu. So I just gave another try to the autoloader, but it just happened again. Now it remains in black screen and with the green led light blinking. I tried several button combinations over and over just to get to the fastboot menu with no success.
I can't make it to bring up the loading screen and neither fastboot menu.
I guess it was because picking a wrong autoloader for flashing the PRIV. I downloade n¿another autoloader for trying.
Please help with this.
My PRIV is the STV100-3.
The first autoloader I tried is the Rogers Canada or Orange Slovakia – STV100-3 & STV100-4 - AAF057 Software Version
The second I want to try is the BlackBerry common SW for generic STV100-1, STV100-3 & STV100-4 devices - AAF518 Software Version
This is the link where I got them:
http ://ca.blackberry.com/content/blackberry-com/en_ca/support/smartphones/blackberry-PRIV/reload.html
Thanks in advance!!
leo_ackzion
if the autoloader solution does not work then you need to force manually the unit into flashboot (google how to force fastboot)
then try to flash each content from the img into the device manually same as the nexus devices
the autoloader should be able to recover your device
this is the reload instruction website
http://support.blackberry.com/kb/articleDetail?articleNumber=000038083
this is where the autoloaders reside
http://ca.blackberry.com/content/bl...pport/smartphones/blackberry-PRIV/reload.html
make sure your device is physically an STV100-3 or 4 it is basic to have the proper version
nicromant said:
leo_ackzion
if the autoloader solution does not work then you need to force manually the unit into flashboot (google how to force fastboot)
then try to flash each content from the img into the device manually same as the nexus devices
the autoloader should be able to recover your device
this is the reload instruction website
http://support.blackberry.com/kb/articleDetail?articleNumber=000038083
this is where the autoloaders reside
http://ca.blackberry.com/content/bl...pport/smartphones/blackberry-PRIV/reload.html
make sure your device is physically an STV100-3 or 4 it is basic to have the proper version
Click to expand...
Click to collapse
Hi nicromant.
After several hours I wrote my last comment, the phone showed the fastboot mode, restarting over and over without showing the BB Logo, but only the fastboot menu, constantly rebooting.
Next, I tried to reload the OS via autoloader again. But then my phone again was in black screen with green and white blinking light.
Then I tried to manually force it into fastboot with the Android SDK Tools, but nothing happens.
When I introduce "adb devices" command, it won't show any connected device in the PC.
So I don't know what else I can do.
Please help!
Thanks in advance.
I just had this problem. Took it to the tmobile store i bought it from and they told me it was fried hardware. The phone keeps trying to reboot and fix itself but obviously it can't happen. Their solution? Get a new phone. I had a 2 year warranty and apparently the priv has been having so many problems that the store was offering a trade up deal to a samsung. Hopefully a store near you is doing the same, because thats probably your only option at this point if it's the same problem as mine.
leo_ackzion said:
Hi nicromant.
After several hours I wrote my last comment, the phone showed the fastboot mode, restarting over and over without showing the BB Logo, but only the fastboot menu, constantly rebooting.
Next, I tried to reload the OS via autoloader again. But then my phone again was in black screen with green and white blinking light.
Then I tried to manually force it into fastboot with the Android SDK Tools, but nothing happens.
When I introduce "adb devices" command, it won't show any connected device in the PC.
So I don't know what else I can do.
Please help!
Thanks in advance.
Click to expand...
Click to collapse
Try to install the appropiate ADB and fastboot drivers it is why your pc is unable to see the device, check on device manager if you have it setup properly, unfortunately i do not have a priv anymore (i change devices every 1 or 2 month)
I have same problem with my Priv from AT&T (100-1). It failed to boot after autoloader. it does not turn on. Just LED flashes: White one flash, then Green 3 flashes. and again. I can not force it into fastboot menu anymore holding Power plus Vol down or any other combination.
Need help! Thanks
after updating with this loader
https://bbapps.download.blackberry.com/Priv/bbry_qc8992_autoloader_user-common-AAG191.zip
i also cant boot the phone it just show me 4 options on screen but keep on coming back to it no matter what i select
Hold power & vol down both for 32 seconds for a real HARD reboot...
Charkatak said:
Hi,
If you don't know the model #, then don't flash...
I read that Hard Reset of the device is needed, by pressing and holding the volume up and down keys simultaneously for at least 10 seconds, when you reach the error screen
Click to expand...
Click to collapse
I had the same issue quite suddently with no warning. Phone just shut itself off (in a manner similar to what happens when you long press the powre button) Spent hours wondering what to do. Finally Thought the power button was stuck. I slipped a long finger nail into the gap where the power button contacts the phone electronics (dont know how to be clearer than this) to try and separate the power button and whatever it touches when you press it. After a couple of tries, The phone started up successfully. It appears to be a design issue
I FIXED IT!
Same issue as described, bootloop after 10 seconds.
I used electrical tape under and over the flat cable of the power button, also covered the "inner" power button with this.
Now it works for already 1,5 hours and is loading updates.
Also posted this as nes3Ah in crackberry forums, but it has to be released by a mod.
Good luck!
Hi people, something quite terrible happened to my phone when I woke up today. Before I went to sleep the phone worked and was charged by about 40% but some apps were force closing like crazy so I turned off the device before I went to sleep, cuz why not, eh? Then I woke up and turned on the phone and it showed the screen to choose if I want to go into downloading mode, I pressed cancel and the phone shutdown and now it wont turn on.
I tried soft resets, tried to charge it for 10 minutes, but the thing is the phone is like its hard bricked for no apparent reason... even the charge indicator when phone is off doesn't show anymore, no lights, no nothing. Please help me. If anyone has an idea what to do it would be greatly appreciated. It worked this morning, no one else touched the phone. :crying:
if it doesnt boot then its a battery problem, even in hard brick, it has some kind of flights flashing.
if Its hard brick then its paper weight, sorry.
Chord_Hugo87 said:
if it doesnt boot then its a battery problem, even in hard brick, it has some kind of flights flashing.
if Its hard brick then its paper weight, sorry.
Click to expand...
Click to collapse
If it's the battery what can I do here at home? At least try? I don't think it's a hardbrick cause I didn't do anything iregular to the phone, it was working before I shut it down and went to sleep. Idk how I hardbricked it by turning it off. :/
theSperks said:
If it's the battery what can I do here at home? At least try? I don't think it's a hardbrick cause I didn't do anything iregular to the phone, it was working before I shut it down and went to sleep. Idk how I hardbricked it by turning it off. :/
Click to expand...
Click to collapse
well the storage drive could fail, that could be another possibility which if I think about it now that seems to be the case. best bet send it to samsung.
if you plug your phone into your computer and it does not read or register, you really dont have any other choices. This goes for all phones, the forum can help you with soft brick, not something like this, this looks like a hardware failure.
Chord_Hugo87 said:
well the storage drive could fail, that could be another possibility which if I think about it now that seems to be the case. best bet send it to samsung.
if you plug your phone into your computer and it does not read or register, you really dont have any other choices. This goes for all phones, the forum can help you with soft brick, not something like this, this looks like a hardware failure.
Click to expand...
Click to collapse
The phone rebooted constantly and force close apps from the day I bought it. I thought it was software issue... I went to my carrier to complain but they said nothing is wrong with the phone (way back few months ago). So my last question is this, can a phone force close apps and restart constantly with a software issue? or does it happen only to devices with hardware issues?
theSperks said:
The phone rebooted constantly and force close apps from the day I bought it. I thought it was software issue... I went to my carrier to complain but they said nothing is wrong with the phone (way back few months ago). So my last question is this, can a phone force close apps and restart constantly with a software issue? or does it happen only to devices with hardware issues?
Click to expand...
Click to collapse
that sounds like a storage drive failure...no apps doesnt do that and phone doesnt restart for no reason.
Chord_Hugo87 said:
that sounds like a storage drive failure...no apps doesnt do that and phone doesnt restart for no reason.
Click to expand...
Click to collapse
Ok so good news! Today I plugged it in the charger again and it booted! As I see it when I turn it off it doesnt really shut down properly and it stays in some kind of a phase and doesnt let me reset or do anything really... but It drained the battery that it had left and it bugged out. I know this cause I shutted it down again via the android option and its "bricked" again. Now I will wait for it to lose charge again so I can boot it.
Can you please tell me how to properly flash via odin to the latest nougat firmware? The phone was from Vodafone in Germany, few months ago I flashed a Netherlands firmware, then some other one few weeks down the road. Can you please tell me how to flash it back to full stock and what firmware should I download? The model is SM-G935F and the S/N is RF8H61YE4CP. I prevously tried THIS firmware from sammobile. Is this the correct one for my phone? I tried using samsung smart switch but it says "Secure Check Fail : Bootloader" when it tries to emergency restore it in the download mode, and the smart switch software says just error. Also whenever I flashed with Odin, BL never wanted to flash cause of just one file in every BL md5 file and that is the param.bin one, everything else flashes like it should. Please write me a guide on how to flash it properly and "upgrade" everything to the latest version correctly for my phone. (many settings in Odin that I never touched)
theSperks said:
Ok so good news! Today I plugged it in the charger again and it booted! As I see it when I turn it off it doesnt really shut down properly and it stays in some kind of a phase and doesnt let me reset or do anything really... but It drained the battery that it had left and it bugged out. I know this cause I shutted it down again via the android option and its "bricked" again. Now I will wait for it to lose charge again so I can boot it.
Can you please tell me how to properly flash via odin to the latest nougat firmware? The phone was from Vodafone in Germany, few months ago I flashed a Netherlands firmware, then some other one few weeks down the road. Can you please tell me how to flash it back to full stock and what firmware should I download? The model is SM-G935F and the S/N is RF8H61YE4CP. I prevously tried THIS firmware from sammobile. Is this the correct one for my phone? I tried using samsung smart switch but it says "Secure Check Fail : Bootloader" when it tries to emergency restore it in the download mode, and the smart switch software says just error. Also whenever I flashed with Odin, BL never wanted to flash cause of just one file in every BL md5 file and that is the param.bin one, everything else flashes like it should. Please write me a guide on how to flash it properly and "upgrade" everything to the latest version correctly for my phone. (many settings in Odin that I never touched)
Click to expand...
Click to collapse
i had a simmilar problem i couple months ago when i flashed a custom kernel.
i was overclocking the cpu but caused the phone to freeze actually without being able to to anything
i thougt my battery was dead also
when i charged it nothing came up into the screen also.
you just have to hard reset it but just keep on pressing your volume down button together wih your home button and the power button
it may take lonnger then you can normally do it cuz your phone freezed
but eventually your phone will just reboot into download mode then eand you can hit the volume down button to reboot your phone then
Hey Guys,
I have a dead phone(kind of). All it displays is
"Have been in Factory Mode. long press power button and Normal boot"
And in very tiny font, there is a line saying
"=>Tool DL Image Load Fail!"
This stays for a few seconds then it turns off, and repeat, again the same this comes up on the screen.
What I have tried:
1) Flash the stock ROM using SP Flash Tools several times
2) Cleaned the power button from the inside a bit, because some thread said there might be a sticky button.
Flashing with SP Flash Tools shows that the flash is successful, but it didn't help.
EDIT: Now it displays something as "eFuse blow: Success". Damn!
PraneethMv said:
Hey Guys,
I have a dead phone(kind of). All it displays is
"Have been in Factory Mode. long press power button and Normal boot"
And in very tiny font, there is a line saying
"=>Tool DL Image Load Fail!"
This stays for a few seconds then it turns off, and repeat, again the same this comes up on the screen.
What I have tried:
1) Flash the stock ROM using SP Flash Tools several times
2) Cleaned the power button from the inside a bit, because some thread said there might be a sticky button.
Flashing with SP Flash Tools shows that the flash is successful, but it didn't help.
EDIT: Now it displays something as "eFuse blow: Success". Damn!
Click to expand...
Click to collapse
Have you set it to format all in sp?
Try it maybe it will work
If didnt i think its hardware issue
crazylife said:
Have you set it to format all in sp?
Try it maybe it will work
If didnt i think its hardware issue
Click to expand...
Click to collapse
Hey, Thank you for replying.
Have tried that method, its just the same thing, but now it is not displaying that tiny line.
Now it goes into the factory mode and shows some options in Chinese. And it stays there till i select something.
The last option, i know is "Reboot To Phone" (Via Google Translate).
When i select that option it goes back into the Factory mode again.
Can you flash twrp and boot in to recovery...May be..And then do something from there?:
sandeep101 said:
Can you flash twrp and boot in to recovery...May be..And then do something from there?:
Click to expand...
Click to collapse
Tried to flash TWRP through SP, it returns an error:
ERROR: S_SECURITY_SECURE_USB_DL_IMAGE_SIGN_HEADER_NOT_FOUND(6045)
MSP ERROR CODE:0x00.
Make sure volume + button is not pressed.
During boot can you boot in to stock recovery,
press POWER BUTTON + VOLUME UP + VOLUME DOWN until Lenovo logo appear, then continue press VOLUME UP + VOLUME DOWN
Thanks all. I somehow got it to work... and now my phone is all good.
As crazylife told, there was some hardware issue. Apparently, there was a tini-tiny bit of a circuit which, due to water allegedly, got short. I had it cleaned by some local phone shop.( He also claimed that the phone work anyway ,though). After that i flashed the stock rom, and it worked.
And btw, how do i mark the thread solved?
Hi, even I'm stuck with the same problem.
PraneethMv said:
Thanks all. I somehow got it to work... and now my phone is all good.
As crazylife told, there was some hardware issue. Apparently, there was a tini-tiny bit of a circuit which, due to water allegedly, got short. I had it cleaned by some local phone shop.( He also claimed that the phone work anyway ,though). After that i flashed the stock rom, and it worked.
And btw, how do i mark the thread solved?
Click to expand...
Click to collapse
Hi, even I'm stuck with the same problem.
Even the lenovo service center guys raised their hands saying it's an hardware problem and I've to replace the entire PCB to slove the issue. Could you be more specific on how to resolve this issue? if possible could you please let me know at which place you got your mobile fixed? Thanks
Regards,
Jagan ([email protected])
Jaganathan.S said:
Hi, even I'm stuck with the same problem.
Even the lenovo service center guys raised their hands saying it's an hardware problem and I've to replace the entire PCB to slove the issue. Could you be more specific on how to resolve this issue? if possible could you please let me know at which place you got your mobile fixed? Thanks
Regards,
Jagan ([email protected])
Click to expand...
Click to collapse
I had a problem with the Motherboard due to water getting in, and apparently it caused a short-circuit near the power button module. Actually speaking, I was really dissatisfied with the kind of service the Lenovo guys give to its customers, because first they told me that they will clean, and claimed that the board must be changed. The only thing which needed to be done in my phone was to clean that part of the board with White Petrol(you can ask the local mobile shop guys, they will have it, but just be careful). That solved my problem. And thanks to few threads, i got it working.
P.S: I am from Hyderabad, so had it solved here in a local shop.
Hi, Thanks for your reply. Was able to come out of that situation after 3 days, but had left my mobile with the local service center for 2 days (At the time, when i took my mobile from service center, my mobile was not working, was informed that the mobile is dead) I thought of giving a last try and plugged in the charger on 3rd day it started working . My mobile had a new problem display was broken (from inside) and speakers were not working, when i asked that guy his reply was " how can i know, your mobile was dead, when u brought in hear, my job was to fix it, why will i break it?" though my mobile was back to normal I had to pay a huge price of display and speakers. Hope everyone got to know the take away from my story. Crazy world; lesson learnt.
The same is happening to me!
And my phone keeps vibrating, also I don't know how to select one of those Chinese options, can you please help me sir?
Pok25dhw said:
The same is happening to me!
And my phone keeps vibrating, also I don't know how to select one of those Chinese options, can you please help me sir?
Click to expand...
Click to collapse
Hey!
My phone had some water damage issue, hence the loop. Opened the phone and cleaned it a bit. Yours might be different problem, try flashing stock firmware, or going into fastboot mode and flashing recovery. Currently don't have this phone so can't help that much.
PraneethMv said:
Hey!
My phone had some water damage issue, hence the loop. Opened the phone and cleaned it a bit. Yours might be different problem, try flashing stock firmware, or going into fastboot mode and flashing recovery. Currently don't have this phone so can't help that much.
Click to expand...
Click to collapse
Oh. Yes my phone too got wet in rain. I went to some shop and they helped me out. But thanks to you I realize that it was repairable and that too without loosing any data. Thanks so much for saving my thousands of ruppees that'd have been wasted to get a new phone. Also yes this model in general is pretty old so I can understand that most of the people don't use it anymore. Again thank you very much for saving all the stuff I had on this phone and the money. ??
I've been using the stock rom on my phone for years, until after one update my wifi went incredibly choppy, so I tried rooting and LineageOS but experienced lots of other issues, so I reverted to the original stock rom.
I've stuck with 6.0 for over a year, unrooted, unspoilt, but I was constantly pestered with update notifications.
I accidentally hit 'Yes, I'm in' the other day and it downloaded the update, and the pestering went next level insane.
I'd hit dismiss and 5 seconds later - DO YOU WANT TO INSTALL THE UPDATE? It would reappear a minute later.
So I finally caved and just said yes, curious whether or not my wifi would suffer, figuring it might have been a bad update that caused my wifi issues which has since been fixed.
I installed the first update, which brought me to 6.0.1 I think, and then I installed the update to 7.0.
And then my phone died completely.
The only sign of life is when I plug it into the PC, the charging light blinks, but I don't even see a battery charging screen.
The screen has stayed black since, can't reboot into any mode.
What now?
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
hedgehog90 said:
I've been using the stock rom on my phone for years, until after one update my wifi went incredibly choppy, so I tried rooting and LineageOS but experienced lots of other issues, so I reverted to the original stock rom.
I've stuck with 6.0 for over a year, unrooted, unspoilt, but I was constantly pestered with update notifications.
I accidentally hit 'Yes, I'm in' the other day and it downloaded the update, and the pestering went next level insane.
I'd hit dismiss and 5 seconds later - DO YOU WANT TO INSTALL THE UPDATE? It would reappear a minute later.
So I finally caved and just said yes, curious whether or not my wifi would suffer, figuring it might have been a bad update that caused my wifi issues which has since been fixed.
I installed the first update, which brought me to 6.0.1 I think, and then I installed the update to 7.0.
And then my phone died completely.
The only sign of life is when I plug it into the PC, the charging light blinks, but I don't even see a battery charging screen.
The screen has stayed black since, can't reboot into any mode.
What now?
Click to expand...
Click to collapse
Does it vibrate or any other indication that the phone is trying to boot? Will it charge? needs to be at least 40% to recover. USB to ADB and see if the phone is recognized on a PC. Could be hard bricked ... there is one other mode that some phones use where the screen is black and the only way to talk to it is through a flashing tool. I apologize that I cannot recall the name of that mode but considering that Lenovo developed this phone it wouldnt surprise me if it was just in that mode, waiting for a boot load update of some kind. A lenovo flash program might be worth a try.
milesius said:
Does it vibrate or any other indication that the phone is trying to boot? Will it charge? needs to be at least 40% to recover. USB to ADB and see if the phone is recognized on a PC. Could be hard bricked ... there is one other mode that some phones use where the screen is black and the only way to talk to it is through a flashing tool. I apologize that I cannot recall the name of that mode but considering that Lenovo developed this phone it wouldnt surprise me if it was just in that mode, waiting for a boot load update of some kind. A lenovo flash program might be worth a try.
Click to expand...
Click to collapse
I eventually fixed it using adb following a set of unbricking instructions on XDA.
Sorry for not updating the thread.