Develop Bugs

[Solved] Need help with installing Cyanogenmod (Without a PC if possible)

Hi all, new to all of this. Please keep this in mind as you read this thread.
Well first of all I have been reading about Cyanogenmod and how it helps saves battery. I also wanted to use cputuner to overclock my phone a little. I have in the past rooted this phone and installed cputuner not knowing that it could damage your phone if you didn't have a custom kernel that supported overclocking. After I found that out I uninstalled it and unrooted in fear of damage to my phone. Anyways I have a few questions and was looking knowledge, resources, and help about a few things.
Questions:
Is installing a custom rom and things needed to install a custom rom possible with a PC?
Can I safely reroot my device since I unrooted through #SU?
What do I need to do besides reroot my device in order to install a custom rom? (Cyanogenmod)
Thanks in advance!
Other INFO:
My device is a Samsung Galaxy S3 I-747
Firmware 4.4.2 KitKat
Device was rooted before using towelroot but I unrooted using #SU.
.

Ok. To install cm with no computer use, I'd say the easiest way would be to get root again with towelroot. Then install flashify from the play store. use flashify to install a custom recovery. I prefer TWRP.
Next download cm rom and Gapps. Follow the installation instructions for the rom. Generally that's boot into recovery, wipe dalvik, cache, system, and data, flash rom, flash Gapps, then reboot. You can do this from the internal SD, it won't erase that when you wipe. However, an external SD can be really handy for getting out of a jam.
If you haven't done it, a little research on the forums here about backing up your efs might be in order before flashing roms. Hope you never need it, but it could make life easier someday.
Read, read, read the forum here. This was just a real brief overview. If you don't quite understand any part, it should at least help you with what to search to learn what you need to know.
Sent from my LG-V410 using XDA Free mobile app

jason2678 said:
Ok. To install cm with no computer use, I'd say the easiest way would be to get root again with towelroot. Then install flashify from the play store. use flashify to install a custom recovery. I prefer TWRP.
Next download cm rom and Gapps. Follow the installation instructions for the rom. Generally that's boot into recovery, wipe dalvik, cache, system, and data, flash rom, flash Gapps, then reboot. You can do this from the internal SD, it won't erase that when you wipe. However, an external SD can be really handy for getting out of a jam.
If you haven't done it, a little research on the forums here about backing up your efs might be in order before flashing roms. Hope you never need it, but it could make life easier someday.
Read, read, read the forum here. This was just a real brief overview. If you don't quite understand any part, it should at least help you with what to search to learn what you need to know.
Sent from my LG-V410 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks friend will look into it a little more. So is there a major risk of getting bricked or are chances slim? Also do you have any links to the Cyanogenmod version I'm looking for? I would like it to be 4.4.2, not 5.X.X. And I also need the appropriate gapps file. If you don't know I still thank you for the info friend!

KentuckyGuy447 said:
Thanks friend will look into it a little more. So is there a major risk of getting bricked or are chances slim? Also do you have any links to the Cyanogenmod version I'm looking for? I would like it to be 4.4.2, not 5.X.X. And I also need the appropriate gapps file. If you don't know I still thank you for the info friend!
Click to expand...
Click to collapse
Chances of bricking should be slim as long as you follow the instructions closely.
CyanogenMod 11 is based on Android 4.4.X, Kitkat. Nightlies can be found here or here.
Snapshot releases, sometimes called monthlies, can be found here.
There are options regarding Google Apps( GAPPS ) the choices from CM are here.
Some prefer the GAPPS packages provided by Paranoid Android, look here.

dawgdoc said:
Chances of bricking should be slim as long as you follow the instructions closely.
CyanogenMod 11 is based on Android 4.4.X, Kitkat. Nightlies can be found here or here.
Snapshot releases, sometimes called monthlies, can be found here.
There are options regarding Google Apps( GAPPS ) the choices from CM are here.
Some prefer the GAPPS packages provided by Paranoid Android, look here.
Click to expand...
Click to collapse
Thanks so much! Have been researching like crazy and odds seem pretty good. Problem is I've hit a ditch headfirst. I can't reboot using towering because I updated my kernel sometime through the period when my phone was unrooted (idk when or how this was done.) The date is apast june the 3rd and i read it won't work apast that date. Is there a workaround for this? I have no PC so I would like a non-PC method if possible. I just wanted to say I have tried all the modstrings for toweroot and still nothing.

KentuckyGuy447 said:
Thanks so much! Have been researching like crazy and odds seem pretty good. Problem is I've hit a ditch headfirst. I can't reboot using towering because I updated my kernel sometime through the period when my phone was unrooted (idk when or how this was done.) The date is apast june the 3rd and i read it won't work apast that date. Is there a workaround for this? I have no PC so I would like a non-PC method if possible. I just wanted to say I have tried all the modstrings for toweroot and still nothing.
Click to expand...
Click to collapse
The June 3rd date probably only counts if you took all of the OTA updates, okay rechecked your OP and I see that you are on NE4. I recall that either the NE4 or the NJ1 update patched the kernel to block TowelRoot. I take it when you say Firmware 4.4.2 KitKat you mean baseband, modem, and Samsung stock rom.
With SuperSu you can re-root using it, assuming you unrooted but did not remove the app. I don't know if the same applies to th SU app that comes with CWM. You could try. If you did go back to stock rom and properly formated you may no longer have su on your phone.
Yes, if you have a custom recovery on your phone you should be able to re-root without a PC. Search for the zip version of SuperSu, put it on an external sdcard, and flash it through the recovery. Without a custom recovery I'm not sure of other options not requiring root that do not involve a PC (Windows or Linux) or a Mac. Apps like Flashify require root, so will not work for you at the moment.

dawgdoc said:
The June 3rd date probably only counts if you took all of the OTA updates, okay rechecked your OP and I see that you are on NE4. I recall that either the NE4 or the NJ1 update patched the kernel to block TowelRoot. I take it when you say Firmware 4.4.2 KitKat you mean baseband, modem, and Samsung stock rom.
With SuperSu you can re-root using it, assuming you unrooted but did not remove the app. I don't know if the same applies to th SU app that comes with CWM. You could try. If you did go back to stock rom and properly formated you may no longer have su on your phone.
Yes, if you have a custom recovery on your phone you should be able to re-root without a PC. Search for the zip version of SuperSu, put it on an external sdcard, and flash it through the recovery. Without a custom recovery I'm not sure of other options not requiring root that do not involve a PC (Windows or Linux) or a Mac. Apps like Flashify require root, so will not work for you at the moment.
Click to expand...
Click to collapse
Thanks for the info, sadly I did uninstall #SU. Here is a ss of my modem info and such. I think it pretty much confirms I have the NJ1 version but I need you to confirm that.

KentuckyGuy447 said:
Thanks for the info, sadly I did uninstall #SU. Here is a ss of my modem info and such. I think it pretty much confirms I have the NJ1 version but I need you to confirm that.
Click to expand...
Click to collapse
I'm stuck.
You can install a custom recovery without having root, if you have a PC. You would use either Odin, Heimdall, or maybe adb.
You can install a custom recovery without a PC if you have root. You would use an app Like Flashify, Rom Manager, or Goo Manager (if it still exists).
You can flash a rom without a PC if you have a custom recovery, root is not needed.
Some roms, usually stock, can be flashed without a custom recovery if you have a PC.
I don't know the solution until you have access to a PC. I could see it being possible using a live USB with persistence of a Linux distribution, but you still have need for a PC. It's been a while since I created a live USB. The method I used required a small installation on the PC. so I don't see this as an immediate solution for you.

Oh sorry. I don't think towelroot works once you're on nj1, unless it has been updated.
If you get access to a PC, rooting is still fairly easy. You can use download mode and odin or heimdall to flash a custom recovery (be sure to uncheck reboot if using odin, or be really ready to pull battery). Don't let your phone reboot normally, you'll have to pull battery once odin is done.
Reboot to custom recovery, then flash supersu and you'll be rooted again, and set up to do whatever you want with your phone.
Sent from my LG-V410 using XDA Free mobile app

Thanks all for your help. I have decided I'm gonna give C-F Root a try as it seems very easy, then use Flashify to get CWM. Correct me if I'm wrong but there's no boot loader for my model type right? Couldn't seem to find anything on the subject except the Verizon variant. I'm gonna still need help deciding which gapps to flash as I'm gonna flash the latest Cyanogenmod monthly build. Is there anything else to be aware of when using a new Rom?

KentuckyGuy447 said:
Thanks all for your help. I have decided I'm gonna give C-F Root a try as it seems very easy, then use Flashify to get CWM. Correct me if I'm wrong but there's no boot loader for my model type right? Couldn't seem to find anything on the subject except the Verizon variant. I'm gonna still need help deciding which gapps to flash as I'm gonna flash the latest Cyanogenmod monthly build. Is there anything else to be aware of when using a new Rom?
Click to expand...
Click to collapse
excuse for butting in .... but if you dont know your bootloader/modem info. here is an app called 'samsung info' that should tell you.
your question "...... but theres no bootloader for my phone model right?" kinda worried me. its important to know because they should match AND trying to downgrade can brick your device. on the plus side ; i've never seen a custom ROM include bootloader/modem in it.
again , just a thought and not trying to butt in.:good:
https://www.dropbox.com/s/4ka74x02tg1rrn1/org.vndnguyen.phoneinfo-1.apk?dl=0
"all i can really do , is stay out of my own way and let the will of heaven be done"

As mrrocketdog stated, the Samsung Info app will tell you your bootloader and modem. If what you previously stated is correct, they should both be NJ1. You can get the same info by issuing these commands in a terminal emulator on the phone:
Code:
getprop ro.bootloader
and
Code:
getprop | grep version.baseband

Appreciate the butting in! You may have just saved me from bricking my phone lol. Maybe I need to do a lot more research because that just lost me. So how do I tell that my phone is equipped with a boot loader? And if it is how do I disable it? I read that in order to flash a new Rom the boot loader must be disabled. (Correct me if I'm wrong) I'm no where near the point of flashing a new Rom (Cyanogenmod) but this is a great furniture reference to me.

KentuckyGuy447 said:
Appreciate the butting in! You may have just saved me from bricking my phone lol. Maybe I need to do a lot more research because that just lost me. So how do I tell that my phone is equipped with a boot loader? And if it is how do I disable it? I read that in order to flash a new Rom the boot loader must be disabled. (Correct me if I'm wrong) I'm no where near the point of flashing a new Rom (Cyanogenmod) but this is a great furniture reference to me.
Click to expand...
Click to collapse
every phone has a bootloader , two if i'm not mistaken. the one you're concerned with comes already unlocked on the good 'ol S3. (i bricked my first s3 trying to 'unlock' the bootloader). just find out bootloader/modem version (see posts above) to make sure they match (to avoid issues later) and just dont ever try to downgrade.
"all i can really do , is stay out of my own way and let the will of heaven be done"

mrrocketdog said:
every phone has a bootloader , two if i'm not mistaken. the one you're concerned with comes already unlocked on the good 'ol S3. (i bricked my first s3 trying to 'unlock' the bootloader). just find out bootloader/modem version (see posts above) to make sure they match (to avoid issues later) and just dont ever try to downgrade.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
You have lifted a burden off my shoulders friend! Ever since I wanted to flash a custom Rom I've been worried if my phones bootloader was locked! I can now be at ease now that I know its unlocked. Will check upon that info about bootloader/modem.

Here is the info mrrocketdog

Is there a reason you can't use a PC to install a ROM?
I'm asking because I also do not know of a way to install a ROM without having root.
If you are able to root, you could try using the CM installer again.

audit13;5898140 said:
Thanks friend no worries, mrrocketdog helped me figure it out, than to all who helped!
Click to expand...
Click to collapse

KentuckyGuy447 said:
Here is the info mrrocketdog
Click to expand...
Click to collapse
Those are the latest versions of the bootloader and modem. You will be good for CM 12 or CM 11, and other custom ROMs based on CM. Older versions will work with them, but you probably need to edit the updater-script. (The older versions are not likely to include the NJ1 versions in the checks as they were not out when the ROMs were last updated.) NJ1 will also work with any of the ROMs based on the KitKat TouchWiz releases by Samsung.
As soon as you can find a PC to borrow you should be in business. Any chance of using one at a public library?

Appreciate all the help you gave me too friend, providing the links to cm and gapps, gonna borrow my friends laptop Sunday and try to root flash C-F Root through Odin. Thats the part that scares me but I should be good as people has confirmed it works for NJ1. Wish me luck friend. Would you recommend installing CM12? I personally like kit Kat and I know CM11 is based on that but is CM12 better? I guess its based on Lollipop

How to get back to stock?

My op3 is running on cm14.1 jgcaap and I was planning to go back to OOs. I want to flash 3.2.8. Should I flash through twrp or adb side load ?

MM MaD said:
My op3 is running on cm14.1 jgcaap and I was planning to go back to OOs. I want to flash 3.2.8. Should I flash through twrp or adb side load ?
Click to expand...
Click to collapse
You can do either but ensure two things for avoiding a possible bootloop. One is the TWRP and the other is wiping all except internal storage before flashing the ROM.
You should have the modified TWRP 3.0.2-23.
Wipe, flash ROM and flash TWRP before booting as the existing TWRP is likely to be overwritten by the stock recovery. Speaking from experience!
Though I was going from 3.2.7 to 3.2.8, TWRP was overwritten which I found only after booting and when I tried to get back into recovery.

Hi. what's the difference between the official and modded twrp? And is it better to have which one? Thanks

jfodra said:
Hi. what's the difference between the official and modded twrp? And is it better to have which one? Thanks
Click to expand...
Click to collapse
The reason of the existence of the modified TWRP is the inability of the original one to deal with the OOS community builds. The modified version is capable of flashing these builds.
Some older versions of recoveries have problems flashing some newer android version so you should always use the newest TWRP release out there and since the original release is a little bit outdated, the modified one is the better choice if you want to use Nougat
If you want to stay with Marshmallow then the original TWRP release would also do the trick for you (I use the original one too)

lekronop said:
The reason of the existence of the modified TWRP is the inability of the original one to deal with the OOS community builds. The modified version is capable of flashing these builds.
Some older versions of recoveries have problems flashing some newer android version so you should always use the newest TWRP release out there and since the original release is a little bit outdated, the modified one is the better choice if you want to use Nougat
If you want to stay with Marshmallow then the original TWRP release would also do the trick for you (I use the original one too)
Click to expand...
Click to collapse
Ooohh. If i flashed the modified one, i could still be able to flash the official oos builds? I'm going to use the toolkit provided and it seems that uses the modified twrp one.

jfodra said:
Ooohh. If i flashed the modified one, i could still be able to flash the official oos builds? I'm going to use the toolkit provided and it seems that uses the modified twrp one.
Click to expand...
Click to collapse
Yes this is no problem, you can flash the older builds with the modified twrp, so no worries.

lekronop said:
Yes this is no problem, you can flash the older builds with the modified twrp, so no worries.
Click to expand...
Click to collapse
Oh okay. Thanks a lot for the clarifications.

jfodra said:
Oh okay. Thanks a lot for the clarifications.
Click to expand...
Click to collapse
No problem, but even if the modified one couldn't handle older android versions then you can always flash another twrp which works for your desired task. So if you have twrp 3.0.2-23 installed you can go back to 3.0.2-1 or even lower without any problems

lekronop said:
No problem, but even if the modified one couldn't handle older android versions then you can always flash another twrp which works for your desired task. So if you have twrp 3.0.2-23 installed you can go back to 3.0.2-1 or even lower without any problems
Click to expand...
Click to collapse
Oh. Okay. Just a question though, does unlocking the bootloader also wipes the files in the phone such as the images and music?

jfodra said:
Oh. Okay. Just a question though, does unlocking the bootloader also wipes the files in the phone such as the images and music?
Click to expand...
Click to collapse
Yes it does.. That's the reason I unlock the bootloader as soon as I get a new device

i was on freedom os . i am back on stock oxygen os but i have 2 issues.
1) when i got an update to 3.2.7 it showed in german that there is an update even though the language i chose was english
2) The boot animation shows the freedom os splash screen and then the boots into stock. Ihave got the boot animation of stock os but need instructions on how to flash the zip.
Can someone throw light on the above 2 issues?

Help updating ROM please

Hi guys, I'm on the international beta rom but it's quite outdated now and I'd like to get up to speed with the OTA's.
I download the full version for flashing in TWRP as i'm rooted but it asks for a password everytime.
Apparently I need to format the internal storage to get past this, but I don't want to lose all my apps and setup etc. Is there anyway to update without losing root and files etc?
Thank you in advance,
Andy

The beta is based on Android 7 Nougat, right? And the stable is currently still based on 6.0.1. If you mean you'd like to get back to the stable channel I think a clean flash is the only option. You might be able to restore your data via TWRP but I'm not sure if that's OK when downgrading from 7 to 6. Maybe someone else can confirm this.
I'd say the best option would be a fastboot clean flash of the full ROM and go from there. Then you can reflash TWRP.

thank you for your reply, but I'm not on nougat at the moment, I'm happy sticking to the beta channel but as I'm rooted I can't OTA update to newer beta version which would be nougat.
Cheers,
Andy

andypa1 said:
thank you for your reply, but I'm not on nougat at the moment, I'm happy sticking to the beta channel but as I'm rooted I can't OTA update to newer beta version which would be nougat.
Cheers,
Andy
Click to expand...
Click to collapse
In that case, follow the steps I mentioned but using the Beta Fastboot ROM using the Mi Flash tool. Make sure you select "flash_all_except_storage.bat" and you'll keep your data and apps during the process. Once the device is booted, just make sure not to root and you'll be able to OTA to new beta roms when they are released.
Here's a link to the full list of Fastboot flashable ROMs. You didn't mention whether you're on Helium or Hydrogen, so make sure to pick the correct ROM for your device.
Good luck!

Question flashing Oos update through twrp?

can we flash Oos through twrp? also can we flash Oos rom from custom rom? if so what are the instructions? thx in advance. yes i have a lot of questions lol

freddienuxx said:
can we flash Oos through twrp? also can we flash Oos rom from custom rom? if so what are the instructions? thx in advance. yes i have a lot of questions lol
Click to expand...
Click to collapse
I'm also curious about this. My current method is to just use the MSM tool whenever I want to go back to stock but it is definitely time consuming. As far as I know TWRP is still early in development and a lot of things that should normally work dont work perfectly

I have definitely flashed OOS through TWRP (from AA to BA, not a custom rom), but haven't had any issues since I did it. That being said I would assume the steps would be to flash, factory reset, then root etc.

Haunt3r said:
I have definitely flashed OOS through TWRP (from AA to BA, not a custom rom), but haven't had any issues since I did it. That being said I would assume the steps would be to flash, factory reset, then root etc.
Click to expand...
Click to collapse
hm that is great to hear, however, when I attempt to flash oos 11.2.7.7AA (from oos 11.2.4.4AA) I get an error saying that I am missing /system_ext, /product, and /odm partitions. did you do anything other than simply install oos via twrp, because I am not sure why I am getting this error

thirtythr33 said:
hm that is great to hear, however, when I attempt to flash oos 11.2.7.7AA (from oos 11.2.4.4AA) I get an error saying that I am missing /system_ext, /product, and /odm partitions. did you do anything other than simply install oos via twrp, because I am not sure why I am getting this error
Click to expand...
Click to collapse
To my knowledge you cannot flash from 2.4.4AA to 2.7.7AA because it is an incremental update, at least through twrp. (I've never flashed anything but full roms via twrp). I actually fully switched to the EU firmware from the Global firmware because of the global version seemingly going fully to OTA updates and not providing full ROMs like the EU version.

Haunt3r said:
To my knowledge you cannot flash from 2.4.4AA to 2.7.7AA because it is an incremental update, at least through twrp. (I've never flashed anything but full roms via twrp). I actually fully switched to the EU firmware from the Global firmware because of the global version seemingly going fully to OTA updates and not providing full ROMs like the EU version.
Click to expand...
Click to collapse
no you are right, but I have the full update via oxygen updater, so these errors of missing partitions are extremely frustrating.

thirtythr33 said:
no you are right, but I have the full update via oxygen updater, so these errors of missing partitions are extremely frustrating.
Click to expand...
Click to collapse
there is no "full" update for 7.7aa it's solely an OTA

Haunt3r said:
there is no "full" update for 7.7aa it's solely an OTA
Click to expand...
Click to collapse
yeah man there is, came out June 28th, check oxygen updater or oneplus software download.
lol either way I can't flash it so fml

Haunt3r said:
there is no "full" update for 7.7aa it's solely an OTA
Click to expand...
Click to collapse
Yes there is, it came out a few days ago about 3gb's on OnePlus website...

Ah ****. Had no idea. Might flash back to aa if they're releasing full updates. Only reason I switched to eu was that reason. Definitely weird you're running into issues with it though

Haunt3r said:
Ah ****. Had no idea. Might flash back to aa if they're releasing full updates. Only reason I switched to eu was that reason. Definitely weird you're running into issues with it though
Click to expand...
Click to collapse
yeah man we have to wait insane long for AA full updates. yeah my issue is very frustrating and I've tried everything short of msm, I just don't see how it is possible that twrp reports I am missing those partitions yet my phone boots, but slot B is f'd, and I can't flash full AA update either through twrp or local upgrade.

Okay so if we do flash the full ota through recovery what's the correct process on this to keep twrp and magisk without needing a PC to push the recovery and root back onto the device?

Question Upgrading to Android 13 Question

Hi,
I am currently on Android 12, rooted with Magisk, and I update each month using the latest Factory Image.
If (when) I upgrade to Android 13...
- I know it's usually recommended to do a clean install when you go to a brand new build, which means wiping data. I'm okay with this ASIDE from the fact that I have GBs worth of music on my phone which takes forever to both back up and restore.
- Do I really need to install 13 to both slots?
- Is root / Magisk working fine on 13?
- Any other suggestions on how to make this upgrade easier?
Thanks in advance!
Tony

tonyfiore75 said:
Hi,
I am currently on Android 12, rooted with Magisk, and I update each month using the latest Factory Image.
If (when) I upgrade to Android 13...
- I know it's usually recommended to do a clean install when you go to a brand new build, which means wiping data. I'm okay with this ASIDE from the fact that I have GBs worth of music on my phone which takes forever to both back up and restore.
- Do I really need to install 13 to both slots?
- Is root / Magisk working fine on 13?
- Any other suggestions on how to make this upgrade easier?
Thanks in advance!
Tony
Click to expand...
Click to collapse
it would be recommended to flash at least the bootloader to both slots, root works perfectly fine

tonyfiore75 said:
Hi,
I am currently on Android 12, rooted with Magisk, and I update each month using the latest Factory Image.
If (when) I upgrade to Android 13...
- I know it's usually recommended to do a clean install when you go to a brand new build, which means wiping data. I'm okay with this ASIDE from the fact that I have GBs worth of music on my phone which takes forever to both back up and restore.
Click to expand...
Click to collapse
I haven't wiped before flashing a new version of Android on my Pixel phones in the last 5-6 years. Android 13 Stable that I manually updated using the full factory image, coming from the first Android 12 July update has worked fine for me.
Good thing, too, because I hate starting from scratch any more.
(I too have hundreds of GBs of music on my phone)
tonyfiore75 said:
- Do I really need to install 13 to both slots?
Click to expand...
Click to collapse
"Have to"? No. It would be good advice to install it to both slots, though.
tonyfiore75 said:
- Is root / Magisk working fine on 13?
Click to expand...
Click to collapse
Yes.
tonyfiore75 said:
- Any other suggestions on how to make this upgrade easier?
Thanks in advance!
Tony
Click to expand...
Click to collapse
No. Everything was just like every month's normal update process for me with flashing the full firmware zip to update, and then I flashed it again to the other slot the next day.

Thanks, everyone! I really appreciate it. I'll just flash the update as I normally would (editing the .bat file) to Slot A and then do the same to Slot B. Or can you flash it to -all slots at the same time? I know I used to do that with my Pixel 4 but that may have just been when flashing the magisk file.

tonyfiore75 said:
Or can you flash it to -all slots at the same time?
Click to expand...
Click to collapse
Yes, you can.

Cool, thanks.

Sorry it's my first time with root and a custom kernel in the pixel, I have never updated it because I installed it on June, could you post a guide with the commands please?
Thanks a lot!

jumpet said:
Sorry it's my first time with root and a custom kernel in the pixel, I have never updated it because I installed it on June, could you post a guide with the commands please?
Thanks a lot!
Click to expand...
Click to collapse
Hiya! Just click the yellow How To Guide quick filter at the top of list of threads in this section, and there are at least two or three threads for how to update. The OP of the thread in my signature below also has the commands.

roirraW edor ehT said:
Yes, you can.
Click to expand...
Click to collapse
If I have to flash to both slots with the factory image, do I also have to flash to both slots with the updated Magisk file as well?

Didn't come to the forum to read messages in the past few days! I updated my P6P from A13 beta 4.1 to official using the factory image -w method as I have done it in the past 10 months. It is now running smoothly and I didn't encounter any problem so far. I start reading messages saying that A13 has to be flashed in slot A and slot B. Since I already upgrade my machine with normal method, I still able to keep my data, root and API integrity, and most import booting up normally, so do I have do it again to reflash to this Slot A/B thing? I am not so sure I understand this new requirement, so sorry if this question sounds stupid.

tonyfiore75 said:
If I have to flash to both slots with the factory image, do I also have to flash to both slots with the updated Magisk file as well?
Click to expand...
Click to collapse
Not really. Just do it on the slot you end up running. The slot you won't be running won't have root, but that's okay. You'll likely never actually use the other slot, and if by some rare chance you do, it's an easy thing to flash the Magisk'd stock boot.img to it at that time.

acwcanada said:
Didn't come to the forum to read messages in the past few days! I updated my P6P from A13 beta 4.1 to official using the factory image -w method as I have done it in the past 10 months. It is now running smoothly and I didn't encounter any problem so far. I start reading messages saying that A13 has to be flashed in slot A and slot B. Since I already upgrade my machine with normal method, I still able to keep my data, root and API integrity, and most import booting up normally, so do I have do it again to reflash to this Slot A/B thing? I am not so sure I understand this new requirement, so sorry if this question sounds stupid.
Click to expand...
Click to collapse
I'm trying to answer on mobile, so it's tough for me because most detailed support I give I do from the computer but I can't right now.
Check out the OP and last few pages of the thread on my signature below (use desktop mode in a mobile browser if necessary) for more information about flashing to both slots.
Look at it this way. Normally you only flash the full factory image once (so only to one slot). This time you did it once already, so now you'll have to switch slots and flash it to the other slot.
You could then switch slots again and use the slot you already re-rooted. Both slots have the same exact apps and app data - the second flashed slot just won't have the rooted boot.img that you already have on the slot you're running now.

I think it's most simple to use the Google flash tool. You don't have to wipe anything, just unroot, run the tool, reroot. Not script editing and praying that you didn't screw anything up.

rhetorician said:
I think it's most simple to use the Google flash tool. You don't have to wipe anything, just unroot, run the tool, reroot. Not script editing and praying that you didn't screw anything up.
Click to expand...
Click to collapse
That's how I do it every month

roirraW edor ehT said:
I'm trying to answer on mobile, so it's tough for me because most detailed support I give I do from the computer but I can't right now.
Check out the OP and last few pages of the thread on my signature below (use desktop mode in a mobile browser if necessary) for more information about flashing to both slots.
Look at it this way. Normally you only flash the full factory image once (so only to one slot). This time you did it once already, so now you'll have to switch slots and flash it to the other slot.
You could then switch slots again and use the slot you already re-rooted. Both slots have the same exact apps and app data - the second flashed slot just won't have the rooted boot.img that you already have on the slot you're running now.
Click to expand...
Click to collapse
OK, thanks so much, achieved done that. One more question, how about the future updates? Do we have to do it every month in the future when Google provide the monthly updates?

acwcanada said:
OK, thanks so much, achieved done that. One more question, how about the future updates? Do we have to do it every month in the future when Google provide the monthly updates?
Click to expand...
Click to collapse
No, you only needed to flash to both slots this one time just to make sure both slots were on A13.

Lughnasadh said:
No, you only needed to flash to both slots this one time just to make sure both slots were on A13.
Click to expand...
Click to collapse
Thank you for the feedback.

rhetorician said:
I think it's most simple to use the Google flash tool. You don't have to wipe anything, just unroot, run the tool, reroot. Not script editing and praying that you didn't screw anything up.
Click to expand...
Click to collapse
No need to unroot - just run the tool (making sure wipe or force flash all partitions isn't selected), and then reroot.
I like the satisfaction of getting my hands a little dirty, plus the knowledge that if something goes wrong, it's most probably my fault!
I also like to Magisk my own boot.img from the factory image, and if I'm going to download it anyway, I figure might as well flash it.