Related
*Download all necessary files*
Magisk v15.0 or newest available
Download ElementalX kernel @ elementalx.org
Download latest Magisk Manager from official xda thread
Download TWRP for Moto G4 (Athene)
from twrp.me
Unlock bootloader (Go to Motorola's official site)
Check Unknown Sources in Android settings under security tab.
Download and install ADB & Fastboot on your PC
Boot into fastboot by holding down vol down and power.
Once you see Android robot with text at the bottom, on your computer in cmd type "fastboot boot TWRP image path" ex: fastboot boot D:/TWRPimages/twrp.athene.img
Once phone boots to TWRP, TWRP will ask to make modifications to system. Keep read only. (Note: if is asks to install, always say no.) Next go to backup, and make backup. (Just backup what is selected by default: system, data, and most importantly, boot.img) Note: make sure to tell it to backup to SD, and make sure the SD card is formatted as portable, not adoptable. Note: you might need mount the card under Mount tab first before being able to select it.
Next, go to mount, and uncheck "keep system read only", and swipe to allow modifications. Go to install, and flash ElementalX, and set it up in the following screen. As we already have the turbopower charger, you don't need to enable USB fast charging.
Wipe dalvik cache, and flash Magisk. Then, wipe dalvik again, and power off.
Boot into Android to make sure everything works. Install Magisk app if it didn't appear in your apps drawer from the .apk you downloaded earlier.
Hope this helps! Good luck!
Note: If you would like to flash TWRP instead, use "fastboot flash recovery TWRP.img" instead of fastboot boot.
Thank you for this tutorial! Is it required to install the ElementalX kernel?
Romano2K said:
Thank you for this tutorial! Is it required to install the ElementalX kernel?
Click to expand...
Click to collapse
It appears to be. I tried it without ElementalX first and got to the point of installing Magisk then rebooting before my G4 went to brick with the flashing light. Same behavior occurred when installed SuperSU. After installing ElementalX everything worked fine.
To supplement this guide, here are a few more links and notes of what I did.
Links
The December 2017 Nougat ROM from here
G4 compatible Shreps TWRP from here
Current Magisk here
ElementalX for G4 is here
If needed, install Platform Tools and Android File Transfer
Steps
Install the ROM using these commands (on Mac):
./fastboot flash partition gpt.bin
./fastboot flash bootloader bootloader.img
./fastboot flash logo logo.bin
./fastboot flash boot boot.img
./fastboot flash recovery ./twrp-3.1.1-athene_shreps.img
./fastboot flash dsp adspso.bin
./fastboot flash oem oem.img
./fastboot flash system system.img_sparsechunk.0
./fastboot flash system system.img_sparsechunk.1
./fastboot flash system system.img_sparsechunk.2
./fastboot flash system system.img_sparsechunk.3
./fastboot flash system system.img_sparsechunk.4
./fastboot flash system system.img_sparsechunk.5
./fastboot flash system system.img_sparsechunk.6
./fastboot flash system system.img_sparsechunk.7
./fastboot flash modem NON-HLOS.bin
./fastboot erase modemst1
./fastboot erase modemst2
./fastboot flash fsg fsg.mbn
./fastboot erase cache
./fastboot erase userdata
./fastboot erase customize
./fastboot erase clogo
Click to expand...
Click to collapse
After running commands, restart bootloader w/o rebooting
Go into recovery w/o rebooting
Reboot
After booting into the OS, turn on Developer Mode (tap About / Build Number 8 times)
Go to Developer Options and turn on OEM unlocking and USB debugging
Copy Magisk and ElementX kernel to / using Android File Transfer (if AFT doesn't connect select USB config, change to charging then back to MTP to enable file transfer)
Reboot into Recovery, then Install Magisk and ElementX from TWRP
Performed on an G4 XT-1625, resulted was a rooted Nougat.
@Sanras, I followed your instructions and they went great on a republic wireless xt1625, thank you! But your post just says to boot into twrp, which means if I ever want to use twrp I have to connect my computer. Is there a special way to flash twrp instead of just booting to it? Because I tried flashing twrp but the phone wouldn't boot afterward. So I had to flash the stock rom and redo everything. Let me know and thanks!
supermaxkato said:
@Sanras, I followed your instructions and they went great on a republic wireless xt1625, thank you! But your post just says to boot into twrp, which means if I ever want to use twrp I have to connect my computer. Is there a special way to flash twrp instead of just booting to it? Because I tried flashing twrp but the phone wouldn't boot afterward. So I had to flash the stock rom and redo everything. Let me know and thanks!
Click to expand...
Click to collapse
You should be able to flash TWRP. That's actually the most used method. I simply recommended booting and not flashing because it is easier to revert to stock for an update. However, you should be able to flash TWRP if you want with "fastboot flash recovery D:/TWRPimages/twrp.athene.img"
(Replace last part with image path on your computer)
Thanks Sanras,
Great guide, worked for me with no problems.
Anyone know how to approach security updates after rooting via this method?
Currently on Dec17 looking to update to Apr18 security patch just don't want to brick device.
Thanks in advance. :good:
Thanks. Sanras.
I got my phone bricked after restore my stock rom and try to install magisk to it. This solved my case also.
I just have to pay attention that just installing the kernel after try the magisk is not enough. Like you said:
* Install ElementalX kernel; wipe caches
* then install Magisk (again), and wipe caches again
Is this safe for Qualcomm variants like the Boost Mobile version?
chuman72486 said:
Is this safe for Qualcomm variants like the Boost Mobile version?
Click to expand...
Click to collapse
Yes, my own G4 is a Snapdragon 617 (unlocked US Variant) XT-1625
SD Card Configured Adoptable
Sanras said:
*Download all necessary files*
Magisk v15.0 or newest available
Download ElementalX kernel @ elementalx.org
Download latest Magisk Manager from official xda thread
Download TWRP for Moto G4 (Athene)
from twrp.me
Unlock bootloader (Go to Motorola's official site)
Check Unknown Sources in Android settings under security tab.
Download and install ADB & Fastboot on your PC
Boot into fastboot by holding down vol down and power.
Once you see Android robot with text at the bottom, on your computer in cmd type "fastboot boot TWRP image path" ex: fastboot boot D:/TWRPimages/twrp.athene.img
Once phone boots to TWRP, TWRP will ask to make modifications to system. Keep read only. (Note: if is asks to install, always say no.) Next go to backup, and make backup. (Just backup what is selected by default: system, data, and most importantly, boot.img) Note: make sure to tell it to backup to SD, and make sure the SD card is formatted as portable, not adoptable. Note: you might need mount the card under Mount tab first before being able to select it.
Next, go to mount, and uncheck "keep system read only", and swipe to allow modifications. Go to install, and flash ElementalX, and set it up in the following screen. As we already have the turbopower charger, you don't need to enable USB fast charging.
Wipe dalvik cache, and flash Magisk. Then, wipe dalvik again, and power off.
Boot into Android to make sure everything works. Install Magisk app if it didn't appear in your apps drawer from the .apk you downloaded earlier.
Hope this helps! Good luck!
Note: If you would like to flash TWRP instead, use "fastboot flash recovery TWRP.img" instead of fastboot boot.
Click to expand...
Click to collapse
My Moto G4 has an SD card formatted adoptable. Is there a work around in step 6 to accommodate an adoptable SD card?
Thanks
rwruck said:
My Moto G4 has an SD card formatted adoptable. Is there a work around in step 6 to accommodate an adoptable SD card?
Thanks
Click to expand...
Click to collapse
Sure. Instead of making a backup to the card, backup to internal storage. Then, before doing anything else, on your pc copy the files from the newly created TWRP folder on your internal storage. These are your backups. You can then proceed with the rest of the steps. Honestly, the backup isn't even necessary, it's just good to have in case something goes wrong.
Hi
I know it's a bit old now, but I'm unable to root my Nougat XT1641
I already have the whole stuff :
- BL unlocked ;
- TWRP installed ;
- all backups done.
But everytime I try to flash ElementalX/Magisk, it fails and ends in a bootloop.
Can someone have an advice to help me ?
Well, I used this : https://topjohnwu.github.io/Magisk/install.html#patching-images
Patching my boot.img did the trick !
# I assume you are confident with ADB and Fastboot commands and you know what you are doing. #
# If you don't, search on Google before messing with your device. #
# I am not responsible for...you know what I mean. On the other hand, please feel free to point out any error in this guide. #
# Lots of useful information can be found on Telegram Group for Mi 9 SE #
# If you already unlocked your bootloader and flashed TWRP, go directly to part 2 of this guide #
PART 1 - UNLOCK DEVICE AND FLASH TWRP
# Before starting, be sure that you can unlock your bootloader and you have these files: #
- Mi Unlock tool (http://en.miui.com/unlock/)
- Minimal ADB & Fastboot 1.4.3 (https://forum.xda-developers.com/showthread.php?t=2317790)
- TWRP recovery for your device (please check the development section).
Install ADB and Fastboot drivers on your PC, if you don't have them already.
- enable developer options on device, allow OEM unlock and ADB debug.
- install Minimal ADB & Fastboot tool and run a command window. PLEASE DON'T USE WINDOWS 10 POWER SHELL. Double click on "cmdhere.dll" in root folder instead.
- move twrp image in the same folder where Minimal ADB & Fastboot is installed.
- for your convenience, rename twrp file as "twrp" only.
- connect your device to your PC USB port, pair it with PC then reboot it to bootloader (power + volume down combo).
Unlock bootloader using Mi Unlock tool (full unlocking guide at https://c.mi.com/thread-1635834-1-1.html)
Unlocking bootloader will erase all of your data, including storage.
Once you unlocked:
- reboot and setup device
- enable developer options again
- double check bootloader status and allow ADB debug
- connect to USB port and pair device with PC for ADB debug bridge then type in command window:
Code:
adb devices
Code:
adb reboot bootloader
once in bootloader screen code:
Code:
fastboot devices
Code:
fastboot flash recovery twrp.img
- don't give fastboot command "fastboot boot recovery twrp" or "fastboot reboot recovery twrp". Just press and hold power+volume up for about 10 seconds to reboot to recovery.
- swipe to allow twrp modifications.
- I would suggest to NOT format data to get rid of encryption unless you actually need it. Encryption does not slow down your device or harm your battery life.
- I would also suggest to NOT wipe system and reboot to recovery because it could lead to a fastboot bootloop.
PART 2 - HOW TO FLASH A GSI ROM
# IMPORTANT #
When flashing a GSI ROM, it is recommended to use a Stable firmware as base.
If device is running different builds, flash latest Global or China Stable before starting using MiFlash tool.
Beware that device could have the anti-rollback enabled, so be careful when flashing another firmware.
Mi 9 SE is a system-as-root device, so you must flash A/B type GSI ROMs.
You will need these files:
- GSI A/B ROM (FlokoROM at https://treble.andro.plus/ or choose one at https://forum.xda-developers.com/project-treble/trebleenabled-device-development)
- vbmeta.img (https://androidfilehost.com/?fid=818070582850505317)
- gapps for Google services (https://opengapps.org/) - select ARM64 - 9.0 - I would suggest nano or pico package.
- magisk for root and modules (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
- MiFlash flashable STABLE stock firmware (http://en.miui.com/download or https://mirom.ezbox.idv.tw/en/phone/grus/)
- MiFlash tool (https://www.xiaomiflash.com/)
If you are already running a Stable firmware start from here, if you don't, flash a Stable firmware.
- move GSI and vbmeta images in the same folder where Minimal ADB & Fastboot is installed.
- for your convenience, rename GSI file as "system" only.
- reboot device to bootloader, ensure you are connected with your PC properly
- to double check it, run a command window and type:
Code:
fastboot devices
once you get the device recognized type:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
this command will disable dm-verity and AVB on device. PLEASE DON'T USE WINDOWS 10 POWER SHELL to disable vbmeta or you will get an error feedback. Double click on "cmdhere.dll" in root folder instead.
then:
Code:
fastboot flash system system.img
this command will flash system.img
Code:
fastboot -w
this command will wipe data on device
Reboot your device in recovery using button combo and resize system partition to install Gapps.
From TWRP Wipe menu > advanced wipe > system > repair or change file system > resize system > swipe to resize
- move magisk and gapps from PC to device
- go to mount menu and tick mount system
- go back to install menu and flash gapps
- once you flashed gapps unmount system
- go to install and flash magisk
- go to wipe menu and swipe for factory reset
- reboot
once rebooted, complete the device setup.
be aware that some GSI could bootloop or not boot at all even if you followed the guide properly.
in case rely on GSI devs for assistance or fixes.
Of course you can flash a GSI ROM using TWRP.
The only fastboot command you need to perform is to disable dm-verity and AVB.
If you already disabled it while flashing TWRP for the first time, you can follow these steps to flash a GSI using TWRP:
- Tap on advanced Wipe menu and wipe cache, dalvik, data and system
- Tap on Install > Install Image > select image and flash it to system
- Install Gapps with the same process shown above.
- Swipe for factory reset and reboot.
-----------------------------------------------------------------------------------------------------------------------------------------------
If updating GSIs builds from the same branch (e.g. Floko 060219 to Floko 060919) you are not required to wipe data. You can update flashing system.img on TWRP and Gapps time by time.
If you are moving from unofficial builds to official, or if you are moving between branches (e.g. Floko to Havoc), you need to wipe data as well.
@pengus77 provided for a very useful Magisk Module that will fix adaptive brightness, battery stats and in-call BT. You will find it here: https://forum.xda-developers.com/showpost.php?p=79762257&postcount=242
If you flashed a GSI ROM, you are basically using a system.img flashed on top of your stock firmware so, unless you performed modifications to vendor or boot partition, you can revert to stock using fastboot or TWRP.
You need to extract system.img (and boot and vendor, if needed) from the stock firmware.
You will need the vbmeta file as well to re-enable AVB and dm-verity otherwise the device will reboot in fastboot mode only.
Beware: you must flash EXACTLY the same system.img of the firmware you were running before flashing a GSI
Once you have both files, you can follow these steps to go back to stock using fastboot:
- place the files on Minimal ADB & Fastboot root folder
- reboot bootloader
- start a command window from Minimal ADB and type: fastboot devices
once your device has been recognized type the following commands:
- fastboot -w
- fastboot flash system system.img
- (optional) fastboot flash vendor vendor.img
- (optional) fastboot flash boot boot.img
- fastboot flash vbmeta vbmeta.img
- fastboot reboot
You can also revert to stock using TWRP, by the way you will still need fastboot to flash vbmeta partition.
These are the steps to follow if you are using TWRP:
- place system.img on your device and vbmeta.img in Minimal ADB & Fastboot root folder.
- reboot to twrp and wipe dalvik, cache and data
- flash system.img to system partition
- (optional) flash vendor.img to vendor partition
- (optional) flash boot.img to boot partition
- reboot to bootloader
Start a command window in Minimal ADB & Fastboot, then type:
- fastboot devices
- fastboot flash vbmeta vbmeta.img
- fastboot reboot
Thansk for your work.
Does TWRP backup work?For getting back to stock?
Moh3n.B said:
Thansk for your work.
Does TWRP backup work?For getting back to stock?
Click to expand...
Click to collapse
I hope it is helpful
Backup worked for me on the TWRP I mentioned above.
If you want revert to stock you can flash again stock firmware using MiTool (fastboot ROM) or twrp (Recovery ROM).
Good thread! Might be confusing if there's no guide to install TWRP and GSI ?
Great guide. It will help a lot of people to flash and test roms. And us by extension to find the best rom for our device !
Today I had some time and I tried to install the latest Havoc Gsi, unfortunately the result was negative, I ran the guide both from xda and from here, my basic rom was 10.2.3.0, arrived at the command fastboot -w performs the various wipes, but then it does not allow me to go into recovery, it always and only goes in fastboot, and the only way to make the smartphone work is to use miflash and put the official version back.
scorpionredblack said:
Today I had some time and I tried to install the latest Havoc Gsi, unfortunately the result was negative, I ran the guide both from xda and from here, my basic rom was 10.2.3.0, arrived at the command fastboot -w performs the various wipes, but then it does not allow me to go into recovery, it always and only goes in fastboot, and the only way to make the smartphone work is to use miflash and put the official version back.
Click to expand...
Click to collapse
Try to flash vbmeta.
For me is not necesary.
Try like this from twrp:
- Wipe cache, dalvik cache, system, data
- Flash latest weekly eu firmware as base xiaomi.eu_multi_MI9SE_9.6.5_v10-9.zip
- Than flash havoc as system
Optional: flash magisk and custom kernel
Just stuck on bootloader unlocking.
Got this error "current account is not bound to this device"
I added device from mi unlock status too.
Moh3n.B said:
Just stuck on bootloader unlocking.
Click to expand...
Click to collapse
Search on Google. It looks like to be a common issue. If needed, follow the unlocking guide I linked on OP.
successfully flash Foloko ROM to Mi9 se, run very well!
just a small queastion, is DT2W is not working in all GSI rom?
Anyone try it yet?
Is there way to enable DC dimming (anti-pwm)?
I am using Havoc OS and my eyes are hurting..
sky104hk said:
successfully flash Foloko ROM to Mi9 se, run very well!
just a small queastion, is DT2W is not working in all GSI rom?
Anyone try it yet?
Click to expand...
Click to collapse
For now all gsi have same problem.
how to flash gapps ... i got error 70
raber111 said:
how to flash gapps ... i got error 70
Click to expand...
Click to collapse
Read carefully post n.2
Before I flash this, I world like to know from those already using this rom: How is the camera quality and finger print unlock response /speed?
I'm pissed at the frequent snow down of the miui system because I run vpn all day on my phone.
Sent from my Mi 9 SE using Tapatalk
krispuniq said:
Before I flash this...
Click to expand...
Click to collapse
Generally speaking, all the GSIs ROMs are based on Phhusson AOSP GSI ROM, so they have more or less the same performance and bugs.
At he moment FOD is not working well. You cannot unblock the device while on screen off or while on AOD.
For camera, you can install BSG Google Camera mod, that is working quite good.
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus Nord in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus Nord to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
DOWNLOAD
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus Nord/
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (You need the latest sdk platform tools, you can find it here
Is reccomended to format data or the rom cannot boot:
Code:
fastboot -w
Others Commands to flash a fastboot rom
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end.
These ROMs can't be used to update or downgrade your phone but just to restore your phone.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
I was already waiting for it.:laugh:
mauronofrio said:
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus Nord in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus Nord to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
DOWNLOAD
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus Nord/
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (You need the latest sdk platform tools, you can find it here
Is reccomended to format data or the rom cannot boot:
Others Commands to flash a fastboot rom
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end.
These ROMs can't be used to update or downgrade your phone but just to restore your phone.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
Click to expand...
Click to collapse
I an waiting for TWRP...
cieffe54 said:
I an waiting for TWRP...
Click to expand...
Click to collapse
Check development thread
cieffe54 said:
I an waiting for TWRP...
Click to expand...
Click to collapse
And i am waiting for end of corona pandemic.
Kollachi said:
And i am waiting for end of corona pandemic.
Click to expand...
Click to collapse
But i shared it too...
Hello and thank you for the fastboot roms !
How To Use This!
mauronofrio said:
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus Nord in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus Nord to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
DOWNLOAD
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus Nord/
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (You need the latest sdk platform tools, you can find it here
Is reccomended to format data or the rom cannot boot:
Code:
fastboot -w
Others Commands to flash a fastboot rom
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end.
These ROMs can't be used to update or downgrade your phone but just to restore your phone.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
Click to expand...
Click to collapse
Oneplus Nord oxygen os install guide
Get OEM Drivers from https://oneplususbdrivers.com/download-oneplus-usb-driver/
Download Oxygen OS 10.5.4 for your compatible devices from https://sourceforge.net/projects/fastbootroms/files/OnePlus Nord/
(Boot loader Must be Unlocked)
If still able to boot into any version of Android:
1. Install Oneplus OEM Drivers
2. Open Settings
3. Click About
4. Find the build number and click the Build number Severn times until you get a message saying developer Options have been enabled.
5. Enable ADB USB Debugger
6. Unzip the Oxygen OS File
7. Open CMD and run it as Administrator
8. Plug Your Oneplus Nord into your PC
9. Type into CMD cd and drag the Oxygen OS Folder over CMD, then Click Enter
10. This will make the link before the next line quite long.
11. Then Type into CMD “adb reboot bootloader” (This will make your Phone Reboot into Fastboot)
If You are Unable to boot into any Operating System:
1. Install Oneplus OEM Drivers
2. Unzip the Oxygen OS File
3. Open CMD and run it as Administrator
4. Type into CMD cd and drag the Oxygen OS Folder over CMD, then Click Enter
5. This will make the link before the next line quite long.
6. Plug Your Oneplus Nord into your Computer
7. When your phone is powered off, Hold Volume Up, Volume Down and the Power Button until you get the Oneplus Logo with fastboot Beneath.
Once in the Bootloader:
1. Type fastboot devices to confirm that your device has been recognised by your PC.
2. After this Open the Oxygen OS Folder and double click Flash-All.adb and It will open in command Prompt.
3. This will take a long time but wait until the phone has booted up into your phones setup (Do Not touch the Phone or Computer).
4. Setup Your Phone but don’t setup anything as we need to wipe it again, so skip through everything.
5. Once in the primary OS connect to WIFI
6. Go to Settings and Update your phone to the latest version, you will get a message prompting you that the Boot loader is unlocked etc, Ignore this and continue.
7. Click the reboot button when prompted, your Software will update to the latest version of Oxygen OS.
Once Updated:
1. Open Settings
2. Click About
3. Find the build number and click the Build number Severn times until you get a message saying developer Options have been enabled.
4. Enable ADB USB Debugger
5. Unzip the Oxygen OS File
6. Open CMD and run it as Administrator
7. Plug Your Oneplus Nord into your PC
8. Type into CMD cd and drag the Oxygen OS Folder over CMD, then Click Enter
9. This will make the link before the next line quite long.
10. Then Type into CMD “adb reboot bootloader” (This will make your Phone Reboot into Fastboot).
11. Once in Fastboot type “fastboot OEM lock” then your phone will prompt you if you want to Lock the bootloader.
12. Use the volume button to scroll down and press enter to confirm that you want to lock your bootloader.
13. When locked your phone will reboot and it will wipe your operating system and reboot your device into setup.
14. You can now setup your phone as you wish.
there's not oneplus widget? i can't find it
Jackmitchell62 said:
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus Nord in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus Nord to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
DOWNLOAD
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus Nord/
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (You need the latest sdk platform tools, you can find it here
Is reccomended to format data or the rom cannot boot:
Others Commands to flash a fastboot rom
Oneplus Nord oxygen os install guide
Get OEM Drivers from https://oneplususbdrivers.com/download-oneplus-usb-driver/
Download Oxygen OS 10.5.4 for your compatible devices from https://sourceforge.net/projects/fastbootroms/files/OnePlus Nord/
(Boot loader Must be Unlocked)
If still able to boot into any version of Android:
1. Install Oneplus OEM Drivers
2. Open Settings
3. Click About
4. Find the build number and click the Build number Severn times until you get a message saying developer Options have been enabled.
5. Enable ADB USB Debugger
6. Unzip the Oxygen OS File
7. Open CMD and run it as Administrator
8. Plug Your Oneplus Nord into your PC
9. Type into CMD cd and drag the Oxygen OS Folder over CMD, then Click Enter
10. This will make the link before the next line quite long.
11. Then Type into CMD “adb reboot bootloader” (This will make your Phone Reboot into Fastboot)
If You are Unable to boot into any Operating System:
1. Install Oneplus OEM Drivers
2. Unzip the Oxygen OS File
3. Open CMD and run it as Administrator
4. Type into CMD cd and drag the Oxygen OS Folder over CMD, then Click Enter
5. This will make the link before the next line quite long.
6. Plug Your Oneplus Nord into your Computer
7. When your phone is powered off, Hold Volume Up, Volume Down and the Power Button until you get the Oneplus Logo with fastboot Beneath.
Once in the Bootloader:
1. Type fastboot devices to confirm that your device has been recognised by your PC.
2. After this Open the Oxygen OS Folder and double click Flash-All.adb and It will open in command Prompt.
3. This will take a long time but wait until the phone has booted up into your phones setup (Do Not touch the Phone or Computer).
4. Setup Your Phone but don’t setup anything as we need to wipe it again, so skip through everything.
5. Once in the primary OS connect to WIFI
6. Go to Settings and Update your phone to the latest version, you will get a message prompting you that the Boot loader is unlocked etc, Ignore this and continue.
7. Click the reboot button when prompted, your Software will update to the latest version of Oxygen OS.
Once Updated:
1. Open Settings
2. Click About
3. Find the build number and click the Build number Severn times until you get a message saying developer Options have been enabled.
4. Enable ADB USB Debugger
5. Unzip the Oxygen OS File
6. Open CMD and run it as Administrator
7. Plug Your Oneplus Nord into your PC
8. Type into CMD cd and drag the Oxygen OS Folder over CMD, then Click Enter
9. This will make the link before the next line quite long.
10. Then Type into CMD “adb reboot bootloader” (This will make your Phone Reboot into Fastboot).
11. Once in Fastboot type “fastboot OEM lock” then your phone will prompt you if you want to Lock the bootloader.
12. Use the volume button to scroll down and press enter to confirm that you want to lock your bootloader.
13. When locked your phone will reboot and it will wipe your operating system and reboot your device into setup.
14. You can now setup your phone as you wish.
Click to expand...
Click to collapse
Or simply use MSM tool ?
https://forum.xda-developers.com/oneplus-nord/how-to/opnord-unbrick-tool-to-restore-device-t4148415
Reboot in recovery
Hello everyone, I need help.
I got the message "File system raw not supported." after executing the flash_all.bat and
Code:
boot_b, dtbo, modem_b, recovery, vbmeta, vbmeta_system,
was sent with status
Code:
OKAY
(the first part of the script, as far as I can see), then is supposed to reboot on fastboot and stays at
Code:
<waiting for any device>
, here is when my phone restarts in recovery instead (it says "fastbootd" in the upper part and a menu to select chinesse or english, but it's recovery mode, right?), then the first time I wited for 15 minutes but nothing happened, so I selected reboot into fastboot in recovery mode, then in CMD I got the message "fastboot: error Failed to boot into userspace fastboot; one or more components might be unbootable", and the seccond part of the script was executed, but with
Code:
FAILED (remote: 'Flashing is not allowed for Critical Partitions')
status in the writing process, and after,
Code:
"Invalid sparse file format at header magic"
with
Code:
FAILED (remote: 'Partition not found')
when trying to write system, vendor and product. My phone restarted and looked normar but wifi didn't work, and the UI started to fail after the configuration.
So I tried again, but without rebooting from recovery; how much time do I have to wait there?, maybe this will not work.
Please if someone knows how to solve my problem I'll be glad for the help.
MSM TOOL
https://forum.xda-developers.com/oneplus-nord/how-to/opnord-unbrick-tool-to-restore-device-t4148415
I succeeded from linux, everything seems to work fine now.
I just have one question, there's one file missing
fastboot flash storsec storsec.img
Is supposed to be like that or is that an important file missed?
That file doesn't exists in the 10.5.5-INDIA-NordOxygen_14_OTA_007_all_2008180229 zip file
I bricked my device and nothing (what i try) worked.
Hello Guys,
Thanks for the Roms and also for twrp @ mauronofrio!
If i try to flash in fastboot the roms, i get different fails:
the first part of commands are okay until "fastboot reboot fastboot"
than, until "fastboot flash xbl_config xbl_config.img" i get:
"writing 'xbl_config'...
FAILED (remote: Flashing is not allowed for Critical Partitions)"
and for the lasts, i get:
FAILED (remote: Partition not found)
I read that some windows-user have the same Problem and therrefore the Problem is not the bricked phone, is it right?
Someone knows the same Problem in linux? I prefer a solution without windows (msm-tool).
I tried to root and flash with twrp, now i know, it's impossible to flash zips until now. I try some other things with twrp, it's possible that i delete some partitions?
Someone have a good solution?
thanks for reading and support
Hi,
Few questions:
Has Global rom OP dialer? Can be enabled auto call recording with root or adb? I know abut Skvalex.
Can I flash 10.5.5 Global at 10.5.9 EEA (flash_all.bat)?
Getting stuck on odm and vendor flashing. It will not flash odm and vendor no file exists message (using flash all bat). Any help will be greatly appreciated.
Update: got it back to stock using edl mode.
You can flash this way. When you enter from the fastboot to the fastbootD mode Windows thinks it's a new device and doesn't recognize it. If you open device manager from control panel it will showns as unknow device. So all you have to do is install the driver again. Then you can flash anything you want in fastbootD.
-
What does "unbranded" mean here? Will I get OTA updates? Will this relock the bootloader?
delete
Current State:
TWRP Installed, no OS, no system partition, instead a super partition.
I also flashed an orange_state_disabler which seems to have worked just fine.
ADB Sideload:
When I try to start ADB Sideload Feature this is what I get:
https://pastebin.com/k3gJ048P
when trying to use the adb sideload command:
Code:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
I converted the lineageos img file I have to a flashable zip using the tool from here:
https://forum.xda-developers.com/nu.../swapper-generate-flashable-zips-img-t4133591
but when I try to flash that zip file tho it returns this:
Code:
Installing zip file '/usbotg/system.zip'
Checking for Digest file...
Unmounting System...
Invalid zip file format!
Error installing zip file '/usbotg/system.zip'
Updating partition details...
...done
so... yeah, I don't know what else to do right now.
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
jwoegerbauer said:
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
Click to expand...
Click to collapse
Heh, I was just trying to get the ROM on the device so I could flash it then via TWRP but maybe I just misunderstood what adb sideload does
0
Seppppx said:
The Oneplus 8 Pro has a dynamic partition layout and you flash a system image by doing "fastboot flash system system.img"
See : https://forum.xda-developers.com/oneplus-8-pro/development/rom-lineageos-17-1-t4122983
Click to expand...
Click to collapse
Yeah I tried that already, the problem is that it doesn't have a system partition
MoonPadUSer said:
Yeah I tried that already, the problem is that it doesn't have a system partition
Click to expand...
Click to collapse
Your posted error messsage suggests the zip install has failed. So no change to device should have happened.
Current twrp cannot flash system.img
Only super.img(combined system.img, vendor.img, and product.img)
The systemswapper you refered to is from a qualcom device thread, and uses some *qti* device binaries that are not in your recovery. It is unlikely to have worked. (I might be wrong about the *qti* binary being only a qualcom device tool)
These new devices with dynamic partition have 2 fastboot modes.
The bootloader mode (adb reboot bootloader)
This is used for unlocking bootloader, flashing standard partitions
There is fastbootd mode (adb reboot fastboot)
This mode is only available if stock recovery is installed.
It also requires r30 or higher fastboot binary file on PC.
From fastbootd you can flash the sub partitions on super.img
There is alot of changes that take place with this new partition setup.
As for your phone no longer booting into original system, and bootlooping to recovery, I suggest first try boot to bootloader, and flash stock recovery, see if this stopps the bootlooping.
If not then use sp flash tool and flash full stock room and start fresh
mrmazak said:
From fastbootd you can flash the sub partitions on super.img
Click to expand...
Click to collapse
How?
MoonPadUSer said:
How?
Click to expand...
Click to collapse
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
Code:
fastboot flash system /some-directory-on -pc/gsi-system.img
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
MoonPadUSer said:
How?
Click to expand...
Click to collapse
I did another post about using fastbootd on similar device. The information is all relevant to your a7pro too.
https://forum.xda-developers.com/showpost.php?p=83241985&postcount=3
mrmazak said:
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
Click to expand...
Click to collapse
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Where I am right now:
I am back to a fully working device after downloading the stock ROM from my manufacturer and plugging that into SP Flash tool
After that I researched and figured out that the super partition I have basically acts like a container for
system.img, boot.img and vendor.img
which explains while simply flashing LineageOS.img to my super partition (
Code:
fastboot flash system Lineage.img
) resulted in
my device not booting anymore.
I found a tool which can unpack those super.img into system, boot and vendor
(using this youtube video: https://youtu.be/J5cQdzivtXk)
I used that to unpack the super.img which I got from my stock ROM and
now I have system.raw, boot.raw and vendor.raw, I do not know what kind of file these are but my plan is to replace system.whatever with the lineageos.img and then repack it into super.img which I can then use to flash the super partition on my phone
MoonPadUSer said:
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Click to expand...
Click to collapse
Can you show picture of this .
Of both pc screen and phone screen, please
mrmazak said:
Can you show picture of this .
Of both pc screen and phone screen, please
Click to expand...
Click to collapse
I'd love to but how am I supposed to take a picture of my phone screen in fastboot mode? (I don't have any other devices with a camera)
@MoonPadUSer
Code:
fastboot flash system Lineage.img
must have failed.
Reason: This command tries to write a complete Lineage OS ( what itself contains a partition named /system, too ) into phone's Android's current /system partition - what only is 1 partition of multiple ones that exist.
Note: You can't flash a Custom ROM by means of Fastboot.
Re-read post #2
0
Seppppx said:
That's not true when you are flashing a Generic System Image.
Click to expand...
Click to collapse
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
jwoegerbauer said:
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
Click to expand...
Click to collapse
Actually... I don't really care about the version all that much, whatever works, just didn't know if 18x is supported
Downside to Lineage GSI is for Umidigi you can't flash gapps. So unless someone adds it to the gsi for you it's best to use something else.
I went with this
https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559
You have to get the AB version with GAPPS if you want them
Comes pre rooted as well and gave my phone a huge speed boost
Flash the stock ROM
Unlock bootloader
fastboot flashing unlock
(unnecessary if already unlocked)
fastboot flashing unlock_critical
enter fastboot
fastboot reboot (to enter fastbootd)
fastboot erase system
(optional but I had to do this myself)
fastboot delete-logical-partition product - deletes the product partition, allowing a larger system partition
fastboot flash system (gsi file)
And you're good
Don't try to install magisk because it causes a bootloop. Even when installing it through the app. Once the boot image is patched you're in a bootloop until you reflash the stock boot
Made a generic ish Umidigi flashing tutorial because it's the same in all of them I've had so far
https://forum.xda-developers.com/an...ng-rom-gsi-t4182673/post83803205#post83803205
I'll add some links to other threads that helped make this but I've found the root/custom rom process is the same for all
You don't need TWRP and if you're able to install it you won't get far as the system partition is hidden
try to make sure it comes with gapps preinstalled as you won't be able to install it after
*lineage will work but doesn't come with gapps preinstalled for example
Pre requisite: flash the latest rom using spflash tool
Steps:
1. Pick a rom here https://forum.xda-developers.com/project-treble
From the two devices I've had it looks like it must be an AB rom
I went with this as it is pre rooted
2. Back up your data & Unlock bootloader
fastboot flashing unlock
(unnecessary if already unlocked)
fastboot flashing unlock_critical
3. Enter fastboot either with adb or power on while holding volume up
4. Fastboot reboot to enter fastbootd
5. fastboot erase system
6. Your system partition is likely too small so delete it
fastboot delete-logical-partition product - deletes the product partition, allowing a larger system partition
7. fastboot flash system (gsi file here)
And you're good to go
As of right now you can install the magisk app but it won't do much. Tried using the app last night as it got root from the other app but the patched boot image caused a bootloop and I had to reflash stock boot.
It looks like this is a thing with this brand and magisk at the moment not sure why
sources
https://forum.xda-developers.com/android/help/umidigi-power-3-android-10-t4044531
https://forum.xda-developers.com/android/development/twrp-twrp-3-4-0-0-umidigi-t4169405
orions_Cat said:
I'll add some links to other threads that helped make this but I've found the root/custom rom process is the same for all
You don't need TWRP and if you're able to install it you won't get far as the system partition is hidden
try to make sure it comes with gapps preinstalled as you won't be able to install it after
*lineage will work but doesn't come with gapps preinstalled for example
Pre requisite: flash the latest rom using spflash tool
Steps:
1. Pick a rom here https://forum.xda-developers.com/project-treble
From the two devices I've had it looks like it must be an AB rom
I went with this as it is pre rooted
2. Back up your data & Unlock bootloader
fastboot flashing unlock
(unnecessary if already unlocked)
fastboot flashing unlock_critical
3. Enter fastboot either with adb or power on while holding volume up
4. Fastboot reboot to enter fastbootd
5. fastboot erase system
6. Your system partition is likely too small so delete it
fastboot delete-logical-partition product - deletes the product partition, allowing a larger system partition
7. fastboot flash system (gsi file here)
And you're good to go
As of right now you can install the magisk app but it won't do much. Tried using the app last night as it got root from the other app but the patched boot image caused a bootloop and I had to reflash stock boot.
It looks like this is a thing with this brand and magisk at the moment not sure why
sources
https://forum.xda-developers.com/android/help/umidigi-power-3-android-10-t4044531
https://forum.xda-developers.com/android/development/twrp-twrp-3-4-0-0-umidigi-t4169405
Click to expand...
Click to collapse
Hi, when I try to erase the system with fastboot it fails and says that the partition table doesn't exist. How can I solve that? thanks