Database Info

need help flashing recovery

I went ahead and did the oem unlock but when I try and flash the recovery (or boot) image through fastboot using this:
C:\androidsdk\tools\fastboot flash recovery XXXXXXX.img
or
C:\androidsdk\tools\fastboot flash boot rootboot.img
I keep getting this error:
error: cannot load 'XXXXXXX.img'
I've trouble shooted all of the main things. ...my device is definitely attached. I have the recovery .img file in the same folder as fastboot (along with the 2 needed .dll files). I've also done stuff like re-install usb drivers, re-install sdk, I've oem unlocked 3 times.
I have a stock wifi xoom with 3.2
Here are the 2 main root guides I've been using
http://forum.xda-developers.com/showthread.php?t=1170760&highlight=how+to+root
http://forum.xda-developers.com/showthread.php?t=1242241&highlight=how+to+root
Thank you for your help

in cmd(assuming windows) type cd c:/•••••tools
your xoom should be in adb reboot bootloader
type fastboot flash recovery recovery.img
rename recovery file as recovery.img and place in tools/platformtools as the case may be.
sending this message from stock xoom.

awesome, thanks. What you told me was enough to show me what I was doing wrong.
In case someone else reads this later on I had to type
cd C:\androidsdk\tools ...hit enter
then it looked like this
C:\androidsdk\tools> ...and I then typed
fastboot flash recovery XXXX.img
earlier I also renamed the folder to androidSDK from android-sdk

[Q] Erased recovery

Help Ive erased recovery and im not really experienced with fastboot I was trying to install clockworkmod and ended up deleting recovery please help ive got the kernal image from ASus but it is tar.gz please help im so confused I cant update or flash custom rom now its a nightmare just got this 2 or 3 days ago

4SHR4F said:
Help Ive erased recovery and im not really experienced with fastboot I was trying to install clockworkmod and ended up deleting recovery please help ive got the kernal image from ASus but it is tar.gz please help im so confused I cant update or flash custom rom now its a nightmare just got this 2 or 3 days ago
Click to expand...
Click to collapse
So I assumed that your device is unlocked? I recommend to flash twrp, more easier and works wellstart with section 2).
http://forum.xda-developers.com/showthread.php?p=32825557

how did you delete recovery?
cyanogen mod forum has a good wiki on fastboot.

buhohitr said:
So I assumed that your device is unlocked? I recommend to flash twrp, more easier and works wellstart with section 2).
http://forum.xda-developers.com/showthread.php?p=32825557
Click to expand...
Click to collapse
I followed this thread before it says Scott's TF700T Recovery Install tool V1.0
www.scottsroms.com
Congrats! You now have a custom Recovery installed on the official
JB release by Asus!
From here you can install a custom ROM or simply root the stock ROM.
The choice is yours!
Thank you for using my Recovery Install Tool!
Please visit www.scottsroms.com!
Donations Greatly Appreciated but Never Expected!
But when I boot into recovery I get Un recoverable bootloader error (0x00000000)
Also when I used the program it does the first reboot but not the second I dont know why? Please HELP

4SHR4F said:
I followed this thread before it says Scott's TF700T Recovery Install tool V1.0
www.scottsroms.com
Congrats! You now have a custom Recovery installed on the official
JB release by Asus!
From here you can install a custom ROM or simply root the stock ROM.
The choice is yours!
Thank you for using my Recovery Install Tool!
Please visit www.scottsroms.com!
Donations Greatly Appreciated but Never Expected!
But when I boot into recovery I get Un recoverable bootloader error (0x00000000)
Also when I used the program it does the first reboot but not the second I dont know why? Please HELP
Click to expand...
Click to collapse
I don't think you did it correctly, first boot you should see the 4 icons and you need to hit the volume down button on your device (within 10sec) to select USB icon then hit the volume up button to select this setting, now proceed with the instruction on your pc to flash. Make sure you copy the recovery twrp file named" openrecovery-twrp-2.3.1.0-tf700t.blob" from here http://goo.im/devs/OpenRecovery/tf700t to the "install Recovery" folder and RENAME this file to recovery.blob

buhohitr said:
I don't think you did it correctly, first boot you should see the 4 icons and you need to hit the volume down button on your device (within 10sec) to select USB icon then hit the volume up button to select this setting, now proceed with the instruction on your pc to flash. Make sure you copy the recovery twrp file named" openrecovery-twrp-2.3.1.0-tf700t.blob" from here http://goo.im/devs/OpenRecovery/tf700t to the "install Recovery" folder and RENAME this file to recovery.blob
Click to expand...
Click to collapse
OK last time im trying this wish me luck
Edit: Same problem grrrrrr it says its sent hasnt reboot my device as well so have to do it manually and still says same error

4SHR4F said:
OK last time im trying this wish me luck
Edit: Same problem grrrrrr it says its sent hasnt reboot my device as well so have to do it manually and still says same error
Click to expand...
Click to collapse
Sounds like your pc is not communicate correctly with your device. When your device is on and you execute Scott's bat file, is your device reboot into recovery so that you can select fastboot mode? Basically, Scott bat file is using adb command to reboot your device into recovery mode, you manually select and enable fast boot mode on your device, then the script is using fastboot command to push the recovery.blob (located in the same directory as Scott bat file) to your device.

buhohitr said:
Sounds like your pc is not communicate correctly with your device. When your device is on and you execute Scott's bat file, is your device reboot into recovery so that you can select fastboot mode? Basically, Scott bat file is using adb command to reboot your device into recovery mode, you manually select and enable fast boot mode on your device, then the script is using fastboot command to push the recovery.blob (located in the same directory as Scott bat file) to your device.
Click to expand...
Click to collapse
Yes it reboots the first time allowing me to go into recovery but then doesnt reboot second after it writes the recovery files dont know why fastboot works thats why I can delete recovery but writing is a problem :~

4SHR4F said:
Yes it reboots the first time allowing me to go into recovery but then doesnt reboot second after it writes the recovery files dont know why fastboot works thats why I can delete recovery but writing is a problem :~
Click to expand...
Click to collapse
And you did select the USB icon and the text displayed "fastboot" on your device? You also have the twrp renamed to recovery.blob in the same folder as the script? Let manually push this file using fastboot.exe and see what's happens.

buhohitr said:
And you did select the USB icon and the text displayed "fastboot" on your device? You also have the twrp renamed to recovery.blob in the same folder as the script? Let manually push this file using fastboot.exe and see what's happens.
Click to expand...
Click to collapse
With fastboot same problem when I load from command prompt it sends the file however if I do it without starting from that directory it says file not found but fastboot devices show the number should I make a video and send it

4SHR4F said:
With fastboot same problem when I load from command prompt it sends the file however if I do it without starting from that directory it says file not found but fastboot devices show the number should I make a video and send it
Click to expand...
Click to collapse
don't trust the log from fastboot or any script. Just make sure the recovery.blog is in the same directory of the fastboot command and you must execute fastboot.exe from command prompt.
1. manually boot to fastboot mode from your device. (boot to recovery then select USB icon)
2. Open command prompt and run as admin and navigate to fastboot.exe directory (with recovery.blog in this directory also)
3. type;
fastboot.exe -i 0x0B05 flash recovery recovery.blob
4. Once done, type
fastboot -i 0x0B05 reboot
Let me know the status.

buhohitr said:
don't trust the log from fastboot or any script. Just make sure the recovery.blog is in the same directory of the fastboot command and you must execute fastboot.exe from command prompt.
1. manually boot to fastboot mode from your device. (boot to recovery then select USB icon)
2. Open command prompt and run as admin and navigate to fastboot.exe directory (with recovery.blog in this directory also)
3. type;
fastboot.exe -i 0x0B05 flash recovery recovery.blob
4. Once done, type
fastboot -i 0x0B05 reboot
Let me know the status.
Click to expand...
Click to collapse
This is what I get recovery.blob is in the folder and fastboot works as I can delete recovery just not write for some reason
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
H:\Users\Install user>cd C:\Fastboot
H:\Users\Install user>fastboot devices
015d262e99141416 fastboot
H:\Users\Install user>fastboot.exe -i 0x0B05 flash recovery recovery.blob
error: cannot load 'recovery.blob': No error
H:\Users\Install user>
Also I would also like to point out it does not let me reboot after I write the files (using holding shift key and opening command prompt) as it freezes I think??? BEcause I can reboot from fastboot before I input writing flash recovery but after it wont allow don't know why?

4SHR4F said:
This is what I get recovery.blob is in the folder and fastboot works as I can delete recovery just not write for some reason
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
H:\Users\Install user>cd C:\Fastboot
H:\Users\Install user>fastboot devices
015d262e99141416 fastboot
H:\Users\Install user>fastboot.exe -i 0x0B05 flash recovery recovery.blob
error: cannot load 'recovery.blob': No error
Click to expand...
Click to collapse
Did you even notice that you didn't change to drive C: before calling fastboot? Is your recovery.blob in C:\Fastboot or in "H:\Users\Install user"?

_that said:
Did you even notice that you didn't change to drive C: before calling fastboot? Is your recovery.blob in C:\Fastboot or in "H:\Users\Install user"?
Click to expand...
Click to collapse
Yes I know but my command prompt is awkward either way ive tried using Android flasher but I find the problem is my device freezes while writing files dont know why

4SHR4F said:
Yes I know but my command prompt is awkward either way ive tried using Android flasher but I find the problem is my device freezes while writing files dont know why
Click to expand...
Click to collapse
Try this, copy the recovery.blob to this directory:
H:\Users\Install user\
Then type dir then hit enter, make sure your fastboot.exe and recovery.blob are there
H:\Users\Install user> dir then hit enter
Should show both fastboot.exe and recovery.blob
Now execute the fastboot command to push the recovery.blob

buhohitr said:
Try this, copy the recovery.blob to this directory:
H:\Users\Install user\
Then type dir then hit enter, make sure your fastboot.exe and recovery.blob are there
H:\Users\Install user> dir then hit enter
Should show both fastboot.exe and recovery.blob
Now execute the fastboot command to push the recovery.blob
Click to expand...
Click to collapse
Same problem says its sent and that it is written but after if I try to reboot the tablet doesn't respond and cant go into recovery because of that error 0x00000000
All I want to do is get UBuntu and Clean ROM on my Tablet then no more modding

OK I give up with command prompt can I use Odin or some other software to flash recovery or at least flash a custom rom from windows rather then twrp or cwm boatloaders or can I get ubuntu and do it through ubuntu any possibilities helpful please

4SHR4F said:
OK I give up with command prompt can I use Odin or some other software to flash recovery or at least flash a custom rom from windows rather then twrp or cwm boatloaders or can I get ubuntu and do it through ubuntu any possibilities helpful please
Click to expand...
Click to collapse
Nope, no Odin, but if your device is rooted, you could download goomanager from the market and install twrp using goomanager app.

buhohitr said:
Nope, no Odin, but if your device is rooted, you could download goomanager from the market and install twrp using goomanager app.
Click to expand...
Click to collapse
What about install linux without root and from there send in the recovery that way will that work

4SHR4F said:
What about install linux without root and from there send in the recovery that way will that work
Click to expand...
Click to collapse
You can be the first one to try...it may or may not works, but the methods I provided proved by many that they worked.

[Q] Flashable zip to install CWM Recovery?

I have TWRP recovery installed right now but I want to switch back to cwm as I'm more familiar with it. My laptop's usb ports died so I can't use adb to install it. Is there a zip I can install in my current recovery?

No but you can do it from terminal emulator from the play store if you don't have one installed..
The command is in the CWM first post - TWRP can be flashed this way too.

All I see is a command for fastboot. Do I need to download the sdk or fastboot directly to my tablet? I would think I could just copy it over to the recovery partition instead since I'm already in the tablet. I thought fastboot was just used to gain access via a pc?

Organized_Chaos said:
All I see is a command for fastboot. Do I need to download the sdk or fastboot directly to my tablet? I would think I could just copy it over to the recovery partition instead since I'm already in the tablet. I thought fastboot was just used to gain access via a pc?
Click to expand...
Click to collapse
CWM:
Download and rename the file to recovery-jb-touch.img
Fastboot method from a PC:
fastboot -i 0x0B05 flash recovery recovery-jb-touch.img
fastboot -i 0x0B05 reboot
OR
In Terminal Emulator on the device, type the following
su
dd if=recovery-jb-touch.img of=/dev/block/mmcblk0p4
TWRP:
Download and rename the file to twrp.blob
Fastboot method from a PC:
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot
OR
In Terminal Emulator, type the following
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot to complete installation.

Need help to root into moto g3

Hi Team,
I was able to unlock the bootloader on motg3 and do a twrp img. However when I ran the command
adb reboot recovery it doesn't boot into the recovery img and it just says no command on the phone screen. Please help.
Thanks,
Arun

'No Command' means you've still got the stock recovery. Flash TWRP again by:
Code:
fastboot flash recovery twrp.img
(Where twrp.img is the filename of the custom recovery).
Do *not* reboot the phone into system, instead scroll down to select 'recovery' and press power button to load TWRP.
TWRP should load now, swipe to confirm modification (important). Now go to reboot>recovery. Allow the phone to reboot back to TWRP. Now you can select reboot>system and TWRP shall stick permanently.
Broadcasted from Zeta Reticuli

Volume buttons aren't working on the mobile. So I tried adb reboot recovery. But still it didn't boot into recovery. Here is what I had tried.
https://pasteboard.co/HhTTVr1n.png

TWRP will be overwritten by stock recovery if the system is booted up before booting TWRP once.
If the volume buttons are broken, then I'd suggest you first copy twrp.img into phone memory, boot the recovery by :
Code:
fastboot boot recovery.img
Allow modifications, then go to Install>Select Image (img), browse twrp.img on phone>select 'recovery' and swipe to flash.
Now reboot>recovery and then reboot>system. Now it should stick.
I'd recommend being extra careful if your volume button, especially volume down button is broken. If you somehow end up with a non-booting phone, you'd have no way (that I know of) to get to the bootloader mode.
Broadcasted from Zeta Reticuli

I tried fastboot boot recovery.img but it says waiting for device and nothing happens.
https://pasteboard.co/HhVmOD9.png

Make sure your phone is in the bootloader mode and is being recognized by the pc. Run:
Code:
fastboot devices
and make sure it returns with 1 entry of the device along with the text 'fastboot'. Then the command should work.
Broadcasted from Zeta Reticuli

arunkumar413 said:
Hi Team,
I was able to unlock the bootloader on motg3 and do a twrp img. However when I ran the command
adb reboot recovery it doesn't boot into the recovery img and it just says no command on the phone screen. Please help.
Thanks,
Arun
Click to expand...
Click to collapse
Make sure you have installed proper Motorola drivers & Fastboot on you're PC / laptop,
You can get those files from this thread https://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
After installing proper drivers goto this thread https://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537 download & flash latest twrp by given instructions by OP..

I just checked the usb drivers page but there aren't any usb drivers for Linux.
https://mobilesupport.lenovo.com/us/en/solution/MS88481
I tried the command sudo fastboot boot recovery.img and it returned there is no such file or directory. Should recovery file be on phone or on the laptop. Also should all these commands be run from a specific folder either on phone or system?
[email protected] ~ $ sudo fastboot boot recovery.img
cannot load 'recovery.img': No such file or directory
[email protected] ~ $

arunkumar413 said:
I just checked the usb drivers page but there aren't any usb drivers for Linux.
https://mobilesupport.lenovo.com/us/en/solution/MS88481
I tried the command sudo fastboot boot recovery.img and it returned there is no such file or directory. Should recovery file be on phone or on the laptop. Also should all these commands be run from a specific folder either on phone or system?
[email protected] ~ $ sudo fastboot boot recovery.img
cannot load 'recovery.img': No such file or directory
[email protected] ~ $
Click to expand...
Click to collapse
Yes, the terminal should be open to the directory containing the recovery.img file. For simplicity, place twrp into your home folder. The default location for most terminals is home, so no worries about directory now.
Just to be sure, type in :
Code:
ls
(LS lowercase)
Your file should be in the list. You are ready to flash now.
Try the fastboot boot command again.
As you're using GNU/Linux (guessed it early from your screenshots), drivers should not be a problem, at least for this device; unless you are running a minimal or highly customised distro like Gentoo or Arch.
Note: And yes, you'll need another copy of TWRP inside phone storage to actually flash into the device, the PC one is just used to boot temporarily into TWRP.
Broadcasted from Zeta Reticuli

To add more clarity. There are two files here:
1) recovery.img
2)twrp.img
I was able to get the twrp.img file but where do I get the recovery.img file?

Hi All,
Thanks for all the help. I'm now able to root into the device.

arunkumar413 said:
To add more clarity. There are two files here:
1) recovery.img
2)twrp.img
I was able to get the twrp.img file but where do I get the recovery.img file?
Click to expand...
Click to collapse
I apologize for confusing you. They are the one and same. Just rename the downloaded TWRP img file to twrp.img and copy it over to both home folder in pc and into phone.
Use fastboot boot command on pc to temporarily boot up twrp in phone, allow modifications by swiping, go to Install>Install Image (img) option on the bottom>select the twrp.img inside the phone and flash it to 'recovery' partition.
Now reboot>recovery. This time the twrp should be permanently flashed and working properly. You are done.
Edit: Didn't see your last post, glad that you worked it out
Broadcasted from Zeta Reticuli

arunkumar413 said:
To add more clarity. There are two files here:
1) recovery.img
2)twrp.img
I was able to get the twrp.img file but where do I get the recovery.img file?
Click to expand...
Click to collapse
There can be only one either recovery.img file or twrp.img.....as you are trying to replace your stock recovery by TWRP... And you need .img file for this.... Just check the name there should be just one if you have TWRP.img then there is no need for recovery.img file

Hi All,
After I was able to flash twrp and root into the phone I switched off the phone and turned on after couple of days. But now the display isn't turning on. However adb is able to detect the device and also I was able to access the file system through usb. Could you please help me troubleshoot the display issue?

arunkumar413 said:
Hi All,
After I was able to flash twrp and root into the phone I switched off the phone and turned on after couple of days. But now the display isn't turning on. However adb is able to detect the device and also I was able to access the file system through usb. Could you please help me troubleshoot the display issue?
Click to expand...
Click to collapse
Try rebooting into the recovery mode by:
Code:
adb reboot recovery
And doing a Cache/ART cleanup.
If the phone boots up (it should vibrate) but the screen doesn't light up (not even a blank dark grey screen), then I'm afraid the display is at fault.

How to root moto g3
I try to root my motor but network has gone
Then how I root

How To Flash Global Firmware (( PL2-222E-0-00WW-B02 )) Nokia6.1

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