Hello guys,
I've read more or less all threads I could find on the EMMC brickbug, /data partitions locked, phone doesn't boot et cetara but I've got a problem that seems to match all of those problems fairly well, but not really 100%.
I've got a GSM Galaxy Nexus and after the upgrade to 4.1.2 my telephone suddenly started to bootloop (stock, but I did a factory reset). Eventually I pulled the battery and in desperation I decided to download the original Google Factory Image and flash it using ./flash-all.sh and that was when all hell broke lose. I got the fastboot usb_read error and got screen tearing. After that, I couldn't even boot the phone anymore, it was completely dead, so I started to research all over Google.
After a good while of searching and installing Windows on a separate partition I eventually used the GT-9250 OMAPFlash and behold, the phone booted again (well, just to the bootloader, but still, it at least turned on). I decided to do flash-all again and got the very same problem again. Phone locked up, had to do OMAPFlash and next time I started the phone was warning that recovery et cetara is missing, but I still got to the bootloader.
I started to get creative and instead of trying to flash again I fastboot-booted into a temporary Clockwork Recovery (fastboot boot recovery-clockwork.img) as to gain ADB access, which also worked fine. I tried to wipe everything and that worked evenly well (well, except /data which is inaccessible according to clockwork).
So I tried to flash yet again, failed, and did the entire procedure again to get to Clockwork. I started to research on flash memory problems and found something about the EMMC brickbug after which I ran all the tests (dd if=/dev/block/mmcblk0 of=/dev/null and the scripts that are kindly provided here on the forum). Result: No brick found but I didn't quite trust the findings despite running all tests several times. I decided to move the system, cache and data partitions using parted a little further back on the flash. That worked well, no lockup or anything. But the second I try to flash (both using the shell with flash_image or fastboot) the phone will immediately lock up the second the first bytes are written.
What is weird with this is that writing change to the partition table isn't causing locks, formatting /system or /cache doesn't cause locks, only the writing to the partitions will cause an instant lock.
So, my question is: Do you guys recognize this problem (i.e. no brickbug evident during testing, no problems writing partitions or wiping but instant lock when doing either flash_image or fastboot flash)?
Any tips are greatly appreciated!
Can you relock bootloader?
Sent from my i9250
bk201doesntexist said:
Can you relock bootloader?
Sent from my i9250
Click to expand...
Click to collapse
fastboot oem lock and fastboot oem unlock work fine.
there's a possibility that the device is still under warranty, relock/return it.
sent from my i9250
bk201doesntexist said:
there's a possibility that the device is still under warranty, relock/return it.
sent from my i9250
Click to expand...
Click to collapse
Hehe, alright. Was kind of expecting that answer when you asked whether or not I can lock it, but yes. I have 3 weeks left on the warranty.
That aside I am really curious on whether this IS the EMMC brick, a variation of it, or if I am just unlucky that I ran into a regular hardware defect a day after the 4.1.2 update.
Danie1 said:
Hehe, alright. Was kind of expecting that answer when you asked whether or not I can lock it, but yes. I have 3 weeks left on the warranty.
That aside I am really curious on whether this IS the EMMC brick, a variation of it, or if I am just unlucky that I ran into a regular hardware defect a day after the 4.1.2 update.
Click to expand...
Click to collapse
actually, i asked because i'm almost 99% sure you're not facing emmc corruption.
A couple of ideas: tried other computer/usb port/usb cable? Checked usb port on the phone for dust, damage?
Thing is, omapflash doesnt detect corrupt emmc.
sent from my i9250
bk201doesntexist said:
actually, i asked because i'm almost 99% sure you're not facing emmc corruption.
A couple of ideas: tried other computer/usb port/usb cable? Checked usb port on the phone for dust, damage?
Thing is, omapflash doesnt detect corrupt emmc.
sent from my i9250
Click to expand...
Click to collapse
Yeah, I did test if there was something wrong with the USB connection. Even tried with a different computer and different cables. Same thing. Anyway, I packed it up and will return it to the store, let's see what they will find.
Related
Help.... A100 was running fine last night, but hung.... I rebooted it and just got the acer logo and nothing else....
I was running ICS, (not sure which version)....
I've tried quite a few roms as 'update.zip' but all i get is the 'droid' picture, then it lies down with a big red '!'.
Now, all I can do is get into 'bootloader v0.0.13-ICS: Starting Fastboot USB download protocol'
If i connect to pc, doing adb devices shows no devices..
any ideas? :crying:
Yeah eMMc is a goner.
Sent from my Galaxy Nexus using xda app-developers app
filking said:
Help.... A100 was running fine last night, but hung.... I rebooted it and just got the acer logo and nothing else....
I was running ICS, (not sure which version)....
I've tried quite a few roms as 'update.zip' but all i get is the 'droid' picture, then it lies down with a big red '!'.
Now, all I can do is get into 'bootloader v0.0.13-ICS: Starting Fastboot USB download protocol'
If i connect to pc, doing adb devices shows no devices..
any ideas? :crying:
Click to expand...
Click to collapse
Adb commands don't work in fastboot mode, you need fastboot devices instead, so adb devices not working doesn't mean anything. If it did work that's odd though lol. Also, booting in fastboot is the wrong mode anyways, use the other volume key for recovery, for now remove the external sd then boot recovery and report back what happens there.
Tapatalked from my HTC DNA
Ok, removed the usb and external SD.
Do the other boot I get a quick message saying 'erasing cache before sd-update'
Hold on...
While typing this, it's changed..
Before I had the 'droid' then he fell over when '!'... it's done that again, but straight away it's got loads of messages.
E:Can't open /dev/block/mmcblk0p5
(no such file or directory)
that is repeated several time for dif files/directories...
Then it displays the recovery menu.....
reboot,
apply update
wipe data
wipe cache
apply update
1st time it's shown that....
Next step??
Anyone help??
I have the Android system recovery utility...
What now?
filking said:
Anyone help??
I have the Android system recovery utility...
What now?
Click to expand...
Click to collapse
You can try wiping but that error is usually a dead or dying emmc.
Also, have some patience, we have lives to live we answer when we can.
Tapatalked from my HTC DNA
lol, sorry... 2nd post wasn't meant as a 'hurry up and fix mine, because i'm more important'.....
I was typing something else in, then i decided that was stupid, so i deleted and put that instead....
my bad...
:angel:
just as an update, this may seem silly to some but if I don't tell you i'll never know...
The recovery does nothing, so I put it in bootloader mode...
connect up the usb,
then typing 'fastboot reboot' does reboot the device... so maybe other commands will work??
how do i wipe?
and i'm clutching at straws....
filking said:
just as an update, this may seem silly to some but if I don't tell you i'll never know...
The recovery does nothing, so I put it in bootloader mode...
connect up the usb,
then typing 'fastboot reboot' does reboot the device... so maybe other commands will work??
how do i wipe?
and i'm clutching at straws....
Click to expand...
Click to collapse
Fastboot commands will always work provided drivers are installed and it can boot into fastboot, it doesn't mean you aren't in the process of bricking, just hasn't gone all the way yet. When its final you won't even get a screen that lights up or vibration.
Since you asked though in recovery you can wipe cache but that will likely give errors again. The nuclear option is fastboot erase userdata but that's like massive data destruction, even internal sd I think.
As you're stock, stop now, and get in touch with acer and see if they'll cover it for warranty repair under their 1 year BS coverage.
Tapatalked from my HTC DNA
Please excuse my ignorance to some things.
The tab isn't under warranty, it's 15 months old
It wasn't stock, i had one of the modded roms installed... (but i can't remember which one, I did it last year sometime to swap internal disk for external one to give me more space)..
I'm not worried about anything on the tablet at all as luckily I did a complete system backup on titanium 2 days ago on my external sd.
Cheers
filking said:
Please excuse my ignorance to some things.
The tab isn't under warranty, it's 15 months old
It wasn't stock, i had one of the modded roms installed... (but i can't remember which one, I did it last year sometime to swap internal disk for external one to give me more space)..
I'm not worried about anything on the tablet at all as luckily I did a complete system backup on titanium 2 days ago on my external sd.
Cheers
Click to expand...
Click to collapse
I said stock because you have a stock recovery, though fastboot mode says you rooted and all that at some point. Probably ran a stock based Rom and ended up overwriting recovery which makes this harder to figure out. But its 99% likely its dying.
You can manually flash a recovery in fastboot and try to factory reset there or just do the fastboot command in my last post.
Tapatalked from my HTC DNA
Thanks for all the replies... I'll look round the forums to work out how to flash recovery in fastboot mode, then i'll try the wipe userdata.
If that fails,i'll just wait.... I noticed that the genius's are currently looking at ways to fix the numerous brick problems so maybe in the future there will be a simple solution..
Has there been an actual reason for the brickage... Is is motherboard related?
filking said:
Thanks for all the replies... I'll look round the forums to work out how to flash recovery in fastboot mode, then i'll try the wipe userdata.
If that fails,i'll just wait.... I noticed that the genius's are currently looking at ways to fix the numerous brick problems so maybe in the future there will be a simple solution..
Has there been an actual reason for the brickage... Is is motherboard related?
Click to expand...
Click to collapse
Read the brick thread for info on it, but short answer is emmc died.
Tapatalked from my HTC DNA
Well, acer support want £55.15 just to post it back to them, then they will call with cost of repair... lol I don't think so somehow..
Luckily I am in a good position at the mo, so i've just purchased a nexus n7...
I'll monitor this site until 1 day maybe one of the genius's on here will find a cheaper cure..
Good luck all...
(i'll be moving to the nexus section now then.. look out overthere.... :silly
Hello,
just some hours ago my Galaxy Nexus (SC-04D) rebooted while lying on the table next to me. After several sings of vibration I noticed that the phone doesn't boot completely.
When switching on the phone I get the turn-on-vibration, then the google letters are displayed. Most times the word "google" flickers from left to right over the screen (only the line where the word is supposed to be). Sometimes it boots further and I get the colored "X" displayed. This symbol starts flickering, too and if it went so far it reboots.
Here are two pictures I took from the phone failing to boot:
picpaste.com/img_0001_01-Rmm7kDYb.jpg
picpaste.com/img_0001-eoLqVoiM.jpg
The phone is running stock Android from Docomo. The phone is about 14 months old and has never been unlocked, rooted, modded, taken a bath, ... 'til now.
I tried starting with and without SIM-card, with and without charger attached and let it lie around for several minutes without battery between my tries.
Is there any chance to get my data from the phone or even get it fixed? Please give me a hint what I can do.
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix. This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Thanks GPFboy for your fast response,
GPFboyJS said:
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix.
Click to expand...
Click to collapse
As far as I understand a factory reset results in a complete loss of data on the phone, right? So without root/unlock there's no chance to get my data from the phone? That would be really bad.
GPFboyJS said:
This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
Click to expand...
Click to collapse
What is "too many"? I think there are about 35 apps installed atm. By the moment the problem arose wifi and 3g-data,BT,GPS were disabled and just a minute before I took a look how late it was. So nothing special.
GPFboyJS said:
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Click to expand...
Click to collapse
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
BrainSD said:
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
Click to expand...
Click to collapse
thats stock recovery.
is your bootloader already unlocked or no?
Zepius said:
is your bootloader already unlocked or no?
Click to expand...
Click to collapse
It's still locked.
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Zepius said:
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Click to expand...
Click to collapse
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
BrainSD said:
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
Click to expand...
Click to collapse
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Well if I was him I would be more worried about my expensive phone instead of data. Maybe a lesson for later to have a backup
Sent from my Galaxy Nexus using XDA Premium HD app
beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Yes exactly this is the point. Since I don't have a current data backup the first thing to try is getting my data from the phone. I already tried temporary loading the clockwork recovery through fastboot - with the galaxy nexus toolkit and by hand(sdk) - but it failed ("Bootloader locked").
What I'm wondering about is the fact that the phone seems to behave normally in odin and fastbood mode but going nuts the moment it's expected to boot. Besides the flickering google logo and the "matrix-modded" dead android it even ended up in a totally green screen one time.
At the moment I don't dare trying to unlock/flash the phone because of being afraid getting stuck and ending up with the phone being in some kind of undefined / totally broken state. Initially I was in hope of being able to rescue my data but now i will try my luck with docomo support first.
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
I will try to get through 1 to 4 of the guide first and see how far I get.
If this won't work I might try to unlock, recover and try to "undelete" what's possible. (http://forum.xda-developers.com/showthread.php?t=1994705)
Does this order make sense?
Btw, having a dead phone is bad, of course, even when I got it new for 2300Yen but loosing some pictures i really liked and having no phone atm currently hurts more. Especially when knowing that I was thinking of copying all photos to my computer only one day before when I pulled only some minor important ones from the phone I needed for work and planned to do a full backup and unlock this weekend when I get back my 'Milestone' currently lent to someone else.
Once again something I learned. Backup! Even you phone.
BrainSD said:
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
Click to expand...
Click to collapse
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.
It will unlock your bootloader, bypassing fastboot. Still, it's not for the faint hearted. I refered to omapflash because its a low level tool, it doesn't require the bootloader to be unlocked, and is able to restore the bootloader to working state, and I got there because you mentioned you see graphical glitches/flickering which may indicate bootloader partition failure and/or consequent corruption.
I think that's your best shot at trying to get your data back. After unlock, boot to fastboot and 'fastboot boot custom_recovery.img', and grab your stuff (if you can) from /data/.
beekay201 said:
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.....
Click to expand...
Click to collapse
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
BrainSD said:
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
Click to expand...
Click to collapse
Great, so far so good.
Yeah, they're ext4 images, but sparse images i believe - link
For the last days I've been struggling with this friend's device. Some days ago, it just restarted itself and entered endless Bootloop..
The installed rom is slim and cwm recovery.
Here comes the tricky part: only able to enter recovery and bootloader, no matter what you do, the whole device stays unaltered. First we tried wiping the data partitions. It seems to perform it properly, without any errors, but the data is still there, unaltered.
Then, we tried changing the recovery. From fastboot, we flashed twrp, the process seems to go A-OK, but then you restart into recovery and.... You're still on cwm.
Then tried the next level. rm - rf, the process seems to work but... No, no.... The data's still there.
Ok, we brought the big guns: dd on the partitions seems to be performed properly, as usual, the message with the written bytes and that the partition is out of space. The process seems to go as it should, but no.... All the data is still there.
The next step would be calling a priest and bringing some holy water, but first I want to give it a try and ask you guys. What the hell is happening here?
Fried EMMC, need to change.... nothing will stick
Why does that happen??
samersh72 said:
Fried EMMC, need to change.... nothing will stick
Click to expand...
Click to collapse
That same thing happened to me. I just wanted to know how eMMC got damaged so next time I can be careful...
Can moisture be the culprit?
Same to me... i sent my phone to assistance... i hope they repair it without charging fees (because mine is still in warranty)
Today I had my phone in pocket, when I felt it is rather hot. I took it out, pressed power button, Screen lit up and died. Phone is still working, I managed to copy files from sdcard to my PC just in case. Connectors seem fine, but I'm not sure.
I tried doing factoy reset using following commands:
adb reboot bootloader
fastboot devices
fastboot -w
Click to expand...
Click to collapse
And I got message:
Erase successful, but not automatically formatting.
Can't determine partition type
Click to expand...
Click to collapse
I have root, I tried to flash custom rom a while ago but failed so I'm still on stock ROM and kernel. I'm S-ON. After reverting changes phone worked fine, so I doubt it is the reason. Battery should also be fine, I've recently replaced it with new one.
So...I'm put of ideas. I can't really check whether my ROM is working fine. Buttons are responding tho, I can feel(vibrations) after I blindly try to unlock the phone, so I guess it's screen issue.
This could be sleep of death, but it is supposed to be fixed(even if temporarily) after resetting phone/unpulgging battery.
Edit: Confirmed an issue, backlight is not working :/ So the question now is: which connector is responsible for backlight? I'd like to try to clean it first before ordering new one.
Sorry if the thread is not in the right place and not fancy written, I don't use forums a lot..
So I've had that phone for about 3 years now. I've never rooted the device, never installed any custom roms, nothing. Only did a factory reset/wiped data couple of times.
One day I woke up (on 2nd of January), looked at my phone (it was charging whole night) and it was showing the "Google" logo. After that it switched to "colorful X", then it turns off, vibrates and all over again.
I was doing it until I took out the battery for a half an hour. Plugged it back in, turned on... Same thing was happening.
I've removed the battery again and plugged it back in. Pressed the power + vol up + vol down buttons in order to get into the bootloader. Got to the "recovery" and wiped the data/factory reset, and wiped the cache.
Restarted, didn't work.
Got mad here and decided to first time to attempt installing a rom. I've got to the google developer website where there are factory images. There were a couple of versions of the Galaxy Nexus. I didn't know which one to pick, so I've picked the first one (GSM with google wallet latest version). (I've already had Android SDK) so I've followed the instructions by using the "fastboot oem unlock"
then "flash-all". It failed. And the reason is when it rebooted, the bootloader locked again and the script couldn't continue installing/flashing.
So every time I unlock the bootloader and reboot, it locks it again.
I've decided to flash every img individually. By using this pattern:
fastboot oem unlock
fastboot flash bootloader bootloaderblabla.img
fastboot reboot-bootloader
fastboot flash...... and every single image including the radio, boot system, etc....
basically every time I flash and reboot, I unlock the bootloader.
That however didn't fix the problem, it was still remaining in the bootloop.
So I am not sure which version of the galaxy nexus I have, I've tried doing that will few versions of the factory images with no success.
So I came here, in a chance to get it fixed by some magic!
Please help?
Corrupted EMMC (internal memory chip).
Currently no solution to this, unfortunately.
Basically the firmware of the internal Memory Chip screwed up. The firmware on the memory thinks your data might be in danger and switches to read only mode (these firmwares are similar to SSDs for PCs, so thats a good thing in general). So if you unlocked your bootloader, you could retrieve your data.
This is however solveable by reflashing the chips firmware, but it's unshure if this even could be done while the chip is soldered onto the motherboard.
Check the latest pages of the CM12.1 thread, there was some discussion about this topic. If you find a good phone repair place they might have a JTAG flashbox and could reflash the EMMC.
Other soultion would be to replace the board.
Same thing happened to me and I changed my motherboard
Sent from my Galaxy Nexus using XDA Free mobile app
playitlouder said:
Corrupted EMMC (internal memory chip).
Currently no solution to this, unfortunately.
Basically the firmware of the internal Memory Chip screwed up. The firmware on the memory thinks your data might be in danger and switches to read only mode (these firmwares are similar to SSDs for PCs, so thats a good thing in general). So if you unlocked your bootloader, you could retrieve your data.
This is however solveable by reflashing the chips firmware, but it's unshure if this even could be done while the chip is soldered onto the motherboard.
Check the latest pages of the CM12.1 thread, there was some discussion about this topic. If you find a good phone repair place they might have a JTAG flashbox and could reflash the EMMC.
Other soultion would be to replace the board.
Click to expand...
Click to collapse
Ahh that's unfortunate, I think it's better to upgrade to a new phone.. It became laggy anyway.
Thanks!
Hello, please for help, I will not create new thead.
I have a problem, I'm tring to start phone and stucks on bootloop.
The solution should be start recovery, but my second problem is volume down doesn't work.
Is any chance to get to recovery throught ADB while phone is turned off?
Thanks.