My LG D415 has been acting weird lately. The phone would randomly reboot even in TWRP and when the phone is actually usable, the hardware buttons + touch would not work for a minute or two sometimes. Then out of the blue one day the phone just bricked itself and was detected as Qualcomm HS-USB QDloader 9008 when plugged into a PC. Since theres no known way for D415 users to get out of that I just simply left the phone alone for a few days and it started working again somehow. I reflashed the bootstack and went back to CM13 (was on turbo 7.0) and that seemed to stop the random bricking but the random reboots still occur along with the hardware issues.
The thing that really freaked me out was when I adb shell my phone and got garbled text for the phone name
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What i'm really wondering is if my D415 board is screwed and if it is could I fix this with reflashing the .kdz?
The phone appears not to turn on but when I plug it in it mounts as a usb?
Inside theres modem files and such. Totally clueless on what to do here I need help ASAP!
Edit: I pulled the battery out in panic and plugged in the phone w/o battery and it shows a picture of a battery with a triangle BUT so i put battery back in and this time around it boots into fastboot and only fastboot.
Edit2: Pulled the battery again to try to get the phone to mount as a usb and instead started working normally again... fml
Related
Today I've been trying to update my Trinity's Radio ROM to v1.50 or v1.56 and my phone doesn't seem to be accepting ROM upgrades anymore?!
When I try to flash the ROM, my phone's screen goes into the bootloader (the red, green and blue screen.. correct?) and I hear my PC make the USB device disonnected sound and then it reconnects, making the reconnection sound and it says "USB" in the white part at the bottom of the phone's coloured display.
So I get this screen but it gets stuck on 0%:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then after about 30 seconds this comes up:
My phone stays in bootloader mode until I turn it off then back on again (soft reset).
The phone turns back on and I can use it like normal.. but it is still the old ROM obviously because it didn't update.
I've upgraded the ROM many times before.. so why would ROM upgrading suddenly not work anymore?
Suggestions anyone?
Before you get techy!!
Hi there - I had the same problem this eve - reflashed tonnes of time sno worries then all of a sudden nothing.
Before, like me you scour the forum for the techy solution (reinstall activesync, muck with SPL, copy things to SD card) go dig out some USB cables.
I've found that it was a dodgy cable that works for everything else.
So if you get this error and your white strip in bootloader says serial - go get another USB cable first!!!!
Cheers
I've done some searching, but can't seem to find this particular situation.
Stats: Original droid, running clockwork, cyanogen 6.x, everything worked well this weekend. It's not activated currently, but the phone behaved as it should all weekend, as I prepped it for sale yesterday.
Yesterday, I rebooted the phone. Well, sort of. It rebooted, and my motorola logo is centered in the left third of the screen, rather than in the center third. It will not move past the moto logo when powered on.
I've tried X+power, and assorted other combos, and the only one that will allow me access to anything is holding down+camera when booting, which gives me a bootloader 2c.6c screen, showing that the battery is okay, and that it's okay to program.
I can connect in this mode to RSD lite, and attempt a reflash, but when the phone reboots, it goes back to the crooked motorola logo screen, and stays there.
Initially, before I attempted to reflash with rsd, I could find the device with adb, but it wouldn't reboot or reboot-bootloader, hanging instead on the crooked logo.
Am I missing anything? If it's bricked, it's bricked, it hasn't been my primary phone since I bought my X, but Ideally I'd like to restore it and either keep it as a backup, or sell it and make a buck or two.
Sorry for writing a book, just figured I'd convey as much info as possible.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
my cool new boot page. The bottom right side is just some white nonsense, no legible text or anything.
Really? No thoughts at all? Not even a "dude, you're so screwed".
I'm have very bad problem, after march security update, my phone goes in bootloop(screen freez), but i have luck, oem onlock, and after bootloop i'm unlock bootloader, and crytical particion, but my luck goes to end. I can't flash fastboot rom, after 15x time flashed, 2 time after 20 times of flashed, 2 times was successful, but did not want to lift the system to the end, and it was constantly getting back to the beginning on boolocker unlock screen and on android one logos, once it was upgraded, but wi-fi and sim cards did not work and very slow work(last update). I have tried all possible combinations, and nothing is left, 95% of the cases flush the rom without end time goes 800sec+.... What i can do?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/url]Untitled by Milan Aleksic, on Flickr[/IMG]
After this phone turn off and can't to turn on, its hadrbrick, maybe motherboard, maybe display, maybe battery... Who knows. Phones is dies. Can't charging, on PC only sound off USB nothing else. Good bye xiaomi..
After this phone turn off and can't to turn on, its hadrbrick, maybe motherboard, maybe display, maybe battery... Who knows. Phones is dies. Can't charging, on PC only sound off USB nothing else. Good bye xiaomi..
Okay, i had this problem! I know there is no logic behind the solution I'll offer you(or maybe there is, i just don't know about it). I faced the bootloop issue after updating the security patch of may. i came across a post on the mi forums! Someone said to install the update then before hitting that restart option, you are to eject your sim card! It should work as intended! Then when phone updates, reinsert the sim card! Trust me! It worked for me!!
Hi all,
So, I was running fine with CROMi-X KitKat, but wanted to upgrade to Marshmallow (to install sw not supported in KitKat), so decided to try KatKiss 6.0. It's been years since I've played with flashing ROMs, but I did a little reading to refresh my memory. Then I rebooted into recovery (ClockworkMod), backed everything up, then wiped everything, formatted /data, and tried flashing the KatKiss zip file. At that point, it just sat there forever at the ASUS logo screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried several times to boot back into recovery by holding the Vol+ and Power buttons, but it either doesn't boot, or boots to the above screen. I've connected it to my Mac w/ the Android SDK Platform Tools, but adb doesn't see any device listed. [I've got an old Windows laptop (XP?)] I could use if it will do something the Mac can't.]
Any advice on how I can save this tablet?
Have you found a solution finally?
Well, I haven't found a solution, but after letting it sit unplugged for months, I came across it today as I was straightening up. I plugged it in, waited maybe half an hour, and was able to boot it into recovery mode. I was then able to restore from a backup, and damned if it didn't reboot and come up just fine. No idea why it wouldn't boot into recovery before, but I'm happy camper!
Hello! This is my first time creating a post for a problem I had because I'm really desperate.
Some days ago, my Note 8 showed the wet port notification and gave some problems when charging. Then, the notification dissapeared but the problems remained. For some days, I've not been able to charge the mobile when it had battery. I had to wait until it was completelly empty, not just to turn off, but to not be able to turn on again. That's the only time when it charged. I've tried to reinstall the original ROM (I don't remember wich one I have but I installed some things and rooted the phone when I got it, half a year ago.), but I can't use ODIN as when I connect it to my PC it says that the device was not recognised and is not detected at all.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've now wiped the phone and I think that now is able to charge when off, but I'm not sure as it seems to charge whenever it wants.
Thanks for the help to anyone who responds.
[Update]
I've wiped dalvik cache and it seems to charge while on. But my PC still doesn't recognise it.
[Update]
Fast charging does not work, just as before (when it charged was on slow mode).
[Update]
As root was not installed I thought that maybe I had the stock fimware and disabled OEM Unlock. Now it gives me the "Custom binary blocked by FRP Lock." error both on system and twrp so I'm bricked. Also, Odin still doesn't recognise the phone. I don't know what to do now...