Yet another bricked A100 - Need to restore locked bootloader - Acer Iconia Tab A100

So, I'm on vacation last week, watching a movie on my tablet when it starts to become very laggy. After a minute or two, it locks up completely. Just like everyone else, I reboot it to find that it doesn't get any farther that the green Acer logo. I was running CWM recovery, but nothing seems to work... every command gives me an error. After reading this thread by NighPlayer32: http://forum.xda-developers.com/showthread.php?t=1749967 I switch to TWRP recovery and am able to push an update.zip to the internal sdcard, but still can't install it because none of my partitions will mount.
At this point, I've given up on getting this thing to work. I can get into fastboot and recovery, but beyond that I've had no luck and I'm guessing it's fault hardware (EMMC?). It was purchased in December, so it should be under warranty but it has a unlocked bootloader, which will cause some problems if I send it to Acer. Does anyone know of a way to restore it to a stock bootloader via fastboot or recovery? OR... has anyone with missing partitions been able to load an update.zip successfully?
Any help would be GREATLY appreciated!
Thanks in advance!

ED2O9 said:
So, I'm on vacation last week, watching a movie on my tablet when it starts to become very laggy. After a minute or two, it locks up completely. Just like everyone else, I reboot it to find that it doesn't get any farther that the green Acer logo. I was running CWM recovery, but nothing seems to work... every command gives me an error. After reading this thread by NighPlayer32: http://forum.xda-developers.com/showthread.php?t=1749967 I switch to TWRP recovery and am able to push an update.zip to the internal sdcard, but still can't install it because none of my partitions will mount.
At this point, I've given up on getting this thing to work. I can get into fastboot and recovery, but beyond that I've had no luck and I'm guessing it's fault hardware (EMMC?). It was purchased in December, so it should be under warranty but it has a unlocked bootloader, which will cause some problems if I send it to Acer. Does anyone know of a way to restore it to a stock bootloader via fastboot or recovery? OR... has anyone with missing partitions been able to load an update.zip successfully?
Any help would be GREATLY appreciated!
Thanks in advance!
Click to expand...
Click to collapse
Sorry to hear another one died. We've attempted a few methods but none have so far worked. If you can still push to internal SD you can try to push the a100 boot loader in recovery via adb but you'll lose cwm and fast boot so it will still go back with a custom recovery. There is a stock recovery image around which can also be flashed in recovery via abd which should put it back to normal aside from any custom ROM you may be running. If you're interested I'll try to find the stuff for you and setup some instructions. It'll be tomorrow though I'm about to head to bed.
Tapatalked from my A100 - CM10

I'm scared
How can I prevent my own a100's death
Sent from my LG-P500 using xda premium

-DarkKnight- said:
I'm scared
How can I prevent my own a100's death
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Hardbricks you can't , its faulty emmc, you either have it or you don't.
Tapatalked from my A100 - CM10

-DarkKnight- said:
I'm scared
How can I prevent my own a100's death
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
me too lol, i just have rooted my tab but i preffer to not touching the bootloader.
---------- Post added at 05:19 PM ---------- Previous post was at 05:17 PM ----------
pio_masaki said:
Hardbricks you can't , its faulty emmc, you either have it or you don't.
Tapatalked from my A100 - CM10
Click to expand...
Click to collapse
hey pio! sorry but my english is a lil short, i dont understand that part, what do u mean?

pio_masaki said:
If you're interested I'll try to find the stuff for you and setup some instructions.
Click to expand...
Click to collapse
Thanks! Like I said, I've tried everything to get a ROM to load and all I get is "can't mount" failures, so I'm assuming that it need to go back to Acer. If you could give me any tips to restore it to the stock bootloader, I'd really appreciate it. There was a thread I found that had a link to a LOCKED bootloader restore script, but the link was dead.

Deshabilitado said:
me too lol, i just have rooted my tab but i preffer to not touching the bootloader.
---------- Post added at 05:19 PM ---------- Previous post was at 05:17 PM ----------
hey pio! sorry but my english is a lil short, i dont understand that part, what do u mean?
Click to expand...
Click to collapse
emmc is the part of the device where the storage is, everything from recovery, bootloader, system, data, internal sd, etc, are all on this chip, if it's damaged or faulty, you can't use that portion of the the memory. The first sign of it failing generally seems to be laggy, slow running, followed by a freeze. Then you are forced to hard reboot, and then you have problems of any partitions mounting.
@ED209 - I'll see if I have some time to hunt this stuff down, although the script pack that zeronull has for unlocking the bootloader also has the a100 and a revert script to restore the stock locked bootloader. The script may or may not work in recovery as it was meant to run from android, but it should be easy enough to either adapt to recovery, or just manually issue the commands over adb in recovery. The PC side will push the bootloader.blob and the script for the tablet side, then run the script on the tablet which will do the bootloader flash, then reboot, however we don't want it to reboot until you have stock recovery or you get locked out.

I know that flashing update.zip fails due to corrupt or missing partitions, but do you think restoring a backup package might work? I guess I'd need a stock backup image, push it to the internal sdcard and just try to run a restore from TWRP. I have a feeling it won't get any farther than the update.zip, but at this point I'll try anything. Do you remember ever seeming if someone posted a link to a stock restore .img?
Beyond that, is it possible to recreate the partitions through ADB?
Thanks again...

ED2O9 said:
I know that flashing update.zip fails due to corrupt or missing partitions, but do you think restoring a backup package might work? I guess I'd need a stock backup image, push it to the internal sdcard and just try to run a restore from TWRP. I have a feeling it won't get any farther than the update.zip, but at this point I'll try anything. Do you remember ever seeming if someone posted a link to a stock restore .img?
Beyond that, is it possible to recreate the partitions through ADB?
Thanks again...
Click to expand...
Click to collapse
There is parted in custom recovery which would in theory work, but its never been attempted before. I'm supposedly getting a brick sent to me (not 100% if it will happen or not) and it's one of the many things I plan to try.
Flashing and restoring will fail since the partitions can't be accessed.
A restore image will fail for the same reason.
I have tons of ideas but until I get ahold of a brick its all purely theory and speculation and until I'm sitting there looking at it I can't figure out how to do it, its weird I know but I can't just bust out what I want to do, I have to be doing it.....
Tapatalked from my A100 - CM10

I suggest you erase all evidence of it being rooted/modded then your warrenty is ok
Do you have a method to check if it is there so i can pretend to wipe everything and brick it, while pretending it wasn't my fault while my warrenty is still here?

-DarkKnight- said:
I suggest you erase all evidence of it being rooted/modded then your warrenty is ok
Do you have a method to check if it is there so i can pretend to wipe everything and brick it, while pretending it wasn't my fault while my warrenty is still here?
Click to expand...
Click to collapse
A pretend wipe is obvious. And what you just suggested isn't exactly honorable, returning an item as broken when its not. And wiping isn't bricking, during my time making the black hole tools I soft bricked at least 20 times, full out wrecked corrupted effed up partitions, always came back. You can't invoke this brick, you have it or you don't.
As for wiping it clean of mods, that is what we were discussing in this thread already. Its also kinda shady as the warranty expires when you root and again when you unlock, and yet again with the custom recovery and also the custom ROM. However it is a straight hardware failure, an issue Acer knows of. I would suggest calling or maybe chatting on their site, I'm pretty sure another brick victim is getting a replacement even rooted and unlocked.
As for checking, no I don't know of a way. The brick thread had aimed to condense all known information to try to isolate it to any build dates or anything specific, but not enough information was provided to do it. For awhile I thought cm9 was safe, but recently a brick occurred on cm9 as well.
I would advise your next step be to visit the Acer site, try to chat with a rep and ask about the hardware failure and your options with it rooted. You may get the same deal the other user did and just pay shipping.
Tapatalked from my A100 - CM10

I wouldn't send it in under warranty coverage if I felt that the issue was due to improper modifications that I made to the device. I'm typically pretty meticulous about following directions, and I was running the stock ROM. I had unlocked the bootloader and added CWM for back-up purposes (which I never got around to because I needed to make space on my SD card), and the lock-up occurred when I was watching a video clip I recorded that afternoon. Based on the severity of the "brick", I'm fairly certain that it's a hardware issue. I'm hearing people mention $150 repair bills, and I'd hate to pitch this tablet because of a EMMC failure, which appears to be increasingly common on this device.

ED2O9 said:
I wouldn't send it in under warranty coverage if I felt that the issue was due to improper modifications that I made to the device. I'm typically pretty meticulous about following directions, and I was running the stock ROM. I had unlocked the bootloader and added CWM for back-up purposes (which I never got around to because I needed to make space on my SD card), and the lock-up occurred when I was watching a video clip I recorded that afternoon. Based on the severity of the "brick", I'm fairly certain that it's a hardware issue. I'm hearing people mention $150 repair bills, and I'd hate to pitch this tablet because of a EMMC failure, which appears to be increasingly common on this device.
Click to expand...
Click to collapse
That wasn't aimed at you, no worries. I still suggest you go chat with Acer on their site, calling charges you, and see what they say about the tablet in its current state.
Tapatalked from my A100 - CM10

ED2O9 said:
I wouldn't send it in under warranty coverage if I felt that the issue was due to improper modifications that I made to the device. I'm typically pretty meticulous about following directions, and I was running the stock ROM. I had unlocked the bootloader and added CWM for back-up purposes (which I never got around to because I needed to make space on my SD card), and the lock-up occurred when I was watching a video clip I recorded that afternoon. Based on the severity of the "brick", I'm fairly certain that it's a hardware issue. I'm hearing people mention $150 repair bills, and I'd hate to pitch this tablet because of a EMMC failure, which appears to be increasingly common on this device.
Click to expand...
Click to collapse
Well 150 is less than the original price
And pio said its the hardware fault its either broken or not broken so modding wouldn't do anything
Sent from my LG-P500 using xda premium

fastboot oem unlock?

droc.noles said:
fastboot oem unlock?
Click to expand...
Click to collapse
What does that have to do with anything in this thread?
Tapatalked from my Galaxy S II - CM10

Probably trolling
Sent from my Full AOSP on a100 using XDA Premium HD app

pio_masaki said:
What does that have to do with anything in this thread?
Tapatalked from my Galaxy S II - CM10
Click to expand...
Click to collapse
Misinterpreted what OP was trying to get done, don't mind me.
I had an issue where I was locked out due to ignorantly running the revert to locked bootloader script. Boot verified failed, recovery verified failed. fastboot oem unlock got me back to the toggle between lock and unlock. My apologies, carry on.

droc.noles said:
Misinterpreted what OP was trying to get done, don't mind me.
I had an issue where I was locked out due to ignorantly running the revert to locked bootloader script. Boot verified failed, verified failed. fastboot oem unlock got me back to the toggle between lock and unlock. My apologies, carry on.
Click to expand...
Click to collapse
Ah ok. And glad you got that squared away, that info may be useful should that occur again.
Tapatalked from my A100 - CM10

pio_masaki said:
That wasn't aimed at you, no worries. I still suggest you go chat with Acer on their site, calling charges you, and see what they say about the tablet in its current state.
Tapatalked from my A100 - CM10
Click to expand...
Click to collapse
In looking back over the brick threads, I realized that you are the member that posted the scripts to return the tablet to a locked bootloader. The link is dead, so I was wondering if you could repost it.
Thanks!

Related

[Q] Possible brick? Any ideas?

Hey guys, I think I screwed up here and I'm wondering if anyone else has had this problem:
Basically, I had a rooted E4G Touch with a custom ROM installed. I went to install ANOTHER custom ROM THROUGH ODIN, as this previous ROM (I believe it was a Calkulin variant) did NOT have CWM recovery. During the ODIN process, something went wrong, and my computer/ODIN...basically, everything froze up while doing the MODEM portion. NOW I can't do anything.
- CWM was able to install on the thing...but it does not recognize my external SD card now. Every time I try to mount it, I get a "Error mounting /emmc".
- I'm still able to get into download mode on the phone, however the phone is not recognized on any computer I've tried. I've attempted multiple computers/USB cords and nothing picks it up.
I'm running out of ideas here. I picked up a USB jig that should be here soon, so I'm going to try that and reset the counter....which leads me to my next question: If I use that, can I take the thing back to Sprint and get a replacement? I have the insurance plan and everything, so if they won't take it back because of the custom software I guess I could always smash it or something...
Any help would be appreciated!
munson11 said:
Hey guys, I think I screwed up here and I'm wondering if anyone else has had this problem:
Basically, I had a rooted E4G Touch with a custom ROM installed. I went to install ANOTHER custom ROM THROUGH ODIN, as this previous ROM (I believe it was a Calkulin variant) did NOT have CWM recovery. During the ODIN process, something went wrong, and my computer/ODIN...basically, everything froze up while doing the MODEM portion. NOW I can't do anything.
- CWM was able to install on the thing...but it does not recognize my external SD card now. Every time I try to mount it, I get a "Error mounting /emmc".
- I'm still able to get into download mode on the phone, however the phone is not recognized on any computer I've tried. I've attempted multiple computers/USB cords and nothing picks it up.
I'm running out of ideas here. I picked up a USB jig that should be here soon, so I'm going to try that and reset the counter....which leads me to my next question: If I use that, can I take the thing back to Sprint and get a replacement? I have the insurance plan and everything, so if they won't take it back because of the custom software I guess I could always smash it or something...
Any help would be appreciated!
Click to expand...
Click to collapse
The ROM you flashed through ODIN was for this phone, right?
What custom ROM are you referring to that was available through ODIN?
assuming you flashed the right ROM, start with the basics..if you can get into download mode then try a simple reboot of your computer. Sometimes Odin won't recognize after it has been run
Sent from my SPH-D710 using xda premium
barnacles10 said:
The ROM you flashed through ODIN was for this phone, right?
What custom ROM are you referring to that was available through ODIN?
Click to expand...
Click to collapse
It was the CyanogenMod 9 rom that is out there right now. IN the post (I'm having trouble finding it as I'm not at that computer right now) they had an ODIN variation for people such as myself, where you were to flash that and then go back through to update it to the latest version.
JohnCorleone said:
assuming you flashed the right ROM, start with the basics..if you can get into download mode then try a simple reboot of your computer. Sometimes Odin won't recognize after it has been run
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I attempted this as well Went through and rebooted the computer with the phone plugged in. Rebooted with it not plugged in. Plugged the phone in with ODIN on the screen and started it up. Started it up unplugged, went into download mode on the phone, and then plugged it in. Still nothing.
And I just realized I posted this in General and not Q&A...and chance I could get this moved since I am clearly out of my mind right now?
munson11 said:
It was the CyanogenMod 9 rom that is out there right now. IN the post (I'm having trouble finding it as I'm not at that computer right now) they had an ODIN variation for people such as myself, where you were to flash that and then go back through to update it to the latest version.
Click to expand...
Click to collapse
The only odin component involved with flashing CM9 is flashing a gb kernel with a CWM recovery. I haven't seen a cm9 tar, this is why I'm confused. Finding out exactly what you flashed will help in understanding what the problem is.
To flash cm9 you need to odin a gb cwm kernel and then boot to recovery and install cm9. However, that's not a tar, its an update.zip.
barnacles10 said:
The only odin component involved with flashing CM9 is flashing a gb kernel with a CWM recovery. I haven't seen a cm9 tar, this is why I'm confused. Finding out exactly what you flashed will help in understanding what the problem is.
To flash cm9 you need to odin a gb cwm kernel and then boot to recovery and install cm9. However, that's not a tar, its an update.zip.
Click to expand...
Click to collapse
Yeah it was definitely a tar.md5 file, which leads me to believe I was incredibly dumb and possibly flashed a ROM for a different model phone. I'm having difficulty finding the post now which is very strange. This could be one of those moments where I take a good hard look in the mirror and figure out just what the heck I was thinking.
I'll keep looking for what exactly I did wrong, but in the mean time is there anything else I could attempt or look for short of attempting that USB jig and making a trip to Sprint? I'm feeling like a huge idiot right now. I've done this how many times now and when I finally make a mistake, it turns out to be huge.
munson11 said:
It was the CyanogenMod 9 rom that is out there right now. IN the post (I'm having trouble finding it as I'm not at that computer right now) they had an ODIN variation for people such as myself, where you were to flash that and then go back through to update it to the latest version.
I attempted this as well Went through and rebooted the computer with the phone plugged in. Rebooted with it not plugged in. Plugged the phone in with ODIN on the screen and started it up. Started it up unplugged, went into download mode on the phone, and then plugged it in. Still nothing.
And I just realized I posted this in General and not Q&A...and chance I could get this moved since I am clearly out of my mind right now?
Click to expand...
Click to collapse
Maybe you should post the link to exactly what you were flashing...
http://www.addictivetips.com/mobile/cyanogenmod-9-galaxy-s-ii-download/
Please tell me this isnt what you flashed.
Sent from my SPH-D710 using xda premium
munson11 said:
Yeah it was definitely a tar.md5 file, which leads me to believe I was incredibly dumb and possibly flashed a ROM for a different model phone. I'm having difficulty finding the post now which is very strange. This could be one of those moments where I take a good hard look in the mirror and figure out just what the heck I was thinking.
I'll keep looking for what exactly I did wrong, but in the mean time is there anything else I could attempt or look for short of attempting that USB jig and making a trip to Sprint? I'm feeling like a huge idiot right now. I've done this how many times now and when I finally make a mistake, it turns out to be huge.
Click to expand...
Click to collapse
Well ultimately you can try uninstalling / reinstalling drivers. But you say this issue exists across multiple pcs so that likely isn't it.
You can try another cable and see if you have any success with that.
Other then that, it kinda really depends what is in that tar you flashed. Once you find it, post the link, and that will help troubleshoot your issue.
playya said:
Maybe you should post the link to exactly what you were flashing...
Click to expand...
Click to collapse
lballer69 said:
http://www.addictivetips.com/mobile/cyanogenmod-9-galaxy-s-ii-download/
Please tell me this isnt what you flashed.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Haha I am a freaking idiot. How in the heck did I manage to do this...I definitely flashed this: http://forum.xda-developers.com/showthread.php?t=1419102
I do not know what was going through my head last night...but it was not any sort of smart thoughts. A rope and a sturdy tree are what I require at this point, correct?
Whatever insults you guys would like to throw at me, I will take. I clearly deserve them :'(
munson11 said:
Haha I am a freaking idiot. How in the heck did I manage to do this...I definitely flashed this: http://forum.xda-developers.com/showthread.php?t=1419102
I do not know what was going through my head last night...but it was not any sort of smart thoughts. A rope and a sturdy tree are what I require at this point, correct?
Whatever insults you guys would like to throw at me, I will take. I clearly deserve them :'(
Click to expand...
Click to collapse
Did you flash the bootloader from that device? ie did your steps include this? \/
Make sure you're running ICS bootloaders lower than LPH: Download (flash as PDA with odin or extract and $ sudo heimdall flash --primary-boot boot.bin --secondary-boot Sbl.bin)
Click to expand...
Click to collapse
barnacles10 said:
Did you flash the bootloader from that device? ie did your steps include this? \/
Click to expand...
Click to collapse
Negative, I started right at the "Using the noob-proof ODIN method:". It said noob-proof and I decided that would be the easiest. It turns out it is very easy...if you're flashing to the correct phone Plus, I'd used ODIN before and felt comfortable with it.
Ha ha that's the first one for this method......look up jtag they may fix it for u if u don't have USB .... About 60 with shipping
Sent from my SPH-D710 using Tapatalk 2 Beta-5
munson11 said:
Negative, I started right at the "Using the noob-proof ODIN method:". It said noob-proof and I decided that would be the easiest. It turns out it is very easy...if you're flashing to the correct phone Plus, I'd used ODIN before and felt comfortable with it.
Click to expand...
Click to collapse
I just downloaded the tar to have a look at whats included.
After flashing this you'll have a bootloader for the intl. sgs2. This is a problem many ran into when original SGS2 leaked tars started surfacing as well.
JTAG might be able to fix it, I'm not sure whether people with this issue were successful or not with JTAG repair as the intl gs2 flashing boat seems to have sailed now. However, a jig will likely do nothing, unfortunately.
barnacles10 said:
I just downloaded the tar to have a look at whats included.
After flashing this you'll have a bootloader for the intl. sgs2. This is a problem many ran into when original SGS2 leaked tars started surfacing as well.
JTAG might be able to fix it, I'm not sure whether people with this issue were successful or not with JTAG repair as the intl gs2 flashing boat seems to have sailed now. However, a jig will likely do nothing, unfortunately.
Click to expand...
Click to collapse
Ok thank you for your help on this. You don't think a jig will reset the counter or anything so that I can take it back to Sprint? If not, I'm not above "dropping" it on the ground and using the insurance I have on it for a replacement.
munson11 said:
Ok thank you for your help on this. You don't think a jig will reset the counter or anything so that I can take it back to Sprint? If not, I'm not above "dropping" it on the ground and using the insurance I have on it for a replacement.
Click to expand...
Click to collapse
I don't foresee it working only because your phone isn't recognized by your pc and the problem doesnt lie on the pc side.
The problem is instead with the port on the phone which leads me to believe it won't recognize a jig either.
A jtag if successful will leave you with more money in your pocket and a non-returb. Something to consider if you've got a backup phone you can use for a few days.
barnacles10 said:
I don't foresee it working only because your phone isn't recognized by your pc and the problem doesnt lie on the pc side.
The problem is instead with the port on the phone which leads me to believe it won't recognize a jig either.
A jtag if successful will leave you with more money in your pocket and a non-returb. Something to consider if you've got a backup phone you can use for a few days.
Click to expand...
Click to collapse
I don't see sprint replacing it with cm9 On it .... And u will need mobile Odin to get back to stock but with it not mounting the Emmc probably can't do that .... That is your hope to get back to stock using mobile Odin someway .... Triangle away app will reset Odin count but with no radio you need to get apps to do it and no sd from what u said ...maybe tell insurance u lost it and get it replaced
Jtag should work also since there is no emmc failure like the blue light of death bricks ...
Sent from my SPH-D710 using Tapatalk 2 Beta-5

Sudden Boot Loops - I'm Lost

I've been using my Galaxy Nexus for a month or so, with the official JB ROM (JR30C or whatever, deodexed and rooted) and today I opened Gmail.
That's it. I opened GMail, switched accounts, and my phone has been bootlooping ever since.
I wiped everything in CWM multiple times and reflashed it, and I can't get the phone to do anything else.
Any clues?
Do you have a working nandroid? Have you tried flashing a different ROM?
Allons-y
Xfanatic said:
Do you have a working nandroid? Have you tried flashing a different ROM?
Allons-y
Click to expand...
Click to collapse
I do not have a working NANDROID. I wasn't sure about the Internet policies at work, but it looks like I can at least make it on here, I'm not sure I'll be able to download another ROM.
I'm confused though, I mean I know it would help to try as many options as possible (to fix it) - but this ROM has been working for weeks. And the phone died randomly, not due to a recent file change or a botched program. The only boot loops I've experienced before were on the Nexus One, and it was always due to a buggy/bad flash or a corrupted ROM download - this one just developed epilepsy on its own...
Here's my plan, since these are the only things I can manage to download due to restrictions on Internet usage at work.
Factory 4.1.1 takju image from here : https://developers.google.com/android/nexus/images#takju
Modified ODIN software here: http://forum.xda-developers.com/showthread.php?t=1586807
ODIN won't rewrite my bootloader, recovery, or userdata, since I already OEM unlocked, but will reflash a stock image.
EDIT: ODIN won't do anything with my device. Trying this ROM instead:
http://forum.xda-developers.com/showthread.php?t=1801664 was using bigxie OTA before.
is your (sd)storage recognized? thus is a similar symptom to when the stirage goes bad.
Hook the phone up to adb, boot it, and let logcat run. Maybe that will turn something up.
Sent from my Galaxy Nexus using Tapatalk 2
simms22 said:
is your (sd)storage recognized? thus is a similar symptom to when the stirage goes bad.
Click to expand...
Click to collapse
Hmm, you know, I'm not able to find the option to mount to USB in CWM...and just in case I forgot where that is, when I plug it in, I get the "hardware failed" noise from Windows and not the usual friendly "plug in" sound.
infazzdar said:
Hook the phone up to adb, boot it, and let logcat run. Maybe that will turn something up.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'm at work, and I only have my work computer. Group/secpolicy won't allow me to install anything, no admin rights, etc.
Would it even do anything? The phone barely makes it through one second of the boot animation before it loops.
sheik124 said:
Hmm, you know, I'm not able to find the option to mount to USB in CWM...and just in case I forgot where that is, when I plug it in, I get the "hardware failed" noise from Windows and not the usual friendly "plug in" sound.
Click to expand...
Click to collapse
you cant mount the sd card. there is no USB mass storage period. not in recovery or booted normally.
Zepius said:
you cant mount the sd card. there is no USB mass storage period. not in recovery or booted normally.
Click to expand...
Click to collapse
Oy. Then how do I get another ROM on here? fastboot/adb?
sheik124 said:
Oy. Then how do I get another ROM on here? fastboot/adb?
Click to expand...
Click to collapse
Adb push.
Sent from my Galaxy Nexus using Tapatalk 2
Zepius said:
you cant mount the sd card. there is no USB mass storage period. not in recovery or booted normally.
Click to expand...
Click to collapse
sheik124 said:
Oy. Then how do I get another ROM on here? fastboot/adb?
Click to expand...
Click to collapse
Got more than one additional ROM on there via adb/recovery - my clue that CWM hasn't actually been able to do anything since the phone start looping is I'm still getting my custom boot animation.
I'm using the toolkit to reflash a stock image now. What a mess.
Even reflashing a stock image via fastboot did nothing. WTF happened to my phone? Won't stay on long enough to get a logcat
I'm having the same problem as this guy:
http://forum.xda-developers.com/showthread.php?t=1827685&page=2
I just got finished trying to flash 4.1.1 using ODIN. It still shows me the custom animation from bigxie's ROM (which has supposedly since been overwritten 2-4x times).
Screw you Samsung...this phone is a month old, I flashed -once- to rooted Jelly Bean, and the phone dies when I open the GMail app.
EDIT: WTF - I write screw you Samsung, it boots to the Welcome screen! Just long enough for me to see that my files aren't on it anymore, then it bootloops again. And again. Now it's re-stuck in a bootloop.
And now I'm at the homescreen. I can't rely on this thing like this...is my flash dying or something?
Nobody?
It worked long enough for me to re-enter all of my different Google account information and now it's dead again. Now it only flashes the boot animation for a split second for bootlooping.
I'm thinking of a hardware defect.
Beamed from my Grouper
Mach3.2 said:
I'm thinking of a hardware defect.
Beamed from my Grouper
Click to expand...
Click to collapse
Mee too. As you can see from my signature, I gave up and bought a One S yesterday night from Craigslist. Feels like a true successor to the Desire / N1. It's nice to finally have an AMOLED screen that actually seems color calibrated after the ugly mess that was my RAZR and my less than perfect GNex. It's a damn shame how much more painless flashing a recovery was on this thing.
Sent from my HTC VLE_U using xda app-developers app

For all the flashers here for the T989

The whole process is pretty simple on what I have done. I will explain my situation here and my question that has got be baffled.
So it all started about two weeks ago, where I was flashing LiquidSmooth on my phone. I had a Touch-type CWM. It isn't mega old but it's pretty old for CWM, I haven't updated in a while (as i've seen there are updates to recent ones).
Anywho, I did a complete wipe, used the darkside wipe, alongside with the darkside cache wipe.
I think this was my fault, so please correct me anyone if I am wrong here. I accidentally hit "reboot phone" instead of "reboot bootloader"
I got a permabrick from this whole ordeal. It was a permabrick because It said QHSUSB_DLOAD in the device manager, looking this up further confirmed my reasoning. I didn't want to jtag because that invovles removing the phone to pieces and soldering on wires etc. etc.
So I resorted to send it out to Samsung.
All is well when it came back. I made sure this time the whole phone was setup properly.
So I use Odin install for CWM and SU was installed via CWM. I install an older version of CWM (non-touch, i believe 1st revision as i've posted in one of the threads).
I kept stock ROM, everything was working okay and suddenly, KERPLUNK, it went back into permanent brick after I deleted cache partition, dalvik cache, and battery cache wipe. I didn't do fix permissions or anything, just hit reboot afterwards.
This is a super head scratcher here..... Anyone know where I went wrong?
Any insight here is greatly appreciated! :good:
P.S. I am now sending in my phone TWICE to Samsung for repairs.
If you are on the most up to date CWM, do not use the scripts. They are no longer needed, and will cause problems( hard brick though, never heard of) The second time, im stumped. I suggest go to TWRP and ditch the scripts. Latest TWRP does not need it
LoopDoGG79 said:
If you are on the most up to date CWM, do not use the scripts. They are no longer needed, and will cause problems( hard brick though, never heard of) The second time, im stumped. I suggest go to TWRP and ditch the scripts. Latest TWRP does not need it
Click to expand...
Click to collapse
I finally jumped in the water and flashed twrp! Yay!
Sent from my SAMSUNG-SGH-T989 using xda premium
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
rymanh said:
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
great call on that I had to educate a few users that the d2tmo is not for our phone but indeed the S3. Good catch on your part and it sounds like user error as well
LoopDoGG79 said:
If you are on the most up to date CWM, do not use the scripts. They are no longer needed, and will cause problems( hard brick though, never heard of) The second time, im stumped. I suggest go to TWRP and ditch the scripts. Latest TWRP does not need it
Click to expand...
Click to collapse
Could you please educate me with a link referring to what TWRP is? Sorry, i'm still fairly new to the scene and all i've ever been educated upon is CWM.
suaverc118 said:
I finally jumped in the water and flashed twrp! Yay!
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Nice! What is TWRP and how is it like?
rymanh said:
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I've flashed the hercules ROM. I know this for sure because Liquidsmooth was working, it was extremely glitchy (playing games gave me pixelated actions sometimes, and using something like gameCIH/Game Guardian was unworkable). So i decided to ditch it and was getting ready to flash Jedi Mind Trick.
After the whole hard bricking ordeal, I decided to stick to stock rom, and even on that, I just flashed CWM and SU ONLY. Rebooted, and deleted the cache's (like i've posted to you) with absolutely no success. It baffled me that I bricked the phone AGAIN too!
playya said:
great call on that I had to educate a few users that the d2tmo is not for our phone but indeed the S3. Good catch on your part and it sounds like user error as well
Click to expand...
Click to collapse
Yes..... there is something wrong, i feel it is a user error also, but i'm very unsure where to even start
Once again, all of your insight is well appreciated! I just do not want to hardbrick my phone AGAIN and have to send it to Samsung. I am not allowed to even think of a replacement because this was a b-day present a year or two ago from my fiance.
You say that it is bricked again. Do you mean by that, that you cannot get into recovery?
Sent from my SAMSUNG-SGH-T989 using xda premium
XxGoKoUxX said:
Could you please educate me with a link referring to what TWRP is? Sorry, i'm still fairly new to the scene and all i've ever been educated upon is CWM.
Nice! What is TWRP and how is it like?
I've flashed the hercules ROM. I know this for sure because Liquidsmooth was working, it was extremely glitchy (playing games gave me pixelated actions sometimes, and using something like gameCIH/Game Guardian was unworkable). So i decided to ditch it and was getting ready to flash Jedi Mind Trick.
After the whole hard bricking ordeal, I decided to stick to stock rom, and even on that, I just flashed CWM and SU ONLY. Rebooted, and deleted the cache's (like i've posted to you) with absolutely no success. It baffled me that I bricked the phone AGAIN too!
Yes..... there is something wrong, i feel it is a user error also, but i'm very unsure where to even start
Once again, all of your insight is well appreciated! I just do not want to hardbrick my phone AGAIN and have to send it to Samsung. I am not allowed to even think of a replacement because this was a b-day present a year or two ago from my fiance.
Click to expand...
Click to collapse
Flash this in recovery, reboot recovery, and you will have TWRP!!
TWRP 2.3.1.1
DM_Sledge said:
You say that it is bricked again. Do you mean by that, that you cannot get into recovery?
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Yes, it is perma-bricked, meaning the only method of fixing the brick is jtagg'ing
Upon plugging it into device manager, I get the prompt "QHSUSB_DLOAD" and phone doesn't even boot on no matter what combinations I make.
LoopDoGG79 said:
Flash this in recovery, reboot recovery, and you will have TWRP!!
TWRP 2.3.1.1
Click to expand...
Click to collapse
Thank you LoopDo, I will do this after I get my phone home again.
I have this phone, and none of the steps you listed would brick the device. Even with no ROM on the phone, you should still be able to get into recovery.
Is there something you aren't telling us?
Sent from my Galaxy Nexus using xda premium
Nope, wouldn't be a reason why I would lie because then the problem will never be resolved.... I'm kind of nervous on reflashing ONE more time after the phone comes home again....
The phone has been fixed once AGAIN, and it is in the process of being shipped back to me.
Phone will be home Wednesday and I will give it ONE more try
Wish me luck!
P.S. my PC has been glitchy lately, so that MAY or MAY NOT contribute to the permabrick, then again the brick doesn't happen until I flash stuff via CWM.
P.S.S. I've since re-installed Win 7 again, it hasn't been glitchy since
XxGoKoUxX said:
Nope, wouldn't be a reason why I would lie because then the problem will never be resolved.... I'm kind of nervous on reflashing ONE more time after the phone comes home again....
The phone has been fixed once AGAIN, and it is in the process of being shipped back to me.
Phone will be home Wednesday and I will give it ONE more try
Wish me luck!
P.S. my PC has been glitchy lately, so that MAY or MAY NOT contribute to the permabrick, then again the brick doesn't happen until I flash stuff via CWM.
P.S.S. I've since re-installed Win 7 again, it hasn't been glitchy since
Click to expand...
Click to collapse
You most likely flashed the Wrong Liquidsmooth ROM (incompatible Kernel), and it hard bricked the phone. It happened to me the same way, and I had to send it in for JTAG.
I have bricked my phone installing the Liquidsmooth ROM too. I downloaded the wrong ROM, though. The thread should have a big ****in warning to double check the ROM you are about to download, otherwise your phone is a toast. There were more people who bricked their phones by installing the Liquidsmooth.
Well, I got it back from the warranty and the phone looks good. Installed that Liquidsmooth again and played for a day. Tried other JB ROMs. Most of them are OK in terms of battery life and smoothness, but there is something wrong with the signal. People always say my voice isn't clear. I got tired of all this BS and testing new ROMs and went to back to ICS and won't look back, not anytime.
Don't use darkside scripts, btw. You don't need that anymore.
I'd like to say thank you for everyone's patience. All of your insight is more than helpful!
DroidDonX said:
You most likely flashed the Wrong Liquidsmooth ROM (incompatible Kernel), and it hard bricked the phone. It happened to me the same way, and I had to send it in for JTAG.
Click to expand...
Click to collapse
I might have, but the one i downloaded (which is still on the phone's memory card) is a hercules ROM. Either way on my second try there was a hard brick also, in return of which I had to resend it in. The second try was just simply: Odin---->CWM---->Root---->SU---->wipe cache partition+fix permissions+wipe dalvik cache via CWM (not the super scripts).
cipsaz said:
I have bricked my phone installing the Liquidsmooth ROM too. I downloaded the wrong ROM, though. The thread should have a big ****in warning to double check the ROM you are about to download, otherwise your phone is a toast. There were more people who bricked their phones by installing the Liquidsmooth.
Well, I got it back from the warranty and the phone looks good. Installed that Liquidsmooth again and played for a day. Tried other JB ROMs. Most of them are OK in terms of battery life and smoothness, but there is something wrong with the signal. People always say my voice isn't clear. I got tired of all this BS and testing new ROMs and went to back to ICS and won't look back, not anytime.
Don't use darkside scripts, btw. You don't need that anymore.
Click to expand...
Click to collapse
Thanks again for your insight I think i'm done with flashing for a little bit for now.... I kind of want as factory of a JB Rom as possible. :good:
If anyone has any idea where I can get that, please let me know as my Stock ICS is a bit laggy at times, with the facial recognition system, it lags even worse!
rymanh said:
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
that just happened to me today with liquid smooth. i had to unroot, flash stock, and start over. im pretty sure i got it from goo.im under hercules. unfortunate mislabeling? oh yeah, and if your phone shows anything other than nothing, youre not hard bricked. thats why its called Hercules, i think. ive been soft bricked so many times from dumb **** like. ****ing with the governors and all that **** cm gives you the option to do when there aint even a 1080p camera that works fully = / lol <3 Cm I Love Yew!! But yeah, odin will set you free!!!

[Q] Greetings, I understand I have a hard brick?

I first rooted and flashed a KANG JUGGERNAUT ROM 2 years ago, back when I first got my phone.
Just two days ago, a friend recommended flashing CM10 cause it's nearly up-to-date and stuff.
Was instructed to flash CM10 then GAPPS and wipe after; did so, boot loop.
Told me that I was supposed to wipe beforehand? Wish I known, still had soft bricks / boot loops.
Kept restoring and re-flashing; came to a point CWM became super slow, kept hanging when trying to restore/wipe.
Then I chose to flash ROM again, this time it kept rebooting/looping into installation process, hang, fail then rebooting to continue this cycle.
Told friend about it, said he'd look at it when he came over; cause my Odin kept crashing for some unknown reason.
He couldn't get it to stop boot looping so he offered to take back home where he said he had all the stuff he had installed on his PC/MAC.
After awhile he said it wouldn't boot anymore, hard brick.
Afterward he returned it to me, I confirmed a hard brick according to what I have searched/researched online.
Plugging into the USB gives me a connection beep but hitting the power button, gives a disconnect beep? So unable to go into download mode.
I have looked around and found a couple of possible solutions: JTAGGING and USB JIGGING
I'm not sure but I kept seeing a lot of testimony that jigging it wouldn't work on a hard brick phone, can anyone confirm this?
Not sure what JTAG is but apparently is the sure-fire way to get the device in working condition again; is this something I can do by myself?
I see the costs range from $50-100 but I'm not sure if I can afford that right now/tight pockets/strapped4cash/whatever as an unemployed student from LIF with other crazy stuff to deal with.
Worst come to worst, I will probably opt for this JTAG thing.
EDIT: I have this QHSUSB_DLOAD shown in the device manager as I connected the dead device; while searching/looking around, someone said it was fixable but it wasn't in the T989 thread so I'm unsure.
Is this really fixable? and if so, what would this exactly permit me to do after?
Any insight as what options I have? I really would like to get this resolved ASAP.
Thank you for reading; I am also located in NYC, if any locals can help.
Jtag
Hey buddy i recent hard bricked mine last month got it back today PM this guy tomy1986.nt only charged 25$ and had it back in 7 days sucker working good now hes in texas only cost me 5.80$ shipped from Phx Az hope that helps Sounds like a defint hard brick!!!
JahJahLoO said:
I first rooted and flashed a KANG JUGGERNAUT ROM 2 years ago, back when I first got my phone.
Just two days ago, a friend recommended flashing CM10 cause it's nearly up-to-date and stuff.
Was instructed to flash CM10 then GAPPS and wipe after; did so, boot loop.
Told me that I was supposed to wipe beforehand? Wish I known, still had soft bricks / boot loops.
Kept restoring and re-flashing; came to a point CWM became super slow, kept hanging when trying to restore/wipe.
Then I chose to flash ROM again, this time it kept rebooting/looping into installation process, hang, fail then rebooting to continue this cycle.
Told friend about it, said he'd look at it when he came over; cause my Odin kept crashing for some unknown reason.
He couldn't get it to stop boot looping so he offered to take back home where he said he had all the stuff he had installed on his PC/MAC.
After awhile he said it wouldn't boot anymore, hard brick.
Afterward he returned it to me, I confirmed a hard brick according to what I have searched/researched online.
Plugging into the USB gives me a connection beep but hitting the power button, gives a disconnect beep? So unable to go into download mode.
I have looked around and found a couple of possible solutions: JTAGGING and USB JIGGING
I'm not sure but I kept seeing a lot of testimony that jigging it wouldn't work on a hard brick phone, can anyone confirm this?
Not sure what JTAG is but apparently is the sure-fire way to get the device in working condition again; is this something I can do by myself?
I see the costs range from $50-100 but I'm not sure if I can afford that right now/tight pockets/strapped4cash/whatever as an unemployed student from LIF with other crazy stuff to deal with.
Worst come to worst, I will probably opt for this JTAG thing.
EDIT: I have this QHSUSB_DLOAD shown in the device manager as I connected the dead device; while searching/looking around, someone said it was fixable but it wasn't in the T989 thread so I'm unsure.
Is this really fixable? and if so, what would this exactly permit me to do after?
Any insight as what options I have? I really would like to get this resolved ASAP.
Thank you for reading; I am also located in NYC, if any locals can help.
Click to expand...
Click to collapse
Got your phone this morning, an it is already fixed. Restore it to stock rom 4.1.2 everything is ready to go.
Will ship it tomorrow morning.
Thanks choosing my service.
Praise!
tomy1986.nt said:
Got your phone this morning, an it is already fixed. Restore it to stock rom 4.1.2 everything is ready to go.
Will ship it tomorrow morning.
Thanks choosing my service.
Click to expand...
Click to collapse
All praise Tomy for his swift and kind work in helping a poor Samaritan. Thoust good deed shant go unnoticed.
How do I prevent these bricks? Just bricked mine and getting it back from JTAG
I'M BATMAN
-DarkKnight- said:
How do I prevent these bricks? Just bricked mine and getting it back from JTAG
I'M BATMAN
Click to expand...
Click to collapse
Good morning guys
tomy1986.nt said:
Good morning guys
Click to expand...
Click to collapse
How would I prevent my device from getting bricked?
I'M BATMAN
-DarkKnight- said:
How would I prevent my device from getting bricked?
I'M BATMAN
Click to expand...
Click to collapse
Do not flash modified Rom. :laugh:
tomy1986.nt said:
Do not flash modified Rom. :laugh:
Click to expand...
Click to collapse
What do you mean "modified"
Would I have to compare the md5 or what?
I'M BATMAN
-DarkKnight- said:
How would I prevent my device from getting bricked?
I'M BATMAN
Click to expand...
Click to collapse
-DarkKnight- said:
What do you mean "modified"
Would I have to compare the md5 or what?
I'M BATMAN
Click to expand...
Click to collapse
Alway flash phone with Stock rom.
tomy1986.nt said:
Alway flash phone with Stock rom.
Click to expand...
Click to collapse
What about custom ROMs like cm10.1 or JediMindTrick?
I'M BATMAN
The note 1 SGH-i717 of Keith_Dallas,TX member has already fixed today give it back only about a hours.

[Q] HELP I think that I have finally bricked my phone!

Hey XDAers,
I need your help. I think my phone's eMmc chip is dead. Today my phone's screen didnt turn on, I suspected it to be just a buggy kernel or ROM so as any other person would do, I removed the battery and rebooted. Well it did reboot although the boot animation (of Vanir) was lagging. Then I got to my lockscreen but when i was entering my passcode it was extremely laggy and it continued that way for like a min or 2 just freezing for like 5 seconds then continuing until it finally froze for like a min and I decided to reboot. Same thing happened, I kept trying to reboot sometimes it would just freeze others it would reboot on its own. Then I went into recovery and fixed permissions... same thing. Then I wiped dalvik cache, same results. I finally decided to connect it to the PC and pulled everything from the phone using adb and made a nandroid backup to my USB flash drive using my OTG cable and CWM, because when I tried backing up normally to the internal memory I was faced with errors. So then as a last resort I just was gonna flash to stock using fastboot (by the Nexus toolkit). While flashing I got an error telling me that the baseband version I have is different than the one required. even though the baseband from the .tgz or whatever file was successfully flashed. So apparently my radio is UGLL1 (I think) and the radio included in .tgz package was XXLJ1 and even though it was flashed, it didnt change. I tried manually flashing the radio and it also didnt change. So i went in the .tgz file and edited the android-info.txt file inside so that it doesnt require the XXLJ1 baseband to be present and instead just the UGLL1. It started flashing but got stuck at flashing the system partition after it was "sent". At this point I started paniking because normally flashing stock solves everything. So I tried using ODIN (my first time with it) and it took 30 mins to flash everything (25 mins just for flashing system. I was feeling optimistic since it was successfully completed.
Then it rebooted and I see the Vanir boot animation >_> WHATTT??? after all these system flashes and wipes Vanir is still present?? Then after it boots it takes my right to my same lockscreen, like the data and system partition weren't even touched!!! And its still lagging and freezing. So I go to TWRP recovery and try deleting everything from /data/media which works then I reboot again in recovery and everything is back ??? I cant wipe anything. I can add things because I remember earlier during this process I pushed a zip file.
I AM DYING HERE OMG MY PHONE IS LIKE MY LIFE. PLEASE HELP!!!!!!!! I THINK ITS DEAD BUT I'LL TRY ANYTHING :crying:
Same issue I had; unfortunately that is describing the painful EMMC death. Had to buy another GNEX (http://forum.xda-developers.com/showthread.php?t=1909331 and http://forum.xda-developers.com/showthread.php?t=2354641)
jhonnyx said:
Same issue I had; unfortunately that is describing the painful EMMC death. Had to buy another GNEX (http://forum.xda-developers.com/showthread.php?t=1909331 and http://forum.xda-developers.com/showthread.php?t=2354641)
Click to expand...
Click to collapse
This is devastating me... I've been crying for the past half hour about this. I never thought this could happen, that this device could be bricked
Do you know if Samsung could help me with this, like if they could replace the motherboard maybe. Hopefully it doesn't cost much trying to think of any under-$100 options.
yasir.97 said:
This is devastating me... I've been crying for the past half hour about this. I never thought this could happen, that this device could be bricked
Do you know if Samsung could help me with this, like if they could replace the motherboard maybe. Hopefully it doesn't cost much trying to think of any under-$100 options.
Click to expand...
Click to collapse
You can try Samsungs warranty. Once I bricked my motherboard and got it replaced.
Sent from my Galaxy Nexus using Tapatalk
aaron13 said:
You can try Samsungs warranty. Once I bricked my motherboard and got it replaced.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
They said it would cost about $300 in total. The employee advised me to buy a new phone which I'm going to do. I'll get the Nexus 5 now .
I'm gonna miss this Galaxy Nexus community
yasir.97 said:
They said it would cost about $300 in total. The employee advised me to buy a new phone which I'm going to do. I'll get the Nexus 5 now .
I'm gonna miss this Galaxy Nexus community
Click to expand...
Click to collapse
If your screen is in good shape, you may be able to sell your Gnex for parts.
Sent from my Nexus 7 using xda app-developers app

Categories

Resources