Database Info

[Q][D2303] How to root with unlocked bootloader?

Hi guys! Im on 4.4.4 with unlocked bootloader, the only way to root this device that i found on the internet is to use locked bootloader tutorials.
Is there any easy way to root unlocked bootloader D2303 on 4.4.4 18.3.1.C.1.15? I tried flashtool but when it installs towel root and i press make it rain! it says this device is not supported. Thanks in advance!

Here is one easiest way, but its over chinese app called KingRoot.
1. Download latest KingRoot.
2. Press Root button
3. Allow USB debug in Developer settings(Tap 10 times in Phone info on Build number to get Dev. settings)
4. Install Philz Recovery
5. Flash SuperSU V.249 BETA! Important!
6. Flash RICDefeat.zip
Same way is described here
http://forum.xda-developers.com/xperia-m2/general/how-to-permanently-root-xperia-m2-t3106534
But dont forget to flash SuperSU V2.49 BETA and RICDefeat & remove KingRoot apps.

Lothgar said:
Hi guys! Im on 4.4.4 with unlocked bootloader, the only way to root this device that i found on the internet is to use locked bootloader tutorials.
Is there any easy way to root unlocked bootloader D2303 on 4.4.4 18.3.1.C.1.15? I tried flashtool but when it installs towel root and i press make it rain! it says this device is not supported. Thanks in advance!
Click to expand...
Click to collapse
Update your bootloader using emma, then flash a recovery like CM12.1 Recovery from here: http://www.mediafire.com/download/lfub133wy5833bx/recovery.img and flash with it SuperSU zip and RICdefeat. Then you're done.
---------- Post added at 12:06 ---------- Previous post was at 12:05 ----------
Enycz11 said:
Here is one easiest way, but its over chinese app called KingRoot.
1. Download latest KingRoot.
2. Press Root button
3. Allow USB debug in Developer settings(Tap 10 times in Phone info on Build number to get Dev. settings)
4. Install Philz Recovery
5. Flash SuperSU V.249 BETA! Important!
6. Flash RICDefeat.zip
Same way is described here
http://forum.xda-developers.com/xperia-m2/general/how-to-permanently-root-xperia-m2-t3106534
But dont forget to flash SuperSU V.249 BETA and RICDefeat & remove KingRoot apps.
Click to expand...
Click to collapse
Actually that's a locked bootloader method.
And Kingroot also sends your IMEI info to chinese unknown servers...

linuxct said:
Update your bootloader using emma, then flash a recovery like CM12.1 Recovery from here: http://www.mediafire.com/download/lfub133wy5833bx/recovery.img and flash with it SuperSU zip and RICdefeat. Then you're done.
---------- Post added at 12:06 ---------- Previous post was at 12:05 ----------
Actually that's a locked bootloader method.
And Kingroot also sends your IMEI info to chinese unknown servers...
Click to expand...
Click to collapse
Thanks! Trying right now!

linuxct said:
Update your bootloader using emma, then flash a recovery like CM12.1 Recovery from here: http://www.mediafire.com/download/lfub133wy5833bx/recovery.img and flash with it SuperSU zip and RICdefeat. Then you're done.
---------- Post added at 12:06 ---------- Previous post was at 12:05 ----------
Actually that's a locked bootloader method.
And Kingroot also sends your IMEI info to chinese unknown servers...
Click to expand...
Click to collapse
Wait! How to flash recovery? Via flashtool by androxyde or emma?
EDIT: Tryed via fastboot the cm12 recovery, all what i got is grey screen with blue lines yey.

Lothgar said:
Wait! How to flash recovery? Via flashtool by androxyde or emma?
EDIT: Tryed via fastboot the cm12 recovery, all what i got is grey screen with blue lines yey.
Click to expand...
Click to collapse
But you have to do a fastboot flash recovery recovery.img . Did you do that ?

linuxct said:
But you have to do a fastboot flash recovery recovery.img . Did you do that ?
Click to expand...
Click to collapse
Yep.

Lothgar said:
Yep.
Click to expand...
Click to collapse
Then there's no reason to happen that. The lines appear when you boot it normally or when you try to enter recovery by keep holding the Vol- button?
In my D2303 is fine working...

linuxct said:
Then there's no reason to happen that. The lines appear when you boot it normally or when you try to enter recovery by keep holding the Vol- button?
In my D2303 is fine working...
Click to expand...
Click to collapse
The phone is off. I press the power button it vibrates, then for 5-6 second the screen is black. Then the lines shows up and no boot. Vol- pressed or not is the same.
EDIT: Reflashed now only if i try to enter recovery the lines shows up!

Lothgar said:
The phone is off. I press the power button it vibrates, then for 5-6 second the screen is black. Then the lines shows up and no boot. Vol- pressed or not is the same.
Click to expand...
Click to collapse
Go in fastboot mode and run fastboot erase recovery .
Again, I see no reason why this could be happening as this recovery runs in it's partition, isolated, so if you don't run it (Vol- button from the beggining) then it should not interfere with device boot up. Try flashing the latest kernel from the .15 ftf also.

linuxct said:
Go in fastboot mode and run fastboot erase recovery .
Again, I see no reason why this could be happening as this recovery runs in it's partition, isolated, so if you don't run it (Vol- button from the beggining) then it should not interfere with device boot up. Try flashing the latest kernel from the .15 ftf also.
Click to expand...
Click to collapse
I reflashed the recovery trough fastboot and now only if i try to boot recovery the blue lines shows up. I think that is a problem of the recovery.

Lothgar said:
I reflashed the recovery trough fastboot and now only if i try to boot recovery the blue lines shows up. I think that is a problem of the recovery.
Click to expand...
Click to collapse
Maybe is a screen driver problem, but on a D2303?? For me it's working

linuxct said:
Maybe is a screen driver problem, but on a D2303?? For me it's working
Click to expand...
Click to collapse
I remember that you gave me and alternative recovery for the locked bootloader becouse the standard doesn't working. Maybe the same issue?

Lothgar said:
I remember that you gave me and alternative recovery for the locked bootloader becouse the standard doesn't working. Maybe the same issue?
Click to expand...
Click to collapse
No, it shouldn't as the problem only was the GPIO Keys... Not screen driver problem... But yes, looks like you can't use the CM Recovery.
Format your fastboot partition with fastboot erase recovery and use the locked bootloader procedure... What a pity.

linuxct said:
No, it shouldn't as the problem only was the GPIO Keys... Not screen driver problem... But yes, looks like you can't use the CM Recovery.
Format your fastboot partition with fastboot erase recovery and use the locked bootloader procedure... What a pity.
Click to expand...
Click to collapse
I'll try but i dont know how to get the root because the procedure of downgrading the kernel doesn't work i tryed several times!
Here what i got:

Lothgar said:
I'll try but i dont know how to get the root because the procedure of downgrading the kernel doesn't work i tryed several times!
Here what i got:
Click to expand...
Click to collapse
But that pic is from CM recovery or from kernel downgrade?
And in what step you get stuck in the kernel downgrade root method?...

linuxct said:
But that pic is from CM recovery or from kernel downgrade?
And in what step you get stuck in the kernel downgrade root method?...
Click to expand...
Click to collapse
CM recovery. If i downgrade the kernel the adb doesn't start! And yes is enabled in the settings.
EDIT: Solved trying now for the locked bootloader method!

Installed philz recovery with locked bootloader method but i cant flash omnirom! (status 7)

Can Nokia 3 root

Hello guys i have Nokia 3 and i want to root it can i root it without any problems and after root can I recieve updates and am able to install it successfully?

I need help
I unlocked the bootloader, Thanks to the_laser, but... I can´t install any recovery, I´ve looking many options, and I can´t
Can yo help me, giving me the link here or by private message.
I need to root my nokia 3 ta-1028 please.
Thanks a lot

xdrucsix said:
I unlocked the bootloader, Thanks to the_laser, but... I can´t install any recovery, I´ve looking many options, and I can´t
Can yo help me, giving me the link here or by private message.
I need to root my nokia 3 ta-1028 please.
Thanks a lot
Click to expand...
Click to collapse
twrp is available only for ta-1032, sorry about that, you need to wait for someone to port it.

SkaboXD said:
twrp is available only for ta-1032, sorry about that, you need to wait for someone to port it.
Click to expand...
Click to collapse
Oh, Ok I can see, I have to wait :/

is there any difference between ta-1028 and ta-1032 in TWRP view ?
it is easy to try just boot into recovery - "fastboot boot <recovery.img>"

the_laser said:
is there any difference between ta-1028 and ta-1032 in TWRP view ?
it is easy to try just boot into recovery - fastboot boot recovery <recovery.img>
Click to expand...
Click to collapse
i know that ta-1032 is for EU dual sim, ta-1028 is american single sim version but i think that there is no difference in hardware. he can try that command to see is that recovery works @xdrucsix
Steps:
first download twrp if you didn't
rename recovery to recovery.img and move it to platform-tools
open cmd as administrator
type location of platform-tools
boot to fastboot
type command
fastboot boot recovery.img
then you will see does it boot or not. twrp will disappear completely after you exit twrp.

I did every step that you say, nothing happened :/

something should definitely happen
at least show all fastboot.exe output during your tries

SkaboXD said:
twrp is available only for ta-1032, sorry about that, you need to wait for someone to port it.
Click to expand...
Click to collapse
The twrp dint even work for 1032..

Mithra siva said:
The twrp dint even work for 1032..
Click to expand...
Click to collapse
it worked for me and others, which method you tried?

SkaboXD said:
it worked for me and others, which method you tried?
Click to expand...
Click to collapse
The method you have mentioned only.. it was showing writing ..'recovery' failed..
---------- Post added at 12:53 PM ---------- Previous post was at 12:49 PM ----------
SkaboXD said:
it worked for me and others, which method you tried?
Click to expand...
Click to collapse
The method you have mentioned only..
It was showing ." Writing 'recovery'...failed (remote size too large)... Please help

SkaboXD said:
it worked for me and others, which method you tried?
Click to expand...
Click to collapse
Bro say something

Mithra siva said:
Bro say something
Click to expand...
Click to collapse
try this
Steps:
first download twrp if you didn't
rename recovery to recovery.img and move it to platform-tools
open cmd as administrator
type location of platform-tools
boot to fastboot
type command
fastboot boot recovery.img

SkaboXD said:
try this
Steps:
first download twrp if you didn't
rename recovery to recovery.img and move it to platform-tools
open cmd as administrator
type location of platform-tools
boot to fastboot
type command
fastboot boot recovery.img
Click to expand...
Click to collapse
How to type location..I have kept it in root folder of (E)
---------- Post added at 05:16 AM ---------- Previous post was at 05:00 AM ----------
SkaboXD said:
try this
Steps:
first download twrp if you didn't
rename recovery to recovery.img and move it to platform-tools
open cmd as administrator
type location of platform-tools
boot to fastboot
type command
fastboot boot recovery.img
Click to expand...
Click to collapse
Can you please send again...how to install twrp..with twrp link indetail.. I go for a last try..

Mithra siva said:
How to type location..I have kept it in root folder of (E)
---------- Post added at 05:16 AM ---------- Previous post was at 05:00 AM ----------
Can you please send again...how to install twrp..with twrp link indetail.. I go for a last try..
Click to expand...
Click to collapse
link for twrp
https://1drv.ms/u/s!AsmTb5aqoY12mDZqDZbPOp47QVMV
when downloaded, copy twrp to folder platform-tools and rename it to recovery.img
to type platform-tools location, type this:
chdir C:/Users/John/Desktop/platform-tools (this is just a example, you need to type your own location of platform-tools)
reboot to recovery
adb reboot recovery
then reboot to bootloader (fastboot) by pressing volume keys.
to flash recovery type this command:
fastboot flash recovery recovery.img
then reboot, fastboot reboot
if it didn't worked, use this command just to boot to twrp (you need to do this everytime when you are connected to PC)
fastboot boot recovery.img
To install root, first disable system modification on twrp then flash this zip for root.
This is not the latest version of SuperSU, but newest releases have some problems and crashes. (at least for me). This is last version that works for me.
That is it.

SkaboXD said:
link for twrp
https://1drv.ms/u/s!AsmTb5aqoY12mDZqDZbPOp47QVMV
when downloaded, copy twrp to folder platform-tools and rename it to recovery.img
to type platform-tools location, type this:
chdir C:/Users/John/Desktop/platform-tools (this is just a example, you need to type your own location of platform-tools)
reboot to recovery
adb reboot recovery
then reboot to bootloader (fastboot) by pressing volume keys.
to flash recovery type this command:
fastboot flash recovery recovery.img
then reboot, fastboot reboot
if it didn't worked, use this command just to boot to twrp (you need to do this everytime when you are connected to PC)
fastboot boot recovery.img
To install root, first disable system modification on twrp then flash this zip for root.
This is not the latest version of SuperSU, but newest releases have some problems and crashes. (at least for me). This is last version that works for me.
That is it.
Click to expand...
Click to collapse
Thanks man it's done..
---------- Post added at 03:35 PM ---------- Previous post was at 03:33 PM ----------
Mithra siva said:
Thanks man it's done..
Click to expand...
Click to collapse
Now can I relock my Bootloader with root..if i can please instruct me
And again thanks a lot

Mithra siva said:
Thanks man it's done..
---------- Post added at 03:35 PM ---------- Previous post was at 03:33 PM ----------
Now can I relock my Bootloader with root..if i can please instruct me
And again thanks a lot
Click to expand...
Click to collapse
no, you can't have locked bootloader and root, after locking bootloader you need to reflash .nb0 file with OST because locking bootloader don't just remove data, it removes whole ROM.

SkaboXD said:
no, you can't have locked bootloader and root, after locking bootloader you need to reflash .nb0 file with OST because locking bootloader don't just remove data, it removes whole ROM.
Click to expand...
Click to collapse
I can't able to remove the system apps even after root..I used system app remover (root) ..
Help

Mithra siva said:
I can't able to remove the system apps even after root..I used system app remover (root) ..
Help
Click to expand...
Click to collapse
did you rebooted after uninstalling system apps?

SkaboXD said:
did you rebooted after uninstalling system apps?
Click to expand...
Click to collapse
It was showing uninstalling failed

[GUIDE][Nougat & Oreo] How to flash TWRP and Magisk with locked bootloader

Before following guide check this:
If you never unlocked bootloader or you flashed Android 7.1.1 nb0 with locked bootloader, then you need to go back to Android 7.0, after that unlock then lock bootloader. If you want to update, use OTA, don't flash nb0 because it have stock LK inside.
Here is the explanation why:
bigrammy said:
In theory and put simply as possible it should not work on a never unlocked before device if the LK does it's job properly.
The LK does all the checking down the secure boot chain prior to allowing the recovery or boot.img to boot.
If a device has been officially Unlocked then the LK should write (normally hidden) 1 bite identifiers to partitions like secro, misc, oem, etc etc (Depends on the OEM where and how) so when you flash a new ROM the new LK should still look for these bite's and if it see's them then it will allow the none stock .img's like twrp to boot normally.
So to sum up
1. Nokia made a huge screw up and the Nokia 3 is a totally insecure device like most of cheap MediaTek Chinese phone's out there.
2. The LK knows the bootloader was officially Unlocked before and therefore ignores the secure boot chain.
Click to expand...
Click to collapse
Downloads:
SP Flash Tool:
https://spflashtool.com/download/
VCOM Drivers:
https://spflashtool.com/download/MediaTek_USB_VCOM_drivers.zip
Scatter file (extracted from nb0, use this scatter to avoid renaming issue):
https://mega.nz/#!qJh1TSLL!5afi-7NYqKT3H62tqBISYSAdBDgN6eIM20WRSbtq3qE
Compatible DA (Download Agent):
https://mega.nz/#!xd8B3AJQ!PW82IpLzMzyNQk55BdwMnRMPlKQA0Yzj_8k_xN5r9XM
Stock boot.img and Stock recovery.img:
https://forum.xda-developers.com/nokia-3/development/link-stock-boot-img-stock-recovery-img-t3785576
TWRP 3.1.0-0 by mediafire007:
https://onedrive.live.com/?authkey=...126&parId=768DA1AA966F93C9!3122&action=locate
TWRP 3.2.1-0 by SkaboXD:
https://mega.nz/#!qIhFkKia!AkUMvQJ0PGVnSePabTvOgO-oUAMZahlCNaZfy2gE4vE
Magisk ZIP:
https://github.com/topjohnwu/Magisk/releases/download/v16.0/Magisk-v16.0.zip
Magisk Manager APK:
https://github.com/topjohnwu/MagiskManager/releases/download/v5.7.0/MagiskManager-v5.7.0.apk
unSU script:
https://forum.xda-developers.com/attachment.php?attachmentid=4410561&d=1517853382
First Step: Installing and setting SP Flash Tools
Install VCOM Drivers (video tutorial): https://youtube.com/watch?v=w3whZ2QMGvo
Then extract SP Flash Tool to Desktop. Open extracted folder and open flash_tool.exe. Create new folder on Desktop and call it ''magisk twrp sp flash tool'' or something like that and move scatter to that folder. Then go back to SP Flash Tool and load scatter file. Close SP Flash Tool. Now copy/move DA_SWSEC_CRYPTO20.bin (Compatible DA that you downloaded) and replace it to sp flash tool folder. Then open sp flash tool and load DA that you replaced.
Second Step: Flashing TWRP and Magisk
Extract twrp to ''magisk twrp sp flash tool'' folder. Rename it to NE1-0-215H-00WW-recovery so SP Flash Tool can recognize it. Turn off your phone. Now open SP Flash Tool, tick recovery, select Download only mode and click Download. Hold power + vol up button at the same time and quickly connect phone to USB. Then it will go to META mode and downloading will begin first with red bar and second with yellow bar. When download completes, green tick/circle mark will appear. Now you have TWRP. Rename NE1-0-215H-00WW-recovery to twrp-recovery.img so you can remember file name.
If you don't have root, just flash Magisk ZIP with TWRP.
If you have SuperSU and you want to switch to Magisk, flash unSU script with TWRP which uninstalls SuperSU, then you need to flash stock boot.img. Switch from install zip to install image and click on stock boot.img. Tick boot partition and flash. When it's done with flashing, you can flash Magisk.
OPTIONAL
If you are for some reason scared to flash TWRP or don't want to mess with recovery partition, this is step for you.
Second Step: Flashing Magisk without touching recovery partition
If you want to switch from SuperSU to Magisk, unroot SuperSU in SuperSU options. Transfer stock boot.img to your device from PC. Go to your phone and install Magisk Manager APK and open it. Click install then click "Patch boot image file" then select stock boot.img then it starts downloading Magisk ZIP and patching boot.img. You will get patched_boot.img in /sdcard/MagiskManager. Now transfer stock boot.img and patched boot.img back to PC and move it to "magisk twrp sp flash tool" folder. Rename stock boot.img to NE1-0-215H-00WW-boot. Turn off your phone. Now open SP Flash Tool, tick boot, select Download only mode and click Download. Hold power + vol up button at the same time and quickly connect phone to USB. Then it will go to META mode and downloading will begin first with red bar and second with yellow bar. When download completes, green tick/circle mark will appear. Close SP Flash Tool. Rename NE1-0-215H-00WW-boot to stock-boot.img and rename patched-boot.img to NE1-0-215H-00WW-boot. Turn off your phone. Now open SP Flash Tool, tick boot, select Download only mode and click Download. Hold power + vol up button at the same time and quickly connect phone to USB. Then it will go to META mode and downloading will begin first with red bar and second with yellow bar. When download completes, green tick/circle mark will appear. TA-DA you have Magisk root. Rename NE1-0-215H-00WW-boot to patched-boot.img so you can remember file name.
What about OTA?:
If you want to have OTA updates, remember to flash stock recovery back if you flashed TWRP. With installed update you will not lose:
- Data (apps, internal storage data)
- Xposed framework (if flashed directly to system)
- Xposed modules
you will lose:
- Magisk
- Magisk modules
- Xposed framework (if you flashed it systemlessly)
To gain root, just flash Magisk again.
Comment if links need to be updated.
Credits:
@sp flash Tool developers for providing SP Flash Tool
@blackpanther0582 for nb0 and scatter file
@Max brackenz for Download Agent
@mediafire007 for TWRP
@topjohnwu for Magisk
@osm0sis for unSU script
@bigrammy for useful tips

I very happy to hearing a New Guide to root Nokia 3 ^^
---------- Post added at 05:47 PM ---------- Previous post was at 05:44 PM ----------
I will try it when I get up

Does the boot.img work regardless of whether one is on nougat or Oreo?

redweaver said:
Does the boot.img work regardless of whether one is on nougat or Oreo?
Click to expand...
Click to collapse
both boot.img work, i tested.

Try to flash official firmware 7.0 via SPFlashTool with uncheck in preloader and use Download Only, then my Phone just virable
---------- Post added at 08:41 AM ---------- Previous post was at 08:03 AM ----------
ERROR: S_BROM_CMD_STARTCMD_FAIL (0x7D5)
[BROM] Can not pass bootrom start command! Possibly target power up too early
[HINT]:

Elvaa said:
Try to flash official firmware 7.0 via SPFlashTool with uncheck in preloader and use Download Only, then my Phone just virable
---------- Post added at 08:41 AM ---------- Previous post was at 08:03 AM ----------
ERROR: S_BROM_CMD_STARTCMD_FAIL (0x7D5)
[BROM] Can not pass bootrom start command! Possibly target power up too early
[HINT]:
Click to expand...
Click to collapse
You inserted USB late, try again

You inserted USB late, try again
Click to expand...
Click to collapse
Not good. I was know that before you comment. But I use format tab, with default choose, I click start. It successfully. Now I can't see the Phone virable
---------- Post added at 10:11 AM ---------- Previous post was at 09:29 AM ----------
Except the Bootloader Format selected
---------- Post added at 10:15 AM ---------- Previous post was at 10:11 AM ----------
My Windows found Ports COM (when Plugin phone with PC). I try Remove cable, click Download, press UP volume + Power button, Insert cable. But It show AUTH_HANDLE_IS_NOT_READY. Then I click Download again, it show me the ERROR similar after I using format tab

Elvaa said:
Not good. I was know that before you comment. But I use format tab, with default choose, I click start. It successfully. Now I can't see the Phone virable
---------- Post added at 10:11 AM ---------- Previous post was at 09:29 AM ----------
Except the Bootloader Format selected
---------- Post added at 10:15 AM ---------- Previous post was at 10:11 AM ----------
My Windows found Ports COM (when Plugin phone with PC). I try Remove cable, click Download, press UP volume + Power button, Insert cable. But It show AUTH_HANDLE_IS_NOT_READY. Then I click Download again, it show me the ERROR similar after I using format tab
Click to expand...
Click to collapse
Not good,never use format unless you know what you're doing . You can try and see if you can flash OST , if that doesn't work, there's a post by SkaboXD on recovering his phone using spflashtool. Hopefully one of those methods will work

I may found my problem. I can't authentic by hand for my phone. Because If I press UP + Power button, It said ERROR s_auth_handle_is_not_ready (5000). If then I click download again, it said ERROR ERROR: S_BROM_CMD_STARTCMD_FAIL (0x7D5) if I still press two button too up to 7sec. It said similar ERROR when I click download and remove cable
---------- Post added at 10:40 AM ---------- Previous post was at 10:38 AM ----------
redweaver said:
Not good,never use format unless you know what you're doing . You can try and see if you can flash OST , if that doesn't work, there's a post by SkaboXD on recovering his phone using spflashtool. Hopefully one of those methods will work
Click to expand...
Click to collapse
Except Bootloader

Works in variant TA-1028 on official Oreo. Great guide tnx

I waited a week for this guide when I saw you talking to each other in the Nokia 3 TWRP thread..
And when I lost hope that you're going to make the thread I had to break down what you were saying amd make my own way..
It took me 6 hours to get all the tools and files and figure it out..
Thank you anyways <3

Any video tutorials for this? Iam a noob

DHruV07 said:
Any video tutorials for this? Iam a noob
Click to expand...
Click to collapse
currently no, but it would be great if someone make it.

Is there any slowdowns with the magisk ? Can it run viper4android as module afterwards?
Thank you skabo as always!
Thank you

Nikola Jovanovic said:
Is there any slowdowns with the magisk ? Can it run viper4android as module afterwards?
Thank you skabo as always!
Thank you
Click to expand...
Click to collapse
Thanks bro,
No slowdowns, it even works better than SuperSU. For example i couldn't install Nethunter because SuperSU misses some lib for sh execution. With Magisk it works perfectly.
Also you have magisk modules unlike SuperSU (i didn't tested it though).

Nice Tread.
It will be interesting to see if this works for someone who as never unlocked the bootloader previously which is why I held off since there were no volunteers to test it.

bigrammy said:
It will be interesting to see if this works for someone who as never unlocked the bootloader previously which is why I held off since there were no volunteers to test it.
Click to expand...
Click to collapse
Me too.
Thank you

bigrammy said:
It will be interesting to see if this works for someone who as never unlocked the bootloader previously which is why I held off since there were no volunteers to test it.
Click to expand...
Click to collapse
well it should work for them too, but where to find someone who never unlocked bootloader.

SkaboXD said:
well it should work for them too, but where to find someone who never unlocked bootloader.
Click to expand...
Click to collapse
I've never unlocked a Nokia (HMD) device bootloader and to be honest, after reading all the issues and problems some have been having trying to unlock their Nokia 3's, I don't think I want to try.
I am getting very frustrated about the fact my TA 1020 (UK) is still stuck on Android 7.1.1 and the march security update.
I've tried all the hacks suggested like taking the Sim out and resetting, connecting to Indian vpns and pressing check for updates every hour over a 14 hour period.
My Nokia 3 is an unlocked (Sim free) version as well.

bubba1601 said:
I've never unlocked a Nokia (HMD) device bootloader and to be honest, after reading all the issues and problems some have been having trying to unlock their Nokia 3's, I don't think I want to try.
I am getting very frustrated about the fact my TA 1020 (UK) is still stuck on Android 7.1.1 and the march security update.
I've tried all the hacks suggested like taking the Sim out and resetting, connecting to Indian vpns and pressing check for updates every hour over a 14 hour period.
My Nokia 3 is an unlocked (Sim free) version as well.
Click to expand...
Click to collapse
did you cleaned Google services data after that?

How Root My XZP with Pie

I lose the Root after update to Pie
then i can't find my device by using the "adb devices"
How to Root for Magisk ?

@shoey63 , please guide, have you rooted your XZP ? (on PIE)

YasuHamed said:
@shoey63 , please guide, have you rooted your XZP ? (on PIE)
Click to expand...
Click to collapse
Just flash Magisk 17.3 in TWRP. No DRM fix needed for camera on Pie either. Rooted on Pie right now with my source built dttw kernel [emoji41]

After update: Does you have enabled the Developer menu, activate the adb debugging?
During try a connection via PC to the mobile, you must confirm on the cell phone , that you trust your PC

shoey63 said:
Just flash Magisk 17.3 in TWRP. No DRM fix needed for camera on Pie either. Rooted on Pie right now with my source built dttw kernel [emoji41]
Click to expand...
Click to collapse
its there any guide i have pie 47.2.a.6.30 i really need how to intall twrp en xzp dual

please help y cant use fastboot i tried use adb but when i type fastboot devices, nothing happen.
please help me with the twrp

evermyself said:
its there any guide i have pie 47.2.a.6.30 i really need how to intall twrp en xzp dual
Click to expand...
Click to collapse
Plenty of guides out there, no need for a new one.
Making sure device is authorised and correct drivers are installed would be a good start.

i download and debugmode its activated when i try adb devices work fine but fastboot no what i doing wrong, i already tried in another pc bith have windows 10 pro
i dont know what else can try

evermyself said:
i download and debugmode its activated when i try adb devices work fine but fastboot no what i doing wrong, i already tried in another pc bith have windows 10 pro
i dont know what else can try
Click to expand...
Click to collapse
Try zadig https://zadig.akeo.ie/
So you can do this :
Download the tool, start it.
Select the "S1Boot fastboot" device
Select the WinUSB Driver
Click Install
And then*fastboot devices*list your device

there is not any S1Boot fastboot i check there only in list all devices, then android (libusbk, lisbusb-win32, usb serial , Winusb)
what im doing wrong?
im already conected my xperia xzp fastboot mode (green light) , and device manager only say sony sa0116 adb interface but still with the yellow triangle

Fastboot is blue light. Volume up + insert usb

shoey63 said:
Fastboot is blue light. Volume up + insert usb
Click to expand...
Click to collapse
and traied to but not listed with fastboot devices...

finally its listed but now i dont know what to do , maybe download twrp and flash white the following
line : fastboot flash recovery (name.img), then flash boot.img? srry but ims so close please help
---------- Post added at 04:28 AM ---------- Previous post was at 04:21 AM ----------
ok i already flashed whit the following line fastboot flash recovery twrp.img and fastboot reboot (everything goes fine) the phone reboot fine,
but thenhow can i enter the recovery mode ?
---------- Post added at 04:33 AM ---------- Previous post was at 04:28 AM ----------
evermyself said:
finally its listed but now i dont know what to do , maybe download twrp and flash white the following
line : fastboot flash recovery (name.img), then flash boot.img? srry but ims so close please help
---------- Post added at 04:28 AM ---------- Previous post was at 04:21 AM ----------
ok i already flashed whit the following line fastboot flash recovery twrp.img and fastboot reboot (everything goes fine) the phone reboot fine,
but thenhow can i enter the recovery mode ?
Click to expand...
Click to collapse
ok i figuret google dont hurt thanks now im goin to install magisk
thanks for all your help srry again for my bad english im from argentina
oh by the way my error was port com3 has a android driver installed , i unistalled and used fastool drivers utility then everything goes well.
---------- Post added at 04:45 AM ---------- Previous post was at 04:33 AM ----------
here me again its there any mode to quit the lock img from the boot ?

When you unlock, the warning with a lock symbol is permanent.

looks like thts all now im searching a way for use titanium back up, but looks i cant and pokemon go never come back for my phone... sad day no way to downgrade google play services, no way to quite a lock symbol pie really sucks

Magisk Settings - repackage Magisk manager with a random name.
Magisk hide - select Pokemon Go.
But why aren't you googling all this?
XDA isn't a place to come to be spoon-fed.
Edit: Not that I care but you have not thanked a single helpful post.

shoey63 said:
Magisk Settings - repackage Magisk manager with a random name.
Magisk hide - select Pokemon Go.
But why aren't you googling all this?
XDA isn't a place to come to be spoon-fed.
Edit: Not that I care but you have not thanked a single helpful post.
Click to expand...
Click to collapse
i already done all like package magisk whit another name , but works just for a while then just come a advice say device not compatible but you right anyway, thanks a lots, and yes you care lol.... thanks for help buddy really you are great
but looks like i have to downgrade for play pokemon go ,sad day
---------- Post added at 04:16 PM ---------- Previous post was at 04:13 PM ----------
Magisk hide - select Pokemon Go., and thats looks like nol work fine because i check int magisk and its cant check safety net

s8 unique rom???

No single blackview s8 unique rom

MTom said:
No single blackview s8 unique rom
Click to expand...
Click to collapse
Nope.
Im trying to root this device but no success. Did you manage to root it?

mellowbug said:
Nope.
Im trying to root this device but no success. Did you manage to root it?
Click to expand...
Click to collapse
I have not tried
maybe it works
https://www.getdroidtips.com/twrp-recovery-on-blackview-s8-root/
this is my primary phone, I can't experiment.

MTom said:
I have not tried
maybe it works
https://www.getdroidtips.com/twrp-recovery-on-blackview-s8-root/
this is my primary phone, I can't experiment.
Click to expand...
Click to collapse
That tutorial is fake. As far as i know this device has no working fastboot/bootloader mode. With the device connected : adb reboot bootloader / fastboot the device just restarts and charging.
And reboot bootloader from within the recovery it just turns off.
So basically every tut. that even mentions fastboot (regarding the blackview s8) is fake.. click bait, copy paste lies.
It has verified boot (avb 1.0 according to magisk) and dm-verity. So i cant even flash the patched boot.img.
Im stuck. Any thoughts?
Btw. Did you came across or do you know a way to get the device into bootloader / fastboot mode?

mellowbug said:
That tutorial is fake. As far as i know this device has no working fastboot/bootloader mode. With the device connected : adb reboot bootloader / fastboot the device just restarts and charging.
And reboot bootloader from within the recovery it just turns off.
So basically every tut. that even mentions fastboot (regarding the blackview s8) is fake.. click bait, copy paste lies.
It has verified boot (avb 1.0 according to magisk) and dm-verity. So i cant even flash the patched boot.img.
Im stuck. Any thoughts?
Btw. Did you came across or do you know a way to get the device into bootloader / fastboot mode?
Click to expand...
Click to collapse
Unfortunately I can not help. sorry

no one can know root access

MTom said:
I have not tried
maybe it works
https://www.getdroidtips.com/twrp-recovery-on-blackview-s8-root/
this is my primary phone, I can't experiment.
Click to expand...
Click to collapse
Those trick doesn't work, most post the probably automated copy paste bs just for the click bait topic. It causing my phone to stuck at boot following that tutorial. I'll ended reflash my phone. mine not s8 but a9 pro.
All i wanted i to root my phone so i can use firewall app, but i think blackview is a minority in the market so no one bother to make custom rom for it.

MTom said:
No single blackview s8 unique rom
Click to expand...
Click to collapse
Hey, i own Blackview A60 Pro and the answer is quietly no, Blackview does not make the device trees public for their devices.
Sure a developer could make these but their devices are not popular enough.
On my A60 Pro I run AOSP GSI (Generic System Images) tremble from phhusson with magisk root.
There are also unofficial LinageOS GSI Images available maybe you could try these.
---------- Post added at 08:46 PM ---------- Previous post was at 08:38 PM ----------
mellowbug said:
That tutorial is fake. As far as i know this device has no working fastboot/bootloader mode. With the device connected : adb reboot bootloader / fastboot the device just restarts and charging.
And reboot bootloader from within the recovery it just turns off.
So basically every tut. that even mentions fastboot (regarding the blackview s8) is fake.. click bait, copy paste lies.
It has verified boot (avb 1.0 according to magisk) and dm-verity. So i cant even flash the patched boot.img.
Im stuck. Any thoughts?
Btw. Did you came across or do you know a way to get the device into bootloader / fastboot mode?
Click to expand...
Click to collapse
Have you tried to disconnect the cable after you hit the command "adb reboot bootloader"?
You can easily disable verified boot with "fastboot --disable-verification flash vbmeta vbmeta.img" when you can acces fastboot....

str8unknown said:
Hey, i own Blackview A60 Pro and the answer is quietly no, Blackview does not make the device trees public for their devices.
Sure a developer could make these but their devices are not popular enough.
On my A60 Pro I run AOSP GSI (Generic System Images) tremble from phhusson with magisk root.
There are also unofficial LinageOS GSI Images available maybe you could try these.
---------- Post added at 08:46 PM ---------- Previous post was at 08:38 PM ----------
Have you tried to disconnect the cable after you hit the command "adb reboot bootloader"?
You can easily disable verified boot with "fastboot --disable-verification flash vbmeta vbmeta.img" when you can acces fastboot....
Click to expand...
Click to collapse
Hi, I have a Blackview A80 Pro, and I unlocked the bootlader but I can't install TWRP, can you help me?