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

Note 3 Japan version SCL22 sim unlock

Hi
Phone get rooted now. but i can't unlock to use sim free. how can i get network control unlock key ?

doantri said:
Hi
Phone get rooted now. but i can't unlock to use sim free. how can i get network control unlock key ?
Click to expand...
Click to collapse
How to display network unlock guy?

how did you root your SCL22 Note 3?

can u tell me what is the method that you used to root your SCL22 note 3
because i have the same problem .

Hi
You should use CWM SM-N9005 then update SU via CWM
I need unlock phone to use with gsm simcard but can't get unlock code.

doantri said:
Hi
You should use CWM SM-N9005 then update SU via CWM
I need unlock phone to use with gsm simcard but can't get unlock code.
Click to expand...
Click to collapse
can you share the file you use to unlock your phone?
you can you galaxim(i think) you can download in google play for free or regionlock away

beast08 said:
can you share the file you use to unlock your phone?
you can you galaxim(i think) you can download in google play for free or regionlock away
Click to expand...
Click to collapse
- CWM recovery for N9005: https://mega.co.nz/#!C0Y1RbyT!Iq1A1Aaef1qioyDHkGQVtkRUdGN0LCa37umKGMDyDs8
- SuperSU: http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
first install CWM recovery then flash SuperSU via recovery

vndnguyen said:
- CWM recovery for N9005: https://mega.co.nz/#!C0Y1RbyT!Iq1A1Aaef1qioyDHkGQVtkRUdGN0LCa37umKGMDyDs8
- SuperSU: http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
first install CWM recovery then flash SuperSU via recovery
Click to expand...
Click to collapse
i tried this method before, flashing the SuperSU v1.86 to my phone, but everytime im opening the app, it saying su binary need to update, abd the phone will reboot to CWM recovery, and when i checked it will Root Checker, it says the phone is not properly rooted.

beast08 said:
i tried this method before, flashing the SuperSU v1.86 to my phone, but everytime im opening the app, it saying su binary need to update, abd the phone will reboot to CWM recovery, and when i checked it will Root Checker, it says the phone is not properly rooted.
Click to expand...
Click to collapse
I just provided these links per suggestion from doantri
I'm not sure if it works for your phone or not. Sorry to hear that.

Can you re upload the cwm file in other site? Im getting a hard tome downloading a file from mega
Sent from my SCL22 using xda app-developers app

need help
Hi everybody. I successfully rooted my scl22 using the instructions in a chinese site : " SCL22 root & sim unlock
Galaxy Note3 SCL22のRoot化(SC-01Fも対応)
SM-N9005用CWMをOdinから焼き込み、SuperSUをインストールすればRoot化完了。
・SM-N9005用CWMのダウンロード先
n9005-cwm-recovery-6.0.4.5(1116).tar
・SuperSUのダウンロード先
UPDATE-SuperSU-v1.65.zip
・sgs3_rooting_supersu_v3.zipも必要です。ググってください。
○順番
1.CWMをOdinで焼きこみ。
2.CWMを起動し、sgs3_rooting_supersu_v3.zipをインストール。
3.続けてUPDATE-SuperSU-v1.65.zipをインストール。
4.再起動すればsuが効くようになります。
○カウントアップはCWMを焼くとKNOX WARRANTYが変化します。
他は初期ROM焼いて初期化すれば元に戻ります。
※カウントアップするとオサイフがNGになります。
※Root化されたsystem.imgのみ焼けば大丈夫かも？
KNOX WARRANTY VOID : 0x0
↓
KNOX WARRANTY VOID : 0x1
Galaxy Note 3 SCL22の内部パーティション
[email protected]:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name/
ls -l /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 1970-01-02 04:36 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 04:36 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 04:36 backup -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 04:36 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 04:36 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 04:36 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 04:36 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 04:36 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 04:36 fota -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 04:36 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 04:36 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 04:36 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 04:36 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 04:36 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 04:36 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 04:36 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 04:36 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 04:36 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 04:36 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 04:36 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 04:36 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 04:36 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 04:36 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 04:36 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 04:36 userdata -> /dev/block/mmcblk0p25
zhongkai cheng*时间：*下午7:20
,but not beeing experienced in programming , i wasn't able to aply the second set of instructions. There is a script that should be run and i do not know how to do that. Maybe someone with experience can help us.

Please anyone help us to SIM unlock Note 3 SCL22
mvmaos said:
Hi everybody. I successfully rooted my scl22 using the instructions in a chinese site : " SCL22 root & sim unlock
Galaxy Note3 SCL22のRoot化(SC-01Fも対応)
SM-N9005用CWMをOdinから焼き込み、SuperSUをインストールすればRoot化完了。
・SM-N9005用CWMのダウンロード先
n9005-cwm-recovery-6.0.4.5(1116).tar
・SuperSUのダウンロード先
UPDATE-SuperSU-v1.65.zip
・sgs3_rooting_supersu_v3.zipも必要です。ググってください。
○順番
1.CWMをOdinで焼きこみ。
2.CWMを起動し、sgs3_rooting_supersu_v3.zipをインストール。
3.続けてUPDATE-SuperSU-v1.65.zipをインストール。
4.再起動すればsuが効くようになります。
○カウントアップはCWMを焼くとKNOX WARRANTYが変化します。
他は初期ROM焼いて初期化すれば元に戻ります。
※カウントアップするとオサイフがNGになります。
※Root化されたsystem.imgのみ焼けば大丈夫かも？
KNOX WARRANTY VOID : 0x0
↓
KNOX WARRANTY VOID : 0x1
Galaxy Note 3 SCL22の内部パーティション
[email protected]:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name/
ls -l /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 1970-01-02 04:36 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 04:36 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 04:36 backup -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 04:36 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 04:36 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 04:36 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 04:36 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 04:36 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 04:36 fota -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 04:36 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 04:36 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 04:36 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 04:36 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 04:36 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 04:36 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 04:36 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 04:36 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 04:36 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 04:36 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 04:36 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 04:36 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 04:36 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 04:36 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 04:36 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 04:36 userdata -> /dev/block/mmcblk0p25
zhongkai cheng*时间：*下午7:20
,but not beeing experienced in programming , i wasn't able to aply the second set of instructions. There is a script that should be run and i do not know how to do that. Maybe someone with experience can help us.
Click to expand...
Click to collapse

hey
anyone know a method to get unlock code for SCL22 Galaxy note 3 ?

mvmaos said:
Hi everybody. I successfully rooted my scl22 using the instructions in a chinese site : " SCL22 root & sim unlock
Galaxy Note3 SCL22のRoot化(SC-01Fも対応)
SM-N9005用CWMをOdinから焼き込み、SuperSUをインストールすればRoot化完了。
・SM-N9005用CWMのダウンロード先
n9005-cwm-recovery-6.0.4.5(1116).tar
・SuperSUのダウンロード先
UPDATE-SuperSU-v1.65.zip
・sgs3_rooting_supersu_v3.zipも必要です。ググってください。
○順番
1.CWMをOdinで焼きこみ。
2.CWMを起動し、sgs3_rooting_supersu_v3.zipをインストール。
3.続けてUPDATE-SuperSU-v1.65.zipをインストール。
4.再起動すればsuが効くようになります。
○カウントアップはCWMを焼くとKNOX WARRANTYが変化します。
他は初期ROM焼いて初期化すれば元に戻ります。
※カウントアップするとオサイフがNGになります。
※Root化されたsystem.imgのみ焼けば大丈夫かも？
KNOX WARRANTY VOID : 0x0
↓
KNOX WARRANTY VOID : 0x1
Galaxy Note 3 SCL22の内部パーティション
[email protected]:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name/
ls -l /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 1970-01-02 04:36 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 04:36 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 04:36 backup -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 04:36 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 04:36 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 04:36 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 04:36 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 04:36 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 04:36 fota -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 04:36 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 04:36 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 04:36 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 04:36 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 04:36 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 04:36 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 04:36 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 04:36 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 04:36 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 04:36 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 04:36 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 04:36 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 04:36 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 04:36 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 04:36 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 04:36 userdata -> /dev/block/mmcblk0p25
zhongkai cheng*时间：*下午7:20
,but not beeing experienced in programming , i wasn't able to aply the second set of instructions. There is a script that should be run and i do not know how to do that. Maybe someone with experience can help us.
Click to expand...
Click to collapse
Hi mvmaos, can you hsare the files that needed to root the phone? i cant seem to download the files in the chinese site, thanks in advance
---------- Post added at 06:48 PM ---------- Previous post was at 06:39 PM ----------
niranjan.anu said:
hey
anyone know a method to get unlock code for SCL22 Galaxy note 3 ?
Click to expand...
Click to collapse
Hi niranjan.anu, are you rooted already? have you tried the region unlock app? or the galaxsim unlock app? you can find that in palystore

beast08 said:
Hi mvmaos, can you hsare the files that needed to root the phone? i cant seem to download the files in the chinese site, thanks in advance
---------- Post added at 06:48 PM ---------- Previous post was at 06:39 PM ----------
Hi niranjan.anu, are you rooted already? have you tried the region unlock app? or the galaxsim unlock app? you can find that in palystore
Click to expand...
Click to collapse
Hi to you to . just google for them, they are easy to find. the two aps won't work for our phone, i tried them all, i succedeed even the script above , but it won't work. i will try these days at a samsung service, maybe they can be briebd .
the problem with our phone is that is locked in the service menu, and we can not acces that menu and our phone has gsm frequencies locked.

mvmaos said:
Hi to you to . just google for them, they are easy to find. the two aps won't work for our phone, i tried them all, i succedeed even the script above , but it won't work. i will try these days at a samsung service, maybe they can be briebd .
the problem with our phone is that is locked in the service menu, and we can not acces that menu and our phone has gsm frequencies locked.
Click to expand...
Click to collapse
too bad those two app wont work, so we have to wait until someone find a way on how to unlock our phone.

SCL22 Simunlock OK!
If you can send a SCL22 in Japan, I can do a SIM unlock.
Price : $90 + postage(Paypal)
mail : [email protected]
>>1
You are copying Root from my blog.

scl 22 unlock
Philipe9_person9 said:
If you can send a SCL22 in Japan, I can do a SIM unlock.
Price : $90 + postage(Paypal)
mail : [email protected]
>>1
You are copying Root from my blog.
Click to expand...
Click to collapse
unfortunately, sending it from Romania to Japan would cost me a bit to much, so, if there is an other way you can help me, i am listening...

Philipe9_person9 said:
If you can send a SCL22 in Japan, I can do a SIM unlock.
Price : $90 + postage(Paypal)
mail : [email protected]
>>1
You are copying Root from my blog.
Click to expand...
Click to collapse
Yep sending it to japan from srilanka is very diffcult. Can you guide us through email or skype to unlock it
Sent from my SCL22 using xda app-developers app

beast08 said:
i tried this method before, flashing the SuperSU v1.86 to my phone, but everytime im opening the app, it saying su binary need to update, abd the phone will reboot to CWM recovery, and when i checked it will Root Checker, it says the phone is not properly rooted.
Click to expand...
Click to collapse
I installed the CWM. but i can't go to the CWM recovery mode. What can be the reason ?

CWM for Samsung SM G360H Galaxy Core Prime

help my CWM for SM G360H

courier72 said:
help my CWM for SM G360H
Click to expand...
Click to collapse
attach your stock boot.img and stock recovery.img and I will try to help.

y300-0100 said:
attach your stock boot.img and stock recovery.img and i will try to help.
Click to expand...
Click to collapse
View attachment boot.img View attachment recovery.img

twrp recovery test version
try this recovery. if not working i made stock recovery flashable via odin.
sources are here for you to check out (partitions , names):
https://github.com/Y300-0100/twrp_samsung_core33gxx

recovery.tar.md5 not work CWM for Samsung SM G360H Galaxy Core Prime

hanyyyy said:
recovery.tar.md5 not work CWM for Samsung SM G360H Galaxy Core Prime
Click to expand...
Click to collapse
Its stock recovery. Just made for odin.
did you tried twrp recovery? .

Y300-0100 said:
Its stock recovery. Just made for odin.
did you tried twrp recovery? .
Click to expand...
Click to collapse
i tried twrp recovery to by Odin
not work to when i git in recovery mod its gif me boot log and never get in recovery mod at all

hanyyyy said:
recovery.tar.md5 not work CWM for Samsung SM G360H Galaxy Core Prime
Click to expand...
Click to collapse
Y300-0100
Maybe more, need other files? Can I help?

courier72 said:
Y300-0100
Maybe more, need other files? Can I help?
Click to expand...
Click to collapse
Full partition table by name and block number.
what not working little more details like black screen or stuck in splash screen etc.
logcat if possible.
"Not working " answer doesn't mean anything for me.
It's like " my blender is not working. Any solution?
:.

Y300-0100 said:
Full partition table by name and block number.
:.
Click to expand...
Click to collapse
how to do it?

Y300-0100 said:
what not working little more details like black screen or stuck in splash screen etc.
Click to expand...
Click to collapse
stuck in splash screen

courier72 said:
how to do it?
Click to expand...
Click to collapse
for my device command is this:
Code:
ls -al /dev/block/platform/sprd-sdhci.3/by-name
but for your you should check this for your device "sprd-sdhci.3"
Just check your fstab. Command is same as for G355HN
Code:
1|[email protected]:/ $ ls -al /dev/block/platform/sprd-sdhci.3/by-name
lrwxrwxrwx root root 2014-12-17 11:33 CSC -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-12-17 11:33 FIXNV1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-12-17 11:33 FIXNV2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-12-17 11:33 FOTA_SIG -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-12-17 11:33 HIDDEN -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-12-17 11:33 KERNEL -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-12-17 11:33 MODEM -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-12-17 11:33 MODEM_BACKUP -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-12-17 11:33 OTA -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-12-17 11:33 Odin_reserved -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-12-17 11:33 PARAM -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-12-17 11:33 RECOVERY -> /dev/block/mmcblk0p18lrwxrwxrwx root root 2014-12-17 11:33 RUNTIMENV1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-12-17 11:33 RUNTIMENV2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-12-17 11:33 SBL1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-12-17 11:33 SBL2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-12-17 11:33 WDSP -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-12-17 11:33 WDSP_BACKUP -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-12-17 11:33 efs -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-12-17 11:33 fixnv1 -> /dev/block/platform/sprd-sdhci.3/by-name/FIXNV2
lrwxrwxrwx root root 2014-12-17 11:33 fixnv2 -> /dev/block/platform/sprd-sdhci.3/by-name/FIXNV1
lrwxrwxrwx root root 2014-12-17 11:33 prodnv -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-12-17 11:33 runtimenv1 -> /dev/block/platform/sprd-sdhci.3/by-name/RUNTIMENV1
lrwxrwxrwx root root 2014-12-17 11:33 runtimenv2 -> /dev/block/platform/sprd-sdhci.3/by-name/RUNTIMENV2
lrwxrwxrwx root root 2014-12-17 11:33 system -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-12-17 11:33 userdata -> /dev/block/mmcblk0p22

Y300-0100 said:
Just check your fstab. Command is same as for G355HN
Click to expand...
Click to collapse
Is not entirely clear. To do this, you need a computer and Linux?

courier72 said:
Is not entirely clear. To do this, you need a computer and Linux?
Click to expand...
Click to collapse
Just install android terminal.( from play store ) Command work's with non roted phones also .
and you shoud get this:
.

Y300-0100 said:
Just install android terminal.
Click to expand...
Click to collapse
But I do not understand what to do next

courier72 said:
But I do not understand what to do next
Click to expand...
Click to collapse
Oopen terminal, type command from above and hit enter...

k/platform/sprd-sdhci.3/by-name <
lrwxrwxrwx root root 2015-03-02 22:43 CSC -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-03-02 22:43 FOTA_SIG -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-03-02 22:43 HIDDEN -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-03-02 22:43 KERNEL -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-03-02 22:43 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-03-02 22:43 MODEM2 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-03-02 22:43 PARAM -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-03-02 22:43 RECOVERY -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-03-02 22:43 RESERVED2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-03-02 22:43 SBOOT -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-03-02 22:43 SBOOT2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-03-02 22:43 TDDSP -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-03-02 22:43 WDSP -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-03-02 22:43 efs -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-03-02 22:43 prodnv -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-03-02 22:43 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-03-02 22:43 tdfixnv1 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-03-02 22:43 tdfixnv2 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-03-02 22:43 tdruntimenv1 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-03-02 22:43 tdruntimenv2 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-03-02 22:43 userdata -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2015-03-02 22:43 wfixnv1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-03-02 22:43 wfixnv2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-03-02 22:43 wruntimenv1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-03-02 22:43 wruntimenv2 -> /dev/block/mmcblk0p13
[email protected]:/ $

Y300-0100 said:
Full partition table by name and block number.
what not working little more details like black screen or stuck in splash screen etc.
logcat if possible.
"Not working " answer doesn't mean anything for me.
It's like " my blender is not working. Any solution?
:.
Click to expand...
Click to collapse
stuck in splash screen
and this is the Full partition table by name and block number
ਊock/platform/sprd-sdhci.3/by-name <
lrwxrwxrwx root root 2015-03-02 21:27 CSC -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-03-02 21:27 FOTA_SIG -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-03-02 21:27 HIDDEN -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-03-02 21:27 KERNEL -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-03-02 21:27 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-03-02 21:27 MODEM2 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-03-02 21:27 PARAM -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-03-02 21:27 RECOVERY -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-03-02 21:27 RESERVED2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-03-02 21:27 SBOOT -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-03-02 21:27 SBOOT2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-03-02 21:27 TDDSP -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-03-02 21:27 WDSP -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-03-02 21:27 efs -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-03-02 21:27 prodnv -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-03-02 21:27 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-03-02 21:27 tdfixnv1 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-03-02 21:27 tdfixnv2 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-03-02 21:27 tdruntimenv1 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-03-02 21:27 tdruntimenv2 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-03-02 21:27 userdata -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2015-03-02 21:27 wfixnv1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-03-02 21:27 wfixnv2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-03-02 21:27 wruntimenv1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-03-02 21:27 wruntimenv2 -> /dev/block/mmcblk0p13
[email protected]:/ $
�

Cwm for samsung galaxy core prime
Any one can plz make cwm for core prime

twrp recovery test version
Changes I made :
https://github.com/Y300-0100/twrp_samsung_core33gxx/commit/8dde6d106ef5abf6ea52203d13091cb1b11480be
I will upload test build later

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.

[SHV-E330S] dd recovery.img to wrong partition

I have a Korean Galaxy S4, model number SHV-E330S. Copied the TWRP recovery.img to /dev/block/mmcblk0p10 but it turned out that 0p10 is the "param" partition, so now the phone cannot connect to cellular network, it shows the circle icon with strike-through. The phone still shows the correct IMEI number when dialing *#06#, and it can connect to wifi networks. Also can boot into recovery mode and wiping the system does not help.
Is there any way to make my phone work?
A bit more context of what I did:
Tried to install cyanogenmod on the phone, but it failed with "Signature verification failed". I thought it is because the stock recovery does not allow to install 3rd party roms.
So I tried to install CWM/TWRP recovery on it using ODIN3 when the phone was in download mode. It did not work, could not boot into CWM, it always started the stock recovery. I saw in the install guides that I can copy the recovery image to the phone with dd if I have root.
So I rooted it with this. It worked. Then I followed the instructions here (came from this site) and executed dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p10
This website did not talk about creating a backup of that partition first, so I did not do that. The cellular network probably stopped working at this point, but I only noticed it later.
The partitions on my phone:
[email protected]:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-01-02 00:00 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 00:00 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 00:00 backup -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 00:00 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 00:00 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 00:00 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 00:00 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 00:00 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 00:00 fota -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 00:00 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 00:00 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 00:00 hidden -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-02 00:00 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 00:00 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 00:00 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 00:00 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 00:00 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 00:00 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 00:00 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 00:00 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 00:00 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 00:00 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 00:00 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 00:00 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 00:00 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 00:00 userdata -> /dev/block/mmcblk0p26
[email protected]:/ #
Would it work if I copy the /dev/block/mmcblk0p10 partition from an other phone? What is on the param partition?

sullerandras said:
I have a Korean Galaxy S4, model number SHV-E330S. Copied the TWRP recovery.img to /dev/block/mmcblk0p10 but it turned out that 0p10 is the "param" partition, so now the phone cannot connect to cellular network, it shows the circle icon with strike-through. The phone still shows the correct IMEI number when dialing *#06#, and it can connect to wifi networks. Also can boot into recovery mode and wiping the system does not help.
Is there any way to make my phone work?
A bit more context of what I did:
Tried to install cyanogenmod on the phone, but it failed with "Signature verification failed". I thought it is because the stock recovery does not allow to install 3rd party roms.
So I tried to install CWM/TWRP recovery on it using ODIN3 when the phone was in download mode. It did not work, could not boot into CWM, it always started the stock recovery. I saw in the install guides that I can copy the recovery image to the phone with dd if I have root.
So I rooted it with this. It worked. Then I followed the instructions here (came from this site) and executed dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p10
This website did not talk about creating a backup of that partition first, so I did not do that. The cellular network probably stopped working at this point, but I only noticed it later.
The partitions on my phone:
[email protected]:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-01-02 00:00 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-02 00:00 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-02 00:00 backup -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-02 00:00 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-02 00:00 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-02 00:00 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-02 00:00 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-02 00:00 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-02 00:00 fota -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-02 00:00 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-02 00:00 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-02 00:00 hidden -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-02 00:00 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-02 00:00 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-02 00:00 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-02 00:00 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-02 00:00 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-02 00:00 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-02 00:00 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-02 00:00 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-02 00:00 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-02 00:00 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-02 00:00 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-02 00:00 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-02 00:00 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-02 00:00 userdata -> /dev/block/mmcblk0p26
[email protected]:/ #
Would it work if I copy the /dev/block/mmcblk0p10 partition from an other phone? What is on the param partition?
Click to expand...
Click to collapse
If you're rooted you can use the app Flashify to flash the recovery.img. I recommend TWRP though.

GDReaper said:
If you're rooted you can use the app Flashify to flash the recovery.img. I recommend TWRP though.
Click to expand...
Click to collapse
Thanks. But it is too late for that, isn't it? The phone is kind of bricked, and flashing a TWRP recovery will not magically unbrick it, right?

sullerandras said:
Thanks. But it is too late for that, isn't it? The phone is kind of bricked, and flashing a TWRP recovery will not magically unbrick it, right?
Click to expand...
Click to collapse
How is it bricked?
From what I understood, you don't have signal anymore, but other than that the phone works.
But you are right, flashing a recovery won't make your signal come back, but maybe flashing a modem will.
The param partition is setting where the boot images are stored, from what I've taken in other threads.

GDReaper said:
How is it bricked?
From what I understood, you don't have signal anymore, but other than that the phone works.
But you are right, flashing a recovery won't make your signal come back, but maybe flashing a modem will.
The param partition is setting where the boot images are stored, from what I've taken in other threads.
Click to expand...
Click to collapse
As I described in the first message in the thread, I accidentally overwrote the mmcblk0p10 partition which is the "param" partition. Since that the phone cannot connect to cellular network, so cannot make phone calls, cannot receive sms and cannot connect to LTE.
But it shows the correct "IMEI" and the correct "Baseband version" in Settings / About device. It can also connect to wifi network, so I can install/update apps and play games.
I downloaded the stock ROM from samsung-update.com: SKT-E330SKSUCNJ1-20141015090913.zip. It is 1.7GB and it took almost 24 hours to download.
I installed this ROM on the phone with ODIN but it did not help. So the problem is probably not with the "modem" partition since it was overwritten by the stock rom.
And found some details about the param partition here:
PARAM: This is the Parameter partition which contains a number of parameters,
variables and settings of the hardware. Apparently it has an 88 byte header
structure that tell us if the MODEMST1 and MODEMST2 have been backed up to the
FSG and BACKUP partitions, respectively. Furthermore it contain all the debug
settings (DLOW/DMID/DHIG etc), the "triangle" status of whether or not you have
flashed custom ROMs and the flash count (0x3FFE00). Current boot mode in use,
and much more. The info about this partition could easily occupy a book by
itself.
Click to expand...
Click to collapse

sullerandras said:
As I described in the first message in the thread, I accidentally overwrote the mmcblk0p10 partition which is the "param" partition. Since that the phone cannot connect to cellular network, so cannot make phone calls, cannot receive sms and cannot connect to LTE.
But it shows the correct "IMEI" and the correct "Baseband version" in Settings / About device. It can also connect to wifi network, so I can install/update apps and play games.
I downloaded the stock ROM from samsung-update.com: SKT-E330SKSUCNJ1-20141015090913.zip. It is 1.7GB and it took almost 24 hours to download.
I installed this ROM on the phone with ODIN but it did not help. So the problem is probably not with the "modem" partition since it was overwritten by the stock rom.
And found some details about the param partition here:
Click to expand...
Click to collapse
Try using a PIT file.

GDReaper said:
Try using a PIT file.
Click to expand...
Click to collapse
It turns out the phone is working, but the reception is bad: if I go to a better location then it works, I'm able to make and receive calls.
So the problem is not with the software. Maybe the antenna is spoiled? I suspect that because pulling the antenna out does not improve the signal level.

sullerandras said:
It turns out the phone is working, but the reception is bad: if I go to a better location then it works, I'm able to make and receive calls.
So the problem is not with the software. Maybe the antenna is spoiled? I suspect that because pulling the antenna out does not improve the signal level.
Click to expand...
Click to collapse
I would try and change the modem.
Otherwise try fixing the antenna if the modem doesn't change anything.

GDReaper said:
I would try and change the modem.
Otherwise try fixing the antenna if the modem doesn't change anything.
Click to expand...
Click to collapse
What do you mean "change the modem"?
I guess the modem's firmware was updated because after I reinstalled the original OS the phone updated itself OTA to the latest 5.0.1 android, and now it shows a different Baseband number than before.
Do you think this could still be a software issue?

sullerandras said:
What do you mean "change the modem"?
I guess the modem's firmware was updated because after I reinstalled the original OS the phone updated itself OTA to the latest 5.0.1 android, and now it shows a different Baseband number than before.
Do you think this could still be a software issue?
Click to expand...
Click to collapse
People say Modems can change reception. Although I never saw any changes myself.