Related
After updating my zenfone 5 (intel 2.0GHz) to android Marshmallow screen locks and unlocks randomly when it's laying in landscape or horisontal position(if I handle it with any angle it also does, but less frequently)
I have no idea what to do. I have tried unofficial CM13.1 and Resurection Remix and it's the same(I made clean flash of course). Dirty unicorns doesn't boot at all, so I have no chance to check it.
Maybe I should flash any speciffic firmware to use marshmallow without problems but I have no idea wchich one... (Is there any step-by-step manual of moving to MM and flashing these ROMs? I'm not sure but i think I have used this one)
The second problem but a bit smaller is that I can't connect to the cellular data internet but i'd focus one the first one.
Here's the video:
https://www.youtube.com/watch?v=qEAg6K3z0OE
If I enable any screen lock I just can't use the phone
Before Marshmallow update(on stock ROM, but unlocked) there was everything ok.
It also doesn't locks on TWRP, only on system
thats came from bootloaderunlock you can use cm 13.1 kernel and enable dnxfix for this second dirtyunicorn is booting when you came from cm based roms you must make a fullwipe then dirty is aosp thanks
Thanks
Ok, I flashed CM13.1 boot img. It's the same. I also tried to reflash whole CM from here: http://forum.xda-developers.com/zenfone-5/development/cyanogenmod-13-t3382702 and it doesn't work.
The phone still locks and unlocks its screen :/
I made full wipe of course...
"dnxfix" - do you mean "dnfix" wchich is mentioned in cyanogen's thread? Ok, I'll try it. And slockfix. It looks promising
Have the same problem here. The problem goes away on airplane mode though.
I just moved from Pure Nexus 7.1 to SuperXE 8.1. I think I forgot to flash vendor image but otherwise did full clean flash. ROM boots but when trying to connect to WiFi there is voice input but no keyboard. Haven't ever seen something like this before... Added vendor image and redid full/clean flash multiple times with same result. Unfortunately, activity on that ROM thread is a bit slow and I'm down without my phone so decided to ask for help here.
Adding $20 bounty for help fixing. Serious withdrawal mode without my phone. I have a backup phone but it is nearly unusable...
Solution here https://forum.xda-developers.com/showpost.php?p=76126862&postcount=263
Since you are coming from Nougat to Oreo i would suggest you first flash the full oreo factory image before flashing the oreo custom rom. Its not usually a must but solves a lot of minor problems
I have an SM-N900V (Note 3, Verizon variant, hltevzw).
Detailed timeline:
- I flashed it back to firmware OB6 using Odin 3.09.
- I rooted it using ArabicToolApp.
- I used this tool to unlock the bootloader
- I installed a build of LineageOS 14.1 for hlte
- It didn't recognize the SIM so I did a dirty flash of this build of LineageOS 15.1 for hltetmo on top (hltetmo actually has different hardware than hlte, and the correct one for SM-N900V)
- Messed around with the APNs until it recognized and connected to Verizon's network. I DO have functioning SMS and LTE data, but I have not tested phone calls yet
- Messed around some with SuperSU in system- and systemless-mode. Bricked my device more times than I could count, then unbricked over and over using SuperSU's impeccable installer. Messed around with this quite a bit
- Also messed around with Xposed some. The OS is too unstable to run Xposed Installer correctly, so I uninstalled it
- Removed SuperSU, installed Magisk. Phone now passes SafetyNet
So, my phone now runs 8.1 and a Lineage build from 9 days ago. Cool. But, if I was satisfied I wouldn't be making this post. There are multiple instances of the same kind of "app freeze" - App screen freezes, sometimes it'll go completely black. Interactivity doesn't work, obviously, the app is completely frozen. Hold Back to kill doesn't work (Application Killed toast shows, but nothing happens). ANR (when it comes up) Close doesn't work. Home button works and brings me away from the app, but it's still there. Swipe away in Overview doesn't actually kill the app. Even in App Info, Force Stop doesn't work. The app is forever frozen. Tapping the icon from the launcher no longer does anything, it doesn't even bring up the app. The app is permanently crashed and inaccessible until a reboot.
Issues:
- Sometimes when booting the phone will not recognize the SIM until a reboot. As in, "No SIM" message and everything
- Sometimes it will get stuck at boot, I have foxy-boot installed, so I can see the logs. I don't remember what it was all about, if it comes up again I'll update the post
- Google Chrome sometimes crashes when trying to download a file. I've gotten my phone to self-host before, but this issue always seems to come back, and when it does Google Chrome ALWAYS crashes when trying to download a file. App Freeze
- Netflix installs and logs in but freezes at the "can't connect to service (-9)" message. App Freeze
- Certain apps like NativeScript Playground get stuck at the splash screen. App Freeze
- Xposed Installer did this when opening the Settings, whether Xposed was installed or not. App Freeze
- F-Droid also sometimes crashes, although it's somewhat arbitrary, I can't reproduce it reliably. App Freeze
I have tried reflashing the ROM, flashing Xposed uninstaller, reinstalling Magisk, none of it seems to work. I have TWRP 3.3.0 so I can do pretty much anything that doesn't involve the SD card (the SD card is probably broken in hardware, it's so read-only that Android and TWRP both can't write to it at all, but they can both read the same half-broken filesystem).
I fear that this OS is just too unstable for the phone and there's nothing I can do. I sincerely hope this is not the case.
Try other ROMs or perform a clean installation.
Make sure you are on PL1 bootloader/modem.
Currently using Resurrection Remix v5.8.5 Nougat because it was the last Android version for this device with working Bluetooth calls but if you don't use that feature you could use their Pie version as well.
RR ROMs are solid and work extremely well.
Do a clean installation via TWRP if you go this route.
terminator911 said:
Try other ROMs or perform a clean installation.
Make sure you are on PL1 bootloader/modem.
Currently using Resurrection Remix v5.8.5 Nougat because it was the last Android version for this device with working Bluetooth calls but if you don't use that feature you could use their Pie version as well.
RR ROMs are solid and work extremely well.
Do a clean installation via TWRP if you go this route.
Click to expand...
Click to collapse
I did a clean installation of RR 6.0.0 (Android 8.1) and it works a lot better than LineageOS did, with even more configuration options. I really really hate Pie and its gesture-based gimmicks (Screw you Google for copying more of Apple's bad design decisions), so I assumed Oreo would be more stable, but the ROM I installed still has crashing apps. Google Chrome still won't download most things (I've gotten it to download before), trying to change the accent color crashes the 'LineageOS Settings' app, and F-Droid is seriously messed up, but most other things are stable, including the Verizon network which required no pesky APN setup.
I'm on the OB6 bootloader/modem, is that a problem? I doubt that would be an issue, but I can always back up and reflash via Odin. The cool thing is that I installed a patch to TWRP which backs up /data/media along with everything else, after installing the custom ROM. So, really, I can do anything and be perfectly fine. There's, AFAIK, no way to ruin the phone unless something exploits the eMMC brick bug.
If there's another ROM you'd recommend me install, I'd be happy to try it out. I would really like to have a stable OS on here, where Chrome will work and download files. I'd also love Camera2 API since the phone has the chip for it (Snapdragon 800), but none of the ROMs I have support it and there's been no discussion online other than some years-old threads with no answers. I know there have been some articles online listing Note 3 as a phone that'd support Camera2 API with a software update. Would updating the bootloader/modem do anything on that front?
I would upgrade to PL1 bootloader/modem for your device. This is what I have and have had 0 issues. I'd recommend you trying the Samsung Internet browser over Google Chrome; it's much better in my opinion.
You can find the modem here:
https://androidfilehost.com/?w=files&flid=160694
As far as ROMs are concerned you can either try the Nougat version of RR which is what I am currently using as my daily driver with no issues at all including Bluetooth calls:
[ROM][HLTE\TMO\CHN][OFFICIAL]*** Resurrection Remix N 5.8.5 ***[13.03.2018]
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
See here to check whether or not your phone has the Camera2 API capabilities; if not use OpenCamera.
https://www.androidexplained.com/camera2-api-support/
terminator911 said:
I would upgrade to PL1 bootloader/modem for your device. This is what I have and have had 0 issues. I'd recommend you trying the Samsung Internet browser over Google Chrome; it's much better in my opinion.
You can find the modem here:
https://androidfilehost.com/?w=files&flid=160694
As far as ROMs are concerned you can either try the Nougat version of RR which is what I am currently using as my daily driver with no issues at all including Bluetooth calls:
[ROM][HLTE\TMO\CHN][OFFICIAL]*** Resurrection Remix N 5.8.5 ***[13.03.2018]
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
See here to check whether or not your phone has the Camera2 API capabilities; if not use OpenCamera.
https://www.androidexplained.com/camera2-api-support/
Click to expand...
Click to collapse
Excuse me but custom ROMs don't have "the Samsung Internet browser". Additionally the modem shouldn't cause app crashes (if it does, correct me please).
I might try the Nougat ROM. Bluetooth calls don't matter to me, but stability does. I just kinda really like Oreo and all its customization options but it may be too new for this old phone from 2013. It still works as a phone though, Messages and phone calls work fine, so I may just deal with it.
I use Open Camera, and I've tried multiple Camera2 API enablers. The phone has a Qualcomm Snapdragon 800 and the necessary links (in hardware, between the camera/other things) to support Camera2, but nobody seems to have tried it. Probably because the Verizon Note 3 is really locked down, and can only be rooted on a special version of the samsung ROM, and can only be bootloader-unlocked via the eMMC brick bug... There are Magisk modules for Camera2 on Exynos-based devices, but none for the Verizon Note 3 AFAIK.
I just found out that RR 7 officially supports `hltetmo`, but RR 6 doesn't. That's kinda sad, I hate Pie, but I might try it...
I've had the SEPL stuff before, that's the one that can't be rooted. I suppose I didn't consider upgrading again after I unlocked my bootloader. I'll try SEPL1 firmware again, but with a custom ROM...
You can install the Samsung browser from the Play Store. Again, highly recommended.
As far as SEPL1 just update the modem to it; that shouldn't cause any issues but it will ensure your SIM is recognized and data works with the latest ROMs. That is one requirement you will see listed on all of these ROMs.
Not sure which one you are trying to install but here are all the Resurrection Remix versions:
Nougat:
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
Oreo:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrection-remix-n-6-0-0-t3748689
Pie:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrectionremix-v7-0-0-t3894244
If you don't care about Bluetooth audio during calls then you can safely use Oreo and Pie options.
terminator911 said:
You can install the Samsung browser from the Play Store. Again, highly recommended.
As far as SEPL1 just update the modem to it; that shouldn't cause any issues but it will ensure your SIM is recognized and data works with the latest ROMs. That is one requirement you will see listed on all of these ROMs.
Not sure which one you are trying to install but here are all the Resurrection Remix versions:
Nougat:
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
Oreo:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrection-remix-n-6-0-0-t3748689
Pie:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrectionremix-v7-0-0-t3894244
If you don't care about Bluetooth audio during calls then you can safely use Oreo and Pie options.
Click to expand...
Click to collapse
Yeah but, data and calling worked fine on the LineageOS and RR roms, so there's no reason to update the modem.
Besides, I flashed SEPL1 6 times using Odin (multiple times by flashing, rebooting directly into download mode and flashing it once more) and it doesn't want to update. Still on OB6. On the latest (official Pie) RR rom, data worked on first boot but doesn't work anymore (I'm going to mess around with the data settings until it works), but I have no reason to believe that my phone needs a modem update to function.
I did, many times, make calls to various phone numbers and they all worked flawlessly. SEPL1 is therefore not needed if that's all it does.
And I do know about all the Resurrection Remix versions: One is Nougat from their archive, one is the Oreo version I had installed just yesterday before flashing Pie, and the other one is Pie which is now officially supported.
I am currently working on getting RR7 to work, it's only crashed a few times, and I don't even remember what those times were (I think it was using the Back button in Overview/Recents at the same time as the Overview button?)
When updating modem via Odin you have to pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot. If you look at the ROM threads for anything newer than Android v5 they all recommend updating to the latest bootloader & modem for your device which in this case is PL1. This can be to prevent crashes/no signal /no SIM, etc...
Are you dirty flashing these ROMs? I have never experienced any crashes with any of the RRs on my phone but I always do a clean install and make sure to also delete the "Android" folder on my SD Card via TWRP after doing the "Advanced" wipe and deleting everything listed there except for the External SD Card.
terminator911 said:
When updating modem via Odin you have to pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot. If you look at the ROM threads for anything newer than Android v5 they all recommend updating to the latest bootloader & modem for your device which in this case is PL1. This can be to prevent crashes/no signal /no SIM, etc...
Are you dirty flashing these ROMs? I have never experienced any crashes with any of the RRs on my phone but I always do a clean install and make sure to also delete the "Android" folder on my SD Card via TWRP after doing the "Advanced" wipe and deleting everything listed there except for the External SD Card.
Click to expand...
Click to collapse
"pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot"
So...
- Reboot phone into Download mode
- Pull battery while in Download mode
- Flash thingy
- Reboot back into Download mode
- Flash thingy again
? That will be very difficult to do with my dodgy charging cable that doesn't like being repositioned...
I do that without pulling the battery, but I could try it with.
I'm downloading the full SEPL stock image to flash. Once that's done, I'll flash it, reflash TWRP, restore my backup, and see if the baseband has updated.
And no, never dirty flashed the ROM. Always completely wiped data, system, cache and everything. I always backup first. I currently have 3 backups: Lineage OS (before installing RR), RR6 (Oreo), and RR7 (right now before that stock image I'm going to flash).
My external SD card is nonfunctional and read-only with some trash files from the previous phone.
I flashed the stock SEPL ROM. Baseband still didn't change. Restored from backup, SIM now works. Network is detected, SMS and data both work reliably on all reboots.
I will mention that I did brick my phone by using Odin to erase the eMMC, but I fixed that from TWRP, and now everything works flawlessly. There are still some app crashes, but most things are very stable. Camera2 API still nonexistent, which is sad because I got used to it on my old phone, but I shouldn't hope for it.
Fingerprint Scanner Null after Pie ROM Flash - Custom ROM won't fix. Stock Only
Ok, the story.... Moto G5+ retail, running 8.1 Oreo, Bootloader Unlocked, rooted using Magisk 16.7 and was able to backup my Stock Oreo ROM once rooted, or I'd be dead in the water.
So wanting to stay ahead, I tried my hand at RR v7's Pie version, which, after some troubleshooting, was able to install successfully; but I don't much care for the google bar and other hard-coded "pure android" features. Same thing with Pixel Exp. Not to mention that Pie disallows call recording among a few other things Google decided to stifle its customers with. Deal breaker. So - moving on...or back for that matter.
I proceeded to download RRv6, which is btw running nicely on a 2nd G5+, same GApps, installs perfect except - FingerPrint Reader is not acknowledged. Period. No Security settings, No RR Config to access it, Nada. No matter what ROM I flash outside of the StockROM I backed up, it won't recognize the fp reader upon boot up. Whether I clear Dalvik/Cache, All DATA, do a full Wipe, DATA WIPE, REPAIR, FORMAT, nothing allows me to install RR v6.0 or any other flavor, Oreo or Pie, even while trying a dirty flash over Stock Oreo on this Moto G5+. Tried with several SD Cards, downloading fresh zip files from RR. I even went so far as to image the working G5+, then copy into the 2nd G5's SN folder, and do a restore, just loops - even after repairing the partition. I managed to work around that, Restored the image, but still no FP recognized by the initial Google startup/setup. It's almost as if the phone's been "firmwared" or "tagged".
Any ideas what could be lingering from Android Pie that would survive a F2FS/exT Format? Because something updated some kind of firmware on the phone during a Pie ROM flash, that now won't let me go back to anything below Pie, with a working fingerprint reader. The only difference between the G5 that works and this one is the working one has never seen Android 9. And it's staying that way til we come up with a way to hack the google crap.
Any help would be - awesome to say the least.
Thanks for looking.
Hello,
The issue with fingerprint is that after flashing stock Oreo ROM it replaces some files related to fingerprint sensor.
Hence all the newer custom ROM builds use the Oreo firmware related files. Hence it worked on the Pie ROM.
RR v6 would be still using the old nougat firmware hence you need to flash a file for it work. Which will replace the fingerprint related files for Nougat Stock firmware:
https://androidfilehost.com/?fid=1322778262904029634
In case you want to revert the changes and use Pie ROMs:
https://androidfilehost.com/?fid=1322778262904029635
sharan.nyn said:
Hello,
The issue with fingerprint is that after flashing stock Oreo ROM it replaces some files related to fingerprint sensor.
Hence all the newer custom ROM builds use the Oreo firmware related files. Hence it worked on the Pie ROM.
RR v6 would be still using the old nougat firmware hence you need to flash a file for it work. Which will replace the fingerprint related files for Nougat Stock firmware:
https://androidfilehost.com/?fid=1322778262904029634
In case you want to revert the changes and use Pie ROMs:
https://androidfilehost.com/?fid=1322778262904029635
Click to expand...
Click to collapse
That would make sense if PHONE1 manifested the same thing. But I went from StockOreo to RRv6-Oreo w/out losing anything and having to flash any FP Firmware. I used the RRv6 Official from 18-0911. Which is what's been leading me to believe there's something awry with this 2nd G5. I wonder is it possible PHONE2 has some slight firmware variance that is simply ignoring during the RR flash? Anyway, I'll give this a shot. this is TWRP flash, not fastboot, yes? Just being clear as I'm not proficient at this just yet.
Thanks Sharan!
DJScribe said:
That would make sense if PHONE1 manifested the same thing. But I went from StockOreo to RRv6-Oreo w/out losing anything and having to flash any FP Firmware. I used the RRv6 Official from 18-0911. Which is what's been leading me to believe there's something awry with this 2nd G5. I wonder is it possible PHONE2 has some slight firmware variance that is simply ignoring during the RR flash? Anyway, I'll give this a shot. this is TWRP flash, not fastboot, yes? Just being clear as I'm not proficient at this just yet.
Thanks Sharan!
Click to expand...
Click to collapse
Yeah, give it a try. And yes it's to be flashed via TWRP.
[SOLVED]
sharan.nyn said:
Yeah, give it a try. And yes it's to be flashed via TWRP.
Click to expand...
Click to collapse
Sweet! I had to reflash from scratch as for some reason it wouldn't let me update the ROM already running. But once I re-flashed RRv6-8.1, then flashed FP, it's now back. You rock Sharyn - nice work!
Now if only we found a way to cleanup that Pie - hate the perpetual time stamp, search bar and inability to record voice. Which is why I'm staying on Oreo til further notice. I know it was Google who took it away on v9.
Thanks again Shar!
:good::victory:
DJScribe said:
Sweet! I had to reflash from scratch as for some reason it wouldn't let me update the ROM already running. But once I re-flashed RRv6-8.1, then flashed FP, it's now back. You rock Sharyn - nice work!
Now if only we found a way to cleanup that Pie - hate the perpetual time stamp, search bar and inability to record voice. Which is why I'm staying on Oreo til further notice. I know it was Google who took it away on v9.
Thanks again Shar!
:good::victory:
Click to expand...
Click to collapse
Crap - so turns out this solution was short-lived. FingerPrint Scanner is back to inactive and FPzip isn't fixing it. Only StockOreo brings it back. Tried a plethora of ROMs from Nougat to Oreo, nothing but Pie and stock Oreo. Symptoms say it's the ROM, but a ROM that is currently working on the 1st G5 won't work either. Still looking for solutions, anyone...
Hi, I open this thread because I wanted to kindly ask for advice on what the best bootstack to install Pie Roms like Resurrection Remix 7.0.2 or ViperOS 6.7 might be.
I have already used the A2017x_LineageOS15.1_UniversalBootstack_v2_by_DrakenFX but, when I flash it, even with TWRP_3.2.3-0L_v1.3-Axon7-Labs_Mod and its Remove Message function, I cannot remove the Bootloader Unlock Warning and I cannot boot directly into recovery (either from the phone off with the combination of keys or through the advanced restart of the Roms) without pressing the VolumUp key 2 or 3 times on the Bootloader Unlock Warning screen.
It's not a particularly annoying thing but it led me to wonder if there was a better Bootstack (in the past I tried the Axon7_RR-O_B32-B10_TREBLE-Ready_Oki20180803_FULL_EDL by Oki and I liked his Customized Bootstack with the personalized boot image)
So I wanted to kindly ask if anyone is aware of a better or more stable or more updated Boostack than this (all 3 would be better :fingers-crossed.
I accept any advice and I thank in advance anyone who will know how to help me and the whole forum to keep this device still alive (a special thanks to Raystef66, Oki, NFound and DrakenFX for all the work and guides that have been very useful to me in recent days).
Hi,
When flashing full EDL from DrakenFX, did you put a generic splash.img in the specific "splash" folder located in EDL TOOL ? If I remember correctly, this could delete annoying warning message when booting.
Volumetrik said:
Hi,
When flashing full EDL from DrakenFX, did you put a generic splash.img in the specific "splash" folder located in EDL TOOL ? If I remember correctly, this could delete annoying warning message when booting.
Click to expand...
Click to collapse
I downloaded A2017x_LineageOS15.1_UniversalBootstack_v2_by_DrakenFX.zip and flashed it with A2017G-O-B04-MODEM.zip from TWRP before flashing the rom.
Punisherk said:
I downloaded A2017x_LineageOS15.1_UniversalBootstack_v2_by_DrakenFX.zip and flashed it with A2017G-O-B04-MODEM.zip from TWRP before flashing the rom.
Click to expand...
Click to collapse
OK, I made a mistake, full EDL is by Oki and not DrakenFX. This is in full EDL package the abitility to flash "splash.img".
This operation can be performed in EDL mode, that's what I meant in my previous post.
In the past, I tried your method (flashing by TWRP) , but I can't help since it didn't work for me.
Volumetrik said:
OK, I made a mistake, full EDL is by Oki and not DrakenFX. This is in full EDL package the abitility to flash "splash.img".
This operation can be performed in EDL mode, that's what I meant in my previous post.
In the past, I tried your method (flashing by TWRP) , but I can't help since it didn't work for me.
Click to expand...
Click to collapse
Thanks for the answer, I have already tried Oki's EDL in the past (Axon7_RR-O_B32-B10_TREBLE-Ready_Oki20180803_FULL_EDL) but, I experienced some problems flashing an alternative recovery to NFound's 3.2.1-7 present inside the package after the installation.
If I'm not mistaken then it seems to me that the DrakenFX boostack is more recent and updated (I'm not an expert, I only compared the modification and creation dates of the files and the original creation dates of the ZTE boostacks, modified and used by Oki , and LineageOS used by DrakenFX, and so it seemed to me ).
I will try again and see how it goes.
For the moment the combination of A2017x_LineageOS15.1_UniversalBootstack_v2_by_DrakenFX with A2017G-O-B04-MODEM (especially this because the A2017G_OreoModem proposed by DrakenFX to be combined with his bootstack is more dated and, here in Italy, with the latest original modem published by ZTE, the reception in LTE with Fastweb is much better) and RR-P-v7.0.2-20200112-axon7-OFFICIAL works beautifully without bugs (or at least I haven't experienced it yet :fingers-crossed.
Can I kindly ask you if you know any other modified bootstack besides Oki's and DrakenFX's that are worth trying?
PS: I apologize if there are grammatical errors but my English is a bit rusty and I am helping myself with Google Translate to write these messages .
I didn't try another kernel/bootstack. However, many users talk about baddar kernel.
If you can try it (or another one) , I am very interested by your feedback [emoji39]
Volumetrik said:
I didn't try another kernel/bootstack. However, many users talk about baddar kernel.
If you can try it (or another one) , I am very interested by your feedback [emoji39]
Click to expand...
Click to collapse
If I remember correctly the Resurrection Remix 7.0.2, which I am currently using, it is based on the Baddar kernel RC1.2 (OrdenKrieger's work).
I am currently using it with great satisfaction and it works beautifully.
For the activities that I have done so far I have not encountered any bugs, the phone works fast and smooth and the battery lasts 90-100% longer than before (more than 2 days between a recharge, for a battery older than 2 years , it's miraculous).
Punisherk said:
Hi, I open this thread because I wanted to kindly ask for advice on what the best bootstack to install Pie Roms?
Click to expand...
Click to collapse
Saw your post and you reminded me about AEX 5.8 ROM by NFound. One of the versions had a great battery life, and there was bootstack transition recommended by NFound itself.
Not sure, but he suggest to use A2017U B12 Oreo beta bootstack instead of A2017U B35 Nougat on later versions. Why? I don't know.
Most of people will use Universal v2 by DrakenFX, some may stay on Verequies no splash (B20 US?)/NFound (B12 US?) bootstack/Oki.
Did anyone stayed with Nougat bootstack on Oreo/Pie and have an opinion about this mix?
Few minutes ago, I jumped to b12 bootstack, with TWRP 3.2.1-8 treble and no issues so far.
klałn said:
Saw your post and you reminded me about AEX 5.8 ROM by NFound. One of the versions had a great battery life, and there was bootstack transition recommended by NFound itself.
Not sure, but he suggest to use A2017U B12 Oreo beta bootstack instead of A2017U B35 Nougat on later versions. Why? I don't know.
Most of people will use Universal v2 by DrakenFX, some may stay on Verequies no splash (B20 US?)/NFound (B12 US?) bootstack/Oki.
Did anyone stayed with Nougat bootstack on Oreo/Pie and have an opinion about this mix?
Few minutes ago, I jumped to b12 bootstack, with TWRP 3.2.1-8 treble and no issues so far.
Click to expand...
Click to collapse
If I'm not mistaken, NFound's guide to installing AEX plans to Treblelize the phone by creating multiple partitions and formatting Data and Cache in f2fs file system instead of ext4.
I tried this solution about a year ago, following a guide, but the result, even after a couple of attempts, was not satisfactory in my case (long-term instability problems, sometimes abnormal battery consumption and not really working fluid).
At the end of the tests I had returned to the original system making myself lean towards waiting for new solutions.
I haven't tried AEX since, but I think I'll think about it since time and updates have gone by.
For Verequies, if I remember correctly, it should be included in one of the two EDL packages proposed in the Oki guide [GUIDE] [TREBLE] Axon 7 Custom OREO ROM installation for newbies - 2018.08.05.
I also tried this system but, for the results obtained, I preferred to use another solution.
Currently I have installed the RR 7.0.2 with the DrakenFX Universal Boostack, even if with another Modem compared to the one proposed by him for the A2017G (i.e. the A2017G-O-B04-MODEM of the original Oreo update of the ZTE because, here in Italy with Fastweb operator, it has better reception in LTE +).
Everything works beautifully, smoothly, without bugs or crashes (with formatting in ext4 because, in f2fs instead, crashes started already after 2 days without restarting the device) and the battery consumption is halved (two days between a charge and the other that, for a battery 2 years old and more, seems almost a miracle).
I also really like the enormous possibility of personalization that RR brings with it.
I will try to experiment an installation with the original Nougat boostack, as you suggested, to see the results and compare them.
For the TWRP to be used, do you suggest the NFound 3.2.1-8 or the TWRP_3.2.3-0L_v1.3-Axon7-Labs_Mod made in collaboration (personally I prefer the second one for the multi language besides other things)?
Punisherk said:
If I'm not mistaken, NFound's guide to installing AEX plans to Treblelize the phone by creating multiple partitions and formatting Data and Cache in f2fs file system instead of ext4.
I tried this solution about a year ago, following a guide, but the result, even after a couple of attempts, was not satisfactory in my case (long-term instability problems, sometimes abnormal battery consumption and not really working fluid).
At the end of the tests I had returned to the original system making myself lean towards waiting for new solutions.
I haven't tried AEX since, but I think I'll think about it since time and updates have gone by.
For Verequies, if I remember correctly, it should be included in one of the two EDL packages proposed in the Oki guide [GUIDE] [TREBLE] Axon 7 Custom OREO ROM installation for newbies - 2018.08.05.
I also tried this system but, for the results obtained, I preferred to use another solution.
Currently I have installed the RR 7.0.2 with the DrakenFX Universal Boostack, even if with another Modem compared to the one proposed by him for the A2017G (i.e. the A2017G-O-B04-MODEM of the original Oreo update of the ZTE because, here in Italy with Fastweb operator, it has better reception in LTE +).
Everything works beautifully, smoothly, without bugs or crashes (with formatting in ext4 because, in f2fs instead, crashes started already after 2 days without restarting the device) and the battery consumption is halved (two days between a charge and the other that, for a battery 2 years old and more, seems almost a miracle).
I also really like the enormous possibility of personalization that RR brings with it.
I will try to experiment an installation with the original Nougat boostack, as you suggested, to see the results and compare them.
For the TWRP to be used, do you suggest the NFound 3.2.1-8 or the TWRP_3.2.3-0L_v1.3-Axon7-Labs_Mod made in collaboration (personally I prefer the second one for the multi language besides other things)?
Click to expand...
Click to collapse
Have been on B12 Nougat bootstack and I don't recommend it.
- Offline charging worked when ROM was installed, without ROM, offline charging still worked but broke Oreo recovery.
- Fastboot worked - like above
- B04 modem worked
- Different BMS/battery behaviour on low health battery (72%) - SOT was same, no shutdowns on low battery, better battery percentage calculation.
(Could be placebo due to battery health and warmer weather)
- Colder phone on low tasks (placebo)
It isn't worth to stay on B12 bootstack.
Everything was fine, until played with him, then **** happened.
3.2.1-8, 3.2.3 with vendor support and 3.2.3 oki recovery doesn't work, if they are flashed on clean B12 - 3 blinks.
They only work, when flashed on DrakenFX bootstack and moving to B12 bootstack.
On first boot to recovery on DFX, they doesn't work, but on second boot they are working.
After flashing no splash message aboot on B12 it worked, until i tried fastboot - everything broke up, incl. system partitions.