How To Guide Extract Boot Image (for Root) - the DSU-Sideloader Method (and Other Tutorials)

How To Guide Extract Boot Image (for Root) - the DSU-Sideloader Method (and Other Tutorials) - Lenovo Legion Y700

Very nice to see Y700 get it's own place on XDA! I myself had just bought the 12GB version and have been very satisfied. The tutorials and info related to this model had been very difficult to come by and mostly in other languages, so I had to do my own research and exploration. So far I was able to flash ROM and extract it's boot image for root thanks to the following tutorial (in Japanese)
boot.imgを入手できない機種でMagiskを導入する方法【DSU Loader】
Android端末のカスタマイズやRoot権限の使用が可能となる「Magisk」ですが、一部例外を除き、導入に…
smartasw.com
The boot image extraction part is trickier as Y700's roms come in GSI form. But with a workaround we can still achieve the same goal. (I heard that you can also use QFIL to do that but I haven't been able to make the tool work, so if someone else can make a tutorial that'd be great)
First you need to prepare:
- DSI-Sideloader from https://github.com/VegaBobo/DSU-Sideloader/releases
- Magisk Manager from topjohnwu's GitHub repo
- a GSI ROM with built in root permission. The one the tutorial was using: https://github.com/phhusson/treble_experimentations/releases/tag/v402 --> go download "system-squeak-arm64-ab-vanilla.img.xz" (~600MB, smallest needed to fulfill the task)
- turn on developer mode and ADB debugging. Get Google SDK platform tools ready and USB drivers installed.
Connect your Y700 to a computer. Check if ADB works.
Next, install the DSI-Sideloader app. Also extract the .xz package you downloaded above to get the .img image (should be ~1.7GB in size)
Copy the image to your Y700 tablet. Open the DSI-Sideloader app, load the image, set userdata size to default (2GB). You can leave image size unchanged.
NOTE: if you have an SD card inserted, click on "config" and check "Unmount SD", or just eject your SD card from tray. Failing to do so will result in error in the install step.
After you're done, click "Install". Once finished there will be a pop-up with commands you need to enter in the terminal of your choosing. On your computer navigate to the directory containing executables of Google SDK platform tools, fire up terminal, enter the 1st command (says non-root) as instructed, and run it.
You will see a progress bar in the drop-down notification area which will complete in a moment and prompt you to reboot. Do that from there.
After reboot you will be running the modded Project Treble ROM, with root access. It's a full fledge OS but once you shutdown / reboot you will go back to your own OS. Treat it as a LiveCD of some sort.
While still connected, turn on dev mode + ADB debugging and go back to terminal for some ADB work. Next we will be extracting boot image under the current environment, made possible by it's built-in root permission.
Run the following line by line:
Bash:
adb shell
Bash:
su
Bash:
cd /dev/block/bootdevice/by-name/
Bash:
mkdir /sdcard/backup_img
Bash:
for file in *; do
if [[ "${file}" = boot* ]]; then dd if=/dev/block/bootdevice/by-name/"${file}" of=/sdcard/backup_img/"${file}".img ; else continue ; fi
done
The 4th command creates a new directory storing extracted boot image, in our case /SD card/backup_img; and the 5th command is the meat of the entire process. It consists of 3 lines, key in one at a time and press "Enter". First line is "for...do", second is "if [[..." to "fi", third is just "done".
After some time the extracted boot image will be stored under the directory specified by the 4th command, in our case /sdcard/backup_img . They are stored in the temporary user space and once you reboot to your original OS you won't be able to access them again. So you need to turn on File Transfer mode, go to the actual directory on your PC and move them to your computer. They have the filenames "boot_a.img" and "boot_b.img" . After you're done, just reboot as usual and you'll get into your old OS.
Now you have the boot images, all that's left is to use Magisk Manager to patch them, enter fastboot mode, and flash the patched images using the following commands:
fastboot flash boot_a patched_img_A.img
fastboot flash boot_b patched_img_B.img
(Rename as needed)
And now your Y700 is rooted.
The linked Japanese webpage also talks about working Android 12 / 13 GSI flavors, patches, and ways to set up your Y700.

Related

[FAQ] GT540 Reference Thread | How-to's | Data2System method by Anton_ch ADDED!

~ FAQ | LG GT540 REFERENCE THREAD ~
.:: http://mygt540.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"
}
~ o ~
LG GT540 is equipped with 512Mb ROM (flash memory).
It is divided into sections: * Boot (boot partition | 5 MB) - contains the kernel of linux system and the ram-disk image
* System (system partition | 245 MB) - contains built-in Android applications
* User (userdata partition | 138 MB) - contains custom applications / settings
* Cache (cache partition | 64 MB) - unnecesary files you need to clean often
 ~ o ~
START | NEWBIE
[HOW-TO] Set up SDK/ADB/FASTBOOT on Ubuntu 11.04
[HOW-TO] Set up SDK/ADB/FASTBOOT on Windows | Flash Android ROMs 2.1/2.2/2.3
[HOW-TO] Create a EXT4 & SWAP partition on Windows / Linux
[HOW-TO] Use ADB tool | Android Debug Bridge
[HOW-TO] Install LG IME Full
[HOW-TO] Change default fonts | Custom ROMs
[HOW-TO] Use Fastboot tool | Bootloader
[HOW-TO] Replace Files | Set permissions
__________________________________________________
RESTORATION | ADVANCED
[FAQ] My Phone is bricked !!! | GUIDE
__________________________________________________
TECHNICAL TRICKS
[TUTORIAL] Self-Assembly of Android OS Firmware
[TUTORIAL] Data2System method by Anton_ch | Custom ROM's
[HOW-TO] Fix MD5 mismatch | Nandroid restore
[HOW-TO] Fix Russian Profile | Swiftdroid
[HOW-TO] Change default low system sounds | Sound Scheme
~ Please user DO NOT POST IN HERE, LET'S KEEP THE THREAD CLEAN, PM me if you have a question or something to say. Thanks! ~

are Welcomed!!!

[HOW-TO] Set up SDK/ADB/FASTBOOT on Ubuntu 11.04
TUTORIAL #1
THANKS TO bloodychaos FROM XDA
I've been searching around the forums,the stickies and Google on how to install ADB in Ubuntu from scratch but I wasn't able to get a guide anywhere. What I found mostly are for Windows or little bits and pieces of info which did not cover the whole thing. Which is when I decided to grab some Tab and Mountain Dew, and Google my way through to make it work and share it to those who had trouble or no idea how to install it on Ubuntu.
When I'm writing this, I'm using Ubuntu 10.10 64bit to install and run everything. There was mentions of using Eclipse SDK while searching around, but I won't be touching on that. There's another guide for it at the end of my guide. I have yet to encounter any problems while using ADB in 64bit environment. I've tested it out on the 32bit platform as well and it works. It'll also work on SD and NAND versions of Android for the HD2, since it's my main phone. Also, this is my first time making a guide, so bear with me if there's any mistakes. I've checked the article a few times hoping that it's clear and easy to understand.
Step 1. Install JDK
You'll need to install JDK for ADB to work. If you have already installed JDK, I recommend reinstalling it again, just in case there are new updates or you have the older version.
Open Terminal and enter the following command(s), then enter your ubuntu login password followed by ‘y’ when prompted for yes/no.
Code:
$ sudo apt-get update
$ sudo apt-get install openjdk-6-jdk
Step 2. Download and Install Android SDK
Download the Android SDK. Obviously, choose the one for linux (android-sdk_r10-linux_86.tgz)
Code:
http://developer.android.com/sdk/index.html
Extract the android-sdk-linux_x86 folder from android-sdk_r10-linux_x86.tgz and put folder to your desired location. I recommend to put in home/username/ | When using the terminal the same path is described as ~/
Step 3. Choose packages to install
First of all go to ~/android-sdk-linux_x86/tools/
Right clic to android >> Properties >> Permissions
Make sure "allow executing file as a program" it's checked
In Terminal, type the following
Code:
$ cd ~/android-sdk-linux_x86/tools
$ ./android update sdk
The 'Android SDK and AVD Manager' window will appear (screencap below). If you are not a developer then just accept the first option to install and the rest reject. Once installation is finished, it will prompt you to restart the manager. Just click 'Yes' and close the manager
Step 4. Check your device's permission
Now head over to the platform-tools directory
Code:
$ cd ~/android-sdk-linux_x86/platform-tools
Check if you have permission for your device
Code:
$ ./adb devices
If you're getting the following, go on to Step 5.
Code:
List of devices attached
???????????? no permissions
If you're getting something like this or other random numbers with the word device next to it, congrats! You now could use ADB. Now go on to Step 7.
Code:
List of devices attached
0123456789ABCDEF device
Step 5. Giving permission to your device
You'll need to create a certain udev rule. First off type the following in Terminal:
Code:
$ sudo gedit /etc/udev/rules.d/99-android.rules
Once the gedit window pops-up, type the following line
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
Here's a list of each vendor's ID. Source: http://developer.android.com/guide/developing/device.html
Save the file and exit out of gedit. Back in Terminal execute the following
Code:
$ sudo chmod a+rx /etc/udev/rules.d/99-android.rules
$ sudo restart udev
$ sudo adb kill-server
Then unplug your phone and plug it again
Now to check if it works
Code:
$ ./adb devices
You should be getting the following line or something similar:
Code:
List of devices attached
0123456789ABCDEF device
Congrats! Now you can use ADB in Ubuntu! Now hop on to Step 6!
Step 6. Create path for ADB and Fastboot
NOTE: while using adb in Linux, you'll need to type ./adb to execute adb unless you create a path in ~/.bashrc.
Code:
$ sudo gedit ~/.bashrc
Add the following line at the very end of the file. Once you're done, save and exit.
Code:
# Android tools
export PATH=${PATH}:$HOME"/android-sdk-linux_x86/tools"
export PATH=${PATH}:$HOME"/android-sdk-linux_x86/platform-tools"
Then in a Terminal run this command to reload your .bashrc:
Code:
source ~/.bashrc
Now you can just run adb without put ./ before every command.
Step 7. Set up FASTBOOT
Download Fastboot file from here: http://www.mediafire.com/?uc8zvuoklr8qlmk
Move it to ~/android-sdk-linux_x86/tools/ folder
Right clic to Fastboot >> Properties >> Permissions
Make sure "allow executing file as a program" it's checked
Reboot in fastboot mode (bootloader), then plug your phone with USB cable to a computer
Open a terminal and type:
Code:
$ sudo -s
# fastboot devices
0123456789ABCDEF fastboot
NOTE: you must login as root to fastboot to work. If you get an error issuing the last command then most likely something went wrong while creating a path for fastboot in ~/.bashrc, then you should try with ./ statement before the command like this:
Code:
# ./fastboot devices
0123456789ABCDEF fastboot
__________________________________________________
* For more in-depth guide, try HowtoForge. Just found this guide today and I find it VERY useful and even have a good guide on Eclipse.

[HOW-TO] Set up SDK/ADB/FASTBOOT on Windows | Flash Android ROMs 2.1/2.2/2.3
TUTORIAL #2
HELLO I SEE THERE IS QUITE OF PEOPLE (NEWBIES) THAT ARE HAVING PROBLEMS WHILE FLASHING, MOST OF THE TIMES FROM STOCK 1.6 TO 2.1, SO I WANTED TO SHARE THIS TUTORIAL I MADE AND WOULD LIKE TO ALL OF YOU CONTRIBUTE IN SOMETHING MISSING OR NEW THINGS FOR THIS TUTO AND MAKE IT THE UPDATED AND BEST TUTO FOR DUMMIES OUT THERE . NO OFFENSE . JUST THAT THERE ARE LOTS OF PEOPLE NOT FAMILIARIZED WITH THIS KIND OF STUFFS.
THANKS TO CHKRLY FROM TARINGA! FOR THE BASIS OF THIS TUTORIAL, i added and quit some parts, translated and attached files...
WARNING: Any of these methods can brick your phone, im not responsible if that happens. READ ALL THE TUTORIAL FIRST. If your phone gets unresponsive DO NOT PANIC! we are here for HELP!
FIRST PART
(Flash from 1.6 to 2.1 with fastboot)
In this part we are going to flash an european ROM that comes with fastboot with the purpose of flash other ROMs that needs fastboot later...
1. Create a folder, download the KDZ Updater , the European ROM and the drivers for our LG GT540 and unzip them all in the same folder.
Install KDZ
Deactivate your FIREWALL and Antivirus if necessary
Install drivers:
UPDATE: Thanks to eoghan2t7 you can install LG GT540 drivers all in one:
METHOD1: NEW
LGGT540 ALL IN ONE DRIVER PACK.exe (32 bits users only)
METHOD2: OLD
Or install the drivers in the old normal way (32 & 64 bits users)
WINDOWS7 users: Right clic>> Run as administrator.
Also is very important you install the drivers inside the LG_SmartPhone folder:
2. On to the phone go to: SETTINGS >> APPLICATIONS >> DEVELOPMENT and activate the mode USB debugging , also check out this:
SETTINGS >> SD CARD AND PHONE MEMORY >> EXTERNAL ONLY MEMORY (not SECRET_, remove if), then plug you phone to the computer
3. Close all applications you do not need on the computer and run the KDZ_FW_UPD.exe (Windows 7 users: right clic>>start as Administrator)
4. Once in the program select from the TYPE list the 3GQTC option and then clic in the folder icon and select the European ROM(KDZ file) from the folder where you unziped, then press the button Launch Software Update
NOTE: It is important mention that while in the process dot not interrupt the program, unplug the phone or shutdown the computer
*If it stops in any of the processes and doesn't finish (processes doesn't get stuck for long), then unplug your phone, close the program, open it again plug your phone, and run it again.
*If that doesn't help eather, remove the battery, close the program, plug your phone to the computer, start the program and run the process again.
NOTE: various problems in the following procedure to update can occur if non of the above tips helped then try this:
Go to Device Manager in your computer>> right click on the LG Modem Android>> DISABLE / Modem>> LGE Virtual Modem>> DISABLE and then try FLASHING AGAIN
THE WHOLE PROCESS SHOULD TAKE 10 MINUTES
Once the program has loaded the ROM to the phone it will appear a leyend FINISHED, after that the phone will reboot and boot android 2.1 with fastboot.
SECOND PART
(Flash from stock 2.1+fastboot to custom 2.1/2.2/2.3...)
1. Download the following files:
- Google SDK tools, unzip and put the folder in C:\ drive
- Drivers for your computer recognize the phone in fastboot mode. Unzip and put the files inside the folder in C:\android-sdk (take a look of the 3th image)
INSTALL WITH YOUR PHONE PLUGGED:
... then next and it will install the drivers.
- Clockwork recovery (latest version) and place it in C:\android-sdk
- Download the ROM you want to flash for FASTBOOT NOT RECOVERY, UNZIP and place the .IMG FILES in C:\android-sdk
NOTE: It is RECOMMENDED that from stock 2.1 you flash to 2.2 and then to 2.3 and so on, this means not go directly to 2.3.3 as may cause your phone do not boot properly and also not login to recovery. This is not confirmed but some users have experienced this kinds of issues.
2. Shutdown your phone and Start it in fastboot mode (CAMERA+POWER BUTTON) hold the camera for 1 sec then add the power button . Wait few second you will see LG's logo then the screen will turn dark, CLEAN DARK SCREEN, just in that moment you are in FASTBOOT mode.
3. Flash rom by FASTBOOT mode:
Plug your phone to the computer and open a CMD terminal and type:
Code:
cd C:\android-sdk
4. Once inside the folder type ONE by ONE:
Code:
fastboot flash recovery recovery_clockwork_3.0.2.4_swift.img
fastboot -w
fastboot erase boot
fastboot erase system
fastboot flash boot boot.img
fastboot flash system system.img
fastboot -w
fastboot reboot
THAT MY FRIEND IS A CLEAN INSTALL...
5. Once is rebooting fast login to recovery pressing POWER+HOME. Inside recovery select wipe data/factoryreset for reset the phone. Then select reboot, and that's it YOUR DONE!
NOTE: If you are flashing any ROM with data2system method then DO NOT WIPE DATA/FACTORY RESET, just reboot.
6. Set your phone as you like install all your apps and once you done reboot into recovery and go to backup & restore>> backup for create a backup of your entire phone.

[HOW-TO] Use ADB tool | Android Debug Bridge
TUTORIAL #3
You can find the adb tool in C:\<sdk>\platform-tools\ or C:\<sdk>\
*All the examples refers to /data/app path you can change to /system/app or any other path you need
Open a CMD terminal on Windows:
Start>>run>> type cmd>> click ok (WinXP)
Start>> in search box type cmd>> right click Run as Administrator (Win7)
Once opened type:
Code:
cd C:\<sdk>\platform-tools
adb devices
adb remount (from r/o to r/w)
-----------------------------------------------------
adb shell mount /system (if you only want to mount system)
adb shell mount /data (if you only want to mount data)
Installing an Aplication .apk
Put the .apk file into C:\<sdk>\platform-tools\ folder and type
Code:
adb install [B]appname[/B].apk
Uninstalling an Aplication
There is an uninstall adb commans that always shows failure!!!
So we are going to use Adb Shell:
Code:
adb shell
# cd data/app
# ls
# rm -r appname.apk
# ls
Ctrl+c to exit shell mode
You will not find this application, you just removed it!
Push & Pull commands
Pull:
Code:
adb pull /data/app/appname.apk
If you want to PULL all the files located in a folder then:
Code:
adb pull /data/app test
to pull all the .apk's located /data/app and save them into a folder that it will create in C:\Android-SDK\platform-tools named test
Push:
Code:
adb push appname.apk /data/app
If you want to PUSH all the files located in a folder then:
Code:
adb push test /data/app
to push all the .apk's located in C:\Android-SDK\platform-tools\test folder to /data/app
Close ADB
Code:
adb kill-server
exit

[How-to] Replace Files | Set permissions
TUTORIAL #4
When you need or would like to add or replace a file to our phone we need to set permissions.
In this tutorial we are going to use Root Explorer for this purpose, because is the "standar" file manager that comes with custom roms lately.
Apart of this, if you are having issues with applications for incorrect permissions then you might FIX permissions using ROM MANAGER application not RECOVERY (not recommended)
REPLACING A FILE:
in this example we are going to replace our old Music.apk for the newest Music.apk...
*Applies for replace any file
Before: After:
1. Backup your old Music.apk then uninstall it (I can do both with RootAppRemover.apk or Titanium Backup)
1. Plug your phone, mount your sdcard then download Music.zip
to your desktop
2. Put the Music.apk and libjumper.so into /sdcard/newmusic folder
3. Close the windows, unmount your sdcard, unplug your phone then go open Root Explorer application
4. Go to sdcard/newmusic/ >> press menu button >> Multi-select >> select Music.apk >> press copy button
5. Press back button and go to system/app/ >> press Mount R/W >> press Paste button
6. Look for the Music.apk you just pasted and press on it until a window pops up:
7. Select Permissions and change them to rw-r--r--
TO
It should look like this:
9. Repeat process from step 4-to-7 to replace libjumper.so but to /system/lib/ path
THANKS ARE WELCOMED!!!

[TUTORIAL] Self-Assembly of Android OS Firmware
TUTORIAL #5
* This tutorial was created for me after read from many sites and figure it out by myself and the result is a 100% fully working step by step tutorial.
* First of all you need to have installed Ubuntu then Follow this: [How-to] Set up SDK/ADB/FASTBOOT in Ubuntu 10.10
* Once everything is set and working download IMG_tools.zip then unzip in home/username/IMG_tools/
* When i mention ~/ means home/username/ but shorty
Proceed...
Extract boot. img
-To extract boot.img use extract_boot from ~/IMG_tools/boot
- Put boot.img file inside ~/IMG_tools/boot/ folder
- Open a terminal and type:
Code:
$ cd ~/IMG_tools/boot
$ ./extract_boot boot.img
- if you want to extract boot.img in another folder, for ex. in ~/ROM/ then the command is
Code:
$ ./extract_boot ~/ROM/boot.img
- You will get something like this
Page size: 2048 (0x00000800)
Kernel size: 2664916 (0x0028a9d4)
Ramdisk size: 966,485 (0x000ebf55)
Second size: 0 (0x00000000)
Board name:
Command line: mem = 214M console = tty0, 115200n8 androidboot.hardware = swift uart.mode = arm11_uart_disable crash = off
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
3210 block
Click to expand...
Click to collapse
Rebuild boot.img
-To rebuild boot.img use make_boot from ~/IMG_tools/boot
- Double click make_boot>> show
Compare info after cmdline with Command Line after extracted boot.img, if its different then modify the file.
- Once verified info type:
Code:
$ ./make_boot boot.img
- You will now see a boot-new.img file ready for flash
Click to expand...
Click to collapse
Extract system. img
-To extract system.img use unyaffs from ~/IMG_tools/system
- Put system.img and unyaffs file inside ~/IMG_tools/system/system folder
- Open the terminal and type:
Code:
$ cd ~/IMG_tools/system/system
$ ./unyaffs system.img
- Then cut system.img and unyaffs file and put them back to ~/IMG_tools/system
Click to expand...
Click to collapse
Rebuild system. img
-To Rebuild system.img use mkfs.yaffs2 from ~/IMG_tools/system
- Do not move mkfs.yaffs2 file
- Open the terminal and type:
Code:
$ ./mkfs.yaffs2 system system.img
Click to expand...
Click to collapse
Rebuild system. img [update.zip]
* works to sign .apk too
- If you have based your work on RUU file, you’ll have to create META-INF folder with the correct information and update scripts inside. If you have unpacked someone’s .zip, the META-INF folder should be already present. Update script might mention some files in the update, so if you have removed (or added new) files, the update script should be amended to reflect those changes. Please, get a few images from different developers and try to understand the correct internal structure.
Once you have something like this:
- Open the terminal and go where your <workdir> content is: META-INF, system, boot.img then type
Code:
$ zip -r9 update.zip *
-r9 tells the program to collect files recursively and use the maximum compression. If you omit “r”, the subfolders will not be included (bad, bad idea!), if you omit “9″ nothing bad will happens, but resulting file might be about 1% larger.
- Now to sign the zip file put sign folder and androsign file from ~/IMG_tools/sign/ to ~/*SDK/tools
- Go back to the terminal and type
Code:
androsign /<workdir>/update.zip
Click to expand...
Click to collapse
Odex Files
- What are those Odex files? Answer
- How to get rid of them?
Odex files depend on framework they are made for. To deodex an odex file use that how to
Then you may create a classes.dex file by executing the smali program on the "out" folder. You then rename it to classes.dex and add it to the .apk.
- How to create them?
Use dexopt-wrapper on device.
For deodex ODEX files, use this howto
Then you can create classes.dex file by running smali from your "out". Then rename it to classes.dex and add it to apk.
Click to expand...
Click to collapse
Porting another's devices ROM
Well, this part is simple smile_good.gif
- Extract system.img
- Extract boot.img
- Replace boot.img-kernel of the original Roma HTC Hero.
- Rebuild boot.img
- Collect update.zip (see how it's done in any Custom rum for Hero)
- Sign and flash.
Device should start, and even be able to call, but probably will not work WiFi, BT, trackball.
Click to expand...
Click to collapse

[HOW-TO] Fix MD5 mismatch | Nandroid restore
TUTORIAL #6
THANKS TO ihtfp69 FROM XDA!
To fix this is assuming you did not change the folder names and let Clockworkmod create them.
Code:
Checking MD5 sums...
MD5 mismatch!
- Plug your phone to the computer
- Open a Terminal and type:
Code:
adb devices
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
# exit
* Substitute the final folder name for the backup you need to fix.
- Re-run the restore and everything should be fine.
NOTE: As rpearl stated, there could be something really wrong with your nandroid, so use this tutorial as a learning experience and not a fix-all. In my case, everything was fine after restoring. However, that may not always be the case. Do this with caution.

[HOW-TO] Install LG IME Full
TUTORIAL #7
- Dowload LG_IME_data2system and unzip in desktop
- Open System folder and copy the 3 folders: app, lib2 and usr folders to C:\*SDK\platform-tools\
- Plug your phone to the computer
- Open a CMD terminal and type:
Code:
cd C:\*SDK\platform-tools
adb devices
adb remount
adb push app /system/app
adb push lib2 /system/lib
adb push usr /system/usr
adb kill-server
exit
- Unplug your phone
- Go to ROM Manager application and run Fix Permissions (DO NOT avoid this step, so you dont get FC's)
DONE!

[HOW-TO] Use Fastboot tool | Bootloader
- What is fastboot?
Fastboot tool is a program used to update the flash partitions in Android devices from a host (PC) over USB.
It allows you to perform flashing images (*.img) files to your device.
_________________________________________
- How do i get in Fastboot mode?
You can boot in Fastboot mode in two ways:
1. For 2.2 / 2.3 Android ROM:
Hold the power button until a window pops up | Select reboot >> bootloader >> OK
2. For any Android ROM
Shutdown the phone >> hold CAMERA + POWER buttons
_________________________________________
- How do i know im in Fastboot mode?
After you press the combo buttons and the phone starts you be able to see the LG logo and just after that the screen will clean and turn dark-blue, nothing else. If that happens congratulations! you are in Fastboot mode.
NOTE: it has been told that in some firmwares the fastboot mode screen turns out blank. If you experience that dont panic! you might want to try another firmware with the normal fastboot mode.
_________________________________________
- Usage of the Fastboot commands
NOTE: to start using Fastboot is assuming you already have installed SDK with all the tools
1. You need to place the *.img files you are going to flash into
C:\*SDK\tools\ (Windows)
Home/username/*SDK/tools (Linux)
Click to expand...
Click to collapse
2. Plug your phone with a USB cable to your computer
3. Open a Terminal (Windows|Linux) and issue the following commands:
Code:
fastboot erase recovery
------------------------------------
fastboot flash recovery recovery_clockwork_x.x.x.x_swift.img
fastboot -w
fastboot erase boot
fastboot erase system
fastboot flash boot boot.img
fastboot flash system system.img
fastboot -w
fastboot reboot
* fastboot erase recovery | use when reinstalling clockwork recovery
* fastboot -w | is for wipe data/cache and make a factory reset

[HOW-TO] Fix Russian Profile | Swiftdroid
THANKS TO tejasdj12 FOR THIS FIX
There are 2 ways to Fix Russian Profile:
METHOD #1:
Copy the profiles.xml file to /data/system folder. Reboot.
* If the first method did not work then you have a second method
METHOD #2:
1. Open Root Explorer or any other file manager
2. Find /system/build.prop file and edit these sections:
Code:
'ro.product.locale.language=ru' to 'ro.product.locale.language=en'
'ro.product.locale.region=RU' to 'ro.product.locale.region=US
3. Save the File
4. Reboot into recovery and wipe user data/factory reset. Reboot.

[HOW-TO] Change default fonts | Custom ROMs
THANKS TO sonnysekhon FROM XDA!
* Tested on CM7 ROMs | PM me if it works with/without CM6
METHOD #1: [Install zip from recovery]
1. Download the Font you like from here:
2. Mount your phone and put the .zip into SDcard/
3. Unplug your phone and reboot it into recovery.
4. After that, go to “install zip from sdcard >> choose zip from sdcard >> select your copied zip file”
5. After it installs it, select “reboot system now”
________________________________________________
METHOD #2: [Using ADB tools | Data2System by Anton_ch users]
1. Download the Font you like from here:
2. Unzip the folder to your desktop. You will see 2 folders:
META-INF
System
3. Open System folder and copy fonts folder to C:\*SDK\platform-tools\
4. Plug your phone to the computer
5. Open a CMD terminal and type:
Code:
cd C:\*SDK\platform-tools
adb devices
adb remount
adb push fonts /system/fonts
adb kill-server
exit
6. Unplug your phone. Reboot
DONE!
________________________________________________
* If you want to go back to default-fonts, download and repeat steps 2-6 from METHOD #2

[FAQ] My Phone is bricked !!! | GUIDE
THANKS TO ilovelg FROM MODACO!
So you failed to read the TUTORIAL and bricked your phone while trying to flash GT540, here is what you should try to do:
[HOW-TO] Repair your device if you see only LG logo | Nothing else happens when you boot your device
Make sure you use USB ports that are in back of youre PC, dont use front ones.
Disable LGE Virtual Modem. In your Windows operating system, go to Control Panel > System > Hardware > Device Manager > Modems > Right click on LGE Virtual Modem and click Disable.
Try to reflash your phone again, in the normal way.
____________________________________________
[HOW-TO] Repair your device if it feels like dead | When you click power button nothing happens (Note that this may or may not work)
Make sure you use USB ports that are in back of youre PC, dont use front ones.
Disable LGE Virtual Modem. In your Windows operating system, go to Control Panel > System > Hardware > Device Manager > Modems > Right click on LGE Virtual Modem and click Disable.
Try to boot your phone into Emergency/Download mode (VOL DOWN + POWER).
If the phone booted into Emergency/Download mode, launch KDZ Updater.
In TYPE dropdown menu, choose EMERGENCY.
Load KDZ(ROM) and flash your phone.
If the phone failed to boot into Emergency/Download mode (VOL DOWN + POWER), launch KDZ Updater.
In TYPE dropdown menu, choose CS_EMERGENCY.
Load KDZ(ROM) and flash your phone.
____________________________________________
THANKS TO fishears FROM XDA!
[HOW-TO] Repair your device if you don't see LG logo, boot animation | Recovery doesn't show up
Download the French v20A and the out.kdz
Take out your battery, SIM and SD card
Plug USB into PC (but not phone yet)
Hold (VOL DOWN) button and plug USB into phone | *Phone goes into Download Mode
Run KDZ Updater
In TYPE dropdown menu, choose CS_Emergency mode
Load French V20A ROM and flash it
When it's finished pull out USB again and hold (VOL DOWN) and reinsert USB to put phone back in Download Mode
Launch KDZ Updater (still in CS_Emergency mode)
Load out.kdz and flash it
You should now have your boot animations back and you can flash whatever ROM you want to use.
____________________________________________
LAST RESOURCE:
If the phone still doesn't work, take your phone to local LG Warranty service or your Operator where you got the phone. Tell them that after you turned the phone off, it doesn't seem to turn back on again!
Click to expand...
Click to collapse

[HOW-TO] Change default low system sounds | Sound Scheme
THANKS TO miroslav_mm & Glay-z FROM 4PDA!
Introduction:
Sources were taken from the phones Nokia, Sony Ericsson, iPhone, HTC and others converted to a good quality and matched to the "my taste, for a full sound experience through our LG GT540 speaker! No pop, rock and techno is not here! 
Also, as a bonus, was changed bootanimation(CyanogenMod 7.0) and tuned the system started for 2.1 ROMs!
- Requires ROOT
- Require recovery v3.0.2.4 +
- The installation is via recovery: Update.zip
-----------------------------------------------------------------------------
- Data2System by Anton_ch users cannot install zip from sdcard, instead replace with Root Explorer or push files with adb tool. Please take a look in the Thread to see how-to do it.
The path is:
Code:
/system/media/audio/alarms
/system/media/audio/notifications
/system/media/audio/ringtones
* In almost all the versions i've made there is not need to do this as i've already done it, only the clean versions users might use it!
Sound Scheme for LG GT540 v1.0 by miroslav_mm
* Works on firmware version 2.1 (A, B, D, Quarx) | 2.2.1 (only partially replaces the tunes as there are more than 2.1)
Were replaced by all the usual sounds of SMS, alarm clock, income calls!
update.zip (16.69MB)
Sound Scheme for LG GT540 v2.0 by Glay-z
* Works on firmware version 2.3.2 | 2.3.3 | 2.3.4
Were replaced by all the usual sounds of SMS, alarm clock, income calls, all the keys and the camera!
update3.zip (15.18MB)
Sound Scheme for LG GT540 v3.0 by Glay-z
* Works on firmware version 2.3.2 | 2.3.3 | 2.3.4
Unlike version 2.0 it does not replace the key sound but instead installed a new font
update5.zip (33.03MB)
Sound Scheme for LG GT540 v4.0 by Glay-z
* Works on firmware version 2.1 | 2.3.2 (ignore the bootanimation) | 2.3.3 | 2.3.4
Were replaced all the system sounds and added CM7 bootanimation as a bonus
update10.zip (45.34MB)

[TUTORIAL] Data2System method by Anton_ch | Custom ROM's
PREREQUISITES:
------------------------------------
* Have Ubuntu in your PC by: Live CD, installing with Wubi, installing with a Virtual Machine or if you want to give it a long try installing directly to your PC.
* Set up Ubuntu with Android-SDK tools: [How-to] Set up SDK/ADB/FASTBOOT in Ubuntu 10.10
* Once everything is set and working download IMG_tools.zip then unzip in home/username/IMG_tools/
* FLASH THE ROM/FIRMWARE YOU WANT TO MODIFY WITH THIS METHOD
INSTRUCTIONS:
------------------------------------
FIRST PART
[Rebuild the kernel with a modified init.rc]
SECOND PART
[Flash new kernel, fit system in /data, modifications]
1. Go in recovery > mounts&storage and mount / system and / data
2. Open a terminal and type:
$ cd ~/android-sdk-linux_x86/platform-tools
$ adb shell
First make sure that operation is possible:
# df
Will be a similar conclusion:
# Filesystem 1K-blocks Used Available Use% Mounted on
# Tmpfs 85908 0 85908 0% / dev
# / Dev/block/mtdblock1 65536 1160 64376 2% / cache
# / Dev/block/mtdblock4 250880 122344 128536 49% / system
# / Dev/block/mtdblock6 141 824 1156 140 668 1% / data
Size used in the /system 122,344 KB
Total size in /data partition 141824 KB
3. Hence system will fit in /data (estimate with a margin of 3-4 MB just in case)
As 122344 is < than 141824 = IT FITS! / Until 138 MB size in /system is safe to go
If it does not fit - clean /system from unnecessary:
# cd /system/app
# ls
# rm example.apk
If it fits, has more free space and you want to install apps:
# exit
Install applications of interest, here are some how-to's:
<< You can fill the partition until you get 138MB to be safe >>
[HOW-TO] Install LG IME Full
[HOW-TO] Change default fonts | Custom ROMs
[HOW-TO] Replace Files | Set permissions
[HOW-TO] Change default low system sounds | Sound Scheme
$ adb push ...
If it fits but you don't want any modification in it, then we proceed...
# exit
4. Put boot-new.img into ~/android-sdk-linux_x86/platform-tools/ folder and type:
$ adb push boot-new.img /data/
$ adb shell
# flash_image boot /data/boot-new.img
Now go to the directory /data and clean it
# cd /data
# rm -r *
On the lost + found - do not pay attention, everything is OK
Go to /system and copy all to /data
# cd /system
# cp -a * /data/
Process is not fast ... wait
Now clear the /system
# rm -r *
5. In the recovery unmount /system and /data
6. You can immediately make a backup of what happened.

I am on switdroid M5. I tried method 1 above for two different fonts and both failed with similar messages.
E:Error in /sdcard/Font_stock.zip (status 0)
Installation aborted.

[email protected] said:
I am on switdroid M5. I tried method 1 above for two different fonts and both failed with similar messages.
E:Error in /sdcard/Font_stock.zip (status 0)
Installation aborted.
Click to expand...
Click to collapse
Maybe because you have the latest recovery installed and its not compatible with that script, but try second method works for everybody anyways
EDIT: Please DO NOT POST IN HERE, LET'S KEEP THE THREAD CLEAN, PM me if you have a question or something to say.
Veronica

[HOW-TO] Create a EXT4 & SWAP partition on Windows / Linux
Thanks to pyroblazer from XDA!
*** PRINT THIS HOW-TO ***
WINDOWS
What is needed:
* gParted / Ubuntu Live CD image
* Blank CD-R / WUBI for Ubuntu
* Software to burn a .iso image
* USB cable / card reader
1) Download the stable version of gparted Live CD (.iso) from here:
http://gparted.sourceforge.net/download.php (133.6 MB)
Or download Ubuntu (.iso) Live CD, which is always good to have:
http://www.ubuntu.com/download/ubuntu/download (685,29 MB)
If you already have an Ubuntu image good for you !
2) Once downloaded Burn it using your favorite burning software (i use Ultra ISO), it will burn as bootable by default.
If you don't have a blank CD-R and want to give ubuntu a try you can install it with WUBI on windows as any other program.
3) Restart your computer and enter to the BIOS (usually by pressing F2/del) ,in boot menu change the boot order to bring your CD drive on the top and then exit saving changes with F10
4) Once your computer restarts, it will boot from the CD and you will see some weird lines on ur screen, the you'll come to a page where u have 4 options, select the 1st one.
5) Once started it will ask you for preferred language, select ur language by typing the numbers given and hit enter, after that it will again give u 3 options PRESS 0 AND HIT ENTER
-----U Will get a blurred screen now bt dont worry -------
6) Now u should have booted into gparted, wait for a dialog to open, then you would be able to see your computer's hardisks
7) Plug your phone to the pc & Turn on USB storage / put your sdcard inside a card reader and connect it to the pc
8) On the right-hand side top corner you can select to see ur SD card (dropdown list of all the storage devices connected to the PC)
9) After selecting the SD card you will see ur SD card in the main screen(along with the partitions, if any)
10) Right Click on you FAT32 SD card partition and then click Resize partition
11) A box will appear to resize the space for a new partition. Choose the size you want to make it (Just think about the size of EXT4 partition + 32 MB [recommendable] SWAP you want to give in the 'Free space following box'. Leave it as PRIMARY and then clik add.
12) Now you'll see 2 partitions, one FAT32 and the other one is unallocated, right click on the unallocated one and click new then type 32 in the free space following box, make sure its also on PRIMARY in the create as box, and then u can select any file system you want (EXT2,3,4) then click add
13) Now only 32 MB will be shown as unallocated. Right click on that and click new, don't change anything, except the file system box, select it as linux SWAP, then click add
14) Now click apply. Congratulations!!!!!!! You are done with the partitioning of your SD card!!!!
On the top left of your screen u can see an icon named as exit/turn off, click on it and then select reboot and click ok... ur pc will restart and boot to windows....
UBUNTU LINUX
What is needed:
* USB cable / card reader
The proceedment is almost the same as above, because gParted belongs to linux and Ubuntu already comes with gParted application so that means you are ready to go!
1) Plug your phone to the pc & Turn on USB storage / put your sdcard inside a card reader and connect it to the pc
2) Open Gparted > Right Click on you FAT32 SD card partition and then click Resize partition
3) A box will appear to resize the space for a new partition. Choose the size you want to make it (Just think about the size of EXT4 partition + 32 MB [recommendable] SWAP you want to give in the 'Free space following box'. Leave it as PRIMARY and then clik add.
4) Now you'll see 2 partitions, one FAT32 and the other one is unallocated, right click on the unallocated one and click new then type 32 in the free space following box, make sure its also on PRIMARY in the create as box, and then u can select any file system you want (EXT2,3,4) then click add
5) Now only 32 MB will be shown as unallocated. Right click on that and click new, don't change anything, except the file system box, select it as linux SWAP, then click add
6) Now click apply. Congratulations!!!!!!! You are done with the partitioning of your SD card!!!!

AutoBoot on Power not quite working

I am having some trouble getting my auto boot script to work. Doing an in-car install so power up on usb is critical.
The method im using is by editing /system/bin/lpm to execute a script.
I edited the lpm file to read as such:
Code:
#!/system/bin/sh
/system/bin/reboot
But the code doesn't execute as expected. The code works. BUT it boots into recovery mode (TWRP) Is there any shell command i can force a boot to regular system?

Well, almost 20 hours of pain but i found a solution!
For anyone else looking here is what worked:
Fresh install of Stock Lite v7
Extract the boot image. Load TWRP > Backup Boot. Then you will find this file \Internal Storage\TWRP\BACKUPS\***\***\boot.emmc.win
Rename the file to boot.img. Use Carliv+Image+Kitchen+Windows+v1.3 to extract the image.
Open ramdisk/init.rc
Search for on charger and add at the end of this section:
Code:
setprop ro.bootmode "normal"
setprop sys.powerctl "reboot"
Repack the image with the same tool. Copy back to device.
Install new boot.img with TWRP. Install > Install image
@Svan987 if you were curious

Method for root - OnePlus Nord N100 (BE2011 unlocked)

I have successfully rooted my OnePlus Nord N100 (BE2011) using stock boot.img file patched with Magisk.
Here I will attempt to provide a detailed guide.
This is for OnePlus Nord N100 version BE2011 (Carrier unlocked) bought in the US at Best Buy. The build number is 10.5.8.BE81AA (As of today June 29, 2021)
Carrier locked versions will not work with this method because the bootloader is locked.
NOTE: Please follow the details as I had soft bricked the phone a few times by installing the wrong version of boot.img In which case the phone would not work for calls / txt
**MAKE SURE THE EXTRACTED boot.img FILE IS FROM THE EXACT OTA .zip file that is installed with the "Local Upgrade" method as described in STEP 3)***
Luckily I was able to get it to factory default by using the MSM method posted here:
[OPN100][OOS 81AA/83BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
STEP 1- On a new phone the user may have to use the automatic update either through wifi or mobile data BEFORE using "Local Upgrade" method as the 'settings' icon (gear wheel) under 'Settings' - 'system update', may not be displayed.
STEP 2- Install OnePlus Drivers on PC. USB setting should be set to file transfer.
STEP 3- Download and Update to latest firmware from OnePlus using "Local Upgrade Method"
This will be the full firmware (About 2GB file) not the smaller "update file"
This is from and email from support at OnePlus which includes the link to the latest firmware
(As of today June 6, 2021):
Check this link:
Software Upgrade - OnePlus.com
Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.
www.oneplus.com
Download the software build for your device from the above page. Please back up your data before flashing your device.
**KEEP A COPY of the .zip file on the PC as it will be needed to extract the bootloader boot.img file**
Plug your phone into your computer and copy the downloaded .zip to your phone’s storage.
(At the root of Internal storage: BE2011>Internal shared storage) see below picture.
If you’re using a Mac, you can install Android File Transfer Android File Transfer for this operation.
After the .zip file is copied to your phone, go to 'Settings' - 'system update', click the 'settings' icon on the top right corner, choose 'Local upgrade', find the .zip file and click on 'Install' to confirm.
The update takes about a minute (depending upon the file size), once done reboot your device to boot into the latest Oxygen OS.
{
"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 4- Extract boot.img file from payload.bin
The firmware download is a .zip file. When unzipped on the PC there will be a large file called "payload.bin" In order to extract boot.img from payload.bin the user will need to use a python script called payload_dumper.py
In order to use the tools, there should be no proxy server and use "Administrator" account. (I had errors when using proxy server and my windows user account.)
4a - Install the latest Python from here: https://www.python.org/downloads/
On Python install select "Add Python 3.xx to PATH"
4b - Download payload dumper from here :
https://www.mediafire.com/file/pslxh616isribx6/payload_dumper.zip/file
4c Upon successful download, extract all the files inside the ZIP folder to the same location where you have installed Python.
4d Unzip the OnePlus firmware file .zip and copy payload.bin to the python folder ( This means that the folder will have Python, the Payload Dumper Tool, and the payload.bin file in the same place.)
4e- Open the folder in CMD and use command: python -m pip install protobuf
(this will download and install Protocol Buffers Google’s data interchange format)
4f- execute the following command: python payload_dumper.py payload.bin
The .img files should now be extracted to the "output" folder
STEP 5- Install Android SDK Platform-Tools on Your PC
5a - Enable developer options on phone in settings>about phone. tap on "build number" several times until it displays "you are now a developer"
5b - On phone go to settings>system>developer options and Enable USB debugging (in Windows Device manager there should show "ADB Interface" under USB devices. If not the OnePlus ADB drivers need to be installed)
5c - Install ADB on Windows
Download the platform-tools package for Windows from Google:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
We are going to need a location on the PC where the files could remain untouched, yet easily accessible. So extract the content of the downloaded “platform-tools-latest-windows.zip” file to C:\adb
5d- Connect phone with ADB
Go to the folder where the files are present (Example: C:\adb).
On an empty space inside this folder, press the SHIFT key and right-click. Select “Open command window here” or “Open PowerShell window here” from the menu that appears.
With the Android device connected to the PC using USB cable enter the following command to initiate the ADB connection:
adb devices
The phone will ask for permission. Select allow and click ok
enter the command again:
adb devices
This will show that the device is connected with ADB.
STEP 6- Unlock Bootloader ****THIS WILL WIPE ALL DATA FROM PHONE****
6a- On phone go to settings>system>developer options and enable "OEM unlocking"
NOTE OPTION WILL ONLY BE AVAILABLE WITH CARRIER UNLOCKED PHONE
6b- In CMD or Powershell use command : adb reboot bootloader
This will reboot the phone into fastboot mode
6c- enter command: fastboot devices
The phone should be displayed. This verifies the connection with fastboot driver
6d- enter command: fastboot oem unlock
The phone will now ask to confirm. Use the vol +/- numbers to navigate and power button to select "unlock bootloader"
6e- if the phone doesnt automatically reset use command : fastboot reboot
6f- on reboot the user will have to go through the factory "setup" again and enable developer options and USB debugging again (Steps 5a, 5b from above)
STEP 7- Install Magisk and patch boot.img file
7a- Download Magisk APK file from here: https://magiskmanager.com/go/download
7b- Copy the .apk file to phone and use file manager to run. (it will ask for permission)
7c- copy the file "boot.img" from the PC to the phone internal storage (output folder under Python Step 4f above)
7d- run Magisk app on phone
7e- Click "install" under the Magisk heading and check "select and patch a file"
7f- choose the boot.img file that was just copied to the phone
Magisk will now patch the boot.img file and show the file location. This may be in "Downloads" folder.
7g- Copy the patched magisk boot.img file back to the PC in the \adb folder. File name should be something like "magisk_patched-23000_XXXXX.img"
STEP 8 - Boot with magisk patched boot.img file
8a - use command prompt and enter command: adb devices
the device should be displayed
8b - enter command: adb reboot bootloader
phone will reboot in fastboot mode
8c - ensure connnetion with command : fastboot devices
device should be displayed
8d - Test boot image by executing command:
fastboot boot magisk_patched-XXXXXXX.img
This will only boot the image once! Make sure everything is working (e.g. WiFi, PHone Messaging doesn't work on wrong image)
Call your phone and txt and use WIFI to make sure all the communication features are working
Open the Magisk APP. It should show Magisk installed.
The device is now temporarily rooted.
STEP 9 - Flash Bootloader
9a - use command prompt and enter command: adb devices
the device should be displayed
9b - enter command: adb reboot bootloader
phone will reboot in fastboot mode
9c - ensure connnetion with command : fastboot devices
device should be displayed
9d - Flash boot image by entering command:
fastboot flash boot magisk_patched-XXXXXX.img

Did you have an issue with the phone updating itself recently? Mine auto installed without any prompts this morning, so I went through the process again of unbricking to 10.5.5, manually updating to 10.5.8, patching, rooting, and tried blocking all oneplus domains to prevent any updates. Then a couple hours later it randomly rebooted and installed an update again without any prompt. I check OnePlus's website and the most recent update is from June.

If only someone would post the OTA zip file! Please! My n100 updated overnight without warning and I lost root. I'd really like to get a hold of it so I could patch boot.img and get root back.
Does anyone know how to get the OTA zip file after the update has run? Any other ways to re-obtain root without flashing back to android 10? Any advice would be greatly appreciated!

I contacted one plus support and they asked me for IMEI number and proof of purchase. Then they sent me the link for the current firmware download (the complete zip not the update this file should be about 2GB).
I have posted the link that they sent me in the instructions above.
For this to work you have to let the unrooted stock phone download the OTA update the normal way in systemm settings.
Once it does that you will be able to flash it with the firmware from the zip file manually.
I have disabled all automatic updates and ever since i rooted it the update option in system settings is greyed out.
Hope this helps

alexspecht said:
I have successfully rooted my OnePlus Nord N100 (BE2011) using stock boot.img file patched with Magisk.
Here I will attempt to provide a detailed guide.
This is for OnePlus Nord N100 version BE2011 (Carrier unlocked) bought in the US at Best Buy. The build number is 10.5.8.BE81AA (As of today June 29, 2021)
Carrier locked versions will not work with this method because the bootloader is locked.
NOTE: Please follow the details as I had soft bricked the phone a few times by installing the wrong version of boot.img In which case the phone would not work for calls / txt
**MAKE SURE THE EXTRACTED boot.img FILE IS FROM THE EXACT OTA .zip file that is installed with the "Local Upgrade" method as described in STEP 3)***
Luckily I was able to get it to factory default by using the MSM method posted here:
[OPN100][OOS 81AA/83BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
STEP 1- On a new phone the user may have to use the automatic update either through wifi or mobile data BEFORE using "Local Upgrade" method as the 'settings' icon (gear wheel) under 'Settings' - 'system update', may not be displayed.
STEP 2- Install OnePlus Drivers on PC. USB setting should be set to file transfer.
STEP 3- Download and Update to latest firmware from OnePlus using "Local Upgrade Method"
This will be the full firmware (About 2GB file) not the smaller "update file"
This is from and email from support at OnePlus which includes the link to the latest firmware
(As of today June 6, 2021):
Check this link:
Software Upgrade - OnePlus.com
Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.
www.oneplus.com
Download the software build for your device from the above page. Please back up your data before flashing your device.
**KEEP A COPY of the .zip file on the PC as it will be needed to extract the bootloader boot.img file**
Plug your phone into your computer and copy the downloaded .zip to your phone’s storage.
(At the root of Internal storage: BE2011>Internal shared storage) see below picture.
If you’re using a Mac, you can install Android File Transfer Android File Transfer for this operation.
After the .zip file is copied to your phone, go to 'Settings' - 'system update', click the 'settings' icon on the top right corner, choose 'Local upgrade', find the .zip file and click on 'Install' to confirm.
The update takes about a minute (depending upon the file size), once done reboot your device to boot into the latest Oxygen OS.
View attachment 5351013
STEP 4- Extract boot.img file from payload.bin
The firmware download is a .zip file. When unzipped on the PC there will be a large file called "payload.bin" In order to extract boot.img from payload.bin the user will need to use a python script called payload_dumper.py
In order to use the tools, there should be no proxy server and use "Administrator" account. (I had errors when using proxy server and my windows user account.)
4a - Install the latest Python from here: https://www.python.org/downloads/
On Python install select "Add Python 3.xx to PATH"
4b - Download payload dumper from here :
https://www.mediafire.com/file/pslxh616isribx6/payload_dumper.zip/file
4c Upon successful download, extract all the files inside the ZIP folder to the same location where you have installed Python.
4d Unzip the OnePlus firmware file .zip and copy payload.bin to the python folder ( This means that the folder will have Python, the Payload Dumper Tool, and the payload.bin file in the same place.)
4e- Open the folder in CMD and use command: python -m pip install protobuf
(this will download and install Protocol Buffers Google’s data interchange format)
4f- execute the following command: python payload_dumper.py payload.bin
The .img files should now be extracted to the "output" folder
View attachment 5351027
STEP 5- Install Android SDK Platform-Tools on Your PC
5a - Enable developer options on phone in settings>about phone. tap on "build number" several times until it displays "you are now a developer"
5b - On phone go to settings>system>developer options and Enable USB debugging (in Windows Device manager there should show "ADB Interface" under USB devices. If not the OnePlus ADB drivers need to be installed)
5c - Install ADB on Windows
Download the platform-tools package for Windows from Google:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
We are going to need a location on the PC where the files could remain untouched, yet easily accessible. So extract the content of the downloaded “platform-tools-latest-windows.zip” file to C:\adb
5d- Connect phone with ADB
Go to the folder where the files are present (Example: C:\adb).
On an empty space inside this folder, press the SHIFT key and right-click. Select “Open command window here” or “Open PowerShell window here” from the menu that appears.
With the Android device connected to the PC using USB cable enter the following command to initiate the ADB connection:
adb devices
The phone will ask for permission. Select allow and click ok
enter the command again:
adb devices
This will show that the device is connected with ADB.
STEP 6- Unlock Bootloader ****THIS WILL WIPE ALL DATA FROM PHONE****
6a- On phone go to settings>system>developer options and enable "OEM unlocking"
NOTE OPTION WILL ONLY BE AVAILABLE WITH CARRIER UNLOCKED PHONE
6b- In CMD or Powershell use command : adb reboot bootloader
This will reboot the phone into fastboot mode
6c- enter command: fastboot devices
The phone should be displayed. This verifies the connection with fastboot driver
6d- enter command: fastboot oem unlock
The phone will now ask to confirm. Use the vol +/- numbers to navigate and power button to select "unlock bootloader"
6e- if the phone doesnt automatically reset use command : fastboot reboot
6f- on reboot the user will have to go through the factory "setup" again and enable developer options and USB debugging again (Steps 5a, 5b from above)
STEP 7- Install Magisk and patch boot.img file
7a- Download Magisk APK file from here: https://magiskmanager.com/go/download
7b- Copy the .apk file to phone and use file manager to run. (it will ask for permission)
7c- copy the file "boot.img" from the PC to the phone internal storage (output folder under Python Step 4f above)
7d- run Magisk app on phone
7e- Click "install" under the Magisk heading and check "select and patch a file"
7f- choose the boot.img file that was just copied to the phone
Magisk will now patch the boot.img file and show the file location. This may be in "Downloads" folder.
7g- Copy the patched magisk boot.img file back to the PC in the \adb folder. File name should be something like "magisk_patched-23000_XXXXX.img"
STEP 8 - Boot with magisk patched boot.img file
8a - use command prompt and enter command: adb devices
the device should be displayed
8b - enter command: adb reboot bootloader
phone will reboot in fastboot mode
8c - ensure connnetion with command : fastboot devices
device should be displayed
8d - Test boot image by executing command:
fastboot boot magisk_patched-XXXXXXX.img
This will only boot the image once! Make sure everything is working (e.g. WiFi, PHone Messaging doesn't work on wrong image)
Call your phone and txt and use WIFI to make sure all the communication features are working
Open the Magisk APP. It should show Magisk installed.
The device is now temporarily rooted.
STEP 9 - Flash Bootloader
9a - use command prompt and enter command: adb devices
the device should be displayed
9b - enter command: adb reboot bootloader
phone will reboot in fastboot mode
9c - ensure connnetion with command : fastboot devices
device should be displayed
9d - Flash boot image by entering command:
fastboot flash boot magisk_patched-XXXXXX.img
Click to expand...
Click to collapse
Bro ..This is too much am lost,why don't they have this phone listed on Twrp sites?Can't i install twrp recovery on this N100

alexspecht said:
I have successfully rooted my OnePlus Nord N100 (BE2011) using stock boot.img file patched with Magisk.
Here I will attempt to provide a detailed guide.
This is for OnePlus Nord N100 version BE2011 (Carrier unlocked) bought in the US at Best Buy. The build number is 10.5.8.BE81AA (As of today June 29, 2021)
Carrier locked versions will not work with this method because the bootloader is locked.
NOTE: Please follow the details as I had soft bricked the phone a few times by installing the wrong version of boot.img In which case the phone would not work for calls / txt
**MAKE SURE THE EXTRACTED boot.img FILE IS FROM THE EXACT OTA .zip file that is installed with the "Local Upgrade" method as described in STEP 3)***
Luckily I was able to get it to factory default by using the MSM method posted here:
[OPN100][OOS 81AA/83BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
STEP 1- On a new phone the user may have to use the automatic update either through wifi or mobile data BEFORE using "Local Upgrade" method as the 'settings' icon (gear wheel) under 'Settings' - 'system update', may not be displayed.
STEP 2- Install OnePlus Drivers on PC. USB setting should be set to file transfer.
STEP 3- Download and Update to latest firmware from OnePlus using "Local Upgrade Method"
This will be the full firmware (About 2GB file) not the smaller "update file"
This is from and email from support at OnePlus which includes the link to the latest firmware
(As of today June 6, 2021):
Check this link:
Software Upgrade - OnePlus.com
Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.
www.oneplus.com
Download the software build for your device from the above page. Please back up your data before flashing your device.
**KEEP A COPY of the .zip file on the PC as it will be needed to extract the bootloader boot.img file**
Plug your phone into your computer and copy the downloaded .zip to your phone’s storage.
(At the root of Internal storage: BE2011>Internal shared storage) see below picture.
If you’re using a Mac, you can install Android File Transfer Android File Transfer for this operation.
After the .zip file is copied to your phone, go to 'Settings' - 'system update', click the 'settings' icon on the top right corner, choose 'Local upgrade', find the .zip file and click on 'Install' to confirm.
The update takes about a minute (depending upon the file size), once done reboot your device to boot into the latest Oxygen OS.
View attachment 5351013
STEP 4- Extract boot.img file from payload.bin
The firmware download is a .zip file. When unzipped on the PC there will be a large file called "payload.bin" In order to extract boot.img from payload.bin the user will need to use a python script called payload_dumper.py
In order to use the tools, there should be no proxy server and use "Administrator" account. (I had errors when using proxy server and my windows user account.)
4a - Install the latest Python from here: https://www.python.org/downloads/
On Python install select "Add Python 3.xx to PATH"
4b - Download payload dumper from here :
https://www.mediafire.com/file/pslxh616isribx6/payload_dumper.zip/file
4c Upon successful download, extract all the files inside the ZIP folder to the same location where you have installed Python.
4d Unzip the OnePlus firmware file .zip and copy payload.bin to the python folder ( This means that the folder will have Python, the Payload Dumper Tool, and the payload.bin file in the same place.)
4e- Open the folder in CMD and use command: python -m pip install protobuf
(this will download and install Protocol Buffers Google’s data interchange format)
4f- execute the following command: python payload_dumper.py payload.bin
The .img files should now be extracted to the "output" folder
View attachment 5351027
STEP 5- Install Android SDK Platform-Tools on Your PC
5a - Enable developer options on phone in settings>about phone. tap on "build number" several times until it displays "you are now a developer"
5b - On phone go to settings>system>developer options and Enable USB debugging (in Windows Device manager there should show "ADB Interface" under USB devices. If not the OnePlus ADB drivers need to be installed)
5c - Install ADB on Windows
Download the platform-tools package for Windows from Google:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
We are going to need a location on the PC where the files could remain untouched, yet easily accessible. So extract the content of the downloaded “platform-tools-latest-windows.zip” file to C:\adb
5d- Connect phone with ADB
Go to the folder where the files are present (Example: C:\adb).
On an empty space inside this folder, press the SHIFT key and right-click. Select “Open command window here” or “Open PowerShell window here” from the menu that appears.
With the Android device connected to the PC using USB cable enter the following command to initiate the ADB connection:
adb devices
The phone will ask for permission. Select allow and click ok
enter the command again:
adb devices
This will show that the device is connected with ADB.
STEP 6- Unlock Bootloader ****THIS WILL WIPE ALL DATA FROM PHONE****
6a- On phone go to settings>system>developer options and enable "OEM unlocking"
NOTE OPTION WILL ONLY BE AVAILABLE WITH CARRIER UNLOCKED PHONE
6b- In CMD or Powershell use command : adb reboot bootloader
This will reboot the phone into fastboot mode
6c- enter command: fastboot devices
The phone should be displayed. This verifies the connection with fastboot driver
6d- enter command: fastboot oem unlock
The phone will now ask to confirm. Use the vol +/- numbers to navigate and power button to select "unlock bootloader"
6e- if the phone doesnt automatically reset use command : fastboot reboot
6f- on reboot the user will have to go through the factory "setup" again and enable developer options and USB debugging again (Steps 5a, 5b from above)
STEP 7- Install Magisk and patch boot.img file
7a- Download Magisk APK file from here: https://magiskmanager.com/go/download
7b- Copy the .apk file to phone and use file manager to run. (it will ask for permission)
7c- copy the file "boot.img" from the PC to the phone internal storage (output folder under Python Step 4f above)
7d- run Magisk app on phone
7e- Click "install" under the Magisk heading and check "select and patch a file"
7f- choose the boot.img file that was just copied to the phone
Magisk will now patch the boot.img file and show the file location. This may be in "Downloads" folder.
7g- Copy the patched magisk boot.img file back to the PC in the \adb folder. File name should be something like "magisk_patched-23000_XXXXX.img"
STEP 8 - Boot with magisk patched boot.img file
8a - use command prompt and enter command: adb devices
the device should be displayed
8b - enter command: adb reboot bootloader
phone will reboot in fastboot mode
8c - ensure connnetion with command : fastboot devices
device should be displayed
8d - Test boot image by executing command:
fastboot boot magisk_patched-XXXXXXX.img
This will only boot the image once! Make sure everything is working (e.g. WiFi, PHone Messaging doesn't work on wrong image)
Call your phone and txt and use WIFI to make sure all the communication features are working
Open the Magisk APP. It should show Magisk installed.
The device is now temporarily rooted.
STEP 9 - Flash Bootloader
9a - use command prompt and enter command: adb devices
the device should be displayed
9b - enter command: adb reboot bootloader
phone will reboot in fastboot mode
9c - ensure connnetion with command : fastboot devices
device should be displayed
9d - Flash boot image by entering command:
fastboot flash boot magisk_patched-XXXXXX.img
Click to expand...
Click to collapse
My N100 build no. is Oxygen Os 10.5.10.BE83BA can i update and root my phone with the same firmware?

Wanted to drop in and thank the OP for this. The steps worked like a charm. I even powered off the phone and booted back up to insure Root was successfully implemented.
I installed Package Manager and successfully removed all the bloatware and tracking apps phone manufacturers love to refuse to allow to you remove. I'm not a power user like alot of root people, I just want a clean and private experience on my phone. I don't even sign into a Google account with my phones, that's how privacy conscious I am.
My last few phones were HTC because they made is very easy to unlock the bootloader and play around. It's sad they're not making phones anymore, but when I heard OnePlus was bootloader friendly, I decided to check them out and I'm glad I did.
So, thank you again!

So for anyone like me who had a mini panic attack when they got the notice to update to build 11.0.1.BE81AA, it did not break root, deactivate developer options, or lock the bootloader. The update was successful, and as far as I can tell, I still have root.
Though, I wouldn't mind re-locking the bootloader now that I'm rooted. The option is greyed out in Developer options. It's not a big deal, except for the annoying warning message and a few seconds delay when rebooting.

jtl2dotnet said:
So for anyone like me who had a mini panic attack when they got the notice to update to build 11.0.1.BE81AA, it did not break root, deactivate developer options, or lock the bootloader. The update was successful, and as far as I can tell, I still have root.
Though, I wouldn't mind re-locking the bootloader now that I'm rooted. The option is greyed out in Developer options. It's not a big deal, except for the annoying warning message and a few seconds delay when rebooting.
Click to expand...
Click to collapse
Amigo,como le hiciste?
Yo tengo la misma actualización pero no logro sacar el boot.img

Okay, time for an update. I can officially confirm that upgrading to 11.0.1.BE81AA does break root. One of the apps I used appeared to be working in fact, but it really wasn't. It didn't give any error messages that I could see, the app appeared to work as normal but actually wasn't doing anything. Thinking it must be broken root, I downloaded a root checker and that confirmed it.
Again: upgrading to 11.0.1.BE81AA breaks root.
I checked OnePlus' website and they not released the zip file for this release yet. I am hoping that once they do, these steps will work by simply using the boot.img from the 11.0.1.BE81AA zip, but until it's officially released I don't know of way to test it.
If anyone has gotten 11.0.1.BE81AA rooted, I would be interested to know.

My device automatically upgraded to 11.0.1.BE81AA. It is in android 11. Please help me. I want to Root.

OK, for those of you that had a problem with One Plus pushing the 11.0.1.BE81AA android 11 update to your phone and are still struggling, I will post what I did. Just follow the instructions from the previous several messages above, and use the boot.img file you can find at link to repo . I used the file named "OnePlusN100Oxygen_14.O.21_GLO_0210_2107241056" (AKA "f0ca210dff1c162c3c4a68f2560ef50898ac1797.zip" and the tool "payload_dumper-win64.zip". ISInce I already had Magisk on my phone and just just lost root, I followed the instructions posted in post #1 in this thread (thanks, alexspecht for the detailed instructions!) starting with step 7.
To summarize: WARNING, I BEAR NO RESPONSIBILITY IF YOU DAMAGE OR RENDER YOUR DEVICE UNUSABLE:
1. I unpacked the boot.img, and copied it to my phone.
2. I used Magisk to patch it
3. I copied the patched boot.img file to my platform tools folder on my windows PC.
4. I skipped step 8 and jumped right to step 9
5. I used a command window to send "adb devices" to my phone to verify connection
5. I then issued the "adb boot bootloader" command, and authorized my device when asked.
6. Next, i entered "fastboot devices"
7. And finally I issued the "fastboot flash boot magisk_patched-XXXXXX.img" command
8. and rebooted by selecting "Start" on my phone screen.
I knew it was working when I saw the live boot screen I use instead of the standard oneplus boot sequence.
Once again, thank you, @alexspecht !

Glad to see people found this useful. They dont make it easy anymore.
As far as the OTA push thats been breaking peoples phone:
If you disable google play services the update will not come through.
The update uses wifi to download, so luckily I was not connected to wifi when the update came in.
so if you need google play services make sure your not on wifi. So far they havent broken my phone, sorry thats the best I could do.

I can confirm that repeating the steps in the OP with the EU 11.0.0.0 ROM (OnePlusN100Oxygen_14.E.20_GLO_0200_2106222205) successfully resulted in root.

I was able to successfully root my oneplus N100 BE2011 i checked my text messages and they work but my calls dont come in, when i try to make a phone call the phone freezes up, i completed the root process and disabled auto updates. Sucks the phone does not work i cant make any calls but atleast im rooted ?

Is there a way to update to 10.5.8.BE81AA using the downloaded payload with an MSM tool?
This would save all the time of updating via auto-downlaod update, then moving the file to the phone, then doing manual local update.

alexspecht said:
STEP 1- On a new phone the user may have to use the automatic update either through wifi or mobile data BEFORE using "Local Upgrade" method as the 'settings' icon (gear wheel) under 'Settings' - 'system update', may not be displayed.
Click to expand...
Click to collapse
This is correct, there's no `settings` icon unless you do the update. BUT when you do the update, now you're in android 11 and they won't let you downgrade: "The version of your selected package is lower than that of the current system. To avoid booting up failure, downgrading is not allowed."
So I'm not sure how to make your guide work, given this.

Wish the n200 had this much development

I did this and have root access verified. But now everytime I try to get SU in adb it automatically denies access. Any ideas?

Is there a way to save a modified boot image from within the booted ROM which is rooted with magisk

I don't have the original boot.img. I want to unroot temporarily. But want to re-root afterward.
I was wondering if I can save a modified_boot.img somehow and flash that later once I am done. Is it possible?

devsk said:
I don't have the original boot.img. I want to unroot temporarily. But want to re-root afterward.
I was wondering if I can save a modified_boot.img somehow and flash that later once I am done. Is it possible?
Click to expand...
Click to collapse
What ROM and device are you using?
How did you root it in the first place?
What OS are you running?

Heres my 30 second version of how id do it on my Pixel 2 XL an a/b device....ymmv, depending on device
Download latest platform tools from Google for your OS, if necessary: https://developer.android.com/studio/releases/platform-tools
Next you'll need dd, if you're on Linux, you can skip ahead
For Windows....go to http://gnuwin32.sourceforge.net/packages/coreutils.htm
Download Binaries & Dependencies zips
Extract dd.exe from coreutils-5.3.0-bin.zip /bin to platform tools path
Extract all .dll's from coreutils-5.3.0-dep.zip /bin to platform tools path
Enable USB Debugging & ABD access on device
Boot device to recovery (usually TWRP)
on PC and prompt in platform tools folder:
if you have recovery (usually TWRP) installed:
adb reboot recovery
if you DONT have recovery (usually TWRP) installed, but instead fastboot it via bootloader (as i do on my Pixel 2XL):
adb reboot bootloader
fastboot boot twrp-xxx.img
swipe into twrp
back to PC prompt:
adb shell
dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
adb pull /sdcard/boot.img magisk_boot.img
Uninstall magisk
When you need to flash magisk boot image back:
Boot to bootloader..
on PC and prompt in platform tools folder:
adb reboot bootloader
fastboot flash boot magisk_boot.img
fastboot reboot
Note: You can of course use the same first process to backup (and extract) the stock boot.img before rooting ....and the latter to reflash it if needed if rooting goes wrong

Sorry, I should update my profile. My device is OnePlus 8 Pro.
> dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/magisk_boot.img
@73sydney why would this not work from within a rooted device? Its not like some process is holding a read lock on that partition or something else is also writing to it. Its a partition persisted in the NAND, which is not being touched by anything.
The only thing is that there are 2 partitions on the NAND: boot_a and boot_b. I need to know which one is the current one.
And this tells me slot B:
cat /proc/cmdline | tr ' ' '\n' | grep --color slot
androidboot.slot_suffix=_b
For flashing back, I obviously need to be in bootloader because I won't have the root to write to the partition.

[GUIDE] Installing Lineage 18.1 (& more) [X00H] [X00I]

In this guide, i'm going to be a bit straightforward on how to install LOS 18.1 on your X00H/X00I device.
For the process, you need:
Your X00H/X00I device;
The following must be unlocked (if you didn't, you can follow the howto over my post);
A rooted phone/tablet with Magisk (any ADB & Fastboot tool is fine, but i suggest using this for simplicity);
In case you have none of the above, even a PC or Laptop with ADB and Fastboot binaries installed will suffice;
If you're on Windows, you can get the installer over GitHub;
If you're on Linux, hop into your package manager and install them via terminal (the following example will be for Debian/Deb-based/Ubuntu/Ubuntu-based distros. If you're on Arch, Fedora, etc.: just search for "fastboot" by using the respective pkg manager's search flag, then install it basing from the name it's repo gives):
Code:
sudo apt install fastboot
An USB cable (should come into the device's box, also must be capable of data transfering);
If you're going to do the process via a rooted device, the Asus device should come in it's packaging with an OTG adapter (be sure to attach the following to the rooted device);
PBRP (Pitch Black Recovery Project) for the device- OG post can be checked here;
Latest version for X00H;
Latest version for X00I;
If your device is an X00I, you can alternatively get TWRP instead;
The Android 9 Beta update (you MUST have the device updated to that version, else you'll risk the device to be bricked- for more info, check the OG post by Seba);
If you want to flash it via stock recovery, you can get the file over ASUS' site on the device;
Download for the X00H;
Download for the X00I;
If you have already flashed a custom recovery on your device, you can get the "custom recovery flashable zip"over SebaUbuntu's site;
.zip file for the X00H;
.zip file for the X00I;
Tiny discalimer on the flashable .zip above: once installed, your device's recovery will be replaced to stock (in other words, you'll lose the custom recovery);
The Lineage OS 18.1 rom and recovery (credits to @miya0405 for finding the site);
ROM and LOS Recovery for the X00H;
ROM and LOS Recovery for the X00I;
If you have all of the things required in the list, let's go!
--------------------------------------------------------------
Installing the Android 9 BetaStock Recovery method:
Download the Android 9 Beta over ASUS' site (any device is fine, even using the phone itself);
Put an SDCard inside the device;
Move the .zip file inside the SDCard;
Turn off the device;
Boot into recovery (do Power + Vol.up combo- if your device's unlocked, tap on the volume button and select "Recovery" by pressing on the power button to confirm);
Select "Update from sd card";
Select the .zip file you've downloaded;
Wait for the update to install;
After updated, go back and select "Power off";
Custom Recovery Method:
Download the Android 9 Beta flashable .zip over SebaUbuntu's site;
Put an SDCard inside the device;
Move the .zip file inside the SDCard;
Turn off the device;
Boot into recovery;
Select "Install";
Select the "External Memory" storage;
Search for the .zip file inside the SDCard;
Tap on it and install it, unchecking everything;
Swipe to continue and let the .zip file install;
The recovery will print you text on the progress (also gives advice on what to do after install);
Reboot to system;
Power off the device;
----------------------------------------------------------------
Unlocking the device:Just a tiny reminder if you haven't yet, check my guide about it: then, resume from this point and proceed;
----------------------------------------------------------------
!!A word of advice!!Don't install PBRP recovery just yet!
If you'll pick PBRP instead of the LOS recovery as the custom recovery of choice, flashing LOS 18.4 with it should make Lineage 100% unbootable and stuck in a bootloop!
Don't reboot back to PBRP if bootloops happen:
neither don't fix the "Cache" partiton with it, else it'll cripple more Lineage and redirect the boot to recovery or fastboot/bootloader!
TL;DR: Don't do my same mistake and flash the recovery partition with the wrong recovery (on the bright side, the device will still be salvageable).
----------------------------------------------------------------
Flashing Lineage Recovery:Before proceeding, do the following firsthand:
Be sure to have the ADB & Fastboot binaries installed;
Your device rebooted to fastboot/bootloader mode (any method is acceptable);
Must have downloaded the recovery for your specific model (links are on the "required" list);
The device must be connected to the host machine (if you're using a rooted phone, be sure to have the OTG adapter connected to it first);
Rooted Android Device Method:
Open the "ADB & Fastboot"tools of your choice;
Whether it is a terminal or the app i've suggested earlier: this portion will purely give instructions if you have the app;
If you're going to do the process via terminal, then jump to the "Linux Method" instead;
If it is the first time you open the tool, it should ask for root perms.- allow them;
Tap on the top right corner of the UI;
Tap on "Fastboot";
Tap on "Refresh";
Go to the "Partition" title, next to it you should see a dropdown menu;
Select "recovery";
Tap on the "Flash" button;
A file manager should open: search where the lineage recovery is (typically you can find it in the "Download" folder. The file should be called "recovery.img");
After selected, the app will automatically flash the recovery for you;
Disconnect the device;
Navigate over your Asus device with the volume buttons;
Select "Reboot recovery" and confirm with the power button;
Hooray, you have LOS Recovery installed;
Linux Method:
Open the terminal (use the shortcut CTRL+ALT+T to open it, preferrably);
Do the following:
Code:
lsusb
# This checks if your asus device is connected proper to the machine
# If it is, lsusb should output something around a "Google" or "Qualcomm" device on the ID Bus
cd Downloads
# If you have put a different language locale, cd into the Downloads folder with it's localized name
ls
# List for the files inside the folder. You should see a file called 'recovery.img' inside
fastboot devices
# Tell fastboot to check if any device on bootloader/fastboot mode is connected
fastboot flash recovery recovery.img
# Gives fastboot the instruction to flash the .img file to the desired device's partition, which is the recovery in this case
After done flashing, disconnect the device;
Navigate over your Asus device with the volume buttons;
Select "Reboot recovery" and confirm with the power button;
Hooray, you have LOS Recovery installed;
Windows Method:GUI Method:
Simply use the "Latest ADB Launcher"executable located on the desktop of your PC;
Just make sure to flash the recovery partition with the "recovery.img" file;
Terminal Method:
Navigate with the File Explorer;
Go to your Downloads folder and find for a file called "recovery.img";
Cut and paste it to where the ADB and Fastboot tools are installed at;
Click on your mouse's right button;
Select "Open terminal here" over the contextual menu;
A terminal should pop-up (Command Prompt, that is);
Type in the following:
Code:
fastboot devices
fastboot flash recovery recovery.img
Wait for the recovery to flash on the device;
After done so, disconnect the device;
Navigate over your Asus device with the volume buttons;
Select "Reboot recovery" and confirm with the power button;
Hooray, you have LOS Recovery installed;
------------------------------------------------------------
Installing Lineage OS 18.1:Before proceeding, do the following firsthand:
Your device must be turned off;
Must have deleted the Android 9 Beta .zip file from the SDCard, for avoiding accidents;
Download the Lineage file off of the "required" list's links for your specific model;
Put the downloaded .zip file on an SDCard;
Insert the SDCard inside the device's slot;
Boot up into recovery mode;
Select with the volume keys "Apply Update" > "Apply from sdcard" and confirm with the power button;
Select the LineageOS .zip file;
Confirm with the power button;
Let the rom install by the recovery;
After install, navigate to the back button with the volume keys;
Select "Factory reset" > "Format cache partition";
The recovery will ask you the following:
Code:
Format Cache?
THIS CAN'T BE UNDONE!
Select "Yes";
Go back;
Select "Reboot system now";
First bootup will take some while, but you'll be greeted by the setup screen in no time.
Congratz, now your device has Lineage OS installed!
-------------------------------------------------------------------
Extras/FAQ Section:Q: Is it possible to get root priviledges on the device?A: Sure! There are different ways to apply root on the ROM, but feel free to pick whichever method you like:
Rooting your device by picking it's 'boot.img' (exactly located on the folder of the respective model) over SebaUbuntu's Lineage site and patch it with an already-rooted device that has the Magisk companion app installed (requires no recovery patching, but it is required to boot the asus device in fastboot mode and patch the boot partition);
Downloading the Magisk companion app over it's GitHub page, rename the .apk file by replacing '.apk' to '.zip' via file manager, patch PBRP over the recovery partition (with one of the methods listed over 2 titles above this one), and install the 'magisk.zip' file like you could usually do on any other device with custom recovery;
If you use an X00I device, you can preferrably install TWRP from here instead of PBRP;
After applied root on the device, patch back on the device the Lineage recovery- just for avoiding any inconvenience if you want to factory reset the device;
Q: My device has Lineage installed, but the bottom buttons don't work. Is there a way to enable a virtual navbar?A: Yep, but it's a bit of a tricky process. You must have either apps like Terminal Emulator or Termux installed for making this work- as an extra, you could get other keyboards like BeHe Keyboard or Hacker's Keyboard: but that is only if you've picked Terminal Emulator as your choice.For direct instructions, follow this (you must be inside the terminal app of your choice and already gave storage perms to it firsthand):
Code:
su
mount -o rw,remount /
vi /system/build.prop
# After come this far, go to the bottom of the build.prop file by scrolling with the touch screen
# On your keyboard, press the I key. This should make vi enter into INSERT mode
# When done so, add the following line on the build.prop file
qemu.hw.mainkeys=0
# For getting out of INSERT mode, find on your keyboard or terminal UI the ESC button
# For quitting and saving the file on vi, type the following
:wq!
# This should make vi quit and save the modifications to the build.prop file
# For rebooting the device straight from the terminal, just type in
reboot
# The device should immediately reboot, and upon unlocking: the virtual navbar should appear
Q: Can it be possible installing MicroG on the device?A: You can! Every method for installing MicroG perfectly works on this ROM;
Q: I have MicroG installed on my device, but i want to apply signature spoofing for extra functionality. Is this possible?A: Sadly, due to the tinkering i've done on my side: the ROM gets a meltdown when modifying the 'services.jar' file is involved (root or non-root). If you follow some guides online (despite being few), the ROM, regardless of what you do or which method you follow: it will end up in a bootloop (or, to be more specific, the SystemUI starts to become picky);
------------------------------------------------------------------
Credits:
miya0405 (for the lineage site)
SebaUbuntu (for the LOS rom, recovery, and PBRP recovery)
Erwin Abs (PBRP Recovery)
aaaaaaziskurnia (TWRP recovery for the X00I)
You, for dedicating your time on reading this long guide!

Database Develop

welcome