Unable to see device in bootloader mode. - Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl

Hi XDA,
I have a problem where I'm able to see the device when turned on, but when I enter the bootloader through ADB, suddenly the device is not seen anymore. Therefore, I cannot continue to install TWRP (and a custom ROM after).
- I think this has to do with the weird USB driver that appears to be installed when entering the bootloader, it is called "Samsung Mobile USB Modem". In the device manager, it is also in the modem category, which is very odd.
- When the tablet is active regularly, the APK Installer tells me that the Device status is OK, which doesn't appear to be the case in the bootloader...
- When I uninstall the Samsung Mobile USB Modem when in the bootloader, it just reinstalls again if I reconnect the tablet to the PC.
What do I need to do to make sure I can also see the device in the bootloader? I really want to get rid of the Samsung ROM
Thanks in advance,
Reinier

Related

R800i Issues with USB Driver and Bootloader!

Hi Guys,
Any help would be great! i do have google talk if anyone is willing to help me out!
My R800i Is rooted and has a version of recovery but not sure which version, i am wanting to update my phone with a better kernel and rom since the current one i have installed is giving me issues ( not being able to receive incoming calls for example )
Another problem is i reformatted the phone since i was having issues with receiving calls but now when i connect my phone to ANY computer via the USB cable the computer trys to install MTP or MSC driver ( depends on which connection type i select ) the Installer fails and i cant even take any files off my phone.
Provided details below. i want to somehow get into the current bootloader and install the ROM thats on my SD card! i do have flashtool installed and Android tool SDK installed but still no success in phone wanting to talk to my laptop.
I am running windows 7 64 bit. i am starting to think the phone is belond repair since i cant get any software to work between the phone and computer.
does anyone know what buttons i need to push on the Xperia Play to enter into the boot loader, i have tried pressing the back button and search button on phone boot but nothing happens apart from the phone starts up normally.
would a factory reset delete the boot loader and other config-ed software off the phone is this why i cant enter the boot loader or am i not pressing the right buttons on boot.
Any help would be really appreciated!
IMEI:
357302043579712
IMEI Software Verson
49
Available Speech Codecs
HR, FR, EFR, AMR_HR, AMR_FR
Working Bands
GSM850, GSM900, GSM1800, GSM1900, UMTS_BC1, UMTS_BC8
Rooting Status Bootloader Unlocked Allowed: Yes
Phone Software Version
1245-8821_4.0.1.A.0.283
S1 Boot Version
1241-3656 R9A021
EST Software Version
1242.5099_10
Android Version
2.3.4
Baseband Version
8x55A-AAABQMAZM-203028A-49
Kernel Version
2.6.32.9-perf
Build Number
4.0.1.A.0.283
If you want to change the kernel you must unlock your bootloader. If your Xperia Play is a SIM free one, you can do it for free in this link: http://unlockbootloader.sonymobile.com
For SIM locked devices I think you must find another ways to do it. There are some online sites that unlock bootloader to SIM locked devices for a fee.
Once you have unlocked your bootloader, turn off the phone, hold on the search button, plug the USB cable in the computer, release the search button (power button LED will be blue) and install this driver: http://drivers.softpedia.com/progDownload/Google-USB-Driver-Revision4-Download-139077.html
Now you are ready to flash any kernel you want with Flashtool or any other app.
Thanks for the information, i have already done this, i payed £25 for a guy on this forum to unlock my phone to any network. i'll give this a try and get back to you, problem is the phone doesn't like to talk to my laptop via USB cable keeps on failing to install the drivers..
Thanks for quick response.
PsychoShaft said:
Thanks for the information, i have already done this, i payed £25 for a guy on this forum to unlock my phone to any network. i'll give this a try and get back to you, problem is the phone doesn't like to talk to my laptop via USB cable keeps on failing to install the drivers..
Thanks for quick response.
Click to expand...
Click to collapse
I have tried what you said but having problems with connecting my phone to my Windows 7 Laptop!
Check your device manager. The fastest way to open it is running this command: devmgmt.msc
There must be some kind of Android device while your phone is connected in fastboot mode. If you see it, update its driver with the Google USB driver v4 pointing at the folder path with the uncompressed files.
jcarbox said:
Check your device manager. The fastest way to open it is running this command: devmgmt.msc
There must be some kind of Android device while your phone is connected in fastboot mode. If you see it, update its driver with the Google USB driver v4 pointing at the folder path with the uncompressed files.
Click to expand...
Click to collapse
Hi I tried what you said, i Turned off my phone and holded the search button and turned it back on, the light went blue and the computer popped up trying to install fast boot i point to the SDK folder to update the driver but it fails.
do you have google talk might be easier on there to talk! cheers!
I'm not using gtalk atm. Sorry.
Be sure the driver you downloaded is named usb_driver_rev4.zip: http://drivers.softpedia.com/dyn-postdownload.php?p=139077&t=4&i=1
If Windows doesn't detects any driver in that uncompressed folder, you can choose to select the device from a list, point to that folder and force to install the driver. It's named something like Android ADB Interface.
jcarbox said:
I'm not using gtalk atm. Sorry.
Be sure the driver you downloaded is named usb_driver_rev4.zip: http://drivers.softpedia.com/dyn-postdownload.php?p=139077&t=4&i=1
If Windows doesn't detects any driver in that uncompressed folder, you can choose to select the device from a list, point to that folder and force to install the driver. It's named something like Android ADB Interface.
Click to expand...
Click to collapse
Thanks for the download link, i going to try this in a bit and get back to you! thanks for the support guys! :good:
Just tried, i put my phone into Media Transfer Mode.. my computer tried to install the MTP usb device and i directed the installation to the driver you linked..
Update Driver Software says: the best driver software for your device is already installed MTP USB DEVICE, there is a small yellow triangle on the icon and in MTP USB Device Properties it says: This device cannot start. (Code 10)
i need someone to Teamviewer with me, for the record i don't have the Sony Ericsson software installed on my Computer because that still wont install the drivers for my phone, i also know its not needed for installing new kernel and roms.
i tried connecting this phone to a bunch of pcs including my friends and it still fails to install any drivers!!! i think i am just going to bin this phone! i have had enough (
You must install that driver when you plug the phone in fastboot mode. It shouldn't work in any other case. In other words, when you plug your Xperia Play being powered on and Android is running it needs one driver, and when you boot it in fastboot mode you need other driver.
Please, install the driver following the steps previously posted with your phone in fastboot mode (blue LED).
Hello, i put my phone into fastboot mode, my device manager shows 1 device not installed S1Boot Fastboot, i right click go to properties and click update driver...
then i browse my computer for driver software i point the location to usb_driver_rev4\usb_driver and it says: Windows was unable to install your s1Boot fastboot!
Ok, let's see...
Try to update the driver using the "choose from a list" option to force the installation, point to the driver folder and select "Android ADB Interface" from the list. If Windows shows a warning message don't worry about it and go ahead.
i tryed this and its not wanting to work (
Sorry to hear that because I don't have any more ideas for your problem.
Maybe you may spend some minutes searching in the forum to find some detail that can help you.
i need someone with teamviewer to help me go though the setup process again, if anyone is willing to get my phone working i will happy pay them some money!
Thanks Jcarbox for all your support!
Regards
Paul
I just check the Windows device manager with my phone plugged in bootloader mode and it appears as Android Bootloader Interface, so this is the device you must choose from the list when you install the driver.
Hope this helps you.
thanks for the help, to bad my phone isnt having any of it.. just going to buy another phone (
This may work
PsychoShaft said:
thanks for the help, to bad my phone isnt having any of it.. just going to buy another phone (
Click to expand...
Click to collapse
hi PsychoShaft,
I had similar problems. I don't know how to fix it permanently. but i do this to make it work for some time.First, download flashtool and install it.Open your device manager and select view->show hidden drivers.Then, delete all your drivers related to xperia play. like the adb interface, semc flash ,etc. All of them in all categories. then reboot your computer into safe mode with administrator and connect your device with flashtool running in your windows in safe mode. then the flashtool will indicate that you don't have the drivers. then,open the drivers folder in flashtool and use the setup to install arc-play-...,flashmode drivers and fastboot mode drivers.then after the installation is over windows will ask you to reboot.now reboot with your mobile connected. after boot windows will automatically install the drivers. then unplug your phone and turn off it and connect in flash/fastboot mode.it will automatically install drivers.wait for windows to say drivers installed successfully or installation failed. don't unplug it in the middle of the process then you will have to start from first.sometimes it will not work in the first time ,then reboot into safe mode and try again installing the drivers and rebooting into safe mode itself and connecting your device.at one point of time flashtool will say your device is connected in flas/fastboot mode.then continue with flashing
Gladwin.
Thanks for the support guys i managed to solve the issue!
^^^^ Glad i could help
Sent from my GT-I9300

[Q] Problems in adb/fastboot

Hey all,
I've been rooting phones for a little bit, so when I got my Nexus 7 a couple weeks ago and found that it was as simple as "fastboot oem unlock", I was thrilled. However, it ended up not being that simple, of course.
At first I couldn't get the device to show up for ADB or fastboot at all, even though Windows recognized the device. I downloaded the zip file of the drivers from Google, no luck. Downloaded a new version of the Android SDK, and used the adb/fastboot from it, and then ADB was able to see the N7 and was able to reboot it into the bootloader. However, once in the bootloader, it stops recognizing that the N7 is connected again. Trying "fastboot oem unlock" just causes the program to display <waiting for device> indefinitely.
So that's where I'm stuck now, I haven't been able to find any concrete details on this that are for the N7 2013 (pretty much everything I've found has either not been helpful or has been related to the original N7). Anyone able to help from here? Thanks!
Do u have USB debugging enabled in developer settings? Try turning your USB computer connection to PTP from MTP if you haven't already in storage settings. Then a pop-up will come on your n7 asking to approve your computer to see it. Tell it yes
>^.^< Sent From Meow HTC One
DowntownJeffBrown said:
Do u have USB debugging enabled in developer settings? Try turning your USB computer connection to PTP from MTP if you haven't already in storage settings. Then a pop-up will come on your n7 asking to approve your computer to see it. Tell it yes
>^.^< Sent From Meow HTC One
Click to expand...
Click to collapse
Thanks for the suggestions. Alas, I tried these things. The problem exists now when I'm in the bootloader, which is where fastboot won't recognize that the device is attached.
tigerxchaos said:
Thanks for the suggestions. Alas, I tried these things. The problem exists now when I'm in the bootloader, which is where fastboot won't recognize that the device is attached.
Click to expand...
Click to collapse
When you have the device connected to your computer when it's at the Bootloader screen, what does Device Manager show on your computer? Does it recognize the tablet but doesn't know what it is? You may need to install the drivers when you have the device in the Bootloader menu. I use the Google USB Driver (which you can download in the SDK Manager), right click on the device in Device Manager, select "Update Driver Software", "Browse my computer for driver software", "Let me pick from a list of device drivers on my computer", then browse the list. It may be listed under Android Device, Google...just look down the list, then select the appropriate driver. I believe from there you can select "Android Bootloader Interface", and that should let fastboot commands work.
You may need to reboot the computer.
Make sure you are using the usb cable that came from asus.
Thanks for the help. I tried the process again on a different computer, and eventually got it to work. I was able to unlock bootloader and flash TWRP 2.6.3.0. However, I was only able to mount System, Cache, and USB-OTG as partitions in TWRP, so I couldn't figure out where to drop the SuperSU binary .zip file. I tried rebooting, and (this may have been a mistake) installed the TWRP SU binaries on the way out. Now the device is stuck in a bootloop. Not sure if it was related to the SU binaries or the fact that I couldn't load any sort of data partition. Any thoughts?
EDIT: Apparently the root instructions don't make it clear that you will lock your data partition if you don't boot the device after unlocking the bootloader. I went straight into TWRP from the bootloader after unlocking it, and got a password request. Hit "Cancel" and it let me into TWRP, but factory reset failed. I had to wipe data, wipe cache, then reboot, then do a factory reset and now I'm back in.

[Q] Can't fastboot, won't recognize via USB, can't update recovery

I am having a hell of a time trying to get my phone back to a fully operable phone. I was running SlimBean but had GPS issues so I switched to Carbon. GPS works, but MMS (sending AND receiving) and data connection after WiFi disconnect doesn't work. But now my real problem is not being able to flash a new ROM. I hoped to install a 4.4 ROM, but that requires me to install an update to my recovery. When I boot to bootloader, I select Fastboot (it is highlighted in red), but it does nothing to allow me to install a newer .IMG. Am I missing something?
Not only that, but I'm not able to get my phone to be recognized by the computer that I previously never had an issue with. The phone charges via USB but is not visible by the computer. I've turned on USB debugging in settings, but the computer does not even see it as a device in Device Manager. Is it possible that I've fouled something up physically on my USB port or is it a software/ROM issue? I have even installed a stable 4.3 ROM (cyanogen), and I still can't get the PC to see that I'm connected.
Anyone have any ideas?
Try Flashify from the market to flash the recovery img.
Sent from my Galaxy Tab 10.1

[HELP] No Internet Connectivity after bootloader Unlock

Hi,
I cannot connect to the internet after unlocking boot loader. Phone was already rooted and have dual recovery. I tired to connect wifi and 3G, despite it CONNECT, no data is sent or received.. Rebooted multiple times. no change.
I tried to unlock by bootloader by official method. So here is what i did:
1. Switched off the phone and connected via usb while pressing the vol up button.
2. Blue led appeared and detected by pc (running on Win 8.1 64bit with flashtool installed)
3. opened cmd and checked for connected device.
IT SHOWED NONE!
4. removed usb cable and connected again by holding vol+
STILL ADB DEVICES SHOWS NO CONNECTED DEVICE
5. Device Manager shows something with "Sony s1 boot ..." on android. Still adb shows no attached device.So I deleted the driver, again installed the drivers from Flashtool for my device. Selected manually, (i dont recall the driver name exactly, but its with "s109..." ). After the drivers were successfully installed, i again checked for devices and STILL I DONT FINE MY DEVICE.
6. Again i reconnected the phone.
7. typed the unlock command ' fastboot -i 0x0fce oem unlock 0x<myKey> ' and I got 'OKAY'.
After that I switch on the phone and wondered to see that the internal memory is formated! ( is it suppose to happen when unlocking the boot loader??) And I have to setup, like a band new phone.
Checked the bootloader unlock status. It shows YES.
Sorry I am new to these things. I tried to google and search for similar thread here but I think are different from what i am having here.
I flashed stock firmware. Everything is fine now.. *sigh*
Now I have to do everything all over again (exp the unlocking)

Can't get windows 10 to detect my Fastboot device

hey guys, I just got my OP3, I want to open the bootloader before I store some data that will be erased anyway when unlocking, I enabled USB Debugging & OEM unlocking & Advanced reboot and then I accepted the RSA Fingerprint popup. (Then, when running adb devices, I got the id of my device).
Now, I am in bootloader mode, and when running fastboot devices, I get nothing. I already installed Oneplus drivers when first connected the device.
In Device Manager under Other Devices I can see a device named "Android". When trying to install the drivers manually by browsing devices I have on my computer, I can only see "Samsung ADB Interface" and I am afraid installing this will not work when trying to unlock the bootloader. What can I do? I also have a Kali Linux Laptop if that's helping. Thanks.
Put in fastboot mode, connect to computer and manually select fastboot interface from the device manager "install device/update driver manually" box. That worked for me.
JusTeN_ said:
hey guys, I just got my OP3, I want to open the bootloader before I store some data that will be erased anyway when unlocking, I enabled USB Debugging & OEM unlocking & Advanced reboot and then I accepted the RSA Fingerprint popup. (Then, when running adb devices, I got the id of my device).
Now, I am in bootloader mode, and when running fastboot devices, I get nothing. I already installed Oneplus drivers when first connected the device.
In Device Manager under Other Devices I can see a device named "Android". When trying to install the drivers manually by browsing devices I have on my computer, I can only see "Samsung ADB Interface" and I am afraid installing this will not work when trying to unlock the bootloader. What can I do? I also have a Kali Linux Laptop if that's helping. Thanks.
Click to expand...
Click to collapse
Its fine just search for fastboot devices and see if your device comes up. Mine was showing the same thing and i continued and it worked

Categories

Resources