Hey everyone,
I did something really stupid while trying to get a certain app to recognize a codec that it needed in order for it to work and seem to have probably bricked my phone.
Phone Details:
LGH812
Lollipop 5.0.1
rooted
I went to /system/ and renamed lib64 to lib64bak because I wanted to put some new files in there. This caused the phone screen to immediately go black and unresponsive. I took out the battery and re-inserted it. The phone boot logo with LG comes up and then it goes to a black screen with the dead android guy with red triangle and the exclamation mark. No other text is present in this screen. Stays at this screen for about a minute and reboots only to go back to the exact same screen.
Things I have tried:
1.) I tried to boot into download mode (power+volume down) still goes to the aforementioned screen.
2.) Got LGUP to recognize the com port once, but it shows up as unknown and won't let me proceed with a fresh wipe/install
3.) Tried the LG Flashing tool, couldn't even see the com port.
4.) Tried the WHQL universal drivers as well as the specific device drivers with no advancement.
What I believe is happening is that it's trying to boot properly initially, but it can't find lib64 folder so it fails to launch the os and then tries to go into recovery due to error, but fails to go to recovery also because of lib64 is missing.
If anyone has any ideas/things I can try to get it into recovery or download mode or if anyone has seen this state before and was able to fix it please let me know.
Thank you all for your time!
Related
I have been reading these forums ALL day, i have a factory cable and ive done everything I can think of as of now.
Earlier today I pulled the battery out of my kindle fire and put a dead one in its place (not knowing it was dead of course). After I realized the battery was dead I put the old one (100%) charged back in.....thats where everything went HORRIBLY wrong..
When I turn it back on it just goes to the boot screen "Kindle FIre" (non animated), stays there for about 10 to 15 seconds and then flashes and goes right back into the same exact screen. I can get it to go into fastboot with the flashing green traffic light (using my factory cable) but the problem is windows will not identify the device, its listed under the device manager as unknown. when I manually pointed it to the Andoid ADB driver it says error 10 (the device failed to start
I am completely lost, Idk what to do and if anybody can help me I would GREATLY appreciate it. Thanks
F34RCON said:
I have been reading these forums ALL day, i have a factory cable and ive done everything I can think of as of now.
Earlier today I pulled the battery out of my kindle fire and put a dead one in its place (not knowing it was dead of course). After I realized the battery was dead I put the old one (100%) charged back in.....thats where everything went HORRIBLY wrong..
When I turn it back on it just goes to the boot screen "Kindle FIre" (non animated), stays there for about 10 to 15 seconds and then flashes and goes right back into the same exact screen. I can get it to go into fastboot with the flashing green traffic light (using my factory cable) but the problem is windows will not identify the device, its listed under the device manager as unknown. when I manually pointed it to the Andoid ADB driver it says error 10 (the device failed to start
I am completely lost, Idk what to do and if anybody can help me I would GREATLY appreciate it. Thanks
Click to expand...
Click to collapse
Put the device in fastboot and see here:
http://forum.xda-developers.com/showthread.php?t=2088864
Installing Kindle Drivers
F34RCON said:
I have been reading these forums ALL day, i have a factory cable and ive done everything I can think of as of now.
Earlier today I pulled the battery out of my kindle fire and put a dead one in its place (not knowing it was dead of course). After I realized the battery was dead I put the old one (100%) charged back in.....thats where everything went HORRIBLY wrong..
When I turn it back on it just goes to the boot screen "Kindle FIre" (non animated), stays there for about 10 to 15 seconds and then flashes and goes right back into the same exact screen. I can get it to go into fastboot with the flashing green traffic light (using my factory cable) but the problem is windows will not identify the device, its listed under the device manager as unknown. when I manually pointed it to the Andoid ADB driver it says error 10 (the device failed to start
I am completely lost, Idk what to do and if anybody can help me I would GREATLY appreciate it. Thanks
Click to expand...
Click to collapse
I had the same problem and the ONLY thing that worked for me was to copy all driver files to \windows\system32. You will probably find these files at C:\Program Files\Amazon.com\Kindle Fire\Drivers. Just select the 'DLL's from the appropriate flavor of architecture and the android_winusb.inf and copy them directly to \windows\system32. Hope this helps
Hey guys. just tried to flash CM 10.1.3 after some bugs in Carbon started getting on my nerves. Used ROM Toolbox and ended up getting my device stuck in some kind of weird boot loop. The phone boots up with the samsung logo and (recovery booting) text at the top left hand corner. For some reason, it boots up, but nothing on the display. it vibrates every few seconds, but nothing. I tried to boot into recovery manually, but the same thing happens. So i figure I'll just to into Odin and flash my stock copy on, no big deal. For some reason, my PC, nor Odin are recognizing that the GS3 is plugged in and in download mode. No Unkown Devices, nothing shows up anywhere. Anyone know a fix, or am I completely ****ed?
If your PC does not recognize download mode, you can try to check the cable, plug it into a different USB port, or pull your battery and try again.
If none of that works, you are not screwed. Be lucky you have an android It's possible for an android to boot from an SDcard such as a windows boot disk on desktop.
Click V
http://forum.xda-developers.com/showthread.php?t=2439367 DIRECTIONS TO UNBRICK: Their download link for unbrick.img is for T-MOBILE only
http://forum.xda-developers.com/showthread.php?t=2345860 AT THE BOTTOM OF THIS THREAD, contains a link for an AT&T SGH-i747 debrick.img which should work ( I will edit my post when I complete, I am in the process of repairing my old brick now)
I an not responsible for any damage done to the device, or any sudden loss of limbs.
Thanks
So it all started out rather stupidly. I was attempting to flash a new ROM to my phone and I was deleting everything and accidentally deleted the OS by accident (mis-touched in recovery mode). I panicked and I attempted to push a file through adb but it was halting between 4MB - 8MB on a 200MB file. I knew this wasn't right. I ran cmd in administrator mode and tried again and got the same results.
I then moved to ODIN to attempt to flash the ROM. I ran ODIN in administrative mode. Bootloader was unlocked. I attempted to flash the new ROM but it stopped at about 1/8th of the progress (as shown in the download mode). This led to my phone having communication issues with my PC (displayed the phone with a hazard sign on the cord to the PC). I assumed it was bricked after googling around.
I then tried to use OMAPFlash as suggested by other people with the same issue. I did this, followed instructions perfectly, installed certificates. It got to the point where it was attempting to download a file. After 2 hours of waiting, I stopped it stupidly because it was making no progress.
Now my phone is completely black. I have no OS and I am not even sure if I have any files on it. Screen is black, phone not responding to button pushes and it isn't being recognised by my PC. I have tried unplugging it, removing battery and then plugging it in and inserting the battery again and that has failed.
I don't know what else to do. OMAP isn't picking up the phone anymore even though I have followed the instructions perfectly again. The one sign that my phone is still alive is the beeping noise from windows as I insert it meaning something must be happening. This however is soon followed by "Your device is unrecognised".
Can anyone help me on the situation as the phone is in perfect condition (physically) and I can't really afford a new decent phone at the moment.
Here is all the information you may need:
[Before incident]:
ROM: CM11
Rooted: Yes
Bootloader Unlocked: Yes
Ask for anything else.
[Attempted to change to]
ROM: XenonHD
Ask for anything else.
first off, why odin?
its a nexus you can flash back to stock from fastboot. I would suggest you download the factory images for the phone from here:
https://dl.google.com/dl/android/aosp/takju-jwr66y-factory-5104ab1d.tgz
then extract the images into a folder - remove the battery from the phone, put it back in the phone, power up while holding down vol + and vol - to get into fastboot
hopefully you have android sdk installed and fastboot working. use the flash-all script to flash every partition of the phone back to 4.3 stock.
good luck.
Well first thing, did you select the right zip file for your Gnex when flashing XenonHD. Bcz in my case few days ago i stupidly selected the wrong zip file (ROM for Nexus 5) to flash, but luckily i was saved by the CWM via "Status 7 Error".
But your case is more complicated i would suggest you to use Gnex toolkit with Google Factory Images, i hope that it will come for your rescue . Also try this method http://www.androidrootz.com/2012/08/how-to-restore-galaxy-nexus-i9250-to.html maybe it will do some miracle for you. Best of luck.
Progress
So after sleeping on it and spending some time deeply reflecting on the derp that I had made, I successfully managed to use omap to restore my device to the Phone-Exclamation mark sign as posted by another XDA user who ended up sending his phone back. If you search galaxy nexus brick in google images, you will see what I am talking about (can't post image).
I guess the best way to explain it is: [] -- /_\ -- [ ]
Basically it is a phone connected to a yellow exclamation mark sign and then that is connected to a computer.
Is there a way to force my phone into download mode from here. I can't seem to do anything. Some good news is that ODIN is now picking up my device. It is however crashing whenever I attempt to flash the stock ROM (either "odin3 communicator has stopped working" or "odin3 downloader has stopped working").
Any help fixing this?
Hi guys, so my problem is I was installing a new rom on my rooted D855. everything was going along fine but then the process stalled. I left it running for 15 - 20 minutes but it was still on 33%. I tried holding the power button in desperation which shut the thing down. Now when I try to factory reset it goes to the prompt screen, I answer yes, then it asks me to confirm. from there however it goes to LG splash screen and eventually a black screen with Fastboot mode started. -reset- portcharge -reset- portcharge fastboot: processing commands in the top left corner. That's it.. If I try download mode it goes to the download screen and then to the black screen as described above.
Sounds pretty ordinary but if there is an answer out there I am sure one of you guys will know it.
TIA
i had some similar other issue and the only way i got out of it, is by using the lg flashtool 2014 and the KDZ file appropriate to your version
there is a thread with a step by step instructions.
you launch the flashtool, then insert the kdz file (original stock rom) then you put your phone into download mode (making sure in windows/controlpanel/devicemanager/ports - comp port 41 for the device driver)
you press volume up and plug it into the pc, the pc sees the phone and it starts reflashing the custom rom to your cell.
i presume that as soon as your download mode is working by flashing whatever command is corrupt and makes your phone black should be bypassed by then
i hope it helps - look for the thread how to flash the lg
Thanks I'll give it a shot. Not sure device manager is seeing it properly. I'll have a play and see. Thanks again for the reply
O.K here's the thing, my phone is seen in device manager as a Samsung Android Phone. Under the details tab it shows it connected via USB Modem Phone ADB Port. There is no option to change the port to 41. Anybody who can help I would be very grateful......
Hello everyone,
so here's my problem:
Wednesday morning i took my phone out of my pocket and had a blackscreen. I tried to restart it and took out the batterie but i always got stuck in the LG Logo or a bootloop. Since i had TWRP and lineage OS installed, i tried to go into the twrp menu with the factory mode (power button + volume down) but after the "double yes" i always got a blackscreen.
So i went into the internet to fix it myself. I tried the "LG Flash Tool 2014" with the kdz. reset & the other Flash tool with the tot. reset. Both didnt recognize my phone. At this point, the only thing that worked was the download mode BUT not the recovery mode that usually comes after it. It just showed the download mode for some seconds and then a black screen. Later i noticed that my phone showed as a "qualcomm device" in the device manager, and the internet said that this was bad. So i used "Board diag" and "Smart boot diag" to fix it, but at the point where the device should have restarted, and the download mode should have worked WITH the recovery mode, i always ONLY had the 6 second download mode. After messing a bit with "Board Diag" i even got it to show up as LGE AndroidNet USB Serial Port in the device manager, which apparently was even more bad and only way to go back to qualcomm was to shorten the pins which i did. And it worked BUT now i was back with the qualcomm stuff.
So as you can see, i've prety much run i circles since wednesday... Iam now at a point where 3 different thingscan happen when I try to put my LG into download mode (volume up + usb cable):
1. Its recognized as a unknown device which is constantly connecting and diconnecting, so iam assuming my phone is bootlooping with a black screen.
2. The download mode icon shows on my phone and disappears after some seconds but my pc fails to recognize it.
3. Nothing happens and the screen stays black
When i only connect the usb cable, it shows a stuck charging icon for some seconds and then goes black. Connecting without a battery shows the "missing battery icon". I tried with 2 pc's, both having the LG mobile driver 4.2 and the qualcomm driver installed AND beeing in testmode. Both don't recognize the device. I also tried 2 batteries on my phone but it changes nothing.
I have a D855. And i know that my situation is pretty f*cked but maybe someone i able to help me anyway. Thanks alot.