Database Info

[A510] Bricked ?

Hi,
some of them have seen my interest on this tab,
unfortunately, it seems it has gone a bit too far.
today,i made a reset through the parameters, and it stuck (had a custom recovery and root)
trying to hard reset did not help
now, i've got an 0x19000008 error when trying to erase userdata with hard-reset procedure
and i'm struck on iconia tab logo
trying to recover my backup using nikagl recovery without data partition did not help as it remains block
i still have access to fastboot
what is your advice on that ??
which trick might help or is it good for service ?

i have the same problem with you!

then welcome
my tab is at acer service from last monday. status is "under repair'
wiating for news..

jokerzlh said:
i have the same problem with you!
Click to expand...
Click to collapse
can you describe clearly what you did and what you have currently ?

BENETNATH said:
Hi,
some of them have seen my interest on this tab,
unfortunately, it seems it has gone a bit too far.
today,i made a reset through the parameters, and it stuck (had a custom recovery and root)
trying to hard reset did not help
now, i've got an 0x19000008 error when trying to erase userdata with hard-reset procedure
and i'm struck on iconia tab logo
trying to recover my backup using nikagl recovery without data partition did not help as it remains block
i still have access to fastboot
what is your advice on that ??
which trick might help or is it good for service ?
Click to expand...
Click to collapse
i installed the nikagl CWM recovery (version5.8.5), I entered the CWM and tried to wipe data/factory reset, it stuck!
i reset and back to CWM, this time i only flash the zip, but it stuck again!
after that i can't enter the system anymore, i'm stuck on iconia tab logo like you.
so i try to enter fastboot and install the stock recovery, then i use it to flash the update.zip in SD card, but every time the flash will stuck in 1/5 of the whole progress bar, I changed it with other rom zip, or even change the SD card, it didn't work anyway! but It used to be fine with my tab.
anyone can help us? :crying:

can you use fastboot and try this command
fastboot erase userdata
and
fastboot erase cache

BENETNATH said:
then welcome
my tab is at acer service from last monday. status is "under repair'
wiating for news..
Click to expand...
Click to collapse
your tab will be repaired soon, i think.
but i have nowhere to repair, because the A510 doesn't go to market of China mainland this moment!
btw, i really realy hate to fill in the code in the image! so hard for me to read.

jokerzlh said:
your tab will be repaired soon, i think.
but i have nowhere to repair, because the A510 doesn't go to market of China mainland this moment!
btw, i really realy hate to fill in the code in the image! so hard for me to read.
Click to expand...
Click to collapse
sad for you the absence of repair service..
can't you get a repair where you purchased (internet vendor) ?
no image for me

BENETNATH said:
can you use fastboot and try this command
fastboot erase userdata
and
fastboot erase cache
Click to expand...
Click to collapse
I had a try, but it seems doesn't work.
erasing 'userdata' ... failed <remote:<19000008>>
erasing 'cache' ... failed <command write failed <NO Such file or directory>>

ok, seems your data partition is corrupted.
the only escape way would be to have nvflash tools, which we currently do not have..
so two option:
1) wait until the dev manage to get a solution, with a unusable brick
2) send to repair center and possibly pay to have a working device..

BENETNATH said:
ok, seems your data partition is corrupted.
the only escape way would be to have nvflash tools, which we currently do not have..
so two option:
1) wait until the dev manage to get a solution, with a unusable brick
2) send to repair center and possibly pay to have a working device..
Click to expand...
Click to collapse
when i use the command you gave, there're some text on tab screen:
white text: StorMgr Formatting UDA
red text: Failed to process command erase:userdata error ( 0X19000008 )
I think you are right! I can only wait.
thanks for your help

it seems that on some device, keeping trying worth the cost
so i would suggest that if you plan to wait, you should try from time to time some hard reset procedure (vol down + lock switch triggering on boot)
eg . http://forums.lenovo.com/t5/IdeaPad...er-Error-0x19000008-after-Factory/td-p/759121

good news, i just have an email from acer customer service.
they gave me a tracking number to get my device back

Nice
That was a quick repair. Does Acer charge you for anything (repairs or at least shipping)?

it seems that the whole thing was free, will confirm when i have the package
but at least i did not receive any quote before repairing..
and for the first shipment i'd received a free shipping card.
now, i hope that the tab will be completely fixed (partition bricked, and my headphone jack was non working)

BENETNATH said:
it seems that on some device, keeping trying worth the cost
so i would suggest that if you plan to wait, you should try from time to time some hard reset procedure (vol down + lock switch triggering on boot)
eg . http://forums.lenovo.com/t5/IdeaPad...er-Error-0x19000008-after-Factory/td-p/759121
Click to expand...
Click to collapse
thanks, but i'm not lucky!
i tried many many times, it still show:
Erasing userdata...
Unrecoverable Bootloader Error (0x19000008)
it's time to give it up:crying:

let it rest a bit, and watch olympic games
then try again one day or the other..
sorry, no other solution. or find a way to have it repaired (send it to me )

BENETNATH said:
good news, i just have an email from acer customer service.
they gave me a tracking number to get my device back
Click to expand...
Click to collapse
congratulation!
---------- Post added at 11:29 PM ---------- Previous post was at 11:15 PM ----------
BENETNATH said:
it seems that the whole thing was free, will confirm when i have the package
but at least i did not receive any quote before repairing..
and for the first shipment i'd received a free shipping card.
now, i hope that the tab will be completely fixed (partition bricked, and my headphone jack was non working)
Click to expand...
Click to collapse
waiting for your test report.
When you go to get your device back, is that possible to ask Acer for some Official Flash Tool or some thing like that?

that was my initial plan if they asked for some money (ok to pay, but with nvflash tool )

I already tried to ask Acer for a flash tool but they told me they cannot provide any. Updates will ony come OTA.
We have top hope that a tool will be leaked like for the Tegra2 devices.

Boot stops at 'Google', can't mout sdcard in cwm

Hi,
since this morning I have this problem that my Nexus S just boots until the Google logo appears.
I have no idea what caused this. I was just reinstalling the youtube app and rebooted after that and it booted.
Then I noticed that my phone would not change the screen orientation and because it worked in the past I started another reboot. But then it got stuck at the Google logo.
To solve this problem I just wanted to flash my nandroid backup but that didn't work as well cause the recovery was not able to mount the sdcard.
E:Can't mount /sdcard
Does anyone have an idea how to solve this problem? By the way is it possible to pull the Nandroid backup from the phone to my computer with ADB for example. Would be great because (of course) I just have an backup on my phone... (but if not... well, **** happens)
Thanks in advance!

PedroBustamonte said:
Hi,
since this morning I have this problem that my Nexus S just boots until the Google logo appears.
I have no idea what caused this. I was just reinstalling the youtube app and rebooted after that and it booted.
Then I noticed that my phone would not change the screen orientation and because it worked in the past I started another reboot. But then it got stuck at the Google logo.
To solve this problem I just wanted to flash my nandroid backup but that didn't work as well cause the recovery was not able to mount the sdcard.
E:Can't mount /sdcard
Does anyone have an idea how to solve this problem? By the way is it possible to pull the Nandroid backup from the phone to my computer with ADB for example. Would be great because (of course) I just have an backup on my phone... (but if not... well, **** happens)
Thanks in advance!
Click to expand...
Click to collapse
flasgh stock via fastboot and wipe everything DONE!

i had this problem when i flashed a non-cm kernel on a cm-based rom. try flashing a different kernel. know what kernel your rom is compatible to,

Cascabreu said:
flasgh stock via fastboot and wipe everything DONE!
Click to expand...
Click to collapse
So there's no way to get the content of the sdcard before I wipe everything?
ej8989 said:
i had this problem when i flashed a non-cm kernel on a cm-based rom. try flashing a different kernel. know what kernel your rom is compatible to,
Click to expand...
Click to collapse
I'm using ParanoidAndroid with Mamite (the version for cm based roms since PA is also based on cm)

PedroBustamonte said:
So there's no way to get the content of the sdcard before I wipe everything?
I'm using ParanoidAndroid with Mamite (the version for cm based roms since PA is also based on cm)
Click to expand...
Click to collapse
Go to mounts and storage in CWM Recovery and "mount usb storage". That will let you get to your SD card to backup. Then I suggest just a clean wipe and start over.
Note: mount /sdcard just mounts it to the phone. You are wanting to mount it to your computer to pull the files off the external.

mdean1981 said:
Go to mounts and storage in CWM Recovery and "mount usb storage". That will let you get to your SD card to backup. Then I suggest just a clean wipe and start over.
Note: mount /sdcard just mounts it to the phone. You are wanting to mount it to your computer to pull the files off the external.
Click to expand...
Click to collapse
Yup thank you. Already tried that and a lot of other stuff. Seems like my phone's broken. I can't write on or erase /system or /sdcard. I'll try today to lock the bootloader and then unlock it. Maybe that solves the problem...

It will also wipe everything if I remember well
Envoyé depuis mon Nexus S avec Tapatalk

PedroBustamonte said:
Yup thank you. Already tried that and a lot of other stuff. Seems like my phone's broken. I can't write on or erase /system or /sdcard. I'll try today to lock the bootloader and then unlock it. Maybe that solves the problem...
Click to expand...
Click to collapse
dont lock it cuz u wont be able to unlock it after. unlocking requires being able to erase the sdcard
tested it my self yesterday on a phone with the same issue

Cascabreu said:
dont lock it cuz u wont be able to unlock it after. unlocking requires being able to erase the sdcard
tested it my self yesterday on a phone with the same issue
Click to expand...
Click to collapse
Yes you're right. But I really can't think of any thing I could try.

PedroBustamonte said:
Yes you're right. But I really can't think of any thing I could try.
Click to expand...
Click to collapse
It's interesting and maybe fortuite that this is happening to you just as something almost equal happens to me (see here: http://forum.xda-developers.com/showthread.php?t=1972447 ) You should also enter the recovery via adb from your computer if you have it, and check if a) you have mmc* files in /dev/block and b) have mmc error messages in dmesg (in the phone: "dmesg|grep mmc" and look for lines with "error" in them).
Btw to the person who suggested flashing stock thorough fastboot, do you mean stock system, system+boot or system+boot+recovery ? and where could I find those stock .img please? Mine's an i9020a

Blissfull said:
It's interesting and maybe fortuite that this is happening to you just as something almost equal happens to me (see here: http://forum.xda-developers.com/showthread.php?t=1972447 ) You should also enter the recovery via adb from your computer if you have it, and check if a) you have mmc* files in /dev/block and b) have mmc error messages in dmesg (in the phone: "dmesg|grep mmc" and look for lines with "error" in them).
Btw to the person who suggested flashing stock thorough fastboot, do you mean stock system, system+boot or system+boot+recovery ? and where could I find those stock .img please? Mine's an i9020a
Click to expand...
Click to collapse
Factory Images for Nexus Devices
https://developers.google.com/android/nexus/images

Hi ^^
I had the same problem with my Nexus S a long time ago and never found out how to solve it. It seems that the internal memory is corrupted and nothing but replacing the motherboard can solve it. Since I bought mine in the USA but I live in Belgium I never got mine repaired. Sometimes I come back here to see if there is still no solution but each time I'm disappointed...
Sorry.

PedroBustamonte said:
Yes you're right. But I really can't think of any thing I could try.
Click to expand...
Click to collapse
Cascabreu said:
dont lock it cuz u wont be able to unlock it after. unlocking requires being able to erase the sdcard
tested it my self yesterday on a phone with the same issue
Click to expand...
Click to collapse
I can confirm this. I had the same thing happen to my Nexus S 4G recently. I was never able to salvage any data off the sdcard no matter what I tried (various mounting attempts in recovery, any adb command I thought might be helpful, etc.). As a last resort I tried to lock/unlock the bootloader - once I locked it, I was unable to unlock it again, it just froze up after asking me if I was sure I wanted to unlock. I guess that's what happens when the internal sdcard goes to hell. I ended up taking it to my local Sprint store and they replaced the phone with a refurbished one from Samsung (for approximately $35).

[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

[Q] Accidentally bricked Nexus...I think...

Hi all, first post to the forums so forgive me if I'm forgetting some sort of forum etiquette.
My brother's Nexus 5 stopped working a while ago, it'd just go straight to the Google screen on start up and sit there indefinitely. Recovery mode? Non-existent. I could get into the bootloader easy as, but selecting recovery mode just resulted in a black screen that would not accept any commands. So since I've reflashed my own Nexus 5 with various flavours of Android before I decided to just reflash his too, as I figured there's no reason that shouldn't work.
500 attempts later and uh, yeah, I don't think it's working.
I've tried installing the official versions of 4.3, 4.4, and 5.0, but Fastboot results in "failure to write" errors. I even tried sideloading with TWRP and Clockwork, but both of those give me error messages saying failure to mount /cache or /recovery or whatever.
I've spent an entire day (that should have been spent working on certain assignments :s) trying to fix this and looking around forums for a solution yet can't seem to find anything.
If anyone has any idea on how to fix this it would be greatly appreciated, I'm not too sure Google would honor the warranty on this anymore...

D0UBLEJUMP said:
Hi all, first post to the forums so forgive me if I'm forgetting some sort of forum etiquette.
My brother's Nexus 5 stopped working a while ago, it'd just go straight to the Google screen on start up and sit there indefinitely. Recovery mode? Non-existent. I could get into the bootloader easy as, but selecting recovery mode just resulted in a black screen that would not accept any commands. So since I've reflashed my own Nexus 5 with various flavours of Android before I decided to just reflash his too, as I figured there's no reason that shouldn't work.
500 attempts later and uh, yeah, I don't think it's working.
I've tried installing the official versions of 4.3, 4.4, and 5.0, but Fastboot results in "failure to write" errors. I even tried sideloading with TWRP and Clockwork, but both of those give me error messages saying failure to mount /cache or /recovery or whatever.
I've spent an entire day (that should have been spent working on certain assignments :s) trying to fix this and looking around forums for a solution yet can't seem to find anything.
If anyone has any idea on how to fix this it would be greatly appreciated, I'm not too sure Google would honor the warranty on this anymore...
Click to expand...
Click to collapse
Is your bootloader unlocked?
Are you getting the images from here, and following all the instructions: https://developers.google.com/android/nexus/images

krs360 said:
Is your bootloader unlocked?
Are you getting the images from here, and following all the instructions
Click to expand...
Click to collapse
Yes, yes and yes.
Like I said, everything went fine with reflashing my own Nexus 5, but my brother's one is just being so, so, so uncooperative.

D0UBLEJUMP said:
Yes, yes and yes.
Like I said, everything went fine with reflashing my own Nexus 5, but my brother's one is just being so, so, so uncooperative.
Click to expand...
Click to collapse
Try locking the bootloader in fastoot. Reboot to bootloader. If the bootloader still says unlocked you have a bad emmc chip.

theesotericone said:
Try locking the bootloader in fastoot. Reboot to bootloader. If the bootloader still says unlocked you have a bad emmc chip.
Click to expand...
Click to collapse
Bootloader always relocks when the phone restarts :/

It's a hardware error, a bad emmc chip. Your only choice is to exchange it under the warranty.

BirchBarlow said:
It's a hardware error, a bad emmc chip. Your only choice is to exchange it under the warranty.
Click to expand...
Click to collapse
Do you know if Google will still exchange it? It's within the warranty period, but I have been reflashing it and unlocking the bootloader which I doubt they're too excited about. Or is this a sort of special case since it's a hardware error?

D0UBLEJUMP said:
Do you know if Google will still exchange it? It's within the warranty period, but I have been reflashing it and unlocking the bootloader which I doubt they're too excited about. Or is this a sort of special case since it's a hardware error?
Click to expand...
Click to collapse
if your emmc is corrupt i don't think they will be able to find out you have been messing with your device and if your bootloader is locked that should do fine. Only thing that i'm not able to confirm is about the tamper flag

nexus.freak said:
if your emmc is corrupt i don't think they will be able to find out you have been messing with your device and if your bootloader is locked that should do fine. Only thing that i'm not able to confirm is about the tamper flag
Click to expand...
Click to collapse
I believe you can reset the tamper flag with a bit of luck by booting twrp from fastboot ( fastboot boot twrp.img ) then sideload and flash the tamper resetter.
That being said , anyone know what's the incidence of bad emmc chips on our devices ? And/or if there's a trigger to them ?

Niflheimer said:
I believe you can reset the tamper flag with a bit of luck by booting twrp from fastboot ( fastboot boot twrp.img ) then sideload and flash the tamper resetter.
That being said , anyone know what's the incidence of bad emmc chips on our devices ? And/or if there's a trigger to them ?
Click to expand...
Click to collapse
Woohoo! Flag reset!
Judging by what I found when I was looking around it doesn't seem like bad emmc is too common, couldn't find many suffering the same issues as me.
As for triggers, my brother's Nexus worked completely fine just like mine, then powered off, powered on, and broken. So...I guess the message of the story is to never turn them off (or try reflash) and they'll be fine?

If you bought phone of play store you can send it to google, there was a tread here some time ago and it said that google accept to replace phones with temper flag and unlocked bootloader.
Good luck

Nexus 5 bricked - HEEELP!!!

Hi, tonight my Nexus 5 updated after that, he called on google setup screen (as if it were the first boot), and began to see a message saying that the store was full, when I see the 16 GB only 128 Mb was available. I tried to flash the Nexus Toolkit original system, but gives error ... when I try to enter the recovery, gives error mounting partitions. Please help me!!! Note: he's no longer under warranty.
Model: Nexus 5 D821 (E) 16 GB, red
sorry for my English, I am Brazilian, and I wrote this using google translator. :crying:

What error are you getting from the tool kit? Have you tried wiping data? Have you tried manually flashing without a toolkit?

audit13 said:
What error are you getting from the tool kit? Have you tried wiping data? Have you tried manually flashing without a toolkit?
Click to expand...
Click to collapse
invalid argument error in recovery, failed (remote write fail) in fastboot, and nexus toolkit

The bootloader is unlocked?

audit13 said:
The bootloader is unlocked?
Click to expand...
Click to collapse
Yes! And relock does not work. when you restart, it is as if nothing had happened.

I think the emmc is dead because the amount of available memory is minuscule and the bootloader cannot be relocked.

audit13 said:
I think the emmc is dead because the amount of available memory is minuscule and the bootloader cannot be relocked.
Click to expand...
Click to collapse
and there's no way to pack without changing the plate? in Brazil it is very expensive, and care is even more expensive. Perhaps LGNPST?

You could try since you have nothing to lose.

audit13 said:
You could try since you have nothing to lose.
Click to expand...
Click to collapse
in your opinion, this maybe work? http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447

Not sure if that will solve the problem. If you have no warranty and you've tried everything else, you could try that method.