Database Info

[Q] G2x stuck at LG logo/cannot access recovery

Hey all
Before anyone mentions that i should be searching around more, i would like to say that i've been on multiple threads and they all state the same thing (use NVflash to flash CWM and then boot into CWM but the solution did not work for me past flashing CWM and then trying to access recovery after) and i wasn't able to find one that had a similar problem as mine.
I have CWM flashed through NVflash and was running CM7.1 RC1. I took a screenshot with the 'shootme' app and proceeded to look at the gallery to make sure it came out okay. The gallery crashed and i was sent to the home screen. I swiped to a different homescreen when my phone froze halfway through the transition to the next screen. No combination of buttons/long presses were able to get me out of it so i went ahead and did a battery pull. So my dilemma is that now i'm stuck at the LG boot logo with no blue status bar under it. It freezes there and will not do anything every time i boot up. volume down+power does not give me access to recovery nor does any other button combo get me past the LG boot logo.
Are there any other methods i might be able to use like ADB or what not to get myself out of this situation? or at least into recovery? Any comments or suggestions would be greatly appreciated as i've been searching for hours with little help and my eyes are starting to get strained.

hmmm.. I know it's a simple question, but I gotta ask.. are you holding the pwr and volume down button long enough? you have to keep holding it even after you see the LG screen.. Keep holding until you see the 2nd screen?
If so.. do the nvflash again? Edit: Not sure if I would do this without getting further guidance tho..

schmit said:
hmmm.. I know it's a simple question, but I gotta ask.. are you holding the pwr and volume down button long enough? you have to keep holding it even after you see the LG screen.. Keep holding until you see the 2nd screen?
Click to expand...
Click to collapse
This. I remember when I boot looped my phone I had the problem of letting go of the volume key too early, you need to hold down volume and power from a totally powered off phone until recovery actually starts and you see the green "android" logo of CWM.
Try re-flashing CWM, NVFlash CAN fail. There is literally nothing you can do within the OS that will prevent recovery from working. Either you did something wrong somewhere along the recovery process or you discovered an entirely new problem with the phone. I'm going to hazard a guess and say it's the former.

Thanks for the response guys. I wish that it was the case of not holding the buttons long enough. I have tried numerous times with the buttons held down for a long period of time. I even held the combo down for almost 5 minutes a few times.
Every time i try to boot up, it won't go past the LG boot screen so i would pull the battery out and go through flashing CWM through NVflash again. I'm sure I'm not missing anything because everything goes through and gets sent to the phone successfully.
I did happen to run into a thread that was closely similar to mine but his method was to just keep reflashing CWM and the stock recovery back and forth every time it failed until it turned on. I might have to try that if i cannot figure out this problem out soon. Not being able to use this phone is killing me! heh.

I just joined your club. Wow this sucks.

So apparently this is a whole new problem that's been found? Every other help thread seems to point to using NVflash or remaking the partitions due to a bad flash using an O2x based file instead of G2x.
But none of those solutions come close to doing anything. There has been some people with the same problem as me but aren't proactive at all enough to get someone's attention, so i'm guessing this problem is getting pushed to the side with people just going about getting their phones replaces/buying new ones.
I did happen to run into a thread on paulobrien/modaco's forum that had people using NVflash to get out of any sticky situation like this. It just reverts everything back to the stock factory settings but with root. We cannot use this though because he hasn't built it to be compatible with our LGP999's because everything was built for their UK LGP990's. Maybe that's a start to getting this solution fixed?

I hate to say this, bit you might have to call t mobile and get a replacement. Flash back to stock recovery and they won't know you messed with anything.
Sent from my Nexus 5g using XDA Ultimate App

Don't send back....you'll get same defacement a battery pull go into nvflah and go back stock then flash nv flash fix pArtitions

As I have mentioned before, NVflash does NOT give me access to my recovery let alone solve anything else. NVflash DOES work and does sucessfully send both CWM and the stock recovery but when I try to boot into either of them, let alone just power on normally, it simply DOES NOT go past the LG boot screen. it just hangs there doing nothing at all until I pull the battery out and do the same process over until it just hangs again.
while it is on/stuck at the LG screen, my computer does not recognize it so i cannot even try and run ADB commands. It does however, recognize it when I plug it in using the volume buttons held down when I use NVflash but there's nothing else I can do besides use NVflash obviously.

Jduhb said:
As I have mentioned before, NVflash does NOT give me access to my recovery let alone solve anything else. NVflash DOES work and does sucessfully send both CWM and the stock recovery but when I try to boot into either of them, let alone just power on normally, it simply DOES NOT go past the LG boot screen. it just hangs there doing nothing at all until I pull the battery out and do the same process over until it just hangs again.
while it is on/stuck at the LG screen, my computer does not recognize it so i cannot even try and run ADB commands. It does however, recognize it when I plug it in using the volume buttons held down when I use NVflash but there's nothing else I can do besides use NVflash obviously.
Click to expand...
Click to collapse
Did you ever find a solution to this issue? Because my phone is doing this...
I attempted to restore my phone back to the wrong backup that was from a galaxy sII (2.3.4 i think); needless to say, the restore failed. I then restarted my phone from CWM and it gets stuck at LG screen.
I have tried to NVflash back to stock; nothing. same thing reflashing back to CWM.
ideas?

have you tried this link out yet?
http://forum.xda-developers.com/showthread.php?t=1180331

same problem..... anybody find something to fix this yet?

From what I heard is that you need to remove the battery, then boot into recovery or something.
Sent from my G2X

Use smartflash for the p990 but only use the p999 ap.bin file which will put the rom and kernel back to stock p999.

Rom for recovery always fixes any soft brick back to stock 2.3.3 OTA. It's saved my phone multiple times from stuck on S/W screen to being stuck on lg logo or even the dreaded can't mount sdcard-cache errors in cwm.
Sent from my LG-P999 using xda premium

I used the following method when Clockworkmod became corrupted and was unable to mount my sd card. I had just wiped everything on my phone intending to install a new rom when the issue happened. I could not even get to the S/W upgrade screen. It saved my phone. Hope it works for you.
http://forum.xda-developers.com/showthread.php?p=17258229

jcbofkc said:
I used the following method when Clockworkmod became corrupted and was unable to mount my sd card. I had just wiped everything on my phone intending to install a new rom when the issue happened. I could not even get to the S/W upgrade screen. It saved my phone. Hope it works for you.
http://forum.xda-developers.com/showthread.php?p=17258229
Click to expand...
Click to collapse
omg thank you so much! It worked! Not only that but i was stuck on frodo 2.2.2 before which is why i was messing with my phone in the first place and now its on gingerbread. Awesome! thank you!!!!

sabotage99 said:
omg thank you so much! It worked! Not only that but i was stuck on frodo 2.2.2 before which is why i was messing with my phone in the first place and now its on gingerbread. Awesome! thank you!!!!
Click to expand...
Click to collapse
Glad for you that it worked.
Kwes1020 pointed me in the right direction last week. Be sure to give a thanks to ILUHA_89 who came up with the fix.

Amazing how people are soo lost without providing them link after link to other threads. They are soo lazy and can't follow simple directions, each time i get a new phone i go to that section on xda and soak up all the information as it usually is already there. It's just funny is all i guess.

d12unk13astard said:
Amazing how people are soo lost without providing them link after link to other threads. They are soo lazy and can't follow simple directions, each time i get a new phone i go to that section on xda and soak up all the information as it usually is already there. It's just funny is all i guess.
Click to expand...
Click to collapse
It's really not that big a deal. I was brand new to android once and asked all sorts of things.
I, like you, happen to read everything I can get my hands on. Some struggle going through all the info. I was here the day the forum opened, so I kind of remember where everything is.
Some are lazy and others just have no idea what the heck is going on and are intimidated by certain processes. I would rather help someone instead of listening to them ***** about their broken phone.

[Oh Crap] XOOM is dead and it won't boot up!

I don't have a history of random reboots other than the once in a blue reboot because the browser gets stuck. I was using my Xoom last night before going to bed checking out a couple of website. I laid it down and went to bed and this morning I just put it in my bag and left to work.
The Xoom doesn't get past the Motorola logo and then the screen dims a black-blueish tint as if it were on but not on. I booted into recovery and tried to do a nandroid restore to a prior date. The restore finishes but when I reboot the Xoom still has the same issue.
The last thing I downloaded on the Xoom was that new market but I didn't like it so I uninstalled it. Right now the Xoom is plugged in charging. I don't believe it's the screen because I'm able to navigate through recovery without it shutting off. I'm stuck. What could it be?
By the way I pressed Vol Up + Power to force reboot and it's not working. Still a blackish blue tint screen.

Not sure where to put this but I can't post in the development thread. I flashed to 3.2 stock from rooted 3.1 stock and I'm stuck in a bootloop.
Any thoughts?

fleury14 said:
Not sure where to put this but I can't post in the development thread. I flashed to 3.2 stock from rooted 3.1 stock and I'm stuck in a bootloop.
Any thoughts?
Click to expand...
Click to collapse
Not for nothing but you're thread jacking.

Not trying to. Just didn't want to litter with a whole new thread.
Sent from my Nexus S 4G using Tapatalk

It's cool but my Xoom is still dead
I'm going to try and do the update.zip for 3.2 after class and see if it boots up with that. This sucks.
Sent from my PC36100 using XDA App

Update:
I downloaded the 3.2 update that's in the development section and installed it. It still won't boot past the Motorola logo. It goes to the Motorola logo and then the screen turns blackish blue. If I hit the power the screen goes black. It was working g fine yesterday and I'm out of ideas.
Sent from my PC36100 using XDA App

Try going back to the beginning. Flash stock 3.0 and lock. If your xoom boots then you're back in the game. If not, at least its stock to send in for warranty repair.
Sent from my HD2

That will have to wait until tomorrow. What could have caused it?
Sent from my PC36100 using XDA App

Dunno........just blame Motorola......Its fun! Seriously I have no idea, I hope you get it worked out. At least you can get into fastboot & recovery.
Sent from my HD2

jase33 said:
Dunno........just blame Motorola......Its fun! Seriously I have no idea, I hope you get it worked out. At least you can get into fastboot & recovery.
Sent from my HD2
Click to expand...
Click to collapse
I hope it's not an issue with my screen. I just find it weird that the screen shows that weird tint and if I hit the power button it goes black. It's as if the tablet is on but I'm not seeing an image on the screen. When I did a nandroid restore it got past the Motorola logo and went into the next phase (boot animation). It froze on the boot animation within 1 second of entering it. I left it alone for 30 minutes and it didn't do anything.
I don't want to send it back to Moto because G-D only knows when I'll get it back. Does anyone have experience with their repair ETA's? I'm nervous on sending it in because I read a thread where some Xoom owner got accused of having water damage. I don't want to them use that as an excuse so they won't fix it.

I have no personal experience. But there were a couple of posts in the General section (April, May time frame) from users who sent there Xoom to Moto for repair. All reported outstanding service. Call Motorola customer service and they will send you a shipping box overnight. Turn around in most cases was only 2 days. All had their devices back in under a week (departure to return). Good luck. Won't hurt to call Moto and talk to them about it.

Thanks. I'm going to have to return this to stock and relock it again before I can do that. I will call today and have them send me the box. I'm frustrated that I have nothing to play with.

gqstatus0685 said:
Thanks. I'm going to have to return this to stock and relock it again before I can do that. I will call today and have them send me the box. I'm frustrated that I have nothing to play with.
Click to expand...
Click to collapse
You didn't use an app like screen off and lock did you? I had a problem with that app after the update...at one point my screen went completely black, I could see my soft keys and could access settings but that was it. Had to boot to recovery and wipe all over again.
It's a long shot but sometimes apps that behaved before an update can act whacky.

No nothing like that. I remember I was watching some YouTube videos and ended my night. The last thing I downloaded was the new market but it looked hideous so I removed it. I'm trying different things and I can't get it to work.
Sent from my PC36100 using XDA App

I've not got a tablet (hanging out here since I'm considering buying a xoom), but have you tried wiping data, cache, and dalvik in cwm? That, or don't you guys have some sort of computer based flashing program like Samsung's ODIN? Wiping or a fresh reinstall has always fixed that issue on my Vibrant.
Goodluck!
Sent from my GT-I9000 using XDA App

Oxirane said:
I've not got a tablet (hanging out here since I'm considering buying a xoom), but have you tried wiping data, cache, and dalvik in cwm? That, or don't you guys have some sort of computer based flashing program like Samsung's ODIN? Wiping or a fresh reinstall has always fixed that issue on my Vibrant.
Goodluck!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
No such odin for us...and I don't think an SBF has been released, but we do have stock images from motorola for 3.0 and unofficial 3.1 and they can be flashed quite simply using fastboot. In your case, if you can still get into recovery, I don't believe this is a screen issue. It just sounds like you completely botched your software...not sure how this could have happened...but honestly, if you are curious to see exactly whats going on and you have ddms, just type ddms.bat into CMD while in your platform-tools folder, and then boot up your xoom and read the output. This will tell you exactly whats going on. If it says cannot detect device, it may be an issue with debugging not being activated from your last flash...that being said, I have been stuck at the Moto screen several times and luckily, restoring to stock 3.0 has ALWAYS gotten me out of it, as long as you can get into fastboot, you should be good to go.

Wipe, wipe, repeat!
This most certainly is a software issue. The fact alone that the device is showing the boot logo proves that the screen is functional. Sounds like a boot img problem.
I have had similar issues on a few occasions with my Evo, doing a full wipe and restore has always done the trick as has been posted above.
Good luck Gq.

dhemke17 said:
No such odin for us...and I don't think an SBF has been released, but we do have stock images from motorola for 3.0 and unofficial 3.1 and they can be flashed quite simply using fastboot. In your case, if you can still get into recovery, I don't believe this is a screen issue. It just sounds like you completely botched your software...not sure how this could have happened...but honestly, if you are curious to see exactly whats going on and you have ddms, just type ddms.bat into CMD while in your platform-tools folder, and then boot up your xoom and read the output. This will tell you exactly whats going on. If it says cannot detect device, it may be an issue with debugging not being activated from your last flash...that being said, I have been stuck at the Moto screen several times and luckily, restoring to stock 3.0 has ALWAYS gotten me out of it, as long as you can get into fastboot, you should be good to go.
Click to expand...
Click to collapse
Thanks for the advice. I was too busy yesterday (Full Time Work and Student) to fix it. I will try today since I don't have class. I really want to see what caused the problem so I will try that command in CMD and will post the output on these forums. Hopefully a dev can use it in the future to prevent this from happening to someone else.
I miss my Xoom.
I'm assuming I would CD to the directory and then run that command, correct?

Ok I guys I included the attachment so maybe someone can tell me what's wrong with my Xoom.
When I ran that command in command prompt a debug window popped up. Let me know if the attachment makes sense.
Uncaught Exception most likely has to do with software as I remember fixing Blackberry's that always had those issues but I could be wrong.
Update:
I followed this thread
Re-Lock & Unroot
http://forum.xda-developers.com/showthread.php?t=1084537
and everything successfully pushed. I ended up getting an error messaage in fastboot (Failed image SOS 0x0002) so I decided to unlock the device by running fastboot oem unlock command. It completed successfully and got rid of the error message in fastboot. When I hit reboot it got past the Motorola logo and froze at that honeycomb animation (right in the beginning. I turned it off and turned it on again and now it won't go past the Motorola screen.
I went on a chat with Motorola and they will be sending me an email so I can send my Xoom for repair. I'm going to lock it again and send it back. I'm giving up unless anyone recommeds something I can try.

Phone appears dead after failed flash.

So I was running CM10 Alpha 4.4 and phone was running pretty well for the 24 Hours I had it installed, but unfortunately I couldnt do any nandroid backups or restores. Would always reboot near the end. Well I was told that I could flash the boot.img file from the alpha 4.3 version and that should solve the issue until the newer version is fixed. Anyway, i installed Heimdall on my mac, started it as root. Created the pic, then went to flash the new boot.img. The first come times i got handshake failures, but then i restarted the phone into download mode again for the second time and it finally started to move forward. I then got the following response:
ERROR: Failed to confirm end of file transfer sequence!
GANG upload failed!
Ending session...
ERROR: Failed to send end session packet!
Click to expand...
Click to collapse
So it appeared that Heidmall had given up basically gave me the option to try again (aka, the start button was available again). The phone was still in download mode and appeared like it was still trying to do a download, so i left it be for about 10 minutes and still no change and heimdall wasnt doing anythign with it anymore. So i turned off the phone and tried to turn it back on to get it back into download mode again so i could try again. Unfortunately now the phone wont even turn on. I mean no responses at all that its getting an type of power or anything (aka, no lights). I took the battery out for 10 mins and then put it back in and still no luck. Its back on the charger, but I am worried that its dead. What sucks is that i just got this replacement phone in June after someone physically broke my old E4GT. =/
Any suggestions?

MACscr said:
So I was running CM10 Alpha 4.4 and phone was running pretty well for the 24 Hours I had it installed, but unfortunately I couldnt do any nandroid backups or restores. Would always reboot near the end. Well I was told that I could flash the boot.img file from the alpha 4.3 version and that should solve the issue until the newer version is fixed. Anyway, i installed Heimdall on my mac, started it as root. Created the pic, then went to flash the new boot.img. The first come times i got handshake failures, but then i restarted the phone into download mode again for the second time and it finally started to move forward. I then got the following response:
So it appeared that Heidmall had given up basically gave me the option to try again (aka, the start button was available again). The phone was still in download mode and appeared like it was still trying to do a download, so i left it be for about 10 minutes and still no change and heimdall wasnt doing anythign with it anymore. So i turned off the phone and tried to turn it back on to get it back into download mode again so i could try again. Unfortunately now the phone wont even turn on. I mean no responses at all that its getting an type of power or anything (aka, no lights). I took the battery out for 10 mins and then put it back in and still no luck. Its back on the charger, but I am worried that its dead. What sucks is that i just got this replacement phone in June after someone physically broke my old E4GT. =/
Any suggestions?
Click to expand...
Click to collapse
If you cant get into download mode with the key combo ( VOL- / POWER / HOME) then a Jig may be your only hope beside JTAG.

Since it sounds like its hard bricked, a JIG probably wouldnt work, right? I just dont want to waste time/money trying to get it fixed with that method if i should be going straight to a service provider that can do JTAG.

hi mate just an option
it sounds bricked if you hold down the volume up button the bottom button and the power button fallow the same steps in there to install a rom just dont use any zips just rebootyou can use CWM to do a recovery from a back up if not as a last resort reinstall the rom you are using what rom is it that you use im trying to find a good one but you could try to do the update again or use a pc try back up the files you would need then reinstall but hope i helpped please click the tanks button if you feel i helped.

99ryan993 said:
you can use CWM to do a recovery from a back up if not as a last resort reinstall the rom you are using what rom is it that you use im trying to find a good one but you could try to do the update again or use a pc try back up the files you would need then reinstall but hope i helpped please click the tanks button if you feel i helped.
Click to expand...
Click to collapse
lol, you didnt help at all. You obviously didnt read my problem.

MACscr said:
Since it sounds like its hard bricked, a JIG probably wouldnt work, right? I just dont want to waste time/money trying to get it fixed with that method if i should be going straight to a service provider that can do JTAG.
Click to expand...
Click to collapse
Im not exactly sure if a jig will help you. There cheap to buy or make. I think its a long shot but who knows. How long have you had the phone and where did you buy it from? JTAG is $50 i believe. You could always try taking it to a verizon store.

Just got pointed out to me that I accidentally posted in the s3 forum when i have a e4gt. The local sprint store is replacing my phone though for only $35. Though their manager showed me her s3 and its pretty freakin sweet. With trade in and upgrade, I could get the s3 for about $140 after fees. Not sure if I am going to do it.

MACscr said:
Just got pointed out to me that I accidentally posted in the s3 forum when i have a e4gt. The local sprint store is replacing my phone though for only $35. Though their manager showed me her s3 and its pretty freakin sweet. With trade in and upgrade, I could get the s3 for about $140 after fees. Not sure if I am going to do it.
Click to expand...
Click to collapse
Nevermind, I am getting the s3 on Saturday when I am eligible and just selling the epic 4g touch on ebay.

lay off them bath salts and you would be suprised how much easier it is to navigate xda and post in the correct forum lol.

[Q] Help Me I really effed up!

Good Morning Everyone, This is my first post. I try to never post just read. I have read and read but to no avail. I have a AT&T Samsung infuse 4g. it WAS running froyo. What I mean by WAS, is that I was trying to install the modded 3e recovery so I could install clockworkmod recovery. During this process I read that I need to mount the /system partition as read/write I did this using the tool box that was created by some of your developers. It is awsome by the way. Well I did that and put a new recovery file in the /bin but it did not work as the website claimed so I thought well I should delete the old one. Bad Idea when I did the reboot it stopped me at the samsung screen. I tried to hard reboot it pulled the battery talked to it with a really kind voice and nothing happend. So I decided to use GEG's Ultimate Unbrick because this has worked for me in the past when i have messed up. So I put my phone into download mode and started the process with Odin. And here is where it gets bad.... one of my children was talking with me during the process and he decided to unplug my phone.. AHH EFFFFFF! I thought. Well when I tried to fix it it was to late. My phone will no longer turn on or even pretend to start. I am broke and cannot afford a new phone plus my wife would kill me seeing we have 6 children and it is right before christmas if I came home with a new galaxy note 2 Please Please can any one help a desperate dad with a busted Samsung Infuse. Thank you all for this awesome website that has taught me alot.. Please dont kill me for posting something someone has already posted because I could not find anything that was helpful for this situation with my phone.

Xda is awesome!
Well I didnt read good enough I guess because while I was waiting not so patiently for a reply I found this http://forum.xda-developers.com/showthread.php?t=1194294 which got me back to download mode yes!!!! Thank you thank you thank youXDA love you guys! Merry Christmas! PS I still want the Galaxy Note 2 so if you have a extra one please PM me and I will give you my address LOL!

MerkTheMedia said:
Well I didnt read good enough I guess because while I was waiting not so patiently for a reply I found this http://forum.xda-developers.com/showthread.php?t=1194294 which got me back to download mode yes!!!! Thank you thank you thank youXDA love you guys! Merry Christmas! PS I still want the Galaxy Note 2 so if you have a extra one please PM me and I will give you my address LOL!
Click to expand...
Click to collapse
Awesome! Glad you got your phone functioning again. Being persistent in searching and reading and trying to find answers usually results in good outcomes. :thumbup:
Sent from a de-Funkt Infuse

Okay now I have really done it this time. So I worked a 18 hour day and thought well instead of getting some rest i will install Gingerbread on my infuse. To make a long story short while I was using odin to install it paused for a long time at the format stage, so I thought well I will just turn it off even though it says not to and then.....well it did a rainbow colored screen I tried to figure it out last night with no luck. So I have been working on it all morning the rainbow screen is gone but now it just goes from black to all white screen. I have tried every possible way to get into download mode with no luck. Am I screwed or what? Does anyone have any suggestions. If I am out of luck does anyone know if bestbuy's warrenty covers rooted phones that are [email protected] bricked?

You just need To update your boot loader.
You can navigate in the screwy screens but it takes patience and some guesswork. Been there
Also...
Good instructions here
http://forum.xda-developers.com/showthread.php?p=14550608
USB cables have given me issues as well as drivers. Install Kies to get the drivers.
Another...
http://forum.xda-developers.com/showthread.php?p=23118134
Sent from my SGH-I997 using xda app-developers app
Sent from my SGH-I997 using xda app-developers app

saxk said:
You just need To update your boot loader.
You can navigate in the screwy screens but it takes patience and some guesswork. Been there
Also...
Good instructions here
http://forum.xda-developers.com/showthread.php?p=14550608
USB cables have given me issues as well as drivers. Install Kies to get the drivers.
Another...
http://forum.xda-developers.com/showthread.php?p=23118134
Sent from my SGH-I997 using xda app-developers app
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
It still will not get me into download mode it is powering on and off connecting and disconnecting I have the drivers installed I have tried gtg's guide I have tried qstars one click nothing is working. These have worked for me in the past but that was because I can get into down load mode. Unfortunately not any more Is there a way to make the phone stay on and connected so it stops going black to white to black screen? I am so bummed out! I have been reading for so many hours my brain hurts. I have learn a ton but I can't do anything with my new knowledge with no phone!!!AAAHHHHHH

MerkTheMedia said:
It still will not get me into download mode it is powering on and off connecting and disconnecting I have the drivers installed I have tried gtg's guide I have tried qstars one click nothing is working. These have worked for me in the past but that was because I can get into down load mode. Unfortunately not any more Is there a way to make the phone stay on and connected so it stops going black to white to black screen? I am so bummed out! I have been reading for so many hours my brain hurts. I have learn a ton but I can't do anything with my new knowledge with no phone!!!AAAHHHHHH
Click to expand...
Click to collapse
if you're boot looping in the samsung logo, it could be your power button. search for how to fix power button

qkster said:
if you're boot looping in the samsung logo, it could be your power button. search for how to fix power button
Click to expand...
Click to collapse
Qkster its a honor to have you comment on my thread, Unfortunately Im not boot looping to the samsung logo it is just a black then white then black back and forth taunting me with every blink. I did read the thread about the power button earlier though and that is unfortunately not the fix either. I do appreciate the input you guys really do try and help! Maybe you can answer a question for me is there a way to get to the phone through command prompt? I really need this phone fixed. My wife has been telling me I shouldnt be messing around with it because im gonna break it. I really dont want to tell her she was right. I will never hear the end of it lol!

MerkTheMedia said:
Qkster its a honor to have you comment on my thread, Unfortunately Im not boot looping to the samsung logo it is just a black then white then black back and forth taunting me with every blink. I did read the thread about the power button earlier though and that is unfortunately not the fix either. I do appreciate the input you guys really do try and help! Maybe you can answer a question for me is there a way to get to the phone through command prompt? I really need this phone fixed. My wife has been telling me I shouldnt be messing around with it because im gonna break it. I really dont want to tell her she was right. I will never hear the end of it lol!
Click to expand...
Click to collapse
You're too kind, Merk.
I'm not sure what happened to your phone. The Infuse is pretty sturdy. Flashing should not cause much of an issue. The faulty power button and corrosion of the circuit board were the most I've seen reported.
This is what I use to force the phone into download mode:
http://www.ebay.com/itm/Micro-USB-J...665854?pt=PDA_Accessories&hash=item3f201c4f3e
Once in DL mode, it's a matter of choosing Odin or Heimdall to bring it back to stock.
One other thought, try a different battery as well.

I had the same exact problem. If the only thing the phone will do is go into download mode, then Samsung will fix it (if your still under warranty). They fixed mine and sent it back to me. Then I tried to flash another ROM on there and while it was flashing, I went to the store, and when I came back it said failed. Then it would only go into the other download mode. The one that has this (phone...!...PC). It wouldnt show up on odin 1.7 anymore. So I ended up trying a USB cable for my HTC evo v, and the drivers installed, then it popped up on Odin. I used G2G's Ultimate Unbrick (dude is a f-ng genius, all credit goes to him) and instead of putting the pit, PDA, and phone file on there and flashing, I flashed one at a time......then....I went back and flashed all at once and everything worked perfect. If your still having trouble with it, I can tell you exactly how I did it, and maybe that will work for you. Sorry to but in on this post and sorry it was so long of a reply. I just no what its like when you half brick an infuse. Mine was like that for 6 months because I couldn't get any computer to recognize it. But anyway, I hope I was helpful.
Sent from my SAMSUNG-SGH-I747 running CM10 4.1.2 JB using xda premium

michaelsinbad said:
I had the same exact problem. If the only thing the phone will do is go into download mode, then Samsung will fix it (if your still under warranty). They fixed mine and sent it back to me. Then I tried to flash another ROM on there and while it was flashing, I went to the store, and when I came back it said failed. Then it would only go into the other download mode. The one that has this (phone...!...PC). It wouldnt show up on odin 1.7 anymore. So I ended up trying a USB cable for my HTC evo v, and the drivers installed, then it popped up on Odin. I used G2G's Ultimate Unbrick (dude is a f-ng genius, all credit goes to him) and instead of putting the pit, PDA, and phone file on there and flashing, I flashed one at a time......then....I went back and flashed all at once and everything worked perfect. If your still having trouble with it, I can tell you exactly how I did it, and maybe that will work for you. Sorry to but in on this post and sorry it was so long of a reply. I just no what its like when you half brick an infuse. Mine was like that for 6 months because I couldn't get any computer to recognize it. But anyway, I hope I was helpful.
Sent from my SAMSUNG-SGH-I747 running CM10 4.1.2 JB using xda premium
Click to expand...
Click to collapse
Well im going to give it a shot I still have the old infuse I tried to make my own jig which didnt work for me so I took it into bestbuy and they gave me a brand new phone and in all of the hustle and bustle of christmas shopping going on around me they did not take my bricked infuse so now I have a spare to tinker with. Thanks I will definately give it a try and report with my findings
Sent from my SAMSUNG-SGH-I997 using xda app-developers app

michaelsinbad said:
I had the same exact problem. If the only thing the phone will do is go into download mode, then Samsung will fix it (if your still under warranty). They fixed mine and sent it back to me. Then I tried to flash another ROM on there and while it was flashing, I went to the store, and when I came back it said failed. Then it would only go into the other download mode. The one that has this (phone...!...PC). It wouldnt show up on odin 1.7 anymore. So I ended up trying a USB cable for my HTC evo v, and the drivers installed, then it popped up on Odin. I used G2G's Ultimate Unbrick (dude is a f-ng genius, all credit goes to him) and instead of putting the pit, PDA, and phone file on there and flashing, I flashed one at a time......then....I went back and flashed all at once and everything worked perfect. If your still having trouble with it, I can tell you exactly how I did it, and maybe that will work for you. Sorry to but in on this post and sorry it was so long of a reply. I just no what its like when you half brick an infuse. Mine was like that for 6 months because I couldn't get any computer to recognize it. But anyway, I hope I was helpful.
Sent from my SAMSUNG-SGH-I747 running CM10 4.1.2 JB using xda premium
Click to expand...
Click to collapse
okay I tried but that didnt work either. Can you go ahead and explain "exactly" what you did maybe it will work!
Thanks again for everyones help!

Ok first I downloaded the unbrick package from this website. I downloaded the drivers for the infuse (not sure exactly where I got them from). I would just Google them. Then I tried every USB port on the laptop. Then switched cables and it finally worked. Opened Odin 1.7 and clicked pit, then flashed. Then I unplugged it, took the battery out and put back in and tried to boot. Didn't work. Then flashed PDA. Did same steps as before and still didn't work. Then flashed phone file. Tried to boot and still didn't work. Then I flashed all 3 files at once. Also, not sure if you know or not but the only thing that should be checked in Odin is f: reset time. Then the phone booted up and it stayed on at&t screen for about 5 minutes then finally came on. Also, you could also try to flash this other PDA file on there. I have the link saved on my computer but I'm not at home right now so I'll have to post that later. In easier steps
1. Put phone in Download mode and plug into pc.
2. Run Odin as admin and only thing checked is f reset time.
3.Flash pit then try to boot
4. Flash PDA then try to boot
5. Flash phone then try to boot
6. Flash all three at once
7. After flash While in download mode, unplug USB cable, take battery out and put back in
8. Reboot phone.
Sorry everything is all jumbled, I just got back to my home state from a road trip and I'm running on about 6 hours of sleep in 3 days. I hope this works for you. Also, there is a video on YouTube of a unbrick service for the phone. Its $30. I personally would not try it but its just an idea if you would want to.
Sent from my SAMSUNG-SGH-I747 using xda premium

I had the issue where I had the phone, the exclamation mark, and the computer symbol (The Black Screen of Death: Imaged Attached), that is all it would show when I turned it on. I thought the phone was completely bricked until I did the following, which put it into a hidden download mode and allowed ODIN to recognize it. I DID NOT NEED TO BUY A USB JIG.
1. Make sure you have Odin already downloaded and ready to go.
2. Remove the SIM and SD Cards
3. Load up Odin and make sure it is up and running on the computer. DO NOT plug your phone into the computer yet.
4. Reinstall the Battery and plug the phone to the USB cable to the computer.
5. Hold down both Volume keys and then push and hold the power button
6. Keep holding the buttons until it goes to black, KEEP HOLDING A SECOND TIME until it goes to black and the icon comes back on.
7. Now when it goes Black the second time release the Power button only.
8. You should now be in Download mode. The key is holding the buttons, letting it go to black once, and then letting it go to black again, and then release only the power button while your fingers are still on the volume buttons.
9. Now Odin should recognize the phone on a Com port (turn yellow).
10. You are now ready to return it back to stock.
I hope this helps!

did you ever get your infuse fixed man?
Sent from my SAMSUNG-SGH-I747 running CM10 JB 4.1.2 using xda premium

Yes I tried to make my own jig but my fat shaky hands could get the end of the wires to hit the correct contacts so I ordered one online and that got me into download mode! Now I'm running jelly bean! Thanks to everyone that helped out I love you guys!!!! PS. Don't skip backing up your efs folder!! Unless you want a headache. But with all my problems it has taught me a lot. My number one tip is to read read read there is always an answer! Thanks again everyone! Always hit the thanks button its the least we can do for all of these brilliant hard working developers.
Sent from my SGH-I997 using xda app-developers app

Is my Sensation bricked or not?

Hello, guys. I'm new here, so please dont hate me.
I think I've bricked my Sensation.
So, here's the deal. My Sensation was unlocked and S-OFF, I was using Ivanich's CM 12 and my phone started to work real slow. Then I read somewhere on XDA that changing data partition to f2fs can speed it up a bit. So I tried to change partition in TWRP and it stucked saying formating or something like that, I waited for 30-40 minutes but no result. And I removed the battery. Since then Twrp says "cant mount \data,\system,\cache" and so on. I tried to format it back to ext4, but no luck. I think my internal sd corrupted.
The next thing I tried was to install RUU, but it also stucked on 37%. (I checked that it stucks on <bootloader> [RUU]WP,dzdata,0).
So now I've got my Sensation stucked in RUU mode, with silver HTC logo and 4 triangles in the corners. I can't go to recovery and anything, but fastboot works.
And here's the main question: can I make it back to work or is it completely dead and i can throw it away?
P.S. I've read lots of threads with simillar problems and as far as I see this is the end for my phone. Just needed one last confirmation from someone more experiensed than myself.
I realy liked my Senny, but maybe it's time for upgrade?

fallen_apple said:
Hello, guys. I'm new here, so please dont hate me.
I think I've bricked my Sensation.
So, here's the deal. My Sensation was unlocked and S-OFF, I was using Ivanich's CM 12 and my phone started to work real slow. Then I read somewhere on XDA that changing data partition to f2fs can speed it up a bit. So I tried to change partition in TWRP and it stucked saying formating or something like that, I waited for 30-40 minutes but no result. And I removed the battery. Since then Twrp says "cant mount \data,\system,\cache" and so on. I tried to format it back to ext4, but no luck. I think my internal sd corrupted.
The next thing I tried was to install RUU, but it also stucked on 37%. (I checked that it stucks on <bootloader> [RUU]WP,dzdata,0).
So now I've got my Sensation stucked in RUU mode, with silver HTC logo and 4 triangles in the corners. I can't go to recovery and anything, but fastboot works.
And here's the main question: can I make it back to work or is it completely dead and i can throw it away?
P.S. I've read lots of threads with simillar problems and as far as I see this is the end for my phone. Just needed one last confirmation from someone more experiensed than myself.
I realy liked my Senny, but maybe it's time for upgrade?
Click to expand...
Click to collapse
see here
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588
check also post #35 from that thread

rzr86 said:
see here
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588
check also post #35 from that thread
Click to expand...
Click to collapse
Thanks for your reply
Yes, I've read this thread and it seems to work, but the thing is that I'm stuck in RUU mode and can't boot to the recovery. The only thing I see on the screen of my phone is silver htc logo and 4 warning logos in the corners.

fallen_apple said:
Thanks for your reply
Yes, I've read this thread and it seems to work, but the thing is that I'm stuck in RUU mode and can't boot to the recovery. The only thing I see on the screen of my phone is silver htc logo and 4 warning logos in the corners.
Click to expand...
Click to collapse
did you try to use the command fastboot reboot bootloader from ruu mode?

Meh, it seems to be a lost cause.
I had an exact same issue. /system, /data and /cache partitions got completely messed up, with no hope of restoring them.
The only possibilities for fixing that seem to be changing the emmc chip... or somehow plugging it under Linux disto and completely rewriting the partition table. In theory it should work, but I have completely zero clue how to get to it.
Darn, if only Android/ARM would be as simple to fix as x86 systems.
Oh well, At least I have a nice paperweight. A shame
Screw TWRP. Someone failed to test their software and we are paying the price.

rzr86 said:
did you try to use the command fastboot reboot bootloader from ruu mode?
Click to expand...
Click to collapse
Yes, I tried, phone reboots but nothing changes. Just same RUU mode htc logo on the screen
XTacDK said:
Meh, it seems to be a lost cause.
I had an exact same issue. /system, /data and /cache partitions got completely messed up, with no hope of restoring them.
The only possibilities for fixing that seem to be changing the emmc chip... or somehow plugging it under Linux disto and completely rewriting the partition table. In theory it should work, but I have completely zero clue how to get to it.
Darn, if only Android/ARM would be as simple to fix as x86 systems.
Oh well, At least I have a nice paperweight. A shame
Screw TWRP. Someone failed to test their software and we are paying the price.
Click to expand...
Click to collapse
God damn TWRP!
So for now I think my Senny is a useless peace of gear. Maybe someday people find out how to fix this issue, I hope:fingers-crossed:

fallen_apple said:
Yes, I tried, phone reboots but nothing changes. Just same RUU mode htc logo on the screen
God damn TWRP!
So for now I think my Senny is a useless peace of gear. Maybe someday people find out how to fix this issue, I hope:fingers-crossed:
Click to expand...
Click to collapse
Same with my Senny, tried to change the rom and got stuck on bootloader ((((p
All sympthoms are the same, half a day looking for solution but, no way ((((((((((

XTacDK said:
Meh, it seems to be a lost cause.
I had an exact same issue. /system, /data and /cache partitions got completely messed up, with no hope of restoring them.
The only possibilities for fixing that seem to be changing the emmc chip... or somehow plugging it under Linux disto and completely rewriting the partition table. In theory it should work, but I have completely zero clue how to get to it.
Darn, if only Android/ARM would be as simple to fix as x86 systems.
Oh well, At least I have a nice paperweight. A shame
Screw TWRP. Someone failed to test their software and we are paying the price.
Click to expand...
Click to collapse
Same here my friend, BRICKED WITH TWRP, stuck with 4 triangles and only ruu which also gets stuck at 42%
---------- Post added at 10:10 PM ---------- Previous post was at 10:07 PM ----------
fallen_apple said:
Thanks for your reply
Yes, I've read this thread and it seems to work, but the thing is that I'm stuck in RUU mode and can't boot to the recovery. The only thing I see on the screen of my phone is silver htc logo and 4 warning logos in the corners.
Click to expand...
Click to collapse
if you find a fix update this post...

I have the exact same problem. Bootloader is unlocked and fastboot is working, and I even succeeded in flashing recovery (at least no error showed up when doing so), but when I try to get into recovery mode or simply boot the phone, HTC splash screen shows up and lasts indefinitely. Is there a solution for this?

Ranching said:
I have the exact same problem. Bootloader is unlocked and fastboot is working, and I even succeeded in flashing recovery (at least no error showed up when doing so), but when I try to get into recovery mode or simply boot the phone, HTC splash screen shows up and lasts indefinitely. Is there a solution for this?
Click to expand...
Click to collapse
Try redownloading the recovery (download 4EXT, avoid TWRP at all costs!), and reflashing it.
It might be a CRC error.