HELP - Google Pixel 5 Questions & Answers

i was on developer preview 3 android 12 and my phone will boot to the G of the splash screen and hangs there. i can get to factory recovery and run adb sideload and i can get to fastboot. MY BOOTLOADER IS LOCKED so im having no luck installing the factoty image. if anyone knows how i may be able to install software to end thus problem please post here and thanks

treIII said:
i was on developer preview 3 android 12 and my phone will boot to the G of the splash screen and hangs there. i can get to factory recovery and run adb sideload and i can get to fastboot. MY BOOTLOADER IS LOCKED so im having no luck installing the factoty image. if anyone knows how i may be able to install software to end thus problem please post here and thanks
Click to expand...
Click to collapse
Your best bet is to use the public beta and do the update OTA:
Android Beta Program
Android Beta Program allows you to enroll your Android device for beta releases.
www.google.com

svetius said:
Your best bet is to use the public beta and do the update OTA:
Android Beta Program
Android Beta Program allows you to enroll your Android device for beta releases.
www.google.com
Click to expand...
Click to collapse
the phone wont boot up so how do i get the public beta and what way do i flash it? is the public beta availoable for adb sideload or how do i install it considering the phone wont boot up?

treIII said:
the phone wont boot up so how do i get the public beta and what way do i flash it? is the public beta availoable for adb sideload or how do i install it considering the phone wont boot up?
Click to expand...
Click to collapse
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Follow the instructions and cross your fingers.
You may need to factory reset from the recovery.
As long as you can get to the recovery, you have a shot.
Beta 3 has been very stable for me.

I'm having the same issue! My cell service stopped working today and I decided to try restarting it and now it just hangs at the G. I've tried applying the OTA update but it still hangs. Is there away to mount the user partition so I can back my stuff up before trying a factory restore?

Related

[CUSTOM RECOVERY] TWRP Recovery

DISCLAIMER
We are not responsible for any damage, bootloop, bricked or broken tablets and Relationships.
Team @csolanol & @diegocr is back!!!
Notice
This recovery can't be flashed to the tablet meanwhile the bootloader is locked. We don't have any way to unlock it for now so you must launch it this way:
Code:
fastboot boot TWRP_Fire_2.8.7.0_adb.img
Edit: Project became stable. Got rid of the backlight error thanks to @diegocr.
Download
https://www.androidfilehost.com/?fid=24269982087018181
Update 2015-12-14
MTP working, if doesn't mount disable and re-enable
Don't use USB storage, not working
Update 2015-12-13
Added adb & USB storage mount USB storage not working
XDA:DevDB Information
[CUSTOM RECOVERY] TWRP Recovery, Tool/Utility for the Amazon Fire
Contributors
csolanol, diegocr
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2015-11-09
Created 2015-11-06
Last Updated 2015-12-14
Video: 2015 Fire: Booting TWRP, Rooting, Installing Gapps
Basic Directions
Download/Install Drivers
Verify Divers were installed Correctly
Download/Install ADB/Fastboot files
Test Fastboot commands
Download Twrp.img from link in post #1
Boot Custom Recovery with
Code:
fastboot boot TWRP_Fire_recovery.img
check root status with https://play.google.com/store/apps/details?id=com.jrummyapps.rootchecker
This is a temporary recovery, it must be booted with fastboot commands, every time want to use it.
What you can do with a Custom Recovery
Root Stock rom with SuperSu.zip
Install Google Apps Select Arm | 5.1 | pico version
Install Xposed Framwork
Backup Rom
Install Custom ROM
Install Stock Firmware (UnBrick)
...
I know this sounds stupid but cant you sign your images by getting the amazon api key or something?
Awesomeslayerg said:
I know this sounds stupid but cant you sign your images by getting the amazon api key or something?
Click to expand...
Click to collapse
I don't think there is anyway to do that which is why signed software is generally trust-able.
bullet25 said:
I don't think there is anyway to do that which is why signed software is generally trust-able.
Click to expand...
Click to collapse
Well i've seen people using lg sign tool or something to sign there images to flash thier images and make them bootable.
keep up the great work now we just gotta get custom rom installed
Can Flashify be used to boot into the recovery?
niphoet said:
Can Flashify be used to boot into the recovery?
Click to expand...
Click to collapse
no, can not
Sent from my KFFOWI using Tapatalk
Hopefully we'll get custom roms soon... AOSP on a $50, quality, device would be awesome!
THANK YOU!!! Making a backup now! I don't know if this is important or not but when I started my backup, it showed the command screen, and the first line I saw there was in red, and said
Code:
[COLOR="Red"]E:Find_File: Error opening '/sys/class/backlight'[/COLOR]
again, don't know if it's a big deal or not but thanks again so glad I can now make a backup and to OTG USB thumb drive even!!! THANKS!!!!!!!!!!!
petermg said:
THANK YOU!!! Making a backup now! I don't know if this is important or not but when I started my backup, it showed the command screen, and the first line I saw there was in red, and said
Code:
[COLOR="Red"]E:Find_File: Error opening '/sys/class/backlight'[/COLOR]
again, don't know if it's a big deal or not but thanks again so glad I can now make a backup and to OTG USB thumb drive even!!! THANKS!!!!!!!!!!!
Click to expand...
Click to collapse
Just ignore that line.
Any Tom development started yet?
Awesomeslayerg said:
Any Tom development started yet?
Click to expand...
Click to collapse
Yes, however right now I'm just doing a highly customized, de-bloated, de-amazon'd, pre-rooted, stock based rom. I don't know if anyone is working on AOSP or CM based roms at the moment.
added video to post #2
Harry44 said:
Yes, however right now I'm just doing a highly customized, de-bloated, de-amazon'd, pre-rooted, stock based rom. I don't know if anyone is working on AOSP or CM based roms at the moment.
Click to expand...
Click to collapse
That sounds really great. I tried to make a deblooated rom, but I broke the settings application by accident. I guess I'll just wait until someone else releases theirs... :/
SD, I am trying to install TWRP as per the video. For some reason, my files look different then your and I am running Win 10. Any advice? Thanks much.
PS: When I get to the command prompt,, mine just opens up to my system, not the ADB folder....
EDIT: Ok, got it to go, don't know how, but it worked. Anyone else notice the device runs a little sluggish after this? Thanks!
hey since this is running lollipop amazon os. cany you guys make a costom rom like the hdx developers do that can be booted without unlocking the bootloader. they use safestrap which is like twrp but for locked bootloaders and install custom roms. they arnt fully custom they have amazon aspects that let it boot with the locked bootloader but it is almost fully custom the hdx has a nexus rom and a cm11 rom they made for it.
sandman512 said:
SD, I am trying to install TWRP as per the video. For some reason, my files look different then your and I am running Win 10. Any advice? Thanks much.
PS: When I get to the command prompt,, mine just opens up to my system, not the ADB folder....
EDIT: Ok, got it to go, don't know how, but it worked. Anyone else notice the device runs a little sluggish after this? Thanks!
Click to expand...
Click to collapse
Did you install Google apps zip?
It's not unusual for google services to slow down a device
sd_shadow said:
Did you install Google apps zip?
It's not unusual for google services to slow down a device
Click to expand...
Click to collapse
Thanks for the reply. Yes, did install the Google Apps Zip? Can that be uninstalled?
sandman512 said:
Thanks for the reply. Yes, did install the Google Apps Zip? Can that be uninstalled?
Click to expand...
Click to collapse
Not as easily as it they were installed.
Use a root file manager, to delete or rename or move.
Use titanium backup pro or similar app, to freeze google apps
you freeze all google apps, and see if performance improved, them unfreeze google apps one at a time to see which ones are causing issues.

Problems with Android N Preview and Unenrollement

Good Morning Everyone! I decided to open this discussion hoping someone could help me solve or at least understand the problem I have been having on my Nexus 6 with Android N Preview. So, I have the Nexus 6 since April and I got it from a friend who sold it to me. At that moment the phone was already enrolled in the Beta Program, and was running one of the first previews. But here came the problem. In fact I wanted to unenroll the phone but when I enter the Beta Program page, my Nexus does not appear as eligible device nor I can unenroll it from there. I looked at Device Manager and it shows my Nexus 6, but I actually could not do anything to unenroll it. I tried flashing a Marshmallow build with NRT but as soon as I turn on my phone, an annoying notification shows up, saying I can update to the N preview. So, how can I try to uneroll my Nexus 6? My friend says he is not able to do it for me, cause he doesn't see the device on his account anymore. What do you suggest me to do?
Thanks in advance, guys!
Here is an idea.
When NRT is used Twrp-recovery is installed.
Copy a lite stock rom in 'zip-format' to internal memory. Or download it.
http://forum.xda-developers.com/showthread.php?p=59561445/
Reboot in recovery and wipe the system partition and caches.
Still in Twrp-recovery - Flash the 'zip' with lite stock rom.
Reboot.
NLBeev said:
Here is an idea.
When NRT is used Twrp-recovery is installed.
Copy a lite stock rom in 'zip-format' to internal memory. Or download it.
http://forum.xda-developers.com/showthread.php?p=59561445/
Reboot in recovery and wipe the system partition and caches.
Still in Twrp-recovery - Flash the 'zip' with lite stock rom.
Reboot.
Click to expand...
Click to collapse
Thanks for your tips, man! I have some questions about: with this procedure I'm going to install a custom ROM, but if I wanted to go back to latest official MM build and flash it with NRT, will be the problem solved in the same way in your opinion or will I get the notification about the preview again? What if I try to access with another different account after that in your opinion?
Ste293919 said:
.... if I wanted to go back to latest official MM build and flash it with NRT, will be the problem solved.....
Click to expand...
Click to collapse
You need to delete the current account and do a factory reset.
For going back to stock there is a tutorial,
http://forum.xda-developers.com/showthread.php?p=57063390/
So I managed to go back to android MM after enteting a new account and unenrolling my Nexus 6 from Beta Program. Now everything seemed fine but then after I updated back with the OTA I received, I noticed my device has still July Security patch. I thought Google would have sent me September ones, so I tried to check manually and waited a whole day, but nothing happened. Coukd it be a problem related to bad installation in your opinion? Do you suggest me to restore September build through NRT?
Thanks for all your help man, I owe you and thanks you for your time!

[Q] ota update always failing

i had twrp but i wanted ota updates now and i flashed stock recovery and locked the bootloader but after i update from ota i always end up getting installation failed why is that? i didnt root
Spiffy Jay said:
i had twrp but i wanted ota updates now and i flashed stock recovery and locked the bootloader but after i update from ota i always end up getting installation failed why is that? i didnt root
Click to expand...
Click to collapse
You really dont need to re-lock bootloader. You could have just downloaded and flashed through twrp and then flash supersu. But i am not sure why it is failing on your end.
Same thing here, always installation failed
Try a different type c cable.. Apparently, I was having this issue
Op3t original cable : Android auto and adb side load works perfectly on my op3
But when used on op3t, android auto cannot detect and side load of ota fails.
Used the original cable from Google Nexus 6p, Android auto works perfectly but I didn't try side load adb because I already flash via TWRP instead.
Try changing cables
Found a FIX!
its sort of a long process if anyone is interested lmk sorry would post but doont know if anyone cares
Spiffy Jay said:
its sort of a long process if anyone is interested lmk sorry would post but doont know if anyone cares
Click to expand...
Click to collapse
I too had the same problem. Can you explain me how to get that?
sure @kabeeradam so what you need to do or atleast what worked for me was go all stock recovery and rom and had bootloader locked too.
flash the beta rom from oneplus through sideload then flash the stable rom from oneplus then do the normal ota update and it should work. lmk for any other info also sorry if it looks like a mess this is my first time explaining these types of things. hope it helps
Spiffy Jay said:
sure @kabeeradam so what you need to do or atleast what worked for me was go all stock recovery and rom and had bootloader locked too.
flash the beta rom from oneplus through sideload then flash the stable rom from oneplus then do the normal ota update and it should work. lmk for any other info also sorry if it looks like a mess this is my first time explaining these types of things. hope it helps
Click to expand...
Click to collapse
I am in 3.5.3 now. Locked bootloader. Still OTA gets failed. When I tried Oxygen OS 3.5.3 through sideload also gets failed. Can you give me the link for beta rom???
@kabeeradam im a complete dumbass i realized that i posted this on the wrong phone it was meant to be one the oneplus 3 not 3t but it should be the same i guess
http://downloads.oneplus.net/devices/oneplus-3/ flash open beta 10 through sideload and then flash oxygenos 3.2.8 and do normal ota update im sorry i just saw

Twrp problem please help!

So let me explain the whole story, so a couple days ago i install OOS 4.0 on my Oneplus 3T and tried to root it, bearing in mind i was already rooted when i upgraded and I lost my root privileges. So then when i tried to re-root my phone it ahs come up with "dm-verity has not started in enforcing mode and may not work properly", so a bit weird but then i tried to install TWRP and when i booted into TWRP, it just stayed at flash screen of TWRP and wouldn't initialize. I have being trying ever since, factory resetting my phone, re-root etc. Please help me!
I CANNOT BOOT INTO TWRP, IF YOU WERE GOING TO SAY THAT!
Boot it into a boot loader and use this :
https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
Choose option 4 and make sure you are unlocked.
Choose option 7 and wait a few moments to see if that works. If not try the UnBrick tool.
How long have you been waiting on the TWRP startup screen? You do know it takes a long time to startup using F2FS and encryption on data partition, up to a minute from what I've heard.
pitrus- said:
How long have you been waiting on the TWRP startup screen? You do know it takes a long time to startup using F2FS and encryption on data partition, up to a minute from what I've heard.
Click to expand...
Click to collapse
I'd normally wait around 5 minutes
UPDATE:So i just booted into TWRP and have been waiting around one minute and it is still on the splash screen.
Look at this:
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
DarqAnshin said:
Look at this:
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
I'll check it out.
DerpDiamonds said:
I'll check it out.
Click to expand...
Click to collapse
It didn't work
is your bootloader locked or unlocked?
This question seems to keep repeating itself due to missing information on TWRP post about the latest official version being incompatible with OOS 4 encryption method, but that is the explanation. There is a beta release of TWRP in post 550 in that thread that is supposed to fix this.
DerpDiamonds said:
I'll check it out.
Click to expand...
Click to collapse
pitrus- said:
This question seems to keep repeating itself due to missing information on TWRP post about the latest official version being incompatible with OOS 4 encryption method, but that is the explanation. There is a beta release of TWRP in post 550 in that thread that is supposed to fix this.
Click to expand...
Click to collapse
Oh i get it now, thanks i'll wait for TWRP to update. Thanks!

Google's 12 Beta test.

Hello everyone,
So I recently was testing for Googles Android 12 beta test program which converted my phone over to Android 12. And then I realized I didn't like Android 12 because my apps weren't working with it.
During the beta test program Android said you can revert back to Android 11 which it didn't allow me to.
I tried looking on the forums for recovery and tried everything I could to revert it back to Android 11 however the file format of the system that Google put on was a Raw file system that recoveries and even Google's recovery software was not fixing at the time, so I ended up bricking my device basically.
Now that it's been a few months I'm wondering if any of you know of a fix at the moment that might work. So I can unbrick my device.
try to flash the very first (oldest) factory image. i had to do that once my phone wouldnt flash any other image they would all fail but the oldest was the only one to flash
https://dl.google.com/dl/android/aosp/coral-qd1a.190821.007-factory-e915f51a.zip
kidhudi said:
try to flash the very first (oldest) factory image. i had to do that once my phone wouldnt flash any other image they would all fail but the oldest was the only one to flash
https://dl.google.com/dl/android/aosp/coral-qd1a.190821.007-factory-e915f51a.zip
Click to expand...
Click to collapse
I'll give it a try thank you.

Categories

Resources