[SOLVED] Stuck into TWRP 3.0.4-0 - OnePlus 3T Questions & Answers

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.

Related

Root Tutorial

Warning don't try this if you are new to rooting.. wait for more confirmation
I've successfully rooted my phone using these steps:
Download the TWRP recovery image from http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601 credit @jemmini
Download SuperSU from http://download.chainfire.eu/supersu-beta
Enable Developer Options
Enable OEM unlock
Enable USB Debugging
Reboot phone bootloader (adb reboot bootloader or vol up + power)
fastboot oem unlock
vol up to confirm unlock
your phone will ask you to reboot but vol up and vol down doesn't do anything. (other were having issue with boot looping here because of this..)
fastboot reboot bootloader
fastboot flash recovery twrp-recovery.img (the file downloaded in step 1)
fastboot reboot
while the phone is rebooting, press and hold vol up (this will launch TWRP recovery)
Optional: do not enable write access (for backup purpose)
select wipe, format data, type in yes (this fixes the boot looping issue -- credit @acotto)
now make a backup of your phone
Copy supersu.zip to your phone
install supersu.zip
To make TWRP recovery permanent: rename or delete /system/recovery-from-boot.p
reboot
your phone will take awhile to boot up since it has to rebuild all of your applications for the first time.
Edit:
I haven't figured out how to make TWRP permanent yet. Blu is restoring the stock recovery on reboot.
Thanks for the write up, looks really promising.
For those who need fastboot, I used this All in One to get it set up on my PC. I am running Windows 10 and it installed and worked just fine.
Followed the instructions above and achieved root. Thanks to OP for the great instructions.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
updated the instructions to make TWRP permanent.
emowing said:
updated the instructions to make TWRP permanent.
Click to expand...
Click to collapse
I did your original instructions and TWRP was permanent automatically.
Sent from my VIVO XL using Tapatalk
As bad as I wanna root this, I'll be waiting for a backup stock rom just in case thanks for the info!!
Never mind I guess there is a stock rom but its too early for me.
Help please>> bootloop
i've got the bootloop after unlocking the OEM... does anyone have a work around it yet??
The Remedy said:
i've got the bootloop after unlocking the OEM... does anyone have a work around it yet??
Click to expand...
Click to collapse
Don't unlock bootloader, it's not needed.
For now, use recovery restore to original ROM, clear data/cache in recovery, then you should be able to boot.
The Remedy said:
i've got the bootloop after unlocking the OEM... does anyone have a work around it yet??
Click to expand...
Click to collapse
I have already given a big warning about this unlock bootloader, why didn't you read ?
Click the link, the solution is there. Generally, install TWRP, then restore from the image given.
quyvinh said:
I have already given a big warning about this unlock bootloader, why didn't you read ?
Click the link, the solution is there. Generally, install TWRP, then restore from the image given.
Click to expand...
Click to collapse
I was in a rush and didnt want to do much rushing but I figured out on my own and I've been running Root w/ Xposed for the last 2 days now....SOLID!!
Not Working for Vivo y51l.
emowing said:
Warning don't try this if you are new to rooting.. wait for more confirmation
I've successfully rooted my phone using these steps:
Download the TWRP recovery image from http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601 credit @jemmini
Download SuperSU from http://download.chainfire.eu/supersu-beta
Enable Developer Options
Enable OEM unlock
Enable USB Debugging
Reboot phone bootloader (adb reboot bootloader or vol up + power)
fastboot oem unlock
vol up to confirm unlock
your phone will ask you to reboot but vol up and vol down doesn't do anything. (other were having issue with boot looping here because of this..)
fastboot reboot bootloader
fastboot flash recovery twrp-recovery.img (the file downloaded in step 1)
fastboot reboot
while the phone is rebooting, press and hold vol up (this will launch TWRP recovery)
Optional: do not enable write access (for backup purpose)
select wipe, format data, type in yes (this fixes the boot looping issue -- credit @acotto)
now make a backup of your phone
Copy supersu.zip to your phone
install supersu.zip
To make TWRP recovery permanent: rename or delete /system/recovery-from-boot.p
reboot
your phone will take awhile to boot up since it has to rebuild all of your applications for the first time.
Edit:
I haven't figured out how to make TWRP permanent yet. Blu is restoring the stock recovery on reboot.
Click to expand...
Click to collapse
Help me find out method to root this phone.
Had tried kingroot,kingoroot and other root tools.
Model : Vivo y51
Waiting...
Why won't this work?! I can't even load TWRR once. It always boots and then re-boots to the original recovery. Pushing volume up after flashing the twrr recovery doesn't go into recovery mode.
---------- Post added at 01:30 AM ---------- Previous post was at 01:25 AM ----------
Is it okay to change or delete /system/recovery-from-boot.p before loading the recovery.img of TWRR??
What version of android is this working on? I'm on the latest
How do I get out of this bootloop?
emowing said:
Warning don't try this if you are new to rooting.. wait for more confirmation
I've successfully rooted my phone using these steps:
Download the TWRP recovery image from http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601 credit @jemmini
Download SuperSU from http://download.chainfire.eu/supersu-beta
Enable Developer Options
Enable OEM unlock
Enable USB Debugging
Reboot phone bootloader (adb reboot bootloader or vol up + power)
fastboot oem unlock
vol up to confirm unlock
your phone will ask you to reboot but vol up and vol down doesn't do anything. (other were having issue with boot looping here because of this..)
fastboot reboot bootloader
fastboot flash recovery twrp-recovery.img (the file downloaded in step 1)
fastboot reboot
while the phone is rebooting, press and hold vol up (this will launch TWRP recovery)
Optional: do not enable write access (for backup purpose)
select wipe, format data, type in yes (this fixes the boot looping issue -- credit @acotto)
now make a backup of your phone
Copy supersu.zip to your phone
install supersu.zip
To make TWRP recovery permanent: rename or delete /system/recovery-from-boot.p
reboot
your phone will take awhile to boot up since it has to rebuild all of your applications for the first time.
Edit:
I haven't figured out how to make TWRP permanent yet. Blu is restoring the stock recovery on reboot.
Click to expand...
Click to collapse
was able to flash the twrp by renaming to recovery.img. but after fastboot reboot, even holding volume up it just reboots like normal?
what version of android should I have installed for this tutorial to work?

Can't access to TWRP anymore

Hello everyone,
so here is my configuration:
-latest TWRP (3.0.2) with F2S support
-bootloader unlocked
-the N6 is rooted
-ROM: AICP MM
2 days ago I tried to reboot to recovery to flash a more recent version of my AICP ROM. I just had the time to see the TWRP boot logo and then the phone rebooted to load the system. I can't access anymore to my recovery. I tried to rename the twrp directory on the internal SD but it does not change anything.
I reflashed TWRP with ADB and fastboot, but it didn't resolve the problem.
The only change I made recently was to flash a new radio to try to improve my connectivity.
I flashed 5.34 with the new bootloader in fastboot. Then I tried 5.32 without changing the bootloader and finally the 5.36 with the latest bootloader. So I don't know when the problem occured but now my phone even reboots randomly !
So if anyone has a solution you're welcome !
What happens when you connect the N6 to the PC and issue the fastboot boot recovery command?
Check your volume controls. They may be stuck.
Had this Problem on an other device . No recovery flash with fastboot . Dont no how , but Trwp manager APP from playstore did it .
you have to flash twrp right.. if you use a toolkit or flash the recovery with fastboot boot(instead of fastboot flash) then it will only boot into twrp 1 time, then you will need to flash it again if you want to use it again.
Strephon Alkhalikoi said:
What happens when you connect the N6 to the PC and issue the fastboot boot recovery command?
Check your volume controls. They may be stuck.
Click to expand...
Click to collapse
If I'm using "adb reboot recovery", the N6 is rebooting and load the recovery but I only see the TWRP boot logo. Then it's rebooting from the Google logo...
I've flashed the recovery with "fastboot flash recovery recovery.img", but I've also tried with flashify and still the same problem !
In fact I think that's a problem which is related to the upgrade of the bootloader or the radio. I'm with the 71.21 bootloader which came with the latest radio (from the Android N images). Even with the previous bootloader the problem occured. So until which bootloader can I downgrade without bricking my phone ?
Thanks in advance for your suggestions !
marcp39 said:
If I'm using "adb reboot recovery", the N6 is rebooting and load the recovery but I only see the TWRP boot logo. Then it's rebooting from the Google logo...
I've flashed the recovery with "fastboot flash recovery recovery.img", but I've also tried with flashify and still the same problem !
In fact I think that's a problem which is related to the upgrade of the bootloader or the radio. I'm with the 71.21 bootloader which came with the latest radio (from the Android N images). Even with the previous bootloader the problem occured. So until which bootloader can I downgrade without bricking my phone ?
Thanks in advance for your suggestions !
Click to expand...
Click to collapse
yea, you can downgrade, but why? and why are you doing adb reboot recovery? you know that you can use a terminal emulator app on your phone and then reboot recovery using it? every custom rom should also have a reboot recovery option when pressing the power button as well.
simms22 said:
yea, you can downgrade, but why? and why are you doing adb reboot recovery? you know that you can use a terminal emulator app on your phone and then reboot recovery using it? every custom rom should also have a reboot recovery option when pressing the power button as well.
Click to expand...
Click to collapse
I want to try to downgrade the bootloader because this problem occured just after changing it. I've not modified anything else.
I've tried with a terminal emulator, same symptoms.
If I'm using the reboot menu of AICP it's exactly the same behaviour. And that's the usual function I'm using to reboot to recovery. In fact all the commands are working, the N6 is rebooting to recovery but I just see the TWRP logo, then it reboots the phone to the google logo, then it starts the system...
Even if I'm launching recovery from the bootloader, I'm getting the same result.
marcp39 said:
I want to try to downgrade the bootloader because this problem occured just after changing it. I've not modified anything else.
I've tried with a terminal emulator, same symptoms.
If I'm using the reboot menu of AICP it's exactly the same behaviour. And that's the usual function I'm using to reboot to recovery. In fact all the commands are working, the N6 is rebooting to recovery but I just see the TWRP logo, then it reboots the phone to the google logo, then it starts the system...
Even if I'm launching recovery from the bootloader, I'm getting the same result.
Click to expand...
Click to collapse
sounds like you need to clear the recovery partition, then flash twrp again.
simms22 said:
sounds like you need to clear the recovery partition, then flash twrp again.
Click to expand...
Click to collapse
With "fastboot erase recovery" ?
marcp39 said:
With "fastboot erase recovery" ?
Click to expand...
Click to collapse
honestly, i dont remember how.
So here are my last attempts:
-I've tried to clean the cache with "fastboot erase cache", I thought it could be corrupted. BIG MISTAKE ! This time the phone is bootlooping when lauching the ROM...
And of course, I'm making some backups but they are on the "internal sd"... So I can't access my files anymore !
-I've also tried "fastboot erase recovery" and reflashed recovery. No improvement.
-I've downgraded the bootloader from 71.21 to 71.18. Nothing changed.
-I was asking myself if last time I didn't enter a wrong command in typing "fastboot flash boot bootloader.img" instead of "fastboot flash bootloader bootloader.img". So even if I've added benzocore on my AICP ROM, I decided to flash the boot.img from AICP zipfile on the boot partition (+ erase boot). So this time no more bootlooping of the ROM, because I'm stuck on the google logo :crying:...
I've never encounter such a desperate situation ! I don't even understand why I can't boot in recovery...
I could reflash a factory image on my phone, but this would erase all my datas !
Do you think I could reflash a factory image (except the data partition), just to be able to get a valid recovery, and access my files from the computer ? Then I could erase data partition, and reflash a new ROM ?
I don't want to precipitate the next actions because I don't have any joker... and with this stupid idea of not putting any µSD slot in most phones nowadays we're captive of the situation when the phone is bricked ! We can't recover data easily, even with adb pull (which does not work in my case of course).
So please share your ideas, they'll be welcome ! I've read A LOT of posts on XDA and others, but no solution until now....
TIBU to back up your data and then move the data on to PC. Use NRT WUG Fresh tool to flash MOB30M (stock, unroot) and then root/recovery and then start over. If you don't want encrypt then "format data" once in TWRP and then flash custom kernel like HellsCore to not force encrypt.
marcp39 said:
I could reflash a factory image on my phone, but this would erase all my datas !
Click to expand...
Click to collapse
Don't use FlashAll, it's usually broken, anyway. But rather unpack the zip, flash boot and system. And either flash cache or erase it. It does the same.
HueyT said:
TIBU to back up your data and then move the data on to PC. Use NRT WUG Fresh tool to flash MOB30M (stock, unroot) and then root/recovery and then start over. If you don't want encrypt then "format data" once in TWRP and then flash custom kernel like HellsCore to not force encrypt.
Click to expand...
Click to collapse
TIBU for Titanium Backup ? How do you want I use this app since I don't have access to android, only to the bootloader ? You want me to install MOB30M without wiping the datas from my current rom, export the result and then wipe everything to make a clean install ?
marcp39 said:
TIBU for Titanium Backup ? How do you want I use this app since I don't have access to android, only to the bootloader ? You want me to install MOB30M without wiping the datas from my current rom, export the result and then wipe everything to make a clean install ?
Click to expand...
Click to collapse
If you can't backup your data via an app, then you're stuck to flash back to stock losing your info. You can move stuff from your "internal sd" and "data" partitions to your laptop by using fastboot command but I don't remember the exact command
---------- Post added at 03:16 PM ---------- Previous post was at 03:12 PM ----------
HueyT said:
If you can't backup your data via an app, then you're stuck to flash back to stock losing your info. You can move stuff from your "internal sd" and "data" partitions to your laptop by using fastboot command but I don't remember the exact command
Click to expand...
Click to collapse
Just looked it up. You can't backup your data via fastboot but you can using "adb" command. The problem is getting "adb" to work requires "USB Debugging" to be on and android working Thus, you're likely stuck losing your data.
HueyT said:
If you can't backup your data via an app, then you're stuck to flash back to stock losing your info. You can move stuff from your "internal sd" and "data" partitions to your laptop by using fastboot command but I don't remember the exact command
---------- Post added at 03:16 PM ---------- Previous post was at 03:12 PM ----------
Just looked it up. You can't backup your data via fastboot but you can using "adb" command. The problem is getting "adb" to work requires "USB Debugging" to be on and android working Thus, you're likely stuck losing your data.
Click to expand...
Click to collapse
Yeah unfortunately we can do it with adb (like this http://stackoverflow.com/questions/8650407/how-to-copy-selected-files-from-android-with-adb-pull) but not with fastboot. Tomorrow I'll try to flash each *.img from MOB30M separately and see if I can recover a working recovery to access to my datas ! Thanks for your answer btw.
Hello everyone !
So here are the last news...
I've tried an older TWRP like 2.8.x.x same problem.
I've flashed all the *.img from MOB30M except data, but my recovery was still not accessible !!!
So I was resigned to format my data and flash the *.img on it.
This time it worked, my N6 was coming back to life !!! Then I had to root it, flash the recovery, remove encryption and format data with F2FS !
I still don't understand how a corrupted (?) data partition could block the running of recovery, that's strange !
So now I have to restore the data from a TWRP image dated 04-16 I had on my NAS...I can tell you that in the future I won't let my recent backups only on internal storage !
Will you believe me if I tell you that the same problem is occuring again :crying: ?
Several days ago, it started when the impossibility to enter the recovery but this time it does not reboot in bootloader, just stuck... Now I got random reboots and stange behaviour from applications !
I NEVER had a serious problem like that with my N6 before. So I don't understand how can I get data corruption like this ? Last time I was using Benzo kernel, now DeYuS kernel but with no exceptional settings, no overclocking.
I've just disabled "forceencrypt" and convert data to F2FS (no problem before).
So does anyone have a clue about this problem ?

Trying to install TWRP on my Nexus 6 - keeps reverting back to stock recover

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.

Redmi 4X bootloop after installing TWRP?

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.

Question How do i get Stock recovery to not replace TWRP when rebooting???

Tried a bunch of things to make the TWRP installation persistent, but it just goes back to MIUI recovery when i reboot from the system.
I'm using TWRP 3.5.2 by Nebrassy.
USB debugging turned on
Correct drivers installed
fastboot devices work Using minimal ADB and fastboot
I have the file renamed as TWRP.img.
Steps i followed:
fastboot boot "TWRP.img" - Correctly boots into TWRP
install the TWRP image to the recovery partition - Happens with no errors
Reboot to system - No errors there as well
Reboot to recovery - Goes back to MIUI recovery.
Can someone please tell me what i should do?
PS: Tried with TWRP 3.6.0 as well just now. Same issue.
Helhound0 said:
Tried a bunch of things to make the TWRP installation persistent, but it just goes back to MIUI recovery when i reboot from the system.
I'm using TWRP 3.5.2 by Nebrassy.
USB debugging turned on
Correct drivers installed
fastboot devices work Using minimal ADB and fastboot
I have the file renamed as TWRP.img.
Steps i followed:
fastboot boot "TWRP.img" - Correctly boots into TWRP
install the TWRP image to the recovery partition - Happens with no errors
Reboot to system - No errors there as well
Reboot to recovery - Goes back to MIUI recovery.
Can someone please tell me what i should do?
PS: Tried with TWRP 3.6.0 as well just now. Same issue.
Click to expand...
Click to collapse
Try again to flash TWRP dirty and if it's started don't boot with software. You have to boot TWRP again by pressing volume + and power button until you'll get vibration , afterwards you'll be in TWRP again, clear dalvik and cache and restart system via TWRP menu
Laptapper said:
Try again to flash TWRP dirty and if it's started don't boot with software. You have to boot TWRP again by pressing volume + and power button until you'll get vibration , afterwards you'll be in TWRP again, clear dalvik and cache and restart system via TWRP menu
Click to expand...
Click to collapse
Sorry mate that didn't work. Still going back to stock recovery...
Since i didn't find a solution to make the installation presistant, i went ahead and flashed Elixir with the temporarily booted TWRP. Then wiped cache and dalvik, flashed the TWRP image, formatted data and then rebooted. Now it works.
Edit: This method did something to my recovery. I can boot to system and recovery fine but TWRP isn't able to mount the data partition. So i'm not able to flash anything or root the device anymore.
I tried formatting data, no luck.
Then tried repairing the data partition. No luck.
Changed the file system to EX2 and then EX4... Nothing.
Anyone know a solution for this?
Helhound0 said:
Sorry mate that didn't work. Still going back to stock recovery...
Click to expand...
Click to collapse
Then you've got to do a flash with stock ROM and miflash via pc
Laptapper said:
Then you've got to do a flash with stock ROM and miflash via pc
Click to expand...
Click to collapse
Would that re-lock the bootloader? And if so do i have to wait 7 more days for it to be unlocked?
I used the Disable-Dm-Verity-Zip directly in TWRP after installation. Worked without a problem.
romuser87 said:
I used the Disable-Dm-Verity-Zip directly in TWRP after installation. Worked without a problem.
Click to expand...
Click to collapse
I read that somewhere too but that didn't help me at all... Maybe i have a bad zip file..
Can you share the zip you flashed?
Also, any idea how i could get this fixed:
Helhound0 said:
Since i didn't find a solution to make the installation presistant, i went ahead and flashed Elixir with the temporarily booted TWRP. Then wiped cache and dalvik, flashed the TWRP image, formatted data and then rebooted. Now it works.
Edit: This method did something to my recovery. I can boot to system and recovery fine but TWRP isn't able to mount the data partition. So i'm not able to flash anything or root the device anymore.
I tried formatting data, no luck.
Then tried repairing the data partition. No luck.
Changed the file system to EX2 and then EX4... Nothing.
Anyone know a solution for this?
Click to expand...
Click to collapse
Helhound0 said:
I read that somewhere too but that didn't help me at all... Maybe i have a bad zip file..
Can you share the zip you flashed?
Also, any idea how i could get this fixed:
Click to expand...
Click to collapse
The attached file worked for me
Helhound0 said:
Would that re-lock the bootloader? And if so do i have to wait 7 more days for it to be unlocked?
Click to expand...
Click to collapse
1. With MiFlash there is an option at the bottom of the screen to lock bootloader. Just make sure it is NOT checked, and you will be safe to use MiFlash without relocking bootloader.
2. When installing TWRP for first time, it is essential that your first reboot is straight back to TWRP - then it becomes persistent, and future reboots to recovery will be to TWRP. If you do not do the first reboot back to TWRP, the stock MIUI ROM recovery reinstalls itself.
HiQual said:
1. With MiFlash there is an option at the bottom of the screen to lock bootloader. Just make sure it is NOT checked, and you will be safe to use MiFlash without relocking bootloader.
2. When installing TWRP for first time, it is essential that your first reboot is straight back to TWRP - then it becomes persistent, and future reboots to recovery will be to TWRP. If you do not do the first reboot back to TWRP, the stock MIUI ROM recovery reinstalls itself.
Click to expand...
Click to collapse
The first ever twrp install i did, i rebooted to system by mistake but i reflashed twrp and made sure to reboot to recovery.... That was the second try. I think i may have tried at least two dozen times since that but it just kept booting back to stock recovery...
I think I'll run with this until the end of Jan and then redo everything from scratch...
Helhound0 said:
Since i didn't find a solution to make the installation presistant, i went ahead and flashed Elixir with the temporarily booted TWRP. Then wiped cache and dalvik, flashed the TWRP image, formatted data and then rebooted. Now it works.
Edit: This method did something to my recovery. I can boot to system and recovery fine but TWRP isn't able to mount the data partition. So i'm not able to flash anything or root the device anymore.
I tried formatting data, no luck.
Then tried repairing the data partition. No luck.
Changed the file system to EX2 and then EX4... Nothing.
Anyone know a solution for this?
Click to expand...
Click to collapse
I'm stuck at this stage. Have you found any solution yet?

Categories

Resources