Related
Ok so today I mow my yard and I plug in my Thunderbolt in to the USB charger on my PC when I come inside my phone is bootlooping. So I think ok whatever I will flash one of the many backup's I made.
So I pull the battery and boot into the bootloader, then when I go into recovery after about 2 seconds the phone powers off and starts bootlooping again??? Ok that's a first for me and I have been flashing and rooting since launch day of the OG Droid, (ok, ok not since the first day but like a month later). So I pull the battery again this time for 30 minutes because I read someone else had something like this happen yesterday. When I put the battery back in same thing! Now I pull the battery for 4 hours...same outcome.
Now I'm thinking RUU time so I grab the stock RUU pull the SD card from my Thunderbolt pop it in my Incredible load the RUU renamed to PG05IMG.zip and put it back in the Thunderbolt. Load the bootloader and flash the RUU. Reboot after it's done and would you believe it...the same thing! the phone won't load past the splash screen before rebooting.
I forgot to mention before trying all this I tried using adb to reboot into recovery and I kept getting "error: device not found" and I know how to use adb.
It's only been about 9 hours since I've been able to use my 2.3.4 GingerBread with parts of 3.0 Sense Thunderbolt and I already having withdrawals how am I going to make the next 2 to 3 weeks while it's being repaired???
Ok end rant...
Go to verizon, swap it for a new one. Warranty case for sure.
bilbobrian said:
Go to verizon, swap it for a new one. Warranty case for sure.
Click to expand...
Click to collapse
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.
I'm loosing faith in the Thunderbolt. I really feel we are all just a bunch of beta testers.
bunklung said:
I'm loosing faith in the Thunderbolt. I really feel we are all just a bunch of beta testers.
Click to expand...
Click to collapse
Huh? Off topic and makes no sense.
//Tap'd on my TBolt while grounded\\
bp328i said:
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.
Click to expand...
Click to collapse
I understand your rooted but if it cant boot up then there is a problem. Just go to verizon and show them. Once they see it cant boot properly they will exchange it or overnight one to you.
I apologize if Im missing something..
bp328i said:
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.
Click to expand...
Click to collapse
You may get away with getting it swapped through warranty. But I can't promise you it won't come back at you. Someone may have a solution for you though. Wouldn't give up yet. Sorry I don't.
//Tap'd on my TBolt while grounded\\
chkmate said:
Huh? Off topic and makes no sense.
//Tap'd on my TBolt while grounded\\
Click to expand...
Click to collapse
*Shrug*
He has a problem, I do too. We both own Thunderbolts. Maybe I should have been more specific.
To each his own. The end.
bunklung said:
*Shrug*
He has a problem, I do too. We both own Thunderbolts. Maybe I should have been more specific.
To each his own. The end.
Click to expand...
Click to collapse
Well then relate your problem with his. Just saying "your losing faith in Thunderbolt" tells me nothing. Don't mean to sound like an a$$, just saying. When I read your first comment I got nothing from it.
That being said...I haven't been a Bolt owner for long, but it does seem like a strange issue. You would think flashing a radio or backup would resolve the issue. But hasn't.
//Tap'd on my TBolt while grounded\\
Definitely sounds like a Warranty Issue. I'd try to get it exchanged if no one can come up for a solution to the problem.
I had a G1 back in the day that had some odd problem and I was rooted, Tmo looked at it and wouldn't touch it. So, I called HTC. I told them that I purchased the phone off Craigslist so Tmo couldn't help me, and asked how the warranty works on their end. They said that since the production of the phone started less than a year ago, they knew it was still eligible for warranty even without a receipt. There would be a triage fee if it was found to be a non-warranty issue, and it was something like $40 including the shipping back. I acted dumb when they asked if it was rooted...asked them what that meant? LOL. Sent it in, they fixed it and sent it back to me, no charge. Fast too. I was very happy and that is why I have stuck with HTC since then. It may or may not work for you, but it was painless for me.
bp328i said:
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.
Click to expand...
Click to collapse
Such chivalry is rare in these days.
Applaud. Best of luck!
Sent from my ADR6400L using Tapatalk
bp328i said:
Thanks, but I rooted it, therefore I have no warranty. I knew the chance I was taking when I rooted it so I'm paying for it to be repaired.
Click to expand...
Click to collapse
They don't care. Take my word for it. If it never boots they won't care.
I'm actually having this exact same issue. Has anyone found a solution yet or is the only solution to have the phone replaced?
Wow. I thought for sure hbooting the unsigned stock RUU would fix this. How about hbooting a signed ruu? It wouldn't hurt at this point.
Also make sure when you renamed the pgimg05. Zip that there was nothing at the end of the extention. I've heard some people say that windows has been known not to show that full file extension correctly.
raider3bravo said:
Wow. I thought for sure hbooting the unsigned stock RUU would fix this. How about hbooting a signed ruu? It wouldn't hurt at this point.
Also make sure when you renamed the pgimg05. Zip that there was nothing at the end of the extention. I've heard some people say that windows has been known not to show that full file extension correctly.
Click to expand...
Click to collapse
I thought hbooting the stock RUU would fix it as well, and yep it was named correctly. It's funny because it would stay on the hboot screen as long as I let it with no issue what so ever but within 2 seconds of going into recovery it would reboot.
I went back to Best Buy today as that is where I bought it to see how much they would charge to ship it out to be fixed. The mobile manager remembered me because I was 1st on the pre-order list. (I'm sure we all remember the train wreck the Best Buy pre-orders became) So any way he really went out of his way to help me. He said he has had 3 other Thunderbolts brought in for the same issue. He was able to send my phone in under their Black Tie program.
I told him I rooted the phone and was willing to pay for the repairs but he said he was pretty sure that the other 3 phones were not rooted. He said that he knew FOR SURE that at least one of the phones was not rooted because the lady that owned it did not have any branches in her family tree, (his words not mine). Since he has seen it 3 times he was not charging me. He only asked that I had the stock hboot on the phone. I had already flashed that in my attempt to get it running.
I'm with cstrife, I managed to destroy my tab with a mix of flashing and charging via outlets in India. It bootlooped for a while then just kind of gave up and began to display a strange download screen when I plugged it in to charge. I brought it to VZW and played stupid, I told them I woke up and it had this weird screen... I had a brand new one at my door the next morning and haven't heard a word from them... It probably just costs more to check it out deep enough to find out its rooted than it does to just give you a refurbished one, gut swap yours, and then send to someone else as a refurbished one...
Sent from my SCH-I800 using XDA App
Had this happen to me and just pulled my SD card, rebooted and it was fine. Not saying it will work for u but give it a shot.
Sent from my ADR6400L using XDA App
bp328i said:
I thought hbooting the stock RUU would fix it as well, and yep it was named correctly. It's funny because it would stay on the hboot screen as long as I let it with no issue what so ever but within 2 seconds of going into recovery it would reboot.
I went back to Best Buy today as that is where I bought it to see how much they would charge to ship it out to be fixed. The mobile manager remembered me because I was 1st on the pre-order list. (I'm sure we all remember the train wreck the Best Buy pre-orders became) So any way he really went out of his way to help me. He said he has had 3 other Thunderbolts brought in for the same issue. He was able to send my phone in under their Black Tie program.
I told him I rooted the phone and was willing to pay for the repairs but he said he was pretty sure that the other 3 phones were not rooted. He said that he knew FOR SURE that at least one of the phones was not rooted because the lady that owned it did not have any branches in her family tree, (his words not mine). Since he has seen it 3 times he was not charging me. He only asked that I had the stock hboot on the phone. I had already flashed that in my attempt to get it running.
Click to expand...
Click to collapse
Honesty turned out to be the best policy in this case. Congrats.
Sent from my ADR6400L using Tapatalk
MrHawaii said:
Honesty turned out to be the best policy in this case. Congrats.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Thanks, now I just have to wait 2 to 3 weeks to get it back. What to do with all that time!!!
I dl'ed the Nightly 123 for CM7 this AM around 4 then proceeded to make a nandroid then flash it. All hell broke loose from there. Bootloops, stuck @ white HTC screen, couldn't restore my nandroid. All was not bueno.
I ended up having to flash fresh and go through the displeasure of completely reconfiguring my phone. What a PITA. This is my first ever mishap w/ a flash and first ever failed nandroid. The md5 passed the check, it would go through the process of restoration but would get stuck @ the HTC screen.
Ughh, is it Friday yet?
Tx Redneck said:
I dl'ed the Nightly 123 for CM7 this AM around 4 then proceeded to make a nandroid then flash it. All hell broke loose from there. Bootloops, stuck @ white HTC screen, couldn't restore my nandroid. All was not bueno.
I ended up having to flash fresh and go through the displeasure of completely reconfiguring my phone. What a PITA. This is my first ever mishap w/ a flash and first ever failed nandroid. The md5 passed the check, it would go through the process of restoration but would get stuck @ the HTC screen.
Ughh, is it Friday yet?
Click to expand...
Click to collapse
The price we pay for freedom!!!...or something like that...just trying to cheer you up . I've soft bricked the phone a few times, but every time, as in your case, recoverable, if a PITA.
Tx Redneck said:
I dl'ed the Nightly 123 for CM7 this AM around 4 then proceeded to make a nandroid then flash it. All hell broke loose from there. Bootloops, stuck @ white HTC screen, couldn't restore my nandroid. All was not bueno.
I ended up having to flash fresh and go through the displeasure of completely reconfiguring my phone. What a PITA. This is my first ever mishap w/ a flash and first ever failed nandroid. The md5 passed the check, it would go through the process of restoration but would get stuck @ the HTC screen.
Ughh, is it Friday yet?
Click to expand...
Click to collapse
I have yet to "pay my dues to the Android gods" in this department.
Sooner or later it will happen, no matter how prepared one thinks they are.
And when it happens to me, I'll end up breaking all my own rules and posting without searching first, and get a taste of my own medicine for having been mean to some new people in the past.
And those people will bask in the satisfaction of the payback I'll be enduring.
^LOL
Glad you recovered it .
I have boot looped mine once a few weeks back and just 2 hours ago I Installed a UOT kitchen on a fresh install of Ninja, which I had completely configured and had forgotten to do a nand, which unfortunately broke the status bar (it would error out: Status bar has stopped working) No Status bar at all and it threw up the error like every 2 minutes. Lol
Man I couldn't even restore my nandroid that I do religiously prior to every flash. I has hacked to say the least.
I haven't bricked my Inspire (yet) but I have done a number on my old captivate as well as a few (don't hold it against me) iphones. In each case I was able to get the device up and running again. I think the worst part of the ordeal is when crap hits the fan after we know we did everything right.
Sent from my soon to be bricked Inspire using XDA Premium App
Or when "I'll just flash this new rom before I go to work. It only takes a few minutes." Then something goes wrong boss gets a call "I'm gonna be late I have explosive diarrhea." .
Bahahaha!
I almost called in but decided to do.it while I was working. It only took three frackin hours but it's done.
And the lesson here kids is don't assume that everything is going to go right if you choose to try and flash/update a rom before work.
ycode90 said:
Or when "I'll just flash this new rom before I go to work. It only takes a few minutes." Then something goes wrong boss gets a call "I'm gonna be late I have explosive diarrhea." .
Click to expand...
Click to collapse
man I wish that's all that happened to mine. Take a soft brick over a fried machine any day of the week. glad I bought two
Sent from my Desire HD using XDA App
What happened to it? Over oc?
Tx Redneck said:
I dl'ed the Nightly 123 for CM7 this AM around 4 then proceeded to make a nandroid then flash it. All hell broke loose from there. Bootloops, stuck @ white HTC screen, couldn't restore my nandroid. All was not bueno.
I ended up having to flash fresh and go through the displeasure of completely reconfiguring my phone. What a PITA. This is my first ever mishap w/ a flash and first ever failed nandroid. The md5 passed the check, it would go through the process of restoration but would get stuck @ the HTC screen.
Ughh, is it Friday yet?
Click to expand...
Click to collapse
Glad you recovered!!!
Tx Redneck said:
What happened to it? Over oc?
Click to expand...
Click to collapse
I think it had something to do with the rom Matt was running, but i'll let him expand on it if he drops back in.
I don't think you can actually fry it over oc'ing can you? Wouldn't it just freeze up or reboot first? Maybe overvolting or something.
Clearly, I don't know **** about the subject.
Scott_S said:
I think it had something to do with the rom Matt was running, but i'll let him expand on it if he drops back in.
I don't think you can actually fry it over oc'ing can you? Wouldn't it just freeze up or reboot first? Maybe overvolting or something.
Clearly, I don't know **** about the subject.
Click to expand...
Click to collapse
An excessive OC run for extended lengths or fully loaded(100%CPU usage) will kill it. Phones don't have the means to dissipate heat like a PC w/ a good cooler. If it didn't kill the proc, it could take out the mobo.
Tx Redneck said:
An excessive OC run for extended lengths or fully loaded(100%CPU usage) will kill it. Phones don't have the means to dissipate heat like a PC w/ a good cooler. If it didn't kill the proc, it could take out the mobo.
Click to expand...
Click to collapse
I gotcha. That makes complete sense. The freezing or rebooting I was thinking of would probably be from using settings that the phone straight-up wouldn't handle first shot, and wouldn't account for a setting that the phone would at least *start* to run, but after a prolonged period of time, generates so much heat that **** starts burning up due to the lack of ventilation.
Ouch.
Thanks tx...
Do like I do TX...keep a few different backups...
My backup folder typically looks like this...
2 different backups of Gingerbeast
1 of my straight up stock right after I rooted my phone
1 of A sense 3.0 ROM
Of course this does take up some space buy It saved my a$$ a couple times...
Sent from my Inspire 4G using XDA Premium App
You know, I actually do that but my 8gig card was gettin too full too fast. I only keep one of each because of all the photo's I take.
Tx Redneck said:
You know, I actually do that but my 8gig card was gettin too full too fast. I only keep one of each because of all the photo's I take.
Click to expand...
Click to collapse
Yeah, nandroids fill space fast. Just ordered a 32gb card.
Sent from my Inspire 4G using the power of the dark side.
Yeah Scott I had it set to 1.3ghz but the voltage was really high im assuming and eachtime I was on the phone or just playing a games,it got to 106°-110° so damn hot I couldn't handle holding it. It was the rom because after my issue,suddenly a flashable fix for voltage was released and many users experienced over heating issues after a release was made. U gotta be careful with the new guys that are creating their first roms, and ill never go back to using that rom again. I took it to.at&t and even the guy smelt the sweet burnt smell. And the over heating happened at night when I plugged it in.
Sent from my Desire HD using XDA App
mattmiller said:
Yeah Scott I had it set to 1.3ghz but the voltage was really high im assuming and eachtime I was on the phone or just playing a games,it got to 106°-110° so damn hot I couldn't handle holding it. It was the rom because after my issue,suddenly a flashable fix for voltage was released and many users experienced over heating issues after a release was made. U gotta be careful with the new guys that are creating their first roms, and ill never go back to using that rom again. I took it to.at&t and even the guy smelt the sweet burnt smell. And the over heating happened at night when I plugged it in.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Yup, I remember. I just didn't want to dis you, since it was your deal and all. Sucks it happened.
Thing is, I was about ready to flash it myself, and then that happened, and I said, nope, I ain't taking any chances... I paid off contract for this phone and still haven't got around to selling my Captivate. No way I'm gonna blow this phone up.
My sensation went off last night and wont come back on, no charging light no screen etc...
the only thing is usb does kinda pick it up as QHSUSB_DLOAD with no drivers to install, any ideas?
edit: never mind i now know this is bricked and a jtag needs doing....
Help! Same problem
I have no power to the device. Tmobile sent me a new sensation but i would like to try and fix the old one before i send it back, only have 5 more days.
Its not the battery or the sd since they both work fine in new phone.
Windows reads the same thing when on usb. No drivers. No power No nothing????
Can anyone help please or am i done for?
anarchyuk said:
My sensation went off last night and wont come back on, no charging light no screen etc...
the only thing is usb does kinda pick it up as QHSUSB_DLOAD with no drivers to install, any ideas?
edit: never mind i now know this is bricked and a jtag needs doing....
Click to expand...
Click to collapse
Could you explain what you did to cause this? I really hope you were messing with things other than what most people have done, otherwise, this could be a real problem for the rest of us.
Matt
Yes i would also like toknow what You did please
Sent from my HTC Sensation 4G using XDA Premium App
mrg02d said:
Could you explain what you did to cause this? I really hope you were messing with things other than what most people have done, otherwise, this could be a real problem for the rest of us.
Matt
Click to expand...
Click to collapse
+1
10Char
If you did brick there is a thred in the dev's that can and will show you how to unbrick and you can shop and decide on witch Rom you won't to go with look at it this way you have the best of both worlds good luck
Sent from my HTC Sensation 4G using XDA App
Had an issue today similar to yours, unlocked the bootloader today and kept the stock rom. Tonight I started deleting the bloatware, mainly using root explorer, no issues really. Used titanium backup to "force remove by exploit" I think its called. Did that and phone went black, tried powering back on, pulled battery etc, nada.
Ended up plugging device to usb charger and booted into bootloader, rebooted from there and its fine.
I ran into this tonight. See this thread:
http://forum.xda-developers.com/showthread.php?t=1198585
Short story -- Clockwork Recovery is bugged and won't charge the phone. Your battery level is too low to power on, so you need to use another method to get some power into it.
I did this:
http://dl.dropbox.com/u/15034469/tmp/recovery_fail.jpg
And yeah it's a lame problem.
Ahh, so this is not really a bricked phone, but a case of CWM dead battery! Good to know, as its an "easy" fix then. I was afraid that the phone, simply S-off and perm rooted, had somehow crashed permanently.
Matt
Straight Bricked
For me its not the battery, when tmobile sent me a new sensation i used my old battery, sdcard and sim and the battery still had around a 75% charge. I cant boot from usb i cant do anything. Its completely dead.
As for what i did?
I had been flashing multiple roms and kernels for 2 weeks. Overclocking, undervloting bla bla. No issues a wipe and flash couldnt take care of. I think i did a wipe and flash of a new rom and thats it. Dead. Wish i could remember exactly what it was. I guess im gonna mail it back since i have a new one and probably get charged full retail if they see its s-off and root.
blackstarnino said:
I had been flashing multiple roms and kernels for 2 weeks. Overclocking, undervloting bla bla. No issues a wipe and flash couldnt take care of. I think i did a wipe and flash of a new rom and thats it. Dead. Wish i could remember exactly what it was. I guess im gonna mail it back since i have a new one and probably get charged full retail if they see its s-off and root.
Click to expand...
Click to collapse
Ahh..So it wasnt the silly CWM ordeal then. That sucks!
Try to pinpoint what you were doing right before this happened. Were you wiping something? (what were you wiping) Were you flashing a ROM? (What were to flashing)
Try to provide more details, as I am sure some of the devs here will be looking to jump all over it shortly.
EDIT: Were to making sure to check that the ROM you were flashing was meant for your version of the phone as well as the files not corrupted? I know it sounds silly, but its something to rule out.
Matt
happened to me too on two batteries. I believe that it is due to overclocking the cpu. because the battery stats are calibrated for a slower CPU speed, it drains it past the failsafe point to pure failure. CWM will recognize CPU for the given ROM. i flashed back to S-ON and regular RUU 1.29 and charging my batteries again for the correct CPU + battery stats. wish me best of luck
Wow, am i that stupid
Not positive but i think i figured out what i did. Something really stupid.
I think i flashed: [Desire] InsertCoin CM7/STOCK 1.1.0
So am i fully bricked?
Gotta put the phone in the mail tomorrow.
Do you think they will see that its s-off or if its (truly) bricked can they not?
Nino
blackstarnino said:
Not positive but i think i figured out what i did. Something really stupid.
I think i flashed: [Desire] InsertCoin CM7/STOCK 1.1.0
So am i fully bricked?
Gotta put the phone in the mail tomorrow.
Do you think they will see that its s-off or if its (truly) bricked can they not?
Nino
Click to expand...
Click to collapse
They'll know....
actually... having worked in a few cell phone repair / refurbish facilities... i can tell you that they won't even look. they just plug the phone up to their bench and it overides everything and does a fresh flash. from there they just replace plastics to make it look like a brand new phone. if they are unable to flash it at the bench, they replace internals. so relax... no one will know or care what you did to it. these places get thousands of phones a day. and each tech at the bench has a quota to get through.
Thanks for your feedback guys. Shipping it off now...
Still cant believe it. Still have my n1 from launch day and it took everything i could throw at it. Still kicking like a beast. **** my g1 is still running cm4 i think lol.
anarchyuk said:
My sensation went off last night and wont come back on, no charging light no screen etc...
the only thing is usb does kinda pick it up as QHSUSB_DLOAD with no drivers to install, any ideas?
edit: never mind i now know this is bricked and a jtag needs doing....
Click to expand...
Click to collapse
I'm in the same situation. This sucks. I tried to get back S-ON. Did you receive a new phone?
So you flashed a desire ROM.... Well no ****...
Sent from my Transformer TF101 using xda premium
My phone fell in a puddle last night. Everything seemed to be working fine until this morning it got stuck in boot loop. I opened up the hboot menu.
s-on rl
HBOOT-1.44.0007
eMMC-boot
jun 27 2011
The phone was never rooted it's 100% factory. I have no idea what to do. I did search but none of the answers were on point.
Thank you in advance!
Is there an option under the hboot menu to restore the phone to factory defaults?
If so, this would wipe out everything on your phone, but it may start booting again.
Having subjected the hardware to an unfortunate water incident puts the hardware into an unpredictable and unknowable state. The best we can do is guess at this point. T-Mobile is unlikely to RMA it, sadly, as they have water detector stickers on the phone.
It sucks being in this predicament, I know. I wish you the best of luck!
Take the battery out and put everything in a Noel of rice for at leather 48 hours to completely dry the phone. The worst thing you can do is turn on a phone once it has gotten wet. Dry it before trying anything else, this is very important!
Sent from my Bulletproof_Doubleshot using XDA App
Kanerix said:
Is there an option under the hboot menu to restore the phone to factory defaults?
If so, this would wipe out everything on your phone, but it may start booting again.
Having subjected the hardware to an unfortunate water incident puts the hardware into an unpredictable and unknowable state. The best we can do is guess at this point. T-Mobile is unlikely to RMA it, sadly, as they have water detector stickers on the phone.
It sucks being in this predicament, I know. I wish you the best of luck!
Click to expand...
Click to collapse
I see what your saying I tried that but it still wouldn't start up. Also the water damage stickers didn't get touched.
But thank you for your opinion!
Kanerix said:
Is there an option under the hboot menu to restore the phone to factory defaults?
If so, this would wipe out everything on your phone, but it may start booting again.
Having subjected the hardware to an unfortunate water incident puts the hardware into an unpredictable and unknowable state. The best we can do is guess at this point. T-Mobile is unlikely to RMA it, sadly, as they have water detector stickers on the phone.
It sucks being in this predicament, I know. I wish you the best of luck!
Click to expand...
Click to collapse
yellowjacket1981 said:
Take the battery out and put everything in a Noel of rice for at leather 48 hours to completely dry the phone. The worst thing you can do is turn on a phone once it has gotten wet. Dry it before trying anything else, this is very important!
Sent from my Bulletproof_Doubleshot using XDA App
Click to expand...
Click to collapse
That's exactly what I'm doing right now. Just sucks being phoneless haha
Thank you for your intput
wow, I didn't notice how many typos there was in my post! They are pretty funny. Damn you auto correct!
yellowjacket1981 said:
wow, I didn't notice how many typos there was in my post! They are pretty funny. Damn you auto correct!
Click to expand...
Click to collapse
Don't stress it! It was very helpful!
i would do the rice for sure. i stepped in the shower with my G2 in the pocket of my bathing suit..... the phone was wonky at first, then i kept it in dry white rice for a day or two, as long as i could, and eventually everything came back fully functional. i thought the vibrator was dead for good, but even that came back after a week or so!
yogi2010 said:
i would do the rice for sure. i stepped in the shower with my G2 in the pocket of my bathing suit..... the phone was wonky at first, then i kept it in dry white rice for a day or two, as long as i could, and eventually everything came back fully functional. i thought the vibrator was dead for good, but even that came back after a week or so!
Click to expand...
Click to collapse
I'm currently doing that, praying to god I get some of that luck. In the mean while look for a new phone maybe a galaxys2 or an htc amaze
goldenwireless said:
I'm currently doing that, praying to god I get some of that luck. In the mean while look for a new phone maybe a galaxys2 or an htc amaze
Click to expand...
Click to collapse
yeah cool, i hope it comes back to life for you. and we can help you restore the stock firmware if you want to try it as a last-ditch effort. it would seem more of a hardware thing, but i'd say it'd be worth a try.
yogi2010 said:
yeah cool, i hope it comes back to life for you. and we can help you restore the stock firmware if you want to try it as a last-ditch effort. it would seem more of a hardware thing, but i'd say it'd be worth a try.
Click to expand...
Click to collapse
Actually that's what I'm planning to do. I would like to do it as soon as I possible actually. The phone has been soaking in rice for about a day and half I think it's dry enough, I think it just needs the stock file for the bootloader. I also wouldn't know how to load it up from there.
goldenwireless said:
Actually that's what I'm planning to do. I would like to do it as soon as I possible actually. The phone has been soaking in rice for about a day and half I think it's dry enough, I think it just needs the stock file for the bootloader. I also wouldn't know how to load it up from there.
Click to expand...
Click to collapse
ah ok, did you try booting it up, is it still bootlooping?
also, might you wanna try and get S-OFF first? it would give you more freedom, and if you flash one of the factory ROM files with S-ON, you might get to where S-OFF wouldn't be possible anymore, with what we know at this moment.
or if you don't care about S-OFF, you could check this out and download the 1.55.531.3 ROM file... and follow the directions for flashing it.....
http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24
yogi2010 said:
ah ok, did you try booting it up, is it still bootlooping?
also, might you wanna try and get S-OFF first? it would give you more freedom, and if you flash one of the factory ROM files with S-ON, you might get to where S-OFF wouldn't be possible anymore, with what we know at this moment.
or if you don't care about S-OFF, you could check this out and download the 1.55.531.3 ROM file... and follow the directions for flashing it.....
http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24
Click to expand...
Click to collapse
Even with S-On there's always flashing the boot.img file to the phone via Fastboot.
Posted from Spaceball One
blackknightavalon said:
Even with S-On there's always flashing the boot.img file to the phone via Fastboot.
Posted from Spaceball One
Click to expand...
Click to collapse
And how would I do that? I'm new at this.
actually I think I got it started it updating. I pray to god this works.
goldenwireless said:
So now how would I achieve S-off while the phone is boot looping?
Click to expand...
Click to collapse
Well yeah, it may or not work, depending on the state your device is in..... but could be worth a try?
Basically, go to Revolutionary.io, download the program, and run it while your phone is trying to boot up.
If it doesn't work, I think you'll have to try and flash a higher stock ROM version thru the bootloader.
Also it could be worth noting, there was guy around who said he knew the fix for water-damaged phones.... it had something to do with opening it up and scraping off some corrosion somewhere...? Not sure if this would apply to you or not. And in any case, it can't hurt trying to restore the device software-wise.
boot into recovery and run it
I followed the instruction for the this link that yogi2010 provided me and the phone did update but still no progress, the phone is still under boot loop even after it updated.
goldenwireless said:
I followed the instruction for the this link that yogi2010 provided me and the phone did update but still no progress, the phone is still under boot loop even after it updated.
Click to expand...
Click to collapse
Unfortunately, it sounds like the hardware is dead.
Kanerix said:
Unfortunately, it sounds like the hardware is dead.
Click to expand...
Click to collapse
Guess I'll wait for the HTC One S haha
I finally managed to do it. I officially bricked my Infuse. No clue how I did it but it's finally borked for good. Cant access download mode when I try nothing happens. Used 4 different computers, 5 different cords and approx 23 different USB slots. 3 different batteries(just incase it was a bad battery) Nothing haha. Infuse is completely dead!.... My backup infuse is pretty messed up as well (screen is cracked all to hell) This happened after I Heimdall'd my phone phone to clean the slate. It booted up, then bootlopped once then just didnt turn on again.
i would try letting it sit with the battery out overnight then giving it a shot again, also try differnt tools like gtg unbrick
also try using a usb jig
(i once messed mine up badly enough that when you put in in download mode it was a black screen with red green and blue dots on it, using gtg unbrick fixed it for me !
fingers crossed that itll come back to life for ya.
if you didnt open it, crack the screen, or drop it in water, att will replace it under warranty. give em a call tomorrow at 18008011101. have your iemi ready.
The Jack of Clubs said:
if you didnt open it, crack the screen, or drop it in water, att will replace it under warranty. give em a call tomorrow at 18008011101. have your iemi ready.
Click to expand...
Click to collapse
also try you could always send it in under warranty
The_Zodiac said:
i would try letting it sit with the battery out overnight then giving it a shot again, also try differnt tools like gtg unbrick
also try using a usb jig
fingers crossed that itll come back to life for ya.
Click to expand...
Click to collapse
The batteries been out for a bit now gonna leave it out and put it in tomorrow see if maybe that does something. If anything theres a couple Infuse 4G's on Craigslist for pretty cheap. And if this one doesnt end up working, I'll throw it up on there for parts, might be useful to someone.
Also I dont have an actuall plan with AT&T so thats a no go haha
The Jack of Clubs said:
if you didnt open it, crack the screen, or drop it in water, att will replace it under warranty. give em a call tomorrow at 18008011101. have your iemi ready.
Click to expand...
Click to collapse
Yeah, after paying a $200 deductable. That's how much it would have been to replace my stolen infuse even under warranty.
Try a pizza taco sometime, if you don't know what it is, look it up then
Dont give up hope... if you didnt flash any bootloaders i dont think its bricked
this looks almost like what happened to me last night..
Odined to stock only to find phone booting up to nothing just a black
screen... i thought i was done for good but i kept trying and one of the times
odin managed to see the device...
even with a completaly black screen it still booted up to "download mode"
even tho i couldnt see that particular screen
i ran odin and it booted up fine
keep trying buddy dont lose hope
jayRokk said:
Dont give up hope... if you didnt flash any bootloaders i dont think its bricked
this looks almost like what happened to me last night..
Odined to stock only to find phone booting up to nothing just a black
screen... i thought i was done for good but i kept trying and one of the times
odin managed to see the device...
even with a completaly black screen it still booted up to "download mode"
even tho i couldnt see that particular screen
i ran odin and it booted up fine
keep trying buddy dont lose hope
Click to expand...
Click to collapse
Hehe I wont give up just yet. Honestly I think it's something wrong in the Hardware of the phone. I'm gonna take it apart later and have a look see. Might be able to replace the problem with a part from my old Infuse
MaliciousIntent69 said:
Hehe I wont give up just yet. Honestly I think it's something wrong in the Hardware of the phone. I'm gonna take it apart later and have a look see. Might be able to replace the problem with a part from my old Infuse
Click to expand...
Click to collapse
if it is that might as well take the whole motherboard and switch it out right??
if you know how to do all that of course
but good luck to you and hopefully its nothing major
warranty is different than insurance. even if you buy it off contract or from someone else, you should still have the warranty. they provide 1 year for all branded phones. its only been on sale for 11 months so everyone should be under warranty.
jayRokk said:
if it is that might as well take the whole motherboard and switch it out right??
if you know how to do all that of course
but good luck to you and hopefully its nothing major
Click to expand...
Click to collapse
Yeah thats pretty much what I was gonna do if there is something wrong with this ones motherboard xD Plus I wouldn't mind the camera off my old one cause on this one the lens is scratched
MaliciousIntent69 said:
Yeah thats pretty much what I was gonna do if there is something wrong with this ones motherboard xD Plus I wouldn't mind the camera off my old one cause on this one the lens is scratched
Click to expand...
Click to collapse
Nice!!
Win win situation!!
Got impatient so I switched out motherboards.... haha. got it up and running now. Weird as hell though I don't see how Using Heimdall would damage my motherboard? I highly doubt it was heimdall. but... who knows
But now I finally have a camera that doesn't take ****ty pics haha
MaliciousIntent69 said:
Got impatient so I switched out motherboards.... haha. got it up and running now. Weird as hell though I don't see how Using Heimdall would damage my motherboard? I highly doubt it was heimdall. but... who knows
Click to expand...
Click to collapse
glad its up and running
jayRokk said:
glad its up and running
Click to expand...
Click to collapse
Mee too now time to test the new build of ICS that jt released Working camera equalls DD for me
MaliciousIntent69 said:
Mee too now time to test the new build of ICS that jt released Working camera equalls DD for me
Click to expand...
Click to collapse
its running great!! Switched from Trebuchet Launcher to Nova (found in Google Play) and its buttery smooth
camera works flawlessly..
front facing camera is zoomed in for some reason but i dont really use it so
who cares lol
but i think for a DD is good
at least for me haha
If your cracked screen infuse still works then I would just swap out the internals. Should be easy enough. I did it to my wife's phone.. screen cracked and we had an identical backup phone that my daughter played with. Swapped out the boards and all was well.
Sent from my SGH-I997 using XDA
I thought I did something similar but then tried a different method of reverting back to stock & it worked.
It wasn't going into download mode either and the screen was all pixilated but it worked. Maybe try a different method of reverting back to stock (gtg unbrick)
Sent from my SAMSUNG-SGH-I997 using Tapatalk
The Jack of Clubs said:
warranty is different than insurance. even if you buy it off contract or from someone else, you should still have the warranty. they provide 1 year for all branded phones. its only been on sale for 11 months so everyone should be under warranty.
Click to expand...
Click to collapse
Yup..what jack said. Someone else went that route too
Sent from my phone.