Hi,
Yesterday I "blindly" installed the latest CM nightly without noticing that I was installing CM13... After the install, no Google App was working (as expected). When I noticed I had installed CM13, I tried downloading OpenGapps (all from nano to stock for ARM, -not ARM64-), and none of these can be installed, I always get an error (Status Code 1). After a lot of trying, I coundn't even make a wipe (I got an error while formatting data).
After flashing a stock ROM via Odin, the phone worked again, so I tried reinstalling. Now the issue I have is that I can't install any custom ROM to the phone, I have tried flashing CyanogenmodRecovery (for CM12 and CM13) and CWM 6.0.4.7, all of them let me install the latest CM12.2 nightly (26.12), but the phone always hangs on the Cyanogenmod Bootscreen. Wiping is not showing any errors anymore.
Any thoughts? Am I missing something? I am relatively new to the S4, and I got mine already with CM11 on it, and until yesterday I was always able to update without any issues... Am I missing some step?
Small update: I get some errors in the recovery logs: unable to mount /efs. I don't understand why I get this error when a OEM Kitkat works, but well, will keep trying, maybe I find a way to get it working...
1. Use TWRP, CWM is outdated.
2. "Nightly" realeases are testing firmwares. CM13 for GT-i9505 is in early releases too. They have lot of bugs still.
3. - Download the latest stable CM firmware: HERE and copy it to your SDCARD external + Gapps (ARM+ android 5.1 + nano).
- Go to DOWNLOAD MODE and flash TWRP. Boot in TWRP - Select Wipe - Advanced Wipe and wipe all (less usb-otg and external memory).
- Flash CM12.1 firmware and GApps then. Reboot and enjoy.
Use TWRP. Google for s4 twrp. On that page you will also have various install instructions. Afterwards you can flash pretty much any custom rom.
Well, tried exactly these steps, I only skipped gapps for now. I installed following version: cm-12.1-20151117-SNAPSHOT-YOG7DAO1JN-jfltexx. However the phone still hangs while booting... I will let it for a while and see if it boots, but I think it's still stuck... The stock Samsung Kitkat flashes properly from Odin and can be booted... Really strange. Is there anything I can do to see what's going on? I only get the Cyanogenmod Bootscreen, but no adb access...
Well, I am getting some errors: unable to mount /efs... This seems to be the problem, no idea why this is happening... I will keep looking around for a fix... I still don't quite understand why a stock KitKat works...
mschmiedel said:
Hi,
Yesterday I "blindly" installed the latest CM nightly without noticing that I was installing CM13... After the install, no Google App was working (as expected). When I noticed I had installed CM13, I tried downloading OpenGapps (all from nano to stock for ARM, -not ARM64-), and none of these can be installed, I always get an error (Status Code 1). After a lot of trying, I coundn't even make a wipe (I got an error while formatting data).
After flashing a stock ROM via Odin, the phone worked again, so I tried reinstalling. Now the issue I have is that I can't install any custom ROM to the phone, I have tried flashing CyanogenmodRecovery (for CM12 and CM13) and CWM 6.0.4.7, all of them let me install the latest CM12.2 nightly (26.12), but the phone always hangs on the Cyanogenmod Bootscreen. Wiping is not showing any errors anymore.
Any thoughts? Am I missing something? I am relatively new to the S4, and I got mine already with CM11 on it, and until yesterday I was always able to update without any issues... Am I missing some step?
Small update: I get some errors in the recovery logs: unable to mount /efs. I don't understand why I get this error when a OEM Kitkat works, but well, will keep trying, maybe I find a way to get it working...
Click to expand...
Click to collapse
Try dowloading the rom from a thread here on the forum.
You didn't mention what phone model you got so I assume it is a GT-I9505. You can find the official thread in the I9505 original android development section. The maintainer is AntaresOne.
It is the GT-I9505, I now was able to install a stock Kitkat, and it now is allowing me to update via OTA, (first time I got a message that I had a "changed" phone and OTA was disabled). I will let it install this way and see what happens.
Last time I tried with TWRP I was getting the error "unable to mount /efs", but after flashing an ODIN ROM the phone works, I have LTE Data and can place and receive calls, IMEI is there, so I am now confused about what can be wrong.
When this OTA update works, I will try to reflash TWRP via Odin (and not mess around with heimdall anymore), and see if then I can install CM12...
I downloaded the version from the Cyanogenmod site, the latest stable CM12.1 release, so I guess it should be as good as downloading it from an xda thread...
I don't know. It's worth a try.
If you get errors about efs,be careful.The EFS partition contains the most important stuff like your IMEI.There are some backup/restore tools of EFS, you should check them out.Wipe everything,flash cm,then restore EFS backup.
Related
This post is about the failure to install gapps after flashing ROM and the troubleshooting that ensues.
Posting here, in case somebody might find this helpful. All the best!
I read an article in ibtimes about flashing SuperNexus 4.0 kitkat into Galaxy s3 and I was bored :silly:
I decided to flash SuperNexus 4.0 into my phone, replacing its stock 4.3 Jelly Bean ROM
I rooted the phone first, using Odin 3.0.7 and the CF root that comes with it. It works without hiccups
I downloaded a copy of CWM 6.0.4.6 and flashed it, but it did not work. Failed at Odin. Odin just freezes without failure indication. It took me a couple of hours to finally detach the USB cable and restart the phone out of download mode. It was my first time, of course, I was scared.
I downloaded a copy of CWM 6.0.3.2 and flashed it, it works.
But I decided to download a copy of CWM 6.0.4.5 instead, the one that the ibtimes tutorial links to, and flashed it, it works
However, I can't format /data. I can't mount /data and /system. I can't format Dalvik Cache. I don't have any experience yet, ibtimes seems to indicate that this should not be the behavior, but I moved forward anyway.
I flashed SuperNexus anyway, It works. (flashing SuperNexus is tricky too, I have to edit the updater-script within the zip file to remove asserts. the asserts are causing failure since assert does not match exactly the model number and ROM target)
I tried to flash gapps, but it can't. Reason being that it can't set /system folder during installation setting, probably since CWM can't mount it.
I assumed that the partition is corrupted. I assumed that something messed with the partition since it can't mount it. I assumed that the hiccup while attempting to flash CWM 6.0.4.6 is the culprit
So I mucked around, collecting information on how to do re-partition. However, I ensured that I understand fully about re-partitioning. Since It sounds like it may really brick the phone if I messed it up.
Gathering information about partitioning is a hit miss since the community is filled with reverse engineers. So there are no definitive guide, just guess works.
While following various leads, I tried looking at GPT fdisk since running fdisk shows that /dev/block/mmcblk0 contains only /dev/block/mmcblk0pt1, which leads me to believe that the phone needs gdisk to check the partition (I read this in La Grande partition table reference in xda). I tried to follow this lead, but I have trouble finding gdisk that was compiled for android. When I do find one, I have trouble executing it. I can't seem to be able to chmod it to 764. I dropped this lead.
I flashed Cyanogenmod 10.3, thus reverting back to Jelly Bean 4.3 because SuperNexus 4.0 is not stable yet. Ironic yes? (Removed assert too)
Cyanogenmod works well, in fact, altough I failed to install gapps, the phone is working perfectly. This niggles me into doubting that there is any fault with the partition or the phone.
I tried to sideload gapps. To sideload gapps, I need to run adb alongside CWM in sideload mode. CWM in sideload mode causes the PC to not recognize the phone. It shows the phone as GT-I9305 unknown device.
I failed at finding the driver that could recognize that. Reading off the internet leads me to assume that Windows 8 does not support the USB driver.
I also have this niggling feeling that maybe it is the CWM that is causing the driver problem in sideload mode, since it should be the CWM that communicates with adb.
I re-flashed CWM 6.0.3.2 in hopes that it is more stable.
I now I can connect sideload on adb, but I can't sideload it, because of error, but it looks better since there is actual communication between the phone and abd. Furthermore, device manager identifies the phone as Samsung USB device. I'm feeling optimistic here. Since communicating with adb means the CWM is better than the latest 6.0.4.5. I hope that this CWM can mount /data and /system!
I tried to mount /data and /system on the CWM, lo and behold, it mounted those folders!
I tried to install gapps, the latest one. It soft bricked my phone into boot looping Cyanogenmod, (well at least I believed so since the load takes a longer time than usual) and I did not wait to finish it.
I boot into CWM and format /data /system to reset Cyanogenmod, It works, and loads Cyanogenmod upon reboot
I downloaded the correct gapps version that corresponds to Cyanogenmod 10.3, then booted into CWM and installs the gapps, it works!
I booted into Cyanogenmod and the gapps is finally there!
I opened Google Play, it asks me for my google account. I filled it and all other gapps picks it up, showing contacts, mail and other syncs.
The real culprit? my curiosity? No, CWM 6.0.4.5! Lesson learned: In the world of flashing ROM, the latest might not be the greatest...
Reading you, I could not help but remembering running into the same kind of hurdles a year ago when I rooted and rommed my I9300 for the first time. From my experience, it is quite difficult to brick this phone. I know it, I flashed a kernel instead of a ROM once by mistake.
I never had to tamper with zips, but maybe your S3 is not an international version ?
You should always do a nandroid backup before flashing a new ROM, it can be of great help if something goes wrong.
For the future, I suggest you drop CWM and go to TWRP instead. And as I am running SuperNexus 4.0, and went from CM 10.3 to OmniRom then SuperNexus, I think the stability of these ROMs are comparable. No recurring FCs, no really hampering issues. Probably due to its lack of customizations, I would say SuperNexus is the best of the three in terms of performance.
Anyway, all custom ROMs for Exynos Galaxy S3 usually suffer from issues with graphic drivers (some display elements are badly rendered, I can see it often on wallpapers, as some colors are wrong), and sometimes with the camera. Thanks, Samsung!
The first times flashing can be really stressful, but once you get the hold of it, your phone is running free
I'm trying to install CM via TWRP.
First I had to unlock the bootloader, so I did, and since then I could not boot to my stock Android (although, correct me if I'm wrong, unlocking the bootloader should NOT delete the OS), it just sent me to recovery.
So I went along, flashed TWRP and got cm 10.2.1 for jfltexx. At first it didn't install well, because my data partition was not formatted correctly. So I formatted it, now TWRP sees it correctly and is able to mount it, enable MTP and everything. When I try to install now, everything seems fine and TWRP's log shows "Updating partition details..." and gives me the "Successful" message, offering to wipe cache/reboot system. (I did wipe cache and dalvik cache before, of course).
If I choose "Reboot System", it just boots back to recovery. The same happens if I power it off and boot normally, even if I pull out the battery and retry that way.
What can I do about it?
Jon-G said:
I'm trying to install CM via TWRP.
First I had to unlock the bootloader, so I did, and since then I could not boot to my stock Android (although, correct me if I'm wrong, unlocking the bootloader should NOT delete the OS), it just sent me to recovery.
So I went along, flashed TWRP and got cm 10.2.1 for jfltexx. At first it didn't install well, because my data partition was not formatted correctly. So I formatted it, now TWRP sees it correctly and is able to mount it, enable MTP and everything. When I try to install now, everything seems fine and TWRP's log shows "Updating partition details..." and gives me the "Successful" message, offering to wipe cache/reboot system. (I did wipe cache and dalvik cache before, of course).
If I choose "Reboot System", it just boots back to recovery. The same happens if I power it off and boot normally, even if I pull out the battery and retry that way.
What can I do about it?
Click to expand...
Click to collapse
First I'd try a newer version of CM. That's an old one. It might not work and play well with a newer version of TWRP. Plus the newer version is a little more polished.
Second, if you must use that CM version, redownload it. You wouldn't be the first person who got a corrupted install file that causes screwball issues like this.
Third, if all else fails use Odin to reset back to stock and start over. Something might have gotten all borked up when you first modified the device that isn't letting the install work. A full restore to stock should correct that.
Skipjacks said:
First I'd try a newer version of CM. That's an old one. It might not work and play well with a newer version of TWRP. Plus the newer version is a little more polished.
Second, if you must use that CM version, redownload it. You wouldn't be the first person who got a corrupted install file that causes screwball issues like this.
Third, if all else fails use Odin to reset back to stock and start over. Something might have gotten all borked up when you first modified the device that isn't letting the install work. A full restore to stock should correct that.
Click to expand...
Click to collapse
Thanks for the reply.
Regarding the versions of CM and TWRP, I deliberately picked these versions due to their high download count (A sign I can trust these builds, being not too buggy). I'll try a newer CM version and another TWRP version if that didn't help.
I will also verify the MD5 for the downloaded file this time.
If I restore to stock via Odin, wouldn't that override the recovery? I've looked on some tutorial on how it's done, and it seems like the stock recovery is flashed, then used to restore the stock. Is there any way to use Odin to flash other ROMs?
EDIT: Nope cm-11-20140210 also failed, and I did verify the MD5 now. My TWRP is the newest available for jgedlte in the download page (2.8.0.1).
I did manage getting into some sort of a boot loop (The initial "Reboot System" brought back the recovery, but after a full power off and a reboot, the screen remains black and the phone vibrates every 4 seconds or so.)
EDIT 2: I tried to flash the stock back, following this tutorial. I downloaded the Open European version, flashed the AP but it failed during the write of system.img.ext4, saying that the image is invalid. I tried again with the PIT file, but it failed too (secure check fail while repartitioning...).
Hey guys,
Recently I flashed
ClockWorkMod recovery - v 6.0.1.9
Cyanogenmod 12.1 nightly -cm-12.1-20150706-NIGHTLY-mako.zip
It all worked out (with great difficulty) and the phone works fine.
However, I have no google apps. Coming from stock factory setting to a rom with no google apps is quite difficult.
So, i tried flashing the gapps along with the rom but i keep getting a status 7 error message and the installation gets aborted, the result being when i reboot my phone i get a plethora or error messages of all the google apps which stop working (i.e none of the gapps work).
I have tried flashing the following (file names) gapp zip files with no luck.
gapps-5.1-2015-06-02-15-21
gapps-5.1-2015-07-03-13-41
gapps-L-4-21-15
gapps-lp-20150211-signed
BaNkS-dynamic-gapps-L-6-21-15
pa_gapps-modular-mini-5.1-20150315-signed
Even the gapps link on the cyanogenmod wiki page does not work. ( i think i included that filename in the above list)
On reading other forums, members say that the recovery must be updated.
Quite honestly i am quite apprehensive to do anything to the recovery as i got stuck into a bootloop once and it took me a day to get out of it.
P.S i am a complete amatuer in this process, this is the first custom rom i flashed after staying on stock factory images for 2 years.
I really do need help, as no other rom works well except the cm 12.1 and itwould be absoutely brilliant if i have the google apps too!
Thanks in advance.
solution found
Hey there, I have the s4 (GT-i9505)
I had the same problem until today and I have found the solution to it,
I updated my cm12.1 nightly to 20150706,
Downloaded slim gapps 5.1.x mini latest (20150706), [I searched for it on Google]
Tried flashing the cm and then the gapps but it didn't work, and gave me all the errors of apps that have stopped which was very annoying.
So then I did a little research and figured out that I was using twrp v2.6.0.0 which was quite old , so I never gapps after the root. So then I updated it to the latest version by connecting my phone to the PC in download mode and downloaded the twrp v.2.8.0 (latest) and recovery booted my phone.
Factory reseted my phone, installed both the cm12.1 and gapps by selecting the zip files and then flashing them. Wiped the dalvik cache. Finally rebooted my phone.
And to my surprise it actually worked. Thank god that now I have the play store and all the other apps without any annoying popups.
I'm on my phone so I can't seem to be able to upload any links .
I'm sorry you gotta have to search on Google for the download links.
Have fun buddy. Hope it works on your nexus 4. Enjoy !!
Got it working!!
So, followed some forums ( including mehsan23) and updated my custom recovery. The most surprising thing is that you can do this by downloading zip files of the latest cmw recovery and flash them on to your existing recovery and the recovery automatically updates.
Then flashed the gapps on cm12.1 wiki page and it worked! So relieved! However the Google app crashes but its alright I can do without it.
Thanks guys!!
P.s thanks again mehsan23
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Mmmh, strange, I did a factory installation (latest 5.1.1 from Google) and started the same thing from scratch ... and guess what... the system is booting fine now.
No idea why it did not work on my first attempt .
Regards, mistersixt.
mistersixt said:
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Click to expand...
Click to collapse
Same here. Running stock until today, wanted to see a different ROM, flashed TWRP 3.0.0, it refused to boot anything else. Tried to flash DU, then tried Chroma. Did a full wipe, then an advanced wipe selecting everything, then a full format, same thing. Installed TWRP 2.8.7, same thing. Finally installed latest stock, it is now booting, optimizing apps. I don't know if installing a custom rom will work or not yet.
Edit: Yeap, after flashing stock 5.1.1 and installing TWRP 3 again, the phone is now booting into DU.
First time I did a wipe with TWRP, it complained that it couldn't mount /data. Since this is the first time doing it, I assumed it was normal. After going through a full format, it didn't complain about data anymore, but it did complain about something to do with /dev/zero and another file under /dev/. I assume it was trying to dd /dev/zero to a file under /dev/ that didn't exist.
+1
Done the whole process from scratch again and worked like a charm
Hello, same story here.
First I:
- unlocked bootloader
- flashed TWRP (last version)
- flashed Chroma and Gapps
- reboot
=> I consistently rebooted on TWRP. No way to properly install the ROM. No error message at all.
Then I found this thread, and did as described:
- flashed the latest stock ROM
- flashed TWRP again (took me ages to manage to do this: TWRP would not install. I don't know how I finally did it, but at some point it suddenly worked. Probably a driver problem)
- flashed Chroma and Gapps again
Bingo, this time it worked! I don't know why it didn't work the first time. Could it be linked to the bootloader unlock thing?
So I got my 6GB/64GB x720 yesterday. It had Google Play Store already installed (ordered it from HonorBuy) and asked me to install a 7MB OTA, so it seems it had a recent version of EUI on it. My idea was to put LineageOS 14.1 on it or if it wasn't stable enough for me, at least a debloated and rooted stock. So searched XDA and followed this HowTo. No Errors, flashboot oem device-info said, bootloader unlocked, perfekt. Installed TWRP, downloaded recent LineageOS and followed the guides to flash (wipe, ...). Unfortunately flashing never finished, I always had a full progress-bar and it stayed there without doing anything (ok, the device got hot). Thinking of a broken download, I redownloaded the ROM but same problem. So I started downloading other ROMs from XDA: Resurection Remix and OmniROM. Flashing-process went thru, but couldn't flash gapps and ROMs didn't boot at all. I was always only getting to the LeEco-Bootlogo with the chinese writings. So next thought was, maybe for some reason I can't install Lineage-based ROMs, let's figure out later and get a debloated stock ROM. So I downloaded MAURO V2.2_Free and gave it another try. Looked more promising, as the bootlogo was a little different, no more chinese writing but english. Unfortunately this was all I could see of MAURO as I only got a bootloop... so again reflashed MAURO and this time a single line in TWRP-output came to my eye "boot.img could not be written". I checked flashboot oem device-info after every flash and it always told me, bootloader is unlocked, but there seems to be something else that I'm missing that obviously still keeps the bootloader locked. I wiped the phone several times, even sdcard... nothing helped. The only method that worked for me to get a working rom running was by this guide, manualy flashing every bit of stock ROM with flashboot. With MAURO-ROM, I also tried to flash boot.img manually with flashboot, but that didn't work, either.
Anyone of you experienced the same? What am I missing? Or is this some new protection implemented by LeEco for the most recent devices? Any help really appreciated!
regards
CDFS
I have the same phone from Honorbuy, I flashed twrp using the tool by Mauronofrio and from the twrp wiped all and flashed the custom rom, all went ok, no errors at all! Glad to see you have solved anyway!
Thanks for the answer... no, it's not solved for me... still a lot of bloat on the phone I can't get rid of. Do you have a link for the tool you mentioned? Could be worth a try...
Hi! I've used this tool installing it on a Windows 7 64 system:
https://forum.xda-developers.com/le-pro3/development/tool-tool-one-mauronofrio-t3580611
Then turned ON the (original LeEco stock rom) usb debug option by the rom's developer options, then downloaded the LineageOS 14.1 by Team Superluminal in the phone's internal SD (the only SD it have!) + Arm64 nano Gapps, then with the tool gave a reboot in sideload mode. Then flashed the twrp recovery by the tool, restarted in recovery mode then executed a backup of ALL the "backupable" stuff (all the original rom and data and efs), then in wipe/advanced options I wiped dalvik, system, cache, data. Then in Advanced/file manager I wiped all the SD files with a dot ( . ) at the beginning of their names, then flashed the custom rom + gapps, reboot system, wait some minutes, done!
No luck with this tool, it doesn't even find my device. Any other ideas? I've read something for the x727, where they had to flash a 19s bootloader first, but I don't want to fiddle with flashing files that are not 100% meant for the x720...
CDFS
Solved! As I could install TWRP I just went the next step and installed SuperSU (rooted the phone) in order to at least debloat stock rom. During the installation of SuperSU I saw, that SuperSU obviously patches somehow the bootloader. After checking that SuperSU worked in the ROM, I was curious if this could be the missing part I was searching for. I tried to install a LineageOS-based ROM and BINGO! it just went straight through! From my previous phones I was used to just install TWRP, wipe anything and flash desired ROM. This seems to be different on this device... so the proper procedure to be able to flash any ROMs is: Install TWRP, root stock ROM, reboot so SuperSU is fully functional, then go back into TWRP, wipe, flash what you want.
CDFS
I hate to say it, but it's still not solved. After testing Resurrection Remix, I wanted to test turbos ROMs, so went to TWRP, wiped and flashed... and got the same behaviour as before, ROM not booting. Also installing SuperSU via TWRP again didn't help, so brought back the phone to stock 023S manualy with the guide by Presterin, installed TWRP again and also SuperSU. No Errors, but flashing a different ROM didn't worked. So for now I'm back to stock, rooted it and tried to debloat it by myself. The only difference between the successful flashing and the failed was the stock version: I had the 026S-update when I rooted the phone and successfuly could flash another ROM. My guess would be that LeEco changed something in the bootloader, but I have no chance to verify this. Anyone from the devs maybe who could look into this? If you need dumos, logs or anything like that, I would be happy to help.
CDFS
This seems unrelated to bootloader.
Anyway:
1. Make sure you got the latest firmware, if not sure:
1.1. Download latest OFFICIAL ROM
1.2. Rename the rom to a 'update.zip' and place it on phone's root directory.
1.3. Reboot to fastboot and flash STOCK RECOVERY
1.4. Reboot to recovery and flash, also check wipe data.
DO NOT FLASH STOCK ROM WITH TWRP! THIS WILL NOT WORK!
That's it, you should have the latest firmware now.
After booting to stock rom, reboot a few times is recommended.
2. Download latest OFFICIAL TWRP
2.1. Flash TWRP with fastboot.
2.2. Reboot to TWRP.
2.3. Download any custom rom of your choice.
2.4. Wipe.
2.5 Flash.
Done.
You can try to flash a stock, old rom using the "Qfil/FlashOne" way as suggested by Tryzex (read his thread and other related threads), then once you have got a stable, full working phone, you can (hopefully!) wait for a LeEco OTA automatic update that can "repair" the file system/partition structure (also bootloader I hope!).
Btw, to debloat it isn't necessary to root the phone, you can keep the phone unrooted & debloated using the file manager embedded in twrp recovery to delete/replace any file/app you want. I'm sorry I can't help you better, cheers and... good luck!
PS
I see now the post from Voron00, it's a good hint!
@voron00 thx for the steps described. I'm using the most recent, official TWRP (3.1.1). Latest Official Stock seems to be 023S on their site, even though there is a 026S update. However, I did this 026S-update and rooted again, but was to cusious if flashing would work now... so I tried flashing turbos MIUI... guess what? It worked. So for whatever reason I seem to have trouble when flashing from a 023S, but no problems when flashing from 026S. I don't quite understand why you think that my problem is not related to the bootloader? As mentioned in the OP, I could see in the logs that while flashing, some roms had thrown errors regarding writing the bootpartition.
CDFS
Seems as I found the culprit, somehow. At least I could flash two other ROMs without any problems. Obviously I mixed and partly missinterpreted some steps found in different threads and howtos. I had "rm -rf for formating" ticked all the time in TWRP. My flashing procedure is now as follows:
1. in TWRP settings check that "rm -rf instead of format" is NOT ticked
2. wipe Cache, System and Data
3. repair filesystem for Cache, System and Data and check that no errors occur
4. in TWRP settings tick "rm -rf instead of format"
5. flash ROM
6. wipe Dalvik
CDFS
"rm -rf" clears all the files and directories without formatting the partition. If your partition is damaged you need a real format to obtain a reliable partition (if the "disk" isn't faulty). Perhaps in your case a real format was required to solve the problem! I always used the real format and assumed other users even so. I see you finally solved the problem!