Related
Hello guys,
I have done my level best research but stuck at some simple steps. My goal is to see a logcat from a application for troubleshoot. This is what I have done so far. I have a laptop running on Ubuntu 12.04 32 bit. I followed this link https://help.ubuntu.com/community/AndroidSDK and have SDK manager running successfully.
I have usb debugging enabled on my G-tablet. after connecting tablet and running the command "adb devices" the laptop recognize my device.
then I run the command " adb logcat > logcat.txt " just like explained on this link http://forum.xda-developers.com/showthread.php?t=1616059
after running the above command I noticed a file in my home folder (laptop) named logcat.txt but the file contains only this "Unable to open log device '/dev/log/main': No such file or directory"
So here comes my silly questions:
1.) am I missing something obvious?
2.) If i want to see a log of what is happening when I run a particular application , How do i do it?
3.) Do I have to run SDK manager at the same time I am trying to run adb command? (i mean on background)
OH I have many more questions ,, but for now, please answer above.
theteju said:
after running the above command I noticed a file in my home folder (laptop) named logcat.txt but the file contains only this "Unable to open log device '/dev/log/main': No such file or directory"
Click to expand...
Click to collapse
That looks like a problem on the ROM. Either a misconfigured kernel or the ROM not setting up the log devices correctly. What's the output of this command on the device?
Code:
$ [B]ls -l /dev/log[/B]
crw-rw-rw- root log 10, 47 2013-01-29 11:10 events
crw-rw-rw- root log 10, 46 2013-01-29 11:10 radio
crw-rw-rw- root log 10, 45 2013-01-29 11:10 system
thats the output on my tablet running the command you mentioned.
theteju said:
crw-rw-rw- root log 10, 47 2013-01-29 11:10 events
crw-rw-rw- root log 10, 46 2013-01-29 11:10 radio
crw-rw-rw- root log 10, 45 2013-01-29 11:10 system
Click to expand...
Click to collapse
And there you have it. The main device is non-existent--as the error message stated. Plus, the major and minor device numbers seem wrong.
What's the output of this command?
Code:
$ [B]su[/B]
# [B]strings /init | fgrep log/[/B]
/dev/log/
/dev/log/main
/dev/log/radio
same as yours.
/dev/log/
/dev/log/main
/dev/log/radio
so what is going on with my system? Am I looking at clean flash?
theteju said:
same as yours.
/dev/log/
/dev/log/main
/dev/log/radio
Click to expand...
Click to collapse
Next:
Reboot the device and post the output of this command:
Code:
$ [B]dmesg | fgrep logger[/B]
[ 13.343038] logger: created 64K log 'log_main'
[ 13.343216] logger: created 256K log 'log_events'
[ 13.343395] logger: created 64K log 'log_radio'
[ 13.343574] logger: created 64K log 'log_system'
[email protected]:/ $ su
[email protected]:/ # dmesg | fgrep logger
<6>[ 1.969399] logger: created 256K log 'log_main'
<6>[ 1.969608] logger: created 256K log 'log_events'
<6>[ 1.969750] logger: created 256K log 'log_radio'
<6>[ 1.969899] logger: created 256K log 'log_system'
[email protected]:/ #
sorry I am being impatient. and Thanks for your prompt replies..I understand its too late @ your end now.
theteju said:
I understand its too late @ your end now.
Click to expand...
Click to collapse
Well, I *was* a bit sleepy, but, now that you've tossed this bizarre problem onto my lap, I'm feeling decidedly perky. Next:
Code:
$ su
# [B]ls -l /sys/class/misc/ /sys/devices/virtual/misc/ | fgrep log_[/B]
lrwxrwxrwx 1 root root 0 Jan 29 23:45 log_events -> ../../devices/virtual/misc/log_events
lrwxrwxrwx 1 root root 0 Jan 29 23:45 log_main -> ../../devices/virtual/misc/log_main
lrwxrwxrwx 1 root root 0 Jan 29 23:45 log_radio -> ../../devices/virtual/misc/log_radio
lrwxrwxrwx 1 root root 0 Jan 29 23:45 log_system -> ../../devices/virtual/misc/log_system
drwxr-xr-x 3 root root 0 Jan 29 23:45 log_events
drwxr-xr-x 3 root root 0 Jan 29 23:45 log_main
drwxr-xr-x 3 root root 0 Jan 29 23:45 log_radio
drwxr-xr-x 3 root root 0 Jan 29 23:45 log_system
Also repeat the "ls -l /dev/log" command in post #2.
/devices/virtual/misc/ | fgrep log_ <
lrwxrwxrwx root root 2013-01-29 13:52 log_events -> ../../devices/virtual/misc/log_events
lrwxrwxrwx root root 2013-01-29 13:52 log_main -> ../../devices/virtual/misc/log_main
lrwxrwxrwx root root 2013-01-29 13:52 log_radio -> ../../devices/virtual/misc/log_radio
lrwxrwxrwx root root 2013-01-29 13:52 log_system -> ../../devices/virtual/misc/log_system
drwxr-xr-x root root 2013-01-29 13:52 log_events
drwxr-xr-x root root 2013-01-29 13:52 log_main
drwxr-xr-x root root 2013-01-29 13:52 log_radio
drwxr-xr-x root root 2013-01-29 13:52 log_system
[email protected]:/ #
Sent from my Malata SMBA1002 using xda app-developers app
[email protected]:/ # ls -l /dev/log
crw-rw-rw- root log 10, 47 2013-01-29 13:12 events
crw-rw-rw- root log 10, 46 2013-01-29 13:12 radio
crw-rw-rw- root log 10, 45 2013-01-29 13:12 system
[email protected]:/ #
Sent from my Malata SMBA1002 using xda app-developers app
theteju said:
[email protected]:/ # ls -l /dev/log
crw-rw-rw- root log 10, 47 2013-01-29 13:12 events
crw-rw-rw- root log 10, 46 2013-01-29 13:12 radio
crw-rw-rw- root log 10, 45 2013-01-29 13:12 system
[email protected]:/ #
Click to expand...
Click to collapse
You did reboot the device like I asked you to, right?
Next:
Code:
$ [B]su[/B]
# [B]for f in /sys/class/misc/log_*/dev[/B]
> [B]do[/B] [B]echo $f: $(cat $f)[/B]
> [B]done[/B]
/sys/class/misc/log_events/dev: 10:46
/sys/class/misc/log_main/dev: 10:47
/sys/class/misc/log_radio/dev: 10:45
/sys/class/misc/log_system/dev: 10:44
Yes I did reboot.
[email protected]:/ # for f /sys/class/misc//log_*/dev
sh: syntax error: '/sys/class/misc//log_*/dev' unexpected
[email protected]:/ # echo $f: $(cat $f)
done
The terminal is stuck with last command.
Sent from my Malata SMBA1002 using xda app-developers app
I think I am doing something really stupid. Please make the commands in bold only.
The commands are in bold. You've missed out the `in' and 'do' keywords. Close the Term window and retype.
You should also be able to use adb: "adb logcat" doesn't work, however, "adb shell" should.
[email protected]:/ $ su
[email protected]:/ # for f in /sys/class/misc/log_*/dev
> do echo $f: $(cat $f)
> done
/sys/class/misc/log_events/dev: 10:47
/sys/class/misc/log_main/dev: 10:48
/sys/class/misc/log_radio/dev: 10:46
/sys/class/misc/log_system/dev: 10:45
[email protected]:/ #
rajeevvp said:
The commands are in bold. You've missed out the `in' and 'do' keywords. Close the Term window and retype.
You should also be able to use adb: "adb logcat" doesn't work, however, "adb shell" should.
Click to expand...
Click to collapse
Does android SDK has to run on background on laptop to use adb?
cool I am in adb shell, makes life more easy..
Next:
Code:
$ [B]su[/B]
# [B]cat /sys/class/misc/log_*/uevent
[/B]MAJOR=10
MINOR=46
DEVNAME=log_events
MAJOR=10
MINOR=47
DEVNAME=log_main
MAJOR=10
MINOR=45
DEVNAME=log_radio
MAJOR=10
MINOR=44
DEVNAME=log_system
---------- Post added at 01:18 AM ---------- Previous post was at 01:16 AM ----------
theteju said:
Does android SDK has to run on background on laptop to use adb?
Click to expand...
Click to collapse
On Linux, you only need the adb binary to run adb commands. You don't need the entire Android SDK.
Hi, i tried to backup my current rom image and installed TWRP from this webpage.
But after installing TWRP the software application continuously looping to its homescreen menu when i reboot every time.
I Tried fastboot but i dint turned on usb debug option in development settings before i install TWRP. my device is offline in adb devices from command prompt window. I cant turn on usb debug option until i boot into my device OS homescreen menu.
The terminal command is available from TWRP menu screen.
help me if i can turn on usb debug option through terminal command.
help me if i can recover my device from TWRP boot loop through the terminal commands.
Hope someone will fix my problem
st10user said:
Hi, i tried to backup my current rom image and installed TWRP from this webpage.
But after installing TWRP the software application continuously looping to its homescreen menu when i reboot every time.
I Tried fastboot but i dint turned on usb debug option in development settings before i install TWRP. my device is offline in adb devices from command prompt window. I cant turn on usb debug option until i boot into my device OS homescreen menu.
The terminal command is available from TWRP menu screen.
help me if i can turn on usb debug option through terminal command.
help me if i can recover my device from TWRP boot loop through the terminal commands.
Hope someone will fix my problem
Click to expand...
Click to collapse
Try:
Code:
adb kill-server
adb start-server
adb devices
fuser-invent said:
Try:
Code:
adb kill-server
adb start-server
adb devices
Click to expand...
Click to collapse
Thanks for your reply.
Tried these commands. device is offline in command prompt window.
st10user said:
Thanks for your reply.
Tried these commands. device is offline in command prompt window.
Click to expand...
Click to collapse
Have you tried flashing either of my ROM's from TWRP? I read in the other thread that you wiped /system so you probably don't have an operating system to boot into, that's why it keeps booting back into TWRP.
Yes bro, I tried flashing your roms through "apply update from EXT" but not worked for me.
I dont know how to flash through twrp terminal commands.
Plz help me.
which commands i need to flash through twrp?
Maybe you should try ADT android download tool
PM me if u need help
Sent from MOON......
You can't flash my ROM's through "apply update from EXT" because that is the stock recovery and they are built to be flashed in TWRP. You don't need to use terminal commands to flash anything in TWRP.
All you do is press the "Install" button, choose the zip files you want to flash and then swipe the button that shows up on the screen to the right to start the flashing process. When it's done, hit the "wipe dalvik and cache" button, flash it the ROM again, hit "wipe dalvik and cache" again and then reboot. For some reason on a lot of these tablets you need to double flash the firmware.
When i installing karbonn_custom_st10_v1.3.zip or karbonn_st10_stock_plus_v1.2.zip I receiving message like "skipping md5 check: no md5 file found."
After that everything installing successfully. But after reboot to system still my tablet stuck on twrp.
Help me.
st10user said:
When i installing karbonn_custom_st10_v1.3.zip or karbonn_st10_stock_plus_v1.2.zip I receiving message like "skipping md5 check: no md5 file found."
After that everything installing successfully. But after reboot to system still my tablet stuck on twrp.
Help me.
Click to expand...
Click to collapse
"skipping md5 check: no md5 file found." doesn't matter, you can ignore that.
Are you using the correct TWRP? There are two, one is for the ST8 and one is for the ST10.
Did you use the double flash method I suggested with the wipes? Have you tried flashing anything else before this? I'm hoping that you followed the instructions and didn't try to flash the stock+ ROM in TWRP, right?
The Stock+ ROM is for the stock recovery and the Custom ROM is for TWRP.
If there are more details, please write them. From what I understand this is where you are at so far and nothing more.
1. You downloaded TWRP
2. You flashed TWRP using ozadroid's instructions
3. You booted into TWRP and wiped /system
4. Your tablet reboots and is stuck in a boot loop.
fuser-invent said:
"skipping md5 check: no md5 file found." doesn't matter, you can ignore that.
Are you using the correct TWRP? There are two, one is for the ST8 and one is for the ST10.
Did you use the double flash method I suggested with the wipes? Have you tried flashing anything else before this? I'm hoping that you followed the instructions and didn't try to flash the stock+ ROM in TWRP, right?
The Stock+ ROM is for the stock recovery and the Custom ROM is for TWRP.
If there are more details, please write them. From what I understand this is where you are at so far and nothing more.
1. You downloaded TWRP
2. You flashed TWRP using ozadroid's instructions
3. You booted into TWRP and wiped /system
4. Your tablet reboots and is stuck in a boot loop.
Click to expand...
Click to collapse
I installed correct twrp for st10. I followed your guidance but still stuck with twrp loop. I uploaded a video of my st10 installing log here
Plz help me.
Same thing happend to me also.when I flashed twrmp .it doesn't boot to system or stock recovery. I gave it and serviced by service centre.
Sent from my Micromax A110 using xda premium
In the video you are flashing the Stock+ ROM. Flash the Karbonn Custom ROM in the same way instead. When it gets to the last step right before you hit the reboot button, remove your external SD card and then hit the reboot button with the SD card out. Let me know what happens, there could be something on your SD card forcing you to reboot into recovery instead of the ROM.
Also, it looks like ozadroid has released a newer version of TWRP than the one you are running, I would suggest downloading that and using it instead.
I flashed newer version of trmp but no change .my tab stuck again.it doesn't reboot to system.but stock recovery is available,I flashed stock rom.but no change it reboot again to trmp.now what should I do .my service center will not accept my tab again.
Sent from my Micromax A110 using xda premium
Okay, so it doesn't appear from the TWRP install video that the partitions are damaged but we should check that out, fun the following in adb from TWRP:
Code:
adb kill-server
adb start-server
adb devices
adb shell cat /proc/partitions
adb shell parted /dev/block/mtdblock0 print
adb shell parted /dev/block/mtdblock8 print
adb shell parted /dev/block/avnftli print
adb shell fdisk -l /dev/block/mtdblock0
adb shell fdisk -l /dev/block/mtdblock8
adb shell fdisk -l /dev/block/avnftli
If when you run "adb shell cat /proc/partitions" the partitions are labeled differently, then change the block name in the next section of commands. You should get something like this:
Code:
C:\adb>adb shell cat /proc/partitions
major minor #blocks name
31 0 8192 mtdblock0
31 1 8192 mtdblock1
31 2 8192 mtdblock2
31 3 8192 mtdblock3
31 4 8192 mtdblock4
31 5 524288 mtdblock5
31 6 262144 mtdblock6
31 7 1048576 mtdblock7
31 8 6504448 mtdblock8
250 32 6041600 avnftli
250 33 6024375 avnftli1
253 0 1906688 cardblksd
253 1 1905049 cardblksd1
Then this with "print" in "parted":
Code:
C:\adb>adb shell parted /dev/block/mtdblock0 print
Error: Can't have a partition outside the disk!
C:\adb>adb shell parted /dev/block/mtdblock8 print
Model: Unknown (unknown)
Disk /dev/block/mtdblock8: 6661MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 16.5MB 6185MB 6169MB primary
C:\adb>adb shell parted /dev/block/avnftli print
Model: Unknown (unknown)
Disk /dev/block/avnftli: 6187MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 16.5MB 6185MB 6169MB primary fat32
Then this with" fdisk":
Code:
C:\adb>adb shell fdisk -l /dev/block/mtdblock0
Disk /dev/block/mtdblock0: 8 MB, 8388608 bytes
255 heads, 63 sectors/track, 1 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mtdblock0p1 2 481 3855600 b Win95 FAT32
C:\adb>adb shell fdisk -l /dev/block/mtdblock8
Disk /dev/block/mtdblock8: 6660 MB, 6660554752 bytes
255 heads, 63 sectors/track, 809 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mtdblock8p1 3 752 6024375 b Win95 FAT32
C:\adb>adb shell fdisk -l /dev/block/avnftli
Disk /dev/block/avnftli: 6186 MB, 6186598400 bytes
255 heads, 63 sectors/track, 752 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/avnftli1 3 752 6024375 b Win95 FAT32
The main thing you want to be looking for is that they actually show up and don't read:
Code:
Error: /dev/block/mtdblock8: unrecognised disk label
or
Code:
Error: Partition doesn't exist.
or
Code:
Disk /dev/block/mtdblock8 doesn't contain a valid partition table
You also want to make sure that it says your partition tablet is "msdos" and the format is "FAT32"
Lastly, I wanted to ask you both which method you used to install TWRP, did you flash the zip in the stock recovery, did you place the TWRP "recovery.img" on your external SD card or did you use the "Android Partition Manager" app to flash it?
I used android partation manager.I will check wid adb
Sent from my Micromax A110 using xda premium
---------- Post added at 12:31 AM ---------- Previous post was at 12:18 AM ----------
Adb method not working
Sent from my Micromax A110 using xda premium
@ st10user
I think you have done something in the booting system. I have seen your video and saw that without pressing any keys combination your tab is just booting in TWRP.
I believe you have done the same mistake the other user done..You have flashed recovery.img in boot partition...
Solution should be now, to flash boot.img to boot partition and recovery.img to recovery partition...But not sure how to help you..
There should be some flashable file which you can use and flash thru TWRP..
--------------------------------------------------------------------------------------------
Edit: Here is your solution provided by great Fuser...
http://forum.xda-developers.com/showthread.php?t=2105692&page=65
Moonguy75 said:
Maybe you should try ADT android download tool
PM me if u need help
Sent from MOON......
Click to expand...
Click to collapse
Now my problem is solved. Thanks for your help.
KSKHH said:
@ st10user
.
I think you have done something in the booting system. I have seen your video and saw that without pressing any keys combination your tab is just booting in TWRP.
I believe you have done the same mistake the other user done..You have flashed recovery.img in boot partition...
Solution should be now, to flash boot.img to boot partition and recovery.img to recovery partition...But not sure how to help you..
There should be some flashable file which you can use and flash thru TWRP..
--------------------------------------------------------------------------------------------
Edit: Here is your solution provided by great Fuser...
http://forum.xda-developers.com/showthread.php?t=2105692&page=65
Click to expand...
Click to collapse
Now everything fine. Thanks for your help.
Thank you very much fuser-invent. You saved my tab.
Wish you all the best.
st10user said:
Thank you very much fuser-invent. You saved my tab.
Wish you all the best.
Click to expand...
Click to collapse
So please google and get some basic knowledge..that will help you in future..
Even I do not have much knowledge, however just playing with the things with common sense...:laugh:
after install the twrp my tab is dead
after install twrp in my smart tab 10 after one minute it is swzoff but still it not start then what i ll do please help me m hope less ....i charged it 1 day thare after also it not start ....plz help me......my email.id - [email protected]...
The intention of this thread is to help newbies step by step to become an entry level developer so each one can contribute their ideas and opinions inspired by hands on experiment so as to share and increase the vast knowledge of Android
How To Setup Android Development Environment on Ubuntu 13.10
Hardware Needed : Atleat Dual Core 2.8 GHz. Processor, 4GB RAM (8GB recommended).
Software Needed For Virtualisation : VMware Workstation 10.0.1 Build 1379776
OS Needed : Ubuntu 13.10/13.04 x64 (64 bit recommended)
Virtual Machine Requirement : Atleast 3 GB RAM and 40 GB Hard Disk Space
Other Requirement : Atleast 1 Mbps (4 Mbps recommended) Shared Internet Connection.
http://forum.xda-developers.com/show....php?t=2302780 [Follow This Tutorial By Matt95. All Links Are Given There.]
JDK
$ sudo mkdir /usr/lib/jvm
$ cd ~/Downloads/
$ chmod +x jdk-6u45-linux-x64.bin
$ ./jdk-6u45-linux-x64.bin
$ sudo mv jdk1.6.0_45 /usr/lib/jvm/
$ sudo update-alternatives --install /usr/bin/javac javac /usr/lib/jvm/jdk1.6.0_45/bin/javac 1
$ sudo update-alternatives --install /usr/bin/java java /usr/lib/jvm/jdk1.6.0_45/bin/java 1
$ sudo update-alternatives --install /usr/bin/jar jar /usr/lib/jvm/jdk1.6.0_45/bin/jar 1
$ sudo update-alternatives --install /usr/bin/javaws javaws /usr/lib/jvm/jdk1.6.0_45/bin/javaws 1
$ java -version
Now a restart is recommended before installing git.
GIT
$ sudo apt-get install git
$ y
PYTHON
$ cd ~/Downloads/
$ tar -xzvf Python-2.7.5.tgz
$ cd Python-2.7.5/
$ ./configure
$ make
$ sudo make altinstall
GNU
$ cd ~/Downloads/
$ tar -zxvf make-3.82.tar.gz
$ cd make-3.82
$ ./configure
$ make
$ sudo make install
[Do not use make 4.0]
OTHER PACKAGES
sudo apt-get install lib32z1 lib32ncurses5 lib32bz2-1.0 lib32stdc++6
ANDROID SDK
$ mkdir ~/development
$ cd ~/Downloads
$ tar -zxvf android-sdk_r22.2.1-linux.tgz
$ mv ~/Downloads/android-sdk-linux ~/development/
SETUP ADB/FASTBOOT
$ cd ~/development/android-sdk-linux/tools
$ ./android
SDK Path: Tools (Tick All)
Extras (Tick All)
[This process will take time depending upon the internet bandwidth]
$ sudo gedit .bashrc (ignore the error)
Now paste this at the end of the file:
#Android PATHS
export PATH=$PATH:~/development/android-sdk-linux/tools
export PATH=$PATH:~/development/android-sdk-linux/platform-tools
Save the file.
Now in a terminal window type
$ adb
$ fastboot
Both commands shows list of attributes.
Connected Samsung Galaxy Grand Quattro (I8552) to Workstation through USB Cable.
$ adb devices
Successfully Shows Device Number (Device is attached).
You are done!
How To Install, Initialize and Sync Repo on Ubuntu 13.10
How To Install, Initialize and Sync Repo on Ubuntu 13.10
Hardware Needed : Atleat Dual Core 2.8 GHz. Processor, 4GB RAM (8GB recommended).
Software Needed For Virtualisation : VMware Workstation 10.0.1 Build 1379776
OS Needed : Ubuntu 13.10/13.04 x64 (64 bit recommended)
Virtual Machine Requirement : Atleast 3 GB RAM and 40 GB Hard Disk Space
Other Requirement : Atleast 1 Mbps Shared Internet Connection.
A. INSTALL REPO PART
Install needed libs (Ubuntu 13.10) [Nearly 161 MB]
sudo apt-get install git-core flex bison gperf build-essential curl zlib1g-dev zlib1g-dev:i386 lib32ncurses5-dev x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 lib32z-dev libgl1-mesa-glx:i386 libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc libreadline6-dev lib32readline-gplv2-dev lib32readline6 libreadline-dev libbz2-dev libghc-bzlib-dev lib32bz2-dev libsdl1.2-dev libesd0-dev squashfs-tools pngcrush schedtool libwxgtk2.8-dev
Create Directories
$ mkdir -p ~/bin && mkdir -p ~/android/system
Install Repo
$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
Make Repo Executable
$ chmod a+x ~/bin/repo
Add "~/bin" to PATH of Execution
Start By Typing
gedit ~/.bashrc
Add The Below Line
export PATH=${PATH}:~/bin
B. CREATING AN ACCOUNT AT https://github.com
Go to github.com and register yourself. [If you are already a registered user then you do not have to register again]
In terminal type:
git config --global user.name "Your Name Here"
git config --global user.email "[email protected]"
[NOTE: Use the e-mail used in the website account creation]
Create your unique SSH public key
ssh-keygen -t rsa -C "[email protected]"
You can create a passphrase or omit.
Now press enter to save the ssh public keys.
Now two keys will be saved in/home/.ssh folder. (Hidden folder)
Now go to ~/.ssh folder and copy your id_rsa.pub content into account administration on github.com (double click id_rsa.pub, copy the key, login to github, go to account setting, click the SSH link and peste there).
Note: If this is the second time you are generating the ssh pubic key then after the generation copy it and visit Github. After clicking the ssh key link you will find a button "Add SSH Key". Click this and paste your new ssh key below the previous one.
Now check whether everything is ok by typing
ssh -T [email protected]
In the prompt type "yes" and you are done!
C. INITIALIZE REPO PART
$ cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
(instead of jellybean, depending on your built you may use gingerbread or ics)
D. SYNCING REPO PART
$ repo sync -j16
[This process will really take time depending on your bandwidth as this will download +16GB]
You can download all at a time or part by part. For downloading part by part just close the download at any time and safely logoff/shutdown your Ubuntu. Next time just cd to ~/android/system and type repo sync -j16. Just like any Window based download manager your download will begin from the point you closed in the last session.
You are done!
Can I also use Windows 7 for development. I have a video tutorial from YouTube indicating setting up android environment in windows. I am just asking because I never tested that I haven't a fast internet connection but if u approved for Windows 7 than I will download required sdk and exe from cafe and install them in my pc.
And also if u can please share tutorials for Windows.
Sent from my GT-I8552 using xda app-developers app
Vikas,
You are welcome to show developments in Windows. In-fact personally I feel that we can approach mass if Window is used as the development platform as newbies are much more accustomed with Window OS.
Also let me share my plan for this tutorial.
I started with ADB, the first step to connect Android based Smartphones to any OS based Workstation where Android environment is created. Then I discussed about Repo, the prime base for Android development.
Now the future plans are as following:
1. How to built a Device Tree for any new devices.
2. How to built CWM.
3. How to built Cyanogen Mod.
4. Tutorial about Eclipse.
5. Android Kitchen Setup.
6. Building Custom ROM.
The only condition is that all these steps must be shown in details for newbies in a step by step approach and it must be a generalized approach so that any devices developement can be done through these set of tutorials.
Thanks for cooperation sir give me 7-10 days and I will start development work because I truly want to learn something in android and if a support from expert side than definitely it will be more helpful.
I will start my dev from windows and very soon I will install all recommended files from tutorial and report u by pm.:thumbup::thumbup::thumbup::thumbup:
Sent from my GT-I8552 using xda app-developers app
Very useful guide...thanks for the initiative..appreciate the efforts..
You are welcome to post here.
Regards
nice info..
i just want to ask a question,
how do we compile android kernel by cygwin?
since dsixda kitchen are working flawlesly,but i wonder
why kernel seems not even compiling a kernel.
it say total errors...
i hope someone can make a clear instructions "how to"
cause ive came across all TUT in xda and i think something is missing in their TUT
Dear Jefry,
Though the kernel compilation shows error why don't you share the steps, code you have used etc. so we can all learn through it? Let it be wrong, we all will go through the coded lines, if needed search net, consult between us and then again try.
Hope you understand.
Regards
Few Basic Terminology
WHAT IS AN ANDROID EMULATOR
While there are hundreds of millions of Android devices representing hundreds of
models, you probably do not have one of each model. You may only have a single
piece of Android hardware. And if you do not even have that, you most certainly will
want to acquire one before trying to publish an Android app.
To help fill in the gaps between the devices you have and the devices that are
possible, the Android developer tools ship an emulator. The emulator behaves like a
piece of Android hardware, but it is a program you run on your development
machine. You can use this emulator to emulate many different devices, with
different screen sizes and Android OS versions, by creating one or more Android
virtual devices, or AVDs.
ANDROID OS VERSIONS AND API LEVEL
Android has come a long way since the early beta releases from late 2007. Each new
Android OS version adds more capabilities to the platform and more things that
developers can do to exploit those capabilities.
Moreover, the core Android development team tries very hard to ensure forwards
and backwards compatibility. An app you write today should work unchanged on
future versions of Android (forwards compatibility), albeit perhaps missing some
features or working in some sort of “compatibility mode”. And there are well-trodpaths for how to
create apps that will work both on the latest and on previous
versions of Android (backwards compatibility).
To help us keep track of all the different OS versions that matter to us as developers,
Android has API levels. A new API level is defined when an Android version ships
that contains changes that affect developers. When you create an emulator AVD to
test your app, you will indicate what API level that emulator should emulate. When
you distribute your app, you will indicate the oldest API level your app supports, so
the app is not installed on older devices.
At the time of this writing, the API levels of significance to most Android developers
are:
Android 1.0 (API level 1)
Android 1.1 (API level 2)
Android 1.5 Cupcake (API level 3)
Android 1.6 Donut (API level 4)
Android 2.0 Eclair (API level 5)
Android 2.0.1 Eclair (API level 6)
Android 2.1 Eclair (API level 7)
Android 2.2–2.2.3 Froyo (API level 8)
Android 2.3–2.3.2 Gingerbread (API level 9)
Android 2.3.3–2.3.7 Gingerbread (API level 10)
Android 3.0 Honeycomb (API level 11)
Android 3.1 Honeycomb (API level 12)
Android 3.2 Honeycomb (API level 13)
Android 4.0–4.0.2 Ice Cream Sandwich (API level 14)
Android 4.0.3–4.0.4 Ice Cream Sandwich (API level 15)
Android 4.1 Jelly Bean (API level 16)
Android 4.2 Jelly Bean (API level 17)
Android 4.3 Jelly Bean (API level 18)
Android 4.4 KitKat (API level 19)
WHAT IS DALVIK
In terms of Android, Dalvik is a virtual machine (VM). Virtual machines are used by
many programming languages, such as Java, Perl, and Smalltalk. The Dalvik VM is
designed to work much like a Java VM, but optimized for embedded Linux
environments.
So, what really goes on when somebody writes an Android application is:
1. Developers write Java-syntax source code, leveraging class libraries published
by the Android project and third parties.
2. Developers compile the source code into Java VM bytecode, using the javac
compiler that comes with the Java SDK.
3. Developers translate the Java VM bytecode into Dalvik VM bytecode, which
is packaged with other files into a ZIP archive with the .apk extension (the
APK file).
4. An Android device or emulator runs the APK file, causing the bytecode to be
executed by an instance of a Dalvik VM.
How To Connect Your Android Phone/Tablet With Your PC For Developement
Follow Post #2 i.e. 'How To Setup Android Development Environment on Ubuntu 13.10'
Now in a terminal window type the command
$ adb devices
The output will be something similar to:
List of devices attached
f9eru809279 device
If by any case this command fails to work, you may need to add some udev rules.
For example, here is a
51-android.rules file that will handle the devices from a handful of manufacturers:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", ATTRS{idProduct}=="0c01",
MODE="0666", OWNER="[me]"
SUBSYSTEM=="usb", SYSFS{idVendor}=="19d2", SYSFS{idProduct}=="1354", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", SYSFS{idProduct}=="681c", MODE="0666"
Open gedit and copy the above codes, then put the file in /etc/udev/rules.d directory and reboot the system.
Note that the CyanogenMod project uses these udev rules.
Before We Begin
WHO MANAGED ANDROID?
Android is very different from other mobile platforms currently available. It is not
managed by a single organization, but by a group of companies named the “Open
Handset Alliance,” which is committed to providing a mobile OS that is free, complete,
and open source.
WHY THIS CREATES COMPLEXITY?
1.Multiple screen sizes
Android devices come in a multitude of different screen sizes. Success of your app
can hinge upon how your app looks across devices.
2.Fragmentation
It is up to the carrier and manufacturer to update their devices when a new version
of the OS and runtime are released, which doesn’t always happen in a timely manner.
It is therefore necessary to support older versions of the OS and runtime.
3.Different hardware capabilities
Android phones come in all shapes, sizes, and capabilities. It is necessary to ensure
that you degrade unsupported features gracefully when the hardware is limited.
Another important consideration is the particular hardware components on which
you can or cannot rely (for instance, some devices don’t have cameras, GPS sensors,
or keyboards).
4.Resource limitations
Developing applications targeted to the mobile environment is different from developing
for the desktop. CPU speed and memory are limited compared to desktops
or servers. Mobile device users don’t put up with apps that tie up their devices
(blocking the UI), consume too many resources, or crash their devices.
DEVELOPEMENT PROCESS FOR ANDRIOD DEVELOPER TOOLS
Google manages ADT (Android Developer Tools) development, as well as the standard Android platform.
However,the two products are managed very differently, particularly in regards to the opensource
nature of the products. The ADT project is developed by a different group from
the one that manages the main platform. The tools are released separately from the
standard SDK and follow their own release cycle, which is frequently (but not always)
tied to the platform release.
The standard OS is developed behind closed doors—contributions are not accepted to
the current code base. The source code is released to the public at some point after the
group releases it to manufacturers and other insiders.
ANDROID SOFTWARE DEVELOPEMENT KIT
This bundle consists of:
• The Eclipse IDE, including the ADT plug-ins, and all the required extensions
• The SDK Tools
• The Platform Tools
• The latest Android Platform
• A CPU image compatible with the latest platform
CONFIGURING A DEVICE FOR DEVELOPEMENT
The simplest way to test your applications is often by using an Android device. You can
use almost any Android device for development, as long as you make a few changes in
order to enable communication with the development tools.
1. Configuring a Physical Device for Development.
2. Change phone settings.
Launch the Settings app on your phone, then select Applications → Development
→ USB-Debugging. Check the box next to “USB debugging” to enable this functionality.
3. Download the ADB driver.
In order to connect an Android-powered device for testing on Windows machines,
it is necessary to install the appropriate USB driver. This is not necessary on Mac
OS X or Linux.
You can find drivers at the website of the manufacturer of your phone. You may be
able to find a driver through the Android Document website, which contains a list
of links to software for many original equipment manufacturers (OEMs).
4. Validate debugging on the phone.
Connect your device to your computer. If everything went well, you will see a notification
from your operating system, indicating that the device is installed and ready to use.
WHAT IS ADB?
Andriod Debug Bridge (ADB) is the main tool that allows you to interact with your emulator or a
connected device. The ADB process is actually a client/server program. The server component
communicates with a variety of clients (such as the command line or DDMS). The
daemon process on the device facilitates communication of activities such as:
• Push/pull of data or apps
• Issuing shell commands
• Restarting the device
• Reading system logs
Let Us Start Communicating
Before you begin follow post no #2 and follow accordingly.
Now issue the command:
$ adb devices
The response will include:
Serial number
The unique ID of each connected device. You will need the serial number to connect
directly. The format of the serial number includes information about the device
itself (namely, the type of device and the port on which it is listening).
State
The connection state of the device. This will be offline if the device is connected but
not responding. It will be device if is available and connected. Otherwise, the response
will be no devices, which indicates there are no active devices that ADB can
communicate with currently.
Now issue the command:
$ adb -s serialNumber version [serialNumber = The serial number you get from $adb devices command]
The output will be like this:
[email protected]:~$ adb -s 1fd***** version
Android Debug Bridge version 1.0.31
Now that ADB knows which device to target, we can interact with it. It is possible to do
a variety of useful things with this interface.
TRANSFERRING FILES: THE FAMOUS PUSH & PULL COMMANDS
It is very easy to transfer files between your computer and your device using the push
and pull commands.
PUSH = File transferrs from your computer to the attached device.
PULL = File transfers from your attached device to computer.
You can include additional path parameters if you would like to specify a
particular location for the files. If a path is not specified, the commands will use the
current directory of your computer for the local location and the data folder on the
device for the remote location. push and pull can also copy complete directories
(recursively), which can be very useful.
The syntax of push is:
$ adb push local-directory
remote
An example of using this command is shown here. We are using ADB to push a file
named test.txt from the current directory to the SD card. The syntax for this is:
$ adb push test.txt /sdcard/test.txt [Here sdcard means the internal sdcard]
To move the file off the SD card and back onto your machine, in a new directory and
with a new name, type:
$ adb pull /sdcard/test.txt home/arinio/andro/test.txt
INTERACTIVE MODE
Interactive mode allows you to execute more than one command successively on the
device. To start interactive shell mode, type:
$ adb shell
You will see a # symbol, which indicates that you are in shell mode. When you are ready
to exit the remote shell, you can use Ctrl+D or type exit to end the shell session.
REal-Time Example:
[email protected]:~$ adb shell
[email protected]:/ $
/
[email protected]:/ $ cd /sys
sys/ system/
[email protected]:/ $ cd /system/etc/
[email protected]:/system/etc $ pwd
/system/etc
[email protected]:/system/etc $exit
ONE-OFF MODE
It is also possible to execute commands noninteractively. To do this, type the command
you want to execute after the shell keyword.
adb shell command
[email protected]:~$ adb shell cat /system/etc/hosts
127.0.0.1 localhost
RETRIEVING SYSTEM DATA
There are many cases in which you need detailed information about the various systems
on your device. Some useful commands can dump huge amounts of information about
the system, including service status, system statistics, and error logs. You may want to
collect these statistics if you are trying to analyze trends or specific details about your application.
$ adb shell dumpsys > /home/arinio/Downloads/dump.txt [Here I redirected the output to dump.txt file. Tolal output line is 31000+]
Outputs data about specific system services to the screen. For example, adb shell
dumpsys alarm will output details about all the alarms currently registered on the
system.
The first few lines are:
Currently running services:
AtCmdFwd
CustomFrequencyManagerService
DirEncryptService
FMPlayer
SurfaceFlinger
accessibility
account
activity
alarm
apn_settings_policy
application_policy
apppermission_control_policy
appwidget
audio
auditlog
backup
battery
batteryinfo
bluetooth
bluetooth_a2dp
bluetooth_avrcp
bluetooth_policy
browser_policy
certificate_policy
clipboard
clipboardEx
commontime_management
connectivity
content
country_detector
cpuinfo
date_time_policy
dbinfo
device_account_policy
device_info
device_policy
devicestoragemonitor
diskstats
display.hwcservice
drm.drmManager
dropbox
eas_account_policy
edm_proxy
edmnativehelper
email_account_policy
email_policy
enterprise_license_policy
enterprise_policy
enterprise_vpn_policy
entropy
firewall_policy
geofencing
gfxinfo
hardware
input
input_method
iphonesubinfo
iphonesubinfo_msim
isms
isms_msim
kioskmode
ldap_account_policy
license_log_service
location
location_policy
lock_settings
lockscreen_overlay
log_manager_service
mdm.remotedesktop
media.audio_flinger
media.audio_policy
media.camera
media.gestures
media.player
meminfo
mini_mode_app_manager
misc_policy
motion_recognition
mount
netpolicy
netstats
network_management
notification
package
password_policy
permission
phone
phone_msim
phone_restriction_policy
phoneextadb shell dumpsys > /home/arinio/Downloads/dump.txt
power
remoteinjection
restriction_policy
roaming_policy
samplingprofiler
samsung.facedetection_service
scheduling_policy
seandroid_policy
search
security_policy
sensorservice
serial
servicediscovery
simphonebook
simphonebook_msim
sip
smartcard_browser_policy
smartcard_email_policy
smartcard_vpn_policy
statusbar
telephony.msim.registry
telephony.registry
textservices
throttle
uimode
updatelock
usagestats
usb
vibrator
voip
vpn_policy
wallpaper
wifi
wifi_policy
wifip2p
window
Another Command:
$ adb shell dumpstate > /home/arinio/Downloads/dump1.txt
Detailed system data representing a device at a particular state in time (includes
dumpsys information as well).
The output contains 90772 lines.
THe first few lines are:
mkdir(/data/anr): Permission denied
========================================================
== dumpstate: 2013-11-30 22:37:19
========================================================
Build: JZO54K.I8552XXAMJ7
Build fingerprint: 'samsung/delos3gxx/delos3geur:4.1.2/JZO54K/I8552XXAMJ7:user/release-keys'
Bootloader: I8552XXAMDB
Radio: msm
Network: AirTel
Kernel: Linux version 3.4.0-1441994 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Tue Oct 29 13:28:51 KST 2013
Command line: (unknown)
------ UPTIME (uptime) ------
up time: 4 days, 03:13:23, idle time: 1 days, 23:21:38, sleep time: 3 days, 14:12:20
[uptime: 0.1s elapsed]
------ MEMORY INFO (/proc/meminfo) ------
MemTotal: 865328 kB
MemFree: 63208 kB
Buffers: 18316 kB
Cached: 201748 kB
SwapCached: 0 kB
Active: 540780 kB
Inactive: 121620 kB
Active(anon): 443292 kB
Inactive(anon): 1020 kB
Active(file): 97488 kB
Inactive(file): 120600 kB
Unevictable: 848 kB
Mlocked: 0 kB
HighTotal: 117760 kB
HighFree: 1624 kB
LowTotal: 747568 kB
LowFree: 61584 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 443196 kB
Mapped: 105740 kB
Shmem: 1116 kB
Slab: 46192 kB
SReclaimable: 9332 kB
SUnreclaim: 36860 kB
KernelStack: 8112 kB
PageTables: 16444 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 432664 kB
Committed_AS: 8003824 kB
VmallocTotal: 245760 kB
VmallocUsed: 82488 kB
VmallocChunk: 59248 kB
------ CPU INFO (top -n 1 -d 1 -m 30 -t) ------
User 2%, System 8%, IOW 0%, IRQ 0%
User 21 + Nice 0 + Sys 61 + Idle 645 + IOW 0 + IRQ 0 + SIRQ 0 = 727
PID TID PR CPU% S VSS RSS PCY UID Thread Proc
26459 26459 0 10% R 1432K 808K shell top top
96 96 0 0% S 0K 0K root irq/89-msm-cpr-
1013 1025 0 0% S 6012K 448K root mpdecision /system/bin/mpdecision
6 6 0 0% S 0K 0K root migration/0
16 16 1 0% S 0K 0K root khelper
17 17 1 0% S 0K 0K root suspend_sys_syn
18 18 1 0% S 0K 0K root suspend
19 19 0 0% S 0K 0K root irq/53-msmdatam
20 20 0 0% S 0K 0K root sync_supers
21 21 0 0% S 0K 0K root bdi-default
22 22 1 0% S 0K 0K root kblockd
23 23 0 0% S 0K 0K root khubd
24 24 1 0% S 0K 0K root modem_notifier
25 25 1 0% S 0K 0K root smd_channel_clo
26 26 1 0% S 0K 0K root smsm_cb_wq
30 30 1 0% S 0K 0K root qmi
31 31 1 0% S 0K 0K root rpcrouter
32 32 1 0% S 0K 0K root rpcrotuer_smd_x
33 33 0 0% S 0K 0K root krpcserversd
35 35 0 0% S 0K 0K root rmt_storage
36 36 1 0% S 0K 0K root kadspd
37 37 1 0% D 0K 0K root voicememo_rpc
39 39 0 0% D 0K 0K root krmt_storagecln
40 40 0 0% D 0K 0K root krmt_storagecln
41 41 0 0% S 0K 0K root kswapd0
42 42 0 0% S 0K 0K root fsnotify_mark
43 43 0 0% S 0K 0K root ecryptfs-kthrea
44 44 1 0% S 0K 0K root crypto
57 57 1 0% S 0K 0K root mdp_dma_wq
58 58 1 0% S 0K 0K root mdp_vsync_wq
[top: 2.7s elapsed]
------ PROCRANK (procrank) ------
*** exec(procrank): Permission denied
*** procrank: Exit code 255
[procrank: 0.1s elapsed]
------ VIRTUAL MEMORY STATS (/proc/vmstat) ------
nr_free_pages 10236
nr_inactive_anon 255
nr_active_anon 110826
nr_inactive_file 30149
nr_active_file 24375
nr_unevictable 212
nr_mlock 0
nr_anon_pages 110801
nr_mapped 26437
nr_file_pages 55015
nr_dirty 0
nr_writeback 0
nr_slab_reclaimable 2746
nr_slab_unreclaimable 14345
nr_page_table_pages 4117
nr_kernel_stack 1015
nr_unstable 0
nr_bounce 0
nr_vmscan_write 0
nr_vmscan_immediate_reclaim 0
nr_writeback_temp 0
nr_isolated_anon 0
nr_isolated_file 0
nr_shmem 279
nr_dirtied 439303
nr_written 438957
nr_anon_transparent_hugepages 0
nr_dirty_threshold 11861
nr_dirty_background_threshold 2965
pgpgin 1208499
pgpgout 1874766
pswpin 0
pswpout 0
pgalloc_normal 7397855
pgalloc_high 1334847
pgalloc_movable 0
pgfree 8862011
pgactivate 127582
pgdeactivate 53470
pgfault 10679448
pgmajfault 8080
pgrefill_normal 15854
pgrefill_high 79498
pgrefill_movable 0
pgsteal_kswapd_normal 337890
pgsteal_kswapd_high 103263
pgsteal_kswapd_movable 0
pgsteal_direct_normal 17327
pgsteal_direct_high 1880
pgsteal_direct_movable 0
pgscan_kswapd_normal 352987
pgscan_kswapd_high 127978
pgscan_kswapd_movable 0
pgscan_direct_normal 22790
pgscan_direct_high 2645
pgscan_direct_movable 0
pginodesteal 0
slabs_scanned 28130432
kswapd_inodesteal 0
kswapd_low_wmark_hit_quickly 289
kswapd_high_wmark_hit_quickly 748
kswapd_skip_congestion_wait 0
pageoutrun 2014157
allocstall 452
pgrotated 8
compact_blocks_moved 17749
compact_pages_moved 78038
compact_pagemigrate_failed 10421
compact_stall 640
compact_fail 248
compact_success 392
unevictable_pgs_culled 212
unevictable_pgs_scanned 0
unevictable_pgs_rescued 2
unevictable_pgs_mlocked 2
unevictable_pgs_munlocked 2
unevictable_pgs_cleared 0
unevictable_pgs_stranded 0
unevictable_pgs_mlockfreed 0
Another Useful Command:
$ adb shell logcat -b radio
This command provides access to the cellular radio log. This information is useful
when interacting with the networking stack. Some of the information available in
this log includes time of events, a listing of commands used by the system to com‐
municate, SMS information, IP information, and cellular network data.
ADB DOES A LOT MORE:
The ADB tool has a variety of additional functionality. Some functionality worth highlighting includes:
• Modify network configuration options like port forwarding (example: adb forward
tcp:7101 tcp:8101)
• Access your device as the root user (example: adb shell su)
• Restart the device in alternate modes, such as recovery mode (example: adb reboot
recovery)
• View system logs, such as the radio or event buffers (example: adb logcat -b events)
• Examine system utilization (example: adb shell tail | top)
There is a lot of other functionality we aren’t able to cover. For a complete list of all
available commands and their parameters, type adb -help without any additional arguments to get a listing of all options.
How To Find The Complete File System Of Galaxy Grand Quattro
Before you begin follow post no #2 and follow accordingly.
Now issue the command:
[email protected]:~$ adb devices
[email protected]:~$ adb shell
[email protected]:/ $ su -
[email protected]:/ # ls -R /
Move this find.txt from internal to external sdcard with the command:
[email protected]:/ # ls -R / > /sdcard/filesystem.doc
You can now transfer this file to your computer.
The file system of Galaxy Grand Quattro (GT-I8552) is as below: (Total 4253 pages of a MSWord doc)
[FONT="]/:
acct
cache
charger
config
d
data
default.prop
dev
efs
etc
factory
fstab.delos3g
fstab.msm7627a
fstab.qcom
init
init.goldfish.rc
init.qcom.class_core.sh
init.qcom.class_main.sh
init.qcom.rc
init.qcom.ril.path.sh
init.qcom.sh
init.qcom.unicorn-dpi.sh
init.qcom.usb.rc
init.qcom.usb.sh
init.rc
init.target.rc
init.trace.rc
init.usb.rc
initlogo.rle
initlogo_swa.rle
lpm.rc
mnt
persist
preload
proc
res
root
sbin
sdcard
storage
sys
system
ueventd.goldfish.rc
ueventd.qcom.rc
ueventd.rc
vendor[/FONT]
.
.
.
..........(4253 pages)
The /proc/partitions Table Of Galaxy Grand Quattro
[email protected]:/sdcard # cat /proc/partitions
[FONT="]
[/FONT]
[FONT="]major minor #blocks name[/FONT]
[FONT="] [/FONT]
[FONT="] 179 0 7634944 mmcblk0[/FONT]
[FONT="] 179 1 20 mmcblk0p1[/FONT]
[FONT="] 179 2 175 mmcblk0p2[/FONT]
[FONT="] 179 3 20480 mmcblk0p3[/FONT]
[FONT="] 179 4 1 mmcblk0p4[/FONT]
[FONT="] 179 5 1000 mmcblk0p5[/FONT]
[FONT="] 179 6 1000 mmcblk0p6[/FONT]
[FONT="] 179 7 2000 mmcblk0p7[/FONT]
[FONT="] 179 8 12288 mmcblk0p8[/FONT]
[FONT="] 179 9 3072 mmcblk0p9[/FONT]
[FONT="] 179 10 3072 mmcblk0p10[/FONT]
[FONT="] 179 11 4096 mmcblk0p11[/FONT]
[FONT="] 179 12 8192 mmcblk0p12[/FONT]
[FONT="] 179 13 12288 mmcblk0p13[/FONT]
[FONT="] 179 14 4096 mmcblk0p14[/FONT]
[FONT="] 179 15 4096 mmcblk0p15[/FONT]
[FONT="] 179 16 12288 mmcblk0p16[/FONT]
[FONT="] 179 17 24576 mmcblk0p17[/FONT]
[FONT="] 179 18 4096 mmcblk0p18[/FONT]
[FONT="] 179 19 512 mmcblk0p19[/FONT]
[FONT="] 179 20 2048 mmcblk0p20[/FONT]
[FONT="] 179 21 1228800 mmcblk0p21[/FONT]
[FONT="] 179 22 737280 mmcblk0p22[/FONT]
[FONT="] 179 23 102400 mmcblk0p23[/FONT]
[FONT="] 179 24 5443168 mmcblk0p24[/FONT]
[FONT="] 179 32 31166976 mmcblk1[/FONT]
[FONT="] 179 33 31165952 mmcblk1p1[/FONT][FONT="]
[/FONT]
The /proc/partitions Table Of Galaxy Grand Quattro In Structured Format
Please view attachment.
The /proc/partitions Table Of Galaxy Grand Quattro After Decimal To Hex Convertion
Here we have the /proc/partitions table after converting the values to hexadecimal.
Samsung no more provides the file /proc/mtd for make the developers work easy.
I want all to emphasis on this table structure as for building recovery and CWM this table structure is invaluable.
However still the name of the partitions are not known to us in desired format like boot, recovery etc.
We will do further research in the upcoming tutorial.
How To Unpack Recovery Image
For now let us shift our attention fro the /proc folder and focus over the recovery image file. Later on we will again review our previous discussion in more detailed manner.
Let us jump into this current topic.
Now the first question is where to find the recovery image?
In old days it was possible to locate that file by simply typing the command:
$ adb devices
$ adb shell
$ su -
and then in the root typing # cat /proc/mtd (for Samsung) or # cat /proc/emmc (for HTC)
Alas! Now there is no such files.
So, let us apply the hard way to find that image file.
Start...............
In google simply type sammobile or directly type in the address bar www.sammobile.com
Register yourself first and foremost.
Now click the Firmware link or you can directly click the Firmwares link after typing sammobile in google search box. It's up to you.
Here you will find a box 'search your device here'
There simply type I8552
The search result will consist of seven columns.
Importantis column no. two where you will find your country, column three where you will find the Firmware release month (go for the latest month), column six where the name of the version you will get and finally the last column where the download link is there.
Now click the latest download link (for India it is I8552XXAMJ7) and in the latest windows you will get a Captcha challenge. Unfortunately though filling the right letters/numbers the Captcha will fail and fortunately you will get another link for download. [There are two links for India, one will show INU file and another INS file. In your Galaxy Grand Quattro box you will find whether your device is based on INU or INS].
The download links are always Hotfile links and they are resumable. Better to use Internet Download Manager (IDM) to download this file.
The files are nearly 750 MB sizes and they are compressed in rar format.
With the help of WInRAR unRAR it and you will get a tar.md5 formatted file and the latest Firmwares size will become 1.3 GB.
We call them as tarball (actually a .tar file is a tarball file and here in this case this is a tarball file with md5 checksum) files and inside this Firmware the recovery image file is hidden.
For Indian user the file will look like I8552XXAMJ7_I8552ODDAMI4_I8552DDAMI1_HOME.tar.md5
If you are not very much accustomed with VMWare how to create a link between your Original OS (we call it host) and virtually running Ubuntu (we call it guest) simply go to your Windows OS, copy the file in a USB drive and then again plug it while in Ubuntu and paste it in your home folder.
Now the main part...............
Right click this file and delete the .md5 words (mind the dot)
In Ubuntu open a terminal window and fire up these commands:
[email protected]:~$ mkdir quattro
[email protected]:~$ mv I8552XXAMJ7_I8552ODDAMI4_I8552DDAMI1_HOME.tar /home/arinio/quattro/
[email protected]:~$ cd quattro/
[email protected]:~/quattro$ tar xvf I8552XXAMJ7_I8552ODDAMI4_I8552DDAMI1_HOME.tar
boot.img
recovery.img
system.img.ext4
fat.bin
cache.img.ext4
hidden.img.ext4
So finally inside the quattro folder we got six files and one of them is recovery.img. Note that another important file is boot.img
Now you can delete the I8552XXAMJ7_I8552ODDAMI4_I8552DDAMI1_HOME.tar file. This will be no more needed. Infact you can delete all other files except recovery.img and boot.img
So if now you issue this command you will observe
[email protected]:~$ ls /home/arinio/quattro/
boot.img recovery.img
Let us target recovery.img
First visit this page http://forum.xda-developers.com/showthread.php?t=1877807 and download unmkbootimg.gz file.
Inside your /home partition you will find one folder named Download. After the download is complete (1-5 second) you will find the unmkbootimg.gz file there only.
Now issue this commands:
[email protected]:~$ cd /home/arinio/Downloads/
[email protected]:~/Downloads$ ls
ADB.txt dump1.txt Python-2.7.5
ADB.txt~ dump2.txt REPO PART.txt
Android Developer Tools Essentials.pdf dump.txt REPO PART.txt~
CWM BUILD PATH.txt~ make-4.0 unmkbootimg.gz
[email protected]:~/Downloads$ gunzip unmkbootimg.gz
[email protected]:~/Downloads$ ls
ADB.txt dump1.txt Python-2.7.5
ADB.txt~ dump2.txt REPO PART.txt
Android Developer Tools Essentials.pdf dump.txt REPO PART.txt~
CWM BUILD PATH.txt~ make-4.0 unmkbootimg
So unmkbootimg.gz becomes unmkbootimg
Now cut the unmkbootimg file from Downloads folder and paste it inside quattro folder.
So now the quattro folder will look like:
[email protected]:~/Downloads$ ls /home/arinio/quattro/
boot.img recovery.img unmkbootimg
Now right click the unmkbootimg and click 'Properties'.
In the new window click the tab 'Pemissions' and check-mark 'Allow executing file as program'.
Close the 'Permissions' window.
Now while inside the quattro folder issue this command:
[email protected]:~/quattro$ ./unmkbootimg recovery.img > recoveryoutput.txt
Now issue
[email protected]:~/quattro$ ls
boot.img recovery.img unmkbootimg
initramfs.cpio.gz recoveryoutput.txt zImage
Here The kernel is zImage and the ramdisk is initramfs.cpio.gz.
So, ultimately we have successfully unpacked the recovery image and recovery.img consists two files namely zImage and initramfs.cpio.gz
If we issue this command:
[email protected]:~/quattro$ cat recoveryoutput.txt
The output will show:
unmkbootimg version 1.2 - Mikael Q Kuisma <[email protected]>
Kernel size 4694160
Kernel address 0x208000
Ramdisk size 1082913
Ramdisk address 0x1500000
Secondary size 0
Secondary address 0x1100000
Kernel tags address 0x200100
Flash page size 4096
Board name is ""
Command line "androidboot.hardware=qcom loglevel=1 vmalloc=200M"
*** WARNING ****
This image is built using NON-standard mkbootimg!
OFF_RAMDISK_ADDR is 0x01300000
Please modify mkbootimg.c using the above values to build your image.
****************
Extracting kernel to file zImage ...
Extracting root filesystem to file initramfs.cpio.gz ...
All done.
---------------
To recompile this image, use:
mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --base 0x200000 --cmdline 'androidboot.hardware=qcom loglevel=1 vmalloc=200M' --pagesize 4096 -o new_boot.img
---------------
Done!
You have been simple superb so far...no other dev would care to go into all these details...thanks a lot for your efforts..
im learning android a bit
For those who wants to know and learn how:
Requirements.
Preparation.
Collecting Information.
Dumping.
Build Up Flashable Image.
Click to expand...
Click to collapse
CREDITS
I do not want to take any credit for this as it is not my work, I just have forked it from http://www.freaktab.com.
You can check the original post here
I just have simplified it.
Requirements
Requirements :
USB Drivers Of your device installed
ADB ( Android Debugging Bridge)
romdump_v82b.zip (Android ROM dumper by Sebastian404)
Micro-USB-cable
microSD-card OR USB-Stick
Newer busybox
Click to expand...
Click to collapse
Code:
[B]* If you don't want to work with microSD-card OR USB-Stick you can use:
ADB push <from-PC-file> <to-android-file>
ADB pull <from-android-file> <to-PC-file>
(don't forget the pathes)
[/B]
Preparations
Preparations
Setup android
Settings -> [DEVICE] USB -> Enable Connect to PC
Settings -> [PERSONAL] Security -> Enable Unknown Sources
Settings -> [SYSTEM] Developer options -> Enable USB debugging
Click to expand...
Click to collapse
Install USB-Driver
Conect Your device With computer
open device manager
right click on not recognized device
click update driver.
Click to expand...
Click to collapse
Format SD Card
copy romdump form romdump_v82b.zip to the microSD-card
make directory "rompump.out" and "dd.out"
Remove it "secure" from PC
put it into your device
Click to expand...
Click to collapse
Collecting Information
1. Starting shell via ADB
Browse to the folder where adb files are places
E.G. I have My adb files in adb folder in C: drive
Code:
cd\
cd adb
Code:
C:\adb>
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
0123456789ABCDEF device
C:\adb>adb shell
Code:
[email protected]:/ #
=> this seems to be the ideal, because it's root (SU), if you don't have the # you have to try to type su
Confirm the correct user:
[email protected]:/ # id
Code:
uid=0(root) gid=0(root)
OR
[email protected]:/ # echo $USER
Code:
root
You can find your microSD-card under the directory "/mnt"
[email protected]:/ # cd /mnt
[email protected]:/mnt # ls
Code:
asec
external_sd
obb
sdcard
secure
shell
usb_storage
[email protected]:/mnt # cd external_sd
[email protected]:/mnt/external_sd # ls
Code:
LOST.DIR
dd.out
romdump
romdump.out
for the correct busybox release
[email protected]: # cat /proc/cpuinfo
Code:
Processor : ARMv7 Processor rev 0 (v7l)
:
After you have via PC download the newer busybox (I give it the name "busybox-armv7l_1.21.1") and put it to your microSD-card, then you have to copy it to your device
[email protected]:/ # cp /mnt/external_sd/busybox-armv7l_1.21.1 /data/busybox-armv7l_1.21.1
Destination MUST BE "/data/", otherwise it isn't executable...
[email protected]: # cat /proc/mtd
Code:
dev: size erasesize name
mtd0: 00400000 00004000 "misc"
mtd1: 01000000 00004000 "kernel"
mtd2: 01000000 00004000 "boot"
mtd3: 01000000 00004000 "recovery"
mtd4: 18000000 00004000 "backup"
mtd5: 08000000 00004000 "cache"
mtd6: 80000000 00004000 "userdata"
mtd7: 00400000 00004000 "kpanic"
mtd8: 20000000 00004000 "system"
mtd9: 113400000 00004000 "user"
[email protected]: # cat /proc/partitions
Code:
major minor #blocks name
31 0 4096 mtdblock0
31 1 16384 mtdblock1
31 2 16384 mtdblock2
31 3 16384 mtdblock3
31 4 393216 mtdblock4
31 5 131072 mtdblock5
31 6 2097152 mtdblock6
31 7 4096 mtdblock7
31 8 524288 mtdblock8
31 9 4509696 mtdblock9
179 0 3941376 mmcblk0
179 1 3941344 mmcblk0p1
[email protected]:/ # ls -al /dev/block
Code:
brw------- root root 7, 0 2013-10-27 15:39 loop0
brw------- root root 7, 1 2013-10-27 15:39 loop1
brw------- root root 7, 2 2013-10-27 15:39 loop2
brw------- root root 7, 3 2013-10-27 15:39 loop3
brw------- root root 7, 4 2013-10-27 15:39 loop4
brw------- root root 7, 5 2013-10-27 15:39 loop5
brw------- root root 7, 6 2013-10-27 15:39 loop6
brw------- root root 7, 7 2013-10-27 15:39 loop7
brw------- root root 179, 0 2013-10-27 16:29 mmcblk0
brw------- root root 179, 1 2013-10-27 16:29 mmcblk0p1
drwxr-xr-x root root 2013-10-27 15:39 mtd
brw------- root root 31, 0 2013-10-27 15:39 mtdblock0
brw------- root root 31, 1 2013-10-27 15:39 mtdblock1
brw------- root root 31, 2 2013-10-27 15:39 mtdblock2
brw------- root root 31, 3 2013-10-27 15:39 mtdblock3
brw------- root root 31, 4 2013-10-27 15:39 mtdblock4
brw------- root root 31, 5 2013-10-27 15:39 mtdblock5
brw------- root root 31, 6 2013-10-27 15:39 mtdblock6
brw------- root root 31, 7 2013-10-27 15:39 mtdblock7
brw------- root root 31, 8 2013-10-27 15:39 mtdblock8
brw------- root root 31, 9 2013-10-27 15:39 mtdblock9
drwxr-xr-x root root 2013-10-27 15:39 platform
drwx------ root root 2013-10-27 15:39 vold
[email protected]:/ # ls -al /dev/block/mtd/by-name
Code:
lrwxrwxrwx root root 2013-10-27 15:39 backup -> /dev/block/mtdblock4
lrwxrwxrwx root root 2013-10-27 15:39 boot -> /dev/block/mtdblock2
lrwxrwxrwx root root 2013-10-27 15:39 cache -> /dev/block/mtdblock5
lrwxrwxrwx root root 2013-10-27 15:39 kernel -> /dev/block/mtdblock1
lrwxrwxrwx root root 2013-10-27 15:39 kpanic -> /dev/block/mtdblock7
lrwxrwxrwx root root 2013-10-27 15:39 misc -> /dev/block/mtdblock0
lrwxrwxrwx root root 2013-10-27 15:39 recovery -> /dev/block/mtdblock3
lrwxrwxrwx root root 2013-10-27 15:39 system -> /dev/block/mtdblock8
lrwxrwxrwx root root 2013-10-27 15:39 user -> /dev/block/mtdblock9
lrwxrwxrwx root root 2013-10-27 15:39 userdata -> /dev/block/mtdblock6
[email protected]:/dev # /data/busybox-armv7l_1.21.1 blkid
Code:
/dev/block/mmcblk0p1: UUID="04A7-463C"
/dev/block/vold/31:9: UUID="8269-1ED1"
/dev/block/vold/179:1: UUID="04A7-463C"
/dev/block/mtdblock9: UUID="8269-1ED1"
/dev/block/mtdblock8: LABEL="system" UUID="06bc9880-9e07-4dec-ae8d-1e59a1b88921"
/dev/block/mtdblock6: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b"
/dev/block/mtdblock5: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b"
DUMPING
Dumping ROM
Dumping (at adb shell)
1.) via dd:
dd if=/dev/block/mtdblock0 of=/mnt/external_sd/dd.out/misc.img
Code:
8192+0 records in
8192+0 records out
4194304 bytes transferred in 0.677 secs (6195426 bytes/sec)
dd if=/dev/block/mtdblock1 of=/mnt/external_sd/dd.out/kernel.img
Code:
32768+0 records in
32768+0 records out
16777216 bytes transferred in 1.734 secs (9675441 bytes/sec)
dd if=/dev/block/mtdblock2 of=/mnt/external_sd/dd.out/boot.img
Code:
32768+0 records in
32768+0 records out
16777216 bytes transferred in 2.665 secs (6295390 bytes/sec)
dd if=/dev/block/mtdblock3 of=/mnt/external_sd/dd.out/recovery.img
Code:
32768+0 records in
32768+0 records out
16777216 bytes transferred in 1.340 secs (12520310 bytes/sec)
dd if=/dev/block/mtdblock4 of=/mnt/external_sd/dd.out/backup.img
Code:
786432+0 records in
786432+0 records out
402653184 bytes transferred in 69.198 secs (5818855 bytes/sec)
dd if=/dev/block/mtdblock8 of=/mnt/external_sd/dd.out/system.img
Code:
1048576+0 records in
1048576+0 records out
536870912 bytes transferred in 57.050 secs (9410533 bytes/sec)
/data/busybox-armv7l_1.21.1 ls -ltr /mnt/external_sd/dd.out/
Code:
-rwxrwxr-x 1 1000 1015 4194304 Oct 27 21:09 misc.img
-rwxrwxr-x 1 1000 1015 16777216 Oct 27 21:12 kernel.img
-rwxrwxr-x 1 1000 1015 16777216 Oct 27 21:14 boot.img
-rwxrwxr-x 1 1000 1015 16777216 Oct 27 21:15 recovery.img
-rwxrwxr-x 1 1000 1015 402653184 Oct 27 21:17 backup.img
-rwxrwxr-x 1 1000 1015 536870912 Oct 27 21:27 system.img
?not really need?
Code:
dd if=/dev/block/mtdblock5 of=/mnt/external_sd/dd.out/cache.img
dd if=/dev/block/mtdblock6 of=/mnt/external_sd/dd.out/userdata.img
dd if=/dev/block/mtdblock7 of=/mnt/external_sd/dd.out/kpanic.img
dd if=/dev/block/mtdblock9 of=/mnt/external_sd/dd.out/user.img
2.) via "romdump":
cp /mnt/external_sd/romdump /data/romdump
/data/romdump
Code:
Android ROM dumper v0.82b
(c)2011 Sebastian404
Device : rk31sdk-eng 4.2.2 JDQ39 eng.linking.20130709.184313 test-keys
Creating required files... done.
Opening mtd table... done.
Dumping kernel config... sh: cat: /proc/config.gz: No such file or directory
done.
Dumping boot partition... done.
Dumping recovery partition... done.
Dumping system partition... done.
Creating Checksums... done.
Cleaning up... done.
All done.
ls -al /sdcard/romdump
Code:
-rwxrwxr-x system sdcard_rw 16777216 2013-10-27 22:46 boot.img
-rwxrwxr-x system sdcard_rw 275 2013-10-27 22:48 checksum.md5
-rwxrwxr-x system sdcard_rw 0 2013-10-27 22:46 config.gz
-rwxrwxr-x system sdcard_rw 16777216 2013-10-27 22:46 recovery.img
-rwxrwxr-x system sdcard_rw 1507 2013-10-27 22:46 system.info.gz
-rwxrwxr-x system sdcard_rw 373034496 2013-10-27 22:48 system.tar
cp /sdcard/romdump/boot.img /mnt/external_sd/romdump.out/boot.img
cp /sdcard/romdump/checksum.md5 /mnt/external_sd/romdump.out/checksum.md5
cp /sdcard/romdump/config.gz /mnt/external_sd/romdump.out/config.gz
cp /sdcard/romdump/recovery.img /mnt/external_sd/romdump.out/recovery.img
cp /sdcard/romdump/system.info.gz /mnt/external_sd/romdump.out/system.info.gz
cp /sdcard/romdump/system.tar /mnt/external_sd/romdump.out/system.tar
ls -al /mnt/external_sd/romdump.out
Code:
-rwxrwxr-x system sdcard_rw 16777216 2013-10-27 23:15 boot.img
-rwxrwxr-x system sdcard_rw 275 2013-10-27 23:15 checksum.md5
-rwxrwxr-x system sdcard_rw 0 2013-10-27 23:15 config.gz
-rwxrwxr-x system sdcard_rw 16777216 2013-10-27 23:15 recovery.img
-rwxrwxr-x system sdcard_rw 1507 2013-10-27 23:15 system.info.gz
-rwxrwxr-x system sdcard_rw 373034496 2013-10-27 23:16 system.tar
Build Up Flashable Image
Build Up Flashable Image
WinHex or any other Hex-Editor who can work with large files
Rk29xx ImageTools V2.1 by wendal (I download it here at 4. (it's without "su" and "Superuser.apk"))
(Alternatively you can use RK3xxx Firmware Tools by SergioPoverony)
First check the "dd.out/backup.img" with a HexEditor to determine whether there is information in it (first 4 characters "RKAF") or only zeros (HEX "FF") what means it is empty...
If there is this information in it, you will perhaps* have the complete ROM in it, which will include the loader and parameter files and you can use "wendal tools" to extract it...
1. Put the "backup.img" into the wendal tools directory and rename it to "wendal.img"
2. Start the "Runme.bat",
2a. Select 1 + return
2b. then any key
2c. and then you have to wait.
Code:
D:\RK3066_IMG_Mod_Tool>lua rk29xx_rom_tools_tnt.lua
RK29xx Image Pack/Unpack Tools
Blog http://wendal.net
Project: https://github.com/wendal/teclast_tools
feedback: [email protected]
Pls input: 1-Unpack 2-Pack 3-Exit
1
Pls copy Image file into this folder,and rename to wendal.img
Notify any errors!
Drücken Sie eine beliebige Taste . . .
Reading file header...
File header: RKFWf
Read loader's offset
Read loader's len
Read update.img's offset
Read update.img's len
Output Loader
offset(0x66) len(0x2F8AE)
Output updata.img
offset(0x2F914) len(0x1973A804)
Unpack updata.img to Temp folder
Check file... OK
------- UNPACK ------
package-file 0x00000800 0x00000241
RK3188Loader(L)_V1.20.bin 0x00001000 0x0002F96E
parameter 0x00031000 0x00000266
Image/misc.img 0x00031800 0x0000C000
Image/kernel.img 0x0003D800 0x00846034
Image/boot.img 0x00884000 0x000FE6F1
Image/recovery.img 0x00982800 0x00B18000
Image/system.img 0x0149A800 0x16E09800
backupimage/backup.img 0x182A4000 0x01495004
update-script 0x19739800 0x000003A5
recover-script 0x1973A000 0x0000010A
Unpack firmware OK!
------ OK ------
Unpack -- All Done
Pls input: 1-Unpack 2-Pack 3-Exit
Amazing work,you should add your name at TWRP which you compiled.
Well,hats off bro.
Steps for MMC based devices
Thanks for the info. Don't know why it hadn't occur to me to use dd for taking the image.
This works great for MTD based devices but does nothing for MMC based devices.
Never fear, I found the answer in an old post from lavero.burgos on repartitioning a Nook tablet.
Turns out if you use the parted from the CM team you can acquire the partition information you need.
Here is a shorthand of the previous instructions as they apply to MMC devices:
Req:
USB Drivers for your device
ADB installed and in your path
Appropriately sized USB cable for your device
microSD card
GNU parted
a rooted device
Prep:
make directory "firmware-img" on SD Card
make directory "tools" on SD Card
copy parted to tools directory on SD Card
Remove SD Card safely from PC
put SD Card into rooted device
Collect Info:
Run the commands below (one per line)
adb shell
su (if not already root user)
cp /mnt/<sd card mount point>/tools/parted /system/bin
cat /proc/partitions
parted /dev/block/mmcblk0
print
make note of the partition number and name for the partitions you wish to dump
quit
Dumping ROM:
Run dd as defined below each partition you wan to dump, the <partition path> will be /dev/block/mmcblk0p<partition number>.
dd if=<partition path> of=/mnt/<sd card mount point>/firmware-img/<partition name>.img
---------- Post added at 02:36 PM ---------- Previous post was at 02:21 PM ----------
I hope this helps. I'm by no means an expert on this type of thing, so if you have additions or corrections, plz feel free. I've been watching learning and gathering, now I have a chance to give back.
I've gotten this to work on Nook tablet, Atrix HD and gonna test it on my Xoom in the next few days.
I dont know much about the MMC based devices .. As I onLy Have used Mediatek devices so far, btw thanx for the information
When I tried to do cat proc/mtd I got this error
Code:
1|[email protected]:/ # cat /proc/mtd
cat /proc/mtd
sh: cat: /proc/mtd: No such file or directory
1|[email protected]:/ #
i have a question please help me if you can
i didnt find the cat /proc/mtd is working because the mtd is not found in proc so after search i used proc/mount with link
i got the system file only but i didn't got the recovery or boot
i need another way to get it to build CWM
my device is totally new and support for it at all because it is BCM 21663 broadom
i have dual core Arm 7
512 ram
8g storage
1024*600
2 sim 3g tablet
any other CWM may works? or firmware refer to this specs??
ANY EXPERT THERE???
Thank you very much for the post, it was very helpful! It's a good complement to this post:
http://forum.xda-developers.com/showthread.php?t=2450045
modify download directory
Hi. I have a problem with my lenovo A526, whenever I want to download, it says "modify thedownload directory of the ". How can I do that? Can someone help me please? Thank you.
Ruscelle23 said:
Hi. I have a problem with my lenovo A526, whenever I want to download, it says "modify thedownload directory of the ". How can I do that? Can someone help me please? Thank you.
Click to expand...
Click to collapse
Try Using any other browser like opera or UC and choose custom directory before downloading a file. Ruscelle23
hssrgh said:
i have a question please help me if you can
i didnt find the cat /proc/mtd is working because the mtd is not found in proc so after search i used proc/mount with link
i got the system file only but i didn't got the recovery or boot
i need another way to get it to build CWM
my device is totally new and support for it at all because it is BCM 21663 broadom
i have dual core Arm 7
512 ram
8g storage
1024*600
2 sim 3g tablet
any other CWM may works? or firmware refer to this specs??
ANY EXPERT THERE???
Click to expand...
Click to collapse
Use cat /proc/emmc
The original link for romdump doesn't work, so here is an alternative one.
romdump_v82b.zip | by bhiga for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
codenation said:
The original link for romdump doesn't work, so here is an alternative one.
romdump_v82b.zip | by bhiga for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Click to expand...
Click to collapse
Thanks a lot for that.
Hello,
I am looking for a mmcblk0p3 file located in the phones to redo the update.
to check the score of the phone:
Code:
adb shell cat proc/partitions
here is the code to extract the file in the SD card:
Code:
adb shell su -c dd if=/dev/block/mmcblk0p3 of=/sdcard/ids.img bs=4096
I tried but the problem my phone not recognize sd card as there is always block the startup logo.
here is the second code to extract the file on pc:
Code:
adb -d shell su -c busybox dd if=/dev/block/mmcblk0p3 > C:\Users\%username%\Desktop\ids.img
when I install a ROM by accident I mmcblk0p3 erase the file is replaced with the boot file.
I try again to do the update but I have a problem because it marks me "failure reading device information. Check the condition of the phone"
I'm looking to remake mmcblk0p3 updating the phone.
there is there anyone who could share that file (1024 kb) => traceability?
Thank you for your reply.