Related
Can anybody build the CopperheadOS for our Pixel? Maybe with a small Donation?
https://copperhead.co/android/docs/building
If it is not allowed to ask such things here, please send me a PM.
Greetings
what does this include? and your in the wrong thread
robotnikz said:
Can anybody build the CopperheadOS for our Pixel? Maybe with a small Donation?
https://copperhead.co/android/docs/building
If it is not allowed to ask such things here, please send me a PM.
Greetings
Click to expand...
Click to collapse
But they have a download link for Pixel on their website: https://copperhead.co/android/downloads
Is it because they say: "available via purchase soon"?
uodii said:
But they have a download link for Pixel on their website:https://copperhead.co/android/downloads
Is it because they say: "available via purchase soon"?
Click to expand...
Click to collapse
You need a login to download it. I assume you only get a login after purchasing a license from them.
uodii said:
But they have a download link for Pixel on their website: https://copperhead.co/android/downloads
Is it because they say: "available via purchase soon"?
Click to expand...
Click to collapse
Yes you have to purchase it or build it yourself. But I am not able to build it myself
robotnikz said:
Yes you have to purchase it or build it yourself. But I am not able to build it myself
Click to expand...
Click to collapse
If they are selling security and the OS I dou t that they allow anyone to build their software. If you can build from their sources I dou t it includes any of their additional software and is pro ably just bare android
devilsadidas said:
If they are selling security and the OS I dou t that they allow anyone to build their software. If you can build from their sources I dou t it includes any of their additional software and is pro ably just bare android
Click to expand...
Click to collapse
No. It is allowed to build from their sources.
robotnikz said:
No. It is allowed to build from their sources.
Click to expand...
Click to collapse
I tried to build it two times. The first built with no errors but the files weren't in zip format and I couldn't figure how to flash them. My second failed because I still need to get by build environment set up again. I just re-installed Linux a few days. I just switched to Linux Mint permanently a few weeks ago from Windows so I've been dealing with the transition. I have the source downloaded so I'll be tinkering with that when I have time. Hopefully something good will happen in a few days on my end. Till then this thread needs to be moved to the Q&A section. I'm glad you threw the question out there and hopefully others will join the party.
Misterxtc said:
I tried to build it two times. The first built with no errors but the files weren't in zip format and I couldn't figure how to flash them. My second failed because I still need to get by build environment set up again. I just re-installed Linux a few days. I just switched to Linux Mint permanently a few weeks ago from Windows so I've been dealing with the transition. I have the source downloaded so I'll be tinkering with that when I have time. Hopefully something good will happen in a few days on my end. Till then this thread needs to be moved to the Q&A section. I'm glad you threw the question out there and hopefully others will join the party.
Click to expand...
Click to collapse
Thank you very much for your effort. I am also on Mint but I am not familiar with building ROMs. Maybe I'll have a look at it someday
robotnikz said:
Thank you very much for your effort. I am also on Mint but I am not familiar with building ROMs. Maybe I'll have a look at it someday
Click to expand...
Click to collapse
My guess is that they don't mind private builds. However, I would doubt they would be okay with a build being posted in a forum like this. Also, from reading their website it appears when you pay, you're getting the support of the devs directly as well as their updates pushed directly to your phone without having to do new builds like you will without a license. I could be slightly off but I think that was the gist of it.
robotnikz said:
Thank you very much for your effort. I am also on Mint but I am not familiar with building ROMs. Maybe I'll have a look at it someday
Click to expand...
Click to collapse
Same here. I used to build ROMs for Samsung and AOSP is pretty foreign to me but I am learning. It's quite a bit for me between real life, a new OS and AOSP. It's cool though, my 40+ year old brain was getting a bit stale.... Anyway I tried again today for a few hours and made some progress. I successfully compiled a generic build but when I try sailfish I get a user error and it tells me to change user. Seeing that the official build isn't available for purchase I think they blocked the build process some way. I can compile Pure Nexus no problem so it's not my set up, probably their directions. But on the other hand it could be on my end. Either way I'll still be looking into it.
Is there a way to compile this os with gapps already built in for personal use. After building and flashing it on my phone I found the lack of certain Google services very annoying. Flashing gapps after installing the os didn't work. Also if you're on T-Mobile no data connection unless you change settings in apn, I wonder if flashing stock vendor img would help with that.
robotnikz said:
Can anybody build the CopperheadOS for our Pixel? Maybe with a small Donation?
https://copperhead.co/android/docs/building
If it is not allowed to ask such things here, please send me a PM.
Greetings
Click to expand...
Click to collapse
did you did it, can you instruct this ?
robotnikz said:
Can anybody build the CopperheadOS for our Pixel? Maybe with a small Donation?
https://copperhead.co/android/docs/building
If it is not allowed to ask such things here, please send me a PM.
Greetings
Click to expand...
Click to collapse
Hello,
I have successfully found a way to build sailfish cos , if you are interested .
ksuhiyp said:
Hello,
I have successfully found a way to build sailfish cos , if you are interested .
Click to expand...
Click to collapse
Would be great. I'm very interested.
ksuhiyp said:
Hello,
I have successfully found a way to build sailfish cos , if you are interested .
Click to expand...
Click to collapse
I'm also very interested! Tell how you did it
Pixel 2 CopperheadOS
Anyone have tryied to compile from source copperhead for Pixel2 phone?
I am also very interested! Could you please share? May be for a donation....
ksuhiyp said:
Hello,
I have successfully found a way to build sailfish cos , if you are interested .
Click to expand...
Click to collapse
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
Hey,
over the last few weeks I've used my Christmas vacation to start working on the Z18 again. However since work is coming up again soon, I won't have that much time (and nerves) for working on this properly until the end of summer probably.
That's why I want to share my codebase with you, so maybe someone can pick up where I left off (and really, it's nothing big I did. I merely set up the device tree and made it compile more or less. It doesn't boot because of avb and I'm not aware of any way around that)
The device tree can be found here. It's still using a prebuilt kernel but I'll work on fixing the kernel source to a compileable state next.
If anyone wants to get involved, help or pick this up, feel free to do so. The community and I are always happy for help.
Explanations of what the next steps would be can be found below.
Again, do not install this unless you want to softbrick! It's not useable at all and will currently fail at boot verification!!
So what's next?
Fixing avb2.0: This isn't an easy task. How I understand, it either needs the official keys or I failed at signing the build with test keys from LineageOS. Either way this is the first step and top priority so the device boots again at least
EDIT: It seems that https://github.com/rockchip-linux/tools/tree/master/linux/Linux_SecurityAVB might be of some use (given that youyim123, the guy who also did the TWRP for Z18 starred this project). However I don't speak Chinese and putting my device in the hands of Google Translate is risky.. so anyone willing to translate, I'm open for DMs or anything
EDIT2: avb is working, so we can move on to breaking our system now (yay)
Hi, Its a long time i am waiting for a suitable rom to be installed in my Nubia Z18. Can you tell me when this rom can get out? Your effort is highly appreciated.
Zahidul Hasan said:
Hi, Its a long time i am waiting for a suitable rom to be installed in my Nubia Z18. Can you tell me when this rom can get out? Your effort is highly appreciated.
Click to expand...
Click to collapse
Sorry but I can't give you any ETA on this. I'm working on it in my little free time and I'm not even sure what I'm really doing with this. The source is all on the GitHub repo I linked in the OP though, so if you're hesitant and want to get a working ROM, just get involved. It's really not that hard, all it requires is time, patience and lots of googling for weird error messages and further features you want to implement.
You can mostly follow the guide here https://wiki.lineageos.org/devices/bacon/build just replace the bacon command with nx606j-eng and you're good to go and build this yourself. Maybe you can figure out avb since I can't do it by myself, so any help is appreciated.
Dear Sir, Thank you so much for your reply. Last day i tried to push a TWRP from here TWRP installed, but failed to install any gaapps. although process said success.
curtisy said:
Sorry but I can't give you any ETA on this. I'm working on it in my little free time and I'm not even sure what I'm really doing with this. The source is all on the GitHub repo I linked in the OP though, so if you're hesitant and want to get a working ROM, just get involved. It's really not that hard, all it requires is time, patience and lots of googling for weird error messages and further features you want to implement.
You can mostly follow the guide here https://wiki.lineageos.org/devices/bacon/build just replace the bacon command with nx606j-eng and you're good to go and build this yourself. Maybe you can figure out avb since I can't do it by myself, so any help is appreciated.
Click to expand...
Click to collapse
Zahidul Hasan said:
Dear Sir, Thank you so much for your reply. Last day i tried to push a TWRP from here TWRP installed, but failed to install any gaapps. although process said success.
Click to expand...
Click to collapse
Yeah, that thread, if most of the development threads on the Z18 so far, was made by me. I also mentioned in post #3 that flashing Gapps doesn't seem to be working and I was trying to ask the GApps team for help. I never got an answer though, so I stopped looking into this and instead focused my effort on providing a working Lineage build for everyone. The result of that is this thread here
Hey curtisy, are u building lineage OS forZ18 right now?
im chinese and can help to test this rom if need tester, I've a Z18 on hand rite now and still finding a solution to solve the "GAPP" problem
try to flash GAPP package but no luck!
hope the Lineage can release soon for testing~tks!
sky104hk said:
Hey curtisy, are u building lineage OS forZ18 right now?
im chinese and can help to test this rom if need tester, I've a Z18 on hand rite now and still finding a solution to solve the "GAPP" problem
try to flash GAPP package but no luck!
hope the Lineage can release soon for testing~tks!
Click to expand...
Click to collapse
I'm not building it right now. As I said, the project is pretty much on standby for anyone to take it where I left it but I'm still working on it sometimes and try to get it to work. The big issue is that the Z18 uses avb2 which I'm not sure how to bypass and which is also why the Lineage I built will not boot correctly. I don't want to seem rude saying this over and over again, but rather than testing, it would help if I had some more people to get involved. Just download the source and follow the instructions I mentioned in post#4. Progress will be much faster if there was a team behind this and not only one guy who doesn't know what he's doing most of the time. Also getting support in the Lineage IRC is tedious because I can't be online 24/7, so having some more people nag about avb2 there would also be of huge help.
And when there finally is something to test, not only will you be satisfied by your own achievement, but you can also be the initial tester since you built the ROM yourself.
PS: The Gapps issue is probably because of avb2 as well, however I'm not too sure about that
curtisy said:
I'm not building it right now. As I said, the project is pretty much on standby for anyone to take it where I left it but I'm still working on it sometimes and try to get it to work. The big issue is that the Z18 uses avb2 which I'm not sure how to bypass and which is also why the Lineage I built will not boot correctly. I don't want to seem rude saying this over and over again, but rather than testing, it would help if I had some more people to get involved. Just download the source and follow the instructions I mentioned in post#4. Progress will be much faster if there was a team behind this and not only one guy who doesn't know what he's doing most of the time. Also getting support in the Lineage IRC is tedious because I can't be online 24/7, so having some more people nag about avb2 there would also be of huge help.
And when there finally is something to test, not only will you be satisfied by your own achievement, but you can also be the initial tester since you built the ROM yourself.
PS: The Gapps issue is probably because of avb2 as well, however I'm not too sure about that
Click to expand...
Click to collapse
OK I understand your situation, probably not as many ppl own this phone at all...there are many ppl doing developement in Oneplus 6 which I actually own that phone, the Z18 is actually my fd, therefore I cannot keep the phone long...just wonder if there have more ppl involve to this...the "avb2" I'll check to see if anyone on the net doing this, haha! the only solution is more developer involve to this phone!
sky104hk said:
OK I understand your situation, probably not as many ppl own this phone at all...there are many ppl doing developement in Oneplus 6 which I actually own that phone, the Z18 is actually my fd, therefore I cannot keep the phone long...just wonder if there have more ppl involve to this...the "avb2" I'll check to see if anyone on the net doing this, haha! the only solution is more developer involve to this phone!
Click to expand...
Click to collapse
As a quick update for everyone here as well because the discussion has somewhat shifted to the TWRP thread I worked around avb now. I also have a system.img but it's not working as of yet. If you want to get stuck in a boot loop, feel free to ask here and I'll attach the files in the OP for you to try and modify. Without building from source, there's probably not that much you can do though.
Hint: try booting phh-treble GSI first.
j1505243 said:
Hint: try booting phh-treble GSI first.
Click to expand...
Click to collapse
Thanks! Going to try that later but out of curiosity, isn't the reason this phone doesn't have google services out of the box that it wasn't certified by google? If so it's not treble compatible either right? Or am I missing something?
curtisy said:
Thanks! Going to try that later but out of curiosity, isn't the reason this phone doesn't have google services out of the box that it wasn't certified by google? If so it's not treble compatible either right? Or am I missing something?
Click to expand...
Click to collapse
An uncertified device can be freely Treble compatible, so it's really worth to try. Remember to join the Telegram chat of phh-treble if you happen to need some quicker response.
j1505243 said:
An uncertified device can be freely Treble compatible, so it's really worth to try. Remember to join the Telegram chat of phh-treble if you happen to need some quicker response.
Click to expand...
Click to collapse
Awesome. Thank you for the heads up! Might be worth to invest some time in this again then.
j1505243 said:
Hint: try booting phh-treble GSI first.
Click to expand...
Click to collapse
Alright, I tried and I don't think it's working. I get stuck in a bootloop again which repeats every few seconds.
Since I got Lineage compiled, wouldn't it be a better idea to just get that working and be done with it?
Any help is much appreciated!
Hello curtisy, I wish you good luck with your work on the Nubia Z18. I'd love to help you, but unfortunately I have no skills at android developing. Anyway... in case you will get LineageOS to run, I'd be very happy to post an instruction for the installation on my website chinahandys.net. Liebe Grüße, Joscha
curtisy said:
Alright, I tried and I don't think it's working. I get stuck in a bootloop again which repeats every few seconds.
Since I got Lineage compiled, wouldn't it be a better idea to just get that working and be done with it?
Any help is much appreciated!
Click to expand...
Click to collapse
Booting non-GSI will only be tougher :/ Capture deep level logs and inspect that. If you need help, join a phh-treble chat somewhere.
j1505243 said:
Booting non-GSI will only be tougher :/ Capture deep level logs and inspect that. If you need help, join a phh-treble chat somewhere.
Click to expand...
Click to collapse
Yeah that's actually the same point I stopped at with Lineage. Got it to boot to the Nubia logo, captured logs and I can see some weird errors. But getting replies on IRC is a pain, especially if I can only be online for 2hrs a day. That's why I had hoped someone would pick this up but to no avail. Guess I'll have to look into it again and experiment.
Thanks for your help so far! If there's any more tips you want to share, I'm always open for them
furiousjay said:
Hello curtisy, I wish you good luck with your work on the Nubia Z18. I'd love to help you, but unfortunately I have no skills at android developing. Anyway... in case you will get LineageOS to run, I'd be very happy to post an instruction for the installation on my website chinahandys.net. Liebe Grüße, Joscha
Click to expand...
Click to collapse
Hey, sure thing I actually know the site well and got the idea of getting a Z18 from your site. In case you know anyone that might be able to help with logs or anything, I'm always open for suggestions and help.
As a general rule of thumb, so far the process isn't exactly easy because it requires proprietary software. The issue is with boot verification, so to get around that, I rooted my phone with some Chinese Windows application (still trying to reverse that to get the actual keys..) then I could start flashing. The process is tedious though as every failure means reflashing the original rom as well as running the root tool again. I'll try to make it simpler and cross platform once the rom actually works. But it's still a long way to that point.
curtisy said:
Hey, sure thing I actually know the site well and got the idea of getting a Z18 from your site. In case you know anyone that might be able to help with logs or anything, I'm always open for suggestions and help.
As a general rule of thumb, so far the process isn't exactly easy because it requires proprietary software. The issue is with boot verification, so to get around that, I rooted my phone with some Chinese Windows application (still trying to reverse that to get the actual keys..) then I could start flashing. The process is tedious though as every failure means reflashing the original rom as well as running the root tool again. I'll try to make it simpler and cross platform once the rom actually works. But it's still a long way to that point.
Click to expand...
Click to collapse
Unfortunately I personally don't know somebody who has the skills to support you. I have included a call for support for your project in our review.
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
Hi guys, So how I can install this ?
https://www.xda-developers.com/android-q-gsi-project-treble/amp/?__twitter_impression=true
I don't know if unmodified gsi will work for us, as treble requirements have been changed since our phone shipped. May be possible to modify but that is for smarter people than me. Google is apparently doing beta program again probably starting with beta 3 so maybe better to wait for that
M.
mattman83 said:
I don't know if unmodified gsi will work for us, as treble requirements have been changed since our phone shipped. May be possible to modify but that is for smarter people than me. Google is apparently doing beta program again probably starting with beta 3 so maybe better to wait for that
M.
Click to expand...
Click to collapse
Ok we'll see if it's possible , if I know something I'll Post it here .
Thanks
It boots but lots of bugs and not usable at the moment for our phone. Google's version doesn't work you have to use efrans version. If you want to keep up with it here's the telegram link.
https://t.me/androidqgsi
tember1214 said:
It boots but lots of bugs and not usable at the moment for our phone. Google's version doesn't work you have to use efrans version. If you want to keep up with it here's the telegram link.
https://t.me/androidqgsi
Click to expand...
Click to collapse
Thanks anyway, can you say something when it will be usable :fingers-crossed:
Sure