[EOL][ROM][UNOFFICIAL][12.1] LineageOS 19.1 for Galaxy Note10 5G [d1x][N971N][ENCRYPTION] - Samsung Galaxy Note 10 ROMs, Kernels, Recoveries,

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Known Issues
You tell me
Requirements
Required firmware version is N971NKSU2HVE9.
Instructions
You can follow the instructions on the wiki page for d1: https://wiki.lineageos.org/devices/d1/install
Please remember to upgrade your firmware through Odin. Put the provided file in the BL slot.
Only the provided lineage recovery will be supported, using TWRP might result in a possible data loss!
Note: You may use Odin instead of Heimdall, for this you will need to rename the recovery image to recovery.img and pack it into a tar archive.
Downloads
Builds: https://sourceforge.net/projects/lineageos-samsung-note10-5g/files/lineage-19.1/
GApps: https://wiki.lineageos.org/gapps.html
Firmware: https://sourceforge.net/projects/firmware-samsung-note10-5g/files/
Source
https://github.com/Rocky7842/android_kernel_samsung_exynos9820/tree/lineage-19.1
Contributors
Rocky7842
Linux4 for maintaining the trees for exynos982x devices.
LineageOS team

About Safetynet
The safetynet on this ROM can pass basic integrity, but not CTS.
Due to the official stance of LineageOS team, and spoofing the build fingerprint may causes issues because Android uses build fingerprint changes as a signal to clear and rebuild several caches, I will not put the modifications in the ROM itself. Instant I'll put the information here, you can choose to do it or not.
To pass CTS:
We have to install Magisk(or Lygisk), then install both Universal SafetyNet Fix and MagiskHidePropsConf modules.
Reboot, enter adb shell.
In adb shell, type in "props". Now Magisk should ask you for su, accept it.
Type in "1". Which is edit device fingerprint.
Type in "samsung/d1xks/d1x:12/SP1A.210812.016/N971NKSU2HVE9:user/release-keys".
Type in "y" to confirm.
Type in "n" to avoid reboot now.
Type in "b" to go back to main menu.
Type in "5". Which is add/edit custom props.
Type in "n". Which is new custom prop.
Type in "ro.build.version.security_patch".
Type in "2022-05-01".
Type in "y" to confirm.
Type in "y" to reboot.
Now the security patch date and build fingerprint should be what we set, and Safetynet should pass now.

Working, I can confirm

A working rom for d1x, am I dreaming?

jamesrrred said:
A working rom for d1x, am I dreaming?
Click to expand...
Click to collapse
Give it a try and you'll know if it's a dream or not.

jamesrrred said:
A working rom for d1x, am I dreaming?
Click to expand...
Click to collapse
Thanks to Rocky7842

jamesrrred said:
A working rom for d1x, am I dreaming?
Click to expand...
Click to collapse
Please give some feedback if you already try it.

Rocky7842 said:
Please give some feedback if you already try it.
Click to expand...
Click to collapse

Bro can you give me rooting tools for note 10 N971N? Please or even just the link bro please!

JÅ“508 said:
Bro can you give me rooting tools for note 10 N971N? Please or even just the link bro please!
Click to expand...
Click to collapse
What do you mean...? Just use magisk.

Rocky7842 said:
What do you mean...? Just use magisk.
Click to expand...
Click to collapse
i want to root my samsung note 10 n971n version. Maybe you can help me

I don't know where to download the root files.

Enable Developer Options
Under developer options enable OEM unlock
Download latest firmware for your phone
Go-to https://galaxyfirmware.com/model/SM-N971N/
Download the right file for your device (just choose one)
Download magisk
Once this is downloaded, we can install it.
With that done, extract. The contents of the firmware you downloaded earlier.
Copy the AP file onto your phone.
Now open magisk app and tap on the install button and, make sure that the recovery mode Option stays checked, now tap the next option to bring us to the method which lets us select and patch a file.
Locate that AP file and then load it up into magic before tapping. The, let's go button.
After magisk is done patching the files..
Now you're going to be told that there is an output file, You just need to make sure that we look at where this file is and copy it to your PC.
Put the device into download mode,
Now extract the Odin program and open it
connect phone to PC
disable the auto reboot option under options tab
Locate the firmware that was downloaded and the patched file.
start loading these files into Odin.
click the BL button and load the file that begins with the letters BL.
Remember the same with the CSC and we need to load the CSC file (not the home CSC file).
Now click the AP button right here, but instead of loading, the AP file, instead we're going to load the AP file magisk patched.
there is a progress bar on the phone itself as well on the PC.
So once you get a green pass message
Device is not going to reboot because we need to manually reboot to instantly however.
With Odin finished, unplug USB cable. now, We're going to press the VOLUME DOWN and the SIDE BUTTON till the screen go black, let go of the VOLUME DOWN button while still holding the SIDE BUTTON and press and hold the VOLUME Up button. So you're gonna press these two buttons to force the device to reboot.
After reboot locate and open magisk

VoLTE Supported?

Alexis Levin said:
VoLTE Supported?
Click to expand...
Click to collapse
VoLTE is not supported.

New build uploaded. Security patch date is now 2022-11-05.

I flashed recovery using Odin and can enter Lineage recovery mode successfully.
But when I use adb sideload <ROM.zip>, it cannot detect my devices to sideload the custom ROM.
There's no devices under adb devices either.

ngfuong said:
I flashed recovery using Odin and can enter Lineage recovery mode successfully.
But when I use adb sideload <ROM.zip>, it cannot detect my devices to sideload the custom ROM.
There's no devices under adb devices either.
Click to expand...
Click to collapse
If you sure you have put the phone into sideload mode, check your cable/driver or change a computer.

Rocky7842 said:
If you sure you have put the phone into sideload mode, check your cable/driver or change a computer.
Click to expand...
Click to collapse
Thank you for replying. I changed to Linux and now I can sideload the .zip file.
However, after sideloading using this command:
adb sideload lineage-19.1-20221113-UNOFFICIAL-d1x.zip
The phone returns this:
E: Signature verification failed
E: error: 21
Then I choose Install anyway, and receive:
Installing update...
E: Failed to find update binary META-INF/com/google/android/update-binary
Any idea what I missed?

ngfuong said:
Thank you for replying. I changed to Linux and now I can sideload the .zip file.
However, after sideloading using this command:
adb sideload lineage-19.1-20221113-UNOFFICIAL-d1x.zip
The phone returns this:
E: Signature verification failed
E: error: 21
Then I choose Install anyway, and receive:
Installing update...
E: Failed to find update binary META-INF/com/google/android/update-binary
Any idea what I missed?
Click to expand...
Click to collapse
Please try re-download the file. If it still fails, try install the "20221023" build.
I didn't test the "20221113" version since I'm doing the bring up of A13. There's a possibility that the file was corrupt in the uploading procedure. No one reports that so far, though.

Related

Update to Marshmallow 6.0.1 Step by Step

This is a Step by Step guide to update from Lollipop build N920AUCU2APB2 to Marshmallow build N920AUCU2BPE5
Tools Required
1. ADB, download here, install with arguments Y, N, Y
2a If your current build is N920AUCU2APB2 download this update
2b If your current build is N920AUCS2APE3 download this update
2c. If coming from a different build number see Post #2 to manually ODIN back to PB2 then run the update in step 2a
******************
If you get "Error 403 Forbidden" on any of the downloads use the following work around:
Download the Chrome Extension 'User-Agent Switcher'
Once installed switch to the agent 'Googlebot (Googles Spider)'
Downloads will be working again
After the downloads have started switch the Agent back to 'Default'
******************
Thank you to @bmatney who uploaded the DL to here
MD5: 7941A2C689C5B141675593E3FA33FB9A
was tested on a Windows 10 64 bit machine.
Steps:
1. Backup everything of importance on your phone!!!
2. Now, make sure you have "show file extension" enabled in Windows, and add the .zip extension to SS-G920AUCU3BOJ7-to-U3BOJ9-UP, so it is now called SS-G920AUCU3BOJ7-to-U3BOJ9-UP.zip
3. Shutdown your phone
4. Enter recovery mode by pressing volume up, home and power button together
* A green Droid will appear on screen with the text Installing system update…
5. Using the Volume Button Navigate and the Power button to select ‘Apply Update from ADB’
6. Connect your phone via USB to your computer
7. Open a CMD prompt from your PC. Type cd
in my case: cd C:\Users\Danny\Desktop\Note5
8. Navigate to the directory that contains the update ‘SS-N920AUCU2APB2-to-U2BPE5-UP.zip’
*Note I had issue when the directory contained a space. Moving the update to a directory with no spaces resolved the issue.
Also moved the adb driver to the same directory 'C:\Users\Danny\Desktop\Note5'
9. Type adb devices. You should see 1 device listed
{
"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"
}
10.Type adb sideload SS-N920AUCU2APB2-to-U2BPE5-UP.zip
11. This took around 25 minutes to complete
12. Phone will now be updated Marshmallow
First time creating a How to post. If there is something not correct please let me know!
Thank you to
@sand_bit for his step by step guide in S6 forum here
@bmatney Mega upload
For those of you coming from a different builds here are the other links for updating:
From N920AUCU2APB2 to APE3 https://xdmd.sl.attcompute.com/agents/48725/1488/SS-N920AUCU2APB2-to-U2APE3
meek2100 said:
Here are the other update links people are asking for:
N920 Update File Links
(5.1.1) U2APB2 -> (6.0.1) 2BPE5 Credit to: ColoMtn
https://xdmd.sl.attcompute.com/agents/48725/1488/SS-N920AUCU2APB2-to-U2BPE5-UP
----------------------------------------
(5.1.1) 2AOJ1 -> (5.1.1) U2APB2 Credit to: meek2100
https://xdmd.sl.attcompute.com/agents/48725/1488/SS-N920AUCU2AOJ1-to-U2APB2-UP
----------------------------------------
(5.1.1) 2AOI6 -> (5.1.1) U2APB2 Credit to: meek2100
https://xdmd.sl.attcompute.com/agents/48725/1488/SS-N920AUCU2AOI6-to-U2APB2-UP
-----------------------------------------
(5.1.1) U2APB2 ODIN files for clean flash or restoring to STOCK can be found here. Credit to: Sunderwear
http://forum.xda-developers.com/att-galaxy-note5/general/note-5-marshmallow-odin-package-t3331843
------------------------------------------------------------------------------
Click to expand...
Click to collapse
ColoMtn said:
Tools Required
1. ADB, download here, install with arguments Y, N, Y
2. Odin, get a clean version from Sammobile here
3. Ensure your Note 5 is running Build: N920AUCU2APB2 this is the latest OTA available as of (5/16/16)
4. Download this to update from Lollipop PB2 ->PE5
Thank you to @bmatney who uploaded the DL to here
was tested on a Windows 10 64 bit machine.
Steps:
1. Backup everything of importance on your phone!!!
2. Now, make sure you have "show file extension" enabled in Windows, and add the .zip extension to SS-G920AUCU3BOJ7-to-U3BOJ9-UP, so it is now called SS-G920AUCU3BOJ7-to-U3BOJ9-UP.zip
3. Shutdown your phone
4. Shutdown your phone, and enter recovery mode by pressing volume up, home and power button together
* A green Droid will appear on screen with the text Installing system update…
5. Using the Volume Button Navigate and the Power button to select ‘Apply Update from ADB’
6. Connect your phone via USB to your computer
7. Open a CMD prompt from your PC. Type cd <Your Directory>
in my case: cd C:\Users\Danny\Desktop\Note5
8. Navigate to the directory that contains the update ‘SS-N920AUCU2APB2-to-U2BPE5-UP.zip’
*Note I had issue when the directory contained a space. Moving the update to a directory with no spaces resolved the issue.
Also moved the adb driver to the same directory 'C:\Users\Danny\Desktop\Note5'
9. Type adb devices. You should see 1 device listed
10.Type adb sideload SS-N920AUCU2APB2-to-U2BPE5-UP.zip
11. This took around 25 minutes to complete
12. Phone will now be updated Marshmallow
First time creating a How to post. If there is something not correct please let me know!
Thank you to 
 @sand_bit for his step by step guide in S6 forum here
 @bmatney Mega upload
Click to expand...
Click to collapse
I'm getting "cannot read 'marshmallow.zip' " error
i keep getting dm-verity verification failed update from adb is disabled
creedicd said:
I'm getting "cannot read 'marshmallow.zip' " error
Click to expand...
Click to collapse
Did you make sure the directory had no Spaces and also move the ADB drivers to the same directory?
There are also users reporting that renaming the file 'marshmallow.zip.zip' fixes the issue.
im new to adb. i have no idea lol
blane3298 said:
i keep getting dm-verity verification failed update from adb is disabled
Click to expand...
Click to collapse
A quick google search says you may need to re-download the update
Odin?
ColoMtn said:
Tools Required
1. ADB, download here, install with arguments Y, N, Y
2. Odin, get a clean version from Sammobile here
3. Ensure your Note 5 is running Build: N920AUCU2APB2 this is the latest OTA available as of (5/16/16)
4. Download this to update from Lollipop PB2 ->PE5
Thank you to @bmatney who uploaded the DL to here
was tested on a Windows 10 64 bit machine.
Steps:
1. Backup everything of importance on your phone!!!
2. Now, make sure you have "show file extension" enabled in Windows, and add the .zip extension to SS-G920AUCU3BOJ7-to-U3BOJ9-UP, so it is now called SS-G920AUCU3BOJ7-to-U3BOJ9-UP.zip
3. Shutdown your phone
4. Shutdown your phone, and enter recovery mode by pressing volume up, home and power button together
* A green Droid will appear on screen with the text Installing system update…
5. Using the Volume Button Navigate and the Power button to select ‘Apply Update from ADB’
6. Connect your phone via USB to your computer
7. Open a CMD prompt from your PC. Type cd <Your Directory>
in my case: cd C:\Users\Danny\Desktop\Note5
8. Navigate to the directory that contains the update ‘SS-N920AUCU2APB2-to-U2BPE5-UP.zip’
*Note I had issue when the directory contained a space. Moving the update to a directory with no spaces resolved the issue.
Also moved the adb driver to the same directory 'C:\Users\Danny\Desktop\Note5'
9. Type adb devices. You should see 1 device listed
10.Type adb sideload SS-N920AUCU2APB2-to-U2BPE5-UP.zip
11. This took around 25 minutes to complete
12. Phone will now be updated Marshmallow
First time creating a How to post. If there is something not correct please let me know!
Thank you to
@sand_bit for his step by step guide in S6 forum here
@bmatney Mega upload
Click to expand...
Click to collapse
Thanks man - awesome stuff. Why Odin download? Needed at this stage? Or just ADB sideload?
tr8ze said:
Thanks man - awesome stuff. Why Odin download? Needed at this stage? Or just ADB sideload?
Click to expand...
Click to collapse
Just ADB sideload. Will update. Thanks!
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
Will these steps work on an encrypted phone?
darktrancer said:
Will these steps work on an encrypted phone?
Click to expand...
Click to collapse
Not sure.
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
I am on OJ1, do you think it will work? or is there any way to update from OJ1 to PB2, since I am not on the US and cant get OTA updates, thank you very much
any way this could be made into a odin flashable file?
mcepedaj said:
I am on OJ1, do you think it will work? or is there any way to update from OJ1 to PB2, since I am not on the US and cant get OTA updates, thank you very much
Click to expand...
Click to collapse
Try to update the url with in the original thread to reflect OJ1 and PB2 build numbers (can't look up the full build numbers right now). If that works use this same guide to apply the update.
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
blane3298 said:
any way this could be made into a odin flashable file?
Click to expand...
Click to collapse
I don't know how to do that but side loading was fairly simple.
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
so i can get up to the point of doing the "adb sideloade" command but i get the cannot read error. where can i locate the adb drivers? im new to adb and sideloading. thanks for the write up though.
bdevillier19 said:
so i can get up to the point of doing the "adb sideloade" command but i get the cannot read error. where can i locate the adb drivers? im new to adb and sideloading. thanks for the write up though.
Click to expand...
Click to collapse
Step 1
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
ColoMtn said:
Step 1
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
Click to expand...
Click to collapse
step 1 of the tools required section? i've done that numerous times. it says the driver is installed but doesnt give me any info as to where the drive is at. thanks for the reply
I'm trying to download the update from the Mega link provided earlier. It is taking SO LONG.
I'm getting impatient.
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
Working on getting apps reinstalled... AT&T loaded more **** on this firmware than they ever have before. Ridiculous.

[GUIDE][BR][LP]Complete guide for unlock bootloader and flash TWRP in H442F DUAL SIM

Hello folks!
It's been a while since last time I spent in this forum section (when the method for flashing Poland MM KDZ was published), but suddenly I decided to check the current development and it was great do discover that developers found a way to unlock bootloader! Then, I tried to do the procedures, found some adversities around the path, flashed stock KDZ for my device A LOT and finally managed to obtain a fully working LP stock with root and TWRP for my model: H442F (Dual SIM) ("LG Volt 4G" in Brazil).
The thing is: although a lot was done regarding the Spirit LTE, I found near zero information specifically for my device variant. Since I tried a lot of paths and eventually achieved an interesting result, I decided to write a full tutorial, with a lot of instructions and pictures for "novices" who desire learn all the steps but gives up at the high learning curve. Finally, I also wrote this tutorial in Brazilian Portuguese, which I believe will help at least some comrades (you can download the PDF in portuguese HERE).
Needed files:
LG Drivers (remove old ones if already instaled)
LG Flash Tool 2014 (credits to @quangnhut123 from this thread)
Brazilian H442F10a Firmware (this is a low speed server, I can upload to a better one if someone asks)
Android SDK Tools (for Windows users; Linux ones just install the package android-tools-adb)
Kingroot (or download here: www.kingroot.net)
Latin America Patched Aboot (credits to @pvineeth97 , for more info check this thread)
TWRP (or download here: https://twrp.me/lg/lgspiritlte.html)
Flashfy (or download here: https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en)
SuperSU (or download here: http://www.supersu.com/)
Finally, if you prefer, you can download a full pack in this link (except for KDZ), however, I did prefer to keep isolated links for better credits and referrals
Step-by-step
Download all needed files
Install drivers, SDK and unpack Flash Tool
Save all files in the same folder, but keep KDZ file inside Flash Tool folder
Put your phone in download mode (power off, hold vol+, plug usb in pc, keep holding until download icon appears)
Wait a little for Windows completely detects device and load all drivers
Verify in Device Manager if your pc detects phone as "LG Mobile USB Serial Port (COM#)"
{
"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"
}
Open LG Flash Tool as admin
Select KDZ file
Choose the downloaded H442F10a_03.kdz file
Choose CSE Flash
Click START
Then, "Clear phone software update registry"
You'll see a warning
Then, OK (no need to change country)
Another app will open for the flashing. If you are offline, it is possible to show just a "?" character. Wait patiently...
In about 5min it will finish
After some reboots, you'll see the phone starter screen. Just move forward (no need to configure anything right now, maybe wifi, but not google account)
Enable Developer Options going to Settings/General/Common/Software Information and tap some simes in Build Number until the "You are a developer" message appears
Go back to Settings/Developer Options and turn on USB Debugging
With Debugging on, choose MTP (for Windows) or PTP (Linux), and when asked, allow the computer
Now, make sure you installed (and know how to use, since I will cover just a few commands here) the Android Debugging Bridge (adb). It will be essential for some steps, as well for entering Recovery Mode (I will show some Linux screenshots because I do not use Windows - for this tutorial, just for KDZ flash - but with a working adb the commands are the same)
Open a command prompt (Windows: right click in start menu) or a terminal (Linux) and run "adb devices" to see if the device was detected. If not, run again and check if phone are asking permissions (and grant it)
Go (cd) to the folder with all downloaded files and write the commands (some names may be different if you downloaded individual files from official links)
adb push aboot_5120_patched.bin /sdcard/
adb push twrp-3.2.1.0-cn70n.img /sdcard/
adb push SuperSU-v2.82-201705271722.zip /sdcard/
adb install Flashify_1.9.2.apk
adb install KingrootV5.3.1.apk
At whit point, make sure your internet is fully working (3-4G or WIfi), then, open Kingroot and root the device
After a well successful root, go back to adb and run "adb shell" and then "su". The phone will ask root permission. Grant it and in adb again run "cd /sdcard"
Now we arrived a critical step. Make sure to type the command as is show, because an error may result brick. We will copy the modified aboot into the respective phone partition (check code, check picture, and double check!)
If everything occurs all right, will appear this message
Great! Now you have an unlocked bootloader! What we have to do now is fhash a custom recovery (in this case, TWRP).
Open Flashify, give root rights, then go into Flash/Recovery Image/Choose a file/File explorer/sdcard/[downloaded file]. When asked to flash click "YUP!" and then "Flash More" (as we do not want the phone to reboot right now)
An extra step I prefer to do is remove Kingroot, since it installs a lot of services and keep device substantially slow. If you prefer Kingroot over SuperSU, you are DONE!
Case you prefer SuperSU... Open Kingroot/.../Settings/Uninstall Kingroot
It will prompt if you are sure. Just click Continue/OK
Go back to prompt/terminal and run "adb reboot recovery"
Phone will enter TWRP!
Now, just a few steps!
Go to Install and flash SuperSU
Go to Wipe and do a Factory Reset
Go to Settings and disable TWRP app installer (optional)
And finally go to Reboot and choose System
DONE!!!
Now you have a phone with an unlocked bootloader, a recovery capable of doing a lot of stuff (sideload, wipe cache, backups), and rooted as well.
A really good job, I'm sure a lot of your fellow countryman will find this very useful!
Korelev said:
A really good job, I'm sure a lot of your fellow countryman will find this very useful!
Click to expand...
Click to collapse
Thanks man! Today I finally added a link with portuguese-br instructions. Hope more Brazilian users will have the chance to perform these operations!
Valeeeu dms irmao, ajudou dmss
Ninloth said:
Thanks man! Today I finally added a link with portuguese-br instructions. Hope more Brazilian users will have the chance to perform these operations!
Click to expand...
Click to collapse
Thanks for the instructions. After unlocking its bootloader, wil it be compatible with any H440 custom rom (single sim operation, of course)? Or the only custom rom we get is Cm12?
Mrkblo said:
Thanks for the instructions. After unlocking its bootloader, wil it be compatible with any H440 custom rom (single sim operation, of course)? Or the only custom rom we get is Cm12?
Click to expand...
Click to collapse
Hi!
Well, unfortunately I don't know. I made the procedure, wrote the tutorial, and 2 months later changed my phone for a new one. Can't test anymore.
Mrkblo said:
Thanks for the instructions. After unlocking its bootloader, wil it be compatible with any H440 custom rom (single sim operation, of course)? Or the only custom rom we get is Cm12?
Click to expand...
Click to collapse
Yes, it should be compatible with any custom rom as long as your phone is Lg spirit LTE( snapdragon variant ).

Sideload Addison Oreo 8.0 Update noob thread

This is a tutorial for noobs. It is meant to provide information that you may or may not need, nonetheless it should get you from stock 7.1.1 to 8.0 Oreo regardless of your geographic location.
I am not responsible if you mess up your phone, however this is pretty safe since it has checks in place and will simply fail if you don't have the proper version of 7.1.1 on your phone.
METHOD 1 confirmed by @alypotter1 and @kingstu
A simplified way of updating using your device only. Untested by me but confirmed to be working.
Download
Move this zip file to the root directory of your internal storage
Go to Settings>Apps and Notifications>App permissions>Storage. In the top corner select the dots and activate 'Show system'. Find 'Motorola Update Services' and activate it
Reboot your device
The update should be detected by Update services automatically
METHOD 2
Prerequisites:
Your phone is up to date (Feb security patch-NPNS26.118-22-2-17)
Motorola Drivers - This is kinda a pain to find, most links take you to an old version not compatible with Windows 10
Moto Z Play Oreo update
ADB turned on-Developer options (Activate under About Phone>Build number hit repeatedly)-USB Debugging
Procedure:
1. Download the files, ADB is already included with the update file
2. Make sure you have Motorola drivers installed and ADB enabled
3. Unzip the files and open a command prompt in windows
4. In cmd, browse to the folder containing the files using cd (File location)-switch drives if you need to using D:, C:, etc
Your Phone:
1. Turn it off
2. Hold the power button and volume down until it starts in AP Fastboot mode
3. Hit Vol down until you see Recovery Mode
4. Hit Power button to enter it-You should see an Android on his back and 'No command'
5. Hit Power and Vol up at the same time to enter download mode - This may take a few tries, removing your case may make this easier
6. Press Vol down to get to 'Apply update from ADB' and hit the power button
7. Now you're ready to connect to your PC
Back to the PC:
1. Once connected windows should detect it and install the correct drivers (You should hear the windows 'new device' notification)
2. Type adb devices in the command window
You should see something like:
Code:
List of devices attached
ZY123SZC57D sideload
If not, you need to diagnose why windows is not detecting the device
3. Now type adb sideload update.zip
The phone will display progress updates as the update sideloads. This can take approx. 30 minutes (some have reported it taking up to an hour!). Resist the urge to assume it has hung at any point, walk away if you have to.
If I missed anything please let me know.
Alternate Google drive link-Use only if Mega is not working
Special thanks @talktosam for uploading the original update files
How to root 8.0.0
Details:
Code:
Version 8.0.0
Software Channel: Remains unchanged
Security patch: April 1st
Baseband: M8953_10238.63.04.83R ADDISON_ROW_CUST
Kernel: 3.18.71-perf-g174984b
Build: OPN27.76-12-22
scottdanpor said:
This is a tutorial for noobs. It is meant to provide information that you may or may not need, nonetheless it should get you from stock 7.1.1 to 8.0 Oreo regardless of your geographic location.
Prerequisites:
Motorola Drivers - This is kinda a pain to find, most links take you to an old version not compatible with Windows 10
Moto Z Play Oreo update
ADB turned on-Developer options (Activate under About Phone>Build number hit repeatedly)-USB Debugging
Procedure:
1. Download the files, ADB is already included with the update file
2. Make sure you have Motorola drivers installed and ADB enabled
3. Unzip the files and open a command prompt in windows
4. In cmd, browse to the folder containing the files using cd (File location)-switch drives if you need to using D:, C:, etc
Your Phone:
1. Turn it off
2. Hold the power button and volume down until it starts in AP Fastboot mode
3. Hit Vol down until you see Recovery Mode
4. Hit Power button to enter it-You should see an Android on his back and 'No command'
5. Hit Power and Vol up at the same time to enter download mode - This may take a few tries, removing your case may make this easier
6. Press Vol down to get to 'Apply update from ADB' and hit the power button
7. Now your ready to connect to your PC
Back to the PC:
1. Once connected windows should detect it and install the correct drivers (You should hear the windows 'new device' notification
2. Type 'adb devices' in the command window (without quotes)
You should see something like: List of devices attached
ZY123SZC57D sideload
If not, you need to diagnose why windows is not detecting the device
3. Now type 'adb sideload update.zip'
The phone will display progress updates as the update sideloads
If I missed anything please let me know.
Alternate Google drive link-Use only if Mega is not working
Special thanks @talktosam for uploading the original update files
Click to expand...
Click to collapse
welcome, may be this is our last soak test for z play... see u guys any custom rom threads..
talktosam said:
welcome, may be this is our last soak test for z play... see u guys any custom rom threads..
Click to expand...
Click to collapse
Yes this should be the last major update for Moto Z Play. Anybody looking for 8.1+ will need a custom rom.
So this update, which appeared today on retin, could be safely installed on reteu?
yaatzek said:
So this update, which appeared today on retin, could be safely installed on reteu?
Click to expand...
Click to collapse
Yes the update is the same, we just have to wait for it to be distributed to our devices. I'm on tkpca and it has not released yet on that channel.
After the update you will have version 8.0.0, and will still be on software channel reteu in your case. Security patch is April 1st.
scottdanpor said:
Yes the update is the same, we just have to wait for it to be distributed to our devices. I'm on tkpca and it has not released yet on that channel.
After the update you will have version 8.0.0, and will still be on software channel reteu in your case. Security patch is April 1st.
Click to expand...
Click to collapse
any software channel can update this ota safely... no matter retin, reteu, br etc
Hi all,
It worked for me!
Thanks to @scottdanpor for this post!
{
"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"
}
I'm on 7.1.1 June 1, 2017 security patch (NPN26.107). Wondering if this OTA will work for me.
boonhoong said:
I'm on 7.1.1 June 1, 2017 security patch (NPN26.107). Wondering if this OTA will work for me.
Click to expand...
Click to collapse
Give it a try, it will either install or fail to install without making any changes.
boonhoong said:
I'm on 7.1.1 June 1, 2017 security patch (NPN26.107). Wondering if this OTA will work for me.
Click to expand...
Click to collapse
Flashing this official Oreo OTA will likely fail, as your device does not have the correct build. You need a clean, fully stock firmware with either the Feb 2018 7.1.1 security patch (build NPNS26.118-22-2-17) or the Oreo last soak test patch (OPN27.76-12-22) to flash this:
Package expects build thumbprint of 8.0.0/OPN27.76-12-22/24:user/release-keys or 7.1.1/NPNS26.118-22-2-17/21:user/release-keys
Is there a guide on what to do with unlocked boothloaders? I'm on Oreo SOAK 2 (or maybe 3) with TWRP. How can I fully unroot, replace bootlader/recovery, and lock the device? There used to be a guide for Nougat, but since I updated to SOAK, I haven't been able to go back to stock.
goncalesi said:
Hi all,
It worked for me!
Thanks to @scottdanpor for this post!
Click to expand...
Click to collapse
what compile number did you have before installing this update?
fuelvolts said:
Is there a guide on what to do with unlocked boothloaders? I'm on Oreo SOAK 2 (or maybe 3) with TWRP. How can I fully unroot, replace bootlader/recovery, and lock the device? There used to be a guide for Nougat, but since I updated to SOAK, I haven't been able to go back to stock.
Click to expand...
Click to collapse
You need to unroot and restore stock recovery and move forward. Your best bet might be to just wait for 8.0 complete flash firmware. That's why I stayed away from the soak installs, can be a real hassle.
_heberlopez95 said:
what compile number did you have before installing this update?
Click to expand...
Click to collapse
I was with the feb/2018 security patch before the update
Hi guys! How long does the update takes?
Mine is at 58% (patching system image after verification on phone) for a long, long time.
Just asking, because I'm pretty sure it's not stuck.
Do you know if this will work on Verizon variant? (Moto Z Play Droid XT1635-01)
marcuspereira said:
Hi guys! How long does the update takes?
Mine is at 58% (patching system image after verification on phone) for a long, long time.
Just asking, because I'm pretty sure it's not stuck.
Click to expand...
Click to collapse
It takes quite a while, and it does hang for a while on 58%, just walk away for a bit.
rusa-raus said:
Do you know if this will work on Verizon variant? (Moto Z Play Droid XT1635-01)
Click to expand...
Click to collapse
My guess would be no. Verizon likes to do things differently.
I'm stuck at 77% for 10 minutes now :/
yaatzek said:
I'm stuck at 77% for 10 minutes now :/
Click to expand...
Click to collapse
Don't touch it.

How To Guide Simple Guide How To Root

Alright so a lot of people seem to have issues with rooting their device and creating a lot of spam on this forum because they don't know how to read.
This guide is for Windows PCs and will be for the people who don't want to read complicated guides.
What you Need:
A Device that has an unlocked Bootloader
The Factory Image of the ROM you are using or updating to Download Here
The Latest STABLE Magisk Download Here, if you are opting for a Beta/Canary then have fun.
7-zip or similar file extractor
ADB and Fastboot, I use Minimal ADB and Fastboot but this Script Here will download the latest version and add it to your PATH.
Way to Transfer Files to Phone (USB Cable?)
Steps:
Update to the Latest ROM. This can be done via Sideloading (personal preference) or OTA
Confirm you are on the same version as the factory image. Current is SP2A.220305.013 aka March 2022 Update
Extract the Zip File to a Folder. Current filename is raven-sp2a.220305.013.a3-factory-87b3bf0a.zip
Go in to the folder and extract the Image ZIP into a Folder. Current Name is image-raven-sp21.220305.003.zip
Find the Boot.img and transfer it to your device.
Install the Magisk Manager APK on the Device
Open Magisk and press Install.
Select "Select and Patch a File" and select the Boot.img you transferred to your device.
Magisk will patch the file and place the new .img file in your downloads. The filename will look like "magisk_patched-24300_abcde.img".
Transfer the patched file from your Downloads folder to your PC.
Reboot your phone to Fastboot mode Youtube Tutorial
Locate the patched .img file and press SHIFT+RightClick, click the option "Copy as Path"
On your PC open Command Prompt. If you dont know how to do this, you shouldn't be rooting your device.
In command prompt type "fastboot flash boot" and then paste the location of your patched .img file.
The whole command should look like "fastboot flash boot "C:\Users\Admin\Downloads\magisk_patched-24300_abcde.img"
Reboot the phone with the command "fastboot reboot"
Once the device is booted up, go to Magisk and see if you are rooted.
If there is enough demand, I can provide photos to help.
If I messed up along the way, let me know and I can change the guide.
Saved
{
"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"
}
I can't find my Downlaods folder. Idk what that is.
Gytole said:
View attachment 5574243
I can't find my Downlaods folder. Idk what that is.
Click to expand...
Click to collapse
Fixed lol
vassosman said:
Alright so a lot of people seem to have issues with rooting their device and creating a lot of spam on this forum because they don't know how to read.
This guide is for Windows PCs and will be for the people who don't want to read complicated guides.
What you Need:
A Device that has an unlocked Bootloader
The Factory Image of the ROM you are using or updating to Download Here
The Latest STABLE Magisk Download Here, if you are opting for a Beta/Canary then have fun.
7-zip or similar file extractor
ADB and Fastboot, I use Minimal ADB and Fastboot but this Script Here will download the latest version and add it to your PATH.
Way to Transfer Files to Phone (USB Cable?)
Steps:
Update to the Latest ROM. This can be done via Sideloading (personal preference) or OTA
Confirm you are on the same version as the factory image. Current is SP2A.220305.013 aka March 2022 Update
Extract the Zip File to a Folder. Current filename is raven-sp2a.220305.013.a3-factory-87b3bf0a.zip
Go in to the folder and extract the Image ZIP into a Folder. Current Name is image-raven-sp21.220305.003.zip
Find the Boot.img and transfer it to your device.
Install the Magisk Manager APK on the Device
Open Magisk and press Install.
Select "Select and Patch a File" and select the Boot.img you transferred to your device.
Magisk will patch the file and place the new .img file in your downloads. The filename will look like "magisk_patched-24300_abcde.img".
Transfer the patched file from your Downloads folder to your PC.
Reboot your phone to Fastboot mode Youtube Tutorial
Locate the patched .img file and press SHIFT+RightClick, click the option "Copy as Path"
On your PC open Command Prompt. If you dont know how to do this, you shouldn't be rooting your device.
In command prompt type "fastboot flash boot" and then paste the location of your patched .img file.
The whole command should look like "fastboot flash boot "C:\Users\Admin\Downloads\magisk_patched-24300_abcde.img"
Reboot the phone with the command "adb reboot"
Once the device is booted up, go to Magisk and see if you are rooted.
If there is enough demand, I can provide photos to help.
If I messed up along the way, let me know and I can change the guide.
Click to expand...
Click to collapse
It should be fastboot reboot
fil3s said:
It should be fastboot reboot
Click to expand...
Click to collapse
Good call, I was writing this on the fly and wasn't actually doing it as I was writing the guide.
fil3s said:
It should be fastboot reboot
Click to expand...
Click to collapse
Rather than saying they don't know how to read", it might be that they don't understand the "meta-language" of any given discussion or explanation!
EdBurger l said:
Rather than saying they don't know how to read", it might be that they don't understand the "meta-language" of any given discussion or explanation!
Click to expand...
Click to collapse
Goodo bruh.
vassosman said:
Saved
Click to expand...
Click to collapse
Do you really think this guide is too hard to follow? It's thoughtful that you typed out the steps but is it really less confusing or difficult?
[GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️ WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com
Is the whole vbmeta / boot verification thing no longer necessary?
I tuned out from all the root stuff because I only unlocked in the beginning and didn't want to wipe.
.
dmarden said:
Is the whole vbmeta / boot verification thing no longer necessary?
I tuned out from all the root stuff because I only unlocked in the beginning and didn't want to wipe.
Click to expand...
Click to collapse
They are not required to change if you plan on running Magisk 24.3. I did not change anything when I updated my P6P (bought in Feb) and rooted it.
dmarden said:
Is the whole vbmeta / boot verification thing no longer necessary?
I tuned out from all the root stuff because I only unlocked in the beginning and didn't want to wipe.
Click to expand...
Click to collapse
not needed anymore with latest magisk
That's great news, I've been missing it.
I am going to do this on S3B1.220218.006 (QPR3 Beta 1.1). Fingers crossed!
Worked perfectly, the only thing I might add is a link to the Google USB Drivers (since they must've updated). I had them installed originally (to have unlocked my device in the first place) but needed to update them.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Thanks a ton! I would've never noticed that the wipe step was no longer needed.
I recognize I am replying a lot, haha... sorry about that.
Presumably the update method for this should work exactly like past Pixel devices, yeah?
For me, this method was as follows:
1. Download the full image and edit the script to remove the "-w"
2. Install the modified image
3. Boot up once
4. Then basically follow the original procedure from this thread again
I know on OnePlus devices I was always able to uninstall Magisk root via the Magisk app, take the OTA, then reinstall Magist root via the Magisk app before rebooting, but that never seemed to work on Pixel devices (at least for me).
Just to share...
I decided to give the Magisk restore images, OTA, install again before reboot method a try and it worked perfectly going from QPR 1.1 to 2.
Thank you for this post. I would like to root my phone. I am a noob and it’s a little intimidating. If you would add pictures, I for one, would really appreciate that. Thanks again!

How To Guide Ultra - Fast and Stable ROG PHONE 6 PRO ROOT GUIDE !!!!!!!!!!!!!!!!!!!! (Updated)

So, i was the first to provide the update for this beauty. 6 and 6 pro.
This file will allow you to have ROOT on yout device, extracted with some tools, Terminal/adb typing, etc.
JUST TWO STEPS!
Step 1: Flash the Magisk package on Terminal, CMD or whatever (fastboot flash boot.img) www.mediafire.com/u6weyjcf7edg/igjva0go25fgtcy/magisk_patched-25200_8b9nH.img
Step 2: Download Magisk.apk and that's all!!!!!!
-----
&&&&&&&&&&
Workaround:
- computer doesnt detect phone:
Install this and double click! https://forum.xda-developers.com/t/tool-windows-adb-fastboot-august-2022.3944288/
-¿hou can Y Flass Both.IMGG?
- https://forum.xda-developers.com/t/tutorial-how-to-flash-a-new-boot-img-via-fastboot.1752270/
- I brake my phony please jelp:
Flash RAW or, Flash EDL.
- How do I preseve root with OTA UPDATE?
[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com
3. Tap "Download and install" or local update if OTA from ASUS WEBSITE
4. Wait until you are prompted to reboot - DO NOT REBOOT NOW!
5. Open Magisk Application
a. Select the Install option.
b. Use Install to inactive slot
{
"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"
}
Step 2 - Reboot and enjoy your device still rooted with latest OTA installed !​
Thank you for this guide!
Is there a way to go from CN to WW without root?
insideoft said:
Thank you for this guide!
Is there a way to go from CN to WW without root?
Click to expand...
Click to collapse
You don't need root. You can just flash the RAW file. But you MIGHT not be able to update it because updater won't recognize WW update zip file if you don't change that COUNTRY file.
Hello. Is there a link for the OPEN BL?
i searched google but cant find any links for it from the asus side.
i dont really want to install the ones belonging to the older generation of the ROG Phone.
Thanks
BaronBeef said:
Hello. Is there a link for the OPEN BL?
i searched google but cant find any links for it from the asus side.
i dont really want to install the ones belonging to the older generation of the ROG Phone.
Thanks
Click to expand...
Click to collapse
Yes! I don't know if they really work from you, maybe gets you error. But those are in Asus Website as well.
insideoft said:
Thank you for this guide!
Is there a way to go from CN to WW without root?
Click to expand...
Click to collapse
No, you need BL unlock to flash things.
And... "Root is temporary, rom is forever"
So, you can stay without root NOT FOLLOWING the latest'step.
Moderator Information
Dear all,
Two points on the current discussion: 1. give proper credit and 2. follow XDA rules on sharing other's works.
A refresher:
XDA-Developers FORUM RULES
BaronBeef said:
Hello. Is there a link for the OPEN BL?
i searched google but cant find any links for it from the asus side.
i dont really want to install the ones belonging to the older generation of the ROG Phone.
Thanks
Click to expand...
Click to collapse
insideoft said:
Thank you for this guide!
Is there a way to go from CN to WW without root?
Click to expand...
Click to collapse
YOU MAY NOT UNLOCK YOUR BL AFTER YOU UNLOCKED IT ONCE AND RELOCK IT! NOT VERIFIED ON ROG 6 SO PROCEED WITH CAUTION.
The link in step one doesn't work.
williamcll said:
The link in step one doesn't work.
Click to expand...
Click to collapse
FXD!
How to unroot after rooting? Do i need to extract the current boot.img & re flash it to unroot it?
Therazorsedge said:
Hi, I see a lot of threads, so, I open my own.
This is a tutorial of how you can have root permanently AND updates (root+updates) on this beauty.
And also, you can switch to CN (more battery, but less features -> themes, stuff) or WW ROM.
First of all, there's this files you should download on your computer or your beauty:
(A) Log by Google: MOD EDIT: LINK REMOVED, please provide proper credits when sharing others' work
(B) Download OPEN BL from Asus website, the APK to open it.
(C) Root the Asus (Fastboot flash boot on CMD) with a GOOD CABLE (**** cables doesn't work, sorry.) AND with the LATERAL PORT. You need PLATFORM TOOLS AND/OR MINIMAL ADB (GOOGLE IT AS EVERYTHING...) TO RUN...
(D) "Buy" the root explorer APK on play store, don't think for a minute you can find that on Google, or you can find it, I don't know
(E) Install Magisk APK check everything works as ROOT ENVIROMENT SUCCESFULLY INSTALLED.
(F) On ROOT EXPLORER APK press on the ‘ROOT‘ tab to access the root storage of your phone. Navigate to the ‘/Vendor/Factory‘ folder and find the file with the name ‘COUNTRY‘. Tap on the file and open it with the ‘Text Editor‘. put there CN if you want China (capital letters) or, WW if you want global, reset phone.
(G) Go to the big 4GB file you first downloaded and search the FLASH ALL AFT bat, (extract it first); then, put the phone to BL with power+vol. UP until you see in GREEN Start. Put cable on side port, and double click on FLASH ALL. Voila! You have your phone converter and -it can eat updates.
(H) To update it search for updates on Asus; rog 6 firmware on Google.
Troubleshooting
If your phone isn't detected use another cable go to device manager and check for ASUS ADB INTERFACE TO SHOW if not, change cable and/or download ADB drivers on XDA the .exe file.
The magisk image is to root the phone Fastboot flash boot .IMG (put it on CMD window)
Bonus:
To remove HARDWARESTUB download Notifications off root on play store and install it.
(10) The last step of this very good and awesome tutorial; to keep root after update; download the file, put on root directory; let it update DONT DONT DONT reboot; go to Magisk,
a. Select the Install option.
b. Use Install to inactive slot
Reboot, done.
I'm not asking for donation but; you can "donate" me more "Freely" through subscribing to my YT channel if you really want is the same and it's indeed, Free. https://youtube.com/channel/UCRFpKkKvIOrkFY5eDUG_VBg
Click to expand...
Click to collapse
Thank you for the instructions.
My phone's product code has been changed to "WW_AI2201" and could be updated the firmware from ASUS site once. However, after update the product code returned "CN_AI2201". Could you please help me to keep it "WW"?
And also please tell how to change the fingerprint from "CN" to "WW", if you know.
finallau said:
How to unroot after rooting? Do i need to extract the current boot.img & re flash it to unroot it?
Click to expand...
Click to collapse
To unroot you can just go into magisk and click uninstall, but then you probably also want to relock your bootloader MAKE SURE YOU FACTORY RESET AND HAVE STOCK ROM BEFORE YOU RELOCK YOUR BOOTLOADER!!!
Code:
fastboot oem lock
#OR
fastboot flashing lock
Then you probably also want to go to settings -> developer mode afterwards and disable -> 'OEM Unlocking'
I can't get root explorer to mount R/W on root to get COUNTRY file changed from CN to WW..
Though I could save the file but device info HW shows my fingerprint is still CN..
unable to perform manual update as fingerprint is still CN..
Had my root checker checked, running latest magisk as well..
Tried multiple root explorer versions & other file manager with root access..
Some file manager showed "file is read-only"
anybody having the same issue? any solution?
PiPpikachu said:
Thank you for the instructions.
My phone's product code has been changed to "WW_AI2201" and could be updated the firmware from ASUS site once. However, after update the product code returned "CN_AI2201". Could you please help me to keep it "WW"?
And also please tell how to change the fingerprint from "CN" to "WW", if you know.
Click to expand...
Click to collapse
I'm having the same issue too.. looks like it wasn't R/W but R/O only in root explorer hence it's the cause you won't permanently change the COUNTRY file..
Did a fingerprint check using device info HW app still shows my fingerprint as CN...
hi how i can look boot
nadeer88 said:
hi how i can look boot
Click to expand...
Click to collapse
fastboot oem lock
Or
fastboot flashing lock
AzimBahar said:
fastboot oem lock
Or
fastboot flashing lock
Click to expand...
Click to collapse
I have tried but it always doesn't go through..
I use:
adb devices and it I can see it reads my phone.. but when I type adb reboot bootloader, it doesn't continue after this for me to be able to use the commands that you gave.
Is there any way that I am doing wrong? Kindly help me lock my phone again.
Thank you!
PiPpikachu said:
Thank you for the instructions.
My phone's product code has been changed to "WW_AI2201" and could be updated the firmware from ASUS site once. However, after update the product code returned "CN_AI2201". Could you please help me to keep it "WW"?
And also please tell how to change the fingerprint from "CN" to "WW", if you know.
Click to expand...
Click to collapse
Same as me! Just update zip once, then 2n update will be fail, but i saw the country file show WW in root explorer .....any method can flash zip directly?
iMoc said:
You don't need root. You can just flash the RAW file. But you MIGHT not be able to update it because updater won't recognize WW update zip file if you don't change that COUNTRY file.
Click to expand...
Click to collapse
I bought the version with 12GB Ram and 128GB SSD, and I think that's what happens to mine, because I can´t update it OTG, what steps should I follow? What risk do I run that I already have a root and the seller did, and I don't know by what method he did or what he did to pass it from CN to WW

Categories

Resources