Database Info

TWRP infinitely installs a ROM

I didn't know where to post this so i am posting it here.
I tried to flash the latest version of CrDroid some hours ago and although the installation began with no errors, the whole thing got stuck on an infinite installation of the ROM. The log displayed "Patching system image unconditionaly."
After about 30 minutes i just lost faith and held down power button to force a reboot. Then, TWRP got reset to the screen which you see when you first flash TWRP, the one ascing about wether to keep system read only or not.
I will post screenshots too as soon as i figure out how to do it
.

Set it back to RW mode from RO mode. If it constantly turns back to RO, try reflashing the recovery image.
If you are lucky enough to abruptly abort a ROM installation, you will be able to atleast use the device. I had aborted a nandroid restore and my entire data partition was corrupted.
In any case you should post it in the appropriate ROM thread.

Make sure system is mounted writable, wipe system, data, and caches, and flash... it's that simple. If it fails use another ROM.
BTW, it is usually useful to tell which device (specifically), what ROM/Gapps, what version of TWRP, etc... the devil is usually in the details, the more the better.

Yeah i forgot about that, im new here. So, its the latest version of TWRP and the ROM was the latest version of crDroid (April 17th). Anyways, me being extremely stubborn as usual, I tried flashing the ROM through FlashFire and the problem is still there. By the way I did mount everything and it doesnt get better. I dont care anyways i'll just return to some other Nougat ROM. Thanks for replying though!

mike.... said:
Yeah i forgot about that, im new here. So, its the latest version of TWRP and the ROM was the latest version of crDroid (April 17th). Anyways, me being extremely stubborn as usual, I tried flashing the ROM through FlashFire and the problem is still there. By the way I did mount everything and it doesnt get better. I dont care anyways i'll just return to some other Nougat ROM. Thanks for replying though!
Click to expand...
Click to collapse
Weird... We can pretty much guarantee nothing is working in TWRP though, or at least it's not processing even the boot image of your ROM or the device wouldn't boot.
What is bootloader status?

OnePlus One - Won't boot RR , boot loop happens

Hi!
A while back I had some issues with the phone, it was when I was supposed to boot it, it always took 2 tries. It always got stuck, then had to long press the lock key to hard reboot it, then it worked fine. This prevented me from doing a factory reset (in hope to fix (what I later found out was) a media rescan etc). Tried to root it, something happened and it wouldn't boot anymore. Yiti yata and the phone wouldn't boot. Finally I got it back to life with some guide on here and I used whatever 4.4.4 I downloaded.
The software wouldn't find any "normal" update phone updates, so I figured I would try Resurrection Remix 7.1.x (.2 I think it was). At first I got just that it failed with some 2.x twrp version. Updated to TWRP 3.1.x.x (3.1.1.0 if I guess). Now I got to know that it was a TZ error (ERROR 7) from TWRP. This happened to my "RR-N-v5.8.3-20170718-bacon-Official.zip" file. I managed to get around it by doing this: https://forum.xda-developers.com/showthread.php?t=2522762. So I could get this installed, sort of I think. The problem now was that it would show the very first oneplus boot screen for around 20 ish seconds, before it would reboot in a boot loop.
So I tried to install some other CM Lineage Os nightly thing (they said install that and then RR), but that didn't work either. This post was the one I donwloaded from (install this first, then RR should work).
I tried doing this both on TWRP 2.8.6.0 and 3.1.1.0 since I saw some post about the modem not being right from versions newer than 2.8.6.0.
Looking around a bit more I saw in some post someone talking about firmware..? Does this matter anything, also how is this different from the recovery or ROM? (new to this stuff)
In short, last working version of Android I had on there was 4.4.4 (think I followed this post). Using a Mac currently and have no problem with flashing, entering fastboot or recovery.
My procedure when I tried to install RR was:
Install the TWRP 3.1.1.0 or 2.8.6.0 (since I did it several times).
Wipe everything (Have nothing of value on the phone) cache, system, internal storage, dalvik and data. Also did a factory reset (from TWRP) before if that matters.
Copied RR and Gapps 7.1 ARM (not arm64) over.
Installed RR, wiped cache/dalvik. (or linear/cm (post above^^) when I tried that)
Installed Gapps, wiped cache/dalvik.
Boot loop.
Also tried with/without emptying cache/dalvik also chose to install both zips at once.
So can anyone clue in how I can proceed to get RR 7.1 onto my OPO? Any help is very much appreciated
I'm sorry if this wasn't the best post. Have an immense headache at the moment

wahlmat said:
Hi!
A while back I had some issues with the phone, it was when I was supposed to boot it, it always took 2 tries. It always got stuck, then had to long press the lock key to hard reboot it, then it worked fine. This prevented me from doing a factory reset (in hope to fix (what I later found out was) a media rescan etc). Tried to root it, something happened and it wouldn't boot anymore. Yiti yata and the phone wouldn't boot. Finally I got it back to life with some guide on here and I used whatever 4.4.4 I downloaded.
The software wouldn't find any "normal" update phone updates, so I figured I would try Resurrection Remix 7.1.x (.2 I think it was). At first I got just that it failed with some 2.x twrp version. Updated to TWRP 3.1.x.x (3.1.1.0 if I guess). Now I got to know that it was a TZ error (ERROR 7) from TWRP. This happened to my "RR-N-v5.8.3-20170718-bacon-Official.zip" file. I managed to get around it by doing this: https://forum.xda-developers.com/showthread.php?t=2522762. So I could get this installed, sort of I think. The problem now was that it would show the very first oneplus boot screen for around 20 ish seconds, before it would reboot in a boot loop.
So I tried to install some other CM Lineage Os nightly thing (they said install that and then RR), but that didn't work either. This post was the one I donwloaded from (install this first, then RR should work).
I tried doing this both on TWRP 2.8.6.0 and 3.1.1.0 since I saw some post about the modem not being right from versions newer than 2.8.6.0.
Looking around a bit more I saw in some post someone talking about firmware..? Does this matter anything, also how is this different from the recovery or ROM? (new to this stuff)
In short, last working version of Android I had on there was 4.4.4 (think I followed this post). Using a Mac currently and have no problem with flashing, entering fastboot or recovery.
My procedure when I tried to install RR was:
Install the TWRP 3.1.1.0 or 2.8.6.0 (since I did it several times).
Wipe everything (Have nothing of value on the phone) cache, system, internal storage, dalvik and data. Also did a factory reset (from TWRP) before if that matters.
Copied RR and Gapps 7.1 ARM (not arm64) over.
Installed RR, wiped cache/dalvik. (or linear/cm (post above^^) when I tried that)
Installed Gapps, wiped cache/dalvik.
Boot loop.
Also tried with/without emptying cache/dalvik also chose to install both zips at once.
So can anyone clue in how I can proceed to get RR 7.1 onto my OPO? Any help is very much appreciated
I'm sorry if this wasn't the best post. Have an immense headache at the moment
Click to expand...
Click to collapse
Calm down.
You're right about that firmware thing,that is the one causing issue when you're trying to flash RR 5.8.3 over KitKat.
This is because the firmware that kitkat comes with,is old and don't support newer android versions,that's because it is made for KitKat only.
Always use latest Twrp(https://dl.twrp.me/bacon/).
Make sure you don't edit any zip like what you did with the Rom zip earlier(devs don't post non-working zips),I'm sure you've a backup of your non-edited zip,if not,re-download the zip.
Now boot into latest twrp,wipe everything except internal storage.
Firmware: https://drive.google.com/file/d/0BxysuRdzsJeWeW9JbTNwaUJKb1E/view?usp=drivesdk
Flash the above zip,then without wiping anything flash rom zip(unedited) then flash google apps package(opengapps.org)(optional).
Reboot.It should boot fine now.
Good luck!

Mr.Ak said:
Calm down.
You're right about that firmware thing,that is the one causing issue when you're trying to flash RR 5.8.3 over KitKat.
This is because the firmware that kitkat comes with,is old and don't support newer android versions,that's because it is made for KitKat only.
Always use latest Twrp(Can't post links withing 10 posts apparently...).
Make sure you don't edit any zip like what you did with the Rom zip earlier(devs don't post non-working zips),I'm sure you've a backup of your non-edited zip,if not,re-download the zip.
Now boot into latest twrp,wipe everything except internal storage.
Firmware:
Flash the above zip,then without wiping anything flash rom zip(unedited) then flash google apps package(Can't post links withing 10 posts apparently...)(optional).
Reboot.It should boot fine now.
Good luck!
Click to expand...
Click to collapse
Thank you so much! Got it working on 1st try with what you provided! Seems like the firmware thing was the bad guy in this scenario. A little interest, what specifically is the firmware in this case? Either way, rocking RR now and I'm really grateful

wahlmat said:
Thank you so much! Got it working on 1st try with what you provided! Seems like the firmware thing was the bad guy in this scenario. A little interest, what specifically is the firmware in this case? Either way, rocking RR now and I'm really grateful
Click to expand...
Click to collapse
I'm glad you got it up and running.
Here are some FAQs:
What is a Firmware? What is Modem?
- Firmware is the whole package of proprietary partitions of your device, modem itself is a NON-HLOS file responsible for your device's communications over Wi-Fi, Mobile Networks and other such stuff.
So what is the difference between firmware and ROM then?
- Firmware is the responsible partition for IMEIs, the modemst partitions hold your IMEI, persist holds your Mac addresses etc.
ROM is only a combination​ of system.img and boot.img (kernel)
What to restore if I loose my IMEI?
- Both the modemst partitions (IMP: considering you took a backup of them before)
What is the default firmware? (default= firmware which comes with the latest CM/ LineageOS 14.1 weeklies)
- c6-00241

Thanks a lot, once again

Help!
I'm not sure of all the specifics on my oneplus one but I accidentally updated the wrong update from my nightly bacon.. it now is stuck in Boot Loop I can get to the fastboot screen (it gets stuck there too) and I can get to the recovery, etc (but it is not the usual screen with all the folders (it was rooted).. it is now just four options in Cyanogenmod recovery.. none work. I do not want to lose my data :crying: .. Sadly my techy is not available to save me! Please help this untechy Cali Girl! I've googled and researched and its still like a foreign language.. Thank you!!

HisMuse said:
I'm not sure of all the specifics on my oneplus one but I accidentally updated the wrong update from my nightly bacon.. it now is stuck in Boot Loop I can get to the fastboot screen (it gets stuck there too) and I can get to the recovery, etc (but it is not the usual screen with all the folders (it was rooted).. it is now just four options in Cyanogenmod recovery.. none work. I do not want to lose my data :crying: .. Sadly my techy is not available to save me! Please help this untechy Cali Girl! I've googled and researched and its still like a foreign language.. Thank you!!
Click to expand...
Click to collapse
I am not 100% sure, but I would say, boot into fastboot, flash something like TWRP recovery, then you will be able to access the device files from the recovery. Just reflashing the boot shouldn't mess up anything as far as I am concerned. After that (when you've grabbed all the files you want), flash the newest firmware the guy linked above and install your latest 7.0 ROM

wahlmat said:
I am not 100% sure, but I would say, boot into fastboot, flash something like TWRP recovery, then you will be able to access the device files from the recovery. Just reflashing the boot shouldn't mess up anything as far as I am concerned. After that (when you've grabbed all the files you want), flash the newest firmware the guy linked above and install your latest 7.0 ROM
Click to expand...
Click to collapse
I can get phone to fastboot but it just stays on the screen that says fastboot.. do I need a computer?

HisMuse said:
I can get phone to fastboot but it just stays on the screen that says fastboot.. do I need a computer?
Click to expand...
Click to collapse
Yes you do. You need that + some software. Check out some "install custom recovery oneplus one" guides, you should be able to find something. Are you on Mac or Windows?

Yes I'm on Windows 10.. I tried removing battery overnight as well .. its not boiling hot anymore but still stuck in bootloop.

HisMuse said:
Yes I'm on Windows 10.. I tried removing battery overnight as well .. its not boiling hot anymore but still stuck in bootloop.
Click to expand...
Click to collapse
Download the Samsung ADB driver or whatever it was called, then flash a new recovery for it. There are multiple guides for doing that. After that you should be able to transfer your files to your pc while being in recovery mode

Samsung Galaxy J320FN - update fail/loop

Hi everyone! Before I describe my problem, I need you to know that I'm somewhat a noob when it comes to resolving and tinkering with software on Androids, but have some basic knowledge. I've look into all options and posting here is my last resort, please be patient
So recently, a customer brought in a J320FN. It is running on an older update (J320FNXXU0APH1, August 2016), and a few days back, after updating it to the lastest version the phone seized up. The owner has pictures and contacts that he really want to recover. After surfing through some forums, I saw that some phones, when being flashed with stock ROM via Odin, don't lose personal data, and some do. Before I try to flash this device, I want to make sure I can flash the stock ROM and eventually save the data.
I've tried wiping cache partition, because that's what I usually do when encountering software issues.
Also, the phone boots to the point where I can see the current time, and swipe down the notification bar. After some seconds, the phone reboots and the whole thing just goes on.
So my questions are;
1. Do I flash the latest version of Android or just reflash the current one?
2. Do I lose personal data, such as photos, videos and contacts?
3. Is there anything else I can do, before flashing fresh ROM on the device ?​

bregaryevich said:
Hi everyone! Before I describe my problem, I need you to know that I'm somewhat a noob when it comes to resolving and tinkering with software on Androids, but have some basic knowledge. I've look into all options and posting here is my last resort, please be patient
So recently, a customer brought in a J320FN. It is running on an older update (J320FNXXU0APH1, August 2016), and a few days back, after updating it to the lastest version the phone seized up. The owner has pictures and contacts that he really want to recover. After surfing through some forums, I saw that some phones, when being flashed with stock ROM via Odin, don't lose personal data, and some do. Before I try to flash this device, I want to make sure I can flash the stock ROM and eventually save the data.
I've tried wiping cache partition, because that's what I usually do when encountering software issues.
Also, the phone boots to the point where I can see the current time, and swipe down the notification bar. After some seconds, the phone reboots and the whole thing just goes on.
So my questions are;
1. Do I flash the latest version of Android or just reflash the current one?
2. Do I lose personal data, such as photos, videos and contacts?
3. Is there anything else I can do, before flashing fresh ROM on the device ?​
Click to expand...
Click to collapse
When it comes to flashing Samsung devices via Odin and whether or not the user data is erased or not, it depends on whether you are flashing a firmware that has an upgraded or downgraded bootloader.
The user data only gets wiped if you flash a firmware that has a bootloader that is older than the one currently installed on the device or if the bootloader is newer than the one currently on the device.
The user data does not get wiped if you flash the exact same firmware that is currently installed on the device, or at least, a firmware that has the exact same version of bootloader as the one currently installed on the device.
So you basically have 2 questions to answer.
1) does the firmware that I want to flash have an upgraded bootloader version compared to the bootloader version that is currently installed on the device?
2) does the firmware that I want to flash have a downgraded bootloader version compared to the bootloader version that is currently installed on the device?
If the answer to either of these two questions is no, then you can flash without it wiping the user data.
If the answer to either of these two questions is yes, then the user WILL be wiped during flashing.
If you want to try to save the user data before flashing the firmware, you can try finding a version of TWRP for J320N and flash it on the device then use the backup feature in TWRP to create a full backup of all data on the device. Then flash the firmware of uour choice via Odin, then the data can be extracted from the backup that was created via TWRP and restored on the device after flashing the firmware.
Sent from my LGL84VL using Tapatalk

Droidriven said:
When it comes to flashing Samsung devices via Odin and whether or not the user data is erased or not, it depends on whether you are flashing a firmware that has an upgraded or downgraded bootloader.
The user data only gets wiped if you flash a firmware that has a bootloader that is older than the one currently installed on the device or if the bootloader is newer than the one currently on the device.
The user data does not get wiped if you flash the exact same firmware that is currently installed on the device, or at least, a firmware that has the exact same version of bootloader as the one currently installed on the device.
So you basically have 2 questions to answer.
1) does the firmware that I want to flash have an upgraded bootloader version compared to the bootloader version that is currently installed on the device?
2) does the firmware that I want to flash have a downgraded bootloader version compared to the bootloader version that is currently installed on the device?
If the answer to either of these two questions is no, then you can flash without it wiping the user data.
If the answer to either of these two questions is yes, then the user WILL be wiped during flashing.
If you want to try to save the user data before flashing the firmware, you can try finding a version of TWRP for J320N and flash it on the device then use the backup feature in TWRP to create a full backup of all data on the device. Then flash the firmware of uour choice via Odin, then the data can be extracted from the backup that was created via TWRP and restored on the device after flashing the firmware.
Click to expand...
Click to collapse
Hey, thanks for the quick response.
I tried what you recommended but the problem still persists. After flashing the current version, the phone did the exact same thing and started looping.
Also tried TWRP but there's an FRP lock, preventing me from flashing it.
Now that the stock rom flash thing failed, guess there's only TWRP left. I did FRP unlocks before, but not on phones that are soft bricked. Is there anyway around it except wiping all data?
I may have forgot to mention, that the phone indeed has a passcode. And god knows what did the owner install/do with the device, that made ot to seize up.

how to know if it's a bootloop?

hello i was upgrading from stock 9.0.7 to 9.0.9, my bootloader is unlocked and twrp is a permanent one, the phone is also rooted. i wiped system then flashed the 9.0.9 then flashed the 4.0.4 twrp, rebooted into twrp, flashed latest magisk, rebooted into twrp and then pressed reboot into system. the phone is encrypted. the booting animation has been on for 20-30 minutes at this point. is it a bootloop? why what did i do wrong? thanks

@seth wellington
Try formatting data them reboot system. That should get you booted up.
Never wipe system or vendor on these devices and always when flashing a rom flash TWRP installer zip or you won't have twrp because of where recovery is located which is same place as boot.img and it has to be installed when flashing a rom or update to a rom or it won't be present.
How I flash OOS on my once T-Mobile now converted international/global OnePlus 6t.
Boot TWRP
Flash OOS global 10.3.6
Flash TWRP installer
Flash finalize
Format data
Reboot system
How I install a rom on my converted OnePlus 6t. This installation process varies depending on whether or not whatever rom I'm installing comes with gapps and or TWRP and of course you don't want to install global OOS on another model device. Since I converted my T-Mobile OnePlus 6t using guide and msm tool I now use global or international OnePlus 6t roms, firmware... Example Pixel Experience rom installation:
Boot TWRP
Flash OOS 10.3.6 global from repo xda thread
Flash Pixel Experience rom
Flash TWRP installer zip
Flash finalize zip
Format data
Reboot system.
Start to set up device then at some point enable developer options and usb debugging and doable any lock screen and boot twrp and flash magisk for root and reboot system. That is how I install a rom that has gapps but not twrp included in rom zip. Finalize can he found with a quick search on xda. It copies firmware to other slot on your AB partition device so that you don't have to. Saves 5-6 minutes and works great.
Edit
What you could have done is just flash your updated OOS , flash TWRP installer zip, reboot recovery, flash magisk, reboot system. That's what I would have done updating OOS ..
Hope this helps.
Sent from my OnePlus6T using XDA Labs

flash713 said:
@seth wellington
Try formatting data them reboot system. That should get you booted up.
Never wipe system or vendor on these devices and always when flashing a rom flash TWRP installer zip or you won't have twrp because of where recovery is located which is same place as boot.img and it has to be installed when flashing a rom or update to a rom or it won't be present.
How I flash OOS on my once T-Mobile now converted international/global OnePlus 6t.
Boot TWRP
Flash OOS global 10.3.6
Flash TWRP installer
Flash finalize
Format data
Reboot system
How I install a rom on my converted OnePlus 6t. This installation process varies depending on whether or not whatever rom I'm installing comes with gapps and or TWRP and of course you don't want to install global OOS on another model device. Since I converted my T-Mobile OnePlus 6t using guide and msm tool I now use global or international OnePlus 6t roms, firmware... Example Pixel Experience rom installation:
Boot TWRP
Flash OOS 10.3.6 global from repo xda thread
Flash Pixel Experience rom
Flash TWRP installer zip
Flash finalize zip
Format data
Reboot system.
Start to set up device then at some point enable developer options and usb debugging and doable any lock screen and boot twrp and flash magisk for root and reboot system. That is how I install a rom that has gapps but not twrp included in rom zip. Finalize can he found with a quick search on xda. It copies firmware to other slot on your AB partition device so that you don't have to. Saves 5-6 minutes and works great.
Edit
What you could have done is just flash your updated OOS , flash TWRP installer zip, reboot recovery, flash magisk, reboot system. That's what I would have done updating OOS ..
Hope this helps.
Sent from my OnePlus6T using XDA Labs
Click to expand...
Click to collapse
Thank you very much for your reply. Unfortunately I couldn't wait for that long and I had to do something right then. After some attempts I also lost my twrp and was left without a functioning recovery, so I had to look for help and some people helped me go through unbricking through the msm tool.
The thing is i just really want to always flash clean so that the phone doesn't lag and works properly, I had no idea you shouldn't wipe system... The guide that I followed said that when updating oxygen manually you have to wipe system so I thought nothing would go wrong. I still don't know what caused a bootloop since that guide was a verified one. Thanks a lot for your help. So if I'm reading it correctly, you have to do the wipes after you've installed the system, not before?

seth wellington said:
Thank you very much for your reply. Unfortunately I couldn't wait for that long and I had to do something right then. After some attempts I also lost my twrp and was left without a functioning recovery, so I had to look for help and some people helped me go through unbricking through the msm tool.
The thing is i just really want to always flash clean so that the phone doesn't lag and works properly, I had no idea you shouldn't wipe system... The guide that I followed said that when updating oxygen manually you have to wipe system so I thought nothing would go wrong. I still don't know what caused a bootloop since that guide was a verified one. Thanks a lot for your help. So if I'm reading it correctly, you have to do the wipes after you've installed the system, not before?
Click to expand...
Click to collapse
Quit a few pretty well known developers here on xda (AOSiP op is one and there are more) say not to wipe system or vendor in their first posts of their custom rom threads. The way I describe how I install works 100% always and is the cleanest possible installation. Formatting data when installing a new rom at the end of install process does all the wiping needed to make sure nothing is left from the past and everything is clean. I used to wipe various partitions but on other devices. The install directions I use are originally from the PiXeN rom developers op. I've been flashing roms since the Nexus S days. Not saying that means anything other than I'm kinda old now. ? But that install process has never failed me once and I've flashed I'm sure hundreds of times on this device.. When I update i just flashing the updated rom over current and don't wipe anything then flashing twrp installer zip, reboot recovery flash magisk reboot system or if gapps are needed when I reboot recovery flash gapps..Unless it's a major OS update that's always worked for me.
Possibly not formatting data caused boot loop.. I know when going from OOS to AOSP rom format data is mandatory or it won't boot system.. I never flash magisk during initial flash. I always boot system first then at some point boot twrp and flash magisk. Try that next round and see if it turns out better. The whole AB partition deal made me feel like I was really old and retarded.
If I was updating OOS I would boot recovery, flash OOS, flash twrp installer zip reboot recovery, flash magisk, reboot system. Check out the finalize script xda thread. There are two here. The original person who made finalize has a thread and another user has another finalize thread. I believe in guides section of OnePlus 6t. With Android there are always more than a few ways to achieve something you know ... But what I post here is what I've been doing and I've flashed 400-500 times at least on this device.
Sent from my OnePlus6T using XDA Labs

@flash713
I totally trust you and respect anything you say and recommend me to do. Thanks a lot for all the instructions and clarification. I've been into android far less time than you — only since oneplus one. I'm extremely bad with tech but even with that phone j somehow managed to get bootloops or half-bricks ten times less than with the oneplus 6. And back then in 2015 I was way more enthusiastic: flashing twice a month loads and loads of roms. Of course it wasn't my personal achievement, I was still simply following detailed and carefully written instructions on forums on how to flash a particular rom in a particular way, but hey, at least I somehow managed it.
Now in this case I'm assuming it's the a/b partitions they've introduced that have completely changed the process and ways of flashing to the point that I stick to the guides and still get bootloops lol. That unbricking process was a huge stress for me, I don't think I'm going to touch anything in my phone for a while now. And I'm on the latest 10.3.6 oxygen so it's alright. Thank you for your help buddy

seth wellington said:
@flash713
I totally trust you and respect anything you say and recommend me to do. Thanks a lot for all the instructions and clarification. I've been into android far less time than you — only since oneplus one. I'm extremely bad with tech but even with that phone j somehow managed to get bootloops or half-bricks ten times less than with the oneplus 6. And back then in 2015 I was way more enthusiastic: flashing twice a month loads and loads of roms. Of course it wasn't my personal achievement, I was still simply following detailed and carefully written instructions on forums on how to flash a particular rom in a particular way, but hey, at least I somehow managed it.
Now in this case I'm assuming it's the a/b partitions they've introduced that have completely changed the process and ways of flashing to the point that I stick to the guides and still get bootloops lol. That unbricking process was a huge stress for me, I don't think I'm going to touch anything in my phone for a while now. And I'm on the latest 10.3.6 oxygen so it's alright. Thank you for your help buddy
Click to expand...
Click to collapse
Np. My real first name is Seth. Haha. Cool name btw. I just installed OOS 10.3.7 on my 6t. I was notified of the update yesterday via oxygen updater app from play store. Good handy app to have. I would have never known 10.3.7 was out or at least not so soon if it wasn't for that app. I believe it auto notified me too. I don't remember setting it up. Android has changed soooo much you know.. I love my OnePlus 6t though. Definitely one of my most favorite devices I've ever used. What's new today is gone at some point and replaced with "better.." lol. Not always better imo anyway. Glad I could help. Feel free to message me any time. Good day to you.

Upgrade to LineageOS 19.1

Hi All,
since a couple of days the new LineageOS 19.1 is available for the Moto g7 Power.
A manual upgrade is needed to get it onto the phone.
Since I did the installation but not yet a manual upgrade of LOS to a new major version I have some questions about it:
When reading the upgrade guide there is no info about .... :
will I lose apps or any data when simply sideloading the new version?
will I have to newly install/sideload Magsik?
are there any other important things to consider when doing such an upgrade?
Thanks a lot in advance.
Cheers

1. From my experience of dirty flashing roms via twrp, I can tell you that if you flash a newer lineage zip after ONLY wiping the cache and dalvik partitions, you'll keep your data and settings etc.
2. You most likely won't have to flash the newer version of gapps (as it gets updated upon restart).
Magisk and (maybe) magisk mods are cleared as the boot image gets replaced when flashing a rom.
3. Make a full TWRP backup of your current rom just incase things go sideways with the new one (during installation, or if you want to revert back later).
Since "dirty flashing" via twrp is basically sorta sideloading, I'd assume that these would apply for you as well. I can confirm the magisk one, as that will get removed regardless.

PhotonIce said:
1. From my experience of dirty flashing roms via twrp, I can tell you that if you flash a newer lineage zip after ONLY wiping the cache and dalvik partitions, you'll keep your data and settings etc.
2. You most likely won't have to flash the newer version of gapps (as it gets updated upon restart).
Magisk and (maybe) magisk mods are cleared as the boot image gets replaced when flashing a rom.
3. Make a full TWRP backup of your current rom just incase things go sideways with the new one (during installation, or if you want to revert back later).
Since "dirty flashing" via twrp is basically sorta sideloading, I'd assume that these would apply for you as well. I can confirm the magisk one, as that will get removed regardless.
Click to expand...
Click to collapse
Great, all worked fine, thanks!