In brief:
The N4 is stuck on the whirling circles during boot. It is likely due to some broken bit of hardware. I would like to determine where it's stuck. After that I can decide if repair is possible or if I don't need that feature and it can be skipped one way or another or toss the brick altogether.
In full:
While out of town S.O. dropped the phone and the digitizer shattered. She said the screen appeared to still work, but no input was possible. She ordered a new digitizer and dumped it on me to repair, little realizing the difficulty of replacing only the digitizer. Still, I gave it the ol' college try on a slow day at work, heating the glass shards to yield the glue and get them off the screen. After installing new digitizer I was not surprised that I had damaged the screen and just a few colored stripes displayed.
So I ordered and installed a digi/lcd assembly and I now have a functioning screen and digitizer. The problem is the system won't completely boot and is stuck on the infamous whirling circles. I am fairly certain that during boot some device is being queried and is broken, and the boot has no timeout to skip it and move on. I would like to know where it's stuck. I *think* the way to do that is to somehow direct kernel messages out the phone's USB so I can use PuTTY to display them on a workstation. I do not know how to do that. If there's some other way, like getting the messages to display on the phone's screen, I don't know that either. Hence my post.
The techie bits:
Long story short here's a summary of relevant actions I've done so far.
Phone still goes into the mako bootloader and I can use fastboot.
Used TWRP recovery to wipe everything (including itself)
Flashed factory 4.4.2 OS
Reinstalled TWRP recovery and had it root for me
I now have two ways to access the phone - fastboot when in the stock mako bootloader, and adb when I fire up TWRP.
Now what can I do to find where the system boot is hanging? Suggestions welcome.
first thing to look at - proximity / light sensors connector . phone will not boot if they are disconnected from mainboard.
RolF2 said:
first thing to look at - proximity / light sensors connector . phone will not boot if they are disconnected from mainboard.
Click to expand...
Click to collapse
I will check that. Thanks for the reply.
Edit: I just checked, and you were right on the money. The tab with the connector for that device had flipped under the mainboard so I didn't connect it. All fixed now and I have a working phone. I owe you a couple beers. Thanks.
Hi, you are lucky
I have a similar problem.
Yesterday i restarted my phone and >problem, stuck at X-boot-logo<
Already tried different roms.
Can get into fastboot-mode and therefore can have ADB with CMW-recovery.
I replaced my screen a few months ago.
Already checked proximity sensor cable.
btw:
at the beginning, one time I got it to "optimizing apps...", but it was stuck at "starting apps"
How can I see if my proximity/light sensor is dead?
can I use the Nexus 4 serial?
Any other solution?
Regards
You can try to downgrade to stock 4.2 android, phone most likelly will boot, but looks like you have lost your IMEI.
RolF2 said:
You can try to downgrade to stock 4.2 android, phone most likelly will boot, but looks like you have lost your IMEI.
Click to expand...
Click to collapse
OK, I'll try to go back to 4.2.
Anything I can do if I really lost IMEI?
I think you could be right.
I rebooted my phone because i got no network connection. (even after airplanemode on/off)
---------- Post added at 07:05 PM ---------- Previous post was at 06:45 PM ----------
OK, 4.2 booted successfully
Thanks.
but phone does not connect to network.
IMEI seems to be lost (*#06# shows nothing for imei)
What do you think about restoring IMEI with dd-command from "somewhere"?
take a look here : http://forum.xda-developers.com/wiki/LG_Nexus_4/Partition_Layout
do you have baseband version unknown too ?
if yes, first I would try dd mmcblk0p1 (modem / radio.img) and only after that next step would be m9kefs1/mmcblk0p8 , m9kefs2/mmcblk0p9 = IMEI
this is only speculation, never tried that ...
RolF2 said:
take a look here : http://forum.xda-developers.com/wiki/LG_Nexus_4/Partition_Layout
do you have baseband version unknown too ?
if yes, first I would try dd mmcblk0p1 (modem / radio.img) and only after that next step would be m9kefs1/mmcblk0p8 , m9kefs2/mmcblk0p9 = IMEI
this is only speculation, never tried that ...
Click to expand...
Click to collapse
no baseband too.
imei empty, not zero
I don't think dd mmcblk0p1 would be useful as it is only the radio.img.
You can find it in the stock image
The first step now is backupping the efs-partitions
do you mean directly writing IMEI to it?
I can try to copy the IMEI(or all partitions) from my brother's phone to mine
Thx
don't hurt to try dd modem partition first, maybe it's corrupted in some way ... why it's unknown ?
Related
After reading the TF300 topic about flashing the firmware of the PCB I maybe found a solution for the ME301T
In the dir /system/etc/firmware/touch I've found the following versions:
0b-00-0009.ekt
0b-01-0009.ekt
0b-03-0006.ekt
Tried all three versions and they all show me a different version in the about tab and all change in a different way how the digitizer reacts, but I still haven't the right one.
One does everything in the opposite way, the other doesn't react and another only reacts on 1/2 of the screen.
So does anyone have other versions?
Can you upload screenshots of what you did exactly? My touchscreen sometimes lags randomly. Im trying to fix it somehow. Let me know how to fix it please
EtoshNL said:
After reading the TF300 topic about flashing the firmware of the PCB I maybe found a solution for the ME301T
In the dir /system/etc/firmware/touch I've found the following versions:
0b-00-0009.ekt
0b-01-0009.ekt
0b-03-0006.ekt
Tried all three versions and they all show me a different version in the about tab and all change in a different way how the digitizer reacts, but I still haven't the right one.
One does everything in the opposite way, the other doesn't react and another only reacts on 1/2 of the screen.
So does anyone have other versions?
Click to expand...
Click to collapse
The solution is easy.
You need the PCB to get stuck in bootloader mode, when the firmware is reflashed , the PCB looses the calibration data.
There are two ways to achieve it:
1. The easy way:
-After digitizer replacement DO NOT connect the digitizer flex cable.
-Turn the device on and be ready do disconnect the battery.
When the device boots the PCB will notice "a change" in the digitizer and will try to reflash the firmware. You will see on the screen "updating touch firmware" or something similar.
-As soon you see the percentage gets HIGHER THAN ZERO pull the battery out.
-Connect the digitizer flex.
-Turn the tablet on.
Same as before, when the device boots the PCB will notice "a change" in the digitizer and will try to reflash the firmware. This time, let it finish the process.
-You'll get a perfectly working touchscreen
Sometimes the device will not start the updating process by itself. Try to connect/remove the flex cable and reboot. If the firmware update process doesn't start by itself move to the second method.
2. The hard way
-You need to root the device.
-You need to flash the firmware same method as TF300.
adb shell
su
touch_fw_update -u /system/etc/firmware/touch/0b-00-0009.ekt
-You need to brake the updating process as soon the PCB gets to bootloader mode.
When you hit "Enter" you'll see some rows with PCB data and then numbered packets are sent.
-When the first packet is sent you'll see the progress dots ". . . . . . . . . . . . . . . . . ", hit "Control+C" as soon you see it.
-Reboot the device.
-If the device won't update the firmware by itself during boot, repeat the flashing process manually but let the update process to finish this time.
Enjoy
Vadim Brook
http://masahim.co.il
Solved "low sensitiviy" issue
I'd like to thank Vadimbrk, solved my issue too.
Just to summarize if someone runs to a similar troubles:
ME301T, broken glass, replaced with the same type (5280N FPC-1 REV.4), but after that, the touch screen looked like having very low sensitivity, sometimes not responding to touches, loosing touch when dragging, etc. Practically useless. I have checked all connectors number of times, disconnected display, swithed off wifi, if it could me an EMC issue, no luck.
Not sure why, but the firmware re-flash helped! I wonder if it was that the firmware reflash invoked some autocalibration... no idea, but it works
Just exactly as Vadimbrk described (the easy way) I let the digitizer firmware re-flashed and the touch screen (digitizer) started working like charm.
Thanks again!
Hi all,
Does this mean that we can now mount a 5235N in place of a 5280N ?
Thanks for your answer.
Best regards,
You CAN mount a 5235N in place of a 5280N without it.... Just install it and it just works...
You also can mount T01 instead 5280N but its hard to find those this days...
Hi, I've installed a 5235 and it doesn't work correctly, tried the steps you mentionned and it doesn't work, any help ?
Note : haven't tried the root method yet...
NGRaziel said:
Hi, I've installed a 5235 and it doesn't work correctly, tried the steps you mentionned and it doesn't work, any help ?
Note : haven't tried the root method yet...
Click to expand...
Click to collapse
You probably installed it wrong....
Connect the flex upside down....
vadimbrk said:
You probably installed it wrong....
Connect the flex upside down....
Click to expand...
Click to collapse
Actually, that's what I had originally done :silly:
NGRaziel said:
Actually, that's what I had originally done :silly:
Click to expand...
Click to collapse
I don't know what it means but the flex should be inserted with the metal connector pads UP
vadimbrk said:
I don't know what it means but the flex should be inserted with the metal connector pads UP
Click to expand...
Click to collapse
Ok, just kill me, that was it. Wife's laughing at me right now
Thanks a lot
---------- Post added at 10:40 PM ---------- Previous post was at 10:38 PM ----------
Is it just me or is the 5235 extremly sensitive ?
NGRaziel said:
Ok, just kill me, that was it. Wife's laughing at me right now
Thanks a lot
---------- Post added at 10:40 PM ---------- Previous post was at 10:38 PM ----------
Is it just me or is the 5235 extremly sensitive ?
Click to expand...
Click to collapse
Ok, so, seems it's still not perfect, doesn't seem to record long press, I'm having a hell of a hard time unlocking the device, and to top it all, ghost touches ? :/
vadimbrk said:
The solution is easy.
You need the PCB to get stuck in bootloader mode, when the firmware is reflashed , the PCB looses the calibration data.
There are two ways to achieve it:
1. The easy way:
-After digitizer replacement DO NOT connect the digitizer flex cable.
-Turn the device on and be ready do disconnect the battery.
When the device boots the PCB will notice "a change" in the digitizer and will try to reflash the firmware. You will see on the screen "updating touch firmware" or something similar.
-As soon you see the percentage gets HIGHER THAN ZERO pull the battery out.
-Connect the digitizer flex.
-Turn the tablet on.
Same as before, when the device boots the PCB will notice "a change" in the digitizer and will try to reflash the firmware. This time, let it finish the process.
-You'll get a perfectly working touchscreen
Sometimes the device will not start the updating process by itself. Try to connect/remove the flex cable and reboot. If the firmware update process doesn't start by itself move to the second method.
Click to expand...
Click to collapse
My touchscreen lags, swiping gets cut off/stutters, and long press fails to work. It's a highly intermittent problem and I've never replaced the digitizer. It started after flashing omnirom. I've reseated the flex cable and it works fine for a few hours. But then it goes back to its old issues for a couple of days.
Do you think I have a firmware problem, or is this some other hardware/software problem. Do you suggest I try this method?
Could my firmware have been corrupted after flashing omnirom?
Just to confirm what you are trying to do: force the unit to wipe the firmware by removing the cable, reconnect the cable and then the unit will flash the correct firmware calibration. Do I have that straight?
vsny said:
Just to confirm what you are trying to do: force the unit to wipe the firmware calibration by removing the cable, reconnect the cable and then the unit will flash the correct firmware calibration. Do I have that straight?
Click to expand...
Click to collapse
...
---------- Post added at 03:42 PM ---------- Previous post was at 03:40 PM ----------
NGRaziel said:
Ok, so, seems it's still not perfect, doesn't seem to record long press, I'm having a hell of a hard time unlocking the device, and to top it all, ghost touches ? :/
Click to expand...
Click to collapse
Put some padding between the LCD frame and digitizer. Double sided foam or something....
Yep, investigating led me to such a solution, but the digitizer broke for some reason, so I gave up, can't afford to buy one again...
Thanks anyway.
vadimbrk said:
1. The easy way:
-After digitizer replacement DO NOT connect the digitizer flex cable.
-Turn the device on and be ready do disconnect the battery.
When the device boots the PCB will notice "a change" in the digitizer and will try to reflash the firmware. You will see on the screen "updating touch firmware" or something similar.
Click to expand...
Click to collapse
Vadimbrk,
My rom is omnirom.
When I pull the digitizer cable (the wide copper colored flex cable on the top left (holding it upside down backwards)) and turn the device on, I do not get the next step "updating touch firmware" or something similar. It just boots into omnirom. Do I have to reflash the stock rom?
vsny said:
Vadimbrk,
My rom is omnirom.
When I pull the digitizer cable (the wide copper colored flex cable on the top left (holding it upside down backwards)) and turn the device on, I do not get the next step "updating touch firmware" or something similar. It just boots into omnirom. Do I have to reflash the stock rom?
Click to expand...
Click to collapse
Yep, you need the stock rom for the touch firmware to be flashed.
So far so good. It took me a couple of tries. I reflashed the stock firmware and didn't realize you need to get to the desktop (it was still asking to choose a language). I figured the recalibration would happen before the os boots.
I following the instructions and reflashed omnirom. So far so good. I haven't used the tablet much, but so far I haven't noticed any touch problems.
Now if I can just fix issues with my SD cards. Every once in a while it will not be recognized.
This is an old post, but definetely a saver!!!! thanks allot. just used the first method and it worked. the not working digitizer is working now
thanks thanks thanks allot!!!
A few posters here claim that the G2 is unbrickable - but I think I can challenge that. It started off with me wrongly flashing the Cloudy ROM 3.0 - what I didn't realise only till later was that it was intended for the Korean variant of the G2. Dummy move indeed.. I had previously taken the necessary precautions and took a full titanium backup and ROM backup onto a USB drive via TWRP - I previously ran Cloudy ROM 2.2 with Dorimanx Kernel on KK 4.4.2.
Right now, the phone doesn't seem to power on via buttons. When I plug it to the PC via the USB, I get "QHSUSB_BULK" as an unknown device only.. no black screen while on, no drives or COM port.
First off I want to be clear that I know I and only I am responsible for bricking my phone - The reason I'm in this mess is completely down to my stupidity, and trusting 'educated guesses' instead of confirming specs black of white. Just wanted to be clear in case anyone gets the wrong impression.
So this is more or less the sequence of events;
1. After flashing, I got stuck in fastboot mode.. (can't find the link) I followed one post where I needed to flashed .img files via the Fastboot CLI (similar to ADB). I used the images from the LG G2 D802 16GB in europe. source.. It was a toss up between the EUR and non EUR, and so I made the first of my so called 'educated guesses' that sent this phone deeper into the ground.
2. Something went wrong as when I rebooted the phone (had no idea what had gone wrong at the time), I got no logo. After some time, I noticed the screen on with a black background. when plugged into the pc, the QHSUSB_BULK would appear and with it a bunch of drives that Windows thought needed repairing. so I followed This .. I installed ubuntu, booted to terminal so I don't get those auto discovery pop ups, I used the images recommended there for my device (again, it seemed to make sense to use the same that the OP was using for my LG G2 D802 16GB in europe... After I rebooted, it was to my horror that the screen didn't even turn on, with no drives being detected via USB.. just the QHSUSB_BULK. This is what made me realise that the culprit was most probably using wrong images rather than improperly executing the instructions.
3. I opened the phone and tried shorting some capacitors where I'm supposed to see the drives again to no avail. I even tried shorting the capacitors ends as described here to no avail. I done a good full hour shorting the hell out of those capacitors (the post says to keep at it till it works cos it can sometimes be a bit tricky) but I saw no change. I would like to try the DL mode described there but I can't figure out what I have to ground from the images shown in the post regarding the "BOOT CONFIG".
This is basically the state the phone is in at the moment. so to recap:
No bootloader,
no recovery,
no fastboot,
no download mode,
no drives when in QHSUSB_BULK mode,
no COM port.
From the multitude of unbricking guides here, I gather that I either need to see that bunch of drives again when via USB or a COM port. I tried installing Qualcomm drivers, thinking that if the pc recognises the device, I might get the pc to identify the COM port, but the driver couldn't be installed for the QHSUSB_BULK device (got some error.. I can update this post later).
I tagged this post as a question.. i'm sure there's a question here somewhere...
HELP?!
bump.
Could really use a little help... anything
kuwlij said:
bump.
Could really use a little help... anything
Click to expand...
Click to collapse
You can ask @somboons
he came from deep hard bricked.
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
http://forum.xda-developers.com/showpost.php?p=56608822&postcount=2
http://forum.xda-developers.com/lg-g2/development-d802/tools-mini-srk-tool-d802-t3098163
:good:
.
...
When I first tried to enter QHUSB_BULK mode on mine, I took ages. Seriously, ages. It kept not showing the drives. Important thing to remember, in my opinion, is to use Linux (latest Ubuntu in my case). If you keep trying, eventually they will pop up for a split second. I can't remember how I did it, but you have to use a partition tool, I think, to get it to freeze the positions of the drives. Then, once it's 'mounted' them, you can try (and keep trying) to flash to each partition.
Mine was well and truly screwed, so I flashed a blank partition table on, then flashed each image onto that. It took a lot of trial and error, though, because it kept not showing the drives.
furzewolf said:
When I first tried to enter QHUSB_BULK mode on mine, I took ages. Seriously, ages. It kept not showing the drives. Important thing to remember, in my opinion, is to use Linux (latest Ubuntu in my case). If you keep trying, eventually they will pop up for a split second. I can't remember how I did it, but you have to use a partition tool, I think, to get it to freeze the positions of the drives. Then, once it's 'mounted' them, you can try (and keep trying) to flash to each partition.
Mine was well and truly screwed, so I flashed a blank partition table on, then flashed each image onto that. It took a lot of trial and error, though, because it kept not showing the drives.
Click to expand...
Click to collapse
Mine was exactly the same I also had a blank partition table.. Anyway just keep trying because It took me a while to get mine working.. I was trying to short the capacitors but it seems to be quite hard sometimes especially if you aren't carefull.. Because you can start to mess with the soldering of the capacitors and it'll be harder after that.. It happened to me..
Anyway here's something I've wanted to ask everyone, after I sucessfully put my phone back to life, it seems like the middle button isn't working, the LED and the volume rockers are fully working, but if I ever press the power button after some time it shutdowns just like if I pressed and hold for a while, has anyone got this problem? It seems like the flex cable or something is damaged but i wanted to be sure it's really damaged or just something I could solve.. thanks and sorry for the off topic..
kuwlij said:
bump.
Could really use a little help... anything
Click to expand...
Click to collapse
This
HTML:
http://forum.xda-developers.com/showthread.php?t=2582142
saved my D802.Take time to read all post
Hello,
This is my first post on this forum so hello everyone! This forum has helped me numerous times with various devices, it is a valuable source of information and the people here seem very helpful. I have searched but cant find a thread relating to my current issue so I decided to start a thread and hopefully get some answers.
Ill try to keep this short while still providing enough information, first things first my device is a D802T 32GB model. Timeline of steps ive taken are as follows.
-Running Ressurection Remix ROM
-Downloaded ROM update and flashed with TWRP
-Device would get to "Upgrading Apps" step then restart half way through, back to upgrading app, restart again and so on
-Flashed stock ROM with LG Flash tool 2014, Froze at 49%
-Tried again to flash Stock ROM, this time it froze at 10%
-This caused the phone to loose Download mode & Recovery.... HARD BRICKED
-Phone would show as Qualcomm HS-USB 9006 in device manager
-Used Ubuntu to flash Partitions
-Must have flashed wrong partitions, after I flashed them the phone seemed to be 100% bricked with no signs of life at all
-Managed to jump pins on chip inside phone to get it into Qualcomm HS-USB 9008 mode
-Downloaded BIN_LGD802AT-00-V10b-SEA-XX-SEP-04-2013-32G+0 TOT File and extracted partitons
-Used BoardDiag to re flash Partitions I extracted from TOT file above
-Phone now seems 100% fixed except for one issue NO DISPLAY!
The phone boots, I hear the boot sound, the touch screen works as it should but I have no display whatsoever not even a black screen. My question is can flashing partitions cause you to loose display but the phone still boot and retain digitizer function?
I repair phones for a bit of extra money on the side so I know what im doing but I wanted another opinion or two before I go ordering parts. Does this sound like I may have damaged something while jumping the pins or could it be the partitions I flashed? Also if I have damaged something how can I tell if its the screen or if I damaged the charge port flex as this carry's the display signal. Keep in mind everything else works on that lower board such as the USB port etc. It seems a massive coincidence I loose display after flashing partitions but then again I was fiddling with the insides but I have done that many many times before so what are peoples thoughts on this?
I appreciate anyone who takes the time to help
42 views and no one has any ideas at all?
Sorry m8.....the last time i had 9006 brick i flashed correct partitions and got my phone working through TOT.......
You could try a new flex cable or even a new screen to diagnose whether its a hardware problem, black screen usually indicates damaged LCD connector pins on LCD panel or flex cable.
Also having "white tv noise" indicates a damaged flex cable.
Next time you have 9006, use this! https://www.youtube.com/watch?v=_d5b_osUTug
You don't need Ubuntu and you have less chance of super bricking.
Hey mate thanks for replying,
I did try that method but kept getting an error (something about cannot find file specified) so I just went the Ubuntu method. I did plan on just ordering a new screen but wanted to be a bit more certain of the issue first. I wish I had of kept my old damaged screens so I could fit one to determine if the screen really is the issue.
I didn't need to touch the bottom part where the LCD flex cables plug onto the board but stranger things have happened, unfortunately the G2 doesn't seem to be very popular in my area as I dont know anyone else that has one that I could possibly put my motherboard in to know for sure its the screen.
I might completely disassemble it and inspect it under a magnifier to make sure I haven't knocked any resistors or anything off the board, ill probably end up just ordering a screen as it seems the only way to know.
Thanks for your help
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.
Hi everyone, i have a G2(D802) which i have used for 5 years. Yesterday, when i turn off the screen then try to turn on it didn't. I tried to reset with holding power button like 20-25 seconds. It stucked at LG logo. After many reset nothing happened. Then this morning i could was able to open my phone, so i thought it was a problem about software things, so i backuped everything and change my rom(i was using Lineage 14.1 ) to Resurrection Remix. But same thing happened, when i turn off the screen it has gone again. So i decided to install stock rom back. But this time when i used Flash Tool 2014 and appropriate KDZ, it stacked at 4%, after trying different cables, ports,windows 7/xp and programs (like LG Mobile Support Tool, LG Up) in Device Manager it seemed as : "qualcomm hs-usb qdloader 9006" and no recovery mode no download mode, when i google this problem i found it named with "qhsusb_bulk" and i found this article and successfully recover download mode. Now in Device Manager it seems as "LGE AndroidNet USB Serial Port".
TLDR: I can only open download mode, no recovery, it stacked LG logo, when i use Flash Tool 2014 or LG Mobile Support Tool with different KDZ/TOT it stacked at 4%. What should i do? What's wrong with my phone? I need your help urgently because i have no other phone. Thank you for reading.
metobayrak said:
Hi everyone, i have a G2(D802) which i have used for 5 years. Yesterday, when i turn off the screen then try to turn on it didn't. I tried to reset with holding power button like 20-25 seconds. It stucked at LG logo. After many reset nothing happened. Then this morning i could was able to open my phone, so i thought it was a problem about software things, so i backuped everything and change my rom(i was using Lineage 14.1 ) to Resurrection Remix. But same thing happened, when i turn off the screen it has gone again. So i decided to install stock rom back. But this time when i used Flash Tool 2014 and appropriate KDZ, it stacked at 4%, after trying different cables, ports,windows 7/xp and programs (like LG Mobile Support Tool, LG Up) in Device Manager it seemed as : "qualcomm hs-usb qdloader 9006" and no recovery mode no download mode, when i google this problem i found it named with "qhsusb_bulk" and i found this article and successfully recover download mode. Now in Device Manager it seems as "LGE AndroidNet USB Serial Port".
TLDR: I can only open download mode, no recovery, it stacked LG logo, when i use Flash Tool 2014 or LG Mobile Support Tool with different KDZ/TOT it stacked at 4%. What should i do? What's wrong with my phone? I need your help urgently because i have no other phone. Thank you for reading.
Click to expand...
Click to collapse
hi there.. unfortunately LG did a mess in my opinion! After buying G2 and G Pad I will never buy LG again because of this..
anyway, assuming you're doing everything as described into the guides (like port COM 41, copy the right DLL file etc) there is one thing I would try in your situation: trying with a different PC, in particular a Windows 7 / XP one..
also I read that sometimes this issues was randomly gone after trying and trying and trying and trying and trying..! If available I would also try different KDZ firmware (but be sure it's for your model.. as long as it is it doesn't matter if it's JB, KK or LP)
brainvision said:
hi there.. unfortunately LG did a mess in my opinion! After buying G2 and G Pad I will never buy LG again because of this..
anyway, assuming you're doing everything as described into the guides (like port COM 41, copy the right DLL file etc) there is one thing I would try in your situation: trying with a different PC, in particular a Windows 7 / XP one..
also I read that sometimes this issues was randomly gone after trying and trying and trying and trying and trying..! If available I would also try different KDZ firmware (but be sure it's for your model.. as long as it is it doesn't matter if it's JB, KK or LP)
Click to expand...
Click to collapse
Thank you for your suggestion, after several hundred attempts i successfully go back to stock rom(an Indian stock rom which i found it in storagecow link), but the problem is; when i turn off the screen, i can not open again, and it restarts and stuck at lg logo. After hundred times reset, phone started normally, then i flash a twrp recovery (with autorec) and go recovery. This time twrp said Unable to Mount System,Storage etc. so twrp shows internal storage: 0mb and all folders(data,sdcard,system etc.) empty. I mean define this problem is very hard and i think it is very rare problem. I'm not sure which part of the phone is the problem. I don't know is this a hardware problem or a software(like wrong partition or something like that) problem.
metobayrak said:
Thank you for your suggestion, after several hundred attempts i successfully go back to stock rom(an Indian stock rom which i found it in storagecow link), but the problem is; when i turn off the screen, i can not open again, and it restarts and stuck at lg logo. After hundred times reset, phone started normally, then i flash a twrp recovery (with autorec) and go recovery. This time twrp said Unable to Mount System,Storage etc. so twrp shows internal storage: 0mb and all folders(data,sdcard,system etc.) empty. I mean define this problem is very hard and i think it is very rare problem. I'm not sure which part of the phone is the problem. I don't know is this a hardware problem or a software(like wrong partition or something like that) problem.
Click to expand...
Click to collapse
so ROM is flashed but no files are anywhere? Did the same happens when you browse the device with the windows command Prompt / Linux Terminal?
Yea anyway weird, maybe you can see if this tool has original partitions for your model: https://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 - please pay attention if you do it and backup the partitions you have atm before
brainvision said:
so ROM is flashed but no files are anywhere? Did the same happens when you browse the device with the windows command Prompt / Linux Terminal?
Yea anyway weird, maybe you can see if this tool has original partitions for your model: https://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 - please pay attention if you do it and backup the partitions you have atm before
Click to expand...
Click to collapse
I used this tool when my phone showed in Device Manager as : "qualcomm hs-usb qdloader 9006" and it worked, today when i opened my phone(after install stock rom again) i kept the screen always open. After 5 minutes, suddenly screen gone and stuck at lg logo. Now I think that the problem is definitely hardware. Because i did nothing and phone was connected with a cable to my pc. If the solution is to change a part(like the processor) inside the phone, I will write here what the problem part is. Thank you again.
metobayrak said:
I use this tool when my phone showed in Device Manager as : "qualcomm hs-usb qdloader 9006" and it worked, today when i open my phone(after install stock rom again) i kept the screen always open. After 5 minutes, suddenly screen gone and stuck at lg logo. Now I think that the problem is definitely hardware. Because i did nothing and phone was connected with a cable to my pc. If the solution is to change a part(like the processor) inside the phone, I will write here what the problem part is. Thank you again.
Click to expand...
Click to collapse
pretty sure it's the mainboard, I saw it's the first part of the G2 that gives problem after a while
brainvision said:
pretty sure it's the mainboard, I saw it's the first part of the G2 that gives problem after a while
Click to expand...
Click to collapse
I found the problem part. It's the eMMC chip. I disassemblied the phone and heat the relevant chip (on my motherboard the chip named as Toshiba) with hot air gun. My phone worked properly for 1 minute, then gone again.
metobayrak said:
I found the problem part. It's the eMMC chip. I disassemblied the phone and heat the relevant chip (on my motherboard the chip named as Toshiba) with hot air gun. My phone worked properly for 1 minute, then gone again.
Click to expand...
Click to collapse
you know what: I think my device has the same issue, eMMC is damaged.. I'm not using the G2 as primary or secondary device anymore but from time to time I like to flash something and using it.. but it's almost one year that when stuff I have no error but when I boot the device and start using it I have random reboots.. but they are totally random and almost happen when installing one app, using a system app or something like that. it happens with both stock firmware both with custom ROMs.. basically I have to flash and using the device for a day and if I have less then two reboots in that period I go on..
I'm not an expert about hardware matters, do you mind linking me a video on YouTube about what have you done with the airgun? Also I tried to search for spare eMMC but I wasn't able to find any (some time ago) so the option would be to change the motherboard.. did you find something instead?
brainvision said:
you know what: I think my device has the same issue, eMMC is damaged.. I'm not using the G2 as primary or secondary device anymore but from time to time I like to flash something and using it.. but it's almost one year that when stuff I have no error but when I boot the device and start using it I have random reboots.. but they are totally random and almost happen when installing one app, using a system app or something like that. it happens with both stock firmware both with custom ROMs.. basically I have to flash and using the device for a day and if I have less then two reboots in that period I go on..
I'm not an expert about hardware matters, do you mind linking me a video on YouTube about what have you done with the airgun? Also I tried to search for spare eMMC but I wasn't able to find any (some time ago) so the option would be to change the motherboard.. did you find something instead?
Click to expand...
Click to collapse
This is the video I get help with: https://www.youtube.com/watch?v=ft8V5yrQFic
this guy did this for g3 but doing for g2 also works. This is definitely a temporary solution. It works maybe just 1 minute (like me) or 1 hour if you are lucky maybe 1 month. Changing motherboard is primary solution but it is expensive and worthless. I think that is chronic problem for LG G series. There is no proper heat dissipation on the motherboard. They have just put thin metal plates. Maybe you can try after the heating process, just put a thermal pads the relevant chipsets. You can see from this video: https://www.youtube.com/watch?v=HMdvG6w7etU
metobayrak said:
This is the video I get help with: https://www.youtube.com/watch?v=ft8V5yrQFic
this guy did this for g3 but doing for g2 also works. This is definitely a temporary solution. It works maybe just 1 minute (like me) or 1 hour if you are lucky maybe 1 month. Changing motherboard is primary solution but it is expensive and worthless. I think that is chronic problem for LG G series. There is no proper heat dissipation on the motherboard. They have just put thin metal plates. Maybe you can try after the heating process, just put a thermal pads the relevant chipsets. You can see from this video: https://www.youtube.com/watch?v=HMdvG6w7etU
Click to expand...
Click to collapse
I thought about applying something (couldn't imagine what however) on the internal back of the cover but not because of the issues I have but simply because the device get hot very soon! I'
But basically you are saying that this issue related to the eMMC is not because the chip is damaged but only for the temperature it reaches?
brainvision said:
I thought about applying something (couldn't imagine what however) on the internal back of the cover but not because of the issues I have but simply because the device get hot very soon! I'
But basically you are saying that this issue related to the eMMC is not because the chip is damaged but only for the temperature it reaches?
Click to expand...
Click to collapse
Yes, because of the eMMC chip is damaged. But the crux of the problem is processor heats and cause of no proper heat dissipation this damages other chipsets. Thermal pad solution must be done after chip replacement.