+1 ^Yes but only if someone ports it for the desire 816
Multirom will make it easier if someone wants to give it a try.
+1 ^Yes but only if someone ports it for the desire 816
Unfortunately no one is there to port+1 ^
Multirom will make it easier if someone wants to give it a try.
we get it lineage 15 for desire 816 or no?+1 ^
Multirom will make it easier if someone wants to give it a try.
Maybe, think the thing stopping boot was a kernel config issue with not having hwbinder turned on. Figured that out thanks to my evo3d, which does boot android 8 now.we get it lineage 15 for desire 816 or no?
ok. for what RR remix 5.8 not make for this phone ? RR remix beauty rom on android 7.1.x Will it base on the lineage os??Maybe, think the thing stopping boot was a kernel config issue with not having hwbinder turned on. Figured that out thanks to my evo3d, which does boot android 8 now.
Since I'm working with evervolv tree on my Iimited hard drive space, if anything I'll try to get EV Oreo on this device.
Not sure, not currently in process.
No the 8.0 rom will be based on LOS 15ok. for what RR remix 5.8 not make for this phone ? RR remix beauty rom on android 7.1.x Will it base on the lineage os??
Right now with limited hard drive space, if I build 8 for the a5 soon, it'll be evervolv. That's what my evo 3d likes, so it's what I've got synced at the moment.No the 8.0 rom will be based on LOS 15
check outok. for what RR remix 5.8 not make for this phone ? RR remix beauty rom on android 7.1.x Will it base on the lineage os??
Interesting. What version of twrp are you using again? And can you install it again, and grab me the recovery.log?Just like last version, boots right to bootloader.
3.0.2Interesting. What version of twrp are you using again? And can you install it again, and grab me the recovery.log?
advanced menu, copy log to sdcard3.0.2
Where/how so I get recovery.log?
It does throw a couple errors during install that 'log' is an unknown command though.
Won't likely get a chance until late tonight, but will do when I can.advanced menu, copy log to sdcard
checking the kernel log box and uploading that one too wouldn't hurt either.
Here ya go.advanced menu, copy log to sdcard
checking the kernel log box and uploading that one too wouldn't hurt either.
Main thing I see to try is flash without supersu and see if it boots.Here ya go.
Before, I was flashing lineage, Super SU, and gapps. In that order, in the select multiples in one flash mode.Main thing I see to try is flash without supersu and see if it boots.
Try rom only, no supersu or gapps.Before, I was flashing lineage, Super SU, and gapps. In that order, in the select multiples in one flash mode.
Tried with taking out Super SU, and the gapps install (through aroma) would crash. Installed Lineage and gApps in two separate flashes, and it seemed to work. But, still the booting to boatloader. Forgot to grab a log this time.
Try rom only, no supersu or gapps.
If it goes to bootloader, select recovery
Advanced-terminal
cat /proc/last_kmsg > /sdcard/kmsg.txt
Let me see the kernel log from when it crashes and maybe I can figure out more. You've got the same model and firmware as my phone.
Last time I saw this was from a dead battery that wouldn't take a charge. The ROM bails out during boot if it thinks the battery is dead.Same result doing just rom. Possibly worth noting, it boots to fastboot mode of bootloader.
Apparently I can't upload the files from mobile. I'll attach them when I'm back home.
Battery seems to be just fine. No issues with stock, nor your CM13 rom.Last time I saw this was from a dead battery that wouldn't take a charge. The ROM bails out during boot if it thinks the battery is dead.