Related
Hi.
I was recently experiencing some problems with my desire and I believe that I might have rushed into bricking it.
I woke up the day of the bricking. I had just installed the newest version of GingerVillain (version 2.4). My phone had run out of power the day before so I started recharging it. After it had charged for a couple of hours I went to the market to update some apps. During the update my phone suddently rebooted. I thought that it was nothing and went back to the market and continued updating. A few minutes later it rebooted agian. It kept on rebooting with less and less time in between after each attempt until it chose to reboot at the splash screen continuesly.
This is when I thought of starting the phone in recovery and do a NAND restore. As I tried to enter the recovery mode the phone froze at a black screen. I pulled out the battery and retried a couple of times without success.
I read a little on the internet about ADB and tried doing some stuff but I kept on getting errors when running commands in the tools directory. At this point I was getting desperate because I needed the phone to work as I was expecting an important call. I tried flashing a new RUU (through the installer on my PC) while the phone was in fastboot (but without using any ADB and CMD stuff). After this installation almost had finished I got an error saying that the version of the rom wasn't the right one for my phone and the phone shut off.
Since then I haven't been able to boot it into bootloader or even boot it at all. Whenever I hold down power + volume down nothing happends and if I try only pressing the power button the phone vibrates and other than that nothing else happends. Not even the screen turns on.
I since then set up ADB and got it working. I then tried to see if the phone was still able to fastboot through the following commands:
Code:
adb devices
and
Code:
fastboot devices
but found that this was not the case.
Whenever the battery is in the phone though, the bottom of the phone starts to get warm, a little like it's actually using the battery to perform some actions or something. I was also able to recharge it through my computer.
I really need a phone and as it seems I have got my hands on a spare one, but only for a limited time. I'm really thinking of handing it in to the HTC Concept Store so they can send it to the repair department and hopefully get it back as fast as possible.
Its seems.. S-LCD Brick
try This
http://forum.xda-developers.com/showthread.php?t=748498
or
http://forum.xda-developers.com/showthread.php?t=831734
Ohh dude! I BELIEVE YOU MIGHT JUST HAVE SAVED MY LIFE! TY! TY! TY! TY!
My stationary just killed itself because of the hot weather and a little bit too much work. If I was going to hand in my phone and they couldn't repair it since I had "destroyed" it, I would be forced to buy a new one, and with that I wouldn't be able to afford new components for my stationary.
I will get right on with trying this method as soon as I get home and then I will give feedback asap. It will probably be the most fun "digging in the dark" I will ever do if it turns out to work.
I was almost sure I had killed my beautiful phone, and with it only being a couple of months old that would have been a pain in the ass.
Once again TY so much!!
I have been at this for almost 4 hours now and still no result. I believe the guides could have been more noob friendly. I've been to hell and back reading all the kinds of guides out there to get it all to work and now I'm tired and believe I won't be able to fix this, or atleast doesn't have the capacity to keep on trying.
I pretty much believe that I had this SLCD-brick, but trying out different RUU's is killing me inside and stealing my time. I'd rather just hand in the phone and recieve it as it was from the beginning again to start all over.
Trying to repair a smartphone with a blackscreen is is not something I have the capacity to do. Besides I have my recently deseased stationary computer to take care of as well.
I do have a goldcard, pushed the PB99IMG.zip file to my /sdcard/ through adb and tried starting up fastboot and do as described here.
But somehow I did not find any changes to the problem and the guide itself was wierdly written although the only guide I could find on this problem.
But now I'm giving up. I seriously just hope they will repair my device at no cost.
Regards,
Me
Man.. what happen when you connect your mobile to PC.. is it showing android device and under that bootloader interface.. dont lose hope... lets try some steps...
connect your mobile to PC and see in your device manager.. can you see android.. if yes than your driver are installed...
than remove the phone from pc.. take out the battery.. and put back battery.. and start by volume down and power.. and than after 10 sec just press power button again.. and connect to pc again... and cehck device manager.. and you should see the same if not.. than install your adb driver.
Point is.. install ADB driver.. when you are on hboot screen.. as well fastboot screen..
Than your RUU will detect your phone.
Well I tried all the steps for this. I can see the phone when booting it with the following combos:
Code:
1: Volume down + Power
2: Power
1: Volume down + Power
2: Volume down
3: Power
When using the first method I should as far as I can understand myself enter fastboot and the other one is recovery. Even when running the fastboot devices / adb devices commands in ADB it tells me what state my devices in, that is either fastboot or recovery. So that's for certain.
I tried running the following RUU when I had connected my device with fastboot:
RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed.exe
The RUU found my device and I ended up with a 140 Error. I read in some guide that this error could be to blame of different windows drivers so I tried grabbing the rom.zip from the RUU (from Temp folder) and renamed it to PB99IMG.zip and put it on the phone. As I couldn't get access to my SD card since I can't see what's on my screen in fastboot and recovery mode I used:
Code:
adb push PB99IMG.zip /sdcard/
with the PB99IMG.zip placed in my tools folder for the transfer. It completed and now the PB99IMG.zip should be placed on the root of my sdcard.
As a notice I live in Denmark and the above RUU should as far as I can understand be the one I need and should as well be SLCD compatible.
When I try to trace the steps in the "not able to see your screen guide" placed here I get none of the desired outcomes:
http://forum.xda-developers.com/showthread.php?t=880268
I find the guide a little but confusing though. When to use the right commands to trace through a black screen fastboot/recovery and stuff isn't really "noob"-friendly.
When I tried using the following command I didn't get the desired result either:
Code:
fastboot oem gencheckpt
Which should return a HTC_<number> that could tell me whether my phone is branded or not, but instead resulted in an error. As far as I can remember I did make my sdcard a goldcard when I rooted my phone, without knowing whether I would need it, so this number should be irrelevant. So I kept on going at this point.
I have basicly tried everything that I can find guides for and have traced all the steps in detail as far as I understand the guides anyhow. I feel like at a dead end. I am having doubtsg whether the PB99IMG.zip is run when I boot my phone.
Having a clean slate (but still the PB99IMG.zip on the sdcard I have now tried the following:
Code:
Volume down + Power
Windows reported a connected Android 1.0 device and the Android Bootloader Interface.
Power once more (should now be in fastboot)
fastboot devices
confirmed the above, but using ADB devices only return a result if the phone is in recovery mode
So far so good..
I'll give this one more day which will be when I return home at 17:00 today. Then I'll head to tech support at my HTC Store.
Good.. i think you should try this RUU
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.exe
As error 140 is for wrong bootloader.. so try this RUU.. n try to run RUU from PC rather than putting PB99IMG into sd..
jhonybravo4u said:
Good.. i think you should try this RUU
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.exe
As error 140 is for wrong bootloader.. so try this RUU.. n try to run RUU from PC rather than putting PB99IMG into sd..
Click to expand...
Click to collapse
Okay. I'll try this and should I run it while in recovery like I did with the other one?
Does it matter if my SD card is out of the phone?
EDIT 1:
I tried with the sdcard out of the phone and with the RUU installed through windows. I now see a HTC Logo on the screen.. and an installing bar below the logo.. Seems like you were my divine interception mate.. ty a lot. I will write once the installation is done.. whether or not it succeeds.
EDIT 2:
My phone is now working. Booted with HTC Sense and a pin code request. Currently setting it up.
I guess I should now be able to re-root it again and get back to the state I was in before I SLCD-bricked it.. or what?
And in what way do I easiest remove that PM99IMG.zip file from the sdcard..? I booted my phone without the sdcard in it to avoid it running the PM99IMG.zip file..
One little question more.. I don't have any phone signal.. could this be to blame for the radio? I can connect to wifi though.. or can I simply run that other RUU I used earlier with the bootloader error to get back my signal?
So happy right now..
EDIT 3:
Nvm. I tried shutting down the phone, put in the sdcard, boot it up again. I found that the ADB push command on that PM99IMG.zip file didn't work. The file wasn't there.. and I suddently got back my signal. Only question is, can I now re-root it again and get back to my previous state without any problems?
Yes Ofcourse you can re root it.. with Unrevoked rooting wont be a big problem... and as soon as you root... just take a nandroid backup from it and be safe..
Enjoy the victory you earned... .. ;-)
Hey guys, I was flashing a rom on my One x but for some reason it got stuck in a bootloop. After that, I tried restoring to my earlier rom using CWM but I forgot to flash the boot.img from cmd first so it didn't work. After that I tried restarting my phone but it wouldn't turn on after turning off. When I plug in my charger the red light comes up but I can't turn it on. I left it to charge for a few hours but it still won't turn on, the only sign of it working is that it vibrates when I attempt to turn it on. I also tried connecting it to my pc and it senses it but I get no results when I type adb devices in cmd. Can someone please help me with this issue? Thanks!
What can you see in windows device management? Does
Code:
fastboot devices
give you any info?
No, nothing, but when I connect to pc it says installing device software
Oh yeah, I also forgot to mention that it did turn on before and I got into the bootloader but then it turned off again
I mean the device management in the control panel. It should be there if it says something about drivers.
It says MTP USB Device
What ROM are you on?
I was attempting to flash Blade rom when it got stuck in bootloop
MTP should be only available when the phone is booted. I really don't know what is the problem here, sorry.
Ok, Thanks anyway
I just restarted my pc and after running cmd and entering adb devices I get: SH24KW107359 recovery. But the phone is still off. Any ideas?
If the phone vibrates and your computer sees it like MTP that it might be a hardware failure. Contact HTC for further assistance, or try search the forum. I am sure many faced the same problem, and some got it working finally.
I'm no longer getting MTP, it now says E:\
Wait, were you on android 4.0.4 just before you tried flashing Blade?
BlueSingA said:
Wait, were you on android 4.0.4 just before you tried flashing Blade?
Click to expand...
Click to collapse
No, I was not. At least I don't think so. It's my sisters phone so I'm not sure. Why?
I believe that the phone is switched on, but the screen remains off. Try this:
Code:
fastboot getvar all
I tried turning it on and it turns on then it shows the HTC logo, then when I try to get into CMW it shows a dark screen but u can tell its on.
Ok, if your in cwm, from a cmd prompt run:
adb reboot bootloader
That should put you in the bootloader.
From there use fastboot to flash the kernel to boot as you should have done earlier.
When your done just:
fastboot reboot
-SLS-
When I type fastboot devices in cmd i get: SH24KW107359 fastboot. Can I flash a boot.img by using fastboot flash boot boot.img?
Yes, and also reflash cwm. Dl from clockworkmod site and flash using:
fastboot flash recovery nameofthefile.zip
Sent from my HTC One X using xda app-developers app
Ok, to begin with I bought a second hand Desire yesterday. The phone was sim-locked therefore I decided to unlock it using the Sim-unlock utility available here.
When I first tried to unlock it, the phone restarted and gave me 7 vibrartions. After that the phone was going all sorts of crazy. Sometimes it would start and stuck at HTC start screen, sometimes it would load the operating system and then restart.
Therefore, I decided to ask for info at the HTC Desire SIM-Unlock Utility thread that can be found here:
http://forum.xda-developers.com/showthread.php?t=943726&page=157
starting from post 1567.
Please read what happened up to post 1575.
The phone doesn't switch on anymore..
Any help would be much appreciated
Won't switch on at all? Not even in hboot?
Does the led blink when you plug it in?
The vodafone_uk RUU wasn't the best choice you have taken...
yes, the led switches on when its plugged in
Pull out the battery, push the power button for 5 seconds, put the battery back in place, and try booting in hboot.
No, not responding.
Update:
Ok, I have noticed, when i plug the phone in, the computer recognises the phone. ( I get the sound that a usb is plugged in)
However, the screen's phone doesn't switch on.
You flashed the wrong RUU for your type of screen.
Try flashing the 2.3 ruu again.
abaaaabbbb63 said:
You flashed the wrong RUU for your type of screen.
Try flashing the 2.3 ruu again.
Click to expand...
Click to collapse
Ok, this is what's happening now.
I created a goldcard, as I fugured, maybe the phone was branded to vodafone.
Now since I can't see whats happening i decided to flash the new rom via my computer.
I am trying to flash RUU_HTC Desire Android 2.3 Upgrade (Gingerbread).exe.
I get to the point where it says:
From
Image Version: 2.29.405.5
To
3.13.405.1
Now to reach there I assume that the phone is connected to the computer. But as it installs, the installation stops and says Error 107:USB not found.
What should I do??
U shoulda just used the PB99IMG.zip of the 2.3 gb upgrade. No computer errors... just make sure u have enough charge on the battery.
jmcclue said:
U shoulda just used the PB99IMG.zip of the 2.3 gb upgrade. No computer errors... just make sure u have enough charge on the battery.
Click to expand...
Click to collapse
Ok, i appreciate your advice.
However I do not have any access to my screen what so ever and therefore I cannot install this from my sd card.
Try this..
Download the 2.3 gb upgrade PB99IMG in my sig and put it on ur sdcard (not in a folder) then press and hold volume down + power... Wait 10 minutes then press volume up, then wait another 10 minutes and press volume up. Hopefully ur phone will boot. If not then u will have to keep trying the ruu from ur computer.
jmcclue said:
Try this..
Download the 2.3 gb upgrade PB99IMG in my sig and put it on ur sdcard (not in a folder) then press and hold volume down + power... Wait 10 minutes then press volume up, then wait another 10 minutes and press volume up. Hopefully ur phone will boot. If not then u will have to keep trying the ruu from ur computer.
Click to expand...
Click to collapse
I just tried this, did not work.
Is there any way, from the computer that I can check that the phone is connected with the pc? I mean using commands and stuff.
The weird thing is my computer says that the phone is connected with the pc even if I just power it on. I don't know if its booted in hboot or normal boot.
savvasch1 said:
I just tried this, did not work.
Is there any way, from the computer that I can check that the phone is connected with the pc? I mean using commands and stuff.
The weird thing is my computer says that the phone is connected with the pc even if I just power it on. I don't know if its booted in hboot or normal boot.
Click to expand...
Click to collapse
When I try to update the RUU from the computer, I get stuck where it says "waiting for bootloader" and then I get the Error 171: Usb not connected.
savvasch1 said:
When I try to update the RUU from the computer, I get stuck where it says "waiting for bootloader" and then I get the Error 171: Usb not connected.
Click to expand...
Click to collapse
I did some more digging and I figured how to use fastboot.exe
Now I know that I am connected properly to the phone because I can run the commands:
\fastboot devices
and get:
HT01xxxxxxx
and also
\fastboot reboot-bootloader
and get:
rebooting into bootloader OKAY
Does anyone know how to use fastboot.exe properly and help me out??
UPDATE!!!!
Ok, as I explained, I can connect to the phone via fastboot. However, when I try to flash a bootloader through fastboot i get the error FAILED: REMOTE NOT ALLOWED. Also, if i try to flash the RUU using fastboot I get "Whoops didn't find expected signature read_central_directory_entry failed"
Also, Android Flasher does not allow me to update hboot. It's just stuck at waiting for devices.
Lastly, I figured maybe the device is back to S-ON for some reason and I tried to S-OFF it through revolutionary, but again it's stuck at waiting for devices.
abaaaabbbb63 said:
Won't switch on at all? Not even in hboot?
Does the led blink when you plug it in?
The vodafone_uk RUU wasn't the best choice you have taken...
Click to expand...
Click to collapse
jmcclue said:
Try this..
Download the 2.3 gb upgrade PB99IMG in my sig and put it on ur sdcard (not in a folder) then press and hold volume down + power... Wait 10 minutes then press volume up, then wait another 10 minutes and press volume up. Hopefully ur phone will boot. If not then u will have to keep trying the ruu from ur computer.
Click to expand...
Click to collapse
Just tell me if its hard bricked:
Firstly, i cannot run the RUU from the computer since i get Error 171. So that knocks out choice #1
I did extensively tried performing an blind update through my SD card with no sucess at all. #2 is out
Now regarding fastboot, I have to admit i did try to install the components one by one. However for system.img i get the error "file too large to send" and for everything else ( radio, boot) error "failed to connect with remote".
I honestly run out of ideas
Update 04/03/2013:
I have now solid reason to believe that the device is bricked. I run the Fastboot commander v1.5 which is a GUI interface of fastboot
This is what I get:
Code:
Feedback, criticism, ideas, improvments, thanks and appreciations are welcomed on the forum-thread.
............................................................
Operating system: Windows.
Tools folder found.
Windows fastboot tools found.
The folder containing the IMG files was not found.
No Nandroid folder was not found - "Restore" button disabled.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 0.80.0000.
Radio version: 4.06.00.02_2.
Main software version: 2.29.405.5.
cid: 11111111.
cpld: .
-----------------------------------.
PRINT OF DEVICE INFO FAILURE - PLEASE CHECK YOUR CONNECTION.
-----------------------------------.
HT091PL00003 Connected.
-----------------------------------(note: here I forced the phone reboot into fastboot).
Rebooting device.
Reboot SUCCESSFUL.
-----------------------------------.
HT091PL00003 Connected.
-----------------------------------.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: failed.
Radio version: failed.
Main software version: failed.
cid: failed.
cpld: failed.
getvar:product failed (command write failed (unknown error)).
getvar:mid failed (command write failed (unknown error)).
getvar:security failed (command write failed (unknown error)).
getvar:build-mode failed (command write failed (unknown error)).
-----------------------------------.
Print of device info SUCCESSFUL.
This device does not have s-off nor eng hboot.
ARE YOU SURE THAT THIS IS THE RIGHT TOOL FOR YOU?.
Hboot, radio & recovery files set - FlashAll button enabled.
-----------------------------------.
STARTING FLASH OF CUSTOM FILES.
Flashing "radio" - PLEASE WAIT.
"radio" flash FAILURE.
FLASH OF CUSTOM FILES FAILURE - RADIO FAILURE.
-----------------------------------.
Running fastboot command - PLEASE WAIT.
###Calling fastboot with: oem rebootRUU###
... FAILED (command write failed (Unknown error))
finished. total time: 0.641s
********************************
Hmm... it may either be improper installed drivers, or a radio brick. One has an obvious fix, the other one needs patience and strong nerves, and hope.
First try by reinstalling adb, fastboot and hboot drivers. If that doesn't work, run RUUs like crazy with the hope that it will sometime work
abaaaabbbb63 said:
Hmm... it may either be improper installed drivers, or a radio brick. One has an obvious fix, the other one needs patience and strong nerves, and hope.
First try by reinstalling adb, fastboot and hboot drivers. If that doesn't work, run RUUs like crazy with the hope that it will sometime work
Click to expand...
Click to collapse
I did reinstall the drivers, no luck
The thing is that all 2.3 update RUU stops at "Waiting for bootloader", which results to Error 171: No device found. However this update at least recognises the phone's "OS version" (2.29xxxx)
All other RUU's don't even go that far. They don't even recognise that at least the device is plugged in.
I think that is because I don't have any bootloader at all. I also think that the only think funtioning in the phone is the radio (because the phone charges properly)
And plus I can't see anything going on my screen!!!
Hey I don't know if this is any help but what drivers are you using? Cause I got a second hand desire yesterday that was locked to Vodafone uk and I had trouble getting it to flash ruus and unlock I had to try few different drivers before I could get it to work properly I even tried the generic Google ones but the strange was I could control the phone with adb commands but the ruu still wouldn't work. I ended up using some old htc sync drivers and just had to force install the hboot driver now its working perfectly.
Sent from my HTC Desire using xda app-developers app
andrewtjb said:
Hey I don't know if this is any help but what drivers are you using? Cause I got a second hand desire yesterday that was locked to Vodafone uk and I had trouble getting it to flash ruus and unlock I had to try few different drivers before I could get it to work properly I even tried the generic Google ones but the strange was I could control the phone with adb commands but the ruu still wouldn't work. I ended up using some old htc sync drivers and just had to force install the hboot driver now its working perfectly.
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
What do you mean force install hboot?
In device manager mine was showing up as unkown device when I was in the bootloader so had to click update driver and click have disk and force install the driver.
Sent from my HTC Desire using xda app-developers app
andrewtjb said:
In device manager mine was showing up as unkown device when I was in the bootloader so had to click update driver and click have disk and force install the driver.
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
No, that's not the issue. The driver is properly installed.
The thing is that it when I am trying to flash an RUU, it always stops at "Waiting for bootloader". It's like it doesn't have one.
Hi, I got an M8 from a friend which has a few problems, and I want to find out what is wrong with the device. First, the USB port is a little dodgy, so I have to apply pressure to front of the cable when attached for it to make a connection. It also seems as if the battery isn't charging properly, because I can only get the phone turned on when it's been connected for a while. Then if it desides to turn on, it goes straight into fastboot mode. The phones ROM won't boot, it hangs at the HTC One splash screen. So I've managed to unlock the bootloader, but it won't let me flash the TWRP recovery. It errors saying Bootmagic check fail. I've added a screenshot showing the message. Any suggestions on how to fix this? Or might the device be corrupted beyond repair... Thanks!
Bootmagic error usually means wrong recovery version on a wrong device.
Post fastboot getvar all result, this will show what device you really have.
Hello @All,
I bought myself a new toy: a bricked Nexus 5x. The only thing I can do is enter the bootloader mode. Otherwise the phone is showing the Google logo.
In bootloader mode the last two lines are "Secure Boot - Enabled" and "Device State - Locked". The "fastboot devices" states that the device is present.
I can neither access any recovery nor install one (because bootloader locked). The device isn't rooted. Parallel to posting this I am searching the depths of the web. Of course without a solution.
Can I do anything else?
hmm, did you try going into the recovery and resseting it, if that didnt work go on your computer, go to bootloader mode, and on your computer try typing: fastboot flashing unlock or fastboot oem unlock, if none of those work, then try reflashing the firmware trough recovery or fastboot, here is the rom for adb sideload trough recovery...
here is a direct download cuz it wouldnt post the zip https://dl.google.com/dl/android/aosp//bullhead-ota-mhc19q-8fe67a2b.zip
I can't access the recovery, but I'll try fastboot again. "fastboot flashing unlock" and "fastboot oem unlock" don't work. I get a " FAILED (remote: 'oem unlock is not allowed')" message.
ok, try this, go in fastboot, and run this command, fastboot flash boot N2G47Z_4Cores.img with the img that i send you, if it works, then see if iit boots up!
it doesnt wanna send it, heres a link to download it https://www.dropbox.com/s/tm7qt98r6d7q2a6/N2G47Z_4Cores.img?dl=0
I tried
Code:
$ fastboot flash boot N2G47Z_4Cores.img
and the answer was
Code:
Sending 'boot' (12045 KB) OKAY [ 0.464s]
Writing 'boot' FAILED (remote: 'device is locked. Cannot flash images')
fastboot: error: Command failed
...
But thanks for your effort to help me
Heinz- said:
I tried
Code:
$ fastboot flash boot N2G47Z_4Cores.img
and the answer was
Code:
Sending 'boot' (12045 KB) OKAY [ 0.464s]
Writing 'boot' FAILED (remote: 'device is locked. Cannot flash images')
fastboot: error: Command failed
...
But thanks for your effort to help me
Click to expand...
Click to collapse
hey is there a way you can send me a video of what happens when it boots up and when you try to enter recovery, maybe i can still help.
if you cant here send it to my mail [email protected] , this is my mail since 2016 and zombie was mostly for minecraft . but then i was young, so yeah.
I can only describe it for you...
When I try to boot into recovery it happens the same as booting the system. The Google sign appears with a short buzz of the vibration motor, then disappears after 16 seconds, and a second later the same again. A classical boot loop. I can only access the bootloader mode. When I try to boot from there, the same happens. The "system state" is locked, and Secure Boot is enabled.
I can power off the device from the bootloader, then it stays off.
Is there any hope to bring it to life again, or is it a brick forever?
Heinz- said:
I can only describe it for you...
When I try to boot into recovery it happens the same as booting the system. The Google sign appears with a short buzz of the vibration motor, then disappears after 16 seconds, and a second later the same again. A classical boot loop. I can only access the bootloader mode. When I try to boot from there, the same happens. The "system state" is locked, and Secure Boot is enabled.
I can power off the device from the bootloader, then it stays off.
Is there any hope to bring it to life again, or is it a brick forever?
Click to expand...
Click to collapse
well it looks like a problem with either the ram, vibrator, or the partitions, sadly this happened with old nexus devices, so its a brick forever sadly. but if you want you can sell it online for parts.
Ok then, I hope I can sell the brick. Thank you again for your help, @NikolaTechGuy !
But there's one last hope: This thread, shown to me directly under this answer ("Similar threads") that I'm currently writing. One last try...
Heinz- said:
Ok then, I hope I can sell the brick. Thank you again for your help, @NikolaTechGuy !
But there's one last hope: This thread, shown to me directly under this answer ("Similar threads") that I'm currently writing. One last try...
Click to expand...
Click to collapse
Sorry if this is too late but are you sure you can't do anything with the phone?
To enter Bootloader Mode press and hold Vol Down + Power. You will automatically enter Fastboot Mode. You will see the settings of 'Secure boot' and 'Device State'
Use Vol up and Vol Down to scroll through menu and the Power button to select an option:
Start
Restart bootloader
Recovery Mode
Power Off
If you select Recovery Mode, wait until you see the 'Robot lying down' image and "No command" text appear on screen. Now hold Power button and briefly press the Vol up button. The 'Android Recovery' screen should now appear.
To enter LG 'Download Mode':
Power Off your phone.
Now press the Vol. Up button and hold it
Now Plug your phone into your computer using a USB cable
After a few seconds 'download mode' should appear on your phone screen, followed by a 'Firmware Update' screen.
If it doesn't enter LG Downoad Mode then check in your Windows Device Manager under COM/PORTS. See if you have connected in Qualcomm 9008 EDL (Emergency Download ) Mode. The connection will appear as Qualcomm HS-USB QDLoader 9008. You might have to download the Qualcomm driver for this to work.
If you can get into Recovery Mode or EDL mode you still have options! It depends how much time and effort you want to spend on a 7 year old phone with no sd card option.
You can become 'obsessed' like me, and buy a hot air gun solder rework station to try and reflow the solder under the MSM8992 chip to fix the 'bootloop of death'! NOTE: I have tried it on 3 bricked Nexus 5X and only got a temporary success on one phone - the other two I did a very good job of frying the chip! Mind you I now have alot of spare parts!
I took the Nexus to a repairman who calls himself "Handy-Doc". He told me it was the hardware. He couldn't install anything as well as me. But replacing the motherboard could help. So I ordered a motherboard on AliExpress. This is my last try!
Heinz- said:
I took the Nexus to a repairman who calls himself "Handy-Doc". He told me it was the hardware. He couldn't install anything as well as me. But replacing the motherboard could help. So I ordered a motherboard on AliExpress. This is my last try!
Click to expand...
Click to collapse
You will have to keep us updated. I looked at those motherboards but wasn't sure about them. What version of Android is installed? Do they come with a new IMEI or are they blank? etc. Taking a 5X apart is very straightforward with a couple of simple phone tools. There are plenty of Youtube videos that show you how to do it - it might save you having to pay "handy-Doc"!
No, it doesn't work. I can plugin the phone when it's in "Download Mode" but nothing more happens. After a few seconds the phone tries to boot again. The "Handy Doc" man gave me back the phone without asking for payment.
The motherboard is on its way from China to Germany. This can take several weeks.
Hi
I am sorry if I am posting this at the wrong place.
I bricked my Nexus 5x device flashing DivestOS on it.
I flashed two different LineagOS on this device successfully in the past and the genuine Android when I was rolling it back. It always worked, but not this time.
Trying to roll it back to genuine Android, there were errors that several ".img" was missing in the archive.
I tried to chat with Android developers on Matrix chat and also reported this problem here, on DivestOS forum, but they blame hardware and/or user mistake.
I took it farther to sort the device problem and made it unresponsive, the screen is black and it does not react to anything at all now.
All I needed to know if there is ANY way to bring this device back to life.
I found some "LGFlashTool_2.0.1.6" on one of the old forumes of (2016), but I did not try it, I believe it will not work, and wanted to know from Android developer's oppinion before I try anything else.
Thank you
---Update:
I opened it, unplugged and re-plugged the battery.
Was able to boot it into the fastboot menu.
1. secure boot - enabled
2. device state - unlocked
-Tried to flash the genuine Android (I did it several times and I know it works)
No success!
Please see the terminal screenshot attached for errors.
If you can get into fastboot have you tried flashing TWRP and getting into it again? Then try flashing a lineageOS that you know works.
bjlabuk said:
If you can get into fastboot have you tried flashing TWRP and getting into it again? Then try flashing a lineageOS that you know works.
Click to expand...
Click to collapse
Thanks for reply =).
This is a goot point.
I'll try and post the result here.
Now, not always I can boot it into fastboot menu, sometimes it's totally un-resposive, does not show any sights of life, it can be the battery charge problem (battery was not bad though).
balakarpo said:
Thanks for reply =).
This is a goot point.
I'll try and post the result here.
Now, not always I can boot it into fastboot menu, sometimes it's totally un-resposive, does not show any sights of life, it can be the battery charge problem (battery was not bad though).
Click to expand...
Click to collapse
Yea, looking at the log everything appears to be okay until that last line. Did you use flash-all.bat from the factory image bullhead-opm7.181205.001-factory-5f189d84.zip?