Related
[A2017U - B29] "Fastboot Flashing Unlock" returns "Unknown Command" in ADB
Hi !
Quick info: I am not a novice when it comes to rooting / unlocking bootloader / installing TWRP or CWM / installing Xposed Frameworks, etc
I will make this short and sweet.
My Info :
- Axon 7 Gold - A2107U (US variant) with Update B29 installed (A2017UV1.0.0B29)
- Minimal ADB and Fastboot
- Windows 7 x64 Home premium
Here are the steps I have done:
1-
I installed the ADB drivers and Qualcomm WWAN drivers on my computer.
2-
Under Developers settings, I have enabled "OEM Unlocking".
3-
Using Axon7backup.exe, I created 2 backup files: "stock_recovery_backup.img" and "stock_boot_backup.img"
4-
Rebooted in bootloader using "adb reboot bootloader", (my device was listed). I first tried "fastboot oem unlock" then tried "fastboot flashing unlock", both returning "Unknown Command".
HERE IS WHERE I AM CONFUSED:
Normally, anyone would Unlock to bootloader THEN install TWRP, but from what I've seen with Axon7, some people say that Installing TWRP is "required" to unlock the bootloader.
I've seen some say that they have successfully rooted / unlocked bootloader with the B29 update, but I don't see any zip files or threads for the B29.
Could anyone enlighten me on the steps that I (and many others) have to do in order to Unlock the Bootloader and be able to install TWRP and Xposed Framework (and root).
Thank you !
Could anyone enlighten me on the steps that I (and many others) have to do in order to Unlock the Bootloader and be able to install TWRP and Xposed Framework (and root).
Thank you ![/QUOTE]
Ok so the long story short is that the bootloader is not unlockable out of the box. When ZTE released the bootloader unlock, they released a separate ota for it called B20_boot from B20 which modified the fastboot image. It didn't make sense for a lot of people for ZTE to release a separate OTA since it would not allow them to recieve future otas (such as B29) so they are working on a new bootloader unlock. So since you are on B29 and the bootloader is not unlockable out of the box and you cannot update to B20_boot since you are not on B20 this is what you do:
1) I am assuming you already have the tool downloaded since you used it to create the backup files so just follow the same instructions to boot into edl mode, then open a command window where the tool is located. Then execute:
Code:
axon7backup.exe
to start the tool and then
Code:
axon7root.exe -p # -r
where # is your COM Port # in Device Manager. The tool will flash the signed version of TWRP with ZTE's signature from the leaked firehose onto your Axon 7.
2)Hold down volume up and power to exit download mode and boot into recovery which should now be TWRP.
3) Download the bootloader unlock zip from @DrakenFX: https://www.androidfilehost.com/?fid=529152257862665656. Flashing the zip will replace your fastboot image with the one from B20_boot.
4) After you have flashed the zip, reboot to bootloader and just execute
Code:
fastboot oem unlock
and you are good to go!
^^The stock fastboot does not support the unlocking command. There's another fastboot image in the bootloader unlock thread that gets flashed first. *THEN* you can issue the unlock command.
I've been messing with android at least since late 2009 and have seen many variants of unlocking processes. This one is new for me too.
bkores said:
Ok so the long story short is that the bootloader is not unlockable out of the box. When ZTE released the bootloader unlock, they released a separate ota for it called B20_boot from B20 which modified the fastboot image. It didn't make sense for a lot of people for ZTE to release a separate OTA since it would not allow them to recieve future otas (such as B29) so they are working on a new bootloader unlock. So since you are on B29 and the bootloader is not unlockable out of the box and you cannot update to B20_boot since you are not on B20 this is what you do:
1) Go to this thread: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204. Download @tenfar's tool for A2017U B20(axon7root.exe not axon7backup.exe). There is no tool for B27 or B29 because the OP is no longer active but it will still work(I have tested.)
Click to expand...
Click to collapse
I see that the release a "axon7root-us-b27.zip" here: http://d-h.st/kRgq
"Uploaded By: tenfar
Uploaded On: 2016-09-19 23:10:07"
Should I use the B27 or follow the B20 method ?
EDIT: Should I do following command ?: reboot disemmcwp (to remove protect write, or it's no longer necessary? )
Boutchoo said:
I see that the release a "axon7root-us-b27.zip" here: http://d-h.st/kRgq
"Uploaded By: tenfar
Uploaded On: 2016-09-19 23:10:07"
Should I use the B27 or follow the B20 method ?
Click to expand...
Click to collapse
I edited my original answer. Since you already have axon7backup.exe you don't have to download the tool. And yes you should do "reboot disemmcwp" if you want to be able to make changes to /system
bkores said:
I edited my original answer. Since you already have axon7backup.exe you don't have to download the tool.
Click to expand...
Click to collapse
Nice ! TWRP is now installed !
I was wondering, if I backup my DATA only using TWRP and restore them after doing "fastboot oem unlock", will I be able to get my apps back without breaking my system ?
EDIT: After doing "Fastboot oem unlock", TWRP gives me "Mount: Decrypt Data: Enter Password:"...
EDIT2: Ok now Android is locked... it's asking me to enter a password *NEVER MIND- FORMATED CELL, NOW WORKS*
Edit3: Do I need to flash SuperSU or is it pre-packaged ?
Boutchoo said:
Nice ! TWRP is now installed !
I was wondering, if I backup my DATA only using TWRP and restore them after doing "fastboot oem unlock", will I be able to get my apps back without breaking my system ?
EDIT: After doing "Fastboot oem unlock", TWRP gives me "Mount: Decrypt Data: Enter Password:"...
EDIT2: Ok now Android is locked... it's asking me to enter a password
Click to expand...
Click to collapse
Did you just flash TWRP using -r or flashed the boot image as well using -b? Because if you just flashed TWRP the data decryption thing should not have happened. For some reason ZTE screwed up encryption to the point where if you backup data in TWRP with a pin/password/pattern enabled and then restore from it you will get a data decryption prompt where no password would work, not even your own. If you get this you have no choice but to wipe your data and then do either a Google restore during setup or use Titanium Backup(after you flash SuperSU) if you have it. In the future if you want to backup your data and until ZTE fixes it, you have to disable your pin/password/pattern first.
bkores said:
Did you just flash TWRP using -r or flashed the boot image as well using -b? Because if you just flashed TWRP the data decryption thing should not have happened.
Click to expand...
Click to collapse
I copy pasted your line "axon7root.exe -p 8 -r" only, did nothing else.
Also, do I need to flash SuperSU for the root or is it pre-packaged ?
Boutchoo said:
I copy pasted your line "axon7root.exe -p 8 -r" only, did nothing else.
Also, do I need to flash SuperSU for the root or is it pre-packaged ?
Click to expand...
Click to collapse
Flash SuperSU
bkores said:
Flash SuperSU
Click to expand...
Click to collapse
When I flash SuperSU-v2.78-201609011115.zip from my SD Card, it crashes TWRP.
Boutchoo said:
When I flash SuperSU-v2.78-201609011115.zip from my SD Card, it crashes TWRP.
Click to expand...
Click to collapse
You need SuperSU v2.65 as any other version will crash TWRP(no one knows why)
bkores said:
You need SuperSU v2.65 as any other version will crash TWRP(no one knows why)
Click to expand...
Click to collapse
Ah, I see. It's weird !
Also, what does flashing the boot (-b) does with the Axon 7 ? It's weird that only recovery (-r) is necessary.
Boutchoo said:
Ah, I see. It's weird !
Also, what does flashing the boot (-b) does with the Axon 7 ? It's weird that only recovery (-r) is necessary.
Click to expand...
Click to collapse
The modified boot image allows people without an unlocked bootloader to have root however if your bootloader is unlocked you should not do it as you will have the data decryption issue.
Boutchoo said:
When I flash SuperSU-v2.78-201609011115.zip from my SD Card, it crashes TWRP.
Click to expand...
Click to collapse
Try 2.65
With the huawei support down, could anyone please help me to unlock huawei nova 2i RNE-L22 bootloader and to root it?
DC. UNLOCKER?
https://www.dc-unlocker.com/how-to-read-huawei-bootloader-unlock-code
bootloader unlock codes forbidden
Chisetdel31260 said:
DC. UNLOCKER?
It says
> If your phone runs Android 8 or later with latest security patch - then this service won't work!
I have the latest security patch(March 1, 2019), I've been searching for the past 3 days for a working method to root my mate 10 lite, found nothing.
Huawei stopped providing oem unlock codes, All the services that provided unlock codes for money are now obsolete too.
I'm trying to find a way to root this phone on my own, but I'm not sure where to go from here.
I've read this book today "XDA Developers' Android Hacker's Toolkit", but it teaches how to use rooting methods that are already out there and not how to create your own way to root a device.
Can you provide guidance on where to go from here to learn how to find vulnerabilities in android?
Click to expand...
Click to collapse
"If your phone runs Android 8 or later with latest security patch - then this service won't work! " it's true , you must downgrade to Nougat via HiSuite .
it works
bozka1 said:
"If your phone runs Android 8 or later with latest security patch - then this service won't work! " it's true , you must downgrade to Nougat via HiSuite ane than using Service ROM flash FW with security patch max. april 2018. After you can get bootloader unlock code here
(4€/4$).
Service ROMs you can find here :
Type RNE- or Rhone or Mate 10 lite. Gl!
Click to expand...
Click to collapse
Thanks, it worked!
I got my bootloader unlocker, now I'm installing a custom rom, but there's no much custom roms for mate 10 lite.
m10_lite said:
Thanks, it worked!
I got my bootloader unlocker, now I'm installing a custom rom, but there's no much custom roms for mate 10 lite.
Click to expand...
Click to collapse
Best Custom ROM is Stock ROM & root .
bozka1 said:
Best Custom ROM is Stock ROM & root .
Click to expand...
Click to collapse
Do you have the guide for rooting RNE-L21, stock ROM, Android and EMUI version 8.0?
davideakc said:
Do you have the guide for rooting RNE-L21, stock ROM, Android and EMUI version 8.0?
Click to expand...
Click to collapse
He did already
bozka1 said:
"If your phone runs Android 8 or later with latest security patch - then this service won't work! " it's true , you must downgrade to Nougat via HiSuite ane than using Service ROM flash FW with security patch max. april 2018. After you can get bootloader unlock code here
https://www.dc-unlocker.com/how-to-read-huawei-bootloader-unlock-code
(4€/4$).
Service ROMs you can find here :
https://androidhost.ru/search.html
Type RNE- or Rhone or Mate 10 lite. Gl!
Click to expand...
Click to collapse
ante0 said:
He did already
Click to expand...
Click to collapse
Sorry, I've not explained clearly what i want to do...
I'm already with bootloader unlocked, I need a guide for root the phone
davideakc said:
Sorry, I've not explained clearly what i want to do...
I'm already with bootloader unlocked, I need a guide for root the phone
Click to expand...
Click to collapse
Sorry, I misread. xD
Well, you can either flash TWRP for Oreo. Not sure which is "best" though, take one with decryption support if available for RNE on Oreo. Then you flash Magisk zip in twrp.
Or you can take your stock ramdisk and patch it in Magisk Manager, then flash the patched ramdisk from fastboot.
I would provably go with TWRP and Magisk zip though, as you would need a stock ramdisk from an update.app of your build. So saves some downloading
Basically flash TWRP using fastboot: fastboot flash recovery_ramdisk twrp.img
Reboot to recovery which will end up in TWRP. Flash latest Magisk using the Install button in twrp.
ante0 said:
Sorry, I misread. xD
Well, you can either flash TWRP for Oreo. Not sure which is "best" though, take one with decryption support if available for RNE on Oreo. Then you flash Magisk zip in twrp.
Or you can take your stock ramdisk and patch it in Magisk Manager, then flash the patched ramdisk from fastboot.
I would provably go with TWRP and Magisk zip though, as you would need a stock ramdisk from an update.app of your build. So saves some downloading
Basically flash TWRP using fastboot: fastboot flash recovery_ramdisk twrp.img
Reboot to recovery which will end up in TWRP. Flash latest Magisk using the Install button in twrp.
Click to expand...
Click to collapse
Don't worry, thanks for the fast reply!
davideakc said:
Don't worry, thanks for the fast reply!
Click to expand...
Click to collapse
I can't find any TWRP with decryption. This one might work, it's from the MorfuZ thread: https://mega.nz/#!uD4FlCqL!ERBzP4ZWa2sR8f_wnn15F_cOFCdYVKgfYETjiehQkkQ
So it may or may not have working decryption. But if you have an external SD it doesn't really matter as you'd only transfer magisk to that.
Magisk from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Download latest stable.
Flash twrp using fastboot.
Reboot to recovery.
Transfer magisk zip to external SD.
Flash Magisk zip using the Install button
You will probably have to browse to /external_sd manually as it will default to /sdcard in the install browser.
If it fails to install using TWRP:
Open terminal in TWRP from the Advanced button then enter this command:
dd if=/dev/block/bootdevice/by-name/ramdisk of=/external_sd/ramdisk.img
This will dump your stock ramdisk to external sd, which you then can patch in Magisk Manager and flash the output file to 'ramdisk' using fastboot. You will have to install Magisk Manager apk first though, it can be found in the Magisk thread.
davideakc said:
Do you have the guide for rooting RNE-L21, stock ROM, Android and EMUI version 8.0?
Click to expand...
Click to collapse
Only EMUI 8.x !!!
Your device must have an*unlocked bootloader.
Huawei HiSuite installed on your computer because it will install all the USB drivers
Download and install*Minimal ADB and fastboot Tool*on your computer. The folder location should be C:\Program Files(x86)\Minimal ADB and fastboot.
https://www.the***********.com/minimal-adb-and-fastboot-tool-for-windows/
Download*TWRP-oreo-smart.img*file
https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
Copy the downloaded* TWRP file to the*Minimal ADB and fastboot folder.
Enable OEM unlocking on your phone (developer options) and USB debugging mode.
Now launch MAF32.exe (or cmd-here) file from the Minimal ADB and fastboot folder, a command window will open up.
Turn off your phone and connect to your PC. Reboot to fastboot mode using button combination Power and Volume down.
In the command window, enter the following commands one by one
- fastboot devices - this command will verify connection in fastbot mode (you will see your serial number)
-fastboot flash recovery_ramdisk TWRP-oreo-smart.img
-fastboot reboot - the device will reboot
Now you can boot into TWRP mode using button combination Power and Volume Up or command*
adb reboot recovery
Download and copy to SD card latest Magisk.zip.
Boot your phone into TWRP,* in TWRP main menu tap 'Install', then navigate to the*Magisk.zip , tap it, then ‘Swipe to confirm Flash’.*
When the process is complete, tap Reboot System.
Enjoy !*
bozka1 said:
Only EMUI 8.x !!!
Your device must have an*unlocked bootloader.
Huawei HiSuite installed on your computer because it will install all the USB drivers
Download and install*Minimal ADB and fastboot Tool*on your computer. The folder location should be C:\Program Files(x86)\Minimal ADB and fastboot.
https://www.the***********.com/minimal-adb-and-fastboot-tool-for-windows/
Download*TWRP-oreo-smart.img*file
https://mega.nz/#!ot8TGIIa!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
Copy the downloaded* TWRP file to the*Minimal ADB and fastboot folder.
Enable OEM unlocking on your phone (developer options) and USB debugging mode.
Now launch MAF32.exe (or cmd-here) file from the Minimal ADB and fastboot folder, a command window will open up.
Turn off your phone and connect to your PC. Reboot to fastboot mode using button combination Power and Volume down.
In the command window, enter the following commands one by one
- fastboot devices - this command will verify connection in fastbot mode (you will see your serial number)
-fastboot flash recovery_ramdisk TWRP-oreo-smart.img
-fastboot reboot - the device will reboot
Now you can boot into TWRP mode using button combination Power and Volume Up or command*
adb reboot recovery
Download and copy to SD card latest Magisk.zip.
Boot your phone into TWRP,* in TWRP main menu tap 'Install', then navigate to the*Magisk.zip , tap it, then ‘Swipe to confirm Flash’.*
When the process is complete, tap Reboot System.
Enjoy !*
Click to expand...
Click to collapse
If I do this, I lost all apps and data or not?
davideakc said:
If I do this, I lost all apps and data or not?
Click to expand...
Click to collapse
No you won't, but you should always backup your data.
AztekSoul said:
No you won't, but you should always backup your data.
Click to expand...
Click to collapse
And after flashing that TWRP can I still install Huawei updates like security patches etc... even if I don't have stock recovery?
davideakc said:
And after flashing that TWRP can I still install Huawei updates like security patches etc... even if I don't have stock recovery?
Click to expand...
Click to collapse
Yes you can, although you have to download updates through firmware finder and update with HuRUpdater in twrp.
davideakc said:
And after flashing that TWRP can I still install Huawei updates like security patches etc... even if I don't have stock recovery?
Click to expand...
Click to collapse
Then there is another solution - install TWRP over eRecovery (my own experience) :
- copy to SD card TWRP-oreo-smart.img
- in main TWRP menu tap Install image, then navigate
to the TWRP-oreo-smart, select
eRecovery_ramdisk and confirm Flash . System
reboot.
- Download and copy to the Minimal ADB and fastboot folder RECOVERY_RAMDISK330.img
https://mega.nz/#!I511VK4b!9cGodiCORHOvXndOCHyqcezpHmUk2zeTslqpbZe8pk4
Connect your phone to PC in fastboot mode and install recovery_ramdisk using command
- fastboot flash recovery_ramdisk RECOVERY_RAMDISK330.img
- fastboot reboot
How to boot into TWRP: reboot your phone and press Volume Up key up to 3 seconds to enter TWRP.
bozka1 said:
Then there is another solution - install TWRP over eRecovery (my own experience) :
- copy to SD card TWRP-oreo-smart.img
- in main TWRP menu tap Install image, then navigate
to the TWRP-oreo-smart, select
eRecovery_ramdisk and confirm Flash . System
reboot.
- Download and copy to the Minimal ADB and fastboot folder RECOVERY_RAMDISK330.img
https://mega.nz/#!I511VK4b!9cGodiCORHOvXndOCHyqcezpHmUk2zeTslqpbZe8pk4
Connect your phone to PC in fastboot mode and install recovery_ramdisk using command
- fastboot flash recovery_ramdisk RECOVERY_RAMDISK330.img
- fastboot reboot
How to boot into TWRP: reboot your phone and press Volume Up key up to 3 seconds to enter TWRP.
Click to expand...
Click to collapse
After that, how can I restore factory eRecovery?
davideakc said:
After that, how can I restore factory eRecovery?
Click to expand...
Click to collapse
Okay, one can install Magisk without TWRP. There are plenty of guides on how to do these things in the Mate 10 forums. Of course, TWRP makes things easier ....
Hi all,
Since there is no TWRP for the MI A2 in Android Pie we can only use magisk to root.
The problem is that Xiaomi does not release the update zip and we can not patch the boot.img of the last security patch.
I have discovered a method to extract the boot img without root and then be able to patch it to have ROOT!
Nevermind, now TWRP supports PIE...
UNLOCKING THE BOOTLOADER:
Tap 7 times in build number for enable developer options
Enable OEM Unlock in developer options
Reboot the phone in fastboot:
Code:
adb reboot bootloader
Unlock the BL:
Code:
fastboot oem-unlock
Unlock critical flashing:
Code:
fastboot flashing unlock_critical
Reboot and wait for the phone boot up:
Code:
fastboot reboot
Now you have the bootloader unlocked!
INSTALLING TWRP AND MAGISK:
Download TWRP 3.3.0-0
Boot to the TWRP:
Code:
fastboot boot twrp-3.3.0-0-jasmine_sprout.img
It will ask for decryption password, click on cancel
Swipe for allow system modifications
Go to install and select the Magisk.zip
Install it and reboot
Wait for the phone boots up
Now install Magisk.apk
Enjoy root!
DOWNLOADS:
TWRP
MAGISK.APK
https://twrp.me/xiaomi/xiaomimia2.html
joaomiguelsm said:
https://twrp.me/xiaomi/xiaomimia2.html
Click to expand...
Click to collapse
Oh f*** I didn't see that TWRP...
Updated!
Rortiz2 said:
Oh f*** I didn't see that TWRP...
Updated!
Click to expand...
Click to collapse
would you help? i just flashed this twrp which worked fine but i'm not able to flash custom roms . or whenever i try to, it got failed with a massage "updater process ended with error 1".
your guidance would be helpful..thanks
Amnvlad said:
would you help? i just flashed this twrp which worked fine but i'm not able to flash custom roms . or whenever i try to, it got failed with a massage "updater process ended with error 1".
your guidance would be helpful..thanks
Click to expand...
Click to collapse
That's because the ROM's are only for Android Oreo.. Wait until anyone compile a ROM for Android pie.
Sent from my Mi A2 using Tapatalk
Where do we get Magisk.zip? From the website? Sorry been away from the rooting scene for a long time.
Also I'm guessing this only use TWRP temporarily?
how does one go about to keep the usual ota after unlocking and flashing magisk?
L.E. does the unlock wipe the data on the phone?
---------- Post added at 09:15 AM ---------- Previous post was at 09:14 AM ----------
[/COLOR]
Rortiz2 said:
That's because the ROM's are only for Android Oreo.. Wait until anyone compile a ROM for Android pie.
Sent from my Mi A2 using Tapatalk
Click to expand...
Click to collapse
Hi Terresa. Havoc OS, RR, Pixel roms, aren't they pie based roms ? I am getting the same error while flashing any ram using temp TWRP. I also tried going back to stock Orio and followed the same procedure still can't flash any roms . I followed every tutorial on MI A2 forums stil could not manage to install any rom
I can't install the TWRP when I reboot by holding down the volume + key with the "Fastboot reboot" command. The phone restarts normally
After flashing magisk i dont need to flash recovery?
Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
¿GJ?
¿GotJazz? said:
Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
¿GJ?
Click to expand...
Click to collapse
I'm having the same problem
¿GotJazz? said:
Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
¿GJ?
Click to expand...
Click to collapse
3.3.1.-1???...
cultofluna said:
3.3.1.-1???...
Click to expand...
Click to collapse
Affirmative. Fajita 3.3.1-1. See attached screenshot from TWRP.me. Should I be booting into a different version?
¿GotJazz? said:
Affirmative. Fajita 3.3.1-1. See attached screenshot from TWRP.me. Should I be booting into a different version?
Click to expand...
Click to collapse
Those "official" TWRP builds don't work properly on Android 10. Here is a link to the one you need:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
jp0469 said:
Those "official" TWRP builds don't work properly on Android 10. Here is a link to the one you need:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
Click to expand...
Click to collapse
Thanks, @jp0469! This helps a lot!
Just to be clear (and to get to a successful conclusion without a bricked phone), I won't be installing a TWRP installer ZIP file after booting into this TWRP image (The old style method), but instead installing the same TWRP IMG file as a "Recovery RAM Disk", correct?
¿GJ?
¿GotJazz? said:
Thanks, @jp0469! This helps a lot!
Just to be clear (and to get to a successful conclusion without a bricked phone), I won't be installing a TWRP installer ZIP file after booting into this TWRP image (The old style method), but instead installing the same TWRP IMG file as a "Recovery RAM Disk", correct?
¿GJ?
Click to expand...
Click to collapse
Need a little more info before you proceed.
I know you said that you're currently on Android 10.3.0
Are you rooted with Magisk? If not, are you planning on rooting?
jp0469 said:
Need a little more info before you proceed.
I know you said that you're currently on Android 10.3.0
Are you rooted with Magisk? If not, are you planning on rooting?
Click to expand...
Click to collapse
I was rooted with Magisk, but that got lost when I did the 10.3.0 update. Definitely planning on TWRPing and rooting again, as long as it's safe.
¿GotJazz? said:
I was rooted with Magisk, but that got lost when I did the 10.3.0 update. Definitely planning on TWRPing and rooting again, as long as it's safe.
Click to expand...
Click to collapse
Stick to good old ones...
Once booted in twrp via fastboot flash the installer zip. It has always worked and will always. Always latest version. And flash Magisk after.
¿GotJazz? said:
I was rooted with Magisk, but that got lost when I did the 10.3.0 update. Definitely planning on TWRPing and rooting again, as long as it's safe.
Click to expand...
Click to collapse
Put the latest Magisk zip and TWRP installer (zip file) on your phone's internal memory if you don't already have them there. Now you can fastboot boot the TWRP img file (Q version). Next flash the TWRP zip to permanently install TWRP into recovery. Reboot back to recovery to make sure it worked and then flash Magisk to re-gain root.
Reboot
Thanks, guys - The only reason I asked about the alternate "RAM Disk" method was because it was listed as the installation method by the developer on the link that @jp0469 provided earlier.
I'll try the old-fashioned method, since y'all say that it works OK.
I have a brand new hp windows 10 PC and a new op6t converted to international version. Running pie latest oxygen os. I need to get minimal adb fastboot installed so I can install twrp and root. Ik it's a little different process to get twrp on 6t but I need some help. Can someone provide me with the correct fastboot to install
[email protected] said:
I have a brand new hp windows 10 PC and a new op6t converted to international version. Running pie latest oxygen os. I need to get minimal adb fastboot installed so I can install twrp and root. Ik it's a little different process to get twrp on 6t but I need some help. Can someone provide me with the correct fastboot to install
Click to expand...
Click to collapse
I always install the latest directly from Google. There is a link on this page to the latest version of Windows ADB and Fastboot. Just unzip the file you download into a directory of your choice.
Everytime I try to boot twrp It says waiting on device. What's that mean
[email protected] said:
Everytime I try to boot twrp It says waiting on device. What's that mean
Click to expand...
Click to collapse
It mean you didn't install driver on your PC.
---------- Post added at 03:38 AM ---------- Previous post was at 03:35 AM ----------
¿GotJazz? said:
Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
¿GJ?
Click to expand...
Click to collapse
Type Command: fastboot flash boot
And Use TWRP 3.3.1.30 .
Hi - I am trying to reinstall TWRP on my OP6T after upgrading to OOS 10.3.0.
I am running Minimal ADB and Fastboot v1.4.3 on my Win10 PC. I have connected my phone to my PC, and entered Fastboot mode. The OP6T is detected when I do a fastboot devices command.
Next, I try doing a temporary Recovery Mode boot into TWRP with a fastboot boot twrp-3.3.1-1-fajita.img command. This is where I run into a problem ... While the Minimal ADB and Fastboot window says that the TWRP image was sent to the OP6T, I am still stuck on the Fastboot screen, and the phone is locked up and doesn't reboot the image.
What is going wrong?
Click to expand...
Click to collapse
same thing happened to me, but my screen went black and i cant seem to turn it back on again. what a day. fml
i really need help, i only have that one phone for daily usage. arghhhh
uncleheng said:
same thing happened to me, but my screen went black and i cant seem to turn it back on again. what a day. fml
i really need help, i only have that one phone for daily usage. arghhhh
Click to expand...
Click to collapse
press volume down,up and power button same time for 10sec your phone will boot to bootloader mode.
After doing the fastboot boot twrp-3.3.1-30-fajita-Q-mauronofrio.img in Fastboot Mode, I installed twrp-3.3.1-30-fajita-installer-mauronofrio.zip in the booted TWRP Recovery Mode, and everything is working fine again.
Thanks, guys!
Hey I am running Android 10.3.7 and am having the same problem, I tried unofficial twrp linked abouve and still stuck on fastboot screen, I think I'm using abd 1.43, if twrp doesn't work is there an alternative? I'm newish to rooting I've rooted other phones but that was back in the good old days where it wasn't complicated. I am running a T-Mobile phone converted to international with bootloader unlocked
Hello all...
Just a quick question as I am reading and seeing so many different answers. I have the UNLOCKED US version OnePlus 8 Pro (IN2025) Which is currently running Oxygen OS 11.IN11AA (Android 11 Official). I have successfully unlocked the bootloader and am ready to root with Magisk. I am at a loss because I dont know which Magisk to use or how to properly flash it. I have Magisk Manager 8.0.2 and have Magisk version 21.0
I have also downloaded the patched boot image from here... https://forum.xda-developers.com/oneplus-8-pro/how-to/root-patched-boot-img-android-11-op8-t4174919
What am I doing wrong? Can someone please just give me a quick rundown... I am not new to rooting just haven't done in in over a year. Thank you!
Don't think your doing anything wrong, just need to get that image on your pc, and fastboot flash it to both a/b slots then reboot your phone and you should have root available
adb reboot bootloader
fastboot boot (name of image).img - Try this one first as it just allows you to see if the phone boots up fine, if it does reboot back into the bootloader and then do the following...
fastboot flash boot_a (name of image).img
fastboot flash boot_b (name of image).img
fastboot reboot
How do I get Magisk 21.0 to install through Magisk Manager?
You don't, that's why you've downloaded a patched img, that has been patched with magisk already, just need to flash it accordingly
CraigHardy said:
You don't, that's why you've downloaded a patched img, that has been patched with magisk already, just need to flash it accordingly
Click to expand...
Click to collapse
This is what I am getting after following your directions to a T!
I also flashed to both partitions. Please see attachments. I sent 2 screenshots.
You don't do the install from magisk, have to copy the patched img to a pc where you have adb/fastboot installed then install from command prompt
CraigHardy said:
You don't do the install from magisk, have to copy the patched img to a pc where you have adb/fastboot installed then install from command prompt
Click to expand...
Click to collapse
I did not do the install through Magisk Manager I did the install via adb and fastboot in fastboot mode. It Said flash successful. But when I go into Magisk Manager after rebooting, nothing changes.
Doesn't work. Download the patched image, put it on the phone, use magisk canary manager to patch it again, transfer it off your phone, then boot into Fastboot and flash it.
It has to be patched in the phone it will be installed to otherwise it will not work.
akinkoff85 said:
I did not do the install through Magisk Manager I did the install via adb and fastboot in fastboot mode. It Said flash successful. But when I go into Magisk Manager after rebooting, nothing changes.
Click to expand...
Click to collapse
Use the beta magisk.
Re-patch it in your newly updated magisk manager then flash to both slots..
Also verify the size of the file prior to flashing.. Mine was 96MB
Here is the exact size.
Problem uploading image
I am a little confused now... I uninstalled root for a few days and now have the second release of android 11... I am in fastboot mode doing fastboot flash boot... then the file name and all it says is waiting for device?? Any help??
dladz said:
Use the beta magisk.
Re-patch it in your newly updated magisk manager then flash to both slots..
Also verify the size of the file prior to flashing.. Mine was 96MB
Click to expand...
Click to collapse
Indeed, using the beta version worked for me! Thanks for the tip!
imval said:
Indeed, using the beta version worked for me! Thanks for the tip!
Click to expand...
Click to collapse
No worries man, glad you're sorted
CraigHardy said:
Don't think your doing anything wrong, just need to get that image on your pc, and fastboot flash it to both a/b slots then reboot your phone and you should have root available
adb reboot bootloader
fastboot boot (name of image).img - Try this one first as it just allows you to see if the phone boots up fine, if it does reboot back into the bootloader and then do the following...
fastboot flash boot_a (name of image).img
fastboot flash boot_b (name of image).img
fastboot reboot
Click to expand...
Click to collapse
What is the explanation as to why one needs to fastboot flash Magisk to both slots instead of using the following command:
adb reboot bootloader
fastboot getvar current-slot
*in my case Slot B*
fastboot flash boot_b magisk_patched.img
fastboot reboot
rodken said:
What is the explanation as to why one needs to fastboot flash Magisk to both slots instead of using the following command:
adb reboot bootloader
fastboot getvar current-slot
*in my case Slot B*
fastboot flash boot_b magisk_patched.img
fastboot reboot
Click to expand...
Click to collapse
You can, however flashing to both slots is seemingly easier.
Personally I wouldn't flash at all.
Just boot to avoid the possibility of a bad boot.
akinkoff85 said:
Hello all...
Just a quick question as I am reading and seeing so many different answers. I have the UNLOCKED US version OnePlus 8 Pro (IN2025) Which is currently running Oxygen OS 11.IN11AA (Android 11 Official). I have successfully unlocked the bootloader and am ready to root with Magisk. I am at a loss because I dont know which Magisk to use or how to properly flash it. I have Magisk Manager 8.0.2 and have Magisk version 21.0
I have also downloaded the patched boot image from here... https://forum.xda-developers.com/oneplus-8-pro/how-to/root-patched-boot-img-android-11-op8-t4174919
What am I doing wrong? Can someone please just give me a quick rundown... I am not new to rooting just haven't done in in over a year. Thank you!
Click to expand...
Click to collapse
Watch this video it helped me out allot
dladz said:
You can, however flashing to both slots is seemingly easier.
Personally I wouldn't flash at all.
Just boot to avoid the possibility of a bad boot.
Click to expand...
Click to collapse
I did not know that one can just boot a magisk_patched.img instead of flashing.
rodken said:
I did not know that one can just boot a magisk_patched.img instead of flashing.
Click to expand...
Click to collapse
It's preferable.
There are some things to note.
1st. You are only booting it, meaning if you reboot; you will start using the installed / flashed image and the booted image will be lost.
2nd. For the above reason. If you want to make root permanent you have to open magisk after opening and then click install - install directly.
As magisk will already have root access, it will be able to accomplish patching, if you tried this whilst unrooted it would fail, or not be an option.
3rd. By booting you avoid the potential bootloop problems you can and almost will have at some point if you always flash, bad images are pretty rife for a number of reasons.
I've got a large guide for rooting in the guides section which covers all the bases and their shortcomings /benefits.