Database Info

[Q][EMERGENCY] Storage Freezing or corrupt, Unlock FAILED (Erase Fail)

i have a big problem
i buy a stock phone (I9020T)
but i cant unlock the phone with any method and cant root or flash and ...
phone random correctly boot and random (90%) hang on google logo
i cant do anything with phone when randomly boot on ! (many error)
i even cant erase and restore factory device (failed) in recovery mode (after press all keys i see standard menu)
i must 10 - 20 time pull battery and power again to ics boot up
but every thing back to a point (last user setting and photo-gallery and ...)
and dont save anything in next boot !!!
how can check internal memory for any damage ?
i thing have exact problem http://forum.xda-developers.com/showthread.php?t=993403
but phone is LOCKED and cant test that methods and cant return to samsung :'(
please helpppppppp me
Carrier TMB
LOCKED
Rom: ICS (no root, no mod, no customize)
bootloader ver: I9020XXKL1
Baseband ver: I9020XXKI1
i try every guid and tutorial to unlock and root, not work anyone !
FAILED (remote: Erase Fail) and many error like this Erase Fail or write failed
memory is readonly ? or phone was crashed ?
any solutions ????
tanx

i see same error in nexusshacks.com ics root guid :'(

please helpppppp ....
anybody any idea .......

Have you encrypted your phone?
Sent from my Nexus S using XDA

maybe your sdcard / internel memory is faulty?

jorim.tielemans said:
Have you encrypted your phone?
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
no i dont ! how can check it ?

mtothearkus said:
maybe your sdcard / internel memory is faulty?
Click to expand...
Click to collapse
some time when ics boot up and i can use usb storage mount i can work with memory and its ok.
but how can check internal ? its maybe readonly !

I am having the same exact issue. I have tried many different things. My ICS boots but everything force closes. When I installed fastboot, adb, sdk, etc., everything installs but when I run fastboot oem unlock i get the remote: erase fail error, even though the phones display gives me the unlock option screen. I also tried to do a wipe in stock recovery and that does not take. Once booted into ics, though nothing works, I can mount the phone to my computer but when I try to copy over a stock image to reflash the computer gets an error and won't copy. I would also appreciate anyones help with any new ideas. I don't think its a hardware issue, but maybe?

ninfragile14 said:
I am having the same exact issue. I have tried many different things. My ICS boots but everything force closes. When I installed fastboot, adb, sdk, etc., everything installs but when I run fastboot oem unlock i get the remote: erase fail error, even though the phones display gives me the unlock option screen. I also tried to do a wipe in stock recovery and that does not take. Once booted into ics, though nothing works, I can mount the phone to my computer but when I try to copy over a stock image to reflash the computer gets an error and won't copy. I would also appreciate anyones help with any new ideas. I don't think its a hardware issue, but maybe?
Click to expand...
Click to collapse
i found very good solution : recycle bin
but i see on it : don't recycle
-> ye shoare ghadimi hast ke mige samsung faghat lcd ! (khak too saret samsung)

i have same problem and i cant work with my mobile
ninfragile14 said:
I am having the same exact issue. I have tried many different things. My ICS boots but everything force closes. When I installed fastboot, adb, sdk, etc., everything installs but when I run fastboot oem unlock i get the remote: erase fail error, even though the phones display gives me the unlock option screen. I also tried to do a wipe in stock recovery and that does not take. Once booted into ics, though nothing works, I can mount the phone to my computer but when I try to copy over a stock image to reflash the computer gets an error and won't copy. I would also appreciate anyones help with any new ideas. I don't think its a hardware issue, but maybe?
Click to expand...
Click to collapse
i have same problem and i cant work with my mobile

I Have Same Problem how can i fix it?
ali.md said:
i have a big problem
i buy a stock phone (I9020T)
but i cant unlock the phone with any method and cant root or flash and ...
phone random correctly boot and random (90%) hang on google logo
i cant do anything with phone when randomly boot on ! (many error)
i even cant erase and restore factory device (failed) in recovery mode (after press all keys i see standard menu)
i must 10 - 20 time pull battery and power again to ics boot up
but every thing back to a point (last user setting and photo-gallery and ...)
and dont save anything in next boot !!!
how can check internal memory for any damage ?
i thing have exact problem http://forum.xda-developers.com/showthread.php?t=993403
but phone is LOCKED and cant test that methods and cant return to samsung :'(
please helpppppppp me
Carrier TMB
LOCKED
Rom: ICS (no root, no mod, no customize)
bootloader ver: I9020XXKL1
Baseband ver: I9020XXKI1
i try every guid and tutorial to unlock and root, not work anyone !
FAILED (remote: Erase Fail) and many error like this Erase Fail or write failed
memory is readonly ? or phone was crashed ?
any solutions ????
tanx
Click to expand...
Click to collapse
can u help me ? my mobile stop with google logo
i try to unlock with fastboot oem unlock but it doesnt work
i get feil ...
Help me please if u get the solution
[email protected] please send to me email if u get the answer thank you

zaherrrr said:
can u help me ? my mobile stop with google logo
i try to unlock with fastboot oem unlock but it doesnt work
i get feil ...
Help me please if u get the solution
[email protected] please send to me email if u get the answer thank you
Click to expand...
Click to collapse
I have same problem too,Any way to fix this ?

Paper Weight
My nexus s has the fail problem too and so does my daughters,nothing will fix this problem but a new motherboard.Its a result of a hardware failure.I have tried even reseating the chips.My fix was searching the net for people selling their phone due to broken screen.I found one so far for 50 bucks and bought it.Fixed my daughters with easy by changing the board.I have spent hours upon hours reading articles on this problem.The best article i read addressing the problem was the placement of chips too close to the edge of a circuit board.After looking at the placement of the memory chip in my nexus s,I fully understand why it fails.Just by upgrading your phone and causing the phone to over heat a bit could warp the BGA seating of a chip resulting in a paper weight so to speak.This is only my response to how i feel on this subject.The end result for those with no warranty.Search the resell sites for a phone with broken screen and fix.

any solution yet ?
i look at my phone every day on my desk and ... :crying:
my phone turn back on after full wipe but storage freezed
for example wen i copy file/ delete/ format / ... and turn usb storage off and on again (without restart) everything backed !!!!
storage locked and freezed or corrupted !

help us someone please

D2G Cant do nothing, Help Plz!

Hi guys, i need help with a D2G, the phone is not mine i am trying to fix it, the problem is, that i cant flash any custom rom or stock SBF on it since the owner formating the SD card, i cant do factory reset or save current settings, always appear the same setting when i reboot, if i uninstall apps or install new apps, when reboot, the apps installed gone or the deleted apps are there again so weird.. i intall CWM but when reboot nothing happens even pressing Power + X, it just enter to stock recovery but nothing works..
Other thing is in the "System folder of the phone the Recovery folder is not there" i do not know if can be deleted, and if yes.. can it damage the phone?
I already Flash stock SBFs (VRZ_A956_2.4.33_1FF_01.sbf) and now i have
Bootloader
D0.11
Code Corrupt
I have attached a screen capture with the FAIL in RSD when flashing.. the FAIL message appear when is rebooting in the final process.
PS: the phone comes with this procedure & rom >>> http://wiki.cyanogenmod.com/wiki/Motorola_Droid_2_Global:_Full_Update_Guide
Thx in advance !!

There are two possible answers:
1. The SBF file is corrupt.
2. The phone's flash memory is corrupt (aka dead, not usable any more).

Gasai Yuno said:
There are two possible answers:
1. The SBF file is corrupt.
2. The phone's flash memory is corrupt (aka dead, not usable any more).
Click to expand...
Click to collapse
Thx for reply.
a few hours ago i made it funcional, but with the same problem.. cant save settings, in this rigth moment flashing it again.. waiting for process end. Will see what happen...
EDIT. Flash Process FAIL again. I gonna take the phone to a service...
If someone have a solution plz post it..
thx in advance
Cheers!!

Well, your phone's internal flash memory is probably fried.
The solution would be to file a warranty claim with Verizon or Motorola Mobility.

Gasai Yuno said:
Well, your phone's internal flash memory is probably fried.
The solution would be to file a warranty claim with Verizon or Motorola Mobility.
Click to expand...
Click to collapse
Thx for help man. but i am not in the USA, in my country dont have Verizon and Motorola Store.. the was bough on Ebay.. so i think i gonna sell it for parts..
Cheers !!

how did you fix this issue with code corupt? did your phone recognize usb cable? look same issue due this same spb

jararak said:
how did you fix this issue with code corupt? did your phone recognize usb cable? look same issue due this same spb
Click to expand...
Click to collapse
i cant fix the phone, the only thing i do was flash and re flash after 1st flash, and the phone comes alive again, but i have the same problem with the internal memory, no save any changes i made, if i delete an app or change a theme, when i restart the phone, everything is there again or back to the normal, and i cant made a Factory Reset.. the phone is usable but every time that i made a restart all the settings or changes are gone..
Cheers..

most likely bad flash memory
but I would try ezSBF, just to see
[TOOL] ezSBF D2G
some times it works when rsd lite fails

sd_shadow said:
most likely bad flash memory
but I would try ezSBF, just to see
[TOOL] ezSBF D2G
some times it works when rsd lite fails
Click to expand...
Click to collapse
Thx man!! i will try it.
but now i've noticed somthing, when i boot in recovery mode on the bottom appear "Error E:/System/Recovery/ not found" something like that. It can be possible to delete the recovery partition on an Android device?
Cheers mate!!
EDIT: Here is what i get when enter to Recovery, image attached..
i already used ezSBF D2G, but not solve the problem, =(
any solution for that, or the phone is "fckd up"?
Thx in advance!!

[Q] Moto G stuck; recovery fails from boot menu: Can I reflash the stock firmware?

I have a Moto G that has gotten "stuck", if that's a good description. If I start it, the initial Moto splash screens go fine and then it becomes a dark screen but backlight On and just stays stuck there for ever. (Is this what is called a boot loop? Not sure)
By using the Power + Down Vol key combo I did manage to get it to the boot menu. Unfortunately the Recovery Option there does not work. Shows a quick Moto bootup splash screen, then Says "Boot up failed" and falls to the boot menu again.
What's my best bet to recover from this?
I did install adb + fastboot on my laptop & then connected the Moto G with a USB Cable. fastboot seems to work. I could get the phone to reboot, and some other basic diagnostics. e.g. "fastboot oem get_unlock_data works". "fastboot devices" also shows my device Serial Number correctly. But I want to be careful before I issue any further erase or flash commands so I thought it best to post on here. What is the logical next step in the debug?
"adb devices" did not succeed.
The phone had the original Google / Motorola software so far and I'd never even attempted to flash it etc. Only whatever automatic updates got pushed by Google / Moto / Carrier over the network. Right before this happened I was in a call and got a bunch of pop ups saying Application xxx was being shut down.
The phone is out of warranty. It is still locked, but when I enter the details on the Moto Website it says it can be unlocked. So I can proceed to get the unlock codes etc. if that helps.
The exact SKU is XT1033. Boot menu says (Version 41.13; Battery OK; Device is locked; Status Code 0) if that is of any help. Was a Dual SIM phone on a GSM Carrier.

Tried issuing the commands
Code:
fastboot erase cache
fastboot erase userdata
Both don't seem to have helped at all.
Any other ideas?

To flash anything you first need to unlock bootloader. Doing that erases all your data including internal memory. Then you can flash a recovery & a custom rom.

legolas06 said:
To flash anything you first need to unlock bootloader. Doing that erases all your data including internal memory. Then you can flash a recovery & a custom rom.
Click to expand...
Click to collapse
Thanks @Legolas!
I did not realize that. So I guess if I just tried a flashboot flash command it would fail since my phone is not unlocked at the moment.
Luckily I can get the unlock code from the Motorola site. I will proceed to do that then first and subsequently try all the other steps needing flashing.

What happened? Did you manage to boot it up?

@carefulcat : i have a similar problem as a well.let me know if and how you managed to fix it

Lucariel said:
What happened? Did you manage to boot it up?
Click to expand...
Click to collapse
@Lucariel
Sadly not. It is still lying dead.
If you have any ideas let me know!

ravibhat said:
@carefulcat : i have a similar problem as a well.let me know if and how you managed to fix it
Click to expand...
Click to collapse
No luck yet. If you find any ideas let me know!

@carefulcat :
Check out my thread @ http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492
The only difference I find from what you've shared is that both of us have different bootloaders.
Let me know if this is true.

ravibhat said:
@carefulcat :
Check out my thread @ http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492
The only difference I find from what you've shared is that both of us have different bootloaders.
Let me know if this is true.
Click to expand...
Click to collapse
Indeed. Very similar problems. Could be identical.
I've, in fact, even erased via fastboot & unlocked via motorola's site. Hasn't helped so far.
I haven't had the stomach to download a 500 MB stock firmware yet.
Who do you think our bootloader is different?

@carefulcat :
Well,I am on an unlocked unrooted Android L 5.0.2 XT1033 Asia Retail Edition (upgraded via OTA) which has Bootloader version 41.18.
You've just cleared the ROM it seems.
Unlocking the bootloader will wipe off all the data from your device.
It seems yours is still locked,you have the unlock code but didn't use it.
Which OS did you have?Exact version,region and type of upgrade.
And which commands have you used till now?
If you're clear with the basics try stocking a Stock Flash ROM (depending on your bootloader and previous OS) or custom recovery like TWRP or CW.
carefulcat said:
Indeed. Very similar problems. Could be identical.
I've, in fact, even erased via fastboot & unlocked via motorola's site. Hasn't helped so far.
I haven't had the stomach to download a 500 MB stock firmware yet.
Who do you think our bootloader is different?
Click to expand...
Click to collapse

carefulcat said:
@Lucariel
Sadly not. It is still lying dead.
If you have any ideas let me know!
Click to expand...
Click to collapse
Took it to a repair shop, the said something was wrong with my mother, they fixed that and now the phone enters into recovery, what wont boot.
Will try the "qhsusb_dload" thing this week.

[Q] Nexus 5 stuck on google logo boot loop

Hello everybody here at XDA, ( this is my first post here so bare with me here)(english is not my native language either)
My device:
Nexus 5 - hammerhead D821(H) 16GB
BL version - HHZ12h
BB version M8974A-2.0.50.2.26
Secure boot enabled
lock state unlocked
today i got a "broken" nexus 5 that is in boot loop with the google logo and it wont boot into any .img
At the start i read the pinned posts and found this tutorial: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
followed it step by step. but unfortunatly it didnt help my situation. there werent any errors or such kind.
i also tried this tutorial with other images but nothing worked.
When i go to the recovery mode and press the power button the phone get into the google logo and i can see some sort of strange stripes in like a milisecond but then it just gets into the boot loop.
i really think ive tried everything accept for relocking the bootloader but cant imaging that this could be the problem.
If you guys need more info please just ask me.
Hope you guys can help me out here.
Martin

Really thought XDA forums would be able to help me.
Any admins or mods or any other veteran that could help me out?

If that's not working for you, you can try using the Nexus Root Toolkit just to be sure.
If that doesn't work, than it could be hardware related, and not much you can do about that.

Hi All,
I have boot-loop problem for Nexus5 as described earlier .
As I was able to boot in Fastboot
I went for factory reset, and saw FAILED (remote: flash write failure).
I have tried to flash countless time with same error.
Then I read this thread and considered phone memory is toasted.
LG service-center have quoted me around $180 for mother board replacement.
Today I tried twrp project to boot in openrecovery and start an adb shell.
I was able to see file system of my phone.
These following folders are empty:
/boot
/cache
/data
In system folder there is only bin folder and which is empty.
/system
I have gotten this far, is internal memory roasted
Any direction or suggestions welcomed :good:

mesh120673 said:
Hi All,
I have boot-loop problem for Nexus5 as described earlier .
As I was able to boot in Fastboot
I went for factory reset, and saw FAILED (remote: flash write failure).
I have tried to flash countless time with same error.
Then I read this thread and considered phone memory is toasted.
LG service-center have quoted me around $180 for mother board replacement.
Today I tried twrp project to boot in openrecovery and start an adb shell.
I was able to see file system of my phone.
These following folders are empty:
/boot
/cache
/data
In system folder there is only bin folder and which is empty.
/system
I have gotten this far, is internal memory roasted
Any direction or suggestions welcomed :good:
Click to expand...
Click to collapse
Are you sure your bootloader is unlocked?
When you boot the phone in Fastboot mode, does the "lock state" say UNLOCKED?
If so, then yeah, your internal memory could be huffed.

spookytay said:
Are you sure your bootloader is unlocked?
When you boot the phone in Fastboot mode, does the "lock state" say UNLOCKED?
If so, then yeah, your internal memory could be huffed.
Click to expand...
Click to collapse
It says Locked.
I unlock it using ./fastboot oem unlock

I just got my N5 and was messing around. Rooted it and loaded a rom, but it would just seem to hang at the spinning dots forever. Though I didn't wait THAT long like some users did and had success.
I can't find the link I used, but googling around should get you there. I ended up restoring a factory image via fastboot. I ended up using THIS PROGRAM to root the phone. This program also has a restore option and gives an option to check in case you are in boot loop status. Give it a shot.
Yes I do believe you have to unlock the bootloader as well.

Nurmi_CEO said:
I just got my N5 and was messing around. Rooted it and loaded a rom, but it would just seem to hang at the spinning dots forever. Though I didn't wait THAT long like some users did and had success.
I can't find the link I used, but googling around should get you there. I ended up restoring a factory image via fastboot. I ended up using THIS PROGRAM to root the phone. This program also has a restore option and gives an option to check in case you are in boot loop status. Give it a shot.
Yes I do believe you have to unlock the bootloader as well.
Click to expand...
Click to collapse
Yes the bootloader must be unlocked before you can do ANYTHING to the phone, it's what's there to protect it from being hacked/changed or whatever. So before you can write anything to your phone, you need to make sure you OEM UNLOCK the bootloader.

[Solved!] Nexus 5 boot loop at Google logo
I found a solution on Youtube comment (can't post url, too new user).
You just have to press quickly the Power button durint 1-2 minutes (continue untill the Android animation start, don't stop when the Google logo appear)3
As crazy as it sounds, IT WORKS

Wow .. i had the exact same problem (Startup loop on Nexus 5 that shows the Google logo and restarts, over and over), and i pressed the power button quicky about 30 or 40 time until after I saw the startup animation and my phone came back to life. I have been charging it with cables other than the one that came with the phone for a few months now, and it has been acting strangely while plugged in (randomly clicking things on the screen, and enabling my camera and taking pictures on its own, etc.). So, to avoid problems in the future, I think I'll invest in a wireless charger. Thanks JackNUMBER for the easy solution. I hope this works for others as well. Saved me a trip to the store.

Nexus 5 bootloop, stuck in Rom intro - Don't know how to connect it to my pc

First of all, I'm pretty noob this days on Android so I'm very sorry guys, also english is not my first language.
My nexus was working great until today. I ended a Whatsapp Call and get a black screen, phone looks frozen (happened before). Reboot it and works fine for 5-10 minutes, after that it started to reboot itself the whole time in bootlop, stuck in the rom intro, after the Google text. My rom is one of the very first roms from Slim Roms, I'm sorry I don't remember the Android Version, but is "old".
I can access to the recovery mode tho. I tried to wipe dalvik cache and the TWRP failed, wipe and factory reset, fail as well... I don't know what else to do. I don't have any image to install in the sd, or any backup. Windows 10 recognize an "android" but can't access to it so I can't copy any file to it.
Is my phone dead or can I do something? I love this phone :crying:

Any help please? I tried using ADB and get to copy some files into the phone but still every time I try to do a wipe cache, factory reset or what ever I get a Unable to mount Data / Cache / Storage... every time the same error.
I google it and found that some people could fix that error by repairing the file system and select ext4. But I can't do that, my TWRP build is quite old (v2.6.3.4) and doesn't have that option here. Any suggestions?
Thanks btw

Me again
I've been reading forums for more than 7 hours today and trying different solutions, and nothing. But found this guy here https://androidforums.com/threads/is-my-nexus-5-dead.1099076/
He basically had the same issue as me few years ago, exactly the same, He didn't find any luck apparently.
How is it possible that a phone that can get access to TWRP or copy/flash files via ADB/Fastboot can't be saved? Theoretically in this case this is not a hard bricked, right? So? This is so so weird

It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.

No OS but twrp working
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!

audit13 said:
It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.
Click to expand...
Click to collapse
I tried that already, it does the installation thing but always fail in the end
mevrik_007 said:
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!
Click to expand...
Click to collapse
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad

ekeixdurden said:
I tried that already, it does the installation thing but always fail in the end
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad
Click to expand...
Click to collapse
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.

audit13 said:
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.
Click to expand...
Click to collapse
I tried that with the Nexus root tool kit and the bootloader still is unlocked

ekeixdurden said:
I tried that with the Nexus root tool kit and the bootloader still is unlocked
Click to expand...
Click to collapse
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.

audit13 said:
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.
Click to expand...
Click to collapse
Shieeeet... So nothing to do I guess? I already ordered a new phone but if I can save this beauty would be great

It would be great to fix it but the simplest solution may be to buy a nexus 5 with a smashed screen and working motherboard. I've done this before and it's worked out well because the nexus 5 is pretty old by today's phone standards so I got it cheap.

hmm not a bad idea at all. Thank you!