Hi,
I was able to install custom rom on my v300s
but found out that twrp wasn't installed.
I used my computer adb to open twrp and installed custom rom
Then i found our something was wrong, any way to install twrp from now on?
i tried to open twrp with adb again,
when i use adb devices I was able to find lge~~~ on there.
but when i try fastboot boot twrp, it shows awaiting for devices then nothing happen
(I set my phone as ptp mode then usb debugging was on.
on my laptop the phone was resister as portable device and using MTP usb driver, wasn't able to change it to adb driver)
then i tried to boot my v30 as bootloader but pressing volume down key didn't work.
any way to install twrp from this state?
sorry for my bad English
I think you need to ensure you have the correct drivers installed. Even when they are, you need to also check in Device Manager that the correct driver is used when the phone is connected. It also sounds like you don't have USB debugging enabled.
ldeveraux said:
I think you need to ensure you have the correct drivers installed. Even when they are, you need to also check in Device Manager that the correct driver is used when the phone is connected. It also sounds like you don't have USB debugging enabled.
Click to expand...
Click to collapse
Ah the usb debugging was enabled.
I found something called qfil from qualcom and was able to reinstall my bootloader img file with it.
then i was able to connect my device as ADB devices
Thanks btw
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
winxp sp3 sony tablet s when put in recovery mode for flashing the mtp driver
shows yellow (!).when i try to install driver manually it trys to start but comes
back with code 10.with tablet in normal mode winxp sees mtp & adb drivers.
the problem is only with recovery mode.tryed all i can think of and read all
solutions but driver still fails to start.so i can,t flash fw!. i really need help with
this one. please someone help i`ll give you a big thanks. i know i am not the
only one with this problem.i hope this is clear enough.
Same problem here:
Everything's fine in normal boot, but in recovery mode, I can't install the MPT driver. Win7pro. It tries to install, but ends up with a Code28 (something in the INF file is invalid, can't tell the english error message, because I have German Win7).
This seems to cause my problem flashing to R5a by AiO or the auto flasher by condi.
I get the exact error message on the tablet, as shown in post #72 in this thread:
[FW R5A WIFI/3G] NEW! custom preROOTed newest stock nbx03 R5A with R1A's recovery
Trying since four nights...
At least I managed to flash and root to 4.0.3 R2a from the "unrootable" 3.2 R10 by flashing via recovery mode to Sony original ICS R2a (downloadable from sony) and then using the AIO 5.3 to root. Don't know why this way is not published here... Tried updating to 3.2.1 etc, nothing worked... the found the links to sony's fw and thought "WTF! Let's try ICS R2a, worst case is an also unrootable Tablet but with ICS". Worked, and was rootable then.
Just ignore the problem. I believe seeing the alerted MTP USB Device in Windows Device Manager when your tablet is in Recovery Mode is being cause by your tablet's borked Android System Recovery Revision 36 (i.e., Rev.36). This problem did not occur with earlier revisions of Android System Recovery. Normally, no MTP USB Device (or Sony Tablet S) should be displayed or even installed for Recovery Mode because a tablet in Recovery Mode cannot provide MTP functionality. Recovery Mode only requires Android Composite ADB Device be installed. Normal Mode, however, requires both Android Composite ADB Device (but only when the tablet's USB Debugging is turned on) and MTP USB Device, which Windows Device Manager renames and displays as Sony Tablet S.
You are basically right... it was ADB drivers, not MTP.
I tried all possible drivers from the list, also some "phone" devices. And YES!! Windows accepted one of them...
After that, I had no problem flashing my tablet to ICS R5a!!
please, could somebody who has writing permission in the dev forums, tell Condi, that the AiO 5.3 tools tells you to check this driver ONLY AFTER you are NOT stuck in "status7" error!!!!!
You do NOT get the message in the terminal box, IF you are stuck.
That would have saved me one or two nights trial and error...
But, after all, I have a nice working ICS R5a on my tablet S
I will post a how-to for other 3.2 kernel10
that explains a lot. so i need to find another adb driver that works in recovery mode and
not worry about mtp driver?.
phc1234 said:
that explains a lot. so i need to find another adb driver that works in recovery mode and
not worry about mtp driver?.
Click to expand...
Click to collapse
Right.
In device manager, it's "android phone" (?), when you select driver manually, then I think it was the same as on the first install, so the third ADB device in the drivers list.
Windows fools you, it installs an MTP driver, and thus keeps you from using your brain
Install ADB drivers, check whether your tablet will be correctly recognized in both modes... then at least the all in one tool with custom zip will work (hopefully).
Why the flasher did not work? Don't know. looking again at my error messages, I would guess, that the busybox was not working correctly. I don't know if you have to install busybox before, manually. I thought everything was integrated into the flasher...
android phone dosent show in device manager
ThreeEyes said:
Right.
In device manager, it's "android phone" (?), when you select driver manually, then I think it was the same as on the first install, so the third ADB device in the drivers list.
Windows fools you, it installs an MTP driver, and thus keeps you from using your brain
Install ADB drivers, check whether your tablet will be correctly recognized in both modes... then at least the all in one tool with custom zip will work (hopefully).
Why the flasher did not work? Don't know. looking again at my error messages, I would guess, that the busybox was not working correctly. I don't know if you have to install busybox before, manually. I thought everything was integrated into the flasher...
Click to expand...
Click to collapse
[edit]
thats the problem android phone dosent show up in device manager. tryed on 3 wixp computers and nothing no way
ti install adb drivers.
phc1234 said:
[edit]
thats the problem android phone dosent show up in device manager. tryed on 3 wixp computers and nothing no way
ti install adb drivers.
Click to expand...
Click to collapse
But by manually updating the driver and choosing manually, you can assign ANY driver to any device - it may not work or even do some damage to the system, but basically, it's your choice!
Take the device with the "!" and give it the right driver...
"CAT" above is right with rel5 and 5a that they changed the recovery rev to 36 and this rendered the
tablet s from loading any mtp driver or seeing the android phone entry in device manager so no way
to install adb driver.this has killed conis AIO tool flashing firmware and roms until someone breaks
the lockdown sony put in.
today i reflashed my phone with stock 4.0.4 french ftf and it is working fine with usb debugging off but with debugging on, my computer doesnt see the phone! what should i do?
i have reflashed it but still usb debugging mode is not working! help! please what can the problem be?
plz help !
im stuck on stock! no root! nothing good!
First: Don't Panic.
Second: Check your drivers. If not properly installed, try one from sony (just google your device together with "adb driver").
Third: after a complete flash it's like you've never touched your device, means you have to re-root your device normally.
i hope this helps.
murderered said:
First: Don't Panic.
Second: Check your drivers. If not properly installed, try one from sony (just google your device together with "adb driver").
Third: after a complete flash it's like you've never touched your device, means you have to re-root your device normally.
i hope this helps.
Click to expand...
Click to collapse
no its not working!
ive installed a new windows on virtualbox but there also no usb debugging is working!
and how do you install the adb drivers in the zip?
even though it is in debugging mode..when i try to root, it says please connect your phone in debugging mode
Can't say if it generally works with virtualbox. try to get drivers for your native system.
So the question is now: What's your host system?
If it's Windows, get Flashtool and install included driver (found in <FlashtoolInstallDir>\driver) just for rooting the device.
If you're using linux you can look if your device was recognized properly with lsusb it should be listed there.
You can try it too in virtualbox, but i don't trust the USB-driver (i would not flash or so through it) and do not recommend it.
murderered said:
Can't say if it generally works with virtualbox. try to get drivers for your native system.
So the question is now: What's your host system?
If it's Windows, get Flashtool and install included driver (found in <FlashtoolInstallDir>\driver) just for rooting the device.
If you're using linux you can look if your device was recognized properly with lsusb it should be listed there.
You can try it too in virtualbox, but i don't trust the USB-driver (i would not flash or so through it) and do not recommend it.
Click to expand...
Click to collapse
i am using windows 7 32 bit
ive already have flashtool and have tried to install the drivers but nothing works!
Ok, you've installed (i assume) the right adb drivers for your device through the installer located in <FlashtoolsInstallDir>\driver.
So is there any Android/Sony (Ericsson) named device in your device manager? What does Flashtools write if you connect? If your device is listed in device manager, does it show an error, if yes which error?
murderered said:
Ok, you've installed (i assume) the right adb drivers for your device through the installer located in <FlashtoolsInstallDir>\driver.
So is there any Android/Sony (Ericsson) named device in your device manager? What does Flashtools write if you connect? If your device is listed in device manager, does it show an error, if yes which error?
Click to expand...
Click to collapse
in flashtool it shows the same thing in on and off
the 2nd one is debugging on and 3rd with off
Please post output of "adb devices" (if not recognizing, try again after "adb usb"). If no serial number/device is shown then do following:
There is a newer version of Flashtool available, update to 0.9.11, http://androxyde.github.io/
check after reinstallation (of drivers, too)
Maybe you have to try sonys driver from the zip. So extract them (all files).
right click at your device in the device manager
click to "update driversoftware" (or something like that, i don't have english windows)
click "search on my computer for new drivers"
choose from list
display all devices
click the button below the list (i have no idea what there could be written, it's not "windows update")
search for the inf-file extracted and choose the "sa<somenumbers>adb.inf"
if not already installing, choose "Sony Ericsson saXXXX ADB Interface Driver"
reboot (pc)
check again
Hello,
I'm trying to connect my Samsung GS3 to my computer to use with the Android SDK Manager and the ADB console, but when I connect it to my computer it recognizes it as a Camera and ADB doesn't recognize it either, how do I fix this?
I'm locked out of my phone and trying to unlock it using methods from here: http://forum.xda-developers.com/showthread.php?t=2620456. So I have no interaction with my phone beyond the locksreen to change from PTP to MTP as I've seen people with similair problems suggest. Is their a workaround?
1337Dev said:
Hello,
I'm trying to connect my Samsung GS3 to my computer to use with the Android SDK Manager and the ADB console, but when I connect it to my computer it recognizes it as a Camera and ADB doesn't recognize it either, how do I fix this?
I'm locked out of my phone and trying to unlock it using methods from here: http://forum.xda-developers.com/showthread.php?t=2620456. So I have no interaction with my phone beyond the locksreen to change from PTP to MTP as I've seen people with similair problems suggest. Is their a workaround?
Click to expand...
Click to collapse
install kies if you have it installed already then uninstall it then install again
1337Dev said:
Hello,
I'm trying to connect my Samsung GS3 to my computer to use with the Android SDK Manager and the ADB console, but when I connect it to my computer it recognizes it as a Camera and ADB doesn't recognize it either, how do I fix this?
I'm locked out of my phone and trying to unlock it using methods from here: http://forum.xda-developers.com/showthread.php?t=2620456. So I have no interaction with my phone beyond the locksreen to change from PTP to MTP as I've seen people with similair problems suggest. Is their a workaround?
Click to expand...
Click to collapse
Since you're already looking in the right place, consider installing a custom recovery (such as philz) with odin and then flash the zip.
Thanks for the help. I was finally able to get my computer to recognize the GS3 (Installed Samsung USB Drivers from their website instead of Kies). But now after it recognizes that I have new hardware installed, when I try to use the Wizard to automatically install the drivers I get the error: "The required section was not found in the inf", did some searching and realized that this is due to not having the wpdmtp.inf file on your computer. I've checked and it is indeed missing, does anyone now of a way to install this file?
I'm still locked out of my phone. And I don't have an SD Card to install recovery and flash the zip as dxppxd suggested.
1337Dev said:
Thanks for the help. I was finally able to get my computer to recognize the GS3 (Installed Samsung USB Drivers from their website instead of Kies). But now after it recognizes that I have new hardware installed, when I try to use the Wizard to automatically install the drivers I get the error: "The required section was not found in the inf", did some searching and realized that this is due to not having the wpdmtp.inf file on your computer. I've checked and it is indeed missing, does anyone now of a way to install this file?
I'm still locked out of my phone. And I don't have an SD Card to install recovery and flash the zip as dxppxd suggested.
Click to expand...
Click to collapse
Take another shot by booting into a custom recovery, most give you adb access while in recovery.
If the phone is locked with usb debugging disabled you won't be able to get adb access.
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.