Related
This is simply a stock AOSP otapackage build using the preview binaries from here https://developers.google.com/android/nexus/blobs-preview
Considering that Android L is not released and these are preview blobs you should understand that this may not be considered perfect as in there may be bugs (although i have not seen any)
Use my GAPPS otherwise **** will not work
You will lose twrp after installing this so you will need to reapply that afterwords… follow these instructions to a tee to get this working
I take no responsibility if you destroy your system , proceed at your own risk bla bla bla
Install… FOLLOW EXACTLY... I will know when you deviate and will not respond to messages for help afterwords
Copy gapps and ota to internal sdcard
Boot to twrp
Wipe data and system and cache via advanced (this must be done)
Install aosp_manta-ota-eng.kejar31.zip
Back to main menu
Select mount then unselect system (uncheck it)
Back to main menu
Install gapps-lp-20141106-signed.zip
reboot
Download
ROM - https://mega.co.nz/#!VZpgHTTa!_WYFnfmSm5aQAE3DyZ35x2PaRIzM-2U_nigqb6hlMEw
GAPPS - https://mega.co.nz/#!JdYCnSxZ!fn82nMs3mA0VdDBTYuguT9OXHjQtt7P9jnZUyndrtZA
if someone wants to host mirrors let me know.
Does this have the Wifi fix in it? or has Google not published that yet?
Can't wait to install this and try it. I was going to wait it out for the official release but I've broke I have to try it.
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
ChaosMinionX said:
Does this have the Wifi fix in it? or has Google not published that yet?
Click to expand...
Click to collapse
I don't think it will be as Google haven't released the version with the patch yet as that will be the OTA or factory image versions.
ChaosMinionX said:
Does this have the Wifi fix in it? or has Google not published that yet?
Click to expand...
Click to collapse
most likely not have not tested for any wifi bugs atm
Thank you I'm really excited about it. But I have a question. Can I have use my flash drives in this ROM without stickmount?
ROM
So is this a full-fledged ROM that I can install after wiping any ROM, or do I have to flash back to stock android 4.4.4 and then flash this??
I seem to be unable to install on my Nexus 10. I've followed the stages, but when I get to flashing the AOSP rom it stays on it forever!
I've updated my TWRP to v2.8.1.0 but it does the same thing.
Sorted the problem I think, some how the download I had on my Nexus was not a happy one haha. just on the boot logo now :3
Thank you, booted up and running. One question, I couldn't install Google+. It cannot be found on Play Store and installing from APK doesn't work neither.
Great work, thanks. Flashed about an hour ago, flawless so far!
seems my internal storage is not working ,I am not able to see any storage area, it gives an error. Might be a bad flash.
gabegom said:
So is this a full-fledged ROM that I can install after wiping any ROM, or do I have to flash back to stock android 4.4.4 and then flash this??
Click to expand...
Click to collapse
Same question here. Can we flash after any ROM or do we have to flash stock .imgs first then this?
Is anyone having problems with Wifi? I have flashed this twice and I cannot get Wifi to connect. It sees networks but won't connect to any of them.
ChaosMinionX said:
seems my internal storage is not working ,I am not able to see any storage area, it gives an error. Might be a bad flash.
Click to expand...
Click to collapse
internal storage is working here
Followed all the steps to the T, now it just boots up to the android logo and shuts down?
Anybody have the same problem?
chowynatt said:
Followed all the steps to the T, now it just boots up to the android logo and shuts down?
Anybody have the same problem?
Click to expand...
Click to collapse
For me it took a lot of time booting up, I was about to power it off and reinstall, but eventually it show the android logo and now is running well.
tavocabe said:
For me it took a lot of time booting up, I was about to power it off and reinstall, but eventually it show the android logo and now is running well.
Click to expand...
Click to collapse
Did you manage to install Google+?
kejar31 said:
This is simply a stock AOSP otapackage build using the preview binaries from here https://developers.google.com/android/nexus/blobs-preview
Considering that Android L is not released and these are preview blobs you should understand that this may not be considered perfect as in there may be bugs (although i have not seen any)
Use my GAPPS otherwise **** will not work
You will lose twrp after installing this so you will need to reapply that afterwords… follow these instructions to a tee to get this working
I take no responsibility if you destroy your system , proceed at your own risk bla bla bla
Install… FOLLOW EXACTLY... I will know when you deviate and will not respond to messages for help afterwords
Copy gapps and ota to internal sdcard
Boot to twrp
Wipe data and system and cache via advanced (this must be done)
Install aosp_manta-ota-eng.kejar31.zip
Back to main menu
Select mount then unselect system (uncheck it)
Back to main menu
Install gapps-lp-20141106-signed.zip
reboot
Download
ROM - https://mega.co.nz/#!VZpgHTTa!_WYFnfmSm5aQAE3DyZ35x2PaRIzM-2U_nigqb6hlMEw
GAPPS - https://mega.co.nz/#!lVYHAAjI!-478q0a5v6QAL9-6bDNzo7utJ1AXZD539CpTP6R63w8
if someone wants to host mirrors let me know.
Click to expand...
Click to collapse
So far so good! I'm in the setup... it's taking a long time checking my wifi connection.
edit:changing to 5ghz did the trick
edit2: after passing setup, changing back to 2.4ghz works just fine.
tavocabe said:
For me it took a lot of time booting up, I was about to power it off and reinstall, but eventually it show the android logo and now is running well.
Click to expand...
Click to collapse
Yeah all working now, took forever to boot, went black a few times and then started working.
Now the $64,000 Question: will it root?
because I've had my fun with it. And without root, I can't keep it. I doubt it can be, but I have to hope.
Flashed yesterday. My experience was as follow:
1) Dirty flash from PA, system erase command did t seem to work. After flashing it booted up all apps were there, 4.4 gapps were force closing.
2) Twrp advance factory reset and erase. normal flash afterwards with gapps 5.0. Setup wizard crash. Couldn't get past that error.
3) Factory 4.4 image. Complete erase, and flash to L, boot up and then TWRP and gapps flash. Tablet booted correctly and works since then.
Regarding the WiFi battery drain bug:
No issue here. Battery drain when idle is a flat line. No misc group with excessive battery is listed in the battery stats.
Further more performance is great, basic apps seem to work correctly. Haven't gotten much into detail.
Regarding the G+ question. It works fine.
Dear every one, I really like this ROM, but how to flash this ROM?
I try to flash to use fastboot and TWRP with IMG flashIng, but after flashing them, the mobile phone will jump to Bootloader page, but when I use the same method in other ROM(like PHH and RR6.1.0)it works. My last ROM version is MIUI10-8.7.12 Globle.
details here
1.formate data
2.4 wipe
3.install and choose img file with system type.
4.wipe again
5.reboot
THanks.
If supported you can flash the image in bootloader mode.
Type in this command.
fastboot flash system nameofimage.img and reboot.
PE just wont boot for some devices. There is a whole different thread about fixing this, it may be for Huawei, but it could work for more devices. Apparently flashing a patched boot from Magisk works.
flash magisk 16.6 it will boot. but then you will have to also format data(not wipe) in twrp to disable encryption.
It finally works!
The steps I took to get it working are the following:
1. Boot to TWRP (I used version 3.2.0.1/v5 from here: https://forum.xda-developers.com/xiaomi-mi-mix-2s/development/recovery-twrp-mix-2s-t3790922
2. Format data, confirm with "yes"
3. Wipe data, system, cache, dalvik
4. Install latest Pixel Experince.img (GSI) from the thread on XDA
5. Flash magisk 16.6 directly after the image. Didn't do a reboot before flashing magisk
6. Rebooted system
7. Got many warnings that the device is not Google certified. Search for this terms and you'll find a tutorial to get rid of the messages. Simply downloaded the "device+ID.apk" from XDA and installed it. Wrote down the GSF ID and visited the mentioned page and got my device registered. Warnings are gone, play services are running perfectly fine. Here's the link to the article https://www.google.at/amp/s/www.xda...fix-device-not-certified-by-google-error/amp/
8. Rebooted system again
Works like a charm. Got everything set up to my needs. Only thing I had to configure was the navigation bar as it was hidden from the beginning. Just opened settings and toggled the navigation bar settings from one setting to the other and it appeared.
Will definitely be my daily driver from no on. Finally we can have a "Pixel" for half the price!
I'm so happy right now. Thanks to all the people who supported me and answered all my questions!
kleinholzinferno said:
It finally works!
The steps I took to get it working are the following:
1. Boot to TWRP (I'm using version 3.2.0.1)
2. Format data, confirm with "yes"
3. Wipe data, system, cache, dalvik
4. Install latest Pixel Experince.img (GSI) from the thread on XDA
5. Flash magisk 16.6 directly after the image. Didn't do a reboot before flashing magisk
6. Rebooted system
7. Got many warnings that the device is not Google certified. Search for this terms and you'll find a tutorial to get rid of the messages. Simply downloaded the "device+ID.apk" from XDA and installed it. Wrote down the GSF ID and visited the mentioned page and got my device registered. Warnings are gone, play services are running perfectly fine. Here's the link to the article https://www.google.at/amp/s/www.xda...fix-device-not-certified-by-google-error/amp/
9. Rebooted system again and it works like a charm. Got everything set up to my needs. Only thing I had to configure was the navigation bar as it was hidden from the beginning. Just opened settings and toggled the navigation bar settings from one setting to the other and it appeared.
Will definitely be my daily driver from no on. Finally we can have a "Pixel" for half the price!
I'm so happy right now. Thanks to all the people who supported me and answered all my questions!
Click to expand...
Click to collapse
didnt worked for me rebooted into recovery i used 3.2.1-0 can you link me yours?
From this thread
https://forum.xda-developers.com/xiaomi-mi-mix-2s/development/recovery-twrp-mix-2s-t3790922
I used version 5 because in version 6 usb MTP mode is disabled.
Which rom did you come from? I came from a working official resurrection remix gsi. But I don't know if this matters as you wipe everything from the device.
Have you ever had a treble gsi running on your device? I remember installing RR after the android P beta from Xiaomi failed. I then started from scratch and installed the latest official global stable miui rom for the MiMix2S from Xiaomi without magisk and all and went from there. Don't know why but this fixed the problem with the RR gsi.
Maybe theres a problem with older mods you have done. You could try and start from zero and get the device back into the original state.
Hope it works out for you! Let us know how it turned out. Could be anyone else has some more input for you.
I know it's frustrating to flash a rom that works for others and not on your device although you have the same as them and followed every step in the tutorial. I've been there so many times that I lost count but it's always the little things that cause problems. Take your time, read some more about this whole stuff. I had to read a lot to get into this topic. Maybe theres a nother method of flashing that works for you.
kleinholzinferno said:
From this thread
https://forum.xda-developers.com/xiaomi-mi-mix-2s/development/recovery-twrp-mix-2s-t3790922
I used version 5 because in version 6 usb MTP mode is disabled.
Which rom did you come from? I came from a working official resurrection remix gsi. But I don't know if this matters as you wipe everything from the device.
Have you ever had a treble gsi running on your device? I remember installing RR after the android P beta from Xiaomi failed. I then started from scratch and installed the latest official global stable miui rom for the MiMix2S from Xiaomi without magisk and all and went from there. Don't know why but this fixed the problem with the RR gsi.
Maybe theres a problem with older mods you have done. You could try and start from zero and get the device back into the original state.
Hope it works out for you! Let us know how it turned out. Could be anyone else has some more input for you.
I know it's frustrating to flash a rom that works for others and not on your device although you have the same as them and followed every step in the tutorial. I've been there so many times that I lost count but it's always the little things that cause problems. Take your time, read some more about this whole stuff. I had to read a lot to get into this topic. Maybe theres a nother method of flashing that works for you.
Click to expand...
Click to collapse
i started from 0 flashed in order global official miui rom after rr and after pixel experience all ok without strange messages
PITTAR said:
i started from 0 flashed in order global official miui rom after rr and after pixel experience all ok without strange messages
Click to expand...
Click to collapse
Very good, great it works for you now.
Enjoy the new phone! I have it running for a few days now and so far I love it! I'm never going back to miui again! Never!
Some things are not working at the moment like Bluetooth audio to car stereo. Although it shows the song playing with the title and the correct time on the car head unit I hear no sound. Hands free calls work without any problems.
In band ringing doesn't work so I don't hear my ringtone over the car stereo. I can activate this in developer options but it doesn't stay on and doesn't work. Nevermind, this isn't important.
Haven't found many other things that I need at the moment.
Great rom, hope it gets maintained in the future and there will be a device specific rom for the MiMix2S in the near future.
Hopefully Android P in fall/winter?
kleinholzinferno said:
It finally works!
The steps I took to get it working are the following:
1. Boot to TWRP (I'm using version 3.2.0.1/v5 from here: https://forum.xda-developers.com/xiaomi-mi-mix-2s/development/recovery-twrp-mix-2s-t3790922
2. Format data, confirm with "yes"
3. Wipe data, system, cache, dalvik
4. Install latest Pixel Experince.img (GSI) from the thread on XDA
5. Flash magisk 16.6 directly after the image. Didn't do a reboot before flashing magisk
6. Rebooted system
7. Got many warnings that the device is not Google certified. Search for this terms and you'll find a tutorial to get rid of the messages. Simply downloaded the "device+ID.apk" from XDA and installed it. Wrote down the GSF ID and visited the mentioned page and got my device registered. Warnings are gone, play services are running perfectly fine. Here's the link to the article https://www.google.at/amp/s/www.xda...fix-device-not-certified-by-google-error/amp/
8. Rebooted system again
Works like a charm. Got everything set up to my needs. Only thing I had to configure was the navigation bar as it was hidden from the beginning. Just opened settings and toggled the navigation bar settings from one setting to the other and it appeared.
Will definitely be my daily driver from no on. Finally we can have a "Pixel" for half the price!
I'm so happy right now. Thanks to all the people who supported me and answered all my questions!
Click to expand...
Click to collapse
Thanks for sharing so much...but I wanna know flashing Magisk 16.6 is significant or not? Why should I must flash that..caz I use bank App which is not allowed root device..Oh, I try to flash Omin ROM, but it can't get into the system..and Magisk16.6 can't be flashed in with error..
jayxiao171735 said:
Thanks for sharing so much...but I wanna know flashing Magisk 16.6 is significant or not? Why should I must flash that..caz I use bank App which is not allowed root device..
Click to expand...
Click to collapse
Magisk was mandatory for me because otherwise it ended up booting only to recovery.
I haven't tried what happens when you uninstall magisk after successfully setting up the device.
If you need to hide root use magisk hide, maybe that helps?
The below is a guide to installing GSI images on the Mi 8 Pro. I specifically have experience with the PixelExperience 9.0 (Unofficial) but have had other GSI ROMs booting and working. I hope this is useful for some.
GSI (Generic System Image) ROMS can be flashed to any Project Treble enabled device. These devices have either an A/B partition layout (these allow for seamless updating as the system can boot from A or B partition) or just an A only partition layout. The Mi 8 Pro is an arm64 a only device and support project treble ROMs. You can choose from suitable ROMs listed here and here.
The instructions given below are for Android Pie (9.0). The same basic setup can be used for Android Oreo (8.0, 8.1) ROMs, but the Mi 8 Pro should be flashed with the appropriate Xiaomi base ROM first before flashing any 8 based GSI ROM
As the ROM development for the Mi 8 Pro is basically dead, I decided to buy a OnePlus 6T and sell my Mi 8 Pro. However, due to having my new OnePlus 6T stolen, and due to a lack of funds to buy a new device, I have revived my Mi 8 Pro to try to get something other than MIUI working on it. I now have The PixelExperience (Unofficial) GSI ROM running very smoothly on my Mi 8 Pro.
As the PixelExperience team has stated they will be delivering GSI images again, if there are enough of us asking, we could get better support for things like the fingerprint sensor, for a more complete experience.
Some of the below steps may be unnecessary, but are there for a complete beginner's guide to doing this and getting the right results.
Working:
WiFi
Bluetooth (with APTX)
NFC (Including Google Pay)
RIL
Mobile data (LTE / HSPDA / 3G / EDGE)
GPS
Camera (with camera built in to ROM, as well as some GCAM implementations)
Video Camera (not working on GCAM implementations tested so far - only working on Camer built in to ROM)
Flashlight
Sound / Vibrations
Face Unlock
Hotspot
Not Working:
VoLTE (I have had it working, but unable to end phone calls and problems receiving SMS messages, so reverted)
Fingerprint (There is some support. The fingerprint area of the screen lights up when trying to enrol a new fingerprint. The screen dims when a finger is placed on the sensor, and a green light us emitted from the sensor area, but it does not register the fingerprint and this is not currently working.)
Notification LED
You Tell Me
How to install
Flash the latest Fastboot Global Stable Android PIE (9.0) ROM for the Mi 8 Pro. (eg. equuleus_global_images_V10.3.4.0.PECMIXM_20190712.0000.00_9.0_global_9a181f79c1.tgz) using the Xiaomi Tool.
Update: Use the latest MIUI system. The contents of the vendor partition are important. The most compatible vendor partition as of 2019-08-19 is from equuleus_global_V10.3.5.0.PECMIXM. You can download and flash that vendor independantly, if you have already set up your GSI image.
Reboot and finish basic MIUI setup.
Reboot to recovery.
[*]Format data (Wipe - Advanced - format data - confirm by typing yes)
DO NOT FORMAT DATA. Just perform a factory reset. Formatting data can cause issues and prevent booting.
Wipe Cache - Dalvik Cache and System
Reboot recovery
Use adb to push PixelExperience GSI image (img file extracted from download) and latest version of Magisk to root of SDCard. (Empty due to formatting data).
("adb push c:\path\system.img /sdcard/" and then "adb push c:\path\Magiskv19.3.apk /sdcard/")
Flash the image to system partition by taping INSTALL and then on the "Install Image" button (to toggle between flashing zip and img files). Do not reboot yet.
Flash magisk zip in the normal way (hit the same button as in previous step to show zip files to flash. (This is necessary to avoid bootloops)
Reboot, and enjoy.
You can now set up your "PixelExperience" device with your apps and settings, including registering a face for face unlock.
To pass cts validation for the safetynet and to allow service such as Google Pay to work
In Magisk, under settings - Find “Magisk Hide” and toggle the switch on
Magisk restarts. Go to Magisk Hide from the Magisk menu and ensure that...
Google Pay
Google Play
Google Play Services
Google Service Framework
Any Banking Apps
...are checked so that they cannot see Magisk (canont see phone as rooted).
Now go to downloads and install the SafetyPatch v3 module (created by hackintosh5).
Reboot.
Open settings - go to apps and notifications - and find the above apps to clear all data.
Enjoy your rooted safetynet compliant, as close to stock as possible Xiaomi Mi 8 Pro.
nice work thanks for this great notice, i will test PixelExperience, how work the face unlock? i use the finger print very much, all day, but not work i will use the facial unlock. Then i wanna know how work this.
thanks!!
axelgrox said:
nice work thanks for this great notice, i will test PixelExperience, how work the face unlock? i use the finger print very much, all day, but not work i will use the facial unlock. Then i wanna know how work this.
thanks!!
Click to expand...
Click to collapse
Face unlock works fine. I have it paired with Pick to wake phone - so when I pick it up it wakes up to allow face unlock.
However, be prepared for some investment of time (not for face unlock).... I am a bit stuck now and cannot reproduce the above to get this working. Sometimes the results are different depending on base ROM etc.
Share how you get on and anything you may need to do to get this working.
Thanks
Nice work, i will try it .
The mi8 pro 's fingerprint is so bad which can be ignored, and the face unlock is the mostly used, hahahah
thank you very much for your work
Hi, I am waiting to unlock bootloader. Need 148hrs. Will install this. Thanks for sharing.
Quick update: There are some issues with GSI ROMs and the Mi 8 Pro. SOe of these relate to the SIMcard settings - and selection of preferred SIM for data, calls etc.
My experience shows that the vendor image from equuleus_global_V10.3.5.0.PECMIXM fixes many of these. The vendor image from the original MIUI ROM is used with the GSI system image to make the whole Project treble stuff work. I advise flashing this latest vendor image for maximum compatibility.
Do you know what issues remain after flashing the latest vendor image?
Does the face unlock on Pixel Experience work with IR camera or front cam?
I tried installing this and it got stuck on the loading screen with the Google logo. I tried following your instructions and a few other ways and couldn't get it to work at all i'm also not able to root my phone at all. When ever I try rooting my phone just reboots to twrp until I reflash the ram or flash the magisk uninstaller.
Do you have any tips, tricks, or suggestions I might try?
Thanks!
eremeya said:
I tried installing this and it got stuck on the loading screen with the Google logo. I tried following your instructions and a few other ways and couldn't get it to work at all i'm also not able to root my phone at all. When ever I try rooting my phone just reboots to twrp until I reflash the ram or flash the magisk uninstaller.
Do you have any tips, tricks, or suggestions I might try?
Thanks!
Click to expand...
Click to collapse
Have experienced this on occasion also.
What GSI image have you tried? after my multiple efforts, I would recommend... in this order: Omni. HavocOS, Descendant(no future updates), PIxelExperience. I am hopeful about the PixelExperience team who have made an announcement that as of August they will no longer produce CAF versions of PixelExperience, and that they will maintain regular GSI builds also. PE official GSI - I am full of hope.
Anyway, back on topic: Try this.
Follow the instructions - a few precisions:
Use XiaoMiFlash to flash the equuleus_global_images_V10.3.4.0 as a base. You can update the vendor partition once you have GSI up and running, but don't let the MIUI update to 10.3.5. Ensure you define a PIN to make sure that data partition is encrypted. (everyone should use encryption nowadays, and besides, I have had bad experiences whn using a xiaomi eu or mi-globe ROM (unencrypted) as the base
Reboot and finish basic MIUI setup. - What I mean here is to let the ROM boot, don't have to sign in to Google or Mi, but get to the home screen after the initial setup.
Then reboot fastboot and flash TWRP 3.3.0. Search for TWRP-3.3.0-0504-XIAOMI8UD-CN-wzsx150.zip.
Boot to TWRP. Make sure that you are able to decrypt the data partition with the PIN you set earlier. If TWRP does not ask you for the passcode / PIN - something is wrong. Try again. ONce all is OK in TWRP, perform factory reset. (DO NOT FORMAT DATA for the aforementioned encryption reason).
adb push the img file.
adb push the Magisk 19.3 zip.
Flash both in TWRP
Reboot TWRP
Reboot system. If it appears to hang, after 5 minutes you can force restart with the power button. I have had the ROM boot OK after second boot only?
Pretty sure that if you strictly follow the above you should get a working GSI image on Mi 8 Pro. Let me know...
It's a bit flaky to set up, but once set up, apart from fingerprint sensor not working, very stable and lovely to have the stock ish android system on a MIUI phone!
Be careful with preferred network type for mobile network as some selections have messed up incoming SMS messages for me... a dealbreaker.
What happens when you flash Magisk? What does TWRP say? Have you tried flashing Magisk, rebooting TWRP, and flahing Magisk again? It may be a TWRP version issue?
Thanks for your reply!
The version of twrp you mention is what I have used. I have not tried installing then rebooting to twrp so I try that.
When flashing magisk it usually flashes fine (I have had a couple times where it just throws an error) then when I reboot the phone will boot past the Mi logo the the Android boot logo then after 10-15 sec. it just reboots to twrp.
I was finally able to get the twrp to stick across boots by flashing twrp, signing boot image, removing twrp then reboot to Miui.
Do I need to adb push the GSI image or should it be fine to install from a USB drive?
The SMS issue isn't really a big deal for me as I use Google Fi routed through hangouts for one sim and a local sim where I'm living for mostly data and a few phone calls for the second one
Thanks so much for this post. I was completely oblivious to the fact that the Mi 8 Pro would actually be different to the Mi 8 when it comes to custom roms. When I decided on my next phone, I read the positive reviews and saw enough Mi 8 roms to be willing to make a switch to Xiaomi. Until I read your post I was close to despairing as I don't want a Xiaomi rom on my phone for various reasons (among them is the fact that I don't trust them and the way they have decided to collect user data).
I've tried to follow your guide in every step (I've also flashed the updated vendor.img), but unfortunately I have not been able to install the Pixel Experience rom on my device. I do see the boot animation but it never stops, I'm forever stuck with the Google-G and the progress bar below it. Has anyone else managed to install the Pixel Experience rom on the Mi 8 Pro? If yes, did you follow the guide here or did you do something else?
Also, in your initial post you write that we should wipe the system in TWRP but as far as I can tell GSI roms need you to wipe data, cache and dalvik cache but not the system partition (if you do it, you also don't get asked for your PIN code in TWRP any more, which - as you said - indicates that something went wrong).
Did you install a particular version of the Pixel Experience rom? Maybe that might be part of my issue?
I have try many times installing it. Didn't manage to boot it up.
Finally, tested with Miroom ROM as base then flash the system.img manage to boot up.
Don't know why it didn't boot but at lease any one who have issue booting may want to try using Miroom rom as base.
tllim73 said:
I have try many times installing it. Didn't manage to boot it up.
Finally, tested with Miroom ROM as base then flash the system.img manage to boot up.
Don't know why it didn't boot but at lease any one who have issue booting may want to try using Miroom rom as base.
Click to expand...
Click to collapse
What did you do to install miroom? I've been trying to install it and it just stays on the boot screen. The only non-official from I've been able to install and boot is the unofficial LineageOS rom by fenix-UK.
eremeya said:
What did you do to install miroom? I've been trying to install it and it just stays on the boot screen. The only non-official from I've been able to install and boot is the unofficial LineageOS rom by fenix-UK.
Click to expand...
Click to collapse
I install it using twrp 3.3.0 version. Build 0503. But before that I have install the stock rom goble stable version 10.3.5.0. update FW & Vendor using the same twrp.
tllim73 said:
I install it using twrp 3.3.0 version. Build 0503. But before that I have install the stock rom goble stable version 10.3.5.0. update FW & Vendor using the same twrp.
Click to expand...
Click to collapse
Thanks.
Is your phone a Chinese version or EU version? Were you able to root global stock rom?
eremeya said:
Thanks.
Is your phone a Chinese version or EU version? Were you able to root global stock rom?
Click to expand...
Click to collapse
Hi, I am using a Chinese version. But once you unlock it you will be able to flash any version with the twrp.
I try rooting it with magisk but unable to boot up. That's why I turn to Miroom Rom. They have done something which can boot it up.
tllim73 said:
Hi, I am using a Chinese version. But once you unlock it you will be able to flash any version with the twrp.
Click to expand...
Click to collapse
I'm also using the Chinese version but no matter what I try I cannot root the global version of the rom. I can root the Chinese version fine.
eremeya said:
I'm also using the Chinese version but no matter what I try I cannot root the global version of the rom. I can root the Chinese version fine.
Click to expand...
Click to collapse
Might be the developer version is only for the Chinese Rom. Anyway I am happy now running with GSI Rom.
eremeya said:
I'm also using the Chinese version but no matter what I try I cannot root the global version of the rom. I can root the Chinese version fine.
Click to expand...
Click to collapse
What version of TWRP are you using?
Unofficial builds for Moto X Style (clark)....
Download: https://www.androidfilehost.com/?fid=10763459528675594482 - Version 2020-11-30
Lineage Recovery: https://www.androidfilehost.com/?fid=10763459528675582393 - Version 2020-11-12
TWRP (unofficial): https://www.androidfilehost.com/?fid=10763459528675598925 - Version 2020-12-06.II
What doesn't work (yet).
- Google camera
- Camera: QC reader sometimes doesn't auto-focus (sometimes rotating camera back and forth helps)
- Powerdrain when display on
- Powerdrain when display off could also be better
- You tell me
Sources:
Kernel: https://github.com/chrmhoffmann/android_kernel_motorola_msm8992/tree/staging/rebase/lineage-17.1 [*]
Device: https://github.com/chrmhoffmann/android_device_motorola_clark/tree/staging/lineage-17.1 [**]
Vendor: https://github.com/chrmhoffmann/proprietary_vendor_motorola/tree/staging/lineage-17.1 [***]
Eng version: https://www.androidfilehost.com/?fid=8889791610682927582 - only to be used if the normal ROM crashes on startup
Requirements:
Clark with Nougat (N) bootloader
[*] The kernel sources have already been merged into official lineage repos, but add-ons might come first here. Gerrit contributions are thus open.
[**] Device tree is in gerrit.
[***] Will upload at some point to lineage muppet, but....
Older downloads: Download: https://www.androidfilehost.com/?fid=8889791610682878064
I need your help, bro. I was running the last Nougat update released for the device and did a full factory reset before flashing via TWRP your Lineage OS update and GApps. However, the device had not powered on yet. It simply stays on the Lineage booting phase. What do I do?
thanks soon i will install it
B4oE said:
I need your help, bro. I was running the last Nougat update released for the device and did a full factory reset before flashing via TWRP your Lineage OS update and GApps. However, the device had not powered on yet. It simply stays on the Lineage booting phase. What do I do?
Click to expand...
Click to collapse
I suppose logcat doesn't show anything?
Do you know how to flash boot.img with fastboot?
Chris
Hi @chrmhoffmann
thank you for putting so much work in our old devices,
this weekend i upgraded TWRP to 3.4.0-0 and dirty flashed your UNOFFICIAL_20200625 build over the latest LineageOS 14.1 build for Nougat BL.
It's my son "wifi only" youtube/games device so i cannot test cellular data but everything else it's working.
Photos are 21MP, with correct rotation and camera works if called from apps (tested with hangouts and ghost observer)
The only strange thing is that, while audio is generally working, most games are completely silent.
I first had the impression that was the landscape rotation but happens even on portrait ones.
My son found that even while games are silent, ADS has sounds..
If you need something (logcat, ecc.) let me know, i can also try wiping data if you want.
Thank you,
Fabio
Hello, flashed this rom today coming from stock 7.0.
It booted nice, setup no problems.
Everything is quite smooth, camera working fine.
The handwave gesture to wake up screen is a bit buggy. (Wakes up to late)
Anyway, verry happy to see our old moto running lineage 17.1
Thx for your efforts chrmhoffmann , you did a great job, keep up this great work!
Please provide me with the instructions on how to flash LineageOS 17.1. Apparently, I am doing something wrong. I was on originally on CLARK_RETUS_7.0_NPH25.200-22. Then I flashed TWRP 3.4.0-0. Afterwards, I flashed via TWRP the LineageOS 17.1 from this thread, along with GApps 10.0 micro (ARM64) and Magisk v20.4. Then I rebooted the device. Now the devices just stays on the Lineage loading stage. Please help.
B4oE said:
Please provide me with the instructions on how to flash LineageOS 17.1. Apparently, I am doing something wrong. I was on originally on CLARK_RETUS_7.0_NPH25.200-22. Then I flashed TWRP 3.4.0-0. Afterwards, I flashed via TWRP the LineageOS 17.1 from this thread, along with GApps 10.0 micro (ARM64) and Magisk v20.4. Then I rebooted the device. Now the devices just stays on the Lineage loading stage. Please help.
Click to expand...
Click to collapse
I flashed latest twrp 3.4.0-0 then booted in twrp did a factory reset then I flashed lineage/ gapps nano/ wipe cache/ reboot system. No magisk. Maybe first reboot into system and then try install magisk?
moviefirst said:
I flashed latest twrp 3.4.0-0 then booted in twrp did a factory reset then I flashed lineage/ gapps nano/ wipe cache/ reboot system. No magisk. Maybe first reboot into system and then try install magisk?
Click to expand...
Click to collapse
Should System be mounted on TWRP?
B4oE said:
Should System be mounted on TWRP?
Click to expand...
Click to collapse
I didn't touch system.
B4oE said:
Should System be mounted on TWRP?
Click to expand...
Click to collapse
After factory reset, do I immediately reboot and let it begin and THEN go back to TWRP to flash? Or do I just factory reset and flash LineageOS immediately after?
B4oE said:
After factory reset, do I immediately reboot and let it begin and THEN go back to TWRP to flash? Or do I just factory reset and flash LineageOS immediately after?
Click to expand...
Click to collapse
Install twrp
Reboot into twrp
Factory reset
Flash lineage and gapps nano
Wipe cache
Reboot system, in twrp uncheck install twrp then do not install
Fabiett83 said:
Hi @chrmhoffmann
thank you for putting so much work in our old devices,
this weekend i upgraded TWRP to 3.4.0-0 and dirty flashed your UNOFFICIAL_20200625 build over the latest LineageOS 14.1 build for Nougat BL.
It's my son "wifi only" youtube/games device so i cannot test cellular data but everything else it's working.
Photos are 21MP, with correct rotation and camera works if called from apps (tested with hangouts and ghost observer)
The only strange thing is that, while audio is generally working, most games are completely silent.
I first had the impression that was the landscape rotation but happens even on portrait ones.
My son found that even while games are silent, ADS has sounds..
If you need something (logcat, ecc.) let me know, i can also try wiping data if you want.
Thank you,
Fabio
Click to expand...
Click to collapse
Hi,
Which game for example? I tried candy crush and that has sound
Chris
moviefirst said:
Install twrp
Reboot into twrp
Factory reset
Flash lineage and gapps nano
Wipe cache
Reboot system, in twrp uncheck install twrp then do not install
Click to expand...
Click to collapse
Bro... THANK YOU SO MUCH!! It finally worked.
So far, I noticed that the stock camera app is not auto focusing.
B4oE said:
Bro... THANK YOU SO MUCH!! It finally worked.
So far, I noticed that the stock camera app is not auto focusing.
Click to expand...
Click to collapse
Glad you have succeeded, auto focusing isn't working smooth all the time, maybe the dev will figure it out.
It now seems that I cannot flash via TWRP Magisk v20.4. When I do, TWRP freezes and forces a reboot into my device. Any ideas?
UPDATE: Now it seems that anything I do via TWRP is forcing it to freeze and reboot. I just wiped my cache only and it happened.
chrmhoffmann said:
Hi,
Which game for example? I tried candy crush and that has sound
Chris
Click to expand...
Click to collapse
With this games i have no sound/music:
Archero, Art of war: Legions, Bottle flip 3d, Burrito Bison: Launcher, Cell 13, Crazy Shopping, Hunter assassin, Kick the Buddy, Toca Life World, and others i had no time to test.
Strangely Candy Crush Saga and Ghost Observer has working audio..
I did a backup in twrp-3.4.0-0 but every time i tried to wipe data it rebooted without wiping, thinking that was caused by the F2FS filesystem (same thing happened to my daughter's Serranoltexx from LOS16 to LOS17.1) i changed the internal storage to ext4, reconfigured my son's account and tested the games again, still no audio!
So i restored the twrp backup but since it was a F2FS backup restored in a ext4 partition some games are damaged, i will fix it somehow..
This evening i will save a logcat and see if i can find something useful.
Thank you
Fabio
Edit: Since you are working with the kernel, can you limit CPU freq/cores based on temperature? the phone get really hot, more than in 14.1, and during tests yesterday i lost all battery in like 1 hour.
i don't know how thermald/core control works on clark, but i know that SD810/808 are overheating easily, so it's not an easy task.
i know i's a totally different cpu but was thinking about this commits from Serrano:
https://review.lineageos.org/c/LineageOS/android_kernel_samsung_msm8930-common/+/275733
https://review.lineageos.org/c/LineageOS/android_kernel_samsung_msm8930-common/+/275736
Fabiett83 said:
With this games i have no sound/music:
Archero, Art of war: Legions, Bottle flip 3d, Burrito Bison: Launcher, Cell 13, Crazy Shopping, Hunter assassin, Kick the Buddy, Toca Life World, and others i had no time to test.
Strangely Candy Crush Saga and Ghost Observer has working audio..
I did a backup in twrp-3.4.0-0 but every time i tried to wipe data it rebooted without wiping, thinking that was caused by the F2FS filesystem (same thing happened to my daughter's Serranoltexx from LOS16 to LOS17.1) i changed the internal storage to ext4, reconfigured my son's account and tested the games again, still no audio!
So i restored the twrp backup but since it was a F2FS backup restored in a ext4 partition some games are damaged, i will fix it somehow..
This evening i will save a logcat and see if i can find something useful.
Thank you
Fabio
Edit: Since you are working with the kernel, can you limit CPU freq/cores based on temperature? the phone get really hot, more than in 14.1, and during tests yesterday i lost all battery in like 1 hour.
i don't know how thermald/core control works on clark, but i know that SD810/808 are overheating easily, so it's not an easy task.
i know i's a totally different cpu but was thinking about this commits from Serrano:
https://review.lineageos.org/c/LineageOS/android_kernel_samsung_msm8930-common/+/275733
https://review.lineageos.org/c/LineageOS/android_kernel_samsung_msm8930-common/+/275736
Click to expand...
Click to collapse
Try the new build.
Audio: should be audible now - but is not 100% great yet (cracking noises).
Heat: Well, maybe this works better if thermanager starts now
I also added the Lineage Recovery download link. I hope this can be used instead by people who experience issues with flashing the ROM with TWRP.
chrmhoffmann said:
Try the new build.
Audio: should be audible now - but is not 100% great yet (cracking noises).
Heat: Well, maybe this works better if thermanager starts now
I also added the Lineage Recovery download link. I hope this can be used instead by people who experience issues with flashing the ROM with TWRP.
Click to expand...
Click to collapse
Thank you, as you said audio now works in all games tested, the cracking/stuttering is sometimes present but i'ts not game breaking.
I don't know how removing thermanager service definition could fix the thermanager service but looks like it's working better, too early to see battery life, but at least the temperature seems to be under control.
Since i wanted to keep the good twrp backups i have not tested the new Lineage Recovery.
Fabio
Hello, just a feedback about this rom. I never expected to get Lineageos 17.1 on our old Moto x style. Even the moto actions are built in, the camera functions properly. It would be great if this build became official. I would like to thank the dev very much for his work and dedication so that we can use our reliable moto x style for a long time to come.
For almost a month now I have been happily using LOS 17.1 on my Xiaomi Redmi Note 8T (flashed via LOS recovery, everything working great), until yesterday all of a sudden the OS crashed (I actually don't know what happend, I put the phone away and when I wanted to use it again I just saw the boot screen). Now the phone wont boot to OS no matter what I do (restart, turn off and on, fastboot and back), but I can still enter recovery.
What the hell happened??
What I can do to fix it - e.g. reinstall LOS/install last update?
Will any of the steps to fix it remove the data on my phone?
lueromat said:
For almost a month now I have been happily using LOS 17.1 on my Xiaomi Redmi Note 8T (flashed via LOS recovery, everything working great), until yesterday all of a sudden the OS crashed (I actually don't know what happend, I put the phone away and when I wanted to use it again I just saw the boot screen). Now the phone wont boot to OS no matter what I do (restart, turn off and on, fastboot and back), but I can still enter recovery.
What the hell happened??
What I can do to fix it - e.g. reinstall LOS/install last update?
Will any of the steps to fix it remove the data on my phone?
Click to expand...
Click to collapse
1-delete the folder : data/system/dropbox
reboot,and when the system restarts , read logs in that folder to know what is happening
2-if you didn't remove any important system file, reinstall will fix nothing
3-in most cases,wiping data will fix the problem, just be prepared to it
your best shot would be making a twrp backup of data and explore it with 7z and try to restore your app + data when the system boots
thanks !
how can I access the dropbox folder if the system isn't booting? not finding the device in fastboot...
I don't have twrp, but lineage recovery - is that an issue? there are also some logs here, but probably not related to the system, I assume?
lueromat said:
how can I access the dropbox folder if the system isn't booting?
I don't have twrp, but lineage recovery - is that an issue? there are also some logs here, but probably not related to the system, I assume?
Click to expand...
Click to collapse
next time use "quote" or "reply" so i get a notification
i don't know if lineage recovery has a file manager or not, but i strongly recomand using orangefox recovery for multiple reasons ...
when you make a backup of data, browse to that folder and do what i said
and when your system is on you can restore your app + data using that backup and titanium backup app or copy paste if you know the path ...
so I ended up flashing LOS and pic GApps again, as per a suggestion on reddit, which didn't wipe my data:
https://www.reddit.com/r/LineageOS/comments/lotixs
it was suggested that the crash could have originated from some GApps error, but since those logs were overwritten with the reinstall I'll never find out
loopypalm said:
i don't know if lineage recovery has a file manager or not, but i strongly recomand using orangefox recovery for multiple reasons ...
Click to expand...
Click to collapse
I don't have a ton of experience with different recoveries, so far I have used TWRP and LOS recovery and have been moderately happy - orange fox looks like a great project, I'll make sure to give it a try next time
lueromat said:
so I ended up flashing LOS and pic GApps again, as per a suggestion on reddit, which didn't wipe my data:
https://www.reddit.com/r/LineageOS/comments/lotixs
it was suggested that the crash could have originated from some GApps error, but since those logs were overwritten with the reinstall I'll never find out
lueromat said:
so I ended up flashing LOS and pic GApps again, as per a suggestion on reddit, which didn't wipe my data:
https://www.reddit.com/r/LineageOS/comments/lotixs
it was suggested that the crash could have originated from some GApps error, but since those logs were overwritten with the reinstall I'll never find out
I don't have a ton of experience with different recoveries, so far I have used TWRP and LOS recovery and have been moderately happy - orange fox looks like a great project, I'll make sure to give it a try next time
Click to expand...
Click to collapse
I don't have a ton of experience with different recoveries, so far I have used TWRP and LOS recovery and have been moderately happy - orange fox looks like a great project, I'll make sure to give it a try next time
Click to expand...
Click to collapse
You shouldn't have flashed pic GApps coz of that it will go to same issue when the rom gets updated. Instead flash OpenGapps one of the best GApps for LineageOS. There was same issue with my Moto G3 Turbo(Merlin) when I flashed BitGapps, always use Trusted GApps by LineageOS. It is also available on the LineageOS Forum