Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

Formated internal sd. No recovery, no adb, no flashtool, no dl-mode

OP android404

11th April 2014, 04:03 PM   |  #1  
android404's Avatar
OP Senior Member
Oslo
Thanks Meter: 482
 
778 posts
Join Date:Joined: Jan 2013
I messed it up ultimately. I wanted to repartition the external sd using "aparted", instead I formated and repartitioned the internal one.

My situation now: tab doesn't boot into system, doesn't show in adb, doesn't show in flashtool (offline or online), doesn't boot to recovery, doesn't boot to download and doesn't show in windows. There's only one sign of life: when I plug it into a usb cable which is attached to my PC I get the windows "connect sound". And I get the disconnect/connect sounds when turning it off while attached to PC.

I assume that I can throw away my tab. If you know better, don't be afraid to tell me!
11th April 2014, 05:21 PM   |  #2  
sleekmason's Avatar
Senior Member
Flag Fayetteville
Thanks Meter: 218
 
449 posts
Join Date:Joined: Dec 2013
Quote:
Originally Posted by android404

I messed it up ultimately. I wanted to repartition the external sd using "aparted", instead I formated and repartitioned the internal one.

My situation now: tab doesn't boot into system, doesn't show in adb, doesn't show in flashtool (offline or online), doesn't boot to recovery, doesn't boot to download and doesn't show in windows. There's only one sign of life: when I plug it into a usb cable which is attached to my PC I get the windows "connect sound". And I get the disconnect/connect sounds when turning it off while attached to PC.

I assume that I can throw away my tab. If you know better, don't be afraid to tell me!

Ouch.

You've tried all the button combos?

You could try the warranty... If they can't get into it either, then it probably won't matter if your rooted or not.
The Following User Says Thank You to sleekmason For This Useful Post: [ View ]
11th April 2014, 08:53 PM   |  #3  
id10terror's Avatar
Senior Member
Thanks Meter: 527
 
302 posts
Join Date:Joined: Nov 2010
More
Quote:
Originally Posted by android404

I messed it up ultimately. I wanted to repartition the external sd using "aparted", instead I formated and repartitioned the internal one.

My situation now: tab doesn't boot into system, doesn't show in adb, doesn't show in flashtool (offline or online), doesn't boot to recovery, doesn't boot to download and doesn't show in windows. There's only one sign of life: when I plug it into a usb cable which is attached to my PC I get the windows "connect sound". And I get the disconnect/connect sounds when turning it off while attached to PC.

I assume that I can throw away my tab. If you know better, don't be afraid to tell me!

When you connect to computer do you see any devices in Device Manager?
The Following User Says Thank You to id10terror For This Useful Post: [ View ]
11th April 2014, 10:07 PM   |  #4  
Senior Member
Thanks Meter: 6
 
124 posts
Join Date:Joined: May 2013
You should still be able to get into download mode and use "upgrade recovery" in lg mobile tool.
The Following User Says Thank You to Qefx For This Useful Post: [ View ]
11th April 2014, 10:49 PM   |  #5  
android404's Avatar
OP Senior Member
Oslo
Thanks Meter: 482
 
778 posts
Join Date:Joined: Jan 2013
Quote:
Originally Posted by id10terror

When you connect to computer do you see any devices in Device Manager?

Hi. Actually, it does appear here, as qhsusb_dload. That must be a good sign..?
11th April 2014, 11:18 PM   |  #6  
id10terror's Avatar
Senior Member
Thanks Meter: 527
 
302 posts
Join Date:Joined: Nov 2010
More
Quote:
Originally Posted by android404

Hi. Actually, it does appear here, as qhsusb_dload. That must be a good sign..?

Good sign, yes, but will probably be difficult to recover from, might be better off just doing a warranty replacement.

Another option is to use a current version of Ubuntu or similar linux distro to see if you can access partitions from there. I remember something similar on a buddy's HTC phone a couple years back and was able to get him back up and running, so might be a similar issue here.
The Following User Says Thank You to id10terror For This Useful Post: [ View ]
12th April 2014, 12:17 AM   |  #7  
android404's Avatar
OP Senior Member
Oslo
Thanks Meter: 482
 
778 posts
Join Date:Joined: Jan 2013
Quote:
Originally Posted by id10terror

Good sign, yes, but will probably be difficult to recover from, might be better off just doing a warranty replacement.

Another option is to use a current version of Ubuntu or similar linux distro to see if you can access partitions from there. I remember something similar on a buddy's HTC phone a couple years back and was able to get him back up and running, so might be a similar issue here.

Ok. I installed a virtual ubuntu and after work tomorrow i'll follow this http://forum.xda-developers.com/show....php?t=2582142 thread to see if it shows me anything. If so I might need halp to find the proper images to push. I found some other potenitally helpful stuff when googling qhsusb_dload. I'll see what where it takes me tomorrow. A replacement is kind of hard to get here in Norway afer my experience.

Thanks for now!
The Following User Says Thank You to android404 For This Useful Post: [ View ]
12th April 2014, 12:59 AM   |  #8  
id10terror's Avatar
Senior Member
Thanks Meter: 527
 
302 posts
Join Date:Joined: Nov 2010
More
Quote:
Originally Posted by android404

Ok. I installed a virtual ubuntu and after work tomorrow i'll follow this http://forum.xda-developers.com/show....php?t=2582142 thread to see if it shows me anything. If so I might need halp to find the proper images to push. I found some other potenitally helpful stuff when googling qhsusb_dload. I'll see what where it takes me tomorrow. A replacement is kind of hard to get here in Norway afer my experience.

Thanks for now!

Good find! If that works out for you, maybe you can do a How To incase anyone encounters the same issue down the road.

Let me know if you need any partitions, although you should be able to grab most of them from any of my flashable zips. Just get them from the flash folder in the zip.

Good luck and godspeed!
The Following User Says Thank You to id10terror For This Useful Post: [ View ]
14th April 2014, 06:23 PM   |  #9  
Junior Member
Thanks Meter: 2
 
28 posts
Join Date:Joined: Aug 2007
Quote:
Originally Posted by id10terror

Good find! If that works out for you, maybe you can do a How To incase anyone encounters the same issue down the road.

Let me know if you need any partitions, although you should be able to grab most of them from any of my flashable zips. Just get them from the flash folder in the zip.

Good luck and godspeed!

I think that will not work.
qhsusb_bulk is different from qhsusb_dload.
Newer qualcomm SOC has some "rescue" modes to recover fom bad flash. If the internal flash/eMMC canīt be accessed the SOC "bootROM" activates the qhsusb_dload mode. To get the device to "live" again is needed to use a qualcomm program to flash a qhsusb_bulk "driver" to the internal eMMC to activate the mass storage device...
There is a Korean Note2 qhsusb_dload topic about this here on xda... http://forum.xda-developers.com/show....php?t=1914359
The problem is find the correct flasher binary to upload to the SOC, the right "driver" to flash and the correct partition layout of the internal flash/eMMC.

Itīs better send to warranty replace...
Last edited by sfortier; 14th April 2014 at 06:29 PM.

The Following User Says Thank You to sfortier For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes