Develop Bugs

Cyanogen 12.1 test builds for Raspi2

Download:
https://www.androidfilehost.com/?w=files&flid=39635
Let me know if these work out for you. You can smack the ramdisk to the original kernel zimage to make the boot.img partition.
Source will be released if this works...
Cheers!

hey!
i would really love to test this.
im just now sure how to get the different .img-files to my SD card (win or osx)
do i partition manually first and then write each IMG seperately? what file system?
i'm really interested in this since im planning to construct my very own RPi2-Android-Car-Headunit...

I really wold like to test this out, I would really appreciate when someone gives install instructions

@Childofthehorn
don't take this the wrong way but can you highlight the zImage your referring too?
are you talking about the android generic device kernel?
are you talking about pulling it from another distro?
just a tad more explanation and I can give this a try. I have scoped out your git for some other clues but come up empty

feherneoh said:
As there is no kernel provided, try raspbian kernel first
I will check it later as I have a "working" lollipop kernel for rPi2 somewhere, but I have to find it
Click to expand...
Click to collapse
Thanks, if we can get some source of stuffs working i would give building a crack as well

feherneoh said:
Building CM12.1 using the same device tree that I used for AOSP 5.1, will see if it works
Click to expand...
Click to collapse
Hi, news about it?

feherneoh said:
I'm buildind inside screen, so I cannot scroll (I have no idea, how to do that) and the error message is outside of the 80x50 terminal I'm using
Click to expand...
Click to collapse
Many thanks for your effort.
If you could build it and boot it, please create your own topic so you are able to upgrade changelog and so on..

feherneoh said:
I'm buildind inside screen, so I cannot scroll (I have no idea, how to do that) and the error message is outside of the 80x50 terminal I'm using
Click to expand...
Click to collapse
Well, You could redirect the output to a file and read that file using vim. To redirect to file run
Code:
command > file.txt

Is it possible to write install instructions?

yes,I want to obtain the install instruction.
Sent from my MI 2S using Tapatalk

I'm interested too!

partition boot as fat,system as ext4, cache as ext4, and data as ext4, then restore file.
Sent from my MI 2S using Tapatalk

feherneoh said:
I know how to do this, and I would need to use command &> file.txt, as I need stderr, too
Click to expand...
Click to collapse
To put also stderr to the same file use:
Code:
command > file.txt 2>&1
To use different files:
Code:
command > file.txt 2> err_file
Another possibility to see output and stderr on screen and also put it in a file:
Code:
command 2>&1 | tee file.txt

i have a working rom for raspberry pi 1, 2 and 3. the only issue im having is getting the wifi and bluetooth to work. any suggestions?

How to install it ?

Badfiler said:
How to install it ?
Click to expand...
Click to collapse
Why install something that isn't working?

[CHINA DEV 7.5.5] System dump

http://bigota.d.miui.com/7.5.5/sagit_images_7.5.5_20170505.0000.00_7.1_cn_da4bcba334.tgz
Ext4 unpacker and ext2explore do not always work properly on my W10 laptop :/

https://mega.nz/#!yQdgACCa!sudwBkM-X-Dmt365NPOGJlDdRqn_x4vzNDuiBOEMxEM
Done it by myself

Sorry, but what is that? What can I do with your file on my device?

hoaithy92 said:
Sorry, but what is that? What can I do with your file on my device?
Click to expand...
Click to collapse
Use it to flash a Chinese MIUI by fastboot.

Unable to flash zip files in Magisk and TWRP

Please I need help. I can no longer install zip files in Magisk or TWRP. Each attempt returns with installation failed... Please what do I do?

Datbro said:
Please I need help. I can no longer install zip files in Magisk or TWRP. Each attempt returns with installation failed... Please what do I do?
Click to expand...
Click to collapse
Post log.

Log deleted

Datbro said:
-
Click to expand...
Click to collapse
Please post the actual recovery log file from TWRP.

Please I can't find the log file in TWRP. Where can I get it from?

Datbro said:
Please I can't find the log file in TWRP. Where can I get it from?
Click to expand...
Click to collapse
Advanced/save log

I'll upload the actual Logfile

Please that's the log I got from TWRP

Datbro said:
Please that's the log I got from TWRP
Click to expand...
Click to collapse
Would you please remove the copy and paste and just post the actual log file. Its rather against xda rules to post huge logs like that.
Anyway looks like your issue is that /data is not mounted.
You need to FORMAT /data and patch the boot partition.

Thanks. Noted for the copy and paste.
However, formatting data has to be done with TWRP?
What do I use to patch the boot partition?

Datbro said:
Thanks. Noted for the copy and paste.
However, formatting data has to be done with TWRP?
What do I use to patch the boot partition?
Click to expand...
Click to collapse
See the link below for info.
https://forum.xda-developers.com/samsung-a-series-2017/development/xcc-t3591448

Thanks.. I have read it and I'll follow the instruction and hoping to return with success story.

Thank you so much. It worked but I noticed that there is about 6-7 seconds delay when you want to unlock the phone.
Any fix for that?

TWRP openrecoveryscript on A/B partitions

I am trying to automate my nandroid backups but apparently a/b devices mount /data/cache as /cache so I don't know how to make twrp read my openrecoveryscript file from /data/cache. Any help would be greatly appreciated.

darkfire404 said:
I am trying to automate my nandroid backups but apparently a/b devices mount /data/cache as /cache so I don't know how to make twrp read my openrecoveryscript file from /data/cache. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you solved this problem? if yes how did you solve your problem?

mauronofrio said:
Have you solved this problem? if yes how did you solve your problem?
Click to expand...
Click to collapse
I haven't yet. I don't know if it's possible without modifying TWRP to read from /data/cache on startup since the cache partition doesn't exist on a/b devices

I doubt it will help or not...
But I noticed when sideloading an OTA, that whatever the .zip file would be called would "extract" to the folder "sideload" (in the /sdcard, but there's a good chance that it's its own folder in the root directory...) as sideload.zip (i believe...I can easily be wrong....but I remember it was a simple and obvious one-word name....). I remember having issues with TWRP processing the initial .zip file, so I would extract the initial OTA .zip file, then manually input what was extracted into that folder under that specific name and TWRP was able to automatically start processing the OTA....
I'm not sure, but maybe you might find this process beneficial and/or interesting/inspiring...

darkfire404 said:
I am trying to automate my nandroid backups but apparently a/b devices mount /data/cache as /cache so I don't know how to make twrp read my openrecoveryscript file from /data/cache. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried to put the script in /data/cache/recovery/openrecoveryscript ? if the folder doesn't exist try to create it

mauronofrio said:
Have you tried to put the script in /data/cache/recovery/openrecoveryscript ? if the folder doesn't exist try to create it
Click to expand...
Click to collapse
I did that. It didn't work

I'm encountering the same behavior. OpenRecoveryScripts are not being executed.
Running TWRP-3.2.3-0, Pixel 2 on Android 9.0.

UncertainSpin said:
I'm encountering the same behavior. OpenRecoveryScripts are not being executed.
Running TWRP-3.2.3-0, Pixel 2 on Android 9.0.
Click to expand...
Click to collapse
I'm having the same problem too. I have been using Tasker to write to /cache/recovery/openrecoveryscript because that's all I could find online.
I intend to have this in the Run Shell command in Tasker.
chmod 0777 /cache/recovery
echo "backup SDCRBM weeklybackup" > /cache/recovery/openrecoveryscript
echo "reboot" >> /cache/recovery/openrecoveryscript
chmod 664 /cache/recovery/openrecoveryscript
I have verified that it is writing the file, and TWRP seems to be erasing it which from what I gather it is supposed to do. But it is not executing the command when TWRP starts.
LineageOS 16.0 unofficial/ TWRP 3.2.3 on Samsung Galaxy S7.

We need to bring TWRP developers awareness for this issue, it's already reported on GitHub (https://github.com/omnirom/android_bootable_recovery/issues/221) but not acknowledge by TWRP team... If you have a GitHub account, vote for that issue, if you know someone from TWRP, bring them attention to that.
IMO, having this script working is very important for truly automated backups of our devices, let's get this issue fixed...

rfgamaral said:
We need to bring TWRP developers awareness for this issue, it's already reported on GitHub (https://github.com/omnirom/android_bootable_recovery/issues/221) but not acknowledge by TWRP team... If you have a GitHub account, vote for that issue, if you know someone from TWRP, bring them attention to that.
IMO, having this script working is very important for truly automated backups of our devices, let's get this issue fixed...
Click to expand...
Click to collapse
Yup indeed needs to be fixed..

Getting GSI ROM's for g4

Hello, this sounds a little bit impossible but i made some progress with my friend. We made a vendor partition, edited the TWRP but we stuck at the part of making a vendor. Can the g4 community do it? I think you can, especially @steadfasterX. UsU, FWUL and SALT were masterpieces.

Also, it looks so hard. Because there is no phone with S808 and A9.

If you need to know how did i made the vendor partiton, i can help.

I use H815TR UsU'd. If that helps.

You should describe much more detailed what you did and what problems you have after that.

steadfasterX said:
You should describe much more detailed what you did and what problems you have after that.
Click to expand...
Click to collapse
First i put the parted file on the phone and run it via terminal in TWRP.
cp /sdcard/parted /sbin/ && chmod 755 /sbin/parted was the command i used.
Second, i unmounted every partition and wrote the command: parted /dev/block/mmcblk0
After, I wrote p to see what number was my userdata (it was 50) and i wrote rm 50.
After i deleted the userdata, i wrote
mkpart userdata ext4 6359MB 30GB
mkpart vendor ext4 30GB 31.3GB
to make a vendor partiton.
Finally, i did a format data and @MeizuM6T edited the TWRP.
I did everything with @MeizuM6T .

Now i need vendor files.

The easiest way is to simply copy /system/vendor from an existing ROM tbh.

steadfasterX said:
The easiest way is to simply copy /system/vendor from an existing ROM tbh.
Click to expand...
Click to collapse
Most roms contain system-as root, obviously this is where @Emo19 and me get stuck.
Would connecting the vendor via FSTAB be enough to boot?

MeizuM6T said:
Most roms contain system-as root, obviously this is where @Emo19 and me get stuck.
Would connecting the vendor via FSTAB be enough to boot?
Click to expand...
Click to collapse
Well then i don't get the problem.
We mimic a vendor partition since (iirc) pie and to follow android standards we already moved everything needed to /system/vendor including config updates where needed pointing to /vendor. I would say 98% of this move is done already for the rest see e.g: https://github.com/LGgFour/android_device_lge_g4-common/search?q=System/vendor
Ofc currently /vendor is just a symlink to /system/vendor but for the system it feels like it has a separate vendor partition already.
So my guess was you just copy everything from /system/vendor and put that in your /vendor partition and if we made everything right and you fix the rest of the few /system/vendor paths it should just boot. Ofc you would need to update fstab to point to the dedicated vendor partition then. Does that help?

steadfasterX said:
Well then i don't get the problem.
Click to expand...
Click to collapse
The vendor has successfully connected but the treble support is still not visible.
Vendor is connected to the system and is working now, how should we arrange for treble?

MeizuM6T said:
The vendor has successfully connected but the treble support is still not visible.
Vendor is connected to the system and is working now, how should we arrange for treble?
Click to expand...
Click to collapse
no idea really. I have never ported anything to treble. just the other way around

steadfasterX said:
no idea really. I have never ported anything to treble. just the other way around
Click to expand...
Click to collapse
Thanks, I think we need to write "ro.treble.enabled = true" via build.prop. then we will try to install some GSI Roms.

MeizuM6T said:
Thanks, I think we need to write "ro.treble.enabled = true" via build.prop. then we will try to install some GSI Roms.
Click to expand...
Click to collapse
well I dont think its THAT easy. I was serious about the other way around so take a look at what I did for another device:
https://code.binbash.rocks:8443/MVA-VoLTE/android_device_samsung_j5y17lte/commits/branch/eos-q/search?q=treble&all=true
https://code.binbash.rocks:8443/MVA-VoLTE/android_device_samsung_exynos7870-common/commit/ab2567dc82fbdb2a21aa3ea28572dd18e5b7fb79
https://code.binbash.rocks:8443/MVA-VoLTE/android_kernel_samsung_exynos7870/commit/b8e2cf570dfd383fb3a4497d6b53d51c9226ca7b
Ofc you would do the opposite then what the commits showing and ofc I dunno if thats enough and haven't checked what needs to be adapted etc but it should give you an idea

steadfasterX said:
well I dont think its THAT easy. I was serious about the other way around so take a look at what I did for another device:
Click to expand...
Click to collapse
I doubt it will open either, it shouldn't be that simple. I will look at what you have thrown