Database Info

[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] Perma Brick?

My friend was running completely same setup of latest RastaKat + trinity kernel on N5. This morning device rebooted randomly with factory settings and reported Gallery and Camera stopped working after booting to Android, SIM card was not recognized and internal storage was unavailable. I tried to flash full stock firmware package, unfortunatly cache and userdata coudn't be erased/formated, flashing failed (tried force flash setting on recovery and flash manually as well).
Phone boots to same old RastaKat ROM after everything I've done to him.
I'm completely lost, is it a hardware fault or simple software incident? Any help appreciated and sorry for my English

neoneras said:
My friend was running completely same setup of latest RastaKat + trinity kernel on N5. This morning device rebooted randomly with factory settings and reported Gallery and Camera stopped working after booting to Android, SIM card was not recognized and internal storage was unavailable. I tried to flash full stock firmware package, unfortunatly cache and userdata coudn't be erased/formated, flashing failed (tried force flash setting on recovery and flash manually as well).
Phone boots to same old after everything I've done to him.
I'm completely lost, is it a hardware fault or simple software incident? Any help appreciated and sorry for my English
Click to expand...
Click to collapse
Does the phone show up on the computer/device manager? if so, does it have the name it used to have?
---------- Post added at 02:42 PM ---------- Previous post was at 02:37 PM ----------
Also, did you follow these methods 1&2? if you only did # 1, try # 2
http://forum.xda-developers.com/showthread.php?t=2513701

Yep, it responds to fastboot commands with either success or failed responses. It shows in my computer under media devices but I can't access internal storage.

neoneras said:
Yep, it responds to fastboot commands with either success or failed responses. It shows in my computer under media devices but I can't access internal storage.
Click to expand...
Click to collapse
go to the link I posted above

on flashing bootloader I get:
sending 'bootloader' (2508 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.487s
Click to expand...
Click to collapse

neoneras said:
on flashing bootloader I get:
Click to expand...
Click to collapse
Flash memory failure (emmc bug), i`am afraid there is nothing you can do anymore. The motherboard has to be replaced.

neoneras said:
on flashing bootloader I get:
Click to expand...
Click to collapse
put phone o fastboot mode and lock it typing
"fastboot oem lock"
if it doesn't work, It is pointing to bad emmc

GUGUITOMTG4 said:
put phone o fastboot mode and lock it typing
"fastboot oem lock"
if it doesn't work, It is pointing to bad emmc
Click to expand...
Click to collapse
thanks for replies. Well, now only thing that's left is to convince warranty that is emmc problem and should be covered as warranty

Can you tell me pls if your friend used any toolkit on rooting his Nexus?
Because it's important to me to know,if so,I will be aware of toolkits like hot iron. xD

Simonna said:
Can you tell me pls if your friend used any toolkit on rooting his Nexus?
Because it's important to me to know,if so,I will be aware of toolkits like hot iron. xD
Click to expand...
Click to collapse
no, original unlock and root was done using my own hands and terminal shell

neoneras said:
no, original unlock and root was done using my own hands and terminal shell
Click to expand...
Click to collapse
Just bad luck bro, could and does happen to anyone

OP Im Afraid you will be phoneless for 1 Month as Google warehouse has run dry of N5 32 and 16GB

Well it's not me, my N5 is running like a charm. My poor friend on the other hand had PC HDD failure last week and this week his Nexus died. Well that's karma, because recently he was cheating on his girlfriend

neoneras said:
Well it's not me, my N5 is running like a charm. My poor friend on the other hand had PC HDD failure last week and this week his Nexus died. Well that's karma, because recently he was cheating on his girlfriend
Click to expand...
Click to collapse
What a garbage individual.
He deserved what's coming to him.

neoneras said:
Well it's not me, my N5 is running like a charm. My poor friend on the other hand had PC HDD failure last week and this week his Nexus died. Well that's karma, because recently he was cheating on his girlfriend
Click to expand...
Click to collapse
Google Knows

markdapimp said:
Google Knows
Click to expand...
Click to collapse
Indeed, Google Knows, Google punishes.
Ok, warranty is a pain in the ass in my country. Any ideas how can I completely kill nexus so it doesn't turn on anymore?

neoneras said:
Indeed, Google Knows, Google punishes.
Ok, warranty is a pain in the ass in my country. Any ideas how can I completely kill nexus so it doesn't turn on anymore?
Click to expand...
Click to collapse
Why would you want to do that?

markdapimp said:
Why would you want to do that?
Click to expand...
Click to collapse
Sounds like warranty fraud which xda does not condone
Sent from my Nexus 5

[Q] Stuck in bootloop.

Hi everyone.
I have the following problem with a Nexus 5: During an update, the system crashed. The phone is now stuck in an endless bootloop, trying to install the update. When left long enough, the update screens eventually come up, but you are immediately blasted with a ton of errors and no matter what you do, you are unable to complete the update. This, however, is not the problem.
I have tried various utilities in order to flash the phone back to factory settings. I have made use of Unified Android ToolKit, as well as Nexus Root Toolkit, but a problem with the phone itself is preventing me from flashing it and the problem is as follows: I can access the phone via USB, as well as the bootloader, but when I unlock the bootloader to start the flashing, it immediately locks itself again and I'm unable to start the flash process.
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?

Mystical_Titan said:
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Click to expand...
Click to collapse
If the lock state reverts on a reboot, 99 times out of 100, it means the internal memory has an issue. RMA.

rootSU said:
If the lock state reverts on a reboot, 99 times out of 100, it means the internal memory has an issue. RMA.
Click to expand...
Click to collapse
Thanks for the fast response. :good:

Mystical_Titan said:
Thanks for the fast response. :good:
Click to expand...
Click to collapse
No probs. Sounds like the update got stuck at the bootloader flash and corrupted. It's probably not a fatal NAND issue, rather corrupt partition or two but it usually means sending it in.
You can try the LG flashtool as a last resort before doing so though, as you never know...
You can find a link to it in the sticky thread in my signature. Best to stay away from actual "toolkits" though and either use fastboot manually or LG flash tool, although fastboot probably cant help you here - just saying for future ref...

Mystical_Titan said:
Hi everyone.
I have the following problem with a Nexus 5: During an update, the system crashed. The phone is now stuck in an endless bootloop, trying to install the update. When left long enough, the update screens eventually come up, but you are immediately blasted with a ton of errors and no matter what you do, you are unable to complete the update. This, however, is not the problem.
I have tried various utilities in order to flash the phone back to factory settings. I have made use of Unified Android ToolKit, as well as Nexus Root Toolkit, but a problem with the phone itself is preventing me from flashing it and the problem is as follows: I can access the phone via USB, as well as the bootloader, but when I unlock the bootloader to start the flashing, it immediately locks itself again and I'm unable to start the flash process.
I've searched for other instances in which the bootloader won't unlock, but I can't find any information. Is there perhaps a hardware problem preventing me from unlocking the bootloader or can someone help me find a solution to this problem?
Click to expand...
Click to collapse
happened to me while installing the new SNAPSHOT version of Cyanogenmod, I wiped everything and reflashed it and it works

BruKnowsBest said:
happened to me while installing the new SNAPSHOT version of Cyanogenmod, I wiped everything and reflashed it and it works
Click to expand...
Click to collapse
Can anyone suggest some steps for me to try before I RMA the phone? Although, being unable to unlock the bootloader probably limits my options.

Mystical_Titan said:
Can anyone suggest some steps for me to try before I RMA the phone? Although, being unable to unlock the bootloader probably limits my options.
Click to expand...
Click to collapse
I was stuck in the boot animation and when it opened there was a lot of system errors and it would reboot by itself over and over again.
what fixed it was to do a wipe cache and dalvik and reinstall it

BruKnowsBest said:
I was stuck in the boot animation and when it opened there was a lot of system errors and it would reboot by itself over and over again.
what fixed it was to do a wipe cache and dalvik and reinstall it
Click to expand...
Click to collapse
I tried the 'wipe cache' as well, but it returns a bunch of errors as well. I'm starting to think the NAND is screwed. What is dalvik?

Mystical_Titan said:
I tried the 'wipe cache' as well, but it returns a bunch of errors as well. I'm starting to think the NAND is screwed. What is dalvik?
Click to expand...
Click to collapse
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk

rootSU said:
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I completely forgot that you mentioned the LG Flashtool, I feel like such an idiot. I'll try that tomorrow as a last resort.

No worries
Sent from my Nexus 5 using Tapatalk

rootSU said:
Dalvik cannot break your bootloader. Your only option was use lg flashtool and if that failed, RMA. Let's not get false hopes and waste time not doing this.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i thought about LG FLASHTOOL but decided to try reinstaling the rom cuz i had no other option since i forgot to leave a backup rom on the device. So I did it as if I was installing a brand new rom Wiped dalvik, cache and system then reflashed the rom and then the gapps. Even tho it was the same ROM file I had a different outcome. It's working fine now but I did go back to the nightlies after it started working again just to be safe.
Now... people may have a different outcome when trying to solve this issue but this actually worked for me after having a minor heart-attack thinking I was gonna lose all my stuff

BruKnowsBest said:
i thought about LG FLASHTOOL but decided to try reinstaling the rom cuz i had no other option since i forgot to leave a backup rom on the device. So I did it as if I was installing a brand new rom Wiped dalvik, cache and system then reflashed the rom and then the gapps. Even tho it was the same ROM file I had a different outcome. It's working fine now but I did go back to the nightlies after it started working again just to be safe.
Now... people may have a different outcome when trying to solve this issue but this actually worked for me after having a minor heart-attack thinking I was gonna lose all my stuff
Click to expand...
Click to collapse
Yes, but your issue is different to the OP's. His bootloader lock state reverts whenever he changes it. This is a pretty much "fatal" issue. What you did cannot help him unfortunately.

rootSU said:
Yes, but your issue is different to the OP's. His bootloader lock state reverts whenever he changes it. This is a pretty much "fatal" issue. What you did cannot help him unfortunately.
Click to expand...
Click to collapse
oh ok, I misunderstood

rootSU said:
No worries
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It speaks about a KDZ file. What is it and where would I find it?

Mystical_Titan said:
It speaks about a KDZ file. What is it and where would I find it?
Click to expand...
Click to collapse
Not sure, never used it. Are you following the Nexus 5 LG Flash tool guide? If not, have a look. You can get to it via my signature

rootSU said:
Not sure, never used it. Are you following the Nexus 5 LG Flash tool guide? If not, have a look. You can get to it via my signature
Click to expand...
Click to collapse
Well, that's that. This phone is done.

Yup. RMA
Sent from my Nexus 5 using Tapatalk

IMEI Unknown

Hi guys! I've looked all around and tried the fixes that people recommended, which is basically going back to stock.
So this is what happened to my brother's phone:
Was using the phone and all a sudden the phone freezes (He was on Android L) and he rebooted it. After rebooting, the phone went into bootloop. He downloaded some program that supposedly fixes softbrick and bootloop (by flashing stock ROM) Nexus Root Toolkit v1.8.7.
The phone was fixed.. Kinda.. He couldn't get any cell signal. Turns out his baseband and IMEI read unknown. He has the box the phone came in, to we know the physical IMEI number.
Is there a fix for this? I've tried this thread http://forum.xda-developers.com/google-nexus-5/help/lost-imei-please-help-t2529103 but it didn't work.
Any ideas?

You_got_owned123 said:
Hi guys! I've looked all around and tried the fixes that people recommended, which is basically going back to stock.
So this is what happened to my brother's phone:
Was using the phone and all a sudden the phone freezes (He was on Android L) and he rebooted it. After rebooting, the phone went into bootloop. He downloaded some program that supposedly fixes softbrick and bootloop (by flashing stock ROM) Nexus Root Toolkit v1.8.7.
The phone was fixed.. Kinda.. He couldn't get any cell signal. Turns out his baseband and IMEI read unknown. He has the box the phone came in, to we know the physical IMEI number.
Is there a fix for this? I've tried this thread http://forum.xda-developers.com/google-nexus-5/help/lost-imei-please-help-t2529103 but it didn't work.
Any ideas?
Click to expand...
Click to collapse
Try to run the "fastboot earease cache" command in fastboot. Read the sticky thread in the general forum.

bitdomo said:
Try to run the "fastboot earease cache" command in fastboot. Read the sticky thread in the general forum.
Click to expand...
Click to collapse
Sad to say, I've already tried that.. Even tried to flash stock cache image.

You_got_owned123 said:
Sad to say, I've already tried that.. Even tried to flash stock cache image.
Click to expand...
Click to collapse
Also you said the baseband is unknown. Have you tried to reflash the radio/modem image?

bitdomo said:
Also you said the baseband is unknown. Have you tried to reflash the radio/modem image?
Click to expand...
Click to collapse
I've flashed radio, but modem I have not. I'll have to try that!

You_got_owned123 said:
I've flashed radio, but modem I have not. I'll have to try that!
Click to expand...
Click to collapse
It's the same thing!
restore fully to stock using LG Flashtool. See if that fixes...

rootSU said:
It's the same thing!
restore fully to stock using LG Flashtool. See if that fixes...
Click to expand...
Click to collapse
Can you by any chance give me a link? Did a quick Google search and didn't find anything official.

You_got_owned123 said:
Can you by any chance give me a link? Did a quick Google search and didn't find anything official.
Click to expand...
Click to collapse
See my signature
Sent from my Nexus 5 using Tapatalk

You_got_owned123 said:
Can you by any chance give me a link? Did a quick Google search and didn't find anything official.
Click to expand...
Click to collapse
Or check my signature.
Someone calls it modem and someone calls it radio.

rootSU said:
See my signature
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hey! I was reading on a thread where you helped someone fix their phone!
Did a stock flash do it for them? I got the factory images and ran the flash-all scrip and still nothing.

You_got_owned123 said:
Hey! I was reading on a thread where you helped someone fix their phone!
Did a stock flash do it for them? I got the factory images and ran the flash-all scrip and still nothing.
Click to expand...
Click to collapse
I help a lot of people. I cannot pick out individual instances.
Use LG flashtool
Sent from my Nexus 5 using Tapatalk

You_got_owned123 said:
Hey! I was reading on a thread where you helped someone fix their phone!
Did a stock flash do it for them? I got the factory images and ran the flash-all scrip and still nothing.
Click to expand...
Click to collapse
Also check if wifi mac address is changing after each reboot. Corrupted persist partition can cause problems like that and also other things like crasing apps
Check out my thread about it http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576. It worths a try. If it does not help then you have to buy a new motherboard or claim your warranty if you have any.

bitdomo said:
Also check if wifi mac address is changing after each reboot. Corrupted persist partition can cause problems like that and also other things like crasing apps
Check out my thread about it http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576. It worths a try. If it does not help then you have to buy a new motherboard or claim your warranty if you have any.
Click to expand...
Click to collapse
Perist will not mount. I hasn't seen factory image for persist partition.

You_got_owned123 said:
Perist will not mount. I hasn't seen factory image for persist partition.
Click to expand...
Click to collapse
Because there arent any. It is unique for every device like efs.

bitdomo said:
Because there arent any. It is unique for every device like efs.
Click to expand...
Click to collapse
So is that a problem?

You_got_owned123 said:
So is that a problem?
Click to expand...
Click to collapse
If you see that /persist cannot be mounted then it could be.

bitdomo said:
If you see that /persist cannot be mounted then it could be.
Click to expand...
Click to collapse
I tried wiping cache and then it gave me a bunch or partitions that were errors. With persist being one of them. After a while, I was able to clear cache with no errors.

You_got_owned123 said:
I tried wiping cache and then it gave me a bunch or partitions that were errors. With persist being one of them. After a while, I was able to clear cache with no errors.
Click to expand...
Click to collapse
Then it is up to you what are you going to do with the persist partition. You will lose nothing but time by formating the persist partition. If it not fix your problem then you have to buy a new motherboard for the phone to make phone calls either way because you dont have any efs backup.

bitdomo said:
Then it is up to you what are you going to do with the persist partition. You will lose nothing but time by formating the persist partition. If it not fix your problem then you have to buy a new motherboard for the phone to make phone calls either way because you dont have any efs backup.
Click to expand...
Click to collapse
Persist was the problem. Fixed that partition and was golden. Thank you so much all of you. Took 3 hours. So much Google.

You_got_owned123 said:
Persist was the problem. Fixed that partition and was golden. Thank you so much all of you. Took 3 hours. So much Google.
Click to expand...
Click to collapse
It would be nice if you would post how did you solve your issue. Some will learn and it could help others having the same issue.

[BOOTLOOP]Nexus 5 problem with persist partition

Hi, i have a big problem for 4 months with my nexus 5:
A day, it starts bootloop and I take it at the LG center, one month afther they tell me that they can't repair the phone because i have rooted it. They said that i must pay a lot of money because i have to replace the motherboard.
I didn't pay anything and i got the device with a new problem: It is in bootloop, but i can access to the recovery but these are the problems:
1) the twrp recovovery says "Unable to mount /persist" and "unable to open "/cache/recovery/.version
2) I can't wipe and flash anything aside "boot.img" and "recovery.img"
3)I tried to use this command in the prompt:
e2fsck /dev/block/platform/msm_sdcc.1/byname/persist but it says "recovering journal superblock needs_recovery is clear but journal has data, run journal anyway?" i enter "y" and it says "unable to set superblock flags".
I have made many sacrifices to buy the phone and i can't get a new one, how can I solve this problem? (now it still in bootloop)
Sorry for my bad english

There's a whole guide to repair /persist in the general forum. Look in "sticky roll-up" thread.

rootSU said:
There's a whole guide to repair /persist in the general forum. Look in "sticky roll-up" thread.
Click to expand...
Click to collapse
Thank you for your answer
i followed the guide, but when i enter "make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist" to format the partition, the problem still persist...
:crying:

Hello
I had a similar problem a I did managed to make it work using this helpful post
http://forum.xda-developers.com/goo...l-06-03-14-one-click-factory-restore-t2513937
After that you can root again, and start to play.

Muaitai said:
Hello
I had a similar problem a I did managed to make it work using this helpful post
http://forum.xda-developers.com/goo...l-06-03-14-one-click-factory-restore-t2513937
After that you can root again, and start to play.
Click to expand...
Click to collapse
i haven't try it yet, but i have the writing error when i flash the stock image with wug fresh toolkit, are you sure that this can solve the problem?
EDT---
I have tried it but there is the same problem (write failure). Any solutions?

Can everyone help me?

#$wag said:
Can everyone help me?
Click to expand...
Click to collapse
try http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
this touches on partitions that normal factory images dont.

opssemnik said:
try http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
this touches on partitions that normal factory images dont.
Click to expand...
Click to collapse
Thanks for answer, but when I use this tool, there is an error with sending userdata and there is no change...

#$wag said:
Thanks for answer, but when I use this tool, there is an error with sending userdata and there is no change...
Click to expand...
Click to collapse
i bet your emmc is bad

opssemnik said:
i bet your emmc is bad
Click to expand...
Click to collapse
:crying:
Can I replace the emmc?

#$wag said:
:crying:
Can I replace the emmc?
Click to expand...
Click to collapse
by your own no. if you have warranty, lg covers that (or google depending on where you live/bought the device).
basicly you need to replace the whole motherboard

opssemnik said:
by your own no. if you have warranty, lg covers that (or google depending on where you live/bought the device).
basicly you need to replace the whole motherboard
Click to expand...
Click to collapse
I have already sent my phone to lg but they said that it is rooted and they can't help me.
how much does a new motherboard costs?

#$wag said:
I have already sent my phone to lg but they said that it is rooted and they can't help me.
how much does a new motherboard costs?
Click to expand...
Click to collapse
tbh no idea, but probably $150-$200

opssemnik said:
tbh no idea, but probably $150-$200
Click to expand...
Click to collapse
Sorry but I don't think that the emmc is bad, i've tried to make a directory with adb and it create the directory, so I think that i must to reset the partition (whith TWRP)... But i don't know the commands...

#$wag said:
Sorry but I don't think that the emmc is bad, i've tried to make a directory with adb and it create the directory, so I think that i must to reset the partition (whith TWRP)... But i don't know the commands...
Click to expand...
Click to collapse
just like hdds and ssds, flash memories can also get corrupted/ bad sectors, these are hardware defects only at certain part of the memory.
the command you are looking for is already done by lg flash tool, but it failed to do because your emmc is bad.
anyway if you want to
mkfs.ext4 /dev/block/platform/msm_sdcc.1/by-name/persist /persist
if gives command not found then try
mkfs_ext4 instead
if you willing to try something, pm me