Database Develop

[RECOVERY] TWRP Recovery 2.6.3.0 | MoltenMotherBoard

FEEL FREE TO DONATE US FOR ALL WE'RE DOING FOR YOU!
For general discussions, bug reports and FAQ, write HERE!​
Credits:
MoltenMotherBoard team!
Downloads:
TWRP Recovery | Code.Google
Full sources:
MoltenMotherBoard sources: MoltenMotherBoard | Github
CyanogenMod sources: CyanogenMod | Github
Kernel: lge-kernel-p880 | Github
Changelog:
20131126
Fixed partition table
Code updates from TWRP, Google
20131120
First release
Issues:
Do you want to report an issue? Do it here!
In order to do it, create a new issue, choosing correct labels corrisponding to: Device/OS which you're using, ROM/project you're on, kind of issue.
Also, please, be sure you're running the ROM/project in the exact way we've provided it to you (do not create issues if you're using different
kernel, mod, plugins and dependencies we didn't tell to use).
General Questions: MoltenMotherBoard Projects | General Questions and Info
Official Mantainer(s): Mackief, ItachiSama, p4c0

Installation guide:
[Method 1° ~ fastboot]
Code:
$ adb reboot oem-unlock
$ fastboot flash recovery /PATH-TO-THE-IMG-FOLDER-ON-YOUR-COMPUTER/twrp.img
$ fastboot reboot
[Method 2° ~ adb] (put the recovery.img in your sdcard)
Code:
$ adb shell
$ su
# cat /sdcard/twrp.img > /dev/block/mmcblk0p1
# sync
# exit
$ exit
---------- Post added at 09:44 PM ---------- Previous post was at 09:43 PM ----------
I know you already have a 2.6.3.0 TWRP recovery, but it's based on 4.4 OMNI Android source code, and it's still in work-in-progress. This means, I'll keep it up-to-date with mainline sources.
Anyway, it would be appreciated if you report bugs here, so that I can check them!

"I know you already have a 2.6.3.0 TWRP recovery, but it's based on 4.4 OMNI Android source code, and it's still in work-in-progress. This means, I'll keep it up-to-date with mainline sources."
what does it mean ? Is 4.4 OMNI Android source code bad ? What did you use ? Whay is it better for us ?

EB20XY said:
"I know you already have a 2.6.3.0 TWRP recovery, but it's based on 4.4 OMNI Android source code, and it's still in work-in-progress. This means, I'll keep it up-to-date with mainline sources."
what does it mean ? Is 4.4 OMNI Android source code bad ? What did you use ? Whay is it better for us ?
Click to expand...
Click to collapse
It means it this versions supports Android4.4-based roms flashing.
It also means that it will be updated by the team.
Obviously, the team is doing a great work, why shouldn't it have done it?

Error or not? I wanted to make a backup copy of a recovery, and it turned out that there is no choice where to save it! Neither the internal memory card or an external card!

negativman said:
Error or not? I wanted to make a backup copy of a recovery, and it turned out that there is no choice where to save it! Neither the internal memory card or an external card!
Click to expand...
Click to collapse
Don't understand. What are you meaning?

mackief said:
Don't understand. What are you meaning?
Click to expand...
Click to collapse
I go into recovery, make a backup copy. Click "Backup", in the center of a blank window, and there is nowhere to select the item to save a backup (internal or external sdcard).

negativman said:
I go into recovery, make a backup copy. Click "Backup", in the center of a blank window, and there is nowhere to select the item to save a backup (internal or external sdcard).
Click to expand...
Click to collapse
OK. I'll check!

Think it's almost important for you to read this post: http://forum.xda-developers.com/showpost.php?p=47827005&postcount=11

mackief said:
It means it this versions supports Android4.4-based roms flashing.
It also means that it will be updated by the team.
Obviously, the team is doing a great work, why shouldn't it have done it?
Click to expand...
Click to collapse
what is exactly is the difference for kitkat ? Are the partitions different ?

EB20XY said:
what is exactly is the difference for kitkat ? Are the partitions different ?
Click to expand...
Click to collapse
Nope. At recovery-level, the biggest differencies are in the binary commands, then in Edify scripts.
Nothing relevant, but if you wanna flash a KitKat rom, you HAVE to use a 'KitKat' recovery!

mackief said:
Think it's almost important for you to read this post: http://forum.xda-developers.com/showpost.php?p=47827005&postcount=11
Click to expand...
Click to collapse
And where can I download it? Discovered the mistake about which I spoke to you?

negativman said:
And where can I download it? Discovered the mistake about which I spoke to you?
Click to expand...
Click to collapse
It should be a still-working-on broken feature by team.
It's a early recovery port, as the team is still making its own modifies on 4.4 code.
BTW, today I should release newer build

negativman said:
And where can I download it? Discovered the mistake about which I spoke to you?
Click to expand...
Click to collapse
Ok, I was wrong. That's an issue caused by the fact that TWRP doesn't support fstab v2 - the partition table - and, as our device tree is using this version of table, TWRP didn't load our partition and couldn't backup anything.

Just released new build of CWM.
Changelog:
Fixed partition table
Code updates from TWRP, Google
Follow us on Google+, Facebook & Twitter!
Cheers.

I have a few questions. They apply both to this and CWM.
Why have another build of both recoveries? I still understand TWRP, but @laufersteppenwolf has a released touch version of CWM. Why would anyone use a non-touch version?
The above doesn't apply if these builds have something special. If there is any, update the OP with the features list.
If #2 applies, you should share your sources.
Restore commit history as soon as you can here and in other device folder repos. Original creators deserve the credit. Also, rename the branch from cm9, it's misleading. If somebody tried to build CM9 with that branch, they surely couldn't.
What flags do you use for building TWRP? I don't see any in BoardConfig.mk.
What kernel sources do you use? Even if you didn't change anything in kernel source, put a link to the source you used in the OP.

Adam77Root said:
I have a few questions. They apply both to this and CWM.
Why have another build of both recoveries? I still understand TWRP, but @laufersteppenwolf has a released touch version of CWM. Why would anyone use a non-touch version?
The above doesn't apply if these builds have something special. If there is any, update the OP with the features list.
If #2 applies, you should share your sources.
Restore commit history as soon as you can here and in other device folder repos. Original creators deserve the credit. Also, rename the branch from cm9, it's misleading. If somebody tried to build CM9 with that branch, they surely couldn't.
What flags do you use for building TWRP? I don't see any in BoardConfig.mk.
What kernel sources do you use? Even if you didn't change anything in kernel source, put a link to the source you used in the OP.
Click to expand...
Click to collapse
Actually, they're based on 4.4 . No new features, nothing new.
Then, my device tree with CM9 has nothing to do with these recoveries; of course I'll add kernel sources and so on.
---------- Post added at 08:57 PM ---------- Previous post was at 08:46 PM ----------
Just updated OP and sources. Thanks for the report.

@Adam77Root is right, posting 2 equal projects is not only useless, but it could also be counted as spamming the forum (please don't get me wrong, it's the mod in me speaking ATM, not the person )
If you want to, I can give you access to my thread so we both can use it. I guess that'd be a win-win situation for everyone then
So, what do you say?

laufersteppenwolf said:
@Adam77Root is right, posting 2 equal projects is not only useless, but it could also be counted as spamming the forum (please don't get me wrong, it's the mod in me speaking ATM, not the person )
If you want to, I can give you access to my thread so we both can use it. I guess that'd be a win-win situation for everyone then
So, what do you say?
Click to expand...
Click to collapse
Nope, don't worry! If you think it's a problem, don't worry. Close my doubled threads! It's not a problem!

mackief said:
Nope, don't worry! If you think it's a problem, don't worry. Close my doubled threads! It's not a problem!
Click to expand...
Click to collapse
You know, that's exactly the problem/difficulty of being a mod in his own section
I personally do not have a problem with it, but if someone wants to, he can see it as spamming, which could get you in trouble some time.
So I usually try to avoid such situations as soon as possible
So all in all it's your call. I have no problem giving you access to my thread, so we both can keep on deving on it, but it would be less work for both of us if we'd share it. (which I actually could use ATM )
So you tell me what you want to do

[ROM][5.1.1][6.0.1][Haxynox] AOSP for i9300

​
What is this?
This is clean AOSP, tailored to exynos4 chipsets. It is part of the Haxynox Project.
The whaaaa?
The Haxynox Project. A ROM agnostic effort to minimize the h4xx on the exynos4 support in all of Androidness. If you've ever glanced upon the sources, or worked with them, you know exactly what we mean.
Who's behind that?
Currently, the dev line up is Ivan_Meler, dexter93 and myself. Special thanks to Cocolopes for the graphics and general testing.
Why did you bother doing that? And why AOSP?
Well.. nowadays custom ROMs are packed with features. While those are good, they often introduce bugs, or drift off the scope of AOSP as a whole.
Given the state of exynos4 support in the community, we decided to take on the exynos4 platform in AOSP, thus taking away any custom ROM flaws.
That way we can focus fixing issues and updating the trees, ensuring maximum compatibility and stability.
Blah.. you're kangers
Quite the opposite. We do take pride in our work, and honor the original authors of any code we've used. While the commits speak for themselves, here's a small list
[Credits roll]
SlimRoms
CyanogenMod
OmniRom
Replicant
Insignal
Nameless
and the rest of the community
[/Credits roll]
Ok, enough with the fancy stuff. Where's the Bug list?
Everything appears to be working so far. However keep in mind that this is an experiment opting to experienced users. Bugs are expected, please log and report them.
note: SEAndroid currently disabled.
Got Root?
Nope. This is completely non-rooted. Feel free to flash the latest SuperSU if you want root access.
Source
You can find our source code here​
XDA:DevDB Information
Haxynox i9300, ROM for the Samsung Galaxy S III I9300
Contributors
mcgi5sr2, Ivan_Meler, dexter93
Source Code: https://github.com/haxynox
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Testing
Created 2015-09-21
Last Updated 2015-12-12

Reserved
Changelog
20150921-1824: Changelog: Fixed recovery issues <<-- building
20150918-1152 : initial release [5.1.1_r16]
Downloads
haxynox-6.0-i9300-20151211-2331.zip 236.6MB
33aeb6e59ec686818cd4088502b75fd1
haxynox-i9300-20150921-1824.zip 208MB
MD5:130cea4633f0e9b278aeb3def6d67d08

Reserved
GApps
For Marshmallow 6.0 Roms I recommend the PICO version of OpenGapps
http://opengapps.org/
I have tested @dankoman s GApps ZERO package with this ROM and it works fine.
Here is the link
http://forum.xda-developers.com/slimroms/general/gapps-official-slim-gapps-trds-slimkat-t2792842
If you want to use anything else, please feel free to post about your experience, but be aware that if you GApps package of choice doesn't work on this AOSP rom, you'll need to convince the GApps maintainer to take a look into it. That being said I am happy to talk with any maintainer.

mcgi5sr2 said:
​
What is this?
This is clean AOSP, tailored to exynos4 chipsets. It is part of the Haxynox Project.
The whaaaa?
The Haxynox Project. A ROM agnostic effort to minimize the h4xx on the exynos4 support in all of Androidness. If you've ever glanced upon the sources, or worked with them, you know exactly what we mean.
Who's behind that?
Currently, the dev line up is Ivan_Meler, mcgi5sr2 and myself. Special thanks to Cocolopes for the graphics and general testing.
Why did you bother doing that? And why AOSP?
Well.. nowadays custom ROMs are packed with features. While those are good, they often introduce bugs, or drift off the scope of AOSP as a whole.
Given the state of exynos4 support in the community, we decided to take on the exynos4 platform in AOSP, thus taking away any custom ROM flaws.
That way we can focus fixing issues and updating the trees, ensuring maximum compatibility and stability.
Blah.. you're kangers
Quite the opposite. We do take pride in our work, and honor the original authors of any code we've used. While the commits speak for themselves, here's a small list
[Credits roll]
SlimRoms
CyanogenMod
OmniRom
Replicant
Insignal
Nameless
and the rest of the community
[/Credits roll]
Ok, enough with the fancy stuff. Where's the Bug list?
Everything appears to be working so far. However keep in mind that this is an experiment opting to experienced users. Bugs are expected, please log and report them.
note: SEAndroid currently disabled.
Got Root?
Nope. This is completely non-rooted. Feel free to flash the latest SuperSU if you want root access.
Source
You can find our source code here​
XDA:DevDB Information
Haxynox i9300, ROM for the Samsung Galaxy S III I9300
Contributors
mcgi5sr2, Ivan_Meler, dexter93
Source Code: https://github.com/haxynox
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Testing
Created 2015-09-21
Last Updated 2015-09-21
Click to expand...
Click to collapse
^
That is what we always needed. Finnaly someone made it. THANK YOU!

Is there any screen shoots? And do we need GAPPS or is it included? I will try the rom. Thanks for taking your time to make annother ROM for our old S3

@mcgi5sr2 Hey man, I really commend you for doing this. All I've seen lately is Archi, Moster, & co.'s work (Apologies to the many unmentioned) being used as "base" for other users "projects", and of course all the real work is going on at source in the aforementioned dev's repos. I feel XDA has become a really unoriginal and user- (rather than dev-) oriented place recently.
Of course, you're not radically rewriting the fundamental Android code like the PA team did with Hybrid, but with such a ***ch of a chipset* it's pretty sick that you've taken it head-on to get AOSP up.
Sorry if this was a bit aggrandizing, I've just been tired of the constant stream of Sammy ROM ports and zip kangs.
By the way, you refer to yourself: "Ivan_Meler, mcgi5sr2 and myself", I think it should be "Ivan_Meler, dexter93 and myself"?
* "If you've ever glanced upon the sources" ... you bet you ... a glance was too much, I'm scarred ...

Thread cleaned, if you think you spotted a bug please attach logfiles and/or what you tried to fix it yourself etc.
Whiskey
Forum Moderator

Excellent, thanks for creating a thread for haxynox. Better than people posting in the slim/omni thread.

Any idea on how to fix the fact im getting bootloops on this particular rom?

I waited a long time for this! Thanks to all team :highfive::highfive:

So,no disrespect here,does this rom have anything different than eg. Archidroid,temasek unofficials etc.??

The Funky Pear said:
So,no disrespect here,does this rom have anything different than eg. Archidroid,temasek unofficials etc.??
Click to expand...
Click to collapse
it's pure AOSP code ... without cyanogenmod 12.1 modifications.
if i understood correctly

The Funky Pear said:
So,no disrespect here,does this rom have anything different than eg. Archidroid,temasek unofficials etc.??
Click to expand...
Click to collapse
In layman's terms, this rom would make you feel like you're using stock android 5.1.1 that comes on nexus devices, without any modifications.

hello devs,
would it be possible to compile this rom with the old deodexed system data files ?
thx in advance for the reply

center clock - and - pointer to move with volume keys, only two options that i really need, is it possible to implement?

lukewilliams418 said:
Any idea on how to fix the fact im getting bootloops on this particular rom?
Click to expand...
Click to collapse
Could you provide a little more info please?
The Funky Pear said:
So,no disrespect here,does this rom have anything different than eg. Archidroid,temasek unofficials etc.??
Click to expand...
Click to collapse
No, in fact it has a lot less, but that is the point.
b0unty said:
hello devs,
would it be possible to compile this rom with the old deodexed system data files ?
thx in advance for the reply
Click to expand...
Click to collapse
The sources are all freely available, feel free to use them
lukaaa477 said:
center clock - and - pointer to move with volume keys, only two options that i really need, is it possible to implement?
Click to expand...
Click to collapse
see above...

myshakugan said:
In layman's terms, this rom would make you feel like you're using stock android 5.1.1 that comes on nexus devices, without any modifications.
Click to expand...
Click to collapse
Yea,sure it does,but i mean something else.
What i mean is, is there anything specific to the device changed, eg. Ram management,performance gains,optimizations etc.

mcgi5sr2 said:
Could you provide a little more info please?
No, in fact it has a lot less, but that is the point.
The sources are all freely available, feel free to use them
see above...
Click to expand...
Click to collapse
I used the latest version of TWRP to wipe all data and then I Installed the haxynox zip file with TWRP and then it just goes in a bootloop.

Bootloop
Enviado desde mi GT-I9300 mediante Tapatalk

any fix for this bootloop???

[ROM][9.0][TREBLE][UNOFFICIAL]MoKee Open Source Android Project

MoKee Open Source is the biggest non-profit Android Open Source development team in China, with members from all parts of the world. We follow the latest development from Google closely and improve various parts of Android according to the user habits. Being a non-profit organisation, we utilise our spare time and own funds to keep this passion alive. Therefore, the costs for the forum and servers are solely beared by us. In order to provide a good user experience, we only included a few preinstalls in the ROM. Along with the advertisements in the forum; we hardly get enough to pay for the bandwidth. The point is, those are our only source of income, however many developers choose to exclude them when releasing unofficial builds. Unlike CyanogenMod, we did not accept monetary help at the early stages, as in China, most people do not understand the meaning of “making a donation”. They would think of it as buying a service, which is conflicting with our objectives. Anyways, we still made it until today, and even started to provide third party developers a chance to utilise our OTA system. All of these are the fruit of our hard work and passion. We are proud of the happy users, and we are also proud of the support given to MoKee Open Source. Most importantly, we are proud of the improvements we have achieved all these while, and the advancements never stop.
Hit thanks if you like my work.
Downloads : "removed by moderator"
Gapps :== "removed by moderator"
Nano recommended
Twrp :== "removed by moderator"
Don't flash magisk, right now root not supported.
What's working ---
WiFi
Mobile data
bluetooth
mobile data
hotspot
gcam
magisk
If you want to root your pie rom
just simply flash the magisk zip file via twrp.
then install the magisk manager apk manually and open that then you can the installed magisk version.
also you can check your rooot via rootchecker apk
Test this build and let me know the issue, so we could fix those issue.
Special thanks to all oxygen team and all group mates, who provides logs.
Testing thanks
@Cirno
@remicaa
@luciano Henrique
@Mario Resurrected
Credits:
MactavishAO
Hard_rock83
Mokee Development Team
LineageOS
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Based On: Mokee Open Source Project
Version Information
Status: stable

First android 9? Things are coming! Thank you for the hard work.

Android-9.0(Pie)
It's just first build which booted properly. So there would be lots of bugs.
Let me know the bugs, so we could work on fixing bugs.

fgaurano said:
First android 9? Things are coming! Thank you for the hard work.
Click to expand...
Click to collapse
It's just first build, so there would be lots of bugs, let me know the bugs, so we could fix them.

Gapps?
MI MAX 2 cihazımdan Tapatalk kullanılarak gönderildi

OTA uptades avaible?

Appreciate the effort of developers who bought us PIE flavor for our beloved MAX2

Finally Pie on the Max 2, this is what so many have been waiting so long for. Can't wait for Gcam 6.1.

not
finger print,
double click open the screen
not blutouth
not xposed

Theseusperse said:
Finally Pie on the Max 2, this is what so many have been waiting so long for. Can't wait for Gcam 6.1.
Click to expand...
Click to collapse
GCam 6.1 working on oreo

Which twrp to be used?

ridershahmir said:
GCam 6.1 working on oreo
Click to expand...
Click to collapse
How?!?! What APK are you using for the Mi Max 2? I've tried everything, even wiped my phone and used every ROM out there and can't get anything to work. I'm specifically talking about the latest 6.1 GcCam from the Pixel 3 (Pixel3Mod) with the latest low light enhancement features from the new photo core. I'd love to know how you got it working on the Mi Max 2 on Oreo.
None of the ones on this list work for me so far:
https://www.celsoazevedo.com/files/android/google-camera/
And that's literally all of them as far as I know, including highly specialised device variants. As far as I'm aware it's Pie only.

cem_uar said:
not
finger print,
double click open the screen
not blutouth
not xposed
Click to expand...
Click to collapse
What can you expect from an alpha build .lol. isn't it enough you got pie.

scissordragonboy said:
What can you expect from an alpha build .lol. isn't it enough you got pie.
Click to expand...
Click to collapse
Is camera working on pie?

reversegear said:
Appreciate the effort of developers who bought us PIE flavor for our beloved MAX2
Click to expand...
Click to collapse
If you want to handle this Pie project you can compile from source.
My trees are open on GitHub.

Downloading. Is there a problem with IMEI?

Hucksley said:
Downloading. Is there a problem with IMEI?
Click to expand...
Click to collapse
IMEI -- no problem is rest regarding this issue -- mobile data is working properly, just don't play with network section
And add access point in data section then mobile data will work properly.

scissordragonboy said:
IMEI -- no problem is rest regarding this issue -- mobile data is working properly, just don't play with network section
And add access point in data section then mobile data will work properly.
Click to expand...
Click to collapse
Camera? Totally not working?

scissordragonboy said:
IMEI -- no problem is rest regarding this issue -- mobile data is working properly, just don't play with network section
And add access point in data section then mobile data will work properly.
Click to expand...
Click to collapse
I'm already using rom and I want to thank you for your great work.
I will use it until the next updates come out and I will notify any unknown bug so far.
Thanks again for the work!
(Sorry for the English)

hard to download

[DEV][WIP][LINUX] PostMarketOS for G610F

LinuxForExynos Group Presents​A WONDERFUL NON WORKING LINUX DISTRO THAT DOESNT EVEN TRY TO BOOT​ANYWAYS TO FLASH IT:​First, flash TWRP or OrangeFox​Secondly, flash Astrako's Partitioner Script from here https://forum.xda-developers.com/t/...epartition-script-for-vendor-support.4143541/ . What this does is it makes your system partition to 4GB, which is good for PostMarketOS. Flash this and reboot to recovery. WARNING: ALL DATA WILL BE GONE​Thirdly, download PostMarketOS from the links given below and flash it via PBRP. it is automatic and please do NOT opt in for Full Disk Encryption as it will break the phone.​Fourth, reboot and enjoy! For now this only has a terminal with a touch keyboard. The login is `user` with the password `12345`.​​If it works for you or doesn't PLEASE let me know and please do note that this is alpha build software and you should not use it as a daily driver or expect your phone to be stable. Thank you.​
Contributors:
@Astrako for his repartition script
@Parthib and DedSec#3307 for their VPS
@zpunout and @thinhhdk for their time and effort and testing the product
@thinhhdk for patches
AFH and GitHub for letting me host the files
Download V1.1:
pmos-on7xelte-31JAN.zip | by Otus9051 for Galaxy J7 Prime
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Release Boots initramfs, no networking yet, includes LXDE. · LinuxForExynos/pmos-samsung-on7xelte
This build now has a booting initramfs and working usb. Networking and display and other stuff isnt working.
github.com
Download V1:
pmos-samsung-on7xelte.zip | by Otus9051 for Galaxy J7 Prime
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
https://files.catbox.moe/fxphum.zip
pmos-samsung-on7xelte.zip
drive.google.com
I am working on a pmOS port to G610F. Currently there is a port for the J710F (https://wiki.postmarketos.org/wiki/Samsung_Galaxy_J7_(2016)). This new port will be based on that. Due to me breaking my grandma's phone, she actually has the G610F, also yes she is outstation so I don't have the phone, so, basically I need testers for the new port. Every single development enhancements, milestones and builds will be provided here. As of now, I have the source at https://github.com/LinuxForExynos/pmos-samsung-on7xelte. If you have any suggestions or are interesting in developing or testing, please reply to this thread or hit me a dm at Otus9051#5971 in discord. This project won't be possible without you. Also, I am developing Halium for it too, so this thread will also have this too.
Requirements for testing:
Knowledge with Linux (atleast upto knowing how to cd or cp, the more the better)
Time (a lot)
My PBRP build (https://forum.xda-developers.com/t/...-pitch-black-recovery-project-v3-1-0.4287985/) [actually any twrp build but this one has a better terminal ui and looks cool]
A G610F, with my pbrp
Requirements for development:
why am i putting this but anyways
Knowledge with Alpine Linux and Linux Kernels
Knowledge with DTBs and stuff and android ofc
A laptop/pc with Linux (not wsl) and atleast 6gb ram and a dual core processor
-------------

Otus9051 said:
MODS PLEASE SEE THIS!!!
Click to expand...
Click to collapse
My apologies for my earlier mistake. Carry on my friend.
Cheers: Badger50

Badger50 said:
My apologies for my earlier mistake. Carry on my friend.
Cheers: Badger50
Click to expand...
Click to collapse
It's ok man

I have here a G610Y. My knowledge of Linux (Debian/Ubuntu/Mint) I think is somewhere between beginner and intermediate. I am familiar with flashing to partitions on the phone with Heimdall though.

zpunout said:
I have here a G610Y. My knowledge of Linux (Debian/Ubuntu/Mint) I think is somewhere between beginner and intermediate. I am familiar with flashing to partitions on the phone with Heimdall though.
Click to expand...
Click to collapse
I will be releasing the first release of pmOS (probably non-booting) in a couple of weeks. Thanks for your interest and help!

@zpunout new release in a bit, getting the dtbs rn
btw if you have discord or anything hit me a dm with your tag, matrix works too. just dont wanna clutter this thread up

Otus9051 said:
@zpunout new release in a bit, getting the dtbs rn
btw if you have discord or anything hit me a dm with your tag, matrix works too. just dont wanna clutter this thread up
Click to expand...
Click to collapse
Matrix works for me. I just set up an account

zpunout said:
Matrix works for me. I just set up an account @zpunout:matrix.org
Click to expand...
Click to collapse
DMed ye

Ran into a big problem: pmbootstrap is broken

its workin'

@zpunout get ready with latest stock, DO NOT BOOT PLEASE I BEG YOU, and flash my recovery instead of stock recovery at the time of flashing. and do not boot to system.

still compiling

See the Main Post for Links

> (doesn't work lol[if you thought it would well no your dreams are gone])
Can confirm, doesn't boot, stuck at samsung splash screen, charging doesn't show percentage so maybe kernel problems.

Yeah, I and zpunout are working on it. Infact, WE HAVE NO LEADS LOL so uh yeah i have to do some digging i guess... The biggest problem is that I don't have the device itself right now so it makes it a bit difficult to work and apply patches. My current workflow is Patch > Build > Upload > Test > Repeat
And uploading takes a long time where I live like a 200MB file takes 10mins to upload... Yeah...

Otus9051 said:
Yeah, I and zpunout are working on it. Infact, WE HAVE NO LEADS LOL so uh yeah i have to do some digging i guess... The biggest problem is that I don't have the device itself right now so it makes it a bit difficult to work and apply patches. My current workflow is Patch > Build > Upload > Test > Repeat
And uploading takes a long time where I live like a 200MB file takes 10mins to upload... Yeah...
Click to expand...
Click to collapse
I want to be a tester, i sent a friend request on discord

It might seem that development is dead but its not. It takes more than a year to complete each port. Please have patience. You can track our progress at https://github.com/LinuxForExy7870/

failed to mount /system_root

serelafo said:
failed to mount /system_root
Click to expand...
Click to collapse
Its a common problem. It has still installed nonetheless.

FYI, project still alive, working on Android 12 currently.

Question TWRP

We badly need Twrp for this device. To me actually even Twrp was surpassed by that great small recovery OS which was Orangefox, still functioning well in i.e. Oneplus 5.
There is a Chinese web site (will post it in the future, don't have it with me now) which lists a series of tools for the latest Oneplus devices, and TWRP support is listed as in development.
Let's hope it comes soon...

Any news?

It will be nice at least to have in stock recovery option to clear cache, eventual dalvik cache

We do not have a dedicated recovery partition on our device (it's actually the same for MOST recent A/B devices). The recovery is actually part of the main operating system, basically using the same kernel as the main system. Even if we manage to compile a custom recovery for our device, it won't be really useful for installing zips, as it will be overwriting itself if installing those zips.

In realitty is a midranger phone... so not so important... And if you look at our device on xda forum is almost dead. Unused.

We have a TWRP in testing. Will publish after some testing and if everything goes according to the plan.
Currently we have used files from CPH2423 i.e. 80W variant.
Will update soon.

hamsteer said:
Any news?
Click to expand...
Click to collapse
We have TWRP tree ready we will start testing soon for both 80W and 150W.
(PS: I am not the dev.)

yashaswee1708 said:
We have TWRP tree ready we will start testing soon for both 80W and 150W.
(PS: I am not the dev.)
Click to expand...
Click to collapse
Any news?

HomiRuim said:
Any news?
Click to expand...
Click to collapse
Devs will be releasing in a few days

yashaswee1708 said:
Devs will be releasing in a few days
Click to expand...
Click to collapse
Finally That, now we are waiting for custom firmware

yashaswee1708 said:
Devs will be releasing in a few days
Click to expand...
Click to collapse
where do you post twrp?

daytooo said:
where do you post twrp?
Click to expand...
Click to collapse
It's still under development; the TWRP tree is 80% complete. Just few rounds of testing and it should be available for public.
NOTE: As of now TWRP will be only for OOS12.
As soon as public release is available, I will create a new thread on xda and I can also let you know here.
If you want to stay updated, you can join the 10R/Ace Discussion group - https://t.me/OnePlus10ROfficial

any update guys?
yashaswee1708 said:
It's still under development; the TWRP tree is 80% complete. Just few rounds of testing and it should be available for public.
NOTE: As of now TWRP will be only for OOS12.
As soon as public release is available, I will create a new thread on xda and I can also let you know here.
If you want to stay updated, you can join the 10R/Ace Discussion group - https://t.me/OnePlus10ROfficial
Click to expand...
Click to collapse
Any Update bro ?​

Helll7 said:
any update guys?
Any Update bro ?​
Click to expand...
Click to collapse
The devs are still working on it. Some issues were there. They want it to stable before they can release it, since no unbrick tool is there.
Simultaneously they are also working on Device Trees for custom ROM.