I bought an Lg G2 d802 from aliexpress, the phone came rooted and with Philz touch installed.
A few days ago i decided to install a custom Rom (liquidsmooth but i don't think it's relevant), after i did the steps to install the custom rom when i rebooted the phone , on the screen appeard that error (690) fastboot has started.
I couldn't do anything so i decided to restore stock firmware, i thought the first version i installed wasn't the right one because the touchscreen was not working properly so i tried different one but still the same behavior.
Everything else on the phone seems to work but i can't write. I can't select anything the normal way , but i found a pattern to do things.
Basically when i place my finger on o part of the screen it actually senses the touch on another part of the screen.
Any thoughts on how this can be fixed ?
Related
This is almost embarrassing to post, but I need some help...
I have the T-Mobile G2, btw, which was rooted and with TWRP 2.6.3.3
So I was installing an AOSP ROM, and like a dumbass, instead of installing gapps like I meant to do, I accidentally flashed Smikey's KitKat ROM on top of Cyanfox. I realized it too late to stop it, and once the flash finished, I did a wipe of everything but internal storage and tried to restore a backup of CloudyStock. When I rebooted it goes to the LG screen with a secure boot error, and then a black screen where you can still see the backlight if you tilt the phone.
I tried using the LG Mobile Support tool to go back to stock, (It will go into download mode), but I can't get it to push any of the three stock images to the phone.
Holding down and power to do a hardware reset doesn't work either.
Help!!!
I picked up a cheap Tmobile prepaid to use until I get this figured out, but I want my G2 back! Does anyone have any advice at all, or did I brick my phone beyond repair?
I forgot to mention, I'm not sure if it's the phone or the drivers aren't properly installed on my computer, but LG Mobile support tool is reading my phone as a V500...
http://forum.xda-developers.com/showthread.php?t=2010624
Anyone know if this method for unbricking the Optimus G will work?
So hello, i've got a D806, and installed CloudyG3 1.3 ROM and it worked like a charm.
So i went further and started tweaking this ROM and adding stuff, and reached the point where i wanted to place the G3's Keyboard due to its resize function. I ended founding Cloudyfa's G3 Ported Keyboard and i supposed it would work perfectly (Being both ROM and Keyboard from same developer), Yet, i went for the APK installation and opened it.
1- Loads up and shows my model (D806) perfectly
2- Backup current
3- Install New & Reboot
When i rebooted, the home wouldnt stop crashing (And therefore not starting up), and i managed to open the recent-apps window, wich resulted in the systemui crashing, and rebooting the phone. It ended up breaking the ROM (The phone never booted totally, it just kept with the LG startup icon moving endlessly) and i had to go into TWRP and Re-flash the ROM to fix back up everything. (When i could load up again the keyboard screen sensor was not good and i couldnt touch the bottom keys, so i restored the backup i did and it worked great back again).
I wanted this keyboard and i certainly dont want to go back throught all the steps of re-customizing my ROM back, so how can i make this with no risks (or the least possible)?
Geetz
HyPeXeLeD said:
So hello, i've got a D806, and installed CloudyG3 1.3 ROM and it worked like a charm.
So i went further and started tweaking this ROM and adding stuff, and reached the point where i wanted to place the G3's Keyboard due to its resize function. I ended founding Cloudyfa's G3 Ported Keyboard and i supposed it would work perfectly (Being both ROM and Keyboard from same developer), Yet, i went for the APK installation and opened it.
1- Loads up and shows my model (D806) perfectly
2- Backup current
3- Install New & Reboot
When i rebooted, the home wouldnt stop crashing (And therefore not starting up), and i managed to open the recent-apps window, wich resulted in the systemui crashing, and rebooting the phone. It ended up breaking the ROM (The phone never booted totally, it just kept with the LG startup icon moving endlessly) and i had to go into TWRP and Re-flash the ROM to fix back up everything. (When i could load up again the keyboard screen sensor was not good and i couldnt touch the bottom keys, so i restored the backup i did and it worked great back again).
I wanted this keyboard and i certainly dont want to go back throught all the steps of re-customizing my ROM back, so how can i make this with no risks (or the least possible)?
Geetz
Click to expand...
Click to collapse
have you tried manually installing the files as suggested in the keyboard mod thread?
you have a backup so no harm in trying right?
Yeah ive got the backups.. i will try it when i feel ready to spend hours tweaking my phone again... (or i will backup 100% with twrp)
Yeah it's a pain when getting one thing to work means redoing everything else.
Best of luck.
Hey,
I've messed up my phone many times before but I usually find my way and end up fixing it. This time, I have no idea.
I got a new refurbished LG G2 in the mail after my old one had completely broken down and Rogers honored their warranty and sent me a replacement. This replacement took a while and I became an iPhone guy for a bit (about a month). Usually there aren't much options for the D803 but this time I seen the new 5.0 Lolipop Resurrection Remix for D803 and having been away from andriod for so long I wanted the latest and greatest features so I blinded installed it (after rooting using towelroot and installing recovery through AutoRec). I used TWRP to flash the ROM and then GAPPS right after. When the phone restarted it would pass the LG boot logo but got hung on the Resurrection Remix boot logo for quite some time. I let the phone sit for a few minutes and it finally went to the setup page of the ROM. I input everything and being worried that this would happen again when I restart my phone, I used Flashify to flash a 4.4.4 ROM because I thought it was the 5.0 ROM that was causing the problems. The phone still hangs sometimes. So I thought I would go back to stock using LG Flashtool and a D803 Kdz. (which I've done numerous times before). I then realized that whenever I connect my phone to my computer, it doesn't recognize it at all. (makes no noise, but it charges). The phone doesn't prompt me to select which method I want to use for my usb connection either (usually it asks if I wanna use it just to charge, MTP, tether, etc).
I realized I probably did a couple of things wrong here and I was wondering if anyone knows where I would start to get my G2 back to working order. (I hate using the iPhone)
Any help
Same probem here, i read in other post that it's a problem on boot image, i don't know i kdz tool can be the cause but after that i got back stock firmware doesn't work.
here my post http://forum.xda-developers.com/lg-g2/help/usb-otg-t3012311
About 6 months ago I bricked my lg g2 and bought a new one and was able to root it and added a custom rom. I then was actually able to fix my old phone and gave the new one to my wife and then I had to redo the phone and now there are bad spots on the screen. When you hit home it doesn't do anything and when you try to type a text and hit a certain letter it'll show one of the other letters around it, so you have to keep rotating the phone to get it work. She has different phone now, so I reset it to factory settings, but it still is messed up, I was able to root it with stumproot and installed twrp (which was very hard because where you swipe is the bad spot). I installed cloudystock 2.7 and the spots are still dead. I'm just curious if installing a custom rom could have messed with the digitzer or if it actually went bad.
If it worked fine before messing with custom roms, then it likely got messed up from one of the roms you flashed. I can't believe you bought a new one and immediately rooted and flashed a custom rom on it...one would think that you learned you lesson from the first time...
I find it hilarious how people think custom roms are somehow better than stock since most are pure garbage with terrible performance and reliability - if they don't brick your phone...
Tot back to stock and if it still has the spots, then it's almost certainly a hardware issue and you'll need a new screen/digitizer.
First off, this wasn't the first time I've done this before. I've rooted all my phones and put custom roms on them and got a hold of a bad one that messed it up. I was just curious if a ROM could do that. I didn't see any issues with installing a custom ROM on a phone that I just got, like I said before this wasn't the first time I've done.
Hey everyone,
I have been looking around online for several days now, but haven't been able to find a description of the problem I have with my n910f nor a solution.
When I got the phone it was stuck in bootloops and so I though it was soft bricked.
After I installed the custom rom and the latest version of TWRP via Odin, I thought that the problem was fixed, because the phone booted and I was able to start the configuration of Android (where it asks you for language, time zone etc.)
However, the phone turned itself off during this process. So I wiped everything and tried again, the same thing happened.
I then flashed it with Lineage, but it would turn itself off even before the logo appeared.
Then I flashed it with Ressurrection ROM, but again, the phone turns itself off during booting.
I can access download and recovery mode without any problems, I can flash roms and Odin works like a charm. I also used 2 different batteries.
Does anyone has an idea what I could try? Could it be the version of TWRP I am using (3.0.2.0)? Or is it a hardware issue?
Thank you!!
Hi, I have this exact same issue with my N910T and so far haven't found a solution to this. I really love my Note 4 so I'd like to know if this issue can be solved or not. I event went to a supposed repair shop and they couldn't figure out the problem, guess they weren't that good.
Sorry to hear this.
I have found issues that seemed similar, but not quite the same, and people hinted that it could be a worn out motherboard that is causing this top happen. But before I open up the phone (at the potential risk of breaking at least the screen) I would try everything else.
Or is there a way to test whether the motherboard is defective?
Its the plague of overheated, worn out emmc memories, sadly. Once it happen,the only way is a new/used motherboard,prefferably C model.
eMMC failure, snapdragon models are susceptible to this.
Tüddels said:
Hey everyone,
I have been looking around online for several days now, but haven't been able to find a description of the problem I have with my n910f nor a solution.
When I got the phone it was stuck in bootloops and so I though it was soft bricked.
After I installed the custom rom and the latest version of TWRP via Odin, I thought that the problem was fixed, because the phone booted and I was able to start the configuration of Android (where it asks you for language, time zone etc.)
However, the phone turned itself off during this process. So I wiped everything and tried again, the same thing happened.
I then flashed it with Lineage, but it would turn itself off even before the logo appeared.
Then I flashed it with Ressurrection ROM, but again, the phone turns itself off during booting.
I can access download and recovery mode without any problems, I can flash roms and Odin works like a charm. I also used 2 different batteries.
Does anyone has an idea what I could try? Could it be the version of TWRP I am using (3.0.2.0)? Or is it a hardware issue?
Thank you!!
Click to expand...
Click to collapse
I suggest flashing stock rom with Odin after wiping your whole device in TWRP. I've had the same thing about 2 months ago.
Hey,
thank you for your responses. Yes, I read a lot about it being a motherboard problem.
I got it to work now thanks to this post: https://forum.xda-developers.com/note-4/general/downgrade-official-mm-to-kitkat-t3383885
First nothing happened, but after I flashed Modem and the original Bootloader again (after installing the rom) the phone turned on and I was able to use it for a while (20mins maybe). Then suddenly it turned itself off and stayed on the "Samsung Galaxy" screen for a long time.
Apparently a lot of people are using Wakelock and it seems to be working for some of them, but that seems to defy the point somehow.
KirbyFan64 said:
I suggest flashing stock rom with Odin after wiping your whole device in TWRP. I've had the same thing about 2 months ago.
Click to expand...
Click to collapse
Which Stock Rom did you use exactly? Is your phone working fine?