Related
Okay so I got my oneplus 3t today and I updated it to Nougat via the ota file all good so far. I then decided that I wanted to install a custom rom so I downloaded twrp supersu etc everything needed to root and install the rom. Here's where it went wrong in knowingly I downloaded the wrong twrp flashed it and it would just hang at the flash screen for twrp. Anyway after hours of trying to install a recovery I managed to get a stock one to semi work, now it turns out I don't know how I did it but my phone won't even boot it just turns on and goes straight to fastboot mode. I managed to get a stock recovery semi working but it won't let me install the stock rom from internal storage and I've tried updating through adb and it will hang at a random percentage for a good 20 mins and then just fail. Really need some help here it would be great, thanks
Hi,
If you can get into fastboot mode then the best recourse is through there. Hope you properly OEM unlocked your device.
First of all, you MUST have the latest adb/fastboot binaries and FOR SURE have the correct drivers.
Follow the links on this XDA article to download the latest adb and fastboot binaries: https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads
This is the link for the Windows binary: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Extract all the contents of the zip file in a folder on your PC.
Then, also make sure to have THE CORRECT twrp, 3.0.2.0 or 3.0.3.0. This is the link but currently it is down: https://twrp.me/devices/oneplus3t.html
Download THE IMAGE, NOT FLASHABLE ZIP and put it in the same folder as the android platform tools above.
Finally, download the latest complete 3T firmware from OnePlus from this link: http://downloads.oneplus.net/devices/oneplus-3t/
I STRONGLY recommend not to use an update zip, even a full ROM update zip as that one might not include certain firmware images.
Put THE ZIP on the same folder as the others, DO NOT EXTRACT ANYTHING.
On your PC, open a command prompt in the folder where you extracted the android platform tools and run the following: fastboot boot twrp-3.0.3-0-oneplus3t.img (assuming you downloaded the 3.0.3 version of twrp).
Your phone will TEMPORARILY accept the twrp recovery as a boot image and boot from there. NOTHING IS BEING PERMANENTLY WRITTEN AT THIS TIME.
After that, enter TWRP's Wipe menu and wipe system, data and cache.
Finally, use TWRP's Advanced menu and enter adb sideload mode. Once there slide that slider to the right to enable adb mode and return to your PC and enter the following command in the command prompt:
adb sideload OnePlus3TOxygen_28_OTA_029_all_1612131737_17e7161d2b234949.zip (assuming you downloaded the 3.5.4 binary from OnePlus).
TWRP should properly flash the OnePlus ROM and hopefully, return you to proper function. You can then update back to Nougat.
Hope that helped!
Yeah that sorted it thanks a lot
Use the emergency tool for OP3T and start from scratch:
https://forums.oneplus.net/threads/unbrick-guide-oneplus-3t.481214/
@KeyperOS
I'm trying to follow this guide, but did you miss something out here?
On your PC, open a command prompt in the folder where you extracted the android platform tools and run the following: fastboot boot twrp-3.0.3-0-oneplus3t.img (assuming you downloaded the 3.0.3 version of twrp).
Your phone will TEMPORARILY accept the twrp recovery as a boot image and boot from there. NOTHING IS BEING PERMANENTLY WRITTEN AT THIS TIME.
Click to expand...
Click to collapse
Once I do "fastboot boot twrp" and get a success, then what?
Do I need to somehow reboot the phone into TWRP - because that didn't happen on its own.
If so, how do I do this?
Thanks,
jackmacbunton said:
Yeah that sorted it thanks a lot
Click to expand...
Click to collapse
Glad that sorted it out
PugRallye said:
@KeyperOSI'm trying to follow this guide, but did you miss something out here?
Once I do "fastboot boot twrp" and get a success, then what? Do I need to somehow reboot the phone into TWRP - because that didn't happen on its own. If so, how do I do this? Thanks,
Click to expand...
Click to collapse
My instructions while detailed are not step-by-step. I expect the person reading them to have their PC configured correctly and at least a vague idea of what they're doing.
So, assuming you put the correct TWRP image (my command uses the name of the image for TWRP 3.0.3.0, you MUST alter it to reflect the actual image's filename if it's not that) on the same folder as the fastboot binary then yeah, the command
fastboot boot twrp-3.0.3-0-oneplus3t.img
should have made your phone reboot and enter into the TWRP image that you had on your PC.
If it didn't then you did sth else wrong before that.
Either you didn't OEM unlock your phone when you still could or you didn't use the android platform tools that I linked or you don't have the correct ADB drivers installed on your PC.
Start from there.
Hope that helped!
Thanks for your help @KeyperOS - I know where I went wrong...
To save some time, when I tried to reboot into TWRP, I typed "fastboot boot " then I dragged and dropped the TWRP img file onto that line in the cmd window (rather than typing the filename manually) - when you do that, it appears to include the full path to the img - it was that that was causing the problem.
When I typed the TWRP filename manually, it worked.
The only thing that caught me out was after I'd installed the ROM (via adb sideload) I tried to reboot the device from TWRP recovery - this seemed to just hang. In the end I just powered off the phone using the power key, then powered it back up as per usual.
Checked that the phone booted to the first of the setup screens, then powered off/booted into fastboot mode, relocked the bootloader and it seems to be OK.
I'm now back on 3.5.4 again, which was what I was trying to do...
4.0.0/1 had felt a bit laggy, and I'd sensed some issues with wifi and BT, I can now run 3.5.4 and see how it compares - was I just imagining it?
Thanks again for the guide and your help - I really appreciated it
@PugRallye
Windows' command prompt has an autocomplete feature. If you want it to add the name of a file, type a couple letters and then present TAB, it's gonna complete the filename itself and if it's the wrong file you can keep tapping tab to cycle through all the options.
Really glad it worked out Btw [emoji4]
In my experience, 3.5.4 was great but 4.0 is a step up in both battery life, which IME is amazing and features, with it I almost didn't need root and certainly don't need xposed which was a first.
First of all, I would like to say thanks to @DrakenFX, @tenfar, @rczrider, and @tennear for their work on the Axon 7.
Code:
/* Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or any other mishaps that may occur. YOU are choosing to make these modifications, and if
* you blame me in any way for what happens to your device, I will laugh at you.
*/
This guide is intended to help anyone wishing to return to stock B20 firmware on the A2017U for the purposes of re-locking the bootloader (either for sending a device in for an RMA or whatever you may need). After much trial and error, I have finally come up with a guide and attached all necessary files to do this. I performed the following steps on my Axon 7 2017U on the B29 firmware and successfully downgraded to the B20 firmware with a re-locked bootloader.
Here are the files you will need:
Stock system
Stock boot stack
Stock fastboot
Stock recovery
TWRP
Make sure you have ADB and fastboot set up properly on your computer.
Use the TWRP linked in this post. I know for sure that this version works towards the end of this process when your bootloader is locked again.
After you have the zip files, you will need to move them to your phone to flash in TWRP. Follow these steps:
1. Make a backup of all of your important data. EVERYTHING will be wiped in this process, including internal storage.
2. Power off the phone.
3. Download the the axon7tool executable file from this link: Here Check the post for instructions pertaining to drivers needed.
4. Boot the phone into EDL mode. Do this by holding down the Volume Up and Volume Down keys simultaneously and then plugging the phone in to your computer while keeping these keys pressed. (The phone's screen will be completely black and it will appear like nothing is happening. This is EDL mode.)
5. Open a command prompt in the directory with the axon7tool executable. (Windows: right click while holding shift and select "Open command window here." Linux: Open a terminal and cd into the directory)
6. Dump your gpt with the tool. (Note: you may need root access to run the following commands on Linux)
Code:
Windows: axon7tool-1.5-win64 -r gpt
Linux: ./axon7tool-1.5-linux -r gpt
7. The axon7tool will automatically reboot you. Reboot to TWRP.
8. Make a backup of your EFS partition by going to "Backup" with only the EFS box checked.
9. Copy the "TWRP" folder from your internal storage to your computer. This folder contains the EFS backup.
10. Go to "Wipe" -> "Advanced" -> "Format Data." Type "yes." WARNING: THIS DELETES ALL DATA. MAKE SURE YOU HAVE A BACKUP.
11. Reboot back into TWRP. Ignore anything TWRP says or asks you to do upon a reboot.
12. Copy the "B20_stock_system," B20_stock_bootstack," and "B20_stock_fastboot" zip files to your internal storage.
13. Flash the stock system zip first, then the boot stack zip, and finally the fastboot zip.
14. At this point you are on the stock B20 system, but with an unlocked bootloader. TWRP will probably be overwritten, so follow these next steps regardless.
15. Reboot the phone and let it get to the set up screen. This step can take a while; my Axon took almost a minute to get off of the ZTE splash screen initially.
16. As soon as you see that the phone boots, power off the phone and reboot to EDL mode.
17. Flash TWRP again with the axon7tool as it has been overwritten at this point and will be necessary soon. Download the linked TWRP recovery image and rename the file to "recovery.bin" Place it in the same folder as the axon7tool. Flash the recovery. (Note: you may need root access to run the following commands on Linux)
Code:
Windows: axon7tool-1.5-win64 -w recovery
Linux: ./axon7tool-1.5-linux -w recovery
18. Reboot the phone into the bootloader. You can do this by going to TWRP and by choosing reboot to bootloader or by manually doing so.
19. Type "fastboot oem lock" into a command prompt. This will lock your bootloader.
20. After I did this, I thought I was done. However, when I rebooted my phone, I saw that /data required a password to be decrypted upon a reboot. This is why we flashed TWRP. Go into TWRP and format data again.
21. Copy the "TWRP" phone from earlier back onto your internal storage. Restore your EFS in case anything has happened to your IMEI in this process.
22. At this point your phone is completely locked but with a custom recovery. To restore the stock recovery, reboot into EDL mode and replace the TWRP recovery.bin file from a few steps ago with the B20_stock_recovery.bin file you downloaded. Rename the B20_stock_recovery.bin file to recovery.bin and make sure it's in the same folder as the axon7tool.
23. Flash the stock recovery with the same commands for the axon7tool as listed earlier for TWRP.
24. Profit
As tennear has noted, do NOT backup or restore the EFS partition.
Never restore EFS using TWRP. You will lose its contents and probably your IMEI.
@tennear Thanks for the heads up. I'll remove that part from my guide.
Hi
I flashed the twrp recovery on locked bootloader but i lost my recovery
My firmware was 0b15
Can i flash the 0b20 stock recovery.bin to restore it?
mortkarg5 said:
Hi
I flashed the twrp recovery on locked bootloader but i lost my recovery
My firmware was 0b15
Can i flash the 0b20 stock recovery.bin to restore it?
Click to expand...
Click to collapse
Were you trying to restore your whole firmware to b20 as the guide demonstrates or were you only flashing the TWRP linked in this post?
Yoshi_Guy said:
Were you trying to restore your whole firmware to b20 as the guide demonstrates or were you only flashing the TWRP linked in this post?
Click to expand...
Click to collapse
Oh no...
I had tried to flash twrp to install a custom rom...
And i used the Miflash tool to flash it,but i forgot to unlock bootloader, and i think if i flash the stock recovery, i will be able to change the situation...
Are you think this will work?
Or i have to downgrade my firmware to 0b20 and then flash the full pack?
mortkarg5 said:
Oh no...
I had tried to flash twrp to install a custom rom...
And i used the Miflash tool to flash it,but i forgot to unlock bootloader, and i think if i flash the stock recovery, i will be able to change the situation...
Are you think this will work?
Or i have to downgrade my firmware to 0b20 and then flash the full pack?
Click to expand...
Click to collapse
You can try, but I'm not sure if it would work. The recovery is for stock b20 so try it at your own discretion.
Every time I try to do the fastboot oem lock it fails, I have the twrp you mentioned in the post and followed the steps as listed. Did you run into this issue?
Sent from my ZTE A2017U using Tapatalk
i can't found same file u can upload again?
Yeah.... most links are dead. Does anyone else have them?
Flapjack said:
Yeah.... most links are dead. Does anyone else have them?
Click to expand...
Click to collapse
I'll fix them.
Yoshi_Guy said:
I'll fix them.
Click to expand...
Click to collapse
Thanks, brotha.
Flapjack said:
Thanks, brotha.
Click to expand...
Click to collapse
Try again, they should be working now.
Yoshi_Guy said:
Try again, they should be working now.
Click to expand...
Click to collapse
Thanks... but holy f*ck... this MEGA bs. What a piece of garbage. Why do I need to create an account?
I'm getting the following error (Win 10). Others have gotten the same error in various versions of linux, as well. The only one who resolved the error had forgot to elevate his terminal (which I've done):
Code:
c:\Temp\Axon>axon7tool-1.5-win64 -r gpt
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
c:\Temp\Axon>axon7tool-1.5-win64 -r gpt
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
I'm seriously stuck. I did everything up to step 15, but it starts to boot, sits at the ZTE screen for about 30 seconds, then shuts off. When I try to reboot, it does the same thing. I had two problems getting up to step 15. The first problem was that the axon tool refused to work. I posted the error a few days ago, but no one replied. Since the phone has to go back to ZTE and I'm running out of time, I decided to press on.... since it only seemed like a backup, which I have plenty of.
The second error was at step 12. After Step 10, I could not read/write anything on the internal sdcard. It is obviously encrypted... which begs the question... what good is step 10 if it doesn't blow away the encryption? At any rate, I copied the the three zip files to an external SD card flashed the bootstack and fastboot, both of which completed without error.
As of now, I can get into the ZTE MiFavor recovery and then to bootloader mode, but it won't take any of the fastboot commands. Running fastboot devices shows the phone, but every fastboot command fails with "unknown command".
I've also tried flashing the B20 system and fastboot zips from the MiFavor recovery, but both say "signature verification failed".
Not sure what to do now.
---------- Post added at 08:13 PM ---------- Previous post was at 07:26 PM ----------
I just tried the official ZTE file here, but it said "signature verification failed" also. Not sure how that's possible.
@Yoshi_Guy
In step 22) where stock recovery has to be restored, instead of reusing axon7tool in EDL mode, maybe it would be easier to flash stock recovery by the signed tenfar TWRP itself (by using TWRP Install/flash image option, boot partition). This is a kind of "hara-kiri" (current TWRP destroys itself) but it should work.
Flapjack said:
I'm seriously stuck. I did everything up to step 15, but it starts to boot, sits at the ZTE screen for about 30 seconds, then shuts off. When I try to reboot, it does the same thing. I had two problems getting up to step 15. The first problem was that the axon tool refused to work. I posted the error a few days ago, but no one replied. Since the phone has to go back to ZTE and I'm running out of time, I decided to press on.... since it only seemed like a backup, which I have plenty of.
The second error was at step 12. After Step 10, I could not read/write anything on the internal sdcard. It is obviously encrypted... which begs the question... what good is step 10 if it doesn't blow away the encryption? At any rate, I copied the the three zip files to an external SD card flashed the bootstack and fastboot, both of which completed without error.
As of now, I can get into the ZTE MiFavor recovery and then to bootloader mode, but it won't take any of the fastboot commands. Running fastboot devices shows the phone, but every fastboot command fails with "unknown command".
I've also tried flashing the B20 system and fastboot zips from the MiFavor recovery, but both say "signature verification failed".
Not sure what to do now.
---------- Post added at 08:13 PM ---------- Previous post was at 07:26 PM ----------
I just tried the official ZTE file here, but it said "signature verification failed" also. Not sure how that's possible.
Click to expand...
Click to collapse
That's quite odd, what version of Linux are you using? Also, are you able to try the Windows version of the tool? I've used the tool on Arch Linux and had no problems. Also, the program does need to be run as root, as you mentioned. The signature verification probably failed because you are trying to downgrade your version, I wouldn't recommend using the official ZTE zips entirely. I would take what you need and flash just that, downgrading is rather complex.
Thanks for the guide, but wish you would've used androidfilehost. I hit MEGA quota at 80%, so I'll have to wait til late tonight to give this a shot.
nvm: using megadownloader now
First, thanks to @Uzephi and @41rw4lk for helping me to use/recover my phone. Please, read and do not underestimate the guides: our phone is tricky! We have two system partitions (slot a and b) to allow stock updates on-the-fly. This complicates the normal flashing process and if you do not follow the steps, you may bootloop. Use these guides at your own risk!
Reading this page is a good beginning to understanding the A/B partitioning scheme and how Motorola Z2 Force works:
1) Our phone has A/B partitioning, so flashing Magisk/XPosed is different
2) It does not support Project Treble (faster stock updates)
3) It does not a recovery partition, so flashing TWRP is different
Note also that the RSD Lite from Motorola has issues with Windows 10 and you’ll need to manual flash firmware if you bootloop (see Process E below). Other way is directly flashing from Qualcomm EDL mode (Emergency Download Mode) from which users can perform various tasks like unbricking, unlock bootloader, and installation of any custom ROMs.
Right now, this guide has 5 parts (maybe we can dual boot our phone in the future). If you just want to use a rooted stock ROM, please, search for other guides here on xda. These guides were written (and tested) using a Motorola Z2 Force XT1789-05 phone (Brazil), although most of it should work for other variants if you download and use proper firmware files for these other phones. For other models, better if you follow Uzephi’s guide.
A. Opening bootloader
B. Preparing the phone to move into custom ROMs (AOSP) + TWRP recovery
C. Flashing a custom AOSP ROM + rooting
D. Dirty flashing AOSP ROM updates
E. Recovering from bricks or returning to stock
F. Oreo ROM features comparison table
If you want to move your Motorola Z2 Force to Project Treble ROMs, please, check this guide.
Here is a list of the ROMs that are waiting for you.
A. Opening bootloader
With enough battery in your phone (80%), you can follow the Motorola official guide which steps are:
1. Backup everything you need. Your phone will be reseted including the internal sdcard.
2. Into the phone, enable the Developer Options clicking 7 times over the version (About section in the Settings). Go to Developer Options, click the OEM unlock option to enable it. Also enable USB debugging.
3. Install the Motorola drivers in your computer, but (in my personal experience) not the Android SDK suggested in the official guide. Instead, extract these adb/fastboot files in a blank folder of your computer.
3.1) Do not use other adb/fastboot binaries: I cannot guarantee they will work.
3.2) You need to use a USB 2.0 port of your computer. Some users report that USB 3.0 will also work.
4. Open a command line window in the adb/fastboot folder (step 3), reboot the phone into the bootloader (see adb command below or press power + volume down buttons). Plug the phone on computer (see 3.2 above). Test the connection and run the command to get the code for unlocking:
Code:
adb reboot bootloader
fastboot devices
fastboot oem get_unlock_data
You’ll get:
Code:
(bootloader) Unlock data:
(bootloader) <code 1>
(bootloader) <code 2>
(bootloader) <code 3>
(bootloader) <code 4>
(bootloader) <code 5>
5. You’ll need to join 5 codes and, after logging into your own Motorola account, check by clicking the button “Can my device be unlocked” (step 6) by Motorola here. Read the text: your warranty will be void if you go ahead. Consider if you have enough knowledge, time and money to deal with a troublesome (or bricked) device. Although, it’s not that easy to hard brick this phone (see process E below).
Code:
<code 1><code 2><code 3><code 4><code 5>
6. You’ll receive back an email with the code to unlock your bootloader (if it is available for your model). Then you’ll run the following command:
Code:
fastboot oem unlock <code 1><code 2><code 3><code 4><code 5>
7. You’ll receive a warning that all your data would be erased (see step 1 above) and need to re-run the same command to confirm. At this point, your bootloader should be unlocked. As an Android restriction, each time you boot the phone you’ll see a warning. Do nothing, wait for 5 seconds and the phone boots normally. Some users bother with this warning and try to get rid of it.
B. Preparing the phone to move into custom ROMs (AOSP) + TWRP recovery
Requirements: unlocked bootloader (see guide A) and no security lock: disable PIN, gestures and fingerprinting (because TWRP cannot read the locked/cryptographed data of the phone). Enough battery in your phone (80%).
If you do not prepare your phone to custom ROMs and if you do not have both bootloaders of the phone in the same Android version of the ROM you’ll flash, you’ll hard brick the phone and lose also the access to the bootloader! You’ve been warned: follow the guide!
Note: if you hard brick, I suggest you be prepared to follow the Unbrick Qualcomm mobiles with Step-by-step guide or the Unbrick All Qualcomm Snapdragon’s from Qualcomm HS-USB QDLoader 9008 guide, but I never tested them myself. You can also use Qualcomm Flash Image Loader (QFIL) tool.
1. Backup everything you need. Your phone will be reset including the internal sdcard.
2. Into the phone, enable the Developer Options clicking 7 times over the version (About section in the Settings). Go to Developer Options and enable USB debugging.
3. Install the Motorola drivers and the adb/fastboot files.
3.1) do not use other adb/fastboot binaries: we cannot guarantee they will work.
3.2) you need to use a USB 2.0 port of your computer. Some users report that USB 3.0 will also work.
4. Download the firmware of the same Android major version of the future ROM you’ll install (Oreo for Oreo ROMs, for instance). When (and if) we move to Android P, most probably we will need to follow this guide again.
- Retail (XT1789-05) (Europe/Brazil).
- Other models (branded): ATT, Sprint, T-Mobile (TMO), USC, Verizon.
- Note: NPXS26 versions stand for Nougat and OPXS27 for Oreo. You do not need Nougat versions for anything.
5. Extract the zip contents to a blank folder in your computer.
6. Download the FlashAll_XT1789-05.zip file, extract the content and move all files to the same firmware folder (step 5 above). Be sure to overwrite any file (if needed).
7. Run the Preparation.bat file there to generate the flashfile.bat file that will send the commands to the phone. Credits: the original preparation files were from RootJunky (can be downloaded here) and include more options that we do not need for our purpose here. Also, it includes adb/fastboot binaries that could not work with our phone.
8. Reboot the phone into the bootloader (see adb command below or power + volume down buttons). Open a command line window in the firmware folder (step 5 above), test the connection and execute the flashfile.bat file generated on step 7.
Code:
adb devices
adb reboot bootloader
fastboot devices
flashfile.bat
Never ever unplug the device from the USB 2.0 port while flashing the firmware. This could cause a hard brick and your device will be dead.
9. There is a pause at the end. You should review if everything went fine (or even click on the menu of the command line window, select all and copy&paste the contents in a .txt file for further help/revision).
10. Reboot your phone into the system (ROM) and do a quick configuration (remember that everything will be deleted when you install TWRP further…).
11. Into the phone, enable the Developer Options clicking 7 times over the version (About section in the settings). Go to Developer Options and enable USB debugging.
12. Download both the .img and .zip file of the TWRP recovery from the official site. It's the same file for all models/variants of Z2 Force phone. Put the files into our firmware folder (step 5 above). Copy the .zip file to the phone internal card. Note: versions older than 3.2.2-2 does not support PIN/Password/Fingerprint, so disable them before proceed. Most probably, ROMs before July 20th, 2018 cannot be flashed in older TWRP.
13. Now boot (not flash) the TWRP .img file using a command line window in the same firmware folder (step 5 above):
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot boot <TWRP file name>.img
14. Only now that you’re inside TWRP temporarily flash the TWRP .zip file you’ve saved into the phone (step 12 above).
15. Reboot into TWRP (use the main reboot menu in TWRP).
16. Now, you should reboot again into bootloader: inside TWRP, go to Reboot menu and choose Bootloader.
17. Now you will wipe all user data via bootloader. This is necessary to use an AOSP ROM when you come from stock. Using a command line window in the same firmware folder of your computer (step 5 above), run the following commands:
Code:
fastboot devices
fastboot -w
18. Now you can reboot the phone into System using the buttons volume up/down to navigate and confirming with the Power button. You’ll be with stock ROM and TWRP. If you want to move to a custom AOSP ROM, do a quick configuration: into the phone, enable the Developer Options clicking 7 times over the version (About section in the settings). Go to Developer Options and enable USB debugging and go to the proper guide (Process C).
C. Flashing a custom AOSP ROM + rooting
1. Requirements:
1.1 Motorola drivers.
1.2 Our custom adb/fastboot files (others may not work!).
1.3 USB debugging enabled into the Developer Options.
1.4 If you're using TWRP older than 3.2.2-2, disable disable PIN/gestures/fingerprinting. Also, most probably, ROMs after July 20th, 2018 cannot be flashed in older TWRP.
1.5 An USB 2.0 port of your computer (some users report that USB 3.0 will also work).
1.6 Two Oreo bootloaders (process B above).
1.7 Permanent TWRP
1.8 Enough battery in your phone (80%).
2. Download the AOSP ROM you want and move the .zip files to the phone. Right now, we have:
2.1 Dirty Unicorns: no need for Gapps. Official and Weeklies can be dirty flashed interchangeably. RC has a different signature. Support on Google+ page. More about DU kernel.
2.2 Lineage OS 15.1. MindTheGapps needed. OpenGapps not compatible yet. XDA thread.
2.3 Mokee: Gapps needed. Take care: online guides assume that you already have an AOSP ROM, TWRP and rooted device.
Deprecated (?)
2.4 AOSiP: no need for Gapps. XDA thread.
2.5 Invictrix. Gapps are built in. XDA thread
3. Choose the root method and download the .zip files: Magisk (suggested) or LineageOS SU Addon. Move the .zip files to phone. Note: if you bootloop on Magisk, most probably you’re flashing a wrong/different version of Magisk or you did not reboot between flashing ROM/Gapps and Magisk. Note: SuperSu is deprecated.
4. Reboot into TWRP:
Code:
adb reboot recovery
Then flash the ROM. It will be flashed in two steps only in the “other” slot. We have two slots, A and B. Our phone can be upgraded on-the-fly because the update is always applied to the slot not booted, the “other” slot. Then, immediately, flash the .zip TWRP or you will lose it.
5. Go to Reboot menu of TWRP and reboot into bootloader. Then, in the folder with adb/fastboot binaries (see 1.2 above), you need to wipe data (including sdcard) with the following commands:
Code:
fastboot devices
fastboot -w
6. Now you need to reboot the phone into System using the buttons volume up/down and confirming with the Power button (or typing fastboot reboot into the command line windows). You’ll be with an AOSP ROM and TWRP.
7. Once into the phone, enable the Developer Options clicking 7 times over the version (About section in the settings). Go to Developer Options and enable USB debugging if you intend to dirty flash ROM updates.
8. Reboot into TWRP again, flash Magisk (your settings and modules will be preserved). Note: if you bootloop on Magisk, remember it is mandatory to reboot between ROM flash (step 4 above) and GApps/Addon flash due to verity/slot-swap logic.
9. A good place to read what is not working is in the section known problems of LineageOS.
D. Dirty flashing AOSP ROM updates
1. If you follow all the processes above, you can dirty flash updates because you have:
1.1 Motorola drivers installed.
1.2 Specific adb/fastboot files for our phone and an USB 2.0 port in a Windows computer (some users report that USB 3.0 will also work).
1.3 Unlocked bootloaders (Process A above).
1.4 Permanent TWRP running and TWRP .zip file placed inside your phone and ready to be flashed again.
1.5 An AOSP ROM already running.
1.6 Developer Options and USB debugging enabled.
1.7 If you're using TWRP older than 3.2.2-2, disable disable PIN/gestures/fingerprinting. Also, most probably, ROMs after July 20th, 2018 cannot be flashed in older TWRP.
1.8 Enough battery in your phone (80%)
2. Download your ROM .zip update, copy it into the phone sdcard and reboot your phone into TWRP. See download links here.
3. Within TWRP you should flash (install) things in the following order:
3.1 ROM update .zip file. Remember that, at this time, the update will be flashed int the other slot and inside phone you’ll have both the system before update (in the booted slot) and updated ROM in the other slot.
3.2 TWRP .zip file (step 1.4 above) once again (do not skip this step or you’ll bootloop!).
4. Reboot to System: if you skip this step, you’ll bootloop.
5. Reboot into TWRP again, flash Magisk (your settings and modules will be preserved) or LineageOS SU Addon .zip file. Note: if you bootloop on Magisk, most probably you’re flashing a wrong/different version of Magisk. I suggest v16.0 and, after you got rooted with 16.0, you can update. It is mandatory to reboot between ROM flash (step 4 above) and GApps/Addon flash due to verity/slot-swap logic.
Note: SuperSu is deprecated.
6. Wipe Dalvik/ART cache: go to Wipe menu of TWRP > Advanced Wipe > Dalvik/ART Cache only.
7. Reboot your phone into System (ROM) will use the “other” slot, the one with the updated ROM.
8. You can use XPosed installer app (and reboot).
9. Now you can add your PIN, fingerprint, gestures back until next flashing.
E. Recovering from soft bricks or returning to Stock
If you’re reading this is because you already unlock your bootloader (see guide A) and anything went wrong, but you still can boot your phone into bootloader. Plug your phone and get enough battery (even if you do not see any charging signal).
1. Install the Motorola drivers and the specific adb/fastboot files for our phone. Remember, follow the rules because our device is tricky!
1.1) Do not use other adb/fastboot binaries: we cannot guarantee they will work.
1.2) You need to use a USB 2.0 port of your computer (some users report that USB 3.0 will also work).
2. Download the latest firmware for your model:
- Retail (XT1789-05) (Europe/Brazil).
- Other models (branded): ATT, Sprint, T-Mobile (TMO), USC, Verizon.
- Note: NPXS26 versions stand for Nougat and OPXS27 for Oreo. You do not need Nougat versions for anything.
3. Extract the zip contents to a blank folder in your computer.
4. Download the FlashAll_XT1789-05.zip file (it should work for other Motorola Z2 Force models as well), extract the content and move all files to the same firmware folder (step 2 above). Be sure to overwrite any file (if needed).
5. Run the Preparation.bat file there to generate the flashfile.bat file that will send the commands to the phone. Credits: the original preparation files were from RootJunky (can be downloaded here) and include more options that we do not need for our purpose here. Also, it includes adb/fastboot binaries that could not work with our phone.
6. Reboot the phone into the bootloader (see adb command below or power + volume down). Open a command line window in the firmware folder (step 5 above), test the connection and execute the flashfile.bat file generated on step 5.
Code:
adb reboot bootloader
fastboot devices
flashfile.bat
Never ever unplug the device from the USB 2.0 port while flashing the firmware. This could cause a hard brick and your device will be dead.
7. There is a pause at the end. You should review if everything went fine (or even click on the menu of the command line window, select all and copy&paste the contents in a .txt file for further help/revision).
8. Reboot your phone into system (ROM) and do not forget, later, to enable the Developer Options and USB debugging again.
Note: if you hard brick, I suggest you be prepared to follow the Unbrick Qualcomm mobiles with Step-by-step guide or the Unbrick All Qualcomm Snapdragon’s from Qualcomm HS-USB QDLoader 9008 guide, but I never tested them myself. You can also use Qualcomm Flash Image Loader (QFIL) tool. Maybe these Latest 2017 Qualcomm Diag QD-Loader Windows 10 Drivers signed will help you.
F. Oreo ROM features comparison
This is a table for Oreo ROM features comparison for Motorola Z2 Force - nash.
I would like to receive feedback and updates from the users, as I can't keep changing from one ROM to another and they get new features, updates, improvements, etc.
I consider Lineage OS 15.1 our stock ROM regarding to customization. So, it's not listed there.
Legend:
Code:
X = Feature present
XX = ROM excels in this particular feature (in my opinion).
If you want to move your Motorola Z2 Force to Project Treble ROMs, please, check this guide.
Here is a list of the ROMs that are waiting for you.
I came back to stock ROM. the problem is that it gets stuck in the initial configurations of the android trying to find a wifi network, to continue the configuration, without success, because I see in fastboot that the baseband is unknown, and I also can not install any rom, or recovery image because I have the following message in fastboot: FLASHING_LOCKED. and since I can not get past the initial android settings, I also can not unlock the developer options to enable OEM unlocking. now I'm standing in a rom that does not leave the initial configuration, it does not connect to any network and a fastboot that does not let me install anything. and I also tried the recovery mode and even tried to install an update via sideload, without success. I do not know what else to do if you can give me a light.
renanjones said:
I came back to stock ROM. the problem is that it gets stuck in the initial configurations of the android trying to find a wifi network, to continue the configuration, without success, because I see in fastboot that the baseband is unknown, and I also can not install any rom, or recovery image because I have the following message in fastboot: FLASHING_LOCKED. and since I can not get past the initial android settings, I also can not unlock the developer options to enable OEM unlocking. now I'm standing in a rom that does not leave the initial configuration, it does not connect to any network and a fastboot that does not let me install anything. and I also tried the recovery mode and even tried to install an update via sideload, without success. I do not know what else to do if you can give me a light.
Click to expand...
Click to collapse
I see two possible scenarios:
1. Your bootloader is locked (yet) (see guide A).
2. Your in a "false locked" situation that, maybe, could be solved by resetting data via recovery or in bootloader (with the command: fastboot -w).
Great tutorial, but I did not get 4g in any of the roms, only 3g
Gutto said:
Great tutorial, but I did not get 4g in any of the roms, only 3g
Click to expand...
Click to collapse
I got 4G in any ROM... AOSIP, DU or Invictrix...
Are you using a branded (carrier) phone? If not, maybe you should return to stock (to recover any changes on partitions).
Technical said:
I got 4G in any ROM... AOSIP, DU or Invictrix...
Are you using a branded (carrier) phone? If not, maybe you should return to stock (to recover any changes on partitions).
Click to expand...
Click to collapse
My cell phone and Sprint, I did every process that you indicated, but not 4G
So I followed the instructions as noted, as soon as I got to the root installation part, it started throwing a "cannot mount /system" error. I thought a reboot would solve the issue, but now I think I'm bricked. Can't boot into anything, all I can do is plug my phone in and listen to it keep disconnecting every 10 seconds or so. The phone had booted up fine prior to starting the installation process, and I don't see how just a bad ROM install is preventing me from getting into either bootloader or recovery. Any advice?
For clarity, i'm unable to use QBOOT to do anything since after it hits the "powered on" state I'm assuming it's in, it just resets and does the same thing over and over again
shalpp said:
So I followed the instructions as noted, as soon as I got to the root installation part, it started throwing a "cannot mount /system" error. I thought a reboot would solve the issue, but now I think I'm bricked. Can't boot into anything, all I can do is plug my phone in and listen to it keep disconnecting every 10 seconds or so. The phone had booted up fine prior to starting the installation process, and I don't see how just a bad ROM install is preventing me from getting into either bootloader or recovery. Any advice?
For clarity, i'm unable to use QBOOT to do anything since after it hits the "powered on" state I'm assuming it's in, it just resets and does the same thing over and over again
Click to expand...
Click to collapse
Have you tried holding vol dwn + pwr btn to force it into bootloader mode? If you can get there, then you can use the keys to get to recovery and try a factory reset. If that don't work, go back to bootloader mode and try flashing back to stock. Might double check that the battery has plenty of charge.
41rw4lk said:
Have you tried holding vol dwn + pwr btn to force it into bootloader mode? If you can get there, then you can use the keys to get to recovery and try a factory reset. If that don't work, go back to bootloader mode and try flashing back to stock. Might double check that the battery has plenty of charge.
Click to expand...
Click to collapse
I'm unable to get the phone out of qboot (or whatever it's called). I've tried using a blank-flash but all that happens is device restarts as made evident by the "device disconnect" sound playing every few seconds. The phone had around 80% when I started the process. Should I just let it die and try loading into BL after a few hours of this thing power cycling itself?
shalpp said:
I'm unable to get the phone out of qboot (or whatever it's called). I've tried using a blank-flash but all that happens is device restarts as made evident by the "device disconnect" sound playing every few seconds. The phone had around 80% when I started the process. Should I just let it die and try loading into BL after a few hours of this thing power cycling itself?
Click to expand...
Click to collapse
It's weird that it is power cycling like that. Have you tired unplugging the phone and booting? Whether it's recovery, bootloader, qboot; you need to get to one place or the other if possible because power cycling won't allow you to do anything. If you can get a stable boot in any mode I would suggest moving your cable to another port so any corruptions aren't a factor anymore. I don't think a drain will resolve anything, but I've never heard anyone mention power cycling like that.
41rw4lk said:
It's weird that it is power cycling like that. Have you tired unplugging the phone and booting? Whether it's recovery, bootloader, qboot; you need to get to one place or the other if possible because power cycling won't allow you to do anything. If you can get a stable boot in any mode I would suggest moving your cable to another port so any corruptions aren't a factor anymore. I don't think a drain will resolve anything, but I've never heard anyone mention power cycling like that.
Click to expand...
Click to collapse
Power cycling is just an assumption since regardless of whatever port its in it keeps an endless loop of connect, disconnect". Basically after rebooting the device after attempting to install the ROM is when it went black and started not doing anything other than connect, disconnect
shalpp said:
Power cycling is just an assumption since regardless of whatever port its in it keeps an endless loop of connect, disconnect". Basically after rebooting the device after attempting to install the ROM is when it went black and started not doing anything other than connect, disconnect
Click to expand...
Click to collapse
When it's trying to connect do you have a pop up on your pc showing what it sees the phone as? Does it say nash fastboot, or 9008, Z2? That might give some idea of where it's failing.
41rw4lk said:
When it's trying to connect do you have a pop up on your pc showing what it sees the phone as? Does it say nash fastboot, or 9008, Z2? That might give some idea of where it's failing.
Click to expand...
Click to collapse
It appears as Qualcomm 9008
It only starts the loop after starting a blankflash. That's about the only response I get out of the device, otherwise it does absolutely nothing, no combination of buttons do anything
Edit: Confirmed connect/disconnect on another machine with the same driver configuration
Code:
/*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns.
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
A guide to unlock bootloader, flash a custom recovery and root your Redmi Note 8/8T device :
1. UNLOCKING BOOTLOADER :
Backup your data first. Unlocking will erase your data.
- Enable Developer Options in your phone by tapping the "MIUI Version" 7 times in About Phone.
- Go to Settings > Additional Settings > Developer Options.
- Enable OEM Unlocking, USB Debugging and USB Debugging (Security Settings) .
- Also add account in Mi Unlock Status (Can be found in Developer Options).
- Install the required ADB and Fastboot drivers in your PC from here.
- Download Mi Unlock to PC from here, and sign in with your Mi Account.
- Shut down your phone manually, and hold volume down key and power button to enter Fastboot mode.
- Connect your phone to PC using USB cable and click "Unlock" in Mi Unlock Tool.
- You will be given a specific time (168 hours usually).
- Wait for the given time. Make sure to use your phone and don't log out of your mi account from the phone or reset your device.
- Once waiting time is over, redo Unlock process.
- Your phone will be unlocked successfully.
2. FLASHING TWRP :
- Install the required ADB and Fastboot drivers in your PC if not already in step 1. from here.
- Download TWRP from here.
- Put that TWRP in the ADB and Fastboot installed folder (mostly C:\Program Files (x86)\Minimal ADB and Fastboot).
- Rename that recovery(TWRP file) to "recovery" for convenience (optional).
- Click on Start Menu, type cmd
- Right click and select Run as administrator
- Then type:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
- Now Connect your phone to PC With USB Debugging on (keep phone on).
- Type:
Code:
adb devices
and accept the pop up on phone's screen.
- Now reboot your phone to Fastboot mode either manually by shutting down phone and then holding volume down key and power button or by:
Code:
adb reboot bootloader
- Once in Fastboot mode type:
Code:
fastboot devices
- Your device ID will be visible on Screen.
- Then type(hit ENTER after each line):
Code:
fastboot flash recovery recovery.img
fastboot boot recovery.img
- Now your phone will boot into TWRP.
OPTIONAL STEPS (Not Recommended): Encryption is always recommended for better security. However if you don't want encryption in your device, follow these steps. Again, not recommended.
- In TWRP go to Wipe and select Format Data(don't go to advanced). Type yes and format data. [This process will format all your data so make sure your data is backed up]
- Go back to TWRP home and Reboot > Recovery.(Don't reboot system or else you will have to repeat whole process again).
- Done
3. ROOTING :
- Download Magisk zip to PC from here.
- Download Universal DM-Verity and ForceEncrypt disabler from here. (Only required if you followed optional steps.)
- When in TWRP transfer the file(s) to phone and go to Install.
- Here select Magisk zip file and swipe to flash.
- Then select Universal DM-Verity and ForceEncrypt disabler zip and swipe to flash(Make sure to flash this at last or else phone won't boot). (Only required if you followed optional steps.)
- Reboot system.
- Done. Debloat. Enjoy
Links
1. Minimal ADB and Fastboot
2. MI Unlock Tool
3. TWRP
4. Magisk
5. Universal DM-Verity and ForceEncrypt Disabler (OPTIONAL)
If this helped you then hit the Thanks Button. Good Luck.
Thanks for guide. Anyway, latest versions of Windows 10 don't have "Open command prompt here" option. Instead, they have PowerShell. I don't know how PowerShell will react with ADB, so, for these Windows 10 is better to:
Click on Start Menu, type cmd
Right click with mouse and choose "Run as administrator"
Type these commands (hit ENTER after each line):
cd\
cd "program files (x86)
cd "minimal adb and fastboot"
Now the user is on right folder.
--------------------------------
A question: I'm on stock ROM and have a Google Apps account on my phone, and I'm currently using stock Second Space feature to handle it. As encryption is mandatory to use a Google Apps account, I can't use "disable encryption". Or will Second Space be encrypted even if "main account" isn't? There are any problems to use Magisk with encrypted phone?
romulocarlos said:
Thanks for guide. Anyway, latest versions of Windows 10 don't have "Open command prompt here" option. Instead, they have PowerShell. I don't know how PowerShell will react with ADB, so, for these Windows 10 is better to:
Click on Start Menu, type cmd
Right click with mouse and choose "Run as administrator"
Type these commands (hit ENTER after each line):
cd\
cd "program files (x86)
cd "minimal adb and fastboot"
Now the user is on right folder.
--------------------------------
A question: I'm on stock ROM and have a Google Apps account on my phone, and I'm currently using stock Second Space feature to handle it. As encryption is mandatory to use a Google Apps account, I can't use "disable encryption". Or will Second Space be encrypted even if "main account" isn't? There are any problems to use Magisk with encrypted phone?
Click to expand...
Click to collapse
totally forgot about the powershell thing . Thanks to you I updated my post.
What do you mean by Google Apps account. Do you mean google account??. I'm using a decrypted phone right now and google apps work just fine with decryption too.
There aren't any problems to use Magisk with encrypted phone(I used it myself for a good week or so before decrypting).
Unfortunately as of now I don't have the answer to your second space question. Will let you know once I get it myself.
the_weird_aquarian said:
totally forgot about the powershell thing . Thanks to you I updated my post.
What do you mean by Google Apps account. Do you mean google account??. I'm using a decrypted phone right now and google apps work just fine with decryption too.
There aren't any problems to use Magisk with encrypted phone(I used it myself for a good week or so before decrypting).
Unfortunately as of now I don't have the answer to your second space question. Will let you know once I get it myself.
Click to expand...
Click to collapse
You must update the command to change folder on cmd. Put the path in quotes, or else the users will receive an error!
Code:
cd "C:\Program Files (x86)\Minimal ADB and Fastboot"
About Google Apps, is also called Google for Work, or Work Profile. Is MANDATORY to have the phone encrypted, or the account won't sync.
Thank you for feedback!
romulocarlos said:
You must update the command to change folder on cmd. Put the path in quotes, or else the users will receive an error!
Code:
cd "C:\Program Files (x86)\Minimal ADB and Fastboot"
About Google Apps, is also called Google for Work, or Work Profile. Is MANDATORY to have the phone encrypted, or the account won't sync.
Thank you for feedback!
Click to expand...
Click to collapse
the command works fine without quotes too man, checked it myself. both ADB and Fastboot commands work fine.
I'll check about Google for work issue. :good:
the_weird_aquarian said:
the command works fine without quotes too man, checked it myself. both ADB and Fastboot commands work fine.
I'll check about Google for work issue. :good:
Click to expand...
Click to collapse
You're right. Tested right now and worked. Maybe newer Win10 versions are "smarter" than older... who knows...
Well, about the second space, thanks, but you don't need to check with an Google Apps account.
If your phone is decrypted, just open Second Space, configuring it for first time use as you like. Then, on Second Space, go Settings -> Password and security -> privacy. Check if encryption is active.
Thanks again!
Thank you for this awesome tutorial.. now i m in "waiting mode" for unlocking bootloader ?
Just one dummy question for me sir .. can i root my device while i am using stock rom (miui 11 global) ? Or i have to install custom rom ? Thank you ?
Mozar3lla said:
Thank you for this awesome tutorial.. now i m in "waiting mode" for unlocking bootloader
Just one dummy question for me sir .. can i root my device while i am using stock rom (miui 11 global) ? Or i have to install custom rom ? Thank you
Click to expand...
Click to collapse
Yes you can root on stock rom. Rooting is not rom specific. You can root on any rom.
Hope it helps.
@the_weird_aquarian thanks for the tutorial mate, do i have to flash dm verity everytime i flash magisk????
and also I found this tutorial and software for flashing twrp, is it ok to use this software too?
https://github.com/XiaomiWiki/XiaomiWiki.github.io/blob/master/wiki/Flash_TWRP_and_custom_ROMs.md
shayanb2004 said:
@the_weird_aquarian thanks for the tutorial mate, do i have to flash dm verity everytime i flash magisk????
and also I found this tutorial and software for flashing twrp, is it ok to use this software too?
https://github.com/XiaomiWiki/XiaomiWiki.github.io/blob/master/wiki/Flash_TWRP_and_custom_ROMs.md
Click to expand...
Click to collapse
dm-verity is just required to stop the stock mi recovery from coming back. Hence it's just for MIUI based roms. However disable forceencrypt helps you get rid of force encryption of miui or other custom roms(so that you can access internal storage from recovery too if you are flashing something). The zip provided has both features in one file. Just rename the file to whatever you want to disable(see instructions here).
Regarding that tool on github, I have never used it personally as I like doing each step myself so if something goes wrong I know the last working step and from there I can figure out what went wrong. Using the tool might or might not work for you. Use at your own risk.
the_weird_aquarian said:
dm-verity is just required to stop the stock mi recovery from coming back. Hence it's just for MIUI based roms. However disable forceencrypt helps you get rid of force encryption of miui or other custom roms(so that you can access internal storage from recovery too if you are flashing something). The zip provided has both features in one file. Just rename the file to whatever you want to disable(see instructions here).
Regarding that tool on github, I have never used it personally as I like doing each step myself so if something goes wrong I know the last working step and from there I can figure out what went wrong. Using the tool might or might not work for you. Use at your own risk.
Click to expand...
Click to collapse
Thanks for the info mate
damn I have to wait a whole week to unlock my bootlaoder
shayanb2004 said:
Thanks for the info mate
damn I have to wait a whole week to unlock my bootlaoder
Click to expand...
Click to collapse
Yeah you gotta wait for a week. Weird Xiaomi policy. Can't help you with that though.
the_weird_aquarian said:
Yeah you gotta wait for a week. Weird Xiaomi policy. Can't help you with that though.
Click to expand...
Click to collapse
yea too bad... I cant use it for a week cuz all of my data is gonna get wiped again
I need to transfer all my data and apps from my old phone with migrate
so I will wait
shayanb2004 said:
yea too bad... I cant use it for a week cuz all of my data is gonna get wiped again
I need to transfer all my data and apps from my old phone with migrate
so I will wait
Click to expand...
Click to collapse
Make sure to atleast keep your phone turned on.
I will try it to root my device to get rid off the annoying ads. But my ordered cell phone does not come yet and I still patient to wait it.
Question :
1. Can I use the Mi Mover application to migrate data from an old cellphone (Redmi Note 5) to Redmi Note 8?
2. Whether migrating data (via Mi Mover) before root or do data migration after root ? Because my old RN5 already rooted, have it TWRP and Magisk too.
AMJ_Vario said:
I will try it to root my device to get rid off the annoying ads. But my ordered cell phone does not come yet and I still patient to wait it.
Question :
1. Can I use the Mi Mover application to migrate data from an old cellphone (Redmi Note 5) to Redmi Note 8?
2. Whether migrating data (via Mi Mover) before root or do data migration after root ? Because my old RN5 already rooted, have it TWRP and Magisk too.
Click to expand...
Click to collapse
I suggest you to move AFTER you root your new device, because to have root, you must unlock the bootloader. And when you unlock the bootloader, all data is lost.
romulocarlos said:
I suggest you to move AFTER you root your new device, because to have root, you must unlock the bootloader. And when you unlock the bootloader, all data is lost.
Click to expand...
Click to collapse
So its mean, first the device RN8 must do unlock the bootloader, then root it, next is migration data from old cellphone.
Is that the right way?
Is the migration data from old cellphone, will included the third party application from that old cellphone too? Is it will compatible on RN8?
Or just migration important data only (like email account + Mi account + contact + notes, etc) and the application 3rd party should be installed one by one on the RN8 exacly as RN5?
Sorry for asked to much becuse I dont want to make a mistake on the new devices.
Just guide me into the right way, please..
Thanks for the respond..:good:
AMJ_Vario said:
So its mean, first the device RN8 must do unlock the bootloader, then root it, next is migration data from old cellphone.
Is that the right way?
Is the migration data from old cellphone, will included the third party application from that old cellphone too? Is it will compatible on RN8?
Or just migration important data only (like email account + Mi account + contact + notes, etc) and the application 3rd party should be installed one by one on the RN8 exacly as RN5?
Sorry for asked to much becuse I dont want to make a mistake on the new devices.
Just guide me into the right way, please..
Thanks for the respond..:good:
Click to expand...
Click to collapse
In fact, I never used Mi Mover. As each device has its features, I prefer to install apps one by one. My data is on cloud, so for me is easyer.
I suggest you to do the transfer, only for tests, just after you receive your phone. These videos may help you also:
https://www.youtube.com/watch?v=shf-i8z86Ms and https://www.youtube.com/watch?v=ql-f88qllrE
@the_weird_aquarian mate have you tested orangefox recovery?
I'm hearing a lot about it, but donno anything :S
thinking if it is good instead of twrp or not?
shayanb2004 said:
@the_weird_aquarian mate have you tested orangefox recovery?
I'm hearing a lot about it, but donno anything :S
thinking if it is good instead of twrp or not?
Click to expand...
Click to collapse
yes so I have recently flashed orangefox about 2 weeks ago or something. I personally don't use anything other than official twrp, but I flashed orangefox because of it's miui OTA update feature. You can flash if you are planning on staying on stock rom with a decrypted device, as I have dirty flashed stock rom with my decrypted device but it always ends up in bootloop with official twrp. I have to format data everytime. Surprisingly Orangefox solves this issue. Also if you are a fan of theming then it provides a few custom fonts, colors and themes. However if your device is encrypted there's absolutely no reason to switch from official to any other recovery unless you want to customize the looks of your recovery.
In this guide, ill be showing you how to install a custom rom onto your OnePlus 7T Pro device. Ill be assuming your phone is completely stock and you haven't done any modifications. This is done at your own risk, i am not responsible for corrupted images, bricked devices etc.
*NOTE: This guide is for the OnePlus 7T Pro only*
What you will need:
A windows PC - idk buy one lol? *NOTE* You will need a Windows 10 PC, Windows 11 can't recognize your phone in fastboot for some reason. You can manually install the adb drivers to the PC If you must use windows 11.
Platform tools SDK - https://developer.android.com/studio/releases/platform-tools
USB cable that came with the phone
Derpfest ROM - https://sourceforge.net/projects/derpfest/files/hotdog/ (This was made by @NurKeinNeid, It's truly an amazing rom and would recommend it to anyone who wants android 12 on their devices! XDA forum for the ROM - https://forum.xda-developers.com/t/rom-12-0-derpfest-for-oneplus-7t-pro-official-hotdog.4250469/ ) Download the .img.zip, not just the .zip!
Orange Fox Recovery - https://orangefox.download/device/hotdog
Payload Dumper - https://androidfilehost.com/?fid=818070582850510260
Custom Flashing Script - https://github.com/AlaistairP/Install-Scripts
Step 1: Unlocking your Bootloader.
(i) In order to install software onto your phone you must have an unlocked bootloader. To start, go to settings - about phone - tap on the build number 7 times, input your password and developer options should then be enabled.
(ii) Then go into the main settings page - system - developer options. Enable the 'OEM UNLOCKING' feature. After that scroll down and enable USB Debugging. At this stage, plug your device into your pc. A dialogue should come up to allow the computer to connect to your phone, click yes.
(iii) Now on your computer, navigate to the platform tools folder you downloaded, in the main directory with all the files, in the search bar type cmd and press enter. You now need to boot your phone into fastboot mode. To do this, turn your phone off. Then, hold the power button with the volume up and down button! You should see a menu with green text saying 'Start' at the top.
(iv) Plug your phone into your computer, and in the cmd menu you opened, type 'fastboot devices', you should see the word fastboot followed by a string of numbers. Now type - 'fastboot oem unlocking' A dialogue will appear on your phone, using the volume keys select the option to unlock the bootloader. *NOTE - ALL DATA WILL BE REMOVED'
Step 2: Flashing a custom recovery
Reboot your phone to fastboot, then connect your phone to your pc. Type in 'fastboot reboot fastboot' your device should reboot into 'fastbootd' Now using the recovery.img file you downloaded from Firefox, type the following command, `'fastboot flash recovery 'PATH TO RECOVERY.IMG FILE'
Once the file has flashed, restart your phone into fastboot mode and using the volume keys, navigate to recovery mode. You should now boot into Orange Fox recovery. Now, in orangefox, go to Wipe - Format Data - then type yes and wait for the process to finish.
Voila!
Step 3: Flashing the ROM!
Open your downloaded version of derpfest, you should see a file called payload.bin, place that into the payload dumper input folder, then run the programme and wait for it complete, you should have loads of .img files. Copy all of these into your platform tools folder! Now download the custom script and place that into the platform tool folder as well.
Reboot your phone into fastboot mode, and once again type 'fastboot reboot fastboot' Once you're in fastbootd mode, right click the flash-all.bat script and run as admin, click more info if you have microsoft defender and click run anyway, The rest is done in the script!
*HOW TO UPDATE*
Once you have downloaded and extracted the new files from the most recent payload.bin file which the dev releases, copy these files into your platform-tools folder. You need to make sure there are no .img files from the old Rom remaining. Now, connect your phone to your pc. Open a cmd windows inside the platform-tools window and type 'adb reboot fastboot', once your phone has entered fastboot, type 'fastboot reboot fastbootd' Once your in fastbootd, simply run the update.bat script and voila!
After, reboot your phone and you should load into your new Android 12 OS!
If you have any questions please dont hesitate to ask!
If i have made any mistakes in this guide, or you guys think i should make any changes, let me know, im new to this!
*NOTE - I intend to make a full video walk through soon, ill have the youtube video linked here in the near future*
astroarchcraft said:
In this guide, ill be showing you how to install a custom rom onto your OnePlus 7T Pro device. Ill be assuming your phone is completely stock and you haven't done any modifications. This is done at your own risk, i am not responsible for corrupted images, bricked devices etc.
*NOTE: This guide is for the OnePlus 7T Pro only*
What you will need:
A windows PC - idk buy one lol?
Platform tools SDK - https://developer.android.com/studio/releases/platform-tools
USB cable that came with the phone
Derpfest ROM - https://sourceforge.net/projects/derpfest/files/hotdog/ (This was made by @NurKeinNeid, It's truly an amazing rom and would recommend it to anyone who wants android 12 on their devices! XDA forum for the ROM - https://forum.xda-developers.com/t/rom-12-0-derpfest-for-oneplus-7t-pro-official-hotdog.4250469/ ) Download the .img, not zip!
Orange Fox Recovery - https://orangefox.download/device/hotdog
Payload Dumper - https://androidfilehost.com/?fid=818070582850510260
Custom Flashing Script - https://github.com/astroarchcraft/A12script/tree/main
Step 1: Unlocking your Bootloader.
(i) In order to install software onto your phone you must have an unlocked bootloader. To start, go to settings - about phone - tap on the build number 7 times, input your password and developer options should then be enabled.
(ii) Then go into the main settings page - system - developer options. Enable the 'OEM UNLOCKING' feature. After that scroll down and enable USB Debugging. At this stage, plug your device into your pc. A dialogue should come up to allow the computer to connect to your phone, click yes.
(iii) Now on your computer, navigate to the platform tools folder you downloaded, in the main directory with all the files, in the search bar type cmd and press enter. You now need to boot your phone into fastboot mode. To do this, turn your phone off. Then, hold the power button with the volume up and down button! You should see a menu with green text saying 'Start' at the top.
(iv) Plug your phone into your computer, and in the cmd menu you opened, type 'fastboot devices', you should see the word fastboot followed by a string of numbers. Now type - 'fastboot oem unlocking' A dialogue will appear on your phone, using the volume keys select the option to unlock the bootloader. *NOTE - ALL DATA WILL BE REMOVED'
Step 2: Flashing a custom recovery
Reboot your phone to fastboot, then connect your phone to your pc. Type in 'fastboot reboot fastboot' your device should reboot into 'fastbootd' Now using the recovery.img file you downloaded from Firefox, type the following command, `'fastboot flash recovery 'PATH TO RECOVERY.IMG FILE'
Once the file has flashed, restart your phone into fastboot mode and using the volume keys, navigate to recovery mode. You should now boot into Orange Fox recovery. Now, in orangefox, go to Wipe - Format Data - then type yes and wait for the process to finish.
Voila!
Step 3: Flashing the ROM!
Open your downloaded version of derpfest, you should see a file called payload.bin, place that into the payload dumper input folder, then run the programme and wait for it complete, you should have loads of .img files. Copy all of these into your platform tools folder! Now download the custom script and place that into the platform tool folder as well.
Reboot your phone into fastboot mode, and once again type 'fastboot reboot fastboot' Once you're in fastbootd mode, right click the script and run as admin, click more info if you have microsoft defender and click run anyway, The rest is done in the script!
After, reboot your phone and you should load into your new Android 12 OS!
If you have any questions please dont hesitate to ask!
If i have made any mistakes in this guide, or you guys think i should make any changes, let me know, im new to this!
Click to expand...
Click to collapse
I really appreciate the time and work you put into it. Thank you very much!
Btw I will release new build tonight. Now I can link to this post in the update announcement as well.
NurKeinNeid said:
I really appreciate the time and work you put into it. Thank you very much!
Btw I will release new build tonight. Now I can link to this post in the update announcement as well.
Click to expand...
Click to collapse
No Problem, Quite satisfying to write actually! Thanks so much for all the effort you put into the ROM, Best one I have used on my phone yet! Looking forward to the new build
Hi Team, this method with flashing Orange Fox recovery and formatting Data, do you know if will enable backup/restore and viewable sdcard for Android 12/Derp?
The only thing I haven't been willing to try is formatting/converting Data, as I've re-setup my phone about 5 times now trying various methods over several days trying to get a working custom recovery for Derp
somemadcaaant said:
Hi Team, this method with flashing Orange Fox recovery and formatting Data, do you know if will enable backup/restore and viewable sdcard for Android 12/Derp?
The only thing I haven't been willing to try is formatting/converting Data, as I've re-setup my phone about 5 times now trying various methods over several days trying to get a working custom recovery for Derp
Click to expand...
Click to collapse
Hey I'm not sure about the backup/restore, but after formatting the drive, they'll no longer be encrypted so Orange Fox should be able to read the data on your drive.
Thought as much, time for another reinstall. Thanks again have a thumbs up.
Hi Astroarchcraft, thank you for this guide! If you only put it out 2 days earlier you'd have saved me from a soft brick! (from which I recovered luckily ahahh)
Anyway, could you please also add the guide on how to update to a newer build? Is there a way to do it without losing all data? Thanks!
Looking forward to move to the new 2022-01-07 build!
Instead of going to fastbootd after flashing orangefox recovery, it just goes to orangefox's fastboot mode and did the script there. Should it work the same? (I'm still waiting for the flash to finish, will update what will happen after) Thanks!
Edit: Looks like it works just the same even if you run flash all script inside orangefox recovery fastboot.
Anyways, thanks for the nice guide. Really helpful! I know i've been flashing ROMs ever since back then. But its always nice to have a guide here and there. So kudos to you for making this one. Thanks!
What if I'm on a A12 AOSP ROM and want to try Derpfest ROm? can I just flash it in TWRP or are there any instructions to follow?
iSyncX said:
Instead of going to fastbootd after flashing orangefox recovery, it just goes to orangefox's fastboot mode and did the script there. Should it work the same? (I'm still waiting for the flash to finish, will update what will happen after) Thanks!
Edit: Looks like it works just the same even if you run flash all script inside orangefox recovery fastboot.
Anyways, thanks for the nice guide. Really helpful! I know i've been flashing ROMs ever since back then. But its always nice to have a guide here and there. So kudos to you for making this one. Thanks!
Click to expand...
Click to collapse
Yup, orange Fox fastboot is fastbootd if you do it from the bootloader
salomaoa said:
What if I'm on a A12 AOSP ROM and want to try Derpfest ROm? can I just flash it in TWRP or are there any instructions to follow?
Click to expand...
Click to collapse
Nope, it's a fastboot ROM so it must be done via fastboot!
Ninotzz said:
Hi Astroarchcraft, thank you for this guide! If only you put it out 2 days earlier you'd have saved me from a soft brick! (from which I recovered luckily ahahh)
Anyway, could you please also add the guide on how to update to a newer build? Is there a way to do it without losing all data? Thanks!
Looking forward to move to the new 2022-01-07 build!
Click to expand...
Click to collapse
I'll make a guide later, but for the moment, all you need to do it download the update files, instead of the original files, and don't erase the data when given the option in the script!
astroarchcraft said:
I'll make a guide later, but for the moment, all you need to do it download the update files, instead of the original files, and don't erase the data when given the option in the script!
Click to expand...
Click to collapse
So won't I have problems with my data being encrypted by the previous version of the ROM? Will the new one be able to read it anyway?
Cheers ✌
I've updated and it was perfect, my recommendation for the moment is to go to the how to update section on the official ROM page and do what is said from there, like I said, I'll make a guide as soon as I get a chance
astroarchcraft said:
I've updated and it was perfect, my recommendation for the moment is to go to the how to update section on the official ROM page and do what is said from there, like I said, I'll make a guide as soon as I get a chance
Click to expand...
Click to collapse
Unfortunately NurKein removed it from the post in favor of the link to your guide So I'll try to follow what you told me in this thread for now
astroarchcraft said:
In this guide, ill be showing you how to install a custom rom onto your OnePlus 7T Pro device. Ill be assuming your phone is completely stock and you haven't done any modifications. This is done at your own risk, i am not responsible for corrupted images, bricked devices etc.
*NOTE: This guide is for the OnePlus 7T Pro only*
What you will need:
A windows PC - idk buy one lol?
Platform tools SDK - https://developer.android.com/studio/releases/platform-tools
USB cable that came with the phone
Derpfest ROM - https://sourceforge.net/projects/derpfest/files/hotdog/ (This was made by @NurKeinNeid, It's truly an amazing rom and would recommend it to anyone who wants android 12 on their devices! XDA forum for the ROM - https://forum.xda-developers.com/t/rom-12-0-derpfest-for-oneplus-7t-pro-official-hotdog.4250469/ ) Download the .img, not zip!
Orange Fox Recovery - https://orangefox.download/device/hotdog
Payload Dumper - https://androidfilehost.com/?fid=818070582850510260
Custom Flashing Script - https://github.com/astroarchcraft/A12script/tree/main
Step 1: Unlocking your Bootloader.
(i) In order to install software onto your phone you must have an unlocked bootloader. To start, go to settings - about phone - tap on the build number 7 times, input your password and developer options should then be enabled.
(ii) Then go into the main settings page - system - developer options. Enable the 'OEM UNLOCKING' feature. After that scroll down and enable USB Debugging. At this stage, plug your device into your pc. A dialogue should come up to allow the computer to connect to your phone, click yes.
(iii) Now on your computer, navigate to the platform tools folder you downloaded, in the main directory with all the files, in the search bar type cmd and press enter. You now need to boot your phone into fastboot mode. To do this, turn your phone off. Then, hold the power button with the volume up and down button! You should see a menu with green text saying 'Start' at the top.
(iv) Plug your phone into your computer, and in the cmd menu you opened, type 'fastboot devices', you should see the word fastboot followed by a string of numbers. Now type - 'fastboot oem unlocking' A dialogue will appear on your phone, using the volume keys select the option to unlock the bootloader. *NOTE - ALL DATA WILL BE REMOVED'
Step 2: Flashing a custom recovery
Reboot your phone to fastboot, then connect your phone to your pc. Type in 'fastboot reboot fastboot' your device should reboot into 'fastbootd' Now using the recovery.img file you downloaded from Firefox, type the following command, `'fastboot flash recovery 'PATH TO RECOVERY.IMG FILE'
Once the file has flashed, restart your phone into fastboot mode and using the volume keys, navigate to recovery mode. You should now boot into Orange Fox recovery. Now, in orangefox, go to Wipe - Format Data - then type yes and wait for the process to finish.
Voila!
Step 3: Flashing the ROM!
Open your downloaded version of derpfest, you should see a file called payload.bin, place that into the payload dumper input folder, then run the programme and wait for it complete, you should have loads of .img files. Copy all of these into your platform tools folder! Now download the custom script and place that into the platform tool folder as well.
Reboot your phone into fastboot mode, and once again type 'fastboot reboot fastboot' Once you're in fastbootd mode, right click the script and run as admin, click more info if you have microsoft defender and click run anyway, The rest is done in the script!
After, reboot your phone and you should load into your new Android 12 OS!
If you have any questions please dont hesitate to ask!
If i have made any mistakes in this guide, or you guys think i should make any changes, let me know, im new to this!
*NOTE - I intend to make a full video walk through soon, ill have the youtube video linked here in the near future*
Click to expand...
Click to collapse
Thank you for the awesome guide, I have some questions, since this wipes all my data, what is the most efficient way of backing up my device data as I always don't know what people do to not lose their data while constantly switching ROMs, keeping in mind that this is my first time installing a custom ROM ever!
as well as, what's your experience with the ROM so far, any bugs popped up? Widevine still L1 and SafetyNet passes?
Did you find a way of installing OxygenOS camera? if not, what GCAM are you using?
i think you should add "How to dirty flash an update " also.
0mar32 said:
Thank you for the awesome guide, I have some questions, since this wipes all my data, what is the most efficient way of backing up my device data as I always don't know what people do to not lose their data while constantly switching ROMs, keeping in mind that this is my first time installing a custom ROM ever!
as well as, what's your experience with the ROM so far, any bugs popped up? Widevine still L1 and SafetyNet passes?
Did you find a way of installing OxygenOS camera? if not, what GCAM are you using?
Click to expand...
Click to collapse
Some minor bugs have popped up, like apps closing randomly, but that was because of my magisk root, as soon as I got rid of it, all the apps worked. Oxygen OS Camera wouldn't work so I'm using a Gcam mod for the 7T Pro. As for keeping your data, i would advice performing a nandroid backup. There's guides on YouTube as to how to do this.
amitkuliyal said:
i think you should add "How to dirty flash an update " also.
Click to expand...
Click to collapse
About to start work on an updating part now
astroarchcraft said:
Some minor bugs have popped up, like apps closing randomly, but that was because of my magisk root, as soon as I got rid of it, all the apps worked. Oxygen OS Camera wouldn't work so I'm using a Gcam mod for the 7T Pro. As for keeping your data, i would advice performing a nandroid backup. There's guides on YouTube as to how to do this.
Click to expand...
Click to collapse
So nothing other than apps randomly closing, hmm, good, does Derpfest have a Parallel Apps feature like OOS? as I employ 2 WhatsApp accounts (Personal and Work accounts).
Are you using the recommended GCAM from the ROM Post? https://forum.xda-developers.com/t/...official-hotdog.4250469/page-18#post-86176205
anything else I need to be on the lookout for before I start, coming from OOS I mean, something missing from Derpfest that was on OOS?
Sorry for hammering you, it's just my first time flashing a custom ROM and I'm minutes away from doing it.