I have tried a number of times to install TWRP (unrooted) on my Nexus 6. I am following the instructions from here
https://twrp.me/devices/motorolanexus6.html
I am noting the warnings here
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.
Once I issue the fastboot reboot command before the Nexus 6 shows anything on the display I press power and vol down and get into TWRP. It seems to what it's supposed to do (presumably patch the stock ROM) and then I reboot to Android.
But the next time I boot to recovery I end up with stock recovery again. I have tried this a number of times and while I can get TWRP installed it always reverts to stock recovery after the next restart.
Is there something else I have missed here in the instructions? They seem fairly clear.
Not that I think it matters but I am running 7.1.1 (flashed with the OTA image since I was not getting OTA updates)
Thanks
Instead of using the fastboot command to reboot to recovery after you have flashed TWRP do it manually. Been a while but I believe that should work.
Dont use the fastboot reboot command, use the volume keys to enter twrp recovery after flashing twrp in fastboot mode
Once you are in twrp swipe to allow changes and if needed change twrp settings, after that reboot into rom.
TMG1961 said:
Dont use the fastboot reboot command, use the volume keys to enter twrp recovery after flashing twrp in fastboot mode
Once you are in twrp swipe to allow changes and if needed change twrp settings, after that reboot into rom.
Click to expand...
Click to collapse
I have done that several times. This is the screen I see when TWRP is loading for the first time.
Not sure if those red messages are fatal or not
When I am in TWRP I can reboot to recovery and it gets back to TWRP but if I reboot to system and then try to enter TWRP on a reboot (holding power and volume up/down it boots into the Fastboot and when I choose Recovery mode I send up with stock recovery again.
Am running 7.1.1 myself and flashed the latest TWRP 3.1.1-0
Were did you download the twrp img from? I download mine from https://dl.twrp.me/shamu/ Once i downloaaded it i rename it to recovery.img
I use cmd on laptop andhook up the phone, then run adb reboot bootloader followed by fastboot flash recovery recovery.img, then i use the volume keys to get into twrp, swipe to allow changes and make changes to settings. Then reboot into rom.
TMG1961 said:
Am running 7.1.1 myself and flashed the latest TWRP 3.1.1-0
Were did you download the twrp img from? I download mine from https://dl.twrp.me/shamu/ Once i downloaaded it i rename it to recovery.img
I use cmd on laptop andhook up the phone, then run adb reboot bootloader followed by fastboot flash recovery recovery.img, then i use the volume keys to get into twrp, swipe to allow changes and make changes to settings. Then reboot into rom.
Click to expand...
Click to collapse
That is pretty much what I have been doing. The only difference is, the first time I did this (before I realised it wasn't working), I rebooted from adb and I did see the swipe to allow changes. But since then if I boot from abd or boot from the bootloader, I don't see the TWRP option to swipe to allow changes anymore.
I wonder if it's because the data is encrypted (standard on a N6?)
I checked the box to not show the swipe to allow modification. I have never decrypted my phone and twrp sticks. So not sure why yours isnt sticking.
TMG1961 said:
I checked the box to not show the swipe to allow modification. I have never decrypted my phone and twrp sticks. So not sure why yours isnt sticking.
Click to expand...
Click to collapse
Well the first time I did it I saw that message about allow modification and I agreed. Never seen it again.
The point of installing TWRP was to install a custom ROM. I wonder if I load the ROM image into the phone first, install TWRP and get into the first time, which I can, then install the ROM would that work?
lchiu7 said:
Well the first time I did it I saw that message about allow modification and I agreed. Never seen it again.
The point of installing TWRP was to install a custom ROM. I wonder if I load the ROM image into the phone first, install TWRP and get into the first time, which I can, then install the ROM would that work?
Click to expand...
Click to collapse
After using fastboot to flash TWRP, use the volume and power buttons to boot into TWRP, and allow modifications, then make a backup and reboot system. Go back to recovery and if all is well, then flash your ROM. Make sure you've got your TWRP issue fixed first though.
The same thing keeps happening to me. I can't seem to make twrp stick. I'd really appreciate some help.
Depending on what your doing, typically you have to manually boot into recovery after flashing twrp (from fastboot), don't use fastboot reboot xxxx. Use the power/volume key combo to reboot. Then accept either system modification or flash a systemless root solution. This will enable custom recovery to "stick". Otherwise, stock android will overwrite recovery on boot.
The TWRP thread has discussions about this. Starting at post 1044 should help.
mrcreativity said:
The same thing keeps happening to me. I can't seem to make twrp stick. I'd really appreciate some help.
Click to expand...
Click to collapse
Is your device encrypted before you flash TWRP?
Yes it is encrypted.
Anyway, I tried all the various methods and combinations but ended up going back to stock recovery. What worked was flashing SU after TWRP.
I'm running pure nexus now and enjoying it.
Related
Not really sure what I'm doing wrong. Last rooted phone was a Nexus 5, and that was of course painless to root and flash ROMs to...
I'm using a Verizon XT1096 with 5.1 on T-Mobile.
So I was able to get the bootloader unlocked via Motorola's website, now that Verizon is allowing them to do so. No problems there. My problem now is that I can flash a recovery, but if it reboots, the recovery is gone. And I can't get any recoveries to flash anything. I can't push an apk, root zip, or even a ROM. Says Installation Aborted, with no other error codes. Even tried CWM and disabling Signature Checking, which gives me more info, saying that the footer is mismatched. Phone does say the bootloader is unlocked though so that shouldn't be it...
Honestly, I'd just like to get it on CM12 until I can get a Nexus 6P.. Can anyone tell me if I'm doing something wrong? Or is there just no way to root yet? I figured even the XT1095 CF-Auto-Root method would work for 5.1, but no dice..
Not sure what to do here. Please move my thread if need be. Don't post here much...
I followed the instructions on the TWRP website (link below) and it worked flawlessly. One thing you have to do is, after running the "fastboot flash recovery twrp.img" command, make sure to manually scroll on the phone and reboot into recovery. Hope that helps...
https://twrp.me/devices/motorolamotox2014.html
There is a partition mismatch. So do this. Download supersu and place it in the phones memory. Boot to fastboot mode and then fastboot boot recovery.img rather than fastboot flash recovery.img. You will boot to twrp, install SuperSU then download twrp from the playstore and install thru the app. It works, that's how I did it. Also when booting to recovery from the fastboot menu choose recovery with the vol up key rather than power button.
RepeatUntilTheEnd said:
I followed the instructions on the TWRP website (link below) and it worked flawlessly. One thing you have to do is, after running the "fastboot flash recovery twrp.img" command, make sure to manually scroll on the phone and reboot into recovery. Hope that helps...
https://twrp.me/devices/motorolamotox2014.html
Click to expand...
Click to collapse
I thought I tried that but maybe not. I've read that some stock ROMs can and will overwrite the recovery upon booting, but I could be wrong. I'll look at that when I get home tonight.
oraixearl said:
There is a partition mismatch. So do this. Download supersu and place it in the phones memory. Boot to fastboot mode and then fastboot boot recovery.img rather than fastboot flash recovery.img. You will boot to twrp, install SuperSU then download twrp from the playstore and install thru the app. It works, that's how I did it. Also when booting to recovery from the fastboot menu choose recovery with the vol up key rather than power button.
Click to expand...
Click to collapse
Thank you, I'll try this tonight when I get home. This may solve it. I think I remember the bootloader spitting something out about a partition mismatch.. Will report back as soon as I try it.
So I went ahead and tried both your guys' methods.
Oraixearl, I figured your solution would work, but it actually didn't, to my surprise. It returned no results, as the root zip didn't end up doing anything.
RepeatUntilTheEnd's solution worked here. I guess I didn't try rebooting the phone after flashing the recovery, before going into it..
So here's what I did.
1.) Boot into bootloader
2.) Fastboot flash recovery [recovery.img]
3.) adb reboot bootloader
4.) Used keys on phone to go into recovery,
5.) Flashed root.zip
6.) Booted into OS, and ran root checker. Worked.
7.) To my surprise, TWRP stuck around, too.
Thank you guys!
TsarProdigy said:
So I went ahead and tried both your guys' methods.
Oraixearl, I figured your solution would work, but it actually didn't, to my surprise. It returned no results, as the root zip didn't end up doing anything.
RepeatUntilTheEnd's solution worked here. I guess I didn't try rebooting the phone after flashing the recovery, before going into it..
So here's what I did.
1.) Boot into bootloader
2.) Fastboot flash recovery [recovery.img]
3.) adb reboot bootloader
4.) Used keys on phone to go into recovery,
5.) Flashed root.zip
6.) Booted into OS, and ran root checker. Worked.
7.) To my surprise, TWRP stuck around, too.
Thank you guys!
Click to expand...
Click to collapse
Strange as it worked for me. I'm glad you got it sorted out tho. Cheers.
Hi,
Due to an unsuccessful decryption during the boot process, I had to format data.
I pushed a custom ROM to my phone and flashed it from TWRP.
I can't reboot to Android now. Each time I try to reboot I go back to TWRP...
How to solve it?
Thanks.
@mad-murdock @nvertigo67 could you help guys?
Same issue
---------- Post added at 10:08 AM ---------- Previous post was at 09:58 AM ----------
try this
n your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Reboot your device into fastboot mode. To do this, select reboot from the power menu and hold the [Volume Up] + [Power] buttons while your device reboots or boots from power off.
Once you're in fastboot mode, you need to unlock your bootloader. To do this, run the command:
fastboot oem unlock
WARNING: Unlocking your bootloader will erase all userdata on the device! Your device will be completely reset to factory defaults!
Once your bootloader is unlocked, you're ready to flash TWRP. To do this, run the command (replacing twrp.img with the actual image name):
fastboot flash recovery twrp.img
Once the image is flashed, you should use your volume keys to navigate to RECOVERY and the press the power key to select it.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If your device asks for a password to mount internal storage, and your password doesn't work or you haven't set one, see below under known issues for a fix!
If you want to be rooted with SuperSU:
Download the latest SuperSU Stable by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
---or (not both) ---
If you want to be rooted with something else or just want a bootable system:
Download the latest dm-verity and forced encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
This will also allow you to use [Format Data] to completely disable your encryption if desired.
Go to [Reboot] -> [System].
This is the TWRP thread... How can it help in my situation?
I flashed the dm-verity and forced encryption disabler zip, wiped all data and a custom rom. It doesn't help.
Primokorn said:
Hi,
Due to an unsuccessful decryption during the boot process, I had to format data.
I pushed a custom ROM to my phone and flashed it from TWRP.
I can't reboot to Android now. Each time I try to reboot I go back to TWRP...
How to solve it?
Thanks.
@mad-murdock @nvertigo67 could you help guys?
Click to expand...
Click to collapse
In twrp: Advanced->Terminal
In Terminal type wipe_misc and press enter. Reboot to system.
EDIT: this erases misc partition by dding /dev/zero to misc partition. (I've tested both, wipe_misc sceipt as well as dd by hand - it's safe; you will not loose anything [if there would be something on data... SCNR ])
---------- Post added at 19:18 ---------- Previous post was at 19:14 ----------
networx2002 said:
Same issue
[...]
Go to [Reboot] -> [System].
Click to expand...
Click to collapse
Very true, but that answers not his question...
nvertigo67 said:
In twrp: Advanced->Terminal
In Terminal type wipe_misc and press enter. Reboot to system.
Click to expand...
Click to collapse
Already tried. Is there something else to do after entering this command? (wipe data, flash rom again..)
EDIT: flashing the stock recovery and full 4.0.2 OTA might help?
Primokorn said:
Already tried. Is there something else to do after entering this command? (wipe data, flash rom again..)
EDIT: flashing the stock recovery and full 4.0.2 OTA might help?
Click to expand...
Click to collapse
Stay on twrp (3.0.3-1). Wipe art, system, data and cache. Flash full 4.0.2. Go to twrphome->mount and check if system is unmounted (*)- if so: boot to system; if system is mounted reboot to recovery and dirty flash (without any wipe) full 4.0.2 again; boot to system.
Whenever I had this boot to recovery but not to system, wipe_misc was allways sufficient.
BTW: disconnect usb before rebooting. otg-sticks as well charger result sometimes in unpredictable reboot behavior.
(*) I've still not found what's triggering this, but if after flashing system is mounted, you can't boot directly into system, and twrp tells you on reboot, that no system is installed, even if you just flashed a rom...
Primokorn said:
Hi,
Due to an unsuccessful decryption during the boot process, I had to format data.
I pushed a custom ROM to my phone and flashed it from TWRP.
I can't reboot to Android now. Each time I try to reboot I go back to TWRP...
How to solve it?
Thanks.
@mad-murdock @nvertigo67 could you help guys?
Click to expand...
Click to collapse
I ran into a similar problem with mine yesterday / today with 3.0.4-0....after countless tests, it came down to holding down the power button for 20s and releasing (hard shut down)...wait 20s, hold power for it to come back on, ROM loaded up.
I tried every boot option from TWRP, and just kept looping.
Give this a try, as trivial as it seems, fixed it for me.
stephlal said:
I ran into a similar problem with mine yesterday / today with 3.0.4-0....after countless tests, it came down to holding down the power button for 20s and releasing (hard shut down)...wait 20s, hold power for it to come back on, ROM loaded up.
I tried every boot option from TWRP, and just kept looping.
Give this a try, as trivial as it seems, fixed it for me.
Click to expand...
Click to collapse
How could it be possible?
It works! Thanks for your help.
I've flashed Tesla ROM and the phone boots. I'm charging my phone to enable encryption then I'll see how to set a boot password (without any issues this time lol).
I set a password to encrypt my data and flashed TWRP 3.0.1-0 again.
I'm not able to decrypt my data in TWRP...
After a reboot, the ROM doesn't recognize my password anymore. I'm fed up with encryption!
Primokorn said:
I set a password to encrypt my data and flashed TWRP 3.0.1-0 again.
I'm not able to decrypt my data in TWRP...
After a reboot, the ROM doesn't recognize my password anymore. I'm fed up with encryption!
Click to expand...
Click to collapse
imo just the unbrick tool to go back to fully stock and start the whole process again
I had this issue with the password.
I had to flash the stock recovery, go into stock recovery, it will ask you for the password, just choose forgot password and it will prompt to format everything. Click yes to accept. After it formats, flash the custom twrp recovery. Once it flashes, load recovery and flash the 3.5.4 bootloader here:
https://forum.xda-developers.com/showpost.php?p=70393513&postcount=72
OR you can boot into bootloader/fastboot and type in these commands:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
m0d hipp¥ said:
I had this issue with the password.
I had to flash the stock recovery, go into stock recovery, it will ask you for the password, just choose forgot password and it will prompt to format everything. Click yes to accept. After it formats, flash the custom twrp recovery. Once it flashes, load recovery and flash the 3.5.4 bootloader here:
https://forum.xda-developers.com/showpost.php?p=70393513&postcount=72
OR you can boot into bootloader/fastboot and type in these commands:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
Click to expand...
Click to collapse
Thanks but I'll just enjoy my phone for now. Encryption can wait.
Only these two fastboot commands will avoid the wrong password issue? It seems to be helpful to remove the dm-verity error and I don't have it.
Sorry I guess I misinterpreted the issue. I thought that the dm-verity and the encryption issue were somehow linked. Anyway, the first few steps I took with flashing the stock recovery and wiping everything from stock recovery is what fixed the immediate encryption issue for me.
Hi,
I'm having a bit of trouble. I had a brand new Redmi 4X, and I was advised to install TWRP, root it, and install the Xiaomi.eu rom until LineageOS is released. I unlocked the bootloader, flashed TWRP, managed to get into it once and now I can't do it again. When TWRP loaded it asked me for a password for decryption but it let me just skip it it seems (not sure if that is the problem) but now I can't boot normally, I can't boot into recovery, but fastboot seems to work okay. How do I go about fixing this?
I've tried reflashing TWRP but I still can't get to it, and I don't really know enough about this stuff to know where I've gone wrong.
UPDATE - I think this is to do with dm-verity and having the stock kernel installed. Now it's too late to undo what I've already done, so I hope to god that someone knows how to fix this.
UPDATE - Right, the problem is solved I think. I had to do an awful lot of googling, and I'm not entirely sure what it was specifically that fixed it. But I found a guide that taught me the fastboot command "fastboot boot twrp.img" which saved the day. Even when my phone wouldn't let me into recovery, it allowed me to flash a no-verity.zip which i think is what allowed me to boot, and it allowed me to flash superSU.zip and then the ROM I was aiming for. And now I've booted into the ROM successfully and hopefully I am rooted and all is well. Plus I can access TWRP as normal now.
Any help would be greatly appreciated
Can you boot into TWRP by pressing the buttons so that you boot directly to TWRP??
Have you tried Command Prompt to boot with commands in to recovery??
And if you get into TWRP you should have everything on the SDCard and then just
format all things except SDCard and then flash from SDCard everything
That is what I would try..and yes it ask for a password but just skip it to get to it
If you can get into TWRP to flash from SDCard then you good to go..if not
Google all the commands for CMD..and plug your phone to the PC and flash everything with the
commands.....
Let us know what is working and what not and what steps exectly you are doing
EDIT
Turn off your device > Press and hold “Power” and “Volume +” buttons at the same time.
After short vibration signal release the power button and wait for TWRP to start.
To boot in stock recovery open “Update” app.
In the setting select “Boot in recovery”.
brljak83 said:
Can you boot into TWRP by pressing the buttons so that you boot directly to TWRP??
Have you tried Command Prompt to boot with commands in to recovery??
And if you get into TWRP you should have everything on the SDCard and then just
format all things except SDCard and then flash from SDCard everything
That is what I would try..and yes it ask for a password but just skip it to get to it
If you can get into TWRP to flash from SDCard then you good to go..if not
Google all the commands for CMD..and plug your phone to the PC and flash everything with the
commands.....
Let us know what is working and what not and what steps exectly you are doing
EDIT
Turn off your device > Press and hold “Power” and “Volume +” buttons at the same time.
After short vibration signal release the power button and wait for TWRP to start.
To boot in stock recovery open “Update” app.
In the setting select “Boot in recovery”.
Click to expand...
Click to collapse
Thanks for the reply. I can't get into TWRP. Even if I could get into TWRP how would I get files on the phone to flash them?
Is it possible to flash any rom from the pc directly and if it is will this possibly help? I think it's not booting because the kernel is still stock.
I'm not sure what you mean in the edit, how do I boot into stock recovery without being able to boot the phone (and when I have already flashed TWRP)?
brokemyG2 said:
Thanks for the reply. I can't get into TWRP. Even if I could get into TWRP how would I get files on the phone to flash them?
Is it possible to flash any rom from the pc directly and if it is will this possibly help? I think it's not booting because the kernel is still stock.
I'm not sure what you mean in the edit, how do I boot into stock recovery without being able to boot the phone (and when I have already flashed TWRP)?
Click to expand...
Click to collapse
Hii
I just have been reading about this bootloop
Go over here and read all of the 6 pages..will not take much time but could help you out much
https://forum.xda-developers.com/xiaomi-redmi-4x/development/official-twrp-3-2-1-0-xiaomi-redmi-4x-t3718217
Hey, I have exactly the same problem. Latest stock rom, flashed twrp in fastboot and got into the boot loop. Nothing works. I can only enter fastboot. What exactly did you do then? What is this no-verity.zip? I can't find anything about it.
I had a problem
I unlocked bootloader then installed redwolf recovery and took a nandroid backup. After that i rebooted to system but stuck into bootloop, could not boot to recovery, could not boot into system, So the only thing worked was that i flashed fastboot rom with mi flasher. And syccessfully rebooted to system with bootloader locked and stock recovery. So, if anyone have same problem you can do the same. How do i install recovery safely again? Should i use TWRP only? Should i flash v3.1.0 with lazy flasher or v3.2 directly without lazy flasher? I don't want to stuck into bootloader again, have to get all data deleted.
Hi,
I unlocked the bootloader on my Oneplus 3T, then flashed TWRP. Unfortunately I misread and tapped on the read-only bit, and since then I am not able to boot into TWRP after the first time.
These are my steps (which I am trying over and over)
- fastboot;
- flash TWRP with fastboot flash recovery recovery.img
- disconnect the phone and shutdown
- boot into recovery with power/vol-
- twrp boots; I reboot into system
- system boots; i shut down
- boot into recovery with power/vol-
- the default recovery loads instead of TWRP.
I tried ticking and unticking the checkbox for read only under Mount in TWRP; I tried restoring the full backup. Every time it keeps going into the default recovery
from TWRP, I can shut down and boot into recovery and I'll get TWRP. I can reboot into recovery and I'll get TWRP. But as soon as I reboot into system, TWRP is gone
any ideas?
https://forum.xda-developers.com/on...elp-thread-t3509641/post75240034#post75240034
eLcTrOn said:
https://forum.xda-developers.com/on...elp-thread-t3509641/post75240034#post75240034
Click to expand...
Click to collapse
hm, ok thanks; I must have missed that bit.
I flashed TWRP again, then installed SuperSU from it. It went fine, then it prompts me to reboot. upon reboot I am using root checker and it says it's not done. I reboot into recovery and I get the default one again...
edit: nevermind, I used another zip for supersu and it worked. now it boots into twrp, many thanks.
Wouldn't it be better to use Magisk?
przemcio510 said:
Wouldn't it be better to use Magisk?
Click to expand...
Click to collapse
I flashed FreedomOS with Magisk at the end.
I have been using this phone for a few months now but have never been able to get twrp to work. I am currently running on android pie. Has anyone been able to successfully install twrp?
I can boot twrp and access files, if my phone is password free. If it has a password, I can type it in and I am stuck on trying decryption until it gives up. If I type it in wrong, it fails instantly. Any advice, or changes I should make?
me too, still failed to flash TWRP and custom rom
even after followed steps here > https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375/page25
nope :/
Same issue for me
no twrp is working at all...even magisk get uninstalled automatically with boot, and if try to flash any magisk module it gets stuck in bootloops:crying:
It is working fine here.
Download the last TWRP.img and installer.zip, put the installer.zip on phone (twrp.me/xiaomi/xiaomimia2.html)
1. In settings select "none" to screen lock (Just for the install);
2. Boot TWRP by fastboot;
3. In TWRP flash the Installer.zip;
4. Flash magisk If you want.
5. Reboot
6. Enable your screen lock again.
It works
clemel said:
It works
Click to expand...
Click to collapse
Which version?