I tried flashing the marshmallow update that was just released (a very, very idiotic move) I flashed it the first time and all seemed well; everything flashed with no errors, and it rebooted. Well, upon reboot, I get the dreaded Factory Reset Status 2. Okay, no big deal, I just realized that I forgot to select "BOARD DL". I got to try to flash again, this time selected BOARD. Now, I get a dodownloaderror at 18s. Every time. I have tried everything, battery pulls, reflashing, I even tried reflashing ZV6 (this is probably what dug my grave). Nothing. I can still boot to recovery and DL mode, but nothing is working. I didn't put a stock img on my internal storage, so sideloading from recovery isn't an option either.
I am such an idiot. Now I have a paperweight, and it is going to cost me several hundred, if not a thousand, dollars to end my contract on the brick and then go out and buy a new phone.
Does anyone have an methods that I haven't tried?
Did I mention that I am a huge idiot?
ironbesterer said:
I tried flashing the marshmallow update that was just released (a very, very idiotic move) I flashed it the first time and all seemed well; everything flashed with no errors, and it rebooted. Well, upon reboot, I get the dreaded Factory Reset Status 2. Okay, no big deal, I just realized that I forgot to select "BOARD DL". I got to try to flash again, this time selected BOARD. Now, I get a dodownloaderror at 18s. Every time. I have tried everything, battery pulls, reflashing, I even tried reflashing ZV6 (this is probably what dug my grave). Nothing. I can still boot to recovery and DL mode, but nothing is working. I didn't put a stock img on my internal storage, so sideloading from recovery isn't an option either.
I am such an idiot. Now I have a paperweight, and it is going to cost me several hundred, if not a thousand, dollars to end my contract on the brick and then go out and buy a new phone.
Does anyone have an methods that I haven't tried?
Did I mention that I am a huge idiot?
Click to expand...
Click to collapse
Same here..
Why are you both flashing MM? Is there an official image to flash?
EmSeeMAC said:
Why are you both flashing MM? Is there an official image to flash?
Click to expand...
Click to collapse
That's why I'm an idiot. It's not an official .TOT.
ironbesterer said:
That's why I'm an idiot. It's not an official .TOT.
Click to expand...
Click to collapse
I fixed mines using LG UP
http://forum.xda-developers.com/sprint-g4/development/howto-downgrade-to-zv6-upgrade-to-t3265976
This should help you fix the dreaded 2
If you can boot into download mode, flash the ROM for your phone on sammobile
Just say you installed an update and it bricked your phone if it's still under warranty. I dunno how many times I botched my G Flex 2 and LG replaced it (ATT model).
Why is it gonna cost you $1000.00. At worst you just buy another phone.
But the cheapest is to add TEP and bring it in. You might want to brick it hard enough that they cannot see that it was every rooted though
He fixed it
ironbesterer said:
I tried flashing the marshmallow update that was just released (a very, very idiotic move) I flashed it the first time and all seemed well; everything flashed with no errors, and it rebooted. Well, upon reboot, I get the dreaded Factory Reset Status 2. Okay, no big deal, I just realized that I forgot to select "BOARD DL". I got to try to flash again, this time selected BOARD. Now, I get a dodownloaderror at 18s. Every time. I have tried everything, battery pulls, reflashing, I even tried reflashing ZV6 (this is probably what dug my grave). Nothing. I can still boot to recovery and DL mode, but nothing is working. I didn't put a stock img on my internal storage, so sideloading from recovery isn't an option either.
I am such an idiot. Now I have a paperweight, and it is going to cost me several hundred, if not a thousand, dollars to end my contract on the brick and then go out and buy a new phone.
Does anyone have an methods that I haven't tried?
Did I mention that I am a huge idiot?
Click to expand...
Click to collapse
Okay, if you can get to download mode, then use the 'send_command' batch file to adb push a stock image to /dev/media/0/ then dd it.
---------- Post added at 05:55 PM ---------- Previous post was at 05:52 PM ----------
mswlogo said:
Why is it gonna cost you $1000.00. At worst you just buy another phone.
But the cheapest is to add TEP and bring it in. You might want to brick it hard enough that they cannot see that it was every rooted though
Click to expand...
Click to collapse
Hahaha this.
With a bootloader that's totally locked down you can just say that you accepted an OTA and your battery died while it was flashing and now your phone is screwed.
agentfusion said:
Okay, if you can get to download mode, then use the 'send_command' batch file to adb push a stock image to /dev/media/0/ then dd it.
---------- Post added at 05:55 PM ---------- Previous post was at 05:52 PM ----------
Hahaha this.
With a bootloader that's totally locked down you can just say that you accepted an OTA and your battery died while it was flashing and now your phone is screwed.
Click to expand...
Click to collapse
It would be close to a thousand to pay off my current device (around $300 owed on it) and then go out and buy a new one. But, with autoprime and awesomeslayerg's help, I got my phone back to normal.
I'm glad I seen this before I tried that
Related
I'm gonna just cut to the chase here, I've already looked at the forums and searched and all that.
Phone has been fine for about 3 weeks, since I got it, and all of a sudden it froze up on me and gave me the error "Process System Isn't responding" and of course with the 'wait' and 'ok' options. Phone does work fine except for the active display will not work and every time I unlock the phone it tells me that it crashed. I get random app crashes at random times as well. And my wifi is stuck in a permanent 'turning wifi on...' phase so I'm forced to use my 4g. I have tried all the suggestions that are possbile for the model of the Moto X that I have but nothing will work. Multiple factory resets, cahce wipes, everything. I've even tried flashing a stock rom to the phone via fastboot, didn't think it would work as I am on 4.4.2 AT&T version of the Moto X, and of course it didn't. Has anyone had the same problem, or found a workaround that actually works?
Well....it seems you're only option is flashing the 4.4.2 files for your phone. And if they aren't available....you probably have to play the waiting game unfortunately.
Are you rooted?? I would say if you're rooted, xposed or something that has changed system files is the culprit. But if you're not rooted....then who knows.
Good luck!!
P.s. never try to downgrade. You're lucky you got an error.....cause sometimes you get a brick.
---------- Post added at 07:00 PM ---------- Previous post was at 06:58 PM ----------
I thought at&t files were out now?????
kj2112 said:
Well....it seems you're only option is flashing the 4.4.2 files for your phone. And if they aren't available....you probably have to play the waiting game unfortunately.
Are you rooted?? I would say if you're rooted, xposed or something that has changed system files is the culprit. But if you're not rooted....then who knows.
Good luck!!
P.s. never try to downgrade. You're lucky you got an error.....cause sometimes you get a brick.
Click to expand...
Click to collapse
Not rooted, everything is completely stock, I did try flashing the 4.4.2 files to my phone, but can't get system.img to write, tried just flashing the update as a zip but wouldn't work because of something like the update-version wasnt found in the zip file... If only I had root, this would be a lot easier...
Edit: Would you be able to point me to the AT&T files? I did find firmware but that won't flash for some reason.
xVesica said:
Not rooted, everything is completely stock, I did try flashing the 4.4.2 files to my phone, but can't get system.img to write, tried just flashing the update as a zip but wouldn't work because of something like the update-version wasnt found in the zip file... If only I had root, this would be a lot easier...
Edit: Would you be able to point me to the AT&T files? I did find firmware but that won't flash for some reason.
Click to expand...
Click to collapse
I'm not sure where to get at&t files...there's a site that has them all...but I can't think of it.
And this guide has a return to stock section. Make sure you did it right. You do need to use mfastboot. Fastboot won't work on the bigger files.
http://forum.xda-developers.com/showthread.php?t=2558785
kj2112 said:
I'm not sure where to get at&t files...there's a site that has them all...but I can't think of it.
And this guide has a return to stock section. Make sure you did it right. You do need to use mfastboot. Fastboot won't work on the bigger files.
http://forum.xda-developers.com/showthread.php?t=2558785
Click to expand...
Click to collapse
Thanks for all the help, hopefully everything works.
Edit: Used the toolkit to flash the 4.4.2 update. I guess it just didn't like the way I was trying to do it before. Everything works again though, and hopefully it stays that way.
Now I get to go through the process of restoring all of my files.
Hello guys! So I bought a 64gb version of Nexus 6 just before new years eve and it started having issues in february. It got fully replaced by the service company for a new one. Yesterday my phone started complaining that I have insufficient storage. I checked how much memory I had and it said "32gb". So I'm using now a 32gb instead of a 64gb version which I was supposed to get from warranty. Nobody told me about the switch and the store where I bought it from said there has happened a mistake.
The thing that makes this tricky is that I've dropped the phone and the top layer of the screen is cracked. The screen itself works 100%, no color issues or issue tracking finger. It's just the top layer of protective glass that's bricked http://i.imgur.com/g6Se9dd.jpg They should contact on moday to me about this but what are really my options? If there never would had been a failure from their side, I would be living hapily with a 64gb bricked screen nexus 6 and have no issues. Do you think there are going to be more expenses for me due to their mistake?
Checked all papers over the issue. In the document over the repair, it states that they give me a new 64gb model of the phone.
One thing I started wondering about this morning. As me and my friend rooted my N6, we installed his stock image on it due to mine bugging out. He has a 32gb of N6. Could this affect it also? Both android system and disc checker app says I have left 23.03gb, aka. 32gb model.
FiresStream said:
Hello guys! So I bought a 64gb version of Nexus 6 just before new years eve and it started having issues in february. It got fully replaced by the service company for a new one. Yesterday my phone started complaining that I have insufficient storage. I checked how much memory I had and it said "32gb". So I'm using now a 32gb instead of a 64gb version which I was supposed to get from warranty. Nobody told me about the switch and the store where I bought it from said there has happened a mistake.
The thing that makes this tricky is that I've dropped the phone and the top layer of the screen is cracked. The screen itself works 100%, no color issues or issue tracking finger. It's just the top layer of protective glass that's bricked http://i.imgur.com/g6Se9dd.jpg They should contact on moday to me about this but what are really my options? If there never would had been a failure from their side, I would be living hapily with a 64gb bricked screen nexus 6 and have no issues. Do you think there are going to be more expenses for me due to their mistake?
Checked all papers over the issue. In the document over the repair, it states that they give me a new 64gb model of the phone.
One thing I started wondering about this morning. As me and my friend rooted my N6, we installed his stock image on it due to mine bugging out. He has a 32gb of N6. Could this affect it also? Both android system and disc checker app says I have left 23.03gb, aka. 32gb model.
Click to expand...
Click to collapse
Fastboot flashing the factory image will do this. To get your full 64gb of memory back, from bootloader do >
fastboot format userdata
NOTE: this will wipe the contents of your SDcard, so back it up on your PC first.
Yeah to echo the above, its quite common on the nexus to accidentally appear you have the smaller version after a flash...reflashing stock should fix it.
Doesn't it say which version you have in the bootloader?
Apparently emmc 64gb. Darn... Musta have flashed wrong stock image...
FiresStream said:
Apparently emmc 64gb. Darn... Musta have flashed wrong stock image...
Click to expand...
Click to collapse
No, there's no such thing as a wrong stock image. They're not storage-exclusive. Just a bad flash, it happens sometimes.
FiresStream said:
Apparently emmc 64gb. Darn... Musta have flashed wrong stock image...
Click to expand...
Click to collapse
No, you didn't. This happens with the 64gb versions. Factory reset after flashing factory image usually prevents it.
So I guess, nandroid backup and then reinstall. The backup should get everything back so I don't need to spend 4 hours to set up my phone accounts/settings etc?
FiresStream said:
So I guess, nandroid backup and then reinstall. The backup should get everything back so I don't need to spend 4 hours to set up my phone accounts/settings etc?
Click to expand...
Click to collapse
Not sure. Try it and see. Be sure to save it to your PC, as "fastboot format userdata" will wipe your SDcard.
****...
Tried to reinstall the phone but I'm now stuck in a situation where I can only access Fastboot and Recovery. Tried several times Nexus RootKit Stock flash but it doesn't seem to help either. Also wiped system/cache etc. for bad files. I really feel like this is a brick now...
Devicde is LOCKED. Status Code: 2
Any ideas how to proceed?
FiresStream said:
Tried to reinstall the phone but I'm now stuck in a situation where I can only access Fastboot and Recovery. Tried several times Nexus RootKit Stock flash but it doesn't seem to help either. Also wiped system/cache etc. for bad files. I really feel like this is a brick now...
Devicde is LOCKED. Status Code: 2
Any ideas how to proceed?
Click to expand...
Click to collapse
the toolkit is where you made the mistake. you have to flash the factory image via fastboot while you are hooked up to a computer while you're in the bootloader. if you have no idea what you are doing, toolkits wont help you out. read how to do it right, thete are a few threads here explaining for you, in detail.
---------- Post added at 05:09 PM ---------- Previous post was at 05:02 PM ----------
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
FiresStream said:
Tried to reinstall the phone but I'm now stuck in a situation where I can only access Fastboot and Recovery. Tried several times Nexus RootKit Stock flash but it doesn't seem to help either. Also wiped system/cache etc. for bad files. I really feel like this is a brick now...
Devicde is LOCKED. Status Code: 2
Any ideas how to proceed?
Click to expand...
Click to collapse
What happens when you try to reboot to Android? Your bootloader is locked so there isn't much you can do if you can't boot Android.
Do you have stock recovery or TWRP?
Tried quite a few options already in the Nexus Root Toolkit but without any results...
Anything specific I should give a try to hopefully let me sleep this night in peace?
Bootloop, just nothing... It just displays "Google" logo and does nothing further.
FiresStream said:
Bootloop, just nothing... It just displays "Google" logo and does nothing further.
Click to expand...
Click to collapse
try this via fastboot, and see if itll boot up. you have to be in the bootloader to use fastboot..
fastboot format cache
fastboot format userdata
then try booting up and enabling oem unlock.
simms22 said:
try this via fastboot, and see if itll boot up. you have to be in the bootloader to use fastboot..
fastboot format cache
fastboot format userdata
then try booting up and enabling oem unlock.
Click to expand...
Click to collapse
Got android studio installed from some time ago, just need to find out how to push the commands from cmd...
FiresStream said:
Got android studio installed from some time ago, just need to find out how to push the commands from cmd...
Click to expand...
Click to collapse
and hows android studio gonna help? you arent building an app.. you need to use fastboot.
simms22 said:
and hows android studio gonna help? you arent building an app.. you need to use fastboot.
Click to expand...
Click to collapse
Gotta say I'm hopeless in my situation... Got fastboot and abd drivers installed now, now I just need to find out how to use them...
FiresStream said:
Gotta say I'm hopeless in my situation... Got fastboot and abd drivers installed now, now I just need to find out how to use them...
Click to expand...
Click to collapse
thats ok, i was useless with fastboot at one time as well. at the very beginning, is when its the hardest, just because you are clueless. once you do it one time, its much easier every time after.
simms22 said:
thats ok, i was useless with fastboot at one time as well. at the very beginning, is when its the hardest, just because you are clueless. once you fo it one time, its much easier every time after.
Click to expand...
Click to collapse
Got the commands done which you suggested, how should I proceed?
FiresStream said:
Got the commands done which you suggested, how should I proceed?
Click to expand...
Click to collapse
try booting up. if you boot up, enable developer options, then go into them and enable oem unlocking. then you can unlock the bootloader and flash a factory image.
btw, i found this thread about using fastboot. its an older thread but.. http://forum.xda-developers.com/showthread.php?t=2277112
I need help, fast. im freaking out.
ok so, i needed to unroot my phone so i could send it in to get it replaced.well i went to unroot, i had the proper flash files and drivers and everything wugfresh said needed. but i forgot to make a recovery file, mostly cuz it told me i didnt have enough space on my phone, anyways thinking it went fine, i decided to lock the bootloader, and then it started to bootloop TWRP, so trying the unroot thing again, that didnt work, so i tried to unlock bootloader again, that didnt work. So in a moment of panic and stupidity i tried reinstalling everything using the guide that it had, but it wouldnt install anything. It's still in bootloop and idk what to do. have i screwed up? i dont have money for a new phone or another phone to use. any help would be great..
thanks in advance..
1. Don't use toolkits unless you can replicate everything they do (or everything you plan to use them for) on the the command line. They are for convenience, not for doing something you don't know how to do.
2. Try to unlock the bootloader again...but...
3. There is no need to unroot a nexus to send it in for a hardware defect. Just factory reset, take your sim out and ship. Just ship it.
brizey said:
1. Don't use toolkits unless you can replicate everything they do (or everything you plan to use them for) on the the command line. They are for convenience, not for doing something you don't know how to do.
2. Try to unlock the bootloader again...but...
3. There is no need to unroot a nexus to send it in for a hardware defect. Just factory reset, take your sim out and ship. Just ship it.
Click to expand...
Click to collapse
:victory:
---------- Post added at 11:07 PM ---------- Previous post was at 11:05 PM ----------
undeadfreak said:
I need help, fast. im freaking out.
ok so, i needed to unroot my phone so i could send it in to get it replaced.well i went to unroot, i had the proper flash files and drivers and everything wugfresh said needed. but i forgot to make a recovery file, mostly cuz it told me i didnt have enough space on my phone, anyways thinking it went fine, i decided to lock the bootloader, and then it started to bootloop TWRP, so trying the unroot thing again, that didnt work, so i tried to unlock bootloader again, that didnt work. So in a moment of panic and stupidity i tried reinstalling everything using the guide that it had, but it wouldnt install anything. It's still in bootloop and idk what to do. have i screwed up? i dont have money for a new phone or another phone to use. any help would be great..
thanks in advance..
Click to expand...
Click to collapse
you can try fastboot formatting userdata and cache, but that generally only works if you still have twrp installed. other than that, theres really nothing else that you can do.
brizey said:
3. There is no need to unroot a nexus to send it in for a hardware defect. Just factory reset, take your sim out and ship. Just ship it.
Click to expand...
Click to collapse
When I had to get mine replaced Sprint gave me crap cause I had bootloader unlocked and twrp installed. I had to take it home flash factory images and relock before they would take it back (for a sim slot issue) always best to go stock to avoid any issues.
Sent from my Nexus 6 using XDA Free mobile app
undeadfreak said:
I need help, fast. im freaking out.
ok so, i needed to unroot my phone so i could send it in to get it replaced.well i went to unroot, i had the proper flash files and drivers and everything wugfresh said needed. but i forgot to make a recovery file, mostly cuz it told me i didnt have enough space on my phone, anyways thinking it went fine, i decided to lock the bootloader, and then it started to bootloop TWRP, so trying the unroot thing again, that didnt work, so i tried to unlock bootloader again, that didnt work. So in a moment of panic and stupidity i tried reinstalling everything using the guide that it had, but it wouldnt install anything. It's still in bootloop and idk what to do. have i screwed up? i dont have money for a new phone or another phone to use. any help would be great..
thanks in advance..
Click to expand...
Click to collapse
If you cannot unlock the bootloader, fastboot format userdata and cache. Boot into TWRP and copy any rom.zip to the sdcard using MTP.
Flash the rom, tick the "allow oem unlock"
Boot to bootloader, unlock it. Flash stock CHECK IT BOOTS before you lock the BL.
Flex Hard bricked for seemingly no reason, I was on JB. I definitely declined any and all OTAs, one minute I was texting my boyfriend, locked the phone, set it down. Next minute it rebooted into recovery and refused to reboot into anything else. No big deal, adb was broken but I still had backups to flash. DL mode was broken, btw. I used usbotg to load up a backup and it still only booted into recovery. I figured I'd fix my dl mode by dding a laf.img backup I had made a while back to the right spot, but then after rebooting, recovery broke, and dl mode loaded, alas it was stuck on the dots. So I just gave up and have been boned ever since, figured I'd finally make a post asking if anyone would explain a process to repair, or be willing to do a hardmod for me for free, or money if wanted. I'm in the US and can probably ship most places, going on pure trust here.
Still looking for help
Have you tried flashing back to stock using DL mode and LG flash tools?
Since the same problem i have:
vivebatu said:
Have you tried flashing back to stock using DL mode and LG flash tools?
Click to expand...
Click to collapse
Sorry for intervening, i have the same problem and the same root of problem. accidentally i accepted an OTA and there it goes "bricked". i have only download mode. crossdl [d959] to [d958] swversion 0000000064 in LGFLASHTOOL when i tried to flash my stockrom. i already tried "hex editing" and the error goes to "Failed PreviousLoad". i cannot connect to adb or fastboot. the phone after the logo will said "Security Error". can you help please.
sharing results:
dongdong6968 said:
Flex Hard bricked for seemingly no reason, I was on JB. I definitely declined any and all OTAs, one minute I was texting my boyfriend, locked the phone, set it down. Next minute it rebooted into recovery and refused to reboot into anything else. No big deal, adb was broken but I still had backups to flash. DL mode was broken, btw. I used usbotg to load up a backup and it still only booted into recovery. I figured I'd fix my dl mode by dding a laf.img backup I had made a while back to the right spot, but then after rebooting, recovery broke, and dl mode loaded, alas it was stuck on the dots. So I just gave up and have been boned ever since, figured I'd finally make a post asking if anyone would explain a process to repair, or be willing to do a hardmod for me for free, or money if wanted. I'm in the US and can probably ship most places, going on pure trust here.
Click to expand...
Click to collapse
I have the same problem my dear and i am scouring the net for solution if you first find please share i will do the same. Thank you and God bless.
Anyone that can help?
QuickBrown said:
I have the same problem my dear and i am scouring the net for solution if you first find please share i will do the same. Thank you and God bless.
Click to expand...
Click to collapse
It doesn't seem you have the same problem, you have dl and I don't. I didn't ota, and you did. Maybe make your own post?
Sent from my LG-D950 using XDA Premium App
dongdong6968 :Have you tried LG Flash Tool 1.8 TOT and DLL method? If you at least have dl mode it should work. Mine ended up like yours, but with that method it works just fine now. And your device is soft bricked btw not hard bricked.
Sent from my LG G Flex LS995!
Kernelerf-g00861fe #1 (3.4.0)
Recovery/Version: TWRP 2.8.0.0 (still have stock backed up JIK)
ROM: MIUI v5 4.2.2 (JDQ39B)
---------- Post added at 06:04 PM ---------- Previous post was at 05:18 PM ----------
QuickBrown said:
Sorry for intervening, i have the same problem and the same root of problem. accidentally i accepted an OTA and there it goes "bricked". i have only download mode. crossdl [d959] to [d958] swversion 0000000064 in LGFLASHTOOL when i tried to flash my stockrom. i already tried "hex editing" and the error goes to "Failed PreviousLoad". i cannot connect to adb or fastboot. the phone after the logo will said "Security Error". can you help please.
Click to expand...
Click to collapse
As for your device QuickBrown. DO NOT cross DLL files you have a huge chance to brick! Look for your specific device files, thus eliminating hex editing. If you do OTA download it from someone who has posted them here in XDA. Mine had the same issue with accepting the OTA's. When i downloaded the OTA's from XDA and flashed them via adb sideload it worked fine. As for your adb and fastboot issue. Go to DL mode and flash the tot and dll. And if you decide to take the OTA downloads from here on XDA, when applying them via adb sideload do not skip the update order! As far as i know the ls995 flex (sprint) has the OTA's available here on XDA. As for the other variants i am unsure. Hope it helps! :fingers-crossed:
Hey there everyone, here to report unfortunate news about my g4 has died all out. Was using it to navigate using maps to a job yesterday, when suddenly my phone reboots and gets in boot loop. I take off battery to boot up phone back on, but turns out it doesn't at all respond to turn on, I try the hard master reset buttons to then boot to twrp but not even that responds. Weird cuz I had 40 percent battery left, connected phone to my charger and three more and no response at all in boot up or even sign of life. What can I do?
I have the same problem, phone wont respond at all and it was doing a boot loop, now it just wont turn on or respond to charging/no led light, nothing.
What are my options?
Rooted/No Insurance.
ExhumedWolf said:
I have the same problem, phone wont respond at all and it was doing a boot loop, now it just wont turn on or respond to charging/no led light, nothing.
What are my options?
Rooted/No Insurance.
Click to expand...
Click to collapse
That's weird how this has happened when i was running completely stock rom 10n rooted. Sucks that my screen has a very thin hairline crack which T-Mobile told me that LG won't accept it for warranty since it has physical damage.
Is there a way to restore the phone to complete stock using download mode? I'm in the same boat and now need to research a solution before returning to T-Mobile. This happened to a friend, too.
In my case, I was playing Fallout Shelter, the phone froze, so I did a battery pull. Now it won't boot up. Sometimes I can get it to go as far as the "Android is upgrading screen, " but then it either freezes again or goes into a bootloop. Tried booting into TWRP, but it either won't, or it'll freeze while inside before I can attempt to restore a backup or anything.
partylikeaninjastar said:
Is there a way to restore the phone to complete stock using download mode? I'm in the same boat and now need to research a solution before returning to T-Mobile. This happened to a friend, too.
In my case, I was playing Fallout Shelter, the phone froze, so I did a battery pull. Now it won't boot up. Sometimes I can get it to go as far as the "Android is upgrading screen, " but then it either freezes again or goes into a bootloop. Tried booting into TWRP, but it either won't, or it'll freeze while inside before I can attempt to restore a backup or anything.
Click to expand...
Click to collapse
Tried to boot in download mode and haven't been able since this occured. Nothing at all works for me in booting up to anything through the buttons, hopefully you can get DL mode working so you can get your g4 working back to normal.
wadamean said:
Tried to boot in download mode and haven't been able since this occured. Nothing at all works for me in booting up to anything through the buttons, hopefully you can get DL mode working so you can get your g4 working back to normal.
Click to expand...
Click to collapse
When I tried, I was able to boot into download mode, I didn't have any KDZ or whatever downloaded already or the flash tool in order to actually do anything so it was pointless, but it appears to boot into DL mode with no issue. For all I know, though, even though it booted into DL mode, it could have been completely frozen and unresponsive.
I think I found a thread with instructions and a link to the KDZ I need to download. Going to give this a try when I get home from work in twelve hours. If that fail, it's off to T-Mobile I go....
I have the same issue. I was browsing G+ then the phone just froze and now I can't get it to boot up or get into twrp. It will only boot loop.
Edit 1: I got my phone to boot and did a factory reset but it just ended up freezing and rebooting just like before. I'm going to try and get into twrp and flash the 10n stock then go to t-mobile to try and get them to get me a new one. I have insurance but the phone just randomly died, no dropping, didn't get it wet, so I don't want to have to pay a deductible.
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
That's to the lasted 10n version boot loader,DO NOT I REPEAT DO NOT FLASH THE BOOTLOADER TO A LOWER VERSION THEN YOU ALREADY HAVE! you will be beyond ****ed and not even lg can help you at that point..the bootladers have backwards protection to if you haven't updated to marshmallow flash the 10n bootloader( the most lasted bootloader for lp) and you should be fine.the lg flash tool should be included but be careful guys..I can't stress enough how important it is you flash the right BL..you will perma brick
mr turtle droid said:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
That's to the lasted 10n version boot loader,DO NOT I REPEAT DO NOT FLASH THE BOOTLOADER TO A LOWER VERSION THEN YOU ALREADY HAVE! you will be beyond ****ed and not even lg can help you at that point..the bootladers have backwards protection to if you haven't updated to marshmallow flash the 10n bootloader( the most lasted bootloader for lp) and you should be fine.the lg flash tool should be included but be careful guys..I can't stress enough how important it is you flash the right BL..you will perma brick
Click to expand...
Click to collapse
Thanks for the reminder. That's the thread I found and I also already made a mental note to flash the right image. My friend had this same problem and the person she tasked with fixing her phone flashed the wrong image and perma bricked her. Fortunately, T-Mobile still replaced her phone, though.
Sent from my LG-D851 using Tapatalk
mr turtle droid said:
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
That's to the lasted 10n version boot loader,DO NOT I REPEAT DO NOT FLASH THE BOOTLOADER TO A LOWER VERSION THEN YOU ALREADY HAVE! you will be beyond ****ed and not even lg can help you at that point..the bootladers have backwards protection to if you haven't updated to marshmallow flash the 10n bootloader( the most lasted bootloader for lp) and you should be fine.the lg flash tool should be included but be careful guys..I can't stress enough how important it is you flash the right BL..you will perma brick
Click to expand...
Click to collapse
That's true and I have not flashed nothing at all and only remained all on 10n rom and bootloader and modem. Yet this still happened to me.
My phone lives!
partylikeaninjastar said:
My phone lives!
Click to expand...
Click to collapse
That's amazing news!!!!
Actually, I take it back. It stopped working after an hour and started doing the same thing. On my way to T-Mobile in a bit.
Sent from my LG-D851 using Tapatalk
partylikeaninjastar said:
My phone lives!
Click to expand...
Click to collapse
partylikeaninjastar said:
Actually, I take it back. It stopped working after an hour and started doing the same thing. On my way to T-Mobile in a bit.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Let us know how it goes with T-Mobile. I was planning on getting my phone back to stock and then going to T-Mobile. I haven't had any luck bringing my phone back.
WillDeC said:
Let us know how it goes with T-Mobile. I was planning on getting my phone back to stock and then going to T-Mobile. I haven't had any luck bringing my phone back.
Click to expand...
Click to collapse
No hassle at all. Surprisingly. He just asked me what happened, then ordered my replacement to be delivered. Will have a new phone on Tuesday.
Sent from my LG-D851 using Tapatalk
WillDeC said:
Let us know how it goes with T-Mobile. I was planning on getting my phone back to stock and then going to T-Mobile. I haven't had any luck bringing my phone back.
Click to expand...
Click to collapse
I have great news everyone! Today I was cleaning my room. And just moved my g4 around onto my bed and then I see that the screen comes on saying I need to charge it. Which then I plug in and it charges now. I then wait a good while, get it to magically boot onto twrp. So excited and only option was to wipe all except the storages. I did, then flashed 10n rom again, not its back to life with no issues. Need to go to T-Mobile to connect it back on.
partylikeaninjastar said:
No hassle at all. Surprisingly. He just asked me what happened, then ordered my replacement to be delivered. Will have a new phone on Tuesday.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Good to hear. I just want to try and get it to stock. Sometime I can get to boot twrp and don't want to have to deal with them questioning about if they try and factory reset it or something.
WillDeC said:
Good to hear. I just want to try and get it to stock. Sometime I can get to boot twrp and don't want to have to deal with them questioning about if they try and factory reset it or something.
Click to expand...
Click to collapse
Reason why this issue has occurred is most likely in my opinion because of xposed. There is versions that work and those that aren't so stable in certain devices. What I advise you to do is boot into twrp when you get the chance, wipe all except the storages. You will notice how stable the phone gets and won't be bootlooping, which is what I noticed. Then flash whatever rom you have. Boot up, skip all intro steps, download the zip to get it to stock so you get the replacement. Keep telling T-Mobile that maybe at the moment it seems stable but it does this and you have gotten so fed up with it and won't be leaving until a replacement takes place. Either warranty or at store.
wadamean said:
Reason why this issue has occurred is most likely in my opinion because of xposed. There is versions that work and those that aren't so stable in certain devices. What I advise you to do is boot into twrp when you get the chance, wipe all except the storages. You will notice how stable the phone gets and won't be bootlooping, which is what I noticed. Then flash whatever rom you have. Boot up, skip all intro steps, download the zip to get it to stock so you get the replacement. Keep telling T-Mobile that maybe at the moment it seems stable but it does this and you have gotten so fed up with it and won't be leaving until a replacement takes place. Either warranty or at store.
Click to expand...
Click to collapse
I've never put xposed on this phone. I put twrp, rooted and was using a debloated rom. I had actually removed root so I could use android pay. It was working fine then just froze and constant reboots and freezing. I've only been able to get into twrp once without it freezing and rebooting,
WillDeC said:
I've never put xposed on this phone. I put twrp, rooted and was using a debloated rom. I had actually removed root so I could use android pay. It was working fine then just froze and constant reboots and freezing. I've only been able to get into twrp once without it freezing and rebooting,
Click to expand...
Click to collapse
You shouldn't have removed root and just used root cloak so that android pay thinks your unrooted. That's what I have been using. Because debloated roms always come injected with root and at times it becomes their core use within to function. When you get the chance to boot into twrp. Wipe all except storages and then reflash.