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 was running cm7 on my phone, and was throwing on the audio fix to get better speaker volume, which sent the phone into a boot loop. I tried to put my phone into hboot (power+volume-) which it does not. It tries to boot every time. I've tried probably 50+ times and same result. I'm guessing it has to deal with the poor built buttons on this phone and the volume down just does not work. My question is despite the fact I'm rooted and running cm7, am I safe to say this is a hardware issue? I just don't want to send in my phone to Verizon and get billed for the fact the phones "tampered" with.
Should verizon replace your phone after you borked it? I think you already know the answer
xebryus said:
I was running cm7 on my phone, and was throwing on the audio fix to get better speaker volume, which sent the phone into a boot loop. I tried to put my phone into hboot (power+volume-) which it does not. It tries to boot every time. I've tried probably 50+ times and same result. I'm guessing it has to deal with the poor built buttons on this phone and the volume down just does not work. My question is despite the fact I'm rooted and running cm7, am I safe to say this is a hardware issue? I just don't want to send in my phone to Verizon and get billed for the fact the phones "tampered" with.
Click to expand...
Click to collapse
long of it, no they shouldn't. will they? who knows, depends on if you tell them the truth or not.
Should they? Technically no. Will they? Sure. They would be happy to.
but he didnt break it if the loop comes from a hardware defect,all he did was get it to fail sooner than later basically what happened to others,so technically yes they should,or can anyone prove the software killed the hardware.
sent from a screamin' bamfed out tbolt
satseaker said:
but he didnt break it if the loop comes from a hardware defect,all he did was get it to fail sooner than later basically what happened to others,so technically yes they should,or can anyone prove the software killed the hardware.
sent from a screamin' bamfed out tbolt
Click to expand...
Click to collapse
Honestly, it doesn't matter if anyone can prove the software did it or not. He voided his warranty by rooting. But they likely will replace his phone, driving up the costs for future phones.
You rooted your phone. Take it for what it is...a non-warrantied phone.
Touchy
I will start off by saying I don't have a solid answer but being as it is a hardware problem they "should" fix it. Will they? Probably not. They'll take one look, see it's rooted, and tell you that you broke it by tampering with it. All bets are off as soon as the phone is rooted...unless you can unroot and take it in I think you're in trouble but since the button is broken you can't do anything with it. Good luck and let us know what you were able to get done.
I see what you guys are saying from a moral standpoint. I'm just angry cause I know for a fact my buttons are not up to par to what they're supposed to be. I don't want to fraud the companies over something that is my fault, but in this case I'm almost positive it's related to the fact this phone was not built too well. I dunno, do "authorized retailers" handle claims with faulty hardware or just official Verizon wireless stores?
This is why you should have ADB installed and working on your computer. Hook up the phone via USB, get into ADB and reboot into recovery. There are a few threads out there for ADB you should be able to find them using Google, hopefully that will be able to help you.
If you can get into the boot loader with and then you might be able to save your phone.. Maybe, not clear take your as card out and import the rhi, they might work...
Sent from my ThunderBolt using XDA App
if you can prove that the failure was not caused by rooting, then they should fix it for you under warranty. but that is hard to prove.
xebryus said:
I see what you guys are saying from a moral standpoint. I'm just angry cause I know for a fact my buttons are not up to par to what they're supposed to be. I don't want to fraud the companies over something that is my fault, but in this case I'm almost positive it's related to the fact this phone was not built too well. I dunno, do "authorized retailers" handle claims with faulty hardware or just official Verizon wireless stores?[/QUOTE
Did you try BOTH volume buttons at the same time? This got me to bootloader.
Click to expand...
Click to collapse
Just say you tried to install the last update and your phone wont boot now. They won't know the difference.
dpham00 said:
if you can prove that the failure was not caused by rooting, then they should fix it for you under warranty. but that is hard to prove.
Click to expand...
Click to collapse
Caused by rooting or not, there is NO warranty once a phone is rooted. Has nothing to do with what caused the malfunction.
ADB reboot bootloader or recovery should work though, as long as he catches it with the right timing during the loop.
Sent from my ADR6400L using XDA App
Well update on the situation. I called Verizon telling them I can't turn on my because it "freezes" when it tries to boot up every time. He told me to try a hard reset (try to go into hboot) and I told him I tried that at least 30 times and it won't. I said I think there's something wrong with my buttons because they're not very responsive and stick really easily (which they do) and he said they're overnighting a phone to me. That was yesterday, its waiting for me at home. I'm gonna send my old phone back asap.
I'm wondering, if they have a way to find out I'm rooted, will they charge me for the phone? I don't think they'll be able to though because if I can't get into hboot, how will they? I tried adb into bootloader, but as many times as I tried, no devices were found.
you're probably aright since they might just get it and toss it in the "to be refurbed" bin. It costs a lot of money to test every return. Good luck and let us know how it turns out.
xebryus said:
I'm wondering, if they have a way to find out I'm rooted, will they charge me for the phone? I don't think they'll be able to though because if I can't get into hboot, how will they? I tried adb into bootloader, but as many times as I tried, no devices were found.
Click to expand...
Click to collapse
If they do find out, they will charge you. Don't know if they will, but be prepared for the worst.
Sent from my ThunderBolt using Tapatalk
Yes, they get broken down abd only really check for water/physical damage
Sent from the Swag ThunderBolt ADR6400L with some GingerLove (Gingeritis 1.0) using XDA Premium App
Must Watch Before Any Forum Post http://goo.gl/b4IJJ
xebryus said:
Well update on the situation. I called Verizon telling them I can't turn on my because it "freezes" when it tries to boot up every time. He told me to try a hard reset (try to go into hboot) and I told him I tried that at least 30 times and it won't. I said I think there's something wrong with my buttons because they're not very responsive and stick really easily (which they do) and he said they're overnighting a phone to me. That was yesterday, its waiting for me at home. I'm gonna send my old phone back asap.
I'm wondering, if they have a way to find out I'm rooted, will they charge me for the phone? I don't think they'll be able to though because if I can't get into hboot, how will they? I tried adb into bootloader, but as many times as I tried, no devices were found.
Click to expand...
Click to collapse
Congrats on getting a new phone I guess.
I have noticed Verizon has been VERY accomodating with these phones. One call is all that's needed to get a new phone. Im guess they're so generous because they devices have been so finnicky so far and they just want to keep people pleased for now.
I envision them cracking down hard sooner or later though. They're not stupid. They've already come down on tethering and such, so it probably wont be long until they get hardcore on replacements.
My son works for VZ...
and he takes your calls... and this is what he told me. Anything covered under insurance (Asurion), they really don't check/don't care about rooting. VZ, on the other hand, will look pretty extensively if it's covered under the warranty. They will look for rooting or anything else that would break warranty coverage.
So my wife is out of town and i just got a frantic call from her on her moms phone telling me that her Inspire is constantly been shutting down.
We live in Texas and she's visiting family in Ft. Lauderdale since before Christmas. She's said since she's been there that the phone has been acting wonky, but starting today the phone will not stay powered on when not on the charger.
When it's on the charger she says she has 80% battery life, but when she unplugs it and tries to do something with it the phone powers down.
She's done the battery pulls, she's cleared the cache and removed unnecessary apps. I'm really not sure what to tell her other than go to AT&T and get a different battery, and fi that does't work - plug it into your laptop, copy all of your pictures and necessary data then do a factory reset.
Any other advice from more experienced members?
Sounds like your on the right track. You could try downloading the ruu from HTC as well and do a clean install. If all else fails just do a warranty.
I had the same problem. It was the battery, bought a new stock HTC battery and it works perfectly don't try a reset or any of that. You will lose you're stuff, tell her to just charge it until she can get it replaced I kept mine on charger for 4 days until I bought it and got it in the mail. Phone works perfectly now
Sent from my Inspire 4G using xda premium
We had to get the screen replaced so AT&T wouldn't help her because hey could tell it's been opened
It was opened about 4 months ago, and has been working fine until she went to Florida. She has had battery issues though since she go the device back in February.
She said the AT&T person tried to do a factory reset and that "it wouldnt take" which i found was odd. More than likely the AT&T person was doing it while the phone was on, rather than doing the volume down + power button to load into recovery and do it that way.
Anyone know why a factory reset wouldn't go through?
Selecting it through the phone just boots into hboot to finish the process, but if the phone is freezing and powering down it would probably keep it from completing. Try it through hboot. Did the att guy at least test a different battery in the device? Some of those att employees really shouldn't be helping people troubleshoot. Too bad they aren't all as educated as zel.
Gizmoe said:
Selecting it through the phone just boots into hboot to finish the process, but if the phone is freezing and powering down it would probably keep it from completing. Try it through hboot. Did the att guy at least test a different battery in the device? Some of those att employees really shouldn't be helping people troubleshoot. Too bad they aren't all as educated as zel.
Click to expand...
Click to collapse
They didnt even entertain the idea of a different battery. They took the battery door off and could tell that it had been opened. Right then and there they basically sent we can't help you because it's out of warranty and HTC will charge you full price for a new phone, but then whispered to her that she could go to a local shop.
Needless to say i was a little pissed that they wouldn't even let her try a different battery.
MikeIsCore said:
They didnt even entertain the idea of a different battery. They took the battery door off and could tell that it had been opened. Right then and there they basically sent we can't help you because it's out of warranty and HTC will charge you full price for a new phone, but then whispered to her that she could go to a local shop.
Needless to say i was a little pissed that they wouldn't even let her try a different battery.
Click to expand...
Click to collapse
That is one of the risks of Modding your phone or someone else's. All support now relies on the phones owner.
As for the rep. He couldn't do anything without possibly losing his/her job. I used to work for them so I really can't blame the employee.
Now for her prob the only thing I would suggest is that she get another battery which may or may not be the issue.
Why was it opened? If you don't mind me asking?
zelendel said:
That is one of the risks of Modding your phone or someone else's. All support now relies on the phones owner.
As for the rep. He couldn't do anything without possibly losing his/her job. I used to work for them so I really can't blame the employee.
Now for her prob the only thing I would suggest is that she get another battery which may or may not be the issue.
Why was it opened? If you don't mind me asking?
Click to expand...
Click to collapse
The screen was replaced.
zelendel said:
That is one of the risks of Modding your phone or someone else's. All support now relies on the phones owner.
As for the rep. He couldn't do anything without possibly losing his/her job. I used to work for them so I really can't blame the employee.
Now for her prob the only thing I would suggest is that she get another battery which may or may not be the issue.
Why was it opened? If you don't mind me asking?
Click to expand...
Click to collapse
Tx Redneck is correct. As I stated the screen had to be replaced.
I understand about the rep not being able to do anything because of potential job loss, but does that mean they can't even let her borrow a battery to test it?
MikeIsCore said:
Tx Redneck is correct. As I stated the screen had to be replaced.
I understand about the rep not being able to do anything because of potential job loss, but does that mean they can't even let her borrow a battery to test it?
Click to expand...
Click to collapse
By the rules as much as I hate to say it. Yes. If they see that the phone was modded they cant even allow the use of another battery for testing. I normally kept a few extra personal batteries to help people out but had to do it off the clock. ATT is very strict about it.
I was written up once when I was helping someone with an issue and my boss looked over my shoulder and noticed the sticker was missing. HE asked me if I noticed and I said yes i did but it had nothing to do with what I was helping with. He took the phone, handed it back to the owner, said sorry there is nothing we can do for you. Then sent me home and when I came back in I was written up with a final warning.
zelendel said:
By the rules as much as I hate to say it. Yes. If they see that the phone was modded they cant even allow the use of another battery for testing. I normally kept a few extra personal batteries to help people out but had to do it off the clock. ATT is very strict about it.
I was written up once when I was helping someone with an issue and my boss looked over my shoulder and noticed the sticker was missing. HE asked me if I noticed and I said yes i did but it had nothing to do with what I was helping with. He took the phone, handed it back to the owner, said sorry there is nothing we can do for you. Then sent me home and when I came back in I was written up with a final warning.
Click to expand...
Click to collapse
Well that sucks. Appreciate the information though. Thanks Zelendel.
MikeIsCore said:
Well that sucks. Appreciate the information though. Thanks Zelendel.
Click to expand...
Click to collapse
Yeah it does. No prob.
Once she's returned from her trip i'll come back and post whether or not i was able to fix the issue or if we need to procure a new phone.
First one was hacked almost immediately. Ended up perma-roaming with an IMEI of 0.
They replaced that with a new one. Of course they wanted to re-up my contract and steal my unlimited data. I looked the guy dead in the eye and said "No, that's unacceptable." He said "but unlimited data isn't in the system." I said "There's no 'system' to it. I take my old SIM, put in in a new phone, and walk out." Then he wanted to tell me that wouldn't work, until I grabbed my old phone, SIM, and threw it in the new phone. Then the manager walked up and said I could go.
That phone lasted until yesterday. Capacitive touchscreen starts acting up. Reboot, nothing. Turn it off for a while (CM10 was running hot), and it started working for just a couple of minutes. Restored to stock and it stopped working all together.
Took that to the store, and they were nice once they figured out that this one didn't come from online, but another store. Then they realized it was out of 14 days so it had to be a refurb. Wanted to ship it with free 5 day, but I paid $15 for it to get here by 10am this morning. Not a bad deal, over all.
Refurb arrives this morning, pull the SIM, battery, etc from the old one, and boot it up. Capacitive layer works properly, so that's good. Skip all the My Verizon and Google stuff, because I want to get everything tested. Open a few apps, good. Press physical home button....
NOTHING. Press it again. Nothing. Third time (really pressing hard this time), it pauses for a few seconds then slowly crawls back to the homescreen.
Freaking refurb. I call up verizon and they were super nice. Explained this was my 3rd phone, and they are overnighting another GS3 for free. Let's hope this lasts a little longer.
Edit: just realized this was my first actual post! I've been a member here since I got my first smart phone: an HTC Touch with WM 6!
I'll bet those VZW reps are loving to see you come through the door :laugh:
It's amazing how easy it is to get into the refurb vortex and not be able to get out. As you've seen, device after device has some inconspicuous issue that requires a return. These forums are loaded with these stories.
Hopefully the next one will be the one that keeps you happy, out of the VZW stores, and out of that vortex.
A QPST backup would have kept you out of this loop lol. So sorry to hear the struggle!
con247 said:
A QPST backup would have kept you out of this loop lol. So sorry to hear the struggle!
Click to expand...
Click to collapse
Yeah, I was in IRC while switching to CM10. invisibleK tried to help me out, but this was before the EFS or QPST fixes.
I too got the IMEI of 0 prior to QPST backups (ironically I got it from a TW rom, never flashed a AOSP rom. I think it was the lean Kernal.) I tried restoring my efs.sbn but I am stuck in roaming. If I Odin back to stock and take my phone back to a VZW will they give me a new one?
I got Verizon to do an even swap form a GNEX to a GS3 because of the connectivity issues it has had...free upgrade
no wonder verizon doesnt like people rooting their phones. op's fault
First two refurbs were your fault, hopefully with this 4th one it'll act right, and you won't mess it up.
luke1333 said:
no wonder verizon doesnt like people rooting their phones. op's fault
Click to expand...
Click to collapse
Yeah, I'd like to say it's vzw's fault for locking things down, but it happens on other networks as well. Looks like a Samsung issue.
Jothen2002 said:
I got Verizon to do an even swap form a GNEX to a GS3 because of the connectivity issues it has had...free upgrade
Click to expand...
Click to collapse
Hah, I tried to switch to a gnex and they talked me out of it.
tgom222 said:
I too got the IMEI of 0 prior to QPST backups (ironically I got it from a TW rom, never flashed a AOSP rom. I think it was the lean Kernal.) I tried restoring my efs.sbn but I am stuck in roaming. If I Odin back to stock and take my phone back to a VZW will they give me a new one?
Click to expand...
Click to collapse
Yeah, they should replace it, just play dumb and make sure you're on stock. But you'll end up with a return if it's been more than 14 days, and you really don't want that. Instead, just use QPST to write your IMEI to your phone. You don't need a backup, just the number on the back of the phone.
Neverendingxsin said:
First two refurbs were your fault, hopefully with this 4th one it'll act right, and you won't mess it up.
Click to expand...
Click to collapse
How is a faulty capacitive layer on a touchscreen my fault? A ROM doesn't make a touchscreen go bad.
Hi all. My new phone was going greatish. It was a little laggy, so thought I would root it and remove some of the preinstalled junk. All went fine no problem.
I removed some of the vodafone (UK) stuff, and all was well. Some time later though, I get a message:
"Unfortunately, the process com.android.phone has stopped"
And now my phone won't find the network and message pops up every couple of seconds. I tried a factory reset, but I suspect this made it worse as I have now lost my backups from Titanium app. The phone is basically unusable as it is due to constant error message and no network.
I have tried to access the recovery menu, but i get an empty robot with "no command".
I have seen some mention of CIDs on other forums but haven't got a clue how to go about fixing it or even where to start.
Any help would be greatly appreciated as obviously the phone is absolutely brand new, and I'm very very upset about the whole thing! Not to mention the fact that I feel like an idiot!
Anyway, thanks in advance.
You deleted something that was not suppose to be deleted. Don't the stock tot file on this forum and follow the steps to Flash back to factory
http://forum.xda-developers.com/g-flex2/general/guide-lg-g-flex-2-stock-firmware-to-t3037593 follow the video and you should be up in running in no time . make sure this link support your version not sure which g flex2 Version you have.
Still no tot files available for the LG G Flex 2 (any variant). Sorry got to wait for some to become available.
Thanks for the input. I figured it would be something like that. Any idea when the files might be available? I don't mind being a guinea pig at this stage. My phone is LG H955 on Vodafone UK.
I am going to try and play dumb in Vodafone shop today and see if they'll replace it there and then (doubtful).
I suppose my other alternative is to return it to LG for Firmware Flash. Anyone know if this is possible and potential cost?
Strangely, I'm not so bothered about (temporarily) destroying my brand new phone too much, it's my sudden lack of connectivity that hurts the most.
Thanks guys
Further update; I have spoken to LG tech support / repair department, and I told them the phone had been rooted etc. (I didn't leave any identifying details!) They informed me that as the phone was now out of warranty, I should speak to their service partner SBE.
After calling SBE, they informed me that LG or their partner have no obligation to fix rooted phones, so apparently they just won't do it, even though I'm certain they could, which kind of sucks, as I was obviously willing to pay.
So it looks like I'm waiting for the TOT files. I hope they come along soon!
Lesson well and truly learned!
djjag1 said:
Further update; I have spoken to LG tech support / repair department, and I told them the phone had been rooted etc. (I didn't leave any identifying details!) They informed me that as the phone was now out of warranty, I should speak to their service partner SBE.
After calling SBE, they informed me that LG or their partner have no obligation to fix rooted phones, so apparently they just won't do it, even though I'm certain they could, which kind of sucks, as I was obviously willing to pay.
So it looks like I'm waiting for the TOT files. I hope they come along soon!
Lesson well and truly learned!
Click to expand...
Click to collapse
Stay positive. Hopefully those tot files come soon. I on the other hand what to experiment with my phone but need a tot file just in case I mess anything up.
If it's just your dialer that's acting up, have you tried a third party dialer to make phone calls?
djjag1 said:
Further update; I have spoken to LG tech support / repair department, and I told them the phone had been rooted etc. (I didn't leave any identifying details!) They informed me that as the phone was now out of warranty, I should speak to their service partner SBE.
After calling SBE, they informed me that LG or their partner have no obligation to fix rooted phones, so apparently they just won't do it, even though I'm certain they could, which kind of sucks, as I was obviously willing to pay.
So it looks like I'm waiting for the TOT files. I hope they come along soon!
Lesson well and truly learned!
Click to expand...
Click to collapse
Lets see if we can work on this.
Is it working ok, just not picking up the network?
How long exactly have you had it?
If you put what you all deleted meaning what folders they were in i could make a copy of that folder or apps you deleted and upload them on dropbox for you that might help get you going worth a shot
Be better if someone had the same variant as you i have the Sprint model.
Thanks again for input. I have hopefully managed to sort this with my provider. I was just within the 14 day cancellation period, so I have arranged for a brand new handset. I know its a little bit naughty but if the phone wasnt so laggy to begin with, I would never have rooted it.
I'm guessing it makes no difference to them as the phone will go back to lg for wipe and reflash as a matter of course once returned.
Thanks folks, I will remain on this forum and hopefully not do anything quite so stupid again!
Unfortunately this is my last day with this device . Great phone but i was wrong the 810 processor is dangerously hot to the point it felt like my pockets were on fire. This my second g flex2 and I'm moving on to something more reliable. Love this phone but this heat issue i can't risk. After 14 days i would be stuck with this phone and i can't take the risk of hoping of getting a device that function fine bye everyone.
:victory::victory::victory:
Today, I've gotten myself in a similar pickle after applying noob root.. Data OK but no phonecalls and no txts. When I tried to make a call, the thing said the phone is not activated. Sprint tech supp was of course no help, so after some digging I found this: ##72786#
Factory reset, keep the data (and all apps).
That solved it.
I guess I'm old enough to know that being lazy doesn't pay.
Stank0 said:
Today, I've gotten myself in a similar pickle after applying noob root.. Data OK but no phonecalls and no txts. When I tried to make a call, the thing said the phone is not activated. Sprint tech supp was of course no help, so after some digging I found this: ##72786#
Factory reset, keep the data (and all apps).
That solved it.
I guess I'm old enough to know that being lazy doesn't pay.
Click to expand...
Click to collapse
so you had root, and while doing this factory reset you were able to go back to full stock unrooted rom? if so, were you able to install updates? i too have a sprint version and i was rooted and tried installing an update but failed, i then unrooted my phone tried the update again and still got an error. im just wondering if this method would actually help people who have the same problem as i do.
gothikzoul said:
so you had root, and while doing this factory reset you were able to go back to full stock unrooted rom? if so, were you able to install updates? i too have a sprint version and i was rooted and tried installing an update but failed, i then unrooted my phone tried the update again and still got an error. im just wondering if this method would actually help people who have the same problem as i do.
Click to expand...
Click to collapse
Unfortunately, that wasn't the case.
I tried every possible way to install this damn update. Rooted, unrooted, factory reset 4 times, tried to install from the system update in settings, from recovery (which is, at least for me, very tricky to get into) all efforts errored out.
I posted a link to the update.zip in other thread.
So then I gave up and used this noob root which killed voice calls and text.
This code I posted says it does a factory reset but is resetting something else than other factory resets because almost all my settings, passwords and all apps remained intact.. Then I used the original root method and everything works like it's supposed to.
I guess we'll have to wait until someone finally starts developing for our phone.
So after a few days I just received a notification for the update for the third time. Any suggestions as to how I should proceed? I've tried it while being rooted and failed, also tried it the second time after unrooting and failed too. Also, what is the default location where the update is downloaded to, so I can back it up.
So far nothing has worked. The update should be in the cache folder. There is also a link to download the update that someone posted in another thread here about the update.
FYI - I forced the update through recovery over root and bricked my phone. Like all the way bricked. I can get to recovery and download mode, but no fastboot even. Luckily I was within my 14 days and there is no way to tell it is rooted... because it doesn't even get that far, so I got a replacement. My sincere advice would be to wait to root until we have custom recovery and stock firmware available, and if you have root now, wait to update until a dev can release a "root safe" version.
I'm not an expert but I'm not new either. I got the original Evo on launch day and have done all kinds of dumb stuff to every phone since. This is the first time I haven't been able to recover it.
austontatious said:
FYI - I forced the update through recovery over root and bricked my phone. Like all the way bricked. I can get to recovery and download mode, but no fastboot even. Luckily I was within my 14 days and there is no way to tell it is rooted... because it doesn't even get that far, so I got a replacement. My sincere advice would be to wait to root until we have custom recovery and stock firmware available, and if you have root now, wait to update until a dev can release a "root safe" version.
I'm not an expert but I'm not new either. I got the original Evo on launch day and have done all kinds of dumb stuff to every phone since. This is the first time I haven't been able to recover it.
Click to expand...
Click to collapse
=( *hug. That sucks man, thankfully you were able to get it replaced. *pfew I dodged a bullet there. I was actually thinking about doing the same thing getting home from work. Yeah its best we don't mess with the phone any longer those that have root at the moment. Until custom recovery and stock rom is out like he says.
Wow. How did you manage to "force" the update through recovery? I tried it through recovery but it would error out. (Error 7)
I will tell you, as a cautionary tale.
The error when you flash from recovery references a specific file that is incompatible with the update. I used root explorer to investigate further and found that the root script had overwritten a system file. The original was saved as "original" so I deleted the file causing the error and renamed the original one. After that, the update went through and I thought I was golden... Only now nothing else works.