Related
Cwm v5.0.2.7 For LG Nitro HD (P930) /Optimus LTE
Current Status: Operational
Installation/Update Instructions:
Before installing make sure that your phone is rooted
Code:
Backup your existing recovery:
1) [COLOR="Magenta"]cat /dev/block/mmcblk0p13 > /sdcard/recovery-backup.img[/COLOR]
Flash the new recovery by:
1) Download the bc64-recovery.rar and extract it
2) Copy the extracted bc64-recovery.img to your /sdcard
3) via terminal emulator or adb shell execute:
[COLOR="Magenta"]
su
cd /sdcard
cat bc64-recovery.img > /dev/block/mmcblk0p13[/COLOR]
All Done!
Now to Boot into recovery , press the vol down+pwr button , when it asks you to factory reset , tap twice the pwr button to confirm (dont worry it wont format your device)
Screenshots:
Video:
Code:
http://www.youtube.com/watch?v=okr8PWeQ30E
ChangeLog:
Code:
v0.2 B20120124
Changes:
* Added postrecoveryboot.sh to clear out boot command
* Added Partition/fs Utils (useful for rom dev in formatting/checking ext4 fs)
-e2fsck_static
-mke2fs_static
-resize2fs_static
-tune2fs_static
v0.1 B20120120 (Initial Release)
Known Issues:
Code:
wrong timestamps
Tested On:
Code:
Atnt LG Nitro HD (P930)
LG Optimus LTE (SU640)
Thanks To:
Code:
schwin97
[email protected]
Malnilion
repherb
aquariuz23
gte460z
and everyone else who contributed to this thread :P
Download:
Code:
http://www.mediafire.com/?mnf53sxmp5aifd9
Source Code (Sorry , too lazy for github fttb):
Code:
http://www.mediafire.com/?f27d8j8d7mc8qi8
For Rom Developers:
It seems that default cwm format is messing up (due to ext4 file system) , Please use (edify) the following script to format the data and cache partition (or System)
Code:
#Format Data
/sbin/mke2fs_static -t ext4 -b 4096 /dev/block/mmcblk0p30
#Format Cache
/sbin/mke2fs_static -t ext4 -b 4096 /dev/block/mmcblk0p28
# After Format Verify the FIle System
/sbin/e2fsck_static -y /dev/block/mmcblk0p30
/sbin/e2fsck_static -y /dev/block/mmcblk0p28
Edify (To Format System):
Code:
run_program("/sbin/mke2fs_static", "-t" , "ext4" "/dev/block/mmcblk0p27");
AND
run_program("/sbin/e2fsck_static", "-y", "/dev/block/mmcblk0p27");
/proc/mtd doesn't exist...
Don't know if this any help:
http://forum.xda-developers.com/showpost.php?p=20514396&postcount=32
Images Added based on the info provided :
Code:
http://forum.xda-developers.com/showpost.php?p=20514396&postcount=32
Is this suppose to be Clockwork Mod for the Nitro? Wat's with the 5? Version 5?
Can you teach me how to make the recovery.img.
My device is LG Optimus LTE SU640 which has the most same hardware with P930.
Yes this is version 5
@belth219 ill port it for you once i get confirmation for this image
Ok,thanks.
@belth219 could you do a "cat /proc/partitions" on your cell and post its results?
Also providing the results for the above command for nitro HD would also be very usefull.
This is the result of my lu6200
Another version of p930
# su
su
# cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 3526656 mmcblk0
179 1 32768 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 5120 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 10240 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 32768 mmcblk0p14
179 15 3072 mmcblk0p15
179 16 3072 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 3072 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 8192 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 73728 mmcblk0p22
179 23 8192 mmcblk0p23
179 24 24576 mmcblk0p24
179 25 8192 mmcblk0p25
179 26 1048576 mmcblk0p26
179 27 327680 mmcblk0p27
179 28 1548288 mmcblk0p28
179 29 16384 mmcblk0p29
179 30 1024 mmcblk0p30
179 31 229376 mmcblk0p31
259 0 4096 mmcblk0p32
179 32 7774208 mmcblk1
179 33 7773184 mmcblk1p1
#
$ cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,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/mmcblk0p26 /system ext4 rw,relatime,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p1 /firmware vfat ro,relatime,fmask=0000,dmask=0000,allow_utim
e=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p28 /data ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
,noauto_da_alloc 0 0
/dev/block/mmcblk0p12 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=orde
red 0 0
/dev/block/mmcblk0p27 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordere
d 0 0
/dev/block/mmcblk0p29 /mpt ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p31 /lgumsg ext4 rw,nosuid,nodev,relatime,barrier=1,data=order
ed 0 0
/dev/block/mmcblk0p23 /mm ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0
0
/dev/block/mmcblk0p14 /system/etc/firmware/misc_mdm vfat ro,relatime,fmask=0000,
dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,e
rrors=remount-ro 0 0
My phone is LU6200,too. Could you tell me if I can install this mod on my phone? The only difference of 2 device is the CPU
I dont think it would work on your device as im sure it has diffrent kernel , upload your boot.img , i will port it once i get nitro hd confirmation
SU640
# cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 2111 loop0
179 0 3526656 mmcblk0
179 1 32768 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 5120 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 10240 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 32768 mmcblk0p14
179 15 3072 mmcblk0p15
179 16 3072 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 3072 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 8192 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 73728 mmcblk0p22
179 23 8192 mmcblk0p23
179 24 24576 mmcblk0p24
179 25 8192 mmcblk0p25
179 26 1024 mmcblk0p26
179 27 860160 mmcblk0p27
179 28 327680 mmcblk0p28
179 29 3072 mmcblk0p29
179 30 1957638 mmcblk0p30
179 31 16384 mmcblk0p31
259 0 2048 mmcblk0p32
179 32 15622144 mmcblk1
179 33 15618048 mmcblk1p1
254 0 2110 dm-0
# cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,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/mmcblk0p27 /system ext4 ro,relatime,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p22 /tombstones ext4 rw,nosuid,nodev,relatime,barrier=1,data=o
rdered 0 0
/dev/block/mmcblk0p1 /firmware vfat ro,relatime,fmask=0000,dmask=0000,allow_utim
e=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p30 /data ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
,noauto_da_alloc 0 0
/dev/block/mmcblk0p12 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=orde
red 0 0
/dev/block/mmcblk0p28 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordere
d 0 0
/dev/block/mmcblk0p31 /mpt ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p23 /mm ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0
0
/dev/block/mmcblk0p14 /system/etc/firmware/misc_mdm vfat ro,relatime,fmask=0000,
dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,e
rrors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,tz=UTC,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,tz=UTC,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.cyandroid.pianofull-1 vfat ro,dirsync,nosuid,nodev
,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shor
tname=mixed,utf8,tz=UTC,errors=remount-ro 0 0
OK...
I just ran 'cat /dev/zero > /dev/block/mmcblk0p27', remounted my system partition as read/write and copied the recovery.img into the directory. Just rebooted in hopes it will flash the recovery image to the recovery partition p27 above. Will now attempt rebooting into recovery to see if anything happened...
---------- Post added at 09:05 AM ---------- Previous post was at 09:01 AM ----------
Upon using anreboot to boot into recovery I get...
Code:
Enter the fastboot...
Enter the fastboot...
Long time no see!
And the LG logo beneath it... It also attempted to install a new driver 'android', but couldn't find it on my computer. Very excited that we are moving closer to getting a 'real' recovery mode on the phone...
Now to see if I can reboot normally?
---------- Post added at 09:09 AM ---------- Previous post was at 09:05 AM ----------
And it still boots normally and is fully functional when it does boot!!! Good progress so far. Now, does anyone know how to determine the driver it is looking for? I think if I find the right driver I can get into fastboot mode and do anything else that is necessary?
schwin97 said:
OK...
I just ran 'cat /dev/zero > /dev/block/mmcblk0p27', remounted my system partition as read/write and copied the recovery.img into the directory. Just rebooted in hopes it will flash the recovery image to the recovery partition p27 above. Will now attempt rebooting into recovery to see if anything happened...
---------- Post added at 09:05 AM ---------- Previous post was at 09:01 AM ----------
Upon using anreboot to boot into recovery I get...
Code:
Enter the fastboot...
Enter the fastboot...
Long time no see!
And the LG logo beneath it... It also attempted to install a new driver 'android', but couldn't find it on my computer. Very excited that we are moving closer to getting a 'real' recovery mode on the phone...
Now to see if I can reboot normally?
Click to expand...
Click to collapse
Why did you ran cat /dev/zero > /dev/block/mmcblk0p27?
as of this http://forum.xda-developers.com/showpost.php?p=20514396&postcount=32 post your recovery partition should be /dev/block/mmcblk0p27
so To be me steps would have been:
1) Backing up recovery partition using dd
2) Remounting System partiton as read write
3) copying recovery.img to /system and flashing the recovery.img
4) booting into recovery
For fastboot you should have andriod sdk installed , get it at :
Code:
http://developer.android.com/sdk/download.html
I agree, but when I miss the part about putting the recovery image in the system directory for it to automatically reflash, I started running the steps to flash the recovery image as people flash the boot image...
An extra step that luckily didn't have any bad consequences...
---------- Post added at 09:18 AM ---------- Previous post was at 09:16 AM ----------
bytecode64 said:
For fastboot you should have andriod sdk installed , get it at :
Code:
http://developer.android.com/sdk/download.html
Click to expand...
Click to collapse
I have the sdk installed - but my laptop is asking for a driver - is the driver within the sdk download? If I don't give it the driver then it says the device didn't get installed correctly and fastboot doesn't see it.
what about USB drivers and Modem?
Did you installed http://s3.amazonaws.com/lgforum.com/resources/assets/680/original/LGP930.zip?1322664514
?
I have uploaded my boot.img & recovery.img to dropbox.
But I can not post any links now.It needs 8 posts.
Sure did. I have the drivers that are needed when the phone boots up normally? Just when it boots up in this new recovery mode that it is asking for a new driver? It shouldn't be asking for anything new, but it is... Another question - after it loads up the new recovery image from the /system directory should it remove the recovery image? If so, then if the recovery image is still in the system directory we may have a problem?
---------- Post added at 09:44 AM ---------- Previous post was at 09:39 AM ----------
As I had thought - recovery.img is still in the system directory... Does this indicate a problem?
schwin97 said:
I have the sdk installed - but my laptop is asking for a driver - is the driver within the sdk download? If I don't give it the driver then it says the device didn't get installed correctly and fastboot doesn't see it.
Click to expand...
Click to collapse
You should install the LGMobile update which can be downloaded from LG official website.
That is a useful tool.
Any help will be appreciated :good:
As you know backup and restore partitions can be done using dd command in linux.
I know it's not noob friendly, but since custom kernels and recoveries raises flash counter, it's a good idea.
rotohammer has made a detailed explanation here for Galaxy Tab.
So all we need the block device list for note 2
/dev/block/mmcblk0 Whole Internal Storage
/dev/block/mmcblk0p1 4194kB BOTA0
/dev/block/mmcblk0p2 4194kB BOTA1
/dev/block/mmcblk0p3 21.0MB EFS
/dev/block/mmcblk0p4 4194kB m9kefs1
/dev/block/mmcblk0p5 4194kB m9kefs2
/dev/block/mmcblk0p6 4194kB m9kefs3
/dev/block/mmcblk0p7 8389kB PARAM
/dev/block/mmcblk0p8 8389kB BOOT (Kernel)
/dev/block/mmcblk0p9 8389kB RECOVERY
/dev/block/mmcblk0p10 92.3MB RADIO (Modem)
/dev/block/mmcblk0p11 4194kB TOMBSTONES
/dev/block/mmcblk0p12 1434MB CACHE
/dev/block/mmcblk0p13 2147MB SYSTEM
/dev/block/mmcblk0p14 587MB HIDDEN
/dev/block/mmcblk0p15 8389kB OTA
/dev/block/mmcblk0p16 11.4GB USERDATA (User Accessible Storage and /DATA folder)
[email protected] said:
As you know backup and restore partitions can be done using dd command in linux.
I know it's not noob friendly, but since custom kernels and recoveries raises flash counter, it's a good idea.
rotohammer has made a detailed explanation here for Galaxy Tab.
So I need all the block device list for note 2
So far I know
/dev/block/mmcblk0p13 = /system
/dev/block/mmcblk0p12 = /cache
/dev/block/mmcblk0p16 = /data
/dev/block/mmcblk0p3 = /efs
/dev/block/mmcblk0p9 = /recovery
/dev/block/mmcblk0p8 = /boot (kernel)
I'm not a linux expert, can somebody confirm/correct these?
Click to expand...
Click to collapse
Perhaps you should find out what the mount command does before you start using dd to read and write directly to the partitions. These sort of commands don't take prisoners
I said I'm not a linux expert, it doesn't mean I'm totally noob. I'm using Lubuntu on my netbook.
I'm well aware of risks, I'm using dd on PC time to time.
Mount only shows mounted partitions. I'm asking those partitions. I couldn't find a full partitions list anywhere
There are many partitions and I want to know what they are
Code:
cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 8192 mmcblk0p7
179 8 8192 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 90112 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 1400832 mmcblk0p12
179 13 2097152 mmcblk0p13
179 14 573440 mmcblk0p14
179 15 8192 mmcblk0p15
259 0 11141120 mmcblk0p16
179 16 62367744 mmcblk1
179 17 62351360 mmcblk1p1
[email protected]:/ # ls -l /dev/block/mmcblk*
ls -l /dev/block/mmcblk*
brw------- root root 179, 0 2013-04-01 00:14 mmcblk0
brw------- root root 179, 1 2013-04-01 00:14 mmcblk0p1
brw-rw---- system radio 179, 10 2013-04-01 00:14 mmcblk0p10
brw-rw---- system radio 179, 11 2013-04-01 00:14 mmcblk0p11
brw------- root root 179, 12 2013-04-01 00:14 mmcblk0p12
brw------- root root 179, 13 2013-04-01 00:14 mmcblk0p13
brw------- root root 179, 14 2013-04-01 00:14 mmcblk0p14
brw------- root root 179, 15 2013-04-01 00:14 mmcblk0p15
brw------- root root 259, 0 2013-04-01 00:14 mmcblk0p16
brw------- root root 179, 2 2013-04-01 00:14 mmcblk0p2
brw------- root root 179, 3 2013-04-01 00:14 mmcblk0p3
brw-rw---- system radio 179, 4 2013-04-01 00:14 mmcblk0p4
brw-rw---- system radio 179, 5 2013-04-01 00:14 mmcblk0p5
brw-rw---- system radio 179, 6 2013-04-01 00:14 mmcblk0p6
brw-rw---- system root 179, 7 2013-04-01 00:14 mmcblk0p7
brw------- root root 179, 8 2013-04-01 00:14 mmcblk0p8
brw------- root root 179, 9 2013-04-01 00:14 mmcblk0p9
brw------- root root 179, 16 2013-04-01 00:14 mmcblk1
brw------- root root 179, 17 2013-04-01 00:14 mmcblk1p1
For some reason listing partitions by-label doesn't work either for android or block devices.
Code:
[email protected]:/ # ls -l /dev/block/by-label
ls -l /dev/block/by-label
/dev/block/by-label: No such file or directory
[email protected] said:
...So far I know
/dev/block/mmcblk0p13 = /system
/dev/block/mmcblk0p12 = /cache
/dev/block/mmcblk0p16 = /data
/dev/block/mmcblk0p3 = /efs
/dev/block/mmcblk0p9 = /recovery
/dev/block/mmcblk0p8 = /boot (kernel)
I'm not a linux expert, can somebody confirm/correct these?
Click to expand...
Click to collapse
These partitions are correct. Radio/modem partition is missing. /dev/block/mmcblk0p10 = /modem/baseband/radio
Edit:
For the list of all partitions, use 'parted' command.
Partitions from the international GNote2 N7100 are:
Code:
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\cargo>cd tools
C:\Users\cargo\tools>adb shell
~ # ←[6nparted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC VTU00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 37.7MB 4194kB m9kefs1
5 37.7MB 41.9MB 4194kB m9kefs2
6 41.9MB 46.1MB 4194kB m9kefs3
7 46.1MB 54.5MB 8389kB PARAM
8 54.5MB 62.9MB 8389kB BOOT
9 62.9MB 71.3MB 8389kB RECOVERY
10 71.3MB 164MB 92.3MB RADIO
11 164MB 168MB 4194kB TOMBSTONES
12 168MB 1602MB 1434MB ext4 CACHE
13 1602MB 3750MB 2147MB ext4 SYSTEM
14 3750MB 4337MB 587MB ext4 HIDDEN
15 4337MB 4345MB 8389kB OTA
16 4345MB 15.8GB 11.4GB ext4 USERDATA
(parted)
cargobr151 said:
These partitions are correct. Radio/modem partition is missing. /dev/block/mmcblk0p10 = /modem/baseband/radio
Edit:
For the list of all partitions, use 'parted' command.
Partitions from the international GNote2 N7100 are:
Code:
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\cargo>cd tools
C:\Users\cargo\tools>adb shell
~ # ←[6nparted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC VTU00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 37.7MB 4194kB m9kefs1
5 37.7MB 41.9MB 4194kB m9kefs2
6 41.9MB 46.1MB 4194kB m9kefs3
7 46.1MB 54.5MB 8389kB PARAM
8 54.5MB 62.9MB 8389kB BOOT
9 62.9MB 71.3MB 8389kB RECOVERY
10 71.3MB 164MB 92.3MB RADIO
11 164MB 168MB 4194kB TOMBSTONES
12 168MB 1602MB 1434MB ext4 CACHE
13 1602MB 3750MB 2147MB ext4 SYSTEM
14 3750MB 4337MB 587MB ext4 HIDDEN
15 4337MB 4345MB 8389kB OTA
16 4345MB 15.8GB 11.4GB ext4 USERDATA
(parted)
Click to expand...
Click to collapse
Thank you a lot, parted is not working on mine. Probably busybox related?
Edit: Nevermind I found the executable file of parted . Worked fine. Thanks again.
You must have installed a custom recovery. (with parted command included)
Like cwm or twrp v2.4.4.0. I use twrp v2.4.4.0.
@OP updated my thread with this thread info...You can visit here
@[email protected]
So continue here
Question is if we makes tar file form dump file we have created like system.img, can we flash it with odin?
dr.ketan said:
@[email protected]
So continue here
Question is if we makes tar file form dump file we have created like system.img, can we flash it with odin?
Click to expand...
Click to collapse
Roger that
here http://forum.xda-developers.com/showthread.php?t=1777579 @das7982 well explained the instructions for Galaxy SIII
According to his post, he's recommending to make an ODIN package from only system.img
To make system.img of note 2
Code:
dd if=/dev/block/mmcblk0p13 of=/storage/extSdCard/system.img bs=4096
Here we need a linux pc or Cygwin for Windows. If we going to use Cygwin, we need to install it along with tar, md5sum commands
Code:
tar -H ustar -c system.img > system.img.tar
Then we need to make Md5 checksum
Code:
md5sum -t system.img.tar >> system.img.tar
rename it
Code:
mv system.img.tar system.img.tar.md5
I haven't tried this yet but I'll try soon
I have already made this and also in try to test it.
Sent from my GT-N7100 using xda premium
---------- Post added at 11:00 PM ---------- Previous post was at 10:55 PM ----------
I have read it, I think it shouldn't raise counter unless we have custom recovery /kernel
B'coz I don't think custom tar will raise counter, i am regularly extract recovery and kernel from stock and packing it separately in tar, it never raised counter.
Sent from my GT-N7100 using xda premium
dr.ketan said:
I have already made this and also in try to test it.
Sent from my GT-N7100 using xda premium
---------- Post added at 11:00 PM ---------- Previous post was at 10:55 PM ----------
I have read it, I think it shouldn't raise counter unless we have custom recovery /kernel
B'coz I don't think custom tar will raise counter, i am regularly extract recovery and kernel from stock and packing it separately in tar, it never raised counter.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
You're correct, stock kernel and recovery shouldn't increase the flash counter.
To backup /data we can use
Code:
adb shell
stop
busybox tar -cZvf /storage/extSdCard/data.ext4.tar --exclude media --exclude dalvik-cache /data
reboot
To restore
Code:
adb shell
stop
busybox tar -xvf /storage/extSdCard/data.ext4.tar -C /
reboot
Hi guys,
I have a Linux partition on my sdcard and I want to have it mount at boot. I checked out this page( a page that I am not permitted to link to that might or might not contain this text "wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images") on how to do it and I have put together a boot.img file I want to flash. The instructions call for this maneuver:
# cat /dev/zero > /dev/mtd/mtd2
write: No space left on device [this is ok, you can ignore]
# flash_image boot /sdcard/mynewimage.img
but the Note 8 doesn't have a MTD device:
[email protected]:/storage/sdcard0 # ls -l /dev/mtd*
/dev/mtd*: No such file or directory
what do I do?
mounting at boot time
Hi guys,
It has been about a week since I posted this question here. The reason I am trying to edit the boot.img file is to add a persistent mount point to a Linux partition on my sdcard. After fussing with several third party kernels and not succeeding in creating my own working ramdisk, I tried adding init.d support and putting the mount command in a startup script. It looks like the sdcard is not mounted by the time the init process is finished. I tried editing the vold.fstab file. I tried adding this line to the end:
dev_mount debian /storage/extSdCard/debian 50 /devices/platform/s3c-sdhci.2/mmc_host/mmc1/
No dice.
what is the format of this file? Where can I find a man page or a doc?
These are my partitions:
1|[email protected]:/sdcard # cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 32768 mmcblk0p7
179 8 1572864 mmcblk0p8
179 9 2621440 mmcblk0p9
179 10 573440 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 10518528 mmcblk0p12
179 32 4096 mmcblk0boot1
179 16 4096 mmcblk0boot0
179 48 31166976 mmcblk1
179 49 27343750 mmcblk1p1
179 50 2929687 mmcblk1p2
[email protected]:/sdcard #
these have changed since I updated to 4.2.2 about a week ago. Is there some way to have the config persist through device upgrades?
Hey guys,
Here is the mountpoint information for Xperia M I am still figuring out which of these goes for which partitions I will update if I find
Code:
PERM UID GID DATE PATH
lrwxrwxrwx root root 1970-07-11 15:19 FOTAKernel -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-07-11 15:19 LTALabel -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-07-11 15:19 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-07-11 15:19 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-07-11 15:19 alt -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-07-11 15:19 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-07-11 15:19 cache -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-07-11 15:19 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-07-11 15:19 modem -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-07-11 15:19 modemst1 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-07-11 15:19 modemst2 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-07-11 15:19 persist -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-07-11 15:19 ramdump -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-07-11 15:19 rpm -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-07-11 15:19 s1sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-07-11 15:19 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-07-11 15:19 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-07-11 15:19 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-07-11 15:19 system -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-07-11 15:19 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-07-11 15:19 userdata -> /dev/block/mmcblk0p27
Huge thanks to @mbc07
Code:
major minor #blocks name
179 0 3866624 mmcblk0
179 1 2048 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 256 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 128 mmcblk0p8
179 9 256 mmcblk0p9
179 10 256 mmcblk0p10
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 512 mmcblk0p13
179 14 512 mmcblk0p14
179 15 512 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 20480 mmcblk0p17
179 18 65536 mmcblk0p18
179 19 3072 mmcblk0p19
179 20 3072 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 5120 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 4096 mmcblk0p24
179 25 1228800 mmcblk0p25
179 26 256000 mmcblk0p26
179 27 2183151 mmcblk0p27
179 32 7822336 mmcblk1
179 33 7821312 mmcblk1p1
Just use ls -l /dev/block/platform/msm_sdcc.1/by-name
Layout:
Code:
PERM UID GID DATE PATH
lrwxrwxrwx root root 1970-07-11 15:19 FOTAKernel -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-07-11 15:19 LTALabel -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-07-11 15:19 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-07-11 15:19 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-07-11 15:19 alt -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-07-11 15:19 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-07-11 15:19 cache -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-07-11 15:19 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-07-11 15:19 modem -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-07-11 15:19 modemst1 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-07-11 15:19 modemst2 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-07-11 15:19 persist -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-07-11 15:19 ramdump -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-07-11 15:19 rpm -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-07-11 15:19 s1sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-07-11 15:19 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-07-11 15:19 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-07-11 15:19 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-07-11 15:19 system -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-07-11 15:19 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-07-11 15:19 userdata -> /dev/block/mmcblk0p27
Here you are a bit more information.
Also I have dumps of all these partitions and GPT backup.
If someone need to restore something – send PM (C1905 btw).
Code:
parted /dev/block/mmcblk0
print
Number Start End Size File system Name
1 131kB 2228kB 2097kB TA
2 2228kB 2359kB 131kB sbl1
3 2359kB 2621kB 262kB sbl2
4 2621kB 2884kB 262kB s1sbl2
5 2884kB 3408kB 524kB sbl3
6 3408kB 3932kB 524kB aboot
7 3932kB 4456kB 524kB tz
8 4456kB 4588kB 131kB alt_sbl1
9 4588kB 4850kB 262kB alt_sbl2
10 4850kB 5112kB 262kB alt_s1sbl2
11 5112kB 5636kB 524kB alt_sbl3
12 5636kB 6160kB 524kB alt_aboot
13 6160kB 6685kB 524kB alt_tz
14 6685kB 7209kB 524kB rpm
15 7209kB 7733kB 524kB alt_rpm
16 8389kB 25.2MB 16.8MB ext4 LTALabel
17 25.2MB 46.1MB 21.0MB boot
18 46.1MB 113MB 67.1MB fat16 modem
19 113MB 116MB 3146kB modemst1
20 117MB 121MB 3146kB modemst2
21 122MB 125MB 3146kB fsg
22 125MB 130MB 5243kB ramdump
23 130MB 147MB 16.8MB FOTAKernel
24 147MB 151MB 4194kB ext2 persist
25 151MB 1514MB 1363MB ext4 system
26 1514MB 1724MB 210MB ext4 cache
27 1724MB 3909MB 2185MB ext4 userdata
---------------
gdisk /dev/block/mmcblk0
p
Disk /dev/block/mmcblk0: 7733248 sectors, 3.7 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Partition table holds up to 27 entries
First usable sector is 34, last usable sector is 7733214
Partitions will be aligned on 256-sector boundaries
Total free space is 103902 sectors (50.7 MiB)
Number Start (sector) End (sector) Size Code Name
1 256 4351 2.0 MiB FFFF TA
2 4352 4607 128.0 KiB FFFF sbl1
3 4608 5119 256.0 KiB FFFF sbl2
4 5120 5631 256.0 KiB FFFF s1sbl2
5 5632 6655 512.0 KiB FFFF sbl3
6 6656 7679 512.0 KiB FFFF aboot
7 7680 8703 512.0 KiB FFFF tz
8 8704 8959 128.0 KiB FFFF alt_sbl1
9 8960 9471 256.0 KiB FFFF alt_sbl2
10 9472 9983 256.0 KiB FFFF alt_s1sbl2
11 9984 11007 512.0 KiB FFFF alt_sbl3
12 11008 12031 512.0 KiB FFFF alt_aboot
13 12032 13055 512.0 KiB FFFF alt_tz
14 13056 14079 512.0 KiB FFFF rpm
15 14080 15103 512.0 KiB FFFF alt_rpm
16 16384 49151 16.0 MiB 8300 LTALabel
17 49152 90111 20.0 MiB FFFF boot
18 90112 221183 64.0 MiB 0700 modem
19 221184 227327 3.0 MiB FFFF modemst1
20 229376 235519 3.0 MiB FFFF modemst2
21 237568 243711 3.0 MiB FFFF fsg
22 243712 253951 5.0 MiB FFFF ramdump
23 253952 286719 16.0 MiB FFFF FOTAKernel
24 286720 294911 4.0 MiB 8300 persist
25 294912 2957311 1.3 GiB 8300 system
26 2957312 3366911 200.0 MiB 8300 cache
27 3366912 7634910 2.0 GiB 8300 userdata
---------------
gdisk /dev/block/mmcblk0
x
o
Disk size is 7733248 sectors (3.7 GiB)
MBR disk identifier: 0x00000000
MBR partitions:
Number Boot Start Sector End Sector Status Code
1 1 7733247 primary 0xEE
---------------
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 3959 MB, 3959422976 bytes
95 heads, 61 sectors/track, 1334 cylinders
Units = cylinders of 5795 * 512 = 2967040 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1335 3866623+ ee EFI GPT
---------------
df
Filesystem Size Used Free Blksize
/dev 430.6M 128.0K 430.4M 4096
/sys/fs/cgroup 430.6M 12.0K 430.5M 4096
/mnt/asec 430.6M 0.0K 430.6M 4096
/mnt/obb 430.6M 0.0K 430.6M 4096
/mnt/fuse 430.6M 0.0K 430.6M 4096
/system 1.3G 374.4M 907.4M 4096
/data 2.0G 1.5G 555.2M 4096
/cache 197.0M 68.2M 128.8M 4096
/persist 3.9M 84.0K 3.8M 4096
/lta-label 15.8M 4.1M 11.7M 4096
/firmware 64.0M 44.1M 19.9M 16384
/mnt/shell/emulated 2.0G 1.5G 555.2M 4096
/storage/emulated/legacy 2.0G 1.5G 555.2M 4096
/mnt/media_rw/sdcard1 14.8G 11.6G 3.3G 8192
/storage/sdcard1 14.8G 11.6G 3.3G 8192
---------------
mount
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/LTALabel /lta-label ext4 ro,seclabel,nosuid,nodev,noexec,noatime,nobarrier,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:33 /mnt/media_rw/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,cod
epage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
I am just trying to get a rough feel for the demand that exists for getting CM-12 on the T-Mobile variant of the Tab S 10.5.
I have one that I picked up, and I have not done much with it. I have been kicking around the idea of trying to get CM-12.0 up on it, but I dont want to soak a ton of time into if there is not a decent demand for it.
Anyway guys, let me know!
Sounds like a great idea, I don't have one yet, but would definitely consider picking one up if CM12 came out.
This is all I really want out of this tablet. Let me know if you're seriously thinking about doing it because I'll kick you a few bucks if its doable.
do it please!
I would also shoot you some money I get paid on Friday and would love to donate to getting my tablet rooted
Yes, yes please.
I have the T-Mobile variant and would really appreciate the effort. I, too, would be happy to kick a few bucks your way for the trouble.
It would be amazing to have an AOSP option for it without shutting out LTE.
Please. I am so ready for 12.
Before you try does the Tmobile variant have an unlockable bootloader if it does its going to be a brand new bring up none of the work for the t805 (Exynos Galaxy tab S 10.5 LTE) will work because the US LTE variants have Qualcomm chipsets you would have to base the work off of mondrianlte (Galaxy Tab Pro 8.0 LTE)
deadman96385 said:
Before you try does the Tmobile variant have an unlockable bootloader if it does its going to be a brand new bring up none of the work for the t805 (Exynos Galaxy tab S 10.5 LTE) will work because the US LTE variants have Qualcomm chipsets you would have to base the work off of mondrianlte (Galaxy Tab Pro 8.0 LTE)
Click to expand...
Click to collapse
T807T has unlocked bootloader (T-Mobile device). Specs are exactly the same as T805 exynos. The only thing that's different is that it won't connect to Lte and such since its an T-Mobile device from what I heard.
T807P= Sprint Tab S with Snapdragon. Unlocked bootloader too.
Hopefully this helps!
DUHAsianSKILLZ said:
T807T has unlocked bootloader (T-Mobile device). Specs are exactly the same as T805 exynos. The only thing that's different is that it won't connect to Lte and such since its an T-Mobile device from what I heard.
T807P= Sprint Tab S with Snapdragon. Unlocked bootloader too.
Hopefully this helps!
Click to expand...
Click to collapse
Sweet did not know i will take a peek at the kernel source for the tmobile and see whats needed to add support for it in my kernel
Edit: Took a quick peek its using the gpu that all the other tab S's use except the chagalllte and its not using the broadcom wifi cob for whatever reason
Edit 2: There you go kernel support right away (Was not hard at all it only needed a new defconfig, i did not find any other differences kernel source wise)
https://github.com/LiquidSmooth-Dev...mmit/26f98a28280b72c135c81a0304152f550ffe9603
Edit 3: Now all you need is some basic edits to the chagalllte tree to change it too chagalltmo
Edit 4: Basic Device Tree: https://github.com/deadman96385/android_device_samsung_chagalltmo
I would need someone who owns it too pull the system partition not in img form though to make somthing that will actually work
deadman96385 said:
Sweet did not know i will take a peek at the kernel source for the tmobile and see whats needed to add support for it in my kernel
Edit: Took a quick peek its using the gpu that all the other tab S's use except the chagalllte and its not using the broadcom wifi cob for whatever reason
Edit 2: There you go kernel support right away (Was not hard at all it only needed a new defconfig, i did not find any other differences kernel source wise)
https://github.com/LiquidSmooth-Dev...mmit/26f98a28280b72c135c81a0304152f550ffe9603
Edit 3: Now all you need is some basic edits to the chagalllte tree to change it too chagalltmo
Edit 4: Basic Device Tree: https://github.com/deadman96385/android_device_samsung_chagalltmo
I would need someone who owns it too pull the system partition not in img form though to make somthing that will actually work
Click to expand...
Click to collapse
Tell me what to do and I will. To give you an idea of my skill level - I have made kernel edits before from guides and can sometimes get away with smali changes. My device is rooted and I am not worried about warranty voids. TWRP recovery only as far as I know.
In fact, if you could get Liquidsmooth working too I would be thrilled to pieces. I love that rom! I will help you test both and report any bugs I find.
thats good news if you are going to work on an exynos based tablet. this way cm12 can support other exynos models too .. i have a 805y model.
You will need to do section 1 and 2 and pull the system partition like they do there and make sure to also right down the partition layout and sizes http://forum.xda-developers.com/showthread.php?t=2450045
deadman96385 said:
You will need to do section 1 and 2 and pull the system partition like they do there and make sure to also right down the partition layout and sizes http://forum.xda-developers.com/showthread.php?t=2450045
Click to expand...
Click to collapse
Code:
s[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
253 0 1048576 vnswap0
179 0 15388672 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 1024 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 10240 mmcblk0p9
259 2 12288 mmcblk0p10
259 3 10240 mmcblk0p11
259 4 1024 mmcblk0p12
259 5 49152 mmcblk0p13
259 6 1024 mmcblk0p14
259 7 1024 mmcblk0p15
259 8 12288 mmcblk0p16
259 9 4096 mmcblk0p17
259 10 3719168 mmcblk0p18
259 11 512000 mmcblk0p19
259 12 10240 mmcblk0p20
259 13 10985472 mmcblk0p21
179 24 4096 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
[email protected]:/ $ ls -al /dev/block/platform/dw_mmc.0/by-name
ls -al /dev/block/platform/dw_mmc.0/by-name
lrwxrwxrwx root root 2015-06-21 13:21 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-06-21 13:21 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-06-21 13:21 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-06-21 13:21 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-06-21 13:21 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-06-21 13:21 CDMA-RADIO -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-06-21 13:21 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-06-21 13:21 HIDDEN -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-06-21 13:21 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-06-21 13:21 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-06-21 13:21 PERSDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-06-21 13:21 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-06-21 13:21 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-06-21 13:21 RESERVED2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-06-21 13:21 SYSTEM -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-06-21 13:21 TDATA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-06-21 13:21 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-06-21 13:21 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-06-21 13:21 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-06-21 13:21 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-06-21 13:21 m9kefs3 -> /dev/block/mmcblk0p6
I am currently uploading the .img dump and will edit this post when it is up. If you need in another format you'll have to let me know how to go about that.
mmolitor87 said:
Code:
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
253 0 1048576 vnswap0
179 0 15388672 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 1024 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 10240 mmcblk0p9
259 2 12288 mmcblk0p10
259 3 10240 mmcblk0p11
259 4 1024 mmcblk0p12
259 5 49152 mmcblk0p13
259 6 1024 mmcblk0p14
259 7 1024 mmcblk0p15
259 8 12288 mmcblk0p16
259 9 4096 mmcblk0p17
259 10 3719168 mmcblk0p18
259 11 512000 mmcblk0p19
259 12 10240 mmcblk0p20
259 13 10985472 mmcblk0p21
179 24 4096 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
[email protected]:/ $ ls -al /dev/block/platform/dw_mmc.0/by-name
ls -al /dev/block/platform/dw_mmc.0/by-name
lrwxrwxrwx root root 2015-06-21 13:21 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-06-21 13:21 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-06-21 13:21 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-06-21 13:21 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-06-21 13:21 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-06-21 13:21 CDMA-RADIO -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-06-21 13:21 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-06-21 13:21 HIDDEN -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-06-21 13:21 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-06-21 13:21 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-06-21 13:21 PERSDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-06-21 13:21 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-06-21 13:21 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-06-21 13:21 RESERVED2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-06-21 13:21 SYSTEM -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-06-21 13:21 TDATA -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-06-21 13:21 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-06-21 13:21 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-06-21 13:21 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-06-21 13:21 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-06-21 13:21 m9kefs3 -> /dev/block/mmcblk0p6
I am currently uploading the .img dump and will edit this post when it is up. If you need in another format you'll have to let me know how to go about that.
Click to expand...
Click to collapse
I have updated the tree with the partition sizes for your variant in theory it should build now i will be gone for 6 days so i will work on it again then.
deadman96385 said:
I have updated the tree with the partition sizes for your variant in theory it should build now i will be gone for 6 days so i will work on it again then.
Click to expand...
Click to collapse
https://mega.co.nz/#!ikEGFByQ!ye01JD1anD6xNItVJXdd69YN2uTFhkEkxrQdVmsaKeY
This is the .img file! Let me know if you need anything else for it. I'm excited to get flashing.
mmolitor87 said:
https://mega.co.nz/#!ikEGFByQ!ye01JD1anD6xNItVJXdd69YN2uTFhkEkxrQdVmsaKeY
This is the .img file! Let me know if you need anything else for it. I'm excited to get flashing.
Click to expand...
Click to collapse
Thanks that helped, sadly i have to go before my build finishes but if it does it will copy the build to the link below so give it a few hours after this post for it too appear if it doesn't i'll fix it when i get back had to do some hacky kernel work.
http://www.drdevs.com/devs/teamliquid/Test/
deadman96385 said:
Thanks that helped, sadly i have to go before my build finishes but if it does it will copy the build to the link below so give it a few hours after this post for it too appear if it doesn't i'll fix it when i get back had to do some hacky kernel work.
http://www.drdevs.com/devs/teamliquid/Test/
Click to expand...
Click to collapse
Glad it helped! I will keep an eye out for it. Nothing just yet. I can't wait...this would be the first AOSP rom for this variant as far as I'm aware!
mmolitor87 said:
Glad it helped! I will keep an eye out for it. Nothing just yet. I can't wait...this would be the first AOSP rom for this variant as far as I'm aware!
Click to expand...
Click to collapse
Another interested t807t user here. Would help with testing. Surprised to find that CM12 isn't already a thing on this device. We need more heroes to continue this quest
Nice to see CM12 coming to this device.
I am waiting patiently for this. I have a question. Can I install the other variant roms on this device as well? I am ok with no lte.