Database Info

[Q] URGENT! bootloop cm11 not recognised by pc in fastboot

followed the regular procedure. unlocked the bootloader via motorola, flash cwm recovery and used it to install cm11 falcon rom. its not stuck on bootloop on the cm logo. i can still access fastboot and recovery but when plugged into usb it makes 3 dongs(low pitch and computer does not find device. tried to reflash stock via moto g allinone tool and it says waiting for device.
please explain it simply, im a noob-didnt make a backup either
also, left charging overnight and would not power on at all this morning, no screen, no LED and wouldnt boot to fastboot. fixed by plugging in and holding power for 2 mins

Is there an unkown device in your device manager in windows?
If, then your USB drivers are not installed properly.

mokkami said:
Is there an unkown device in your device manager in windows?
If, then your USB drivers are not installed properly.
Click to expand...
Click to collapse
device manager>other devices>fastboot falcon s>double click>
device type: other devices
manufacturer: unknown
The drivers for this device are not installed. (Code 28)
There is no driver selected for the device information set or element.
To find a driver for this device, click Update Driver.
what can i do, i have motorola device manager installed?

acko2011 said:
device manager>other devices>fastboot falcon s>double click>
device type: other devices
manufacturer: unknown
The drivers for this device are not installed. (Code 28)
There is no driver selected for the device information set or element.
To find a driver for this device, click Update Driver.
what can i do, i have motorola device manager installed?
Click to expand...
Click to collapse
it now says android on device manager, but still says could not find device software?

They are still not working?
At the beginning i also had the same problem mit the Motorola Device Manager. And some others also.
Since then i am using koush's Universal ADB drivers without any problem.
Edit:
But maybe it is the same as with the koush driver. I have not tested it afterwards.
You have to istall them from Device Manager manually again.
From device manager install the drivers new, i guess you'll find them in the Motorola Device Manager installation folder.

just set this installing, do i need to install it to a specific location?
and can i use the moto allinone tool to flash stock/gpe devices to stop this bootloop?

acko2011 said:
just set this installing, do i need to install it to a specific location?
and can i use the moto allinone tool to flash stock/gpe devices to stop this bootloop?
Click to expand...
Click to collapse
installed, its now finding the device and says installing device software when running cwm recovery, but still not recognising device in fastboot mode?

acko2011 said:
just set this installing, do i need to install it to a specific location?
Click to expand...
Click to collapse
No.
and can i use the moto allinone tool to flash stock/gpe devices to stop this bootloop?
Click to expand...
Click to collapse
Yes. You can restore your GPE device. But atm not the NON-GPE.
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
When device in Fastboot mode go to your Device Manager. Install new driver > Go to installation folder of Universal adb driver and search the......ahm, not sure atm......winusb.inf or something.

Did you try rebooting your pc? I had this kind of problem, but a reboot fixed it.

mokkami said:
No.
Yes. You can restore your GPE device. But atm not the NON-GPE.
Click to expand...
Click to collapse
ive installed, its making a connection on recovery but not fastboot. and in either it still says waiting for device on cmd?

acko2011 said:
ive installed, its making a connection on recovery but not fastboot. and in either it still says waiting for device on cmd?
Click to expand...
Click to collapse
The driver must be installed twice. Once for ADB and once for Fastboot.
---------- Post added at 07:18 PM ---------- Previous post was at 07:16 PM ----------
If you have Team viewer i can help you.....if you want.
I'll leave in 15 mins.
---------- Post added at 07:20 PM ---------- Previous post was at 07:18 PM ----------
Or try what mvs1989 said.

mokkami said:
The driver must be installed twice. Once for ADB and once for Fastboot.
---------- Post added at 07:18 PM ---------- Previous post was at 07:16 PM ----------
If you have Team viewer i can help you.....if you want.
I'll leave in 15 mins.
Click to expand...
Click to collapse
im so lost here when trying to manually install the driver it says not compatible for the motorola part.
i dont have a teamviewer, what is it and how do i get it?

http://www.teamviewer.com/en/index.aspx
No need to install. When double clicking it ask you if install or just start. Then just start and pm me your connection Number and pw which TV ptrovides you.
EDIT:
Sorry i can not use it here on this PC, it is blocked by the administrator.
But i have the older 8 version. They now offer the Version 9. The versions must be same if connecting.
So either you have to download the 8 version also on that site........or try to install driver as i said.
I did that in the same way on W8.1
Shaftenberg also told in his thread, that the drivers need to be installed twice. !!!Note the file does not need anymore to be modified. The version you downloaded is already updated.
6. let Windows install this driver from koush's directory once in adb mode and once in fastboot mode (two drivers!)
Click to expand...
Click to collapse

mokkami said:
http://www.teamviewer.com/en/index.aspx
No need to install. When double clicking it ask you if install or just start. Then just start and pm me your connection Number and pw which TV ptrovides you.
EDIT:
Sorry i can not use it here on this PC, it is blocked by the administrator.
But i have the older 8 version. They now offer the Version 9. The versions must be same if connecting.
So either you have to download the 8 version also on that site........or try to install driver as i said.
I did that in the same way on W8.1
Click to expand...
Click to collapse
ill pm you a link, tell me which file i need please

Sony Xperia E5 F3311 [Root][Guide][Twrp]

After a lot of struggles, we've finally managed to root the Sony Xperia E5.
If you own this device and would like to root it, this thread will guide you through the process.
Requirements:
-You must have the correct drivers installed!
You can't proceed without them as the adb interface won't recognize your device.
-The modified boot.img for 37.0.A.2.156 which you can download here
-The modified boot.img for 37.0.A.2.248 which you can download here
-Twrp recovery which you can download here
-The adb interface, google it.
-Your bootloader must be unlocked via the Sony official method. If you can't find the E5 in the list, you can use the code of the E4g.
-Supersu 2.79 zip which you can download here
-An equal kernel (boot.img) to your desired firmware version. 37.0.A.2.156+37.0.A.2.156 or 37.0.A.2.248+37.0.A.2.248.
-The no-verity encryption fix (optional): (link to be added)
-30 minutes of your time.
I'm not responsible for any possible damage caused to your phone, even though it most likely won't go wrong if you follow the instructions carefully.
I can, however, provide support if your device is stuck in a bootloop.
I won't reply to questions, of which the answers are already mentioned in this thread.
YOU MUST MAKE SURE YOU'VE DOWNLOADED THE KERNEL THAT IS MEANT FOR YOUR SPECIFIC FIRMWARE VERSION!
IF THE TWO AREN'T EQUAL, YOU'LL HARD BRICK YOUR DEVICE AND YOU'LL HAVE TO AGREE THAT I WON'T BE HELD RESPONSIBLE!
Instructions:
1. Unlock your bootloader, check out Sony's website to see how.
2. Check whether the boot unlock succeeded or not.
To do so, you can open your dialer and type *#*#7378423#*#* .
A screen will appear, tap on service info and go to configuration.
Check the rooting status:
*If it says 'bootloader unlock allowed=yes' it means your bootloader is still locked.
*If it says 'bootloader unlocked=yes' it means your bootloader is unlocked.
3. Install the correct drivers for your device, Sony adb+fastboot etc.
4. Go to the root directory of your adb folder, location depending of where you installed it.
Hold Shift and right click to show a menu.
In that menu there should be an option called 'open command prompt here', click on it and it should start adb.
5. Make sure to enable usb debugging on your device.
6. Connect your phone to your computer and type this command in adb:
Code:
adb devices
If your device shows up, it means adb recognized your device and you may proceed.
If it doesn't show up you have to double check your installed drivers in device manager.
7. Type
Code:
adb reboot bootloader
to reboot the device to fastboot.
8. Now you'll have to flash the kernel and recovery.
Put both of the files into the root directory of the adb folder and rename them to boot.img and recovery.img, type
Code:
fastboot flash boot boot.img
to flash the kernel and type
Code:
fastboot flash recovery recovery.img
to flash the recovery.
9. Unplug your device and boot into twrp by pressing the power+volume down buttons. Keep holding the volume down button and release the power button quickly.
10. When you're in twrp, head to 'wipe'->'advanced wipe'->'(user)data partition'.
This step is optional, but recommended to avoid problems with encryption.
Update: the forced encryption has proven to bring limitations and issues to the recovery and system.
The updated steps are now mandatory!
11. Now head to 'install', browse to the directory in which you saved the supersu zip file and flash/install it.
12. Flash the latest version of the encryption fixed no-verity-opt-encrypt zip file, which can be downloaded from here
At first I made my own fix zip file, but I lost it and lot's of other projects, so the above file is a workaround.
13. If the installation succeeds, you may reboot your device.
Please be patient, the first boot may take a while.
It will reboot during the initialization, so don't panic and think it's a bootloop, cause it simply isn't.
I hope this has helped people with rooting their Sony Xperia E5.
I'm here if you need support, unless it's something dumb and/or already mentioned.
UPDATE APRIL 2018
A new modified kernel is available for the latest firmware 37.0.A.2.248!
The rooting process is the same as written above, but instead of flashing the older kernel and firmware, you'll have to flash the new ones.
Be warned, you cannot flash any newer kernel on an older firmware version and the other way around!
The kernel and firmware versions always have to be equal, no exceptions.
An advantage of flashing the newer kernel is that it should support Magisk, while the previous one didn't.
If you want to root your device with Magisk, or install both Magisk and Supersu, the rooting instructions will differ.
You can find new instructions here: (Link to the thread to be added!)
~A special thanks to rrvuhpg and Tu_Angel

Thank you a lot! It worked and now I have my E5 rooted:good::good:

How is the camera quality after unlocking bootloader ?

Tried it last night and it works. Thank you!

wardonz said:
How is the camera quality after unlocking bootloader ?
Click to expand...
Click to collapse
It's exactly the same, the camera works well in all resolutions, video recording seems to be fine too.

Hello, Im stuck in the process of unlock bootloader, im doing all step by step but i couldnt resolve this error:
Code:
C:\Users\Cristian\AppData\Local\Android\Sdk\platform-tools>fastboot devices
RQ3001L5W7 fastboot
C:\Users\Cristian\AppData\Local\Android\Sdk\platform-tools>fastboot -i 0x0fce oe
m unlock 0xA55381B959C2CA7B
...
FAILED (remote: Command not allowed)
finished. total time: 0.029s
Help, Thank you.

CrStN224 said:
Hello, Im stuck in the process of unlock bootloader, im doing all step by step but i couldnt resolve this error:
Code:
C:\Users\Cristian\AppData\Local\Android\Sdk\platform-tools>fastboot devices
RQ3001L5W7 fastboot
C:\Users\Cristian\AppData\Local\Android\Sdk\platform-tools>fastboot -i 0x0fce oe
m unlock 0xA55381B959C2CA7B
...
FAILED (remote: Command not allowed)
finished. total time: 0.029s
Help, Thank you.
Click to expand...
Click to collapse
You must enable oem unlocking in developer options.
To do this you'll have to go to settings, tap on about device and tap build number 5 times in a row.
This will enable the developer options on your device.
Now go to the developer options in settings and make sure oem unlocking is checked.
Now try to unlock the bootloader again.
It should work now, but if it doesn't, you'll have to check your drivers.

It worked perfectly, I had to restore everything because my phone turned on with fabric presets, but the technology saved me, my phone automatically did a backup this morning. Thanks!

CrStN224 said:
It worked perfectly, I had to restore everything because my phone turned on with fabric presets, but the technology saved me, my phone automatically did a backup this morning. Thanks!
Click to expand...
Click to collapse
Unlocking the bootloader always deletes all your data, I'm glad you've made a backup.
So did you manage to root it?

Well, right now im officially Rooted, but unsucesfully... My device is detected by Root Checker like a rooted device, but I dont know why some apps dont recoignize it. I have two apps what works with root:
- The first one ask me for root permissions but says dont detect root...
- The another app dont ask me and dont recoignize it...
But that everything looks fine, i dont know whats the issue.

CrStN224 said:
Well, right now im officially Rooted, but unsucesfully... My device is detected by Root Checker like a rooted device, but I dont know why some apps dont recoignize it. I have two apps what works with root:
- The first one ask me for root permissions but says dont detect root...
- The another app dont ask me and dont recoignize it...
But that everything looks fine, i dont know whats the issue.
Click to expand...
Click to collapse
That's odd, do you see the supersu app in your app drawer?
If not, install it from the play store and within the app update the su binary.
Also make sure that in supsersu settings, superuser is enabled and that mount namespace seperation is disabled.
Let me know if that worked out with you

I confirm you thats all ok, i dont know how to resolve the issue...

CrStN224 said:
Well, right now im officially Rooted, but unsucesfully... My device is detected by Root Checker like a rooted device, but I dont know why some apps dont recoignize it. I have two apps what works with root:
- The first one ask me for root permissions but says dont detect root...
- The another app dont ask me and dont recoignize it...
But that everything looks fine, i dont know whats the issue.
Click to expand...
Click to collapse
Hi, if you use Magisk try to disable build in Busybox and install it from Playstore app. It solve the problem on some devices.

OK, I downloaded Magisk and Busybox, I wish I have all the requirements for use any root app! I will reply again if Im done, Thank you!
---------- Post added at 09:30 PM ---------- Previous post was at 09:23 PM ----------
Okay, it works at least, but the apps "CIH" and "No-frills CPU Control" doesnt work for me.
---------- Post added at 09:30 PM ---------- Previous post was at 09:30 PM ----------
Okay, it works at least, but the apps "CIH" and "No-frills CPU Control" doesnt work for me.

CrStN224 said:
OK, I downloaded Magisk and Busybox, I wish I have all the requirements for use any root app! I will reply again if Im done, Thank you!
---------- Post added at 09:30 PM ---------- Previous post was at 09:23 PM ----------
Okay, it works at least, but the apps "CIH" and "No-frills CPU Control" doesnt work for me.
---------- Post added at 09:30 PM ---------- Previous post was at 09:30 PM ----------
Okay, it works at least, but the apps "CIH" and "No-frills CPU Control" doesnt work for me.
Click to expand...
Click to collapse
No-frills cpu control didn't work on mine either, I replaced it with kernel adiutor.
Besides, you can tweak a lot more in it than in no-frills

mrmarvin_16 said:
-The modified boot.img which you can download here-link
....
~A special thanks to rrvuhpg for the kernel
Click to expand...
Click to collapse
Hello.
Why do we need to flash modified kernel?
Isn't recovery just enough for installing supersu zip onto system partition?

freedom74 said:
Hello.
Why do we need to flash modified kernel?
Isn't recovery just enough for installing supersu zip onto system partition?
Click to expand...
Click to collapse
Flashing only the recovery will result into a bootloop.
As this is a newer device, some kernel patches are required due to dm-verity, bootcheck, etc.
Also make sure to first flash the kernel and then the kernel afterwards to finish the rooting process successfully.
Good luck.

Please! Need Help Fast
Need Help !!! I'm stucked at point 8. After i typed in comand 7. my phone goes into fastboot okay... but then i got two Problems: First one is that i didnt really understand where to put the two files you named.
Second one is that after i typed in command 8. the cmd says >waiting for device< and i can't type in anything anymore.
while my second problem my phone is in fastboot: the blue light in the left top corner is on and the screen is on and has the color black. please help me fast THANK YOU !!!

Wlans Theme said:
Need Help !!! I'm stucked at point 8. After i typed in comand 7. my phone goes into fastboot okay... but then i got two Problems: First one is that i didnt really understand where to put the two files you named.
Second one is that after i typed in command 8. the cmd says >waiting for device< and i can't type in anything anymore.
while my second problem my phone is in fastboot: the blue light in the left top corner is on and the screen is on and has the color black. please help me fast THANK YOU !!!
Click to expand...
Click to collapse
You haven't done anything wrong so far.
The two downloaded files must be placed in your adb folder
You must rename the kernel into boot.img and the recovery into recovery.img
Try to then re-enter the commands of step 8.
If it still says waiting for device it means you'll need to check if you have the proper drivers installed in device manager.
If you really want to turn your device off for now, you can long press the volume up+volume down+power buttons at the same time so your device will turn itself off.

I need help
After unlocking the bootloader, I can`t restore the backup.

Root & Install twrp on Doogee BL7000

i am going to share this post because this is not available here,
How to Root your Doogee BL7000
1. download twrp recovery https://androidfilehost.com/?fid=817906626617934998
2. unlock bootloader using this code
Code:
fastboot oem unlock
3. flash twrp using this code
Code:
fastboot flash recovery 'file name with format'
4. then download magisk https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
5. reboot to recovery and create a backup of your ROM and then flash Magisk..
twrp taken from this article-
https://romprovider.com/2017/09/twrp-recovery-root-doogee-bl7000/

Hi, where to write the code?
Tgere is an option in developer options to unlock bootloader, does it work?

Talionator said:
Hi, where to write the code?
Tgere is an option in developer options to unlock bootloader, does it work?
Click to expand...
Click to collapse
in CMD if you don't know you can use included Script

Alright, but where to find doggee bl7000 drivers I cant find them
---------- Post added at 12:49 PM ---------- Previous post was at 12:49 PM ----------
Its stuck on waiting for device

Means no Driver Installed on Your PC

mark332 said:
Means no Driver Installed on Your PC
Click to expand...
Click to collapse
phone got bootloop on orange state on logo

Mine got too
Talionator said:
phone got bootloop on orange state on logo
Click to expand...
Click to collapse
What i'm supposed to do ??? Mine got bootlooped too !

Bootloop
You must follow that instruction i got a bootloop after that i fixed it
community.doogee.cc/forum.php?mod=viewthread&tid=228&extra=page%3D1
and please use that firmware only for Dodgee BL7000
mega.nz/#!4W40QayS!8R7cJ6H0TwNPJpVQWpRWepGWI2Z0DiKC9A7GSHPlTz4

Hello. Do you know where to find a twrp for Doogee Bl12000 ? I can't find any. Thanks.
Bootloader is unlocked. I keep watching Needrom. Nothing so far ?
Found a TWRP at a russian site. "Rulsmart.com". No idea if it's reliable. No use anyway, because the zip file is encrypted.

Christian1968.Bolz said:
Hello. Do you know where to find a twrp for Doogee Bl12000 ? I can't find any. Thanks.
Bootloader is unlocked. I keep watching Needrom. Nothing so far ?
Found a TWRP at a russian site. "Rulsmart.com". No idea if it's reliable. No use anyway, because the zip file is encrypted.
Click to expand...
Click to collapse
I have the same phone, same question. Maybe the bl7000 way works for bl12000 too? Justin the TWRP infos. I will root with Magisk
---------- Post added at 08:20 AM ---------- Previous post was at 08:16 AM ----------
mark332 said:
i am going to share this post because this is not available here,
How to Root your Doogee BL7000
1. download twrp recovery https://androidfilehost.com/?fid=817906626617934998
2. unlock bootloader using this code
Code:
fastboot oem unlock
3. flash twrp using this code
Code:
fastboot flash recovery 'file name with format'
4. then download magisk https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
5. reboot to recovery and create a backup of your ROM and then flash Magisk..
twrp taken from this article-
https://romprovider.com/2017/09/twrp-recovery-root-doogee-bl7000/
Click to expand...
Click to collapse
I have a BL12000 and i am looking for install TWRP. May these steps works for it too?

steathnic666 said:
I have the same phone, same question. Maybe the bl7000 way works for bl12000 too? Justin the TWRP infos. I will root with Magisk
---------- Post added at 08:20 AM ---------- Previous post was at 08:16 AM ----------
I have a BL12000 and i am looking for install TWRP. May these steps works for it too?
Click to expand...
Click to collapse
Not work
You can use Magisk for initial root
or wait while someone compile

After i followed the Instructions with the BL7000 unlock/root/ twrp tool , the bootloader was unlocked but the phone soft-bricked....Imei gone of course....back to stock rom....well...i tried to flash Twrp with flashtool, "size too big"
then tried to flash a smaller version of Twrp (13Mb ver. 3.2.1.0) that lead into total blackness....back to regular recovery...voila.....i dont wanna try the Tool again .....bootloader is still unlocked
i am giving up for now....
cheers...

Is there ANY working root method for the BL12000 (NOT pro) ? I've been looking for months now without success

hi my phone is stuck in a boot loop the doogee logo shows up after a couple of seconds screen turns off and doogee logo shows up again
i try to boot into recovery mode but nothing happens phone just turns on and bootloops i plug into my pc and get the usb connected sound then the usb disconnected sound then phone just bootloops can you help

[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?

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?