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.
Related
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
My wife has been nagging me to root and rom up her Fascinate for a while now after seeing me spend hours playing with different roms and mods on my Incredible. She got bored and tried to flash something and "bricked" her phone. Uuhhg guess who gets to fix it? I want to thank you all for the easy to follow directions, I was able to get her on DL09 after following the great guides posted in the forum. Man this phone is a little more tricky than my dInc, but I am in LOVE with the big screen!! Once again, thank you all, my wife finally is happier and stopped nagging me!
Congrats man, thats good to hear. The phone's not really that difficult to mess around with though
kenesis said:
Congrats man, thats good to hear. The phone's not really that difficult to mess around with though
Click to expand...
Click to collapse
I'm just use to my phone I guess Odin had me a little nervous (hooking up with the battery pulled and all) but given a little time I'll probably be allot more comfortable with it (until the wife gets bored again).
Just keep in mind that as long as you don't flash anything with the Phone button in ODIN, it's almost impossible to actually brick this phone. Even then it's not technically a brick, as you can still make it bootable; the cellular radio just won't work anymore.
Can we trade wives?
tyler1234567 said:
Can we trade wives?
Click to expand...
Click to collapse
I'll let you know as soon as she breaks something else I have to fix
ivorycruncher said:
Just keep in mind that as long as you don't flash anything with the Phone button in ODIN, it's almost impossible to actually brick this phone. Even then it's not technically a brick, as you can still make it bootable; the cellular radio just won't work anymore.
Click to expand...
Click to collapse
I was wondering about that; glad I'm good at following directions. Thanks for taming my curiosity on the other buttons
ivorycruncher said:
Just keep in mind that as long as you don't flash anything with the Phone button in ODIN, it's almost impossible to actually brick this phone. Even then it's not technically a brick, as you can still make it bootable; the cellular radio just won't work anymore.
Click to expand...
Click to collapse
Thanks for the info!
Awesome, my wife hates my phone. She can't stand hearing about roms and kernels.. I understand why but that just sucks
mindcritic said:
I'll let you know as soon as she breaks something else I have to fix
Click to expand...
Click to collapse
Sent from my SCH-I500 using XDA App
Hello friends,
For reasons I do not even want to bother to understand, as I am on the waiting list for the Evo 3D and will never again buy any Samsung product, though I would like to have at least basic mobile phone capabilities until the end of June, my Epic has died. It got to the point I would have to remove the battery every 10 minutes and restart. I would get all these Touchwiz errors. So I decided to hard reset, at least so I could have a phone. I'll reinstall apps when I get my Evo 3D. So I removed the SD card, and went to Settings-Security and initiated a hard reset. That was four hours ago and the SAMSUNG logo is appearing as when you restart the device, and staying put. Is the hard reset this long? What should I do? This phone, which I've had since last fall, has been the worst experience of my life, and that doesn't even count the Froyo fiasco of a few months ago. Good riddance to Samsung. I bought a Moto Xoom, which has worked flawlessly over the past month on Honeycomb. It's nice to know that there are some Android devices that don't cause so much pain and suffering that you want to scream as does this horrid Samsung phone. But I need a phone for the next 2 and a half weeks before the Evo 3D makes an appearance, so I would dearly love to know what to do at this point! Thanks in advance.
Hard reset shouldn't take more than 3 or 4 minutes.
Is your phone rooted? Are you on a custom ROM? Do you know how to use ODIN?
Thanks.
poit said:
Hard reset shouldn't take more than 3 or 4 minutes.
Is your phone rooted? Are you on a custom ROM? Do you know how to use ODIN?
Click to expand...
Click to collapse
Thanks. I am/was rooted. I do have ODIN but need a refresher.
Roots his phone, has issues, incorrectly tries to do a recovery and it's Samsung's fault...
drplaud said:
Thanks. I am/was rooted. I do have ODIN but need a refresher.
Click to expand...
Click to collapse
Recommend you follow the instructions in this thread.:
http://forum.xda-developers.com/showthread.php?t=1052813
Read it carefully, Do exactly as it says. Do NOT unplug the phone until they tell you to.
Good luck.
Seems like some people like to generate heat and no light...
gjones77 said:
Roots his phone, has issues, incorrectly tries to do a recovery and it's Samsung's fault...
Click to expand...
Click to collapse
I am looking for assistance, not your petty judgment. The root issue had to do with a recommendation from this very forum. Thank you for your non-help. Yet another reason that I wish to leave Samsung forums. I hope Samsung is paying you for your good work.
poit said:
Recommend you follow the instructions in this thread.:
http://forum.xda-developers.com/showthread.php?t=1052813
Read it carefully, Do exactly as it says. Do NOT unplug the phone until they tell you to.
Good luck.
Click to expand...
Click to collapse
Thank you very much. I will do so, and again thank you for helping rather than criticizing as in that other fellow's reply. Where do those people come from?
The thing is u blame samsung for all of it when it probably was user error. But u don't want to hear that.
"The greatest respect you can earn is self respect" Louie Simmons
drplaud said:
Hello friends,
For reasons I do not even want to bother to understand
Click to expand...
Click to collapse
Aka pebcak
Sent from my SPH-D700 using XDA App
drplaud said:
Thank you very much. I will do so, and again thank you for helping rather than criticizing as in that other fellow's reply. Where do those people come from?
Click to expand...
Click to collapse
Just need to mention that my first instinct was to criticize too. It comes from the tone and attitude of your original post. Most of us in this group like our Epics, and in my case it has been the best phone I have ever owned. I have found that the few problems I have had with it have come from my mistakes, installing poorly designed ROMS, etc. I'm back on the stock Sprint ROM and have a rock solid well performing phone. Maybe you have a lemon, but without knowing the history I'm not going to judge.
Anyway, best of luck getting the phone revived.
Got it to work.
poit said:
Just need to mention that my first instinct was to criticize too. It comes from the tone and attitude of your original post. Most of us in this group like our Epics, and in my case it has been the best phone I have ever owned. I have found that the few problems I have had with it have come from my mistakes, installing poorly designed ROMS, etc. I'm back on the stock Sprint ROM and have a rock solid well performing phone. Maybe you have a lemon, but without knowing the history I'm not going to judge.
Anyway, best of luck getting the phone revived.
Click to expand...
Click to collapse
I followed POIT's recommendations, and I have my phone back, worked like a charm, thanks. I understand the issues, but this phone has been a challenge. When I got it I was "promised" a 2.2 upgrade within weeks, quickly ran out of space with no ability to put apps on the SD card, and then what ensued was four months of FROYO chaos. Enough. I hope you all enjoy your Epics, shortly I'll be in Evo 3D land, and I think more content.
Once again, to those who helped, many thanks, especially POIT.
drplaud said:
I am looking for assistance, not your petty judgment. The root issue had to do with a recommendation from this very forum. Thank you for your non-help. Yet another reason that I wish to leave Samsung forums. I hope Samsung is paying you for your good work.
Click to expand...
Click to collapse
First off, when a person seems to know enough to go and root their phone yet doesn't bother to go about finding the information to setting it back to stock which is a sticky in the dev section, yes I'm going to make note.
When a person goes and creates problems for themselves and then wants to blame the product for their own inability to follow directions and be ready for a failure, that person needs to learn the hard way, I'm sorry ignorance should be painful.
Now, I wish I was being paid by Samsung, hell, I'd take a free WiThin, but alas I'm not, I actually came over from the EVO because I had too many issues with it.
I'm one of the first people to call a company out for a poor product or poor service, in this case the issue arrived from neither, the issue was your own doing.
I made some of the same mistakes and semi-bricked my Epic, I was able to Odin it back to stock by reading how to on this forum, not by posting a thread bashing the Epic because I was too lazy, impatient and ignorant to educate myself.
gjones77 said:
... not by posting a thread bashing the Epic because I was too lazy, impatient and ignorant to educate myself.
Click to expand...
Click to collapse
Your quote above speaks volumes about yourself. You do not spend your time assisting others, instead insulting them, calling them names. Apparently this community should be in reverence to someone of your self-described qualities. I am not lazy, a bit impatient, and not ignorant. Perhaps I don't have your skills in searching through archives, but I think the skill you might want to focus on for yourself in the future concerns developing social skills. Why would you want to contribute or be a member of a forum when instead of assisting you decide to deride? I have had many issues with the Epic these past nine months, and God forbid a little bit of my frustration bubbled to the surface. I am about to leave this forum for good (thanking again those who did assist me), and so there will be one less person for you to insult.
This threads abit useless so I have a question.
How do u do Hard reset? My phone locked up once and I held idk what buttons for like 1min and it rebooted. But now idk what or how I did it =(
Sent from my Epix 4G using XDA
Shoulon said:
This threads abit useless so I have a question.
How do u do Hard reset? My phone locked up once and I held idk what buttons for like 1min and it rebooted. But now idk what or how I did it =(
Sent from my Epix 4G using XDA
Click to expand...
Click to collapse
Use Odin. The hard reset wont help /system/ corruption (TW, etc.). You have to odin or flash a rom at this point. Pull battery, hold 1 on keyboard and power, set up odin/heimdall on computer, plug in phone, flash using odin.
Sent from my SPH-D700 using XDA App
marcusant said:
Use Odin. The hard reset wont help /system/ corruption (TW, etc.). You have to odin or flash a rom at this point. Pull battery, hold 1 on keyboard and power, set up odin/heimdall on computer, plug in phone, flash using odin.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
soo... there are no reboot steps? like original non smartphones had? (Hold power til ur finger hurts?)
Shoulon said:
soo... there are no reboot steps? like original non smartphones had? (Hold power til ur finger hurts?)
Click to expand...
Click to collapse
Oh... on froyo its power, volume up and camera. On GB, there is nothing but a good old fashion battery pull.
Sent from my SPH-D700 using XDA App
never mind
poit said:
never mind
Click to expand...
Click to collapse
believe me i know how you feel... =/
you get thanks cause iknow you tried. =)
idea for ya
drplaud said:
Hello friends,
For reasons I do not even want to bother to understand, as I am on the waiting list for the Evo 3D and will never again buy any Samsung product, though I would like to have at least basic mobile phone capabilities until the end of June, my Epic has died. It got to the point I would have to remove the battery every 10 minutes and restart. I would get all these Touchwiz errors. So I decided to hard reset, at least so I could have a phone. I'll reinstall apps when I get my Evo 3D. So I removed the SD card, and went to Settings-Security and initiated a hard reset. That was four hours ago and the SAMSUNG logo is appearing as when you restart the device, and staying put. Is the hard reset this long? What should I do? This phone, which I've had since last fall, has been the worst experience of my life, and that doesn't even count the Froyo fiasco of a few months ago. Good riddance to Samsung. I bought a Moto Xoom, which has worked flawlessly over the past month on Honeycomb. It's nice to know that there are some Android devices that don't cause so much pain and suffering that you want to scream as does this horrid Samsung phone. But I need a phone for the next 2 and a half weeks before the Evo 3D makes an appearance, so I would dearly love to know what to do at this point! Thanks in advance.
Click to expand...
Click to collapse
later man hope the evo treats you better
I was running Core Droid 1.2. I WASNT flashing a rom, I WASNT flashing anything or messing with anything. I was just watching a youtube video. The phone froze. I didnt want to remove the battery as i thought it was bad. I tried finding a way to emergency shutdown my phone like volume up and down and power or something but it seems there wasnt one. I took out the battery and put it back in. I turned the phone on but all that came up was a black screen. I took it out and put it back in again. It won't turn on period.
Any ideas?
tradejak66 said:
I was running Core Droid 1.2. I WASNT flashing a rom, I WASNT flashing anything or messing with anything. I was just watching a youtube video. The phone froze. I didnt want to remove the battery as i thought it was bad. I tried finding a way to emergency shutdown my phone like volume up and down and power or something but it seems there wasnt one. I took out the battery and put it back in. I turned the phone on but all that came up was a black screen. I took it out and put it back in again. It won't turn on period.
Any ideas?
Click to expand...
Click to collapse
Read my sticky in the general section
Sent from my Infernalized Glacier!
-Team Inferno
saranhai said:
Read my sticky in the general section
Sent from my Infernalized Glacier!
-Team Inferno
Click to expand...
Click to collapse
Yeah I did. And its funny cause when i read it 2 days ago I got scared that my bad eMMC chip would die any second... now it looks like it just did.
I just posted this anyways cause I was desperate >.> but t-mobile says my warranty hasnt run out yet. And since it cant boot up whatsoever they cant tell its rooted. SO I get a free replacement
I was kind of hoping they'd claim the phone was defective and give me a sensation or something
This doesn't look like eMMC failure at all.
Jack_R1 said:
This doesn't look like eMMC failure at all.
Click to expand...
Click to collapse
what would you think it is then? My new phone comes today and i have to ship this one off to tmobile, so its too late. But I still want to know
Most likely - corrupted SBL. It doesn't necessarily mean eMMC failure - though it could be. Pulling the battery out while there is some eMMC activity could have caused it.
sorry im nooby. whats SBL and can it be fixed easily?
SBL is Secondary Bootloader, in our case also known as HBOOT.
Once it was corrupted, it can't be fixed, since the phone won't boot to any state that allows you to work with it.
Jack_R1 said:
SBL is Secondary Bootloader, in our case also known as HBOOT.
Once it was corrupted, it can't be fixed, since the phone won't boot to any state that allows you to work with it.
Click to expand...
Click to collapse
I don't think that was it. He obviously could get to HBOOT by flashing PD15IMG.zip and getting failed-pu error. But I may be wrong, feel free to correct.
To flash PD15IMG, he needs HBOOT running - it's the HBOOT that flashes these files, it's the first screen on your phone that you can actually see and interact with. If HBOOT is gone, you don't boot - because you have nothing to boot to. Or actually, the phone boots to some state, but you don't know it - because you can't interact with it anymore.
invasion2 said:
I don't think that was it. He obviously could get to HBOOT by flashing PD15IMG.zip and getting failed-pu error. But I may be wrong, feel free to correct.
Click to expand...
Click to collapse
Nope. I cant flash PD15 if i cant get to HBOOT. the phone doesnt turn on at all, just a backlight for one second. Which looks like its attempting to turn on but failing.
Jack_R1 said:
SBL is Secondary Bootloader, in our case also known as HBOOT.
Once it was corrupted, it can't be fixed, since the phone won't boot to any state that allows you to work with it.
Click to expand...
Click to collapse
hmm. you'd think these phones would have some sort of fail-safe feature when it comes to pulling the battery, cause people obviously do it alot.
tradejak66 said:
Nope. I cant flash PD15 if i cant get to HBOOT. the phone doesnt turn on at all, just a backlight for one second. Which looks like its attempting to turn on but failing.
Click to expand...
Click to collapse
Ahhh my bad, sorry. Didn't read Definitely seems like you are bricked! >.<
No, I'm not crazy! I'm actually attempting to use a home made program to see if I can unbrick it. Does anyone know how I could do this? Thanks!
Don't know sorry but it's so fun
We spend so much time to avoid that happen ...
Sent with my GT-P7500 CM10
corybantic said:
No, I'm not crazy! I'm actually attempting to use a home made program to see if I can unbrick it. Does anyone know how I could do this? Thanks!
Click to expand...
Click to collapse
Try flashing recovery in odin and disconnect it in the middle
...
Flash a rom with odin and use repartition.
This will brick your device.
Sent from my GT-P7500 using XDA Premium HD app
Flash a rom from another device works, too.
corybantic said:
No, I'm not crazy! I'm actually attempting to use a home made program to see if I can unbrick it. Does anyone know how I could do this? Thanks!
Click to expand...
Click to collapse
Well, the other ones pretty much covered your query. I want to ask what happens if your program fails? And you mean soft or hard brick?
Sent from my amazing 10.1 galaxy tab
Like all the folks before me, flashing wrong rom from other device probably would brick it... BUT to really, really brick it messing up the bootloader is always a good way to go.
Can you short it out?
Ooops,I guess I should've been clearer! I'm trying to brick it without rooting it, i.e., perhaps some code that I could input at the bootloader?
Panos_dm said:
Well, the other ones pretty much covered your query. I want to ask what happens if your program fails? And you mean soft or hard brick?
Sent from my amazing 10.1 galaxy tab
Click to expand...
Click to collapse
Well if it fails, then I guess I gotta try - or come up with - a different program. The thing is, I had two SGT 10.1, one recently went back to Best Buy after the ICS update started freezing up my internet (not tripping tho, I was able to get a raincheck for the Note 10.1! Good thing I got the Product Replacement Plan!: victory, so I have literally a spare SGT 10.1 to mess around with. I've already rooted it and flashed different roms as well as unrooted it back to factory settings. So, to be honest, I simply have a tablet for having a tablet's sake right now.
I'm actually trying to "hard" brick it. The thing is my little program works on a "soft" brick palette so it has (usually) been able to unbrick an inadvertantly bricked phone as well as the SGT 10.1. I'm trying to see if I can brick it without rooting it to see if I can resuscitate it back to working condition.
"hard"brick it means you'd have to produce an hardware faillure, You wouldn't be able to fix an hardware failure unless you change the part that failed.
IE: Your memory chip has fried, your CPU overheated FUBAR, this kinda things
Well mine is pretty screwed. Wish I knew how it happened so I can tell you, but I don't. Yesterday I watched a movie on it and put it on the table. Later when I wanted to use it, nothing happens.
If I plug it into my PC I can get it into APX mode, but thats all. The backlight doesn't even go on. On NVflash I get the rcm version = 0x4, which means I got a locked bootloader.
When on charge, also nothing happens. The camera flash just flashed about every 2 seconds. Same thing when I keep the power button held in.
I could try your app for you on mine if you want...