Related
Hey guys I think I actually did it. I was going to install the JPC Froyo Rom, and somehow booted into recovery in the ROM. Now whenever I turn the phone on it boots into recovery, and none of the button combinations work for putting it into Download mode so I can flash back to stock. On the i9000 thread it says that if you get into this situation you cannot flash back. Any of you guys run into this issue? If not then it looks like I'll be trying to convince an ATT rep to give me a new phone
Try powering off... Then hold vol up and down buttons then plug in usb.... That happened to me... Your not bricked
Sent from my SAMSUNG-SGH-I897 using XDA App
Connect to adb and run reboot command
Sent from my GT-I9000 using XDA App
Nope
Nope sorry guys I know all of what you just said. As for plugging in USB while holding volume buttons, it'll just go to that battery charging screen, and adb doesn't work because it doesn't boot past recovery. Sorry guys but yes it was bricked. It's okay though because I just went to ATT and since they can't identify the problem they just replaced the phone
Thought mine was bricked one night, too. Same scenario. Tried dropping the SIM and SD card out even though I didn't think it would make a difference, but it did. Got to download screen and reflashed with ODIN.
Good luck.
Sent from my SAMSUNG-SGH-I897 using XDA App
KCutrer1 said:
Nope sorry guys I know all of what you just said. As for plugging in USB while holding volume buttons, it'll just go to that battery charging screen, and adb doesn't work because it doesn't boot past recovery. Sorry guys but yes it was bricked. It's okay though because I just went to ATT and since they can't identify the problem they just replaced the phone
Click to expand...
Click to collapse
If you pull the battery, then put the battery in. hold both volume buttons buttons, and then plug the phone into the computer, it didn't boot to download?
Im curious if you even tried to use the Odin one click thread
There are 4 or 5 ways in that thread on how to get to download mode. And how exactly does this relate to development...just another curious thought. Well, you are getting a new phone, just hope that ATT or Samsung don't try to figure out the cause of your phone being "bricked".
AGAIN!
Okay after this I swear I won't be messing around with Froyo anymore. Here's the story: I got into download on the replacement captivate. Tried to install JPC froyo, but it never started flashing so I unplugged it from Odin and then tried to turn it back on. It goes to the normal "connect phone to computer" screen. However no attempts to get back into download mode have worked. Holding both volume buttons and power until second black screen doesn't work, booting while holding volume down doesn't work, holding both volume buttons and then inserting USB cable doesn't work. I think I'm stuck in this screen unless there's some incredible way I have yet to try. Anybody have any ideas? I would greatly appreciate feedback from the experienced users (Zilch25, designgears, kaik, reaver117), because I think I'd be pushing it trying to get it replaced a second time in such rapid succession
To flashman2002:
I put it in this section because it's in the development section that most flashing and such occurs so I thought there would be the greatest knowledge base. And yes I've pored over the one click thread and none of the methods mentioned there have any effect!
Jeez, I just scared the **** out of myself. I ran the remove lagfix script and it rebooted my phone but it was just a black screen. So I take the battery out. Bad Idea. It showed the ATT screen but just black after that. I could get it into recovery mode but not download. Then I messed some more and would only show a vague disconnected pic.
Finally I got it into download by doing this: (had odin open before hand)
1. took everything out including sim and usb cable.
2. quickly inserted battery and held volume buttons and very quickly inserted usb.
I'm pretty sure its the speed that matters because I tried about 4 times and only when I did it really fast did it work.
ThisWasATriumph said:
Jeez, I just scared the **** out of myself. I ran the remove lagfix script and it rebooted my phone but it was just a black screen. So I take the battery out. Bad Idea. It showed the ATT screen but just black after that. I could get it into recovery mode but not download. Then I messed some more and would only show a vague disconnected pic.
Finally I got it into download by doing this: (had odin open before hand)
1. took everything out including sim and usb cable.
2. quickly inserted battery and held volume buttons and very quickly inserted usb.
I'm pretty sure its the speed that matters because I tried about 4 times and only when I did it really fast did it work.
Click to expand...
Click to collapse
Nope. Unless you can do this with godly speed I dont think it'll work. I just got to the "Connect Phone to Computer" screen again.
You had the usb in before anything appeared on the screen right?
ThisWasATriumph said:
You had the usb in before anything appeared on the screen right?
Click to expand...
Click to collapse
Yeah originally. I can get to that screen now by just putting the battery in and holding power button. It seems to behave exactly like it normally would, just can't get out of it.
What screen? The screen you want has a big yellow triangle and says download.
ThisWasATriumph said:
What screen? The screen you want has a big yellow triangle and says download.
Click to expand...
Click to collapse
No it's on the phone...!...computer screen. That's what I'm saying, it's been stuck here for a while and none of the methods described on the one click thread work. I've been here before and just holding volume buttons and holding down power for it to boot twice and releasing would do it. Not so anymore. Can't get into download mode doing anything!
Well I read In the SRE thread I think that there are reports of newer phones not responding to any button combos. Bad batch they said not on purpose...
Also for the i9000 apparently you only have to hold the down volume key so since you flashed a i9000 rom try that if you haven't already.
You cant get into recovery right? Just holding volume and power then letting go of power after a bit?
Adb reboot download...
Sent from my SAMSUNG-SGH-I897 using XDA App
ThisWasATriumph said:
Well I read In the SRE thread I think that there are reports of newer phones not responding to any button combos. Bad batch they said not on purpose...
Also for the i9000 apparently you only have to hold the down volume key so since you flashed a i9000 rom try that if you haven't already.
You cant get into recovery right? Just holding volume and power then letting go of power after a bit?
Click to expand...
Click to collapse
Nope none of it works. I just got it replaced less then 3 hours ago and I already bricked it. I hope somebody finds out something that'll get this fixed. Maybe some way to force download mode through a computer application or something.
Well theres adb like mentioned above but im pretty sure that requires at least recovery mode working.
Like i said before i was stuck on the same screen so maybe theres still hope.
If all else fails someone will figure out how to JTAG these things eventually...
ThisWasATriumph said:
Jeez, I just scared the **** out of myself. I ran the remove lagfix script and it rebooted my phone but it was just a black screen. So I take the battery out. Bad Idea. It showed the ATT screen but just black after that. I could get it into recovery mode but not download. Then I messed some more and would only show a vague disconnected pic.
Finally I got it into download by doing this: (had odin open before hand)
1. took everything out including sim and usb cable.
2. quickly inserted battery and held volume buttons and very quickly inserted usb.
I'm pretty sure its the speed that matters because I tried about 4 times and only when I did it really fast did it work.
Click to expand...
Click to collapse
I know it doesn't help you out now, but when you remove the lag fix, just leave it set on the black screen. It's doing its thing. It will reboot when it's done. The home keys should still light up if you press them in this state...
Well thanks for your input anyway guys. Hopefully somebody figures something out. For now I guess I'll keep the SIM in my old iPhone 3G so I at least have a phone. Tomorrow I'll go to another ATT store in my area. Chances are the rep won't know what the hell that screen means and will replace the phone promptly.
OK, I've been reading here for 6 days all manner of Captivate unbricking. Here is my story...
I picked up a Captivate on the Rogers network. I connected it to my email server (Exchange 2010) with no problems, poked around, noticed the lag, noticed the SMS time issue, then promptly rooted, installed clockwork, and then threw cognition 2.2 beta 9.1.3. Quite frankly I was shocked at how much faster it was.
Anyways, after a day of poking around, I could not get my email to my exchange server running (tried the email.pak floating about), so I actually decided I was going to go back to the backup I made of my phone using clockwork before I installed cognition. When I restored my backup, I thought I had bricked my phone.
I let it rest for a day, then came back here, and found one of the 3-4 different variations of the 4 button download mode combo that permitted me to do the 1 click restore. This restored me to the AT&T version of 2.1. It worked, but was less than desirable.
I decided that at that point I really wanted to go back to stock, so I downloaded the stock backup on the Rogers Captivate wiki page, and did the restore using clockwork. The phone has not been the same since.
When i turn it on, I get an at&t splash screen, then in about 20 seconds I get the at&t "jingle", but the splash screen stays on. I can't seem to find any key combination that will permit me to get back into download mode so I can restore using the One Click that worked for me the first time. I have tried:
1. 3 button salute with USB in first, battery out initially.
2. 3 button salute with USB plugged in *as* I was inserting the battery.
3. Power and volume down (both with and without USB, and with battery being plugged in after USB and "during" insertion of battery)
4.Power and volume up with same combo's as #3.
5. Just volume up and volume down with same combo's as #3.
In all cases Odin was running before USB connected, running as administrator. I'm running 64bit windows, but I'm sure I have the correct drivers because I did this the first time with Odin and download mode and I haven't added or changed anything. But just for arguements sake I did uninstall, and then install the drivers again.
Any combination of power and volume buttons just gives me a battery charging logo. Occasionally when holding up until the second black screen I will get a quick indication that the computer might see something, but it dissappears withing a handful of seconds showing it promptly removed.
I'm downloading the Android SDK in the hopes that when I get the normal at&t splash screen after the "jingle" that something might actually be running in the background and maybe I can adb reboot download it but I'm not holding my breath.
Anyone seen this that has managed to get out of it? I'm starting to think the "unbrickable captivate" can be bricked. Assuming it is bricked, short of taking it back, is there anyone on the internet that can jtag these and in some fashion bring back to life?
Cheers,
Tim
This doesn't belong in Development.
MikeyMike01 said:
This doesn't belong in Development.
Click to expand...
Click to collapse
ditto
and download mode is easy.
1. start odin3 and have data cable plugged into the computer
2. insert proper files if needed
3. hold volume up and volume down for 2 sec (no power button needed) then insert usb cable, continue to hold volumes till either the download mode screen pops up or odin3 sees the phone(if you bork the phone bad enough you can corrupt the download mode image, i did it with the not to successfull manhatten project kernel) but despite the screen being black it very well may be in download mode.
4. start flash
5. if it doesn't work send it to me ill find a use for it
alternatively if the phone can go passed the splash screens and boots fully you can adb reboot download. just get the development kit and drivers on your pc.
Dani897 said:
ditto
and download mode is easy.
1. start odin3 and have data cable plugged into the computer
2. insert proper files if needed
3. hold volume up and volume down for 2 sec (no power button needed) then insert usb cable, continue to hold volumes till either the download mode screen pops up or odin3 sees the phone(if you bork the phone bad enough you can corrupt the download mode image, i did it with the not to successfull manhatten project kernel) but despite the screen being black it very well may be in download mode.
4. start flash
5. if it doesn't work send it to me ill find a use for it
alternatively if the phone can go passed the splash screens and boots fully you can adb reboot download. just get the development kit and drivers on your pc.
Click to expand...
Click to collapse
Thanks, but that doesn't work. All I get is the battery charging screen. Using the process it does not go into download mode.
MikeyMike01 said:
This doesn't belong in Development.
Click to expand...
Click to collapse
Could a moderator move this to Captivate General then? Sorry about that...
timmy22 said:
Thanks, but that doesn't work. All I get is the battery charging screen. Using the process it does not go into download mode.
Click to expand...
Click to collapse
just to be clear, you are holding volume up as well as volume down starting with the phone being powered down and continue to hold them after you plug in usb untill something shows on the screen?
if your phone is not seeing the volumes buttons you are one of the very unlucky few that had a problem at the most inopportune moment.
there is also a way where you hold all three buttons till the phone reboots twice, or something. let me try it and ill give more specifics.
timmy22 said:
Thanks, but that doesn't work. All I get is the battery charging screen. Using the process it does not go into download mode.
Click to expand...
Click to collapse
Pull the battery, open odin, plug usb into computer, hold vol up and down, plug usb into phone still holding vol buttons, drop in battery still holding vol buttons, when dl screen pops up and yellow com port lights up in odin release volume buttons. Do not touch power button at any time
Swyped...and sorry I don't proofread
Have you tried rebooting into recovery mode instead of download mode? Stock recovery is adb-ready and you should be able to adb reboot download. Its a long shot if you're having problems using button combo to get to d/l mode, but it's probably still worth a shot at this point.
If you were able to use 3 button combos before all this happened, and did NOT have to install the 3 button combo fix, its strange you don't have access to it now... Could restoring a Rogers Cappy to AT&T stock be the problem?
Dani897 said:
just to be clear, you are holding volume up as well as volume down starting with the phone being powered down and continue to hold them untill something shows on the screen?
if your phone is not seeing the volumes buttons you are one of the very unlucky few that had a problem at the most inopportune moment.
there is also a way where you hold all three buttons till the phone reboots twice, or something. let me try it and ill give more specifics.
Click to expand...
Click to collapse
Yes, that's exactly correct. I do this:
1. everything pulled (battery, USB, sim, sd)
2. Open Oden (1 click)
3. Install battery
4. hold down (and keep holding) volume up and volume down
5. insert USB cable
6. depress (i.e. don't hold) power button
Goes straight to battery charging indicator.
If I swap #6 with holding the power button down, it continually reboots while just barely showing the battery charging indicator. I've tried letting go between black screens on the 1st, 2nd, 3rd, 4th, and 5th black screen. Still no android dude with the shovel.
Try all the steps you stated but not the last one where you press the power button. Don't press the power button.
newter55 said:
Pull the battery, open odin, plug usb into computer, hold vol up and down, plug usb into phone still holding vol buttons, drop in battery still holding vol buttons, when dl screen pops up and yellow com port lights up in odin release volume buttons. Do not touch power button at any time
Swyped...and sorry I don't proofread
Click to expand...
Click to collapse
Goes straight to battery charging.
johnny13oi said:
Try all the steps you stated but not the last one where you press the power button. Don't press the power button.
Click to expand...
Click to collapse
Goes straight to battery charging.
Pull out battery for 10 seconds, hold volume up + down, connect usb into other usb port.
Sent from my GT-I9000 using XDA App
Seriously, try adb. It works wonders.
Sent from my SAMSUNG-SGH-I897 using XDA App
10tonhammr said:
Have you tried rebooting into recovery mode instead of download mode? Stock recovery is adb-ready and you should be able to adb reboot download. Its a long shot if you're having problems using button combo to get to d/l mode, but it's probably still worth a shot at this point.
If you were able to use 3 button combos before all this happened, and did NOT have to install the 3 button combo fix, its strange you don't have access to it now... Could restoring a Rogers Cappy to AT&T stock be the problem?
Click to expand...
Click to collapse
Trying to get into recovery mode gets me the at&t logo and the "jingle", but no recovery mode menu to reboot, etc.
This is what I'm worried about, restoring the Rogers stock over top of the Odin 1 click restore (which is an AT&T image) has bricked it and prevents download mode from invoking.
fatttire said:
Seriously, try adb. It works wonders.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I know, I played with adb before I bricked it. ADB needs to "see" the phone, it no longer sees it (I have three computers, all three can't see it, but they can see my friends cappy with no problems first time, every time). Same process for his phone works every time to get into download mode, but not on mine.
And yes, have tried other USB ports on the same computer, both on the mainboard, and on the front ports.
Keep the ideas coming though please, I will try every one.
timmy22 said:
I know, I played with adb before I bricked it. ADB needs to "see" the phone, it no longer sees it (I have three computers, all three can't see it, but they can see my friends cappy with no problems first time, every time). Same process for his phone works every time to get into download mode, but not on mine.
And yes, have tried other USB ports on the same computer, both on the mainboard, and on the front ports.
Keep the ideas coming though please, I will try every one.
Click to expand...
Click to collapse
There's a trick to prompt download mode through a "jig" which you can hack together for about $2 in parts and a sacrificial microUSB cable...it works on the other SGSes, but I think it should work on the Captivate as well. Never tried it personally...
Merlin_reloaded said:
There's a trick to prompt download mode through a "jig" which you can hack together for about $2 in parts and a sacrificial microUSB cable...it works on the other SGSes, but I think it should work on the Captivate as well. Never tried it personally...
Click to expand...
Click to collapse
I work in a tech shop so have access to electronics, sacrificial cables, soldering irons, resistors, caps, etc.... could you point me in the right direction?
Oh, nevermind, found it in the i9000 forum. Will test first thing in the morning!
Cheers,
I bricked one today as well. Exactly what you are talking about here. The only thing is that i was still under the 30days so i swapped it out for a new one. As of right now ive been debating whether i want to do the voodoo fix (which i think is what bricked it to begin with)
When I tried to disable the voodoo lagfix my phone froze, after about 20 minutes i decided to pull the battery and now the phone freezes when trying to boot and even after plugging in the charger, it freezes on the battery load symbol. Unfortunately, the 3 button way to get to the recovery menu doesn't work. help me please??
I'm having the same problem - phone just hung on the kernel load screen (firebird 2) after trying to shut off lagfix - although I can get to a red recovery mode menu. Not that it's helping at this time. It would be nice if I could recover without a clean wipe of the phone.
Anyone have any ideas. I'll be scouring the threads...
You could try making a jig and flashing to stock http://forum.xda-developers.com/showthread.php?t=841512
how are you getting to the red recovery menu?
i have the same kernel and i'm running the firefly 1.5 rom
I can't boot into anything and the only solution i have so far is to make a jig or buy one and not have a phone for a little bit, which is going to suck..
I've tried the following combinations, just because I know people are going to ask.
1. take out battery, sim, etc.
2. leave out for about 15 seconds
3. plug in the battery, plug in usb and hold two volume buttons-> freezes while trying to load battery status
3.b same precedure as above except plug in usb first hold volume buttons then battery-> still frozen
3.c hold volume buttons, battery, then power button, let it cycle atleast 2 times and let go of power at att logo while holding the volume-> frozen at kernel loader
3.d same as above but with only one volume button at a time, both up and down-> no cigar
3.e all the precedures above while wildly pressing all the soft keys (home, search, yadda yadda) out of frustration -> thinking, gosh i'm screwed
did i miss out any secret other combinations or methods known to work?
I'd really like to do this without hardware, but making a jig kinda sounds like a fun project and i do have a soldering iron in storage somewhere...
xsamxoxo said:
how are you getting to the red recovery menu?
i have the same kernel and i'm running the firefly 1.5 rom
I can't boot into anything and the only solution i have so far is to make a jig or buy one and not have a phone for a little bit, which is going to suck..
I've tried the following combinations, just because I know people are going to ask.
1. take out battery, sim, etc.
2. leave out for about 15 seconds
3. plug in the battery, plug in usb and hold two volume buttons-> freezes while trying to load battery status
3.b same precedure as above except plug in usb first hold volume buttons then battery-> still frozen
3.c hold volume buttons, battery, then power button, let it cycle atleast 2 times and let go of power at att logo while holding the volume-> frozen at kernel loader
3.d same as above but with only one volume button at a time, both up and down-> no cigar
3.e all the precedures above while wildly pressing all the soft keys (home, search, yadda yadda) out of frustration -> thinking, gosh i'm screwed
did i miss out any secret other combinations or methods known to work?
Click to expand...
Click to collapse
I'm afraid not. This happened to someone I know and they told samsung the OTA update bricked it and AFAIK they fixed it for free. They never tried using a jig though, so if you don't want to wait to replace it or anything you could try a jig since it might work and the parts are pretty easy to get (and if you'd be replacing the phone, a jig is ALWAYS good to have anyway)
Just another note to throw in there, the computer recognizes the phone, but strangely my computer freezes while trying to read the media storage drives. I can't tell if the internal sd is mounted because of the ever-lasting wait but i'm almost positive its not.
Do adb commands work?
Sent from my SGH-I897 using XDA App
Thnikk said:
Do adb commands work?
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
nope, it says "error device is offline"
You could try ... when the phone is booting and trying to catch it before it freezes is spam the heck out of the command adb reboot download then after hitting the enter button hit the up arrow and keep repeating until either the phone a) hopefully goes into download mode or b) freezes and throws the error.
Who knows.. might get lucky.
avgjoegeek said:
You could try ... when the phone is booting and trying to catch it before it freezes is spam the heck out of the command adb reboot download then after hitting the enter button hit the up arrow and keep repeating until either the phone a) hopefully goes into download mode or b) freezes and throws the error.
Who knows.. might get lucky.
Click to expand...
Click to collapse
it connects even though the phone is frozen. I'm heading over to "The Shack" pretty soon and just making a jig.
Thanks for all your help everyone.
Edit: Just confirming that with much dedication and a steady hand I finally have my captivate up and running with the help of the resistors. I also flashed the 3 button fix stock rom.
Well, I kept trying the least invasive methods first. Tried to reflash Firebird. Then went adb and such. In the end, it was pretty clear that it had hung at the lagfix correction, and I was dealing with a file system error. I was eventually able to get into download mode. The hardest discovery was finding that I had gotten the wrong drivers from samsung. The ones in the [stock rom] odin master clear page were what I should have been using. When I loaded those, the computer recognized that I had a phone and not a "serial gadget" and then I knew I was close. Odin finally saw the phone, and a couple tries at "light" re-stocking failed at file analysis, so I did the repartition (aha, file system error), and it shot through the whole process and I had my phone back and flashed to Serendipity in about 20 minutes.
But I would like to know about the red menu. That was unexpected (blue for standard, green for cwm).
No need for a jig. I had access to some phone functions, most importantly, download mode.
I'm stuck in a pretty crappy situation. The phone is on some weird bootloop. When it boots, the AT&T screen comes up, then some weird multi-colored screen comes on, the phone turns off, and this process repeats.
I know how to put it into download mode, but the phone turns on as soon as I put the battery in. I'm not sure how to have it powered off with the battery in long enough so I can hold the volume buttons down and plug the USB in. If I could at least get into download mode and flash something via Odin, I could possibly fix it.
Any suggestions?
did you try, remove battery, plug in usb, hold power and both volume buttons then insert battery? or even just hold vol down and power then insert battery?
adobrakic said:
I'm stuck in a pretty crappy situation. The phone is on some weird bootloop. When it boots, the AT&T screen comes up, then some weird multi-colored screen comes on, the phone turns off, and this process repeats.
I know how to put it into download mode, but the phone turns on as soon as I put the battery in. I'm not sure how to have it powered off with the battery in long enough so I can hold the volume buttons down and plug the USB in. If I could at least get into download mode and flash something via Odin, I could possibly fix it.
Any suggestions?
Click to expand...
Click to collapse
fractaline said:
did you try, remove battery, plug in usb, hold power and both volume buttons then insert battery? or even just hold vol down and power then insert battery?
Click to expand...
Click to collapse
(psst, he said his power button is broken)
You dont need to use the power buttons to enter download mode. Just hold both volume buttons and plug in usb. Though tbh I haven't had to do it in so long my memory is a bit foggy on whether it was both volume buttons + usb or just volume up + usb. Either way one of those should work. Im pretty sure you should be able to do it without the battery inserted.
When all else fails, jig it. Jig it hard.
Herp derp Captivate Tapatalk 2
fractaline said:
did you try, remove battery, plug in usb, hold power and both volume buttons then insert battery? or even just hold vol down and power then insert battery?
Click to expand...
Click to collapse
Well, the power button doesn't work, so I haven't tried the latter. It's not rooted, so trying to get into CWM wouldn't really do much. When I try to plug in the USB, hold the volume buttons, and plug in the battery last, the phone just goes to the battery charging screen. If I take the USB out.. it stays there.
I'm not sure why the phone turns on by itself as soon as I put the battery in. My sister has the same model, and she has to hold the power button to turn it on. :/
I just turned it on, and it's stuck on the AT&t screen instead of bootlooping. This is the first time it has done this after the bootloop began. Odin recognizes it. Is this ninja download mode? If so, could you please point me in the right direction of getting out of this mess? :x This is my sister's fiance's phone, I own a SGS4G. Really don't wanna risk this phone any more than I already have, lol.
Thanks, guys.
--Edit--
To be more specific, I attempted using this to root the phone, which resulted in this situation. Not sure if that's even helpful, but it can't hurt.
I feel for ya, I hate having hardware issues when a software issues happens..
follow fractaline's instructions: Odin ON, battery out, Good USB cable with good USB port Insert, (this is where it gets tricky), hold down volume up and volume down, whilst 2 seconds later putting the battery back in.
if you see the screen with something that looks like this, http://movilzone.org/files/2011/09/Captivate-Download-Mode1.jpeg
or this,
http://1.bp.blogspot.com/-BwmbWV5u6h8/TvNq1jXT7oI/AAAAAAAAMpU/_Mh4V9LMYd8/s1600/Semi-bricked.jpg, Then you can flash a kernel.
Were you on gingerbread 2.3.5? if so I would recommend this http://forum.xda-developers.com/showthread.php?t=1294477&highlight=corn
if you flash corn there is an option in CWM to install root I believe.
I used to flash the corn kernel all day to fix my 2.3.5 problems.
it really depends which version you previously were running. which is hard to tell since it wasn't your phone... more info needed, i'll be back in the morning. hope this helps.
Oh and on the hardware side of things, you could take the back plate off, the plate under the battery, and clean all the crap out. i find with mine i often get dust particles that interfere with my power button. there is a guide to properly tear down a captivate on xda somewhere... I've posted on it before as well.
or, take your fingernails and try and peel back the plastic on the edge of the glass up by the power button, if you can pull it back enough to blow air in there sometimes you can dislodge/clean out whatever is obstructing the power button.
Edit: if you do get it rooted, bring it up to ICS, it's fantastic up here
adobrakic said:
Well, the power button doesn't work, so I haven't tried the latter. It's not rooted, so trying to get into CWM wouldn't really do much. When I try to plug in the USB, hold the volume buttons, and plug in the battery last, the phone just goes to the battery charging screen. If I take the USB out.. it stays there.
I'm not sure why the phone turns on by itself as soon as I put the battery in. My sister has the same model, and she has to hold the power button to turn it on. :/
I just turned it on, and it's stuck on the AT&t screen instead of bootlooping. This is the first time it has done this after the bootloop began. Odin recognizes it. Is this ninja download mode? If so, could you please point me in the right direction of getting out of this mess? :x This is my sister's fiance's phone, I own a SGS4G. Really don't wanna risk this phone any more than I already have, lol.
Thanks, guys.
--Edit--
To be more specific, I attempted using this to root the phone, which resulted in this situation. Not sure if that's even helpful, but it can't hurt.
Click to expand...
Click to collapse
I think you were not on Gingerbread and you attempted to flash a gingerbread kernel. That is why it is bootlooping. You can flash back to stock (Gingerbread or froyo) and that should solve your issue. I'm trying to download and get the stock froyo kernel for you so you can flash that again. Just an FYI, applying root through CWM would require the use of the power button.
Try flashing this in the PDA in Odin. It is the stock froyo kernel.
https://www.dropbox.com/s/vx5r7hr3iokj764/zImage.tar
@Bacon, it was version 2.2. I can't get to download mode because the phone turns on as soon as I put the battery in. I'm not sure why it does this. Also, I don't get the bricked screen because it just bootloops. The AT&T screen comes on, then this comes on, the phone turns off, and this repeats. I'm assuming that the multi-colored screen would be the SGS screen, or something similar.
Oh and on the hardware side of things, you could take the back plate off, the plate under the battery, and clean all the crap out. i find with mine i often get dust particles that interfere with my power button. there is a guide to properly tear down a captivate on xda somewhere... I've posted on it before as well.
or, take your fingernails and try and peel back the plastic on the edge of the glass up by the power button, if you can pull it back enough to blow air in there sometimes you can dislodge/clean out whatever is obstructing the power button.
Click to expand...
Click to collapse
If it comes to that, I'll definitely keep this in mind.
@Red Wow, I'm stupid. -_- I don't know how I missed the "Requirements" on that page. Thanks, I'll try your .tar now.
--Edit--
Ah, unfortunately that AT&T screen wasn't download mode. I guess I'm just gonna have to keep trying until I finally get it into download mode. I just don't get why it's this difficult.
adobrakic said:
@Red Wow, I'm stupid. -_- I don't know how I missed the "Requirements" on that page. Thanks, I'll try your .tar now.
--Edit--
Ah, unfortunately that AT&T screen wasn't download mode. I guess I'm just gonna have to keep trying until I finally get it into download mode. I just don't get why it's this difficult.
Click to expand...
Click to collapse
You're not stupid. I added that after reading your post to prevent others from getting into the same situation.
As for download mode, if you don't have a jig, try this:
Take battery out
Plug phone into computer
Hold down Volume Buttons
Put battery in
adobrakic said:
@Red Wow, I'm stupid. -_- I don't know how I missed the "Requirements" on that page. Thanks, I'll try your .tar now.
--Edit--
Ah, unfortunately that AT&T screen wasn't download mode. I guess I'm just gonna have to keep trying until I finally get it into download mode. I just don't get why it's this difficult.
Click to expand...
Click to collapse
I can't tell you how many times i flashed the wrong kernel because i didn't read that it was for my version! lol!
that screen is unsettling...
well it's tough to say what to do next... just keep trying for a download mode. I've never used a Jig, perhaps that would be a good investment. Maybe use a one click.. I don't know..
I don't suppose this could be a bootloader issue could it?
EDIT: You're sure you have a reliable USB port/Plug? it's very important that both are good.
Red_81 said:
You're not stupid. I added that after reading your post to prevent others from getting into the same situation.
As for download mode, if you don't have a jig, try this:
Take battery out
Plug phone into computer
Hold down Volume Buttons
Put battery in
Click to expand...
Click to collapse
When I do that, I get to this screen. I'm assuming that's the battery charging screen, but the picture of the battery never comes up, just that refreshing icon.
If I keep holding the volume buttons, the phone seems to turn off in this state. I tried immediately unplugging the USB cable and letting go of the volume buttons once it does this. It stays off (if it's actually off). However, when I hold the volume buttons down and plug the USB back in, it just goes back to that screen. No download mode.
@Bacon
I don't suppose this could be a bootloader issue could it?
EDIT: You're sure you have a reliable USB port/Plug? it's very important that both are good.
Click to expand...
Click to collapse
To be honest, I have no idea if it could be a bootloader issue. I'm knowledgeable of Android as far as a user goes, I know nothing about the OS past rooting it, and tweaking it to OC/UC, etc. Also, I believe that the USB port/plug is reliable. It's the same combo I used prior to bricking it (lol). However, I have about 8 different ports and a few different cables as well, I'll give those a go.
Thanks for the help guys, I really do appreciate it.
adobrakic said:
@Bacon
To be honest, I have no idea if it could be a bootloader issue. I'm knowledgeable of Android as far as a user goes, I know nothing about the OS past rooting it, and tweaking it to OC/UC, etc. Also, I believe that the USB port/plug is reliable. It's the same combo I used prior to bricking it (lol). However, I have about 8 different ports and a few different cables as well, I'll give those a go.
Thanks for the help guys, I really do appreciate it.
Click to expand...
Click to collapse
Man I wish I could help more, i tend to be a hardware guy so i'm not much help other than telling you how to fix you power button... just keep flashing the crap out of it i guess. see if anything sticks...
Open a dos window and go to KK4_Root\Tools (probably on your C:\ drive)
Type:
Code:
adb wait-for-device reboot download
and hit enter.
Now try booting the phone with it plugged in again. If the computer recognizes it during the bootloop, it will issue it the command to boot into download mode.
Otherwise, I would suggest getting a download Jig. It will put you into download mode every time.
@Bacon
All good buddy, thanks so much for your help.
@Red
Holy ****, that worked perfectly. I'm in download mode right now, and am in the process of using a one click to get back to stock.
I'll post back with results.
--Edit--
This is the one click I was using. It won't flash bootloaders at first to prevent bricking, so I'm now in Android system recovery. I'm wanting to get into download mode again, but I guess since it's not in bootloop, the command Red gave me doesn't get me there. I need to get back into download so the bootloaders can be flashed. Any suggestions as to how I could get there again?
the most success I've had is using kies mini up to 2.3.5 and then using corn from there on.
Sent from my SGH-I897 using xda app-developers app
Does it always boot to recovery? You could just pull the battery and then try to let it boot normally.
Sent from my SAMSUNG-SGH-I897 using xda premium
@Bacon
Don't I need the phone to boot up for kies, though?
@Red
Yes. As soon as I put the battery in, the AT&T screen comes on, and then the Android System Recovery <3e> screen comes on.
When I try to plug in the USB, hold the volume buttons down, and plug in the battery last, it simply goes to the battery charging screen. I don't know why it doesn't go to download mode. I've tested the volume buttons in the Android System Recovery screen, both work just fine.
If you could get that power button to work you could try wiping data. That might get it out of that funk.
Try this:
Open a dos window and go to KK4_Root\Tools (probably on your C:\ drive)
Code:
adb reboot recovery --wipe_data
Crap, my computer doesn't seem to recognize the device when it's in the Android System Recovery screen. Should I try prying open the power button and seeing if I can get it to work? Don't see any other way out of this. I wish the soft-key buttons could be used for 'enter' instead of just the power button. :|
adobrakic said:
@Bacon
Don't I need the phone to boot up for kies, though?
Click to expand...
Click to collapse
Shoot, sorry i misread i thought you said you had gotten it partially fixed... my b.
I was just commenting how I'd had the most success using a one click to stock and moving up with kies. I'm afraid you may have to wipe data, which would suck.
Try the power button first. It's really easy taking the hardware apart. Just don't strip the tiny screws.... i only have three of the 6 holding my back plate in. You really don't need them all
Sent from my SGH-I897 using xda app-developers app
Honestly man, at this point, I wouldn't care if I had to repurchase all of the apps that I had if it was necessary to get the phone working. I'll YouTube some instructions for disassembly. Hopefully it'll get me out of this jam.
So I've posted this problem here before:
http://forum.xda-developers.com/htc-one/help/please-confirm-totally-bricked-t2831685
Just wondering if any of you would know how to fix it.
Probably no one will want to read that much, so here's the short version:
-Can't enter bootloader
-Can't enter recovery
-ABD doesn't work
-Fastboot doesn't work
Reasons why I think it still can get fixed:
-It stills turns on.
-Battery has ran out a couple of times, so it still charges.
-Windows 8 makes a pulg-in sound when I connect the phone to the laptop.
The phone also keeps rebooting each 6 to 10 seconds, so it is actually a plug-in, and plug-out, and a plug-in, and so on...
It doesn't list anything inside Device Manager.
Some people have tried Dexter's fix for bricked devices, but I think it only works for devices listed at least as QHSUSB_DLOAD.
Mine is not recognized that way... or at all.
That plug-in sound though.
HTC Drivers Installed:
setup_3.1.24.5_htc.exe
HTC_BMP_USB_Driver_x64_1.0.5375.msi
HTC Driver 4.10.0.001.exe
HTC Sync Manager
KomuroXV said:
So I've posted this problem here before:
http://forum.xda-developers.com/htc-one/help/please-confirm-totally-bricked-t2831685
Just wondering if any of you would know how to fix it.
Probably no one will want to read that much, so here's the short version:
-Can't enter bootloader
-Can't enter recovery
-ABD doesn't work
-Fastboot doesn't work
Reasons why I think it still can get fixed:
-It stills turns on.
-Battery has ran out a couple of times, so it still charges.
-Windows 8 makes a pulg-in sound when I connect the phone to the laptop.
The phone also keeps rebooting each 6 to 10 seconds, so it is actually a plug-in, and plug-out, and a plug-in, and so on...
It doesn't list anything inside Device Manager.
Some people have tried Dexter's fix for bricked devices, but I think it only works for devices listed at least as QHSUSB_DLOAD.
Mine is not recognized that way... or at all.
That plug-in sound though.
HTC Drivers Installed:
setup_3.1.24.5_htc.exe
HTC_BMP_USB_Driver_x64_1.0.5375.msi
HTC Driver 4.10.0.001.exe
HTC Sync Manager
Click to expand...
Click to collapse
So wait. Why can't you enter? Because it reboots too fast? Can you shut off your phone? If yes do it so and then try to reboot to bootloader. And if it reboots there too every 5 to 6 seconds, you're gonna have a big problem. Within 5-6 seconds you can't hide the rooted state of your device and this also means that you can't return it.
But if you can get to your bootloader and if you can fastboot connect it, I'd recommend using a RUU if you are S-OFF. Otherwise I'd try to reinstall another recovery and from the recovery I'd reinstall a new OS.
Anyways, just try to get to the bootloader and do what I told you to. If my instructions were too unaccurate, just mention or quote me, I'll get back to you.
LibertyMarine said:
So wait. Why can't you enter? Because it reboots too fast? Can you shut off your phone? If yes do it so and then try to reboot to bootloader. And if it reboots there too every 5 to 6 seconds, you're gonna have a big problem. Within 5-6 seconds you can't hide the rooted state of your device and this also means that you can't return it.
But if you can get to your bootloader and if you can fastboot connect it, I'd recommend using a RUU if you are S-OFF. Otherwise I'd try to reinstall another recovery and from the recovery I'd reinstall a new OS.
Anyways, just try to get to the bootloader and do what I told you to. If my instructions were too unaccurate, just mention or quote me, I'll get back to you.
Click to expand...
Click to collapse
First of all, thank you for replying.
On topic.
Phone is actually turned off right now.
Battery died again.
Only way to turn it back on is connecting it to the wall charger and sometimes to the laptop.
But as soon as I do...
1. Phone turns on.
2. Shows the white screen with only the green HTC logo.
3. If it's plugged to the laptop then I hear that "plug in" sound Windows does.
4. After a few seconds phone reboots... and reboots... and reboots... doing the same I just stated.
I also get to hear the Windows "plug-out" sound everytime it turns off to reboot.
Not sure of why I can't enter the boot loader.
This problem started after I decided to turn off my phone while it was installing a custom recovery (Process was being slow and I am OCD like that)
My paranoic guesses are that I screwed it so bad I wiped the bootloader also, but is that even possible?
KomuroXV said:
First of all, thank you for replying.
On topic.
Phone is actually turned off right now.
Battery died again.
Only way to turn it back on is connecting it to the wall charger and sometimes to the laptop.
But as soon as I do...
1. Phone turns on.
2. Shows the white screen with only the green HTC logo.
3. If it's plugged to the laptop then I hear that "plug in" sound Windows does.
4. After a few seconds phone reboots... and reboots... and reboots... doing the same I just stated.
I also get to hear the Windows "plug-out" sound everytime it turns off to reboot.
Not sure of why I can't enter the boot loader.
This problem started after I decided to turn off my phone while it was installing a custom recovery (Process was being slow and I am OCD like that)
My paranoic guesses are that I screwed it so bad I wiped the bootloader also, but is that even possible?
Click to expand...
Click to collapse
I wonder if this is a damaged partition - and it's tricky to solve
@nkk71 what do you think?
stovie_steve said:
I wonder if this is a damaged partition - and it's tricky to solve
@nkk71 what do you think?
Click to expand...
Click to collapse
I made a video, hope it helps.
https://www.youtube.com/watch?v=GMuo-kvIGIc
Suggestions: Mute it :silly:
KomuroXV said:
I made a video, hope it helps.
https://www.youtube.com/watch?v=GMuo-kvIGIc
Suggestions: Mute it :silly:
Click to expand...
Click to collapse
only thing i noticed in the video is your holding volume up not volume down. Volume up plus power will not load the bootloader
clsA said:
only thing i noticed in the video is your holding volume up not volume down. Volume up plus power will not load the bootloader
Click to expand...
Click to collapse
I've tried both.
Here's another one anyways.
https://www.youtube.com/watch?v=1zyA6XGFEpo&list=UUzlEfhRw_dyaJ7aAFpWC7-A
KomuroXV said:
First of all, thank you for replying.
On topic.
Phone is actually turned off right now.
Battery died again.
Only way to turn it back on is connecting it to the wall charger and sometimes to the laptop.
But as soon as I do...
1. Phone turns on.
2. Shows the white screen with only the green HTC logo.
3. If it's plugged to the laptop then I hear that "plug in" sound Windows does.
4. After a few seconds phone reboots... and reboots... and reboots... doing the same I just stated.
I also get to hear the Windows "plug-out" sound everytime it turns off to reboot.
Not sure of why I can't enter the boot loader.
This problem started after I decided to turn off my phone while it was installing a custom recovery (Process was being slow and I am OCD like that)
My paranoic guesses are that I screwed it so bad I wiped the bootloader also, but is that even possible?
Click to expand...
Click to collapse
Hmmm, as the others said this might be really hard to solve.
Most likely this here won't solve your problem but it's better to try it than to just let it be:
Hold your HTC One below a bright lights source and hold the power button for about 15 seconds or even longer. The charging light will light up. Then hold down the volume down button and try different key combinations!
I heard about that this here could get some devices to fully boot after they had been in such a strange loop as your phone is:
A: Hold volume down and volume up button and the power button for about 90 seconds. If this doesn't work, try holding your phone below bright light again
I couldn't watch the second video (it's private) where you pressed the volume down button. But I believe you're right.
@stovie_steve what is the indication for this damaged partition? I can't imagine which partition would lead into a such behaviour.
Anyways.. @KomuroXV just try what I've writtten if it doesn't work, just mention or quote again, I'll try to look up what it could be.
Good luck!
LibertyMarine said:
Hmmm, as the others said this might be really hard to solve.
Most likely this here won't solve your problem but it's better to try it than to just let it be:
Hold your HTC One below a bright lights source and hold the power button for about 15 seconds or even longer. The charging light will light up. Then hold down the volume down button and try different key combinations!
I heard about that this here could get some devices to fully boot after they had been in such a strange loop as your phone is:
A: Hold volume down and volume up button and the power button for about 90 seconds. If this doesn't work, try holding your phone below bright light again
I couldn't watch the second video (it's private) where you pressed the volume down button. But I believe you're right.
@stovie_steve what is the indication for this damaged partition? I can't imagine which partition would lead into a such behaviour.
Anyways.. @KomuroXV just try what I've writtten if it doesn't work, just mention or quote again, I'll try to look up what it could be.
Good luck!
Click to expand...
Click to collapse
Oh... I fixed the private video thing, sorry about that.
I've tried the bright light + power + volume down button combination before but it never managed to make the phone to boot properly.
It did have some little behaviour changes though...
Like... it was more responsive for the button combination making it turn off kind of faster, just to reboot again some seconds after anyway.
Tried it again just now, but still nothing different. :/
Same stuff as before.
I could make another video if you guys wanted to make sure, but it'd be me just pressing the volume down + power under the bright light for nothing but the loop, besides the responsiveness I've told you it seems to get to pressing the buttons.
Anyway, just tell me if making another video would help.
By the way.
Some months ago (Yeah, I have a lot of time dealing with this) I was able to turn it on with or without the charger, now it seems like it's only possible when it's "charging" or connected to the laptop, regardless of bright light or not.
Guess that was because it had charge before, now it doesn't and it's unable to actually charge the battery.
Which would explain why the orange little charging light is off now.
I'm open to any new ideas. :/
Thank you guys for all your support.
KomuroXV said:
Oh... I fixed the private video thing, sorry about that.
I've tried the bright light + power + volume down button combination before but it never managed to make the phone to boot properly.
It did have some little behaviour changes though...
Like... it was more responsive for the button combination making it turn off kind of faster, just to reboot again some seconds after anyway.
Tried it again just now, but still nothing different. :/
Same stuff as before.
I could make another video if you guys wanted to make sure, but it'd be me just pressing the volume down + power under the bright light for nothing but the loop, besides the responsiveness I've told you it seems to get to pressing the buttons.
Anyway, just tell me if making another video would help.
By the way.
Some months ago (Yeah, I have a lot of time dealing with this) I was able to turn it on with or without the charger, now it seems like it's only possible when it's "charging" or connected to the laptop, regardless of bright light or not.
Guess that was because it had charge before, now it doesn't and it's unable to actually charge the battery.
Which would explain why the orange little charging light is off now.
I'm open to any new ideas. :/
Thank you guys for all your support.
Click to expand...
Click to collapse
hey guys, sorry been/am a bit busy lately, so don't get to respond/contribute much
OP, looks like your power button is messed up? (ie it's continually "pressed") you can try to nudge a little, to see if it gets unpressed
after "nudging" a little, don't even bother pressing it, when the phone reboots, just hold voldown to get to bootloader
EDIT: be gentle :silly: :laugh:
nkk71 said:
hey guys, sorry been/am a bit busy lately, so don't get to respond/contribute much
OP, looks like your power button is messed up? (ie it's continually "pressed") you can try to nudge a little, to see if it gets unpressed
after "nudging" a little, don't even bother pressing it, when the phone reboots, just hold voldown to get to bootloader
EDIT: be gentle :silly: :laugh:
Click to expand...
Click to collapse
hey @nkk71, but in what way does that explain the fact that it only boots when the phone is connected to a power source? And he also holds down the powerbutton the first time. I can't find an explanation for this.
@KomuroXV but what nkk suggested is a good idea, but just be very very gentle. I f#cked up my powerbutton pressing it too much. Luckily HTC believed my (altered) story and I got a replacement.
What you can try is to just go with a paper edge between the power button and the Magnesium surrounding then try to much it upwards and downwards, this may help "unstucking" your powerbutton if that's even the case.
I'm gonna test the with my phone how long it takes to reboot if I hold down the power button (will post again in a few min). If it's about the same as shown in your vid, it might really be a stuck power button.
LibertyMarine said:
hey @nkk71, but in what way does that explain the fact that it only boots when the phone is connected to a power source? And he also holds down the powerbutton the first time. I can't find an explanation for this.
Click to expand...
Click to collapse
1) battery drains, he plugs it in -> boom, it turns on
2) it reboots no matter what button combo he tries
3) it's not even staying on the bootsplash long enough (from the video) to consider it a bootloop
it's just a thought, but that's what it looks like to me
(if it were even going slightly further than the bootsplash, or even bootlooping back to bootloader, then it could be something else, it just looks to me as if the power button is constantly pressed)
nkk71 said:
1) battery drains, he plugs it in -> boom, it turns on
2) it reboots no matter what button combo he tries
3) it's not even staying on the bootsplash long enough (from the video) to consider it a bootloop
it's just a thought, but that's what it looks like to me
(if it were even going slightly further than the bootsplash, or even bootlooping back to bootloader, then it could be something else, it just looks to me as if the power button is constantly pressed)
Click to expand...
Click to collapse
@KomuroXV and @nkk71 I mistreated my phone and yeah, seems to have about the same time to reboot.
And yeah, I now saw in the first video he didn't first hold down the power button. So your thesis is very probable.
So yeah only way is to try and get the button unstuck and if this doesn't work I'd return it to the manufacturer. Shouldn't be something you have to pay for. Only bad thing is that if they notice the altered motherboard...
LibertyMarine said:
@KomuroXV and @nkk71 I mistreated my phone and yeah, seems to have about the same time to reboot.
And yeah, I now saw in the first video he didn't first hold down the power button. So your thesis is very probable.
So yeah only way is to try and get the button unstuck and if this doesn't work I'd return it to the manufacturer. Shouldn't be something you have to pay for. Only bad thing is that if they notice the altered motherboard...
Click to expand...
Click to collapse
For a second there I thought it could be this, but it looks like it's not.
I nudged it.
Carefully cleaned with the edge of a paper too.
God, I basically gave a blowjob to that power button just in case there was any dust inside of it.
But it looks like there's not anything.
It was a good theory though.
But still it wouldn't explain, why did it happen just after I interrupted the custom recovery flashing?
Let explain again in case I didn't do it clearly last time.
I flashed a Custom Recovery through fastboot.
I was Unlocked, S-Off, Rooted, everything good.
All went smoothly at CMD screen.
But the process in the phone was being slow and it looked like if it was stuck to me.
Which it wasn't I guess... but I panicked and turned off the phone like at 40% of the install.
Then all this happened.
That broken power button thing would be way too much coincidence.
My theory is that since I was flashing Custom Recovery through fastboot (bootloader) and I interrupted it.
Now, every time it turns on, it tries to log into fastboot and continue the process I stopped.
Just that now.... it doesn't has the files needed to complete it, or maybe just got corrupted.
Since it can't finish that ghost recovery flashing process, it gives error and reboots.... and reboots... and reboots...
Doesn't really look like a hardware problem.
Seriously, it's the most well taken care phone I've ever had.
I bought it a tempered glass screen protector, an UAG case which for me made the phone indestructible.
Still, guess it wasn't silly-owner-proof.
*facepalms*
:silly:
KomuroXV said:
For a second there I thought it could be this, but it looks like it's not.
I nudged it.
Carefully cleaned with the edge of a paper too.
God, I basically gave a blowjob to that power button just in case there was any dust inside of it.
But it looks like there's not anything.
It was a good theory though.
But still it wouldn't explain, why did it happen just after I interrupted the custom recovery flashing?
Let explain again in case I didn't do it clearly last time.
I flashed a Custom Recovery through fastboot.
I was Unlocked, S-Off, Rooted, everything good.
All went smoothly at CMD screen.
But the process in the phone was being slow and it looked like if it was stuck to me.
Which it wasn't I guess... but I panicked and turned off the phone like at 40% of the install.
Then all this happened.
That broken power button thing would be way too much coincidence.
My theory is that since I was flashing Custom Recovery through fastboot (bootloader) and I interrupted it.
Now, every time it turns on, it tries to log into fastboot and continue the process I stopped.
Just that now.... it doesn't has the files needed to complete it, or maybe just got corrupted.
Since it can't finish that ghost recovery flashing process, it gives error and reboots.... and reboots... and reboots...
Doesn't really look like a hardware problem.
Seriously, it's the most well taken care phone I've ever had.
I bought it a tempered glass screen protector, an UAG case which for me made the phone indestructible.
Still, guess it wasn't silly-owner-proof.
*facepalms*
:silly:
Click to expand...
Click to collapse
I'm gonna sleep now, will answer tomorrow evening. I have an important meeting tomorrow.
KomuroXV said:
I flashed a Custom Recovery through fastboot.
I was Unlocked, S-Off, Rooted, everything good.
All went smoothly at CMD screen.
But the process in the phone was being slow and it looked like if it was stuck to me.
Which it wasn't I guess... but I panicked and turned off the phone like at 40% of the install.
Then all this happened.
That broken power button thing would be way too much coincidence.
Click to expand...
Click to collapse
i dont see how flashing / interrupting flashing a recovery could cause that, the recovery is in a different partition than bootloader, so even if you were unable to enter recovery (due to bad flash), you should be able to get to bootloader
but when you say it got stock at 40%, i'm seriously surprised, as flashing a recovery literally takes 2 seconds:
Code:
C:\ADB3>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
maybe try covering the light sensors completely, and hold voldown, when it reboots again.... maybe (though i doubt it), it will forego the simulated battery pull
KomuroXV said:
[...]
I flashed a Custom Recovery through fastboot.
I was Unlocked, S-Off, Rooted, everything good.
All went smoothly at CMD screen.
But the process in the phone was being slow and it looked like if it was stuck to me.
Which it wasn't I guess... but I panicked and turned off the phone like at 40% of the install.
Then all this happened.
That broken power button thing would be way too much coincidence.
My theory is that since I was flashing Custom Recovery through fastboot (bootloader) and I interrupted it.
Now, every time it turns on, it tries to log into fastboot and continue the process I stopped.
Just that now.... it doesn't has the files needed to complete it, or maybe just got corrupted.
Since it can't finish that ghost recovery flashing process, it gives error and reboots.... and reboots... and reboots...
[...]
Click to expand...
Click to collapse
How did you turn it off? Did you press the power button very hard/strong?
Did you flash the recovery with fastboot
or did you flash your recovery within rebootRUU and with an firmware.zip ?
Because the method via fastboot (fastboot flash recovery recovery.img) doesn't indicate a percentage. And btw. I had issues with this method too and interrupted the installation several times, didn't cause any problems. To the theory that your phone wants to continue flashing recovery is not true. This isn't possible since your phone should boot correctly and if it wanted to boot into recovery you could prevent that with pressing the vol. down button. That didn't work in your case so I think that this theory doesn't work out.
If you flashed it with a firmware zip, was there another hboot.img that you installed too without knowing/wanting? Because interrupting a hboot flash will brick your device. but if that happend you wouldn't be able to boot your phone. So I think this isn't true either.
i have exactly the same problem, is very strange beacause i was updating my ROM