Database Users

Galaxy S III partition layout, basic EFS backup instructions included

The partition layout of the SGS3 is the following:
/dev/block/mmcblk0p9 /system ext4
/dev/block/mmcblk0p12 /data ext4
/dev/block/mmcblk0p8 /cache ext4
/dev/block/mmcblk0p3 /efs ext4
So, backing up efs with adb is easy:
'adb shell'
'dd if=/dev/block/mmcblk0p3 of=/sdcard/efsbackup.img'
'exit'
'adb pull /sdcard/efsbackup.img'
And there you go.
Restoring it is nearly the same process, but *surprise* reversed.
Only restore your efs partition if it's absolutely necessary. Yes, there is only a 0.01% chance of corrupting your efs partition/backup while doing the backup or restore but I won't be able to help you if you corrupt your backup or partition. You've been warned.
The usual disclaimer applies here: I nor XDA-developers.com are responsible for any damage you do to your phone.
But if you must know:
'adb push efsbackup.img /sdcard/efsbackup.img'
'adb shell'
'dd if=/sdcard/efsbackup.img of=/dev/mmcblk0p3'
'exit'
And if you want to be absolutely sure there's no garbage left on your efs partition prior to restoring it:
'adb push efsbackup.img /sdcard/efsbackup.img'
'adb shell'
'dd if=/dev/zero of=/dev/block/mmcblk0p3'
'dd if=/sdcard/efsbackup.img of=/dev/mmcblk0p3'
'exit'
But, and yes this is a major problem. Adb shell isn't functioning properly on our SGS3. As I mentioned in this thread, you can only use one adb shell command per cmd window. If you want to do two things in adb shell, you'll have to open a new command prompt and enter the second command which isn't a huge disaster but it's quite annoying, especially if you've got some heavy duty shell work.

you can also use this for EFS Folder Backup
http://forum.xda-developers.com/showthread.php?t=1308546
Test:
http://translate.google.com/transla...sa=X&tbo=1&tbas=0&biw=1680&bih=925&prmd=imvns

I wonder if there are any information about other partitions? There are suppose to be 12 partitions. I only know the purpose of a couple of them.
Below is what I can find so far.
/dev/block/mmcblk0p1 - unknown
/dev/block/mmcblk0p2 - unknown
/dev/block/mmcblk0p3 - /efs
/dev/block/mmcblk0p4 - unknown
/dev/block/mmcblk0p5 - kernel
/dev/block/mmcblk0p6 - recovery
/dev/block/mmcblk0p7 - unknown
/dev/block/mmcblk0p8 - /cache
/dev/block/mmcblk0p9 - /system
/dev/block/mmcblk0p10 - unknown
/dev/block/mmcblk0p11 - unknown
/dev/block/mmcblk0p12 - /data
Supposing some of the unknown ones are bootloader related.

what partition is for modem?
Thx.

thanks to both of you guys for posting this! i was wondering what the partition layout looked like. now i'm ready to start tweaking even if we don't get root for US versions day1. this is unlikely, though.

Samsung Galaxy S3 I9300 Full Partition Layout
This should fill in the "blanks". From my system dump yesterday when I was searching for the modem (radio) partition. Check my guide in the sig
{
"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"
}

That's great information! The only remaining question is the mapping of sboot.bin and tz.img. I often see these two partitions in many ROMs. It seems likely that these are the first 2 partitions.

Thijs96 said:
.............But if you must know:
'adb push efsbackup.img /sdcard/efsbackup.img'
'adb shell'
'dd if=/sdcard/efsbackup.img of=/dev/mmcblk0p3'
'exit'
And if you want to be absolutely sure there's no garbage left on your efs partition prior to restoring it:
'adb push efsbackup.img /sdcard/efsbackup.img'
'adb shell'
'dd if=/dev/zero of=/dev/block/mmcblk0p3'
'dd if=/sdcard/efsbackup.img of=/dev/mmcblk0p3'
'exit'
.........
Click to expand...
Click to collapse
Hey, why are the /block/ parts missing in some lines of code? looks like an error, isn't it? It should always be /dev/block/mmcblk0p3 if I'm not wrong
Thanks.

WT Ho said:
That's great information! The only remaining question is the mapping of sboot.bin and tz.img. I often see these two partitions in many ROMs. It seems likely that these are the first 2 partitions.
Click to expand...
Click to collapse
The sboot.bin is stored in the mmcblk0p1 partition. No idea what the tz.img stands for though...

is this info still the exact same info for SPH-L710 (Sprint CDMA) S3 Device?
its running android 4.1.1 stock but im rooted and have CWM installed

en11gma said:
is this info still the exact same info for SPH-L710 (Sprint CDMA) S3 Device?
its running android 4.1.1 stock but im rooted and have CWM installed
Click to expand...
Click to collapse
Have a look here http://forum.xda-developers.com/showthread.php?t=1959445

Perka said:
Have a look here http://forum.xda-developers.com/showthread.php?t=1959445
Click to expand...
Click to collapse
i did a search there for sph-l710 (my model and nothing came up)
i dont think that thread was for this phone so i guess the question remains.
is the partition tables in the (1st page) not just the first post correct for SPH-L710?

WT Ho said:
I wonder if there are any information about other partitions? There are suppose to be 12 partitions. I only know the purpose of a couple of them.
Below is what I can find so far.
/dev/block/mmcblk0p1 - unknown
/dev/block/mmcblk0p2 - unknown
/dev/block/mmcblk0p3 - /efs
/dev/block/mmcblk0p4 - unknown
/dev/block/mmcblk0p5 - kernel
/dev/block/mmcblk0p6 - recovery
/dev/block/mmcblk0p7 - unknown
/dev/block/mmcblk0p8 - /cache
/dev/block/mmcblk0p9 - /system
/dev/block/mmcblk0p10 - unknown
/dev/block/mmcblk0p11 - unknown
/dev/block/mmcblk0p12 - /data
Supposing some of the unknown ones are bootloader related.
Click to expand...
Click to collapse
odia gives this to restore bootloaders
# dd if=/sdcard/sboot.bin of=/dev/block/mmcblk0p1
# dd if=/sdcard/tz.img of=/dev/block/mmcblk0p2
# dd if=/sdcard/param.bin of=/dev/block/mmcblk0p4
so 1 = bootloader
2= tz
3= param

en11gma said:
i did a search there for sph-l710 (my model and nothing came up)
i dont think that thread was for this phone so i guess the question remains.
is the partition tables in the (1st page) not just the first post correct for SPH-L710?
Click to expand...
Click to collapse
well maybe you can use the commands to find your table?
in adb type:
mount

Sorry for bumping this thread but nothing is working for me. I've tried the EFS pro backup tool and only get "connecting to device" for hours. So I saw this thread and thought manually doing it would work fine, and I get "permission denied".
I'm on a rooted, US variant, the SPH-L710. Even backing up the MSL has posed problems, so idk what is going on. Please help. I've been searching the site for 2 days and came up with tons of threads that just do not work.

Now if only we could resize these partitions!
Sent from my GT-I9300 using Tapatalk

AzzidReign said:
Sorry for bumping this thread but nothing is working for me. I've tried the EFS pro backup tool and only get "connecting to device" for hours. So I saw this thread and thought manually doing it would work fine, and I get "permission denied".
I'm on a rooted, US variant, the SPH-L710. Even backing up the MSL has posed problems, so idk what is going on. Please help. I've been searching the site for 2 days and came up with tons of threads that just do not work.
Click to expand...
Click to collapse
AS this is not your phones forum i suggest you ask in your phones forum as there are significant differences in the hardware .
The I9300 stickys have a network EFS IMEI thread if you want to read that but any I9300 firmware or fixes may brick a different phone .

OH1 partitions
Thought I should post the latest partition for OH1 firmware (Stagefright BUG FIX firmware)
[email protected]:/ # ls -al /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 2013-12-31 23:48 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-12-31 23:48 backup -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2013-12-31 23:48 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-12-31 23:48 cache -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2013-12-31 23:48 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-12-31 23:48 fota -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2013-12-31 23:48 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2013-12-31 23:48 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2013-12-31 23:48 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-12-31 23:48 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-12-31 23:48 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-12-31 23:48 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-12-31 23:48 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-12-31 23:48 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2013-12-31 23:48 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2013-12-31 23:48 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-12-31 23:48 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-12-31 23:48 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-12-31 23:48 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-12-31 23:48 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2013-12-31 23:48 system -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2013-12-31 23:48 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-12-31 23:48 userdata -> /dev/block/mmcblk0p15

[GUIDE][HOW-TO]Extracting A 'boot.img' From An FTF

This is compatible with a wide variety of Xperia Devices​
A guide bought to you by matt4321 and DaRk-L0rD​
Here I am going to show you how to get the boot.img (kernel) out of an FTF! This procedure is most useful for Locked Bootloaders as it means we can upgrade without the need for FlashTool!
This guide assumes that you have FlashTool installed on your PC
#############################​
Step 1:
You need a file extractor such as WinRar or 7zip.
Once this is done you want to open the whole FTF in the extractor. You will see a lot of .sin files!
The one we want is 'kernel.sin', not 'fotakernel.sin'.
Extract that file to somewhere appropriate on your computer, like the desktop!
{
"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"
}
#############################​
Step 2:
Now you need to open FlashTool,
At the top you will see a tab that says 'Tools', click on that and select 'SIN Editor'. You will see a button that has 3 dots in the top right. This is the browse button, click on it and locate where your SIN file is.
One that is done, you need to click on 'Dump Data'.
This will dump the 'kernel.elf' to the same location of where your 'kernel.sin' is.
#############################​
Step 3:
The next part is simple,
All you need to do is rename your 'kernel.elf' to 'boot.img' and put it in a flashable zip, to make the flashable zip follow the instructions by @DaRk-L0rD in the 2nd post!
Keep in mind that the kernel should be 20mb.
#############################​
Step 4:
Enjoy! The kernel can be flashed via PhilZ for Locked Bootloaders and will work on both Locked and Unlocked bootloaders, since it is an official kernel it is signed by the Sony key so will be fine for Locked Bootloaders.

If you want to make a kernel's flashable zip
What you need:
1. winrar
2. Notepad++
3. The attachment: View attachment META-INF.rar
4. boot.img or kernel.elf
Procedure:
1. Extract the META-INF folder from the rar archive previously downloaded.
2. Open it and go META-INF -> google -> android and using Notepad++ edit the updater-script (right click on it and choose open with Notepad++).
3. Now you can see that the updater-script looks like this:
4. The line package_extract_file("boot.img", "/dev/block/mmcblkXXX"); should be edited ONLY for 2 reasons.
In case you have a kernel.elf (custom kernels) instead of a boot.img
To edit the mmcblkXXX partition since it's different for each device
5. At the end of this post you will find a list of the /mmcblkXXX . For each device are different to choose wisely!!
In my case is the /mmcblk0p4, so will look like this:
6. ui_print(""); , inside the " " you can add the text what you want. Remember that all the users will use this zip will be able to see what you wrote, so please be polite
For example:
ui_print("Installing the kernel");
ui_print("matt4321");
ui_print("DaRk-L0rD");
ui_print("");
package_extract_file("boot.img", "/dev/block/mmcblk0p4");
ui_print("Enjoy");
ui_print("Hit the thanks button");
Click to expand...
Click to collapse
----------------In case the kernel's format is kernel.elf, you can change the line and make it look like this: ----------------
package_extract_file("kernel.elf", "/dev/block/mmcblk0p4"); (as i said you before, the partition is my case is mmcblk0p4)
Also, make sure that you leave an empty line at the end of the commands (as you can see the line number 8 is empty).
6. Now select the META-INF folder and the boot.img or the kernel.elf file, right click on them and select Add to archive.
7. Make sure that the Archive format is ZIP and the Compression method is Store
8. Now your flashable zip is ready!
9. Enjoy
List of /mmcblkXXX
Each device has different partition for the kernel. Here is a list of those we found so far:
Xperia SP ---- /dev/block/mmcblk0p4
Xperia T---- /dev/block/mmcblk0p4
Xperia V---- /dev/block/mmcblk0p4
Xperia TX---- /dev/block/mmcblk0p4
Xperia Z1---- /dev/block/mmcblk0p14
Xperia E---- /dev/block/mmcblk0p3
Xperia Tipo---- /dev/block/mmcblk0p3
Xperia S---- /dev/block/mmcblk0p3
Xperia Ion---- /dev/block/mmcblk0p3
Since we don't know all devices' partition, you should give us a hand.
Here is what you have to do:
Procedure:
via adb shell
ls -l /dev/block/platform/
Click to expand...
Click to collapse
then pick the top one (in my case is msm_sdcc.1), so
ls -l /dev/block/platform/msm_sdcc.1/by-name
Click to expand...
Click to collapse
Then which ever says 'kernel' is the one we want.

On portal
Congrats you 2

Took much of wrong/incorrect/partial info in this thread...

DooMLoRD said:
Took much of wrong/incorrect/partial info in this thread...
Click to expand...
Click to collapse
Could you give us a hand with the right/correct/total mate?
We tested all this in different Xperia devices and never had issues and that's why we made the tutorial.

DooMLoRD said:
Took much of wrong/incorrect/partial info in this thread...
Click to expand...
Click to collapse
Reiterating what DaRk-L0rD said, what can we change/how can we make it better?
Sent from my LT30p using Tapatalk

DaRk-L0rD said:
Could you give us a hand with the right/correct/total mate?
We tested all this in different Xperia devices and never had issues and that's why we made the tutorial.
Click to expand...
Click to collapse
matt4321 said:
Reiterating what DaRk-L0rD said, what can we change/how can we make it better?
Sent from my LT30p using Tapatalk
Click to expand...
Click to collapse
btw you can still use with this script :
Code:
package_extract_file("kernel.elf", "/dev/block/platform/msm_sdcc.1/by-name/Kernel");
Code:
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/Kernel");
you don't need to change compressed zip to store, normal is work

For a long time since Xperia X10, I think we can't flash kernel using an update package to flash in CWM?

This guide is very simple and very interesting, especially for locked bootloader users, but with just "rename" it would not cause a very high risk? ...
sorry with my question (just want to make sure ), because I know about kernel on Xperia devices that are quite complicated (unlike the Galaxy device)
btw, thank for the very simple guide, this is very useful, especially for my rom

ibanez7 said:
This guide is very simple and very interesting, especially for locked bootloader users, but with just "rename" it would not cause a very high risk? ...
sorry with my question (just want to make sure ), because I know about kernel on Xperia devices that are quite complicated (unlike the Galaxy device)
btw, thank for the very simple guide, this is very useful, especially for my rom
Click to expand...
Click to collapse
It's the method I have used for countless firmwares on the T, have done it for the V and TX as well. renaming it isn't totally necessary afaik, people are just more comfortable with the thought of a boot.img rather than a kernel.elf

New possibilities
Will this open up the possibility of upgrading android beyond 4.1.2 on locked bootloader on Xperia S and Ion?

osamaanjum said:
Will this open up the possibility of upgrading android beyond 4.1.2 on locked bootloader on Xperia S and Ion?
Click to expand...
Click to collapse
I don't think so, as it's just a method of flashing a stock kernel via recovery instead of using Flashtool. It will not allow modified/custom kernels to run on a device with a locked bootloader.
Sent from my C6603 using Tapatalk

osamaanjum said:
Will this open up the possibility of upgrading android beyond 4.1.2 on locked bootloader on Xperia S and Ion?
Click to expand...
Click to collapse
It just allows locked bootloaders to flash a kernel via a locked bootloader recovery. It helps for people to update without the need for flashtool
Sent from my LT30p using Tapatalk

When you update kernel, I think you have to update rpm too.
rpm is proprietary firmware file to be added to the kernel.
Code:
package_extract_file("rpm.elf", "/dev/block/platform/msm_sdcc.1/by-name/rpm");

Can you tell me what is the partition layout of 2011 device such as xperia mini. /dev/block/mmcblk???

no /dev/block/platform folder (xperia z)
where gonna help a bit by finding info fo SGP321 (xperia tablet z) but as title says I could not find the listed folder
Edit:
I found it but this is what I get
[email protected]:/dev/block/platform/msm_sdcc.1 $ ls -l /dev/block/platform/msm_sdcc
.1/by-name
/platform/msm_sdcc.1/by-name <
lrwxrwxrwx root root 2014-06-08 20:48 B2B -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2014-06-08 20:48 FOTAKernel -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-06-08 20:48 LTALabel -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-06-08 20:48 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-06-08 20:48 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-06-08 20:48 alt_aboot -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-06-08 20:48 alt_rpm -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-06-08 20:48 alt_s1sbl2 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-06-08 20:48 alt_sbl1 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-06-08 20:48 alt_sbl2 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-06-08 20:48 alt_sbl3 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-06-08 20:48 alt_tz -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-06-08 20:48 apps_log -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-06-08 20:48 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-06-08 20:48 cache -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2014-06-08 20:48 m9kefs1 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-06-08 20:48 m9kefs2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-06-08 20:48 m9kefs3 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-06-08 20:48 ramdump -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-06-08 20:48 rpm -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-06-08 20:48 s1sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-06-08 20:48 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-06-08 20:48 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-06-08 20:48 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-06-08 20:48 system -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-06-08 20:48 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-06-08 20:48 userdata -> /dev/block/mmcblk0p27

i extracted the kernel.sin from Sony xperia z 4.4.4 ftf and using flashtool to dum data and renamed .elf to Boot.img but its only 7.86 mb ??????? while trying to cook a rom with Android kitchen , Android kitchen gives me an error that android magic header not found at start of boot.img and then a warning Android header not found in boot.img ( Unsupported format ) any idea what is going on ?
---------- Post added at 06:38 AM ---------- Previous post was at 06:04 AM ----------
Fota kernel is the kernel that you mentioned in ?? if no than i do not see any kernel listed here in adb shell.
if yes then here you can it add in the op.
Sony Xperia Z (C6603)
FOTAKernel -> /dev/block/mmcb1k0p23
ls -l /dev/block/platform/
then pick the top one (in my case is msm_sdcc.1), so
Quote:
ls -l /dev/block/platform/msm_sdcc.1/by-name
Then which ever says 'kernel' is the one we want. ???

In recent Xperia devices, kernel partition is called boot.

For android 4.4+ boot.img should b below 9 mb and its the correct one..So if u don't get a 20 mb sized boot.img means don't afraid. Just go ahead.

Epic guide man! You just saved some time for me with this guide!
That's me when I was searching for elf2img software on google and then I found your thread. xD

P7000 root guide for UNIX users

Hi guys.
I'm an ArchLinux user and was quite disappointed to see we needed to use a Windows-based software in order to replace some partitions. This reminded me the old ages of Odin on Samsung devices, when Heimdall didn't exist yet. I initially posted my tutorial on the Elephone forums, but the latter is really buggy and trying to format the command properly does not give the expected result, seeing HTML code inserted everywhere.
Just to let you know. If you are using a UNIX based system like OS X or a GNU/Linux distribution, or if simply do not want to use the piece of software specified above. You have to know that all features implemented in the Flash Tool can be made manually. Here is a tutorial in that regard:
Please make sure Settings -> Developer options -> USB debogging is enabled. This should be the case by default, using the stock ROM or with a brand new P7000 device.
Install adb with one of the method for your OS.
In a terminal, type
Code:
adb shell
You should get a prompt like this
Code:
[email protected]_jbaol_3m_fhd_elephone:/ #
NOTE: The serial number is by default 0123456789ABCDEFG. It seems Elephone just too the SoC from MediaTek without even changing the serial number. You will thus have a problem if you connect several P7000 devices to the same computer. adb uses indeed that number to differentiate which device send commands to, with the following adb command:
Code:
adb -s 0123456789ABCDEFG shell
The recovery should be on the partition number 8. Check that by typing:
Code:
/dev/block/platform/mtk-msdc.0/by-name/
In the result, you should see a line with:
Code:
lrwxrwxrwx root root 2015-07-10 16:34 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-07-10 16:34 cache -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-07-10 16:34 expdb -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-07-10 16:34 flashinfo -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-07-10 16:34 lk -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-07-10 16:34 logo -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-07-10 16:34 metadata -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-07-10 16:34 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-07-10 16:34 para -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-07-10 16:34 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-07-10 16:34 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-07-10 16:34 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-07-10 16:34 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-07-10 16:34 seccfg -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-07-10 16:34 secro -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-07-10 16:34 system -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-07-10 16:34 tee1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-07-10 16:34 tee2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-07-10 16:34 userdata -> /dev/block/mmcblk0p18
Which confirms the assumptions.
Now, make a backup of the original recovery if anything goes wrong. First we are gonna dump the partition content to the sdcard emulated location (even if you do not have a SD card, that location is present). Type:
Code:
dd if=/dev/block/mmcblk0p8 of=/sdcard/recovery_backup.img
To pull that file to your computer, open a new terminal on your computer, change dir to the location you want the backup saved in and type:
Code:
adb pull /sdcard/recovery_backup.img
Now, download the RAR archive from Elephone. Extract it. In the folder "SuperSU/p7000-recovery/", you can find the file recovery.img. Send that file to your device with adb, by typing still in a terminal on your computer:
Code:
adb push ./recovery.img /sdcard/recovery.img
Now you just need to replace the recovery with the file now on your phone.
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p8
This should have been copied with successful and you see this result appearing on the screen:
Code:
19720+0 records in
19720+0 records out
10096640 bytes transferred in 1.336 secs (7557365 bytes/sec)
Now you just need to reboot to the recovery to make sure the process worked flawlessly. From your computer type,
Code:
adb reboot recovery
or shut down the device manually, and boot it up pressing and holding the power and volume up buttons.
Hope this helps. My 2 cents.

downgrade bootloader 5.11 to 5.01

i remember a great developer ( odia ) who downgrade the I9300 xella
has someone try this way ?
http://forum.xda-developers.com/gal.../util-sboot-checker-simple-downgrade-t2081748
this method was used also for N7100
http://forum.xda-developers.com/showthread.php?t=2089353
I HAVE NOT TRY THIS WITH N910C I JUST ASK IF SOMEONE TRY THIS !!!

kondronaute said:
i remember a great developer ( odia ) who downgrade the I9300 xella
has someone try this way ?
http://forum.xda-developers.com/gal.../util-sboot-checker-simple-downgrade-t2081748
this method was used also for N7100
http://forum.xda-developers.com/showthread.php?t=2089353
I HAVE NOT TRY THIS WITH N910C I JUST ASK IF SOMEONE TRY THIS !!!
Click to expand...
Click to collapse
Very interesting....
Only thing to verify if partitions are the same. They should be. Since this is 2 years old wonder if Samsung has caught on.

dicksteele said:
Very interesting....
Only thing to verify if partitions are the same. They should be. Since this is 2 years old wonder if Samsung has caught on.
Click to expand...
Click to collapse
first look there are same, I am happy with the new rom and I haven't time to test .....
if someone want to test he must take last abd version .... (you can download the zip with batch...)

kondronaute said:
first look there are same, I am happy with the new rom and I haven't time to test .....
if someone want to test he must take last abd version .... (you can download the zip with batch...)
Click to expand...
Click to collapse
I just got my phone last month and did the OJ5 update not realizing it was locked. I was on ATT Note 2 for years and years and never got to try a Dr Ketan's ROM. Pissed with the new locked bootloader.
So I'm ODIN flashing to full COJ5.
Will back up efs, param, pit and whatever else I can think of and give it a shot.
Obviously it seems to simple to work.
I did a compare yesterday on the pre-locked 5.1.1 bootloaders and the locked one.
I saw a few things in there that were different and I modified them in the locked one.
My edited one flashed so I was surprised. But I tried to downgrade and it didn't work..... So what I changed didn't make a difference. Yet ! :laugh:

dicksteele said:
I just got my phone last month and did the OJ5 update not realizing it was locked. I was on ATT Note 2 for years and years and never got to try a Dr Ketan's ROM. Pissed with the new locked bootloader.
So I'm ODIN flashing to full COJ5.
Will back up efs, param, pit and whatever else I can think of and give it a shot.
Obviously it seems to simple to work.
I did a compare yesterday on the pre-locked 5.1.1 bootloaders and the locked one.
I saw a few things in there that were different and I modified them in the locked one.
My edited one flashed so I was surprised. But I tried to downgrade and it didn't work..... So what I changed didn't make a difference. Yet ! :laugh:
Click to expand...
Click to collapse
ok good luck
i think this is the better option in the past i do it for 3 or 4 I9300 without any pbm hope it's same again

kondronaute said:
ok good luck
i think this is the better option in the past i do it for 3 or 4 I9300 without any pbm hope it's same again
Click to expand...
Click to collapse
Double checking things Back on full stock
[email protected]:/dev/block/platform/15540000.dwmmc0/by-name $ ls -la
ls -la
lrwxrwxrwx root root 2015-11-28 11:15 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-11-28 11:15 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-11-28 11:15 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-11-28 11:15 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-11-28 11:15 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-11-28 11:15 CDMA-RADIO -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-11-28 11:15 DNT -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-11-28 11:15 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-11-28 11:15 HIDDEN -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-11-28 11:15 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-11-28 11:15 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-11-28 11:15 PERSDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-11-28 11:15 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-11-28 11:15 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-11-28 11:15 RESERVED2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-11-28 11:15 SYSTEM -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-11-28 11:15 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-11-28 11:15 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-11-28 11:15 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-11-28 11:15 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-11-28 11:15 m9kefs3 -> /dev/block/mmcblk0p6
# dd if=/sdcard/sboot.bin of=/dev/block/mmcblk0p1 BOTA0 Restore Bootloader (I hope!)
# dd if=/sdcard/tz.img of=/dev/block/mmcblk0p2 BOTA1 Restore tz.img
# dd if=/sdcard/param.bin of=/dev/block/mmcblk0p4 PARAM Restore PARAM
# dd if=/dev/block/mmcblk0 of=/sdcard/N910C.pit bs=8 count=580 skip=2176 Backup PIT
PIT -> /dev/block/mmcblk0
BOOT -> /dev/block/mmcblk0p9 Kernel
RECOVERY-> /dev/block/mmcblk0p10 TWRP
RADIO -> /dev/block/mmcblk0p13 Modem
Starting partition backups and continuing internal debate of how confident I am I won't f**k something up

dicksteele said:
Double checking things Back on full stock
[email protected]:/dev/block/platform/15540000.dwmmc0/by-name $ ls -la
ls -la
lrwxrwxrwx root root 2015-11-28 11:15 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-11-28 11:15 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-11-28 11:15 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-11-28 11:15 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-11-28 11:15 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-11-28 11:15 CDMA-RADIO -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-11-28 11:15 DNT -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-11-28 11:15 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-11-28 11:15 HIDDEN -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-11-28 11:15 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-11-28 11:15 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-11-28 11:15 PERSDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-11-28 11:15 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-11-28 11:15 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-11-28 11:15 RESERVED2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-11-28 11:15 SYSTEM -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-11-28 11:15 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-11-28 11:15 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-11-28 11:15 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-11-28 11:15 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-11-28 11:15 m9kefs3 -> /dev/block/mmcblk0p6
# dd if=/sdcard/sboot.bin of=/dev/block/mmcblk0p1 BOTA0 Restore Bootloader (I hope!)
# dd if=/sdcard/tz.img of=/dev/block/mmcblk0p2 BOTA1 Restore tz.img
# dd if=/sdcard/param.bin of=/dev/block/mmcblk0p4 PARAM Restore PARAM
# dd if=/dev/block/mmcblk0 of=/sdcard/N910C.pit bs=8 count=580 skip=2176 Backup PIT
PIT -> /dev/block/mmcblk0
BOOT -> /dev/block/mmcblk0p9 Kernel
RECOVERY-> /dev/block/mmcblk0p10 TWRP
RADIO -> /dev/block/mmcblk0p13 Modem
Starting partition backups and continuing internal debate of how confident I am I won't f**k something up
Click to expand...
Click to collapse
i think you can try without tz.img and param.bin
look at this rar (i put the last adb)
(when I do it with I9300 the phone was on ....)

kondronaute said:
i think you can try without tz.img and param.bin
look at this rar (i put the last adb)
(when I do it with I9300 the phone was on ....)
Click to expand...
Click to collapse
No dice with and without param.bin. Good news still boots.
Still shows bootloader of COJ5
Maybe it does need tz.img

dicksteele said:
No dice with and without param.bin. Good news still boots.
Still shows bootloader of COJ5
Maybe it does need tz.img
Click to expand...
Click to collapse
yes god news i boot but seem not do the job....
do you try w ith only this script
@files1\adb push sboot.bin /sdcard/sboot.bin
 @files1\adb shell su -c "dd if=/sdcard/sboot.bin of=/dev/block/mmcblk0p1"
 @files1\adb shell rm /sdcard/sboot.bin
 @files1\adb reboot fota_bl

kondronaute said:
yes god news i boot but seem not do the job....
do you try w ith only this script
@files1\adb push sboot.bin /sdcard/sboot.bin
@files1\adb shell su -c "dd if=/sdcard/sboot.bin of=/dev/block/mmcblk0p1"
@files1\adb shell rm /sdcard/sboot.bin
@files1\adb reboot fota_bl
Click to expand...
Click to collapse
Yeah, I did that
Then I bumped it up a notch
@files1\adb shell su -c "dd if=/sdcard/sboot.bin of=/dev/block/platform/15540000.dwmmc0/by-name/BOTA0"
 @files1\adb shell getprop ro.boot.bootloader
 @pause
After the pause it comes back with the COJ5.
Rebooting, running same command, COJ5.
Assuming this will create a tz.img.... I haven't seen anything referring to it for 5.1.1
dd if=/dev/block/mmcblk0p2 of=/sdcard/cache.rfs bs=4096
dd if=/dev/block/platform/15540000.dwmmc0/by-name/BOTA1 of=/sdcard/tz.img bs=4096
Also just downloaded 11/27 firmware for Kenya going to try that. I've been using the sboot.bin from here
http://forum.xda-developers.com/note-4/development/rom-note-4-mod-t3244665

dicksteele said:
Yeah, I did that
Then I bumped it up a notch
@files1\adb shell su -c "dd if=/sdcard/sboot.bin of=/dev/block/platform/15540000.dwmmc0/by-name/BOTA0"
@files1\adb shell getprop ro.boot.bootloader
@pause
After the pause it comes back with the COJ5.
Rebooting, running same command, COJ5.
Assuming this will create a tz.img.... I haven't seen anything referring to it for 5.1.1
dd if=/dev/block/mmcblk0p2 of=/sdcard/cache.rfs bs=4096
dd if=/dev/block/platform/15540000.dwmmc0/by-name/BOTA1 of=/sdcard/tz.img bs=4096
Also just downloaded 11/27 firmware for Kenya going to try that. I've been using the sboot.bin from here
http://forum.xda-developers.com/note-4/development/rom-note-4-mod-t3244665
Click to expand...
Click to collapse
after the pause can you reboot directly in download mode and flash again the new bootloader with odin
try this bootloader
N910CXXU1COH4 Bootloader (5.1.1)(ONLY for N910C users)
http://forum.xda-developers.com/showpost.php?p=58867937&postcount=3
I am very pessimistic with this ...

kondronaute said:
after the pause can you reboot directly in download mode and flash again the new bootloader with odin
try this bootloader
N910CXXU1COH4 Bootloader (5.1.1)(ONLY for N910C users)
http://forum.xda-developers.com/showpost.php?p=58867937&postcount=3
I am very pessimistic with this ...
Click to expand...
Click to collapse
You should be .... No dice.
But again. I was able to pull battery go back into download mode and ODIN flash the COJ5 I had
Kenya firmware from 11/27 same thing...

dicksteele said:
You should be .... No dice.
But again. I was able to pull battery go back into download mode and ODIN flash the COJ5 I had
Kenya firmware from 11/27 same thing...
Click to expand...
Click to collapse
when you pull the battery after flashed a pre locked bootloader can you in the go reflash the same pre locked bl with odin ( it flash or it say error .....)

kondronaute said:
when you pull the battery after flashed a pre locked bootloader can you in the go reflash the same pre locked bl with odin ( it flash or it say error .....)
Click to expand...
Click to collapse
Same error NAND write fail

dicksteele said:
Same error NAND write fail
Click to expand...
Click to collapse
it was a pleasure to collaborate with u
i hope a developer look at this pbm; really i am happy with 5.1.1 coz i can use xposed and it's better than 5.0.1 but I love to have the choice, I love the idea to be free and I don't understand why samsung and other lock our phones; personally I have no care for guaranty.... i want just be free to play with my phone !

kondronaute said:
it was a pleasure to collaborate with u
i hope a developer look at this pbm; really i am happy with 5.1.1 coz i can use xposed and it's better than 5.0.1 but I love to have the choice, I love the idea to be free and I don't understand why samsung and other lock our phones; personally I have no care for guaranty.... i want just be free to play with my phone !
Click to expand...
Click to collapse
Agree.
I'm really having no issues with 5.1.1.
I'm with you, it was more of a challenge to see if it could be done. CM 13 seems to be moving along so that may take the desire to flash back to lessen. Take care. I'll be around

dicksteele said:
Agree.
I'm really having no issues with 5.1.1.
I'm with you, it was more of a challenge to see if it could be done. CM 13 seems to be moving along so that may take the desire to flash back to lessen. Take care. I'll be around
Click to expand...
Click to collapse
please guys for those who are on COH4 can you install partition backup (wanam) from store and give us the backup of
BOTA0
BOTA1
PARAM
please in raw partion image (img)
thank u by advance

please friends it will take you just a little of your time and if work it will help all
btw if you are in kitkat also you can give us

How can I backup everything on my rooted N4? (Every single thing)

This might seem like a newbie question but this isn't the case.
I already know Titanium backup exists and I have been using it for years. However a few months back I suffered from the ''infamous brick'' seen everywhere on this thread caused by the unofficial CM13 ROM.
This brick corrupted everything on my phone (EFS Partition, etc) and the ONLY thing i could ever boot into was the recovery.
2 months and $150 later in repairs (literally everyone failed to fix it software-side) I learned my lesson
I need to back up my entire phone incase something like this happens again. What app should I use, and what should I back up?
Thanks

Do a nandroid backup from the recovery

Nortabun said:
This might seem like a newbie question but this isn't the case.
I already know Titanium backup exists and I have been using it for years. However a few months back I suffered from the ''infamous brick'' seen everywhere on this thread caused by the unofficial CM13 ROM.
This brick corrupted everything on my phone (EFS Partition, etc) and the ONLY thing i could ever boot into was the recovery.
2 months and $150 later in repairs (literally everyone failed to fix it software-side) I learned my lesson
I need to back up my entire phone incase something like this happens again. What app should I use, and what should I back up?
Thanks
Click to expand...
Click to collapse
Here is a snapshot of everything on the entire phone.
[email protected]:/dev/block/platform/15540000.dwmmc0/by-name # ls -la
ls -la
lrwxrwxrwx root root 2015-12-31 13:08 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-12-31 13:08 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-12-31 13:08 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-12-31 13:08 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-12-31 13:08 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-12-31 13:08 CDMA-RADIO -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-12-31 13:08 DNT -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-12-31 13:08 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-12-31 13:08 HIDDEN -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-12-31 13:08 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-12-31 13:08 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-12-31 13:08 PERSDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-12-31 13:08 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-12-31 13:08 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-12-31 13:08 RESERVED2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-12-31 13:08 SYSTEM -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-12-31 13:08 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-12-31 13:08 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-12-31 13:08 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-12-31 13:08 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-12-31 13:08 m9kefs3 -> /dev/block/mmcblk0p6
Option 1 Command line:
Quick and easy way to backup /system
dd if=/dev/block/mmcblk0p18 of=/sdcard/system.img bs=4096
Quick and easy way to backup the kernel
dd if=/dev/block/mmcblk0p9 of=/sdcard/boot.img bs=4096
Quick and easy way to back up EFS
dd if=/dev/block/mmcblk0p3 of=/sdcard/efs.img bs=4096
Quick and easy way to back up Radio
dd if=/dev/block/mmcblk0p13 of=/sdcard/radio.img bs=4096
Quick and easy way to back up Recovery
dd if=/dev/block/mmcblk0p10 of=/sdcard/recovery.img bs=4096
Create a directory on your machine. C:\Phonerecovery
Copy all those files from /sdcard to that directory.
With those images you can build a ODIN flash file
Using Cygwin or a Linux machine: tar -H ustar -c boot.img kernel.img recovery.img system.img > Unf*ckMyNote4.tar
Using ODIN to restore stock firmware usually will unf*ck a CM flashed phone. Keeping one handy from a provider of stock Samsung Note 4 firmware is also a good thing.
Option 2:
Custom recovery like CWM / TWRP installed on your phone
Since you were able to reboot into recovery having a TWRP backup probably would have saved you.
{
"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"
}