[MOD] Disable Forced Encryption on Robin [Updated 2016-10-09]

[MOD] Disable Forced Encryption on Robin [Updated 2016-10-09] - Nextbit Robin

I've modified Robin's boot.img to disable forced encryption.
With encryption gone, you'll be able to use TWRP to flash mods etc, without having to wipe your data every single time.
Other benefits include faster performance and better battery life.
Unfortunately, to actually remove the encryption - you will need to format one last time.
But once done and set up, you'll see that your phone is no longer encrypted.
{
"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"
}
Requirements:
- Unlocked bootloader
- PC / Mac
- fastboot (+ USB drivers if needed) -or- existing TWRP install
Instructions:
If you're using TWRP:
1. Perform a factory reset from within TWRP and reboot back into it (Note: This isn't required if your upgrading from an existing unencrypted stock install).
2. Flash the included zip file
3. Reboot
Manual flash using fastboot:
1. Download the zip and extract the boot.img file
2. Reboot your Robin into fastboot mode
3. Flash using the command:
Code:
fastboot -i 0x2c3f flash boot boot.img
4. Factory reset. (This isn't required if your Robin is already unecrypted and you simply want to update your /boot)
Note: If you skip this step, your phone will remain encrypted.
5. Reboot
Rollback:
1. Re-Enable encryption from Settings -> Security -> Encrypt Phone
2. Flash the stock boot.img
Credits:
@reddv1 for the original modification instructions (adapted from Nexus 5X) and @osm0sis for AIK
----
Disclaimer: Disabling encryption on your phone *will* reduce it's security. These files / instructions are provided only for those who understand and accept the risks of using an un-encrypted device, and are comfortable with modifying the internals of their phone. I will not be held responsible for any loss or damages occurred as a result of following the instructions and/or downloading the files listed on this page.

Thanks, worked well!
Thank tested, will se if it gets any faster. Have been having some problem with lag that comes from time to time that I haven't seen on other devices.
Otherwise, great to see support for such a small phone!

The Robin devs are trying to be Community friendly as much as possible its good to see.

can it still be updated using this mod boot ?

kanded said:
can it still be updated using this mod boot ?
Click to expand...
Click to collapse
Unfortunately no, because the OTA includes an updated delta for the kernel as well (which means the /boot needs to be 100% stock).
If you want to install via the OTA, you need to restore the stock boot.img (and the system partition - if you're rooted or modified it in any way, and the recovery too, if you have TWRP installed).
Alternatively, you may simply flash the updated stock ROM zip on top of your existing install - just be sure to flash the new boot.img zip immediately after (as well as SuperSU and any other mods you may have, if you want to preserve your current setup).

Thank you for this [deXter] it works great.
However does anyone have a solution for how to get rid of the 5 sec nag screen popping up at reboot?
Thanks in advance/arc.

For June update 350 please.

I need help!
When I boot up and finish setup ,my battery percentage said : 3.0858 % and Wi-Fi wasn't turning on did I do something wrong?

Angeldgaf said:
When I boot up and finish setup ,my battery percentage said : 3.0858 % and Wi-Fi wasn't turning on did I do something wrong?
Click to expand...
Click to collapse
This mod only allows you to use your phone unencrypted - it shouldn't affect your battery or WiFi. Are you sure you flashed the correct version?
Goto Settings - About. If you're on the June 1 ROM (Build 00WW_1_350) then your kernel version should say 3.10.84 Wed Jun 1. If these numbers do not match then restore to the latest factory image/ROM and start over. Also, have you tried a factory reset yet?

For 450 Please

Updated for build 450.

Hi everybody! Just receveid the OTA notification
I'm currentyl on 6.0.1 1450 rooted with twrp, do you have the modified boot.img for the Nougat beta as well? Thanks

Many thanks for this work. Getting the Robin rooted and usable was a struggle compared to the Nexus4. This mod helped greatly.

Boot image for N88 please. Thanks in advance.

So did I understand right, I only can use this mod for stock ROM (not for LineageOS 14.1)?

Steffen1st said:
So did I understand right, I only can use this mod for stock ROM (not for LineageOS 14.1)?
Click to expand...
Click to collapse
Yes. Lineage does not have forced encryption.

[deXter] said:
I've modified Robin's boot.img to disable forced encryption.
With encryption gone, you'll be able to use TWRP to flash mods etc, without having to wipe your data every single time.
Other benefits include faster performance and better battery life.
Unfortunately, to actually remove the encryption - you will need to format one last time.
But once done and set up, you'll see that your phone is no longer encrypted.
Requirements:
- Unlocked bootloader
- PC / Mac
- fastboot (+ USB drivers if needed) -or- existing TWRP install
Instructions:
If you're using TWRP:
1. Perform a factory reset from within TWRP and reboot back into it (Note: This isn't required if your upgrading from an existing unencrypted stock install).
2. Flash the included zip file
3. Reboot
Manual flash using fastboot:
1. Download the zip and extract the boot.img file
2. Reboot your Robin into fastboot mode
3. Flash using the command:
Code:
fastboot -i 0x2c3f flash boot boot.img
4. Factory reset. (This isn't required if your Robin is already unecrypted and you simply want to update your /boot)
Note: If you skip this step, your phone will remain encrypted.
5. Reboot
Rollback:
1. Re-Enable encryption from Settings -> Security -> Encrypt Phone
2. Flash the stock boot.img
Credits:
@reddv1 for the original modification instructions (adapted from Nexus 5X) and @osm0sis for AIK
----
Disclaimer: Disabling encryption on your phone *will* reduce it's security. These files / instructions are provided only for those who understand and accept the risks of using an un-encrypted device, and are comfortable with modifying the internals of their phone. I will not be held responsible for any loss or damages occurred as a result of following the instructions and/or downloading the files listed on this page.
Click to expand...
Click to collapse
Boot.img for N108?

Use the modified FED Patcher for the Robin from this thread:
https://forum.xda-developers.com/ne...d-patcher-robin-forceencrypt-disable-t3352006
It worked fine for me on 108. After flashing the latest 108 7.1.1 file from the Razer forums, I flashed TWRP 3.1.0-0, then the FED Patcher, and finally Super SU 2.82.

Related

[TWRP] TWRP/No-Verity Kernel for Moto E5 (Nora)(XT1944-2/-4)

Hi guys, today I'm going to explain you, how to use TWRP and also how to disable forced encryption
Very Important!!!!
Works for all ROMs included stock ROM
Take a backup of boot partition with TWRP in case of something goes wrong
Pre-requisites
1.- Unlocked Bootloader
2.- PC, drivers installed and plattform tools folder: https://www.dropbox.com/s/c3c8rev5e40gy5b/platform-tools-latest-windows.zip?dl=0
3.- TWRP for Moto E5 Play by @CodyF86 : https://androidfilehost.com/?fid=3700668719832239867
4. No verity kernel by @MotoJunkie01 (Only for XT1944-2 or XT1944-4!!!!) : https://drive.google.com/file/d/1NcyuFRgvvRiS5MT5Jxl3uS3XHCnULBMc/view
5. fstab.qcom by CodyF86 also: https://androidfilehost.com/?fid=674106145207491856
Procedure
1.- While you have downloaded all necessary files, go to platform tools folder, and put there TWRP image
2.- Reboot your phone onto fastboot/bootloader, then open cmd and boot into TWRP with this code: fastboot boot twrp_james.img (don't try to flash it because it won't work, and you will need to do that in order to use TWRP, all the time!!!)
3.- While you are in TWRP, go to bakcup and select everything, put the backup into SD Card to prevent some accidents. (The time that it will take depends on how much things you have on your phone)
4.- When backup it's done reboot to bootloader and flash the no-verity kernel
5.- Reboot system
6.- Then use some root explorer, this one is free and very useful https://forum.xda-developers.com/showthread.php?t=1523691
7.- Copy downloaded fstab.qcom and go to vendor/etc, the replace the file with the new one and reboot
8.- Boot again into TWRP, and swipe for factory reset, then format data (Remember that you'll lost your data
9.- Reboot the device, and wait.
This method is easier than the other and works fine, if you go to settings/security you'll see that device is encrypted but if you open that option, you'll notice that encryption is gone.*
Thanks to @MotoJunkie01 for the kernel
Thanks to @CodyF86 for TWRP and fstab.qcom

Nice guide @Fersho. Clear, informative, comprehensive and easy to follow.

MotoJunkie01 said:
Nice guide @Fersho. Clear, informative, comprehensive and easy to follow.
Click to expand...
Click to collapse
Thanks to you for helping with the kernel, I'm very thankful with you

Fersho said:
Thanks to you for helping with the kernel, I'm very thankful with you
Click to expand...
Click to collapse
No problem. I'm glad you posted a guide with the kernel and supporting files to help others. That's what it's all about.

MotoJunkie01 said:
No problem. I'm glad you posted a guide with the kernel and supporting files to help others. That's what it's all about.
Click to expand...
Click to collapse
Then now I'm going to share how to install RR and Pie GSI and also the way to fix lag on both Oreo/Pie

where can we get the verity kernel for moto e5 1944-3

Will the no verity kernel work for XT1944-5?

Mahendra11 said:
Will the no verity kernel work for XT1944-5?
Click to expand...
Click to collapse
Maybe, try by your own risk, make a backup of boot partition because is the one that you'll need in case of something goes wrong

Thread updated, I've noticed that the previous method didn't work at all, and also I discovered that stock rom works fine without encryption, then if stock is decrypted, other roms won't be encrypted anymore

No verity kernel link is down pls re-upload it bro

Fersho said:
Thread updated, I've noticed that the previous method didn't work at all, and also I discovered that stock rom works fine without encryption, then if stock is decrypted, other roms won't be encrypted anymore
Click to expand...
Click to collapse
Re upload please

borksek said:
Re upload please
Click to expand...
Click to collapse
Sorry but I only have stock for XT1944-4 the other stock roms are lost, if somebody had downloaded the others then he could upload them

Fersho said:
Sorry but I only have stock for XT1944-4 the other stock roms are lost, if somebody had downloaded the others then he could upload them
Click to expand...
Click to collapse
Please I have the XT1944-4 could send me the file no Verity Kernel

Do you have a non-verity kernel for XT1944-3? please (single sim variant)

no-verity undownloadable
Fersho said:
Hi guys, today I'm going to explain you, how to use TWRP and also how to disable forced encryption
Very Important!!!!
Works for all ROMs included stock ROM
Take a backup of boot partition with TWRP in case of something goes wrong
Pre-requisites
1.- Unlocked Bootloader
2.- PC, drivers installed and plattform tools folder: https://www.dropbox.com/s/c3c8rev5e40gy5b/platform-tools-latest-windows.zip?dl=0
3.- TWRP for Moto E5 Play by @CodyF86 : https://androidfilehost.com/?fid=3700668719832239867
4. No verity kernel by @MotoJunkie01 (Only for XT1944-2 or XT1944-4!!!!) : https://drive.google.com/file/d/1NcyuFRgvvRiS5MT5Jxl3uS3XHCnULBMc/view
5. fstab.qcom by CodyF86 also: https://androidfilehost.com/?fid=674106145207491856
Procedure
1.- While you have downloaded all necessary files, go to platform tools folder, and put there TWRP image
2.- Reboot your phone onto fastboot/bootloader, then open cmd and boot into TWRP with this code: fastboot boot twrp_james.img (don't try to flash it because it won't work, and you will need to do that in order to use TWRP, all the time!!!)
3.- While you are in TWRP, go to bakcup and select everything, put the backup into SD Card to prevent some accidents. (The time that it will take depends on how much things you have on your phone)
4.- When backup it's done reboot to bootloader and flash the no-verity kernel
5.- Reboot system
6.- Then use some root explorer, this one is free and very useful https://forum.xda-developers.com/showthread.php?t=1523691
7.- Copy downloaded fstab.qcom and go to vendor/etc, the replace the file with the new one and reboot
8.- Boot again into TWRP, and swipe for factory reset, then format data (Remember that you'll lost your data
9.- Reboot the device, and wait.
This method is easier than the other and works fine, if you go to settings/security you'll see that device is encrypted but if you open that option, you'll notice that encryption is gone.*
Thanks to @MotoJunkie01 for the kernel
Thanks to @CodyF86 for TWRP and fstab.qcom
Click to expand...
Click to collapse
hello first congratulations for this tutorial and your work, but there is a small problem with the famous no-verity ^^ it is impossible to download would it be possible to have new links? thank you in advance!!

Hi there. I tried a thousand times now ... no succeed. Everytime I try to boot to twrp_james.img the screen is not accessable anymore. No interaction possible.
Switching device off -> switching device on .... even the "swipe to unlock" doesn't work. I use Motorola Moto E5 Nora XT1944-2.
Any ideas?!

honk0504 said:
Hi there. I tried a thousand times now ... no succeed. Everytime I try to boot to twrp_james.img the screen is not accessable anymore. No interaction possible.
Switching device off -> switching device on .... even the "swipe to unlock" doesn't work. I use Motorola Moto E5 Nora XT1944-2.
Any ideas?!
Click to expand...
Click to collapse
I have the same problem, I tried everything.
I'm unable to use TWRP (james).
after "fastboot boot twrp_james.img"
TWRP comes up with the Mount/dycrypt your data screen, a mouse pointer is visible in the middle. No user interaction is possible twrp doesn't seem to respond to touch screen user input.
Also the "No verity kernel by @MotoJunkie01 (Only for XT1944-2 or XT1944-4!!!!) : https://drive.google.com/file/d/1Ncy...XHCnULBMc/view" link is dead. Can someone reupload this files.
Does anybody have a fix for this problem? I'm using the Moto E5 XT1944-2.

honk0504 said:
Hi there. I tried a thousand times now ... no succeed. Everytime I try to boot to twrp_james.img the screen is not accessable anymore. No interaction possible.
Switching device off -> switching device on .... even the "swipe to unlock" doesn't work. I use Motorola Moto E5 Nora XT1944-2.
Any ideas?!
Click to expand...
Click to collapse
I found a solution to use twrp on the Moto E5 Nora XT1944-2:
Use a micro usb to usb adapter (OTG adapter) and connect a mouse to you phone, now you can use twrp using the mouse.
{
"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"
}

Here is my no-verity kernel for xt1944-3 succesfully working
please OP add this to the thread!
https://www.mediafire.com/file/u52pxc21arlktn4/patched_boot.img/file

Can I install the No-Verity-opt-Encrypt zip instead of installing the kernel?

[ROM][Custom] - = EDGE PURE EDITION = -

Can i Flash from Lineage or need stay in stock?

VitilinVk said:
Can i Flash from Lineage or need stay in stock?
Click to expand...
Click to collapse
"New and Clean Stock firmware is required"

Upgraded Edge Pure Edition!
- created an image in a different format which reduced its size by 6 GB;
- full mount of system in r/w and r/o, allowing the system to boot up fully if you forget to put the system in r/o after making edits to the system partitions;
- updated GApps to the base of 27/02/21.

I'm not sure if you actually know the rules but wrz are not allowed

Upgraded Edge Pure Edition!
- updated ROM to the latest versions of stock firmware QPD30.114-80-4 (09 March 2021) ;
- updated GApps to the base of 12/03/21.

Upgraded Edge Pure Edition!
- Chrome bug fixed

Updated the ROM to a version based on Android 11(R).

Anyone using this daily?

I use. Why can't this ROM be used as the main firmware?

Hi, I tried installing the android 11 version of this from after clean restoring to stock. I installed the .img to the super partition and the phone wont boot. I get the "unable to open block device /dev/block/loop (20, 19, 18, 17): no such device or address. Any help? Thanks

Have you fully read and followed all the points in the instructions? Have you installed Magisk?
To install Edge_R_Pure_Edition, the firmware RPD31.Q4U-39-26-4, Android 11, must be installed on the device.
Download Stock Android 11

Nicktsaab said:
I get the "unable to open block device /dev/block/loop (20, 19, 18, 17): no such device or address.
Click to expand...
Click to collapse
This message appears because TWRP is not adapted to Android 11. Ignore it.

ilia3367 said:
Have you fully read and followed all the points in the instructions? Have you installed Magisk?
To install Edge_R_Pure_Edition, the firmware RPD31.Q4U-39-26-4, Android 11, must be installed on the device.
Download Stock Android 11
Click to expand...
Click to collapse
Ahh thank you, I was trying to install on the Android 10 base. Thanks!

what is the difference between r and q? android 10 and 11 i assume?
also ive been out of the rom loop for quite a while (lg g8, just got unlock like a month ago), what is wrz and why is it not allowed? just curious.

im having a weird issue. i bought 2 edges recently, and wanted to install this rom. both are on final android 10 firmware, and im flashing the q img. obviously both are bootloader unlocked and using twrp 3.5.2.
i followed instructions on one, and it went perfectly fine no issues. on the second whenever i flash the image it wont boot and the twrp log has a few errors about partitions. also there are 2 super partitions listed. even restoring my bone stock twrp image or flashing the factory fimware i have the same issue and the twin super partitions persist. the phone will boot on the stock rom fine however.
edit: weirdness continues, now all of the sudden the rom image flashed perfectly fine, when i rebooted back to twrp for magisk.zip i had no errors. however there STILL is 2 supers listed. but i flashed magisk and booted to system... and it boots. idk.
in the select partition to flash to menu the partitions listed (in order) are: boot, dtbo, boot logo, recovery, super, vbmeta, vbmeta system, super. ive tried both instances of super and both had problems except for this time where it succeeded (i did the first instance this time).
i should also note that this was like this when i made my initial twrp backup, there were 2 super partitions in the backup menu. but, the other phone that had no issues, did NOT have 2 super partitions at any point. again... idk.

Unfortunately, I didn't understand a lot of it, because I don't know English very well.
The fact that in TWRP in Backup you see two Super partitions, it's not a big deal. Choose both, but in fact your backup will have one Super partition.

its just strange but i guess if it works.
but im also having issues with applications. for one, the asus gallery and file browser that are bundled always ask for storaage permissions, even if i grant them they wont launch and keep asking for permissions. wipe data, force stop, grant permissions again, nope they still ask for permissions. i dont know whats going on with them. also i cant set a picture wallpaper. not with gallery, google photos, google gallery, nothing. i get a notification that says "error, could not load media" every time i do it no matter what app i try to use. live wallpapers are fine.

There should be no such problems. This behavior can only be when you try to make these applications (Asus Gallery, Asus File Manager) system applications using, for example, RootExplorer.
I don't have this problem even after restoring a backup.
Install ROM on a clean, re-installed stock firmware.

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

Development [Recovery] [A325x] [Stable-ish, Unofficial] TWRP 3.7.0_12.1 - Galaxy A32 4G

{
"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:
#include <not_my_phone.h>
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* 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.
*/
TWRP 3.7.0_12.1 - Samsung Galaxy A32 4G
Current Status: Stable-ish
Supported Models:
SM-A325F: tested by @Long266 .
SM-A325M: tested by @Melky777 .
SM-A325N: not tested.
Bugs known so far:
TWRP cannot decrypt userdata if you set lockscreen. (one said it works, other it doesn't, so idk I'll just leave it here, YMMV)
Flashing anything shows many "unlock" red lines. (They are currently harmless by our knowledge).
USB-OTG
<!> There can be many more bugs unknown to me and testers. Report as soon as you face problem.
<!> PSA: I don't have the device to verify some of these bugs.
Download:
TWRP (3.7.0): https://github.com/almondnguyen/twr...a32-20230208/TWRP-3.7.0_12.1-a32-20230208.tar
Samsung USB Driver: https://developer.samsung.com/mobile/android-usb-driver.html
Odin (3.14.4): https://samfw.com/Odin/Samfw.com_Odin3_v3.14.4.zip
Disable VBMeta: https://forum.xda-developers.com/at...236537/?hash=f7249adaefe16f3aeac3256a63063f0a
(Optional) Root using Magisk: https://github.com/topjohnwu/Magisk/releases/
Install:
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:
Go to Settings > About Phone > About Software. Tap build number (10 times) until "you are now a developer" toast shows up.
Go back, go to Developer Settings.
Turn on OEM unlock toggle.
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).
Your device will boot into download mode with a warning. Accept it.
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.
‎
When it reboots to OS, finish setting up your device.
Double check to make sure OEM Unlock is still ON.
‎ ‎
Preparing for the installation:
Download everything above onto your PC.
Install Samsung USB Driver.
Open Odin.
Connect your phone to your PC. There should be a COM entry on the top.
Make sure your phone is in Download Mode. (see step 4 of section Unlock Bootloader)
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:
Ensure phone is in Download mode.
In Odin:
Load in Userdata: VBMeta_disabler.tar file.
Load in AP: TWRP TAR file.
Prepare yourself. keep your hand on Volume-up and Power button (don't press yet).
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 TWRP up and running now.
‎
Post-Installation:
MUST: Trigger Multi-disabler.
In TWRP, go to Advanced > Terminal.
Type multidisabler, then enter. If it fails with something about vendor free space, run it again.
Run multidisabler again.
Go to main screen. go to Wipe > Format Data, type yes then swipe.
Reboot to Recovery. Now you can do other stuff.
Should: Backup all vital partitions:
In TWRP, go to Backup
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)
Download the tar recovery image, then extract it to get recovery.img
Copy it to phone, then reboot to TWRP (Combo is Power + Volume-up)
Go: Install > Install image > select recovery.img file > select Recovery
Swipe to confirm flashing.
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.
GSI and related stuff:
GSI should be directly flashable now. Big credit to @Long266
Install TWRP, do all the instructions.
Download a GSI. Phh's is a good start.
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
If downloaded a compressed file (the extension is not .IMG; e.g: `gsi.img.gz` ), extract it to get an IMG file. Copy the IMG file to your phone.
Reboot into TWRP.
Tap Install > Install Image > Select your GSI .img file.
Select System Image, then flash.
If previously you were on stock, Wipe > Format data.
Reboot System.
Profit.
Source codes:
Kernel: https://github.com/long266/android_kernel_samsung_a32/tree/s
TWRP device: https://github.com/almondnguyen/twrp_device_samsung_a32/tree/twrp-12.1
Credits:
Devs involved in the making and maintaining of TWRP, twrpdtgen, Magisk and base software.
All the Testers.
@Long266 as tester, collab-dev.
@ianmacd for multidisabler.
@afaneh92 for a32x base tree and MTK-Samsung multidisabler.
@dronkit and @Mighty_Rearranger for Magisk-IMEI fix on MTK devices.
@klfld for GSI installation guide.
Older Release(s):
TWRP 3.6.2_12.1-20220703: https://github.com/almondnguyen/twrp_device_samsung_a32/releases/tag/TWRP-3.6.2_12.1-a32-20220703
TWRP 3.6.2_12.1-20220528: https://github.com/almondnguyen/twrp_device_samsung_a32/releases/twrp-3.6.2_12.1/
TWRP 3.6.1_11: https://github.com/almondnguyen/android_OTA/releases/TWRP-3.6.1_11-a32-B20220324
Footer Infos:
Status: Beta
Current Stable Version: 3.7.0_12.1
Created: 2022-03-24
Last Updated: 2022-07-03

chmod 550 /mnt/vendor/nvdata/md/NVRAM/NVD_IMEI must run on OS, not TWRP, since TWRP cannot mount /mnt

I can't install large IMG files to internal memory? For example a gsi?

Melky777 said:
I can't install large IMG files to internal memory? For example a gsi?
Click to expand...
Click to collapse
I should clarify that I don't own the device and all the testing was/is done by @Long266 .
These specific questions should be inquired to him instead (on his thread here: https://forum.xda-developers.com/t/...hawk-recovery-project-3-1-2021-03-24.4420469/ ).
Anyways, the bug that you are mentioning means that you can't flash images FROM internal SD card. GSI and image stuff should be flashable from other places like external SD or cache. Zip files are so far working as intended (as is they are flashable from anywhere).
To be fair, there could be flaws in his testing methodology and you should try it yourself.

Thanks Bro
I will owe the test of the A325M. I have no SD card at the moment.

Build 2022-03-25 changes:
Add backup entry for NVRAM, so in case Magisk messes up you still have a working copy intact.
Fix flashing image causing file size exceeded limit.

Updated TWRP Link, previously pointing to dead end.

It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!

Melky777 said:
It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!
Click to expand...
Click to collapse
can u send recovery.log ?

Melky777 said:
It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!
Click to expand...
Click to collapse
just skip NULL errors

How to update the TWRP version if it is already installed?
Is it enough to just flash the new TWRP version in Odin?
Or do I need to do the same steps as with the first installation (i.e. multidisabler, etc)?

YellowSM said:
How to update the TWRP version if it is already installed?
Is it enough to just flash the new TWRP version in Odin?
Or do I need to do the same steps as with the first installation (i.e. multidisabler, etc)?
Click to expand...
Click to collapse
You can use the "install Image" under TWRP.
From the <!> For more info part, download .img file instead, copy it to your phone. Then go to TWRP > Install > Install Image > select TWRP img > select Recovery to flash.
If you've done, Post-installation steps are unnecessary to do again.
edit: upgrade section added to main post.

How to deactive KC Client and
Knox Enrollment Service?

Hi, I wanted to try a GSI with this, is it safe to try it? Thanks for developing this TWRP, I can help with testing too.

Okay, I tested flashing phh's AOSP GSI, TWRP doesn't have the entry to flash to the dynamic partitions (system, vendor, product, etc). It can flash only to the super partition. Tried to flash the GSI there just in case, but i get a bootloop obviously. Restored successfully through ODIN. I wont test magisk because I don't want to lose IMEI.

klfld said:
Okay, I tested flashing phh's AOSP GSI, TWRP doesn't have the entry to flash to the dynamic partitions (system, vendor, product, etc). It can flash only to the super partition. Tried to flash the GSI there just in case, but i get a bootloop obviously. Restored successfully through ODIN. I wont test magisk because I don't want to lose IMEI.
Click to expand...
Click to collapse
try flashing via fastboot!
I saw a video of a Brazilian doing it on the A22

Long266 said:
can u send recovery.log ?
Click to expand...
Click to collapse
On the same day I removed the twrp and blocked the bootloader.

Melky777 said:
try flashing via fastboot!
I saw a video of a Brazilian doing it on the A22
Click to expand...
Click to collapse
I could install the Lineageos 19.1 GSI! I had to use this zip as a workaround ChonDoe_Flasher.zip, that allows flashing dynamic partitions even if the TWRP doesn't. I also made a treble overlay for this device (vendor.img), that fixes power profiles and all this stuff, ill upload it now if anyone is interested.
To flash the GSI you have to rename the .img file to system.img, put it in the same location than the zip and flash the zip. I have the scripts inside the zip to check if it didnt do anything weird and the source code seems safe, tried two GSIs today.
What doesnt work with the Lineage GSI or phh's AOSP is MTP and the fingerprint reader. Also i can't get encryption to work, the GSI crashes if i don't use multidisabler to remove encryption from the fstab. Everything else works flawlessly from my testing.
For file transfer i'm using ADB with this tool, it's even faster than MTP somehow Python ADB File Explorer
EDIT: Uploaded vendor.img with the overlay for this device, ill push the changes to github later.
Download here: vendor.img

klfld said:
I could install the Lineageos 19.1 GSI! I had to use this zip as a workaround ChonDoe_Flasher.zip, that allows flashing dynamic partitions even if the TWRP doesn't. I also made a treble overlay for this device (vendor.img), that fixes power profiles and all this stuff, ill upload it now if anyone is interested.
What doesnt work with the Lineage GSI or phh's AOSP is MTP and the fingerprint reader. Also i can't get encryption to work, the GSI crashes if i don't use multidisabler to remove encryption from the fstab. Everything else works flawlessly from my testing.
Click to expand...
Click to collapse
Very good job!!!
Makes a topic, I think I'm not the only one who wants to install a GSI.

Develop Bugs

welcome