Dears, I hope someone has any idea about what I can do...
Yesterday I had the G6 with fulmics ROM installed. I tried to make a factory reset with TWRP to clean everything was fine but I was not able to get out of the recovery. I was stuck in a recovery bootloop...
I tried this command from another thread:
Code:
dd if=/dev/zero of=/dev/block/platform/soc/624000.ufshc/by-name/misc
and I was able to get out of recovery, but now I was stuck at bootloop with the message "Your device is corrupt"
I let the battery discharge completely then I pressed UP button and inserted USB to my PC and I was in Download Mode.
With LG UP and Uppercut I loaded the image of the stock firmware I was having before and now the G6 is booting correctly when I have no SIM card inside.
If I put the SIM Card the process com.android.phone stops working continuously and I cannot have network connection...
I browsed the phone informations without SIM Card and I still have the correct IMEI inside but, the IMEIsv is 00 and the S/N of the phone is empty...
So, do anyone have any idea of what I can do to have it working back again?
I cannot unlock the bootloader again because the unlock.bin is related to the IMEI and S/N and one of them is gone....
Authorized service should repair it free of charge. By the way, tempering with S/N etc. is illegal and not supported by this community.
oh good, I was thinking I destroyed it completely. Tomorrow I will bring it to the LG service. Thank you!
Related
Hello
I have an LG G2 D802 that was working perfectly but some days ago, after a crash with broken screen the phone suddenly show the message "Service Disabled" and the code *#06# returns IMEI Null.
By the time of the crash it was kit kat, and I made a factory reset that did not solve the problem. After that I use LG Flash tool to install the lollipop 5.0.2 rom, but the problem remains.
Then I took a lot of time trying to understand the problem and I found out that it could have a EFS backup, but in fact I didn't have one.
The next thing was root the device (it is allready out of warranty) and use alternative tools. I have tried to rewrite the IMEI I have in the box with QPST , Qualcomm NV tools and did not work.
- QPST (2.7.4.11) works and shows the device but doesn't work the Backup QCN (To get QPST to show the device I needed to apply this with adb shell - http://forum.xda-developers.com/lg-...ct-g2-d800-t3175064/post62250384#post62250384, but it works and shows the phone in the ports list);
- RF NV manager returns and error "NvManager::getNvItemsFromPhone( const string comPort ) - QpstServer::sendSyncImpl - Bad response from phone (DM packet commands 19-24)";
- Qualcomm NV tools works and reads the device, then I write ESN, MEID and IMEI with good confirmation messages, but when I rebbot it remains with Null IMEI.
By this time I am in the search for more wise help and experience.
I also have "Unknown Baseband", and by reading some threads I thing the problem is that the phone has Null IMEI and the tools are unable to writr data to partitions. The only way is to write NV1 and NV2 by dd command into mmcblk0p10 and mmcblk0p11.
The phone works perfectly in all aspects (sensors, camera, wifi, screen) except for the phone signal "service disabled" with an X above the 4 signal bars. I gess it is not a hardware problem
I am struggling with this because it is a very nice device, and I need to bring it back to life before replacing the broken screen.
Any help?
thanks
aquelhas said:
Hello
I have an LG G2 D802 that was working perfectly but some days ago, after a crash with broken screen the phone suddenly show the message "Service Disabled" and the code *#06# returns IMEI Null.
By the time of the crash it was kit kat, and I made a factory reset that did not solve the problem. After that I use LG Flash tool to install the lollipop 5.0.2 rom, but the problem remains.
Then I took a lot of time trying to understand the problem and I found out that it could have a EFS backup, but in fact I didn't have one.
The next thing was root the device (it is allready out of warranty) and use alternative tools. I have tried to rewrite the IMEI I have in the box with QPST , Qualcomm NV tools and did not work.
- QPST (2.7.4.11) works and shows the device but doesn't work the Backup QCN (To get QPST to show the device I needed to apply this with adb shell - http://forum.xda-developers.com/lg-...ct-g2-d800-t3175064/post62250384#post62250384, but it works and shows the phone in the ports list);
- RF NV manager returns and error "NvManager::getNvItemsFromPhone( const string comPort ) - QpstServer::sendSyncImpl - Bad response from phone (DM packet commands 19-24)";
- Qualcomm NV tools works and reads the device, then I write ESN, MEID and IMEI with good confirmation messages, but when I rebbot it remains with Null IMEI.
By this time I am in the search for more wise help and experience.
I also have "Unknown Baseband", and by reading some threads I thing the problem is that the phone has Null IMEI and the tools are unable to writr data to partitions. The only way is to write NV1 and NV2 by dd command into mmcblk0p10 and mmcblk0p11.
The phone works perfectly in all aspects (sensors, camera, wifi, screen) except for the phone signal "service disabled" with an X above the 4 signal bars. I gess it is not a hardware problem
I am struggling with this because it is a very nice device, and I need to bring it back to life before replacing the broken screen.
Any help?
thanks
Click to expand...
Click to collapse
Today I tried this method with adb shell, to make sure Qualcomm NV tool writes IMEI to the phone...
setprop sys.usb.config diag,adb
ls -al /dev/block/platform/msm_sdcc.1/by-name
dd if=/dev/zero of=/dev/block/mmcblk0p10 (no space left on device)
dd if=/dev/zero of=/dev/block/mmcblk0p11 (no space left on device)
dd if=/dev/zero of=/dev/block/mmcblk0p16 (no space left on device)
Can anyone tell me why the "no space left on device" occurs?
Thanks
Hello!!!
First sorry for my poor english!
I think that you have a bad connection after crash!!!!
1. Remove the Backcover of your phone.
2. Remove the backplastic on upper part of phone using screw driver.
after remove back cover and upper plastic
3. Remove Battery Connector.
4.Remove all connectors except camera connector, Proximity sensor and face camera
After removing connectors
6.Reattach all connectors! Firmly press all the connectors
7.Reattach battery connector!!
Et voilĂ*!!! This is a way I do after losing IMEI and Baseband! IMEI: null and baseband should be implemented!!!
I had tried most method to fix but nothing happens,
Hope to help you!
aquelhas said:
Hello
I have an LG G2 D802 that was working perfectly but some days ago, after a crash with broken screen the phone suddenly show the message "Service Disabled" and the code *#06# returns IMEI Null.
By the time of the crash it was kit kat, and I made a factory reset that did not solve the problem. After that I use LG Flash tool to install the lollipop 5.0.2 rom, but the problem remains.
Then I took a lot of time trying to understand the problem and I found out that it could have a EFS backup, but in fact I didn't have one.
The next thing was root the device (it is allready out of warranty) and use alternative tools. I have tried to rewrite the IMEI I have in the box with QPST , Qualcomm NV tools and did not work.
- QPST (2.7.4.11) works and shows the device but doesn't work the Backup QCN (To get QPST to show the device I needed to apply this with adb shell - http://forum.xda-developers.com/lg-...ct-g2-d800-t3175064/post62250384#post62250384, but it works and shows the phone in the ports list);
- RF NV manager returns and error "NvManager::getNvItemsFromPhone( const string comPort ) - QpstServer::sendSyncImpl - Bad response from phone (DM packet commands 19-24)";
- Qualcomm NV tools works and reads the device, then I write ESN, MEID and IMEI with good confirmation messages, but when I rebbot it remains with Null IMEI.
By this time I am in the search for more wise help and experience.
I also have "Unknown Baseband", and by reading some threads I thing the problem is that the phone has Null IMEI and the tools are unable to writr data to partitions. The only way is to write NV1 and NV2 by dd command into mmcblk0p10 and mmcblk0p11.
The phone works perfectly in all aspects (sensors, camera, wifi, screen) except for the phone signal "service disabled" with an X above the 4 signal bars. I gess it is not a hardware problem
I am struggling with this because it is a very nice device, and I need to bring it back to life before replacing the broken screen.
Any help?
thanks
Click to expand...
Click to collapse
What should I do? If the same problems on RF NV manager got the same error. bad response from phone. How do i fix it?
Wow! What a coincidence!
I also have a LG G2 (D802) and the EXACTLY SAME problems!
Background:
It's been about a year since I am on Lineage OS 14.1.
Since 6 months ago, I started having issues with my antenna. Sometimes, antenna bar got empty and sometimes I couldn't get 3G signal on locations that I had before (and others had with no problem)
Fast forward 3 months ago and one day my phone couldn't detect sim card and IMEI was vanished. I had to restart it few times to make it come again.
And a month ago, I dropped my phone and screen shattered, Exactly Like you. After changing broken LCD with new one, and also a new battery, I couldn't get sim card detected anymore, No matter how much i restarted the phone.
IMEI was null and no baseband version was showed on about page. Also back of the phone (under camera started to get suspiciously hot.
I started applying pressure to different parts and sometimes phone hanged and restarted and maybe one in 20 times I could get antenna and sim card back.
Things I've done and their result:
Opening the phone numerous times and checked the connectors and unplugged/plugged them: nothing changed
Flashing back to stock (found lollipop kdz and flashed it via lg flashtool): nothing changed
Flashing Radio (Some images were available on XDA): nothing changed
Restoring ROM to an old backup I had (year ago): same as above
Trying to use QPST/NV Tools: They cant talk to modem.
Showing the phone to some repairmen: they cant talk to modem to set the IMEI either.
Still, sometimes by applying pressure to phone randomly, the IMEI comes back, which prevents me to cut hope and drop the phone into trash!
I would really love to know your result! were you able to fix it?
euphoria360 said:
Wow! What a coincidence!
I also have a LG G2 (D802) and the EXACTLY SAME problems!
Background:
my phone couldn't detect sim card and IMEI was vanished. I had to restart it few times to make it come again.
And a month ago, I dropped my phone and screen shattered, Exactly Like you. After changing broken LCD with new one, and also a new battery, I couldn't get sim card detected anymore, No matter how much i restarted the phone.
IMEI was null and no baseband version was showed on about page. Also back of the phone (under camera started to get suspiciously hot.
I started applying pressure to different parts and sometimes phone hanged and restarted and maybe one in 20 times I could get antenna and sim card back ...
Click to expand...
Click to collapse
How to Fix LG G2 no IMEI and not detecting SIM Card!
After I posted this reply here, I found a solution on some other topic about how to fix LG G2 WiFi issue. He opened the phone, and applied constant pressure (by putting a tape between WiFi chip and Metal Cover).
And I thought maybe my problem is similar too. So, this is the things I've done:
Download the Service Manual for your phone model. you can find it on Internet. Here is the one for LG G2
Look at the Service manual and find the chipsets related to IMEI/Service Issue. Usually they classify board components based on their common issues. For example, in G2 service manual, in pages 38 and 263, you can see this info.
For LG G2, The chips/IC's related to IMEI and Service were: U2003 (Bypass Booster), U2002 (WTR1605L), FL1014 (B3 DPX), U1101 (SP4T B7), FL1015 (B2/B3 Filter), FL1010 (DPX B20), U1005, U1000, U1001, U2002.
Most of these parts are under a metal shield which can be easily unmounted and mounted back on.
Make a thick piece of Tape and put it between the chips and the metal cover. The goal is to apply pressure to them to stick to the board.
Put the metal cover back on and close assemble the board. Done!
In my case, it worked, although after lots of repair men simply rejected my phone, I fixed it with just a little tape. Now, the IMEI is back, SIM Card is detected the moment phone is on, and I guess the phone consumes less power, since it doesn't get hot anymore.
Why this works? Well when you use your phone for a long time and it undergoes a of of heat/cooling cycle, the pins of some of these chips that tend to get hot, become a bit loose and get disconnected from the board. by doing above instructions you simply push them back.
Hey guys, my device lost it's IMEI number when the battery died. When i check with *#06# i get a message with "null" on the screen, and i constatly get a popup that the LG keyboard has stopped. Is there anything i can do to get the phone working again? Just to mention my phone is not rooted.
Thanks
Edit: when i tried to put the phone in download mode i get boot sertification error and my phone is recognized as storage device with two folders called "image" and "verinfo" on device manager it's recognized as "LGE AndroidNet USB Serial Port" How can i restore download mode? :/
try this: http://en.miui.com/thread-245598-1-1.html
I somehow managed to boot it in download mode via "QPST" and reflash the stock ROM, but i have a wierd bug, everytime my battery dies or i turn off the phone the IMEI get lost again and i have to flash the ROM to get the phone work again... If anyone know how to fix thiss issue let me know
Thanks
Hi everyone
The last week i updated OTA nougat on my lenovo k6 note, and after that i lost my connectivity (4g/3g etc).
To try to restore my phone i downgraded (flashed) 2 stock firmware:
- a wrong stock rom ( lenovo k6 k 33 my mistake...)
-After that i flashed a correct version K53_S123_170216_ROW_QPST via qfil, and then i manage to recover the dual SIM IMEI (just typin the IMEI number in my k6 note box) with this tool (qualcomm-smartphone-write-imei-tool-v1.01) via diagnostic menu , but the connectivity wasn't restored completely.
- In about device it says : Baseband JO.1.2.c2-00099-8937 unknown.
-The Sim 1 detect 4g but i can't enter to internet and it can't make calls. but it can receive calls and SMS.
-Same as for SIM 2, it can receive SMS but can't make calls.
I tried to do the following:
-Re flash stock firmware, and make a hard reset (didn't work)
-i made a xQCN backup from other k6 note, and i reflashed with qpst and changing the IMEI didn't work.
I don't know what else do
Thanks in advance for your answers.
Sorry i cant help you but let me tell you what i did when i faced almost the same problem.
I am a lenovo k6 power user (k33a42). After upgrading my stock rom to latest nougat update through OTA my device went into bootloops. Unfortunately i had no backups so i reflashed the stock rom. The device started working again but then i found out that both of my SIMs were not working (No sim indication, no IMEI number, no network). Tried everything i could but later decided to give it to the customer care as it was still in warranty. It took them 4 weeks (4 WEEKS!!!) to fix the device and later told me that the motherboard was faulty. So if no methods work out for you, my only advice is to go to the customer care if you still have the warranty.
yes, i still have warranty, but first i need to know how re lock my bootloader before giving it to customer care .
Thanks for the reminder i didn't consider that option.
Oh thats simple if you have proper drivers (ADB & FASTBOOT) installed.
Just boot your device into fastboot mode. Connect it to the PC and type this code in cmd:
"fastboot oem lock" and press enter (without quotes)
The device may restart but if it doesn't just type this code:
"fastboot reboot"
If everything goes fine, reboot the device to bootloader again and check the bootloader status by typing this line in cmd:
"fastboot oem device-info"
It must say that "bootloader unlocked: false"
Done!!
I seem to have encountered quite the predicament. My VS995 doesn't boot any more. It shows the "Your device is corrupt. It cannot be trusted, and will not boot" message that it always has, but then it reboots and shows it again, and repeats that process forever. I cannot boot into TWRP or Fastboot mode, but Download mode still works. Upon entering download mode, the little box at the bottom says "633A B50 Modified" and the loading bar says 0%. I don't have a Windows computer (all my computers run some variant of Linux Mint) and have been using a Windows 7 VM in VirtualBox. Device manager and LG Flash Tool recognize the phone, but LG Flash Tool fails to flash it at 4% claiming an "RX Timeout" error no matter what I do with it, and the little box in the phone's download mode changes to say "633A B25 Modified." LGUP (with or without Uppercut) simply says "Unknown [COM41,]" followed by "You must select a known model, please."
I tried following this guide (https://forum.xda-developers.com/v20/how-to/guide-lg-v20-to-life-t3827732) and several others around the internet to no avail. Does anybody have any idea if this phone can be saved? Or is it destined to the dump?
Since you still get the "device is corrupt" message, you still have the engineering aboot, so you have full fastboot.
Download the KDZ for you phone and extract it. (Search, there are lots of good posts on extracting KDZs)
Boot to fastboot. With the phone off, hold vol DOWN and plug in the USB cable.
fastboot flash twrp.img recovery
fastboot reboot
Then use the key combo to try and get to TWRP. If you can't then you probably have a hardware problem (bad NAND).
Whatever you do, don't do anything that will overwrite aboot or you have a 0% chance of fixing your phone.
-- Brian
runningnak3d said:
<snip>
-- Brian
Click to expand...
Click to collapse
You boot into fastboot by holding volume down and plugging the phone into a computer, correct? Whenever I do that it just shows the "device is corrupt" screen and does the reboot loop. I can only ever get to download mode.
Try this no guaranty it will work start LG up on your computer plug in device then remove battery from device and then reboot your computer without killing LG up then put battery back in phone and restart LG up......see what happens.
Kiraisuki said:
You boot into fastboot by holding volume down and plugging the phone into a computer, correct? Whenever I do that it just shows the "device is corrupt" screen and does the reboot loop. I can only ever get to download mode.
Click to expand...
Click to collapse
When did this start? Did you do anything to your phone, or did you reboot it and it just started doing this?
-- Brian
runningnak3d said:
<snip>
-- Brian
Click to expand...
Click to collapse
For reference, I bought it used (but tested working) on eBay a month ago. First, the SD slot corrupted my SD card and then started saying the SD was not compatible with the phone. Then the SIM slot stopped reading the SIM, so I restored a backup I had made a couple days ago in TWRP and it didn't fix it. I tried dirty flashing the ROM, then clean flashing a few other ROMs, but nothing fixed either slot. After a little more of this flashing, I rebooted and the phone started doing this.
It sounds like with the flashing you did, you restored the stock aboot while you still had a modified recovery (TWRP) and modified boot (rooted) .. that is the reason you can only get to download mode -- since laf wasn't modified.
The RX timeout you are getting sounds like you have a marginal USB port or cable, you need to try flashing on another PC, and don't use VBox. I think you can still save your phone...
-- Brian
If your bootloader is unlocked then you can fix your phone, if not then i had the same problem, repaired it from market, I think he used some kind of box(maybe octopus) and got it fixed.
runningnak3d said:
<snip>
-- Brian
Click to expand...
Click to collapse
I installed Windows 7 onto a laptop and installed the programs on it. LG Flash Tool still failed at 4% claiming the KDZ and DZ didn't support something (I couldn't read it because the box was too small and it didn't scroll) but LGUP via Uppercut recognized the phone and flashed it! The phone booted to a screen with a big red 2 on it, then I reflashed it with the same KDZ in LGUP and it booted, but now it's bootlooping. I waited about 20 minutes and it didn't boot beyond the Verizon boot animation.
Kiraisuki said:
I installed Windows 7 onto a laptop and installed the programs on it. LG Flash Tool still failed at 4% claiming the KDZ and DZ didn't support something (I couldn't read it because the box was too small and it didn't scroll) but LGUP via Uppercut recognized the phone and flashed it! The phone booted to a screen with a big red 2 on it, then I reflashed it with the same KDZ in LGUP and it booted, but now it's bootlooping. I waited about 20 minutes and it didn't boot beyond the Verizon boot animation.
Click to expand...
Click to collapse
It sounds like you have a hardware problem with the NAND chip on your phone. That is the only thing that makes sense as to why you were able to get it to boot, but now it bootloops.
The data on the NAND is good enough for one boot, but then becomes corrupt....
-- Brian
runningnak3d said:
<snip>
-- Brian
Click to expand...
Click to collapse
Could the bad NAND have also caused the SIM and SD slots to stop functioning, or did the phone just basically disintegrate in my hands?
The firmware could have had problems, or whatever hardware failure messed up your NAND also toasted those.
-- Brian
runningnak3d said:
<snip>
-- Brian
Click to expand...
Click to collapse
Well that stinks. For the month I owned it, the LG V20 was the best phone I've owned so far. Oh well, thanks for helping me.
Same Boat
Kiraisuki said:
I seem to have encountered quite the predicament. My VS995 doesn't boot any more. It shows the "Your device is corrupt. It cannot be trusted, and will not boot" message that it always has, but then it reboots and shows it again, and repeats that process forever. I cannot boot into TWRP or Fastboot mode, but Download mode still works. Upon entering download mode, the little box at the bottom says "633A B50 Modified" and the loading bar says 0%. I don't have a Windows computer (all my computers run some variant of Linux Mint) and have been using a Windows 7 VM in VirtualBox. Device manager and LG Flash Tool recognize the phone, but LG Flash Tool fails to flash it at 4% claiming an "RX Timeout" error no matter what I do with it, and the little box in the phone's download mode changes to say "633A B25 Modified." LGUP (with or without Uppercut) simply says "Unknown [COM41,]" followed by "You must select a known model, please."
I tried following this guide (https://forum.xda-developers.com/v20/how-to/guide-lg-v20-to-life-t3827732) and several others around the internet to no avail. Does anybody have any idea if this phone can be saved? Or is it destined to the dump?
Click to expand...
Click to collapse
I was hoping there was a solution to Kiraisuki's post as I having similar symptoms with my phone.
My V20 is a US996 BPT with a locked boot-loader. Mine will crash apps, stop at 4% via LG Flash, then reboot into "Your device is corrupt. It cannot be trusted" then lock into the LG logo until I pull the battery 3 or 4 times forcing a restart. I also have the same results with LG Bridge.
Does the NAND chip itself fail or could the chip be reflowed to the board with a little precision work?
If I start my phone without sim card, it won't boot. And if I start it with sim card, it will ask for the pin code and freeze at 2-3 seconds with a reboot. I tried a lot of stock versions, even flashing in edl mode without success. The only way I got my phone working was by flashing the MIUI port, but the sim was broken there too. I've been following some tutorials here in xda and it semms that my efs is broken (?). I tried to fix that in qualcomm software download tool and it doesn't detect my phone in miui.
Could anybody help me?
Follow the link...
https://forum.xda-developers.com/mi-a1/how-to/solution-bootloop-9-0-beta-t3876533
Same here and mistake with mi flash bootloader relocked :crying:
Any suggestions ?