Related
Thinking about moving over to oreo from PureNexus as the updates are alot more timely and there may not be much of a future in custom roms on the XL however I have a few questions I hope someone can help me with
1) How easy is it to update to new versions of oreo without wiping my device every time or losing installed mods.
2) I only use a few mods, is there anything out there that will help me centre the clock and hide the battery icon
3) Do i go with supersu or majisk what is the most reliable, i'd use it with custom kernel and adaway mostly
If anyone can shed some light it would be appreciated
1) As far as I know if you want to switch from a custom ROM to stock your best bet is to completely wipe your phone before installing the stock ROM. This gives you the freshest start and makes sure no unnecessary files/folders are left behind that could interfere with performance.
2) Stock 8.0 has a system UI tuner as a hidden feature that lets you hide the clock and battery icons if you wish, centering the clock is not an option though. I am not sure what mods are available to center the clock but I loved being able to do that in my custom roms as well.
3) I went with Magisk as I was able to root my phone without a custom kernel, thus allowing me to still receive OTA updates in the future without fear of losing my root. Magisk has a module that blocks ads much like adaway does and it has worked great for me. I've also installed busy box and lucky patcher which are all working as needed. Magisk also hides itself/root without needing to flash another file which just seemed easier and more intuitive to me. I'm able to use Android Pay, Pokemon Go, Netflix ect without a hitch.
Thanks for the answer but I think the first question was misinterpreted, my question was, once on oreo how easy is it to update to new versions of oreo without wiping the device each time and keeping my mods intact, does it do it like if I were stock or do I have to flash a new image via bootloader
yusuo said:
Thanks for the answer but I think the first question was misinterpreted, my question was, once on oreo how easy is it to update to new versions of oreo without wiping the device each time and keeping my mods intact, does it do it like if I were stock or do I have to flash a new image via bootloader
Click to expand...
Click to collapse
Some people here update simply by flashing the OTA zip file. I personally don't do this.
Every month when google rolls out the new update, I wipe the device and flash the stock images via fastboot. It's the way I have done it for years and in my opinion is the safest way.
As far as mods, specifically center clock mod, I have several running on my device which is on the latest October security patch.
https://forum.xda-developers.com/pixel-xl/themes/mods-android-oreo-aroma-installer-misc-t3666777
The linked thread is an awesome mod collection by tulsadiver. He created an aroma mod installer. Follow the directions. You flash it in TWRP and flash one mod at a time. Works great.
Pain-N-Panic said:
Some people here update simply by flashing the OTA zip file. I personally don't do this.
Every month when google rolls out the new update, I wipe the device and flash the stock images via fastboot. It's the way I have done it for years and in my opinion is the safest way.
As far as mods, specifically center clock mod, I have several running on my device which is on the latest October security patch.
https://forum.xda-developers.com/pixel-xl/themes/mods-android-oreo-aroma-installer-misc-t3666777
The linked thread is an awesome mod collection by tulsadiver. He created an aroma mod installer. Follow the directions. You flash it in TWRP and flash one mod at a time. Works great.
Click to expand...
Click to collapse
Thanks for your help, nice hercules reference
First time messing with this phone
followed the instructions for unlocking bootloader, installing TWRP, and rooting here: https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unlock-bootloader-flash-twrp-t3704592
Successfully unlocked bootloader, flashed TWRP, but now hung up on SuperSU.
Flashed SuperSU VV2.82 zip from http://www.supersu.com/download in TWRP
Wiped dalvik and cache
reboot
Now it's been about 10 minutes. Blank screen and blue LED.
Hold power until it reboots again, Android sometimes has issues with new boot.imgs at first
l3ones said:
Hold power until it reboots again, Android sometimes has issues with new boot.imgs at first
Click to expand...
Click to collapse
I did, three times.
I ended up flashing the latest complete OTA to get it back to being able to boot.
Are you on Oreo? I don't know if SuperSU is compatible with it. I switched to Magisk a few weeks ago.
Macusercom said:
Are you on Oreo? I don't know if SuperSU is compatible with it. I switched to Magisk a few weeks ago.
Click to expand...
Click to collapse
was on the latest stock OTA, which was 8.0.0
Flashed Mgisk after flashing the latest OTA, and everything is working swimmingly
Exact Same thing happened to me last night.
And I lost my internal sdcard.
Eventually flashed stock recovery didn't do anything different so flash twrp again and got sdcard back.
It was a strange one.
Now I'm waiting for an update or the right file for root.
Maybe this has something to do with Keymaster?
So, I've been trying to get my OP5t working for a solid six hours straight, and I'm just about to loose my mind.
I'm sorry if this isn't the right place to post this. I've always just sorta lurked about in here.
Here's the deal for my OP5t.
Now I'm stuck in a situation where I can get my phone to boot on all of the OOS versions I've mentioned, but always without root. And If I do manage to get it booting, I end up loosing TWRP and having to reflash it through fastboot.
Since I've always just relied on Titanium backup (yes I know, how silly) I've never had any trouble restoring my backups, but since I've now lost root and being unable to obtain it again, I'm locked out of all my sweet app data. It's all a bit messy now, and I think I'm begging to repeat previous steps and combinations, but here's a list of what I've tried. I really hope some white knight comes to the rescue.
It all happened when I tried doing a clean flash wiping caches, data and system of OOS 5.0.3 (coming from the latest official OOS Nougat build). It all started when I tried to flash the magisk 15.3 after this boot, which resulted in ERROR 1.
- I've tried installing both the old version the previous nougat build and the two most recent stable oreo ones. Wiping thoroughly inbetween even, since at this point I have nothing left to loose.
- Whenever I try to flash magisk 15,1 /3 or 4 I get error 1. Whenever I try to flash supersu (s.82 included the modded SR5 version) I Just don't get root or end up in an endless +1 screen (before the spinner) for 12+ minutes.
- I've tried flashing the stock boot.img
- I've tried all of the above in combination with bluspark recovery 8.61 and 69 + the r100 kernel
- I've tried using codeworks cheesburger and dumpling recoveries
What am I missing here? I assume my phone is encrypted since it asks for a code to open TWRP.
I've never had any issues so grave that I couldn't just search my way through it, but this time I'm at my wits end, and just about ready to settle(tm) for no root.
I've never tried exporting a log, but I sense that I do that from TWRP and then grab it via a file manager from some folder?
Use codeworkx dumpling TWRP, dirty flash your ROM, boot it once, then reboot to recovery and flash Magisk 15.3. Should be all you need.
For Nougat, I think it's better to flash Magisk 14, on some ROMs.
New apps
Great information provided by many users. I have just joined this group and read many experts advice. Thanks
Latest SuperSU (beta 2.85 i believe) don't work on OP5T Oreo update (stable or Open Beta). Don't know why, but I had to use Magisk. ANd I must say, I'm pretty happy with it, too!
Elfomze said:
So, I've been trying to get my OP5t working for a solid six hours straight, and I'm just about to loose my mind.
I'm sorry if this isn't the right place to post this. I've always just sorta lurked about in here.
Here's the deal for my OP5t.
Now I'm stuck in a situation where I can get my phone to boot on all of the OOS versions I've mentioned, but always without root. And If I do manage to get it booting, I end up loosing TWRP and having to reflash it through fastboot.
Since I've always just relied on Titanium backup (yes I know, how silly) I've never had any trouble restoring my backups, but since I've now lost root and being unable to obtain it again, I'm locked out of all my sweet app data. It's all a bit messy now, and I think I'm begging to repeat previous steps and combinations, but here's a list of what I've tried. I really hope some white knight comes to the rescue.
It all happened when I tried doing a clean flash wiping caches, data and system of OOS 5.0.3 (coming from the latest official OOS Nougat build). It all started when I tried to flash the magisk 15.3 after this boot, which resulted in ERROR 1.
- I've tried installing both the old version the previous nougat build and the two most recent stable oreo ones. Wiping thoroughly inbetween even, since at this point I have nothing left to loose.
- Whenever I try to flash magisk 15,1 /3 or 4 I get error 1. Whenever I try to flash supersu (s.82 included the modded SR5 version) I Just don't get root or end up in an endless +1 screen (before the spinner) for 12+ minutes.
- I've tried flashing the stock boot.img
- I've tried all of the above in combination with bluspark recovery 8.61 and 69 + the r100 kernel
- I've tried using codeworks cheesburger and dumpling recoveries
What am I missing here? I assume my phone is encrypted since it asks for a code to open TWRP.
I've never had any issues so grave that I couldn't just search my way through it, but this time I'm at my wits end, and just about ready to settle(tm) for no root.
I've never tried exporting a log, but I sense that I do that from TWRP and then grab it via a file manager from some folder?
Click to expand...
Click to collapse
Same kind of problem here. After clean flashing Oreo can't root anymore. Flashing Magisk ends up in Bootloop. Tried various combinations of TWRPs and Magisk versions, no use. :/
Kunjuuuz said:
Same kind of problem here. After clean flashing Oreo can't root anymore. Flashing Magisk ends up in Bootloop. Tried various combinations of TWRPs and Magisk versions, no use. :/
Click to expand...
Click to collapse
Okay so I managed to figure it out. The problem seemed to be that where one TWRP version could flash magisk, another wouldn't be able to decrypt the phone properly, which I think is what caused the bootloops/non sticky root for me (though I'm by no means sure of this).
I managed to get it worked out by fiddling around a bit more with the different versions and using the a Remix ROM to remove the pin (which I probably should've done initially). I also noticed that I didn't originally pay attention to the fact that codeworks' (non universal) recoveries are aimed at 8.0 and 8.1 respectively, which might have complicated things a bit more for me.
Sorry for spamming up the thread. I hope you figure things out though
The latest SuperSu does not work with 8.1 for us and some other (or all other) 8.1 phones.
And... SuperSu is no longer in development.
Rumor has it a slightly older SuperSu version works in 8.1 but I never got around to trying it and forget the version # now.
And Lineage has not released a SuperSu/superuser for 8.1 yet.
It bums me out because I want that Magisk alternative.
Not a fan of Magisk yet.
Elfomze said:
Okay so I managed to figure it out. The problem seemed to be that where one TWRP version could flash magisk, another wouldn't be able to decrypt the phone properly, which I think is what caused the bootloops/non sticky root for me (though I'm by no means sure of this).
I managed to get it worked out by fiddling around a bit more with the different versions and using the a Remix ROM to remove the pin (which I probably should've done initially). I also noticed that I didn't originally pay attention to the fact that codeworks' (non universal) recoveries are aimed at 8.0 and 8.1 respectively, which might have complicated things a bit more for me.
Sorry for spamming up the thread. I hope you figure things out though
Click to expand...
Click to collapse
Locking the bootloader, wiping, and unlocking the bootloader again fixed the issue for me.
Hi, I'm replacing a lost Moto G3 TE with a Moto G5 (xt1671 dual sim) that should be coming in the mail on Monday. I'd like to do whatever mods I want to my phone right away, before activating my google account on it and everything. So, I'd really like any advice any of you can give as to preferred custom rom with root that I should put on my new phone, so I can get to it right away. I've already found the thread to unlock it (same process as in past mostly), and I've found the guides for putting on TWRP (either 32-bit or 64-bit). So, now I just need to decide which custom ROM to use. Please advise!
I've also had a Moto G2 in the past. I've unlocked and used custom roms and root on all my phones so far, from Cyanogenmod 12.1 to AOSP Extended, ViperOS, and LineageOS. My wife's Moto G2 has Oreo on it (through AEX) and we're enjoying it (I had her add me as an account until I get my new phone). So, I'd like to continue using an Oreo system if possible, and I'd even prefer AEX, but it seems that it's discontinued for the Moto G5. Is that correct?
My overall goals for a custom rom are, in order of priority: reliability, speed/performance, battery life, and customization options. I found that AEX balanced all of that well on our past phones. Is the discontinued AEX for this phone reliable, or not? I've also seen the LineageOS thread and the KAOSP thread and have glanced at a few others. I use google accounts and half their apps for sure (so I'll want to install a GApps package with it). And I see there's a possibility to unlock RAW/DNG files for the camera, which I'd really like to try (as I prefer raw file editing instead of JPGs). And the customizations I like (if still possible) are mainly involving the way the launcher responds - I like having the navigation buttons hide, or to swipe up to get them back, I like being able to modify the status bar, etc.... typical customizations that were usually available in AEX that I've used. I also use root for file explorer and a few other functions - I used to always use SuperSU in the past, but just recently started using Magisk (on the Moto G2) and it seems good, though I'm open to any recommendation about which root to use.
So, please fire away! Please give your suggestion as to which currently available custom ROMs are stable, have good performance, good battery life, and offer standard customization, plus which I can root. I appreciate any suggestions and any advice you can give, especially regarding if there's a recommended rom but if it has known issues and any known workarounds. Also, I'd appreciate advice anytime today or tomorrow (since it'll likely be the afternoon or evening of Monday +3 GMT time - Madagascar - that I'm able to start working on unlocking it, installing custom recovery, etc.). But even if the advice is late, I might still be able to use it. I know this is a bit much to ask, but please give your own opinions freely!
Oh, by the way, do I need updated Motorola drivers, or will the motorola drivers and adb/fastboot I installed last time (for the Moto G3 TE) keep working with the new phone? The unlock thread I've found here doesn't say anything about motorola drivers or adb/fastboot. Thanks in advance!
the best stable rom is stock rooted
woozie.2007 said:
the best stable rom is stock rooted
Click to expand...
Click to collapse
Thanks for the response! Is there a stock oreo available? And is stock rooted still customizable (like with AEX or something - can I install some sort of thing to let me customize it more?). And is there a debloated version of the stock rom available? I saw one thread on here about a debloated stock rom, but it looked like it was still nougat.
If it's possible to customize the stock rom further, please point me in the right direction. And if not possible to customize it further... then are you suggesting that any of the custom roms available aren't very stable to be used well for a daily driver?
Again, thanks for your response and also for any more feedback you can give!
So, I have my phone now and it came with stock Nougat. I've unlocked it, and I'm currently working on getting TWRP, Dm-verity thing on it, and then magisk. After that can I still update it to Oreo or not? Please advise. Thank you!
madagascaradam said:
So, I have my phone now and it came with stock Nougat. I've unlocked it, and I'm currently working on getting TWRP, Dm-verity thing on it, and then magisk. After that can I still update it to Oreo or not? Please advise. Thank you!
Click to expand...
Click to collapse
no, you have to update oreo first, after that install twrp and magisk for root it
woozie.2007 said:
no, you have to update oreo first, after that install twrp and magisk for root it
Click to expand...
Click to collapse
Crud, that sucks! I was already finished rooting and everything on magisk, then I let the OTA update download and when it restarted my phone, it just automatically sends it into recovery (TWRP) every time now! I tried to install this TWRP stock Oreo (dirtying flashing it) hoping it would fix the boot-loop-to-TWRP-recovery problem, but it didn't. So now I need to figure out a way to get back to the original, so I can start over and try again.
I'm trying to do a factory reset and try again, but in TRWP it says ""Failed to mount '/data' (Device or resource busy)'" This sucks! Any ideas where I can go or what I can do (such as some fastboot commands or something) to get it all working again?
EDIT: It does reboot to bootloader though, so it's not hardbricked. Just need to figure out what to do from here. Thanks for any help!
try to flash via fastboot only boot, recovery, oem and system from oreo, then aply update, then root
Thanks! I downloaded the firmware (for latest Nougat) from this thread: https://forum.xda-developers.com/g5/development/stock-upgrade-to-official-stock-oreo-8-t3823598
Then I flashed everything they said through fastboot (ignoring the modem stuff) because I'm still downloading the oreo firmware right now anyway (my connection is quite slow). At first the bootloader got stuck and said "error" and I was freaking out thinking I'd hard-bricked it. But I turned it off and on again anyway and it loaded fine back into nougat for that latest version.
So now I'm downloading the latest stock Oreo and I'll probably try to ADB sideload it.
Which root do you recommend? I have the Magisk I did for nougat that worked great - 11.6 But there's this thread here (https://forum.xda-developers.com/g5/how-to/guide-how-to-root-stock-oreo-8-1-soak-t3832347) that talks about what seems like a complicated way of doing Magisk 15.3 and then getting it up to 16. What do you suggest?
magisk 17.1 its ok, but you have to flash only partition that i said, not full firmware, and DONT flash the bootloader and GPT partition
---------- Post added at 06:11 PM ---------- Previous post was at 06:10 PM ----------
better let the phone to update ota for latest security patch, dont flash via fastboot
OK, I installed the stock oreo through ADB sideload (it wouldn't read my storage for some reason).... then I reinstalled TWRP, no problem... then installed Magisk 17.1 (per your suggestion) and then the apk for the manager. Everything's working great! Didn't even need that dm-verity thing.
I'm still looking into the mods I can do to it now that it's rooted (such as changing boot logo and boot animation, adding that 'camera 2' setting, etc.) So I'm not sure I'm at a finished product yet, but I'm definitely at a stable rooted oreo with all my regular stuff installed, so that's a good place to start! I've made a nandroid backup here in case any of my further experimenting messes it up.
Thanks again for your help! And if you can give any suggestions towards the best way to customize the look (for example - is nova launcher still the best way to do that?) or other aspects of the system UI, while still being on this stock rom, then please let me know. I'll look up how to get that better camera mode working.
woozie.2007 said:
magisk 17.1 its ok, but you have to flash only partition that i said, not full firmware, and DONT flash the bootloader and GPT partition
---------- Post added at 06:11 PM ---------- Previous post was at 06:10 PM ----------
better let the phone to update ota for latest security patch, dont flash via fastboot
Click to expand...
Click to collapse
Could you help me with this: if I backup my system (everything) with TWRP.... can I then switch to a custom rom to try it out (in case I want a different user interface, more tweaks, etc.) and if I don't like it can I easily switch back to the stock rom nandroid backup I have saved in TWRP (thus restoring my previous state, but without having to start from factory reset)? Or would it be difficult to switch back - like would I have to redo it through fastboot or something and factory reset, etc.?
I'm asking because in the past I never used the stock rom much and I definitely never switched between a custom rom and the stock rom. Once I went for custom rom, I didn't go back - so I don't know if it's as simple as restoring a nandroid backup or if it's much more effort. Please let me know. Thanks a lot!
you must be very carefully because most of the custom roms need twrp on 64 bits, now you have official twrp 32. When you come back from custom roms 64bit to previous nandroid backup, you must install 32 bits twrp, otherwise you may lose the imei of the phone, just read very well when you want to do something risky
woozie.2007 said:
you must be very carefully because most of the custom roms need twrp on 64 bits, now you have official twrp 32. When you come back from custom roms 64bit to previous nandroid backup, you must install 32 bits twrp, otherwise you may lose the imei of the phone, just read very well when you want to do something risky
Click to expand...
Click to collapse
OK, thanks a lot for that helpful info! So just to clarify to be sure: basically, if I want to switch back and forth, I'll install the 64-bit twrp first, then the custom rom(s). Then if I want to come back to my stock image backup, I re-install the 32-bit twrp (like the one I'm currently using) and then I can just restore my nandroid backup I took of the stock and all is well? And it's not risky if I do it like that?
yes, its correct that
I'm having issues with certain "secure" apps not working on Pie with Magisk after updating from Oreo (Google Pay in stores, Zelle, Chase, etc.) even though safetynet and everything else checks out perfectly. I'm thinking about doing a clean install but I'm not sure what's causing the issue and I'd like to avoid it again if at all possible... I followed a guide on XDA and everything works right except for this issues and the only things different from when I was on Oreo are:
* Installed TWRP instead of just fastbooting into it for flashing
* Installed Sultan's kernel, per the guide (not 100% sure how to get back to stock on that either, unless it'll happen when flashing the update from Google)
I think everything else was the same, other than updating Magisk from 16.1 to 18.0 (and later downgrading to 17.2 after reading that 18 had some issues with hiding). Anyone have a similar issue and found a solution or have advice on troubleshooting? I'm planning on trying a fresh install and only fastbooting into TWRP to install Magisk instead of installing it, and staying on the stock kernel to see if that helps but trying to avoid bricking my phone too.
Thanks
Join the crowd... It's been a few weeks since this started. There are a few work around methods but they don't seem to be consistent or permanent. Most are just waiting until magisk gets updated to fix whatever Google did to detect modified systems.
Just curious if anybody has some insight here...
I have a XT1710-09 which I have unlocked the bootloader and went to Lineage, only to find that the moto mods I use aren't working. So I've reverted back to the stock ROM. Everything works, but if I try and flash any version of Magisk (17.3 through 19), my phone will boot loop. I have tried the below items, but they all result in a boot loop:
https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
I can recover from the bootloop by reflashing the boot.img, but I obviously don't have any modification support. I've also noticed the boot.img seems to overwrite my TWRP install on the first boot when applying the encryption.
My phone is currently being flashed with ALBUS_OPS27.76-12-25. Does anybody have any guidance on getting this working? Sadly, I want to get the AAC codecs installed, otherwise my bluetooth system keeps falling back to sbc. Worked great in Lineage, but I have too many moto mods that wouldn't work (including the JBL and Hasselblad).
Thanks!
Are you sure you executed the two commands for keeping force encrypt and keep dm-verity before flashing on TWRP terminal? Because the only reason Magisk ever gives me bootloop on stock is because it automatically sets keep force encrypt, but not the other one.
And of course use v19