Related
Is it possible.Moto G has same pixel density and same screen resolution and chipset
Please do it it would be great
CM Actions , Kernel Selinux Changes where will they go its better to compile from source
I am a begginer i dont fully understand the whole concept of building or porting roms.But anything will work
You can give it a shot.Same kernel and chipset,should work.I will test it for sure.
Well im not good at porting i would need some help and mentoring but i would like to see Nougat run on Lenovo a6000
How about Yu Yuphoria? Same everything there too. And they've got a working build already too.
Redmi2 or prime also got nougat. Mostly ported roms frm this phone also. Pls cjeck it out...
rule breaker sarath said:
Redmi2 or prime also got nougat. Mostly ported roms frm this phone also. Pls cjeck it out...
Click to expand...
Click to collapse
Yes,indeed.I can check it out,there was a tutorial how to port roms somewhere here.Redmi 2 ports are usually pretty stable.
Allright,thats the nougat for redmi 2.Its not public yet,but seems quite promising.Guess we will have to wait until its uploaded,but if I get some free time before that I might try to port the moto g3 build(just for fun,of course it wont be as stable as redmi 2 port).
I would also try porting it using mshoaib7s guide but question is which rom to use as base
Hi, I'm kind new in creating stuff for my phones but I want to give a try and bring CM/AOSP (I know that they are totally different things) to our phones.
I've done a research and all that I found was that it wasn't possible because we haven't the kernel source. But now that it is available in the Samsumg Open Source page could we make that possible?
Thanks a lot!!
If u really did the research, u should know someone had made this before but unable to call success....
http://forum.xda-developers.com/s7-edge/development/cyanogenmod-13-galaxy-s7-edge-t3414697
pigmich said:
If u really did the research, u should know someone had made this before but unable to call success....
http://forum.xda-developers.com/s7-edge/development/cyanogenmod-13-galaxy-s7-edge-t3414697
Click to expand...
Click to collapse
Yes, i did read that, but everything i found was this:
In the case of the S7/S7E because the SOC is either closed source (Exynos) or has a locked bootloader (Qualcomm). The former makes it very difficult to produce a Rom that approaches anything near being stable, the latter makes it literally impossible until the bootloader is unlocked, which is unlikely to happen.
Click to expand...
Click to collapse
But I can't understand why if we already got the kernel source. Can't we just modify the kernel to make a kind of "mask" that allows the ROM to use the hardware correctly?
Maybe I'm asking something really stupid, and if thats the case I'm sorry, but I really want to know why we fail in this and see if I can find a workaround
Start here: http://forum.xda-developers.com/s7-edge/development/cyanogenmod-13-galaxy-s7-edge-t3414697
Get the source, make a local_manifest.xml file, get the rest of the source, edit the source code and build a rom .
But before You try, I can already tell You that it will be extremely hard to do. I've got CM to compile (yeah, compiling is actually a HUGE step) on other devices and then eventually to boot. But it took couple of days of code fixing (which I at this point somehow understand but it's still quite a magic for me).
Couple of days ago I tried building CM 13 and 14 for S7 Edge and after a whole day of fixing code and stuff I gave up. The worst issues are "shared library, excludes, includes" thingys.
Update News Flash Galaxy note 4 running Oreo 8.1
3-29-18
OMG. I said it here first. 32 bit processors CAN be ported to Oreo. Maybe not trebel yet. Smug emoticon
In just a few days , not even I thought it was possible.
Running Oreo via lineageOS 15.1 with root on my Samsung Galaxy Note 4.
The dev who devotes time to compiling builds @ripee has had his daily downloads of 14.1 for the note 4 has more than doubled. Currently running about 250 users testing builds. SMOKIN.....
Here is the OP
https://forum.xda-developers.com/no...0-unofficial-lineage-15-1-rom-t3760969/page92
Update 2-28-18
OpenGapps 8.1 is released for both arm and arm 64.
That means Oreo can be compiled it 32 bit.
Researching Oreo and Oreo go compiler instructions.
Mebbe I can compile AOSP for my older Note 4 .. So cool
https://forum.xda-developers.com/android/apps-games/arm-unofficial-opengapps-builds-android-t3743495
Updated 1-20-18
Newest musings on top. Oreo Go is currently being modded into an older Sony phone. Awesome
So since I posted this OP...my musings have been correct in these posts.
This came out on XDA, check out the links in it.
https://www.xda-developers.com/android-go-old-android-8-1-oreo/
Android Oreo and android in general is getting closer to Linux . Mainly for the same reasons
I have been installing different distributions of Linux on an older laptop.
1. To learn installing hard to find drivers
2. Learning Linux architecture and commands
3. Learning to build Linux kernel for my device
http:// www.kernel.org
4. Learning to build lineageos14 in general
With these guides
https://forum.xda-developers.com/note-4/general/guide-build-lineageos-14-1-trltexx-t3567885
Thanks @_mone and @ripee
https://forum.xda-developers.com/chef-central/android/how-to-build-lineageos-14-1-t3551484
Thanks @FSadino
5. Actually compiling lineageOS-14 for my two devices I have access to
Galaxy note 4 Verizon thanks to @ripee for his contribution by building daily's at
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-lineageos-14-1-t3536401
And my galaxy tab S2 sm-t710
Thanks to @Bonuzz for getting the camera, mic GPS and Bluetooth working, and posting sources
https://forum.xda-developers.com/tab-s2/development/t710-t715-lineage-14-1-t3713097
Thanks to @Ather for getting Samsung to release their Kernel sources and building a android 7 rom
https://forum.xda-developers.com/tab-s2/development/kernel-poseidonkernel-v1-0-permissive-t3588069
https://forum.xda-developers.com/tab-s2/development/rom-poseidonrom-v1-0-deodexedrooted-t3590228
6. Thinking and musing about things
Symlinks, multi boot, and partitions. ( Treble )
In Linux, I have another partition with downloaded files on another drive
When the kernel boots, the directory tree just sees /data even though it's a separate drive
This is because of a symbolic link that mounts the partition as a folder. This prevents me, from deleting that data with permissions
So the Trebel rules tell the vendor to make a separate partition in the drive but the kernel gets a symbolic link to it, and the user (Google) cannot over write the partition with the critical info..when the ROM gets flashed? correct ?
The bootloader has boot path a, or boot path b.
The user files are in protected memory
So with Linux, when I updated my kernel,
The grub bootloader tells me I can use kernel 4.1.x or 4.2.x when I boot
The kernel loads the drivers
And then looks at the symbolic links to mount the drives.
This is somewhere in the /etc files or somewhere
So Trebel has to be a set of decision trees based on symbic links to hardware
Where all the hardware drivers are independent of the kernel
More musings later. Must build....
**************
Dec 2017 sometime
Thanks to all for viewing my first OP.
I'm just learning about building ROMs, and look forward to this thread to spitball ideas and see what sticks.
If I don't know something its because I am correcting my ignorance.
This won't be an actually development thread, just trying to understand hardware from 30 years of not being in the tech field.
Eventually I will tire or wear out of driving truck, and work with my passion again.
I am a follow the steps kind of mind, so I am learning how the world of Android / Linux works.
If I understand the Trebel development correctly...
https://www.xda-developers.com/goog...ze-android-so-oems-can-update-devices-faster/
IF we can modify the older device drivers to be Trebel compliant, then once they work, then they always should work. And any Trebel ROM can work on Any Trebel Device withOUT compiling over and over.
This should result in an explosion of custom ROMs .
So I am suggesting a repository of drivers per device that are compliant for older devices.
How do we do that?
So here is the Google announcement of Trebel
https://android-developers.googleblog.com/2017/05/here-comes-treble-modular-base-for.html?m=1
Here is the developer preview of ”O”
https://developer.android.com/preview/download.html
It details how to install it on your Trebel Device.
Wow. Just Wow.
OH MY GOODNESS. I would love this on my lg g3, oneplus one, and moto e2. WOW.
TotalNoobTrucker said:
If I understand the Trebel development correctly...
https://www.xda-developers.com/goog...ze-android-so-oems-can-update-devices-faster/
IF we can modify the older device drivers to be Trebel compliant, then once they work, then they always should work. And any Trebel ROM can work on Any Trebel Device withOUT compiling over and over.
This should result in an explosion of custom ROMs .
So I am suggesting a repository of drivers per device that are compliant for older devices.
How do we do that?
Click to expand...
Click to collapse
How do you wanna to do that ?
Vendor files are NOT open-source so you cannot make them treble enabled sadly.
Haxk20 said:
How do you wanna to do that ?
Vendor files are NOT open-source so you cannot make them treble enabled sadly.
Click to expand...
Click to collapse
So far all it looks like ROM dev is trial and error with people posting guides on repeatable success... (Community)
I haven't built a ROM, ( haven't built a compiler computer yet) plus I drive truck 70 hrs a week..
but have read
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763/
And
https://forum.xda-developers.com/android/software/how-to-port-samsung-rom-to-samsung-t3481114/
So what's different in the building process? With Trebel?
Google dev page lists an additional partition for drivers called VENDOR
A file called manifest.xml
And a A/B partition.
So assuming I am building a Lineage OS ROM 14.x
In that compile process, everything is compiled in the ROM
Kernel, Lineage front end, AOSP programs etc.
So somewhere in the compiler process the drivers to my N910V are pulled in from somewhere? Github¿?
If they are not open source, they were pulled from system image via ADB or Android image kitchen and uploaded to where?
So i guess we need a guide on how to build Trebel for non Trebel devices. The folks on the other Trebel thread are doing it on newer devices and getting some exciting results.
There is only a couple of Lineage 15.x builds going, but once someone has the Process down to build a Trebel on non / close to Trebel hardware,
It should be repeatable for ANY Oreo and up compiled ROM.
I may not be able to build yet, but since Trebel is the new path, I want to gather Trebel success and Process here. Maybe make a guide..
In conclusion, the drivers may not be open source, but the code is out there somewhere.
Sent from my Lineage OS 14 Samsung Verizon Note 4 from @ripee
My other device is a Samsung T710 running Posiedon 1.0 . Thanks for a stable rooted tablet @Ather
Sent from my Samsung SM-N910V using XDA Labs
TotalNoobTrucker said:
So far all it looks like ROM dev is trial and error with people posting guides on repeatable success... (Community)
I haven't built a ROM, ( haven't built a compiler computer yet) plus I drive truck 70 hrs a week..
but have read
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763/
And
https://forum.xda-developers.com/android/software/how-to-port-samsung-rom-to-samsung-t3481114/
So what's different in the building process? With Trebel?
Google dev page lists an additional partition for drivers called VENDOR
A file called manifest.xml
And a A/B partition.
So assuming I am building a Lineage OS ROM 14.x
In that compile process, everything is compiled in the ROM
Kernel, Lineage front end, AOSP programs etc.
So somewhere in the compiler process the drivers to my N910V are pulled in from somewhere? Github¿?
If they are not open source, they were pulled from system image via ADB or Android image kitchen and uploaded to where?
So i guess we need a guide on how to build Trebel for non Trebel devices. The folks on the other Trebel thread are doing it on newer devices and getting some exciting results.
There is only a couple of Lineage 15.x builds going, but once someone has the Process down to build a Trebel on non / close to Trebel hardware,
It should be repeatable for ANY Oreo and up compiled ROM.
I may not be able to build yet, but since Trebel is the new path, I want to gather Trebel success and Process here. Maybe make a guide..
In conclusion, the drivers may not be open source, but the code is out there somewhere.
Sent from my Lineage OS 14 Samsung Verizon Note 4 from @ripee
My other device is a Samsung T710 running Posiedon 1.0 . Thanks
Click to expand...
Click to collapse
The OEM needs to add support for treble there is no treble for non-treble devices.
Treble works like so:
Vendor files are stored in separate partition (Those files are edited to work with treble)
Then android just takes those files from there and work.
The vendor files are not in system.img but in /vendors (the partition is mounted here)
Only a few devices have vendor files open source there is possible to make the device treble supported but 99% of devices have vendor files closed and so its not possible for some dev here to make the device supported.
Also A/B is new partition layout:
You have your system on A but once update is available its downloaded onto B and then it just switch them (Don't read about that much so I canbe wrong here).
Also I have build ROM for xperia P and if I wanted to build 8.0.0 I cannot use treble sadly that would have made my job lot easier.
Hmm.
Haxk20 said:
The OEM needs to add support for treble there is no treble for non-treble devices.
Treble works like so:
Vendor files are stored in separate partition (Those files are edited to work with treble)
Then android just takes those files from there and work.
The vendor files are not in system.img but in /vendors (the partition is mounted here)
Only a few devices have vendor files open source there is possible to make the device treble supported but 99% of devices have vendor files closed and so its not possible for some dev here to make the device supported.
Also A/B is new partition layout:
You have your system on A but once update is available its downloaded onto B and then it just switch them (Don't read about that much so I canbe wrong here).
Also I have build ROM for xperia P and if I wanted to build 8.0.0 I cannot use treble sadly that would have made my job lot easier.
Click to expand...
Click to collapse
So where are the Xperia P files you imported into your 8.0 biuld¿ Can't you put them in the vendor folder and see if it boots¿ I presume you have to make a manifest.xml file so the ROM can see the files
Sent from my Samsung SM-N910V using XDA Labs
TotalNoobTrucker said:
So where are the Xperia P files you imported into your 8.0 biuld¿ Can't you put them in the vendor folder and see if it boots¿ I presume you have to make a manifest.xml file so the ROM can see the files
Click to expand...
Click to collapse
I haven't done 8.0.0 build yet cause the device got only CM-12.1 and now trying to port 8.0.0 and no putting the files there will not work:
1. Old devices don't have that partition and evenif I reformat it and add it and edited fstab to see it.
2. The files NEEDS TO BE EDITED TO WORK WITH TREBLE. If it was that easy to make partition put there the files and tadaaa treble device then every old device could get 8.0.0 to run but well I don't see threads about it. It's not that easy you NEED THE SOURCES TO MAKE IT TREBLE ENABLED.
Haxk20 said:
I haven't done 8.0.0 build yet cause the device got only CM-12.1 and now trying to port 8.0.0 and no putting the files there will not work:
1. Old devices don't have that partition and evenif I reformat it and add it and edited fstab to see it.
2. The files NEEDS TO BE EDITED TO WORK WITH TREBLE. If it was that easy to make partition put there the files and tadaaa treble device then every old device could get 8.0.0 to run but well I don't see threads about it. It's not that easy you NEED THE SOURCES TO MAKE IT TREBLE ENABLED.
Click to expand...
Click to collapse
Sadly, I think android 8.1 trebel is 64 bit. My note 4 is a 32bit arm71
So I dunno how it could run on my note 4. However the nexus 6 is the same cpu hardware as the note 4
However the nexus 6p is the 8core with 2 other core chipset, which is 64 bit and supported by 8.1 Trebel
So me thinks the older devices are not able to run trebel
Sent from my Samsung SM-N910V using XDA Labs
TotalNoobTrucker said:
Sadly, I think android 8.1 trebel is 64 bit. My note 4 is a 32bit arm71
So I dunno how it could run on my note 4. However the nexus 6 is the same cpu hardware as the note 4
However the nexus 6p is the 8core with 2 other core chipset, which is 64 bit and supported by 8.1 Trebel
So me thinks the older devices are not able to run trebel
Click to expand...
Click to collapse
Yeah that's another problem even if there was a way to edit vendor files treble is 64bit only
If I undertand it correctly, there's another layer between the HAL and the android framework, the HIDL, which decribes the interface of the HAL.
Shouldn't we theorically be able to edit that?
The good news is my sm-t710 is a exynos5433 chipset which supports 64bit. So maybe I will get to play with 8.n someday
android1111 said:
If I undertand it correctly, there's another layer between the HAL and the android framework, the HIDL, which decribes the interface of the HAL.
Shouldn't we theorically be able to edit that?
Click to expand...
Click to collapse
I think so. If you look at the other forum, it seems they're editing only a couple files. The manifest.xml describes what files are the drivers and where to look for them. This is a crucial file, as the drivers are in a separate partition from the system/data partition now. Download one and read it .it's a very simple exchange script
TotalNoobTrucker said:
I think so. If you look at the other forum, it seems they're editing only a couple files. The manifest.xml describes what files are the drivers and where to look for them. This is a crucial file, as the drivers are in a separate partition from the system/data partition now. Download one and read it .it's a very simple exchange script
Click to expand...
Click to collapse
As I said above you NEED the vendor file sources then create /vendor partition to add the vendor files there.
Without sources you can't make Treble running.
So if you ever want to play with 8.0 on your phone you should start porting right now.
---------- Post added at 10:42 PM ---------- Previous post was at 10:41 PM ----------
TotalNoobTrucker said:
I think so. If you look at the other forum, it seems they're editing only a couple files. The manifest.xml describes what files are the drivers and where to look for them. This is a crucial file, as the drivers are in a separate partition from the system/data partition now. Download one and read it .it's a very simple exchange script
Click to expand...
Click to collapse
I mean porting as the "hard way" = modifying device tree to work with new sources and patching the sources.
Haxk20 said:
As I said above you NEED the vendor file sources then create /vendor partition to add the vendor files there.
Without sources you can't make Treble running.
So if you ever want to play with 8.0 on your phone you should start porting right now.
---------- Post added at 10:42 PM ---------- Previous post was at 10:41 PM ----------
I mean porting as the "hard way" = modifying device tree to work with new sources and patching the sources.
Click to expand...
Click to collapse
I get that to begin the process for non Trebel, that's the idea.
Move all the vendor libraries to the vendor file, and run them through the Google process to make them compliant.
I would have to find a piece of hardware that has the same SoC just to begin.
No wonder the note 4 stalled at 6.0.1, verizion want going to rewrite the code. Just to get to 7. They would rather sell note 8's
Sent from my Samsung SM-N910V using XDA Labs
See scenario 2 on
source android com devices architecture hidl-cpp
We need to code o adapt a passthrough HIDL
It's not a matter of editing a file
TotalNoobTrucker said:
I think so. If you look at the other forum, it seems they're editing only a couple files. The manifest.xml describes what files are the drivers and where to look for them. This is a crucial file, as the drivers are in a separate partition from the system/data partition now. Download one and read it .it's a very simple exchange script
Click to expand...
Click to collapse
It's not a matter of editing a file to tell Android and the kernel where to look for drivers. We are not "editing" manifest.xml, it is generated during the build process. The whole structure and system calls of the drivers is changed to make them suitable for treble. And that is done by the SoC vendor whomever they may be. You can build Oreo to work on older devices by using your existing drivers, but not by using treble, you have to use your existing kernel, and write your own "hooks" into your existing drivers (better be familiar with hex code), and do a LOT of modifications to the Android code. Treble is not intended as a way for older devices to get custom ROMs, as their pre Oreo kernels and drives are not capable.
A N00b's explanation of Project Treble
Okay so I've seen a lot of confusion about how Project Treble does and does not work, so I'm going to provide a small explanation, simplified to a fault, but it'll do:
In ye olden days (Nougat and back), the Android OS was very tightly integrated with the drivers of the system. This made custom firmware very difficult to port (relatively speaking). Certain drivers were more difficult to make workable and as a result you'd have work in progress ROMs that didn't have WI-FI or cameras working, etc. It really was a pain in the butt.
Project Treble changes all of that. What it does is separate the operating system from the drivers, making porting much easier for devices that support it. The problem is that in order to enable this it would require almost a complete rebuild of these drivers, which would in turn require access to the source code and a LOT of work (hence why companies like OnePlus are releasing devices with Nougat so they don't have to use Treble, which is required on all devices that start with Oreo).
In short, COULD Treble be ported to older devices? Yes; Google and Essential have proven that. Is it feasible? Unless you've got some friends at Samsung/HTC/Xiaomi/insert-other-company-here willing to leak source code, no not really. The only device that I could possibly see getting a Treble port is the HTC HD2, simply because that phone is basically the technological equivalent of a cockroach, and I think they may have actually reverse engineered their drivers to get them to work on so many operating systems. I know I've probably made some mistakes in my explanation, but it's my best way if simplifying how this works so that people don't come along, see Treble and expect an Oreo ROM for their Fire Phone or something
2390 said:
Okay so I've seen a lot of confusion about how Project Treble does and does not work, so I'm going to provide a small explanation, simplified to a fault, but it'll do:
In ye olden days (Nougat and back), the Android OS was very tightly integrated with the drivers of the system. This made custom firmware very difficult to port (relatively speaking). Certain drivers were more difficult to make workable and as a result you'd have work in progress ROMs that didn't have WI-FI or cameras working, etc. It really was a pain in the butt.
Project Treble changes all of that. What it does is separate the operating system from the drivers, making porting much easier for devices that support it. The problem is that in order to enable this it would require almost a complete rebuild of these drivers, which would in turn require access to the source code and a LOT of work (hence why companies like OnePlus are releasing devices with Nougat so they don't have to use Treble, which is required on all devices that start with Oreo).
In short, COULD Treble be ported to older devices? Yes; Google and Essential have proven that. Is it feasible? Unless you've got some friends at Samsung/HTC/Xiaomi/insert-other-company-here willing to leak source code, no not really. The only device that I could possibly see getting a Treble port is the HTC HD2, simply because that phone is basically the technological equivalent of a cockroach, and I think they may have actually reverse engineered their drivers to get them to work on so many operating systems. I know I've probably made some mistakes in my explanation, but it's my best way if simplifying how this works so that people don't come along, see Treble and expect an Oreo ROM for their Fire Phone or something
Click to expand...
Click to collapse
So who do we know at Samsung/HTC/Xiaomi ?
Haha.
Or better yet who do we ask there? Do they have only internal development? Customer service? How do some Devs get source code? When a company releases a developers version ( thankfully someone had a way to flash a dev version 5.1.1 of my verizion note 4 so it could get a ROM.. ), does the developers edition phone come with the support and access of developers?
The reason I ask. Is I used to have MSDN access when I worked at [email protected]#$0ft . just asking again. What's the path to be a developer from a builder like Samsung?
Good luck with that
TotalNoobTrucker said:
So who do we know at Samsung/HTC/Xiaomi ?
Haha.
Or better yet who do we ask there? Do they have only internal development? Customer service? How do some Devs get source code? When a company releases a developers version ( thankfully someone had a way to flash a dev version 5.1.1 of my verizion note 4 so it could get a ROM.. ), does the developers edition phone come with the support and access of developers?
The reason I ask. Is I used to have MSDN access when I worked at [email protected]#$0ft . just asking again. What's the path to be a developer from a builder like Samsung?
Click to expand...
Click to collapse
You're going to have better luck getting blood out of a rock than that. Even when they have "developer" editions of phones they don't give you access to their code, that just means it's totally unlocked for you to f*** up or flash ROMs to. The phone manufacturers get the drivers for the SoC from the manufacturer of the chip, and except in binary form that never leaves and stays in house. Only way you're going to get that is by knowing someone who works at Qualcomm, Samsung, etc. who is willing to risk being fired, sued, thrown in jail, or all of the above for stealing the source code and leaking it to you. When a phone manufacturer releases "source code" if you examine it you will find that those closed source drivers are not included, you can build it but a lot of things won't work. (Besides the fact that it is always outdated code).
Are You Like Me?
Have you remained Vigilant.. and kept your 7x a Virgin?
Untouched by the rough hands of another country's software.. resisting the unwanted pressures of your peers to unlock your chastity belt.. (A.K.A.) your bootloader.. to give in to what's been described as plethora of pleasure known as:
TWRP.. Root.. ROM's ( As Unstable As They Currently Are On The 7x )
Well..
I'm happy to say Gratification is just around the corner..
U.S.A. Variants ( BND-24) Versions of the 7x will recieve the "OFFICIAL AND 100% STABLE" release of EMUI / OREO 8.0 within the next 72 hours of this writing via an O.T.A. update from Honor.
I'm So Glad I Stayed Locked & Stock
Congratulations Honor!
You came through!!! :good:
RaiderWill said:
Are You Like Me?
Have you remained Vigilant.. and kept your 7x a Virgin?
Untouched by the rough hands of another country's software.. resisting the unwanted pressures of your peers to unlock your chastity belt.. (A.K.A.) your bootloader.. to give in to what's been described as plethora of pleasure known as:
TWRP.. Root.. ROM's ( As Unstable As They Currently Are On The 7x )
Well..
I'm happy to say Gratification is just around the corner..
U.S.A. Variants ( BND-24) Versions of the 7x will recieve the "OFFICIAL AND 100% STABLE" release of EMUI / OREO 8.0 within the next 72 hours of this writing via an O.T.A. update from Honor.
I'm So Glad I Stayed Locked & Stock
Congratulations Honor!
You came through!!! :good:
Click to expand...
Click to collapse
Unlocking the bootloader has nothing to do with taking ota, flashing a custom recovery does. People that rooted would have problems with taking the ota.
You State The Obvious..
EnIXmA said:
Unlocking the bootloader has nothing to do with taking ota, flashing a custom recovery does. People that rooted would have problems with taking the ota.
Click to expand...
Click to collapse
Who Unlocks Their Bootloader To Look At That Hidious Exclaimation Warning! Screen And Not Modify Their Device?
You State The Obvious.
Of Course You Blow Your O.T.A.'s..
And You Also Rush To Root... And Brick.. Based On How Many "HELP ME!" Threads Now Saturate The 7x Threads.
RaiderWill said:
Who Unlocks Their Bootloader To Look At That Hidious Exclaimation Warning! Screen And Not Modify Their Device?
You State The Obvious.
Of Course You Blow Your O.T.A.'s..
And You Also Rush To Root... And Brick.. Based On How Many "HELP ME!" Threads Now Saturate The 7x Threads.
Click to expand...
Click to collapse
I just got this device. I was on here seeing if theres a way to unlock bootloader and return to factory later. Because I knew the Oreo was coming soon. That's great news. I thought it was coming in May. So I'll just chill and wait for ota for now. Will honor come through when it comes to letting us unlock out bootloader that is the question. Or are they just working on updating a faster bootloader unlock process for us?
A Suggestion...
allrockedout said:
I just got this device. I was on here seeing if theres a way to unlock bootloader and return to factory later. Because I knew the Oreo was coming soon. That's great news. I thought it was coming in May. So I'll just chill and wait for ota for now. Will honor come through when it comes to letting us unlock out bootloader that is the question. Or are they just working on updating a faster bootloader unlock process for us?
Click to expand...
Click to collapse
Congrats On Purchasing A Fine Device...
LEAVE IT STOCK.
Take A Look Around The Threads..
Look at how many have bricked their 7x's
In Such A Hurry To Root... For What?
There Is Not A Stable Fully Functional Custom ROM Out There For The 7x.
There Are NO United States Of America FACTORY IMAGES Out There For The 7x.
You can eh.... Flash a Stock ROM from another country At Your Own Risk Of Course.
Have you stopped to ask yourself.. why Honor has not released Factory Images for this device.. that was announced in October of 2017 and released December 7th 2017 ?
People are actually PAYING services out there to recover their 7x's.... because they go down the rabbit hole and can't get out.
How Sad Is That...
You Were Wise To Stay Locked & Stock.. :good:
In about 60 hours you'll get your payoff..
Wait until Decryption is resolved before you Root.
Wait until a U.S.A. Factory Image is released before you Root.
You Can Do Everything With A STOCK 7x That You Can Do With A Rooted 7x
You don't need backups.... STOCK ROM'S DON'T CRASH... AND "FACTORY RESET IS YOUR BACKUP" when you don't root.
RaiderWill said:
Who Unlocks Their Bootloader To Look At That Hidious Exclaimation Warning! Screen And Not Modify Their Device?
You State The Obvious.
Of Course You Blow Your O.T.A.'s..
And You Also Rush To Root... And Brick.. Based On How Many "HELP ME!" Threads Now Saturate The 7x Threads.
Click to expand...
Click to collapse
I did, so I don't have to lose my data once factory images are available and I decide to root it in the future.
Yeah exactly the same reason as the post above mine. I unlocked the bootloader the day I got the phone so that way when the time comes to do any rooting or modding I wouldn't have to wipe my phone and lose everything. And I've still received all the ota updates on the L24 thus far with the unlocked bootloader.
RaiderWill said:
Congrats On Purchasing A Fine Device...
LEAVE IT STOCK.
Take A Look Around The Threads..
Look at how many have bricked their 7x's
In Such A Hurry To Root... For What?
There Is Not A Stable Fully Functional Custom ROM Out There For The 7x.
There Are NO United States Of America FACTORY IMAGES Out There For The 7x.
You can eh.... Flash a Stock ROM from another country At Your Own Risk Of Course.
Have you stopped to ask yourself.. why Honor has not released Factory Images for this device.. that was announced in October of 2017 and released December 7th 2017 ?
People are actually PAYING services out there to recover their 7x's.... because they go down the rabbit hole and can't get out.
How Sad Is That...
You Were Wise To Stay Locked & Stock.. :good:
In about 60 hours you'll get your payoff..
Wait until Decryption is resolved before you Root.
Wait until a U.S.A. Factory Image is released before you Root.
You Can Do Everything With A STOCK 7x That You Can Do With A Rooted 7x
You don't need backups.... STOCK ROM'S DON'T CRASH... AND "FACTORY RESET IS YOUR BACKUP" when you don't root.
Click to expand...
Click to collapse
Yeah but stock ROMs send your data to the Chinese government
str8stryk3r said:
Yeah exactly the same reason as the post above mine. I unlocked the bootloader the day I got the phone so that way when the time comes to do any rooting or modding I wouldn't have to wipe my phone and lose everything. And I've still received all the ota updates on the L24 thus far with the unlocked bootloader.
Click to expand...
Click to collapse
Still can't believe they took down the BL unlock site.
Sent from my BND-L24 using Tapatalk
I Fully Understand Your Reasoning..
EnIXmA said:
I did, so I don't have to lose my data once factory images are available and I decide to root it in the future.
Click to expand...
Click to collapse
It's A Logical Path To Pursue...
I have NO FAITH in Honor releasing Factory Images in the near future.
I think there is a "Method Behind The Madness"
Personally, my Android Data is all backed up in 2 places.. and it's all Android - Centric
I would NEVER do ANY personal business (Banking , Shopping Etc) on any Android device.
Especially an HUAWEI / HONOR device.. for all the reasons my Government has stated.
This is not a "Long-Term" solution phone for me personally.. It will be sold.. actually it would have already been sold, but I had $900.00 vehicle repair snatch my OnePlus 6 money right out of my hands..
This device was a Failure as far as gaining Developer support...
No Custom Kernels: "Franco's Kernel" oh if only... ( So why root.. You can't under / overvolt, swap governers, add features etc )
Even though Kernel Source was released 5 months ago.
It appears... Treble Ports are the way of the Future. I'm not complaining just stating facts.. ( I guess if I loved the 7x that much I would learn how to pack a Kernel for myself and use it..) but I don't love the 7x and it's Kirin Technology enough to do so.
This device will just never gain ground or love.. is hated by my government.. has the Un-popular ( For Developer's ) Kirin Processor and a weak GPu.
What it does have is Oreo 8.0 and Project Treble Support baked in.
Let's keep it shinny and in "Like-New" condition.. Pure Stock ( No Warning! Screens NEVER Modified in any way ) and ready to sell...
That's The Ticket.
So I'm unlocked rooted and running TWRP on my l24 does that mean I miss out on emui 8 or are there any Solutions
RaiderWill said:
It's A Logical Path To Pursue...
I have NO FAITH in Honor releasing Factory Images in the near future.
I think there is a "Method Behind The Madness"
Personally, my Android Data is all backed up in 2 places.. and it's all Android - Centric
I would NEVER do ANY personal business (Banking , Shopping Etc) on any Android device.
Especially an HUAWEI / HONOR device.. for all the reasons my Government has stated.
This is not a "Long-Term" solution phone for me personally.. It will be sold.. actually it would have already been sold, but I had $900.00 vehicle repair snatch my OnePlus 6 money right out of my hands..
This device was a Failure as far as gaining Developer support...
No Custom Kernels: "Franco's Kernel" oh if only... ( So why root.. You can't under / overvolt, swap governers, add features etc )
Even though Kernel Source was released 5 months ago.
It appears... Treble Ports are the way of the Future. I'm not complaining just stating facts.. ( I guess if I loved the 7x that much I would learn how to pack a Kernel for myself and use it..) but I don't love the 7x and it's Kirin Technology enough to do so.
This device will just never gain ground or love.. is hated by my government.. has the Un-popular ( For Developer's ) Kirin Processor and a weak GPu.
What it does have is Oreo 8.0 and Project Treble Support baked in.
Let's keep it shinny and in "Like-New" condition.. Pure Stock ( No Warning! Screens NEVER Modified in any way ) and ready to sell...
That's The Ticket.
Click to expand...
Click to collapse
How long you think it'll take for treble to be active for this device? I'm considering updating to the beta so I can then use the RR rom but whats the point if I can just wait a few days to get official Oreo and then be all in with treble. I guess I don't fully understand what treble is nor it's immediate relation to this device.
carnivalrejectq said:
How long you think it'll take for treble to be active for this device? I'm considering updating to the beta so I can then use the RR rom but whats the point if I can just wait a few days to get official Oreo and then be all in with treble. I guess I don't fully understand what treble is nor it's immediate relation to this device.
Click to expand...
Click to collapse
Treble will help get custom ROMs on our device faster. Just wait for official Oreo. Than we unlock bootloader. Wait for updated twrp with Oreo support. Than custom ROMs. Than would need treble support twrp. So we still have a ways to go for treble and custom ROMs. But we're getting close.
carnivalrejectq said:
How long you think it'll take for treble to be active for this device? I'm considering updating to the beta so I can then use the RR rom but whats the point if I can just wait a few days to get official Oreo and then be all in with treble. I guess I don't fully understand what treble is nor it's immediate relation to this device.
Click to expand...
Click to collapse
This is a simplified explanation of how Treble works, or at least my simple understanding of it. Google requires any device shipping with Oreo to have the main OS reside in its own partition separate from the OEM vender stuff.
Is no one else going to comment on how crazy this guy is?
Why Wait ?
carnivalrejectq said:
How long you think it'll take for treble to be active for this device? I'm considering updating to the beta so I can then use the RR rom but whats the point if I can just wait a few days to get official Oreo and then be all in with treble. I guess I don't fully understand what treble is nor it's immediate relation to this device.
Click to expand...
Click to collapse
Listen... You Don't Need To Wait For Anything...
I MAY BE 100% INCORRECT.. BUT, IT'S MY UNDERSTANDING THAT HUAWEI / HONOR HAS STOPPED THE ABILITY TO RETREIVE YOUR UNLOCK CODE (OFFICIALLY) FROM THEIR WEBSITE.
If True...
Do you know what that means?
It means... they MAY NOT enable the Vendor Partition in the OFFICIAL ( O.T.A. ) version of Oreo / EMUI 8.0 that will be released in about 48 hours from the time of this writing.
Without That Partition.... Project Treble is a NO GO.
In your case.. If all you want to do is run the ROM you mentioned, just use the Bootleg Method posted elsewhere in these threads to Unlock your bootloader.. Install one of these Unofficial TWRP's floating around... and install your ROM.
Done.
Why Wait?
For the Official Release of Oreo on Monday when all you are going to do is Overwrite it with a ROM posted elsewhere?
Sounds Like You Know What You Want...
Go For It.
Stock Oreo has NOTHING OF INTEREST for those that just want to flash Beta ROM's
Stock Oreo / EMUI 8.0 is for those of us that put 100% Stability and FULL Functionality First & Foremost..
I paid 100% of the Price for this Device.
I Personally.. Want 100% OF THE DEVICE'S SOFTWARE & FEATURES FUNCTIONAL...
At this point in the 7x's development... Only Stock EMUI provides that level of performance.
RaiderWill said:
Listen... You Don't Need To Wait For Anything...
I MAY BE 100% INCORRECT.. BUT, IT'S MY UNDERSTANDING THAT HUAWEI / HONOR HAS STOPPED THE ABILITY TO RETREIVE YOUR UNLOCK CODE (OFFICIALLY) FROM THEIR WEBSITE.
If True...
Do you know what that means?
It means... they MAY NOT enable the Vendor Partition in the OFFICIAL ( O.T.A. ) version of Oreo / EMUI 8.0 that will be released in about 48 hours from the time of this writing.
Without That Partition.... Project Treble is a NO GO.
In your case.. If all you want to do is run the ROM you mentioned, just use the Bootleg Method posted elsewhere in these threads to Unlock your bootloader.. Install one of these Unofficial TWRP's floating around... and install your ROM.
Done.
Why Wait?
For the Official Release of Oreo on Monday when all you are going to do is Overwrite it with a ROM posted elsewhere?
Sounds Like You Know What You Want...
Go For It.
Stock Oreo has NOTHING OF INTEREST for those that just want to flash Beta ROM's
Stock Oreo / EMUI 8.0 is for those of us that put 100% Stability and FULL Functionality First & Foremost..
I paid 100% of the Price for this Device.
I Personally.. Want 100% OF THE DEVICE'S SOFTWARE & FEATURES FUNCTIONAL...
At this point in the 7x's development... Only Stock EMUI provides that level of performance.
Click to expand...
Click to collapse
I actually like EMUI. I'm just concerned about the whole Chinese government thing mostly lol.
monorail0 said:
Is no one else going to comment on how crazy this guy is?
Click to expand...
Click to collapse
Haha yeah, and the extensive use of emojis really gets on the nerves.
carnivalrejectq said:
I actually like EMUI. I'm just concerned about the whole Chinese government thing mostly lol.
Click to expand...
Click to collapse
If I Handled My Personal Business On A Cell Phone... I'd Be Concerned Too...
If all you have are Android Apps.... who cares.
That's a PERSONAL CHOICE as to how much of your life you trust to divulge to your cellular devices.
And Yeah... as far as features an the ability to Customize a Pure Stock device, EMUI Kicks Ass and Takes Names :good:
And it's Soooooo Stable and Smooth.. and has 10 TIMES the Developer Support for Customization of what you ACTUALLY interact with.. than those who worry about what the Developer - Unfriendly Kirin Engine is doing.
It Cracks Me Up how many have went Ape S*it trying to Root and have bricked.. then are like OH MY GOD! HELP ME!
Leave the Damn thing "STOCK" until the day you have REAL REGIONAL FIRMWARE available to you.. To Fix Your Boo-Boos.. And leave all these BOOTLEG methods starting to pop up left and right alone.
ahmad.o said:
Haha yeah, and the extensive use of emojis really gets on the nerves.
Click to expand...
Click to collapse
Hey Ahmad...
Here is a way to avoid seeing my emo's
I ONLY POST IN "MY THREADS" WHEN IT COMES TO THE 7X... THERE IS NOTHING ELSE OF RELEVANCE HERE ANYMORE EVEN WORTHY OF MY TIME..
I'm sick of seeing " Help Me! My 7x has fallen and can't get up! " threads.
So you pretty much will not see RAIDERWILL & HIS EMO'S anywhere but in a thread he created.
SO AHMAD... JUST STAY AWAY FROM "A-N-Y" RAIDERWILL THREADS.... AND YOU'LL BE GOOD-TO-GO.
Why?
monorail0 said:
Is no one else going to comment on how crazy this guy is?
Click to expand...
Click to collapse
Monorail ? :laugh: You Have A Singular Wit.
If I'm insane.... Then Why Are You Reading The Comments Of A Madman?
Have You Asked Yourself that mono....
I Don't Know.... Over 1/2 of all the comments I've ever made on XDA have been "Thanked" for being useful or insightful.
But... since you're *Correct* in your assessment of RAIDERWILL... I guess the 500 or so others were either just as insane as RAIDERWILL for giving him Acknowledgment with a " Thanks! " or simply don't possess your keen insight...
Or... could it be that.. ANYONE on this rock we refer to as Earth.. that has the Unmitigated Gall to Disagree with YOU Monorail should be Hanged, Drawn and Quartered !!! :laugh:
Pssssst.... Hey You...... Over Here.. I'm going to tell you a secret to help ease your Ailment...
*Simply Don't Read RAIDERWILL'S COMMENTS OR THREADS..*
Done.
so after long searching it finally clear to me that
- treble partition and recovery are available
- Can flash GSI/Treble rom but with quirks, e.g. bluetooth, hotspot not working
- Missing shims? Updated vendor partition?
so we need a great dev to work on it??
if great dev starts the project and start a pool for collecting $$$ as support i'll gladly donate $10us I'm sure more people will join too....
especially now that MIUI has finally released the final version https://www.xda-developers.com/xiaomi-redmi-note-3-final-miui-10-stable-update/
optionalmgrr.la said:
if great dev starts the project and start a pool for collecting $$$ as support i'll gladly donate $10us I'm sure more people will join too....
especially now that MIUI has finally released the final version https://www.xda-developers.com/xiaomi-redmi-note-3-final-miui-10-stable-update/
Click to expand...
Click to collapse
Who gonna rewrite vendor code? Its not devs work. It comes from vendor and silicon manufacturer. They knows their hardware. So they work closely with google to write vendor blobs.
Why u want treble rom? Flashing gsi doesnt give u more performance and stabilty. They are more buggy than non treble rom. Non treble rom are device specific so have less bugs.
Kenzo will get android 10 and thats enough. After that 5g phones will hit the market and all will rush for it. So dont assume kenzo will survive till 2050 if we make it treble :laugh:
5G is going to be a flop like 3D TV.
If there is official LineageOS 16.0 then it's ok, but all other ROMs are too flicky they don't even support SELinux.
All those 1000s of different ROMs are basically the same base just add on top different customizations. That's why all 9.0 ROM are SELinux permissive.
In short, too many fancy half-working stuffs without any substance. We need a substantiated deve to help us out of this mess......
optionalmgrr.la said:
5G is going to be a flop like 3D TV.
If there is official LineageOS 16.0 then it's ok, but all other ROMs are too flicky they don't even support SELinux.
All those 1000s of different ROMs are basically the same base just add on top different customizations. That's why all 9.0 ROM are SELinux permissive.
In short, too many fancy half-working stuffs without any substance. We need a substantiated deve to help us out of this mess......
Click to expand...
Click to collapse
Do u even know how selinux works.
What do u mean they dont even support selinux.? Every rom has selinux support since kitkat.
Why dont u write ur perfect selinux policy and help to this devs so that it can be enforced on pie.
And whats there in lineage official rom which other roms dont have. Lineage official has its rules which cant be met for older phones which has old vendor blobs. Difficult to get official status.
And Who really give damn about lineage official.
Other roms are more customizable and have far more better and miles ahead in features then los rom.
And what u mean by mess? Xiaomi gave mm blobs coz official miui on android 6. Then from where we will get latest code if qualcomm is not updating code for sd650.
Only stuff is broken on pie is Vilte. If u have selinux priority then use Citrus.
ok thx
Forget about project trouble for our kenzo