Database Info

TWRP installation after having rooted

Hey guys,
Recently moving back to Android with a Samsung Galaxy S7 (SM-G930F) and I have some problems to get everything working. I didn't find (or didn't managed to find) the informations I was looking for on the forum or anywhere else on internet.
Here is what I did since now:
1. Rooted my phone with CF-Auto-Root.
2. Phone rooted correctly, SuperSU installed => no problem
3. Installed TWRP Manager.
4. Launched installation of TWRP from the TWRP Manager and selected the latest version of herolte (3.0.2-2).
5. Installation failed, relaunched it, didn't get any notice of success or failed this time so I presumed it was good.
6. Restarted the phone in normal mode => No problem.
7. Restarted the phone in recovery mode => Access to TWRP asking me if I want to stay in read only or allow read/write.
> Can I boot up at this stage in read/write without causing any issues since I saw in the TWRP root installation process (http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770)
"By swiping right, you will trigger dm-verity, and if you don't follow step 11 you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications."
> Since I am already rooted, it shouldn't cause any issues right?
8. I tried to do a backup of my phone but the data folder is showing no data and when performing a backup I am getting a "failed to mount /data error"
> Don't really know how to fix this error.
> I can backup without any issue Boot and System.
Thank you per advance for your answers

1. You need to flash dm-verity and force encryption disabler before you swipe right and activate read/write. Otherwise it won't boot.
2. If you want to do a backup with TWRP you need to format data once, so the encryption is disabled. Just perform a backup via Titanium and format data in TWRP. Afterwards you can make backups in TWRP.

Thank You.
I just did the steps described but it seems that I lost my root after having wipe the data partition.
Now when I am rebooting the phone I am getting "kernel is not seandroid enforcing" in red on top of the screen but the phone still boot up fully.
Tried to reboot in recovery but it seems that TWRP is not present anymore.

I re-rooted the phone using CF-Auto-Root.
Now the phone is rooted, I installed once again TWRP Manager and tried to reboot in recovery mode but getting "dm-verity verification failed…"
I don't have the "kernel is not seandroid enforcing" error anymore.
Do I need to reinstall TWRP in order to solve the issue?

Julek_Fr said:
I re-rooted the phone using CF-Auto-Root.
Now the phone is rooted, I installed once again TWRP Manager and tried to reboot in recovery mode but getting "dm-verity verification failed…"
I don't have the "kernel is not seandroid enforcing" error anymore.
Do I need to reinstall TWRP in order to solve the issue?
Click to expand...
Click to collapse
Hi
did you do this?
Point 11
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
Kernel thing is normal ........

MAX 404 said:
Hi
did you do this?
Point 11
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
Kernel thing is normal ........
Click to expand...
Click to collapse
Thank you for your reply.
Since the phone was already rooted I didn't done the SuperSU but wipped the data partition and flashed with the "dm-verity and force encryption disabler".
After reboot I was not rooted anymore, so I re-rooted the phone and reinstalled the aps.
Now if I try to reboot in recovery mode, I get the error "dm-verity verification failed…"
If I try to factory default the phone I am getting the same error.
Do you think I can just flash back in stock firmware using odin and the good version downloaded from sammobile? It will remove TWRP and the root right ?

Julek_Fr said:
Thank you for your reply.
Since the phone was already rooted I didn't done the SuperSU but wipped the data partition and flashed with the "dm-verity and force encryption disabler".
After reboot I was not rooted anymore, so I re-rooted the phone and reinstalled the aps.
Now if I try to reboot in recovery mode, I get the error "dm-verity verification failed…"
If I try to factory default the phone I am getting the same error.
Do you think I can just flash back in stock firmware using odin and the good version downloaded from sammobile? It will remove TWRP and the root right ?
Click to expand...
Click to collapse
Hi
Flash a stock firmware is an option but not necessary at this point
Go back to TWRP page
http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
and re do all this steps one by one ( 1 to 13 ), make sure OEM unlock is enables , back up important thing before you do anything just in case
FULL STEPS FOR OBTAINING ROOT
You can follow this video by Max Lee if you'd like: How to Root Galaxy S7 & S7 Edge! [Exynos ONLY]
Otherwise, follow these instructions:
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Extract Odin_3.10.7.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for herolte.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot without touching any other options, then press [Start].
Hold [Volume Up] + [Home] buttons near the end of the flash, and keep holding them until you are in recovery.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow step 11 you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
Only if you want internal storage or data to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery].
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
Wait 5-15 minutes for your device to finish setting itself up.
try this first....

GerasVille said:
1. You need to flash dm-verity and force encryption disablerbefore you swipe right and activate read/write. Otherwise it won't boot.
2. If you want to do a backup with TWRP you need to format data once, so the encryption is disabled. Just perform a backup via Titanium and format data in TWRP. Afterwards you can make backups in TWRP.
Click to expand...
Click to collapse
How to flash this file? Please treat me like an idiot. What exactly do I have to do?
I am trying to flash the ROM of a different model of my phone, and thus need TWRP, but this needs to be unlocked first somehow.

Disable Re Encryption On Update Or Workaround

As you can see from the title, I am looking for a way to stop my phone from re encrypting itself every time I update his firmware.
It is rooted with magisk and has twrp installed.
If there is no way to prevent it from re encrypting everything, is there a way to backup all my data in a manner that would allow me to reinject it retaining all the data? (like the authentication tokens and such)
I really need help in this domain since I seem to be unable to find a workaround myself and also the 8.0 update seems to be just around the corner and I want to be able to update and keep everything.
Smart Switch is not an alternative since it does back up all the apps but it does not back up the data.
~Thanks

bump
anyone?

heeeeeeeeelp
Have you found a way?... I'm in your situation and it's been frustrating me for a decade...
After updating my ROM, I don't have access to /data in TWRP, because the Update encrypts it.
I haven't set a password, so I tried the TWRP Terminal and do "twrp decrypt default_password". I read that "default_password" is the standard encryption password, but it doesn't work...

How to update ROM without /data getting encrypted
Dude, I found out how to disable the Forced Encryption!
Or in other words, how to update ROM without /data getting encrypted!
The key is: Before the first android boot, flash TWRP, boot into TWRP, flash Magisk.
Why: Because the first android boot encrypts /data. And Magisk disables this Encryption-process.
So, step by step:
1. Make a complete backup, in case you fail the steps (I use TWRP for backups)
2. Flash your updated ROM with ODIN.
3. Let it reboot to the blue screen stuff. (That's not the android boot, yet! It's just the Samsung Bootloader finalizing the update)
4. Your phone will reboot again now, DON'T LET IT BOOT TO ANDROID! Boot into Download Mode instead!
5. In ODIN, uncheck "Auto Reboot" and flash TWRP.
6. Now reboot from Download Mode into TWRP.
7. Flash Magisk.
8. Done! You can reboot now.
/data is now accessable in TWRP and in Android, in Settings > Biometrics and Security, you will now see the option to "Encrypt device" "Device not encrypted".
Notice:
Everytime you flash an updated ROM, you need to flash Magisk immediately afterwards. After the blue screen process, but before the first android boot!
Do not forget this, when flashing an updated ROM in the future!
Too bad i'm 2 years late for you, but I hope other people with the same problem find this.

What's New(?) procedure to install Custom ROMs coming from OOS 9.0.5?

Hello guys,
I'm having trouble trying to install a Custom ROM (Tresk Mod, but I get it with others too)
So basically some days ago my whole Internal Storage got encrypted so I had to a full wipe.
From there I decided to use Msmtools just in case, so I got back to OOS 5.1.5 from there I updated to OOS 9.0.5 via OTA and unlock the bootloader and install TWRP everything works fine.
But when I tried to install any custom ROM I either cannot boot and just boots to Bootloader (Not even the recovery works) and I get "Failed to load/authenticate boot image: Load Error" which I can fix fastboot flashing all the partitions...
Or I straight get a black screen with the White Notifications LED whenever I try to boot either to system or recovery and from there I can only recover using Msmtools...
So I'm now asking, what are the steps for flashing Custom ROMs now?? Because seems like I'm doing something wrong since I'm ending having a Bricked device...

try to flash rom with bluespark recovery

Nothing changed that I'm aware of, but I found that I'll have the same experience if I try to root before booting the system at least once rootless first. Also, I have issues like that whenever I keep TWRP (even Blu Spark) installed. Now I only use it via sideload every time. I never have issues anymore.

Mdknight said:
Nothing changed that I'm aware of, but I found that I'll have the same experience if I try to root before booting the system at least once rootless first. Also, I have issues like that whenever I keep TWRP (even Blu Spark) installed. Now I only use it via sideload every time. I never have issues anymore.
Click to expand...
Click to collapse
I did the following:
1. Upgraded from 5.1.5 to 9.0.5 (Since I was coming from Msmtools fix)
2. Unlock bootloader
3. Reboot to system and then boot again to bootloader for doing (fastboot boot TWRP.xxx.img)
4. Once in the recovery flash recovery and Magisk (just because) and back to system (where everything was working perfectly)
5. Rebooted to recovery and did the following:
Factory Reset (The one that you slide which should wipe Cache, Dalvik and Data)
Flashed the ROM (HavocOS 2.5) and right after that TWRP
And at this point I tried to reboot back to recovery but black screen and cannot boot to recovery nor system not even via fastboot
Is your order different? Am I missing something?

Asiier said:
I did the following:
1. Upgraded from 5.1.5 to 9.0.5 (Since I was coming from Msmtools fix)
2. Unlock bootloader
3. Reboot to system and then boot again to bootloader for doing (fastboot boot TWRP.xxx.img)
4. Once in the recovery flash recovery and Magisk (just because) and back to system (where everything was working perfectly)
5. Rebooted to recovery and did the following:
Factory Reset (The one that you slide which should wipe Cache, Dalvik and Data)
Flashed the ROM (HavocOS 2.5) and right after that TWRP
And at this point I tried to reboot back to recovery but black screen and cannot boot to recovery nor system not even via fastboot
Is your order different? Am I missing something?
Click to expand...
Click to collapse
You have to install twrp.zip again after havoc, boot Back Into Recovery and then gapps and magisk

Asiier said:
I did the following:
1. Upgraded from 5.1.5 to 9.0.5 (Since I was coming from Msmtools fix)
2. Unlock bootloader
3. Reboot to system and then boot again to bootloader for doing (fastboot boot TWRP.xxx.img)
4. Once in the recovery flash recovery and Magisk (just because) and back to system (where everything was working perfectly)
5. Rebooted to recovery and did the following:
Factory Reset (The one that you slide which should wipe Cache, Dalvik and Data)
Flashed the ROM (HavocOS 2.5) and right after that TWRP
And at this point I tried to reboot back to recovery but black screen and cannot boot to recovery nor system not even via fastboot
Is your order different? Am I missing something?
Click to expand...
Click to collapse
Sconny said:
You have to install twrp.zip again after havoc, boot Back Into Recovery and then gapps and magisk
Click to expand...
Click to collapse
Agreed. Always reboot from recovery to recovery after flashing a new one (TWRP). THEN, go ahead and flash gapps and magisk.

Sconny said:
You have to install twrp.zip again after havoc, boot Back Into Recovery and then gapps and magisk
Click to expand...
Click to collapse
Mdknight said:
Agreed. Always reboot from recovery to recovery after flashing a new one (TWRP). THEN, go ahead and flash gapps and magisk.
Click to expand...
Click to collapse
I finally figured it out
The problem was that as I was updating via OTA OOS 9.0.5 was only installed in one Slot so I need to install it in the other as well.
Did the following process:
1. Boot to Bootloader and do "fastboot boot TWRP.img"
2. From there flash TWRP.zip and Reboot back to it (Recovery)
3. Flash OOS Latest (9.0.5)
4. Flash TWRP
5. Reboot to TWRP
6. Flash OOS Latest (9.0.5)
7. Flash TWRP
8. Reboot to TWRP
9. Wipe data, dalvik cache
10. Flash ROM
11. Flash TWRP
12. Reboot to TWRP
13. Flash gapps + Misc (Magisk, etc)
14. Boot system
Technically just one 1 installation should do as the other slot was already populated but the twice just to be safe.

OnePlus 7 Pro Flashing doesn't work properly

Hey guys,
so first of all I wanna let you know that my device is not bricked or something (it was a couple of times though).
But let's get started with my issue. For me, personally, I have experienced that the slot system (A/B Slot) doesn't work that good. I had a OnePlus 3T before and I never had any problems with flashing, but now...
My impression is that it's a lot easier to brick its' device than before. Every time I want to flash a new OS I gotta use the msmtool.
1. I boot to recovery mode through the OS
2. I boot to fastboot trough the OOS stock recovery
3. I try to flash TWRP to erase the system
4. Flashing works, but I can no longer boot into recovery mode
5. I have a bootloop (fastboot mode only)
6. I have to use that msmtool
7. I have some old OOS (9.5.5 or something)
8. I unlock the bootloader through the OS & fastboot
9. I boot into TWRP, delete everything and flash another ROM
10. Everything works and the cicle begins again​
I really don't know why I'm always stuck in that bootloop... Maybe you guys could help me and give me your personal opinion on the slot system?

I totally know that feeling. I started with a tmo op7p, flashed international, unlocked bootloader, try to boot TWRP, and nope. Switch slot, it works. Flash it, great. Make a backup with TWRP of my working system, flash ROMaur, won't do anything but boot to TWRP. Open TWRP file manager and every file on internal storage is a ton of folders with jumbled strings of letters and numbers for names. MSM tool back to intl stock, try lineage... Nope. Keeps telling me to do a factory reset. I did, but I do another and still boot loop. MSM to intl, try other roms, same outcome.
I can unlock my bootloader and root it and run intl stock but that's it.

oxadedzn said:
Hey guys,
so first of all I wanna let you know that my device is not bricked or something (it was a couple of times though).
But let's get started with my issue. For me, personally, I have experienced that the slot system (A/B Slot) doesn't work that good. I had a OnePlus 3T before and I never had any problems with flashing, but now...
My impression is that it's a lot easier to brick its' device than before. Every time I want to flash a new OS I gotta use the msmtool.
1. I boot to recovery mode through the OS
2. I boot to fastboot trough the OOS stock recovery
3. I try to flash TWRP to erase the system
4. Flashing works, but I can no longer boot into recovery mode
5. I have a bootloop (fastboot mode only)
6. I have to use that msmtool
7. I have some old OOS (9.5.5 or something)
8. I unlock the bootloader through the OS & fastboot
9. I boot into TWRP, delete everything and flash another ROM
10. Everything works and the cicle begins again
I really don't know why I'm always stuck in that bootloop... Maybe you guys could help me and give me your personal opinion on the slot system?
Click to expand...
Click to collapse
Doing it wrong.
If you are currently rooted and a new OS comes out you can do the following and you don't need to flash with TWRP or use a computer.
1. Download the full OTA. You can use Oxygen updater to do that or use a link in the stock ROM section on this site.
2. Make sure you have the Magisk and the TWRP zip on the phone.
3. Do a local update in the system area but do not reboot.
4. Launch Magisk manager and select install.
5. Use the OTA install option to inactive slot.
6. Now you can reboot. You have installed the new OS and root also.
7. Once rebooted do another local install. This will install in the slot that you were just running. It will fail the first time, but work the second time.
8. Repeat 4.
9. Repeat 5.
10 . Repeat 6.
You now have both slots with the same OS and rooted.
If you want to install TWRP.
Launch Magisk and install the TWRP zip.
Reboot into recovery. This is important because you cannot boot in slot with TWRP unless Magisk in installed.
Now flash the Magisk image file.
Now in TWRP select the other slot and reboot into recovery.
In recovery install Magisk image to this slot.
Now you have TWRP and Magisk in both slots.
I have done it that way since 9.5.7 and have not had an issue.

tech_head said:
Doing it wrong.
If you are currently rooted and a new OS comes out you can do the following and you don't need to flash with TWRP or use a computer.
1. Download the full OTA. You can use Oxygen updater to do that or use a link in the stock ROM section on this site.
2. Make sure you have the Magisk and the TWRP zip on the phone.
3. Do a local update in the system area but do not reboot.
4. Launch Magisk manager and select install.
5. Use the OTA install option to inactive slot.
6. Now you can reboot. You have installed the new OS and root also.
7. Once rebooted do another local install. This will install in the slot that you were just running. It will fail the first time, but work the second time.
8. Repeat 4.
9. Repeat 5.
10 . Repeat 6.
You now have both slots with the same OS and rooted.
If you want to install TWRP.
Launch Magisk and install the TWRP zip.
Reboot into recovery. This is important because you cannot boot in slot with TWRP unless Magisk in installed.
Now flash the Magisk image file.
Now in TWRP select the other slot and reboot into recovery.
In recovery install Magisk image to this slot.
Now you have TWRP and Magisk in both slots.
I have done it that way since 9.5.7 and have not had an issue.
Click to expand...
Click to collapse
Irrelevant ISH, but ever had that one bootloop where it only bootloops at the "Warning Bootloader unlocked screen" constantly? When I try to access fastboot, it'll just go straight to recovery without even waiting for input (to my luck, of course, until I had to uninstall magisk in full, reinstall, make sure TWRP was reflashed and did the "Fix recovery bootloop", though that wasn't the seemingly the issue). The issue got resolved, but it was very scary for that to have happened as soon as i enabled sudohide (I always had it work, but with huge problems, but never enough to bootloop me to death)

JhinCuatro said:
Irrelevant ISH, but ever had that one bootloop where it only bootloops at the "Warning Bootloader unlocked screen" constantly? When I try to access fastboot, it'll just go straight to recovery without even waiting for input (to my luck, of course, until I had to uninstall magisk in full, reinstall, make sure TWRP was reflashed and did the "Fix recovery bootloop", though that wasn't the seemingly the issue). The issue got resolved, but it was very scary for that to have happened as soon as i enabled sudohide (I always had it work, but with huge problems, but never enough to bootloop me to death)
Click to expand...
Click to collapse
If you install TWRP on a 7 Pro without installing Magisk you will absolutely boot loop. If you wipe the system in one slot and have a differing ROM from the active slot you can in fact boot loop. Although the systems are different, the settings between the systems are shared.

Sorry to say, but nothing about those steps is correct. Follow some guides in the guides section to get aquatinted with the A/B system

Arden144 said:
Sorry to say, but nothing about those steps is correct. Follow some guides in the guides section to get aquatinted with the A/B system
Click to expand...
Click to collapse
You are absolutely incorrect.
When going from 9.5.10 to 9.5.11 and all my previous upgrades it has been:
1. Local install of the new OS with a full OTA since I am rooted.
2. Do not reboot.
3. Install Magisk to inactive slot.
4. Reboot (Slot will automatically switch to the one recently updated).
5. Local install of OS into the other slot, fails first time, do it again.
6. Install Magisk into inactive slot.
7. Reboot. (Slot will switch to recently updated slot).
8. Both slots now have latest OS and are rooted.
You can also install TWRP if you like.
No computer needed.
This works.

tech_head said:
You are absolutely incorrect.
When going from 9.5.10 to 9.5.11 and all my previous upgrades it has been:
1. Local install of the new OS with a full OTA since I am rooted.
2. Do not reboot.
3. Install Magisk to inactive slot.
4. Reboot (Slot will automatically switch to the one recently updated).
5. Local install of OS into the other slot, fails first time, do it again.
6. Install Magisk into inactive slot.
7. Reboot. (Slot will switch to recently updated slot).
8. Both slots now have latest OS and are rooted.
This works.
Click to expand...
Click to collapse
That's completely unnecessary and just avoiding the purpose of the a/b system.
All it would take is:
1. Local install
2. Install magisk to inactive slot

[SOLVED] Installing ANY custom ROM bricks Oneplus 6

Hello!
I'm having quite a hard time figuring out what is happening on my new Oneplus 6.
The first time i flashed LineageOS 16 microg edition it booted but since i tried to restore stock ROM backup with TWRP it all went to hell.
Device immediately bricked, only booting to fastboot.
Had to use msm tool to unbrick. ( the first of so many times.... )
Then updated from settings to latest OOS 9.0.9.
unnlocked bootloader
and flashed again.
NO OS INSTALLED.
phone boots only in fastboot.
can't boot any recovery from fastboot. gives error.
if reboot to recovery blue led and black screen is all that i see.
only fix is msm.
From that point onwards i tried EVERY guide I could find (and recognize as valid of interest) here on xda, youtube, google.
Multiple times per guide.
here's an example of a "last resort" guide from https://forum.xda-developers.com/oneplus-6/how-to/guide-microg-oneplus-6-source-ligthway-t3874469
INSTALLATION TUTORIAL
Italic = recommended, but not mandatory. Do it if something doesn't work properly
0) DON'T RESTORE your apps until everything is set up, otherwise you'll have issues with GCM (getting instant notifications from messaging apps for example)
1) Reboot to blu spark TWRP
2) step deleted
3) Flash OOS
4) Flash TWRP
5) Reboot to recovery
6) Flash OOS
7) Flash TWRP
8) Reboot to recovery
9) Flash your custom ROM + TWRP + reboot to TWRP
10) Flash again your custom ROM + TWRP
11) Reboot to recovery
11 bis) Wipe data ("factory reset")
12) Flash Magisk
13) Reboot to system. It's just to make sure the installation worked.
... more on link
Click to expand...
Click to collapse
Tried also official lineage, SyberiaOS. Different previous version of the two (since I read in the lineage official thread others have this issue)
Basically at the point after flashing any of these roms results immediately in TWRP warning "no os is installed" at reboot attempt with or without re-flashing twrp after.
Then if rebooted just hangs on blue led. can't boot anything.
Meanwhile flashing OTAs + twrp results in bootable system.
Other things that i tried:
before unlocking BL update to latest OTA_34 -> 9.0.9, reboot, install again.
using mauronofrio twrp version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Any ideas?
[SOLUTION]
If you're bricked follow this: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
1 - Have last OOS installed in both slots
- update from settings, local update, latest OTA (Pie) from oneplus support site.​- reboot, let it complete​- apply again​2 - Enable OEM Unlock in Developer options
3 - Boot to Fastboot and unlock bootloader:
Code:
fastboot oem unlock
4 - Once in OOS reboot to fastboot and boot twrp:
Code:
fastboot boot <twrp-img-name>.img
5 - Push twrp + custom rom:
Code:
adb push <custom-rom-name>.zip <twrp-zip-name>.zip /sdcard
6 - Flash twrp in twrp
7 - Reboot to recovery
8 - Wipe system and Data
9 - flash ROM
10 - flash twrp
[IMPORTANT]
11 - Tap Reboot to recovery then if it says No OS installed! tap home button! Don't reboot! reboot = brick = msmdownloadtool
12 - Go in advanced menu and select Fix Recovery Bootloop and swipe
13 - THEN TRY TO MOUNT /system.
IF YOU'RE UNABLE TO MOUNT /system APPLY AGAIN THE FIX AND REPEAT FROM STEP 7​14 - Reboot to recovery
It WILL stil say No OS installed but now you'll be able to reboot to recovery​[/IMPORTANT]
15 - Once in recovery reboot to system.
If you've done everything correctly it won't complain again about no OS being installed and you'll get your rom up and running.​16 - Let it reboot to system and complete first configuration
17 - Now you can reboot and flash every module you like from twrp.
That's it. Hope this'll spare nightmares and storage write life.

This is a bad phone .. I have it too
تم الإرسال من ONEPLUS A6003 باستخدام Tapatalk

But you seem (from post history) to be able to install ROMs :crying:
As most of those who try i guess.
Maybe my phone is somehow damaged

What some guides miss out is that you have to install everything twice. Once on slot A and once on slot B and after each install, verify what slot you are on before reboot and then check what slot you are on after reboot. I ran into issues flashing Havoc OS onto my phone too and figured it out in the end after so many times that I was in fact installing stuff twice on the same slot because it never switched over. I'll run you through the order I did things so hopefully you can follow.
-Use MSM Tool to revert everything back to stock and once the phone is booted, update to 9.0.9 either by downloading the update through the phone or by local upgrade if you have the file to hand. (remember to only have the OOS file present as any other OS in zip form crashes the local updater). You don't need to do this if you are already rocking stock Oxygen OS.
-Once the phone has restarted after the upgrade, let the post update procedure finish before continuing.
-Enter developer mode and enable OEM unlocking, Advanced Restart and USB Debugging. From here, reboot to bootloader.
-Plug your phone into the PC now and assuming you have fastboot setup ready on your PC, type 'fastboot oem unlock' and use the volume keys to select the option to unlock and press the power button to select.
-After the phone has completed it's wipe cycle, re-enable Advanced Restart and USB Debugging. The OEM unlock option should be greyed out as it's already been enabled. Make sure you don't add a pin code or password just yet as you will enable encryption which will make the next steps harder than it should be.
-Boot back to bootloader and type 'fastboot boot twrp.img' (or whatever you named it. Make sure that the image file is in the same folder you initiated cmd or powershell)
-Once booted into TWRP, flash blu_spark TWRP as that supports encryption apparently and is more stable than any other. To make sure that the script executed on both slots, hit reboot and check what slot you are on and tap the button for the other slot. Now reboot back to recovery, check you are on the other slot and flash it again.
-Now flash your 9.0.9 OOS zip followed by TWRP once on slot A and once on slot B while making sure you are on the other slot when doing it a second time. Remember that you have to re-flash TWRP after any flashable file that alters the boot partition before you reboot or you will undo all your work. Just make it habit that you re-flash it every time and you should be good.
-Once OOS and TWRP have been flashed on BOTH slots, reboot back to recovery and do the whole process again with your custom ROM (Remembering to flash TWRP before you reboot and checking which slot you are one before and after each flash).
-Once that has completed, reboot back to recovery and flash Magisk on each slot and GApps or MicroG if your ROM supports it. You don't need to re-flash TWRP after this but I do anyway to keep the habit lol.
-Entirely up to you, but before you reboot to your fresh new OS, you can wipe internal storage ONLY if you want all traces of your previous OS gone, but this will also remove personal files etc. I generally just head into TWRP file manager and delete the Android folder and keep the rest.
If you run into issues like crashes on your new OS, reboot to recovery and do a factory reset, but you will also need to re-flash Magisk again. GApps installs itself to system, so you won't need to re-flash that. MicroG does not and will need setting up again. One thing that took me a while to realise is that if you try rebooting while your USB is plugged into your PC, you will sometimes enter download mode, so only keep it plugged in when you need it for MSM Tool or to transfer files across.
I'm pretty sure I put everything down the way I did it and didn't miss anything, but it is late and I am half asleep. Will check back in the morning and double check with a fresh brain.

Many thanks for your exhaustive reply!
Will follow this tomorrow morning with a fresh brain

Fixed!
Now I'll write a guide for those in the same situation.

franticboe said:
Hello!
I'm having quite a hard time figuring out what is happening on my new Oneplus 6.
The first time i flashed LineageOS 16 microg edition it booted but since i tried to restore stock ROM backup with TWRP it all went to hell.
Device immediately bricked, only booting to fastboot.
Had to use msm tool to unbrick. ( the first of so many times.... )
Then updated from settings to latest OOS 9.0.9.
unnlocked bootloader
and flashed again.
NO OS INSTALLED.
phone boots only in fastboot.
can't boot any recovery from fastboot. gives error.
if reboot to recovery blue led and black screen is all that i see.
only fix is msm.
From that point onwards i tried EVERY guide I could find (and recognize as valid of interest) here on xda, youtube, google.
Multiple times per guide.
here's an example of a "last resort" guide from https://forum.xda-developers.com/oneplus-6/how-to/guide-microg-oneplus-6-source-ligthway-t3874469
Tried also official lineage, SyberiaOS. Different previous version of the two (since I read in the lineage official thread others have this issue)
Basically at the point after flashing any of these roms results immediately in TWRP warning "no os is installed" at reboot attempt with or without re-flashing twrp after.
Then if rebooted just hangs on blue led. can't boot anything.
Meanwhile flashing OTAs + twrp results in bootable system.
Other things that i tried:
before unlocking BL update to latest OTA_34 -> 9.0.9, reboot, install again.
using mauronofrio twrp version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Any ideas?
[SOLUTION]
If you're bricked follow this: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
1 - Have last OOS installed in both slots
- update from settings, local update, latest OTA (Pie) from oneplus support site.​- reboot, let it complete​- apply again​2 - Enable OEM Unlock in Developer options
3 - Boot to Fastboot and unlock bootloader:
Code:
fastboot oem unlock
4 - Once in OOS reboot to fastboot and boot twrp:
Code:
fastboot boot <twrp-img-name>.img
5 - Push twrp + custom rom:
Code:
adb push <custom-rom-name>.zip <twrp-zip-name>.zip /sdcard
6 - Flash twrp in twrp
7 - Reboot to recovery
8 - Wipe system and Data
9 - flash ROM
10 - flash twrp
[IMPORTANT]
11 - Tap Reboot to recovery then if it says No OS installed! tap home button! Don't reboot! reboot = brick = msmdownloadtool
12 - Go in advanced menu and select Fix Recovery Bootloop and swipe
13 - THEN TRY TO MOUNT /system.
IF YOU'RE UNABLE TO MOUNT /system APPLY AGAIN THE FIX AND REPEAT FROM STEP 7​14 - Reboot to recovery
It WILL stil say No OS installed but now you'll be able to reboot to recovery​[/IMPORTANT]
15 - Once in recovery reboot to system.
If you've done everything correctly it won't complain again about no OS being installed and you'll get your rom up and running.​16 - Let it reboot to system and complete first configuration
17 - Now you can reboot and flash every module you like from twrp.
That's it. Hope this'll spare nightmares and storage write life.
Click to expand...
Click to collapse
i tried all the mentioned steps, nothing worked for me. Even i tried all the guides, here on xda and on youtube i am not able to boot my 1+6 it is getting booted to fastboot mode, after installing custom rom. But if i flash only OOS then it boots back properly.
But in case of a custom rom it boots back to fastboot mode, and then in the end msm tool is the last resort to lock bootloader and make it stock.

i tried all the mentioned steps, nothing worked for me. Even i tried all the guides, here on xda and on youtube i am not able to boot my 1+6 it is getting booted to fastboot mode, after installing custom rom. But if i flash only OOS then it boots back properly.
But in case of a custom rom it boots back to fastboot mode, and then in the end msm tool is the last resort to lock bootloader and make it stock.
Click to expand...
Click to collapse
If you are stuck on fastboot try
fastboot set_active other
then try rebooting recovery if fails try
fastboot boot pc-stored-twrp
I found changing the active slot via fastboot may unbrick it without msm. It all depends on what steps you actually take during installation.
For installing LOS try not flashing twrp after installation. Los comes with its own recovery. Anyway if it says no OS installed you HAVE to fix recovery bootloop.