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!
New universal method of rooted for the Optimus 2x
After much programming and experimenting with another great part, already I can deliver my latest work.
So far have only made for Linux and Mac. (there are methods to not be as done in CMD)
Apparently it seems very simple, but it cheats, it is quite complex, since I've programmed detection of errors and possible solutions to the problems of communication.
The program is smart, detects the operating system that we are using, Linux or iOS, and detects the version of ROM installed to determine installation done.
Also installs the CWM Recovery, and also knows which install depending on the GB ROM or ICS, all automatic, without having to think that option used.
Before you root it will ask you if the CWM Recovery is installed and if it is not you can do it at that time.
The method used is not new, I already used it in earlier versions of GB, the difference with the other methods is that you don't have to copy anything to the SD and things of these, simple and clean installation.
Well I hope that you have Linux or a Mac can root without having to boot the "tedious" Windows.
CHANGELOG
V-0.5
-Implemented detecting permissions
-Implemented detection system 32/64b
-Fixed bug, was not working in Ubuntu 11.04 and higher
V-0.4
-Detection of new possible connection failures.
-Detection of errors in routines Android
-Optimized routines
V-0.3
-Fixed bug of execution, did not work on some current versions of Ubuntu and derivatives
-New start menu.
-New header
V-0.2
-Re-raise with correction error in English language, it only pulled in Spanish
-Includes English language
-Changing the graphic appearance
V-0.1
-Only in Spanish
Click to expand...
Click to collapse
DOWNLOAD
Toolkit_ICS-Root_Stock-v-0.5_LINUX-MAC_by_Homero.rar - 13.40 MB
Thank's Man...and have a nice year 2013!!!...
Nice, it should became sticked.
Also... your program must be also noob-proof
Great work, homero! Thank you.
Sent from my LG-P990 using xda app-developers app
Homero again back with a bang...you're hulk of lg optimus forum..you rock bro
Finally some Linux love.... :thumbup:
Sent from my LG-P990 using xda app-developers app
Thanks homero
Enviado desde mi O2X
I have committed an error, and the English version, and does not run.
You can download the new corrected version or edit and modify.
Edit the root file and look for this line:
Code:
if [ "$ANSWER" = 1 ]; then
tools/es.sh
elif [ "$ANSWER" = 2 ]; then
tools/es.sh
elif [ "$ANSWER" = "x" ] || [ "$ANSWER" = "X" ]; then
Changing this:
Code:
elif [ "$ANSWER" = 2 ]; then
tools/es.sh
why another:
Code:
elif [ "$ANSWER" = 2 ]; then
tools/en.sh
Save and ready, already operates the English version
Homero2 said:
I have committed an error, and the English version, and does not run.
You can download the new corrected version or edit and modify.
Edit the root file and look for this line:
Code:
if [ "$ANSWER" = 1 ]; then
tools/es.sh
elif [ "$ANSWER" = 2 ]; then
tools/es.sh
elif [ "$ANSWER" = "x" ] || [ "$ANSWER" = "X" ]; then
Changing this:
Code:
elif [ "$ANSWER" = 2 ]; then
tools/es.sh
why another:
Code:
elif [ "$ANSWER" = 2 ]; then
tools/en.sh
Save and ready, already operates the English version
Click to expand...
Click to collapse
Beware of #!/bin/sh ... read -n command is bash command, and it does not work well in /bin/sh ...
Confirmed on NetRunner (kubuntu 12.10 ).
You should use #!/bin/bash. That applies to all *.sh scripts.
asmerito said:
Beware of #!/bin/sh ... read -n command is bash command, and it does not work well in /bin/sh ...
Confirmed on NetRunner (kubuntu 12.10 ).
You should use #!/bin/bash. That applies to all *.sh scripts.
Click to expand...
Click to collapse
OK, that is the answer that was waiting, since neither worked in Ubuntu 12.04
EDIT:
Re-raise corrected v-0.3
Though your tool says that flashing the recovery worked successful, I can't boot into recovery. When pushing vol- and power I'm just stuck at the pink LG logo (it's in a boot loop while holding vol- and power). Since the system is not rooted, yet, I also cannot boot into recovery with the CWM app.
thorstenhirsch said:
Though your tool says that flashing the recovery worked successful, I can't boot into recovery. When pushing vol- and power I'm just stuck at the pink LG logo (it's in a boot loop while holding vol- and power). Since the system is not rooted, yet, I also cannot boot into recovery with the CWM app.
Click to expand...
Click to collapse
Don't worry in excess, can be retrieved very easily, but before answer to these questions.
Android version?
did CWM previously installed?.
Terminal type? (P990, P990, etc.)
on slackware 14.0, expanded in /opt:
two patches applied;
files are executables with right permissions;
dir 'tools' is accessible;
lg2x is connected via USB (on, off, MTP, PC Suite, without battery and vol -, ...?)
but same result
Terminal: P990 (EU)
ROM: ICS stock
Previous ver: CM 7.2 stable
Previous CWM: 5.0.2
Homero2 said:
Android version?
did CWM previously installed?.
Terminal type? (P990, P990, etc.)
Click to expand...
Click to collapse
Android 4.0.4 (official V30A)
CWM - well, under GB layout I could install it (I was on CWM5 first and later switched to CWM6), but this was my first try on ICS layout
Terminal type - you mean the shell? I'm using Ubuntu 12.10, so /bin/sh did not work and I replaced all /bin/sh with /bin/bash, that means I was running bash when I "bricked" my phone.
kanzy said:
on slackware 14.0, expanded in /opt:
two patches applied;
files are executables with right permissions;
dir 'tools' is accessible;
lg2x is connected via USB (on, off, MTP, PC Suite, without battery and vol -, ...?)
but same result
Terminal: P990 (EU)
ROM: ICS stock
Previous ver: CM 7.2 stable
Previous CWM: 5.0.2
Click to expand...
Click to collapse
Is about understands that this method of single rooted is for Stock ROM versions.
Clarified the issue, I see errors jump to run ADB.
Try with the latest version that I uploaded, the V-0.4
thorstenhirsch said:
Android 4.0.4 (official V30A)
CWM - well, under GB layout I could install it (I was on CWM5 first and later switched to CWM6), but this was my first try on ICS layout
Terminal type - you mean the shell? I'm using Ubuntu 12.10, so /bin/sh did not work and I replaced all /bin/sh with /bin/bash, that means I was running bash when I "bricked" my phone.
Click to expand...
Click to collapse
Not be what could happen...
Doing tests I found that if you are in Recovery, and the SYSTEM partition is not mounted, the program cannot determine partition type should be used.
That error is already fixed in the V-0.4.
It can reflash the Recovery with one of the many versions that we have in the Forum, one in Flash only recovery or All in one.
I say this because it is the only thing that could have happened, since the rooted is not harmful, only copy two files in the system.
Using V-0.4, and it does not work...
Homero2 said:
Is about understands that this method of single rooted is for Stock ROM versions.
Clarified the issue, I see errors jump to run ADB.
Try with the latest version that I uploaded, the V-0.4
Not be what could happen...
Doing tests I found that if you are in Recovery, and the SYSTEM partition is not mounted, the program cannot determine partition type should be used.
That error is already fixed in the V-0.4.
It can reflash the Recovery with one of the many versions that we have in the Forum, one in Flash only recovery or All in one.
I say this because it is the only thing that could have happened, since the rooted is not harmful, only copy two files in the system.
Click to expand...
Click to collapse
Same problem as on slackware, got booloop after flashing recovery. Cannot enter recovery
After this step:
INSTRUCTIONS
CWM will be installed for version ICS V-4.0.4 of Android
Nvflash started
rcm version 0X20001_____________________________________________________________
System Information:
chip name: unknownh Recovery CWM
chip id: 0x20 major: 1 minor: 4
chip sku: 0xf
chip uid: 0x045070c04120b4d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: tools/fastboot.bin
/ 1027184/1027184 bytes sent
tools/fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: tools/recovery_cwm-6_ics_opti.img
\ 7145472/7145472 bytes sent
tools/recovery_cwm-6_ics_opti.img sent successfully
everything went wrong, and my stock ICS got bootloop.
Using Kubuntu 12.10, stock ICS and V-0.4 of your tool.
Thank you mate! Gonna share it like a bee
asmerito said:
Same problem as on slackware, got booloop after flashing recovery. Cannot enter recovery
...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=921169
Fixed bug, now works in Ubuntu 11.04, 11.10, 12.04 and 12.10
An error has been detected by Jonki, Thank you!!
Homero2 said:
Fixed bug, now works in Ubuntu 11.04, 11.10, 12.04 and 12.10
An error has been detected by Jonki, Thank you!!
Click to expand...
Click to collapse
What was the problem?