Pixel 5 Boot Debug - Google Pixel 5 Questions & Answers

Guten Tag, ich habe ein gebrauchtes Pixel 5 gekauft.
- product revision
- bootloader version
- baseband version
- serial number
- secure boot: production
- NOS production: YES
- DRAM 6GB
- UFS 128GB
- Device state: locked
- Boot slot: a
- Enter reason: Combo key
debug policy(a): enabled(not-in-list)
debug policy(b): enabled(not-in-list)
Was bedeutet das mit dem debug policy ? und wie kann ich das beheben?
Vielen Dank für eure Hilfe
Hello, I have consumed a used Pixel 5.
- product revision
- bootloader version
- baseband version
- serial number
- secure boot: production
- NOS production: YES
- DRAM 6GB
- UFS 128GB
- Device state: locked
- Boot slot: a
- Enter reason: Combo key
debug policy(a): enabled(not-in-list)
debug policy(b): enabled(not-in-list)
What does this mean with the debug policy ? and how can I fix this ?
Thanks for your help

Tobias769 said:
Guten Tag, ich habe ein gebrauchtes Pixel 5 gekauft.
- product revision
- bootloader version
- baseband version
- serial number
- secure boot: production
- NOS production: YES
- DRAM 6GB
- UFS 128GB
- Device state: locked
- Boot slot: a
- Enter reason: Combo key
debug policy(a): enabled(not-in-list)
debug policy(b): enabled(not-in-list)
Was bedeutet das mit dem debug policy ? und wie kann ich das beheben?
Vielen Dank für eure Hilfe
Hello, I have consumed a used Pixel 5.
- product revision
- bootloader version
- baseband version
- serial number
- secure boot: production
- NOS production: YES
- DRAM 6GB
- UFS 128GB
- Device state: locked
- Boot slot: a
- Enter reason: Combo key
debug policy(a): enabled(not-in-list)
debug policy(b): enabled(not-in-list)
What does this mean with the debug policy ? and how can I fix this ?
Thanks for your help
Click to expand...
Click to collapse
Someone just flashed a stock debug rom using the android flash tool on the Chrome web browser, I did it yesterday and my phone says the same thing debug policy, Android Flash Tool - Device Chooser

elong7681 said:
Someone just flashed a stock debug rom using the android flash tool on the Chrome web browser, I did it yesterday and my phone says the same thing debug policy, Android Flash Tool - Device Chooser
Click to expand...
Click to collapse
ah okay, do you know how I fix it?

Tobias769 said:
ah okay, do you know how I fix it?
Click to expand...
Click to collapse
@Tobias769 I don't know how to fix it, I don't think it causes any issues at least I haven't experienced any.

elong7681 said:
@Tobias769 I don't know how to fix it, I don't think it causes any issues at least I haven't experienced any.
Click to expand...
Click to collapse
i don't think so either. my system runs great.
what system do you use on your pixel ?

Tobias769 said:
i don't think so either. my system runs great.
what system do you use on your pixel ?
Click to expand...
Click to collapse
Stock Android 11 with root and cleanslate kernel

elong7681 said:
Stock Android 11 with root and cleanslate kernel
Click to expand...
Click to collapse
nice

Tobias769 said:
nice
Click to expand...
Click to collapse
What about you

elong7681 said:
What about you
Click to expand...
Click to collapse
i use grapheneos. its a wonderfull rom, without spyware

Related

Kaiser locks up while clearing the memory

Hello !
I wanted to reset my device to factory defaults over "settings - clear memory"
After a reboot, the phone locks up on the green windows logo while displaying "Clearing memory. Please wait" (translated - the german text is "Das Gerät löscht den Speicher. Bitte warten").
I tried Soft- and Hardreset.
Does anyone have a hint, how to solve this ?
Thanks in advance
/edit: WM6.1
/edit2: I get a new phone - memory was dead...

Problems with X1 Windows Mobile 6.5 and Windows 7 Build 7600.16385 X64

Hello...
First of all I want to thank all the People, who work on the fantastic roms available in this forum...
Maybe somebody already had the same problem and can help me...
I have installed Windows 7 X64 and set up the Windows Mobile Device Center to connect and sync my Xperia X1 with Outlook 2007.
The connection is working perfectly, I've got access to the memory of my x1 and also the Multimedia-Features of WMDC are useable... But the synchronisation doesn't work... or only partly...
When I choose something in the synchronisation, which is taken from Outlook there appears an error message... When I disable the checkboxes Contacts, Mails, Tasks, ... then the sync works...
I have turned on the debug mode in WMDC and this is what the logfiles tell...
Code:
wmdc Information: 8 : Engine.OnLoaded - ActiveSync in Windows-PC 2
DateTime=2009-09-16T11:16:20.8320161Z
wmdc Information: 0 : SyncController.Run - RaiseSyncStarted
DateTime=2009-09-16T11:16:20.8320161Z
wmdc Verbose: 0 : SyncController.RaiseSyncStarted Count:1
DateTime=2009-09-16T11:16:20.8320161Z
wmdc Information: 8 : WindowsMobileDevice2005.OnSyncStarted - Posting OnBegin notification
DateTime=2009-09-16T11:16:20.8320161Z
wmdc Information: 8 : WindowsMobileDevice.PostNotification - Davids X1i.OnBegin to Davids X1i
DateTime=2009-09-16T11:16:20.8320161Z
wmdc Information: 0 : SyncController.Run - AirSyncDesktop.BeginSync
DateTime=2009-09-16T11:16:20.8476162Z
wmdc Information: 0 : Request start sync AirSyncDesktop
DateTime=2009-09-16T11:16:20.8476162Z
wmdc Information: 8 : WindowsMobileDevice.OnNotification.OnBegin - from Davids X1i
DateTime=2009-09-16T11:16:20.8632162Z
wmdc Information: 8 : SyncController2005.OnNotify - AirSyncStatusListener sent device OnBegin notification, count 1
DateTime=2009-09-16T11:16:21.6744176Z
wmdc Verbose: 0 : SyncController.RaiseSyncStarted Count:2
DateTime=2009-09-16T11:16:21.6744176Z
wmdc Information: 8 : [Windows-PC 2] Engine b9217127-3cb7-427b-8605-4962e901e52f OnItemsOutOfDate
DateTime=2009-09-16T11:16:22.1892185Z
wmdc Information: 0 : SyncQueue.Enqueue - Item ActiveSync already in queue not enqueing
DateTime=2009-09-16T11:16:22.1892185Z
wmdc Information: 8 : Engine.OnBegin - AirSyncDesktop in Windows-PC 2
DateTime=2009-09-16T11:16:22.4076189Z
wmdc Information: 8 : WindowsMobileDevice.PostNotification - AirSyncDesktop.OnBegin to Windows-PC 2
DateTime=2009-09-16T11:16:22.4232189Z
wmdc Information: 8 : DataSource.OnNotification - from AirSyncDesktop, OnBegin
DateTime=2009-09-16T11:16:22.4232189Z
wmdc Information: 8 : Engine.OnError in AirSyncDesktop in Windows-PC 2 - HRESULT:80004005 - Achtung%Die Synchronisierung konnte nicht abgeschlossen werden. Wenn das Problem weiterhin besteht, löschen Sie Synchronisierungspartnerschaften, und stellen Sie sie erneut her.
DateTime=2009-09-16T11:16:26.2452256Z
wmdc Information: 8 : WindowsMobileDevice.PostNotification - AirSyncDesktop.OnError to Windows-PC 2
DateTime=2009-09-16T11:16:26.2608256Z
wmdc Information: 8 : WindowsMobileDevice.PostNotification - Windows-PC 2.OnError to Davids X1i
DateTime=2009-09-16T11:16:26.2608256Z
wmdc Information: 0 : Toast::OnError (-2147467259, Achtung - Die Synchronisierung konnte nicht abgeschlossen werden. Wenn das Problem weiterhin besteht, löschen Sie Synchronisierungspartnerschaften, und stellen Sie sie erneut her.)
DateTime=2009-09-16T11:16:26.2608256Z
wmdc Information: 8 : Engine.OnEnd - AirSyncDesktop in Windows-PC 2
DateTime=2009-09-16T11:16:26.8068266Z
wmdc Information: 8 : WindowsMobileDevice.PostNotification - AirSyncDesktop.OnEnd to Windows-PC 2
DateTime=2009-09-16T11:16:26.8068266Z
wmdc Information: 8 : DataSource.OnNotification - from AirSyncDesktop, OnEnd
DateTime=2009-09-16T11:16:26.8068266Z
wmdc Information: 0 : SyncController.Run - AirSyncDesktop.EndSync
My second problem is the thing with Windows SideShow, the little, undiscoverable feature, which should connect my Phone with my PC even closer... (control Media Player, Media Center, ...)
I already connected my phone to the WMDC over Bluetooth and installed the SideShow cab for Windows Mobile on my phone... but when I start it and press connect, there is a notification, that the connection failed and I shall ensure that my Phone is already paired with the PC... but as I wrote above it's even connected to the WMDC... Anybody who knows how to activate, or install Windows SideShow??
In the end I have to excuse my english, I'm a german guy
Thanks a lot for the answers in advance,
greets LichtiMC
tried to disable ur firewall?
I had the same situation as u do.....
win 7 professional X64
win 7 installed everything correctly......i can access my sd card, my phone memory....but just couldn't sync
but once I remove my firewall software (agnitum outpost in my case)
it works automatically.....
check your event viewer and see what error u get.
Just tried...
I've just tried to sync with firewall disabled... same result...
I've read, that this is probably caused by the outlook.pst file... I already executed scanpst.exe until there weren't any errors anymore... So... may you or somebody else has another advice for me...?
LichtiMC said:
I've just tried to sync with firewall disabled... same result...
I've read, that this is probably caused by the outlook.pst file... I already executed scanpst.exe until there weren't any errors anymore... So... may you or somebody else has another advice for me...?
Click to expand...
Click to collapse
Edit: Is it possible that there are missing some rights for WMDC to connect to the Contacts, Mails, Tasks, ... I found out, that the problem is still there, if I create a new outlook.pst file...
Pls sbdy help... =)
(Sorry for the douple post... pressed the false Button...)
Problem solved...
OK, now I know, that the ActiveSync problem is a bug of the X10 Roms and will be corrected soon...
Now I'd like to know, if smdy of you already played around with Windows SideShow... As long as I search, I just can't find it in Windows 7...
Edit: Found out, that in Windows 7 SideShow only appears if you are already paired over Bluetooth with your device... also you have to choose SideShow at the Blutooth Services for your device... (In my case this wasn't possible, because the SideShow Universal Driver for Bluetooth wasn't installed and Windows Update didn't find it... so I installed it manually and then the connection worked...=)
I heard Windows Sideshow does not work with Windows 7... did you really get it to work with Windows Mobile?
can i have the link of windows 7 u installed?

[Q] Unlock Windows Phone 7

Hello!
I looked around for ages now, and I'm not getting my HD7 unlocked.
As far as I know, there are just 2 Possibilities to unlock the Phone:
1. Chevron WP7
2. WP7-Update-Cab-Sender
As long as I have Version 7392 , I can't use Chevron.
I tested around with the Sender, but every cab I use can't be sended because some Certificate is missing.
This is what it says. Appearently it is in German, but the error code should be the same:
Code:
UpdateWP version 4.8.2345.0
Applying updates to device
Id: \\?\usb#vid_045e&pid_04ec&mi_00#6&2940f84b&0&0000#{ca3d7387-f67b-11da-bbec-8000600fe800}
SN: 930b0693 - 157d256b - e8fa5cac - b1d407b1
Name: HDSiebön
KITLName: QSD8XXX07387240
Manufacturer: HTC
ModelId: 1
Model: HD7 T9292
MobileOperator: O2O-DE
Version: 07.00.07392.03-00.00.00000.00-00.00.00000.00
Der Status Ihre Telefons wird überprüft: Completed in 0,01 seconds
Systemanforderungen werden geprüft: Completed in 0,06 seconds
Updates werden heruntergeladen: Completed in 2,16 seconds
Systemanforderungen werden geprüft: Completed in 0,01 seconds
Updates werden übertragen: Completed in 0,05 seconds
Installation wird vorbereitet: Completed in 2,02 seconds
Error:
Update device 930b0693 - 157d256b - e8fa5cac - b1d407b1 Complete with error code: 800B010A, error message: Es konnte keine Zertifikatkette zu einer ve
rtrauenswürdigen Root-Berechtigung aufgebaut werden.
So my Question is: What am I doing wrong, and how do I get this Working?
I hate not being allowed to have my own Ringtone or Colour or Bluetooth connection or to access the file System or to search my Calendar...
Thanks for helping.
I had my hd7 unlocked on 7392, have you tried downgrading to pre nodo?
No, how do I get it pre Nodo?
(I have the ROM, but how do I get it on my Phone)
Is the Sender working then?
This problem, which I suffer of them too .
plz what i do with this problem .​

falsche IMEI

Already in advance, I've already read all the threads on this subject, unfortunately everything did not help. (And no, I did not EFS backup before)
To my problem:
Originally my S5 Mini is no longer powered.
It's stuck on the Samsung logo.
The S5 Mini has been up to this time rooted nor whatever (warranty had expired).
Following I have the floor-ROM 5.1 installed.
Device is rebooted, unfortunately after that no longer fit the IMEI, the IMEI held on the unit match, thus no power application possible.
Then I rooted the device and TWRP Recovery 3.0 installed.
In Recovery Mode me the "Failed to mount / EFS" error is noticed.
NAlready in advance, I've already read all the threads on this subject, unfortunately everything did not help. (And no, I did not EFS backup before)
To my problem:
Originally my S5 Mini is no longer powered.
It's stuck on the Samsung logo.
The S5 Mini has been up to this time rooted nor whatever (warranty had expired).
Following I have the floor-ROM 5.1 installed.
Device is rebooted, unfortunately after that no longer fit the IMEI, the IMEI held on the unit match, thus no power application possible.
Then I rooted the device and TWRP Recovery 3.0 installed.
In Recovery Mode me the "Failed to mount / EFS" error is noticed.
Next step was:
Open ADB command window and type the Following cmd:
adb shell
mke2fs / dev / block / mmcblk0p3
mount -w -t ext4 / dev / block / mmcblk0p3
reboot
The IMEI remained the same
Now I have unfortunately no idea what to do yet.
Does somebody has any idea?
Open ADB command window and type the Following cmd:
adb shell
mke2fs / dev / block / mmcblk0p3
mount -w -t ext4 / dev / block / mmcblk0p3
reboot
The IMEI remained the same
Now I have unfortunately no idea what to do yet.
Does somebody has any idea?
Bereits vorab, ich habe alle Threads zu diesem Thema bereits gelesen, leider hat alles nichts genutzt. (und nein, ich habe kein EFS-Backup davor gemacht )
Zu meinem Problem:
Ursprünglich ist mein S5 Mini nicht mehr hochgefahren.
Es ist beim Samsung-Logo hängengeblieben.
Das S5 Mini wurde bis zu diesem Zeitpunkt weder gerootet noch sonstwas (Garantie war bereits abgelaufen).
Im Anschluss habe ich das Stock-ROM 5.1 installiert.
Gerät ist wieder hochgefahren, leider passte danach die IMEI nicht mehr, mit der auf dem Gerät befindlichen IMEI überein, deswegen auch keine Netzanmeldung mehr möglich.
Daraufhin habe ich das Gerät gerootet und TWRP Recovery 3.0 installiert.
Im Recovery Mode ist mir der "Failed to mount /EFS"-Fehler aufgefallen.
Als nächstes habe ich die folgendem Kommandos erfolgreich im ADB abgesetzt:
Open ADB command window and type the following cmd:
adb shell
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
Die IMEI blieb gleich
Ich habe nun leider keine Ahnung mehr, was ich noch machen soll.
Hat jemand eine Idee?
Same Probleme here / Selbes Problem bei mir
Hi
Do you still have this troubles? Or did you solve it already somehow? I'm facing the same problem since few weeks. Also tried a lot of different things. Obviously there are people who succeed with writing cert. I also tried but was not lucky until now. In a post on the gmshosting people of the octopus box tried to solve this problem. They said there is a way. You need the backup of someone else with a working S5 Mini. Then you can write cert from there and restore your efs. this shoud make it work again. but i didnt find someone yet who is willing to share its backup to me
Is your new weird suddenly appeard IMEI also 350695200123951 ?
Can anyone share a backup with me?
i'm facing the same problem, please someone who can upload her EFS for us ! thank you for being generous. please help US.

[VoLTE/VoWiFi][OP5/5T] for almost all carrier!

Hey!
I have found a way to activate VoLTE and VoWiFi for OnePlus 3/3T, 5/5T, 6 and 6T!
Please follow this Guide to Activate it to your Phone!
Link for english user:
https://forum.xda-developers.com/oneplus-5t/how-to/guide-volte-vowifi-german-carriers-t3817542
Link for German user: https://android-freaks.de/forum/thr...neplus-8-und-8-pro-freischalten-die-nicht-of/
This is more for advanced users!
Greetings,
jamal2367
I'd like to let you know that this method also worked for me in Czech Republic for Vodafone. This guide probably works for most of the carriers in EU. Thanks!
Diese Methode hat auch in Tschechien funktioniert, ich kann nicht VoWiFi benutzen aber VoLTE funktioniert super. Wahrscheinlich funktioniert dieses Guide für alle Netzbetreiber in EU.
gonna try at ukrainian Vodafone.... when they will launch Volte
Worked. Germany and o2.
Why not sharing here, too?
Read something about EFS? Will it survuve, are there some modifications?
Thanks in advance.
tidschi said:
Why not sharing here, too?
Read something about EFS? Will it survuve, are there some modifications?
Thanks in advance.
Click to expand...
Click to collapse
It survives modem flashes and all. I'd write the whole procedure here but I'd need @jamal2367 permission to do so.
It worked! It woooorked
Many many endless thanks, Jamal!
Hello,
tried here in belgium, when i click on "activate" it does nothing and when i click on start, nothing too.. Is there a validation message at the end of the procedure or not? thx
Working with Vodafone Portugal! Can't test a call just yet, I don't know anyone with a VoLTE device, but the icon appears.
From what I read on the forum, it's just the Magisk module for root users or the toolkit procedure for the ones without.
It does help with some carriers, but not everywhere =(
Thanks anyway!
angourakis said:
From what I read on the forum, it's just the Magisk module for root users or the toolkit procedure for the ones without.
It does help with some carriers, but not everywhere =(
Thanks anyway!
Click to expand...
Click to collapse
And you have to modify your EFS ...
Read the OP on Hubo, he has an spoiler at the end.
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
DKett said:
And you have to modify your EFS ...
Read the OP on Hubo, he has an spoiler at the end.
Click to expand...
Click to collapse
Danke! I couldn't find it because Google Translate breaks everything.
Btw, could you modify your phone? I'm on step 7, but when I select my device, it gives me an error: "Failed to select interface with provided ID, please make sure interface still exist".
I did install the drivers and the QPST 2.7.420, did the *#801# and "Serial" + "Full-port switch" and I also tried removing and adding the port inside QPST Configuration and running QPST Software Download as Administrator.
The device is also shown under Ports in Device Manager (Windows 10).
Nothing worked...
Thanks!
angourakis said:
Danke! I couldn't find it because Google Translate breaks everything.
Btw, could you modify your phone? I'm on step 7, but when I select my device, it gives me an error: "Failed to select interface with provided ID, please make sure interface still exist".
I did install the drivers and the QPST 2.7.420, did the *#801# and "Serial" + "Full-port switch" and I also tried removing and adding the port inside QPST Configuration and running QPST Software Download as Administrator.
The device is also shown under Ports in Device Manager (Windows 10).
Nothing worked...
Thanks!
Click to expand...
Click to collapse
Had the same issue, I rebooted my PC and that worked
/* Disclaimer */
This is at your own risk.
I am not responsible for broken phones, lost IMEI numbers, damaged EFS partition, whatever.
First make a backup of the EFS partition via TWRP or ADB, and back it up to a safe place on your computer!
WARNING: The EFS partition contains unique data for your device that is necessary for the phone function of your device. If you lose them, no one can help you out. So make a backup. If something goes wrong, you can restore the backup and you will be back to its original state.
2. you go to your computer and install both.
Qualcomm QPST Diag x64 driver
QPST_2.7.420
Now connect your mobile phone to your computer via a "USB cable".
4. opens the phone app and enter this code *#801#.
Now a new menu appears and switches "Serial" and "Full-port switch" on.
Now you start the program: "QPST Software Download" and connect it to your device.
Go to the "MCFG_PDC" tab at the top and select your device under "Device:".
Right-click on "Oversea-Commercial_DS" and select "Sub0" and "Sub1" under "Deactivate".
Now click on "Oversea-Commercial_DS" again and click on "Remove" on the right.
Now restart the program and go to the tab "MCFG_PDC" and under "Device:" select your device again.
Now select "Telefonica_UK_Commercial", right click and select "SetSelectedConfig" "Sub0" and "Sub1".
12. click on "Telefonica_UK_Commercial" then right click on "Activate" and then on "Start" below
13. after you have done everything, restart the device!
After a successful restart, the "VoLTE or VoWiFi logo" should appear in the expanded status bar.
No wonder why you dial "Telefonica_UK_Commercial", works great in Germany with all providers!
Translated with www.DeepL.com/Translator
I wonder if this has the potential to fix the 3G issues as well, as we're effectively changing the modem's default profile it seems.
david19au said:
Had the same issue, I rebooted my PC and that worked
Click to expand...
Click to collapse
No lucky =( What's the name of the device that appears for you under MCFG_PDC tab?
Thank you!
angourakis said:
No lucky =( What's the name of the device that appears for you under MCFG_PDC tab?
Thank you!
Click to expand...
Click to collapse
It should be a long string of characters, IIRC. The name is unique to every device afaik.
Did someone tried this with French network ?
Is there any way to enable this on aosp rom?
Στάλθηκε από το ONEPLUS A5010 μου χρησιμοποιώντας Tapatalk
I don't think so. Most AOSP rom's are missing some APN's. Ask the Dev if he implements all Google AOSP APN's.

Categories

Resources