Database Develop

[DEV] NEXUS 4 MOUNT POINTS

/dev/block/platform/msm_sdcc.1/by-name:
lrwxrwxrwx root root 2012-11-13 19:02 DDR -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2012-11-13 19:02 aboot -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-11-13 19:02 abootb -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2012-11-13 19:02 boot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2012-11-13 19:02 cache -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2012-11-13 19:02 grow -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2012-11-13 19:02 m9kefs1 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-11-13 19:02 m9kefs2 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-11-13 19:02 m9kefs3 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-11-13 19:02 metadata -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2012-11-13 19:02 misc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2012-11-13 19:02 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-11-13 19:02 persist -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2012-11-13 19:02 recovery -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-11-13 19:02 rpm -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-11-13 19:02 rpmb -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2012-11-13 19:02 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-11-13 19:02 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-11-13 19:02 sbl2b -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-11-13 19:02 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-11-13 19:02 sbl3b -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2012-11-13 19:02 system -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2012-11-13 19:02 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-11-13 19:02 tzb -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2012-11-13 19:02 userdata -> /dev/block/mmcblk0p23
Also provided by c900712 is the Voodoo Report file for the Nexus 4 it may be interesting reading for some people.
EDIT:
Originally posted by Houstonn in post#28
Code:
LG Nexus 4 Mako - LGE960 JVP15Q
Number Start (sector) End (sector) Size Code Name
1 1024 132095 64.0 MiB 0700 modem
2 132096 133119 512.0 KiB FFFF sbl1
3 133120 134143 512.0 KiB FFFF sbl2
4 134144 138239 2.0 MiB FFFF sbl3
5 138240 139263 512.0 KiB FFFF tz
6 139264 184319 22.0 MiB FFFF boot
7 184320 229375 22.0 MiB FFFF recovery
8 229376 230935 780.0 KiB FFFF m9kefs1
9 230936 232495 780.0 KiB FFFF m9kefs2
10 232496 234055 780.0 KiB FFFF m9kefs3
11 234496 235519 512.0 KiB FFFF rpm
12 235520 236543 512.0 KiB FFFF aboot
13 236544 237567 512.0 KiB FFFF sbl2b
14 237568 241663 2.0 MiB FFFF sbl3b
15 241664 242687 512.0 KiB FFFF abootb
16 242688 243711 512.0 KiB FFFF rpmb
17 243712 244735 512.0 KiB FFFF tzb
18 244736 245759 512.0 KiB 8301 metadata
19 245760 278527 16.0 MiB FFFF misc
20 278528 311295 16.0 MiB 8300 persist
21 311296 2031615 840.0 MiB 8300 system
22 2031616 3178495 560.0 MiB 8300 cache
23 3178496 15267839 5.8 GiB 8300 userdata
24 15267840 15268863 512.0 KiB FFFF DDR
25 15268864 15269854 495.5 KiB 8300 grow
Mark.

check ur email
Sent from my Nexus 4 using xda premium

c900712 said:
check ur email
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thank you thats everything I needed.
Mark.

That's really helpful, thank you! And I am interest to know how to get mount point from a new device? Thanks again.
Sent from my DROID2 GLOBAL using xda app-developers app

Anyone fancy being nice and making a file to use with dsixda's kitchen? Wanna play about with stock ROM build before I get my N4

EddyOS said:
Anyone fancy being nice and making a file to use with dsixda's kitchen? Wanna play about with stock ROM build before I get my N4
Click to expand...
Click to collapse
Just extract system img and then you must make a file for mako to make kitchen work (maybe)
Sent from my HTC Explorer A310e using xda app-developers app

All that's the easy part, it's getting the right mount points so it'll flash correctly. Comparing the OP to existing device files doesn't mean a lot to me unfortunately! Here's the edify_defs file for the Galaxy Nexus if someone wants to help out?
# Samsung Galaxy Nexus (GSM/HSPA+)
change_mnt=yes
param1=ext4
param2=HSMMC
sys_mnt=\/dev\/block\/platform\/omap\/omap_hsmmc.0\/by-name\/system
cache_mnt=\/dev\/block\/platform\/omap\/omap_hsmmc.0\/by-name\/cache
boot_mnt=\/dev\/block\/platform\/omap\/omap_hsmmc.0\/by-name\/boot
data_mnt=\/dev\/block\/platform\/omap\/omap_hsmmc.0\/by-name\/userdata
sdcard_mnt=???
fix_boot3=yes

zyy757 said:
That's really helpful, thank you! And I am interest to know how to get mount point from a new device? Thanks again.
Sent from my DROID2 GLOBAL using xda app-developers app
Click to expand...
Click to collapse
Just download Voodoo Report from the Market and save the output to your usb storage. It will save a zip file to your Internal Storage that has all the info you need.
Mark.

Also got the issue of not being able to deodex the ROM using the kitchen as it's not supporting SDK17 yet...d'oh!

Any ETA for your tool kit please?

vinnyutd6899 said:
Any ETA for your tool kit please?
Click to expand...
Click to collapse
Im working on it right now and have everything set up im just going through all the procedures and adding the FAQ section in the Toolkit.
I will need 1 or 2 testers to make sure the insecure boot image works properly and the nand backup and 1-click works as I dont have a device to test on. As like many others I waited up to order it on the Play Store but had to take my son to school and when I got back it had sold out
Any testers available tonight?
Mark.

mskip said:
Im working on it right now and have everything set up im just going through all the procedures and adding the FAQ section in the Toolkit.
I will need 1 or 2 testers to make sure the insecure boot image works properly and the nand backup and 1-click works as I dont have a device to test on. As like many others I waited up to order it on the Play Store but had to take my son to school and when I got back it had sold out
Any testers available tonight?
Mark.
Click to expand...
Click to collapse
I can test if you want. Just send me an email when you would like to.

mskip said:
Im working on it right now and have everything set up im just going through all the procedures and adding the FAQ section in the Toolkit.
I will need 1 or 2 testers to make sure the insecure boot image works properly and the nand backup and 1-click works as I dont have a device to test on. As like many others I waited up to order it on the Play Store but had to take my son to school and when I got back it had sold out
Any testers available tonight?
Mark.
Click to expand...
Click to collapse
i will test it

Can someone who has fastboot drivers set up please try BOOTING (not flashing) this insecure boot image to see if it boots into Android. If it gets stuck just long press the power button the reboot normally.
Mark.

mskip said:
Can someone who has fastboot drivers set up please try BOOTING (not flashing) this insecure boot image to see if it boots into Android. If it gets stuck just long press the power button the reboot normally.
Mark.
Click to expand...
Click to collapse
Yeah thats worked for me

[vertigo] said:
Yeah thats worked for me
Click to expand...
Click to collapse
+1
Gesendet von meinem Nexus 4 mit Tapatalk 2

[vertigo] said:
Yeah thats worked for me
Click to expand...
Click to collapse
P0MM3S said:
+1
Gesendet von meinem Nexus 4 mit Tapatalk 2
Click to expand...
Click to collapse
Thank you very much I can finish building the toolkit now. I will post when its ready for testing and see who is available. The initial version will have custom recovery operations blocked as it isnt available yet but it shouldnt be long before a working recovery is built.
Mark.

I'm up for testing mskip, also any insight as to why these insecure boot images aren't booting after being flashed yet?
Sent from my Nexus 4 using Tapatalk 2

Kstarz said:
I'm up for testing mskip, also any insight as to why these insecure boot images aren't booting after being flashed yet?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Which insecure boot images arent booting? They dont need to be flashed, just booted to boot the phone and give adb root access.
The one I made and posted a few posts back has been reported to work fine.
Mark.

mskip said:
Which insecure boot images arent booting? They dont need to be flashed, just booted to boot the phone and give adb root access.
The one I made and posted a few posts back has been reported to work fine.
Mark.
Click to expand...
Click to collapse
Yes booting it works fine but flashing it doesn't and I am unsure why it doesn't.
Sent from my Nexus 4 using Tapatalk 2

[INFO] SPH-L720 Hidden Dialer Codes, AT Commands, Partition List and AOSP Diag Mode

One of my standard threads with codes and info. I will add onto this as I find more.
Dialer Codes
Code:
##25327# - nothing?
##2539# - nothing?
##3282# - DATA
##33284# - DEBUG (Password: 777468 / SPRINT)
##3424# - DIAG
##367738# - DNSSET
##4772579# - GPSCLRX
##72786# - SCRTN
##786# - RTN
##889# - TTY
*#0011# - Service Mode
*#7284#
**7838 - nothing?
**583 - nothing?
Stole some codes from [B][URL="http://forum.xda-developers.com/member.php?u=2698939"]thekingofmean[/URL][/B]'s thread [URL="http://forum.xda-developers.com/showthread.php?t=2261538"]here[/URL]. Thank you!
*#0*# General Test Mode
*#0228# Battery status
*#06# IMEI
*#1234# Check HW/SW Info, PDA, CSC, MODEM (F/W Ver)
*#12580*369# SW & HW Info
*#2663# TSP / TSK firmware update
*#34971539# Camera Firmware Update
*#7353# Quick Test Menu
*#9900# Sys Dump Menu
*#9090# Diag Config
AT Commands
See here for AT command info from E:V:A
Code:
AT+SYSSLEEP
AT+VERSNAME
AT+MAXPOWER
AT+TEMPTEST
AT+SIMDETEC
AT+PRODCODE
AT+CALIDATE
AT+BANSELCT
AT+SECNRSSI
AT+READRSSI
AT+CALLCONN
AT+SCMMONIT
AT+TESTMODE
AT+GPSSTEST
AT+MSLSECUR
AT+IMEITEST
AT+AKSEEDNO
AT+LIFETIME
AT+IMEICERT
AT+LVOFLOCK
AT+DETALOCK
AT+LOCKREAD
AT+CFUN
AT+MEIDAUTH
AT+CHNSELCT
AT+AOTKEYWR
AT+FACTORST
AT+BAKUPCHK
AT+FAILDUMP
AT+NAMCHECK
AT+PRLVERIF
AT+RECONDIT
AT+KSTRINGB
AT+SVCBANDB
AT+LOCKINFO
AT+EFSSYNCC
AT+$QCSIMSTAT
AT+$QCPBMPREF
AT+$CREG
AT+$CCLK
AT+$QCCNMI
AT+*CNTI
AT+$QCCLR
AT+$QCDMR
AT+$QCDNSP
AT+$QCDNSS
AT+$QCTER
AT+$QCSLOT
AT+$QCSIMAPP
AT+$QCPINSTAT
AT+$QCPDPP
AT+$QCPDPLT
AT+$QCPWRDN
AT+$QCDGEN
AT+$QCPDPCFGE
AT+$BREW
AT+$QCANTE
AT+$QCRPW
AT+$QCSQ
AT+$CSQ
AT+$QCSYSMODE
AT+$QCCTM
AT+$QCBANDPREF
AT+^PREFMODE
AT+^SYSINFO
AT+^SYSCONFIG
AT+^CARDMODE
AT+^DSCI
AT+$QCVOLT
AT+$QCHWREV
AT+$QCBOOTVER
AT+$ECALL
AT+$QCDEFPROF
AT+$QCMRUE
AT+$QCMRUC
AT+$QCAPNE
AT+$QCPDPIMSCFGE
AT+$QCCLAC
AT+^SPN
AT+$QCRMCALL
AT+$QCDRX
AT+$MDN
AT+$MSID
AT+$MIPERR
AT+$1XRXPWR
AT+$1XECIO
AT+$DORXPWR
AT+$DOSINR
AT+$DEBUG
AT+$ERI
AT+FCLASS
AT+ICF
AT+IFC
AT+IPR
AT+GMI
AT+GMM
AT+GMR
AT+GCAP
AT+GSN
AT+CMEE
AT+WS46
AT+PACSP
AT+CLCC
Partition List
Thanks to balistic2 for providing this.
Code:
[email protected]:/ # ls -al /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root backup -> /dev/block/mmcblk0p23
lrwxrwxrwx root boot -> /dev/block/mmcblk0p20
lrwxrwxrwx root cache -> /dev/block/mmcblk0p18
lrwxrwxrwx root carrier -> /dev/block/mmcblk0p28
lrwxrwxrwx root efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root fota -> /dev/block/mmcblk0p22
lrwxrwxrwx root fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root hidden -> /dev/block/mmcblk0p27
lrwxrwxrwx root m9kefs1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root m9kefs2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root m9kefs3 -> /dev/block/mmcblk0p15
lrwxrwxrwx root mdm -> /dev/block/mmcblk0p2
lrwxrwxrwx root modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root param -> /dev/block/mmcblk0p19
lrwxrwxrwx root persdata -> /dev/block/mmcblk0p26
lrwxrwxrwx root persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root ssd -> /dev/block/mmcblk0p25
lrwxrwxrwx root system -> /dev/block/mmcblk0p16
lrwxrwxrwx root tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root userdata -> /dev/block/mmcblk0p29
AOSP Diag Mode
Make script or run in Script Manager. See here for more diag mode info.
Code:
#/system/bin/sh
#reboot phone to disable
#enables diag mode
echo "0" /sys/class/android_usb/android0/enable
echo "04E8" /sys/class/android_usb/android0/idVendor
echo "685D" /sys/class/android_usb/android0/idProduct
echo "diag,diag_mdm" /sys/class/android_usb/android0/f_diag/clients
echo "hsic" /sys/class/android_usb/android0/f_acm/acm_transports
echo "diag,acm,adb" /sys/class/android_usb/android0/functions
echo "1" /sys/module/ci13xxx_msm/parameters/streaming
echo "1" /sys/class/android_usb/android0/enable

autoprime said:
*#0011# - Service Mode
​
Click to expand...
Click to collapse
Mine says No Service. I hit Menu button. Wifi is the only thing that really gives me any options. There is a Wifi Power Save toggle switch for On or Off. What does this do?

jpkelly05 said:
Mine says No Service. I hit Menu button. Wifi is the only thing that really gives me any options. There is a Wifi Power Save toggle switch for On or Off. What does this do?
Click to expand...
Click to collapse
unfortunately i dont have this device yet so I can't say exactly what everything does. I'm just sifting thru dumps and roms to find fun stuff.
on a different note... I've updated the OP to include a script to enable diag mode on the GS4. Diag mode can be used to write new PRLs to your device while on an AOSP rom(using DFS or QPST etc)... or diag mode can be used for other fun things... but if you don't know what it does then you probably don't need it

whats the test screen? ##0#?? does anyone kno it? NEVERMIND!! i found it.. *#0*#

what are all the commands aosp roms will take?

Been trying to work on learning AT commands and found some in the modem.bin of the NAE tarball like AT+MSLSECUR and AT+SIMDETEC however NONE of the commands in this list do anything. I've tried a ? after the command and a =? after the command, still errors out. I'm connected to the modem port (not the port used for flashing phones but for sending AT commands). I think this port is labeled /dev/ttyUSB0. I've tried downgrading to MDC baseband. Still nothing. How the heck am I supposed to send these other AT commands to the phone?

@ecs87 The AT commands shown on top of this thread are not correct, because:
1) they are device dependent
2) they are service provider dependent
3) they are mixed "fake" AT commands, as interpreted by RIL daemon, and "real" Modem AT commands, as we like.
I have several posts and threads on this subject, please search. In addition, AT port may not be accessible if
already used by RIL daemon in some cases.

I figured it out EVA. Apparently you MUST be using a UART cable. I think it's just the regular USB cable with a resistor on a line. I didn't do too much research on it because I was able to simulate the same thing using a GSM service box and a c3300k cable then accessing the box port using a terminal type application. I was then able to use the "exteneded" set of AT commands I found in modem.bin. The AT+AKSEEDNO does have me stumped though. Well...I guess the AT+MSLSECUR does as well. I'm able to get an output, but it must be calculated and returned. I was able to logcat the default MSLSECUR password for the G900P but I wasn't sure how it was calculated. Same goes for the AKSEEDNO. And considering how the AKSEEDNO changes every time you call for it, logging does nothing to help.
Sent from my SPH-L720 using XDA Free mobile app
My original thread for this is http://forum.gsmhosting.com/vbb/f83/note-3-imei-writing-questions-1828950/ Keep in mind I'm not trying to CHANGE the IMEI, but rather write the original one WITHOUT a box or EFS backup (I like to tinker...what can I say?). I got all the way down to the AKSEEDNO...then I hit a brick wall lol. Makes sense considering that's the absolute last step before I get to send the AT command to write the IMEI and sign the IMEI with a certificate.

Unable to access diag mode in AOSP
I've got a Galaxy S4 on SlimKat 4.4.4.
I've saved the script for AOSP diag mode in Script Manager, and ran it. I also tried running it over an ADB shell. Neither reports errors, but nothing ever changes. The phone remains the same. I've tried unplugging/replugging USB cable to no avail. The phone never shows as a different device in device manager. Are there any known reasons for this not working?

[Q] au SCL22

I currently having a au (Japan) SCL22 which is a au kddi branded Galaxy Note 3. I'm wondering if anyone knows how to root it?

ken0ryu said:
I currently having a au (Japan) SCL22 which is a au kddi branded Galaxy Note 3. I'm wondering if anyone knows how to root it?
Click to expand...
Click to collapse
I suppose unless somebody gets the official firmware to people who know how to root devices here, we won't see one. =) Someone is on the Docomo version already. I am sure it will be rooted, just a bit later. Until then, I will keep wondering why I will have to void my warranty in order to have access to what Note 3 can already do - unrestricted multi-tasking with multi windows and s pen window...

Snakiest said:
I suppose unless somebody gets the official firmware to people who know how to root devices here, we won't see one. =) Someone is on the Docomo version already. I am sure it will be rooted, just a bit later. Until then, I will keep wondering why I will have to void my warranty in order to have access to what Note 3 can already do - unrestricted multi-tasking with multi windows and s pen window...
Click to expand...
Click to collapse
This phone can't root now.

doantri said:
This phone can't root now.
Click to expand...
Click to collapse
Well, that is what I said. I remember it took about 6 months for the AU version of the Galazy S2 to get rooted, so I expect something like this with Note 3.

This is ridiculousness! I had a desire HD on Softbank and could run any desire HD rom on it I wanted. Now I switch to au to find this is not the case huh? Why can't we use sprint or Verizon roms/recoveries?

You ever figure anything out? This is killing me. Custom rom seems like is never going to happen
ken0ryu said:
I currently having a au (Japan) SCL22 which is a au kddi branded Galaxy Note 3. I'm wondering if anyone knows how to root it?
Click to expand...
Click to collapse

rooted note scl22
dan.kels.r said:
You ever figure anything out? This is killing me. Custom rom seems like is never going to happen
Click to expand...
Click to collapse
thanks for replay but some one rooted done

how to root Galaxy note 3 SCL22
hi
i also want to know same thing, how to root Galaxy note 3 SCL22
anyone know pls help us

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.

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
You may have rooted, but you also blew your KNOX fuse and now your warranty is voided. KNOX WARRANTY VOID : 0x1 this line tells you that the KNOX has been tripped. This is impossible to reset so if you ever have to send your phone in for repairs now you will not be able to make a warranty claim. This is what haapens when you get impatient and try things that have not been proven like KINGOROOT.

need help
Solarenemy68 said:
You may have rooted, but you also blew your KNOX fuse and now your warranty is voided. KNOX WARRANTY VOID : 0x1 this line tells you that the KNOX has been tripped. This is impossible to reset so if you ever have to send your phone in for repairs now you will not be able to make a warranty claim. This is what haapens when you get impatient and try things that have not been proven like KINGOROOT.
Click to expand...
Click to collapse
i do not care about the knox.
mi problem is that i can not use a european sim for gsm , hence the need to unlock the phone. so if you can help with that script, please do.
i saw on youtube someone in vietnam, that unlocked a japanesse version of note 3, and offers his service for money, but only if you can go with the phone to him..., so... it can be done.

mvmaos said:
i do not care about the knox.
mi problem is that i can not use a european sim for gsm , hence the need to unlock the phone. so if you can help with that script, please do.
i saw on youtube someone in vietnam, that unlocked a japanesse version of note 3, and offers his service for money, but only if you can go with the phone to him..., so... it can be done.
Click to expand...
Click to collapse
can you provide me that vietnam video link pls. If you have any additional details about unlocking SCL22 pls share with us. I will do
the same. Because i want to unlock my Note 3 SCL22 immediately.

need help
niranjan.anu said:
can you provide me that vietnam video link pls. If you have any additional details about unlocking SCL22 pls share with us. I will do
the same. Because i want to unlock my Note 3 SCL22 immediately. [/QUOTE
watch?v=7E12QTQv3Io just check that id on youtube or search for "unlock scl22"
Click to expand...
Click to collapse

mvmaos said:
niranjan.anu said:
can you provide me that vietnam video link pls. If you have any additional details about unlocking SCL22 pls share with us. I will do
the same. Because i want to unlock my Note 3 SCL22 immediately. [/QUOTE
watch?v=7E12QTQv3Io just check that id on youtube or search for "unlock scl22"
Click to expand...
Click to collapse
I send a message to this person. He replied as
"I can unlock SCL22 but i cant to do it by network. sorry"
Click to expand...
Click to collapse

scl 22 unlock
niranjan.anu said:
mvmaos said:
I send a message to this person. He replied as
"I can unlock SCL22 but i cant to do it by network. sorry"
Click to expand...
Click to collapse
did you try to ask him, at least how it can be done,or, like , what tool or software he's using ?
Click to expand...
Click to collapse

Hm, that root should be fine in a year when the warranty ends unless some smart fellow comes up with a better way to do it. As for the SIM-unlock, I hear it is possible to ask either the carrier or the phone maker for the unlock key (or whatever it is). I believe some companies even do that officially for a fee. You guys should contact AU and then Samsung support for that, really, especially if you are Japanese - should be a lot easier than for some of us here. And then report here to let everybody know.

I have another AU phone, Xperia Acro. Long time ago, I also was looking for a way to unlock it, to use with European SiM. That was hard to find. After long search, I found a company which did it for about 50 bucks. But, at the end, I could only use my phone to do phone calls, but no SMS. Tried different ways - but SMS didn't work. Fund similar complaints about SMS on my AU model online, so its a real issue. And using phone without SMS in Europe sucks.
Got another phone for Europe, after all.
AU have something weird about their frequency so that might be that SCL22 will not be able to handle SMS either, even unlocked. Think if you really need to unock it

How To Root Samsung Galaxy Note 3
How To Root Samsung Galaxy Note 3 SCL22 au by KDDI (JAPAN phone) 100% working.
Quote:
My phone details (Tested devise)
Samsung Galaxy Note 3 SCL22 AU by KDDI (JAPAN phone) SM-N900J
Android Version - 4.4.2
Baseband Version - SCL22KDU2FNF7
Kernel Version - 3.4.0-1990145
This is all the stuff you need to Root your phone -
01. Kies3Setup.exe
02. ODIN 3.07 (Do Not Use 3.09)
03. UPDATE-SuperSU-v2.35.zip
04. hltedcm-KK-KBC-CWM-v6.0.5.0_r0-recovery.tar
05. CWMrecovery-scl22kk.tar
06. Stock firmware - (for that you need to register and download the stock kernel from sammobile. you better download it just in case )
DOWNLOAD LINKS -
01.hltedcm-KK-KBC-CWM-v6.0.5.0_r0-recovery.tar - https://mega.co.nz/#!1FI3xICS!7Un6z5...8GUZMkxkAwa7n4
02.02.CWMrecovery-scl22kk.tar - https://mega.co.nz/#!FZoEAbxC!j_l24G...3Vl63DHMSThuwE
03.twrp.tar - https://mega.co.nz/#!wd5Ama5b!33WccV...a6F0uHlBf_CVRE
04.SuperSU.rar - https://mega.co.nz/#!xY5CBJ4Y!NCN_DL...7l0b5P7UmaesyA
Quote:
(This file comes with a RAR format so extract it and inside that folder you can see UPDATE-SuperSU-v2.35.zip file )
05.Odin307.zip - https://mega.co.nz/#!Bd5x0CzC!UavXZ3...nWex3ECZ_mH8LI
01.Connect your phone to PC and copy and paste UPDATE-SuperSU-v2.35.zip to phone SD card
02.Start Odin 3.07
03.Put your phone to Download mode
04.Flash the hltedcm-KK-KBC-CWM-v6.0.5.0_r0-recovery.tar
05.Flash the CWMrecovery-scl22kk.tar
06.Start your phone then put it to Recovery mode and install UPDATE-SuperSU-v2.35.zip
07.Start your phone in normal mode. And now you all set and ROOT.
FINISH.!
Enjoy your rooted phone.!

ken0ryu said:
I currently having a au (Japan) SCL22 which is a au kddi branded Galaxy Note 3. I'm wondering if anyone knows how to root it?
Click to expand...
Click to collapse
Read this - http://forum.xda-developers.com/galaxy-note-3/general/samsung-galaxy-note-3-scl22-au-kddi-t2964801

*MODS* Just you you ;) [R&D] Samsung Snapdragon 800 harmonizing

Dear Moderators!
Since I had top stop being active in the development the threads that I started with having a master directory and thus that are left here has become totally stale since they have not been updated in a long time nor do I have current plans to continue.
I don't track this forum and the wonders done with this phone but this post has some real potential danger.
The post is outdated and the information in it could therefore be wrong, faulty or even harmful. And I see it mostly harmful in my point of view, since this was the baby steps taken a long time ago.
Looking at the contents it compares several parts of partition tables and even brave (and foolish) tries of me testing philz recoveries. Now Philz has put some safety code since the Note II/S3 melds but for a less experienced user that look at the names.
"hlte and jflte", sound pretty close that we know is not the case but they reeeely want so badly into the "world" of S4 they could try to alter the partition tables, that we serve them on a platter and that there are easy utils for, to TRY make it look like the "real" S4 and really hard brick the phone, or even worse try TWRP of the hlfe "since it was so long time ago" and look at their screen melting away.
Proper scientific rules dictates that if any information is unknown and therefore in a volatile state it should fall under the principle of caution until verified of its validity and safety. I have no insight into that validly and the current development but I highly doubt this post is needed any longer and since this is accessible to the public the "not doing any harm" comes into place and thus this thread should be deleted since if anything useful came out of it it has already been taken into current development and it can cause harm. A lock will not suffice.
Since I know that many posts are not considered being "device specific enough" (like a discussion about lowering the voltage of the kernel) or "cluttering" (explaining the booting process of a kernel works) this post should absolutely fall under some of those rules (or some other that I've yet not encountered) and I strongly think a deletion of this would be more proper then just moving it to the trashcan "General"?
So at least I try to make you see that this post should not be in the trashcan but deleted for the safety of less experienced users.
You can say that they are then stupid. I call them inexperienced. I tried to so many times to post and raise the level of knowledge and we all know where those writing for 8 hours posts went, right?
But this is not about being ignored from "higher devs" about my finding of a side channel attack in the bootloader in 4.3.
This post is just not a safe for those unlucky who got this ****ty phone on their warranty (I got one too). They feel cheated and I understand them.
It's useless, can't use the S4 and not the N9005 stuff. The guys here did an amazing job with it but I had leave. But someone can really do something stupid and and this post gives false "hope". I got some "Pit"-file. Lets try that one...
Since this is also a stub for a "collection" that I also could not finish and I don't recall if I did something more of those but I know you are pros of finding nonsense like this and could you please remove that "clutter" as well?
All the best,
Absie
Abstract
This thread is about testing and finding similarities and differences between the currently two Snapdragon 800 Samsung smartphones, namely the I9506 and Galaxy Note 3 (SM-N9005, hltexx). What we know so far is that they use the same hardware and production line and are separated quite late where they diverge. The theory is therefore that the Samsung Note 3 LTE binaries should work since the development here is non-existent and the similarities are larger between those two then with the previous S4, I9505. The work seem not as straight forward and so far binaries from Note 3 have been incompatible and this thread is about finding our just WHY this is so and how we can try to overcome those problems and have some porting of available ROMs from the major project branches. Similarities with the previous S4 (I9505) will be investigated along the progress of this thread. Since this device is shipped with Android v4.2.2 and without KNOX activated we also need to investigate what activates KNOX and how to avoid that.
Collection of findings
This is a stub of the different pages that will be updated as the progress is ongoing and will be updates as we move along and collect the findings.
General Findings
Stub
Custom Recoveries
Stub
Kernels
Stub
Roms
Stub
Other (KNOX, modems, bootloaders etc)
Stub
.

General Findings​
Things we know
The I9506 and Note 3 (int) are based on the same board and therefore they should be interchangeable.
The Pit-files (Partition information) are identical for the both devices except for the obvious, larger screen, more mem and bigger internal data partition. All other partitions are exactly the same and lies on the same place in the Flash which should porting much easier since the core partition layout is the same and makes it much easier and safer to try different versions.
The initial tests done with trying different Custom recoveries has not worked.
Things we don't know
Are the kernel interchangable? Here we have note yet had a 4.3 for I9506 to compare but Samsung has started to roll out that. Knox is then activated.
Differences between other partitions and their content
Questions that need answers (volunteers are needed!)
Now that we have at least 2 versions of the 4.3, we need to hunt for the same releases made on Note 3 and compare them.
Why is not Custom recovery working? Is it something simple?
Does anything from the I9505 work? Are there any similarities there?
.

Custom Recovery​
So far we hare 2 custom recoveries (links will be provied).
No custom recoveries from Note 3 has yet been working.
The following recoveries from Note 3 have been tested and found not been working my normal replacement in Odin
Philz_touch_6.04.1 - (Give the first BSOD! Blue! Blue!)
Philz_touch_6.08.9 - (Seems like the screen is melting)
Openrecovery-twrp-2.6.3.0 - (Black screen. Nothing happens)
You can all try, those who has 4.3 and Knox 0x01 could test those. It seems a bit scary, but at least for the the "pull the battery and reinstall a normal one with Odin" worked,
but as usual, this is work that need to be done and nobody here can promise anything. Brick/unbrick, but you might be the hero if you get stuff to work from over Note (like a kernel).
So I have something to fill the next post with?
Who initially provided the working custom recoveries and what was done to make them work?
Please PM me if you don't want to write it here.
.

Kernels​

Roms​

Other (KNOX, modems, bootloaders etc)​

Reserved

Absolon said:
Custom Recovery​
So far we hare 2 custom recoveries (links will be provied)
No custom recoveries from Note 3 has yet been working.
The following recoveries from Note 3 have been tested and found not been working my normal replacement in Odin
Philz_touch_6.04.1
Philz_touch_6.08.9
Openrecovery-twrp-2.6.3.0
.
Click to expand...
Click to collapse
Hi Absolon.
Probably because a different portion table. Our is even different from the GT-I9505.
I'll post our full partion table, as it looks on our phone. Just need to get home and fire up my Ubuntu/Linux.
See ya'
Sent from my GT-I9305 using XDA Premium 4 mobile app

I made the Pit files yesterday from the two devices and the are the same.
Same size, same memory adresses.

DeHAWK said:
Hi Absolon.
Probably because a different portion table. Our is even different from the GT-I9505.
I'll post our full partion table, as it looks on our phone. Just need to get home and fire up my Ubuntu/Linux.
See ya'
Sent from my GT-I9305 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did you see the PIT-files I sent you yesterday?
Those where the same. Exactly the same. So how can it differ?
I posted them above this reply

Absolon said:
Did you see the PIT-files I sent you yesterday?
Those where the same. Exactly the same. So how can it differ?
I posted them above this reply
Click to expand...
Click to collapse
Just received them. I put the files up in a moment.
Sent from my GT-I9506 using XDA Premium 4 mobile app
Ok, now back on my PC, look at this..
[email protected]:/ $ ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 2013-06-28 18:24 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-06-28 18:24 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-06-28 18:24 backup -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2013-06-28 18:24 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2013-06-28 18:24 cache > /dev/block/mmcblk0p24
lrwxrwxrwx root root 2013-06-28 18:24 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-06-28 18:24 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-06-28 18:24 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-06-28 18:24 fota -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2013-06-28 18:24 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2013-06-28 18:24 fsg -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2013-06-28 18:24 hidden -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2013-06-28 18:24 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-06-28 18:24 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-06-28 18:24 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-06-28 18:24 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-06-28 18:24 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-06-28 18:24 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2013-06-28 18:24 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2013-06-28 18:24 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2013-06-28 18:24 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-06-28 18:24 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-06-28 18:24 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2013-06-28 18:24 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2013-06-28 18:24 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-06-28 18:24 userdata -> /dev/block/mmcblk0p26
Mount Point Number Filesystem name
/dev/block/mmcblk0p1 anphlos
/dev/block/mmcblk0p2 modem
/dev/block/mmcblk0p3 sbl1
/dev/block/mmcblk0p4 dbi
/dev/block/mmcblk0p5 ddr
/dev/block/mmcblk0p6 aboot
/dev/block/mmcblk0p7 rpm
/dev/block/mmcblk0p8 tz
/dev/block/mmcblk0p9 pad
/dev/block/mmcblk0p10 param
/dev/block/mmcblk0p11 ext4 efs
/dev/block/mmcblk0p12 modemst1
/dev/block/mmcblk0p13 modemst2
/dev/block/mmcblk0p14 boot
/dev/block/mmcblk0p15 recovery
/dev/block/mmcblk0p16 fota
/dev/block/mmcblk0p17 backup
/dev/block/mmcblk0p18 fsg
/dev/block/mmcblk0p19 fsc
/dev/block/mmcblk0p20 ssd
/dev/block/mmcblk0p21 persist
/dev/block/mmcblk0p22 ext4 persdata
/dev/block/mmcblk0p23 ext4 system
/dev/block/mmcblk0p24 ext4 cache
/dev/block/mmcblk0p25 ext4 hidden
/dev/block/mmcblk0p26 ext4 userdata
Number Start End Size File system Name Flags
1 4194kB 17.3MB 13.1MB apnhlos
2 17.3MB 71.3MB 54.0MB mdm
3 71.3MB 71.4MB 131kB sbl1
4 71.4MB 71.7MB 262kB sbl2
5 71.7MB 72.2MB 524kB sbl3
6 72.2MB 74.3MB 2097kB aboot
7 74.3MB 74.8MB 524kB rpm
8 74.8MB 75.4MB 524kB tz
9 75.4MB 92.7MB 17.3MB pad
10 92.7MB 107MB 14.3MB ext4 efs
11 107MB 110MB 3146kB modemst1
12 110MB 113MB 3146kB modemst2
13 113MB 114MB 799kB m9kefs1
14 114MB 115MB 799kB m9kefs2
15 115MB 116MB 799kB m9kefs3
16 116MB 3010MB 2894MB ext4 system
17 3010MB 3018MB 8389kB persist
18 3018MB 5189MB 2171MB ext4 cache
19 5189MB 5195MB 6291kB param
20 5195MB 5205MB 10.5MB boot
21 5205MB 5216MB 10.5MB recovery
22 5216MB 5226MB 10.5MB fota
23 5226MB 5233MB 6291kB backup
24 5233MB 5236MB 3146kB fsg
25 5236MB 5236MB 8192B ssd
26 5236MB 5245MB 9437kB ext4 persdata
27 5245MB 5770MB 524MB ext4 hidden
28 5770MB 5791MB 21.0MB carrier
29 5791MB 15.8GB 9961MB ext4 userdata
I had to find some info in XDA, but it should look like this. One thing is sure, and thats the first part, the last 2 parts I made myself...
Try to run the command: ls -al /dev/block/platform/msm_sdcc.1/by-name
Do it in a terminal.
Btw. Does anybody know why I can't upload screenshots and other stuff???

I just compared the 2 .txt files in excel
The result are in attachement >
Cell B is BASE
Cell A is compared with Cell B
- Everthing green in Cell A is identical with Cell B
- Everthing white in Cell A is different to Cell B
You can also compare to this ref thread [DEV][REF][INFO] Partitions GT-I9506
Cheers

Absolon said:
I made the Pit files yesterday from the two devices and the are the same.
Same size, same memory adresses.
Click to expand...
Click to collapse
Got your mail, looking at them right now and comparing with my own files.
See ya'
---------- Post added at 08:09 PM ---------- Previous post was at 08:01 PM ----------
DeHAWK said:
Got your mail, looking at them right now and comparing with my own files.
See ya'
Click to expand...
Click to collapse
Ok, this looks nice. Have to look more into them.
---------- Post added at 08:21 PM ---------- Previous post was at 08:09 PM ----------
xenix96 said:
I just compared the 2 .txt files in excel
The result are in attachement >
Cell B is BASE
Cell A is compared with Cell B
- Everthing green in Cell A is identical with Cell B
- Everthing white in Cell A is different to Cell B
You can also compare to this ref thread [DEV][REF][INFO] Partitions GT-I9506
Cheers
Click to expand...
Click to collapse
My dear friend, please zip your files, I don't use rar in Ubuntu.
Have to switch to Windows and back...lol
Somethings wrong with my account here, it log out out after a few minutes, can't add pics etc...
But at least I can get in now on my laptop. Might have to cantact the Mod.
See ya'

DeHAWK said:
Got your mail, looking at them right now and comparing with my own files.
See ya'
---------- Post added at 08:09 PM ---------- Previous post was at 08:01 PM ----------
Ok, this looks nice. Have to look more into them.
---------- Post added at 08:21 PM ---------- Previous post was at 08:09 PM ----------
My dear friend, please zip your files, I don't use rar in Ubuntu.
Have to switch to Windows and back...lol
Somethings wrong with my account here, it log out out after a few minutes, can't add pics etc...
But at least I can get in now on my laptop. Might have to cantact the Mod.
See ya'
Click to expand...
Click to collapse
Added Mappe1.zip to http://forum.xda-developers.com/showpost.php?p=49182714&postcount=12
Cheers

Nice thread, i already have the i9506, and i will get my Note 3 as a company phone on wednesday. I'd ble glad to help!

I created my I9506 files from my phone.
All XDA related content will be placed here for reference and PM me your gmails and I give you r/w there.
(changed the link since someone tried to read INSIDE a rar file in gdocs. There is a zip there now as well)
So, as you see, I got the same values, just that you didn't give you any?
We do have exactly the same layout
We know it's the same board
We have recovery that is working
N9005 recoveries are NOT?
Any idea?
Who had the "mended" Philz from start? What was changed so it would work?
Because if we can figure this out it looks promising. If we can't then we need to start trying (need that anyway) compiling stuff and go from there.
But I thought it would be interesting just to check if it would work or not. Damn it...
/Abs
Edit: OMG, I outed myself
xenix96 said:
I just compared the 2 .txt files in excel
The result are in attachement >
Cell B is BASE
Cell A is compared with Cell B
- Everthing green in Cell A is identical with Cell B
- Everthing white in Cell A is different to Cell B
You can also compare to this ref thread [DEV][REF][INFO] Partitions GT-I9506
Cheers
Click to expand...
Click to collapse
I created the PIT-file from my phone.
Will place all further things

xenix96 said:
Added Mappe1.zip to http://forum.xda-developers.com/showpost.php?p=49182714&postcount=12
Cheers
Click to expand...
Click to collapse
Yes, I will use the algorithm that was invented in 1978 (ok 1989 and I have NO IDEA why Google chose that when there are so many more effective alg that are OS)...
I can use LHA, or even a C64 cruncher just to get you start working dammit
And btw, unrar if freeware
/Absie

[Q] Creating partition images on 870A

Does anyone know the relation of which block devices in /dev/mmcblk0pXX belong to which partition? (ex: system, modem, boot, etc)
I'm looking to create a custom Odin AIO package for my install of lollipop, which has been rooted and such; going back to NE4 is a PITA and would like a faster route for when a full wipe is required.
Thanks in advance :good:

After scrounging the internet for awhile, I was able to answer my own question. I've posted the partition scheme below for others who might need it someday:
aboot -> /dev/block/mmcblk0p6
apnhlos -> /dev/block/mmcblk0p1
backup -> /dev/block/mmcblk0p18
boot -> /dev/block/mmcblk0p15
cache -> /dev/block/mmcblk0p24
dbi -> /dev/block/mmcblk0p4
ddr -> /dev/block/mmcblk0p5
efs -> /dev/block/mmcblk0p12
fota -> /dev/block/mmcblk0p17
fsc -> /dev/block/mmcblk0p19
fsg -> /dev/block/mmcblk0p9
modem -> /dev/block/mmcblk0p2
modemst1 -> /dev/block/mmcblk0p13
modemst2 -> /dev/block/mmcblk0p14
pad -> /dev/block/mmcblk0p10
param -> /dev/block/mmcblk0p11
persdata -> /dev/block/mmcblk0p22
persist -> /dev/block/mmcblk0p21
recovery -> /dev/block/mmcblk0p16
rpm -> /dev/block/mmcblk0p7
sbl1 -> /dev/block/mmcblk0p3
ssd -> /dev/block/mmcblk0p20
system -> /dev/block/mmcblk0p23
tz -> /dev/block/mmcblk0p8
userdata -> /dev/block/mmcblk0p25