HELP!!! Recovery and system wont boot - Google Pixel Questions & Answers

I just received my Pixel (not XL and not verizon version) that I bought from the Google Store and I tried loading TWRP on it. Fastboot works and I can fastboot into a TWRP recovery, however, whenever I try to flash another recovery with that recovery, the the message warning me to lock the bootloader pops up, then the phone very briefly goes to white screen with the google logo and instantly shuts off. Then it automatically repeats that process.. Am not sure what I did wrong (for example if I accidentally flashed the wrong variant to begin with?) but I also don't know how to fix it. I have tried all of the TWRP variants and nothing has worked. I also think the I was on 7.1.2.
I spent all night searching through all of the threads and could not find anyone who had a similar situation so any help is greatly appreciated and desperately needed.
Thank you in advance

SponsOne said:
I just received my Pixel (not XL and not verizon version) that I bought from the Google Store and I tried loading TWRP on it. Fastboot works and I can fastboot into a TWRP recovery, however, whenever I try to flash another recovery with that recovery, the the message warning me to lock the bootloader pops up, then the phone very briefly goes to white screen with the google logo and instantly shuts off. Then it automatically repeats that process.. Am not sure what I did wrong (for example if I accidentally flashed the wrong variant to begin with?) but I also don't know how to fix it. I have tried all of the TWRP variants and nothing has worked. I also think the I was on 7.1.2.
I spent all night searching through all of the threads and could not find anyone who had a similar situation so any help is greatly appreciated and desperately needed.
Thank you in advance
Click to expand...
Click to collapse
Try fastboot flashing 7.1.2 boot.img, then fastboot boot into TWRP, flash the attached twrp pixel installer, reboot to recovery from recovery , then flash supersu, then reboot. It will reboot a time or two if that is normal.

Tulsadiver said:
Try fastboot flashing 7.1.2 boot.img, then fastboot boot into TWRP, flash the attached twrp pixel installer, reboot to recovery from recovery , then flash supersu, then reboot. It will reboot a time or two if that is normal.
Click to expand...
Click to collapse
Thank you so much for your quick response.
Is this the version I use? I want to make sure I download the correct one: 7 .1.2 (N2G47O, May 2017)

SponsOne said:
Thank you so much for your quick response.
Is this the version I use? I want to make sure I download the correct one: 7 .1.2 (N2G47O, May 2017)
Click to expand...
Click to collapse
That should work though there should be June update.

p
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG]
Tulsadiver said:
That should work though there should be June update.
Click to expand...
Click to collapse
Thank you again for your help. I put the June version on instead of the previous and everything seems to be working. My only question is at the end of fastbooting the factory img, it said, "FAILED (remote: Partition table doesn't exist). Is that normal or something to be concerned about?
Here is a photo I took of it:

[/IMG]

SponsOne said:
[/IMG]
Click to expand...
Click to collapse
I don't know why the image doesn't seem to be uploading so here is a link to it:
https://drive.google.com/open?id=0B3fIceeoMIn8NC1XTUVTODNBT1k

Related

boot stuck at "fastboot menu" and "This build is for development purposes only."

boot stuck at "fastboot menu" and "This build is for development purposes only."
After flashing recovery , whatever how many time reboot it ,my phone stuck at "fastboot" menu.
When I click "recovery", Red information "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission." was flashing then back to menu again.
Any advise?
Thanks~~
flyingcowboy said:
After flashing recovery , whatever how many time reboot it ,my phone stuck at "fastboot" menu.
When I click "recovery", Red information "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission." was flashing then back to menu again.
Any advise?
Thanks~~
Click to expand...
Click to collapse
I think you need to unlock bootloader
gss93 said:
I think you need to unlock bootloader
Click to expand...
Click to collapse
Do you mean the pic below?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://drive.google.com/open?id=0B98TI8vzkIzCUkJPNEV1TGlRZ3M
flyingcowboy said:
Do you mean the pic below?
https://drive.google.com/open?id=0B98TI8vzkIzCUkJPNEV1TGlRZ3M
Click to expand...
Click to collapse
Never mind it looks like it is already unlocked based off of the picture. Have you flashed/reflashed TWRP or CWM?
gss93 said:
Never mind it looks like it is already unlocked based off of the picture. Have you flashed/reflashed TWRP or CWM?
Click to expand...
Click to collapse
Yes I tried them both still same
flyingcowboy said:
Yes I tried them both still same
Click to expand...
Click to collapse
Sorry someone more experienced will probably have to help you. I did loose recovery once i had to flash a couple of different times. I tried locking and unlocking boot loader then it eventually worked. What command are you using to flash TWRP/CWM fastboot flash recovery (Name).img?
gss93 said:
Sorry someone more experienced will probably have to help you. I did loose recovery once i had to flash a couple of different times. I tried locking and unlocking boot loader then it eventually worked. What command are you using to flash TWRP/CWM fastboot flash recovery (Name).img?
Click to expand...
Click to collapse
fastboot flash recovery recovery.img
anyway still thanks a lot~~:good:
flyingcowboy said:
fastboot flash recovery recovery.img
anyway still thanks a lot~~:good:
Click to expand...
Click to collapse
No problem. Which one are you flashing twrp or cwm? Maybe changing the recovery/ version of recovery may help. I'm not sure but perhaps certain versions are not compatible with your phone maybe try googling it.

Help Moto G stoping in "Warning BootLoader"

Hello guys! I'm on a G 2015 bike to find a way around it. Good tried the procedures without unlocking the bootloader, but without success! Then I went and I was able to unlock Bootloader and repeat the process to install Roo Stock. But to no avail as well. Does anyone have any tips for solving this problem?
I would guess it stops in bootloader because it doesn't like the rom you've flashed.
Did you flash TWRP?
Boot to TWRP and clean flash something else.
Else flash TWRP and then do that.
Hi there! I had the same problem, but the solution was just wait. It took a full 5 minutes to boot since the warning appeared, but it worked fine. Give it a try, wait 5 minutes (literally) and see what happens. If it still stuck, then try the solution above.
KrisM22 said:
I would guess it stops in bootloader because it doesn't like the rom you've flashed.
Did you flash TWRP?
Boot to TWRP and clean flash something else.
Else flash TWRP and then do that.
Click to expand...
Click to collapse
Hi. I tried to do the way you said it, but it did not work. Take a look at the picture
I follow this GUIDE for install
https://forum.xda-developers.com/moto-g/general/guide-custom-recovery-moto-g-xt1033-t2972905
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't think your bootloader is unlocked.
Have you unlocked your bootloader using the Motorola site? No other method will work.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
which recovery are you using - copy/paste full module name.
The bootloader has been unlocked by the motorola website! When I insert the cell phone, the message appears that the bootloader is unlocked.
Jdoria said:
The bootloader has been unlocked by the motorola website! When I insert the cell phone, the message appears that the bootloader is unlocked.
Click to expand...
Click to collapse
"when you insert the cell phone" into what?
EDITED POST FOR WINDOWS:
for windows I think type cmd in search bar, right click on cmd.exe and choose administrative (you may have to enter a password) and do everything in that window.
fastboot flash recovery twrp.img
but first tell me exactly which twrp you are using - one is bad.
Better than that just grab the latest from squid and use that. I know it's good.
When it flashes successfully, DO IT AGAIN - don't ask why, just do it - same command.
THEN boot to TWRP and backup your stock if you still have one.
Then and only then, wipe and flash whatever your heart desires.
@Jdoria Please attach the output of "fastboot getvar all"
@KrisM22 "sudo" wont do anything, this is WINDOWS, not Linux.
acejavelin said:
@Jdoria Please attach the output of "fastboot getvar all"
@KrisM22 "sudo" wont do anything, this is WINDOWS, not Linux.
Click to expand...
Click to collapse
Yeah I put a note at the bottom of that post for that. My bad.
Hi I ran cmd.exe in managed mode. Is there any method to format the data of the phone and install everything from scratch?
Jdoria said:
Hi I ran cmd.exe in managed mode. Is there any method to format the data of the phone and install everything from scratch?
Click to expand...
Click to collapse
You need to run it in administrative mode.

Bootloop issue

Hi, i've been using the Mi Mix 3 (chinese ver.) for the past few months as my main device and today i tried to install the Pixel Experience rom but it didn't go well.
I'm now stuck on a bootloop, all i get is a black screen that says "Mi" and "unlocked" at the bottom of the screen.
I can still access fastboot and twrp but i can't get anything to work with either, installing any rom through twrp gets me back to the bootloop and i can't get the chinese rom to install through fastboot.
I also tried to install back the chinese rom with MiFlash but everytime i'm prompted with this error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm not sure what to do at this point and could use some detailed help
here's a list of what i did btw:
- unlock the device with Mi Unlock
- install twrp with fastboot
- boot into twrp and installed pixel experience rom
hopefully i didn't make my phone a useless slab of glass and ceramic
Did you wipe data?
raven213 said:
Did you wipe data?
Click to expand...
Click to collapse
Yes pretty sure i did
Mel35 said:
Yes pretty sure i did
Click to expand...
Click to collapse
Wiping isn't enough, you need to format data in twrp to remove encryption
Mackay53 said:
Wiping isn't enough, you need to format data in twrp to remove encryption
Click to expand...
Click to collapse
done that and i'm still stuck on the same screen
i could use a step by step guide because i'm not sure what i could've messed up at this point
Mel35 said:
done that and i'm still stuck on the same screen
i could use a step by step guide because i'm not sure what i could've messed up at this point
Click to expand...
Click to collapse
Possibly using the wrong vendor, seems to be common in the PE thread
Mel35 said:
Hi, i've been using the Mi Mix 3 (chinese ver.) for the past few months as my main device and today i tried to install the Pixel Experience rom but it didn't go well.
I'm now stuck on a bootloop, all i get is a black screen that says "Mi" and "unlocked" at the bottom of the screen.
I can still access fastboot and twrp but i can't get anything to work with either, installing any rom through twrp gets me back to the bootloop and i can't get the chinese rom to install through fastboot.
I also tried to install back the chinese rom with MiFlash but everytime i'm prompted with this error:
I'm not sure what to do at this point and could use some detailed help
here's a list of what i did btw:
- unlock the device with Mi Unlock
- install twrp with fastboot
- boot into twrp and installed pixel experience rom
hopefully i didn't make my phone a useless slab of glass and ceramic
Click to expand...
Click to collapse
Did you flashed miui ROM before flashing PE stable rom 2 seems to be working

QUALCOMM Crashdump Mode on boot even after using MSM tool

So long story short: I was on Flamingo OS A13, got a crashdump mode all of the sudden, I tried flashing again without success. Then I used MSM tool to go back to OOS 11 and after completing, the device just shows the OnePlus logo, screen gets distorted (see image below) and goes off. I try turning it off and on using all the buttons, and I can access Fastboot mode and Recovery only without any problem. But when I try to boot normally, it crashes on the OP logo again and goes into crashdump mode. I tried every latest MSM tool (OOS9, OOS10, OOS11).
Not sure what else to do.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
for some reason I always get the same error after using msm tool.
try to boot to twrp recovery using all in one tool or any other way. then flash OOS 11 on both slots (don't forget to format data).
you should be fine. tell us if you managed to fix it by any way
Dark Fear said:
for some reason I always get the same error after using msm tool.
try to boot to twrp recovery using all in one tool or any other way. then flash OOS 11 on both slots (don't forget to format data).
you should be fine. tell us if you managed to fix it by any way
Click to expand...
Click to collapse
Thanks for your reply. Unfortunately I can't boot to twrp since MSM locks the bootloader and I can't unlock it unless I boot the device first, which is the problem.
Nimrodz91 said:
Thanks for your reply. Unfortunately I can't boot to twrp since MSM locks the bootloader and I can't unlock it unless I boot the device first, which is the problem.
Click to expand...
Click to collapse
can you use fastboot roms?
Dark Fear said:
can you use fastboot roms?
Click to expand...
Click to collapse
No, because bootloader is locked and I can't boot up first.
Nimrodz91 said:
No, because bootloader is locked and I can't boot up first.
Click to expand...
Click to collapse
Did find the solution. I have the same problem even the photo that you shared of the phone its the same with lines coming. The MSM tool does it all but again the phone goes black and i can just access Fastboot
abbasi89 said:
Did find the solution. I have the same problem even the photo that you shared of the phone its the same with lines coming. The MSM tool does it all but again the phone goes black and i can just access Fastboot
Click to expand...
Click to collapse
Unfortunately, no. After researching about the issue, I found that it's a hardware problem where the RAM or motherboard needs to be replaced. I ended up buying another OP7Pro and decided to get my hardbricked one fixed sometime later.

Question I cannot install twrp on to my galaxy a12

i tried to install twrp , root and degoogle my galaxy a12, i have no experience at all and nearly bricked my phone
i unlocked my bootloader, go into download mode, i tried flashing twrp 3.7.0 image i downloaded on the official website, it didn't work and everytime i reboot it got into download mode again
i flashed the stock rom again, go to the support thread of twrp on the galaxy 12 here, i did like the tutorial but i cannot flash the rom with the re partition and nand erase because odin will just froze and the progress bar wont appear
after that i tried flashing it like the post said. put the twrp image in the AP box, and the vbmeta.img.md5(i extracted the vbmeta.zip file since i cannot put the zip file into the box) into userdata box, then start, restarted the phone and after that it got the "An ERROR Has Occured While Updating Device Software" with the teal background, i freaked out but luckily i fixed it with the frp hijack software.
after that i'm just too scared to continue, does anyone know what i did wrong? my guess is that it's at the vbmeta file but the support post give that file only and i just extracted it and put the md5 file in the userdata box.
I assume that you flashed twrp recovery with vbmeta and you had One Ui 4.0 (Android 12) on stock. It's just that I had a similar thing when I flashed it on TWRP.
Note: WHEN YOU HAVE INSTALLED THE VBMETA AND TWRP FILE AND YOU ARE USING THE STOCK FIRMWARE THEN DO NOT LOGIN TO YOUR SAMSUNG ACCOUNT. YOUR PHONE WILL BE BLOCKED. AND WHEN TURNED ON, IT WILL PROVIDE THE FOLLOWING.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
lil_kyrick said:
I assume that you flashed twrp recovery with vbmeta and you had One Ui 4.0 (Android 12) on stock. It's just that I had a similar thing when I flashed it on TWRP.
Note: WHEN YOU HAVE INSTALLED THE VBMETA AND TWRP FILE AND YOU ARE USING THE STOCK FIRMWARE THEN DO NOT LOGIN TO YOUR SAMSUNG ACCOUNT. YOUR PHONE WILL BE BLOCKED. AND WHEN TURNED ON, IT WILL PROVIDE THE FOLLOWING.
View attachment 5789287
Click to expand...
Click to collapse
no, it is the android 11 version with the A127FXXU5AVC4 stock firmware (vietnam region) and no i didn't login to anything after unlocking bootloader, and the warning shows something like this image here
but without the 2 last line, instead it has a korean and japanese translation below that first 2 english lines
i think i messed up at the vbmeta part, i though my phone was hard bricked but i managed to fix it and flashed a the stock firmware again
Oh ****. So connect your phone to your computer and use the "Emegency Software Recovery" function in the Smart Switch program.
What was your mistake? Yes, the fact is that you have SM-A127F, and you set it for SM-125F. And you need to repair the device now, otherwise, contact the nearest service center. Here is a link to the guide you need for your device.
lil_kyrick said:
Oh ****. So connect your phone to your computer and use the "Emegency Software Recovery" function in the Smart Switch program.
What was your mistake? Yes, the fact is that you have SM-A127F, and you set it for SM-125F. And you need to repair the device now, otherwise, contact the nearest service center. Here is a link to the guide you need for your device.
Click to expand...
Click to collapse
ah i already fixed it myself with frp hijacker, thank you for your consideration
az_r08 said:
ah i already fixed it myself with frp hijacker, thank you for your consideration
Click to expand...
Click to collapse
Can you send a ss of the odin you are using and the settings?
What I assume is you need to use patched odin or you device is encrypted.

Categories

Resources