How To Flash Global Firmware (( PL2-222E-0-00WW-B02 )) Nokia6.1 - Nokia 6.1 (2018) Guides, News, & Discussion

How to flash the stock global firmware
Hello guys in this thread i`ll provide you esaier way to flash the stock global firmware that`s available with june security patch
PL2-222E-0-00WW-B02
Required things
1- bootloader unlocked
2- enable usb debugging from developer option
3-adb and fastboot tools
4- use this codes to reboot download mode
Code:
adb shell
Code:
reboot bootloader
5- download the zips provided in the link below unzip it on your desktop
6- brain working
INSTALLATION
1- install OST LA 6.0.4 tool (( double click on LAUNCHER.EXE ))
when installition done go to C driver/program files/OST LA folder then look for this tow files and delete them
a- OnlineUpdateTool.exe
b- OnlineUpdateToolConfiger.exe
2- now from OSTLA patch zip copy OnlineUpdateTool.exe to OST folder in C driver then Run it as administrator / click NEXT / click on 3 dots { ... } to pick up PL2-222E-0-00WW-B02.mlf from where you placed the unpacked firmware
3- reboot your phone to downloade mode (( Bootloader )) or (( Fastboot mode )) and plug it into your PC then click next
installation completed now force your phone to reboot recovery ((keep your phone pluged into pc or charger press and hold 3 buttons at the same time when the phone switched off release volume down and keep holding volume up and power then when the bootloader unlocked message disappear release power button now you`ll get page with yellow robot hold power button then once click on volume up okay good now you are in stock recovery go to factory reset then restart system wait the phone till reboot system it`ll take few minutes be patient now system boot you are totally stock update your system and enjoy
you can relock your bootloader as you like {{NOTICE}} after the last August update the unlock.bin file doesn`t work to unlock blootloader you need to set active the inactive slot ""the one with July patch usually on slot b""
command is
Code:
fastboot --set_active=b
5- please forgive me for my bad English
4- don`t forget to hit thanks button if you like my work
DOWNLOAD
unpacked firmware
https://mega.nz/#!jgAXnSrQ!M_NEBQsoNd48qdYpry2L9ER9-Xm5EebBTLgvopCbwJw
OST LA 6.0.4 tool and patch
https://mega.nz/#!2pBXgKgL!TifBFGYWDsC2TqUWzZvTeJlkzJTo0I4MTthCJxuifN0
Sٍpecial Thanks
@hikari_calyx to his special work for Nokia users
@blackpanther0582 for his stock fw
@heineken78 for his patch

I reuploade the unpacked firmware folder already edited the files inside all what you need is following the steps to success

#reserved

where did you get this firmware and how do i know you didn't put a trojan in it

prg318 said:
where did you get this firmware and how do i know you didn't put a trojan in it
Click to expand...
Click to collapse
It's from the guy i maintained and he is a trusted guy he provided almost all Nokia firmware
If you can't trust me or trust him so please don't flash it and stay on the safe side ?

Maherabed1986 said:
It's from the guy i maintained and he is a trusted guy he provided almost all Nokia firmware
If you can't trust me or trust him so please don't flash it and stay on the safe side
Click to expand...
Click to collapse
Yeah - I understand. I'm more confused about why Nokia doesn't provide stock images and how people are finding them. Does nokia provide these images to retailers or something?

Maherabed1986 said:
How to flash the stock global firmware
Hello guys in this thread i`ll provide you esaier way to flash the stock global firmware that`s available with june security patch
PL2-222E-0-00WW-B02
Required things
1- bootloader unlocked
2- enable usb debugging from developer option
3-adb and fastboot tools
4- use this codes
Code:
adb shell
Code:
reboot bootloader
5- download the zips provided in the link below unzip it on yor desktop
6- brain
INSTALLATION
1- install OST LA 6.0.4 tool (( double click on LAUNCHER.EXE ))
when installition done go to C driver/program files/OST LA folder then look for this tow files and delete them
a- OnlineUpdateTool.exe
b- OnlineUpdateToolConfiger.exe
2- now from OSTLA patch zip copy OnlineUpdateTool.exe to OST folder in C driver then Run it as administrator / click NEXT / click on 3 dots ... to pick up PL2-222E-0-00WW-B02.mlf from where you placed the unpacked firmware
if you get any options " in my case i didn`t get any options " check those option (( Normal Download;Erase user data;Erase error data;Erase FRP;Unlock Screen Lock;Check System AP Status ))
3- reboot your phone to downloade mode (( Bootloader )) or (( Fastboot mode )) and plug it into your PC then click next installation completed you`re done
you can now relock your bootloader as you like {{NOTICE}} after the last August update the unlock.bin file doesn`t work to unlock or relock bl you need to set active the other slot ""the one with July patch""
4- don`t forget to hit thanks button if you like my work
DOWNLOAD
unpacked firmware
https://mega.nz/#!jgAXnSrQ!M_NEBQsoNd48qdYpry2L9ER9-Xm5EebBTLgvopCbwJw
OST LA 6.0.4 tool and patch
https://mega.nz/#!2pBXgKgL!TifBFGYWDsC2TqUWzZvTeJlkzJTo0I4MTthCJxuifN0
Sٍpecial Thanks
@hikari_calyx to his special work for Nokia users
@blackpanther0582 for his stock fw
@heineken78 for his patch
Click to expand...
Click to collapse
Is it work on Ta 1054? chinese varient?

juwelrana091 said:
Is it work on Ta 1054? chinese varient?
Click to expand...
Click to collapse
I have no idea if that will work but i heard before you try that with @hikary

juwelrana091 said:
Is it work on Ta 1054? chinese varient?
Click to expand...
Click to collapse
I have no idea if that will work but i heard before you try that with @hikary

I tried, does not work with TA-1054

Does this work with ta1045
Edit - Yes. I didn't try with the OST tool but did it with fastboot and it worked for my 1045

Make sure your device is unlock before you install the August update. Nokia blocked the ability to unlock with the August update.
Aslo, after you install the Global Firmware, do a factory reset from the recovery menu. After it boots into system, reboot to download mode and boot a patched boot file that was created by Maher, that allows you to install Magisk and have root without flashing TWRP. Flashing TWRP, will cause you not to be able to install future OTAs.
The patched boot it's only to boot it temporarily then install magisk direct to your boot:
Link to Maher's XDA post: https://forum.xda-developers.com/nokia-6-2018/development/root-nokia6-1-devices-t3831682
patched_boot_Nokia6.1_Aug.img
https://mega.nz/#!M8klgYqA!fcQU6Dqs9...PwZ0JTScPIPi1A
Here are the commads:
fastboot boot patched_boot_Nokia6.1_Aug.img
then from magisk manager apk install/install direct after the processes done reboot

If you have issue running OST
Edit the PL2-222E-0-00WW-B02.mlf inside the extracted global firmware and modify these values as shown below lines 7-8 and save:
Code:
INITOPTION = 0x20000
INITDLTYPE = 0x60
SECURITY_VER = 0x0001

Danny1976 said:
If you have issue running OST
Edit the PL2-222E-0-00WW-B02.mlf inside the extracted global firmware and modify these values as shown below lines 7-8 and save:
Code:
INITOPTION = 0x20000
INITDLTYPE = 0x60
SECURITY_VER = 0x0001
Click to expand...
Click to collapse
You are super fast buddy i was going to edit the installation steps
Additional to this delete md5 file inside unpacked fw

Maherabed1986 said:
You are super fast buddy i was going to edit the installation steps
Additional to this delete md5 file inside unpacked fw
Click to expand...
Click to collapse
Just trying to help, since you have helped so much.

prg318 said:
Does this work with ta1045
Edit - Yes. I didn't try with the OST tool but did it with fastboot and it worked for my 1045
Click to expand...
Click to collapse
How did you flash it with fastboot?

nikalus said:
How did you flash it with fastboot?
Click to expand...
Click to collapse
Use the "extracted" image (should have a bunch of .elf, .img, and .mbn files). Then you need to execute a bunch of fastboot commands for each partition.
You'll have to adjust the commands somewhat to work with the image that your flashing but you can get an idea of what needs to be done from this script:
PHP:
@echo off
cls
cd /d %~dp0
fastboot oem alive
fastboot flash xbl_a B2N-0-132E-xbl_service.elf
fastboot flash xbl_b B2N-0-132E-xbl_service.elf
fastboot flash abl_a B2N-0-132E-abl_service.elf
fastboot flash abl_b B2N-0-132E-abl_service.elf
fastboot reboot-bootloader
echo.
echo Waiting for device...
@ping localhost -n 5 >nul
echo.
fastboot flash partition B2N-0-132E-gpt_both0.bin
fastboot flash xbl_a B2N-0-132E-xbl_service.elf
fastboot flash xbl_b B2N-0-132E-xbl_service.elf
fastboot flash abl_a B2N-0-132E-abl_service.elf
fastboot flash abl_b B2N-0-132E-abl_service.elf
fastboot flash tz_a B2N-0-132E-tz.mbn
fastboot flash rpm_a B2N-0-132E-rpm.mbn
fastboot flash hwcfg B2N-0-132E-hwcfg.img
fastboot flash hyp_a B2N-0-132E-hyp.mbn
fastboot flash pmic_a B2N-0-132E-pmic.elf
fastboot flash keymaster_a B2N-0-132E-keymaster64.mbn
fastboot flash cmnlib_a B2N-0-132E-cmnlib.mbn
fastboot flash cmnlib64_a B2N-0-132E-cmnlib64.mbn
fastboot flash dsp_a B2N-0-132E-dspso.bin
fastboot flash devcfg_a B2N-0-132E-devcfg.mbn
fastboot flash sec B2N-0-132E-sec.dat
fastboot flash mdtpsecapp_a B2N-0-132E-mdtpsecapp.mbn
fastboot flash storsec B2N-0-132E-storsec.mbn
fastboot flash systeminfo_a systeminfo.img
fastboot reboot-bootloader
echo.
echo Waiting for device...
@ping localhost -n 5 >nul
echo.
fastboot flash modem_a B2N-1-132E-NON-HLOS.bin
fastboot flash mdtp_a B2N-0-132E-00CN-mdtp.img
fastboot flash boot_a B2N-0-132G-00CN-boot.img
fastboot erase boot_b
fastboot flash system_a B2N-0-132E-00CN-system.img
fastboot flash system_b B2N-0-132E-00CN-system_other.img
fastboot flash bluetooth_a B2N-0-132E-BTFM.bin
fastboot flash persist B2N-0-132E-00CN-persist.img
fastboot erase userdata
fastboot flash sutinfo B2N-00CN-001-sutinfo.img
fastboot flash nvdef_a B2N-0-132E-NV-default.mbn
fastboot flash hidden_a C1N-0-0020-0001-hidden.img.ext4
fastboot flash cda_a B2N-00CN-007-cda.img
fastboot erase ssd
fastboot erase misc
fastboot erase sti
fastboot flash splash_a B2N-00CN-007-splash.img
fastboot erase ddr
fastboot flash KEY_INFO B2N-00CN-006-keyinfo.img
:flash_vendor
fastboot flash vendor_a B2N-0-132E-00CN-vendor.img >log.txt 2>&1
find /i "FAILED" log.txt
if %errorlevel% NEQ 0 (
echo OKAY
) else (
echo WRITE FAILED REFLASHING...
call:flash_vendor
)
fastboot flash xbl_a B2N-0-132E-xbl.elf
fastboot flash xbl_b B2N-0-132E-xbl.elf
fastboot flash abl_a B2N-0-132E-abl.elf
fastboot flash abl_b B2N-0-132E-abl.elf
fastboot oem set_active _a
fastboot oem enable-charger-screen
:flash_e2p_package
fastboot flash e2p_package B2N-0-132E-e2p.tar >log.txt 2>&1
find /i "FAILED" log.txt
if %errorlevel% NEQ 0 (
echo OKAY
) else (
echo WRITE FAILED REFLASHING...
call:flash_e2p_package
)
:flash_e2p_script
fastboot flash e2p_script B2N-0-132E-e2p.sh >log.txt 2>&1
find /i "FAILED" log.txt
if %errorlevel% NEQ 0 (
echo OKAY
) else (
echo WRITE FAILED REFLASHING...
call:flash_e2p_script
)
:flash_md4
fastboot flash md4 md4.dat >log.txt 2>&1
find /i "FAILED" log.txt
if %errorlevel% NEQ 0 (
echo OKAY
) else (
echo WRITE FAILED REFLASHING...
call:flash_md4
)
echo.
echo rebooting device...
echo done!
del log.txt
pause
exit

waiting for device
someone know a solution?

nokia a said:
waiting for device
someone know a solution?
Click to expand...
Click to collapse
Install Nokia Driver

could you send me the drivers that work? nokia ta-1054

Related

[Q] Newbie needing help rooting my Sensation!

Hi there,
I'm new to all things development. I have an HTC Sensation on Virgin mobile in Canada. I am trying desperately to root my phone and I have followed this guide (http://forum.xda-developers.com/showthread.php?t=1632553). I've done lots of searching on this forum and google and can't find anyone with my specific problem.
I have put the SupperSU.zip file into my SD root, unlocked my bootloader through the HTC dev website and flashed CWM using the One X program. However, when I try to boot into recovery it stalls on the white HTC loading screen. I have tried to boot into recovery using One X, a command control from my android folder on my computer and using the power button and down volume button but it always stalls. Since I cant boot into recovery I cant use CWM flash the SuperSU.zip, which I understand finishes the rooting process.
Also: I am pretty sure my drivers are up to date but when I tried to install the drivers from One X it always interrupts the installer saying the Device is in Use...andnI dont know if that means my phone (which its not) or my computer. I uninstalled my antivirus because I read that might be blocking it... but still no luck!
I would really appreciate any help or guidance you can offer! I am a complete newbie when it comes to this and I have done my best to search out answers and tutorials before coming here for help.
reflash the recovery.img using the fastboot command(rename it as recovery.img)
fastboot flash recovery recovery.img then do
fastboot reboot bootloader
after that try to enter to recovery
note:i assume you know how to use fastboot commands
if you still can't enter to recovery then try this
place the recovery.img in the folder where you have adb and fastboot files
boot the device to bootloader and connect it to pc via usb(in the hboot screen must say fastboot usb)
open in the folder a cmd window and do
fastboot reboot recovery.img
rzr86 said:
reflash the recovery.img using the fastboot command(rename it as recovery.img)
fastboot flash recovery recovery.img then do
fastboot reboot bootloader
after that try to enter to recovery
note:i assume you know how to use fastboot commands
if you still can't enter to recovery then try this
place the recovery.img in the folder where you have adb and fastboot files
boot the device to bootloader and connect it to pc via usb(in the hboot screen must say fastboot usb)
open in the folder a cmd window and do
fastboot reboot recovery.img
Click to expand...
Click to collapse
Thanks for your advice! I just want to double check what you mean before I try anything.. Do you mean that I should rename the fastboot file to 'recovery.img' and then use the fastboot commands (by holding shift and right click on my android folder to open command folder)? I am really quite new an d I think I know how to use fastboot commands but I'm not positive. I'm not sure where to find the recovery.img file!
I'm a complete beginner and I'm really trying to understand this Thanks for being patient and helping!
kellai15 said:
Thanks for your advice! I just want to double check what you mean before I try anything.. Do you mean that I should rename the fastboot file to 'recovery.img' and then use the fastboot commands (by holding shift and right click on my android folder to open command folder)? I am really quite new an d I think I know how to use fastboot commands but I'm not positive. I'm not sure where to find the recovery.img file!
I'm a complete beginner and I'm really trying to understand this Thanks for being patient and helping!
Click to expand...
Click to collapse
exactly as you said
about recovery.img use the one from the guide you used to root the device(CMW 5.8.0.9 )
or check 4ext recovery from this guide
http://forum.xda-developers.com/showthread.php?t=1631861 (step 2)
rzr86 said:
exactly as you said
about recovery.img use the one from the guide you used to root the device(CMW 5.8.0.9 )
or check 4ext recovery from this guide
http://forum.xda-developers.com/showthread.php?t=1631861 (step 2)
Click to expand...
Click to collapse
So when I renamed my CMW recovery file as recovery.img and put it in my android folder, booted my phone into fastboot usb mode and connected it to my pc. I opened a command window from the android folder with the recovery.img file in it and typed fastboot reboot recovery.img all I got was this:
C:\android>fastboot reboot recovery.img
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
What should I do now? Thank you again!!
--
I also tried to open a command window there and reflash the recovery.img by typing fastboot flash recovery recovery.img ...except it said "error: "cannot load recovery.img" except the file is definitely in that folder and named recovery.img
kellai15 said:
So when I renamed my CMW recovery file as recovery.img and put it in my android folder, booted my phone into fastboot usb mode and connected it to my pc. I opened a command window from the android folder with the recovery.img file in it and typed fastboot reboot recovery.img all I got was this:
C:\android>fastboot reboot recovery.img
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
What should I do now? Thank you again!!
Click to expand...
Click to collapse
try this
fastboot boot recovery.img
rzr86 said:
try this
fastboot boot recovery.img
Click to expand...
Click to collapse
I tried that but it keeps saying - Cannot Load "recovery.img" and I know that the file is in the folder I'm opening the command window from and named recovery.img .
kellai15 said:
I tried that but it keeps saying - Cannot Load "recovery.img" and I know that the file is in the folder I'm opening the command window from and named recovery.img .
Click to expand...
Click to collapse
ok then flash it again with fastboot command
don't use the tool
then from bootloader select recovery
rzr86 said:
ok then flash it again with fastboot command
don't use the tool
then from bootloader select recovery
Click to expand...
Click to collapse
Sorry - can you explain exactly how and what I should flash again? I'm just a little unclear.
kellai15 said:
Sorry - can you explain exactly how and what I should flash again? I'm just a little unclear.
Click to expand...
Click to collapse
as you are in the folder with cmd window opened do
fastboot flash recovery recovery.img
fastboot reboot bootloader
then from bootloader select recovery
i assume you still have the recovery.img in the folder
rzr86 said:
as you are in the folder with cmd window opened do
fastboot flash recovery recovery.img
fastboot reboot bootloader
then from bootloader select recovery
i assume you still have the recovery.img in the folder
Click to expand...
Click to collapse
That worked!! I realized I had renamed the recovery file 'recovery.img' instead of just 'recovery)" (the second .img was redundant) which is why it wouldnt find the file. Anyway, it's rooted now!
You are the best! Thanks so much for helping a newbie out
kellai15 said:
That worked!! I realized I had renamed the recovery file 'recovery.img' instead of just 'recovery)" (the second .img was redundant) which is why it wouldnt find the file. Anyway, it's rooted now!
You are the best! Thanks so much for helping a newbie out
Click to expand...
Click to collapse
congratulations mate
but i suggest you to have 4ext recovery instead of cwm because of the smartflash feature(for S-ON devices only)
as i understand you are on S-ON
rzr86 said:
congratulations mate
but i suggest you to have 4ext recovery instead of cwm because of the smartflash feature(for S-ON devices only)
as i understand you are on S-ON
Click to expand...
Click to collapse
I have now flashed 4ext and installed a customROM! Couldn't have done it without your help

Fix Unrecoverable bootloader error[Buster99 Solution]

Hello ,
First of all Thanks to Buster99 and his Solution for fixing this problem,
This guide is for helping you to fix Unrecoverable bootloader error, Hope it will help you out of this problem,
Step-by-step guide:
1 - Download the Stock rom .
2 - Extract downloaded file and put the blob file in fastboot folder.
3 - if you need adb,apx,fastboot drivers , i attached these drivers so you can download it from below.
4- Power off the tablet.
5- Connect the tablet to PC via USB cable.
6- Boot your tablet into the recovery mode. Press and hold Volume DOWN+Power keys together.
7- Open command prompt. For this, go to Start. Select ‘Run’ and type ‘cmd’. go to your fastboot folder.
8- type following command-lines in cmd-window:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system blob(depending on where you stored extracted blob file)
fastboot -i 0x0B05 reboot
Remember : Wait until you've seen in the CMD window that erase or upload is finished.
hope this solution works for whoever is facing the same problem,
I'm very glad, you saved your tablet

Just upgraded to LOS 14.1 unofficial from MM - this is how

Thought I would make a thread, which could help someone.
My bootloader is unlocked
I was using Marshmallow LOS 13 unofficial build by Qbanin.
But these directions should be the same for anyone on MM unlocked.
You will need to know how to use ADB from PC and have platform-tools.
The reason I upgraded to 14.1 unofficial instead of official is because official requires the MM modem, and I had already flashed the stock nougat rom when i started looking for roms to flash.
Download the Nougat Stock Firmware:
https://androidfilehost.com/?fid=889964283620765304
Drop the contents of unzipped stock nougat into your platform-tools folder.
Hit the shift button and right click the mouse and 'open command window here'
Connect your MM device to your pc - booted into your current rom with usb debugging enabled
In the command windows type 'adb devices', you may need to confirm access on the screen of your phone, and try the command again.
Make sure your device is listed and authorized.
Type in the command window 'adb reboot bootloader'
Your device will reboot into the bootloader and is ready to program
Run these commands to flash stock nougat, make sure each command succeeds.
If they do not, run any command that fails multiple times until it succeeds and move on to the next, if a command fails more than 5-10 times in a row, start over from the beginning.
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata -w
fastboot reboot
If your device reboots into bootloader repeatedly run this command:
fastboot oem fb_mode_clear
fastboot reboot
Your device will reboot, wait a while during Nougats first run.
Once Nougat is loaded and you pass setup, enable developer options and then ADB usb debugging.
run 'adb devices' command again and confirm the device is listed and authorized.
Download latest official TWRP 3.2.1.0
https://eu.dl.twrp.me/clark/
rename the file to twrp.img and place in the platform-tools folder
Download LOS 14.1 Unofficial (the latest build 2/23 is for MM modem: avoid)
Grab the 2/18 build or read around the forums for latest compatible build
https://androidfilehost.com/?w=files&flid=131793
Move the file to the root of your external sd card via MTP.
Download ARM64 7.1 OpenGapps and move to root of your external sd card
http://opengapps.org/
Run these commands in the command prompt
adb reboot bootloader
adb flash recovery twrp.img
Press 'down vol' for the recovery option and then press the power button
Phone should reboot into TWRP recovery
Allow TWRP to modify contents by swiping at the bottom.
Remember TWRP makes you swipe if your screen shuts off, so you may need to swipe twice to peform operations, ALWAYS PAY ATTENTION IN TWRP.
Select WIPE in twrp, and then ADVANCED WIPE.
Select the Data checkbox and hit the Repair or Change File System at bottom.
Select CHANGE FILE SYSTEM at bottom right.
Select F2FS and proceed with the format.
Select WIPE (again) from home screen choose to wipe dalvik,system,internal & cache
Select INSTALL from home screen and choose the LineageOS 14.1 build.
You will need to SELECT STORAGE at bottom left and choose your external card.
Add the openGapps 7.1 to the install queue as well.
Swipe to confirm flash and let the new rom and gapps install.
After complete wipe dalvik/cache and reboot.
Enjoy your new rom.
I also flashed systemless root in twrp.
https://drive.google.com/file/d/1GjKdxvoTi9YCU43HIy2XTTcB-bGnNn84/view?usp=sharing
This is for unofficial 14.1 only using the 2/10 or 2/18 build only.
The 2/23 build as I understand is a test build for MM modem only.
All future builds should be verified around the forum with hashbangs notes/recommendations as they do not exist at the time of this post.

Boot Loop in Recovery mode unable to start

ach time i Restart my pixel it open recovery mode with two option :
try again or factory data reset but on choosing any of option it do same again .
to resolve this i try to flash image using flash-all.sh script with both android o and android p Preview
but it show following error :
extracting system.img (1752 MB) to disk...W/ziparchive(30294): Zip: unable to allocate 1837265176 bytes at offset 0: No space left on device
error:
failed to extract 'system.img': I/O error
to resolve this i do extract zip and run following command one by one on slot a:
1) fastboot flash bootloader bootloader-sailfish-8996-012001-1711291800.img
2) fastboot flash radio radio-sailfish-8996-130091-1802061512.img
3) fastboot reboot-bootloader
4) fastboot flash boot boot.img
5) fastboot flash system system.img
6) fastboot reboot
but after reboot it reach to recovery mode with again two option
then i try above six command with both slot a and b but same thing happen on reboot
please help!!!

General P11 plus 616f installation rom gsi + root

Start by downloading the official stock rom. If you had a problem with the installation or just want to go back to the original usage
Flash SP Tools
- download the latest version of Android sdk platform-tools
- Put in the platform-tools folder your boot.img and vbmeta.img that you have copied from your previously downloaded official rom.
- Then download the generic system image you want to install, put it in the platform-tools folder and rename it GSI.img
- Put your smartphone in developer mode, in the settings press 7 times on the build number
- In the menu Options for developers that appeared, you must enable OEM unlocking, enable USB debugging
- Connect the smartphone to the computer, in Configuration usb choose Connection sharing via usb
accept the requested authorization on your smartphone,
- In the platform-tools folder enter the command
adb reboot bootloader
fastboot flashing unlock Press VOL+ to confirm
fastboot flashing unlock_critical Press VOL+ to confirm
fastboot --disable-verification flash boot boot.img
fastboot --disable-verify flash vbmeta vbmeta.img
fastboot -w
fastboot reboot fastboot The tel switch to FastbootD mode and wait for a moment before entering the following command
fastboot delete system
fastboot delete-logical-partition product_a
fastboot --disable-verity --disable-verification system flash Gsi.img Wait for a moment
fastboot -w
fastboot bootloader
fastboot delete user data
fastboot reboot
Lenovo then logo rom gsi and install
evolutionx rom
Releases · ponces/treble_build_evo
Script and patches for building PHH-Treble Evolution X - ponces/treble_build_evo
github.com
rom lenovo and flashtool 616f
https://mirrors.lolinet.com/firmware/lenovo/Tab_P11_Plus/TB-J616F/TB-J616F_S240155_230210_ROW_SVC.zip
https://mirrors.lolinet.com/firmware/lenovo/Tab_P11_Plus/flashtool/MTK_Flash_Tool_v5.2104_P522.zip
Last tested rom that works
https://private.projectelixiros.com/thirteen/gsi/ProjectElixir_3.6_gsi-13.0-20230223-1108-OFFICIAL.img.xz
Root lenovo 616f
Install the Magisk app to your phone and install
In the Options menu, enable both the Preserve Force Encryption and Recovery Mode options.
Choose Select and Patch a file.
Browse to the extracted boot.img file and select it.
Magisk will now load the boot.img file and start patching.
Then the patched patched boot image file will be saved as magisk_patched.img in Internal Storage Downloads.
The file will be named as magisk_patched.img.
Transfer the magisk_patched.img file to the platform-tools folder.In the platform-tools folder enter the command
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
successfully rooted
Magisk 25.2
https://github.com/topjohnwu/Magisk/releases/download/v25.2/Magisk-v25.2.apk
Can you make a video to review that rom on p11
It has only one flaw,
The PC does not recognize the tablet, it can only be charged, files cannot be transferred and adb does not work either.

Categories

Resources