Well, me being a little riskay was messing with my phone flashing new roms and themes and stuff kinda thinks I really may have bricked or fried my battery. The last thing I downloaded was a recovery image for the Mytouch from HTC. My phone attempted to boot back up and the HTC screen came on. I pulled the battery out b/c it wasn't going anywhere (pretty sure I didn't unplug from my computer ) And put my battery back in and tried to turn on. Anyways it won't charge, turn on or anything. Bricked or fried battery?
No bashing please, just asking a ? before I decide to make an executive decision !!
iluvmymytouch said:
Well, me being a little riskay was messing with my phone flashing new roms and themes and stuff kinda thinks I really may have bricked or fried my battery. The last thing I downloaded was a recovery image for the Mytouch from HTC. My phone attempted to boot back up and the HTC screen came on. I pulled the battery out b/c it wasn't going anywhere (pretty sure I didn't unplug from my computer ) And put my battery back in and tried to turn on. Anyways it won't charge, turn on or anything. Bricked or fried battery?
No bashing please, just asking a ? before I decide to make an executive decision !!
Click to expand...
Click to collapse
what phone do you have what was the exact thing you tried to flash where it messed up your phone? need more specific details
mt3g said:
what phone do you have what was the exact thing you tried to flash where it messed up your phone? need more specific details
Click to expand...
Click to collapse
Mytouch.... and the file similar to this but for the MYTOUCH
signed-dream_devphone_userdebug-ota-14721.
signed-google_ion-ota-14721.zip
ITS BRICKED lol went to tmobile and had them look at it no go...
Did you try to boot it in bootloader?
(VOLUME DOWN+POWER)
fezypoo said:
Did you try to boot it in bootloader?
(VOLUME DOWN+POWER)
Click to expand...
Click to collapse
Yep... a no go
iluvmymytouch said:
Yep... a no go
Click to expand...
Click to collapse
so all you did was flash the htc adp image and you bricked the phone?
mt3g said:
so all you did was flash the htc adp image and you bricked the phone?
Click to expand...
Click to collapse
Sure seems like it dont it. Im trying to mess with it now, but it's not working. power and vol down.... power and back.... etc etc etc.
iluvmymytouch said:
Sure seems like it dont it. Im trying to mess with it now, but it's not working. power and vol down.... power and back.... etc etc etc.
Click to expand...
Click to collapse
the only thing that shouldve bricked the phone was a radio flash an spl to my knowledge read up on installing adb and after its installed properly see if the phone is recognized when you turn it on if it is then you should be able to get it back
mt3g said:
the only thing that shouldve bricked the phone was a radio flash an spl to my knowledge read up on installing adb and after its installed properly see if the phone is recognized when you turn it on if it is then you should be able to get it back
Click to expand...
Click to collapse
It wont sync, turn on, charge, not recognized by my computer, nothing completely dead ... I already put it on ebay ... and got another... next time ill be more careful... lol thanks for the help!
iluvmymytouch said:
It wont sync, turn on, charge, not recognized by my computer, nothing completely dead ... I already put it on ebay ... and got another... next time ill be more careful... lol thanks for the help!
Click to expand...
Click to collapse
O I got what you said... Ive been having issues trying to download SDK for my computer. Windows says it's not installed properly..ive tried about a million dam times.
Different computer
Ok i think i figured it out. I ran CMD and typed C:\android-sdk-windows\tools then adb devices I don't see my device listed. Then adb shell :error device not found.
OK so i think not sure if this would do anything but when i put my sd card into my computer it tells me that there are problems with some of the files on my sd card. Im thinking that the recovery image that was flashed was corrupted.
Do we think making a gold card would maybe work??
Dead or Bricked?
I have the same situation...
I have recently bought a MT3G second hand....
When I first got the phone, it worked fine, but the battery was low, but I managed to wipe it before it eventually died (stooooppppiiiid).
Now, when I plug it in, nothing happens. When I hit the power button, the only thing that happens is the red LED blinks...thats it.
I tried multiple chargers, none of them work.
Is it bricked or is the battery dead?
wingman1986 said:
I have the same situation...
I have recently bought a MT3G second hand....
When I first got the phone, it worked fine, but the battery was low, but I managed to wipe it before it eventually died (stooooppppiiiid).
Now, when I plug it in, nothing happens. When I hit the power button, the only thing that happens is the red LED blinks...thats it.
I tried multiple chargers, none of them work.
Is it bricked or is the battery dead?
Click to expand...
Click to collapse
Try and swap out the battery I did have this happen within one month of buy a mytouch, same red led. Go into a store and ask them to swap in a new battery.
If it is the battery buy a new one and hold on to the packaging, put in the old battery and return it to a different tmobile
Related
A few days ago I bricked my phone. I performed a SPL flash which seemed to go ok, the phone rebooted and then just stuck at the first splash screen. I waited for 30 minutes and it was still there.
I then removed the battery, reinserted it, and tried booting into recovery mode. Nothing happened, it just stuck at the first splash screen.
So I removed the battery again, reinserted it, and tried booting into fastboot mode. Nothing happened, it just stuck at the first splash screen.
I repeated these steps a few times with the same result.
I tried booting it with the USB cable attached, the result was the same, and Windows showed the phone as an 'unrecognized device'.
At this point, I was nearly crying, my phone was a brick.
Then, for some reason I tried the following:
-On the PC, i ran the command 'fastboot boot recoveryimage.img'.
-At this point the command says 'waiting for device' (or something like that).
-I removed the battery.
-I Connected USB.
-I inserted the battery.
-I booted the phone while holding the HOME key.
-The phone still froze at the first splash screen, but then suddenly, the waiting fastboot command detected the phone and booted the recovery image! Yay!
That's it. I didn't test it any more thoroughly for obvious reasons, I just reflashed the SPL and everything was back to normal.
I hope this helps someone in the future....
Very nice..
wow seriously, didnt expected that..
good job mate!
btw wat did u do to cause the brick?
Just read the very first line of his post...
marcdbl said:
A few days ago I bricked my phone. I performed a SPL flash which seemed to go ok, the phone rebooted and then just stuck at the first splash screen. I waited for 30 minutes and it was still there.
[...]
Click to expand...
Click to collapse
mgear356 said:
btw wat did u do to cause the brick
Click to expand...
Click to collapse
As I said above, I had been flashing the SPL, and when I rebooted following the flash it was bricked (stuck at first splash screen).
It's weird, because once I managed to get back into fastboot, I simply flashed the same SPL again and it worked fine.
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
Never seen someone say the splash screen isn't coming up without blaming the hardware. I didn't think that flashing the wrong SPL would case the splash to not come up. I bricked my first phone by stupidly flashing the wrong SPL first before loading an OS. I thought the whole point of using the word 'brick' was when referring to the phone failing to enter 'fastboot' and 'recovery mode'. At that point, the phone would technically be a 'brick'. This has to be the first post I've seen with a possible fix but I could be wrong since I gave up on fixing that phone awhile ago.
goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
bricking means you can't get to fastboot or recovery no matter what you do.
so he counts as bricking.
this might be a fix for the haykuro spl bricked users..
Well done if we have HTC G1 user with brick phone who want to try this methode and give feedback
goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
No, You can still get to your splashscreen when the phone is bricked, If you cant turn on the phone then thats called the phone is dead not bricked. As stated already if you can't fastboot, or get to recovery then thats a brick.
Just tried it does not work and I was flash the death spl from haykuro,I am getting a new one but wanted to see if this works and I did not think it would which it didnt.
imfloflo said:
Well done if we have HTC G1 user with brick phone who want to try this methode and give feedback
Click to expand...
Click to collapse
Posted the fix on the android community forums. I have none person in mind, bricked it applying a spl, but he hasn't relied yet. Keep you informed if he does.
Did you reflash ROM after applying spl..? If you did and it still didn't boot then that should most likely be a brick. Can you boot into recovery right now and tell us your SPL version and radio?
goa200 said:
thats not really unbricking your phone. gotta be bricked meaning it wont even go to the splashscreen. and there is no way to unbrick it at that point. Still for those that end up in same situation as you this might help indeed.
Click to expand...
Click to collapse
Yes bricking your phone is when it wont even turn on! In the case of the sapphire when you hold power the led will flsh red quickly once then nothing.
On the blackstone you dont even get the pleasure of the led flash if your phone will turn on there is a way to get it fixed.
When ive been stuck on the bootscreen i have managed to revert using sappimg.nbh (which is 32b in my case) dunno where i got it from but i have it!
sappimg.zip (which is 32A) i got from Amon_RA's post and also have that, ive managed to revert back with both images after being stuck on "red screen of death"
A bit of a personal opinion here:
"Dead" is when the phone doesn't respond to anything, at all.
The charging light does not come on, the power button does nothing, and there is not so much as a flicker in the screen. Also, it is completely inaccessible for hardware debugging (JTAG, serial, USB or otherwise). This usually happens from a hardware problem, or doing something stupid like zero'ing the IPL.
Examples:
- My brother dropped his Nokia N75 in water. It's dead.
- I dropped my Cingular 8125 (HTC Wizard) on the ground. It doesn't power on any more, and plugging it into the charger does nothing. Voltmeter shows a charge running through some areas of the device's motherboard once disassembled. It's dead.
Solutions: Replace, recycle or sell for parts.
"Bricked" is when a purely software problem causes the device to no longer respond.
This may happen on many levels, but usually results in the OS not booting, or booting and being completely unusable (e.g. stopped with kernel panic at OS splash). It may light up and/or show a splash screen, but it fails to enter the bootloader or recovery menus. Its recoverability may vary, but will usually involve a debugging tool and a computer, and likely a copmlete wipe of everything on the device. Even if it's heavily bricked, if it can be recovered via JTAG or similar, it's not "dead".
Examples:
- HTC Dream only goes as far as splash screen, and freezes there. Does not respond to ADB. Does not enter recovery, or bootloader, however fastboot responds.
- HTC Dream shows blank screen, but lights up as if it were powering on. Fastboot does not respond. I connect my HTC ExtUSB Serial dongle to it though, and I'm able to get a response to some commands.
- Western Digital MyBook World Edition NAS powers on, and spins up hard drive, but does not go any farther than that. Front lights do not light up, and no hard disk activity is heard. Networking is not yet enabled. Hard drive can, however, manually be connected to a PC with SATA, and the firmware image re-written to its partitions.
- XBOX (the original) was softmodded, but the dashboard.xbe (the OS shell) was overwritten. It now just stays at the Microsoft logo.
- iPhone was recently jailbroken and SIM unlocked, then Apple pushed an update on me, and my iPhone is in a state where it doesn't enter DFU/Recovery, and when it boots, it says "Emergency calls only."
Solutions: Be very careful not to further brick the device, but use any methods available. Be sure to check documentations, search forums, and then ask questions if unsure. Make sure you finish every process you start.
After this, might just be hardware "damage" (like a power button not working right) or software "errors", like the home screen failing to load because of "Process com.google.android.gapps quit unexpectedly." These are usually relatively easy to fix, or have fixed.
Again, this is just an opinion.
Back on topic though, I seriously wouldn't have probably thought of using fastboot while it's stuck at the G1 screen, unless mine were bricked. Kudos to you, and I hope this works on some other bricked G1's out there (At least ones with the Engineering/Hard/DangerSPL, the stock SPL doesn't support fastboot as far as I know.)
bonesy said:
Yes bricking your phone is when it wont even turn on! In the case of the sapphire when you hold power the led will flsh red quickly once then nothing.
On the blackstone you dont even get the pleasure of the led flash if your phone will turn on there is a way to get it fixed.
When ive been stuck on the bootscreen i have managed to revert using sappimg.nbh (which is 32b in my case) dunno where i got it from but i have it!
sappimg.zip (which is 32A) i got from Amon_RA's post and also have that, ive managed to revert back with both images after being stuck on "red screen of death"
Click to expand...
Click to collapse
Won't agree with that, what you describe as a brick is a DEAD mobile. A brick is a useless piece which wont get into any state of recovery. The only thing i will agree with is that if it'll turn on there is a way to get it fixed that's why we even got the word unbricking which is done with many other pieces than Android mobiles.
Hope this will get us closer to a unbricking method which works on all the BRICKED pieces out there.
Good job dude!
Yes, my phone is back!
I bricked my G1 about 2 months ago pretty much the same way marcdbl did.
I gave up on it and sit it aside getting a new MT3G.
Sweet, now I got 2 phones to play with.
Thank You marcdbl
wow sweet news
fishman0919 said:
Yes, my phone is back!
I bricked my G1 about 2 months ago pretty much the same way marcdbl did.
I gave up on it and sit it aside getting a new MT3G.
Sweet, now I got 2 phones to play with.
Thank You marcdbl
Click to expand...
Click to collapse
Very glad to hear that your dead or bricked or whatever-you-may-call phone is back to LIVE!!!
So I think this solution works for some certain people. So i think rather than arguing on terminology, better spread this good trick to people who had dead/bricked/whatevery-you-may-call phone. IMHO
Thanks for the solution.
Best,
Thihaz
marcdbl said:
A few days ago I bricked my phone. I performed a SPL flash which seemed to go ok, the phone rebooted and then just stuck at the first splash screen. I waited for 30 minutes and it was still there.
I then removed the battery, reinserted it, and tried booting into recovery mode. Nothing happened, it just stuck at the first splash screen.
So I removed the battery again, reinserted it, and tried booting into fastboot mode. Nothing happened, it just stuck at the first splash screen.
I repeated these steps a few times with the same result.
I tried booting it with the USB cable attached, the result was the same, and Windows showed the phone as an 'unrecognized device'.
At this point, I was nearly crying, my phone was a brick.
Then, for some reason I tried the following:
-On the PC, i ran the command 'fastboot boot recoveryimage.img'.
-At this point the command says 'waiting for device' (or something like that).
-I removed the battery.
-I Connected USB.
-I inserted the battery.
-I booted the phone while holding the HOME key.
-The phone still froze at the first splash screen, but then suddenly, the waiting fastboot command detected the phone and booted the recovery image! Yay!
That's it. I didn't test it any more thoroughly for obvious reasons, I just reflashed the SPL and everything was back to normal.
I hope this helps someone in the future....
Click to expand...
Click to collapse
where were you 2 months ago dude? I paid 270€ to change the board on my magic
Good Job! Thanks for the info
Hi
So last night when I flashed my new created ROM with CWM, it seems like I ruined my boot loader, and from that I can't find the way to recover
SYMPTOMS:
- black screen
- power button doesn't do anything
- no button combination boots to download mode
- no charghing indication when connected to charger or USB
- no detection in the computer when connected to the USB
Is this the real black screen of death?
How did I get there?
I flashed a ROM through CWM, when it finished I selected reboot from CWM, and since then, all I see is black screen, no indication whatsoever to powering up.
I didn't try a USB JIG yet, but I will at Thursday (meet with a friend that has one)
as far as I understand the only way to recover from this is using a RIFF Box JTAG which requires, taking apart the phone, and soldering small wires to the board, and then reload the boot loader
Where do we go from here?
If it happened to you Please write down:
how did it happened to you?
what did you do to try to recover?
did you mange to recover?
if you did, how did you?
Why is this post so important to everyone?
Because if it didn't happen to you yet it might happen in your next CWM flashing.
So its very important to find a solution or at least the way to prevent it.
- update 31/12/2010 -
Cause
corrupted boot loader , bad sbl.bin flashing
Prevention:
do not flash roms/addons/fixes with sbl.bin
if you must flash sbl.bin, do it while you are sure that your USB configuration is perfect, and do it as less as possible.
Solution (for those who already bricked to black)
you're not gonna like it
find riffbox jtag....
marcelo.waisman said:
Hi
So last night when I flashed my new created ROM with CWM, it seems like I ruined my boot loader, and from that I can't find the way to recover
SYMPTOMS:
- black screen
- power button doesn't do anything
- no button combination boots to download mode
- no charghing indication when connected to charger or USB
- no detection in the computer when connected to the USB
Is this the real black screen of death?
How did I get there?
I flashed a ROM through CWM, when it finished I selected reboot from CWM, and since then, all I see is black screen, no indication whatsoever to powering up.
I didn't try a USB JIG yet, but I will at Thursday (meet with a friend that has one)
as far as I understand the only way to recover from this is using a RIFF Box JTAG which requires, taking apart the phone, and soldering small wires to the board, and then reload the boot loader
Where do we go from here?
If it happened to you Please write down:
how did it happened to you?
what did you do to try to recover?
did you mange to recover?
if you did, how did you?
Why is this post so important to everyone?
Because if it didn't happen to you yet it might happen in your next CWM flashing.
So its very important to find a solution or at least the way to prevent it.
BTW I think its a developers post, because we need developers creative way of thinking to find a solution
Click to expand...
Click to collapse
Happened to me too. I was tinkering with the Armani source to hopefully find something of use for Axura, and I bricked it. Same things happened to me. I called att and got a new one.
marcelo.waisman said:
Hi
So last night when I flashed my new created ROM with CWM, it seems like I ruined my boot loader, and from that I can't find the way to recover
SYMPTOMS:
- black screen
- power button doesn't do anything
- no button combination boots to download mode
- no charghing indication when connected to charger or USB
- no detection in the computer when connected to the USB
Is this the real black screen of death?
How did I get there?
I flashed a ROM through CWM, when it finished I selected reboot from CWM, and since then, all I see is black screen, no indication whatsoever to powering up.
I didn't try a USB JIG yet, but I will at Thursday (meet with a friend that has one)
as far as I understand the only way to recover from this is using a RIFF Box JTAG which requires, taking apart the phone, and soldering small wires to the board, and then reload the boot loader
Where do we go from here?
If it happened to you Please write down:
how did it happened to you?
what did you do to try to recover?
did you mange to recover?
if you did, how did you?
Why is this post so important to everyone?
Because if it didn't happen to you yet it might happen in your next CWM flashing.
So its very important to find a solution or at least the way to prevent it.
BTW I think its a developers post, because we need developers creative way of thinking to find a solution
Click to expand...
Click to collapse
Did you try removing battery and putting it back and then opening ODIN, holding the volume up/down and inserting the usb to bring it on the download mode. I guess I might have experience almost similar issue with one of the rom. I almost freaked out. Phone wont show if its charging. It wont mount on the pc. But tried all the possible method available several times including adb shell command. And finally I did hear the magical sound from window when the usb is connected and finally it did work.
Also try the adb method if it doesn't go into download mode using volume button combo.
Sent from my SAMSUNG-SGH-I897 using XDA App
Did u remove sbl.bin
Sent from my SAMSUNG-SGH-I897 using XDA App
Happened to me the first time I ran the OTA update from ATT. Paused the update, and when I resumed it - the phone though I finished downloading the JH7 update and tried to apply it.
It failed to apply and when it went to restart, it never powered on. No download mode, recovery, USB power, Odin, nothing. It was completely dead.
I got it replaced at the AT&T store.
If sbl.bin was removed or corrupted you should call the warranty center. Tell them ota update bricked your phone. Lol good luck
sent from my cappy running di11igaf's rom v2.5 at 1280mhz!!
I think it is just bad luck. I was once being careless and had the battery fall out of my phone while flashing, it interrupted the flash and I was still able to get in download mode to Odin it. Needless to say, I'll never flash again without the back cover on
bulletproof1013 said:
Did u remove sbl.bin
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yes i'ts probably a bad sbl.bin, but I didn't remove it I flashed a new one, most of the rom's do the same
yeah sounds like it...sry for your luck.but seems like its toast then. keep us posted
But if you had a batch 1008 captivate and you messed up during and Odin flash to stock then your screwed bcuz Odin one click swaps the sbl.bins to make your button combinations impossible. ADB would work but you obviously can't access that. I too have a 1008 and it sucks, that is why I bought a jig.
silverslotcar said:
But if you had a batch 1008 captivate and you messed up during and Odin flash to stock then your screwed bcuz Odin one click swaps the sbl.bins to make your button combinations impossible. ADB would work but you obviously can't access that. I too have a 1008 and it sucks, that is why I bought a jig.
Click to expand...
Click to collapse
There is a a way. Whenever you need to flash to stock you must use following stock. http://forum.xda-developers.com/showthread.php?t=818439
This is same as normal stock posted by DG except that it includes sbl.bin that we (1008) need. I use it everytime and 3 button combos for Download, Recovery work great.
silverslotcar said:
But if you had a batch 1008 captivate and you messed up during and Odin flash to stock then your screwed bcuz Odin one click swaps the sbl.bins to make your button combinations impossible. ADB would work but you obviously can't access that. I too have a 1008 and it sucks, that is why I bought a jig.
Click to expand...
Click to collapse
it seems like this is not my case
I'm still looking for other people who had my case, and recovered (even with the JTAG riff box) or at least find someone who know's what we shouldn't do, so we don't break our phones.
so whats batch 1008?
This happened to me last night. I was trying to flash the Darky port via CWM and during the flash it became unresponsive. I had to pull the battery. This caused 2 different things. Sometimes it would be a never ending loop of boot screens and then others it would just go into recovery where it wouldn't let me do anything.
From here luckily I was able to access download mode by using the "adb reboot download" command. So I then got into dl mode and tried to flash stock (not the 3 button fixed one) and it froze on FACTORYFS (or whatever it is). I had no choice but to pull the battery. Now it won't boot at all. So my assumption is it wiped the bootloader. I'm not 100% sure but I feel that the reason it stopped where it did was because I didn't run odin as admin on my Win7 pc. I read in another thread that someone had the same problem when they didn't do that either.
If you are in a pitch black room and you press power you can see your screen illuminate, it's just very dim.
I have batch 1008 if it makes any difference to anyone.
Either way I'm heading to the device support center in a half hour or so to try to get a replacement. I originally was going to make or order a jig but people are saying it only works if the bootloader is intact. I originally had hopes because one person claimed that they recovered a completely dead phone with it, but upon further reading all others could not. It seems like his phone may not have been completely bricked.
Update:
Just got back from the at&t device support center. They gave me a new phone without any hassle. They asked what was wrong with my phone and I told them that I was trying to update it and now it won't turn on. The guy tried a few combinations of button presses and tried hooking it up to a jig-like device. Nothing worked so he just gave me a refurbished phones. No questions asked. As I was walking out he said a few people have had the same issue so it's not a big deal.
Either way I thought this would help to realize that there is likely no way to get the phone to boot unless you have a jtag handy.
I don't feel safe to flash rom via CWM.
If you really want to do that, delete the bootloader inside the .zip
So i think i killed mine too
so i get black screen, two button combo gives me SEC S5PC110 Test B/d
I opened odin but nothing Is this toast?
I had this exact problem over thanksgiving weekend. My phone was was was hard bricked I was getting the "phone + computer" it took some effort to get it into download but I got it there and when I was recovering with odin the connection got lost the screen went blue and then nothing. It was dead totally unresponsive no charging or boot screen nothing but once I got a black screen with redlines. After a lot of attempts to revive it I gave up called ATT warranty for a replacement. Luckily I opted for the slow mail service and kept reading. Yesterday I saw the above post and now I can say "yes even now your phone is not bricked even though it does NOTHING"
step 1) first thing I did was charge the battery with my replacement phone as the bricked phone was no longer able to charge the battery
step 2) open odin1 click and hooked up the usb to the phone and computer no battery
step 3) inserted the battery holding only volume up+down
step 4) "BOOM" download mode and a happy dance
I posted this in the"read before flashing" thread there are other people who have recovered from this and now I think that the extra trick to this is getting a 100% battery you need this to flash, and state the phone is in now wont charge a battery.
hope this sound encouraging
silverslotcar said:
But if you had a batch 1008 captivate and you messed up during and Odin flash to stock then your screwed bcuz Odin one click swaps the sbl.bins to make your button combinations impossible. ADB would work but you obviously can't access that. I too have a 1008 and it sucks, that is why I bought a jig.
Click to expand...
Click to collapse
It's odd because I keep seeing people saying things like this. I, too, have a 1008 Captivate. My button combos have worked from day one and Odin one click has never messed that up. Maybe I'm just lucky?
Sent from my SAMSUNG-SGH-I897 using XDA App
RKight said:
It's odd because I keep seeing people saying things like this. I, too, have a 1008 Captivate. My button combos have worked from day one and Odin one click has never messed that up. Maybe I'm just lucky?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I believe there's a "fixed" 1008 batch. Not all 1008s are going to have the problem.
norcal einstein said:
I believe there's a "fixed" 1008 batch. Not all 1008s are going to have the problem.
Click to expand...
Click to collapse
Yeah it's either that or just a misconception spread by the community. Both my old captivate and replacement were 1008. I have been able to get into recovery via the power+volume combination. I was also able to get into dl mode using the vol+insert usb combination.
It's possible I just got lucky on both but who knows.
I, and many others have a 1008 that don't go into download or recovery via the button combos without fixing sbl.bin.
Sent from my SAMSUNG-SGH-I897 using XDA App
ok here is my problem i rooted my mt4g then i tried to re rom it using cwr the phone was in bootloop so i tried reflashing and reflashing thinking i was doing something wrong then I downloaded PD15IMG pulled the battery to shut the phone off before i got to reflash and it hasnt turn on since when i plug it into the pc i detects it as qhsusb_dload I dont have warranty and i dont have another phone to use really dont want to dish out anymore money i just got the phone like 2 days ago someone please help
synej6 said:
ok here is my problem i rooted my mt4g then i tried to re rom it using cwr the phone was in bootloop so i tried reflashing and reflashing thinking i was doing something wrong then I downloaded PD15IMG pulled the battery to shut the phone off before i got to reflash and it hasnt turn on since when i plug it into the pc i detects it as qhsusb_dload I dont have warranty and i dont have another phone to use really dont want to dish out anymore money i just got the phone like 2 days ago someone please help
Click to expand...
Click to collapse
Oh man, when you were constantly reflashing did you wipe before you reflashed? And it wont get back into clockwork or fastboot?
mackster248 said:
Oh man, when you were constantly reflashing did you wipe before you reflashed? And it wont get back into clockwork or fastboot?
Click to expand...
Click to collapse
yea i wiped then reflash it was going back to fastboot for a while until figured out to just flash the stock rom and just do the process all over again but by that time the phone was on while i downloaded it and when i went to turn it off to get into bootloader it never turned back on I tried taking everything out let it sit then put the battery back nothing then I thought the battery was dead so i plugged it to the ac charger and i get no red amber or green light, then i thought the battery was damaged but when i plugged to the pc this morning it was detected but as qhsusb_dload ever since then i been searching for the driver for it but no luck
28 views and only 1 reply guys please help
synej6 said:
28 views and only 1 reply guys please help
Click to expand...
Click to collapse
It sounds like you bricked yourself. Providing more info may help. How did you root? Did you use ROM manager? What version of clockwork were you using. Do you have engineering bootloader. What Rom did you try and flash? What version were you on? Be as specific as you can and the great team of guys/girls here can walk you through it , if it's recoverable at this point.
Coppo said:
It sounds like you bricked yourself. Providing more info may help. How did you root? Did you use ROM manager? What version of clockwork were you using. Do you have engineering bootloader. What Rom did you try and flash? What version were you on? Be as specific as you can and the great team of guys/girls here can walk you through it , if it's recoverable at this point.
Click to expand...
Click to collapse
rooted with gfree
yes i used rom manager not sure what version of clockwork
what is engineering bootloader?
Rom:Royal_Panache_v1_2.zip
andriod 2.2.1
thanks
anyone?????????
synej6 said:
anyone?????????
Click to expand...
Click to collapse
Do you have ADB installed with the usb drivers? If not I would do that and then run adb devices and see if your phone shows up. If that doesn't work I would either get a new battery to see if you can at least get to the bootloader and then revert to stock or call HTC at 866-449-8358 and play the victim card. Good luck!
if you pull the battery and put it back in. Hold down the power button and the volume down rocker on the volume controls. Can you get into hBoot?
Mcoddt said:
Do you have ADB installed with the usb drivers? If not I would do that and then run adb devices and see if your phone shows up. If that doesn't work I would either get a new battery to see if you can at least get to the bootloader and then revert to stock or call HTC at 866-449-8358 and play the victim card. Good luck!
Click to expand...
Click to collapse
ADB doesn't detect it i tried then i made the pc think it was a android phone and still nada, I'm just gonna end up calling htc and cry to them lol
neidlinger said:
if you pull the battery and put it back in. Hold down the power button and the volume down rocker on the volume controls. Can you get into hBoot?
Click to expand...
Click to collapse
i wish i could if it would power up and go into hboot i would just use the pmd15.zip
I will try to keep this short but... it wont be. Please don't press that back button!
I had 4.4 on my VZ980 rooted device with a custom ROM but I felt like cleaning it up and starting over (phone was acting up a bit, nothing major) so I went ahead and unrooted it successfully back to factory stock. While unrooted I downloaded the new 12b update... just to check it out. After that lost my attention span within 2 seconds, I decided to flash back to 10b and root again. Everything went perfectly.
After rooting I immediately went and put TWRP on my phone (still stock rooted).. but it would not let me flash 2.6.3.4 only 2.6.3.2... which shouldn't have been a big deal but I.. brilliantly decided NO! I WANT 2.6.3.4... yadda yadda tried a couple different ways, then I read about flashify. Attempted to flashify the file and it still did not work. Within a couple of minutes my phone turned off.... no big deal I thought... WRONG!
My phone is stuck on the LG splash screen. It will not boot into recovery mode... it gets stuck on the factory hard reset saying "factory reset processing" no Teamwin logo ever comes up.. no matter how long I let it sit there
Next move was download mode obviously. But alas, that to bit the big one.. and before you ask I tried every possible button combination.. I was making up my own combinations in desperation. The only things I can bring up are factory hard reset and the hardware key control mode.
Heres the big problem. My phone is not recognized (tried on the factory reset screen and hardward key mode too)... not drivers, not ADB, not even the QHUSB_DLOAD that has been populating the scene lately. I tried downloading everything. Different flash tools, different drivers, different USB cords, different computers, I even tried to use a different OS to see if i could get a reaction.. Nothin! Tried LGNPST, QPST, you name it... I tried it! I even took apart the phone, took out the battery and put it back together (I did this with a previous phone stuck on splash screen and it actually made it work again) still sitting on that ugly splash screen.
Is there any thing I am missing.. that I could possibly try? If not... if it is truly bricked then I need help on how to make it so my provider will not see that it says "Rooted" in the top left corner when they try to put it in factory reset mode.
ANY QUESTIONS/SUGGESTIONS ARE WELCOME! Thank you so much for reading my novela! :good:
brittany.18424 said:
I will try to keep this short but... it wont be. Please don't press that back button!
I had 4.4 on my VZ980 rooted device with a custom ROM but I felt like cleaning it up and starting over (phone was acting up a bit, nothing major) so I went ahead and unrooted it successfully back to factory stock. While unrooted I downloaded the new 12b update... just to check it out. After that lost my attention span within 2 seconds, I decided to flash back to 10b and root again. Everything went perfectly.
After rooting I immediately went and put TWRP on my phone (still stock rooted).. but it would not let me flash 2.6.3.4 only 2.6.3.2... which shouldn't have been a big deal but I.. brilliantly decided NO! I WANT 2.6.3.4... yadda yadda tried a couple different ways, then I read about flashify. Attempted to flashify the file and it still did not work. Within a couple of minutes my phone turned off.... no big deal I thought... WRONG!
My phone is stuck on the LG splash screen. It will not boot into recovery mode... it gets stuck on the factory hard reset saying "factory reset processing" no Teamwin logo ever comes up.. no matter how long I let it sit there
Next move was download mode obviously. But alas, that to bit the big one.. and before you ask I tried every possible button combination.. I was making up my own combinations in desperation. The only things I can bring up are factory hard reset and the hardware key control mode.
Heres the big problem. My phone is not recognized (tried on the factory reset screen and hardward key mode too)... not drivers, not ADB, not even the QHUSB_DLOAD that has been populating the scene lately. I tried downloading everything. Different flash tools, different drivers, different USB cords, different computers, I even tried to use a different OS to see if i could get a reaction.. Nothin! Tried LGNPST, QPST, you name it... I tried it! I even took apart the phone, took out the battery and put it back together (I did this with a previous phone stuck on splash screen and it actually made it work again) still sitting on that ugly splash screen.
Is there any thing I am missing.. that I could possibly try? If not... if it is truly bricked then I need help on how to make it so my provider will not see that it says "Rooted" in the top left corner when they try to put it in factory reset mode.
ANY QUESTIONS/SUGGESTIONS ARE WELCOME! Thank you so much for reading my novela! :good:
Click to expand...
Click to collapse
you know download mode is volume up + usb right?
datechnerd said:
you know download mode is volume up + usb right?
Click to expand...
Click to collapse
I sure do! The phone is recognizing that its plugged into something but it doesn't seem to send any signal out. I have tried to get into DL mode hundreds of times over the past 2 days. The phone is responding to the USB but not sending anything to the computers is what it seems like.
brittany.18424 said:
I sure do! The phone is recognizing that its plugged into something but it doesn't seem to send any signal out. I have tried to get into DL mode hundreds of times over the past 2 days. The phone is responding to the USB but not sending anything to the computers is what it seems like.
Click to expand...
Click to collapse
proper drivers installed?
datechnerd said:
proper drivers installed?
Click to expand...
Click to collapse
Yep, I tried several different types.. latest update, the LG VZW united WHQL_2.11.1 (not sure of exact phrasing), Qualcomm, ADB wont recognize it either. I tried this on 2 different computers, both computers can easily recognize other phones/tablets/etc.
brittany.18424 said:
Yep, I tried several different types.. latest update, the LG VZW united WHQL_2.11.1 (not sure of exact phrasing), Qualcomm, ADB wont recognize it either. I tried this on 2 different computers, both computers can easily recognize other phones/tablets/etc.
Click to expand...
Click to collapse
is it showing up somewhere else in device manager (when the phone connected in download mode)
datechnerd said:
is it showing up somewhere else in device manager (when the phone connected in download mode)
Click to expand...
Click to collapse
The phone will not go into download mode. when I do the Vol+ key and usb the splash screen just remains there. But no, it is not showing up any where in the device manager I went through everything.
brittany.18424 said:
The phone will not go into download mode. when I do the Vol+ key and usb the splash screen just remains there. But no, it is not showing up any where in the device manager I went through everything.
Click to expand...
Click to collapse
you did the combo with the phone off right?
datechnerd said:
you did the combo with the phone off right?
Click to expand...
Click to collapse
yep, phone was off, when pressing the vol+ and inserting usb the LG splash screen would appear but the download mode did not follow afterwards. It just stays on the LG screen until I turn it off again.
brittany.18424 said:
yep, phone was off, when pressing the vol+ and inserting usb the LG splash screen would appear but the download mode did not follow afterwards. It just stays on the LG screen until I turn it off again.
Click to expand...
Click to collapse
alright try a safemode boot
hold power and volume down, when lg logo comes up let go of power and keep holding volume down until you see safe mode or safeboot or something with safe xD
datechnerd said:
alright try a safemode boot
hold power and volume down, when lg logo comes up let go of power and keep holding volume down until you see safe mode or safeboot or something with safe xD
Click to expand...
Click to collapse
Alrighty! I am going to try that now.. thank you for you help thus far... greatly appreciated! don't go far i'll have a result in a moment haha
brittany.18424 said:
Alrighty! I am going to try that now.. thank you for you help thus far... greatly appreciated! don't go far i'll have a result in a moment haha
Click to expand...
Click to collapse
i've spent the last two days doing just this for people
datechnerd said:
i've spent the last two days doing just this for people
Click to expand...
Click to collapse
I'm sure I've learned quite a bit from you then! (been lurking over every "brick" post trying to figure this out) Ok, so I tried that.. first unplugged and when that didn't work I tried it plugged in... Still will not leave the LG screen though.
brittany.18424 said:
I'm sure I've learned quite a bit from you then! (been lurking over every "brick" post trying to figure this out) Ok, so I tried that.. first unplugged and when that didn't work I tried it plugged in... Still will not leave the LG screen though.
Click to expand...
Click to collapse
hmmmm... this one might have me. I'll look around
datechnerd said:
hmmmm... this one might have me. I'll look around
Click to expand...
Click to collapse
Yeah it's been driving me crazy, i tried to be as thorough as I could trying every option, but everything I thought of hasn't worked. It's going on 2 days of trial and error (but believe me I am no expert on this stuff yet, def still learning... the hard way) I do have warranty, but it says rooted in the factory hard reset (when attempting to get to TWRP but it freezes or wont load) so thats another problem!
brittany.18424 said:
I'm sure I've learned quite a bit from you then! (been lurking over every "brick" post trying to figure this out) Ok, so I tried that.. first unplugged and when that didn't work I tried it plugged in... Still will not leave the LG screen though.
Click to expand...
Click to collapse
any experience with any version of linux?
http://forum.xda-developers.com/showthread.php?t=2582142
in theory you could follow that and just pick the stock files for your g2
datechnerd said:
any experience with any version of linux?
http://forum.xda-developers.com/showthread.php?t=2582142
in theory you could follow that and just pick the stock files for your g2
Click to expand...
Click to collapse
I actually already tried that, I made sure I downloaded the correct files for my model as well. My problem is "5- LG detected as qhsusb_bulk in device manager" I have no sign of computers recognizing my phone, even on linux (which I think may be the reason I cant get into DL mode... possibly)
brittany.18424 said:
I actually already tried that, I made sure I downloaded the correct files for my model as well. My problem is "5- LG detected as qhsusb_bulk in device manager" I have no sign of computers recognizing my phone, even on linux (which I think may be the reason I cant get into DL mode... possibly)
Click to expand...
Click to collapse
It's times like this I wish I had the troubled device
datechnerd said:
It's times like this I wish I had the troubled device
Click to expand...
Click to collapse
I told you I was thorough! I mean.. I took it apart haha! But I feel like there has got to be SOMETHING considering my phone is recognizing when I plug in the USB but no computer or operating system will recognize it no matter what drivers (or random methods... I got creative.. none of it worked... but creative at least)
brittany.18424 said:
I told you I was thorough! I mean.. I took it apart haha! But I feel like there has got to be SOMETHING considering my phone is recognizing when I plug in the USB but no computer or operating system will recognize it no matter what drivers (or random methods... I got creative.. none of it worked... but creative at least)
Click to expand...
Click to collapse
well good creative is what this looks like its going to take
Today, I attempt to root my G2 and i done so successfully. After I attempted to add a recovery via Flashify as told to me from someone from this site and it softed bricked my phone to where i only powered on to fastboot mode. After researching further I attempted the ubuntu fix for the situation and after I cant turn my phone on and there is no charge light indication. HELP PLZ
deetea48601 said:
Today, I attempt to root my G2 and i done so successfully. After I attempted to add a recovery via Flashify as told to me from someone from this site and it softed bricked my phone to where i only powered on to fastboot mode. After researching further I attempted the ubuntu fix for the situation and after I cant turn my phone on and there is no charge light indication. HELP PLZ
Click to expand...
Click to collapse
hold power down for 20 seconds. let phone sit for 1 minute. now hold power and volume down. this should bring you to a white reset screen. press power 3 times.
gentlemandroid17 said:
hold power down for 20 seconds. let phone sit for 1 minute. now hold power and volume down. this should bring you to a white reset screen. press power 3 times.
Click to expand...
Click to collapse
i tried that and nothing happened.
When you plug in USB does charge light come on. Sounds like a battery went dead.
Sent from my LG-D802 using Tapatalk
I've heard some people are having issues with the charge port and/or cord also. Maybe try another cord and make sure it's plugging in tightly? I think the last person covered everything else.
gentlemandroid17 said:
When you plug in USB does charge light come on. Sounds like a battery went dead.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
No charge light at all =/
I had the same problem, it occured while switching from cwm to twrp. i used the unbuntu method ( i think you mean this right here: http://forum.xda-developers.com/showthread.php?t=2582142)
are you sure you were in fastboot mode? because i wasnt and it should say so in the top left corner if you were.
try different cords/ usb ports or even pc's to charge it. my mac couldn't find it at all, my windows did.
UnknownCloakedMan said:
I've heard some people are having issues with the charge port and/or cord also. Maybe try another cord and make sure it's plugging in tightly? I think the last person covered everything else.
Click to expand...
Click to collapse
Cord charge my tab just fine, therefore im assuming the cord is fine... i think
i have the same problem
deetea48601 said:
Today, I attempt to root my G2 and i done so successfully. After I attempted to add a recovery via Flashify as told to me from someone from this site and it softed bricked my phone to where i only powered on to fastboot mode. After researching further I attempted the ubuntu fix for the situation and after I cant turn my phone on and there is no charge light indication. HELP PLZ
Click to expand...
Click to collapse
I have the same problem my phone is completly dead i don't know what else can i do, the linux tutorial doesn't work because the pc don't detects the phone
did tou guys check if the twrp image you downloaded was correct size? Wonder if a bad download could cause this.
bachera said:
did tou guys check if the twrp image you downloaded was correct size? Wonder if a bad download could cause this.
Click to expand...
Click to collapse
For me the brick happened when i was flashing KK with TWRP, during the flashing appears something that said "couldn't not mount system" and the phone shut down and never power up again , no usb no charge, no linux, no nothing, when i plug my device in windows appears that the devices cannot install the drivers, and i've tried all the drivers and still doesn't work
Hold power down until phone is completely off. Then, hold power and down volume until you see LG logo. As soon as you see the LG logo, release and then quickly press power and down again. Hold until you see a white screen. Then go from there.
techbeck said:
Hold power down until phone is completely off. Then, hold power and down volume until you see LG logo. As soon as you see the LG logo, release and then quickly press power and down again. Hold until you see a white screen. Then go from there.
Click to expand...
Click to collapse
i've tried all the possible combinations of buttons and no one works, i've been holding the power button for a whole minute and nothing happened, and the other combination either, nothing seems to work i give up
It's just power you press after the logo, not power and volume down.
pimfram said:
It's just power you press after the logo, not power and volume down.
Click to expand...
Click to collapse
There's no logo, 'cause it doesn't turn on by any means , no matter what button or combination i press, there's no response.
Thanks
Have you tried getting into download mode?
pimfram said:
Have you tried getting into download mode?
Click to expand...
Click to collapse
i've tried everything, download mode, linux, recovery, lg mobile, and nothing works i think it's completly brick, i hope one day someone comes with the solution, because i went today to SAT and they don't even know what happened with my phone, and i bought it in another country so they don't want to get involve
So all you get is a black screen with you boot? There's probably a way to push whatever file might be missing or even an entire ROM but I lack the knowledge on how to do that. I remember I had to work some magic on my Galaxy Nexus but I used a toolkit so I'm afraid I've got no really useful information for you.
This also happened to me!
I am in the same state.
I rooted the LG, I installed the custom Rom, I installed an updated GAPPS and it wasnt working. I then went and installed another GAPPS overtop and I got stuck in boot loop. After I tried recovery from ADB I tried to restore from TRWP and it didnt take. After I rebooted nothing turned on, no LED, I tried ALL button combinations and nothing comes on at all. I am wondering if the phone died and now will not charge...I started with 60% but the last time i saw it it was down to 15% just thinking maybe it died completely and without any software to boot it wont charge...I have had it on charge for 8 hrs since and still nothing...
Please help!
Bobert the great said:
I am in the same state.
I rooted the LG, I installed the custom Rom, I installed an updated GAPPS and it wasnt working. I then went and installed another GAPPS overtop and I got stuck in boot loop. After I tried recovery from ADB I tried to restore from TRWP and it didnt take. After I rebooted nothing turned on, no LED, I tried ALL button combinations and nothing comes on at all. I am wondering if the phone died and now will not charge...I started with 60% but the last time i saw it it was down to 15% just thinking maybe it died completely and without any software to boot it wont charge...I have had it on charge for 8 hrs since and still nothing...
Please help!
Click to expand...
Click to collapse
I'm afraid to tell you, but our phones die there's nothing to do to saved them, we just have to keep them in that state meanwhile the solution comes up, because in this very moment there's nothing we can do