I have a question for all of you that managed to install /e/ A12 onto your Note 10+. Or perhaps any other version for that matter…
I have flashed many devices so far, inkluding /e/ so I am not a complete newbie even tho i haven’t been working with newer devices like Note 10+. I am asking because i have a Note 10+ and i can’t seem to flash anything into it and i am afraid it might have something to do with it’s firmware being updated recently. Because I’ve read on xda that there were other devices from approximatelly same generation that can become unflashable after updating to the most recent firmware somewhere in the beginning of januari this year.
So now i am considering buying another Note 10 plus that has not been updated recently. But then i read that /e/ does not OTA automatically upgrades from A11 to A12 but it has to be done manually and in worst case you have to flash stock A12 first in order to be able to flash /e/ A12. And if I do that I see a risk of me making another not cheap a device unflashable.
I wrote the info on the versions you asked about directly into your text. And i must admit my experience is not sufficient to really understand your answer. But it’s not only /e/ that is unflashable, the TWRP too. Nothing goes in…
@aibd sez:
This is something of a “rolling issue”, the important thing that can be a blocker for a month or so are the two Security Patch Levels (SPL). My interpretation, loosely speaking, might be that the device was “unflashable” that month, but hopefully one can wait for /e/OS to “catch up” with SPL.
Please tell us what you see for both SPL on your device
Settings > About phone > Android version …
Android security patch level: 1.jan 2023
Vendor security patch level: i can’t find this one. Where is it?
here we can see that security patch level is from january for latest samsung firmwre, and here we can see that security patch level is also from january for latest e-1.9-s
so you need to downgrade to N975FXXU8HVK3 or wait for the next /e/ release
what is your installed baseband ?
Thank you for answering, but i can’t flash anything to the phone, not TWRP either.
Do i understand correctly:
You are suggesting I sideload stock rom that is older? I think i was on that one already when it didn’t want to flash anything, then i updated to the latest one. That means i have to go several versions back. Isn’t there a risk of bricking the damn thing?
Baseband: N975FXXS8HVL3
“L” is for december so it is OK, but you probably have forgoten to flash the vbmeta.img along the recovery.img flashing
but Baseband: N975FXXS8HVL3 is a part of the firmware from january N975FXXS8HWA3
so you need to downgrade to N975FXXU8HVK3 or wait for the next /e/ release
windows or Linux/macOS ?
what is your country/CSC ?
No, i didn’t. I was very careful to include it in the flashing since on the twrp site they wrote that otherwise there was a risk of bricking the device…
And when i try heimdal and adb the device is listed as … unidentifed, or something like that. And no workarounds helped there…
Yes. I was carefull with that also. Tried to follow exactly your tutorial for the device. The bootloader was unlocked and i made sure it remained unlocked after connecting to wifi again after unlocking it.
Or you mean the wifi should remain open when turning the device off beforw thw flashing process? I thing i switched it off when i made sure the bootloader was unlocked.
There was one thing unusual tho when i boot to bootloader: there was scripts on several asian languages, and i’ve never seen that on bootloaders before…
have you trying plug / unplug ?
some old device must boot to download mode before to be plugged
some recent have to be plugged to boot in download mode
)