I was on DP2, with root and unofficial twrp-3.0.2-3-angler(previous versions had problems). And had google assistant too with modified build.prop. Today I flashed a zip file for pixel features. But after reboot, it stuck on the new pixel boot animation. I then applied a rollback zip file, now it is showing the old boot animation, but still stuck. I have wiped cache/dalvik.
I had a password set during boot. Previously, it used to ask for password, but not now. TWRP is now showing unable to mount storage. I don't know where the problem is. Is it the boot password? Please help. Thanks in advance.
Importantly if I wish to flash factory image, then can I flash the final build of 7.1.1(NMF26F)? Earlier I was on DP2. (npf26f).
ikaushalsha said:
I was on DP2, with root and unofficial twrp-3.0.2-3-angler(previous versions had problems). And had google assistant too with modified build.prop. Today I flashed a zip file for pixel features. But after reboot, it stuck on the new pixel boot animation. I then applied a rollback zip file, now it is showing the old boot animation, but still stuck. I have wiped cache/dalvik.
I had a password set during boot. Previously, it used to ask for password, but not now. TWRP is now showing unable to mount storage. I don't know where the problem is. Is it the boot password? Please help. Thanks in advance.
Importantly if I wish to flash factory image, then can I flash the final build of 7.1.1(NMF26F)? Earlier I was on DP2. (npf26f).
Click to expand...
Click to collapse
Greetings and welcome to assist. It appears you have already asked your question in the correct place here
http://forum.xda-developers.com/showthread.php?t=3517583
So I will close this one up
Good Luck
Sawdoctor
Related
So I had my Honor 8 (FRD L04) unlocked, rooted and running stock just fine. Then I decided to flash the unofficial Lineage rom. After doing so I got a prompt to enter a password to decrypt, while booting into Lineage and even into TWRP, I never set the password so I wasn't sure what to do. I tried a few things then eventually reflashed TWRP and got rid of the password problem then tried to restore my back up but it didn't work. Now I'm stuck. I can access fastboot, TWRP and eRecovery. eRecovery always fails to get package info. And whenever I try to do anything in TWRP it says it failed to mount cust, vendor and product. I've tried a lot of different solutions I've seen on here the dload method always goes to 5% then fails. I've flashed stock boot, recovery and system.img but didn't change anything. And I can't seem to get it to boot to stock recovery to format/wipe that way.
If there's anything anyone knows that I can do it'd be appreciated.
Got my issue solved thanks to the thread above. Not sure how to mark this as solved or closed.
Rommco05 said:
Good to know if you want rename thread u can, but I know how to do it only in phone XDA app
Click to expand...
Click to collapse
Just found how to do it on the app. Name offically changed. Thanks again for the help.
Hello, been running twrp with encryption on Lineage OS 16 without problems for 6 months. But yesterday I flashed new android Q factory image and was unable to decrypt my data in twrp, even when I put the right password in it says ''password failed, please try again''. I tried flashing various factory images, custom roms even Lineage 16 but problem persists. I had this same problem back then when I first bought this phone but managed to solve it, I can't remember how I did it. TWRP is up to date. Any ideas? thanks.
It's TWRP issue. Sadly TWRP 3.3.1 is not available in zip format. Only in .img format. In 3.3.1 this problem is resolved.
As workaround you can remove any PIN, fingerprint and set security to none in setting and you won't have to enter anything in TWRP. Do whatever you want in TWRP and then set up PIN and fingerprint again.
matusala said:
It's TWRP issue. Sadly TWRP 3.3.1 is not available in zip format. Only in .img format. In 3.3.1 this problem is resolved.
As workaround you can remove any PIN, fingerprint and set security to none in setting and you won't have to enter anything in TWRP. Do whatever you want in TWRP and then set up PIN and fingerprint again.
Click to expand...
Click to collapse
Yeah I know this, but why did it started to do this after flashing Q factory image? TWRP worked without any problem on various custom roms. Actually now I remembered that while flashing Q factory image there was a problem mounting vendor and system partition, so I went back and flashed Lineage 16 and there this TWRP password thing started if I remember correctly.
I came here looking for the answer to this very issue.
I shot off an email to TWRP if they were going to update the latest zip to 3.3.1 because fastbooting to the img works fine.
I might try the trick of removing pin and security and try again.
I have the same problem but with 9.0, if I have a pin it's ok it decrypts just fine but when I have the fingerprint set up I get this problem, it kinda blows, I'm not using twrp everyday but it still blows that you have to disable security Everytime you want to use it, also, last night I used twrp with the security on it could not decrypt so and when i tried to reboot into system, I got the prompt to install the twrp app, I screwed up and used the slider instead of the button to cancel the installation and it messed up the system, so watch out for that crap.
Hello everyone,
As I mentioned in the title, since I upgraded to Android 10, can't boot to recovery.
Dowloaded latest version of the Adb kit, and while issuing
adb reboot recovery
the phone reboots but goes to normal boot.
Tried manually (power + vol down etc.) and when choosing Recovery - same thing happens.
Needless to say that my laptop is authorized debug device and phone is in debug mode etc. - I have done this many times before Android 10 update.
All I try to do is to sideload the latest OTA as I did many times before because my phone is rooted and the updates do not install automatically.
Pixel (First generation)
Rooted with Magisk
Bootloader unlocked
Stock recovery (using TWRP without installing it when flashing Magisk)
Hope somebody can advise. Obviously there is something new in Android 10 which has to be set (like the need for debugging authorization for example, which I already did).
Thank you
John
Im getting a similar problem. I get stuck on th Google logo screen. I cant hard-reset, recovery mode or boot, the only things that works is th barcode.
Android 10 changed something in the ramdisk that you can't install TWRP directly on the phone. You have to boot it via PC using "fastboot boot <insert twrp image name>.img"
You can try installing twrp to ramdisk. Put twrp 3.3.1-0.img in your devices storage and then fastboot twrp 3.3.0-0 (disable pin etc first) then once it's booted go to advanced and select install to ramdisk and select the 3.3.1-0.img and it should install it. You may get a not enough storage error on 10/Q (I did) bit worth a punt. Make a back up first as usual, if no good flash a fresh factory.img and see if that cures it and then restore your apps/data etcfrom your Google back up (if you use it)
Good luck
junglism93 said:
You can try installing twrp to ramdisk. Put twrp 3.3.1-0.img in your devices storage and then fastboot twrp 3.3.0-0 (disable pin etc first) then once it's booted go to advanced and select install to ramdisk and select the 3.3.1-0.img and it should install it. You may get a not enough storage error on 10/Q (I did) bit worth a punt. Make a back up first as usual, if no good flash a fresh factory.img and see if that cures it and then restore your apps/data etcfrom your Google back up (if you use it)
Good luck
Click to expand...
Click to collapse
Thank you for the advice, however as I mentioned in my original post I don't want to install TWRP permanently , and the problem is that I cannot go to the stock recovery mode which has no connection to TWRP. There is something with Android 10 which changed since 9 and I'm interested to find what. Everything worked fine before the upgrade.
Also, the option to flash factory image and restore (I also have Titanium in addition to Google backup) is a too much of a hassle. I use this phone for real, not only to play with it.
Anyway, again thank you for your input.
John
Sorry mate, re read your OP. I just tried booting into the aosp recovery and got the same issue! My guess is its magisk as I could boot into the aosp recovery prior to installing it. Re flash or restore the previous boot.img or a stock boot.img and it should boot into aosp recovery again. Magisk must be installing to or patching the aosp recovery ramdisk and stopping it booting. Other than that just fastboot twrp and use that.
Edit: it's magisk, restored original images and it booted into aosp recovery first try.
I've had no problems installing TWRP 3.3.0.0 normally after using an *.img file to get TWRP started. EDIT: and booting into it.
junglism93 said:
Sorry mate, re read your OP. I just tried booting into the aosp recovery and got the same issue! My guess is its magisk as I could boot into the aosp recovery prior to installing it. Re flash or restore the previous boot.img or a stock boot.img and it should boot into aosp recovery again. Magisk must be installing to or patching the aosp recovery ramdisk and stopping it booting. Other than that just fastboot twrp and use that.
Edit: it's magisk, restored original images and it booted into aosp recovery first try.
Click to expand...
Click to collapse
You are right. I did open Magisk and from the uninstall options choosed "Restore images" (no need to do complete uninstall, which is the other option). After that I was able to boot in recovery etc. I guess this is what you meant in your PS. At the end re-flashed Magisk and all is back to normal.
I will alert the Magisk team about the issue (if they are not already aware).
Case closed.
Thanks again.
John
Master Cylinder said:
I've had no problems installing TWRP 3.3.0.0 normally after using an *.img file to get TWRP started. EDIT: and booting into it.
Click to expand...
Click to collapse
Please read my OP. I was clear that I DON'T want to install TWRP permanently and this was never the problem.
The problem is solved (kind of). See the other posts.
Thank you.
John
I thought TWRP wasn't compatible with Android 10 yet? I am seeing mixed things
aholeinthewor1d said:
I thought TWRP wasn't compatible with Android 10 yet? I am seeing mixed things
Click to expand...
Click to collapse
It works just fine.
Mzprx said:
It works just fine.
Click to expand...
Click to collapse
Are there steps for how to install somewhere? I keep reading that it's not working on the Pixel with Android 10. Thanks
aholeinthewor1d said:
Are there steps for how to install somewhere? I keep reading that it's not working on the Pixel with Android 10. Thanks
Click to expand...
Click to collapse
It is a mess. It works with Pixel (I have this one and can confirm) and supposedly Pixel 2. It won't work for brand new phones arriving with factory installed Android 10.
Read the following:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html#
After that, if you want to try, go to the page below to find instructions for your device. Note that the list is by manufacturer, so if you are looking for Pixel, it is under Google.
https://twrp.me/Devices/
Just in case - backup and have the factory image for your phone handy in case something goes wrong. For google phones you can download the image and see instructions here:
https://developers.google.com/android/images
Note that I never installed TWRP permanently, so I can't say if the permanent installation will work (I think it should, but not sure). Typically I just load TWRP and use it to flash pakages, but at the end I'm keeping the stock recovery.
Hope this helps. Good luck.
John
Mzprx said:
It is a mess. It works with Pixel (I have this one and can confirm) and supposedly Pixel 2. It won't work for brand new phones arriving with factory installed Android 10.
Read the following:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html#
After that, if you want to try, go to the page below to find instructions for your device. Note that the list is by manufacturer, so if you are looking for Pixel, it is under Google.
https://twrp.me/Devices/
Just in case - backup and have the factory image for your phone handy in case something goes wrong. For google phones you can download the image and see instructions here:
https://developers.google.com/android/images
Note that I never installed TWRP permanently, so I can't say if the permanent installation will work (I think it should, but not sure). Typically I just load TWRP and use it to flash pakages, but at the end I'm keeping the stock recovery.
Hope this helps. Good luck.
John
Click to expand...
Click to collapse
Thanks. Yea from what I can tell no one has had luck actually installing it on the Pixel with Android 10 yet. I'm familiar with how to fix everything if something goes wrong. I would try but others have already tried and failed. It won't install for them.
firstly, dont use whatever ****ty platform-tools you are using, get them from here.
secondly, you dont install recovery on android 10 yet, it doenst work. you have to just boot to twrp using `fastboot boot twrp.img` once you are in bootloader mode.
Hi everyone,
I've been trying to get TWRP to stick for a while now, but still haven't been able to get it to install. A while ago I managed to flash Resurrection Remix using Lineage recovery which does work, but since Lineage recovery is quite limited, I really wanted to get TWRP to work. Since TWRP 3.5.0 released yesterday, I gave it another shot hoping that they fixed the issue, to no success.
I can get into TWRP just fine by temp booting it with fastboot, but after flashing the installer zip, any recovery that was previously installed gets wiped and the device will reboot when trying to get into recovery. I can still boot my phone otherwise.
The steps I took to get to this point:
Unlocked bootloader
fastboot boot twrp.img
Decrypt using screen pattern (successfully)
Flashed twrp installer zip (no error messages, process finishes successfully)
Reboot into recovery (both from twrp and bootloader at a later point)
Things I've tried:
Use a different TWRP version. Same problem as described above on both 3.4.x and 3.5.x, can't get it to decrypt on lower versions due to Android 10.
Install to recovery ramdisk, this just breaks things even more, probably because it's an A/B device?
Try a different recovery. Lineage recovery works just fine, but it's very very limited. Would really like to get TWRP working.
Trying to flash the zip results in no error messages, but any previously installed recovery gets wiped and magisk is uninstalled, which leads me to believe that it has done at least something to the boot img.
Thank you in advance.
EDIT 25.02.2021:
- Attached TWRP log
EDIT 12.03.2021:
- Log didn't want to attach, they can be found here: https://pastebin.com/awnhHDBU
Same question here. It seems that you can only boot from TWRP, not install it.
Tried installing again today, to no avail. However, I was smart enough to save the log this time. I have attached it to the main post, would be much appreciated if someone could check it out.
Hey folks,
I have a big problem.
My OnePlus 6 suddenly stopped responding today and then the power went out. When I restart I can no longer get out of boot animation. Although I thought I had a custom recovery this is also stock again and unfortunately I also no longer know for sure which Android version I last had.
So I downloaded the firmware here and wanted to flash it via fastboot.
Software Upgrade - OnePlus.com
Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.
www.oneplus.com
I can switch to fastboot mode, but I read that I can't flash full OTA zips there. So I wanted to try it via adb, but the stock recovery does not seem to have this function.
Fortunately I do not often have problems, but that's why I'm stuck now.
If possible I don't want to lose any data.
I hope someone can help.
Thanks!
mcdy
Download official twrp, use Fastboot to boot into it
Fastboot boot twrp.img
vkass said:
Download official twrp, use Fastboot to boot into it
Fastboot boot twrp.img
Click to expand...
Click to collapse
Hey, so TWRP works meanwhile officially on actual Android versions? Last time I tried only mods maybe works. Thx
Hey @vkass
haven't time to do it earlier.
The part with the TWRP works well but when I try to flash "OnePlus6Oxygen_22.J.52_OTA_052_all_2103022341_f3ff04643ea24e51.zip" after reboot the phone is only able to boot into Recovery (of cource default recovery).
Do I need to install Magisk?
Would have tried with the "Magisk-24.2.zip", but TWRP says it is invalid.
Thanks!
mcdy
Because you flashed an old android 10 zip.
OnePlus6Oxygen_22.J.62_OTA_0620_all_2111252336_14afec75dd6fa.zip | by OPTeam for OnePlus 6
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Hey @vkass
thanks for your fast reply.I thought that's the last version becouse it is linked here: https://www.oneplus.com/at/support/softwareupgrade/details?code=PM1574156173727
Anyway I now downloaded the last version from Android Filehost: https://androidfilehost.com/?fid=7161016148664850007
But unfortunately, that just brings me back to my original problem.
I see now again the boot animation and since I unfortunately do not know any method with which I could see where there are problems, I only could wait for some time an hope.
Any other ideas?
Thanks!
Backup what you can with twrp, factory reset and reflash
Hey @vkass
I was afraid you were going to say that.
Because of WhatsApp, Googe Authenticator App and other banking apps it would have been great to get access again. But, since the system unfortunately does not provide any info at boot time, I do not know what else would be possible.
Somehow strange that there are no logs.
I would have also tried to reinstall Magisk and also uninstall it, but unfortunately without success. For whatever reason I come after the installation of TWRP via TWRP now even again only directly into the recovery (but no password query comes) and a boot of the system does not work at all.
Thanks!