I keep getting an error when trying to run fastboot. Any idea's?
c:Android>fastboot oem get_indentifier_token
'fastboot' is not recognized as an internal or external command, operable program or batch file.
Do you have adb and fastboot in the c:\android folder?
Yep they are both there. In my tools folder it says that he adb tool has moved to platform-tools/
If you don't see this directory in your SDK,
launch the SDK and AVD Manager (execute the android tool)
and install "Android SDK Platform-tools"
Please also update your PATH environment variable to
include the platform-tools/ directory, so you can
execute adb from any location.
Would this have any effect?
Yes. So you would have to point to the platform-tools folder or move adb into your android folder. Easier to just put it in your android folder so you don't have to navigate to it with the cmd prompt. Or do the PATH thing which I don't know how to do.
All you need in there is:
adb
AdbWinApi.dll
fastboot
Then after you get your Unlock_code.bin emailed to you copy that into there too.
I just keep all that as is and then anything I want to flash later I just copy in and then delete after I'm done flashing it. Except for the Amon Ra recovery, I've been keeping the current version of that in there too.
Related
Ok I have seen enough people having trouble whith the current root process so I going to try to explain it in the best way I know how.
First off if you have applied the new OTA update from tmobile either from tmobile or from xda dev forums the current root process WILL NOT WORK.
Now, that being said,
Step 1: Setting up the android sdk
Ok the Android sdk is a set of executable files thrown together to help developers piece together .apk's and various components for android devices thus the name "Software Developers kit". Now once you download the sdk I suggest that you install it on the root of your hard drive. In most users case it would be "C:/", and I also suggest your name its directory something simple like "SDK" like me because it cuts down on typing and the possiblity of typos.
Within the sdk directory there will be a directory called tools and this is where you will need to "cd" to in "cmd"
Cd = change directory
Cmd = Command Prompt
You may skip the next step if you have been able to view your devices serial number in "cmd".
Step 2: Viewing your devices serial number
I'm sure all of you like me as soon as we got our phone plugged it into our computer and messed around with it, well we just gave ourselves our first headache.
To fix this issue first we need to download and install "USBDeview" and uninstall all "Mytouch Slide" drivers from the computer .
Next we need to download "PDAnet" and install and choose "HTC" as the device.
Now we goto "Settings>Applications>Development and check "USB Debugging".
Now we can plug in our slide and our adb driver should install automatically without a hitch.
Now to verify open "cmd" type in "cd/" then "cd /sdk/tools" and "adb devices" and you should see your devices serial number.
Step 3: Understanding Root.zip package
The current root process is called "OTA spoofing" and its named this way for good reason. Within the root.zip there will be three files loop.bat, ota.zip, and update.zip.
Loop.bat = a batch script which loops the command "adb devices" until user command to stop "ctrl+c" verify with "Y".
OTA.zip = A .zip archive with tmobile ota signatures to allow the file to be read this file does not contain clockwormod recovery or superuser.apk or su.
Update.zip = the important file this file is what contains the recovery img and root permission "su" and "superuser.apk".
These files need to be placed in your "C:/SDK/tools" directory
Step 4: Getting your device to read in recovery
Now we power off the phone and power back on into "bootloader" press and hold Volume Down and power until your in bootloader.
Now it will check for an img on your sdcard it will not find one unless you put one there.
After its done press volume down before you select with power open up "cmd" and "cd" too your android sdk tools directory.
Type "loop" to start your loop batch script you should see "adbe devices" repeatedly being displayed on your screen.
Now select power.
If successful you will see "device offline" repeating
If not then repeat this step.
Otherwise unplug your usb cable from your device and then type "adb devices" and it should return with your serial number and devices in recovery.
Step 5: Pushing files and gaining root
Ok here we go...
Its important to know what the commands mean when doing this process.
"Adb push" :: adb push your.file /todirectory :: what this command is doing is sending the file you selected (in this case "your.file" to the directory you selected in this case the directory "todirectory") this is the proper syntax to push a file
However we need to send the ota.zip to the sdcard first but for the android recovery to read it it needs to be named "update". And we all know that two files with the same file extention and the same name cannot exist in the same directory. How do we solve this? By pushing ota.zip to the sdcard as "update.zip". This is done by the following command:
adb push ota.zip /sdcard/update.zip
This will send the ota.zip to the sdcard as "update.zip"
Now simply type in the following command BUT DO NOT PRESS RETURN ON YOUR KEYBOARD YET.
adb push update.zip /sdcard
Now scroll to "apply sdcard:update.zip" with volume down
Press power count
1...
2...
Press enter on your computers keyboard to send update.zip to the sdcard.
Boom you should see clockworkmod recovery.
Select install from sdcard find update.zip and select with the power and you now have root.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Should talk about the engineering rom too
Seriously. It took me A LOT of reading and swarming through 20+ tabs of the same thing to figure out that when everyone mentions ENG and installing ClockWorkMod Recovery and then small glimps of everyone saying "ENG for its recovery" that I FINALLY figured out you NEED to flash the ENG build for soley its test key's recovery to HAVE clockwork working the way its supposed to.
I rooted and now I keep losing su permissions and I can't boot into cwm recovery. I figure something messed up during the process. I guess I should unroot and then try the process again. I'm trying to use the HOWTO Return to stock properly and safely process.
I have adb installed and when I try to do the first step:
(adb push misc.img /data/local/)
It says this:
adb server is out of date. Killing....
* daemon started successfully *
cannot stat 'misc.img': no such file or directory
I'm sure I have a file in the wrong directory? Any help is appreciated!
From your pc before you run adb push did you:
cd c:\path\to\downloads\
?
I cannot the 100 percent certain that is what you need from your description but I however am 80 percent sure.
this is not a signature I type it in every time maybe sent from my phone or my computer
In the newer ADB version you need to have your command promt directed to the platform-tools directory. So, whatever you are trying to push also needs to be within that directory.
Even if you add it to your $PATH?
I haven't updated my sdk in a long long time so I'm not sure
this is not a signature I type it in every time maybe sent from my phone or my computer
If you have an old version of the Android SDK then misc.img should be placed in the tools directory. Personally I have the SDK version 7 and I had to place the files in Platform-tools.
rizzomegav said:
Even if you add it to your $PATH?
I haven't updated my sdk in a long long time so I'm not sure
this is not a signature I type it in every time maybe sent from my phone or my computer
Click to expand...
Click to collapse
It depends which directory path you have in your $PATH variable. If you have the latest SDK and $PATH is still pointing to "tools" then ADB will not be there... you need to update your $PATH variable to point wherever ADB is located.
stedrocklp said:
In the newer ADB version you need to have your command promt directed to the platform-tools directory. So, whatever you are trying to push also needs to be within that directory.
Click to expand...
Click to collapse
How can I see what version I'm using? I'm new to ADB and was just trying to follow the instructions on the HOWTO so I didn't have to ask a bunch of questions.
My adb is in C:\sdk\platform-tools\
if that helps any. That is also the file that the misc.img file is in
If your adb is in C:\sdk\platform-tools\ did you cd C:\sdk\platform-tools\ first?
Thanks to everyone for the help. I got it figured out last night!
what i want to do is to be able to use adb in any directory in windows instead of having to "cd" to the platform-tools directory and then using it, it makes it easier for when i want to copy a certain file to my tablet, i can just go where the file is at and use adb there. i know how to do it in linux, all i have to do in linux is make a shortcut of the adb file and copy it to the /usr/bin/ directory but when i tried that with windows, making the shortcut to adb and copying it to the c:\windows\system32\ directory, it didn't work. any help would be awesome!!! thanks in advance!
Hi all-
I have unknowingly renamed the framework-res.apk file to framework-res.bak, following the suggestion of a website (who had said to copy the file over, not rename it). I had no idea that would make the phone instantly useless, and render everything inoperative
I was rooted. All I need to do is copy the backup back over, but how?
I am able to get into CMM-based Recovery v5.0.2.7 and can mount the system directory and see it on my PC, but for some reason the framework directory is invisible. There is talk on the web about getting to a prompt and typing:
adb push framework-res.apk /system/framework/framework-res.apk
But how in the world do you get to a prompt? I don't see it on any menu, anywhere and the adb command is unrecognized on my OS.
Hoping I'm not ruined...... thanks for any advice.
Samsung Captivate Glide Android 2.3, Ubuntu
To get ADB, you first have to install the Android SDK.
http://developer.android.com/sdk/index.html
Then, you have to put ADB in the PATH variable.
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
After that, you can just type adb in the command prompt and it should work.
Hi,
I downloaded the SDK tools and got the adb command, but when I mount the phone with recovery I still don't see any framework directory.
I got to DOS and navigated to the directory where my copied framework-res.apk file was, and ran:
c:\adb\adb push framework-res.apk L:\framework\framework-res.apk
it replied with:
1319 kb/s (7979827 bytes in 5.905s)
However, then I rebooted the phone and it won't get past the SAMSUNG screen at all, it just sits there forever.
- why can't I see the framework directory, even though I have mounted it through CWM based recovery?
- can I see it using the ADB tools?
- has just copying the copied file back over, destroyed the cell phone? I can't possibly see how.
Thanks for any help
OK I found out the problem.
you need to use forward slashes and put the whole pathname in:
C:\adb\adb push framework-res.apk /system/framework/framework-res.apk
Thats assuming you have the adb command in the c:\adb directory.
It seems the phone is working again.
WHEW! Man that file is dangerous. be warned.
I'm trying to follow this tutorial on this page: https://forum.xda-developers.com/lg-g-pad-83/general/vk810-altev-complete-root-recovery-t3108260
Im on the section that says "How to downgrade and flash aboot4.2.2 " I put the aboot.img file in all the required folders, in the root of my internal memory on my android device, on the root of the sd card and in the platform tools folder. I am in adb mode on the PC and the device has USB debugging on. When i get to part after entering "SU" in CMD and enter the "dd if....." line of code it says that no such file or directory exists.
Why cant it find the aboot file I put in the folder and flash it? I'm all out of ideas and I'm about to go crazy if I cant figure this out.
masterx1234 said:
I'm trying to follow this tutorial on this page: https://forum.xda-developers.com/lg-g-pad-83/general/vk810-altev-complete-root-recovery-t3108260
Im on the section that says "How to downgrade and flash aboot4.2.2 " I put the aboot.img file in all the required folders, in the root of my internal memory on my android device, on the root of the sd card and in the platform tools folder. I am in adb mode on the PC and the device has USB debugging on. When i get to part after entering "SU" in CMD and enter the "dd if....." line of code it says that no such file or directory exists.
Why cant it find the aboot file I put in the folder and flash it? I'm all out of ideas and I'm about to go crazy if I cant figure this out.
Click to expand...
Click to collapse
Instruction number 3 says to put a boot file in /platform-tools folder of SD card, but then command shows 'if /sdcard/aboot', which would point the program to the root of your internal storage. Instead of copying the commands directly, modify the command to point to where your about file actually is.