I just updated to 6.0.1 (MMB29P on my nexus 6p and tried to root. I installed twrp via fastboot adb whatever and I get dead android guy. Twrp just will not install. I need to update for cm 13 so i stop getting internal error message at boot which drives me crazy. I do not want to downgrade so i can keep the January security updates but i might have to at this point.
Related
I was trying to upgrade from CM10.2 to CM11 (M2 Snapshot) and now I'm getting status 7 and can't install the CM11 image. I can't boot now either. I queued both this and the 4.4 google apps up (that is a mistake I guess?) and I'm guessing it went ahead and installed the incompatible google apps even though the CM11 failed.
So I'm thinking the status 7 error is because my TWRP image is outdated, because I have the correct CM11 for my device. Is there a way to update TWRP from within TWRP? I am not seeing the option. I do have the recovery.img on the device.Not sure what else it could be. Do I have to load ADB and use it to flash an updated recovery now?
Any help would be appreciated. Kind of desperate here since nothing is working at this point.
I got it sorted out... loaded the SDK, managed to update the TWRP image to something more current with fastboot and finally was able to install the CM11 zip without the status 7 error.
[OTA Captured] Android 4.4.4 KTU84P for the Nexus 7 2013
Nexus 7 2013 Wifi (flo) Over Air Update from KTU84L 4.4.3 to KTU84P 4.4.4
This only for Nexus 7 2013 Wifi Version
If you ran Towelroot on 4.4.3 and got root, then took this OTA, you will lose root (no surprise there). I was able to reinstall Towelroot and reroot. (SuperSU reports new binary required, then reports update failed, but after reboot I was rerooted.) Obviously, this only matters if your bootloader is locked.
Yesterday.
I lose root and custom recovery (cwm) after 4.4.4 OTA update on my Nexus 7.
Then I installed TowelRoot, applied the exploit and I gain root again... very very simple! No unlock bootloader needed or fastboot command...
Then with Rom Manager I reflashed custom recovery (cwm), flashed UPDATESuperSu.zip and uninstalled Towelroot apk....
recovery gone
This OTA (actually installed via Android system update) killed my recovery (TWRP) too.
I've reflashed TWRP 2.7.1.1 via fastboot, but I can't seem to get into recovery. Whenever I select Recovery from the bootloader, I get an opened-up android drawing with a red exclamation over him, sort of like the "No command" thing with my Nexus 4, only without "No command". Naturally, I tried holding Power+Vol-UP, but that didn't work like my Nexus 4. I can't seem make any key combination or duration of key hold work...
The happy ending is that I went back to TWRP 2.7.1.0 and I can get into recovery (and reflash SuperSU). Hard to believe there's really a problem with 2.7.1.1. Maybe I'll try the next version...
NRT works perfectly
I just used Nexus Root Toolkit with TWRP and worked perfectly fine for re-rooting.
Just I update the latest version 4.4.4. Its still not rooted from the beginning. Can anyone advice shall I change to run on ART on my tab which is not rooted. Thhhanks
Sent from my Nexus 7 using XDA Free mobile app
I wanted to downgrade from 5.1.1 to 4.4.4, as the lollipop update wasn't stable for me. I used the Wugfresh Nexus Rootkit. However, when I ran the whole process, the device failed to boot. The bootloader works, but recovery does not. Any help will be welcome
I've searched tried many things can't get a recovery to work. I'm on the latest version of N rooted with auto root. Now what.
Flash the latest 6.0 vendor image and TWRP will work, however 7.0 wont boot without the 7.0 vendor image. So if you're wanting 7.0 to boot, flash 6.0 vendor>flash twrp>do whatever>flash 7.0 vendor>boot into Android.
Vekhez said:
Flash the latest 6.0 vendor image and TWRP will work, however 7.0 wont boot without the 7.0 vendor image. So if you're wanting 7.0 to boot, flash 6.0 vendor>flash twrp>do whatever>flash 7.0 vendor>boot into Android.
Click to expand...
Click to collapse
Can I trouble you for the link for trwp. IMG.
Googling TWRP for Nexus 6P is pretty easy..
https://twrp.me/devices/huaweinexus6p.html
Tried the method above no go.
Adb flashed latest marshmallow image. Then trwp. 3.02 or the latest. Could not get past frozen trwp screen.
pospower said:
Tried the method above no go.
Adb flashed latest marshmallow image. Then trwp. 3.02 or the latest. Could not get past frozen trwp screen.
Click to expand...
Click to collapse
You're being pretty vague in describing what you've done which makes it very difficult to help you. Are you currently on Marshmallow or Android N? If you're on Android you need a modified boot.img and you must also fully decrypt.
A couple of months ago I flashed the June 4, 2019 Pixel Experience ROM using TWRP v3.2.3-1 on my Nexus 6P and worked very well using a Win10 PC and Android SDK for Windows.
When the September 6, 2019 update was available so I decided to flash it on my Nexus 6P. That's when things went wrong. Now my Nexus 6P boots back and forth between the initial bootloader and the Google logo about 2-3 times then goes into TWRP. Once in TWRP I'm able to wipe the cache and format the data. Then I try to do the adb sideload, when it reaches anywhere from 3% to 15% then my Nexus 6P freezes up for about a few seconds, then reboots eventually going back to TWRP. I have used TWRP v3.3.1-0 and v3.2.3-1 but same results. I've tried flashing the Aug 26 Pixel Exp ROM and even tried to restore the June 4 Pixel Exp ROM I had working on it, but no luck.
Update: I applied the BLOD workaround and flashed the TWRP FBE version on the my Nexus 6p. The adb sideload successfully completes now, but the Nexus 6p still boots back and forth between the initial bootloader warning screen and the white Google logo.
Update: I flashed the June 4, 2019 Pixel ROM, THEN I applied the BLOD patch and it worked! My Nexus 6P is now running great with the Pixel Experience ROM from June 2019. However I when I try to install the updates it goes into TWRP prompts me for a password. I enter the password in TWRP but it says the password is invalid. So I can't apply any updates to the Pixel ROM. I tried flashing newer versions then applying the BLOD patch but no luck. It seems like I'm stuck with the June 2019 Pixel ROM and can't upgrade beyond that version.
Has anyone ran into this issue?