Related
So I been bored and making videos.
I got more on the way but here are some I have now
install the sdk and add it to your system path and adb drivers for windows 7 here
Install android sdk and add it to your system path and htc drivers ubuntu here
Root the latest sprint update here
Sign an update zip in ubuntu here
Install the gingerbread version of android sdk and fix it also some adb commands here
Extract a kernel and ramdisk from boot.img edit the ramdisk and then recompile and flash to your phone here
Extract rom.zip from a ruu here
How to make/sign update zip and add java to your path windows 7 here
How to turn a system image into a custom rom here
how to install adw theme/make adw backup/restore all apps button here
how to upload roms, themes files in general for free no waiting period no ads here
How to install the htc diag drivers here
How to turn a video into a bootanimation here
How to flash a custom rom and make a nandroid backup here
If you got any requests then let me know and I'll try to make it happen
just taking the first spot and saving it for some downloads i gotta post
unyaffs batch here
flash_image, recovery image and patched boot.img here
makebootfs/makebootimg and perl scripts here
htc diag drivers here
The following are some scripts for the installing sdk/eclipse in linux video
installsdk script
Code:
## add necessary repository
sudo add-apt-repository ppa:ferramroberto/java
sudo apt-get update
mkdir -p ~/android
sudo mv 51-android.rules /etc/udev/rules.d
## install java cuz it's needed
sudo apt-get install sun-java6-jre sun-java6-plugin sun-java6-fonts sun-java6-jdk eclipse
## download sdk you may choose older versions if you like by changing the 14 to 13 or whatever floats your boat
wget http://dl.google.com/android/android-sdk_r15-linux.tgz
tar -zxvf android-sdk_r15-linux.tgz
mv 'android-sdk-linux' ~/android/sdk
## make temp directory to give it permissions before anything is there
mkdir -p ~/android/sdk/platform-tools
## add the platform-tools and tools to bashrc
echo 'export PATH="~/android/sdk/tools:${PATH}"' >> ~/.bashrc
echo 'export PATH="~/android/sdk/platform-tools:${PATH}"' >> ~/.bashrc
printf ALL DONE WITH THIS
exit
51-android.rules
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="618e", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="d00d", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", SYMLINK+="android_adb", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="d00d", SYMLINK+="android_adb", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="413c", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0489", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="091E", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0482", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0955", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="10A9", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="04dd", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="19D2", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0451", MODE="0666"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{PRODUCT}=="e79/*", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="e79", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="0e79", MODE="0666"
Just wanna say thanks, these can and will come in handy!
Thread stuck as requested.
Can you do one on installing and theming adw?
abadasstanker69 said:
Can you do one on installing and theming adw?
Click to expand...
Click to collapse
Do you mean making an adw theme? Or just applying one to adw? I can do the first but the second I can ask JAguirre1231 (he made the sense themes) He's pretty cool so he might.
Videos are great but Audio quality is very bad
First, thanks for sharing what you have thus far. Are you aware of anyone that has built a virtual machine for android development? I'm looking for a VMWare vm, but would use a Virtual Box image, as well.
atmchuck said:
First, thanks for sharing what you have thus far. Are you aware of anyone that has built a virtual machine for android development? I'm looking for a VMWare vm, but would use a Virtual Box image, as well.
Click to expand...
Click to collapse
I built a virtual box in windows 7 awhile back but got rid of it and installed ubuntu is that what your looking for.
Not sure if its your area of expertise or not, but a video on .9.png edits for theming would be very helpful.
Thanks for all youve posted so far too!
Yes, a vm with the tools already installed would be cool for me. I'm a MSFT dev during the day, and our dev team uses VPC extensively for dev. As our dev env evolves/upgrades, this makes it easy to go back and patch prior versions.
It sounds like there isn't anything out there for VMWare (which is my preferred target). So, I'll start from scratch and see how far I get. If you have a Virtual Box image of Ubuntu that you'd be willing to share, that would be helpful.
And, sorry for not replying sooner. I did not have email notify turned on for thread responses. I'll be quicker to reply in the future. Again, thanks for any and all help, I do appreciate it.
atmchuck said:
Yes, a vm with the tools already installed would be cool for me. I'm a MSFT dev during the day, and our dev team uses VPC extensively for dev. As our dev env evolves/upgrades, this makes it easy to go back and patch prior versions.
It sounds like there isn't anything out there for VMWare (which is my preferred target). So, I'll start from scratch and see how far I get. If you have a Virtual Box image of Ubuntu that you'd be willing to share, that would be helpful.
And, sorry for not replying sooner. I did not have email notify turned on for thread responses. I'll be quicker to reply in the future. Again, thanks for any and all help, I do appreciate it.
Click to expand...
Click to collapse
I'm currently working on the .9 png tutorial. I'm probably going to have to do the virtual box at a later time just because there's so much into it and if I end up messing up my machine right now I'm screwed but I'm going to eventually get to it probably before the end of the month
np. I realize I'm off topic here. Thanks for the reply; I'm working on setting up a vm now. pm me if you are interested in taking a look.
atmchuck said:
np. I realize I'm off topic here. Thanks for the reply; I'm working on setting up a vm now. pm me if you are interested in taking a look.
Click to expand...
Click to collapse
Your definitely not off topic and virtual box is probably one of those things that everyone who devs will probably get unless they dualboot. I might even make a video on how I set up ubuntu from a fresh start. It's definitely dev related.
nice
There are already pre-made images ('appliances') on the net for both vmware and virtualbox.
vmware:
http://www.vmware.com/appliances/
virtualbox:
http://www.google.com/search?sclien...tualbox+images&aq=f&aqi=g10&aql=&oq=&gs_rfai=
sirmx said:
There are already pre-made images ('appliances') on the net for both vmware and virtualbox.
vmware:
http://www.vmware.com/appliances/
virtualbox:
http://www.google.com/search?sclien...tualbox+images&aq=f&aqi=g10&aql=&oq=&gs_rfai=
Click to expand...
Click to collapse
Sirmx,
Thanks for the reply. I'm currently using VMWare. But, the support for my Win7 dev is awful, so I may just switch to the Virtual Box. I just read a review of the latest release fo VB, and it looks pretty nice.
My biggest question(s) will not be so much with the VM, and more with the dev environment. I'd love to hear what other Android developers (App devs, not rom devs) are using for tools. I would guess that Eclipse and the Android SDK are requirements. But, beyond that, I really don't know. Any feedback on tools (and their versions) is appreciated.
Edit: sirmx, again, thanks for the links. I found a VirtualBox virtual machine here that I've started to use. Easy, peasy, lemon squeezy! I'll look (again) for a thread here that addresses VMs and development. I may go ahead and start one, as I think it could be helpful.
Well guys two good things happened lately and I got a virgin mobile optimus v (it rocks) and I got a job. So my time is not what it used to be. You've probably noticed or not. But I'm going into the optimus v development I'll still be making videos when I have the time or need to.....but it's not looking good right now.
If anyone has any videos they want to post on the front page send me a pm and I'll hook it up
[B]SOLVED[/B]ok made afew mistakes
[SOLVED]so I didnt rename sdk folder and in the bash file i put () instead of {} and now i dont have permissions to the home folder or the bash.bashrc so what do i do?? when i open term to gain root it comes up with
"bash: PATH: command not found
Command 'lesspipe' is available in the following places
* /bin/lesspipe
* /usr/bin/lesspipe
The command could not be located because '/usr/bin:/bin' is not included in the PATH environment variable.
lesspipe: command not found
Command 'dircolors' is available in '/usr/bin/dircolors'
The command could not be located because '/usr/bin' is not included in the PATH environment variable.
dircolors: command not found
Command 'uname' is available in '/bin/uname'
The command could not be located because '/bin' is not included in the PATH environment variable.
uname: command not found
bash: [: !=: unary operator expected
bash: [: too many arguments
bash: [: too many arguments
bash: [: too many arguments
bash: [: =: unary operator expected
bash: [: too many arguments
bash: [: too many arguments
bash: [: =: unary operator expected
bash: [: =: unary operator expected
bash: [: =: unary operator expected
bash: [: =: unary operator expected
bash: [: =: unary operator expected
Command 'sed' is available in '/bin/sed'
The command could not be located because '/bin' is not included in the PATH environment variable.
sed: command not found
bash: [: too many arguments
bash: [: =: unary operator expected
bash: [: too many arguments
bash: [: too many arguments
bash: [: =: unary operator expected
bash: [: =: unary operator expected
bash: [: =: unary operator expected
bash: [: =: unary operator expected
[email protected]:~$ "
when i type gksu nautilus to gain root through nautilus it follows .
[email protected]:~$ gksu nautilus
Command 'gksu' is available in '/usr/bin/gksu'
The command could not be located because '/usr/bin' is not included in the PATH environment variable.
gksu: command not found
[email protected]:~$
this is what ive changed bash.bashrc to #AndroidDEV PATH
export PATH=$(PATH):/home/androidsdk/tools Notice there are Less pipes instead of {PATH}
so im stuck with this current dilema of how to gain root ive tried -i and comes up with the same error with any input command since the bash.bashrc is invalid and rooted to terminal?
now my question is i do not have a restore point nor do i have anyway of gaining root unless you know of another way?
EDIT: Installed Gksu-nautilus from software center and opened as administrator fixed errors and fixed
Asadullah said:
So I been bored and making videos.
I got more on the way but here are some I have now
install the sdk and add it to your system path and adb drivers for windows 7 here
Install android sdk and add it to your system path and htc drivers ubuntu here
Root the latest sprint update here
Sign an update zip in ubuntu here
Install the gingerbread version of android sdk and fix it also some adb commands here
Extract a kernel and ramdisk from boot.img edit the ramdisk and then recompile and flash to your phone here
Extract rom.zip from a ruu here
How to make/sign update zip and add java to your path windows 7 here
How to turn a system image into a custom rom here
how to install adw theme/make adw backup/restore all apps button here
how to upload roms, themes files in general for free no waiting period no ads here
How to install the htc diag drivers here
How to turn a video into a bootanimation here
How to flash a custom rom and make a nandroid backup here
If you got any requests then let me know and I'll try to make it happen
Click to expand...
Click to collapse
Thanks a Million for these!!
Sent from my Hero using XDA App
Hi,
I found several ways to access the files of a Xoom via MTP from a Linux (in my case Ubuntu 11.04) machine. The most comvenient seems to be gphoto2 way with gvfs. To do this, you need to have the following UDEV rules:
ATTRS{idVendor}=="22b8", ATTRS{idProduct}=="70a8", ENV{ID_MEDIA_PLAYER}="1", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1", ENV{ID_MTP_DEVICE}="1", MODE="0664", GROUP="audio"
ATTRS{idVendor}=="22b8", ATTRS{idProduct}=="70a9", ENV{ID_MEDIA_PLAYER}="1", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1", ENV{ID_MTP_DEVICE}="1", MODE="0664", GROUP="audio"
Click to expand...
Click to collapse
When you plug in your device, it is recognized and mounted automatically. Unfortunately, there is one major problem: I _can_ upload files to the device, but _not_ see them after that. I can perfectly see and browse the directory structure, but I will never see a file. I know the file is there as Android can see it, but from Linux's point of view it is not there.
Does any have experience with this and have a solution?
For the moment, I decided to use the mtpfs way - but I'd prefer the integrated automated way. I myself can live very well with typing commands to mount and unmount the device, but other people probably can't
cheers
mathiase
Hello everyone at xda !
As a newcomer I was searching for a bit of help getting started with android tools and its development.
So I decided to help out the newcomers a bit more by creating this thread..
I found this to be essential for our HTC Explorer Development Forum
This guide contains :
Post 1:
Info about SDK / ADB and how to install them on linux and windows.
Logcat- How to logcat , types of logcats , meaning
Adb wireless
Post 2:
Clean install
Paritioning sd
Flashing kernel , recovery
Permissions
What is overclocking ?
Recover from OC
md5 checksum
Post 3:
Video tuts and credits.
Info about ADB/SDK :
ADB
What is adb ?
Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device. It is a client-server program that includes three components:
A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
A daemon, which runs as a background process on each emulator or device instance.
SDK
What is android SDK ?
Android software development is the process by which new applications are created for the Android operating system. Applications are usually developed in the Java programming language using the Android Software Development Kit, but other development tools are available. As of October 2012, more than 700,000 applications have been developed for Android, with over 25 billion downloads.The Android platform has also grown to become a favorite among mobile developers.
Want to download and use adb and SDK ( its in one package )?
Visit http://developer.android.com/sdk/index.html
Extract the files of the package you downloaded from the site as whatever you want to but remember it ?
Windows Specific (VISTA)
Keep your path name to which is extracted to
Eg : C:\(*package-name*) [ eg of package name : adt-bundle-windows-x86 ]
Rename the Folder to C:\(*Whatever you want to name it*) [ eg change "adt-bundle-windows-x86" to "android" ]
In order to run adb do the following steps :
Click start
Search for cmd
Right click and * RUN AS ADMINISTRATOR *
type the following commands
Code:
C:\Windows\system32\>cd C:\android*\sdk\platform-tools\ [*click enter*]
C:\android*\sdk\platform-tools>adb
C:\android*\sdk\platform-tools>adb devices
Now you should get a huge code block with all the adb commands
That means adb has been installed correctly.
adb devices gives you the list of attached adb devices and if their permissions are right..
Setting up ADB as a command on Windows 7/ Vista
Assuming you have done the above steps correctly you should have no problem going ahead
Right click on Computer
Click on properties
Go the advanced system settings
Click on the advanced tab
Go to Enviornmental variables in the dialog box
In system variables find the variable " Path ".
Double click on it and in variable value add the following line at the end of it :
Code:
;C:\android\sdk\platform-tools\;
Click on OK etc and save the settings
now Run command prompt
Type adb and your adb commands will be in function..
You can now run adb as a command and dont need to go to the directory every time.
Linux Specific ( Ubuntu )
PS (important) if someone has a 64bit linux then they need to download 32bit libs
for this, before all these steps run this
Code:
sudo apt-get install ia32-libs
You should have an updated JDK for this.. Just in case..
Code:
$ sudo add-apt-repository ppa:sun-java-community-team/sun-java6
$ sudo apt-get update
$ sudo apt-get install sun-java6-jre sun-java6-bin sun-java6-jdk
we need to make a new directory by this command
Code:
mkdir android
then extract by
Code:
tar -zxvf ~/Downloads/android-sdk_r21.0.1-linux.tgz
then move it to the directory we just made
Code:
mv android-sdk-linux ~/android/sdk
the open android sdk manager by
Code:
android/sdk/tools/android
this will open android sdk manager
we need to select just android sdk tools and android sdk platform tools for adb and then select install packages
^^this will download everything required
then we need to set a path to include adb
Code:
gedit .bashrc
and then a file opens and paste this text in that file
Code:
export PATH=${PATH}:~/android/sdk/platform-tools
then we make the above bashrc file executable by this
Code:
chmod a+x .bashrc
then we need to setup device rules and make that file executable
ps sample is the username
Code:
]sudo gedit /etc/udev/rules.d/51-android.rules
and copy and paste this
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="413c", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0489", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="091E", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="10A9", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="04dd", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="19D2", MODE="0666"
and then make rules executable by:
Code:
sudo chmod a+x /etc/udev/rules.d/*
we need to add full path to adb start server
Type :
Code:
sudo gedit /etc/rc.local
this will open a file
now add this line just above where it is written exit 0
Code:
/home/sample/android/sdk/platform-tools/adb start-server
"sample is username"
after this we dont need to cd to adb directory..we can just type adb devices and the phone will surely show up
Guide for Linux by Gnexus. Thank him Here!
Now we have a blooming xda forum at HTC Pico aka Explorer with :
Cyanogen mod 7
Cyanogenmod 9
Cyanogenmod 10
Cyanogenmod 10.1
Sense 3.5(stock)
Sense 4.0
Which is quite a lot considering our device is considered as
A legacy / low activity device
Click to expand...
Click to collapse
Now with all those ROMs come their respective bugs..
Just saying
" Random reboot "
" I dont know but xyz doesnt work "
" Xyz fces "
Click to expand...
Click to collapse
Gives just another burdening job for a ROM dev of trying to find that same mistake and trying to take a log of it..
At times they are on a different ROM and it becomes difficult for them to flash their old ROMs again..
Sometimes they dont even have the same device !!
So.. Try to ease the job of the dev by bringing whats called a logcat so you can do the following to help them out :
You should have installed adb and fastboot by now
For getting a logcat you should do the following easy steps
Connect phone to pc / laptop ( quite obviously )
Assuming you have rooted your phone you should have required drivers installed ?
To enable ADB mode on your phone go to settings > developer options > Debugging > USB Debugging > ON
1st go to cmd and run as administrator and go to the root of adb
simply type
Code:
C:\android*\sdk\platform-tools>adb logcat
and you get a logcat running on your screen
Want to post a logcat somewhere ?
1] A logcat that can be easily copy pasted and given to someone else :
to do that type :
Code:
adb logcat > cat.txt
*cat is just an example .. it can be Anything logcat.txt, catlog.txt, etc ( let your imagination go wild )
This gives you a logcat at the platform-tools folder .
Now if you get your logcat you can post the logcat somewhere in the dev threads as a whole logcat or you can put specific lines where you want the dev to look at or you know the error is present. There is a character number limitation on a single post on xda for which you can simply upload the .txt file or you can also post it on Pastebin and share the link/url on the thread. This helps a lot .
Alternatively there are apps such as aLogcat or Catlog but installing adb and fastboot is essential as it will not only help you with this but other functions also look further down..
Meanings of symbols in a logcat !
You usually see this at the start of a sentence in logcat .
I/> ===> Information
S/> ===> Silent
D/> ===> Debug
W/> ===> Warning
E/> ===> Error
F/> ===> Fatal
For more information about logcats
Help with solving a logcat from fellow members only for pico !
DMESG (*Useful for devs / beta testers alike*)
Go to your adb directory via terminal / cmd on admin privileges
Type
Code:
adb shell dmesg > dmesgLOG.txt
Terminal emulator :
Code:
dmesg > /sdcard/dmesglog.txt
DMESG is useful for finding out errors / bugs in the hardware aspects caused due to software issues and kernel issues (* eg : deepsleep , bluetooth not working , wifi not working etc . *) which cannot sometimes be easily solved through a simple logcat.
Lastly K-MESG
To help solving with respect to kernels (* Yes it is a kernel not kernal... *)
Kernel issues like a kernel panic and similar. Similar steps to dmesg but the code is
Code:
adb shell cat /proc/last_kmsg > kmsg.txt (*via adb*)
cat /proc/last_kmsg > /sdcard/last_kmsg.txt (*via terminal emulator*)
ADB wirelessly
To use adb via Wi-Fi
Download this wonderful app from the playstore adbWireless
Click on the green button and an IP will come on the app screen. (* eg: 123.456.7.890 *)
On your computer go to your adb directory via terminal / cmd prompt
type
Code:
adb connect 123.456.7.890
Voila! You are using adb wirelessly
Some useful extra stuff !
Adb guide
Note : Please do not quote the entire first post in the replies !
Some other essential guides.
What do you mean by a clean install ?
WARNING ! : Do NOT wipe/format External storage . This will result in the loss of data.
A clean install can be done as follows :
On CWM / Yannou's recovery :
Boot into recovery
Do a factory reset
Go into mounts and storage using volume rockers and power button.
Format /system /boot /cache
Go to advanced : Wipe Dalvik Cache.
On TWRP Recovery :
Go to wipe
Wipe Cache , Dalvik Cache , System SD Ext and then do a factory reset.
Done ! Now flash the required ROM you want to flash!
How to partition SD card ?
Note :
This will result in your SD card being formatted. So always keep a backup of all your files on your computer.
For Stock ROM you need a FAT 32 partition which can be done via computer ONLY.
Via Recovery
Boot into recovery
Go to advanced
Partition SD card (*EXT 2,3,4 etc.*)
Select EXT Size *to whatever you want to preferably 512 mb or more*
Select Swap = 0 mb as Explorer doesnt support swap. ( at least till now )
Partition SD card! (*Will take some time*)
After partitioning is done just remove your SD card (*while your phone is off*) and just insert it back in manually.
Reboot /system (*if you have a ROM installed*)
Connect to PC and check for bad partitions just in case.
Steps 7,8,9 are not mandatory but are a good practice.
Via a computer : ( Windows )
Requirement :
SD Card reader
MiniTool Partition Wizard Home Edition 7.7 .
For further details on this visit this great guide
How to flash custom recoveries / kernels ?
How to flash a custom recovery ?
Via computer
Copy the recovery.img of the custom recovery you are try to flash and paste it in the adb directory ( for windows ==> C:\android\sdk\platform-tools\*paste here* )
Boot your Pico into bootloader (*remove battery and after 3-4 secs press vol. down and power button simeltaneously*)
In bootloader menu connect pc to your phone via usb cable and then there will be a red coloured sign just above the options saying
FASTBOOT USB
Click to expand...
Click to collapse
Now start
Windows Go to platform-tools directory in command prompt and type
Code:
fastboot flash recovery recovery.img
fastboot reboot
Linux Go to the directory of adb and fastboot and type in terminal
Code:
$ ./fastboot flash recovery recovery.img && fastboot reboot
or if path is set directly..
Via phone Terminal Emulator
Take the recovery.img that you want to flash and place it on your sd card ( eg /sdcard/(*here*) )
Begin Terminal emulator app (*Download from playstore*)
Type su (*enter*)
Allow superuser permissions (*enter*)
Note : Now you must get a line beginning with $
Enter
Code:
flash_image recovery sdcard/recovery.img
Still racking your brains over this ? Check out post 3 for video tuts !
For kernels do the same thing except replace replace Recovery.img with Boot.img
Setting permissions
Heard about setting permissions ? Ever wondered what they are ?
On a UNIX based system, every single file and folder stored on the hard drive has a set of permissions associated with it, which says who is allowed to do what with the file. Every file (and folder) also has an "owner" and a "group" associated with it. If you created the file, then you are usually the owner of that file, and your group, or the group associated with the folder you created the file in, will usually be associated with that file.
Click to expand...
Click to collapse
So how to configure them ?
You need a file explorer with Root access
Go to the required folder/app you want to set a permission and long press on it ( in most file explorers )
You will get something like this:
{
"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"
}
Select what is required and close.
Alternative via adb
Same as before from adb directory on cmd propt / terminal
Code:
adb shell
su
chmod 777 /system/app/Notes.apk
INDEX :
r = read w = write x = execute
Reference for chmod
So 777 = rwxrwxrwx 755 = rwxr-xr-x and so on and so forth..
What is overclocking ?
Overclocking is the process of making a computer or component operate faster than the specified clock frequency by the manufacturer by modifying system parameters. One of the most important techniques is running at a higher clock rate (more clock cycles per second; hence the name "overclocking")..
Operating voltages may also be changed (increased), which can increase the speed at which operation remains stable.
Pros : You get much more performance including gaming performance and overall UI performance..
Cons : Overclocking is always risky if something is configured improperly and may also result in permanent damage of your hardware. As long as it is done safely you are good to go.
You may see some increased power consumption.
Extreme overclocking might kill your hardware.
Undervolting :
The process where you provide less voltage to your cpu rather than the stock voltage.
Advantage:
Reduced heat from your device.
Good battery life.
Disadvantage:
Extreme undervolting will make your device unstable and some times even end up with a boot loop.
Recovering from an OC NAND Wipe..
cute_prince said:
Ok guys, here I am posting NAND Recovery Procedure:
Download the following attachment.. Rename flash_erase.txt to flash_erase ( Its actually a binary file )
Copy this file to /system/xbin directory using Root Explorer. Set permission as 755
Make sure Root Access is enabled for both Apps and ADB in Developer settings
Connect phone to PC .. Now open a terminal ( I am using Ubuntu ) and type the following:
Code:
[COLOR="Blue"]adb shell
su
cd /system/xbin
./flash_erase -N /dev/mtd/mtd2 0 0
./flash_erase -N /dev/mtd/mtd4 0 0
./flash_erase -N /dev/mtd/mtd5 0 0[/COLOR]
Note: when you execute above command you may get an IO error.. Its OK, dont get panic
Now disconnect phone from PC.. Remove battery and reinsert it ..
Goto recovery and:
format /boot
format /system
wipe data / factory reset
Now install your favourite ROM
Once the ROM is booted, goto storage settings.. Everything should be fine now and you should get around 140MB free depending on your ROM
Click to expand...
Click to collapse
What is md5 ? How is it useful?
The MD5 Message-Digest Algorithm is a widely used cryptographic hash function that produces a 128-bit (16-byte) hash value. Specified in RFC 1321, MD5 has been utilized in a wide variety of security applications, and is also commonly used to check data integrity. MD5 was designed by Ron Rivest in 1991 to replace an earlier hash function, MD4. An MD5 hash is typically expressed as a hexadecimal number, 32 digits long.
What does it mean in english ?
For android basically it is used to maintain the uniqueness of a file. It is also used to check wheter the file is the same file that has been uploaded or not .. or wheter the the downloaded file is half downloaded or broken..
You can check the md5 sum of two files. If they match then they are the same file. If they dont .. back to your download screen.
How do I check the md5 sum ?
On windows :
Download this and extract it on your pc..
Just put in the file's location..
Get the md5 sum from the OP
Match them ..
On android
There is an app for it : Android Filve Verifier
Video Tutorial # 1 : How to flash any recovery thru terminal emulator ! By Rishik
Video Tutorial # 2 : How to take a backup of your system! By Rishik
Please thank him for it.. HERE !
Credits : bala_gamer, cute_prince , Genexus , Rishik999, wikipedia , sdk , many tutorials on xda and other forums... and google.
Re: [GUIDE] How to install sdk / adb and do a logcat
Wrong section post in general this isnt any development
Sent from my HTC Explorer A310e using xda premium
---------- Post added at 12:03 PM ---------- Previous post was at 12:01 PM ----------
Mods move this to general!
Sent from my HTC Explorer A310e using xda premium
I knew this was coming .. It is in many development sections even for my old device Sensation. Trust me it is needed in the development section. Mods are free to move it.. Even mentioned it in the first post.. as good as a guide on rooting the pico or even compiling a kernel. Dont you think ?
If you think the people actually read the general section why would the dev thread be full of so much spam ? :silly:
good..nice..
i think this will work on win 7 also??
and give a tut for linux too...if you want i can post one here!!
Adding a lot.. Even video tuts.. if possible..
Video Tutorials
I have recently made a tutor on how to flash recovery.img through terminal emulator
I guess OP needed them?
I hope,he wont mind sharing them
http://www.youtube.com/watch?v=ND9UvfV3G34
Liked it
Please hit the like button on the vedio
Ofc the thanks button also
Disliked?
Nevermind :victory:
Thanks!
Re: [GUIDE] How to install sdk / adb and do a logcat
Can u add guide how to adb via wireless
Sent from my HTC Explorer using xda app-developers app
Re: [GUIDE] How to install sdk / adb and do a logcat
KiranP23 said:
Can u add guide how to adb via wireless
Sent from my HTC Explorer using xda app-developers app
Click to expand...
Click to collapse
Yeah was about to add it soon...
Rishik999 said:
I have recently made a tutor on how to flash recovery.img through terminal emulator
I guess OP needed them?
I hope,he wont mind sharing them
http://www.youtube.com/watch?v=ND9UvfV3G34
Liked it
Please hit the like button on the vedio
Ofc the thanks button also
Disliked?
Nevermind :victory:
Thanks!
Click to expand...
Click to collapse
Adding them bro thanks a lot .. I'll pm you
Sent from my HTC Explorer A310e using xda premium
logcats
Thanks a lot OP for making this noob friendly guide!
This really helped me,in getting logcats ..Where first I use to scratch my brains
Such guide will definitely gonna boost up development ! As there would less of noobish post! :victory:
Please,add as much as u can in these guides! :good:
U can still add on ..How to read logcats?
Anyways,I found it really helpful!
Re: [GUIDE] How to install sdk / adb and do a logcat
Fully Reading logcats and undertanding them in detail
. will need a book on java.. I will add some basics symbols and meanings in a log cat ..
Sent from my HTC Explorer A310e using xda premium
Re: [GUIDE] How to install sdk / adb and do a logcat
akshat.shenoy said:
Fully Reading logcats and undertanding them in detail
. will need a book on java.. I will add some basics symbols and meanings in a log cat ..
Sent from my HTC Explorer A310e using xda premium
Click to expand...
Click to collapse
This will be very helpful if u add meaning of those codes
sometimes after doing the instructions given in your tut for linux adb still returns
HTML:
List of devices
???????????
im on linux mint nadia and this did happen to me
so we need to setup device rules..and because we might use another android phone also its wise to add all the rules, so:
Code:
]sudo gedit /etc/udev/rules.d/51-android.rules
and copy and paste this
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="413c", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0489", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="091E", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="10A9", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="04dd", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="19D2", MODE="0666"
and then make rules executable by:
Code:
sudo chmod a+x /etc/udev/rules.d/*
and akshat we need to make bashrc also executable..
Re: [GUIDE] How to install sdk / adb and do a logcat
I really don't have linux just added what sprintonfire suggested he gave me a shell of what to do so apart from the linux part I have tried and tested everything else. Free for susuggestions and improvements not only on linux but also for the windows part thanks gnexus your a genius ( what my auto correct typed when I tried typing your name)
Cheers
Sent from my HTC Explorer A310e using xda app-developers app
akshat.shenoy said:
I really don't have linux just added what sprintonfire suggested he gave me a shell of what to do so apart from the linux part I have tried and tested everything else. Free for susuggestions and improvements not only on linux but also for the windows part thanks gnexus your a genius ( what my auto correct typed when I tried typing your name)
Cheers
Sent from my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse
i aint that much of a genius...but thanx bro
check ur pm..
didnt put all that here because it would have crowded the thread..!
Edited first post .
Changed entire Linux guide for installing sdk tools.
Added a small bit of info right at the end.
Reading logcats (basic)
http://forum.xda-developers.com/showthread.php?t=1378491
I guess this can be helpfull for noobs like me xD
This one is perfect
http://developer.android.com/tools/debugging/debugging-log.html
Real S**t xD
akshat you havent given a link from where to download sdk package for linux..
for those who just want adb follow these steps before step 1:
go here
and click on sub category "DOWNLOAD FOR OTHER PLATFORMS"
and under "sdk tools only" download the one for linux!
@akshat include this before step 1 of linux guide!
gnexus said:
akshat you havent given a link from where to download sdk package for linux..
for those who just want adb follow these steps before step 1:
go here
and click on sub category "DOWNLOAD FOR OTHER PLATFORMS"
and under "sdk tools only" download the one for linux!
@akshat include this before step 1 of linux guide!
Click to expand...
Click to collapse
They should understand that at least I guess..
still will include thanks..
Hi guys, First post here, really looking forward to learn more about android .
I'm trying to root a generic tablet (titan pc008) using linux and ADB.
The thing is when i connect the tablet and run adb devices it doesn't get listed.
So i guess i need to install some sort of generic driver or something but i've very superficial knowledge about rooting and android tinkering in general.
I've already tried killing and restarting the adb server
The lsusb output for my device:
Code:
Bus 002 Device 004: ID 2207:0000
Added this line to the file "/etc/udev/rules.d/99-android.rules":
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="2207", ATTR{idProduct}=="0000", MODE="0666", OWNER="user"
Hi guys.
I kept on googling and finally found a was to set up adb for this device on stackoverflow by Mateus Sousa Mello
I had same problem as you, what i done: Added vendor id to ~/.android/adb_usb.ini
echo "0x2207" >>~/.android/adb_usb.ini
Added the following lines to /etc/udev/rules.d/51-android.rules:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device",
ENV{PRODUCT}=="207/*", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="207", MODE="0666"
Now my chinese tablet Archos c906 is recognize on ./adb device as:
List of devices attached
0123456789ABCDEF device
Click to expand...
Click to collapse
I hope this might help someone in the future.
is Pure Nexus the only ROM / kernel so far to support no force encrypt? Has anyone else found a way to disable it, or knows if its being worked on?
The only way I found is install magisk.
Magisk will remove dm-verity check and force encrypt on boot, but as far as I know Magisk works only with twrp rc2, that has issues on twrp restores.
Take a look here, the link provided in the guide is for twrp rc2 and if you use rc1 magisk zip won't install.
TENN3R said:
The only way I found is install magisk.
Magisk will remove dm-verity check and force encrypt on boot, but as far as I know Magisk works only with twrp rc2, that has issues on twrp restores.
Take a look here, the link provided in the guide is for twrp rc2 and if you use rc1 magisk zip won't install.
Click to expand...
Click to collapse
Thanks for that. Last i checked Pixel compatibility was a known issue, I'll give it another go. What ROM(s) did you get successful no-force-encrypt in?
Found it!!!
Managed to get force-encrypt disabled with just plain old SuperSU!!
In general I was moving too fast and trying to do everything on the phone itself. Not a good idea on Pixel (with all the crazy differences in partitions).
Here's what I tried (overkill method):
(the red stuff is most likely the most important, other stuff you can probably ignore)
revert to stock (flash-all - modified)
---> fastboot set_active a (establishing consistency)
---> fastboot -w --skip-reboot update image-sailfish-xxxx.zip
---> -w formats userdata partition
---> --skip-reboot prevents reboot
---> don't want to boot into OS until after Magisk install - right?
---> the rest is normal ... but finish with ...
---> fastboot set_active a (finish with slot A active)
---> fastboot reboot-bootloader (reboot to bootloader instead of OS)
---> trying to introduce a level of control / I've noticed active slot changing unexpectedly after installing certain packages (SuperSU / Magisk / etc)
fastboot boot twrp.img
set TWRP to sideload mode
adb sideload twrp.zip
adb reboot recovery
---> wipe dalvik / data / system / internal
---> format internal storage (typed "yes")
adb reboot recovery (again)
---> select "don't show this again" / swipe right
---> now you can see TWRP folder in /sdcard directory
---> writing to /sdcard is possible without full boot into OS
adb sideload ROM.zip
---> or copy ROM to phone and install with TWRP
adb sideload twrp.zip
---> or copy twrp.zip to phone and instal with TWRP
adb reboot recovery
install SuperSU
---> slot B now active
adb reboot
---> leave slot B active and reboot
This was done on OctOS ROM (multiple times).
Other than that, isn't it weird that slot B is active after installing SuperSU??? I've tried setting slot = A then rebooting after installing SuperSU but it boot loops until it goes back to TWRP. System must remain in slot B to boot.
Also tried setting active slot A in fastboot, but it boot looped until it finally loaded the OS (still unencrypted). Went back into fastboot to check the active slot, and it was slot = B again.
Slightly off topic, I've noticed that the repository versions of the Android SDK Tools gave me funky results (ie. not up-to-date, fastboot not being able to format userdata / unknown partiton format etc) so I setup SDK tools (tools only) from the Android SDK site and added them to my path.
Currently running:
Android SDK Platform-Tools v25.0.6 (lets me set active slot in fastboot)
I modified the file ~/.profile and added my AndroidSDK location at the end:
Code:
PATH="$HOME/AndroidSDK/platform-tools:$PATH"
PATH="$HOME/AndroidSDK/build-tools/25.0.3:$PATH"
Just in case, here's all my UDEV rules (haven't found a list this complete online yet but I needed most of these for the Pixel). Run terminal:
Code:
sudo nano /etc/udev/rules.d/android.rules
This will give you the option to create the file "android.rules". Just paste the below in there and close out/save the file.
Code:
# fastboot mode
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee0", MODE="0666"
# ROM booted - debug mode disabled - not listed in "adb devices"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee8", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee1", MODE="0666"
# ROM booted - debug mode enabled - charging mode
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee7", MODE="0666"
# ROM booted - debug mode enabled - photo transfer (PTP)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee6", MODE="0666"
# ROM booted - debug mode enabled - file transfer (MPT)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee2", MODE="0666"
# ROM booted - debug mode enabled - MIDI mode
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee9", MODE="0666"
# Pixel - different sideload states
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d001", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d002", MODE="0666"
To close and save:
- CTRL + X
- ENTER to finalize save
(take your time and read the prompts at the bottom of the screen - nano is easy to use)
- reboot when done
Turns out this might not work with May update and later at least until full root can be achieved. :crying: