Database Develop

Galaxy Tab bricked.. like really bricked

Ok guys, I feel this is just the end of the games... I was flashing back the Roto JME fw with the swype keyboard issue fixed that I have just made, when I accidentally unplugged the tab while starting flashing and in downloading mode.
Now all I get is a logo with a phone an alert symbol and a computer .
Windows as well as Odin see it, but I can't do anything, as Odin hangs on waiting for connection, or something like that.
Is there anything I can do?? Or do I really have to take it to the warranty? And if I will have to take it to the warranty will they see I have previously flashed a beta rooted image on it??
Here's what I am talking about
Please I need some help..
Thanks

Is there no recovery mode by buttons like the captivate? I hate seeing all the bricks
Sent from my SPH-P100 using XDA App

Its not bricked
heimdall close-pc-screen
should restart it
then power it off
then put it into download mode again using power + volume down
-d

Technomancer said:
Its not bricked
heimdall close-pc-screen
should restart it
then power it off
then put it into download mode again using power + volume down
-d
Click to expand...
Click to collapse
damn it says Failed to access device. Error: -12 .. I am on windows with latest version of heimdall ...

Segnale007 said:
damn it says Failed to access device. Error: -12 .. I am on windows with latest version of heimdall ...
Click to expand...
Click to collapse
Ops, it was the driver... damn windows ...
Solved btw.. I just realized I have lots of things to learn ... I have almost died of heart attack when I saw my tab stucked on that logo.. and now its back again..
Thank u falks

You need to make sure samsung kies are not running for sure unistall it and try it again

use odin. that is still download mode. might take you a couple of tries but works. i was in your shoes the other day

Everything is fixed thanks to Tecnomancer. Thank u guys
Sent from my GT-P1000 using XDA App

Could you please list the steps you went through in order to fix this - for everyone else's sake? Thx!
Segnale007 said:
Everything is fixed thanks to Tecnomancer. Thank u guys
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse

I've heard plenty of goofy stories about bricking devices over the years. You must conclude the following:
1.Flash your device in a locked room to avoid your wife/ child pulling cables or pressing buttons.
2.Don't touch anything while you're flashing. This is why many people that could help you will ignore you after reading about 'accidentally disconnected' wires - they just assume you're a moron not worth helping.
3.Read instructions carefully and write the procedure out in your own words if its your first time.
I've been flashing for years and haven't had a brick yet. Not crossing my fingers either because it has little to do with luck and much to do with care. In this way its a lot like making babies...

ftgg99 said:
2.Don't touch anything while you're flashing. This is why many people that could help you will ignore you after reading about 'accidentally disconnected' wires - they just assume you're a moron not worth helping.
Click to expand...
Click to collapse
Good advice.
My only semi-bricks (that involved an hour or two of trial and error to unbrick) resulted from some manner of overzealous cable unplugging.

zyborg said:
Could you please list the steps you went through in order to fix this - for everyone else's sake? Thx!
Click to expand...
Click to collapse
This is what I have done
Technomancer said:
Its not bricked
heimdall close-pc-screen
should restart it
then power it off
then put it into download mode again using power + volume down
-d
Click to expand...
Click to collapse

ftgg99 said:
2.Don't touch anything while you're flashing. This is why many people that could help you will ignore you after reading about 'accidentally disconnected' wires - they just assume you're a moron not worth helping.
Click to expand...
Click to collapse
Well, first of all thanks for ur nice words. Let me just say that I was about to disconnect another device from the hub where the GTAB was attached and flashing at that time, and yea, I accidentally unplugged the GTAB instead of the other device. I may be a moron, thanks, and thankfully not everyone believes themselves as god, which is a good reason to not help other people who are in troubles, even if for stupid things sometimes... If everyone were thinking like u we were probably still at the age of 1400 ...

Mate it wasn't a barb directed at you personally, but you weren't exactly careful were you?
I'm no god... but I've never bricked a device either, and I've been flashing for over five years now. To top it off I've almost never owned a device which could be taken back to the shop (90% of them come from other countries, not my local retailers). Perhaps this has taught me to be careful.
In any case, what I said holds true, and if you ask around I'm certain you find most will agree.

Dude, you have the best avatar! I can't keep my eyes away! Good luck, and don't worry about mistakes - that is one reason this forum exists.

Cannot start my Gtab after trying update JMC
...Hello everybody,
I am really worry about the fact my Gtab doesn't want to switch on after trying to flash it. I tried all process to put it on download mode or recovery but nothing work.
Do you have any idea about it ? Is there a specific procedure to switch on (eg : press power for 1 minutes + blablabla).
My provider doesn't want to take my Gtab in warenty before my contract is activated (the 4th of february).
Thank you for your answer

HELP, I have same problem, please explain how Hemidall can fix it?
Thanks
[email protected]

zyborg said:
Could you please list the steps you went through in order to fix this - for everyone else's sake? Thx!
Click to expand...
Click to collapse
I also had a semi-bricked VZW Tab, with the phone-triangle-computer warning graphic at start up. (I flashed a new boot loader, and failed to read the instructions closely enough. Either the file was incorrect for my device, or the drivers were not loaded correctly, but my tablet was borked.)
Using heimdall 1.3.2 (with the correct drivers, on a 32-bit windows system), I clicked the "close pc screen" option to clear the warning.
I then held the power button until it turned off, then held vol+ and power to re-enter download mode. Once in download mode, I used heimdall 1.1.1 to flash the zImage from SCH-I800-Stock-Rooted-2.3.5. My tablet (still unrooted, and still stock?) booted, but sat at the SAMSUNG logo for ten minutes or more. (It announced its progress, telling me periodically "five minutes remaining", etc.)
Once it finished, my tablet was revived. I will now follow the above advice and read all instructions very carefully, re-writing them in my own words to ensure I understand what I'm doing, before I try this again.

One year old thread......do you guys ever watch posting dates???
Sent from my GT-P1000 using Tapatalk 2

...like REALLY bricked
bumping this old thread in hopes that someone can point me in the right direction...
Got my p7510 (10.1" wifi retail) stuck pretty badly when trying to restore stock ROM coming from Overcome (it came rooted from ebay). From what I gather from the forums, seems like my bootloader is still locked.
whenever I attempt to flash a BOOTLOADER, PIT, or PDA using ODIN it connects, initializes, and gets stuck on "Flashing boot.img"
I think the recovery partition is damaged. When I boot using Power + Volume Down, I can get to the screen where you select recovery mode or download mode but recovery mode will not load. The screen flickers when I select recovery, but goes nowhere. Download mode works.
I tried using nvflash to force the right software onto it but I get error 0x4 (usb write failed).
There has to be a way to restore the stock bootloader and get this thing running again. Tablet will not boot android at this point. I have been searching the forums for about a week now, anyone have any ideas?

[Q] Pattern Bypass Streak 7

basically, before you guys judge, why would i need a pattern bypass, let me get through the story.
Basically, my tenant couldnt pay her rent, so she decided to give me half and leave. when she left, she also left her dell streak. i gave her a call and she told me i can just have it. when i tried to turn it on, it wouldnt so i charged it. waited a while, say 6 hours, then when i got back to it, there was a pattern lock. called her again but unfortunately, her cell phone line got deactivated. its been 2 days, and ive been trying but no luck.
basically, i just need a program, software, anything? lol. to bypass this because i want to sell it, or maybe try to fall in love with it
*things i have tried*
[1.] Vol up + Power
~brings me to (stock??) recovery (im guessing?) with 5 choices.
0. Boot Up
1. Factory reset (User data only)
2. Software upgrade via update.pkg on SD card
3. Factory reset (User data and Internal Tablet storage)
4. Power off
~Chose #1 which failed
~Chose #3 also failed
both booted up perfectly and still showed the pattern unlock screen.
[2.] Followed a guide
~i basically treated the streak like it was bricked, so i fallowed a guide from illdill (sorry i forgot the link) but it was something related to nvflash and using it to flash images 2-21 on the dell streak 7.
~this method also failed, and also booted up perfectly.
*[3.] Try to put HoneyStreak RC 2.1*
~i get the error "Formatting partition 2 BCT please wait.. FAILED!"
idk what i means but all i know is that when i used the search button, i guess peoples who ask about it and have trouble about it, they get ignored. they try to bump, but yet no response. I read from post 427 to almost 560. none was answered. if there is a way out there. please help me ;(
only 2 methods i tried. anyone else? thanks in advance xda users. quick responses that arent usually nonsense gets a thank button clicked from me

jayjaypops said:
basically, before you guys judge, why would i need a pattern bypass, let me get through the story.
Basically, my tenant couldnt pay her rent, so she decided to give me half and leave. when she left, she also left her dell streak. i gave her a call and she told me i can just have it. when i tried to turn it on, it wouldnt so i charged it. waited a while, say 6 hours, then when i got back to it, there was a pattern lock. called him again but unfortunately, his cell phone line got deactivated. its been 2 days, and ive been trying but no luck.
basically, i just need a program, software, anything? lol. to bypass this because i want to sell it, or maybe try to fall in love with it
*things i have tried*
[1.] Vol up + Power
~brings me to (stock??) recovery (im guessing?) with 5 choices.
0. Boot Up
1. Factory reset (User data only)
2. Software upgrade via update.pkg on SD card
3. Factory reset (User data and Internal Tablet storage)
4. Power off
~Chose #1 which failed
~Chose #3 also failed
both booted up perfectly and still showed the pattern unlock screen.
[2.] Followed a guide
~i basically treated the streak like it was bricked, so i fallowed a guide from illdill (sorry i forgot the link) but it was something related to nvflash and using it to flash images 2-21 on the dell streak 7.
~this method also failed, and also booted up perfectly.
only 2 methods i tried. anyone else? thanks in advance xda users. quick responses that arent usually nonsense gets a thank button clicked from me
Click to expand...
Click to collapse
Try flashing Honeystreak (it completely erases the internal memory since it needs to repartition it) if you like Honeystreak, keep it, if you want stock, flash back. Hopefully that will work.

bluesy_92 said:
Try flashing Honeystreak (it completely erases the internal memory since it needs to repartition it) if you like Honeystreak, keep it, if you want stock, flash back. Hopefully that will work.
Click to expand...
Click to collapse
thanks for quick response, ill try and see, most of the things im reading are, i have to atleast have CWR. which i highly doubt she has. when i tried to explain to her what "rooting" means, lets just say she wasnt interested at all.

unfortunately, it didnt work. somethings about "Formatting partition 2 BCT please wait.. FAILED!" and doesnt go through, that makes method 3 = failed. unless someone out there has a different suggestion?
thanks in advance

Uh...it failed to format the partition? I don't think I've ever seen that happen.
I know this will sound stupid, since you are probably in the right forum, but where you said "streak" are you sure it was the 7 inch and not the 5? Also, you said you got into recovery by volume UP and power, but I think volume DOWN and power is stock recovery...maybe it had CWM installed by someone who has used it before? (the options sound like CWM) and in that case, someone may have changed something. Again, I'm shooting in the dark, but if it is a streak 5, or if it has CWM, it would be different than just a stock Streak 7 on the lockscreen. The streak 5 and 7 are not just different sizes of the same device - they run on a different chipset. The 5 has a snapdragon (I believe) and the 7 has a Tegra 2.
EDIT: You said Streak 7 in the title, so...I'm pretty sure you know it's a 7. In that case, I don't know why it won't flash :-/

bluesy_92 said:
Uh...it failed to format the partition? I don't think I've ever seen that happen.
I know this will sound stupid, since you are probably in the right forum, but where you said "streak" are you sure it was the 7 inch and not the 5? Also, you said you got into recovery by volume UP and power, but I think volume DOWN and power is stock recovery...maybe it had CWM installed by someone who has used it before? (the options sound like CWM) and in that case, someone may have changed something. Again, I'm shooting in the dark, but if it is a streak 5, or if it has CWM, it would be different than just a stock Streak 7 on the lockscreen. The streak 5 and 7 are not just different sizes of the same device - they run on a different chipset. The 5 has a snapdragon (I believe) and the 7 has a Tegra 2.
Click to expand...
Click to collapse
ahhh, thank you. first off, the partition, basically it looks like this (http://forum.xda-developers.com/showpost.php?p=15109690&postcount=425). i have no idea why it fails.
the only ways i could tell it "might be" a streak 7 is....
stock, Volume Up+Power is stock recovery menu. Volume Down+power is USB Fastboot. Has red letters as well.
now. is there anything visible or any button power combo where i would be able to find out if this was a dell streak 5 or 7? sorry for the nweb question.
*fyi, i know how CMW looks like, i have owned many android devices and... lets just say trust me... the Volume Up+Power looks like stock recovery and the only reason i say this is because it has 5 options, and 2 of them are Factory Reset.
Thanks again for quick response!

Other than the screen size, the capacitive buttons are layed out differently. On the streak 5, they are equally spaced, wheras the Streak 7 has them placed so that in landscape, they would all be under your thumb. The Streak 5 also has a removable battery, and the Streak 7 does not. If you check the back and it is smooth with a removable battery, it's a 5. If it is lightly textured without a removable battery, it is a 7.
Hope this helps
EDIT: And as far as the partition, I still don't know what would cause the problem. It might be best to ask someone with more NVFlash experience than me

bluesy_92 said:
Other than the screen size, the capacitive buttons are layed out differently. On the streak 5, they are equally spaced, wheras the Streak 7 has them placed so that in landscape, they would all be under your thumb. The Streak 5 also has a removable battery, and the Streak 7 does not. If you check the back and it is smooth with a removable battery, it's a 5. If it is lightly textured without a removable battery, it is a 7.
Hope this helps
EDIT: And as far as the partition, I still don't know what would cause the problem. It might be best to ask someone with more NVFlash experience than me
Click to expand...
Click to collapse
perfect bluesy_92. you've helped me so much already even thought my dell streak is still "unable to be used" now im for sure guarenteed this is a dell streak 7 (lol) since there is no removable battery and the c buttons are right under my thumb landscape wise.
as for the partition, would you help me figure out? ill sorta spam (not really) on the development thread for anyone who has nvflash experience to help me out with my streak.
as for others who click on this thread and do read and by any chance know any nvflash experience. please do help and just jump right in. thanks so much XDA community providers lets see if we can get through a bypass.

as of things to try
as of things to try in the morning when i wake up for work
the only thing im missing now is my adapter for my miniSD card to stick it in my streak and do the update.pkg file from the stock recovery menu. idk if it will bring me far because at work, i have internet access all day via phone (htc sensation) and i can try to keep update with my xda app but i have no desktop whatsoever.

jayjaypops said:
perfect bluesy_92. you've helped me so much already even thought my dell streak is still "unable to be used" now im for sure guarenteed this is a dell streak 7 (lol) since there is no removable battery and the c buttons are right under my thumb landscape wise.
as for the partition, would you help me figure out? ill sorta spam (not really) on the development thread for anyone who has nvflash experience to help me out with my streak.
as for others who click on this thread and do read and by any chance know any nvflash experience. please do help and just jump right in. thanks so much XDA community providers lets see if we can get through a bypass.
Click to expand...
Click to collapse
Well, I've heard of people getting devices that are locked in read-only, basically making them unable to be flashed. The fact that nothing is working scares me that this may be the case, but at the same time, I never experienced it, so I definately can't be sure. Someone who has may be able to tell you if you're stuck. If it is read-only, your only hope is Dell by that point :-/
That's the first thing I think you should find out. Because if it is locked in read-only, your case is pretty much closed at that point (and not in a good way, unless Dell helps you.) If you find out it's not, then I would try to figure out why Honeystreak isn't flashing properly.
You can try update.pkg - everything is worth a shot, but unlike flashing Honeystreak, I think it won't repartition or anything (updating through a .pkg is the way manufacturers release updates - it was not designed to be harmful to the users data, afaik) so that's not exactly a sure-thing. Don't let that stop you from trying it, though - when something can't be used at all, any idea is a good idea

bluesy_92 said:
Well, I've heard of people getting devices that are locked in read-only, basically making them unable to be flashed. The fact that nothing is working scares me that this may be the case, but at the same time, I never experienced it, so I definately can't be sure. Someone who has may be able to tell you if you're stuck. If it is read-only, your only hope is Dell by that point :-/
That's the first thing I think you should find out. Because if it is locked in read-only, your case is pretty much closed at that point (and not in a good way, unless Dell helps you.) If you find out it's not, then I would try to figure out why Honeystreak isn't flashing properly.
You can try update.pkg - everything is worth a shot, but unlike flashing Honeystreak, I think it won't repartition or anything (updating through a .pkg is the way manufacturers release updates - it was not designed to be harmful to the users data, afaik) so that's not exactly a sure-thing. Don't let that stop you from trying it, though - when something can't be used at all, any idea is a good idea
Click to expand...
Click to collapse
well, im not really trying to flash anything, i dont even care if its rooted or not, i just want it to be working basically. so my son can watch his elmo while i play my game or update my roms or watch my movies without him whining anything just to make it stock perfect again and this bypass to go through >__<"

What happened when you tried nvflash ?
Did it push all of the partitions properly ?
Are you sure you had it in apx mode ?
I just recovered mine from a honeystreak flash and nvflash rewrites all partitions. Then try to fastboot push the system / recovery images.. After that you should be able to use cwm via fastboot to write a new rom ( I went back to streakdroid 1.3 ).
Just put the image file into your fastboot directory and boot it from your computers hard drive ( fastboot boot cwm.img )

pyraxiate said:
What happened when you tried nvflash ?
Did it push all of the partitions properly ?
Are you sure you had it in apx mode ?
I just recovered mine from a honeystreak flash and nvflash rewrites all partitions. Then try to fastboot push the system / recovery images.. After that you should be able to use cwm via fastboot to write a new rom ( I went back to streakdroid 1.3 ).
Just put the image file into your fastboot directory and boot it from your computers hard drive ( fastboot boot cwm.img )
Click to expand...
Click to collapse
re read past posts?
pyraxiate said:
What happened when you tried nvflash ?
Did it push all of the partitions properly ?
Click to expand...
Click to collapse
this is what it looks like when i double click download.bat (http://forum.xda-developers.com/showpost.php?p=15109690&postcount=425) it gives me a FAILED!
pyraxiate said:
Are you sure you had it in apx mode ?
Click to expand...
Click to collapse
hold down Volume up + Volume down while plugging the USB cable in? Pretty sure i am because the first time i got prompted on my computer, i already downloaded the drivers, i just had to direct it to find the drivers, it said APX mode.
pyraxiate said:
I just recovered mine from a honeystreak flash and nvflash rewrites all partitions. Then try to fastboot push the system / recovery images.. After that you should be able to use cwm via fastboot to write a new rom ( I went back to streakdroid 1.3 ).
Click to expand...
Click to collapse
when you double click download.bat, after the img file 14 or 15 goes through, does your command screen suddenly disappear? whats your next step through that?

I flashed using these partition images ( Not the ones in the initial NVflash post) Maybe your image files were corrupted on download. Im glad someone uploaded them in 1 rar to ensure a clean set
Id start over from scratch by using this rar as your c:\Nvflash directory
http://www.multiupload.com/OM0VO9HBO9
See if those make a difference. After Nvflash completes the box will close, its normal. Use the pinhole to reset. From there I just used fastboot ( vol down and power ) to boot into cwm ( i can dropbox the image if you need it ). The command is : fastboot boot cwmimagename.img
from there you can format data/cache/system/dalvik/storage ( mine came back with an error not being able to format a few but try it anyway)
Mount SD card and copy something like the streakdroid zip to it. Using CWM's menus, install a zip from SDcard and choose it. It should run w/o error.
I had the Dell logo only stuck on boot after that , so I went into recovery and formatted user data only . From there it booted right up.
When you boot your streak, does it still boot into the original rom or does it just freeze on the Dell logo?

Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General

pyraxiate said:
I flashed using these partition images ( Not the ones in the initial NVflash post) Maybe your image files were corrupted on download. Im glad someone uploaded them in 1 rar to ensure a clean set
Id start over from scratch by using this rar as your c:\Nvflash directory
http://www.multiupload.com/OM0VO9HBO9
See if those make a difference. After Nvflash completes the box will close, its normal. Use the pinhole to reset. From there I just used fastboot ( vol down and power ) to boot into cwm ( i can dropbox the image if you need it ). The command is : fastboot boot cwmimagename.img
from there you can format data/cache/system/dalvik/storage ( mine came back with an error not being able to format a few but try it anyway)
Mount SD card and copy something like the streakdroid zip to it. Using CWM's menus, install a zip from SDcard and choose it. It should run w/o error.
I had the Dell logo only stuck on boot after that , so I went into recovery and formatted user data only . From there it booted right up.
Click to expand...
Click to collapse
sorry for the late reply, i just barely got home from work. i just bought myself a 2 gig micro sd card, and the adapter to stick the micro sd card in the bigger sd card. im going to try the update.pkg. unfortunate of me, i tried to do it right away but its low battery just my luck. charging the streak 7 right now.
pyraxiate said:
When you boot your streak, does it still boot into the original rom or does it just freeze on the Dell logo?
Click to expand...
Click to collapse
not even, it would boot original rom with the users data still enabled. (the reason i say this is because, the pattern lock is still there) even when i tried the nvflash, it would boot right up to the pattern lock and with the same background she always had.

idea
since i now have an sd card, im going to try the "Restore your DS7" but the only thing thats stopping me is that it requires CWR which i dont have. ill try to work around it since my DS7 is recognized by fastboot and ADB. Also wanted to add another misfortune of mine, she does have debug mode on but fastboot should work rather than ADB. wish me luck.
if anyone has any other suggestions or ideas, please budge in. i dont mind at all. thanks for the help all!

lufc said:
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
Click to expand...
Click to collapse
sorry lufc. thanks for moving. i apologize. just stressed out from real life events. arent we all ? aha. thanks and im sorry once again!

jayjaypops said:
since i now have an sd card, im going to try the "Restore your DS7"
Click to expand...
Click to collapse
failed, right when i typed adb devices, it shows my DS7 numbers, but when i type adb shell, i dont get ~# sign back. i get an error: Closed!
here i come nvflash. i shall try you again with the help of "pyraxiate" link he used to restore his DS7. wish me luck!

here i come nvflash. i shall try you again with the help of "pyraxiate" link he used to restore his DS7. wish me luck!
Click to expand...
Click to collapse
failed aswell, after double clicking restore.bat, i let it do its own thing, after it pushes p14.img file, it closes the command box right away, so i used an earring to turn off the device, unplugged from the usb, and yet, it still loads up pefectly with the same wallpaper and still the pattern lock... ughh, this is really frustrating!! ;'(
im trying one last step, before i call dell... (i dont even know if they'll replace this since im not the owner or the buyer of the product. unless they will? let me know)
my last step im taking is, im gonna use nvflash again, but this time im gonna use the WIFI DS7 partitions. hopefully it works. please almight lord! *sniff* begging. wish me luck. ill update
and as you already know what im going to say next, if anyone out there has any suggestions, ideas or plans. please help me out. might help others out in the community. thanks so much in advance

qhsusb_bulk hard bricked my Shamu,how can i unbrick it?

Actually my friend bricked his phone, he flashed the 5.1 bootloader and radio.then somehow he flasheed back to 5.0.1 stock. then he flashed Euphoria again. The phone rebooted fine and he went to sleep. Then woke up and found out his phone was dead. And all buttons combo didn't work at all. It's just a piece of dead body.When plugging into the PC, it shows qhsusb_bulk. There were devices that had same problems but they managed to unbrick it, But those methods don't apply to Shamu. Odd thing is I did the same thing so far my Nexus 6 is fine .I've started worrying, tho. We bought it from amazon.fr and I'm sure i dont want to send it back all the way from China to France.
Also , i read some dudes encountered the same problem after flashing Cm12 with 5.1 BL. I really need your help.
I tried Nexus Root Toolkit to flash the factory image, it didnt work. It's still using the fastboot, and ofc i don't get to go there.
I've installed the Qualcomm_QHSUSB_driver, but it doesn't seem to fix anything.

no one?

Mine has done the same thing. Went to flash 5.1 nexus image from the google dev site. The flash did boot and radio and failed size on system ( even re-downloaded). I plug my N6 into my linux machine and this what I get on lsusb "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)". I am also in need of help.

This updates been a nightmare

synapses said:
Mine has done the same thing. Went to flash 5.1 nexus image from the google dev site. The flash did boot and radio and failed size on system ( even re-downloaded). I plug my N6 into my linux machine and this what I get on lsusb "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)". I am also in need of help.
Click to expand...
Click to collapse
So you're like me, no way to enter bootloader right? I've seen some other phones with the same problems but they figured a way out to solve it. I don't know we'll get that

beachbum40 said:
This updates been a nightmare
Click to expand...
Click to collapse
I'm not sure it has anything to do with the update. My friend didn't flash the 5.1 google factory image . He flashed the 5.1 BL on a 5.0.2 aosp based rom then went back to stock 5.0.1 then flashed the same 5.0.2 aosp rom. Now it ends up dead.

This happened on Samsung devices too and it was a emmc issue, so the internal drive among others was no longer readable and writable and hardware like buttons was not working either. Unless someone comes with the golden tip you`ll have to turn it in for repair. Good luck guys

randy6644 said:
So you're like me, no way to enter bootloader right? I've seen some other phones with the same problems but they figured a way out to solve it. I don't know we'll get that
Click to expand...
Click to collapse
doing some reading and it seams to be a broken bootloader.

synapses said:
doing some reading and it seams to be a broken bootloader.
Click to expand...
Click to collapse
I'm also a g2 owner, some just broke their devices and ended up sth similar. But they managed to unbrick it. I don't know if we stand a chance to bring it back to life.

I'm still stuck. Any progress ?

synapses said:
doing some reading and it seams to be a broken bootloader.
Click to expand...
Click to collapse
Any progress? I tried several ways and none of them worked

I had to RMA

randy6644 said:
Actually my friend bricked his phone, he flashed the 5.1 bootloader and radio.then somehow he flasheed back to 5.0.1 stock. then he flashed Euphoria again. The phone rebooted fine and he went to sleep. Then woke up and found out his phone was dead. And all buttons combo didn't work at all. It's just a piece of dead body.When plugging into the PC, it shows qhsusb_bulk. There were devices that had same problems but they managed to unbrick it, But those methods don't apply to Shamu. Odd thing is I did the same thing so far my Nexus 6 is fine .I've started worrying, tho. We bought it from amazon.fr and I'm sure i dont want to send it back all the way from China to France.
Also , i read some dudes encountered the same problem after flashing Cm12 with 5.1 BL. I really need your help.
I tried Nexus Root Toolkit to flash the factory image, it didnt work. It's still using the fastboot, and ofc i don't get to go there.
I've installed the Qualcomm_QHSUSB_driver, but it doesn't seem to fix anything.
Click to expand...
Click to collapse
Something should be able to be done using QPST (i.e., to force flash the bootloader), but that is above my level of knowledge.

efrant said:
Something should be able to be done using QPST (i.e., to force flash the bootloader), but that is above my level of knowledge.
Click to expand...
Click to collapse
I'm going through similar with a dead Nexus 7. I think the eMMC died in it though, as it just went out without any tinkering. No sign of life on the device, but is picked up as a Qualcomm modem port and detected by QPST in download mode. I don't have/can't find the hex files required by QPST to flash it though.
I theorize that if a working device can be put in QPST "diag" mode, then QPST will allow exporting the storage contents in a flashable hex file, and that file could be used to restore the boot partitions on the dead device. I haven't been able to find information about this "diag"nostic mode, however.

Same issue guys, Upgraded to 5.1 OTA rooted and flashed cm12 tried to reboot. Nothing. Stuck in "Qualcomm HS-USB QDLoader 9008" QPST will recognize it in Download mode. If we can get these Hex files I will give it a shot. Thanks!

http://bbs.gfan.com/forum.php?mod=viewthread&tid=7863761
found sth here dont know if its useful, all written in Chine

randy6644 said:
http://bbs.gfan.com/forum.php?mod=viewthread&tid=7863761
found sth here dont know if its useful, all written in Chine
Click to expand...
Click to collapse
Cant find much relating to our issue but there may be relevant info there, we cant download or make an account on that site due to our american IP anyway.

i will upload them when im home. i read sth about qc diag interface,qcn stuff. but this thread is a tutorial for cracking the China Telecom band. Dont know if theres anything useful

randy6644 said:
i will upload them when im home. i read sth about qc diag interface,qcn stuff. but this thread is a tutorial for cracking the China Telecom band. Dont know if theres anything useful
Click to expand...
Click to collapse
If you are able to export the Hex file with everything we need to restore through QPST you will be saving alot of peoples ass as the number of hard bricks are growing hourly now! Or at least the threads being started about hard bricks are! Appreciate the help brother. AdA

im not sure if i can find the useful files you need. just trying my best to contact that op , if he knows sth. my ass will ne saved. but its 1 .30 am in China.i dont think hes awake. i will keep an eye on that.

CM13 and future son in law bricked my Lg G2

So here is what I know, an attempt was made to update my G2 by someone other than myself. It now has a black screen and no recovery, it has also been attempted to be repaired by the same person. My pc no longer sees my phone, no download mode or anything else. Is there any hope for this device?

Well, any thoughts from the vast knowledge pooled on here?

godzilla61 said:
Well, any thoughts from the vast knowledge pooled on here?
Click to expand...
Click to collapse
Power on? Anything?
Sent from my Nexus 6 using XDA Free mobile app

31ken31 said:
Power on? Anything?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Downlad and run SRKtool_2.1_droidth with the correct drives.. All will be well again..

tried the srktool, no drives detected. the qhsusb_bulk driver loads so it does see something......

godzilla61 said:
tried the srktool, no drives detected. the qhsusb_bulk driver loads so it does see something......
Click to expand...
Click to collapse
When you start it pick #4 fixed then #5 unbrick.. You must have had USB Debugging mode Enable prior to bricking.. Also check device manager in windows and check ports.. Will try to help you the best I can, had the same issue 3 days after getting the phone.. If you get it to work after use th Lg program and do fix phone or you will have a lot of issues.

No JOY,
hankbizzo5 said:
When you start it pick #4 fixed then #5 unbrick.. You must have had USB Debugging mode Enable prior to bricking.. Also check device manager in windows and check ports.. Will try to help you the best I can, had the same issue 3 days after getting the phone.. If you get it to work after use th Lg program and do fix phone or you will have a lot of issues.
Click to expand...
Click to collapse
The problem I'm running into is there isn't a bunch of disks shown, only the fixed disks in my comp. So nothing is being seen or they are not there to see.

godzilla61 said:
The problem I'm running into is there isn't a bunch of disks shown, only the fixed disks in my comp. So nothing is being seen or they are not there to see.
Click to expand...
Click to collapse
That is what should happen.. You need the qhsusb QUALCOMM DRIVER..

it is seen as that and on com 7, tried the srktool, no drives detected. the qhsusb_bulk driver loads so it does see something......

Well, I guess it's dead if no one else has any suggestions....... what a shame I really liked this device.

godzilla61 said:
So here is what I know, an attempt was made to update my G2 by someone other than myself. It now has a black screen and no recovery, it has also been attempted to be repaired by the same person. My pc no longer sees my phone, no download mode or anything else. Is there any hope for this device?
Click to expand...
Click to collapse
Does your phone boot? Does it charges?

yes it charges. no it does not boot.

godzilla61 said:
yes it charges. no it does not boot.
Click to expand...
Click to collapse
I have the VS980 (Verizon version) and I was completely...and I mean completely dead (due to my own mistake) , no charge, no power, no download mode, no led, nothing at all. I had a full on 100% brick sitting on my desk. BUT.....I went here, http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404 and was able to bring it back to life. Now yes you do have to open the device and mess with inside parts but i was able to get mine going. The guide here is for the other models (specifically not the vs980) but I was able to finagle the inside parts to make it work the way I needed to. From there I was able to boot back up and i flashed all the way back to 10B and just OTA back up to lollipop and root again and install TWRP and I'm back up to where I was a few weeks ago, of course I lost everything (texts,photos) in the process but I am back up and running and I am happy I was able to pull that off thanks to the great folks who figure all this stuff up for us.
So I would say go for it and try it, or if not I could do it for you, and if not I'm am surely positive that someone here can help you figure it out with your current situation. Cheers.
PS, if you dont want to mess with it, just let me have it LOL!

Fully Hard Bricked Moto G xt1072 (Help) DX

So i have a Moto g xt1072 wich i got second hand.. i got it into recovery mode and eventually got it working, but it was really unstable, so i wanted to reflash the stock rom, because it looked like the current one on the phone was corrupted (i was running android 6.0) (btw i have a xt1068 as my daily driver, but i want this to work again)
So i started flashing http://forum.xda-developers.com/moto-g-lte/general/stock-6-0-marshmallow-europe-reteu-t3338075 <-this
but i had errors and it was failing multiple times.. so i looked up some tutorials, and most of them were unlocking the bootloader at the beginning, so i was unlocking and locking the bootloader trying to get the commands to work,
then i found a tutorial wich coppyd all of the commands at once, so i tried that.. screen went black..
Wont boot into recovery, 3sec method or 120 sec method, and connects to my pc as QHSUSB_BULK
luckily i made a picture of the recovery when i tried to flash:
http://imgur.com/8avCk3T
I think i may need to blank flash, but im not certain..
I would also like to find the firmware for this phone that wont brick it..
Can anyone help?
Need more info?
Please just ask me, i will respond immediately
i dont care what i need to do.. even if i need to hardwire (because im really good at those finicky things)
Thanks for reading XD

Same issue here. I flashed a stock image and something must've gone wrong at some point

hamzahrmalik said:
Same issue here. I flashed a stock image and something must've gone wrong at some point
Click to expand...
Click to collapse
you probably also flashed the vootloader and the bootanimation, these are known to give problems, but ive foubd a test point on the pcb which brings the phone in a les hard bricked state, but ive yet to find a method to unbrick the phone..
ill keep you posted

ora69 said:
you probably also flashed the vootloader and the bootanimation, these are known to give problems, but ive foubd a test point on the pcb which brings the phone in a les hard bricked state, but ive yet to find a method to unbrick the phone..
ill keep you posted
Click to expand...
Click to collapse
Sorry could you please explain. How can a phone be less hard bricked. Thanks
Sent from my A0001 using Tapatalk

hamzahrmalik said:
Sorry could you please explain. How can a phone be less hard bricked. Thanks
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
okay, so there are different types of hardbricks, all act the same, but one is harder to unbrick than the other, there is qh usb bulk and qhas bulk with numbers behind it, search for force unbrick lg g2,
now the problem is, it should be easy to unbrick the phone at thsi point, but im not an expert in that and have no idea what to do now xD so i posted it on xda, but no one answered me.. xD hopefully this clears it up some more

ora69 said:
okay, so there are different types of hardbricks, all act the same, but one is harder to unbrick than the other, there is qh usb bulk and qhas bulk with numbers behind it, search for force unbrick lg g2,
now the problem is, it should be easy to unbrick the phone at thsi point, but im not an expert in that and have no idea what to do now xD so i posted it on xda, but no one answered me.. xD hopefully this clears it up some more
Click to expand...
Click to collapse
Oh ok I get you. Mines USB bulk 9000 or something i can't remmeber now
Sent from my A0001 using Tapatalk

ora69 said:
So i have a Moto g xt1072 wich i got second hand.. i got it into recovery mode and eventually got it working, but it was really unstable, so i wanted to reflash the stock rom, because it looked like the current one on the phone was corrupted (i was running android 6.0) (btw i have a xt1068 as my daily driver, but i want this to work again)
So i started flashing http://forum.xda-developers.com/moto-g-lte/general/stock-6-0-marshmallow-europe-reteu-t3338075 <-this
but i had errors and it was failing multiple times.. so i looked up some tutorials, and most of them were unlocking the bootloader at the beginning, so i was unlocking and locking the bootloader trying to get the commands to work,
then i found a tutorial wich coppyd all of the commands at once, so i tried that.. screen went black..
Wont boot into recovery, 3sec method or 120 sec method, and connects to my pc as QHSUSB_BULK
luckily i made a picture of the recovery when i tried to flash:
http://imgur.com/8avCk3T
I think i may need to blank flash, but im not certain..
I would also like to find the firmware for this phone that wont brick it..
Can anyone help?
Need more info?
Please just ask me, i will respond immediately
i dont care what i need to do.. even if i need to hardwire (because im really good at those finicky things)
Thanks for reading XD
Click to expand...
Click to collapse
So that link to another thread in XDA forum, I think I had a similar experience. I too have the XT1072 as I live in the UK. now here on XDA you have to be careful and ask 3 4 maybe 5 times before someone listens properly. I know it is hard for the devs with so many dumb noobs asking so many dumb questions, I include myself as a noob so no worries. Anyway to get to the point that link is not referring to our phone the XT1072. You should ignore LTE in your search criteria, it will always point you towards the 2015 model and believe you me all roms in my experience area very device specific. You need to simply put Moto G 2nd gen 2014 in search criteria when it comes to searching for custom recoverys and/or stock ROMS. The Titan.IMG is always a safe bet if I remember correctly, dont take my word for it, I have been known to have a memory like a sieve now and again, the problem with getting older, cache gets smaller and smaller, lol! Best of luck!

hamzahrmalik said:
Sorry could you please explain. How can a phone be less hard bricked. Thanks
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Read the beginning on this article: http://rootmyandroid.org/how-to-unbrick-your-android-device-the-ultimate-guide.html/
the bricked term is a common misconception for phones that still turn on..