Official TWRP for NB1

Search This thread
Aug 17, 2016
24
8
Quang Nam
I think what he means is that the popup to allow superuser access for an app doesn't appear and access is just declined, even if the magisk settings are correct.

@ghostwalkergamma which Magisk version do you have? Did you keep the preinstalled 17.1 Magisk or did you update it?
What I would try is to boot to TWRP, flash the Magisk uninstaller, and then reflash Magisk again (use 17.1, that works just fine for me)
Yes, tks god thats what I mean :D
Ok, i would try reflashing this, magisk just ask me to install update for the first time and I dont know that newest version (17.3) is not compatible with our newest patch
Btw, do you have the stock nov patch? I need it just in case something went wrong :D
 

czupyt

Senior Member
Apr 3, 2012
125
60
Poland
Yes, tks god thats what I mean :D
Ok, i would try reflashing this, magisk just ask me to install update for the first time and I dont know that newest version (17.3) is not compatible with our newest patch
Btw, do you have the stock nov patch? I need it just in case something went wrong :D

Patched and stock you may find here, also from other months.
https://drive.google.com/open?id=1UkFSbOESPdoKlFW6gV1iYqEplhzVwZs7

Regarding Magisk 17.3, I have this version and all is fine. Show first Magisk settings. If all is ok there, try to use Magisk 17.1. Also to be sure, you do not have any other SuperUser way, like SuperSu?
 

THMSP

Senior Member
Jul 19, 2018
138
250
Europe
tmsp.io
Yes, tks god thats what I mean :D
Ok, i would try reflashing this, magisk just ask me to install update for the first time and I dont know that newest version (17.3) is not compatible with our newest patch
Btw, do you have the stock nov patch? I need it just in case something went wrong :D
Go to Magisk Manager -> Settings and set "Update Channel" to stable, then it shouldn't suggest you to update to 17.3
Stock Images for November are here: https://forum.xda-developers.com/showpost.php?p=78169095&postcount=44
 
  • Like
Reactions: ghostwalkergamma
Aug 17, 2016
24
8
Quang Nam
Patched and stock you may find here, also from other months.
https://drive.google.com/open?id=1UkFSbOESPdoKlFW6gV1iYqEplhzVwZs7

Regarding Magisk 17.3, I have this version and all is fine. Show first Magisk settings. If all is ok there, try to use Magisk 17.1. Also to be sure, you do not have any other SuperUser way, like SuperSu?
I haven't used SuperSu for a long time, just want to stick with Magisk :D
Btw, reflashing Magisk 17.1 fix my problem too, and here my Magisk settings
seNh4a6.png

t4zRsET.png

Tks for all your support :victory:

---------- Post added at 20:11 ---------- Previous post was at 20:10 ----------

Go to Magisk Manager -> Settings and set "Update Channel" to stable, then it shouldn't suggest you to update to 17.3
Stock Images for November are here: https://forum.xda-developers.com/showpost.php?p=78169095&postcount=44

Yup, my problem is gone now, tks for your support :victory:
 

Zeuss92

Member
Jul 9, 2015
16
1
Galatina
If you want to install OTA updates, you need to reflash the stock image of your security patch, reboot to Android, do the OTA update, then reboot again and reflash the TWRP image.

It does not work for me. When I fastboot flash the stock security patch of mine, it says update failed. What if I want to hard reset my phone, having the patched boot image? Does hard reset restore stock boot image also?
 

ogzhnpcmn

Member
Nov 11, 2012
27
2
Patched and stock you may find here, also from other months.
https://drive.google.com/open?id=1UkFSbOESPdoKlFW6gV1iYqEplhzVwZs7

Regarding Magisk 17.3, I have this version and all is fine. Show first Magisk settings. If all is ok there, try to use Magisk 17.1. Also to be sure, you do not have any other SuperUser way, like SuperSu?

Hi, do you also have the Pre Rooted December version?
Because my phone has December 1 security patch and Prerooted Novemder doesnt work with this.

I can also downgrade my phone but tbh i have no clue how to do it :/

Thanks a lot
 

nabil427

Senior Member
Mar 11, 2011
347
35
Did not manage to boot on it using official Pie with december security. Any Idea? thx

>> Hi, never mind working OK thx
 
Last edited:

st-mc

New member
Aug 9, 2016
2
0
hi
I'm running android 8.1.0 with december patch. Just got twrp 3.2.3-1 img, the command "fastboot boot twrp.img" brings up a screen with powered by android written on it and does nothing.
I want to root my phone and don't know what to do.
please help....
 

sumitinhome

Senior Member
Jul 1, 2014
108
27
hi
I'm running android 8.1.0 with december patch. Just got twrp 3.2.3-1 img, the command "fastboot boot twrp.img" brings up a screen with powered by android written on it and does nothing.
I want to root my phone and don't know what to do.
please help....

you need to use the command "fastboot flash boot_x twrp.img". where x= your active partition (either a or b)
 
  • Like
Reactions: st-mc

Dr. Slump

Senior Member
Sep 13, 2012
67
25
Given the fact that "fastboot boot" doesn't work, what we can do to properly patch the boot image with TWRP?
I think our most obvious option is to flash the unactive boot partition and run twrp.img from there and make it patching the active boot partition, right? Is there any better solution like the way magisk does? (as it runs a normal process on android and can patch the image file, not the partition itself)
 

THMSP

Senior Member
Jul 19, 2018
138
250
Europe
tmsp.io
Given the fact that "fastboot boot" doesn't work, what we can do to properly patch the boot image with TWRP?
I think our most obvious option is to flash the unactive boot partition and run twrp.img from there and make it patching the active boot partition, right? Is there any better solution like the way magisk does? (as it runs a normal process on android and can patch the image file, not the partition itself)
While it is possible to patch an image externally I wouldn't recommend it, since that does not give you the convenient ability to get a backup of the stock image at the same time
(required for OTA updates). The easiest solution for the enduser is using prepatched boot images. If you want to make images yourself you should use the inactive slot method.
 

Dr. Slump

Senior Member
Sep 13, 2012
67
25
While it is possible to patch an image externally I wouldn't recommend it, since that does not give you the convenient ability to get a backup of the stock image at the same time
(required for OTA updates). The easiest solution for the enduser is using prepatched boot images. If you want to make images yourself you should use the inactive slot method.

Stock image is the captured OTA image already :) How can I patch it externally?
 

THMSP

Senior Member
Jul 19, 2018
138
250
Europe
tmsp.io
Stock image is the captured OTA image already :) How can I patch it externally?
By using a boot image unpacker, replacing the ramdisk image with the one from the installer .zip and repackaging.
However I have never done that except for some random experiments with it on linux so I can't help you with exact steps unfortunately.

However, if you are talking about the official Pie update (since thats a full OTA), I already have a prepatched image for it
(https://bit.ly/nokia-nb1 in the folder "Boot Images/2018-12"), if that makes it easier for you.
 
  • Like
Reactions: Dr. Slump

Dr. Slump

Senior Member
Sep 13, 2012
67
25
By using a boot image unpacker, replacing the ramdisk image with the one from the installer .zip and repackaging.
However I have never done that except for some random experiments with it on linux so I can't help you with exact steps unfortunately.

However, if you are talking about the official Pie update (since thats a full OTA), I already have a prepatched image for it
(https://bit.ly/nokia-nb1 in the folder "Boot Images/2018-12"), if that makes it easier for you.

OK, thank you. Changing some properties would be nice along with integrating the TWRP :D I will experiment, too.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 12
    Hey now TWRP is officially available for Nokia 8 NB1


    Installation:
    If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
    If you do not already have TWRP installed: Download both the img and the zip.You will need to have fastboot binaries and the correct drivers installed.
    You can grab latest platform-tools (fastboot binaries) from [here]https://developer.android.com/studio/releases/platform-tools
    Now go in the directory where your adb/fastboot binaries exists.Connect the device to your PC.Enable USB debugging in developer options & then open a command window and run the following command from the proper location:
    adb reboot bootloader
    Your device should now be in the bootloader.
    Then again from command window run the following command from the proper location:
    fastboot boot path/to/twrp.img
    This will temporarily boot TWRP on your device. Use adb to push the zip onto your device:
    adb push path/to/twrp.zip /
    Even MTP is working you can also directly copy zip from your pc and paste to your device.
    Go to install and browse to the zip and install the zip. The zip will install TWRP to both boot slots. Installing TWRP at this time will remove root if you are currently rooted.
    If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.



    Thanks to @dg28gadhavi he is the maintainer for NB1




    https://eu.dl.twrp.me/NB1/#
    Flash instruction see dev post #4

    Powered by View 10
    11
    Some days ago while rooting my device, I found a flaky behaviour in the bootloader regarding "fastboot boot" (see this post about the topic that I made on the thread for prerooted boot images: https://forum.xda-developers.com/showpost.php?p=78033924&postcount=26)
    Basically what seems to have happened with the August Update is that fastboot boot is now completely broken, since it doesn't even boot stock images - they stay in the same "Powered by Android" screen that TWRP stays in. After flashing everything booted just fine.

    That made me thinking: What if not TWRP is the problem, but the way how it is installed? Since the official way of installing TWRP is to boot a temporary image, and then flash an installer .zip that patches your boot image and adds TWRP to it, it would potentially be subject to the same bug I experienced with the prerooted boot images. So I just went fully haywire, and flashed the temporary TWRP image to the boot partition of my inactive slot. And, well, it worked just fine! Continuing from that I could easily flash the permanent making .zip and Magisk to patch the boot image of my active slot, and then reboot into the active one again. Some quick testing (adb reboot recovery) showed that this was working just fine. Even installing the custom kernel that Dhruv made before the August update worked just fine for me.

    Reminder: I used the official builds. I neither made my own device tree or kernel, I don't even have any idea how to do that :p

    So, since my way of doing it is really stupid and it should be done by noone else, I decided to prepare some prepatched boot images for public release. You can download them, and "fastboot flash" them to your boot partition, getting full TWRP support without having to follow what I did initially.

    Link: https://bit.ly/nokia-nb1, under the folder "Boot Images" you can find folders sorted by security patch version

    The linked folder contains two .img files:
    • Stock: A clean backup of the stock image for restoring before OTA updates.
    • TWRP: A twrp prepatched (and in case of Oreo) prerooted boot image you have to flash to your active boot partiton

    After downloading the image of your choice, you need to reboot your phone into download mode and flash the image using fastboot, depending on your active slot.
    You need an unlocked bootloader for this.

    Code:
    adb reboot bootloader
    fastboot getvar current-slot
    # x = the slot name the previous command returns (either a or b)
    fastboot flash boot_x <path to the downloaded .img>
    If you want to install OTA updates, you need to reflash the stock image of your security patch, reboot to Android, do the OTA update, then reboot again and reflash the TWRP image.
    Even though I would be careful with installing updates as soon as Pie drops :p

    All Credits go to Dhruv for his TWRP, and to Czupyt and whalesplaho from the Telegram group for testing those images.
    6
    Gonna make a proper thread Have fun ! BTW don't flash it to boot partitions instead use ramdisk injector zip provided by me or TWRP team site!

    For Now wait! ( Am not able to send Link in message as I freshly rejoined )

    Quick steps :

    1) adb reboot bootloader
    2) fastboot boot twrp-3.2.3-0-NB1.img
    3 ) Flash permanent making zip once booted in twrp
    4) Go in reboot menu of twrp and reboot to recovery once permanent making zip is flashed
    5 ) Now flash Magisk zip. ( Latest beta 16.7 not stable 16.0 )
    6
    For all present here if u don't have a telegram account please make one and who already have it please join this

    t.me/HMD_Nokia_8 So i can contact u ppl and testers more easily Thank You !

    Regards and Apologies fot the issues you all faced so far it's gonna fix by today!
    5
    New build up with sdcard,otg fixes grab it from official TWRP site !!!

    https://twrp.me/nokia/nokia8.html