• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[CHAT] HD10 (2017) - custom ROM brainstorming:

Search This thread
Has anyone made a (somewhat) working nougat or higher rom for the hd 10?

There is an HD 10 ROM for Android 9.0 but there was never an official thread made for it and I'm not sure exactly which thread to discussion of it took place in and that's where the link to it would be. there is a 5.1 right now and I am currently working on a marshmallow ROM which hopefully if everything has finally been corrected because I'm dumb (not really just dumb mistakes I stupidly overlooked) then in two days or less will have a functioning marshmallow ROM.

Sent from my Amazon KFSUWI using XDA Labs
 

Justsnoopy30

Member
Mar 18, 2018
41
4
There is an HD 10 ROM for Android 9.0 but there was never an official thread made for it and I'm not sure exactly which thread to discussion of it took place in and that's where the link to it would be. there is a 5.1 right now and I am currently working on a marshmallow ROM which hopefully if everything has finally been corrected because I'm dumb (not really just dumb mistakes I stupidly overlooked) then in two days or less will have a functioning marshmallow ROM.
So does anyone have a link to that android pie rom?
 

moosefist

Senior Member
Sep 13, 2008
362
22
Has anyone made a (somewhat) working nougat or higher rom for the hd 10?

I think @Legitsu made it if I recall correctly. He would be the best one to provide the link.

Sent from my Amazon KFSUWI using XDA Labs[/QUOTE @k4y0z made it..

Enviado desde mi Mi A2 mediante Tapatalk

I think @Legitsu made it if I recall correctly. He would be the best one to provide the link.

Sent from my Amazon KFSUWI using XDA Labs

@k4y0z did make it. It was discussed in his bootloader unlock thread. It was described as very buggy / alpha https://forum.xda-developers.com/showpost.php?p=79892280&postcount=430

Here are the files: https://androidfilehost.com/?w=files&flid=296326
 

Justsnoopy30

Member
Mar 18, 2018
41
4
I think @Legitsu made it if I recall correctly. He would be the best one to provide the link.

I have searched both's recent posts and threads and not found anything about it.
Can anyone link me?

---------- Post added at 10:16 PM ---------- Previous post was at 10:14 PM ----------

@k4y0z did make it. It was discussed in his bootloader unlock thread. It was described as very buggy / alpha https://forum.xda-developers.com/showpost.php?p=79892280&postcount=430

Here are the files: https://androidfilehost.com/?w=files&flid=296326

Oh oops I didn't see this until I posted.
Thanks.
 

Justsnoopy30

Member
Mar 18, 2018
41
4
One question, why is there so "low" system partition space according to gapps? Using twrp -> wipe -> advanced wipe -> system -> Repair/resize -> Available memory = 357. I tried flashing gapps stock, full, mini, micro, nano, and finally pico worked. Micro zip size is smaller than the free system partition space. It is insanely small. Is there any way to resize the system partition to be bigger?
 
One question, why is there so "low" system partition space according to gapps? Using twrp -> wipe -> advanced wipe -> system -> Repair/resize -> Available memory = 357. I tried flashing gapps stock, full, mini, micro, nano, and finally pico worked. Micro zip size is smaller than the free system partition space. It is insanely small. Is there any way to resize the system partition to be bigger?

Have you debloated any apps? because nearly all of Amazon's apps running in the background all of the time in some capacity or another. I don't even know if the right memory is displayed properly on fire OS. Though I can safely say I have never had a problem with memory or storage with any of the things I have done or been doing on stock fire OS. The biggest memory hogs in terms of the Google applications will be the Google app and Google Play services.

Sent from my Amazon KFSUWI using XDA Labs
 

DB126

Senior Member
Oct 15, 2013
15,269
10,044
One question, why is there so "low" system partition space according to gapps? Using twrp -> wipe -> advanced wipe -> system -> Repair/resize -> Available memory = 357. I tried flashing gapps stock, full, mini, micro, nano, and finally pico worked. Micro zip size is smaller than the free system partition space. It is insanely small. Is there any way to resize the system partition to be bigger?
Nope, unless you want to go deep with a high probably of borking your device. Assuming you have write access to the system partition find a tool (app) that accurately displays size and content. Eliminate a few Amazon hogs and you'll have more than sufficient space for most GApps 'core' builds (albeit perhaps not stock). Stuff that doesn't fit can be added separately via Play Store; those components will get installed in the data partition.
 
  • Like
Reactions: Kctucka

Justsnoopy30

Member
Mar 18, 2018
41
4
Have you debloated any apps? because nearly all of Amazon's apps running in the background all of the time in some capacity or another. I don't even know if the right memory is displayed properly on fire OS. Though I can safely say I have never had a problem with memory or storage with any of the things I have done or been doing on stock fire OS. The biggest memory hogs in terms of the Google applications will be the Google app and Google Play services.


Nope, unless you want to go deep with a high probably of borking your device. Assuming you have write access to the system partition find a tool (app) that accurately displays size and content. Eliminate a few Amazon hogs and you'll have more than sufficient space for most GApps 'core' builds (albeit perhaps not stock). Stuff that doesn't fit can be added separately via Play Store; those components will get installed in the data partition.
I mean that the android pie rom is taking up so much space in the system partition, not amazon stock rom.
 
Last edited:

Justsnoopy30

Member
Mar 18, 2018
41
4
The last date the pie rom was updated was 7/6. Did @k4y0z stop working on it?

---------- Post added at 02:16 PM ---------- Previous post was at 02:13 PM ----------

The LOS Pie rom still contains lots of unneeded binary-blobs that should be removed.
But then again it's still very alpha and I haven't had much time to work on it further.
Ok. The major issue I noticed was the graphics being glitchy and slow.
The last date the pie rom was updated was 7/6. Did @k4y0z stop working on it?
Oh, I sent that before I saw the previous message.
 
CM13 will not build. There is a maven repository module both the original CM and Lineage CM repositories that's required to build certain apps. Neither of the two will acknowledge the module instructions despite it being part of the source code. I've tried all the 'fixes' I can find, and none of them seem to make a difference. So I am going to go back to straight AOSP and see what happens over there.

Sent from my Amazon KFSUWI using XDA Labs
 
  • Like
Reactions: avalst

Top Liked Posts

  • There are no posts matching your filters.
  • 16
    Just dropping this here...
    14
    what is the ouput of the mount command??
    Would mount -o remount, rw work to see if it is possible to write through at all?

    Just a thought doesn't happen to be permission issue within one of the XML files? because that's what it sounds like it sounds like the permissions wasn't added to the platform XML in etc/permissions/platform.xml.

    Neither of that was the issue, I think it's just that using FUSE for internal storage isn't really supported on Pie.
    So I ditched the idea altogether and went ahead and merged SDCARDFS into the kernel.
    We now have full SDCARDFS-support which also solves the mounting and permission issues => Downloading files works now.
    I have also changed the brand to google and indeed the play-certification issue has disappeared.

    I do not recommend to flash gapps beside the rom.
    This isn't something lineage related. You simply can't use Google services if ur device is not certified.
    If u want to use them anyway then check out microG.

    With this build I flashed open_gapps-arm64-9.0-pico-20190706.zip which worked fine.
    There is probably lots of proprietary stuff that can be removed from the build, so we can flash larger gapps in the future.

    Check out the new build:
    lineage-16.0-20190706-UNOFFICIAL-suez.zip
    10
    Guys, I am following this thread for quite a while and I have the feeling it is getting somewhat emotional now.
    From my point of view, "learning" is something totally individual so please do it the way it suits you best :)
    I am impressed of all the time and passion DragonFire puts into this project, so please keep going :good:

    By the way, I am willing to contribute somehow. I would like to reproduce your build, but some things are not clear to me or are scattered around this thread. It would be nice to have a compilation of what your have right now:
    - Which kernel source(s) did you use and did you merge them to upstream?
    - Which module(s sources) did you enable/use for build?
    - Which environment options or arguments did you use for build?
    - Any further steps to bring the kernel into the ROM.
    I have some good hardware around and some really nice collegues which might support me to reproduce your build.
    If this question is out of scope or just too much to answer, please ignore this post.

    Here are the sources I have. If anyone can expand on them...
    TWRP device tree for Amazon Fire HD10 (2017) https://github.com/chaosmaster/android_device_amazon_suez
    Kernel source https://github.com/chaosmaster/android_kernel_amazon_suez and https://www.amazon.com/gp/help/customer/display.html?nodeId=202194760
    MT8173 Source https://github.com/Goayandi/mediatek_mt8176_development
    Device tree https://github.com/488315/android_device_amazon_suez/tree/cm-14.1
    Proprietary https://github.com/488315/android_vendor_amazon_suez
    Kernel patches https://github.com/488315/Linux-Patches
    Possible portable ROM, stock Hi9 tablet (nearly identical to our build) android 7.0 https://drive.google.com/file/d/1mneBbR8eYceXrqxgVbBa6bBLZm7J7NTp/view?usp=sharing
    MT8173 Kit to make an LK, bootloader, preloader and boot.img https://drive.google.com/file/d/1i_xcl1RQwHJVLBvX3uDVFlcddcaLp8mf/view?usp=sharing

    I'll upload to github what I have been working on in terms of a ROM. I am reformatting my make files (they were bad) and it will take a hot minute.
    8
    Just giving a general update. I am almost done reformatting the makefile(s). There's a lot we have to import from the vendor area. and again because a profile to this extent has not existed for this device I'm stuck with making it all from scratch.

    There were some other things that I wanted to see if I can add in terms of mediatek proprietary applications that will allow for certain features to exist on a possible lollipop ROM that would not otherwise exist on a lollipop ROM. For some reason, in all the sources we have for this particular mediatek device, they do not seem to contain their proprietary applications, aside from ones that would normally be in the LK (fastboot et Al). That will take a minimum amount of time to add the device make file. The longest process is just simply adding all the lines of all the enormous amount of stuff we have to import from the rest of vendor. It weren't for that this would have been done long ago.

    Now that I have the next few days off I can focus on finishing that up and and making sure everything is in place to try another build.

    Sent from my Amazon KFSUWI using XDA Labs
    8
    I have a good feeling about this build. It's going to actually finish this time....the rom that is. I have no idea how long it has left to build but it's not long.

    Sent from my Amazon KFSUWI using XDA Labs