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.
Related
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
Code:
major minor #blocks name
179 0 15388672 mmcblk0
179 1 12772 mmcblk0p1
179 2 52764 mmcblk0p2
179 3 128 mmcblk0p3
179 4 256 mmcblk0p4
179 5 512 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 16896 mmcblk0p9
179 10 13952 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 780 mmcblk0p15
179 16 2826240 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 2119680 mmcblk0p18
179 19 6144 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 10240 mmcblk0p21
179 22 10240 mmcblk0p22
179 23 6144 mmcblk0p23
179 24 3072 mmcblk0p24
179 25 8 mmcblk0p25
179 26 9216 mmcblk0p26
179 27 512000 mmcblk0p27
179 28 20480 mmcblk0p28
179 29 9728000 mmcblk0p29
Code:
lrwxrwxrwx root root 1970-01-02 04:23 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 04:23 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 04:23 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 04:23 boot -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 04:23 cache -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 04:23 carrier -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-02 04:23 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 04:23 fota -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 04:23 fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 04:23 hidden -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-02 04:23 m9kefs1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 04:23 m9kefs2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 04:23 m9kefs3 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 04:23 mdm -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 04:23 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 04:23 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 04:23 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 04:23 param -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 04:23 persdata -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-02 04:23 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 04:23 recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 04:23 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 04:23 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 04:23 sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 04:23 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 04:23 ssd -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-02 04:23 system -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 04:23 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 04:23 userdata -> /dev/block/mmcblk0p29
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
EDIT: oops problem solved using carliv image kitchen
I'm completely at a loss here trying to just make an image or mount the stock recovery partition on the F460 variant. Much thanks to anyone who looks at this...
I did the standard dd to img file and I can't open it, getting a bunch of errors (see below) when run through various disk tools. I tried to dd the exact block range which just produces the same result.
I tried mounting the recovery partition on the device but mount doesn't want to work with me.
Code:
1|[email protected]:/ # mount /dev/block/mmcblk0p21 /sdcard/recovery
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/ # mount -t ext4 /dev/block/mmcblk0p21 /sdcard/recovery
mount: Invalid argument
I booted into recovery from ADB just to see if it was even intact and it showed the stock recovery logo just fine.
Here's some (helpful??) details...
Code:
[email protected]:/ $ cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 87536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 16 mmcblk0p4
179 5 512 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 4 mmcblk0p9
179 10 1024 mmcblk0p10
179 11 512 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 512 mmcblk0p16
179 17 2048 mmcblk0p17
179 18 2044 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 32768 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 1024 mmcblk0p22
179 23 1024 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 1 mmcblk0p25
179 26 4 mmcblk0p26
179 27 3072 mmcblk0p27
179 28 512 mmcblk0p28
179 29 512 mmcblk0p29
179 30 4 mmcblk0p30
179 31 512 mmcblk0p31
259 0 512 mmcblk0p32
259 1 8 mmcblk0p33
259 2 5104 mmcblk0p34
259 3 16384 mmcblk0p35
259 4 8192 mmcblk0p36
259 5 8192 mmcblk0p37
259 6 32768 mmcblk0p38
259 7 32768 mmcblk0p39
259 8 32768 mmcblk0p40
259 9 32768 mmcblk0p41
259 10 2523136 mmcblk0p42
259 11 868352 mmcblk0p43
259 12 16384 mmcblk0p44
259 13 26480640 mmcblk0p45
259 14 188399 mmcblk0p46
179 32 4096 mmcblk0rpmb
179 64 30703616 mmcblk1
179 65 30702592 mmcblk1p1
Code:
[email protected]:/ $ ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-01-04 01:47 DDR -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-04 01:47 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-04 01:47 abootb -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-04 01:47 boot -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-04 01:47 cache -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-01-04 01:47 drm -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-04 01:47 eksst -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-04 01:47 encrypt -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-04 01:47 factory -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-04 01:47 fota -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-04 01:47 fsc -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-04 01:47 fsg -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-04 01:47 grow -> /dev/block/mmcblk0p46
lrwxrwxrwx root root 1970-01-04 01:47 laf -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-04 01:47 mdm1m9kefs1 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-04 01:47 mdm1m9kefs2 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-04 01:47 mdm1m9kefs3 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-04 01:47 mdm1m9kefsc -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-04 01:47 misc -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-04 01:47 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-04 01:47 mpt -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-04 01:47 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-04 01:47 pad1 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-04 01:47 pad2 -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-04 01:47 persist -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-04 01:47 rct -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-04 01:47 recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-04 01:47 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-04 01:47 rpmbak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-04 01:47 rpmf -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-04 01:47 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-04 01:47 sbl1b -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-04 01:47 sdi -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-04 01:47 sdibak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-04 01:47 sdif -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-04 01:47 sec -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-04 01:47 sns -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-04 01:47 spare1 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-04 01:47 spare2 -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-04 01:47 spare3 -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-01-04 01:47 ssd -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-04 01:47 system -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-04 01:47 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-04 01:47 tzbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-04 01:47 tzf -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-04 01:47 userdata -> /dev/block/mmcblk0p45
Code:
[email protected]:~/Desktop$ parted recovery.img
WARNING: You are not superuser. Watch out for permissions.
GNU Parted 2.3
Using /home/shawn/Desktop/recovery.img
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Error: /home/shawn/Desktop/recovery.img: unrecognised disk label
[email protected]:~/Desktop$ fdisk -l recovery.img
Disk recovery.img: 16 MB, 16777216 bytes
255 heads, 63 sectors/track, 2 cylinders, total 32768 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk recovery.img doesn't contain a valid partition table
[email protected]:~/Desktop$ e2fsck recovery.img
e2fsck 1.42.9 (4-Feb-2014)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open recovery.img
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
[email protected]:~/Desktop$ e2fsck -b 8192 recovery.img
e2fsck 1.42.9 (4-Feb-2014)
e2fsck: Attempt to read block from filesystem resulted in short read while trying to open recovery.img
Could this be a zero-length partition?
Hi.
I get a Nexus 7 2013. Problem is, it will not boot any rom.
Fastboot, TWRP, flash rom or factory image works fine, but i will bootloop every time with any rom.
Tried with CM14.1, CM13, AOSP, latest factory image and first factory image.
Someone has an idea? Can i log the boot somehow?
baggerbodo said:
Hi.
I get a Nexus 7 2013. Problem is, it will not boot any rom.
Fastboot, TWRP, flash rom or factory image works fine, but i will bootloop every time with any rom.
Tried wich CM14.1, CM13, AOSP, latest factory image and first factory image.
Someone has an idea? Can i log the boot somehow?
Click to expand...
Click to collapse
Hello, I think I know the problem but let's see some logs first. Start your OS and on the next bootloop turn it off and as quickly as possible turn it back on to TWRP recovery. The off/on must happen within max 2 seconds in order to preserve last_kmsg in RAM intact. Then while in TWRP attach an OTG USB drive with my get-logs.zip on it, 'install' it and post 'logs.tgz' which was created on the flashdrive.
If you don't have an OTG drive/adapter, have a look inside the zip and use ADB to get the logs manually.
That´s crazy. Now i havo no bootloops more but stuck on boot logo.
Anyway, here is my log after 15 minutes boot. (please remove .zip)
The kernel cannot communicate properly with LTE modem and constantly, repeatedly logs this sequence:
Code:
mdm_modem_ioctl: Powering on mdm id 0
mdm_do_soft_power_on: id 0: soft resetting mdm modem
It is either a software/data or hardware issue.
Apart from the 'radio' partition which you have reflashed many times, the modem also needs:
Code:
modemst1 mmcblk0p2 3MB
modemst2 mmcblk0p3 3MB
fsg mmcblk0p8 3MB
These partitions are never flashed from OS and I/we always back them up before any ROM changes on mobile phones.
I don't have the LTE N7 and can't help you if the partitions are corrupt or erased.
As for possible hardware issue I note on the pictures antenna sockets, so the modem seems to be next to SIM card reader on the daughterboard PCB. If so, then the fix is very simple. The wide silver flex cable which connects both PCBs is notoriously unreliable and needs to be re-seated on both connectors. I'd bet on it :fingers-crossed:
So you think i need a complete system dump?
Here are my partitiones.
Code:
179 0 30539776 mmcblk0
179 1 87536 mmcblk0p1
179 2 3072 mmcblk0p2
179 3 3072 mmcblk0p3
179 4 15000 mmcblk0p4
179 5 780 mmcblk0p5
179 6 780 mmcblk0p6
179 7 780 mmcblk0p7
179 8 3072 mmcblk0p8
179 9 1500 mmcblk0p9
179 10 1500 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 5120 mmcblk0p12
179 13 512 mmcblk0p13
179 14 16384 mmcblk0p14
179 15 512 mmcblk0p15
179 16 1 mmcblk0p16
179 17 1500 mmcblk0p17
179 18 2048 mmcblk0p18
179 19 5120 mmcblk0p19
179 20 512 mmcblk0p20
179 21 512 mmcblk0p21
179 22 860160 mmcblk0p22
179 23 573440 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 10240 mmcblk0p25
179 26 8 mmcblk0p26
179 27 8 mmcblk0p27
179 28 1 mmcblk0p28
179 29 32 mmcblk0p29
179 30 28180463 mmcblk0p30
Code:
drwxr-xr-x 2 root root 640 Jan 1 00:02 .
drwxr-xr-x 4 root root 700 Jan 1 00:02 ..
lrwxrwxrwx 1 root root 21 Jan 1 00:02 DDR -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Jan 1 00:02 aboot -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Jan 1 00:02 abootb -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Jan 1 00:02 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Jan 1 00:02 cache -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 20 Jan 1 00:02 fsg -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Jan 1 00:02 m9kefs1 -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 1 00:02 m9kefs2 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Jan 1 00:02 m9kefs3 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Jan 1 00:02 m9kefsc -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 Jan 1 00:02 metadata -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 Jan 1 00:02 misc -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 Jan 1 00:02 modemst1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Jan 1 00:02 modemst2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Jan 1 00:02 pad -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 20 Jan 1 00:02 persist -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Jan 1 00:02 radio -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Jan 1 00:02 recovery -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Jan 1 00:02 rpm -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Jan 1 00:02 rpmb -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 20 Jan 1 00:02 sbl1 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Jan 1 00:02 sbl2 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 1 00:02 sbl2b -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Jan 1 00:02 sbl3 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Jan 1 00:02 sbl3b -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Jan 1 00:02 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 Jan 1 00:02 system -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Jan 1 00:02 tz -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Jan 1 00:02 tzb -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Jan 1 00:02 userdata -> /dev/block/mmcblk0p30
Now i get bootloops again, please have a look in my logs.
baggerbodo said:
So you think i need a complete system dump?
Now i get bootloops again, please have a look in my logs.
Click to expand...
Click to collapse
I think you need to check the cable first.
The new logs don't offer more insights but if you are successful in capturing logcat during bootloop it would be very interesting:
http://forum.xda-developers.com/general/xda-university/universal-test-rom-build-didnt-boot-t3258818
http://forum.xda-developers.com/showpost.php?p=47172724