My intention is to list all physical partitions of /dev/block/mmcblk0 but outputs the following:
Code:
# fdisk -l /dev/block/mmcblk0
sh: fdisk: not found
Any idea about how to install such fdisk, cfdisk, parted or alternative command? Apparently it is not shipped by default.
Note: Superuser is installed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey! At least you made it on the right for part of the site!
Sent from my GT-I9100 using xda premium
Use busybox.
scandiun said:
My intention is to list all physical partitions of /dev/block/mmcblk0 but outputs the following:
Code:
# fdisk -l /dev/block/mmcblk0
sh: fdisk: not found
Any idea about how to install such fdisk, cfdisk, parted or alternative command? Apparently it is not shipped by default.
Note: Superuser is installed.
Click to expand...
Click to collapse
Do you have busybox installed?
EDIT: WAIT.
You said above:
My intention is to list all physical partitions of /dev/block/mmcblk0
Click to expand...
Click to collapse
Are you sure you want to use fdisk? Maybe you should read what fdisk does...
ctomgee said:
Do you have busybox installed?
EDIT: WAIT.
You said above:
Are you sure you want to use fdisk? Maybe you should read what fdisk does...
Click to expand...
Click to collapse
I had fdisk installed, but was version 1.17.1 which hadn't the fdisk applet. now I've got the BusyBox Pro 1.20.0 from market and does have it, just what I needed.
However, I haven't found what I am looking for. There seems to be only one partition, while I am looking for all the ones corresponding to efs, data, system, misc, boot, recovery and so on. Any ideas on that?
And yes, I used fdisk before on linux and cfdisk on freebsd so I feel quite comfortable with it.
scandiun said:
I had fdisk installed, but was version 1.17.1 which hadn't the fdisk applet. now I've got the BusyBox Pro 1.20.0 from market and does have it, just what I needed.
However, I haven't found what I am looking for. There seems to be only one partition, while I am looking for all the ones corresponding to efs, data, system, misc, boot, recovery and so on. Any ideas on that?
And yes, I used fdisk before on linux and cfdisk on freebsd so I feel quite comfortable with it.
Click to expand...
Click to collapse
Sorry, I missed the -l flag in your image, and for some reason I didn't process what you were looking for exactly.
Use the "df" command.
What are you trying to figure out exactly? Just a list of the partitions or sizes or something else...
Here is a list of the partitions and what they are used for
[email protected]:/sdcard # ls -l /dev/block/platform/dw_mmc/by-name/
lrwxrwxrwx 1 root root 20 May 12 21:24 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 May 12 21:24 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 May 12 21:24 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 May 12 21:24 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 May 12 21:24 HIDDEN -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 May 12 21:24 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 May 12 21:24 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 May 12 21:24 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 May 12 21:24 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 May 12 21:24 UMS -> /dev/block/mmcblk0p11
shadowofdarkness said:
What are you trying to figure out exactly? Just a list of the partitions or sizes or something else...
Here is a list of the partitions and what they are used for
[email protected]:/sdcard # ls -l /dev/block/platform/dw_mmc/by-name/
lrwxrwxrwx 1 root root 20 May 12 21:24 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 May 12 21:24 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 May 12 21:24 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 May 12 21:24 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 May 12 21:24 HIDDEN -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 May 12 21:24 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 May 12 21:24 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 May 12 21:24 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 May 12 21:24 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 May 12 21:24 UMS -> /dev/block/mmcblk0p11
Click to expand...
Click to collapse
That is what I was looking for. As i see, there is no such /misc partition.
scandiun said:
That is what I was looking for. As i see, there is no such /misc partition.
Click to expand...
Click to collapse
I have seen people using the normally unused partition 12 on /misc to hide files or just as extra space.
shadowofdarkness said:
I have seen people using the normally unused partition 12 on /misc to hide files or just as extra space.
Click to expand...
Click to collapse
Is there where linux/ubuntu is installed with some market installers?
How to get the size (dynamic, I mean kB, MB, etc) of all partitions? Why partitions won't shop up in mmcblk0 directly?
scandiun said:
How to get the size (dynamic, I mean kB, MB, etc) of all partitions? Why partitions won't shop up in mmcblk0 directly?
Click to expand...
Click to collapse
Use df:
Code:
[email protected]:/ # df
df
Filesystem Size Used Free Blksize
/dev 415M 32K 415M 4096
/mnt/asec 415M 0K 415M 4096
/mnt/obb 415M 0K 415M 4096
/system 503M 429M 74M 4096
/cache 98M 4M 94M 4096
/efs 19M 8M 11M 4096
/data 1G 666M 1G 4096
/mnt/.lfs: Function not implemented
/mnt/sdcard 11G 2G 9G 32768
/mnt/sdcard/external_sd 29G 24G 5G 32768
/mnt/sdcard/external_sd 29G 24G 5G 32768
Related
I've seen a lot of stuff using 'dd' but nothing that uses that for backuping the entire phone.
When I connect my phone I see both the external SDcard and the internal and just to be sure to take the correct one I pull the external out,
unless you know by its size, can I use this: (this assumes that /dev/sdb is the internal SDcard)
Code:
dd if=/dev/sdb of=/some/place/phone.image bs=4096 conv=notrunc,noerror
and later use that for a total recovery?
I've done this for lots of my Linux systems even just to backup some partitions (but then sdbN...)
but never on a phone and since it's Linux based....
//B52
Of course you can backup using dd, I suggest though that you do partitions seperately since restoring a single image be problematic if possible since some partitions are hidden and writing to the bootloader partitions is not a good idea incase of problems
Here is a list of the partitions with names.
[email protected]:/sdcard # ls -l /dev/block/platform/dw_mmc/by-name/
lrwxrwxrwx 1 root root 20 May 12 21:24 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 May 12 21:24 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 May 12 21:24 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 May 12 21:24 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 May 12 21:24 HIDDEN -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 May 12 21:24 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 May 12 21:24 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 May 12 21:24 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 May 12 21:24 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 May 12 21:24 UMS -> /dev/block/mmcblk0p11
The ones I suggest backing up are:
EFS this is a must and the most important without it your phone could be unusable if the files become corrupt and you don't have a backup
DATAFS is user data
FACTORYFS is the system partition
HIDDEN if you are on Jelly Bean this adds to and extends the system partition
UMS is your internal sdcard (probably better ways to backup then a dd)
Even if you backup don't restore the SBL partitions since if something goes wrong it will screw your phone and they are not damaged if your phone boots at all if they get damaged you will be paying to get your phone jtaged
One thing though, since this is not under /dev/sdX, is it possible to use dd on these /dev/block/ ?
Never done that before and what is the difference between a block and a device?
Is it possible to restore a damaged device partition (eg. from below list) (eg : /dev/block/mmcblk0p8) using a backup from another working phone ?
lrwxrwxrwx 1 root root 20 May 12 21:24 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 May 12 21:24 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 May 12 21:24 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 May 12 21:24 UMS -> /dev/block/mmcblk0p11
is the content of the partition different on each s2 phone ?
If we create a backup with following command :
[dd if=/dev/block/mmcblk0p8 of=/sdcard/phonebackup/mmcblk0p8.img bs=4096]
and restore in similar way,is there a risk of bricking the phone ?
I545 ME7 new version has a lock, do not accidentally brush or misuse upgrade, think about tossing a Brush Brush RECOVERY trouble. Is it possible to upgrade will not be downgraded? The answer is definitely no. Well, we want to downgrade, then understand its partition structure is a must. You know, in the end we have to upgrade to upgrade what was a result of being locked!
First, here is the I545 partition table structure:
Code:
lrwxrwxrwx root root 1970-01-01 16:14 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 16:14 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 16:14 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-01 16:14 boot -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-01 16:14 cache -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-01 16:14 carrier -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-01 16:14 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-01 16:14 fota -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-01 16:14 fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-01 16:14 hidden -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-01 16:14 m9kefs1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-01 16:14 m9kefs2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-01 16:14 m9kefs3 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-01 16:14 mdm -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 16:14 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-01 16:14 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-01 16:14 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-01 16:14 param -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-01 16:14 persdata -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-01 16:14 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-01 16:14 recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-01 16:14 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-01 16:14 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 16:14 sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 16:14 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 16:14 ssd -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-01 16:14 system -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-01 16:14 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 16:14 userdata -> /dev/block/mmcblk0p29
Know the partition table, then we have to look at the official ROM ME7 what is inside, at least to know what he upgraded partition was a result of being locked.
The following is the official package ME7 opened with RAR see:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can see, there are 12 official package file , in fact, there should be 13 years , I feel like I had a SBL1.MBN delete the file, this is an important guiding document , a blank screen will be lost . Connection brush modes anyhow. So we know that under the first bar . BOOT.IMG is the core of the boot files will be lost card first screen . CACHE This is not , MODEM.BIN and NON-HLOS.BIN this is related to the baseband , I brush off alone , it will not be locked , and this has nothing to do , RECOVERY This is a card swipe mode , recovery mode , this is not , RPM is a power management scheme related , SBL2.MBN SBL3.MBN boot record which two are related , SYSTEM this is the system , nor is , TZ is that I do not understand what to do .
**Now the question comes, if not understand, a recovery in the past may have a try. Such high risk factor . Therefore, we even try , but also row a sequence . For example SBL1.MBN, this is the first boot , when this fails if the coverage directly on a black screen , and we try not to move it to this , at least we do not move it, cover the failure modes that can feed wire brush brush the official rescue package bricks ! Of course , this is not relevant to the lock BOOTLOADER .
***535 used all know , 535 is V version, it also has BOOTLOADER lock, then unlock 535 using what methods do, in fact, is replaced by the partition method, which is aboot.mbn replace this partition. In fact, it says so much just thinking, we can be like 535 as a direct replacement overwrite this partition. If not, then only SBL2 SBL3 SBL1 these three , this three risk factor is quite high, and our principle is can not move do not move these three !
Well, just say replace overridden methods !
First of all, we have to use ADB SHELL under the DD command. Then we will obtain ADB SHELL authority , which is first ROOT.
The ROOT method ME7 forum there, I will not say more . I direct that ADB SHELL command .
We go first to Taiwan MDK the machine, put a few partition backup, is SBL1.MBN SBL2.MBN SBL3.MBN and ABOOT.MBN If you are interested , you can put all of the above partition table partition backup under , be prepared to stay with maybe someday that can use ! ~ ~
Backup method is to obtain ROOT , enter ADB SHELL command:
Code:
adb shell
dd if=/dev/block/mmcblk0p3 of=/sdcard/sbl1.mbn bs=4096
dd if=/dev/block/mmcblk0p4 of=/sdcard/sbl2.mbn bs=4096
dd if=/dev/block/mmcblk0p5 of=/sdcard/sbl3.mbn bs=4096
dd if=/dev/block/mmcblk0p6 of=/sdcard/aboot.mbn bs=4096
To explain, dd command to copy the partition related commands, if the meaning can be understood as if it. If there IF = path behind the partition, partition backup to put this on the path of = this, SDCARD this is the path of built-in memory card, you can back up directly to an external memory card, you have to do to change the path down.
Next, we put the backup files are copied to the four external SD card, or copied to a computer backup.
Then again, we took our locked machine, and put the MDK overwrite these partitions ME7 partition. Cover only aboot.mbn oh.
We first connect the phone to the computer, the backup out who's copied to the phone's built-in memory card.
root, I do not say this directly into the adb shell input overrides command:
Code:
adb shell
dd if=/dev/block/mmcblk0p6 of=/sdcard/ME7_aboot.mbn bs=4096
dd if=/sdcard/aboot.mbn of=/dev/block/mmcblk0p6 bs=4096
Note that this command following the second IF = OF = position and the position in turn, because it is not backed up, it was restored. The first DD command can not operate, I was customary to put it back down. Be prepared!
Well, I write to you, these commands is very dangerous, and can not be successful looking at you peril Oh, I only provide ideas and does not promise any consequences. Understand their own caution to decide whether to try, do not understand it not tried!
New ideas are always appreciated. Thank you for your efforts!
There are two places to discuss this ...and remember, if you ever try any of this stuff, you do so at your own risk....
see http://forum.xda-developers.com/showthread.php?t=2500826
or
http://forum.xda-developers.com/showthread.php?t=2417713
or possibly here http://forum.xda-developers.com/showthread.php?t=2428226
Assembling system.img for the models on the processor Samsung Snapdragon &Exynos Octa
Assembling sewn images (img) for the models on the processor Samsung Exynos Octa (S4-GT9500; Note-3 SM-N900, etc..)
What's needed to build their own ROM images: Preferably installed natively (live, not to Wirth., Machine) operating system based on Linux (UBUNTU, Linux Mint) and always 64 bit version.
Configure the system to use in building firmware:
Code:
sudo apt-get install git-core gnupg flex bison gperf libsdl-dev libesd0-dev libwxgtk2.8-dev build-essential zip curl libncurses5-dev zlib1g-dev valgrind libreadline6-dev gcc-multilib g++-multilib libc6-dev x11proto-core-dev libx11-dev libz-dev gawk texinfo automake libtool cvs libsdl-dev
Code:
sudo add-apt-repository "deb http://archive.canonical.com/ raring partner"
sudo apt-get update
Code:
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-jdk7-installer
Code:
sudo apt-get update
sudo apt-get install ia32-libs
Collect firmware:
1. - We will need to complete the assembly binaries Downloading this file
View attachment ext4_utils.zip
On versions of UBUNTU 13.04 and above may experience problems when you use these binaries, the way to solve:
http://forum.xda-developers.com/showpost.php?p=13834882&postcount=1
2. - Unpack the archive in your home directory, which is desirable in any folder you created previously, for example util
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. - Extract to the same folder from the downloaded firmware zip or in other formats, depending on where you get it. Prior to the status of individual images as below:
4. - Go to the folder in the terminal:
Code:
cd utils
We carry out the same in the terminal
Code:
ext4_utils/simg2img ./system.img ./system.raw.img
Code:
mkdir system
Code:
sudo mount -t ext4 -o loop system.raw.img system
Here, the terminal will be prompted to enter your administrator password, enter.
Here's what happened in the folder utils
5. - All our image system.img safely disassembled and placed in a folder for editing system (DO NOT close the terminal after these teams, if something else is needed to perform open another copy of the terminal) Next, go to the folder under administrator privileges (as root) and make the necessary changes. I've been using for these purposes Krusader, it is possible and usual file manager (as root)
For example:
Code:
sudo nautilus
But it more difficult to edit the permissions on files of modified, shorter than an amateur))
6. - After making the changes need to raise the image back to this continuing in the same place at the terminal where they made the disassembly:
Code:
ext4_utils/ext2simg -v system.raw.img system_new.img
Wait for the end of the process, and then:
Code:
ext4_utils/sgs4ext4fs --bloat system_new.img notesystem.img
Wait for the end of the process, and then:
Code:
chmod 0644 notesystem.img
7. - All our way safely assembled and ready after a subsequent packaging tar.md5 for flashing. Before packing firmware tar.md5 change the name of the new image notesystem.img on system.img simple renaming. Everything! Can clean the folder for the following assemblies, and unmount the mounted folder system
Code:
sudo umount system
Automated build process and edit images ---------------------------------- -------------------- ------------ V
View attachment 2431367
Special Thanks
Chainfire
A.S._id
Does this differ for SM-N9005?
Sent from my SM-N9005 using xda app-developers app
danieljamie said:
Does this differ for SM-N9005?
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Many of the other image format.
alexyuh said:
Many of the other image format.
Click to expand...
Click to collapse
help image I9505 Android 4.3
Help me the format image system.img.ext4, the working as above way and the result ODIN flash failed
thinh182009 said:
help image I9505 Android 4.3
But flash odin fail
Click to expand...
Click to collapse
Assembling sewn images (img) for the models on the processor Samsung Exynos Octa (S4-GT9500; Note-3 SM-N900, etc..)
alexyuh said:
Assembling sewn images (img) for the models on the processor Samsung Exynos Octa (S4-GT9500; Note-3 SM-N900, etc..)
Click to expand...
Click to collapse
Thank you for this tutorial. I did successfully I9500 version 4.3. You are asked to do all Note3 are successfully using this method. Thank you very much
Please SP all Qualcomm Snapdragon & Exynos 5 Octa
Thank you very much
Do you want a manual for Qualcomm Snapdragon?
Give me a log of commands from a terminal emulator.
Code:
cat /proc/partitions
and
Code:
cd dev/block/platform/dw_mmc.0/by-name
*************************************************************
or if does not work
*************************************************************
cd dev/block/platform/msm_sdcc.1/by-name
Code:
ls-l
alexyuh said:
Do you want a manual for Qualcomm Snapdragon?
Give me a log of commands from a terminal emulator.
Code:
cat /proc/partitions
and
Code:
cd dev/block/platform/dw_mmc.0/by-name
*************************************************************
or if does not work
*************************************************************
cd dev/block/platform/msm_sdcc.1/by-name
Code:
ls-l
Click to expand...
Click to collapse
Code:
[email protected]:/dev/block/platform/msm_sdcc.1/by-name # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
253 0 512000 zram0
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 mmcblk0p
su-mksh: cd: /dev/block/platform/msm_sdcc.1/by-name/dev/block/platform/msm_sdcc.1/by-name: No such file or directory
2|[email protected]:/dev/block/platform/msm_sdcc.1/by-name # ls -l
ls -l
lrwxrwxrwx root root 1970-04-05 13:01 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-04-05 13:01 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-04-05 13:01 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-04-05 13:01 boot -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-04-05 13:01 cache -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-04-05 13:01 carrier -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-04-05 13:01 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-04-05 13:01 fota -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-04-05 13:01 fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-04-05 13:01 hidden -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-04-05 13:01 m9kefs1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-04-05 13:01 m9kefs2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-04-05 13:01 m9kefs3 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-04-05 13:01 mdm -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-04-05 13:01 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-04-05 13:01 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-04-05 13:01 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-04-05 13:01 param -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-04-05 13:01 persdata -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-04-05 13:01 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-04-05 13:01 recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-04-05 13:01 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-04-05 13:01 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-04-05 13:01 sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-04-05 13:01 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-04-05 13:01 ssd -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-04-05 13:01 system -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-04-05 13:01 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-04-05 13:01 userdata -> /dev/block/mmcblk0p29
[email protected]:/dev/block/platform/msm_sdcc.1/by-name #
Please Slution. Thanks you very much:good:
---------- Post added at 11:29 AM ---------- Previous post was at 11:01 AM ----------
I was dumb to succeed, but I want you to open and close a tutorial of the original file system
You can collect an image directly on phone.
It will be flash.
Will contain already only regional part of csc. Thus I remade custom rom. For example
http://forum.xda-developers.com/showthread.php?t=2511167
Collected image internal sd to the card. It should be packed into tar.md5
Flashing Odin3
I will write the instruction for the personal computer later.
Okta
su
make_ext4fs -s -l 2436890624B -a system /sdcard/system.img /system
Snap
su
make_ext4fs -s -l 2894069760B -a system /sdcard/system.img.ext4 /system
Sent from my SM-N900 using xda app-developers app
alexyuh said:
You can collect an image directly on phone.
It will be flash.
Will contain already only regional part of csc. Thus I remade custom rom. For example
http://forum.xda-developers.com/showthread.php?t=2511167
Collected image internal sd to the card. It should be packed into tar.md5
Flashing Odin3
I will write the instruction for the personal computer later.
Okta
su
make_ext4fs -s -l 2436890624B -a system /sdcard/system.img /system
Snap
su
make_ext4fs -s -l 2894069760B -a system /sdcard/system.img.ext4 /system
Sent from my SM-N900 using xda app-developers app
Click to expand...
Click to collapse
Hi alexyuh! Requirements of thinh182009 want your phone to run guide build Qualcomm Snapdragon chip by means of
which you have given above.
Please guide thinh182009. I trust you to do this Thank you very much.
FAQ
Repacker Exynos Okta
Made for themselves.
Before use, configure OS UBUNTU as stated in 1 of the theme topic
VIDEO: PUSH
TOOL: PUSH
Good luck!
Refinement welcome! :fingers-crossed:
To build on Snap:
http://forum.xda-developers.com/showpost.php?p=46906278&postcount=1
In one of the points have been a topic change:
4 -> After unpacking the firmware from zip -> Change the name on system.img.ext system.img, simply renaming the image.
Code:
mv system.img.ext system.img
And mount as indicated:
Code:
ext4_utils/simg2img ./system.img ./system.raw.img
Code:
mkdir system
Code:
sudo mount -t ext4 -o loop system.raw.img system
6-> Assembly:
Code:
sudo ./make_ext4fs -s -l 2894069760B -a system system_new.img system
Code:
sudo chown 1000.1000 system_new.img
Code:
rm -f system.img
Code:
mv system_new.img system.img.ext
Code:
sudo umount system
Code:
rm -r system
Code:
rm *.raw.img
Pack into the firmware tar.md5
To assemble the need to add this folder ext4_utils binary.
View attachment make_ext4fs.zip <-- Unpack the zip of a folder and add ext4_utils
alexyuh said:
Repacker Exynos Okta
Made for themselves.
Before use, configure OS UBUNTU as stated in 1 of the theme topic
VIDEO: PUSH
TOOL: PUSH
Good luck!
Refinement welcome! :fingers-crossed:
Click to expand...
Click to collapse
Thanks you very much
very professional:good:
alexyuh said:
Repacker Exynos Okta
Made for themselves.
Before use, configure OS UBUNTU as stated in 1 of the theme topic
VIDEO: PUSH
TOOL: PUSH
Good luck!
Refinement welcome! :fingers-crossed:
Click to expand...
Click to collapse
Thank you. You do a very professional.
You can create for me simg2img make_ext4fs adnroid version 4.4_r1 (https://android.googlesource.com/platform/system/extras/).
I really believe you do this. Thank you very much.
[/COLOR]
linhbs said:
Thank you. You do a very professional.
You can create for me simg2img make_ext4fs adnroid version 4.4_r1 (https://android.googlesource.com/platform/system/extras/).
I really believe you do this. Thank you very much.
Click to expand...
Click to collapse
Yes, show for us the master class, and will you make Makefile android-4.4_r1.2 brunch well, or even android-4.3_r2? we are trusting in you...
A.S._id said:
[/COLOR]
Yes, show for us the master class, and will you make Makefile android-4.4_r1.2 brunch well, or even android-4.3_r2? we are trusting in you...
Click to expand...
Click to collapse
Thank you. You can create makefile from https://android.googlesource.com/platform/system/extras/+/refs/heads/master/ext4_utils/ help me.
I want to get Make_ext4fs. If you create make_ext4fs help me. I believe you do this. Thank you very much.
Automated build process and edit images ---------------------------------- -------------------- ------------ V
View attachment 2431377
ext4_utils_4.3
1- Download folder on your computer and unzip
2- Open the folder ext4_utils in the terminal
3- Execute the command
Code:
make
4-Enjoy :laugh:
https://mega.co.nz/#!DwIjyRTY!a9Ega2UnJwDg_E__QV0GVSXqWVUl9IudzdsvNUkTGDU
dell
Hi, I have bought a prototype z ultra, probably BROWN - the tech support said customers aren't allowed to have these, and there's no way to update it. Can I install any custom roms on it? Please, help me, I'm really despaired...
UPDATE:
I flashed cyanogenmod 10.2 on it, but it didn't recognize my sim card, the radio was off, mobile service not working.
Then I flashed the AOSB ROM, now the IMEI has gone lost. Before I made any changes I backed up that TA partiton, maybe that can help in some way? Then I unlocked the bootloader, and flashed the cyanogen.
Does someone know if it's safe to flash an ftf file on a prototype device?
dkanas said:
Hi, I have bought a prototype z ultra, probably BROWN - the tech support said customers aren't allowed to have these, and there's no way to update it. Can I install any custom roms on it? Please, help me, I'm really despaired...
UPDATE:
I flashed cyanogenmod 10.2 on it, but it didn't recognize my sim card, the radio was off, mobile service not working.
Then I flashed the AOSB ROM, now the IMEI has gone lost. Before I made any changes I backed up that TA partiton, maybe that can help in some way? Then I unlocked the bootloader, and flashed the cyanogen.
Does someone know if it's safe to flash an ftf file on a prototype device?
Click to expand...
Click to collapse
Was it on the latest firmware?
I thought that prototypes mostly couldn't unlock the BL, but then there as some on here that could...? confused...
blueether said:
Was it on the latest firmware?
I thought that prototypes mostly couldn't unlock the BL, but then there as some on here that could...? confused...
Click to expand...
Click to collapse
It was on some early software, 14.1.B.1.263, android 4.2.2. I couldn't update it with pc companion and the update center on the phone. The imei was beginning with 0044.
dkanas said:
It was on some early software, 14.1.B.1.263, android 4.2.2. I couldn't update it with pc companion and the update center on the phone. The imei was beginning with 0044.
Click to expand...
Click to collapse
restoring the correct, or even a new, FTF will bring back the imei.
the next issue is if flashtool will flash a new FTF, if it will then you can then use a 4.4.4 or 5.0 ROM hopefully
blueether said:
restoring the correct, or even a new, FTF will bring back the imei.
the next issue is if flashtool will flash a new FTF, if it will then you can then use a 4.4.4 or 5.0 ROM hopefully
Click to expand...
Click to collapse
Yes, i know. But I don't know if the partitions in this prototype match the production models partitions, there could be a difference, like in the gpe model. I don't want to brick this device, it's worth a half of the usual monthly salary in my country Does someone know what exactly is the difference between the regular and the gpe editions?
Update: I think I pulled out the partition layout from my prototype:
Code:
lrwxrwxrwx root root 1970-01-02 04:33 DDR -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 04:33 FOTAKernel -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 04:33 LTALabel -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 04:33 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 04:33 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 04:33 alt_aboot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 04:33 alt_dbi -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 04:33 alt_rpm -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 04:33 alt_s1sbl -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 04:33 alt_sbl1 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 04:33 alt_tz -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 04:33 apps_log -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 04:33 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 04:33 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 04:33 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 04:33 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 04:33 modemst1 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 04:33 modemst2 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 04:33 ramdump -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 04:33 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 04:33 s1sbl -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 04:33 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 04:33 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 04:33 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 04:33 userdata -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-02 04:33 DDR -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 04:33 FOTAKernel -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 04:33 LTALabel -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 04:33 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 04:33 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 04:33 alt_aboot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 04:33 alt_dbi -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 04:33 alt_rpm -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 04:33 alt_s1sbl -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 04:33 alt_sbl1 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 04:33 alt_tz -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 04:33 apps_log -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 04:33 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 04:33 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 04:33 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 04:33 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 04:33 modemst1 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 04:33 modemst2 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 04:33 ramdump -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 04:33 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 04:33 s1sbl -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 04:33 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 04:33 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 04:33 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 04:33 userdata -> /dev/block/mmcblk0p25
What further information can I provide you?
I flashed cyanogenmod 10.2 back, the IMEI is now back - but still no mobile service. Any ideas what could be wrong?
Settings -> About phone -> Status:
Network: unknown
Mobile network type: unknown
Service state: radio off
Roaming: no roaming
Mobile network state: disconnected
IMEI: 0044***********
IMEI SV: 17 (before messing with custom roms it was 01, or 11, can't recall now...)
Baseband version: 8974-AAAAANAZQ-10220006-17
Signal strenght: 2147483647 ASU 255 - that's weird.
Also, network mode is set on WCDMA preferred and I can't switch to another option - it immediately switches back.
Update:
Dial *#*#4636#*#* ---> phone info ---> there is a switch to turn on/off radio - >didn't work either
dkanas said:
I flashed cyanogenmod 10.2 back, the IMEI is now back - but still no mobile service. Any ideas what could be wrong?
Settings -> About phone -> Status:
Network: unknown
Mobile network type: unknown
Service state: radio off
Roaming: no roaming
Mobile network state: disconnected
IMEI: 0044***********
IMEI SV: 17 (before messing with custom roms it was 01, or 11, can't recall now...)
Baseband version: 8974-AAAAANAZQ-10220006-17
Signal strenght: 2147483647 ASU 255 - that's weird.
Also, network mode is set on WCDMA preferred and I can't switch to another option - it immediately switches back.
Update:
Dial *#*#4636#*#* ---> phone info ---> there is a switch to turn on/off radio - >didn't work either
Click to expand...
Click to collapse
I cant see that the partition layout would have changed can uou use adb shell to list the partitions?
Code:
adb shell
su
fdisk -l /dev/block/platform/msm_sdcc.1/mmcblk0
output should be:
Code:
Found valid GPT with protective MBR; using GPT
Disk /dev/block/platform/msm_sdcc.1/mmcblk0: 30535680 sectors, 2622M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 25 entries
First usable sector is 34, last usable sector is 30535646
Number Start (sector) End (sector) Size Code Name
1 256 4351 2048K 0700 TA
2 4352 5375 512K 0700 sbl1
3 5376 5887 256K 0700 s1sbl
4 5888 6015 65536 0700 dbi
5 6016 7039 512K 0700 aboot
6 7040 8063 512K 0700 rpm
7 8064 9087 512K 0700 tz
8 9088 10111 512K 0700 alt_sbl1
9 10112 10623 256K 0700 alt_s1sbl
10 10624 10751 65536 0700 alt_dbi
11 10752 11775 512K 0700 alt_aboot
12 11776 12799 512K 0700 alt_rpm
13 12800 13823 512K 0700 alt_tz
14 13824 54783 20.0M 0700 boot
15 54784 75263 10.0M 0700 ramdump
16 75264 108031 16.0M 0700 FOTAKernel
17 108032 108095 32768 0700 DDR
18 114688 147455 16.0M 0700 LTALabel
19 147456 150527 1536K 0700 modemst1
20 155648 158719 1536K 0700 modemst2
21 163840 166911 1536K 0700 fsg
22 172032 188415 8192K 0700 apps_log
23 188416 4947967 2324M 0700 system
24 4947968 5357567 200M 0700 cache
25 5357568 30535646 12.0G 0700 userdata
[email protected]:/ #
@blueether
Code:
Disk /dev/block/platform/msm_sdcc.1/mmcblk0: 15.6 GB, 15634268160 bytes
255 heads, 63 sectors/track, 1900 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/platform/msm_sdcc.1/mmcblk0p1 1 1901 15267839+ ee EFI GPT
This is what I got
I see I have EFI, and not MBR, which doesn't sound good, am I right?
dkanas said:
@blueether
Code:
Disk /dev/block/platform/msm_sdcc.1/mmcblk0: 15.6 GB, 15634268160 bytes
255 heads, 63 sectors/track, 1900 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/platform/msm_sdcc.1/mmcblk0p1 1 1901 15267839+ ee EFI GPT
This is what I got
I see I have EFI, and not MBR, which doesn't sound good, am I right?
Click to expand...
Click to collapse
not sure on the effect of EFi vs MBR
@blueether
I got this from parted: (sorry it's only a screenshot)
Althought diskinfo utility for android is showing the same values as your fdisk results
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dkanas said:
@blueether
I got this from parted: (sorry it's only a screenshot)
Althought diskinfo utility for android is showing the same values as your fdisk results
Click to expand...
Click to collapse
@blueether
I flashed the newest FTF and it's working! I'll be grateful to death!
for partitions you can also use parted
Code:
adb shell
cd /dev/block
# you can use
Code:
ls
if you want to see which partitions are in this folder. mmcblk0 is the one were everyting in is stored, mmcblk1 is your sdcard.
Code:
parted mmcblk0
print
.
now you see your partitions, with parted you can also adjust them (Don't do that, you'll brick when you make a mistake)
for commando options in parted use
Code:
help
or
Code:
parted
(i forgot)
Anyway good that you fixed your phone, just wanted to share
Can brown devices receive OTA updates? Ever since I have my prototype XZL, I never received a single update from sony, the only updates I receive are those from apps installed via the playstore.