Develop Bugs

[Q] Wiped OS need help to sideload zip file

I just messed up big time.
I have been rooted for a couple of months now and played around with a couple of roms. I noticed my free storage shrinking when there apparently should have been nothing on my Nexus 7 except for the system files. What I did was delete my system,storage and cache with Clockworkmod Recovery leaving me with a blank tablet. Unfortunately now I can't install any zip from my sdcard as there is just emptiness on my tablet meaning I have no OS. I had initially thought I would be able to just install the OS from my usb stick but I couldn't find any way to mount my usb stick in recovery mode and I have reason to believe it just isn't possible.
As far as my research has taught me the only way to install a OS now is via sideloading it. I have spent like 2 hours reading through several threads and various other sites how to sideload a zip file onto my tablet but I'm having trouble with that. I downloaded ADB tools and I looked into this thread: http://forum.xda-developers.com/showthread.php?t=2380913
My current state is that I am in recovery mode and selected 'install zip from sideload' I have ADB tools and the OS but can't sideload it onto my tablet. When I use the command 'adb devices' my N7 is not listed. When I go to device manager the N7 is listed but there is also a warning sign displayed.
{
"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 desperately need help to resolve this issue, I love my Nexus 7 and can't bear the thought of having bricked it for good because of my own stupidity.
Much thanks in advance.
P.S. It is already late at night in Germany so I won't answer in the next few hours.

I think you are on the wrong sub-forum, this is the Nexus 7 - 2013 (2nd revision) sub-forum.
However to answer your question, personally I would boot into the bootloader and use the factory images here:
http://developers.google.com/android/nexus/images
Pick nakasi or nakasig depending on whether you have wifi or mobile version

You need to install this to use ADB while in recovery. You can use fastboot to flash the stock ROM.

sfhub said:
I think you are on the wrong sub-forum, this is the Nexus 7 - 2013 (2nd revision) sub-forum.
However to answer your question, personally I would boot into the bootloader and use the factory images
Click to expand...
Click to collapse
I'm sorry I wasn't aware of this being the wrong sub-forum.
Thanks for your submitted fix, it sounds very simple yet I don't know how to perform it. Do you mean I have to select 'Restart bootloader' on my N7?
How do I then get the factory image onto my tablet?

I'll just summarize, the factory restore is in .tgz (tar.gz) formst. Using 7-zip to open the .tgz and extract the tar file. Open the tar file in 7-zip again the get the factory image directory. Within that directoy is a batch file called flash-all.bat. It needs fastboot.exe to work. Easiest way, copy these files from your platform-tools (adb directory)
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
into the factory image directory.
Reboot your tablet into bootloader (power down, then power+vol- until bootloader menu comes up) That's the button sequence on N7 2013. I don't know about N7 2012
then just type flash-all in a command prompt. It will do the rest.
Make *sure* you get the right version of the factory restore (wifi or mobile).
Alternatively do as Username mentioned. You'll need to delete your existing drivers and install the one he pointed you to. This should get the adb connection recognized. From there you can do the adb sideload you've been attempting.

sfhub said:
I'll just summarize, the factory restore is in .tgz (tar.gz) formst. Using 7-zip to open the .tgz and extract the tar file. Open the tar file in 7-zip again the get the factory image directory. Within that directoy is a batch file called flash-all.bat. It needs fastboot.exe to work. Easiest way, copy these files from your platform-tools (adb directory)
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
into the factory image directory.
Reboot your tablet into bootloader (power down, then power+vol- until bootloader menu comes up) That's the button sequence on N7 2013. I don't know about N7 2012
then just type flash-all in a command prompt. It will do the rest.
Make *sure* you get the right version of the factory restore (wifi or mobile).
Alternatively do as Username mentioned. You'll need to delete your existing drivers and install the one he pointed you to. This should get the adb connection recognized. From there you can do the adb sideload you've been attempting.
Click to expand...
Click to collapse
The ADB/Fastboot driver from SDK only works when in bootloader and booted into ROM. Without the Naked Driver 0.72, his computer would show "Nexus 7" under Unknown Devices in the Device Manager while in recovery. He needs to install it in addition to the SDK driver for his computer to recognize the device while in recovery to Sideload or ADB push.

sfhub said:
...
Alternatively do as Username mentioned. You'll need to delete your existing drivers and install the one he pointed you to. This should get the adb connection recognized. From there you can do the adb sideload you've been attempting.
Click to expand...
Click to collapse
Username invalid said:
The ADB/Fastboot driver from SDK only works when in bootloader and booted into ROM. Without the Naked Driver 0.72, his computer would show "Nexus 7" under Unknown Devices in the Device Manager while in recovery.
Click to expand...
Click to collapse
That's why I suggested he follow your post to install the naked drivers if he wanted to use adb sideload in recovery instead of using fastboot and the images.
Username invalid said:
He needs to install it in addition to the SDK driver for his computer to recognize the device while in recovery to Sideload or ADB push.
Click to expand...
Click to collapse
According to the OP for naked drivers, he suggests removing old drivers. I just relayed what was in that post.
1wayjonny said:
Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers
Click to expand...
Click to collapse

merchants oicedBri
Update:
Thanks for your helpful answers, I figured it out now.

[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 ).

[GUIDE] Flash 'fastboot ROMs' for Lenovo Z6 Pro

Disclaim
All steps described here have been many times tested and proved to be safe but, you may know that sometimes in life unexpected things happen. I'm not responsible for any damage in your devices, do things at your own risk.
Introduction
Thanks to xda user @alexeei we can install almost every Z6 Pro stock ROMs using the Fastboot Mode. You always should check the package content and the installation script(s) to be sure that you know exactly what is gonna be installed. You can find all the ROMs listed and linked in this index.
Let's go with the guide.
0. Pre-requirements
- The Bootloader must be unlocked.
- Lenovo drivers installed in your computer. You can download them here . Thanks @benjieb
1. Download and extract the ROM
You cand find many of them here. Extract the downloaded file and a folder will be created with these contents:
- All the files required for the installation in Fastboot Mode.
- The ROM files.
- The .bat file(s) which contain(s) all the actions that will be performed during the installation.
{
"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"
}
You always should check the content of the .bat file(s). Read post #2 to get more info about this.
2. Reboot your device in Fastboot Mode
Shut down your device and boot it holding pressed both Volume Down + Power buttons until the Fastboot Mode menu appears. You can navigate in the Fastboot Mode menu with volume buttons to choose the options and the Power button to confirm, but at this point you don't need to do any action in this menu.
3. Connect the device to the computer with USB cable
4. Execute the .bat file
Just execute the .bat file with a double click and a CMD window will be opened and the installation will start. Only a few lines will appear at the beginning and then nothing will happen, it will seem to be stopped but actually it's not, just be patient because this screen could last around ten minutes. So despite of the 'Invalid sparse file format at header magic", keep the faith and don't do anything but wait.
The device will reboot once the installation is done.
5. Errors in the log. No voice in calls.
Some errors may appear in the CMD window during the installation, this is because some partitions are 'critical' and we're not allowed to modify them via fastboot. Usually this is not a problem because these "small partitions" don't prevent the new ROM to work normally, except if you're installing Android 10 from Android 9. If you change Android version with this method you will find that your micro doesn't work in calls. You can fix it installing these "small partitions" from TWRP.
Any correction, info or advise about this post will be very welcome.

About the .bat file(s):
You always should check the content of these files before doing any installation, specially with recent fastboot installers including several .bat files for diferent uses. Just open the .bat file with right click and select Edit to view the actions included in the file.
None of Alexei's fastboot installers have never included any command to erase Data, but I'd say it's mandatory to check twice the .bat file to be sure that you're not going to affect an undesired partition. In case e.g. the .bat file includes the line 'fastboot flash system system.img' but you don't want System partition to be installed, just delete this line from the file and Save before closing it.
Maybe you want to edit the file to include in the batch any other thing, a custom recovery for instance. Just drop your custom recovery file in the rom folder (the fastboot installer folder) and make sure that the line in the .bat file regarding the recovery matchs with your recovery file name.
Also you can notice that recent fastboot installers include more than one .bat file. They are named in a descriptive way like "UpdateZUI.bat" or "UpsateAOSP", but you should check them anyways. Let's say you're using any of the Q aosp-based custom ROMs (they include Boot and System partitions) and you want to update the vendor and/or the firmware. You should check the .bat files to find which of them suits better with your needs.

descarao81 said:
About the .bat file(s):
You always should check the content of these files before doing any installation, specially with recent fastboot installers including several .bat files for diferent uses. Just open the .bat file with right click and select Edit to view the actions included in the file.
None of Alexei's fastboot installers have never included any command to erase Data, but I'd say it's mandatory to check twice the .bat file to be sure that you're not going to affect an undesired partition. In case e.g. the .bat file includes the line 'fastboot flash system system.img' but you don't want System partition to be installed, just delete this line from the file and Save before closing it.
Maybe you want to edit the file to include in the batch any other thing, a custom recovery for instance. Just drop your custom recovery file in the rom folder (the fastboot installer folder) and make sure that the line in the .bat file regarding the recovery matchs with your recovery file name.
Also you can notice that recent fastboot installers include more than one .bat file. They are named in a descriptive way like "UpdateZUI.bat" or "UpsateAOSP", but you should check them anyways. Let's say you're using any of the Q aosp-based custom ROMs (they include Boot and System partitions) and you want to update the vendor and/or the firmware. You should check the .bat files to find which of them suits better with your needs.
Click to expand...
Click to collapse
Thanks for your instruction. Will this method work on other lenovo devices. I have a lenovo tablet running android 10 chinese stock rom, now I would like to flash global stock rom

hilary trump said:
Thanks for your instruction. Will this method work on other lenovo devices. I have a lenovo tablet running android 10 chinese stock rom, now I would like to flash global stock rom
Click to expand...
Click to collapse
It depends on the rom package. The packages made to be installed using fastboot are usually very similar, but you should check the .bat files. I could take a look if you provide a link.

descarao81 said:
It depends on the rom package. The packages made to be installed using fastboot are usually very similar, but you should check the .bat files. I could take a look if you provide a link.
Click to expand...
Click to collapse
Thanks. The rom has not released yet. I just pre-ordered a chinese variant tablet P11 pro TB-J706F

descarao81 said:
It depends on the rom package. The packages made to be installed using fastboot are usually very similar, but you should check the .bat files. I could take a look if you provide a link.
Click to expand...
Click to collapse
I found the link as follows
mirrors.lolinet.com/firmware/lenovo/ Tab_P11_Pro/TB-J706F/TB-J706F_S210002_201015_ROW.zip
But inside the package there is no BAT file though

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

[EOL][ROM][UNOFFICIAL][12.1] LineageOS 19.1 for Galaxy Note10 5G [d1x][N971N][ENCRYPTION]

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