[R&D] Pit file, aboot, partition info

[BeansTown106]

just starting a thread with some of the things we will need when unlocked or to help devs with unlocking this is also a discussion thread pertaining to bootloader development/hacks

these are from retail Verizon Note3 with build VRUBMI9

partition info:

lrwxrwxrwx root root 1969-12-31 22:37 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1969-12-31 22:37 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1969-12-31 22:37 backup -> /dev/block/mmcblk0p17 
lrwxrwxrwx root root 1969-12-31 22:37 boot -> /dev/block/mmcblk0p14 
lrwxrwxrwx root root 1969-12-31 22:37 cache -> /dev/block/mmcblk0p24 
lrwxrwxrwx root root 1969-12-31 22:37 dbi -> /dev/block/mmcblk0p4 
lrwxrwxrwx root root 1969-12-31 22:37 ddr -> /dev/block/mmcblk0p5 
lrwxrwxrwx root root 1969-12-31 22:37 efs -> /dev/block/mmcblk0p11 
lrwxrwxrwx root root 1969-12-31 22:37 fota -> /dev/block/mmcblk0p16 
lrwxrwxrwx root root 1969-12-31 22:37 fsc -> /dev/block/mmcblk0p19 
lrwxrwxrwx root root 1969-12-31 22:37 fsg -> /dev/block/mmcblk0p18 
lrwxrwxrwx root root 1969-12-31 22:37 modem -> /dev/block/mmcblk0p2 
lrwxrwxrwx root root 1969-12-31 22:37 modemst1 -> /dev/block/mmcblk0p12 
lrwxrwxrwx root root 1969-12-31 22:37 modemst2 -> /dev/block/mmcblk0p13 
lrwxrwxrwx root root 1969-12-31 22:37 pad -> /dev/block/mmcblk0p9 
lrwxrwxrwx root root 1969-12-31 22:37 param -> /dev/block/mmcblk0p10 
lrwxrwxrwx root root 1969-12-31 22:37 persdata -> /dev/block/mmcblk0p22 
lrwxrwxrwx root root 1969-12-31 22:37 persist -> /dev/block/mmcblk0p21 
lrwxrwxrwx root root 1969-12-31 22:37 recovery -> /dev/block/mmcblk0p15 
lrwxrwxrwx root root 1969-12-31 22:37 rpm -> /dev/block/mmcblk0p7 
lrwxrwxrwx root root 1969-12-31 22:37 sbl1 -> /dev/block/mmcblk0p3 
lrwxrwxrwx root root 1969-12-31 22:37 ssd -> /dev/block/mmcblk0p20 
lrwxrwxrwx root root 1969-12-31 22:37 system -> /dev/block/mmcblk0p23 
lrwxrwxrwx root root 1969-12-31 22:37 tz -> /dev/block/mmcblk0p8 
lrwxrwxrwx root root 1969-12-31 22:37 userdata -> /dev/block/mmcblk0p25

PIT Analysis:

Started by user anonymous
[EnvInject] - Loading node environment variables.
Building in workspace /var/lib/jenkins/workspace/Analyze PIT File
Copying file to ./part.pit
[Analyze PIT File] $ /bin/bash +x /tmp/hudson5599640215980603364.sh
-----BEGIN PIT ANALYSIS-----

PIT Name: MSM8974
Entry Count: 29
File Type: COM_TAR2


--- Entry #0 ---
ID: 1   Partition Name: APNHLOS
Filename: NON-HLOS.bin
Block Size: 30720 (15.7MB)
Block range: 8192 - 38911 (hex 0x2000 - 0x97ff)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The APNHLOS partition, identified as partition number 1, is 15.7MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as NON-HLOS.bin.


--- Entry #1 ---
ID: 2   Partition Name: MODEM
Filename: modem.bin
Block Size: 117632 (60.2MB)
Block range: 38912 - 156543 (hex 0x9800 - 0x2637f)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The MODEM partition, identified as partition number 2, is 60.2MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as modem.bin.


--- Entry #2 ---
ID: 3   Partition Name: SBL1
Filename: sbl1.mbn
Block Size: 1024 (524.3kB)
Block range: 156544 - 157567 (hex 0x26380 - 0x2677f)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The SBL1 partition, identified as partition number 3, is 524.3kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as sbl1.mbn.


--- Entry #3 ---
ID: 4   Partition Name: DBI
Filename: sdi.mbn
Block Size: 64 (32.8kB)
Block range: 157568 - 157631 (hex 0x26780 - 0x267bf)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The DBI partition, identified as partition number 4, is 32.8kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as sdi.mbn.


--- Entry #4 ---
ID: 5   Partition Name: DDR
Filename: 
Block Size: 64 (32.8kB)
Block range: 157632 - 157695 (hex 0x267c0 - 0x267ff)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The DDR partition, identified as partition number 5, is 32.8kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. 


--- Entry #5 ---
ID: 6   Partition Name: ABOOT
Filename: aboot.mbn
Block Size: 4096 (2.1MB)
Block range: 157696 - 161791 (hex 0x26800 - 0x277ff)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The ABOOT partition, identified as partition number 6, is 2.1MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as aboot.mbn.


--- Entry #6 ---
ID: 7   Partition Name: RPM
Filename: rpm.mbn
Block Size: 1024 (524.3kB)
Block range: 161792 - 162815 (hex 0x27800 - 0x27bff)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The RPM partition, identified as partition number 7, is 524.3kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as rpm.mbn.


--- Entry #7 ---
ID: 8   Partition Name: TZ
Filename: tz.mbn
Block Size: 1024 (524.3kB)
Block range: 162816 - 163839 (hex 0x27c00 - 0x27fff)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The TZ partition, identified as partition number 8, is 524.3kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as tz.mbn.


--- Entry #8 ---
ID: 9   Partition Name: PAD
Filename: 
Block Size: 20480 (10.5MB)
Block range: 163840 - 184319 (hex 0x28000 - 0x2cfff)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The PAD partition, identified as partition number 9, is 10.5MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. 


--- Entry #9 ---
ID: 10   Partition Name: PARAM
Filename: param.bin
Block Size: 20480 (10.5MB)
Block range: 184320 - 204799 (hex 0x2d000 - 0x31fff)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The PARAM partition, identified as partition number 10, is 10.5MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as param.bin.


--- Entry #10 ---
ID: 11   Partition Name: EFS
Filename: efs.img.ext4
Block Size: 28672 (14.7MB)
Block range: 204800 - 233471 (hex 0x32000 - 0x38fff)
PartType: 5   FilesystemType: 5   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The EFS partition, identified as partition number 11, is 14.7MB in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as efs.img.ext4.


--- Entry #11 ---
ID: 12   Partition Name: MODEMST1
Filename: nvrebuild1.bin
Block Size: 6144 (3.1MB)
Block range: 233472 - 239615 (hex 0x39000 - 0x3a7ff)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The MODEMST1 partition, identified as partition number 12, is 3.1MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as nvrebuild1.bin.


--- Entry #12 ---
ID: 13   Partition Name: MODEMST2
Filename: nvrebuild2.bin
Block Size: 6144 (3.1MB)
Block range: 239616 - 245759 (hex 0x3a800 - 0x3bfff)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The MODEMST2 partition, identified as partition number 13, is 3.1MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as nvrebuild2.bin.


--- Entry #13 ---
ID: 14   Partition Name: BOOT
Filename: boot.img
Block Size: 22528 (11.5MB)
Block range: 245760 - 268287 (hex 0x3c000 - 0x417ff)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The BOOT partition, identified as partition number 14, is 11.5MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as boot.img.


--- Entry #14 ---
ID: 15   Partition Name: RECOVERY
Filename: recovery.img
Block Size: 26624 (13.6MB)
Block range: 268288 - 294911 (hex 0x41800 - 0x47fff)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The RECOVERY partition, identified as partition number 15, is 13.6MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as recovery.img.


--- Entry #15 ---
ID: 16   Partition Name: FOTA
Filename: 
Block Size: 26624 (13.6MB)
Block range: 294912 - 321535 (hex 0x48000 - 0x4e7ff)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The FOTA partition, identified as partition number 16, is 13.6MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. 


--- Entry #16 ---
ID: 17   Partition Name: BACKUP
Filename: 
Block Size: 14318 (7.3MB)
Block range: 321536 - 335853 (hex 0x4e800 - 0x51fed)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The BACKUP partition, identified as partition number 17, is 7.3MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. 


--- Entry #17 ---
ID: 18   Partition Name: FSG
Filename: 
Block Size: 6144 (3.1MB)
Block range: 335854 - 341997 (hex 0x51fee - 0x537ed)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The FSG partition, identified as partition number 18, is 3.1MB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. 


--- Entry #18 ---
ID: 19   Partition Name: FSC
Filename: 
Block Size: 2 (1.0kB)
Block range: 341998 - 341999 (hex 0x537ee - 0x537ef)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The FSC partition, identified as partition number 19, is 1.0kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. 


--- Entry #19 ---
ID: 20   Partition Name: SSD
Filename: 
Block Size: 16 (8.2kB)
Block range: 342000 - 342015 (hex 0x537f0 - 0x537ff)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The SSD partition, identified as partition number 20, is 8.2kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. 


--- Entry #20 ---
ID: 21   Partition Name: PERSIST
Filename: persist.img.ext4
Block Size: 16384 (8.4MB)
Block range: 342016 - 358399 (hex 0x53800 - 0x577ff)
PartType: 5   FilesystemType: 5   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The PERSIST partition, identified as partition number 21, is 8.4MB in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as persist.img.ext4.


--- Entry #21 ---
ID: 22   Partition Name: PERSDATA
Filename: persdata.img.ext4
Block Size: 18432 (9.4MB)
Block range: 358400 - 376831 (hex 0x57800 - 0x5bfff)
PartType: 5   FilesystemType: 5   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The PERSDATA partition, identified as partition number 22, is 9.4MB in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as persdata.img.ext4.


--- Entry #22 ---
ID: 23   Partition Name: SYSTEM
Filename: system.img.ext4
Block Size: 5554176 (2.8GB)
Block range: 376832 - 5931007 (hex 0x5c000 - 0x5a7fff)
PartType: 5   FilesystemType: 5   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The SYSTEM partition, identified as partition number 23, is 2.8GB in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as system.img.ext4.


--- Entry #23 ---
ID: 24   Partition Name: CACHE
Filename: cache.img.ext4
Block Size: 2097152 (1.1GB)
Block range: 5931008 - 8028159 (hex 0x5a8000 - 0x7a7fff)
PartType: 5   FilesystemType: 5   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The CACHE partition, identified as partition number 24, is 1.1GB in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as cache.img.ext4.


--- Entry #24 ---
ID: 25   Partition Name: USERDATA
Filename: userdata.img.ext4
Block Size: 0 (0B)
Block range: 8028160 - 8028159 (hex 0x7a8000 - 0x7a7fff)
PartType: 5   FilesystemType: 5   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: remained
The USERDATA partition, identified as partition number 25, is 0B in size. It carries a EXT4 format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as userdata.img.ext4. The partition will expand to fill the remainder of the EMMC.


--- Entry #25 ---
ID: 70   Partition Name: PGPT
Filename: pgpt.img
Block Size: 34 (17.4kB)
Block range: 0 - 33 (hex 0x0 - 0x21)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The PGPT partition, identified as partition number 70, is 17.4kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as pgpt.img.


--- Entry #26 ---
ID: 71   Partition Name: PIT
Filename: MSM8974.pit
Block Size: 16 (8.2kB)
Block range: 34 - 49 (hex 0x22 - 0x31)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The PIT partition, identified as partition number 71, is 8.2kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as MSM8974.pit.


--- Entry #27 ---
ID: 72   Partition Name: MD5
Filename: md5.img
Block Size: 32 (16.4kB)
Block range: 50 - 81 (hex 0x32 - 0x51)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The MD5 partition, identified as partition number 72, is 16.4kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as md5.img.


--- Entry #28 ---
ID: 73   Partition Name: SGPT
Filename: sgpt.img
Block Size: 33 (16.9kB)
Block range: 61071327 - 61071359 (hex 0x3a3dfdf - 0x3a3dfff)
PartType: 5   FilesystemType: 1   BinType: 0   DevType: 2
Offset:0   Size: 0   FOTA: 
The SGPT partition, identified as partition number 73, is 16.9kB in size. It carries a Basic format and Data data type. The partition resides on the AP EMMC. It identifies itself to Odin as sgpt.img.





-----END PIT ANALYSIS-----
Finished: SUCCESS

aboot: http://www.androidfilehost.com/?fid=23159073880936456

pit: http://www.androidfilehost.com/?fid=23159073880936457

unbrick image for vzw n3: http://www.androidfilehost.com/?fid=23159073880937014 use in combo with design gears/shabbypenguins method just use this image instead of the one in his thread http://forum.xda-developers.com/showthread.php?t=2476353

 

[aerichards1977]

Glad to see you here. Dumped the htc, huh? About time

Sent from my SM-N900V using Tapatalk

 

[Clamhost]

just starting a thread with some of the things we will need when unlocked or to help devs with unlocking this is also a discussion thread pertaining to bootloader development/hacks

these are from retail Verizon Note3 with build VRUBMI9

partition info:

lrwxrwxrwx root root 1969-12-31 22:37 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1969-12-31 22:37 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1969-12-31 22:37 backup -> /dev/block/mmcblk0p17 
lrwxrwxrwx root root 1969-12-31 22:37 boot -> /dev/block/mmcblk0p14 
lrwxrwxrwx root root 1969-12-31 22:37 cache -> /dev/block/mmcblk0p24 
lrwxrwxrwx root root 1969-12-31 22:37 dbi -> /dev/block/mmcblk0p4 
lrwxrwxrwx root root 1969-12-31 22:37 ddr -> /dev/block/mmcblk0p5 
lrwxrwxrwx root root 1969-12-31 22:37 efs -> /dev/block/mmcblk0p11 
lrwxrwxrwx root root 1969-12-31 22:37 fota -> /dev/block/mmcblk0p16 
lrwxrwxrwx root root 1969-12-31 22:37 fsc -> /dev/block/mmcblk0p19 
lrwxrwxrwx root root 1969-12-31 22:37 fsg -> /dev/block/mmcblk0p18 
lrwxrwxrwx root root 1969-12-31 22:37 modem -> /dev/block/mmcblk0p2 
lrwxrwxrwx root root 1969-12-31 22:37 modemst1 -> /dev/block/mmcblk0p12 
lrwxrwxrwx root root 1969-12-31 22:37 modemst2 -> /dev/block/mmcblk0p13 
lrwxrwxrwx root root 1969-12-31 22:37 pad -> /dev/block/mmcblk0p9 
lrwxrwxrwx root root 1969-12-31 22:37 param -> /dev/block/mmcblk0p10 
lrwxrwxrwx root root 1969-12-31 22:37 persdata -> /dev/block/mmcblk0p22 
lrwxrwxrwx root root 1969-12-31 22:37 persist -> /dev/block/mmcblk0p21 
lrwxrwxrwx root root 1969-12-31 22:37 recovery -> /dev/block/mmcblk0p15 
lrwxrwxrwx root root 1969-12-31 22:37 rpm -> /dev/block/mmcblk0p7 
lrwxrwxrwx root root 1969-12-31 22:37 sbl1 -> /dev/block/mmcblk0p3 
lrwxrwxrwx root root 1969-12-31 22:37 ssd -> /dev/block/mmcblk0p20 
lrwxrwxrwx root root 1969-12-31 22:37 system -> /dev/block/mmcblk0p23 
lrwxrwxrwx root root 1969-12-31 22:37 tz -> /dev/block/mmcblk0p8 
lrwxrwxrwx root root 1969-12-31 22:37 userdata -> /dev/block/mmcblk0p25

aboot:

pit:

So excited to see a bootloader unlock in the works. It's nice to see people/devs taking the time to try to benefit the community, via bootloader unlock.

 

[BeansTown106]

Glad to see you here. Dumped the htc, huh? About time

Sent from my SM-N900V using Tapatalk

ya returned it today and got the retail note3 still planning on getting the dev edition though

So excited to see a bootloader unlock in the works. It's nice to see people/devs taking the time to try to benefit the community, via bootloader unlock.

dont think there is one in the works but a workaround for recovery most likely is. getting a true unlock on this device is highly unlikely.

 

[keynith]

Im waiting on that dev edition too!

Sent from my SM-N900V using Tapatalk

 

[drsoftich]

Oh man, I hope we will see a beans note 3 rom...

Sent from my SM-N900V using XDA Premium 4 mobile app

 

[abe_cedar]

ya returned it today and got the retail note3 still planning on getting the dev edition though

dont think there is one in the works but a workaround for recovery most likely is. getting a true unlock on this device is highly unlikely.

Beans
Sent you a donation for your great sammy support sir.
22 updates from you on note 2.
Can't wait 4 dev edt.
Thanks

---------- Post added at 10:11 PM ---------- Previous post was at 10:10 PM ----------

Oh man, I hope we will see a beans note 3 rom...

Sent from my SM-N900V using XDA Premium 4 mobile app

Me too

 

[droidstyle]

Thanks for posting this! Pit file will definitely be useful for recovering from a soft brick!

 

[downhillvinnie]

Great to see you here too....Just got a Note 3 today!

 

[Bizack]

Glad to see you beans...

Sent from my SM-N900V using Tapatalk now Free

 

[TechSavvy2]

Just to add if you so well please....wrote this up last week as a reference when I was gonna pull system dumps, but then the factory images got posted up for grabs and made them useless.....same sh1t, with small additions, plus partition sizes

major     minor  #blocks   name         Label

   7        0      21861 loop0		
   7        1       3150 loop1		
   7        2      26019 loop2		
   7        3       9387 loop3		
   7        4       2111 loop4		
   7        5       4190 loop5		
   7        6      26019 loop6		
 179        0   30535680 mmcblk0	
 179        1      15360 mmcblk0p1	apnhlos
 179        2      58816 mmcblk0p2	modem
 179        3        512 mmcblk0p3	sbl1
 179        4         32 mmcblk0p4	dbi
 179        5         32 mmcblk0p5	ddr
 179        6       2048 mmcblk0p6	aboot
 179        7        512 mmcblk0p7	rpm
 179        8        512 mmcblk0p8	tz
 179        9      10240 mmcblk0p9	pad
 179       10      10240 mmcblk0p10	param
 179       11      14336 mmcblk0p11	efs
 179       12       3072 mmcblk0p12	modemst1
 179       13       3072 mmcblk0p13	modemst2
 179       14      11264 mmcblk0p14	boot
 179       15      13312 mmcblk0p15	recovery
 179       16      13312 mmcblk0p16	fota
 179       17       7159 mmcblk0p17	backup
 179       18       3072 mmcblk0p18	fsg
 179       19          1 mmcblk0p19	fsc
 179       20          8 mmcblk0p20	ssd
 179       21       8192 mmcblk0p21	persist
 179       22       9216 mmcblk0p22	persdata
 179       23    2777088 mmcblk0p23	system
 179       24    1048576 mmcblk0p24	cache
 179       25   26521583 mmcblk0p25	userdata
 179       32        512 mmcblk0rpmb	
 179       64   30702592 mmcblk1	
 179       65   30701568 mmcblk1p1	
 254        0      21861 dm-0		
 254        1       3150 dm-1		
 254        2      26019 dm-2		
 254        3       9387 dm-3		
 254        4       2110 dm-4		
 254        5       4189 dm-5		
 254        6      26019 dm-6

AS A SIDE NOTE:
Now if other people feel like doing the same thing I WAS gonna do before the images got posted, and pull your own stuff for safe-keeping, you can do the following commands in adb:

(Root required for this method)

> adb shell
> su
> dd if=/dev/block/mmcblk0p15 of=/sdcard/recovery.img

This will pull the factory stock recovery image and place it on your internal sd-card for you to do what you please with. Note for others, you need replace location and file name.

 

[imbolc]

Beans..
Great to see you with n3. I still have to take your 22 off my n2 and go back to factory so I can put it on eBay.
Looking forward to some great roms from you in the future.

Sent from my SM-N900V using xda app-developers app

 

[wy1d]

Beans..
Great to see you with n3. I still have to take your 22 off my n2 and go back to factory so I can put it on eBay.
Looking forward to some great roms from you in the future.

Sent from my SM-N900V using xda app-developers app

Same here on all points!

My coworker also a Note 2 and was considering a HTC One Max but when I told him Beans was hanging out in the Note 3 forums he picked up the Note 3 instead. Can't wait for Beans on Note 3!

 

[Spectredroid]

Beans + note 3= Best phone ever. However you are right Beans, unlock unlikely. I might sell mine and get the dev edition too. Are you going to make a rom for the dev edition?

Sent from my SM-N900V using Tapatalk

 

[kdizzleh85]

Just waiting on either the dev edition or the unlocked bootloader. Glad to see you here man. Thanks for this.

Sent from my SPH-L900 using Xparent BlueTapatalk 2
Team Nocturnal Member
Always RoCkIn GoOdNeSs
[email protected]

 

[daavy]

cool beans

glad to see beans on this too... was using his rom for my s3 for the longest time... a dev N3 isnt in my future so i hope you guys can get something working

 

[760hacker]

From all the notes i see regarding bootloader unlock it doesn't appear that anyone is optimistic. Someone correct me if you have seen otherwise? If this is going to likely remain locked down, i'm gonna have a hard decision to make. For those that are gonna jump ship before to another device, which are you considering?

 

[Gil Smash]

From all the notes i see regarding bootloader unlock it doesn't appear that anyone is optimistic. Someone correct me if you have seen otherwise? If this is going to likely remain locked down, i'm gonna have a hard decision to make. For those that are gonna jump ship before to another device, which are you considering?

Pretty sure we'll get bootloader bypass and recovery at the very least. Unlock may not be possible but with a bypass you can still install roms and kernels and functions almost the same for the most part.

Sent from my SM-N900V using Tapatalk

 

[760hacker]

Right but using kexec?

Sent from my SM-N900V using Tapatalk

 

[Thepooch]

I have seen It happen with Amazons second gen. Kindle Fire @Hashcode rocked right through that issue good chance he could be an asset in the search. I can not speak for the Devs but I can say these guys twist up the ball of adversity that companies try to push at us and over hand pitch it back at them. It can be done when is the only question, now just patience is required. Power to the Devs!!