Related
Hi all,
Earlier this week my HTC One Mini got stuck in an unstoppable bootloop. I couldn't even access fastboot/recovery, as everytime I booted into HBOOT the device would restart itself.
Thanks largely to the troubleshooting threads and the assistance of a few *extremely* helpful xda members, I've now escaped the clutches of the bootloop and I can boot into tr1gg3r84's 4.3 stock ROM.
However, my issues haven't been entirely fixed. The phone appears to boot up with no problems but when I try and use it, it'll hang for a second before unexpectedly rebooting. This is happened a number of times - within settings, within Play Store and sometimes whilst on standby when I'm not even touching it.
On top of that, the phone won't power off (even after deactivating fast boot in Settings > Power). I have tried powering off normally and in HBOOT - the screen goes dark for about 5 seconds, and then powers on again.
I thought I was out of the woods once the bootloop was fixed, but I'm at my wit's end.
Procedure I followed with current ROM:
- Wiped system, data, cache, and dalvik (TWRP)
- Installed Stock2.12.401.1Deodex(tr1gg3r84).zip
- Installed SuperSU update
- Rebooted into recovery
- Rebooted into bootloader
- Flashed boot.img from zip
At this point I attempted to start recovery from HBOOT in order to wipe cache and dalvik again - I got the purple 'Entering Recovery...' text but then the screen went black and rebooted as normal. After the phone booted for the first time, I enabled USB debugging and used 'adb reboot recovery' to get back into TWRP and wipe cache & dalvik.
Can anybody help?
Try following this thread.....reflash the OTA
---------- Post added at 02:09 AM ---------- Previous post was at 02:07 AM ----------
http://forum.xda-developers.com/showthread.php?t=2573479
I have the same thing
the only way i can power it down is through the bootloader menu. Pain in the ass but it is a solid work around.
Macko mia said:
Try following this thread.....reflash the OTA
---------- Post added at 02:09 AM ---------- Previous post was at 02:07 AM ----------
http://forum.xda-developers.com/showthread.php?t=2573479
Click to expand...
Click to collapse
Thanks for the tip, I'll give it a try.
elmuziko said:
I have the same thing
the only way i can power it down is through the bootloader menu. Pain in the ass but it is a solid work around.
Click to expand...
Click to collapse
I did try that, but all I get is a black screen for 2~ seconds then the phone powers back on.
Hi guys, my sister has this phone and she has the following problem: the phone keeps crashing just after inserting the PIN (it says that the process.gapps or process.swiftkey has stopped working). We don't even have time to reach settings. I went in recovery mode (TWRP 2.8.0.0) and wiped data, system, etc, but after the reboot I noticed that the phone was in the exact same state it was before factory reset! Flashing a new ROM is not working either. I tried to change and downgrade recovery, but nothing. I also tried Original Firmware and Vol+, Vol-, Power, but it says
"update exception
emmc is readonly, you can't update your system"
Any suggestion? ADB does not find it in fastboot mode.
Hi, thank you fur using XDA Assist. There seems there are a number of variants of your phone so I don't know if this will work, but try this,http://forum.xda-developers.com/showthread.php?t=2452430
Thread closed.
my honor 8 is stuck on honor 8 blue screen, cant turn it off.
cant access fastboot, recovery or even dload. only vibrates twice.
can anyone help me to solve this issue???
abbassbhai said:
my honor 8 is stuck on honor 8 blue screen, cant turn it off.
cant access fastboot, recovery or even dload. only vibrates twice.
can anyone help me to solve this issue???
Click to expand...
Click to collapse
Have you tried to flash custom ROMs or TWRP?
overcustom said:
Have you tried to flash custom ROMs or TWRP?
Click to expand...
Click to collapse
i was trying to dload mm firmware. The firmware dloaded fine but after factory reset and reboot, the fone is jus staying on honor screen after 3d text. i tried to go in erecovery but cannot, fone jus vibrates twice and then after 3d honor text, it stays on blue honor screen forever.
i tried to boot in fastboot as well as dload.....same thing happend not booting in fastboot or dload.
only 3d text and blue screen.
now fone doesnt even turns on if power button pressed ,but juss vibrates twice and blue screen after 3d text.
Leave your device as it is so that the battery is fully drained and is powered off. Then plug your device to charger for 5 minutes. Unplug it and now try to boot to recovery.
Hold the power button and volume up button until you hear the first vibration and screen goes on. Leave both buttons. Now you can go to recovery. Perform a full factory reset. Then power off your device and move the dload package to your external SD card. Repeat the same process but this time hold both volume buttons and power button.
hackslash said:
Leave your device as it is so that the battery is fully drained and is powered off. Then plug your device to charger for 5 minutes. Unplug it and now try to boot to recovery.
Hold the power button and volume up button until you hear the first vibration and screen goes on. Leave both buttons. Now you can go to recovery. Perform a full factory reset. Then power off your device and move the dload package to your external SD card. Repeat the same process but this time hold both volume buttons and power button.
Click to expand...
Click to collapse
thankyou bro for ur suggestion...i already tried all tht but no luck.
the fone turns on everytime whatever i try to do....only 3d text and it is stuck on blue honor screen.
no recovery dload fastboot etc.
Hi. Sorry the revive.
Could you solve this? I'm in the same situation
No unlock, can't enter to recovery, can't enter to erecovery so I can't flash with dload, fastboot is a joke if the phone has locked bootloader so I can't reflash the recoveries.
abbassbhai said:
my honor 8 is stuck on honor 8 blue screen, cant turn it off.
cant access fastboot, recovery or even dload. only vibrates twice.
can anyone help me to solve this issue???
Click to expand...
Click to collapse
Noivern said:
Hi everyone!
First, sorry reviving the threadm but this one is similar to my trouble.
Second, every flash process was done with dload method and vol + - and power combination.
Third, I never unlock my phone before or flashed any custom rom or recovery, everything was stock.
Last night, I tried to rollback my honor 8 frd-al19 to emui 6.0 with proper rollback package and firmware for Android 6.0 (both official and for my model), but phone went into boot lock. It isn't boot loop, It's stuck on the Honor blue logo. I can't even turn off the phone.
I did this procedure once before with success. I was on fdr-al19c432b360 firmware 100% functional (I was an idiot to rollback again when not needed at all... I know). I applied the rollback package correctly, and then I did a mistake and flashed full c636b131 Android 6.0 firmware instead of c432b131 Android 6.0.
Phone started ok with everything working. But I noticed my bad (emui didn't find any update package from OTA, and noticed the error in version model shown) and reflashed rollback package... At this point is where I think I messed up the recoveries or something. When ended the flashing process, I copied the correct firmware (the c432b131 android 6) on dload folder and tried again to flash.... but this time phone never entered on erecovery nor recovery. Only thing I get is stuck honor blue screen. It refuses to enter on recovery or erecovery. It just reboots, vibrate twice and keeps stuck after that on honor screen.
Strange thing, is that I did this procedure once before some months ago with success, but that time I didn't make the mistake with the versions.
After panic, I tried to boot in fastboot connected to my pc, and HiSuite knows there is something connected, because it launches it self, but don't recognize the phone and says it can't be recovered. Also, Adb don't see the phone either, only fastboot.
With fastboot commands I tried to reboot into recovery and nothing happened. Then wipe cache/user data, reflash stock recovery. Everything failed with message "remote: not allowed". And of course, because I never unlocked my bootloader. Fastboot says phone locked, frp locked (was frp, don't remember now exactly).
Then, I read about to let the battery die. I did. That didn't work either, phone keeps stuck on honor blue logo.
I downloaded multitool for huawei software, and everything requires an unlocked bootloader to recover.
Then, I tried to get unlock code, but huawei site ask me product id which I can't get because phone is bricked (I have all other data, imei, serial, etc.) . Tried with id generator too, and nothing what I tried have work so far. It's frustrating.
I'm pretty hopeless now, no unlock, no recovery, no erecovery, so I can't flash anything on the damn phone to try to recover it.
Can I save my phone or is it just an expensive brick? Any help will be REALLY welcome.
:crying:
Click to expand...
Click to collapse
Well, is a bit silly to answer yourself but this can help someone else:
I did purchase a license of 3 days of dc phoenix software and force updated version android 6.0 c432B131 on my honor 8 fdr L19.
It flashed ok, but software said that couldn't install update. On phone went to 99% for long time (more than 1 hour).
So I looking for some info, and also the software said that I had to manually update. I just copied the same rom with dload method: just the same UPDATE.APP on the folder, and tried the 3 buttons: It worked!
After a success bootup, it found inmediatelly (OTA) the update to android 7, c432b360 firmware and downloaded and installed.
Here went something strange: after updated again via OTA, everything was working ok, but on about phone, the version shown wasn't the c432b360. Instead it said something about test keys build. Just for being safe, I tried to full reset the phone and... it failed. It said failed on erecovery menu, and after that, the next boot up I couldn't pass over wifi setting menu: keyboard was missing and it just tried to talk to text input. Another panic moment, so I tried to enter on recovery to clear cache and reset user with no luck. After that, phone refused to start showing an error message on fastboot screen: "phone couldn't pass verification, it may not function properly".
What to do? just do all the things again, but just with dload method. As I was on android 7, first I installed downgrade package. Ok, it did well. After, installed again c432b131 (android 6). And finally success!.
Once again, phone ask for install OTA android 7 and I let it. Now, I just didn't tried to do a factory reset and so far is ok.... but it hasn't AOSP Android keyboard anymore. So far is working ok, everything is working: wifi, phone, 4g mobile internet, nfc, sensors, apps, gps, compass... so I'm pretty happy now, but not sure what happened when I tried to factory reset and what happened to AOSP Android keyboard.
Noivern said:
Well, is a bit silly to answer yourself but this can help someone else:
I did purchase a license of 3 days of dc phoenix software and force updated version android 6.0 c432B131 on my honor 8 fdr L19.
It flashed ok, but software said that couldn't install update. On phone went to 99% for long time (more than 1 hour).
So I looking for some info, and also the software said that I had to manually update. I just copied the same rom with dload method: just the same UPDATE.APP on the folder, and tried the 3 buttons: It worked!
After a success bootup, it found inmediatelly (OTA) the update to android 7, c432b360 firmware and downloaded and installed.
Here went something strange: after updated again via OTA, everything was working ok, but on about phone, the version shown wasn't the c432b360. Instead it said something about test keys build. Just for being safe, I tried to full reset the phone and... it failed. It said failed on erecovery menu, and after that, the next boot up I couldn't pass over wifi setting menu: keyboard was missing and it just tried to talk to text input. Another panic moment, so I tried to enter on recovery to clear cache and reset user with no luck. After that, phone refused to start showing an error message on fastboot screen: "phone couldn't pass verification, it may not function properly".
What to do? just do all the things again, but just with dload method. As I was on android 7, first I installed downgrade package. Ok, it did well. After, installed again c432b131 (android 6). And finally success!.
Once again, phone ask for install OTA android 7 and I let it. Now, I just didn't tried to do a factory reset and so far is ok.... but it hasn't AOSP Android keyboard anymore. So far is working ok, everything is working: wifi, phone, 4g mobile internet, nfc, sensors, apps, gps, compass... so I'm pretty happy now, but not sure what happened when I tried to factory reset and what happened to AOSP Android keyboard.
Click to expand...
Click to collapse
A late answer but maybe useful for some
Because the OTA showed up, was not a full OTA file. I guess it was only 1.3 gb something. It was a test build and didnt have any apks inside including the keyboard. And also not a stable one (test build) So it is always better to download FULL package from the menu and flash that one.
Hey,
I need some help with this problem. I have a frd lo4 on nougat. I tried to return to stock from being rooted. The dLoad folder method wasn’t working (returned invalid package) so I unrooted via the SU app, flashed stock recovery, and went into fastboot and relocked the bootloader with the code.
Now it won’t boot or shut off. Just a bootloop showing the blue screen. I could use to access fastboot before but now my pc doesn’t detect my phone. I’ve tried different ports and pc’s. I can’t access recovery either.
Any help is appreciated
EDIT: I let the battery die, then tried going into fastboot mode and it worked. I flashed the stock recovery 1 and 2. I then used the correct rollback package and put it on my sd card then flashed. I then downloaded the full 6.0 firmware and did the same. Now I’m unrooted, locked bootloader, and stock.
Hope this helps someone.
Excatly the same thing happened to me 1 week ago.. My phone was going on bott loop in recovery mode.. I tried Dload method and recovery but nothing happened.. atlast i let the battery die. After the battery is completly dead i connexted the charger and hola the adb is working now. Then i flashed correct recovery and rom. Ecerything is working fine now.
Hi everyone!
First, sorry reviving the threadm but this one is similar to my trouble.
Second, every flash process was done with dload method and vol + - and power combination.
Third, I never unlock my phone before or flashed any custom rom or recovery, everything was stock.
Last night, I tried to rollback my honor 8 frd-al19 to emui 6.0 with proper rollback package and firmware for Android 6.0 (both official and for my model), but phone went into boot lock. It isn't boot loop, It's stuck on the Honor blue logo. I can't even turn off the phone.
I did this procedure once before with success. I was on fdr-al19c432b360 firmware 100% functional (I was an idiot to rollback again when not needed at all... I know). I applied the rollback package correctly, and then I did a mistake and flashed full c636b131 Android 6.0 firmware instead of c432b131 Android 6.0.
Phone started ok with everything working. But I noticed my bad (emui didn't find any update package from OTA, and noticed the error in version model shown) and reflashed rollback package... At this point is where I think I messed up the recoveries or something. When ended the flashing process, I copied the correct firmware (the c432b131 android 6) on dload folder and tried again to flash.... but this time phone never entered on erecovery nor recovery. Only thing I get is stuck honor blue screen. It refuses to enter on recovery or erecovery. It just reboots, vibrate twice and keeps stuck after that on honor screen.
Strange thing, is that I did this procedure once before some months ago with success, but that time I didn't make the mistake with the versions.
After panic, I tried to boot in fastboot connected to my pc, and HiSuite knows there is something connected, because it launches it self, but don't recognize the phone and says it can't be recovered. Also, Adb don't see the phone either, only fastboot.
With fastboot commands I tried to reboot into recovery and nothing happened. Then wipe cache/user data, reflash stock recovery. Everything failed with message "remote: not allowed". And of course, because I never unlocked my bootloader. Fastboot says phone locked, frp locked (was frp, don't remember now exactly).
Then, I read about to let the battery die. I did. That didn't work either, phone keeps stuck on honor blue logo.
I downloaded multitool for huawei software, and everything requires an unlocked bootloader to recover.
Then, I tried to get unlock code, but huawei site ask me product id which I can't get because phone is bricked (I have all other data, imei, serial, etc.) . Tried with id generator too, and nothing what I tried have work so far. It's frustrating.
I'm pretty hopeless now, no unlock, no recovery, no erecovery, so I can't flash anything on the damn phone to try to recover it.
Can I save my phone or is it just an expensive brick? Any help will be REALLY welcome.
:crying:
Noivern said:
Hi everyone!
First, sorry reviving the threadm but this one is similar to my trouble.
Second, every flash process was done with dload method and vol + - and power combination.
Third, I never unlock my phone before or flashed any custom rom or recovery, everything was stock.
Last night, I tried to rollback my honor 8 frd-al19 to emui 6.0 with proper rollback package and firmware for Android 6.0 (both official and for my model), but phone went into boot lock. It isn't boot loop, It's stuck on the Honor blue logo. I can't even turn off the phone.
I did this procedure once before with success. I was on fdr-al19c432b360 firmware 100% functional (I was an idiot to rollback again when not needed at all... I know). I applied the rollback package correctly, and then I did a mistake and flashed full c636b131 Android 6.0 firmware instead of c432b131 Android 6.0.
Phone started ok with everything working. But I noticed my bad (emui didn't find any update package from OTA, and noticed the error in version model shown) and reflashed rollback package... At this point is where I think I messed up the recoveries or something. When ended the flashing process, I copied the correct firmware (the c432b131 android 6) on dload folder and tried again to flash.... but this time phone never entered on erecovery nor recovery. Only thing I get is stuck honor blue screen. It refuses to enter on recovery or erecovery. It just reboots, vibrate twice and keeps stuck after that on honor screen.
Strange thing, is that I did this procedure once before some months ago with success, but that time I didn't make the mistake with the versions.
After panic, I tried to boot in fastboot connected to my pc, and HiSuite knows there is something connected, because it launches it self, but don't recognize the phone and says it can't be recovered. Also, Adb don't see the phone either, only fastboot.
With fastboot commands I tried to reboot into recovery and nothing happened. Then wipe cache/user data, reflash stock recovery. Everything failed with message "remote: not allowed". And of course, because I never unlocked my bootloader. Fastboot says phone locked, frp locked (was frp, don't remember now exactly).
Then, I read about to let the battery die. I did. That didn't work either, phone keeps stuck on honor blue logo.
I downloaded multitool for huawei software, and everything requires an unlocked bootloader to recover.
Then, I tried to get unlock code, but huawei site ask me product id which I can't get because phone is bricked (I have all other data, imei, serial, etc.) . Tried with id generator too, and nothing what I tried have work so far. It's frustrating.
I'm pretty hopeless now, no unlock, no recovery, no erecovery, so I can't flash anything on the damn phone to try to recover it.
Can I save my phone or is it just an expensive brick? Any help will be REALLY welcome.
:crying:
Click to expand...
Click to collapse
Well, is a bit silly to answer yourself but this can help someone else:
I did purchase a license of 3 days of dc phoenix software and force updated version android 6.0 c432B131 on my honor 8 fdr L19.
It flashed ok, but software said that couldn't install update. On phone went to 99% for long time (more than 1 hour).
So I looking for some info, and also the software said that I had to manually update. I just copied the same rom with dload method: just the same UPDATE.APP on the folder, and tried the 3 buttons: It worked!
After a success bootup, it found inmediatelly (OTA) the update to android 7, c432b360 firmware and downloaded and installed.
Here went something strange: after updated again via OTA, everything was working ok, but on about phone, the version shown wasn't the c432b360. Instead it said something about test keys build. Just for being safe, I tried to full reset the phone and... it failed. It said failed on erecovery menu, and after that, the next boot up I couldn't pass over wifi setting menu: keyboard was missing and it just tried to talk to text input. Another panic moment, so I tried to enter on recovery to clear cache and reset user with no luck. After that, phone refused to start showing an error message on fastboot screen: "phone couldn't pass verification, it may not function properly".
What to do? just do all the things again, but just with dload method. As I was on android 7, first I installed downgrade package. Ok, it did well. After, installed again c432b131 (android 6). And finally success!.
Once again, phone ask for install OTA android 7 and I let it. Now, I just didn't tried to do a factory reset and so far is ok.... but it hasn't AOSP Android keyboard anymore. So far is working ok, everything is working: wifi, phone, 4g mobile internet, nfc, sensors, apps, gps, compass... so I'm pretty happy now, but not sure what happened when I tried to factory reset and what happened to AOSP Android keyboard.
Noivern said:
Hi everyone!
First, sorry reviving the threadm but this one is similar to my trouble.
Second, every flash process was done with dload method and vol + - and power combination.
Third, I never unlock my phone before or flashed any custom rom or recovery, everything was stock.
Last night, I tried to rollback my honor 8 frd-al19 to emui 6.0 with proper rollback package and firmware for Android 6.0 (both official and for my model), but phone went into boot lock. It isn't boot loop, It's stuck on the Honor blue logo. I can't even turn off the phone.
I did this procedure once before with success. I was on fdr-al19c432b360 firmware 100% functional (I was an idiot to rollback again when not needed at all... I know). I applied the rollback package correctly, and then I did a mistake and flashed full c636b131 Android 6.0 firmware instead of c432b131 Android 6.0.
Phone started ok with everything working. But I noticed my bad (emui didn't find any update package from OTA, and noticed the error in version model shown) and reflashed rollback package... At this point is where I think I messed up the recoveries or something. When ended the flashing process, I copied the correct firmware (the c432b131 android 6) on dload folder and tried again to flash.... but this time phone never entered on erecovery nor recovery. Only thing I get is stuck honor blue screen. It refuses to enter on recovery or erecovery. It just reboots, vibrate twice and keeps stuck after that on honor screen.
Strange thing, is that I did this procedure once before some months ago with success, but that time I didn't make the mistake with the versions.
After panic, I tried to boot in fastboot connected to my pc, and HiSuite knows there is something connected, because it launches it self, but don't recognize the phone and says it can't be recovered. Also, Adb don't see the phone either, only fastboot.
With fastboot commands I tried to reboot into recovery and nothing happened. Then wipe cache/user data, reflash stock recovery. Everything failed with message "remote: not allowed". And of course, because I never unlocked my bootloader. Fastboot says phone locked, frp locked (was frp, don't remember now exactly).
Then, I read about to let the battery die. I did. That didn't work either, phone keeps stuck on honor blue logo.
I downloaded multitool for huawei software, and everything requires an unlocked bootloader to recover.
Then, I tried to get unlock code, but huawei site ask me product id which I can't get because phone is bricked (I have all other data, imei, serial, etc.) . Tried with id generator too, and nothing what I tried have work so far. It's frustrating.
I'm pretty hopeless now, no unlock, no recovery, no erecovery, so I can't flash anything on the damn phone to try to recover it.
Can I save my phone or is it just an expensive brick? Any help will be REALLY welcome.
:crying:
Click to expand...
Click to collapse
did u solve this bro. Same here happened, no recover no erecovery but just fastboot mode working. I let the battery died but cant charge it now, charging light is just blinking.. I have unlocked bootloader..
Trying to root my phone. Flashed TWRP in Odin, then installed SuperSU through TWRP. At the end it gives me the error in the title, and I get a 'failed integrity check' when booting into the system.
Help?
I've always read you have to do a factory reset after TWRP installation due to encryption, but apparently you don't have to
It still says you lose your OS though.
https://forum.xda-developers.com/galaxy-s7/help/root-twrp-flashing-t3535545
AzzyC said:
No factory reset required. Basically, the file system of your Data partition is incorrect and that is why it can't be mounted on to.
Go to 'Wipe'->'Advanced Wipe'->Click on the Data box->'Partition Options'->(You may be seeing values like 0mb for most of the information displayed and why you can't mount to it; if you are not let me know!)->'Change File System'->(Try out different File Systems until you being to see true values for the sizes, but avoid using EXT2 and EXT3 if you can)
Doing all this you will be able to Mount to your Data partition, however your OS will be deleted! So get your phone into Download mode, open up Odin program on your PC, and flash a Bootloader (BL) and your phone will be fine.
Then flash the 'no-verity-encryption-opt.zip' and then your SU Binary and Xposed Framework etc.
Good luck again Buddy!
---------- Post added at 05:41 PM ---------- Previous post was at 05:12 PM ----------
Wait Install the No-verity zip first then, then flash a BL
Click to expand...
Click to collapse
It's a brand-new phone so I don't really care about the OS.
Also I tried restoring my Nandroid backup, but the drive appears empty when I go to the "Restore" option in TWRP. Not sure if I need to fix the data thing first anyway, but surely it should show up?
EDIT: Now that I think about it wasn't there some requirement to clear a cache at some point? I vaguely remember that from the last time I rooted an S7.
I've tried formatting, and the readout says "formatting" and then "Done.", but there's still a progress bar and the title area still says "Formatting...".
EDIT 2: It's plugged in but the battery is still dropping, and it only started at 8%. So it might just die anyway.
I recently went back and forth between Oreo and a TWRP Nougat backup, and was flashing TWRP each time I went up to Oreo because I was installing it via Odin which was blowing away TWRP.
I must have had to factory reset and flash the dm-no verity.zip a few times each TWRP install before I got /system and /data to not return an error. I was probably doing something out of order, but it always seemed finnicky.
How does one do the factory reset?
TWRP still reckons it's formatting, even though it says "Done.", but the battery has just hit 0% so it won't last much longer anyway.
EDIT: Or not...battery still going strong at apparently 0%. But it's been formatting for over two hours now.
Advanced wipe with data, cache, and davlik cache checked should be enough
When was I supposed to do that step? It rings a bell but it isn't in the instructions I found.
The phone finally died, and now I cant' seem to get past the TWRP splash screen.
EDIT: Just plugging it in results in the TWRP splash screen. None of the buttons seem to do anything, so I can't get into download mode and reflash TWRP or anything...
Okay, so I left it on the charger for a couple of hours.
Pressing and holding the power button turns it off. A few seconds after plugging it in, I get the Galaxy splash screen followed by the TWRP splash screen, and then the latter just stays there. Forever.
Once I turn it off, I'm unable to turn it back on at all - standard boot, recovery or download. I pressed and held the buttons for a full minute, made no difference.
EDIT: Leaving it off the charger results in the screen turning off a few minutes later. Again, no amount of pushing the buttons will do anything.
EDIT 2: Got it into download mode by plugging it in and holding the buttons down while waiting for it to automatically boot. Next step? Flash a bootloader, or reflash TWRP, or both?
Tried reflashing TWRP, changes nothing. Also tried flashing a BL and CP from the last time I installed SupermanROM, but it failed in Odin. Not sure if they're just too old or something, I have no idea how that stuff works or how updated my software is or anything.
It's the same handset I had before, but it had to go back to Samsung for repair because the battery blew up, so they very kindly wiped everything, reset Knox, etc.