Due to dirty flashing and flashing a rom with the wrong kernel, my phone goes into a logo boot loop. I had cleared my internal storage after flashing since i thot flashing had succeeded. Now, I can only access twrp. I formatted the internal storage, i cant access adb. My pc doesnt recognize the phone at all. My kernal is NoKernal, i cleared everything including system, and twrp doesn't recognize my usb either. Please help me! Thanks a lot in advance!
-Danny
Try to check whether fastboot is working, check with a different usb cable. Once you can access adb, you can sideload any rom you want.
No, fastboot isn't working either. I switched the phone onto fastboot mode, but nothing showed up when i used 'fastboot devices'.
Related
I flashed the wrong kernal and I'm stuck on a bootloop. I can't access my internal storage via TWRP or cant use ADB either. ADB isn't recognizing the device. Is there anyway I can come out of this without losing my data on the phone? I can see the g2 listed as Other Devices in my PC's Device Manager while plugged in. I suppose that has something to do with it. Is there some driver I need to use ADB in recovery?
sacredsoul said:
I flashed the wrong kernal and I'm stuck on a bootloop. I can't access my internal storage via TWRP or cant use ADB either. ADB isn't recognizing the device. Is there anyway I can come out of this without losing my data on the phone? I can see the g2 listed as Other Devices in my PC's Device Manager while plugged in. I suppose that has something to do with it. Is there some driver I need to use ADB in recovery?
Click to expand...
Click to collapse
not sure if you found out already but
all you have t do is go to mount and mount what uou need
sacredsoul said:
I flashed the wrong kernal and I'm stuck on a bootloop. I can't access my internal storage via TWRP or cant use ADB either. ADB isn't recognizing the device. Is there anyway I can come out of this without losing my data on the phone? I can see the g2 listed as Other Devices in my PC's Device Manager while plugged in. I suppose that has something to do with it. Is there some driver I need to use ADB in recovery?
Click to expand...
Click to collapse
http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
device manager, right click phone, update drivers, browse computer, let me pick from a list, unclick show compatible hardware, and find LGE or LG and pick the adb driver
Yes, I solved it. Got the drivers fixed.
Fun fact : If your G2 is just getting stuck at boot, turn it off for an over and try again. I stupidly flashed a zip containing a recovery using Flashify and not the boot.img and I got stuck in Fastboot mode or it'd just stuck at the boot animation. I had given up and decided to go back to stock, wiping all my photos. But thankfully the stock flash got stuck because I am using a custom kernal. I turned it off, watched some tv and tried again. Booted right back into the rom. Flashed a proper recovery using adb, got into TWRP, reflashed my rom and didn't lose any data. @autoprime got me through the process via IRC so big kudos to him!
Ok, I'm going to start by explaining everything I did up to this point to eliminate any troubleshooting sugggestions i may have already done.
I rooted and installed recovery the same way everyone else did. After a couple of days, I tried to install a ROM but im assuming i was encrypted because i was stuck in a loop that would only boot me into TWRP. Did my research and took the necessary steps to get around that and decrypt and boot into the new ROM.. FINALLY!!! Only one problem, this rom doesn't have Super SU installed, Alright... so i download the proper Super SU build and put it on my Micro SD card and try to boot into TWRP to flash....
This is where the problem begins. I never get the prompt to authorize my PC from my phone to allow anything, and i never did each time i reset. I'm almost certain the adb on this rom is messed up, i've wiped about 4-5 times to re-enable usb debugging from scratch in order to adb or fastboot into recovery via command prompt, however when i try adb, i get that unauthorized error an there's no option on the LG V20 to revoke under developer settings. Fastboot i just get the same "waiting for device" message. Also keep in mind that i set it to photo mode, every mode that was available and nothing. Tried different USB Cords and did this on both my laptop and my PC at work
I've tried uninstalling and reinstalling all of the drivers, re-installed the latest version of adb and fastboot to my PC, that didn't work either. Tried deleting the adbkeys file in the .android folder and still nothing.
When i try to boot in recovery manually, i just get the wipe data option and when i click yes to everything, it actually wipes my data. I'm unable to reflash TWRP because I can't access ADB or Fastboot due to the unauthorized error.
Someone, PLEASE HELP!!!!
any luck?
ahq1216 said:
Ok, I'm going to start by explaining everything I did up to this point to eliminate any troubleshooting sugggestions i may have already done.
I rooted and installed recovery the same way everyone else did. After a couple of days, I tried to install a ROM but im assuming i was encrypted because i was stuck in a loop that would only boot me into TWRP. Did my research and took the necessary steps to get around that and decrypt and boot into the new ROM.. FINALLY!!! Only one problem, this rom doesn't have Super SU installed, Alright... so i download the proper Super SU build and put it on my Micro SD card and try to boot into TWRP to flash....
This is where the problem begins. I never get the prompt to authorize my PC from my phone to allow anything, and i never did each time i reset. I'm almost certain the adb on this rom is messed up, i've wiped about 4-5 times to re-enable usb debugging from scratch in order to adb or fastboot into recovery via command prompt, however when i try adb, i get that unauthorized error an there's no option on the LG V20 to revoke under developer settings. Fastboot i just get the same "waiting for device" message. Also keep in mind that i set it to photo mode, every mode that was available and nothing. Tried different USB Cords and did this on both my laptop and my PC at work
I've tried uninstalling and reinstalling all of the drivers, re-installed the latest version of adb and fastboot to my PC, that didn't work either. Tried deleting the adbkeys file in the .android folder and still nothing.
When i try to boot in recovery manually, i just get the wipe data option and when i click yes to everything, it actually wipes my data. I'm unable to reflash TWRP because I can't access ADB or Fastboot due to the unauthorized error.
Someone, PLEASE HELP!!!!
Click to expand...
Click to collapse
different route but im in the same boat. any luck?
I fixed this shortly after. Wanted to avoid returning to stock as. The only option was you and I was on 10d. I had to go back to stock but luckily the recovery method still works.
Hi,
My devices is stuck on Mi logo, it was not Bootloop, it cant reboot to EDL, sometimes my devices can go to Fasboot mode but sometimes cant, while in fastboot mode I check in the Device drivers section theres no Qualcomm blablabla but the only available is Android Bootloader Interface and when I try to flash my phone via Mi Flash Tool I cant because my devices is not detected, What should I do? :crying:
1. My device is already unlocked
2. Before this I was flashing RR, and it was just fine, then I try to boot to my TWRp but it seems I cant, then I install TWRP and it just works fine, then I want to flash new rom, then I qipe dalvik cache, cache, system, and data then it shows error "partitions blablabla" then I try to factory reset in TWRP, its done its job, then I try to flash the new rom but when I pick "sdcard" (internal storage) it was blank! then I check "sdcard1" (external memory) it was blank too! then I just reboot (it says no OS installed, I just swipe then it stuck on MI Logo).
3. I have tried some tricks to recover it but It cant! (I still didn't tries deep flash cable or either test point method because I don't know how to do that)
4. My devices Is Detected when I typed "fastboot devices" in cmd but not detected in MiFlash Tool.
Please how do I fix this problem?? please help me as soon as possible!!
Thanks.
Help me!
Please someone answers me! :crying:
Since your device is showing in fastboot, flash TWRP again from fastboot. Copy ROM and GApps to external SD card and boot into TWRP. Wipe dalvik, cache, data, system, and internal storage. Flash new ROM, GApps reboot.
If you get any errors while wiping partitions then format the partitions to f2fs or anything then again back to ext4.
Hope this helps!!!
Cheers ?
Chris828 said:
Hi,
My devices is stuck on Mi logo, it was not Bootloop, it cant reboot to EDL, sometimes my devices can go to Fasboot mode but sometimes cant, while in fastboot mode I check in the Device drivers section theres no Qualcomm blablabla but the only available is Android Bootloader Interface and when I try to flash my phone via Mi Flash Tool I cant because my devices is not detected, What should I do? :crying:
1. My device is already unlocked
2. Before this I was flashing RR, and it was just fine, then I try to boot to my TWRp but it seems I cant, then I install TWRP and it just works fine, then I want to flash new rom, then I qipe dalvik cache, cache, system, and data then it shows error "partitions blablabla" then I try to factory reset in TWRP, its done its job, then I try to flash the new rom but when I pick "sdcard" (internal storage) it was blank! then I check "sdcard1" (external memory) it was blank too! then I just reboot (it says no OS installed, I just swipe then it stuck on MI Logo).
3. I have tried some tricks to recover it but It cant! (I still didn't tries deep flash cable or either test point method because I don't know how to do that)
4. My devices Is Detected when I typed "fastboot devices" in cmd but not detected in MiFlash Tool.
Please how do I fix this problem?? please help me as soon as possible!!
Thanks.
Click to expand...
Click to collapse
Yeah. This is not a hard brick. You can also reflash miui from fastboot. Extract that tgz file of miui and click on one of the batch files.
So I seem to have wiped/formatted completely through TWRP and it wiped out the original stock rom, so I have absolutely no OS...
I can still get to bootloader and TWRP Recovery, but USB OTG won't mount no matter how many times I try to connect it (which I need to install the downloaded ROM)
I was hoping I could copy the rom via ADB command but it won't recognize the device with 'adb devices'. It does however recognize when I do "fastboot devices"
What should I do? I think since it wiped out the OS, my device no longer is able to run in USB Debugging mode... how could I load the ROM onto my device?
IF you download the WUG toolkit, you can flash the ROM .img files in Fastboot mode (Boot/System/Recovery/Cache etc).
So I screwed up. When wiping my system for lineageos, I accidentally wiped everything, including the system, internal storage, and data. I am in TWRP right now. Trying to send files over at MTP just makes the progress bar not move. I cannot move it over with my phone mounted as a usb storage device. When using adb push to send over a ROM, the command completes, but it does not appear in the sdcard folder as I specified. Adb sideload just stops at 50%, with the phone displaying step 2/2 and not continuing after that- I have the option to reboot or wipe dalvik / cache. I have no OS. I know that rebooting into TWRP again will make MTP work, however as I have no OS installed I know that I will not be able to access fastboot. Any ideas on how to get a rom onto my phone's storage?
You might need to format your internal storage as it may still be encrypted which may be why files aren't copying across. This is just a guess though. If all else fails (I have been in a similar situation before), you should be able to boot into fastboot (bootloader) mode from TWRP and flash OOS back through that. You would need to find the fastboot version of the ROM. I believe there is a thread in this forum somewhere. A last resort would be using the MSMTool to get back to stock. I've never had to do this myself though. The phone will be in a like brand new state though, so you would need to unlock the bootloader again if you are going to flash a custom ROM or do any modding after.
You can use OTG storage, encryption has no effect on it and you can flash files too. I used it to bypass the encryption issue in TWRP. If that doesn't work then post #2 is your best option. Also you can still boot in fastboot even if your ROM is broken. You can find the fastboot ROMs in the guide section.