Database Info

TWRP 2.7 for HTC Desire S

Hi. As you propably know, there is no TWRP 2.7 for saga. This is why:
Saga would need a number of updates in order to make it work with 4.4 Kit Kat ROMs. 4.4 ROM support really doesn't depend on the recovery itself. The kernel and other parts of the ramdisk have to support SELinux contexts in order for the set_metadata functions to work. I don't have a saga myself and at this point I have no plans to continue to support the device. I've been building saga in a CM7 / gingerbread tree which doesn't support the things needed for SELinux. The device would need to be compiled with an updated kernel in at least a 4.1 and preferably a 4.3 or 4.4 tree to support installing Kit Kat ROMs.
I plan to drop official support for any device that I've been building in ICS or Gingerbread trees which includes saga. If people want to see continued support for those devices, then hopefully developers for those devices will step up and build TWRP themselves and maybe offer their updated device files to us so that we can extend official support.
Click to expand...
Click to collapse
So basically we need developers who would like to help with that. I'm not that techy to understand what the problem is but I would like you to tell me and help.
BTW! Why our device is not available in DevDB! How do we change that?

Hm. I might take a shot at this. Though I personally prefer 4ext

devil-kin said:
Hm. I might take a shot at this. Though I personally prefer 4ext
Click to expand...
Click to collapse
It would be really splendid thing to do sir

Got it to build, just not to boot. I guess a black screen is no use to anyone
Will fiddle some more with it.

devil-kin said:
Got it to build, just not to boot. I guess a black screen is no use to anyone
Will fiddle some more with it.
Click to expand...
Click to collapse
That's great! It would be even better if you could somehow share some of your work here so maybe someone else could take a look (i don't know if it's possible. But you use github right?) I would love to add this project to DevDB but it seems that our phone is not there and i don't know how to add it.

My github repos are at https://github.com/jdeluyck - I haven't uploaded anything yet save for the changes to the repo file to pull in TWRP.

Here ya go, first build of TWRP 2.7.0.0 for Desire S, which seems to work
Please test and let me know

PERFECT!
devil-kin said:
Here ya go, first build of TWRP 2.7.0.0 for Desire S, which seems to work
Please test and let me know
Click to expand...
Click to collapse
I flashed it, I backed up my rom, I wiped, I flashed my rom clean, it booted, I went to recovery and I restored my rom. Everything went perfect, no problems whatsoever! Now there are 2 questions left to ask.
1. May I update TWRP for saga developement thread and attach this build?
2. Would you be willing to offer updated device files to TWRP team? From my observation most people download TWRP drom official website and it would be great if 2.7 would make an appearance there.
Anyway great work devil-kin :highfive: Personally I see TWRP as the best recovery and I'm on it from 2.2. Seeing it still working in its latest iteration on my beloved DS makes little tears appear in the corners of my eyes. I absolutely love this phone for it's size, specs, build quality and weird survability (many screen to sidewalk encounters and no broken glass Only praiseworthy scars). LONG LIVE DS! <3

VnnAmed said:
1. May I update TWRP for saga developement thread and attach this build?
Click to expand...
Click to collapse
Sure. I'm even willing to offer up new updates as long as I got a working CM tree to base it off.
VnnAmed said:
2. Would you be willing to offer updated device files to TWRP team? From my observation most people download TWRP drom official website and it would be great if 2.7 would make an appearance there.
Click to expand...
Click to collapse
Sure - the device files can be found at https://github.com/jdeluyck/android_device_htc_saga
Do I have to send them to anyone specific?

devil-kin said:
Sure. I'm even willing to offer up new updates as long as I got a working CM tree to base it off.
Sure - the device files can be found at https://github.com/jdeluyck/android_device_htc_saga
Do I have to send them to anyone specific?
Click to expand...
Click to collapse
Thank you very much If you could, i would like you to PM Dees_Troy and tell him that you have succesfully compiled 2.7 for saga, so if he has some more technical questions you can answer them I'm updating TWRP for saga thread right away

[FreeXperia Project] AOSP Android 5.1.x

Hi all,
We are starting today daily AOSP builds for all 2014 Sony devices so that you can enjoy a NEXUS like experience
Thanks
SONY for publishing AOSP base gits
All AOSP developers and testers
Sources
https://github.com/fxpdev
Download
http://fxpblog.co/

howto flash
download Android SDK
http://developer.android.com/sdk/index.html#Other
in adt-bundle-windows-x86_64-xxxxxxxx/sdk/platform-tools folder you have the required files
copy the following files in same folder where your AOSP image files are
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
disconnect device, press power and enjoy!

What an excellent Xmas gift from the fxp team. Will try later today, thanks
???

For the newbies:
You don't need the entire SDK. Just download a small ADB and Fastboot package from XDA, it'll make your life much easier.
Builds are building and/or uploading, will be available on: http://fxpblog.co/aosp/aosp-5-0/

Bootloader locked or unlocked only?

lirondeespaña said:
Bootloader locked or unlocked only?
Click to expand...
Click to collapse
I'll be quick here:
Until root for a locked bootloader has been found for the Z3 series, no ROM can be flashed.
And even after (or if) you get a recovery and root working on a phone with a locked bootloader, there's still something you have to consider: you cannot flash boot images others than completely stock ones onto a device with a locked bootloader.
This ROM's functionality is completely different than that of any stock ROM, meaning it requires its own boot image (so, one that is not stock).

Is there a list of what doesn't work?

Sean09 said:
Is there a list of what doesn't work?
Click to expand...
Click to collapse
There are no builds yet so nobody can report back, but camera is said to be broken right now (as with any other AOSP ROM).

Maybe no builds today, they should announce this after at least one build is uploaded.

jsscx said:
Maybe no builds today, they should announce this after at least one build is uploaded.
Click to expand...
Click to collapse
That would have made sense.
Effort is underway nevertheless.
Be interested to see how long it takes to achieve Daily Driver status. I suspect that's far away... Be surprised if DD aosp for z3c arrives before the z4c hits shelves.
Anyway thanks for working on the z3c. Look forward to peoples experiences with this.

Lol...trust in them,they are nearly the only ones who work a lot on our device.And I just couldn't keep patience,z3c is not popular ,which causes it so slow to see any booting builds on it
edit:
finally found it,http://uploaded.net/f/dv4mt9
sry for previous words.
will test
edit2:
Flashed.
1.no modem band,while wifi works
2.nfc dosen't work
3.no sound,no camera
There may be more issues,but these ones make it not a daily drive...
but at least it boots,and works smoothly!Thank you.

Nothing works? Sony has the code for them I don't understand why they're not releasing them.

jsscx said:
Lol...trust in them,they are nearly the only ones who work a lot on our device.And I just couldn't keep patience,z3c is not popular ,which causes it so slow to see any booting builds on it
edit:
finally found it,http://uploaded.net/f/dv4mt9
sry for previous words.
will test
edit2:
Flashed.
1.no modem band,while wifi works
2.nfc dosen't work
3.no sound,no camera
There may be more issues,but these ones make it not a daily drive...
but at least it boots,and works smoothly!Thank you.
Click to expand...
Click to collapse
Thanks for posting your exoerinece for others to know what's what.
Given this is the first build.... We can only expect improvements which is a good thing. Now they have the build trees and nightlies in order. So let's hope for good progress to follow.
Either way this is good news.. We all have itchy feet for aosp, but at least the devs are now beginning to make strides. So thanks to them for that alone.

There's a 29/12 build. I wonder if it's anything new or just a daily build.
Also, @freexperia what are the sources you're using? I tried looking through your GitHub account but didn't find an aries device tree -- or are you just using the sonyxperiadev branches?
EDIT: Would you guys mind if I mirrored a build every once in a while? DepositFiles and Uploaded cap their download speeds at 50kB/s, way below what most of the planet has.
EDIT2: Here's the mirror I made (hope it's alright with you guys). Took me over 2 hours to get 300MB of data downloaded lol don't want anyone else to feel my pain.https://drive.google.com/open?id=0BzcBVe17cfU-eFp1WnZ3VDRtbUE
I'll be compressing everything I upload with LZMA/LZMA2 and at least a 256MB dictionary -- I'd advise you to have at least 300MB of RAM free when extracting these archives.
Anything RIL-related isn't working (at least not as I can see) -- I have a logcat attached of me fooling around, opening a few apps and such. Perhaps it'll help somebody.

hi
we use sony ones
mirroring is useless since new build comes every day
br
someone755 said:
There's a 29/12 build. I wonder if it's anything new or just a daily build.
Also, @freexperia what are the sources you're using? I tried looking through your GitHub account but didn't find an aries device tree -- or are you just using the sonyxperiadev branches?
EDIT: Would you guys mind if I mirrored a build every once in a while? DepositFiles and Uploaded cap their download speeds at 50kB/s, way below what most of the planet has.
EDIT2: Here's the mirror I made (hope it's alright with you guys). Took me over 2 hours to get 300MB of data downloaded lol don't want anyone else to feel my pain.https://drive.google.com/open?id=0BzcBVe17cfU-eFp1WnZ3VDRtbUE
I'll be compressing everything I upload with LZMA/LZMA2 and at least a 256MB dictionary -- I'd advise you to have at least 300MB of RAM free when extracting these archives.
Anything RIL-related isn't working (at least not as I can see) -- I have a logcat attached of me fooling around, opening a few apps and such. Perhaps it'll help somebody.
Click to expand...
Click to collapse

freexperia said:
hi
we use sony ones
mirroring is useless since new build comes every day
br
Click to expand...
Click to collapse
Thanks for that!
But does each build improve on the previous one? A lot of the daily builds are in essence just copies of the older builds with the only difference being the time at which they were built. At least that's the situation with daily CM builds for this and some other devices.

someone755 said:
Thanks for that!
But does each build improve on the previous one? A lot of the daily builds are in essence just copies of the older builds with the only difference being the time at which they were built. At least that's the situation with daily CM builds for this and some other devices.
Click to expand...
Click to collapse
Dailies are a development tool, not a consumer tool. They are built with what is in the repo's at that time, every day.
If you want builds that are consumer focused with constant improvements over previous you should only flash release builds. Not only will dailies not always be better then the previous, its very likely that they will be worse at time.

jug6ernaut said:
Dailies are a development tool, not a consumer tool. They are built with what is in the repo's at that time, every day.
If you want builds that are consumer focused with constant improvements over previous you should only flash release builds. Not only will dailies not always be better then the previous, its very likely that they will be worse at time.
Click to expand...
Click to collapse
I am aware of that, but I was merely pointing out that not every build brings changes as many builds' only difference than the rest is the date on which it was built -- often, the repo stays the same for several days.
I am in no way blaming them or requesting anything from them, just wanted to point out why I believe mirrors aren't pointless.

Is there a changelog for this rom guys? or am I looking in the wrong place. Cheers

someone755 said:
I am aware of that, but I was merely pointing out that not every build brings changes as many builds' only difference than the rest is the date on which it was built -- often, the repo stays the same for several days.
I am in no way blaming them or requesting anything from them, just wanted to point out why I believe mirrors aren't pointless.
Click to expand...
Click to collapse
Maybe what we need is changelog

Temasek unofficial cm-12.1 builds

This thread is for updates of temasek cm12.1 built by myself. I will be building for hlte and hltespr.
Temasek made this all possible and it is all his work I am just taking the time to build and upload.
V19.3+ root removed, you will need to flash SuperSU zip to achieve root.
Downloads:
Hlte or Hlte on my BasketBuild
Hltespr or Hltespr on my BasketBuild
Credits: @temasek
XDA:DevDB Information
Temasek cm-12.1 unofficial cyanogenmod, ROM for the Samsung Galaxy Note 3
Contributors
trader418, Temasek
Source Code: https://github.com/temasek/
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: Cyanogenmod
Version Information
Status: Beta
Created 2016-03-26
Last Updated 2016-03-26

Thanks for keeping support for the Note 3 alive.

Great, good to see 12.1 back alive. Anything I can do to help, just say so.

Thanks again! Always willing to help however I can.
BTW, really good job on creating the thread using just your phone! I've seen FAR worse.

Buslova said:
Thanks again! Always willing to help however I can.
BTW, really good job on creating the thread using just your phone! I've seen FAR worse.
Click to expand...
Click to collapse
Haha thank you, I try my best
Glad to see all of you guys showing support. If I ever don't see temasek updated the version and any of you do just post here and I'll build, however I think most of the time I should be okay. I'm going to set up a straw poll in the include root vs not include. I also could start to use the ota app if you guys really would like that

Straw poll whether to include root in the build here http://strawpoll.me/7191529

trader418 said:
Haha thank you, I try my best
Glad to see all of you guys showing support. If I ever don't see temasek updated the version and any of you do just post here and I'll build, however I think most of the time I should be okay. I'm going to set up a straw poll in the include root vs not include. I also could start to use the ota app if you guys really would like that
Click to expand...
Click to collapse
I will always use root however I understand some people's need for it to be rootless and well, let's be honest, it ain't hard to flash supersu right after flashing the rom. lol.
OTA is a nice lazy option for the USER but I've gathered from past posts in other threads that it's not always so easy for the dev since the OTA app is maintained/owned by another dev and sometimes has issues. Again, we're talking about a community here who is flashing custom roms on their devices. Manually downloading and flashing shouldn't be a major issue.
Having said all that, if i were to vote I'd say:
Built-in root: No
OTA: Yes (if it's not a headache)

Buslova said:
I will always use root however I understand some people's need for it to be rootless and well, let's be honest, it ain't hard to flash supersu right after flashing the rom. lol.
OTA is a nice lazy option for the USER but I've gathered from past posts in other threads that it's not always so easy for the dev since the OTA app is maintained/owned by another dev and sometimes has issues. Again, we're talking about a community here who is flashing custom roms on their devices. Manually downloading and flashing shouldn't be a major issue.
Having said all that, if i were to vote I'd say:
Built-in root: No
OTA: Yes (if it's not a headache)
Click to expand...
Click to collapse
Ota isn't too bad, I'll probably use it soon tbh, but I won't promise anything

hey guys, I have been having trouble with tema's cm 13 builds so i decided to give 19.1 a shot. Unfortunately, I haven't had any luck with the rom. The rom just boot loops after every installation. I have tried with gapps aroma and pico with different wipes with no luck. continues to bootloop as soon as I reboot and i never get into the rom. I am back on tema's for now but would love to switch to 19.1 if I could get some help. Sorry for being a noob, Im probably messing something up somewhere and I thank you for your help in advance!

redfuryjr55 said:
hey guys, I have been having trouble with tema's cm 13 builds so i decided to give 19.1 a shot. Unfortunately, I haven't had any luck with the rom. The rom just boot loops after every installation. I have tried with gapps aroma and pico with different wipes with no luck. continues to bootloop as soon as I reboot and i never get into the rom. I am back on tema's for now but would love to switch to 19.1 if I could get some help. Sorry for being a noob, Im probably messing something up somewhere and I thank you for your help in advance!
Click to expand...
Click to collapse
Start with which device you have

trader418 said:
Start with which device you have
Click to expand...
Click to collapse
haha sorry! htlespr!

redfuryjr55 said:
haha sorry! htlespr!
Click to expand...
Click to collapse
I'm not sure mate, has anyone else got any suggestions?
There has been reports of multiple wipes and reboots and then flashing the ROM helps but I cannot say it will help

trader418 said:
I'm not sure mate, has anyone else got any suggestions?
There has been reports of multiple wipes and reboots and then flashing the ROM helps but I cannot say it will help
Click to expand...
Click to collapse
hmmm.. well I managed to get booted by installing temasek's last build (12.9 i think, the one from jan) along with his kernel. It booted fine and made it into setup. I then rebooted to recovery and dirty flashed you 19.1. Got bootlooped and said fk it and re-flashed the kernel and got into 19.1! Now that is great and all, but super weird/inconsistent. Also, once I got everything set up I could not turn on wifi or bluetooth; is this a known issue with a fix? Also, are there recommended installation instructions or is there a recommended kernel for you build? Thanks in advance for your help and patience with my noobness! Again I am on htlespr!

redfuryjr55 said:
hmmm.. well I managed to get booted by installing temasek's last build (12.9 i think, the one from jan) along with his kernel. It booted fine and made it into setup. I then rebooted to recovery and dirty flashed you 19.1. Got bootlooped and said fk it and re-flashed the kernel and got into 19.1! Now that is great and all, but super weird/inconsistent. Also, once I got everything set up I could not turn on wifi or bluetooth; is this a known issue with a fix? Also, are there recommended installation instructions or is there a recommended kernel for you build? Thanks in advance for your help and patience with my noobness! Again I am on htlespr!
Click to expand...
Click to collapse
All I know is that all my hlte builds are tested with a clean wipe and then a flash and reboot. I have no problems. I am using temaseks device tree so the only difference between his and my build should technically be root and ota app. Other than that it should be identical

trader418 said:
All I know is that all my hlte builds are tested with a clean wipe and then a flash and reboot. I have no problems. I am using temaseks device tree so the only difference between his and my build should technically be root and ota app. Other than that it should be identical
Click to expand...
Click to collapse
I am using this as my daily Rom, the only problems I get are the weather widget doesn't update and it wont connect to the wifi in my local hospital, I am using build v19.0 build date 17th of march, even my s-pen works !
I will test this later and post back results

swukjay said:
I am using this as my daily Rom, the only problems I get are the weather widget doesn't update and it wont connect to the wifi in my local hospital, I am using build v19.0 build date 17th of march, even my s-pen works !
I will test this later and post back results
Click to expand...
Click to collapse
Either change weather provider to another or customize your location. Sometimes yahoo weather isn't working well.
As for WiFi, check your dev options.

redfuryjr55 said:
haha sorry! htlespr!
Click to expand...
Click to collapse
Just in case - have updated your Modem and Bootloader to the latest? All wireless related problems might be connected to it.

eseregin said:
Just in case - have updated your Modem and Bootloader to the latest? All wireless related problems might be connected to it.
Click to expand...
Click to collapse
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?

redfuryjr55 said:
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
Click to expand...
Click to collapse
Hmm, still no luck eh? I tried helping ya last night in the other thread. I'm also a hltespr user. I'm still running OH1 baseband however OK2 is the latest. Also, as I told you last night, I'm using an older version of TWRP recovery (ver. 2.8.7) however the latest is 3.0.0.
What baseband are YOU running? Go to settings, "About phone", and look for "Baseband version" and let us know. =)

redfuryjr55 said:
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
Click to expand...
Click to collapse
Sorry, I have different phone..
Might be the latest here
https://idlekernel.com/flash-tools/firmware/hltespr_SM-N900P/N900PVPUEOK2/
But I am far away from sure

Kernel source release?

HTC might need a gentle reminder about releasing kernel sources, none of the U series have been released yet, they are required for us to support SlimRoms/LineageOS/aosp/caf style ROMs.
I've tweeted at htcdev etc...
Nick.

Flinny said:
HTC might need a gentle reminder about releasing kernel sources, none of the U series have been released yet, they are required for us to support SlimRoms/LineageOS/aosp/caf style ROMs.
I've tweeted at htcdev etc...
Nick.
Click to expand...
Click to collapse
With you, just retweeted

Flinny said:
HTC might need a gentle reminder about releasing kernel sources, none of the U series have been released yet, they are required for us to support SlimRoms/LineageOS/aosp/caf style ROMs.
I've tweeted at htcdev etc...
Nick.
Click to expand...
Click to collapse
tbalden said:
With you, just retweeted
Click to expand...
Click to collapse
With you both. Also retweeted. Lets Hope for the best.
I didn´t even know HTC never released kernel source for U Ultra etc. I thought they had a good record releasing source code (well, sometimes a bit late but...)
One of my intentions when buying U11 was to create a kernel for the ocean after I took the trip to the Pixel XL and created my first kernel there.

tbalden said:
With you, just retweeted
Click to expand...
Click to collapse
Are you getting the U11?

flar2 said:
Are you getting the U11?
Click to expand...
Click to collapse
Yes, hopefully next week

I just noticed they added kernel source of u play.
Also a search category for android 7.1 appeared which is still empty. Previously highest was 7.0.
Fingers crossed it's for the 11.

At least TWRP is fully working without it on this device. So I need it less than you kernel/AOSP devs this time around .

I emailed htcdev and asked about all U series kernel source. They said it had been passed on. May just be coincidence though

@Flinny @tbalden @flar2 @Captain_Throwback
source is out
Let the fun begin

Freak07 said:
@Flinny @tbalden @flar2 source is out
Let the fun begin
Click to expand...
Click to collapse
Yeeeeew!!!

Heh they snuck that out in the few hours of sleep I had last night! Funny they released Vodafone UK source when they don't seem to be stocking the phone! I've been playing with building using the stock kernel. The biggest problem I'm having is actually restoring my stock backup afterwards. /Data either won't restore or when I do fully wipe it and get it to restore it won't accept my unlock code/pattern/fingerprint anymore.
Setting the phone up from scratch every time you test is a pita!

https://github.com/htc-msm8998/kernel_htc_msm8998

Is it relevant that there still no US unlocked & sprint variations kernel source?
Sent from my HTC U11 using XDA Labs

I expect they will come, but it looks like it's fully interchangeable currently, at least I've been running the europe unlocked boot.img on my EE UK single sim device without issue. I've just built it and it's running also.

Flinny said:
Heh they snuck that out in the few hours of sleep I had last night! Funny they released Vodafone UK source when they don't seem to be stocking the phone! I've been playing with building using the stock kernel. The biggest problem I'm having is actually restoring my stock backup afterwards. /Data either won't restore or when I do fully wipe it and get it to restore it won't accept my unlock code/pattern/fingerprint anymore.
Setting the phone up from scratch every time you test is a pita!
Click to expand...
Click to collapse
Ouch, that sounds bad. I'm not sure when I'll start hacking, my vacation is very close and by then I guess most features might be already done and ported for sense kernels.. tho the new soc may add some pain to the equation of simple patching

Bliss Rom Official

Anyone was aware about this ROM... Installed yesterday and as of now running smoothly... If anyone interested give a shot. Links are
Bliss ROM
boot.img

And no illustrations : không chắc::đảo mắtn)

Raj Pandiyan said:
Anyone was aware about this ROM... Installed yesterday and as of now running smoothly... If anyone interested give a shot. Links are
Bliss ROM
boot.img
Click to expand...
Click to collapse
Nice, who's building it?

Edmontonchef said:
Nice, who's building it?
Click to expand...
Click to collapse
Actually I was using their GSI on my previous device. I got notified from their blog regarding this... That's why shared...
Bliss Roms
Downloads

general question: what's the with move away from roms listing features or including screenshots these days? both blissroms and lineageOS have fancy websites with almost no details on what the roms offer and no screenshots. i get that they are free and owe me nothing but why on earth would i install any of them (and wipe my data) with no information on what i stand to gain?

c_tho said:
general question: what's the with move _away_ from roms listing features or including screenshots these days? both blissroms and lineageOS have fancy websites with almost no details on what the roms offer and no screenshots. i get that they are free and owe me nothing but why on earth would i install any of them (and wipe my data) with no information on what i stand to gain?
Click to expand...
Click to collapse
Exactly I was wondering about the same riddle... Even I came across while just surfing... There is no forum I can put this point up as the only discussion is through telegram and I'm least interested in that...

Raj Pandiyan said:
Exactly I was wondering about the same riddle... Even I came across while just surfing... There is no forum I can put this point up as the only discussion is through telegram and I'm least interested in that...
Click to expand...
Click to collapse
oh my goodness, telegram is an absolute nightmare, can you imagine trying to work out a list of rom features from a telegram channel? surely one of the worst places to get this kind of information.
anyway i don't like to complain, i'm sure the rom is very good, just a strange phenomenon i've been wondering about lately. i would have thought with stock android getting so much better over the years, rom devs would have had more reason to be more explicit about what their roms offer, rather than less. oh well.

New update guys!!!!!!!!
ROM
& same boot.img referred earlier....
This one is amazing..... June security patch...

c_tho said:
oh my goodness, telegram is an absolute nightmare, can you imagine trying to work out a list of rom features from a telegram channel? surely one of the worst places to get this kind of information.
anyway i don't like to complain, i'm sure the rom is very good, just a strange phenomenon i've been wondering about lately. i would have thought with stock android getting so much better over the years, rom devs would have had more reason to be more explicit about what their roms offer, rather than less. oh well.
Click to expand...
Click to collapse
Bliss Roms Blog
Bliss ROM Downloads
Cheers!!!!

edit: latest wont boot from clean flash... spinning boot logo ??
edit: previous version boots.. lets try update that..

badaas said:
edit: latest wont boot from clean flash... spinning boot logo ??
edit: previous version boots.. lets try update that..
Click to expand...
Click to collapse
Actually I downloaded the boot and used rom ( may release )... Got updated automatically... Working perfectly fine with no issues

boot doesnt work with june! can only install june via ota from may.....need new boot.img from payload.bin
June boot extracted:

Random reboots. Think it's location based as used to happen on my Xiaomi when going outside...
Still nags about update even though it's installed..
Auto brightness stopped working needs reboot.
But I do like the roms battery idle and usage, very good!

badaas said:
Random reboots. Think it's location based as used to happen on my Xiaomi when going outside...
Still nags about update even though it's installed..
Auto brightness stopped working needs reboot.
But I do like the roms battery idle and usage, very good!
Click to expand...
Click to collapse
I am using this ROM and as of now it's fine. Yes, there is some issue with auto brightness... Rest I hope it's sorted... It's smooth.... Battery optimization is also good...

Does it keep asking to update on reboot?

badaas said:
Does it keep asking to update on reboot?
Click to expand...
Click to collapse
No.... U update play store... that should fix that... Delete the ROM update that shows even after updating...

... Edit...

Same random reboot when going the shops. 2 different kernels, take phone out to check, soon as turn screen on, death.

badaas said:
Same random reboot when going the shops. 2 different kernels, take phone out to check, soon as turn screen on, death.
Click to expand...
Click to collapse
Pls post on official forum bro.... It's up now in ROMs forum XDA...