• If you are experiencing issues logging in, we moved to a new and more secure software and older account passwords were not able to be migrated. We recommend trying to reset your password, then contacting us if there are issues.
  • Nearly done! Migration cleanup is mostly done. There are a small number of issues left that we continue to work on, but all the heavy lifting is done. We still would love to hear feedback over at this thread and also check out the new XDA app! Thanks and we hope you enjoy the new forums, and thanks for your support of XDA <3

[ROM][e610][UBER TC][AOSP-CAF] GlazeOS | Experimental Build (02/04/2017)

ROM-PacMe

Member
Dec 14, 2013
22
55
0
Los Ángeles


Code:
/* Disclaimer 
* I am not responsible for bricked devices, dead SD cards, thermonuclear war, 
* or you getting fired because the alarm app failed. Please do some research 
* if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you blame me in any way for what happens to your device, I will laugh at you.
* BOOM! goes the dynamite
*/

About GlazeOS:
Glaze OS is a free, open-source, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. It offers features not found in the official Android based firmwares of vendors.

AOSP
Based on Android Open Source Project.

Linaro Optimized
Linaro’s GCC improvements have been producing measurable performance advantages over Google’s stock Android environment and build toolchain, delivering an improvement of 30 to 100 percent in various benchmarks.

Enablement for Qualcomm MSM
The Android for MSM project allows users to build an Android based platform containing additional enhancements for Qualcomm chipsets. The platform uses Google's Android Linux implementation and tools.

Substratum Theme Engine
Based on Sony's Overlay Manager Service (OMS). This is similar to Layers in terms of stability and customization as it runs off an upgraded version of the Resource Runtime Overlay system, with the added benefit of running up-to-date Sony code on a customized ROM.

Customization
Soon :D:laugh::cool:


BUGS
  • Camera
  • Wi-Fi

You tell me more bugs :3

Downloads:
GlazeOS for e610
Gapps ARM->7.1->PICO Recommended

Flashing Instructions:
  • Download GlazeOS-v1.0-EXPERIMENTAL-e610-2017XXXX-XXXX.zip
  • Copy to SD-CARD
  • Wipe dalvik, cache and system.
  • Install ROM and GAPPS
  • Reboot system

Screenshots:




Credits:
  • Team Subtratum
  • Team Linaro
  • AOSP
  • Team LineageOS
  • Team GlazeOS
  • And More People :3 :D

XDA:DevDB Information
GlazeOS, ROM for the LG Optimus L5

Contributors
ROM-PacMe, ROM-PacMe
Source Code: https://github.com/GlazeOS

ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: AOSP-CAF

Version Information
Status: Testing

Created 2017-04-02
Last Updated 2017-04-02
 
Last edited:

adeii

Senior Member
Nov 11, 2013
322
83
28
Sajlent Hil
I finished compiling GlazeOS (android 7.1.2_r8) for LG L7 II (Vee7).
https://www.androidfilehost.com/?fid=745425885120732876 Anyone want to try?!
NOTE: Do not flash recovery from this ROM, it will not work and maybe damage /recovery partition!

My main job is to make nougat rom for Huawei Y300/G510 since there is none till today, but first to made working rom for LG L7 II, because of more resources and because of similar specifications (same CPU, GPU, RAM).
 
Last edited:

XDA-00

Senior Member
Sep 6, 2015
348
49
0
New Delhi
I finished compiling GlazeOS (android 7.1.2_r8) for LG L7 II (Vee7).
https://www.androidfilehost.com/?fid=745425885120732876 Anyone want to try?!
NOTE: Do not flash recovery from this ROM, it will not work and maybe damage /recovery partition!

My main job is to make nougat rom for Huawei Y300/G510 since there is none till today, but first to made working rom for LG L7 II, because of more resources and because of similar specifications (same CPU, GPU, RAM).
Hi. I am not able to flash the rom. I am getting 'signal 4 error' right at the start.
It failed even after removing assert() functions and otasigcheck. Maybe the updater-script is corrupted.
Kindly fix this issue.

Can't wait to try this one.
 

adeii

Senior Member
Nov 11, 2013
322
83
28
Sajlent Hil
@adeii
Maybe the logs will help???
I modified the boot.img (ro.secure=1 ---> 0)
Can't get past the boot LOGO/LG Logo (not to be confused with bootanimation).
Thank you for trying. I do not know why is not booting.
Device tree is from: https://github.com/LegacyLG
I also got flashing error 4, on TWRP 3.1.0.0, on Y300, use update-binaries fro 6.0.1 rom to finish installing.
Also do not boot, keeps restarting on Huawei logo screen.
In your log, there are errors like:
0.000000] smem_find(137, 80): wrong size 64
0.000000] smem_find(137, 72): wrong size 64
0.094871] vddx_c2: 750 <--> 1500 mV at 1150 mV normal
0.094999] Error-Bad Function Input
0.187663] CRASH LOG START ADDR : 0x1ff3e000
0.187854] CRASH LOG END ADDR : 0x1ff3efff
0.225056] qup_i2c qup_i2c.1: I2C slave addr:0x3e not connected
0.225269] sx150x 1-003e: i2c write fail: can't write 01 to 1f: -107
0.225624] sx150x: probe of 1-003e failed with error -107
0.447166] get_nand_partitions: no flash partition table in shared memory
0.456164] rpcrouter: Server create rejected, version = 0, program = 3000003b

Do you know what could make them?
 

XDA-00

Senior Member
Sep 6, 2015
348
49
0
New Delhi
Thank you for trying. I do not know why is not booting.
Device tree is from: https://github.com/LegacyLG
I also got flashing error 4, on TWRP 3.1.0.0, on Y300, use update-binaries fro 6.0.1 rom to finish installing.
Also do not boot, keeps restarting on Huawei logo screen.
In your log, there are errors like:
0.000000] smem_find(137, 80): wrong size 64
0.000000] smem_find(137, 72): wrong size 64
0.094871] vddx_c2: 750 <--> 1500 mV at 1150 mV normal
0.094999] Error-Bad Function Input
0.187663] CRASH LOG START ADDR : 0x1ff3e000
0.187854] CRASH LOG END ADDR : 0x1ff3efff
0.225056] qup_i2c qup_i2c.1: I2C slave addr:0x3e not connected
0.225269] sx150x 1-003e: i2c write fail: can't write 01 to 1f: -107
0.225624] sx150x: probe of 1-003e failed with error -107
0.447166] get_nand_partitions: no flash partition table in shared memory
0.456164] rpcrouter: Server create rejected, version = 0, program = 3000003b

Do you know what could make them?
https://github.com/search?utf8=✓&q=vee7&type=

Some of the links are from nicknitewolf. Just Saying.

I tried TWRP 3.1.1-0 made by him and it did not work. Wasn't able to boot into recovery.:(

You should recheck the kernel.
Maybe, you can try this source=https://github.com/weritos666/Vee7

OR THIS :- https://github.com/TeamHackLG/android_device_lge_msm7x27a-common

I really can't help much:(, but you can ask neutrondev or weritos for help, they might solve the issue and if you recompile the rom, just change the value of ro.secure to 0 (in default.prop of kernel)

OR Maybe you can ask for help at modaco too.

Do you know what could make them?
Maybe the file_contexts.bin is corrupt? Isin't it supposed to be just file_contexts (without .bin extension)?
Thats all I can say. :)
Lets hope someone fixes the issue and we'll have nougat for our devices.

Edit :- just realized that the fork should be from msm7x27 not msm7x30 (see attachment)
and re-check fstab.vee7, there might be some error regarding partitions/blocks.
 
Last edited:

adeii

Senior Member
Nov 11, 2013
322
83
28
Sajlent Hil
https://github.com/search?utf8=✓&q=vee7&type=

Some of the links are from nicknitewolf. Just Saying.

I tried TWRP 3.1.1-0 made by him and it did not work. Wasn't able to boot into recovery.:(

You should recheck the kernel.
Maybe, you can try this source=https://github.com/weritos666/Vee7

OR THIS :- https://github.com/TeamHackLG/android_device_lge_msm7x27a-common

I really can't help much:(, but you can ask neutrondev or weritos for help, they might solve the issue and if you recompile the rom, just change the value of ro.secure to 0 (in default.prop of kernel)

OR Maybe you can ask for help at modaco too.



Maybe the file_contexts.bin is corrupt? Isin't it supposed to be just file_contexts (without .bin extension)?
Thats all I can say. :)
Lets hope someone fixes the issue and we'll have nougat for our devices.

Edit :- just realized that the fork should be from msm7x27 not msm7x30 (see attachment)
and re-check fstab.vee7, there might be some error regarding partitions/blocks.
Thanks a lot for reply. I hope I'll find errors. Have you tried to boot with newboot.img ? Somewhere is written that TWRP 3.0.3.0 should be enough to boot 7.1.1...but this is 7.1.2.
 

XDA-00

Senior Member
Sep 6, 2015
348
49
0
New Delhi
Thanks a lot for reply. I hope I'll find errors. Have you tried to boot with newboot.img ? Somewhere is written that TWRP 3.0.3.0 should be enough to boot 7.1.1...but this is 7.1.2.
You're welcome. And no I did not try, I'm done.. for now.

I have TWRP 3.0.2-0. Its the only working recovery.

Try contacting weritos or neutrondev.
 

Gent'

Senior Member
Apr 5, 2016
501
232
0
Mitrovica
@adeii

Maybe the logs will help???
I modified the boot.img (ro.secure=1 ---> 0)
Can't get past the boot LOGO/LG Logo (not to be confused with bootanimation).
How did you manage to make logs while booting the device?I cant figure out how to do that.
I set persist.sys.usb=adb and ro secure=0 but adb says device unauthorized.

Thanks.
 

XDA-00

Senior Member
Sep 6, 2015
348
49
0
New Delhi
How did you manage to make logs while booting the device?I cant figure out how to do that.
I set persist.sys.usb=adb and ro secure=0 but adb says device unauthorized.

Thanks.
After kernel crash/bootloop, goto twrp > advanced > terminal and type :

For kernel log :-

cat /proc/last_kmsg > /sdcard/last_kmsg.text

For dmesg :-

dmesg > /sdcard/dmesg.txt

Edit :- set persist.adb.debugging to 1 if not done already.
 
Last edited:
  • Like
Reactions: Gent'

adeii

Senior Member
Nov 11, 2013
322
83
28
Sajlent Hil
https://github.com/search?utf8=✓&q=vee7&type=
You should recheck the kernel.
Maybe, you can try this source=https://github.com/weritos666/Vee7

Maybe the file_contexts.bin is corrupt? Isin't it supposed to be just file_contexts (without .bin extension)?
Kernel is changed to weritos' Vee7.
https://www.androidfilehost.com/?fid=817550096634773143 try this kernel.
From 7.0 it is changed to file_contexts.bin, no more textual file contexts.

Newer kernel, with updated fstub.qcom and ro.secure and ro.adb.secure=0 at https://www.androidfilehost.com/?fid=961840155545568953
 

XDA-00

Senior Member
Sep 6, 2015
348
49
0
New Delhi
Kernel is changed to weritos' Vee7.
https://www.androidfilehost.com/?fid=817550096634773143 try this kernel.
From 7.0 it is changed to file_contexts.bin, no more textual file contexts.

Newer kernel, with updated fstub.qcom and ro.secure and ro.adb.secure=0 at https://www.androidfilehost.com/?fid=961840155545568953
Did not boot man. I tried both kernels but did not succeed.:(
See logcat.

KMSG :- https://pastebin.com/dvDjz6S6

DMESG :- https://pastebin.com/ppNiHVFX

Try changing SELINUX to permissive default and upload fixed rom zip.

Are you sure that the file inside is fstAb.qcom and NOT fstUb.qcom

Don't lose hope.:fingers-crossed:
 
Last edited: