[OFFICIAL] TWRP 3.4.0-0 | Team Win Recovery Project | Nokia 7 Plus | Onyx |

Raghu varma

Senior Member
Mar 22, 2017
738
1,038
113
Hyderabad
raghuvarma331.github.io



Note - Iam Not Responsible for bricked devices

About Team win recovery project

TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.

Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.


Installation procedure

Note - According to HMD global Nokia 7 Plus launched in 2018 march with Oreo out of the box.

Well in my official twrp thread one of my user posted a photo during when he tried to boot twrp of mine on his Nokia 7 Plus phone turns in to white screen with some lines & he underlined that his phone having different display ( pure display ) . According to HMD employee He undelined that " they changed the screen provider of Nokia 7 Plus from some period of time"

Well to make these things clear ?

I introduced a separate infra for this Nokia 7 Plus phones and we call them as

OOB & POB

Means The people who got Oreo out of the box can actually use the twrp builds named with

OOB ( Oreo out of the box )

&

The people who got Pie out of the box phones can actually use the twrp builds named with

POB ( Pie out of the box )
.


1 . Download twrp-3.4.0-0-B2N_sprout_sprout.img & twrp-installer-3.4.0-0-B2N_sprout.zip copy in one folder
2. connect phone to pc boot your phone to download mode
3. open cmd in that folder
4. type fastboot devices
5. type fastboot boot twrp-3.4.0-0-B2N_sprout.img
6. now your phone will boot in to twrp
7. now copy twrp installer.zip in to your phone from pc using type c usb cable
8. now flash twrp installer zip ( this will make your twrp permanent )
10. now flash magisk or what ever your wish and press reboot system
11. now if you people want to boot in to twrp? power off your phone connect to pc or charger
& wait for battery logo and press volume up and power button for 8 seconds now you will boot in to twrp


Download Android 11 Twrp-3.4.0-0 From Here


Download Android 10 Twrp-3.4.0-0 From Here


Download Android 9 Twrp-3.3.1-0 From Here





XDA:DevDB Information
TWRP 3.4.0-0 , for the Nokia 7 Plus

Contributors
Raghu varma
Source Code:
https://github.com/TeamWin/android_device_nokia_B2N_sprout
My build script https://github.com/RaghuVarma331/scripts

Version Information
Status: Stable
Current Beta Version: 3.4.0-0

Created 2019-06-16
Last Updated 2020-06-25
 
Last edited:

ban.codrut

Senior Member
Jan 11, 2015
422
120
63
Thank you for compiling and shearing this. I'm really excited to test it out, especially the crypto part if it works properly !
I've been looking through your repositories and I've noticed you've build B2N tree from DRG tree. How much are they alike, with emphasis on audio part, eg mixer paths ?
Also I'm the owner of an bl-unlocked B2N , if you ever need someone to beta test PM me.
 
Last edited:

k3dar7

Senior Member
Apr 14, 2018
812
441
73
>> Remove lock screen password , pin , pattern

but this remove crypt from internal_storage or not?? anyway this step is i hope need only if i want acces to internal_storage from TWRP, if i not need and use (same as with https://forum.xda-developers.com/nokia-7-plus/development/recovery-twrp-3-2-3-0-t3892644) USB-C where store Magisk.zip for install, then is this step not need?

>> this will work only On June 2019 Security Patch And From Now i will update Twrp Every Month
sure? for boot only is not need same TWRP version as installed SecurityPatch, and twrp-installer is not "only" patching/adding TWRP to actual/stock/any_sec_patch_version??
 
Last edited:
  • Like
Reactions: xsycox

Raghu varma

Senior Member
Mar 22, 2017
738
1,038
113
Hyderabad
raghuvarma331.github.io
Thank you for compiling and shearing this. I'm really excited to test it out, especially the crypto part if it works properly !
I've been looking through your repositories and I've noticed you've build B2N tree from DRG tree. How much are they alike, with emphasis on audio part, eg mixer paths ?
Also I'm the owner of an bl-unlocked B2N (by you), if you ever need someone to beta test PM me.
Sure thanks :)
 

ban.codrut

Senior Member
Jan 11, 2015
422
120
63
Stuck at Spash Screen after installing TWRP

Title says it all.
Using fastboot boot works properly and I'm presented with the decrypt page after a couple of seconds.
Using the installer.zip and trying to boot into recovery ends up being stuck at the spash screen, with no decrypt page showing up. I've uploaded recovery.log
View attachment stuckspash.log with permanent installer stops at line 81
View attachment fastbootrecovery.log with fastboot boot continues after line 82 with key management : Using Keymaster HAL: 3 from QTI for encryption. Security level: TRUSTED_ENVIRONMENT, HAL: [email protected]::IKeymasterDevice/default

on a side note: other issues / small annoyances
a) While fastboot boot into it, on the decrypt page there is some graphical glitches: flashing yellow on top bar, and other color errors. Touching the screen first time fixes it. Also (maybe a TWRP thing) the aspec ratio is 16:9 with gap on top.
b) Display locking doesn't work properly. It's unable to actually turn off the screen, instead it only dims the screen and stays on with the last frame on it (no picture update), instead of actually turning off the screen.
Both can be seen in fastbootrecovery.log:
a) line 15 - 25 :
Code:
Starting the UI...
setting DRM_FORMAT_BGRA8888 and GGL_PIXEL_FORMAT_BGRA_8888
cannot find/open a drm device: No such file or directory
fb0 reports (possibly inaccurate):
  vi.bits_per_pixel = 32
  vi.red.offset   =   0   .length =   8
  vi.green.offset =   8   .length =   8
  vi.blue.offset  =  16   .length =   8
setting GGL_PIXEL_FORMAT_RGBA_8888
double buffered
RECOVERY_BGRA
b) line 26 - 33:
Code:
framebuffer: 0 (1080 x 2160)
Using fbdev graphics.
I:TWFunc::Set_Brightness: Setting brightness control to 420
I:Loading package: splash (/twres/splash.xml)
I:Load XML directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/splash.xml' directly
I:Checking resolution...
I:Scaling theme width 1.000000x and height 1.083333x, offsets x: 0 y: 80 w: 0 h: -80
 

Raghu varma

Senior Member
Mar 22, 2017
738
1,038
113
Hyderabad
raghuvarma331.github.io
Title says it all.
Using fastboot boot works properly and I'm presented with the decrypt page after a couple of seconds.
Using the installer.zip and trying to boot into recovery ends up being stuck at the spash screen, with no decrypt page showing up. I've uploaded recovery.log
View attachment 4780973 with permanent installer stops at line 81
View attachment 4780979 with fastboot boot continues after line 82 with key management : Using Keymaster HAL: 3 from QTI for encryption. Security level: TRUSTED_ENVIRONMENT, HAL: [email protected]::IKeymasterDevice/default

on a side note: other issues / small annoyances
a) While fastboot boot into it, on the decrypt page there is some graphical glitches: flashing yellow on top bar, and other color errors. Touching the screen first time fixes it. Also (maybe a TWRP thing) the aspec ratio is 16:9 with gap on top.
b) Display locking doesn't work properly. It's unable to actually turn off the screen, instead it only dims the screen and stays on with the last frame on it (no picture update), instead of actually turning off the screen.
Both can be seen in fastbootrecovery.log:
a) line 15 - 25 :
Code:
Starting the UI...
setting DRM_FORMAT_BGRA8888 and GGL_PIXEL_FORMAT_BGRA_8888
cannot find/open a drm device: No such file or directory
fb0 reports (possibly inaccurate):
  vi.bits_per_pixel = 32
  vi.red.offset   =   0   .length =   8
  vi.green.offset =   8   .length =   8
  vi.blue.offset  =  16   .length =   8
setting GGL_PIXEL_FORMAT_RGBA_8888
double buffered
RECOVERY_BGRA
b) line 26 - 33:
Code:
framebuffer: 0 (1080 x 2160)
Using fbdev graphics.
I:TWFunc::Set_Brightness: Setting brightness control to 420
I:Loading package: splash (/twres/splash.xml)
I:Load XML directly
I:PageManager::LoadFileToBuffer loading filename: '/twres/splash.xml' directly
I:Checking resolution...
I:Scaling theme width 1.000000x and height 1.083333x, offsets x: 0 y: 80 w: 0 h: -80
as i said this will work only on June 2019 security patch due to decryption works according to security patch
may be you may forgot to read that line
{ Note - this will work only On June 2019 Security Patch And From Now i will update Twrp Every Month & if you get password error in twrp just get back to system and Remove lock screen password , pin , pattern and keep in swipe mode and follow the procedure }
and thanks for posting logs
 
Last edited:
  • Like
Reactions: ban.codrut

ban.codrut

Senior Member
Jan 11, 2015
422
120
63
as i said this will work only on June 2019 security patch due to decryption works according to security patch
may be you may forgot to read that line
{ Note - this will work only On June 2019 Security Patch And From Now i will update Twrp Every Month & if you get password error in twrp just get back to system and Remove lock screen password , pin , pattern and keep in swipe mode and follow the procedure }
and thanks for posting logs
Admittedly I haven't payed much attention to that line.
I read it but didn't understood it, mainly because there is no June SP out there yet.
So you are saying that we must wait for the SP to come out before trying the permanent zip installer ?
For my own reading, could you please share a link to the decryption changes ? I've tried to look for something related in Android Security Bulletin but couldn't find. Maybe I missed it :(
 

ban.codrut

Senior Member
Jan 11, 2015
422
120
63
@k3dar7 you might be interested in my post above. Apparently TWRP and the installer has security patch version hardcoded, meaning it is not taken from what you have.
 
Last edited:

ban.codrut

Senior Member
Jan 11, 2015
422
120
63
As of this the May repack is not needed anymore.
I know it hasn't rolled out fully yet, but you can still use stock recovery and sd card update method.
So after some days after this post I will remove the link to May repack as it will not be needed.
 

k3dar7

Senior Member
Apr 14, 2018
812
441
73
@k3dar7 you might be interested in my post above. Apparently TWRP and the installer has security patch version hardcoded, meaning it is not taken from what you have.
thanks, understand and confirm that twrp from #1 work with june security update installed with data decryption :)
only question for clarify, if i (or other who this read) not want in twrp decrypt data partition (with using usb-c flash or push zip from pc to /tmp), is possible use actual version with older/newer than june ota update?