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)
Related
Hello, I have a weird issue, I looked in the brick thread but didn't see any thing that was just like my issue. Last night I tried flashing the rom and used the zero system wipe available in the dev thread (not saying that is the issue just saying what I was doing). It was clearing the cache(never got passed the cache) for over an hour, then it powered off. I tried restarting it into recovery and it did half the time(especially if I removed the sd card) but couldn't mount anything(sd card /system, /data, etc). But this is were it starts getting weird and not like the brick thread. This morning I tried it again and it booted to recovery and mounted everything!!! Thought it was fixed so I went to do a factory reset to install a new rom. That was an hour ago and it is still clearing cache. The lines in the progress bar slowly move but no blue progress bar at all. Any help at all will be appreciated. I am afraid it will power off again and be a true brick this time (then again maybe it already is)
I am using TWRP and was on the 9/02 cm10 nightly before this all happened.
Thank You.
Edit: still clearing/formating cache but upon closer look it did format /data
nsmith4 said:
Hello, I have a weird issue, I looked in the brick thread but didn't see any thing that was just like my issue. Last night I tried flashing the rom and used the zero system wipe available in the dev thread (not saying that is the issue just saying what I was doing). It was clearing the cache(never got passed the cache) for over an hour, then it powered off. I tried restarting it into recovery and it did half the time(especially if I removed the sd card) but couldn't mount anything(sd card /system, /data, etc). But this is were it starts getting weird and not like the brick thread. This morning I tried it again and it booted to recovery and mounted everything!!! Thought it was fixed so I went to do a factory reset to install a new rom. That was an hour ago and it is still clearing cache. The lines in the progress bar slowly move but no blue progress bar at all. Any help at all will be appreciated. I am afraid it will power off again and be a true brick this time (then again maybe it already is)
I am using TWRP and was on the 9/02 cm10 nightly before this all happened.
Thank You.
Edit: still clearing/formating cache but upon closer look it did format /data
Click to expand...
Click to collapse
I've seen this happen one other time, though it happened just running in android, lost cache etc but just magically came back to life after being off for awhile. In that case AFAIK it didn't brick, or it did and they just never mentioned it.
It does however sound like its gonna give out and just lose them for good.
Only thing I can really suggest is just flash a ROM and see how it goes.
Tapatalked from my Galaxy S II.
pio_masaki said:
I've seen this happen one other time, though it happened just running in android, lost cache etc but just magically came back to life after being off for awhile. In that case AFAIK it didn't brick, or it did and they just never mentioned it.
It does however sound like its gonna give out and just lose them for good.
Only thing I can really suggest is just flash a ROM and see how it goes.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
It still says formatting cache should I just force shut down.
The diagonal lines in the progress bar are moving more smoothly now if that means anything.
Thanks for the reply.
nsmith4 said:
It still says formatting cache should I just force shut down.
The diagonal lines in the progress bar are moving more smoothly now if that means anything.
Thanks for the reply.
Click to expand...
Click to collapse
It will probably eventually shut down or reboot on its own if its having filesystem problems.
If you have adb up you can do adb reboot recovery and bypass the cache format it usually does when you use the volume button. Also you can pull a dmesg which will show what's going on in the file systems.
Tapatalked from my Galaxy S II.
well the device shut down again. It won't even boot to the acer screen, blue light just flashes. The computer knew I plugged something in but ADB says no devices. Guess it is bricked.
thanks for your help
nsmith4 said:
well the device shut down again. It won't even boot to the acer screen, blue light just flashes. The computer knew I plugged something in but ADB says no devices. Guess it is bricked.
thanks for your help
Click to expand...
Click to collapse
Yeah sounds like failsafe apx which happens on numerous sequential failed system or boot reads. If its under a year old I should suggest getting a rep on acer chat to set a repair in motion. If its under warranty it just costs shipping it to them. The rep can tell you if you're still covered.
Tapatalked from my Galaxy S II.
Thanks for all your help. Hopefully since it won't boot they won't notice I rooted and unlocked the boot loader.
nsmith4 said:
Thanks for all your help. Hopefully since it won't boot they won't notice I rooted and unlocked the boot loader.
Click to expand...
Click to collapse
If its in failsafe no they just replace the board and send it back. If it can get to the Acer screen then they can tell.
Tapatalked from my Galaxy S II.
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.
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
So a week back.
I was just chilling on my phone playing clash royale
And all of a sudden..
My phone just rebooted..i thought it is normal...as i am rooted of due to some issue it rebooted
But after waiting for some time... I saw that... It is rebooting again and again to the galaxy note 2 logo and was not going ahead
So i plugged in my charger and it went to the homescreen...but i was unable to do anything
Yesterday after googling everything my mind coud thing
But got no result for this issue
So i decided to flash stock rom
But even after flashing stock...it is behaving like before
I even did a full wipe including internal sd from twrp
Still nothing.. Then i decided to restore it from a previous twrp backup created a year before.. Still the same thing
Not it is successfully booting but..i still cant go past lock screen.... As soon as i unlock...it just freezes and reboots..
And as soon as i remove my charging plus...it starts to reboot again like crazy... Plz hepl... Never encounterd this issue before
I love my note 2 and dont feel like changing my beloved phone
Have you tried a factory wipe using stock recovery right after flashing stock rom with Odin?
If nothing works, the memory chip may be damaged.
audit13 said:
Have you tried a factory wipe using stock recovery right after flashing stock rom with Odin?
If nothing works, the memory chip may be damaged.
Click to expand...
Click to collapse
Thank you very much for replying
If the memory chip is damaged in that case
What can i do?
You would need to replace the motherboard if the memory chip is damaged.
audit13 said:
You would need to replace the motherboard if the memory chip is damaged.
Click to expand...
Click to collapse
I dont think...that it is the sds (sudden death syndrome) my phone only turns on....while im charging it. But if i enter recovery while charging the phone...and then....if i remove the cable... It stays normal
But as soon as i quit the recovery mode and turn on my device....ut just does not show any thing...
I can enter download mode as well
But recently... It started guving me error like....cache not found...something like that....
I will post a pic...as soon as i reach home
Failing to mount partitions is an indication that something is wrong with the memory. If flashing a stock ROM with a pit file is successful but does not allow the data and cache partitions to be wiped/mounted or the ROM cannot be booted, the memory chip could be damaged.
my phone was working normally and all of a sudden I came back to my room and it only displayed the galaxy a50 starting screen (the one before there is just "samsung" written).
Restarting it didn't help and it always gets stuck at the same display or restarts endlessly. Sometimes it makes it until the "samsung" display.
Firstly, I don't really know why it rebooted anyway and the problem started. There is a software update I should have been doing for quite some time, so maybe that got executed automatically (is that even possible?) and failed?
What I already tried:
Charging (100% charged)
Went into recovery mode and:
repaired apps (didn't help)
powered off and restarted after 20 minutes of being turned off (didn't help)
Run graphics/ locale test (didn't help, the graphics test said something about deleting so I got afraid and restarted it. Could I have lost some data because of that?)
click on mount/system (as far as I can tell nothing happened)
wiped cache partition (didn't help)
clicked reboot to bootloader (what does that do? There was written downloading but then I got scared and restarted the phone, could that have done some damage?)
Rebooted (nothing happened)
downloaded drphone, phone does not get recognized
As you might see, I'm a bit desperate and although being quite tech savvy I don't know that much about android.
What is most important to me is recovering/ not deleting the data on my phone (last backup is about one month old so not too bad but still very bad for me) so please suggest safe options first in that regard (if there are any).
Can I maybe just update the software via ADB without damaging my data?
Or use ODIN for that? Also heard something about TWRP. Don't really know how any of these three work exactly (but totally willing to learn how!)
Your help would mean the world to me
the deleting part in the graphics test is just texts it does nothing. i dunno if the usb debugging is enabled, but if it is get alternative boot partition (saved my pixel 4 like that). i used linageOS 20 recovery mode that got me to os i backed up my files and then reflashed.
KirinPixel said:
the deleting part in the graphics test is just texts it does nothing. i dunno if the usb debugging is enabled, but if it is get alternative boot partition (saved my pixel 4 like that). i used linageOS 20 recovery mode that got me to os i backed up my files and then reflashed.
Click to expand...
Click to collapse
Thanks very much for your reply! I found out quite a bit by now and it seems to me after intensely studying this thread https://forum.xda-developers.com/t/...ce-is-stuck-on-boot-loop.4536965/page-2#posts only reinstalling the software (most likely with ODIN) is the way to get back to the phone working properly. You don't know anything about that, maybe? I'm very afraid to do it wrong and wipe my data.
Can I just reinstall the already installed software version? Or should I go higher?
I restarted it once though and even put in my PIN but after the home screen appeared it fell back into the bootloop again.
I have no experiance with samsung odin. But what i say is you bring it to someone who does to back ya fils up. Then go play with flashing. Odin is far from the only way. Unfortunately i can not assist you on it because i never used it. Good luck!