Database Users

[GUIDE] How to get CM 14.1 working.

Hi,
So I have created this thread just because I can see many people creating new threads as after flashing CM 14.1, their phone doesn't boot up. So for all those who are going to flash CM 14.1 or have already flashed it and can't get it working, this thread is for you.
What you will need:
1. Rooted OnePlus X (Obviously)
2. Custom Recovery (TWRP recommended)
3. Latest CM 14.1 build
4. Arsenic Kernel or BlackReactor Kernel
So this is how you get CM 14.1 working on your OPX (make sure your battery is above 80% just to be sure that nothing will go wrong considering battery's point of view)
Make sure you have backed up everything before performing the following steps as the process will wipe your data completely. (I would recommend to take a Titanium backup of all user apps and then taking a nandroid backup of system and data)
1. Download the required files and place them in your SD Card or internal storage
2. Reboot your device into recovery
3. Go to wipe, and swipe to factory reset (Note! This will completely wipe all the data from your device including app data and SMS! This won't wipe the contacts but just to be safe, have a backup of all your contacts)
4. Go to Wipe again, and go to Advanced wipe, select the following partitions - System, Cache, Dalvik cache. Swipe to wipe (Note! Make sure you have a backup of the System as this will wipe the Operating System from your phone!) Although this step isn't necessary, I like to do it.
5. Go to install, and direct to the location where you have saved the CM 14.1 zip file and the kernel. Select the files, and swipe to flash.
6. If you want anything else in your system, direct to that location, select the zip file, and swipe to flash. (Note! You need not flash the SuperSU zip file as CM offers Root access in developer options)
7. Reboot your system and wait for it to boot.
Viola! Your device is now running official CM 14.1 nightly.
Hope this helps! ?
Downloads:
1. Latest CyanogenMod nightly - found here https://download.cyanogenmod.org/?device=onyx
You can have any version of the nightly as long as it is CM 14.1
2. Arsenic Kernel R32 (or R31) - http://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
Open the above thread and follow the guide
OR
Black Reactor kernel v1.0 - http://forum.xda-developers.com/oneplus-x/development/kernel-blackreactor-kernel-oneplus-x-t3460989

-Reserved-

Good Evening, @aamodjoshi23 THX a Lot. You are my Hero. Finally it works.
greetings

If you're facing some Error 7 while trying to flash cm 14.1, you can try updating the bootloader following this
http://forum.xda-developers.com/showpost.php?p=69267239&postcount=2560
I used the Oxygen OS 3.13 full ROM as recommended, edited updater-script (following those instructions)
Immediately after flashing the OOS 3.13 rom, you don't have to reboot.
I immediately flashed twrp 3.0.3 original from https://dl.twrp.me/onyx/
I then rebooted into twrp 3.0.3 (using the reboot button in twrp, then bootloader)
Then I installed (in this order):
cm 14.1 (https://download.cyanogenmod.org/?device=onyx)
arsenic kernel (as recommended above)
opengapps
Not sure if this step is necessary, but I wanted to let twrp patch the rom to not overwrite twrp so I rebooted into twrp again (using reboot --> bootloader in twrp)
Then I used reboot --> system
First boot took a while, but now I have nougat!!

kenel zip every time
Do i need to flash the kenel zip every time I update the the cm 14.1 zip file?

allons-y said:
Do i need to flash the kenel zip every time I update the the cm 14.1 zip file?
Click to expand...
Click to collapse
Yes, as when you flash the CM 14.1 build, the kernel that is provided with the build is also flashed, and that is not supported. So you need to flash it every time you flash a CM 14.1 build, but if you want to flash any other build, something like CM 13.0, then you need not as the kernels provided in those are supported.

aamodjoshi23 said:
Yes, as when you flash the CM 14.1 build, the kernel that is provided with the build is also flashed, and that is not supported. So you need to flash it every time you flash a CM 14.1 build, but if you want to flash any other build, something like CM 13.0, then you need not as the kernels provided in those are supported.
Click to expand...
Click to collapse
Hi,
I have a very specific problem. I rooted my Oneplus x few months back and everything was fine. I use to get update notifications and after downloading it use to update automatically. But since last 2 months i download the update files but it takes me to recovery and then i cant find the zip file to flash/install. (i also started using external sd card two months back, but not sure if it has to do anything with this). I tried searching a solution on web - tried checking 'system' under Mount tab, installed an app for auto update and some more but no use. I even connected my phone in recovery mode to laptop and copied the zip file to internal memory but while flashing it gave error.
Now i am not sure what the problem is. Do i need to update my recovery or something else. Pls help.

shashanksachdeva said:
Hi,
I have a very specific problem. I rooted my Oneplus x few months back and everything was fine. I use to get update notifications and after downloading it use to update automatically. But since last 2 months i download the update files but it takes me to recovery and then i cant find the zip file to flash/install. (i also started using external sd card two months back, but not sure if it has to do anything with this). I tried searching a solution on web - tried checking 'system' under Mount tab, installed an app for auto update and some more but no use. I even connected my phone in recovery mode to laptop and copied the zip file to internal memory but while flashing it gave error.
Now i am not sure what the problem is. Do i need to update my recovery or something else. Pls help.
Click to expand...
Click to collapse
First of all we need more info about your current ROM recovery etc.

Fap4k said:
First of all we need more info about your current ROM recovery etc.
Click to expand...
Click to collapse
I installed CM 13.0-20160928-NIGHTLY-onyx and the recovery is: TWRP v2.8.7.0 | blu_spark r8
I'll be grateful for a solution.

shashanksachdeva said:
I installed CM 13.0-20160928-NIGHTLY-onyx and the recovery is: TWRP v2.8.7.0 | blu_spark r8
I'll be grateful for a solution.
Click to expand...
Click to collapse
In October oneplus updated to 6.0.1 officially i.e OOS 3 it brings new bootloader to the device as you are using old recovery you can't flash new update..so you need to upgrade to latest bootloader by following thread available in general section or you can flash stock recovery and upgrade to latest OOS and flash whatever you want to flash..I recommend you to see how to upgrade bootloader in general section if you are planning to flash custom ROMs or if want to flash latest OOS then simply flash stock recovery and upgrade. onece you updated to OOS 3 after that you can flash new official twrp 3.0.3.0 from its official page.
Edit: for old bootloader you need stock 5.1.1 recovery..which is not available in official oneplus download page..so just follow below link
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917

Fap4k said:
In October oneplus updated to 6.0.1 officially i.e OOS 3 it brings new bootloader to the device as you are using old recovery you can't flash new update..so you need to upgrade to latest bootloader by following thread available in general section or you can flash stock recovery and upgrade to latest OOS and flash whatever you want to flash..I recommend you to see how to upgrade bootloader in general section if you are planning to flash custom ROMs or if want to flash latest OOS then simply flash stock recovery and upgrade. onece you updated to OOS 3 after that you can flash new official twrp 3.0.3.0 from its official page.
Edit: for old bootloader you need stock 5.1.1 recovery..which is not available in official oneplus download page..so just follow below link
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Click to expand...
Click to collapse
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.

shashanksachdeva said:
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
Click to expand...
Click to collapse
This is because you flashed wrong recovery twrp 3.0.3 is for new bootloader and you are on old bootloader..that's why it all happened..so you just need to flash old recovery..then follow given link to upgrade bootloader and recovery.

shashanksachdeva said:
I made a blunder. I read somewhere to upgrade TWRP to 3.0.3 and after doing that now i just can't access the recovery mode. When i try to boot in recovery mode the screen gets stuck with One+ logo. Then I even tried to Factory reset and the phone rebooted to the same screen stuck with logo. I longed pressed the power button and it got switched off and then again turned it on. It started and is working fine but I cant factory set it, nor cant I access recovery to flash anything.
Click to expand...
Click to collapse
I've got a good news and bad news for you.
The bad news is, no one has the older 2.8.x TWRP image files and there are no threads that have the download links for the older version of TWRP. So you're stuck and you have lost your recovery. You have lost everything... Having no recovery means you can't do a lot of things like factory reset, any wipe of a partition, you won't be able to update your system, you won't be able to flash zip files to enhance your experience and many more... I'm sorry my friend...
The good news is, I've got you covered. I had saved the older TWRP so that if anyone one day would need that recovery image, I would be able to help them.
Download the older TWRP from here : https://drive.google.com/file/d/0B2Ms-zaNd3SiTmpxX0UtYUV2R1k/view?usp=drivesdk
Flash it. You should get back your recovery.

e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.

Plush suthar said:
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Click to expand...
Click to collapse
Which ROM you are on currently?
If possible post screenshot of about device in setting.

Fap4k said:
Which ROM you are on currently?
If possible post screenshot of about device in setting.
Click to expand...
Click to collapse
using resurrection remix marshmallow 6.0...

Plush suthar said:
using resurrection remix marshmallow 6.0...
Click to expand...
Click to collapse
Did you ever updated bootloader?
If not than update your bootloader and install latest recovery!!

Plush suthar said:
e: unknown command (log)
e: unknown command (log)
am not able to make my device android 7.0 running...
i tryed and install kernal after that but no luck, stuck on boot only 1 plus logo will appear, please recommend any solution.
Click to expand...
Click to collapse
By stuck on boot, I didn't know you meant that it showed only the OnePlus logo and not even powered by Android.
In that case, follow this guide to update your bootloader :
https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917

Kate CM13 Flash/Repair guide.

Dwl99 put a great guide together, the link is here:
http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-special-edition-kate-t3523371
Another guide I found useful is http://en.miui.com/thread-363264-1-1.html
Full URL of original post is:
https://forums.whirlpool.net.au/forum-replies.cfm?t=2566258&p=6&#r120
Now, I did it in a slightly different way, I prefer my way because I believe it is safer but here goes:
0. Update Miui to latest version Using the OTA update or Fastboot/Miflash method mentioned above. (I have a guide in this thread)
Once up to date:
1. Unlock the boot loader using the official method, this can take two 2 three days using en.miui.com/unlock/
Download the unlock tool. - Enable unlock boot loader options in developer options on MIUI (This can be done by tapping 10 times quickly on "Miui Version" in the about phone section of the phone. After this, go to additional settings >Developer options > enable developer options and unlock boot loader.
Next simply follow the guide on the MIUI unlock tool to unlock boot loader.
2. Flash TWRP ZCX Version: http://forum.xda-developers.com/redmi-note-3/how-to/zcx-twrp-install-twrp-flash-supersu-t3462448
This version of TWRP allows you to see and backup ALL partitions of your Xiaomi device.
Make sure you boot into this TWRP after flashing so it sticks (otherwise your phone will not boot)
Use the settings to back up ALL partitions to your EXTERNAL SD card. Keep that safe for the future in case you break your phone or lose imei or whatever.
I recommend transferring this backup to a PC or desktop. - Once this is done, you can breathe easy, you will always have a complete full backup of your device should you break it, you can relax in the future.
3. After backing up all of the partitions to the external SD card:
Download some files on https://forums.whirlpool.net.au/forum-replies.cfm?t=2566258&p=6&#r120
The 4 main files you need are: 1 CM13 rom file, 2 TWRP Cofface Version, 3 the KATE version of CM13 firmware files (Whirlpool has this on his guide at the bottom edit) and 4 your favourite version of the Google apps @ opengapps.org
The version you will need is ARM64 version 6 for CM13.
Transfer these files to your phone external storage (We will be wiping internal storage).
4. Flash the Cofface edition of TWRP to your Phone either using Fastboot or TWRP.
The reason for this is I have found ZCX version, whilst awesome for seeing and backing up all parts of the MIUI phone, actually breaks non MIUI flashes because it is designed primarily to work well with MIUI Roms (hence we use them to back up)
All TWRP versions can be found here: http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708/
Once Cofface TWRP is flashed you can move onto step 5 – Flashing Roms.
*NOTE* I have read some people recommend ALKA TWRP to A) backup all partitions, but also B, to flash CM as it does all things. I am only sharing my personal experience of what I have done here, and Alka could work well, but I have not tested it.
All I can say is flashing CM13 with ZCX TWRP Broke my device. – But it was great for making backups.
5. Flashing. Here all you need to do is boot into Cofface TWRP and go to Wipe. Choose advanced options. And wipe ALL partitions you see (Don’t worry, Cofface will not let you wipe out your boot loader, Recovery, IMEI or anything else that is critical) – First flash CM13. Then next, flash the Kate CM13 firmware, and third flash Opengapps. 1 after another (I actually added all three zips in that order and let them flash all together)
6. Reboot and enjoy. You now have an Unrooted CM13 with google apps a working fingerprint reader working radio etc. Happy days.
7. – EMERGENCY FIX EMERGENCY FIX!!! – As I mentioned earlier, TWRP zcx broke my device when I flashed the Roms. I was facing a device decryption error and 0mb data problem.
I fixed this with this URL http://en.miui.com/thread-344450-1-1.html
There is a file there called TWRP_Kenzo_Fix.zip and a batch script that will restore your phone and rebuild the partitions and install Cofface twrp for you!!! So that’s a good option if you break it.
Hope that helps

ZCX-TWRP works perfect for CM-ROMs. I've flashed so many ROMs without any problem!

Upgrade path from xXx no limits 10.2 to OOS 9.0.5?

I have seen some simlar posts, but in my case the phone is unencrypted. Currently TWRP3.2.1-1.
I am thinking of going back to stock OOS and reinstalling twrp and magisk.
I have a full backup through twrp and sd backup through adb, so I am not worried about losing anything.
What's is the simplest upgrade path?

kuhnto said:
I have seen some simlar posts, but in my case the phone is unencrypted. Currently TWRP3.2.1-1.
I am thinking of going back to stock OOS and reinstalling twrp and magisk.
I have a full backup through twrp and sd backup through adb, so I am not worried about losing anything.
What's is the simplest upgrade path?
Click to expand...
Click to collapse
Hello, you need to remove your screen lock and clean flash the OxygenOS 5.1.4(you can skip format of internal storage for now) with your new recovery, I recommend this one to flash before flashing 5.1.4:
https://drive.google.com/file/d/1UlTftbe6wooAs4Fp0cjwXlOKmfQHgdfL/view?usp=drivesdk
After that flash magisk(I recommend 18.1) and no verity patch you'll find it here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040
If you can sucessfully boot into 5.1.4 and your internal storage is accessible(don't enable any screen lock security) you are ready now to proceed with dirty flash(you have Oreo recovery now, so delete compatibility.zip) like described here(you can go to 9.0.5 skipping 5.1.7, works for majority) https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040
You can update to the latest recovery 3.3.x after you have successfully completed the installation of 9.0.5.

Thank you so much! Sounds pretty straight forward. Now I just need to wait for a time when i will be in critical need of my phone in 6 hours to start this process.

kuhnto said:
Thank you so much! Sounds pretty straight forward. Now I just need to wait for a time when i will be in critical need of my phone in 6 hours to start this process.
Click to expand...
Click to collapse
Good luck, report back if successful or help needed.

strongst said:
...After that flash magisk(I recommend 18.1) and no verity patch you'll find it here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040...
Click to expand...
Click to collapse
will no-verity-op5(T)_V3_treble_.zip work with the magisk 18.1 downloaded from above? the link was in the instructions.

kuhnto said:
will no-verity-op5(T)_V3_treble_.zip work with the magisk 18.1 downloaded from above? the link was in the instructions.
Click to expand...
Click to collapse
Yes, I'm using the same constellation for example:good:

strongst said:
...delete compatibility.zip...
...You can update to the latest recovery 3.3.x after you have successfully completed the installation of 9.0.5....
Click to expand...
Click to collapse
Two MOre questions... I think i read somewhere how to remove compatability.zip, but I will need to check on that. IS there somewhere I can reference? and does this have to do with the unencrypted data partition?
Also I saw a TWRP 3.2.3 that had "nocompat check" IS this something to do with the non-encrypted partition?

kuhnto said:
Two MOre questions... I think i read somewhere how to remove compatability.zip, but I will need to check on that. IS there somewhere I can reference? and does this have to do with the unencrypted data partition?
Also I saw a TWRP 3.2.3 that had "nocompat check" IS this something to do with the non-encrypted partition?
Click to expand...
Click to collapse
To your first question: it's mentioned there https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040 and I explained you before
2nd: don't use other TWRPs in any stage, it will be more difficult to troubleshoot
Both have nothing to do with the encryption status of your data partition. It's just a compatibility check from oneplus.

Here is my progress so far...
Downloaded (Some later as I found I needed them):
1. twrp-3.2.3-0-20181031-codeworkx-cheeseburger
2. Magisk-v18.1.zip
3. twrp-3.3.0-0-20190427-codeworkx-cheeseburger.img
4. Magisk-v19.2.zip
5. OnePlus5Oxygen_23_OTA_048_all_1904191531_09adcad0d3e4.zip
6. no-verity-op5(T)_V3_treble_.zip
7. OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6.zip
8. Magisk-uninstaller-20190204.zip
Actions:
1. Backed up sdcard
2. NAndroid backup
3. FLashed twrp-3.2.3-0-20181031-codeworkx-cheeseburger
4. Flash suscessful
5. flashed OS - Error - Zip Treble compatability error
6. Remembered I need to remove compatabilitycheck. - but now I realized I tried flashing 9.x.x. I need to flash 5.1.4 per instructions
7. Spent 15 minutes trying to find 5.1.4. FOund it!!
8. Flashing OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6
9. Flashed
10. Seemed to work except the failed to mount vendor
11. Wiped Cache..
12. Flashed Magisk 18.1
13. wipe Cache again
14. Rebootsing and crossing fingers
15. Splash screen boot loops then boots to TWRP - Forgot no-Verity
16. Flashing 5.1.4 + MAgisk 18.1 + no-Verity
17. Rebooting
18. Seems to be booting into something...
19. It booted into OS and it shows 5.1.4 of the OOS version
20. Ran MAgisk Manager - did not show MAgisk. but none the less, I am moving forward
21. Checked if internal storage is accessible - Check
22. Downloaded Total Commander
23. Deleted compatibility.zip from OnePlus5Oxygen_23_OTA_048_all_1904191531_09adcad0d3e4
24. Taking nandroid backup - But need to clear more space off my USB - I needed to delete Drone videos my brother took right before he passed away.
25. Forgot to get MAgisk Uninstaller - Downloading now
26. Installed the uninstaller
27. Tried installing 9.0.5 - Error Zip Trible Compatibility error - Invalid zip file format. I feel that I might need to read some instructions
28. Let my try to get back to 5.1.4 GOTO step 16.
29. That got me back to functional - My battery is low so I am stopping for the night.
30. After getting bored I tried installing 9.0.5 - Worked
31. Installed MAgisk 19.1 - Worked
32. Installed no-verity - Worked
OS booted - 9.0.5
I think I might have tried installing the 9.0.5 form the usb stick perhaps that did not have the compatability.zip removed. TWRP sometimes has me in USB and other times in the phone. Perhaps I selected the wrong thing????
Working well now

@kuhnto so you've got what you need?

strongst said:
@kuhnto so you've got what you need?
Click to expand...
Click to collapse
Yep! Everything is updated. I posted my effort for posterity for anyone else doing the same.

Questions about upgrading Lineage OS 16 to 17

Hello,
I do have some questions about upgrading LOS from 16 to 17, maybe someone can help me bringing a little light into this upgrading process.
- Is the sideload way the correct way to do this? ( https:// wiki.lineageos.org /devices /fajita /upgrade)
- What´s about the play services, I dont have any installed ( ..."If you did not have Google Apps installed, you must wipe the Data partition (or perform a factory reset) to install them"...) So if later on I want to install e.g. opengapps I have to wipe all my data after upgrading to 17??? (How? TWRP - wipe -advanced wipe - data and cache ???)
and what´s with all may data? I have titanium backup pro (no SD card), so I backup may phone, put it to my PC, upgrade to 17, wipe all data, put the backup back to phone and reboot?
Or do I have to install Magisk.zip and titanium.zip from within TWRP again first
- What do I do if the sideload fails?
- Can I do the upgrad process with TWRP too? (copying and installing from within TWRP?)
- And what about with the A/B slots, no installing twice on both slots?
As you see, I am unsure on how to do things right and I only did this once before as I installed Lineage OS.
(This would be the way I would do this:
- backup all data to PC
- Boot into TWRP
- copy LOS17.zip. Magisk.zip and Titaniumbackup-pro.zip into internal storage
- install LOS17 and boot into TWRP
- wipe data and cache
- install magisk and TB
- copy all data back and restore? (only user data or the system data too??))
Maybe someone can help me with this. Thanks!

My guide for installing Lineage maybe helpful: Guide Installing Lineage
I would recommend a clean install. Most that have tried to follow that wiki have had issues (if you look in the LOS thread). I haven't used. TB zip, but I did use my TB data from the app without issues. If you dont use Gapps, just dont install them. Skip that step. You still have to reboot to recovery to install Magisk though. I dont think I would try a TB zip until after the first boot.
Installing twice is for the intial install to get the same thing on both slots. You dont want Android 9 on one slot and Android 10 on another, or LOS 17 on one and OOS on another. Once you have LOS 17 on both slots and go to update you will just flash once. See my guide about doing an update.

Thank you for your reply,
so if I got your answer right, I should install the LOS17 like the LOS16 before, as a clean,fresh install.
Seems reasonable to me
I will do the same steps as you gave me before https://forum.xda-developers.com/oneplus-6t/help/instructions-installing-lineage-t3949628
- Backup everything to the PC, so you will need to copy all your data over.
- Sync all your accounts, etc.
- In TWRP format data. Reboot recovery
- Factory Reset.
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Lineage (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Flash TWRP Installer (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Reboot to Recovery (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Flash Gapps
- Flash Magisk
- Reboot to System.
- Then you should be able to setup the device, copy everything back over. Restore your data.
Will do the flash on weekend, then I will let you know....
Thanks.

KKF32 said:
Thank you for your reply,
so if I got your answer right, I should install the LOS17 like the LOS16 before, as a clean,fresh install.
Seems reasonable to me
I will do the same steps as you gave me before https://forum.xda-developers.com/oneplus-6t/help/instructions-installing-lineage-t3949628
- Backup everything to the PC, so you will need to copy all your data over.
- Sync all your accounts, etc.
- In TWRP format data. Reboot recovery
- Factory Reset.
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Lineage (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Flash TWRP Installer (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Reboot to Recovery (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Flash Gapps
- Flash Magisk
- Reboot to System.
- Then you should be able to setup the device, copy everything back over. Restore your data.
Will do the flash on weekend, then I will let you know....
Thanks.
Click to expand...
Click to collapse
How did it go?

badpanda said:
How did it go?
Click to expand...
Click to collapse
To put it short: a disaster
What I did:
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Magisk
- Flash TB
- Reboot to System.
What I got was a "Qualcom Crashdump Mode" kind of report
What I used: lineage-17.1-20200418-nightly-fajita-signed / twrp-installer-3.3.1-1-fajita / Magisk-v20.4
So I thought maybe the "no factory reset" at the beginning may caused this problem, so I started the whole flashing again.
Long story short: Being distracted I once forgt to flash TWRP after the LOS and now I am stuck in fastboot.
Cant get anymore into TWRP, "fastboot boot TWRP.img" always throws me into fastboot forever wait
Tried to flash TWRP direct from fastboot "fastboot flash recovery twrp.img", always get a write error.
So, at the moment all I can get in is the bootloader, and I have no clou how to get TWRP up and running again.
Edit: Managed to get into TWRP again, but this double flash + Magisk always gives me this "Qualcomm Crashdump Mode"
Help would very much appreciated!

KKF32 said:
To put it short: a disaster
What I did:
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Magisk
- Flash TB
- Reboot to System.
What I got was a "Qualcom Crashdump Mode" kind of report
What I used: lineage-17.1-20200418-nightly-fajita-signed / twrp-installer-3.3.1-1-fajita / Magisk-v20.4
Click to expand...
Click to collapse
So you tried to go straight to LOS 17, used an old version of TWRP, and never wiped data while going between Android 9 and 10? None of that will work. I think didn't make it clear, you need you need to be on the OOS 10 firmware first. Flash OOS 10 to both slots, at this point using the fastboot ROM would be my suggestion, like my [Guide]Installing Lineage.
Once you have Android 10 in place one both slots, then start your OS 17 install. Note there is a cliff notes version of that guide in the second post, if you don't want all the "wordy" details.

Oh my, I really didn´t understood the step with "get OOS10 on both slots first"
I am often a little sloppy with details, bad habit, will take some time tomorrow and do the reading and the flashing then.
Thanks again.

KKF32 said:
Oh my, I really didn´t understood the step with "get OOS10 on both slots first"
I am often a little sloppy with details, bad habit, will take some time tomorrow and do the reading and the flashing then.
Thanks again.
Click to expand...
Click to collapse
Make sure you use the"unofficial" version of TWRP, linked to in that guide, rather than the outdated official one you used before as well.

OhioYJ said:
Make sure you use the"unofficial" version of TWRP, linked to in that guide, rather than the outdated official one you used before as well.
Click to expand...
Click to collapse
So, LOS17 is up and running, I did it the long way but good to know the fastboot Rom method now. I confess some part of this thread would not have been necessary if had read your installations instruction carefully....
So let me thank you for patience und help, "Reading broadens the mind", I often tell others, will remind myself nexttime

Boot Problem after Successful TWRP flash

Hi,
I'm sure someone else will have had my problem but I can't seem to find a straight forward solution.
I am wanting to upgrade my Samsung S7 Edge, SM-G935F Exynos, to the latest Lineage OS with Android 10 as Samsung are no longer supporting my phone. The phone is unlocked as supplied from Samsung.
I downloaded Odin v3.14 and successfully flashed TWRP 3.4.0.0 hero.2lte.img.tar. I activated Developer Options and OEM unlock before flashing.
I can enter TWRP but am unsure what I do regarding the Unmodified System Partition options on the 1st TWRP screen so I hit 'Keep Read Only' and then 'Reboot' only to find that the phone attempts to restart, I see the Samsung Galaxy S7 Edge splash screen which then goes off and restarts again repeatedly, so I can't check if all my data etc. is ok on the phone. I did back up Whatsapp and made s Smart Switch backup too but forgot to do Samsung & Google account backups before the flashing.
I'm assuming I've missed something out in the flashing procedure but am not sure of exactly what. I have previously flashed and upgraded Galaxy S3, S3 Mini & a Tab2 10.1 using earlier TWRP versions so it's not that I'm a total beginner. I also tried to do a rom backup via TWRP but that failed and also a wipe Dalvik cache but that also failed.
Please advise:
1. what I've done wrong if anything?
2. Best way to restore the phone without losing existing data if possible perhaps with stock rom flashing? I could try the Smart Switch Emergency Software recovery & Initialisation but I understand that resets the phone to Factory settings loosing all data.
3. Procedure to flash Lineage rom that's 'idiot proofed'?
Thanks in advance.

rebgershon said:
Hi,
I'm sure someone else will have had my problem but I can't seem to find a straight forward solution.
I am wanting to upgrade my Samsung S7 Edge, SM-G935F Exynos, to the latest Lineage OS with Android 10 as Samsung are no longer supporting my phone. The phone is unlocked as supplied from Samsung.
I downloaded Odin v3.14 and successfully flashed TWRP 3.4.0.0 hero.2lte.img.tar. I activated Developer Options and OEM unlock before flashing.
I can enter TWRP but am unsure what I do regarding the Unmodified System Partition options on the 1st TWRP screen so I hit 'Keep Read Only' and then 'Reboot' only to find that the phone attempts to restart, I see the Samsung Galaxy S7 Edge splash screen which then goes off and restarts again repeatedly, so I can't check if all my data etc. is ok on the phone. I did back up Whatsapp and made s Smart Switch backup too but forgot to do Samsung & Google account backups before the flashing.
I'm assuming I've missed something out in the flashing procedure but am not sure of exactly what. I have previously flashed and upgraded Galaxy S3, S3 Mini & a Tab2 10.1 using earlier TWRP versions so it's not that I'm a total beginner. I also tried to do a rom backup via TWRP but that failed and also a wipe Dalvik cache but that also failed.
Please advise:
1. what I've done wrong if anything?
2. Best way to restore the phone without losing existing data if possible perhaps with stock rom flashing? I could try the Smart Switch Emergency Software recovery & Initialisation but I understand that resets the phone to Factory settings loosing all data.
3. Procedure to flash Lineage rom that's 'idiot proofed'?
Thanks in advance.
Click to expand...
Click to collapse
1] You didn't formatted /data and/or flashed magisk or supersu after booting into twrp first time.
Note that you need to format /data under wipe in twrp and type yes and then again reboot in twrp. This is necessary step to disable encryption. And after that flash magisk without any reboot or flash your required rom by following your respective rom thread.
Please note that keeping system read only will cause you to flash in systemless root mode like magisk or super su in systemless mode. There is no difference between normal root mode and systemless root mode except that you will need to allow system modifications in twrp in normal root which will in turn trigger dm verity check and you will need to flash no verity zip to make phone bootable when system modification method (normal root) is selected. Plus system modification will cause certain apps to detect root easily plus increasing complications like I said above. So just keep read only and flash magisk and you will get root in systemless mode without any cons !
Here, you said you're getting a verification screen after rebooting twrp..
This can be caused either by.
1. Not formatting /data after booting twrp for first time
2. Not flashing magisk after formatting /data
3. Enabling system modifications and not flashing no verity zips/magisk
4. Oem unlock is not enabled..
2] You cannot restore data if you didn't back it up before messing with it, or you made a titanium backup/twrp backup.
Smart switch cannot flash phone anymore ..
Yes, flashing stock firmware using home_csc in odin, will not delete data and may restore your phone, but no guarantee that it will work, you can try though. Thats why its strictly advised to do backup before messing your phone in anyway..
3. Pls refer or ask in your respective rom thread.
Sent from my hero2lte using XDA Labs

shah22 said:
1] You didn't formatted /data and/or flashed magisk or supersu after booting into twrp first time.
Note that you need to format /data under wipe in twrp and type yes and then again reboot in twrp. This is necessary step to disable encryption. And after that flash magisk without any reboot or flash your required rom by following your respective rom thread.
Please note that keeping system read only will cause you to flash in systemless root mode like magisk or super su in systemless mode. There is no difference between normal root mode and systemless root mode except that you will need to allow system modifications in twrp in normal root which will in turn trigger dm verity check and you will need to flash no verity zip to make phone bootable when system modification method (normal root) is selected. Plus system modification will cause certain apps to detect root easily plus increasing complications like I said above. So just keep read only and flash magisk and you will get root in systemless mode without any cons !
Here, you said you're getting a verification screen after rebooting twrp..
This can be caused either by.
1. Not formatting /data after booting twrp for first time
2. Not flashing magisk after formatting /data
3. Enabling system modifications and not flashing no verity zips/magisk
4. Oem unlock is not enabled..
2] You cannot restore data if you didn't back it up before messing with it, or you made a titanium backup/twrp backup.
Smart switch cannot flash phone anymore ..
Yes, flashing stock firmware using home_csc in odin, will not delete data and may restore your phone, but no guarantee that it will work, you can try though. Thats why its strictly advised to do backup before messing your phone in anyway..
3. Pls refer or ask in your respective rom thread.
Thanks for your reply Shah though I'm still a bit confused by it.
UnIock OEM was enabled as was USB debugging.
Fortunately, I was able to reflash the stock rom and phone is working again but what sort of backup are you indicating in part 2. above), NAND, Smartswitch or just back up to google, Samsung & Whatsapp accounts?
In 1). of your reply you say 'You didn't formatted /data and/or flashed magisk or supersu after booting into twrp first time.
Note that you need to format /data under wipe in twrp and type yes and then again reboot in twrp. This is necessary step to disable encryption. And after that flash magisk without any reboot or flash your required rom by following your respective rom thread.'
I thought that if I do format /data my data would be lost and I want to make a NAND backup of the existing rom and data before flashing/modifying but if that doesn't loose the data, I assume then the steps are as follows:
1. Flash TWRP with Odin
2. Boot into Recovery-TWRP
3. Tap on the Read Only button on the 1st TWRP screen
4. Format /data under wipe in TWRP and tap yes and then reboot in TWRP. - Do you mean reboot the phone into TWRP of just go back into the TWRP main menu & when do I make the NAND backup?
5. Flash magisk or supersu from SD card no reboot
6. Flash Lineage OS rom from SD card.
7. Reboot.
Please correct any errors above as I've now tried 3 times since my original post without success but always managed to reflash the stock rom to get me going again.
Click to expand...
Click to collapse

rebgershon said:
Thanks for your reply Shah though I'm still a bit confused by it.
Click to expand...
Click to collapse
Thats why you read forums again and again and unless you are sure and know what you're doing, don't proceed with these things and read again.
rebgershon said:
UnIock OEM was enabled as was USB debugging.
Fortunately, I was able to reflash the stock rom and phone is working again but what sort of backup are you indicating in part 2. above), NAND, Smartswitch or just back up to google, Samsung & Whatsapp accounts?
Click to expand...
Click to collapse
Upto you which backup you prefer, saving data on separate storage is the main goal as rooting and flashing custom rom would erase all your data from phone.
rebgershon said:
I thought that if I do format /data my data would be lost and I want to make a NAND backup of the existing rom and data before flashing/modifying but if that doesn't loose the data, I assume then the steps are as follows
Click to expand...
Click to collapse
What you mean exactly ? What doesn't loose the data ? Flashing custom rom first time/rooting always erases your data and yes you need to backup before flashing/modifying.
rebgershon said:
1. Flash TWRP with Odin
2. Boot into Recovery-TWRP
3. Tap on the Read Only button on the 1st TWRP screen
4. Format /data under wipe in TWRP and tap yes and then reboot in TWRP. - Do you mean reboot the phone into TWRP of just go back into the TWRP main menu & when do I make the NAND backup?
5. Flash magisk or supersu from SD card no reboot
6. Flash Lineage OS rom from SD card.
7. Reboot.
Click to expand...
Click to collapse
In step 4. Reboot again in twrp after formatting /data.
When do you make nand backup?? Lol, at this point your phone would have nothing to backup, you should have made a backup the first time you tried modifying your phone. Because flashing stock rom like you said you did many times, already formats the phone.
If you mean you want to backup your phone again, then you can't backup in twrp in this stage. Backup before flashing twrp through any means.
Step 5 is correct, I don't know about step 6. I never flashed lineage and have no experience about it. Pls refer lineage's respective rom thread for exact steps. Good luck
Sent from my hero2lte using XDA Labs

shah22 said:
Thats why you read forums again and again and unless you are sure and know what you're doing, don't proceed with these things and read again.
Upto you which backup you prefer, saving data on separate storage is the main goal as rooting and flashing custom rom would erase all your data from phone.
What you mean exactly ? What doesn't loose the data ? Flashing custom rom first time/rooting always erases your data and yes you need to backup before flashing/modifying.
In step 4. Reboot again in twrp after formatting /data.
When do you make nand backup?? Lol, at this point your phone would have nothing to backup, you should have made a backup the first time you tried modifying your phone. Because flashing stock rom like you said you did many times, already formats the phone.
If you mean you want to backup your phone again, then you can't backup in twrp in this stage. Backup before flashing twrp through any means.
Step 5 is correct, I don't know about step 6. I never flashed lineage and have no experience about it. Pls refer lineage's respective rom thread for exact steps. Good luck
Sent from my hero2lte using XDA Labs
Click to expand...
Click to collapse
Thanks again Shah for your reply/help.
I followed the instructions and got the lineage rom installed and Gapps but I don't think Gapps installed properly as I wasn't able to restore any of the saved data from my google account and it wouldn't allow me to add any other accounts except email so for now I've restored the stock rom and my data.
Is there another Android 10 rom you can recommend besides lineage that will have a similar appearance to Samsung?

rebgershon said:
Thanks again Shah for your reply/help.
I followed the instructions and got the lineage rom installed and Gapps but I don't think Gapps installed properly as I wasn't able to restore any of the saved data from my google account and it wouldn't allow me to add any other accounts except email so for now I've restored the stock rom and my data.
Is there another Android 10 rom you can recommend besides lineage that will have a similar appearance to Samsung?
Click to expand...
Click to collapse
I don't recommend any rom except a stock rooted debloated one.. (like Alexndr's devbase)
Reason : because full custom roms have a high chance to mess up your phone's efs and permanent soft brick issues.
But, I'm in love with infinity wallpapers, dark mode and android 10 in general like all others these days.. so if you really want samsung android 10 for S7 edge, then Floyd V4 is your best bet.. see on rom and software developer section of s7 edge to find floyd v4. Its a s9 android 10 one ui 2 port...
Personally, I'm using latest alexndr's devbase rom. Because I'm still paranoid about fully custom or ported roms
Alexndr's devbase is a full stock oreo - debloated rom. Which has option to root during flashing in twrp too. Its perfect for my needs.
But maybe soon, I will change to Floyd v4 to experience the future.. who knows
Sent from my Legendary Hero2LTE using Tapatalk

shah22 said:
I don't recommend any rom except a stock rooted debloated one.. (like Alexndr's devbase)
Reason : because full custom roms have a high chance to mess up your phone's efs and permanent soft brick issues.
But, I'm in love with infinity wallpapers, dark mode and android 10 in general like all others these days.. so if you really want samsung android 10 for S7 edge, then Floyd V4 is your best bet.. see on rom and software developer section of s7 edge to find floyd v4. Its a s9 android 10 one ui 2 port...
Personally, I'm using latest alexndr's devbase rom. Because I'm still paranoid about fully custom or ported roms
Alexndr's devbase is a full stock oreo - debloated rom. Which has option to root during flashing in twrp too. Its perfect for my needs.
But maybe soon, I will change to Floyd v4 to experience the future.. who knows
Shah,
Many thanks for the recommendation of the FloydQ rom.
I installed it yesterday after making all backups inc. Smartswitch.
Very easy to install both from flashing and Aroma installation viewpoints. Ran 1st time without a glitch and phone now thinks its an S9+ running Android 10 a la Samsung. I even managed to transfer my Smartswitch backup to my wife's old S7 Edge and then used Smartswitch to transfer from that phone to the 'S9+'.
Only glitch was logging into my Samsung account but sorted that as well so all in all very happy so far.:good:
Click to expand...
Click to collapse