Related
My N10 with stock 5.1 previously had root with TWRP 2.8.6, but for some reason it recently lost root. In addition, it seems that TWRP has been corrupted because whenever I try to boot into recovery I get a dead bootloader with a red exclamation mart. After I flashed the most recent version of TWRP 3.0.0-1 using "fastboot flash recovery twrp-3.0.0-1-manta.img" (bootloader still unlocked), I still get a dead bootloader when booting into recovery.
Then I flashed back to TWRP 2.8.6, but the problem remains!
How to fix the problem? Thanks!
I hope you can go to bootloader mode... Revert to stock by flashing the factory images and then start over again
nitin.chobhe said:
I hope you can go to bootloader mode... Revert to stock by flashing the factory images and then start over again
Click to expand...
Click to collapse
Thanks!
Just flashed an even older version (2.8.5) of TWRP, and now suddenly it can boot into recovery without any problem. I have also gained root now after flashing SuperSU.
I was planning to flash the most recent version of TWRP (3.0.0-1), and then try out CM13, but for some reason my N10 with stock 5.1 does not like those newer versions of TWRP. Do you know why?
mj56gt said:
Thanks!
Just flashed an even older version (2.8.5) of TWRP, and now suddenly it can boot into recovery without any problem. I have also gained root now after flashing SuperSU.
I was planning to flash the most recent version of TWRP (3.0.0-1), and then try out CM13, but for some reason my N10 with stock 5.1 does not like those newer versions of TWRP. Do you know why?
Click to expand...
Click to collapse
No, I do not konw that. Are you flashing correct version of TWRP made for manta?
nitin.chobhe said:
No, I do not konw that. Are you flashing correct version of TWRP made for manta?
Click to expand...
Click to collapse
I downloaded all the three versions (2.8.5, 2.8.6, and 3.0.0-1) of TWRP I've flashed so far from here:
https://dl.twrp.me/manta/
This is weird. Is it because I didn't have root during the time I flashed 2.8.6 or 3.0.0-1? I thought that flashing TWRP would not require root.
Can I flash CM13 with TWRP 2.8.5? I'll definitely make a Nandroid backup before proceeding.
mj56gt said:
I downloaded all the three versions (2.8.5, 2.8.6, and 3.0.0-1) of TWRP I've flashed so far from here:
https://dl.twrp.me/manta/
This is weird. Is it because I didn't have root during the time I flashed 2.8.6 or 3.0.0-1? I thought that flashing TWRP would not require root.
Can I flash CM13 with TWRP 2.8.5? I'll definitely make a Nandroid backup before proceeding.
Click to expand...
Click to collapse
With nandroid, you are good to go.
Should be possible :fingers-crossed:
nitin.chobhe said:
With nandroid, you are good to go.
Should be possible :fingers-crossed:
Click to expand...
Click to collapse
I did factory reset in TWRP 3.0.0-1 and then flashed CM 13.0-20160309 on my N10 with the dynamic Gapps. Now I get this error Unfortunately Google Play Services Has Stopped. Is it because the default factory reset is not good enough or something else? If it needs a full wipe, what exactly should I wipe, system and data? And after a full wipe, do I need to reflash CM13 or just Gapps?
Thanks!
mj56gt said:
I did factory reset in TWRP 3.0.0-1 and then flashed CM 13.0-20160309 on my N10 with the dynamic Gapps. Now I get this error Unfortunately Google Play Services Has Stopped. Is it because the default factory reset is not good enough or something else? If it needs a full wipe, what exactly should I wipe, system and data? And after a full wipe, do I need to reflash CM13 or just Gapps?
Thanks!
Click to expand...
Click to collapse
Problem solved: Just flashed the pico Gapps, and now everything works fine. For some reason the dynamic Gapps didn't work for me.
mj56gt said:
Problem solved: Just flashed the pico Gapps, and now everything works fine. For some reason the dynamic Gapps didn't work for me.
Click to expand...
Click to collapse
May be there isn't enough space to flash them.
Happy that is working now
Sent from my Nexus 4 using XDA Free mobile app
Hello, for the first time I used Flashfire to update my phone to the latest security update. This did install the system properly, but now if I try to boot into TWRP it will ask for my password to decrypt. I have tried entering both my Google password and my PIN key and neither are accepted. I have also tried changing my PIN key in the Android system settings but this still does not allow TWRP to decrypt my data. Am I missing something?
Same issue! I don't want to factory reset....
Edit: For now, I just flashed my kernel and SuperSU through the USB-OTG feature in TWRP... Fine for the moment.
Having the same issue as well. I updated to MHC19I through fastboot and everything went well. Installed TWRP 3.0.0 and it installed without any problems, but when I attempted to decrypt with my pattern it doesn't work. Booting to Android after decrypting it with the pattern works fine though. I wonder if this is just a TWRP issue?
I am having this same issue as well. However, I have noticed that whenever I boot into the system then try to go back into TWRP recovery it appears that the recovery is missing. The only way I have found to get back into recovery is to re-flash through fastboot.
dkflint723 said:
I am having this same issue as well. However, I have noticed that whenever I boot into the system then try to go back into TWRP recovery it appears that the recovery is missing. The only way I have found to get back into recovery is to re-flash through fastboot.
Click to expand...
Click to collapse
When you flash a boot and system image, if you dont root and patch it with SuperSU, the moment you reboot to android, it will replace recovery. Thats why after flashing is important to boot straight into TWRP, flash the SUperSU zip to patch and root and it wont revert it
But i am on the same boat... went to 19I version... saw the password message from TWRP... i even tried back 29V and took off security, reflashed 19I and still... So i figured it was TWRP needing update... So i flashed 29V and will wait a day or so
chaco81 said:
When you flash a boot and system image, if you dont root and patch it with SuperSU, the moment you reboot to android, it will replace recovery. Thats why after flashing is important to boot straight into TWRP, flash the SUperSU zip to patch and root and it wont revert it
But i am on the same boat... went to 19I version... saw the password message from TWRP... i even tried back 29V and took off security, reflashed 19I and still... So i figured it was TWRP needing update... So i flashed 29V and will wait a day or so
Click to expand...
Click to collapse
So, if you look over at the TWRP thread it is mentioned that it is possible to sideload SuperSU as well as kernels. I was able to do this just fine myself. I think TWRP just needs to be updated by the dev.
I can confirm I have Root access (Flashed SuperSU v2.68 zip) via OTG. Also flashed Xposed Framework v80 and ElementalX Kernel via the same method. I had to download v1.14 zip manually to my OTG as the auto flash method via ElementalX Kernel Manager saves the downloaded zip file to Data and TWRP has no access to it. Bit annoying
What's worse is that TWRP doesn't save any of its' own settings (Time Zone, Haptic Feedback, Display Brightness etc). Guessing this would've normally been saved on Data partition as well. So everytime you boot into recovery, its' like the first time you flashed TWRP Anyway, all working well now and I didn't have to wipe anything.
Confirmed that after the mhc19i TWRP can't decrypt.
adb sideloaded twrp again(for fun), supersu, francokernel v12.
Just getting a ton of app crashes now. Might need to format system and start over :-/
*edit* was able to transfer my /sdcard/ to computer while apps were crashing.
Rebooted to fastboot and did as follows
fastboot update -w image-angler-mhc19i.zip to format everything and start over.
fastboot flash recovery twrp-angler-3.0.0.0.img
reboot to recovery
Enable twrp to write to system
adb sideload franco kernel r12 and supersu
Now everything is decrypted (i have nothing to hide), I ahve root, I have kernel I want, and TWRP is happy because it doesnt' have to decrypt anything
I use WugFresh NRT to root my phone. I unrooted it this morning to get the OTA March update. Everything went fine until I tried to reroot. I can't get past the TWRP screen asking for a password. How can I reroot without TWRP or will this encryption problem always crop up? I do not want to factory reset.
Hey Guys, on Reddit a user suggested flashing the previous builds Vendor image. That should allow twrp decrypt.
flashcity90 said:
Hey Guys, on Reddit a user suggested flashing the previous builds Vendor image. That should allow twrp decrypt.
Click to expand...
Click to collapse
What if I'm already decrypted and using systemless root?
Sent from my Nexus 6P using Tapatalk
brianjking said:
What if I'm already decrypted and using systemless root?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
TWRP 3.0 works as normal if you are already decrypted. The issue, which is in the process of being resolved, only pertains to people using encryption.
Sent from my Nexus 5X using Tapatalk
TWRP 3.0.0-1 is out now. The issue is fixed. You can download from here: https://dl.twrp.me/angler/
Sent from my Nexus 6P using Tapatalk
dkflint723 said:
TWRP 3.0.0-1 is out now. The issue is fixed. You can download from here: https://dl.twrp.me/angler/
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Thanks for posting this info - saved me a headache updating CM today!
Okay, so I've been reading XDA for a while now to root my devices and install custom ROMs and its been incredibly helpful. However I have a huge issue with my nexus 6p and can't find a way to solve it.
Here goes....
I bought it of eBay a few months ago and unlocked the boot loader and rooted the phone plus i also installed twrp and made a nandroid backup. I then installed pure nexus rom and the phone was working incredibly well.
Fast forward to this week, I decided I wanted to upgrade to cm13, since I missed the cm theme engine. So I Wiped my device clean using twrp. And installed cm 13 and the gapps then rebooted.
The phone booted perfectly but on the optimising apps screen it would reboot and tell me to enter the password that I originally had on the pure nexus ROM. After doing so it would re optimise the apps but would crash and reboot. It was doing this continuously.
Twrp also asked for this password on every boot before it let me see the main recovery menu.
So then I took the logical next step and decided to wipe the phone clean again using twrp. Seeing as my password seemed to not clear the first time.
After the wipe, I decided to use the original nandroid backup to restore my device as the password thing was still showing up. And cm 13 was still not installing. Neither was pure nexus.
Okay this is where it went downhill. I hit restore and had everything checked. The process was going well but instead of the restore completing and twrp saying it was successful. It crashed halfway and rebooted.
Since then its stuck in a bootloop. Its on the google splash screen and then reboots to the google splash screen continuously. And does not boot to the os.
On another note. The bootloader is still unlocked. The recovery works. And so does adb/fastboot. So I wouldn't consider it hard bricked.
Here's what I've tried so far:
I've used the wugfresh root toolkit to flash stock and unroot the phone. With softbrick checked. Still nothing. Phone boots to the splash screen and then reboots to the splash screen.
I then reflashed twrp 3.0.2-1 . which worked And its not asking for my password anymore.
Again I tried restoring from my nandroid and it crashed midway which makes me think the nandroid backup is/was corrupted causing the issue in the first place?
I've also tried to just restore and Flash twrp again and then install pure nexus ROM. And still nothing?
I can also still mount my phone to the PC and copy and remove files.
On another note I find it interesting that although the ROM is installed. And the storage bar on my PC is partially filled showing that it clearly has a ROM installed. The phone does not have the standard android file system. Just the twrp backup folder and that's it.
I would be honoured if you could help me out here. And get my 6p up and running again.
Thank you . [emoji45]
I would suggest you flash the factory stock system image using fastboot to get your 6P back up and running.
If you don't have the factory image they can be downloaded from here
Extract the factory image then use fastboot to flash
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
Check out this guide which has all the information you need, especially around device encryption and flashing roms. Lastly gaining root is as simple as flashing SuperSU or Phh's SuperUser in TWRP.
I hope that helps, let me know if you get stuck.
Yea just flash stock image I had this happen to me before and flashing stock image fixed it.
Thanks guys. I'm going to read the guide and try it out. Then let you know how it all goes. Fingers crossed it all works
Sent from my ONE A2003 using Tapatalk
im_Zak said:
Thanks guys. I'm going to read the guide and try it out. Then let you know how it all goes. Fingers crossed it all works
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
FYI don't backup efs partition with that version of twrp. It's a known issue.
i did not realize that twrp had that issue
And guys, I followed the fastboot process by the letter and although everything worked well. The nexus 6p is still bootlooping on the google splash screen and not going any further. :crying:
What should I do? i've added the cmd window screenshot so you guys can have a look.
Try this thread:
http://forum.xda-developers.com/and...r-bootloop-t3454938/post68872362#post68872362
I worked for me when I was having issues. If it worked for you, please make sure to thank the OP in the thread.
this looks promising. thank you. i'll have a go now. might need your help if i get stuck somewhere though :good:
pctechdroid said:
Try this thread:
http://forum.xda-developers.com/and...r-bootloop-t3454938/post68872362#post68872362
I worked for me when I was having issues. If it worked for you, please make sure to thank the OP in the thread.
Click to expand...
Click to collapse
Thank you so so much dude. After countless hours trying everything to get my nexus 6p up and running to no avail this post did the trick.
Respect!!?✌✌??
im_Zak said:
Thank you so so much dude. After countless hours trying everything to get my nexus 6p up and running to no avail this post did the trick.
Respect!!
Click to expand...
Click to collapse
Upgrade to TWRP 3.0.2-2 real quick. You didn't need that guide(in terms of his nandroid) but I am glad it worked. Just need to wipe efs partition using adb commands.
I see. And I have upgraded to the latest twrp so hopefully it doesn't not happen again
Sent from my ONE A2003 using Tapatalk
im_Zak said:
I see. And I have upgraded to the latest twrp so hopefully it doesn't not happen again
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Good deal!!! There's a build that's unofficial of 3.0.2-3 that you can also jump onto. The current version 3.0.2-2 has a bug with backups on Android N. There was a comprehensive post that someone made about the issues with the different versions but I cannot find it for the life of me.
Jammol said:
Good deal!!! There's a build that's unofficial of 3.0.2-3 that you can also jump onto. The current version 3.0.2-2 has a bug with backups on Android N. There was a comprehensive post that someone made about the issues with the different versions but I cannot find it for the life of me.
Click to expand...
Click to collapse
Thanks for the heads up!
My rooted Axon 7 (A2017U) does not show the boot partition in TWRP when backing up or restoring a backup that previously showed the boot partition. Here is what I did prior to the problem:
1. Manually updated stock rom to B32 using DrakenFX procedures, which includes flashing bootstack. (I made a backup after the upgrade of boot, data, and system - as usual.)
2. When I restored AICP nandroid, boot was shown along with data and system. Phone operated normally, but would not flash OTA upgrade - error 7. (Attempted to flash a previous version that I had flashed before with the same error 7.)
3. Rather than unzipping the rom and deleting the asserts line, I flashed the universal boot image from LineageOS and was able to OTA without issue, but when I ran the TWRP backup, boot did not show and only system and data backed up.
4. Restored the stock nandroid, boot did not show.
My phone is operating normally, but I find it disconcerting to have made an unintended change and would appreciate any help in correcting my error.
Thanks in advance.
Hi have you fixed your problem or not?
William Guo said:
Hi have you fixed your problem or not?
Click to expand...
Click to collapse
No, still waiting for assistance.
Reflash TWRP. I had partitions missing and there was a weird version of TWRP installed for unknown reasons. Reflashing the latest TWRP fixed my problem.
JKSurf said:
Reflash TWRP. I had partitions missing and there was a weird version of TWRP installed for unknown reasons. Reflashing the latest TWRP fixed my problem.
Click to expand...
Click to collapse
That worked. Thank you very much. Weird how that happened.
Just as a matter of interest, I just did a clean install of AICP, which required installation of universal bootstack, and found that TWRP version had been replaced with an old version that did not show boot partition when doing nandroid. Reflashed current build image and boot file was visible.
Keep the latest .img on TWRP, and when you flash the universal bootstack, flash the TWRP .img after. I've asked over at the LOS thread if they could update the TWRP version on the bootstack and nobody answered lol
Should we use the one from twrps official website? I'm having the same issue but I can't remember changing my recovery.
jojofreddy said:
Should we use the one from twrps official website? I'm having the same issue but I can't remember changing my recovery.
Click to expand...
Click to collapse
You don't change your recovery, the universal bootstack zip does
It's the same whether you use the zip from TWRP's official website or raystef66's download center really
I purchased a used Nexus 6p from ebay. I've unlocked the bootloader and installed TWRP. When I boot into recovery, I get a screen that's titled, "Mount Decrpt Data". It wants me to enter a password. I don't have the password. What are my options?
I want to root the phone and install custom ROMs.
@msmcintosh- The 6P defaults to data encryption on first boot. You need to do a factory reset and before booting to the OS install TWRP and then boot back into TWRP (reboot recovery). If you want to keep your data unencrypted you now have to either flash SuperSU or a custom kernel. Either of these will disable the force encrypt flag. Also make sure you are installing v3.1.1.0.
v12xke said:
@msmcintosh- The 6P defaults to data encryption on first boot. You need to do a factory reset and before booting to the OS install TWRP and then boot back into TWRP (reboot recovery). If you want to keep your data unencrypted you now have to either flash SuperSU or a custom kernel. Either of these will disable the force encrypt flag. Also make sure you are installing v3.1.1.0.
Click to expand...
Click to collapse
I managed to screw it up. I'm stuck at the Google screen. I can boot into TWRP. I had tried to install Pure Nexus, GApps, Magisk and Franco kernel, but obviously didn't do it correctly. How can I recover my phone?
Uppdate: I download and installed the Oreo factory image and flashed it. Then TWRP. Now to figure out what went wrong flashing Pure Nexus. I'm coming from a nexus 6.
msmcintosh said:
I managed to screw it up. I'm stuck at the Google screen. I can boot into TWRP. I had tried to install Pure Nexus, GApps, Magisk and Franco kernel, but obviously didn't do it correctly. How can I recover my phone?
Uppdate: I download and installed the Oreo factory image and flashed it. Then TWRP. Now to figure out what went wrong flashing Pure Nexus. I'm coming from a nexus 6.
Click to expand...
Click to collapse
I keep screwing this up. I have TWRP, factory Oreo, rooted with Magisk. I made a backup in TWRP. I per Pure Nexus instruction, I installed the Vendor image, Pure Nexus ROM, GApps and Magisk. The system won't boot. Gets stuck at the Google screen. Can't boot into TWRP either. I can reflash TWRP, but the backup is no good (gets stuck at Google screen). I end up reflashing the factory image and TWRP. Then it will boot into Android.
I'm not sure what I'm doing wrong. It was easy to do this on my Nexus 6.
msmcintosh said:
I keep screwing this up. I have TWRP, factory Oreo, rooted with Magisk. I made a backup in TWRP. I per Pure Nexus instruction, I installed the Vendor image, Pure Nexus ROM, GApps and Magisk. The system won't boot. Gets stuck at the Google screen. Can't boot into TWRP either. I can reflash TWRP, but the backup is no good (gets stuck at Google screen). I end up reflashing the factory image and TWRP. Then it will boot into Android. I'm not sure what I'm doing wrong. It was easy to do this on my Nexus 6.
Click to expand...
Click to collapse
Not sure what you are doing wrong with the clean PN install, but you can't downgrade from O to N by flashing an older PN ROM. You may get more specific help in the dedicated PN install thread by nathanchance.
v12xke said:
Not sure what you are doing wrong with the clean PN install, but you can't downgrade from O to N by flashing an older PN ROM. You may get more specific help in the dedicated PN install thread by nathanchance.
Click to expand...
Click to collapse
I ended up flashing Nitrogen O, which worked. Thanks.