[TOOL] [14th Dec] | AIOlog - All in One Android Logger v0.5 - Android Software Development

AIOlog - All in One Android Logger​
{
"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"
}
Features:
Display and output Logcat
Last_kmsg
Dmesg
Kmsg
Kernel Version
Click to expand...
Click to collapse
Latest Version:
1. AIOlog for Windows: http://aiolog.googlecode.com/files/aiolog_win_v0.5.zip
2. AIOlog for Linux 32bit: http://aiolog.googlecode.com/files/aiolog_linux_32_v0.5.tar
3. AIOlog for Linux 64bit: http://aiolog.googlecode.com/files/aiolog_linux_64_v0.5.tar
4. AIOlog for Mac 32bit: http://aiolog.googlecode.com/files/aiolog_mac_32_v0.5.tar
5. AIOlog for Mac 64bit: http://aiolog.googlecode.com/files/aiolog_mac_64_v0.5.tar
Click to expand...
Click to collapse
NOTE: If you have this error "Cannot execute binary files" while using the AIOlog for linux, please download the 32bit version.
If you've downloaded the AIOlog v0.3 generic, please use the following file:
Either the aiolog_32bit or aiolog_generic_32bit
If this is your first time doing a log, you may need this file(Windows only):
http://code.google.com/p/aiolog/downloads/detail?name=aiolog_adb_fastboot_win_v0.1.zip
New features:
Added log push to phone and phone directory creation(log will be available at the computer, and the .aiolog, aiolog and root folder of your phone)
Added log archiving(unix)
Added log cid version
Added ADB files for Windows
Fixed a bug to auto detect device id when there is only one device
Click to expand...
Click to collapse
Full Changelog: https://github.com/wcypierre/AIOlog/commits/master​
Hi, I'm now in the look for users who can provide me with some data(non-private and non-confidential ones) in order to improve AIOlog as a big amount of data is needed for AIOlog in order to success.
If you're interested, please pm me and state your device name or you can email me via [email protected]
Basic Howto:
1. At your phone, go to Settings -> Developer Options
2. Tick the "Android Debugging"
3. Connect your phone to your computer(desktop/laptop)
Windows:
1. Navigate to the location where the aiolog is located
2. Extract it and place it to a folder
3. Open aiolog.exe by clicking at it
4. The menu will appear
5. Just enter the number(1,2,3 ...) of the function that you wanted to do
Linux:
NOTE: For AIOlog version 0.4 onwards, the binary file is called either aiolog_32bit or aiolog_64bit so please change it accordingly (The steps for the filename is used in Step #3)
1. Open your terminal
2. Navigate to where aiolog is located. Example, "cd ~/Downloads/" (Assuming that the file is saved at Downloads folder)
3. Type "./aiolog" and press enter
4. The menu will appear
5. Just enter the number(1,2,3 ...) of the function that you wanted to do
Click to expand...
Click to collapse
Advanced Howto:
1. At your phone, go to Settings -> Developer Options
2. Tick the "Android Debugging"
3. Connect your phone to your computer(desktop/laptop)
Windows:
1. Open the cmd
2. Navigate to the folder where aiolog is located
3. Type "aiolog -h" and press enter
4. Search for the functions that you wanted to do and type its command(refer to the examples below)
Examples:
1. To log all logs, type "aiolog.exe -a"
2. To get the logcat, type "aiolog.exe -l"
3. To get the last_kmsg, type "aiolog.exe -lk"
4. To specify a device that is to be used(use it when you have a lot of devices connected) and to get a dmesg, "aiolog.exe -id SH<yourdeviceid> -d"
Linux:
1. Open your terminal
2. Navigate to where aiolog is located. Example, "cd ~/Downloads/" (Assuming that the file is saved at Downloads folder)
3. Type "./aiolog -h" and press enter
4. Search for the functions that you wanted to do and type its command(refer to the examples below).
Examples:
1. To log all logs, type "aiolog.exe -a"
2. To get the logcat, type "./aiolog -l"
3. To get the last_kmsg, type "./aiolog -lk"
4. To specify a device that is to be used(use it when you have a lot of devices connected) and to get a dmesg, "./aiolog -id SH<yourdeviceid> -d"
Click to expand...
Click to collapse
Compatibility:
1. Full support on Windows
2. Partial support on Linux
3. Partial support on Mac(Version 0.5 onwards)
Issues:
1. May not work on mac yet(but it should be).
2. AIOlog will not work if the adb is not started for a 30 seconds to 1 minute in advance
Found a bug?
1. Go to here: http://code.google.com/p/aiolog/issues/list
2. Click New issue
3. Fill in the details
4. Report
5. Wait for it to be resolved :good:
Changelog:
Version 0.4
1. Added Auto Device Id detection
2. Logging support when there are more than 2 devices connected
3. Added logcat clear and dmesg clear
Version 0.3
1. Added logcat radio(to debug for radio issues)
2. Added log essential(logcat, dmesg, kmsg and last_kmsg)
3. Disable reprompt of device id after it has been entered
4. Misc Fixes
Version 0.2
1. Logcat, kmsg continuous(the normal logcat, kmsg way instead of log, stop and save method) added
2. Added additional checking on device id
3. Removed debug code
Version 0.1
1. Core functions(logcat, last_kmsg, dmesg, last_kmsg) implemented
2. Outputs the log to the current directory of AIOlog
3. kernel version output is implemented
Click to expand...
Click to collapse
To do list:
1. To archive the logs into an archive(zip, rar, tar)
2. To include mac support
3. To include log essential (Done )
4. To log other details
5. Fix any existing bugs

Building from Source
Prerequisite:
- Command Line Git(be it from any OS)
Instructions:
To clone the AIOlog(one time process):
git clone git://github.com/wcypierre/AIOlog.git
To update the existing AIOlog:
git remote update
git rebase origin/master
To compile AIOlog:
g++ main.cpp log.cpp -o aiolog.exe (for windows) / g++ main.cpp log.cpp -o aiolog (for mac/linux)

Miscellaneous:
If you want to log the logs using other methods, please refer to this thread by nitubhaskar:
http://forum.xda-developers.com/showthread.php?p=33716489

Nice. Will try it

Warren87 said:
Nice. Will try it
Click to expand...
Click to collapse
Please do try it and give any suggestions and how to improve the program

Nice tool, wcypierre!
Very helpfull for noob users.

icke said:
Nice tool, wcypierre!
Very helpfull for noob users.
Click to expand...
Click to collapse
Thanks . Please do provide some feedbacks after you've use it eh

Build from source instructions is added

For those who build from source, v0.3a is out(but the version number shows it as v0.2)

Version 0.2 is out!
1. AIOlog for Windows: http://aiolog.googlecode.com/files/aiolog_win_v0.2.zip
2. AIOlog for Linux: http://aiolog.googlecode.com/files/aiolog_linux_v0.2.tar
3. AIOlog for Mac: Coming soon.......
New features:
Version 0.2
1. Logcat, kmsg continuous(the normal logcat, kmsg way instead of log, stop and save method) added
2. Added additional checking on device id
3. Removed debug code

For those who build from source, please do a remote update as new commits has been committed to github

Ok, so I haven't played with it yet but I thought that I would provide some information to any other Ubuntu users who try to use the tool.
The download and compile of the executable occurs without any problems. If you have compiled nay other apps form source this is really easy.
In order to get the app to run you need to have adb installed and running.
I am not going to get into all the details for that. Google it.
But what you won't find in the instructions for when installing adb is the following:
a) You need to run adb under sudo, otherwise you get an error which says something along the lines of "no permissions", or "no permissions for this device" when you run aiolog.
b) If you have added adb to your path (Google it for instructions) then you run sudo with the -i argument. That is enter "sudo -i ad start-server"
Good luck

Nice gonna try soon

GaryWS said:
Ok, so I haven't played with it yet but I thought that I would provide some information to any other Ubuntu users who try to use the tool.
The download and compile of the executable occurs without any problems. If you have compiled nay other apps form source this is really easy.
In order to get the app to run you need to have adb installed and running.
I am not going to get into all the details for that. Google it.
But what you won't find in the instructions for when installing adb is the following:
a) You need to run adb under sudo, otherwise you get an error which says something along the lines of "no permissions", or "no permissions for this device" when you run aiolog.
b) If you have added adb to your path (Google it for instructions) then you run sudo with the -i argument. That is enter "sudo -i ad start-server"
Good luck
Click to expand...
Click to collapse
Thanks for the feedback . Was waiting for things like these(community feedback, so I can know new issues and write up on it) :good: .Provided that you know how to use git, usually compiling from source would not be a problem(especially when the project is only this small )
For the permission problem, I used to had that as well but I don't quite remember how I solved that. It can either be a permission problem at the adb file or the aiolog. anyway, just chmod the file to 755 with superuser permission(sudo) and you should be able to run it
Sample run of the command:
sudo chmod 755 aiolog
btw, would you mind to add a "b" after the "ad", because it should be "adb" instead of "ad"

Version 0.3 is out
New Features
Version 0.3
1. Added logcat radio(to debug for radio issues)
2. Added log essential(logcat, dmesg, kmsg and last_kmsg)
3. Disable reprompt of device id after it has been entered
4. Misc Fixes

Hey, i have added your tool to my all in one guide mate as we discussed.. and gave thread link to here..
Also congrats on hitting the portal news!! You got covered by POORCOLLEGEGUY.. he is awesome at covering these,..

nitubhaskar said:
Hey, i have added your tool to my all in one guide mate as we discussed.. and gave thread link to here..
Also congrats on hitting the portal news!! You got covered by POORCOLLEGEGUY.. he is awesome at covering these,..
Click to expand...
Click to collapse
hey, thanks for doing that :good: . I'll try and see what I can do for your thread
yeah, just noticed that, you're welcome

Hi, there!
Just downloaded aiolog_linux_v0.3.tar, extract and tried to execute, but had no succes ((
Can anybody help me?
Thanks!
Code:
[email protected]:~/Downloads/aiolog_v0.3$ uname -a
Linux vovs-pc 3.2.0-32-generic-pae #51-Ubuntu SMP Wed Sep 26 21:54:23 UTC 2012 i686 athlon i386 GNU/Linux
[email protected]:~/Downloads/aiolog_v0.3$ ./aiolog
bash: ./aiolog: cannot execute binary file

v0vs said:
Hi, there!
Just downloaded aiolog_linux_v0.3.tar, extract and tried to execute, but had no succes ((
Can anybody help me?
Thanks!
Code:
[email protected]:~/Downloads/aiolog_v0.3$ uname -a
Linux vovs-pc 3.2.0-32-generic-pae #51-Ubuntu SMP Wed Sep 26 21:54:23 UTC 2012 i686 athlon i386 GNU/Linux
[email protected]:~/Downloads/aiolog_v0.3$ ./aiolog
bash: ./aiolog: cannot execute binary file
Click to expand...
Click to collapse
Try to change the permissions and run it again
do the following:
sudo chmod 755 aiolog
Click to expand...
Click to collapse

same result
Code:
[email protected]:~/Downloads/aiolog_v0.3$ sudo chmod 755 aiolog
[sudo] password for vovs:
[email protected]:~/Downloads/aiolog_v0.3$ ./aiolog
bash: ./aiolog: cannot execute binary file
[email protected]:~/Downloads/aiolog_v0.3$ ls -l
total 64
-rwxr-xr-x 1 vovs vovs 27133 Nov 4 14:54 aiolog
-rw-rw-r-- 1 vovs vovs 35147 Oct 16 16:47 COPYING
[email protected]:~/Downloads/aiolog_v0.3$ ./aiolog
bash: ./aiolog: cannot execute binary file

Related

[Guide] Setting up ADB [Windows]

This guide was originally written by ante0 on VillainROM.co.uk. For the original click here. Due to some people having issues accessing VillainROM's website I have asked ante0 to give me permission to post the guide here. He happily obliged so thanks go to ante0 for this guide!
All I have done to it is change the layout and remove any unnecessary text.
Tools needed:
Android SDK
HTC Sync 3.0.5387 - get the latest if this is old
WinRAR - to extract Android's SDK files
Patience and time
1. Getting ADB (Android Debug Bridge)
ADB is a part of android's SDK. It can be obtained here. Please get the latest Windows version.
Next we need to "install" it.
This is done by simply extracting it to your hard drive:
Install WinRar, then right click on the zip file and choose "extract to".
I chose C:\ as the folder in the zip is named "android-sdk-windows", so you can find the files in C:\android-sdk-windows
After that is done we are now done with the "installing" part.
2. Setting up environment variables - access adb from outside of \android-sdk-windows\tools directory in a command prompt
Now that we have extracted all files we need to set up Windows environment variables to make our lives easier.
I always do this, because it saves you having to cd C:\android-sdk-windows\tools every time you load a cmd prompt.
Windows XP:
Right click on "My computer" and select "Properties"
Click on the "Advanced" tab in the box that appears, looks like the pic below.
{
"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"
}
Click on the button named "Environment Variables".
Now, double click on the text entry named "Path" in the lower list box
At the end of it, add ";C:\android-sdk-windows\Tools"
(";" is required at the start so windows knows it's a new entry.)
Click on OK to exit out of the dialog, then OK again to get out of My computer's properties. After you reboot your computer you'll have it set up.
Windows 7/Vista:
Right click on "Computer" and select "Properties"
In the System window that appears click on "Advanced System settings" located in the left list
Click on the Advanced tab in the box that appears, then on the "environment variables" button.
Double click on "Path" located in the lower list box.
At the end of it, add ";C:\android-sdk-windows\Tools"
(";" is required at the start so windows knows it's a new entry.)
Now click on OK, then OK again to exit. Restart and all will be set up.
3. Making sure USB works
(original guide linked to my old driver guide - here are new details)
Install the very latest version of HTC Sync - 3.0.5387 is the latest at time of writing but get the latest if this is old
This should install the correct drivers regardless of whether you're on 64-bit, 32-bit, Vista, 7 or XP.
4. Using ADB
(unedited)
I won't list all commands you can use here. I will only list some examples...
Remember to plug your phone in your usb cable (I've forgotten sometimes... lol)
Start by opening a command prompt.
This is done by opening up the startmenu then click on "Run..." (Alternative way: Windowskey + R).
In the "Run..." box, enter "cmd" without quotes.
If you have some knowledge of using a cmd prompt you don't need to read the next part.
To navigate you mainly use the commands CD and DIR.
Here's an image of what it looks like
C:\Documents and settings\jwork> tells you what your current working folder is.
To get out of it, use the command "cd ..".
This will go back one folder, so your new location will be C:\Documents and settings>
One more "cd .." will take you to C:\.
Now, lets say you have a folder named Images in C:\. To enter it you use "cd Images".
If you want to list all files in that folder, enter the command "dir".
Now you might have a image named image01.jpg in that folder, that you want to get to your phone.
Use the command adb push image01.jpg /sdcard/
It should notify you now if the push was successful.
You can check if the image is on your sdcard by using the command "adb shell ls /sdcard/".
That should conclude this guide...
One more thing, if you just enter "adb" it will show a list of all commands with descriptions.
Any questions? Just post here.
Hi
i really need some help here. whenever i type adb into the command box , i get "adb" is not recognised as an internal or external command , operable program or batch file. But i have alrdy installed the ADB by extracting it to a folder.
Right now im trying to install a custom rom and im stuck at accessing the recovery page pls help meee
Sounds like you haven't successfully added adb to your DOS path. Re-read section 2 again and make sure you followed the instructions correctly.
Great guide man, very nice work
That's awesome!!! It's a nice tutorial for the newbies! And it benefits me, I reli like it!!
Thx!!!
Sent from my E15i using XDA App
jubo1236 said:
Hi
i really need some help here. whenever i type adb into the command box , i get "adb" is not recognised as an internal or external command , operable program or batch file. But i have alrdy installed the ADB by extracting it to a folder.
Right now im trying to install a custom rom and im stuck at accessing the recovery page pls help meee
Click to expand...
Click to collapse
I had the same problem because the path was incorrect. I found the adb command in
Code:
android-sdk-windows/platform-tools/
rather than in
Code:
android-sdk-windows/tools/
btdag said:
1. Getting ADB (Android Debug Bridge)
ADB is a part of android's SDK. It can be obtained here. Please get the latest Windows version.
Click to expand...
Click to collapse
hi,
thanks for the explanation both for you and ante0 but can you reload the link if possible becaue i cannot download the file for the first step? it gives error
No matter what I do. I always get the "adb" is not recognised as an internal or external command , operable program or batch file. What am I doing wrong?
Google has recently changed where adb can be found in the sdk. Just un-zip it anywhere i recommend the C drive, so it should look like this C:\android-sdk-windows\
Then browse to this folder and launch 'SDK Manager'
Open the window 'Choose packages to install' (it should open automatically first time) and choose to install the 'Android SDK Platform-tools, revision *'
To set the variable paths, do as in the first post and add these variable strings (assuming you unzipped it to C:\android-sdk-windows\ if not just modify it so it matches where you unzipped it to
Code:
;c:\android-sdk-windows\tools;c:\android-sdk-windows\platform-tools
Then you're good to go!
After doing all the above stated i still can't execute any commands. I typed "adb devices" and it just says the devices that are linked but it doesn't give me a serial number.
NeatBee said:
Google has recently changed where adb can be found in the sdk. Just un-zip it anywhere i recommend the C drive, so it should look like this C:\android-sdk-windows\
Then browse to this folder and launch 'SDK Manager'
Open the window 'Choose packages to install' (it should open automatically first time) and choose to install the 'Android SDK Platform-tools, revision *'
To set the variable paths, do as in the first post and add these variable strings (assuming you unzipped it to C:\android-sdk-windows\ if not just modify it so it matches where you unzipped it to
Code:
;c:\android-sdk-windows\tools;c:\android-sdk-windows\platform-tools
Then you're good to go!
Click to expand...
Click to collapse
What does it say? Copy it to here
Sent from my Hero using Tapatalk
I have tried to restart the computer, sign in and out, install SDK again and again, changed the PATH in Enviromentor variables ... but still refuses ADB to work!
I typed "C: \ android-sdk-windows \-platform tools," in the PATH box and restarted the computer. Then I typed "adb" in CMD, but it is all the time: "'adb' Is Not Recognized as an internal or external command,
operable program or batch file. "
Is crazy! What is the problem?
BTW, I have installed the driver for my phone and selected "USB debugging".
You've typed the path wrong. Delete the path you've already put in it and copy this one
Code:
;C:/android-sdk-windows/platform-tools/;C:/android-sdk-windows/tools/;
hello
NeatBee said:
You've typed the path wrong. Delete the path you've already put in it and copy this one
Code:
;C:/android-sdk-windows/platform-tools/;C:/android-sdk-windows/tools/;
Click to expand...
Click to collapse
I think you are using wrong format, \ instead of /
For me I used "C:\Program Files\Android\android-sdk-windows\platform-tools\;C:\android-sdk-windows\tools\;"
in order to make it work"....ignore quotes.
Yet when I try to do the push command with some files
it gives me error: devise not found
anyone have clue?!
Thanks
This guide is rock solid! Thanks
mm realy need to learn to use adb been flashing my hero for over a year now and still dont know how adb works
sorry for the silly question but will the same steps help to setup a path for windows 7
because i really need to know how to use it as well if someone acn post a link for steps to use it it would be really appreaciated
thanks
EDIT: extremely sorry did not read the full post there is already a guide for windows 7
thanks for the post
ok so i have tried all of the above steps
i now get adbd cannot run in production builds
thanks alot
once i get adb all set up and it works fine - can i uninstall HTC sync and HTC driver? will adb still work?

[HOW TO]Unlocking method for "file not found" problem

Before we start, ROOT access, along with the "usb debugging" to be enabled on your phone for this unlock to be successful. Your phone must be connected to the computer.
UPDATE:One-click unlock for PC & MAC Created: http://forum.xda-developers.com/showthread.php?t=761751
The first step requires ADB which is a console that comes with the Android SDK, and is located in the C:\ Drive.
You can create a easy script to access adb by creating a text file and copying the following information:
Code:
@echo off
cd c:\android-sdk-windows\Tools
adb devices
pause
adb shell
NOTE: The android sdk must be in the C:\ drive for the script to work, and you can rename the "android-sdk-windows" to something else if you have an alternate name for your android sdk folder.
name the script ADB, and rename the .txt extension to .bat (enable view hidden file extensions in folder options) and run it for quick, and easy access to adb.
Now that problem is solved, lets get on to extracting the actual file from the internal sd card, to your computer for the purpose of extracting the unlock code.
Run adb.bat to open up adb, or any other method you might use and you should see a cmd promt with A list of the devices attached along with your device.
Press any key, and you should see a $ -----> type "su" (without the quotation marks) and press [ENTER]. If your device has already granted "su" or Superuser permissions to your desktop adb console, then you should see a # now you type
the following:
cat /efs/nv_data.bin >> /sdcard/nv_data.bin
press [ENTER] and you should see a repetition of the command you just typed with the difference being that the "#" is not before it, but under it.
You have successfully transferred the file to your internal sd card!
{
"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"
}
Now to transferring the file that we will obtain the unlock code, to the computer to extract said code.
On your phone (while still connected to the computer) you must mount the USB storage to extract the file off the internal SD card, (to do this drag the notification bar down while connected, and click the "usb connected" button, which will prompt a pop up for "Mount" and "Don't Mount", we'll be mounting the sd card to extract the file)
now check "my computer" and look for the storage disk of the internal sd card for your phone (not the external!)
then move the "nv_data.bin" file to your C:\ drive
Now you need to download the "sgux.exe" unlock code finder, you can find it at the following:
http://www.mediafire.com/?js8dgn3nic5asb0 or http://www.multiupload.com/2IAYWWGF8A
after downloading the file from either mirror (the media fire one is zipped, which means you need to extract it) you need to move the sgux.exe file to your C:\
Now onto the last step:Obtaining the Code!
after having both the sgux.exe, and nv_data.bin file in the C:\ drive
Run your command promt (run>cmd or if you have a "windows key" press the windows key+r) in the command prompt type "cd C:\" (without the quotation marks) then sgux.exe nv_data.bin and voila the proccess should generate your own 8-digit unlock code!!
Now give yourself a pat on the back for your hard work ;P
HOW TO LOCK SAMSUNG GALAXY S - FOR WARRANTY AND ALTERNATIVE "UNLOCK"
After you get the NCK code using the method above, enter: *7465625*638*#
There will be a pop-up box.
Complete the first field (MCC/MNC) with the network you want your phone locked to (eg. 226 10 where 226 = romania; 10 = orange etc.) and the second field (Control Key) with the NCK extracted from the .bin file.
Press OK and your phone should relock.
This method can also be used in the case where the universal unlock code doesn't work, this is done by "locking the device to the carrier+sim" so someone who uses Rogers in Canada, would use the NETWORK "MCC" for their Country (302) and MNC for the carrier (720) so you use 302 720 with the instructions above to lock the phone to Rogers in Canada, thus allowing you to use the sim card. This is a "unlock" in terms that you can use it with another carrier, but not a "universal" unlock that can be used with any carrier without the hassle of repeating the above method.
Here are the MCC/MNC country codes:
http://en.wikipedia.org/wiki/Mobile_Network_Code
HOW TO UNLOCK AFTER PLACING DIFFERENT SIM
After inserting new sim, you should be prompted to enter unlock code, if not then to unlock your phone just use the code: #7465625*638*# and enter your NCK in the pop-up box. Press OK. Phone should get unlocked .
Click to expand...
Click to collapse
NOTE: Below I have attached the "adb.bat script, and the sgux.exe" files in zips, for those who want to download it directly from here.
I have flashed to JM5 and with Samset 1.9f, It comes pre-rooted but does not have a terminal emulator yet and Id like to give this a try on my locked Galaxy S, but Im not familiar with how to get ADB for my computer.. maybe you can add the steps or post another link for ADB ?
EarlZ said:
I have flashed to JM5 and with Samset 1.9f, It comes pre-rooted but does not have a terminal emulator yet and Id like to give this a try on my locked Galaxy S, but Im not familiar with how to get ADB for my computer.. maybe you can add the steps or post another link for ADB ?
Click to expand...
Click to collapse
I've included all the instruction for running ADB , but in that case make sure you have the android sdk installed
You can download it at the following:
http://dl.google.com/android/android-sdk_r06-windows.zip
Extract the zip, and then just follow my instructions in my original post.
I've also included a script to run it directly, it's attached in the first post and is called "adb.zip" that has the adb.bat script inside.
UPDATE:
You can also use the original method
http://forum.xda-developers.com/showpost.php?p=7776555&postcount=1
but instead of the adb code in there which is the following:
Code:
adb shell
su
dd if=/dev/block/bml3 of=/sdcard/bml3.bak
the above is the original method, but for some adb consoles there's a VITAL step missing!
the actual dev directory.
So below is the fix for the first method to work (use this)
Code:
adb shell
cd /dev/block
su
dd if=/dev/block/bml3 of=/sdcard/bml3.bak
Bowsa2511 said:
UPDATE:
You can also use the original method
http://forum.xda-developers.com/showpost.php?p=7776555&postcount=1
but instead of the adb code in there which is the following:
Code:
adb shell
su
dd if=/dev/block/bml3 of=/sdcard/bml3.bak
the above is the original method, but for some adb consoles there's a VITAL step missing!
the actual dev directory.
So below is the fix for the first method to work (use this)
Code:
adb shell
cd /dev/block
su
dd if=/dev/block/bml3 of=/sdcard/bml3.bak
Click to expand...
Click to collapse
the cd /dev/block shouldn't matter but I will add it to the guide
dagentooboy said:
the cd /dev/block shouldn't matter but I will add it to the guide
Click to expand...
Click to collapse
In my case (along with others) it wouldn't recognize and direct to the directory automatically, causing the creation of the nv_data.bin method.
The simple fix was directing adb to that directory XD
Bowsa2511 said:
In my case (along with others) it wouldn't recognize and direct to the directory automatically, causing the creation of the nv_data.bin method.
The simple fix was directing adb to that directory XD
Click to expand...
Click to collapse
ok sounds good. I found the nv_data.bin method by tracing where bml3 was being mounted. It turns out bml3 is mounted at /efs .... that is probably why you need su to copy bml3 because it is in use.
guys, could you please explain how to sim unlock but with some easier methods
these ADB and so on just have eaten my brains
spent 3 hours and 0 result
using mac os + windows 7 as virtual machine
DarkVasyaK said:
guys, could you please explain how to sim unlock but with some easier methods
these ADB and so on just have eaten my brains
spent 3 hours and 0 result
using mac os + windows 7 as virtual machine
Click to expand...
Click to collapse
Check out the original thread here. I updated it with an automatic script to generate the code.
It Worked.............great................Thank you so much.......
thansk for this!
Instructions worked perfectly ... got my code!
Now just have to find a foreign SIM to complete the job ...
Thanks to all that made this possible. AT&T was being a real PITA about unlocking.
Bowsa2511 said:
Before we start, ROOT access, along with the "usb debugging" to be enabled on your phone for this unlock to be successful. Your phone must be connected to the computer.
The first step requires ADB which is a console that comes with the Android SDK, and is located in the C:\ Drive.
You can create a easy script to access adb by creating a text file and copying the following information:
Code:
@echo off
cd c:\android-sdk-windows\Tools
adb devices
pause
adb shell
NOTE: The android sdk must be in the C:\ drive for the script to work, and you can rename the "android-sdk-windows" to something else if you have an alternate name for your android sdk folder.
name the script ADB, and rename the .txt extension to .bat (enable view hidden file extensions in folder options) and run it for quick, and easy access to adb.
Now that problem is solved, lets get on to extracting the actual file from the internal sd card, to your computer for the purpose of extracting the unlock code.
Run adb.bat to open up adb, or any other method you might use and you should see a cmd promt with A list of the devices attached along with your device.
Press any key, and you should see a $ -----> type "su" (without the quotation marks) and press [ENTER]. If your device has already granted "su" or Superuser permissions to your desktop adb console, then you should see a # now you type
the following:
cat /efs/nv_data.bin >> /sdcard/nv_data.bin
press [ENTER] and you should see a repetition of the command you just typed with the difference being that the "#" is not before it, but under it.
NOTE: Below I have attached the "adb.bat script, and the sgux.exe" files in zips, for those who want to download it directly from here.
Click to expand...
Click to collapse
Thank you for your step by step sir, very helpful, as i was trying to figure out how to get ADB running on my PC.
Thanks again.
not working...tried all methods for pc
tried adb method and cannot create nv_data.bin file system is read-only
tried unlocker app and it says NO CODES FOUND, and also says are you sure your using a samsung galaxy S.
my phone is samsung i897 captivate under att contract, never had to enter a code in the past, but now the phone is locked and i cant retrieve the code, any ideas?
Help please
i´ve tried to unlock have searched der nv_data.bin with a root explorer app, copied this to sd and from there in my folder c:\hack, where the sgux.exe is also
I run it and following i see if its ready:
Opening file <nv.bata.bin>....
Searching code block....
Found
Searching Code...
C:\hack>
where is my code?
Please help
Awesome guide! Can't wait to get my phone monday
I tried adb, and when I type su I get a reply superuser denied, don't understand why, need help
bump......
After running sgux.exe nv_data.bin, this is what show up:
MCC/MNC lock :00101
Any idea?
I'm on att, but currently roaming in China...
after I type su, it say's "Permission denied" what am I doing wrong? Can some please help me

[How-To] Root an Android Virtual Device (AVD) [Video]

Hi guys, I made a little screen-cast of the routine used to root an android emulator.
Here's the video version, but I wrote the text version under it too.
Prerequisities​
su binary : http://d-h.st/qZ2
busybox binary : http://d-h.st/IIv
Superuser apk : http://d-h.st/Et5
(These instructions are assuming you're on ubuntu or an other debian-based linux distro, but it should be pretty easy to adapt to batch if you're on windows.)
Instructions​
1) First, create a new AVD in Eclipse or in terminal
Here's the manpage for the emulator :
Code:
Android Emulator usage: emulator [options] [-qemu args]
options:
-sysdir <dir> search for system disk images in <dir>
-system <file> read initial system image from <file>
-datadir <dir> write user data into <dir>
-kernel <file> use specific emulated kernel
-ramdisk <file> ramdisk image (default <system>/ramdisk.img
-image <file> obsolete, use -system <file> instead
-initdata <file> same as '-init-data <file>'
-data <file> data image (default <datadir>/userdata-qemu.img
-partition-size <size> system/data partition size in MBs
-cache <file> cache partition image (default is temporary file)
-cache-size <size> cache partition size in MBs
-no-cache disable the cache partition
-nocache same as -no-cache
-sdcard <file> SD card image (default <system>/sdcard.img
-snapstorage <file> file that contains all state snapshots (default <datadir>/snapshots.img)
-no-snapstorage do not mount a snapshot storage file (this disables all snapshot functionality)
-snapshot <name> name of snapshot within storage file for auto-start and auto-save (default 'default-boot')
-no-snapshot perform a full boot and do not do not auto-save, but qemu vmload and vmsave operate on snapstorage
-no-snapshot-save do not auto-save to snapshot on exit: abandon changed state
-no-snapshot-load do not auto-start from snapshot: perform a full boot
-snapshot-list show a list of available snapshots
-no-snapshot-update-time do not do try to correct snapshot time on restore
-wipe-data reset the user data image (copy it from initdata)
-avd <name> use a specific android virtual device
-skindir <dir> search skins in <dir> (default <system>/skins)
-skin <name> select a given skin
-no-skin don't use any emulator skin
-noskin same as -no-skin
-dynamic-skin dynamically construct a skin of given size, requires -skin WxH option
-memory <size> physical RAM size in MBs
-netspeed <speed> maximum network download/upload speeds
-netdelay <delay> network latency emulation
-netfast disable network shaping
-trace <name> enable code profiling (F9 to start)
-show-kernel display kernel messages
-shell enable root shell on current terminal
-no-jni disable JNI checks in the Dalvik runtime
-nojni same as -no-jni
-logcat <tags> enable logcat output with given tags
-no-audio disable audio support
-noaudio same as -no-audio
-audio <backend> use specific audio backend
-raw-keys disable Unicode keyboard reverse-mapping
-radio <device> redirect radio modem interface to character device
-port <port> TCP port that will be used for the console
-ports <consoleport>,<adbport> TCP ports used for the console and adb bridge
-onion <image> use overlay PNG image over screen
-onion-alpha <%age> specify onion-skin translucency
-onion-rotation 0|1|2|3 specify onion-skin rotation
-scale <scale> scale emulator window
-dpi-device <dpi> specify device's resolution in dpi (default 165)
-http-proxy <proxy> make TCP connections through a HTTP/HTTPS proxy
-timezone <timezone> use this timezone instead of the host's default
-dns-server <servers> use this DNS server(s) in the emulated system
-cpu-delay <cpudelay> throttle CPU emulation
-no-boot-anim disable animation for faster boot
-no-window disable graphical window display
-version display emulator version number
-report-console <socket> report console port to remote socket
-gps <device> redirect NMEA GPS to character device
-keyset <name> specify keyset file name
-shell-serial <device> specific character device for root shell
-tcpdump <file> capture network packets to file
-bootchart <timeout> enable bootcharting
-charmap <file> use specific key character map
-prop <name>=<value> set system property on boot
-shared-net-id <number> join the shared network, using IP address 10.1.2.<number>
-nand-limits <nlimits> enforce NAND/Flash read/write thresholds
-memcheck <flags> enable memory access checking
-gpu <mode> set hardware OpenGLES emulation mode
-camera-back <mode> set emulation mode for a camera facing back
-camera-front <mode> set emulation mode for a camera facing front
-webcam-list lists web cameras available for emulation
-screen <mode> set emulated screen mode
-force-32bit always use 32-bit emulator
-qemu args... pass arguments to qemu
-qemu -h display qemu help
-verbose same as '-debug-init'
-debug <tags> enable/disable debug messages
-debug-<tag> enable specific debug messages
-debug-no-<tag> disable specific debug messages
-help print this help
-help-<option> print option-specific help
-help-disk-images about disk images
-help-keys supported key bindings
-help-debug-tags debug tags for -debug <tags>
-help-char-devices character <device> specification
-help-environment environment variables
-help-keyset-file key bindings configuration file
-help-virtual-device virtual device management
-help-sdk-images about disk images when using the SDK
-help-build-images about disk images when building Android
-help-all prints all help content
2) Then, open a terminal (ctrl+alt+T) and type the following command in order to start you freshly created emulator with a bigger /system partition so we can push the su & busybox binaries :
Code:
emulator -avd yourNewAvdName -partition-size 256 -no-snapshot-load
Wait for the emulator to boot.
3) Now, cd to the directory where you put the binaries and the apk you downloaded in the prerequisities, and issue the following comands in your terminal :
Code:
adb shell mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
adb push su /system/xbin/su
adb push busybox /system/xbin/busybox
adb install Superuser.apk
adb shell
chmod 06755 /system/xbin/su
chmod 06755 /system/xbin/busybox
4) Enjoy your Rooted emulator
However, you might need to go through these steps every time you start this emulator, to avoid this hassle, here's a script containing those commands : rootavd.sh
Simply put it where you put the binaries, cd to this location and enter the following command to execute it :
Code:
bash rootavd.sh
...since many thanked you apparently it worked to many but why didn't it to me?
{
"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"
}
Why's this so? I've tried many similar guides, and it makes sense for this to work but it always shows the above (permision denied) and there's absolutely no other way to test applications that require root, for better or worse :/
Obviously I've followed the step it's not that it is hard to do so gave the right permissions but still no root?
Sth's on with the chmod commands?
Thanks for the guide and attention...
PS: It probably doesn't work in JellyBean'd AVD? :/
Stevethegreat said:
...since many thanked you apparently it worked to many but why didn't it to me?
Why's this so? I've tried many similar guides, and it makes sense for this to work but it always shows the above (permision denied) and there's absolutely no other way to test applications that require root, for better or worse :/
Obviously I've followed the step it's not that it is hard to do so gave the right permissions but still no root?
Sth's on with the chmod commands?
Thanks for the guide and attention...
PS: It probably doesn't work in JellyBean'd AVD? :/
Click to expand...
Click to collapse
Yeah, I believe it's been patched in jellybean.
However, you can use Jar of Beans, which is a community-built pre-rooted jb emulator.
Sadly it seems to be windows only. I'll post a guide if I manage to run it on linux through WINE
I know this is a little old of a post but i wanted to point out that i noticed a lot of people (when i was searching for a solution) having a hard time trying to get,
emulator -avd youravdhere -partition-size 256 -no-snapshot-load, to work correctly or not popup at all.
After a little research i noticed that you should add
./emulator to the first part instead of just "emulator"
hope this helps anyone. (credits goes to another person on another site i take no credit just spreading the knowledge)
kamakazidreamer said:
I know this is a little old of a post but i wanted to point out that i noticed a lot of people (when i was searching for a solution) having a hard time trying to get,
emulator -avd youravdhere -partition-size 256 -no-snapshot-load, to work correctly or not popup at all.
After a little research i noticed that you should add
./emulator to the first part instead of just "emulator"
hope this helps anyone. (credits goes to another person on another site i take no credit just spreading the knowledge)
Click to expand...
Click to collapse
You don't necessarily need that. As far as I know the only situation in which you might need this is on a Linux system. (Not sure about Mac)
And even in this case it depends. You can also add the tools directory to your PATH variable. Then you won't need it.
So not all people will need this but some definitely will. So thanks for that.
nikwen said:
You don't necessarily need that. As far as I know the only situation in which you might need this is on a Linux system. (Not sure about Mac)
And even in this case it depends. You can also add the tools directory to your PATH variable. Then you won't need it.
So not all people will need this but some definitely will. So thanks for that.
Click to expand...
Click to collapse
guess i should have pointed out i was using xubuntu to do all this haha.
Hello
Can you redownload files for rooting emulator?
I downloaded files from another source, but it doesn't work with it.
kolia2221 said:
Hello
Can you redownload files for rooting emulator?
I downloaded files from another source, but it doesn't work with it.
Click to expand...
Click to collapse
Can anyone help me?
Android L
Will this work on an Android L avd
i have nand backup generated from galaxy s2 . can i restore this backup on rooted avd s2
or virtual machine??
akhilnarang said:
Will this work on an Android L avd
Click to expand...
Click to collapse
I've had no luck so far, followed the guide but SuperSU tells me that "su is not present" and that "he cannot install it".
Anyone succeded in rooting a 5.0 AVD?
I am trying to get xposed framework going in remix os to get xprivacy. I am running remix os in virtualbox and I am having trouble getting adb set up. Remix os is similar to android x86 so has anyone been able to get xposed working in either remix os or android x86 marshmallow?

Guide: Simple sideload OTA update to KitKat

After seeing so many people get hung up on complicated guides to manually update to 4.4, I thought I'd write the simple guide during my next bout of insomnia. So, no sleep tonight for me means a new guide for you. It's very simple, with only four steps: 1) download the OTA update, 2) reboot into recovery, 3) prepare to sideload, and 4) sideload.
Preamble:
I use a Mac. My Nexus 7 2013 is WiFi only (flo). This guide is written from that perspective.
It's just as easy to do this from any computer you'd like (e.g. Linux, Mac, or Windows *see end of post*). The commands are exactly the same. The only difference is the way you install the android SDK (+/- USB drivers *see end of post*) and open a terminal or command prompt on your machine of choice. Learning this is simple and necessary for developing, hacking, rooting, unbricking on ANY ANDROID DEVICE.
Three things you need to have set up before starting
Other than being stock, the other items on this list are going to come in handy if you want to fully realize the potential of your nexus device, so take a minute and set it up if you haven't already.
1. NEXUS 7 2013, build number JSS15R, with STOCK ROM. The guide is written from the perspective of STOCK RECOVERY, but it's been done from TWRP (I swear to god). Yes, you can be any combination of rooted, unrooted, locked, unlocked, but if you're rooted, you should probably revert any changes you've made to system files before starting.
2. Up to date android platform tools from the SDK installed on your Mac:
http://developer.android.com/sdk/index.html
Note: the only platform tool you need to sideload is adb.
3. USB debugging enabled on your Nexus 7:
Settings, About tablet, tap build number a bunch of times to enable developer options, back out to settings, developer options, check USB debugging
THE ACTUAL GUIDE:.
STEP 1 (DOWNLOAD):
This is the second hardest step in this guide. You have to download the OTA, not the factory image, so, on your Mac, download this file: http://android.clients.google.com/p....signed-razor-KRT16O-from-JSS15R.3a3951e8.zip
STEP 2 (REBOOT INTO RECOVERY):
a. Hold the Power and Volume down buttons at the same time to enter fastboot mode.
b. Find and select "Recovery Mode" using the volume and power buttons
STEP 3 (PREPARE TO SIDELOAD):
a. Connect your N7 to your Mac with a USB cord
b. While in recovery mode, hold the power button and tap the volume up button (this is the hardest part of the guide).
c. Select "apply update from ADB"
STEP 4 (SIDELOAD):
a. Open a terminal window on your Mac and type "adb devices". Terminal will identify your nexus 7.
b. Type "adb sideload ". Don't forget the space.
c. Open a finder window and find the file you downloaded in step 1. Drag and drop it to your terminal window. Press enter.
VICTORY!
* Windows 8.1 x64 drivers, thanks to sahilcc7: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Command not found
xdhall said:
After seeing so many people get hung up on complicated guides to manually update to 4.4, I thought I'd write the simple guide during my next bout of insomnia. So, no sleep tonight for me means a new guide for you. It's very simple, with only four steps: 1) download the OTA update, 2) reboot into recovery, 3) prepare to sideload, and 4) sideload.
Preamble:
I use a Mac. My Nexus 7 2013 is WiFi only (flo). This guide is written from that perspective.
It's just as easy to do this from any computer you'd like (e.g. Linux, Mac, or Windows). The commands are exactly the same. The only difference is the way you install the android SDK (+/- USB drivers) and open a terminal or command prompt on your machine of choice. Learning this is simple and necessary for ANY developing, hacking, rooting, unbricking on ANY ANDROID DEVICE.
Three things you need to have set up before starting
Other than being stock, the other items on this list are going to come in handy if you want to fully realize the potential of your nexus device, so take a minute and set it up if you haven't already.
1. NEXUS 7 2013, build number JSS15R, with STOCK ROM. The guide is written from the perspective of STOCK RECOVERY, but it's been done from TWRP (I swear to god). Yes, you can be any combination of rooted, unrooted, locked, unlocked, but if you're rooted, you should probably revert any changes you've made to system files before starting.
2. Up to date android SDK installed on your Mac:
Follow instructions here: http://developer.android.com/sdk/index.html
3. USB debugging enabled on your Nexus 7:
Settings, About tablet, tap build number a bunch of times to enable developer options, back out to settings, developer options, check USB debugging
THE ACTUAL GUIDE:.
STEP 1 (DOWNLOAD):
This is the second hardest step in this guide. You have to download the OTA, not the factory image, so, on your Mac, download this file: http://android.clients.google.com/packages/data/ota/google_razor/3a3951e8243c82bc01a620ab858f4454c8ebd65c.signed-razor-KRT16O-from-JSS15R.3a3951e8.zip
STEP 2 (REBOOT INTO RECOVERY):
a. Hold the Power and Volume down buttons at the same time to enter fastboot mode.
b. Find and select "Recovery Mode" using the volume and power buttons
STEP 3 (PREPARE TO SIDELOAD):
a. Connect your N7 to your Mac with a USB cord
b. While in recovery mode, hold the power button and volume up button down (this is the hardest part of the guide).
c. Select "apply update from ADB"
STEP 4 (SIDELOAD):
a. In the terminal window on your Mac, type "adb sideload "
b. Open a finder window and find the file you downloaded in step 1. Drag and drop it to your terminal window. Press enter.
VICTORY!
Click to expand...
Click to collapse
I downloaded the SDK file for Mac and set up the Eclipse app. However I get a "Command Not Found" when I try to type into Terminal? I appreciate seeing instructions for a Mac; thank you.
Make sure you're connected with a microUSB. Type "adb devices" in terminal to verify that you're hooked up.
Sent from my Nexus 7 using Tapatalk 4
Also, be sure there's a space between the word sideload and the file name that shows up after you've dropped the zip onto the terminal window.
Sent from my Nexus 7 using Tapatalk 4
That's another problem I'm having my files automatically unzip. I'm looking to find out how to stop that from happening.
---------- Post added at 02:21 AM ---------- Previous post was at 02:12 AM ----------
Found the reason files unzipping and fixed. FIle is downloading again and I will try your suggestions. Thanks!
---------- Post added at 02:24 AM ---------- Previous post was at 02:21 AM ----------
Found the reason files unzipping and fixed. FIle is downloading again and I will try your suggestions. Thanks!
You can use Mini ADB and Fastboot Installer from xda too, just 2mb. I used it.
Sent from my Nexus 7 (2013)
bobng said:
That's another problem I'm having my files automatically unzip. I'm looking to find out how to stop that from happening.
---------- Post added at 02:21 AM ---------- Previous post was at 02:12 AM ----------
Found the reason files unzipping and fixed. FIle is downloading again and I will try your suggestions. Thanks!
Click to expand...
Click to collapse
In theory the first time you execute an adb command during a session in terminal you'll get the following echo:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Then it will execute your initial command.
I've added an adb devices command to the guide so if anyone reports a problem, they'll already know if they've been able to communicate across the microUSB cord.
Sent from my Nexus 7 using Tapatalk 4
I downloaded everything again and even though I deleted a program that aoto unzipped files the both unzipped. I connected the tablet and tried "adb Devices" and still returned -bash: adb: command not found
I've been at this for several hours. Google might even beat me with their installation at this rate.
bobng said:
I downloaded everything again and even though I deleted a program that aoto unzipped files the both unzipped. I connected the tablet and tried "adb Devices" and still returned -bash: adb: command not found
I've been at this for several hours. Google might even beat me with their installation at this rate.
Click to expand...
Click to collapse
I believe you're missing a step or so when installing sdk. You likely need to edit your profile. I couldn't readily find it on the Google site, but here's an independent guide: http://m.androidauthority.com/how-to-install-android-sdk-software-development-kit-21137/. I expect the part your missing begins with step 4 under "Installing on Mac OS X; Installing the Android SDK"
Sent from my Nexus 7 using Tapatalk 4
xdhall said:
I believe you're missing a step or so when installing sdk. You likely need to edit your profile. I couldn't readily find it on the Google site, but here's an independent guide: http://m.androidauthority.com/how-to-install-android-sdk-software-development-kit-21137/. I expect the part your missing begins with step 4 under "Installing on Mac OS X; Installing the Android SDK"
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Thanks, I rarely use Terminal so will have to read up some more to get this working.
bobng said:
Thanks, I rarely use Terminal so will have to read up some more to get this working.
Click to expand...
Click to collapse
I should be able to walk you through it tomorrow.
Sent from my Nexus 7 using Tapatalk 4
Thanks, guide worked great. Just the part where you select adb sideload - maybe state that you should hold power and tap vol up to select it. I got stuck there.
And for those with Windows 8.1 x64: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Those drivers worked.
bobng said:
Thanks, I rarely use Terminal so will have to read up some more to get this working.
Click to expand...
Click to collapse
Basically you need to tell terminal where to find the bits of the various SDK programs by editing your bash profile. This is how terminal knows what you mean when you ask it to execute an adb or fastboot command. Let me simplify from the androidauthority guide. It takes three lines of code.
Open up a terminal window and execute the following:
Step 1: This step lets you edit the profile that tells terminal where to find executable binary files
Type and press enter:
Code:
vi ~/.bash_profile
Step 2: The step actually edits said profile
Type but don't press enter:
Code:
export PATH=$PATH:
Open a Finder window and find the folder "platform-tools" in the sdk folder (make sure you've put your sdk folder wherever you want it to live--if you move it later, terminal won't be able to find it). Drag and drop the folder on the terminal window. This time you DON'T want a space between the typed code and the file path.
Now press enter.
Step 3: This step saves your changes
Type and press enter:
Code:
source $HOME/.bash_profile
From now on, whenever you open a terminal window, you'll be able to use your sdk tools.
sahilcc7 said:
Thanks, guide worked great. Just the part where you select adb sideload - maybe state that you should hold power and tap vol up to select it. I got stuck there.
And for those with Windows 8.1 x64: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Those drivers worked.
Click to expand...
Click to collapse
Updated OP with the recommended tweak to the language and the link to the drivers. Thanks!
Sent from my Nexus 7 using Tapatalk 4
This worked for me without issue. I only had to install the proper drivers and after that it went smooth.
I tried your suggestion and as you can see Step 1 wasn't successful but I tried the rest the result is as follows:
Last login: Mon Nov 18 21:56:38 on ttys000
Bobs-Retina:~ bobng$ vi -/.bash_profile
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Aug 24 2013 18:58:47)
Unknown option argument: "-/.bash_profile"
More info with: "vim -h"
Bobs-Retina:~ bobng$ vi-/.bash_profile
-bash: vi-/.bash_profile: No such file or directory
Bobs-Retina:~ bobng$ vim -h
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Aug 24 2013 18:58:47)
usage: vim [arguments] [file ..] edit specified file(s)
or: vim [arguments] - read text from stdin
or: vim [arguments] -t tag edit file where tag is defined
or: vim [arguments] -q [errorfile] edit file with first error
Arguments:
-- Only file names after this
-v Vi mode (like "vi")
-e Ex mode (like "ex")
-s Silent (batch) mode (only for "ex")
-d Diff mode (like "vimdiff")
-y Easy mode (like "evim", modeless)
-R Readonly mode (like "view")
-Z Restricted mode (like "rvim")
-m Modifications (writing files) not allowed
-M Modifications in text not allowed
-b Binary mode
-l Lisp mode
-C Compatible with Vi: 'compatible'
-N Not fully Vi compatible: 'nocompatible'
-V[N][fname] Be verbose [level N] [log messages to fname]
-D Debugging mode
-n No swap file, use memory only
-r List swap files and exit
-r (with file name) Recover crashed session
-L Same as -r
-T <terminal> Set terminal type to <terminal>
-u <vimrc> Use <vimrc> instead of any .vimrc
--noplugin Don't load plugin scripts
-p[N] Open N tab pages (default: one for each file)
-o[N] Open N windows (default: one for each file)
-O[N] Like -o but split vertically
+ Start at end of file
+<lnum> Start at line <lnum>
--cmd <command> Execute <command> before loading any vimrc file
-c <command> Execute <command> after loading the first file
-S <session> Source file <session> after loading the first file
-s <scriptin> Read Normal mode commands from file <scriptin>
-w <scriptout> Append all typed commands to file <scriptout>
-W <scriptout> Write all typed commands to file <scriptout>
-x Edit encrypted files
--startuptime <file> Write startup timing messages to <file>
-i <viminfo> Use <viminfo> instead of .viminfo
-h or --help Print Help (this message) and exit
--version Print version information and exit
Bobs-Retina:~ bobng$ -v -/.bash_profile
-bash: -v: command not found
Bobs-Retina:~ bobng$ export PATH=$PATH:/Users/bobng/Downloads/adt-bundle-mac-x86_64-20131030/sdk/platform-tools
Bobs-Retina:~ bobng$ source $HOME/.bash_profile
-bash: /Users/bobng/.bash_profile: No such file or directory
Bobs-Retina:~ bobng$
I just upgraded to Mavericks, not sure if that makes a difference?
bobng said:
I tried your suggestion and as you can see Step 1 wasn't successful but I tried the rest the result is as follows:
Last login: Mon Nov 18 21:56:38 on ttys000
Bobs-Retina:~ bobng$ vi -/.bash_profile
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Aug 24 2013 18:58:47)
Unknown option argument: "-/.bash_profile"
More info with: "vim -h"
Bobs-Retina:~ bobng$ vi-/.bash_profile
-bash: vi-/.bash_profile: No such file or directory
Bobs-Retina:~ bobng$ vim -h
I just upgraded to Mavericks, not sure if that makes a difference?
Click to expand...
Click to collapse
You're using a hyphen where you need a tilda.
You typed: vi -/.bash_profile
It should be: vi ~/.bash_profile
vi space tilda forward slash period bash underscore profile
It might help to copy and paste the code from my post directly into terminal.
Thanks again, I see that it is a tilda now. I appreciate you sticking with me.
---------- Post added at 01:15 AM ---------- Previous post was at 01:00 AM ----------
OK, I got in trouble again. When I did Step 2 I got a message abowut not being found. I tried to copy and somehow moved it and couldn't get a prompt. So I tried to shut down and start over, not a good idea. Here is where I am now:
Bobs-Retina:~ bobng$ vi ~/.bash_profile
E325: ATTENTION
Found a swap file by the name "~/.bash_profile.swp"
owned by: bobng dated: Tue Nov 19 19:04:46 2013
file name: ~bobng/.bash_profile
modified: YES
user name: bobng host name: Bobs-Retina.local
process ID: 20981
While opening file "/Users/bobng/.bash_profile"
(1) Another program may be editing the same file.
If this is the case, be careful not to end up with two
different instances of the same file when making changes.
Quit, or continue with caution.
(2) An edit session for this file crashed.
If this is the case, use ":recover" or "vim -r /Users/bobng/.bash_profile"
to recover the changes (see ":help recovery").
If you did this already, delete the swap file "/Users/bobng/.bash_profile.sw
p"
to avoid this message.
Swap file "~/.bash_profile.swp" already exists!
[O]pen Read-Only, (E)dit anyway, (R)ecover, (D)elete it, (Q)uit, (A)bort:
bobng said:
Thanks again, I see that it is a tilda now. I appreciate you sticking with me.
---------- Post added at 01:15 AM ---------- Previous post was at 01:00 AM ----------
OK, I got in trouble again. When I did Step 2 I got a message abowut not being found. I tried to copy and somehow moved it and couldn't get a prompt. So I tried to shut down and start over, not a good idea. Here is where I am now:
Bobs-Retina:~ bobng$ vi ~/.bash_profile
E325: ATTENTION
Found a swap file by the name "~/.bash_profile.swp"
owned by: bobng dated: Tue Nov 19 19:04:46 2013
file name: ~bobng/.bash_profile
modified: YES
user name: bobng host name: Bobs-Retina.local
process ID: 20981
While opening file "/Users/bobng/.bash_profile"
(1) Another program may be editing the same file.
If this is the case, be careful not to end up with two
different instances of the same file when making changes.
Quit, or continue with caution.
(2) An edit session for this file crashed.
If this is the case, use ":recover" or "vim -r /Users/bobng/.bash_profile"
to recover the changes (see ":help recovery").
If you did this already, delete the swap file "/Users/bobng/.bash_profile.sw
p"
to avoid this message.
Swap file "~/.bash_profile.swp" already exists!
[O]pen Read-Only, (E)dit anyway, (R)ecover, (D)elete it, (Q)uit, (A)bort:
Click to expand...
Click to collapse
Delete the swap file by executing the following:
Code:
rm -r ~/.bash_profile.swp
Don't forget the ".swp" at the end
Then start again
Here's what I did, I downloaded the the full image, some 400mb to
File i found in the forums here, I then rebooted into twrp, and installed from zip.
Boom.
All my apps were ok apart from the browser. I'm on 4.4, have new kit Kat features etc. Other than that, how do I know if I did it right?
Sent from my Nexus 7 using xda app-developers app

[Q] Internal Memory data recovery

[email protected] /cygdrive/c/Users/user/Desktop
$ adb forward tcp:5555 tcp:5555
bash: adb: command not found
[email protected] /cygdrive/c/Users/user/Desktop
$ adb shell
bash: adb: command not found
[email protected] /cygdrive/c/Users/user/Desktop
$ /system/bin/busybox nc -l -p 5555 -e /system/bin/busybox dd if=/dev/block/mmcblk0p12
Can you help ? when i paste this command(adb forward tcp:5555 tcp:5555
adb shell
/system/bin/busybox nc -l -p 5555 -e /system/bin/busybox dd if=/dev/block/mmcblk0p12) on cgywin this what happens.
i really want my phone's internal memory back. it's taken from this guide : http://forum.xda-developers.com/gala...y-yes-t1994705 +,when he says to open another terminal ,he means another window of cygwn not just the one i am using ?
i Really need your advice. i want to recover every kind of data from before the format. adb is installed ,nc is in the folder it's suppose to be ,busybox and the other app installed on my device. all are set in their place.
im on my pc win 7 downloaded and did what is on the guide...
+what does it mean connect your phone in adb mode and unlock the screen ? i connent my phone normally through usb and my adb detects my phone in the list in the commmand prompt and thats all ...
is there a mode i am suppose to be into while accessing my phone through usb cable from my pc ?
EDIT : i saw a guide about it,i try now ...
Are you on Android 4.3+? If so, don't waste your time. That method doesn't work anymore when you have deleted your files.
Lennyz1988 said:
Are you on Android 4.3+? If so, don't waste your time. That method doesn't work anymore when you have deleted your files.
Click to expand...
Click to collapse
4.1.2
Dorpwnz said:
4.1.2
Click to expand...
Click to collapse
Ok then it should work. What's your question? It's not very clear in your first post.
Lennyz1988 said:
Ok then it should work. What's your question? It's not very clear in your first post.
Click to expand...
Click to collapse
Im in the stage where it says "pv command not found nc command not found" and creates only a 0 bytes file on my directory right now .
using the "improved" guide [it really made some things clear] http://forum.xda-developers.com/galaxy-s4/general/guide-internal-memory-data-recovery-t3093292
+ p.s ,doest it matter if my first terminal says "adb server is out of date.,killing...
deamon succesful!
or it doesnt matter that much
because honestly ,all i get is bash: pv command not found and bash : nc command not found together in the same prompt like this :
bash: pv command not found
bash: nc: command not found and i need to put adb forward tcp:5555 tcp:5555
cd /samsung
nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p10.raw and click enter to get them . and all i get in the end is a 0 byte file
p.s , i have nc.exe in bin and also pv ... so what could be the problem
i copy past t adb forward tcp:5555 tcp:5555
cd /samsung from notepad in order to do this. if i write it down manually by hand all i get is "permission denied" message without even an 0 byte file. nothing at all...
Dorpwnz said:
Im in the stage where it says "pv command not found nc command not found" and creates only a 0 bytes file on my directory right now .
using the "improved" guide [it really made some things clear] http://forum.xda-developers.com/galaxy-s4/general/guide-internal-memory-data-recovery-t3093292
+ p.s ,doest it matter if my first terminal says "adb server is out of date.,killing...
deamon succesful!
or it doesnt matter that much
because honestly ,all i get is bash: pv command not found and bash : nc command not found together in the same prompt like this :
bash: pv command not found
bash: nc: command not found and i need to put adb forward tcp:5555 tcp:5555
cd /samsung
nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p10.raw and click enter to get them . and all i get in the end is a 0 byte file
p.s , i have nc.exe in bin and also pv ... so what could be the problem
i copy past t adb forward tcp:5555 tcp:5555
cd /samsung from notepad in order to do this. if i write it down manually by hand all i get is "permission denied" message without even an 0 byte file. nothing at all...
Click to expand...
Click to collapse
Use this thread for reference:
http://forum.xda-developers.com/gal...de-internal-memory-data-recovery-yes-t1994705
Read the last pages and search for that question in there. I can remember it's been discussed lot's of times in that thread.
ps you did follow this part?
"Cygwin installed to [c:\cygwin] with pv and util-linux from the repo (at the package selection screen search for pv then util-linux and click on Default to change it to Install)."
and you have to have the x86 version NOT the x64 version.
Lennyz1988 said:
Use this thread for reference:
http://forum.xda-developers.com/gal...de-internal-memory-data-recovery-yes-t1994705
Read the last pages and search for that question in there. I can remember it's been discussed lot's of times in that thread.
ps you did follow this part?
"Cygwin installed to [c:\cygwin] with pv and util-linux from the repo (at the package selection screen search for pv then util-linux and click on Default to change it to Install)."
and you have to have the x86 version NOT the x64 version.
Click to expand...
Click to collapse
with pv and linux from the repo . i dont know what it means but in the package selection i've searched for pv and after that util linux but i had to install both debug,base and utils because every time i searched for pv and changed to install and after that searched util-linux and changed to install i had to notice that if i search pv again i will find it in "default" mode.
p.s my cygwin is x86 even the setup file is called like that.
oh and in one phrase of the guide i have sent you (the "improved" one):
19. Right-click on the RAW space and select Format... MAKE SURE to change the File system to FAT32. Set the Allocation unit size dropdown to 'Default.' MAKE SURE that the Perform a quick format checkbox is CHECKED. You do not want to overwrite the entire new drive with all zeroes (0's) and destroy your data. Quick Format means that it will only attempt to destroy the index for the drive by establishing a new index. Without this box checked the Windows operating system will write zeroes (0's) across the entire volume, potentially destroying your data. Select the OK button.
what is the point ? in the middle of the proccess i will have to format my NTFS drive and all the date i personally have in there will be lost.
Lennyz1988 said:
Use this thread for reference:
http://forum.xda-developers.com/gal...de-internal-memory-data-recovery-yes-t1994705
Read the last pages and search for that question in there. I can remember it's been discussed lot's of times in that thread.
ps you did follow this part?
"Cygwin installed to [c:\cygwin] with pv and util-linux from the repo (at the package selection screen search for pv then util-linux and click on Default to change it to Install)."
and you have to have the x86 version NOT the x64 version.
Click to expand...
Click to collapse
Now if i write adb forward tcp:5555 tcp:5555
cd /samsung
nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p10.raw manually by hand instead of permission denied it says pv command not found ,wierd.
Did you download pv and util-linux from WITHIN cygwin? You have to select it during the installation of cygwin.
Lennyz1988 said:
Did you download pv and util-linux from WITHIN cygwin? You have to select it during the installation of cygwin.
Click to expand...
Click to collapse
in the search option i search for one of the packages , change from default to install.
when i search the second package [for example util linux,and the first one pv] i change the second package from default to install.
But,when i check if everything is alright by searching the first one again, i notice that it changed back to defualt! like i didnt change it to install a second before.
anyway,when i check in the folder, i see the files appear in there.
edit : in cygwin folder, i cant see a file called util-linux in it's bin folder,if it's okay.
okay i have fixed the misunderstanding with the cygwin search using a video.
okay, still $ nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p10.raw
bash: nc: command not found
bash: pv: command not found
in https://www.youtube.com/watch?v=Mwn20Udp5YA&feature=iv&src_vid=HomqBx0J0e8&annotation_id=annotation_583506
3:07 part of the video. sucks.
okay ,still $ nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p10.raw
bash: nc: command not found
bash: pv: command not found
in 3:07 part of the video
Sucks.
Dorpwnz said:
okay ,still $ nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p10.raw
bash: nc: command not found
bash: pv: command not found
in 3:07 part of the video
Sucks.
Click to expand...
Click to collapse
You sure you installed it to [c:\cygwin] ?
Lennyz1988 said:
You sure you installed it to [c:\cygwin] ?
Click to expand...
Click to collapse
Yup
{
"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"
}
i navigated to samsung (my folder where the vhdtool is) in cygwin and then did the command ($ nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p10.raw)
nc is at bin in cygwin where it should be . util-linux and pv are installed as it gave me their utils and debug to install in the cygwin search in the cygwin setup and all is fine.
im just stuck here and cant make any transfare..
Dorpwnz said:
Yup View attachment 3415018
i navigated to samsung (my folder where the vhdtool is) in cygwin and then did the command ($ nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0p10.raw) View attachment 3415023
nc is at bin in cygwin where it should be . util-linux and pv are installed as it gave me their utils and debug to install in the cygwin search in the cygwin setup and all is fine.
im just stuck here and cant make any transfare..
Click to expand...
Click to collapse
You also selected NC when installing cygwin?
Lennyz1988 said:
You also selected NC when installing cygwin?
Click to expand...
Click to collapse
no , i just downloaded it manually and put in in the bin ... like the guide says
Dorpwnz said:
no , i just downloaded it manually and put in in the bin ... like the guide says
Click to expand...
Click to collapse
Try to install it directly from the cygwin setup.

Categories

Resources