[GUIDE][TREBLE] Axon 7 Custom OREO ROM installation for newbies - 2018.08.05

Infy_AsiX

Senior Member
Feb 13, 2012
965
389
0
Brisbane
By the way for those still on B32+10 RR O to avoid the AUX jack CPU usage bug. I noticed wifi latency is poor spiking high often on this ROM.


I took a guess it was system wifi following this Magisk wifi mod thread. Thanks to ChrisFeiveel from Schwifty Telegram chat for sharing his WCNSS_qcom_cfg.ini from Nfound's Havoc ROM. Using TWRP copy unzipped attached file to /system/vendor/etc/wifi. Fixed.


It seems the WCNSS_qcom_cfg.ini on @Kranoner's RR-O is the same as Lineage 14.1's which doesn't work properly with O. Seems somewhere sometime someone fixed the wifi on O.
 

Maxemus_04

Member
Feb 14, 2017
34
2
0
Webview crashes on me anyone else have this problem?

---------- Post added at 12:36 AM ---------- Previous post was at 12:31 AM ----------

Webview crashes all the time anyone else
 
  • Like
Reactions: imakul8

janthe6th

Senior Member
Feb 6, 2011
125
40
0
my understanding of the the battery charge limit app is that it will make phone stop charging at say 90% and start charging at 80%. So is it weird that I always wake up to my phone at 90%? This means that the phone is continuously being charged even when it gets to the upper limit? This defeats the purpose of the app. Did anyone ever wake up to something other than the upper charge limit they set up?
 

Oki

Senior Member
Jul 6, 2006
1,009
1,858
0
East Coast
my understanding of the the battery charge limit app is that it will make phone stop charging at say 90% and start charging at 80%. So is it weird that I always wake up to my phone at 90%? This means that the phone is continuously being charged even when it gets to the upper limit? This defeats the purpose of the app. Did anyone ever wake up to something other than the upper charge limit they set up?
The app disconnects the charging at 90% in your case and at that point the phone works only from the USB power, not battery. The bottom limit is the upper threshold for connecting again the battery charge. That means that if you go on battery for a while and you plug it again, it won't charge unless it is 80% (in your case) or less.
 

marcdw

Senior Member
Sep 24, 2014
5,732
2,880
253
57
Baldwin Park
my understanding of the the battery charge limit app is that it will make phone stop charging at say 90% and start charging at 80%. So is it weird that I always wake up to my phone at 90%? This means that the phone is continuously being charged even when it gets to the upper limit? This defeats the purpose of the app. Did anyone ever wake up to something other than the upper charge limit they set up?
For me I'll see that it is maintaining at the upper limit I set. Phone is cool so I know it's not charging beyond that.
I do remember on one ROM (Axon or Moto, I forget) where it indeed was above the limit set. App/service was working. Gotta check again which ROM I had that issue with.


ZTE Axon 7 A2017U, Dark ROM, LlamaSweet 0.5 Kernel, Multiboot, XDA Legacy
 

AnonVendetta

Senior Member
Apr 29, 2016
823
301
63
Portland, OR
I just tried booting stock B12 Oreo with @Oki's bootstack, it doesn't boot. I can get into TWRP, EDL, FTM, but can't boot into the ROM. I only flashed the B12 bootstack EDL, not the much larger full package that has @Oki's TWRP, vendor partition, custom ROM, etc. I used A7 EDL Tool for flashing, not MiFlash. AOSP Extended Nougat by @NFound doesn't boot either.

Attempting to flash the bootstack zip from TWRP throws an error about not being able to flash the xblbak partition, it just hangs and never finishes.

As far as removing the unlocked bootloader message, I actually prefer to have it, because then I can use the bootloader menu. Is there a way to get it back? The unlocked message doesn't bother me, I don't mind waiting a few seconds. I know the bootloader message is in aboot, the ZTE splash screen is probably in the splash partition.

Thanks!
 

ls117

Senior Member
Jun 11, 2017
51
7
0
the instructions for the audio mods need to be updated. the ainur mod doesnt work with 17.1 or 17.2, it hangs when unmounting during twrp flashing. you have to downgrade to 16.6, maybe 7(i used 6) and continue from there. i might need a new battery, because i dont see any battery life improvements, and i've actually been charging to 80% and recharging around 15 for awhile now, at least 8 months or so. that said im also using xposed, along with the audio mods and i never listen to music below max volume.
 
  • Like
Reactions: ajwbae

AnonVendetta

Senior Member
Apr 29, 2016
823
301
63
Portland, OR
Big problem here:

I flashed the B12 EDL exactly as instructed in the first post. Followed everything to the letter. ROM boots up fine. Then I reboot into TWRP to flash Oreo Xposed, not the Magisk version but the one that installs directly into system. Then I wipe cache/dalvik and try to reboot into ROM. It hangs on the splash screen for about 10 seconds, then a red light flashes and the phone powers off. It isnt a low battery issue, my phone was around 60%. After rebooting into TWRP, the log shows that the cache partition cant be mounted, it appears to be corrupt. All other partitions are fine. So I format cache as ext4 then back to F2FS. I also flashed the Xposed uninstaller zip, along with wiping cache/dalvik again. Phone still doesn't boot. I don't think this is an Xposed issue, I've used the same zip on other Oreo ROMs, no issues.

What the hell is going on here? Thanks!
 

jogai

Senior Member
Nov 27, 2011
281
61
0
Its been a while since I flashed my phone. These instructions seem easy enough. I have one question. How do I backup my current app data. When I went from stock to custom in the past I did root => titaniumbackup => wipe => install => boot => titaniumrestore, or a variation on it, but in this guide I dont see any option to make app backups. Is that correct?
 

Dave_XDA

Member
Feb 15, 2014
34
1
0
Hello Oki,
since some day's i have some issues with the location services. So far i could have the Location Service at battery safing mode (wlan and provider network only) and GMaps found my location instandly. Now, since some day it does'nt work anymore. GMaps tells me, that i'm more than 250km away from my current possition. I try'd the AGPS setting to clear and update, but it does'nt work. If i set the phone to full location service (gps, wlan, provider...) it needs some minutes but it finds my possition. If i turn it into battery save mode the location goes back to the far point.
Is there a solution i can do without resetting my phone? So far it work'd really well for me. I'm still using your "old" non trebble methode and the "stable" v6 20180511 Rom.
I realy don't know what caus'd this issue, but it's really frustrating. If i need to use the gps i have to wait longer as necessary, this was'nt so since these day's the issue starts. Even indoor i had a close to perfect location with wlan and network provider (powersave mode in location).
Many thx
Dave
 

zinger123

Member
Oct 29, 2009
7
0
0
Hi. How to flash to stock A2017G firmware and LOCK boot loader (can't use nfc with bank). Anybody can send me proper link to guide? (I try one but without succes). @Oki ?
 
Last edited:

dj_jormi

Member
Jul 9, 2008
40
9
0
Hello Oki,
since some day's i have some issues with the location services. So far i could have the Location Service at battery safing mode (wlan and provider network only) and GMaps found my location instandly. Now, since some day it does'nt work anymore. GMaps tells me, that i'm more than 250km away from my current possition. I try'd the AGPS setting to clear and update, but it does'nt work. If i set the phone to full location service (gps, wlan, provider...) it needs some minutes but it finds my possition. If i turn it into battery save mode the location goes back to the far point.
Is there a solution i can do without resetting my phone? So far it work'd really well for me. I'm still using your "old" non trebble methode and the "stable" v6 20180511 Rom.
I realy don't know what caus'd this issue, but it's really frustrating. If i need to use the gps i have to wait longer as necessary, this was'nt so since these day's the issue starts. Even indoor i had a close to perfect location with wlan and network provider (powersave mode in location).
Many thx
Dave
I have th same problem!! GPS not works!

have solution??
 

Dave_XDA

Member
Feb 15, 2014
34
1
0
I have th same problem!! GPS not works!

have solution??
Hello,

i could fix my problem by turning the hone off, taking out the sim card, turning it on again. After a short bootup and resetting gps/agps via the "Gps Test" App (hit the 3 dot's in the uper right corner -> AGPS -> Clear and Udate) i turn'd off the phone, inserted the Sim again and booted the phone. After that i had my GPS/Location running again like befour. I got the GPS location correct with GPS High, and after this i've gone inside my house and turn'd the location mode to energy saving and it work'd. Now everything is like befour the issue.

Hope i could help
Dave
 

dj_jormi

Member
Jul 9, 2008
40
9
0
Hello,

i could fix my problem by turning the hone off, taking out the sim card, turning it on again. After a short bootup and resetting gps/agps via the "Gps Test" App (hit the 3 dot's in the uper right corner -> AGPS -> Clear and Udate) i turn'd off the phone, inserted the Sim again and booted the phone. After that i had my GPS/Location running again like befour. I got the GPS location correct with GPS High, and after this i've gone inside my house and turn'd the location mode to energy saving and it work'd. Now everything is like befour the issue.

Hope i could help
Dave

thanks friend!! have myou a apk gps test????
 

dj_jormi

Member
Jul 9, 2008
40
9
0
thanks friend!! have myou a apk gps test????
great!!!! its works!!! thanks for all

---------- Post added at 02:19 PM ---------- Previous post was at 02:16 PM ----------

another problem and soulution:

if you have a problem with "enter the password android", very important made:

then go to Wipe > Advanced Wipe, select Data partition and tap on Repair_or_Change_File_System button and then on Change_File_System button. Format DATA as EXT4 first and, without leaving TWRP do it again as F2FS. That will fix the issue.