CM13 + IsoRec Problem - Galaxy S II Q&A, Help & Troubleshooting

Hi all, first off. Thanks to all devs and the XDA team for providing an invaluable resource which has provided me with the information to successfully flash all of my phones over the years.
TL;DR : CM13 Flash > Repartition > Can't flash gapps using CMRecovery > Factory reset+cache wipe > Stuck in Bootloop > reflashed Lanchon TRIM IsoRec > Still stuck in Bootloop.
I've encountered a problem which I'll try to detail as best as possible.
I wanted to upgrade my S2 i1900 to the latest Cyanogenmod, going from v11 (4.4.4) to v13 (6.0.1). I did this successfully, however I neglected to repartition the device as instructed which left me without gapps.
So I went back and attempted to repartition the device using Odin. The partition was successful. I then attempted to flash gapps using the native CM Recovery. Suprise, surprise I was unable to, needing to instead use either CWM or TWRP.
Whilst in the CMRecovery I wiped cache and performed a factory reset. I am now stuck on the CM loading screen. I did wait and wait and wait as is custom for first boots but I find myself locked in the dreaded bootloop.
I reflashed the IsoRec Tar file for CM13 with no luck or change. I know I'm missing something, I just can't put my finger on it...
Thanks,

---

Reflashed to stock partition using Odin:
kernel-Lanchon-TRIM-IsoRec-20160207-cm-13.0-i9100-for-ODIN.tar
and
I9100_STOCK-System_2GB-Data_512MB-Preload.pit
Still stuck in bootloop/softbrick.

---

Hi,
You are using the wrong pit file, that's why gapps can't be flashed.
You need to use a pit file with 1GB system partition.
gsstudios

---

Hi, thanks for the reply.
The issue isn't with the gapps package, I was well aware before upgrading to CM13 that the 5XXmb (Stock) system partition .pits would not suffice if i wanted both CM13 and gapps. The issue is I have soft bricked my S2 with CM13 bootloop.

---

w0lf91 said:
Hi, thanks for the reply.
The issue isn't with the gapps package, I was well aware before upgrading to CM13 that the 5XXmb (Stock) system partition .pits would not suffice if i wanted both CM13 and gapps. The issue is I have soft bricked my S2 with CM13 bootloop.
Click to expand...
Click to collapse
I assume that you know that CM recovery in CM13 is broken?
You should be using TWRP for your recovery, making sure to wipe system, data and cache. (Backup as always).
Isorec kernel is not required on CM13. Just flash TWRP (see thread for more details).
There is also a CM13 upgrade guide I made that should help solve 99% of these issues.
gsstudios

---

I can't boot into recovery mode, not even after following your guide here: http://forum.xda-developers.com/gal...es/guide-want-to-update-to-cm13-read-t3313978
Which leads to: http://forum.xda-developers.com/showpost.php?p=57974756&postcount=4
Kernel which flashed successfully, but failed to boot was:
kernel-Lanchon-TRIM-FreezeFix-TWRP-20160111-cm-12.1-i9100-for-ODIN.tar

---

w0lf91 said:
I can't boot into recovery mode, not even after following your guide here: http://forum.xda-developers.com/gal...es/guide-want-to-update-to-cm13-read-t3313978
Which leads to: http://forum.xda-developers.com/showpost.php?p=57974756&postcount=4
Kernel which flashed successfully, but failed to boot was:
kernel-Lanchon-TRIM-FreezeFix-TWRP-20160111-cm-12.1-i9100-for-ODIN.tar
Click to expand...
Click to collapse
You are looking at the wrong thing.
Scroll down until you see " If you forgot to flash Isorec Recovery when upgrading, this is what you can do:"
Try the ADB Sideload method first. If that doesn't work, try the terminal method. If you are following the second method, you need to follow the flashing guide again, but making sure to flash TWRP here. You only need to flash the TWRP isorec recovery and not the kernel itself.
gsstudios

---

Sorry, but I don't think you've read any of my posts properly.
I can't do ADB Sideload as I can't get into CMRecovery, after following your guide that "fixes 99% of problems".
I can't do the terminal method either because I can't get into the ROM, as I'm softbricked; stuck on the CM13 bootloop.
The only thing I now have access to is the Download mode.
Out of frustration I kept spamming the recovery (vol up+home+power) and managed to boot into TWRP v2.8.7.0
If i follow your guide here: http://forum.xda-developers.com/gal...es/guide-want-to-update-to-cm13-read-t3313978
From "If you require to use Gapps, make sure to re-partition your phone now if you haven't done so! This can be done by following one of the guides linked in the Gapps section" onwards, I should be ok, correct?

---

w0lf91 said:
Sorry, but I don't think you've read any of my posts properly.
I can't do ADB Sideload as I can't get into CMRecovery, after following your guide that "fixes 99% of problems".
I can't do the terminal method either because I can't get into the ROM, as I'm softbricked; stuck on the CM13 bootloop.
The only thing I now have access to is the Download mode.
Out of frustration I kept spamming the recovery (vol up+home+power) and managed to boot into TWRP v2.8.7.0
If i follow your guide here: http://forum.xda-developers.com/gal...es/guide-want-to-update-to-cm13-read-t3313978
From "If you require to use Gapps, make sure to re-partition your phone now if you haven't done so! This can be done by following one of the guides linked in the Gapps section" onwards, I should be ok, correct?
Click to expand...
Click to collapse
Yep, you should be fine following that guide onwards.
Let me know if you encounter any other issues.
gsstudios

---

Ok, so I reflashed I9100_1GB-System_4GB-Data_512MB-Preload.pit, but now I can't get back into TWRP!! I did not flash a different/new kernel alongside it.
vol_up+home+power just keeps looping the battery icon.
Should I have flashed the kernel WITH the .pit?
Thanks for all your help thus far.

---

w0lf91 said:
Ok, so I reflashed I9100_1GB-System_4GB-Data_512MB-Preload.pit, but now I can't get back into TWRP!! I did not flash a different/new kernel alongside it.
vol_up+home+power just keeps looping the battery icon.
Should I have flashed the kernel WITH the .pit?
Thanks for all your help thus far.
Click to expand...
Click to collapse
Yep, it is required for you to flash kernel alongside the pit file.
gsstudios

---

gsstudios said:
Yep, it is required for you to flash kernel alongside the pit file.
gsstudios
Click to expand...
Click to collapse
I'm really stuck on what to do now >.<
Any ideas?
Edit: When I go into Download mode this info appears:
ODIN MODE
PRODUCT NAME: GT-i9100
CUSTOM BINARY DOWNLOAD: YES (8 counts)
CURRENT BINARY: CUSTOM
So I'm guessing that the "8 Counts" if from me flashing data and its getting piled on top of each other. I've tried using the "nand erase all" option but that fails as well.
(see attachment)

---

w0lf91 said:
I'm really stuck on what to do now >.<
Any ideas?
Edit: When I go into Download mode this info appears:
ODIN MODE
PRODUCT NAME: GT-i9100
CUSTOM BINARY DOWNLOAD: YES (8 counts)
CURRENT BINARY: CUSTOM
So I'm guessing that the "8 Counts" if from me flashing data and its getting piled on top of each other. I've tried using the "nand erase all" option but that fails as well.
(see attachment)
Click to expand...
Click to collapse
Try using this guide:
[GUIDE][Troubleshoot a failed Odin flash]
Usually write failures usually mean that your device has been bricked. However, it is necessary to test every other method before drawing this conclusion.
Maybe try stock pit file.
gsstudios

---

Success! Sort of...
I was able to recover the phone in its entirety using the section:
Another option for i9100
If you have an i9100, probably the best option to flash is to flash 4.1.2 JellyBean leak. Huge thanks to It_ler for providing the file after it was lost during the shutdown of hosting site hotfile.com and re-hosting on his dev-host, and for keithross39 for re-hosting the file on his storage. Download it here: (Android File Host link) or here: Mega link. This is a 3-part firmware. It will wipe your device as it flashes, and in many cases this extra wipe while flashing contributes to a successful flash. To set this file up in Odin (as it is 3 parts): PDA = CODE_I9100XXLSJ.tar, PHONE = MODEM_I9100XXLS6.tar, and CSC = CSC_HOME_OXX_I9100OXXLS1.tar. As usual, do not tick 'repartition'.
Click to expand...
Click to collapse
Thank you gsstudios for your time and patience, I'll reattempt the upgrade to CM13 when I have the patience again.

---

gsstudios said:
Try using this guide:
[GUIDE][Troubleshoot a failed Odin flash]
Usually write failures usually mean that your device has been bricked. However, it is necessary to test every other method before drawing this conclusion.
Maybe try stock pit file.
gsstudios
Click to expand...
Click to collapse
TL;DR 1 - Can't root Galaxy S2 gt-i9100? Use Siyah CWM Recovery.
TL;DR2 - Stock CM13 Recovery appears to be working.
Hi Gsstudios, thought you might like to know my progress.
I came across a problem with the JB firmware I used to recover my phone in that I couldn't gain root. I tried KingoRoot and the update.zip method from CWM and TWRP. But either root would only be temporary until I rebooted the phone, or the update.zip refused to flash entirely. I also could not find a ChainFire fix for my specific ROM. I ended up using Siyah's CWM recovery.
Whilst Siyah's CWM recovery granted me root apps like rootchecker would not recognise it. The warning triangle at launch said otherwise! So I risked it and followed your guide from that start. CM13 was flashed successfully, but again I forgot to flash gapps. On reboot to recovery I was greeted with CM13Recovery. I flashed gapps, reboot to OS and received a tonne of errors. Went back to CM13Recovery wiped everything, reflashed CM13 & gapps using CM13Recovery!!
And hey presto! Everything is working again and now on A-M6.0.1