Related
First question does Osprey's hardware support Android O ?
Prob does but we'll prob not be able to have some features
Osprey's hardware didn't supported android N too but we got it with custom rom... I think this will happened with android O too
Our device is in list to get los 15 ie. android O
androidbaba said:
Our device is in list to get los 15 ie. android O
Click to expand...
Click to collapse
Well that's a pleasant news. And considering the awesome dev support our device has, I'm pretty sure we'll be getting plenty of Android O ROMs to try out.
adityak1303 said:
Well that's a pleasant news. And considering the awesome dev support our device has, I'm pretty sure we'll be getting plenty of Android O ROMs to try out.
Click to expand...
Click to collapse
Just for fyi, lineageosdownloads.com is not the official site (download links are redirected to actual linageos.org (org, not com)). So information they give cannot be verified unless the official linageos blog posts something about it.
It's still a long way. Source code hasn't been out yet. After AOSP code is pushed, linageos team will work on it, but considering the limited resources (unlike CyanogenMod), it can take a while. After the base is ready, then devs will focus on building device specific images and fix bugs. Only then android o will be roaster ready. Other derivative ROMs will take more time obviously.
We can't be sure if 8.0 will be fully compatible with our device. We don't have official Nougat kernel sources and proprietary blobs (AFAIK), also from what I've observed so far, the farther apart the last official firmware and target firmware are, the harder it is to keep a ROM unmodified and yet stable & functional.
Our device shouldn't die that easy though, as newer Moto devices with similar hardware as osprey and Merlin have been released.
Broadcasted from Zeta Reticuli
Just like i say earlier our device it wasn't supported android N but we got it thanks to our awesome developers. I think they won't let us down with android O too.. it maybe take a little time but i think we will have android O for our moto g 2015
sorry for my bad english
Hopefully we get O, and hopefully O comes default with the pixel nav because redacting that would take effort thats not worth it now that nexus is dead .
Nikos dima said:
Just like i say earlier our device it wasn't supported android N but we got it thanks to our awesome developers. I think they won't let us down with android O too.. it maybe take a little time but i think we will have android O for our moto g 2015
sorry for my bad english
Click to expand...
Click to collapse
Our device does support Nougat, it is evident by the presence of custom ROMs (and even a stock port). The only reason we didn't get a OTA was because the company didn't provide us. The Moto ROM and these custom ROMs all are based on AOSP code.( Technically, if the company released the full source of their ROM and features, then we could build stock ROMs too)
And yes, you are right, it may take a little while but eventually we should see the ROMs coming
But the absence of latest device specific proprietary stuff and official kernel sources forces devs to look for other branches to fill the gaps and get newer thingies working. In some places it's not possible to implement a certain feature and an older feature is modded to make it work, for example before the official marshmallow OTA was out, we already got marshmallow ROMs but it had some hacky workarounds for radio (I don't know if it was updated after that), same goes for early Nougat when camera was becoming a problem. The camera is still not perfect (check linageos thread), working correctly on some apps and glitching on others. Newer software, newer challenges.
But codes are not exactly like food though, mixture of old and new ones is not always bad. But the blobs and drivers sometime give headache
Broadcasted from Zeta Reticuli
Have faith on our awsome developer we will surely have android O
Well, Android Oreo is out. I really hope that Osprey will get it soon.
https://source.android.com/devices/architecture/treble
according to this website,
"With Treble, a new stable vendor interface provides access to the hardware-specific parts of Android, enabling device makers to deliver new Android releases simply by updating the Android OS framework—without any additional work required from the silicon manufacturers"
Does this mean if someone gets Lineage OS 15 or OTA of Stock Android 8.0, they will receive all the updates from google from security patch to new Android versions (If the hardware is capable of running that version obviously!)?
---------- Post added at 09:47 AM ---------- Previous post was at 09:46 AM ----------
If that so, Manufacturers can just update all the devices which theoretically can run android O , it will be a onetime work, after that it'll be easy to update the devices
That would be amazing. Let's wait for a developer opinion.
I managed to build AOSP 8.0_r4 for osprey with SELinux disabled and tons of warnings, using cm14.1's files with some edits. Though for some reason the kernel doesn't seem to boot (I tried with linage os and squid kernel)
I attached the boot.img it built if someone more expert wants to look at it (I didn't manage to find anything wrong)
Flashing the file results in fastboot "Error: failed to load the kernel"
android1111 said:
I managed to build AOSP 8.0_r4 for osprey with SELinux disabled and tons of warnings, using cm14.1's files with some edits. Though for some reason the kernel doesn't seem to boot (I tried with linage os and squid kernel)
I attached the boot.img it built if someone more expert wants to look at it (I didn't manage to find anything wrong)
Flashing the file results in fastboot "Error: failed to load the kernel"
Click to expand...
Click to collapse
Hi, Alberto97 (the official maintainer of lineageOS for osprey) has successfully booted android O on osprey. If you can get in contact with him, he might help you.
PS. Don't bug him about ETAs. He'll release when he feels its ready.
adityak1303 said:
Hi, Alberto97 (the official maintainer of lineageOS for osprey) has successfully booted android O on osprey. If you can get in contact with him, he might help you.
PS. Don't bug him about ETAs. He'll release when he feels its ready.
Click to expand...
Click to collapse
Wow.. nice to hear this.. dude how do you know about this
rahul9999 said:
Wow.. nice to hear this.. dude how do you know about this
Click to expand...
Click to collapse
I follow him on G+. He posted the good news there.
https://plus.google.com/+AlbertoPedron/posts/Av6Knfnsja2
adityak1303 said:
I follow him on G+. He posted the good news there.
https://plus.google.com/+AlbertoPedron/posts/Av6Knfnsja2
Click to expand...
Click to collapse
Thanks For the information
I want to know about Merlin.. is it gonna get Android O? And if yes , when?
Abhishek17599 said:
I want to know about Merlin.. is it gonna get Android O? And if yes , when?
Click to expand...
Click to collapse
Hello,
There is no confirmation yet about this from official maintainer
Yes it should be get as Osprey already successfully booted it.. but don't ask for ETA
With HD10 (2017) unlock/TWRP available - link (thanks to @k4y0z!!!), the next natural question is a custom ROM. The subject may turn out to be slightly trickier than what appears at first sight.
Let's have a discussion thread to brainstorm on this and not wonder off-topic in other places.
I had seen @DragonFire1024 & @Rortiz2 tried to work on that, so feel free to chime in as necessary.
What we have:
HD10 (2017) chipset - MT8173 (2+2 cores), there is an beefier brother to it, MT8176 (2+4 cores). For most practical purposes both chipsets seem almost identical software-wise.
MT8173 was introduced in March 2015 (time of Lollipop domination - Android 5). MT8176 was introduced in October 2016 (getting toward Nougat - Android 7).
The efforts up to date on a custom ROM for this chipset appear to be by @Goayandi, who is still active on XDA, so his work could be used a starting point. I believe @Goayandi was working on Android 7 (Nougat). Here are some of the original links:
XDA : Mediatek MT8173 & MT8176 development
Reddit: Mediatek MT8173 & MT8176 development
Stuff from Amazon for MT8173 (both HD10 2017 and FireTV2) is Lollipop-vintage (Android 5), other devices with these chipsets seem to have reached Nougat (Android 7). It does not appear that there is any known MT8173/MT8176 device with Android 8, or 9 (or is there?). It seems that @diplomatic has an Asus like this with Nougat.
At the moment, it feels a a Nougat custom ROM might be the ceiling for the device, given the difficulties of finding proprietary pieces for MTK chipsets to get Android 8 or 9 going. Now, even Android 7 is still a bit of a challenge, given limited prior success.
More thoughts/ideas? Feel free to fill this thread with random thoughts as much as you want - that's what it's for!!!
I'm really looking forward to an AOSP experience on this tablet, to be honest. Can't wait to see what they come up with!
GuyInDogSuit said:
I'm really looking forward to an AOSP experience on this tablet, to be honest. Can't wait to see what they come up with!
Click to expand...
Click to collapse
As long as I can set up everything properly I'm ready to go. I've managed to get past script issues I think. I can get it to flash and it boots to the orange fire logo and sits for eternity. This was the same result pre and post TWRP. So at this point it's probably the installation and improper setup of the tree and files. If someone can point me to a guide or give me instructions on how to add support to my AOSP working directory, that would be great. This bit of the leg work is hard as there really aren't any guides that are detailed enough or that work anymore.
Secondly, I think if we are going to use a kernel, we either use the 7.0 source, or just use the kit I have to build our own. Amazon cherry picked the crap out of the kernel practically to the bare bones, so I think expanding from it is just a waste of time, especially since we have the kit that does a lot of the work for us, including providing signatures and the tools to sign etc.
Sent from my Galaxy Tab3 Lite 7.0 using XDA Labs
I wouldn't mind even if the best ROM available is a 6.0 Marshmallow one. Anything that gives AOSP on a stable base for the Fire HD10 is going to be awesome.
DragonFire1024 said:
As long as I can set up everything properly I'm ready to go. I've managed to get past script issues I think. I can get it to flash and it boots to the orange fire logo and sits for eternity. This was the same result pre and post TWRP. So at this point it's probably the installation and improper setup of the tree and files. If someone can point me to a guide or give me instructions on how to add support to my AOSP working directory, that would be great. This bit of the leg work is hard as there really aren't any guides that are detailed enough or that work anymore.
Secondly, I think if we are going to use a kernel, we either use the 7.0 source, or just use the kit I have to build our own. Amazon cherry picked the crap out of the kernel practically to the bare bones, so I think expanding from it is just a waste of time, especially since we have the kit that does a lot of the work for us, including providing signatures and the tools to sign etc.
Sent from my Galaxy Tab3 Lite 7.0 using XDA Labs
Click to expand...
Click to collapse
So did you end up successfully unbricking your device?
I did share working amazon kernel sources in the HD-10 Unlock thread.
They worked well in my tree to compile TWRP.
k4y0z said:
So did you end up successfully unbricking your device?
I did share working amazon kernel sources in the HD-10 Unlock thread.
They worked well in my tree to compile TWRP.
Click to expand...
Click to collapse
Sorry for being out of the loop - were those kernel sources for Lollipop? Or does it even matter at all - meaning they would be good to go with newer Android versions as well.
Could you link to those posts in here?
bibikalka said:
Sorry for being out of the loop - were those kernel sources for Lollipop? Or does it even matter at all - meaning they would be good to go with newer Android versions as well.
Could you link to those posts in here?
Click to expand...
Click to collapse
They will likely need some patches to work with newer versions, but it's a good start I'd say.
It's the most recent version amazon has published.
k4y0z said:
So did you end up successfully unbricking your device?
I did share working amazon kernel sources in the HD-10 Unlock thread.
They worked well in my tree to compile TWRP.
Click to expand...
Click to collapse
I am working on it as we speak. I downloaded the zip from the second post in this thread, 1.1. extracted and ran sudo ./bootrom-step.sh. said it can't find build/payload directory it doesn't exist. So I assume I use that folder from the other unbricking thread copy it to yours? Assuming its a yes to that question, I keep getting the serial port errors. I also had to delete a setting in udev (this was my own addition to it) and rebooted PC. Now I am having a cigarette. When I do it again, if I still get serial port errors, time to try each of the 8 or 10 other ports on the PC.
Sent from my MotoG3 using XDA Labs
---------- Post added at 06:23 PM ---------- Previous post was at 06:21 PM ----------
bibikalka said:
Sorry for being out of the loop - were those kernel sources for Lollipop? Or does it even matter at all - meaning they would be good to go with newer Android versions as well.
Could you link to those posts in here?
Click to expand...
Click to collapse
The one I have and provided is a source to 7.0. looks nicely stocked.
Sent from my MotoG3 using XDA Labs
bibikalka said:
With HD10 (2017) unlock/TWRP available - link (thanks to @k4y0z!!!), the next natural question is a custom ROM. The subject may turn out to be slightly trickier than what appears at first sight.
Let's have a discussion thread to brainstorm on this and not wonder off-topic in other places.
I had seen @DragonFire1024 & @Rortiz2 tried to work on that, so feel free to chime in as necessary.
What we have:
HD10 (2017) chipset - MT8173 (2+2 cores), there is an beefier brother to it, MT8176 (2+4 cores). For most practical purposes both chipsets seem almost identical software-wise.
MT8173 was introduced in March 2015 (time of Lollipop domination - Android 5). MT8176 was introduced in October 2016 (getting toward Nougat - Android 7).
The efforts up to date on a custom ROM for this chipset appear to be by @Goayandi, who is still active on XDA, so his work could be used a starting point. I believe @Goayandi was working on Android 7 (Nougat). Here are some of the original links:
XDA : Mediatek MT8173 & MT8176 development
Reddit: Mediatek MT8173 & MT8176 development
Stuff from Amazon for MT8173 (both HD10 2017 and FireTV2) is Lollipop-vintage (Android 5), other devices with these chipsets seem to have reached Nougat (Android 7). It does not appear that there is any known MT8173/MT8176 device with Android 8, or 9 (or is there?). It seems that @diplomatic has an Asus like this with Nougat.
At the moment, it feels a a Nougat custom ROM might be the ceiling for the device, given the difficulties of finding proprietary pieces for MTK chipsets to get Android 8 or 9 going. Now, even Android 7 is still a bit of a challenge, given limited prior success.
More thoughts/ideas? Feel free to fill this thread with random thoughts as much as you want - that's what it's for!!!
Click to expand...
Click to collapse
Hi bibikalka,
Very good idea this thread.
What you can do, is to port a port a ROM of another MT8173 tablet to the FIRE HD10 2017.
This works and I have tested it on my BQ Aquaris M8 (MT8163) it has a similar MTK so I guess it will work. I have ported for example a ROM of an asus zenpad that uses MT8163 and at least the rom boots.
BTW: Oreo on MT8176: https://www.xda-developers.com/alldocube-x-10-5-inch-android-8-1-oreo/
DragonFire1024 said:
I am working on it as we speak. I downloaded the zip from the second post in this thread, 1.1. extracted and ran sudo ./bootrom-step.sh. said it can't find build/payload directory it doesn't exist. So I assume I use that folder from the other unbricking thread copy it to yours? Assuming its a yes to that question, I keep getting the serial port errors. I also had to delete a setting in udev (this was my own addition to it) and rebooted PC. Now I am having a cigarette. When I do it again, if I still get serial port errors, time to try each of the 8 or 10 other ports on the PC.
Click to expand...
Click to collapse
Apparently I forgot to add the right files.
give me a moment.
---------- Post added at 06:47 PM ---------- Previous post was at 06:36 PM ----------
DragonFire1024 said:
I am working on it as we speak. I downloaded the zip from the second post in this thread, 1.1. extracted and ran sudo ./bootrom-step.sh. said it can't find build/payload directory it doesn't exist. So I assume I use that folder from the other unbricking thread copy it to yours? Assuming its a yes to that question, I keep getting the serial port errors. I also had to delete a setting in udev (this was my own addition to it) and rebooted PC. Now I am having a cigarette. When I do it again, if I still get serial port errors, time to try each of the 8 or 10 other ports on the PC.
Click to expand...
Click to collapse
I have fixed the upload, please use amonet-suez-v1.1.1.zip
DragonFire1024 said:
The one I have and provided is a source to 7.0. looks nicely stocked.
Click to expand...
Click to collapse
But these aren't amazon sources are they?
They probably are missing some drivers then.
But if they are for mt8173 they could be used as a source to patch the amazon-sources.
k4y0z said:
Apparently I forgot to add the right files.
give me a moment.
---------- Post added at 06:47 PM ---------- Previous post was at 06:36 PM ----------
I have fixed the upload, please use amonet-suez-v1.1.1.zip
But these aren't amazon sources are they?
They probably are missing some drivers then.
But if they are for mt8173 they could be used as a source to patch the amazon-sources.
Click to expand...
Click to collapse
I'll provide a link in a few. Trying your fix now.
Sent from my Galaxy Tab3 Lite 7.0 using XDA Labs
Rortiz2 said:
Hi bibikalka,
Very good idea this thread.
What you can do, is to port a port a ROM of another MT8173 tablet to the FIRE HD10 2017.
This works and I have tested it on my BQ Aquaris M8 (MT8163) it has a similar MTK so I guess it will work. I have ported for example a ROM of an asus zenpad that uses MT8163 and at least the rom boots.
BTW: Oreo on MT8176: https://www.xda-developers.com/alldocube-x-10-5-inch-android-8-1-oreo/
Click to expand...
Click to collapse
Excellent find! Here is a review link:
https://forum.xda-developers.com/ge...ldocube-x-review-media-playback-king-t3902539
Alldocube X kind of has 2x of everything compared to HD10 2017, but at 2x price I wonder how fast Oreo would be on HD10 and if 2Gb of RAM would cut it. But this is definitely the device to copy if one wants latest and greatest!
And here is a thread with misc download links for ROMs:
https://forum.xda-developers.com/ge...n/10-5-inch-super-amoled-2560-x-1600-t3821327
bibikalka said:
Excellent find! Here is a review link:
https://forum.xda-developers.com/ge...ldocube-x-review-media-playback-king-t3902539
Alldocube X kind of has 2x of everything compared to HD10 2017, but at 2x price I wonder how fast Oreo would be on HD10 and if 2Gb of RAM would cut it. But this is definitely the device to copy if one wants latest and greatest!
And here is a thread with misc download links for ROMs:
https://forum.xda-developers.com/ge...n/10-5-inch-super-amoled-2560-x-1600-t3821327
Click to expand...
Click to collapse
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Rortiz2 said:
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Click to expand...
Click to collapse
This is great news! I am eagerly awaiting more info about this AOSP ROM
Rortiz2 said:
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Click to expand...
Click to collapse
ffstudios said:
This is great news! I am eagerly awaiting more info about this AOSP ROM
Click to expand...
Click to collapse
Alright, we have both an eager developer, and a tester!!! Just remember, avoid bricking !
Very recently (March 2019) @wangyiling seems to have put together a LineageOS 15.1 ROM for MT8173/8176 - link, so hopefully we can re-purpose that for HD10. It's great to have an active developer elsewhere looking at the same thing!
It feels that if there is at least something that boots the kernel, it'd be a huge step forward.
bibikalka said:
Alright, we have both an eager developer, and a tester!!! Just remember, avoid bricking !
Very recently (March 2019) @wangyiling seems to have put together a LineageOS 15.1 ROM for MT8173/8176 - link, so hopefully we can re-purpose that for HD10. It's great to have an active developer elsewhere looking at the same thing!
It feels that if there is at least something that boots the kernel, it'd be a huge step forward.
Click to expand...
Click to collapse
If my testing on ROMs caused my brick, we have to be careful. I've been testing and flashing test ROMs for months now and never bricked like this. I think I may know what happened and if I'm right, I'm not sure what effect if any this will have on flashing a rom. According to the fstab.mt8173 file in the root directory, the partitions we flash for a rom, aren't part of the EMMC: data, system, cache are all ext4. All other partitions are however EMMC. So if I recall correctly, I did list the system as EMMC in the build script, but did intend to remove it. I made a last minute adjustment to the script and didn't change that part though.
https://forum.xda-developers.com/showpost.php?p=78542898&postcount=618
Sent from my MotoG3 using XDA Labs
Rortiz2 said:
I will try to port lineage 15.1 but the safest thing is that it will not work.
I have also ported an AOSP Rom for anyone who wants to try it. Tomorrow I will give more info.
Click to expand...
Click to collapse
I too am willing to test. Just let me know and I'll be sure to wear my best testing pants. [emoji41]
Sent from my SM-G9650/DS running stang5litre Pie ROM
AOSP ROM TEST 1 (suez)
Ok guys so here's the first test for the AOSP ROM.
First of all, I am not responsible for bricked devices. It is you who decides to try the ROM without knowing if it will work because it is a TEST.
DOWNLOAD: Removed
INSTALL INSTRUCTIONS:
- Boot TWRP
- Make NANDROID BACKUP
- Make wipes
- Format data
- Install ROM
- Reboot
Please. If the installation fails, send the errors and if the ROM starts, comment on the bugs.
Regards!
Rortiz2 said:
Ok guys so here's the first test for the AOSP ROM.
First of all, I am not responsible for bricked devices. It is you who decides to try the ROM without knowing if it will work because it is a TEST.
DOWNLOAD: https://mega.nz/#!C5dEQIKR!14BcGTiaT-xsrPUc-AxmWrTLj92Y5A2VgeNX2VA1uUE
INSTALL INSTRUCTIONS:
- Boot TWRP
- Make NANDROID BACKUP
- Make wipes
- Format data
- Install ROM
- Reboot
Please. If the installation fails, send the errors and if the ROM starts, comment on the bugs.
Regards!
Click to expand...
Click to collapse
Sounds good to me. Won't have a chance till later this afternoon/evening to give it a whirl, but when I do I'll definitely share my results and any information that may be useful. Thank you!
Sent from my SM-G9650/DS running stang5litre Pie ROM
Rortiz2 said:
Ok guys so here's the first test for the AOSP ROM.
First of all, I am not responsible for bricked devices. It is you who decides to try the ROM without knowing if it will work because it is a TEST.
DOWNLOAD: https://mega.nz/#!C5dEQIKR!14BcGTiaT-xsrPUc-AxmWrTLj92Y5A2VgeNX2VA1uUE
...
Please. If the installation fails, send the errors and if the ROM starts, comment on the bugs.
Click to expand...
Click to collapse
Which AOSP version is this? Could you try that Oreo Lineage stuff from @wangyiling at some point as well?
One of these days we'll have a ROM developer and a tester within the same person Too bad we've lost @DragonFire1024 since his tablet got bricked
Actually this question for developers will this miracle happens again?
Any news or work in progress
I haven't seen a single bacon-related commit in LOS17 gerrit so far.
We just got to wait until see either official or unofficial LineageOS 17
Someone around here said: "...started having a look at Android 10".
Of course ... the work has begun.
any AOSP release?! unfortunately it seem opo developers are not active as much as 4 years ago :'(
Yup, there is bootable and somewhat working Android 10 build for OPO. Long live the bacon indeed. But yeah our device is getting old and developers have moved to the other devices.
in my opinion our device working like charm and it's has as much as worth to support it for more several years.
A Android 10 version of MSM Xtended was released today.
isaacpixel said:
A Android 10 version of MSM Xtended was released today.
Click to expand...
Click to collapse
I'm Lineage OS with microG user. I did install it temporary and it seem good Rom. Please support developer to guaranty better device support.
Here was a Guide. Someone said people don't care about Me or My Work so...
does it require an unlock bootloader?is it prerooted?does it have drm keys? sorry for the questions.
nolihowell said:
does it require an unlock bootloader?is it prerooted?does it have drm keys? sorry for the questions.
Click to expand...
Click to collapse
Yes, You need to be unlocked, otherwise is there no chance to flash with fastboot. Besides the rooting of the Kernel is everything Stock. Everything works so far even with GSIs
Where did you get the Customized EU 55.1.A.0.748 J9210 ?? I does not appear on XperiFirm.
nreuge said:
Where did you get the Customized EU 55.1.A.0.748 J9210 ?? I does not appear on XperiFirm.
Click to expand...
Click to collapse
My Bad, it is the UK one... I'm also still waiting for customized EU which was always My Choice for Xperia Sources and Development. I'm currently working with GSIs on My Xperia 5 but think i will Release some Stock work soon since i prefer Xperia Android actually over AOSP...
Users will be able to use any Base Firmwares (Android 10) for it but i will personally Test on Custom EU :fingers-crossed:
@Miustone will you be releasing a boot.img for the latest security patch?
fcb13 said:
@Miustone will you be releasing a boot.img for the latest security patch?
Click to expand...
Click to collapse
Just downloaded J9210_Customized EU3_1320-1208_55.1.A.3.49_R2B. I will release a Update after getting it running on My X5 this Weekend alongside with a Magisk Module Update for XPIXELERIA https://github.com/Miustone/XPIXELERIA
BR
Miustone said:
Just downloaded J9210_Customized EU3_1320-1208_55.1.A.3.49_R2B. I will release a Update after getting it running on My X5 this Weekend alongside with a Magisk Module Update for XPIXELERIA https://github.com/Miustone/XPIXELERIA
BR
Click to expand...
Click to collapse
@Miustone Sorry to bother you here, but I am struggling with patching the Xperia 1 .sin boot image with any current version of Magisk. I've tried a few versions but they all fail to create the image from the .sin file. Any help you can provide is greatly appreciated!
I should add, I was trying to use these instructions: https://forum.xda-developers.com/xperia-1/how-to/xperia-1-root-guide-t3938304
charlatan01 said:
@Miustone Sorry to bother you here, but I am struggling with patching the Xperia 1 .sin boot image with any current version of Magisk. I've tried a few versions but they all fail to create the image from the .sin file. Any help you can provide is greatly appreciated!
I should add, I was trying to use these instructions: https://forum.xda-developers.com/xperia-1/how-to/xperia-1-root-guide-t3938304
Click to expand...
Click to collapse
Just read the first Post of this Thread and You will get everything You'll need.
EDIT: Since You just need a .img File for Magisk is there no need to share it with Me actually. Just patch it in the Magisk Manager App and flash it with fastboot afterwards.
Miustone said:
Just read the first Post of this Thread and You will get everything You'll need.
EDIT: Since You just need a .img File for Magisk is there no need to share it with Me actually. Just patch it in the Magisk Manager App and flash it with fastboot afterwards.
Click to expand...
Click to collapse
Ah, okay. Thanks. One last stupid question.. for the firmware, does it matter if the img file comes from the Android 10 firmware? I am planning to flash my Xperia 1 with PE, which is still Pie.
charlatan01 said:
Ah, okay. Thanks. One last stupid question.. for the firmware, does it matter if the img file comes from the Android 10 firmware? I am planning to flash my Xperia 1 with PE, which is still Pie.
Click to expand...
Click to collapse
Prefer a newer Base Firmware over a newer GSI. A Android 9 GSI will run better with Android 10 Kernel as vice versa. Pie will be no Problem if You run Android 10 Vendor and Kernels. Happy flashing! :fingers-crossed:
EDIT: There are also PE Android 10 Builds out there... https://forum.xda-developers.com/pr...iscussion/gsi-expressluke-built-gsis-t4003457
help me
hi i need a boot.img for my xperia 1 j8170 please help me 10 (55.1.a.3.107)
This method has always been magisk module not friendly. audio compat worked. But once i through more at it it bricked device and had to reflash with new flasher
Hi
Can you please patch this file for me (Device = J9210 Dual | Firmware = 55.1.A.3.149)
boot_X-FLASH-ALL-A2CD.7z
Kind Regards
After I get root, can I completely deGoogle my phone? Since there is no Lineage OS for XPERIA 5, can I manually get rid of all of Google's stuff?
Help is greatly appreciated.
Thank you.
BuyXRPnow! said:
After I get root, can I completely deGoogle my phone? Since there is no Lineage OS for XPERIA 5, can I manually get rid of all of Google's stuff?
Help is greatly appreciated.
Thank you.
Click to expand...
Click to collapse
Yes You can. But You can also install LOS 17.1 from the GSI Forums. I also did Instructions for flashing GSI Treble ROMs in the Xpiera 5 Guides Forum :good:
After that You may want to have Magisk to pass safetynet and to install MicroG or NanoDroid to get everything working. I'm actually running PHHs AOSP with My SOM Module and it's one of My Favorites so far. You may also like Havoc OS Official which also comes as no Google Apps Version. You can do the same on Havoc like You can on LOS but + endless Costomization
Miustone said:
Yes You can. But You can also install LOS 17.1 from the GSI Forums. I also did Instructions for flashing GSI Treble ROMs in the Xpiera 5 Guides Forum :good:
After that You may want to have Magisk to pass safetynet and to install MicroG or NanoDroid to get everything working. I'm actually running PHHs AOSP with My SOM Module and it's one of My Favorites so far. You may also like Havoc OS Official which also comes as no Google Apps Version. You can do the same on Havoc like You can on LOS but + endless Costomization
Click to expand...
Click to collapse
I really appreciate your reply, but I am a complete noob and all this is extremely overwhelming.
"PHHs AOSP with My SOM Module" - this alone gives me terrors
I know nothing about these things but I understand you, it's just everyday business for you coz you are a developer. I tried reading your guides and there are so many things I don't understand. I also was traumatized by rooting my S10, which I sold and got Xperia 5 instead. I read here people said I will permanently lose DRM keys after rooting. This is my biggest problem. With S10 I knew I could go back to stock and not worry. Here, if I go all the way and deGoogle my Xperia and it doesn't work the way it should I won't be able to go back and on top of that selling it will be harder and I will lose money since not everyone is willing to buy a phone which can't get Netflix and other DMR-dependent garbage.
Maybe I could sponsor you to help me flashing all the stuff. I just don't know if it's a crazy idea. Also, asking you to rewrite your guides for idiots like me is asking too much, given how busy you are.
If you have some advice I would greatly appreciate it.
BuyXRPnow! said:
I really appreciate your reply, but I am a complete noob and all this is extremely overwhelming.
"PHHs AOSP with My SOM Module" - this alone gives me terrors
I know nothing about these things but I understand you, it's just everyday business for you coz you are a developer. I tried reading your guides and there are so many things I don't understand. I also was traumatized by rooting my S10, which I sold and got Xperia 5 instead. I read here people said I will permanently lose DRM keys after rooting. This is my biggest problem. With S10 I knew I could go back to stock and not worry. Here, if I go all the way and deGoogle my Xperia and it doesn't work the way it should I won't be able to go back and on top of that selling it will be harder and I will lose money since not everyone is willing to buy a phone which can't get Netflix and other DMR-dependent garbage.
Maybe I could sponsor you to help me flashing all the stuff. I just don't know if it's a crazy idea. Also, asking you to rewrite your guides for idiots like me is asking too much, given how busy you are.
If you have some advice I would greatly appreciate it.
Click to expand...
Click to collapse
First of all. Good choice to get rid of a Samsung Device Like i did with My S9+! Sammy is pushing Android into a Appleish Edge that shouldn't exist...
Just like Huawei. But different Story...
Out of My View with Years of expierence with different Brands is SONY one of the Most supporting OEM in Views of Android Development besides the Fact they Always excluded some functionality of the included Smartphone Hardware. For example:
-Xperia Z1 lost the Complete Camera Function after unlocking (Got fixed with a Update later after Claims from Customers) and lost Display enhancements + Camera Noise reduction
-Xperia Z3 lost the Vibrant Display Colors after unlocking (Aka Bravia Engine) which ended Up in washed Out Colors and was still loosing Noise reduction
-Xperia XZ Premium still loosing enhancements after unlocking plus the loss of Camera Noise reduction
And now the Xperia 5...
Sony used for the First Time Samsung Sensors for the Cameras instead of own ones with High Resolution. So no Noise Reduction needed anymore. Finally OLED, so no washed Out colors without Display Enhancements.
I'm quite Happy with this One since you don't loose Something Essential. Besides that have i Always Managed since the Z3 to fix almost all Problems on Xperias with native Android functionalities that is used on other Devices. Eg. For the Display, Audio, Camera, Mics and so on.
And thats the final Point. While older Devices Had the Chance to Backup and restore the TA Partition or even to use a Recovery on locked Bootloader (I've also worked with this for some Time) which allowed to make Your Device Complete Stock again. We don't really have that Options anymore. So i would say an Unlock is a final Step. But to be honest. I sold many Devices claimed as unlocked and rooted and it hasn't Cut the Price at all. And even if You Don't. I don't think a normal Person will See a difference after unlocking and relocking
Is it worth it? For Me a clear Yes! I never looked back after unlocking any of My "Hundreds" of Devices i used. Magisk and GSIs alone are really worth the Unlock Out of My View actually. You can do so much with Android and it finally doesn't feels Bad anymore on Xperias. My SOM (Magisk based ROM (Systemless-On-Memory) will do a lot of awesome Things with Our Xperias (1 & 5). Another good Reason maybe...
It could be smart to make a Video which explains how to get My Work on Your Xperias. From unlocking to Flashing... Would really like to do that after some preparing for it. Possible that there are a lot of People who don't even know about Bootloader unlocking so it really could be cool. I already did some Videos in the Past; https://www.youtube.com/user/TheMarius517
Think i got a bit lazy since the Software alone takes so much time These days. But i will do My best to get People in Touch and to Show everything step by step.
Lot of Text but Hope i made Your decision to Unlock or not easier... Don't think about the Future of Your Device. Think about what You want from it right now...:good:
Btw. Not Sure but You could try ADB to remove Apps. But idk. If IT IS possible with Google Apps (Locked Bootloader Method)
All the Best,
Miu
Thank you! You are a hero. I will be waiting for your updated guides and possibly a video for noobs. Appreciate your time!
Peace.
Optimized the Thread Structure and Instructions. Optimized Thread Title. Updated Boot Image / Kernel to latest EU .149
Hi, which rom are you using for oneplus 9?
Unfortunately, the rom support for this model is very bad and many developers have stopped developing roms for op9. I'm looking for a rom that can get continuous updates. Best regards
JaguarOs for Android 11
NamelessOs for Android !2
These two roms are getting regular monthly updates and both are great.
try gsi
incesu said:
JaguarOs for Android 11
NamelessOs for Android !2
These two roms are getting regular monthly updates and both are great.
Click to expand...
Click to collapse
Nameless developers stopped roms.
Nameless Cdroid for op9 finish
amonstercattt said:
try gsi
Click to expand...
Click to collapse
How gsi işi full version
ooemir said:
Nameless developers stopped roms.
Nameless Cdroid for op9 finish
Click to expand...
Click to collapse
sadece op9 için mi yoksa bütün nameless romlar için mi bitirdiler.
Translation:
are they just finished for op9 or for all nameless roms?
derp
incesu said:
sadece op9 için mi yoksa bütün nameless romlar için mi bitirdiler.
Click to expand...
Click to collapse
For Op 9 and 9 pro finish
"Evolution X" I love the customization it has. Which is why I haven't updated to 12 yet lol. I will sometime. Love the rom though
Personally, DerpOS, which has both OP9/Pro support. Make sure to check out the pro XDA forums, as you'll be able to find many new ROMs outside of just on here.
I used to run EvoX, which is a very good A12 ROM, but when compared to others, isn't updated as much (I believe it's still on the Feb patch). I haven't heard much of when it's planned to be updated, as it's still migrating between maintainers at the moment.
A12.1 builds for the OP9 are limited unfortunately, as LineageOS 19, at the time of writing, is the only "official" one I know of, which you're able to do if you're happy flashing GAPPs.
However, many ROMs have A12.1 working in testing, though not officially released yet. Hopefully you'll see them pop up within the next few weeks, once they've passed their maintainer's QA checks, though I can't speak on their behalf (they'll be ready when they're ready). I'd personally be comfortable in flashing either one of these, as their developers seem very dedicated to supporting the device into the future:
StagOS, DerpOS, DotOS
StagOS in particular is also the only ROM I know of that are working on OOSCam. It seems their progress is coming along well, but you won't find it in any of their public builds as of yet.
As mentioned by a couple of people earlier, though I'd love to recommend Nameless as it's a fantastic ROM, it isn't being maintained at the moment. CrDroid for the Op9, though on paper is maintained, hasn't been updated for a while and the developer has been somewhat MIA. Love to see either come back though.
Personally, I'm still undecided. I saw that someone had problems with the Evox and with the derp very draining of battery. I would be tempted for StageOs ... but I'm still on oxygen 11.2.10.10 even if my device offered me the update to Android 12 C47. However if I do it I cannot flash rom!
morfances said:
Personally, I'm still undecided. I saw that someone had problems with the Evox and with the derp very draining of battery. I would be tempted for StageOs ... but I'm still on oxygen 11.2.10.10 even if my device offered me the update to Android 12 C47. However if I do it I cannot flash rom!
Click to expand...
Click to collapse
Personally haven't had any issues with derp, though I did notice evox had a few weird bugs with material you in the latest update. To each their own, I suppose! OOS11 is still quite good, although I really do like the theaming in a12.
I have flashed all the roms possible. Stag and Evo are pretty gnarly, but I keep it stock OS rooted on 10AA because for some Reason, PuBG is not as smooth on any roms as it is on Oxygen, plus its like the Read-Ahead is way better. Everything Renders in much faster. Like its almost already all there. The Roms arent like that.
I kinda wish someone would make a Gaming Specific rom.
Bone-Dry nothing to it.
FeroxFoxxo said:
Personally, DerpOS, which has both OP9/Pro support. Make sure to check out the pro XDA forums, as you'll be able to find many new ROMs outside of just on here.
I used to run EvoX, which is a very good A12 ROM, but when compared to others, isn't updated as much (I believe it's still on the Feb patch). I haven't heard much of when it's planned to be updated, as it's still migrating between maintainers at the moment.
A12.1 builds for the OP9 are limited unfortunately, as LineageOS 19, at the time of writing, is the only "official" one I know of, which you're able to do if you're happy flashing GAPPs.
However, many ROMs have A12.1 working in testing, though not officially released yet. Hopefully you'll see them pop up within the next few weeks, once they've passed their maintainer's QA checks, though I can't speak on their behalf (they'll be ready when they're ready). I'd personally be comfortable in flashing either one of these, as their developers seem very dedicated to supporting the device into the future:
StagOS, DerpOS, DotOS
StagOS in particular is also the only ROM I know of that are working on OOSCam. It seems their progress is coming along well, but you won't find it in any of their public builds as of yet.
As mentioned by a couple of people earlier, though I'd love to recommend Nameless as it's a fantastic ROM, it isn't being maintained at the moment. CrDroid for the Op9, though on paper is maintained, hasn't been updated for a while and the developer has been somewhat MIA. Love to see either come back though.
Click to expand...
Click to collapse
Thanks for this. I am so fed up with the bugs on OOS 12 and the app performance throttling. I have been holding off on unlocking the bootloader but I just can't deal with the issues anymore. Would be nice to see what this device can actually do... Sometimes it feels slower than my LG G8 with an 855...
I am waiting for official Pixel Experience so still OOS 12 for me
has anybody here tried lineageos on oneplus 9?
Anyone tested nameless rom?
morfances said:
Anyone tested nameless rom?
Click to expand...
Click to collapse
Hi! Nameless to my knowledge isn't being maintained anymore. It was a good ROM, but don't expect to get any updates like 12.1 13 etc.
Last build is 03/07
Nameless-AOSP - Browse /lemonade at SourceForge.net
Nameless AOSP is based on Android Open Source Project, inspired by Google Pixel. We offer a smooth and stable experience for your device with a…
sourceforge.net
morfances said:
Last build is 03/07
Nameless-AOSP - Browse /lemonade at SourceForge.net
Nameless AOSP is based on Android Open Source Project, inspired by Google Pixel. We offer a smooth and stable experience for your device with a…
sourceforge.net
Click to expand...
Click to collapse
I realize! I'm relatively sure it's not being maintained though since then, and support for it has been dropped.