Related
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 have a chance to pick up a mint sensation locally for a cheap price. The seller is under the impression it is bricked. I've read through the threads for a while now but thought I would ask for some help/advice. The seller told me that he bricked the phone by trying to unroot it but has also said he was trying to "flash boot or something." He has made it clear that the phone will not turn on or show any signs of life. He has tried multiple batteries as well.
So, is there any way to ensure it is bricked? I had thought that maybe he messed up flashing a new rom.
If it is clearly bricked, what would be a good price to snag it for?
Would it be possible to buy it and contact HTC in regard to the warranty? What would this cost?
Thanks in advance,
PS; I have read about the inablility to charge after flashing CWM. I'm not sure if CWM was installed or not. I will ask that asap.
Sounds like an inappropriate file was flashed to hboot, in which case it's dead. Short of jtagging there is no way to fix it.
Thanks for the quick reply globatron. That sucks to hear that it probably is fried. Would the HTC warranty cover this type of repair?
MRpeabodyia said:
Thanks for the quick reply globatron. That sucks to hear that it probably is fried. Would the HTC warranty cover this type of repair?
Click to expand...
Click to collapse
No, they wouldnt as it was from user error.
Matt
Do you know for sure they wouldn't cover it? All morality aside it could be argued that it wasn't user error considering I'm not entirely sure what the seller did to it.
MRpeabodyia said:
Do you know for sure they wouldn't cover it? All morality aside it could be argued that it wasn't user error considering I'm not entirely sure what the seller did to it.
Click to expand...
Click to collapse
Well,morality aside you can always tell them that the OTA update bricked it.If you are a TMOUS customer you can try and contact T-mo first.They are usually easier to deal with than HTC.
NYCguy I read through your thread discussing your dealings with Tmous. I had thought about contacting them but they have been a huge pain for me lately. (Almost to the point of ending my contract). I shot HTC an email out of curiousity so I should hear back from them soon. I've had to replace a phone before via T-mobile and it was pretty smooth. I just don't want to do it all the time as this may look odd on their end.
NYCguy I read through your thread discussing your dealings with Tmous. I had thought about contacting them but they have been a huge pain for me lately. (Almost to the point of ending my contract). I shot HTC an email out of curiousity so I should hear back from them soon. I've had to replace a phone before via T-mobile and it was pretty smooth. I just don't want to do it all the time as this may look odd on their end.
Well I bought my "bricked" sensation. I spoke with the seller for a while and it seems he had rooted it, received notification of the OTA, and attempted to unroot it. He didn't give me specifics on the procedure he used but I'm going to read as much as I can, depending on when my monster child will let me, and attempt to fix this thing. I read about the battery tricks and will try those tonight. Any suggestions as this point guys?
Well after reading and tinkering with this thing for a while it seems I have the dreaded qhsusb brick. I already spoke with HTC and it is under warranty until November of 2013. My new question is, Will HTC be able to tell the device was ever rooted? A rom was never installed so it should be stock. Seems the seller made a mistake in trying to go from s-off to s-on. Just hoping I won't have to pay much to have a new one sent from the manufacturer.
Thanks
MRpeabodyia said:
Well after reading and tinkering with this thing for a while it seems I have the dreaded qhsusb brick. I already spoke with HTC and it is under warranty until November of 2013. My new question is, Will HTC be able to tell the device was ever rooted? A rom was never installed so it should be stock. Seems the seller made a mistake in trying to go from s-off to s-on. Just hoping I won't have to pay much to have a new one sent from the manufacturer.
Thanks
Click to expand...
Click to collapse
Well if it's a QHSUB brick that means the phone is truely DEAD.If you can't boot into bootloader,can't charge it and can't connect to a PC,then i don't see how could they tell if it was rooted or not.There is no way for them to tell.You just tell them you bricked it while trying to install the OTA update,or do as i did and contact T-mobile.
Good luck!
Thought I would update this thread for anyone who may stumble across it at a later date. I went ahead and sent my bricked phone into HTC. They repaired the phone and sent it back. I was suprised to see that they didn't send me a refurb.
I have to say that HTC were very easy to work with were quick in returning my phone.
As a preface, I got the ATT one x a few days ago, so far I'm really happy with it, but would like to get rid of a bunch of the bloatware and want to get root.
So this morning I woke up to the update message. Now I read up on it the night before on these forums that I should wait to update if I want to root/etc, so naturally I don't want to update quite yet. But here's the problem. The message popped up so fast that I could barely read the message. My thumb must have been right above the accept button, since the message disappeared almost instantly and the process started up. I exited it as far as possible, and it seemed to work. I used apps on the phone, and everything seemed fine. As soon as I locked the phone again, it decided to reboot, initiating the update, all on its own. Even a forced power-off wouldn't stop the wheels turning. And now I feel like an idiot. So is there any way/what is the best way to downgrade or reverse the update?
TL;DR: I accidentally updated the new update, is there, and or what is the best way to downgrade so I can eventually root?
As for my second question, obviously the warranty will be in question if I root/unlock. I've read that HTC will honor the warranty even if it's an unlock, but not a rom flash (even after a return to stock?) If I root/unlock, run into a problem, and return to stock will by warranty be effected? I've never done a warranty return, so would there be a difference if I tried to go through HTC, ATT, or Costco (purchase location)? The reason I ask is because my last phone's (Original Atrix, love it so much) wifi died before the 2 year period, and we had an upgrade on the family account, and this time the One x was purchased with American Express, so I now effectively have a 2 year warranty to cover such problems I might have.
I know that with enough time I could find some of these answers on the forums, but because they are so lively, it's hard to keep track and sift through the forums for information. Thanks for your time and thank you in advance for your help.
In regards to the root on the update there is no way to downgrade or root given your situation at this time but hopefully one of the talented people here on xda wil find a new exploit like they did for the 1.85
As far as warranty goes someone else will.have to let you know.
Sent from my Nocturnalized Beast
same boat
I am in exactly the same boat. I didn't check the MD5 on a download of CR4.5 and it completed wiped my phone (SD Card as well). I was away from my laptop and had to wait days to get it back online. When I finally got it up and running, I was rooting through the one click and in checking the update, it updated to 2.20. So now I'm stuck.
I have my previous unlock token, but I'm not sure if that will do me any good. I don't want to do much until a new RUU becomes available.
misiek93 said:
As a preface, I got the ATT one x a few days ago, so far I'm really happy with it, but would like to get rid of a bunch of the bloatware and want to get root.
So this morning I woke up to the update message. Now I read up on it the night before on these forums that I should wait to update if I want to root/etc, so naturally I don't want to update quite yet. But here's the problem. The message popped up so fast that I could barely read the message. My thumb must have been right above the accept button, since the message disappeared almost instantly and the process started up. I exited it as far as possible, and it seemed to work. I used apps on the phone, and everything seemed fine. As soon as I locked the phone again, it decided to reboot, initiating the update, all on its own. Even a forced power-off wouldn't stop the wheels turning. And now I feel like an idiot. So is there any way/what is the best way to downgrade or reverse the update?
TL;DR: I accidentally updated the new update, is there, and or what is the best way to downgrade so I can eventually root?
As for my second question, obviously the warranty will be in question if I root/unlock. I've read that HTC will honor the warranty even if it's an unlock, but not a rom flash (even after a return to stock?) If I root/unlock, run into a problem, and return to stock will by warranty be effected? I've never done a warranty return, so would there be a difference if I tried to go through HTC, ATT, or Costco (purchase location)? The reason I ask is because my last phone's (Original Atrix, love it so much) wifi died before the 2 year period, and we had an upgrade on the family account, and this time the One x was purchased with American Express, so I now effectively have a 2 year warranty to cover such problems I might have.
I know that with enough time I could find some of these answers on the forums, but because they are so lively, it's hard to keep track and sift through the forums for information. Thanks for your time and thank you in advance for your help.
Click to expand...
Click to collapse
BB2DX said:
I am in exactly the same boat. I didn't check the MD5 on a download of CR4.5 and it completed wiped my phone (SD Card as well). I was away from my laptop and had to wait days to get it back online. When I finally got it up and running, I was rooting through the one click and in checking the update, it updated to 2.20. So now I'm stuck.
I have my previous unlock token, but I'm not sure if that will do me any good. I don't want to do much until a new RUU becomes available.
Click to expand...
Click to collapse
The ruu is out for the 2.20 on the HTC dev site
If you already have your unlock token you should be fine just run through the steps to unlock then root. Your still stuck with the new hboot so your previous nandroids will no longer work and you can no longer flash boot images from recovery.
Sent from my Nocturnalized Beast
misiek93 said:
As for my second question, obviously the warranty will be in question if I root/unlock. I've read that HTC will honor the warranty even if it's an unlock, but not a rom flash (even after a return to stock?) If I root/unlock, run into a problem, and return to stock will by warranty be effected? I've never done a warranty return, so would there be a difference if I tried to go through HTC, ATT, or Costco (purchase location)? The reason I ask is because my last phone's (Original Atrix, love it so much) wifi died before the 2 year period, and we had an upgrade on the family account, and this time the One x was purchased with American Express, so I now effectively have a 2 year warranty to cover such problems I might have.
Click to expand...
Click to collapse
Consensus seems to be that a warranty return to AT&T, they don't normally check for bootloader unlock at all. Technically, they can check, and void your warranty. But to this point, they don't seem to be. This is probably your safest bet. But that warranty is only one year.
Based on various reports by XDA users HTC seems to be much more strict about enforcing their own warranty terms. I would suggest going through AT&T rather than HTC.
For your AmEx warranty, I think that would be handled by AmEx (not AT&T). You should probably check through them, and see what the warranty terms our (might be handled by a 3rd party?). I think only someone that has had experience with the AmEx process could say for sure what would happen in this case. So maybe somebody will chime in.
redpoint73 said:
Consensus seems to be that a warranty return to AT&T, they don't normally check for bootloader unlock at all. Technically, they can check, and void your warranty. But to this point, they don't seem to be. This is probably your safest bet. But that warranty is only one year.
Based on various reports by XDA users HTC seems to be much more strict about enforcing their own warranty terms. I would suggest going through AT&T rather than HTC.
For your AmEx warranty, I think that would be handled by AmEx (not AT&T). You should probably check through them, and see what the warranty terms our (might be handled by a 3rd party?). I think only someone that has had experience with the AmEx process could say for sure what would happen in this case. So maybe somebody will chime in.
Click to expand...
Click to collapse
Amex is extremely lax. All they want is a copy of the original warranty and require doing the work at an authorized repair shop. Then they reimburse you, no questions asked.
GroovyGeek said:
Amex is extremely lax. All they want is a copy of the original warranty and require doing the work at an authorized repair shop. Then they reimburse you, no questions asked.
Click to expand...
Click to collapse
I kinda figured as much. They aren't in the business of fixing phones, so I guessed they either just farmed it out to a 3rd party company, or just paid up pretty easily. Credit cards (especially AmEx) also often cover things like lost luggage, travel insurance (cancelled flights, etc.) and I don't imagine they go through much hassle confirming that kind of thing either. They must figure that the extra business gained from offering their services (and yearly fees) outweighs the payouts they have to make.
Thanks for clarifying with your personal experience, probably useful to the OP.
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