Pixel Custom Boot Procedure - Google Pixel Questions & Answers

Hi,
I have a pixel with the factory software bootloop issues.
I have been able to boot into the original os (5% success rate) by using various OTA images.
Been trying to install a custom ROM (tried benzo, RR, pixeldust) all without any success.
Twrp says flash successfully after ROM flash, I then flash twrp reboot recovery, flash gapps and vendor if needed and then boot.
Once it starts booting the OEM unlock message comes up and then google logo with a bootloop, phone restarts and back to OEM unlocked screen.
Can someone help me find out how to fix this or what I am doing wrong

Do it one step at a time. Flash only the custom ROM, then see if you can boot into it successfully. Then flash only Gapps, reboot. Keep doing this until you get the bootloop. Getting a logcat will help pinpoint where the error lies.
Have you tried flashing the latest full factory image? There is no good reason you shouldn't be able to boot into that.

Just tried flashing latest Factory image for sailfish.
Booted into recovery done a full wipe, factory reset and data wipe.
Booted into bootloader
Unlocked OEM_critical
Ran the script in factory zip
Completed with no issues
Boot screen with unlocked warning
Google sign (spelled GOOGLE)
Another google sign (Colourful "G")
Bootloop to OEM recovery
I am also unable to get the boot logcat, not sure what I am doing wrong

For sailfish, you shouldn't need to mess with the critical partitions. I have no idea what happens if you do unlock them, or if it's dangerous to relock them. fastboot flashing unlock should be all you need to unlock the bootloader.
You did make sure you're running the latest versions of adb and fastboot?

I am currently downloading the lastest android SDK toolkit to make sure adb and fastboot are the latest.
I used the
Code:
fastboot OEM unlock
and
Code:
fastboot OEM unlock_critical
I might try to use the
Code:
fastboot flashing unlock
and see if that does anything.

Updated ADB and fastboot.
Locked and unlocked bootloader using various methods, but phone still bootloops after flashing factory image (9.0.0 (PPR2.181005.003, Oct 2018))

Is there any other suggestions on how to fix the boot

Try to get a logcat of the initial boot, so errors can be identified.

How do i do that?
ADB logcat does not work

Related

[Q] Help flashing a rom

I've been trying to flash CM10.1 to my htc one x.
my phone is unlocked, s-off, supercid, rooted, everything..
I put the cm10.zip on my sdcard.
I wiped my phone (cache,delvik,system [not sure if i should wipe more than this? idk... this was all i saw on a few threads])
I flash the cm10.zip to my phone.
I extracted the boot.img from cm10.zip to my adb/fastboot folder
I reboot into bootloader and attempt to fastboot flash the boot.img to my phone ** (I think this is where the problem is but idk..)
I reboot my phone and i'm stuck at the cm10 loading screen.
Help?
I think my problem might be when I'm trying to fastboot the boot.img on my phone... When I attempt to see adb devices (while I'm in bootloader) I get none... I would always have to load into android before adb would recognize my device then boot into bootloader and do anything (it always worked in the past so i never really cared..) but with a custom rom I'm unable to boot into android so idk any suggestions? would this be the problem? it says it successfully flashes it but i'm having doubts... as it shows no connected devices. can I flash the boot.img to my phone before i flash the rom?
obg8 said:
I've been trying to flash CM10.1 to my htc one x.
my phone is unlocked, s-off, supercid, rooted, everything..
I put the cm10.zip on my sdcard.
I wiped my phone (cache,delvik,system [not sure if i should wipe more than this? idk... this was all i saw on a few threads])
I flash the cm10.zip to my phone.
I extracted the boot.img from cm10.zip to my adb/fastboot folder
I reboot into bootloader and attempt to fastboot flash the boot.img to my phone ** (I think this is where the problem is but idk..)
I reboot my phone and i'm stuck at the cm10 loading screen.
Help?
I think my problem might be when I'm trying to fastboot the boot.img on my phone... When I attempt to see adb devices (while I'm in bootloader) I get none... I would always have to load into android before adb would recognize my device then boot into bootloader and do anything (it always worked in the past so i never really cared..) but with a custom rom I'm unable to boot into android so idk any suggestions? would this be the problem? it says it successfully flashes it but i'm having doubts... as it shows no connected devices. can I flash the boot.img to my phone before i flash the rom?
Click to expand...
Click to collapse
If you are s-off you shouldn't need to flash the kernel seperately.. However use "fastboot devices" instead of "adb devices". When you are connected to a computer via USB it should indicate that on the bootloader.
Before I was s-off I'd flash the rom then return to the bootloader directly and flash the kernel before attempting to boot for the first time.
The post above mine is correct. If you are s-off you don't have to flash the boot.img. Going by what you posted it doesn't look like you wiped your data in recovery, which is something you have to wipe when flashing a new ROM. That's probably why it didn't boot properly. Try again doing a full wipe/factory reset from recovery.
Sent from my One X using Tapatalk 2

Stuck on Google splash screen after flash of rom.

After about a month of my phone rebooting itself or freezing up on me, I decided to flash a new rom. I made sure I had the most recent TWRP v2.8.7.1, wiped my cache and did a factory wipe. I attempted to flash BlissPop v3.9 and it failed stating, "This package supports booloader (s): HHZ12h; this device has bootloader HHZ11d.
It rebooted and now just sits on the Google splash screen. I can turn it off and manually get into the bootloader screen and TWRP.
How will I be able to download another rom from my computer and put it onto my phone? Please be nice, I really suck at adb. I can I access my phones memory while its in Recovery mode?
And no, I was a dumbass and forgot to back up before I attempted to flash the rom.
abd push (drag desired rom here) /sdcard
After that boot into recovery and flash it. If you can't get to the phone that way then download the factory image from google and fastboot flash, or alternatively download the twrp image and fastboot boot (twrp img) again, just drag the file into the command prompt. If you boot into twrp, or just flash it, you can then push the rom.
Just flash the newer bootloader
Sent from my Nexus 5 using Tapatalk

Can't install TWRP?

Maybe it's me not understanding what's new, I've "rooted" quite a few phones going back to the OG Droid - Motorola, Samsung, HTC. Never had any significant issue following directions and getting it done. Maybe things have changed over time. OG Pixel, 128GB, with sailfish-opr3.170623.008 (8.0.0). Auto-update disabled, USB debugging enabled, bootloader unlocked.
Setup: twrp-3.2.1-2-sailfish.img in platform-tools with adb and fastboot (latest versions). twrp-pixel-installer-sailfish-3.2.1-2.zip and Magisk-v16.0.zip at root of "Pixel/Internal Shared Storage". I also extracted a fresh boot.img from a factory image.
Just to make sure I'm starting fresh:
Code:
adb reboot bootloader
fastboot flash boot boot.img
fastboot --slot other flash boot boot.img
So far so good.
Code:
fastboot boot twrp-3.2.1-2-sailfish.img
TWRP comes up, I give it my PIN, it says decrypt OK, I tell it to install twrp-pixel-installer-sailfish-3.2.1-2.zip. Install seems fine, no errors reported. Back up a couple of levels, and "reboot recovery." It tries, eventually goes to a black screen for a few seconds, then does another reboot to system. No TWRP. Am I wrong in thinking I should be in TWRP at this point?
I can do the above, but flash Magisk-v16.0.zip instead, and I do end up with root, so that works. Just no way to get to TWRP except by fastbooting an external image.
I've also tried installing VerifiedBootSigner-v8.zip after installing twrp.zip, but that fails at the end with an "unable to verify..." or similar message. I'm not sure if that's supposed to be required or not currently, the TWRP install instructions don't mention it, but other guides do.
What am I doing wrong?
All I've ever done was boot to fastboot, adb boot <path-to-twrp>.img, and flash twrp. No need to use the boot signer anymore.
Sent from my Pixel using Tapatalk
Well, I can only guess that twrp-pixel-installer-sailfish-3.2.1-2.zip isn't compatible with the boot image in sailfish-opr3.170623.008.
I installed sailfish-opm1.171019.021-factory-68d3b69a.zip, then the twrp (and Majesk) install worked, just as expected.

Pixel 2 Magisk Bug won't take pin

Pixel 2 XL is soft bricked at the moment and I can't for the life of me think of what I need to do to recover it. I unlocked my bootloader and rooted when I switched to Pie, (I saw people we're already able to use Android pay on a rooted device again and I just couldn't help myself.) I installed twrp accidentally tried to flash TWRP not realizing I needed to temporary boot it and pushing the zip over erasing the recovery I proceeded to just fastboot it and carry on with the normal procedure with my phone. after getting Magisk installed I had my phone all set up until the next time I turned it on and back off again It said I forgot my PIN which I know I didn't I think this was because a glitch with smartlock I just setup so I go to my recovery and wipe the Dalvik cache, cache, Internal storage, and data and low and behold my phone bootloops never making past the final stage before it gets to the lockscreen. I go to Fastboot screen on my phone and my mac can't list my phone as a device in adb and now I am having issues getting back into recovery which I think might be because I am on the stock kernel my Fastboot screen on my phone says Product Name - Taimen, Variant - MSM USF:SAMSUNG(64gig) DDR:SAMSUNG, Bootloader version - TM220j, Baseband version - g899800253-1805232234, my Serial number, Serure boot - Yes, Device status - Unlocked, Vart console - Disabled, HW version - rev_10
I can't get it to stop bootlooping and just turn off.
bump
xda Zed said:
bump
Click to expand...
Click to collapse
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.
robocuff said:
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.
Click to expand...
Click to collapse
I stopped my endless bootloop! Now it says my device is corrupt and cannot be trusted and may not work properly when I tried to start it I couldn't get past the google screen. When I plug it into charge now it doesn't automatically going into a bootloop that can only be stoped by going into the fastboot mode or running out of battery, but the the charging symbol on the screen won't go away. I might have wiped system when I was in TWRP when I couldn't boot back after the first wipe. And I accidentally tried fastbooting Telstra img first. Anyway to get past this white Google screen? Also when I trey to go to recovery now it's the android laying on it's back with a red triangle and it says no command. Should I execute the flash-all script?
Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now
xda Zed said:
Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now
Click to expand...
Click to collapse
Glad to hear you got it working again. As for the recovery screen that say no command, that't the way it works with the stock recovery. When you see that screen, press and hold power and volume up. That will get you into recovery. If you happen to try rooting again and get stuck in a bootloop or some such thing, just flash the stock boot image.. That should get you going again.

Phone boots into fastboot, system files corrupted

Hi! My old phone is booting into fastboot mode, when I try to boot normally I get a black screen, the "Power off" button appears when I hold the power button. The bootloader is not unlocked and the phone was never rooted. Wiping the user partition does not help. It is visible in fastboot mode and I can enter stock recovery, though trying to adb sideload a stock rom returns an error (footer is wrong; signature verification failed). Trying to fastboot boot twrp or recovery.img doesn't work either. I've ran out of ideas, what should I do to get this phone to work?
Try flashing the stock ROM with fastboot. I'm pretty sure ADB doesn't let you flash onto your phone because using your phone with ADB means that it's still powered on - which can cause some issues. You can also try and unlock your bootloader through fastboot, and then flash a recovery and custom ROM.
Both failed. I attached the errors I recieved.
crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try "fastboot bootloader unlock", maybe. Also: Is there a flashall.bat in the stock ROM folder? If there is: Connect your device while in fastboot, and double-click it.
crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try this maybe. I know you can't wipe through the stock ROM, so, try the command: "fastboot -w". That'll wipe everything off the device.
[INDEX][Osprey][Merlin] Moto G Factory Firmware Images
Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own. Moto G (3rd Gen) Factory Firmware Images - Provided by Firmware TEAM - Please report broken links. New Mirrors welcome...
forum.xda-developers.com
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
crepper4454 said:
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
Click to expand...
Click to collapse
Try this: https://forum.xda-developers.com/t/guide-osprey-fastboot-flashing-factory-firmware-images.3187750/
It says there that the "preflash validation failed" error occurs when the firmware being flashed is older than the one already installed. I will try downloading a newer version and flashing it. Will update here.
Update: I have dowloaded a newer rom and tried to flash it. This time got different errors (picture attached, this went for every sparsechunk). I think I know the reason but I do not know how to solve it. This might not be the exact stock rom of this phone so I cannot flash it with a locked bootloader. Could someone help me finding the correct rom or suggest a different solution?
Yooooo. I have the Moto e5 Cruise and so does my wife. We bought them in 2018 from Cricket and last night hers went to emmc failure, also known scientifically as 'no worky' mode.
The phone would only load in fastboot and had tried to use my Moto RSD tool to reflash but the phone would not detect in anything but fastboot mode.. Here's where it gets interesting....
There is a piece of software called the Lenovo (which now owns Moto) Rescue and Smart Assistant that can reflash your phone back to factory, no matter your sub-variant (cricket, metro, etc). Without having a fresh backup on hand, you're going to be beholden to the last cloud sync or manual backup you have because all data will be wiped in the below process.
BTW: Just run the assistant as it seems to be the easiest 'back-to-stock/working' tool I can find. Going to fastboot alone yielded weird errors since i didn't have the unlock code for the 'fastboot oem unlock [code goes here]' command.
**RESTORATION PROCESS**
This will apply to multiple Lenovo/Moto Mobility devices. Unknown at this time how many have been impacted by this seemingly pre-planned failure on Lenovo's part.
If your phone is stuck in fastboot mode where MTK download mode does not load, nor does adb, follow these simple steps:
(NOTE: BACKUP YOUR FILES IF POSSIBLE)
1. Click the link above to be directed to the Lenovo software download page and run the installer on your PC (Sorry Mac users :'().
2. The software, once installed, will require you to sign up for OR link a google, fb, g+, etc account to it for purposes of creating a Lenovo ID. Once signed in, click on 'Rescue Now'.
3. With your phone in fastboot mode, allow the software to download the firmware for your phone.
4. Once the firmware has finished downloading and validating, click on 'Rescue Now' once again. Your phone will begin the reflashing process.
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
crepper4454 said:
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
Click to expand...
Click to collapse
No problemo! Glad it worked!

Categories

Resources