Database Users

[ATTN ROM COOKS/NOOBs][READ BEFORE FLASHING] Please prompt users to create backups!

Dear newbies, please back your device up before updating, trying custom ROMs, Kernels and other modifications. Most common and easy backup methods can be found here. Please note that Acer has released firmwares that broke the update cycle. First thing to do when getting a device is a backup or you might get stuck on an old version!
Dear ROM cooks, please prompt users to create backups. Although for some it may seem common sense, other may suppose that restoring their tablet is an easy task - until Acer releases an OTA update to the current 3.1 we can't say for sure our stock 3.1 will match all the required checksums.
Please do not modify Device Information, Model number, Android version, SN and SNID if possible. I understand you take pride in your work, and you should but by over-branding the FW you can be making it very hard for developers to properly identify the device and address bugs. Some will even ignore reports from modded devices.
Thank you for your cooperation.

I agree flashing custom roms can brick a phone or tablet. Users should be aware of tue possible consequences, but they rooted the phone which makes all this possible. That by itself largely takes them outside of support.
I agree blanking sn and snid, as well as change device types etc should be pointed out where possible, but being realistic most devs will not devote the time for it.
I personally do not develop on android, but have dealt with custom roms on multiple android and other os's. I generally make I have a way to return to stable state. The net result is i have never permanately bricked a phone. Close a few times.
I think a good mandatory read post about the dangers of rooting, installing root apps or flashing romss and kernels, would a good idea before people can accesss the sub-furoms devote to that stuff.
But realize that most owners of any android, iphone, windows mobile, etc will never root(jailbreak). Only the curious. Rememberthe saying about curiousity and the cat.
DEVs - Keep up the good work.
Users - Understand the risks. If you don't understand what you are doing. THINK THREE TIMES
Hopefully, if something goes wrong someone here can help.

FLEX Version : Blank
Product SKU : 3G
SN : Blank
SNID : Blank
My Flex Version : 22_COM_GEN1 (was 04_COM_GEN1 but on my second tablet now it's 22_COM_GEN1)
My SKU should be WIFI
My SNID Should be XEH6LAN00511515CF11500
My SN Should be 11508932915
MY UID :0x03807001422172d7
How put those information back to the tablet????
rooted for sure, root explorer indeed... but where, how, etc... thanks if someone know
How to get back those lost information:
Serial Number ID (SNID)
go to https://registration.acer.com/myaccount/page11.do?link=kln2s.redirect&changedAlts=
and login
then get back your SNID from your devices list your register at ACER.... you did it didn't you ?
or that is not a SURE thing, but on my bills I have the Snid wrote down.
Serial Number (SN)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flex Version
(that is related to the firmware, it's the last group starting with a number)
22_COM_GEN1 for the 4.010.22_COM_GEN1
SKU
WIFI

Tell that to the people trying to fix their tablet after flashing your ROM.
Just asking nicely to post a note about backing up, but no, you just have to be a jerk.

Thanks for sharing, hopefully people read it before flashing.
This is just an effort to caution the noobs and request the ROM chefs to caution the noobs, we are not trying to blame it on the Chefs, and if developers feel that noobs won't read this - well we can't force anyone to read this - but we can try and help them to not brick their device - which will lead to another 100 threads with the title " I brick my device - whats to dos now " in the dev section, if by one thread we can save 100 new threads - maybe worth a shot.

[Q] kernel for ICS

Hey,
I've read various topics on the forum, but they seem to confuse me as they say different things:
when ICS was released, some people said we needed a newer kernel for our nook in order to run ICS. but now, we have a pre-alpha build which runs on the old kernel. There are various other devices which have ICS builds on a 2.6.32.x kernel, so why did some people say that we needed a newer kernel?
Are Dal and fattire building ics ontop of a gingerbread kernel?
And which kernel is the "default" for ics? a 3.0 kernel?
i'd appreciate some answers to enlighten me

Take a look here, from the dev thread, kernel is 2.6.32.9.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Homer

Homer_S_xda said:
Take a look here, from the dev thread, kernel is 2.6.32.9.
Homer
Click to expand...
Click to collapse
Yeah, i know we are on that kernel, but my question is: how is this possible? Are they porting ICS to a froyo kernel?
The HD2 uses a froyo kernel too, for it's ICS builds.
But why were people saying when the ics source code was just released that we need a newer kernel before ICS could be ported to our nook?

I think you might be confused between NT and NC.
AFAIK, NT does need newer kernel (as set of drivers since it has new hardware) while NC doesn't require to. I might be wrong though.

It's my understanding that the NC (not sure about the NT) doesn't actually need the new kernel to run, but it would make things a hell of a lot easier. Mainly, the problem seems to be getting outdated hardware drivers working with the newer parts of ICS--thus the lack of sound and video, among others--and that 2.6.35 has code and/or links to drivers that would help. But until B&N updates to that kernel (unlikely for now)m anyone working on CM9 has to deal with the old code and thus has an uphill battle.
IIRC, at first the CM9 team said it might never come to the NC, so I feel like we're kinda lucky. And if you read the first post of the DEV thread, you'll see that they're still iffy (and that's being generous) on a final, working, daily-driver version ever being released.

A lot of misleading info here , I'll try to make it simple and understandable
First , NT has a locked bootloader - it doesn't have anything to do with ICS or kernel ver.
ICS doesn't NEED 3.0 kernel to run ( proven on many devices ) , BUT there are some compatibility issues that needs fixing/back-porting/revere-engineering
and there are some things that can't be exactly ported ( or it's pretty hard and not worthy to reverse engineer ) , such as closed-source drivers
The main issues most devices encounter are GPU & Camera
Since we don't have a cam , the GPU drivers are the main thing to worry about
As dalingrin explained some time ago , there are closed-source libs that we need updated from the manufacturer to support ICS - It seems some can be found compatible with newer kernel versions ( 2.6.35 ) , but again it doesn't promise full support till an official ICS version for a similar spec device comes out
As I see it , a 2.6.35/37/38 or even better 3.0 ( as some devices starting to concentrate on now to get full gpu support & camera working instead of back-porting closed source drivers ) eventually will be necessary , because all we do now is relying on legacy support / hacks
I'm hoping for a community port of 3.0 kernel once ICS port will reach its full potential using 2.6.32 kernel ( now that fat-tire has caused many people to learn how to build , maybe we will see more progress soon )

AOSP port to Note-4 trltexx,trltedt

Greeting Developers ,
I am new to this ROM building/porting process.
I want to install Vanilla Android on my note-4, so after questioning Google number of times, I came across official Android development guide on official Android website: https://source.android.com/source/downloading.html
I have downloaded the Android source locally and was following various Guides and tutorials from XDA-University & forums only for the development process. http://xda-university.com/as-a-devel...ng-source-code
I discovered that for downloading/configuring the build for a specific device(trltexx), we need to create a localmanifest file that contains device tree, vendor and kernel configuration links for repo syncing.
Now, I want your expertise to guide me forward from this point. Questions being:
1. Can I use CM or other projects (eg. AICP etc.) device configurations for this AOSP project.
2. Can I use these configurations for cross-version android build, say if I want to compile version 6.x, can 5.x configs can be used. (Manufacturer will take several months to release version update)
or Create new configurations using some guide/tutorial/book or something.
In XDA, I know I'm at the write place posting my questions and asking for expertised help.
Thanks!!

Head into the aosp Dev thread from raymanfx he is working on 6.x and has 5.1 aosp mostly fully working.
For exynos there's no other vanilla rom as far that I know apart from his. For non exynos there is an official cyanogen rom I believe

contramundi said:
Head into the aosp Dev thread from raymanfx he is working on 6.x and has 5.1 aosp mostly fully working.
For exynos there's no other vanilla rom as far that I know apart from his. For non exynos there is an official cyanogen rom I believe
Click to expand...
Click to collapse
Thanks for your reply @contramundi, I got N-910G which is a snapdragon version. I just want to know if I can use AOSP sources from google and device configurations from CM, AOSP rom can be built or I need to use specific device configurations for AOSP.

Why?
There's no need to start a whole thread for this as there are numerous threads to ask such a simple question. You didn't say which version of AOSP you were building, but regardless-- yes, you can try to start with CM device trees, but prepared to change quite a bit as there are quite a few dependencies on CM enhancements there.
If you want a truly "vanilla" experience, I"d use the Code Aurora sources, not AOSP's, as CA has all the latest Qualcomm support/bug fixes for MSM and APQ devices, which only may hit the AOSP tree when they do a new release. It is the repository where Samsung starts with their version of Android, and it's where CM also gets its qcom support/repositories.
Gekke, slahyer, and I have done the work to make the Note 4 build/work-- both for lollipop and now starting for 6.0 Marshmallow. And speaking of 6.0, before you even think of building that w/AOSP, you'd also need tons of patches for the Samsung kernel which I also have also already done.
Rather than just applying our work to vanilla AOSP though, you're welcome to join the community effort on CM 13, which has already been successfully built for tmo, eur/xx, spr, and edge so far) on the other thread. You'll need to read about the last two months of posts to catch up. I also posted a link to instructions on building CM-13 in my .sig below.
If you are insisting on straight AOSP by yourself, I would recommend you look at the shamu (Nexus 6) model. It is the same soc as the Note 4, albeit with different peripherals (screen, fingerprint reader, etc.). But it might be a place to start. My build instructions would need some slight tweaking for vanilla AOSP, but I'm sure you could figure it out.
ft

Compiling 8.1 oreo for note 4
Hi,I have been trying to compile aosp for note 4 snapdragon variant.I have downloaded the repo and the required files.I started the compilation and after 25% of the compilation is over,it shows some error and stops the process.Can anyone please help me.I have added the screenshots for reference.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

The Current State of ROM & Mod Development

THE FUTURE IS LOOKING GREAT!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now that @sToRm// has released the long anticipated DRM fix for this magnificant phone. Should we start to see an increase in ROM development? Hopefully.
Background​After owning an OnePlus One (and a 2 for a brief time), the ROM development scene made the phone a beast. It was my phone for 4 years and will continue to be (in my opinion) the Holy Grail of development for Android. That phone is what brought me to this community, and why I may never switch back to Apple. This phone is the perfect phone to a lot of people including myself and I would love to see some ROMs being developed, Mods like MultiROM being produced, and more like that. I currently would like to develop a port of LineageOS to this phone however there are some concerns I have.
Concerns​I posted about this in the TWRP thread here about an issue when restoring from a Nandroid backup with TWRP how it ends in a specific error and leaves the phone bootlooped at the Sony logo. I got a response from @Myself5 here mentioning how this error isn't something @sToRm// or @Myself5 could fix. I have seen countless other posts around the internet but I have not seen a fix that works. It has something to do with storage sizes as @Myself5 mentioned in his reply.
The reason I bring up the TWRP issue is because producing custom ROMs requires a LOT of flashing and backing up ( I assume) and being able to restore would be really huge. Especially since restoring to stock requires a computer and newflasher. Once an issue like this is solved, I (and a lot of others) are most likely willing to dive into development. I really would like to start developing ROMs for Android phones as well as Mods for Magisk. If MultiROM was on the XZ Premium (which I understand would be a stretch), I think that would be very impressive.
Conclusion​The first post will be reserved for cool mods or updates on upcoming mods. This thread will change once the TWRP concerns are fixed to more of a "Mod Database" for this phone. I felt like making this post as it is a way to inform the users of this issue and also attempt to further start development on the XZ Premium. I'd like to thank @sToRm// for the DRM fix and to other developers who are willing to jump on the bandwagon like me and tear this phone apart. It is a fantastic phone, and I feel we should do something about that.
- C​

BEFORE UNLOCKING OR ROOTING, READ THIS THREAD! ONCE YOU HAVE FOLLOWED THIS THREAD, THEN PROCEED!
Mods
These enhance the current ROM you are on. They are NOT custom ROMs.
LIGHT PATCH
System Debloater
Screen Mirroring Fix, Hide VoLTE, & Data Notification icons
Soundmod
Enable Ambient Display Courtesy of @iArvee
Custom ROMs
WARNING: These ROMs are VERY unstable. Use with caution. ALWAYS backup before flashing
Note: There is no way to restore from a Nandroid Backup with TWRP.
AICP 12.1 by: @AndroPlus
AOSP 8.0 Beta 1 by: @Dutchdeveloper
Feel free to post any files you think I should add to the list! ​

Looking forward to the bright future of custom mods, kernels, roms, etc. on our G814X. I miss having @niaboc79 's eXistenZ rom on my phone.

What do you think a DRM fix will accomplish when it comes to development? Anything Lineage- or AOSP-based will not profit from this tweak, although it will attract more people to unlock their bootloaders, and by extension more people who will inevitably brick their phones and spam the Forums for help.
Also why is this in the 'Development' forum?

someone755 said:
What do you think a DRM fix will accomplish when it comes to development? Anything Lineage- or AOSP-based will not profit from this tweak, although it will attract more people to unlock their bootloaders, and by extension more people who will inevitably brick their phones and spam the Forums for help.
Also why is this in the 'Development' forum?
Click to expand...
Click to collapse
Because it is Development releated, that's why.

Alex1911 said:
Because it is Development releated, that's why.
Click to expand...
Click to collapse
Oh I'm sorry I thought the Development section was intended for things that have been developed. You know, like the name says, "ROMs, Kernels, Recoveries, & Other Development". Silly me.

glad to heard this conclusion and looking forward your ROM！ganbaru，sensei！

While this wasn't made specifically for the XZP, this overlay surprisingly works on our phone:
Enable Ambient Display:
https://forum.xda-developers.com/cr...ps/app-enable-ambient-display-xperia-t3647213

Building CM11/LineageOS 11 from latest sources

I'm pretty sure that I'll get little help on it, but I'll give it a try.
So, I want to use 4.4 KitKat on my HD2, but the only ROM available for now is NexusHD2-4.4 by tytung and others. It's based on 2.6 kernel, has built-in GAPPS and some missing settings, like the setting to turn on screenshot button in power menu. There actually was a ROM based on more clean codebase and 3.0 kernel, but all the links are dead.
The point is - I want to build my own CM11, or LineageOS 11 if I'll use the latest cm-11.0 branch from LineageOS team, without any built-in Google apps and with a 3.0 kernel. But as far as I know, literally no one made even a short guide on how to build a ROM for HD2 - the only guides I've found are about installing the already built ROM. It's a shame that nobody made these kind of guides, although the device had very big community back in the golden days.
Honestly - I'm no expert in building Android ROMs. My last attempt was building LineageOS 14.1 for Samsung Galaxy Core Prime VE SM-G361H/DS that eventually was unsuccessful - and I don't even remember why it was so. But I see that in case of HD2 the ROM should be adapted to it, because literally all Android NAND ROMs on the device have AROMA installer that provides choice between RMNET for MAGLDR and PPP for both MAGLDR and cLK and other minor things. So I'm concerned that I will need to make some modifications to ROM code to make it work like already built CM11. I can be wrong, but forgive me please, because I haven't used this device for a while, and also haven't built any ROMs for any of my devices in a while.
Also I have very little info about the device tree of HD2, especially for 4.4, but I guess that's because of my zero experience. If you can help me, you can point me to the tree, kernel and other things that are crucial when building the ROM.
So, the question is - are there any recommendations that I may follow while configuring the build? What Linux distribution should I use to build the ROM (Google recommends Ubuntu 12.04 LTS, but I can try to do it either on Ubuntu 22.04 LTS or on Arch Linux)? And what are the other obstacles that may occur while building the ROM for such an old and very, very unsupported device that I may need to overcome?
(By the way, sorry for my English, it's not my native lang, but I think you've got the point)

So, I have succesfully compiled clean LineageOS 11 for HD2 using Arch Linux and Ubuntu 12.04 in Docker container, but I think the ROM should be adapted to use on that strange device, for example NativeSD install ability is not implemented yet.

My talents lie elsewhere, but I'd be really happy to find a basic ROM that enables me to log into Google to access Google Play and download apps from there.
Can't be too advanced as the HT2 just won't cope, but it seems with the ROMS available at the moment either you can either log into Google or access wifi/data, you cannot do both.

grayme said:
a basic ROM that enables me to log into Google to access Google Play and download apps from there.
Click to expand...
Click to collapse
For me the main goal is kinda different - I want a KitKat rom that has 3.0 kernel, compiled from the latest CM11 sources available (from LineageOS team) and without any GAPPS, because I see that they really slow down the system even on Jelly Bean ROMs. I don't give any promises anyway, but I can try to insert GAPPS somehow and adapt them to be installable on HD2.
By the way, here's the link to absolutely raw and unfinished ROM, without any adaptations to HD2, just right after the compilation process: MEGA
It still needs a lot to do, because as I see now, it's built for NAND-only installation, uses ppp and not adapted to use with MAGLDR and NativeSD in any way:
Spoiler
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I wonder — why are there three different initrds for all three installation types. I'll experiment later with it, maybe I'll be really lucky and be really able to start this ROM on the device

So, I've analyzed some things, added some lines to initrd and rewrote updater-script - no luck at all. I wish I could make it bootable by any means

SuperHipster said:
I wonder — why are there three different initrds for all three installation types. I'll experiment later with it, maybe I'll be really lucky and be really able to start this ROM on the device
Click to expand...
Click to collapse
Because the fstab is in initrd and i already made data on ext ramdisk i will try to get this to boot this evening.
Any logs or sources?

J0SH1X said:
Because the fstab is in initrd and i already made data on ext ramdisk i will try to get this to boot this evening.
Any logs or sources?
Click to expand...
Click to collapse
I remember that I built it using this kernel and this tree. Unfortunately I have no logs whatsoever, because I was forced to wipe the HDD where all the sources and modifications (there were a little of them) were. And also I've got not so much time right now, I guess I'll be back when I have less problems in my personal life.