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!
Related
Today, I wanted to reinstall the ROM on my Google nexus 4, and my phone was previously rooted months ago (with Google_Nexus_4_ToolKit_v2.0.0) and was installed with AOKP custom ROM. So I booted into the recovery mode, and accidentally I formatted the system, the cache, the data, etc. I thought when I connect the phone (in recovery mode) to my PC, the PC should recognize my phone and display it as a USB drive in my computer.
However, I was so wrong. With the right driver, the phone is recognized by my PC (as shown in device manager), but it won't show up as a USB drive. So I cannot put in any ROM/gapps file into the phone, I tried to use adb push to load the ROM/gapps into the phone, but I keep getting the "Read-only file system" error. I found the /storage/sdcard0/ can receive the pushed files, but in recovery mode, I cannot select these files for install.
I am now stuck in the recovery mode and cannot do anything. I need you guys help. How can I install a ROM now? thanks a million!!!!
Adb can only be used when your device is booted on android. If not then go to the boot loader and use fastboot.
Sent from my Nexus 4 using Tapatalk 2
rcholic said:
Today, I wanted to reinstall the ROM on my Google nexus 4, and my phone was previously rooted months ago (with Google_Nexus_4_ToolKit_v2.0.0) and was installed with AOKP custom ROM. So I booted into the recovery mode, and accidentally I formatted the system, the cache, the data, etc. I thought when I connect the phone (in recovery mode) to my PC, the PC should recognize my phone and display it as a USB drive in my computer.
However, I was so wrong. With the right driver, the phone is recognized by my PC (as shown in device manager), but it won't show up as a USB drive. So I cannot put in any ROM/gapps file into the phone, I tried to use adb push to load the ROM/gapps into the phone, but I keep getting the "Read-only file system" error. I found the /storage/sdcard0/ can receive the pushed files, but in recovery mode, I cannot select these files for install.
I am now stuck in the recovery mode and cannot do anything. I need you guys help. How can I install a ROM now? thanks a million!!!!
Click to expand...
Click to collapse
Of course you are able to use ADB in recovery mode. Have you tried
Code:
adb push nameoftherom.zip /sdcard/
or if you are using a recovery where you are able to use adb sideload
Code:
adb sideload nameoftherom.zip
Then it should work. Or try mounting the usb in mounts/storage -> mount usb storage
scream4cheese said:
Adb can only be used when your device is booted on android. If not then go to the boot loader and use fastboot.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Of course, it should work if the drivers are installed properly
Like others said use adb push to put a file on the device and then you can flash it with recovery.
If you don't have adb you can get it either by downloading android SDK or just downloading adb did
Sent from my Nexus 4 using xda app-developers app
Try flashing back to stock, then just root and put your ROM back on, I've had to do it once before
Sent from my Nexus 4
Hi Everyone,
I've had some serious issues with the G2 since the night I got it. Basically I soft bricked it when I tried to load Cyanogen because it was a version for the 802 and I have the VS980. Now I've finally managed to get back into TWRP recovery, but I do not have a backup of the stock OS. I also am unable to mount the device to my computer to install a clean rom. (I've tried 3 computers, LG drivers, drivers from PDAnet, nothing works). ADB sideload also won't start inside TWRP and I can't get any adb commands to work. When I type adb devices it either shows nothing, or it lists the device as "host" and doesn't allow me to do anything.
Does anyone know any workarounds for these issues? I'm starting to run out of options. When I boot my phone I just get a loop to the screen that says "Secure boot failed." TWRP is the only thing I can get into, but if I can't push any files to the phone, it may as well be bricked. I also can't use the LG manufacture tool to take it back to stock because it doesn't recognize my device as the 980. The LG Mobile support tool also does not work - it just hangs when it attempts to download the firmware.
Would greatly appreciate any input!!
Flash CWM via TWRP. Has loki w/ OTG support. Plug OTG drive with backup on it. Flash. Worth a try.
Steamer86 said:
Flash CWM via TWRP. Has loki w/ OTG support. Plug OTG drive with backup on it. Flash. Worth a try.
Click to expand...
Click to collapse
There would be no way to flash CWM since it wasn't already on the device. Luckily I was able to fix this simply by wiping the whole phone, which wiped out the bad CyanogenMod info and let me factory reset with the LG flash tool.
Derp.... My fault lol. I keep backups of stock recovery and others. Shouldn't assume others do. Nice, odd you couldn't do it to begin with. I keep a virtual Windows XP for dealing with major phone bs like adb, qpst, lgnpst, ect. Just handles these things with more stability. LG Updater and LGNPST seems real finicky with the G2.
Hey guys,
Yesterday I tried, after a few months of not modding my phone, to update my recovery as i was running a very old version of TWRP. Long story short I did something wrong somewhere and my phone has ended up in a bit of a weird state.
At the moment the OS is BlissRom, however it fails to boot. The loading screen runs very slowly and never actually boots the OS. The current recovery is the stock recovery.
The thing that is giving me an issue is the fact that somehow the bootloader has locked, so I am unable to flash a new OS onto my phone. I'm not able to flash anything onto my phone as it throws an error telling me the phone is locked.
Overall I aren't able to boot into the OS, however I have access to the stock recovery and fastboot. Unfortunately it looks as though the bootloader has locked some how.
Any ideas how I can fix this, or have I completely messed my phone up?
Thanks in advance.
Hi
U said u were running twrp before which means u have unlocked bootloader and flash roms already.
How did u end up with stock recovery?
Also is it phone being detected bycur PC?
Sent from my ONE A2005 using Tapatalk
I believe it was a result of running the QualComm restoration tool. I ran this and it didn't look as though it did anything however after i rebooted into recovery I found it was stock.
I'm not sure if using this tool also re locked the bootloader however as it appears to be locked and I cant flash anything in fastboot mode.
colinbest2 said:
I believe it was a result of running the QualComm restoration tool. I ran this and it didn't look as though it did anything however after i rebooted into recovery I found it was stock.
I'm not sure if using this tool also re locked the bootloader however as it appears to be locked and I cant flash anything in fastboot mode.
Click to expand...
Click to collapse
Did u also tried command fastboot oem unlock
Sent from my ONE A2005 using Tapatalk
Indeed I have, I get an error saying "phone is locked".
I think the resolution will be running the restoration tool fully but i cant seem to get it to do anything. It just sits there with no progress bars appearing.
Have you ever had any experience with this tool?
No I never used recovery tools.
Can u at any point let's say u boot into recovery and connect the device to PC, will it detected the internal storage?
Sent from my ONE A2005 using Tapatalk
Unfortunately not, if I boot the OS it gets stuck at the loading animation, it isn't a bootloop oddly enough.
Booting in recovery the PC doesn't detect the internal storage, however if I choose "Update from USB" I can see that ADB detects my phone in sideload mode.
Much like in fastboot mode I can see my PC detects my phone in fastboot mode.
I do have some OS zips on the internal storage which I have tried flashing in stock recovery, however these always result in "Install failed" errors.
Dude i think you have to use recovery tool now
Here is the link first read carefully https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Thanks for the link buddy.
I've gone through this thread, I think the issue preventing this from working for me is the fact that although I have installed the relevant drivers, when I plug my phone into my PC the drivers assigned to it are "Android Bootloader Interface". When I try to target another driver, using the Update driver functionality it just refuses to change, saying the driver already assigned is the newer one.
Any ideas how I can get around this? I know ideally it should appear as Qualcomm 9008. I've tried all the methods in the "How to Make the device show as Qualcomm 9008" section without any success.
colinbest2 said:
Unfortunately not, if I boot the OS it gets stuck at the loading animation, it isn't a bootloop oddly enough.
Booting in recovery the PC doesn't detect the internal storage, however if I choose "Update from USB" I can see that ADB detects my phone in sideload mode.
Much like in fastboot mode I can see my PC detects my phone in fastboot mode.
I do have some OS zips on the internal storage which I have tried flashing in stock recovery, however these always result in "Install failed" errors.
Click to expand...
Click to collapse
Here's what to do...
U will need to sideload the stock rom which can be downloaded from here: https://s3.amazonaws.com/oxygenos.o...4_OTA_020_all_1608262242_44a55e674a2b4bf6.zip
-Place the zip in ur adb folder and rename it to update.zip.
-Connect the Oneplus2 to the PC with USB cable and open a command prompt or terminal on your PC. To do this open the ADB folder press shift + right click and click on open command here.
-Reboot to recovery and select install from usb.
-Flash the OxygenOS on OnePlus 2 by typing:
adb sideload update.zip
-Now the update will start and this will take some time.
Hope it helped[emoji106]
Sent from my ONE A2005 using Tapatalk
Brandon Indar said:
Here's what to do...
U will need to sideload the stock rom which can be downloaded from here: https://s3.amazonaws.com/oxygenos.o...4_OTA_020_all_1608262242_44a55e674a2b4bf6.zip
-Place the zip in ur adb folder and rename it to update.zip.
-Connect the Oneplus2 to the PC with USB cable and open a command prompt or terminal on your PC. To do this open the ADB folder press shift + right click and click on open command here.
-Reboot to recovery and select install from usb.
-Flash the OxygenOS on OnePlus 2 by typing:
adb sideload update.zip
-Now the update will start and this will take some time.
Hope it helped[emoji106]
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
Hey dude, thanks for the help! So I went through these steps and it actually appeared to sideload and update properly.
However now it looks as though my phone is stuck at the one+ logo when I go to boot the OS.
colinbest2 said:
Hey dude, thanks for the help! So I went through these steps and it actually appeared to sideload and update properly.
However now it looks as though my phone is stuck at the one+ logo when I go to boot the OS.
Click to expand...
Click to collapse
Try this one :
https://s3.amazonaws.com/oxygenos.o...4_OTA_019_all_1606041303_bd42fc5cc5cc4ab2.zip
If still stuck on boot logo, boot in fastboot, connect to PC and run command : fastboot erase userdata
If not work try sideload a rom u have with same steps[emoji4]
Sent from my ONE A2005 using Tapatalk
So i've gone through every thread here without success. I have a unlocked bootloader but no OS nor custom recovery and i cant get into fastboot mode to install twrp. When i use ADB it wont find my device unless i go into Stock recovery -> update through ADB and even then it only recognized my device as sideload. What can i do? When i tried to use the MiFlash tool i cant seem to get the correct qualcomm drivers installed. what can i do?
Edit: I solved my issue by downloader the stock B08 system on my S5 and then i placed it in the external sd. Then i put the SD back into the Axon and installed the system. After i had installed the system and booted into the OS i could enter adb with my device being recognized and after that i flashed twrp by using ADB.
I have a new problem though and that is that i can't install the 3.1.0.0. twrp. it only boots into black screen when i enter recovery. I can use the 3.0.4.0. version though.
You can't enter fastboot mode on your phone. Correct?
I also assume that you installed a ROM from recovery and that's what caused the brick, right?
What happens when you try to enter recovery?
senny22 said:
So i've gone through every thread here without success. I have a unlocked bootloader but no OS nor custom recovery and i cant get into fastboot mode to install twrp. When i use ADB it wont find my device unless i go into Stock recovery -> update through ADB and even then it only recognized my device as sideload. What can i do? When i tried to use the MiFlash tool i cant seem to get the correct qualcomm drivers installed. what can i do?
Click to expand...
Click to collapse
Go into My Computer, manage, devices and try to uninstall all drivers that are possibly related to your device.
Unplug your phone and let the drivers reinstall by itself.
Go into ADB and see if ADB Devices works.
If possible go into ADB reboot edl and try to reflash custom recovery : "axon7tool -w recovery"
When recounting unplug your phone and see if you can reboot, shutdown and enter into TWRP.
ps : i hope you have a backup ?
nonamesl said:
You can't enter fastboot mode on your phone. Correct?
I also assume that you installed a ROM from recovery and that's what caused the brick, right?
What happens when you try to enter recovery?
Click to expand...
Click to collapse
Correct. It simply reboots.
Yup, i tried installing the B29 stock system on my G model and so i suppose i had the wrong bootstack becasue this is where my problems started.
I get to the stock android recovery.
raystef66 said:
Go into My Computer, manage, devices and try to uninstall all drivers that are possibly related to your device.
Unplug your phone and let the drivers reinstall by itself.
Go into ADB and see if ADB Devices works.
If possible go into ADB reboot edl and try to reflash custom recovery : "axon7tool -w recovery"
When recounting unplug your phone and see if you can reboot, shutdown and enter into TWRP.
ps : i hope you have a backup ?
Click to expand...
Click to collapse
It still wont recognize my device. Which driver am i supposed to have in the Device manager? Do you think i can use my old S5 to transfer a Stock system to the sd card and then update my phone manually through the stock recovery and then when i have an OS installed maybe i can connect to ADB. I read somewhere that ADB commands only works in recovery and in the OS.
I have a twrp backup of my system on my SD card so no worries there.
senny22 said:
It still wont recognize my device. Which driver am i supposed to have in the Device manager? Do you think i can use my old S5 to transfer a Stock system to the sd card and then update my phone manually through the stock recovery and then when i have an OS installed maybe i can connect to ADB. I read somewhere that ADB commands only works in recovery and in the OS.
I have a twrp backup of my system on my SD card so no worries there.
Click to expand...
Click to collapse
You should see your phone as QUSB_BULK. Installed the ZADIG drivers ? That may cure the problem.
After that, imo, it is important you can reboot edl and flash TWRP recovery again AND when it recounts, you pull usb.
Normally you will have replaced recovery , reboot ok and you can enter TWRP and fastboot also.
ps : sometimes it is also advisable to go to ADB RECOVERY directly and do the processes.
ps2 : when TWRP backup, you can always put it on SD via other phone and in TWRP restore. Normaly you're good to go then...
Try the Marshall London Bootloader Interface driver maybe?
nonamesl said:
Try the Marshall London Bootloader Interface driver maybe?
Click to expand...
Click to collapse
Ok, should i be able to find my device with "adb devices" if i uninstall all the other drivers and install this driver?
senny22 said:
Ok, should i be able to find my device with "adb devices" if i uninstall all the other drivers and install this driver?
Click to expand...
Click to collapse
Installing the driver and using it for the phone (device manager -> change driver manually (or something of the sort)) worked for me, but it could differ. Let me know. You don't have to uninstall other drivers just use that specific one for your phone by switching the driver manually via device manager.
Recently lost the ability to dash charge and use my USB-C jump drive on my OP6T. I've flashed a couple of different ROMS, I updated to OnePlus6TOxygen_34.J.55_OTA_055_all_2107132253_b2cbbb97b4eee.zip, re-flashed another rom, I even swapped out the port with a new replacement I ordered. I'm out of ideas, the port is new so it doesnt need cleaning, USB debugging has been toggled and USB config set to file transfer. Computer doesnt recognize it using the original cable either. I'm leaning towards a software issue but i'm afraid to do too much flashing as I dont have my USB-C to fall back on as backup and would essentially brick the thing if I cant read from the jump drive. Any idead?
Are you able to run fastboot commands from the bootloader or adb commands in recovery?
Or even mount storage in recovery?
SMcC2 said:
Are you able to run fastboot commands from the bootloader or adb commands in recovery?
Or even mount storage in recovery?
Click to expand...
Click to collapse
I'm able to get to get to fastboot, and now I just screwed myself out of TWRP and root by flashing a rom without TWRP. The PC will charge the phone, but wont see it. ADB sees no devices and Shapeshift's recovery doesnt have many options. Basically now i need to flash a recovery image by device only. and that still doesn't solve the connection and slow charge issue
Are you rooted with Magisk?
You should be able to install the twrp.zip from Magisk if so. If not the TWRP app in may work to get it back.
It sounds like you may need to try the MSM tool soon.
root checker says i'm not properly rooted anymore, i've only got the magisk.apk courtesy of google's restore. Looks like the official twrp app will download but not let you flash the img unless rooted. I'm hoping this is a software bug with the oxygen image since i replaced the cable and port and no fix, otherwise i'm gonna have to buy a new device.
and I dont think MSMtool will do anything if the phones not recognized. the all-in-one tool was useless since it didnt see the phone in fastboot
I am able to wirelessly ADB. but as far as i know, there's no way to flash recovery. As soon as i boot to fastboot I obviously lose wifi. any other ideas? i'm not familiar with wireless adb