Hi,
Is it possible to install TWRP v3.0.0.0 on a LG Nexus 5 HAMMERHEAD v6.0.1 (MMB29Q) without rooting? Not that it's something I absolutely need to do but by browsing through different sites and tutorials, it seems possible although my own tests prove the contrary...
Firstly, on TWRP official website, it's written that you can:
Fastboot Install Method (No Root Required):
You will need the platform-tools from the Android SDK on your computer. Find the SDK Only section on the page linked and install the SDK and download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on your computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
adb reboot bootloader
You should now be in fastboot mode. Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
fastboot flash recovery twrp.img
fastboot reboot
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
I tried this method but it didn't work at all:
After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP.
Click to expand...
Click to collapse
Even I booted directly to TWRP recovery mode after I manually flashed it, it obviously didn't patched the stock ROM since after I later booted the phone normally in Android system and rebooted in recovery mode, the stock recovery mode was back, no TWRP!
Secondly, when I used Nexus Root Toolkit (NRT) v2.1.4, I had no choice but to root if I wanted to flash the custom recovery (TWRP). I successfully rooted and installed TWRP permanently using the tool.
Therefore, is installing TWRP without rooting some kind of myth that maybe worked with previous Android build and TWRP versions or is there actually really a way to do so?
I just did it yesterday on the March patch but had to flash twrp twice. The first time it bypassed recovery and booted into the os. After booting back into the bootloader and flashing twrp again it did boot into twrp.
Sent from my Nexus 5X using XDA Free mobile app
To install TWRP, the phone needs to have an unlocked bootloader, not root.
You can flash TWRP using fastboot commands. After flashing TWRP in fastboot, use the volume and power button to boot directly into recovery.
Hi,
Yesterday my WileyFox Spark+ came in, which is still equipped with COS13.0.1, based on Android 6.0.1.
When I tried rooting the phone, I got stuck at the point of using TWRP for flashing SuperSU.zip.
Until then, I had succesfully followed the following process:
-Enabled 'OEM Bootloader allowed to be unlocked' in Developer Options
-Installed USB drivers and such on PC
-Enabled USB debugging, apps from unknown sources, ADB install unsigned apps allowed etc.
-Unlocked bootloader like this in CMD:
fastboot devices (my phone showed up)
fastboot flashing unlock
I pressed volume up button (yes)
I selected boot mode fastboot
-Flashed TWRP Recovery to phone like this in CMD:
fastboot flash recovery twrp3100.img
-I booted into TWRP recovery
A lot of folders and some files were present there, but almost all folders were 'empty'. I couldn't reach my SC-Card with SuperSU.zip on it.
TWRP even said no OS was installed when I wanted to reboot to retry.
I was confused for a while, only to discover the OS was still there after booting into System.
I tried to flash SuperSU from ADB, but that also didn't work. I issued the following commands in CMD:
adb reboot recovery
(ticked adb sideload in TWRP +wipe dalvik & cache)
adb sideload supersu279.zip
TWRP said it executed succesfully, but failed to access /data and /cache.
It was at this point that I discovered the phone was encrypted already from the box. I had never considered this as an option.
It's weird though, because I have heard that flashing SuperSU from ADB should work even with an encrypted phone.
Now the interwebs and WileyFox themselves say Encryption is disabled when you factory reset the phone. So I did that, but it just booted into TWRP with the same circumstances.
Few folders, almost all empty. SD-card not visible.
I tried sideloading SuperSU again, but without result.
Any idea how i should progress further? 'Cause I have run out of ideas..
Is it possible to flash SuperSU via fastboot or anything?
I have found a LineageOS 13 ROM for my phone, but it's a .zip so I don't think I can use it.
Anyway, any help would be greatly appreciated!
Cheers.
NB: I don't care about encryption, i'd rather have it gone, but whatever option is best for rooting this thing will work fine for me.
Hi all,
I just updated to the latest beta with Android Q, everything is fine except one thing. I successfully re-enabled Magisk with a patched boot image, and all was fine.
However when I flashed a module (despite it saying it was compatible with Q), my phone desicided not to boot anymore.
If I fastboot flash the unpatched boot image, of course it works, but I don't have root access anymore.
If I re-flash the patched boot image, it stays stuck to the boot animation.
Since I'm on Q, I have no TWRP recovery, so impossible to flash the magisk uninstaller zip.
What could I try ?
My options are now either to erase data and start fresh, which is a lot of trouble for such a small problem, or to wait for a TWRP release.
Any other suggestion would be very welcome
Thanks!
Edit: Managed to solve it. Little how-to, in case someone else has the issue :
On the PC, relaunch your adb daemon in root mode by typing
Code:
adb kill-server
and then
Code:
adb root
Now reboot your phone into Fastboot and plug it in the PC
Flash the patched boot image by typing
Code:
fastboot flash boot oos_10_ob1_patched_boot.img
and start the phone
While it's attempting to boot (it is stuck on the animation because of the problematic module), type
Code:
adb shell
then in the shell, type
Code:
magisk --remove-modules
The phone should reboot, and complete this boot sequence normally. You can then go into Magisk Manager and reflash magisk (direct install) and start over
Thanks for this. Keeping this as reference. I believe this works only if you've enabled USB Debugging in your phone and granted it access to your PC, right?
Is there a way to get patched boot img with twrp? I cant install twrp because of the fastboot unknown command thing.
Dolenutsi said:
I got it working! Here are the steps.
-I downloaded the mauronofrio twrp img, mauronofrio twrp installer zip and OOS10 from oxygen updater
-fastboot flash boot *filename*.img
-reboot to recovery
-dirty flash the OOS10 package
-flash the mauronofrio twrp installer
-Working!
Click to expand...
Click to collapse
Update rom and active debug usb on developer options.
Can't flash twrp even after usb debugging is on.
AndryOut said:
Update rom and active debug usb on developer options.
Click to expand...
Click to collapse
I have latest update and i tried everything including downgrading and can't boot twrp image
I had the same problem, I looked at many guides but without results. So I tried my own way. I installed a previous version of the operating system but the problem persisted. The only way is to install a previous version, do the official update from the phone (this enables the fastboot), enable usb debugging and start the bootloader from the advanced reboot of the phone without disconnecting the cable from the PC. This worked for me.
AndryOut said:
I had the same problem, I looked at many guides but without results. So I tried my own way. I installed a previous version of the operating system but the problem persisted. The only way is to install a previous version, do the official update from the phone (this enables the fastboot), enable usb debugging and start the bootloader from the advanced reboot of the phone without disconnecting the cable from the PC. This worked for me.
Click to expand...
Click to collapse
Which version did you install? Did you update it to OOS 10 or some earlier version?
AndryOut said:
I had the same problem, I looked at many guides but without results. So I tried my own way. I installed a previous version of the operating system but the problem persisted. The only way is to install a previous version, do the official update from the phone (this enables the fastboot), enable usb debugging and start the bootloader from the advanced reboot of the phone without disconnecting the cable from the PC. This worked for me.
Click to expand...
Click to collapse
Any one is fine, the important thing is that you update to the latest version from the phone. (remember that you cannot install a package downloaded from the official website, because it uses a different installation engine, you must download the stock package otherwise it will go into bootloop or it will turn on but it will not read the internal memory.)
@AndryOut
@Dolenutsi
@sahadrafiq
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
I have updated from the phone to the latest version, I've debug USB on, but I cant run twrp from fastboot.
Any clues?
davidebeatrice said:
I have updated from the phone to the latest version, I've debug USB on, but I cant run twrp from fastboot.
Any clues?
Click to expand...
Click to collapse
What command do you use? I used "fastboot boot namefile.Img". If you use the "adb devices" command on windows will it show you your phone?
I got it working! Here are the steps.
-I downloaded the mauronofrio twrp img, mauronofrio twrp installer zip and OOS10 from oxygen updater
-fastboot flash boot *filename*.img
-reboot to recovery
-dirty flash the OOS10 package
-flash the mauronofrio twrp installer
-Working!
My phone. - Galaxy A51, One UI Version is 4.1, Android version is 12, Product Name – SM-A515F.
Stock ROM up to date.
I can boot into download mode, +/- volume, connect to pc. Works just fine.
But + volume & power boots into safe mode; - volume & power boots into safe mode; +/- volume & power boots into safe mode; +/- volume only boots into safe mode. I have ran out of button sequences to try.
What is wrong with my phone, is it impossoble to boot into recovery mode on my model of phone. This is why I cannot install TWRP as when I install via Odin, it will not boot into recovery post installation.
I am stumped.
Hello!
What is about phone: is it bootlooping or is it in downloading mode?
Other question: from what source did you download the twrp.tar file?
You should be able to force a reboot to recovery using ADB. Enable developer options, then enable USB Debugging. Download the SDK Platform Tools and open a command line in the platform tools directory (where you find the fastboot, adb, etc programs)
First, type adb devices. ADB will then start the ADB daemon.
Next, connect your device via USB cable while unlocked. You should get a prompt on the device screen requesting USB debugging authorization. Go ahead and grant it.
Then, type adb devices again. If you authorized USB debugging correctly, you should see your device listed.
Now, type adb reboot recovery. Your device should reboot into TWRP.
V0latyle said:
You should be able to force a reboot to recovery using ADB. Enable developer options, then enable USB Debugging. Download the SDK Platform Tools and open a command line in the platform tools directory (where you find the fastboot, adb, etc programs)
First, type adb devices. ADB will then start the ADB daemon.
Next, connect your device via USB cable while unlocked. You should get a prompt on the device screen requesting USB debugging authorization. Go ahead and grant it.
Then, type adb devices again. If you authorized USB debugging correctly, you should see your device listed.
Now, type adb reboot recovery. Your device should reboot into TWRP.
Click to expand...
Click to collapse
Guy, to complete the TWRP installation, it is needed to flash Disable_Dm-Verity_ForceEncrypt from TWRP, otherwise the device will not boot properly
vmirrimv said:
Other question: from what source did you download the twrp.tar file?
Click to expand...
Click to collapse
It's in Stock now. But it was stuck in a bootloop, but could boot into download mode. These are the recovery's which all installed but I could not boot into. I cannot boot into recovery now I am in Stock. It's as if there is no recovery option for my A51.
Twrp+vbmeta_A11.tar,
TWRP-11-3.6.0-a51-20220210-1636.tar,
TWRP-11-3.6.1-a51-20220228-2050.tar,
TWRP-11-3.6.1-a51-20220321-1406-hotfix.tar,
TWRP-11-3.6.2-a51-20220602-0515.tar,
twrp-a51-3.5.0_10-1_ianmacd.tar
vmirrimv said:
Guy, to complete the TWRP installation, it is needed to flash Disable_Dm-Verity_ForceEncrypt from TWRP, otherwise the device will not boot properly
Click to expand...
Click to collapse
I was stuck in a bootloop and could not boot into TWRP..
Unless there is a way to flash Disable_Dm-Verity_ForceEncrypt in downlad mode using Odin?
V0latyle said:
You should be able to force a reboot to recovery using ADB. Enable developer options, then enable USB Debugging. Download the SDK Platform Tools and open a command line in the platform tools directory (where you find the fastboot, adb, etc programs)
First, type adb devices. ADB will then start the ADB daemon.
Next, connect your device via USB cable while unlocked. You should get a prompt on the device screen requesting USB debugging authorization. Go ahead and grant it.
Then, type adb devices again. If you authorized USB debugging correctly, you should see your device listed.
Now, type adb reboot recovery. Your device should reboot into TWRP.
Click to expand...
Click to collapse
Hi I am back in stock now, so no TWRP installed. Would this method boot you into Stock recovery?
Do I need to be in download mode or just normal mode when connecting the phone to the pc?
Hello, can you say what version of Android your phone on?
If it is on 12th, then I would say, that the problem is, that this version may not fully supported for TWRP working
Because as I tried, there was a fail in the procces.
Sorry, i did not see that you have already written about it
Yep, think I will have to download Android 10 stock rom; and hopefully be able to install 10 via Odin from 12 back to 10.
Sign1 said:
Hi I am back in stock now, so no TWRP installed. Would this method boot you into Stock recovery?
Do I need to be in download mode or just normal mode when connecting the phone to the pc?
Click to expand...
Click to collapse
ADB commands must be issued in system. The alternative would be from fastboot but it doesn't seem you can access that.
Try flashing TWRP again, but immediately hold Volume Up during boot to force booting into TWRP. Newer Samsung firmware does seem to have some sort of security measure that will replace a custom recovery, so you'll have to flash the Multidisabler to disable stock recovery auto-restoration.
Sign1 said:
Yep, think I will have to download Android 10 stock rom; and hopefully be able to install 10 via Odin from 12 back to 10.
Click to expand...
Click to collapse
I do not want to mislead you, but you will not be able to roll back from Android 12 to Android 10, because the current binary version of your phone (5) cannot be changed to lower one (4).
Maximum as you can do, is to downgrade to the 11th version and there, as I think and tried, the Twrp+vbmeta_A11.tar recovery file will be flashed sucessfuly and you will be able to enter TWRP without issues like bootloop.
Other problems are, as I think, that you may forgot to enable USB Debugging on your phone and authorize it with your computer, you may forgot to set the default USB Configuration as data transfer (MTP), or even you may not unlocked the bootloader.
I think they are the reasons because of which you could not enter TWRP, because, as I have tried to flash One UI 4.1 Android 12 according to this thread recently: https://forum.xda-developers.com/t/...ecovery-project-v3-6-2-android-11-12.4400869/
everything has been sucessful, both flashing and entering and following rebooting to Stock system.
Or you may even not removed the check mark from the parameter "Auto Reboot" in Odin
vmirrimv said:
I do not want to mislead you, but you will not be able to roll back from Android 12 to Android 10, because the current binary version of your phone (5) cannot be changed to lower one (4).
Maximum as you can do, is to downgrade to the 11th version and there, as I think and tried, the Twrp+vbmeta_A11.tar recovery file will be flashed sucessfuly and you will be able to enter TWRP without issues like bootloop.
Click to expand...
Click to collapse
Cheers for that, just downloaded Android 10, took me twelve hours to download, so its no use to me. I need to download Android 11.
vmirrimv said:
Or you may even not removed the check mark from the parameter "Auto Reboot" in Odin
Click to expand...
Click to collapse
Yep did that.