Database Develop

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] X1i HardSPL Error 262

Hi,
I cannot flash 0.78.OliNex Hard-SPL on my new X1i: The progress bar stays at 0% until the timeout, then Error 262. I tried everything (no sd-card, no sim, hard reset, compability mode etc.), no avail.
My new X1i has the image version 1.05.932.7 (03/24/09), the bootloader reads:
KOVS110
SPL-0.78.0000
MicroP1-787
MicroP2-707
The type is AAD-380001-BV.
Radio is 1.14.25.55, protocol 52.65.25.34J, extended protocol 1.0.11809.7229.
Software ID is 1213-6439, version R3AA007, user id 1215-3303, user version R15A, content version PA10.
I noticed that the installed WME 6.1 is modified compared to the old X1. In particular, during my first attempt, a WM6.1 warning message with a red boundary popped up, indicating that proceeding could harm the phone (yes/no). I checked yes, and since then, the message does not come up anymore. Probably the ROM is not in Olis compatibility list, so I looked for unsigned HardSPL, but found only the Image Version 1.00.Diamond, so I did not flash it (probably it would brick my X1i). Any idea would be very much welcomed, I want to get rid of WM6.1 and flash WM6.5.3.
Thanks a lot for any hints.
BTW, I've posted this thread alredy in the X1 General forum and realised only now that this forum might be a better choice, sorry for that.

Next try
Hi,
I found the recommendation below and tried, but no avail as well.
Does anyone know an unsigned HardSPL by Oli for the SE X1?
Any help appreciated.
_________________________________________
xidesu
3rd August 2010, 09:33 PM
Default HTC Touch Pro, Fuze HardSPL Error 262 FIX
Alright, this is how i fixed my 262 error after ripping out all my hair for a week.
- Plug your phone into any working usb port (make sure Active sync is up and running)
- Run RaphaelHardSPL-Unsigned_190_1_3.exe and on the first screen pop up, 9 files will be created in the directory you run the .exe from.
- Copy these 9 files to another folder because you will be clicking cancel on the pop up which will in turn erase the 9 files it created.
- Click cancel on the pop up.
- Go to the folder in which you copied these 9 files to.
- Run ROMUpdateUtility.exe and the same screen pop will appear as before.
- Follow the prompts and it should work.

don't flash bootloader-stuff from other devices, never! Oo
try flashing hardspl 0.72 via usb first (the old one), then flash 0.78 as an "update".

Next step, but still not working
Well, I was able to flash APP_SW_X1i_GENERIC_UK_1213-6450_CDF1215-1832_KOV_R1AA017
from the SD card, and I have now SPL0.72.0000 on my X1.
ROM Version:1.02.931.3
Date: 08/29/08
Radio: 1.06.25.29
Protocol: 52.43.25.24U
Software ID: 1213-6450
Version: R1AA017
However, X1_HardSPL still terminates with Error 262 as before. Flashing OliNex's HardSPL via SD card (RUU_Signed.nbh renamed to kovsimg.nbh) does not work either. I still cannot flash my Dynamics GTX 2.3.5 GER ROM.
Any ideas?
BTW, I tried with a desktop and a laptop, both XP SP3 and Active Sync 4.5 on various USB ports. I disabled Security Options via X1_Tweaks. Everything seems to work, only flashing HardSPL still fails.
At least, I am a step back now ;-)

Bingo!
I succeeded. The solution has been:
- Establish an Active Sync connection via USB.
- Copy the file Xperia-SSPL-Manual.exe to the root directory of a FAT32-formatted SD card (no SDHC, an elder one). SSPL-Manual is the basic part of OliNex bootloader.
- Unpack HardSPL by starting it or use RUU_Kovsky files in a directory of the PC hard disk. Make sure that the proper RUU_Signed.nbh file is in this directory (the HardSPL image by Olimex in the version you whish to complete the basic SPL started onthe X1)..
- On the X1, open the file manager and start Xperia-SSPL-Manual.exe by clicking on it. The X1 switches to the boot loader mode indicating HardSPL 0.52 by OliNex.
- On the PC connected to the X1, start ROMUpdateUtility.exe.
In my case, the flashing went very quickly to 100%, and I have now HardSPL0.78OliNex on my X1. Now I can proceed (Task29, image flashing). At least I hope so.
My assumption about the the problems I faced: My X1 had a quite recent firmware which probably blocked any change of the SPL and allowed only generic signed images to be flashed, no cooked ones. Xperia-SSPL-Manual.exe bypasses this lock by applying an OliNex cracked routine, thus allowing to overwrite the SPL. At least I think so.

Done.
My Dynamics GTX 2.3.5 GER ROM is now up and running. THX a lot for the great support of this forum!

Thanks for instructions I have same problem with my X1.

You're welcome.
It has been worth the troubles - the Dynamics ROM is great, and until now, I found no hickups.

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.

Pixel 5 Boot Debug

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