Hello everyone,
*
I have a little (big) issue with my LG G2 (International D802). Everything was fine until I decided to change rom ( the stock is nice, but has micro lags ). So I decided to change and move to the Carbon rom (nightly) .
*
But the phone battery life was not as good as before, and there was some missing features (complete LG Quickwindow support for exemple)
*
Then, I decided to test cyanogenmod , especially to see if the battery life is better . And then I did something wrong : I started the stock rom recovery (there was an old backup on my phone) .
*
I realized at the end, and the recovery did completely fail , leading to a bootloop .
*
I finally managed to get booting to the stock rom with a .kdz flash using LG FlashTool software.
However, the phone is no longer stable at all: the wifi is slow, it does not detect my sim card , and most importantly, the phone crashes regularly (~ every 5 minutes). I'm unable to access files from windows ( but the phone is detected, just not visible in the explorer) .
*
I also tested the rom 4.4 SFR (France) : no more crashes (at least much less) , but sim card and LG applications do not work.
*
I also managed to get in TWRP recovery : When I turn on the adb sideload function, the transfer is successful, the installation completes without any problems (although I feel it is really quick - I tested Carbon and Cyanogenmod -) but in the end the system refuses to boot ( freeze on the boot animation)
*
In your opinion, is it recoverable?
*
Thanks!
Kakawada said:
Hello everyone,
*
I have a little (big) issue with my LG G2 (International D802). Everything was fine until I decided to change rom ( the stock is nice, but has micro lags ). So I decided to change and move to the Carbon rom (nightly) .
*
But the phone battery life was not as good as before, and there was some missing features (complete LG Quickwindow support for exemple)
*
Then, I decided to test cyanogenmod , especially to see if the battery life is better . And then I did something wrong : I started the stock rom recovery (there was an old backup on my phone) .
*
I realized at the end, and the recovery did completely fail , leading to a bootloop .
*
I finally managed to get booting to the stock rom with a .kdz flash using LG FlashTool software.
However, the phone is no longer stable at all: the wifi is slow, it does not detect my sim card , and most importantly, the phone crashes regularly (~ every 5 minutes). I'm unable to access files from windows ( but the phone is detected, just not visible in the explorer) .
*
I also tested the rom 4.4 SFR (France) : no more crashes (at least much less) , but sim card and LG applications do not work.
*
I also managed to get in TWRP recovery : When I turn on the adb sideload function, the transfer is successful, the installation completes without any problems (although I feel it is really quick - I tested Carbon and Cyanogenmod -) but in the end the system refuses to boot ( freeze on the boot animation)
*
In your opinion, is it recoverable?
*
Thanks!
Click to expand...
Click to collapse
i would kdz again. it sounds like it did not install properly the first time making sure its the exact same kdz file you need. i have had to kdz more than once in the past for it to install properly.
http://forum.xda-developers.com/showthread.php?t=2432476
you can also try redownloading your kdz, might have had a bad dowload
XxZombiePikachu said:
you can also try redownloading your kdz, might have had a bad dowload
Click to expand...
Click to collapse
that 2
gentlemandroid17 said:
i would kdz again. it sounds like it did not install properly the first time making sure its the exact same kdz file you need. i have had to kdz more than once in the past for it to install properly.
http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
XxZombiePikachu said:
you can also try redownloading your kdz, might have had a bad dowload
Click to expand...
Click to collapse
Thanks for the answers.
I tried flashing the kdz several times.
I tried 2 kdz: one with kitkat, and the other with jelly bean.
I'm sure that the jelly bean kdz is working, because I flashed it when I got the phone (Hong Kong Rom -> Europe Open)
I'll try the Kitkat Europe Open kdz when it will be available.
Okay... my phone is still buggy, I think the EFS is damaged. Is it possible to repair it ? (found backup and restore but not repair)
Related
I tried to load old stock of LG E400, however, it gave me some error at final stages. Now, the phone is working except two issues:
1: The USB is not working at all, neither for charging not for data transfer i.e. the phone is not detected on computer.
2: The graphics are not good as it should be. I guess its operating at 8bits or so.
I tried Voume Down, Home key and power, but no help by resetting it to default.
I tried Volume Up, Home and power, but i don't know how to proceed once it shows notice screen. I am not sure how to proceed or restore a new stock ROM or load a custom ROM since the recovery is not installed nor the device is rooted.
The current ROM is V10b.
Please help!
amjadakmal said:
I tried to load old stock of LG E400, however, it gave me some error at final stages. Now, the phone is working except two issues:
1: The USB is not working at all, neither for charging not for data transfer i.e. the phone is not detected on computer.
2: The graphics are not good as it should be. I guess its operating at 8bits or so.
I tried Voume Down, Home key and power, but no help by resetting it to default.
I tried Volume Up, Home and power, but i don't know how to proceed once it shows notice screen. I am not sure how to proceed or restore a new stock ROM or load a custom ROM since the recovery is not installed nor the device is rooted.
The current ROM is V10b.
Please help!
Click to expand...
Click to collapse
graphic error is sometimes because of firmware incompatibility with new released phone if im not mistaken
about your phone not detected
have you ever tried to uninstall the driver then reinstall and make sure that you enable usb debbuging
and if the debbuging works then i suggest you upgrade to other latest firmware because v10b is too old
Thank you for replying. I did tried uninstalling and installing, it did not help. However, I tried flashing 10E and it helped in fixing the USB issues. However, my graphics still not fixed, even i tried installing a custom ROM but still graphics are not fixed
EDIT: V10F fixed the graphics problem in the stock ROM however, in the custom Rom, its still not working. Trying V10H stockrom and trying to install the custom ROM to verify.
jsarunotres said:
graphic error is sometimes because of firmware incompatibility with new released phone if im not mistaken
about your phone not detected
have you ever tried to uninstall the driver then reinstall and make sure that you enable usb debbuging
and if the debbuging works then i suggest you upgrade to other latest firmware because v10b is too old
Click to expand...
Click to collapse
The spectrum and other rooting hacks for LG - E400 only works upto V10C stock rom.
amjadakmal said:
The spectrum and other rooting hacks for LG - E400 only works upto V10C stock rom.
Click to expand...
Click to collapse
you should trying with v10n t-mobile
htn2205 said:
you should trying with v10n t-mobile
Click to expand...
Click to collapse
May I get the link for the v10n, please.
amjadakmal said:
The spectrum and other rooting hacks for LG - E400 only works upto V10C stock rom.
Click to expand...
Click to collapse
I have LG-E400f-V10f as a baseband version, and I rooted successfully with spectrum.
@amjadakmal, what error did you receive in the final stage of KDZ-Flasher?
What version of KDZ-Flasher are you using?
Hi guys
first, I apologize for my english
Two week ago, I has get started try KK mod on my device.
I encountred several problems, (the biggest was http://forum.xda-developers.com/showthread.php?t=2582142) but all successfully overcome...
...but last week,i had this new problem that seems to affect only my device ... in the world!
1 - Knock-ON has completely stopped functioning (but knock-OFF works perfectly!!!)
2 - five millimeters of the display (right side) does not respond to commands (following a perfectly straight vertical line, including nav-bar and status-bar)!!!
I tried to:
1 flash another ROM (stock, aosp, cm)
2 upgrade/downgrade with FlashTool
3 back to factory stock by LGMobile Support Tool -> options -> resolution update problems
4 upgrade/downgrade by flashing
5 all the recovery
6 all kind of advanced wipe
7 changing kernel (stock, stock-mod and mod)
8 sensor calibration
9 all the test in the hidden menu
...and more
NOTHING
Question: What do you think about flash manually all partitions?(http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware/10b_EUR_16G_partitions)
if this is a good idea, how I can flash, for example, tz.img or primaryGPT.img etc? What are their locations? I have to use the command fastboot or flashing by including the .img file in a .zip archive?
thank you all, my hopes are in your hands!:angel:
Hello, I flashed my S7710 ( skoomer, galaxy xcover 2 ) with CM 10.2. Everything was perfectly fine. Unfortunately, one night I had to have a fatal error during sleep as Android ( app ).
My phone was turning on and off during charging and while connected to pc. I solved it and flashed it once again. It was unstable and crashed few times so I flashed an original ( firmware ) ROM.
Unfortunately, I still got this screen (attached) after turning my phone on. ( just for 3-4 secs ) It disappeares and phone boots normally ( almost because I got small lags during booting, both sound and animation ), starting with samsung logo. Got similar f*ck-ups while getting to recovery but it's not permanent and overall I get to the destination point which is recovery menu.
I would like to know, what should I do with this. Can't find three files rom to this model. ( with pit to re parition it - don't know if it will help but still worth to try ) . I've done all wipes etc. I flashed everything with odin, except CM 10.2 witch had to be installed from recovery.
What's more, this gray-like screen changes a bit if there is another ROM. What I mean is that there are more colorful pixels in the background now that there were on CM 10.2 .
i had the exact same problem. The problem is solved by flashing via odin a stock rom with pitfile and csc file, too. Unfortunately for my device, althought i fixed that error, i lost the touchscreen response. Dont know if it's a software error or a hardware one. If you're still looking i could find it.
After having had a 1 month experience with the rom pixel experience I wanted to return to the rom stock of miui by downloading it from the official pages, I installed them normal as I would with a custom rom (clean installation) but at the time of starting the system at load the first steps and the different configurations the fps drops appear on the screen and it is blocked for 5 to 10 seconds.
I would like to know if I am doing something wrong and I need your help to return to the rom stock and that it works smoothly as before.
Thanks :'(
Download Mi flashtool and fastboot rom.
Here a good how to
https://in.c.mi.com/thread-714161-1-0.html
alejandr769 said:
After having had a 1 month experience with the rom pixel experience I wanted to return to the rom stock of miui by downloading it from the official pages, I installed them normal as I would with a custom rom (clean installation) but at the time of starting the system at load the first steps and the different configurations the fps drops appear on the screen and it is blocked for 5 to 10 seconds.
I would like to know if I am doing something wrong and I need your help to return to the rom stock and that it works smoothly as before.
Thanks :'(
Click to expand...
Click to collapse
As said by the other member (joke19), the best solution is to use the mi tool so as to bring the phone back to its original condition, certainly one of the partitions (probably The vendor partition or persist) (it's just a guess) but ... did you install the latest firmware available in the version of the rom that you then installed?(you said you did a clean install, which means formatting sistem data cache vendor ... And then before installing the new rom reinstalled the Appropriate firmware ...) Personally only once did I return from custom to MIUI (not MIUI stock, however, and at the time I lost the IMEI despite all the correct steps) but it was a long time ago However, these are things that can happen even when you switch from one custom to another, even if one does all the steps. Correct "formatting" from twrp is never a formatting Really clean ... only from fastboot or using the xiaomi tool you usually have a Complete formatting And I would like to underline COMPLETE because in twrp only some partitions are cleaned and this can sometimes lead to small problems
Few days ago, while tinkering with my yu+, i decided to roll back to aosp kitkat (which came preinstalled). The ygpd flash was ok, except for the fact that my screen was all black (phone booted) and there was no yu logo. As usual, i booted to fastboot and flashed cm12.1. Booted, everything went fine only to notice that touch was not working properly. If i touched up it would register down. The main interesting thing was that, if i rebooted, the touch would work fine but as soon as i pressed the power button, it would malfunction. Same issue in twrp too.
These things mentioned below are the methods i tried to fix:
1) Flashing stock rom through YGPD again
2) Flashing stock rom through bootloader
3) Flashing rom through QFIL
4) Flashing stock touchscreen config though GptAdb Tool -reference link: https://forum.xda-developers.com/t/guide-fix-yureka-ao5510-touchscreen-calibration-issue.3488017/
As all hope was lost, i decided to contact our fellow hard working dev @abhishekt295
Back to the GptAdb tool, we tinkered and experimented all day, and found out that for some reason my yureka+ had the touch panel from "each" vendor, which comes with the yureka (AO5510), while the + variant( YU5510a) has the vendor "ofilm". They both have different values in their cfg.
Note: Check your touch firmware version in /sys/devices/virtual/touchscreen/touchscreen_dev/firmware_version file.
There are three vendors which are:
1) Each:GT970:0x1039
2) Ofilm:GT970:0x1039
3) Boen:GT970:0x1039:0x48
This post is applicable to those who have firmware version Each:GT970:0x1039
@abhishekt295 modified the cfg file, i flashed through gpt tool and DONE! My touch was back to normal.
Below is link for the modified cfg by @abhishekt295. You can find the tool and instructions in the reference link above, just be sure to use the cfg given here.
Link: https://androidfilehost.com/?fid=7161016148664782334
Endnote: While my device is working again, i would like to thank abhishek for his continuous efforts all day long. I gave up hope for my device, and was going to shell out money for new panel, but he didn't gave up and in the end fixed the issue. All credits to him.