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 ?

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

My LG died ... maybe. sry for my english help me please

Good evening,
That I had already come to you last summer because I had managed to bricking my LG.
Now I got new adventures ... If you have an idea, please ...
Let me explain, having broken my screen, I'm ordering one, when I received it I noticed that he was writing D800 on one party. I then contact the vendor who told me it was "fit", so I still do the replacement. After that the phone did not want to come out of standby (but the backlight is lit yet); and occasionally, white stripes with a focal effect.
I say that with a little luck it was a software concern. I reinstall an update CM days that the manager had automatically upload at a time. Then the phone remained bootloop on the LG logo.
So surely very intelligently I wanted to zero all over again, and so I reinstall the recovery to date (http: //forum.xda-dev...-tools-t2898705) and then install rom ..
So then the real trouble begins, I had more access to recovery and against it as going longer in the sequence of boot, until optimazation App and continually turned round: restart, optimization, restart. ..
So I told myself last solution KDZ flash tool, not quite knowing what version take KDZ file I got the following: UK EE D80230b.
And since I have nothing, no download mode, no recovery, and even no screen! just the backlight that lights up.
Help please

edit :
and when i'm plug it in, in the device manager its say : USB MTP and LGE phone ... but no bulkmode or something

Try reinstalling your broken screen or another screen matching the model of your device. If it works then you're set. But if it doesn't, replace the d800 screen with the correct screen and try flashing cyanogen or another rom for your model. Thats all I have goodluck I hope you manage to fix your phone.
---------- Post added at 02:45 PM ---------- Previous post was at 02:44 PM ----------
butinside said:
Try reinstalling your broken screen or another screen matching the model of your device. If it works then you're set. But if it doesn't, replace the d800 screen with the correct screen and try flashing cyanogen or another rom for your model. Thats all I have goodluck I hope you manage to fix your phone.
Click to expand...
Click to collapse
I meant flashing another rom which you are completely sure is compatible with your phone.

XZ Premium Dead

Hey guys,
My XZ Premium updated to 9.0. Since then I started to have many problems.
Yesterday a messagage appeared: Your phone is corrupt, it may not work properly. It can't be trusted.
Hours later it frozed and turned off. Now it's not responding to anything. The led isn't working and the device manager shows it as SOMC Flash Device.
The comands pressing volume buttons while I connect the USB cable are not working either.
Can I save it? I bought it three months ago :crying:

First, try to repair it with Sony Companion and Newflasher. if those not work return it to your dealer or ask for a repair under warranty.

Styler911 said:
First, try to repair it with Sony Companion and Newflasher. if those not work return it to your dealer or ask for a repair under warranty.
Click to expand...
Click to collapse
I alredy tried. It's not working. I bought in a different country that I live now. I can't use the local warranty.

first of all try a factory reset if the phone not modified.
If you have TWRP installed, wipe the phone out of TWRP.

Probably water in usb port then charging caused it

it cant hurt to try have you tried pressing volume up and power together until you get 3 vibrations?

mad0701 said:
first of all try a factory reset if the phone not modified.
If you have TWRP installed, wipe the phone out of TWRP.
Click to expand...
Click to collapse
I don't have the TWRP installed. The device is not responing via PC.:crying:

stipi69 said:
it cant hurt to try have you tried pressing volume up and power together until you get 3 vibrations?
Click to expand...
Click to collapse
The device is not responding to any command that I try...

amakuramio said:
Probably water in usb port then charging caused it
Click to expand...
Click to collapse
It never get wet, and when it does I make sure that no water remains....

Can you see your phone in the Systemcontrol? If yes: does the device is valid or does the device has an Akklamation Mark "!" beside? Maybe you must install the fastboot driver?
---------- Post added at 08:42 AM ---------- Previous post was at 08:37 AM ----------
on other hand:
try the Flash tool (Version 0.9.2.5.0) with a ftf file.
With this you can also change the version of country, remove a branding or viversa....
You will find links to the tool and ftf here in the forum

mad0701 said:
Can you see your phone in the Systemcontrol? If yes: does the device is valid or does the device has an Akklamation Mark "!" beside? Maybe you must install the fastboot driver?
---------- Post added at 08:42 AM ---------- Previous post was at 08:37 AM ----------
on other hand:
try the Flash tool (Version 0.9.2.5.0) with a ftf file.
With this you can also change the version of country, remove a branding or viversa....
You will find links to the tool and ftf here in the forum
Click to expand...
Click to collapse
It only appears as SOMC Flash Device. The ADB or Flash Tools can't get access to the internal memory. I know there's a way to access the internal memory. Just don't know which one yet.

It looks like a coincidence. Hardware not be working may be the real issue.
If you find a knowledgeable repair shop, they can clear your flash and install the original Sony shipped OS for a little money. Most of the time this is done from the USB after a factory reset explained by others here. However, if the USB port is not working then accessing the flash needs opening the unit which will cost you.
And then if the hardware has failed, none of this would help anyway.

What's happen, if you press for 6 Sec or longer Power and Volume up together?

Lenovo Tab M10 FHD Plus (X606f) won't power on after flashing older ROM

I'm flashing my new Lenovo tablet with Android 9 (so I can flash it later with Ubuntu Touch) and after SP Flash tool finished flashing
tablet won't power on. The power button does nothing and holding volume down + power button does nothing either.
The battery isn't dead so I'm trying to figure out why the tablet won't come on if older ROM is on it.
I had no error outputs during the flash.
This is the ROM I flashed https://mirrors.lolinet.com/firmwar..._Gen/TB-X606F/TB-X606F_S300007_200923_BMP.zip
Any suggestion as to how to get it to work again ?

I don't think you can downgrade these. You may need to completely wipe and reinstall the ROM.

ldeveraux said:
I don't think you can downgrade these. You may need to completely wipe and reinstall the ROM.
Click to expand...
Click to collapse
I'm using the official Lenovo's Rescue Tool but it's not helping. The tool isn't detecting the device after holding volume up + connecting.

python_rocks said:
I'm using the official Lenovo's Rescue Tool but it's not helping. The tool isn't detecting the device after holding volume up + connecting.
Click to expand...
Click to collapse
assuming windows, check that your drivers are detecting the recovery module

ldeveraux said:
assuming windows, check that your drivers are detecting the recovery module
Click to expand...
Click to collapse
Yes I'm using W10. adb is working and I've got Lenovo USB drivers installed too. What do you mean by "recovery module" ? Recovery partition inside the tablet ?

python_rocks said:
I'm flashing my new Lenovo tablet with Android 9 (so I can flash it later with Ubuntu Touch)...
Click to expand...
Click to collapse
Cool. Are you doing a Halium port for this device?

Yahoo Mike said:
Cool. Are you doing a Halium port for this device?
Click to expand...
Click to collapse
I'm not a Halium dev but I'm trying to flash the device. Me and another member of the community have our tablets dead after flushing it with supposedly Android 9 ROM. Not even Lenovo's Rescue Tool is helping now.

python_rocks said:
Yes I'm using W10. adb is working and I've got Lenovo USB drivers installed too. What do you mean by "recovery module" ? Recovery partition inside the tablet ?
Click to expand...
Click to collapse
No i mean when you connect the tablet to the pc in recovery, open Device Manager and ensure the tablet is connected with the correct driver. I'm sorry i don't know what that is offhand, but it should be different than when you connect it if the tablet was working. Sorry if it makes no sense, but i think this is what's going on.

ldeveraux said:
No i mean when you connect the tablet to the pc in recovery, open Device Manager and ensure the tablet is connected with the correct driver. I'm sorry i don't know what that is offhand, but it should be different than when you connect it if the tablet was working. Sorry if it makes no sense, but i think this is what's going on.
Click to expand...
Click to collapse
In my case there's no "connect the tablet to the PC in recovery". The tablet won't power on at all. Can't invoke fastboot nor recovery. The tablet doesn't react to any presses. Or press and holds. No nothing. The only thing I can confirm is the red LED on when the tablet is on charger.
Window's device manager is recognizing MediaTek USB driver when plugged in but that's it.
I've ran out of ideas about how to restore it hence I'm posting here.

python_rocks said:
In my case there's no "connect the tablet to the PC in recovery". The tablet won't power on at all. Can't invoke fastboot nor recovery. The tablet doesn't react to any presses. Or press and holds. No nothing. The only thing I can confirm is the red LED on when the tablet is on charger.
Window's device manager is recognizing MediaTek USB driver when plugged in but that's it.
I've ran out of ideas about how to restore it hence I'm posting here.
Click to expand...
Click to collapse
Oh i misunderstood completely! That is worse, i have no clue how to fix it...

python_rocks said:
The tablet won't power on at all.
Click to expand...
Click to collapse
If it's that dead, then it sounds like the preloader.bin is trashed.
Try this method.
There is also an older thread for older SOCs that might have some hints.
Otherwise, you might have to open up the tablet.
You could research and try the "test point" method. It involves shorting two points on the motherboard. I did something similar for the X605F (which has a QCom SOC).
I'm not sure where the test points on this tablet are. Some MTK devices don't have test points. Google "mediatek test point" for starters. If you can't find them, then maybe ask Lenovo where they are. If you find out, post a photo of the test points on here.
If you're not confident doing any of this, then send the tablet to Lenovo for repair.

Yahoo Mike said:
If it's that dead, then it sounds like the preloader.bin is trashed.
Try this method.
There is also an older thread for older SOCs that might have some hints.
Otherwise, you might have to open up the tablet.
You could research and try the "test point" method. It involves shorting two points on the motherboard. I did something similar for the X605F (which has a QCom SOC).
I'm not sure where the test points on this tablet are. Some MTK devices don't have test points. Google "mediatek test point" for starters. If you can't find them, then maybe ask Lenovo where they are. If you find out, post a photo of the test points on here.
If you're not confident doing any of this, then send the tablet to Lenovo for repair.
Click to expand...
Click to collapse
Yeah, I've ordered opening kit. I'm going in. Quite a few people got their devices working by disconnecting the battery and connecting it back. I've noticed that no matter how long the
tablet is on charger the LED stays red, it doesn't change to orange or green.
This same problem has happen to two more members of the community. Same tablet.
We had to flag that ROM as it bricks the tablet.

python_rocks said:
We had to flag that ROM as it bricks the tablet.
Click to expand...
Click to collapse
I don't have a lot of experience with the SPF tool, but could the root-cause of your problem be that you need to use a different dropdown option? See the description of the options in the unbrick guide - specifically the firmware upgrade option.
It makes sense that you want to force a full flash of low-level firmware when changing Android versions. That option seems to do exactly that.
Android 9 OS is not going to play nice with low-level firmware written for Android 10.
There might be nothing wrong with the ROM ??? ...just an idle thought.

Yahoo Mike said:
I don't have a lot of experience with the SPF tool, but could the root-cause of your problem be that you need to use a different dropdown option? See the description of the options in the unbrick guide - specifically the firmware upgrade option.
It makes sense that you want to force a full flash of low-level firmware when changing Android versions. That option seems to do exactly that.
Android 9 OS is not going to play nice with low-level firmware written for Android 10.
There might be nothing wrong with the ROM ??? ...just an idle thought.
Click to expand...
Click to collapse
Thank you for trying to help.
The flash tool doesn't do anything when I click Download and plugging in the tablet while holding the volume down button. Dropdown option was set to "firmware upgrade" as advised.
The guide suggests that it's for people who can at least power on the device. It says "switch off the phone ..." which I don't need to do since I can't even switch it on

python_rocks said:
I'm flashing my new Lenovo tablet with Android 9 (so I can flash it later with Ubuntu Touch) and after SP Flash tool finished flashing
tablet won't power on. The power button does nothing and holding volume down + power button does nothing either.
The battery isn't dead so I'm trying to figure out why the tablet won't come on if older ROM is on it.
I had no error outputs during the flash.
This is the ROM I flashed https://mirrors.lolinet.com/firmwar..._Gen/TB-X606F/TB-X606F_S300007_200923_BMP.zip
Any suggestion as to how to get it to work again
Click to expand...
Click to collapse
Did you mange to fix it?

A. Alaska said:
Did you mange to fix it?
Click to expand...
Click to collapse
You need to use a rework station heat gun or maybe a hair blow dryer might work to heat the sides of the screen to remove it.
I recommend cutting a water bottle in a square or rectangle shape then using the corner to slowly pry the screen off. After that remove the battery ribbon and hold the power bottom for 20-60 seconds to fully drain the charge.
Then recconect it and turn it on 100 percent works.
Just remember you must have the flash tool app and firmware ready in upgrade or download mode while holding down vol. It will reflash the tablet and bam will unbrick.

Just to note down my experiences here as well. I now also got into the same trouble. I tried
TB-X606F_S100015_191127_BMP.zip and also TB-X606F_S300091_201215_BMP.zip
It turns out that with these two you cannot start up the device anymore. Just as the thread-creator described. In my case pluging out and in again seems to give the SP FalshTool the chance to flash again (put it in "Download"-Mode before). So the latest firmware by today - TB-X606F_S300429_21110_BMP.zip - helped me to revive it again.
For me this is nice, but I also wanted to put Ubuntu touch on it just as described here: https://gitlab.com/ubports/community-ports/android9/lenovo-tab-m10-fhd-plus/lenovo-x606 ... unfortunately I am blocked now due to not being able to bring Android 9 on it. btw: There is no proposal on the site which firmware-version is even Android 9. I just guessed from the date.