Develop Bugs

is this **** bricked??

its just sitting on the freaking LG screen... every time i vol dwn + pwr and double press power it goes normal but then cwm doesn't come up and it just restarts and hangs at LG again. i ****ing hate this phone can someone please help me out? why won't cwm load

can you describe exactly the process you took to port CWM into your phone? Let's see if something happened along the way to cause it to not work properly.
Also, is CWM the one not working, or did you flash a ROM on your phone and something went wrong, and you are trying to get to CWM to restore your phone but not getting anywhere with it?

aquariuz23 said:
can you describe exactly the process you took to port CWM into your phone? Let's see if something happened along the way to cause it to not work properly.
Also, is CWM the one not working, or did you flash a ROM on your phone and something went wrong, and you are trying to get to CWM to restore your phone but not getting anywhere with it?
Click to expand...
Click to collapse
followed the steps on the cwm thread. used terminal emulator. worked great. was working fine until now. i flashed kernels beta 2 and only wiped cache and dalvik and now nothing is working. no cwm to restore, can't even get to the at&t boot animation. this is a mystery.

mic.mayorga said:
followed the steps on the cwm thread. used terminal emulator. worked great. was working fine until now. i flashed kernels beta 2 and only wiped cache and dalvik and now nothing is working. no cwm to restore, can't even get to the at&t boot animation. this is a mystery.
Click to expand...
Click to collapse
Sorry to hear that. Unfortunately I can't help much at all since I haven't done either yet (CWM or Kernels/rom installations) so rather than making things worse for you, I'll leave it to the Pros here to help you. Im sure one of them will respond back soon enough.

Try this:
Disconnect the phone and pull out the battery.
Put battery back in and plug phone to a wall charger. Let it boot to the battery charging screen. Once there press and hold POWER + VOLDOWN
Depends on type of the problem, it helped me 9 out 10 times...

tried it at least 20 times now. just realized that i didn't format /system nor did i update cwm yesterday. probably the root of all these problems. I'm just gonna start fresh with the kdz. I'm on a mac though so its going to be a long night starting with boot camp.

I'm having the same problems...well kind of...
I followed all the instructions for CWM and everything went great. No real issues but had to reinstall the .img twice and then was perfect thereafter. Saw the beta 2 ROM and figured what the hey...downloaded and installed to SD Card. Used CWM/Nandroid to do a backup then installed the zip for the ROM from the sd card.
It took a matter of 10 seconds and said it was successful/done and restarted phone-got a boot loop on LG screen for about 15 minutes and finally did a battery pull-tried several times to get it into CWM with no luck and finally was able to get in-but had to plug it into the wall and wait for charging screen to show. Was able to restore and all was well until turning the phone off.
Turning off the phone now causes the phone to loop on the ATT screen-I can get into download mode and can get into CWM and restore and all is well until turning phone off.
I figured it just needs a fresh install so I've been trying to flash the kdz but the firmware updater keeps faulting and never makes it through the process...so I'm stuck...have all the files I need (I believe) and have everything in place...just can't get it back to normal.
Any ideas from here?
Thanks in advance!

Yeah, sometimes it could be quicker just start over and restore backups...
While you there, would you mind do this: Needed SystemUI.apk from SU640
[EDIT]
@fishscale28:
did you do kdz unbrick before? If not, then perhaps you are not doing it right...btw, kdz file for LU6200 didn't work for me.

Nope-never done a kdz unbrick before-I have the kdz v10i_00 for the 640. I have all the drivers installed, the parser deal installed, windows enabler program running and use the kdz updater to update the firmware. Is there something Im missing here? Seems like several people have gotten the updater to crash when trying to update the firmware...any ideas why?
---------- Post added at 05:51 AM ---------- Previous post was at 05:38 AM ----------
I went through a few of the threads and saw there was a .dll file to be deleted in the updater folders so I did that and now I can do absolutely nothing with the program. Only start and exit...am unable to select anything, view anything, get anything to function...

fishscale28 said:
Nope-never done a kdz unbrick before-I have the kdz v10i_00 for the 640. I have all the drivers installed, the parser deal installed, windows enabler program running and use the kdz updater to update the firmware. Is there something Im missing here? Seems like several people have gotten the updater to crash when trying to update the firmware...any ideas why?
---------- Post added at 05:51 AM ---------- Previous post was at 05:38 AM ----------
I went through a few of the threads and saw there was a .dll file to be deleted in the updater folders so I did that and now I can do absolutely nothing with the program. Only start and exit...am unable to select anything, view anything, get anything to function...
Click to expand...
Click to collapse
I installed from the kdz yesterday and didn't have to delete any files. I'm on Win 7 x64. The first time it ran it told me to restart my phone cause it didn't see it, but the second time it ran until my phone reboot and I killed the program. Be sure you have the KDZ_FW_UPD_EN with UpTestEX_mod2_marwin.exe in it. Hope this helps.

Thanks for your help. I did all that...again...I even deleted, reinstalled all the updater stuff, tried running as admin, tried running in compatibility mode, ran it after deleting the recommended .dll file and the option to do anything was gone, put it back in and was able to run everything fine and a little after extracting the kdz it would crash. I unplugged the phone and re-ran the proggy and it went through the check, noticed the phone wasn't hooked up and finished the check. Plug phone in, start process over and proggy crashes.
I don't get it-I would say its the wrong kdz but its not. I installed all the drivers and it still doesn't work. I've tried every combo of everything and the proggies keep crashing.
Now I was finally able to get into CWM to flash another ROM and was able to get one going-was able to boot into the os but same as before-once the phone is turned off it starts the boot loop. Now its even harder to get back to CWM but a restore works from there. Any ideas on why the boot image keeps reverting back to whatever was screwed up? Has to be something that happens once the system starts up again as it's after a restore and when the phone is turned off. Stumped and would love to be able to use my phone...It seems like flashing the kdz would be the sure fire way to get it done-are there options aside from the updaters that keep crashing?
Thanks in advance!

Maybe http://www.microsoft.com/windows/virtual-pc/ can help?

alright so i got to the 4% thing and my phone rebooted but it kept looping to the screen LG Optimus LTE bootscreen with the pink candy cane. thats it. i did vol dwn + pwr and got the android arrow and box with loading bar no text, then it rebooted back to the optimus lte screen. never got to the setup screen. tried the kdz again and my phone died. now when i plug it in i only get download mode... does it charge in download mode and why did it not get to the setup screen?!

fishscale28 said:
Thanks for your help. I did all that...again...I even deleted, reinstalled all the updater stuff, tried running as admin, tried running in compatibility mode, ran it after deleting the recommended .dll file and the option to do anything was gone, put it back in and was able to run everything fine and a little after extracting the kdz it would crash. I unplugged the phone and re-ran the proggy and it went through the check, noticed the phone wasn't hooked up and finished the check. Plug phone in, start process over and proggy crashes.
I don't get it-I would say its the wrong kdz but its not. I installed all the drivers and it still doesn't work. I've tried every combo of everything and the proggies keep crashing.
Now I was finally able to get into CWM to flash another ROM and was able to get one going-was able to boot into the os but same as before-once the phone is turned off it starts the boot loop. Now its even harder to get back to CWM but a restore works from there. Any ideas on why the boot image keeps reverting back to whatever was screwed up? Has to be something that happens once the system starts up again as it's after a restore and when the phone is turned off. Stumped and would love to be able to use my phone...It seems like flashing the kdz would be the sure fire way to get it done-are there options aside from the updaters that keep crashing?
Thanks in advance!
Click to expand...
Click to collapse
Even after running the kdz, my phone still does that after installing CWM. I don't know if it's something with my ROM or something with CWM, but if you can't get into CWM you probably don't need to run the kdz. I couldn't get into CWM anymore when I ran it.

So you're saying you go into the boot loop after turning off your phone even after unbricking?

I don't get it-now I can't get into recovery and it keeps up with the boot loop. I've tried running on the virtual PC/XP deal and it doesn't crash but now it doesn't even see the phone...reinstalled all the drivers, etc. and still no luck. Is there anyway to get the kdz installed without this updater?

fishscale28 said:
So you're saying you go into the boot loop after turning off your phone even after unbricking?
Click to expand...
Click to collapse
Yes. I don't think that was happening until I put CWM on. But I can live with it until the issue is solved. I don't think I'm the only one having it.

[Q] continuous boot loop TWRP

First of i'd like to thank the community! I've ran in to numerous issues and have been graciously saved several times.
I'll start of by providing some context in to the issue.
original configuration:
Unlocked - T-Mobile US SIM
AT&T LG E980 factory tot 4.1.2 - flashed using LG Flashing Tool
Root - E980 Universal Root
Unlocked Bootloader - Freegee [Android Marketplace]
Installed Recovery TWRP v2.6 - Freegee [Android Marketplace]
Removed bloatware - AT&T Applications
So from this point the phone was working as expected. I spent hours configuring to my liking and decided to call it a night. Before I called it quits I decided to make a backup using TWRP. Backup took a really long time but it said successful. I left handset plugged in to charger overnight, roughly 6 hours of continuous charging. When I woke up I noticed the phone was in recovery mode. Touchscreen was also unresponsive. I held the power button to allow it to reboot and it rebooted me back to recovery. At this point I knew something was wrong. I attempted to re-install backup files made from previous night, this failed. The phone booted back to recovery. I then installing some zip files I had pre-loaded on to the external SD card, this was CM10.1 and gapps files for E980. I tried this out a few days ago and it was working fine. I decided lets try installing this and see what happens. Install was successful and rebooted. The phone boots back in to recovery. At this point I'm really frustrated. I checked the memory card by running through the TWRP menu. I noticed the file sizes were unchanged but the files were not displayed on both in/ext memory. I decided to finally restore again by using LG Flashing Tool. This by the way has saved my a$$ numerous times. So the one thing I would note, at the 85% when the phone reboots I noticed there was an error, an error I've never seen before. It was a picture of sync icon (large) and android man on top of it and text that said "error 0x123456" I didn't note the exact string. I let it go and monitored the flashing tool, somewhere around 93-95% it rebooted again in to the normal boot sequence. Viola my phone is back to where I started.
So here's some of the questions I had:
How did I end up in the TWRP Recovery boot loop?
Why could I not see the files to install once in TWRP?
Why did TWRP continuously boot back in to recovery mode after successful install of restore?
Why did TWRP continuously boot back in to recovery mode after successful install of CM10.1/gapps zip?
Has anyone seen the LG Flashing Tool error I described above and does anyone have an explanation as to what happened?
Here's my theory on what happened...
My phone was on 4.1.2 as mentioned. I noticed a few times that there was a notification stating the phone had a OTA software update available. The first time I tried to update (already rooted and unlocked) the phone failed to update. The error cited that my phone was believed to be rooted. I paid no attention to this and decided to continue using. Later in the day I noticed the notification again, I opted to try again. The phone updated, or at least tried to. It kept booting in to TWRP Recovery. Nothing I could do could restore it, except flashing using the LG Tool. After experiencing this I knew to leave the OTA alone. I don't know if this is possible but somehow I think the OTA was pushed and forced through while I was sleeping allowing the phone to charge. This is the only time I've seen that behavior. Is that even possible???
Where am I now...?
Phone is restored, I opted to upgrade using the OTA before I start tinkering again. Maybe I won't mess with it at all and leave it alone at this point.

D851 T-Mobile G3

Hoping someone can help me here.
My wife has a G3 that started acting up back in September or so. It would randomly turn off and reboot, usually while not even touching it. Did some looking around and found that the Facebook Messenger app could cause some instability. Removed the app, all was good for a couple of weeks before it started again. This time, we backed everything up, did a factory reset, all was good for about a week. Reboots started again so I did a hard reset from Recovery. Booted up, everything was good again for about a week again before the reboots started up. The wife ended up giving up on it and went back to her Galaxy S3.
I've been messing around with it today. Phone has been stuck in a boot loop at the LG logo. Battery is fully charged. I followed some guides and downloaded the V10c stock firmware TOT file, dated June 20th, 2014 and LGD851_20140611_LGFLASHv160.dll and loaded them up into LGFlashTool v1.8.1. Installed fresh LG drivers on my Win7 PC, followed the flashing instructions to the letter using a USB 2.0 port (as I read somewhere that 3.0 ports have caused issues on some devices). Everything flashes 100%, flash tool reads complete, phone shows a big 3 on the screen with a blue background. Unplug and reboot the device and it's right back to a boot loop at the LG logo.
Now at one point, during the flashing process, it would boot into LG MiniOS 3.1 and I was able to choose an option (chose Normal Boot) and it would go back into the boot loop. Also, I connected it to my Ubuntu machine just to see what would happen and I received an error "Unable to mount LGE Android Phone. Unable to open MTP device", which makes sense. However, the phone itself would get to the T-Mobile logo and briefly jump into the initial setup of the phone before jumping back to the LG logo and starting over again. Connecting back to my Win7 machine, it just boot loops unless I have the flash tool running. Not having USB connected, it just boot loops.
I'm at a loss here. I can usually muddle my way through these kind of things but this one has me completely stumped. Ordinarily, I wouldn't worry much about this but she's wanting to get a new phone through T-Mobile's JUMP program and we can't do that if the phone won't even boot.
Any help would be appreciated.

Valorendk said:
Hoping someone can help me here.
My wife has a G3 that started acting up back in September or so. It would randomly turn off and reboot, usually while not even touching it. Did some looking around and found that the Facebook Messenger app could cause some instability. Removed the app, all was good for a couple of weeks before it started again. This time, we backed everything up, did a factory reset, all was good for about a week. Reboots started again so I did a hard reset from Recovery. Booted up, everything was good again for about a week again before the reboots started up. The wife ended up giving up on it and went back to her Galaxy S3.
I've been messing around with it today. Phone has been stuck in a boot loop at the LG logo. Battery is fully charged. I followed some guides and downloaded the V10c stock firmware TOT file, dated June 20th, 2014 and LGD851_20140611_LGFLASHv160.dll and loaded them up into LGFlashTool v1.8.1. Installed fresh LG drivers on my Win7 PC, followed the flashing instructions to the letter using a USB 2.0 port (as I read somewhere that 3.0 ports have caused issues on some devices). Everything flashes 100%, flash tool reads complete, phone shows a big 3 on the screen with a blue background. Unplug and reboot the device and it's right back to a boot loop at the LG logo.
Now at one point, during the flashing process, it would boot into LG MiniOS 3.1 and I was able to choose an option (chose Normal Boot) and it would go back into the boot loop. Also, I connected it to my Ubuntu machine just to see what would happen and I received an error "Unable to mount LGE Android Phone. Unable to open MTP device", which makes sense. However, the phone itself would get to the T-Mobile logo and briefly jump into the initial setup of the phone before jumping back to the LG logo and starting over again. Connecting back to my Win7 machine, it just boot loops unless I have the flash tool running. Not having USB connected, it just boot loops.
I'm at a loss here. I can usually muddle my way through these kind of things but this one has me completely stumped. Ordinarily, I wouldn't worry much about this but she's wanting to get a new phone through T-Mobile's JUMP program and we can't do that if the phone won't even boot.
Any help would be appreciated.
Click to expand...
Click to collapse
Good afternoon, my recommendation is that flashes with lg flash tool 2015. All you need is your phone updated driver installed on your pc. Further, you need to download the KDZ (firmware of your stock rom) corresponding to your model. Look at the XDA thread as do or YouTube. If you need more help, you can consult here.

cesarandres_8911 said:
Good afternoon, my recommendation is that flashes with lg flash tool 2015. All you need is your phone updated driver installed on your pc. Further, you need to download the KDZ (firmware of your stock rom) corresponding to your model. Look at the XDA thread as do or YouTube. If you need more help, you can consult here.
Click to expand...
Click to collapse
IIRC, he's talking about going back to the latest stock firmware available from LG and flashing with with @quangnhut123's flash tool.

Thanks for both of your help on this. I actually had given up on the phone for a while. The last time I flashed, it was allowing me to get into the first time setup but wouldn't let me complete setup before rebooting. So I ordered a new battery and everything is working like it's brand new. Thanks again!

M8 is unable to restart, no USB debug on, S-On, please help

Deze All
I Have the following issue:
Some days ago my phone started to act weirdly, was getting error messages of all my apps that stopped working. After some searching on the internet I thought the best would be to do a factory reset using the boot menu.
I tried recovery first but this only gave the red triangle with a red exclamation mark. Booted back up but error messages kept spamming.
So then I tried to do a factory reset in the same menu, this started out well but when the loading was done the phone was stuck on the htc-logo screen. I had it there for some hours, but without any results.
I tried this process agqin, but no other result.
I tried some things listed on forums here and there but since I have not ever put the phone in developer mode I cannot get the PC to recognize my phone.
I read somewhere to flash with my SD-card but I did not found a full tutorial on that (considering I am a noob on all this).
The phone just turned 1y old and I really need one for work and other stuff so I am also wondering if there even is a way, if there is not you can give me the hard truth and I will order a new one. But would be stupid to not have tried all the options and found out later it could be fixed easily.
Anyway thanks in advance look forward to your replies
Pieter

have you unlocked your bootloader with HTCDEV and are you able to get in to fastboot?
if so you could flash TWRP and restore with a stock backup.
if not and you aren't able to get the device to be dectected by a computer, you may have to contact HTC for a repair.

I had the exact same problem as you and I tried a million different things but then this man saved my life and came to my rescue!
http://forum.xda-developers.com/htc...tarting-correctly-tried-t3361256#post66433650
Go to my thread and do those steps as i did and get your phone back

I have hit a wall

Hello everyone, Merry Christmas!
Although I say that, I bring not so merry news. My OnePlus 7T is bricked and after trying everything I don't know where to go from here. Currently I am stuck at the:
The current image (boot/recovery) has been destroyed​phase of things and all I can do is boot into fastboot, that is it.
How did this all start? All I did was just update the phone to Android 12 with the official OTA update from OnePlus, big mistake. Worst update ever; my adaptive brightness went haywire, the brightness gets stuck at max, I couldn't receive calls, data was completely unresponsive, and the list goes on. So before the obvious downgrade method, I try a few things first:
Cycle airplane mode on/off
Reset network settings
Reset ANR
These worked for a minute on my data then right back to the same issue.
Wipe cache partition... Oh wait I had to find out the hard way Android 12 removed this option....
Wipe the phone
That fixed nothing.
Ok time to downgrade, but this is where things got tricky and I realized that maybe all my issues stemmed from me getting the wrong update from OnePlus? Although I found this out too late.
See my phone model is HD1907 which I already knew at the back of my head, but when it mattered to remember the most, I didn't catch what happened. After my update to A12, my model number changed to HD1901 which is the Indian version, and when I saw it didn't think anything of it at the time but then after all my problems it came back to me, my phone has always HD1907 so maybe this is a compatibility issue.
Anyway since I was going to downgrade anyway I thought to myself, 'since I already wiped everything, maybe I can use this opportunity to try out a ROM for A12 and see if it is just this ****ty OOS causing all these issues,' and so I did. First thing I did was unlock the bootloader, and try get TWRP on my phone. That all went fine, I booted into TWRP, flashed my zip for TWRP, then proceeded to try to boot into the OS... and the rest is history because that is as far as I got. Apparently my boot.img is destroyed and I can't boot back into TWRP anymore either, all I can do is get to fastboot.
So then I tried MSM, it won't detect my phone.... So then I tried flashing my Stock ROM through fastboot, apparently I'm missing a partition and it won't write to a critical partition either....
So where do I go from here...?

Hello I was in the exact same boat as you today same phone, same update issues, same no recovery mode, no os to boot into only greeted with fastboot mode. I have resolved it and I'm back on oos 11 good as new. I did use the msm tool it is tricky for sure at first. A critical step is installing the qualcomm drivers and then rebooting your pc. Get them here
https://androiddatahost.com/nbyn6. Be sure to reboot. It's late and I just got this thing back into working shape so I don't want to write a lot a right now. It's been a few days since this post so... If you are still stuck I will be glad to help out let me know. There is hope!

Canbeit said:
Hello I was in the exact same boat as you today same phone, same update issues, same no recovery mode, no os to boot into only greeted with fastboot mode. I have resolved it and I'm back on oos 11 good as new. I did use the msm tool it is tricky for sure at first. A critical step is installing the qualcomm drivers and then rebooting your pc. Get them here
https://androiddatahost.com/nbyn6. Be sure to reboot. It's late and I just got this thing back into working shape so I don't want to write a lot a right now. It's been a few days since this post so... If you are still stuck I will be glad to help out let me know. There is hope!
Click to expand...
Click to collapse
I too had all the symptoms after an update to OOS12, including progressively losing any semblance of booting. not even recovery and the drivers found elsewhere didn't work, and had a different name when installed and would never get detected in the MsmDownloadTool. After installing this one and rebooting, it finally detects it and installs the image of EDL mode.