Develop Bugs

A100 bricked, possibly even dead, need help

Okay so I'm running stock ICS without root or any custom stuff, everything just stock, today I was listening to music and decided to change the songs, so I pressed the power button but the screen didn't come on, tried a few more times, the screen didn't come on but the music kept going, so out of desperation I held down the power button and after 3 seconds or so it sounded like a BSOD, sound repeated quickly for a second then just nothing.
So after that I tried starting it up back again, here we go, acer logo....aaaannnddd.......nothing.
Tried a few more times and left it over 30 minutes yet nothing. just that acer logo.
so finally I though I could flash a stock rom file, so I grabbed the .014 ics file and put it in my freshly formatted micro sd under the name update.zip (and no I didn't have the double .zip), then I went to recovery, it came up with the familiar android with his chest open and the spinning cube thingy in front of him, then after 5 seconds it came up with the android and the red warning sign above him, which usually meant either SD card not found or update.zip not found, tried a few more times and NOTHING.
FINALLY, I tried the volume down and rotation lock method to try factory reset, it erased userdata and cache and fingers crossed...yet nothing.
am I SOL? Or is there any hope at all, I tried connecting to a computer while it's at the Acer logo screen, you can hear the USB connect and disconnect sound, but adb won't detect it, please help, I love this thing too much and Acer wants me to pay 100 dollars to fix it, I'll die before I do that.
ANY HELP will be appreciated, any suggestions are welcome.

Bump, anyone please??
I love this tablet too much

Try update.zip again on a different SD card. Not all of them work in all devices. Also doubt check its formatted fat32 not something else. Are you sure you have the proper drivers installed for adb?
Tapatalked from my Galaxy S II.

pio_masaki said:
Try update.zip again on a different SD card. Not all of them work in all devices. Also doubt check its formatted fat32 not something else. Are you sure you have the proper drivers installed for adb?
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
I have proper drivers installed and I tried with 2 sd cards, one was almost full but on FAT32, and one was freshly formatted to FAT, I'll try format to FAT32 and report back

I tried formatting to FAT32, placing the update.zip
Sadly, didn't work
Any other suggestions anyone?

Metallica 4 Life said:
I tried formatting to FAT32, placing the update.zip
Sadly, didn't work
Any other suggestions anyone?
Click to expand...
Click to collapse
What does didn't work mean? The answers are in the details, we need them or we're just guessing at random things. Any text, vibrations, lights, pictures all that.
Try adb from a different cable, port, computer? Try hard reset again, hell try 3-4 times, sometimes it takes some persistence.
Oh also plug it into power supply, low battery can cause issues too.
Tapatalked from my A100 - Flex Reaper RF1.

I've been trying for a few days with almost everything, tried APX mode but apparently it doesn't work since you need the CPU ID
and by "doesn't work", I mean I get the vibration, the acer logo pops up, then at the top it starts saying the loading update.zip stuff, then it goes to the green android with it's chest opened and a small blue link ball rotating beside him, after 7-8 seconds, it just shows a dead android, with his chest open and a red triangle with an ! in it.
So yeah, ADB doesn't work, as it never goes past the acer screen.

OK have you managed or tried fastboot? If you can manage that then you should be able to get adb up.
This is basically what I mean about fast boot
http://forum.xda-developers.com/showthread.php?p=27015316
Tapatalked from my Galaxy S II.

Only if I can get to fastboot from stock bootloader, everything I had was stock, OTA ICS, stock bootloader, and no root

Metallica 4 Life said:
Only if I can get to fastboot from stock bootloader, everything I had was stock, OTA ICS, stock bootloader, and no root
Click to expand...
Click to collapse
You can that's how you unlock the boot loader, check out that post and give it a shot.
Tapatalked from my Galaxy S II.

Can you maybe link me or if you know tell me how to get to it? I'm kind of new to all of this :/, I tried searching with no results

Take a read through this thread
http://forum.xda-developers.com/showthread.php?t=1655945
It discusses a slightly different scenario but the techniques attempted are what I mean to try.
Post #3 gives a good outline of steps to try. Also 14 25 31 maybe 27 if it goes south.
I've never personally experienced this so I have no experience however the process in that thread is the same I would attempt if it happened to me. Basically it will attempt to unlock the boot loader then flash a custom recovery which you can then install a new rom. It will turn it into a modded device BUT it will unbrick you and make repairing this issue a lot easier in the future.
Tapatalked from my Galaxy S II.

Gave up
Update:
So yeah i've tried everything and nothing seemed to work, all it shows is that acer logo
Gave it to my sister, she said she'd send it back to the acer facility, hope for best.

[Q] A100 Is it bricked?

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

[Q] Potential hardware issues/ brick / batter issue? Please help

Hello all. Let me first thank you for your time in reading my post. I appreciate it. I'm not a fan of only posting for help but I suppose that the site suggesting to always search first is to thank for that because I am usually able to find answers. So please forgive me if this is posted elsewhere but I really have searched and asked around but haven't seen anything similar to my issue. If there is something like it I do not know what to call it. I at first thought it was a sudden death, but realized I think my device model & the symptoms have disproved this theory.
My story...
I bought my AT&T Galaxy S3 feb 2013. I have had it, spent a month or two stock everything. The past month & a half I have flashed CM 10.1 & most recently PK-2.32 for about 3 weeks. Have ran it and loved it with no issues. Used the kernel that comes with both ROMs.
4 days ago
I was charging my phone at work, picked it up after a while, and it wouldn't turn on. It was stuck in a loop of 2 of the screens in my attachments(the battery screen & the SGS3 logo). The battery screen is not in motion, it is stationary like that so that the circle doesn't move.
I have tested quite a few things in regard to what I thought might be the issue...other batteries, chargers, cables pull sim & SD and still no luck...etc.
While the phone is unplugged I get no indication of life. Only when I plug it in will it show me the battery symbol & the logo.
After some playing with it while it is plugged in I have been able to get it into download mode quite frequently with no issue as seen in the third attachment.
So yes I can get into download mode but I'm still "fairly new" and not sure where to proceed from here. I'm not sure what my options are as this is new to me and I can't find anything related, nor can my much more experience friend who is not so new at it that got me into wanting to load custom ROMs.
And yes, as you can see it has tripped my flash counter up once, from what I've read there's only one way to fix that if I need to send it in.
So...If you are able and willing to help I would greatly appreciate it and any options you might give me. I'm willing to try almost anything as my phone is of no use to me at this moment.

if you can access download mode,one option is to connect the device to your PC and flash the stock firmware via odin. untick the Auto Reboot option. once you get a PASS, pull the battery, replace and immediately hit vol up + home + power button. when the device vibrates, release just the power button. in recovery, wipe data/factory reset, wipe cache. reboot.
first, can you boot into recovery at all?

xBeerdroiDx said:
if you can access download mode,one option is to connect the device to your PC and flash the stock firmware via odin. untick the Auto Reboot option. once you get a PASS, pull the battery, replace and immediately hit vol up + home + power button. when the device vibrates, release just the power button. in recovery, wipe data/factory reset, wipe cache. reboot.
first, can you boot into recovery at all?
Click to expand...
Click to collapse
First of all, thank you for your reply. I will definitely use your suggestion if that turns out to be my best option.
Secondly, it's funny you should ask about recovery. I have tried and tried to get into recovery, I have only been able to boot into it one time while it is on a charger, did not try anything because I thought that if I could get in it once I could get in it again, but since then no I have not...
UNTIL just now when you asked, I tried again and I am in TWRP. It is still in recovery at this moment, again only because I have it plugged in so I am open to your advice.

Well, since you're in recovery, I would consider wiping data/factory reset, wipe cache and dalvik, flash rom again and gapps. Reboot to see if that got you cleared up. This would mean you have to reset up your phone for the most part.
You could also consider wiping cache and dalvik, and flashing the rom and gapps. maybe this would correct your issue without wiping the device data.
Sou your device just did this? You weren't trying to flash a new kernel or anything?

moose0003 said:
First of all, thank you for your reply. I will definitely use your suggestion if that turns out to be my best option.
Secondly, it's funny you should ask about recovery. I have tried and tried to get into recovery, I have only been able to boot into it one time while it is on a charger, did not try anything because I thought that if I could get in it once I could get in it again, but since then no I have not...
UNTIL just now when you asked, I tried again and I am in TWRP. It is still in recovery at this moment, again only because I have it plugged in so I am open to your advice.
Click to expand...
Click to collapse
You have a few options at this point. You can access recovery and download mode so this is good. You can try and flash a new ROM through TWRP. You can also go into download mode and install a stock rom to start over. With TWRP choose a ROM of your choice (as long it is intended for your model). You could just restore a nandroid of one that you know worked...if you made any.

xBeerdroiDx said:
Well, since you're in recovery, I would consider wiping data/factory reset, wipe cache and dalvik, flash rom again and gapps. Reboot to see if that got you cleared up. This would mean you have to reset up your phone for the most part.
You could also consider wiping cache and dalvik, and flashing the rom and gapps. maybe this would correct your issue without wiping the device data.
Sou your device just did this? You weren't trying to flash a new kernel or anything?
Click to expand...
Click to collapse
Thanks again for your reply. I will try this and check back.
You are correct, it just did this, no kernel or anything. I will try wiping the device the data doesn't bother me. I won't lose much.
Have you or anyone else heard of this happening or know a cause? I could not find anything.
aybarrap1 said:
You have a few options at this point. You can access recovery and download mode so this is good. You can try and flash a new ROM through TWRP. You can also go into download mode and install a stock rom to start over. With TWRP choose a ROM of your choice (as long it is intended for your model). You could just restore a nandroid of one that you know worked...if you made any.
Click to expand...
Click to collapse
Thanks for your reply. I have a few backups. I will try stock first and see where that takes me and go from there.

Sorry about the delay. I was in recovery but I could not get it to recognize my SD card. So I took it out to try to load it in the computer and I'm having the worst time getting either of my computers to recognize either SD card I have even with 2 different readers. Still working on it though...

moose0003 said:
Sorry about the delay. I was in recovery but I could not get it to recognize my SD card. So I took it out to try to load it in the computer and I'm having the worst time getting either of my computers to recognize either SD card I have even with 2 different readers. Still working on it though...
Click to expand...
Click to collapse
Ouch sounds like your sd card is corrupted, you may not be able to get any info off it. You may have to use Odin to flash a stock ROM. You can still get to Download right?

metalsnakebite said:
Ouch sounds like your sd card is corrupted, you may not be able to get any info off it. You may have to use Odin to flash a stock ROM. You can still get to Download right?
Click to expand...
Click to collapse
Thanks for commenting. You were correct, my sd card was corrupted. Had my 4gb card that was working so I was able to determine that was the case.
Latest update
I was frustrated at the most recent attempt to load recovery, which I never succeeded in doing. I then decided to load a stock ROM from odin. Started this process, and it was going well until the reboot phase, which is what I was fearing the most.
Once it attempted the reboot, it attempted to reboot, then would just vibrate shortly over and over and over, with nothing on the screen.
Unplugged the device hoping for the best, yet nothing happened upon my attempts to power on.
Plugged back in and would initiate the same sequence in my original post, with the image of the battery, to the image of the SGS3 logo.
So...hoping for any good news someone has to offer, but have come to terms with the worst.
Again, appreciate any comments toward the struggles with my phone.

xBeerdroiDx said:
Well, since you're in recovery, I would consider wiping data/factory reset, wipe cache and dalvik, flash rom again and gapps. Reboot to see if that got you cleared up.......
Click to expand...
Click to collapse
Forgot to mention in my last post...I did the steps above while in recovery then I tried to reboot with nothing happening still. I did this before doing anything in ODIN.

moose0003 said:
Forgot to mention in my last post...I did the steps above while in recovery then I tried to reboot with nothing happening still. I did this before doing anything in ODIN.
Click to expand...
Click to collapse
after flashing stock via odin, you generally have to boot into stock recovery to wipe data/factory reset and wipe cache. reboot.

moose0003 said:
Thanks for commenting. You were correct, my sd card was corrupted. Had my 4gb card that was working so I was able to determine that was the case.
Latest update
I was frustrated at the most recent attempt to load recovery, which I never succeeded in doing. I then decided to load a stock ROM from odin. Started this process, and it was going well until the reboot phase, which is what I was fearing the most.
Once it attempted the reboot, it attempted to reboot, then would just vibrate shortly over and over and over, with nothing on the screen.
Unplugged the device hoping for the best, yet nothing happened upon my attempts to power on.
Plugged back in and would initiate the same sequence in my original post, with the image of the battery, to the image of the SGS3 logo.
So...hoping for any good news someone has to offer, but have come to terms with the worst.
Again, appreciate any comments toward the struggles with my phone.
Click to expand...
Click to collapse
Well usually after a fresh Stock Install using Odin you need to to go into the recovery and wipe data, cache/dalvic cache, factory reset. That should fix your problem.
Lol...beerdroid bro i didnt hit the next page you said what i just did.

metalsnakebite said:
Lol...beerdroid bro i didnt hit the next page you said what i just did.
Click to expand...
Click to collapse
haha. i've done that before. cheers, buddy.

xBeerdroiDx said:
after flashing stock via odin, you generally have to boot into stock recovery to wipe data/factory reset and wipe cache. reboot.
Click to expand...
Click to collapse
metalsnakebite said:
Well usually after a fresh Stock Install using Odin you need to to go into the recovery and wipe data, cache/dalvic cache, factory reset. That should fix your problem.
Lol...beerdroid bro i didnt hit the next page you said what i just did.
Click to expand...
Click to collapse
Thanks for the input guys. I'm having a difficult time to get it to stay into recovery now again. It acts like it wants to go in but it will just reboot. I will keep trying and if I need anymore help I will come back. Thanks so much again.

Back again. So I kept playing and was finally able to get into recovery as you guys suggested. Once I got in it finished the odin process and actually booted up! First time in a week. So ran through setup and then was able to determine that wifi is not working with stock ROM. Not sure if it's the phone or the ROM.
After it booted up and turned on was able actually do most functions, didn't test a lot wanted to see if it would work without being plugged in...this answer was no.
So after much testing I think what determines what will power it on and off is determined by what it is plugged into. I still think it is having hardware issues though because of the lack of powering on, but I am fairly certain that I can start it every time with a certain cable/charging dock.
I think the next thing I might try since I can get it to turn on is to root it again, load TriangleAway from an SD card, fix flash counter, unroot, load stock & see if they will warranty for hardware issues on the battery connection or whatever it is.
Haven't done this yet but will start tonight & have it finished by tomorrow is the plan. If anyone has any better suggestions I would gladly take them.

So this should be my last post unless a question arises for me.
moose0003 said:
.....I think the next thing I might try since I can get it to turn on is to root it again, load TriangleAway from an SD card, fix flash counter, unroot, load stock & see if they will warranty for hardware issues on the battery connection or whatever it is.....
Click to expand...
Click to collapse
This is what I said I was going to try to do. Took it to work and found time to do the above. TriangleAway worked a lot better than I ever thought it would. Flash counter reset, loaded unrooted stock and have a replacement on the way. Went very smoothly.
So doubt I will root & rom again until out of warranty. I appreciate everyone's help with my issue.
XDA is a great place.

[Q] Unresponsive Screen + Bootloop

I brought my phone in to have the charger port replaced. It worked fine ad then all of a sudden the phone boots up, stays booted for a minute and then reboots. also the screen is unresponsive.
I have used a gnex kit to get into CWM and erase cache and dalvik cache and fix permission and the problem is not resolved.
with out the gnex kit i can't even get into CWM and all i get is a little droid guy with an open stomach hatch with a red mark.
i would erase all data and factory reset as a last option but i have some work photos on the device that are extremely important for me to extract. I should also mention that with the CWM kit I am unable to find the files I wish to pull yet for the few seconds I am able to boot into android my photos are there in the album.
can someone please help me find a way to extract those files so I can try to wipe the device and move on?

cardozanick said:
I brought my phone in to have the charger port replaced. It worked fine ad then all of a sudden the phone boots up, stays booted for a minute and then reboots. also the screen is unresponsive.
I have used a gnex kit to get into CWM and erase cache and dalvik cache and fix permission and the problem is not resolved.
with out the gnex kit i can't even get into CWM and all i get is a little droid guy with an open stomach hatch with a red mark.
i would erase all data and factory reset as a last option but i have some work photos on the device that are extremely important for me to extract. I should also mention that with the CWM kit I am unable to find the files I wish to pull yet for the few seconds I am able to boot into android my photos are there in the album.
can someone please help me find a way to extract those files so I can try to wipe the device and move on?
Click to expand...
Click to collapse
With factory reset your sdcard will not be touched. You will have all your files (unless youre in stock recovery I think). You can use adb pull /sdcard/ to get all youre files.
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
With factory reset your sdcard will not be touched. You will have all your files (unless youre in stock recovery I think). You can use adb pull /sdcard/ to get all youre files.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
so what you're saying is if I boot into CWM with the kit, do a factory reset, all my photos will be there? can you please elaborate?

cardozanick said:
so what you're saying is if I boot into CWM with the kit, do a factory reset, all my photos will be there? can you please elaborate?
Click to expand...
Click to collapse
Yes that is correct. You can wipe everything as long as you dont wipe /sdcard. I am not a 100% sure since you are on stock but I know sure for 99%. Google is your friend
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
Yes that is correct. You can wipe everything as long as you dont wipe /sdcard. I am not a 100% sure since you are on stock but I know sure for 99%. Google is your friend
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Alright,
alright, we have 50% success!
I was able to get all the files off that I was looking to get, albeit during 20 second intervals in which the phone would allow me to before rebooting....
which brings me to my next point - Phone is stuck in bootloop after following (successfully) this guide to flash stock and unroot which, needless to say, seems strange to me.
Now I supposedly have a fully formatted i9250 maguro with a fresh flash of stock running and i'm stuck in a boot loop which if i leave sitting long enough will eventually get to the "Welcome" [choose your language] screen with an unresponsive display panel until it reboots after about 30 seconds.
please help.
EDIT: I flashed the Factory Image Android 4.2.2 (JDQ39) and still stuck in bootloop with unresponsive screen. maybe this is better as a paperweight??

cardozanick said:
Alright,
alright, we have 50% success!
I was able to get all the files off that I was looking to get, albeit during 20 second intervals in which the phone would allow me to before rebooting....
which brings me to my next point - Phone is stuck in bootloop after following (successfully) this guide to flash stock and unroot which, needless to say, seems strange to me.
Now I supposedly have a fully formatted i9250 maguro with a fresh flash of stock running and i'm stuck in a boot loop which if i leave sitting long enough will eventually get to the "Welcome" [choose your language] screen with an unresponsive display panel until it reboots after about 30 seconds.
please help.
EDIT: I flashed the Factory Image Android 4.2.2 (JDQ39) and still stuck in bootloop with unresponsive screen. maybe this is better as a paperweight??
Click to expand...
Click to collapse
Thats strange. But you have your files and you are on completely stock unrooted. If you still have warranty you can send it back. Maybe you can try this: http://xda-university.com/as-a-user/how-to-recover-from-a-bootloop
Sent from my Galaxy Nexus using XDA Premium HD app

Strange Fix reveals deeper issue
good news and bad news
Alright, so I have swapped the motherboard with an old gnex i had laying around that has a broken screen that wouldn't turn on at all..
I found out that the motherboard on the old phone must be dead because it won't work in the newer phone so I put the guts of the newer on into the broken screen phone and it worked perfectly - albeit with a huge crack in it. so i then thought maybe the issue was solved and put the guts that worked back into the original phone and it is unresponsive and reboots... I've come to the conclusion that the screen is the issue on that device.
but is this fixable??? i have taken the whole thing apart and can't see how that screen could be shorting the device and cause it to reboot nor can i understand why it wouldn't be responsive to the touch for no reason.
anybody have a clue how i can fix that?

(help) Bootloop and partitions read only

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)