Question (Fixed)Messed up my Pixel 6 Pro - Google Pixel 6 Pro

I installed Magisk canary, I was on latest open beta, patched boot image, flashed, booted fine, tried to install the busybox that smartpack kernel asks and after installing, I rebooted and infinite bootloop. It does not let me enter fastboot mode, I tried power plus volume down, volume up and won't get on fastboot, my bootloader is unlocked, what can I do?
*Holding power plus volume down for 2 minutes straight got me to fastboot, will see how this goes*
Appreciate any help

It shows Google logo and after a minute restarts back to the bootloader unlocked screen, flashed back original boot img and tried the patched one, update, using android flash tool it got fixed, had to factory reset, at least I have a backup made few hours ago

Related

Robin on Nougat Won't Boot After Flashing TWRP

I just upgraded my rooted and bootloader unlocked Robin to Nougat last night by installing the official upgrade files from the Razer Community forum. I've tried installing TWRP several times through fastboot, and each time I can get the phone into recovery, but the phone will never boot into the system. It hangs on the black "Nextbit by Robin" screen, and never goes past it. If I turn off the phone by holding down the power and volume down buttons, and then turn it back on, it still won't get past that screen. I can always get into TWRP, though, but no matter what I do, the phone won't boot. I've been using TWRP 3.1.0. Is there a different version that's required for Nougat?
Saaber said:
I just upgraded my rooted and bootloader unlocked Robin to Nougat last night by installing the official upgrade files from the Razer Community forum. I've tried installing TWRP several times through fastboot, and each time I can get the phone into recovery, but the phone will never boot into the system. It hangs on the black "Nextbit by Robin" screen, and never goes past it. If I turn off the phone by holding down the power and volume down buttons, and then turn it back on, it still won't get past that screen. I can always get into TWRP, though, but no matter what I do, the phone won't boot. I've been using TWRP 3.1.0. Is there a different version that's required for Nougat?
Click to expand...
Click to collapse
My guess is you messed up the boot.img, or worse you corrupted some partition. If it's the boot.img, go get the latest factory image, unzip it, and move the file 'boot.Img' onto where your adb and fastboot files are located. Then go into fastboot on your Robin, and run this command on your PC:
Fastboot flash boot boot.img
If you corrupted something, you basically need to go into fastboot and use the flash-all.bat in the already unzipped Robin_nougat_88 folder to bring your phone back bone stock.
Hope that helped
Had this issue with my phone at first, but eventually just fixed it anyway by flashing the decrypted boot.img.
I ended up fixing it the same way you did. No matter how many times I took it back to stock by flashing the files in the Robin_nougat_88 folder and then flashing TWRP, no matter which version of TWRP I used, it would never boot. I finally flashed TWRP, then booted back into recovery, wiped the phone, loaded and flashed the decrypted boot image and SuperSU, and then the phone booted fine. I should have just done that in the first place since it was always my intention to unencrpyt it and rooted it again, anyway.

Updated Android O stuck on G boot screen

Hey all,
So I updated my pixel xl to Android O, and then used the modified TWRP to flash Super Su, SUhide. The phone booted up and everything was perfect. It was a little sluggish so I decided to do a full factory reset... again, phone reset, booted perfectly. I then restored all my apps from the google play store cloud... phone was functioning fine.
I went to reboot the phone after a while... and now the phone is stuck on the G logo after the bouncing dots... and just continues to load.
It's been like that for over 20 minutes.
Is this normal? Anyway I can fix this?
Thanks!
8.0.0 rooting nightmare
gaw54 said:
Hey all,
So I updated my pixel xl to Android O, and then used the modified TWRP to flash Super Su, SUhide. The phone booted up and everything was perfect. It was a little sluggish so I decided to do a full factory reset... again, phone reset, booted perfectly. I then restored all my apps from the google play store cloud... phone was functioning fine.
I went to reboot the phone after a while... and now the phone is stuck on the G logo after the bouncing dots... and just continues to load.
It's been like that for over 20 minutes.
Is this normal? Anyway I can fix this?
Thanks!
Click to expand...
Click to collapse
I have the same exact issue after following the exact process described above. After a weekend of frustration, I was thrilled to see this post, but then bummed there are no suggestions. There is no way I can get it back to recovery, no matter what power/volume combination I try. The phone is not detectable by ADB either, so unless a kind soul has a suggestion, there seems to be nothing to do except let the battery die and hope.
Umm boot into bootloader and flash stock boot.img and system.img?
george241312 said:
Umm boot into bootloader and flash stock boot.img and system.img?
Click to expand...
Click to collapse
I would love to do that, but how is it possible if there is no power or volume button combination that can get me off of the Google boot screen and into bootloader?
Have you tried Power + volume down ? It'll turn off after release power button only. That or let the battery die and when you try to plug it up next time leave vol down pressed.
george241312 said:
Have you tried Power + volume down ? It'll turn off after release power button only. That or let the battery die and when you try to plug it up next time leave vol down pressed.
Click to expand...
Click to collapse
I have tried that, thank you. I will let battery die and do the Volume Down method you suggest, and report back.
edjanx said:
I have tried that, thank you. I will let battery die and do the Volume Down method you suggest, and report back.
Click to expand...
Click to collapse
That did the trick. Back to stock 8.0.0, and hoping to find a stable root method that doesn't hang-up on the first reboot. Thanks for the help!
First of all. Hold the power button for about 20 secs and the phone will reboot.
Hold vol - and you are straight to bootloader.
Second flash full factory to both slots.
And third stop using the - w solution when you are coming from another rom or a different stock version. We had this problems on other forums and it was every time - w or not flashing both slots. I know for many people there will be no problem but some apps are just misbehaving when you do so. And they are causing reboots and bootloops.
mikaole said:
First of all. Hold the power button for about 20 secs and the phone will reboot.
Hold vol - and you are straight to bootloader.
Second flash full factory to both slots.
And third stop using the - w solution when you are coming from another rom or a different stock version. We had this problems on other forums and it was every time - w or not flashing both slots. I know for many people there will be no problem but some apps are just misbehaving when you do so. And they are causing reboots and bootloops.
Click to expand...
Click to collapse
OK, thank you! I am not familiar with the -w method. This is a new Pixel XL I received from Google to replace a nexus 6p with a bootloader issue. I made the mistake of not attempting this before it updated from 7.1.2 to 8.0.0, or it may have been a different story.
So I have the the phone restored to 8.0.0 and was going to attempt root. But I didn't realize there are two slots to flash. I simply ran flash-all.bat and the phone came back up. So I guess I'd have to move the Sept security stock image over to the phone along with the SU, SU Config (which may not be needed if on 8.0.0?), and Su Hide. Then I boot up TWRP 3.1.1 and flash stock image to both slots, reboot, then get back into TWRP and run the SU, then SU Hide on *both* slots?
Thanks!
Janx
Run flashall.bat on the slot you are now in. Reboot to system
Back to bootloader. Switch slots through fastboot
fastboot --set-active=_b
fasboot reboot bootloader
Now you should be on the other slot
Flashall.bat
Reboot to system
Back to bootloader
fastboot boot twrp.img (latest)
In twrp put latest su or in my case magisk 14.2, twrp zip on device.
If you use su just flash it
If you use magisk. Flash magisk, flash twrp.zip and magisk again. With magisk twrp will stick.
Reboot and you are good to go.
If you want a kernel you have to flash twrp and magisk after again.
mikaole said:
Run flashall.bat on the slot you are now in. Reboot to system
Back to bootloader. Switch slots through fastboot
<SNIP>
If you want a kernel you have to flash twrp and magisk after again.
Click to expand...
Click to collapse
Thank you! I will be able to perform this sequence in a few hours and will report back. :good:
Ok. Will be in bed than. If you have any problems give me a PM and we can do it together via hangouts.
Update: I successfully flashed A & B, got to the step where I flash Magisk 14.2. It finished unmounting partitions, but when updating partition details fails, "failed to mount '/system' (device or resource busy)...done
It said successfully installed, so I flashed twrp to the boot image, flashed magisk again, and it is now rebooting endlessly. Wrong place to flash the twrp image I'm guessing?
EDIT: Just noticed your message, good night - thanks again. I'm working through it and will take you up on your kind offer should I not find success.
I did a 'flash-all.sh' on both A and B again, copying over my old phone, then will attempt to gain root by booting into TWRP 3.1.1, installing "SR3-SuperSU-v2.82-SR3-20170813133244", reboot bootloader, go into TWRP again and then install "UPDATE-suhide-v1.08-20170815171034"
EDIT #2: EDIT #2: Stable root achieved using newer versions of files "SR5-SuperSU-v2.82-SR5-20171001224502" & after booting, applying "UPDATE-suhide-v1.09-20171001222116". So far it has survived several reboots, so I'm hoping it's all good now.

Did I brick my Pixel 3 XL?

Brand new Pixel 3 XL
Enabled OEM Unlocking
Enabled USB Debugging
Unlocked Bootloader
Copied twrp-pixel3-installer-crosshatch-3.2.3-5.zip to my phone
Rebooted into bootloader
fastboot boot c:\...\twrp-3.3.1-3-crosshatch.img
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Wiped system/data/cache
Flashed AOSiP-9.0-Official-crosshatch-20190722.zip
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Rebooted
When the system rebooted, it brought me into bootloader. I selected Start and then it rebooted into Bootloader again. I then figured something went wrong with installing AOSiP, so I booted into recovery.... from TWRP, I wiped system/data/cache/storage/data in attempt to start over and flash the ROM again. This time, I rebooted the system after the wipe and upon rebooting, the phone never turned back on. Pressing and holding the power button for long periods of time doesn't seem to do anything. Any ideas where I went wrong and more importantly if I bricked my phone? Thx.
EDIT: Tried holding volume down and power button for 10+ seconds and it booted into bootloader. Not really sure where to go from here.
EDIT 2: I tried booting into Recovery. It went back to the black screen. I had to use volume down and power button to get back into bootloader. Fastboot devices does detect the phone. I'm guessing this is a softbrick and I can follow the softbrick tutorial from here? Either way, it'd be nice to know where I took a wrong turn if anybody knows. Thanks.
EDIT 3: It may also be worth mentioning that I confirmed all the md5sum's before flashing the zips or booting the img.
thex2 said:
Brand new Pixel 3 XL
Enabled OEM Unlocking
Enabled USB Debugging
Unlocked Bootloader
Copied twrp-pixel3-installer-crosshatch-3.2.3-5.zip to my phone
Rebooted into bootloader
fastboot boot c:\...\twrp-3.3.1-3-crosshatch.img
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Wiped system/data/cache
Flashed AOSiP-9.0-Official-crosshatch-20190722.zip
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Rebooted
When the system rebooted, it brought me into bootloader. I selected Start and then it rebooted into Bootloader again. I then figured something went wrong with installing AOSiP, so I booted into recovery.... from TWRP, I wiped system/data/cache/storage/data in attempt to start over and flash the ROM again. This time, I rebooted the system after the wipe and upon rebooting, the phone never turned back on. Pressing and holding the power button for long periods of time doesn't seem to do anything. Any ideas where I went wrong and more importantly if I bricked my phone? Thx.
EDIT: Tried holding volume down and power button for 10+ seconds and it booted into bootloader. Not really sure where to go from here.
EDIT 2: I tried booting into Recovery. It went back to the black screen. I had to use volume down and power button to get back into bootloader. Fastboot devices does detect the phone. I'm guessing this is a softbrick and I can follow the softbrick tutorial from here? Either way, it'd be nice to know where I took a wrong turn if anybody knows. Thanks.
EDIT 3: It may also be worth mentioning that I confirmed all the md5sum's before flashing the zips or booting the img.
Click to expand...
Click to collapse
Nevermind, @sliding_billy has the answer.
I
thex2 said:
Brand new Pixel 3 XL
Enabled OEM Unlocking
Enabled USB Debugging
Unlocked Bootloader
Copied twrp-pixel3-installer-crosshatch-3.2.3-5.zip to my phone
Rebooted into bootloader
fastboot boot c:\...\twrp-3.3.1-3-crosshatch.img
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Wiped system/data/cache
Flashed AOSiP-9.0-Official-crosshatch-20190722.zip
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Rebooted
When the system rebooted, it brought me into bootloader. I selected Start and then it rebooted into Bootloader again. I then figured something went wrong with installing AOSiP, so I booted into recovery.... from TWRP, I wiped system/data/cache/storage/data in attempt to start over and flash the ROM again. This time, I rebooted the system after the wipe and upon rebooting, the phone never turned back on. Pressing and holding the power button for long periods of time doesn't seem to do anything. Any ideas where I went wrong and more importantly if I bricked my phone? Thx.
EDIT: Tried holding volume down and power button for 10+ seconds and it booted into bootloader. Not really sure where to go from here.
EDIT 2: I tried booting into Recovery. It went back to the black screen. I had to use volume down and power button to get back into bootloader. Fastboot devices does detect the phone. I'm guessing this is a softbrick and I can follow the softbrick tutorial from here? Either way, it'd be nice to know where I took a wrong turn if anybody knows. Thanks.
EDIT 3: It may also be worth mentioning that I confirmed all the md5sum's before flashing the zips or booting the img.
Click to expand...
Click to collapse
If you can get to BL and fastboot devices is recognizing it, you are only soft bricked. Do a flash-all of the factory image. You will be starting over with the exception of OEM unlock and BL unlock. Once you are up and running, go back to BL, change slots and do the flash-all again. Of course, you will be setting up again but you should be clean. Be sure to use the last Android 9 factory image for flash-all if you are not intending to go to 10 yet. There is one rock solid custom ROM for 10 (Havoc). Take a read of the install instructions as it doesn't use TWRP (not available for 10 yet). It does need the flash-all of November factory image done to both slots, so if you are looking at that do it immediately IMO since you will have to wipe anyways.
If you wipe system in TWRP then you have to flash a ROM from there. That is why it went blank when you rebooted. You have nothing to boot up on.
ADB a stock file and start over...it's not bricked.
Thank you for the help guys. I will work on fixing the issue tonight. Also, thanks for the suggestion on the Havoc ROM, but I'm staying with Android 9 because of the menu navigation button at the bottom right of the older apps... https://www.androidpolice.com/2019/...utton-has-finally-been-retired-in-android-10/
thex2 said:
Thank you for the help guys. I will work on fixing the issue tonight. Also, thanks for the suggestion on the Havoc ROM, but I'm staying with Android 9 because of the menu navigation button at the bottom right of the older apps... https://www.androidpolice.com/2019/...utton-has-finally-been-retired-in-android-10/
Click to expand...
Click to collapse
Havoc also had pie builds if you wanted to try.

Need Help. Phone stuck on black screen on boot

I flashed nusantara project 2.6(android 11) on my redmi note 5 pro along with nikgapps. Everything was working fine on booting but I didn't like the launcher. I saw that nikgapps had an addon package for pixel launcher and thought i'll install that. So i booted into my recovery and flashed that and rebooted into my system. On booting, I get the boot animation which gets completed and the phone boots but instead of the lockscreen, i only see a black screen. On holding the power button I see three options: power off, reboot and emergency call.
So i thought maybe the launcher was not compatible and that reflashing the rom would fix it. But I'm not able to boot into my recovery with any key combo. I'm also not able to boot into fastboot either. So I can't even use the miflash tool to flash a fastboot miui rom.
When booted into the black screen, miflash does detect my device when i connect it but when i flash a fastboot rom, nothing happens. It says flashing for an extremely long time and my phone is still in the black screen itself
Let me know if you have any ideas which i can try to fix this
Fixed it by going into edl mode and using miflash tool

Unlocked bootloader - boot loop after trying to put stock firmware back on

My telephone keeps booting to fastboot after trying to update TWRP.
I am trying to restore the original ROM (apollo_eea_global_images_V12.5.12.0.RJDEUXM_20220208.0000.00_11.0_eea) and I can get the rom installed through fastboot but the phone enters a boot loop cycle. It starts up, vibrates shortly then reboots.
If i press volume up it goes into the original recovery menu. I have tried clearing everything and even entering safe mode but the phone will not boot.
Am i screwed?
Thanks in advance.
I installed the Pixel Experience recovery and side-loaded the zip and at least have a working OS.
I must be doing something wrong with the stock mi10t
Now i sided the miui zip and its working agian. I think i have misunderstood the procedure. I thought you only need to install the rom with flashboot and that was it.

Categories

Resources