Related
1. AOSP, by @freexperia -
https://www.androidfilehost.com/?a=show&w=files&flid=17562
Tested 2/27 AOSP build. Seems smooth and stable overall. Only browser is some kind of experimental one that doesn't work too well, or at least you need to spend more time getting used to it than I was willing to. Camera works, but is as good as any other N camera at this point, (bad).
2. AOSP and Lineage, (CM), 14, micro-g patched, by @MSe1969 - https://www.androidfilehost.com/?a=show&w=files&flid=155737 - haven't tried yet. I mistakenly linked it to fxp until I just now noticed it. Will try soon...
3. AICP - https://forum.xda-developers.com/so...lopment/rom-aicp-11-0-mm-6-0-1-amami-t3428288
Excellent rom, regular updates, and lots of customization. Some people have posted about dropped calls in recent builds, but haven't heard of other issues. Magisk integrated. If someone can figure out how to get a good camera, you could hardly ask for more.
4. AOSP by @CLINTZ9 - https://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/aosp-t3317511
I haven't been able to get it to boot, (error in twrp). OP says to ignore error and flash, but it won't flash anything for me. I think others have, though, so maybe just something I'm missing. Let me know.
5. LOS by micha-btz - https://www.androidfilehost.com/?w=files&flid=153937
Just stumbled across it, and my BL is currently re-locked, so plan on trying soon...
Update - tried today and works well, everything seemed to function. Bad camera as usual, and I couldn't get back into recovery for some reason. I had to flash a different kernel first...
6. CM14/LOS builds by @derf elot https://www.androidfilehost.com/?w=files&flid=41716
7. AOSP builds by SonyAOSP team, (@davidteri91) - https://www.androidfilehost.com/?a=show&w=files&flid=187966
8. LOS 14 by @Hazou - https://forum.xda-developers.com/so...opment/rom-unofficial-lineageos-14-1-t3636822
Haven't tried yet. Let us know...
9. LOS 14 by munjeni - https://forum.xda-developers.com/sony-xperia-z1-compact/development/rom-t3657384 Probably the best yet. Excellent camera. Some have had random reboots on latest build, but maybe fixed with this - http://munjeni.myiphost.com/system.rar
10. Sudamod by @maz-1 - https://forum.xda-developers.com/sony-xperia-z1-compact/development/rom-sudamod-3-1-t3666092
Testing now, LOS-based with some custom tweaks. Fast and smooth, fully working. Op says camera is good, even though 3.1 kernel, pictures look OK so far, going to test more in the light. Very nice ROM.
11. M-ROM port by @dmgZero - https://forum.xda-developers.com/sony-xperia-z1-compact/development/m-rom-v2-4-0-t3711381
Stock Nougat style and apps on custom (Carbon) rom. Very nice. Original dev seems to have abandoned xda, but rom has been popular on several devices up to v2.3.1 (I use it on Z3c [https://forum.xda-developers.com/z3-compact/development/rom-los-xperia-ui-z3c-t3654894]). 2.4 was never posted on xda, AFAIK, but posted on a Chinese site called 0z4l, or something, but not possible to download without registration, and I couldn't get successful registration. dmgZero has modded it, apparently. I haven't tried it, since I'm using Z3c at the moment...
BTW - seems to be some degree of controversy around the security of latest version. Check device threads and judge for yourself.
12. Flyme OS by @dmgZero - https://forum.xda-developers.com/sony-xperia-z1-compact/development/m-rom-z1cflyme6-8-1-22r-t3742581 I'm mainly on Xc now, so check thread for reports...
to those that have tried the FXP 7.0 (nougat) rom:
did you encounter any other problems besides the non working camera?
Tried out AICP 10/3. Looks good, runs good, no camera...
levone1 said:
Tried out AICP 10/3. Looks good, runs good, no camera...
Click to expand...
Click to collapse
saw you install third party camera. did it worked?
bardagolkapote said:
saw you install third party camera. did it worked?
Click to expand...
Click to collapse
No camera with any app - just black screen.
can anyone help me please , i need to get the new bootloader with the real recovery coz i want to flash this rom
alaaawi said:
can anyone help me please , i need to get the new bootloader with the real recovery coz i want to flash this rom
Click to expand...
Click to collapse
https://tapatalk.com/shareLink?url=...share_tid=3117568&share_fid=3793&share_type=t
New bootloader for open devices (now with real recovery)
twrp 3.0.0.2
CM12.1/AICP 11
?I use Google translation?
alaaawi said:
can anyone help me please , i need to get the new bootloader with the real recovery coz i want to flash this rom
Click to expand...
Click to collapse
Link?
Tapatalkkal küldve az én Sony z1 compact eszközömről
http://forum.xda-developers.com/showthread.php?t=3117568
twrp 3.0.0.2
CM12.1/AICP 11
?I use Google translation?
Jesusnagler said:
http://.xda-.com/showthread.php?t=3117568
twrp 3.0.0.2
CM12.1/AICP 11
I use Google translation
Click to expand...
Click to collapse
it worked , thanks man
New AICP build 11/4
hi good day. I'm pretty new to flashing
I managed to install some custom rom and gapps with TWRP.
so I'm now a bit more confident in installing new roms
there's so many custom roms, I don't know which to choose. I need something not bloated, fast, and fully working camera. any help is greatly appreciated.
(or maybe I just should root the stock rom and uninstall bloated apps ?)
zzzxtreme said:
hi good day. I'm pretty new to flashing
I managed to install some custom rom and gapps with TWRP.
so I'm now a bit more confident in installing new roms
there's so many custom roms, I don't know which to choose. I need something not bloated, fast, and fully working camera. any help is greatly appreciated.
(or maybe I just should root the stock rom and uninstall bloated apps ?)
Click to expand...
Click to collapse
Try jaguar rom, it works great for me and is really well made and maintained:good:
DrtiBarta said:
Try jaguar rom, it works great for me and is really well made and maintained:good:
Click to expand...
Click to collapse
zzzxtreme said:
hi good day. I'm pretty new to flashing
I managed to install some custom rom and gapps with TWRP.
so I'm now a bit more confident in installing new roms
there's so many custom roms, I don't know which to choose. I need something not bloated, fast, and fully working camera. any help is greatly appreciated.
(or maybe I just should root the stock rom and uninstall bloated apps ?)
Click to expand...
Click to collapse
For the short answer, he's probably right - Jaguar Is excellent. However, there are now very good roms for this phone in kk, lp, mm, and now n, so there's lots to try. If stability and camera are your main priorities, go with stock-based, or Jaguar. Personally, I don't feel debloating is necessary, if you use an app-management app, like AFwall, or 3C toolbox.
thanks guys !! i shall try jaguar !
I don't find the link for Jaguar N
Sony Z1c
twrp 3.0.0.2
CM12.1/AICP12.1
?I use Google translation?
Jesusnagler said:
I don't find the link for Jaguar N
Sony Z1c
twrp 3.0.0.2
CM12.1/AICP12.1
?I use Google translation?
Click to expand...
Click to collapse
Jaguar is lollipop And There wont be N rom.
DrtiBarta said:
Jaguar is lollipop And There wont be N rom.
Click to expand...
Click to collapse
OK, I understand
Thanks[emoji106]
Sony Z1c
twrp 3.0.0.2
CM12.1/AICP12.1
?I use Google translation?
Jaguar has all the security updates included which even some Nougat Roms does not have.
Hi there,
I made a CM14.1 build for amami for you to try, based on the sources of sonyxperiadev, SonyCM and SonyAosp. So a big thank you is in order to everyone involved in these projects. I only modified the sonyxperiadev amami sources to work with this build, set SELinux to enforced and removed the Gello browser from the build (there are more updated derivatives on the Play Store anyway).
I have run it for a little bit, and noticed the following bugs so far:
- deepsleep not working when wifi is on (I think)
- camera sometimes force closes, sometimes works (known memory leak bug I think, cam is work in progress)
- lots of CM stuff is not there yet, including themes (remember, CM14.1 is a work in progress)
- ?
To install it, you most likely need real recovery with TWRP3. It includes the new Sony init, so reboot to recovery from ROM works. I'm currently using it with latest OpenGapps and SuperSU, which both seem to work fine as well.
The Z1C is currently my secondary phone, but once it becomes more stable and feature-rich and once Xposed is available for 7.1 (fingers crossed), I will probably also build for the Z3C. Unless we get to see some official CM love again of course.
Sources:
sonyxperiadev: https://github.com/sonyxperiadev
SonyCM: https://github.com/SonyCM
SonyAosp: https://github.com/sonyaosp
Mine (for amami): https://github.com/derfelot/android_device_sony_amami
Download: https://www.androidfilehost.com/?fid=457095661767120697
Cheers
I am currently on MIUI 7, the one just before it updates to MIUI 8. What I want to know is, what is the best possible custom rom I can flash to that will work with this device? I have Team Win Recovery 3.0.0.0 installed.
I have installed Redmi 2 2014811 for my casual user (no root or else) with this base rom : miui_HM2XWCProGlobal_V8.0.7.0.LHJMIDG_3240991baf_5.1.zip via CWM
AMJ_Vario said:
I have installed Redmi 2 2014811 for my casual user (no root or else) with this base rom : miui_HM2XWCProGlobal_V8.0.7.0.LHJMIDG_3240991baf_5.1.zip via CWM
Click to expand...
Click to collapse
Cool thanks, I will look up the rom. I thought about Android 6 or 7, but see those still have some major issues here and there.
saa044 said:
Cool thanks, I will look up the rom. I thought about Android 6 or 7, but see those still have some major issues here and there.
Click to expand...
Click to collapse
Major issues?which ROM r u talking about?there are so many ROMs those are pretty stable.Only minor bugs(miui also have this)
BTW devs work very hard for these ROMs and they got nothing but our thanks and encouragement. These custom ROMs are way better in performance and customization than sluggish and heavy MIUI rom.
My phone is 8months old and this phone is still with me because of efforts of devs.
So don't be so demanding about 200% no bug and be thankful to them.
raymond_bqg said:
Major issues?which ROM r u talking about?there are so many ROMs those are pretty stable.Only minor bugs(miui also have this)
BTW devs work very hard for these ROMs and they got nothing but our thanks and encouragement. These custom ROMs are way better in performance and customization than sluggish and heavy MIUI rom.
My phone is 8months old and this phone is still with me because of efforts of devs.
So don't be so demanding about 200% no bug and be thankful to them.
Click to expand...
Click to collapse
Don't get me wrong, I am very grateful. I worked on Windows Mobile roms back in the day so know what type of work goes into it. I have only started to look at custom roms today and am so completely lost, guess I chose the wrong word being major. When i said major I had camera and Gps in mind, as I saw some of those roms had issues with those. So again, no disrespect meant from my side and I apologize if It came out that way. I was just kind of hoping someone could bump me in the right direction. The last time this phone was flashed the previous owner flashed it in such a way that the sim card could not be detected, after fixing that I flashed a MIUI rom, but that was sort of the Chinese version and stuff like google services did not work properly and push notifications would not work unless you turn the phone on and go into the app. So yeah if you can point me in the right direction I will appreciate it a lot.
saa044 said:
Don't get me wrong, I am very grateful. I worked on Windows Mobile roms back in the day so know what type of work goes into it. I have only started to look at custom roms today and am so completely lost, guess I chose the wrong word being major. When i said major I had camera and Gps in mind, as I saw some of those roms had issues with those. So again, no disrespect meant from my side and I apologize if It came out that way. I was just kind of hoping someone could bump me in the right direction. The last time this phone was flashed the previous owner flashed it in such a way that the sim card could not be detected, after fixing that I flashed a MIUI rom, but that was sort of the Chinese version and stuff like google services did not work properly and push notifications would not work unless you turn the phone on and go into the app. So yeah if you can point me in the right direction I will appreciate it a lot.
Click to expand...
Click to collapse
Video recording was a issue for Nougat based ROM but it has been fixed.And about gps, it is working fine (i like to use waze)with Marshmallow based ROM.I don't know about nougat as I didn't fully moved to nougat.I have downloaded Tesla (N) and sodamod(cm 14) today .So I will report you soon about GPS in Nougat.
Till now I have tried cm(M),RR(M),DU(M),Tesla(M),orion(M),zephyre(M),AICP(M),AOKP(M).Most of them has kept my expectation.Now I am on project-x(M).It is also suberb with almost no problem.
If you want to stick with miui based then there is also"thunder-miui" by @gkalen.
Try these ROMs and see which is suitable for you.I like to stick with cm based for C.M.T.E.
Edit:-GPS works fine in nougat.
Lollipop (5.x) - CM 12.1
Marshmallow (6.x) - MoKee
Nougat (7.x) - I only tested Suda not good for daily driver
Hello,
It's been almost a little over a year since I was last really into android customization. Since it's been so long it has become clear to me that my phone is outdated in many ways. I'm still running OxygenOS 2.2.1 with Android 5.1.1. I've been wanting to update up to Android N (7.x.x) for a long time now, but haven't seen any real stable roms or haven't really had the time to look for one. Now I've finally found my self with free time and ready upgrade my rom. I've just faced couple of problems, I can't really find what should I do when upgrading from 5.1.1 to 7.x.x since no-one is really doing that anymore. I remember reading sometime back that if you dont have the right firmwares you'll brick ur phone, and I wouldn't really want to go through that hassle at the moment. Is it still a thing or should it be just fine for me to flash a new rom just on top of this? (Ofc with clearing memory etc) Other question that is in my mind is that is there any critical bugs in Android N roms? It's bit unclear to me since there are such many roms that have their status as work in progress or beta etc, but some roms have status as stable. Are there any roms that I should clearly avoid? Im not new to this so I don't really need any deep info how to do everything etc, just a bit of a oversight on how things are going atm.
Thanks.
first of all is ur device rooted?? If yes then install the latest twrp recovery...then take a backup.. and flash any nougat rom which u like...If at all u would need Volte support then u l have to flash the 3.5.7 firmware..or else the 3.1.0 firmware works fine with most of the nougat roms..some nougat roms i would recommend are AICP, Resurrection Remix and AOSP extended .... In my suggestion u should probably first upgrade the Oxygen Os on ur device through official updates via OTA atleast upto the 3.5.6 firmware
there's no need to update until 3.5.6, unless you aren't going to plan staying with OOS [the only "stable" firmware which provides you VoLTE working, but it's still M-based and not N].
as @mhd athiq said, unlock your bootloader [just in case you still haven't done it before] then update your TWRP recovery to the latest version.
then flash the incrementals OTAs until OOS 3.1.x and you are good to go to flash any custom ROM which is N-based.
to avoid any mistake, please make a EFS backup via terminal [just to have a backup of your modems] and save the files to a safe location.
I don't have a specific ROM to suggest to you, but in my experience I have found the CAF/AOSP-based ones to be the ones with the best battery backup and less bugs then LOS-based ones.
I have used happily for a few months CypherOS version 3.5.1 [not the latest one, I find it quite unstable as the developers tried to implement OMS].
sidenote:
flashing N-based custom ROMs upon OOS 3.5.6 firmwares gives random reboots and unstable network in many cases/scenarios.
so don't update to that OOS version unless you have a mandatory VoLTE feature required [but you'll have to live with random reboots and poor network stability].
After waiting over a year for the Nougat update (still nothing) and almost a year for a security patch (nothing since Dec 2016), and now knowing Moto will probably never patch the KRACK wpa2 bug, I'm officially done with Motorola and their carelessness with our security.
My questions:
I assume if I load a custom ROM, I will be able to stay up to date with patches and new Android versions? True?
Which one do you all recommend?
Edit: A solution which can pass Safetynet is HIGHLY preferred
I don't need anything fancy, I just want everything to work properly like the stock ROM, but be able to stay up to date
I don't even need root, as in the past I've had some apps stop working if I was rooted, although with systemless root, that night not be a problem anymore. I guess it would be nice to be able to root if desired, but have it as an option only.
Edit- probably should have mentioned I'm on the US Moto X Pure Edition (XT1575)
Thanks for any help.
xdafan15 said:
After waiting over a year for the Nougat update (still nothing) and almost a year for a security patch (nothing since Dec 2016), and now knowing Moto will probably never patch the KRACK wpa2 bug, I'm officially done with Motorola and their carelessness with our security.
My questions:
I assume if I load a custom ROM, I will be able to stay up to date with patches and new Android versions? True?
Which one do you all recommend?
I don't need anything fancy, I just want everything to work properly like the stock ROM, but be able to stay up to date
I don't even need root, as in the past I've had some apps stop working if I was rooted, although with systemless root, that night not be a problem anymore. I guess it would be nice to be able to root if desired, but have it as an option only.
Edit- probably should have mentioned I'm on the US Moto X Pure Edition (XT1575)
Thanks for any help.
Click to expand...
Click to collapse
First off it's a 2 year old phone. That's a normal end of update cycle. Second the 7.0 update is out for the 1575 but for some reason only Sprint Sims seem to have gotten it so far. It's still coming to your phone. Custom roms are nice for updates to a point but safety net still doesn't like them if I recall properly. I switched from the pure to a Moto Z play and have loved it. About to get the October security patch and they're already working on Oreo for it. The pure was the last phone before Lenovo took over. There were issues with the hand off but they seem to have it together mostly now.
@xantanion, thanks for your post. I could argue with you about whether the phone was updated on a timely basis over the last 2 years, but I don't want to get into that right now.
Good point about safetynet. If I'm going to go custom ROM, I'd like to be able to pass safetynet, whether by using Magisk, not rooting, using a custom kernel, whatever options are available/necessary.
With this in mind, any suggestions for a solution?
Not getting security patches (my current situation) is not acceptable.
I'd like to squeeze another year out of this phone before replacing. Thanks for any suggestions
xdafan15 said:
@xantanion, thanks for your post. I could argue with you about whether the phone was updated on a timely basis over the last 2 years, but I don't want to get into that right now.
Good point about safetynet. If I'm going to go custom ROM, I'd like to be able to pass safetynet, whether by using Magisk, not rooting, using a custom kernel, whatever options are available/necessary.
With this in mind, any suggestions for a solution?
Not getting security patches (my current situation) is not acceptable.
I'd like to squeeze another year out of this phone before replacing. Thanks for any suggestions
Click to expand...
Click to collapse
I'd switch to Dirty unicorns. I retired this phone a couple of months ago, but they maintain it regularly, and release monthly security patches. As for safety net, magisk works great. Since on Android 7.0 + even an unlocked bootloader trips safety net, then you actually NEED magisk to patch that and then pass safety net. DU is an unrooted ROM but just flash magisk afterwords.
xdafan15 said:
@xantanion, thanks for your post. I could argue with you about whether the phone was updated on a timely basis over the last 2 years, but I don't want to get into that right now.
Good point about safetynet. If I'm going to go custom ROM, I'd like to be able to pass safetynet, whether by using Magisk, not rooting, using a custom kernel, whatever options are available/necessary.
With this in mind, any suggestions for a solution?
Not getting security patches (my current situation) is not acceptable.
I'd like to squeeze another year out of this phone before replacing. Thanks for any suggestions
Click to expand...
Click to collapse
Lineage OS 14.1 (based on nougat 7.1.2) gets security updates monthly. It's close to vanilla android and doesn't come with all the bells and whistles of unicorns or aicp. This is good for those happy with the stock android features like myself. I don't need custom themes and crazy config options. Never needed a custom kernel. Battery and performance is exceptional as is.
https://download.lineageos.org/clark
Rooting with Magisk 14 will pass safetynet. I use android pay daily with no problems.
https://forum.xda-developers.com/attachment.php?attachmentid=4302781&d=1508010356
I run with a fairly minimal OpenGApps 7.1 arm64 aroma installation. I use the aroma installer and pretty much only check the boxes for a few apps to be pre installed. If I really need something I can grab it from the play store or apk mirror. My base config for OpenGApps aroma is here: https://drive.google.com/drive/folders/0B2lKWOIH0bTqMEQ1cmo2QjlydDA?usp=sharing
https://github.com/opengapps/arm64/...71102/open_gapps-arm64-7.1-aroma-20171102.zip
If the new stock 7.0 nougat release is what you're after you can get a twrp backup here you can restore from. Keep in mind this is 7.0 not 7.1.2 and security patch up to only September 2017. This will be the last update to the Moto X Pure/Style. So no further security patches.
I tried stock 7.0 for a few days but went back to Lineage OS. I missed the long press on icons to get actions menu that isn't in 7.0 (among other things).
Spencervb256 said:
I'd switch to Dirty unicorns. I retired this phone a couple of months ago, but they maintain it regularly, and release monthly security patches. As for safety net, magisk works great. Since on Android 7.0 + even an unlocked bootloader trips safety net, then you actually NEED magisk to patch that and then pass safety net. DU is an unrooted ROM but just flash magisk afterwords.
Click to expand...
Click to collapse
ptn107 said:
Lineage OS 14.1 (based on nougat 7.1.2) gets security updates monthly. It's close to vanilla android and doesn't come with all the bells and whistles of unicorns or aicp. This is good for those happy with the stock android features like myself. I don't need custom themes and crazy config options. Never needed a custom kernel. Battery and performance is exceptional as is.
https://download.lineageos.org/clark
Rooting with Magisk 14 will pass safetynet. I use android pay daily with no problems.
https://forum.xda-developers.com/attachment.php?attachmentid=4302781&d=1508010356
I run with a fairly minimal OpenGApps 7.1 arm64 aroma installation. I use the aroma installer and pretty much only check the boxes for a few apps to be pre installed. If I really need something I can grab it from the play store or apk mirror. My base config for OpenGApps aroma is here: https://drive.google.com/drive/folders/0B2lKWOIH0bTqMEQ1cmo2QjlydDA?usp=sharing
https://github.com/opengapps/arm64/...71102/open_gapps-arm64-7.1-aroma-20171102.zip
If the new stock 7.0 nougat release is what you're after you can get a twrp backup here you can restore from. Keep in mind this is 7.0 not 7.1.2 and security patch up to only September 2017. This will be the last update to the Moto X Pure/Style. So no further security patches.
Click to expand...
Click to collapse
Thanks, @Spencervb256, for the recommendation and comments on Safetynet and security patches.
Double thanks, @ptn107, for the helpful recommendations and files. I really appreciate you sharing that info.
If you'll continue to put up with my ignorance, do I correctly understand how to restore to stock if I choose to do so later as listed below. I'm still on MPHS24.49-18-16. I didn't update to 7.0.
1) According to this thread, the MotoX Pure can only be returned to the stock firmware it was running before switching to a custom ROM, or to a newer version. You cannot go back to an earlier version.
2) There isn't a firmware .zip available for 24.49-18-16, so according to this post, you flash the 24.49-18-8 .zip (which IS available) and then sideload the .zip from @annoyingduck to update to 18-16 to get back to where you started.
3) Alternately, since the file for Nougat 7.0 is available, I could also update to 7.0, then load a custom ROM, and later return to 7.0 using the available file.
Am I understanding this process correctly?
Thanks in advance for your help.
xdafan15 said:
Thanks, @Spencervb256, for the recommendation and comments on Safetynet and security patches.
Double thanks, @ptn107, for the helpful recommendations and files. I really appreciate you sharing that info.
If you'll continue to put up with my ignorance, do I correctly understand how to restore to stock if I choose to do so later as listed below. I'm still on MPHS24.49-18-16. I didn't update to 7.0.
1) According to this thread, the MotoX Pure can only be returned to the stock firmware it was running before switching to a custom ROM, or to a newer version. You cannot go back to an earlier version.
2) There isn't a firmware .zip available for 24.49-18-16, so according to this post, you flash the 24.49-18-8 .zip (which IS available) and then sideload the .zip from @annoyingduck to update to 18-16 to get back to where you started.
3) Alternately, since the file for Nougat 7.0 is available, I could also update to 7.0, then load a custom ROM, and later return to 7.0 using the available file.
Am I understanding this process correctly?
Thanks in advance for your help.
Click to expand...
Click to collapse
I'm not extremely knowledgeable on the whole returning to stock unfortunately...but if you're currently on 6.0, almost all the custom roms are compatible with that firmware, and only a SELECT FEW (such as a lineage os test build) are compatible with the newer 7.0 stock firmware. Paging @dzidexx for a better explanation
Spencervb256 said:
I'm not extremely knowledgeable on the whole returning to stock unfortunately...but if you're currently on 6.0, almost all the custom roms are compatible with that firmware, and only a SELECT FEW (such as a lineage os test build) are compatible with the newer 7.0 stock firmware. Paging @dzidexx for a better explanation
Click to expand...
Click to collapse
Thanks again, @Spencervb256.
So you're saying that the Android version of my custom rom has to match the version of the stock rom that I'm coming from? No mixing marshmallow and nougat?
Also, if I stay on marshmallow and want to return to stock and unroot, I wonder if I can just flash the available nougat firmware and restore the stock recovery. Maybe @dzidexx can help with that question, too.
Wish I was more skilled in all this. Thanks for the help.
xdafan15 said:
Thanks again, @Spencervb256.
So you're saying that the Android version of my custom rom has to match the version of the stock rom that I'm coming from? No mixing marshmallow and nougat?
Also, if I stay on marshmallow and want to return to stock and unroot, I wonder if I can just flash the available nougat firmware and restore the stock recovery. Maybe @dzidexx can help with that question, too.
Wish I was more skilled in all this. Thanks for the help.
Click to expand...
Click to collapse
No haha it's hard to explain. But until about a month ago, no custom roms could be flashed if users were running stock 7.0 from Moto. Now there are a couple builds of roms which can be flashed over stock 7.0, with no bootloops. This is because Motorola upgraded the modem firmware in stock 7.0, so the custom roms did not work with it.
You can 100% mix the two, so if you are in stock 6.0, you can install any rom you like, as they are made to work with the 6.0 firmware. Even though they are nougat roms.
When stock 7.0 was released, people had issues with installing custom roms over that, because of the modem upgrade, but now there are a couple builds that will install over this firmware and not result in a bootloop.
I will try and find a few links for you which can explain some things, this is all from my mediocre memory haha
If that confused you even more then just stay tuned, I'll send you a pm soon with links to some reading in different threads which explain it much better than I can!
@Spencervb256, I think I understand you. Most of the custom ROMs, whether MM or N, use the stock radios released with MM. When Moto updated to N, they also changed the cellular radio, so the custom ROMs don't work properly unless they are updated to be compatible with it.
So then, if I stay on MM, I can use any custom ROM, if I would've updated, I'd be limited to the few ROMs that were updated.
xdafan15 said:
@Spencervb256, I think I understand you. Most of the custom ROMs, whether MM or N, use the stock radios released with MM. When Moto updated to N, they also changed the cellular radio, so the custom ROMs don't work properly unless they are updated to be compatible with it.
So then, if I stay on MM, I can use any custom ROM, if I would've updated, I'd be limited to the few ROMs that were updated.
Click to expand...
Click to collapse
Pretty much...
xantanion said:
First off it's a 2 year old phone. That's a normal end of update cycle. Second the 7.0 update is out for the 1575 but for some reason only Sprint Sims seem to have gotten it so far. It's still coming to your phone. Custom roms are nice for updates to a point but safety net still doesn't like them if I recall properly. I switched from the pure to a Moto Z play and have loved it. About to get the October security patch and they're already working on Oreo for it. The pure was the last phone before Lenovo took over. There were issues with the hand off but they seem to have it together mostly now.
Click to expand...
Click to collapse
aybarrap1 said:
Pretty much...
Click to expand...
Click to collapse
My rule of thumb is simply wait for the official supported OS version. This means everything (including modem) will work - the community will then hack and modify from there.
xdafan15 said:
@Spencervb256, I think I understand you. Most of the custom ROMs, whether MM or N, use the stock radios released with MM. When Moto updated to N, they also changed the cellular radio, so the custom ROMs don't work properly unless they are updated to be compatible with it.
So then, if I stay on MM, I can use any custom ROM, if I would've updated, I'd be limited to the few ROMs that were updated.
Click to expand...
Click to collapse
That's exactly it! You nailed it. Explained it better than I could, so yeah, you got it!!
What you guys suggest!? I want to root my Phone but I am waiting for The Oreo Update
Should I wait Further or not!?
Personally I was wondering the same, but decided a week or so ago to unlock the bootloader and install lineage 14.1. Happy with my decision, it actually fixed a bug I had with NFC only working occasionally. Also good to be able to use my root apps again. I won't upgrade to Oreo until after the official Oreo release and developers have had a chance to fix the issues there seems to be with Bluetooth calling, votle, imei, etc.
So my answer would be sure go ahead, as long as you know what you're doing it for and understand the risks.
I agree with NZedPred, nothing wrong with rooting and installing custom rom, but I wouldn't install any Oreo rom until/if official Oreo for this device gets released. Just too many problems.
Same here waiting for Oreo before root
Rutambh said:
Admin Note: This is a special Q&A-formatted thread. Please follow this link to view it in your browser: http://xda.tv/post76427271
Click to expand...
Click to collapse
If you can fix the various common problems that may come with custom ROMs, go ahead. Otherwise, you could stay stock and wait for the update. It all depends on you if you want to have the latest Oreo (8.1 and the latest security patches).
If you just want to root, it's fine too but you'll still lose warranty.
Not sure, i have zero problems on ResurrectionRemix Oreo.
I was thinking the same and now i'm glad that i did it. RR working like a champ.
some custom rom are stable and u can use for daily driver
I'll wait. There's nothing revolutionary about Android 8, the custom roms are almost always buggy, and also all these reports of IMEI 0 are troublesome.