Develop Bugs

iovyroot for Nokia-N1(A5CNB19, A5FMB19 Supported)

source code here:
https://github.com/jemyzhang/iovyroot/tree/nokia-n1
{
"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"
}
Since the system is verity on, seems no more things can do.
iovyroot binary for nokia n1:
20160922: View attachment iovyroot.n1.zip
After get the root privilege, boot and recovery can be flashed by dd, with the recovery, the corresponding update package can be flashed by adb sideload.
And also, the boot can be repack for verity off and also the selinux can be disabled.
- turn off selinux
add cmdline parameter: androidboot.selinux=permissive
- turn off system verity
change the fstab, remove "verify" option

How to use it?
Any guide or root step?

jemyzhang said:
iovyroot binary for nokia n1:
20160922: View attachment 3883559
Click to expand...
Click to collapse
latheliao said:
How to use it?
Any guide or root step?
Click to expand...
Click to collapse
ZIP-file with binary attached by jemyzhang contains a guide. Seems to be quite simple to follow.
I can't test it as I'm still on 5.0.2 (CN rooted, but for unkown reasons still unable to flash to FM version) - but it's probably worth a try for those who have already updated to CN or FM 5.1.1 and are stuck with a non-rooted N1.
If there are any voluntaries - please post detailed report. N1-community would definitely appreaciate it! It is such a beautiful device.
It would be especially great if someone with a CN 5.1.1 could report success (I guess it would be a three-step-approach: rooting CN 5.1.1, then switching to FM 5.1.1, then probalby necessary to root again?)

I will test this when I have time (later this week I hope). I will definetely post a guide if I succeed with this.

the boot partition is verity off, you can flash the recovery(FM) to the boot partition, and flash the FM package with sideload.

Hi Jemy,
Really appreciate your work on Nokia N1 and I'm so glad that it is possible to root devices with A5CNB19. However, as a rookie, I have no idea how to follow your guidance and successfully root the tablet. Could you please update some detailed instructions on how to root this device? Thanks again for your kindly work on this tablet.
David
jemyzhang said:
the boot partition is verity off, you can flash the recovery(FM) to the boot partition, and flash the FM package with sideload.
Click to expand...
Click to collapse

steps for change rom from A5CNB19 to A5FMB19
stock recovery of A5FMB19: View attachment recovery.img.zip
for whom want to flash from A5CNB19 to A5FMB19.
A5FMB19 rom download: A5FMB19_update.zip
Important: bootloader must be unlocked. If the bootloader was locked, boot partition will also be verified.
- Unlock bootloader
Attention: data will be lost if you unlock your device
1. enter into fastboot by hold power and volume up key while power on
2. use the following command to unlock the bootloader
Code:
fastboot oem unlock
3. choose "Yes" in the next screen
Steps for flash:
1. boot into fastboot
2. flash recovery image with the following command:
Code:
fastboot flash boot recovery.img
3. boot into 'normal' mode, this will actually boot into recovery
4. press "power" + "vol up" key, which will leading to the text mode
5. choose "apply update from ADB" and confirm with power key
6. upload stock FMB19 package with sideload from pc:
Code:
adb sideload A5FMB19_update.zip

steps for rooting A5FMB19
[Download Section]
- original boot image for FMB19:View attachment boot-A5FMB19.img.zip
- custom recovery: View attachment n1_twrp_fmb19.img-by-jemyzhang.zip
- magiskv6: View attachment Magisk-v6-for-nokia-n1-mod-by-jemyzhang.zip
---- apk: View attachment Magisk_Manager_v1.2.apk
- superuser: View attachment phh-superuser-17-magisk-for-x86-64-mod-by-jemyzhang.zip
---- apk: install from play store me.phh.superuser
magisk v7: pull request has been pushed, waiting for merge.
[Preparation]
Code:
adb push boot.img /sdcard/
adb push Magisk-v6-for-nokia-n1-mod-by-jemyzhang.zip /sdcard/
adb push phh-superuser-17-magisk-for-x86-64-mod-by-jemyzhang.zip /sdcard/
[flash twrp recovery]
first of all unlock the boot loader
1.1. boot into fastboot
1.2. flash recovery image with the following command:
Code:
fastboot flash boot n1_twrp_rec.img
1.3. boot into 'normal' mode, this will actually boot into recovery
[restore boot image]
- restore back the orignal FMB19 boot image:
flash boot.img from recovery(switch to image mode)
[flash magisk and phh-supersu]
That's all
[Anything not ready for twrp]
1. adbd, usb connection error
2. graphic, low performance for text display
3. no signature:::: so flash into recovery partition is impossible

How to unlock boot loader??

Any one try the method? N1 can not unlock bootloader by command from adb before.
Sent from my Redmi Note 3 using XDA-Developers mobile app

Fail to root A5FMB19
I have tried "steps for rooting A5FMB19", but I failed.
As you say, first I adb push three files to the sdcard of N1. Then I unlock the bootloader. But when I unlock it, all the data in the tablet will be cleared.
So, when I want to flash boot.img from recovery, I can't find them in my tablet.

damoguyanzero said:
I have tried "steps for rooting A5FMB19", but I failed.
As you say, first I adb push three files to the sdcard of N1. Then I unlock the bootloader. But when I unlock it, all the data in the tablet will be cleared.
So, when I want to flash boot.img from recovery, I can't find them in my tablet.
Click to expand...
Click to collapse
me too
---------- Post added at 09:59 AM ---------- Previous post was at 09:54 AM ----------
do you have the recovery of A5CNB19，i wanna go back to that version, thank you very much

I have taken your step to root my device . However the twrp failed to mount /data and unable to mount storage .
So could you help me to solve this problem ?
Thank you !

damoguyanzero said:
I have tried "steps for rooting A5FMB19", but I failed.
As you say, first I adb push three files to the sdcard of N1. Then I unlock the bootloader. But when I unlock it, all the data in the tablet will be cleared.
So, when I want to flash boot.img from recovery, I can't find them in my tablet.
Click to expand...
Click to collapse
any solution?

realceday said:
any solution?
Click to expand...
Click to collapse
fist unlock the divice, then restart to the system, if the restart doesn't work, you should flash "fastboot –w" in the fastboot modle。after that, copy the files into your divice, then go to the fastboot and flash twrp。
if you can read chinese, read baidu tieba, goto the nokian1 section(i can't post the url)

Have anyone succeeded with this method ?

I can confirm this working.
Several notes to make:
1. from what I understand, the iovyroot method is only POC, and unrelated to the second approach. ( I actually tried this approach and couldn't get root access)
2. the second approach works for me. Note that both magisk and phh-supersu require two steps of installation: first flash in recovery, and install the correspoding apk in android.
Thank you jemyzhang!

Not able to push the iovyroot.n1 it says : permission denied . even in recovery as in fastboot as in normal boot
i'm actually using A5FMB19

[UNOFFICIAL][TWRP][Recovery] TWRP 3.3.1-0

1 . unlock BootLoader AND Root https://forum.xda-developers.com/v50-thinq/development/lg-v50-temp-root-exploit-via-cve-2020-t4098077
2. Download the required files ( twrp-installer-v3.3.1-V50_ab.zip )
View attachment twrp-installer-v3.3.1-V50_ab.zip
3.Install the corresponding TWRP flash module in Magisk Manager, remember not to restart
The module is one-time, and it will be deleted automatically after TWRP is successfully brushed in
{
"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"
}
4.Re-swipe the Magisk 20.4 card package in Magisk Manager
5.Verify that TWRP is successfully installed
adb reboot recovery
6.Wait for the phone to restart to the TWRP interface, I believe everyone knows what this thing looks like
7.Disable_Dm-Verity can solve the problem of decryption failure after booting

Does this still have the touchscreen issue if you boot from OS to Recovery?

5dprince said:
1 . unlock BootLoader AND Root https://forum.xda-developers.com/v5...g-v50-temp-root-exploit-via-cve-2020-t4098077
2. Download the required files ( twrp-installer-v3.3.1-V50_ab.zip )
3.Install the corresponding TWRP flash module in Magisk Manager, remember not to restart
The module is one-time, and it will be deleted automatically after TWRP is successfully brushed in
4.Re-swipe the Magisk 20.4 card package in Magisk Manager
5.Verify that TWRP is successfully installed
adb reboot recovery
6.Wait for the phone to restart to the TWRP interface, I believe everyone knows what this thing looks like
7.Disable_Dm-Verity can solve the problem of decryption failure after booting
Click to expand...
Click to collapse
Dude. You didn't say to flash magisk again, nor did you credit the author of the twrp. And touchscreen does not work with the adb command, so I do not know why you said to do that instead of the key combo...

Indeed, there are some problems with the touch screen in this TWRP version. Can anyone elaborate on how do I even boot into it with key combination? I've been fiddling with them for about half an hour before I dropped it on the carpet and it booted, and I had exactly one chance to flash everything before a reboot, I'd rather know what I pressed if I ever want to do that again.
UPD: getting into TWRP is almost like on v30: power+volUp, when logo appears you let go of power button and immediately press it again, then proceed to factory reset option which will boot you to TWRP. I'll leave it here in case somebody will google it later.
https://youtu.be/b1lnYdNxVMg

The issue with touch not always working in TWRP is that the stock kernel disables the touch driver when the boot reason is recovery (aka from adb reboot recovery), while via button combo, the reason isnt "recovery", so touch works in TWRP

Is there a way to get twrp image somewhere? If I now have unlocked bootloader, won't I be able to just flash it from fastboot?

Installed it but can't mount my internal storage in TWRP. Anyone else have this issue?

SGCMarkus said:
The issue with touch not always working in TWRP is that the stock kernel disables the touch driver when the boot reason is recovery (aka from adb reboot recovery), while via button combo, the reason isnt "recovery", so touch works in TWRP
Click to expand...
Click to collapse
And what would be the combination of buttons to start the TWRP with active touch functionality? If I install TWRP from fastboot is it different than if I install it from QFIL?

Is there a way to get an img file so we can just flash TWRP from ADB instead using fastboot commands instead of having to use Magisk? I just plan on unlocking the bootloader for now on my Verizon V50 (LG450VM) and not rooting because their are patched Magisk files for that phone yet.

GeoFX said:
Is there a way to get an img file so we can just flash TWRP from ADB instead using fastboot commands instead of having to use Magisk? I just plan on unlocking the bootloader for now on my Verizon V50 (LG450VM) and not rooting because their are patched Magisk files for that phone yet.
Click to expand...
Click to collapse
That would be great.

smitra420 said:
Installed it but can't mount my internal storage in TWRP. Anyone else have this issue?
Click to expand...
Click to collapse
See https://forum.xda-developers.com/t/twrp_3-3-1-for-usa.4304847/.

GeoFX said:
Is there a way to get an img file so we can just flash TWRP from ADB instead using fastboot commands instead of having to use Magisk? I just plan on unlocking the bootloader for now on my Verizon V50 (LG450VM) and not rooting because their are patched Magisk files for that phone yet.
Click to expand...
Click to collapse
is this available yet, for the LM-V500EM?

Didn't work for me 500N problem of decryption failure after booting, how to disable it?

didn't work for me LM-V500EM after boot twrp asks for decryption password ?

GeoFX said:
Is there a way to get an img file so we can just flash TWRP from ADB instead using fastboot commands instead of having to use Magisk? I just plan on unlocking the bootloader for now on my Verizon V50 (LG450VM) and not rooting because their are patched Magisk files for that phone yet.
Click to expand...
Click to collapse
I don't think that's possible since this device does not have a separate recovery partition so this patch unpacks the boot ramdisk and injects twrp code there - not doable via fastboot.

antintin said:
Dude. You didn't say to flash magisk again, nor did you credit the author of the twrp. And touchscreen does not work with the adb command, so I do not know why you said to do that instead of the key combo...
Click to expand...
Click to collapse
Exactly. The pictures no longer display and this magisk is different than the latest. Do we leave dmverity checked in magisk?
I rebooted before re flashing magisk again because I've never done this and its mind boggling to have to flash magisk twice (why couldn't it stick the first time or have an obvious option?). Anyway. Anyone know how to reverse the softbootloop these instructions result in!?!

How do I get root back after magisk flashed twrp and lied? When I go to recovery, its stock. Now when I replace boot_a with magisk patched in edl mode bootloop! This worked the first time why doesn't it any longer?

q-killer said:
How do I get root back after magisk flashed twrp and lied? When I go to recovery, its stock. Now when I replace boot_a with magisk patched in edl mode bootloop! This worked the first time why doesn't it any longer?
Click to expand...
Click to collapse
Why would you want TWRP if you weren't going to replace the OS? Go into TWRP and flash something else, with Magisk as well.
For anyone reading, the button combo to get into TWRP is Vold down + power. As soon as LG Logo starts up, you release power for a second then go back to pressing it. Phone will ask if you want to erase data. Select yes, and yes. Phone will boot TWRP.

TPMJB said:
Why would you want TWRP if you weren't going to replace the OS? Go into TWRP and flash something else, with Magisk as well.
For anyone reading, the button combo to get into TWRP is Vold down + power. As soon as LG Logo starts up, you release power for a second then go back to pressing it. Phone will ask if you want to erase data. Select yes, and yes. Phone will boot TWRP.
Click to expand...
Click to collapse
Thanks for this question, and advice on getting to recovery with keys, it's the only way to get touchscreen support in recovery, and it's a good question... unfortunately my phone no longer asks if I want to erase data for some odd reason when accessing recovery... this really tripped me up. I was trying to flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip, but it was too late in this instance as system was already encrypted. so the mistake made was that I didn't disable dmverity, which needs to be done either before setup, or directly after first restart. Otherwise system starts encrypting and it seems boot_a is encrypted and can't be directly replaced via qfil, since it causes a bootloop at that point. I wasn't able to access and therefore fix NT-Code issue errors (observed after cross flashing) at this point either, so the key is to first backup or get a copy of vmeta_a and boot_a along with other key files, then flash engineering (eng_abl) in qfil so that fastboot can be accessed and then fastboot --disable-verity --disable-verification flash vbmeta vbmeta_a-v50original.bin, place backed up boot_a on phone, patch with Majisk, copy back to pc, then flash patched boot with qfil or fastboot, Then fastboot flash abl_a abl_a(orig-nonENG).bin, also then restore ftm-original and modem_a/b-original with same method in fastboot or using qfil, rebot then *#*#4636#*#* choose automatic and NR/LTE/CDMA/EcDO/GSM/WCDMA , then append NT errors to /Product/OP/cust_path_mapptings.cfg following format there, and then finally flash twrp via magisk but don't reboot, and then reflash magisk.zip, and reboot. Finally, following guides for adaway, revanced, and wallet hiding should work. There are a ton of steps to this phone, especially sprint version.

i have lg v50 450 verizon model number lm-g850 android version 10 g85020j
does not read sim cards.
How to unlock the bootloader on it and flash it. Thank you !!!

Installing TWRP on G4 H815 doesn't work

Hello forum,
I wanted to breathe new life into my old G4 H815, but I didn't come very far, because some commands behave not as expected. Here are the facts:
1.
Bash:
adb reboot bootloader
always works and sets up the device in fastboot mode.
2.
Bash:
fastboot devices
recognises the device.
3.
Bash:
fastboot flash recovery twrp.img
gives positive feedback, though it seems not to work properly, because when it restarts afterwards and asks me if it should wipe all data it wipes the data and doesn't start TWRP.
4.
Bash:
fastboot boot twrp.img
doesn't reboot into recovery mode.
5. I used
Bash:
fastboot getvar all
to make sure that the device is unlocked.
6.
Bash:
adb reboot recovery
takes the phone to recovery mode, but then it stops with a "no command" message and an image with a red triangle and a dead Android robot appears. I pushed all possible button combination, but I couldn't enter the recovery menu.
The phone doesn't have any hardware issues and is basically in a good condition. How can I pinpoint the error?

Try removing the stock recovery before flashing TWRP. Use fastboot erase recovery
Make sure to have a backup for stock recovery should you need to flash it ever again.
Or after flashing TWRP disconnect from PC and use button combination to boot to recovery.

Thanks, but how can I backup the stock recovery? The recovery is located in the /dev directory:
Bash:
lrwxrwxrwx 1 root root 21 2015-01-01 01:00 recovery -> /dev/block/mmcblk0p39
I tried to copy the recovery to the SD card:
Bash:
cat /dev/block/mmcblk0p39 > /sdcard/recovery.img
However, it didn't work, because I get a "Permission denied" error. Maybe i have to root the phone first?

Make a nandroid backup of all your partitions with TWRP, and it should include recovery img as well. Use fastboot boot twrp.img then do a nandroid backup.
However on some phones TWRP can't backup the recovery properly, and if that's the case then do the following:
Root your phone (Flash magisk or supersu, whatever works for you)
Reboot your phone to recovery.
Type adb shell su then dd if=/dev/block/mmcblk0p39 of=/sdcard/recovery.img
This will put recovery.img on your SD card.
I'm not sure if TWRP can properly backup recovery on your device, but trying both methods won't hurt.

How can I root my phone with Magisk without installing TWRP before?
I found the stock roms for my G4 here:
Codefire - Listing of H815
How can I find out which version (10C, 20D...) I need? The recovery is contained in the stocks roms, correct?

The recovery is usually contained in the stock ROM, downloading it to make sure won't hurt.
To find the device's model simply see your device manual.
Or if you remove your device's cover it should be written on the battery.

My device is a H815 with Android 7.0 and software version V29a-EUR-XX. In order to root the phone I would like to install an image file with a rom that is already rooted, but I couldn't find an image with my software version:
[ROOT] TMO/VZW/ATT/SPRINT/INTL Root your LG G4 with Low Effort Root!
Hello all, It's that time of the night where I post things on XDA and wake up to a bajillion PMs. Without further ado, I introduce "Low Effort Root". What is this? Low Effort Root is a root for your LG G4, named such because this is a root we...
forum.xda-developers.com
I could either install another H815 version (how risky is that?) or I could create an image of the rom on my device, root this image and then transfer it back on the phone.

pizza_alarm said:
My device is a H815 with Android 7.0 and software version V29a-EUR-XX. In order to root the phone I would like to install an image file with a rom that is already rooted, but I couldn't find an image with my software version:
[ROOT] TMO/VZW/ATT/SPRINT/INTL Root your LG G4 with Low Effort Root!
Hello all, It's that time of the night where I post things on XDA and wake up to a bajillion PMs. Without further ado, I introduce "Low Effort Root". What is this? Low Effort Root is a root for your LG G4, named such because this is a root we...
forum.xda-developers.com
I could either install another H815 version (how risky is that?) or I could create an image of the rom on my device, root this image and then transfer it back on the phone.
Click to expand...
Click to collapse
How about installing magisk manager on your phone then patching the boot.img through the app?
Installing a different version than your device can cause soft brick and that if you're lucky, so don't even think about it.

I installed Magisk Manager and followed method 2 in this guide:
How to Install Magisk and Root Android Devices with it [2 Methods]
In this comprehensive guide, we will show you how to install Magisk Universal Systemless Interface to root Android devices. There are two different methods to install it – First…
www.thecustomdroid.com
However, I don't know where I could find the correct stock boot image for my device. I can't extract it from my own device, because I need root permissions for that.

pizza_alarm said:
I installed Magisk Manager and followed method 2 in this guide:
How to Install Magisk and Root Android Devices with it [2 Methods]
In this comprehensive guide, we will show you how to install Magisk Universal Systemless Interface to root Android devices. There are two different methods to install it – First…
www.thecustomdroid.com
However, I don't know where I could find the correct stock boot image for my device. I can't extract it from my own device, because I need root permissions for that.
Click to expand...
Click to collapse
I'm sorry, but I can't help you with that :/
Keep searching I got those sites here, here, here and here. Just from typing "H815 stock rom" into google.
I don't know if they're official stock ROM nor if they're tampered with. So use them on your own risk.
Also those sites don't provide MD5 checksum to verify the integrity of the files so I wouldn't recommend them.
If you know someone with the same device from the same vendor in the same region as you then you may ask him to backup his stock ROM for you.
You can try asking a service center, I doubt they'll readily give you the ROM though.
If you absolutely need a custom ROM or root access for some reason, then get a device that has an active developing community. On a side note don't even think about Xiaomi devices. Maybe OnePlus or Pixel.
Goodluck.

I found the matching LG-H815_Official_v29A rom which contains the following files:
{
"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"
}
Is boot.bin the file which can be easily renamed as boot.img so that Idon't need any kind of extractor tool? In the case that the stock rom wasn't unlocked could the patched boot.img re-lock the phone?

pizza_alarm said:
I found the matching LG-H815_Official_v29A rom which contains the following files:
View attachment 5225263
Is boot.bin the file which can be easily renamed as boot.img so that Idon't need any kind of extractor tool? In the case that the stock rom wasn't unlocked could the patched boot.img re-lock the phone?
Click to expand...
Click to collapse
If you already found the stock ROM of your device then you don't need to root to backup your recovery.
I guess you failed to notice the recovery.bin file there haha. Don't be so tense when flashing the ROM friend relax a little and take a breath.
Now just make sure to flash the correct TWRP version of your device.
Goodluck.

Development [ROM][Android 11][OP9Pro] crDroid v7

{
"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
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Pre-installation:
Until TWRP is ready, this version of crDroid comes with prebaked core Gapps
Download LOS recovery
Download Tiny ADB & Fastboot
First time installation (clean flash):
It is recommended to come clean from latest OOS installation
Backup your data to PC, OTG flash drive
Reboot to bootloader (fastboot)
Run fastboot devices to confirm there is connection to the phone
Install LOS recovery with following command fastboot flash boot lineage-18.1-20210615-recovery-lemonadep.img
Power off and reboot to recovery by pressing VOL down + Power from shutdown state
Navigate with volume keys to Factory Reset -> Format data/factory reset and confirm format of data
Go back to main menu and choose Apply update and Apply from ADB
Now adb sideload latest crDroid package with adb sideload crDroid.zip
When asked to confirm flash, do confirm it
Sideload push will go up to 47% and fail - no worry is normal
Reboot to system
Update installation:
Through recovery:
Download latest crDroid zip and reboot to recovery
Choose Apply update and Apply from ADB
Now adb sideload latest crDroid package with adb sideload crDroid.zip
Sideload push will go up to 47% and fail - no worry is normal
Reboot to system
Built-in OTA (slower):
When ready
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sm8350
Download:
ROM https://crdroid.net/lemonadep#crDroid-v7
Changelog: https://crdroid.net/lemonadep#crDroid-v7/changelog
Known issues:
- waiting for more feedback to see
Visit official website @ crDroid.net
crDroid OnePlus 9 Pro Telegram
crDroid Community Telegram
crDroid is built with passion by @neobuddy89 and @gwolfu
If you like our work, do consider a donation to support further device development
ROM OS Version: Android 11
ROM Kernel: Linux 5.4

Awesome.

I have the Tmobile version of OP9pro. Will I need to flash the tmobile modem.img?

burtonlax said:
I have the Tmobile version of OP9pro. Will I need to flash the tmobile modem.img?
Click to expand...
Click to collapse
Testing of this rom has been done on the EU variant
I am not sure how Tmobile version works, but rom side, is same as on LOS

gwolfu said:
Testing of this rom has been done on the EU variant
I am not sure how Tmobile version works, but rom side, is same as on LOS
Click to expand...
Click to collapse
it's best to go global first coming from tmo. No, as long as you don't do an ota on Global. so flash global then boot, then flash custom rom(following their guide).
If u lose service modem is provided (Just unzip) Bootloader fastboot command "fastboot flash modem modem.img
This of course is assuming u got unlock.bin and unlocked Bootloader

Here we go!
Welcome @gwolfu
Hopefully we don't need 11.2.7.7?? It's not out here in EU yet, what's the reason most of the custom roms seem to want the EU build by the way?

CRDroid, fantastic to see this here my favorite ROM since the days of my LG G3! Can't wait to try this out, will sadly be waiting till TWRP tho as I'd prefer to avaoid gapps. Unless there is any chance of a non gapps build also? Cheeky....!

I'll flash and report tomorrow .
post logs through here or telegram?

ryantf420 said:
I'll flash and report tomorrow .
post logs through here or telegram?
Click to expand...
Click to collapse
preferably here as to better keep track of stuff

I know it may not be recommended, but has anyone been able to flash this without using a computer?

phr0zen said:
I know it may not be recommended, but has anyone been able to flash this without using a computer?
Click to expand...
Click to collapse
Since the instructions specify using fastboot (as well as sideloading the rom), that's not possible.

phr0zen said:
I know it may not be recommended, but has anyone been able to flash this without using a computer?
Click to expand...
Click to collapse
without TWRP, not possible

TWRP is death.

This is awesome news brother

So I've been out of the root and rom flashing game for a bit, got it side loaded and everything my issue is i cant get root permissions working wasn't sure how i go about setting it up since all i have worked with on the one plus is magisk and having to install to a .img and input on how to get it working?

crazyvash1 said:
So I've been out of the root and rom flashing game for a bit, got it side loaded and everything my issue is i cant get root permissions working wasn't sure how i go about setting it up since all i have worked with on the one plus is magisk and having to install to a .img and input on how to get it working?
Click to expand...
Click to collapse
extract crdroid.zip content
extract boot.img from payload.bin file using payload dumper
install magisk apk on phone as any other apk (I know we are not rooted yet)
copy boot.img to internal phone storage
open magisk and click on top install button
choose "select and patch a file"
select the boot.img from internal storage
after done, copy magisk patched boot image from Download folder on phone storage, to PC
now on PC, reboot to bootloader and run
Code:
fastboot flash boot magisk_patched-23000_xxxxx.img
check file name to match xxxxx = random generated text
reboot to system and enjoy

gwolfu said:
extract crdroid.zip content
extract boot.img from payload.bin file using payload dumper
install magisk apk on phone as any other apk (I know we are not rooted yet)
copy boot.img to internal phone storage
open magisk and click on top install button
choose "select and patch a file"
select the boot.img from internal storage
after done, copy magisk patched boot image from Download folder on phone storage, to PC
now on PC, reboot to bootloader and run
Code:
fastboot flash boot magisk_patched-23000_xxxxx.img
check file name to match xxxxx = random generated text
reboot to system and enjoy
Click to expand...
Click to collapse
Think you missed the last step to use Magisk again to root the installed boot image?

djsubterrain said:
Think you missed the last step to use Magisk again to root the installed boot image?
Click to expand...
Click to collapse
Not need
I used fastboot flash not fastboot boot so boot is already patched
No temp boot and patch after

gwolfu said:
Not need
I used fastboot flash not fastboot boot so boot is already patched
No temp boot and patch after
Click to expand...
Click to collapse
Didn't notice that, totally right. Sorry.

truly have found nothing broken
except power menu settings only work in crdroid Settings not in System>Gestures>power menu...
Great job

[Simple method] Root N10 5G using Magisk for factory stock

First, as you might now, I am not liable if your phone would be bricked or damaged after this tutorial.
This method has worked perfectly for on my phone, which: OnePlus Nord N10 5G from Metro by T-Mobile. Build Number: 11.0.1.BE88CF. And it should work any rom stock
This tutorial is inspired by andreas__ from this topic. I recommend to take a quick glance before processing here.
General Info:
You need adb and fastboot installed and should know how to use it
You must do this process only once, afterwards you can follow the OTA survival steps
You need to factory hard reset the phone (very important)
Unlock the bootloader
If you are using locked metro by T-Mobile phone, make sure to request the "unlock token" in order to unlock the bootloader.
Google "How to Unlock Bootloader on OnePlus Phones | Unlocked and T-Mobile Variants" for the instructions
After you have unlocked the bootloader using this command:
Code:
fastboot oem unlock
The data will be wiped and it will do the factory reset
Create the boot image:
You need to pull out a clean boot image from your phone. I have used TWRP to do that
flash the latest twrp for this phone:
[TWRP][3.5.2_10][Billie]TWRP for Oneplus Nord N10 5G [BETA]
Use this command to flash it:
Code:
fastboot flash recovery Twrp_3.5.2-10_EduardoA3677-billie_OxygenOs11_Android11.img
boot the phone to twrp recovery, then head to:
Backup > select "Boot (96MB)" > Swipe to Backup
The boot image will be generated in the internal storage under the name "boot.emmc.win"
root and patch the image:
Restart the phone to the system, then download the latest magisk app
Make sure to allow "USB debugging" from the developer Options
Install and open the magisk app then tap on "install" (very top)
tap on "select and patch a file"
select "boot.emmc.win" which is the image that was generated by twrp
Magisk will patch it and place it in the download folder under the name "magisk_patched-23000_Obpf5.img"
Copy the patched image into ADB folder in your PC
flash the patched image:
Reboot the phone into bootloader mode
Then flash the patched image:
Code:
fastboot flash boot magisk_patched-23000_Obpf5.img
Reboot the phone into the system
Hurray! your phone now is officially rooted. You're welcome
I hope you find my instructions useful.

Reserved !!

hamooz92 said:
First, as you might now, I am not liable if your phone would be bricked or damaged after this tutorial.
This method has worked perfectly for on my phone, which: OnePlus Nord N10 5G from Metro by T-Mobile. Build Number: 11.0.1.BE88CF. And it should work any rom stock
This tutorial is inspired by andreas__ from this topic. I recommend to take a quick glance before processing here.
General Info:
You need adb and fastboot installed and should know how to use it
You must do this process only once, afterwards you can follow the OTA survival steps
You need to factory hard reset the phone (very important)
Unlock the bootloader
If you are using locked metro by T-Mobile phone, make sure to request the "unlock token" in order to unlock the bootloader.
Google "How to Unlock Bootloader on OnePlus Phones | Unlocked and T-Mobile Variants" for the instructions
After you have unlocked the bootloader using this command:
Code:
fastboot oem unlock
The data will be wiped and it will do the factory reset
Create the boot image:
You need to pull out a clean boot image from your phone. I have used TWRP to do that
flash the latest twrp for this phone:
[TWRP][3.5.2_10][Billie]TWRP for Oneplus Nord N10 5G [BETA]
Use this command to flash it:
Code:
fastboot flash recovery Twrp_3.5.2-10_EduardoA3677-billie_OxygenOs11_Android11.img
boot the phone to twrp recovery, then head to:
Backup > select "Boot (96MB)" > Swipe to Backup
The boot image will be generated in the internal storage under the name "boot.emmc.win"
root and patch the image:
Restart the phone to the system, then download the latest magisk app
Make sure to allow "USB debugging" from the developer Options
Install and open the magisk app then tap on "install" (very top)
tap on "select and patch a file"
select "boot.emmc.win" which is the image that was generated by twrp
Magisk will patch it and place it in the download folder under the name "magisk_patched-23000_Obpf5.img"
Copy the patched image into ADB folder in your PC
flash the patched image:
Reboot the phone into bootloader mode
Then flash the patched image:
Code:
fastboot flash boot magisk_patched-23000_Obpf5.img
Reboot the phone into the system
Hurray! your phone now is officially rooted. You're welcome
I hope you find my instructions useful.
Click to expand...
Click to collapse
Hate to tell you this but if using twrp just rename magisk apk to magisk zip and install zip it auto patches to the right slot for you and you just confirm the install via magisk in android

scottlam1 said:
Hate to tell you this but if using twrp just rename magisk apk to magisk zip and install zip it auto patches to the right slot for you and you just confirm the install via magisk in android
Click to expand...
Click to collapse
Exactly.

I lost root after the forced OTA on July 31/August 1. Today I followed this guide to install twrp, factory reset, then installed Magisk by renaming the APK and flashing within TWRP. However the SafetyNet check showed "Attestation Failed." I enabled MagiskHide and rebooted, and now pass SafetyNet.
Thank you for this very simple and useful guide. I was able to root with no loss of userdata, saving a lot of time that would otherwise go into creating a backup.

scottlam1 said:
Hate to tell you this but if using twrp just rename magisk apk to magisk zip and install zip it auto patches to the right slot for you and you just confirm the install via magisk in android
Click to expand...
Click to collapse
I don't understand

bgfal3 said:
I don't understand
Click to expand...
Click to collapse
They are saying rename magisk from apk to zip and flash it in TWRP

bgfal3 said:
I don't understand
Click to expand...
Click to collapse
Just rename the APK to .zip extention and install through zip installer in twrp

iam almost ready to root my device i have both zip files from adreas tutorial on how root it.
where those zips files need to be in order to flash it?
cmd can be used, sorry iam new to this.

{
"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"
}

3lgato said:
View attachment 5485447
Click to expand...
Click to collapse
You need to get the unlock token first
Here is the instructions:
https://www.oneplus.com/support/answer/detail/op588

raginhomosapien said:
I lost root after the forced OTA on July 31/August 1. Today I followed this guide to install twrp, factory reset, then installed Magisk by renaming the APK and flashing within TWRP. However the SafetyNet check showed "Attestation Failed." I enabled MagiskHide and rebooted, and now pass SafetyNet.
Thank you for this very simple and useful guide. I was able to root with no loss of userdata, saving a lot of time that would otherwise go into creating a backup.
Click to expand...
Click to collapse
Glad it worked for you. You're welcome

Why it wait forever for attached device, even removing and reconnecting phone?

Rulesless said:
View attachment 5568509
Why it wait forever for attached device, even removing and reconnecting phone?
Click to expand...
Click to collapse
You have to be in fastboot mode before you can flash the recovery. Reboot into fastboot by typing "adb reboot fastboot" (without the quotes). Your phone should then reboot into fastboot mode. NOW, assuming you have already unlocked your bootloader, you can flash the recovery.

If anyone is still having the OEM unlocking greyed out issue, you need to do the device unlock from your phone, select request permanent unlocks then your device will reboot, from there you can then head back into dev options and you will be able to OEM unlock. Hope this helps seems not a lot of people realize this I hunted for the answer all over only to happen upon it when I was about to say forget it.

wcoolj said:
If anyone is still having the OEM unlocking greyed out issue, you need to do the device unlock from your phone, select request permanent unlocks then your device will reboot, from there you can then head back into dev options and you will be able to OEM unlock. Hope this helps seems not a lot of people realize this I hunted for the answer all over only to happen upon it when I was about to say forget it.
Click to expand...
Click to collapse
Just to add to this.....If you are unable to use device unlock because you have not met your carrier's requirements to do so yet you can use the script at this thread and it will open up oem unlock even if your phone is not eligible yet.

I have the N20. No twrp. Flashed a patched boot.img and lost radios. No wifi Bluetooth or sim)mobile data. Hoping that the platform is similar enough that someone could help me recover my device. Phone was sim locked, not sure if that's the issue. I forgot to run the command from the debloat script after flashing the unlock token, shouldn't have rushed this. I don't have a backup of anything though. Was trying to get root to back up everything. Factory resetting did nothing to fix the issue

PsYk0n4uT said:
Factory resetting did nothing to fix the issue
Click to expand...
Click to collapse
LOL never does at this level, just wipes cache and user partition, but nothing of value where we play- the assumption is you (or the bad guys) can't figure out how to write to the system, boot, etc partitions. (snicker).
So the good news is if you can find the EDL image, and follow the procedure to reflash the phone... it should restore everything for you.

(To be clear @PsYk0n4uT I linked you to the N10 EDL thread, not the N20...)

Thanks. So my issue so far. I don't think there is even a stock firmware posted anywhere. Though there is a backup of another device posted. How would I go about finding the EDL files for mine? Can one be created? Or would I need to source that from OnePlus or wait on someone to do that? I actually wasn't aware that I could boot the boot omg without flashing it to test it out first