Related
Hello dear XDA community, if you haven't seen already, PA aka Paranoid Android is back!
More information: https://www.xda-developers.com/para...-2-builds-pie-controls-color-engine-and-more/
You can download it here: http://get.aospa.co/official/sailfish
Hope yall enjoy the PA godess! If you have tried it out, you may tell us how it went for you and how things are going.
Kind regards and happy flashing :highfive:
What would the proper sequence of steps be to flash this? I'm currently running Pixeldusts latest with April BL and TWRP rc1
Edit: nevermind I am an idiot
I may be wrong but I thought we weren't able to flash gapps on the pixel? Also, what build is this based on?
Error!
Just tried flashing. On April bootloader. Got an error message:
"Could not find the 'META/INF/com/google/android/update-binary' in the zip file"
Oh, well.
Oops - error was because I was trying to install from TWRP that was using fastboot! Once I flashed TWRP, installation was perfect!
pavanmaverick said:
Just tried flashing. On April bootloader. Got an error message:
"Could not find the 'META/INF/com/google/android/update-binary' in the zip file"
Oh, well.
Click to expand...
Click to collapse
I got it to boot but the beans GApps I had wouldn't let me back up from the cloud upon setup and a few other things are kinda buggy so I went back to PN
deleted to wrong method
inyourname said:
1. go to fastboot mode and boot twrp rc1
2. flash data, system, cache
3. install rom
4. reboot to system
5. turn off your phone, go to fastboot mode and boot twrp rc1 again
6. flash twrp rc2 -> bootsigner
7. reboot to twrp
8. install beansgapps
9. reboot to system
follow this instruction and it will works perfect!
Click to expand...
Click to collapse
Were you able to restore apps via Google backup?
crossen0 said:
Were you able to restore apps via Google backup?
Click to expand...
Click to collapse
i tried after writing the instruction but nothing works either. even i cannot even boot to the lockscreen properly. my bad
follow this method and it works but not working google backup setup, so you should install apps and backup settings manually
1. go to fastboot mode and boot twrp rc1
2. flash data, system, cache
3. install rom
4. reboot to system and unlock the lockscreen (it means swipe the lockscreen)
5. turn off your phone, go to fastboot mode and boot twrp rc1 again
6. flash twrp rc2 -> bootsigner
7. reboot to twrp
8. install beansgapps
9. reboot to system
i hope it helps
It says 0 downloads on the site linked above. Weird or am I just "paranoid"??
ragzz03 said:
It says 0 downloads on the site linked above. Weird or am I just "paranoid"??
Click to expand...
Click to collapse
On their google+ official forum they said they're having issues with their own serves, there is an official mirror if you check
Working so far....
I'm on the April Bootloader, and this ROM is working like a charm so far. My steps:
1. Install TWRP, boot into Recovery
2. Wipe
3. Install PA ROM
4. Reboot into System, and then boot into Fastboot
5. Reinstall TWRP, boot into Recovery
6. Install Open GApps (Nano package)
7. Reboot into System
8. Boot into TWRP
9. Install SuperSU
10. Reboot into System
11. Used Titanium Backup to reinstall apps and data
With this method, everything seems to work. I guess if you are on May bootloader you will need to reflash the boot signer after each step involving flashing sometime from TWRP?
pavanmaverick said:
I'm on the April Bootloader, and this ROM is working like a charm so far. My steps:
1. Install TWRP, boot into Recovery
2. Wipe
3. Install PA ROM
4. Reboot into System, and then boot into Fastboot
5. Reinstall TWRP, boot into Recovery
6. Install Open GApps (Nano package)
7. Reboot into System
8. Boot into TWRP
9. Install SuperSU
10. Reboot into System
11. Used Titanium Backup to reinstall apps and data
With this method, everything seems to work. I guess if you are on May bootloader you will need to reflash the boot signer after each step involving flashing sometime from TWRP?
Click to expand...
Click to collapse
Does this have all the navbar and status bar mods?
And does setup wizard cloud backup work with the nano GApps? I tried full and it would only allow phone to phone back up.
S8ntsHaz3 said:
And does setup wizard cloud backup work with the nano GApps? I tried full and it would only allow phone to phone back up.
Click to expand...
Click to collapse
Don't know - I use Titanium, and not the cloud backup. Sorry.
---------- Post added at 10:42 AM ---------- Previous post was at 10:41 AM ----------
drocny87 said:
Does this have all the navbar and status bar mods?
Click to expand...
Click to collapse
Not sure which mods you're referring to. It has immersive mode, and Pie controls.
All good thanks
S8ntsHaz3 said:
And does setup wizard cloud backup work with the nano GApps? I tried full and it would only allow phone to phone back up.
Click to expand...
Click to collapse
if you boot the phone after follows that instruction and flash nano gapps,
Hello screen - wifi setting - connect pixel<->other phone(mine was nexus5) - then the screen said you must use other way to restore back up - select cloud backup - email and password - restore backup
In that case you can restore your apps and backup settings from cloud backup cause i tried and works perfect.
i tried everything to restore cloud backup without connecting other phone but cannot found any ideas.
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
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?
Hey all,
Phone is new to me, t-mo version. Did the international conversion, unlocked the bootloader, installed TWRP 3.3.1.1.img. All with minimal issues. Installed the 20200121 nightly of LOS successfully, but it powered off a few minutes after getting through the setup menu. Bootlooped. I may have gotten it out of the bootloop with the vol up+down trick from the msmdownloadtool trick, or something, cause I got the screen to turn off and left it for the night.
Tonight, the phone was totally dead, but I was able to start over with the (patched) msmtool I used initially. All good. Went through the same steps and got TWRP and LOS installed. This time I used last nights nightly 20200123. All set for a minute, before it bootlooped again.
Here's some details that might be useful:
The phone powered off after unplugging it. This is when the bootloop started, I can't be sure it was after dissconnecting each time, but at least the last time. The battery was >80%. I also managed to get it to boot into LOS after the most recent bootloop, for a few minutes, and it powered off without being connected or disconnected. So probably not related.
I did a system wipe, along with the format, as recommended in the LOS installation steps from them
The system wipe maybe wasn't a good idea??
I tried to sideload LOS.zip, which seemed to work fine according to my terminal, but it warned me that I had no OS installed when I went to reboot. So I adb pushed LOS and installed. I got the same no OS warning, but rebooted anyway this time. LOS started up fine, for a few minutes, before powering off and then looping.
Could I have 2 instances conflicting??
Nothing else installed yet, not root, magisk, or anything yet.
I shut it down this time with a vol up + power, which worked. I'm done for tonight, but I would appreciate any ideas on what may be causing this so I can give it a third go tomorrow.
Thanks!
try this
BeansBeanson said:
Hey all,
Phone is new to me, t-mo version. Did the international conversion, unlocked the bootloader, installed TWRP 3.3.1.1.img. All with minimal issues. Installed the 20200121 nightly of LOS successfully, but it powered off a few minutes after getting through the setup menu. Bootlooped. I may have gotten it out of the bootloop with the vol up+down trick from the msmdownloadtool trick, or something, cause I got the screen to turn off and left it for the night.
Tonight, the phone was totally dead, but I was able to start over with the (patched) msmtool I used initially. All good. Went through the same steps and got TWRP and LOS installed. This time I used last nights nightly 20200123. All set for a minute, before it bootlooped again.
Here's some details that might be useful:
The phone powered off after unplugging it. This is when the bootloop started, I can't be sure it was after dissconnecting each time, but at least the last time. The battery was >80%. I also managed to get it to boot into LOS after the most recent bootloop, for a few minutes, and it powered off without being connected or disconnected. So probably not related.
I did a system wipe, along with the format, as recommended in the LOS installation steps from them
The system wipe maybe wasn't a good idea??
I tried to sideload LOS.zip, which seemed to work fine according to my terminal, but it warned me that I had no OS installed when I went to reboot. So I adb pushed LOS and installed. I got the same no OS warning, but rebooted anyway this time. LOS started up fine, for a few minutes, before powering off and then looping.
Could I have 2 instances conflicting??
Nothing else installed yet, not root, magisk, or anything yet.
I shut it down this time with a vol up + power, which worked. I'm done for tonight, but I would appreciate any ideas on what may be causing this so I can give it a third go tomorrow.
Thanks!
Click to expand...
Click to collapse
(BASE STOCK ROM)
OnePlus6TOxygen_41_OTA_063_all_2001032024_215eea3f e7c64e37.zip (BETA4)
whatever the rom requires(10.3.0) however the Q beta 4 works just fine, havent found any real bugs / newer security patches etc.
(CUSTOM ROM)
Latest rom that will work with BASE and TWRP decryption
(latest TWRP )
twrp 3.3.1-31 zip
(Latest)
Magisk Canary . Zip
(Latest)
open_gapps - Q
(Latest)
custom compatible kernel
(Latest)
NanoDroid - with con/fig read alter installation notes
(&)
India_Fake_Partition_Deleter
------------------- EASY-CLEAN-INSTALL (LONG BUT BULLETPROOF) -------------------
!(BACK UP STORAGE / U WILL LOSE DATA ETC.
ALL FILES ABOVE CAN BE SUBSTITUTED FOR ANY "IDEAL" ROM SETUP
CONFIGURATIONS YOU MAY PREFER., THESE ARE MYNE)!
------------------------------------------------------------------------------------------------
You only need any custom rom with the required BASE STOCK ROM and compatible TWRP version to decrypt storage, and of course, the latest magisk.
------------------------------------------------------------------------------------------------
From dirty or clean system - to - clean flash
in cmd type
fastboot boot twrp.img
Install twrp installer.
Mount all partitions / wipe / advanced / check all boxes & wipe all / format.
- - Reboot twrp - -
Mount all partitions / wipe / advanced / check all boxes & wipe all / format.
Reboot twrp
(DONT BE MOUNTING OR UNMOUNTING ANYTHING MANUALY ANYMORE!)
install OOS(BETA4).zip / TWRP installer
- - reboot recovery - -
install OOS(BETA4).zip / TWRP installer
- - reboot to recovery - -
Copy -
Magisk , TWRP & ROM to internal storage.
Format Data
Flash ROM
Flash TWRP installer
Reboot to recovery
Wipe Dalvik/ART Cache
Wipe Data
Flash Magisk.
Reboot system with your device unplugged to be safe (Device may reboot a couple times)
- - reboot to recovery - -
Copy -
Magisk , TWRP & ROM to internal storage.
Flash ROM
Flash TWRP installer
- - reboot to recovery - -
Flash Magisk
BOOT UP System
- - reboot back to recovery - -
Choose Reboot Option / (CHANGE YOUR SLOT) / Back / Reboot Recovery
Flash Magisk.
Reboot system
SETUP ROM
/////////////////////////////////////\OPTIONAL/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
- - REBOOT TO RECOVERY - -
----------------------------------------------------------------------------------------------------
STEP *( .=./ )*
Flash GAPPS
Flash India_Fake_Partition_Deleter
Flash NanoDroid (With prefered pre-configured setup/overlay/apps files placed)
Flash Custom Kernel
Re-Flash Magisk again
Click - WIPE DALVIK & Reboot system right after
------------------------------------------------------------------------------------------------------
- - REBOOT TO RECOVERY - -
Choose Reboot (CHANGE YOUR SLOT TO THE OPPOSITE SLOT)
- - REBOOT BACK TO RECOVERY - -
REPEAT STEP " *( .=./ )* "
-------------------------------------------------------------------------------------------------
GAME OVER
1up
THIS is EXTENSIVE but will work for any particular rom setup for a/b devices based on Q
---------- Post added at 10:50 PM ---------- Previous post was at 10:47 PM ----------
just follow install guide download latest linageos and gapps from open gapps. and latest magisk and after flash gapps if you cannot sign into a google account then you need to factory reset both slot in system settings menu and then just reinstall magisk and kernel settings modules etc
---------- Post added at 10:52 PM ---------- Previous post was at 10:50 PM ----------
just switch slots in cmd or via twrp and reboot system and factory reset wipe all via the settings in the booted system, not twrp
I'm a little slow..
I got the phone back to factory with the msmtool, so I'm ready to do this! I get the general idea, but for a few of these, can you ELI5. Thanks so much for taking the time to help me out.
------------------- EASY-CLEAN-INSTALL (LONG BUT BULLETPROOF) -------------------
!(BACK UP STORAGE / U WILL LOSE DATA ETC.
ALL FILES ABOVE CAN BE SUBSTITUTED FOR ANY "IDEAL" ROM SETUP
CONFIGURATIONS YOU MAY PREFER., THESE ARE MYNE)!
------------------------------------------------------------------------------------------------
You only need any custom rom with the required BASE STOCK ROM and compatible TWRP version to decrypt storage, and of course, the latest magisk.
------------------------------------------------------------------------------------------------
From dirty or clean system - to - clean flash
in cmd type
fastboot boot twrp.img
Install twrp installer. Do I just find the zip in the file structure in twrp and install? I'm at this step in twrp and I don't see how to install it. Previously I had `adb push twrp.img /storage/` so that I had a file I could find and install. If it's already there just from `fastboot boot twrp.img`, I can't seem to find it.
--solved this by pushing the twrp-intaller.zip to /storage, and then installing. It did the expected installation to both a/b
Mount all partitions / wipe / advanced / check all boxes & wipe all / format.
- - Reboot twrp - -
I went to `mount` and checked all the boxes. Then went back to `wipe advanced` and checked all those boxes. Now I'm stuck at the fastboot screen and can't boot or start. :crying:
I can't do a `fastboot boot twrp.img either. Any suggestions before I blow it away with the msmtool again??????
Mount all partitions / wipe / advanced / check all boxes & wipe all / format.
Reboot twrp
(DONT BE MOUNTING OR UNMOUNTING ANYTHING MANUALY ANYMORE!) How was I doing it wrong? Or do you mean that these steps just now are the only mounting that should be done?
install OOS(BETA4).zip / TWRP installer What command should I use to move it from my pc to the phone? `adb push .zip storage` ?
- - reboot recovery - -
install OOS(BETA4).zip / TWRP installer Do it twice, exactly the same? Is this so it's on both slots?
- - reboot to recovery - -
Copy -
Magisk , TWRP & ROM to internal storage. What command should I use for copying? Like above `adb push <files> storage`?
Format Data
Flash ROM
Flash TWRP installer
Reboot to recovery
Wipe Dalvik/ART Cache
Wipe Data
Flash Magisk.
Reboot system with your device unplugged to be safe (Device may reboot a couple times)
- - reboot to recovery - -
Copy -
Magisk , TWRP & ROM to internal storage.
Flash ROM
[/COLOR]just follow install guide download latest linageos and gapps from open gapps. and latest magisk and after flash gapps if you cannot sign into a google account then you need to factory reset both slot in system settings menu and then just reinstall magisk and kernel settings modules etc
---------- Post added at 10:52 PM ---------- Previous post was at 10:50 PM ----------
just switch slots in cmd or via twrp and reboot system and factory reset wipe all via the settings in the booted system, not twrp
Not sure what you mean by this part here. I wasn't planning on installing gapps. I'm confused about the reseting both slots. Is the idea that I did the install twice above, so that it's on both a/b slots and I'd have to reset both if there's a problem?
Click to expand...
Click to collapse
The title says it all, i have been using a custom ROM (Havoc OS) and the LolZ kernel with magisk, it works perfectly but as soon as i restart the system. it bootloops and i have to keep restoring, re installing and so on until it finally works.
Does anyone have an idea of what might be going on?
device: Samsung Galaxy Note 3 SM-N9005 hlte
Even more info incase you need it:
Steps to create problem for me:
Install Havoc OS
Install LolZ kernel
Install Magisk
Boot and use
Restart
(problem comes)
Steps to fix (Before):
Install Havoc OS
Get rid of remainders of magisk for lolz kernel
Install LolZ kernel
Install Magisk
Restore Data partition
Reboot to System
Right now nothing is working, ill try another way and update this
also, i noticed that instead of storage being in
/storage/emulated/0
its now in
/sdcard
according to twrp
Ok this should be the actuall way excluding ALL ways:
1. Reboot to cause the issue lol
2. Go to recovery (twrp recommended)
3. repair the system partition and data partition.
4. Shut down then connect to cable.
5. Let it boot, if it dosent boot to kernel and goes to recovery, try reformatting, 6. restoring, dont touch what you dont want lost etc then start from step 3 (If it goes to charging anim, ignore this step)
6. Let the charge animation play
7. after the screen turns off / you know the charging animation played
8. Boot via power button
9. Works!
Now i really feel a tiny bit better when rebooting my phone XD
If it bootloops after step 8, try reformatting, wiping, repairing, restoring etc-