I changed my broken whyred screen some months ago and xiaomi has done a great job. No hairdryer needed, no glued parts. The main difficulty was to open the case with a kind of credit card (I ended with a small screw). There are great tutorials on YouTube. Good luckHave bought new one now on ebay for 26,99 euro. Replace it costs nothing, will do it on my own, well to be honest will try it... But hey how hard could it be.
At the moment i am happy to use (since a long time) good old mido again, forgotten how nice the phone was.
But even if i've repaired the whyred, it will be my "dev phone" for some times. Need an working phone, as you know, if i am working on updates my whyred is shut off for few hours with testing stuff, flashing or solve bootloop. In meantime if my work or family try to call me, can not answer them and this is an no go at the moment.
This are just good news for all of you, means more time to test everything out, play with oreo and pie bootloader for both kernel versions, fixing bugs could be done now faster and so on.
We will see how the things goes on, hopefully everything goes well and we can start the game again very soon.
@sgspluss, if I could make a request: please don't go the Pie direction. Please, let's have one solid and up to date Oreo ROM for the whyred. I'm on Bootleggers Oreo and love the real Xposed and the general stability that Congress with Oreo. Only issue is that it's not being updated with the latest security patches. So, give us total control of our devices!!
Sorry wrong thread... this is LOS thread... for havoc features go to havoc thread... LOS is PURE LOS without extra features...+ 1
Havoc features + Oreo stability + security patches, that would be the party
Yes.It seems to me these are basically security updates (no other features/fixes) is that right?
Most likely no.Would I have problems dirty flashing the latest unofficial over this?
It's offtopic here, but I highly recommend this version by xenius9One last question about what GCAM you guys are using, and what you might suggest.
I had problems with similar migration
I was sharing my GCAM in this thread several pages backwhat GCAM you guys are using
Was it the we transfer link? If so, it expired...I had problems with similar migration
so I would recommend to backup everything (twice!) and only then try to dityflash
I was sharing my GCAM in this thread several pages back
[B]lineage-15.1-20190310-UNOFFICIAL-whyred.zip[/B] Build with clang 9 and sdclang Update vendor security patch to 2019-03-01 Revert some unnecessary patches Sync with latest basickernel sources Sync with latest LineageOS sources Some other device and kernel stuff [B]lineage-15.1-20190224-UNOFFICIAL-whyred.zip[/B] Fix camera bug Sync with latest basickernel sources Sync with latest LineageOS sources Some other device and kernel stuff [B]lineage-15.1-20190219-UNOFFICIAL-whyred.zip[/B] Build with clang 8 and sdclang Update default density to 420 Fix 2nd CPU detection Sync with latest basickernel sources Sync with latest LineageOS sources Some other device and kernel stuff [B]lineage-15.1-20190113-UNOFFICIAL-whyred.zip[/B] Update vendor security patch to 2019-01-01 Sync with latest basickernel sources Sync with latest LineageOS sources Some other device and kernel stuff [B]lineage-15.1-20181209-UNOFFICIAL-whyred.zip[/B] Initial release