Good afternoon! I would like to have some help on how to install custom roms on my phone. I know the essentials since i've already installed custom roms on various devices but each one has it's own procedure and i am a bit confused with the Axon 7. XDA has many threads and i don't know which ones to follow to unlock the bootloader and install TWRP. As said before i have an A2017G and it's currently running Nougat V1.2.0B10. Any help would be appreciated.
A rom recommendation would also be good. Im looking for a (preferably oreo) stable, clean, with good battery life and sound quality (is the AKM DAC used on the custom roms??) rom.
Lastly i would like to know what is Bootstack and Modem is. I see these things all over the Axon 7 XDA forum but i don't know what they are ;-;
Sorry for bad english
Thanks in advance
João Candeias
joaocandeias said:
Good afternoon! I would like to have some help on how to install custom roms on my phone. I know the essentials since i've already installed custom roms on various devices but each one has it's own procedure and i am a bit confused with the Axon 7. XDA has many threads and i don't know which ones to follow to unlock the bootloader and install TWRP. As said before i have an A2017G and it's currently running Nougat V1.2.0B10. Any help would be appreciated.
A rom recommendation would also be good. Im looking for a (preferably oreo) stable, clean, with good battery life and sound quality (is the AKM DAC used on the custom roms??) rom.
Lastly i would like to know what is Bootstack and Modem is. I see these things all over the Axon 7 XDA forum but i don't know what they are ;-;
Sorry for bad english
Thanks in advance
João Candeias
Click to expand...
Click to collapse
-Use EDL Tool to unlock and install TWRP (3.2.1-0), or if it fails use Controllerboy's guide
-For Oreo you have AEX from NFound, or RR-O from Kranoner (on the Hellsgate kernel thread). Don't know about the others.
AEX has awesome sound, don't know about RR but it probably also has good sound.
-Bootloader and modem are the things you have to flash BEFORE flashing the ROM. The bootloader is the thing that basically initializes the system, and the modem file is the modem firmware. You need the Universal B15 bootloader for N custom ROMs or sometimes you can use the B09 bootloaders from Raystef66 (But don't, it's not needed really).
Bootloaders are usually universal, i.e. they work for the G, U and chinese. Modem files are specific for each model.
There are also Bootstacks which are sometimes bootloaders bundled with the specific modem for your phone. But sometimes they are just bootloaders named as bootstacks for some reason. Just read the ROM thread, it should say "flash modem, flash bootstack".
And for Oreo you have NFound's Bootstack which is basically an AROMA zip that contains the 3 modems, so you can select which one you want. The downside is that the zip is about 250 or 300 mb in size.
The latest Oreo bootstack I know is B32+B10 bootloader by nfound. That one supposedly has fixes from the Chinese Oreo build, which mostly fix audio (But audio was already awesome on AEX-O, I'm pretty sure the DAC was already working fine).
joaocandeias said:
Good afternoon! I would like to have some help on how to install custom roms on my phone. I know the essentials since i've already installed custom roms on various devices but each one has it's own procedure and i am a bit confused with the Axon 7. XDA has many threads and i don't know which ones to follow to unlock the bootloader and install TWRP. As said before i have an A2017G and it's currently running Nougat V1.2.0B10. Any help would be appreciated.
A rom recommendation would also be good. Im looking for a (preferably oreo) stable, clean, with good battery life and sound quality (is the AKM DAC used on the custom roms??) rom.
Lastly i would like to know what is Bootstack and Modem is. I see these things all over the Axon 7 XDA forum but i don't know what they are ;-;
Sorry for bad english
Thanks in advance
João Candeias
Click to expand...
Click to collapse
Follow this guide.
You can't get wrong if you follow the guide posted by Oki. I did it myself and I feel quite happy with the result.
Thanks everyone!! Very appreciated
Oki said:
Follow this guide.
Click to expand...
Click to collapse
Do i really need to downgrade to Marshmallow before installing TWRP and unlocking the bootloader? If so, how can i do that?
joaocandeias said:
Do i really need to downgrade to Marshmallow before installing TWRP and unlocking the bootloader? If so, how can i do that?
Click to expand...
Click to collapse
not using that guide and using EDL Tool directly?
No offense @Oki , in fact I used that guide to unlock, but there are new methods available, and not like axon7toolkit that were pretty hardcoded and depended on you having fastboot. EDL Tool is the best way right now.
Beside that, I think you don't need to downgrade. Check WesTD's guide "Unlock bootloader easily", it's roughly the same procedure but i think he doesn't mention downgrading there
So, i used EDL Tool to unlock the bootloader and install TWRP and everything went fine. I actually managed to get oreo running on my phone, but i had problems with both AEX and RR. First i tried AEX and it was working good, pretty stable actually but i only had sound on headphones. Since every phone is unusable without sound i tried another solution: Flash RR.... But that created a bigger problem, it wouldn't even boot lol. It gave me a bootloop.
After that i flashed LOS14.1 for a quick fix, because i didn't had much time to search and fix the AEX bug. This is quite strange because afaik no one had these problems, so i suppose i did something wrong.....
Choose an username... said:
not using that guide and using EDL Tool directly?
No offense @Oki , in fact I used that guide to unlock, but there are new methods available, and not like axon7toolkit that were pretty hardcoded and depended on you having fastboot. EDL Tool is the best way right now.
Beside that, I think you don't need to downgrade. Check WesTD's guide "Unlock bootloader easily", it's roughly the same procedure but i think he doesn't mention downgrading there
Click to expand...
Click to collapse
Do you have a link to that guide? It would save a lot of time to many people.
Oki said:
Do you have a link to that guide? It would save a lot of time to many people.
Click to expand...
Click to collapse
you can literally google it... "unlock bootloader easily", "dfu unbrick", "edl tool"...
Choose an username... said:
you can literally google it... "unlock bootloader easily", "dfu unbrick", "edl tool"...
Click to expand...
Click to collapse
You know what to search for, newbies don't. This is why it is always better to provide a link. I was just trying to make life easier for people without our experience.
Oki said:
You know what to search for, newbies don't. This is why it is always better to provide a link. I was just trying to make life easier for people without our experience.
Click to expand...
Click to collapse
I know what to search for but I also said the name of the guide there. I guess I'll post the links anyways, but it's as easy as googling the guide's name...
https://www.google.com.ar/url?sa=t&...BBAB&usg=AOvVaw10p1GREikMBe89R4S0cikD&cf=1
I think i figured out why RR didn't boot on my phone. Apparently it's encrypted, (encryption isn't working on oreo roms right??) but just don't know how and why... I didn't encrypted it manually. I never done it in my life actually and i can't decrypt it now any help?
joaocandeias said:
I think i figured out why RR didn't boot on my phone. Apparently it's encrypted, (encryption isn't working on oreo roms right??) but just don't know how and why... I didn't encrypted it manually. I never done it in my life actually and i can't decrypt it now any help?
Click to expand...
Click to collapse
Yes, format data
Choose an username... said:
Yes, format data
Click to expand...
Click to collapse
Still recommended to flash root also when flashing ROM?
ZTE Axon 7 A2017U, AospExtended v4.6 ROM, microG (NoGapps), Multiboot, Tapatalk 4.9.5
marcdw said:
Still recommended to flash root also when flashing ROM?
ZTE Axon 7 A2017U, AospExtended v4.6 ROM, microG (NoGapps), Multiboot, Tapatalk 4.9.5
Click to expand...
Click to collapse
Ofc
Neve
Choose an username... said:
Yes, format data
Click to expand...
Click to collapse
I already tried that and it didn't work..... How did the phone encrypted itself?
Edit: Nevermind, I don't need any more help on this subject
Related
So i'am getting my Axon 7 in some days.
I don't really wanna stay stock, but also dont want to run any unstable rom.
So i was thinking about flashing RR + A.R.I.S.E..
Can you recommend me any rom, kernel, mod?
And are there any rom compatible restrictions for the different models?
thx
Hmm i recommend you stock because when you switch to custom you will not get full Axon 7 experience (especially audio) you will not get 100% audio in custom like in stock. Stock isn't bad - nearly like clean Android despite may 2 or 3 APS that you can disable in system. Said far I have Axon since December and firstly I want to switch to custom but I will if Axon will not get Oreo and custom will have Oreo. So as far - most stable and usefully in everyday use is stock.
MrMD69 said:
Hmm i recommend you stock because when you switch to custom you will not get full Axon 7 experience (especially audio) you will not get 100% audio in custom like in stock.
Click to expand...
Click to collapse
Okay, thx.
So you are full stock or have you any kernel or mod installed?
OverBit said:
Okay, thx.
So you are full stock or have you any kernel or mod installed?
Click to expand...
Click to collapse
Hope you got an A2017U - both the G and chinese versions don't have any kernels made for them. I'd also advise staying on stock. There's a Dual boot patcher, seems like a good idea if you want to run another OS besides stock.
But I tell you, no other ROM runs like Stock does right now. and it's been more than a year since they launched the phone, so at least until Android O launches I wouldn't expect that to change
Choose an username... said:
Hope you got an A2017U - both the G and chinese versions don't have any kernels made for them.
Click to expand...
Click to collapse
I am living in Germany, so i think i wont get the 2017U right?
OverBit said:
I am living in Germany, so i think i wont get the 2017U right?
Click to expand...
Click to collapse
Nope, you're getting the A2017G
I have one, and besides the lack of kernels, I can't complain really. It works.
Choose an username... said:
Nope, you're getting the A2017G
I have one, and besides the lack of kernels, I can't complain really. It works.
Click to expand...
Click to collapse
I think i can live without a custom kernel.
Then i think i wont even root, because unlocking bootloader looks kinda messy to me.
Still have my Nvidia Tab's to play around with so the Axon 7 can stay completly stock.
OverBit said:
I think i can live without a custom kernel.
Then i think i wont even root, because unlocking bootloader looks kinda messy to me.
Still have my Nvidia Tab's to play around with so the Axon 7 can stay completly stock.
Click to expand...
Click to collapse
It's not that messy if you use Controllerboy's guide or maybe axon7toolkit (it should do it all by itself)
Choose an username... said:
It's not that messy if you use Controllerboy's guide or maybe axon7toolkit (it should do it all by itself)
Click to expand...
Click to collapse
And they are completely compatible with the 2017G? (sry just saw it in the thread)
Sry for all that noob questions, but all my device i justed before just hadn't different models.
And rooting should break ota's right?
OverBit said:
And they are completely compatible with the 2017G?
Sry for all that noob questions, but all my device i justed before just hadn't different models.
And rooting should break ota's right?
Click to expand...
Click to collapse
They are. Actually the guide is ONLY for the A2017G.
And OTAs are broken out of the box but you just download the official ZIP and put it on the root of the internal storage or the SD and go to Updates, and it does the process just like an OTA. You can also do this to upgrade or downgrade to MM, even if your device is fully stock, locked bootloader and everything
I live in France and bought mine with Amazon from Germany. So it's a G model. Stock works fine and I think you really don't need to root this device. I've only change the launcher by Nova which brings a much better user experience.
Tapatalk--->ZTE Axon 7 Nougat 7.1.1 stock
Stock is much better than LOS, OR or Nuclear. I am trying to get back to Stock.
satish.yarramsetti said:
Stock is much better than LOS, OR or Nuclear. I am trying to get back to Stock.
Click to expand...
Click to collapse
Well if you want to get back the best way is to drop an official full update zip from ZTE on the internal storage, use a flashable recovery zip like those tron1 makes, then use TWRP's reboot to recovery button, and flashing that update zip through there.
My way to RR was the bad battery and sot on stock. I got 4 hrs but that's not enough for me.
Choose an username... said:
They are. Actually the guide is ONLY for the A2017G.
And OTAs are broken out of the box but you just download the official ZIP and put it on the root of the internal storage or the SD and go to Updates, and it does the process just like an OTA. You can also do this to upgrade or downgrade to MM, even if your device is fully stock, locked bootloader and everything
Click to expand...
Click to collapse
Then i think i will root.
To unlock bootloader and flash TWRP with the Toolkit.
1. Do i have to dowgrade to mm to use the toolkit or should it work with latest OTA?
2. Can i still flash the Updates with twrp?
OverBit said:
Then i think i will root.
To unlock bootloader and flash TWRP with the Toolkit.
1. Do i have to dowgrade to mm to use the toolkit or should it work with latest OTA?
2. Can i still flash the Updates with twrp?
Click to expand...
Click to collapse
1. Just try to use it. I expect it to workk, but never used it myself. Better ask @bkores
2. Usually you can, the best way is to flash tron1's flashable OTAs (if you have TWRP) cause he gets rid of the recovery file though. If you try to flash an official zip with TWRP it might work (i flashed full B04), but TWRP will get replaced with the official recovery. You just flash it again
1) Stay STOCK
2) Avoid completely unlock the phone, root, etc etc
3) Buy a U (American) version
4) Stay STOCK !!!
Altomugriento said:
1) Stay STOCK
2) Avoid completely unlock the phone, root, etc etc
3) Buy a U (American) version
4) Stay STOCK !!!
Click to expand...
Click to collapse
por?
Will putting Magisk on My ZTE A2017G with unofficial Lineage 14.1 get passed Safety net and allow me to use apps like Android Pay?
Sent from my ZTE A2017U using Tapatalk
The latest stable version of Magisk (14.0) works fine for me on LineageOS 14.1 and also passes SafetyNet, so the answer is YES. (But I don't know for certain about Android Pay because I don't use it!)
P650SE said:
The latest stable version of Magisk (14.0) works fine for me on LineageOS 14.1 and also passes SafetyNet, so the answer is YES. (But I don't know for certain about Android Pay because I don't use it!)
Click to expand...
Click to collapse
Great thanks for the info I'm just looking at the guide to install it and I don't understand how to do the bit with stock boot image?
Supersilver-Haze said:
Great thanks for the info I'm just looking at the guide to install it and I don't understand how to do the bit with stock boot image?
Click to expand...
Click to collapse
I am not sure what you mean to be honest, where did you see about this? I know when you install LineageOS you have to flash the B15 Universal Bootloader first in TWRP, and you should also flash the Android N modem; both of which are supplied in the Official LineageOS discussion thread. You can then proceed with flashing the ROM and OpenGApps, followed by Magisk 14.0 and anything else you'd like to install before rebooting.
P650SE said:
I am not sure what you mean to be honest, where did you see about this? I know when you install LineageOS you have to flash the B15 Universal Bootloader first in TWRP, and you should also flash the Android N modem; both of which are supplied in the Official LineageOS discussion thread. You can then proceed with flashing the ROM and OpenGapps, followed by Magisk.
Click to expand...
Click to collapse
Yea I've actually done all that and got it working with a bit of stress involved it's just this part in the guide for Magisk "However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN" if you know how to do that bit would be great haha but if not thanks for your help P650E
Supersilver-Haze said:
Yea I've actually done all that and got it working with a bit of stress involved it's just this part in the guide for Magisk "However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN" if you know how to do that bit would be great haha but if not thanks for your help P650E
Click to expand...
Click to collapse
No worries. I don't think you need to worry about anything like that. The usual procedure is just to download Magisk from the link in the official thread on XDA, copy it to the internal storage on the Axon 7 and then flash it in TWRP. It isn't necessary to do anything else, like the stuff you copied above.
P650SE said:
No worries. I don't think you need to worry about anything like that. The usual procedure is just to download Magisk from the link in the official thread on XDA, copy it to the internal storage on the Axon 7 and then flash it in TWRP. It isn't necessary to do anything else, like the stuff you copied above.
Click to expand...
Click to collapse
Oh well that's embarrassing :laugh: just got the zip and flashed like you said everything working perfectly including Android Pay I can't thank you enough :highfive: hope you enjoy the rest of your day and thanks again
Supersilver-Haze said:
Oh well that's embarrassing :laugh: just got the zip and flashed like you said everything working perfectly including Android Pay I can't thank you enough :highfive: hope you enjoy the rest of your day and thanks again
Click to expand...
Click to collapse
Haha, that's quite alright. Feel free to let me know should you have any further problems with the Axon 7. I'm a new owner but have a lot of experience with previous Android devices such as the LG G4 and OnePlus One.
P650SE said:
Haha, that's quite alright. Feel free to let me know should you have any further problems.
Click to expand...
Click to collapse
Ah I know this is a bit fast to be asking about another problem but I just literally found out that I can't make or receive calls on Lineage I can send and receive texts and use data but no calls
Edit: disregard the I figured it out I had it permanently on LTE so I wasn't able to make or receive calls on LTE it seems
Sent from my ZTE A2017U using Tapatalk
Supersilver-Haze said:
Ah I know this is a bit fast to be asking about another problem but I just literally found out that I can't make or receive calls on Lineage I can send and receive texts and use data but no calls
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
Hmm, i'm not sure about that one because I didn't use the phone for making calls when I was running LineageOS on my Axon 7. If you installed the Android N modem before flashing the ROM it should work fine in theory. Maybe you can find someone else in the LineageOS thread who's having the same issue.
Does viper4android through magisk work for you. I keep getting error and then magisk force closes
FuzzyDunlop9 said:
Does viper4android through magisk work for you. I keep getting error and then magisk force closes
Click to expand...
Click to collapse
I also had problems getting Viper4Android to work on this device. For me it would install fine, but the audio effects made no difference in apps like Spotify and YouTube, despite having the deep-buffer fix enabled. Try using this version by ahrion instead, it works for me! (Just make sure you remove anything relating to previous installations of V4A beforehand!)
Hello again, I put the question on the forum but doesn't seem like anyone is answering, do you know the process of going from unofficial lineage to official and should I?
Sent from my ZTE A2017U using Tapatalk
Supersilver-Haze said:
Hello again, I put the question on the forum but doesn't seem like anyone is answering, do you know the process of going from unofficial lineage to official and should I?
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I don't know how much difference it would make, but installing the Official build of LineageOS is probably slightly better. The method of switching from Unofficial to Official is basically the same as what I posted previously in your other discussion thread:
1. Make sure your apps and files from Unofficial LOS are backed-up.
2. Download the Official LOS ROM and copy it to either the internal or expandable SD card storage on the Axon 7.
3. Download the latest GApps arm64 ZIP for Android 7.1 from OpenGapps and copy it to either the internal or expandable SD card storage on the Axon 7.
4. Reboot the phone into TWRP custom recovery.
5. Enter the 'Wipe' menu and wipe the partitions /data, /system, /dalvik and /cache. (It might not be 100% necessary to wipe /data since you're just switching to an official build of the same ROM, but it is still advisable. You could try installing the ROM without wiping /data, but you may encounter some issues!)
6. Switch the the 'Install' menu and flash Official LOS, followed by the OpenGApps ZIP.
7. Reboot the device.
I have the habit of always asking on a new device no matter how much I think I know!
I have an xt1635-02 (I am US ATT Prepaid)(nano SIM) supposedly here tomorrow so I've been reading tons here.
However, it seems that a lot of the threads are aimed at rooting stock, which I never do.
As a rule, it's trivial:
[!] In this case it seems best to OTA update stock to 7.1.1 if it isn't already. I believe bootloader must be 7.x.x for doing custom Oreo ROMs . Since mine was 6.0 it took about 8 updates OTA and maybe 2 hours(wifi) .
[!]I go to moto site and do the unlock bootloader dance (already carrier unlocked supposedly).
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
[!]Then flash twrp-3.2.1-0-addison.img (Alberto97) using fastboot on my PC. (Ubuntu 17.10 dev 18.04 with adb and fastboot)(dual boot win7)
I do this twice in a row as I have experienced it not working the first time (dead android LOL).(OCD much??? )
https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629
- - -
[!] -->then flash Alberto's verity patch mentioned at the top of his TWRP thread
https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629
This modifies stock. Else your backups of stock won't boot. Learned this the hard way!
- - -
[!]Then use TWRP to backup (default settings) stock a couple of times and put copies of both on PC (via USB on stock).(or if for some reason my USB-C doesn't work, via wifi to my router using filezilla FTP and phone app: "wifi file transfer" by "DNL Media UG"(needs permission storage=on..) - I had to redo this twice - redo this twice - kept dropping back to stock recovery.
[!]Then flash the boot logo using fastboot on PC - I usually use TWRP for this but these that I found here are not set up to be TWRP flash compat so will just remove bin from zip and flash using PC. I think I have about 4 possibilities that I found on these threads. Nice! Easy.
[!]Then boot to TWRP and flash Alberto97's AOSP 8.1 arm64 ROM. Why that ROM you may ask. Been using mainly that Alberto97 ROM on my Moto G3 (32bit version of course), and love it. There's plenty of time to try all the others!!!
I usually consider 2 root options; SuperSU 2.82-SR5, or majisk 1520. (for future readers, these are the latest at this time.)(besides I'm very used to them.)
With SuperSU I have had no probs wiping all 4(Dalvik/ART, system, data, cache), flash ROM, flash 8.1 gapps, flash SUperSU, and boot to install.
With majisk I have sometimes had troubles during install if I flash majisk in the first batch so I tend to wipe all 4, flash ROM and gapps, and boot to install. Then when I finally hit desktop, boot back to TWRP and flash 1520 and reboot.
I need root to use TBPro - no restoring on first time with this 64bit ROM- got to do it the hard way!
SO I believe that's it, but if anyone sees a flaw or problem in there, I would appreciate your help.
Thanks!!!
yep look right, i would have added backup EFS and Modem partitions, if you want to be completely safe.
For now, open gapps 8.1 are only unofficial, i would feel a bit unsecure to use that, but it's only me.
fablebreton said:
yep look right, i would have added backup EFS and Modem partitions, if you want to be completely safe.
For now, open gapps 8.1 are only unofficial, i would feel a bit unsecure to use that, but it's only me.
Click to expand...
Click to collapse
Merci! Many thanks for looking in!!!
Yes, forgot to add that - did much xda search on the efs thing and best I found seemed to be a twrp-3.1.1-0-EFS-addison.img which I may very well flash first and do that since no other TWRP that I looked at offers backup efs. Official and squid2 derived (G3) don't. I assume Alberto's doesn't. Seems like I did it very manually on the G3. If you have it it's a pretty good guarantee that you'll never need it! (Murphy axiom)
As to unofficial gapps, I've been testing about 5 different 8.1 ROMs on the Moto G3 over the past couple months and if the gapps aren't built in to the ROM(some pixelexperience roms), all you can get is an unofficial gapps, or do a minor simple hack to an 8.0 so it will accept it. Usually devs will include it. Bless Alberto97 for not including it so I can select my own!!! But I've had no prob with gapps. Open gapps project has 8.0, but of course they won't work on a true 8.1 unless minor hack. I was planning on using open_gapps-arm64-8.1-aroma-20180109-UNOFFICIAL.zip (from https://cloud.kenzoroms.club/?dir=opengapps) unless you have a better idea. I wanted to grab camera from aroma(somebody's idea), but I also have about 5 other cameras and gcams waiting on the Sdcard that I want to test, simply because there seemed to be disagreement on what works on Alberto's new 8.1 build, so wanted to be able to report.
Thanks again!
backup efs / adb way : https://www.reddit.com/r/oneplus/comments/2zq0ff/friendly_reminder_back_up_your_efs_partition_if/
fablebreton said:
backup efs / adb way : https://www.reddit.com/r/oneplus/comments/2zq0ff/friendly_reminder_back_up_your_efs_partition_if/
Click to expand...
Click to collapse
Thanks for great link! yeah I think I used adb as well as an app last time. I'll add recovery this time so that's 3 backups on internal storage (and copied to PC) should be enough! (yes dear readers I am serious about this - 3 times! They are so tiny! And that pretty much guarantees I'll never need it, but if I do, it's childs play to get it back.)
Thanks!!!
If you're wondering about the delay, they sent me a -01 (Droid)(Murphy's law), so they paid for a UPS next day air label back to them(mailed at 4PM) - don't know if I'll get this going before Sat! Oh well!!! Never take these things too seriously!!! Gotta be costing them a chunk! I did briefly turn it on and stuck the SIM in it and it did show LTE on my ATT, but there's a few bands missing that are on the -02, so will wait. Pretty display, though!!! Really looking forward to it!!!
KrisM22 said:
If you're wondering about the delay, they sent me a -01 (Droid)(Murphy's law), so they paid for a UPS next day air label back to them(mailed at 4PM) - don't know if I'll get this going before Sat! Oh well!!! Never take these things too seriously!!! Gotta be costing them a chunk! I did briefly turn it on and stuck the SIM in it and it did show LTE on my ATT, but there's a few bands missing that are on the -02, so will wait. Pretty display, though!!! Really looking forward to it!!!
Click to expand...
Click to collapse
Good plan on sending it back. You would have been SOL trying to root the -01
dandrumheller said:
Good plan on sending it back. You would have been SOL trying to root the -01
Click to expand...
Click to collapse
Yes! I learned about 5 or 6 phones ago NOT to re-invent the wheel!!!
KrisM22 said:
Yes! I learned about 5 or 6 phones ago NOT to re-invent the wheel!!!
Click to expand...
Click to collapse
Okay, refund for that and order another from somebody else! Next week...!
The only thing is no moto mods on non stock (any thing past 7.1.1 or aosp) roms
punkerEVO said:
The only thing is no moto mods on non stock (any thing past 7.1.1 or aosp) roms
Click to expand...
Click to collapse
yes. stock 8.x is a no-no. This one that is coming is 6.0.1 So I will let it ota update to 7.1.1 after giving it a thorough check-out, then try unlocking it, etc. Sound right? I have no interest in any of the hardware-type addons, just the plain phone 3/32 octacore etc. Why this one? - I love the reception (radio) strength of Motos, plus a ton of other things. I stick with them. Plus it's all Albeto97's fault for deving on AOSP 8.1
Lol Alberto97's roms are buttery smooth!
punkerEVO said:
Lol Alberto97's roms are buttery smooth!
Click to expand...
Click to collapse
I think they are. He recently came out with an 8.1 AOSP version for the Moto G3 and I love it. I test others, but that's my daily driver. Sure not perfect, but quite good enough for me!!! So I figure when I get it (Tues?) that's what I'll put on it. There's always plenty of time to test others!
Okay, since I am waiting for phone (Tues) , obviously I am worried about "what-if"s and so researching on what to do, "if".
I succeeded in finding a nice zip for 7.1.1 with the Nov security patch
https://firmware.center/firmware/Motorola/Moto Z Play/Stock/
(I am US)(there are many others at that nice site!!!)
That took a lot of time.
Then I needed to be sure that I could get RSD lite to run, and tried and tried to no avail to get it to recognize my phone (even on my laptop) (I was testing with an old Moto G3 stock zip and my G3 phone) before some post gave me a version number much higher than at the RSD site. google gave me:
http://rsdlite.en.lo4d.com/
version 6.2.4, which worked perfectly.
I really need to write a short guide on this stuff - feels like I'm re-inventing the wheel, even though many folks have written much before I came along!
The reason for the above two is that for a while the last few days I kept running into folks who had taken 7 OTA and wound up with a bricked phone. So, yes, I just did a search for "brick" on xda in moto z play and will start reading them! LOL
Quick EDIT: I think I am wrong in that brick assumption - the first 3 I looked at involved encryption and 2 downgrades to MM (which is a no-no). I will read further.
edit2 - nevermind - most are downgrading to MM. Wish folks would just ask before doing that. That is a no-no of most (all?) phones. -
Hi,
Please share your camera result using Alberto97's roms. I some ROM but i dont like camera result, i think stock ROM still better in camera.
Thank You
wakhidnusa said:
Hi,
Please share your camera result using Alberto97's roms. I some ROM but i dont like camera result, i think stock ROM still better in camera.
Thank You
Click to expand...
Click to collapse
YES! Will do. I have about 5 cameras that I want to try though I will stop at the first one that works. Phone should be here today.
wakhidnusa said:
Hi,
Please share your camera result using Alberto97's roms. I some ROM but i dont like camera result, i think stock ROM still better in camera.
Thank You
Click to expand...
Click to collapse
I have no problem with various cameras getting good image, but sometimes on still first pic doesn't save. ( tried camera MX and Professional camera hd. I'm sure lots work about the same.)
Forgot to flash Alberto's verity patch right after flashing TWRP. So I had to RSD lite 7.1.1 Nov 1 and start over - no big deal! OP corrected.
Hello Kris,
I would like to ask for a link where I can download a working RSD so I can unlocked my bootloader.
Thanks
jeprox said:
Hello Kris,
I would like to ask for a link where I can download a working RSD so I can unlocked my bootloader.
Thanks
Click to expand...
Click to collapse
link to 6.2.4 is in the first post of
https://forum.xda-developers.com/moto-z-play/how-to/guide-rsd-lite-mini-guide-t3740641#post75334194
Hi everyone,
I'm tired of Lenovorola's poor update schedule and have decided to flash any of the latest (stable) custom ROM from the threads here. But before I proceed, I have few concerns.
1. This isn't my first time flashing custom ROMs but it is my first time flashing custom ROM on a phone with locked bootloader. So, my understanding is that first I unlock bootloader, flash a custom recovery & then root with Magisk, ultimately flashing a ROM. Is this the correct process?
2. Will I lose the IMEI information at any point in the process? If yes, if there any solution to circumvent it?
3. Can I use all banking apps on custom ROM without any issues?
4. Is there any other downside of doing all this that's not known commonly?
I've been meaning to get out of the "stock" firmware walled garden for a long time and I think it's time. I'd really appreciate any help you can offer in this regard.
P.s: Also suggest any ROM that in your experience is the best.
Thanks in advance!
yourSAS said:
Hi everyone,
I'm tired of Lenovorola's poor update schedule and have decided to flash any of the latest (stable) custom ROM from the threads here. But before I proceed, I have few concerns.
1. This isn't my first time flashing custom ROMs but it is my first time flashing custom ROM on a phone with locked bootloader. So, my understanding is that first I unlock bootloader, flash a custom recovery & then root with Magisk, ultimately flashing a ROM. Is this the correct process?
Click to expand...
Click to collapse
For the most part yes, you don't need to root before installing a custom rom.
2. Will I lose the IMEI information at any point in the process? If yes, if there any solution to circumvent it?
Click to expand...
Click to collapse
Normally no, it's very rare for IMEI issues.
3. Can I use all banking apps on custom ROM without any issues?
Click to expand...
Click to collapse
Depends on the requirements of the banking apps, I've never had any issues with banking apps.
4. Is there any other downside of doing all this that's not known commonly?
Click to expand...
Click to collapse
There always some issues with a small % of users and rooting/custom roms.
I've been meaning to get out of the "stock" firmware walled garden for a long time and I think it's time. I'd really appreciate any help you can offer in this regard.
P.s: Also suggest any ROM that in your experience is the best.
Thanks in advance!
Click to expand...
Click to collapse
Lineage OS is a good rom to start with, but every rom has it's pros/cons.
I suggest trying a few to see what you like.
First thing after TWRP is installed. Make a backup of your EFS and keep it somewhere safe. Just in case.
Like @Randumb_User said do a backup of the EFS partition (or do a full backup - that's what I would do).
I tried several customs - Nougat and Oreo. In most cases battery life wasn't nearly as good as the StockROM.
If you want to play it safe use one of the TWRP flashable ones. If you want to be up to date I would suggest FrankenROM (best use v12.5, 13 has a minor issue with the recent apps list) - stable, fast, very good battery life (1,5d is no problem).
But hey - it's also a matter of taste ....
yourSAS said:
Hi everyone,
I'm tired of Lenovorola's poor update schedule and have decided to flash any of the latest (stable) custom ROM from the threads here. But before I proceed, I have few concerns.
1. This isn't my first time flashing custom ROMs but it is my first time flashing custom ROM on a phone with locked bootloader. So, my understanding is that first I unlock bootloader, flash a custom recovery & then root with Magisk, ultimately flashing a ROM. Is this the correct process?
2. Will I lose the IMEI information at any point in the process? If yes, if there any solution to circumvent it?
3. Can I use all banking apps on custom ROM without any issues?
4. Is there any other downside of doing all this that's not known commonly?
I've been meaning to get out of the "stock" firmware walled garden for a long time and I think it's time. I'd really appreciate any help you can offer in this regard.
P.s: Also suggest any ROM that in your experience is the best.
Thanks in advance!
Click to expand...
Click to collapse
Looks like I get to answer my own queries.(I've flashed custom ROM)
1. Yes, the process is indeed the same, except you'll have to flash no-verity patch first in recovery before doing anything else.
2. No (at least, in my case)
3. Most of them work (if they don't, use Magisk hide). The only exception so far is Tez, which doesn't work.
4. Nothing that really matters. Custom ROM will offer mostly stable experience and some minor hiccups
I've tried only Xtended ROM so far and mentioned feedback on its thread.
I'll update on this thread if I've anything to add
Update: You'll get to use modded Google Camera with Oreo based ROMs/stock firmware with root - which makes a HUGE difference in photo quality. So, totally worth unlocking the phone.
Read in another thread (think it was baout CarbonROM) that TEZ works when you login/authenticate or what ever before you install Magisk.
TGHH said:
Read in another thread (think it was baout CarbonROM) that TEZ works when you login/authenticate or what ever before you install Magisk.
Click to expand...
Click to collapse
I've uninstalled Magisk and tried but it's not working :/
yourSAS said:
I've uninstalled Magisk and tried but it's not working :/
Click to expand...
Click to collapse
Not sure if uninstall Magisk is enough. Maybe you need to verify TEZ right after flashing and then install Magisk. Maybe contact the member who posted the work around in the post I linked. Good luck!
yourSAS said:
Looks like I get to answer my own queries.(I've flashed custom ROM)
1. Yes, the process is indeed the same, except you'll have to flash no-verity patch first in recovery before doing anything else.
2. No (at least, in my case)
3. Most of them work (if they don't, use Magisk hide). The only exception so far is Tez, which doesn't work.
4. Nothing that really matters. Custom ROM will offer mostly stable experience and some minor hiccups
I've tried only Xtended ROM so far and mentioned feedback on its thread.
I'll update on this thread if I've anything to add
Click to expand...
Click to collapse
is your rom pass safetynet?
if its pass try clear data on tez then use magisk hide it will hide root for tez so u can use tez
dhinesh_cool said:
is your rom pass safetynet?
if its pass try clear data on tez then use magisk hide it will hide root for tez so u can use tez
Click to expand...
Click to collapse
I've tried this already. Didn't help.
yourSAS said:
I've tried this already. Didn't help.
Click to expand...
Click to collapse
You could try enabling magisk hide and then revoke the phone permission for google play services.
kishorv06 said:
You could try enabling magisk hide and then revoke the phone permission for google play services.
Click to expand...
Click to collapse
Thank you. I used this trick (hiding telephony permission) along with all other restrictions like Magisk hide. It worked.
When you go back to stock ROM do not use the fastboot erase modemtest commands because it will erase the imei just those two commands omitted-
RubenPCA said:
When you go back to stock ROM do not use the fastboot erase modemtest commands because it will erase the imei just those two commands omitted-
Click to expand...
Click to collapse
I don't know if I'll be going back to stock ROM because Oreo ROM is that good. Thanks for the heads up though.
yourSAS said:
Thank you. I used this trick (hiding telephony permission) along with all other restrictions like Magisk hide. It worked.
Click to expand...
Click to collapse
Happy to hear that.
I've seen many posts about people losing their imei and volte with no permanent solution. Should i unlock my bootloader and install custom roms on my g5 plus? It's there any chance i might lose my imei or 4g?
spandy992 said:
I've seen many posts about people losing their imei and volte with no permanent solution. Should i unlock my bootloader and install custom roms on my g5 plus? It's there any chance i might lose my imei or 4g?
Click to expand...
Click to collapse
I didn't lose IMEI. I followed the process mentioned in the OP
spandy992 said:
I've seen many posts about people losing their imei and volte with no permanent solution. Should i unlock my bootloader and install custom roms on my g5 plus? It's there any chance i might lose my imei or 4g?
Click to expand...
Click to collapse
Backup your efs partition if u lost volte it will help
Fingerprint option missing in "Security" settings after flashing custom ROMs
Hello! I'm trying to install custom ROMs on my OnePlus 8 Pro (IN2020) and have the problem with fingerprint sensor: when I'm using stock firmwares (A10/11, MSM/fastboot) or GSI (kernel doesn't matter), I have an option in "Security" with ability of using fingerprints. But when I'm flashing any custom ROM, I have an option disappeared. I've tried restoring my persist partition, tried kernels from various authors (even CleanSlate 1.2.7 with special fingerprint fix), tried not using Magisk and so on. Nothing helps. I guess there can be different types of fingerprint sensor hardware on our phones, so drivers required. Dev's help will be appreciated, also I'm ready to test and send any info needed. Thanks in advance!
Very common issue, run through the fix persist img position problem thread, at least ask in there.
Bare in mind that custom ROMs like GSI's do not have fingerprint functionality, it allows you to create data but not to use it.
Easy Solution,
MSM to Android 11.
dladz said:
Very common issue, run through the fix persist img position problem thread, at least ask in there.
Bare in mind that custom ROMs like GSI's do not have fingerprint functionality, it allows you to create data but not to use it.
Click to expand...
Click to collapse
I don't think you've read it quite right. I tried fixing persist partition, also GSI ROMs have the fingerprint option for me.
IronSingh said:
Easy Solution,
MSM to Android 11.
Click to expand...
Click to collapse
How can I flash custom ROMs after flashing A11 MSM??? Sounds impossible for me.
Welld1s said:
I don't think you've read it quite right. I tried fixing persist partition, also GSI ROMs have the fingerprint option for me.
Click to expand...
Click to collapse
I've read that the option is there but after enrollment it fails to function.
So you've been through the persist fix?? Have you asked in that said thread?! There's a tonne of people who have had this issue and have got it fixed.
I'm sure they'll know what to do with it
dladz said:
I've read that the option is there but after enrollment it fails to function.
So you've been through the persist fix?? Have you asked in that said thread?! There's a tonne of people who have had this issue and have got it fixed.
I'm sure they'll know what to do with it
Click to expand...
Click to collapse
There is a difference in our situations: their enrollment is failed, but I don't see an option at all. Like the driver or device is not found, so Android thinks I don't have a fingerprint scanner. Tried the persist fix, yes. I'm not a total noob in here, been ROM addict from Samsung S3 stuff I think the problem is we have another fingerprint scanner hardware with different driver needed on some instantnoodlep devices.
Welld1s said:
There is a difference in our situations: their enrollment is failed, but I don't see an option at all. Like the driver or device is not found, so Android thinks I don't have a fingerprint scanner. Tried the persist fix, yes. I'm not a total noob in here, been ROM addict from Samsung S3 stuff I think the problem is we have another fingerprint scanner hardware with different driver needed on some instantnoodlep devices.
Click to expand...
Click to collapse
I know mate, but that's the only thing I could suggest, the GSI and the OOS issues were always different.
Have you changed firmwares, like from regional to global?
I think it would at least be with talking to the person who came up with the persist fix as they obviously know a lot more about this specific issue.
I highly doubt that the hardware is broken.
Not suggesting you're a noob either, just suggesting you've missed something potentially, that could happen to anyone.
Personally I don't know how to fix it as I've never had they issue.
Good luck with it.
dladz said:
I know mate, but that's the only thing I could suggest, the GSI and the OOS issues were always different.
Have you changed firmwares, like from regional to global?
I think it would at least be with talking to the person who came up with the persist fix as they obviously know a lot more about this specific issue.
I highly doubt that the hardware is broken.
Not suggesting you're a noob either, just suggesting you've missed something potentially, that could happen to anyone.
Personally I don't know how to fix it as I've never had they issue.
Good luck with it.
Click to expand...
Click to collapse
I'm not telling you that hardware is broken, I think that hardware is different, because I've read something similar from people who has newer devices.
Welld1s said:
I'm not telling you that hardware is broken, I think that hardware is different, because I've read something similar from people who has newer devices.
Click to expand...
Click to collapse
Right ok, well good luck with that pal.
v.is.for.vladdy said:
Hello! I'm trying to install custom ROMs on my OnePlus 8 Pro (IN2020) and have the problem with fingerprint sensor: when I'm using stock firmwares (A10/11, MSM/fastboot) or GSI (kernel doesn't matter), I have an option in "Security" with ability of using fingerprints. But when I'm flashing any custom ROM, I have an option disappeared. I've tried restoring my persist partition, tried kernels from various authors (even CleanSlate 1.2.7 with special fingerprint fix), tried not using Magisk and so on. Nothing helps. I guess there can be different types of fingerprint sensor hardware on our phones, so drivers required. Dev's help will be appreciated, also I'm ready to test and send any info needed. Thanks in advance!
Click to expand...
Click to collapse
Bro on my op 8 pro my fp option is also missing if u got anything thats works for you pls let me know I'm using my device without fp and it's been 25 days plus... I'm not happy with face unlock..
Bdw i tried fix persist img and msm tool nothing working for me if u got anything brother let me know ... I cant RDA my device no customer service in my city.
Just curious...you're both on 11 right?
The persist fix I believe was originally intended for Android 10 (I know that's when it came out)
My point being, would it be worth downgrading to 10 then running the through the fix?
dladz said:
Just curious...you're both on 11 right?
The persist fix I believe was originally intended for Android 10 (I know that's when it came out)
My point being, would it be worth downgrading to 10 then running the through the fix?
Click to expand...
Click to collapse
Sir, I don't have fingerprint option only on CUSTOM ROMS, which are currently running Android 10 only. I have it perfectly working on STOCK ROMS (A10/A11) and GSI.
Welld1s said:
Sir, I don't have fingerprint option only on CUSTOM ROMS, which are currently running Android 10 only. I have it perfectly working on STOCK ROMS (A10/A11) and GSI.
Click to expand...
Click to collapse
GSI ROMs don't have the fingerprint working mate. .
Thats pretty well known I believe
And a custom ROM would be a complete ROM a GSI is simply a system image, you almost always have to expect issues.. The title of this thread is misleading for that very reason, should have been called "No fingerprint on GSI ROMs"
What happens if you use lineage or Carbon both built for the 1+8pro, my guess is that it'll work.
You could try to flash an actual custom ROM, then wipe system and install the GSI, if that doesn't work then it won't work.
Nothing to do with your hardware, driver, persist or anything else its just a GSI limitation.
Also stop with the patronising attitude, there's no call for it, it doesn't help you, me or anyone else.
dladz said:
GSI ROMs don't have the fingerprint working mate. .
Thats pretty well known I believe
And a custom ROM would be a complete ROM a GSI is simply a system image, you almost always have to expect issues.. The title of this thread is misleading for that very reason, should have been called "No fingerprint on GSI ROMs"
What happens if you use lineage or Carbon both built for the 1+8pro, my guess is that it'll work.
You could try to flash an actual custom ROM, then wipe system and install the GSI, if that doesn't work then it won't work.
Nothing to do with your hardware, driver, persist or anything else its just a GSI limitation.
Also stop with the patronising attitude, there's no call for it, it doesn't help you, me or anyone else.
Click to expand...
Click to collapse
I guess we have a misunderstanding here. What I did and the result - no fingerprint in security options:
1. Flashed stock A10 firmware via MSM, updated to latest A10 version with zip-archive locally
2. Unlocked the bootloader
3. Rebooted to the system once
4. Booted to fastbootd and flashed any custom ROM for both slots (means Lineage OS, Pixel Experience and Carbon ROM) with data/metadata wipes
5. Rebooted to installed system, passed initial setup
6. Set the PIN, got no fingerprint option in settings.
I can repeat: I have it working on stock A10/11 AND GSI, only Lineage, Pixel and Carbon custom ROMs on A10 are affected. Not making something up, not trolling or "patronising", just trying to provide all the useful info that you, for some reason, don't want or can't accept. :/
Edit: my mistake, as I actually didn't try to add any fingerprint on GSI, so can't say that it works for 100% here. I'm just saying, that the option is in place in settings, but not when using custom ROMs like LOS and so on. No offense.
Welld1s said:
I guess we have a misunderstanding here. What I did and the result - no fingerprint in security options:
1. Flashed stock A10 firmware via MSM, updated to latest A10 version with zip-archive locally
2. Unlocked the bootloader
3. Rebooted to the system once
4. Booted to fastbootd and flashed any custom ROM for both slots (means Lineage OS, Pixel Experience and Carbon ROM) with data/metadata wipes
5. Rebooted to installed system, passed initial setup
6. Set the PIN, got no fingerprint option in settings.
I can repeat: I have it working on stock A10/11 AND GSI, only Lineage, Pixel and Carbon custom ROMs on A10 are affected. Not making something up, not trolling or "patronising", just trying to provide all the useful info that you, for some reason, don't want or can't accept. :/
Edit: my mistake, as I actually didn't try to add any fingerprint on GSI, so can't say that it works for 100% here. I'm just saying, that the option is in place in settings, but not when using custom ROMs like LOS and so on. No offense.
Click to expand...
Click to collapse
Then I'm not sure pal.
GSI I would expect it, lineage I haven't installed it but haven't heard anything to suggest it doesn't work.
Carbon ROM I'm pretty sure had the option for me, was a little flakey by it worked..
None taken, sorry I'd barely slept.
PS: seeing as you're on Android 10 why not use twrp? And is born slots necessary? I don't think I did that.
That's the only significant difference I can see between your method and mine.
Also that I set up the phone with a fingerprint each time, not sure if it did or not.
PPS: "don't want or can't accept" yes that's sarcasm pal just saying.
You have a new device. See this thread: https://forum.xda-developers.com/oneplus-8-pro/help/kernel-devs-fingerprint-scanner-t4163005
And this custom kernel fix: https://forum.xda-developers.com/showthread.php?p=83613489
Basically wait for Android 11 custom ROMs to com out.
dladz said:
Then I'm not sure pal.
GSI I would expect it, lineage I haven't installed it but haven't heard anything to suggest it doesn't work.
Carbon ROM I'm pretty sure had the option for me, was a little flakey by it worked..
None taken, sorry I'd barely slept.
PS: seeing as you're on Android 10 why not use twrp? And is born slots necessary? I don't think I did that.
That's the only significant difference I can see between your method and mine.
Also that I set up the phone with a fingerprint each time, not sure if it did or not.
PPS: "don't want or can't accept" yes that's sarcasm pal just saying.
Click to expand...
Click to collapse
Tried with TWRP too, makes no difference for me. Both slots aren't necessary for sure, but that won't hurt too.
I think I tried literally anything except flashing LOS right on A11 OOS, which is a total nonsense. :^(
Welld1s said:
Tried with TWRP too, makes no difference for me. Both slots aren't necessary for sure, but that won't hurt too.
I think I tried literally anything except flashing LOS right on A11 OOS, which is a total nonsense. :^(
Click to expand...
Click to collapse
I didn't suggest flashing Lineage on 11, that's a bad idea wherever said that.
The chap above has a decent idea there, maybe it is hardware.
Give that a shot.
@DJ said:
You have a new device. See this thread: https://forum.xda-developers.com/oneplus-8-pro/help/kernel-devs-fingerprint-scanner-t4163005
And this custom kernel fix: https://forum.xda-developers.com/showthread.php?p=83613489
Basically wait for Android 11 custom ROMs to com out.
Click to expand...
Click to collapse
As I said in the beginning (love quoting myself):
"tried kernels from various authors (even CleanSlate 1.2.7 with special fingerprint fix)"
Doesn't help + gives a distorted image after booting the system on custom ROMs (disappears after locking and unlocking the device again). Looks like the only way is to waaaait. :'c