failed to mount /efs - Verizon Samsung Galaxy S III

is there a fix for this after going to the 4.3 update. i flashed the stock image from odin and now it am having this issue. My phone also has a black transparent popup with yellow lettering. I believe it is in factory mode. There is no data in the efs file. I think that is the overall issue right now. Does anyone have any help/ suggestions?
Here is what I have done to try and fix this issue
Reflash with odin
reflash with keis
factory reset through operating system
factory reset through recovery
reflash with odin using pit file as well

Dullawolf said:
is there a fix for this after going to the 4.3 update. i flashed the stock image from odin and now it am having this issue. My phone also has a black transparent popup with yellow lettering. I believe it is in factory mode. There is no data in the efs file. I think that is the overall issue right now. Does anyone have any help/ suggestions?
Click to expand...
Click to collapse
So you're on stock 4.3 and then you Odin flash 4.3 again?

buhohitr said:
So you're on stock 4.3 and then you Odin flash 4.3 again?
Click to expand...
Click to collapse
yes, basically.

Dullawolf said:
yes, basically.
Click to expand...
Click to collapse
How about do a factory reset and reflash again? Check make sure your download file is good too just in case.

buhohitr said:
How about do a factory reset and reflash again? Check make sure your download file is good too just in case.
Click to expand...
Click to collapse
did all that like three times.
did factory reset through phone os and through recovery
flashed 4.3 through odin and through kies

OK the last resort probably flash full stock with a PIT file.
Sent from my Galaxy Nexus using xda premium

buhohitr said:
OK the last resort probably flash full stock with a PIT file.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
PIT file?? link?

buhohitr said:
OK the last resort probably flash full stock with a PIT file.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
n/m found it here http://forum.xda-developers.com/showthread.php?t=2586319

Dullawolf said:
n/m found it here http://forum.xda-developers.com/showthread.php?t=2586319
Click to expand...
Click to collapse
pit file didnt work either! dammit!

Anyone else have any suggestions?

Dullawolf said:
Anyone else have any suggestions?
Click to expand...
Click to collapse
So currently can you boot up your phone?

buhohitr said:
So currently can you boot up your phone?
Click to expand...
Click to collapse
well, earlier today i was able to. not so much any more. can't even get into download mode. the only thing that happens now is when i plug it into my computer it says it failed to install hs-usb qdloader drivers.
only time i can get any lights to turn on is when i pull the battery and sim card. and just the led comes on red.
looks like i have myself a paperweight :/

Dullawolf said:
well, earlier today i was able to. not so much any more. can't even get into download mode. the only thing that happens now is when i plug it into my computer it says it failed to install hs-usb qdloader drivers.
only time i can get any lights to turn on is when i pull the battery and sim card. and just the led comes on red.
looks like i have myself a paperweight :/
Click to expand...
Click to collapse
Have to try the hardbrick method (boot off the sdcard) http://forum.xda-developers.com/showthread.php?t=2581166
If you can boot up, we may have a chance to fix the efs issue.

buhohitr said:
Have to try the hardbrick method (boot off the sdcard) http://forum.xda-developers.com/showthread.php?t=2581166
If you can boot up, we may have a chance to fix the efs issue.
Click to expand...
Click to collapse
i would like to try this, but i dont want to mess up my 16gb class 10 micro sd. i tried it with a 4gb class 4 and it wont let me reformat it back, even with the utility he directed us to.

Its safe. I don't think you can mess up the card.
Sent from my Galaxy Nexus using Tapatalk

buhohitr said:
Its safe. I don't think you can mess up the card.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
will this work even if the phone isn't booting? i mean nothing at all. it wont acknowledge anything unless i pull the battery and sim card and plug it into a computer.

Dullawolf said:
will this work even if the phone isn't booting? i mean nothing at all. it wont acknowledge anything unless i pull the battery and sim card and plug it into a computer.
Click to expand...
Click to collapse
If you read the description "how to recover from a hard brick", the phone don't boot at all (appear to be dead). That because there's nothing there to boot, the SDcard mount a new boot image to assist the phone to boot. Currently you don't have much choice; 1) try the hardbrick method 2) send out for JTAG repair 3) buy a new phone or if still under warranty then send out for replacement.

buhohitr said:
If you read the description "how to recover from a hard brick", the phone don't boot at all (appear to be dead). That because there's nothing there to boot, the SDcard mount a new boot image to assist the phone to boot. Currently you don't have much choice; 1) try the hardbrick method 2) send out for JTAG repair 3) buy a new phone or if still under warranty then send out for replacement.
Click to expand...
Click to collapse
fair enough. i also bought a jig, to see if that will help. i will try the sd card thing as well.
thanks for your help. it is much appreciated.

buhohitr said:
Have to try the hardbrick method (boot off the sdcard) http://forum.xda-developers.com/showthread.php?t=2581166
If you can boot up, we may have a chance to fix the efs issue.
Click to expand...
Click to collapse
welp, this didn't work. i will be getting the jig on monday. i will try that then.

Dullawolf said:
welp, this didn't work. i will be getting the jig on monday. i will try that then.
Click to expand...
Click to collapse
You need to try couple times (4-5 times), rewrite the image to sd try again and repeat this process a few times.(each time to retry, you need to rewrite the image then try).

Related

[Q] Helping a noob

Hi there!
I have a Galaxy Tab 7 and I am a noob on this development stufs.
I am trying to install this version on it:
cafe-ti.blog.br/1835~samsung-galaxy-tab-7-gt-p1000-android-jelly-bean-cm10
And looks like the language is pretty simple but I have no clue how to do it...I mean, I trie using Odin..did not work...
I tried this instead:
[wiki.cyanogenmod.com/wiki/Samsung_Galaxy_Tab_(P1000L):_Full_Update_Guide
but the Recovery mode does not work!
There is any step by step non expert language tutorial to how let the Tab 7" with the CM10?
Thanks from Brazil
Rafael
You try this?
http://forum.xda-developers.com/showthread.php?t=1542897
orangekid said:
You try this?
http://forum.xda-developers.com/showthread.php?t=1542897
Click to expand...
Click to collapse
My one is the 7", not the 7'7" and its the GT-P1000L..
It will work on it?
rafapiloto195 said:
My one is the 7", not the 7'7" and its the GT-P1000L..
It will work on it?
Click to expand...
Click to collapse
I tried this video, passin to 2.3.6 first, using Odin..
youtube.com/watch?v=fXDvq5SaA70&feature=relmfu
workd well, however, after flashing, is not turning on again...
What may can be?
Oh yeah don't use the 7.7 forum then...
You Odin flashed a ROM and now the device won't even turn on? Or is it just boot loop?
orangekid said:
Oh yeah don't use the 7.7 forum then...
You Odin flashed a ROM and now the device won't even turn on? Or is it just boot loop?
Click to expand...
Click to collapse
There is no sign...does not even turn on...
black screen only..nothing...
rafapiloto195 said:
There is no sign...does not even turn on...
black screen only..nothing...
Click to expand...
Click to collapse
Can you link the ROM you Odin flashed?
Sounds like you bricked your device...
edit: if you plug it into your computer does anything pop up on the computer?
orangekid said:
Can you link the ROM you Odin flashed?
Sounds like you bricked your device...
edit: if you plug it into your computer does anything pop up on the computer?
Click to expand...
Click to collapse
I had to come to work and let it at home...
Well, as berfore flash it I let the USB on the debugging, I will track the oneclick root directly to se if at least will get a conecction with a computer;
I will try to send it to the dealer as well.
I believe as I let it on the 2.3.6, wich is the same one running on Kies, still under warranty to perform a hard brick recovery.
Let's see.
Thanks..I'll keep you guys posted.
Yeah let us know, hopefully we can do something, not sure why a GB Stock Odin flash would brick it.
orangekid said:
Yeah let us know, hopefully we can do something, not sure why a GB Stock Odin flash would brick it.
Click to expand...
Click to collapse
Just replying to your question, I flash it with the one on the youtube video link I posted:
www.youtube.com/redirect?q=https://...yuzT76vVlfj4vSE98MTM0ODM0OTI1NUAxMzQ4MjYyODU1
rafapiloto195 said:
Just replying to your question, I flash it with the one on the youtube video link I posted:
www.youtube.com/redirect?q=https://...yuzT76vVlfj4vSE98MTM0ODM0OTI1NUAxMzQ4MjYyODU1
Click to expand...
Click to collapse
Well, looks like it is working again,
however, when I try to turn on on the recovery mode to wipe data,
it shows E: MBR Checksum error
Internal MMC checksum verify failed.
Any ideas?
great idea
+1 orangekid
asdera-and said:
+1 orangekid
Click to expand...
Click to collapse
Ok! Is on the 2.3.3 now.
I want to put the Cyanogen 4.1.1 as described here:
http://forum.xda-developers.com/showthread.php?t=1871113
However, when I tried it shows me the error I mentioned above and also
Failed to verify whole-file signature...
Then , I was able to come to CMW where I should install the Cyanoi 4.1.1 however keeps showing me the error:
E: Can't moun /emmc/
Ideas?
OK
now I tried this room:
Rom: Overcome + Overcome Kernel
Following the guide step by step and then the E: looks like to be damaged. I can not even turn it on again.
Just when I put it to charge, it will show the brick scree (the fone and the computer)...
I am almost givin up...
Does your tab have an SD card in it?
If so try a different one, if not odin 100% stock, then do the root, and ROM flash again.

[Q] Serieus problem with the Nexus 5

Hello XDA developers!
I hope you can help me with a serieus problem on my Nexus5 Device!
Let's tell you my little adventure with my Nexus5 :
First my Nexus5 Device worked perfectly, but then the radiobaseband and the sensors magically dissapeared!
https://db.tt/cdZiSukZ i've tooked some screenshots of it on dropbox.
Then I Flashed the factory image for my device by following this guide: http://forum.xda-developers.com/showthread.php?t=2513701
And it started to work perfectly, till now........
after about a week i watched a unspecified video on Google Chrome and the screen freezed ( not literally )
So I hold the power button and turn it off, turn it back on and i got a infinity bootloop.
So I flash again the official factory image and it can't flash my system?
its look like this;
trying to flash system.img....
FAILED
the rest of the process flash succesfull until it reach system.img
and a friend of mine therinsem tried to add a custom recovery and it didn't work, so we flashed again the factory image and it still FAILED,
to flash system.img the rest of the process work until it reach system.img.
now it doesn't even boot? it's only going straight into fastboot-mode
and if i press in fastboot-mode recoverymode than it shows nothing? ( i think because we tried to flash a custom recovery )
- iv'e tried on a bunch of diffrent windows laptop's
- i can't access the internal storage of the device
- i can still '' side-load'' I think
so this is my problem with the nexus5, does anyone have a solution?:crying:
Download the factory image again and make sure the md5 checks. Then try again
There's another thread around here somewhere with pretty much the same issue. Sounds like bad memory. From fastboot try:
Code:
fasboot format system
If that succeeds reflash the factory image. If that fails your most likely looking at RMA.
I wouldn't really since google will charge you twice for tampering with the imei
Sent from my Nexus 5
dicecuber said:
I wouldn't really since google will charge you twice for tampering with the imei
Sent from my Nexus 5
Click to expand...
Click to collapse
What? Who's taking about imei?
jd1639 said:
Download the factory image again and make sure the md5 checks. Then try again
Click to expand...
Click to collapse
Thank you for a answer! i will try it and will give a update status soon.
jd1639 said:
What? Who's taking about imei?
Click to expand...
Click to collapse
Judging from pictures, the stock imei is unknown. I'd refrain from rmaing it just yet
Sent from my Nexus 5
dicecuber said:
Judging from pictures, the stock imei is unknown. I'd refrain from rmaing it just yet
Sent from my Nexus 5
Click to expand...
Click to collapse
Sometimes it happens that you lose your imei. Flashing the factor image can bring it back. Nothing nefarious going on
dicecuber said:
Judging from pictures, the stock imei is unknown. I'd refrain from rmaing it just yet
Click to expand...
Click to collapse
Ummmmm? That's why where trying to help the OP recover. lol OP you can also run this and see what the output is:
Code:
fasboot getvar all
^someone suggested Op rma it. I suggested he refrain from doing that
Sent from my Nexus 5
theesotericone said:
Ummmmm? That's why where trying to help the OP recover. lol OP you can also run this and see what the output is:
Code:
fasboot getvar all
Click to expand...
Click to collapse
theesotericone said:
There's another thread around here somewhere with pretty much the same issue. Sounds like bad memory. From fastboot try:
Code:
fasboot format system
If that succeeds reflash the factory image. If that fails your most likely looking at RMA.
Click to expand...
Click to collapse
Thank you very much for the answers! i will setup my laptop again and will use your advice, to recover my device! ( that rhymes! )
Tomorrow i will give a update, i am going to sleep! good night folk!
tomaszcs said:
Thank you very much for the answers! i will setup my laptop again and will use your advice, to recover my device! ( that rhymes! )
Tomorrow i will give a update, i am going to sleep! good night folk!
Click to expand...
Click to collapse
Formatting system did not work.
I helped Tomasz doing this

[Q] Help Please!

So I have a VZW S3 on NE1 rooted and running xposed. I am not sure what module it was that I installed but my phone is now stuck with the SystemUI constantly crashing to the point of me being unable to use the phone. Then I, like a moron, Unrooted my phone thinking that would stop the issue. It didn't. I do have usb debugging enabled and my phone connects to the computer. Can I just boot into recovery and use the Xposed-disabler-recovery zip to fix this? will that wreck my phone since VZW is so annoying? Would that wipe my memory? And if that doesn't work what else could I do except pull everything I can off my phone and and reflash the entire thing using Odin?
Thanks a million!
J CGPhones said:
So I have a VZW S3 on NE1 rooted and running xposed. I am not sure what module it was that I installed but my phone is now stuck with the SystemUI constantly crashing to the point of me being unable to use the phone. Then I, like a moron, Unrooted my phone thinking that would stop the issue. It didn't. I do have usb debugging enabled and my phone connects to the computer. Can I just boot into recovery and use the Xposed-disabler-recovery zip to fix this? will that wreck my phone since VZW is so annoying? Would that wipe my memory? And if that doesn't work what else could I do except pull everything I can off my phone and and reflash the entire thing using Odin?
Thanks a million!
Click to expand...
Click to collapse
There is an option in xposed to uninstall.
buhohitr said:
There is an option in xposed to uninstall.
Click to expand...
Click to collapse
Right but I can't even get past my homescreen at the moment
J CGPhones said:
Right but I can't even get past my homescreen at the moment
Click to expand...
Click to collapse
OK, I see then just flash the xposed-disabled-recovery.zip using custom recovery. If you locked with only stock recovery, you may need to do a factory reset,
buhohitr said:
OK, I see then just flash the xposed-disabled-recovery.zip.
Click to expand...
Click to collapse
From stock recovery? That won't make my phone trip the fuse for modifying the system? By the way Thank you SO much for replying.
J CGPhones said:
From stock recovery? That won't make my phone trip the fuse for modifying the system? By the way Thank you SO much for replying.
Click to expand...
Click to collapse
I accidentally hit send before finished typing, if you only have stock then a factory reset probably your best bet,
buhohitr said:
I accidentally hit send before finished typing, if you only have stock then a factory reset probably your best bet,
Click to expand...
Click to collapse
Sigh that's what I was afraid of. Oh well I'll get going on pulling all of my files off. Thanks so much for all your help.

CF-Auto Root risk?

Hello, I wanted to know what the risks are that my S6 will bootloop/brick etc, and if I could recover them. I have checked my USB-connection multiple times by copying large files back and forth between PC and phone, so that is perfectly fine. I have an unlocked bootloader, usb-debugging enabled and no reaktivation lock. I dont want to risk breaking my 3 week old phone and still paying until october, just because of a custom rom. Thanks in advance!
Actually, you can't full-brick the S6 anyway.
Just flash it. If something gonna bad, rescue the phone via Smart Switch
You will trip Knox and potentially void your warranty.
forumber2 said:
Actually, you can't full-brick the S6 anyway.
Just flash it. If something gonna bad, rescue the phone via Smart Switch
Click to expand...
Click to collapse
I dont care about my warranty. I never hurt my precous electronics, you could say its a habit. I only need my warranty for software wise errors, but I flashed things quite a few times on other phones, so I got the drill. So its impossible to brick my S6 permanantly? As long as I can restore it to factory status when something goes wrong, I am happy.
Ironknight456 said:
I dont care about my warranty. I never hurt my precous electronics, you could say its a habit. I only need my warranty for software wise errors, but I flashed things quite a few times on other phones, so I got the drill. So its impossible to brick my S6 permanantly? As long as I can restore it to factory status when something goes wrong, I am happy.
Click to expand...
Click to collapse
Maybe filling zero on param partition will cause a non-recoverable fully brick
There's no way (that i know) to full brick the device.
forumber2 said:
Maybe filling zero on param partition will cause a non-recoverable fully brick
There's no way (that i know) to full brick the device.
Click to expand...
Click to collapse
I just want to flash. Never repartitioned, and also never will. So repartitioning the memory to 0 will brick it, and nothing else? Soryy if I am getting on your nerves, just want to clarify
Ironknight456 said:
I just want to flash. Never repartitioned, and also never will. So repartitioning the memory to 0 will brick it, and nothing else? Soryy if I am getting on your nerves, just want to clarify
Click to expand...
Click to collapse
I didn't say anything about repartitioning, and we can't write zeros on complete eMMC anyway (cuz there's a access protection on bootloader partitions)
There's a partition called "PARAM" on Samsung devices, it is /dev/block/sda4 on S6. This partition contains bootlogo and other bootloader images (like the warning screen on download mode).
We can change the bootlogo by changing image in this partition. But, if we type
dd if=/dev/zero of=/dev/block/sda4
at terminal on phone, it is not gonna boot again. Because when we try to boot the phone up, bootloader can't find proper image to show on screen at PARAM partition, so it will fail. We can't boot it on download mode because the same reason.
forumber2 said:
I didn't say anything about repartitioning, and we can't write zeros on complete eMMC anyway (cuz there's a access protection on bootloader partitions)
There's a partition called "PARAM" on Samsung devices, it is /dev/block/sda4 on S6. This partition contains bootlogo and other bootloader images (like the warning screen on download mode).
We can change the bootlogo by changing image in this partition. But, if we type
dd if=/dev/zero of=/dev/block/sda4
at terminal on phone, it is not gonna boot again. Because when we try to boot the phone up, bootloader can't find proper image to show on screen at PARAM partition, so it will fail. We can't boot it on download mode because the same reason.
Click to expand...
Click to collapse
I never use the terminal, only flashing for root, twrp and custom roms. Thats what I need cf auto root for. I dont like to tinker around with the inception layer of my smartphone, too risky for me. Thanks for all your answers guys, now I know as long as I only flash, my device cant break Have a nice day!
Everything worked fine! Root and TWRP going smooth! I dont know how to thank you enough <3
a piece of advice - make a backup and store it to computer before venturing further
Ironknight456 said:
Everything worked fine! Root and TWRP going smooth! I dont know how to thank you enough <3
Click to expand...
Click to collapse
Which TWRP did you flash? Official or the one that needs a kernel change to get it working? And how did you go about it?
Sent from my SM-G920F using Tapatalk
toole said:
Which TWRP did you flash? Official or the one that needs a kernel change to get it working? And how did you go about it?
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
I flashed the one from ManhIT, and I just did it with AP in Odin.
Ironknight456 said:
I flashed the one from ManhIT, and I just did it with AP in Odin.
Click to expand...
Click to collapse
Did you change kernel.?
Sent from my SM-G920F using Tapatalk
toole said:
Did you change kernel.?
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
Nope
Ironknight456 said:
Nope
Click to expand...
Click to collapse
And can were you able to mount an external sd card through OTG in the twrp recovery?
toole said:
And can were you able to mount an external sd card through OTG in the twrp recovery?
Click to expand...
Click to collapse
I dont even have an OTG. And there isnt a SD slot. So I kinda dont understand your question xD
Ironknight456 said:
I dont even have an OTG. And there isnt a SD slot. So I kinda dont understand your question xD
Click to expand...
Click to collapse
I meant a USB stick using an OTG .
Sent from my SM-G920F using Tapatalk
toole said:
I meant a USB stick using an OTG .
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
I still dont have an OTG.

LG-H959 stuck on logo

Hello,
I have an lg-h959 stuck on logo and i want to flash it....problem is i have never flashed an lg before and also i dont know what region it is....can someone help me out?
andrew21 said:
Hello,
I have an lg-h959 stuck on logo and i want to flash it....problem is i have never flashed an lg before and also i dont know what region it is....can someone help me out?
Click to expand...
Click to collapse
What's the reason it's stuck on the logo? Did you do something like attempt root or anything?
If you haven't done anything to cause it did you try performing a factory reset?
It could be a hardware issue or battery problem if you didn't do anything to cause the stuck on LG logo problem.
Sent from my iPhone using Tapatalk
hyelton said:
What's the reason it's stuck on the logo? Did you do something like attempt root or anything?
If you haven't done anything to cause it did you try performing a factory reset?
It could be a hardware issue or battery problem if you didn't do anything to cause the stuck on LG logo problem.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I didnt root the phone, it just goes on and off, i want to try flashing it with LG Flash Tool 2014...i cant hard reset either since it just doesnt go to factory set mode.....can you provide me with correct firmware pls?
andrew21 said:
I didnt root the phone, it just goes on and off, i want to try flashing it with LG Flash Tool 2014...i cant hard reset either since it just doesnt go to factory set mode.....can you provide me with correct firmware pls?
Click to expand...
Click to collapse
So with the phone off you've tired holding down vol up and power or vol down and power to attempt to factory reset? Your phone doesn't need to boot into the OS to factory reset it...
Also normally this doesn't happen unless it's a hardware issue since you didn't do anything to cause it.
Was the device running MM? If so you need to use LGUP. Lg flashtools 2014 won't work if your running MM 6.0.
Just check out the general section there's a back to stock guide with links to firmwares.
Sent from my iPhone using Tapatalk
Ok so I checked it, can you tell me which stock firmware to download, also my phone reboots and I don't know if it running on mm
Hello, my phone constantly reboots and stuck on logo, how do I know android version of this phone? Is there any tool that can help me do this? I can go to factory set mode and download mode
andrew21 said:
Hello, my phone constantly reboots and stuck on logo, how do I know android version of this phone? Is there any tool that can help me do this?
Click to expand...
Click to collapse
Just use LGUP. And flash your models kdz. There's no specific one just make sure it matches your model.
Sent from my iPhone using Tapatalk
hyelton said:
Just use LGUP. And flash your models kdz. There's no specific one just make sure it matches your model.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
So, i downloaded LGUP AND drivers and H95920a_00_0624.kdz file...will that do it? I know the flashing procedure.
andrew21 said:
So, i downloaded LGUP AND drivers and H95920a_00_0624.kdz file...will that do it? I know the flashing procedure.
Click to expand...
Click to collapse
Yes. Just place your phone in download mode.
If your phone still does the same after flashing it's either your battery or a hardware failure.
Sent from my iPhone using Tapatalk
hyelton said:
Yes. Just place your phone in download mode.
If your phone still does the same after flashing it's either your battery or a hardware failure
Ok thanks will try tomorrow and post results
Click to expand...
Click to collapse
Just one more question, can I select refurbish in LGUP and how to select file in this procedure?
andrew21 said:
Just one more question, can I select refurbish in LGUP and how to select file in this procedure?
Click to expand...
Click to collapse
You would choose refurbish
Sent from my iPhone using Tapatalk
Ok will try it out later tomorrow
A couple of us had the same problem. Just buy a new battery and replace it yourself. It fixed the bootloop for all of us.
z.coniglietti said:
A couple of us had the same problem. Just buy a new battery and replace it yourself. It fixed the bootloop for all of us.
Click to expand...
Click to collapse
Ok will do that if software doesnt work
z.coniglietti said:
A couple of us had the same problem. Just buy a new battery and replace it yourself. It fixed the bootloop for all of us.
Click to expand...
Click to collapse
I flashed the phone but same problem...now ill try out new battery and post results tomorrow
Just search the forum and YouTube for lg g flex 2 bootloop and you'll see. I was in the same situation as well and that helped. I replaced it multiple times and I even baked the motherboard in the oven. Just the battery was the issue and thank God nothing worse. And the battery is like 10$ so not too much. Hope you fix it.
z.coniglietti said:
Just search the forum and YouTube for lg g flex 2 bootloop and you'll see. I was in the same situation as well and that helped. I replaced it multiple times and I even baked the motherboard in the oven. Just the battery was the issue and thank God nothing worse. And the battery is like 10$ so not too much. Hope you fix it.
Click to expand...
Click to collapse
Guys problem solved after changing battery...

Categories

Resources