i booted into recovery, made a full backup, wiped everything but internal storage, flashed to lollipop 5.1 but decided to go back to my backup. so rebooted into recovery again and restored the backup. everything seemed to work correctly but after rebooting phoned stuck at lg logo. so i rebooted into recovery by holding "volume - and power" and the factory data reset screen came up and i confirmed that i wanted to reset phone, expecting it to boot into twrp but it went to the the black screen with the android on his side (or something like that), which i assume it did do a factory reset.
so still stuck at lg logo with no custom recovery anymore apparently. among other things, i used srktool to nuke download mode, so phone immediatly goes into fastboot mode. now im trying to use the "fix fastboot mode" but it just sits there saying waiting for device even though i have phone connected to computer in fastboot mode.
is it likely that if/when it did the factory reset, that would disable the usb debugging setting and that's why srktool just shows "waiting for device"?
im betting that your OS got corrupted. You can try to reflash your ROM, or you might be relegated to going into download mode and reflashing the OS back to stock. I have a link for the LG recovery tool and the stock 4.4.2. All youll need from there is towel root and the recovery i have in a separate post
hi i have same problem con you explein how can i do this
hi i have same problem con you explein how can i do this
l.musaj said:
hi i have same problem con you explein how can i do this
Click to expand...
Click to collapse
try this
http://forum.xda-developers.com/att-g2/development/twrp-5-0-d800-g2s-t3247754
youdoofus said:
try this
http://forum.xda-developers.com/att-g2/development/twrp-5-0-d800-g2s-t3247754
Click to expand...
Click to collapse
thank you but my lg d800 dosnt entry in download mode it stuck
{
"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"
}
he stuck here in ports dosnt show nothink but in USB controllers its unknown device
l.musaj said:
thank you but my lg d800 dosnt entry in download mode it stuck
he stuck here in ports dosnt show nothink but in USB controllers its unknown device
Click to expand...
Click to collapse
uninstall the usb driver and let windows find the correct driver for it and follow the stuff in the link i provided after the computer recognizes the device. If that doesnt work do the stuff in the link on another computer or try a different cable. If you can get to download mode, youre likely ok. The issue is either the computer or the cable, not the phone.
Related
Hello,
I am using a SM-G350
Yesterday tried to make a running recovery mode on my phone but failed - when i try to turn on phone in recovery mode (volup+home+power) there is a red exclamation mark in the top right corner. Used Odin v1.85 and it saw my phone and everything seem to went OK there was a PASS message.
It didn't work so I kept reading Installed USB drivers, KIES and then my phone stopped appearing in Odin when I tried to do it again with the drivers instaled and an other ODIN version it just doesnt seem to see my phone anymore, same goes for KIES does not connect to my phone...
Ofc tried ODIN in download mode and opened as admin.
and for KIES tried with the multimedia on etc.
When plugging the phone to the computer there is this install window that show that:
{
"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"
}
CDC Serial
CSC Serial
SM-G350
Cant find drivers.
I tried reinstalling several times dunno what to do now.
Please help!
BarthoSM-G350 said:
Hello,
I am using a SM-G350
Yesterday tried to make a running recovery mode on my phone but failed - when i try to turn on phone in recovery mode (volup+home+power) there is a red exclamation mark in the top right corner. Used Odin v1.85 and it saw my phone and everything seem to went OK there was a PASS message.
It didn't work so I kept reading Installed USB drivers, KIES and then my phone stopped appearing in Odin when I tried to do it again with the drivers instaled and an other ODIN version it just doesnt seem to see my phone anymore, same goes for KIES does not connect to my phone...
Ofc tried ODIN in download mode and opened as admin.
and for KIES tried with the multimedia on etc.
When plugging the phone to the computer there is this install window that show that:
View attachment 2845124
CDC Serial
CSC Serial
SM-G350
Cant find drivers.
I tried reinstalling several times dunno what to do now.
Please help!
Click to expand...
Click to collapse
UPDATE:
Well i thought restoring firmware from phone will help in some way, and now its not turning on because of the red exclamation mark.
WHAT I WANT TO DO IS:
Be able to delete the firware that was on the phone from the provider
Install a custom ROM
If You could provide me with some links or help on how to do it now i would really appreciate it.
T-mobile Prism II (U8686)
Android 4.1.1 (rooted)
Custom Recovery CWM 6
I just setup swap with swappy2 following this guide.
I just rebooted and now my phone shows the T-Mobile logo and then directly to BLUE SCREEN
Turning on with no buttons pressed / pwr & v+ / pwr v-
{
"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"
}
Turning on with both v+/v- pressed
adb/fastboot wont recognize device
any ideas on what is wrong i hope its not bricked?
Diehardshorty said:
T-mobile Prism II (U8686)
Android 4.1.1 (rooted)
Custom Recovery CWM 6
I just setup swap with swappy2 following this guide.
I just rebooted and now my phone shows the T-Mobile logo and then directly to BLUE SCREEN
adb/fastboot wont recognize device
any ideas on what is wrong i hope its not bricked?
Click to expand...
Click to collapse
Try to again flash, and make sure scatter file is correct according to your device.
I have no access to recovery menu, just getting this blue screen each time it powers up.
Diehardshorty said:
T-mobile Prism II (U8686)
Android 4.1.1 (rooted)
Custom Recovery CWM 6
I just setup swap with swappy2 following this guide.
I just rebooted and now my phone shows the T-Mobile logo and then directly to BLUE SCREEN
adb/fastboot wont recognize device
any ideas on what is wrong i hope its not bricked?
Click to expand...
Click to collapse
To use ADB you also need the device Drivers installed.
christoph.gasser said:
To use ADB you also need the device Drivers installed.
Click to expand...
Click to collapse
Did you even read the thread? Go spam else where
Diehardshorty said:
I know how adb and fastboot work the drivers are installed.
Did you even read the thread?
Click to expand...
Click to collapse
Yes I read your thread.
But you don't only need the ADB drivers you also need the device specified drivers.
For example for my HTC One:
I need: the HTC One drivers
the ADB drivers
I had the same problem some time ago.
christoph.gasser said:
Yes I read your thread.
But you don't only need the ADB drivers you also need the device specified drivers.
For example for my HTC One:
I need: the HTC One drivers
the ADB drivers
I had the same problem some time ago.
Click to expand...
Click to collapse
Well the phone came with an autorun cd that mounted with it when you connected it to the computer. It had adb drivers and the device drivers, i installed them both and used the fastboot and adb to flash CWM recovery before this happened to get it rooted. Was working great before i tried to get swap working with the guide i followed above.
Im thinking its bricked possibly bcause this thread. My devices is doing the same thing he is describing.
Just a few images to show you what is happening
Turning on with no buttons pressed / pwr & v+ / pwr v-
Turning on with both v+/v- pressed
bump
I have the same problem and have not found a solution
Hey, my friend has a Pixel 2 that seems to have gotten bricked today. His phone was working fine all day but when he tried to unlock it to check the time, it was suddenly in fastboot mode. He was running stock android, and has never flashed any custom ROM/software to it, nor unlocked it:
{
"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 can't open recovery mode or boot the OS from fastboot. The only option I can access is the "barcode" one. I've been trying to flash a factory image from google(as I've done several time for my Nexus 5 and Nexus 7 using the fastboot/ADB from CMD), but currently ADB won't recognize the device(probably because USB debugging and other developer settings are off/have never been accessed at all), and Fastboot recognizes the device but can't perform any flashing to it because it's locked. I also tried deuces script from a folder with all the factory .img files unzipped etc. I also updated the USB drivers in windows, but basically every step I can find here, on reddit or on stack overflow mention enabling USB-debugging and OEM unlock in the settings, which I can't access. Is there anything I can try or is it per definition bricked?
Marhan93 said:
Hey, my friend has a Pixel 2 that seems to have gotten bricked today. His phone was working fine all day but when he tried to unlock it to check the time, it was suddenly in fastboot mode. He was running stock android, and has never flashed any custom ROM/software to it, nor unlocked it:
I can't open recovery mode or boot the OS from fastboot. The only option I can access is the "barcode" one. I've been trying to flash a factory image from google(as I've done several time for my Nexus 5 and Nexus 7 using the fastboot/ADB from CMD), but currently ADB won't recognize the device(probably because USB debugging and other developer settings are off/have never been accessed at all), and Fastboot recognizes the device but can't perform any flashing to it because it's locked. I also tried deuces script from a folder with all the factory .img files unzipped etc. I also updated the USB drivers in windows, but basically every step I can find here, on reddit or on stack overflow mention enabling USB-debugging and OEM unlock in the settings, which I can't access. Is there anything I can try or is it per definition bricked?
Click to expand...
Click to collapse
Have you tried using the OTA instead of the factory image? That might give you a workaround to get it functioning again.
Sent from my Pixel 2 using Tapatalk
Have you tried changing your usb cable and the port its plugged into? Its stupidly simple, but has solved nuuuuuumerous problems I've had with manually flashing.
Other that that, I think you've covered a lot of bases. Are you sure you can't get into recovery mode tho? I was only able to get in by unplugging, full power off, then using power + vol dn for bootloader mode, then selecting recovery mode. You might be able to do some flashes from there.
Also, adb only works in the OS and maybe recovery mode. Fastboot only works in bootloader mode. I'm not exactly sure if fastboot needs to be authorized. Adb does though.
I have a t mobile variant that is sim unlocked and bootloader unlocked.
I wanted to convert to a Global version however it failed because I apparently had the wrong oem software.
I used all in one tool which worked great for everything else I needed but here is the problem; I can only boot into fastboot mode and crashdump mode. When using all in one tool I chose to wipe the device before installing the new software
I also cannot get into EDL Mode to use the Msmdownload tool even though the correct drivers are installed to use this tool.
Anyway out of this? Thanks...
Aslo; I have tried fastboot commands with no luck...
You need to msm using edl. If you are bl unlocked, flash a custom ROM to get booted and maybe try again using proper tool?
Also, try different USB ports, cables, etc. You should be able to boot into edl with hw keys and connect to msmtool
As I stated I can not get into edl, I tried all the the other things also, cables, ports. I did not know I could have flashed a custom rom at this point, phone was not rooted either...
Oneplus has it now for repair, they are about 300 miles from me, or the service center is?
Gabriel51 said:
As I stated I can not get into edl, I tried all the the other things also, cables, ports. I did not know I could have flashed a custom rom at this point, phone was not rooted either...
Oneplus has it now for repair, they are about 300 miles from me, or the service center is?
Click to expand...
Click to collapse
Not sure if you got this fixed but boot into fastboot, the use "fastboot boot" to boot into AICP Recovery. Within recovery eanble ADB, then "adb reboot edl". EDL mode is just a black screen and your phone will exit it and try to boot after a few seconds if the drivers are not installed so its easy to miss. If your phone can boot into fastboot it can boot into EDL.
I do not see that feature listed? Phone would not boot into normal recovery, it went right back into fastboot.
{
"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"
}
Also if you had read through the posts you would know that I already sent it to 1+ for repair, they have had it a couple of days...
OnePlus repaired my device for nothing which is nice however It's now sim locked and at first try T-mobile says this device does not qualify for unlock!!! T-mobile also said they are looking into it because it was previously unlocked and it may take a week to get a reply.
I called OnePlus and their response was it's not our problem (more or less) I sent them a unlocked phone and they completely ignored my request to load the global software on this device, they did what they wanted to, they could have contacted me at any time..THANK YOU OnePlus.
I HAVE BRICKED MY PHONE BY INSTALLING TWRP AND FLASHING CUSTOM ROM ON TWRP MY LEX507 IS DEAD .
I TRIED TO FLASH MY MOBILE BUT I AM RECIVING MORE ERROR ON FLASH TOOL
ANOTHER THINK IS IN MY COMPUTER WHEM I CONNECT MY LECO DEVICE IT CONTINOUSLY DETECTING AND UNDETECTING TWO DEVICES
{
"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"
}
SOMETIMES IT DETECTS MTK USB
SOMETIMES IT DETECTS PRELOADER USB VCOM PORT
THEN OTHER ERRORS FROM FLASHING TOOL I RECIVE ARE AS FOLLOWS
*
ERROR CODE 5000
*
ERROR CODE 6029
*
ERROR CODE 2005
*
ERROR CODE 2004
PLEASE ANY ONE HELP ME PLZ HELP AS SOON AS POSSIBLE
Can you enter the recovery? If you cannot, the phone is hard bricked. You can't do anything about it.
I CAN'T ENTER RECOVERY IN MY PHONE. IT IS NOT AT ALL BOOTING .
WHEN I CONNECT TO CHARGER RED LED GLOWS.
IS THERE ANY OTHER OPTIONS TO RECOVERY IT.
I AM CRYING.
Have you tried from a device running a supported OS? (not Windows 11)
Not certain if it has anything to do, but AFAIK Windows 11 is only in beta.
I HAVE TRIED FROM WINDOWS 10 ONLY.
PLEASE ANYONE HELP ME I WANT MY PHONE BACK
jason141207 said:
I CAN'T ENTER RECOVERY IN MY PHONE. IT IS NOT AT ALL BOOTING .
WHEN I CONNECT TO CHARGER RED LED GLOWS.
IS THERE ANY OTHER OPTIONS TO RECOVERY IT.
I AM CRYING.
Click to expand...
Click to collapse
Can you enter fastboot or Download mode? Chances are pretty low you can actually do something to be honest...
Those kinds of things happen. It's happened to me tone of times.
dedq said:
Can you enter fastboot or Download mode? Chances are pretty low you can actually do something to be honest...
Those kinds of things happen. It's happened to me tone of times.
Click to expand...
Click to collapse
NO MY PHONE NOT AT ALL BOOTING, WHEN I CONNECT TO CHARGER RED LIGHT GLOWS
jason141207 said:
NO MY PHONE NOT AT ALL BOOTING, WHEN I CONNECT TO CHARGER RED LIGHT GLOWS
Click to expand...
Click to collapse
That is hard brick and go take it somewhere to some third-party technician who will be able to fix it.
dedq said:
That is hard brick and go take it somewhere to some third-party technician who will be able to fix it.
Click to expand...
Click to collapse
THEN MY PHONE DEAD THAT'S ALL,