Database Users

From Root to Brick

Well, I forgot to read that a kernel was for 2.2 after downgrading from 2.2 and rooting 2.1. I attempted to install the battery baked snacks kernel and now touchscreen is not recognized menu and home buttons etc do not work. The only thing that works is the up and down key and power. I have tried to push adb factory kernel however cmd prompt is giving me the error cannot locate device. >.<

boot into recovery and restore your last backup

Yeah thats the problem. I just got done rooting there is no back ups arrrghhhh.

Woohoo I fixed ! Under the recovery menu there is a mount option loaded the PC image from the root method and now im back to where I was 2 hours ago lol!

Thats much better than bricked

Agreed. Now I know how to always recover from that though lol.

EVO 4G said:
Well, I forgot to read that a kernel was for 2.2 after downgrading from 2.2 and rooting 2.1.
Click to expand...
Click to collapse
Guess you'll be reading everything before flashing next time. Glad you worked it out.

Once again, can we stop throwing the word "bricked" around so casually? I've never seen any bricks with recovery consoles.

SilverZero said:
Once again, can we stop throwing the word "bricked" around so casually? I've never seen any bricks with recovery consoles.
Click to expand...
Click to collapse
Quoted For Truth Justice and The XDA Way.

So, Im thinking If I should ROOT my new evo or wait till an easier on/off ROOT!!! Hmm....

SilverZero said:
Once again, can we stop throwing the word "bricked" around so casually? I've never seen any bricks with recovery consoles.
Click to expand...
Click to collapse
Exactly, it's only bricked once you can't get into the bootloader anymore, and even then there is still a small chance of recovery.

donatom3 said:
Exactly, it's only bricked once you can't get into the bootloader anymore, and even then there is still a small chance of recovery.
Click to expand...
Click to collapse
Depending on someone's level of experience, having no functionality other than the bootloader screen is bricked. It goes back to the definition of bricked which is simply a loss of function such that the phone is as useless as a brick. It's all semantics and relative to the users level of experience. It all depends on the user's ability to recover the phone.
Sent from my PC36100 using XDA App

Thanks for the back up sombdy. I agree though its not truely bricked, however at that point in time when it happened it might as well have been a "brick," until I learned that I could mount it through the bootloader and adb push the files I needed to fix it.

EVO 4G said:
Thanks for the back up sombdy. I agree though its not truely bricked, however at that point in time when it happened it might as well have been a "brick," until I learned that I could mount it through the bootloader and adb push the files I needed to fix it.
Click to expand...
Click to collapse
Just pushing for a little conservatism, that's all. Glad you got things lined up.

sombdy said:
Depending on someone's level of experience, having no functionality other than the bootloader screen is bricked. It goes back to the definition of bricked which is simply a loss of function such that the phone is as useless as a brick. It's all semantics and relative to the users level of experience. It all depends on the user's ability to recover the phone.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I guess I look as the term bricked = dead. If the heart is still beating and there is a chance to get the brain functioning again then it's not dead aka bricked.
I will say I'm glad the OP wasn't bricked and even more so that he/she was able to figure out the problem on their own and fix it. Always feels better when you do it yourself, and makes you feel more adventurous the next time you have to do something.

If a person can get the bootloader screen, why wouldn't they just be able to flash stock from there as a last resort?

I have to agree. When I bricked my phone it was truly a brick - no power, nada. Just sat there. No lights. No hboot. No white screen.
If you can power on, there's a solution.

did i kill my epic?

i was running odin and download mode closed my phone now wont boot up or anything......
Euhmmmmm.... *poo*
just loaded and it has a pic of a cell a caution sign then a pc
*end heart-attack it decided it would work* i love the epic even more now....
PyRo
*please lock*

Take off the back, pull out the battery, pop battery back in and boot as normal into Download mode (holding down 1 as it powers up). Should work just fine.

bullet2300 said:
Take off the back, pull out the battery, pop battery back in and boot as normal into Download mode (holding down 1 as it powers up). Should work just fine.
Click to expand...
Click to collapse
I sort of had the same issue, but nothing I do will get the unit to power on. Plugging it in to the charger does not turn the charging light on. And no three button method is working. The screen stays black, no charging light. Suggestions?

Never mind, it did come back.

same problem
epic wont boot, charge, etc
please help

You're going to have to give us info if you want any help.
ROM, What you did right before it happened, etc.

RANT- Is it me or is it ever thread now somebody bricking their epic? Not trying to be a **** but it like people dont research at all. Me coming from an evo i will admit the epic is a whole other beast. But i atleast took the time to research everything before i rooted.
mmhertz26= Try getting the phone in download mode( hold power button with #1 key) at the same time. If that works use odin to flash back to stock with right files. Also check your download files size before you try to flash it.

903tex said:
RANT- Is it me or is it ever thread now somebody bricking their epic? Not trying to be a **** but it like people dont research at all. Me coming from an evo i will admit the epic is a whole other beast. But i atleast took the time to research everything before i rooted.
mmhertz26= Try getting the phone in download mode( hold power button with #1 key) at the same time. If that works use odin to flash back to stock with right files. Also check your download files size before you try to flash it.
Click to expand...
Click to collapse
The word brick is used too losely around here. Unless you've messed with the boot loader, and can no longer get into download mode your phone is NOT bricked.
Bricked means your phones is just a hunk of metal/plastic that's good for nothing but a paper weight.
Sent from my SPH-D700 using XDA Premium App

XtaC318 said:
The word brick is used too losely around here. Unless you've messed with the boot loader, and can no longer get into download mode your phone is NOT bricked.
Bricked means your phones is just a hunk of metal/plastic that's good for nothing but a paper weight.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Yeah we need a new word for soft bricking. Softing? Broft? Oops?

heathmcabee said:
Yeah we need a new word for soft bricking. Softing? Broft? Oops?
Click to expand...
Click to collapse
Nerf Brick? TV Brick? Sponged?
Do you BONSAI?

How about forget the term, and have people who are new to this actually research before jumping in.. but that's impossible because there's a lot of ignorant and stubborn people out there ^-^
Sent from my SPH-D700 using XDA Premium App

XtaC318 said:
How about forget the term, and have people who are new to this actually research before jumping in.. but that's impossible because there's a lot of ignorant and stubborn people out there ^-^
Click to expand...
Click to collapse
you think with all the disclaimers on each and every rom,root,theme,ect that people would understand the risks involved in modding whether its a ps3 xbox360 phone router anything but all logic seems to disappear.

kennyglass123 said:
Nerf Brick? TV Brick? Sponged?
Do you BONSAI?
Click to expand...
Click to collapse
lol
BTW its is thrown around how about saying in your thread title like stuck on a screen, errors in clockwork or other nice terms to help u more,
It is really hard to brick this thing believe me ive done it all, FCs, errors in clockwork, stuck on samsung screens boot loops and yesterday officially bricked!!!
The only reason it bricked is some charge card in a beta bonsai rom, but thats what tep is for.
And remeber if you can see something on your screen of your phone use odin or heimdell to go back to stock if you phone wont charge,gointo download mode or go on or go into recovery then its time to take it in and replace it.

Mnhertz26. Did you fix your epic too or is it another real brick?¿

I know what a brick phone is. Im just tired of people not knowing what to do asking questions that are already explanied and sticky on top of the page. Not researching will cause this problem until people realize that if you dont understand this then you need to read, read, read. I had a wm phone and if you flashed the wrong file...DONE. Atleast with the epic as long as it can get in download mode you should be fine.

brendan802 said:
Mnhertz26. Did you fix your epic too or is it another real brick?¿
Click to expand...
Click to collapse
Another real brick? So far there haven't been any Epic's that weren't recoverable.

Ouch I am so glad I did not run Bonsai on my phone yet I was waiting for i dunno what but dodged that issue.
For those who jacked thier phones but didnt brick persay make sure you have a charged battery before starting and if unabl to charge after the incident you can charge in an external charger to get back into dload mode to odin back to stock or CW flash a back-up
Peace

I just cant brick my phone - WARNING ON ODIN -

Dear all,
Maybe strange.........
I just cant brick my note! Not that i want to but how? before i knew the brickbug i did:
Odin flash to a leak ICS
Rebooted in CWM And wiped Factory default.. No problem
At one time i even formatted EMMC however its called.
At this time ICS brickbug shows up in this forum and i downloaded the APK brickbug app and i seem to be vulnarable.
Today a friend comes in with a bricked note.. tellin me he was flshing from odin and it hung on first part of flash without starting. He removed phone after 30 secs.
please take notice that it can take up to 2 minutes to start flashing.
any thoughts on this story?

jeroen180 said:
Dear all,
Maybe strange.........
I just cant brick my note! Not that i want to but how? before i knew the brickbug i did:
Odin flash to a leak ICS
Rebooted in CWM And wiped Factory default.. No problem
At one time i even formatted EMMC however its called.
At this time ICS brickbug shows up in this forum and i downloaded the APK brickbug app and i seem to be vulnarable.
Today a friend comes in with a bricked note.. tellin me he was flshing from odin and it hung on first part of flash without starting. He removed phone after 30 secs.
please take notice that it can take up to 2 minutes to start flashing.
any thoughts on this story?
Click to expand...
Click to collapse
Go to the church and donate 10 euros...
You might not be so lucky next time around.
Because you didn't brick doing 1 wipe, doesn't mean that you cannot brick..
It's like getting struck by lightning, maybe you will survive the first, but it
might not save you a second time...

Well, it is a brick bug, so it is only a chance - not definitive. I have stock ICS infected with the bug, but haven't nor plan on flashing or anything like that so...

friedje said:
Go to the church and donate 10 euros...
You might not be so lucky next time around.
Because you didn't brick doing 1 wipe, doesn't mean that you cannot brick..
It's like getting struck by lightning, maybe you will survive the first, but it
might not save you a second time...
Click to expand...
Click to collapse
Back on first HTC android phone )G1) i got it bricked 3 times by flashing SPL 3 times. Anywayz Android is much better (for me) then IOS from crapple. Only HTC dreams where crap in quality since the board has been replaced 5 times due hardware failures...
Now back on business:
I know im lucky. But still .. what causes the randomness of bricking. I mean it is there or it is not? Maybe god exists. I love my note too much to brick it

jeroen180 said:
Back on first HTC android phone )G1) i got it bricked 3 times by flashing SPL 3 times. Anywayz Android is much better (for me) then IOS from crapple. Only HTC dreams where crap in quality since the board has been replaced 5 times due hardware failures...
Now back on business:
I know im lucky. But still .. what causes the randomness of bricking. I mean it is there or it is not? Maybe god exists. I love my note too much to brick it
Click to expand...
Click to collapse
It isn't random. There are just multiple conditions that need to come together to trigger it. Read the thread about it to understand better the hows and why's.

friedje said:
It isn't random. There are just multiple conditions that need to come together to trigger it. Read the thread about it to understand better the hows and why's.
Click to expand...
Click to collapse
Even if all the conditions are met there's still a good chance it won't happen. IIRC there are also versions of emmc chips that don't have the brickbug.

pboesboes said:
Even if all the conditions are met there's still a good chance it won't happen. IIRC there are also versions of emmc chips that don't have the brickbug.
Click to expand...
Click to collapse
Well the fact of having a dangerous chip is one of the conditions....
So if you don't have it then not ALL the conditions are met..
Believe me if all the conditions are met, it will brick, it"s not random.
Then, Jeroen stated that he tested with Chainfires app, and he does have the faulty chip.
Finally I haven't seen a Note in the wild yet that doesn't have a faulty chip.

I feel like the OP. Before I knew of the bug I flashed and wiped many times. But I only flash stock roms. I don't know if that helped or not.
Sent from my GT-N7000 using xda premium

[Q] How to prevent bricking/messing up

Hey, I've seen many threads about people bricking their phone, and I don't wanna end up like them.
So, I want to unlock bootloader,root and flash kernel, I've read using TOOLKIT isn't the best thing to do, so I'll follow this tutorial.
My question is, what can go wrong? How to prevent anything from going wrong?
Sorry if it's a stupid question, but it's my first Android and I rather ask than be sorry, thanks in advance.

Ciclop said:
Hey, I've seen many threads about people bricking their phone, and I don't wanna end up like them.
So, I want to unlock bootloader,root and flash kernel, I've read using TOOLKIT isn't the best thing to do, so I'll follow this tutorial.
My question is, what can go wrong? How to prevent anything from going wrong?
Sorry if it's a stupid question, but it's my first Android and I rather ask than be sorry, thanks in advance.
Click to expand...
Click to collapse
Just make sure anything u do you read the thread and defiantly the op and only flash stuff that made for the N4 u should be good. Read read read and learn. I've only bricked one phone and I know what I did wrong its very hard to brick a phone so long as u don't just go flash stuff u dont know what it is.
Oh yea don't over clock your phone and run benchmarks its stupid and has fried a few also. I'm onderclocked to 1134 and I still run smooth as butta.
Sent from my Nexus 4 using Xparent Blue Tapatalk 2

Ciclop said:
Hey, I've seen many threads about people bricking their phone, and I don't wanna end up like them.
So, I want to unlock bootloader,root and flash kernel, I've read using TOOLKIT isn't the best thing to do, so I'll follow this tutorial.
My question is, what can go wrong? How to prevent anything from going wrong?
Sorry if it's a stupid question, but it's my first Android and I rather ask than be sorry, thanks in advance.
Click to expand...
Click to collapse
For a REAL hard brick on a Nexus device, you really have to do something wrong. Like I did with my Nexus S .
A real hard brick, one that isn't even repairable with a JTAG brick repair service, it never happens with a Nexus device. Well, ALMOST never. I made it happen. I don't even know what I did wrong, but apparently I screwed up the radio. Even the best of the best (Adam Outler) wasn't able to repair it. It happened the day after I installed a new ROM and a mod. The battery drained really fast. After it was dead, I plugged it in the charger, booted up my phone, started the browser, and BAM. Dead. Forever.
But I wouldn't worry about those things. Just don't do too much overclocking, because there are ways to screw up the hardware inside. Almost all bricks are fixable. If you can access fastboot mode you're okay. If you can't, there are still ways to fix it, but it might cost you some money. I don't know if Adam Outler's Unbrickable Resurrector tool works with the N4, but that's also an option if you think you really screwed up.

1) Make sure that you never flash a file that wasn't designed for the Nexus 4 (MAKO)
2) Make sure that you don't have empty batteries when you flash. 50% would be a safe minimum (though I personally frequently flash with much less than that)
3) Flashing radios / bootloaders is traditionally amongt the most dangerous operations that you can do. Make sure to check MD5 on all radios (you can check on every file if you want to be super careful)
Note: the reality is that with a nexus device, it's almost impossible to brick your device. Even if you do all of the things above wrong, you'r probably still safe. BUT, you were looking for advise--so follow those three points and you should be fine.

OP, read the link in my signature about toolkits and it will answer your question.
Sent from my Nexus 4 using xda premium

Thank you all for quick replies!
I only plan on flashing Franco's/Faux's kernel, hopefully everything will go well

unlocking the BL on a nexus is very easy. I am not sure if you need a toolkit for that.
but yeah use one if you feel more comfortable with it.
also as of now do not overclock the processor as that has been causing some bricks AFAIK.

Androyed said:
For a REAL hard brick on a Nexus device, you really have to do something wrong. Like I did with my Nexus S .
A real hard brick, one that isn't even repairable with a JTAG brick repair service, it never happens with a Nexus device. Well, ALMOST never. I made it happen. I don't even know what I did wrong, but apparently I screwed up the radio. Even the best of the best (Adam Outler) wasn't able to repair it. It happened the day after I installed a new ROM and a mod. The battery drained really fast. After it was dead, I plugged it in the charger, booted up my phone, started the browser, and BAM. Dead. Forever.
But I wouldn't worry about those things. Just don't do too much overclocking, because there are ways to screw up the hardware inside. Almost all bricks are fixable. If you can access fastboot mode you're okay. If you can't, there are still ways to fix it, but it might cost you some money. I don't know if Adam Outler's Unbrickable Resurrector tool works with the N4, but that's also an option if you think you really screwed up.
Click to expand...
Click to collapse
My N4 its bricked, I contact Google for RMA. Now, my history...
N4 bought 13/nov.
-Rooted with Nexus 4 Toolkit
- ROMS installed: 1- Stock (default) 2- Minco 3- Xylon (when i got bricked)
- Kernels:1- Stock (default) 2- Franco 3- Faux (when i got bricked)
In kernel Ops: (Last Faux beta kernel)
- Underclock: (YES, READ, UNDER): 1mgz at max
- Undervolt: -137 mv all freqs
- GPU Downgraded to 200mhz
- Screen settings changed
- Hapatic feedback downgraded to 50%
That was my config. Now comes the drama...
My phone was perfectly OK at less for 2 days with that kernel and ROM combination (because i've updated few days before got bricked) So, my phone even with the downgrade config was so smoth and everything was perfectly ok.... the night of new year, when I was taking a shower, my N4 was charging SO SLOW, i dont give a f*ck and continue my night so normal, then I went out to my gf house, i have like 30 % and decide to charge again, starts charging slow again, now im worried about it so i decide to restart the phone, and problem still there... but now the device was overheating so much and the phone got discharged because i got to go, when I come to my house in the morning, i put the charger, the only thing it do is blink red led, nothing else.
Conclusion:
When your phone got bricked doesn't mean you have the guilty, because mine was STABLE for at least 2 days, for my, it was an hardware prob.
Now, the only way, RMA.
So if I was you, I lock my bootloader again.

[Q] A500 always powers off after booting up

Hey folks! I have an Acer A500 that I have been working on "with" dibb_nz over the past week. I have no idea what was on it originally, it came to me nearly dead. After a TON of attempts and hard work from dibb, I now have Skrilax's bootloader and recovery installed. I flashed CM10-10 Flex_V6 ROM from Civato onto the device successfully. Here is the problem: no matter how I boot up, it either goes directly into "Power off - Shutting down" then vibrates and blanks out or, after a fresh install, it will say "Android is upgrading", "Optimizing apps", "Starting Apps", then on to the Power Off-shutting down thing.
Does anyone have any clue what may be going on here? I have tried earlier ROMS, all from Civato, but with the same Power OFF result.
Any help would be MUCH appreciated!
Thanks in advance,
Sharkguy

hey sharkguy, I've been combinf forums and threads with no joy at all, the only thing I haven't checked is the rom thread, might pay you to look thru that, just in case its rom related ( I doubt it really, but there maybe other reports such as yours ) If I ever come across something I'll be sure to get back to you, good luck m8
Calling @Moscow Desire---are you out there Mr Moscow?? Ever heard of something like this before, my friend, very strange....Hope you are well MD its been awhile

dibb_nz said:
hey sharkguy, I've been combinf forums and threads with no joy at all, the only thing I haven't checked is the rom thread, might pay you to look thru that, just in case its rom related ( I doubt it really, but there maybe other reports such as yours ) If I ever come across something I'll be sure to get back to you, good luck m8
Calling @Moscow Desire---are you out there Mr Moscow?? Ever heard of something like this before, my friend, very strange....Hope you are well MD its been awhile
Click to expand...
Click to collapse
Hey Dibb! Offhand, I think it may be the old power part that used to be flashed with stock ROMs. Forget what its actually called. Typically we removed this from the install as its generally not needed. That's a guess, but am at work for the night so can't check my stuff. Could explain the shutdown. But if it shuts down when updating the apps, then its probably bad memory partition.
But I'll lean more towards the power part. Will have to check a stock ICS ROM. Might need to make a separate flash install just for it. It it would boot to the display and it had horrible display and battery issues then that would be it.

Well, that sounds complicated. I should have the new battery by the weekend so let me at least try that before anyone gets all technical. Unfortunately I dont know anyone with another a500 to test batteries...
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk

Moscow Desire said:
Hey Dibb! Offhand, I think it may be the old power part that used to be flashed with stock ROMs. Forget what its actually called. Typically we removed this from the install as its generally not needed. That's a guess, but am at work for the night so can't check my stuff. Could explain the shutdown. But if it shuts down when updating the apps, then its probably bad memory partition.
But I'll lean more towards the power part. Will have to check a stock ICS ROM. Might need to make a separate flash install just for it. It it would boot to the display and it had horrible display and battery issues then that would be it.
Click to expand...
Click to collapse
Hey MD good to see u my friend
oh, the eec thing? Rings a bell...
The bad memory partition, do you mean the memory chip itself or just the partition.
I've just never heard of the faulty chip causing a spontaneous shut down, sure has me beat....and I Hate that, lol
But thanks for the response MD, if you can offer any solution from your archives of knowledge and wisdom, I know someone who'd be forever grateful
Have a great day all!!
rgds Donna

Yeah Dib, the eec thing. Just couldn't remember. Usually we just removed that command from the install script as usually once it was flashed at the factory, rarely did you ever have to flash it again. I will have to look and see in the next couple of days. Worth a shot though. Might be able to put it in a CWM install.
Oh, forgot to add @sharkguy
As with a damaged partition, if the memory got hosed in that particular partition, whichever, there's not a whole lot that can be done. Could try running babsector, but not sure if it would fix it or not. There's been success running it before, but only about 30% as I can tell. Devblks can get physically damaged. Usually the partitions are large enough to mark the bad spots as bad, and still be able to install things. That's what babsector did I think as near as I can tell.
A faulty chip "could" cause a shutdown, especially if it couldn't create the dalvak which is kind of the next step when "starting applications" If I guess right, although I would think it would bootloop rather than shut down. As you say, I've never heard of a power off before, unless the eec was bad and it thinks the battery is dead.
I'm just curious if the OP has done a full format on internal memory via CWM? Before installing. Not the usual wipes, but going into advanced, and triggering the full format. I used it after running that CM stuff awhile back, as it messed up everything (lots of testing). Needed a clean sweep of the internal memory.
As you see, I am still around Just with being a senior mod, not a lot of time for messing with things.
I'm still leaning towards eec pwr. (I'm using beer logic at this point)
Bear with me on this. Let's say the eec got hosed somehow. It happens on occasion. And you install several custom roms, which of course don't have eec pwr in the install script as we removed it. Here's what I know.
1) Battery won't charge and is always going to shut down
2) No response on the touch screen if indeed the OS starts.
3. Tab shuts down after OS start.
So you see why I am leaning towards this.
MD
EDIT: The reason why we removed eec from the custom roms to begin with, primarily as it really wasn't needed, but it "could" cause an issue if the flash went bad. But considering the OP has UID and NVFlash, that isn't an issue now.
dibb_nz said:
Hey MD good to see u my friend
oh, the eec thing? Rings a bell...
The bad memory partition, do you mean the memory chip itself or just the partition.
I've just never heard of the faulty chip causing a spontaneous shut down, sure has me beat....and I Hate that, lol
But thanks for the response MD, if you can offer any solution from your archives of knowledge and wisdom, I know someone who'd be forever grateful
Have a great day all!!
rgds Donna
Click to expand...
Click to collapse

Hey MD, thanks for thr insight on my issue. I worked closely with Dibb_nz for close to a week. I am not entirely sure if I did the wipe you mentioned, but believe me, if I could find a way to format, erase, wipe or clear memory I did. Everything you described as what you knew is correct with one exception: if it is relevant the touch screen works in recovery mode.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk

sharkguy said:
Hey MD, thanks for thr insight on my issue. I worked closely with Dibb_nz for close to a week. I am not entirely sure if I did the wipe you mentioned, but believe me, if I could find a way to format, erase, wipe or clear memory I did. Everything you described as what you knew is correct with one exception: if it is relevant the touch screen works in recovery mode.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Always works in recovery, as it is independent of the OS...

Righto. I figured it didnt matter in this case. But yes, the rest of the facts are as you understand them.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk

sharkguy said:
Hey MD, thanks for thr insight on my issue. I worked closely with Dibb_nz for close to a week. I am not entirely sure if I did the wipe you mentioned, but believe me, if I could find a way to format, erase, wipe or clear memory I did. Everything you described as what you knew is correct with one exception: if it is relevant the touch screen works in recovery mode.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
The FULL wipes as stated in the guide m8 or via fastboot erase.
@Moscow Desire _bab sector was run and successfully, boot loader and recovery installed with no errors.
As far as the eec thing I do have a copy of that in my stash if that's any help, but no idea how to apply it????
Sent from my HTC_PN071 using Tapatalk

Well at this point I am open to anything. I just passed up on a steal of a deal on a Samsung Galaxy Tab 3 7" so im itching to know I made the right choice. I am at your mercy. Doesnt look like I will have that battery until saturday at the earliest, but so far all of the work I have done on it has been with AC power and has been successful.
Sent from my SGH-I317M using xda app-developers app

sharkguy said:
Well at this point I am open to anything. I just passed up on a steal of a deal on a Samsung Galaxy Tab 3 7" so im itching to know I made the right choice. I am at your mercy. Doesnt look like I will have that battery until saturday at the earliest, but so far all of the work I have done on it has been with AC power and has been successful.
Sent from my SGH-I317M using xda app-developers app
Click to expand...
Click to collapse
Well m8 I dunno if u made the right choice there, I guess only time will tell...there is this thread http://forum.xda-developers.com/showthread.php?t=2617196. I cannot recommend it but then my tab has never been in that state...and I'm not sure I could bring myself to put it in the oven lol...u nut wanna take a look at it any way
Sent from my HTC_PN071 using Tapatalk

Oh I've heard of ppl doing such things, but I'm luckily far mor fortunate than that. I am an electronics technician and have access to far for humane methods than an oven! Maybe I will see if I can still get the deal, then hack the a500 to pieces after geting the new battery in the mail. Lol
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk

sharkguy said:
Oh I've heard of ppl doing such things, but I'm luckily far mor fortunate than that. I am an electronics technician and have access to far for humane methods than an oven! Maybe I will see if I can still get the deal, then hack the a500 to pieces after geting the new battery in the mail. Lol
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Well, you'll be in your element then,lol...Yeh, your issue is rather unique...with babsector not returning any error its out of my area of expertise!!! But I do know that Acers build quality isn't the best....from power buttons falling out to the memory chip failure and their dodgy soldering techniques, i'm leaning towards a hardware fault 'somewhere'....
But then, it does seem strange the tab powers off during "updating apps" that points to software doesn't it???? Have look in the guide for fastboot commands (if you still have the unlocked bootloader on there) I'd erase all partitions, /system, /data, /cache etc....then run babsectot again to repartition -flash a rom and see what happens...or use tdv4 to do the same, but no rom flash needed for that as it comes with HC 3.2.1 rooted and cwm.
Anyways m8 keep us updated - and fingers crossed you end up with a positive resolution
rgds Donna

One of the last things I think I did was tdv4 without a rom flash. It still came up with the same issue. I did notice that when I took the battery out to charge on the equipment at work (closely monitored of course) to see if there was an issue with the charging circuit, that I could still do all of the same things as before with just the AC plugged in. No battery. This is why I bought a battery to try that out. The Galaxy 3 guy realized what a steal he was offering me and bumped up his price so it looks like I'm stuck woth the A500.
Thanks for the crossed fingers!!
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk

Well new battery us in and seems to charge just fine. In fact the tablet would not even attempt to power on before without AC so that is a plus. However, the same thing happens still. Boots up, and as soon as it enters the OS it gies straight to powering down.
What was the EEC thing you guys were discussing? Would it potentially help here?
Thanks again!
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk

Used all of the elements at my disposal at work to reflow the board without any change in the status of the tablet. Any ideas based on that EEC thing you guys discussed above?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk

sharkguy said:
Well new battery us in and seems to charge just fine. In fact the tablet would not even attempt to power on before without AC so that is a plus. However, the same thing happens still. Boots up, and as soon as it enters the OS it gies straight to powering down.
What was the EEC thing you guys were discussing? Would it potentially help here?
Thanks again!
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
sharkguy said:
Used all of the elements at my disposal at work to reflow the board without any change in the status of the tablet. Any ideas based on that EEC thing you guys discussed above?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Soz m8 been full on at work to even check emails let alone reply...phew!!!!
As MD pointed out above, the EEC file thing, devs have dealt with that particular issue, but b/c yours is a relatively unique issue I guess it can't be ruled out...
Have you managed to take a look at fastboot and using the erase command to delete EVERYTHING - at least u can be sure its as clean as can be, then using babsector with an appropriate rom and see what happens there.
In that "tab flu" thread there are links to another thread (somewhere) re: eec thing - If you find it can link it here in this thread and I'll track down the file -
Oh, just to be clear - when it boots into to the OS and powers off - is it completely shutting down i.e. power led is off or is it actually booting to apx mode, black screen power lite on...whats the chances of a vid so we can see exactly what it does???
rgds dibb

Sure I can video it for ya, but how should I link it? Can I link to YouTube on these forums?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk

sharkguy said:
Sure I can video it for ya, but how should I link it? Can I link to YouTube on these forums?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Ok, so new development, so to speak. As you can see from the crappy video I shot just now, I can boot the tablet into the start of the OS, but it hangs at Powering Down. The new part is that I had to manually shut it off, it did not do that itself this time. I showed you the power light (orange) and when I press it again, it does power on, but is still hung up on the same screen. I don't know if that helps any, but now you can see it. By the way, sorry it is upside down, it was the only way to show you the power button after it booted.
http://youtu.be/pG_efbq6DZg