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

[Q] Stuck in Fastboot and can only access hard reset which goes back to fastboot

Hello,
I know there are a ton of "stuck in fastboot" threads but I've spent hours going through them and none of them seem to be what's happening to me. Or maybe all of them combined would... anyway, I would greatly appreciate some help as I'm at my witt's end. I've even somehow managed to screw up a dual boot of Ubuntu on my windows machine, but that's something I'll fix for myself later
Anyway, here's all the info I can think of and what I have done so far.
A month or two I rooted my phone. I never flashed a custom rom or anything. I altered a couple settings but that's it. My phone has worked perfectly this entire time.
Yesterday there was an OTA. I didn't even intend to accept it, I just got the notification and then my phone shut off and went to fastboot. That's pretty much where I've been ever since.
Rebooting gets me to fastboot. Attempting recovery mode gets me to the hard reset screen but not recovery. Trying to hard reset just goes back to fastboot. Download mode does not come up.
Windows sees my phone but disables it because of an error. Attempting to reinstall drivers does nothing. Ubuntu doesn't acknowledge that the phone is there under the regular terminal. If I run the fastboot tool it wont list it but it will respond to a couple commands. I can reboot... into fastboot. Anything else gets the "waiting for device" notification. My device just says "processing commands" but nothing happens.
So that's where I'm at right now. That's the condensed version of the last 18 hours but I think it contains most of the relavent information. I would greatly appreciate any assistance. I'm lucky to have this phone and I would be very upset if I lost it.
Thank you.

CrazyCat42 said:
Hello,
I know there are a ton of "stuck in fastboot" threads but I've spent hours going through them and none of them seem to be what's happening to me. Or maybe all of them combined would... anyway, I would greatly appreciate some help as I'm at my witt's end. I've even somehow managed to screw up a dual boot of Ubuntu on my windows machine, but that's something I'll fix for myself later
Anyway, here's all the info I can think of and what I have done so far.
A month or two I rooted my phone. I never flashed a custom rom or anything. I altered a couple settings but that's it. My phone has worked perfectly this entire time.
Yesterday there was an OTA. I didn't even intend to accept it, I just got the notification and then my phone shut off and went to fastboot. That's pretty much where I've been ever since.
Rebooting gets me to fastboot. Attempting recovery mode gets me to the hard reset screen but not recovery. Trying to hard reset just goes back to fastboot. Download mode does not come up.
Windows sees my phone but disables it because of an error. Attempting to reinstall drivers does nothing. Ubuntu doesn't acknowledge that the phone is there under the regular terminal. If I run the fastboot tool it wont list it but it will respond to a couple commands. I can reboot... into fastboot. Anything else gets the "waiting for device" notification. My device just says "processing commands" but nothing happens.
So that's where I'm at right now. That's the condensed version of the last 18 hours but I think it contains most of the relavent information. I would greatly appreciate any assistance. I'm lucky to have this phone and I would be very upset if I lost it.
Thank you.
Click to expand...
Click to collapse
You need to get someone to give you the boot.img's from whatever the ota update was and try to fastboot flash them. I have a tut somewhere in these threads how to to fastboot flash
http://forum.xda-developers.com/showthread.php?p=50738417
Sent from my LG-D959 using Tapatalk

D-FUSE said:
You need to get someone to give you the boot.img's from whatever the ota update was and try to fastboot flash them. I have a tut somewhere in these threads how to to fastboot flash
http://forum.xda-developers.com/showthread.php?p=50738417
Sent from my LG-D959 using Tapatalk
Click to expand...
Click to collapse
Ah! I never went back to that thread after installing linux. I will try that now and report back, thanks!

My pc wouldn't recognize my phone in fastboot until I installed the drivers from pdanet. It would get stuck at wating for device. Ihttp://www.androidheat.com/adb-fastboot-install-drivers-setup/

Well currently everything works until I get to the point that I type "adb devices"
I get "List of devices" and it's blank. My phone is now constantly repeating "reset, portcharge" over and over whenever it's plugged in...

CrazyCat42 said:
Well currently everything works until I get to the point that I type "adb devices"
I get "List of devices" and it's blank. My phone is now constantly repeating "reset, portcharge" over and over whenever it's plugged in...
Click to expand...
Click to collapse
Did you try and install the drivers from the link i posted? I would download pdanet for the drivers if i were you. You won't be able to fastboot the boot.img if your pc won't recognize your phone.

PattyNYC said:
Did you try and install the drivers from the link i posted? I would download pdanet for the drivers if i were you. You won't be able to fastboot the boot.img if your pc won't recognize your phone.
Click to expand...
Click to collapse
Not yet but I will be. I'm sorry for the delay, I got distracted with something for a bit. I'm trying to fix windows now at which point I will install the drivers you linked and try again.

CrazyCat42 said:
Well currently everything works until I get to the point that I type "adb devices"
I get "List of devices" and it's blank. My phone is now constantly repeating "reset, portcharge" over and over whenever it's plugged in...
Click to expand...
Click to collapse
Sorry i haven't been around dude I'm trying to get stuff setup of pac
Sent from my LG-D959 using Tapatalk

D-FUSE said:
Sorry i haven't been around dude I'm trying to get stuff setup of pac
Sent from my LG-D959 using Tapatalk
Click to expand...
Click to collapse
No problem. I've got my phone shut off to save battery because I'm under the impression that it won't charge in fastboot and I didn't figure repeating that would be good for it. I'm still trying to restore Windows. I'm not used to being limited to a single computer but without my phone and my desktop currently in another state I'm a bit frustrated.
Anyway, I appreciate the help and will keep trying. I'll update if anything happens.

CrazyCat42 said:
No problem. I've got my phone shut off to save battery because I'm under the impression that it won't charge in fastboot and I didn't figure repeating that would be good for it. I'm still trying to restore Windows. I'm not used to being limited to a single computer but without my phone and my desktop currently in another state I'm a bit frustrated.
Anyway, I appreciate the help and will keep trying. I'll update if anything happens.
Click to expand...
Click to collapse
Do u have the sdk set up
Sent from my LG-D959 using Tapatalk

D-FUSE said:
Do u have the sdk set up
Sent from my LG-D959 using Tapatalk
Click to expand...
Click to collapse
Yes. Everything in the tutorial worked perfectly... until I plugged in my phone, hahaha. I admit now that I'm doing it all in Ubuntu it's a little confusing as this is pretty new to me, but I'm pretty sure I set it up right.

CrazyCat42 said:
Yes. Everything in the tutorial worked perfectly... until I plugged in my phone, hahaha. I admit now that I'm doing it all in Ubuntu it's a little confusing as this is pretty new to me, but I'm pretty sure I set it up right.
Click to expand...
Click to collapse
Do it on windows bro I didn't do the ubuntu tur
Sent from my LG-D959 using Tapatalk

D-FUSE said:
Do it on windows bro I didn't do the ubuntu tur
Sent from my LG-D959 using Tapatalk
Click to expand...
Click to collapse
That's what I'm working on now, I screwed up the dual boot and can't get back into windows. Okay. I'm just going to grab my brother's laptop and use it so I can get this done. I can fix my computer later.
I'm going to start at the beginning of the tutorial since it'll be on a different computer. We'll see how it goes.
Edit: Okay, back to windows and this is what I have going on. I've installed the drivers for my phone, set up the sdk and gone into cmd but even with the drivers Windows is telling me that it has disabled my phone because it is malfunctioning (error code 43). Therefore no matter what I do it will not acknowledge the phone or communicate with it. If I try doing anything it just hangs on "waiting for device".

FIXED!
WOOHOO!!
It's working again! I'm not sure exactly how I did it but I rebooted my computer and suddenly the phone said "processing commands" so even though it still wasn't listed as a device I ran boot.img just to see what happened and it's back up and running just like nothing ever happened.
Thank you so much!

CrazyCat42 said:
WOOHOO!!
It's working again! I'm not sure exactly how I did it but I rebooted my computer and suddenly the phone said "processing commands" so even though it still wasn't listed as a device I ran boot.img just to see what happened and it's back up and running just like nothing ever happened.
Thank you so much!
Click to expand...
Click to collapse
Nice!

PattyNYC said:
Nice!
Click to expand...
Click to collapse
And thank you, too! It may well have been the drivers that did it. All I know is my brother's netbook was having the exact same issue my laptop was and then suddenly it worked.

CrazyCat42 said:
And thank you, too! It may well have been the drivers that did it. All I know is my brother's netbook was having the exact same issue my laptop was and then suddenly it worked.
Click to expand...
Click to collapse
Can anyone post links to download lgls995 lg g flex. Im stuck .. my phone does boot into os but wont go past the lg setup wizard it force closes and goes back to beginning of setup. I can boot into download mode and into system recovery.

LS995
st3wart said:
Can anyone post links to download lgls995 lg g flex. Im stuck .. my phone does boot into os but wont go past the lg setup wizard it force closes and goes back to beginning of setup. I can boot into download mode and into system recovery.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2644083

didithu said:
http://forum.xda-developers.com/showthread.php?t=2644083
Click to expand...
Click to collapse
my ls995 on sprint took the 4.4.2 update and now stuck in fastboot help

Fastboot
scotthall1515 said:
my ls995 on sprint took the 4.4.2 update and now stuck in fastboot help
Click to expand...
Click to collapse
Can u get into dl mode? If yes, u go back to stock for ls995 tot method, n then root it after that accept update KK and re root it. Hope that help.

[Q] Pulled my phone out of my pocket, it was hard bricked

Newb here. My HTC One M7 is hard bricked. LED doesn't turn on when I plug the charger into it. Tried holding pwr and vol-down, and all three buttons at once for two minutes. Nothing and I don't know what to do so I came here. I searched for threads on how to fix it but all I'm finding are fixes for bricks that were caused by rooting. I haven't rooted mine- it's still stock except for a SIM unlock I got about a year ago- so I don't know if those fixes are applicable to me or not.
So, my questions are, are there any threads that might be able to help me? If not, can anyone tell me wtf I can do to fix this? I don't want to end up sending it off to get repaired since I'm out of warranty at this point.
Edit: I should add that I have a Mac, not a PC. I'm out of warranty and I didn't get insurance. I'm probably SOL but figured I'd ask anyway.

ch3nz0 said:
Newb here. My HTC One M7 is hard bricked. LED doesn't turn on when I plug the charger into it. Tried holding pwr and vol-down, and all three buttons at once for two minutes. Nothing and I don't know what to do so I came here. I searched for threads on how to fix it but all I'm finding are fixes for bricks that were caused by rooting. I haven't rooted mine- it's still stock except for a SIM unlock I got about a year ago- so I don't know if those fixes are applicable to me or not.
So, my questions are, are there any threads that might be able to help me? If not, can anyone tell me wtf I can do to fix this? I don't want to end up sending it off to get repaired since I'm out of warranty at this point.
Edit: I should add that I have a Mac, not a PC. I'm out of warranty and I didn't get insurance. I'm probably SOL but figured I'd ask anyway.
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?t=2770684

clsA said:
Try this
http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
Thanks, that was one I found. Perhaps this is a dumb question but that requires a linux machine, does it not? I don't have a linux OS nor any experience with that.

ch3nz0 said:
Thanks, that was one I found. Perhaps this is a dumb question but that requires a linux machine, does it not? I don't have a linux OS nor any experience with that.
Click to expand...
Click to collapse
most use a Ubuntu live cd or flash drive to boot linux and fix their phone .. that's how I did it

clsA said:
most use a Ubuntu live cd or flash drive to boot linux and fix their phone .. that's how I did it
Click to expand...
Click to collapse
So at this point, I've created a usb boot stick with ubuntu, so I got that going for me. Next step, where do I find the appropriate package referenced in step 1 of Dexter's steps?

Now at this point, I've been able to extract the package and run the revive.sh command on the terminal. However, I get an error message saying that a bricked "device can't be found, check connections, aborting." Any advice?

ch3nz0 said:
Now at this point, I've been able to extract the package and run the revive.sh command on the terminal. However, I get an error message saying that a bricked "device can't be found, check connections, aborting." Any advice?
Click to expand...
Click to collapse
Sorry but i don't remember all the steps i took to get it to work. It was over 6 months ago i used it. All I can say is read the entire thread and gather as much information as you can their.

clsA said:
Sorry but i don't remember all the steps i took to get it to work. It was over 6 months ago i used it. All I can say is read the entire thread and gather as much information as you can their.
Click to expand...
Click to collapse
Thanks anyway. I just figured out that my phone is in QDL mode so it appears that Dexter's unbricking method won't work. Back to square 1.

Recovery Mode - what to do?

Found my fire tablet with a black screen and in Amazon system recovery <3e> this morning - not sure how it got into that state & how to get out of it. To my knowledge I didn't press any combination of keys that would get me into that state. It had been only very low battery when I plugged it into the electrical socket last night but I didn't touch it until the morning when I found it in this black screen state.
From searching I think this is the Amazon version of Android System Recovery screen. The exact options are:
-------
Amazon system recovery <3>
Volume up/down to move highlight;
enter button to select.
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
----------
I haven't rooted the tablet although I did apply the "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)"
(http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122)
I've had it for about a month without problems although a couple of days ago it kept trying to update several times in succession.
It has attempted to update a couple of times in the past, which put me into a panic at the time but when I'd check afterwards it would still show 5.0.1. firmware. Also the difference this time was that in the past it would only attempt to update the once, not several times in succession.
I'd assumed that installing "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)" doesn't stop the fire downloading updates but prevents them being installed. So when it happened in the past I didn't worry.
I'm not sure what to do (logically I'd assume I should just select the 1st option and reboot) but I'm not sure how I even got into this screen and if there's a reason for it so hoped someone might be able to advise me.
With thanks & crossed fingers
Frankie

Sorry - one other question!
Which key is the "enter button"?

FrankieChen said:
Sorry - one other question!
Which key is the "enter button"?
Click to expand...
Click to collapse
I've not used it but as we only have three buttons I'm going with the power button.

Pond-life said:
I've not used it but as we only have three buttons I'm going with the power button.
Click to expand...
Click to collapse
That's what I suspected!

Update
Well I ran out of power so the tablet switched off.
When I plugged it into an electricity socket, I decided to try the "reboot system now" option but it just rebooted and cam back to the same screen. I tried it about 4 times with the same result so I tried the "power down" option but it still returned to the same screen when switched back on.
Would really appreciate anyone's help.

Hmm, is there anything in the recovery logs?
Maybe reboot to bootloader, and see if it'll let you twrp to it from a pc, head to the twrp thread and grab the files.
fastboot boot TWRP_Fire_2.8.7.0.img
If it'll do that it's not on 5.1.1 at least, if not it might have tried to get there.

I haven't followed your instructions yet as after I posted last, it started to flash an error message along the lines of battery was too low to "factory reset" and something else - I don't recall what though. I didn't actually select any options apart from reboot and power down.
It was plugged in at the time but I unplugged it & replugged it in, in case for some reason it wasn't charging.
Since then the error message has stopped flashing and I just have a blank screen although you can see it is backlit. Pressing the power button has no effect

And that's on the charger it came with?
It's not looking good.

FrankieChen said:
...I haven't rooted the tablet although I did apply the "Installing Google Framework/Playstore...
...I'd assumed that installing "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)" doesn't stop the fire downloading updates but prevents them being installed....
Click to expand...
Click to collapse
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.

julianpaul said:
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.
Click to expand...
Click to collapse
True but the thread he's referring to does offer that function as an option in the batch file.
http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122
Tomsgt has put together a little install bat (Amazon-Fire-5th-Gen-Install-Play-Store.zip)
Now includes Removing Advertising and Blocks Over the Air System Updates (02 Nov 2015)
Click to expand...
Click to collapse

julianpaul said:
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.
Click to expand...
Click to collapse
It's still useful information - thanks

It's on the charger it came with and it has finally returned to the same Amazon system recovery screen.
In regards to preventing the updates - I think I did that when I installed the google apps but it was the 1st time i ever did this (it's my 1st tablet), and as it was over a month ago I can't be sure - this is all very new to me.
There are 4 recovery logs, completely meaningless to me.
/cache/recovery/last_kmsg
/cache/recovery/last_log
/cache/recovery/last_log1
/cache/recovery/last_log2
the kmsg log zooms past too fast to read with endless pages dealing with "swapper/0"
the last_log seems to have stuff reffering to tzdata, build, product.cpu, ro.product, dalvik and so on . Log1 and log2 seem to be similar stuff but shorter.
Any idea what I should be looking for?

I hoped it would be readable, build number might yield clues.
Given it will show something seems worth trying to see if twrp can see it in bootloader.

It may not have any thing to do with the updates as it was working after the updates had tried to install though I have to admit I only used it for a few minutes and I didn't check it before I plugged it in to charge the night before I found the black screen.
I don't actually have a clue what you mean when you say "twrp can see it in bootloader." so I will have to spend some time reading the forums to figure out what to do.
In desperation this morning I took the wipe data/factory reset option but it didn't work. It returned with the same screen and the error message
E:Error in /cache/recovery/dropbox_last_kmsg (Read-only file system)
I had installed the dropbox app but I had never actually signed in so there wouldn't be any data there.
After rebooting and being returned to the same screen, I attempted again to wipe data/factory reset.
This time it gave the message "data wipe complete" but still returned to the Recovery screen.
I've read the term "bricked" in several of the forums - is this what has happened to my device?
I wondered if I should contact Amazon about it as it's still under warranty but wondered if by installing gapps (and most likely having prevented updates as I followed all the instructions), whether I'd have invalidated my warranty.

FrankieChen said:
After rebooting and being returned to the same screen, I attempted again to wipe data/factory reset.
This time it gave the message "data wipe complete" but still returned to the Recovery screen.
I've read the term "bricked" in several of the forums - is this what has happened to my device?
I wondered if I should contact Amazon about it as it's still under warranty but wondered if by installing gapps (and most likely having prevented updates as I followed all the instructions), whether I'd have invalidated my warranty.
Click to expand...
Click to collapse
At this point, if you have adb drivers (or are comfortable installing them) you may as well try sideloading an update bin file. Links are here. I'd get the 3820 file.
If you want to do this, post back and I or someone will give you the steps. Otherwise, Amazon has been good about replacing tablets if you just describe what you say in the 1st paragraph of your post.

FrankieChen said:
It may not have any thing to do with the updates as it was working after the updates had tried to install though I have to admit I only used it for a few minutes and I didn't check it before I plugged it in to charge the night before I found the black screen.
I don't actually have a clue what you mean when you say "twrp can see it in bootloader." so I will have to spend some time reading the forums to figure out what to do.
Click to expand...
Click to collapse
use the reboot to bootloader option
set pc up with fastboot and see if it can be booted into twrp by fastboot
http://forum.xda-developers.com/showpost.php?p=63635664&postcount=9
http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548

Thank you for the replies. Sorry not to have responded earlier, I had a busy few days and although I have spent a lot of hours trying to read through the forums and find out about twrp, this is the 1st opportunity I have had to get back to trying to resolve the problem.
If I understand correctly, DoLooper has suggested sideloading an update bin file. (3820). I just started trying to do this but as the file to be downloaded is over 600MB and I am on a very slow connection it's showing it's going to take between 7-8 hours to download. If I take this option I will need to wait until tomorrow when I can get to a faster internet.
Pond-life, you have suggested that I
1. "use the reboot to bootloader option"
I'm presuming that this means that I have to select this option from the recovery screen on the tablet - does the tablet have to be attached to the pc via the USB cable when I select the option?
What should I expect once I have selected this option?
Would the tablet not need to be rooted to access the bootloader (as it isn't)?
2. "set pc up with fastboot and see if it can be booted into twrp by fastboot"
When I 1st got the tablet I had difficulties getting the adb drivers to install on my pc and after several days of trying I ended up doing it on another pc which I no longer have access to.
I have tried again to reinstall the drivers using rootjunkies file but again without success. I tried doing it using that method as I remember trying to do it that way (what felt like a billion times) though I don't remember if I finally ended up succeeding with that method or another.
I followed your link "http://forum.xda-developers.com/showpost.php?p=63635664&postcount=9" and tried the 1st method
"[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by Snoop05"
running the "adb-setup-1.4.3.exe" I get "0 files copied" after selecting "Yes to install ADB system-wide" which I recall was the problem (zero files copied) that I had previously.
Openning Device Manager after this does show any Fire or Android devices even when the tablet is connected so I'm assuming that the adb driver installation is failing.
I tried again with "adb-setup-1.3.exe". This time I had 4 files copied and got fire listed in the device manager but when I tried to update the driver I am not given the Android option in the list when I select the option to install driver.
I googled to see if anyone else had this error and I found that some peoplehad difficulties installing on XP but seems that MTP not being supported is the reason and it is resolved by installing WMP v10 and above. I have v11 so presume that's not the problem.
I don't have access to another computer at the moment to try and install the adb drivers but should be able to use another one tomorrow. Last time when I got the drivers to install it was on a vista machine so I wondered if that might have something to do with it.
The other thing that occurred to me was maybe there is something wrong with the cable as I only get the fire shown in the device manager for a few moments before it refreshes and then the fire is no longer shown.
I wondered if I should try to use USBDeview (as per http://www.inlovewithandroid.com/android-usb-connection-problems.html) to see if that is the problem. Certainly if I can the drivers installed on another pc it might suggest that there's a problem with mine.
Anyway, if I get the adb drivers to install successfully on another pc, could you explain what I am trying to do by "booted into twrp by fastboot"? Sorry to be so useless!
Huge thanks

Yeah the files needed will all be pretty hefty. So if thinking about going to a custom rom this would be a good time. Though wouldn't download one or the stock until you've seen if you can use it.
1. Yeah I did mean choose that option on that menu you have onscreen. Doesn't need to be attached to go to the screen technically, but won't be able to do anything there until it is connected so no benefit in not waiting until you are. No doesn't need to be rooted. You'd expect it to go to an almost blank screen with =>FASTBOOT mode.... on it in landscape.
2. On plus side you wouldn't need the adb drivers... But the fastboot ones are probably similarly tricky. These ones worked for me https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
Though I've not used XP.
If it will fastboot into twrp then you can put the original stock rom on or either of the custom ones from there, so it's not dead and can get to downloading. (or 5.1.1 stock using the safe twrp method)
Did you use a different cable on the machine you got it to work on then? If not probably not the cable.

Pond-life said:
Yeah the files needed will all be pretty hefty. So if thinking about going to a custom rom this would be a good time. Though wouldn't download one or the stock until you've seen if you can use it.
1. Yeah I did mean choose that option on that menu you have onscreen. Doesn't need to be attached to go to the screen technically, but won't be able to do anything there until it is connected so no benefit in not waiting until you are. No doesn't need to be rooted. You'd expect it to go to an almost blank screen with =>FASTBOOT mode.... on it in landscape.
2. On plus side you wouldn't need the adb drivers... But the fastboot ones are probably similarly tricky. These ones worked for me https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
Though I've not used XP.
If it will fastboot into twrp then you can put the original stock rom on or either of the custom ones from there, so it's not dead and can get to downloading. (or 5.1.1 stock using the safe twrp method)
Did you use a different cable on the machine you got it to work on then? If not probably not the cable.
Click to expand...
Click to collapse
Thanks for all your help Pond Life.
I had such difficulties get the files to download that in the end I gave up and rang Amazon and they offered to send me a replacement.
Sorry to bail out, this is all new to me and most of what everyone has said has me completely baffled so I've decided to take the easy way out.
Thank you again - I really appreciated all your advice.

FrankieChen said:
Thanks for all your help Pond Life.
I had such difficulties get the files to download that in the end I gave up and rang Amazon and they offered to send me a replacement.
Sorry to bail out, this is all new to me and most of what everyone has said has me completely baffled so I've decided to take the easy way out.
Thank you again - I really appreciated all your advice.
Click to expand...
Click to collapse
Better luck with the new one