Database Users

[Q] Boot not completing - likely hardware problem

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 ?

[Q] [HELP] LG G2 D802 in coma - Really Deep, Hard and Seriously Bricked

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

LG G2 D802 No Display, Bricked, Recovered

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

N7 2012 [WiFi] Grouper - Bricked or the Flash Memory just failed?

Ok, so to start off I'm very familiar with Nexus Root Toolkit an its many graceful features & its ablity to bring the N7 from the brink of destruction (Soft -Brick) "AS LONG AS YOUR PC CAN DETECT THE DEVICE".
Here's the issue.. I was in TWRP (Multi-ROM) just renaming 1 of the Secondary ROMs to more friendly names, I hadn't done any flashing of any zips or roms for a few boots, I just booted into Recovery to do some renaming of Secondary ROMs that I had installed a few nights before but I had been in an out of several different one's just making sure they were all working so anyway.. after I was done renaming, I reboot the system & it just went F'ing blank.. now nothing.. there's no back light, no bootlogo, nothing happens at all when I plug in the charging or hold the power button with or w/out the vol-+ keys, I've checked the battery connection, it was snug but I removed it over night.. still nothing, I'm just clueless.. Before we jump on the NRT do a factory wipe & restore, when I plug it into Windows it instantly pops up with the "Device has Malfunctioned" not the "installing adb drivers" or anything like it has so many times before.. either Im over thinking this an the answer is so simple Im blinded by rage over how much this p1sses me off that it was working fine one moment an then just reboots to blank nothingness.. even if I take the battery out an try plugging it directing into the pc via the OEM usb cable it gives the same error with or w/o the battery in .. the toolkit cant even see it cause windows cant establish what the hell it is.. And yes I've tried installing every android driver possible.. the N7 was primarily for my wife to read e-books on.. so i rarely played with it.. an it was new sealed in the box just bought last year around this time so i can't believe the Flash Memory is shot already, if anyone could throw me their 2 cents it would be greatly appreciated , this is so frustrating but I think its BRICKED.. or at least some tiny flash chip is toast..
its the - N7 2012 Grouper WIFI Only model -
p.s. I apologize for the slight harsh tone, I'm just upset with this issue.. I got this particular tablet with the knowledge an understanding that it was the (almost) un-brickable tablet, yet I managed to do it.. If by some chance I get it to fire up, I will definitely let ya know.. But I have read alot of posts an my guess is somehow I managed to mess up the nvflash an now the memory chip or something is corrupt beyond a NRT Factory reset.. but again it was at almost full battery when i rebooted from within the TWRP Menus & I wasn't flashing anything previous to me being in my Main Rom which was stock rooted 4.4.4 de-bloated, playing a game called Empire 4 Kingdoms for like a 1/2 (just getting my daily's) before i decided to check out my Secondary Roms an rename a few because I wanted to started playing around with them to test how the same game played on different flavors or Android..

phnxnvrdies said:
Ok, so to start off I'm very familiar with Nexus Root Toolkit an its many graceful features & its ablity to bring the N7 from the brink of destruction (Soft -Brick) "AS LONG AS YOUR PC CAN DETECT THE DEVICE".
Here's the issue.. I was in TWRP (Multi-ROM) just renaming 1 of the Secondary ROMs to more friendly names, I hadn't done any flashing of any zips or roms for a few boots, I just booted into Recovery to do some renaming of Secondary ROMs that I had installed a few nights before but I had been in an out of several different one's just making sure they were all working so anyway.. after I was done renaming, I reboot the system & it just went F'ing blank.. now nothing.. there's no back light, no bootlogo, nothing happens at all when I plug in the charging or hold the power button with or w/out the vol-+ keys, I've checked the battery connection, it was snug but I removed it over night.. still nothing, I'm just clueless.. Before we jump on the NRT do a factory wipe & restore, when I plug it into Windows it instantly pops up with the "Device has Malfunctioned" not the "installing adb drivers" or anything like it has so many times before.. either Im over thinking this an the answer is so simple Im blinded by rage over how much this p1sses me off that it was working fine one moment an then just reboots to blank nothingness.. even if I take the battery out an try plugging it directing into the pc via the OEM usb cable it gives the same error with or w/o the battery in .. the toolkit cant even see it cause windows cant establish what the hell it is.. And yes I've tried installing every android driver possible.. the N7 was primarily for my wife to read e-books on.. so i rarely played with it.. an it was new sealed in the box just bought last year around this time so i can't believe the Flash Memory is shot already, if anyone could throw me their 2 cents it would be greatly appreciated , this is so frustrating but I think its BRICKED.. or at least some tiny flash chip is toast..
its the - N7 2012 Grouper WIFI Only model -
p.s. I apologize for the slight harsh tone, I'm just upset with this issue.. I got this particular tablet with the knowledge an understanding that it was the (almost) un-brickable tablet, yet I managed to do it.. If by some chance I get it to fire up, I will definitely let ya know.. But I have read alot of posts an my guess is somehow I managed to mess up the nvflash an now the memory chip or something is corrupt beyond a NRT Factory reset.. but again it was at almost full battery when i rebooted from within the TWRP Menus & I wasn't flashing anything previous to me being in my Main Rom which was stock rooted 4.4.4 de-bloated, playing a game called Empire 4 Kingdoms for like a 1/2 (just getting my daily's) before i decided to check out my Secondary Roms an rename a few because I wanted to started playing around with them to test how the same game played on different flavors or Android..
Click to expand...
Click to collapse
UPDATE STATUS - If I plug it into the pc without the battery i get a windows driver install box that says "Installing APX..." does this indicate the NVFlash is corrupt or is there a way to get out of apx mode.. im not familiar with that mode .. only ADB & fastboot..
Update 2 - After reading lots, I've come to conclude its hardbricked, must have had an error in memory or whatever.. its stuck in APX mode so im going to replace the whole MB with a working 32GB [model me370t] & start over .. maybe ill not install so many ROMS via multirom.. just a few - THREAD BE CLOSED - I'm done here, good luck to anyone with similar results

Zte Axon 7 (A2017G) System ui stopped and continuously self reset

Dear all
i always follow this community with interest but now i have to bother you with a problem.
I have a ZTE AXON 7 that after a while started to give me the message system ui has stopped
i did an hard reset and it was showing the same message directly after rebooting, it doesn't even allow me to finish the initial configuration (google account etc..) that it reboot and hard reset autonomously.
I decided to flash a stock rom with axon 7 EDL TOOL, i followed your instructions unzipping all the files in the folder FLASH-FULL, i selected flash full edl in in the tool, process finished but same problem, message "system ui has sotpped" continuously showing and no way to finish the configuration of android that phone reboot automaticaly and hard reset himself...
can you please support me not to trash this nice phone?
thank you very much for your support
MS

CrazySE said:
Dear all
i always follow this community with interest but now i have to bother you with a problem.
I have a ZTE AXON 7 that after a while started to give me the message system ui has stopped
i did an hard reset and it was showing the same message directly after rebooting, it doesn't even allow me to finish the initial configuration (google account etc..) that it reboot and hard reset autonomously.
I decided to flash a stock rom with axon 7 EDL TOOL, i followed your instructions unzipping all the files in the folder FLASH-FULL, i selected flash full edl in in the tool, process finished but same problem, message "system ui has sotpped" continuously showing and no way to finish the configuration of android that phone reboot automaticaly and hard reset himself...
can you please support me not to trash this nice phone?
thank you very much for your support
MS
Click to expand...
Click to collapse
Boot into recovery and delete dalvik cache, cache and data

CrazySE said:
Dear all
i always follow this community with interest but now i have to bother you with a problem.
I have a ZTE AXON 7 that after a while started to give me the message system ui has stopped
i did an hard reset and it was showing the same message directly after rebooting, it doesn't even allow me to finish the initial configuration (google account etc..) that it reboot and hard reset autonomously.
I decided to flash a stock rom with axon 7 EDL TOOL, i followed your instructions unzipping all the files in the folder FLASH-FULL, i selected flash full edl in in the tool, process finished but same problem, message "system ui has sotpped" continuously showing and no way to finish the configuration of android that phone reboot automaticaly and hard reset himself...
can you please support me not to trash this nice phone?
thank you very much for your support
MS
Click to expand...
Click to collapse
My phone resetted itself about 10 -15 times a day a while ago. Especially when connected to the charger. Some apps stopped working and needed reinstalled. That all happened after I took the pone out skiing with me. I assume it was caused by the phone getting moist in my pocket. After a while the reboots stopped and now its working fine again.
Did your phone get moist or wet? Check the USB port for ingress of dust or moisture.
Clearing Cache is a good idea. Also check how much free memory space you got. If your memory is full to the brim you might experience problems with dead memory cells. Have at least 10GB free.
UPDATE:
When replacing the battery which served for 3 years, I whitnessed corrosion on the USB circuit board. Moisture must have got in thru the unsealed USB port. That corrosion attacked the components around the board aswell as the ribbon cable and connector. After cleaning up with isoprop alcohol (and putting in the new battery) the phone behaves like new! It definately runs smoother and snappier, has no more hickups and itle discharge is back way down. Im sure the reboots on my phone were caused by moisture ingress that confused the bottom PCB.