Before you follow all this steps, remember:
THIS IS NOT A HOW TO...!!!!!!!!!!!
Remember, that i'm asking to other more experienced users if this method should work, so, i haven't tried it yet
Hi, im trying to change the ROM of my galaxy s3 mini from Linux using heimdall, and i've doubts.
My current ROM:
build number: JR003H.I8190XXALL2
kernel version: 3.0.31-639956
android version: 4.1.1
baseband version: I8190XXALL2
New ROM:
http://forum.xda-developers.com/showthread.php?t=2104638
build number: JZO54K.I8190XXAMA1
kernel version: 3.0.31 - 790526
baseband version: XAAMA1 [EUROPE]
android version: 4.1.2
ROM STATUS: NON-WIPE
FIRMWARE STATUS AFTER FLASH: OFFICIAL
BINARY COUNT AFTER FLASH: NONE
In this thread, the user arturaz explained how to change the ROM using heimdall:
http://forum.xda-developers.com/showthread.php?t=2066668
But, he used a ROM with the same baseband than the old one. As you see, I have an issue: my current baseband version is different than the new one. So, i'll have to flash more files, and thats my trouble. Because I'm not sure about that, and I need someone to tell me if my reasoning is ok.
Lets go!
1. Decompress all files of my ROM. I've stored then in my home:
/home/ali3n//galaxys3/I8190XXAMA1_I8190OXAAMA1_4.1.2_rooted_by_infected_/
Code:
[COLOR="Blue"]$ cd /home/ali3n//galaxys3/I8190XXAMA1_I8190OXAAMA1_4.1.2_rooted_by_infected_/[/COLOR]
Code:
[COLOR="Blue"]$ ls -1a[/COLOR]
boot.img
cache.img
hidden.img
modem.bin
STE_boot1.img
STE_boot2.img
system.img
So, those are the files that I've to look for in my current pit file.
I put my phone in download mode, connect to my pc and:
2. ¿Does heimdall detect my device?
Code:
[COLOR="Blue"]$ sudo heimdall detect[/COLOR]
Device detected
3. Lets see my pit file to look for the files needed in the new ROM version and which partitions are used for each of them:
Code:
[COLOR="Blue"]$ sudo heimdall print-pit[/COLOR]
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver... -----> (i'm not sure about if should I continue)
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
PIT file download sucessful
Entry Count: 25
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 28519
Unknown 4: 25708
Unknown 5: 28261
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0
--- 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
Ending session...
Rebooting device...
Re-attaching kernel driver...
4. flashing the device and installing the rooted ROM
Once I've located which Partition Identifier is associated to each of the new ROM files:
Code:
[COLOR="Blue"]$ sudo heimdall flash --3 STE_boot1.img --4 STE_boot2.img --14 modem.bin --18 boot.img --20 system.img --21 cache.img --22 hidden.img[/COLOR]
I think thats all. ¿It's all right? ¿Does anybody do it before? I don't know if should i do anything else before flashing the device, and i wanna know your opinion about if this is the right way.
Thank you!
In Linux, Heimdall doesn't read download mode but ADB reads normally. In Win7, ADB doesn't read but Odin reads download mode.
Sent from Spaceball One.
blackknightavalon said:
In Linux, Heimdall doesn't read download mode but ADB reads normally. In Win7, ADB doesn't read but Odin reads download mode.
Sent from Spaceball One.
Click to expand...
Click to collapse
Thank you for your answer, but I don't know what you mean blackknightavalon. In this thread a user explains how to change the ROM using heimdall in linux:
http://forum.xda-developers.com/showthread.php?t=2066668
My issue, is that the new ROM uses a different baseband version than the current one. So I don't know if the procedure that I've described, based on the experience of arturaz could work.
Thank you!
nslookup said:
In this thread a user explains how to change the ROM using heimdall in linux:
http://forum.xda-developers.com/showthread.php?t=2066668
My issue, is that the new ROM uses a different baseband version than the current one.
Click to expand...
Click to collapse
Probably too late for you, but maybe still useful for further heimdall users...
I guess what arturaz meant, was: Since he had a "XXALJL" build on his phone before he explicitly chose the same build but rooted. And further, since the baseband was the same, all he needed to re-flash was the system partition in order to get the "su" binary where it belongs. That's a Linux habitat: Only change the least that's needed when everything else is already there.
Maybe arturaz is willing to confirm my interpretation.
However, after reading his posting I went the same lane. My Mini had the same build and I've rooted it exactly as described. Then I installed ROM-manager and with the help of su (aka "root"), CWM. Using this I installed BenzROM, which has a different build. But since the entire image was replaced, the baseband fits to it.
And it works
Hope that helps.
I have a Sony Xperia TX. It randomly crashes and it reads - Phone crashed please wait for the crash reports to be saved.
it also say Hardware Watchdog crash stored on internel sdcard.
I am posting my crash reports from the CrashDump folder.
rdlog_init() created temp log file: /hhVMYg
[E] Could not open VT /dev/tty0: "No such file or directory"
Framebuffer initialized: 720x1280, 16bpp, 1.8MB
Setting backlight [/sys/class/leds/lcd-backlight_1/brightness] intensity to 255 (masked to 255)
Setting backlight [/sys/class/leds/lcd-backlight_2/brightness] intensity to 255 (masked to 255)
[E] Failed to open /sys/class/timed_output/vibrator/enable: No such file or directory
RamdumpV3 app. Version: 1.0.A.0.57
Loading configuration from conf.xml
adding 1 mount point(s)
Mount of /dev/block/by-name/SDCard on /YMogkv with file system ext4 returned: SUCCESS
DUMP /YMogkv /dev/block/by-name/SDCard 179:15 ext4 READY
Cleaning up permission problems for CrashDump
Unable to open RTC device
No rtc time
Creating /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000 directory
[W] Failed to create /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000, retrying... No such device
Creating /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0 directory
ramdump log created at "/YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0/ramdump.log"
Updating /YMogkv/CrashDump/crashinfo
opened memory device node /dev/mem (3) in O_RDWR | O_SYNC mode
Verify config
Reading cmdline file /proc/cmdline:
* Found: startup=6a58c
* Found: warmboot=6a594
* Found: androidboot.serialno= CB5A1JYRHT
RestartReason=0xabadbabe, restartReasonType=1
No buildinfo found, fallback to crash-notes.
Storing kernel log to: /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0/ramdump_system.log
Searching linux area 12 (0x80200000, 0x8d00000) for magic 0xCAFEBABE.
[W] Default build id checksum! Early kernel crash?
Found build info in crash notes: 7.0.A.3.193\hayabusa\userdebug
Found crash notes for crashing CPU! Crashing process:
[W] Skipping ram console search, crash type is 1
RESTART_REASON: 0xABADBABE (Hardware watchdog)
Creating /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0/ramdumpinfo
HWWD but can't read /proc/rdtags/addr_scm_regsave from rdtags: errno=2 <No such file or directory>
HWWD using hardcoded physical addr 0x2a03f658
CPU registers dump addr (phy) 0x00000000={0xea000006, 0xea000060, 0xea000063, ...}
HWWD found but no TZBSP_DUMP_CTX_MAGIC (found 0xea000006 expected 0x44434151)
RDTAG_DIR not set for this platform! Skipping rdtags dump!
Creating /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0/productinfo
Creating dump file: /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0/tlcore
Platform: blue
Dump areas:
( 0) address=0x0006206c size=0x00000004 flags=0x00006000 name: WDT Reset... success!
( 1) address=0x09000000 size=0x00008000 flags=0x0000a000 name: MDSP Ram A... success!
( 2) address=0x09200000 size=0x00008000 flags=0x0000c000 name: MDSP Ram B... success!
( 3) address=0x09400000 size=0x0000f800 flags=0x0000e000 name: MDSP Ram C... success!
( 4) address=0x12000000 size=0x0002c000 flags=0x00010008 name: SPS RAM... success!
( 5) address=0x12040000 size=0x00004000 flags=0x00012000 name: SPS Buff RAM... success!
( 6) address=0x12800000 size=0x00008000 flags=0x00014000 name: SPS Pipe Mem... success!
( 7) address=0x28400000 size=0x00020000 flags=0x00016008 name: Lpass Memory... success!
( 8) address=0x2a000000 size=0x00010000 flags=0x00018008 name: System IMEM-A... success!
( 9) address=0x2a03f000 size=0x00001000 flags=0x0001c000 name: System IMEM-C... success!
(10) address=0x38000000 size=0x04000000 flags=0x00020008 name: SMI CS0... success!
(11) address=0x80000000 size=0x00200000 flags=0x00080088 name: EBI1_CH0_CS0(SMEM)... success!
(12) address=0x80200000 size=0x08d00000 flags=0x00080028 name: EBI1_CH0_CS0(LINUX)... success!
(13) address=0x88f00000 size=0x00100000 flags=0x00080008 name: EBI1_CH0_CS0(APPSBL)... success!
(14) address=0x89000000 size=0x04400000 flags=0x00080018 name: EBI1_CH0_CS0(Modem Q6 SW)... success!
(15) address=0x8d400000 size=0x00600000 flags=0x00080018 name: EBI1_CH0_CS0(Modem Q6 FW)... success!
(16) address=0x8da00000 size=0x01800000 flags=0x00080008 name: EBI1_CH0_CS0(LP_Audio_SS)... success!
(17) address=0x8f200000 size=0x00500000 flags=0x00080008 name: EBI1_CH0_CS0(WConnect_SS)... success!
(18) address=0x8f700000 size=0x00080000 flags=0x00080008 name: EBI1_CH0_CS0(TZ Image)... success!
(19) address=0x8f780000 size=0x00080000 flags=0x00080008 name: EBI1_CH0_CS0(Reserved)... success!
(20) address=0x8f800000 size=0x00300000 flags=0x00080008 name: EBI1_CH0_CS0(FS Cache)... success!
(21) address=0x8fb00000 size=0x00300000 flags=0x00080008 name: EBI1_CH0_CS0(RAM EFS)... success!
(22) address=0x8fe00000 size=0x00100000 flags=0x00080008 name: EBI1_CH0_CS0(SPS Image)... success!
(23) address=0x8ff00000 size=0x00100000 flags=0x00080008 name: EBI1_CH0_CS0(SBL3)... success!
(24) address=0x90000000 size=0x10000000 flags=0x00080028 name: EBI1_CH1_CS0(LINUX)... success!
(25) address=0xa0000000 size=0x10000000 flags=0x00100028 name: EBI1_CH0_CS1(LINUX)... success!
(26) address=0xb0000000 size=0x10000000 flags=0x00100028 name: EBI1_CH1_CS1(LINUX)... success!
(27) path=/dev/msm_etb_boot flags=0x00024008 name: ETB... Read from /dev/msm_etb_boot: 16384, written to dump: 1530
success!
(28) cmdlineParam=semcandroidboot.rpmcoderamcopy, address=0x00020000 size=0x00000000 flags=0x00002008 name: RPM Code RAM... Found cmdline specified dump area (semcandroidboot.rpmcoderamcopy)
Reading cmdline file /proc/cmdline:
* Found: semcandroidboot.rpmcoderamcopy=
cmdLine area [email protected],0x20000
addr = 0x88f00000 size = 147456 orgAddr = 0x20000
success!
(29) cmdlineParam=semcandroidboot.rpmregistercopy, address=0x0002e000 size=0x00000000 flags=0x00004000 name: RPM Registers... Found cmdline specified dump area (semcandroidboot.rpmregistercopy)
Reading cmdline file /proc/cmdline:
* Found: semcandroidboot.rpmregistercopy=
cmdLine area [email protected],0x2E000
addr = 0x88f24000 size = 104 orgAddr = 0x2e000
success!
(30) cmdlineParam=semcandroidboot.rpmmsgramcopy, address=0x00108000 size=0x00000000 flags=0x00008000 name: RPM Msg RAM... Found cmdline specified dump area (semcandroidboot.rpmmsgramcopy)
Reading cmdline file /proc/cmdline:
* Found: semcandroidboot.rpmmsgramcopy=
cmdLine area [email protected],0x108000
addr = 0x88f24100 size = 24575 orgAddr = 0x108000
success!
Updating /YMogkv/CrashDump/Crash-YMD-HMS-19000100-000000_0/ramdumpinfo
Ramdump finished in 154s
Ramdump done! type: 1, name: , result: RAMDUMP_RESULT_OK (00)
SD card free space: 8495 MB
Closing graphics and flushing log files
Setting backlight [/sys/class/leds/lcd-backlight_1/brightness] intensity to 0 (masked to 0)
Setting backlight [/sys/class/leds/lcd-backlight_2/brightness] intensity to 0 (masked to 0)
[E] Could not open VT /dev/tty0: "No such file or directory"
Can anyone help me fix this problem?
Go on ,please try to help us help you.
Rooted?
Bootloader unlocked? If so which kernel?
Stock ROM? If so which FW?
Custom ROM? If so which ROM and version.
What did you do to the phone prior to this happening?
gregbradley said:
Go on ,please try to help us help you.
Rooted?
Bootloader unlocked? If so which kernel?
Stock ROM? If so which FW?
Custom ROM? If so which ROM and version.
What did you do to the phone prior to this happening?
Click to expand...
Click to collapse
Not rooted
Bootlocker is not unlocked
The phone is out of the box and i did not change any ROM settings or Rooted it. Nothing has been changed.
I was surfing my gallery when this first happened.
after that it was like 2 to 3 times a day
[MOD][GUIDE]Partition your internal SD for better App management 16GB & 32GB Models!
***************************************************************************************************************
UPDATE 19th July
I have added my donation details to my profile, following a request from @A-S who wished to donate and request a build.
I will always build for people, but he really wanted to donate so I set up the link!
You may thank him for the new versions he requested if they suit you! 10gb & 12gb now available!
32gb Model now supported! First tested and verified 6gb Data version attached, ask if you wish for different partition sizes! !
Beware #1 - Preload moddified version are NOT suitable for Samsung Stock Roms!
Beware #2 - Pre-Load moddified versions are for custom roms that do not use pre-load area! Please post on the respective thread for your rom and ask the author the question prior to using these versions if you are unsure! (I can tell you that SlimRoms & Cyanfox do not use preload, at present at least)
Beware #3 - If you want to go back to stock rom, you just need to flash my standard edition pit files, easy!
***************************************************************************************************************
Increase your data application partition and set your device free!
Are you bored of having to move apps to SD?
Bored of facing a stock issue of not even being able to move apps to your internal SD?
This thread will help you, currently only for n7000 16gb Model only.[/COLOR]
GUIDE - The usual rules apply, You will:
IMPORTANT: Please backup all your photos, videos and other important stuff on your PC, in the cloud or somewhere else where it is safe, as all your stuff on your internal SD card will be deleted!
1) Run compatible version of Odin, put your phone in to download mode (vol down/home/power button) and connect to PC via USB
2) Tick re-partition box
3) Click PIT button and select the pit file of your desired app partition size.
4a) Click PDA and select your stock official samsung jellybean rom - Edit- please remember if you use a rom that is not native to your region, it would be wise to flash the appropriate radio modem afterwards to ensure you get the signal strength you'd expect
4b) OR Flash your persnonal choice of kernel in *.tar format and pit file, reboot to CWM ( power button/vol up/home button) and install new rom or restore nandroid and boot as normal and skip to number 9 in this guide
5) Flash and wait for reboot
6) Let the phone reboot and wait until the android chap finishes his spinny wire ball belly animation and then remove the battery and do a factory reset using the usual power/vol up/ home trick.
7) Let it boot so you can check that you are happy with the result. ( I didn't, but you might want to)
8) Now flash your chosen rooted kernel and either stick with stock rom or enter CWM and flash your own custom rom.
9) When your phone boots, you may get a notification to format usb storage, say yes if prompted! If it that fails, connect you phone to your PC and format the the internal sd card manually.
10) Remember that Android likes automatically deciding where apps go, so sometime it tries to put stuff to SD itself (app requests it), it is worthwhile checking your installed apps to makes sure they went to internal app partition, you can tell this by either:
a) Look in Titanium back up, go to the move/integrate section and see if any apps show as moveable from SD to internal, if so run the batch process to put them on your nice new app partition, otherwise you may have issues running those apps.
b) If you don't have Titanium (why not?) then check the harder way by looking at app manager and swipe to the right to look at SD app, sort by size and then individually move ones back to internal storage.
11) That easy! Here is a shot of my resulting app manager
Files attached to post including original pit in case you want it back to stock values!
Enjoy!
*****************************************************************
Thanks to @RivakDebbie for testing this pit file on his own N7000 :good:
Welcome to the N7000 @metalgearhathaway
Just as a matter of caution, an idea. Would you mind considering to add something like "please backup all your photos, videos and other important stuff on your PC, in the cloud or somewhere else where it is safe, as all your stuff on your internal SD card will be deleted!"
Thanks again for your contribution ?
Sent via GALAXY NOTE N7000 // KitKat
AA1973 said:
Welcome to the N7000 @metalgearhathaway
Just as a matter of caution, an idea. Would you mind considering to add something like "please backup all your photos, videos and other important stuff on your PC, in the cloud or somewhere else where it is safe, as all your stuff on your internal SD card will be deleted!"
Thanks again for your contribution ?
Sent via GALAXY NOTE N7000 // KitKat
Click to expand...
Click to collapse
Done, would thank you, but only 8 allowed, needs extending a little I reckon :good:
Works like a charme! Thank you, been waiting for this since I have my Note! You made my Day!
Pandur said:
Works like a charme! Thank you, been waiting for this since I have my Note! You made my Day!
Click to expand...
Click to collapse
Cool, pleased to be of service!
Nice to see positive results back so quickly :good:
Great
metalgearhathaway said:
Cool, pleased to be of service!
Nice to see positive results back so quickly :good:
Click to expand...
Click to collapse
BUT your Instruction 4b dosnt work for me, CM11 told me some thing like Device Auto is not supported... after flashing a complete Sammy-ROM as instructed in 4a evrything works fine!
Pandur said:
BUT your Instruction 4b dosnt work for me, CM11 told me some thing like Device Auto is not supported... after flashing a complete Sammy-ROM as instructed in 4a evrything works fine!
Click to expand...
Click to collapse
Cheers for letting me know this.
To check, did you then follow 4a and get stock rom on and then upgrade to cm11 afterwards and all worked? I assume so?
Please confirm that and I'll update OP for CM/KK users
Thanks. Just tried it and re-partitioning is done very well.
metalgearhathaway said:
Cheers for letting me know this.
To check, did you then follow 4a and get stock rom on and then upgrade to cm11 afterwards and all worked? I assume so?
Please confirm that and I'll update OP for CM/KK users
Click to expand...
Click to collapse
Yes, let the SammyROM Boot, Format internal SD and then install CM
Gesendet von meinem GT-N7000 mit Tapatalk
Amazing! Simply works. Big THANKS OP.
With a new & better custom TW custom ROM (Arya V4) & a reborn C.O.H.-based kernel (Forrest-Helloworld-Make), the only missing thing in our N7000 is a dual boot using the latest kernels & CWM recovery.
Wow, thanks a lot for this!
Is there a chance though that you could remove (or decrease the size) of the preload partition? A lot of us use AOSP and that doesn't even use preload so that space is wasted.
Also, I understand if I want to go back to the default partition layout I need only flash the stock pit file? just to be sure
XxPixX said:
Wow, thanks a lot for this!
Is there a chance though that you could remove (or decrease the size) of the preload partition? A lot of us use AOSP and that doesn't even use preload so that space is wasted.
Also, I understand if I want to go back to the default partition layout I need only flash the stock pit file? just to be sure
Click to expand...
Click to collapse
Yes, that should be the case by flashing stock or one of my standard modded ones.
I could decrease the preload, where would you want the regained space placing?
Only thing is, it is tested at your risk, I've never played with the preload, so anything may happen, it will be out of my control.
Let me know more and confirm you are happy with the risk.
metalgearhathaway said:
Yes, that should be the case by flashing stock or one of my standard modded ones.
I could decrease the preload, where would you want the regained space placing?
Only thing is, it is tested at your risk, I've never played with the preload, so anything may happen, it will be out of my control.
Let me know more and confirm you are happy with the risk.
Click to expand...
Click to collapse
Hmmm, perhaps in the future then? Since I started flashing ROMs over a year ago I have never been able to stay on one for more than a week, but I have been running this last one for a month now so I am rather resentful to re-partitioning the device.
I also found this:
if you're running an AOSP flavor of android you can get rid of the UMS partition and the HIDDEN one (/preload). Keep in mind the sum of block size and block count of the #12 UMS partition must be exactly the number in the block size of the #13 HIDDEN partition (or the DATAFS must end on the last block of the HIDDEN partition if you're getting rid of the last two partitions).
Click to expand...
Click to collapse
XxPixX said:
Hmmm, perhaps in the future then? Since I started flashing ROMs over a year ago I have never been able to stay on one for more than a week, but I have been running this last one for a month now so I am rather resentful to re-partitioning the device.
I also found this:
Click to expand...
Click to collapse
Yup, I know about the blockcount and being careful with my sums. It's surprisingly simple to mod the the pit file using pitmagic. I think the only reason people have took to my pit files, is because I can count pretty well and use a calculator
So I can do one for you and submit the code for you to read, its pretty straight forward to read, you can then choose if you fancy trying it out.
Here is my output the pit file current hosted for n7000 users, I have highlight in red those that are changed for the hosted version, and in green I have highlighted FACTORYFS (about 800mb) which I think is your preload area, I need clarification however on that:
----------------------------------------------------------
PIT Magic v1.3.10 Copyright © Gaz 2012.
----------------------------------------------------------
Analysis for: Q1_20110914_16GB.pit
----------------------------------------------------------
----------------------------------------------------------
<<< Pit File Start >>>
----------------------------------------------------------
----------------------------------------------------------
<<< PIT File Header Information >>>
----------------------------------------------------------
Header Magic: 0x12349876 (4 Bytes)
Entry Count: 15 (4 Bytes)
----------------------------------------------------------
Dummy Data #1 (In String and Hexadecimal Format):
----------------------------------------------------------
String:
Hexadecimal: 00000000
----------------------------------------------------------
Dummy Data #2 (In String and Hexadecimal Format):
----------------------------------------------------------
String:
Hexadecimal: 00000000
----------------------------------------------------------
Dummy Data #3 (In String and Hexadecimal Format):
----------------------------------------------------------
String:
Hexadecimal: 00000000
----------------------------------------------------------
Dummy Data #4 (In String and Hexadecimal Format):
----------------------------------------------------------
String:
Hexadecimal: 00000000
----------------------------------------------------------
Dummy Data #5 (In String and Hexadecimal Format):
----------------------------------------------------------
String:
Hexadecimal: 00000000
----------------------------------------------------------
Dummy Data Length: (4 Bytes Per Block, 20 Bytes In Total.)
----------------------------------------------------------
Header Size: (28 Bytes)
----------------------------------------------------------
<<< PIT File Entries >>>
----------------------------------------------------------
----------------------------------------------------------
Entry Memory Address: 0x1C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 0
Attribute: 0 (READ ONLY)
Update Attribute: 0 (UNKNOWN)
Block Size:
Block Count:
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: GANG
Flash FileName: emmc.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0xA0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 1
Attribute: 0 (READ ONLY)
Update Attribute: 0 (UNKNOWN)
Block Size:
Block Count:
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash FileName: boot.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x124
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 4
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 8,192
Block Count: 40,960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash FileName: efs.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x1A8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 2
Attribute: 0 (READ ONLY)
Update Attribute: 0 (UNKNOWN)
Block Size: 49,152
Block Count: 2,560
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL1
Flash FileName: Sbl.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x22C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 3
Attribute: 0 (READ ONLY)
Update Attribute: 0 (UNKNOWN)
Block Size: 53,248
Block Count: 2,560
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL2
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x2B0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 5
Attribute: 0 (READ ONLY)
Update Attribute: 0 (UNKNOWN)
Block Size: 57,344
Block Count: 16,384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash FileName: param.lfs
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x334
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 6
Attribute: 0 (READ ONLY)
Update Attribute: 0 (UNKNOWN)
Block Size: 73,728
Block Count: 16,384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: KERNEL
Flash FileName: zImage
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x3B8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 7
Attribute: 0 (READ ONLY)
Update Attribute: 0 (UNKNOWN)
Block Size: 90,112
Block Count: 16,384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x43C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 8
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 106,496
Block Count: 409,600
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash FileName: cache.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x4C0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 9
Attribute: 0 (READ ONLY)
Update Attribute: 0 (UNKNOWN)
Block Size: 516,096
Block Count: 32,768
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEM
Flash FileName: modem.bin
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x544
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 10
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 548,864
Block Count: 1,744,896
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FACTORYFS
Flash FileName: factoryfs.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x5C8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 11
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 2,293,760
Block Count: 8,388,608
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DATAFS
Flash FileName: data.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x64C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 12
Attribute: 2 (STL)
Update Attribute: 0 (UNKNOWN)
Block Size: 10,682,368
Block Count: 19,038,208
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: UMS
Flash FileName: ums.rfs
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x6D0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 13
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 29,720,576
Block Count: 1,048,576
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash FileName: hidden.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x754
----------------------------------------------------------
Binary Type: 1 (COM. PROCESSOR)
Device Type: 1 (FILE / FAT)
Identifier: 9
Attribute: 0 (READ ONLY)
Update Attribute: 0 (UNKNOWN)
Block Size:
Block Count:
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name:
Flash FileName:
FOTA FileName:
----------------------------------------------------------
<<< Pit File End >>>
----------------------------------------------------------
Ok, may I request then a pit file with an increased (so that there is say ~20MB in the /preload partition AND about a 2 gig decrease in the sdcard size) data partition please? I will flash it hopefully on Saturday (I will have to make some backups and recompile Omni for myself and I haven't got much time until Saturday) and report back on how it goes
To make it clear:
/preload total size about 20MB (just in case - it's currently using 8.4MB for an unknown reason)
/storage/sdcard0 decreased by about 2GB
/data increase by 2068MB (about)
Also, I checked with "partition table" and it says the /preload partition is 503.9MB in size whereas the /system is 838.6 MB
{
"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"
}
Thanks a lot!
metalgearhathaway said:
and in green I have highlighted FACTORYFS (about 800mb) which I think is your preload area, I need clarification however on that:
Click to expand...
Click to collapse
I think preload is the hidden.img one which is about 512
FACTORYFS is the /system.
Pit file in OP works perfectly thanks
GT-N7000 cihazımdan Tapatalk 2 ile gönderildi
XxPixX said:
Ok, may I request then a pit file with an increased (so that there is say ~20MB in the /preload partition AND about a 2 gig decrease in the sdcard size) data partition please? I will flash it hopefully on Saturday (I will have to make some backups and recompile Omni for myself and I haven't got much time until Saturday) and report back on how it goes
To make it clear:
/preload total size about 20MB (just in case - it's currently using 8.4MB for an unknown reason)
/storage/sdcard0 decreased by about 2GB
/data increase by 2068MB (about)
Also, I checked with "partition table" and it says the /preload partition is 503.9MB in size whereas the /system is 838.6 MB
Thanks a lot!
Click to expand...
Click to collapse
Here you go then, I have made the following changes labelled and explain in RED:
Entry Memory Address: 0x5C8
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 11
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 1,392,640
Block Count: 8,388,608 - 4GB DATA PARTITION (CHANGED FROM 2GB)
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DATAFS
Flash FileName: data.img
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x64C
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 12
Attribute: 2 (STL)
Update Attribute: 0 (UNKNOWN)
Block Size: 9,781,248
Block Count: 20,946,944 - 10.5GB(ISH) INTERNAL SD CARD PARTITION
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: UMS
Flash FileName:
FOTA FileName:
----------------------------------------------------------
Entry Memory Address: 0x6D0
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 13
Attribute: 1 (READ / WRITE)
Update Attribute: 0 (UNKNOWN)
Block Size: 30,728,192
Block Count: 40,960 - 20MB PRELOAD AREA
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash FileName: hidden.img
FOTA FileName:
You are taking the risk by flashing, as explained, but if it works I will add thanks and credits for your bold testing and offer the community the option to claim half a gig of space back if they have no desire to use dual boot, or indeed that they understand the need to go back to stock based preload pit files should they ever want to return to official samung firmwares
EDIT: Tested it myself, does not work! It ignores the alterations to hidden image, so maybe something blocks me changing certain area's
Thanks very much! I will test it on Saturday.
I double checked the numbers and they seem to be alright, but I have a question about the name of the file:
I9100_4GB data - 20mb preload - 10.5 internal sd - UNTESTED.zip
Click to expand...
Click to collapse
Was that just a mistype or did you accidentally base it on the i9100 pit file?
XxPixX said:
Thanks very much! I will test it on Saturday.
I double checked the numbers and they seem to be alright, but I have a question about the name of the file:
Was that just a mistype or did you accidentally base it on the i9100 pit file?
Click to expand...
Click to collapse
Sorry, I deleted the file, yes it was i9100!
Plus i tested it out on my i9100, the preload area's appears to be untouchable, so I reckon its blocked from alteration sadly
EDIT: I might be wrong, I think I have sorted it, on i9100 atleast, let me test it out a bit longer and I'll report back with a file for you to use in the next couple of days!
EDIT 2: Here is a shot of the result on my i9100, so I will try for you on n7000 now!
MASTER CAUTION: This will wipe ALL data on the device!! Backup your stuff before proceeding. I nor XDA is responsible for loss of your memes!
Flashing last LineageOS microG rom (18.1), I lost data on french laposte (SFR) network. Telephon calls remains, but data don't. I decided to flash last stock ROM using heimdall to avoid Windows VM on my computer.
To succeed you need some information about ROM structure and process.
Firmware versionSome versions of stock ROM are just for upgrade and it doesn't contains all files nedeed. For example, I choose French XEF firmware for SM-G900F on sammobile.com
Last version 6.0.1 G900FXXS1CQD1 (2017-05-03) doesn't contain files as hidden.img.ext4, modem.bin... I nedeed.
I chose first 6.0.1 firmware witch contains all files : G900FXXU1CPE9 (2016-05-22)
Firmware contentFor SM-G900F, firmware ZIP file contains another archive file with .tar.md5 extension. This file is a normal tar file (I don't know why .md5 is added) which contains files to be flashed as PIT partitions
Structure is as below :
{
"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"
}
Firmware extractionWe need to extract 2 levels of archive to obtain files to be flashed.
unzip firmware archive (zip file) to obtain contained archive file (.tar.md5)
untar file to obtain files to be flashed.
Spoiler: To extract files using command line
Code:
unzip -d tarfile_dir <firmware_file>.zip;
cd tarfile_dir;
mkdir flash_files && tar xC flash_files -vf <firmware_tar_file>.tar.md5;
cd flash_files;
Convert sparses filesSome files with ".img.ext4" extension are not a dump of ext4 partition. System can't mount these file at boot if we flash them as this.
These file are "Android sparse image, version: 1.0". We need to convert il in raw ext4 image file with de command simg2img.
Under Debian this command is obtained from the package "android-sdk-libsparse-utils"
Spoiler: To install android-sdk-libsparse-utils paquet using command line
Code:
sudo -i
aptitude update && aptitude -y install android-sdk-libsparse-utils;
exit;
note : sudo command wait for user password to be root.
Use command "simg2img" to convert each file with ".img.ext4" extension.
Spoiler: To convert sparse files using command line
Code:
for i in *.ext4;
do
simg2img $i ${i/ext4/raw};
done;
We are now ready to flash files into the device.
Flashing the filesObtain PIT filesWe need to know in which partition we must flash each file. print-pit operation in heimdall command allow to obtain all information.
To reduce output lines we use grep command as below :
Code:
heimdall print-pit --no-reboot | grep -A1 "Partition Name"
Spoiler: Result of filtered print-pit command
Partition Name: APNHLOS
Flash Filename: NON-HLOS.bin
--
Partition Name: MODEM
Flash Filename: modem.bin
--
Partition Name: SBL1
Flash Filename: sbl1.mbn
--
Partition Name: DBI
Flash Filename: sdi.mbn
--
Partition Name: DDR
Flash Filename:
--
Partition Name: ABOOT
Flash Filename: aboot.mbn
--
Partition Name: RPM
Flash Filename: rpm.mbn
--
Partition Name: TZ
Flash Filename: tz.mbn
--
Partition Name: FSG
Flash Filename:
--
Partition Name: PAD
Flash Filename:
--
Partition Name: PARAM
Flash Filename: param.bin
--
Partition Name: EFS
Flash Filename: efs.img.ext4
--
Partition Name: MODEMST1
Flash Filename: nvrebuild1.bin
--
Partition Name: MODEMST2
Flash Filename: nvrebuild2.bin
--
Partition Name: BOOT
Flash Filename: boot.img
--
Partition Name: RECOVERY
Flash Filename: recovery.img
--
Partition Name: FOTA
Flash Filename:
--
Partition Name: BACKUP
Flash Filename:
--
Partition Name: FSC
Flash Filename:
--
Partition Name: SSD
Flash Filename:
--
Partition Name: PERSIST
Flash Filename: persist.img.ext4
--
Partition Name: PERSDATA
Flash Filename: persdata.img.ext4
--
Partition Name: SYSTEM
Flash Filename: system.img.ext4
--
Partition Name: CACHE
Flash Filename: cache.img.ext4
--
Partition Name: HIDDEN
Flash Filename: hidden.img.ext4
--
Partition Name: USERDATA
Flash Filename: userdata.img.ext4
--
Partition Name: PGPT
Flash Filename: pgpt.img
--
Partition Name: PIT
Flash Filename: MSM8974.pit
--
Partition Name: MD5
Flash Filename: md5.img
--
Partition Name: SGPT
Flash Filename: sgpt.img
With this result we can now construct heimdall flash command.
Flash commandWe need pass each file extracted from tar archive as parameter in flash command associated to its partition name.
CAUTION : Each sparse file (.ext4) must be replaced by associated converted file (.raw)
Here, my command, but you should verify that is correct in your case.
Code:
heimdall flash --SBL1 sbl1.mbn --DBI sdi.mbn --TZ tz.mbn --RPM rpm.mbn --ABOOT aboot.mbn --BOOT boot.img --RECOVERY recovery.img --APNHLOS NON-HLOS.bin --SYSTEM system.img.raw --HIDDEN hidden.img.raw --CACHE cache.img.raw --MODEM modem.bin --no-reboot
Note : --no-reboot option allows to verify and chain another command to re-flash a part (if errors or incomplete flash), but in my case device must be detected before each command. This is done unplugging and re-plugging USB device cable.
RebootTo reboot pass last command without --no-reboot option. For example :
Code:
heimdall print-pit
Firmware upgradeAll upgrade needed to obtain last version can be applied using similar method or by OTA upgrade.
Thanks for this detailed post on flashing with Heimdall. I experienced the exact problem that you mention concerning a LineageOS update breaking my mobile data (Internet). I would believe it to be the same update due to the time frame and symptoms. Everything else worked fine after the update that broke mobile data. The phone is similar to yours, but not identical. It is a Galaxy S5 G900V, using Verizon.
My first attempt with your steps failed on flashing the SYSTEM partition. I found that all of the converted .RAW images were failing. I tested just flashing the original .EXT4 files and they uploaded successfully.
After initially booting it up and going through the stock setup (connect to wireless, Google account setup, etc.), everything seemed to work OK. Unfortunately, after turning off the wireless, my mobile data (Internet browsing etc.) again failed. I did find that with the wireless turned off, the MMS messaging still works. I do not think this worked without wireless the last time I attempted to flash it back to stock.
I have been working with a few people to get this back to stock on this post if you are interested:
[ROM] [OFFICIAL] LineageOS 16.x ALL VARIANTS
* Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in...
forum.xda-developers.com
Were you able to get your G900F to work with mobile data without wifi after reverting to stock?
I have also been updating an additional G900V with the latest over the air LineageOS updates to see if the mobile data issue gets fixed. So far it still fails as of the most recent one released.
Thanks!