Second time Ive gotten stuck in this whole process, man I dont get why no one else seems to be having trouble but myself Worked on this part for at least 40 minutes before posting, will continue while I wait for response.
This part of the instruction:
14. Go to the directory where you downloaded your bootloader unlock key.
15. Enter "fastboot flash unlock unlock.bin" in DOS command window.
“unlock.bin” is the bootloader unlock key you received in the email.
I feel like I must be missing somthing here, because I dont understand why Im bothering to "go to the directory wherer the unlock key is" if Im just going to be entering a command in the dos window. It's not like im browsing to it then adding it, then opening it in a piece of software or whatever....
Either way, just copy pasting "fastboot flash unlock unlock.bin" (without quotations) I get an error "cannot load "unlock.bin"
Using Minimal adb as cmd, this is correct right?
"Edit" Update:
Should I be using adb.exe instead of minimal adb? No need in explaining every step that led to this, but I have this folder now in my c drive (https://gyazo.com/703ba598851878527d817c8ff68ae11b) I've tried running adb.exe as admin, even not as admin, and the command window just flashes up quickly and disappears. This makes more sense to me even though it's not working for some reason.
Thanks
Copy that unlock.bin file to the same folder where your fastboot files are. The same folder where you are right-clicking to create the command window.
Your TWRP file should also be in that same folder (for later).
It's going to look for files in that folder that you are telling it to "flash". If it can't find the file, it can't flash that file.
The instructions are written poorly. I knew what to do, based on past experience.
Sent from my official open market LG US998 V30+
ChazzMatt said:
Copy that unlock.bin file to the same folder where your fastboot files are. The same folder where you are right-clicking to create the command window.
Your TWRP file should also be in that same folder (for later).
It's going to look for files in that folder that you are telling it to "flash". If it can't find the file, it can't flash that file.
The instructions are written poorly. I knew what to do, based on past experience.
Sent from my official open market LG US998 V30+
Click to expand...
Click to collapse
Alright, so youre saying the unlock.bin folder goes into the folder in my screenshot, with the 4 files in it correct? If so, shift right click open cmd window is the only way to bring up the right cmd window in order to unlock the bootloader? If so, is that option default on your pc? I don't have the right click open command window option available. I read into that, it have the impression it was disabled at some point, the task of restoring the option seemed somewhat arduous, at least according to a couple of the walthrough's I read. Are you aware of a simpler method of making this option available?
thanks so much Chazz for youre reply, I was really looking forward to doing this today and this small step has roadblocked me for hours at this point, really appreciate it man
breacherman said:
Alright, so youre saying the unlock.bin folder goes into the folder in my screenshot, with the 4 files in it correct? If so, shift right click open cmd window is the only way to bring up the right cmd window in order to unlock the bootloader? If so, is that option default on your pc? I don't have the right click open command window option available. I read into that, it have the impression it was disabled at some point, the task of restoring the option seemed somewhat arduous, at least according to a couple of the walthrough's I read. Are you aware of a simpler method of making this option available?
thanks so much Chazz for youre reply, I was really looking forward to doing this today and this small step has roadblocked me for hours at this point, really appreciate it man
Click to expand...
Click to collapse
In that folder with your fastboot files, you hold the keyboard "shift" key down, while simultaneously right clicking (in an empty space) with your mouse. In that right click menu should be an option to open a command window. You would click on that option.
Sent from my official open market LG US998 V30+
Powershell, it's powershell. I knew that was a command window, why was I missing it, I'm sure it was there the whole time. Thanks Chazz, looks like I'm gtg.
breacherman said:
Second time Ive gotten stuck in this whole process, man I dont get why no one else seems to be having trouble but myself Worked on this part for at least 40 minutes before posting, will continue while I wait for response.
This part of the instruction:
14. Go to the directory where you downloaded your bootloader unlock key.
15. Enter "fastboot flash unlock unlock.bin" in DOS command window.
“unlock.bin” is the bootloader unlock key you received in the email.
I feel like I must be missing somthing here, because I dont understand why Im bothering to "go to the directory wherer the unlock key is" if Im just going to be entering a command in the dos window. It's not like im browsing to it then adding it, then opening it in a piece of software or whatever....
Either way, just copy pasting "fastboot flash unlock unlock.bin" (without quotations) I get an error "cannot load "unlock.bin"
Using Minimal adb as cmd, this is correct right?
"Edit" Update:
Should I be using adb.exe instead of minimal adb? No need in explaining every step that led to this, but I have this folder now in my c drive (https://gyazo.com/703ba598851878527d817c8ff68ae11b) I've tried running adb.exe as admin, even not as admin, and the command window just flashes up quickly and disappears. This makes more sense to me even though it's not working for some reason.
Thanks
Click to expand...
Click to collapse
how to relock it please ?
octopus82 said:
how to relock it please ?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For G6 but should be the same for LG V30.
https://www.androidexplained.com/lg-g6-lock-bootloader/
Related
When unlocking my BL do I use RSD Lite and fastboot or just RSD Lite? And if only RSD Lite does this sbf (ATT-2.3.4_Pudding_preroot)cover me if Im currently on 2.3.4 OTA and completely stock? Thanks!
Really, that many responses huh?
Sent from my MB860 using XDA App
http://forum.xda-developers.com/showthread.php?t=1154600
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
I have personally answered this questions at least 4 times.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Instructions
1. If you’re on Gingerbread, skip to step 13. 2. Power down your Motorola Atrix 3. Take out your microSD card and SIM card for the flashing process 4. While turning the phone on, hold the Volume Up button until it acknowledges RSD 5. Your device will say “Starting RSD protocol support” 6. Run “RSD Lite” on your computer 7. Press the “. . .” button next to the box labeled “Filename” 8. Load up the SBF file The SBF file is located inside of the .zip file, you must extract it out before loading it into RSD Lite Use WinRAR or 7-Zip to extract the .zip file on your computer 9. Plug your device into your computer Use the USB ports on theback side of your computer for safety 10. RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…” 11. Press the “Start” button 12. Be patient while the phone reboots. It will take a long time. 13. Open and extract the Fastboot package from above 14. Open a command prompt window On Windows, press Start and type “cmd” then press the enter button 15. Type the following command. Your directory will be the folder where you extracted the Fastboot package. (Example: cd C:\Users\Kenneth\Desktop\fastboot-package)
cd your directory here 16. Power down your Atrix device 17. Hold the power button and the downward volume button until you see “Fastboot” 18. Let go of the buttons and press the upward volume button once 19. You will now see “Starting Fastboot protocol support” 20. Plug your device into a USB port in the back slot of your computer Front slots sometimes do not have enough power to stay connected to the device. 21. Type the following command: fastboot oem unlock 22. You will now receive a warning along with a unique device ID 23. Type the following commands using your unique device ID in place of the ####: fastboot oem unlock #### fastboot reboot 24. Wait for your device to reboot. Congratulations! You now have an unlocked bootloader! from my MB860 using XDA App
I appreciate it but does being on gingerbread mean I've rooted already using a gingerbread sbf and I now move on to step 13 to unlock the bl? If so that means I need to start at 1. But if the 2.3.4 sbf I flash has root installed then do I stop at 12?
These posts don't answer these questions and that is the only reason I posted...
Two things:
1. Don't skip steps no matter which version you are on 2.2.2 or 2.3.4, you start at step#1 and do all steps up to the very last step. (Original instructions were written with assumption that 2.3.4 comes with unlocked BL already, but it didn't, so don't skip steps).
2. Steps 21 through 23 will have to be done twice. After first time you will get a "failed to boot" and a soft brick (normal behavior for 2.3.4 roms). Go back into fastboot and repeat the fastboot unlock steps, and all should be fine.
I'm glad what I tried already didnt work then because I had skipped to 13 due to the fact I'm on 2.3.4.
When I was starting the command prompt though and entered in the "cd C:\Temp etc..." It kept saying the path couldn't be found and that's where I extracted fast boot to...? If I run steps 1-12 will then find it automatically using the same cd prompt?
Thanks
Sent from my MB860 using XDA App
supermerkin said:
I'm glad what I tried already didnt work then because I had skipped to 13 due to the fact I'm on 2.3.4.
When I was starting the command prompt though and entered in the "cd C:\Temp etc..." It kept saying the path couldn't be found and that's where I extracted fast boot to...? If I run steps 1-12 will then find it automatically using the same cd prompt?
Thanks
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Download the fastboot package linked in prerequisites of that article.
Extract it to the root of C: drive.
To start a command prompt in that folder, go to C:/fastboot, right click while holding "shift" inside this folder and select "open command prompt here".
I will do just that, and thank you for the help.
EDIT: I dont know if you saw that this was the .sbf I plan on flashing with rsdlite. It says it has unlock built in, will it hurt the phone to flash this with rsd and then go into fastboot?
http://api.viglink.com/api/click?fo...m/C0I82IXH7V&jsonp=vglnk_jsonp_13149735232651 - 2.3.4 full sbf with unlocker and /preinstall root
Sent from my MB860 using XDA App
That file is a full sbf, it includes an unlockable bootloader AND root in /preinstall. You still have to go thru the step to unlock, and move the su binary from /preinstall to /system/bin
supermerkin said:
I will do just that, and thank you for the help.
EDIT: I dont know if you saw that this was the .sbf I plan on flashing with rsdlite. It says it has unlock built in, will it hurt the phone to flash this with rsd and then go into fastboot?
http://api.viglink.com/api/click?fo...m/C0I82IXH7V&jsonp=vglnk_jsonp_13149735232651 - 2.3.4 full sbf with unlocker and /preinstall root
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Did you get a new SGS II? And you want it rooted, but without loosing your factory warranty, or even getting the yellow triangle? Then you're lucky if you are reading this post. All you need, is a few things.
First you need a computer(which is pretty obvious, isn't it?)
Preferably a windows computer, but I can help you, if you've got a mac, aswell.
So, now you've made sure, that you've got these things, let's carry on with the tutorial...
You need Kies (which you use to transfer files, and contacts, to/from your computer and back...) and the android SDK*. If you haven't got these programs, then click on the links below...
Go to: developer.android.com/sdk/index.html (<-Download the SDK.zip)
Just extract the ZIP to your desktop, what you'll need will come in a second...
Now, for all you windows users;
Once you have extracted the SDK_zip to the desktop(or where ever you want to) click on sdk manager.exe, and download everything from google, and download the sdk-tools for your Android version (eg. 2.2, 2.3.x or 4.0.x) once you have downloaded all these tools, close the SDK* manager, and open the folder "Platform-Tools" in here, you wil find some files called "ADB", and two other files, called WinApi. Take these, and copy these into C:\Windows\System32\
Once you have done this, we can carry on...
(On your keyboard) press (and hold) Windows + R. Once the Run dialog has opened, you can release the keys.
Type in the Textbox cmd.exe and hit enter. In the command prompt (cmd) type in this command. "Adb" if some text appears, you have correctly installed ADB* on to your computer. You can now plug your SGS II in, and wait fir windows to determine the device and start installing additional drivers. Make sure you have set your device to allow USB debugging! (Now you can drink a cuppa coffee, and wait for about 5 minutes.)
Once this has been done, type in (in cmd) this command: adb devices And hit enter. If a set of numbers and letters appear(in hexadecimal order) and the word "Device" is written behind the hexadecimal* code, then you are ready to root!
Now for the rooting, itself. (If you want permanent root, skip this part, if you just want temporary root-permissions, then read this.)
First( to make sure that, if you break something in the OS*-Partition, you can repair your device(without flashing) type in the backup command: adb backup C:\MyAndroidBackup.ab -apk -system -shared -all
Check your phone, this is needed,incase you are prompted for permission. Once the backup is done, type in the following command, to gain root access.
Type in the command prompt-window " adb root"
Now, for permanent root access;
Type in the command prompt-window: adb backup -apk -system -shared -all
Check your phone, to see if you are prompted for permission... Wait for the backup to finish. Once it is done, type in the following command, to set your phone, into a type of "Download mode": adb remount
Now, you need to download the files beneath... (Superuser and BusyBox)
Download these files to your C Drive. Now, type in this command,: adb push C:\Superuser-1.apk /system/app
And again: adb push C:\stericson.busybox.apk system/app
Once you have done this, you should be able to use them, after one reboot. So, we will do a quick reboot. This installs the applications, and gets you one step further to being a "legal" root user! To do a reboot, type in: adb reboot
After your device has rebooted, and is ready-to-use, go to your app-drawer, and look for the apps: "Super User" and "BusyBox installer". If you have found these, then you have done the first steps correctly!
Now, type in the Command-Prompt Window: adb devices. And it should say the same hexadecimal code, with the caption "Device" next to it. If it says this, then type in the final command, to gain root access.: adb root
Once you have typed in the command above, you are an official root user!
I do not take responsibility if you break your device! I would gladly help you, but don't make me responsible. And just because I'm new here doesn't mean I'm completely new to android development/ rooting etc. .
If you found, that my tutorial was good, then please thanks me. If you have any ~questions, then please ask! If you have concerns, please let me know! Screenshots and video tutorial are following. I'm still looking for a way to do this on a mac, and I have yet only found one way. But we'll get to that in another thread, once I've proven it's effectiveness. Have a nice day, and have fun rooting!
P.S This works on nearly every android device!
Edit: P.S I forgot to mention =, what the stared words mean. SDK: Software Development Kit
ADB: Android Debugging Bridge
Hexadecimal: A string of combined letters and numbers.
Man u rock
But contact a mod and mave this to development section+ur bootloadter patch one...
familyguy59 said:
type in the following command, to gain root access.
Type in the command prompt-window " adb root"
Click to expand...
Click to collapse
I'm speechless.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sahibunlimited said:
Man u rock
But contact a mod and mave this to development section+ur bootloadter patch one...
Click to expand...
Click to collapse
Will do (at some time) but now, I've got get on developing my own Kernel. Which will make all this much easier!
familyguy59 said:
First( to make sure that, if you break something in the OS*-Partition, you can repair your device(without flashing) type in the backup command: adb backup C:\MyAndroidBackup.ab -apk -system -shared -all
Check your phone, this is needed,incase you are prompted for permission. Once the backup is done, type in the following command, to gain root access.
Type in the command prompt-window " adb root"
Click to expand...
Click to collapse
familyguy59,
I'm not sure what you're trying to do here, but "adb backup" requires ICS so, that and the fact this thread is redundant, I'm closing it.
Thanks
crachel
hi guys....today i rooted my moto e with the help of this site.....after rooting was completed my phone showed warning bootloader unlocked but after it started i checked with root checker app and it shows my phone is not rooted....so i tried to repeat steps of rooting........but when i type command "fastboot oem unlock 'unique key'" it says that my device is already unlocked......i dont know what to do now to root it properly......pls help....thnx in advance
i only did these six steps.....
1.) Put your device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
2.)Open Command Prompt on androidsdk/platform-tools/ (Hold Shift and right click and press open command window here)
Connect your Phone to PC
3.)Type this in the CMD prompt window - fastboot oem get_unlock_data
You will get a return string. Copy it. [Right Click-Mark- Mark the text by pressing the shift key-Now press Ctrl+C]
Paste all the lines together in a notepad. Remove the empty spaces.
4.)Now go to the Motorola Site.Sign in using your Google account or Motorola ID. Scroll down the page and paste the copied string in the field at step #6. Then click on ‘Can my device be unlocked?’, after which a "REQUEST UNLOCK KEY" button will appear at the bottom of page. To get your unlock key, select the ‘I Agree’ option. Note: You will receive an email with your Unlock Key at the email address you used to log in there. Important – Copy the 20-character key that Motorola sent you via email. Make sure your device is connected.
5.)Then in CMD type: fastboot devices (To check your device is connected)
6.)Then type: fastboot oem unlock UNIQUE_KEY
......do i have to do something more...like sumthing i saw on video on twrp flash
smarty007us said:
hi guys....today i rooted my moto e with the help of this site.....after rooting was completed my phone showed warning bootloader unlocked but after it started i checked with root checker app and it shows my phone is not rooted....so i tried to repeat steps of rooting........but when i type command "fastboot oem unlock 'unique key'" it says that my device is already unlocked......i dont know what to do now to root it properly......pls help....thnx in advance
i only did these six steps.....
1.) Put your device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
2.)Open Command Prompt on androidsdk/platform-tools/ (Hold Shift and right click and press open command window here)
Connect your Phone to PC
3.)Type this in the CMD prompt window - fastboot oem get_unlock_data
You will get a return string. Copy it. [Right Click-Mark- Mark the text by pressing the shift key-Now press Ctrl+C]
Paste all the lines together in a notepad. Remove the empty spaces.
4.)Now go to the Motorola Site.Sign in using your Google account or Motorola ID. Scroll down the page and paste the copied string in the field at step #6. Then click on ‘Can my device be unlocked?’, after which a "REQUEST UNLOCK KEY" button will appear at the bottom of page. To get your unlock key, select the ‘I Agree’ option. Note: You will receive an email with your Unlock Key at the email address you used to log in there. Important – Copy the 20-character key that Motorola sent you via email. Make sure your device is connected.
5.)Then in CMD type: fastboot devices (To check your device is connected)
6.)Then type: fastboot oem unlock UNIQUE_KEY
......do i have to do something more...like sumthing i saw on video on twrp flash
Click to expand...
Click to collapse
What you did is for unlocking bootloader see this for rooting : http://forum.xda-developers.com/showthread.php?t=2755336
iTudorS said:
What you did is for unlocking bootloader see this for rooting : http://forum.xda-developers.com/showthread.php?t=2755336
Click to expand...
Click to collapse
Super thnx man.... onw more thing what folder is "root of my internal memory?"
smarty007us said:
Super thnx man.... onw more thing what folder is "root of my internal memory?"
Click to expand...
Click to collapse
This one, the explorer wich I'm using is miXplorer.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok, Phone is rooted, running TWRP recovery. I want to go back to stock. I have been reading about RUU and seems simple enough. I downloaded the most recent RUU 4.28 I believe. Now I need to relock the bootloader. I am S-On. I have seen threads saying I have to run a simple command and it will relock the boot loader but when it comes to command prompt on a computer I am clueless.
First do I have the phone plugged in first before running the prompt?
Do I then have to open the command prompt or do I run a program that will open it.?
What is the prompt I need to type in?
It was my understanding I have to open the command prompt with the fastboot.exe that I downloaded when I went to unlock the phone originally. When I go back to that file on my computer though I get an error...
"The program can't start because the file AdpWinApi.dll is missing from your computer"
What Do I have to do to get around this and be able to open the command prompt to relock my bootloader and flash the 4.28 RUU so that I return my phone to stock (I know it isn't technically complete stock) and get back my ability to do the OTA Updates.
Thanks.
magicbumm328 said:
I am S-On. I have seen threads saying I have to run a simple command and it will relock the boot loader but when it comes to command prompt on a computer I am clueless.
First do I have the phone plugged in first before running the prompt?
Do I then have to open the command prompt or do I run a program that will open it.?
What is the prompt I need to type in?
It was my understanding I have to open the command prompt with the fastboot.exe that I downloaded when I went to unlock the phone originally. When I go back to that file on my computer though I get an error...
Click to expand...
Click to collapse
The phone needs to be connected before running the command. Connect the phone, and reboot into bootloader. It by default (when connected to PC) should indicate FASTBOOT (highlighted in red) on the bootloader screen (and that is the mode it needs to be in, to execute fastboot commands).
Then you will execute the command via the command prompt. Do not try to execute (click on) the fastboot.exe. Its not a exe program you manually run, but something that runs in the background when you enter the command in command prompt.
To do the fastboot command in command prompt, open Command Prompt, then you will need to change directory to wherever the fastboot.exe is located. I don't know where you put it, so I can't tell you the command specifically. But in general, you will probably need to enter:
cd \
(this command brings you back to the root directory of the "C" drive, as the default is usually your user directory)
And then change drive (cd) to the folder where fastboot.exe is located. For example, I will often copy it to the root directory of the "C" drive, in a folder called "Android SDK" to make this path pretty simple. If you do the same (copy to an easier location) make sure you copy all the contents of that folder, not just fastboot.exe. For my "simple" example, the cd path is:
cd Android SDK
But if you have folders within folders (to navigate to where fastboot.exe is located) you need to indicate the path using the "" character between folders:
cd folder1\folder2\Android SDK
After you have entered the path correctly, it should show up in the command prompt: C:\folder1\folder2\Android SDK
Once you have changed directory properly to whatever folder contains fastboot.exe, simply type the command:
fastboot oem lock
After the phone reboots, go into bootloader, and you should see RELOCKED near the top of the screen. Which means you were successful.
If you are still getting the dll error when properly executing the fastboot command, let me know and we will install a new adb/fastboot package.
redpoint73 said:
The phone needs to be connected before running the command. Connect the phone, and reboot into bootloader. It by default (when connected to PC) should indicate FASTBOOT (highlighted in red) on the bootloader screen (and that is the mode it needs to be in, to execute fastboot commands).
Then you will execute the command via the command prompt. Do not try to execute (click on) the fastboot.exe. Its not a exe program you manually run, but something that runs in the background when you enter the command in command prompt.
To do the fastboot command in command prompt, open Command Prompt, then you will need to change directory to wherever the fastboot.exe is located. I don't know where you put it, so I can't tell you the command specifically. But in general, you will probably need to enter:
cd \
(this command brings you back to the root directory of the "C" drive, as the default is usually your user directory)
And then change drive (cd) to the folder where fastboot.exe is located. For example, I will often copy it to the root directory of the "C" drive, in a folder called "Android SDK" to make this path pretty simple. If you do the same (copy to an easier location) make sure you copy all the contents of that folder, not just fastboot.exe. For my "simple" example, the cd path is:
cd Android SDK
But if you have folders within folders (to navigate to where fastboot.exe is located) you need to indicate the path using the "" character between folders:
cd folder1\folder2\Android SDK
After you have entered the path correctly, it should show up in the command prompt: C:\folder1\folder2\Android SDK
Once you have changed directory properly to whatever folder contains fastboot.exe, simply type the command:
fastboot oem lock
After the phone reboots, go into bootloader, and you should see RELOCKED near the top of the screen. Which means you were successful.
If you are still getting the dll error when properly executing the fastboot command, let me know and we will install a new adb/fastboot package.
Click to expand...
Click to collapse
Ok I have gotten the chance to attempt this finally and when I typed in "fastboot oem lock" I get waiting for device and nothing has happened.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/URL][/IMG]Actually it appears it wasnt recognizing that my phone was plugged in. I made sure it noticed it and attempted the prompt again and got this. I think maybe I should just start all from the begining and get a new file all together. I just want to be sure I have everything and I can place it where it should be the first time before I attempt this again. If you could guide me on how to get the new adb/fastboot package so I can try again that would be greatly appreciated
magicbumm328 said:
I think maybe I should just start all from the begining and get a new file all together. I just want to be sure I have everything and I can place it where it should be the first time before I attempt this again. If you could guide me on how to get the new adb/fastboot package so I can try again that would be greatly appreciated
Click to expand...
Click to collapse
Just use the XDA search function with the term "simple adb" and you will get a couple simple adb/fastboot installer packages, which many here have used with success.
OK I have downloaded a new ADB. For some reason when I plug the phone into the computer it only seems to be recognized while the phone is on and plugged in. When I am in the mode that shows the fastboot option the phone is not being recognized by the computer so when I enter the command to 'fastboot oem lock' it simply says "waiting for device" and nothing happens. Any suggestions as to why?
Try uninstalling any HTC drivers and HTC Sync. Then connect the phone, go to Windows Device Manager, find the phone (should have a exclamation point by it) and manually select generic Android MTP device (or something of the sort) drivers. This is what I have to do on my Win7 PC to get both adb/fastboot to work properly.
OK, so i am really lost at this point. I have been trying for the past couple of days with no luck.
I used Minimal adb and fastboot, downloaded Lg drivers (LGMobileDriver_WHQL_Ver_4.0.3), sdk google drivers and looked at many comments to figure this out.
i type adb device and my phone shows, I type fastboot device and last couple of my phone shows. I used Mininimal adb and fasboot to unclock the the bootloader and i followed all the commands but when i get to fastboot flash recovery twrpxxxx.img, it tells me cannot load twrpxxxx.img. Also, when i type in adb reboot bootloader in brings me the an LG screen with powered by android at the bottom instead of the correct screen.
So, i tried the other way. Power phone off, hold down the volume down button and plug in usb and bootloader/fastboot opens up ( the screen with the line in the top left, with a blank page). it shows unlocked, few lines in white, and then few lines in red. I type fasboot devices and my phone shows up displaying last couple of the phone sn#. but when i go to type fasboot flash recovery twrpxxxx.img, i get the same message cannot load twrpxxxx.img. and on the phone is shows fastboot getvar partition recovery.
Any idea on what this is and how can i solve this?
Thanks in advance.
Rename it to recovery.img and try again.
I renamed it and I still get the same error. Cannot load recovery.img
papatoon3 said:
I renamed it and I still get the same error. Cannot load recovery.img
Click to expand...
Click to collapse
Make sure the image is in the same folder that you are running adb from; it doesnt scan your whole computer for the file. ��
Elu_sama said:
Make sure the image is in the same folder that you are running adb from; it doesnt scan your whole computer for the file. ��
Click to expand...
Click to collapse
It is in the same folder.
Does it make any difference that my phone is unlocked from T-Mobile via unlocked code? That should not have anything to do with it thought. I am just tying to figure it out.
Figured it out.
papatoon3 said:
I renamed it and I still get the same error. Cannot load recovery.img
Click to expand...
Click to collapse
I suggest you remove and reinstall sdk or install nexus root tools and run a cmd within the updated tools. Make sure you installed the right drivers, delete all others, reinstall, although your error seems more a problem with the tools, permissions perhaps, did you run cmd as admin?
Unable to load tells me it can't find your file.. Perhaps it has a hidden extension? Recovery.img.txt
Whats the complete exact command you're typing?
"fastboot flash recovery recovery.img"
http://androiding.how/how-to-install-twrp-recovery-via-fastboot/
Sounds like this is not enabled
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LG-H901 using Tapatalk
papatoon3 said:
Does it make any difference that my phone is unlocked from T-Mobile via unlocked code? That should not have anything to do with it thought. I am just tying to figure it out.
Click to expand...
Click to collapse
SIM unlocked (tmo has no code, its an app) and bootloader unlocked isnt the same thing.
Never mind got it
papatoon3 said:
Figured it out.
Click to expand...
Click to collapse
What was the solution i need it please and thanks
tanked89 said:
Never mind got it
What was the solution i need it please and thanks
Click to expand...
Click to collapse
When your phone is turned on and plugged in, type command adb devices, Does it show?
Put phone in fastboot mode, type command fastboot devices, does it show?
I figured it out. I had to install motorola and g4 drivers to get fast boot to read when I only had one or the other it was only reading adb when I had both on pc it read and adb & fastboot and worked. Thank you.
Hi sir I am facing a problem I rooted my v10 first I unlocked bootloader and then I rooted it by using fwul I hard reset it but when I turned it on a twrp recovery menu appeared please help that how it fix