granted that i rooted this through magisk and was expecting an issue with updates but what is the correct procedure to do updates while preserving data?
Also, any release date for twrp + lineageos?
SynGreis said:
granted that i rooted this through magisk and was expecting an issue with updates but what is the correct procedure to do updates while preserving data?
Also, any release date for twrp + lineageos?
Click to expand...
Click to collapse
Try Pixel Flasher
says pixelflasher doesnt need to be installed just double click. which file am i clicking? im on windows 10.
SynGreis said:
granted that i rooted this through magisk and was expecting an issue with updates but what is the correct procedure to do updates while preserving data?
Also, any release date for twrp + lineageos?
Click to expand...
Click to collapse
you can follow this to update , i did this way and it was easy and fast done and kept all data without losing anything
any update on the lineage os for google pixel? im anxious to remove bloatware and such.
Related
This is the first phone where I don't plan to install a custom ROM, and I don't know how OTA updates work while rooted.
Can they still be downloaded/installed normally while rooted? If so do I need to re-apply root each update? Does updating while rooted, or reapplying root afterwords wipe apps/settings?
I'm not sure if these are questions that can even be answered now, before anything has shipped, but worth a shot.
I might be wrong but I believe once you root you have to side load any OTA updates that come along and you may have to reroot and no this won't wipe ur phone
Flash Fire will be the way to go....
On rooted 2016 pixel never got flashfire to work for an ota. As for sideloading, that didn't work either. Had to download latest full image and use minimal adb to flash the full image. That can be done without wiping the phone and the detailed instructions are on XDA. I wonder if the pixel2 will be rootable by the same method to root the 2016 pixel. If I trade in for the pixel2 I will try it.
me_droid said:
On rooted 2016 pixel never got flashfire to work for an ota. As for sideloading, that didn't work either. Had to download latest full image and use minimal adb to flash the full image. That can be done without wiping the phone and the detailed instructions are on XDA. I wonder if the pixel2 will be rootable by the same method to root the 2016 pixel. If I trade in for the pixel2 I will try it.
Click to expand...
Click to collapse
I started with full image and removing the w.
Then Google started releasing OTA So I used flashfire and it worked fine.
I tried sideloading and it worked also.
During the whole period, I never lost root or hotspot accept for the last update I lost hotspot because of an update changing Carrier entitlement. So I had to go about modding system file but. My hats off to developers. I suggest everyone donates to the people who make things available.
Thanks,
There is a tutorial for using Magisk Manager with OTA Updates and A/B partition. I hope this will work with Pixel 2?
github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
FSMcas said:
There is a tutorial for using Magisk Manager with OTA Updates and A/B partition. I hope this will work with Pixel 2?
github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Click to expand...
Click to collapse
Nice tutorial. Is there a way to install magisk any easier if I don't care about OTA's? Can't I just flash magisk and carry on or do I still have to worry about the A/B partitions?
I did this and now I'm stuck in a bootloop!
FSMcas said:
There is a tutorial for using Magisk Manager with OTA Updates and A/B partition. I hope this will work with Pixel 2?
github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Click to expand...
Click to collapse
I followed this procedure and everything seemed to be fine until reboot. At first it would attempt to boot, get to the screen with the G logo, and then after a few seconds reboot again, showing the unlocked bootloader warning screen. i interrupted the loop with the power button, and now I get to the G logo with the small grey animated progress bar going back and forth, but it hangs there and never completes booting..
Hey everyone,
I have a Nexus 5 that I haven't updated in a long time that I'd like to get the latest possible OS for. The only modifications I've made which I think might be important are:
Unlocked bootloader
Rooted using SuperSU (v2.8.2 currently)
Installed XPosed (installer v2.6.1, not sure what version of the framework but it should be the latest supported by 4.4.4) with a few modules
Installed App Ops and removed permissions from some apps
Installed StickMount
I don't believe I have any custom recovery installed (I'd used a script to root and install XPosed originally and I don't know if it made any other changes). I'm comfortable using adb if needed but I'm cool with tools like FlashFire too.
My end goal is to have an updated OS with root and XPosed. I assume I'll need Magisk for XPosed, but not sure about root.
How should I go about doing this? I'm cool with losing all of my data (I'll be making backups with Titanium Backup) though knowing ahead of time if that'll be the case would be nice. If it's possible to update without losing data and without affecting anything that'd be nice, but maybe a clean start would be good? The OTA guide on this forum is only for 5, not 6, and most online guides start with 5. I don't want to mess up obviously. xD
Any advice/steps would be appreciated! Thanks!
Aecyl said:
Hey everyone,
Click to expand...
Click to collapse
You need TWRP. Then to install it. https://forum.xda-developers.com/go...om-android-m-preview-2-flashable-zip-t3157299
pavik62 said:
You need TWRP. Then to install it. https://forum.xda-developers.com/go...om-android-m-preview-2-flashable-zip-t3157299
Click to expand...
Click to collapse
The link you gave doesn't have the latest 6.0.1 build and it also says that it requires a minimum bootloader (HHZ12h) that I don't have (I have HHZ11k). Would it be possible to use the latest build from Google? What do I do about the bootloader? And would using TWRP as the recovery prevent me from passing SafetyNet?
Thanks for replying!
Could I follow this guide with the latest factory image and then install Magisk, root, and XPosed? https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/
If you're on stock, update using the built in updates. That'll get you all the latest firmware. I'm pretty sure the N5 goes up to 5.0 normally.
Roxasmaker said:
If you're on stock, update using the built in updates. That'll get you all the latest firmware. I'm pretty sure the N5 goes up to 5.0 normally.
Click to expand...
Click to collapse
Would I have to do anything to XPosed or supersu first? I'd like to update to 6.0.1, too. I've seen online that there are OTA updates for it too.
Nope. But you may have to reinstall root, which is very easy once you're updated. Just let the updates do their thing, and you'll be on your merry way! Hope I helped
I think what I'll do is flash stock 4.4.4 keeping user data and then use the OTAs to update to 6. That way I have a clean system install to use Magisk with without losing any user data. (If that doesn't work I'll just flash 6.0.1 for a clean install.)
Thanks to our friend @hikari_calyx, who provided Internal OTA Update zip package to Android Pie for Nokia 8, we can test it before Nokia release it. The link contains two zips
1) December patch for Oreo for Nokia 8
2) Update to Pie for Nokia 8
Link:
https://mega.nz/#F!W50gzawY!nC8Yb9yE6n08gGafFi700A
Preconditions:
1) All must be Stock, no root, magisk, xposed, no mods etc.
Steps you have to do is:
1) Download NB1-488L-0-00WW-B01-488K-0-00WW-B01-update.zip - this is December Security Patch
2) Update manually (2 ways)
a)
- Copy the file on internal memory root folder
- Dial
Code:
*#*#874#*#*
and there will be possibility of update (this way you may use this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md#ota-installation to keep Magisk)
b)
- Connect your phone to PC
- Go to stock recovery (https://www.youtube.com/watch?v=RmewL1i50c0)
- Choose Apply Update from ADB,
- Type
Code:
adb sideload path_to_zip/NB1-488L-0-00WW-B01-488K-0-00WW-B01-update.zip
where path_to_zip is a path to the location of the file
- Wait and reboot phone, you should have December Security Patch
3) Repeat whole steps froim point 2) for the NB1-5110-0-00WW-B03-488L-0-00WW-B01-update.zip
4) Since @hikari_calyx provided us next internal update, repeat steps for NB1-5110-0-00WW-B05-5110-0-00WW-B03-update.zip and NB1-5110-0-00WW-B07-5110-0-00WW-B05-update.zip.
5) If you want to root your phone, here you may find stock and patched with twrp boot.imgs provided by @THMSP
https://mega.nz/#F!r3RUnaiC!p8FZqNpiPLK8XNwYusJv1Q
Like I wrote at the beginning, it is internal update, so I would strongly recommend to unlock bootloader in case something goes wrong. Additionally it is not known at the moment whether it can be possible to update to official version when it comes, so most likely downgrade will be necessary.
As always, you do all on your own risk and I won't be responsible for any damage you do to your phone.
PS: Here is the proof:
I'm rooted with magisk, can I update uninstalling magisk? or need reinstal firmware with OST?
Gemmik said:
I'm rooted with magisk, can I update uninstalling magisk? or need reinstal firmware with OST?
Click to expand...
Click to collapse
Flash stock or restore stock by magisk, and than give it a try. If it won't work, than OST, downgrade and upgrade again till November, and than zip provided by @hikari_calyx. And than use images provided by @THMSP to root.
If I move those otas to internal download folder and do as described above any chances to go wrong !?
Bootloader locked unrooted and unmodified attached all
Too good to be truth
Just_Rise said:
If I move those otas to internal download folder and do as described above any chances to go wrong !?
Bootloader locked unrooted and unmodified attached all
Too good to be truth
Click to expand...
Click to collapse
There is a chance that you lose possibility for later OTA updates. I would not try to update without unlocking bootloader
czupyt said:
There is a chance that you lose possibility for later OTA updates. I would not try to update without unlocking bootloader
Click to expand...
Click to collapse
You're right ,didn't thinked about that
Really divided about what to do now
Thanks anyway !
Confirmed working on TA-1012
Known issue on NB1-5110:
The lock screen can't be reconfigured - it will crash when you try to change.
I just tried to install on a Mexico TA-1012 and not working, returns an error "package is for source build 00WW_4_88K but expected 00WW_4_84G, installation aborted"
Did you know what is the problem?
rocalino said:
I just tried to install on a Mexico TA-1012 and not working, returns an error "package is for source build 00WW_4_88K but expected 00WW_4_84G, installation aborted"
Did you know what is the problem?
Click to expand...
Click to collapse
There are two files, please flash the smaller one first via any of the method mentioned, and then the larger.
Sahilsinghlodhi said:
There are two files, please flash the smaller one first via any of the method mentioned, and then the larger.
Click to expand...
Click to collapse
Seems the colleague is on SW older than 4.88B (which would be the update from May), therefore he cannot use ADB sideload directly.
czupyt said:
Seems the colleague is on SW older than 4.88B (which would be the update from May), therefore he cannot use ADB sideload directly.
Click to expand...
Click to collapse
So updates from 488B to 488K need to be uploaded.
On a side note - Pie requiring December security patches means HMD will miss "by end of November" deadline.
revanmj said:
On a side note - Pie requiring December security patches means HMD will miss "by end of November" deadline.
Click to expand...
Click to collapse
Seems so
Solved
Toedwarrior said:
Guys i accidentally flashed stock november boot to october system while doing that now my phone got stuck on Nokia screen and hardwarebuttons is not working. I tried adb command device gets listed but it says unauthorized. What should i do?
Click to expand...
Click to collapse
To be clear - You flashed November /boot partition to October /system partition? Switch slots from active to inactive. If you flashed November boot to October boot, flash again October boot. All in all you can use OST LA to downgrade and upgrade again.
czupyt said:
Preconditions:
1) All must be Stock, no root, magisk, xposed, no mods etc.
......
2) Update manually (2 ways)
a)
- Copy the file on internal memory root folder
Click to expand...
Click to collapse
How does this possible? Without rooting the phone you can`t access root folder, or i am wrong?
phm83 said:
How does this possible? Without rooting the phone you can`t access root folder, or i am wrong?
Click to expand...
Click to collapse
Internal memory root folder, not /
Thank you! Updating as we speak :fingers-crossed:
Sahilsinghlodhi said:
There are two files, please flash the smaller one first via any of the method mentioned, and then the larger.
Click to expand...
Click to collapse
Yes, I know and thats what I tryied to do but unsuccessfully
---------- Post added at 01:30 PM ---------- Previous post was at 01:24 PM ----------
czupyt said:
Seems the colleague is on SW older than 4.88B (which would be the update from May), therefore he cannot use ADB sideload directly.
Click to expand...
Click to collapse
hikari_calyx said:
So updates from 488B to 488K need to be uploaded.
Click to expand...
Click to collapse
After that error, I donwloaded the updates from June to november which someone else's uploaded to his gdrive but I got the same error when tried to update via sideload
Hey,
I have a question I've rooted my OP7 Pro but i have an software update.
How do i update my software without losing my root?
There's a million and one threads about doing so. A simple search will show you
hallo dare said:
There's a million and one threads about doing so. A simple search will show you
Click to expand...
Click to collapse
+1
But FWIW, my process is the following (assuming you are on stock OOS)
Download full OTA zip and place it in root of sdcard
Go to system updates inside of settings and choose local upgrade
Let the update finish
Install TWRP retention in Magisk if you have TWRP and want to keep it
Install Magisk to inactive slot
Reboot
Install custom kernel if you have one
If you are on a custom ROM, I'm still trying to figure that out as I can't seem to find a way to update without factory resetting just yet.
Hello,
my oneplus 7 is rooted with magisk and has TWRP as custom recovery installed.
With the release of Android 10 closing in, would I be able to update to the new Android via the normal update process, or do I have to do something else in order to get that?
zloboh said:
Hello,
my oneplus 7 is rooted with magisk and has TWRP as custom recovery installed.
With the release of Android 10 closing in, would I be able to update to the new Android via the normal update process, or do I have to do something else in order to get that?
Click to expand...
Click to collapse
Yes, local update, data will be not erased, but make backups: https://forum.xda-developers.com/on...7-repo-oxygen-os-builds-t3937152/post80177128
But this is only for non rooted phones with locked bootloader, but sure if the current twrp will work.
zloboh said:
Hello,
my oneplus 7 is rooted with magisk and has TWRP as custom recovery installed.
With the release of Android 10 closing in, would I be able to update to the new Android via the normal update process, or do I have to do something else in order to get that?
Click to expand...
Click to collapse
Yes it's possible. Follow my guide to get TWRP to work also.
https://forum.xda-developers.com/oneplus-7/how-to/guide-how-to-flash-android-10-twrp-t3964131