Root Nord N10 by Sideloading Magisk - OnePlus Nord N10 5G Guides, News, & Discussion

UPDATE: THIS METHOD IS NOT RECOMENDED AS IT MAY LEAD TO A BOOTLOOP AFTER UPDATING YOUR OS, EVEN AFTER REMOVING MAGISK. FOLLOW @ANDREAS_ GUIDE.​​https://forum.xda-developers.com/t/root-n10-using-magisk.4197369/
​
{
"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"
}
​HOW TO ROOT THE NORD N10 BY SIDELOADING MAGISK​
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
If you're on stock firmware or have your boot.img image readily available, check out @andreas__ excellent root guide here: https://forum.xda-developers.com/t/root-n10-using-magisk.4197369/. I recommend following that guide as it is easier to rollback to a non-rooted state if needed, like when needing to update your OS. If you don't care or for whatever reason don't have your boot.img image readily available, continue below.
Spoiler: TL;DR VERSION
Download the recovery image and Magisk​
https://downloads.billaids.dev/0:/Lineage/recovery.img​
https://github.com/topjohnwu/Magisk/releases​
Boot into bootloader/fastbootd adb reboot bootloader​
Boot with the recovery image fastboot boot recovery.img​
Go to "Apply update" and choose "Apply from ADB"​
Sideload Magisk.apk adb sideload magisk.apk​
Reboot, open the Magisk app and let it complete the install.​
Reboot again. Enjoy!​
Spoiler: LONGER VERSION
1. Download the Required Files
a. Recovery image provided by @jnelle from the LineageOS thread.​
Thread: https://forum.xda-developers.com/t/rom-unofficial-lineageos-18-1-oneplus-nord-n10-billie.4255655/
Direct link: https://downloads.billaids.dev/0:/Lineage/recovery.img
b. Latest version of Magisk provided by @topjohnwu on GitHub.​
Releases: https://github.com/topjohnwu/Magisk/releases
Direct link: https://github.com/topjohnwu/Magisk/releases/download/v23.0/Magisk-v23.0.apk
2. Booting into Recovery
We are now going to boot (not flash) your phone with the LineageOS recovery image you downloaded earlier. I'm going to assume you already have:​
android-platform-tools (adb and fastboot)
Bootloader unlocked
USB Debugging enabled
With your phone connected to your computer, open up terminal (or command prompt) and enter the command below to reboot to the bootloader/fastbootd.​​adb reboot bootloader​​Once your phone reboots to the bootloader/fastbootd, enter:​​fastboot boot /path/to/recovery.img​​Replace "/path/to/recovery.img" with the location of the LineageOS recovery image you downloaded earlier. Your phone should now automatically reboot into recovery. Note that once booted into recovery mode, it may still say Pixel Experience. This is normal.​
3. Installing Magisk
Now that you've booted into recovery mode we can go ahead and root your phone with Magisk. Using the volume buttons on your phone to move up and down, highlight "Apply update" then press the power button to select. You should now see "Apply from ADB". Select it.​​Using terminal (or command prompt) on your computer enter:​​adb sideload /path/to/Magisk.apk​​Replace "/path/to/Magisk.apk" with the location of the Magisk application package you downloaded earlier. Your phone will now begin the process of installing Magisk as well as rooting your phone. Once complete, use the volume and power buttons again to back out until you see "Reboot system now". Select it. If all went well you should now be greeted by your lock screen.​​4. Post Install
All that is left now is to open the Magisk app on your phone and let the app finish setting things up. It should ask you to reboot when its done. Enjoy!​

#Reserved

Related

Another Firmware update issue.

Hey all,
Noobie question time! Did the firmware update (or so I think) and now I do have adb connection but not fastboot? or mounted sd card. (Did re-format and now it seems to be available). I messed something up along the way obviously, it looked very much finished after both adb and the phone were inactive for a minute or so.
Currently in what seems to be factory recovery?
{
"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"
}
^^^ Not working?
Android Recovery
HTC?htc_himauhl/htc_himauhl
6.0/MRA58K/buildteam12161528
(up and down for opions)
rbt sys
rbt boot
apply from adb
apply from sd
wipe/factory reset
wipe cache
Also access to everything else works.
What's next guys? I need twp and Venom update. *** Sideload option available didn't want twrp, because of not having fastboot?
Also showing:FILE/mnt/media_rw/ext_sd/0PJAIMG.zip
File not found.
Thanks for all the help, I'd be useless with out you!
I found out that:
1. Android sdk must be installed.
2. Htc sync must be uninstalled but keep its drivers. (install then uninstall it, keep drivers option!).
3. Use twrp 2.9.0.1 (reboot recovery will not appear until you use this twrp) and supersu 2.65.
4. Do not sideload. Use Fastboot and adb. No matter what!.
Download mode is Fastboot commands. Recovery is adb commands.
When you get to the reboot to recovery bit, boot to bootloader with hold vol+& press power. "reboot recovery" should be halfway down the list in bright lime green font. Read carefully. I missed it first time and panicked.
Sent from my HTC One M9 using Tapatalk
shivadow said:
I found out that:
1. Android sdk must be installed.
2. Htc sync must be uninstalled but keep its drivers. (install then uninstall it, keep drivers option!).
3. Use twrp 2.9.0.1 (reboot recovery will not appear until you use this twrp) and supersu 2.65.
4. Do not sideload. Use Fastboot and adb. No matter what!.
Download mode is Fastboot commands. Recovery is adb commands.
When you get to the reboot to recovery bit, boot to bootloader with hold vol+& press power. "reboot recovery" should be halfway down the list in bright lime green font. Read carefully. I missed it first time and panicked.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Shivadow, do you have a link for that twrp I can't seem to find it.
Thanks for the info!
Update:
Got twrp 2.8 on. Won't take newer versions of venom, assuming they need 3.0.
I noticed that the error on the bottom of the device - 0PJAIMG.zip file not found on sd path is RUU related? If so should I try the ruu again as I might have a partial install??
0pjaimg is for flashing but in your case it'll do more damage than good.
You can get twrp 2.9.0.1 from the repo or various sites. Google is your friend.
Sent from my HTC One M9 using Tapatalk

Redmi N8P bootloop suggestions?

Hey all, so I'm desperate for some help, i was stupid enough to unlock my bootloader for my begonia redmi N8P (Miui 12.0.4.0_QGGEUXM), it went successful until I tried to install TWRP, I flashed TWRP.img and ever since I've been bootlooping, I searched the net everywhere to try and resolve this, flashed the same rom with MiFlash and it's either saying mismatched image/ device or fails on something else. Flashing any rom is failing. I have no recovery, just a flashing battery now but still able to get into fastboot.
I'm out of ideas but anyone who's experienced this issue and is willing to help would be much appreciated
Jack.DL said:
Hey all, so I'm desperate for some help, i was stupid enough to unlock my bootloader for my begonia redmi N8P (Miui 12.0.4.0_QGGEUXM), it went successful until I tried to install TWRP, I flashed TWRP.img and ever since I've been bootlooping, I searched the net everywhere to try and resolve this, flashed the same rom with MiFlash and it's either saying mismatched image/ device or fails on something else. Flashing any rom is failing. I have no recovery, just a flashing battery now but still able to get into fastboot.
I'm out of ideas but anyone who's experienced this issue and is willing to help would be much appreciated
Click to expand...
Click to collapse
Witch TWRP version did u installed?
Because there is 2 version.....one for A9 (3.3.1-1104) and another for A10 (3.3.1-1210) If u installed wrong TWRP your phone will bootloop.
I give a guide that i used to ROOT my phone:
If u need any help just ask im rooted my phone multiple time!
[GUIDE][BEGONIA]Unlock Bootloader, Flash TWRP and Root[PROPER]
/* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in...
forum.xda-developers.com
I flashed 3.3.1 - 1210 i typed the Fastboot oem device-info to see if my device is still unlocked because I can't flash back to stock ROM but nothing happenes just freezes me from typing, I flashed another twrp just and it said successful but still can't open recovery to wipe it
Jack.DL said:
I flashed 3.3.1 - 1210 i typed the Fastboot oem device-info to see if my device is still unlocked because I can't flash back to stock ROM but nothing happenes just freezes me from typing, I flashed another twrp just and it said successful but still can't open recovery to wipe it
Click to expand...
Click to collapse
U did like in this screenshot?
(the red line i hided my phone ID)
The first command u need to do while your phone is opened
the second command u need to do while u are in fastboot
and the thirt too
after this u need to reboot your phone to recovery mode!
{
"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"
}
roberto_1986 said:
U did like in this screenshot?
(the red line i hided my phone ID)
The first command u need to do while your phone is opened
the second command u need to do while u are in fastboot
and the thirt too
after this u need to reboot your phone to recovery mode!
View attachment 5254221
Click to expand...
Click to collapse
phone wont boot just in fastboot or flashing battery

Pixel 2XL, adb devices show no devices, no OS, TWRP installed

I've got myself into a bit of a pickle:
trying to install LineageOS on a Pixel 2XL.
I managed to delete the operating system
TWRP is installed and working
When I go to ADB sideload, and try to sideload Lineage, it fails with:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
Click to expand...
Click to collapse
adb devices also doesn't show any devices connected
fastboot seems to work OK.
when in TWRP, Windows Device Manager doesn't show any device (including when ADB Sideload is active) and adb devices shows nothing connected
when rebooted into Bootloader, Windows Device Manager acknowledges the device as Android Device / Android Bootloader Interface
Is there any way to get this phone back up and running or did I bork it? Ideally with Lineage, but the stock Google ROM is fine too.
ADB isn't necessary to install a Custom ROM like LOS: this is done by means of Fastboot what TWRP ( you confirmed it's actually working ) internally runs - what of course requires that device's bootloader got unlocked beforehand.
1. Within the TWRP screen, head over to the Wipe section. Then tap on Advanced Wipe and select Dalvik/ART Cache, System, and Data from the menu. Do not select Internal Storage.
{
"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"
}
2. Then go back to the TWRP home screen, navigate to the downloaded custom ROM and perform a right swipe to flash it.
3. You may now finally reboot your device to the newly installed ROM. For that, head over to Reboot from TWRP and select System.
Thanks for your help. I wasn't able to do that because I didn't have the image on the device and there's no SD card for it.
I did manage to flash it back to stock ROM. In case it's useful to anyone, I did it via flash.android.com
I am having the same problem. I was able to install ProtonAOSP but it is not quite right. Android flash sight is awesome. I use it over and over.

SHARP RECOVERY + Stock recovery + Magisk (3 in 1)

Hello​​This method allows you run custom recovery SHRP (like TWRP), Stock recovery and Magisk Delta 25.2 using the same .img file that flashed to recovery_ramdisk partition​( you will keep stock erecovery ramdisk untouched)​​Download​​Installation:​1. Boot into fastboot: switch off your phone -> Hold vol- while usb connected
2. Flash SHRP-stock-recovery-Magisk-v2.img : fastboot flash recovery_ramdisk and drag & drop .img file to terminal
3. Reboot.
4. Done
​Steps:​A- Boot to system with magisk enabled
while you phone is off and not connected to USB
press Power + Vol+
B- Boot to SHRP recovery
while you phone is off and not connected to USB
Press Power + Vol+
on the yellow warning screen....... press vol+ for 2 sec and release and repeat this for 6 times
C- Boot to stock recovery
boot to SHRP using the pervious method
press "Tweaks" on the main screen
select "Stock Recovery " and press Flash
wait 10 seconds
Touch the middle of the screen one time and use Vol+/- and power Button for navigation
{
"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"
}
Hello. I want to ask about entering the SkyHawk recovery, because the key combination, that You supplied only applies to injecting the Magisk to standard Android boot sequence. Pressing the "Power" + "Volume+" key yields the same results every time, leading to replaced "Stock" recovery. Can You explain this? Thank You.
DeVance said:
Hello. I want to ask about entering the SkyHawk recovery, because the key combination, that You supplied only applies to injecting the Magisk to standard Android boot sequence. Pressing the "Power" + "Volume+" key yields the same results every time, leading to replaced "Stock" recovery. Can You explain this? Thank You.
Click to expand...
Click to collapse
To enter the SkyHawk, You have to do two steps
1- Press Power + Vol+
Then
2- on the yellow warning screen....... press vol+ for 2 sec and release and repeat this for 6 times
I just write here to thank you for this recovery so much!!! You saved me a lot of headache, got a TWRP bootloop after whatever stuff I did with the phone - been already prepared to go through all the long process of reinstalling Lineage from starting with going back to stock rom etc...
1 question: there is magisk, 25.2, I updated to 26.1, but I'm unable to root with patching the boot.img
.... but Just got to know what Ramdisk: NO does mean from this article:
How to root your Android smartphone: Google, OnePlus, Samsung, Xiaomi, and more
Rooting your phone is still possible — and fun — these days. Here's how to do it on your Android device.
www.xda-developers.com
-could you help me with getting root? I guess your guide might include it, but I'm a noob
lulzor said:
1 question: there is magisk, 25.2, I updated to 26.1, but I'm unable to root with patching the boot.img
View attachment 5899347
.... but Just got to know what Ramdisk: NO does mean from this article:
How to root your Android smartphone: Google, OnePlus, Samsung, Xiaomi, and more
Rooting your phone is still possible — and fun — these days. Here's how to do it on your Android device.
www.xda-developers.com
-could you help me with getting root? I guess your guide might include it, but I'm a noob
Click to expand...
Click to collapse
You can root your device using one of these two methods
1- Magisk --> Guide from here
Spoiler: Tweaks--> Spoiler: TWRP on Erecovery, Magisk on Recovery Setup
2- KernelSU ---> Guide from here

Development [Recovery] [a32] Pitch Black Recovery Project [Stable-ish, Unofficial]

{
"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"
}
Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based On TWRP version: 3.7.0
PitchBlack version: 4.0
For device: a32
Maintainer: Ahnet (@Captain_cookie_200 )
PitchBlack source:
PitchBlack Recovery Project
Open-Source Android Recovery Project. PitchBlack Recovery Project has 216 repositories available. Follow their code on GitHub.
github.com
Device tree: https://github.com/ahnet-69/pbrp_device_samsung_a32
Kernel source: https://github.com/ahnet-69/android_kernel_samsung_a32-recovery
Features
Code:
Fully native android like UI
Supports Treble and non-Treble ROMs
Up-to-date kernel, built from sources
Full dark theme with changeable accents
Reorganized menus
Disable DM Verity
Use AromaFM as default file manager
Various tools are include
Universal flash-able file for all variant of a device
Many bug fixes & optimization & much more
Status
stable-ish
Tested on:
SM-A325F (by me)
other models unknown. But should work.
Please report back so i can update the op
Downloads
Click here.
Bugs
1. TWRP cannot decrypt userdata if you set lockscreen. (someone said it works, other it doesn't, so I'll just leave it here, YMMV)
2. Flashing anything shows many "unlock" red lines. (They are currently harmless by our knowledge).
3.USB-OTG
4. Saving settings​
Installation Instructions
Code:
If you have TWRP or any custom recovery installed and bootable, you can upgrade instead; Look below.
<!> the installation will require WIPING DATA. You will also lose access to all Knox-based solutions like Secure Folder.
Backup every precious data you have on your phone.
<!> PC is required. Windows is preferred. (You probably know what you are doing when using Linux/Heimdall. We don't talk about Macs)
Unlock Bootloader:
1. Go to Settings > About Phone > About Software. Tap build number (10 times) until "you are now a developer" toast shows up.
2. Go back, go to Developer Settings.
3. Turn on OEM unlock toggle.
4. Turn off your phone, hold vol-up + vol-down, then plug in charging cable (please don't use 3rd-party charging-only cable, it must have data transfer capability).
5. Your device will boot into download mode with a warning. Accept it.
6. Hold volume-up until the phone shows the bootloader unlock panel "Unlock Bootloader?".
Press volume-up again. Now your phone bootloader is unlocked.
<!> It will now begin the process of wiping data. Let it do its job.
7. When it reboots to OS, finish setting up your device.
8. Double check to make sure OEM Unlock is still ON.
 
Preparing for the installation:
1. Download everything above onto your PC.
2. Rename PBRP recovery img file to recovery.img and add it to archive using any archiver and select gnu tar.
3. Install Samsung USB Driver.
4. Open Odin.
5. Connect your phone to your PC. There should be a COM entry on the top.
6. Make sure your phone is in Download Mode. (see step 4 of section Unlock Bootloader)
7. Make sure that OEM LOCK and REACTIVATION LOCK on your screen show "OFF". If it's not off, DO NOT PROCEED ANY FURTHER.
<!> For those with lock ON, use your device for 7 days without rebooting once. Then check the locks above again.
‎  
 
Installing:
1. Ensure phone is in Download mode.
In Odin:
Load in Userdata: VBMeta_disabler.tar file.
Load in AP: PBRP TAR file.
2. Prepare yourself. keep your hand on Volume-up and Power button (don't press yet).
3. In Odin, press Start. It will flash, then reboot. When the screen turned off, quickly press Vol-up and Power button to boot to recovery (this should take about 20~30 seconds).
<!> You should have PBRP up and running now.  
 
Post-Installation:
MUST: Trigger Multi-disabler.
1. In PBRP, go to Terminal.
2. Type multidisabler, then enter. If it fails with something about vendor free space, run it again.
3. Run multidisabler again.
4. Go to main screen. go to Wipe > Format Data, type yes then swipe.
5. Reboot to Recovery. Now you can do other stuff.
 
Should: Backup all vital partitions:
1. In PBRP, go to Backup
2. Backup: EFS, Modem, NVRAM.
Enjoy: Reboot your phone to have a rooted stock, install custom stuff or do whatever you want.
Upgrade:
<!> Use when you already have any custom recovery installed (TWRP, SHRP, Ofox and the likes)
1. Download the recovery image.
2. Copy it to phone, then reboot to PBRP (Combo is Power + Volume-up)
3. Go: Install > select recovery.img file > select Recovery
4. Swipe to confirm flashing.
5. If success, reboot to recovery.
<!> You can also use Odin to upgrade, the steps similar to the Install section. All Post-installation, if already done, is unnecessary to do again.
Credits:
To the PBRP and TWRP team and everyone involved in making this all work.
@Long266 For his kernel and amazing work.
@ianmacd For multidisabler.
@afaneh92 For his a32x base tree and MTK-Samsung multidisabler.
@KrutosVIP For his experimental lineage kernel source from here.
@LehKeda and his team for lzma compression tool from here.
reserved
reserved
For people wondering why this recovery takes a long time to boot.. its because our phone only has 32mb for recovery partition. So its impossible. The original builds were around 35MB. I had to resort to lzma compression which is slower. but hey atleast it boots

Categories

Resources