Alright, hope I won’t get RMM locked…
Edit : I got RMM locked… Connecting to wifi solved it
@piero my phone is stuck on some type of bootloop ! A blue screen with a android dude saying installing system update appear, and then the screen vanishes and command lines appear
Edit: Fortunately, I can still access download mode
Edit 2: I flashed CSC instead of HOME_CSC, Now that I’ve done it, it seems to be back to normal.
1 Like
Alright, I’ve flashed the first twrp “normal”. I’ve noticed that as soon as I flash twrp the phone gets stuck in a bootloop. Is it normal ?
you may need to use a .PIT file in Odin along samsung firmware to be straight stock
PIT = Partitionning i-something Table
it could be inside the BL or AP, you need to extract it ias i rember well and choosing some option in Odin,
search for instructions
The PIT file was located in the CSC file. I’ve successfully extracted it. However, I have 2 questions : Why would I use this file in order to use TWRP and not having a bootloop on the phone ? According to several forums, this is useful when your device is bricked or doesn’t have firmware and can lead a device to be broken if not flashed properly.
And, if this file is useful, where do I put it in Odin ? CSC ? AP ? BL ?
Could you explain to me what you think I should do and the current situation as you see it, as I’m beginning to get lost in this story? The issues I’ve spotted are the following:
-Flashing twrp while being under the stock rom leads to a bootloop
-System, data, cache or vendor CANNOT be mounted, neither by twrp nor by the system, which leads to a fatal error.
This makes the following steps unreproducible :
-Once TWRP is booted you first need to Mount > your /system, /vendor, /cache, and /data partition
AND MAYBE THE OTHER FILES FLASHED BEFORE. I did not look closely to the logs, but having the system not being able to mount partitions is threatening. What can I use to patch it ?
Edit : I’ve found a post for installing TWRP, maybe that will be worth trying…
https://xdaforums.com/t/recovery-official-twrp-3-3-1-0-for-galaxy-a8-2018.3818201/
same issue : you have modified the partitions table and the partition size to meet the “treble requirements”,
so your stock rom cannot find the proper partition names nor partition sizes nor physical emplacements
search instructions how to use the repartitioning feature in Odin, to reorganise stock partionning
.
do you speak french ?
All right, I’ll see what I can do. There’s a case to tick for repartitioning the phone in Odin. Dunno when to use it, probably while flashing the original firmwares… According to some forum, repartitioning comes with the so-called PIT file. However, I was able to boot to system after flashing the firmware. So i’m not sure that’s necessary.
Edit: forget what I said, I can’t mount Data in twrp, only cache, system and EFS.
I do.
1 Like
dans un smartphone il y plus de 20 partitions toutes de tailles differentes avec leur utilité bien que l’utillisateur ne le vois pas
laisses-moi quelques minutes…
clique ici pour voir la traduction en language comprehensible par les humain du fichier PIT d'un s4mini --> 27 partitions
Set cache size limit to 100.0 GB
antec@antec-p6-2038fr:~$ heimdall print-pit
Heimdall v1.4.2
Copyright (c) 2010-2017 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:
Donate | Glass Echidna
Initialising connection…
Detecting device…
Claiming interface…
Setting up interface…
Initialising protocol…
Protocol initialisation successful.
Beginning session…
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device’s PIT file…
PIT file download successful.
Entry Count: 28
Unknown 1: 1598902083
Unknown 2: 844251476
Unknown 3: 21325
Unknown 4: 14413
Unknown 5: 13113
Unknown 6: 48
Unknown 7: 0
Unknown 8: 0
— Entry #0 —
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: 122880
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEM
Flash Filename: NON-HLOS.bin
FOTA Filename:
— Entry #1 —
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 131072
Partition Block Count: 256
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL1
Flash Filename: sbl1.mbn
FOTA Filename:
— Entry #2 —
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 131328
Partition Block Count: 512
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL2
Flash Filename: sbl2.mbn
FOTA Filename:
— Entry #3 —
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 131840
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL3
Flash Filename: sbl3.mbn
FOTA Filename:
— Entry #4 —
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 132864
Partition Block Count: 4096
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: ABOOT
Flash Filename: aboot.mbn
FOTA Filename:
— Entry #5 —
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 136960
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RPM
Flash Filename: rpm.mbn
FOTA Filename:
— Entry #6 —
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 137984
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TZ
Flash Filename: tz.mbn
FOTA Filename:
— Entry #7 —
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 139008
Partition Block Count: 25600
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PAD
Flash Filename:
FOTA Filename:
— Entry #8 —
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 164608
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename:
FOTA Filename:
— Entry #9 —
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 180992
Partition Block Count: 27904
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img.ext4
FOTA Filename:
— Entry #10 —
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 208896
Partition Block Count: 6144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEMST1
Flash Filename: nvrebuild1.bin
FOTA Filename:
— Entry #11 —
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 215040
Partition Block Count: 6144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEMST2
Flash Filename: nvrebuild2.bin
FOTA Filename:
— Entry #12 —
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 221184
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:
— Entry #13 —
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 14
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 241664
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename:
— Entry #14 —
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 15
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 262144
Partition Block Count: 20480
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FOTA
Flash Filename:
FOTA Filename:
— Entry #15 —
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 16
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 282624
Partition Block Count: 14320
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BACKUP
Flash Filename:
FOTA Filename:
— Entry #16 —
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 17
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 296944
Partition Block Count: 6144
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FSG
Flash Filename:
FOTA Filename:
— Entry #17 —
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 18
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 303088
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SSD
Flash Filename:
FOTA Filename:
— Entry #18 —
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 19
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 303104
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSIST
Flash Filename: persist.img.ext4
FOTA Filename:
— Entry #19 —
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 20
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 319488
Partition Block Count: 24576
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSDATA
Flash Filename: persdata.img.ext4
FOTA Filename:
— Entry #20 —
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 21
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 344064
Partition Block Count: 3072000
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img.ext4
FOTA Filename:
— Entry #21 —
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 22
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 3416064
Partition Block Count: 409600
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img.ext4
FOTA Filename:
— Entry #22 —
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 23
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 3825664
Partition Block Count: 73728
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img.ext4
FOTA Filename:
— Entry #23 —
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 24
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 3899392
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USERDATA
Flash Filename: userdata.img.ext4
FOTA Filename: remained
— Entry #24 —
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 34
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PGPT
Flash Filename: pgpt.img
FOTA Filename:
— Entry #25 —
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
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: MSM8930.pit
FOTA Filename:
— Entry #26 —
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 72
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 50
Partition Block Count: 32
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5
Flash Filename: md5.img
FOTA Filename:
— Entry #27 —
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 73
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 15269855
Partition Block Count: 33
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SGPT
Flash Filename: sgpt.img
FOTA Filename:
Ending session…
Rebooting device…
Releasing device interface…
Huum, et en langage courant ? Je n’ai pas lu l’entiereté des 28 entrées car elles sont formatées de la meme façon. Si j’ai bien compris, il s’agit de repartitionner le telephone en utilisant ce fichier qui contient le nombre de partitions ? Vu que ce fichier est contenu dans le fichier CSC originellement, pourquoi ne pas simplement reflasher le firmware en cochant la case repartitioner ? Si je flash ce fichier PIT avec twrp installé et causant une bootloop, ça ne va pas me causer plus de probleme ?
De plus la bootloop n’est pas causé par treble (meme si le probleme mount oui) puisqu’il avait deja lieu quand j’ai recu le telephone sous stock os et que j’ai installé TWRP. Je voudrais reussir à savoir quel comportement du telephone est normal ou anormal que je sache quels trucs sont problematiques et doivent etre réglés.
Merci d’avance !
I don’t know how to use the PIT file.
I just done it one time some years ago,
I can’t search for now…
@aibd your are good at searching over the “samsung Tips websites”
As I understand it my answer to
why not simply reflash the firmware by checking the repartitioner box?
would be ok … try that.
Say one changes the partitions deliberately and need to revert without destroying contained data, the PIT file could be useful, with the proviso that if any partition did get changed by flashing the PIT file its data would surly be lost.
Is it not the case that the fullest flash of the ROM does include use of Samsung’s own PIT file ? This would seem to fit with “a Samsung is almost unbrickable”. (But I never tried to flash Stock to to a “trebelised” device.)
My notes regarding my repartitioning of my a3y17lte (where I did save an original PIT) are that “the way back” would be Stock ROM only, rather than the PIT file.
The PIT file might be useful if my partitioning had gone wrong in some way especially if I wanted to make a new adjustment.
2 Likes
Thanks for your answers @aibd @piero,
I’ve done some researches myself and i now know how to use the PIT file. However, I still feel as if we’re beating around the bush. I’ll try to flash the pit file this morning. However, i’m pretty sure that this won’t prevent the phone from entering a bootloop when flashing twrp. I’ve found a xda article thay explains how to flash twrp on a A8. https://xdaforums.com/t/recovery-official-twrp-3-3-1-0-for-galaxy-a8-2018.3818201/
There’s lots of other steps to do that aren’t done on regular phone. Looks complicated. Maybe will it prevent the phone from entering a bootloop ??
1 Like
i finder crossed that resolve your issue, because
the link to the XDA thread was there for the beginning…Lol
1 Like
I see on your screenshot that my device is using dm-verify. Maybe that this thing is linked to the fact that i can’t mount system. How do i install a kernal with dm-verify disable in the ftab ?? Sounds like chinese for me !
All right. I’m sorry to ask that, but I don’t know how to download the no-verity-opt-encrypt provided in the post, as I just don’t understand how this repo works. Could you or @aibd tell me how to do so ?
Many thanks !
Edit :
It failed. Complete(Write) operation failed.
Now going on the Pit file 
Edit 2 :
Odin failed to rewrite partition with PIT file too. I guess it’s not a significant problem as the impossibility of mounting system must be due to the dm-verify lock… Still, I’d like help to download the stuff demanded by the post.
it is no more stored on the linked server…
1 Like
I’m sorry for not being really active this week, I’m really busy. I think I’ll be able to try that on this weeknd. Many thanks for the link btw.
1 Like
I am “enjoying” a /e/OS-Q GSI on my Xiaomi Qin 2 AI Life with stock Android 9.0 (Pie Go)
I’m curious to see how and where your excursion will end…