I have rooted my mobile, and safteynet is success, Device is also showing certified in play store settings but i'm unable to update google play system update in security status in settings.
Its showing update available but when I try to do it, asks me to reboot to complete the installation and when I do so it reboots twice and update doesn't happens. Currently its on April 1, 2021.
Anyone?
RavzsTez said:
Anyone?
Click to expand...
Click to collapse
Screenshots? (Make it English, I don't understand Hindi)
I don't really get what you mean.
Security update is not through Playstore.
The ROM provider has to update it.
My bad, I'm out-dated.
MIUI OTA update cannot be done when you have root.
Play service should be auto-updated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
RavzsTez said:
View attachment 5309021
Click to expand...
Click to collapse
Did you try uninstall Magisk, reboot and see if it can update?
I found some reddit having same issues. They had miui 12 android 10.
https://www.reddit.com/r/Xiaomi/comments/khkf3c
If you don't want to uninstall Magisk or factory reset, you can try as here:
https://forum.xda-developers.com/t/...ate-manually-on-any-android-phone-10.4197723/
If you had uninstall Magisk, reboot, but it still cannot update, then you might need to try factory reset.
If factory reset and no magisk installed still won't have this Google Play system update installed, then it's MIUI's fault.
RavzsTez said:
I have rooted my mobile, and safteynet is success, Device is also showing certified in play store settings but i'm unable to update google play system update in security status in settings.
Its showing update available but when I try to do it, asks me to reboot to complete the installation and when I do so it reboots twice and update doesn't happens. Currently its on April 1, 2021.
Click to expand...
Click to collapse
April might be the latest available. I just checked and had March update and after update and restart it is now April and doesn't offer updates
pl1992aw said:
Did you try uninstall Magisk, reboot and see if it can update?
I found some reddit having same issues. They had miui 12 android 10.
https://www.reddit.com/r/Xiaomi/comments/khkf3c
If you don't want to uninstall Magisk or factory reset, you can try as here:
https://forum.xda-developers.com/t/...ate-manually-on-any-android-phone-10.4197723/
If you had uninstall Magisk, reboot, but it still cannot update, then you might need to try factory reset.
If factory reset and no magisk installed still won't have this Google Play system update installed, then it's MIUI's fault.
Click to expand...
Click to collapse
A) I tried this app already, it just changes the date and that too without any reboot. If we download update from phone it requires reboot where as this app just installed and date changed and app disappeared without reboot. Previously it was march, after installing it went to April but still the same update is showing.
B) Uninstalling magisk means just removing the app or complete unrooting the device?
RavzsTez said:
A) I tried this app already, it just changes the date and that too without any reboot. If we download update from phone it requires reboot where as this app just installed and date changed and app disappeared without reboot. Previously it was march, after installing it went to April but still the same update is showing.
B) Uninstalling magisk means just removing the app or complete unrooting the device?
Click to expand...
Click to collapse
I checked the security update in ArrowOS, it's on May 5th, so there's sure an update.
A) I checked the app on that website I provided, and they had only the April update, so you don't find anything changing.
B) I mean unrooting. Removing the app only but there's still something modified in the boot partition by Magisk.
pl1992aw said:
I checked the security update in ArrowOS, it's on May 5th, so there's sure an update.
A) I checked the app on that website I provided, and they had only the April update, so you don't find anything changing.
B) I mean unrooting. Removing the app only but there's still something modified in the boot partition by Magisk.
Click to expand...
Click to collapse
So unrooting and updating is the only option, but if I unroot then device shows not certified and not able to login into any google services and hence cant update that also
RavzsTez said:
So unrooting and updating is the only option, but if I unroot then device shows not certified and not able to login into any google services and hence cant update that also
Click to expand...
Click to collapse
If unrooting is problematic for you, then stay with the April 1st security.
Until the apk website provide a newer update, then you can use it.
Or maybe you can ask ArrowOS if they have an APK for you to install it manually.
Thank for clearing my doubt
RavzsTez said:
Thank for clearing my doubt
Click to expand...
Click to collapse
There's Magisk update, v23.0.
Before try flashing MIUI by Xiaomi.eu, you can try Magisk v23.0 and see if it will allow the security update, maybe it will work.
If you are already on Magisk v23.0, then ignore this reply.
pl1992aw said:
There's Magisk update, v23.0.
Before try flashing MIUI by Xiaomi.eu, you can try Magisk v23.0 and see if it will allow the security update, maybe it will work.
If you are already on Magisk v23.0, then ignore this reply.
Click to expand...
Click to collapse
I'm already on v23 , and even I thought the same thing like u said to try Xiaomi.eu.
But I have some doubts on that rom
1- can I get ota updates
2- should I have stock recovery or twrp for updating ota
3- consider after installing ota will the custom recovery be gone?
4- This EU rom installing for first time on X3 pro, can I install using twrp or I need flash tool and EU fastboot rom?
5- currently any custom recovery is not able to read internal files when I'm in recovery mode, why is this so? Is it my issue or for everyone?
6- If point 6 is true then how to install the rom? Even if I place rom in root folder it's not showing in recovery
7- if I get ota then is it just the update I receive or complete rom file I need to download again?
8- will I need to format everytime for every ota update?
RavzsTez said:
Thank for clearing my doubt
Click to expand...
Click to collapse
Thought of another way to try.
Press the "download & install" in security update.
You said then it tells you to reboot. Don't reboot yet.
Go into Magisk and uninstall Magisk.
After Magisk said it's uninstalled, then you press reboot.
So you get the system planned to install the security update after reboot, and have Magisk uninstalled.
See if this helps.
RavzsTez said:
I'm already on v23 , and even I thought the same thing like u said to try Xiaomi.eu.
But I have some doubts on that rom
1- can I get ota updates
2- should I have stock recovery or twrp for updating ota
3- consider after installing ota will the custom recovery be gone?
4- This EU rom installing for first time on X3 pro, can I install using twrp or I need flash tool and EU fastboot rom?
5- currently any custom recovery is not able to read internal files when I'm in recovery mode, why is this so? Is it my issue or for everyone?
6- If point 6 is true then how to install the rom? Even if I place rom in root folder it's not showing in recovery
7- if I get ota then is it just the update I receive or complete rom file I need to download again?
8- will I need to format everytime for every ota update?
Click to expand...
Click to collapse
1. Yes you'll get ota
2. Stay with twrp
3. Twrp stays
4. You can install miui eu with twrp but may requires format data. You could try dirty flash but expect issues
5. Yes it's normal because of data encryption. Not just you. But the latest twrp by nebrassy can decrypt and mount data properly
6. You can use sd card or otg
7. Updater handles it
8. No unless specifically being told to
pl1992aw said:
Thought of another way to try.
Press the "download & install" in security update.
You said then it tells you to reboot. Don't reboot yet.
Go into Magisk and uninstall Magisk.
After Magisk said it's uninstalled, then you press reboot.
So you get the system planned to install the security update after reboot, and have Magisk uninstalled.
See if this helps.
Click to expand...
Click to collapse
I'll try this but, I want to flash EU rom and try it out
xelrix said:
1. Yes you'll get ota
2. Stay with twrp
3. Twrp stays
4. You can install miui eu with twrp but may requires format data. You could try dirty flash but expect issues
5. Yes it's normal because of data encryption. Not just you. But the latest twrp by nebrassy can decrypt and mount data properly
6. You can use sd card or otg
7. Updater handles it
8. No unless specifically being told to
Click to expand...
Click to collapse
So EU rom has inbuilt custom recovery? If so what is the name of recovery it has?
Also will the device be certified without rooting? like pass safteynet and google services able to login?
I'm currently on nebrassy recovery , but still unable to read system files when I'm in recovery mode
RavzsTez said:
So EU rom has inbuilt custom recovery? If so what is the name of recovery it has?
Also will the device be certified without rooting? like pass safteynet and google services able to login?
I'm currently on nebrassy recovery , but still unable to read system files when I'm in recovery mode
Click to expand...
Click to collapse
No it doesn't have its own custom recovery.
Yes it will be certified oob.
Try setting up a pin code. On start up, it would attempt to decrypt by asking you to put in pin code.
xelrix said:
No it doesn't have its own custom recovery.
Yes it will be certified oob.
Try setting up a pin code. On start up, it would attempt to decrypt by asking you to put in pin code.
Click to expand...
Click to collapse
Or should i use Disable Force encryption? Will there be any issue if i use that?
Also please share the file
pl1992aw said:
Thought of another way to try.
Press the "download & install" in security update.
You said then it tells you to reboot. Don't reboot yet.
Go into Magisk and uninstall Magisk.
After Magisk said it's uninstalled, then you press reboot.
So you get the system planned to install the security update after reboot, and have Magisk uninstalled.
See if this helps.
Click to expand...
Click to collapse
Currently which custom recovery is better for installing custom Rom?
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank you @shunjou for helping RS988 to go official!
This is the official support thread for TWRP for RS988.
Installation from Stock:
**If your bootloader isn't already unlocked, go to the LG Developer website. You'll need to create an account. You can get the necessary ADB and fastboot tools from the Android SDK Platform Tools.**
If you wish to flash a stock ROM, you MUST flash a root .zip such as SuperSU to disable dm-verity and storage encryption! If you later decide to install a custom ROM, and didn't disable dm-verity on stock, you will have to COMPLETELY FORMAT your internal storage. Don't risk it.
1. Reboot into the bootloader with the command "adb reboot bootloader" and issue the command "fastboot flash recovery twrp-x.x.x-x_rs988.img", replacing "twrp.x.x.x..." with the location of the TWRP image on your drive.
2. Once it is done writing the image and says "finished," detach all power sources and remove the battery. This step is important—if you reboot into the system instead, TWRP will be overwritten by the stock recovery.
3. Reinsert the battery. Then start the phone, holding down both the Volume Down and Power button. When the LG logo appears, quickly release and re-press the Power button, continuing to hold Volume Down. This should bring you to a Factory Data Reset screen.
4. Confirm "Yes" on the two prompts (don't worry, no data will be deleted—we've overwritten the stock recovery) and you will be in TWRP.
Make sure to follow these steps as written, and make backups if necessary. You wouldn't want to risk saying "Yes" and actually wipe your data, right?
Click to expand...
Click to collapse
Working:
It works. If there are any problems, report them here.
Click to expand...
Click to collapse
Downloads:
Builds may be downloaded from the TWRP website.
Production builds: twrp.me/lg/lgg5rs988.html.
Test builds will depend on the current version of TWRP. For example, for v3.2.3.0 : http://build.twrp.me/twrp-3.2.3-0-rs988.img
Click to expand...
Click to collapse
XDA:DevDB Information
[OFFICIAL] TWRP 3.3.1-0 for LG G5 RS988, Tool/Utility for the LG G5
Contributors
NextDroid, shunjou
Source Code: https://github.com/TeamWin/android_device_lge_rs988
Version Information
Status: Stable
Created 2018-06-14
Last Updated 2019-06-11
Reserved?
Encryption not working for Linage 15.1
If you wish to flash a stock ROM, you MUST flash a root .zip such as SuperSU to disable dm-verity and storage encryption! If you later decide to install a custom ROM, and didn't disable dm-verity on stock, you will have to COMPLETELY FORMAT your internal storage. Don't risk it.
Click to expand...
Click to collapse
@NextDroid, Can you elaborate on this a little more? I'm not sure I fully understand.
Do you mean if you're on a stock ROM, you should root your device by flashing a root .zip file (magisk/supersu) to disable dm-verity and storage encryption before you install a custom ROM?
I just unlocked the bootloader and installed this version of TWRP on my RS988. I also installed x86cpu's unofficial 15.1 lineageOS ROM.
What I did was:
1. Unlock the bootloader
2. Installed TWRP
3. *Flashed SuperSU zip
4. Installed LineageOS/Gapps
*I think I may have flashed the wrong file for SuperSU because I tried flashing the same SuperSU .zip file after installing LineageOS and it didn't appear to do anything. Apps weren't giving me root access and there was no SuperSU app in my app drawer. I fear that my device wasn't actually rooted before installing LineageOS. Am I screwed? What do you mean that you will have to format your internal storage?
The SuperSU zip file I flashed was: UPDATE-SuperSU-v2.82-20170528234214
Sorry, I'm not the most educated in this kind of stuff. But everything as of now seems to be working fine. TWRP functions properly. I have since installed magisk and my device appears to be properly rooted. LineageOS 15.1 is working with no issues so far.
djskribbles said:
@NextDroid, Can you elaborate on this a little more? I'm not sure I fully understand.
Do you mean if you're on a stock ROM, you should root your device by flashing a root .zip file (magisk/supersu) to disable dm-verity and storage encryption before you install a custom ROM?
I just unlocked the bootloader and installed this version of TWRP on my RS988. I also installed x86cpu's unofficial 15.1 lineageOS ROM.
What I did was:
1. Unlock the bootloader
2. Installed TWRP
3. *Flashed SuperSU zip
4. Installed LineageOS/Gapps
*I think I may have flashed the wrong file for SuperSU because I tried flashing the same SuperSU .zip file after installing LineageOS and it didn't appear to do anything. Apps weren't giving me root access and there was no SuperSU app in my app drawer. I fear that my device wasn't actually rooted before installing LineageOS. Am I screwed? What do you mean that you will have to format your internal storage?
The SuperSU zip file I flashed was: UPDATE-SuperSU-v2.82-20170528234214
Sorry, I'm not the most educated in this kind of stuff. But everything as of now seems to be working fine. TWRP functions properly. I have since installed magisk and my device appears to be properly rooted. LineageOS 15.1 is working with no issues so far.
Click to expand...
Click to collapse
Hey @djskribbles,
As I prefaced them, these instructions only apply when you wish to flash a stock ROM. This implies that you are coming from a custom ROM. The current LG stock ROMs, when flashed, encrypt the internal storage, and TWRP is currently not able to decrypt it. This is why one should flash Magisk to disable storage encryption beforehand.
Also, you'll be better off if you use Magisk instead of SuperSU. Flash Magisk before LineageOS, because the script used to flash it automatically wipes the /system partition, which is where SuperSU, for example, makes its changes to enable root access.
NextDroid said:
As I prefaced them, these instructions only apply when you wish to flash a stock ROM. This implies that you are coming from a custom ROM. The current LG stock ROMs, when flashed, encrypt the internal storage, and TWRP is currently not able to decrypt it. This is why one should flash Magisk to disable storage encryption beforehand.
Click to expand...
Click to collapse
Actually, decryption should be working for stock now since the last builds. At least that's what was confirmed by someone that made me realize that building with omni 8 broke the old decryption fix. I think someone else mentioned cm14.1 worked too, so any nougat rom should be fine.
The issue now, as mentioned by x86cpu above, is that decryption isn't working with oreo roms. This seems common for a large number of devices (eg 1, 2, 3). It looks like codeworkx's fix for the zl1 here might resolve it, though I haven't tried it since I'm not currently able to test decryption myself.
shunjou said:
Actually, decryption should be working for stock now since the last builds. At least that's what was confirmed by someone that made me realize that building with omni 8 broke the old decryption fix. I think someone else mentioned cm14.1 worked too, so any nougat rom should be fine.
The issue now, as mentioned by x86cpu above, is that decryption isn't working with oreo roms. This seems common for a large number of devices (eg 1, 2, 3). It looks like codeworkx's fix for the zl1 here might resolve it, though I haven't tried it since I'm not currently able to test decryption myself.
Click to expand...
Click to collapse
All right, that's great to hear! I'll admit, I wasn't sure when I made that second comment... it had been a while since I'd heard anything on stock encryption.
I actually just finished cooking up a fix for Oreo encryption from work on the G6... I'll head over to zl1 if it doesn't work out.
We'll see what happens... --fingers crossed--
On the website the only TWRP version is 3.2.1-0. Is this different from the unofficial version I'm currently running? Has the wrong battery percentage bug been rectified?
Awkydee said:
On the website the only TWRP version is 3.2.1-0. Is this different from the unofficial version I'm currently running? Has the wrong battery percentage bug been rectified?
Click to expand...
Click to collapse
The latest unofficial build is the same as the official in terms of functionality. The battery life percentage should now display accurately.
NextDroid said:
The latest unofficial build is the same as the official in terms of functionality. The battery life percentage should now display accurately.
Click to expand...
Click to collapse
Yippie! Flashing now!
can i lock back the bootloader later to install oficial oreo when it comes?
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
bmanuelangel said:
can i lock back the bootloader later to install oficial oreo when it comes?
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
Click to expand...
Click to collapse
Are you referring to stock? Hopefully you won't need to re-lock the bootloader. When a .kdz package is published, hopefully @Unscedeo will make one of his COMPLETE INSTALLERS for it, and you could just flash it.
Hmm, I ought to keep up with this thread a bit more...
I've made some updates today and created a test build. Here is the link for anyone who wishes to test: http://build.twrp.me/twrp-3.2.3-0-rs988.img
Hello NextDroid, I noticed that the 3.3.1-0 version TWRP has been released.
According the the release's changes information provided by the TWRP website for the release:
https://twrp.me/site/update/2019/05/22/twrp-3.3.1-0-released.html said:
* Fix selinux issues during formatting - dianlujitao
...
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
Click to expand...
Click to collapse
I have noticed that while using x86cpu's UNOFFICIAL LineageOS-15.1 for G5 (lineage-15.1-20190516-X86CPU-rs988.zip) build, the SELinux status is usually "Enforcing", by sometimes changes to "Permissive". Do you think that the change would be due to the formatting bug corrected by this new TWRP build? If so, can a fix be applied after the buggy formatting from a previous TWRP release has happened and in such a way as to not have to reinstall the operating system? Are TWRP backups done raw, file-based, or differently?
Ascii3 said:
Hello NextDroid, I noticed that the 3.3.1-0 version TWRP has been released.
According the the release's changes information provided by the TWRP website for the release:
I have noticed that while using x86cpu's UNOFFICIAL LineageOS-15.1 for G5 (lineage-15.1-20190516-X86CPU-rs988.zip) build, the SELinux status is usually "Enforcing", by sometimes changes to "Permissive". Do you think that the change would be due to the formatting bug corrected by this new TWRP build? If so, can a fix be applied after the buggy formatting from a previous TWRP release has happened and in such a way as to not have to reinstall the operating system? Are TWRP backups done raw, file-based, or differently?
Click to expand...
Click to collapse
That is a good question. Actually, I am not sure. If you are willing to research that, report your findings to us here I'm interested to know.
I have been very busy for the past couple of months, but the G5 hasn't left my mind... I use it every day I'll see when I can update TWRP and my other builds.
Thanks for keeping us updated, @Ascii3!
NextDroid said:
That is a good question. Actually, I am not sure. If you are willing to research that, report your findings to us here I'm interested to know.
Click to expand...
Click to collapse
Maybe, if I have some time, myself. It is looking like something for August 2019.
NextDroid said:
I have been very busy for the past couple of months...I'll see when I can update TWRP and my other builds.
Click to expand...
Click to collapse
I am glad to see that you your are still around.
NextDroid said:
Thanks for keeping us updated, @Ascii3!
Click to expand...
Click to collapse
Sure.
Ascii3 said:
Are TWRP backups done raw, file-based, or differently?
Click to expand...
Click to collapse
I can and shall answer this question that I posed before:
TWRP allows for both RAW and file-based backups. Usually, however, the GUI provides few items for RAW backup; there is typically a backup option for "System Image" which is a RAW backup.
@NextDroid - I noticed that more recent versions of your TWRP do not have the System Image backup option despite it being in your older TWRP 3.2.3-0 build. The System Image backup functionality from TWRP 3.2.3-0 seemed to work OK. Did you deliberately exclude the "System Image" backup option? I the option missing for good reason?
Op started rolling 5.1.8 update
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ONEPLUS A6003 using Tapatalk
5.1.8 is intended for India
dgunn said:
5.1.8 is intended for India
Click to expand...
Click to collapse
no it says it "also contains the 5.1.7 changes for India" since there were issues with 5.1.7 update for India, it also includes the above changes for all other phones as well, so does not seem to be region specific
True.its for all regions.
Sent from my ONEPLUS A6003 using Tapatalk
So, these guys have an actual department dedicated to fixing community reported issues?
That's incredible.
Is it possible to download it without having to install it right away? Phone is rooted and don't want to lose root in case it starts installing.
Sent from my [device_name] using XDA-Developers Legacy app
Done
To those of you that updated and are rooted, can you confirm you're not sporadically losing root like 5.1.7 was doing?
slonn said:
Is it possible to download it without having to install it right away? Phone is rooted and don't want to lose root in case it starts installing.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
If it installs it won't be active until a reboot anyway, so as long as u don't reboot it won't change, even after install
I never lost root with 5.1.7 or any other 5.1.x rom (no twrp).
akxak said:
I never lost root with 5.1.7 or any other 5.1.x rom (no twrp).
Click to expand...
Click to collapse
users were reporting losing root / twrp with OTA's
im on 5.1.7, if i update to 5.1.8 via system update wont it remove my twrp and root and kernel?
afaik it does...
I applied the OTA (full due to root) with the system installer and reinstalled Magisk via Magisk Manager BEFORE rebooting.
I never used TWRP on the OP 6 and rooted with Magisk, I don't need it. When I got my OP6, there was no TWRP available.
Magisk patched the boot image.
After a smooth reboot, the system was updated and Magisk kept installed.
And yes, TWRP is lost when updating that way but can be reinstalled via Fastboot if it is needed.
so what the proper procedure on installing updates without getting wiped?
so far the most logical way of doing it is downloading the OTA
installing it via twrp
then install twrp.zip in twrp after update
then magisk, then kernel and boot.
If you need TWRP, yes. If not, install via system, reapply Magisk to inactive slot before rebooting and reboot.
I am not sure whether TWRP uses the A/B structure. The system updater does so if for any reason the update dies not start, the old working system remains available and will be booted.
The anxiety whether the system will come up after an update is gone for me... I crashed my OP5 applying the Oreo update and had to setup it up from scratch... while abroad on Christmas.
akxak said:
I never lost root with 5.1.7 or any other 5.1.x rom (no twrp).
Click to expand...
Click to collapse
Of course you lose root and TWRP as it loads a stock Boot.img which includes the OOS stock kernel and stick recovery. You will lose TWRP and Magisk, you have to reflash them.
@Eric214, you did read the original question #8 I was answering?
I answered on a sporadically loss of root, which meant for me after having root, it's suddenly gone without having installed something.
Don't jump on an answer without reading the question.
akxak said:
@Eric214, you did read the original question #8 I was answering?
I answered on a sporadically loss of root, which meant for me after having root, it's suddenly gone without having installed something.
Don't jump on an answer without reading the question.
Click to expand...
Click to collapse
Well I must have read the question wrong as it sounded like some were losing TWRP and root sporadically after the update. I didn't not read it I just took it another way... sorry for confusion
---------- Post added at 09:22 PM ---------- Previous post was at 09:19 PM ----------
Also, just as easy to just wait for Funk Wizard to post the official FULL zip on his thread and just Flash in TWRP. Last time I jumped the gun early I was on the beta 5.1.6 build but saw no issues whatsoever. I'll sit back this time.
Eric214 said:
Of course you lose root and TWRP as it loads a stock Boot.img which includes the OOS stock kernel and stick recovery. You will lose TWRP and Magisk, you have to reflash them.
Click to expand...
Click to collapse
If you only run Magisk and stock recovery, install the update, but before reboot , re-install Magisk to the other A/B side , then reboot. Then reboot, you'll have Magisk freshly installed.
This doesn't work for TWRP!
Sent from my Brain using my Keyboard
akxak said:
If you need TWRP, yes. If not, install via system, reapply Magisk to inactive slot before rebooting and reboot.
I am not sure whether TWRP uses the A/B structure. The system updater does so if for any reason the update dies not start, the old working system remains available and will be booted.
The anxiety whether the system will come up after an update is gone for me... I crashed my OP5 applying the Oreo update and had to setup it up from scratch... while abroad on Christmas.
Click to expand...
Click to collapse
you do appreciate the A/B structure when a flash goes wrong.
ill wait for the official zip to be flashed via TWRP before going ahead with it
virtyx said:
you do appreciate the A/B structure when a flash goes wrong.
ill wait for the official zip to be flashed via TWRP before going ahead with it
Click to expand...
Click to collapse
Of course I do... the Oreo update in December led to an unplanned factory reset of my OP 5 while abroad in Europe for Christmas. With A/B, this would not have happened because the present working OS (with Magisk/root) remains untouched and the update is installed in the other partition. If for any reason the updated OS is not coming up, the systems falls back and boots the previous (working) OS from where a new update or whatever measure can be initiated.
I wonder if (and if not why) TWRP does support that, installing the full update in the unsused slot (including TWRP itself and Magisk) and then boot that slot.
With these two partitions in use, you keep your phone working and avoid a soft brick. For the manufacturer it avoids trouble for the normal user in case an OTA fails...
Hi guys, is there any way to "uninstall" a pre-installed system update?? Currently at OS 5.1.11 but idk what happened suddenly it says "system update (OS 9.0.2) is installed, please reboot". So the last thing I want is to reboot, since I WILL lose my root, and afraid that my TWRP version not compatible for Android P. THANKS!
QUESTIONS
1) IF I were to reboot into recovery, make a backup and install that backup, will that help? Will the update be installed once I reboot into recovery or not? IF I am not mistaken, the updates are only applied when you reboot into the system., but I'm not sure now.
2) I already have a backup of my system but that is months ago. Would I be able to make a complete backup of today's sytem without applying the installed update?
3) Any other way to remove the pre-installed system update besides rebooting into recovery to do a factory reset and restore system settings?
4) Do I need to reinstall TWRP and MAGISK before applying the backup/system restore?
Thanks in advanced!
kahtsin said:
Hi guys, is there any way to "uninstall" a pre-installed system update?? Currently at OS 5.1.11 but idk what happened suddenly it says "system update (OS 9.0.2) is installed, please reboot". So the last thing I want is to reboot, since I WILL lose my root, and afraid that my TWRP version not compatible for Android P. THANKS!
QUESTIONS
1) IF I were to reboot into recovery, make a backup and install that backup, will that help? Will the update be installed once I reboot into recovery or not? IF I am not mistaken, the updates are only applied when you reboot into the system., but I'm not sure now.
2) I already have a backup of my system but that is months ago. Would I be able to make a complete backup of today's sytem without applying the installed update?
3) Any other way to remove the pre-installed system update besides rebooting into recovery to do a factory reset and restore system settings?
4) Do I need to reinstall TWRP and MAGISK before applying the backup/system restore?
Thanks in advanced!
Click to expand...
Click to collapse
If you are rooted then update will not get install; you need to flash full package through twrp
If you dont want to update to pie then flash oos5.1.11 full package through twrp use bluspark twrp
Suggestion: update to pie build
siddhrsh said:
If you are rooted then update will not get install; you need to flash full package through twrp
If you dont want to update to pie then flash oos5.1.11 full package through twrp use bluspark twrp
Suggestion: update to pie build
Click to expand...
Click to collapse
Hi, thanks for the reply.
I think the update WILL be installed after a reboot. And I don't want that, which is why I am avoiding any sort of reboot atm.
kahtsin said:
Hi, thanks for the reply.
I think the update WILL be installed after a reboot. And I don't want that, which is why I am avoiding any sort of reboot atm.
Click to expand...
Click to collapse
Update WILL NOT installed if you have pached boot image
You can flash oos 5.1.11 or 9.0.2 directly through twrp but use only blu_spark twrp
If you have installed magisk then go to magisk manager select uninstall then restore image after select install magisk second slot after ota
Process to install security updates on rooted Nokia 8
Download the Nokia 8 OTA zip files on your Computer from this link in the OTA folder https://bit.ly/nokia-nb1 (it's usually up to date)
Download the Nokia 8 latest FULL ROM OTA zip file on your Computer from this link in the OTA folder https://bit.ly/nokia-nb1 (usually with size above 1 GB, currently it is: NB1-5150-0-00WW-B03-update.zip 1.52 GB)
Connect the phone to the PC using the USB cable and enable USB debugging (after enabling developer options)
Verify connection and drivers are correct on your computer by using the following ADB/Fastboot command(minimal adb fastboot can be found here https://forum.xda-developers.com/showthread.php?t=2317790):
adb devices
Click to expand...
Click to collapse
If you see your device and ID then all good so far
Use the following adb command on your Computer
adb reboot bootloader
Click to expand...
Click to collapse
Alternative to the previous step, you can select ADB sideload from the stock recovery menu after booting into stock.
when the device reboots into bootloader / or ADB sideload is selected from recovery use this command on your computer:
adb sideload path_to_zip/FULL_ROM_OTA.zip
Click to expand...
Click to collapse
Once loaded, reboot using the command
adb reboot
Click to expand...
Click to collapse
Sideload the OTA updates you have downloaded in step 1 using the same process as before OR Update normally through android system settings. Keep updating and restarting until you have the latest update
Download the latest Nokia 8 Stock boot image file on your phone from this link in the STOCK BOOT folder https://bit.ly/nokia-nb1 (it's usually up to date)
Make sure you have the correct Stock boot image file for the the software version you have. (if you have May update, use May image, June update then use June Image, etc....)
Use magisk manager to root the boot image you just downloaded. Use the second option like in the photo below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Transfer the patched image file to your computer
Get back to bootloader (download mode) using any method or the below code (USB debugging on)
adb reboot bootloader
Click to expand...
Click to collapse
When in download mode, use the following command on your computer and take note of the result (in case something goes wrong)
fastboot getvar current-slot
Click to expand...
Click to collapse
Use the following command:
fastboot flash boot path_to_zip/patched_boot.img
Click to expand...
Click to collapse
Reboot
Enjoy
Wait one more month
Repeat
Tested scenarios:
Working on TA-1012 to get the Pie May 2019 update from April update
Working on TA-1012 to get the June 2019 update from May update
Working on TA-1012 to get back to latest rom (NB1-5150-0-00WW-B03-update) from April update
Working on TA-1012 to get back to latest rom (NB1-5150-0-00WW-B03-update) from May update
Working on TA-1012 to get back to latest rom (NB1-5150-0-00WW-B03-update) from June update
Screenshot, showing update using system settings to May update, after sideloading full ROM (NB1-5150-0-00WW-B03-update) from a rooted device on May update, proving downgrading works fine.
June files have been updated to the link: https://bit.ly/nokia-nb1
Thanks to Dorian Stoll
Well I got nowhere. The moment I reboot into bootloader, the device isn't visible in adb anymore, but only under "fastboot devices", so "adb sideload path-" fails because it can't find the device. What gives?
VonZigmas said:
Well I got nowhere. The moment I reboot into bootloader, the device isn't visible in adb anymore, but only under "fastboot devices", so "adb sideload path-" fails because it can't find the device. What gives?
Click to expand...
Click to collapse
Boot into recovery and select "apply update from adb" as shown in the photo below (not mine)
Kiwironic said:
Boot into recovery and select "apply update from adb" as shown in the photo below (not mine)
Click to expand...
Click to collapse
I'm still on TWRP at this stage. I can't get past step 7.
Hi guys,
is it necessary to sideload OTA updates? Can I just update the system in settings and then flash a rooted boot image corresponding to the update version?
VonZigmas said:
I'm still on TWRP at this stage. I can't get past step 7.
Click to expand...
Click to collapse
This is for people like me who are not able to run twrp on their phones. If you have twrp you should be able to flash the zip file easy. This guide assumes you have stock recovery
Update: confirmed working for July update as well.
I'm sorry if this seems dumb, but I'm kinda new to all of this. I have TWRP and now I want the July patch, how can I do it?
Update: I gave up and flashed stock recovery.
helscarthe said:
I'm sorry if this seems dumb, but I'm kinda new to all of this. I have TWRP and now I want the July patch, how can I do it?
Update: I gave up and flashed stock recovery.
Click to expand...
Click to collapse
In twrp it should be straight forward to flash a zip file which includes the update. Another option or if this fails, start sideload from twrp like in the following photos
Hi, links no longer working. Does anyone have working links for V5.15D ? I need stock boot image and OTA update to sideload. Thanks.
Unfortunately the phone has been abandoned by the developers. I have got myself a xiaomi 9t.
I'm sorry
Kiwironic said:
Unfortunately the phone has been abandoned by the developers. I have got myself a xiaomi 9t.
I'm sorry
Click to expand...
Click to collapse
It's ok thanks for your work on it!
Kiwironic said:
Unfortunately the phone has been abandoned by the developers. I have got myself a xiaomi 9t.
I'm sorry
Click to expand...
Click to collapse
Oh man, can you still get stock images or whatnot anywhere? I only need the least that will get me back to stock before I turn it in for warranty but not sure where to start.
Sorry man I relied on the other developer's repository so much that I can't offer any tools nor files. I can help you get to stock easy. As Nokia offers the original Rom on their website officially. I believe it can be found here
https://www.nokia.com/phones/en_int/betalabs
Register for beta labs then de register and download the latest firmware they offer you
Kiwironic said:
Sorry man I relied on the other developer's repository so much that I can't offer any tools nor files. I can help you get to stock easy. As Nokia offers the original Rom on their website officially. I believe it can be found here
https://www.nokia.com/phones/en_int/betalabs
Register for beta labs then de register and download the latest firmware they offer you
Click to expand...
Click to collapse
Hey, sorry for the late reply. I attempted to get back to stock via NOST and the 5150 image he provided https://forum.xda-developers.com/no...re-nokia-to-stock-t3867646/page3#post80627823 , but turns out I don't have critical unlocked and seem to have misplaced the unlock key. What can I do next?
VonZigmas said:
Hey, sorry for the late reply. I attempted to get back to stock via NOST and the 5150 image he provided https://forum.xda-developers.com/no...re-nokia-to-stock-t3867646/page3#post80627823 , but turns out I don't have critical unlocked and seem to have misplaced the unlock key. What can I do next?
Click to expand...
Click to collapse
Try unlocking again using the Nokia unlock Web page
Kiwironic said:
Try unlocking again using the Nokia unlock Web page
Click to expand...
Click to collapse
The web page requires a validation code that you get from the unlock app from your phone and as we know the app gives a nice "Device not support" if you try running it on Pie. Tested myself just in case.
Kiwironic said:
Try unlocking again using the Nokia unlock Web page
Click to expand...
Click to collapse
In the end I've decided to just go for it and see what happens. Shouldn't make things worse. Flashed the stock boot image for my security patch right on top of TWRP. The phone booted, but I still couldn't install updates. Tried flashing the next update (May) from both ADB and the SD card - failed with the same download state initialization error. Figured I may as well try the same but with the full .zip of my current OS version (April) and while it took pretty long, it finished with no issues and OTA's started rolling in without a hiccup. Surprisingly I didn't even lose any of my data in the process, which I was preparing for. I guess all that's left is to lock the bootloader?
Anyway thanks for the help!
My phone gave me the update download notification, but somehow cannot download the OTA - get an error each time. Anyone else on global has same problem?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Same problem here.
I have a T-mobile device converted to global & rooted. Could it have anything to do with this?
I'm on T-Mobile but bought from OnePlus directly. Same problem.
you have to uninstall magisk using "restore images", then install the OTA, then reinstall magisk to the inactive slot. it's failing the check on the boot partition if you're rooted
zander21510 said:
you have to uninstall magisk using "restore images", then install the OTA, then reinstall magisk to the inactive slot. it's failing the check on the boot partition if you're rooted
Click to expand...
Click to collapse
Thanks.
I think that the "Restore Images" option shows up when pressing the "Uninstall" in the Manager. Is it so?
Question: After OTA, can I just "Install" Magisk directly from the Magisk Manager?
Or would I need to patch the boot image and then flash it manually.
sjgoel said:
Thanks.
I think that the "Restore Images" option shows up when pressing the "Uninstall" in the Manager. Is it so?
Question: After OTA, can I just "Install" Magisk directly from the Magisk Manager?
Or would I need to patch the boot image and then flash it manually.
Click to expand...
Click to collapse
I tried the whole restore images and it failed so I tried to fastboot boot the unpatched 11.0.2.2. it booted but no wifi for. Whatever reason. I tried to download 11.0.4.4 on cellular but I don't have a stable signal so it kept failing. Can someone please post the 11.0.4.4 download image and post a link. It would be most appreciated. I cannot find any other way to download it.
zander21510 said:
you have to uninstall magisk using "restore images", then install the OTA, then reinstall magisk to the inactive slot. it's failing the check on the boot partition if you're rooted
Click to expand...
Click to collapse
Not that I don't believe you, but OnePlus never did this before for rooted users. It seems odd that they'd start doing this now.
BeardKing said:
Not that I don't believe you, but OnePlus never did this before for rooted users. It seems odd that they'd start doing this now.
Click to expand...
Click to collapse
It seems so. With an unpatched boot I can try to download, but with a patched boot it gives an error. I'm starting to lose my fondness for OnePlus.
BeardKing said:
Not that I don't believe you, but OnePlus never did this before for rooted users. It seems odd that they'd start doing this now.
Click to expand...
Click to collapse
Agree, never experienced this earlier.
It looks like an increment update (593MB) and will not download for rooted devices. I was able to update on an unrooted device but keep getting error message on mine which is rooted.
I guess we have to wait for the full update zip.
aieromon said:
It looks like an increment update (593MB) and will not download for rooted devices. I was able to update on an unrooted device but keep getting error message on mine which is rooted.
I guess we have to wait for the full update zip.
Click to expand...
Click to collapse
Yes, that was it. I had to MSM back to TMobile A10, unlock bootloader, convert to global A10, and then OTA to 11.0.4.4 - and then root.
aieromon said:
It looks like an increment update (593MB) and will not download for rooted devices. I was able to update on an unrooted device but keep getting error message on mine which is rooted.
I guess we have to wait for the full update zip.
Click to expand...
Click to collapse
Will wait for that full update. TY!
Disregard
If you're using the global version you can use these, 11.0.4.4.IN21AA global kernels patched and stock, tested on an IN2010.
Stock: https://www.davesanthology.com/publ....IN21AA/11.0.4.4.IN21AA_boot_stock_IN2010.img
MD5: https://www.davesanthology.com/publ....IN21AA/11.0.4.4.IN21AA_boot_stock_IN2010.md5
Patched: https://www.davesanthology.com/publ...1.0.4.4.IN21AA_boot_magisk_patched_IN2010.img
MD5: https://www.davesanthology.com/publ...1.0.4.4.IN21AA_boot_magisk_patched_IN2010.md5
For any other version you can d/load and install with a rooted device if you temporarily remove root, I've just done it this way. This assumes you have a stock and patched boot.img for your current ROM available (either in Magisk as a backup image or somewhere else). 4.4 wouldn't download whist I had the patched kernel installed, yes a new OP method.
1. Disable (no need to delete) your Magisk modules (to be safe)
2. Flash the stock boot image (for the ROM you're currently using) in fastboot:
Code:
fastboot flash boot <stock_boot>.img
3. Reboot and test, just to be sure (you shouldn't have root)
4. Boot from the patched (root) boot image (for the ROM you're currently using) in fastboot:
Code:
fastboot boot <patched_boot>.img
5. Now you'll have root back but the stock image will still be installed
6. Download the update, if it's taking a long time hit pause them resume a couple of times
7. Install the update and DO NOT REBOOT!
8. Open Magisk and install via direct method and DO NOT REBOOT!
9. Install Magisk again but this time use install to inactive slot method
10. Reboot when prompted
11. Reenable your Magisk modules
Full update is now available for download
aieromon said:
Full update is now available for download
Click to expand...
Click to collapse
Thanks.
Full update link: https://www.oneplus.com/support/softwareupgrade/details?code=PM1586920535300