Official TWRP for NB1

Search This thread

yozil

Member
Dec 13, 2013
45
6
Anyone have an idea when TWRP would be patched for December Security Patch (Oreo 8.1.0 TA-1012) ? Since we are on Pie now I'm worried that it never release for Oreo...
 

THMSP

Senior Member
Jul 19, 2018
138
253
Europe
tmsp.io
Anyone have an idea when TWRP would be patched for December Security Patch (Oreo 8.1.0 TA-1012) ? Since we are on Pie now I'm worried that it never release for Oreo...
The problem is that, while I would be happy to do the patching, I have no way of getting a stock boot image from december patch which unfortunately is a requirement.
On the other hand, the best way to get a stock image is to do the process thats required for installing TWRP without a prepatched image (i.e. flashing to inactive slot and then patching active slot from there).

This means someone who has the december patch and an unlocked bootloader would have to do the patching on their own and then post the images here.
I wrote a small tutorial on how this can be done some time ago, you can find it in the subfolder "Tutorials" at https://bit.ly/nokia-nb1

IF someone decides to do this, feel free to send me the images and I will put them into the same cloud folder so people can find them more easily (with proper attribution of course).
 

yozil

Member
Dec 13, 2013
45
6
The problem is that, while I would be happy to do the patching, I have no way of getting a stock boot image from december patch which unfortunately is a requirement.
On the other hand, the best way to get a stock image is to do the process thats required for installing TWRP without a prepatched image (i.e. flashing to inactive slot and then patching active slot from there).

This means someone who has the december patch and an unlocked bootloader would have to do the patching on their own and then post the images here.
I wrote a small tutorial on how this can be done some time ago, you can find it in the subfolder "Tutorials" at https://bit.ly/nokia-nb1

IF someone decides to do this, feel free to send me the images and I will put them into the same cloud folder so people can find them more easily (with proper attribution of course).

Is there a risk to brick my phone if I do that ? And is there a way to backup the original image/firmware of a brick happens ?
 
  • Like
Reactions: kokszza

darfri

Senior Member
Nov 13, 2008
935
64
OnePlus 6T
I think I slot bricked my device...
And I do not understand how it is possible, as the slots shouldn't affect boot or recovery data.
So I had tried this before. I had selected slot b from twrp and it booted into a factory-resetted clean os state.
Now I managed to make my system unbootable with 3c Toolbox "One-Click" option called Kernel Tweak (what an idiot I am)
So after that I had working twrp and fastboot and unbootable (Nokia logo stuck) system partition.
So I decided to reflash system partition but I guess didn't find good image and flashed some crap there. I got it into a bootloop with nokia logo entering/exiting different screen brightness state (dangling dakrer and brighter Nokia logo).
So I decided to try slot B
After that, immediate power off and nothing turns it on. Like no battery (which had over 60%). The Vol-Up+power (10sec) has no effect, the cable doesn't charge neither windows device manager sees any device when I connect it to comp. OST also doesn't and also entering fastboot is not possible.
I am hoping that maybe the device booted to slot B system partition which had something on and now the device might be low power consumption stuck BSOD.. The device has been in that state almost for a month.. Now I am losing hope that I am gonna reach the recovery at some point...
What to do? It doesn't make sense - I did not flash recovery or boot, just system. And entered slot B from twrp - boom... BSOD
I want to get back into twrp. Maybe some way to disconnect battery or maybe I am just supid...

EDIT: I Just had a contact with computer - I saw it at least as a HID-devices there for a moment and the device even vibrated after I plugged in... and I blew it - i lost that contact because I unplugged it. Now its back in the previous state I talked about...
I think I was right - it is back in that low powered (on) state because it got charged when connected to computer.
I guess I have to wait again and all retrys would lead to charging (so it wont turn completely off to get it back to bootloader or somewhere there)
I wish there would be a physical reset button or something...

My goal is to get the device to fastboot mode so I could set slot_a active and get back to the bootloop scenario (at least I can restart it, use twrp, adb and fastboot then)
 
Last edited:

rashazad

Senior Member
Mar 3, 2011
186
53
Nokia 8
Xiaomi Poco F3
I was on android 8.1 November patch which I got it from this post.
I unlocked the bootloader successfully. then tried to install TWRP using this method. It did not boot into recovery. Changed the slot. Nothing changed. and when the phone booted again... Oh, man. Pie???
I once had updated it to 9. but flashed to 8.1. Did it remain in my partition B?
no wi-fi or cellular connection of course.
It only shows POWERED BY android trying to get to recovery.

Now what am I supposed to do? :)
Also everytime the phone boots, there is a caution message to lock the bootloader. Is it normal?

update1: it worked. I donno how, but I think playing with A/B fixed it. I'm stuck at nokia logo after flashing Magisk. Gonna fix that.
update2: It's gone :))) Guilty Remnant is coming to get me...

UPDATE3: phone is stuck on powered by... cant shutdown, cant do anything. no fastboot also. Now I'm really in trouble

UPDATE4: Fixed by finding how to turn off phone.
 
Last edited by a moderator:

shivaji namburu

Senior Member
Mar 16, 2017
52
3
Hello i booted into twrp but its asking to enter password to mount decrypt .what is that ,i actually use pin for my screen lock i tried using my pin but it didn't work.so what is this password..?
 

brill_e

Member
Dec 24, 2016
26
2
Graz
I was on android 8.1 November patch which I got it from this post.
I unlocked the bootloader successfully. then tried to install TWRP using this method. It did not boot into recovery. Changed the slot. Nothing changed. and when the phone booted again... Oh, man. Pie???
I once had updated it to 9. but flashed to 8.1. Did it remain in my partition B?
no wi-fi or cellular connection of course.
It only shows POWERED BY android trying to get to recovery.

Now what am I supposed to do? :)
Also everytime the phone boots, there is a caution message to lock the bootloader. Is it normal?

update1: it worked. I donno how, but I think playing with A/B fixed it. I'm stuck at nokia logo after flashing Magisk. Gonna fix that.
update2: It's gone :))) Guilty Remnant is coming to get me...

UPDATE3: phone is stuck on powered by... cant shutdown, cant do anything. no fastboot also. Now I'm really in trouble

UPDATE4: Fixed by finding how to turn off phone.

You can shut down by pressing longer all buttens....
 
  • Like
Reactions: rashazad

F. J.

Member
Jun 13, 2020
6
1
My Nokia 8 is rooted now

Hello.
thanks for the post. I managed to get my Nokia 8 rooted and of course I got the twrp as well.
Thank you so much for @THMSP for sharing your wondefull and informative expereince. Thank you so much for @czupyt for shows detailed method from THMSP somewhere in this post.
A brief journey till I got my Nokia 8 rooted is I went through downgrading my Nokia from Pie to Oreo. After that doing the unlock bootloader. Those two are in other post. Right after that, I carefully read THMSP and czupyt post and comment within this thread. Iprepared everything and followed each step carefully. I kinda deal with some problem when trying to do the CMD process like no permision thing and unknown command J. I dont know where do those problems come from. I dont even know how I solved them. Well, I just move my platform tools folder back and fort from local disk c to desktop and I do re-checking my usb debugging permision in my nokia. after that the no permision issue is gone. Then for the unknown command J issue, i think maybe it was my username in my laptop which cause the problem when I hit CMD. so I changed my username and also move my platform tools back and fort those two places again. Maybe it has something to do with renaming the img file or sooo.
Sorry, Im not so good at this thing actually, Forgive me I cannot provide clear information.
Yet, my main goal to write this post is to let people know that by today, The file shared by THMSP is working. the guide from both THMSP and czupyt is also working. Just in case people need soem information from me, Im using Nokia 8 with Oreo and November security patch.
 

CrashTestDummy_69

New member
May 24, 2020
2
0
It's stuck on boot screen after using the fastboot boot command

Fyi I can still use fastboot while I'm in this situation and I booted back into the OS. I tried doing this with both versions of the .img file on twrp website and I still got the same result
 
Last edited:

riky1234

New member
May 5, 2023
1
0
Can someone help me?
 

Attachments

  • Desktop Screenshot 2023.05.05 - 13.48.30.47.png
    Desktop Screenshot 2023.05.05 - 13.48.30.47.png
    26.5 KB · Views: 24
Can someone help me?
Hello, is this the first time you try to flash this phone, is the bootloader (critical) unlocked?
Apart from the fact that there are more recent versions of TWRP recovery than the one that appears in the image and to flash it (as long as the bootloader is unlocked and allows it) the correct command should be something like "fastboot flash recovery twrp-.... There is a lot of information on this forum about it.
 
Last edited:

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