Database Info

[ROM][9.0_r46][mermaid] SonyAOSP

Code:
#include "std_disclaimer.h"
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)
Whats Working:
Probably everything.
Whats not Working:
Everything should work. If you find bug then please report it here: https://github.com/sonyxperiadev/bug_tracker/issues
Steps to flash:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash userdata userdata.img (WARNING: This will delete all your data on device so have a backup before doing anything)
fastboot flash oem NameOfOEMFile.img
You only need to flash userdata.img when you are going from Stock Firmware to AOSP or when you get issues with future builds.
Downloads:
ROM Dual SIM: Download all the files in that folder
ROM Single SIM: Download all the files in that folder
OEM: OEM Unzip this and flash it as OEM. Instructions above
XDA:DevDB Information
[ROM][9.0_r46][mermaid] SonyAOSP, ROM for the Sony Xperia X10 Plus
Contributors
Haxk20
Source Code: https://android.googlesource.com/platform/manifest
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Created 2019-09-11
Last Updated 2020-01-03

Reserved
NOW: Build for both Dual and Single SIM variants is in to download and test.

Reserved

Help, brothers! Dual sim dont work!!! The network appears and disappears. I bought a phone in Russia. presented to my sister in Belarus. And stumbled upon this problem. Need detailed instructions for flashing the radio module, please!

[email protected] said:
Help, brothers! Dual sim dont work!!! The network appears and disappears. I bought a phone in Russia. presented to my sister in Belarus. And stumbled upon this problem. Need detailed instructions for flashing the radio module, please!
Click to expand...
Click to collapse
Is this issue with the ROM ? Or is the phone running stock firmware ?
If its stock then please move the discussion to questions and answers in 10 Plus forum.
If this is issue with AOSP then please flash stock firmware to check if its working on stock firmware.

I flashed and was able to boot up ok. Initially the phone would only boot up to a blank screen. You could see the volume change when hit vol+ or vol-, the background would remain black. Pulling the SD card and Sim out cause a reboot automatically that seemed to resolve this. The connection to wifi and lte connects and unexpectedly drops. This happens over and over, I cannot make calls or use sms . The browser works fine with the limited LTE time and wifi. There is a vzwinternet apn, I cannot edit them. I wasn't sure if here or where to post. The link to github doest work. The rom is fine otherwise and easily root with magisk 20.1

yitakumini said:
I flashed and was able to boot up ok. Initially the phone would only boot up to a blank screen. You could see the volume change when hit vol+ or vol-, the background would remain black. Pulling the SD card and Sim out cause a reboot automatically that seemed to resolve this. The connection to wifi and lte connects and unexpectedly drops. This happens over and over, I cannot make calls or use sms . The browser works fine with the limited LTE time and wifi. There is a vzwinternet apn, I cannot edit them. I wasn't sure if here or where to post. The link to github doest work. The rom is fine otherwise and easily root with magisk 20.1
Click to expand...
Click to collapse
Link to github is fixed. Thank you for that.
I can say that the ROM worked just fine for me. I switched to different ROM few months ago now and this ROM has no support now. It is very likely you installed wrong OEM image. Please install the latest one for 4.9 kernel.
Because we have started working on 4.14 and well its still in alpha and those 4.14 images there are for us to test it properly.
The WiFi dropping out is known bug and sadly we do not have a fix for it yet.
Please open a bug report on that github repo and explain the issue and post logcat and dmesg files there.
EDIT: Ah my bad. It seems like i already pointed to the correct OEM image. Interesting that calls dont work.

Yo, i've installed the ROM and tried to flash gapps but they didn't install. Is there a way to flash them?

demonic8383 said:
Yo, i've installed the ROM and tried to flash gapps but they didn't install. Is there a way to flash them?
Click to expand...
Click to collapse
You will have to boot TWRP and flash it trough TWRP as AOSP recovery doesnt support flashing openGapps.
Booting up TWRP can be a bit tricky so well good luck.

Haxk20 said:
You will have to boot TWRP and flash it trough TWRP as AOSP recovery doesnt support flashing openGapps.
Booting up TWRP can be a bit tricky so well good luck.
Click to expand...
Click to collapse
Booting into TWRP after the first boot into AOSP is kinda impossible - as far as I know the only way to get TWRP to boot for this device is first to flash the stock ROM -> wait for it to boot completely -> go to bootloader through the ADB command (key combination results in stuck TWRP logo) -> then boot into TWRP. Getting there through the key combination results in black screen. TWRP is in unofficial state - it works only on the stock ROM and only with "fastboot boot twrp.img", it cannot be flashed yet. I'm using this version - https://forum.xda-developers.com/10-plus/development/recovery-twrp-3-3-1-0-unofficial-t3954147
Installing it is possible, however the touchscreen stops working in TWRP when booting the installed version.
Any suggestions on that?

demonic8383 said:
Booting into TWRP after the first boot into AOSP is kinda impossible - as far as I know the only way to get TWRP to boot for this device is first to flash the stock ROM -> wait for it to boot completely -> go to bootloader through the ADB command (key combination results in stuck TWRP logo) -> then boot into TWRP. Getting there through the key combination results in black screen. TWRP is in unofficial state - it works only on the stock ROM and only with "fastboot boot twrp.img", it cannot be flashed yet. I'm using this version - https://forum.xda-developers.com/10-plus/development/recovery-twrp-3-3-1-0-unofficial-t3954147
Installing it is possible, however the touchscreen stops working in TWRP when booting the installed version.
Any suggestions on that?
Click to expand...
Click to collapse
Unfortunately no. SODP does not officially support openGapps and this rom isnt maintained anymore as we are working on 10.
Also twrp for our device will never be flashable image as its useless to do so. We do not have recovery partition and thus have to have recovery in boot image and we build AOSP with stock recovery as its almost impossible to build it with TWRP using AOSP sources. And my guess is that TWRP wont get any better until it supports android 10 which is when we can finally start working on it.
Also on twrp i was able to boot to twrp using this ROM. It was tricky and im guessing the times i did boot it it was just luck.
So so far its a mess.

Haxk20 said:
Unfortunately no. SODP does not officially support openGapps and this rom isnt maintained anymore as we are working on 10.
Also twrp for our device will never be flashable image as its useless to do so. We do not have recovery partition and thus have to have recovery in boot image and we build AOSP with stock recovery as its almost impossible to build it with TWRP using AOSP sources. And my guess is that TWRP wont get any better until it supports android 10 which is when we can finally start working on it.
Also on twrp i was able to boot to twrp using this ROM. It was tricky and im guessing the times i did boot it it was just luck.
So so far its a mess.
Click to expand...
Click to collapse
Damn that's sad, thanks for the info tho

Xperia i4213 problems with sound after flash. No touch sounds. No sound in youtube. The sound appears for 15 seconds after clicking on the flashlight icon. please help fix

OP6 won't get past bootloader after upgrading from 16 to 17.1

I decided it was finally time to upgrade to the newer LineageOS 17.1 branch nightlies from my previous installation of 16, rebooted to recovery and sideloaded lineage-17.1-20201013-nightly-enchilada-signed.zip onto it from https://download.lineageos.org/enchilada .
After doing so it appears the recovery successfully updated, it has a new purple skin it didn't have before, however the actual ROM won't start. Instead it goes to fastboot mode and asks whether I want to Start/Restart/Recovery/etc, but I can only get into fastboot or recovery mode.
I've tried flashing older nightlies, but even with 20200922 the issue was still there. I did notice there was a ton of updates in that specific release so I wonder if anything is broken in there.. unfortunately that's also the oldest available nightly so without compiling my own there's no way I can test whether older ones are functional, unless someone here has an older version available perhaps.
I did notice doing adb sideload only makes it go to 47% before the phone goes to installing it, however maybe that's normal, I haven't used it in a while so I don't know for sure. I tried using ADB to push an image onto /tmp, however the new recovery only seems to have 'Apply from ADB' as option so I can't actually install it from there.
Does anyone have any ideas I could try, or perhaps an older LineageOS nightly from before 09-22 laying around somewhere? Any help or suggestions much appreciated!
PPS: Of course I forgot to mention but I also did a factory reset, but that did not help. unsure what else to try besides compiling a rom myself or trying other roms from the forums here, though I'd very much prefer having LineageOS..

I found the reason. I had to install the official Oneplus 6 ROM first, probably to get the right vendor binaries/kernel modules/drivers.
This is what I did:
- fastboot boot TWRP ( TWRP can be found here https://twrp.me/oneplus/oneplus6.html )
- wipe -> advanced wipe -> all the things (technically optional but if you want to get rid of GApps etc this is needed)
- adb sideload official OnePlus 6 'Oxygen' ROM ( https://www.oneplus.com/global/support/softwareupgrade/details?code=PM1574156173727 )
- reboot, fastboot boot TWRP
- run the 'copy partitions' zip from https://androidfilehost.com/?fid=8889791610682929240 to copy Oxygen to the other A/B partition
- Install latest build from https://download.lineageos.org/enchilada
- reboot, optionally boot TWRP again and install GApps, also optionally install TWRP, reboot, enjoy.
PS: Please note that after this you shouldn't switch A/B partition without first flashing another nightly or something over it, i.e fastboot boot twrp and install latest lineageos again, otherwise you'll end up booting the vanilla Oxygen rom

Oneplus 7 Pro - Sim cards no longer detected after latest OTA update

Hello all,
Everything was working on my rooted oneplus 7 pro, until I applied the latest OTA update. Once that was installed and the phone rebooted, my once working mobile network was no longer working. The phone says no sim card detected and every few seconds the default phone app displays the force close crash dialog. Has anyone else encountered this issue? It looks like rolling it back to the previous OxygenOS version is the only solution, but I'm not quite sure how to go about that safely. Any help would be greatly appreciated.
The device is using Magisk and TWRP
I also tried uninstalling Magisk, but that did not resolve the issue.

Have you tried just doing a reset in settings?
.This is how I install stock oos
You can use MSM tool to revert OOS, or you can try this step:
1. Reboot twrp/lineage recovery, format data. Reboot bootloader
2. Fastboot boot into TWRP FBEv2
3. Sideload official TWRP 3.5.2.9-0 installer (found on TWRP website). Reboot recovery
4. Copy OOS 11.zip to internal storage,or copy to otg drive,Flash OOS 11.zip. Reboot recovery again
5. Format data in OOS stock recovery & Reboot
6. After boot into OOS 11, just local upgrade rom .zip again, you will have OOS on both slots
7. If root is needed fastboot flash magisk patched boot.img

I'll give that a shot today. Do you have the links to MSM and OOS11.zip ? Thanks

ChimmyChanga said:
I'll give that a shot today. Do you have the links to MSM and OOS11.zip ? Thanks
Click to expand...
Click to collapse
Index of /list/Unbrick_Tools
I don't have the oos 11 off hand , I know you can download the latest and greatest directly from OnePlus website under support

I have the same problem i cant do nothing

No SIM card, or No network available -- Any help would be kind and appreciated.
At the start:
Oneplus 7 pro - GM1915 /US- active t-mob sim
LOS 18.1 (latest)
magisk 22.x upgraded along the way to current magisk 25.2, 8.0.7 app
Running LOS recovery ##// no issues since 18.1 came out
USB 2.0 port(s), good'ol red/white cable(s). ##// verified cables/ ports.. typical troubleshooting to rule them out)
Current Platform tools in $PATH
Issue. No SIM card.
Steps to masonry school:
I upgraded my LOS 18.1(magisk 25.2 persistent) to oos 12, then went to LOS 19.1. The update(s) went fine, or so it seemed... Booted fine. Still rooted. All's good until reboot. Then no SIM card found.
Mess around with turning off wi-fi, nfc, mobile data turn on airport mode... all iterations of that..
Occasionally it saw the sim card! Says, "Network unavailable." Shows T-mob on sim 1... Thinks it has 2 sim cards... ##// can't help but think this might be something
Set APN T-mob blah blah... wait.. go to local t-mob verify my sim is provisioned properly get new sim..
Their take is(of course) it's time to upgrade lol... Got a spare $800 laying around? If not, you can pay for it after there is no longer a recession lol... I digress(in distress)
##//
I started having worse problems upon performing the next 19.1 LOS_11-13-22 ota.
Immediately I got into a bootloader loop. I first tried my patched_110622-LOS_boot.img and got nothing but a seemingly successful boot, then those lovely "Power Off" words and back to bootloader.
Once back in fastboot I changed partitions(keep in mind I have not flashed anything to alter the LOS 19.1 boot restructuring at this point. Reboot. Same outcome. Bootloader loop. Booting to recovery, start, power off or bootloader all do the same thing... quickly reboot into bootloader.
I then decided to boot to twrp. I went ahead and did this
#>/ fastboot getvar all ###/// yielding partition a
#>/ fastboot flash boot_a twrp.img
#>/ fastboot boot twrp.img
The screen goes to "fastboot mode" and hangs. power+up_vol & it finally boots into twrp.
I then twrp installed the LOS update, which lead to more bootloops. Various dalvik cache/data and cache wipes after flashing, factory reset won't complete the reset... I have exhausted my limits of attempts at this point, so off to MSM I am.
All versions/drivers correct. On a win10Px64 now. Connects fine.
Now this is where it gets odd(to me anyway). I tried to go to stock oxy10, for GM1911AA and it hangs on the param preload. Something I don't remember seeing since 2020'ish. Tried multiple firmware until it took one, that was H.30. Successfully flashed. Booted. Found SIM card. Thought that was it.. Then I unplugged my usb cable from the op7p and *poof * reboot. After much digging and changing metedata preloads, various things to try to get this thing to work.
Current:
I can get it to run LOS 19.1 No SIM card found. Rooted with twrp and magisk no prob.
Just can't get it to work with the SIM, whether seen or not.
I am suspicious that I should have used H.31 for the MSM... however now it won't get past param preload with anything earlier than 11.5.1 Oxy 12. Also, I even went so far as to try flashing the CB firmware variant to see if it would take the T-mob firmware. Won't let me, says not compatible. So now I have a rooted op7pro that can only communicate via signal lol.. and not long at that...
Any thoughts/help/direction/suggestions, would be greatly appreciated.

Flashing LineageOS 18.1 after using LOS 19.1 results in fastboot loop

Hello there,
I have some sort of a problem (although my phone is still working.. yet)
I recently flashed my OnePlus 6 with LineageOS 19.1 (coming from OxygenOS 11.1.2.2).
I flashed "copy_partitions.zip" first and then the official LineageOS 19.1 ROM without GApps,
but because I wanted to use some features, which needed at least the presence of Google Services, I flashed the "LineageOS for microG" (19.1) ROM.
Which worked like a charm.. besides I was very unhappy because of the lack of customization regarding color-theming and the changes made to the QuickSettings of Android 12 in general..
So I thought I could clean flash LineageOS 18.1 / ("Lineage for microG") to get the old theming back..
So what I did was installing the official custom LineageOS recovery from 18.1 (because microG had none for 18.1),
hit "Factory Reset" and afterwards applied the Lineage 18.1 zip over adb.
A message "Update package is older than the current build, expected a build newer than timestamp [...] but package has timestamp [...] and downgrade not allowed" along with the Question to install anyway appeared right after sideloading it to the phone.
I decided to hit "Yes" because I don't needed to backup any data from the phone and wanted to wipe clean anyways... (which I thought I did with "Factory Reset)
So I installed and afterwards rebooted to recovery to flash Magisk aswell..
After rebooting to system then, the phone entered the fastboot loop.
No matter what I do, it still doesn't boot to system after installing 18.1 from LineageOS recovery (also tried with the newest microG recovery from 19.1).
I also known you would wipe system, cache and data (and maybe vendor aswell) prior to a clean custom ROM flash (via TWRP)..
So flashed TWRP 3.6.2 (latest) for enchilada and tried to wipe my system, vendor and cache, but didn't manage to find "system" or "cache" on the advanced wipe menu, so I formatted and wiped data and wiped vendor.
Then installed LOS 18.1 via TWRP also..
But same problem - fastboot only.
also after my TWRP journey, sometimes when flashing the LOS recovery and booting it, a message appears on screen:
Failed to bind mount /mnt/staging/emulated/media/0 [...]
The thing is, I can install LOS 19.1 (microG) without any problems and it would boot,
but I just want to downgrade and I found no guide for my device (or any with ramdisk and A/B slots)..
And there is also no link to MSMDownloadTools for Android 10 (because onepluscommunityserver.com is offline)..
The links from this post and some other posts I found aren't working anymore..
- Is there a way to go back to LineageOS 18.1? What would be the intended way (not doing a downgrade but flashing clean)?
- Is my phone softbricked somehow? (partitions broken or corrupt?)
- Is it a firmware problem?
(I am on security patch from November 2021)
But I don't know what exactly happened to my firmware when flashing Lineage 19.1 over OOS 11.1.2.2
This is my first post as it is my first Android phone/flashing experience in general.. so I hope I got everything right from all I found out until now..
I really appreciate any help / even if it is just saying I messed up and need to go EDL mode... (if it truly is the case)
Thanks in advance.
You people are great!
o/

screen not registering inputs after update to LineageOS 19.1

So I performed the upgrade from LineageOS 18.1 to LineageOS 19.1 via the following links: https://wiki.lineageos.org/devices/instantnoodle/fw_update & https://wiki.lineageos.org/devices/instantnoodle/install
All seemed well with no problems, but now when I boot up the device (instantnoodle) It starts up normally but then the screen does not register inputs.
So I can't get past the pin for my SIM or the startup screen you get when first startup LineageOS 19.1
What I have done is go back to recovery and did a Factory reset and format all data.
But this did not make things better..
Does anyone have an idea if there is a work around for this problem?

baseballbatboy26 said:
So I performed the upgrade from LineageOS 18.1 to LineageOS 19.1 via the following links: https://wiki.lineageos.org/devices/instantnoodle/fw_update & https://wiki.lineageos.org/devices/instantnoodle/install
All seemed well with no problems, but now when I boot up the device (instantnoodle) It starts up normally but then the screen does not register inputs.
So I can't get past the pin for my SIM or the startup screen you get when first startup LineageOS 19.1
What I have done is go back to recovery and did a Factory reset and format all data.
But this did not make things better..
Does anyone have an idea if there is a work around for this problem?
Click to expand...
Click to collapse
SOLVED. Used the newest OTA Update

my oneplus 8t screen not respond to touch after installing lineageOS 19 today

meowXda said:
my oneplus 8t screen not respond to touch after installing lineageOS 19 today
Click to expand...
Click to collapse
Which method of flashing did you utilize before installing the ROM, e.g., fastboot, TWRP, OrangeFox, etc?

rodken said:
Which method of flashing did you utilize before installing the ROM, e.g., fastboot, TWRP, OrangeFox, etc?
Click to expand...
Click to collapse
I followed the steps provided by the lineage os official website.

meowXda said:
I followed the steps provided by the lineage os official website.
Click to expand...
Click to collapse
Boot into TWRP instead of LOS Recovery
-- Factory Reset, then Format data / factory reset
-- Reflash ROM
You can always revert to a previous build to test for firmware issues.

rodken said:
Boot into TWRP instead of LOS Recovery
-- Factory Reset, then Format data / factory reset
-- Reflash ROM
You can always revert to a previous build to test for firmware issues.
Click to expand...
Click to collapse
I'm unable to turn off my phone now, because touchscreen doesn't work, only the physical buttons work

rodken said:
Boot into TWRP instead of LOS Recovery
-- Factory Reset, then Format data / factory reset
-- Reflash ROM
You can always revert to a previous build to test for firmware issues.
Click to expand...
Click to collapse
Do you have any instructions article or vlog about this

I wanted to get rid of the oxygen os because there was too many bugs..

meowXda said:
I wanted to get rid of the oxygen os because there was too many bugs..
Click to expand...
Click to collapse
Only the physical buttons work on your device which makes your device a candidate for a complete restore via MSM.
Code:
Boot into TWRP
type: fastboot boot twrp.img

rodken said:
Only the physical buttons work on your device which makes your device a candidate for a complete restore via MSM.
Code:
Boot into TWRP
type: fastboot boot twrp.img
Click to expand...
Click to collapse
Is it a bricked phone right?

meowXda said:
Is it a bricked phone right?
Click to expand...
Click to collapse
What does MSM stands for?

meowXda said:
my oneplus 8t screen not respond to touch after installing lineageOS 19 today
Click to expand...
Click to collapse
I would have to assume that you meant Lineage OS 19.1 for Kebab?

meowXda said:
What does MSM stands for?
Click to expand...
Click to collapse
If you are not familiar with the MSM Tool
-- Refer to this guide.

meowXda said:
Is it a bricked phone right?
Click to expand...
Click to collapse
Your device is not bricked
-- Hard bricked devices will show few or no signs of life. A hard bricked device does not power on or show any vendor logo
-- A "soft bricked" device may show signs of life, but fails to boot or may display an error screen
-- Soft bricked devices can usually be fixed

rodken said:
Your device is not bricked
-- Hard bricked devices will show few or no signs of life. A hard bricked device does not power on or show any vendor logo
-- A "soft bricked" device may show signs of life, but fails to boot or may display an error screen
-- Soft bricked devices can usually be fixed
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

rodken said:
Your device is not bricked
-- Hard bricked devices will show few or no signs of life. A hard bricked device does not power on or show any vendor logo
-- A "soft bricked" device may show signs of life, but fails to boot or may display an error screen
-- Soft bricked devices can usually be fixed
Click to expand...
Click to collapse
Can I flash my device with other rom such as PE without going back to oxygen os.

meowXda said:
Can I flash my device with other rom such as PE without going back to oxygen os.
Click to expand...
Click to collapse
If you are thinking about immediately flashing another Custom ROM without rectifying your current issue, you might be in for a rude awakening.
-- Usually, you can flash another Custom ROM by performing a complete factory reset.
-- In your case, start fresh and somewhat new from OOS
-- Remember not to flash a Custom ROM on top of another Custom ROM without clearing the cobwebs.
-- Read, proof-read and read a third time the installation instructions from the developer of each ROM.
OCD Moment: I find myself factory resetting three times between flashing different Custom ROMs

rodken said:
If you are thinking about immediately flashing another Custom ROM without rectifying your current issue, you might be in for a rude awakening.
-- Usually, you can flash another Custom ROM by performing a complete factory reset.
-- In your case, start fresh and somewhat new from OOS
-- Remember not to flash a Custom ROM on top of another Custom ROM without clearing the cobwebs.
-- Read, proof-read and read a third time the installation instructions from the developer of each ROM.
OCD Moment: I find myself factory resetting three times between flashing different Custom ROMs
Click to expand...
Click to collapse
I found that my touchscreen won't work even in the recovery mode(lineage os 19 recovery mode)

rodken said:
If you are thinking about immediately flashing another Custom ROM without rectifying your current issue, you might be in for a rude awakening.
-- Usually, you can flash another Custom ROM by performing a complete factory reset.
-- In your case, start fresh and somewhat new from OOS
-- Remember not to flash a Custom ROM on top of another Custom ROM without clearing the cobwebs.
-- Read, proof-read and read a third time the installation instructions from the developer of each ROM.
OCD Moment: I find myself factory resetting three times between flashing different Custom ROMs
Click to expand...
Click to collapse
I don't if it's the problem with lineageos or my phone itself