Related
Hey guys, as the title states, I'm struggling to install a custom ROM on my Nexus 5X, and I was hoping you guys could read what I did and tell me where I'm going wrong. This is my first time rooting via fastboot commands as whenever I try to root via NRT, SuperSU doesn't flash.
I've had a few failed attempts where my phone has been stuck in bootloop and I've flashed stock using Nexus Root Toolkit. I'll list what I do when trying to root, and if you could tell me where I'm going wrong, that'd be brilliant.
- My first step was to install stock (build number: MTC19T) via NRT
- Connect to the device via fastboot
- Bootloader is already unlocked so I don't bother with that
- Download SuperSU 2.74 in the phone
- Flash over a modified boot.img (found one for my build number on XDA by Tigerstown) via the fastboot commands
***I did this because when I tried to install the SuperSU zip from TWRP 3.0.2, my phone would reboot halfway through the flash and not root***
- Flash over the custom recovery (TWRP 3.0.2 for bullhead)
- Enter recovery from the bootloader
- Install SuperSU via TWRP
- Reboot the phone
- Check if I have root via a Root Checker app in the Play Store
***This part usually goes fine, I've tried it without the boot.img, but TWRP keeps rebooting the system when I try flashing SuperSU***
- Once my phone is rooted, I download Dirty Unicorns 6.0.1 and Banks Dynamic GApps to my phone (I've got these 2 downloaded to my laptop and I just transfer them over to my phone)
- I go back into recovery, I wipe the system (but not internal storage)
- Go to install in TWRP and try to install DU 6.0.1
***My problem here is that TWRP reboots halfway through the installation. I can't flash GApps after the ROM. My phone takes a while to boot up, but when it does, I have DU 6.0.1 even though the installation in TWRP didn't finish***
- I then go back into recovery to install GApps, but the same thing happens to TWRP, it freezes for a second and then reboots my phone.
***However, unlike DU, my GApps won't install. I've tried different a GApps package (Opengapps) but TWRP does the same thing every time***
To summarize, after I root and flash my ROM, I'm left with DU with no GApps. The issue I seem to be having is with TWRP not flashing GApps and I've tried a different version of it but the same thing ends up happening, it freezes for a second and then reboots my phone. I've also tried using SuperSU 2.65 but the same thing happens.
I know this is a long read, but any help would be seriously appreciated!
I haven't heard of twrp rebooting halfway through a flashing sequence before so I'm going to guess that something is corrupted.
I'll try to help you out as much as I can here but if twrp continues to reboot during a flashing sequence I would try to RMA the device and get a new 5X.
Based off what you have typed it sounds like you already have adb access on your computer so I'm going to suggest that you completely wipe the device with these commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase vendor
fastboot erase userdata
Reboot the device into bootloader mode and use this command:
fastboot format userdata <--- This is a must do so that twrp will mount data
Re-download the latest TWRP to make sure the one you have isn't corrupted and then flash it to the device using this command: fastboot flash recovery (name of twrp.img here)
Then flash the Cache.img and Vendor.img that is needed for the DU rom with these commands:
fastboot flash cache cache.img
fastboot flash vendor vendor.img
After the flashing is done boot into recovery mode and wipe the device using twrp. Reboot into recovery mode again. <---- this is a must do so that the other partitions will mount
Transfer the DU rom, Gapps, and SuperSU to the device and flash them while in twrp in this order:
1.) DU rom
2.) SuperSU
3.) Gapps
Reboot the device and you will have the DU with your choice of Gapps and root. Guaranteed.
HesThatGuy said:
I haven't heard of twrp rebooting halfway through a flashing sequence before so I'm going to guess that something is corrupted.
I'll try to help you out as much as I can here but if twrp continues to reboot during a flashing sequence I would try to RMA the device and get a new 5X.
Based off what you have typed it sounds like you already have adb access on your computer so I'm going to suggest that you completely wipe the device with these commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase vendor
fastboot erase userdata
Reboot the device into bootloader mode and use this command:
fastboot format userdata <--- This is a must do so that twrp will mount data
Re-download the latest TWRP to make sure the one you have isn't corrupted and then flash it to the device using this command: fastboot flash recovery (name of twrp.img here)
Then flash the Cache.img and Vendor.img that is needed for the DU rom with these commands:
fastboot flash cache cache.img
fastboot flash vendor vendor.img
After the flashing is done boot into recovery mode and wipe the device using twrp. Reboot into recovery mode again. <---- this is a must do so that the other partitions will mount
Transfer the DU rom, Gapps, and SuperSU to the device and flash them while in twrp in this order:
1.) DU rom
2.) SuperSU
3.) Gapps
Reboot the device and you will have the DU with your choice of Gapps and root. Guaranteed.
Click to expand...
Click to collapse
First of all, just wanted to say thanks for the reply. Unfortunately, I have a few questions (because I'm pretty new at rooting without NRT, so sorry for all these questions)
1) When I fastboot erase everything, is that basically getting rid of the Android OS from my device? If so, would I be able to recover it all by reflashing stock via NRT? (Just in case this goes horribly wrong)
2) What do you mean by adb access? Is that the terminal where you enter commands like "fastboot flash boot <boot.img>" after shift + right clicking on the explorer in windows? (I've been calling that fastboot access)
3) Where would I find the cache.img and vendor.img for DU? I've looked on the DU bullhead page but can't seem to find it.
4) When transferring files after I've flashed TWRP, would I have to sideload the ROM, SuperSU and GApps? I haven't been able to get the hang of that yet, they way I'm doing this is:
- opening the console command
- "adb usb"
- "adb devices"
- going into TWRP, advanced, sideload adb and swiping right
- "adb push <file>" ***not sure if this line is correct
My problem here is that when I swipe in my recovery, I seem to lose adb access. Am I doing this in the wrong order? Are there any other ways of sideloading?
Again, sorry for all the questions but I'm new at all of this and I really want root on my Nexus 5X.
thatguynaveed said:
First of all, just wanted to say thanks for the reply. Unfortunately, I have a few questions (because I'm pretty new at rooting without NRT, so sorry for all these questions)
1) When I fastboot erase everything, is that basically getting rid of the Android OS from my device? If so, would I be able to recover it all by reflashing stock via NRT? (Just in case this goes horribly wrong)
2) What do you mean by adb access? Is that the terminal where you enter commands like "fastboot flash boot <boot.img>" after shift + right clicking on the explorer in windows? (I've been calling that fastboot access)
3) Where would I find the cache.img and vendor.img for DU? I've looked on the DU bullhead page but can't seem to find it.
4) When transferring files after I've flashed TWRP, would I have to sideload the ROM, SuperSU and GApps? I haven't been able to get the hang of that yet, they way I'm doing this is:
- opening the console command
- "adb usb"
- "adb devices"
- going into TWRP, advanced, sideload adb and swiping right
- "adb push <file>" ***not sure if this line is correct
My problem here is that when I swipe in my recovery, I seem to lose adb access. Am I doing this in the wrong order? Are there any other ways of sideloading?
Again, sorry for all the questions but I'm new at all of this and I really want root on my Nexus 5X.
Click to expand...
Click to collapse
1) yes
2) yes
3) factory image zip found here
4) no, when you are in TWRP connect the phone to the computer you will get a window pop up that allows you to brows the internal storage of your device (sd card) you can freely move files back and fourth.
If you didn't execute "Fast boot Flash System 'system.img" not erase System Partition vis Recovery then no, it will not erase the system partition of the device.
Sent from my Nexus 5X using XDA-Developers mobile app
HesThatGuy said:
I haven't heard of twrp rebooting halfway through a flashing sequence before so I'm going to guess that something is corrupted.
I'll try to help you out as much as I can here but if twrp continues to reboot during a flashing sequence I would try to RMA the device and get a new 5X.
Based off what you have typed it sounds like you already have adb access on your computer so I'm going to suggest that you completely wipe the device with these commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase vendor
fastboot erase userdata
Reboot the device into bootloader mode and use this command:
fastboot format userdata <--- This is a must do so that twrp will mount data
Re-download the latest TWRP to make sure the one you have isn't corrupted and then flash it to the device using this command: fastboot flash recovery (name of twrp.img here)
Then flash the Cache.img and Vendor.img that is needed for the DU rom with these commands:
fastboot flash cache cache.img
fastboot flash vendor vendor.img
After the flashing is done boot into recovery mode and wipe the device using twrp. Reboot into recovery mode again. <---- this is a must do so that the other partitions will mount
Transfer the DU rom, Gapps, and SuperSU to the device and flash them while in twrp in this order:
1.) DU rom
2.) SuperSU
3.) Gapps
Reboot the device and you will have the DU with your choice of Gapps and root. Guaranteed.
Click to expand...
Click to collapse
Tried this method this morning, no luck though
Same thing kept happening, TWRP freezes for a second halfway through installing SuperSU (at extracting files) and then rebooting without root.
Gutted I can't get root on my phone
Since TWRP continues to reboot halfway through the flashing sequence I would recommend that you RMA the device and get a new 5X. There could possibly be a hardware failure occurring and with those it's best to try not to fix them yourself.
thatguynaveed said:
Tried this method this morning, no luck though
Same thing kept happening, TWRP freezes for a second halfway through installing SuperSU (at extracting files) and then rebooting without root.
Gutted I can't get root on my phone
Click to expand...
Click to collapse
Are you accepting when TWRP offers to root the phone for you? Don't! That feature does not work on MM and I think they took it out in 3.0x
Download SuperSU from Chainfire's website, flash the zip in Twrp and then install the SuperSU app from Play
berndblb said:
Are you accepting when TWRP offers to root the phone for you? Don't! That feature does not work on MM and I think they took it out in 3.0x
Download SuperSU from Chainfire's website, flash the zip in Twrp and then install the SuperSU app from Play
Click to expand...
Click to collapse
No, I can't even get to that stage. TWRP reboots whilst I'm trying to install SuperSU.
And by flashing the SuperSU zip, wouldn't I already have SuperSU on my phone? Why would I have to install it form the Play Store?
Anyways, I've given up on trying to root my 5X, like HesThatGuy said, my phone probably has some hardware issues and seeing as I bought my phone second hand, I can't replace it. So I'm just sticking with stock.
Thanks for the reply though mate :good:
Why in Matias Duarte's name are you rooting your phone before flashing a custom ROM? That is a massive waste of time and effort. DU is rooted. You dont need to root the stock ROM first.
First, redownload and fastboot flash TWRP. Redownload DU and the recommended GAPPS while you are at it. If you want to be unencrypted go to WIPE and select Format Data (this will nuke all photos, video, music, whatever on your phone. Back it up first). Don't reboot. Now plug your phone into your computer. Move DU and the GAPPS package you redownloaded to your phone. Wipe everything but internal storage. Add both DU and GAPPS to the flash queue. Flash those buggers. Enjoy.
Just wanted to inform you, that rooting with Magisk works like a charm. Even without TWRP.
What you need:
Magisk Manager: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
boot.img from your ROM (prepatched boot.img for CN_V10.0.11.0 ROM here: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=19)
Unlocked Bootloader
ADB and Fastboot on your PC (Simple ADB & Fastboot Installer: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=5)
Installation:
Install MagiskManager.apk on your Smartphone
---SKIP IF YOU USE THE PREPATCHED BOOT.IMG---
Put the unpatched boot.img on your phone
Open MagiskManager and Click "Install"
Select "Patch boot.img" and choose the boot.img with your file manager
Copy the "patched_boot.img" file on your PC
---CONTINUE HERE---
Now connect your Mix 3 to the PC and boot in fastboot mode (over the command line: adb reboot bootloader)
Navigate with the command line to your folder, where you saved the patched_boot.img
Now flash the patched_boot.img file with fastboot: fastboot flash boot patched_boot.img
If the flash is successfull you can reboot the phone with fastboot reboot
Open the MagiskManager and verify that Magisk is installed and your phone is rooted.
Thanks so much! Will try this out! Nice work!
Thanks, after i root my mix 3 can i flash the xiaomi.eu rom on it too without problems ?
Normally you don't need root to flash Xiaomi.eu ROM, just TWRP. But there is no TWRP yet. You could try "Flash Fire", but I don't know if it would work. Never did that before. If you try it make sure, that you have USB Debugging enabled and know how to use common tools like MiFlash etc.
If you are unexperienced wait for TWRP.
PJF16 said:
Normally you don't need root to flash Xiaomi.eu ROM, just TWRP. But there is no TWRP yet. You could try "Flash Fire", but I don't know if it would work. Never did that before. If you try it make sure, that you have USB Debugging enabled and know how to use common tools like MiFlash etc.
If you are unexperienced wait for TWRP.
Click to expand...
Click to collapse
I used TWRP before and Rooted before too but i never used Flash Fire or Flashify. I don't know how hard it would be to use them.
Please report back your success and how it goes for you!
SacredSovL said:
I used TWRP before and Rooted before too but i never used Flash Fire or Flashify. I don't know how hard it would be to use them.
Click to expand...
Click to collapse
It's risky and something I won't be trying, I would wait for TWRP
Hi PJF16
How did you get the boot.img from your device without root? I'd love to make a unmodified copy before trying this out
I got it from the fastboot ROM which I also uploaded to the forum. See here: https://forum.xda-developers.com/mi-mix-3/development/xiaomi-mi-mix-3-fastboot-roms-t3869532
Tested and 100% working! Recommended
smiba said:
Tested and 100% working! Recommended
Click to expand...
Click to collapse
Did u flash xiaomi.eu rom or something else ?
PJF16 said:
Just wanted to inform you, that rooting with Magisk works like a charm. Even without TWRP.
What you need:
Magisk Manager: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
boot.img from your ROM (prepatched boot.img for CN_V10.0.11.0 ROM here: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=19)
Unlocked Bootloader
ADB and Fastboot on your PC (Simple ADB & Fastboot Installer: https://filebase.philipp.technology/filebase/index.php?page=Entry&entryID=5)
Installation:
Install MagiskManager.apk on your Smartphone
---SKIP IF YOU USE THE PREPATCHED BOOT.IMG---
Put the unpatched boot.img on your phone
Open MagiskManager and Click "Install"
Select "Patch boot.img" and choose the boot.img with your file manager
Copy the "patched_boot.img" file on your PC
---CONTINUE HERE---
Now connect your Mix 3 to the PC and boot in fastboot mode (over the command line: adb reboot bootloader)
Navigate with the command line to your folder, where you saved the patched_boot.img
Now flash the patched_boot.img file with fastboot: fastboot flash boot patched_boot.img
If the flash is successfull you can reboot the phone with fastboot reboot
Open the MagiskManager and verify that Magisk is installed and your phone is rooted.
Click to expand...
Click to collapse
I feel like I'm missing something. I fastboot flash but it gets hung up in cmd. Should not take as long as it is trying to
souless poet said:
I feel like I'm missing something. I fastboot flash but it gets hung up in cmd. Should not take as long as it is trying to
Click to expand...
Click to collapse
Nevermind figured it out...duh.
Not working on 8.11.15 dev china rom...
Patched boot is much smaller than it should be and after flashing and fastboot reboot command, phone goes back to fastboot mode
It's normal that the patched boot.img is smaller.
PJF16 said:
It's normal that the patched boot.img is smaller.
Click to expand...
Click to collapse
I know that.
But this is quite smaller than usual and, anyway, it doesn't boot after flashing
Anyone have any issues with v4A magisk module? After I flashed it I lost the ability to turn on wifi. Wondering if anyone else has had that issue.
where can i find the pre patched boot img of 10.0.12.0?
Just use the one for 10.0.11.0.
nosidefcp said:
where can i find the pre patched boot img of 10.0.12.0?
Click to expand...
Click to collapse
Hi, here You can find patched boot for 10.0.12.0:
https://yadi.sk/d/aVlSEC_r7xj0VA
All Praise and All Thanks To God
Things Required: Unlocked bootloader, TWRP file, Disable_Dm-Verity_ForceEncrypt.zip file, External SD card, adb and fastboot drivers installed in pc
Steps to flash TWRP:
Note: This will erase all your data, so please backup important things like photos,contacts etc , before following this procedure
1. Unlock bootloader if not done yet.
see this guide to unlock:
https://forum.xda-developers.com/realme-3/how-to/guide-bootloader-unlock-guide-realme-3-t3999463
2. Copy Disable_Dm-Verity_ForceEncrypt.zip in your External SD Card. Power off your phone by pressing power button, after your phone is powered off ,hold volume down + power button to boot into fastboot mode
3. Commands to execute:
fastboot flash recovery twrp.img
fastboot -w
fastboot oem reboot-recovery
4.Touch will not work for 40 seconds, just wait until touch starts to work.
5. Now very Important part, take full twrp backup in your external sdcard and keep it safe in your pc (This backup will be helpful in future incase you soft brick your device or have some issues in your phone such as network or volte or some other **** not working)
6. Install the Disable_Dm-Verity_ForceEncrypt.zip using twrp
7 .Reboot, Done!
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Please Note:
1. There will be red blinking notification due to flashing Disable_Dm-Verity_ForceEncrypt_Quota_.zip, you can just ignore it. If you don't like the red bliking notification, just restore your nvdata, vendor and system from twrp backup.
2. Don't relock bootloader after flashing twrp, it might brick your device. (Don't use fastboot flashing lock)
3. You cannot restore preloader_a and preloader_b partitions using twrp, only you can backup the two partitions, so always uncheck these two partitions before performing a twrp restore.
4. Please don't use minimal adb and fastboot tool, use Latest ADB and Fastboot Installer tool , link is provided below.
Features:
1. You can directly flash ota zip from twrp, but you have to decrypt it first using ozipdecrypt from here:
https://github.com/bkerler/oppo_ozip_decrypt
2. Fstab includes all the partitions to backup and restore
Links:
TWRP : https://github.com/fawazahmed0/android_device_Realme3_RMX1821/releases
Disable_Dm-Verity_ForceEncrypt.zip: https://zackptg5.com/android.php#disverfe
Latest ADB and Fastboot Installer: https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
Device Tree: https://github.com/fawazahmed0/android_device_Realme3_RMX1821
How to boot to recovery:
A. From adb:
adb reboot recovery
adb shell reboot recovery
B. From fastboot mode:
fastboot oem reboot-recovery
C. There is no way to boot to recovery using power + vol down button after unlocking your bootloader. Only above two methods will work. (Don't relock bootloader after flashing twrp, it might brick your device)
Warning: if you did not follow the steps properly, either the twrp will be blank or you will be in endless recovery mode bootloop or you will revert back to stock recovery next time you try to boot to twrp.
Contributors:
@chankruze for his device tree and stable twrp:
https://github.com/N00bTree/android_device_realme_spartan
Blackcat: Got to know verity can be disabled by modifying vendor partition
@haditriw: For testing and verifying vendor can be modified in this phone
@ashu7073 for fixing screen issue and for his device tree
@jeffalaiza for making twrp ports
@Zackptg5 for his Disable_Dm-Verity_ForceEncrypt.zip
@osm0sis for his system_root mount support in AK3 which Disable_Dm-Verity_ForceEncrypt.zip uses
Nice Work
I will test soon
---------- Post added at 02:15 PM ---------- Previous post was at 02:13 PM ----------
KSUBROTO said:
It didn't work
Click to expand...
Click to collapse
dont be stupid nova customizer you dont have rm3 phone all developer from realme device they know you scammer !!
Will we still see blank screen after 2 minutes of loading, or anything else?
Sounak Biswas said:
Will we still see blank screen after 2 minutes of loading, or anything else?
Click to expand...
Click to collapse
When twrp boots, it will be blank screen, so don't panic.
you have to wait for atleast 2 minutes before executing the next commands
Has anyone been able to flash supersu.zip through shell yet?
Sounak Biswas said:
Has anyone been able to flash supersu.zip through shell yet?
Click to expand...
Click to collapse
Jion This https://t.me/joinchat/HrjmCBBex1F5cy9q0m7cQg
Sounak Biswas said:
Has anyone been able to flash supersu.zip through shell yet?
Click to expand...
Click to collapse
Use magisk, https://forum.xda-developers.com/realme-3/how-to/rooting-guide-realme-3-t3927028
Sounak Biswas said:
Has anyone been able to flash supersu.zip through shell yet?
Click to expand...
Click to collapse
Superuser on magisk .
I need scatter file
Make scatter file for realme 3 my rm3 is deadboot
johncedd said:
Make scatter file for realme 3 my rm3 is deadboot
Click to expand...
Click to collapse
Please Download The Stock Rom inside You Get Scatter File Ok
johncedd said:
Make scatter file for realme 3 my rm3 is deadboot
Click to expand...
Click to collapse
If it's soft brick or bootloop see this guide:
https://forum.xda-developers.com/realme-3/how-to/realme-3-recover-soft-brick-boot-loop-t3920401
if it's hard brick go to service center.
I am not sure how scatter file will help you recover from hard brick.
Here is the scatter file for mt6771 chipset:
https://drive.google.com/file/d/1pjIkb9xuq4WRFVh72V3V6eNfzdhRTk8L/view
Thanks Sir
jeffalaiza said:
Thanks Sir
Click to expand...
Click to collapse
Welcome sir
Work on ROM A.18 sir ?
hi sir, wolud you help me
what step should i do I got HARDBRICK realme 3?
I'm a newbie
Hello. I've recently tried to install TWRP on my RMX1821, and followed all the instructions but hurdled when I tried to format userdata. It says:
CreateProcess failed: the system cannot find the file specified. (2)
error: Cannot generate image for userdata
Click to expand...
Click to collapse
Any advice or solution to rectify this problem?
TwelveMoon said:
Hello. I've recently tried to install TWRP on my RMX1821, and followed all the instructions but hurdled when I tried to format userdata. It says:
Any advice or solution to rectify this problem?
Click to expand...
Click to collapse
Use adb platform tools..
I want to unlock the bootloader but in the application step I have waited more than 1 hour and the server has not shown success.
Can you share a link of video tutorial please.
fawazahmed0 said:
All Praise and All Thanks To God
Features:
1. You can directly flash ota zip from twrp, but you have to decrypt it first using ozipdecrypt from here:
https://github.com/bkerler/oppo_ozip_decrypt
2. Fstab includes all the partitions to backup and restore
Steps to flash TWRP:
Note: This will erase all your data, so please backup important things like photos,contacts etc , before following this procedure
1. Unlock bootloader if not done yet.
see this guide to unlock:
https://forum.xda-developers.com/realme-3/how-to/bootloader-unlock-realme-3guide-t3920394
2. power off your phone by pressing power button, now hold volume down + power button to boot into fastboot mode
3. Commands to execute:
fastboot flash recovery twrp-3.3.1-0-RMX1821.img
fastboot -w
fastboot oem reboot-recovery
4.Touch will not work for 40 seconds, just wait until touch starts to work.
5. Now very Important part, take full twrp backup in your sdcard and keep it safe in your pc (This backup will be helpful in future incase you soft brick your device or have some issues in your phone such as network or volte or some other **** not working)
6a. Copy and install Disable_Dm-Verity_ForceEncrypt_Quota_.zip in your phone using:
adb push Disable_Dm-Verity_ForceEncrypt_Quota_.zip /
adb shell twrp install Disable_Dm-Verity_ForceEncrypt_Quota_.zip
or
b. copy the Disable_Dm-Verity_ForceEncrypt_Quota_.zip in sdcard and install using twrp touch interface, then wipe dalvik, cache, data and format data.
6. Done!
There will be red blinking notification due to flashing Disable_Dm-Verity_ForceEncrypt_Quota_.zip, you can just ignore it. If you don't like the red bliking notification, just restore your nvdata, vendor and system from twrp backup.
Disable_Dm-Verity_ForceEncrypt_Quota_.zip: https://www.androidfilehost.com/?fid=6006931924117924278
or download the latest version from here: https://zackptg5.com/android.php#disverfe
TWRP : https://github.com/fawazahmed0/android_device_Realme3_RMX1821/releases
Device Tree: https://github.com/fawazahmed0/android_device_Realme3_RMX1821
How to boot to recovery:
From adb:
adb reboot recovery
adb shell reboot recovery
From fastboot mode:
fastboot oem reboot-recovery
If you want to boot to recovery using power + vol down button, then you have to lock the bootloader using:
fastboot flashing lock
Warning: if you did not follow the steps properly, either the twrp will be blank or you will be in endless recovery mode bootloop or you will revert back to stock recovery next time you try to boot to twrp.
Contributors:
@chankruze for his device tree and stable twrp:
https://github.com/N00bTree/android_device_realme_spartan
Blackcat: Got to know verity can be disabled by modifying vendor partition
@haditriw: For testing and verifying vendor can be modified in this phone
@ashu7073 for fixing screen issue and for his device tree
@jeffalaiza for making twrp ports
@Zackptg5 for his Disable_Dm-Verity_ForceEncrypt.zip
Click to expand...
Click to collapse
ROM manager shows that TWRP is my current recovery but I can't boot into TWRP recovery, I don't understand the issue.
While waiting for a working TWRP for all those needful of the possibility to access their file system from recovery, e.g. for removing an offensive magisk extension preventing boot I repackaged the Stock OOS recovery from the 10.0.1BA package but with ADB enabled.
Prerequisites:
Oneplus 7T Pro
unlocked bootloader
access to fastboot on the phone
adb and fastboot
Installation:
Reboot the phone to fastboot, then flash the recovery from fastboot with the command
Code:
fastboot flash recovery
(when taking the file as downloaded the filename is "OP7TP_StockRecovery_ADB_nosec.img")
Uninstall:
Same as installation, but flash the original stock recovery instead.
Usage:
Boot up recovery, enter encryption key if file system is encrypted. Then connect the phone to PC and you are ready to go with adb. E.g. by using
Code:
adb shell
to open a shell and access the file system. Magisk modules are located in /data/adb/modules, deleting the corresponding directory there will remove the module in question.
Downloads:
10.0.3BA Recovery
Modified 10.0.3BA recovery from GDrive
Original 10.0.3BA stock recovery from Gdrive
10.0.4BA Recovery
Modified 10.0.4BA recovery from GDrive
Original 10.0.4BA stock recovery from Gdrive
10.0.7BA Recovery
Modified 10.0.7BA recovery from GDrive
Original 10.0.7BA stock recovery from Gdrive
Open Beta 1 Recovery
Modified OB1 recovery from GDrive
Open Beta 2 Recovery
Modified OB2 recovery from GDrive
Notes of caution:
ADB security is disabled as I could not get the recovery to allow for authorizing a connected computer. As a consequence any computer connected is automatically authorized in ADB, although with encrypted filesystem at least no data is accessible without the key.
with direct ADB access to your file system you can easily wreck you phone requiring a factory reset or even reinstallation of the OS from fastboot - please be careful on what you are doing
Credits: Thanks to osm0sis for Android kitchen and all great developers for the Oneplus devices, specifically mauronofrio for his TWRP efforts.
I just need it, thank you very much.
But this rec has a bug
After swiping in and entering REC, the interface does not need to enter a password, and the adb shell opens /data is empty.
Only the boot_a and boot_b that have not been modified by magisk are brushed in and the password is entered again after booting and re-entering rec, and the data can be modified.
但是这个rec有个BUG
刷入并进入REC后 界面不需要输入密码,并且adb shell打开/data是空的
只有刷入没有被magisk修改过的boot_a和boot_b并且开机后重新进入rec才有输入密码的界面,并且data可以修改
991547436 said:
But this rec has a bug
After swiping in and entering REC, the interface does not need to enter a password, and the adb shell opens /data is empty.
Only the boot_a and boot_b that have not been modified by magisk are brushed in and the password is entered again after booting and re-entering rec, and the data can be modified.
但是这个rec有个BUG
刷入并进入REC后 界面不需要输入密码,并且adb shell打开/data是空的
只有刷入没有被magisk修改过的boot_a和boot_b并且开机后重新进入rec才有输入密码的界面,并且data可以修改
Click to expand...
Click to collapse
English only pls?
OnePlus 7T Pro
s3axel said:
While waiting for a working TWRP for all those needful of the possibility to access their file system from recovery, e.g. for removing an offensive magisk extension preventing boot I repackaged the Stock OOS recovery from the 10.0.1BA package but with ADB enabled.
Prerequisites:
Oneplus 7T Pro
unlocked bootloader
access to fastboot on the phone
adb and fastboot
Installation:
Reboot the phone to fastboot, then flash the recovery from fastboot with the command
Code:
fastboot flash recovery <recovery_filename.img>
(when taking the file as downloaded the filename is "OP7TP_StockRecovery_ADB_nosec.img")
Uninstall:
Same as installation, but flash the original stock recovery instead.
Usage:
Boot up recovery, enter encryption key if file system is encrypted. Then connect the phone to PC and you are ready to go with adb. E.g. by using
Code:
adb shell
to open a shell and access the file system. Magisk modules are located in /data/adb/modules, deleting the corresponding directory there will remove the module in question.
Downloads: (all based on 10.0.3BA image from Oneplus)
Modified recovery from GDrive
Original stock recovery from Gdrive
Notes of caution:
ADB security is disabled as I could not get the recovery to allow for authorizing a connected computer. As a consequence any computer connected is automatically authorized in ADB, although with encrypted filesystem at least no data is accessible without the key.
with direct ADB access to your file system you can easily wreck you phone requiring a factory reset or even reinstallation of the OS from fastboot - please be careful on what you are doing
Credits: Thanks to osm0sis for Android kitchen and all great developers for the Oneplus devices, specifically mauronofrio for his TWRP efforts.
Click to expand...
Click to collapse
HolyChickenGuy said:
English only pls?
OnePlus 7T Pro
Click to expand...
Click to collapse
English is a translation. I don't know if the translation is correct.
991547436 said:
But this rec has a bug
After swiping in and entering REC, the interface does not need to enter a password, and the adb shell opens /data is empty.QUOTE]
I noticed the same behaviour when trying "fastboot boot", the recovery needs to be flashed to work.
Second I own an EU device with BA firmware/OS on it, maybe global devices with AA firmware are different...
Click to expand...
Click to collapse
Theres no flashable zip rom for twrp? Thanks
Enviado desde mi MI MAX 3 mediante Tapatalk
jorgeepelos said:
Theres no flashable zip rom for twrp? Thanks
Enviado desde mi MI MAX 3 mediante Tapatalk
Click to expand...
Click to collapse
TWRP doesn't even work for this device, and with devices launched Android 10 you can no longer flash system via TWRP.
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
TWRP doesn't even work for this device, and with devices launched Android 10 you can no longer flash system via TWRP.
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Ok thanks!!!
Enviado desde mi MI MAX 3 mediante Tapatalk
Thank you very much for this recovery.
Just needed it after trying to install Viper4Android and only going to fastboot screen.
Cheers
Same as the user above, had problems with Viper. Used this and removed the modules, and now it boots. Thanks!
This has caused my device to bootloop to recovery. Flashing stock recovery doesn't fix this problem.
Doing fastboot boot boot.img starts my rom, but every time I reboot (via fastboot, adb or normally from rom) it goes back to recovery. I am running 10.0.3.HD01BA and don't have any ideas how to recover from this.
Any help would be appreciated, I am truly a novice in this scene.
Az4z3l11 said:
This has caused my device to bootloop to recovery. Flashing stock recovery doesn't fix this problem.
Doing fastboot boot boot.img starts my rom, but every time I reboot (via fastboot, adb or normally from rom) it goes back to recovery. I am running 10.0.3.HD01BA and don't have any ideas how to recover from this.
Any help would be appreciated, I am truly a novice in this scene.
Click to expand...
Click to collapse
Did you install any modules?
OnePlus 7T Pro
Az4z3l11 said:
This has caused my device to bootloop to recovery. Flashing stock recovery doesn't fix this problem.
Doing fastboot boot boot.img starts my rom, but every time I reboot (via fastboot, adb or normally from rom) it goes back to recovery. I am running 10.0.3.HD01BA and don't have any ideas how to recover from this.
Any help would be appreciated, I am truly a novice in this scene.
Click to expand...
Click to collapse
Just a thought: could it be that you flashed this recovery with "Fastboot flash boot <filename.img> ? This would explain that when booting not the original boot image but recovery comes up.
From your message I take that you have the original boot image at hand, you could try flashing it with "fastboot flash boot boot.img"
The recovery image in this thread is flashed with "fastboot flash recovery <filename.img>...
Hth, cheers,
Axel
Gesendet von meinem HD1913 mit Tapatalk
HolyChickenGuy said:
Did you install any modules?
OnePlus 7T Pro
Click to expand...
Click to collapse
Only one that came with my Swift Installer.
s3axel said:
Just a thought: could it be that you flashed this recovery with "Fastboot flash boot <filename.img> ? This would explain that when booting not the original boot image but recovery comes up.
From your message I take that you have the original boot image at hand, you could try flashing it with "fastboot flash boot boot.img"
The recovery image in this thread is flashed with "fastboot flash recovery <filename.img>...
Hth, cheers,
Axel
Gesendet von meinem HD1913 mit Tapatalk
Click to expand...
Click to collapse
Negative, I have the command prompt window still open, and was extra careful to flash the recovery with recovery, not boot.
The image I have is a patched boot image from another xda thread. I am scared that flashing that would brick my device.
EDIT: Is there a way to extract my original boot.img and then try to flash it?
EDIT2: Extracted my boot.img from /data folder in stock_boot_xxxxxxxxxxx.img.gz. I will try to flash it once I have backed everything up.
EDIT 3: Tried flashing original boot.img and re-rooting phone with magisk, and no luck. The solution was too obvious though. I didn't realize that my phone had encryption on and the password was my lockscreen PIN code. After decrypting the recovery the phone boots normally and the adb recovery works perfectly.
Thanks for the support, it seems that tinkering with your phone is way harder than I remember it from back in the days; hopefully TWRP will fix this, once it supports Android 10.
Thank you very much for the recovery!
Is there a recovery like this for the regular 7t?
Just curious, do you have a guide on how to this yourself?
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
Just curious, do you have a guide on how to this yourself?
Click to expand...
Click to collapse
It's actually pretty easy and this would most probably also work for the 7T...
Prerequisites:
Android Image Kitchen (credit to osm0sis for providing this tool)
the original recovery image file (henceforth called "recovery.img"). You can extract this yourself from an update zip file by unpacking "payload.bin" and then use a tool like payload_dumper (credit to vm03 for providing this) to extract the recovery.img file
Now do the following:
unpack image with Image Kitchen --> this will create a "ramdisk" and a "Split_img" directory with the unpacked content within
navigate into the "ramdisk" folder and use a text editor (on windows preferably Notepad++) to edit the file "prop.default"
look for entry "ro.adb.secure" and change entry value from "1" to "0". Note this entry can occur multiple times (I noticed twice), change each --> this will prevent adb from asking for authorization (the recovery does not provide such a dialogue)
look for entry "ro.debuggable" and change this from "0" to "1" --> this actually enables adb
look for entry "ro.secure" and change this from "1" to "0" --> may be unnecessary but I wanted to avoid brick in case a modified recovery would result in such a behaviour
save textfile
repack the image with Android Image Kitchen and voila:
you have a new modified recovery image you can flash
HolyChickenGuy said:
English only pls?
OnePlus 7T Pro
Click to expand...
Click to collapse
991547436 said:
English is a translation. I don't know if the translation is correct.
Click to expand...
Click to collapse
Moderator Announcement:
The way you did is very fine and exemplary!
*********
您的做法非常好，堪称典范！
XDA Forum Rules (excerpt):
...
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.
...
Click to expand...
Click to collapse
991547436 said:
But this rec has a bug
After swiping in and entering REC, the interface does not need to enter a password, and the adb shell opens /data is empty.
Only the boot_a and boot_b that have not been modified by magisk are brushed in and the password is entered again after booting and re-entering rec, and the data can be modified.
Click to expand...
Click to collapse
I was in a bootloop, because of the GCam aux Magisk module. For me it was the same at first attempt. I installed with
Code:
fastboot flash recovery OP7TP_StockRecovery_ADB_nosec.img
After that I rebooted to recovery. I also did not get a password prompt. I connected with
Code:
adb shell
but /data was empty. Because I wanted to see if my system still works without Magisk, I booted with the unmodified boot.img by using
Code:
fastboot boot boot.img
System came up without Magisk and was usable. After that I rebooted and it got stuck at fastboot screen again. I tried one more time to select recovery from fastboot screen and it asked me for password. Since I don't have encryption I just tried to connect again with
Code:
adb shell
This time /data was properly mounted and I was able to delete the Magisk module. After that I rebooted to system with
Code:
adb reboot
and now I have my fully functional system back. I don't know why it didn't work in the first attempt but this is awesome.
@s3axel you made my day! Thank you very much!!! Your work is appreciated!
For those who can't root via TWRP or somehow lost root while updating (like I did), I have a patched boot image to aid others in this endeavor. This is a boot.img from a T-Mobile 7T which I had converted to the Global ROM, extracted and patched by Magisk after applying the latest update (10.0.13.HD65AA). Fully tested and working!
Instructions:
Unzip and place it in a convenient folder (ie, C:/adb/ or whatever's easy to remember.
Open a cmd prompt and navigate to your fastboot/adb folder.
Then run the command
Code:
fastboot boot boot.img
Your phone will be "temp-rooted" once it boots. If you haven't already, install Magisk Manager, then flash Magisk itself (ALWAYS do direct install!).
Don't install any modules yet. Just reboot when prompted after the Magisk flashing process is done.
Profit!
Download from Google Drive
[I dunno where else to upload this that XDA would consider "safe," so GDrive it is, I suppose.]
Spoiler: Process for manually patching the boot.img without TWRP:
Requirements: Stock device with unlocked bootloader only (no other mods), most recent OTA update applied and system rebooted. Fastboot and ADB Windows executables.
1) Enable advanced reboot and usb debugging in developer options.
2) Reboot to bootloader.
Code:
adb reboot bootloader
3) Boot to twrp
Code:
fastboot boot twrp.img
(or whatever you named it).
4) Once booted, enter:
Code:
adb shell
dd if=/dev/block/bootdevice/by-name/boot of=/tmp/boot.img
exit
5.5) Copy file to the PC:
Code:
adb pull /tmp/boot.img stock_boot.img
6) Reboot phone back to Android.
6.5) Copy boot.img back to phone:
Code:
adb push stock_boot.img /sdcard/boot.img
7) Make sure you have a data connection.
8) Install Magisk Manager.
9) Select option to install Magisk (not the Magisk App). Choose "Select and Patch a File."
10) Point to the boot.img.
11) It will do its thing then come back with a done message. File /sdcard/download/magisk_patched.img will be created.
12) Copy this file to your PC, either using MTP or ADB.
Code:
adb pull /sdcard/download/magisk_patched.img
13) Reboot the phone into bootloader mode again.
Code:
adb reboot bootloader
14) Boot the patched boot from step 12:
Code:
fastboot boot magisk_patched.img
15) Launch Magisk Manager again. You should see the current version available and the installed version below that now. If all is good, choose to install/update Magisk, then "Direct install" and reboot when finished.
I guess you posted it in wrong section as mentioned the file is for Oneplus 7t ?
>Akshay< said:
I guess you posted it in wrong section as mentioned the file is for Oneplus 7t ?
Click to expand...
Click to collapse
OH! You're right. I goofed. I'll ask a mod to move it.
This will delete all the data from the phone + bootloader needs to be unlocked?
Brontok said:
This will delete all the data from the phone + bootloader needs to be unlocked?
Click to expand...
Click to collapse
Flashing this doesn't erase your data, unlocking the bootloader does, though (and is necessary to flash this).
GuyInDogSuit said:
Flashing this doesn't erase your data, unlocking the bootloader does, though (and is necessary to flash this).
Click to expand...
Click to collapse
never mind!
someone already did!
https://forum.xda-developers.com/showpost.php?p=83780229&postcount=12
thanks anyway!
Will this work for 10.0.13 tmobile ? Thanks
gershee said:
Will this work for 10.0.13 tmobile ? Thanks
Click to expand...
Click to collapse
You might be better off pulling the boot.img yourself and patching it. I can't guarantee that this will even work on the T-Mobile version. But if you want to test it, just boot the img and root from Magisk once it loads. If it bootloops, well, then we know.
EDIT: Updated OP with instructions on how to patch the boot.img.
GuyInDogSuit said:
You might be better off pulling the boot.img yourself and patching it. I can't guarantee that this will even work on the T-Mobile version. But if you want to test it, just boot the img and root from Magisk once it loads. If it bootloops, well, then we know.
EDIT: Updated OP with instructions on how to patch the boot.img.
Click to expand...
Click to collapse
Thanks!
Worked like a charm.