Related
I just called Verizon and told them after updating I have been getting random reboots. The tech said its happening to certain phones and is sending a replacement, no questions asked. Im sure my phones not defective I agree with those that say its a radio issue. I even mentioned that to the tech and he said he doesn't think so. Kinda sucks I got to restore to stock, and reroot and what not. I'll be sure to let everyone know if the replacement has the same issues.
Update: Just so you know I've gotten two replacements, and it didn't help my situation. So no point in getting one unless you got a little cosmetic issue with your phone. Htc is working on a fix for these pesky reboots. It's in testing stages right now supposedly.
Sent from my Thunderbolt
It may be a pain to return to stock & root the new phone, but at least verizon is swapping your phone for free. It wouldn't surprise me if they didn't try to blame it on the owner & charge for the exchange
Yeah the tech was real cool about it. Free overnight fed ex and everything.
Do you have to send your current phone back to them, then, or what?
Interesting that they're doing this. I thought this was happening on all TBs, not just individual ones. Maybe I should call. Anybody else had this experience with the techs? Or did ajd88 just happen to catch a tech that had already put in his 2 weeks notice and didn't care.
I called this morning. Having a new one next-day shipped to me. My phone has become unusable.
My phone has rebooted maybe 3 times total since I installed the leaked radio when it first was leaked, you guys think I should try and get a replacement just to be on the safe side?
Sent from my ADR6400L using XDA App
While my phone isn't randonly rebooting it does loose 4G all the time, rarely goes into 3G and 1x seems to be the norm. I live in Chicago so I know it has a solid 4G signal. Wonder if it's worth the trouble of swapping out. But knowing my luck they will give me a refurbished phone...
sublimaze said:
It may be a pain to return to stock & root the new phone, but at least verizon is swapping your phone for free. It wouldn't surprise me if they didn't try to blame it on the owner & charge for the exchange
Click to expand...
Click to collapse
in my experience, verizon has always been really good at replacing phones. I had a droid since launch day before upgrading to my TB, and it had been replaced 2 times.
The first time the camera stopped focusing, the second time it just stopped turning on.
I walked in to a VZW store on a Wednesday, and I had fedex at my door delivering new phone on thursday afternoon. badass!
You know he funny thigh here is. It probably is happening on all thunderbolts or some people just arent ppaying attention and not realizing that this is happening. It even happens on my wife's fascinate. So ineradicable of sending back my non defective phone that random rebooted once in a while for a "refurbished" phone. Ill keep my new out of box one. Not one someone else has allready had. Just because of a software issue.
Well it seems like I get the short end of the stick with VZW on a daily basis. I called and explained it all to the rep and explained how this is a known issue and that there are plently of reputable community sites (like XDA) confirming this and there is rarely a common thread between two devices. Apparently, the rep I spoke to, said that this isn't a known issue.
Got told to factory reset and if it comes down to an exchange, I'd be getting a "certified like-new device" a.k.a. crappy refurb. Again, IF it comes down to that. Awesome. Now they want me to wait it out and see if it keeps acting up. Fun.
I asked the tech if i was gonna get a refurb, he said no. He better not be lying.
Of course theres a gb leak right after, probably with a new radio that fixes it lol.
ajd88 said:
I asked the tech if i was gonna get a refurb, he said no. He better not be lying.
Click to expand...
Click to collapse
You'll most likely get a "Certified Like-New" It's a refurb. But, a refurb with a working power button is better than what I have now so I'm going to give this a go.
ProTekk said:
Well it seems like I get the short end of the stick with VZW on a daily basis. I called and explained it all to the rep and explained how this is a known issue and that there are plently of reputable community sites (like XDA) confirming this and there is rarely a common thread between two devices. Apparently, the rep I spoke to, said that this isn't a known issue.
Got told to factory reset and if it comes down to an exchange, I'd be getting a "certified like-new device" a.k.a. crappy refurb. Again, IF it comes down to that. Awesome. Now they want me to wait it out and see if it keeps acting up. Fun.
Click to expand...
Click to collapse
I just got the same response. Tech support said not a known issue. They want me to see if I can make it happen again. I guess random reboot isn't telling. I know they have to go through their troubleshooting process and I'm not upset about that, but i can see where this is going. I won't get another reboot today which will tell them I don't have a problem. Alright, I'm off the soapbox.
Sent from my ADR6400L using XDA Premium App
ERIFNOMI said:
You'll most likely get a "Certified Like-New" It's a refurb. But, a refurb with a working power button is better than what I have now so I'm going to give this a go.
Click to expand...
Click to collapse
Yeah my power button is F'ed too. Whatever if they send me a phone thats in worse shape then the one i got ill just send it back rather than my old one.
Busphan said:
I just got the same response. Tech support said not a known issue. They want me to see if I can make it happen again. I guess random reboot isn't telling. I know they have to go through their troubleshooting process and I'm not upset about that, but i can see where this is going. I won't get another reboot today which will tell them I don't have a problem. Alright, I'm off the soapbox.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
The guy i spoke to asked if I did a factory restore, I lied told him yes. So there was no troubleshooting. I told him its all over google, he put me on hold came back and said he looked on google and confirmed with me he sees that some people are having problems. After that he told me he was confident a new device would solve my problems and thats it. I guess i might have just got lucky.
It is possible that physical defects in the phones are contributing to the issue. Something like a bad run of filter components could cause the radio to operate ever so slightly out of spec, but still within QA tolerances. Then, if they then tweaked the radio parameters a bunch in the update, it could have pushed the performance requirements of the RF hardware closer to the device tolerances - suddenly revealing a whole bunch of bad components they did not see previously.
I got my new phone today and no reboots and my screen is a lot nicer and brighter. I'm happy
Sent from my ADR6400L using XDA Premium App
Can someone explain the nature of the reboots that they are experiencing? I had a reboot on Friday but it was much more then just a reboot, after the phone was finishing powering back up I had no ability to call out as if there was no service. I tried numerous battery pulls and even had Verizon do a reset on there end, nothing helped yet I was still able to receive and send data. Finally after about an hour my service was back. Then the same thing happened again yesterday, I went through the same processes with no success yet. I have tried all the different radio choices and nothing is working, does anyone have any suggestions?
Thanks!!!
Also I am rooted and using the stock rom
Couple different things I'd like to point out. Most vzw employees at the sales level will replace your phone if they actually see it reboot on its own. Some, though, chalk it up to being just a part of the device. I, myself, am a vzw employee and would most definitely exchange your device if its rebooting. However, rooting your phone voids the manufacturers warranty, so you better have insurance. Also, certified like news are not refurbished phones. They are phones that are brought back within the 14-day return policy because the customer either didn't like it or didn't understand how to use it. They're cleared out, tested, and repackaged as CLNRs. Certified pre-owned are, in fact, refurbished. Just thought I'd clear that up.
Sent from my HTC RootedBolt running CM-7.0.
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 almost did not notice it and was going to flash CMW, and restore a nandroid - lol.
I am going to mess with it a bit and then flash recovery.and do a nandroid of it.
As I understand it, I can then flash a rooted nandroid over it and I will have root, as one-click root would not work (yet).
UPDATE: Had a bad moment with it - could not get into nvflash mode by holding vol up/down. it took the 4th USB port on second computer to get it recognized. Flashed CMW, flashed the rooted 2.3.3 OTA - have got root.
Now only need morfic and/or faux to release a kernel for it. However, probably will be back on EB and CM7 soon in any case.
Did you get the replacement from T-Mobile or LG?
andrewNY said:
Did you get the replacement from T-Mobile or LG?
Click to expand...
Click to collapse
TMo of course.
LG had earlier only offered a refurb only if after an inspection from GOD, they decided to authorize it.
If you got a replacement phone without a battery and rear cover then its going to be a refurb like the one I got from Tmobile. When you hook up your phone to the LG Mobile Update program your phone will be a DWP not DW. Seems they are recycling phones sent back to them. I was offered a third phone, but I refused.
grenademasta said:
If you got a replacement phone without a battery and rear cover then its going to be a refurb like the one I got from Tmobile. When you hook up your phone to the LG Mobile Update program your phone will be a DWP not DW. Seems they are recycling phones sent back to them. I was offered a third phone, but I refused.
Click to expand...
Click to collapse
The model number in the battery case says DW, so other then going to the LG Update (which bricked my previous pone) how else can it be determined?
Mine also said DW on the phone until I connected it to the LG Mobile Update. That's where I found out it was actually refurbished DWP. I don't know any other way to verify it is a refurb other than that method. Also, when I called Tmobile yesterday regarding my current issues, they acknowledged to me that they send out refurbs replacements only. The tech support employee I spoke with said "most of them are found to have nothing wrong with them when we check the phones people send us". LOL! I told her you are just playing musical chairs with the phones sent to you.
keeping my current problems suddenly seems a whole lot better...
grenademasta said:
If you got a replacement phone without a battery and rear cover then its going to be a refurb like the one I got from Tmobile. When you hook up your phone to the LG Mobile Update program your phone will be a DWP not DW. Seems they are recycling phones sent back to them. I was offered a third phone, but I refused.
Click to expand...
Click to collapse
I hooked it up and it shows DW after I connect. Possibly they sent a new one with the update, as updating with LG tool had caused the replacement?
anyone counting on the lgupdate tool to give reliable information is misled. i got mine on day one. phone says dw. lgtool says dwp. i'm not sure who started all this dw/dwp stuff, but i really don't think it means a thing. dwp might just simply be second batch. who confirmed these to be refurbs,or newer/better units?
And for the record, connecting your phone to the LG tool just to have it read the model number will result in a 0% probability of bricking your phone. Unless you hit it with a brick while it's reading.
So there's nothing to be afraid of, and takes only like 15 seconds to find out, which is less than the time it takes to post here.
And furthermore...refurb or NOT, my replacement model (which LG tool reads as DWP, but has DW printed under batter cover and under battery) is MUCH better than my first G2x. It has almost no screenbleed, no screen separation, far less random reboots, better battery life, and gps lock is within 5 seconds now. So if it is, indeed, a refurbished model, they must have refurbed it pretty darn well. If this matters, my original phone SN started with 104, and this replacement starts with 106...seems most likely manufactured more recently than the earlier phone.
mmapcpro said:
Unless you hit it with a brick while it's reading.
Click to expand...
Click to collapse
Haha that made me laugh!
Sent from my HD2 using XDA app
SuperOneClick Fail!
I just received mine a couple hours ago. I hopped on the free G2X offer of last week. SuperOneClick fails to root. I was mortified I'd bricked this new phone; but, after killing SuperOneClick (stuck on Step 6 as apparently happens to all), the device seems fine. Charging the battery overnight and then I may try your method of NVflash. Coming from OG Droid.
I received a replacement from T-Mobile last week, it came up as DW under LG Updater tool. T-Mobile doesn't always send out refurbs.
mondieu1724 said:
I just received mine a couple hours ago. I hopped on the free G2X offer of last week. SuperOneClick fails to root. I was mortified I'd bricked this new phone; but, after killing SuperOneClick (stuck on Step 6 as apparently happens to all), the device seems fine. Charging the battery overnight and then I may try your method of NVflash. Coming from OG Droid.
Click to expand...
Click to collapse
Flash the rooted ROM over it and you have root. Worked for me.
Sent from my LG-P999 using XDA Premium App
gaww said:
Flash the rooted ROM over it and you have root. Worked for me.
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
Which rooted ROM? xboarder's? I just read that entire 35 page thread and some seem to be getting reboots reintroduced. Since mine is currently having no problems whatsoever. I may try to NVflash and then try the brute force approach delineated here:
http://forum.xda-developers.com/showthread.php?p=16015317#post16015317
But, I need to read up on it more.
For now, I just want to Nandroid this installation so I can always go back to it. I think the NVflash will give me that option, right?
mondieu1724 said:
Which rooted ROM? xboarder's? I just read that entire 35 page thread and some seem to be getting reboots reintroduced. Since mine is currently having no problems whatsoever. I may try to NVflash and then try the brute force approach delineated here:
http://forum.xda-developers.com/showthread.php?p=16015317#post16015317
But, I need to read up on it more.
For now, I just want to Nandroid this installation so I can always go back to it. I think the NVflash will give me that option, right?
Click to expand...
Click to collapse
I loaded a rooted 2.3.3 stock OTA from a thread in the development section. Since it is stock, you can decide what you keep and whet you freeze or delete. After flashing over the 2.3.3 on the device - root was back.
I just got a warranty replacement in and it was 2.2.2 with the march baseband! Unsure if refurbed or not.
Lightning Blue said:
I just got a warranty replacement in and it was 2.2.2 with the march baseband! Unsure if refurbed or not.
Click to expand...
Click to collapse
Call TMo and tell them others are getting them with 2.3.3 and July baseband. and you want the same. Especially if you bricked you last one with the LG Updater, you should not have to go down that path again if you can simply get a replacement with it on already.
In any case - insist on a replacement with the latest ROM and baseband on it. I have noted a very significant GPS connection time improvement even with CM7 ROM's (they had been like watching grass grow when waiting on the GPS).
I got my replacement yesterday after bricking it trying to update....its my third phone and it came with 2.3.3. This phone feels perfect and I have yet to have and reboots or freezes. I could care less if its a refurb since it looks brand new. No need to root since nv flash works fine....just restored a nandroid I had from my previous phone. Cm7 rocks and cwm is a life saver
Sent from my LG-P999 using XDA App
gaww said:
Call TMo and tell them others are getting them with 2.3.3 and July baseband. and you want the same. Especially if you bricked you last one with the LG Updater, you should not have to go down that path again if you can simply get a replacement with it on already.
In any case - insist on a replacement with the latest ROM and baseband on it. I have noted a very significant GPS connection time improvement even with CM7 ROM's (they had been like watching grass grow when waiting on the GPS).
Click to expand...
Click to collapse
I managed to update it, it almost bricked but after trying various methods people offered on here plus digging out an XP machine I haven't touched in two years, got it working again!
Hey guys
I gave my cousin my infuse 4g, which was running gtg's Infused latest ROM.
According to her, she was at the mall and she pulled out the phone from her pocket and all she saw was infinite logo bootloop.
At first to me it seemed like a soft brick but it's not recoverable.
When I put the battery in, it goes into infinite samsung logo bootloop.
Three button combo to CWM doesn't work, the download mode jig also does not work.
when i put the download jig in, the yellow downloading mode logo shows up for 2 seconds and then the phone turns off. and the process repeats.
When i put the charging cable in, it infinitely loops the "battery picture", turning off 1 second later everytime and turning back on...
I plan on taking it back to the AT&T Service Shop for a chance at claiming a replacement device.
So here's my question.
I've tried everything I can to get this thing back to a working state, but to no avail.
Does this mean that the engineers at the service center will also not be able to get it back up (meaning that they won't be able to tell that i've voided the warranty)?
I mean, something is seriously wrong with this infuse. it won't even go to download mode.
I bought this device back in July 2011, so I'm still under that 1 year manufacturer's warranty.
Do you guys think I will be able to get a replacement device?
Thanks guys!
EDIT: here are the visual descriptions of what i'm talking about.
http://www.youtube.com/watch?v=bYiZbgI3rnk&feature=channel&list=UL
http://www.youtube.com/watch?v=ZxvIj76MkjA&feature=channel&list=UL
jhong91 said:
Hey guys
I gave my cousin my infuse 4g, which was running gtg's Infused latest ROM.
According to her, she was at the mall and she pulled out the phone from her pocket and all she saw was infinite logo bootloop.
At first to me it seemed like a soft brick but it's not recoverable.
When I put the battery in, it goes into infinite samsung logo bootloop.
Three button combo to CWM doesn't work, the download mode jig also does not work.
when i put the download jig in, the yellow downloading mode logo shows up for 2 seconds and then the phone turns off. and the process repeats.
When i put the charging cable in, it infinitely loops the "battery picture", turning off 1 second later everytime and turning back on...
I plan on taking it back to the AT&T Service Shop for a chance at claiming a replacement device.
So here's my question.
I've tried everything I can to get this thing back to a working state, but to no avail.
Does this mean that the engineers at the service center will also not be able to get it back up (meaning that they won't be able to tell that i've voided the warranty)?
I mean, something is seriously wrong with this infuse. it won't even go to download mode.
I bought this device back in July 2011, so I'm still under that 1 year manufacturer's warranty.
Do you guys think I will be able to get a replacement device?
Thanks guys!
EDIT: here are the visual descriptions of what i'm talking about.
http://www.youtube.com/watch?v=bYiZbgI3rnk&feature=channel&list=UL
http://www.youtube.com/watch?v=ZxvIj76MkjA&feature=channel&list=UL
Click to expand...
Click to collapse
jhong91,
It is not often but several other users have reported similar hard power loops that you're describing.
If you go back through the Q/A thread, there are a few with this.
Some users have succeeded in restoring their device via jtag method - by mobiletech or something like that.
Others opted for the replacement and was successful too.
Look through the last 20-40 pages...(garen21, brazcub may have similar situation ) Others have been told that it was due to corrosion of the battery terminal or bad circuit board.
qkster said:
jhong91,
It is not often but several other users have reported similar hard power loops that you're describing.
If you go back through the Q/A thread, there are a few with this.
Some users have succeeded in restoring their device via jtag method - by mobiletech or something like that.
Others opted for the replacement and was successful too.
Look through the last 20-40 pages...(garen21, brazcub may have similar situation ) Others have been told that it was due to corrosion of the battery terminal or bad circuit board.
Click to expand...
Click to collapse
Hello,
thanks for the reply!
if the problem really is, as you may have kindly pointed out, with the circuit board or bad battery terminal, do you think it's unrecoverable even by the AT&T technicians (or mobiletechvideo's jtag service)?
Also, this is my first time dealing with warranties on smartphone.
If they happen to find out that I have voided the warranty by rooting the phone, the worst thing that could happen is not getting a replacement device right? they can't charge me or penalize me right?
Thanks in advance!
You will be OK.
I bricked mine and sent it in, they didn't even realize it was rooted and sent me a new one. Just don't mention it man. Also its better if you take it to a smaller att store, they seem to be a bit cooler then the big corporate stores
Sent from dr0id using Tapatalk 2 beta 5
eZdubzitmk4 said:
You will be OK.
I bricked mine and sent it in, they didn't even realize it was rooted and sent me a new one. Just don't mention it man. Also its better if you take it to a smaller att store, they seem to be a bit cooler then the big corporate stores
Sent from dr0id using Tapatalk 2 beta 5
Click to expand...
Click to collapse
did you go to a retail store? or an official device support center?
thanks!
A retail store
Sent from dr0id using Tapatalk 2 beta 5
eZdubzitmk4 said:
A retail store
Sent from dr0id using Tapatalk 2 beta 5
Click to expand...
Click to collapse
ok, i thought I was supposed to go to device support center..
i guess i'll go to retail first and then device support center if they should redirect me there..
anyways,
thanks man!
Yeah it all depends on the person, most are pretty cool and try to help.
But others just send you away to support
Sent from dr0id using Tapatalk 2 beta 5
Now I did search the forums and I didn't find anything thing like I have going on. First a little background. I was an iPhone user since iPhone was iPhone. I decided to try Android and was hooked. I got the SGH-i727. I have been flashing since day one. Well, here's my dilemma. I d/l'd a ROM that I thought was for the Skyrocket, but after I read more carefully and already flashed. It was for a i9000. Everything went fine during the ROM, but after a reboot my phone wont power on. No Lights, no vibration, nothing. I'm not sure if this was the dumbest thing I have done yet or if this is an easy fix. I know I should have read more carefully, but I got excited and couldn't help myself. I was running AOKP CM10 with no problems since the first ROM was out, but I got greedy. I hope some of you geniuses can help. I have taken the SIM, SD, battery out. But too no avail! Thanks guys!
If you flashed a ROM from a different phone, it's more than likely bricked. You try getting into download mode and all that already?
Apparently you didn't read enough, your phone is hard bricked you'll have to pay 50$ to get it repaired through jtag.
kishke said:
Apparently you didn't read enough, your phone is hard bricked you'll have to pay 50$ to get it repaired through jtag.
Click to expand...
Click to collapse
Look them up. Think I am going to try to return back to AT&T today and see what they say. I looked up JTAG and it's like 60 when all is said and done. I also contacted Samsung. What are the odds they will repair it. I opened a repair ticket and the guy I talked to said free repair unless it was water damaged. This sucks!
you could say you were upgrading to ICS through kies when the cabled got disconnected in the middle, may work and may not.
You might be not need jtag. Have you looked into a usb jig? You can buy them off of ebay for less then 10 bucks. If your in a hurry and have a spare micro usb cable and are good with your hands you can also make one.
http://forum.xda-developers.com/showthread.php?t=1604707
That should force DL mode then from there flash back to stock.
You are hard bricked. The thing the dude above me said doesn't work for hard bricks.
Call ATT if you have warranty and tell them your phone won't turn on this morning and you don't know what's going on.
If you don't have warranty then jtag it.
Sent from my SGH-I727
Thanks for all the help guys. I have had this awesome phone for 5 weeks, so I am passed the 30 day "trial" period ATT allots you, but I think being a customer for about 15 years may pay off. If not JTAG will work, because I think Sammy will charge me because it had been flashed, and thus warranty voided. Will let everyone know of my successes after Monday evening when I attempt the upgrading to ICS and now it's not working thing.
Going back to Apple for a few days is about to kill me.
Do you have AT&T warranty? Wait nvm, you got a 1 warranty so AT&T will replace it free of charge.
Just tell them you were upgrading to ICS thru kies and when your phone went to reboot it didn't turn on. It's been happening for some reason. People call it the UCLF6 brick bug.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
awesome! being that i am working monday and going to school in the evening, my wife needs something to tell them. so this may work. cant wait to flash again. it was becoming more than a habit
specter07 said:
Do you have AT&T warranty? Wait nvm, you got a 1 warranty so AT&T will replace it free of charge.
Just tell them you were upgrading to ICS thru kies and when your phone went to reboot it didn't turn on. It's been happening for some reason. People call it the UCLF6 brick bug.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Smittiegee19 said:
Thanks for all the help guys. I have had this awesome phone for 5 weeks, so I am passed the 30 day "trial" period ATT allots you, but I think being a customer for about 15 years may pay off. If not JTAG will work, because I think Sammy will charge me because it had been flashed, and thus warranty voided. Will let everyone know of my successes after Monday evening when I attempt the upgrading to ICS and now it's not working thing.
Going back to Apple for a few days is about to kill me.
Click to expand...
Click to collapse
I'm not sure how tough Samsung is on this. I had a custom rom on mine, running fine for a month or so. One day, I go to grab my phone off the dresser and it's so hot I can barely hold it. I powered it off, let it cool down, and went to power on and got nothing. I had a jig and tried it to no avail. Finally, I called ATT and told them what happened. They sent a new (well, refurbished) phone, and I sent mine back to ATT. I was so worried they were going to charge me since it was rooted and running a custom rom, and my wife HATES that I flash and just looks for a reason to get me to stop, but I never heard anything else about it. They said on the phone that it sounded like the processor ws fried. You could use that story too.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Ahh, got my phone back. AT&T gave me a bit of a hard time, but oh well that is what a warranty if for. Back to flashing away! Loving MindMajic's!
Smittiegee19 said:
Ahh, got my phone back. AT&T gave me a bit of a hard time, but oh well that is what a warranty if for. Back to flashing away! Loving MindMajic's!
Click to expand...
Click to collapse
Nice!