Recovery bootloop...does anyone know which file to flash factory recovery? - Google Pixel Questions & Answers

On the August update. Trying to flash the Sep OTA and I can't boot recovery. It tries but then the phone just reboots. I want to try to flash the recovery but don't know which file it is in the factory image in Android 9. Does anyone know?

I don't know, but it would probably be faster to just flash the full factory image. Keep in mind that you should remove the "-w" option, if you want to save your data.

Related

Recovery not starting

Hi,
I wanted to flash the just released lollipop image so I unlocked my phone and updated TWRP from 2.8.0.1 to 2.8.1.0. Then I started Recovery and it was doing some werid thing in a list (was too fast), then rebooted. Recovery came up again (only the image of TWRP) and a restart again. Since then always when I try to go into recovery the starting image will show up, after 2-3 secs it gets black for half a second, then the image will show up again. This is a permanent loop. I flashed back to the old recovery but nnothing, still the same (and this one worked before!).
Hopefully someone of you knows whats wrong.
Thanks,
S3cret
reflash twrp recovery. but to correct you on your mistake before you do it, factory imgs are not flashable via any recovery, you can only flash them via fastboot.
I reflashed recovery several times now. I just thought being on the latest recovery version would be good. I know how to flash the lollipop image via fastboot, but I still need recovery for root.
I locked and unlocked the bootloader again and the same happened. Recovery started, doing some weird things and then the loop again.
Edit: Ok, I fixed it, somehow, I dont rly know how...
TWRP only starts after flashing it on my device. After a reboot, it doesn't work.
vercety974 said:
TWRP only starts after flashing it on my device. After a reboot, it doesn't work.
Click to expand...
Click to collapse
exactly the same here
Yup, dead Android with red warning triangle appears...
My stock recovery is broken after fastbooting the latest 5 image. Shows a red triangle above the laying down android.
How are we supposed to fix this?
Moreover, I've just reflashed the entire rom, and can't access the stock recovery. But the stock recovery seems to work beacause I can to factory reset via the settings menu, backup and restore.... Maybe it is the new security policy from google, to avoid that a thief make a factory reset directly from the recovery ?
So we can't navigate in the stock recovery anymore ?
Highway 55 said:
After fastboot flashing the .img files you need to (WITHOUT REBOOTING) flash custom recovery, TWRP etc... After that from the bootloader reboot into TWRP or whatever. When your in the custom recovery you need to adb push a permissive stock kernel or custom kernel as well as suspersu.zip. Again, without rebooting into the system, flash the kernel first then supersu. Now you can reboot into the system. ?
Click to expand...
Click to collapse
vercety974 said:
Moreover, I've just reflashed the entire rom, and can't access the stock recovery. But the stock recovery seems to work beacause I can to factory reset via the settings menu, backup and restore.... Maybe it is the new security policy from google, to avoid that a thief make a factory reset directly from the recovery ?
So we can't navigate in the stock recovery anymore ?
Click to expand...
Click to collapse
Yes I think it does have to do with the new selinux security stuff. I don't know the specifics. Maybe you want to refer to this thread. http://forum.xda-developers.com/showthread.php?p=56538538 @rootSU knows far more than I do. [emoji6]
Highway 55 said:
Yes I think it does have to do with the new selinux security stuff. I don't know the specifics. Maybe you want to refer to this thread. http://forum.xda-developers.com/showthread.php?p=56538538 @rootSU knows far more than I do. [emoji6]
Click to expand...
Click to collapse
It is exactly as he said in the post you linked.
Flash TWRP recovery and immidiately after run auto root. Then TWRP recovery will survive system boots.

Is This Bad

Tried to update to android l and forgot about twrp. My phone no boots into twrp and then into Android 4.4.4 Normally. After about 2 or 3 mins it boots back into recovery:crying:
What do I Do? XT1032, UK
Download the stock 4.4.4 ROM for your phone and manually flash each partition using fastboot or mfastboot commands.
Wouldnt it be easier to install stock recovery? If i am wrong... Please add my skype: samtenny
Try and flash stock recovery first. If that doesn't work, you may have to do a full wipe to get it to boot. If a full wipe doesn't work, try flashing a stock ROM.
I first suggested flashing a stock ROM because I prefer to use a solution that is most likely to work. I keep a back up of all my phone data so I don't care about losing any thing.

OTA update 2.33.709.6 failed at boot

I was trying to do the OTA update 2.33.709.6 in Taiwan.
At first, I flash the wrong stock recovery, so got the red exclamation mark screen.
Then, I flash the correct 5.0 stock recovery (thought so, as I was able to reboot my phone properly)
I did the OTA update, and got stock at reboot.
The screen just went black out after the white htc boot screen
I believe there are people having the same issues.
Please let me know how to fix it.
If possible, I would prefer not to flash ROM completely and keep my data.
I'm guess I need to flash the correct recovery and boot from OTA update 2.33.709.6.
Please share it with me if you have it.
Thanks.
I got my phone to work again, but have to lose some data
I relocked it and use flash RUU from SD card.
Basically, almost like factory reset
I did backup some data, but not all
If someone run into the same problem, this is not a perfect solution
Of course, please still share if you have better solutions without losing any data

Access BL and stock recovery but stuck in logo

good night. my brother has a moto g on the 5.1 version i guess, never rooted or custom recovery. after a 0% battery and no charge, the device stucked in logo of motorola
the first option is save the device, but data is very important to rescue, so it's priority to me.
the BL was locked, to try flash something i unlock it without loose data, i guess...
i can access BL, 41,1A version. tried fastboot and mfastboot to flash 5.0.2 retail rom and 5.1 stock with no success, boot loop of warning!!
can acess recovery, but can wipe data/factory reset, give a error and boot loop.
adb it's only sideload, and give error of footer, no install any of any file.
on adb apply update from sdcard i can view all my folders that i want to bkp, but how i get them? push and pull doesn't work.
I'm doing something wrong, just do not know what it is...
can someone help me? i read a lot of threads!!
i got this error when try wipe factory reset on stock recovery
blkdiscard on partition /dev/block/platform/msm_sdcc failed
and that's it. just wait like another brick in another falcon device.
tks 4 those who read and do nothing!!!

Switching from SuperSU to Magisk problems

Greetings,
I'm trying to move from SuperSu to Magisk, but have hit a problem with "fully" unrooting SuperSU.
If I tell it to restore the stock boot image the full unroot fails.
If I tell it not to restore the stock boot image, the full unroot "succeeds", but the stock boot image is not restored (obviously) and Magisk fails with an error about non-stock boot image.
If I re-install SuperSU the log shows it attempting to restore the factory boot image, failing and then going ahead with the already patched image.
Is there any way to install just the boot image (Odin, TWRP or ???) without wiping the entire phone?
Phone is a G920T with DPK1, I have the full DPK1 stock image but don't know how to install just the boot image.
Any help is greatly appreciated!

Categories

Resources