Database Info

[INFO] Nexus 7 Partitions!

Here's an output of /proc/mounts, might be help full other devs:
which one is recovery partition does anyone know?
zoneinfo
[email protected]:/proc $ cat mounts
cat mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro,relatime,user_xatt
r,acl,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 rw,nosuid,nodev,noatim
e,errors=panic,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 rw,nosuid,nodev,noatime
,errors=panic,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1
023,default_permissions,allow_other 0 0

run
Code:
ls -l /dev/block/platform/sdhci-tegra.3/by-name/
and that should show all partitions.

Indirect said:
run
Code:
ls -l /dev/block/platform/sdhci-tegra.3/by-name/
and that should show all partitions.
Click to expand...
Click to collapse
Thanks!
C:\Users\max\Downloads\Nexus7Root>adb shell
[email protected]:/ $ ls -l /dev/block/platform/sdhci-tegra.3/by-name/
ls -l /dev/block/platform/sdhci-tegra.3/by-name/
lrwxrwxrwx root root 2012-06-28 11:51 APP -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-06-28 11:51 CAC -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-06-28 11:51 LNX -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-06-28 11:51 MDA -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-06-28 11:51 MSC -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-06-28 11:51 PER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-06-28 11:51 SOS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-06-28 11:51 UDA -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-06-28 11:51 USP -> /dev/block/mmcblk0p6

try
Code:
ls -l /dev/block/
and if you see r on the 3rd from last line of each partition, do the following commands:
Code:
adb shell cat /dev/block/platform/sdhci-tegra.3/by-name/lnx > lnxfile.bin
adb shell cat /dev/block/platform/sdhci-tegra.3/by-name/SOS > SOSfile.bin

Indirect said:
try
Code:
ls -l /dev/block/
and if you see r on the 3rd from last line of each partition, do the following commands:
Code:
adb shell cat /dev/block/platform/sdhci-tegra.3/by-name/lnx > lnxfile.bin
adb shell cat /dev/block/platform/sdhci-tegra.3/by-name/SOS > SOSfile.bin
Click to expand...
Click to collapse
C:\Users\max\Downloads\Nexus7Root>adb shell
[email protected]:/ $ ls -l /dev/block/
ls -l /dev/block/
brw------- root root 7, 0 2012-06-28 11:51 loop0
brw------- root root 7, 1 2012-06-28 11:51 loop1
brw------- root root 7, 2 2012-06-28 11:51 loop2
brw------- root root 7, 3 2012-06-28 11:51 loop3
brw------- root root 7, 4 2012-06-28 11:51 loop4
brw------- root root 7, 5 2012-06-28 11:51 loop5
brw------- root root 7, 6 2012-06-28 11:51 loop6
brw------- root root 7, 7 2012-06-28 11:51 loop7
brw------- root root 179, 0 2012-06-28 11:51 mmcblk0
brw------- root root 179, 16 2012-06-28 11:51 mmcblk0boot0
brw------- root root 179, 32 2012-06-28 11:51 mmcblk0boot1
brw------- root root 179, 1 2012-06-28 11:51 mmcblk0p1
brw------- root root 179, 2 2012-06-28 11:51 mmcblk0p2
brw------- root root 179, 3 2012-06-28 11:51 mmcblk0p3
brw------- root root 179, 4 2012-06-28 11:51 mmcblk0p4
brw------- root root 179, 5 2012-06-28 11:51 mmcblk0p5
brw------- root root 179, 6 2012-06-28 11:51 mmcblk0p6
brw------- root root 179, 7 2012-06-28 11:51 mmcblk0p7
brw------- root root 179, 8 2012-06-28 11:51 mmcblk0p8
brw------- root root 179, 9 2012-06-28 11:51 mmcblk0p9
drwxr-xr-x root root 2012-06-28 11:51 platform
drwx------ root root 2012-06-28 11:51 vold
[email protected]:/ $
Permission denied for cat

yep, that's what I figured but it was still worth a shot. :x
You'll need root. If you can get it before you have to surrender that tab, it'd be great.

run this one:
Code:
cat /proc/partitions
and this one:
Code:
fdisk -l /dev/block/mmcblk0
this command would be interesting too:
Code:
cat /proc/cmdline
And if the file exists execute "adb pull /proc/config.gz"(or copy it via rootexplorer) and post it here. It's the kernel-config

Cool - these are btw mostly generic tegra names, while most are probably obvious I've "translated" them below.
zedomax said:
C:\Users\max\Downloads\Nexus7Root>adb shell
[email protected]:/ $ ls -l /dev/block/platform/sdhci-tegra.3/by-name/
ls -l /dev/block/platform/sdhci-tegra.3/by-name/
lrwxrwxrwx root root 2012-06-28 11:51 APP -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-06-28 11:51 CAC -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-06-28 11:51 LNX -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-06-28 11:51 MDA -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-06-28 11:51 MSC -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-06-28 11:51 PER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-06-28 11:51 SOS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-06-28 11:51 UDA -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-06-28 11:51 USP -> /dev/block/mmcblk0p6
Click to expand...
Click to collapse
APP -> system
CAC -> cache
LNX -> boot.img
MDA -> Unknown
MSC -> Misc (bootloader commands and other misc stuff )
PER -> usually a fat partition containing sensor calibration etc. - per device provisioned.
SOS -> recovery.img
UDA -> /data - "user data area"
USP -> Staging
---------- Post added at 10:18 PM ---------- Previous post was at 10:17 PM ----------
m11kkaa said:
run this one:
Code:
cat /proc/partitions
and this one:
Code:
fdisk -l /dev/block/mmcblk0
Click to expand...
Click to collapse
There's no standard "dos" partition anywhere, so that won't work.
m11kkaa said:
this command would be interesting too:
Code:
cat /proc/cmdline
And if the file exists execute "adb pull /proc/config.gz"(or copy it via rootexplorer) and post it here. It's the kernel-config
Click to expand...
Click to collapse
At least cmdline is actually protected from normal users in newer kernels and same with config.gz I believe. Worth a shot though. (FWIW, usually tegra bootloader fills in kernel cmdline rather than hardcoding it in boot.img )

Code:
1|[email protected]:/dev/block/platform/sdhci-tegra.3/by-name $ cat /proc/partitions
/partitions <
major minor #blocks name
179 0 7467008 mmcblk0
179 1 12288 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 665600 mmcblk0p3
179 4 453632 mmcblk0p4
179 5 512 mmcblk0p5
179 6 10240 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 512 mmcblk0p8
179 9 6302720 mmcblk0p9
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0

Config.gz
Here's Config.gz attached

zedomax said:
Code:
1|[email protected]:/dev/block/platform/sdhci-tegra.3/by-name $ cat /proc/partitions
.....[/QUOTE]
4096Bytes are missing. Maybe the bootloader+PartitionTable at first bytes of Nand :)
Did anyone of you try if there is an bootloader-mode(the usual key-combinations)?
Click to expand...
Click to collapse

Partition sizes
Could you/someone please post a df to see the size of each partition, I wonder how much of the 8GB are available and how much is for /data.
Thanks!

Filesystem Size Used Free Blksize
/dev 487M 32K 487M 4096
/mnt/asec 487M 0K 487M 4096
/mnt/obb 487M 0K 487M 4096
/system 639M 422M 217M 4096
/cache 436M 7M 428M 4096
/data 5G 4G 1G 4096
/storage/sdcard0 5G 4G 1G 4096
/mnt/asec/com.lexi.android-1 3M 1M 1M 4096

Is there any way to creat a extra partition or at least to change the size?

I don't believe so or someone would have done it already.

rayman said:
Cool - these are btw mostly generic tegra names, while most are probably obvious I've "translated" them below.
APP -> system
CAC -> cache
LNX -> boot.img
MDA -> Unknown
MSC -> Misc (bootloader commands and other misc stuff )
PER -> usually a fat partition containing sensor calibration etc. - per device provisioned.
SOS -> recovery.img
UDA -> /data - "user data area"
USP -> Staging
Click to expand...
Click to collapse
Just a bit of an update on these from what I've found. MDA is listed in the fstab as encrypted data.
/dev/block/platform/sdhci-tegra.3/by-name:
lrwxrwxrwx 1 root root 20 Nov 12 00:10 SOS -> /dev/block/mmcblk0p1 -> recovery
lrwxrwxrwx 1 root root 20 Nov 12 00:10 LNX -> /dev/block/mmcblk0p2 -> boot
lrwxrwxrwx 1 root root 20 Nov 12 00:10 APP -> /dev/block/mmcblk0p3 -> system
lrwxrwxrwx 1 root root 20 Nov 12 00:10 CAC -> /dev/block/mmcblk0p4 -> cache
lrwxrwxrwx 1 root root 20 Nov 12 00:10 MSC -> /dev/block/mmcblk0p5 -> misc
lrwxrwxrwx 1 root root 20 Nov 12 00:10 USP -> /dev/block/mmcblk0p6 -> bootloader
lrwxrwxrwx 1 root root 20 Nov 12 00:10 PER -> /dev/block/mmcblk0p7 -> per device calibration
lrwxrwxrwx 1 root root 20 Nov 12 00:10 MDA -> /dev/block/mmcblk0p8 -> encrypted userdata
lrwxrwxrwx 1 root root 20 Nov 12 00:10 UDA -> /dev/block/mmcblk0p9 -> userdata
APP -> system
CAC -> cache
LNX -> boot
MDA -> encrypted userdata
MSC -> misc
PER -> per device calibration
SOS -> recovery
UDA -> userdata
USP -> bootloader
Edit, Jan. 9th: Dug up the N7 tilapia equivalents today because I was curious (found on the Ubuntu site of all places).
/dev/block/platform/sdhci-tegra.3/by-name/
lrwxrwxrwx root root 2012-11-20 13:48 SOS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-11-20 13:48 LNX -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-11-20 13:48 APP -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-11-20 13:48 RDO -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-11-20 13:48 CAC -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-11-20 13:48 MSC -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2012-11-20 13:48 USP -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-11-20 13:48 PER -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-11-20 13:48 MDA -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-11-20 13:48 UDA -> /dev/block/mmcblk0p10
Seems they just stuck RDO (radio) in the middle at p4 so everything else just shifts down, and up a p#.

Also worth mentioning for both N7 variants (and apparently Tegras in general), mmcblk0boot0 and mmbblk0boot1 are continuous and contain 3 partitions: BCT, PT and the start of the bootloader. BCT takes up all of boot0 and the beginning of boot1. They are encrypted and boot0 is where lockstate is stored. For more info check out my BootUnlocker Script thread.
Credits to lilstevie for that information.

USP is only staging Area for bootloader flashes not the bootloader itself...
Is the per partition on all N7 the same or are there differences from device to device, so that I can´t use the per partion of another N7?

osm0sis said:
Just a bit of an update on these from what I've found. MDA is listed in the fstab as encrypted data.
/dev/block/platform/sdhci-tegra.3/by-name:
lrwxrwxrwx 1 root root 20 Nov 12 00:10 SOS -> /dev/block/mmcblk0p1 -> recovery
lrwxrwxrwx 1 root root 20 Nov 12 00:10 LNX -> /dev/block/mmcblk0p2 -> boot
lrwxrwxrwx 1 root root 20 Nov 12 00:10 APP -> /dev/block/mmcblk0p3 -> system
lrwxrwxrwx 1 root root 20 Nov 12 00:10 CAC -> /dev/block/mmcblk0p4 -> cache
lrwxrwxrwx 1 root root 20 Nov 12 00:10 MSC -> /dev/block/mmcblk0p5 -> misc
lrwxrwxrwx 1 root root 20 Nov 12 00:10 USP -> /dev/block/mmcblk0p6 -> bootloader
lrwxrwxrwx 1 root root 20 Nov 12 00:10 PER -> /dev/block/mmcblk0p7 -> per device calibration
lrwxrwxrwx 1 root root 20 Nov 12 00:10 MDA -> /dev/block/mmcblk0p8 -> encrypted userdata
lrwxrwxrwx 1 root root 20 Nov 12 00:10 UDA -> /dev/block/mmcblk0p9 -> userdata
APP -> system
CAC -> cache
LNX -> boot
MDA -> encrypted userdata
MSC -> misc
PER -> per device calibration
SOS -> recovery
UDA -> userdata
USP -> bootloader
Edit, Jan. 9th: Dug up the N7 tilapia equivalents today because I was curious (found on the Ubuntu site of all places).
/dev/block/platform/sdhci-tegra.3/by-name/
lrwxrwxrwx root root 2012-11-20 13:48 SOS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-11-20 13:48 LNX -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-11-20 13:48 APP -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-11-20 13:48 RDO -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-11-20 13:48 CAC -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-11-20 13:48 MSC -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2012-11-20 13:48 USP -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-11-20 13:48 PER -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-11-20 13:48 MDA -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-11-20 13:48 UDA -> /dev/block/mmcblk0p10
Seems they just stuck RDO (radio) in the middle at p4 so everything else just shifts down, and up a p#.
Click to expand...
Click to collapse
Having issues decompiling the Boot and Recovery, code suggestions

[Kernel] Siyah_I9305 Discussion..

As per some comments by G.K i thought it was going to be ported by now but things change , not sure whats
Happening ill leave it open incase we have some news regarding it.

btemtd said:
I spoke to Gohkan regarding porting his kernel to I9305 he said the only reason -not likely- is because he tried this before without owning the device and it was quite hard as he could not test it, especially when bugs arise it got quite frustrating for him. But he was more then happy to give a helping hand to any dev that would like to port his kernel. I guess the best way also is if there is a bug the Dev that ported the Kernel will need to Liase with Gohkan instead of all the users flooding him with bug reports. He mentioned Devs from US variant ported his kernel no problem. So if any of our devs would like to help, Let me know and I can speak to him or just message him and say "you are a dev and want to port his kernel where do we start". I am willing to help with what ever is needed, just let me know
I mean Perseus is 1 AWESOME kernel if you ask me , only thing is there is no interface to tweak it like Siyah's Stweaks. I was told he is working on something tho. Anyways Its always good to have a variety to choose from
Click to expand...
Click to collapse
Please contact me. We are willing to work on this port. Ordering device tomorrow. Talk me: [email protected],

Just checked out liquid smooth for nexus. Looks amazing. Cant wait!!!
Sent from my GT-I9305 using xda premium

The first version is allways difficult!
Congratulations to all equipo.(GT I9305 LTE SiyahKernel)

has one been made?

Amplified said:
Please contact me. We are willing to work on this port. Ordering device tomorrow. Talk me: [email protected],
Click to expand...
Click to collapse
I have Emailed You and I have also PM'd you, I have not received any reply. So evryone Its still in the air at the moment Its up for grabs who ever wants to start, If I knew what to do I would of started already. I myself need some guidance especially with kernels..

I didn't know that 9300 and 9305 was almost identical, even the partition sizes and layout.
I just have to reconfirm that but if it is so I will release i9305 version by simply editing the config file a little + some merges with 9305 kernel sources.
but it will not be so easy if the partition layout is different.

gokhanmoral said:
I didn't know that 9300 and 9305 was almost identical, even the partition sizes and layout.
I just have to reconfirm that but if it is so I will release i9305 version by simply editing the config file a little + some merges with 9305 kernel sources.
but it will not be so easy if the partition layout is different.
Click to expand...
Click to collapse
It would be great to have another choice of kernel

This is what Andreilux wrote before he ported his kernel
The I9305 is almost Identical kernel to the i9300 one. Only difference is:
CMA device memory allocation is gone as we don't need the hacks used in it for larger memory, 2GB with the default setting will suffice. <<< Although if it doesnt hurt and just gives us more then feel free to leave it in there, the more the better I say, But you are the dev so you can decide.
LCDFreq might not work [WIP]
You apparently have no FM radio. <<<<< Although these devices have the hardware and he said he is going to make a kernel with FM support... We havent seen one yet as he is working with Note 2 at the moment. So feel free to try yourself
The port is trivial and everything else should work flawlessly.
Also this helped him create a CWM flash hope this helps you these are the partition locations on the I9305
lrwxrwxrwx root root 2012-10-08 21:43 BOOT -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-10-08 21:43 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-10-08 21:43 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-10-08 21:43 CACHE -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-10-08 21:43 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-10-08 21:43 HIDDEN -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2012-10-08 21:43 OTA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2012-10-08 21:43 PARAM -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-10-08 21:43 RADIO -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-10-08 21:43 RECOVERY -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-10-08 21:43 SYSTEM -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-10-08 21:43 TOMBSTONES -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-10-08 21:43 USERDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs3 -> /dev/block/mmcblk0p6

btemtd said:
This is what Andreilux wrote before he ported his kernel
The I9305 is almost Identical kernel to the i9300 one. Only difference is:
CMA device memory allocation is gone as we don't need the hacks used in it for larger memory, 2GB with the default setting will suffice. <<< Although if it doesnt hurt and just gives us more then feel free to leave it in there, the more the better I say, But you are the dev so you can decide.
LCDFreq might not work [WIP]
You apparently have no FM radio. <<<<< Although these devices have the hardware and he said he is going to make a kernel with FM support... We havent seen one yet as he is working with Note 2 at the moment. So feel free to try yourself
The port is trivial and everything else should work flawlessly.
Also this helped him create a CWM flash hope this helps you these are the partition locations on the I9305
lrwxrwxrwx root root 2012-10-08 21:43 BOOT -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-10-08 21:43 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-10-08 21:43 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-10-08 21:43 CACHE -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-10-08 21:43 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-10-08 21:43 HIDDEN -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2012-10-08 21:43 OTA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2012-10-08 21:43 PARAM -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-10-08 21:43 RADIO -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-10-08 21:43 RECOVERY -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-10-08 21:43 SYSTEM -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-10-08 21:43 TOMBSTONES -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-10-08 21:43 USERDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-10-08 21:43 m9kefs3 -> /dev/block/mmcblk0p6
Click to expand...
Click to collapse
I also need the partition sizes.
so please post "df" and "mount" outputs from adb shell.
it seems that the layout is different but if the formats are the sizes are similar I can get dual boot feature work as well.
and also please post "ls -l /dev/input /dev/block" output

Ok I will get it done now, If somebody is quicker feel free to post for Gohkan

I hope this is right

btemtd said:
I hope I did it right for you Gokz please confirm
Click to expand...
Click to collapse
exactly what I needed.
but it will not be that easy. I will have to make some modifications in the recovery and dual-boot related parts because partition layout is not the same.
so, it will not be released together with tonight's 9300 release.

gokhanmoral said:
exactly what I needed.
but it will not be that easy. I will have to make some modifications in the recovery and dual-boot related parts because partition layout is not the same.
so, it will not be released together with tonight's 9300 release.
Click to expand...
Click to collapse
Bro Not a problem at all.. Do not rush, and thank you so much. I am here if you need anything

if it helps i have dumped a text version of the shell outputs:
Code:
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p12 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered 0 0
/dev/block/mmcblk0p13 /system ext4 ro,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p16 /data ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p10 /firmware vfat ro,relatime,fmask=0133,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/mmcblk0p11 /tombstones ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/dm-0 /mnt/asec/com.suffick.node-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-1 /mnt/asec/com.uberdroidstudio.ubermusic-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/vold/179:17 /storage/extSdCard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
df
Filesystem Size Used Free Blksize
/dev 896M 84K 896M 4096
/mnt/asec 896M 0K 896M 4096
/mnt/obb 896M 0K 896M 4096
/efs 19M 4M 15M 4096
/cache 1007M 17M 990M 4096
/system 1G 1001M 510M 4096
/data 11G 6G 4G 4096
/firmware 199M 45M 154M 4096
/tombstones 251M 18M 233M 4096
/storage/sdcard0 10G 6G 4G 4096
/mnt/asec/com.suffick.node-1 2M 256K 1M 4096
/mnt/asec/com.uberdroidstudio.ubermusic-1 3M 1M 1M 4096
/storage/extSdCard 29G 28G 1G 32768
ls -l /dev/input /dev/block
crw-rw---- root input 13, 64 2012-10-18 11:10 event0
crw-rw---- root input 13, 65 2012-10-18 11:10 event1
crw-rw---- root input 13, 74 2012-10-18 11:10 event10
crw-rw---- root input 13, 66 2012-10-18 11:10 event2
crw-rw---- root input 13, 67 2012-10-18 11:10 event3
crw-rw---- root input 13, 68 2012-10-18 11:10 event4
crw-rw---- root input 13, 69 2012-10-18 11:10 event5
crw-rw---- root input 13, 70 2012-10-18 11:10 event6
crw-rw---- root input 13, 71 2012-10-18 11:10 event7
crw-rw---- root input 13, 72 2012-10-18 11:10 event8
crw-rw---- root input 13, 73 2012-10-18 11:10 event9
crw-rw---- root input 13, 63 2012-10-18 11:10 mice
brw------- root root 254, 0 2012-10-18 11:10 dm-0
brw------- root root 254, 1 2012-10-18 11:10 dm-1
brw------- root root 7, 0 2012-10-18 11:10 loop0
brw------- root root 7, 1 2012-10-18 11:10 loop1
brw------- root root 7, 2 2012-10-18 11:10 loop2
brw------- root root 7, 3 2012-10-18 11:10 loop3
brw------- root root 7, 4 2012-10-18 11:10 loop4
brw------- root root 7, 5 2012-10-18 11:10 loop5
brw------- root root 7, 6 2012-10-18 11:10 loop6
brw------- root root 7, 7 2012-10-18 11:10 loop7
brw------- root root 179, 0 2012-10-18 11:10 mmcblk0
brw------- root root 179, 1 2012-10-18 11:10 mmcblk0p1
brw-rw---- system radio 179, 10 2012-10-18 11:10 mmcblk0p10
brw-rw---- system radio 179, 11 2012-10-18 11:10 mmcblk0p11
brw------- root root 179, 12 2012-10-18 11:10 mmcblk0p12
brw------- root root 179, 13 2012-10-18 11:10 mmcblk0p13
brw------- root root 179, 14 2012-10-18 11:10 mmcblk0p14
brw------- root root 179, 15 2012-10-18 11:10 mmcblk0p15
brw------- root root 259, 0 2012-10-18 11:10 mmcblk0p16
brw------- root root 179, 2 2012-10-18 11:10 mmcblk0p2
brw------- root root 179, 3 2012-10-18 11:10 mmcblk0p3
brw-rw---- system radio 179, 4 2012-10-18 11:12 mmcblk0p4
brw-rw---- system radio 179, 5 2012-10-18 11:10 mmcblk0p5
brw-rw---- system radio 179, 6 2012-10-18 11:10 mmcblk0p6
brw-rw---- system root 179, 7 2012-10-18 11:11 mmcblk0p7
brw------- root root 179, 8 2012-10-18 11:10 mmcblk0p8
brw------- root root 179, 9 2012-10-18 11:10 mmcblk0p9
brw------- root root 179, 16 2012-10-18 11:10 mmcblk1
brw------- root root 179, 17 2012-10-18 11:10 mmcblk1p1
lrwxrwxrwx root root 2012-10-18 11:10 param -> /dev/block/mmcblk0p7
drwxr-xr-x root root 2012-10-18 11:10 platform
brw------- root root 1, 0 2012-10-18 11:10 ram0
brw------- root root 1, 1 2012-10-18 11:10 ram1
brw------- root root 1, 10 2012-10-18 11:10 ram10
brw------- root root 1, 11 2012-10-18 11:10 ram11
brw------- root root 1, 12 2012-10-18 11:10 ram12
brw------- root root 1, 13 2012-10-18 11:10 ram13
brw------- root root 1, 14 2012-10-18 11:10 ram14
brw------- root root 1, 15 2012-10-18 11:10 ram15
brw------- root root 1, 2 2012-10-18 11:10 ram2
brw------- root root 1, 3 2012-10-18 11:10 ram3
brw------- root root 1, 4 2012-10-18 11:10 ram4
brw------- root root 1, 5 2012-10-18 11:10 ram5
brw------- root root 1, 6 2012-10-18 11:10 ram6
brw------- root root 1, 7 2012-10-18 11:10 ram7
brw------- root root 1, 8 2012-10-18 11:10 ram8
brw------- root root 1, 9 2012-10-18 11:10 ram9
drwx------ root root 2012-10-18 11:10 vold
im running stock XXALI5 on my Optus i9305

i got my s3lte today and lol when using phone actually missed the features of ur kernel cnt wait for port
Sent from my GT-I9305 using Tapatalk 2

His working on a few things with other phones this weekend so i am hoping we should have this by next week some time . (Hopefully) his a busy man
Sent from my GT-I9305 using xda app-developers app

anyone up for porting will pm dev bwt this. cnt wait to gt this kernel on i9305. best kernel ever
Sent from my GT-I9305 using Tapatalk 2

No need as gohkan is going to do it he is still working on some s2 sttuff when he finish then its s3, we will get duaL booting feature but there is some bad news to follow. Gohkan is leaving the s3 so updats will be slow. Reason for leaving is because samsung wont release the exynos sources. On other note if they do he might return.
I did here some news on sammobile saying they are going to soon apparently.
Sent from my GT-I9305 using xda app-developers app

Im happy to be kernel Guinni Pig
btemtd said:
No need as gohkan is going to do it he is still working on some s2 sttuff when he finish then its s3, we will get duaL booting feature but there is some bad news to follow. Gohkan is leaving the s3 so updats will be slow. Reason for leaving is because samsung wont release the exynos sources. On other note if they do he might return.
I did here some news on sammobile saying they are going to soon apparently.
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse

[Q] where is ramdisk.img ?

hi, all!
Modify /init.rc configure file is my plan, in android(linux) box, /(rootfs) locate RAM.
So, modify ramdisk.img(initrd.img) is aim, However, I find any image file except recovery backup image:
[email protected]:/ # /system/xbin/busybox find / -name '*.img'
/mnt/sdcard2/clockworkmod/backup/2012-01-01.00.03.03/boot.img
/mnt/sdcard2/clockworkmod/backup/2012-01-01.00.03.03/recovery.img
/system/etc/firmware/modem.img
Did the partition that ramdisk.img save in not mount by kernel ?
My phone information:
all partition:
[email protected]:/ # ll /dev/block/
brw------- root root 254, 0 2012-11-30 22:08 dm-0
brw------- root root 7, 0 2012-11-30 22:07 loop0
brw------- root root 7, 1 2012-11-30 22:07 loop1
brw------- root root 7, 2 2012-11-30 22:07 loop2
brw------- root root 7, 3 2012-11-30 22:07 loop3
brw------- root root 7, 4 2012-11-30 22:07 loop4
brw------- root root 7, 5 2012-11-30 22:07 loop5
brw------- root root 7, 6 2012-11-30 22:07 loop6
brw------- root root 7, 7 2012-11-30 22:07 loop7
brw-rw---- root system 179, 0 2012-11-30 22:07 mmcblk0
brw------- root root 179, 32 2012-11-30 22:07 mmcblk0boot0
brw------- root root 179, 64 2012-11-30 22:07 mmcblk0boot1
brw------- root root 179, 1 2012-11-30 22:07 mmcblk0p1
brw------- root root 179, 2 2012-11-30 22:07 mmcblk0p2
brw------- root root 179, 3 2012-11-30 22:07 mmcblk0p3
brw------- root root 179, 4 2012-11-30 22:07 mmcblk0p4
brw------- root root 179, 5 2012-11-30 22:07 mmcblk0p5
brw------- root root 179, 6 2012-11-30 22:07 mmcblk0p6
brw------- root root 179, 96 2012-11-30 22:07 mmcblk1
brw------- root root 179, 97 2012-11-30 22:07 mmcblk1p1
drwxr-xr-x root root 2012-11-30 22:07 platform
drwxr-xr-x root root 2012-11-30 22:07 vold
mounted partition:
[email protected]:/ # mount|/system/xbin/busybox grep mmc
/[email protected] /system ext4 ro,noatime,user_xattr,commit=1,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
had be linked partition:
[email protected]:/ # ll / |/system/xbin/busybox mmc
lrwxrwxrwx root root 1970-01-01 08:00 [email protected] -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 08:00 [email protected] -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 08:00 [email protected] -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 08:00 [email protected] -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 08:00 [email protected]_ro -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 08:00 [email protected] -> /dev/block/mmcblk0p5

[email protected]:/ # cat /proc/mtd
dev: size erasesize name
[email protected]:/ #
My phone do not use mtd ?
what other technology my phone used? and, what can I locate recovery and boot partition ?

Ramdisk is inside boot.img, you must use dsixda's kitchen to decompile it.
Sent from my PC36100 using xda app-developers app

Yes, the ramdisk is inside the boot.img. The recovery.img contains its own ramdisk. The partition is a basic format created just for android. The first 0x30ish bytes contain offsets and sizes for the kernel image, ramdisk, kernel command line, and stuff like that. And no, the ramdisk is not compiled; you do no decompile it. It is compressed. You can pull the ramdisk out of the partition and decompress it using standard commandline tools.

[Q] How to extract boot.img from Zopo C7 ( MTK6589T)

First how to find location of boot image in device? I want to take current boot image. Do modifications and later flash that boot image back to device.
I have searched correct block device and did some image files with dd command but they were not boot images. I tried with several tools.
Here is some listing from the phone with adb shell commands.
Code:
[email protected]:/proc # cat partitions
major minor #blocks name
179 0 30512256 mmcblk0
179 1 1 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 665600 mmcblk0p5
179 6 129024 mmcblk0p6
179 7 1572864 mmcblk0p7
179 8 28077696 mmcblk0p8
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
Code:
[email protected]:/ # ls -l /emm*
lrwxrwxrwx root root 1970-01-01 06:30 [email protected] -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 06:30 [email protected] -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 06:30 [email protected] -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 06:30 [email protected] -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 06:30 [email protected]_f -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 06:30 [email protected]_s -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 06:30 [email protected]_ro -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 06:30 [email protected] -> /dev/block/mmcblk0p7
[email protected]:/ #
Code:
[email protected]:/dev/block # ls -al
brw------- root root 7, 0 2014-03-12 12:54 loop0
brw------- root root 7, 1 2014-03-12 12:54 loop1
brw------- root root 7, 2 2014-03-12 12:54 loop2
brw------- root root 7, 3 2014-03-12 12:54 loop3
brw------- root root 7, 4 2014-03-12 12:54 loop4
brw------- root root 7, 5 2014-03-12 12:54 loop5
brw------- root root 7, 6 2014-03-12 12:54 loop6
brw------- root root 7, 7 2014-03-12 12:54 loop7
brw-rw---- root system 179, 0 2014-03-12 12:54 mmcblk0
brw------- root root 179, 32 2014-03-12 12:54 mmcblk0boot0
brw------- root root 179, 64 2014-03-12 12:54 mmcblk0boot1
brw------- root root 179, 1 2014-03-12 12:54 mmcblk0p1
brw-r----- root system 179, 2 2014-03-12 12:54 mmcblk0p2
brw------- root root 179, 3 2014-03-12 12:54 mmcblk0p3
brw------- root root 179, 4 2014-03-12 12:54 mmcblk0p4
brw------- root root 179, 5 2014-03-12 12:54 mmcblk0p5
brw------- root root 179, 6 2014-03-12 12:54 mmcblk0p6
brw------- root root 179, 7 2014-03-12 12:54 mmcblk0p7
brw------- root root 179, 8 2014-03-12 12:54 mmcblk0p8
drwxr-xr-x root root 2014-03-12 12:54 platform
[email protected]:/dev/block #
/dev/block/mmcblk0boot0 looked promising but I made image of it by by command dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot.img
But the image was not boot image.
Code:
[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
[email protected] /system ext4 ro,noatime,noauto_da_alloc,commit=1,data=ordered 0 0
[email protected] /data ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected]_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected]_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected] /storage/sdcard0 vfat rw,dirsync,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[email protected]:/ #
I can make full image by dding /dev/block/mmcblk0 but it would be better to get the parts separately.
Is there easy way to find where the boot image is located?

I checked block device sizes
/dev/block/mmcblk0p8 is the internal flash area for user, about 28G. Boot image boot loader etc must be in mmcblk0p1 - mmcblk0p7
Size of the block devices
Code:
/dev/block/mmcblk0 31244550144
/dev/block/mmcblk0boot0 2097152
/dev/block/mmcblk0boot1 2097152
/dev/block/mmcblk0p1 1024
/dev/block/mmcblk0p2 10485760
/dev/block/mmcblk0p3 10485760
/dev/block/mmcblk0p4 6291456
/dev/block/mmcblk0p5 681574400
/dev/block/mmcblk0p6 132120576
/dev/block/mmcblk0p7 1610612736
/dev/block/mmcblk0p8 28751560704
/dev/block/mmcblk1 8178892800
I got these with script
Code:
#!/system/bin/sh
command="/sdcard/busybox blockdev --getsize64"
for f in /dev/block/mm*
do
result=`$command $f`
result="$f \t $result"
echo $result
done

Via Terminal Emulator:
"su
cat /proc/partitions"
When again other command: dd if=/dev/block/(boot_partition_which_showed under /proc/partitions) of=/sdcard/boot.img

Root your device and try MtkDroidTools.
Use MTK SP_Flash_tool to flash image back.

In proc partitions there were two boot related devices listed
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
I made images from both of those but there was nothing inside the images which looked like boot image.
I found that there is /dev/bootimage
Code:
[email protected]:/ # ls -l /dev/boo*
crw-r----- root system 234, 10 2013-01-01 06:30 bootimg
I made image from that. The image is 4.3G. Very large. Anyway I found bootimage inside that. Then I made another smaller one with
Code:
# dd if=/dev/bootimg of=/sdcard/testboot.img count=12000
I can unpack that image in linux with tool unpack-MT65xx.pl. I tried to repack the exact same files without modifying. But repacking the image with repack-MT65.pl generates file which is different.

cnexpat said:
Is there easy way to find where the boot image is located?
Click to expand...
Click to collapse
Looking for same

[Q] Can't load native library. CPU arch invalid for this build

Hi,
i have problem to reflash the lates ROM for P3100.
first i install the lates rom with success, after few days i have error "Can't load native library. CPU arch invalid for this build" then my tab restart. i tried to re flash thr ROM and its success but still same problem then i flash other version ROM its success but when its booting still on the same ROM. i also try to flash stock rom using odin, its success but same problem, booting and still using SlimROM. i have no idea with this problem please help
ROM SlimKAT
Recovery : TWRP
[email protected]:/ $ ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name/
ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name/
lrwxrwxrwx root root 2014-05-16 23:08 CACHE -> /dev/block/mmcbl
k0p7
lrwxrwxrwx root root 2014-05-16 23:08 DATAFS -> /dev/block/mmcb
lk0p10
lrwxrwxrwx root root 2014-05-16 23:08 EFS -> /dev/block/mmcblk0
p1
lrwxrwxrwx root root 2014-05-16 23:08 FACTORYFS -> /dev/block/m
mcblk0p9
lrwxrwxrwx root root 2014-05-16 23:08 HIDDEN -> /dev/block/mmcb
lk0p11
lrwxrwxrwx root root 2014-05-16 23:08 KERNEL -> /dev/block/mmcb
lk0p5
lrwxrwxrwx root root 2014-05-16 23:08 MODEM -> /dev/block/mmcbl
k0p8
lrwxrwxrwx root root 2014-05-16 23:08 PARAM -> /dev/block/mmcbl
k0p4
lrwxrwxrwx root root 2014-05-16 23:08 RECOVERY -> /dev/block/mm
cblk0p6
lrwxrwxrwx root root 2014-05-16 23:08 SBL1 -> /dev/block/mmcblk
0p2
lrwxrwxrwx root root 2014-05-16 23:08 SBL2 -> /dev/block/mmcblk
0p3
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 20480 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 716800 mmcblk0p7
259 0 20480 mmcblk0p8
259 1 1433600 mmcblk0p9
259 2 12640239 mmcblk0p10
259 3 524288 mmcblk0p11
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
179 24 15724544 mmcblk1
179 25 15723520 mmcblk1p1

any idea ? seems every i install apk its success but after restart the phone the program gone, same with when i uninstall apk, when reboot the phone the program still there. whatever im done all coming back
attach recovery log

anyone?