Instant flash TWRP after OEM unlock - Samsung Galaxy S9 Questions & Answers

Just got Samsung Galaxy S9 yesterday, and wanted, of course, to install Lineage OS.
After some investigation I undestood that I need to wait 7 days after switching OEM Unlock in Developer options to flash unofficial recovery.
Fortunately found this video: https://www.youtube.com/watch?v=skyUCTs1cyI, followed instructions and it worked.
To be short:
1) Enable developers settings, and switch OEM unlock in it;
2) Turn phone to download mode, try to flash TWRP - it will be unsuccessfull with "Only official released binaries are allowed" (I've used heimdall on linux to flash);
3) Reboot phone into Android, disable automatic date and time and set it to round 10 days before security patch level (i.e. if your patch level is November 2019 you need to set date to 20-oct-2019);
4) Switch phone off, boot into Download mode again, flash TWRP again - now it would be successfull;
5) Reboot into TWRP not booting into Android (it will wipe recovery back), flash LineageOS / custom kernel / what do you want.
Tested on two different official firmwares (with 0ct 2019 and Nov 2019 patch levels) - it worked.
Also people in video comments say that it works for many Samsung phones.
Looks like universal backdoor in RMM check.
All credits go to https://www.youtube.com/channel/UCDq76mkkOcjn_3BDNyNtKOQ

FossaFX said:
Just got Samsung Galaxy S9 yesterday, and wanted, of course, to install Lineage OS.
After some investigation I undestood that I need to wait 7 days after switching OEM Unlock in Developer options to flash unofficial recovery.
Fortunately found this video: https://www.youtube.com/watch?v=skyUCTs1cyI, followed instructions and it worked.
To be short:
1) Enable developers settings, and switch OEM unlock in it;
2) Turn phone to download mode, try to flash TWRP - it will be unsuccessfull with "Only official released binaries are allowed" (I've used heimdall on linux to flash);
3) Reboot phone into Android, disable automatic date and time and set it to round 10 days before security patch level (i.e. if your patch level is November 2019 you need to set date to 20-oct-2019);
4) Switch phone off, boot into Download mode again, flash TWRP again - now it would be successfull;
5) Reboot into TWRP not booting into Android (it will wipe recovery back), flash LineageOS / custom kernel / what do you want.
Tested on two different official firmwares (with 0ct 2019 and Nov 2019 patch levels) - it worked.
Also people in video comments say that it works for many Samsung phones.
Looks like universal backdoor in RMM check.
All credits go to https://www.youtube.com/channel/UCDq76mkkOcjn_3BDNyNtKOQ
Click to expand...
Click to collapse
I used this method when i first got my S9+, and didn't want to wait, can confirm it works..

FossaFX said:
Just got Samsung Galaxy S9 yesterday, and wanted, of course, to install Lineage OS.
After some investigation I undestood that I need to wait 7 days after switching OEM Unlock in Developer options to flash unofficial recovery.
Fortunately found this video: https://www.youtube.com/watch?v=skyUCTs1cyI, followed instructions and it worked.
To be short:
1) Enable developers settings, and switch OEM unlock in it;
2) Turn phone to download mode, try to flash TWRP - it will be unsuccessfull with "Only official released binaries are allowed" (I've used heimdall on linux to flash);
3) Reboot phone into Android, disable automatic date and time and set it to round 10 days before security patch level (i.e. if your patch level is November 2019 you need to set date to 20-oct-2019);
4) Switch phone off, boot into Download mode again, flash TWRP again - now it would be successfull;
5) Reboot into TWRP not booting into Android (it will wipe recovery back), flash LineageOS / custom kernel / what do you want.
Tested on two different official firmwares (with 0ct 2019 and Nov 2019 patch levels) - it worked.
Also people in video comments say that it works for many Samsung phones.
Looks like universal backdoor in RMM check.
All credits go to https://www.youtube.com/channel/UCDq76mkkOcjn_3BDNyNtKOQ
Click to expand...
Click to collapse
Doesn't work on SM-960W with Dec 1,2019 security patch. I set it to 11-20-2019 ,amd tried to flash but it was unsuccessful

fbarcenas said:
Doesn't work on SM-960W with Dec 1,2019 security patch. I set it to 11-20-2019 ,amd tried to flash but it was unsuccessful
Click to expand...
Click to collapse
Could you try it with earlier official firmware? Saw in comments to video, that it helps.

Increase the date rather than decrease

fbarcenas said:
Doesn't work on SM-960W with Dec 1,2019 security patch. I set it to 11-20-2019 ,amd tried to flash but it was unsuccessful
Click to expand...
Click to collapse
Pretty sure
---------- Post added at 08:24 PM ---------- Previous post was at 08:15 PM ----------
fbarcenas said:
Doesn't work on SM-960W with Dec 1,2019 security patch. I set it to 11-20-2019 ,amd tried to flash but it was unsuccessful
Click to expand...
Click to collapse
Thought you couldn't unlock Snapdragon S9 or is that only SM-960/5U?

I tried to flash TWRP to a S9plus with the information in this thread, but it does not work for me.
- G965F/DS
- heimdall v1.4.2
- TWRP twrp-3.3.1-0-star2lte.img
- I made a build of Lineage 15 for star2lte, but as this tries to extract some files from the Android 8 S9plus, that I do not have, replaced the missing files with placeholder files to get a build.
- I did OEM unlock, but have since then made a number of resets, OEM unlock does no longer show up in menu
- S9+ came with latest version of Android 9 and updated to 10 nearly immidiatly
- Downgraded to july 2019 version of Android 9 (modem to Android 8 latest version)
- shows security patch october 2019 in preferences
- set date to 20 sept 2019 -> heimdall says recovery upload successful, failed to receive session end confirmation
- set date to 22 oct 2019 -> heimdall says recovery upload successful, failed to receive session end confirmation
still no TWRP installed, still no way to flash Lineage

RMM STATUS, I can't unlock it. So I can't flash twrp to phone.

will this trigger knox?
mobile in video is triggered but maybe on a "clean" one not

Related

Safe to Flash Backwards? (8.1 to 7.1.2)

I Flashed March Factory Image, but since my Call Recorder App no longer works correctly I'm hoping to go to 7.1.2 and it should work once more!
However before I did that I figured I'd ask just to be safe...
Is it safe to go from 8.1.0 (OPM1.171019.021, Mar 2018) to 7.1.2 (NJH47F, Aug 2017) ? (I'll be doing the wipe, so it's nice n clean...)
My device is the Google Pixel XL (Verizon with UnLocked Bootloader)
Thanks!
If you perform wipe (keep "-w" in flash-all script in factory image, as default) there shouldn't be any problem.
But just because you have the march 8.1, I'd suggest you to try april 8.1 image before downgrade. Maybe that fixes the problem itself.
Edit: users say you'd better flash nougat image on both slots. But some users say they're stuck in a bootloop.
But here I found a potentially useful post where they talk about flashing also 8.0
Maybe could help in case of a bootloop situation.
IIRC, the factory image checks for a compatible bootloader, If the bootloader has been updated by the 8.1.0 update, or any inbetween, the 7.1.2 factory image may fail for not having a compatible bootloader.
If it does, you should be able to get around this by pulling the bootloader out of the 7.1.2 factory image, and FASTBOOT FLASH bootloader_a (and bootloader_b) [bootloader image file]

I require help upgrading to Android 9 (stock) on my rooted OP5T

OP5T with Android 8.1.0 (Oxygen OS 5.1.7) (Security Patch: 1 Oct 2018)
- Rooted with Magisk (Magisk v.18.1 / Manager v.7.0.0)
- TWRP 3.2.3 (bluspark v.9.85)
I received a notification about the latest Android update. After postponing it for very long, this morning I decided to give it a run. Like previously, I expected the phone will be automatically unrooted after the update and of course, I will have my new android version installed. It did not happen as expected: Android booted in recovery mode (TWRP). Once rebooted will show a notification that the update could not be performed.
My suspicion is that I am missing something here. Do I have to manually restore the phone to stock ROM, before performing this upgrade? Do I have to restore the original recovery? Any other steps that I am missing here?
As I'm not doing this things so often (mostly I'm dealing with my phone's os 1-2 times over the life of the phone), it gets quite frustrating when I forget some specific aspects.
Any help much appreciated.
derei said:
OP5T with Android 8.1.0 (Oxygen OS 5.1.7) (Security Patch: 1 Oct 2018)
- Rooted with Magisk (Magisk v.18.1 / Manager v.7.0.0)
- TWRP 3.2.3 (bluspark v.9.85)
I received a notification about the latest Android update. After postponing it for very long, this morning I decided to give it a run. Like previously, I expected the phone will be automatically unrooted after the update and of course, I will have my new android version installed. It did not happen as expected: Android booted in recovery mode (TWRP). Once rebooted will show a notification that the update could not be performed.
My suspicion is that I am missing something here. Do I have to manually restore the phone to stock ROM, before performing this upgrade? Do I have to restore the original recovery? Any other steps that I am missing here?
As I'm not doing this things so often (mostly I'm dealing with my phone's os 1-2 times over the life of the phone), it gets quite frustrating when I forget some specific aspects.
Any help much appreciated.
Click to expand...
Click to collapse
You need to download the full package and install it from recovery, then set up your root and Magisk again
https://www.oneplus.com/uk/support/softwareupgrade/details?code=7

Why haven't we received the July security patch yet?

It's already August 4th and all the previous patches have come before the end of the month (except when COVID19 hit hard in China).
Our smartphones badly need stability improvements as Android 10 is buggy and unpolished. I'm worried that this update will fix nothing just as the majority of previous monthly patches.
Will xiaomi stop fixing things and just release security patches from now on?
Why is this update late?
Will xiaomi stop fixing things and just release security patches from now on?
Why is this update late?[/QUOTE]
I'd like to know too. All other "Android One" devices have been updated, except this one.
Xiaomi does not miss the opportunity to show disinterest in this terminal and its owners ...
Android One is dead.
Time to move on - Pixel 4a welcome!
Just received 180 MB...
i have received update but my mobile is rooted so i am unable to install it.
Can anyone help me to manual update?
Shoaib.Khan said:
i have received update but my mobile is rooted so i am unable to install it.
Can anyone help me to manual update?
Click to expand...
Click to collapse
If you have Magisk only the process is well documented. Find the Magisk thread and follow the instructions.
If you have TWRP + Magisk there is no simple process. I have a guide but you need a PC to help out and it's not trivial (but it only takes me 30 mins, including uploading new files for everyone else).
If there's a full rom you can flash that and then root it after. I haven't seen reports of a full 11.0.9.0 ROM.
a1291762 said:
If you have Magisk only the process is well documented. Find the Magisk thread and follow the instructions.
If you have TWRP + Magisk there is no simple process. I have a guide but you need a PC to help out and it's not trivial (but it only takes me 30 mins, including uploading new files for everyone else).
If there's a full rom you can flash that and then root it after. I haven't seen reports of a full 11.0.9.0 ROM.
Click to expand...
Click to collapse
I have TWRP + Magisk. Ohhh i see.
In case of full rom i will lost my existing data and cannot do every time when updates available.
Shoaib.Khan said:
I have TWRP + Magisk. Ohhh i see.
In case of full rom i will lost my existing data and cannot do every time when updates available.
Click to expand...
Click to collapse
You can flash a full rom without losing data. It's just that a full rom is not always released.
You can find full ROM of 11.0.9 here:
Recovery Flashable ZIP : https://bigota.d.miui.com/V11.0.9.0.QDLMIXM/miui_DAISYGlobal_V11.0.9.0.QDLMIXM_a057ca010e_10.0.zip
Fastboot : https://bigota.d.miui.com/V11.0.9.0....QDLMIXM_20200805.0000.00_10.0_e1ea175e5b.tgz

Question GSI update

Hi,
I'm currently using system-squeak-arm64-ab-vndklite-vanilla-secure as my daily driver. I install updates regularly as new releases appear on github, but I'm not 100% sure if they're installing or not. Boot loader is unlocked, no custom recovery. For me the update process has been:
Boot into fastoot on the phone
run this from my laptop: fastboot flash system system-squeak-arm64-ab-vndklite-vanilla-secure.img
After success, reboot phone normally
I have no issues or anything, but when I go to Settings > Phh Treble Settings > Updater it reports that my system is up to date on Android version 12, Security path 1 October 2021.
Also if I go to Settings > About Emulated Device > Android Version it's listed as version 12.
The last version I apparently flashed is listed as AOSP 12.1 v414.
All version info has remained the same over the last 3 updates I've installed, so I feel like I must be doing something wrong. Is anyone else seeing this issue, or does it sound like I'm doing something wrong?
Thanks
GSI updates won't update kernel, fws etc.

Question Xiaomi 11 Lite 5G NE - OFFICIAL MIUI 14 GLOBAL V14.0.2.0MIXM - ANYONE UPDATED YET ? Thread starter k500zm Start date 1 minute ago Tags

Has anyone been offered the Global version by their phone and updated ?
If Yes - what is your experience with MIUI 14 and does Dark mode work for individual apps listed separately in dark mode options?
Just received a notification for the update. Should one do a factory reset once upgraded?
EDIT: Ok, just updated and decided I'd just do a factory reset afterwards to start clean. Is it just me or do the graphics, icons and such look a little more blurry now?
Today monring i make an update, it is super. System is faster, but Leica cam app is not possible instal, have anybody newer version of leiaca cam app fo A13? THX
thecumbackkid said:
Just received a notification for the update. Should one do a factory reset once upgraded?
EDIT: Ok, just updated and decided I'd just do a factory reset afterwards to start clean. Is it just me or do the graphics, icons and such look a little more blurry now?
Click to expand...
Click to collapse
@thecumbackkid - Please tell me in settings - display - more dark mode options - does it list all the individual apps to choose dark mode for each app ? (it may take a second or 2 to list them)​
This is what it shows for me.
Thanks for the info thecumbackkid
Looks like its time to upgrade I was stuck on Miui 12.5 as when I updated to 13 all individual dark mode apps options disappered.
Someone stole my phone on holiday so I bought a new one and stuck on 12.5 as Dark mode for individual apps is essential for my over sensitive eyes!
I did the OTA update yesterday.
Before installation I uninstalled magisk, and reinstall it the inactive partition after update, before the reboot prompt.
Everything worked fine but be patient. The phone restart at least 5 times during boot logo. I was suspecting a boot loop but it finally started.
Everything is smooth, magisk root still work, safety net fix was kept.
For the moment the only thing which failed was a Google Keep Widget I had to remove and reinstall to home screen.
Except some little icon changes in notifications I didn't notice lot of changes but it is only after some minutes of utilisation.
Edit : password manager like Bitwarden seems to detect better than before that new password was entered.
snyfear said:
I did the OTA update yesterday.
Before installation I uninstalled magisk, and reinstall it the inactive partition after update, before the reboot prompt.
Everything worked fine but be patient. The phone restart at least 5 times during boot logo. I was suspecting a boot loop but it finally started.
Everything is smooth, magisk root still work, safety net fix was kept.
For the moment the only thing which failed was a Google Keep Widget I had to remove and reinstall to home screen.
Except some little icon changes in notifications I didn't notice lot of changes but it is only after some minutes of utilisation.
Edit : password manager like Bitwarden seems to detect better than before that new password was entered.
Click to expand...
Click to collapse
@snyfear
Thanks for the info - if you notice anything else let us know
Awful battery drain here. Charged to 100% barely did some basic browsing and half is already gone in a short amount of time. Noticed whenever I have it charged to 100% at night and by the middle of the next day where I barely use it for nothing but just to check for notifications on stuff it's already down to 80%...
AFAIK, this appears to be some pilot program build? I never asked to participate in it so how did I get this update?
Does any one know how to Facemoji keyboard in MIUI 14 for Lisa ?
I am not rooted. its plain stock MIUI.
Tried ADB shell uninstall, it gave me failure.
Also tried Xioami debloater tool. That also didnt work.
I still haven't received the update for some reason and i tried to update it manually but it didn't work what should I do
Updated to 14.0.4 EUXM and can't get root to work anymore.
Patched the boot image via Magisk 25.2 and then tested via fastboot, as always.
I run directly into a bootloop, which after a while sometimes returns to the bootloader or automatically deletes the temporary boot and boots with the normal image.
It's also strange that during the bootloop the device vibrates once every 3-5 seconds briefly. I've never had that before either.
Update:
I found a solution without wiping my device.
I remembered that I had a problem during the last update with shamiko and I didn't uninstalled magisk or removed any modules before the update. So in order to remove the modules without access to /data/adb and wihtout root rights you need to do the following, maybe it's interesting for you folks.
1. Open shell with command: "adb wait-for-device shell magisk --remove-modules"
2. Open second shell and boot with patched boot.img: "fastboot boot boot_patched.img"
The short time at boot, where root is present, was enough to remove the modules via the CLI during the boot loop.
Lessons learned:
Before the next major update definitely remove all Magisk modules before, if not root entirely.
Saves the work afterwards.
Btw:
Update is running smoothly so far. No battery drain noticed.
can anyone link me to a tutorial on how to rollback from custom rom (currently AOSPA) to stock MIUI ROM? want to move to MIUI 14 eventually. greatly appreciate it!
You can also install miui eu rom 14.0.6.0. If you first install via fastboot, it installs twrp with it. This way you can install future ota updates without using a computer/fastboot. In my opinion the eu rom is the same if not better as stock EEU global from xiaomi
telefoongids said:
You can also install miui eu rom 14.0.6.0. If you first install via fastboot, it installs twrp with it. This way you can install future ota updates without using a computer/fastboot. In my opinion the eu rom is the same if not better as stock EEU global from xiaomi
Click to expand...
Click to collapse
hey, thanks for the reply! just a few questions, there's no possibility of triggering anti rollback right? I was reading that some ppl faced it - I moved to custom roms from MIUI 13 iirc.
also where can I find the link to the .eu ROM? thanks again!
theanik said:
hey, thanks for the reply! just a few questions, there's no possibility of triggering anti rollback right? I was reading that some ppl faced it - I moved to custom roms from MIUI 13 iirc.
also where can I find the link to the .eu ROM? thanks again!
Click to expand...
Click to collapse
I dont believe the Xiaomi.eu roms have a anti rollback trigger. The previous roms are all a complete package (firmware, recovery, rom etc.) you flash them via fastboot.
The latest 14.0.6.0 comes with twrp. But you have to flash the rom with fastboot first, to get twrp installed.
Here's the link:
MIUI 14 - MIUI 14 STABLE RELEASE
Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
Just search for mi11le in the downloads.
telefoongids said:
I dont believe the Xiaomi.eu roms have a anti rollback trigger. The previous roms are all a complete package (firmware, recovery, rom etc.) you flash them via fastboot.
The latest 14.0.6.0 comes with twrp. But you have to flash it first with fastboot to get twrp installed.
Here's the link:
MIUI 14 - MIUI 14 STABLE RELEASE
Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
Just search for mi11le in the downloads.
Click to expand...
Click to collapse
thank you!
any one from Philippines received the update?

Categories

Resources