Database Users

New User - CyanogenMod Questions

Hello,
I received my Nexus 6P yesterday and got my SIM card activated without any issues at Verizon. I immediately took it home, unlocked the bootloader, installed TWRP, and then flashed CyanogenMod's latest nightly. After booting in, wireless networks weren't detected, and I only had 3G (no 4G LTE as I should). I restored my backup of the stock ROM that I made in TWRP and it hung at the Google logo. I'm not sure why. I then flashed all the latest factory restore images (MTC19X) to get it working again and determined that the issues I had in CyanogenMod might have happened due to the vendor.img I had on my phone at the time not being compatible with that build of CM13.
My questions are:
1) What are the known issues that would likely occur due to vendor.img being a different version than what CM13 was based on? The concept of vendor.img is new to me. I haven't had this, as far as I know, on any of my other phones (granted I'm coming from a locked Samsung Galaxy S5 that I've had for almost 2 years)
2) How can you easily tell which vendor.img CM was based on so you know which one to flash?
3) Is there anything else I should be made aware of before attempting to flash CM13 again?
4) While using CM13, do most people recommend a custom kernel? If so, which one and how stable is it? What are the benefits of switching from the stock kernel, and how simple is it to go back if there's a problem?
Thanks!!

dude...I just got the N6P and ran CM13 within hours. This is what I did...
unlocked the bootloader
downloaded the lastest (MTC19X) image off of https://developers.google.com/android/nexus/images and unpacked it into the C:\Program Files (x86)\Android\android-sdk\platform-tools folder
ran the flash-all.bat
fastbooted TWRP
installed CM13. (didn't wipe internal storage)
installed arm64 open Gapps pico
BAM!!!
right now running stock kernel. it's cool. I'm PrivacyGuard-ing the hell out of all my apps (turned off START AT BOOT and KEEP AWAKE for almost every downloaded app), though, so battery is OK
also using Kernel Adiutor but underclocking values for the CPUs doesn't seem to stick

So it likely worked for you since you had flashed the newest vendor.img first. Apparently there are compatibility issues with certain features that cause them not to work (such as WiFi) if you're using an older one.

chaoticyeshua said:
Hello,
I received my Nexus 6P yesterday and got my SIM card activated without any issues at Verizon. I immediately took it home, unlocked the bootloader, installed TWRP, and then flashed CyanogenMod's latest nightly. After booting in, wireless networks weren't detected, and I only had 3G (no 4G LTE as I should). I restored my backup of the stock ROM that I made in TWRP and it hung at the Google logo. I'm not sure why. I then flashed all the latest factory restore images (MTC19X) to get it working again and determined that the issues I had in CyanogenMod might have happened due to the vendor.img I had on my phone at the time not being compatible with that build of CM13.
My questions are:
1) What are the known issues that would likely occur due to vendor.img being a different version than what CM13 was based on? The concept of vendor.img is new to me. I haven't had this, as far as I know, on any of my other phones (granted I'm coming from a locked Samsung Galaxy S5 that I've had for almost 2 years)
2) How can you easily tell which vendor.img CM was based on so you know which one to flash?
3) Is there anything else I should be made aware of before attempting to flash CM13 again?
4) While using CM13, do most people recommend a custom kernel? If so, which one and how stable is it? What are the benefits of switching from the stock kernel, and how simple is it to go back if there's a problem?
Thanks!!
Click to expand...
Click to collapse
1) Depends on ROM /VENDOR, sometimes nothings happens then an error message, sometimes things doesnt work
2) Just download fresh the latest snapshot, release or nightly (they are much more stable then for a few years!) and vendor image (use these ones which are recommended!)
https://wiki.cyanogenmod.org/w/Install_CM_for_angler (there is a link for the vendor)
3) If you stay close on the tutorials, i dont know what should happen (flashing a rom is normally not critical, installing a recovery can be!)
4) Custom kernels can be great, but its not a must-have. Which kernel you should use depends on your wishes: better battery, more power etc.
Hope i could have help you a little bit!

kaufikauf said:
1) Depends on ROM /VENDOR, sometimes nothings happens then an error message, sometimes things doesnt work
2) Just download fresh the latest snapshot, release or nightly (they are much more stable then for a few years!) and vendor image (use these ones which are recommended!)
https://wiki.cyanogenmod.org/w/Install_CM_for_angler (there is a link for the vendor)
3) If you stay close on the tutorials, i dont know what should happen (flashing a rom is normally not critical, installing a recovery can be!)
4) Custom kernels can be great, but its not a must-have. Which kernel you should use depends on your wishes: better battery, more power etc.
Hope i could have help you a little bit!
Click to expand...
Click to collapse
Very much so. I appreciate it!

Has anyone encountered the constant popup of the Select Sim Card message? I'm using project fi and I am still unable to find a solution to this issue.

Network Solution grayed out/solved

Hi good fellas, so a week back, I flashed mokee build everything was perfect until I received a WhatsApp message from my friend asking me why the hell am I not picking call when it's ringing. I was like what ? Dude send me screenshot and I got roasted. So I tried finding the root cause and got to know sim selection was grayed out.
Issues were,
1. Not able to select sim selection for calls as nothing happens when you click on the selection area. Data works fine for both Sims, I have not tested with SMS.
2. First sim slot works fine for both incoming and outgoing however on the top it shows the second sim name. For example, in my case I'm using Vodafone (first slot) and Tata DoCoMo, so when I make or get a call to Vodafone, it shows me Tata Docomo.
3. There is no way of making calls from second sim.
What did I do?
1. Downloded NucleaRom latest 1.4.1 did a Clean flash (wipe data, cache, dalvik and system) - Did not work.
2. My saviour in flashing, TWRP backups.
Restored NucleaRom 1.3.5 (which was working fine before) - did not work.
3. Restored NucleaRom MM final version 3.0. did not work.
4. Flashed COS 12.1, Bingo got the selection back ( Damn, it has good battery backup) so used it for couple of days.
7. I couldn't take COS Anymore, so downloded last nightly of cm13, clean flash- success
8. Since I'm so addicted to Nougat I wanted to try my luck, tried lates mokee, NucleaRom, RR, sudamod, Cr Droid but it didn't work in any ROM.
9. Back to COS, clean flash, flashed MM Firmware, then Nougat Roms - did not work.
10. Got some update on Nougat ZUI in its XDA post (thanks to developer), downloded both zip and OTA update,clean flashed. Bingo- selection is back. However ZUI still has force close issues
11. Clean flashed NucleaRom, bingo - selection came back.
Not sure what exactly is the root cause since it persists even after clean flash of other ROMS (which were working before) and also backups. If it happens in one ROM, it happens in most or all the Roms. Even in China based ROM.
So, this is the only solution I found, it worked for me. Let me know if it works or if you have any questions.
Thanks to all the developers of Z1. ?

Thanks.
But I think a have found another solution for it.
When I Flash Gapps mini, I have the problem.
But when I Flash Gapps Stock, The default dialer is replaced and then I go to settings and change default dialer to phone(by Google) and sim selection perfect.
Can anyone confirm?

SidthConquerer said:
Thanks.
But I think a have found another solution for it.
When I Flash Gapps mini, I have the problem.
But when I Flash Gapps Stock, The default dialer is replaced and then I go to settings and change default dialer to phone(by Google) and sim selection perfect.
Can anyone confirm?
Click to expand...
Click to collapse
Could be. I had tried with Pico and super. Did not work for me
Sent from my Zuk Z1 using XDA Labs

None of the above two mentioned solutions worked.... can anybody tell me any other way???? i am too disappointed with this problem...

Fahad305 said:
None of the above two mentioned solutions worked.... can anybody tell me any other way???? i am too disappointed with this problem...
Click to expand...
Click to collapse
Is sim selection working on COS, cm13 nightly? What happened when you have flashed zui?
Sent from my Zuk Z1 using XDA Labs

SidthConquerer said:
Thanks.
But I think a have found another solution for it.
When I Flash Gapps mini, I have the problem.
But when I Flash Gapps Stock, The default dialer is replaced and then I go to settings and change default dialer to phone(by Google) and sim selection perfect.
Can anyone confirm?
Click to expand...
Click to collapse
I tried to flash Gapps Stock but it didn't work, Sim selection was still grayed out.
Flashed zui 2.5 Nougat and then clean flashed other Los Nougat ROMs and now Sim selection is working fine.
Thanks for the solution.

SidthConquerer said:
Thanks.
But I think a have found another solution for it.
When I Flash Gapps mini, I have the problem.
But when I Flash Gapps Stock, The default dialer is replaced and then I go to settings and change default dialer to phone(by Google) and sim selection perfect.
Can anyone confirm?
Click to expand...
Click to collapse
I've a same problem haunting me in LOS 14.1, I'll try your solution first...will let you know...
Sent from my ZUK Z1 using Tapatalk

Narasimha12 said:
Is sim selection working on COS, cm13 nightly? What happened when you have flashed zui?
Sent from my Zuk Z1 using XDA Labs
Click to expand...
Click to collapse
my file was corrupt i downloaded it again and bingo. working fine.
thanks

Narasimha12 said:
Hi good fellas, so a week back, I flashed mokee build everything was perfect until I received a WhatsApp message from my friend asking me why the hell am I not picking call when it's ringing. I was like what ? Dude send me screenshot and I got roasted. So I tried finding the root cause and got to know sim selection was grayed out.
Issues were,
1. Not able to select sim selection for calls as nothing happens when you click on the selection area. Data works fine for both Sims, I have not tested with SMS.
2. First sim slot works fine for both incoming and outgoing however on the top it shows the second sim name. For example, in my case I'm using Vodafone (first slot) and Tata DoCoMo, so when I make or get a call to Vodafone, it shows me Tata Docomo.
3. There is no way of making calls from second sim.
What did I do?
1. Downloded NucleaRom latest 1.4.1 did a Clean flash (wipe data, cache, dalvik and system) - Did not work.
2. My saviour in flashing, TWRP backups.
Restored NucleaRom 1.3.5 (which was working fine before) - did not work.
3. Restored NucleaRom MM final version 3.0. did not work.
4. Flashed COS 12.1, Bingo got the selection back ( Damn, it has good battery backup) so used it for couple of days.
7. I couldn't take COS Anymore, so downloded last nightly of cm13, clean flash- success
8. Since I'm so addicted to Nougat I wanted to try my luck, tried lates mokee, NucleaRom, RR, sudamod, Cr Droid but it didn't work in any ROM.
9. Back to COS, clean flash, flashed MM Firmware, then Nougat Roms - did not work.
10. Got some update on Nougat ZUI in its XDA post (thanks to developer), downloded both zip and OTA update,clean flashed. Bingo- selection is back. However ZUI still has force close issues
11. Clean flashed NucleaRom, bingo - selection came back.
Not sure what exactly is the root cause since it persists even after clean flash of other ROMS (which were working before) and also backups. If it happens in one ROM, it happens in most or all the Roms. Even in China based ROM.
So, this is the only solution I found, it worked for me. Let me know if it works or if you have any questions.
Thanks to all the developers of Z1. ?
Click to expand...
Click to collapse
COS 12.1 sim selection was working out of the box.
CM 13 selection was working
LOS 14.1 selection stopped working
Flashed ZUI selection is back
& then clean flashed LOS again selection keeps working
Thanks a lot.
It must be radio baseband issue.
Sent from my ZUK Z1 using Tapatalk

Suggestion
Simply I tried this at my own,
And it worked!
Steps :
1. Install Lineage OS ROM from TWRP. (don't install Gapps)
2. Restart your android.
3. Skip all the startup steps after booting-up.
4. Now go to SIM settings and you see, you are able to select SIM for calls.
5. Select any SIM of your choice.
6. Reboot again into TWRP & install Gapps.
7. Reboot into system.
Now you see, you are able to select any SIM of your choice. :good:

Well...try updating kernel...it worked for me...try radioactive kernel(Radioactive reborn acuicultor) for nougat....here is the process
1)Go to twrp/cwm recovery
2)Perform factory reset and wipe dalvik,data,cache,system
3)first install any nougat rom then install any gapp package for nougat and finally the radioactive reborn kernel for nougat
4)reboot
Bam you are there...should work fine

https://forum.xda-developers.com/zuk-z1/help/network-solution-grayed-solved-t3545218

Can anyone help me in camera issue on nougat....after the clean flash when i open default camera app it works fine in auto mode but when switched to hdr mode then it crashes and says unknown error or cannot connect to camera this error occured in all the nougat rom excpet for los 14.1...Now for los 14.1 camera app works fine for few hours then it lags lije hell touch focus doesnt respond....plzz help

Hello! Im in a bit of a pickle! I have installed the [TWRP]ZUI v2.5.306 through TWRP in hopes to fix the Sim2 slot. Now I cannot access TWRP to try installing Nuclearom back! Now I am stuck with this nougat ZUI. How do I get TWRP back, do I have to ADB Fastboot again? Is it possible that ZUI overwrote my TWRP recovery? Hardware button combination to access TWRP is Vol + and Power at the same time right?

happyflyingipis said:
Hello! Im in a bit of a pickle! I have installed the [TWRP]ZUI v2.5.306 through TWRP in hopes to fix the Sim2 slot. Now I cannot access TWRP to try installing Nuclearom back! Now I am stuck with this nougat ZUI. How do I get TWRP back, do I have to ADB Fastboot again? Is it possible that ZUI overwrote my TWRP recovery? Hardware button combination to access TWRP is Vol + and Power at the same time right?
Click to expand...
Click to collapse
To access the Recovery you have to press the three buttons at the same time (vol+ / vol- / power).
Enviado desde mi ZUK Z1 mediante Tapatalk

happyflyingipis said:
Hello! Im in a bit of a pickle! I have installed the [TWRP]ZUI v2.5.306 through TWRP in hopes to fix the Sim2 slot. Now I cannot access TWRP to try installing Nuclearom back! Now I am stuck with this nougat ZUI. How do I get TWRP back, do I have to ADB Fastboot again? Is it possible that ZUI overwrote my TWRP recovery? Hardware button combination to access TWRP is Vol + and Power at the same time right?
Click to expand...
Click to collapse
Just use "adb reboot recovery" in CMD with USB debugging enabled. Won't have to bother with key combinations. ZUI is installed on system, boot partition, and updates modem partition. Doesn't touch the recovery partition.

Need help getting LineageOS to be stable (15.1 UNOFFICIAL, hltevzw, TWRP 3.3.0)

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.

Best Boostack (A2017G or Universal) for installing Pie Roms

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.

Popup camera not working on xiaomi mi 9t with custom ROM

After smashing my head against the limits of the MIUI again, i decided to say goodbye to my warranty and flash a custom rom. Via TWRP I flashed the latest (stable) version of Arrow OS based on android 10Q. Everything works perfectly aside from the popup camera, that appears to be firmly locked in place feeding live feed from inside the chassis. Thinking it was an error of that release, i tried other ROMs, both Android 9 and 10, ResurrectionRemix, Lineage. With RR the problem is the same, while with Lineage, the camera asks for a calibration: it actually pops out fully does two or three pops and then it says calibration failed. The servos are working, I've opened the chassis and found no dust at all, so I've looked for a fix online. The most common one is a flash of the stock 'persist.img' image, I've tried several times via TWRP, tried a few clean flashes (ROM+image) of different versions and nothing. Am I missing something? I don't want to get back to MIUI...

Did u backup your persist partition before ? if no u can flash any other one that comes in the fastboot stock rom but u will loose L1 (netflix in HD)

The problem persists.
Badis st said:
Did u backup your persist partition before ? if no u can flash any other one that comes in the fastboot stock rom but u will loose L1 (netflix in HD)
Click to expand...
Click to collapse
I did, but even when I tried flashing different versions of persist.img ranging from fastboot stock firmware 10 to 12, with and without backup, (clean wipe, fresh recovery) the problem was still present. I'm no expert but I'd guess the OS doesn't know how to: either tell the servos to pop the camera out (Arrow OS) or recognizing the camera working when calibrating (Lineage OS). I'm trying to dig my way to the cam app in the MIUI release and to install it in the custom ROM, but I don't think it works.