Database Info

[solved] root/recovery borked since 6.0 update - can't apply 4.1 update

OK, so I've got the original shield tablet. I have lost root, and whenever I try to boot to recovery, the system attempts, goes to a black screen, then proceeds to normal system boot. Environment:
stock 6.0
non-rooted (not since updating to 6.0)
shield version 4.0
build MRA58K.41524_664.1902
previously had TWRP
I understand loss of root/recovery w/that last update is normal. However, I've tried:
flashing the new TWRP via fastboot w/o success (3.0.2)
flashing the rooted boot img w/o success
even flashing the stock recovery w/o success
ADB & fastboot commands chug happily along, & I'm left with the same behavior. Flashing the stock recovery actually gave me the dead android at the recovery screen (was this b/c I flashed the one for 4.0.1 & I need the one for 4.0?). So, what's my next move here?

Aaaaaaannnnnd.... I've also completely lost my WiFi. Says that it's on, but it's got the slash through it in quick settings & doesn't find any networks.

t-readyroc said:
OK, so I've got the original shield tablet. I have lost root, and whenever I try to boot to recovery, the system attempts, goes to a black screen, then proceeds to normal system boot. Environment:
stock 6.0
non-rooted (not since updating to 6.0)
shield version 4.0
build MRA58K.41524_664.1902
previously had TWRP
I understand loss of root/recovery w/that last update is normal. However, I've tried:
flashing the new TWRP via fastboot w/o success (3.0.2)
flashing the rooted boot img w/o success
even flashing the stock recovery w/o success
ADB & fastboot commands chug happily along, & I'm left with the same behavior. Flashing the stock recovery actually gave me the dead android at the recovery screen (was this b/c I flashed the one for 4.0.1 & I need the one for 4.0?). So, what's my next move here?
Click to expand...
Click to collapse
1) the twrp you linked to is for lollipop, states that in the notes section half way down the page.
2) to get root with this method you also have to install phh superuser
3) that dead Android IS the stock recovery
Now for help: flash this recovery(there are two here read and find the one for MM)
https://r.tapatalk.com/shareLink?ur...share_tid=2877117&share_fid=3793&share_type=t
[RECOVERY] [unofficial] TWRP 3.0.2-0 (2.8.7.1 for Lollipop) [2016-04-05]
Sent from my SHIELD Tablet K1 using Tapatalk

Thanks Exile. I've got TWRP installed ok now, but it doesn't seem to be able to wipe anything - just kinda hangs there (trying to wipe dalvik & cache - just sits at "formatting cache using make_ext4fs"). It's also weirdly unresponsive with UI lag on button presses; not sure if that's a known thing. I'm assuming that the "E: Failed to mount decrypted adopted storage device" is in reference to my external SD card.
I also still don't have my WiFi. I've grabbed the WiFi full OTA from this post & adb pushed it. TWRP was able to successfully flash it, but then couldn't do the ensuing dalvik/cache wipe. I let it sit for a good 10mins just to see if it would finish, but it still sat at the same point. Force power-cycling booted it into the new 4.1/6.0.1 version, and I do have my WiFi back
So, how to get root back? Can I just flash the SU 2.65 I have from TWRP? Or do I have to flash the rooted boot img again? I do already have the Superuser app installed...

t-readyroc said:
Thanks Exile. I've got TWRP installed ok now, but it doesn't seem to be able to wipe anything - just kinda hangs there (trying to wipe dalvik & cache - just sits at "formatting cache using make_ext4fs"). It's also weirdly unresponsive with UI lag on button presses; not sure if that's a known thing. I'm assuming that the "E: Failed to mount decrypted adopted storage device" is in reference to my external SD card.
I also still don't have my WiFi. I've grabbed the WiFi full OTA from this post & adb pushed it. TWRP was able to successfully flash it, but then couldn't do the ensuing dalvik/cache wipe. I let it sit for a good 10mins just to see if it would finish, but it still sat at the same point. Force power-cycling booted it into the new 4.1/6.0.1 version, and I do have my WiFi back
So, how to get root back? Can I just flash the SU 2.65 I have from TWRP? Or do I have to flash the rooted boot img again? I do already have the Superuser app installed...
Click to expand...
Click to collapse
Ok, from here just flash the supersu.zip and you should be good. I can't remember if 2.65 works or not but I know you can find a copy of 2.71. someone else has a problem with 2.72 so it may or may not work.
As for twrp it has touch screen lag issues, I don't think any of the mm compatible versions have been able to fully fix this. I've had the same problem with dalvik cache and cache wipe, it is slow as molasses but will complete eventually. Once you have root I would suggest using a program called flashfire to flash zips and do things like cache wipe. It works like a charm.
https://r.tapatalk.com/shareLink?ur...share_tid=3075433&share_fid=3793&share_type=t
[Android 4.2+][ROOT][2016.05.11] FlashFire v0.33 - Play BETA
Sent from my SHIELD Tablet K1 using Tapatalk

Thanks again, Exile. I actually had to re-flash TWRP, oddly, but after some searching, I found a mirror for su2.71, & adb pushed it. Once I had TWRP back in order, I was able to then flash it & my root is back together.

Glad you got it working. Have fun and be safe
Sent from my SHIELD Tablet K1 using Tapatalk

SuperSU 2.79 SR3 will not survive reboot

Google Play Store Pixel, stock feb update (nof26v), unrooted, unlocked bootloader. There's a longer back story to this issue I've encountered, but to cut to the chase:
I can successfully flash TWRP 3.0.2 RC1 and 2.79 SR3. I can boot into system and enjoy benefits of root. However, I've noticed that whenever I try to reboot SYSTEM, it only boots into recovery. Even when I boot into bootloader and flash stock boot.img, it'll just reboot into stock recovery, but never into system. My way out of this quasi soft-brick state is to flash stock boot.img and sideload ota and I'm good to go with all my settings/data intact, I'll just be unrooted (as expected). I can verify it survives reboot in this state.
Has anyone else encountered this before? Is there something in the latest SU that won't let it reboot properly? Is there a way I can force it to reboot a certain slot to somehow avoid this issue?
The way Android handles memory now, I don't ever feel the need to reboot. But one of the things that's essential for me is to edit build.prop to enable wifi tether and miracast. Thing is, it requires a reboot for those changes to apply, but as soon as I reboot...
I've had this all working before on the dec update and SuperSU-v2.79-201612051815.zip but then something really strange happened (long backstory referenced above) and it required me to have to re-root, only now it won't survive reboot.
Any insight is greatly appreciated!

I have never encountered this issue as a result of flashing Super SU. I have come across this when I updated to the latest image by just flashing a few components.. IE: i didnt flash the whole factory image.
Flashing the latest factory image to both slots and starting over fixed the issue for me.
Flash the image (flash_all.bat) then fastboot boot twrp and switch slots, flash factory image again.
Just my two cents.

k.s.deviate said:
Flashing the latest factory image to both slots and starting over fixed the issue for me.
Flash the image (flash_all.bat) then fastboot boot twrp and switch slots, flash factory image again.
Just my two cents.
Click to expand...
Click to collapse
Thanks for your input! Should I remove -w while flashing, or when you said starting over do you mean full wipe?
Was hoping to avoid going that route... Is there any way to salvage without wipe?

Let me also share the strange event I encountered which led me to this point:
As stated, I had December update with stable 2.79 and TWRP 3.0.2. I skipped Jan update and was planning to do the same for the Feb update, but for whatever reason, I went to check updates (knowing full well it wouldn't take since I'm not on stock recovery). It gave me the standard "downloading, installing..Oops, there's a problem" prompt and I went on my merry way.
A week or so later, I decided to manually reboot and upon boot, I noticed it said "Android is starting/configuring" something along those lines. Then I tried double tap to lock (Nova gesture) and it says phone wasn't rooted. I check and sure enough, no SU icon. Checked Android version and now it says I'm on Feb update.
Attempt to install latest from chainfire on play store and no dice. Decide to flash it instead. Downloaded 2.79 SR3. Booted temporary TWRP and flashed the install and SU and then I found that phone won't boot to anything but recovery. Now anytime, I modify the boot image in any way, I'm bricked on subsequent reboots until I flash stock boot image and sideload OTA.
How do you think the Feb update installed when it shouldn't have? Did it install to one slot while my other slot was TWRP+root?

I would guess that it may have installed onto the inactive slot, but it doesn't sound like it should have if you had TWRP and Su installed. However we are all still learning new things about the pixel every day.
I would recommend clean flashing the factory image to both slots and starting over. Sounds like something became corrupt.

What version of ADB and Fastboot are you running? This reboot to bootloader happened to me when I unknowing using an older version.

Try wiping the device completely push your factory image via ADB and fastboot and installed of TWRP RC1 use alpha 2 never had a issue with alpha 2 after flashing TWRP boot into stock then go back into TWRP then flash SuperSU

jamespark said:
How do you think the Feb update installed when it shouldn't have?
Click to expand...
Click to collapse
People have reported automatic OTA updates on rooted Pixel phones. You can shut off automatic OTA updates by following the following link. People report still getting a notification for updates after the setting change, but updates no longer happen automatically. The site below also lists a way to entirely shut off OTA notifications, yet that change causes my phone to stay awake constantly and never go into deep sleep, so I only recommend the link. There's a thread or two about FlashFire, which I may eventually get around to trying.
https://www.androidexplained.com/pixel-disable-ota-updates/

Are you okay with losing data? I can post the links I used to download SuperSU and a little guide to flash to stock and reroot. Maybe you'll be able to figure what you're doing wrong or just doing what I do step by step might fix it.

mngdew said:
What version of ADB and Fastboot are you running? This reboot to bootloader happened to me when I unknowing using an older version.
Click to expand...
Click to collapse
Definitely using an older version of adb and fastboot. I'll update and retry with the latest, thanks for the suggestion!

alluringreality said:
People have reported automatic OTA updates on rooted Pixel phones. You can shut off automatic OTA updates by following the following link. People report still getting a notification for updates after the setting change, but updates no longer happen automatically. The site below also lists a way to entirely shut off OTA notifications, yet that change causes my phone to stay awake constantly and never go into deep sleep, so I only recommend the link. There's a thread or two about FlashFire, which I may eventually get around to trying.
https://www.androidexplained.com/pixel-disable-ota-updates/
Click to expand...
Click to collapse
Thanks for the heads up! I had this setting enabled and I have since disabled it.
I really appreciate the community and all your help!

SOLVED
I'm pleased to report that I now have root that survives reboot!
- From stock: flashed TWRP and SU. verified root, edited build.prop and reboot system..... boots into recovery (the usual problem)
- switched active slots and flashed SU, reboot
- SU icon in app drawer but when launched: "supersu binaries not installed"
- reboot into recovery and flashed su, reboot
- su is installed, but build.prop changes didn't stick. edited build.prop, reboot system
- boots into recovery.
- flashed su, did NOT reboot, backed out, switched slots, flash SU to the other slot, reboot
- huzzah!
is it verified that android will alternate active slots upon each subsequent reboot (i.e. A/B/A/B/...)?
it would seem I was making changes and rebooting to the other slot which was jacked up, so I had to finally apply the same changes to both slots and now everything is working!
I honestly don't know what I just did, and I guess sometimes it's better to be lucky than smart lol but, boy, this two-system partition is a piece of work...
Thanks again to everyone for all your help!!

Can't install lineage-15.1-20180918 on a Google Pixel (sailfish) - bootloop

Hello,
I'm trying to install lineage-15.1-20180918 on my new (second hand) Google Pixel (sailfish). It came with Android 7.1.0 (NDE63H, Oct 2016) pre-installed.
No mater what I try to do, after installing Lineage zip file, I always get a warning saying that there is no OS. When I try to reboot to System, I am stuck in a boot loop between a screen saying that I should lock the bootloader and another one displaying the Google logo.
General information about device and softwares used
I run Debian on the PC that is used for the install, adb (v 1:7.0.0+r33-1) and fastboot (v 1:7.0.0+r33-1) are installed.
I got the Lineage zip from there (the shasum is good).
I got the TWRP image from there (v 3.2.3-1).
What I did
I followed the official howto there.
I have unlocked the bootloader, can boot into the TWRP recovery.
TWRP is launched via
Code:
fastboot boot twrp-3.2.3-1-sailfish.img
I did "Format Data", then "Advanced Wipe" (selected everything and wiped).
Then
Code:
adb push lineage-15.1-20180918-nightly-sailfish-signed.zip /sdcard/
(Note that I first tried to sideload both this zip and the suaddon one, given that it didn't seem to work, I wiped everything out again and went with the adb push method)
And, finally, went back to the "Install" menu, selected the zip and launched the install process (without checking the "Verify signature checkbox").
I managed to restore the initial backup created with TWRP, the system booted normally. I then tried a LOS install again and got stuck into a boot loop again.
Problem
At the end of this process, when offered with a swipe gesture to reboot, there is a warning saying that no OS is installed. Swiping to reboot leads to the reboot loop described above.
Any idea on what I can do to fix this issue?
Huge thank you in advance!

Have you tried installing the latest stock ROM first? There may be an incompatibility with other parts of the 7.1.0 ROM, like the modem, etc.

post-mortem said:
Have you tried installing the latest stock ROM first? There may be an incompatibility with other parts of the 7.1.0 ROM, like the modem, etc.
Click to expand...
Click to collapse
I did not. But there were other issues as well (I used outdated version of adb and fastboot), I followed the instructions there (due to the stupid rule for new users, I can't post a direct link to it) old.reddit.com/r/LineageOS/comments/9h0aqy/cant_install_lineage15120180918_on_a_google_pixel/e6nbqg6/ and it worked

My phone stuck flashing TWRP

I have made an OTA update yesterday to my rooted phone by following the usual steps installing magisk to inactive slot etc.. The only difference from other updates I did before this one was from android 10 to android 11. The phone worked fine, until today I wanted to check if TWRP is working and as soon I booted to it now I can't get out. It keeps flashing the twrp loading screen on and off. When I connect my phone to my PC it shows up in ADB in recovery mode when I try "adb reboot" it still boot to recovery when I do "adb reboot bootloader" it goes to fastboot, but no matter what I try I cant boot to the phone system.
UPDATE: I tried to use the patch and method from this post https://forums.oneplus.com/threads/rooted-oxygenos-11-on-my-oneplus-7-pro.1408175/#post-22986849 by Raven6681 then my phone went to stock recovery and I used wipe cache then my phone rebooted and only show a black screen. Then realized it keeps rebooting then black screen then reboot etc..
UPDATE 2: I tried to follow the previous step but now the phone didn't go to the recovery options as before and seems to be only in black screen. Tried to load in recovery and managed to then I used reset phone settings, but still nothing.
UPDATE 3: I tried to use the unpatched boot image from the first update as maybe some of the magisk modules are causing this issue, I tried clear cache and reset system settings and still nothing changed.

Probably an encryption issue. As twrp doesn't support encryption in A11. I don't know what's causing the black screen. The best way out is using msmdownload tool, I believe.

CodeRida said:
I have made an OTA update yesterday to my rooted phone by following the usual steps installing magisk to inactive slot etc.. The only difference from other updates I did before this one was from android 10 to android 11. The phone worked fine, until today I wanted to check if TWRP is working and as soon I booted to it now I can't get out. It keeps flashing the twrp loading screen on and off. When I connect my phone to my PC it shows up in ADB in recovery mode when I try "adb reboot" it still boot to recovery when I do "adb reboot bootloader" it goes to fastboot, but no matter what I try I cant boot to the phone system.
UPDATE: I tried to use the patch and method from this post https://forums.oneplus.com/threads/rooted-oxygenos-11-on-my-oneplus-7-pro.1408175/#post-22986849 by Raven6681 then my phone went to stock recovery and I used wipe cache then my phone rebooted and only show a black screen. Then realized it keeps rebooting then black screen then reboot etc..
UPDATE 2: I tried to follow the previous step but now the phone didn't go to the recovery options as before and seems to be only in black screen. Tried to load in recovery and managed to then I used reset phone settings, but still nothing.
UPDATE 3: I tried to use the unpatched boot image from the first update as maybe some of the magisk modules are causing this issue, I tried clear cache and reset system settings and still nothing changed.
Click to expand...
Click to collapse
in that case reflash twrp,root and the os you were using(in the order you did it the first time and, when you get your next ota update
extract it and edit to remove code which makes it look for stock recovery
select all the decompressed files and compress to ota zip file again
then in update area choose local update and use the file you just edited

TWRP crashing, stuck in recovery bootloop

For the last couple years I've been following this process to retain root using the TWRP A/B Retention Script and installing Magisk to the inactive slot after OTA and everything been fine and dandy. However, after the last time I performed this process Magisk would immediately crash when I tried to launch its app. Upon investigating I noticed that the file it downloaded for flashing was suspiciously small, so I suspect it flashed a corrupted file. I had already successfully rebooted my phone several times after the OTA, so I figured it was just Magisk that got corrupted and TWRP must be fine. I recently tried to reboot into recovery and discovered that TWRP is broken too. My phone briefly flashes the TWRP logo before the screen goes black and it tries to reboot into recovery again.
I've been able to get into fastboot by simultaneously holding down the power button and both volume buttons. However, none of the options in fastboot actually get my anywhere. Choosing start, recovery mode, or power off just get me back into the TWRP bootloop, and restart bootloader obviously just keeps me in fastboot.
I assume I need to reflash TWRP and Magisk, but I'm not sure how to go about that. Can someone point me in the right direction? Thanks.

This is how I proceeded:
Downloaded the latest TWRP image (twrp-3.6.2_11-0-guacamole.img) from here: https://dl.twrp.me/guacamole/
Verified the md5sum to ensure the download wasn't corrupted.
fastboot boot twrp-3.6.2_11-0-guacamole.img
In TWRP, Advanced > Flash Current TWRP
Now I have a working recovery, but I still can't boot into my system. When I go to Reboot > System in TWRP it just boots back into recovery.

I enabled MTP in TWRP and copied off all the data I cared about, then used the "Flash Factory Images" option in the TOOL ALL IN ONE to flash 9.5.13-GM21AA-OnePlus7ProOxygen_21.O.16_OTA_016_all_1908281716_b2bb5-FASTBOOT.zip. I tried it without checking the box to erase everything, hoping I could keep my data, but that didn't work. With that box checked though I was able to boot again, but I cannot turn on WiFi for some reason. I'm hoping the OTA will fix that issue. Does anyone know how to get WiFi working again or why it may have stopped working?

altayh said:
I cannot turn on WiFi for some reason. I'm hoping the OTA will fix that issue.
Click to expand...
Click to collapse
Fortunately enough the first OTA did indeed solve the WiFi issue. Now I've applied all of the OTAs and finally have my phone in a proper working state again.