Related
I have a moto g5 plus xt1687 and I was able to unlock the boot loader and install TWRP successfully. I then install no-verity-opt-encrypt-5.1.zip without trouble and reboot to TWRP again. When I try and install Magisk v14 I get the error message "/system could not be mounted"
I have wiped the system earlier so I do not have an operating system installed anymore but I can get into TWRP. What are my solutions? Thanks.
Flash a custom rom in TWRP or reflash stock with fastboot.
Sent from my Moto G (5) Plus using Tapatalk
Custom rom
riggerman0421 said:
Flash a custom rom in TWRP or reflash stock with fastboot.
Sent from my Moto G (5) Plus using Tapatalk
Click to expand...
Click to collapse
Where can I find the custom rom for moto g5 plus xt1687? Thanks
s_beckett said:
I have a moto g5 plus xt1687 and I was able to unlock the boot loader and install TWRP successfully. I then install no-verity-opt-encrypt-5.1.zip without trouble and reboot to TWRP again. When I try and install Magisk v14 I get the error message "/system could not be mounted"
Click to expand...
Click to collapse
Hi,
If you install the ElementalX custom kernel v1.02 then you fix the error.
Futhermore, with this kernel you don't need the "no-verity-patch"... as I advise that this patch writes the SYSTEM partition... so you lost the option for OTAs.
Here the thread to download this custom kernel:
http://forum.xda-developers.com/g5-plus/development/kernel-elementalx-1-00-moto-g5-plus-t3614211
Regards!
ElementaX
manos78 said:
Hi,
If you install the ElementalX custom kernel v1.02 then you fix the error.
Futhermore, with this kernel you don't need the "no-verity-patch"... as I advise that this patch writes the SYSTEM partition... so you lost the option for OTAs.
Here the thread to download this custom kernel:
http://forum.xda-developers.com/g5-plus/development/kernel-elementalx-1-00-moto-g5-plus-t3614211
Regards!
Click to expand...
Click to collapse
I installed LineageOS and then ElementalX and when I reboot it takes me back to TWRP. Are my steps wrong? The bigger question is why am I getting the "/system could not be mounted" when I installed magisk v14 so remain unrooted??. I followed the steps carefully. What is a clear path out of this mess? Very frustrating. Any assistance is appreciated.
s_beckett said:
I installed LineageOS and then ElementalX and when I reboot it takes me back to TWRP. Are my steps wrong? The bigger question is why am I getting the "/system could not be mounted" when I installed magisk v14 so remain unrooted??. I followed the steps carefully. What is a clear path out of this mess? Very frustrating. Any assistance is appreciated.
Click to expand...
Click to collapse
Hi,
I'm on stock, so if you use LineageOS, then this is my recomendation:
- Reinstall Lineage and check that all works (remeber to do "wipe cache" after install it and before boot it).
- Then install the ElementalX-los version, and reboot. Check that all works.
- Finally, after a full reboot install Magisk v14.0.
If the error of mount in Magisk continues, ask @flar2 to fix the "los" version like the Stock-1.02.
Regards.
Some success
manos78 said:
Hi,
I'm on stock, so if you use LineageOS, then this is my recomendation:
- Reinstall Lineage and check that all works (remeber to do "wipe cache" after install it and before boot it).
- Then install the ElementalX-los version, and reboot. Check that all works.
- Finally, after a full reboot install Magisk v14.0.
If the error of mount in Magisk continues, ask @flar2 to fix the "los" version like the Stock-1.02.
Regards.
Click to expand...
Click to collapse
I was able to install magisk v14, then I installed PureNexus and the suggested gapps. When I reboot I kept going back to TWRP but if I go to the bootloader I am able to start the PureNexus OS without issue (no decrypt error). When I do a root check it indicates I am not rooted. What should I do in the proper order? Should I install no-verity-opt-encrypt-5.1. and "Magisk-v14 again without causing a problem, is that the solution? How many times can you reinstall that those files. Thank for your help.
s_beckett said:
I was able to install magisk v14, then I installed PureNexus and the suggested gapps. When I reboot I kept going back to TWRP but if I go to the bootloader I am able to start the PureNexus OS without issue (no decrypt error). When I do a root check it indicates I am not rooted. What should I do in the proper order? Should I install no-verity-opt-encrypt-5.1. and "Magisk-v14 again without causing a problem, is that the solution? How many times can you reinstall that those files. Thank for your help.
Click to expand...
Click to collapse
Sorry?
Magisk will need to be installed after then ROM and the Kernel.
Futhermore, if you use the proper kernel, you don't need to install the "no-verity-opt-encrypt-5.1".
Please, do it in this order:
1) Install PureNexus or your preferable ROM.
2) Boot and check it (don't configure, only a simple check).
3) Reboot to TWRP and install the ZIP of the custom kernel (I recomend ElementalX).
4) Boot and check it (again don't configure).
5) Reboot to TWRP and re-format the "Data" partition (select "f2fs" if it has another filesystem)... this will disable the "encryption enforcement" (as it formats withtout encryption and the kernel disables the enforcement).
6) Boot and configure.
7) Reboot to TWRP and install Magisk v14.
8) Boot and check MagiskManager, you're now rooted.
9) If you like install Xposed for Magisk and configure it.
That's all!
manos78 said:
Sorry?
Magisk will need to be installed after then ROM and the Kernel.
Futhermore, if you use the proper kernel, you don't need to install the "no-verity-opt-encrypt-5.1".
Please, do it in this order:
1) Install PureNexus or your preferable ROM.
2) Boot and check it (don't configure, only a simple check).
3) Reboot to TWRP and install the ZIP of the custom kernel (I recomend ElementalX).
4) Boot and check it (again don't configure).
5) Reboot to TWRP and re-format the "Data" partition (select "f2fs" if it has another filesystem)... this will disable the "encryption enforcement" (as it formats withtout encryption and the kernel disables the enforcement).
6) Boot and configure.
7) Reboot to TWRP and install Magisk v14.
8) Boot and check MagiskManager, you're now rooted.
9) If you like install Xposed for Magisk and configure it.
That's all!
Click to expand...
Click to collapse
First off really appreciate your help and patience with me. Followed your guidelines have root and PureNexus is working ok. One last issue that persists. Every time I reboot it goes directly to TWRP. I have to go to the bootloader and start the OS that way. How can I get it to boot directly into the OS? Thanks again.
s_beckett said:
First off really appreciate your help and patience with me. Followed your guidelines have root and PureNexus is working ok. One last issue that persists. Every time I reboot it goes directly to TWRP. I have to go to the bootloader and start the OS that way. How can I get it to boot directly into the OS? Thanks again.
Click to expand...
Click to collapse
This is because your bootloader thinks that it need to boot to the "recovery". So, try this:
1) Wipe cache.
2) Do a full power-off from the ROM.
manos78 said:
This is because your bootloader thinks that it need to boot to the "recovery". So, try this:
1) Wipe cache.
2) Do a full power-off from the ROM.
Click to expand...
Click to collapse
Unfortunately this did not work. Are there any other options?
s_beckett said:
Unfortunately this did not work. Are there any other options?
Click to expand...
Click to collapse
Enter into bootloader mode, connect your phone to the PC and type "fastboot continue" command in ADB.
manos78 said:
This is because your bootloader thinks that it need to boot to the "recovery". So, try this:
1) Wipe cache.
2) Do a full power-off from the ROM.
Click to expand...
Click to collapse
I have found success! I wiped the drive in TWRP and install Stoneware v67 then installed magisk v14 and the boot process is now directly to the OS and it is rooted. I did not load a custom ROM but it is working fine. Frankly, I really do not understand which ROM needs a custom one or not and wish there were clear instruction on this matter as there are so many ROMs and some did not install or work well when I tried them. In any event, I appreciate your ongoing assistance and patience with me.
s_beckett said:
I have found success! I wiped the drive in TWRP and install Stoneware v67 then installed magisk v14 and the boot process is now directly to the OS and it is rooted.
Click to expand...
Click to collapse
Great!
The behaviour you have observed is because at some point the "reboot cause" (the trigger that launch the recovery at every boot) isn't cleared or is everytime set incorrectly. If you found a method for clear the cause, then you can continue...
I've got a SM-G950F, and succesfully flashed TWRP on it.
Wiped /data, after that i flashed dm-verity and force encryption disabler, everything was ok until the first boot into the system.
It booted up, and immediately after that i turned off the phone and booted into TWRP, and for some reason it couldnt mount /data again.
The tutorial i have followed:
Thanks for the tutorial to: jesec
Part 1 - HOW-TO FLASH TWRP:
1. In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
2. Go to Settings -> Developer options and enable OEM Unlock option.
3. Download and Install Samsung Mobile Phones Drivers.
- Option 1: Download and Install Smart Switch for PC.
- Option 2: Download and Install standalone driver package.
4. Download and extract Odin (Samsung's Flash Tool) to your computer.
5. Download a .tar image of TWRP.
6. Reboot your device to download mode.
- Hold [VOLUME DOWN] + [BIXBY] + [POWER] for approx. 15 seconds.
- Read the warning carefully.
- If you agree, press [VOLUME UP] to get into Download mode. If you don't agree, STOP.
7. Open Odin and place that TWRP tar file in the [AP] slot.
8. Connect your phone.
9. Hold [VOLUME UP] + [BIXBY] + [POWER] on your phone and then press start on Odin.
10. Wait for the phone to reboot. DO NOT release [VOLUME UP] + [BIXBY] + [POWER] or you may not reboot into TWRP.
Part 2 - HOW-TO INITIALIZE TWRP: (for new phones)
1. If you completed Part 1 successfully, you should be in TWRP now. At this point, you will reach the screen asking you if you want to allow system modifications.
2. Select "Keep /system RO". (Don't swipe right or you may not be able to boot into system if you failed to complete next steps. However, you can swipe right to allow modifications if you are confident that you can complete next steps.)
3. Go to "Wipe" menu of TWRP and you will find "Format Data". Press "Format Data" and type "yes" to continue.
4. Go to "Reboot" menu and Press "Recovery" to reboot TWRP.
5. Download the latest dm-verity and force encryption disabler zip on your computer.
6. Transfer the zip to your phone.
- Option 1: MTP: Connect your phone with computer and just copy the zip to internal storage. (similar to how you transfer files when in system.)
- Option 2: ADB: Connect your phone with computer and run command "adb push /path/to/zip /sdcard/".
- Option 3: External SD: Copy the zip to an external SD and then insert the card to your phone.
7. Go to "Install" menu of TWRP and flash the zip.
TWRP is initialized and fully functional at this stage. Now you can either reboot into system or root, flash custom ROMs via TWRP.
Part 3 - HOW-TO ROOT:
1. Download the flashable zip.
- Option 1: Magisk
- Option 2: SuperSU (untested)
2. Transfer the zip to your phone.
3. Go to "Install" menu of TWRP and flash the zip.
Part 3a - HOW-TO FLASH CUSTOM ROMS:
1. Download the flashable zip.
2. Transfer the zip to your phone.
3. Go to "Install" menu of TWRP and flash the zip.
Simple.
Click to expand...
Click to collapse
Before the 1st boot i even rooted the device, that remained after the first boot, but no /data mount.
After the 5th try, i gave up.
What could be the problem, or is this normal on this phone?
Are you using latest twrp version 3.2.3.2
I'm using 3.2.1.0
kristof889 said:
I'm using 3.2.1.0
Click to expand...
Click to collapse
Use latest twrp 3.2.3.2 should have data mount and quota issues fixed.
You can flash the .Img file through twrp or flash the .img.tar file with Odin.
After flashing reboot straight into twrp and repeat part 2 of the guide you quoted.
I would be interested to know also if in download mode if you have a line in there saying rmm state?
Twrp for s8 exynos
https://dl.twrp.me/dreamlte/
Installed the 3.2.3.2 version, but nothing has changed. after the first boot into system, TWRP says cant mount /data..
I dont have anything like rmm state in download mode.
kristof889 said:
Installed the 3.2.3.2 version, but nothing has changed. after the first boot into system, TWRP says cant mount /data..
I dont have anything like rmm state in download mode.
Click to expand...
Click to collapse
I am assuming you followed the instructions that you quoted in your first post.(mainly part 2) after flashing twrp
Did you format data in twrp - not wipe - this is needed to decrypt your phone.
Rebooted back into twrp.
Did you flash the no verity opt zip (version 6) - this will disable re encryption of your phone when booting back into system.
This should all be done before booting back into system otherwise your phone will re encrypt itself.
I am assuming you followed the instructions that you quoted in your first post.(mainly part 2) after flashing twrp
Did you format data in twrp - not wipe - this is needed to decrypt your phone.
Rebooted back into twrp.
Did you flash the no verity opt zip (version 6) - this will disable re encryption of your phone when booting back into system.
This should all be done before booting back into system otherwise your phone will re encrypt itself.
Click to expand...
Click to collapse
I formatted data, not just wiped it.
I have installed the no verity opt, the latest version.
Even after these, my phone reencrypted itself.
kristof889 said:
I formatted data, not just wiped it.
I have installed the no verity opt, the latest version.
Even after these, my phone reencrypted itself.
Click to expand...
Click to collapse
When do the errors occur ie: during backup,restore,flashing something.
When first starting twrp did you swipe to allow modifications or did you leave it as read only.
You mean, the data mount error?
If yes, immediately after the 2nd boot into TWRP, after the first boot into system. Before i do anything in twrp, i check the log (with the button on the lower right) and it creates a bunch of errors, all in contact with the data partition.
So i can even do a proper backup.
If i flash any zip, upon the next boot into system it says something like verify failed, cannot reboot your phone and it gives a button wich used to restore the phone from recovery, but now i cant even do that bcoz it cant mount /data and thus can restore the phone.
kristof889 said:
You mean, the data mount error?
If yes, immediately after the 2nd boot into TWRP, after the first boot into system. Before i do anything in twrp, i check the log (with the button on the lower right) and it creates a bunch of errors, all in contact with the data partition.
So i can even do a proper backup.
If i flash any zip, upon the next boot into system it says something like verify failed, cannot reboot your phone and it gives a button wich used to restore the phone from recovery, but now i cant even do that bcoz it cant mount /data and thus can restore the phone.
Click to expand...
Click to collapse
Still sounds like you device is still encrypted.
Doing a factory reset with twrp should work to restore your phone or at worst you can re-flash your firmware.
If you can in twrp FORMAT data again and flash the no verity zip use version 6 zip file
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
I would be curious to know in twrp in the mount menu what options are ticked as well.
After the fresh flash, it was not encrypted because i could access the internal storage, and data was mounted.
Now in TWRP system(read only), cache and dalvik is mounted, and internal storage says 0MB
kristof889 said:
After the fresh flash, it was not encrypted because i could access the internal storage, and data was mounted.
Now in TWRP system(read only), cache and dalvik is mounted, and internal storage says 0MB
Click to expand...
Click to collapse
What Android version are you on?
When you flashed twrp it should have asked you whether or not to ' swipe to allow modifications ' did you swipe to allow or not.
In the mount menu of twrp I have ticked/checked data,cache,SD card the option at the bottom to allow read only I have ticked - this does not stop me from doing backups but does stop me from restoring (data mount error ) so you can leave it unticked.
I would.like to know your steps for twrp installation (not the one you quoted in first post) as I screwed up when I first tried.
I attached the software information bellow.
I have not swiped to allow for system modifications
First steps were the followimg:
Install .tra with odin
Immediately reboot to twrp
No swipe for system modifications
Format data
Flash no dm verity v6
(Flash magisk)
Reboot to system
kristof889 said:
First steps were the followimg:
Install .tra with odin
Immediately reboot to twrp
No swipe for system modifications
Format data
Flash no dm verity v6
(Flash magisk)
Reboot to system
Click to expand...
Click to collapse
Ok basically you have missed a step as far as I can see
(When I did mine I did swipe to allow modifications )
After you have formated data you will need to reboot back into twrp ( use reboot menu in twrp )
Then flash the no verity zip and magisk
If using magisk I would try the latest version 18 it's working ok for me.
Then boot into system to see if everything ok
Then reboot into twrp and see if the data mount issue is fixed.
spawnlives said:
Ok basically you have missed a step as far as I can see
(When I did mine I did swipe to allow modifications )
After you have formated data you will need to reboot back into twrp ( use reboot menu in twrp )
Then flash the no verity zip and magisk
If using magisk I would try the latest version 18 it's working ok for me.
Then boot into system to see if everything ok
Then reboot into twrp and see if the data mount issue is fixed.
Click to expand...
Click to collapse
Thank you for your advice. I will try it in the following days and will post the result.
I fixed this by flashing Renovate ICE's ROM and selecting the TWRP included in the AROMA installer.
Can access storage on TWRP now with no issues.
CoreyOS said:
I fixed this by flashing Renovate ICE's ROM and selecting the TWRP included in the AROMA installer.
Can access storage on TWRP now with no issues.
Click to expand...
Click to collapse
But i want to use the stock rom.
Maybe if i flash Renovate rom and after that again the stock?
kristof889 said:
But i want to use the stock rom.
Maybe if i flash Renovate rom and after that again the stock?
Click to expand...
Click to collapse
Why stock???
It pretty much is stock, just you have full control over the apps preinstalled and you can change colours of various UI elements.
It's just easier to flash a zip than it is to flash via ODIN, then flash TWRP and keep trying over and over to get this result when I know this rom works fine with CTSprofile.
You will only need to flash TWRP once and copy the rom to your phone.
The rest is magic (AROMA)
I haven't really had to mess with anything and have just installed and used the HSBC banking app as if it were an official phone. (ROOTED and custom ROM and Recovery)
One extra step you could take is to use Magisk hide and point it to the app you want to hide root from.
CoreyOS said:
Why stock???
It pretty much is stock, just you have full control over the apps preinstalled and you can change colours of various UI elements.
It's just easier to flash a zip than it is to flash via ODIN, then flash TWRP and keep trying over and over to get this result when I know this rom works fine with CTSprofile.
You will only need to flash TWRP once and copy the rom to your phone.
The rest is magic (AROMA)
I haven't really had to mess with anything and have just installed and used the HSBC banking app as if it were an official phone. (ROOTED and custom ROM and Recovery)
One extra step you could take is to use Magisk hide and point it to the app you want to hide root from.
Click to expand...
Click to collapse
So on that rom i can use s health and all knox based apps like normal?
If yes, i will try it, it looks very nice
Hey guys,
I recently flashed Omnirom and after doing so, noticed I had no signal. After flash, reboot, or resetting Network/Data settings, I'll have data for about 20-30 seconds. I can browse the web, but I can't send or receive calls or messages. Then it goes away completely. It sporadically returns, but drops again quickly.
Carrier is Verizon. My Sim card is still being read so the issue doesn't seem to be there. I've put it back in my Pixel 2 and it's working fine.
At a high level, this is what I've done over the past 12 hours:
1. My bootloader is unlocked. I flashed a new ROM and then it wouldn't boot.
2. I did a Factory reset through Recovery and then it booted into the ROM, where I noticed I had no signal
--Possibly an issue here? This factory reset wasn't done thru TWRP, but the stock(?) recovery. I noticed that after doing this, it wiped everything on my phone, including my Nandroid backups
3. I did another factory reset, still no service
4. I moved sim card from Sim Slot 2 to Sim slot 1, temporarily restored service. Then dropped.
5. I flashed OOS 9.0.12 back, service came back temporarily, then dropped
6. I did a network reset, restored service temporarily, then dropped
7. I reflashed modem, system, and vendor images
Anyone have any thoughts or suggestions? Otherwise, I'm probably going to send my phone back to OnePlus for repair.
Try restoring through the msm tool.
TheRemyx said:
Hey guys,
I recently flashed Omnirom and after doing so, noticed I had no signal. After flash, reboot, or resetting Network/Data settings, I'll have data for about 20-30 seconds. I can browse the web, but I can't send or receive calls or messages. Then it goes away completely. It sporadically returns, but drops again quickly.
Carrier is Verizon. My Sim card is still being read so the issue doesn't seem to be there. I've put it back in my Pixel 2 and it's working fine.
At a high level, this is what I've done over the past 12 hours:
1. My bootloader is unlocked. I flashed a new ROM and then it wouldn't boot.
2. I did a Factory reset through Recovery and then it booted into the ROM, where I noticed I had no signal
--Possibly an issue here? This factory reset wasn't done thru TWRP, but the stock(?) recovery. I noticed that after doing this, it wiped everything on my phone, including my Nandroid backups
3. I did another factory reset, still no service
4. I moved sim card from Sim Slot 2 to Sim slot 1, temporarily restored service. Then dropped.
5. I flashed OOS 9.0.12 back, service came back temporarily, then dropped
6. I did a network reset, restored service temporarily, then dropped
7. I reflashed modem, system, and vendor images
Anyone have any thoughts or suggestions? Otherwise, I'm probably going to send my phone back to OnePlus for repair.
Click to expand...
Click to collapse
Have you wiped the cache?
It's not a hardware issue.
rickysidhu_ said:
Try restoring through the msm tool.
Click to expand...
Click to collapse
I would also try the MSM tool to restore back to stock. Then reflash what you want for a ROM.
rickysidhu_ said:
Try restoring through the msm tool.
Click to expand...
Click to collapse
Scott said:
I would also try the MSM tool to restore back to stock. Then reflash what you want for a ROM.
Click to expand...
Click to collapse
Thanks guys. Using MSM worked.
For those who may have the same issue, I used MSM to go back to 9.0.11 since a few people said they had issues with 9.0.12 such as not being able to unlock it. I restored 9.0.11, unlocked my device, then flashed the 9.0.12 OTA. Issue stayed resolved.
I did try to flash Omnirom again and the issue came back, so I'm curious as to what's happening. I'm going to try another Rom.
Just an update, this seems to happen with any rom I flash now. I tried Omnirom, Pixel Experience, and Syberia OS. They boot up but with no 4g connection. When I use MSM to go back to 9.0.11 or 9.0.12 everything works properly. Not sure what I may be missing?
Out of curiosity, how are you installing your custom ROMs. I have installed quite a few custom ROMs in the last week or so and have not encountered any issues. I use a USB pendrive with an OTG adapter to install my stuff as the phone normally ends up in an encrypted state so the internal storage will not be accessible when booting into TWRP. Here are the steps I use when installing a custom ROM:
01. Boot into TWRP
02. Wipe, then swipe. You can choose to Format Data if you want, but this will erase your internal storage so you will lose your recent pictures and other media.
03. Install full OOS 9.0.11/9.0.12 depending on which version is required for the custom ROM and install TWRP also.
04. Reboot recovery.
05. Install full OOS 9.0.11/9.0.12 and TWRP again to ensure both slots have OOS install on it. Use the same version you installed in step 3.
06. Reboot recovery.
07. Install your custom ROM and TWRP.
08. Reboot recovery.
09. Wipe, then swipe (Do not format; unsure if this makes a difference).
10. Install GApps if needed (ROM dependent) and optionally install Magisk and a custom kernel.
11. Reboot system and then wait to setup the phone.
As stated, this has worked flawlessly for me and I have not run into any issues. Admittedly, I have not tried Omnirom directly, but I have tried Omnirom Treskmod (not available on XDA) and SkyDragon which are both based on Omnirom and did not have issues with either. I have tried maybe 10 different custom ROMs in the last week on so and have not had any problems. Still trying to find the best ROM for me. You could say that I'm a flashaholic.
I hope this helps.
Ooms
dj_ooms said:
Out of curiosity, how are you installing your custom ROMs. I have installed quite a few custom ROMs in the last week or so and have not encountered any issues. I use a USB pendrive with an OTG adapter to install my stuff as the phone normally ends up in an encrypted state so the internal storage will not be accessible when booting into TWRP. Here are the steps I use when installing a custom ROM:
01. Boot into TWRP
02. Wipe, then swipe. You can choose to Format Data if you want, but this will erase your internal storage so you will lose your recent pictures and other media.
03. Install full OOS 9.0.11/9.0.12 depending on which version is required for the custom ROM and install TWRP also.
04. Reboot recovery.
05. Install full OOS 9.0.11/9.0.12 and TWRP again to ensure both slots have OOS install on it. Use the same version you installed in step 3.
06. Reboot recovery.
07. Install your custom ROM and TWRP.
08. Reboot recovery.
09. Wipe, then swipe (Do not format; unsure if this makes a difference).
10. Install GApps if needed (ROM dependent) and optionally install Magisk and a custom kernel.
11. Reboot system and then wait to setup the phone.
As stated, this has worked flawlessly for me and I have not run into any issues. Admittedly, I have not tried Omnirom directly, but I have tried Omnirom Treskmod (not available on XDA) and SkyDragon which are both based on Omnirom and did not have issues with either. I have tried maybe 10 different custom ROMs in the last week on so and have not had any problems. Still trying to find the best ROM for me. You could say that I'm a flashaholic.
I hope this helps.
Ooms
Click to expand...
Click to collapse
Because I had erased all data on my phone, I was doing mostly everything from Fastboot or ADB Sideload in TWRP. So my previous steps were something like this:
1. Use MSM to restore OOS 9.0.11
2. Unlock Bootloader
3. Fastboot to TWRP 3.3.0.2
4. Install TWRP on both slots (ADB Sideload)
5. Reboot Recovery
6. Install 9.0.12 on both slots (ADB Sideload)
7. Install TWRP (ADB Sideload)
8. Reboot System to verify I have signal
9. Reboot Recovery
10. Install custom ROM and TWRP (ADB Sideload)
11. Format Data through TWRP
12. Reboot System (No signal)
I had also noticed that there was some system app or process that was repeatedly crashing, but I couldn't tell what it was because the popup notification would disappear so quickly.
TheRemyx said:
Because I had erased all data on my phone, I was doing mostly everything from Fastboot or ADB Sideload in TWRP. So my previous steps were something like this:
1. Use MSM to restore OOS 9.0.11
2. Unlock Bootloader
3. Fastboot to TWRP 3.3.0.2
4. Install TWRP on both slots (ADB Sideload)
5. Reboot Recovery
6. Install 9.0.12 on both slots (ADB Sideload)
7. Install TWRP (ADB Sideload)
8. Reboot System to verify I have signal
9. Reboot Recovery
10. Install custom ROM and TWRP (ADB Sideload)
11. Format Data through TWRP
12. Reboot System (No signal)
I had also noticed that there was some system app or process that was repeatedly crashing, but I couldn't tell what it was because the popup notification would disappear so quickly.
Click to expand...
Click to collapse
I didn't notice any popups when setting up my device. The only thing I can say is that VoLTE never used to work properly for me on OOS. I had to edit a setting in serial mode to get VoLTE working on my network in the UK. Not sure if it is related at all. I highly doubt it. I noticed in your steps, you have not flashed GApps. I believe most custom ROMs don't contain GApps, only a select few. Is there a reason you are not flashing GApps? I know there are individuals who want to stay away from Google and use Micro-G as an alternative. I believe the minimum is to flash Pico or Nano GApps. I am not sure if there is possibly something in GApps that is related to data and telephony. The notification popup you are getting may also be related to not having GApps. I install the Nano GApps so I can get face unlock working. Maybe try that and then try installing Magisk after if you still have the same issues. You are rebooting the system in your Step 12. Maybe try and reboot recovery first, then reboot system to keep TWRP intact. You could try the steps that I posted. I use a USB pendrive but if you Format Data to clear your internal storage, it should not be encrypted after unless you reboot into OOS beforehand. You should be able to push files directly to internal storage through ADB in TWRP or you can maybe mount the phone on the computer and copy the files across. These are only suggestions. I haven't had the issues you are having but the steps I listed seem to have worked consistently for my. As a note, I have never had to use the MSMTool to get my phone back up and running again. I have used fastboot mode before though.
I hope this helps.
Ooms
TheRemyx said:
Because I had erased all data on my phone, I was doing mostly everything from Fastboot or ADB Sideload in TWRP. So my previous steps were something like this:
1. Use MSM to restore OOS 9.0.11
2. Unlock Bootloader
3. Fastboot to TWRP 3.3.0.2
4. Install TWRP on both slots (ADB Sideload)
5. Reboot Recovery
6. Install 9.0.12 on both slots (ADB Sideload)
7. Install TWRP (ADB Sideload)
8. Reboot System to verify I have signal
9. Reboot Recovery
10. Install custom ROM and TWRP (ADB Sideload)
11. Format Data through TWRP
12. Reboot System (No signal)
I had also noticed that there was some system app or process that was repeatedly crashing, but I couldn't tell what it was because the popup notification would disappear so quickly.
Click to expand...
Click to collapse
Not sure if it helps, but you are doing too many repeated steps. Skip 4 & 5, Format Data before installing 9.0.12. Skip 11. Why are you installing TWRP so many times?
dj_ooms said:
I didn't notice any popups when setting up my device. The only thing I can say is that VoLTE never used to work properly for me on OOS. I had to edit a setting in serial mode to get VoLTE working on my network in the UK. Not sure if it is related at all. I highly doubt it. I noticed in your steps, you have not flashed GApps. I believe most custom ROMs don't contain GApps, only a select few. Is there a reason you are not flashing GApps? I know there are individuals who want to stay away from Google and use Micro-G as an alternative. I believe the minimum is to flash Pico or Nano GApps. I am not sure if there is possibly something in GApps that is related to data and telephony. The notification popup you are getting may also be related to not having GApps. I install the Nano GApps so I can get face unlock working. Maybe try that and then try installing Magisk after if you still have the same issues. You are rebooting the system in your Step 12. Maybe try and reboot recovery first, then reboot system to keep TWRP intact. You could try the steps that I posted. I use a USB pendrive but if you Format Data to clear your internal storage, it should not be encrypted after unless you reboot into OOS beforehand. You should be able to push files directly to internal storage through ADB in TWRP or you can maybe mount the phone on the computer and copy the files across. These are only suggestions. I haven't had the issues you are having but the steps I listed seem to have worked consistently for my. As a note, I have never had to use the MSMTool to get my phone back up and running again. I have used fastboot mode before though.
I hope this helps.
Ooms
Click to expand...
Click to collapse
I had tried flashing GAPPs (ARM64-Nano) and it didn't seem to make a difference. I was skipping that and flashing Magisk just to confirm if I had service first. But would service/signal be dependent on something in GAPPs? I may try your way. I hadn't run into any issues with encrypted storage lately. The last few times I was able to get around it by booting to system first, then rebooting back to recovery.
schmeggy929 said:
Not sure if it helps, but you are doing too many repeated steps. Skip 4 & 5, Format Data before installing 9.0.12. Skip 11. Why are you installing TWRP so many times?
Click to expand...
Click to collapse
I was installing TWRP because every time I restored or flashed, I was losing my custom recovery.
From 6T (purchased from oneplus.com), any time I follow the instructions for how to flash one of the custom ROMs, I get stuck at the bootloader with no working rom.
I was able to use the MSMTool to restore to 9.0.13. I upgraded a few times flashing OnePlus6TOxygen_34_OTA_024_all_1909112343_9fd6e0057b8747dc, which works, but when I try to flash a custom ROM, I cannot get past the bootloader. I say a few times because I've tried this for a few days now with no success.
Most recently, I used the Flash-all.bat inside 10.3.0-OnePlus6TOxygen_34_OTA_042_all_1912142031_d9ef3-FASTBOOT
I am currently on 10.3.0, with twrp-3.3.1-31-fajita-Q-mauronofrio installed using the fastboot flash boot_a twrp-3.3.1-31-fajita-Q-mauronofrio.img then fastboot boottwrp-3.3.1-31-fajita-Q-mauronofrio.img commands from fastboot.
I can then install Magisk 19.4 or 20.3, however again when I try to flash a custom ROM, I cannot get past the bootloader.
What am I doing wrong?
When you 'fastboot boot' twrp, you can't flash twrp as .img file after that..... (There is no recovery partition on our phone, only a boot one)
If you flash a twrp img it will overwrite boot partition with only twrp and no kernel... Basic knowledge. Once temporarily booted in twrp by 'fastboot boot' command you must flash the installer, meaning the .zip file.
Then reboot your phone in twrp and flash whatever you want
Always latest versions of Magisk, why flashing a deprecated 19.4?
Striatum_bdr said:
When you 'fastboot boot' twrp, you can't flash twrp as .img file after that..... (There is no recovery partition on our phone, only a boot one)
If you flash a twrp img it will overwrite boot partition with only twrp and no kernel... Basic knowledge. Once temporarily booted in twrp by 'fastboot boot' command you must flash the installer, meaning the .zip file.
Then reboot your phone in twrp and flash whatever you want
Always latest versions of Magisk, why flashing a deprecated 19.4?
Click to expand...
Click to collapse
I was having an issue with the boot command in 10.3.0, which is how I found the flash command, and using both of those seemed to work (at least get me into twrp).
Now I am able to just run fastboot boot twrp-3.3.1-31-fajita-Q-mauronofrio.img and it works.
I was using 19.4 because somewhere in here someone mention twrp not working with magisk 20.3.
I've had no issues with 20.3 and twrp, so I will continue to use 20.3
The steps I use to flash a custom ROM (after twrp is installed)
1. remove the lock screen security from the existing ROM
2. boot straight into recovery from the existing ROM
3. wipe Data, Cache, and Dalvik by swiping right to factory reset from the wipe menu
4. flash the ROM from internal storage using the Install button
at this point I've tried a couple of approaches including a reboot here to see if the ROM flashed, and also installing twrp right after flashing ROM so that I will have a working twrp install.
Either way, I can never get past the bootloader.
Am I performing these steps correctly?
s7itch3s said:
I was having an issue with the boot command in 10.3.0, which is how I found the flash command, and using both of those seemed to work (at least get me into twrp).
Now I am able to just run fastboot boot twrp-3.3.1-31-fajita-Q-mauronofrio.img and it works.
I was using 19.4 because somewhere in here someone mention twrp not working with magisk 20.3.
I've had no issues with 20.3 and twrp, so I will continue to use 20.3
The steps I use to flash a custom ROM (after twrp is installed)
1. remove the lock screen security from the existing ROM
2. boot straight into recovery from the existing ROM
3. wipe Data, Cache, and Dalvik by swiping right to factory reset from the wipe menu
4. flash the ROM from internal storage using the Install button
at this point I've tried a couple of approaches including a reboot here to see if the ROM flashed, and also installing twrp right after flashing ROM so that I will have a working twrp install.
Either way, I can never get past the bootloader.
Am I performing these steps correctly?
Click to expand...
Click to collapse
I don't know I don't flash custom ROMs anymore, too old for that stuff and need my time for me.
There are specific instructions for each custom ROM it's better to ask in dedicated threads, some of them need to have OOS in both slots before, some of them need to be fleshed in both slots. Normally you eventually wipe things, flash the ROM and twrp to keep it, then reboot to twrp (necessary to boot on the slot where the ROM is actually fleshed, which is always the non active slot, which become the new active slot) and flash Gapps and Magisk ( because Gapps and Magisk can be flashed only in active slot) then reboot system
s7itch3s said:
Am I performing these steps correctly?
Click to expand...
Click to collapse
I've updated these instructions here, they are the same, just added to them really.
This is how I install Lineage 17. (If you are doing 16, replace 10.3.0 with 9.0.17, and the Q image of TWRP with the Pie image)
- Install 10.3.0 fastboot ROM again to start over, boot it once. Just to make sure everything is good.
- Reboot to fastboot.
- Boot the Q image of TWRP.
- Run the TWRP installer, reboot to recovery
- You backed everything up right?
- Factory reset (This is the slider at the bottom in the wipe menu).
- Format data. (This is the button that says Format data in the wipe menu)
- Do NOT wipe cache, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else, Just Factory Reset and Format Data. After doing those two Reboot to Recovery one more time. You must do this after formatting data.
- Now transfer Lineage and TWRP to your phone, Windows / Linux should see TWRP fine as a media device when plugged in.
- Install Lineage
- Run the TWRP Installer.
- Reboot to Recovery.
- Install Lineage (You need Lineage on both slots, so yes run it again)
- Run the TWRP Installer (yes again).
- Reboot to Recovery.
- Install Gapps if you want them.
- Install Magisk 20.3 if you use Magisk. I used 20.3 it works fine. (20.4 also fine) Do not install modules or other add ons at this point. Boot once and go through the setup and everything, then install your add-ons.
- Be aware the phone will restart once, then Lineage will start up and all will be good.
From that point on updating should just be like normal :
- Reboot to recovery
- Flash Lineage.
- Flash TWRP Installer
- Reboot to Recovery
- Flash Gapps. (Assuming you use them, if you installed them once you must continue to install them or do a clean install)
- Flash Magisk. (If you use it)
- Reboot to system.
- No loss of data, or anything.
- No need to flash anything twice etc.
I've posted similar instructions here. It was just for LOS 16, same thing essentially though.
OhioYJ said:
I've updated these instructions here, they are the same, just added to them really.
This is how I install Lineage 17. (If you are doing 16, replace 10.3.0 with 9.0.17, and the Q image of TWRP with the Pie image)
- Install 10.3.0 fastboot ROM again to start over, boot it once. Just to make sure everything is good.
- Reboot to fastboot.
- Boot the Q image of TWRP.
- Run the TWRP installer, reboot to recovery
- You backed everything up right?
- Factory reset (This is the slider at the bottom in the wipe menu).
- Format data. (This is the button that says Format data in the wipe menu)
- Do NOT wipe cache, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else, Just Factory Reset and Format Data. After doing those two Reboot to Recovery one more time. You must do this after formatting data.
- Now transfer Lineage and TWRP to your phone, Windows / Linux should see TWRP fine as a media device when plugged in.
- Install Lineage
- Run the TWRP Installer.
- Reboot to Recovery.
- Install Lineage (You need Lineage on both slots, so yes run it again)
- Run the TWRP Installer (yes again).
- Reboot to Recovery.
- Install Gapps if you want them.
- Install Magisk 20.3 if you use Magisk. I used 20.3 it works fine. (20.4 also fine) Do not install modules or other add ons at this point. Boot once and go through the setup and everything, then install your add-ons.
- Be aware the phone will restart once, then Lineage will start up and all will be good.
From that point on updating should just be like normal :
- Reboot to recovery
- Flash Lineage.
- Flash TWRP Installer
- Reboot to Recovery
- Flash Gapps. (Assuming you use them, if you installed them once you must continue to install them or do a clean install)
- Flash Magisk. (If you use it)
- Reboot to system.
- No loss of data, or anything.
- No need to flash anything twice etc.
I've posted similar instructions here. It was just for LOS 16, same thing essentially though.
Click to expand...
Click to collapse
Sir, apology for being an old noob, I am on OOS 10.3.2 TWRP 3.3.1-32 can I follow the above guide? If Yes,
Why aren't we using the "Lineage Recovery" provided in "Lineage OS Downloads" page?? If we use it, will the above instructions change ? What are the cons of using it?
Sorry again for asking!! Can you please share me the Link to Open Gapps which Will be suitable in my scenario ?
Advised Sloth said:
Sir, apology for being an old noob, I am on OOS 10.3.2 TWRP 3.3.1-32 can I follow the above guide? If Yes,
Why aren't we using the "Lineage Recovery" provided in "Lineage OS Downloads" page?? If we use it, will the above instructions change ? What are the cons of using it?
Sorry again for asking!! Can you please share me the Link to Open Gapps which Will be suitable in my scenario ?
Click to expand...
Click to collapse
Historically Lineage / CM recovery was hit or miss, or TWRP or other recoverys worked better. To be fair I haven't even tried the Lineage recovery. So maybe that is no longer true? Right now, I know TWRP works. The updated instructions link up there has links in it, FYI, link OpenGapps. OpenGapps can be found here. You will be using Arm64, Android 10 obviously.
Since you are already on 10.3.2 (I assume you were on 10.3.1 before) you should be good to skip the step about fastboot ROM or install OOS, and you already have TWRP., so you should be able to go right on to backing everything up, wiping everything, and installing Lineage. (So you can skip the first few steps)
Anymore questions feel free to ask.
OhioYJ said:
Historically Lineage / CM recovery was hit or miss, or TWRP or other recoverys worked better. To be fair I haven't even tried the Lineage recovery. So maybe that is no longer true? Right now, I know TWRP works. The updated instructions link up there has links in it, FYI, link OpenGapps. OpenGapps can be found here. You will be using Arm64, Android 10 obviously.
Since you are already on 10.3.2 (I assume you were on 10.3.1 before) you should be good to skip the step about fastboot ROM or install OOS, and you already have TWRP., so you should be able to go right on to backing everything up, wiping everything, and installing Lineage. (So you can skip the first few steps)
Anymore questions feel free to ask.
Click to expand...
Click to collapse
First of all, thank you very much for your time and explanation.
Sir, so i will proceed as follows:
* Boot into TWRP Recovery
* Perform "swipe to factory reset" & "swipe to wipe data"
* Reboot to TWRP recovery again
* Flash LOS 17.1 on slot A
* Reboot to TWRP recovery again
* Flash LOS 17.1 on slot B
* Reboot to system
Sir, please check are my steps correct? If not,
From which step( steps mentioned in your guide) should i start?
Last query is, which GApps zip will be best for me, micro/nano/pico/tv stock, If i want max coverage of google?
Very sorry for knocking you repeatedly!!!
Advised Sloth said:
First of all, thank you very much for your time and explanation.
Last query is, which GApps zip will be best for me, micro/nano/pico/tv stock, If i want max coverage of google?
Click to expand...
Click to collapse
Your starting point is correct. However make sure you don't miss the re-install TWRP after flashing Lineage each time, and the second time you need to flash Gapps before you reboot to system.
Personally I always do Nano. Anything else you need (that would be included in Micro) can be installed from the Play store. Nano at least includes all the things that can't be installed from the play store.
Pico has the least in it. TV is for TV devices. On OpenGapps there is a box next to each package you can click and it will tell you exactly what is in each package.
OhioYJ said:
I've updated these instructions here, they are the same, just added to them really.
This is how I install Lineage 17. (If you are doing 16, replace 10.3.0 with 9.0.17, and the Q image of TWRP with the Pie image)
- Install 10.3.0 fastboot ROM again to start over, boot it once. Just to make sure everything is good.
- Reboot to fastboot.
- Boot the Q image of TWRP.
- Run the TWRP installer, reboot to recovery
- You backed everything up right?
- Factory reset (This is the slider at the bottom in the wipe menu).
- Format data. (This is the button that says Format data in the wipe menu)
- Do NOT wipe cache, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else, Just Factory Reset and Format Data. After doing those two Reboot to Recovery one more time. You must do this after formatting data.
- Now transfer Lineage and TWRP to your phone, Windows / Linux should see TWRP fine as a media device when plugged in.
- Install Lineage
- Run the TWRP Installer.
- Reboot to Recovery.
- Install Lineage (You need Lineage on both slots, so yes run it again)
- Run the TWRP Installer (yes again).
- Reboot to Recovery.
- Install Gapps if you want them.
- Install Magisk 20.3 if you use Magisk. I used 20.3 it works fine. (20.4 also fine) Do not install modules or other add ons at this point. Boot once and go through the setup and everything, then install your add-ons.
- Be aware the phone will restart once, then Lineage will start up and all will be good.
From that point on updating should just be like normal :
- Reboot to recovery
- Flash Lineage.
- Flash TWRP Installer
- Reboot to Recovery
- Flash Gapps. (Assuming you use them, if you installed them once you must continue to install them or do a clean install)
- Flash Magisk. (If you use it)
- Reboot to system.
- No loss of data, or anything.
- No need to flash anything twice etc.
I've posted similar instructions here. It was just for LOS 16, same thing essentially though.
Click to expand...
Click to collapse
Sorry for the necropost, but this also works for TWRP 3.6 and Lineage 18.1. I initially had a problem with the default TWRP for my 6t. During the initial TWRP fastboot the version on their site caused a firmware error which I could just barely get out of, but it screwed up the system boot process in some subtle way that even the fixed version of TWRP (found on this site) couldn't solve.
After trying your instructions above, it didn't work the first time because of the screwed up system boot. It just kept trying to boot to recovery. I suspected a firmware error and was almost going to do an mcmdownload soft-brick rescue. I tried one last thing, using the TWRP on the system to sideload the stock ROM. That worked and patched up the system boot process. Once I booted and ran through some basic initialization to make sure developer options were properly set I followed the above instructions and it worked nearly flawlessly.
One strange thing. After I installed Lineage 18.1 and TWRP to both partitions (as well as Gapps / magisk), it rebooted to system and almost booted without incident -- except a large circular logo popped up that said 100% and stopped. I figured that that meant someting completed properly, so I powered off, waited 10 seconds, powered on and then the Lineage green system initialization spinner came up for a few minutes and it went through the user initialization sequence.
Thanks. I almost gave up and bought a new phone.
OhioYJ said:
I've updated these instructions here, they are the same, just added to them really.
This is how I install Lineage 17. (If you are doing 16, replace 10.3.0 with 9.0.17, and the Q image of TWRP with the Pie image)
- Install 10.3.0 fastboot ROM again to start over, boot it once. Just to make sure everything is good.
- Reboot to fastboot.
- Boot the Q image of TWRP.
- Run the TWRP installer, reboot to recovery
- You backed everything up right?
- Factory reset (This is the slider at the bottom in the wipe menu).
- Format data. (This is the button that says Format data in the wipe menu)
- Do NOT wipe cache, do not Wipe system, do NOT Wipe Dalvik / ART, do not add anything else, Just Factory Reset and Format Data. After doing those two Reboot to Recovery one more time. You must do this after formatting data.
- Now transfer Lineage and TWRP to your phone, Windows / Linux should see TWRP fine as a media device when plugged in.
- Install Lineage
- Run the TWRP Installer.
- Reboot to Recovery.
- Install Lineage (You need Lineage on both slots, so yes run it again)
- Run the TWRP Installer (yes again).
- Reboot to Recovery.
- Install Gapps if you want them.
- Install Magisk 20.3 if you use Magisk. I used 20.3 it works fine. (20.4 also fine) Do not install modules or other add ons at this point. Boot once and go through the setup and everything, then install your add-ons.
- Be aware the phone will restart once, then Lineage will start up and all will be good.
From that point on updating should just be like normal :
- Reboot to recovery
- Flash Lineage.
- Flash TWRP Installer
- Reboot to Recovery
- Flash Gapps. (Assuming you use them, if you installed them once you must continue to install them or do a clean install)
- Flash Magisk. (If you use it)
- Reboot to system.
- No loss of data, or anything.
- No need to flash anything twice etc.
I've posted similar instructions here. It was just for LOS 16, same thing essentially though.
Click to expand...
Click to collapse
OhioYJ, these are great instructions but it initially left me with questions about how that procedures would create duplicate installs on slot A and B. The answer is of course that the Lineage installer for the 6t knows about the dual slot setup and always writes to the inactive slot. Booting into recovery activates the inactive slot so that installing again after that installs to the other slot and now you have Lineage on both slots. The installer for TWRP always installs to both slots and is needed because Lineage always installs its recovery handler and you don't want that so you overwrite.
PS: TWRP has an option for installing itself after installing the requested package. Would that be just as good as installing the TWRP zip?
PPS: I had to do an 'adb push' of the Lineage and TWRP zips to sdcard for the installs. Unfortunately installing and slot switching makes the sdcard unavailable so you have to push the zips again. Is there somewhere I can write them to that I don't lose access to after a boot to recovery?
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