Develop Bugs

Pixel xl in twrp with no OS installed?

Hello to all. I have just unlocked bootloader, installed twrp and su. After everything booted up properly, I went to install an adblocker zip file, however once it booted into twrp it had no download folder, as well as when I went to reboot system it told me I had no os installed.. I'm a bit confused as to what to do now.. My apologies for clogging the thread if this has been answered before..
Edit: do I adb side load an image file or OS? I'm afraid of bricking this phone as I don't know how to continue from this point..

Which guide did you use to do all of this? I will help us understand where you started

Mrbobrowitz said:
Which guide did you use to do all of this? I will help us understand where you started
Click to expand...
Click to collapse
Hi thanks for the reply. This link right here:
http://www.androidsage.com/2016/11/...timate-guide-root-twrp-and-bootloader-unlock/
Steps I followed:
1 unlocked bootloader
2 Download the below files TWRP and Root files for Google Pixel & Pixel XL
Official TWRP for Pixel phones → Download |
Files: twrp-pixel-installer-sailfish-3.0.2-0-alpha1.zip 7.6M
twrp-3.0.2-0-alpha1-fastboot-sailfish.img 25M
Flash SuperSU 2.78 SRF4 → Download | File: SR4-SuperSU-v2.78-SR4-20161115184928.zip
Twrp install instructions:
Step 1: Download the TWRP recovery and latest SuperSU zip file for your Google Pixel and Pixel XL devices. There are 2 TWRP files with .zip and .img extensions. You will need both. You don’t need to extract the files, just place all the files on your PC as well as your Android phone’s internal storage where you can easily locate it.
Step 2: Make sure that you setup ADB and Fastboot on your PC and gone through all the prerequisites from above.
Step 3: Now plug in the Pixel device to the computer and open a command prompt or terminal on your PC to the window where TWRP.zip file is located. (See above to know how to open cmd)
Step 4: Boot your Android device into the bootloader or Fastboot mode. To do so, issue the following command through cmd or terminal. You can also manually boot into it using the hard key combination like Power+Volume Down while the device is turned off. Meanwhile, use code:
adb reboot-bootloader
Step 5: Now issue the following command in the command prompt to check your device connectivity
fastboot devices
Step 6: Now issue the following command to temporarily boot up the TWRP image.
fastboot boot path/to/twrp.img
Note: If you have installed our recommend quick 15 second ADB & fastboot installer, you do not need to insert the complete file path. Simply go to where the TWRP image file is and issue command “fastboot boot twrp.img” Otherwise, note that “path/to/” is the actual directory for the TWRP image file. Use fastboot boot and not fastboot flash and that the file you are booting is not the zip file.
Simply After that, TWRP will be accessible to you no matter which active partition slots are being used.
Step 7: After that fastboot command, you will be rebooted into a temporary TWRP recovery interface. To make it permanent, use the TWRP interface to navigate to and install the TWRP.zip file. This is just like using TWRP to flash custom ROMS and SuperSU.
Once the installation completes, you can now enjoy your new firmware. Alternatively, while, on Mac OS, you can issue “./fastboot boot path/to/twrp.img” command or on Linux type “sudo fastboot path/to/twrp.img” to flash the TWRP. For detailed tutorial and alternate methods to flash the TWRP recovery, click here.
Now it’s time to root your Google Pixel with latest SuperSU 2.78 SR4.
How to root :
Place the latest SuperSU 2.78 SR4 package onto your device’s internal storage or SDcard.
Boot your device into the custom TWRP recovery and tap install. For that, turn off your device completely and hold volume down and power buttons for a few seconds.
Once into TWRP tap the install button and select the SuperSU file.
Swipe the confirmation action below to start flashing.
Once done. reboot to system.
You can boot into the TWRP recovery by issuing the following command:
adb reboot recovery

There is an alpha 2 for twrp now. I would try installing this and seeing if it works. If not, you can simply flash the latest factory image and "start over". Granted you would lose any data that you might have had not backed up on your device, but youre not out of luck!

I wouldn't waste your time. Just flash the factory image and start all over. You managed to wipe the Rom off your device

Smallsmx3 said:
I wouldn't waste your time. Just flash the factory image and start all over. You managed to wipe the Rom off your device
Click to expand...
Click to collapse
Mrbobrowitz said:
There is an alpha 2 for twrp now. I would try installing this and seeing if it works. If not, you can simply flash the latest factory image and "start over". Granted you would lose any data that you might have had not backed up on your device, but youre not out of luck!
Click to expand...
Click to collapse
Thanks guys, I actually have installed the alpha 2 twrp. I guess my question is how do I proceed? I'm in twrp and my PC does not see the device when typing adb devices.. Within twrp it says no os installed... What do I do here?
So how do I "start over" or "flash factory image" from the state that I'm in?

mazubo said:
Thanks guys, I actually have installed the alpha 2 twrp. I guess my question is how do I proceed? I'm in twrp and my PC does not see the device when typing adb devices.. Within twrp it says no os installed... What do I do here?
So how do I "start over" or "flash factory image" from the state that I'm in?
Click to expand...
Click to collapse
You should be able to boot into fastboot

Smallsmx3 said:
You should be able to boot into fastboot
Click to expand...
Click to collapse
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..

mazubo said:
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..
Click to expand...
Click to collapse
I couldn't tell you! I've had it happen to me before a couple times. But yes if you can get into fastboot you should be able to fastboot flash a factory image. Then go and flash TWRP and root

Smallsmx3 said:
I couldn't tell you! I've had it happen to me before a couple times. But yes if you can get into fastboot you should be able to fastboot flash a factory image. Then go and flash TWRP and root
Click to expand...
Click to collapse
Ok thanks. I've been able to reboot to bootloader...

I've figured it out via fast boot. The phone is back in action, however not sure how it got wiped initially.. Thanks everyone!

mazubo said:
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..
Click to expand...
Click to collapse
mazubo said:
I've figured it out via fast boot. The phone is back in action, however not sure how it got wiped initially.. Thanks everyone!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Off the top of my head... Probably selected the wrong "slot" maybe?
Remember on this device there are two locations for the ROM. Slot A and B. If you select the wrong one it will show no OS.
As far as the download folder missing... I know its mute at this point, but that has to do with the FBE (File Based Encryption). Make sure TWRP asks you for your Pattern Password. If you do not have one I would consider setting one. That way you know for fact that the File system will get decrypted properly. Also reports say you may have to reboot TWRP twice to get it to decrypt as well.

TWRP for Realme 3 [Working][Updated:21-Aug-2019]

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.

OUTDATED***[GUIDE] Basic guide to flash a recovery and a rom via recovery in Mi A3.

This is a basic guide to flash a rom via recovery in Mi A3 as title says.
Is created to help all those that want but can't.
Please read before act, and if you don't understand....well read again.
Mi A3 is a device with treble support, and while is not difficult to flash a rom,is a little bit tricky process.
So here are the detailed steps to do achieve that.
First things first, you've got to have your bootloader unlocked. Follow below steps to do that:
-Enable developer options by going to settings/about phone and clicking 5 times on build number.
Inside developer options:
-Find and enable OEM unlocking.
-Find and enable USB debugging.
In adb tools type:
-
Code:
adb devices
reboot to bootloader.
-
Code:
adb reboot bootloader
Unlock bootloader(you will lose all your data).
Code:
fastboot flashing unlock
When the device reboot, boot once again in fastboot by powering off then power on while pressing vol down button.
Type command to full unlock bootloader.
Code:
fastboot flashing unlock_critical
Proceed to recovery flash
Notice that you've got to have all files ready, either inside external sd or in your pc. All files are at the end of this thread as links or attachments.
Also i'm suggesting OrangeFox recovery for now because is the most stable.
-First you following the orangefox recovery installation guide:
- Download the OrangeFox zip file from here or the link at the end and copy it to your device (internal or external storage)
- Extract the recovery.img from the zip and store it, on the folder where you have adb and fastboot files, on your PC
- Open a cmd line and execute these commands (being on that folder, of course):
-
Code:
adb devices
(to make sure your device is detected)
-
Code:
adb reboot bootloader
(to reboot into fastboot mode)
-
Code:
fastboot getvar current-slot
(to check what's your current active slot)
-
Code:
fastboot set_active b
(if your active slot was a, if it was b then change it to a)
-
Code:
fastboot erase boot
-
Code:
fastboot flash boot recovery.img [b](OR WHATEVER NAME YOUR RECOVERY HAVE)[/b]
-
Code:
fastboot reboot
(NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo.
-->> By doing this your device will be forced to boot into Recovery and not into System <<--
- Install the OrangeFox zip (always install the latest build available and always keep a copy of recovery zip file in your external sd)
- Change slot to the one that was active on the beginning of these steps and reboot to Recovery (just to make sure that the slot, in fact, was changed)
After orangefox recovery is installed, you are ready to flash your rom.
You can move your rom files inside your external or internal memory(prefer external to avoid deleting them accidentally).
To do that you can either do it before the whole procedure, or after the recovery installation since you have mtp and adb available.
Copy them drag them or push them via adb(i'm not going to extend the adb push command here)
Now the flashing steps:
-Go to partition manager inside orangefox recovery and select data/format data(red button) and press format.Type YES.
-Go back and find the rom file inside your target directory(internal or external).
-Select the rom file and flash it.
-DO NOT REBOOT.
-Go back where you have the orangefox zip file, select it and flash it.
-Leave the device as is because after the installation it will reboot itself to recovery once again.
-Once the recovery starts again go to the target folder that you have the remaining files.
-Flash magiskV20.zip (if you want your device to be rooted).
-Flash Gapps if there are any or skip this step if your ROM provider have them included.
-Flash patchnofde10 zip to avoid data encryption(if you don't do that the rom will NOT boot).
-Reboot to system and enjoy.
All files are available to the links below.
Patchnofde file is attached to this post.
I'm not responsible if you cause a nuclear war or your cat or dog stop talking to you.
Credtits to:
Orangefox recovery team https://orangefox.tech/
Orangefox recovery dev for Mi A3 https://forum.xda-developers.com/mi-a3/development/official-orangefox-recovery-mi-a3-t3986177
Topjohnwu for the Magisk and Magisk manger https://******************/
XDA Forum because they exist
All devs that put some hard work for you to have a custom recovery and a custom rom and all they hear is questions about ho to do things.
Respect them and read before post a questions.
:angel::angel::angel:

Thanks for the detailed guide, always good to have it :good: :good:

my device is encrypted and if I boot a recovery it shows the data encrypted. How to remove encryption ?

drozo8o8 said:
my device is encrypted and if I boot a recovery it shows the data encrypted. How to remove encryption ?
Click to expand...
Click to collapse
Read it first then do it.
Patchnofde is for the encryption.

sotmax said:
Read it first then do it.
Patchnofde is for the encryption.
Click to expand...
Click to collapse
nvm I think I got it

Can anybody please help? I just bought this phone and followed this guide to the letter. The phone just boots back into recovery, whatever ROM I flash.

Is there support for Android backup and restore
Please tell steps for the same also
As it is not working for me
Mobile is Booting to recovery again after restoring backup

ReekyMarko said:
Can anybody please help? I just bought this phone and followed this guide to the letter. The phone just boots back into recovery, whatever ROM I flash.
Click to expand...
Click to collapse
Okay I got it to boot to Havoc OS but my wifi and gsm calls stopped working. Also videos were flashing during playback. I guess I was doing something wrong during the whole flashing process and the device ended up without the correct firmware.
I have reverted back to stock using one of the fastboot ROM flashing scripts and everything is fine, though I would like to go Android 10 without GAPPS if possible.

Thank you very much for the guide. Do you recommend any backup with orange box? If I want to revert to stock rom, do I need to know something?

How could I update the ROM?

darkjm93 said:
Thank you very much for the guide. Do you recommend any backup with orange box? If I want to revert to stock rom, do I need to know something?
Click to expand...
Click to collapse
You can go back to stock by flashing stock image with mi flashtool

ReekyMarko said:
Can anybody please help? I just bought this phone and followed this guide to the letter. The phone just boots back into recovery, whatever ROM I flash.
Click to expand...
Click to collapse
That's because you didn't follow it to the letter.
You have to flash Patchnofde to boot to rom.

vishwadeepmanu said:
Is there support for Android backup and restore
Please tell steps for the same also
As it is not working for me
Mobile is Booting to recovery again after restoring backup
Click to expand...
Click to collapse
Same as above.
If you don't flash patch for the encryption, you ll end up to recovery again. Also I recommend to read carefully the steps with the recovery flashing. You have to be sure that the slot is what it was at the beginning.
A out the Android backup, yes. You can take and restore backups freely.

Hello,
@sotmax
Thank you for your guide.
@ANyOne i have unlocked the bootloader, but after that, when i'm in fastboot mode, i'm not being detected by the adb devices command. Any idea why ?

mkpanic said:
Hello,
@sotmax
Thank you for your guide.
@ANyOne i have unlocked the bootloader, but after that, when i'm in fastboot mode, i'm not being detected by the adb devices command. Any idea why ?
Click to expand...
Click to collapse
Because ADB and fastboot are different modes and using different commands. In fastboot use "fastboot devices".

_mysiak_ said:
Because ADB and fastboot are different modes and using different commands. In fastboot use "fastboot devices".
Click to expand...
Click to collapse
Thank your for the answer.

If I only want to root the stock installing Orange, this guide works?

fastboot set_active command is not working...only fastboot options are displayed..Any solution?

sibikallikkat said:
fastboot set_active command is not working...only fastboot options are displayed..Any solution?
Click to expand...
Click to collapse
fastboot --set-active=a
fastboot --set-active=b

hi, i followed the guide to flash los17 with BiTGApps.
I also flashed the nofde patch. The phones boots normaly but i have no access to internal storage. All the folders have random numbers and letters. Any ideas?

[Magisk] TWRP/Root-less Module Uninstall by allowing ADB in Recovery

I had trouble finding this information, and since we have no working TWRP yet, here is a way to get low-level access to al lot of files.
Full credits go to: @s3axel, Source
So you flashed a module that is now causing a bootloop?
Follow these steps:
0. check if you can boot using stock boot.img, if that does not work, then you have a bigger problem then I had and this guide may not work for you.
1. Get the stock recovery.img by extracting it from the same OTA file as your current build, using payload_dumper
2. Follow s3axel's guide to get adb to work in recovery mode (after you unlock the drive)
s3axel said:
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
Click to expand...
Click to collapse
3. rename the image_new.img to unsecure_adb_recovery.img
4. flash usecure recovery
Code:
fastboot flash recovery unsecure_adb_recovery.img
5. get into the adb shell
Code:
adb shell
then find the magisk module folder
Code:
cd /data/adb/modules
6. remove the module
Code:
rm -rf name_of_module
7. exit shell
8. reboot back to fastboot (See notes below)
9. flash stock recovery
Code:
fastboot flash recovery recovery.img
10. boot patched boot image to try if magisk worked
Code:
fastboot boot patched_magisk.img
Hopefully, if it boots again with root and Magisk
This worked very well and was very easy to do.
11. Use Magisk apk to install magisk to boot img. Or flash your patched magisk.
Notes:
DO NOT try adb reboot fastboot, I was hoping this would work (I was tired, ok...)
I got stuck in a bootloop (it kept asking me to unlock my device)
to break out of this loop, I used the forced off method: hold power + volume up & down until screen blacks out
From power off to bootloader:
press & hold volume down and power
and hold down until you get back to recovery, reboot to fastboot then flash stock recovery back to secure your ADB and return to as much stock as possible :good:

Here is my patched prop.default

Question: if a patched recovery.img with adb is created for 9.0.4/9.0.5 could anyone use it?
Also, instead of fastboot flash recovery unsecure_recovery.img couldn't you just run fastboot boot recovery unsecure_recovery.img? I was able to boot and not flash the test TWRP build. That way you wouldn't have to reflash everything. It is this per device due to encryption?
Thanks for any info. Good find!

Y not create a core only boot image from magisk andThat share here so it would b really helful to all....

grandpajiver said:
Question: if a patched recovery.img with adb is created for 9.0.4/9.0.5 could anyone use it?
Also, instead of fastboot flash recovery unsecure_recovery.img couldn't you just run fastboot boot recovery unsecure_recovery.img? I was able to boot and not flash the test TWRP build. That way you wouldn't have to reflash everything. It is this per device due to encryption?
Thanks for any info. Good find!
Click to expand...
Click to collapse
The Recovery.img is from stock, so not a per-device thing.
I was just too lazy to find a place to upload large files.
I am currently on 10.0.4 but with 10.0.5 showing up, it would need updating later on.
I am not sure if you can flashboot boot recovery, certainly worth a try? Not sure how all this works, so I just flashed recovery and then flashed stock after I was done.
I also tested the TWRP build by not flashing it but booting it directly, but that was not very productive given it's current state.

hafiz.hasan said:
Y not create a core only boot image from magisk andThat share here so it would b really helful to all....
Click to expand...
Click to collapse
I was actually looking for this, but the how-to-build magisk guide has a lot more to do.
When I saw this guide I was like, oh I already have all the tools required Noice!

If only I didn't have tons of crap at work. This may be the gateway to v4a.
I have the images but not the extractor. Hmmmmm.

FreezyExp said:
I was actually looking for this, but the how-to-build magisk guide has a lot more to do.
When I saw this guide I was like, oh I already have all the tools required Noice!
Click to expand...
Click to collapse
Nice.. So are you gonna help building core only boot img for our device.?

hafiz.hasan said:
Nice.. So are you gonna help building core only boot img for our device.?
Click to expand...
Click to collapse
Nope sorry, not at this time.
There is a pull request on the magisk github that allows us to build Core-Only, so I will be waiting for that.
This guide contains the information that solved my immediate issue with not being in possesion of core-only.
Without having to deal with a lot of unknowns, just download some tools, extract some files, edit a few lines then patch it back up.

Bah. I've had no luck getting payload_dumper.py to work. failing on extracting logo, of all things.
Using windows 10 pro... python is installed, all requirements met... just cannot extract the .bin. Android Image Kitchen isn't for OTA bins either.. that wasn't helpful, unfortunately. Grr. I'm sure its either a stupid Windows thing or a stupid python thing... I installed 3.8 vs 3.6. Dunno. I prefer Perl
I'm not giving up though. I'll probably install Linux for Windows and run through that. Dunno.

grandpajiver said:
Bah. I've had no luck getting payload_dumper.py to work. failing on extracting logo, of all things.
Using windows 10 pro... python is installed, all requirements met... just cannot extract the .bin. Android Image Kitchen isn't for OTA bins either.. that wasn't helpful, unfortunately. Grr. I'm sure its either a stupid Windows thing or a stupid python thing... I installed 3.8 vs 3.6. Dunno. I prefer Perl
I'm not giving up though. I'll probably install Linux for Windows and run through that. Dunno.
Click to expand...
Click to collapse
Try with python 2.7
Sent from my OnePlus7TPro using XDA Labs

Lossyx said:
Try with python 2.7
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
This isn't fun to work on through a locked down Windows 10 pc. gonna try again on my chromebook after I get the 1.0.0.6 build.

here unsecure_adb_recovery 10.0.6 AB
to delete module
rm -rf /data/adb/modules/name of modules

every_one said:
here unsecure_adb_recovery 10.0.6 AB
to delete module
rm -rf /data/adb/modules/name of modules
Click to expand...
Click to collapse
You are awesome.
Found out 1.0.0.6 is Indian only. I guess I best make some coffee and try to work on US unlocked 1.0.0.5.

grandpajiver said:
You are awesome.
Found out 1.0.0.6 is Indian only. I guess I best make some coffee and try to work on US unlocked 1.0.0.5.
Click to expand...
Click to collapse
I got updated to 1.0.0.6.. I went from the '0' version to 'I'. Shrug.
fastboot boot recovery.img nor fastboot boot recovery recovery.img works... sigh.
I do have the full OTA. OnePlus7TOxygen_14.I.08_OTA_008_all_1911061912_10a180d3.zip. Dunno if anyone needs it.

I am on Linux. I used mktool to unpack and repack. I set all the flags properly between entered fastboot and Flash the new image to recovery as specified. device immediately hangs. I hold the keys to enter fastboot mode again and of course I can't run shell as ADB is not available in fastboot.

every_one said:
here unsecure_adb_recovery 10.0.6 AB
to delete module
rm -rf /data/adb/modules/name of modules
Click to expand...
Click to collapse
Hi, I'm stuck, I can't apply this tutorial to get a unsecure recovery. I'm on 10.0.6 international and when I try to boot to the file you provide, phone is stuck on "Fastboot Mode" screen. Is it from Indian variant? Could someone share the modified file from International 10.0.6 variant by any chance?
Or is it safe to flash this one? I don't want to try as I doesn't work with "fastboot boot unsecure_adb_recovery10.0.6.img".
I feel so dumb as I could flash back stock fastboot.img and my phone boots normally but then I don't have root access so can't delete the faulty module. If I boot a magisk patched boot.img then the phone doesn't boot, as the module is still there and activated....
Thanks

morback said:
Hi, I'm stuck, I can't apply this tutorial to get a unsecure recovery. I'm on 10.0.6 international and when I try to boot to the file you provide, phone is stuck on "Fastboot Mode" screen. Is it from Indian variant? Could someone share the modified file from International 10.0.6 variant by any chance?
Or is it safe to flash this one? I don't want to try as I doesn't work with "fastboot boot unsecure_adb_recovery10.0.6.img".
I feel so dumb as I could flash back stock fastboot.img and my phone boots normally but then I don't have root access so can't delete the faulty module. If I boot a magisk patched boot.img then the phone doesn't boot, as the module is still there and activated....
Thanks
Click to expand...
Click to collapse
You have to flash the recovery in order to boot into it.
If the recovery doesn't work you can just flash the stock one and you should be fine.
Sent from my OnePlus7TPro using XDA Labs

Lossyx said:
You have to flash the recovery in order to boot into it.
If the recovery doesn't work you can just flash the stock one and you should be fine.
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Well, that worked! Thanks for your help
I've never really used adb until now so I was a bit lost as the shell window doesn't send any command confirmation when we enter the folder then delete the files, I felt a bit blind. But it worked.
Is there a place I can find the stock recovery from 10.0.6 international to avoid downloading the full rom? I should be able to extract the recovery.img from fastboot full ROM should I?

morback said:
Well, that worked! Thanks for your help
I've never really used adb until now so I was a bit lost as the shell window doesn't send any command confirmation when we enter the folder then delete the files, I felt a bit blind. But it worked.
Is there a place I can find the stock recovery from 10.0.6 international to avoid downloading the full rom? I should be able to extract the recovery.img from fastboot full ROM should I?
Click to expand...
Click to collapse
I have not fiddled around with fastboot ROMs. But you should be able to download your OOS rom with Oxygen Updater.
If someone else haven't uploaded the stock recovery, you'll need to use a tool like this to extract the payload bin inside the zip. The recovery is named recovery.img
https://github.com/cyxx/extract_android_ota_payload
Sent from my OnePlus7TPro using XDA Labs

Development [RECOVERY][OFFICIAL][TWRP-3.7.0_12] TWRP for POCO F4

Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Introduction
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and
customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to
mash. The GUI is also fully XML driven and completely theme-able. You can change just about
every aspect of the look and
Click to expand...
Click to collapse
Prerequisites:
Code:
. Unlocked Bootloader
Installation instructions:
Recovery Install Method:
Simply download the TWRP-3.7.0_12-0 from twrp website and boot it using fastboot mode, steps are mentioned below
Fastboot Boot Method:
You will need the platform-tools from the Android SDK on your computer. Download only the platform-tools according to your device to get adb and fastboot binaries.
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type
Code:
adb reboot bootloader
You should now be in fastboot mode.
Download the twrp boot image from the link given below, and copy twrp.img file into the same folder as your adb and fastboot binaries and type:
Code:
fastboot boot twrp.img
You will be booted to TWRP, from there go to advanced and then click on "Flash Current TWRP"
REMEMBER: if the device waspreviously rooted, then root has been overwritten, you need to flash the magisk zip again to retain root
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Device Changelog
Version:3.7.0_12-0:
Initial Official Release
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Downloads
Official TWRP Website
My Telegram TWRP Support Group:
https://t.me/pocof4_recoveriesCredits:
- TWRP Team
Sources
TWRP: https://github.com/TeamWin/android_bootable_recovery
Device Tree: https://github.com/TeamWin/android_device_xiaomi_munch
Kernel Tree: https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/munch-s-oss
Status: Stable
TWRP: 3.7.0_12

reserved 1

reserved 2

Build will be live on twrp.me soon

Wow nice!

Build is live

Decrypting working? Will working on future Android 13 with decrypting? I know that dev received Android 13 already

Yes decrypting working fine, even on Android 13

When I updated yesterday, I immediately flashed it without losing data. For today's update, why doesn't it turn on, you have to turn on the new data format, is there the same or a solution

Can I just boot it with fastboot and flash Magisk flashable file in order to root the phone?
I have seen videos on youtube showing exactly that, just wanted to make sure it's doable.
Just want to root the phone, do not intend to flash any rom (yet).

dreamdrake said:
Can I just boot it with fastboot and flash Magisk flashable file in order to root the phone?
I have seen videos on youtube showing exactly that, just wanted to make sure it's doable.
Just want to root the phone, do not intend to flash any rom (yet).
Click to expand...
Click to collapse
If you already have your magisk_patched.img, you can choose which method you want:
1. with Fastboot + TWRP (temporary)
fastboot boot [drag and drop recovery.img]
flash your magisk_patched.img in boot partition + check "Flash to both slots"
reboot to system
2. only Fastboot
fastboot flash boot_a [drag and drop magisk_patched.img]
fastboot flash boot_b [drag and drop magisk_patched.img]
fastboot reboot

What if I would "fastboot boot TWRP.img" and then flash Magisk flashable version checking "flash to both slots"?

dreamdrake said:
What if I would "fastboot boot TWRP.img" and then flash Magisk flashable version checking "flash to both slots"?
Click to expand...
Click to collapse
When you check "Flash to both slots" TWRP will flash the makisk_patched.img to boot_a and boot_b.
I'm not sure, but if you don't check the box, TWRP will maybe flash to inactive slot and you are NOT rooted.
Edit: You can check which slot is active with adb shell getprop ro.boot.slot_suffix

Is it possible to make a backup of the installed rom with relative restore using this official twrp? If yes, which files to select

ok... i can't access to internal storage via pc. I formated data (type yes), rebooted to recovery again and my pc sees internal storage but there is no info about size and i can't copy files to it. It shows message something like "this device is disconnected". I tried to reinstall adb drivers, tried to restart my pc and it's not working. I used adb sideload to falsh ROM and after i booted to ROM, rebooted to recovery I can access internal storage via TWRP.

Runs super laggy with kernel compiled with gcc which is very strange and annoying.

Can't access storage with PC... Disabled and enabled MTP multiple times...
I had to flash ROM via OTG...