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... .. ;-)
Acer Iconia a100
i Bricked it, it sits at the acer screen. no signs of loading. It responds to all of the vol + power +
scape combinations. I get bootloader error when i try that combination, the sd update just hangs there i
grabbed flexreaver rom and renamed it update with the file type being a zip and still no cigar.
I wanted to run the fastest most bare rom as possible i think the problem was that i did NOT have the
bootloader unlocked. I tried one idea where you run somekind of batch file and on my tab itself it
stated that the bootloader was NOT unlocked. i have no idea where to go from here. When i go into usb
mode or db it does not connect with the computer i cannot see or add or remvoe file, but i can connect
with msdos to run batches.
I have spent hours looking for a solution and found help only in outdated links, foriegn languages
and a500 tutorials. I have an acer A100. Any help offered to me is much appreciated but if you are going
to help me please be thorough and leave me alot of details please, i do not have the understanding
or the command it takes to successfully unbrick my tablet. So.. Any ideas?
kungfaux17 said:
Acer Iconia a100
i Bricked it, it sits at the acer screen. no signs of loading. It responds to all of the vol + power +
scape combinations. I get bootloader error when i try that combination, the sd update just hangs there i
grabbed flexreaver rom and renamed it update with the file type being a zip and still no cigar.
I wanted to run the fastest most bare rom as possible i think the problem was that i did NOT have the
bootloader unlocked. I tried one idea where you run somekind of batch file and on my tab itself it
stated that the bootloader was NOT unlocked. i have no idea where to go from here. When i go into usb
mode or db it does not connect with the computer i cannot see or add or remvoe file, but i can connect
with msdos to run batches.
I have spent hours looking for a solution and found help only in outdated links, foriegn languages
and a500 tutorials. I have an acer A100. Any help offered to me is much appreciated but if you are going
to help me please be thorough and leave me alot of details please, i do not have the understanding
or the command it takes to successfully unbrick my tablet. So.. Any ideas?
Click to expand...
Click to collapse
I think we need a lot more information in a clear manner.
From the beginning, what did you do? Do you have ICS or HC? Rooted? Did you try to unlock the boot loader? Try to install a recovery?
What batch file did you run, what was it for?
At what point in all of those answers did it stop booting?
Have you hard reset?
You say the computer can not see it but say you can run batch files on it, which is it? Are they seeing it or just running anyways? What boot loader version does it say in the upper left corner?
All if this information provided clearly will tell us exactly where you stand and if it can be corrected.
Tapatalked from my Galaxy S II.
boot loader v0.03.06-ics:starting fastboot usb download..
I had the tablet rooted and i had not updated to the OTA update.
i have only tried the vol+power combos and i tried to rename a rom to update.zip so i could do that update reboot thing and it just hangs..i tried a pin the reset hole still nothing..
i had tried zeronulls bootloader unlock at that point was when my tablet bricked.. since then ive tried to run fastboot_recovery but it doesnt work. i can connect my device with usb and it will respond to certain batches acer a100 unbrick (a100-recovery-win/a100-push-tools) but i cannot access any of the files on the sd card through my computer.
kungfaux17 said:
boot loader v0.03.06-ics:starting fastboot usb download..
I had the tablet rooted and i had not updated to the OTA update.
i have only tried the vol+power combos and i tried to rename a rom to update.zip so i could do that update reboot thing and it just hangs..i tried a pin the reset hole still nothing..
i had tried zeronulls bootloader unlock at that point was when my tablet bricked.. since then ive tried to run fastboot_recovery but it doesnt work. i can connect my device with usb and it will respond to certain batches acer a100 unbrick (a100-recovery-win/a100-push-tools) but i cannot access any of the files on the sd card through my computer.
Click to expand...
Click to collapse
Go to where it says download protocal then in the folder with adb and fast boot from those zips you downloaded open a command prompt, CD to that folder then type
fastboot oem unlock then get ready for the volume keys.
You missed the unlock that's probably why it got jammed up.
So....find the folder you unzipped the boot loader unlock stuff to, copy it to c:\unlock
Open a command prompt, type
cd c:\unlock
Then type
fastboot oem unlock
Place one hand on the tab so you have a finger on each volume button
Hit enter
On the tab press volume up then volume down (furthest from lock switch then closest to lock switch) as soon as the unlock screen comes up.
Gotta be quick if you miss it try again.
Tapatalked from my Galaxy S II.
ha! youre amazing!.. i got it.. ok, now then it still hangs at the acer screen but now it says bootloader version 0.03.06-ics (unlock mode)
what do i do next?
kungfaux17 said:
ha! youre amazing!.. i got it.. ok, now then it still hangs at the acer screen but now it says bootloader version 0.03.06-ics (unlock mode)
what do i do next?
Click to expand...
Click to collapse
Maybe hard reset or just install a custom recovery and then install a custom rom or something lol limitless possibilities now.
Tapatalked from my Galaxy S II.
Acer A100 BRICK NEED ADVICE
marvz_tech said:
Acer A100 BRICK NEED ADVICE
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=27938361
Brick thread, good place to browse.
Tapatalked from my HTC DNA - ReVolt
Hello,
I seem to have really messed up my G3 and after days of research I have not been able to get anywhere with it. I've read posts of people having similar issues, but their solutions do not seem to work for me.
What I tried to do is flash the ROM, starting with TWRP. After installing TWRP and rebooting I was getting the "no command" message on the screen. I believe (this was days ago), I used ADB to remove laf and reboot the phone (for some reason I could not back it up). The phone rebooted in fastboot and it has been downhill from there.
No download mode. When normally started the phone just hangs on the LG logo. Vol- and power gets me to the "Factory data reset", but if I do that, it flashes "erasing" for a second and it goes back to the LG logo screen.
I can get to fastboot, however, any command that I enter in CMD or Linux terminal just shows up on the phone's screen and it does not do anything. Fastboot devices shows the device as "????????" in Linux and as "?" in Windows. I have tried multiple drivers for Windows.
I tried BoardDiag (3 or 4 different versions running as admin) and shorting the pins, but any time I try to run the checks, I get an error - "No response from device" or "Device was not found in dload trying flash programmer"
I also tried SmartBootDiag, but once it detects the phone, it does its checks and it disconnects the device, without giving me an option to flash anything. Looking at the logs, it does not find any anti-rollback issues.
Any suggestions would be greatly appreciated as I am not sure what else to try.......
Thank you.
Anyone??
Hello everyone! So... I rooted my ZE551ML when I got it about a month ago and today an update pop-up from Asus shows up. So I said "what could go wrong?" .... How about everything?? Basically, I tried a bunch of different things because I could access via ADB, so I tried to unroot it with a bat file I found with a guide for that, but nothing. Now, I passed from black boot screen with white logo to white boot screen with black logo and I can't connect it with adb nor recovery mode. Is there something I can do to enter recovery? With the normal "volumeUP+power" I get nowhere. Can anybody help?
mikla90 said:
Hello everyone! So... I rooted my ZE551ML when I got it about a month ago and today an update pop-up from Asus shows up. So I said "what could go wrong?" .... How about everything?? Basically, I tried a bunch of different things because I could access via ADB, so I tried to unroot it with a bat file I found with a guide for that, but nothing. Now, I passed from black boot screen with white logo to white boot screen with black logo and I can't connect it with adb nor recovery mode. Is there something I can do to enter recovery? With the normal "volumeUP+power" I get nowhere. Can anybody help?
Click to expand...
Click to collapse
hope you can access fastboot. if yes you can install recovery and ifwi files from fastboot
How do I start fastboot mode? I let it charge all night and my pc does the "device connected/disconnected" sound all of the time, but adb says no device (the drivers are ok, I tried before). I have to say that I tried to flash boot.img, droidboot.img, recovery.img and system.img. Problem is, while I was downloading those files I found 2 other methods for recover it, one was to unroot it and the other to unlock the bootloader.... And I tried. Now, I'm unable to enter recovery.
Edit: I tried this guide http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 and for a short period of time (about a second or 2) I can see another device under the "Intel SOC" in device manager, but xFTSK cannot see the phone, even when it shows up for just a second on device manager.
Edit2: holding power down and plugging in the usb cable allows xFSTK to see my device, I put in the files and begin downloading, everything is going good but then it says
07:24:01 - XFSTK-LOG--Windriver Error: 0xC0000011, HC status: The host controller has set the Transaction Error (XactErr) bit in the transfer descriptor's status field
And from there it just starts all over again until it fails definetly.
Edit3: I'm trying the hell out of this software. I attach 2 logs to this post with relatives configurations. Still waiting for help.
Using xfstk tool
mikla90 said:
How do I start fastboot mode? I let it charge all night and my pc does the "device connected/disconnected" sound all of the time, but adb says no device (the drivers are ok, I tried before). I have to say that I tried to flash boot.img, droidboot.img, recovery.img and system.img. Problem is, while I was downloading those files I found 2 other methods for recover it, one was to unroot it and the other to unlock the bootloader.... And I tried. Now, I'm unable to enter recovery.
Edit: I tried this guide http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 and for a short period of time (about a second or 2) I can see another device under the "Intel SOC" in device manager, but xFTSK cannot see the phone, even when it shows up for just a second on device manager.
Edit2: holding power down and plugging in the usb cable allows xFSTK to see my device, I put in the files and begin downloading, everything is going good but then it says
07:24:01 - XFSTK-LOG--Windriver Error: 0xC0000011, HC status: The host controller has set the Transaction Error (XactErr) bit in the transfer descriptor's status field
And from there it just starts all over again until it fails definetly.
Edit3: I'm trying the hell out of this software. I attach 2 logs to this post with relatives configurations. Still waiting for help.
Click to expand...
Click to collapse
open Xfstk Tool and click Tab -MRD/AO/BO +MOOR Ao+CRC then go to settings under option menu - enable GP Flag Override Option and Enter value - 0x80000807 and save (OK), then choose files -
FW Dnx - dnx_fwr.bin
IFWI - ifwi.bin
OS IMAGE - droidboot_dnx.img.POS_sign.bin
AND connect phone, press begin and Xfstk tool detect the phone and install the required files and you will able to get Normal Fastboot mode and install the firmware by fastboot / Asus Flash tool / or -SDUPDATE Zip file.
-------------------
Press Thanks Button, If i am helped you
-------------------
In the end, after about 20 times, XFSTK did flash what should have. Now, I'm back in business. I changed nothing, just kept trying.
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?