Database Develop

[Recovery]Clockwork Mod 4.0.1.4 (3.2 compatable)

DJ Steve ported CWM 4.0.1.4 with the release of 507.
Requirements:
Stock 5xx based rom [Honeystreak is not supported!]
Ability to enter fastboot mode: Fastboot+ADB.zip
Battery with 60% or greater charge
Basic understanding of the command line
Install Instructions:
Download recovery.img
flash the recovery with "fastboot flash recovery recovery.img"
Finished
Credits:
DJ_Steve for porting it
Koush for creating clockwork mod
I take no credit beyond this basic guide
Notice:
The Streak 7 with HC might now detect the driver properly, if it doesnt you must force install it using the "Android ADB Interface" from the list of available drivers
Will not work on 2.2.x, you must use CWM 3.0 for that.
Do not attempt to wipe data from within CWM, it will likely case a boot loop afterwards.

Thank you!!
Can I just push this recovery to my recovery partition within 3.2?
Im having issues having my PC at work recognize the fastboot device, and installing the drivers.
I am on xp..
TIA!

'error: cannot load 'recovery.img'
I got fastboot going fine, commands like 'fastboot reboot' are working.
However just above when I use your line to flash recovery, any ideas on what it might be!?

Uploaded new version of fastboot+adb.zip hopefully it has the correct IDs so you dont have to force install it.
Are you sure you downloaded the image correctly, and did you name it correctly when using fastboot

Yeah I was making a repeated typo when pointing fastboot to the recovery but its all working now, thanks a lot.
Clockwork mod (cool blue writing) and rooted all within a few days, good work and thanks to all involved.

FWIW I tried this on the T-MO stock 2.2.2 ROM. The install went fine, I copied S7-4.0.1.4.img to recovery.img and ran the fastboot command with no problems.
I power up the Dell Streak 7 while holding power and the up volume key, and get the menu as expected. I Select "Software Upgrade via update.pkg on SD Card", and the message "Booting recovery kernel image" is displayed.
At this point the machine seems to be frozen. I can reset with a paper clip, and reboot the machine into 2.2.2 just fine, but if I cannot resolve why it does not show the clockwordmod menu, then I guess it is back to NVFLASH.
So what am I doing wrong? do I need an SD card in the device with an update.pkg on the card? Or is there something else?

Oh that was a strong possibility.
CWM 4.0 uses the 507 kernel as a base. 507 will not boot without updating the bootloaders.
So that means CWM 4.0 wouldnt be able to boot unless you had 50x installed.

TheManii said:
Oh that was a strong possibility.
CWM 4.0 uses the 507 kernel as a base. 507 will not boot without updating the bootloaders.
So that means CWM 4.0 wouldnt be able to boot unless you had 50x installed.
Click to expand...
Click to collapse
Probably a good idea then to remove that "Assumed to work on 2.2.2" phrase then from your first append.
So I guess it is NVFLASH time ... Or could I somehow flash back only the original recovery.img using fastboot somehow?

Post updated, i needed someone to actually confirm that it didnt work as i dont have access to a s7

dblml320 said:
Probably a good idea then to remove that "Assumed to work on 2.2.2" phrase then from your first append.
So I guess it is NVFLASH time ... Or could I somehow flash back only the original recovery.img using fastboot somehow?
Click to expand...
Click to collapse
I posted over at TabletRoms yesterday that the new recovery did not work with Froyo 2.2.2.
To answer your question, all you have to do is fastboot flash the old CWM recovery, version 3xx something I think it is.

"waiting for device " and nothing happen !!! what should i do? i can not install driver using files in : Fastboot+ADB\Win32\Streak 5+Streak 7+Venue\Win7 !

cdzo72 said:
I posted over at TabletRoms yesterday that the new recovery did not work with Froyo 2.2.2.
To answer your question, all you have to do is fastboot flash the old CWM recovery, version 3xx something I think it is.
Click to expand...
Click to collapse
Like he said if you flashed it on a s7 that's still on 2.2.x just reflash with the CWM 3.0 one and that one will work fine on 2.2.x

Is there another way to root stock 3.2?
I am getting this error in fastboot...
"Flashing StorMgr partition recovery
Read after write verify partition recovery"

Not the stock one, as no other rooting tools work on it.
Ways to get around it include: using a pre-rooted rom or using a custom rom (which are normally pre-rooted)
Something may be wrong with your device/install if that is coming up. Or possibly your download was bad, try re-downloading it.

I tried re-downloading didn't work, I have stock rom, I don't think I can install a custom or pre-rooted rom without installing CWM?

You can with nvflash, as honeystreak is ment to be installed with nvflash then updated with the bundled CWM, which is prerooted
Whichever method you decide is up to you, as I cannot formally recommend that one method is better then the other.

thesmacker11 said:
Is there another way to root stock 3.2?
I am getting this error in fastboot...
"Flashing StorMgr partition recovery
Read after write verify partition recovery"
Click to expand...
Click to collapse
Well just as an update I tried this on a windows xp, windows 7 32bit, windows 7 64bit computer, and redownloaded that file each time and it still does the same thing on my device.

It's likely your device itself that's the issue then, I cant be more specific as I dont own a S7

I'm not sure if I should be asking questions here or over in another forum. Figure I'll start here...
I was sorely missing app2sd in honeycomb so went to use and install Link2SD figuring I'd use that. But it doesn't seem to see the second partition I've made on my SDHC card. I can mount the card on Mac OS and Linux and both mount the two partitions on the card so I feel pretty sure I formatted the card correctly. I saw some comment about a change in the way CW mounts things and it causing troubles in the Link2SD thread but I don't understand enough about the magic of Android and how it mounts discs, although I know it had Linux roots, so the comments in that thread weren't clear to me what I can do to get Link2SD working or for that matter even start to gather info to try to figure out what's wrong. Can anyone help me out or point me to a thread that can get me started in figuring out what's going wrong?
Sent from my HTC Flyer P512 using Tapatalk

ok so i installed the drivers for fastboot and i can enter fast boot , but how can i push the file? soory im a newb with the streak.

No OS installed, unable to adb push

I can't seem to find a solution to the problem I am having and I spent 5 hours looking at many threads over many forums.
I was trying to restore my stock GPE in order to send to repair, but I accidentally wiped of everything and ended up with no OS installed. I tried then using fastboot/adb to install through recovery, (TWRP) I am able to use fastboot however adb will not see my device therefore I am not able to push any .zip to install GPE Android 4.3
Tried flashing stock.zip, but get the error "remote 12: signature verify fail", then I noticed that it is "S-On"
I am hopeless right now, but I know there is something that can be done or I am missing/screwing something.
Is there any other way in which I can restore my HTC One to GPE Android as initially shipped? I just need to fix this because I have a repair order going.
Any help will be highly appreciated.

In recovery you can see your sd card?
adb drivers are ok?
When the phone is in recovery the pc can detect it?

Guich said:
In recovery you can see your sd card?
adb drivers are ok?
When the phone is in recovery the pc can detect it?
Click to expand...
Click to collapse
In recovery I do see /sdcard, however HTC One does not have sd card.
I tried downloading some drivers, maybe not the most up to date ones, do you have a link where I can download these?
I did not see if the PC could detect it while in recovery, I will check that and let you know.

vaguitovera said:
In recovery I do see /sdcard, however HTC One does not have sd card.
I tried downloading some drivers, maybe not the most up to date ones, do you have a link where I can download these?
I did not see if the PC could detect it while in recovery, I will check that and let you know.
Click to expand...
Click to collapse
Try to use this adb drivers.
However, let me know if, in device manager, you can see your one.

I have noted that CWM shows ADB drivers quickly than TWRP... perhaps try flashing CWM, adb push your_rom.zip /sdcard, and then flash TWRP if necessary, or just install using CWM..

Problems with Honor 5C/7 Lite/Nem-L21, bootloop and more

Hi
I have searched through just about every thread and tried just about every trick in the book to make my Honor 5c/7 Lite/NEM-L21 to work again but nothing works for my problem. I'll try to describe what I did, what I have tried and what I am able to do with it.
What I did
Unlocked bootloader the official way with code from Huawei.
Flashed twrp recovery
Installed SuperSU from twrp and rooted the phone
Tried to install some custom roms and some stock roms, eventually I tried to install something that apparently wasn't for my specific model and twrp started to throw errors at me
The main error whenever I tried to do something in twrp was "can't mount /cust.." and some more error message which I can't remember
After that I tried to reboot my phone and hoping that it would somehow heal magically, which, of course, it didn't
What I did not do
Take a backup before I started to mess with my phone, stupid, yes I know, but tell me if you have to
What I am still able to do
E-recovery: can boot into E-recovery and connect to wifi and search for package info but then it fails with an error message stating that something is wrong with the package
Stock recovery dload method: Starting to install the package but halts at 5% and then the phone reboots and boots with error stating that I should update again, not sure about what package is loading since I think I have a dload folder both on the internal and the external sd card, but I cant see the internal sd card anywhere (loading the external sd card through another phone)
Fastboot: can boot into fastboot with volume- and power button and do almost all the fastboot commands, but adb does not detect my phone.
What I have tried
Googled, looking here and searching deep inside myself for answers (without any luck, needles to say)
Tried downloading a stock rom NEM-L21***B132, Android 6.x Emui 4.1 and extracting boot.img, system.img, recovery.img and cust.img and while boot and recovery flashes fine with this extracted images everything goes ape**** when trying to flash cust and system, with cust I get a partition error while writing and with system I get a sparse flash write failure, I have no idea why this rom fails while I'm able to flash above mentioned files perfectly fine with a stock nougat rom (Nougat is the reason I started this adventure to begin with). When I flashed all the files fine and try to dload the whole update.app I get nowhere anyway, just a bootloop.
Tried to erase and reformat cust and system but when I try that in fastboot I get a remote: command not allowed.
Tried to flash twrp recovery and the flashing succeeds but I cant boot into it, tried several different versions designed for both 'nougat and marshmallow.
What I need
Someone to point me in the right direction because I am totally lost and almost going crazy after trying everything.
All the help and tips I can get from you guys is much appreciated, I'm willing to try everything you throw at me and answer any questions regarding my issue!
Thanks in advance, Jeremias

dload method, use B100 package.

thelous said:
dload method, use B100 package.
Click to expand...
Click to collapse
Thanks for your fast reply, I do have a few questions for you:
1. Do you have any idea where I can find the B100 package? Tried googling but no luck so far, lowest I can find i B130.
2. Should I just put it on the external SD card and try to get it to update or do I need to extract the *.img and flash them in?
3. Could it be a problem that I might have a dload folder on the internal SD card with a different package?
Thanks again.

jerre84 said:
Thanks for your fast reply, I do have a few questions for you:
1. Do you have any idea where I can find the B100 package? Tried googling but no luck so far, lowest I can find i B130.
2. Should I just put it on the external SD card and try to get it to update or do I need to extract the *.img and flash them in?
3. Could it be a problem that I might have a dload folder on the internal SD card with a different package?
Thanks again.
Click to expand...
Click to collapse
i think somewhere in xda theres B100. all you need is update.app file in dload folder on external SD card (recovery wonr read internal memory since it could be corrupted etc...)

thelous said:
i think somewhere in xda theres B100. all you need is update.app file in dload folder on external SD card (recovery wonr read internal memory since it could be corrupted etc...)
Click to expand...
Click to collapse
Found it, crossing my fingers that it will work this time.

Unfortunately I can't get it to update with the B100 package and the dload method. I can start the stock recovery and the update starts but it freezes at 5% and then the phone reboots with no error message and the bootloop continues.
Any more ideas?

Still no luck for me, anyone got any ideas?

jerre84 said:
Still no luck for me, anyone got any ideas?
Click to expand...
Click to collapse
what was your phone build number before all these? EMUI 4 or 5?

shashank1320 said:
what was your phone build number before all these? EMUI 4 or 5?
Click to expand...
Click to collapse
It was EMUI 4. The reason for all this was that I could not get the Nougat-update in any way.
I think that I might be on EMUI 5 now because I can't get the stock recovery from the B100/B132 package to boot but when I flash the recovery from B351 or similar it can boot but I'm, still not able to get any update to work.

jerre84 said:
It was EMUI 4. The reason for all this was that I could not get the Nougat-update in any way.
I think that I might be on EMUI 5 now because I can't get the stock recovery from the B100/B132 package to boot but when I flash the recovery from B351 or similar it can boot but I'm, still not able to get any update to work.
Click to expand...
Click to collapse
I had same issue on mine. I updated to nougat manually with few bugs and then flashed custom arsenic ROM

Trouble rooting my g6

I'm coming to the g6 from an older Samsung. I figured that rooting this one would be just as simple, but was I ever wrong. I've gone through the guides available here, as well as guides on other sites, but no joy. I've probably restored my phone to the original system now 5 or 6 times. I'm hoping that someone can point me in the correct direction here.
The last couple of times I tried, here's what I did and what went wrong. I found a guide over at https://www.androidinfotech.com/root-moto-g6-and-g6-plus-pie/ that was fairly straight forward.
The first time I followed the instructions, booting to twrp failed but I figured that was because it never included flashing twrp to the phone. So I flashed it and used fastboot to boot the phone to the image. I then wiped the phone, flashed magisk and then did the same thing with no-verity-opt and rebooted.
On the reboot, the phone cycled through a couple of attempts and then was successful on the third try. But some things were broken. The battery indicator said I had 0% charge, and the phone refused to connect to wi fi. It also didn't recognize my network. And best of all, I've never achieved root. When I boot back into the bootloader, it comes up with the standard motorola file; not twrp.
Just FYI, I'm running pie.
Can anyone point me in the correct direction here? any help will be very much appreciated.

jmalmberg said:
I'm coming to the g6 from an older Samsung. I figured that rooting this one would be just as simple, but was I ever wrong. I've gone through the guides available here, as well as guides on other sites, but no joy. I've probably restored my phone to the original system now 5 or 6 times. I'm hoping that someone can point me in the correct direction here.
The last couple of times I tried, here's what I did and what went wrong. I found a guide over at https://www.androidinfotech.com/root-moto-g6-and-g6-plus-pie/ that was fairly straight forward.
The first time I followed the instructions, booting to twrp failed but I figured that was because it never included flashing twrp to the phone. So I flashed it and used fastboot to boot the phone to the image. I then wiped the phone, flashed magisk and then did the same thing with no-verity-opt and rebooted.
On the reboot, the phone cycled through a couple of attempts and then was successful on the third try. But some things were broken. The battery indicator said I had 0% charge, and the phone refused to connect to wi fi. It also didn't recognize my network. And best of all, I've never achieved root. When I boot back into the bootloader, it comes up with the standard motorola file; not twrp.
Just FYI, I'm running pie.
Can anyone point me in the correct direction here? any help will be very much appreciated.
Click to expand...
Click to collapse
Need a bit more info
What model G6 ? Software channel?
What build number of Pie are you trying to root?
You say "restored my phone to the original system now 5 or 6 times" what version and build number is that and how are you restoring it?

kc6wke said:
Need a bit more info
What model G6 ? Software channel?
What build number of Pie are you trying to root?
You say "restored my phone to the original system now 5 or 6 times" what version and build number is that and how are you restoring it?
Click to expand...
Click to collapse
Model is xt1925-6
Android version is ALI_RETAIL_9.0_PPS29.118-11-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
I'm restoring it using Minimal ADB and Fastboot, and flashing the files over.
A couple of other things I should probably say too.
1. The phone was originally running Oreo. About two weeks ago, Motorola pushed out PIE to me and I installed it. That caused a tone of problems... the biggest one was that you couldn't hear the phone anymore. Couldn't hear callers, ringing, notifications, etc... It might has well have been a doorstop. I tried to roll the phone back to Oreo doing a factory reset, but that didn't work either. Wiped out my IMEI and carrier. So I did a little research and found out that some other people had the same issue. They couldn't roll back so I figured I was stuck with Pie.
2. At that point, I unlocked the bootloader and downloaded the version above from a link in one of the forums and flashed it to the phone. For whatever reason, that cured the IMEI, carrier and sound issues. Since I've come this far and the phone doesn't have anything on it, I'd like to root what I have and get some of the capability that I had on the Samsung.
Thanks for your assistance on this.

jmalmberg said:
Model is xt1925-6
Android version is ALI_RETAIL_9.0_PPS29.118-11-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
I'm restoring it using Minimal ADB and Fastboot, and flashing the files over.
A couple of other things I should probably say too.
1. The phone was originally running Oreo. About two weeks ago, Motorola pushed out PIE to me and I installed it. That caused a tone of problems... the biggest one was that you couldn't hear the phone anymore. Couldn't hear callers, ringing, notifications, etc... It might has well have been a doorstop. I tried to roll the phone back to Oreo doing a factory reset, but that didn't work either. Wiped out my IMEI and carrier. So I did a little research and found out that some other people had the same issue. They couldn't roll back so I figured I was stuck with Pie.
2. At that point, I unlocked the bootloader and downloaded the version above from a link in one of the forums and flashed it to the phone. For whatever reason, that cured the IMEI, carrier and sound issues. Since I've come this far and the phone doesn't have anything on it, I'd like to root what I have and get some of the capability that I had on the Samsung.
Thanks for your assistance on this.
Click to expand...
Click to collapse
PPS29.118-11-1 has a lot of issues. downgrading doesn't seem possible. I thought we had it solved today but ran into the same issue with calls
Follow This thread for rooting

kc6wke said:
PPS29.118-11-1 has a lot of issues. downgrading doesn't seem possible. I thought we had it solved today but ran into the same issue with calls
Follow This thread for rooting
Click to expand...
Click to collapse
Oh, interesting, That's the thread I started with but couldn't get to work for me. That's when I went out and found the guide that I linked to in my original posting. Let me walk through the steps I used here to see if you can tell me where I went wrong.
1. Unlocked my bootloader.
2. Installed Minimal ADB & Fastboot.
3. Placed TWRP, in the Minimal ADB director on my PC and loaded Magisk, DM Verity, Magisk Manager apk to the SD card on my phone. (NOTE: the SD card isn't installed in the phone yet. I'll do that after doing the wipe. Just putting the software on it.)
4. Flashed TWRP to the phone and used Fastboot to load it.
5. Wiped the phone. Used advanced wipe and deleted the cache and data then rebooted to TWRP and did it again. At this point, I installed the SD card.
6. Rebooted the phone into TWRP and then selected install for DM Verity and again for Magisk.
7. Reboot and check for root using Rootcheck. I'm being told that I don't have root access.
What am I missing here?
Again, thank you for the assistance.

jmalmberg said:
Oh, interesting, That's the thread I started with but couldn't get to work for me. That's when I went out and found the guide that I linked to in my original posting. Let me walk through the steps I used here to see if you can tell me where I went wrong.
1. Unlocked my bootloader.
2. Installed Minimal ADB & Fastboot.
3. Placed TWRP, in the Minimal ADB director on my PC and loaded Magisk, DM Verity, Magisk Manager apk to the SD card on my phone. (NOTE: the SD card isn't installed in the phone yet. I'll do that after doing the wipe. Just putting the software on it.)
4. Flashed TWRP to the phone and used Fastboot to load it.
5. Wiped the phone. Used advanced wipe and deleted the cache and data then rebooted to TWRP and did it again. At this point, I installed the SD card.
6. Rebooted the phone into TWRP and then selected install for DM Verity and again for Magisk.
7. Reboot and check for root using Rootcheck. I'm being told that I don't have root access.
What am I missing here?
Again, thank you for the assistance.
Click to expand...
Click to collapse
You need to format data (type yes) In twrp

kc6wke said:
You need to format data (type yes) In twrp
Click to expand...
Click to collapse
That worked! Thank you very much!!! I really appreciate it!!!!

jmalmberg said:
3. Placed TWRP, in the Minimal ADB director on my PC and loaded Magisk, DM Verity, Magisk Manager apk to the SD card on my phone. (NOTE: the SD card isn't installed in the phone yet. I'll do that after doing the wipe. Just putting the software on it.)
.
Click to expand...
Click to collapse
What ver TWRP did you use?
Apparently there is an official version and a modified version to mount vendor-specific mount points?
Thanks,

Tigger31337 said:
What ver TWRP did you use?
Apparently there is an official version and a modified version to mount vendor-specific mount points?
Thanks,
Click to expand...
Click to collapse
I renamed the TWRP file I flashed "recovery.img" and I don't remember the original file name. When I boot to recovery mode it says 3.3.0-0. Hope that helps

jmalmberg said:
I renamed the TWRP file I flashed "recovery.img" and I don't remember the original file name. When I boot to recovery mode it says 3.3.0-0. Hope that helps
Click to expand...
Click to collapse
Yup, I solved it. Thanks. I ended up using 3.2.3.official.

Rooting; ending in bootloop help
Sorry if I am hijacking this thread; thought to discuss here as the title "Trouble rooting my g6" still applies.
I have:
XT1925-13 (Moto G6 ALI) running stock Android Pie with build ppss29.55-34.
I have issues when I tried to root. I followed these steps:
I downloaded the factory image “ALI_RETAIL_9.0_PPS29.55-34_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip” and flashed it first. The mobile restarted and went to the first screen to select a language.
I rebooted it into bootloader, ran the TWRP as a temp by command “fastboot boot twrp-3.3.0-0-Ali.img,” which asked for the password.
I pressed cancel, and then I wiped cache and data.
Via ADB I transferred “adb push Magisk-v20.0.zip /sdcard” and “adb push no-verity-opt-encrypt-6.1.zip /sdcard”.
Then from TWRP, I installed Magisk. Then when installing no-verity, it gave an error “updater process ended with an error: 1 error installing zip file ‘no-verity-opt-encrypt-6.1.zip’.
Rebooted the device with hope and ended in a boot loop.
I also tried to use Magisk-v19.4.zip in the above steps and also tried to skip no-verity-opt-encrypt-6.1.zip. All ended in boot loop.
Any idea why? Are there any guides for the combination XT1925-13 (Moto G6 ALI) running ppss29.55-34?
Many thanks for your time.

Here is a solution
Flash original boot in fastboot followed by TWRP and reboot in recovery.
Install Magisk 19.4 in TWRP (3.3.x Android 9 OK) and reboot
You can update to 20 in Magisk Manager later

Trouble flashing ROMs, beside stock

Hello everyone,
I have been using custom roms happily for a couple of devices for quite some time now. Now I have the ASUS rog2 and do have some trouble with it.
History:
I bought one a year ago and flashed it with various stuff and got happy with omnirom and it worked fine. I had trouble making TWRP permanent though. However, I did not care much about it, I keep data backups anyway.
At some day the phone software crashed and bricked itself. I could not boot the rom anymore and I formatted every partition and reflashed with TWRP. It failed. Every single time the best I could get was to get the device having a bootloop. I followed what I tend to read here, flash the rom twice on both partitions. I am not sure if that is actually needed If I switch the partition to the one I just flashed.
I then found out about the EDL and flashed the phone with the QPST/QFIL (I forgot which one) and the stock rom. This worked fine and the phone booted. Reflashing again with omnirom via TWRP got me back to bootloops again. So in the end I found myself happy with the stock rom, better than no phone. I used this for some time until I finally hard crashed my phone on the road. I now operate the phone on PC via SCRCPY and I got another ROG2.
Now here is my actual question, TLDR;
I want to flash it and basically went unlocking it, booting TWRP, formatting DATA, internal and caches - Flashed omnirom to both slots via ADB sideload. Now a similar thing happens. It does not even boot past the bootloader.
I flashed the latest stock rom from ASUS, released 27th of April, Android 11 and it boots up fine. I broke it again since I want to try nanodroid and probably did something wrong. No question about it.
What am I doing wrong in flashing a random not-stock-rom?
My experience is that usually it is the users fault, so I expect here I am doing something wrong, missing a stupid step.
I...
- boot TWRP with fastboot.
- flash a rom with ADB sideload, too lazy to copy the ROM to the internal storage. I think these are same anyway.
- reboot the phone, fastboot TWRP.
- flash a rom with ADB sideload to the other slot.
- Boot and fail
Appreciate help and insight on it. I like flashing and trying but I seem to have lost the idea of what I am doing with the A/B partitioning maybe or something with this phone series.

What I found out so far is weird.
Omnirom11 and 12 (just freshly released) can be flashed without error, but when I then look at the directory structure caused by this flash... there is none. As if nothing was written. Stock ROM leaves a directory tree as expected.
So /sdcard/Download, data ... etc. are not present.
Then depends on the TWRP versions: the twrp-3.4.0-0-I001D-Q-mauronofrio.img can be booted normally, it saves its settings on the disk normally. So make changes, reboot, the changes are present.
So far TWRP 3.6 made these changes but did not manage to store them.
When I ADB push a ROM to the phone onto sdcard root, the same funny thing happens. After reboot, the file is gone.

And weirder.... when I copy stuff via adb push to /sdcard/ it is visible over reboots only in the mentioned 3.4 TWRP. If I boot 3.6 then the /sdcard/ is empty. If I reboot back to 3.4, the files are visible.
Is there some problem with some sort of overlay space?

I think I found out why, although this is lazy guesswork.
Found a video by terminal_heat_sink and followed it original; you basically have to install the stock ROM on both slots. Then install omnirom OVER the stock rom. That is maybe how they get the camera, air trigger apps running inside omni (assumption only).

No replies, you are talking to your self.
Thanks for findings

Well, if I spent my time on it understanding it (I do hope so), then maybe it helps someone else and this doesn't end up as a soulless thread that has some xkcd 979 reminisence.