Hello, i've been trying to install a custom mode but i can't because i only have access to recovery mode now because I made a backup but deleted when i wiped my data
So I tried to install my custom rom by using adb but when i type "adb devices" in cmd it just won't list it.
Do you know how to fix this?
Also, in ADB sideload, it shows me "unable to mount /usb-otg" dunno if it is important.
Thanks
EDIT : Problem solved, i went to pheriphericals and updated my G2 drivers.
Related
hi there
I installed twrp using adb, that means i am able to use adb when i'm in the OS
but when i boot into TWRP, i cant get my pc to recognize my phone, when i type "adb devices", nothing shows up ...
and when im in TWRP and go to advanced, adb sideload, i swipe to start it and it says "starting adb sideload feature.." and it stays forever -_-
what could be the problem and how can i fix it ?
j_h3000 said:
hi there
I installed twrp using adb, that means i am able to use adb when i'm in the OS
but when i boot into TWRP, i cant get my pc to recognize my phone, when i type "adb devices", nothing shows up ...
and when im in TWRP and go to advanced, adb sideload, i swipe to start it and it says "starting adb sideload feature.." and it stays forever -_-
what could be the problem and how can i fix it ?
Click to expand...
Click to collapse
Which twrp, first version didn't have adb support as I recall...
Happened to me too. Go to device manager and uninstall any drivers, then install generic adb device
Hi folks!
I wanted to install Cyanogenmod as described in Cyanogenmod Wiki.
So I downloaded ioroot, rootet my phone via adb and used AutoRec to install TWRP (version 2.7.0.0).
Then I rebooted into recovery mode, wiped EVERYTHING and wanted to sideload the CM image via adb.
So in TWRP I selected Advanced/ADB Sideload and swipe to start sideload but all that happens is the notification "Starting ADB sideload feature...".
Consequently the phone is not recognized by adb on my PC.
What can I do to make the sideload feature work?
BTW: TWRP tells me that my devices doesnt appear to be rooted when I want to leave TWRP (reboot). Moreover when i want to enter TWRP again (by pressing POWER + VOLUE DOWN) I first get a screen that asks me if want to do a factory hard reset! Only if I agree (by pressing the power key) I get into TWRP.
Contrary when I enter the Download Mode (VOLUME UP when when connecting the powered off phone to the USB port) I am told that the phone is rooted. Moreover the LG Mobile Support Tool is able to detect the device and tells me that the installed software is up to date.
Thx!!
have you tried typing 'adb sideload rom.zip' on a command window on your pc? name the rom, rom.zip, and have it your adb folder.. also type the command from that folder
Make sure you're in the proper folder in prompt and the device name will be sideload if you do, adb devices.
Sent from my LG-D800 using Tapatalk
meangreenie said:
have you tried typing 'adb sideload rom.zip' on a command window on your pc? name the rom, rom.zip, and have it your adb folder.. also type the command from that folder
Click to expand...
Click to collapse
Thanks but this doesnt help either. Same error message "error: device not found"
boot into twrp, don't start sideload
try adb devices, if you get not find you need to change the usb drivers
when you have it working, type, adb push /sdcard/ rom.zip .. check the syntax on that command, but i think that's right from memory
After flashing recovery via flashify i get TWRP 2.6.3.3
but when i try to get firmware update mode (download mode) it stucks says: download mode.. and cannot recognize by PC whatsoever, so cannot use lg flash tool or support tool or dp-tool.
and in this mode phone gets really hot!
when i enter recovery i couldnt manage to install any rom because my sdcard is empty and otg-usb is not recognizable.
and in recovery mode, pc cannot detect the device only unknown device as "LG D802"
so i found android adb driver and manuelly install to windows.. but still i cannot pust any file over usb via adb.
adb push command gives me "read only system" error.
i also tried adb sideload to install custom rom from pc..
adb sideload command still gives me "read only file system"
i am assuming this is due to secured Kernel.. but i don't know what to do..
i also try the terminal command in twrp for adb commands.. but still no luck.
what can i do to push any custom rom.zip or any way around to install kdz?
i manually installed usb adv driver.. do i need to install as lg adb device..
can you give me a link to adb "inf" driver file?
Y uninstall current lg driver and download newest driver then reinstall( y can use google to find). Good luck
thanks i solved the problem via ubuntu.
i used "adb push" to /sdcard still got "read only" error.
but when i used "adb push" to /tmp i can managed to send/copy some zip files into my device.
I want to unroot my phone and I did manage to flash stock recovery.
But now I want to flash stock firmware through adb sideload.
But when I typ adb devices it does not recognize my device and when I type the sideload command, it says error: device not found.
I am using minimal adb fastboot version 1.4.2.
I already tried to use all the different kinds of drivers @ device manager
I am really out of idea's and hope someone here knows what to do.
Edit:
When I use TWRP recovery and I use sideload, adb can recognize my device (and fastboot can also recognize my device).
So only through stock recovery adb cannot recognize my device.
And I remember that USB debugging is off, I do not know if that has to do something with this?
vldholy said:
When I use TWRP recovery and I use sideload, adb can recognize my device (and fastboot can also recognize my device).
So only through stock recovery adb cannot recognize my device.
And I remember that USB debugging is off, I do not know if that has to do something with this?
Click to expand...
Click to collapse
For the stock recovery, Side load Works.
But only Side load, not "adb devices".
After you have selected Side load from stock recovery,
(Boot in stock recovery,
Select your language, -> install from usb -> yes )
Only after this, your device will show in "adb devices"
It will show as Side load device. Then Side load as usual., It will work.
P.S. - USB debugging is not checked in recovery mode.
pollob666 said:
For the stock recovery, Side load Works.
But only Side load, not "adb devices".
After you have selected Side load from stock recovery,
(Boot in stock recovery,
Select your language, -> install from usb -> yes )
Only after this, your device will show in "adb devices"
It will show as Side load device. Then Side load as usual., It will work.
P.S. - USB debugging is not checked in recovery mode.
Click to expand...
Click to collapse
Sorry for late reply!
I did what you said, but I get this error:
error: device '(null)' not found
And when I select install from usb -> yes, Windows notify that there is a problem with the device and cannot recognize it.
What drivers must be installed, OnePlus drivers and ADB drivers?
Does someone know how to fix it?
vldholy said:
Does someone know how to fix it?
Click to expand...
Click to collapse
The problem is stock recovery that you Install does not work well in windows 10
1 Boot in bootloader install TWRP again here
2 Reboot in TWRP Recovery
3 Wipe> Advance Wipe> Select Dalvik & Cache System & Data> Swipe to Wipe
4 Reboot in TWRP Recovery Transfer OOS 4.5.8 Full Rom Zip to the device over MTP
5 Install Menu> Select OOS 4.5.8 Full Rom Zip> Swipe to Flash
6 Reboot System
Now you are in full stock OOS
If you restart now in stock recovery you will see that sideload will work
Adb sideload with stock recovery not work in Windows 10, if you use Windows 7, you'll find that it work well.
The problem is stock recovery from the official site
This OP5_recovery.img
If you are in TWRP and install OOS stock rom sideload will work in windows 10
Had driver issues to what j did was with twrp installed I transferred the Oxygenos rom to internal storage installed it from twrp and then put the OnePlus recovery back on
Can't flash via TWRP, "failed mount system", twrp sideload not working either.. stuck
I need my phone for work tomorrow so any help would be greatly appreciated.
I'm on TWRP 3.2.3-1 and was using the latest stock oreo rom from here: https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
My phone suddenly didn't have a reception today, after rebooting I regained reception but couldn't make calls. I rebooted to recovery and tried to dirty flash the same stock twrp flashable oreo rom that I was using and it failed. Apparently the OS got corrupted. I tried repeatedly to flash the ROM and then noticed I was getting an error : failed to mount system , invalid argument. I couldn't mount system via the Mount tab in TWRP and I couldn't find anything helpful to resolve this error.
I did some more research downloaded the fastboot flashable ROM from here : https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433 and tried to flash the rom via adb using adb sideload in twrp but twrp doesn't seem to load that function correctly. In the elevated command prompt in the adb directory I type adb sideload filename.zip and it just freezes up my PC. My device does show up with the adb devices command and shows " *Serial Number* RECOVERY ".
I don't understand what to do with the instructions in the fastboot flash stock thread I posted above and I'm at the limit of my knowledge. No idea how to proceed... any help is greatly appreciated.
I tried extracting the xml.zip into the adb folder and rebooted to bootloader/AP Fastboot Flash Mode and was going to try the commands in the fastboot Rom thread but my device only shows up in adb devices when I load twrp. uhhhhgggghhhhhh guess I'll have to buy a backup phone tomorrow while I try to get this one working
Holy hell.... I didn't realize since I was in the fastboot/bootloader I had to use "fastboot devices" command to see the device. Tried that and saw the device listed, so I created a .bat file using the commands in the fastboot roms thread above and I have a functional device again. Whohoooooo!
Did you try to format /System/ as EXT4?