Am I the only one on XT1900-7 stuck on the August update? I mean considering it's NOVEMBER now... it's pretty infuriating. My phone is locked (I suppose... if it ever was) btw.
TeamRainless said:
Am I the only one on XT1900-7 stuck on the August update? I mean considering it's NOVEMBER now... it's pretty infuriating. My phone is locked (I suppose... if it ever was) btw.
Click to expand...
Click to collapse
Same here waiting for it as I hope it fixes the Android Auto connectivity issue .... wonder why it takes so long
Italy, XT1900-7 RETEU stuck on 8.0 August patch here, too.
I hope they're working hard on Pie!
Just got the October update Today. Apparently it was released Oct 4th... we just didn't GET it.
Same here
TeamRainless said:
Just got the October update Today. Apparently it was released Oct 4th... we just didn't GET it.
Click to expand...
Click to collapse
Same here ... just started the installation, but I doubt it will be an 8.1 update based on numbers it's "just" a security update ... will see what it fixes and what will be broken I would love to have Android Auto working without errors
the same **** here
Can I install thiw wia TWPR because i am rooted and I can not update?
vidra said:
Can I install thiw wia TWPR because i am rooted and I can not update?
Click to expand...
Click to collapse
No, only with stock recovery and all stock partitions.
Comby_sk said:
No, only with stock recovery and all stock partitions.
Click to expand...
Click to collapse
So if I restore /boot I should be able to do it?
vidra said:
So if I restore /boot I should be able to do it?
Click to expand...
Click to collapse
And /system too. I do flash fastboot rom without erase userdata and than flash OTA from adb sideload. Check my guide in moto x4 thread.
Comby_sk said:
And /system too. I do flash fastboot rom without erase userdata and than flash OTA from adb sideload. Check my guide in moto x4 thread.
Click to expand...
Click to collapse
I cannot seem to find it, can you please link it?
vidra said:
I cannot seem to find it, can you please link it?
Click to expand...
Click to collapse
1. fastboot flash 8.0 OPWS27.57-40-22 (remove command "fastboot erase userdata" from script) - use this guide - after flash do not reboot to system
2. reboot to stock recovery (how to enter recovery) - install OTA from adb sideload - october 2018 OTA Blur_Version.27.301.32.payton.retail.en.US (save as zip)
3. reboot to system
if you want root gain
4. reboot to bootloader and use fastboot boot twrp.img
5. in twrp flash magisk and reboot to system
Comby_sk said:
1. fastboot flash 8.0 OPWS27.57-40-22 (remove command "fastboot erase userdata" from script) - use this guide - after flash do not reboot to system
2. reboot to stock recovery (how to enter recovery) - install OTA from adb sideload - october 2018 OTA Blur_Version.27.301.32.payton.retail.en.US (save as zip)
3. reboot to system
if you want root gain
4. reboot to bootloader and use fastboot boot twrp.img
5. in twrp flash magisk and reboot to system
Click to expand...
Click to collapse
I don't have the permission to download the OTA.
Comby_sk said:
1. fastboot flash 8.0 OPWS27.57-40-22 (remove command "fastboot erase userdata" from script) - use this guide - after flash do not reboot to system
2. reboot to stock recovery (how to enter recovery) - install OTA from adb sideload - october 2018 OTA Blur_Version.27.301.32.payton.retail.en.US (save as zip)
3. reboot to system
if you want root gain
4. reboot to bootloader and use fastboot boot twrp.img
5. in twrp flash magisk and reboot to system
Click to expand...
Click to collapse
I keep getting E: failed to mount / if i use sideload and failed yo unmount / if I try to install from sdcard in official recovery.
How do I solve that?
Reboot to bootloader and check software status is official.
Comby_sk said:
Reboot to bootloader and check software status is official.
Click to expand...
Click to collapse
I have falsed everything back but it says modified. Did I miss something?
If software status is modified, you cannot install OTA from SD card or from adb sidelod. You will try fastboot flash with "fastboot erase userdata", but you will lost all pictures, settings etc. I dont know if this helps.
Comby_sk said:
If software status is modified, you cannot install OTA from SD card or from adb sidelod. You will try fastboot flash with "fastboot erase userdata", but you will lost all pictures, settings etc. I dont know if this helps.
Click to expand...
Click to collapse
Yes, but shouldn't the flag get reset back to official when I restored factory firmware.
vidra said:
Yes, but shouldn't the flag get reset back to official when I restored factory firmware.
Click to expand...
Click to collapse
It does not.. it will remain modified.. even if you root.. the flag is triggered that helps the folks at Moto recognise the Device is tampered or something.. and I dont think there is a way to get it to official
Abhishek Survase said:
It does not.. it will remain modified.. even if you root.. the flag is triggered that helps the folks at Moto recognise the Device is tampered or something.. and I dont think there is a way to get it to official
Click to expand...
Click to collapse
So how con I install the OTA?
Related
Yesterday I recieved my phone and I unlocked the bootloader as well as rooted using CF. Today I tried to flash the OTA LRX21O (I'm on LNX07M) in TWRP but I'm getting the error "Package expects build fingerprint of google/shamu/shamu:5.0/LNX07M/1543455: user/release-keys or google/shamu/shamu : 5.0/LRX210/1570415 : user/release-keys; this device has Android/aosp_shamu/shamu:5.0LRX21M/dees_troy11191312:userdebug/test-keys"
What the heck does this mean? I also tried flashing back to stock recovery but it just ended up with an android image with "error" below it. I'm assuming it ran into the same problem. Do I need to wipe and start all over??
RandoTheKing said:
Yesterday I recieved my phone and I unlocked the bootloader as well as rooted using CF. Today I tried to flash LRX21O in TWRP but I'm getting the error "Package expects build fingerprint of google/shamu/shamu:5.0/LNX07M/1543455: user/release-keys or google/shamu/shamu : 5.0/LRX210/1570415 : user/release-keys; this device has Android/aosp_shamu/shamu:5.0LRX21M/dees_troy11191312:userdebug/test-keys"
What the heck does this mean? I also tried flashing back to stock recovery but it just ended up with an android image with "error" below it. I'm assuming it ran into the same problem. Do I need to wipe and start all over??
Click to expand...
Click to collapse
You can't install the OTA if you rooted. You'll probably need to just install the factory images via fastboot.
akellar said:
You can't install the OTA if you rooted. You'll probably need to just install the factory images via fastboot.
Click to expand...
Click to collapse
I thought you could always just flash them manually? When did this change? No point in rooting if I'm going to stay stock, it seems.
RandoTheKing said:
I thought you could always just flash them manually? When did this change? No point in rooting if I'm going to stay stock, it seems.
Click to expand...
Click to collapse
5.0 essentially makes it break OTA when you root/modify anything. This has been known for a bit now (which is why I downloaded the update before I did any rooting/unlocking on my device).
Dr Faustus said:
5.0 essentially makes it break OTA when you root/modify anything. This has been known for a bit now (which is why I downloaded the update before I did any rooting/unlocking on my device).
Click to expand...
Click to collapse
well what will you do for future updates? Full wipe?
RandoTheKing said:
well what will you do for future updates? Full wipe?
Click to expand...
Click to collapse
http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
not really - you can just flash the "old" stock system image file and then install the update (or just flash the "new" system file)
Dr Faustus said:
5.0 essentially makes it break OTA when you root/modify anything. This has been known for a bit now (which is why I downloaded the update before I did any rooting/unlocking on my device).
Click to expand...
Click to collapse
jj14 said:
http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
not really - you can just flash the "old" stock system image file and then install the update (or just flash the "new" system file)
Click to expand...
Click to collapse
Any instructions on how to do that? I'm assuming I can still get the update that way
RandoTheKing said:
Any instructions on how to do that? I'm assuming I can still get the update that way
Click to expand...
Click to collapse
It should be the same as the "back to stock" process
Download new (or old) factory images
Unzip and extract the IMG files
Take nandroid backup on phone
Reboot to recovery
Connect to PC (assuming drivers are installed)
Use fastboot to flash the necessary images
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
Edit - flash the cache.img instead of just erasing cache
I had trouble flashing the factory image initially. I kept getting an error so I used this method and it worked perfectly. Hope it helps. http://www.ibtimes.co.uk/how-fix-er...roid-5-0-factory-images-nexus-devices-1474865
So i am root and have done a bit of work on my Nexus 6 (changing system sounds, setting it up and a few other things) If i want to install LRX21O, what is the step by step to do that and after i install it if i do a Nandroid Backup, can i restore the backup on LRX21O? I am currently on LNX07M.
I am curious as well. Also do you happen to have a link to the file to just update.?
EDIT... Found it. Will flash when home
Sent from my Nexus 6 using XDA Free mobile app
jj14 said:
It should be the same as the "back to stock" process
Download new (or old) factory images
Unzip and extract the IMG files
Take nandroid backup on phone
Reboot to recovery
Connect to PC (assuming drivers are installed)
Use fastboot to flash the necessary images
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
Click to expand...
Click to collapse
Should that be `fastboot format cache`?
jm77 said:
Should that be `fastboot format cache`?
Click to expand...
Click to collapse
Actually, you should just flash the cache.img
jj14 said:
It should be the same as the "back to stock" process
Download new (or old) factory images
Unzip and extract the IMG files
Take nandroid backup on phone
Reboot to recovery
Connect to PC (assuming drivers are installed)
Use fastboot to flash the necessary images
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
You don't reboot into recovery if you are using fas boot. You boot into boot loader at least that's how I've done it on every Nexus that I've had.
Edit - flash the cache.img instead of just erasing cache
Click to expand...
Click to collapse
jm77 said:
Should that be `fastboot format cache`?
Click to expand...
Click to collapse
You can use both commands to first format, then flash the new one it doesn't really matter. I've used both methods
jj14 said:
Actually, you should just flash the cache.img
Click to expand...
Click to collapse
6.0.0 (MRA58N) for the Nexus 5 @ https://developers.google.com/android/nexus/images?hl=en
Reddit: https://www.reddit.com/r/Android/comments/3r95t2/android_60_november_security_update_images_are_out/
EDIT: Details at https://groups.google.com/forum/#!topic/android-security-updates/n1aw2MGce4E
So OTA usually comes out days after??
Sent from my Nexus 5 using XDA Free mobile app
I know this is just a security update, but can anyone confirm that the file transfer via USB MTP is working flawlessly?
Unlike this? ---> http://forum.xda-developers.com/google-nexus-5/help/considering-android-6-0-mtp-desktop-pc-t3218687
sutobe said:
I know this is just a security update, but can anyone confirm that the file transfer via USB MTP is working flawlessly?
Unlike this? ---> http://forum.xda-developers.com/google-nexus-5/help/considering-android-6-0-mtp-desktop-pc-t3218687
Click to expand...
Click to collapse
I've personally had no issues with the first 6.0 build on Windows 10 Pro x64, although only ever tried small files (<300MB)
Ok I made a Nandroid and installed 6.0 afterwards. File transfer worked for me now (don't know why it was so faulty before).....but there is still the thing with TWRP and TItanium Backup folders not showing up in Windows Explorer.
If I have a TWRP and / or Titanium Backup folder saved on my desktop's harddrive and want to move it to the phone's SD card the process fails while telling me that the folder already excists....but I can only see them via the phone's file explorer.
That means it is not impossible to move your backed up files to the SD card, it is just terribly awful. Always switch to MTP everytime you reconnect the phone with USB, then rename and move the backup-folders to the SD card and move their content to the proper backup folders (which you can't see in Windows) via a phone explorer.........who at Google had that great idea?
Any success rooting it? I tried the CF-Autoroot beta and last version of Chainfire's modified kernel, but got "no sim" errors.
FreemanAMG said:
Any success rooting it? I tried the CF-Autoroot beta and last version of Chainfire's modified kernel, but got "no sim" errors.
Click to expand...
Click to collapse
Yes. Modified boot.img attached in SuperSU beta thread... No problems.
GROGG88 said:
Yes. Modified boot.img attached in SuperSU beta thread... No problems.
Click to expand...
Click to collapse
Do you have a link? I do have the files from the first marshmallow release, But I'm not sure if you are talking about the latest SuperSU "systemless" beta
FreemanAMG said:
Do you have a link? I do have the files from the first marshmallow release, But I'm not sure if you are talking about the latest SuperSU "systemless" beta
Click to expand...
Click to collapse
I attached it in one of the last couple pages.
OTA failed for me. Using TWRP
fakitol said:
OTA failed for me. Using TWRP
Click to expand...
Click to collapse
Why do we keep having to repeat this?
You CAN NOT apply an OTA if you have modified the system in any way and/or you're using a different recovery. You can be unlocked. You can not be rooted. You can not apply an OTA via TWRP.
Yaz75 said:
Why do we keep having to repeat this?
You CAN NOT apply an OTA if you have modified the system in any way and/or you're using a different recovery. You can be unlocked. You can not be rooted. You can not apply an OTA via TWRP.
Click to expand...
Click to collapse
Because people are lazy and stupid at the same time often.
Sent from my Nexus 5 using Tapatalk
I got the security notification update but I have TWRP installed. I used NRT to Flash stock and unroot so am now down to a standard Nexus 5 with unlocked bootloader. I entered receovery mode and wiped cache for just in case then I tried the OTA install again but get no further than the message rebooting now. After a while it goes back to the restart and install message. Checked system and it shows October update. Any ideas what I can do. Trying to avoid wiping the phone, locking bootloader etc.
KC57 said:
I got the security notification update but I have TWRP installed. I used NRT to Flash stock and unroot so am now down to a standard Nexus 5 with unlocked bootloader. I entered receovery mode and wiped cache for just in case then I tried the OTA install again but get no further than the message rebooting now. After a while it goes back to the restart and install message. Checked system and it shows October update. Any ideas what I can do. Trying to avoid wiping the phone, locking bootloader etc.
Click to expand...
Click to collapse
Just flash the factory image but leave out the userdata.img file
EddyOS said:
Just flash the factory image but leave out the userdata.img file
Click to expand...
Click to collapse
Going to show my Noob quals here, which factory image, the security update? if so where would I find that and can I flash using NRT. Not a technology thicko but have only flashed images with NRT to now, did manage TWRP using ADB but that was a trial.
KC57 said:
Going to show my Noob quals here, which factory image, the security update? if so where would I find that and can I flash using NRT. Not a technology thicko but have only flashed images with NRT to now, did manage TWRP using ADB but that was a trial.
Click to expand...
Click to collapse
Easiest one is to use the latest MRA58N and then you've got the latest version but if you wanna use the previous one and then apply the OTA (to make sure it works) then you can do that as well. As for flashing it, just manually flash each image in fastboot but leave the userdata.img (as that will wipe your files). I do it in this order...
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
fastboot format cache
fastboot reboot
That should do the job
Yaz75 said:
Why do we keep having to repeat this?
You CAN NOT apply an OTA if you have modified the system in any way and/or you're using a different recovery. You can be unlocked. You can not be rooted. You can not apply an OTA via TWRP.
Click to expand...
Click to collapse
Apologies for what is probably a dumb question but is there an easy repo of the contents of the OTA updates in flashable zip format?
EddyOS said:
Easiest one is to use the latest MRA58N and then you've got the latest version but if you wanna use the previous one and then apply the OTA (to make sure it works) then you can do that as well. As for flashing it, just manually flash each image in fastboot but leave the userdata.img (as that will wipe your files). I do it in this order...
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
fastboot format cache
fastboot reboot
That should do the job
Click to expand...
Click to collapse
So does doing this equate almost to a "dirty flash" - i.e. I'm getting all the updates but not wiping any of my data/apps etc off the phone?
anyone a mirror for the 2,5 MB OTA file?
landwomble said:
So does doing this equate almost to a "dirty flash" - i.e. I'm getting all the updates but not wiping any of my data/apps etc off the phone?
Click to expand...
Click to collapse
Yes, but with official system files so you should be OK. Worst case scenario, backup data before doing anything in case you have to do a factory reset (e.g. if it shows 16GB on a 32GB device)
---------- Post added at 08:49 PM ---------- Previous post was at 08:49 PM ----------
hanschke said:
anyone a mirror for the 2,5 MB OTA file?
Click to expand...
Click to collapse
Don't need a mirror with the official Google server links - https://android.googleapis.com/pack...74e.signed-hammerhead-MRA58N-from-MRA58K1.zip
hi my nexus 6 its running 7.0 NBD90Z, and want to update to 7.1.1 march update
this is the 7.0 version im running https://forum.xda-developers.com/nexus-6/general/android-nougat-nbd90z-flashable-image-t3474572
can somebody tell me how to do it without losing data or root ?
thank you
agel1 said:
can somebody tell me how to do it without losing data or root ?
Click to expand...
Click to collapse
First root; flash TWRP-recovery; make a backup with TWRP; flash a stock ROM https://forum.xda-developers.com/showthread.php?p=59561445/; restore data; Unroot.
NLBeev said:
First root; flash TWRP-recovery; make a backup with TWRP; flash a stock ROM https://forum.xda-developers.com/showthread.php?p=59561445/; restore data; Unroot.
Click to expand...
Click to collapse
sorry dont understand
Im already rooted and with twrp installed
agel1 said:
hi my nexus 6 its running 7.0 NBD90Z, and want to update to 7.1.1 march update
this is the 7.0 version im running https://forum.xda-developers.com/nexus-6/general/android-nougat-nbd90z-flashable-image-t3474572
can somebody tell me how to do it without losing data or root ?
thank you
Click to expand...
Click to collapse
Download the factory image of the version you desire to end up on.
Unzip it, then unzip the folder contained in it, then in a terminal/cmd run:
Code:
fastboot flash bootloader bootloader-shamu-*.img
fastboot reboot-bootloader
fastboot flash radio radio-shamu-*.img
fastboot reboot-bootloader
cd shamu-*
fastboot flash boot boot.img
fastboot flash system system.img
Now, you said you wanted to retain root too, if that isn't the case, just run:
Code:
fastboot reboot
If you do still want root, download TWRP, cd to the Downloads directory, then either run:
Code:
fastboot boot twrp-3.1.0-0-shamu.img
if you want to keep the stock recovery
OR
Code:
fastboot flash recovery twrp-3.1.0-0-shamu.img
if you want to keep TWRP.
Now that you're on TWRP, just use file explorer to drag and drop the newest SuperSU zip (at the time of writing this, 2.79 is the latest stable, and SR3-2.79 is the latest beta) if you're on Windows or Linux, or use
Code:
adb push [I]nameofsupersu[/I].zip /sdcard/
.
Now reboot.
Have fun! It may take up to 15 minutes to boot (for dex-opting, and encrypting if you were decrypted and decided to re-encrypt), so don't interrupt that first boot process, just let it go. It will also need to "Optimize" all installed apps, so that could take a long while as well.
agel1 said:
sorry dont understand
Im already rooted and with twrp installed
Click to expand...
Click to collapse
Bad reading by me. Sorry.
Nevertheless you can upgrade to 7.1.1 by flashing the lite ROM of Danvdh.
There is a possibility that dirty flashing will cause reboot issue. Backup first and update your bootloader and radio before flashing the ROM.
There's a thread with flashable zips with latest bootloader/radio.
https://forum.xda-developers.com/showthread.php?p=59728002/
Latest TWRP: https://eu.dl.twrp.me/shamu
Why is everyone recommending the difficult ways???
Just download the OTA image from google and sideload it from your PC.
You don't even need TWRP, unloaded bootloader or root access to do it and you won't loose any data or settings.
More info and OTA images at https://developers.google.com/android/ota
So after an official way to do so Just unlocked my Nokia 8 bootloader.
I don't want to flash recovery as need system updates, so I tried booting to latest official twrp from fastboot "fastboot boot recovery.img" but it only take me to android logo and nothing happens. Any help regarding how to boot in twrp?
Also, is it okay to flash magisk with temporary twrp?
me too , just stuck there =(
you need to fastboot boot to even be able to install it anyway, but it seems to not be working for us that used the official unlock, either that or september update might be the problem
It works tho, I unlocked through official method and downgraded by switching slot a to slot b (search it up) then reboot ur phone you will see it's downgraded to the August update. Then boot the latest TWRP and follow the steps. It works, I assure you. Somehow TWRP is not compatible with the September patch.
iKillua said:
It works tho, I unlocked through official method and downgraded by switching slot a to slot b (search it up) then reboot ur phone you will see it's downgraded to the August update. Then boot the latest TWRP and follow the steps. It works, I assure you. Somehow TWRP is not compatible with the September patch.
Click to expand...
Click to collapse
How to check the current active slot?
fastboot - - set-active a
Will only this command do everything? Or do I need some firmware?
iKillua said:
It works tho, I unlocked through official method and downgraded by switching slot a to slot b (search it up) then reboot ur phone you will see it's downgraded to the August update. Then boot the latest TWRP and follow the steps. It works, I assure you. Somehow TWRP is not compatible with the September patch.
Click to expand...
Click to collapse
Hmmm i'm still on august , did not receive the september yet ( , but still can't boot , so i'm going to down to june by change the slot to a ( mine is b ) , thanks for the info , will try your way )
Sahilsinghlodhi said:
How to check the current active slot?
fastboot - - set-active a
Will only this command do everything? Or do I need some firmware?
Click to expand...
Click to collapse
you can check the current active slot by doing
fastboot getvar current-slot
emoklaga113 said:
Hmmm i'm still on august , did not receive the september yet ( , but still can't boot , so i'm going to down to june by change the slot to a ( mine is b ) , thanks for the info , will try your way )
Click to expand...
Click to collapse
After getting back to August patch it didn't boot for me directly but it did after entering fastboot mode from custom recovery.
1. Boot into Nokia recovery
2. Select reboot to fastboot
3. Use fastboot boot twrp.img
iKillua said:
you can check the current active slot by doing
fastboot getvar current-slot
Click to expand...
Click to collapse
Rooted with magisk ?
Though unable to update to September.(not able to Install), on stock Recovery.
Sahilsinghlodhi said:
So after an official way to do so Just unlocked my Nokia 8 bootloader.
I don't want to flash recovery as need system updates, so I tried booting to latest official twrp from fastboot "fastboot boot recovery.img" but it only take me to android logo and nothing happens. Any help regarding how to boot in twrp?
Also, is it okay to flash magisk with temporary twrp?
Click to expand...
Click to collapse
Just flash the official twrp on both slot, official or unofficial bl unlock works, then after flashing the twrp on both slot run cmd "fastboot reboot recovery" then it's done. You can now flash magisk.
---------- Post added at 04:03 PM ---------- Previous post was at 03:24 PM ----------
Lee Castro said:
Just flash the official twrp on both slot, official or unofficial bl unlock works, then after flashing the twrp on both slot run cmd "fastboot reboot recovery" then it's done. You can now flash magisk.
Click to expand...
Click to collapse
After unlocking the bootloader (official or unofficial bl unlock), run the cmd for flashing the official twrp "fastboot flash boot_a twrp-3.2.3-1-NB1.img" & "fastboot flash boot_b twrp-3.2.3-1-NB1.img" then after flashing run the cmd "fastboot reboot recovery", then flash magisk for rooting.
Sahilsinghlodhi said:
Rooted with magisk ?
Though unable to update to September.(not able to Install), on stock Recovery.
Click to expand...
Click to collapse
you need to update to september security patch then unlock your bootloader officially, flash the official twrp on both slots run cmd "fastboot reboot recovery" then install magisk.
Sent from my TA-1004 using XDA-Developers Legacy app
So, I rooted my device following this https://forum.xda-developers.com/nokia-8/how-to/guide-how-to-root-nokia-8-ability-to-t3848390, but I cannot update my nokia...
The only thing I did different was that I had to rollback my device (with this guide) to June update, and then proceed accordingly.
When I try to update now, I keep getting an error on the update: "Couldn't update. Installation problem".
Can someone please help me? I am ok with both manual or automatic updates, but I need to update.
You only need to flash the stock (untouched) version of the boot partition to the active slot with relevant patch, which is June version at your occasion. Go to this page: https://forum.xda-developers.com/nokia-8/development/nb01-stock-boot-imgs-fixing-wifi-t3854310
***
Edit: See my second post.
Also there is magisk uninstall feature, which you can restore the partition to stock and update and then magisk-root the inactive partition (newly installed system).
I have not upraded my phone, yet. That is, I didn't try anything I mentioned here.
Click to expand...
Click to collapse
Dr. Slump said:
You only need to flash the stock (untouched) version of the boot partition to the active slot with relevant patch, which is June version at your occasion. Go to this page: https://forum.xda-developers.com/nokia-8/development/nb01-stock-boot-imgs-fixing-wifi-t3854310
Click to expand...
Click to collapse
Thanks, I'm in the same situation, unlocked bootloader and rooted on the October patch, do I flash the stock Oct patch and then update via OTA?
Thanks!
vonManstein said:
Thanks, I'm in the same situation, unlocked bootloader and rooted on the October patch, do I flash the stock Oct patch and then update via OTA?
Thanks!
Click to expand...
Click to collapse
That is right. You are welcome.
Also there is magisk uninstall feature, which you can restore the partition to stock and update and then magisk-root the inactive partition (newly installed system).
I have not upraded my phone, yet. That is, I didn't try anything I mentioned here. You may verify the ideas by wandering at some topics like that:
https://forum.xda-developers.com/nokia-8/how-to/guide-how-to-root-nokia-8-ability-to-t3848390
Dr. Slump said:
You only need to flash the stock (untouched) version of the boot partition to the active slot with relevant patch, which is June version at your occasion. Go to this page: https://forum.xda-developers.com/nokia-8/development/nb01-stock-boot-imgs-fixing-wifi-t3854310
***
Edit: See my second post.
Click to expand...
Click to collapse
The magisk uninstall have not worked, the same error persists... I'm gonna try the first method you mentioned, and will be back with results, thanks!
Edit: also, could you please provide steps for doing that?
Not sure if supposed to do that through Nokia software, twrp or fastboot.
Thanks again
guideo said:
The magisk uninstall have not worked, the same error persists... I'm gonna try the first method you mentioned, and will be back with results, thanks!
Edit: also, could you please provide steps for doing that?
Not sure if supposed to do that through Nokia software, twrp or fastboot.
Thanks again
Click to expand...
Click to collapse
It is "fastboot flash". It seems OK. This is what I will do if magisk uninstall doesn't work for me. But, again, you should know that I have not tried this yet.
Also, if your plan is to upgrade to pie, AFAIK there is some preliminary problems with it. They are mentioned in relevant topics here. I think it is better to wait for a better version.
Dr. Slump said:
It is "fastboot flash". It seems OK. This is what I will do if magisk uninstall doesn't work for me. But, again, you should know that I have not tried this yet.
Also, if your plan is to upgrade to pie, AFAIK there is some preliminary problems with it. They are mentioned in relevant topics here. I think it is better to wait for a better version.
Click to expand...
Click to collapse
Hi, thanks for the help.
The command fastboot flash boot "june.img" worked, but now I can't turn on my WiFi... It turns on then off again on its own...
Im gonna tinker around a little with it, but probably be back on the 25th or 26th, due to xmas.
Thanks a lot and merry christmas to you
Worked with may patch...
I think that my device was trying to apply the June patch, and so it was in may patch.
Ive installed it and now the update is ongoing.
Gonna try to re-root it after the holidays
I'm not going to apply the pie update, gonna wait for a while.
Thanks a lot man! You saved my device :laugh:
guideo said:
Worked with may patch...
I think that my device was trying to apply the June patch, and so it was in may patch.
Ive installed it and now the update is ongoing.
Gonna try to re-root it after the holidays
I'm not going to apply the pie update, gonna wait for a while.
Thanks a lot man! You saved my device :laugh:
Click to expand...
Click to collapse
I just got to the september update (should have stopped in august), but now I cannot root my device... TWRP wont boot, neither the prerooted september image.
If you have any idea about this, I would really appreciate! Thanks!
guideo said:
I just got to the september update (should have stopped in august), but now I cannot root my device... TWRP wont boot, neither the prerooted september image.
If you have any idea about this, I would really appreciate! Thanks!
Click to expand...
Click to collapse
Thanks, marry christmas to you, too. TWRP won't work because there isn't a dedicated recovery partition anymore, it was patched into boot partition and wiped out with the flashing
If you are trying the prerooted boot image with "fastboot boot", it is broken after the august update. If not, maybe it is better to download the stock image to /sdcard and patch it with your latest magisk, later upload it to computer and "fastboot flash" it.
So guys any way to root official pie with december security patch?
nabil427 said:
So guys any way to root official pie with december security patch?
Click to expand...
Click to collapse
You can find a twrp-prepatched boot image for Pie + December Patch here: https://cloud.tmsp.io/s/nb1?path=/Boot Images/2018-12
Enter download mode and use fastboot to flash it into your active boot partition (either boot_a or boot_b, depending on the output of "fastboot getvar current-slot").
Then boot into recovery mode (using adb reboot recovery, or by shutting the phone down and pressing volume up while connecting it to the PC) and flash the Magisk installer .zip
THMSP said:
You can find a twrp-prepatched boot image for Pie + December Patch here: https://cloud.tmsp.io/s/nb1?path=/Boot Images/2018-12
Enter download mode and use fastboot to flash it into your active boot partition (either boot_a or boot_b, depending on the output of "fastboot getvar current-slot").
Then boot into recovery mode (using adb reboot recovery, or by shutting the phone down and pressing volume up while connecting it to the PC) and flash the Magisk installer .zip
Click to expand...
Click to collapse
Hi,
thank you for your help but i'm stuck in boot here are the commands I did:
C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot.exe getvar current-
slot
current-slot: b
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot.exe boot twrp-3.2.3
-1-NB1.img --slot=b
downloading 'boot.img'...
OKAY [ 0.127s]
booting...
OKAY [ 5.208s]
finished. total time: 5.337s
I've also tried to boot on TWRP 3.2.3-1 but same issue I could not boot onto it and then flash it.
Any Idea ?
Regards
>> Hi, never mind working OK thx
Dr. Slump said:
Thanks, marry christmas to you, too. TWRP won't work because there isn't a dedicated recovery partition anymore, it was patched into boot partition and wiped out with the flashing
If you are trying the prerooted boot image with "fastboot boot", it is broken after the august update. If not, maybe it is better to download the stock image to /sdcard and patch it with your latest magisk, later upload it to computer and "fastboot flash" it.
Click to expand...
Click to collapse
This worked for me with September boot. Just did what you said and then "fastboot flash boot patched_boot.img".
Thanks again