Hi all
This thread is based on what I learned in an HTC One S thread (http://forum.xda-developers.com/showthread.php?t=1674202)
OK so I have found the location where the CID and IMEI are stored in /dev/block/mmcblk0 at offset 00a00000
00a0000 [email protected]H3G__00135304xxxxxxxxxx
However, when I try to dump the file to SCDARD with
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0
the command never finishes (I broke out after about 5 minutes with a 4GB file sitting on the SDCARD, which I assume is incomplete.
I also dd most of the part "pxx" files but none of them contained the CID & IMEI. ;(
[email protected]:/dev/block # ls -l
ls -l
brw------- root root 254, 0 2012-06-05 16:14 dm-0
brw------- root root 254, 1 2012-06-05 16:14 dm-1
brw------- root root 254, 2 2012-06-05 16:14 dm-2
brw------- root root 254, 3 2012-06-05 16:14 dm-3
brw------- root root 7, 0 2012-06-05 15:34 loop0
brw------- root root 7, 1 2012-06-05 15:34 loop1
brw------- root root 7, 2 2012-06-05 15:34 loop2
brw------- root root 7, 3 2012-06-05 15:34 loop3
brw------- root root 7, 4 2012-06-05 15:34 loop4
brw------- root root 7, 5 2012-06-05 15:34 loop5
brw------- root root 7, 6 2012-06-05 15:34 loop6
brw------- root root 7, 7 2012-06-05 15:34 loop7
brw------- root root 179, 0 2012-06-05 15:34 mmcblk0
brw------- root root 179, 1 2012-06-05 15:34 mmcblk0p1
brw------- root root 179, 10 2012-06-05 15:34 mmcblk0p10
brw------- root root 179, 11 2012-06-05 15:34 mmcblk0p11
brw------- root root 179, 12 2012-06-05 15:34 mmcblk0p12
brw------- root root 179, 13 2012-06-05 15:34 mmcblk0p13
brw------- root root 179, 14 2012-06-05 15:34 mmcblk0p14
brw------- root root 179, 15 2012-06-05 15:34 mmcblk0p15
brw------- root root 179, 16 2012-06-05 15:34 mmcblk0p16
brw------- root root 179, 17 2012-06-05 15:34 mmcblk0p17
brw------- root root 179, 18 2012-06-05 15:34 mmcblk0p18
brw------- root root 179, 19 2012-06-05 15:34 mmcblk0p19
brw------- root root 179, 2 2012-06-05 15:34 mmcblk0p2
brw------- root root 179, 20 2012-06-05 15:34 mmcblk0p20
brw------- root root 179, 3 2012-06-05 15:34 mmcblk0p3
brw------- root root 179, 4 2012-06-05 15:34 mmcblk0p4
brw------- root root 179, 5 2012-06-05 15:34 mmcblk0p5
brw------- root root 179, 6 2012-06-05 15:34 mmcblk0p6
brw------- root root 179, 7 2012-06-05 15:34 mmcblk0p7
brw------- root root 179, 8 2012-06-05 15:34 mmcblk0p8
brw------- root root 179, 9 2012-06-05 15:34 mmcblk0p9
drwxr-xr-x root root 2012-06-05 15:34 platform
drwxr-xr-x root root 2012-06-05 15:34 vold
Is it possible with dd (or another adb shell / linux commmand) to modify only the 8 bytes of mmcblk0 which contain the CID? If so we could debrand with HTC__001 or even superCID with 11111111
Any ideas?
why dont you post this in the S-OFF discussion?
dezborders said:
Is it possible with dd (or another adb shell / linux commmand) to modify only the 8 bytes of mmcblk0 which contain the CID? If so we could debrand with HTC__001 or even superCID with 11111111
Any ideas?
Click to expand...
Click to collapse
man dd
Looks like skip and seek are what you're looking for.
BenPope said:
man dd
Looks like skip and seek are what you're looking for.
Click to expand...
Click to collapse
Sadly conv=notrunc option is disabled in dd on android so I can't update only the area containing cid. It's not feasible to dump all 32gb of mccblk0, edit cid then write back all 32gb.
Sent from my HTC One X using XDA
Does the android version support the "skip" and "seek" options?
dezborders said:
However, when I try to dump the file to SCDARD with
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0
the command never finishes (I broke out after about 5 minutes with a 4GB file sitting on the SDCARD, which I assume is incomplete.
Any ideas?
Click to expand...
Click to collapse
mmcblk0 is the whole 32G flash chip of the phone, while mmcblk0p1 .. mmcblk0p20 are the individual partitions.
I think, it is worth to find specific partition between these 20, which contains CID, and work with it.
k0rner said:
mmcblk0 is the whole 32G flash chip of the phone, while mmcblk0p1 .. mmcblk0p20 are the individual partitions.
I think, it is worth to find specific partition between these 20, which contains CID, and work with it.
Click to expand...
Click to collapse
None of the 20 partitions contain the cid, obviously the area of mmcblk0 containing this data is only accessible to hboot.
Also, it has been suggested writing to the 20 partitions only makes temporary changes which revert to original values at next reboot.
I think this thread should be locked and let the devs in the main S-off thread continue the discussion .)
Sent from my HTC One X using XDA
dezborders said:
None of the 20 partitions contain the cid, obviously the area of mmcblk0 containing this data is only accessible to hboot.
Also, it has been suggested writing to the 20 partitions only makes temporary changes which revert to original values at next reboot.
I think this thread should be locked and let the devs in the main S-off thread continue the discussion .)
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
I think mmcblk0p19 contains CID.
Karel
If I remember correctly p19 is just logs, so its just a text file that happens to contain a copy of your cid code. Sorry
@MOD... If any forum mods are reading, please lock this thread for me, thanks !
Sent from my HTC One X using XDA
mmcblk0p14 contains the cid
no lets keep this discussion outside the S-off section
changing CID is a different and as important as s-off
its really odd that this can be done for the One S and not the X
Hello, I've found 0x00A00000 at /dev/block/mmcblk0 is where the cid and IMEI were stored for some time, but I didn't found a way to change it.
But now that I've got a way to modify it. Use the dd command from Busybox, it can let you use the "conv=notrunc" parameter to write the changed cid into /dev/block/mmcblk0. btw, 0x00A00000 is the offset of DIAG partition, so here is the start of diag partition.
You may use dd command to export the mmcblk0 from 0x00A00000 to a file called "towrite", and modify it using a hex editor, then do the flash just as the following command in the shell:
Code:
busybox dd if=/sdcard/towrite of=/dev/block/mmcblk0 bs=1024 count=1 seek=10240 conv=notrunc
Then you willl get it modified(you can check it by "dd if=/dev/block/mmcblk0 of=/sdcard/dump.txt bs=1024 count=1 skip=10240", and then check "dump.txt" in your sdcard, you will see it has been modified.)
BUT IT WON'T CHANGE THE CID ACTUALLY. If you reboot into bootloader, and execute "fastboot oem readcid" then, the cid remains the original one.
So...I think the CID must be stored in the motherboard, and can't be modified by software methods.
What's about the idea to rip the mmcblk0p4 from an S-OFF device and put it on a S-ON device? As far as I know the hboot is stored within this partition.
It might be that the IMEI will also be the same but I guess with the current eng-hboot there is an option to change it.
Who can offer a backup from an TEGRA S-OFF device?
Don't waste your time, as of now you cannot change your cid, if s_off comes in the future this may change but it might never happen.
Sent from my HTC One X using xda app-developers app
hamdir said:
no lets keep this discussion outside the S-off section
changing CID is a different and as important as s-off
its really odd that this can be done for the One S and not the X
Click to expand...
Click to collapse
i believe its possible for the x if its possible for the s.
but at the same time, i dun think its possible.
remember, the s is a qualcomm and the x is a tegra
shiningarmor said:
i believe its possible for the x if its possible for the s.
but at the same time, i dun think its possible.
remember, the s is a qualcomm and the x is a tegra
Click to expand...
Click to collapse
The one x and the one s do not share the same SoC. What works on the one s doesn't necessarily work on the one x.
Sent from somewhere....if I could only remember where....
Related
Guys I'm in over my head on this one. Long story short I needed to restore the efs partition which I backed up with the Galaxy Note 2 toolkit. Right as I choose the option to restore it I get a blue screen, computer restarts and now the phone won't boot any more. I said I shouldn't worry I just need to flash the efs.img back-up... I tried creating an Odin flashable tar file using the toolkit again but the process of flashing it with Odin fails every time... I also tried flashing a stock firmware and clearing the efs using Odin.
If I go into recovery I get: "E:failed to mount /efs (Invalid argument)"
Any help is greatly appreciated...
Download toolkit. Put img in backup folder and restore via toolkit.
Btw where you in recovery while trying ?
Sent From Samsung's Galaxy Note II Using Internet
No chance
UtkarshGupta said:
Download toolkit. Put img in backup folder and restore via toolkit.
Btw where you in recovery while trying ?
Sent From Samsung's Galaxy Note II Using Internet
Click to expand...
Click to collapse
Thank you for your reply but my phone doesn't boot to android... it hangs at the SAMSUNG logo so I cannot use the toolkit which requires that the phone is booted to android with USB debugging on.
DieZz said:
Thank you for your reply but my phone doesn't boot to android... it hangs at the SAMSUNG logo so I cannot use the toolkit which requires that the phone is booted to android with USB debugging on.
Click to expand...
Click to collapse
Is the device able to boot into recovery? If it is, boot into CWM, wait a minute or two, and then ADB will be up and running and you can use the toolkit. ADB works in CWM just like it does booted into Android.
If you're still rocking a stock recovery, just flash CWM using ODIN. Then boot into recovery and use the toolkit via ADB.
Let me know if any of this helps.
Sent from my GT-N7100 using XDA Premium HD app
Still no change
Mister_Mxyzptlk said:
Is the device able to boot into recovery? If it is, boot into CWM, wait a minute or two, and then ADB will be up and running and you can use the toolkit. ADB works in CWM just like it does booted into Android.
If you're still rocking a stock recovery, just flash CWM using ODIN. Then boot into recovery and use the toolkit via ADB.
Let me know if any of this helps.
Sent from my GT-N7100 using XDA Premium HD app
Click to expand...
Click to collapse
The computer recognized the phone in ADB mode but the toolkit is still prompting me to enable USB debugging and it doesn't detect the phone. Thanks for your reply though...
I went into mounts and storage and tried to mount efs - no luck..
DieZz said:
The computer recognized the phone in ADB mode but the toolkit is still prompting me to enable USB debugging and it doesn't detect the phone. Thanks for your reply though...
I went into mounts and storage and tried to mount efs - no luck..
Click to expand...
Click to collapse
You may need to reinstall the Samsung mobile device USB driver. Also, make sure you've got root access in ADB. Additionally, you may need to restore your efs backup directly via ADB instead of the toolkit. There's a few threads with tutorials. Regardless, as long as you have an efs backup, you're not totally screwed... yet.
Sent from my GT-N7100 using XDA Premium HD app
No solution
Thank you all for your replies but I am afraid that the only solution once this problem has happened is to return the phone to service. No matter what I have tried nothing worked so I ended up sending the phone away. If anyone finds themselves in my position my advice is not to waste any time on it...
DieZz said:
Thank you all for your replies but I am afraid that the only solution once this problem has happened is to return the phone to service. No matter what I have tried nothing worked so I ended up sending the phone away. If anyone finds themselves in my position my advice is not to waste any time on it...
Click to expand...
Click to collapse
I had the same issue last night my man - took me HOURS to fix it. In the end the solution was to boot into CWM and enter a few ADB commands on the PC:
Run an SU shell, then enter "mke2fs / dev/block/mmcblk0p3", then "mount-w-t ext4 / dev/block/mmcblk0p3 / efs"
This magically made the EFS partition mountable again. I then restored my EFS image, and wala all was good again.
But yes you are right, this is DAMN hard to fix (I had to trawl the internet for hours). A full wipe / odin stock rom flash / repartition does not solve the issue.
agentdark45 said:
I had the same issue last night my man - took me HOURS to fix it. In the end the solution was to boot into CWM and enter a few ADB commands on the PC:
Run an SU shell, then enter "mke2fs / dev/block/mmcblk0p3", then "mount-w-t ext4 / dev/block/mmcblk0p3 / efs"
This magically made the EFS partition mountable again. I then restored my EFS image, and wala all was good again.
But yes you are right, this is DAMN hard to fix (I had to trawl the internet for hours). A full wipe / odin stock rom flash / repartition does not solve the issue.
Click to expand...
Click to collapse
Hi All, I have this problem after rooting the stock rom and taking a backup nandroid. The intention was to then install Philz safe kernel and take efs backup. But on reboot from CMW, the phone loops as described above and I get the invalid efs message in the OP.
I can boot into CWM recovery and downloaded and flashed the Rom many times and also installed Philz Rom with no success. Tried Samsung service centre who also refuse to touch the phone.
Having found this ADB suggestion I have followed the instructions above but I get the response ' invalid blocks count - dev/block/mmcblk0p3 ' and can go no further.
If anyone has any other ideas that a noobie can try I shall be very grateful. If not I guess it is going to be ebay!
Thanks.
agentdark45 said:
I had the same issue last night my man - took me HOURS to fix it. In the end the solution was to boot into CWM and enter a few ADB commands on the PC:
Run an SU shell, then enter "mke2fs / dev/block/mmcblk0p3", then "mount-w-t ext4 / dev/block/mmcblk0p3 / efs"
This magically made the EFS partition mountable again. I then restored my EFS image, and wala all was good again.
But yes you are right, this is DAMN hard to fix (I had to trawl the internet for hours). A full wipe / odin stock rom flash / repartition does not solve the issue.
Click to expand...
Click to collapse
Hi !
I have the same problem with my GN2 N7100 and i try to do "mke2fs / dev/block/mmcblk0p3", then "mount-w-t ext4 / dev/block/mmcblk0p3 / efs" but i don't have any file mmcblk0p3.
look my folder :
cd /dev/block
/dev/block # ls -ltr
ls -ltr
brw------- 1 root root 1, 9 Jan 2 03:39 ram9
brw------- 1 root root 1, 8 Jan 2 03:39 ram8
brw------- 1 root root 1, 7 Jan 2 03:39 ram7
brw------- 1 root root 1, 6 Jan 2 03:39 ram6
brw------- 1 root root 1, 5 Jan 2 03:39 ram5
brw------- 1 root root 1, 4 Jan 2 03:39 ram4
brw------- 1 root root 1, 3 Jan 2 03:39 ram3
brw------- 1 root root 1, 2 Jan 2 03:39 ram2
brw------- 1 root root 1, 15 Jan 2 03:39 ram15
brw------- 1 root root 1, 14 Jan 2 03:39 ram14
brw------- 1 root root 1, 13 Jan 2 03:39 ram13
brw------- 1 root root 1, 12 Jan 2 03:39 ram12
brw------- 1 root root 1, 11 Jan 2 03:39 ram11
brw------- 1 root root 1, 10 Jan 2 03:39 ram10
brw------- 1 root root 1, 1 Jan 2 03:39 ram1
brw------- 1 root root 1, 0 Jan 2 03:39 ram0
drwxr-xr-x 4 root root 80 Jan 2 03:39 platform
brw------- 1 root root 179, 19 Jan 2 03:39 mmcblk1p3
brw------- 1 root root 179, 18 Jan 2 03:39 mmcblk1p2
brw------- 1 root root 179, 17 Jan 2 03:39 mmcblk1p1
brw------- 1 root root 179, 16 Jan 2 03:39 mmcblk1
brw------- 1 root root 179, 9 Jan 2 03:39 mmcblk0p9
brw------- 1 root root 179, 8 Jan 2 03:39 mmcblk0p8
brw-rw---- 1 system root 179, 7 Jan 2 03:39 mmcblk0p7
brw-rw---- 1 system radio 179, 6 Jan 2 03:39 mmcblk0p6
brw-rw---- 1 system radio 179, 5 Jan 2 03:39 mmcblk0p5
brw-rw---- 1 system radio 179, 4 Jan 2 03:39 mmcblk0p4
brw------- 1 root root 179, 3 Jan 2 03:39 mmcblk0p3
brw------- 1 root root 179, 2 Jan 2 03:39 mmcblk0p2
brw------- 1 root root 259, 0 Jan 2 03:39 mmcblk0p16
brw------- 1 root root 179, 15 Jan 2 03:39 mmcblk0p15
brw------- 1 root root 179, 14 Jan 2 03:39 mmcblk0p14
brw------- 1 root root 179, 13 Jan 2 03:39 mmcblk0p13
brw-rw---- 1 system radio 179, 11 Jan 2 03:39 mmcblk0p11
brw-rw---- 1 system radio 179, 10 Jan 2 03:39 mmcblk0p10
brw------- 1 root root 179, 1 Jan 2 03:39 mmcblk0p1
brw------- 1 root root 179, 0 Jan 2 03:39 mmcblk0
brw------- 1 root root 7, 7 Jan 2 03:39 loop7
brw------- 1 root root 7, 6 Jan 2 03:39 loop6
brw------- 1 root root 7, 5 Jan 2 03:39 loop5
brw------- 1 root root 7, 4 Jan 2 03:39 loop4
brw------- 1 root root 7, 3 Jan 2 03:39 loop3
brw------- 1 root root 7, 2 Jan 2 03:39 loop2
brw------- 1 root root 7, 1 Jan 2 03:39 loop1
brw------- 1 root root 7, 0 Jan 2 03:39 loop0
brw------- 1 root root 179, 12 Jan 2 03:40 mmcblk0p12
Someone can help me please ?
maybe a funny question, but you may have missed the spot tho..
Did you mount /efs using cwm and fix the permissions?
If not give it a try. Then use cwm to restore efs. I would suggest philz touch anyways
myaslioglu said:
maybe a funny question, but you may have missed the spot tho..
Did you mount /efs using cwm and fix the permissions?
If not give it a try. Then use cwm to restore efs. I would suggest philz touch anyways
Click to expand...
Click to collapse
Thank's for your answer but i can't mount /efs from cwm : i have an error message : "Error mounting /efs!"
How can i restore efs from cwm ?
Maybe efs partition is corrupt.
Ask some expert like skip or ketan to help you reformat it properly.
Sent from my GT-N7100 using xda app-developers app
Thanks but I have the same problem. Attempting to mount /efs gives the response 'Error mounting /efs!'
I agree whole heartedly about Philz Kernel and had wanted this running on this Note 2 having had it on the original Note.
tcastel said:
Hi !
I have the same problem with my GN2 N7100 and i try to do "mke2fs / dev/block/mmcblk0p3", then "mount-w-t ext4 / dev/block/mmcblk0p3 / efs" but i don't have any file mmcblk0p3.
look my folder :
cd /dev/block
/dev/block # ls -ltr
ls -ltr
brw------- 1 root root 1, 9 Jan 2 03:39 ram9
brw------- 1 root root 1, 8 Jan 2 03:39 ram8
brw------- 1 root root 1, 7 Jan 2 03:39 ram7
brw------- 1 root root 1, 6 Jan 2 03:39 ram6
brw------- 1 root root 1, 5 Jan 2 03:39 ram5
brw------- 1 root root 1, 4 Jan 2 03:39 ram4
brw------- 1 root root 1, 3 Jan 2 03:39 ram3
brw------- 1 root root 1, 2 Jan 2 03:39 ram2
brw------- 1 root root 1, 15 Jan 2 03:39 ram15
brw------- 1 root root 1, 14 Jan 2 03:39 ram14
brw------- 1 root root 1, 13 Jan 2 03:39 ram13
brw------- 1 root root 1, 12 Jan 2 03:39 ram12
brw------- 1 root root 1, 11 Jan 2 03:39 ram11
brw------- 1 root root 1, 10 Jan 2 03:39 ram10
brw------- 1 root root 1, 1 Jan 2 03:39 ram1
brw------- 1 root root 1, 0 Jan 2 03:39 ram0
drwxr-xr-x 4 root root 80 Jan 2 03:39 platform
brw------- 1 root root 179, 19 Jan 2 03:39 mmcblk1p3
brw------- 1 root root 179, 18 Jan 2 03:39 mmcblk1p2
brw------- 1 root root 179, 17 Jan 2 03:39 mmcblk1p1
brw------- 1 root root 179, 16 Jan 2 03:39 mmcblk1
brw------- 1 root root 179, 9 Jan 2 03:39 mmcblk0p9
brw------- 1 root root 179, 8 Jan 2 03:39 mmcblk0p8
brw-rw---- 1 system root 179, 7 Jan 2 03:39 mmcblk0p7
brw-rw---- 1 system radio 179, 6 Jan 2 03:39 mmcblk0p6
brw-rw---- 1 system radio 179, 5 Jan 2 03:39 mmcblk0p5
brw-rw---- 1 system radio 179, 4 Jan 2 03:39 mmcblk0p4
brw------- 1 root root 179, 3 Jan 2 03:39 mmcblk0p3
brw------- 1 root root 179, 2 Jan 2 03:39 mmcblk0p2
brw------- 1 root root 259, 0 Jan 2 03:39 mmcblk0p16
brw------- 1 root root 179, 15 Jan 2 03:39 mmcblk0p15
brw------- 1 root root 179, 14 Jan 2 03:39 mmcblk0p14
brw------- 1 root root 179, 13 Jan 2 03:39 mmcblk0p13
brw-rw---- 1 system radio 179, 11 Jan 2 03:39 mmcblk0p11
brw-rw---- 1 system radio 179, 10 Jan 2 03:39 mmcblk0p10
brw------- 1 root root 179, 1 Jan 2 03:39 mmcblk0p1
brw------- 1 root root 179, 0 Jan 2 03:39 mmcblk0
brw------- 1 root root 7, 7 Jan 2 03:39 loop7
brw------- 1 root root 7, 6 Jan 2 03:39 loop6
brw------- 1 root root 7, 5 Jan 2 03:39 loop5
brw------- 1 root root 7, 4 Jan 2 03:39 loop4
brw------- 1 root root 7, 3 Jan 2 03:39 loop3
brw------- 1 root root 7, 2 Jan 2 03:39 loop2
brw------- 1 root root 7, 1 Jan 2 03:39 loop1
brw------- 1 root root 7, 0 Jan 2 03:39 loop0
brw------- 1 root root 179, 12 Jan 2 03:40 mmcblk0p12
Someone can help me please ?
Click to expand...
Click to collapse
I solved half my problem:
by "mke2fs / dev/block/mmcblk0p3" and "mount-w-t ext4 / dev/block/mmcblk0p3 / efs" the phone connected to the pc and recovery by running the cmd windows.
Now the phone starts but I have a black rectangle with the version of my PDA etc ... (see the picture)
Someone can help me please ?
Make a efs backup again a duplicate to be safe. Then flash stock rom again.
And also do a cache and dalvik and data wipe.
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
Make a efs backup again a duplicate to be safe. Then flash stock rom again.
And also do a cache and dalvik and data wipe.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Thank you for your answer but i sent my phone to warranty this morning.
UtkarshGupta said:
Make a efs backup again a duplicate to be safe. Then flash stock rom again.
And also do a cache and dalvik and data wipe.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Thanks for this; I had already tried this, but have given it another try. Still the same issue with the boot loop and "E:failed to mount /efs (Invalid argument)" when I try to make any changes in CWM.
tcastel said:
I solved half my problem:
by "mke2fs / dev/block/mmcblk0p3" and "mount-w-t ext4 / dev/block/mmcblk0p3 / efs" the phone connected to the pc and recovery by running the cmd windows.
Now the phone starts but I have a black rectangle with the version of my PDA etc ... (see the picture)
Someone can help me please ?
Click to expand...
Click to collapse
Hi how did you open a SU shell in the Toolkit - which command did you use or did you download an program to do that?
pdafan1 said:
Hi how did you open a SU shell in the Toolkit - which command did you use or did you download an program to do that?
Click to expand...
Click to collapse
You have to put the phone in recovery mode (CWM), wait 2min, plug it to your pc, launch cmd, go to your adb folder and now you can use adb !
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
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.
Hi everyone,
I was trying to flash an nightly update from cyanogen and was getting the error : CM 12 Error:detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system and so, troubleshooting the problem, I tried to extend the system partitions through the procedure I found in a thread that contained the code down bellow and I believe that was after that that I lost my recoverymode. After this I tried to flash an earlier ROM to see if I could get the phone back and that was the last time I was able to enter in the recoverymode. Now I just have a black screen and also when I try to start my phone it took about 2 min on a black screen and then the OS starts. Besides that, all network connectivity was lost (wifi, call signal, 4g/3g) and my user space (/data partition) too (althoug it seems to be mounted). It appears it that was all disabled. Without a recovery mode and internet I am completely stuck. I tried to install a cwm and a twrp through adb after install flash gordon and flashify apk but it did not worked it cannot recognize a file out my /data . And the idea I had to restore from rommanager apk failed in the moment it tried to connect on internet to download content.
Please help!! Follow details:
LG_E975
I did a full wipe partition / cache/ dalvik
cyanogemMod version: 11-20141115-SNAPSHOT-M12-E975
android : 4.4.4.
kernel version: 3.4.0-CM+
Code I found and ran when trying to solve CM 12 Error:detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
Code:
#!/sbin/sh
OUTFD=$2
ui_print() {
echo -n -e "ui_print $1\n" > /proc/self/fd/$OUTFD
echo -n -e "ui_print\n" > /proc/self/fd/$OUTFD
}
ui_print ""
ui_print "###########################"
ui_print "# audahadi #"
ui_print "# modded from forumber2's #"
ui_print "# Repartition script #"
ui_print "# Mi 3W /system 1.2G #"
ui_print "# only! #"
ui_print "###########################"
ui_print ""
ui_print "Unmounting systems partiton..."
umount -l /system
umount -l /system1
umount -l /dev/block/mmcblk0p25
umount -l /dev/block/mmcblk0p26
ui_print ""
ui_print "WARNING! System is ready, repartitioning will start in 2 seconds"
sleep 2
ui_print ""
ui_print "Removing partitions..."
parted /dev/block/mmcblk0 rm 25
parted /dev/block/mmcblk0 rm 26
ui_print "Removing partitions...COMPLETED"
ui_print ""
ui_print "Creating new partitions..."
parted /dev/block/mmcblk0 mkpart primary 403MB 1740MB
parted /dev/block/mmcblk0 mkpart primary 1740MB 1745MB
parted /dev/block/mmcblk0 name 25 system
parted /dev/block/mmcblk0 name 26 system1
ui_print "Creating new partitions...COMPLETED"
ui_print ""
ui_print "Unmounting systems partitions again..."
umount -l /system
umount -l /system1
umount -l /dev/block/mmcblk0p25
umount -l /dev/block/mmcblk0p26
ui_print "Unmounting systems partitions again...COMPLETED"
ui_print ""
ui_print "Formatting new partitions..."
mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p25
mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p26
ui_print "Formatting new partitions...COMPLETED."
ui_print ""
ui_print "ALL DONE!..."
ui_print ""
ui_print "Rebooting to recovery in 5 seconds..."
ui_print "Thanks to forumber2 for his original GT-i9300 repartition script"
sleep 5
reboot recovery
fi
Output from df command:
Code:
[email protected]:/ $ df
df
Filesystem Size Used Free Blksize
/dev 905.8M 128.0K 905.6M 4096
/sys/fs/cgroup 905.8M 12.0K 905.8M 4096
/mnt/asec 905.8M 0.0K 905.8M 4096
/mnt/obb 905.8M 0.0K 905.8M 4096
/mnt/fuse 905.8M 0.0K 905.8M 4096
/system 1.5G 401.3M 1.1G 4096
/cache 788.4M 14.4M 774.0M 4096
/data 25.0G 271.0M 24.8G 4096
[email protected]:/ $
Output from /proc/partitions
Code:
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 2048 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 24576 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 780 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8 mmcblk0p17
179 18 16384 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 512 mmcblk0p20
179 21 512 mmcblk0p21
179 22 1556480 mmcblk0p22
179 23 819200 mmcblk0p23
179 24 26714112 mmcblk0p24
179 27 24576 mmcblk0p27
179 28 3072 mmcblk0p28
179 29 8 mmcblk0p29
179 30 32768 mmcblk0p30
179 31 32768 mmcblk0p31
259 0 512 mmcblk0p32
259 1 512 mmcblk0p33
259 2 16384 mmcblk0p34
259 3 879599 mmcblk0p35
[email protected]:/ $
Output from /dev/block directory:
Code:
[email protected]:/dev/block $ ls -l
ls -l
brw------- root root 7, 0 1970-01-02 12:07 loop0
brw------- root root 7, 1 1970-01-02 12:07 loop1
brw------- root root 7, 2 1970-01-02 12:07 loop2
brw------- root root 7, 3 1970-01-02 12:07 loop3
brw------- root root 7, 4 1970-01-02 12:07 loop4
brw------- root root 7, 5 1970-01-02 12:07 loop5
brw------- root root 7, 6 1970-01-02 12:07 loop6
brw------- root root 7, 7 1970-01-02 12:07 loop7
brw------- root root 179, 0 1970-01-02 12:07 mmcblk0
brw------- root root 179, 1 1970-01-02 12:07 mmcblk0p1
brw------- root root 179, 10 1970-01-02 12:07 mmcblk0p10
brw------- root root 179, 11 1970-01-02 12:07 mmcblk0p11
brw-rw---- system system 179, 12 1970-01-02 12:07 mmcblk0p12
brw-rw---- system system 179, 13 1970-01-02 12:07 mmcblk0p13
brw-rw---- system system 179, 14 1970-01-02 12:07 mmcblk0p14
brw------- root root 179, 15 1970-01-02 12:07 mmcblk0p15
brw------- root root 179, 16 1970-01-02 12:07 mmcblk0p16
brw------- root root 179, 17 1970-01-02 12:07 mmcblk0p17
brw-rw---- root system 179, 18 1970-01-02 12:07 mmcblk0p18
brw------- root root 179, 19 1970-01-02 12:07 mmcblk0p19
brw------- root root 179, 2 1970-01-02 12:07 mmcblk0p2
brw------- root root 179, 20 1970-01-02 12:07 mmcblk0p20
brw------- root root 179, 21 1970-01-02 12:07 mmcblk0p21
brw------- root root 179, 22 1970-01-02 12:07 mmcblk0p22
brw------- root root 179, 23 1970-01-02 12:07 mmcblk0p23
brw------- root root 179, 24 1970-01-02 12:07 mmcblk0p24
brw------- root root 179, 27 1970-01-02 12:07 mmcblk0p27
brw------- root root 179, 28 1970-01-02 12:07 mmcblk0p28
brw------- root root 179, 29 1970-01-02 12:07 mmcblk0p29
brw------- root root 179, 3 1970-01-02 12:07 mmcblk0p3
brw------- root root 179, 30 1970-01-02 12:07 mmcblk0p30
brw------- root root 179, 31 1970-01-02 12:07 mmcblk0p31
brw------- root root 259, 0 1970-01-02 12:07 mmcblk0p32
brw------- root root 259, 1 1970-01-02 12:07 mmcblk0p33
brw------- root root 259, 2 1970-01-02 12:07 mmcblk0p34
brw------- root root 259, 3 1970-01-02 12:07 mmcblk0p35
brw------- root root 179, 4 1970-01-02 12:07 mmcblk0p4
brw------- root root 179, 5 1970-01-02 12:07 mmcblk0p5
brw------- root root 179, 6 1970-01-02 12:07 mmcblk0p6
brw------- root root 179, 7 1970-01-02 12:07 mmcblk0p7
brw-rw---- system system 179, 8 1970-01-02 12:07 mmcblk0p8
brw-rw---- system system 179, 9 1970-01-02 12:07 mmcblk0p9
drwxr-xr-x root root 1970-01-02 12:07 platform
brw------- root root 1, 0 1970-01-02 12:07 ram0
brw------- root root 1, 1 1970-01-02 12:07 ram1
brw------- root root 1, 10 1970-01-02 12:07 ram10
brw------- root root 1, 11 1970-01-02 12:07 ram11
brw------- root root 1, 12 1970-01-02 12:07 ram12
brw------- root root 1, 13 1970-01-02 12:07 ram13
brw------- root root 1, 14 1970-01-02 12:07 ram14
brw------- root root 1, 15 1970-01-02 12:07 ram15
brw------- root root 1, 2 1970-01-02 12:07 ram2
brw------- root root 1, 3 1970-01-02 12:07 ram3
brw------- root root 1, 4 1970-01-02 12:07 ram4
brw------- root root 1, 5 1970-01-02 12:07 ram5
brw------- root root 1, 6 1970-01-02 12:07 ram6
brw------- root root 1, 7 1970-01-02 12:07 ram7
brw------- root root 1, 8 1970-01-02 12:07 ram8
brw------- root root 1, 9 1970-01-02 12:07 ram9
drwx------ root root 1970-01-02 12:09 vold
[email protected]:/dev/block $
Output from cat /proc/mounts
Code:
[email protected]:/dev/block $ cat /proc/mounts
cat /proc/mounts
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/cache /cache ext4 rw,seclabel,nosuid,node
v,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,no
dev,noatime,noauto_da_alloc,data=ordered 0 0
[email protected]:/dev/block $
Hello,
Have you given up on this, have you fixed it, or are you still trying?
You may be able to flash a new recovery from fastboot (hold volume up while powering on).
I have not had any luck with cm-12.1 either. I did successfully resize my system partition, but cm-12.1 still will not flash. cm-12, however works fine.
TH
I am using a Linux machine and adb.
Nubia NX503a (25S)
Code:
[email protected]:~$ adb devices
List of devices attached
MSM8974 recovery
[email protected]:~$
Code:
~ # ls -la
drwxr-xr-x 22 root root 0 Jan 3 18:48 .
drwxr-xr-x 22 root root 0 Jan 3 18:48 ..
drwxr-xr-x 2 root root 0 Jan 3 18:46 boot
drwxr-xr-x 4 root root 4096 Jan 3 18:03 cache
drwxr-xr-x 5 root root 4096 Jan 3 20:15 data
drwxr-xr-x 2 root root 0 Jan 3 18:46 datadata
-rw-r--r-- 1 root root 5785 Jan 1 00:00 default.prop
drwxr-xr-x 10 root root 15160 Jan 3 18:46 dev
drwxr-xr-x 2 root root 0 Jan 3 18:46 emmc
drwxr-xr-x 2 root root 0 Jan 3 18:46 etc
drwxr-xr-x 2 root root 0 Jan 3 18:46 external_sd
-rwxr-x--- 1 root root 113592 Jan 1 00:00 init
-rwxr-x--- 1 root root 1417 Jan 1 00:00 init.rc
drwxr-xr-x 2 root root 0 Jan 3 18:46 internal_sd
drwxrwx--x 6 system system 4096 Jan 2 00:30 persist
dr-xr-xr-x 158 root root 0 Jan 1 00:00 proc
drwxr-xr-x 2 root root 0 Jan 3 18:46 recovery
drwxr-xr-x 3 root root 0 Jan 1 00:00 res
drwx------ 2 root root 0 Dec 30 2013 root
drwxr-x--- 2 root root 0 Jan 1 00:00 sbin
drwxr-xr-x 2 root root 0 Jan 3 18:46 sd-ext
drwxrwxrwx 2 root root 8192 Jan 1 00:00 sdcard
dr-xr-xr-x 15 root root 0 Jan 3 18:46 sys
drwxr-xr-x 16 root root 4096 Jan 1 00:00 system
drwxrwxr-x 2 root shell 0 Jan 3 18:46 tmp
-rw-r--r-- 1 root root 272 Jan 1 00:00 ueventd.goldfish.rc
-rw-r--r-- 1 root root 5897 Jan 1 00:00 ueventd.rc
~ #
It can be seen that the sdcard is 0% used:
Code:
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 924.0M 48.0K 924.0M 0% /dev
/dev/block/platform/msm_sdcc.1/by-name/cache
492.6M 8.7M 483.9M 2% /cache
/dev/block/platform/msm_sdcc.1/by-name/userdata
2.5G 424.5M 2.0G 17% /data
/dev/block/platform/msm_sdcc.1/by-name/grow
9.8G 8.0K 9.8G 0% /sdcard
/dev/block/platform/msm_sdcc.1/by-name/system
1.2G 485.0M 726.5M 40% /system
/dev/block/platform/msm_sdcc.1/by-name/persist
4.9M 4.1M 812.0K 84% /persist
~ #
The sdcard:
Code:
~ # cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 32 mmcblk0p3
179 4 32 mmcblk0p4
179 5 512 mmcblk0p5
179 6 500 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 500 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 1536 mmcblk0p10
179 11 1536 mmcblk0p11
179 12 1024 mmcblk0p12
179 13 10240 mmcblk0p13
179 14 1258290 mmcblk0p14
179 15 2621440 mmcblk0p15
179 16 32768 mmcblk0p16
179 17 512000 mmcblk0p17
179 18 153600 mmcblk0p18
179 19 10240 mmcblk0p19
179 20 1536 mmcblk0p20
179 21 1 mmcblk0p21
179 22 8 mmcblk0p22
179 23 10276838 mmcblk0p23
179 32 4096 mmcblk0rpmb
~ #
Is 179 23 10276838 mmcblk0p23, but I forget how I linked the sdcard to mmcblk0p23
Using:
adb push -p /home/makem/Downloads/update2.zip /dev/block/mmcblk0p23/update2.zip
or
adb push -p /home/makem/Downloads/update2.zip /data/media/update2.zip
or
adb push -p /home/makem/Downloads/update2.zip /sdcard/
Each fail by stopping anywhere between 5% and 47%. I have wiped the cache, data and delvik cache prior to pushing.
When I check the sdcard again with df I find it is still at 0%, except for the last push which stopped at 10% and showed 1% used sdcard.
EDIT: After the last push the file update2.zip showed in the sdcard when I went to install it. However, it stopped with a 'bad' error. Obviously an incomplete upload but why????
Tearing my hair out here lol.