Android Android experts on gbatemp? Has to be some here

[K3Nv2]

Well I managed to Hard brick my device, on windows it displays a black screen and keeps popping up format disk, theres like 0 information on this situation. In linux the screen blinks but keeps displays pop up volumes saying it can not be formatted.

Just hope to get some help here before it goes to lg tomorrow. Yes it was a rom install screw up but I think it's at the point where not even lg could tell that it's been rooted.

It's a lg g2 d900 btw.

 

[Rise]

Hi
Can you enter recovery or download mode ?
Have your tried flashing the stock rom ?

 

[K3Nv2]

No none of that works

 

[Rise]

ok, have you tried asking over at xda ? if they can`t help you, you need to have LG look at it

 

[Tom Bombadildo]

You've fucked it up too bad ken That's what you get for dicking with fastboot

 

[Bobbyloujo]

If you can't get into recovery or download mode then there isn't much you can do.

 

[stanleyopar2000]

go to XDA or Android Central for issues like this.

for predominately android based questions, especially advanced ones The "temp" is not really an ideal place to get your question answered. First off there is no information or anything or what phone you have. we need more details man. what happens when the phone starts up...when you boot to recovery? Download mode?

I happen to be a very active user in the XDA community however so I guess you're kinda right about some being on the site

my 2 cents is that though if you can't get into download mode to use LG Flash Tool you're fucked. As LG Flash Tools is the number one unbricking tool is the official way to unbrick your device, as is probably what LG will attempt to do first if you send it in. Due to the tool being LG Property they don't want any yay-hoo monkeying with it. You need to set your time back before july 2012 and use the cracked megalock.dll of course [which i'm not supplying for you]) or else you need a manufacture serial. Which I highly doubt you possess

 

[Foxi4]

Just a quick additional question (even though we've established that your phone is borked beyond home repair and requires a hardware flasher), did you install Google's USB driver (comes with the Android SDK)? Because you could try this:

1. Open CMD with Administrator's Privileges
2. cd X:\AndroidSDKFolder\sdk\platform-tools
3. Plug phone in
4. Hold Volume Down + Power button + Home, Windows may or may not detect your phone
5. If it does, go to the Command line and type in:

adb shell
start daemon
exit
adb reboot bootloader

If this doesn't help, nothing other than a hardware flasher will - you might as well get ready to send the phone to LG or a repair store with the right equipment that can re-flash it properly.

 

[Tom Bombadildo]

Just a quick additional question (even though we've established that your phone is borked beyond home repair and requires a hardware flasher), did you install Google's USB driver? Because you could try this:

1. Open CMD with Administrator's Privileges
2. cd X:\AndroidSDKFolder\sdk\platform-tools
3. Plug phone in
4. Hold Volume Down + Power button + Home, Windows may or may not detect your phone
5. If it does, go to the Command line and type in:

adb shell
 
start daemon
exit
adb reboot bootloader

If this doesn't help, nothing other than a hardware flasher will - you might as well get ready to send the phone to LG or a repair store with the right equipment that can re-flash it properly.

His LG phone doesn't have a home button. I assume you're trying to get him into download mode though, which we already tried, and for the LG G2 it's holding Volume Up while plugging a USB cable in to the phone (which is dumb as fuck).

It looks like he actually erased his bootloader with fastboot, which is I assume is why it's practically unrecoverable.

 

[Foxi4]

His LG phone doesn't have a home button. I assume you're trying to get him into download mode though, which we already tried, and for the LG G2 it's holding Volume Up while plugging a USB cable in to the phone (which is dumb as fuck).

It looks like he actually erased his bootloader with fastboot, which is I assume is why it's practically unrecoverable.

I was hoping that the debug bridge could wake it up, but as I said, I'm pretty sure only hardware flashing can save him, judging by our earlier shoutbox conversation.

 

[stanleyopar2000]

alright...more details...wtf did you do before this. tell us the last time it worked. what file did you flash..what ROM. tell us how the scene unfolded. How on earth did fastboot get erased?

 

[Tom Bombadildo]

alright...more details...wtf did you do before this. tell us the last time it worked. what file did you flash..what ROM. tell us how the scene unfolded

He was dicking around in fastboot for some stupid reason, he posted various commands he used yesterday in the Shitbox and it seems he erased the system partition, data, cache, and the bootloader. Hence why it can't boot anything.

As Foxi said above, there's nothing more that can be done without a hardware flasher, though kenenthk you could always try what Foxi posted above, see if that does anything at all just because.

 

[Sanoblue]

agreed stanleyopar. seems like there is more info to this.

 

[stanleyopar2000]

can someone find those commands he posted? I would like to know what commands did he do..i'm guessing they were done via ADB right?

 

[Sanoblue]

if adb is still active (doubt it) he could reflash fastboot and recovery with a program cable. but that requires he order / have / make one, as well as adb being active still long shot but doubt it

 

[Sanoblue]

double post sorry net wigged out on me

 

[Tom Bombadildo]

can someone find those commands he posted? I would like to know what commands did he do..i'm guessing they were done via ADB right?

Only staff have access to the shoutbox logs, so no.

And as I said, they were done via fastboost, not ADB. They're 2 completely different things.

if adb is still active (doubt it) he could reflash fastboot and recovery with a program cable. but that requires he order / have / make one, as well as adb being active still long shot but doubt it

Also, A) ADB is only present when Android is present. Because he deleted the system partition, there's no Android, hence no ADB. B) Fastboot itself is loaded before Android loads, since he can't access fastboot (probably because the bootloader was erased, so it doesn't have any way to boot into Download mode/fastboot mode) there's nothing he can do besides...as Foxi said, use a hardware flasher.

 

[stanleyopar2000]

I scowered the android forums and yeah...it's dead jim. only LG has the physical hardware flashing tools. Everyone who has had an issue that is synonymous with yours usually are getting results of "it's screwed", "send it back to LG", Don't root, blah blah blah...

pretty much it's over. And if the system, data, cache and partitions were erased LG is going to know it was monkey'd with

 

[Foxi4]

I scowered the android forums and yeah...it's dead jim. only LG has the physical hardware flashing tools. Everyone who has had an issue that is synonymous with yours usually are getting results of "it's screwed", "send it back to LG", Don't root, blah blah blah...

pretty much it's over. And if the system, data, cache and partitions were erased LG is going to know it was monkey'd with

I would argue that most stores that deal with this sort of thing can give it some soldering/flash clip love and C.P.R it to life, but it's gonna cost him. Not rooting is silly, rooting without knowing what you're doing is not recommended though.

 

[stanleyopar2000]

I would argue that most stores that deal with this sort of thing can give it some soldering/flash clip love and C.P.R it to life, but it's gonna cost him. Not rooting is silly, rooting without knowing what you're doing is not recommended though.

I was only quoting from other replies about a bricked G2 with no recovery or download mode. I didn't directly tell him to "not root"