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
Related
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.
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
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.
Hello fellow XDA'ers
I have waited and unlocked the phone, running the MIUI 12.5.1.0 (RKHEUXM) the EU Official Rom that came with the phone, and was following the guide on how to root from NaldoTech, but i'm stuck, magisk can't patch any Firmware file i throw at it...
Don't know what i am doing wrong, i opened the zip files manually looking for the boot.img file but i cant seem to find it in any of the Firmwares i download from XiaomiFirmwareUpdater.
Also tried downloading the rom file and extracting the contents using the xiaomi-flashable-firmware-creator, but no luck with that either, throws some permission error at extracting the payload.bin
what can i do from here??
thanks in advance
Easy peasy
Steps
Download Adb and fastboot tool.
Or just download TWRP image and start CMD from there "the folder containing the twrp img" (in destination bar type cmd and press Enter) /the drivers should be installed and working properly ofc.
1- set phone in fastboot mode then plug it in to PC
2- Type: fastboot boot twrp.img (twrp here is the img file)
Then the phone will boot into twrp.
The phone will be shown in PC. Paste Magisk in the phone. Then go back and flash it using TWRP. Then reboot to system. And you're all done.
laid1995 said:
.
Click to expand...
Click to collapse
doesnt boot to twrp just turns off :S
Fyat said:
doesnt boot to twrp just turns off :S
Click to expand...
Click to collapse
You're doing something wrong then.
Check all drivers are set up properly. Try flashing twrp then boot to it using Volume UP + Power button.
Make sure you download Nebrassy's twrp 3.5.10
Managed to do it, not with twrp tho, the way i intended originally, i found this payload extractor, went on miui and download latest package (on the phone), after that sent the file to pc and extracted the contents to the payload extractor tool, follow the tool's guide and Tadaaaa! got yoursef a boot.img.
after that was simple and follow the rest of the NaldoTech guide, which is sending the boot.img to phone, open magisk manager, click install, select the boot image to pach, wait couple seconds and done. After that just copy the magisk patched boot image to pc and turn off your phone, enter fastboot, and flash the boot.img in boot_a and boot_b.
and you are done boot the phone and open magisk app to see the installed confirmation
Fyat said:
Managed to do it, not with twrp tho, the way i intended originally, i found this payload extractor, went on miui and download latest package (on the phone), after that sent the file to pc and extracted the contents to the payload extractor tool, follow the tool's guide and Tadaaaa! got yoursef a boot.img.
after that was simple and follow the rest of the NaldoTech guide, which is sending the boot.img to phone, open magisk manager, click install, select the boot image to pach, wait couple seconds and done. After that just copy the magisk patched boot image to pc and turn off your phone, enter fastboot, and flash the boot.img in boot_a and boot_b.
and you are done boot the phone and open magisk app to see the installed confirmation
Click to expand...
Click to collapse
Whatever was your way, I'm glad you managed to do it
sir i need boot.img file for poco f3
ZAki6464 said:
sir i need boot.img file for poco f3
Click to expand...
Click to collapse
Good
Which version do you need?
Is this international version I should get to use in USA on T-Mobile to root the same way as you?
Amazon F3
I'm using Europe version currently on Global 12.5.6.0 (RKHEUXM)
Fyat said:
I'm using Europe version currently on Global 12.5.6.0 (RKHEUXM)
Click to expand...
Click to collapse
Do you have access to gpu rendering tweaks in turbo game mode ? I can't make it work, I'm on same version than you
Greenspoof said:
Do you have access to gpu rendering tweaks in turbo game mode ? I can't make it work, I'm on same version than you
Click to expand...
Click to collapse
I'm not sure where to find these options as i do not use the turbo mode, can you point to it?