hello masters
i this problem about usb debugging
it happens that my just stop in android image start up
this happend bec. i just installed beats sound app
then when it reboot it stay in android image
i already installed everything usb driver
but my problem is i think i didnt enable usb debugging before
so is there any chance to connect it to android AIO FLASHER
AIO Flasher not detecting my device (
you can try go into recovery and find option to "adb sideload" ... once there just connect to PC and do command "adb sideload rom.zip"
of course you need the ROM zip file in the same folder as all your adb stuff ...
Related
I had this problem just this week after i think i updated to latest CW recovery as my optimus one doesnt get detected anymore when connected to pc, making it impossible for me to obtain flashable zip files for my fone. SD card is working fine. USB debugging is unticked. Please tell me how to solve this as I tried to reflash old recovery but still cannot connect using usb.tried flashing backup but i was greeted by md5 mismatch error.Anyways...md5 issue has been solved but the usb thing still doesnt works
Somebody help me please
DistantFather said:
I had this problem just this week after i think i updated to latest CW recovery as my optimus one doesnt get detected anymore when connected to pc, making it impossible for me to obtain flashable zip files for my fone. SD card is working fine. USB debugging is unticked. Please tell me how to solve this as I tried to reflash old recovery but still cannot connect using usb.tried flashing backup but i was greeted by md5 mismatch error.Anyways...md5 issue has been solved but the usb thing still doesnt works
Click to expand...
Click to collapse
Just enable USB debugging and type in 'adb devices' from command prompt. (For adb to work you need Android SDK)
If it reports as some device as detected, things can be worked out.
developer++ said:
Just enable USB debugging and type in 'adb devices' from command prompt. (For adb to work you need Android SDK)
If it reports as some device as detected, things can be worked out.
Click to expand...
Click to collapse
Figured it out by installing lg driver again
Thanks
Hi my neo l not connecting in fastboot mode. I have updated all drivers but when i connect phone in fastboot mode a popup shows unrecognised usb device. Aldo not showing anything when i typed" fastboot devices " in cmd.
Mani-saini said:
Hi my neo l not connecting in fastboot mode. I have updated all drivers but when i connect phone in fastboot mode a popup shows unrecognised usb device. Aldo not showing anything when i typed" fastboot devices " in cmd.
Click to expand...
Click to collapse
Hello friend, try to connect to another USB port on your computer, if it does not work disconnect any USB devices you may have connected and try again, if still don't work is because drivers are not installed, try re-install them again, what windows version are you using, if it is Windows 8 there is special procedure how to install fastboot drivers,
Good luck
Yeah first make sure you see it in the Device Manager on Windows.
galarpo said:
Hello friend, try to connect to another USB port on your computer, if it does not work disconnect any USB devices you may have connected and try again, if still don't work is because drivers are not installed, try re-install them again, what windows version are you using, if it is Windows 8 there is special procedure how to install fastboot drivers,
Good luck
Click to expand...
Click to collapse
I have instaled all fastboot drivers. Also changed the cable.and in device manager it showing unknown device.
I am using windows 8 .which method for installing drivers???
how to
Mani-saini said:
I have instaled all fastboot drivers. Also changed the cable.and in device manager it showing unknown device.
I am using windows 8 .which method for installing drivers???
Click to expand...
Click to collapse
1- Hold SHIFT and restart you computer, always holding SHIFT or run this "shutdown /r /o"
2- You should be now on "Advanced Startup options", select "Troubleshoot" --->"Advanced Options"--->"Startup settings"--->"restart"
3- Next select option 7
4- plug your phone to computer in fastboot mode and install flashtool drivers, remenber to say yes on the windows appearing during installation, after everything is installed, restart your computer and problem solved.
My end goal is stock lolipop rooted.
I botched a flash and now I cant get developer mode / ADB working.
When I started, my tablet was stock ROM, towelroot. I connect tablet in developer mode, flashed dual recovery and everything was great. I copied the pre-rooted lolipop ROM to my SD card and flashed it. HOWEVER instead of turning off the device, I selected reboot from recovery. This resulted in boot loop.
SOOOO, I figured no worries, just flash old ROM and try again. So did this:installed Androxyde Flashtool
opened XperiFirm
downloaded 1276-8392 and 1274-8801 (I've tried the rest using both ROMs btw)
Tools>Bundler>Create>Selected folder>selected SGP312 for device
For branding I entered the above ie 1276-8392
For version I entered the ver ie 10.5.A.230
Flashmode>checked boxes to wipe everything
The flash goes through without a hitch. Under about tablet, I see
Model : SGP312
Android Ver : 4.4.2
Kernel : 3.4.0-perf-g32ce454, [email protected]#1
Build Number : 10.5.A.0.230
I activate USB debugging and unknown sources, connect to USB and Flashtool returns: Device connected with USB debugging turned off
I went into device manager and found the MTP driver. Also of note, the device ID is: USB\VID_0FCE&PID_5194&REV_0228
I downloaded Sony's ADB drivers, tried to manually update device driver and windows7x64 kicked back driver is not for your device.
I edited the INF to include the hardware ID exactly as it appears in device manager and tried again. This time windows let me load the driver. It shows up in device manager as 'Sony sa0107 ADB Interface Driver'
HOWEVER, Flashtool is still giving me the same MTP message and if I cmd prompt "adb devices" I get nada.
Is there a way to verify developer mode on the tablet? What else can I try? The tablet gives me a notification when I connect 'usb debugging mode connected, ready to install software'
Thanks!
_sadpanda said:
I went into device manager and found the MTP driver. Also of note, the device ID is: USB\VID_0FCE&PID_5194&REV_0228
HOWEVER, Flashtool is still giving me the same MTP message and if I cmd prompt "adb devices" I get nada.
Thanks!
Click to expand...
Click to collapse
I had a very similar problem in 2014. I do not want to discourage you, but at the end I send it back to sony for a repair. They gave me a new tablet and said that the mainboard was broken.
Nevertheless, there is a thread in Sony cross device general, where people like you end up: http://forum.xda-developers.com/showthread.php?t=1849170
You can try and search for help there, maybe you have more luck then me.
Its odd... ADB was working and stopped after flash. Is this what you had or just no connection from the start?
Sorry, I misread your post. I thought your tablet would not start and you could not get flashmode working. Sorry for that.
What you could try:
1. Be sure you actually activated USB debugging in developer options
2. When you connect the device, you should get a prompt on the tablet to allow usb debugging from that computer
Maybe try "revoke USB debugging authorisations" in developer options and reconnect
3. Install the drivers from flashtool/drivers/ or install sony pc companion. Delete your old driver from device manager.
4. try switching between MTP and MSC mode in usb connectivity menu
Since ADB worked before it was probably no driver problem. Now you cannot be sure. Most probably you tapped away the said prompt of allowing usb debugging when connecting.
If none of this helps I don't know of anything more. Maybe try different usb ports or even computers.... Or try to flash again
bernddi said:
4. try switching between MTP and MSC mode in usb connectivity menu
Click to expand...
Click to collapse
UGH!!! I'm a jacka$$. I totally forgot about that menu/setting. fixed instantly.
I tried to install Xposed through Magisk on my device and then it got stuck in a boot loop. I was going to use magisk module uninstaller with twrp but with the usb connected to my computer it only comes up as a cd drive. I tried putting it into download mode but adb wouldn't recognise it.
Edit: Hisuite asked me to install usb driver and it then it worked or it might of been me turning on mtp
Download Mode aka fastboot mode need fastboot.exe, no adb. Fastboot devices and see your phone id.
I upgraded couple of days ago to new PC - Ryzen 5 2600/rog strix b450-f gaming with clean windows 10/64 and now i have problems with adb bootloaader driver and cmd commands. Before i was on intel xeon/gigabyte motherboard socket 775 windows 7/64
I use tool all in one, install usb drivers. When phone is turn on, with usb debuging, i can enter phone storage, device manager see phone as poco,everything is ok. When i start tool all in one i can see device id,i can go into fastboot mode(phone restart and go into fastboot). When phone goes into fastboot,device manager see it as Kedacom usb device/android bootloader interface, or sometimes as android phone/android composite usb device. I have adb/fastboot files all i need on pc. When i enter some command trough cmd,for example fastboot devices,or fastboot reboot bootloader, on phone screen goes to dark and in left top corner with small font is written phone will turn off. On cmd i see afther command i set and pres enter only ??????? questionmarks. So i must again manually enter fastboot mode.
I cant get fastboot/adb to work. I try to install other adb/fastboot drivers(xiaomi and google original from tool all in one),try to connect phone cable to other usb port(2.0/3.0/3.1) at the back of pc chase,also 2.0 in front case. I try other usb cable also. Try to manually update google drivers from this forum,then i cant bcouse some ini file is missing or if i set have disc and do manualy with some other driver it cant see phone in adb-fastboot mode. I try all that fall on my mind with no luck.
At the and i goes to my friend and try to install tool all in one,install google usb drivers from that tool,install adb/fastboot files. Try to enter fastboot and do same commands as before with cmd,and everything is working fine as it was with my old pc setup. Device manager see it as Kedacom usb device/android bootloader. He also have amd cpu/chipset - but it is not ryzen with fresh w10/64
Is there any fix for my case? Does anybody have same problem?