Emmc error in boarddiag - Sprint LG G3

Hello guys, hope you doing well... I've an serious problem with my main phone. First, thank you for taking the time to read my story.
I have an Sprint LG G3 32GB since 2 monts ago and it was performing very well. Then I've flashed Resurrection Remix and a custom kernel on it and everything worked perfectly until some days back. I came back from school and left my data opened since the morning and the phone was discharged. I putted it in charge and was sending some messages on whatsapp. I tried to play some music but the phone was not making any sound and it locked on lockscreen and wasn't able to unlock it. Thought it was an OS bug and tried to reboot. While trying I felt asleep and left the phone in charge. Some hours later, the phone won't just boot and in TWRP, it shows Internal storage OMB.
I've waited some time and tried again then it came and I've restored the KitKat stock ROM. After that, the phone started bootlooping and freezing in logo. I was always facing Internal storage OMB and corrupted partition (cache, userdata, system, etc...).
2 days after, I've managed to flash an stock and fresh install TOT via LG FLashTool. The first time, the process didn't worked and I re-tried and then it flashed successfully the phone rebooted to Factory Reset Status 2. I've rebooted and it started with the QHS 9008 Loader COM. I've used boarddiag and restoring stock partitions and tried to flash again via LGFlashtool but the phone will just reboot during flashing in Download Mode and come back in QHS Loader.
This morning, I've sucessfully restored everything and the phone even booted up. It was discharged so I turned it off and left it in charge. Since 3 hours ago, when I try to start the phone, it may freeze on LG Logo or just stay in QHS with everything black. Managed to try AP CHECK and EMMC TEST but AP Pass and EMMC gives me "Error while trying to read partition from EMMC". Basically, that means that my EMMC has fried out or have been damaged. BUT, SURPRISE, sometimes the phone will boot up normally and work for 2 to 5 minutes and power off again and going back to QHS.
NOTE:
-I can't access download mode
-I've flashed the ZV6 cause that's the only ROM who restored via boarddiag and flashed successfully via Download mode
- Also, I've remarked that in the storage page in settings, the phone will show 9GB available and put 21GB in MISC unusable. That's anormal...
THANKS YOU for reading until here.
This is my main phone, any help would be appreciated thanks a lot for responding.

SOLVED
Unmonted the phone and heated a little bit the EMMC chip and putted an small paper in other to make some pressure and remounted.
Everything worked nicely.
Am know facing unlocking issue

Related

[Q] SM-N900P is stuck in a boot loop

This is the problem I am having with my Samsung Galaxy Note 3 (SM-N900P). This problem just popped up out of the blue on a stock ROM a few days ago and nothing I have tried has gotten close to fixing the issue
Description:
a) The boot sequence repeats in a loop with no more sound. The phone would reboot at the Sprint splash screen
What I've done so far:
a) Pulled the battery and depleted the capacitors
b) Installed TWRP and did a complete wipe
c) Tried installing a custom ROM to see if the issue persisted. ROMs failed to install as /system was being sketchy (at times it was reporting 0MB for partition and then an actual value after repair). When I managed to get a ROM to install still stuck in the boot loop
d) Used Odin to do a full restore to a stock NC5 ROM. The phone got up to initial configuration page and then rebooted, now only gets to the Samsung splash screen before rebooting
Items that I can get into:
Recovery mode
Download mode
I have a 30 second video of it rebooting but cannot post it currently due to the forum rules
Question:
Is this issue fixable or is it a sign of internal memory failure?
Try an older version of TWRP, i.e. 2.8.5.0
Or, try a different recovery.
I'm not sure that it will work, but it's worth a try.
Good luck!
Are you doing it this way?
http://forum.xda-developers.com/showthread.php?t=3069667
rbeavers said:
Are you doing it this way?
http://forum.xda-developers.com/showthread.php?t=3069667
Click to expand...
Click to collapse
I didn't notice that but I just installed TWRP 2.8.0.0 through Odin (like a few minutes ago). Phone actually managed to get to the stock recovery image config screen and was working as long as the cable was still attached to the computer.
As soon as I removed the cable it went straight back to the boot loop
SubRyan said:
I didn't notice that but I just installed TWRP 2.8.0.0 through Odin (like a few minutes ago). Phone actually managed to get to the stock recovery image config screen and was working as long as the cable was still attached to the computer.
As soon as I removed the cable it went straight back to the boot loop
Click to expand...
Click to collapse
Here is what you need to do. First pull battery, reinstall. If you can boot into twrp recovery, fine wipe everything i.e. caches, system, data, etc. If you are on a stock recovery do a factory reset. Pull battery, reinstall and boot into download mode.
NOW let's go to work. First use odin to flash stock NC5 tar. Chances are it will bootloop, STOP !!!! don't panic. Just reflash with odin again. The second time it should take. Remember that your device is setting up for first time use. This will take 3-5 minutes, sitting at the Samsung logo. Since didn't list the most important thing which is what OS you where on where the device Borked, or what you where doing with the device when it Borked. I'm going to assume it was on 4.4.4 and you tried to downgrade to 4.4.2 NC5. In which case a bootloop on the first bootup after a downgrade is normal, you have to flash twice to reset the bootloader. For more info click on rom flashing basics in my signature. Enjoy !!!
Problem solved. I started getting suspicious when the phone would boot up with the charging cable attached to the computer today
The issue was an aftermarket Mugen Power battery that developed a fault. Put the stock battery back in and problem resolved
Thanks for the help guys

[Q] Recovering contacts from a soft bricked S2

Basic info: phone is not rooted, the only messing I have done with it was to flash an updated official firmware via Odin (2 years ago) and after that even Kies recognised the firmware as the one I should have.
Yesterday I had a freeze at ~44% battery, did a reset and the phone booted with 0% battery. It switched off, so I took the battery out, put it back in and swtiched it on again. It showed 10% battery, but before completely booting up it froze again. From this point on every time I switch it on it gets to the pulsing 'SAMSUNG' screen at startup and stays there forever.
I am buying a new battery tomorrow. I have researched some ways I can recover the phone, but I am not sure if they will wipe the data. In particular, I would very much like to save my contacts. Is there a way to do this? For example, I read that to flash CWM recovery with Odin I need to unlock bootloader, which will wipe my data. Would one of the various data recovery softwares work in this case (Yodot, Dr.Fone)? Can I get an update to the firmware to my SD card and apply it from the stock recovery, possibly not wiping the phone and recovering the OS?
Also, FYI, I can get to recovery mode, to download mode, but not to safe mode.

Deleted boot partition, won't boot into fastboot mode, can't access anything

Hi all,
I recently installed Lineage 14.1 on my XT912 using safestrap, I decided that I wanted a larger Gapps package than pico, so I went to reinstall lineage and Gapps.
I was doing this away from home with a Linux PC instead of my normal windows one, and I ended up not being able to push over the larger Gapps file.
Then I did a really dumb thing that I didn't know would be a problem at the time, I restarted the device before reinstalling Lineage.
So I had softbricked it.
Then I tried using RSD lite to flash the stock XT912 ROM, but I ended up finding out that it would fail unless I erased the partitions I was trying to write to, so I went and erased every partition
including the boot partition.
When I went back to flash it I found that the battery had dropped below 80%, so fastboot no longer let me flash it.
So not knowing that I absolutely could not turn it off now that I had erased the boot partition, I went and disconnected the battery and soldered my Li-Po charger to the battery so I could charge it manually manually.
Stupid me.
When I went and tried to boot into fastboot I got a black screen and when I plugged the phone into my PC it would just keep throwing USB errors while disconnecting and reconnecting over and over again.
I'm pretty dang sure it's hardbricked now, but it there's anyone out there who has a solution to this, I'd love to hear it.
Thanks,
-Alec

My S3 is in a TWRP loop and the phone has a broken Charging/USB port

Hey all,
I installed Omega ROM v6.1 on my i9300 and for a while it was good.
Unfortunately one day it decided to crash and crash hard.
It was stuck in a boot loop and so I decided to wipe all the system, cache and factory reset in TWRP.
I then tried to reflash the ROM but it did not reinstall the full thing.
I believe this was down to the fact that I did not perform format data, as I have some mp3's on the internal storage that I wanted to save.
I tried to copy the files from the internal storage to the external micro sd card. This worked at first but then it quit part way through.
I thought this was due to the low battery so I charged and tried to resume. However whenever I tried to copy or move the files over to the external storage the next time it just failed.
I tried to do this a few times as I noticed it would work for a few seconds or a minute before quitting and so thought I could get them all eventually.
The total size of the folder is 2.4GB.
After doing this a few times my phone then decided to boot loop TWRP. It will sit on the startup screen of TWRP but when you try to do something it then resets.
I am running TWRP version v2.3.1.0.
As mentioned before I cannot connect my phone to a computer as the connection port is broken too.
Any help on this matter would be appreciated. I have searched the web for hours but found no such luck.
Kind Regards,
Shaun
You can try reflashing twrp but don't hold your breath.
Without the usb port the device cannot be flashed unless you have mobile odin, for which your device needs to be working.
The only other way is try holding all of the buttons on the device until it boots. Sometimes devices do a reboot when you hold all of the buttons. You must be exact and get all of them at precisely the same time. If no joy then the phone is goosed.
Thanks bro
Thanks for your help, a week or 2 later it decided not to turn on at all....
Think it's toast mate.
Just grabbed and s7 instead

I think I've destroyed accidentally the system

Hi all, i'm stuck at a black screen (completely off screen, even no retroillumination) after a rom change.....
I am under a fully unlocked device, unlocked bootloader, root, usb debug on and with a miui IT (kind of a conversion from miui eu) and working fine for almost 2 years. From 2 months i'm changing rom trying the best for me, the last one was BlissRom. I've just make a backup of miui it rom trought twrp, then wiped system, data, cache and dalvik, like i do everytime even on other devices.
But today at 14:00 i left the blissed tab at 60% battery just after the first android setup, no personal apps installed, and at 19:00 was completely dead, so thinking in a huge battery drain, i've connect the tablet in charging, made a wipe in twrp before restoring the backup made a 14:00 of the original miui. When done, i've rebooted system and i've surprisly got a bootloop, so i've jump in again in twrp, made another full wipe and recovered backup. Again bootloop.... I was able to enter download mode, so when there, i turned off, but it never have turned on again.
Here we have the mistake, i think.... The last full wipe i made, was very full, even the persist partition. I really don't remember if i have check the tickbox of persist, but i'm 80% sure i do...
The only thing it do now, is when i connect to computer, i hear the windows sound of a connected device and it has installed a driver called --Qualcomm HS-USB Diagnostics 900E (COM3)--
The last thing i want to do is test point, if you have any ideas to unbrick this piece of garbage, you're welcome!!!
EDIT: Just downloaded and installed miflash, and i am able to see mi pad connected, and if testpoint is the last hope, guide me to a tutorial pls...
EDIT:
DUNNO what happen, i was attempting to teardown it and it blinked the mi logo.... i quickly run into twrp and i'm flashing the miui it rom, and i'll left it charging for some... i'll keep you updated.
It has self rebooted successfully to miui it.....probably was only a battery fault, but when the screen was off, i wasn't able to charge it, twrp says battery percentage 1% after 1 hour of charging

Categories

Resources