Database Users

lg mobile support tool stuck at 49%

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!

[Q] Entering Download mode while stuck in a bootloop

Hello,
this could be a silly question, but I'm actually hopeless about it...
I've been using CloudyG3 for 3 days, but I had some problems about it, so I decided I'd revert back to stock. I entered the Download Mode, installed the V20D ROM using LG's Support Tool, and, when the phone restarted, tried to enter the Factory Reset screen. Try as I might, I couldn't do that, so I'm stuck in a bootloop (I mean, the LED indicator is flashing, but no LG boot animation - just the static logo. I think there could've been some problem while flashing the FW, that's why I would like to enter Download mode again, or maybe at least turn my phone off (it can only restart). Nevertheless, while trying to flash the FW again while in a bootloop, everything from model no. to firmware version installed is shown correctly, but it can't boot into Download mode.
Thanks in advance!

a5943 said:
Hello,
this could be a silly question, but I'm actually hopeless about it...
I've been using CloudyG3 for 3 days, but I had some problems about it, so I decided I'd revert back to stock. I entered the Download Mode, installed the V20D ROM using LG's Support Tool, and, when the phone restarted, tried to enter the Factory Reset screen. Try as I might, I couldn't do that, so I'm stuck in a bootloop (I mean, the LED indicator is flashing, but no LG boot animation - just the static logo. I think there could've been some problem while flashing the FW, that's why I would like to enter Download mode again, or maybe at least turn my phone off (it can only restart). Nevertheless, while trying to flash the FW again while in a bootloop, everything from model no. to firmware version installed is shown correctly, but it can't boot into Download mode.
Thanks in advance!
Click to expand...
Click to collapse
Have you got a power source connected ?

timlad said:
Have you got a power source connected ?
Click to expand...
Click to collapse
Thanks for your reply!
No, I don't.
EDIT
I'm really grateful to you for your suggestion. Having plugged the device in, the Download mode came up with no problems. Now I'm trying to flash the previous version - V20B, which might make my device usable again.
Thank you very much!

[Bootloop] [No recovery mode] Need help to restore phone.

All!
I am having a huge problem with my phone now. I was updating it to lollipop and i had it a week. Then I decided to go for a new kernel and accualy it gone bootloop. So normalny I wanted to recovery mode by going with volume down + power. But every time I go there is black screen and I cant do anything now (I think its fault that i updated only radio but not bootloaded) Also do see anything happening when trying to plug to USB on Windows....
Any advice how to try to restore it would be much appriciated!

Sooooo, the only chance for you to get back your N4 is to still be able to access the Bootloader/Fastboot mode and I hope you are.

I dont know if bootloader mode is working as when trying the combo volmue down + power I have only black screen.
I am doing format of my windows to check if ill get connection on this black screen.

It seems that you can't even acces your bootloader so no Fastboot mode :/ The last hope for you is a Screen bug (but the rest still functionning)

ah after pluging phone in after volume down + power so my black screen it says "device unknown"
What is screen bug??
The rest is functioning I was able to get into recorvery from ROM Manager so somewhat its possible to get to that. Please help.

does 1one have other suggestions guys? I am hopeless now

Czepek said:
does 1one have other suggestions guys? I am hopeless now
Click to expand...
Click to collapse
If you can boot into the bootloader flash the factory image using fastboot
Sent from my Nexus 5 using XDA Free mobile app

Like I said there is no bootloader - only black screen

No acess to the recovery mode on Samsung

So I have a Samsung Galaxy Gran Prime Duos G530BT and I was installing the TWRP recovery mode on it, the app asked for restart the phone to test the recovery mode, but when I restarted it the phone didn't boot anymore. He just vibrate and nothing appers on the screen.
I can't even get acess to the recovery mode to fix it. Can someone help me?
(I try to use the flash tool since he doesn't boot, but the stock room don't have any scatterd file...)

something similar happend to me..
rxxern said:
So I have a Samsung Gran Prime Duos GM-530BT and I was installing the TWRP recovery mode on it, the app asked for restart the phone to test the recovery mode, but when I restarted it the phone didn't boot anymore. He just vibrate and nothing appers on the screen.
I can't even get acess to the recovery mode to fix it. Can someone help me?
(I try to use the flash tool since he doesn't boot, but the stock room don't have any scatterd file...)
Click to expand...
Click to collapse
same as yours but mine has logo displayed and i cant turn on or put in recovery mode can you please message me if you find a way to fix it?

HyperVenoms said:
same as yours but mine has logo displayed and i cant turn on or put in recovery mode can you please message me if you find a way to fix it?
Click to expand...
Click to collapse
Yeah, sure!
This might be stupid, but did you try use Odin? Since your logo appears, I think you're in a better condicion then me, lol.

No but i found a solution
rxxern said:
Yeah, sure!
This might be stupid, but did you try use Odin? Since your logo appears, I think you're in a better condicion then me, lol.
Click to expand...
Click to collapse
ok so i couldnt put it into recovery mode or anything it was stuck so i took out the battery then held volume down power and home then pressed down to restart device and it came on successfully i hope this also works for you

rxxern said:
So I have a Samsung Gran Prime Duos GM-530BT and I was installing the TWRP recovery mode on it, the app asked for restart the phone to test the recovery mode, but when I restarted it the phone didn't boot anymore. He just vibrate and nothing appers on the screen.
I can't even get acess to the recovery mode to fix it. Can someone help me?
(I try to use the flash tool since he doesn't boot, but the stock room don't have any scatterd file...)
Click to expand...
Click to collapse
Try to download its stockrom boot it into download mode not recovery since recovery doesnt work any more i think its volume - if not + ,power button and Home button then dow load ODIN and flash the it so as to guarentee it to boot up again.
link for the devices stock rom
#https://docs.google.com/uc?id=0B7pEcClQW-2JenF1cW9jb05OVlk&export=download
thanks enjoy!!

No that lucky
HyperVenoms said:
ok so i couldnt put it into recovery mode or anything it was stuck so i took out the battery then held volume down power and home then pressed down to restart device and it came on successfully i hope this also works for you
Click to expand...
Click to collapse
So lucky! I can't do that to mine, when I put the battery out and try to do this, my phone has no response. ):

out of options
marwachacha said:
Try to download its stockrom boot it into download mode not recovery since recovery doesnt work any more i think its volume - if not + ,power button and Home button then dow load ODIN and flash the it so as to guarentee it to boot up again.
link for the devices stock rom
thanks enjoy!!
Click to expand...
Click to collapse
Thanks for the tip, but I really think I hard brick my phone, he just vibrate when the battery is on, when I try to turn him on just with the charger I get no response, my computer cannot ever reconize him. An since it's a national model there isn't much support for it on the internet (now I do regret getting him). I opened him to try force the reconization, but I don't find the force preloader mode test point and there is no way I can get a JTAG on Brazil.
TWRP Recovery Mode f*** me really hard this time.
Now if someone could help me finding the colo/kolo/whatever point on my phone I would really appreciated.

rxxern said:
Thanks for the tip, but I really think I hard brick my phone, he just vibrate when the battery is on, when I try to turn him on just with the charger I get no response, my computer cannot ever reconize him. An since it's a national model there isn't much support for it on the internet (now I do regret getting him). I opened him to try force the reconization, but I don't find the force preloader mode test point and there is no way I can get a JTAG on Brazil.
TWRP Recovery Mode f*** me really hard this time.
Now if someone could help me finding the colo/kolo/whatever point on my phone I would really appreciated.
Click to expand...
Click to collapse
Am not much sure if ti is hard bricked since you sayed that it vibrates lets look how much characteristics of a bricked device of which it posseses so as to conmfirm that it is hard bricked.
Soft Brick - Struck inBoot loop
2. Super Brick - Stuck atflashing Factoryfs.IMG in ODIN . Also called as EMMC Bug
3. Hard Brick -Dead / Costly Paper weights
4. Dead Brick - No chargingbattery sign also - Mostly = Hard Brick; But there is a window of possibilityby a USB JIG for SamsungPhones.
5. OTA Brick - Encountereddue to updating OTA on a rooted Stock ROM
6. CM12 Brick - when CM12encountered a /data write error. Worst is ODIN Flashing Fails
7. Pixel Salad: This is a problemof the graphics unit or the screen which fails to display correctly the imageand put instead random colored pixels on some areas of the screen or the wholescreen. It’s hard to even let the other members know what you are facing sinceyour screenshots would be just clean as it would have been. This also requiresa need for hardware checking if reflashing ROM doesn't work.
Soft brick means a temporary problem, which could be fixed. Soft brick usuallyoccurs after installing custom rom(s) or incorrect installation procedure whichinstallation/manipulation of files like permission settings, erasing systemfiles that is not compatible with each phone.
SOFT BRICKED
PHYSICAL CHARACTERISTICS TO MENTION FEW ARE
Phone struck on OEM logo.
Phone struck on a ROM logo "bootanimation"
The phone does not simply power up
or any other you can add up
HARD BRICKED
PHYSICAL CHARACTERISTICS TO MENTION FEW ARE
· No signs that can turn on directly
· The Charging won't work.
· Phone not detected when connected to a PC
· The LED's do not light up immediately
· No Sound / Vibrate
· Your phone completely off (Paper Weight)
Simply put it cannot be repaired using SEUS, FLASHTOOL, ODIN or even PC COMPANION.

marwachacha said:
Am not much sure if ti is hard bricked since you sayed that it vibrates lets look how much characteristics of a bricked device of which it posseses so as to conmfirm that it is hard bricked.
Soft Brick - Struck inBoot loop
2. Super Brick - Stuck atflashing Factoryfs.IMG in ODIN . Also called as EMMC Bug
3. Hard Brick -Dead / Costly Paper weights
4. Dead Brick - No chargingbattery sign also - Mostly = Hard Brick; But there is a window of possibilityby a USB JIG for SamsungPhones.
5. OTA Brick - Encountereddue to updating OTA on a rooted Stock ROM
6. CM12 Brick - when CM12encountered a /data write error. Worst is ODIN Flashing Fails
7. Pixel Salad: This is a problemof the graphics unit or the screen which fails to display correctly the imageand put instead random colored pixels on some areas of the screen or the wholescreen. It’s hard to even let the other members know what you are facing sinceyour screenshots would be just clean as it would have been. This also requiresa need for hardware checking if reflashing ROM doesn't work.
Soft brick means a temporary problem, which could be fixed. Soft brick usuallyoccurs after installing custom rom(s) or incorrect installation procedure whichinstallation/manipulation of files like permission settings, erasing systemfiles that is not compatible with each phone.
SOFT BRICKED
PHYSICAL CHARACTERISTICS TO MENTION FEW ARE
Phone struck on OEM logo.
Phone struck on a ROM logo "bootanimation"
The phone does not simply power up
or any other you can add up
HARD BRICKED
PHYSICAL CHARACTERISTICS TO MENTION FEW ARE
· No signs that can turn on directly
· The Charging won't work.
· Phone not detected when connected to a PC
· The LED's do not light up immediately
· No Sound / Vibrate
· Your phone completely off (Paper Weight)
Simply put it cannot be repaired using SEUS, FLASHTOOL, ODIN or even PC COMPANION.
Click to expand...
Click to collapse
Even if it's not hard bricked I had no idea on how bring him into life again, since the only signal of life he gives me is the vibration with the battery on.
It could make my computer detect him it would be much easier.

hmmm
rxxern said:
Even if it's not hard bricked I had no idea on how bring him into life again, since the only signal of life he gives me is the vibration with the battery on.
It could make my computer detect him it would be much easier.
Click to expand...
Click to collapse
this may sound dumb but maybe your screen is broke i highly doubt it because of what happened but if you can feel the vibrations but not see the screen then maybe its the screen. There will probably be a way to fix it but im unsure. Its funny how you call your phone him

HyperVenoms said:
this may sound dumb but maybe your screen is broke i highly doubt it because of what happened but if you can feel the vibrations but not see the screen then maybe its the screen. There will probably be a way to fix it but im unsure. Its funny how you call your phone him
Click to expand...
Click to collapse
I didn't mention this but the screen also blinks when is vibrating so... And if It was the screen the computer should reconized the phone, shouldn't?
Haha, english it's not my native language, so I get confuse sometimes, and i don't know calling it him sounds more right for me (?????).

rxxern said:
Even if it's not hard bricked I had no idea on how bring him into life again, since the only signal of life he gives me is the vibration with the battery on.
It could make my computer detect him it would be much easier.
Click to expand...
Click to collapse
rxxern said:
I didn't mention this but the screen also blinks when is vibrating so... And if It was the screen the computer should reconized the phone, shouldn't?
Haha, english it's not my native language, so I get confuse sometimes, and i don't know calling it him sounds more right for me (?????).
Click to expand...
Click to collapse
haha ok, i habe no idea what to do wiith your phone try searching other threads maybe ???

rxxern said:
I didn't mention this but the screen also blinks when is vibrating so... And if It was the screen the computer should reconized the phone, shouldn't?
Haha, english it's not my native language, so I get confuse sometimes, and i don't know calling it him sounds more right for me (?????).
Click to expand...
Click to collapse
also in advance try to change the usb cable which you are using to connect (him) with your computer as well as try different Pc's may Be yours might have some usb port drivers corrupted also try to install the ADB interface drivers in your pc so as you can enhance your Pc detect the devices even if they are powered off gues it will work still i have hope with your (him) buddy!!!

Nothing better than xda.

I am having the same problem with my G530BT. Managed to solve ?
rxxern said:
So I have a Samsung Galaxy Gran Prime Duos G530BT and I was installing the TWRP recovery mode on it, the app asked for restart the phone to test the recovery mode, but when I restarted it the phone didn't boot anymore. He just vibrate and nothing appers on the screen.
I can't even get acess to the recovery mode to fix it. Can someone help me?
(I try to use the flash tool since he doesn't boot, but the stock room don't have any scatterd file...)
Click to expand...
Click to collapse
I am having the same problem with my G530BT. Managed to solve ?

Raphaelfla said:
I am having the same problem with my G530BT. Managed to solve ?
Click to expand...
Click to collapse
Ow, one year latter I don't think this will help you anymore, but just in case someone has the same question: I didn't solve the problem, I took it to the Samsung assistence and discover that the motherboard was damaged, they would have to replace it.

screen flickering issue plzzzz

guys i was using miui 8 rom with phantom kernel
while using it my screen started flickering and just got black
when turning on my phone screen starts for sometime and then same story
also when i turn on my phone in recovery same thing happens
can anyone plz tell me what the problem is
it first shows boot logo and then goes black

If it is happening in recovery too,then it might be a hardware issue.
But try flashing stock ROM.See if that solves the problem.

gauthamkithu said:
If it is happening in recovery too,then it might be a hardware issue.
But try flashing stock ROM.See if that solves the problem.
Click to expand...
Click to collapse
yes bro it is happening in recovery also
is it a display problem
if not what probably it could

Junaid Shafi said:
yes bro it is happening in recovery also
is it a display problem
if not what probably it could
Click to expand...
Click to collapse
Phantom kernal over clocks your GPU.This might also be the cause of flickering.So try flashing the stock rom and see what happens.

gauthamkithu said:
Phantom kernal over clocks your GPU.This might also be the cause of flickering.So try flashing the stock rom and see what happens.
Click to expand...
Click to collapse
bro device is not booting and not booting into recovery so i cant flash

Junaid Shafi said:
bro device is not booting and not booting into recovery so i cant flash
Click to expand...
Click to collapse
is there any way to flash using bootloader

Is bootloader booting fine?
Sent from my Lenovo A6000 Plus

My phone is lenovo a6000plus ,last 3days bacj its upgraded to lollipop 5.2 but from yesterday the screen is flickering continuously how to fix this

Junaid Shafi said:
guys i was using miui 8 rom with phantom kernel
while using it my screen started flickering and just got black
when turning on my phone screen starts for sometime and then same story
also when i turn on my phone in recovery same thing happens
can anyone plz tell me what the problem is
it first shows boot logo and then goes black
Click to expand...
Click to collapse
u can use qfil method to install stock rom but before that checkout is it motherboard problem or the display problem.. if its motherboard problem u should go to service center

varun4495 said:
u can use qfil method to install stock rom but before that checkout is it motherboard problem or the display problem.. If its motherboard problem u should go to service center
Click to expand...
Click to collapse
thanks for your response
but somehow i restarted my phone after 3 days and it started working as usual
i just thought that i had lost it
but by allah's sake it is back to life

ksteja said:
my phone is lenovo a6000plus ,last 3days bacj its upgraded to lollipop 5.2 but from yesterday the screen is flickering continuously how to fix this
Click to expand...
Click to collapse
do u got an update to stock 5.2
and by the way is volte working in that

Screen Flickering is common issue the main cause is because the synaptic driver is not quite compatible to ft5x06 which results in flicker around some interval there is no solution for it lenovo did sh!t with the driver the way out is only rewriting and adapting the driver for our phone accordingly