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?
Related
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
Root Guide
** Root will void the warranty and disable OTA updates **
boot.img patch method
I don't recommend updating the firmware OTA before rooting. There is a chance you will update your phone to a firmware that hasn't been released yet on the ASUS website. New updates are released OTA first and then about a week or two later they are posted on the ASUS website. If by chance you updated the firmware OTA and the firmware isn't on the ASUS website, you'll have to wait for the firmware to be posted before you can root.
If already rooted and updating firmware skip to 5b
1. Make a folder called ROG Phone to store all files needed
2. Download the following to the ROG Phone folder
-- Unlock Tool, aka Unlock Device App
---- https://dlcdnets.asus.com/pub/ASUS/..._SIGNED_UnlockTool_9.1.0.7_180912_fulldpi.apk
-- Latest Firmware - Under Firmware click on See All Downloads | Look at version number, not dates
---- Match SKU/Region - Example: WW->WW, CN->CN, JP->JP
------ Settings > System > About phone > Software information
-------- https://www.asus.com/us/Phone/ROG-Phone/HelpDesk_BIOS/
-- Minimal ADB and Fastboot - Portable
---- https://devsjournal.com/download-minimal-adb-fastboot-tool.html
-- Payload Dumper
---- Attatched image_extrator.zip script
-- Python
---- https://www.python.org/downloads/
-- Magisk Manager
---- https://github.com/topjohnwu/Magisk/releases
3. Unlock bootloader
-- Connect the phone to the PC via the side port on your phone
-- Select USB File Transfer on the phone; If problems connecting, update drivers on the PC
-- Copy the Unlock Tool to your phone's Downloads folder
-- This voids the warranty and disables OTA updates
-- This will force a factory reset, so backup your data
-- Use File Manager (in ASUS folder) on your phone to run the Unlock Tool from the Downloads folder
-- If asked for Pin select "Use your Google account" in white text (can't see) below the Pin request
---- Pin request YouTube: https://www.youtube.com/watch?v=aPKAEGptfas
4. Enable Developer on the phone
-- Settings > System > About phone > Software information
---- Tap "Build number" 7 times
5. Update phone to latest downloadable firmware
-- 5a
-- Open the ROG Phone folder and enable view file extensions
---- File > Change folder and search options > Click View tab > Uncheck Hide extensions for known file types > Click OK
-- Unzip Minimal ADB and Fastboot - Portable file
-- 5b
-- Copy the firmware to the Minimal ADB and Fastboot folder and rename firmware.zip
-- Turn on USB debugging
---- Settings > System > Developer options
------ Enable "USB debugging"
-- Connect the phone to the PC via the side port on your phone
-- Select USB debugging on your phone.
-- From the Minimal ADB and Fastboot folder run cmd-here.exe
-- From the command prompt (black window) type the following:
adb devices
-- To check the connection
adb reboot recovery
-- Select ADB on phone
adb sideload firmware.zip
-- Check that your phone was updated to the latest firmware
---- Settings > System > About phone > Software information
If by chance adb sideload doesn't work, try copying the firmware to the root directory (folder) on the phone and then reboot to install. Don't change the name of the firmware while using this method and you can't skip updates. So if there are two updates out from your current version, you'll have to install both.
6. Extract the boot.img file from the firmware using Payload Dumper
-- Use the attached image extractor script
---- Requires Python; Look at readme.txt
7. Patch boot.img using Magisk Manager
** Make sure that boot.img is from the same firmware version that is on the phone **
-- Turn off USB debugging
---- Settings > System > Developer options
------ Disable "USB debugging"
-- Connect the phone to the PC via the side port on your phone
-- Select USB File Transfer on the phone
-- Copy Magisk Manager and boot.img to your phone's Downloads folder
-- Use File Manager (in ASUS folder) on your phone to run Magisk Manager from the Downloads folder
---- Magisk Manager requires access to the Internet via wifi or mobile network
-- More Information
---- https://www.google.com/search?q=How...Methods)&ie=utf-8&oe=utf-8&client=firefox-b-1
------ Look at Method 2
-- Copy patched_boot.img from the phone's Downloads folder to the Minimal ADB and Fastboot folder
8. Flash patched_boot.img
** Make sure that patched_boot.img is from the same firmware version that is on the phone **
-- Put phone into fastboot mode
---- While the phone is off, hold down volume up and power buttons
-- Connect the phone to the PC via the side port on your phone
-- From the Minimal ADB and Fastboot folder run cmd-here.exe
-- From the command prompt (black window) type the following:
fastboot devices
-- To check the connection
fastboot flash boot patched_boot.img
fastboot reboot
--------------------------------------------------------------------------------
Some users couldn't get a connection to a PC via a PC's Type-C USB port and had to use a Type-C to Type-A USB cable.
https://www.amazon.com/gp/product/B...00__o00_s00?tag=detailedview-20&ie=UTF8&psc=1
If by chance something went wrong and your phone locks up on boot, this raw WW firmware install will get you back up and going (so far it has worked for everyone). This can also be used to relock the bootloader, but it will not restore OTA updates.
https://drive.google.com/file/d/155ZDnBjHeknppthFtNpGadicSNvBGokP/view?usp=sharing
Download and unzip
Reboot phone into fastboot mode
Run flashall_AFT.cmd
..
Tesla74 said:
Quick Root Guide
1. Unlock bootloader
https://dlcdnets.asus.com/pub/ASUS/..._SIGNED_UnlockTool_9.1.0.7_180912_fulldpi.apk
2. Download unofficial TWRP by shakalaca (Doesn't fully work, but can flash files from USB drive)
Download the TWRP that matches your firmware version and rename twrp.img
https://mega.nz/#F!pst3URCQ!l_N503AsNmytaErhmuiwqg
3. Put phone into fastboot mode (volume down + power button)
Connect to the computer using the side USB port
4. Download Minimal ADB and Fastboot and flash twrp.img
https://devsjournal.com/download-minimal-adb-fastboot-tool.html
fastboot flash boot twrp.img
5. Download Magisk Manager, Magisk, and Magisk Unistaller onto a USB drive
https://github.com/topjohnwu/Magisk/releases
6. Flash Magisk with TWRP and install Magisk Manager to root
I don't have the phone yet, but if anyone wants to add to this guide to make it more accurate, I'll update this post.
Click to expand...
Click to collapse
Before running the fastboot command run: "fastboot devices" without quotations. To make sure the device is recognized and connected.
Nice write up!. By the way there is an update to the system a small one maybe 70+ MB. Minor stability update.
Rashad83 said:
Before running the fastboot command run: "fastboot devices" without quotations. To make sure the device is recognized and connected.
Nice write up!. By the way there is an update to the system a small one maybe 70+ MB. Minor stability update.
Click to expand...
Click to collapse
Thanks, I updated post. I was wondering after the system update, does TWRP still work because of encryption? Or does TWRP need to be updated for every system update?
Does the unlock bootloader tool REALLY erases all everything, or it's just ASUS warning so they cover their end if user data is lost?
Tesla74 said:
Thanks, I updated post. I was wondering after the system update, does TWRP still work because of encryption? Or does TWRP need to be updated for every system update?
Click to expand...
Click to collapse
Once you flash TWRP you will not be able to update through OTA. You will have to download the update manually and then flash it, once you do that i believe it flashes the stock boot.img which removes TWRP. When that happens you will have to flash a compatible TWRP for the new update.
That's how i understand it, personally i haven't rooted yet so i can't be 100% certain.
Also it's recommended by TWRP team to return to stock before updating the system and then flashing TWRP.
---------- Post added at 08:04 AM ---------- Previous post was at 07:49 AM ----------
mbze430 said:
Does the unlock bootloader tool REALLY erases all everything, or it's just ASUS warning so they cover their end if user data is lost?
Click to expand...
Click to collapse
It's not just ASUS, Any Android device once you unlock the bootloader the user data is erased. So better backup!. By the way ASUS has a backup tool for all your apps and data i haven't tried it yet, give it a try.
That is correct. When I had my Pixel 2 XL (or any phone for that matter). When you flash TWRP on to the recovery the OTA update will always fail. You will have to either find the original recovery or the whole rom and reflash it.
---------- Post added at 04:07 PM ---------- Previous post was at 04:05 PM ----------
---------- Post added at 08:04 AM ---------- Previous post was at 07:49 AM ----------
[/COLOR]
It's not just ASUS, Any Android device once you unlock the bootloader the user data is erased. So better backup!. By the way ASUS has a backup tool for all your apps and data i haven't tried it yet. so check it out.[/QUOTE]
Dang it! I just setup the phone exactly the way I wanted it too.
Rashad83 said:
Once you flash TWRP you will not be able to update through OTA. You will have to download the update manually and then flash it, once you do that i believe it flashes the stock boot.img which removes TWRP. When that happens you will have to flash a compatible TWRP for the new update.
That's how i understand it, personally i haven't rooted yet so i can't be 100% certain.
Also it's recommended by TWRP team to return to stock before updating the system and then flashing TWRP.
Click to expand...
Click to collapse
Thanks! I hope shakalaca keeps updating TWRP with the new firmwares. Sounds like recovery.img will have to be extracted from the firmware and flashed before updating.
You will not find any file under the name of recovery.img. I tried looking for it in the stock firmware before no such file exists. The only way I think to do it is by flashing all of the boot.img where it resides I think.
Fastboot flash boot boot.img
Rashad83 said:
You will not find any file under the name of recovery.img. I tried looking for it in the stock firmware before no such file exists. The only way I think to do it is by flashing all of the boot.img where it resides I think.
Fastboot flash boot boot.img
Click to expand...
Click to collapse
I wasn't able to find either recovery.img or boot.img in the firmware.
boot.img vs recovery.img always confuses me. I wonder if updating with the update.zip method really needs stock recovery?
Tesla74 said:
I wasn't able to find either recovery.img or boot.img in the firmware.
boot.img vs recovery.img always confuses me. I wonder if updating with the update.zip method really needs stock recovery?
Click to expand...
Click to collapse
You need the payload dumber app on windows to extract the payload file which contains all the .img files which boot.img is one of them.
The boot.img contains the kernel and other important files needed to boot the device, while the recovery contains all the recovery settings responsible for reseting the device and updating, wiping actions.
From the comments i saw about recovering the phone after a bootloop it seems stock recovery isn't needed but i could be wrong. We will need input from others who have done it.
On my previous phone i could go back to stock rom without stock recovery as long it's the same rom build. So you will need to flash the same stock rom you are currently on and then flash the update.
I ran into some trouble. after running bootloader unlocker apk. it is now asking for a PIN. I tried the PIN I used when setting up the fingerprint reader and it doesn't work. It won't let me setup the phone again now.
Also got into the stock Recovery and did a user/data factory reset
Anyone suggestions?
Tesla74 said:
4. Put phone into fastboot mode (volume down + power button)
Connect to the computer using the side USB port
Click to expand...
Click to collapse
By pressing volume down + Power button, the phone goes into recovery mode not fastboot.
It's easiest doing it by adb:
Adb devices
If the phone Is found:
Adb reboot bootloader
That's what I did when I root my Rog
mbze430 said:
I ran into some trouble. after running bootloader unlocker apk. it is now asking for a PIN. I tried the PIN I used when setting up the fingerprint reader and it doesn't work. It won't let me setup the phone again now.
Also got into the stock Recovery and did a user/data factory reset
Anyone suggestions?
Click to expand...
Click to collapse
I was in the same situation, but if you check carefully you will see "use your account Google" it's just below of the pin request.
(It's written in White )
I was in the same situation, but if you check carefully you will see "use your account Google" it's just below of the pin request.
(It's written in White )
Click to expand...
Click to collapse
OMG! You are right! after staring at the screen I can finally see it! THEY NEED TO FIX THAT! I spend the past 2 hours erasing all the partitions! I wanna kill ASUS!
Marco589 said:
By pressing volume down + Power button, the phone goes into recovery mode not fastboot.
It's easiest doing it by adb:
Adb devices
If the phone Is found:
Adb reboot bootloader
That's what I did when I root my Rog
I was in the same situation, but if you check carefully you will see "use your account Google" it's just below of the pin request.
(It's written in White )
Click to expand...
Click to collapse
Thanks! I"ve updated the guide for both issues.
Tesla74 said:
Thanks! I"ve updated the guide for both issues.
Click to expand...
Click to collapse
To go to fastboot mode the hardware method will be by:
1. Holding (Power+Volume Up) until you see "Republic of Gamers" logo then release.
2. If the phone is turned off; hold the volume up only and connect the usb c to the phone(make sure the usb wire is connected to the PC already "It's basically the same as holding the power button except you'r getting the power from the usb"). You will go directly to "fastboot mode/ bootloader mode" i used to do this before on my phones, will also work on the ROG phone.
Rashad83 said:
To go to fastboot mode the hardware method will be by:
1. Holding (Power+Volume Up) until you see "Republic of Gamers" logo then release.
2. If the phone is turned off; hold the volume up only and connect the usb c to the phone(make sure the usb wire is connected to the PC already "It's basically the same as holding the power button except you'r getting the power from the usb"). You will go directly to "fastboot mode/ bootloader mode" i used to do this before on my phones, will also work on the ROG phone.
Click to expand...
Click to collapse
Thanks! I updated the guide and added link to your post.
I loaded TWRP but I can't flash Magisk on it. Can't read the /system partition.
Worse off, I am stuck at the ROG logo even after reboot.
what can I do to get the phone to at least boot back to the OS?
-----Update------
Nevermind I extracted the payload.bin and fastboot flash boot boot.img from there and it booted up again.
mbze430 said:
I loaded TWRP but I can't flash Magisk on it. Can't read the /system partition.
Worse off, I am stuck at the ROG logo even after reboot.
what can I do to get the phone to at least boot back to the OS?
-----Update------
Nevermind I extracted the payload.bin and fastboot flash boot boot.img from there and it booted up again.
Click to expand...
Click to collapse
In order to flash Magisk v17.3, you need to load Magisk and magisk unistaller on a USB drive, then boot into recovery , select USB storage then flash magisk.
Thanks to mbze430 posting the boot.img patch method of rooting, I've updated the guide. This works without the need for TWRP.
Need info on flashing twrp. Are all attempts done on firmware version 23 (where latest shakalaca version of TWRP is supported)? Is there no way to get TWRP working on firmware version 43?
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
After so long i am posting something useful for S10e users and after flashing this there is no need to press that key combo (VOL up key + Power + Bixby) to boot into Magisk mode. Just after flashing this image your S10e will automatically boot up in the Magisk mode. And that key combo (VOL up key + Power + Bixby) will be used to boot your phone directly into recovery mode.
Download : PrePatched TWRPhttp://www.mediafire.com/file/exaf63omahdoeuv/Prepatched_Twrp.zip/file
DISCLAIMER : FLASH AT YOUR OWN RISK AND I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR PHONE.
IF MY POST IS USEFUL FOR YOU THEN KINDLY PRESS THE THANKS BUTTON
Special Thanks To : All credit goes to @ianmacd For his amazing Work for Twrp and Latest unofficial magisk for S10 family & @topjohnwu for his work for Magisk
Installation Instructions for the Rooted Users :
1. Requires Root : Download The Image File From The Above Download Link. Place It In The Root Of Your /sdcard folder .
2. Run The Following Commands Via Adb Shell
3. After Installation Do Wipe Your Internal storage
su
dd if=/sdcard/twrp.img of=/dev/block/platform/13d60000.ufs/by-name/recovery
Click to expand...
Click to collapse
reserved
Can i flash it with magisk
---------- Post added at 07:41 AM ---------- Previous post was at 07:38 AM ----------
Can i do it with flash memory or internal storage
hakim.hqma said:
Can i flash it with magisk
---------- Post added at 07:41 AM ---------- Previous post was at 07:38 AM ----------
Can i do it with flash memory or internal storage
Click to expand...
Click to collapse
dude jst download the prepatched twrp.zip and extract it using 7zip or winrar and place the twrp.img in your internal storage and just follow the commands from the 2nd post and flash it with adb or android emulator and after flashing kindly make a backup of your data and the wipe the internal sorage only of your phone and do not factory reset your phone other wise it will cause bootloop.Enjoy
Nice :good:
Install android terminal
Unzip file to storage
Copy paste code to terminal
Perfecto
---------- Post added at 12:55 AM ---------- Previous post was at 12:53 AM ----------
Thanks
great to hear that
Is it really worth routing the s10e?
ни хрена не получается
пишет, что расширение файла должно быть apk or apex
Will there be a Snapdragon version?
cant get it to work :/
I have an injected root stock-firmware S10E, will this let me flash third party roms?
can i flash linage rom and keep root with magisk after?
I followed this to the letter (after following this guide:I followed this to the letter (after following this guide: I followed this to the letter (after following this guide: the custom droid (no space) "dot com slash" samsung-galaxy-s10-root-guide)
It resulted in bootloop and having to return to stock (via Odin) and re-root following the above guide.
It would seem that the two methods are incompatible, but wondering if anyone has any thoughts/solutions to try (as I'd love to just "reset and forget" and not worry about the button combination unless jumping into recovery.
Thanks!!
It resulted in bootloop and having to return to stock (via Odin) and re-root following the above guide.
It would seem that the two methods are incompatible, but wondering if anyone has any thoughts/solutions to try (as I'd love to just "reset and forget" and not worry about the button combination unless jumping into recovery.
Thanks!!
It resulted in bootloop and having to return to stock (via Odin) and re-root following the above guide.
It would seem that the two methods are incompatible, but wondering if anyone has any thoughts/solutions to try (as I'd love to just "reset and forget" and not worry about the button combination unless jumping into recovery.
Thanks!!
Hello in previous versions of android, everything works perfect, but in ASIG after installation, when restarting it gives error.
A message in red letters at the top.
I DON'T KNOW. ozzy
Angie5 said:
Hello in previous versions of android, everything works perfect, but in ASIG after installation, when restarting it gives error.
A message in red letters at the top.
I DON'T KNOW. ozzy
Click to expand...
Click to collapse
The same as in ASJD.
Hello. Flashing twrp or rooting will trip the knox right? Will I able to return it if I flash stock rom?
LuisFernand said:
Hello. Flashing twrp or rooting will trip the knox right? Will I able to return it if I flash stock rom?
Click to expand...
Click to collapse
Nope. Tripping knox is ireversible for now. Currenty no method is available for it.
Another thing
kkrraazzyy said:
After so long i am posting something useful for S10e users and after flashing this there is no need to press that key combo (VOL up key + Power + Bixby) to boot into Magisk mode. Just after flashing this image your S10e will automatically boot up in the Magisk mode. And that key combo (VOL up key + Power + Bixby) will be used to boot your phone directly into recovery mode.
Download : PrePatched TWRPhttp://www.mediafire.com/file/exaf63omahdoeuv/Prepatched_Twrp.zip/file
DISCLAIMER : FLASH AT YOUR OWN RISK AND I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR PHONE.
IF MY POST IS USEFUL FOR YOU THEN KINDLY PRESS THE THANKS BUTTON
Special Thanks To : All credit goes to @ianmacd For his amazing Work for Twrp and Latest unofficial magisk for S10 family & @topjohnwu for his work for Magisk
Click to expand...
Click to collapse
Is this procedure enable downgrade a earlier bootloader?
he;;o looking to write this say for android pie series or for android 10
Magisk on G7 Play XT1952-4 Installed Succesfully
(Just a heads up. I have never posted to XDA before but have lurked on here for years. I don't have enough posts to post it in the Dev section. So I apologize if my post format is bad. But I will do my best. Hopefully I am not reporting old news, I've been waiting a few months to finally get Magisk to work on this phone.)
I do not take responsibility if you brick your phone doing this. So do it at your own risk.
Google Drive folder link with all files at the bottom of this post with screenshots as well
Install:
Firmware used during this is PPY29.105_160 (Firmware included in GDrive folder)
BOOTLOADER HAS TO BE UNLOCKED ON YOUR PHONE
I suggest you to backup and factory reset your phone before doing this.
If you're already on this firmware, then I have placed both the stock boot.img and the magisk_patched.img separate as well so you don't have to unzip the full firmware. I haven't tried this with other models of this phone or firmwares. Upgrade to this firmware if on an older version. Multiple ways to do so I'm sure you can figure it out
Copy the boot.img to your phones storage
Install Magisk Manager 7.3.4 aka 239 (APK in GDrive folder). Make sure all 3 options are checked in advanced settings in Magisk. Click install on Magisk and patch the file and locate it on your phone.
Place the patched.img in your ADB folder. Reboot into fastboot. I used CMD in Windows so I ran the following "fastboot flash boot magisk_patched.img"
Toggle up to Boot Recovery
Please Note. When I did the following. For some reason I was unable to get to the stock recovery after doing this. If I remove modules and reboot the phone Magisk is "not installed" however if you reboot the phone and go into Fastboot mode and then select the option of boot to recovery, it boots the phone normal with magisk enabled??? :confused. Eh at this point I'm just glad to have Magisk installed on this phone finally lol. I'm sure you can find the answer in the Magisk in Recovery section here
Magisk should be installed now after booting up. Check Magisk Manager to verify.
Notes:
I tried to install one module just to verify it wasn't a fluke and I was able to do so successfully
Once again I apologize if this post is unorganized or anything. Running on little sleep
I will do my best to answer any questions you might have from my experience when I am able to.
GOOGLE DRIVE FOLDER LINK
Nice work OP. Well written guide. Clear and concise.
i need some help i tried this method and ended up loosing baseband idk what i did wrong i have a retail varient , tried flashing stock rom multiple times do we have a persist.img to get the phone booting again ? twrp wont even boot i get the failed to many links error to see if wiping the phone that way would make it boot i flashed to both banks i have the XT195-4 varian
Use rsd lite to flash full rom it will reset your phone then enable usb debugging so you can reboot to fastboot then follow the instructions
Linuxassassin said:
Use rsd lite to flash full rom it will reset your phone then enable usb debugging so you can reboot to fastboot then follow the instructions
Click to expand...
Click to collapse
Thank you I managed to create a flash.bat with revived the phone I can confirm working on retail varient firmware 138
Ok this is a bit odd. Managed to get magisk installed. Rebooted and magisk is no longer installed. Figured I would have to reboot recovery again. Now whenever I go to boot recovery in the bootloader it just falls back to the bootloader.
The recovery option in magisk will not stick either it seems
Edit: Not sure what happened. I reflashed the stock firmware for my device, went through the steps again, and now magisk seems to have stuck. I do have to boot to recovery, but that was to be expected according to the documentation.
Oh Viper4Android, how I have missed thee
Edit 2: It appears the reboot to recovery option in magisk is what is breaking my install. As long as I do not try to reboot to recovery from anything outside of the bootloader, magisk sticks. Not sure what the cause for this is, but for now it is best to stay away from those options in Magisk
Edit 3: Not sure what the issue is, but after some tinkering, and a reboot, booting recovery to get magisk loaded does not work. Reboot to recovery takes me straight to the bootloader. If I click start the phone boots without magisk, and if I hold the button combo I get the stock recovery, but magisk appears to be gone
Please help
I flash wrong boot so I reflashed the entire firmware then patched the boot.img of the firmware I just flashed, all ok.
I flashed the patched boot image and toggled volume key to recovery but have no options there, so have to start phone by holding power button.
When phone boots up magisk is not installed. This is killing me so close yet...
P.s I omitted erase user data and erase DDR and phone is exactly as I left it ?
moochermick said:
Please help
I flash wrong boot so I reflashed the entire firmware then patched the boot.img of the firmware I just flashed, all ok.
I flashed the patched boot image and toggled volume key to recovery but have no options there, so have to start phone by holding power button.
When phone boots up magisk is not installed. This is killing me so close yet...
P.s I omitted erase user data and erase DDR and phone is exactly as I left it
Click to expand...
Click to collapse
your missing a step , what worked for me , since i updated my phone manually and now im on slot_a flash both banks with the magisk_patched.img and you wont have that problem , if your on slot_b flash slot_a as well , and it should work , fastboot getvar all to see what slot is bootable
@thenatti
Thanks I will give that ago.
thenatti said:
your missing a step , what worked for me , since i updated my phone manually and now im on slot_a flash both banks with the magisk_patched.img and you wont have that problem , if your on slot_b flash slot_a as well , and it should work , fastboot getvar all to see what slot is bootable
Click to expand...
Click to collapse
I have flashed the patched boot to both banks and still magisk not installed, what's all this talk about booting from recovery, I can't do anything from recovery except hold the power button to restart the phone.
Any further suggestions?
Ok here's what worked...
Reflashed all firmware and restarted phone,
Flashed patched boot.img and in fastboot on pc "fastboot continue" phone rebooted.
Back into fastboot on phone and selected "recovery" phone rebooted and Magisk installed.???
Many many thanks to op and everyone involved.
Can anyone make a video with installation of Magisk on this device, PLEASE!! Will be more easy..
I am thinking my original problem is with Magisk itself. For some reason I randomly lose root after a restart, and booting recovery just goes straight back to the bootloader. It hasnt happened to me again, but it happened twice yesterday.
I am usually good a bug tracking, but I have been unable to narrow this down to a specific thing.
Anyway.... today things are working great.
moochermick said:
Ok here's what worked...
Reflashed all firmware and restarted phone,
Flashed patched boot.img and in fastboot on pc "fastboot continue" phone rebooted.
Back into fastboot on phone and selected "recovery" phone rebooted and Magisk installed.
Many many thanks to op and everyone involved.
Click to expand...
Click to collapse
Can you bring me your steps for install Magisk on your device with variant that you have, please?
I would suggest for people having trouble with getting magisk installed
A few things to note
No will need to boot into fastboot then use volume keys to
Select recovery option Everytime you boot or you won't be rooted
Stay on the beta of magisk cause stable is not ready for our device
If you brick use rsd lite with latest firmware
Thats on https://mirrors.lolinet.com/firmware/moto/channel/official/
How to boot in fastboot is volume up and power key
When you flash firmware via rsd lite it will factory reset your phone
Then after that setup your phone but don't connect to WiFi or do
Just enable developer options
USB debugging
Plug phone into PC
If you don't have the us varient of the phone get the firmware for your phone
transfer the boot.img from your firmware to your phone
install magisk manager from the original post
Then follow the instructions to install magisk
ALSO MAKE SURE YOUR BOOTLOADER IS UNLOCKED
Or you will brick your phone
Hope that helps
I have had a successful install pretty stable been running great for I think 3days now
Mods I installed
Viper4android
Energized
Edxposed needs riru core to work
Gravitybox for pie requires edxposed
Anyone have the boot.img for firmware
PPYS29.105-134-2
---------- Post added at 10:50 PM ---------- Previous post was at 10:44 PM ----------
Linuxassassin said:
I have had a successful install pretty stable been running great for I think 3days now
Mods I installed
Viper4android
Energized
Edxposed needs riru core to work
Gravitybox for pie requires edxposed
Click to expand...
Click to collapse
How you could flash the modules?
thx
Linuxassassin said:
I would suggest for people having trouble with getting magisk installed
A few things to note
No will need to boot into fastboot then use volume keys to
Select recovery option Everytime you boot or you won't be rooted
Stay on the beta of magisk cause stable is not ready for our device
If you brick use rsd lite with latest firmware
Thats on
How to boot in fastboot is volume up and power key
When you flash firmware via rsd lite it will factory reset your phone
Bro thank you so much rsd lite unbricked my device!
Then after that setup your phone but don't connect to WiFi or do
Just enable developer options
USB debugging
Plug phone into PC
If you don't have the us varient of the phone get the firmware for your phone
transfer the boot.img from your firmware to your phone
install magisk manager from the original post
Then follow the instructions to install magisk
ALSO MAKE SURE YOUR BOOTLOADER IS UNLOCKED
Or you will brick your phone
Hope that helps
Click to expand...
Click to collapse
Bro thank you so much rsd lite unbricked my device!
Fdraco10 said:
Anyone have the boot.img for firmware
PPYS29.105-134-2
---------- Post added at 10:50 PM ---------- Previous post was at 10:44 PM ----------
How you could flash the modules?
Click to expand...
Click to collapse
You search riru core in modules
Install that reboot to recovery
Flash edxposed
Funfact gsi won't flash on a phone till we get unofficial twrp
So I use gravitybox for pie hence my power menu