WARNING
This process will factory reset your device and wipe the internal memory.
You do this at your own risk. I advise you NOT TO DO THIS as there are risks involved, including, but not limited to, bricking your brand new tablet and renderingit useless. You also may void the warranty. I take NO RESPONSIBILITY for any damage. Again, if you decide to follow these steps, it is entirely at your own risk
Prepare:
If you're a Windows user, you might want to refer here. Chainfire has posted an updated stock ROM which does the unlocking for you. If you're a Linux user, you could try flashing Chainfires image using Heimdall but AFAIK, this has not been tested.
Method 1
Download and install the JAVA SDK from here http://www.oracle.com/technetwork/java/javase/downloads/index.html
Download the Android SDK from here http://developer.android.com/sdk/index.html
Follow the instructions here to download the USB drivers http://developer.android.com/sdk/installing.html
Edit the “<PATH TO ANDROID SDK>\extras\google\usb_driver\android_winusb.inf” file and copy/paste the following lines and add them to the [Google.NTx86] section (for 32bit Windows) and/or [Google.NTamd64] (for 64bit Windows).
Download the fastboot zip attached to this post (includes both Win and Linux version) and extract the files to your "<PATH TO ANDROID SDK>\tools" folder
***Do not leave any blank lines before the first “;”
Code:
;
;Galaxy Tab 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6601
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
Now to get started…
1) Power off your tablet
2) Hold the VOLUME DOWN button and press the POWER button (your tablet will power on and you will see the BACKUP and USB icons)
3) Use VOLUME DOWN to select the USB icon, and then press VOLUME UP to confirm the selection.
4) You should now be in fastboot mode (the word FASTBOOT should appear somewhere in the top left corner)
5) If Windows doesn’t automatically detect the device, go to device manager and find the ‘Fastboot’ device. Right-click and select update driver, choose to manually install and browse to the “<PATH TO ANDROID SDK>\extras\google\usb_driver\” folder.
6) Open a command prompt and do
Code:
cd "<PATH TO SDK FOLDER>\tools"
fastboot devices
7) Confirm that your device is detected. If it says “waiting for device”, you need to check that the drivers are installed correctly.
8) In the Command window, type:
Code:
fastboot oem unlock
9) On your Tab, Use the VOLUME DOWN button to select YES and then press VOLUME UP to confirm
10) VIOLA! You are unlocked. Note that these instructions are a work-in-progress. As always, your questions and comments are welcome. OSX / Linux instructions coming soon!
Linux Instructions (thanks to Draco32)
Get your Tab into fastboot mode;
1) Power off your Tab and power it back on while holding VOLUME DOWN
2) Highlight the USB icon by pressing VOLUME DOWN
3) Press VOLUME UP to confirm your selection (Fastboot Mode)
4) Download the Tegra 2 compatible fastboot (attached to this post) and put it somewhere in your path (eg /usr/bin)
5) Plug your device into the PC using the provided USB cable.
6) Open a terminal and type
Code:
fastboot devices
this will list the device but it will be a strign of numbers
7) type
Code:
fastboot oem unlock
your tab will then have a yes no option to unlock the bootloader select yes with VOLUME DOWN, and press VOLUME UP to confirm
8) Your bootloader is now unlocked power off the device and power it back on the device will boot and have an unlocked padlock when loading. Also this will factory reset your device this includes everything on the 16 gb storage.
Now that you're done head over here to get root access.
EDIT:
ORIGINAL POST:
Guide for unlocking is here:
http://411technology.wordpress.com/
If you power off your device and power it on again using the volume rocker (NOT THE POWER BUTTON), you get the OEM unlock Screen.
Looks like we might have an unlockable bootloader. If so, I love this thing even more now!
Im off to play with it now. Will be back to post pics shortly. Text from the screen is below
Left:
ODIN3 Download Mode
(Protocol v2)
Reason: Force Key
Secure Mode: Secure
Check Signature: Check
OEM Lock: Lock
Waiting USB Cable...
Click to expand...
Click to collapse
Right Hand Side:
Unlock Bootloader?
-------------------------------
If you unlock the bootloader.....
Click to expand...
Click to collapse
(continues on with crap about the risks etc)
Will post pics shortly. Time to break this thing
Fastboot Windows Driver INF File (Galaxy Tab 10.1/v ONLY!)
Code:
;
; Android WinUsb driver installation.
;
[Version]
Signature = "$Windows NT$"
Class = AndroidUsbDeviceClass
ClassGuid = {3F966BD9-FA04-4ec5-991C-D326973B5128}
Provider = %ProviderName%
DriverVer = 12/06/2010,4.0.0000.00000
CatalogFile.NTx86 = androidwinusb86.cat
CatalogFile.NTamd64 = androidwinusba64.cat
;
; This section seems to be required for WinUsb driver installation.
; If this section is removed the installer will report an error
; "Required section not found in INF file".
;
[ClassInstall32]
Addreg = AndroidWinUsbClassReg
[AndroidWinUsbClassReg]
HKR,,,0,%ClassName%
HKR,,Icon,,-1
[Manufacturer]
%ProviderName% = Google, NTx86, NTamd64
[Google.NTx86]
;Galaxy Tab 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6601
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
[Google.NTamd64]
;Galaxy Tab 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6601
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
[USB_Install]
Include = winusb.inf
Needs = WINUSB.NT
[USB_Install.Services]
Include = winusb.inf
AddService = WinUSB,0x00000002,WinUSB_ServiceInstall
[WinUSB_ServiceInstall]
DisplayName = %WinUSB_SvcDesc%
ServiceType = 1
StartType = 3
ErrorControl = 1
ServiceBinary = %12%\WinUSB.sys
[USB_Install.Wdf]
KmdfService = WINUSB, WinUSB_Install
[WinUSB_Install]
KmdfLibraryVersion = 1.9
[USB_Install.HW]
AddReg = Dev_AddReg
[Dev_AddReg]
HKR,,DeviceInterfaceGUIDs,0x10000,"{F72FE0D4-CBCB-407d-8814-9ED673D0DD6B}"
[USB_Install.CoInstallers]
AddReg = CoInstallers_AddReg
CopyFiles = CoInstallers_CopyFiles
[CoInstallers_AddReg]
HKR,,CoInstallers32,0x00010000,"WdfCoInstaller01009.dll,WdfCoInstaller","WinUSBCoInstaller2.dll"
[CoInstallers_CopyFiles]
WinUSBCoInstaller2.dll
WdfCoInstaller01009.dll
[DestinationDirs]
CoInstallers_CopyFiles=11
[SourceDisksNames]
1 = %DISK_NAME%,,,\i386
2 = %DISK_NAME%,,,\amd64
[SourceDisksFiles.x86]
WinUSBCoInstaller2.dll = 1
WdfCoInstaller01009.dll = 1
[SourceDisksFiles.amd64]
WinUSBCoInstaller2.dll = 2
WdfCoInstaller01009.dll = 2
[Strings]
ProviderName = "Google, Inc."
SingleAdbInterface = "Android ADB Interface"
CompositeAdbInterface = "Android Composite ADB Interface"
SingleBootLoaderInterface = "Android Bootloader Interface"
WinUSB_SvcDesc = "Android USB Driver"
DISK_NAME = "Android WinUsb installation disk"
ClassName = "Android Phone"
Correct the title - instead of unlockable should be unlocked.
BTW, what's the advantage?
bcmobile said:
EDIT:
Guide for unlocking is here:
http://411technology.wordpress.com/
If you power off your device and power it on again using the volume rocker (NOT THE POWER BUTTON), you get the OEM unlock Screen.
Click to expand...
Click to collapse
It would appear the SGT 10.1v is another Samsung device with a "3 button recovery" lottery. I have been trying every combo of hardware keys from powered off state on mine and am unable to get the screen you have descibed.
I can however get into a "download mode" (Picture of an android dude doing "road works" and a flashing USB symbol with the word "Downloading") on my device - by pressing the power button and then an instant later pressing the left side of the volume rocker (doesn't seem to work if you press them simultaniously).
Hopefully a smart cookie will figure out a way to put a different firmware in with Odin to enable these options on devices like mine (much like the 3BR fix for the SGS).
Edit - Nevermind, got into it. For me it was Press Power, then an instant later volume left and hold both. When you see a screen with a android dude and a usb symbol - pressing right volume gives you the unlock screen, pressing right volume highlights the USB then pressing right volume to select it puts the device in "fastboot" mode.
Woo hoo!!
myself11 said:
Correct the title - instead of unlockable should be unlocked.
BTW, what's the advantage?
Click to expand...
Click to collapse
Since it is not shipped as unlocked, I actually think unlockable is more appropriate
Advantage is that you can flash unsigned ROMs - no hacks required. This is normally only found on the Nexus handsets so it's a pretty big deal for Devs / hackers.
Hi Guys,
I am unable to get the fastboot drivers working. I can install them correctly. ADB devices appears in device manager but when i type i get nothing back. It's like the fastboot device is not connected?
Do i need a newer version of the SDK?
For some reason SDK manager is not working on my PC at work so i am using an older sdk version.
D:\adbsdkold\android-sdk-windows-1.5_r3\tools>fastboot devices
D:\adbsdkold\android-sdk-windows-1.5_r3\tools>fastboot oem unlock
< waiting for device >
^C
Draco32 said:
Hi Guys,
I am unable to get the fastboot drivers working. I can install them correctly. ADB devices appears in device manager but when i type i get nothing back. It's like the fastboot device is not connected?
Do i need a newer version of the SDK?
For some reason SDK manager is not working on my PC at work so i am using an older sdk version.
D:\adbsdkold\android-sdk-windows-1.5_r3\tools>fastboot devices
D:\adbsdkold\android-sdk-windows-1.5_r3\tools>fastboot oem unlock
< waiting for device >
^C
Click to expand...
Click to collapse
If you look at the response from "fastboot devices" command it cannot see any devices.
Post your anroid_winusb.inf (\android-sdk-windows\extras\google\usb_driveranroid_winusb.inf) may just be entered in wrong section/misspell
Also what state is it in? your device might just not be in fastboot
P.S. update your SDK no reason not to
Android Driver
Hey,
I'm using the Nexus S driver thats probably the issue. It reads like this at present.
Can you upload the Google USB drivers as the SDK doesn't seem to be working for me.
--------------------android_winusb.inf------------------------------------------
;
; Android WinUsb driver installation.
;
[Version]
Signature = "$Windows NT$"
Class = AndroidUsbDeviceClass
ClassGuid = {3F966BD9-FA04-4ec5-991C-D326973B5128}
Provider = %ProviderName%
DriverVer = 12/06/2010,4.0.0000.00000
CatalogFile.NTx86 = androidwinusb86.cat
CatalogFile.NTamd64 = androidwinusba64.cat
;
; This section seems to be required for WinUsb driver installation.
; If this section is removed the installer will report an error
; "Required section not found in INF file".
;
[ClassInstall32]
Addreg = AndroidWinUsbClassReg
[AndroidWinUsbClassReg]
HKR,,,0,%ClassName%
HKR,,Icon,,-1
[Manufacturer]
%ProviderName% = Google, NTx86, NTamd64
[Google.NTx86]
; HTC Dream
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
; HTC Magic
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C03&MI_01
;
;Moto Sholes
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB&MI_01
;
;Google NexusOne
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E22&MI_01
;
;Galaxy Tab 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6601
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
[Google.NTamd64]
; HTC Dream
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
; HTC Magic
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C03&MI_01
;
;Moto Sholes
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB&MI_01
;
;Google NexusOne
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E22&MI_01
[USB_Install]
Include = winusb.inf
Needs = WINUSB.NT
[USB_Install.Services]
Include = winusb.inf
AddService = WinUSB,0x00000002,WinUSB_ServiceInstall
[WinUSB_ServiceInstall]
DisplayName = %WinUSB_SvcDesc%
ServiceType = 1
StartType = 3
ErrorControl = 1
ServiceBinary = %12%\WinUSB.sys
[USB_Install.Wdf]
KmdfService = WINUSB, WinUSB_Install
[WinUSB_Install]
KmdfLibraryVersion = 1.9
[USB_Install.HW]
AddReg = Dev_AddReg
[Dev_AddReg]
HKR,,DeviceInterfaceGUIDs,0x10000,"{F72FE0D4-CBCB-407d-8814-9ED673D0DD6B}"
[USB_Install.CoInstallers]
AddReg = CoInstallers_AddReg
CopyFiles = CoInstallers_CopyFiles
[CoInstallers_AddReg]
HKR,,CoInstallers32,0x00010000,"WdfCoInstaller01009.dll,WdfCoInstaller","WinUSBCoInstaller2.dll"
[CoInstallers_CopyFiles]
WinUSBCoInstaller2.dll
WdfCoInstaller01009.dll
[DestinationDirs]
CoInstallers_CopyFiles=11
[SourceDisksNames]
1 = %DISK_NAME%,,,\i386
2 = %DISK_NAME%,,,\amd64
[SourceDisksFiles.x86]
WinUSBCoInstaller2.dll = 1
WdfCoInstaller01009.dll = 1
[SourceDisksFiles.amd64]
WinUSBCoInstaller2.dll = 2
WdfCoInstaller01009.dll = 2
[Strings]
ProviderName = "Google, Inc."
SingleAdbInterface = "Android ADB Interface"
CompositeAdbInterface = "Android Composite ADB Interface"
SingleBootLoaderInterface = "Android Bootloader Interface"
WinUSB_SvcDesc = "Android USB Driver"
DISK_NAME = "Android WinUsb installation disk"
ClassName = "Android Phone"
Yer that looks correct for a 32bit-OS but if your running 64bit-OS put it under "Google.NTamd64"
Also make sure you follow the guide bcmobile post to the letter to get into fastboot
Power off your tablet
Press the VOLUME DOWN button (your tablet will power on and you will see the BACKUP and USB icons)
Use VOLUME UP to select the USB icon, and then press VOLUME DOWN to select it.
You should now be in fastboot mode (the word FASTBOOT should appear somewhere in the top left corner)
If your computer doesn't automatically detect the device, go to device manager and find the 'Fastboot' device. Right-click and select update driver, choose to manually install and browse to the "C:\android-sdk-windows\extras\google\usb_driver\" folder.
Click to expand...
Click to collapse
50-3 said:
Yer that looks correct for a 32bit-OS but if your running 64bit-OS put it under "Google.NTamd64"
Also make sure you follow the guide bcmobile post to the letter to get into fastboot
Click to expand...
Click to collapse
Followed the guide correctly i have fast boot coming up on the tablet just no devices are shown when i do fast boot devices i will have a look when i get home.
Also the part of the guide where it says Volume Up to move it over to the USB icon is incorrect. It's actually Volume Down to move to the USB icon when selecting the fastboot option.
Cheers,
Adrian
Draco32 said:
Followed the guide correctly i have fast boot coming up on the tablet just no devices are shown when i do fast boot devices i will have a look when i get home.
Also the part of the guide where it says Volume Up to move it over to the USB icon is incorrect. It's actually Volume Down to move to the USB icon when selecting the fastboot option.
Cheers,
Adrian
Click to expand...
Click to collapse
Well if you have the right driver file config and in fastboot only thing left i can think of is that windows hasn't been told to use the driver
If your computer doesn't automatically detect the device, go to device manager and find the 'Fastboot' device. Right-click and select update driver, choose to manually install and browse to the "C:\android-sdk-windows\extras\google\usb_driver\" folder.
Click to expand...
Click to collapse
Or it's an old version of SDK tools but i do think that is it.
Anyway sorry i couldn't have been more help
Draco32 said:
Followed the guide correctly i have fast boot coming up on the tablet just no devices are shown when i do fast boot devices i will have a look when i get home.
Also the part of the guide where it says Volume Up to move it over to the USB icon is incorrect. It's actually Volume Down to move to the USB icon when selecting the fastboot option.
Cheers,
Adrian
Click to expand...
Click to collapse
Go into device manager and find the fastboot device. Right click and uninstall it. Unplug the tab and Reboot your PC. Put your tab into fastboot mode before reconnecting
Thanks for pointing out the vol up / down error. I had the old galaxy tab which had them the other way around since it was designed to be used in portrait mode. Ill correct it in the guide later tonight.
Sent from my GT-P7100 using XDA Premium App
bcmobile said:
Advantage is that you can flash unsigned ROMs - no hacks required. This is normally only found on the Nexus handsets so it's a pretty big deal for Devs / hackers.
Click to expand...
Click to collapse
Noob question: but we will still need devs that cook ROM's, right? It isn't as simple as grab Google's update and install it on 10.1v, is it?
myself11 said:
Noob question: but we will still need devs that cook ROM's, right? It isn't as simple as grab Google's update and install it on 10.1v, is it?
Click to expand...
Click to collapse
Unfortunately no, But if were lucky the Devs will push them out quickly
Hi Everyone,
Just to let you know i managed to unlock the bootloader. I used ubuntu linux and fastboot method to get it unlocked.
Get your Tab into fastboot mode;
1. Power + Volume Down
2. Highlight the USB icon by pressing Volume Down
3. Press Volume Up to select the USB icon (Fastboot Mode)
Download the Tegra 2 compatible fastboot from this threadhttp://forum.xda-developers.com/showthread.php?t=1055754;
1. Plug your device into the PC using the provided USB cable.
2. open a terminal and type fastboot devices this will list the device but it will be a strign of numbers
3. type "fastboot oem unlock" your tab will then have a yes no option to unlock the bootloader select yes with Volume Up
5. Your bootloader is now unlocked power off the device and power it back on the device will boot and have an unlocked padlock when loading. Also this will factory reset your device this includes everything on the 16 gb storage.
Cheers,
Draco
A little off-topic, but didn't want to open a new topic: is australian radio version different from european version?
Draco32 said:
Hi Everyone,
...
5. Your bootloader is now unlocked power off the device and power it back on the device will boot and have an unlocked padlock when loading. Also this will factory reset your device this includes everything on the 16 gb storage.
Click to expand...
Click to collapse
Hi everybody,
I received my 10.1v yesterday (Vodafone, Germany) and have noticed that it allready boots with an unlocked padlock. Does this mean that I have an allready unlocked Tab? This is strange ...
smack said:
Hi everybody,
I received my 10.1v yesterday (Vodafone, Germany) and have noticed that it allready boots with an unlocked padlock. Does this mean that I have an allready unlocked Tab? This is strange ...
Click to expand...
Click to collapse
Cool!
Yes that should mean it's unlocked. Apparently the 10.1 is shipping unlocked as well so I guess I shouldn't be surprised.
If you want to be sure, go into fastboot mode using steps 1-4 above and it should say:
Lock State: UNLOCKED
...on the fastboot screen
unlucky, if I Hold the VOLUME DOWN button and press the POWER button , the tablet goes to the normal UI, I cannot understand.......
I did not see anything about BACKUP and USB icons
For those who are having diffficulties unlocking the bootloader, follow all steps mentioned in the guide, and then enter the device in USB mode but don't plug it to the pc.
Open the cmd and type:
cd "<PATH TO SDK FOLDER>\tools"
fastboot devices
fastboot oem unlock (and it will appear a notification saying waiting for device)
Only nows, in USB mode, plug the tab to the PC.
After that choose in the tab "yes" and your bootloader is unlocked.
Hope this could help!
The GPS is not starting up, tried everything. Flashing new GPS configuration, Cleaning GPS data with angry GPS, Booting, reebooting.
i9000 running CM7 7.1.0 Stable
It started after following this Post
http://forum.xda-developers.com/showthread.php?t=1182735
-GPS Antenna is on
-The gps notification used to blink while trying to fix a position, now it doesn't even show up.
Please Help
Part of a alogcat file where the same error keeps repeating itself while the antenna is on.
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
Can anyone give me a hint please?
biomanuel666 said:
The GPS is not starting up, tried everything. Flashing new GPS configuration, Cleaning GPS data with angry GPS, Booting, reebooting.
i9000 running CM7 7.1.0 Stable
It started after following this Post
http://forum.xda-developers.com/showthread.php?t=1182735
-GPS Antenna is on
-The gps notification used to blink while trying to fix a position, now it doesn't even show up.
Please Help
Part of a alogcat file where the same error keeps repeating itself while the antenna is on.
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
I/GPS ( 191): [gps_state_done][line = 293] : successfully called
E/GPS ( 191): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(errno = 2)
Click to expand...
Click to collapse
Please help me out with this!
GPS no longer working
You have a GT-I9000, yet you have sought the answer to your problem on a Vibrant thread. Did you, by any chance, install CM7 for the Vibrant onto your GT-I9000, find a problem with the GPS, and look for the answer within the Vibrant thread?
If you could supply a little more background information, then this would be helpful.