Database Users

OP2 kernel problems, considering H2OS?

Hi all, I am new here. I was referred by a friend who knows more about this than I do. I think I understand how to get fastboot and TWRP, so that is taken care of already. Now the problem with my OP2 running OxygenOS latest version, everything stock, is that it freezes up after unlocking, and the whole phone is just terribly throttled at this slow speed for a long time. All inputs are extremely delayed, and touchscreen is nearly unusable after the lag begins. There are so far two temporary fixes I found: 1) reboot phone 2)wait it out/keep unlocking until it doesn't lag. I also have been unable to make a copy of my internal storage via USB, as it gives unspecified error during copying. And lastly, the screen dims on its own sometimes at random while anything related to auto-brightness should be off. Fortunately, I was able to make a hard copy of my internal storage thru some wifi file manager apps. Now my friend pointed out that my phone's issues could be related to a bad kernel. To remedy this, he told me it would be good to flash a new kernel onto my phone. I considered changing roms to CM, but apparently a lot of functionality is lost when doing this. He told me that I could retain Oxygen OS while flashing a new kernel, but I am not sure how to do this. I came across a post in the android dev section regarding hydrogen os, and I read that it performs better than Oxygen OS, but has minor issues of its own. I am interested in flashing this rom/kernel (I am not sure which is which). Here is the link in that section of the forum I found http://forum.xda-developers.com/oneplus-2/development/rom-h2os-hydrogen-os-ota-clean-stable-t3195636. I see it says that it is working on Indian OP2, and running stock rom and stock kernel. Does this mean that my north american OP2 won't be able to get this rom? Also if it is the stock kernel, does that mean it is the same kernel as the one currently installed on my phone? Anyways, if anyone knows about my phone's problems, or has a way to fix it let me hear it please. Thank you!

Tzheng456 said:
Hi all, I am new here. I was referred by a friend who knows more about this than I do. I think I understand how to get fastboot and TWRP, so that is taken care of already. Now the problem with my OP2 running OxygenOS latest version, everything stock, is that it freezes up after unlocking, and the whole phone is just terribly throttled at this slow speed for a long time. All inputs are extremely delayed, and touchscreen is nearly unusable after the lag begins. There are so far two temporary fixes I found: 1) reboot phone 2)wait it out/keep unlocking until it doesn't lag. I also have been unable to make a copy of my internal storage via USB, as it gives unspecified error during copying. And lastly, the screen dims on its own sometimes at random while anything related to auto-brightness should be off. Fortunately, I was able to make a hard copy of my internal storage thru some wifi file manager apps. Now my friend pointed out that my phone's issues could be related to a bad kernel. To remedy this, he told me it would be good to flash a new kernel onto my phone. I considered changing roms to CM, but apparently a lot of functionality is lost when doing this. He told me that I could retain Oxygen OS while flashing a new kernel, but I am not sure how to do this. I came across a post in the android dev section regarding hydrogen os, and I read that it performs better than Oxygen OS, but has minor issues of its own. I am interested in flashing this rom/kernel (I am not sure which is which). Here is the link in that section of the forum I found http://forum.xda-developers.com/oneplus-2/development/rom-h2os-hydrogen-os-ota-clean-stable-t3195636. I see it says that it is working on Indian OP2, and running stock rom and stock kernel. Does this mean that my north american OP2 won't be able to get this rom? Also if it is the stock kernel, does that mean it is the same kernel as the one currently installed on my phone? Anyways, if anyone knows about my phone's problems, or has a way to fix it let me hear it please. Thank you!
Click to expand...
Click to collapse
I had the same issue with O2. I changed kernels and the problems persisted. A also word the device and started from scratch through fastboot and the issues persisted. I ended up on hydrogen and I've never looked back. There is a flashable zip in that thread for the newest full version .11. Follow the steps wipe everything besides internal storage, flash the full v11 zip and boot the phone. After this reboot to recovery (power and volume down). Flash the gapps and super su zip if you want root. After this you should be able to add your Google account and be good to go. One thing I did was remove all Chinese apps and the stock launcher. I use trebuchet launcher from cm 12.1. Phone runs incredibly smooth now. I recently started running AK kernel as well. The oxygen version works with hydrogen. I have been averaging between 5 and 7 hours of SOT for battery with up to 8 if I'm just watching videos. Hope this helps. The ROM is a little simpler and the notifications settings are different. But you can set apps to have priority notifications and they function similar to oxygens notifications at that point. Everything is in the thread if you have any questions I'll try to help you.

SM-910F with custom ROM shuts off on boot

Hi there, first off please forgive me if I get any terminology wrong - I've been learning way more about this than I ever intended...
I have a Galaxy Note 4 (SM910F / trltexx) that's causing me problems with custom ROMs - the phone gets to various points of the startup process, then either shuts off or reboots.
I'm posting this in the Note 4 forum as it happens with all the following ROMs:
- LineageOS 14.1
- Resurrection Remix 5.7.4 / 5.8.0 / 5.8.3
I assume that either there's something screwed up about the phone itself, or I'm missing something fundamental about what ROMs I'm installing.
When I first install the OS (adb sideload), it will boot up the first time around just fine.
On occasion (with all of the above) the phone has gotten all the way to the initial configuration screen (e.g. select a wireless network). I've tried all types of wipe and format/reset, both clean and dirty flash, no difference. The point to which it gets in the boot process seems random. When the phone is connected to a charger, it will try to reboot. If it is not connected, it just shuts off.
Stock Samsung firmwares (5.0.1 and 6.1.1) with stock recovery all worked fine.
Recovery is TWRP v2.8.7.0 (that's the only one I could get running, 3.x would not start up)
I've recently had the screen replaced, the shop did a poor job (my proximity sensor started acting up, I first tried replacing it, then tried the electrical tape spacer trick, which worked.) I'm also using an aftermarket Anker battery, for what it's worth (they're great, btw).
Any ideas? As mentioned it seems to boot ok with stock firmware, but I don't want to run stock because that's no fun.
Thanks for any ideas!

Bluetooth pairing lost after every reboot

Hello,
Am I the only one with this problem? Bluetooth loses all paired devices after every reboot...
- no problem pairing with any BT device
- after every reboot some or all previously paired devices are completely gone/missing from the list of paired devices.
- after wiping Dalvik/Cache in TWRP, they all show up again and can be paired without going through pairing (until next normal reboot).
- some device on the paired list may be lost permanently even after wiping Dalvik/Cache IF some new BT devices have been added or deleted. In this case a new pairing procedure is needed, as if the device(s) was never paired before.
It seems some devices are more "sensitive" than others. For example a BT mouse may still be on the paired list after reboot while the car BT (Toyota Venza) will always, invariably disappear from the list. In the car, as it tries to connect, the phone will keep asking for randomly generated pairing codes, which the car will not recognize until the phone gets added/paired again. On the other hand, the phone never disappears from the list of paired phones in the car's BT menu.
Just a thought: it's definitely a phone issue rather than a BT device issue (any). Whether connected or not, within or out of range, the phone will always loose the list of paired devices after a reboot.
Phone: SM-G950F (AQH3)
CSC: XEU (UK & Ireland) / Used in Canada on Virgin Mobile
Rooted with Magisk
Thanks!

Same Problems
Hello, I got the same problems. After seeing that this post is a little older, did you found a solution to this?
Need to try the dalvic/cache solutions next reboot.

Some (unknown) system modifications are the culprit! You need to reinstall the firmware (fresh install) using Odin (all sections, not just AP) and most importantly, during the installation of TWRP make sure you do NOT ALLOW SYSTEM MODIFICATIONS (do not use the slider)..

Just started having this very issue recently. Rooted Snapdragon S8+
Used to ok fine remembering all BT devices after a reboot. Just last week, started to notice I would have to start over pairing all my devices after a reboot. Ex: Car Sync, Gear S3 Frontier, Various Earbuds.
I don't have Twrp recovery due to the locked bootloader. I suspect it could be an app, however, no idea where to begin.... Any advice?

Unlikely for an app to do that, unless the app changed your system. Although I'm not sure what really causes it, I know that "some" system modifications do that. At some point I created shortcuts of some hidden settings, using Activities, which caused that to happen again. I didn't have to go through the hassle of reinstalling everything fresh through Odin since I've had a recent TWRP backup and I've restored both, the System and Data. I've lost many hours trying to figure out what exactly causes it but I didn't get any further than figuring out that: (1) some system modifications cause this to happen and (2) reflashing firmware through Odin without allowing any other system modifications during the process, is the ONLY WAY to get back the normal BT behavior.

Any fix for this
I have started getting this on my rooted S9+
Started to get annoying now.
I have stock rom, custom Kernal and magisk.
What resolved yours in the end?

It seems to be an Xposed issue: https://github.com/rovo89/Xposed/issues/294

Despite the apparency, I don't think this is caused by the XPosed framework. As I've detailed above, the problem may occur even before installing XPosed. Even with XPosed installed, everything may be running just fine indefinitely, until certain system modifications seem to be triggering this problem. Although I pointed out before that this would most certainly happen if, during the TWRP installation, system modifications are allowed (by sliding the bar), I'm almost sure that TWRP in itself is NOT the culprit. The same may be said about XPosed. While both may seem to potentially be triggering the issue, I don't think they really are the cause. My feeling is that the real cause is Samsung's native system (possibly one specific application). I've noticed, for example, that when the problem occurs, while Android loses the list of previously BT paired devices either partially or completely, Samsung's Connect still sees them all - as if nothing happened. How is that possible? It's just assumptions at this point but one thing is certain - after freezing Samsung Connect (Smart Things), I've never had the issue again.
As for permanently resolving this once it happens, there seems to be ONLY two ways:
1. Start fresh by re-flashing the stock ROM through ODIN and if TWRP is also installed, system modifications should not be allowed at this time, or.
2. If you already had TWRP installed and had a nandroid backup (System and Data) done before the problem occurred, (1) wiping system and data and then (2) restoring their respective previous versions, definitely solves the problem, without having to go through ODIN everything fresh.
I hope this helps, and I also hope that someone could eventually identify the root cause and address this once and for all. I definitely wouldn't hold my breath counting on Samsung's help!

Note 10 + sm-n975f
Rooted with Magisk
Definitely not an exposed issue because I am not using exposed, never had exposed on this device.
Same problem with 2 different phones of the same model. One was a international dual sim and the other international single sim.
2 other problems,
Sometimes incoming call notification sound can be heard but no incoming call shows up on the screen (ie. Answer /decline. No missed call notification either, only a new voicemail notification, but if they do not leave a message then you would not know who called. lol
Other issue is Sammy is putting music apps to sleep randomly even though I used an app to set screen time out to never.
Never had any of these problems on any other rooted device always used note phones. Ready to get an Exynos note 8, got the 10 because thought it was cool and I was using the note 8 previously with SamFAIL. Too many glitches though.
Man Sammy is failing big time as usual. Never had this foolishness on any other note always been using rooted notes. (exceptffor note 9) Every Sammy support agent acts like they never heard of this before. I see a bunch of note 9 users on shameful Sammy's forums having this exact Bluetooth problem, shame on Sammy's lies and ignorance!
Update :
Found this Magisk fix, This file name is
nfsinjector-956.zip
Flashed with Magisk module manager.
Update : still not working

From experience, I can confirm that a failsafe way to ALWAYS get back all previously stored BT paired devices is to wipe your Dalvik/cache in TWRP.
I'm still on a Samsung S8, rooted with Magisk + TWRP and XPosed. Once in a while I get this BT issue and the above suggested solution always worked for me. Let me know if it works for you.
As for the rest of the problems, I'm really disappointed to hear that. I was planning on buying myself a Note 10 but that makes me rethink it - it pretty much was THE REASON I held back for so long.
I always suspected this had nothing to do with the XPosed framework but every one on Earth, including the devs, swear by it. Well, you just confirmed it.

Xposed had this issue on s8 we had found a fix somewhere. It may not be present on newer versions. Modifying the libs or something. I studied into it. It's even in the github for xposed. So for me it was most definitely xposed

Thanks for the wipe cash fix, I would like to try it, but not sure if I can since I don't have twrp, can twrp be installed on a Exynos note 10?
Is Its possible that the xposed fix is actually fixing a Samsung failure and not an xposed problem to begin with in the place?
all those people on the note 9 shameful Sammy fourms I assume are unrooted users!

Xposed had always had issues on Samsung's. Until s7 or 8 it was modded by Rovo. The s8 didn't need rovos xposed.

Can anybody help me

will be that you can support me on something about this device, a while ago I wanted to install a rom lineage 15.1 and had many bugs, one of them was that Dolby stopped audio did not want to open, so I decided to change it to stock again using minimal adb, and all good, I start the cel, but the problem continued, and restart it I get a message like 10 times in a row that says "daxUser stopped" after that, I skip another window where it says the "internal system is damaged and may be unstable to restore the cell phone factory "and I do not know what to do because I have already installed the rom allegedly stock several times and it does not take off in fact does not sound at all, the speaker is dead, I can not make calls, if the resiven but nothing is heard, it no longer connects to wifi, it leaves the few applications without any reason. ect etc, I hope you can support me with that, and if there is any solution it would be great.

Unroot, lock and take it back for repairs? Sorry, not very XDA-style answer.
Edit: are you completely sure that you flashed the right stock ROM for your device?

Try again
Alvaro Luna said:
will be that you can support me on something about this device, a while ago I wanted to install a rom lineage 15.1 and had many bugs, one of them was that Dolby stopped audio did not want to open, so I decided to change it to stock again using minimal adb, and all good, I start the cel, but the problem continued, and restart it I get a message like 10 times in a row that says "daxUser stopped" after that, I skip another window where it says the "internal system is damaged and may be unstable to restore the cell phone factory "and I do not know what to do because I have already installed the rom allegedly stock several times and it does not take off in fact does not sound at all, the speaker is dead, I can not make calls, if the resiven but nothing is heard, it no longer connects to wifi, it leaves the few applications without any reason. ect etc, I hope you can support me with that, and if there is any solution it would be great.
Click to expand...
Click to collapse
I have a Retla and received official 9.0. download the 89-2 stock firmware. You can find it here. Use the .bat
File, place inside extracted firmware click & when it restarts you should get a notification to download 89-5.. once it completes the next notification will appear.. that's 116-11 9.0..
mod edit - telegram chat spam removed

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.