Hi. I have an LG v20 H990ds. I used a non-genuine usb-c cable which messed up its usb-c port. Ever since then, phone started bootlooping. Despite replacing the usb-c cable, phone is on bootloop. I think the firmware flashing can resolve the issue.
But the phone doesnt stay in download mode for more than 3-4 seconds as it keeps bootlooping. When it is in download mode, my computer doesn't detect it or get a trigger that the phone is connected in device manager.
But when I enter into fastboot, I can install fastboot drivers just fine and able to use fastboot commands. I would have flashed boot.img and system.img using fastboot but it shows the device is 'locked'. Since I cant use 'fastboot oem unlock' as the developer options of the phone software was not enabled, I have come here for seeking help.
Can I bypass the developer options and unlock in fastboot? Can I use EDL mode? Or Qualcomm tools? What are my options? I am really not sure why its bootlooping despite getting usb c port fixed. I will really appreciate if someone can help please. The only way the device can work is if it bypasses the 'lock' checks in fastboot. So a patch or something that can bypass the fastboot can help. Or if I can unlock bootloader n fastboot without using android OS.
Related
Went through the Guide, however i've run into roadblocks.
i've installed all sdk packages, adb commands work, and fastboot commands return serial numbers. however once i run fastboot flashing unlock, there is a thread run in command promp window, with no change in the device's bootloader screen.
i've done the 6.0.1 update, the bootloader screen reads (some important ?) console NULL; device is LOCKED; download mode DISABLED; CONNECT USB DATA CABLE (while plugged in)
usb debugging is enabled, and the OEM unlock option is checked.
Any advice is appreciated.
Is it necessary to use this method? Won't something like Nexus Root Toolkit work too? Just a thought, I may be way off
gman88667733 said:
Is it necessary to use this method? Won't something like Nexus Root Toolkit work too? Just a thought, I may be way off
Click to expand...
Click to collapse
Haven't seen this mentioned before, but im new to this forum. Will defiantly try later if nothing else works
well it worked with unlocking, when rooting flashing twrp, i sucesfully flashed .zips in twrp, then stuck in bootloop. downlownloading the recovery to fix bootloop, any suggestions on how to succesfully root without BL using nexus root toolkit?
AlPoo said:
Went through the Guide, however i've run into roadblocks.
i've installed all sdk packages, adb commands work, and fastboot commands return serial numbers. however once i run fastboot flashing unlock, there is a thread run in command promp window, with no change in the device's bootloader screen.
i've done the 6.0.1 update, the bootloader screen reads (some important ?) console NULL; device is LOCKED; download mode DISABLED; CONNECT USB DATA CABLE (while plugged in)
usb debugging is enabled, and the OEM unlock option is checked.
Any advice is appreciated.
Click to expand...
Click to collapse
When you issue the "fastboot flashing unlock" command does it return a huge list of compatible commands? If so, your adb/fastboot is out of date.
Have you enabled bootloader unlocking in developer options?
Hi.
Few days ago I locked my bootloader while I was having a TWRP.
In result I coudn't EDL thru test point - HS-USB Diagnostic 900E, had full brick with only fastboot. Even LED was not blinking.
Today I found a solution, maybe someone will find it somehow helpful.
1. Unplug your battery from motherboard, connect USB to the phone and computer and get into the fastboot.
2. Open Miflash, it should be in fastboot mode. Flash fastboot rom, I don't know what it does but it may help.
3. Unlock your bootloader with MiUnlock, if you having any errors play with versions.
4. EDL should work fine now, I used a Annabathina's fastboot to EDL.
5. Just flash new software and enjoy your unbricked phone
i decided to flash stock nougat from stock oreo (currently usb debugging is on). While flashing nougat in fastboot my phone showed erase screen and rebooted back to stock 8.1(this happens after may update when the bootloader is unlocked and this time i'm sure that usb debugging option has been reseted and turned off by itself because of boot loader unlock). And then i forgot to turn usb debugging on and booted into fastboot mode and flashed stock nougat and bricked my phone. Please help, is there anyway to turn usb debugging on a bricked device?
Edit: i can access fastboot mode and bootloader is unlocked.
Thank You
Ykhenix said:
i decided to flash stock nougat from stock oreo (currently usb debugging is on). While flashing nougat in fastboot my phone showed erase screen and rebooted back to stock 8.1(this happens after may update when the bootloader is unlocked and this time i'm sure that usb debugging option has been reseted and turned off by itself because of boot loader unlock). And then i forgot to turn usb debugging on and booted into fastboot mode and flashed stock nougat and bricked my phone. Please help, is there anyway to turn usb debugging on a bricked device?
Edit: i can access fastboot mode and bootloader is unlocked and my adb recognize my device.
Thank You
Click to expand...
Click to collapse
Put your phone in fastboot mode (power and vol-) and flash stock Rom with Miflash (clean all).
sipollo said:
Put your phone in fastboot mode (power and vol-) and flash stock Rom with Miflash (clean all).
Click to expand...
Click to collapse
is it possible when usb debugging is turned off?
and when my devices even not detect in adb
EDIT: My device detects in miflash and got error when i flash (error:FAILED(data transfer failure (too may link))
Ykhenix said:
is it possible when usb debugging is turned off?
and when my devices even not detect in adb
EDIT: My device detects in miflash and got error when i flash (error:FAILED(data transfer failure (too may link))
Click to expand...
Click to collapse
Change USB port, change cable or try in another PC.
LG V20 910
On boot, it shows the LG logo, but does not start.
When I hold Vol up and plug in usb, the same thing happens
When I hold Vol down and plug in usb it does boot to fastboot
Factory reset gives a kernel crash error
adb does not recognize the device
fastboot via command prompt in windows does recognize it
LGUP does not recognize it
Is there a way for me to flash back to H91510e_00_VTR_CA_OP_1205.kdz with Fastboot, or is there another method to get download mode again?
How did you brick your phone? If you just turned it on one day and this happened, it is more than likely a hardware problem.
Since you say that you can get to fastboot -- I am guessing you were rooted since the H910 doesn't have fastboot without the engineering bootloader.
If so, then fastboot boot twrp.img
If TWRP will boot, you can fix your phone from that.
-- Brian
Hey guys, I know this isn't super active anymore, but I tried looking and tried posting elsewhere, and I can't find the answer I need. I'm sure it's something super simple I've overlooked.
I was gifted a 2015 Nvidia Shield TV Pro that was never used, so when I turn it on it gets stuck forever asking for my google login and won't proceed (like this thread here).
I can access the fastboot menu on the unit, and I've installed the PC drivers - BUT
When I open command and type "adb devices" it shows no devices connected.
I'm TOLD this is because I need to activate USB debugging on the unit, but how can I toggle on the USB debugging if I can't get past the google sign-in for a first-time set up?
Am I approaching this wrong?
PLEASE help!
Hello, I have exactly the same issue.
I would be really grateful if someone could help us.
i think you must set your SHIELD in FASTBOOT mode and after flash the stock firmware from https://developer.nvidia.com/gameworksdownload (you can't set FASTBOOT mode from ADB because of the wrong login)
to set fastboot mode look here : https://nvidia.custhelp.com/app/ans...invoke-the-android-fastboot-menu-on-shield-tv
Thanks conduisant! It helped.
I have spent some time to flash new recovery:
How far I was able to proceed:
I downloaded ADB Fastboot drivers
I downloaded recovery image (nv-recovery-image-shield-2017-atv-8.2.3)
I connected Nvidia Shield 2017 (model: P2897) with USB-A-to-USB-A cable to the PC
I was able to see "unknown device" so I installed ADB drivers (SHIELD_Family_WHQL_USB_driver_201801)
In device manager I can see my shield (as a Android Bootloader Interface)
I can access fastboot (pressing A+B on controller during turn on of shield)
I opened CMD and type "fastboot devices" - press enter - I can see my device is listed "03xxxxxxx fastboot"
I am able to execute "fastboot oem unlock", so bootloader is unlocked
I am able to write recovery image by using following commands written in instructions:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot oem lock
fastboot reboot
(no errors, everything was "OKAY")
But after the device restart , I can post only until the nvidia logo and that is it. Unfortunately I do not even know which was the original (stock) version of system in nvidia shield pre-installed. I tried to flash several versions of recovery images, but nothing helped. I can still see only nvidia logo :-(
But what I noticed, my Fastboot looks pretty different. I do not see my bootloader version, also some options are missing (lock bootloader, unlock bootloader etc.)
I also tried another options - boot recovery kernel, safe mode, but only nvidia logo every time.What is strange, when I turn-on the device, the Fastboot is automatically booted (I do not even hold A+B to initiate fastboot) I need to select continue.
So now I am not even able to try login into the shield anymore. I guess I already bricked the device :-(
what you have done is pretty correct !
Shield seems to be hard bricked, you can also try to flash TWRP + lineage OS ROM only to see if the SHIELD still not boot...i've no other idea
Thank conduisant for your effort!
Unfortunately, I am not able to boot into the TWRP.
I tried to flash TWRP what I have found here on forum:
UNOFFICIAL-twrp-3.0.2-ALL-Shields-build2.zip
But no success.
I tried to also flash official TWRP:
twrp-3.2.3-0-foster.img
But also no success.
I do not know which offical recovery to flash before LineageOS ROM (or it does not matter?)
Unfortunately, for some reason my gamepad in Fastboot stopped working (gamepad is connectied via USB to the shield, closest to HDMI port)
It just rumble when Fastboot booted and blinks blue led. I tried to charge gamepad - or - another nvidia shield gamepad but it does not work.
Also USB keyboard does not work. Looks like the USB port does not work properly anymore, so I am not able to click "Continue" in fastboot anymore to post at least until nvidia logo.
Luckily, the bootloader is still unlocked, so I am able to flash anything but I have already lost my mind.
I need another coffee and one full-day of meditaion.
i've got 2017 SHIELD, and i've flashed this TWRP last days + this LINEAGE OS : and all working good
TWRP = https://eu.dl.twrp.me/foster/twrp-3.7.0_9-0-foster.img.html
LINEAGE OS = https://download.lineageos.org/foster
when USB debugging is ON, only one USB port is activate for USB devices (keyboard for example) : it's the port near HDMI, the other port (near fan grid) is for ADB connection for the PC