Related
OK, with all my messaging and calendar issues, I decided to re-flash the stock tar (as I had used the old method of rooting). I set the phone up again, and now I am still stuck at the start up screen with the rings. It will not go any further. It works fine as long as I do not shut the phone down. From what I can tell, in order to fix it, I need to factory reset, which I am hoping to not do this time again (for the third time in a day). Where should or can I go from here?
redownload the tar file again, check the md5 sum to make sure its good.
Also make sure the tar file is for your carrier, ie; verizon. that may be your problem.
Ended up they are sending me a new device. Could be the device? Could be an app or setting I am restoring with TB though. Not sure. It is getting kind of frustraing since I am not hacking this as I have other phones in the past and am having more trouble with this than any other phone.
LTLFTCer said:
Ended up they are sending me a new device.
Click to expand...
Click to collapse
This is why we can't have nice things. If people didn't waste so much of Verizon's time and money with their hacking maybe Verizon wouldn't feel the need to fight so hard to keep us from being able to hack our phones.
Did you flash stock with recovery or did you Odin back? Cuz if you odin'ed back, you may have missed the step to uncheck auto reboot, then load stock recovery mode and wipe phone. If you Odin to stock and don't after that, but before booting, you will most likely boot loop or freeze.
For future reference....
jimmiem said:
This is why we can't have nice things. If people didn't waste so much of Verizon's time and money with their hacking maybe Verizon wouldn't feel the need to fight so hard to keep us from being able to hack our phones.
Click to expand...
Click to collapse
Andthis is why XDA sucks sometimes. Guys like you who troll and decide to post in a thread in a negative way instead of helping out earlier. And in all actuality, what is happening to my phone I do not think has anything to do with rooting. I had rooted on 7/9 for the sole purpose of wifi tether, nothing else had been done to the phone. It worked flawlessly until this week when the borwser, calendar and facebook decided to start force closing for no apparent reason. I figured a reboot would help and that started these issues. Sooo..therefore I decided to revert back from scratch and the problem is still there. I think we all would know that Verizon care wouldn't be able to hel outside exchanging the phone.
TechSavvy2 said:
Did you flash stock with recovery or did you Odin back? Cuz if you odin'ed back, you may have missed the step to uncheck auto reboot, then load stock recovery mode and wipe phone. If you Odin to stock and don't after that, but before booting, you will most likely boot loop or freeze.
For future reference....
Click to expand...
Click to collapse
Thanks, I did uncheck autoreboot. And was able to enter stock recovery. I actually factory reset again and other than the calendar issues, seems to be working fine so far.
LTLFTCer said:
Andthis is why XDA sucks sometimes. Guys like you who troll and decide to post in a thread in a negative way instead of helping out earlier.
Click to expand...
Click to collapse
You haven't even waited a day after posting for help before calling Verizon.. Too many people on these forums feel like Verizon is obligated to correct their problems even though they went against their Terms of Service..
Sent from my Commodore 64..
READY.
load"*",8,1
Hypnosis4U2NV said:
You haven't even waited a day after posting for help before calling Verizon.. Too many people on these forums feel like Verizon is obligated to correct their problems even though they went against their Terms of Service..
Sent from my Commodore 64..
READY.
load"*",8,1
Click to expand...
Click to collapse
Maybe so, but this didn't appear to be a root issue. Since this phone is so locked down I hadn't messed with anything and was getting multiple random force closes and then got stuck at the boot screen. No biggie, think I got it sorted out, went throgh and manually reset all settings and apps. Seems to have worked.
I'm glad you fixed the issue yourself..
Sent from my Commodore 64..
READY.
load"*",8,1
I've basically had it with my Skyrocket, or rather, the Skyrocket that I have. It has always had atrocious battery life, exhibited weird behavior (like today when it lost nearly 20% of its battery in about 2 hours, and claiming the PHONE component was the prime culprit when I hadn't made a phone call) and also even after I unlocked the damn thing I still can't get it to force to 2G (yes I'm using an Unlocked RAT as well.) I'm still under warranty so I want a different one even if it is refurbished.
Anyways, I know the whole deal of using ODIN to return to Stock and making sure the Flash Counter isn't tripped, but in this day and age I'm paranoid about tech stuff having personal stuff getting stolen, so I'm tempted to wipe out the internal SD card, but I don't know if this is necessary and/or potentially harmful. Can I boot into Recovery and have it format my internal card, then ODIN back to Stock, or will this just cause more problems than it's worth?
dvandam said:
I've basically had it with my Skyrocket, or rather, the Skyrocket that I have. It has always had atrocious battery life, exhibited weird behavior (like today when it lost nearly 20% of its battery in about 2 hours, and claiming the PHONE component was the prime culprit when I hadn't made a phone call) and also even after I unlocked the damn thing I still can't get it to force to 2G (yes I'm using an Unlocked RAT as well.) I'm still under warranty so I want a different one even if it is refurbished.
Anyways, I know the whole deal of using ODIN to return to Stock and making sure the Flash Counter isn't tripped, but in this day and age I'm paranoid about tech stuff having personal stuff getting stolen, so I'm tempted to wipe out the internal SD card, but I don't know if this is necessary and/or potentially harmful. Can I boot into Recovery and have it format my internal card, then ODIN back to Stock, or will this just cause more problems than it's worth?
Click to expand...
Click to collapse
Yes you can I have reformatted my internal several times before using Odin personally I just mount our to the pc and format that way. Spector7 has done they CWM using format emmc and said out worked fine but emmc is at your own risk I just format they pc
Sent from my SAMSUNG-SGH-I727 using xda premium
Okay next stupid question...
Would it not be easier to just install a Stock Rom then install Stock Recovery to get my phone back to regular state as mentioned here after I do a formatting, as opposed to going through all the ODIN stuff, which, if done wrong, can trip the flash counter more easily and thus leaving me with some explaining to do at the AT&T store?
dvandam said:
Okay next stupid question...
Would it not be easier to just install a Stock Rom then install Stock Recovery to get my phone back to regular state as mentioned here after I do a formatting, as opposed to going through all the ODIN stuff, which, if done wrong, can trip the flash counter more easily and thus leaving me with some explaining to do at the AT&T store?
Click to expand...
Click to collapse
I would Wipe after stock rom modem and recovery that way if it bricks att will need to fix it
Use the CWM method.
Well I returned to stock and am planning on going to AT&T after work to demand a replacement. Maybe I can use my charm and wit to negotiate into getting an upgrade to a S3 if they don't have any Skyrockets in stock, but then again I'm a guy who plays the lottery, so I'll keep my expectations in check. Worst case scenario and they just turn me down I'll brick the damn thing intentionally and then say "Oh it stopped working after the most recent update." Wish me luck.
TBQH, I'd just brick it in Kies by restoring to 2.3.5 and unpluggig during the ICS update. Tell them that you were updating to 4.0, and the thing wouldn't turn back on afterwards. If nothing else, AT&T will help get things with Sammy in order.
I wouldn't even bring up the other problems
Sent from my SGH-I727 using Tapatalk 2
T.J. Bender said:
TBQH, I'd just brick it in Kies by restoring to 2.3.5 and unpluggig during the ICS update. Tell them that you were updating to 4.0, and the thing wouldn't turn back on afterwards. If nothing else, AT&T will help get things with Sammy in order.
I wouldn't even bring up the other problems
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Sorry I have no idea how Kies works (never had a need to use it as I just flash everything) That's a program you install on your CPU right and then do the update by downloading in Kies and then plugging the phone into the CPU to download to it?
dvandam said:
Sorry I have no idea how Kies works (never had a need to use it as I just flash everything) That's a program you install on your CPU right and then do the update by downloading in Kies and then plugging the phone into the CPU to download to it?
Click to expand...
Click to collapse
Correct go too the android development thread and check out Vimcom stick alright so just check it or its not bad
Sent from my SAMSUNG-SGH-I727 using xda premium
Looks like I may have given myself a reason to return it before I could intentionally brick it via Kies..
I just ODINed back to stock and now the device is stuck in a boot loop. I double checked the download mode and it didn't trip the counter, so at least they can't accuse me of messing with it in that regard. I do hope that a new phone helps my problems, because quite frankly it's hard to stick with the Skyrocket in general after seeing the smoothness of the Galaxy Nexus (which my wife has) or the robust beast that is the SIII. I swear though if the Nexus 4 had LTE I'd have already ordered it, paid for same day shipping, and taken the entire day off to be able to play with it. Oh if ONLY they had included LTE... I would have paid $100 extra for that even..
Update on this..
Brought it to my local store, only to be referred to the one and only repair center in the state. They said they were going to try and restore the stock firmware onto the device. I started to get worried as I thought they may be able to undo what I had done. About 15 minutes later they gave up. I think they were trying to use Kies as opposed to ODIN. I didn't want to give on that I really knew my way around the phone and may have done the work myself. Anyways they gave me a new phone and sent me on my way.
I flashed CM10 M2 on my device again. As far as battery life goes.. it seems pretty comparable to what I had before. At this point I don't feel like going back to get yet ANOTHER Skyrocket. I suppose I'm just stuck with this battery life forever.
On a side note, even though for many of us this may be common knowledge, for everyone else, if your device is bricked, whether intentional or not, MAKE SURE YOU WIPE YOUR FLASH COUNT BEFORE BRINGING IN FOR SERVICE! The first thing the tech people are going to do is put your device into Download mode and hook it up to a CPU to flash original firmware. Unless they're COMPLETELY ignorant or don't care, if they see that custom Rom counter tripped then they're not going to touch your device.
dvandam said:
Update on this..
Brought it to my local store, only to be referred to the one and only repair center in the state. They said they were going to try and restore the stock firmware onto the device. I started to get worried as I thought they may be able to undo what I had done. About 15 minutes later they gave up. I think they were trying to use Kies as opposed to ODIN. I didn't want to give on that I really knew my way around the phone and may have done the work myself. Anyways they gave me a new phone and sent me on my way.
I flashed CM10 M2 on my device again. As far as battery life goes.. it seems pretty comparable to what I had before. At this point I don't feel like going back to get yet ANOTHER Skyrocket. I suppose I'm just stuck with this battery life forever.
On a side note, even though for many of us this may be common knowledge, for everyone else, if your device is bricked, whether intentional or not, MAKE SURE YOU WIPE YOUR FLASH COUNT BEFORE BRINGING IN FOR SERVICE! The first thing the tech people are going to do is put your device into Download mode and hook it up to a CPU to flash original firmware. Unless they're COMPLETELY ignorant or don't care, if they see that custom Rom counter tripped then they're not going to touch your device.
Click to expand...
Click to collapse
Did you get a brand new phone or a refurbished?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Not sure. I'd guess refurbished as they basically had buckets in on their wall that had a wide assortment of various phones for replacement. Overall though I'm not going to fight over refurbished vs getting a brand new one. I could just as easily get a bad refurb as I could get a lemon new.
Honestly at this point I'm more annoyed with the lack of "snappiness" of this phone. As I said it doesn't help that my wife has a Galaxy Nexus (which quite frankly even ran ICS better than my Skyrocket ever did) so to see how my system is "supposed" to run and not have it just bugs me. Seeing the Galaxy S3 in action makes me so envious with that gorgeous screen and snappy response just makes me regret more and more that day nearly a year ago when my 21 month old for grabbed my Nexus One and I didn't tackle her before she threw it down the stairs. Being forced to buy a phone well before I wanted to buy a new one as I wanted to wait for LTE deployment in my area, (which I STILL don't have BTW) and now regretting a year later just... ugh.. For all the crap Apple gets with their phones, at least it's easy to pick out which phone of theirs is the best available at any given time, and (assuming they don't change to the iPad release schedule) you can feel confident it'll stay top of the line for a year.
Sorry for the /rant there
dvandam said:
Not sure. I'd guess refurbished as they basically had buckets in on their wall that had a wide assortment of various phones for replacement. Overall though I'm not going to fight over refurbished vs getting a brand new one. I could just as easily get a bad refurb as I could get a lemon new.
Honestly at this point I'm more annoyed with the lack of "snappiness" of this phone. As I said it doesn't help that my wife has a Galaxy Nexus (which quite frankly even ran ICS better than my Skyrocket ever did) so to see how my system is "supposed" to run and not have it just bugs me. Seeing the Galaxy S3 in action makes me so envious with that gorgeous screen and snappy response just makes me regret more and more that day nearly a year ago when my 21 month old for grabbed my Nexus One and I didn't tackle her before she threw it down the stairs. Being forced to buy a phone well before I wanted to buy a new one as I wanted to wait for LTE deployment in my area, (which I STILL don't have BTW) and now regretting a year later just... ugh.. For all the crap Apple gets with their phones, at least it's easy to pick out which phone of theirs is the best available at any given time, and (assuming they don't change to the iPad release schedule) you can feel confident it'll stay top of the line for a year.
Sorry for the /rant there
Click to expand...
Click to collapse
You're confused.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
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.
It would appear that, in my habit of ruining everything, I failed the low effort boot and bricked my new LG G4. Thankfully, I remembered that in this instance you can flash the stock firmware to return to default. Unfortunately, the US firmware wasn't available, but apparently the Puerto Rico one was. I flashed that and got my phone back working just fine, kind of.
First, it doesn't lock normally. Usually, I set it to the 10 minute lock delay, where I just have to swipe unless 10 minutes have passed, then it requires the password. Instead of going to a lock screen, it skips that and just goes right into the phone. It's probably a settings thing, but it's weird.
The worst thing is that I have apparently lost 30GB of storage to "miscellaneous". When I plug it into my computer, it says that I only have 1GB of storage on the whole phone. What is going on here?
Same thing happened to me. Your not gonna be able to flash anything else because of the space on the phone, and can't get the System Image onto a MicroSD card to try and fix it either. I tried both then I just called up AT&T and told them about a problem which I did encounter with the flash making noise when turned on. They replaced the phone
Not sure if there is an actual work around to get the space back but what happened was you flashed it to the wrong partition.
I have the same issue. No one has figured it out yet
TheProblemCauser said:
Same thing happened to me. Your not gonna be able to flash anything else because of the space on the phone, and can't get the System Image onto a MicroSD card to try and fix it either. I tried both then I just called up AT&T and told them about a problem which I did encounter with the flash making noise when turned on. They replaced the phone
Not sure if there is an actual work around to get the space back but what happened was you flashed it to the wrong partition.
Click to expand...
Click to collapse
The problem is that I'm not encountering any issues like that so far. I doubt that they'd replace an issue caused by failed root.
Sorry for the double post, but is there any way that I can create a situation where I could get my phone replaced? I just got it, so it still is under warranty.
Flash the ATT system image back on to it and brick it is about your only option.
Sent from my LG-H810 using Tapatalk
Nynten said:
Sorry for the double post, but is there any way that I can create a situation where I could get my phone replaced? I just got it, so it still is under warranty.
Click to expand...
Click to collapse
Best case scenario would be to call them up and tell them your phone got bricked due to an update. Then let them know that you needed the said phone in a working condition until you can get a replacement.
Or tell them a bull**** problem, normally they send you the replacement then you ship yours out to them. Done this twice already I'm on my 3rd G4
TheProblemCauser said:
Best case scenario would be to call them up and tell them your phone got bricked due to an update. Then let them know that you needed the said phone in a working condition until you can get a replacement.
Or tell them a bull**** problem, normally they send you the replacement then you ship yours out to them. Done this twice already I'm on my 3rd G4
Click to expand...
Click to collapse
Can I just take it to the shop bricked "from an update" and get a new one there or do I have to mail it in?
How do I flash the stock att .Img with a full system data. Sorry of this is a noob question
Nynten said:
Can I just take it to the shop bricked "from an update" and get a new one there or do I have to mail it in?
Click to expand...
Click to collapse
You probably can. Its still under warranty so you should still get it replaced
TheProblemCauser said:
You probably can. Its still under warranty so you should still get it replaced
Click to expand...
Click to collapse
You can take it to a shop, but they will still call customer service and you will have to mail it in still. I paid extra to have a next day replacement.
Was told they don't switch phones in store anymore. Had a few local friends confirm their warranty replacements were done the same way from in store. I'm not sure if that is a national policy, regional, or local. I can say I did like it better when they could switch out in store.
Anybody come up with another solution besides sending the phone back??? I won my phone off a att contest. So I doubt if att will do anything about it. Plus I can't install the stock Img and re soft brick the phone because I don't have anymore space
I have an LG G2 D800, with stock everything; I did something either interesting or dumb, and now it won't boot. I never rooted it because all the instructions were for Windows, and I use Linux, and never found anything that explained how to do it with Linux, if possible. But I now have a a usable Windows (Vista) installed in a VM, so maybe I can do something.
Here's what happened; I hope someone can help steer me in the right direction...
I finished my AT&T contract, and decided to move to Project Fi. I got a Nexus 5X, and got an unlock code for my G2, which I wanted to give to my wife's brother in China. So, I needed to get a non-AT&T sim to enter the unlock code. Here's where I went wrong. I was curious about what would happen if I used the Project Fi sim, and since I wasn't rooted, I didn't think it would do anything bad (silly me!). Well, it did. It crashed, so I removed the sim and turned off the phone. Now, it won't boot. It sometimes just shuts down immediately, sometimes after the LG logo, sometimes after the AT&T logo, and a few times, it made it all the way to the login screen before turning off. Never further than that.
I did a factory reset, tried starting in safe mode many times, and sometimes it gets to a screen saying it's updating Android, but has never made it past 20 files before turning off. By the way, if it was reset, how could it update Android - wouldn't the WiFi need to be set up?
So, I'm wondering what might be wrong, and what might fix it. Obviously, I'm willing to try anything at this point, as it can't get much worse. The phone is in perfect shape, and would make a nice gift (or sellable item), so I hate to lose it.
I'm pretty technically inclined, but I don't know much about phone tech. I know Linux pretty well though, so I can follow directions without too much babying. Or, just point me the right direction.
It did go into download mode, but right now, it seems like it doesn't want to do that.
Thanks to anyone that can help.
Marty
martyfried said:
I have an LG G2 D800, with stock everything; I did something either interesting or dumb, and now it won't boot. I never rooted it because all the instructions were for Windows, and I use Linux, and never found anything that explained how to do it with Linux, if possible. But I now have a a usable Windows (Vista) installed in a VM, so maybe I can do something.
Here's what happened; I hope someone can help steer me in the right direction...
I finished my AT&T contract, and decided to move to Project Fi. I got a Nexus 5X, and got an unlock code for my G2, which I wanted to give to my wife's brother in China. So, I needed to get a non-AT&T sim to enter the unlock code. Here's where I went wrong. I was curious about what would happen if I used the Project Fi sim, and since I wasn't rooted, I didn't think it would do anything bad (silly me!). Well, it did. It crashed, so I removed the sim and turned off the phone. Now, it won't boot. It sometimes just shuts down immediately, sometimes after the LG logo, sometimes after the AT&T logo, and a few times, it made it all the way to the login screen before turning off. Never further than that.
I did a factory reset, tried starting in safe mode many times, and sometimes it gets to a screen saying it's updating Android, but has never made it past 20 files before turning off. By the way, if it was reset, how could it update Android - wouldn't the WiFi need to be set up?
So, I'm wondering what might be wrong, and what might fix it. Obviously, I'm willing to try anything at this point, as it can't get much worse. The phone is in perfect shape, and would make a nice gift (or sellable item), so I hate to lose it.
I'm pretty technically inclined, but I don't know much about phone tech. I know Linux pretty well though, so I can follow directions without too much babying. Or, just point me the right direction.
It did go into download mode, but right now, it seems like it doesn't want to do that.
Thanks to anyone that can help.
Marty
Click to expand...
Click to collapse
Greetings.
Thank you for using XDA Assist. I'm going to move this thread to the specific device Q and A forum. You should find expert help there. Good luck!