[GUIDE] How to root your AB partition scheme based Nokia Android Devices
This guide should work on following models:
Nokia 6.1 or Nokia 6 (2018)
Nokia X6 (2018)
Nokia 7
Nokia 7 Plus
Nokia 8
Nokia 8 Sirocco
Step 1: Unlock the bootloader
Original unlock thread closed
Step 2: Install Magisk Manager
You can download it from here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
中国用户可从酷安下载 Magisk Manager
Chinese users can download it from Coolapk instead
Click to expand...
Click to collapse
Step 3: Patch stock boot from current or close version
Skip this step if you have already patched boot image.
You should know how to patch by reading Magisk Official Release Notes.
Step 4: Load specific patched boot from fastboot mode
For Nokia 6.1/6 (2018), X6, 7, 7 Plus and Sharp Aquos S2:
Android 7.1: C1N-0430-boot-patched.img
Android 8.0: C1N-134E-boot-patched.img
Android 8.1: B2N-222A-boot-patched.img
Android Pie: B2N-322C-boot-patched.img
In fact the kernel between these models are compatible to each other.
For Nokia 8:
Android 7.1: NB1-303A-boot-patched.img
Android 8.0: NB1-435J-boot-patched.img
Android 8.1: NB1-484A-boot-patched.img
Take the Nokia 7 Plus with B2N-222A-boot-patched.img for example.
Enter fastboot/download mode, you should be familiar with it if you've unlocked the bootloader.
Type following commands with your own fastboot:
Code:
fastboot reboot-bootloader
fastboot boot D:\B2N-222A-boot-patched.img
WARNING: DO NOT FLASH boot or this will overwrite the stock boot and may not recoverable.
Click to expand...
Click to collapse
If you're using these commands in OST LA installation directory, use "fastboot-android" instead of "fastboot".
After that, your phone will boot and have root privileges temporarily.
You can check if Magisk Manager indicates "√ Installed Version: 16.0".
Step 5: Reinstall Magisk as module
Your phone may not be able to connect to Wi-Fi, which is normal.
Copy the latest Magisk zip to the phone, I recommend you to copy it to "Download" directory.
Then add the Magisk zip as module. The phone will patch the boot image with Magisk.
Reboot your phone when finished.
After that, your phone will be rooted perfectly.
If you want to install Xposed Framework, you must use this version (Including Framework and Installer) unless you want to break OTA:
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Android 7.1 - sdk25
Android 8.0 - sdk26
Android 8.1 - sdk27
Android P - sdk28 but unreleased yet
Step 6: Install OTA Update (Optional)
If you want to install latest OTA update, you must restore the boot image.
Open Magisk Manager, tap "Uninstall" - "Restore Stock Boot". After the phone displays "Successfully restored", you should be able to install OTA update with no problem.
After OTA update installed, do Step 4 and 5 again.
Patched boot image mentioned in this topic can be downloaded here:
https://drive.google.com/open?id=1ISPiwruAxY0gVp3kil9YTAfIR8xBxHjf
Special thanks:
@topjohnwu for Magisk
@blackpanther0582 for providing stock rom
There have to be another method than to buy the possibilty to unlock your bootloader.
This is really making me angry....
Don't get me wrong... I don't criticize your post! It is even very important to post and share everything about the 7+, especially in relation to unlocking the bootloader and rooting your devive, so that custom development can begin finally.
To pay for unlocking your bootloader (and that even so awkward) is absolutely wrong in my opinion and I will definitely not support it... no matter how much I wish to unlock the bootloader.
But many thanks for sharing and explaining. I hope HMD will offer an official way for unlocking the bootloader very soon, or someone will find a more user-friendly way to do that.
Sent from my Nokia 7 plus using XDA Labs
Micha El said:
There have to be another method than to buy the possibilty to unlock your bootloader.
This is really making me angry....
Don't get me wrong... I don't criticize your post! It is even very important to post and share everything about the 7+, especially in relation to unlocking the bootloader and rooting your devive, so that custom development can begin finally.
To pay for unlocking your bootloader (and that even so awkward) is absolutely wrong in my opinion and I will definitely not support it... no matter how much I wish to unlock the bootloader.
But many thanks for sharing and explaining. I hope HMD will offer an official way for unlocking the bootloader very soon, or someone will find a more user-friendly way to do that.
Click to expand...
Click to collapse
I can understand your feeling.
What I'm doing is making as much pressure as we can to HMD Global in order to make the phone unlockable officially.
Once I achieved that, you needn't to pay for unlock key.
hikari_calyx said:
What I'm doing is making as much pressure as we can to HMD Global in order to make the phone unlockable officially.
Once I achieved that, you needn't to pay for unlock key.
Click to expand...
Click to collapse
We should ask HMD to pay us the SETools credits... Maybe that's easier to do for them.
Sent from my Nokia 7 plus using XDA Labs
Working up until i try to reboot in Step 5 and then hangs on android one screen and then eventually gets to NOKIA splash screen but hangs forever (at least 10 mins and nothing).
Thoughts?
Micha El said:
There have to be another method than to buy the possibilty to unlock your bootloader.
This is really making me angry....
Don't get me wrong... I don't criticize your post! It is even very important to post and share everything about the 7+, especially in relation to unlocking the bootloader and rooting your devive, so that custom development can begin finally.
To pay for unlocking your bootloader (and that even so awkward) is absolutely wrong in my opinion and I will definitely not support it... no matter how much I wish to unlock the bootloader.
But many thanks for sharing and explaining. I hope HMD will offer an official way for unlocking the bootloader very soon, or someone will find a more user-friendly way to do that.
Sent from my Nokia 7 plus using XDA Labs
Click to expand...
Click to collapse
Isnt Android one's prime moto is to being as close as pixel device then why did hmd locked the bootloader
Tried lots of times and every time i get to Step 5 and installing Magisk as a module it just hangs on Nokia screen when it reboots.
Only way back into phone is to get to download mode and 'fastboot boot D:\B2N-222A-boot-patched.img' and then it gets me back.
Help!
Lazyfox007 said:
Isnt Android one's prime moto is to being as close as pixel device then why did hmd locked the bootloader
Click to expand...
Click to collapse
Every phone's bootloader is locked from factory. Most manufacturers offer a possibility to unlock the bootloader, the methods vary.
At the moment, however, there seems to be several manufacturers who do not offer this possibility anymore (e.g. Huawei / Honor).
When I talked with Nokia Phones Support and asked why there's no official method to unlock the N7+ bootloader, they told me that's because of warrenty and security. But everyone who unlocks their bootloader knows about those risks, so the real reason is...
...a big secret that probably will never be revealed...
...or it's just a whim of the manufacturer.
hikari_calyx said:
I can understand your feeling.
What I'm doing is making as much pressure as we can to HMD Global in order to make the phone unlockable officially.
Once I achieved that, you needn't to pay for unlock key.
Click to expand...
Click to collapse
I hope you succeed man.
hikari_calyx said:
[GUIDE] How to root your AB partition scheme based Nokia Android Devices
This guide should work on following models:
Nokia 6.1 or Nokia 6 (2018)
Nokia X6 (2018)
Nokia 7
Nokia 7 Plus
Nokia 8
Nokia 8 Sirocco
Step 1: Unlock the bootloader
Original unlock thread closed
Step 2: Install Magisk Manager
You can download it from here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Step 3: Patch stock boot from current or close version
Skip this step if you have already patched boot image.
You should know how to patch by reading Magisk Official Release Notes.
Step 4: Load specific patched boot from fastboot mode
For Nokia 6.1/6 (2018), X6, 7, 7 Plus and Sharp Aquos S2:
Android 7.1: C1N-0430-boot-patched.img
Android 8.0: C1N-134E-boot-patched.img
Android 8.1: B2N-222A-boot-patched.img
Android P: B2N-3050-boot-patched.img
In fact the kernel between these models are compatible to each other.
For Nokia 8:
Android 7.1: NB1-303A-boot-patched.img
Android 8.0: NB1-435J-boot-patched.img
Android 8.1: NB1-484A-boot-patched.img
Take the Nokia 7 Plus with B2N-222A-boot-patched.img for example.
Enter fastboot/download mode, you should be familiar with it if you've unlocked the bootloader.
Type following commands with your own fastboot:
Code:
fastboot reboot-bootloader
fastboot boot D:\B2N-222A-boot-patched.img
If you're using these commands in OST LA installation directory, use "fastboot-android" instead of "fastboot".
After that, your phone will boot and have root privileges temporarily.
You can check if Magisk Manager indicates "√ Installed Version: 16.0".
Step 5: Reinstall Magisk as module
Your phone may not be able to connect to Wi-Fi, which is normal.
Copy the latest Magisk zip to the phone, I recommend you to copy it to "Download" directory.
Then add the Magisk zip as module. The phone will patch the boot image with Magisk.
Reboot your phone when finished.
After that, your phone will be rooted perfectly.
If you want to install Xposed Framework, you must use this version (Including Framework and Installer) unless you want to break OTA:
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Android 7.1 - sdk25
Android 8.0 - sdk26
Android 8.1 - sdk27
Android P - sdk28 but unreleased yet
Step 6: Install OTA Update (Optional)
If you want to install latest OTA update, you must restore the boot image.
Open Magisk Manager, tap "Uninstall" - "Restore Stock Boot". After the phone displays "Successfully restored", you should be able to install OTA update with no problem.
After OTA update installed, do Step 4 and 5 again.
Patched boot image mentioned in this topic can be downloaded here:
https://drive.google.com/open?id=1ISPiwruAxY0gVp3kil9YTAfIR8xBxHjf
Special thanks:
@topjohnwu for Magisk
@blackpanther0582 for providing stock rom
Click to expand...
Click to collapse
Any chance of a patched boot image off the latest Android P Beta for Nokia 7 Plus? Thanks
To subscribers of this topic:
I uploaded patched DRG-229D boot image which is from Nokia X6. You can try to use it on your Nokia 7 plus and feel free to send feedback here
hikari_calyx said:
To subscribers of this topic:
I uploaded patched DRG-229D boot image which is from Nokia X6. You can try to use it on your Nokia 7 plus and feel free to send feedback here
Click to expand...
Click to collapse
Is that the one to try for new Android P beta?
Edit:
Confirmed doesn't work for latest android p
hikari_calyx said:
To subscribers of this topic:
I uploaded patched DRG-229D boot image which is from Nokia X6. You can try to use it on your Nokia 7 plus and feel free to send feedback here
Click to expand...
Click to collapse
Works fine on B2N TA-1046 on latest 8.1 June 2018 patch. Thank you very much, I just rooted my 7 plus.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Broadcasted from Zeta Reticuli
Since official stock firmwares of Nokia X6 are not available yet, I cannot generate boot_patched.img with Magisk Manager.
Currently, I cannot root my Nokia X6, is it correct ?
Even after correctly restoring stock boot.img I'm unable to update to July patch ( I did the restore from magisk as written in the first post ).
Tried via normal update via OS but it's giving me "Couldn't update - Installation problem".
I took the zip from data and tried from recovery both via sideload and sdcard method. In this case the error is the one attached.
Tried to download it more than once too, no luck..
If someone would have any suggestion it would be helpful.
Edit: system and vendor partition were modified ( don't know how )
I update to july patch but nokia 6x patched boot is not booting anymore.
okay, i tried both the drg and the b2n 8.1 boot images, none of them works. how on earth do i extract my own boot img? so that i can patch it with magisk? i get stuck on the nokia logo every time i try. i have to manually reboot the phone to get it working again. i'm on july security update and ta-1055 version.
---------- Post added at 08:51 PM ---------- Previous post was at 08:34 PM ----------
none of the above boot img's bring me joy. i'm stuck on the nokia logo every time. i guess we need july patched boot.img. anyone knows how to do it?
donjamal said:
okay, i tried both the drg and the b2n 8.1 boot images, none of them works. how on earth do i extract my own boot img? so that i can patch it with magisk? i get stuck on the nokia logo every time i try. i have to manually reboot the phone to get it working again. i'm on july security update and ta-1055 version.
---------- Post added at 08:51 PM ---------- Previous post was at 08:34 PM ----------
none of the above boot img's bring me joy. i'm stuck on the nokia logo every time. i guess we need july patched boot.img. anyone knows how to do it?
Click to expand...
Click to collapse
Here a July patched boot.img, you can fastboot boot it ( I made it by flashing twrp on inactive slot ).
https://www.androidfilehost.com/?fid=5862345805528049361
eskamhl said:
Here a July patched boot.img, you can fastboot boot it ( I made it by flashing twrp on inactive slot ).
https://www.androidfilehost.com/?fid=5862345805528049361
Click to expand...
Click to collapse
worked like a charm! thanks!
eskamhl said:
Here a July patched boot.img, you can fastboot boot it ( I made it by flashing twrp on inactive slot ).
https://www.androidfilehost.com/?fid=5862345805528049361
Click to expand...
Click to collapse
Hi! first thanks for your work!
Second, is it possible to get this boot img for TA-1046? or this boot img works with TA-1046?
i'm on TA-1046 with the last july update.
siberflyers said:
Hi! first thanks for your work!
Second, is it possible to get this boot img for TA-1046? or this boot img works with TA-1046?
i'm on TA-1046 with the last july update.
Click to expand...
Click to collapse
try it. it won't hurt. if you can't boot it, simply press and hold volume up + power until phone reboots and you're back to original boot. you need to have unlocked bootloader and make sure you are just booting from the image and you are not flashing it!
Related
Team Win Recovery Project 3.0.2-0
This is for the Xiaomi Mi MIX only, do not flash on other models!
WARNING: As of Android Marshmallow, factory boot images have dm-verity enabled, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below in order to allow system modifications without the risk of a boot loop!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Read more about TWRP here: https://twrp.me/about/
DOWNLOAD
You can find the device page here:
For official stock/dev firmware: http://teamw.in/devices/xiaomimimix.html
For (slightly newer) firmware: https://build.nethunter.com/test-builds/twrp/xiaomi/twrp-3.0.2-0-rc1-eu-lithium.img
For (the latest EU) firmware: https://build.nethunter.com/test-builds/twrp/xiaomi/twrp-3.0.2-0-rc2-eu-lithium.img
(touchscreen will not respond if not matching firmware)
You can find up to date fastboot & adb binaries here!
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
You must first unlock your device. To do this, follow the instructions on the MIUI forums. (tedious, I know)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Extract adb & fastboot to your computer.
Download TWRP for Xiaomi Mi MIX (lithium).
Reboot your device into fastboot mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Power] buttons while your device reboots.
Once you're in fastboot mode, you're ready to flash TWRP. To do this, run these commands in order:
fastboot flash recovery twrp.img
fastboot boot twrp.img
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you want to be rooted with something else or just want a bootable system:
Download the latest dm-verity and forced encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
This will also allow you to use [Format Data] to completely disable your encryption if desired.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up. (SuperSU will reboot you a few times)
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2-0 - Official release on twrp.me
v3.0.2-0-rc1 - Initial release candidate and first XDA build
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
There's absolutely none that I know of. Rejoice. You even have working hardware encryption!
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree (Official): https://github.com/TeamWin/android_device_xiaomi_lithium (android-6.0)
Device tree (Development): https://github.com/jcadduono/android_device_xiaomi_lithium (android-6.0)
Kernel: Unavailable (waiting on Xiaomi source release, using MIUI stock binary for now)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
Thank you to @wolfgart for requesting device support and reporting feedback on my initial builds.
Great Work
Now Xiaomi MI MIX is the greatest device we can have atm
@jcadduono @wolfgart Wolfgart request your help just because in Italy I've already published italian rom with my recoveryas you see from here
http://forum.hdblog.it/index.php?/topic/55021-xiaomi-mi-mix-official/?p=999961
http://forum.hdblog.it/index.php?/topic/55021-xiaomi-mi-mix-official/?p=1000010
But your official support is obviously better than mine. I follow you in a lot of thread so I know your great work:good::good: Very happy for this
development is starting , great work OP
agriculture said:
development is starting , great work OP
Click to expand...
Click to collapse
Best device now has best TWRP ever made before.
tnx @jcadduono
Looks like it won't be showing up on twrp.me until 3.0.3 or 3.1.0 depending on what's next. There's a few incompatibilities in the device tree and I'd prefer to wait it out till then. Ex. 3.0.2 doesn't support f2fs or ntfs on omnirom trees right now, but our current source does. If I made an official release neither would be supported.
Update: Official release made on newer TWRP build tree.
Wow, a thousand thanks.
I flashed the recovery, but the touch screen was not working, I can't do anything in the recovery, anyone know what's wrong?
mega00 said:
I flashed the recovery, but the touch screen was not working, I can't do anything in the recovery, anyone know what's wrong?
Click to expand...
Click to collapse
did you read the part about needing a different TWRP image for EU vs stock ROM? You will need to boot the ROM you want, then turn off the device completely and boot into the TWRP version that matches it. This is a kernel firmware update issue that I can't fix until Xiaomi releases sources.
mega00 said:
Wow, a thousand thanks.
Click to expand...
Click to collapse
don't quote the entire thread opener.... edit your post and remove it, if you need to make adjustments use the edit button, don't make another post immediately after your own
jcadduono said:
did you read the part about needing a different TWRP image for EU vs stock ROM? You will need to boot the ROM you want, then turn off the device completely and boot into the TWRP version that matches it. This is a kernel firmware update issue that I can't fix until Xiaomi releases sources.
I am on stock rom and using the stock rom version TWRP, the touch screen just don't work.
To be more clear, I am on dev rom 6.11.10 (MIUI8), do I have to change to stable rom V8.0.8.0.MAHCNDI (MIUI8) to make it work?
Update: Yes, I changed to stable rom and it works.
Click to expand...
Click to collapse
mega00 said:
jcadduono said:
did you read the part about needing a different TWRP image for EU vs stock ROM? You will need to boot the ROM you want, then turn off the device completely and boot into the TWRP version that matches it. This is a kernel firmware update issue that I can't fix until Xiaomi releases sources.
I am on stock rom and using the stock rom version TWRP, the touch screen just don't work.
To be more clear, I am on dev rom 6.11.10 (MIUI8), do I have to change to stable rom V8.0.8.0.MAHCNDI (MIUI8) to make it work?
Click to expand...
Click to collapse
you have to flash CN Stable rom V8.0.8.0.MAHCNDI (MIUI8) and use original TWRP for it and if you want Cross-Flash your CN rom with International one Here too .
When you are on International rom up&running you can flash over the EU TWRP .
As explained from @jcadduono this is the only solution for the moment until XIAOMI release his Kernel stuff officially
Click to expand...
Click to collapse
Thanks to the devs for such fast development on this great phone ...
I personally coming from lg so xiaomi is completely new for me ...
I understand the usual steps unlocking bootloader..flashing twrp ...and finally root ....
I don't have the phone yet but when it comes is running the same stock rom for everybody if I'm not wrong?...
What is that with the different roms?...
And how do i know wich twrp have to install?
Thanks again and sorry for the #noob# guestions....
Sent from my LG-D855 using XDA Free mobile app
cultofluna said:
Thanks to the devs for such fast development on this great phone ...
I personally coming from lg so xiaomi is completely new for me ...
I understand the usual steps unlocking bootloader..flashing twrp ...and finally root ....
I don't have the phone yet but when it comes is running the same stock rom for everybody if I'm not wrong?...
What is that with the different roms?...
And how do i know wich twrp have to install?
Thanks again and sorry for the #noob# guestions....
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
cause Stock kernel still was not relased you have to simply flash EU Rom using stock TWRP and after you done you have to change to TWRP EU to make it working again .
We are waiting official sources from Xiaomi
just to make sure i'm understanding this correctly - there is no way to unlock this phone on the day you get it you have to apply and wait upwards of 2 weeks to be able to unlock it?
knives of ice said:
just to make sure i'm understanding this correctly - there is no way to unlock this phone on the day you get it you have to apply and wait upwards of 2 weeks to be able to unlock it?
Click to expand...
Click to collapse
I waited about 4 hours after submitting the application, 2 weeks is a maximum estimation.
knives of ice said:
just to make sure i'm understanding this correctly - there is no way to unlock this phone on the day you get it you have to apply and wait upwards of 2 weeks to be able to unlock it?
Click to expand...
Click to collapse
you have to wait few minutes or at last 24 hours to receive sms unlock approve
:good::good:
wolfgart said:
you have to wait few minutes or at last 24 hours to receive sms unlock approve
Click to expand...
Click to collapse
I am facing the unlock stuck at 50% issue while trying to unlock the bootloader on this phone? any ideas? Thank you.
does anyone know if using TWRP manager will work to install TWRP after you have unlocked?
jim380 said:
I am facing the unlock stuck at 50% issue while trying to unlock the bootloader on this phone? any ideas? Thank you.
Click to expand...
Click to collapse
you have to Log On with your MIUI account on device too and the retry to unlock
---------- Post added at 07:43 AM ---------- Previous post was at 07:42 AM ----------
knives of ice said:
does anyone know if using TWRP manager will work to install TWRP after you have unlocked?
Click to expand...
Click to collapse
it works ! I can confirm. And it works using Flashify too
WARNING:
Please do every preparation that could fix your phone to original state before doing this trick.
DOING THIS MAY VOID YOUR WARRANTY, DO IT AT YOUR OWN RISK
I managed to unpack the official firmware of Nokia 7 and 8, and patched their boot.img with SuperSU Systemless Root.
But I don't know if it works on them.
Patched boot.img can be downloaded at:
https://mega.nz/#F!igsBmarT!3rIjD4ZaZN8ueOTVmciGwg
Here's the method you need to do:
1. Install OST LA and patch it, and OPEN IT FROM INSTALLATION DIRECTORY DIRECTLY.
2. Flash required firmware before proceed. If you don't do that, you won't be able to access Wi-Fi after the boot.img flashed.
For Nokia 7, you need to use the firmware "C1N-0430-0-00CN-B05" which I haven't released to public for some reason.
For Nokia 8, you need to use the firmware "NB1-435J-0-00WW-B01" which released in this topic: https://forum.xda-developers.com/showthread.php?t=3678487
If you've already flashed required firmware before proceed, you can skip this part.
Click to expand...
Click to collapse
3. Use the Service Purposed Bootloader trick I've mentioned in the Nokia 6 Root Guide: https://forum.xda-developers.com/showthread.php?t=3702354
4. Type these commands:
Code:
fastboot-android flash boot_a E:\NB1-435J-Boot-Patched.img
fastboot-android flash boot_b E:\NB1-435J-Boot-Patched.img
fastboot-android reboot
For Nokia 7, use C1N-0430-Boot-Patched.img instead. I've attached the Firehose, rawprogram0 and patch0 for Nokia 7 in case you want to use EDL Mode on Nokia 7.
Click to expand...
Click to collapse
5. If it's accepted by the system, the phone will reboot twice, and you'll see SuperSU appeared.
However, if "Verification Failed" appeared on your phone, then the trick failed. You have to flash original firmware to restore your phone to factory state.
If anyone know how to fix that in boot.img, that's a breakthrough of Nokia Android Devices.
You may want to use Flashfire to flash Xposed Framework or something else, but DO NOT RECEIVE ANY OTA UPDATES after your phone rooted.
I'm looking forward to a boot.img manual patcher on PC or Phone available, which could patch boot.img to achieve Systemless Root either SuperSU or Magisk and bypass Verification Boot.
This looks exciting. I have to look deeper into recovery options before I dare this kind of experiment...
Tried on a retail Nokia 8 TA-1052 running 00WW_4_35J_SP01
Boot passed but unfortunately no root
End up having to upgrade to 4390 using 4G
Update: Can't install 4390 even when I download the update multiple times. Flashed 435J using OST and tried flashing the kernel again but still no root.
ansonscleung said:
Tried on a retail Nokia 8 TA-1052 running 00WW_4_35J_SP01
Boot passed but unfortunately no root
End up having to upgrade to 4390 using 4G
Click to expand...
Click to collapse
Thanks for feedback.
I'll check if anything wrong.
Can you check if you can install SuperSU manually from Google Play?
After you installed it, is root available?
hikari_calyx said:
Thanks for feedback.
I'll check if anything wrong.
Can you check if you can install SuperSU manually from Google Play?
After you installed it, is root available?
Click to expand...
Click to collapse
Nope. SuperSU said "Root not available"
Many thanks for your efforts on this patch, I would love to be able to root my Nokia 8.
Having an unlocked bootloader I am not really worried about, but having root access is a big feature for me.
Any chance this patch will become available to firmware version 00WW_4_390 which is the current latest? (And what my phone is currently running)
Not sure if I can downgrade it to NB1-435J-0-00WW-B01 or not, but I can try that if it is not able to be patched to the latest firmware image.
Thnx hikari_calyx for your hard work!
ansonscleung said:
Tried on a retail Nokia 8 TA-1052 running 00WW_4_35J_SP01
Boot passed but unfortunately no root
End up having to upgrade to 4390 using 4G
Update: Can't install 4390 even when I download the update multiple times. Flashed 435J using OST and tried flashing the kernel again but still no root.
Click to expand...
Click to collapse
Did anyone else but ansoncleung tried this meanwhile?
@hikari_calyx I have a self prepatched boot. IMG for TA1012, flashed via fastboot now I have root with Magisk, but WLAN won't work.
Powered by Nokia 8
2WildFirE said:
@hikari_calyx I have a prepatched boot. IMG for TA1012, flashed via fastboot now I have root with Magisk, but WLAN won't work.
Powered by Nokia 8
Click to expand...
Click to collapse
Log
Op please pm me i am developer too we can do this together.
TheKsM said:
Op please pm me i am developer too we can do this together.
Click to expand...
Click to collapse
Hey we need developers here on Nokia!
And what we need to is a dev who build twrp for Nokia8. The recovery is inside the boot. IMG.
If you want build a one for the community. Thanks
Powered by Nokia 8
In theory, this guide will work on every variant of Nokia 6, but you can only use CN Variant ROM.
Update: Until Jan 25th 2019, D1C-612H-0-00CN-B03 (Feb 2019 Update) was the latest release of Nokia 6 2017.
I strongly recommend you to unlock the bootloader before proceed - I won't tell how to unlock the bootloader in this guide.
Take a look to this video first if you want to know the experience of Android Pie: https://youtu.be/izt650UNB5Y
Click to expand...
Click to collapse
In this guide, I'll provide two different methods to get Android Pie on your Nokia 6.
Both methods will erase your userdata.
Here's an important hint: Nokia 5 (ND1) and Nokia 6 (D1C or PLE) can flash each other's stock firmware, including TA-1000 Chinese firmware.
If you're eager to experience Global Android Pie on your Nokia 6, you can read this guide: https://forum.xda-developers.com/nokia-5/how-to/guide-how-to-install-android-pie-build-t3883901
Method 1: Use OST LA to flash my homebrew firmware
You should be familiar with this method.
1. Download "D1C-612H-0-00CN-B03_Homebrew.7z" from following site:
https://www.androidfilehost.com/?w=files&flid=288043
https://tpedutw-my.sharepoint.com/:...pv2wmqCvD1EqhzLLjvjkQYBULIyM5Yu1SIKp-b-sEdzKQ
Note: If you can't extract it correctly, please use 7-Zip ZStandard (not Original 7-Zip) to extract.
Chinese users can download it from Baidu Netdisk instead
中国用户可以从百度网盘下载
https://pan.baidu.com/s/1lZB4_qa_Z-WJ5sA88aFcMA
Click to expand...
Click to collapse
2. If you have Android 8.x running with LOCKED bootloader, please downgrade bootloader back before processing. If you have unlocked bootloader, you needn't to downgrade the bootloader.
If you're not using TA-1000, you need to change SKUID to 600CN by following this guide: https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-change-skuid-to-worldwide-t3808520
3. Open OST LA or NOST and load the mlf file, in download options, only choose "Normal Download" and "Erase userdata".
If your phone boots suddenly when flashing splash, close OST LA and force power off your phone then flash again.
You can download NOST from https://github.com/StollD/NOST
4. All done, enjoy Android Pie.
Method 2: Force OTA Update
1. Download the package "D1C-612H-0-00CN-B03-update.zip" from here:
https://www.androidfilehost.com/?w=files&flid=288069
Or this for Global Android Pie, rename it to "D1C-612H-0-00WW-B03-update.zip":
https://android.googleapis.com/pack.../97a575ee1c9f1500856dcd94e1b6292998aa78c9.zip
2. If you're not using TA-1000 or 1003, rename the package to PLE-612H-0-00WW-B03-update.zip
3. Skip this step if you're using TA-1000.
Non TA-1000 users need to change SKUID to 600CN by following this guide: https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-change-skuid-to-worldwide-t3808520
4. Place the package to root directory of internal storage.
5. Dial *#*#874#*#* to update.
6. After update installed, it will may tell you "Encryption failed", click "Factory Reset".
7. Enjoy Android Pie.
FAQ:
Q1: Can I root it?
A1: Yes, but you must have unlocked bootloader, and TWRP is unusable. Also, Magisk 18 is unusable.
Q2: How to downgrade bootloader in case I want to roll back without unlocked bootloader?
A2: Rename existing Android 8.0 OTA package for your model to D1C-9999-0-00CN-B09-update.zip. Then you should know what to do next.
Android 8.0 for TA-1000 DL: https://ota-filesite.c2dms.com/SWImage/500000772 (DO NOT USE IT ON NON TA-1000! )
Q3: My language is unavailable!
A3: Please follow this guide: https://hikaricalyx.com/2018/09/21/how-to-change-your-nokia-phone-language-to-japanese-or-korean/
Q4: Where is Google Play Store?
A4: You need to download Play Store APK manually from websites like Apkpure and install it manually.
Q5: I heard both TA-1000 and TA-1003 doesn't have NFC feature. Will I lose NFC if I installed this build?
A5: Nope, you can still use NFC.
Q6: When will you unlock Nokia X7 / Nokia 8.1?
A6: I don't know!
Q7: When will you get Nokia 9 Penta Camera Phone?
A7: I don't know, don't ask.
When for Nokia 5 2017
I'm downloading and testing.
Thanks for sharing.
When for Nokia 5 2017
It's homebrew Pie?
Magnum44pl said:
It's homebrew Pie?
Click to expand...
Click to collapse
Android Pie build itself is official, but I made it as homebrew fastboot firmware.
hikari_calyx said:
Android Pie build itself is official, but I made it as homebrew fastboot firmware.
Click to expand...
Click to collapse
So you Havel access to Pie beta for Nokia 6 2017?
Bugs for a not unlocked TA1025 flashing it:
1. the battery saver won't work and show a blank icon in the quick access tiles.
2. Only App twins is available in the advance Manu in setting.
3. Always on Display not working.
Nokia 6 TA-1021
What about Nokia 6 TA-1021
Tarish Ahmed B said:
What about Nokia 6 TA-1021
Click to expand...
Click to collapse
TA-1021 can also flash this 6120 for D1C
this is great Rom:fingers-crossed::fingers-crossed:
everything is better than global Rom and 8
camera is wonderful:good:
and have new things that amaze you when i use it (like gallery with special recognizatian ; floating ball ; ....)
install it
great job Hikari:good::good::good::good:
Can anyone share a complete review video of android pie on Nokia 6
My Nokia 6 failed to boot. i followed second process it is on Nokia Load screen since past 3 hours what to do now ?
Is there a possibility to get arcore on nokia 6 2017?
is it necessary to Unlock bootloader
is it
sdreddy said:
My Nokia 6 failed to boot. i followed second process it is on Nokia Load screen since past 3 hours what to do now ?
Click to expand...
Click to collapse
You need to enter the recovery and do a factory reset.
VinodTerry said:
is it
Click to expand...
Click to collapse
It is not necessary to unlock the bootloader and the room still works normally, but you have to unlock to edit your global variant into Chinese variant, and also unnecessary, and you can bypass it and force it to update. via OTA but you have to rename the update package as instructed.
4G Volte is Not Working
yuezhengbaizhi said:
You need to enter the recovery and do a factory reset.
Click to expand...
Click to collapse
Voice over LTE mandatory for Jio Network india , there is no Option like that ! Not at all showing , Android is Great loaded with features and Snappy and i use Chinese TA-1000 , so no issues in installation
Downloaded OTA File,my phone is TA-1021 EU variant,skiped SKUID part,just renamed the OTA File,seems to install right now,i hope i didnt brick my phone xD.
---------- Post added at 11:43 PM ---------- Previous post was at 11:37 PM ----------
Flash went ok,but now its seems to be stuck on NOKIA Logo,hardware keys navigation didn't display the light anymore xD.
---------- Post added 20th December 2018 at 12:07 AM ---------- Previous post was 19th December 2018 at 11:43 PM ----------
Entered recovery,wiped data,and i succesfully installed Pie on my Nokia 6 TA-1021 EU variant,but i do have question.
Can i rollback to TA-1021 ROM ? because now my phone its TA-1000.
sdreddy said:
My Nokia 6 failed to boot. i followed second process it is on Nokia Load screen since past 3 hours what to do now ?
Click to expand...
Click to collapse
Factory reset
Process to install security updates on rooted Nokia 8
Download the Nokia 8 OTA zip files on your Computer from this link in the OTA folder https://bit.ly/nokia-nb1 (it's usually up to date)
Download the Nokia 8 latest FULL ROM OTA zip file on your Computer from this link in the OTA folder https://bit.ly/nokia-nb1 (usually with size above 1 GB, currently it is: NB1-5150-0-00WW-B03-update.zip 1.52 GB)
Connect the phone to the PC using the USB cable and enable USB debugging (after enabling developer options)
Verify connection and drivers are correct on your computer by using the following ADB/Fastboot command(minimal adb fastboot can be found here https://forum.xda-developers.com/showthread.php?t=2317790):
adb devices
Click to expand...
Click to collapse
If you see your device and ID then all good so far
Use the following adb command on your Computer
adb reboot bootloader
Click to expand...
Click to collapse
Alternative to the previous step, you can select ADB sideload from the stock recovery menu after booting into stock.
when the device reboots into bootloader / or ADB sideload is selected from recovery use this command on your computer:
adb sideload path_to_zip/FULL_ROM_OTA.zip
Click to expand...
Click to collapse
Once loaded, reboot using the command
adb reboot
Click to expand...
Click to collapse
Sideload the OTA updates you have downloaded in step 1 using the same process as before OR Update normally through android system settings. Keep updating and restarting until you have the latest update
Download the latest Nokia 8 Stock boot image file on your phone from this link in the STOCK BOOT folder https://bit.ly/nokia-nb1 (it's usually up to date)
Make sure you have the correct Stock boot image file for the the software version you have. (if you have May update, use May image, June update then use June Image, etc....)
Use magisk manager to root the boot image you just downloaded. Use the second option like in the photo below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Transfer the patched image file to your computer
Get back to bootloader (download mode) using any method or the below code (USB debugging on)
adb reboot bootloader
Click to expand...
Click to collapse
When in download mode, use the following command on your computer and take note of the result (in case something goes wrong)
fastboot getvar current-slot
Click to expand...
Click to collapse
Use the following command:
fastboot flash boot path_to_zip/patched_boot.img
Click to expand...
Click to collapse
Reboot
Enjoy
Wait one more month
Repeat
Tested scenarios:
Working on TA-1012 to get the Pie May 2019 update from April update
Working on TA-1012 to get the June 2019 update from May update
Working on TA-1012 to get back to latest rom (NB1-5150-0-00WW-B03-update) from April update
Working on TA-1012 to get back to latest rom (NB1-5150-0-00WW-B03-update) from May update
Working on TA-1012 to get back to latest rom (NB1-5150-0-00WW-B03-update) from June update
Screenshot, showing update using system settings to May update, after sideloading full ROM (NB1-5150-0-00WW-B03-update) from a rooted device on May update, proving downgrading works fine.
June files have been updated to the link: https://bit.ly/nokia-nb1
Thanks to Dorian Stoll
Well I got nowhere. The moment I reboot into bootloader, the device isn't visible in adb anymore, but only under "fastboot devices", so "adb sideload path-" fails because it can't find the device. What gives?
VonZigmas said:
Well I got nowhere. The moment I reboot into bootloader, the device isn't visible in adb anymore, but only under "fastboot devices", so "adb sideload path-" fails because it can't find the device. What gives?
Click to expand...
Click to collapse
Boot into recovery and select "apply update from adb" as shown in the photo below (not mine)
Kiwironic said:
Boot into recovery and select "apply update from adb" as shown in the photo below (not mine)
Click to expand...
Click to collapse
I'm still on TWRP at this stage. I can't get past step 7.
Hi guys,
is it necessary to sideload OTA updates? Can I just update the system in settings and then flash a rooted boot image corresponding to the update version?
VonZigmas said:
I'm still on TWRP at this stage. I can't get past step 7.
Click to expand...
Click to collapse
This is for people like me who are not able to run twrp on their phones. If you have twrp you should be able to flash the zip file easy. This guide assumes you have stock recovery
Update: confirmed working for July update as well.
I'm sorry if this seems dumb, but I'm kinda new to all of this. I have TWRP and now I want the July patch, how can I do it?
Update: I gave up and flashed stock recovery.
helscarthe said:
I'm sorry if this seems dumb, but I'm kinda new to all of this. I have TWRP and now I want the July patch, how can I do it?
Update: I gave up and flashed stock recovery.
Click to expand...
Click to collapse
In twrp it should be straight forward to flash a zip file which includes the update. Another option or if this fails, start sideload from twrp like in the following photos
Hi, links no longer working. Does anyone have working links for V5.15D ? I need stock boot image and OTA update to sideload. Thanks.
Unfortunately the phone has been abandoned by the developers. I have got myself a xiaomi 9t.
I'm sorry
Kiwironic said:
Unfortunately the phone has been abandoned by the developers. I have got myself a xiaomi 9t.
I'm sorry
Click to expand...
Click to collapse
It's ok thanks for your work on it!
Kiwironic said:
Unfortunately the phone has been abandoned by the developers. I have got myself a xiaomi 9t.
I'm sorry
Click to expand...
Click to collapse
Oh man, can you still get stock images or whatnot anywhere? I only need the least that will get me back to stock before I turn it in for warranty but not sure where to start.
Sorry man I relied on the other developer's repository so much that I can't offer any tools nor files. I can help you get to stock easy. As Nokia offers the original Rom on their website officially. I believe it can be found here
https://www.nokia.com/phones/en_int/betalabs
Register for beta labs then de register and download the latest firmware they offer you
Kiwironic said:
Sorry man I relied on the other developer's repository so much that I can't offer any tools nor files. I can help you get to stock easy. As Nokia offers the original Rom on their website officially. I believe it can be found here
https://www.nokia.com/phones/en_int/betalabs
Register for beta labs then de register and download the latest firmware they offer you
Click to expand...
Click to collapse
Hey, sorry for the late reply. I attempted to get back to stock via NOST and the 5150 image he provided https://forum.xda-developers.com/no...re-nokia-to-stock-t3867646/page3#post80627823 , but turns out I don't have critical unlocked and seem to have misplaced the unlock key. What can I do next?
VonZigmas said:
Hey, sorry for the late reply. I attempted to get back to stock via NOST and the 5150 image he provided https://forum.xda-developers.com/no...re-nokia-to-stock-t3867646/page3#post80627823 , but turns out I don't have critical unlocked and seem to have misplaced the unlock key. What can I do next?
Click to expand...
Click to collapse
Try unlocking again using the Nokia unlock Web page
Kiwironic said:
Try unlocking again using the Nokia unlock Web page
Click to expand...
Click to collapse
The web page requires a validation code that you get from the unlock app from your phone and as we know the app gives a nice "Device not support" if you try running it on Pie. Tested myself just in case.
Kiwironic said:
Try unlocking again using the Nokia unlock Web page
Click to expand...
Click to collapse
In the end I've decided to just go for it and see what happens. Shouldn't make things worse. Flashed the stock boot image for my security patch right on top of TWRP. The phone booted, but I still couldn't install updates. Tried flashing the next update (May) from both ADB and the SD card - failed with the same download state initialization error. Figured I may as well try the same but with the full .zip of my current OS version (April) and while it took pretty long, it finished with no issues and OTA's started rolling in without a hiccup. Surprisingly I didn't even lose any of my data in the process, which I was preparing for. I guess all that's left is to lock the bootloader?
Anyway thanks for the help!
Team Win Recovery Project 3.6.1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Special Notes:
DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options)
KNOX will be tripped once you flash custom binaries to your phone. Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status
Samsung Firmware OTA (aka System Updates) will no longer work once you flash custom binaries. You can flash custom ROMs if you want to keep the OS up-to-date
All apps that use KNOX like Samsung Pay, Secure Folder and maybe more will no longer work
Download:
Recovery
VBMeta
Multidisabler
Changelog:
21.10.2021
Rebased kernel source to CUH4
16.06.2021
Rebased kernel source to CUC2
03.05.2020
Rebased kernel source to BTB8
25.04.2020
Rebased kernel source to ATA4
07.12.2019
Initial Release
Guide:
If you already have a custom recovery installed:
Boot to your custom recovery
Flash the recovery image
If you are starting from scratch:
Go to Developer Settings and enable "OEM Unlock" option
Power off the device and boot in download mode
In download mode, you will see the long press and volume up option to unlock the bootloader
Unlock the bootloader. That will wipe your device so be sure you made a backup of your data
After bootloader unlock, boot up the phone and make sure it is connected to the internet or it will trigger rmm prenormal
Setup the phone without google account and others
Reboot in download mode and flash the recovery and vbmeta images
Boot to TWRP
Format data in TWRP
Flash the Multidisabler zip
Now you can reboot
Contributors
ponces, geiti94, ianmacd
Source Code: https://github.com/TeamWin/android_device_samsung_a40
Kernel Source Code: https://github.com/ponces/android_kernel_samsung_universal7904
Reserved
I'm really tempted to flash this TWRP and root my A40. Though I know Android 10 has been announced (at least in my region) for April 2020. Should I wait until then? My main concern is, if i flash it now, how easy will it be to upgrade to Android 10 then?
The only real thing I use root privileges for is to remove bloatware completely and edit the hosts file, so I can wait a few months. Also what about dm-verity? Are there any problems there?
My question and can I use this recovery on ITV-A405FNXXU2ASK2-20191218161204?
bishsop said:
I'm really tempted to flash this TWRP and root my A40. Though I know Android 10 has been announced (at least in my region) for April 2020. Should I wait until then? My main concern is, if i flash it now, how easy will it be to upgrade to Android 10 then?
The only real thing I use root privileges for is to remove bloatware completely and edit the hosts file, so I can wait a few months. Also what about dm-verity? Are there any problems there?
Click to expand...
Click to collapse
The choice of waiting is only yours.
In my case I need this as I'm using a custom Treble ROM and not Samsung's firmware.
The ease to upgrade to Android 10 relies only on the your expertise on how to flash the original firmware using ODIN.
At the time of the upgrade you need to use ODIN to flash an original firmware from Android 9 to be able to fully restore the original behavior and flash Android 10.
As far as I'm concerned, DM-Verity is related with both DT and DTBO partitions and those partitions are not even touched during this process.
The ones that are changed are BOOT, RECOVERY and VBMETA to disable a few security procedures from Samsung to be able to flash and boot custom binaries.
Because of this, take in consideration the "Special Notes" section in the first post.
Nevertheless, if the need of changing the hosts file is to block ads, you can reach the same goal by using the "Private DNS" feature introduced in Android 9 as explained here.
costa11 said:
My question and can I use this recovery on ITV-A405FNXXU2ASK2-20191218161204?
Click to expand...
Click to collapse
As you can see in the first post, this TWRP version is for the firmware A405FNXXU2ASJ1 (October's update).
I am still waiting for Samsung to drop A405FNXXU2ASK2 (December's update) sources here to update TWRP.
I'll keep you posted when the sources drop and work on TWRP update begins.
ponces said:
As you can see in the first post, this TWRP version is for the firmware A405FNXXU2ASJ1 (October's update).
I am still waiting for Samsung to drop A405FNXXU2ASK2 (December's update) sources here to update TWRP.
I'll keep you posted when the sources drop and work on TWRP update begins.
Click to expand...
Click to collapse
So I tried to install this recovery on the ASK2 firmware and it worked, there is only one problem when it goes down the brightness does not return anymore remains low! Then another thing I rooted with Magisk is it's not working, come up with an error and then I'll try to take a screenshot!
thank you again for your job
i just updated my rom to the SK2 (downloaded the rom, flashed it with Odin)
then installed you twrp (the SJ1 is OK)
then flashed with magisk manager the boot.img to Root the Rom
and then flashed the param.bin with a better boot logo
thank you so much for your job !!
costa11 said:
Then another thing I rooted with Magisk is it's not working, come up with an error and then I'll try to take a screenshot!
Click to expand...
Click to collapse
Magisk-Root is working for me.
I did this:
[*]Backup of ASJ1 with TWRP
[*]Complete odin flash of ASK1
[*]TWRP - ASJ1 - Version
[*]direct reboot into TWRP
[*]Format Data
[*]Flash Multidisabler
[*]Full Boot
[*]Install Magisk.APK from sd-card
[*]Reboot into TWRP
[*]Flash Magisk
[*]Full boot to check of root access => ok
[*]Reboot into TWRP
[*]Restore of ASJ1-Data
Everything working!
Thanks for the recovery, is working fine with latest ITV (Italian no brand) firmware, to have root is only simple necessary to flash latest Magisk ZIP via twrp (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
i have a big problem about twrp on my phone
I have followed this thread
But when i flash twrp (i have uncheck "reboot" on odin of course) i can't get access to the recovery mode, when i do power button + volume up it doesn't do nothing and show this :
(I have already unlock my boot loader)
I think its DM VERITY who block the access to recovery mode but i can't disable this, cause i can't get access to twrp :/
Thanks for any answers c:
cioce said:
Thanks for the recovery, is working fine with latest ITV (Italian no brand) firmware, to have root is only simple necessary to flash latest Magisk ZIP via twrp (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
Click to expand...
Click to collapse
Can confirm it works with ATA4 (region DBT). Same procedure my post above. With restoring Data as last step there isn't anything lost as well... :good:
Be sure to enable usb debugging after flash of new firmware. Otherwise TWRP flash would fail...
:good:
Leak.dll said:
i have a big problem about twrp on my phone
I have followed this thread
But when i flash twrp (i have uncheck "reboot" on odin of course) i can't get access to the recovery mode, when i do power button + volume up it doesn't do nothing and show this :
...
(I have already unlock my boot loader)
I think its DM VERITY who block the access to recovery mode but i can't disable this, cause i can't get access to twrp :/
Thanks for any answers c:
Click to expand...
Click to collapse
I had some similar problem.
It was a wrong TWRP, I had to try 3 different ones until it finally worked (the one for AJ1 worked for me).
If you are in a bootloop you still can press Volume UP + DOWN and at the same time put the USB cable in when booting. This should set your phone into the download mode and you can flash TWRP or OS again.
Has anyone tried this TWRP build with ATB1 February patch version? It has increased BL version (2->3) so it is not possible to roll back to any older FW...
From my information ATB1 is still the same security patch level as ATA4.
General question: How can I judge the BL version of the firmware?
ruffyrisco said:
Magisk-Root is working for me.
I did this:
Backup of ASJ1 with TWRP
...
Click to expand...
Click to collapse
what TWRP is this and how did you manage to install it before being rooted?
toshibashi said:
what TWRP is this and how did you manage to install it before being rooted?
Click to expand...
Click to collapse
I used the modified TWRP from post #1: https://androidfilehost.com/?fid=4349826312261685733
ruffyrisco said:
From my information ATB1 is still the same security patch level as ATA4.
General question: How can I judge the BL version of the firmware?
Click to expand...
Click to collapse
Well, my info comes from samfw.com/firmware/SM-A405FN/TMZ, not sure how do they extract it.
both ATB1 - samfw.com/firmware/SM-A405FN/TMZ/A405FNXXS3ATB1 and ATA4 - samfw.com/firmware/SM-A405FN/XEZ/A405FNXXU3ATA4 seems like BL (or some OTP bits, I am noob with android internals) bumped from 2 to 3.
(sorry about URL formatting, as a XDA newbie, I am no allowed to post URLs)
xorly said:
both ATB1 - samfw.com/firmware/SM-A405FN/TMZ/A405FNXXS3ATB1 and ATA4 - samfw.com/firmware/SM-A405FN/XEZ/A405FNXXU3ATA4 seems like BL (or some OTP bits, I am noob with android internals) bumped from 2 to 3.
Click to expand...
Click to collapse
As I mentioned earlier ATA4 firmware works fine with TRWP.
But I'm not sure if ATA4 has BL 3.
Does the digit 10 in the firmware number represents the BL?
ruffyrisco said:
But I'm not sure if ATA4 has BL 3.
Click to expand...
Click to collapse
Then reboot into Download mode (you have to do it manually, not via ADB command) and look into top left corner. On ATB1, one of last lines says
Code:
AP SWREV B:3 K:3 S:3
I assume that some fo those numbers (B?) is OTP number set by BL version.
ruffyrisco said:
Does the digit 10 in the firmware number represents the BL?
Click to expand...
Click to collapse
I am not sure which *10* do you mean. It looks like version prefix is bootloader version, number 3 in A405FNXXS3ATB1 or number 2 in A405FNXXU2ASK2. It is the only number which seems to corellate with BL version.
Also, now I can confirm that that this TWRP build (based on A405FNXXU2ASJ1) works with ATB1 firmware! (february sec. patch) Successfuly tested with Phhussons Android 10 GSI quack v213.