Related
Hi, I had recently flashed the jellybean leak Ota for my tab(it's p3100), I had then flashed cwm. Now I tried resetting my flash counter but after rebooting it still stuck at 1 count. What should I do?
Sent from my GT-P3100 using XDA Premium HD app
Help anyone?
Sent from my GT-P3100 using XDA Premium HD app
Maybe flash back to ics. And reset the counter
Sent from my GT-I9100 using Tapatalk 2
Aditya16 said:
Hi, I had recently flashed the jellybean leak Ota for my tab(it's p3100), I had then flashed cwm. Now I tried resetting my flash counter but after rebooting it still stuck at 1 count. What should I do?
Sent from my GT-P3100 using XDA Premium HD app
Click to expand...
Click to collapse
have you tried "Triangule Away" ?
you can installed it from google play
but you need to root your device first
sapiterbang said:
have you tried "Triangle Away" ?
you can installed it from google play
but you need to root your device first
Click to expand...
Click to collapse
I resetted it with that only. Is it some bug in jb?
Sent from my GT-P3100 using XDA Premium HD app
Alvin Lai said:
Maybe flash back to ics. And reset the counter
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Will try that.
Sent from my GT-P3100 using XDA Premium HD app
May be try installing supersu ( not superuser) from google play and give permissions to triangle away
Install latest version 1.95 of triangle away
Sent from Galaxy S2 or Galaxy Tab2
I confirm Triangle Away and SuperSU combination still work in JB.
So after rebooting and going to the download mode, even for me it is zero, but after exiting and booting back it goes back to 1 count.
Sent from my GT-P3100 using XDA Premium HD app
Aditya16 said:
So after rebooting and going to the download mode, even for me it is zero, but after exiting and booting back it goes back to 1 count.
Sent from my GT-P3100 using XDA Premium HD app
Click to expand...
Click to collapse
Post your issue in Triangle Away thread. Maybe someone can help you...
---------- Post added at 05:06 PM ---------- Previous post was at 05:06 PM ----------
Aditya16 said:
So after rebooting and going to the download mode, even for me it is zero, but after exiting and booting back it goes back to 1 count.
Sent from my GT-P3100 using XDA Premium HD app
Click to expand...
Click to collapse
Post your issue in Triangle Away thread. Maybe someone could help you
Waw... Back from recovery I got +1. This is not because JB but Sbl.bin updated (download mode in potrait position now). The second boot loader checkbit RECOVERY partition:
Code:
Secondary Bootloader v3.1 version.
Copyright (C) 2011 System S/W Group. Samsung Electronics Co., Ltd.
Board: GT-P3100 REV 04-REAL / Sep 17 2012 13:37:57
booting code=0x0
===== PARTITION INFORMATION =====
ID : X-loader (0x1)
DEVICE : MMC
FIRST UNIT : 0
NO. UNITS : 0
=================================
ID : EFS (0x4)
DEVICE : MMC
FIRST UNIT : 8192
NO. UNITS : 40960
=================================
ID : SBL1 (0x2)
DEVICE : MMC
FIRST UNIT : 49152
NO. UNITS : 4096
=================================
ID : SBL2 (0x3)
DEVICE : MMC
FIRST UNIT : 53248
NO. UNITS : 4096
=================================
ID : PARAM (0x5)
DEVICE : MMC
FIRST UNIT : 57344
NO. UNITS : 16384
=================================
ID : KERNEL (0x6)
DEVICE : MMC
FIRST UNIT : 73728
NO. UNITS : 16384
=================================
ID : RECOVERY (0x7)
DEVICE : MMC
FIRST UNIT : 90112
NO. UNITS : 16384
=================================
ID : CACHE (0x8)
DEVICE : MMC
FIRST UNIT : 106496
NO. UNITS : 1433600
=================================
ID : MODEM (0x9)
DEVICE : MMC
FIRST UNIT : 1540096
NO. UNITS : 40960
=================================
ID : FACTORYFS (0xa)
DEVICE : MMC
FIRST UNIT : 1581056
NO. UNITS : 2867200
=================================
ID : DATAFS (0xb)
DEVICE : MMC
FIRST UNIT : 4448256
NO. UNITS : 25280478
=================================
ID : HIDDEN (0xd)
DEVICE : MMC
FIRST UNIT : 29728734
NO. UNITS : 1048576
=================================
ID : GANG (0x0)
DEVICE : MMC
FIRST UNIT : 0
NO. UNITS : 0
=================================
loke_init: j4fs_open..success
<start_checksum:310>CHECKSUM_HEADER_SECTOR :42
<start_checksum:313>offset:42, size:1024
Not Need Movinand Checksum
load_lfs_parameters valid magic code and version.
switch_sel_str='1'
switch_sel_int='1'
load_debug_level: read debug level successfully(0x574f4c44)...LOW
init_ddi_data: usable ddi data.
Set charging current TA
omap_max17042_read_temp: FG Temp raw_data : 0x2723
read_temp_adc:adc_data : 772
read_temp_adc:adc_data : 763
read_temp_adc:adc_data : 765
read_temp_adc:adc_data : 759
read_temp_adc:adc_data : 758
check_battery_type: fg temp : 39136, adc_temp : 420
check_battery_type: Set BATTERY_TYPE_SDI
omap_max17042_set_model_data : Already fuel gauge initialized !!
max17042_compensate_soc: vcell(3840), rep_soc(43)
calculate_table_soc: charging status : 2, vcell(3840), table_soc(52)
[SBL] VFOCV MSB : 0xc0, LSB : 0x7
[SBL_CHARGER] SOC : 43, VCELL : 3840, VFSOC : 42, VFOCV : 3840
save param.blk, size: 5268
save param.blk successfully.
save switch_sel(1)...ok
reading nps status file is successfully!.
nps status=0x504d4f43
g_nRebootReason = 0x1
set_lcd_panel_id: panel_adc=142
*** ltn070nl01_power_on ***
lcd_pannel_id=2
Autoboot (1 seconds) in progress, press any key to stop .
boot_kernel: debug level low!
checkbit: find RECOVERY
checkbit (f55f0aa0)
Kernel @ 81808000 (0x3f715c bytes)
Ramdisk @ 82800000 (0x880aa bytes)
Starting kernel at 0x81808000...
Now I need Sbl.bin backup from ICS!
ketut.kumajaya said:
Waw... Back from recovery I got +1. This is not because JB but Sbl.bin updated (download mode in potrait position now). The second boot loader checkbit RECOVERY partition:
Code:
Secondary Bootloader v3.1 version.
Copyright (C) 2011 System S/W Group. Samsung Electronics Co., Ltd.
Board: GT-P3100 REV 04-REAL / Sep 17 2012 13:37:57
booting code=0x0
===== PARTITION INFORMATION =====
ID : X-loader (0x1)
DEVICE : MMC
FIRST UNIT : 0
NO. UNITS : 0
=================================
ID : EFS (0x4)
DEVICE : MMC
FIRST UNIT : 8192
NO. UNITS : 40960
=================================
ID : SBL1 (0x2)
DEVICE : MMC
FIRST UNIT : 49152
NO. UNITS : 4096
=================================
ID : SBL2 (0x3)
DEVICE : MMC
FIRST UNIT : 53248
NO. UNITS : 4096
=================================
ID : PARAM (0x5)
DEVICE : MMC
FIRST UNIT : 57344
NO. UNITS : 16384
=================================
ID : KERNEL (0x6)
DEVICE : MMC
FIRST UNIT : 73728
NO. UNITS : 16384
=================================
ID : RECOVERY (0x7)
DEVICE : MMC
FIRST UNIT : 90112
NO. UNITS : 16384
=================================
ID : CACHE (0x8)
DEVICE : MMC
FIRST UNIT : 106496
NO. UNITS : 1433600
=================================
ID : MODEM (0x9)
DEVICE : MMC
FIRST UNIT : 1540096
NO. UNITS : 40960
=================================
ID : FACTORYFS (0xa)
DEVICE : MMC
FIRST UNIT : 1581056
NO. UNITS : 2867200
=================================
ID : DATAFS (0xb)
DEVICE : MMC
FIRST UNIT : 4448256
NO. UNITS : 25280478
=================================
ID : HIDDEN (0xd)
DEVICE : MMC
FIRST UNIT : 29728734
NO. UNITS : 1048576
=================================
ID : GANG (0x0)
DEVICE : MMC
FIRST UNIT : 0
NO. UNITS : 0
=================================
loke_init: j4fs_open..success
<start_checksum:310>CHECKSUM_HEADER_SECTOR :42
<start_checksum:313>offset:42, size:1024
Not Need Movinand Checksum
load_lfs_parameters valid magic code and version.
switch_sel_str='1'
switch_sel_int='1'
load_debug_level: read debug level successfully(0x574f4c44)...LOW
init_ddi_data: usable ddi data.
Set charging current TA
omap_max17042_read_temp: FG Temp raw_data : 0x2723
read_temp_adc:adc_data : 772
read_temp_adc:adc_data : 763
read_temp_adc:adc_data : 765
read_temp_adc:adc_data : 759
read_temp_adc:adc_data : 758
check_battery_type: fg temp : 39136, adc_temp : 420
check_battery_type: Set BATTERY_TYPE_SDI
omap_max17042_set_model_data : Already fuel gauge initialized !!
max17042_compensate_soc: vcell(3840), rep_soc(43)
calculate_table_soc: charging status : 2, vcell(3840), table_soc(52)
[SBL] VFOCV MSB : 0xc0, LSB : 0x7
[SBL_CHARGER] SOC : 43, VCELL : 3840, VFSOC : 42, VFOCV : 3840
save param.blk, size: 5268
save param.blk successfully.
save switch_sel(1)...ok
reading nps status file is successfully!.
nps status=0x504d4f43
g_nRebootReason = 0x1
set_lcd_panel_id: panel_adc=142
*** ltn070nl01_power_on ***
lcd_pannel_id=2
Autoboot (1 seconds) in progress, press any key to stop .
boot_kernel: debug level low!
checkbit: find RECOVERY
checkbit (f55f0aa0)
Kernel @ 81808000 (0x3f715c bytes)
Ramdisk @ 82800000 (0x880aa bytes)
Starting kernel at 0x81808000...
Now I need Sbl.bin backup from ICS!
Click to expand...
Click to collapse
How will i get this sbl.bin file from?
Aditya16 said:
How will i get this sbl.bin file from?
Click to expand...
Click to collapse
From /dev/block/mmcblk0p2 and /dev/block/mmcblk0p3. Be careful, this is a critical part of boot process.
I really do not not know how to do it advice please?
Sent from my GT-P3100 using XDA Premium HD app
News update guy's. Chainfire pm'ed me saying that he will look into the matter. Now all we can do is cross our finger and wait.
Oh and also this download mode does not show +1 when I replaced CWM with stock recovery. I wonder why?
Sent from my GT-P3100 using XDA Premium HD app
UPDATE:
No warning when boot to stock JB XXCLI5 recovery:
Code:
g_nRebootReason = 0x2
set_lcd_panel_id: panel_adc=143
*** ltn070nl01_power_on ***
lcd_pannel_id=2
Autoboot (1 seconds) in progress, press any key to stop .
boot_kernel: debug level low!
checkbit: find RECOVERY
checkbit (f55f0aa0)
Kernel @ 81808000 (0x3f715c bytes)
Ramdisk @ 82800000 (0x135b4d bytes)
save param.blk, size: 5268
save param.blk successfully.
save switch_sel(1)...ok
Starting kernel at 0x81808000...
More investigation needed, when boot to unofficial recovery:
Code:
g_nRebootReason = 0x2
set_lcd_panel_id: panel_adc=143
*** ltn070nl01_power_on ***
lcd_pannel_id=2
Autoboot (1 seconds) in progress, press any key to stop .
boot_kernel: debug level low!
checkbit: find RECOVERY
checkbit (f55f0aa0)
Kernel @ 81808000 (0x39a7b0 bytes)
Ramdisk @ 82800000 (0x1e4fc6 bytes)
[WARNING] Current kernel is NOT official binary!!!
save param.blk, size: 5268
save param.blk successfully.
save switch_sel(1)...ok
Starting kernel at 0x81808000...
Normal boot to stock JB XXCLI5 kernel:
Code:
g_nRebootReason = 0x1
set_lcd_panel_id: panel_adc=142
*** ltn070nl01_power_on ***
lcd_pannel_id=2
Autoboot (1 seconds) in progress, press any key to stop .
boot_kernel: debug level low!
checkbit: find RECOVERY
checkbit (f55f0aa0)
Kernel @ 81808000 (0x3f715c bytes)
Ramdisk @ 82800000 (0x880aa bytes)
Starting kernel at 0x81808000...
Parsed above value from /proc/last_kmsg. From last_kmsg value (second boot loader message?), I can confirm my boot logo hack is safe. Sbl successfuly mount param.lfs:
Code:
loke_init: j4fs_open..success
<start_checksum:310>CHECKSUM_HEADER_SECTOR :42
<start_checksum:313>offset:42, size:1024
Not Need Movinand Checksum
load_lfs_parameters valid magic code and version.
THIS ONLY WORKS ON ROOTED ROMS/DEVICES
As a owner of the original Galaxy s i have encounter the problem like no radio signal etc, after flashing certain roms,this was because the efs partition/folder somehow got wiped.
This could be fixed by flashing certain original roms, or restoring the EFS folder from a backup, of course allot of people never did such backup
Soo, after you flash a rooted rom into your device this is one of the first thing you must do, believe me soon or later you gonna need it!
Here is how to:
1-Put your device into USB debugging mode
2- download busybox from the market and installed it, launch busybox in the device and press install.
3- download EFS-PRO from here, don't forget to thank the developer
4- launch the application in you pc
5- in " Data Backup Method select" "create compressed tar " or "create partition image" (Personally i used the tar method)
Tick "Save to device storage" and "Save to pc storage,then click "Backup EFS" button.
now you shoud have a Backup of the efs in you device storage card and one in the EFS pro folder in your pc, save it to a safe place and never share it!
{
"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"
}
Many thanks to the developer of EFS PRO tools.
Thanks a lot for the tip mate
One more way to back the efs is to manually mount the filesystems and then copy the /efs folder and paste it somewhere safe
I have not personally tried it Can someone confirm whether this works ? I see no reason that it shouldn't but better be safe than sorry
P.S. This also needs root
Hi, Faria! I messed up the EFS and now I have a problem with the phone, wrote in other forum threads. You know how much, I could not make the file EFS for Odin3 that would fix and restore it.
Great post, and very useful advice. Other partitions can be backup up as well in the following way:
Code:
cd /storage/extSdCard
mkdir backup
cd backup
dd if=/dev/block/mmcblk0p1 of=mmcblk0p1
dd if=/dev/block/mmcblk0boot0 of=mmcblk0boot0
dd if=/dev/block/mmcblk0boot1 of=mmcblk0boot0
dd if=/dev/block/mmcblk0p2 of=mmcblk0p2
dd if=/dev/block/mmcblk0p3 of=mmcblk0p3
dd if=/dev/block/mmcblk0p4 of=mmcblk0p4
dd if=/dev/block/mmcblk0p5 of=mmcblk0p5
dd if=/dev/block/mmcblk0p6 of=mmcblk0p6
dd if=/dev/block/mmcblk0p7 of=mmcblk0p7
dd if=/dev/block/mmcblk0p8 of=mmcblk0p8
dd if=/dev/block/mmcblk0p9 of=mmcblk0p9
dd if=/dev/block/mmcblk0p10 of=mmcblk0p10
dd if=/dev/block/mmcblk0p11 of=mmcblk0p11
dd if=/dev/block/mmcblk0p12 of=mmcblk0p12
dd if=/dev/block/mmcblk0p13 of=mmcblk0p13
dd if=/dev/block/mmcblk0p14 of=mmcblk0p14
dd if=/dev/block/mmcblk0p15 of=mmcblk0p15
dd if=/dev/block/mmcblk0p16 of=mmcblk0p16
dd if=/dev/block/mmcblk0p17 of=mmcblk0p17
dd if=/dev/block/mmcblk0p18 of=mmcblk0p18
dd if=/dev/block/mmcblk0p19 of=mmcblk0p19
sync
This will backup everything excluding the boot, recovery, system, cache, hidden, and data partitions. For the record, here is the PIT partition table:
Code:
--- Entry #0 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 1
Partition Flags: 2 (R/W)
Unknown 1: 1
Partition Block Size: 0
Partition Block Count: 256
Unknown 2: 0
Unknown 3: 0
Partition Name: MBR,GPT
Filename:
--- Entry #1 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 2
Partition Flags: 2 (R/W)
Unknown 1: 1
Partition Block Size: 256
Partition Block Count: 768
Unknown 2: 0
Unknown 3: 0
Partition Name: MasterTOC
Filename: STE_boot.bin
--- Entry #2 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 70
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 1024
Partition Block Count: 2048
Unknown 2: 0
Unknown 3: 0
Partition Name: PIT
Filename: goldenxx.pit
--- Entry #3 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 71
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 6144
Partition Block Count: 2048
Unknown 2: 0
Unknown 3: 0
Partition Name: MD5HDR
Filename: md5.img
--- Entry #4 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 3
Partition Flags: 2 (R/W)
Unknown 1: 1
Partition Block Size: 8192
Partition Block Count: 1024
Unknown 2: 0
Unknown 3: 0
Partition Name: STEboot1
Filename: STE_boot1.img
--- Entry #5 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 4
Partition Flags: 2 (R/W)
Unknown 1: 1
Partition Block Size: 9216
Partition Block Count: 1024
Unknown 2: 0
Unknown 3: 0
Partition Name: STEboot2
Filename: STE_boot2.img
--- Entry #6 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 5
Partition Flags: 2 (R/W)
Unknown 1: 1
Partition Block Size: 10240
Partition Block Count: 1024
Unknown 2: 0
Unknown 3: 0
Partition Name: Dnt
Filename: dnt.ssw
--- Entry #7 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 6
Partition Flags: 2 (R/W)
Unknown 1: 1
Partition Block Size: 11264
Partition Block Count: 1024
Unknown 2: 0
Unknown 3: 0
Partition Name: reserved
Filename:
--- Entry #8 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 7
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 16384
Partition Block Count: 2048
Unknown 2: 0
Unknown 3: 0
Partition Name: CSPSAFS
Filename: cspsa.img
--- Entry #9 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 8
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 18432
Partition Block Count: 2048
Unknown 2: 0
Unknown 3: 0
Partition Name: CSPSAFS2
Filename: cspsa2.img
--- Entry #10 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 9
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 20480
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: EFS
Filename: EFS.img
--- Entry #11 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 10
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 53248
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: ModemFS
Filename: modemfs.img
--- Entry #12 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 11
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 86016
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: ModemFS2
Filename: modemfs2.img
--- Entry #13 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 12
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 118784
Partition Block Count: 102400
Unknown 2: 0
Unknown 3: 0
Partition Name: Fota
Filename: ssgtest.img
--- Entry #14 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 13
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 380928
Partition Block Count: 128
Unknown 2: 0
Unknown 3: 0
Partition Name: IPL Modem
Filename: ipl.bin
--- Entry #15 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 14
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 385024
Partition Block Count: 28672
Unknown 2: 0
Unknown 3: 0
Partition Name: Modem
Filename: modem.bin
--- Entry #16 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 15
Partition Flags: 2 (R/W)
Unknown 1: 1
Partition Block Size: 417792
Partition Block Count: 4096
Unknown 2: 0
Unknown 3: 0
Partition Name: Loke4
Filename: normal.bin
--- Entry #17 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 16
Partition Flags: 2 (R/W)
Unknown 1: 1
Partition Block Size: 421888
Partition Block Count: 4096
Unknown 2: 0
Unknown 3: 0
Partition Name: 2ndLoke4
Filename: normal2.bin
--- Entry #18 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 17
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 425984
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: PARAM
Filename: param.lfs
--- Entry #19 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 18
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 458752
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: Kernel
Filename: boot.img
--- Entry #20 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 19
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 491520
Partition Block Count: 32768
Unknown 2: 0
Unknown 3: 0
Partition Name: Kernel2
Filename: recovery.img
--- Entry #21 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 20
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 524288
Partition Block Count: 2457600
Unknown 2: 0
Unknown 3: 0
Partition Name: SYSTEM
Filename: system.img
--- Entry #22 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 21
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 2981888
Partition Block Count: 1720320
Unknown 2: 0
Unknown 3: 0
Partition Name: CACHEFS
Filename: cache.img
--- Entry #23 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 22
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 4702208
Partition Block Count: 655360
Unknown 2: 0
Unknown 3: 0
Partition Name: HIDDEN
Filename: hidden.img
--- Entry #24 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 23
Partition Flags: 5 (R)
Unknown 1: 5
Partition Block Size: 5357568
Partition Block Count: 9891840
Unknown 2: 0
Unknown 3: 0
Partition Name: DATAFS
Filename: userdata.img
PEV201078 said:
Hi, Faria! I messed up the EFS and now I have a problem with the phone, wrote in other forum threads. You know how much, I could not make the file EFS for Odin3 that would fix and restore it.
Click to expand...
Click to collapse
The tool itself will restore the efs, no need for odin.
But if you never back up the efs folder this tool is not gonna help you now.
Never can find my device... :S
MalekoUK said:
Never can find my device... :S
Click to expand...
Click to collapse
Connect it first then run the program. That helped me.
But I could never get it to work, finds device but no partitions appear. Also says Qualcomm device disabled.
I backed up my efs folder using root explorer but still wanted to do this...
MalekoUK said:
Never can find my device... :S
Click to expand...
Click to collapse
Usb debuging on?
You sure you got all the drivers installed on the pc?
Try another usb slot?
All drivers installed, tested with ADB works, dunno if that means anything.
Sent from my SIII Mini using Tapatalk
for me;
efs ok connect I8190.
ok info rom .
(no partion detect)
Do not use the latest version of EFS , you will not be able to backup anything , search for an older version 1.x.x , I do the same and successfully backup my efs on i8190 .
evilinside said:
Do not use the latest version of EFS , you will not be able to backup anything , search for an older version 1.x.x , I do the same and successfully backup my efs on i8190 .
Click to expand...
Click to collapse
Thanks very much. I couldn't get 2.x.x version working, got a 1.9.12 and worked perfectly.
swagmeister said:
Thanks very much. I couldn't get 2.x.x version working, got a 1.9.12 and worked perfectly.
Click to expand...
Click to collapse
Worked perfectly for me with 1.9.12
Backup success
With the version 1.9.12 it worked for me, too!
Backup, backup backup!
Worked great for me on my GT-I8190L with EFS Pro v1.9.12 :good:
Can someone upload their EFS backup and paste it here, cause I kinda messed mine up and I can't get it back.
Thanks.
Edit: I actually need /modemfs folder /efs is fine.
No will post their efs folder here and if they do it will be taken down.
Efs folder contains the imei, mac etc.
No one wants their phone cloned.
Yes I realized that that's why I edited my post.I need a /modemfs folder, what's in there?
Edit: My /modemfs folder.
I think something's missing in there, I formatted it cause I accidentally installed a boot loader in it (dumba$$ I know) and no matter how many times i flashed my phone via Odin the radio didn't work.
Benzonat0r said:
Yes I realized that that's why I edited my post.I need a /modemfs folder, what's in there?
Edit: My /modemfs folder.
I think something's missing in there, I formatted it cause I accidentally installed a boot loader in it (dumba$$ I know) and no matter how many times i flashed my phone via Odin the radio didn't work.
Click to expand...
Click to collapse
In that folder alone you missing GARDFIIL and trace_auto.conf
I can't find version 1.9.12
Any idea how to...
Tks!
(90% of the time the main cause of Android device lag is slow internal Flash memory!)
Lately, my Note had gotten laggy- apps were taking forever to open, Chrome was slow opening pages and things were just slow overall. Was it one of my kernel mods? Was it the DeOdexed ROM? I'd gone back to a stock kernel and switched back to a stock ROM, but it was still laggy. I'd turned on "Show CPU Usage" and sure enough, my Note was spending a LOT of time in "IOWait" (the blue bar) and the system was spending a lot of time running the process "mmcqd/0" (the kernel thread that runs the Flash memory). None of my troubleshooing worked and I couldn't figure it out 'till I did a "df" and discovered I'd made a newbie mistake- I'd had only 750MB remaining on /data (which also includes where the internal sdcard is located). Bingo!
For those who don't know, I'll give you the "TL;DR" lesson on Flash memories- the fuller they get, the slower they get.
A more-detailed explanation: the controller on a Flash device takes longer to find free space to write file data on as it gets fuller- the "erase size" is usually far bigger than the average size of a kernel write, so the Flash device's internal controller can't find enough empty flash blocks it has to do some time-consuming "Read-Erase-Write" operations, and when that happens (which can take many milliseconds and adds up quickly) no other I/O can happen on the flash device, so your Android device lags as your CPU helplessly sits there waiting for all the I/O to complete. Although we're using the "discard" option on our /data partition (which lets the Flash-memory controller know when Linux has removed a file, helping it keep more available empty blocks for later write operations), there's only so much that can be done when the percentage of free space falls below a certain point.
(OK, the following steps aren't for absolute newbies, and you have to be rooted- so the Standard XDA Disclaimer of "If you fsck this up, don't blame me!" applies here!)
So, I'd first determined where all the space was going (I used "cd /data ; du -kx | sort -rn | head"). In my case, it was a couple of cached Vudu movies, YouTube caching of my "Watch Later", a couple of movies that I hadn't moved to the SD-Card and the Samsung "Note Screensaver" and "Note Manual" apps. I also used TiBu to Integrate updates of my apps back to the ROM. All told, I'd freed up about 4GB.
Next, I ran "fstrim -v /data" to help the Flash memory controller reclaim the space internally. After a reboot (only necessary 'cause of the TiBu "Integrate to ROM"), Voila! Back to speed!
I've attached a zipped-up copy of my "fstrim" binary, and for those using my kernels (which I'll be updating soon as I've got some other goodies too) they'll now have automatic "fstrim" on bootup (BTW, the free version (at least) of "LagFree" app doesn't work on our Notes for some reason).
(TL;DR: keep your internal storage as free as possible, else everything slows down.)
Do I need root to do this?
I spent some time doing some file shuffling between my internal and external memory cards and freed about 3gb of stuff from the internal sd. Tablet is more responsive but I'd still like to be able to clear my cacbes.
Sent from my GT-N8013 using XDA Premium HD app
Temetka said:
Do I need root to do this?
Click to expand...
Click to collapse
Looks like your question was already answered.
kcrudup said:
(OK, the following steps aren't for absolute newbies, and you have to be rooted- so the Standard XDA Disclaimer of "If you fsck this up, don't blame me!" applies here!)
Click to expand...
Click to collapse
Yes it was.
In my defense I was very tired. Just chalk it to me being that guy who asked the obvious.
Sent from my GT-N8013 using XDA Premium HD app
Temetka said:
Just chalk it to me being that guy who asked the obvious
Click to expand...
Click to collapse
Ah, don't sweat it, we've all done it- "Let he of ye without sin ..." and all
But in the next few days (and against my better judgement ) I'll be putting out a series of boot.img files for the most popular ROMs out there (i.e., "the ones I've used"): the latest Samsung Official, Darkman's latest and AR HD's latest.
They'll have my latest OC and upgraded kernels, and my YouTube and "fstrim" mods and I'll update them fairly often.
Is there a non-ODIN method to install boot.img? If not can you make flashable zips?
This very reason is why i bought the 32 gb version.. Some with my nexus 7 and my phone 16 gb .... Its well worth the little bit of extra money .. But its awesome to have people here willing to help. I know on the nexus if you get it half full you will have very bad slow down and issues. This has been discussed over and over in the GOOGLE TECH FORUMS and some here on the xda nexus forum..
I think like with a windows pc . if you move around install and uninstall alot of software applications . You should once in a while wipe and re install the os .So for android devices Cloud storage is awesome.I use a ftp app that will sync to my ftp site once a week of the night time..
I can wipe my device restore from the ftp quick easy and no loss of data...
erica_renee said:
This very reason is why I bought the 32 GB version
Click to expand...
Click to collapse
Yeah, I looked everywhere for a GT-N8000 with 32GB, and apparently they don't make one.
I think like with a windows PC, if you move around, install and uninstall a lot of software applications you should once in a while wipe and re-install the os
Click to expand...
Click to collapse
Well, that's really apples-and-oranges here, though. All that matters to US is relative storage availability (and the "discard" mount flag to give the Flash device hints, which is turned on even in Stock kernels) so there's room for the device to re-arrange things. Based on the design of Android, wipes are really only necessary when an app (or an owner ...) misbehaves.
Remember, too, that most of our devices' OS is in read-only-memory and never changes, also invalidating the need to install.
Windows, on the other hand, is just a mess
kcrudup said:
Yeah, I looked everywhere for a GT-N8000 with 32GB, and apparently they don't make one.
Well, that's really apples-and-oranges here, though. All that matters to US is relative storage availability (and the "discard" mount flag to give the Flash device hints, which is turned on even in Stock kernels) so there's room for the device to re-arrange things. Based on the design of Android, wipes are really only necessary when an app (or an owner ...) misbehaves.
Remember, too, that most of our devices' OS is in read-only-memory and never changes, also invalidating the need to install.
Windows, on the other hand, is just a mess
Click to expand...
Click to collapse
That is true... OOPS and you might be right on the GT-N8000. I have n8013 wifi only tab. Could not find the 3g one within any reasonable price range i was willing to pay..
ohh Sometimes im a mess as well... but thats obvious huh?
Just sold my Galaxy Tab 10.1 and bought a note. My question is, how much space should the system and all the preinstalled apps/bloat take up? I bought a white 16GB and upon turning it on it shows I only have 11.66GB of total space and 11.09GB of free space. Applications are taking up 228MB, Audio is at 20KB, Misc is at 194MB. Does the system really take up almost 4.5GB? Seems like a whole lot.
Shouldn't the system show 16GB of total space? My SGS3 does. Why does the note show only 11.66GB os total space?
The Apostle said:
Does the system really take up almost 4.5GB?
Click to expand...
Click to collapse
Yes, it does.
Seems like a whole lot.
Click to expand...
Click to collapse
No, it isn't.
Shouldn't the system show 16GB of total space?
Click to expand...
Click to collapse
No, it shouldn't.
Regarding to memory space,
Titanium Backup shows me a 2.48 mb free out of 1.44 gb sys rom memory !!!
So, where is the 4.5 gb the rest of 16 gb ???
Sent from my GT-N8000 using xda premium
hatem 5000 said:
So, where is the 4.5 gb the rest of 16 gb
Click to expand...
Click to collapse
There are a LOT of partitions besides system/data/cache/boot/recovery you've got to consider, too:
Code:
$ adb shell cat /proc/partitions | fgrep mmcblk0
179 0 15388672 mmcblk0
179 1 4096 mmcblk0p1
179 2 4096 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 32768 mmcblk0p7
179 8 819200 mmcblk0p8
179 9 1433600 mmcblk0p9
179 10 512000 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 12521472 mmcblk0p12
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
$
... and here's a human-readable dump of the PIT file for the N8000:
Code:
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 80
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size: 0
Partition Block Count: 1734
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOTLOADER
Flash Filename: sboot.bin
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 81
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 1734
Partition Block Count: 312
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TZSW
Flash Filename: tz.img
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 34
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: note10.pit
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 50
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5HDR
Flash Filename: md5.img
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 8192
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA0
Flash Filename: -
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 16384
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA1
Flash Filename: -
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 24576
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img
FOTA Filename:
--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 65536
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.bin
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 81920
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 98304
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 114688
Partition Block Count: 65536
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RADIO
Flash Filename: modem.bin
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 180224
Partition Block Count: 1638400
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 1818624
Partition Block Count: 2867200
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 4685824
Partition Block Count: 1024000
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img
FOTA Filename:
--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size: 5709824
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: OTA
Flash Filename: -
FOTA Filename:
--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size: 5726208
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USERDATA
Flash Filename: userdata.img
FOTA Filename: remained
kcrudup said:
Yes, it does.
No, it isn't.
No, it shouldn't.
Click to expand...
Click to collapse
Thsnk you but can anyone provide insight on why the 16GB note would show 11.66GB of total space and the GSIII would show 16GB of total space?
Sent From a far away Galaxy, in Missouri.
The Apostle said:
Thsnk you but can anyone provide insight on why the 16GB note would show 11.66GB of total space and the GSIII would show 16GB of total space?
Sent From a far away Galaxy, in Missouri.
Click to expand...
Click to collapse
My s3 shows 11.95 gb disk space available by the way! So its the same.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
The Apostle said:
Thsnk you but can anyone provide insight on why the 16GB note would show 11.66GB of total space and the GSIII would show 16GB of total space?
Sent From a far away Galaxy, in Missouri.
Click to expand...
Click to collapse
Every storage device has less than the advertised amount of space available. For example 1tb drives only have 965mb available.
Sent from the mighty Note II
dr.m0x said:
Every storage device has less than the advertised amount of space available. For example 1tb drives only have 965mb available
Click to expand...
Click to collapse
Actually, that particular difference is only due to difference in the definition of sizes; computer people like to think in terms of powers of 2, so a "Terabyte" to computer people is 2^30, or 1073741824 bytes. However, disk-drive manufacturers started using powers-of-10 "Terabytes" (1000000000) so they could legally claim a "Terabyte" (or "Megabyte", as the case may be) but short-change us by not meeting the computer-referenced version of same, so that same "1TiB" drive is really only 954 of the Megabytes that really count.
In the case of our Flash drives, the reason it's smaller than the 16GB (and it's a real "computer 16GB", 16777216 bytes) is because of what I'd stated above, partitioning of the drive into partitions we can't consider available for data storage.
kcrudup said:
Actually, that particular difference is only due to difference in the definition of sizes; computer people like to think in terms of powers of 2, so a "Terabyte" to computer people is 2^30, or 1073741824 bytes. However, disk-drive manufacturers started using powers-of-10 "Terabytes" (1000000000) so they could legally claim a "Terabyte" (or "Megabyte", as the case may be) but short-change us by not meeting the computer-referenced version of same, so that same "1TiB" drive is really only 954 of the Megabytes that really count.
In the case of our Flash drives, the reason it's smaller than the 16GB (and it's a real "computer 16GB", 16777216 bytes) is because of what I'd stated above, partitioning of the drive into partitions we can't consider available for data storage.
Click to expand...
Click to collapse
Well I'm still awake, but barely.
Sent from the mighty Note II
I would like to first start by sharing a bit of history behind this library. @Benjamin Dobell started the Heimdall project where he packet-sniffed the Odin(desktop client)/Loke(on-device server) protocol in order to create Heimdall, an open source flashing tool which I've personally used in my own projects Heimdall one-click and One-Click UnBrick as well as my current project, CASUAL. Heimdall was released with a very rough, but working, analysis of the PIT files and has been slowly increasing over time.
@Ralekdev , @Rebellos and myself began looking at the PIT files much later than Benjamin. Ralekdev and Rebellos were to reverse-engineer the bootloaders of several Samsung devices and was able to come up exploits while I somewhat brought the work together and assisted where I could. Ralekdev even identified proper sizes of data blocks and has created a few tools to assist.
Introduction
I'm happy to announce that we have 100% identification of all parts of the PIT files as they stand today. We are no longer working on identifying variables thanks to Ralekdev, Rebellos and Benjamin's work. We can read, and write and integrate PIT files into our Java Applications. As a demonstration of this library, i encourage you to
Analyze Your Pit File Online
If you don't have a PIT file, you can use this one. This will provide you with human-readable analysis of a PIT file.
This can also be accomplished locally on your computer with this file: http://goo.im/devs/AdamOutler/libpitX/libpit-X-R917.jar
Code:
[email protected]:~$libpit-X.jar GalaxyCamera.pit
PIT Name: Mx
Entry Count: 17
File Type: COM_TAR2
--- Entry #0 ---
ID: 80 Partition Name: BOOTLOADER
Filename: sboot.bin param: md5
Block Size: 1734 (887.8 kB)
Block range: 0 - 1733 (hex 0x0 - 0x6c5)
PartType: 2 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This Basic format Bootloader partition resides on the AP EMMC.
--- Entry #1 ---
ID: 81 Partition Name: TZSW
Filename: tz.img param: md5
Block Size: 312 (159.7 kB)
Block range: 1734 - 2045 (hex 0x6c6 - 0x7fd)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This Basic format Data partition resides on the AP EMMC.
--- Entry #2 ---
ID: 70 Partition Name: PIT
Filename: camera.pit
Block Size: 16 (8.2 kB)
Block range: 34 - 49 (hex 0x22 - 0x31)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This Basic format Data partition resides on the AP EMMC.
--- Entry #3 ---
ID: 71 Partition Name: MD5HDR
Filename: md5.img param: in.md5
Block Size: 2048 (1.0 MB)
Block range: 50 - 2097 (hex 0x32 - 0x831)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This Basic format Data partition resides on the AP EMMC.
--- Entry #4 ---
ID: 1 Partition Name: BOTA0
Filename: -
Block Size: 8192 (4.2 MB)
Block range: 8192 - 16383 (hex 0x2000 - 0x3fff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This Basic format Data partition resides on the AP EMMC.
--- Entry #5 ---
ID: 2 Partition Name: BOTA1
Filename: -
Block Size: 8192 (4.2 MB)
Block range: 16384 - 24575 (hex 0x4000 - 0x5fff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This Basic format Data partition resides on the AP EMMC.
--- Entry #6 ---
ID: 3 Partition Name: EFS
Filename: efs.img param: md5
Block Size: 40960 (21.0 MB)
Block range: 24576 - 65535 (hex 0x6000 - 0xffff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This EXT4 format Data partition resides on the AP EMMC.
--- Entry #7 ---
ID: 4 Partition Name: PARAM
Filename: param.bin param: md5
Block Size: 16384 (8.4 MB)
Block range: 65536 - 81919 (hex 0x10000 - 0x13fff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This Basic format Data partition resides on the AP EMMC.
--- Entry #8 ---
ID: 5 Partition Name: BOOT
Filename: boot.img param: md5
Block Size: 16384 (8.4 MB)
Block range: 81920 - 98303 (hex 0x14000 - 0x17fff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This Basic format Data partition resides on the AP EMMC.
--- Entry #9 ---
ID: 6 Partition Name: RECOVERY
Filename: recovery.img param: md5
Block Size: 16384 (8.4 MB)
Block range: 98304 - 114687 (hex 0x18000 - 0x1bfff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This Basic format Data partition resides on the AP EMMC.
--- Entry #10 ---
ID: 7 Partition Name: RADIO
Filename: modem.bin param: md5
Block Size: 65536 (33.6 MB)
Block range: 114688 - 180223 (hex 0x1c000 - 0x2bfff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This Basic format Data partition resides on the AP EMMC.
--- Entry #11 ---
ID: 8 Partition Name: CACHE
Filename: cache.img param: md5
Block Size: 2097152 (1.1 GB)
Block range: 180224 - 2277375 (hex 0x2c000 - 0x22bfff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This EXT4 format Data partition resides on the AP EMMC.
--- Entry #12 ---
ID: 9 Partition Name: SYSTEM
Filename: system.img param: md5
Block Size: 3145728 (1.6 GB)
Block range: 2277376 - 5423103 (hex 0x22c000 - 0x52bfff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This EXT4 format Data partition resides on the AP EMMC.
--- Entry #13 ---
ID: 10 Partition Name: HIDDEN
Filename: hidden.img param: md5
Block Size: 737280 (377.5 MB)
Block range: 5423104 - 6160383 (hex 0x52c000 - 0x5dffff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This EXT4 format Data partition resides on the AP EMMC.
--- Entry #14 ---
ID: 11 Partition Name: OTA
Filename: -
Block Size: 16384 (8.4 MB)
Block range: 6160384 - 6176767 (hex 0x5e0000 - 0x5e3fff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This Basic format Data partition resides on the AP EMMC.
--- Entry #15 ---
ID: 12 Partition Name: TDATA param: TA
Filename: - param: erdata.img param: md5
Block Size: 409600 (209.7 MB)
Block range: 6176768 - 6586367 (hex 0x5e4000 - 0x647fff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA: param: Dmained
This EXT4 format Data partition resides on the AP EMMC.
--- Entry #16 ---
ID: 13 Partition Name: USERDATA
Filename: userdata.img
Block Size: 0 (0 B)
Block range: 6586368 - 6586367 (hex 0x648000 - 0x647fff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA: remained
This EXT4 format Data partition resides on the AP EMMC. The partition will expand to fill the remainder of the EMMC.
Development Library/Downloads/Documentation
The libpit-X library is an extremely heavy overhaul of the libpit--Java- library by Benjamin Dobell. It features 100% accurate read/write/modification ability. It is also very well documented. I've submitted an issue for Benjamin to pull my changes. Until then you can find the library here.
Online documentation can be found here: http://javadoc.casual-dev.com/namespacecom_1_1casual__dev_1_1libpit_x.html
When you load a Library into your development environment, you need three parts. The Package, the Javadoc and the Source. The latest version of these three parts can be found here:
Package: http://jenkins.casual-dev.com/view/All/job/Build libpitX/ws/trunk/X/libpitX/dist/libpit-X.jar
Javadoc: http://jenkins.casual-dev.com/view/...runk/X/libpitX/dist/javadoc/*zip*/javadoc.zip
Source: http://jenkins.casual-dev.com/view/All/job/Build libpitX/ws/trunk/X/libpitX/src/*zip*/src.zip
Library Archives can be found here: http://goo.im/devs/AdamOutler/libpitX
Here's a picture of the library in action: http://dl.xda-developers.com/attach...3/7/8/Screenshot_from_2013-11-23_21_16_36.png
Automated Testing
Testing is conducted on EVERY SINGLE REVISION and compiled code is not published to the archvies if testing fails.
Latest test results: http://jenkins.casual-dev.com/job/CASUALbuild Test/lastBuild/console
Test code for this $X project: https://code.google.com/p/android-c...trunk/CASUALcore/test/CASUAL/archiving/libpit
And of course you can always test version yourself with our Analyze Your Pit File Online utility.
About
This is a $X project. The $ represents CASUAL for two reasons; CASUAL commands start with $, and the way CASUAL is commonly pronounced is cash-ual. In $X projects, the $ is silent. $X projects are not CASUAL core projects but rather offshoots. Rather than create an entire new repository for $X projects, we will host them in the http://android-casual.googlecode.com repository. For example, the working source code for this project is located in the CASUAL-Core and during build, the $X project is automatically created in the X.casual_dev.libpitX pacakge.
If you wish to contribute to this project, or any other CASUAL project, check out the "Developers" section of this page: http://casual-dev.com/about/. There's a lot to do and we are wiling to help you learn.
Please tell how to redistribute space from cache and hidden partions to increase user space with your utility?
Adam, most PIT files I analyze have one or two strange partitions at the end..is this the fault of the analysis software or is just something else completely? Also, have you ever been able to extract the pit from a device that you was the same as ( md5 match) one you would get in a odin tar? The pit files I extract never end up being the exact same as the pit files that come in the odin tar for a particular device regardless of the method used; Heimdall and/or using dd if/of= w/ correct skip/count don't yield the right results. The PIT analysis tool you helped make lists everything correctly for the VZW GS4 but doesnt list the strange partition at the end thats found with other analysis tools like the one below, so I assume the last thing isn't a partition then?
TL;DR - What is the partition at the end with strange characters?
{
"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"
}
Surge1223 said:
TL;DR - What is the partition at the end with strange characters?
Click to expand...
Click to collapse
That would appear to be a signature.
Please tell me this is going to lead 16gig Samsung Sg4 users to get more than 9 gigs free space when using a non touch wiz ROM . Great project and congrats
igoa said:
Please tell how to redistribute space from cache and hidden partions to increase user space with your utility?
Click to expand...
Click to collapse
This isn't a utility, it's a library. You would include it in your Android Application or Java Desktop App.
Here's how you would use it for your project
Code:
Class BlockResizer{
public void remove100BlocksFromCACHE(){
//Open the PIT file
PitData pd=new PitData("mypit.pit");
//get the CACHE partition
PitEntry CACHE=pd.findEntry(String partitionName);
//Remove 100 blocks from CACHE
int blocksToRemove=100;
CACHE.block_count=CACHE.block_count-blocksToRemove;
//Loop through the rest of the partitions and bump them up 100 blocks.
for (int i=CACHE.part_id+1; i<pd.entryCount; i++){
pd.getEntry(i).BLOCK_START=pd.getEntry(i).BLOCK_START-blocksToRemove;
}
//write out the new PIT to "newPit.pit"
pd.pack(new DataOutputStream(new FileOutputStream("newPit.pit");
}
This would work just fine assuming that the rest of the partitions after the CACHE are in proper order.
igoa said:
Please tell how to redistribute space from cache and hidden partions to increase user space with your utility?
Click to expand...
Click to collapse
Hey, i just added the ability to do this easily after reviewing the code for a bit. The commit is still processing and the new library and documentation should be up shortly... Here goes a partition resize
Code:
public void resize(){
PitData instance = new PitData("MyPitFile.pit");
String partName="CACHE"; //partition name to change
int changeToSize=-2000; //size to change partition (-2000 blocks= 1 megabyte smaller)
try {
instance.resizePartition(partName, changeToSize); //actually resizes the partiton and all others are moved.
} catch (ClassNotFoundException ex) {
Logger.getLogger(PitDataTest.class.getName()).log(Level.SEVERE, null, ex); //this occurs if the partition specified is not found
}
instance.pack(new DataOutputStream(new FileOutputStream("newPit.pit"); //write out the new PIT to "newPit.pit"
}
This code has accompanying test code. So, if you'd like to resize a PIT, all you need to do is add the libpitX library into an existing project then run the code above.
AdamOutler said:
That would appear to be a signature.
Click to expand...
Click to collapse
This is very interesting. Is there anything we can do with it? Or is this read only/unknown flash protocol?
ryanbg said:
This is very interesting. Is there anything we can do with it? Or is this read only/unknown flash protocol?
Click to expand...
Click to collapse
You can append it to the end of the file.
AdamOutler said:
You can append it to the end of the file.
Click to expand...
Click to collapse
So it's not possible to write my own certificate to this 'partition' yet?
ryanbg said:
So it's not possible to write my own certificate to this 'partition' yet?
Click to expand...
Click to collapse
Yeah but it's worthless without Samsung's private key.
AdamOutler said:
Yeah but it's worthless without Samsung's private key.
Click to expand...
Click to collapse
Have you seen this post? here
and more specifically this:
ERROR: Image Invalid, X509_Certificate is NULL!
ERROR: Boot Invalid, RSA_KEY is NULL!
ERROR: Image Invalid! Decryption failed!
ERROR: Image Invalid! Please use another image!
Does this make a difference?
That's just strings and it says what error you'll get if you put in a null signature.
@AdamOutler for the VZW Galaxy S4 I analyzed the PIT file produced by Heimdall and it reports the last four partitions as "remained" so I decided to manually extract my PIT file using
Code:
su
dd if=/dev/block/mmcblk0 of=/sdcard/sch1545.pit bs=8 count=580 skip=2176
which is specific to MSM8690 S4's and the PIT analysis now shows the "remained" partitions actual values and you can see the PIT I extracted is factory signed, because I compare the md5 to the PIT from a factory Odin tar here so is this problem unique to just the S4 or is it a Heimdall problem? I assumed Heimdall just extracted the padded PIT file but even so it should still show the information for the last 4 partitions.
Before
Code:
--- Entry #29 ---
ID: -1 Partition Name: remained
Filename: remained
Block Size: -1 (-512 B)
Block range: -1 - -3 (hex 0xffffffff - 0xfffffffd)
PartType: -1 FilesystemType: -1 BinType: -1 DevType: -1
Offset:-1 Size: -1 FOTA: remained
This unknown format unknown partition resides on the CP unknwon. The partition will expand to fill the remainder of the unknwon.
--- Entry #30 ---
ID: -1 Partition Name: remained
Filename: remained
Block Size: -1 (-512 B)
Block range: -1 - -3 (hex 0xffffffff - 0xfffffffd)
PartType: -1 FilesystemType: -1 BinType: -1 DevType: -1
Offset:-1 Size: -1 FOTA: remained
This unknown format unknown partition resides on the CP unknwon. The partition will expand to fill the remainder of the unknwon.
--- Entry #31 ---
ID: -1 Partition Name: remained
Filename: remained
Block Size: -1 (-512 B)
Block range: -1 - -3 (hex 0xffffffff - 0xfffffffd)
PartType: -1 FilesystemType: -1 BinType: -1 DevType: -1
Offset:-1 Size: -1 FOTA: remained
This unknown format unknown partition resides on the CP unknwon. The partition will expand to fill the remainder of the unknwon.
--- Entry #32 ---
ID: -1 Partition Name: remained
Filename: remained
Block Size: -1 (-512 B)
Block range: -1 - -3 (hex 0xffffffff - 0xfffffffd)
PartType: -1 FilesystemType: -1 BinType: -1 DevType: -1
Offset:-1 Size: -1 FOTA: remained
This unknown format unknown partition resides on the CP unknwon. The partition will expand to fill the remainder of the unknwon.
After
Code:
--- Entry #29 ---
ID: 70 Partition Name: PGPT
Filename: pgpt.img
Block Size: 34 (17.4kB)
Block range: 0 - 33 (hex 0x0 - 0x21)
FilesystemType: 1 PartType: 5 DevType: 2 BinType: 0
Offset:0 Size: 0 FOTA:
The PGPT partition, identified as partition number 70, is 17.4kB in size and carries a Basic format. This partition resides on the Data section of the AP EMMC. It identifies itself to Odin as pgpt.img.
--- Entry #30 ---
ID: 71 Partition Name: PIT
Filename: MSM8960.pit
Block Size: 16 (8.2kB)
Block range: 34 - 49 (hex 0x22 - 0x31)
FilesystemType: 1 PartType: 5 DevType: 2 BinType: 0
Offset:0 Size: 0 FOTA:
The PIT partition, identified as partition number 71, is 8.2kB in size and carries a Basic format. This partition resides on the Data section of the AP EMMC. It identifies itself to Odin as MSM8960.pit.
--- Entry #31 ---
ID: 72 Partition Name: MD5
Filename: md5.img
Block Size: 32 (16.4kB)
Block range: 50 - 81 (hex 0x32 - 0x51)
FilesystemType: 1 PartType: 5 DevType: 2 BinType: 0
Offset:0 Size: 0 FOTA:
The MD5 partition, identified as partition number 72, is 16.4kB in size and carries a Basic format. This partition resides on the Data section of the AP EMMC. It identifies itself to Odin as md5.img.
--- Entry #32 ---
ID: 73 Partition Name: SGPT
Filename: sgpt.img
Block Size: 33 (16.9kB)
Block range: 30777311 - 30777343 (hex 0x1d59fdf - 0x1d59fff)
FilesystemType: 1 PartType: 5 DevType: 2 BinType: 0
Offset:0 Size: 0 FOTA:
The SGPT partition, identified as partition number 73, is 16.9kB in size and carries a Basic format. This partition resides on the Data section of the AP EMMC. It identifies itself to Odin as sgpt.img.
bump
Surge1223 said:
@AdamOutler for the VZW Galaxy S4 I analyzed the PIT file produced by Heimdall and it reports the last four partitions as "remained" so I decided to manually extract my PIT file using
Code:
su
dd if=/dev/block/mmcblk0 of=/sdcard/sch1545.pit bs=8 count=580 skip=2176
which is specific to MSM8690 S4's and the PIT analysis now shows the "remained" partitions actual values and you can see the PIT I extracted is factory signed, because I compare the md5 to the PIT from a factory Odin tar here so is this problem unique to just the S4 or is it a Heimdall problem? I assumed Heimdall just extracted the padded PIT file but even so it should still show the information for the last 4 partitions.
Before
Code:
--- Entry #29 ---
ID: -1 Partition Name: remained
Filename: remained
Block Size: -1 (-512 B)
Block range: -1 - -3 (hex 0xffffffff - 0xfffffffd)
PartType: -1 FilesystemType: -1 BinType: -1 DevType: -1
Offset:-1 Size: -1 FOTA: remained
This unknown format unknown partition resides on the CP unknwon. The partition will expand to fill the remainder of the unknwon.
--- Entry #30 ---
ID: -1 Partition Name: remained
Filename: remained
Block Size: -1 (-512 B)
Block range: -1 - -3 (hex 0xffffffff - 0xfffffffd)
PartType: -1 FilesystemType: -1 BinType: -1 DevType: -1
Offset:-1 Size: -1 FOTA: remained
This unknown format unknown partition resides on the CP unknwon. The partition will expand to fill the remainder of the unknwon.
--- Entry #31 ---
ID: -1 Partition Name: remained
Filename: remained
Block Size: -1 (-512 B)
Block range: -1 - -3 (hex 0xffffffff - 0xfffffffd)
PartType: -1 FilesystemType: -1 BinType: -1 DevType: -1
Offset:-1 Size: -1 FOTA: remained
This unknown format unknown partition resides on the CP unknwon. The partition will expand to fill the remainder of the unknwon.
--- Entry #32 ---
ID: -1 Partition Name: remained
Filename: remained
Block Size: -1 (-512 B)
Block range: -1 - -3 (hex 0xffffffff - 0xfffffffd)
PartType: -1 FilesystemType: -1 BinType: -1 DevType: -1
Offset:-1 Size: -1 FOTA: remained
This unknown format unknown partition resides on the CP unknwon. The partition will expand to fill the remainder of the unknwon.
After
Code:
--- Entry #29 ---
ID: 70 Partition Name: PGPT
Filename: pgpt.img
Block Size: 34 (17.4kB)
Block range: 0 - 33 (hex 0x0 - 0x21)
FilesystemType: 1 PartType: 5 DevType: 2 BinType: 0
Offset:0 Size: 0 FOTA:
The PGPT partition, identified as partition number 70, is 17.4kB in size and carries a Basic format. This partition resides on the Data section of the AP EMMC. It identifies itself to Odin as pgpt.img.
--- Entry #30 ---
ID: 71 Partition Name: PIT
Filename: MSM8960.pit
Block Size: 16 (8.2kB)
Block range: 34 - 49 (hex 0x22 - 0x31)
FilesystemType: 1 PartType: 5 DevType: 2 BinType: 0
Offset:0 Size: 0 FOTA:
The PIT partition, identified as partition number 71, is 8.2kB in size and carries a Basic format. This partition resides on the Data section of the AP EMMC. It identifies itself to Odin as MSM8960.pit.
--- Entry #31 ---
ID: 72 Partition Name: MD5
Filename: md5.img
Block Size: 32 (16.4kB)
Block range: 50 - 81 (hex 0x32 - 0x51)
FilesystemType: 1 PartType: 5 DevType: 2 BinType: 0
Offset:0 Size: 0 FOTA:
The MD5 partition, identified as partition number 72, is 16.4kB in size and carries a Basic format. This partition resides on the Data section of the AP EMMC. It identifies itself to Odin as md5.img.
--- Entry #32 ---
ID: 73 Partition Name: SGPT
Filename: sgpt.img
Block Size: 33 (16.9kB)
Block range: 30777311 - 30777343 (hex 0x1d59fdf - 0x1d59fff)
FilesystemType: 1 PartType: 5 DevType: 2 BinType: 0
Offset:0 Size: 0 FOTA:
The SGPT partition, identified as partition number 73, is 16.9kB in size and carries a Basic format. This partition resides on the Data section of the AP EMMC. It identifies itself to Odin as sgpt.img.
Click to expand...
Click to collapse
@Benjamin Dobell may know something about this.
Can anyone share the file http://goo.im/devs/AdamOutler/libpitX/libpit-X-R917.jar? The link fails.
t2060079 said:
Can anyone share the file http://goo.im/devs/AdamOutler/libpitX/libpit-X-R917.jar? The link fails.
Click to expand...
Click to collapse
I'm looking for the same stuff. I think that the dev has relocated to here:
http://3of5.com/builds.casual-dev.com/files/libpit-X/
HTH, J
D*mnit...i just typed up this informative article to explain whats going on & then the ENTIRE thing got deleted
Please keep checking this post as i will gradually add back the info as i go...for now i will post the zips/files & steps I've taken up to this point along with any other knowledge that u need to know and thx to @sicarius128 for pointing out the release of the south american model
View attachment USALTE705_NG1_MODEM.zip
^T705M NG1 MODEM (Flashing this will enable the north american LTE frequencies...i have tested this myself & it DOES indeed work to change the bands)
View attachment STOCK705_NF7_MODEM.zip
^T705 NF7 MODEM (this will put u back on the stock radio if u need it...although it is labeled NF7 it is the same modem that is included with the newer NG2 as well)
IF ANYONE IS ACTUALLY ABLE TO CONNECT AFTER FLASHING THIS THEN PLEASE DONT JUST GET HAPPY AND RUN OFF BECAUSE I NEED ALL THE DETAILS I CAN GET...THX IN ADVANCE
if u enter the dial code *#2263# (if this doesnt work then try *#0011#...i will include a link below with navigation instructions to get to the band selection menu) then select "LTE BAND" both before & after then u will notice that those available have in fact changed from "1.3,5,7,8,20" which are the stock/rest of the world values to "1,2,4,5,7,17" which correspond to the correct USA frequencies...at this point the mod MAY very well be working for some users but unfortunately for me my device still wont connect to the lte network for whatever reason so i need testers to see if this is an exclusive issue to my tab/sim or are there other settings that need to be changed somewhere. Below i will list additional steps i have taken & document other pieces of the puzzle i have put together for those of u who are interested,,,i humblyrequest that any devs or other knowledgeable users PLEASE post with your wisdom so we can get this working
http://forum.xda-developers.com/galaxy-tab-s/help/unlock-aws-tab-s-8-4-lte-t2860001
^SERVICE MODE *#0011# NAVIGATION INSTRUCTIONS (please see post #2...there is an app called "advanced signal status" that makes this easier to access)
So...once i flashed the columbian modem & found that i still wasnt connecting to LTE even though the NA frequencies were in fact found in the aforementioned menu i tried a few more fixes. After doing some reading i ran across a file in the "system/etc" folder named "lteon_netlist.xml" which seems to contain an index of whitelisted lte networks from around the world & upon opening it i noticed that ALL of the north american companies were missing. i found the the file of the same name from the columbian rom & sure enough it included AT&T as well as t-mo & other domestic services. This almost SURELY seems to be an important part of the problem but even after replacing this file my problem persisted...i guess i should mention that i'm on straight talk with an ATT compatible sim & it may not be important but i tried my sim in a LG phone & it worked after i forced it to LTE . To further complicate things...it wouldnt work on an ATT branded note 3 & the sim card from the same note 3 wouldnt connect to lte on my device either even with proper apn settings
So with all of that said...a few more failed attempts i've made include the following
1. added various apn settings including KNOWN working values on other devices
2. deleted "persist.radio.lteon" from the location "data/property" or change its value from false to true
3. flashed the kernel from the colombian rom & even created an entire rom from the firmware in hope that some combination of the files it contained would cause it to connect...everything was fully functional after the fact but alas no LTE
4. did a REAL factory reset with the stock recovery which even erases the contents of the internal sd card
5. altered a note 2 zip which contains ATT csc files inside which interesting enough does change the device product code to T705NTSAATT according to the app "phone info" (links to zip & app below)
6. Used the band selection menu mentioned above to force lte bands only but not only does ths not work it desnt seem to survive a reboot either...i also used the app method to do the same (link below)
7. Last but not least...i have tried to flash the bootloader & YES i'm aware of how dangerous this is which is why i wont be uploading the zip here although i havent yet found a way to get it to overwrite which is one of the question i need answered below
View attachment lteon_netlist.zip
^LTEON_NETLIST.XML (this zip is NOT flashable because i was being lazy :silly:....unzip then replace the file in "system/etc" & dont forget to change permissions to 0644 or rw-r--r--)
View attachment CSC_705_ATT.zip
^ATT CSC (please be aware...this will show the csc version as N7100ATTDMB1 but doesnt seem to cause any issues)
https://play.google.com/store/apps/details?id=com.cc.signalinfo&hl=en\
^ADVANCED SIGNAL STATUS APP (used to determine your current network connection...can be used to force to a certain type or to enable/disable individual gsm/wcdma/lte bands
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en
^PHONE INFO (provides a ton of info about your device...including a list of all secret codes as well as a csc changer)
couple of quick questions for anyone who can provide answers or otherwise assist...thx in advance
1. @bentee20 @crzcraft does choosing the particular bands or lte only in fact force the mode on your devices...i'm aware when u use the app method that u will need to change the setting every boot. Just out of curiousity...could u guys post your location and device/rom details
2. @vovochka-s2 did u ever find a 705 pit file or can anyone else please provide one for us?
3. Directly related to issue 2...has anyone use hemidall to flash there tab & if so could u please list the steps as well as version u used
4. i dont expect any other users to attempt this at least until i can confirm it fixes things...CAN ANYONE PLEASE PROVIDE A PROVEN WAY OF FLASHING THE BOOTLOADER ON NEWER GALAXY DEVICES? It wont flash through odin do to security reasons (neither would the modem file file but it flashed fine using twrp)...i have tried installing it through recovery but after reboot nothing seems to have been changed according to the phone info app
the input of @UpInTheAir (particularly would like your opinion on #3 & #4 above...yeah i know bro but i'm so close & this is the level of desperation i have reached :laugh or @edan1979 would be welcome although i dont think either of u are actually in the states so im not sure how important this issue is to u if at all...to answer your question from the other thread a few weeks NO i 'm not aware of the exact location of the network selector list but i did notice that it disappears from settings after using the att csc zip so i might spend some time to track it down tonight even though i came across an easy way to change it back
@Hakams the above modem should fix your issue if u never figured it out...please report your results
Sorry, I'm not going to get involved with bootloaders, if you get that wrong, your device is in a permanent world of hurt. It is possible to flash with Odin and I remember CWM.zip from the SGS2 days. On some devices, once you upgrade, it is impossible to revert.
Kernel side:
There is option in kernel build .config file with various regions. I haven't yet looked at what it really does in any sort of depth. I think I remember some thresholds and such. Maybe also drivers specific to various regions. (incl. modem/mobile connectivity ??? )
Code:
CONFIG_TARGET_LOCALE_EUR=y
# CONFIG_TARGET_LOCALE_KOR is not set
# CONFIG_TARGET_LOCALE_USA is not set
# CONFIG_TARGET_LOCALE_DEMO is not set
I don't know if it will even compile, but will try later on if you wish ?
UpInTheAir said:
Sorry, I'm not going to get involved with bootloaders, if you get that wrong, your device is in a permanent world of hurt. It is possible to flash with Odin and I remember CWM.zip from the SGS2 days. On some devices, once you upgrade, it is impossible to revert.
Kernel side:
There is option in kernel build .config file with various regions. I haven't yet looked at what it really does in any sort of depth. I think I remember some thresholds and such. Maybe also drivers specific to various regions. (incl. modem/mobile connectivity ??? )
Code:
CONFIG_TARGET_LOCALE_EUR=y
# CONFIG_TARGET_LOCALE_KOR is not set
# CONFIG_TARGET_LOCALE_USA is not set
# CONFIG_TARGET_LOCALE_DEMO is not set
I don't know if it will even compile, but will try later on if you wish ?
Click to expand...
Click to collapse
I understand the risks & all i'm asking if u happen to know a sure-fire way then please pm me or something but i've already attempted odin, twrp & even dd with no results (of course this would be a last resort option...as more users present new info i'm sure i can find the patience to exhaust those possibilities before doing anything dumb)...as far as the kernel is concerned if its not too much trouble then PLEASE attempt to build one for us. I tried the one from the T705M but as i already stated above it flashed fine & was fully functional but didnt let me connect to LTE...one would assume those configurations would already be set since the frequencies are unlocked by default although i could see samsung using that as another way to keep those devices out of the american market so that they dont hurt domestic sales. I appreciate u chiming in & patiently await a test build of the USA enabled kernel...thx in advance
You won't know of a sure fire way until (if) it's successfully done. ...
If you want to proceed, I can't help with that as I haven't played with the BL for a long time and don't want to give wrong or outdated info. Different devices use different ways.
As I said, I won't get involved with the BL at all (publically or PM).
I will try and compile that kernel for you though.
PM sent:
kernel compiled
Code:
CONFIG_TARGET_LOCALE_USA=y
Fairly sure it won't do anytrhing, could only find threshold changes in source related to that config change.
Please be aware I haven't tested the kernel for boot. There is a CIFS patch I've implemented not in v1.5.
The "problem" could actually be on the hardware side. I've owned a I9100T and I9300T. I remember that modems on ther "T" models were optimised for 850 MHz 3G band. The only difference was (the software) modem, and some internal jumper (recalling fading memory here.....)
Ha, found a thread regarding the SGS3 jumper,......... http://forum.xda-developers.com/galaxy-s3/help/samsung-galaxy-s3-19300t-t1688836/page2
My point is, that there could be hardware changes needed as well
I cant do anything as well. its out of my league.
This would be very useful, maybe US users raise some funds to pay for a test device for a recognized developer to see if this could be implemented?
However if it's a one-shot and the phone/tablet is permanently useless, than it might not be worth it.
PIT
I created a PIT file for SM-T705 16GB through heimdall. Cannot for the life of me get firmware to flash with the PIT (re-partition enabled), checked the PIT with PIT Magic on Windows and seems OK, but then again, unfortunately I don't know a great deal about it. I tried with Odin 1.85, 3.07, 3.09. All setup is Ok because I can flash the firmware without.
There was a risk of hard brick,......... but I was "in the mood". That mood is changing again though .............
edan1979 said:
I cant do anything as well. its out of my league.
Click to expand...
Click to collapse
It's ok bro...thx for checking in
Satorikn said:
This would be very useful, maybe US users raise some funds to pay for a test device for a recognized developer to see if this could be implemented?
However if it's a one-shot and the phone/tablet is permanently useless, than it might not be worth it.
Click to expand...
Click to collapse
Although I would prefer not to I'm willing to risk a brick of my own personal device & just file an insurance claim if so...hopefully we will have a breakthrough before then
UpInTheAir said:
I created a PIT file for SM-T705 16GB through heimdall. Cannot for the life of me get firmware to flash with the PIT (re-partition enabled), checked the PIT with PIT Magic on Windows and seems OK, but then again, unfortunately I don't know a great deal about it. I tried with Odin 1.85, 3.07, 3.09. All setup is Ok because I can flash the firmware without.
There was a risk of hard brick,......... but I was "in the mood". That mood is changing again though .............
Click to expand...
Click to collapse
Could u PLEASE upload or pm me the pit file kind sir...don't know if u tried the custom kernel yourself but even though it was a no go I definitely appreciate the effort
@UpInTheAir
hate to waste a post so hopefully u will see this bat signal...which drivers/process did u use to get heimdall to even initiate the flashing process? I can get it too recognize the device fine but once I press start I have various errors depending upon which driver i choose in zdiag...starting to wonder if it's because I'm on x64 Windows 8 or what?
THEDEVIOUS1 said:
It's ok bro...thx for checking in
Although I would prefer not to I'm willing to risk a brick of my own original device & just file an insurance claim if so...hopefully we will have a breakthrough before then
Could u PLEASE upload or pm me the pit file kind sir...don't know if u tried the custom kernel yourself but of course it was a no go but I definitely appreciate the effort
Click to expand...
Click to collapse
This is the heimdall PIT printout:
Entry Count: 24
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 21324
Unknown 4: 13641
Unknown 5: 12596
Unknown 6: 48
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 80
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 2046
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOTLOADER
Flash Filename: sboot.bin
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 34
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: -
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 50
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5HDR
Flash Filename: md5.img
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8192
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA0
Flash Filename: -
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 16384
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA1
Flash Filename: -
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 24576
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 65536
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: m9kefs1
Flash Filename: m9kefs1.bin
FOTA Filename:
--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 73728
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: m9kefs2
Flash Filename: m9kefs2.bin
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 81920
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: m9kefs3
Flash Filename: m9kefs3.bin
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 90112
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CARRIER
Flash Filename: carrier.img
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 98304
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.bin
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 114688
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 131072
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 151552
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: OTA
Flash Filename: -
FOTA Filename:
--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 172032
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CDMA-RADIO
Flash Filename: modem_cdma.bin
FOTA Filename:
--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 180224
Partition Block Count: 98304
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RADIO
Flash Filename: modem.bin
FOTA Filename:
--- Entry #16 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 14
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 278528
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TOMBSTONES
Flash Filename: tombstones.img
FOTA Filename:
--- Entry #17 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 15
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 286720
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TDATA
Flash Filename: tdata.img
FOTA Filename:
--- Entry #18 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 16
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 294912
Partition Block Count: 24576
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSDATA
Flash Filename: persdata.img
FOTA Filename:
--- Entry #19 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 17
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 319488
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RESERVED2
Flash Filename: -
FOTA Filename:
--- Entry #20 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 18
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 327680
Partition Block Count: 4894720
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img
FOTA Filename:
--- Entry #21 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 19
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 5222400
Partition Block Count: 409600
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img
FOTA Filename:
--- Entry #22 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 20
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 5632000
Partition Block Count: 471040
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img
FOTA Filename:
--- Entry #23 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 21
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 6103040
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USERDATA
Flash Filename: userdata.img
FOTA Filename: remained
I'm just going to give it one last shot..........
Edit: Failed again, stuck at "get PIT for mapping" using 3.07.
PM sent
@THEDEVIOUS1
Installed heimdall on Ubuntu 14.04 64bit ..... Just for your PIT
I didn't actually try flashing anything through heimdall though. Never have (yet).
Kept getting an error eventually download the PIT with device connected to the PC USB 3.0 port. ..
Edit2: Tried to flash PIT with heimdall, but no go. "ERROR: Failed to receive PIT file part response!" , obviuosly something wrong with the PIT. I tried via DD and managed to pull some sort of PIT (doesn't flash), because the count= & BS= no idea where to obtain this info. I'm sure it's device specific
Tester
I will test this tonight when I get home and report back.
Question: What are my chances I will have a successful flash? This may be an obvious question, but assume I will need to root my device first, right?
Device Model: SM-T705
Baseband version: T705ZHU1ANG2
Kernel version: 3.4.39-2290729 [email protected] #1
Build number: KOT49H T705ZHU1ANG2
jadid said:
I will test this tonight when I get home and report back.
Question: What are my chances I will have a successful flash? This may be an obvious question, but assume I will need to root my device first, right?
Device Model: SM-T705
Baseband version: T705ZHU1ANG2
Kernel version: 3.4.39-2290729 [email protected] #1
Build number: KOT49H T705ZHU1ANG2
Click to expand...
Click to collapse
I think the attachments do not exist (maybe taken off a while back)
mac231us said:
I think the attachments do not exist (maybe taken off a while back)
Click to expand...
Click to collapse
Oh man, that suxs! Is there anyway I can get it? I would really like to have my device work with US bands.
jadid said:
Oh man, that suxs! Is there anyway I can get it? I would really like to have my device work with US bands.
Click to expand...
Click to collapse
you might want to ask the OP..he maintains 2 roms one for tabpro and tab S..maybe more...so he is still active on these forums
mac231us said:
you might want to ask the OP..he maintains 2 roms one for tabpro and tab S..maybe more...so he is still active on these forums
Click to expand...
Click to collapse
Thanks, I will!
mac231us said:
I think the attachments do not exist (maybe taken off a while back)
Click to expand...
Click to collapse
not sure what happended...thx for making me ware they were missing
jadid said:
I will test this tonight when I get home and report back.
Question: What are my chances I will have a successful flash? This may be an obvious question, but assume I will need to root my device first, right?
Click to expand...
Click to collapse
the links have been fixed in the first post...thx for testing. i know its a lot but please be sure to read the ENTIRE op...long story short the file labeled USALTE705_NG1_MODEM.zip will in fact flash without problems and show the north american bands when u got to the network menu but still no LTE yet on my personal device (with any luck u will flash this and LTE will automagically work...proving that there is just something set up wrong on my device) The only other zip in the op that i believe to be significant is the lteon_netlist.zip which contains a whitelist of LTE carriers including the north american providers (if u check it against the stock file u will see that they are in fact missing)
while i'm posting i would like to make another plea for some help from other users/devs...can anyone PLEASE tell me a step by step definite method of geting heimdall to recogize this device read the pit/flash files on windows OR linux?!
@pinsb
i posted the band enabling info in thie op of this thread as well as another in the question section...just wanted to get your attention as we may be able to help each other out. So...i'm assuming u were able to achieve root and i was just wondering what chipset the T805W variant uses? (i'm assuming the exynos but i may be mistaken). Most people are not aware but the original samsung tab that tmobile sold could in fact be flashed with the european modem to enable voice calls ( @oldblue910 ...i was gonna bring this to your attention in the other thread but due to the locked bootloader on the ATT version the info was almost irrelevent)! So with all of that said heres what i'm thinking...u MAY be able to flash the brazillian modem which makes calls and also has the north american lte frequencies! Although it would be less impressive...the international modem MAY enable calls with the obvious caveat being that u wouldnt be getting LTE speeds
@jadid
i apologize but i assumed anyone doing this would already have done both...technically all u need to do is flash using cwm/twrp but i would go ahead and root as well
THEDEVIOUS1 said:
not sure what happended...thx for making me ware they were missing
the links have been fixed in the first post...thx for testing. i know its a lot but please be sure to read the ENTIRE op...long story short the file labeled USALTE705_NG1_MODEM.zip will in fact flash without problems and show the north american bands when u got to the network menu but still no LTE yet on my personal device (with any luck u will flash this and LTE will automagically work...proving that there is just something set up wrong on my device) The only other zip in the op that i believe to be significant is the lteon_netlist.zip which contains a whitelist of LTE carriers including the north american providers (if u check it against the stock file u will see that they are in fact missing)
while i'm posting i would like to make another plea for some help from other users/devs...can anyone PLEASE tell me a step by step definite methof of geting heimdall to recogize this device read the pit/flash files on windows OR linux?!
@pinsb
i posted the band enabling info in thie op of this thread as well as another in the question section...just wanted to get your attention as we may be able to help each other out. So...i'm assuming u were able to achieve root and i was just wondering what chipset the T805W variant uses? (i'm assuming the exynos but i may be mistaken). Most people are not aware ( @oldblue910 ...i was gonna bring this to your attention in the other thread but due to the locked bootloader on the ATT version the info was almost irrelevent) but the original samsung tab that tmobile sold could in fact be flashed with the european modem to enable voice calls! So with all of that aid heres what i'm thinking...u MAY be able to flash the brazillian modem which makes calls and also has the north american lte frequencies! Although it would be less impressive...the international modem MAY enable calls with the obvious caveat being that u wouldnt be getting LTE speeds
Click to expand...
Click to collapse
Thank you I appreciate you taking the time to fix the links I download the files. Question: I need to have my device rooted first, right? and do I flash this in odin or cw/twrp? I didn't see any of these details in op.
Thanks again!
THEDEVIOUS1 said:
@pinsb
i posted the band enabling info in thie op of this thread as well as another in the question section...just wanted to get your attention as we may be able to help each other out. So...i'm assuming u were able to achieve root and i was just wondering what chipset the T805W variant uses? (i'm assuming the exynos but i may be mistaken). Most people are not aware but the original samsung tab that tmobile sold could in fact be flashed with the european modem to enable voice calls ( @oldblue910 ...i was gonna bring this to your attention in the other thread but due to the locked bootloader on the ATT version the info was almost irrelevent)! So with all of that said heres what i'm thinking...u MAY be able to flash the brazillian modem which makes calls and also has the north american lte frequencies! Although it would be less impressive...the international modem MAY enable calls with the obvious caveat being that u wouldnt be getting LTE speeds
Click to expand...
Click to collapse
No such luck.
I was looking at buying one on E-Bay UK and was trying to gather info before deciding to purchase. However there's now crazy (IMHO) bidders who have bid it up to over £300 ($480) so not worth the effort now, although whether they'll pay and whether they understand what they're really buying is of course another issue. Auction closes tomorrow on E-Bay UK and isn't too hard to find.
Sorry I can't be more helpful.
--
THEDEVIOUS1 said:
not sure what happended...thx for making me ware they were missing
the links have been fixed in the first post...thx for testing. i know its a lot but please be sure to read the ENTIRE op...long story short the file labeled USALTE705_NG1_MODEM.zip will in fact flash without problems and show the north american bands when u got to the network menu but still no LTE yet on my personal device (with any luck u will flash this and LTE will automagically work...proving that there is just something set up wrong on my device) The only other zip in the op that i believe to be significant is the lteon_netlist.zip which contains a whitelist of LTE carriers including the north american providers (if u check it against the stock file u will see that they are in fact missing)
l
Click to expand...
Click to collapse
I rooted my device and installed TWRP 2.8.1.0 I then flash the USALTE705_NG1_MODEM.zip which installed successfully. I inserted my T-Mobile SIM.
No LTE
I then accessed the Band configuration via the *#0011# code followed the instructions and selected the T-Mobile bands B4 & B17 in the LTE section. and WCDMA: 1900
No LTE
Next attempt was to copy the lteon_netlist.zip file to the system/etc folder and set the permission to 0644 or rw-r--r (note: this file did not exist prior to copying)
No LTE
What else should I try and am I missing anything else?