Related
Hi Guys,
I'm guessing that there's nothing that can be done but last hope!
Last night i was trying to update my Gf's Optimus One with little success using KDZ, got to the point where it wouldnt boot, so flashed the original ROM back to it, during the process after a few minutes it gave an error code and the Flash was unsuccessful. Thought' id' reboot the phone into Emergency and try the flash again - it errored pretty much straight away - Pulled battery from phone - reinserted it and now nothing!
The phone will not respond to power on, USB insert, etc Just completely dead..
Im guessing i know the answer already - but is there anything that can bring this back from the dead.... Seriously in the Doghouse!
Cheers
Paul
This is Dev section , please post in general section !!
Sent from my LG-P500
Sorry - Can a mod please move this to the correct place.
Don't u have warranty???
Sent from my LG-P500 using Tapatalk
I bricked my phone the same way.
I was trying to flash the original russian Gingerbread with LGMDP and there was a cable connection problem... I chose to erase all data before flashing (EFS Erase ALL). If only mobile devices had BIOS...
No hope, unfortunately. You have to connect your chipset to a computer and manually write all data... Or send to LG Service Center. Just hope they'll fix it for free... (They can't detect how you wiped device's boot loader if all the flash memory is empty)
paulrgod said:
Hi Guys,
I'm guessing that there's nothing that can be done but last hope!
Last night i was trying to update my Gf's Optimus One with little success using KDZ, got to the point where it wouldnt boot, so flashed the original ROM back to it, during the process after a few minutes it gave an error code and the Flash was unsuccessful. Thought' id' reboot the phone into Emergency and try the flash again - it errored pretty much straight away - Pulled battery from phone - reinserted it and now nothing!
The phone will not respond to power on, USB insert, etc Just completely dead..
Im guessing i know the answer already - but is there anything that can bring this back from the dead.... Seriously in the Doghouse!
Cheers
Paul
Click to expand...
Click to collapse
read downgrading details along with error thread it will definately come back to life http://forum.xda-developers.com/showthread.php?t=1038338
http://forum.xda-developers.com/showthread.php?t=883314
shhbz said:
read downgrading details along with error thread it will definately come back to life http://forum.xda-developers.com/showthread.php?t=1038338
http://forum.xda-developers.com/showthread.php?t=883314
Click to expand...
Click to collapse
Thanks for the links - i was working my way through the second one at 3am this morning.. Yes - i've even tried Shaking it
The P500 community has produced some wonderful guides and looking at it seems like the device is almost impossible to Brick completely, just how this happened i havn't a clue, seems ive managed the almost impossible..
I'd more than likely be able to ressurect it if it responded to anything at all - but no power, and nothing when the USB is inserted, no vibration, no lights, no signs of life...
the phone may be under warranty, but ive got to dig out the reciept - and i cant even begin to think where that is..
Well anyway i've had to buy her a replacement today - ended up with a Samsung Galaxy Mini as they dont stock the Optimus one anymore. Closest thing i could find.
Cheers for the help guys - i guess next effort will be warranty repair.
dude pls try uninstallin all the lg drivers usb etc etc and then try it again...it happend to me but ive still managed to ressurect it so try this and after send it to warranty
Hi!
I just had the weirdest experience with my sgsii
I have been using the unofficial vsync patched cm10 rom for this modelfor the last month or so.
I have been updating at least one per week but this week I decided to give my phone a break and not flash it... i am actually really busy at job.
Suddenly tonight, the phone looked like when you have a SOD... so i just pulled the battery.
Now, it does not pass from the first logo stage, just prior to start booting.
I cannot access cwm recovery either, but download mode seems to work-
Now the odd thng is that i am attempting to flash somethng to get the phone working but it gets stuck in the step "NAND Write start!".... it goes no furter than that...
I have chosen the options auto reboot and f.reset time.
a pda file, phone and csc file from the eaked jb rom.....
The system I am attempting to flash from is a windows 7 pro 64 bit.... and odin is Odin3 v1.85...
Please, tell me i didnt get a brick and there is a way tofix it... :crying:
EDIT: Desperated, i tried to flash latest jb leak again, and chose the pit file that comes with it, which re-partitions the phone...
After 20 minutes not responding, i pulld the battery out... now i cannot even enter download mode....nothing....nada....
Sounds like you bricked it, good job.
Sent from my GT-I9100 using Forum Runner
GFXi0N said:
EDIT: Desperated, i tried to flash latest jb leak again, and chose the pit file that comes with it, which re-partitions the phone...
After 20 minutes not responding, i pulld the battery out... now i cannot even enter download mode....nothing....nada....
Click to expand...
Click to collapse
too bad never repartition unless you make your own pit file with heimdall .. if you would've wait a couple hours I just pmed you.
and for other people instead of flashing samsung's bricksquadroms you can flash CM9 resurrection edition. http://forum.xda-developers.com/showthread.php?t=1419102
Make a pit file with heimdall of your own device. Don't trust pitfile that comes with a rom.
I re-partitioned my device and i got like 3GB intern memory back.
There's probably a way to get your device alive. it isn't the mmc cap bug so. search some threads on xda about brickbugs etc of galaxy phones and you'll find people who hardbricked and unbricked their device.
Probably usb jig could get you into download mode i'm not sure though. Or else jtag. Ask some people over there they will know it
I will try to revive it with jig.... i must find the thingy though.,..... if not.. i will send it to the service but i'm not sure i'm on warranty....
Being not patient made me f*ck it up bad....
Any clue on how to recover a phone after re-partitioning.... i really don't know where to start...
EDIT: JIG does not switch it on either... why did i have to re-partition?!??!?!?!?!?!
That was a dumb move....... any more ideas?
If you cant enter recovery or download mode you have no choice but to JTAG repair or mobo replacement.
Hard brick.... on its way to service
Wish me luck..
Mobo replacement it is, this incident will at least teach you to be patient, I explained you my problem in PM, I waited for 1 week for USB jig to arrive from eBay then flashed stock ROM. I trust the f/w it came with the most.
Sent from my GT-I9100 using xda app-developers app
Sh4Dy said:
Mobo replacement it is, this incident will at least teach you to be patient, I explained you my problem in PM, I waited for 1 week for USB jig to arrive from eBay then flashed stock ROM. I trust the f/w it came with the most.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
USB JIG didn't work at all..... I have one and it was not able to boot the phone ....
Isn't this kind of brick fixable with Jtag?
Sent from my GT-I9100
Ok, before I repartitioned, making the problem worse, I was experiencing some kind of R/W problem..... there was something odd with the nand because I was able to boot in download mode, but not in recovery (CWM) mode....
Then, when I plugged the phone to the computer, Odin was able to recognize the phone.
I followed some thread around XDA to flash 4.1.2 leak from sammy and when I hit the "Start" button in Odin, it would not pass from the first stages, revealing that R/W or I/O problem.... the internal nand was, somehow broken.... it didn't read or write properly.... so, even If i could find a workaround, I would have lost some internal storage (some posts talk about around 3 Gb or something similar as lost space in these cases).... that is IF i had been able to fix it..... but then, that's what warranty is for..... so I gave it a last (dumb) try..... including the pit file, which attempted a format, which ended messing (i would say the f. word) everything up.
The good side is that unable to even boot, at least i lost the blue loading bar the vsync patched cm10 mod has in the first bootup screen.... which could have revealed to sammy that I was tempering with unofficial roms....
Lesson learned: Be patient people: But also, don't think this could not happen to you: The phone was perfectly working the last time I saw it... and I even was making some phone calls and browsing the internet.... I mean... it gave no prior symptoms or warnings... I t just died..... I guess I have to be glad I'm not one of those people whose phone gets caught up on fire on their pockets for malfunctioning.....
Now waiting for it to come back revived from samsung..... I have hope
hope it will be able to recover
Great: After losing the phone and past almost three months, samsung says the phone has been manipulated and the warranty is voided....
I wasn't able to flash back an original firmware prior to sending it to the tech service.....
What do you recommend me to do?
I guess paying for the repair would be quite expensive....
GFXi0N said:
Great: After losing the phone and past almost three months, samsung says the phone has been manipulated and the warranty is voided....
I wasn't able to flash back an original firmware prior to sending it to the tech service.....
What do you recommend me to do?
I guess paying for the repair would be quite expensive....
Click to expand...
Click to collapse
Well what is it you expect us to say, some secret magic word that will fix it for free?
The choice is pay for it to be fixed or dont.
So no magic word or secret passphrase so they will upgrade my device to a SGSIV for free?
Damn.....
I'm asking for advice, since I'm convinced the brick was not caused by flashing anything.....
Does anyone have any experience with this in the past to know more or less how expensive bill could I be facing for the repair?
GFXi0N said:
So no magic word or secret passphrase so they will upgrade my device to a SGSIV for free?
Damn.....
I'm asking for advice, since I'm convinced the brick was not caused by flashing anything.....
Does anyone have any experience with this in the past to know more or less how expensive bill could I be facing for the repair?
Click to expand...
Click to collapse
Dude, it WAS caused by flashing something.
Initially your device wasn't "bricked" and was likely a kernel issue and possibly a dirty usb data connection.
The point when it was bricked was when you tried flashing the pit file, had bad connection and you then pulling battery. This f**ked your nand chip up and only way to fix it is to replace motherboard.
You will need to either purchase a mobo replacement and replace it yourself or pay somebody to purchase/replace it for you. Probably looking at around £100.
When bricks happen, you really need to BRICK it before claiming warranty.
I've got a couple of guys here that own a PhD in bricking.
Brick is the new flash.
Sent from the little guy
Jig wasn't working
Flashing anyting.. even just a recovery wasn't working
FLashing official didnt work
Flashing CM didnt work either
Tested different cables and different ports
It was f*cked up already... anyway: 4 samsung devices owned: 3 gave problems of hardware..... that cannot be a coincidence...
Repartitioning erased my tracks, if anything... because the 3 key combo for recovery was working until then..... but either way they managed to access the memory somehow, I guess.....
GFXi0N said:
anyway: 4 samsung devices owned: 3 gave problems of hardware..... that cannot be a coincidence....
Click to expand...
Click to collapse
Maybe a PEBCAK?
GFXi0N said:
Jig wasn't working
Flashing anyting.. even just a recovery wasn't working
FLashing official didnt work
Flashing CM didnt work either
Tested different cables and different ports
It was f*cked up already... anyway: 4 samsung devices owned: 3 gave problems of hardware..... that cannot be a coincidence...
Repartitioning erased my tracks, if anything... because the 3 key combo for recovery was working until then..... but either way they managed to access the memory somehow, I guess.....
Click to expand...
Click to collapse
Don't blame the phone, blame the user.
Yeah, sure... anyway... thanks for the help... I hope some day you need it and someone will come not trying to mocking you..... anyway... this is the trend around here lately...
Happy trolling
Hi everyone, I think I just bricked my device. I got my new e970 with 4.04 yesterday and today when trying to flash the new 4.1.2 using lgnpst tool, the process halted at 85% giving out an error stating that the firmware isn't supported. When I unplugged the phone and tried to boot, nothing happened. I am assuming that it's bricked.
Additional info:
When I hold the power button for 30 secs while connected via usb, the red led flashes for 2-3 secs and the PC makes a sound as if it had detected a new hardware (but nothing happens though )
On opening the device manager, I was able to see a "Qualcom HS-USB QDLoader" under the ports tab. And the "usual unknown" device offcourse.
The device wasn't rooted or bootloader unlocked
PS: I have tried to enter the download mode. But it didn't work either.
Help of any kind is welcome
I am sorry to tell you that is a hard brick. It needs to be jtagged, search for Mobiletechvideos.com
Andromann said:
Hi everyone, I think I just bricked my device. I got my new e970 with 4.04 yesterday and today when trying to flash the new 4.1.2 using lgnpst tool, the process halted at 85% giving out an error stating that the firmware isn't supported. When I unplugged the phone and tried to boot, nothing happened. I am assuming that it's bricked.
Additional info:
When I hold the power button for 30 secs while connected via usb, the red led flashes for 2-3 secs and the PC makes a sound as if it had detected a new hardware (but nothing happens though )
On opening the device manager, I was able to see a "Qualcom HS-USB QDLoader" under the ports tab. And the "usual unknown" device offcourse.
The device wasn't rooted or bootloader unlocked
PS: I have tried to enter the download mode. But it didn't work either.
Help of any kind is welcome
Click to expand...
Click to collapse
If you really just got it brand new, just take it back, tell them it was working then just completely stopped.
Next time let the firmware update over the air, personal recommendation
Then freegee yourself, and you may never have to see LGNPST ever. (I've never used it so, here's hoping)
Also, if the OTA update isn't showing up, call AT&T and tell them to push the update, they will.
[r.]GimP said:
If you really just got it brand new, just take it back, tell them it was working then just completely stopped.
Next time let the firmware update over the air, personal recommendation
Then freegee yourself, and you may never have to see LGNPST ever. (I've never used it so, here's hoping)
Also, if the OTA update isn't showing up, call AT&T and tell them to push the update, they will.
Click to expand...
Click to collapse
I think he is in India.
Thanks for your reply guys. @adfurgerson That's correct. India it is. And I've checked the options available for JTAG ing the phone, but there are no reliable people here. @[r.]GimP lol, I don't think LG would be that trusting to believe that the bootloader self destructed by itself. But thanks anyways, that'll be my last resort if I can't get it to run.
Right now, I am looking at these
http://forum.xda-developers.com/showthread.php?t=2208289&nocache=1
http://forum.cyanogenmod.com/topic/71825-hard-brick-to-hell-and-back-guide-to-recovery
to get into the download mode. I'll keep this thread posted with any kind of progress I make
http://forum.xda-developers.com/showthread.php?t=2330488
Relevant thread.
adfurgerson said:
http://forum.xda-developers.com/showthread.php?t=2330488
Relevant thread.
Click to expand...
Click to collapse
Thanks for the info. I saw the thread. But, ultimately the success story ended with JTAG ing. I hope it won't to be the case with mine.
http://webchat.freenode.net/?channels=lg-optimus-g
Link to irc.
adfurgerson said:
http://webchat.freenode.net/?channels=lg-optimus-g
Link to irc.
Click to expand...
Click to collapse
Wow, thanks. I never knew I could find devs in irc. Awesome. I am not giving up on this lovely brick (for now) without a fight!!
http://forum.xda-developers.com/showthread.php?t=2208289
Another link.
adfurgerson said:
http://forum.xda-developers.com/showthread.php?t=2208289
Another link.
Click to expand...
Click to collapse
One of the first threads where I went to search desperately for help
JTagging did the trick!
Hello everyone, I just thought of sharing my experience resurrecting my hard bricked ATT LG Optimus G. After various desperate attempts to recover the device without opening it, I was left with no choice but to send it for JTagging. Amid safety concerns, I sent the phone for repair at a local store in Chennai and amazingly, the phone got back in brand new, fully working condition!! The servicing cost just 1500 Rupees and took 6 hours. If anyone wants information about the store, you can PM me.
Hi there!
This thread is my last hope, so please dont let me down folks...:cyclops:
The story short - one sunny morning i turned on my HTC Nexus One and it got stuck with te X on the screen for about 15 minutes, non of the buttons responded, so i did the first thing that came in my mind - i pulled out the battery. After inserting the battery the phone went full brick, i mean literally, no reaction on anything, even conected to the wall charger, there is no sign of life, no charging LED, nothing. Connected to the PC, it says USB device not recognised.
I dont think this is a hardware proble, the phone workwd fine until this interrupted power on. Phone runned on stock Androud, i have not played aroun with it - no bootloader unlock, no rooting.
I searched the internet for a solution, tried a lot of button combinations like in this thread:
http://forum.xda-developers.com/showthread.php?t=1069032
but still no luck, i cannot restore or flash it while my PC does not recognise the phone.
Found some info about those Usb Jig things, but they work only on Samsung phones, so, is there a way to force the phone to go in recovery mode, or give any sign of life so i can try to recover it or flash a diferent ROM?
The warranty has ended, so no hope there.
Hope there is a way out of this, and, sory for my bad english. :good:
Veesais said:
Hi there!
This thread is my last hope, so please dont let me down folks...:cyclops:
The story short - one sunny morning i turned on my HTC Nexus One and it got stuck with te X on the screen for about 15 minutes, non of the buttons responded, so i did the first thing that came in my mind - i pulled out the battery. After inserting the battery the phone went full brick, i mean literally, no reaction on anything, even conected to the wall charger, there is no sign of life, no charging LED, nothing. Connected to the PC, it says USB device not recognised.
I dont think this is a hardware proble, the phone workwd fine until this interrupted power on. Phone runned on stock Androud, i have not played aroun with it - no bootloader unlock, no rooting.
I searched the internet for a solution, tried a lot of button combinations like in this thread:
http://forum.xda-developers.com/showthread.php?t=1069032
but still no luck, i cannot restore or flash it while my PC does not recognise the phone.
Found some info about those Usb Jig things, but they work only on Samsung phones, so, is there a way to force the phone to go in recovery mode, or give any sign of life so i can try to recover it or flash a diferent ROM?
The warranty has ended, so no hope there.
Hope there is a way out of this, and, sory for my bad english. :good:
Click to expand...
Click to collapse
Well no, bricked is a term used when you are rooted and flash a bad rom,kernel,etc. You have no root, so you cannot be "bricked". Just a software failure, you cannot flash another rom because, again, you have no root or custom recovery. Your best bet is trying to send it back to your carrier and get it replaced
ParanoidKang said:
Well no, bricked is a term used when you are rooted and flash a bad rom,kernel,etc. You have no root, so you cannot be "bricked". Just a software failure, you cannot flash another rom because, again, you have no root or custom recovery. Your best bet is trying to send it back to your carrier and get it replaced
Click to expand...
Click to collapse
The warranty time is out, so there is no help from the carrier, unless for cash...
But there must be a way to bring it back to life.
Veesais said:
The warranty time is out, so there is no help from the carrier, unless for cash...
But there must be a way to bring it back to life.
Click to expand...
Click to collapse
Now the screen may not show, but try booting into fastboot mode by press and hold the Trackball+Power buttons together.
I'm not sure about the nexus one, but newer nexus devices have factory images, supplied by Google. If they exist for the nexus one, you should be able to save your device by flashing them through fastboot. That is if the images exist and you can get to fastboot.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Hey guys !
Well...
Yesterday, I decided to flash a new ROM on my aunt's SII...
It wasn't the first time I did this : my own phones have all been flashed, I know how it works !
But... I got a problem ! While I was wiping the data/cache, the phone got stuck on this step. Then, shut down. And now, it doesn't boot anymore. Screen stays black. I did everything I found on the web : tried to boot on recovery and on download mode, tried to press the buttons to get into these modes and inserting the battery while pressing, tried to connect it on USB (not even detected)...
After some researches, I found out that it was a eMMC problem...
Anyway, in a nutshell, my phone is hard bricked. What can I do ?
Thanks.
rohecla said:
Hey guys !
Well...
Yesterday, I decided to flash a new ROM on my aunt's SII...
It wasn't the first time I did this : my own phones have all been flashed, I know how it works !
But... I got a problem ! While I was wiping the data/cache, the phone got stuck on this step. Then, shut down. And now, it doesn't boot anymore. Screen stays black. I did everything I found on the web : tried to boot on recovery and on download mode, tried to press the buttons to get into these modes and inserting the battery while pressing, tried to connect it on USB (not even detected)...
After some researches, I found out that it was a eMMC problem...
Anyway, in a nutshell, my phone is hard bricked. What can I do ?
Thanks.
Click to expand...
Click to collapse
what stock firmware version was the Phone when u did the wipe from recovery (if it was on ICS 4.0.4 then ur phone will be bricked because of the kernel of ICS4.0.4 being plagued with the 'EMMMC' brick bug and only a JTAG or a MB replacement is the solution for it) .
JTAG won't work; motherboard replacement or bin.
I think it was 4.0.4...
Motherboard replacement is the only thing I can do ?
Mate.... Samsung KNOWS this is a problem.......I'd try for warranty repair/replacement.....if the phone is less than two years old, you have a good chance......
Just remember to 'act dumb' at the service center..... Tell them you were trying to use kies to update from ICS and the phone died...... If it is the emmc brickbug, there's NO WAY they can check what os was on ur phone or whether you'd rooted or modified it in any way.....right now it's an unrecoverable (expensive) paperweight........
This might be my S2, or it might be my W...but it's definitely CM
Yeah, I saw this is a quite common problem... But often, it's just a soft brick. In my case, it's a hard brick...
And warranty expired two months ago...
Well, it's unlikely to succeed, but you could try emailing Samsung explaining your situation regarding expired warranty and going on to explain that updating with kies is a 'normal' procedure and that it's that 'normal' Samsung provided procedure plus the 'unstable' OS version (having read on the internet about 4.0.4 brickbug) that have killed a phone that would otherwise be working today. Stress the point that the ICS firmware AND kies were both supplied by Samsung for official (end user) use on Samsung devices......see what they say.....can't hurt right?
This might be my S2, or it might be my W...but it's definitely CM
Yeah, they're going to honour an expired warranty. That happens all the time
Mb....I *did* say right at the start that it probably wouldn't work..... But what has he got to lose?
Lol.....they *might* be suffering from an excess of Xmas and new year goodwill.......
This might be my S2, or it might be my W...but it's definitely CM
I have twice super bricked my two SGS-2s.... EMMC bug is one hell of a pain in ass. You have to let go some SD card space, but u can revive you phone using the URL in my signature. I revived both my phones losing about a GB space in one and a couple GBs in other. Good Luck
alvinasnow said:
but u can revive you phone using the URL in my signature
Click to expand...
Click to collapse
People have said he needs a new motherboard.Do you know something they dont?.
S4 victim
The problem is that I can't flash anything ! The phone simply doesn't turn on ! No recovery mode, no download mode, nothing ! It doesn't even charge !
Yes try this link from alvinasnow
http://forum.xda-developers.com/showthread.php?t=1667886
So far as I know if you only connect your phone normally if it os charging then it already has some kind of connection with the pc I believe its adb.
But since you dont have warranty you can give it a shot to save money so just give it a try and read carefully. I was surprised when I got this phone, that samsung would make a big mistake like that its a just shame.
Edit: i dont know or you need jtag or riff and I will not test it cause I dont have a superbrick phone with mmc cap erase.
But just open device manager on the pc and connect the phone and see if there is a new device connected.
In my opinion my previous phone has one of the best options to make it unbrickable
It was nvflash but it sucked.nvidia wouldnt release sources.
Gooodluck with your phone
Sent from my GT-I9100 using Tapatalk
Which part of this phone needs a motherboard replacement are you lot having trouble comprehending ?
OK...For all the slow kids who keep posting to this thread (including the OP); this phone needs a new motherboard. No threads promising magical fixes are going to work, there is no other way to fix this.
Is this clear now or do I have to make another post in bolded caps to make it really clear ?
There is a SLIGHT chance that if a JTAG recovery house can boot a kernel via JTAG (I do not know if RIFFBox can do this or not), they can use the solution that the Kindle Fire community used. (This was a recent discovery 2-3 months ago)
The problem is, I have attempted to provide information on this solution to these JTAG houses with no response. I don't know if they can boot a modified kernel via JTAG or not.
Currently:
All Exynos4 devices that are Superbricked are unrecoverable, as Samsung refuses to provide any way to boot these from USB, and anyone who could develop a solution hasn't responded (since most dead devices are long gone at this point...)
All Qualcomm-based Samsungs that are Superbricked are hosed too
Kindle Fires that are Superbricked are recoverable as of 2-3 months ago thanks to some discoveries by Oranav that were used by Hashcode to develop a recovery solution. This solution can't be used on Samsung Exynos4 devices as it depends on the ability to boot the device from USB.
And folks...... @Entropy512 needs to be listened to.......he is the dev who has done the most research into this issue and (somebody cmiiw) was the one who discovered the "emmc cap erase" command was the culprit. I think he also wrote the original (much copied) 'got brickbug' app which tells you if your phone is affected or not. If what he says doesn't work, then as @MistahBungle says, the ONLY OTHER OPTION is a new motherboard........
This might be my S2, or it might be my W...but it's definitely CM
Well...
I think I'm just going to call the insurance, and see what they can do ! Even if my warranty is now void, they may replace the phone !
Thank you all !