Database Info

[HOW-TO] Root Nokia 8 with Systemless Magisk

Reason for edit: Change title so more users can find this method since for now TWRP is working but not to root
Click to expand...
Click to collapse
Hello fellow XDA users,
On this post I'm going to explain how I got root on my own Nokia 8 TA-1004, please be patient because this is my first thread under any development section!!
I've been following all threads here on XDA and for the last few days its like a boom of new information, yesterday a Senior Member provided me with the Unlock Key generated with my IMEI1 and the phone's bootloader is now unlocked:
{
"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"
}
Now the next logical part I would be installing TWRP to flash the magisk flashable zip to the phone, but there is no TWRP built to our phones (old information, there is now an official TWRP build)..
To my surprise there is this thread that offers boot images already patched with root ( @nummerok are they patched under magisk?), I tried flashing first with:
Code:
fastboot boot NB1-0-484A-00WW-boot.img
But it did not worked, no matter what the installed Magisk Manager would not find the Magisk Module on the system.
Then I found out that some users were getting root but with the problem of losing wifi connectivity, that was found to be the fault of the phone having the March Security Patch (00WW_4_84A_SP01) while flashing the boot image of the phone with the February Security Patch (00WW_4_84A).
As of this new A-B partition scheme on Android, when your boot image does not pass dm-verity it restores the older version automatically (Am I right on this point?? can please someone confirm?!)
Since my phone WAS on the march patch I saw no other option but to wait someone to grab the march boot image to patch it Magisk Manager and get root.
Buut since my generation doesn't like to sit and wait I found that there was a way to roll back to the previous firmware!
What I did was, run this code below on adb to know which slot my phone was:
Code:
adb shell getprop ro.boot.slot_suffix
Then take note of the slot and run:
Code:
adb reboot bootloader
After the device starts up in Download Mode you need to switch to the other boot slot. Just run:
Code:
If you are currently on slot A, type this: [B][I]fastboot --set-active=_b[/I][/B]
Or on slot B type this: [B][I]fastboot --set-active=_a[/I][/B]
You should see something like this:
Code:
Setting current slot to 'a'... OKAY [ 0.046s] finished. total time: 0.046s
Now run the code below and cross your fingers!
Code:
fastboot reboot
Once the phone has booted, check in Settings/System/About Phone if your Android security patch level has downgraded to the February one and proceed to the next step.
I've downloaded the full NB1-484A-0-00WW-B03.nb0 firmware from @blackpanther0582 thread under the google drive link and extracted the boot image using the tool made by @heineken78 available over here (be sure to have lots of ram available for the unpack process :fingers-crossed.
With the file NB1-0-484A-00WW-boot.img at hand I've copied it to the Nokia 8 internal storage and ran Magisk Manager to patch it, follow instructions here under Via Magisk Manager (Only support v14.0+) part.
Now grab the patched_boot.img file provided by Magisk from the phone and save it (adb pull or whatever) to your pc and run these commands:
Code:
adb reboot bootloader
After the phone boots up in Download Mode run:
Code:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
fastboot reboot
With that done, after the boot you can open Magisk Manager to see it fully installed and later on install some root checker app just to be sure of the sucess of your rooting:
Split-screen to the rescue lol
This Nokia 8 is officially rooted but with the previous February patch and I'm itching to install the March OTA provided by @2WildFirE here, any thoughts on that? What about the official system update that still lists the 2018-03 security patch? Would any of which work?
And that is all for now folks!
I would like to thank @the_laser @heineken78 @topjohnwu @blackpanther0582 @nummerok and many others in this invaluable path to learning more about this phone and the Android system in general!
Good Luck!!

Reserved

Nice, this will help some people to understand.
Powered by Nokia 8 with open bootloader

2WildFirE said:
Nice, this will help some people to understand.
Click to expand...
Click to collapse
That's the idea @2WildFirE !
btw just to make things clear, the official system update is running for like 10 hours and it seems it's not going anywhere.. would I get success by doing the march update thru the zip you've found?

Yep was working fine here, to bring my wifi back, but lost root [emoji6] what we Really need is twrp and or a method to extract the boot.img from the *. Bin file included in the update zip.
Powered by Nokia 8 with open bootloader

I used your method, but it doesn't work.
When I type "fastboot --set-active=_a",it shows "fastboot usage". I try it fifth time, but it still. I haven't deal anythings about root Nokia8, is it the reason ?

contrahelix said:
I used your method, but it doesn't work.
When I type "fastboot --set-active=_a",it shows "fastboot usage". I try it fifth time, but it still. I haven't deal anythings about root Nokia8, is it the reason ?
Click to expand...
Click to collapse
It should work only if you have your bootloader unlocked @contrahelix
You might get it unlocked officially by Nokia or wait for an alternative method.
Also you should update your adb/fastboot tools, then you would get the right error message telling you about the still locked bootloader!

On this post I'm going to explain how I got root on my own Nokia 8 TA-1004, please be patient because this is my first thread under any development section!!
Click to expand...
Click to collapse
I have a TA-1012 i assume it won't work for me?

For everyone with unlocked bootloader, this is the method to root without TWRP !

Now that we have unlocked bootloaders, is it possible that this can be updated to simply use the latest image instead of rolling back? Or are we still rolling back...

Raithlin said:
Now that we have unlocked bootloaders, is it possible that this can be updated to simply use the latest image instead of rolling back? Or are we still rolling back...
Click to expand...
Click to collapse
Still have to rollback to official image.. you cannot upgrade with patched img unfortunately

As u have unlocked bootloader and installed magisk i have a question .
Is it worth to unlock bootloader and install magisk.......?
And one more any custom rom available for nokia8 ta1004.......?

شرا

GSI/DSU Flashing

How is the proper way of installing GSI images? I have tried TWRP method and Fastboot method, neither of them works. Is it even possible on this device?
Fastboot method gets error @ "fastboot erase system" (remote: Check device console)
BL Unlocked ofc and adb/fastboot is up to date as well drivers
TWRP - i lose all my partitions for some reason and have to MSM back to working state
GSI i tried https://developer.android.com/about/versions/12/gsi-release-notes#downloads
This is my first fully treble supported device and i actually do not know how A and B partitions behave while doing gsi/rom flashing. Perhaps someone can explain it?

ArletPDR said:
How is the proper way of installing GSI images? I have tried TWRP method and Fastboot method, neither of them works. Is it even possible on this device?
Fastboot method gets error @ "fastboot erase system" (remote: Check device console)
BL Unlocked ofc and adb/fastboot is up to date as well drivers
TWRP - i lose all my partitions for some reason and have to MSM back to working state
GSI i tried https://developer.android.com/about/versions/12/gsi-release-notes#downloads
This is my first fully treble supported device and i actually do not know how A and B partitions behave while doing gsi/rom flashing. Perhaps someone can explain it?
Click to expand...
Click to collapse
The 8T is not only an A/B device, it is also a virtual A/B device. I'd be very surprised if you could get a"normal" A/B GSI to boot on an 8T.
Virtual A/B Overview | Android Open Source Project
source.android.com

There is this Dynamic System Updates feature, i have used it earlier to test android 12 GSI
But now I'd ike to delete wherever those GSI's stored, so that i possibly can test other GSI there is
{
"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"
}

ArletPDR said:
There is this Dynamic System Updates feature, i have used it earlier to test android 12 GSI
But now I'd ike to delete wherever those GSI's stored, so that i possibly can test other GSI there is
View attachment 5374671
Click to expand...
Click to collapse
Click discard on the notification of dynamic system updates.
If no notification then the gsi is deleted

I did that in hopes that it clears this dsu dialog up from those that is there now, but no, they are still there and i can use them if i want. it's like they are stored somewhere? (i have no other GSI type file stored on my local storage btw)

ArletPDR said:
I did that in hopes that it clears this dsu dialog up from those that is there now, but no, they are still there and i can use them if i want. it's like they are stored somewhere? (i have no other GSI type file stored on my local storage btw)
Click to expand...
Click to collapse
Do you mean that the installation of the dsu is so fast that it is impossible to download a 3gb GSI in such a short time?

Well, i did not know that it requires internet connection, i always tough it uses file from local storage

ArletPDR said:
Well, i did not know that it requires internet connection, i always tough it uses file from local storage
Click to expand...
Click to collapse
It also occured to me, only takes a few minutes to install dynamic system.
To me though, when I discarded the GSI at that instant there will be a few gigabytes freed and that is a sign of the GSI deleted.

For me it takes a while tho
All the DSU magic happens in this folder

Tried deleting the gsi there?

It was empty before i started dsu installation, also i have no dsu install file on internal storage download folder, that proves the fact that is takes dsu file or filename from internet, because when i rebooted i was greeted with OOS, the same i have primarily installed, with only 4gb on internal storage, and i made screenshots there, but they're gone now.. obviously

LR7875 said:
Tried deleting the gsi there?
Click to expand...
Click to collapse
No i did not, discarding from notification panel did just that

Twrp and Android 10. Fastboot flash recovery command failed even though bootloader is unlocked

The only command prompt that seems to be working is fastboot flash boot twrp.img but when I type fastboot flash recovery the flash fails. I use Minimal ADB and Fastboot command prompt. The latest version too. I downgraded my android 11 to 10 successfully. I have no problems rooting magisk through ADB but why can't TWRP permenantly stick? How can I force it to stick as my main recovery no matter what rom I flash?

Crap. I did not mean to say android 11 on the topic title. Wish I could edit it. I meant to say Android 10. Sorry for the confusion. Any tips of how to retain twrp? Having problems with my unlocked pixel 4a.

This guide shows you how to get TWRP to stick:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com

P4a doesn't have a recovery partition anymore, recovery is part of the boot.img. That's why the fastboot cmd fails.

UltimateGamer83 said:
Crap. I did not mean to say android 11 on the topic title. Wish I could edit it. I meant to say Android 10. Sorry for the confusion. Any tips of how to retain twrp? Having problems with my unlocked pixel 4a.
Click to expand...
Click to collapse
You can't flash recovery on this phone. It's part of boot.img. Put the TWRP.img file in your internal storage of your phone. Flash the TWRP temporarily first. Fastboot boot TWRP.img. When TWRP boots, click install, then select install image. Choose your TWRP file and select install Ramdisk. Swipe to flash. TWRP will then be installed permanently. You must also be using a custom kernel with TWRP compression support because the partition is not big enough and must be compressed otherwise you will run into issues like TWRP freezing or touch screen issues.

I tried that and twrp still wont stick even after a OTA update flash. I installed ram disk twrp even after the update. What gives?

I fixed it. My mistake was flashing magisk boot img after the ramdisk installation and two kenel. I just flashed magisk.zip instead and got things working.

UltimateGamer83 said:
I fixed it. My mistake was flashing magisk boot img after the ramdisk installation and two kenel. I just flashed magisk.zip instead and got things working.
Click to expand...
Click to collapse
Yes, if you flash magisk boot img it will replace TWRP. Flashing the zip is the way to go. Glad you got it working.

UltimateGamer83 said:
I did not mean to say android 11 on the topic title. Wish I could edit it. I meant to say Android 10.
Click to expand...
Click to collapse
I've move your thread out of development, for which it doesn't qualify.
And I assumed your consent and edited the thread title.
In order to edit a title, click the "Edit" button of your OP and you'll see the title at the very top, which you're able to edit:
Spoiler: Screenshots
{
"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"
}
Regards
Oswald Boelcke
Senior Moderator

UltimateGamer83 said:
I tried that and twrp still wont stick even after a OTA update flash. I installed ram disk twrp even after the update. What gives?
Click to expand...
Click to collapse
I'm curious....you said you are on Android 10, but then you mentioned above installing an OTA update.....I thought all the currently available OTA updates are only for android 11?

My 10 cents worth. Magisk kills fastboot and adb in MY armor x5 mt6765, in 10_Q, so had no choice but to load boot-debug.img just to 'test'.
Try an android 9 bootloader designed for them 'super' .img's, this is the only way I could LOAD magisk, only to find what I read here.
Also note, in 10_Q, the gsi ability found in dev options dissapears when magisk is flashed, so I cant flash gsi, never mind use fastboot or adb.
Thank you.

How To Guide [TB-J716F] Flashing Pseudo_Global firmware (many languages inside)

If you not like ZUI firmware - you can flash Pseudo_Global to your tablet. I've tested this way and sharing it here.
Pseudo_global fw was built on ZUI, it has A11 inside and you never can to get some system updates - no one is doing them.
Your data will gone away.
YOU ARE WARNED !
And so:
I've tryed this on ZUI 14.0.127 with unlocked bootloader and active slot _a. Active slot can be checked with
Code:
adb shell /bin/getprop ro.boot.slot_suffix
and answer must be _a
If not, you need change boot slot with command in fastboot mode:
Code:
fastboot set_active other
And now you can reboot in EDL mode and start to flash all needed partitions from unpacked archive Pseudo_ROW_J716Fl.7z
You need unpacked ZUI 12.6.211 from lolinet https://mirrors.lolinet.com/firmware/lenovo/Tab_P11_Pro_2021/TB-J716F/ for working with QPST Partition Manager.
How it looks you can see in this video:
You must flash ALL partitions archive contains. Files in Add.rar not need, it for any case.
MANDATORY ! After flashing you need at first to boot in recovery and make reset to factory settings, it will format userdata. Without this action you can't boot.
Spoiler: IS
{
"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"
}
Good Luck !

f1tm0t said:
If you not like ZUI firmware - you can flash Pseudo_Global to your tablet. I've tested this way and sharing it here.
Pseudo_global fw was built on ZUI, it has A11 inside and you never can to get some system updates - no one is doing them.
Your data will gone away.
YOU ARE WARNED !
And so:
I've tryed this on ZUI 14.0.127 with unlocked bootloader and active slot _a. Active slot can be checked with
Code:
adb shell /bin/getprop ro.boot.slot_suffix
and answer must be _a
If not, you need change boot slot with command in fastboot mode:
Code:
fastboot set_active other
And now you can reboot in EDL mode and start to flash all needed partitions from unpacked archive Pseudo_ROW_J716Fl.7z
You need unpacked ZUI 12.6.211 from lolinet https://mirrors.lolinet.com/firmware/lenovo/Tab_P11_Pro_2021/TB-J716F/ for working with QPST Partition Manager.
How it looks you can see in this video:
You must flash ALL partitions archive contains. Files in Add.rar not need, it for any case.
MANDATORY ! After flashing you need at first to boot in recovery and make reset to factory settings, it will format userdata. Without this action you can't boot.
Spoiler: IS
View attachment 5783891View attachment 5783993View attachment 5783995
Good Luck !
Click to expand...
Click to collapse
It was exactly what I was looking for and trying for days, but following your tutorial I still couldn't, it didn't turn on, I had to upload the rom 12.6.211 again. I wanted to leave it with multiple languages.

augustobfe said:
still couldn't, it didn't turn on
Click to expand...
Click to collapse
OK, I will re-check it in 2-3 days. Although I think you did something wrong.

f1tm0t said:
will re-check it in 2-3 days
Click to expand...
Click to collapse
Dude, I have some bad news for you. Your hands are crooked. That needs to be fixed.
My method works without fail. It only takes half an hour.
Try it again.
Spoiler: Look this:

Rooting Pixel 4a

I attempted to root my Pixel 4a with Android 12 using Magisk. While executing commands, I received an error stating the partition was not found. I dont have the latest version of Andriod. My phone debugger mode is checked.

XZNZI said:
I attempted to root my Pixel 4a with Android 12 using Magisk. While executing commands, I received an error stating the partition was not found. I dont have the latest version of Andriod. My phone debugger mode is checked.
Click to expand...
Click to collapse
Not a lot to go on from you description,, So is this what's been done? Bootloader unlocked, oem unlocking toggled, magisk installed,,, magisk patched boot.img available and the adb command sent "fastboot flash boot patchedboot.img" ??

{
"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"
}

Yes
I downgraded to Andriod 10 and unlocked the bootloader, I installed Magisk and patched the bootimg. I ran the command fastboot boot flash and the partition was not found. I only have one partition. I am running Windows 10 Pro with Andriod SDK installed.

XZNZI said:
Yes
I downgraded to Andriod 10 and unlocked the bootloader, I installed Magisk and patched the bootimg. I ran the command fastboot boot flash and the partition was not found. I only have one partition. I am running Windows 10 Pro with Andriod SDK installed.
Click to expand...
Click to collapse
What version of ADB Platform Tools are you using?
Are you absolutely sure you're using the right firmware?
Why did you downgrade?
Are you following one of the several guides? If not, you should be.

XZNZI said:
Yes
I downgraded to Andriod 10 and unlocked the bootloader, I installed Magisk and patched the bootimg. I ran the command fastboot boot flash and the partition was not found. I only have one partition. I am running Windows 10 Pro with Andriod SDK installed.
Click to expand...
Click to collapse
Maybe some of the steps on this page might help you:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com

EngineerMind said:
Maybe some of the steps on this page might help you:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
Click to expand...
Click to collapse
That guide is very out of date.

V0latyle said:
That guide is very out of date.
Click to expand...
Click to collapse
It is, but since he mentioned Android 10, some of it might help him with his issue because it relates to Andorid 10

XZNZI said:
Yes
I downgraded to Andriod 10 and unlocked the bootloader, I installed Magisk and patched the bootimg. I ran the command fastboot boot flash and the partition was not found. I only have one partition. I am running Windows 10 Pro with Andriod SDK installed.
Click to expand...
Click to collapse
You could make sure your platform tools are upto date from here https://developer.android.com/studio/releases/platform-tools then try again, you could also try Pixel Flasher, it works great, slight learning curve but all in all pretty easy,
📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.
DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...
forum.xda-developers.com

hammered58 said:
You could make sure your platform tools are upto date from here https://developer.android.com/studio/releases/platform-tools then try again, you could also try Pixel Flasher, it works great, slight learning curve but all in all pretty easy,
📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.
DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...
forum.xda-developers.com
Click to expand...
Click to collapse
I download a mini version of the andriod tools and rooted my phone. I attempted to flash TWRP 3.5 for Android 10 for Pixel which failed. Error: Not allowed to flash to recovery. Debugging on Unlocked and rooted..