Hey guys, so I am trying to unlock my bootloader and cmd tells me: can't find "CIDGen.apk" to install. I edited the environment path and directed it to the proper directory with the APK and all of the ADB stuff. I deleted the runme.sh and CIDGen.apk and downloaded a new one to put in there but I still get the same thing. It is not zipped and my path is correct. Please help
Type
CD xxx
Where xxx is the full path to the directory containing the files.
Ok I typed that in. It shows the file directory. Now what?
EDIT: I typed in the install command and it worked!!! Thanks a bunch
Everything went fine. Thanks
Related
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!
Ok, this will be a bit of a technical thread, so bear with me. This is so people have an understanding of how to find and look at the update files that get put on a phone. If you are reading thru this, I will assume that you have a basic understanding of ADB and possibly of shell commands like ls and cd
When you go into settings -> About Phone - Software update, your phone does many checks to the file system. One of them is at a file /data/fota/ipth-muc.prop . Most people do not know this directory exists as when you are in ADB you can not do a list command on the /data directory without root. This file is re-created each time you boot your phone. If we do the following command, we can dowload the file to our computer:
ADB pull /data/fota/ipth-muc.prop
If we open the file, it will look a lot like this.
firmware.version=VS920ZV3
max.pkg.size=157286400
This file can also contain additional data. The string we want to add in there is where to download and place update packages. This can be defined as such:
pkg.location=
If this line does not exist, it will default to /cache/fota . Being as we can not cd into /cache or pull/push files there, this is a bad spot to put it. How ever, we can make directories and read/write to them under /data/local . Using this info we can do the following.
ADB shell
mkdir /data/local/temp
exit
From there, we can edit the original ipth-muc.prop file we pulled to look like this:
firmware.version=VS920ZV3
max.pkg.size=157286400
pkg.location=/data/local/temp
If you edit the file, use a true file editor. Notepad will not save it correctly, but Wordpad had no issues. From there we do the following
ADB push ipth-muc.prop /data/fota
Now when we do the update, it will place the downloaded files into our temp directory (note, you must do this after the phone is fully booted, but before you have the phone look for an update). Once the files are done downloading, click remind me later. Then we can go into ADB and pull the files.
ADB pull /data/local/temp
You will get two files. One will be the update "ipth_package.bin" and the manifest files "ipth_package.bin.dd" . The manifest file also contains the link to the original file name as link to it on the host server. The ipth_package.bin file is a simple zip file that can be opened with almost any archiving program.
The zip is signed by LG using their personal key, so modifying it and pushing it back to the phone is not currently possible. We can however see the contents of an update and see what is being change. I hope to use this in the near future to either break the LG key or find a way to find a glitch in a patch being done.
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.
Hi,
I tried to edit the file "state" in "/sys/devices/virtual/switch/hdmi/" to unlock HDMI checking according to some internet posts I found. The problem is that it won't let me edit the file. I used Root explorer. My phone is rooted.
I also tried using Terminal emulator + Busybox to directly edit the file but it still didn't work. The file can be copied to other directory, and the copied file in the new directory can be edited, but the original file cannot be deleted or edited. When I tried to delete it, the message showed "Operation not permitted".
Any idea? Do I have to use "mount" command ? If so, please suggest. I am new to android and linux.
naiponnoi said:
Hi,
I tried to edit the file "state" in "/sys/devices/virtual/switch/hdmi/" to unlock HDMI checking according to some internet posts I found. The problem is that it won't let me edit the file. I used Root explorer. My phone is rooted.
I also tried using Terminal emulator + Busybox to directly edit the file but it still didn't work. The file can be copied to other directory, and the copied file in the new directory can be edited, but the original file cannot be deleted or edited. When I tried to delete it, the message showed "Operation not permitted".
Any idea? Do I have to use "mount" command ? If so, please suggest. I am new to android and linux.
Click to expand...
Click to collapse
Interested too. I m exactly at the same point, even with sys mounted RW
Hi. Any news oh this? Thanks
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.