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.
Hello, I have sent my phone to warranty and after that I received a phone with NO RPMB and after many frustrations I found (with help of many users and forums) how to workaround this..
To start:
Download boot image from here
Download twrp from the official website
Change the name to boot.img and twrp.img and put it in the platform-tools folder
Open the terminal there
Download your favourite rom
Enter fastboot mode on your phone
!!!!After this you will loose all of your data!!!!
Paste this to the terminal
fastboot oem unlock
(select yes on your phone)
fastboot flash boot boot.img
fastboot flash recovery twrp.img
fastboot format userdata
fastboot format cache
Reboot to recovery (if it doesn't enter at the first time enter download mode again and restart to recovery)
After that you have twrp and can flash every rom.. yay!!!
Wipe everything.
Copy the rom zip to your phone using MTP
Install your fancy new rom
If you want to install magisk:
Install the magisk manager.
On the app select install and select patch image file. (it will create a new boot image already patched)
After that install the new image (patched_boot.img) using twrp
Do a clean instalation of your ROM (recomended) or a Factory Reset first
Reboot to twrp
Select install
Click in install image
Select patched_boot.img
Select install to boot partition
Reboot.
Install magisk manager and do the sugested setup.
You now have magisk working
Thanks to all the users that helped me!!
I had real trouble getting twrp to work the last time I tried this a few months ago. Followed the steps here and am now on pixel experience with magisk. Thanks!
Hello, im in the same situation of NO RPMB. This procedure will permanently lets have bootloader unlocked?
About Magisk, i can install it in usual way once im in the recovery? (I mean download latest stable version for Bullhead and flash via TWRP).
Thanks.
sigibian said:
Hello, im in the same situation of NO RPMB. This procedure will permanently lets have bootloader unlocked?
About Magisk, i can install it in usual way once im in the recovery? (I mean download latest stable version for Bullhead and flash via TWRP).
Thanks.
Click to expand...
Click to collapse
My bootloader is still unlocked after following this guide
For Magisk:
-Install your custom ROM and boot it up (without root)
-Then extract the boot.img from the ROM zip file and save it on your phone storage.
-Install the Magisk manager apk
-In Magisk manager, select install Magisk> choose the patch boot image option and -Select the boot.img you previously saved.
Once it's done, reboot into twrp and flash the patched boot.img. When you reboot Magisk will be working.
I've had no issues with my bootloader, even after an ota update for pixel experience.
Thank you, i will try it.
Another question. I never tried dowload mode before, as i read in other post i should Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb that's already connected to pc, right?
When in download mode i can fire up fastboot commands like im in bootloader mode?
So then after do last command fastboot format cache i can reboot to recovery from terminal using adb reboot recovery or i can / should do it from device?
About twrp it's ok to use the latest 3.2.3.0 official version or the 3.2.1 4core version from here as someone suggested from Reddit? https://forum.xda-developers.com/nexus-5x/development/recovery-twrp-3-2-1-4-core-t3796656
sigibian said:
Thank you, i will try it.
Another question. I never tried dowload mode before, as i read in other post i should Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb that's already connected to pc, right?
When in download mode i can fire up fastboot commands like im in bootloader mode?
So then after do last command fastboot format cache i can reboot to recovery from terminal using adb reboot recovery or i can / should do it from device?
About twrp it's ok to use the latest 3.2.3.0 official version or the 3.2.1 4core version from here as someone suggested from Reddit? https://forum.xda-developers.com/nexus-5x/development/recovery-twrp-3-2-1-4-core-t3796656
Click to expand...
Click to collapse
The official twrp works for fine for me, haven't tried the 4 core version but it can't hurt to try if you need it.
Power off your phone then press and hold volume - and power to enter bootloader, then connect to your pc and follow the steps in the OP
So i have to enter in bootloader mode? At point 6 of OP there is written to enter in the download mode, this makes me confusing.
Can anyone explain me latest 2 commands why they are needed?
fastboot format userdata
fastboot format cache
sigibian said:
So i have to enter in bootloader mode? At point 6 of OP there is written to enter in the download mode, this makes me confusing.
Can anyone explain me latest 2 commands why they are needed?
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
This thread is fairly comprehensive;
https://forum.xda-developers.com/nexus-5x/general/moto-nexus-5x-sticky-roll-t3207487
Holding volume - and power takes you to fastboot mode (download mode essentially), theres also an option to reboot into recovery (selectable using the volume keys.)
Formatting user data and cache is necessary prior to installing a new rom (especially if moving from stock). You lose all data (back up first!) But a clean flash is the best place to start.
baddesthad said:
This thread is fairly comprehensive;
https://forum.xda-developers.com/nexus-5x/general/moto-nexus-5x-sticky-roll-t3207487
Holding volume - and power takes you to fastboot mode (download mode essentially), theres also an option to reboot into recovery (selectable using the volume keys.)
Formatting user data and cache is necessary prior to installing a new rom (especially if moving from stock). You lose all data (back up first!) But a clean flash is the best place to start.
Click to expand...
Click to collapse
Thanks for the explanation but for installing a new ROM usually you can do factory reset directly in TWRP, plus doing all the wipes, this should be enough.
About fastboot mode and download mode, they are completely different, fastboot mode: vol down + power, download mode for LG: Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb.
My question is what i can do in download mode? As OP says after entering download mode open terminal and use fastboot commands.
sigibian said:
Thanks for the explanation but for installing a new ROM usually you can do factory reset directly in TWRP, plus doing all the wipes, this should be enough.
About fastboot mode and download mode, they are completely different, fastboot mode: vol down + power, download mode for LG: Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb.
My question is what i can do in download mode? As OP says after entering download mode open terminal and use fastboot commands.
Click to expand...
Click to collapse
You need to use vol- and power to go into fastboot mode then connect to the pc. As for userdata and cache, if you don't clean them when coming from stock you will have issues (your data will be encrypted if you're on stock?). As I said this guide worked for me. The op was talking about fastboot mode in the 6th option (also there is much more information in the thread I linked above)
sorry for the confusing i wanted to say fastboot mode..
i knew the thread that you are saying but most people doesn't want to search so I made a little thread only with the needed parts..
I use it myself so I have a place to remember all the steps when I need to change the rom to a new one or when I make experiments and brick my phone XD
If anyone know anything else that should be in here just say, I really want to improve the post
Hi. I just went through the whole process several times (I have tried the different modified boot images from the dedicated post) and my device is still locked [emoji24] any suggestions?
fhartane said:
Hi. I just went through the whole process several times (I have tried the different modified boot images from the dedicated post) and my device is still locked [emoji24] any suggestions?
Click to expand...
Click to collapse
your device will always be locked this is a workaround to get twrp, new roms and magisk while it stays locked..
with twrp usable it won't matter if you are locked or not
PedroM.CostaAndrade said:
your device will always be locked this is a workaround to get twrp, new roms and magisk while it stays locked..
with twrp usable it won't matter if you are locked or not
Click to expand...
Click to collapse
Thanks for the answer. You mean that now I have twrp, I can flash custom Roms with my bootloader locked without any issue?
Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
Yes if you have TWRP you can install custom ROMs, custom Kernel's, magisk, super su, etc..
the locked bootloader only prevents you from using fastboot commands like the one needed for installing custom recovery
Now that you have TWRP you can use it for everything
Hello everyone, I also have a nexus 5x with motherboard that has been replaced under warranty and unfortunately I can't keep the bootloader unlocked.
I tried the procedure you have indicated, but at this point there is the problem, because after inserting the boot.img and twrp.img inside the phone, then when I go to do the unlocking procedure with 'fastboot oem unlock (select yes on your phone) 'in practice the memory is deleted on the phone, so I lose the previously uploaded files, and therefore I can no longer continue with the flash procedure of boot.img and twrp.img because they are no longer present in memory.
I hope I made myself understood, maybe I am wrong, or is there a way to solve this problem?
Fabiojoker said:
Hello everyone, I also have a nexus 5x with motherboard that has been replaced under warranty and unfortunately I can't keep the bootloader unlocked.
I tried the procedure you have indicated, but at this point there is the problem, because after inserting the boot.img and twrp.img inside the phone, then when I go to do the unlocking procedure with 'fastboot oem unlock (select yes on your phone) 'in practice the memory is deleted on the phone, so I lose the previously uploaded files, and therefore I can no longer continue with the flash procedure of boot.img and twrp.img because they are no longer present in memory.
I hope I made myself understood, maybe I am wrong, or is there a way to solve this problem?
Click to expand...
Click to collapse
fastboot is for the files on your PC not your phone
you need to put the files inside of platform-tools and then open cmd inside it and use the fastboot commands
fastboot will take the files of your PC
Hello, thank you for your information, since I haven't done modding on phones for a long time, I didn't remember exactly the procedure with fastboot and therefore I didn't understand where I had to put the files, but in the end I did it.
Thank you
PedroM.CostaAndrade said:
fastboot is for the files on your PC not your phone
you need to put the files inside of platform-tools and then open cmd inside it and use the fastboot commands
fastboot will take the files of your PC
Click to expand...
Click to collapse
Why is a custom boot image needed? I don't want to root.
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
For future use or other versions like OOS EUROPE,INDIA, etc. , you can patch your own boot.img with my tool here
But for now just follow the instructions
Boot.img patched with MAGISK 20.4 on OOS 10.0.12 HD65AA (GLOBAL)
Only for OOS 10.0.12 Global!!!!
Enjoy!
Instructions:
reboot to fastboot
Code:
adb reboot bootloader
Code:
fastboot boot magisk_patched_10_0_12.img
let it boot and check if u have root
if u got root then reboot to fastboot again
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched_10_0_12.img
When finished type
Code:
fastboot reboot
patched boot.img download: https://drive.google.com/file/d/1JeNPnEtKKkXYBVlo4pW0VUEnP1BQ7nt_/view?usp=sharing
stock boot.img download: https://drive.google.com/file/d/1rrUcVyTBUl-sED35lxuK82UQ0hHM_PRg/view?usp=sharing
I would be glad if somebody share Magisk patched boot to 10.0.12HD65BA for EU version
Tapatalk via OnePlus 7T
Thank You
I would be glad if somebody share Magisk patched boot to 10.0.12HD65BA for EU version. I can not patch it myself, because 10.0.12HD65BA is not online on oneplus website.
ba47 said:
I would be glad if somebody share Magisk patched boot to 10.0.12HD65BA for EU version. I can not patch it myself, because 10.0.12HD65BA is not online on oneplus website.
Click to expand...
Click to collapse
If u r already on 10.0.12 EU u dont need the rom
If u r on previous OOS then use the oxygen updater app from Play store to update
ba47 said:
I would be glad if somebody share Magisk patched boot to 10.0.12HD65BA for EU version. I can not patch it myself, because 10.0.12HD65BA is not online on oneplus website.
Click to expand...
Click to collapse
One guy already upload this file here :
https://drive.google.com/file/d/1-_3fL5HkWS9cplro7iNiIzqlL_AGTz2B/view?usp=drivesdk
Tapatalk via OnePlus 7T
Hm, I have HD65AA India and after boot (not flash) via fastboot attached here patched boot.img I don't have internet (gsm and wifi).
Do you have India's version of that patch ?
KyoshiDev said:
Instructions:
reboot to fastboot
Code:
adb reboot bootloader
Code:
fastboot boot magisk_patched_10_0_12.img
let it boot and check if u have root
if u got root then reboot to fastboot again
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched_10_0_12.img
Click to expand...
Click to collapse
4. and 5. Step isn't needed.
When you boot your image and check if you have root you just klick: Install --> Install --> direct install. It will automatically patch your actual boot.img and you will permanently have a rooted phone.
I didn't find patched boot.img to 10.0.12/10.3.4 India (!) version, so I created my own (faq linked above).
It works on my device like a charm. I have already gsm internet and WiFi and of course rooted device.
If someone wants to try on 10.3.4/10.0.12 AA (Global and only India version) , I put my patched boot.img here:
https://drive.google.com/file/d/1p6tgyc_WcLl2CW4ysq4xGgFXnmO95Kl0/view?usp=sharing
Did not work for me on reboot after root check says not rooted?
---------- Post added at 06:54 PM ---------- Previous post was at 06:44 PM ----------
Nope did not work for me say I do not have root on root check?
=dgim= said:
I didn't find patched boot.img to 10.0.12/10.3.4 India (!) version, so I created my own (faq linked above).
It works on my device like a charm. I have already gsm internet and WiFi and of course rooted device.
If someone wants to try on 10.3.4/10.0.12 AA (Global and only India version) , I put my patched boot.img here:
https://drive.google.com/file/d/1p6tgyc_WcLl2CW4ysq4xGgFXnmO95Kl0/view?usp=sharing
Click to expand...
Click to collapse
I have updated to 10.3.4.HD65AA yesterday. Have been rooted since much earlier version with Magisk Canary. Now I want to change to stable but not sure of the process.
How do I uninstall Canary version? There does not seem to be any uninstall option in Magisk Manager Canary version. Can I just uninstall as I would any other app?
Is the file you uploaded correct for my version? Would it install Magisk Stable version?
After going into fastboot do I have to connect to PC and give commands there or in the phone itself. Have done it earlier but I forgot. If from PC, which software to use for ADB?
Edit : Will this wipe data?
You can use via TWRP, I suppose (not tested) this Magisk's unistall zip file: https://github.com/topjohnwu/magisk_files/tree/canary
If you flashed a new rom (10.3.4) I believe that you have already stock boot.img, so device is unrooted.
If yes, you can - first, only booted my patched_boot.img to see that everything is OK (gsm, wifi, magisk manager works etc),
and, then, try flash it via fastboot.
I patched my stock boot.img (10.3.4 India version) via latest Magisk Canary.
Here is FAQ:
https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
=dgim= said:
You can use via TWRP, I suppose (not tested) this Magisk's unistall zip file: https://github.com/topjohnwu/magisk_files/tree/canary
If you flashed a new rom (10.3.4) I believe that you have already stock boot.img, so device is unrooted.
If yes, you can - first, only booted my patched_boot.img to see that everything is OK (gsm, wifi, magisk manager works etc),
and, then, try flash it via fastboot.
I patched my stock boot.img (10.3.4 India version) via latest Magisk Canary.
Here is FAQ:
https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
Click to expand...
Click to collapse
I think TWRP is not working for OnePlus7T so not sure about that.
I have updated from rooted 10.3.2 to 10.3.4 via OTP and I already have Magisk Canary. So I am rooted. I want to remove this and get to Magisk Stable version.
jesrani said:
I think TWRP is not working for OnePlus7T so not sure about that.
I have updated from rooted 10.3.2 to 10.3.4 via OTP and I already have Magisk Canary. So I am rooted. I want to remove this and get to Magisk Stable version.
Click to expand...
Click to collapse
Booting and flashing TWRP on recovery partition, I suppose, is working.
I didn't flash Magisk install or unistall via TWRP on OP7T.
Are you sure that, after flashing new rom, your device is rooted ?
Even you have installed Magisk Canary, but - SatetyNet etc, is passed in your device after flashed stock 10.3.4 ?
If not, you can just unistall apk (Magisk Manager), clear cache, flash patched boot.img and install stable Magisk (I didn't test stable on 10.3.4).
I'm lost somehow.
I'm rooted, Global (USA) phone. Last version is 10.0.11.
First, to which directory do I download the patched .img file. To my phone, to my computer? So far I have put in both Magisk directory and my root directory.
I reboot the bootloader. Fine. I fastboot the patched image. Fine. Check for root. Fine
I reboot the bootloader. Fine. Comes up with a menu. The top of the menu says Start.
Then I type fastboot flash boot magisk_patched_10_0_12.img. And nothing happens. I have tried the power button and nothing either. I tried going into Magisk and install as another forum member suggested, but now my phone comes up, still hasn't upgraded to 12. Also now when I click any app the phone it just reboots itself. So I'm really messed up.
My question is what was suppose to happen when i clicked fastboot flash boot magisk_patched_10_0_12.img with the bootloader menu on my screen and where was the .img file suppose to be located. Am I doing this right from my PC (Win10 - PowerShell).
I'm lost because I have been upgrading previously and have had no trouble. Where did I go wrong. Much thanks.
KyoshiDev said:
For future use or other versions like OOS EUROPE,INDIA, etc. , you can patch your own boot.img with my tool here
But for now just follow the instructions
Boot.img patched with MAGISK 20.4 on OOS 10.0.12 HD65AA (GLOBAL)
Only for OOS 10.0.12 Global!!!!
Enjoy!
Instructions:
reboot to fastboot
Code:
adb reboot bootloader
Code:
fastboot boot magisk_patched_10_0_12.img
let it boot and check if u have root
if u got root then reboot to fastboot again
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched_10_0_12.img
patched boot.img download: https://drive.google.com/file/d/1JeNPnEtKKkXYBVlo4pW0VUEnP1BQ7nt_/view?usp=sharing
stock boot.img download: https://drive.google.com/file/d/1rrUcVyTBUl-sED35lxuK82UQ0hHM_PRg/view?usp=sharing
Click to expand...
Click to collapse
davekaye said:
I'm rooted, Global (USA) phone. Last version is 10.0.11.
First, to which directory do I download the patched .img file. To my phone, to my computer? So far I have put in both Magisk directory and my root directory. .
Click to expand...
Click to collapse
to your computer, or rather, to the directory where your adb and fastboot files are, or if you have adb installed system widely, you should put your img in the folder where you are running your cmd window or you can navigate with cmd to the file with "cd"
davekaye said:
Then I type fastboot flash boot magisk_patched_10_0_12.img. And nothing happens. I have tried the power button and nothing either. I tried going into Magisk and install as another forum member suggested, but now my phone comes up, still hasn't upgraded to 12. Also now when I click any app the phone it just reboots itself. So I'm really messed up.
Click to expand...
Click to collapse
What do you mean with "still hasn't upgraded to 12"? You mean OOS 10.0.12? Then you need to update from 10.0.11 to 10.0.12 before rooting your boot partition with a boot.img from an OOS 10.0.12
davekaye said:
My question is what was suppose to happen when i clicked fastboot flash boot magisk_patched_10_0_12.img with the bootloader menu on my screen and where was the .img file suppose to be located. Am I doing this right from my PC (Win10 - PowerShell).
I'm lost because I have been upgrading previously and have had no trouble. Where did I go wrong. Much thanks.
Click to expand...
Click to collapse
nothing should happen to your bootloader screen, but you should see in your cmd window, that the flashing finished, then you can type "fastboot reboot" to reboot your phone.
KyoshiDev said:
to your computer, or rather, to the directory where your adb and fastboot files are, or if you have adb installed system widely, you should put your img in the folder where you are running your cmd window or you can navigate with cmd to the file with "cd"
What do you mean with "still hasn't upgraded to 12"? You mean OOS 10.0.12? Then you need to update from 10.0.11 to 10.0.12 before rooting your boot partition with a boot.img from an OOS 10.0.12
nothing should happen to your bootloader screen, but you should see in your cmd window, that the flashing finished, then you can type "fastboot reboot" to reboot your phone.
Click to expand...
Click to collapse
Thanks. My fault. Since I don't have a working TWRP I haven't been playing around with any ROMs and I guess I'm rusty. So I tried to put your upgrades on the wrong version of Oxygen (11 not 12) and ran into a bootloop. I could not boot into EDL mode (another issue I have to follow up) and it took me some time to finally boot back to 11 and then do the OTA upgrade to 12. All is working now, so thanks again.
Hello, is SafetyNet supposed to fail or I've messed something up?
1nikolas said:
Hello, is SafetyNet supposed to fail or I've messed something up?
Click to expand...
Click to collapse
Safetynet should pass
So i put this on my US version. HD1905. I should have been more careful. Anyway, everything works well except netflix., which is now a system app and will not run or uninstall.
PS: Do you have US version patched boot file ?
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?