yashsingh1/xdaforums huggingface dataset:
[General Topics] rabb1tmac:
Hello, i successfully flashed AOSP rom and l wanted to try Lineage OS and flashed it, it worked. Then i flashed magisks thingy. Now i cant boot into OS, i tried flashing kernal, vendor, rom everything and it boot loops into eRecovery. Any Idea?

UPDATE: I tried flashing back the AOSP rom that i flashed first and it boots in 'ANDROID" booting screen. After awhile, it just automaticcaly boots into TWRP again. Help please?
[General Topics] adeii:
You could not boot to Lineage just after Magisk ? Try to install LOS, install Magisk Manager and then install Magisk (and patch ramdisk.img).

What vendor exactly did you flashed, since no need to flash any? Exept few files could be used from older vendor.

Did you format (not just wipe) /data and /cache before booting AOSP?

Have you flashed dm-verity_and_forced-encryption-remover, reboot to TWRP and then format /data ?

UPDATE: Since, you all got 9.0+ custom roms, you can update OpenGL and Vulkan drivers for Adreno 505! Look for SD430/MSM8937.

GDisk folder with drivers: https://drive.google.com/drive/folders/14dHePwCb6r16roJKo1V1-KaFxk1KlJ2E or even the newest https://drive.google.com/drive/folders/1It3fgN8-hLSeBc4268aArWfCarWx2Z3E

Thread about them (for LG L5, but better find for Xiaomi Riva/Rolex/Land): adreno-5xx-gpu-drivers-t4042619

Known Issues: V@0472.0, V@0481, V@0485.0 and V@0490.0 drivers can cause the following problems on 500 and 600 series

Loss of Bootanimation

Not working Face unlock

Not working Screen recording

Black screen

Bootloop
[General Topics] rabb1tmac:
Okay so i reinstalled stock rom back and tried to do again. I followed all the steps correctly, but, i cant boot into AOSP. After huawei boot logo, a boot screen with 'android' comes up. After few seconds, it automatically reboots and goes into TWRP. I installed the permissive kernal, vendor image, and the fstab modifier script.

When the very first time i attempted, it worked, but there wasnt any setup to do(first time android setup walkthrough), it straight booted up into AOSP rom. I couldn't install stock variant of gapps because i got error 70 (insufficient space). So i install

ed the Pico variant of gapps.

Even though AOSP worked in the first attempt, some things wasnt right(even after installing pico gapps), for example, the google bar widget in home screen looked like from very old version of Android and same with the browser. So i decided to install Lineage. Wiped system, data, cache everything, and install back everything with Lineage OS anddd it worked. If i remember correctly, i installed the ExpressLuke GSI Magisk (I installed at the end because install this wasnt stated in the instructions so i decided to install anyway). The next morning, when i booted, it went into boot loop.

Tried wiping everything possible in TWRP, and install everything back, no success. Even tried installing back stock Huawei rom and trying again, no luck. Same bootloop. AOSP reboots after the 'android' boot screen and Lineage OS reboots after Huawei boot logo.
[General Topics] adeii:
There are about 2,2 GB for system. I have not idea that no space for gapps. Next time try to install that apps one-by-one as user apps.

Have you tried to restore stock via eRecovery ? Try factory defaults after restoring stock.

What exactly model and stock rom version do you have ?
[General Topics] rabb1tmac:
update: I got aosp phh installed and boot up. Tried different kernals provided here and got it to work. I had to install Pico variant of gapps since stock and mini gives error 70. But, the Google search bar and Browser looks like from very old version of Android. Why is that?

anndddd the battery usage is horrible as expected eo I installed nfs injector but it seems the phone is not rooted. What should i install to root it?
[General Topics] adeii:
OK. Just do not flash any vendor image.

Have you installed Magisk by ExpressLuke made for GSI custom roms? Latest version is @ sourceforge.net.

Install app and open to see next instructions.

If you had install OpenGapps from official site, that is old about 1 year.

OpenGApps migate to sourceforce. Latest version for Android 10, ARM64 phones are old about half day. opengapps64-A10.0-pico 89 mb.
[General Topics] rabb1tmac:
another update ;)

i decided to reinstall phh aosp because the ui crashed when setting up pin and after reboot it kept asking for pin which i never set properly so i was stuck there. reinstalled everything, and this time it was rooted and flashed the latest pico o.gapps. got nfs installed and working too but not sure if it's doing its thing yet

also i tried to flash the latest version available for phh aosp but couldn't get it to boot. the version mentioned in the instructions works fine. is it unsupported or i did smtg wrong?

tl;dr: got it into prefect looking pure android but is it possible to increase the brightness more? its even more dark if you use dark mode.
[General Topics] adeii:
Well, maybe you need some post-GSI fixes, there are 3 files mentioned about last year.

About brightness - need to make overlay file for that GSI.

Quick fix - open terminal or adb shell and run commands:

su
cat /sys/class/leds/lcd-backlight/max_brightness

Stock value is 4095. To write this value, try this command:

echo "4095" > /sys/class/leds/lcd-backlight/max_brightness

or

setprop persist.sys.qcom-brightness 4095

.

If can increase brightness more, you can add next line to /system/build.prop to set this value to every boot.

persist.sys.qcom-brightness=4095

.

---------- Post added at 10:44 PM ---------- Previous post was at 10:38 PM ----------

According to thread and thread, I had repacked Magisk module with updated OpenGL and Vulkan driver for GPU Adreno 505, for Android 8.0.

[M]TeamDrivers_OpenGL-Vulkan_SD430-EMUI8.0-313.

Updated versions are OpenGL 3.2 V@313 and Vulkan API 1.0.66. Stock versions are OpenGL 3.2 V@251 and Vulkan API 1.0.49.

Official packages are for Magisk or TWRP, but for Pie/Q roms.
[General Topics] rabb1tmac:
I have executed the commands, still no luck. Looks like the brightness even got lower after the command. (edit: slider doesnt work anymore, its stuck in lowest brightness possible)

also, i think the proximity sensor is not working. Screen rotation does not work. (Even with auto rotate turned on)
[General Topics] adeii:
OK. Lets try to create overlay. What rom do you use?

Can you send me framework-res.apk from /system/frameworks and build.prop from /system ?

Also, list and set value to current brighness with:

Commands to disable/enable auto-rotation are:

su
content insert --uri content://settings/system --bind name:s:accelerometer_rotation --bind value:i:0
content insert --uri content://settings/system --bind name:s:accelerometer_rotation --bind value:i:1

Also can try sensor test apk.
[General Topics] rabb1tmac:
I'm using the AOSP by phhusson (v214). The current brightness command works, slider doesnt.

I have attached the framework-res.apk and build.prop in the zip file.

Sensors doesnt seem to work, but thats okay. I dont really mind it.
[General Topics] adeii:
Thanks. Both framework-res.apk from stock and aosp could be decompiled, but can not recompile them. Overlay have to be made. In meanwhile, you can try Privset app. Search for "bright" commands and app made some kind of overlay and demand reboot. Maybe you can get it works.

Diff values between stock and custom rom are in attachment.
[General Topics] rabb1tmac:
Sorry, i dont really understand how the Privset app works. Searched for 'bright' but i dont see anything revelant?
[General Topics] adeii:
Nevermind for now.

Overlay file was made according to this guide.

Just copy it into /system/overlay/, guess you need to make dir "overlay" and set permission to rw-r--r-- / 0644. Both dir and file.

And then reboot your phone to test your overlay.

Alternative is to try overlay from this thread but put it into /vendor/overlay.
[General Topics] rabb1tmac:
I cant seem to set permission for the file, Im getting an error message when i set permissions in Root Browser.
[General Topics] adeii:
Do it from custom recovery (TWRP) not system.
[General Topics] rabb1tmac:
Hmm, if i open /system/overlay in root browser, theres many other files, i guess its different overlays for different phones. I added the overlay file you provided and set permision to 0644 with adb. - No success.

If i open file manager through TWRP, and access /system, there is no overlay folder, so i created one and pushed the overlay file you gave and set perms to 0644 (both dir and file) but upon rebooting, the files and dir dissappear, the slider doesnt work after reboot too.

Is it the same directory or two different directories? (In root browser and TWRP file manager)
[General Topics] adeii:
Maybe it should be in /vendor/overlay to work? In TWRP /system/vendor/overlay and /vendor/overlay are the same folders.

If you mount /system, it should be also the same partition as on online system. Folders like app, bin, etc, fonts, libs, frameworks, priv-app, vendor, xbin....

On unmounted /system in TWRP, folder /system would have just basic folders from some symlinks, like bin, etc, lib.
[General Topics] KaroloBC:
on LDN-L21 GSI 10/9 with PermissiveKernel = GSI freeze on gray screen (no bootanimation)

---------- Post added at 05:56 PM ---------- Previous post was at 05:51 PM ----------

vendor in the post acts the same as stock vendor from newest EMUI (gray screen, no logo). Maybe creating topic with instruction to boot GSI with all kernels, etc. will be a good idea?

---

i tested some other GSI, all display only gray screen. it's probably problem with libraries (there's part of logcat):

04-26 10:42:24.236 794 794 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/vendor.huawei.hardware.huaweiantitheft@1.0-service": cannot locate symbol "_ZN7android8hardware7details14gServiceSidMapE" referenced by "/vendor/lib64/vendor.huawei.hardware.huaweiantitheft@1.0.so"...

04-26 10:42:24.257 810 810 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/vendor.huawei.hardware.teecdaemon@1.0-service": cannot locate symbol "_ZN7android8hardware7details14gServiceSidMapE" referenced by "/vendor/lib64/vendor.huawei.hardware.teecdaemon@1.0.so"...

04-26 10:42:24.299 795 795 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/vendor.huawei.hardware.huaweisigntool@1.0-service": cannot locate symbol "_ZN7android8hardware7details14gServiceSidMapE" referenced by "/vendor/lib64/vendor.huawei.hardware.huaweisigntool@1.0.so"...

04-26 10:42:24.336 806 806 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/vendor.huawei.hardware.light@2.0-service": cannot locate symbol "_ZN7android8hardware7details14gServiceSidMapE" referenced by "/vendor/lib64/vendor.huawei.hardware.light@2.0.so"...

04-26 10:42:24.336 804 804 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/vendor.huawei.hardware.hwvibrator@1.0-service": cannot locate symbol "_ZN7android8hardware7details14gServiceSidMapE" referenced by "/vendor/lib64/vendor.huawei.hardware.hwvibrator@1.0.so"...

04-26 10:42:24.349 813 813 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/vendor.qti.esepowermanager@1.0-service": cannot locate symbol "_ZN7android8hardware7details14gServiceSidMapE" referenced by "/vendor/lib64/vendor.qti.esepowermanager@1.0_vendor.so"...

04-26 10:42:24.356 814 814 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/vendor.qti.hardware.perf@1.0-service": cannot locate symbol "_ZN7android8hardware7details14gServiceSidMapE" referenced by "/vendor/lib64/vendor.qti.hardware.perf@1.0_vendor.so"...

04-26 10:42:24.357 799 799 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/vendor.huawei.hardware.hwdisplay.displayengine@1.0-service": cannot locate symbol "_ZN7android8hardware7details14gServiceSidMapE" referenced by "/vendor/lib64/vendor.huawei.hardware.hwdisplay.displayengine@1.0.so"...

04-26 10:42:24.357 811 811 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/vendor.huawei.hardware.tp@1.0-service": cannot locate symbol "_ZN7android8hardware7details14gServiceSidMapE" referenced by "/vendor/lib64/vendor.huawei.hardware.tp@1.0.so"...

And some other useful info: my phone is LDN-L21 with 8.0.0.159 vendor.
[General Topics] adeii:
Well, it is better to use newest stock vendor.img. That should be LDN-L21A with 8.0.0.159 ? No need for older vendor.img from Ezz's post since it is for LDN-LX3. What version of permissive kernel do you use (3.18.xx) ?

Basic permissive kernel is by Ezz, ver.3.18.66, pure stock kernel + SE Linux permissive switch. AOSP 10 works with it.

All other kernels are upgraded by me (3.18.66 to 3.18.140) with patches for MSM 3.18 kernels.

Latest version got additional options like KCal, KLapse and few cpu governors and IO schedulers.

If you use that kernel, then it may cause gray screen. You can try FrancoKernel manager to tweak colours.

But no logo is some other problem. Phone by default uses splash screen logo from /oeminfo partition and bootloader animation from /product/etc/media/bootanimation.zip. Custom rom probably use /system/media/bootloader.zip....
[General Topics] adeii:
Users of android 9/10/11 custom roms can update graphic/video drivers against stock oreo driver.

You can update both OpenGL and Vulkan drivers, via TWRP or Magisk Manager (or overwrite original files in /vendor).

More about it in thread adreno-5xx-gpu-drivers-t4042619. Look for SnapDragon/SD 430 (MSM8937) drivers.
[General Topics] adeii:
Newest stock rom for L21B, via eRecovery, 8.0.0.151, region C432/EU, patch 2020-07.

update.zip
/data/update/package_cache/update.zip
http://update.dbankcdn.com/TDS/data/files/p3/s15/G3004/g1650/v448313/f1/full/update.zip

update_data_full_public.zip
/data/update/package_cache/update_data_full_public.zip
http://update.dbankcdn.com/TDS/data/files/p3/s15/G3004/g1650/v448313/f1/full/public/update_data_full_public.zip

update_full_LDN-L21B_hw_eu.zip
/data/update/package_cache/update_full_LDN-L21B_hw_eu.zip
http://update.dbankcdn.com/TDS/data/files/p3/s15/G3004/g1650/v448313/f1/full/LDN-L21B_hw_eu/update_full_LDN-L21B_hw_eu.zip
[P3300, MDA Compact III General] mikehulme1983:
There's always been a java program on the orbit, but other than mini opera are there any decent java programs or games??
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Maggy:
Hello all and Welcome to the Himalaya ROM Zone​

Here You will find all the Windows Mobile 6.x

The List is categorized by Language​

English :

eng 6.1 efsane

c-shekhar 6.0

Syed Ather 6.0

c-shekhar 6.1

Syed Ather 6 aku1

Syed Ather 6.1 Professional

Tofclock Helmi 6.0

c-shekhar 6.0 aku4.2

Ather's Dark Edition WM 6.1

Ather's Diamond Edition 6.1

Himalaya_WM6.1 .Build 19949WWE[7/6/2008]/Build20262 WWE/CHS[7/21]

[Beta]Ather's Himalaya WM6.1 Manila 2D Version

[Himalaya]WinMoB 6.1 ProEdition OS 5.2.21109 Build 21109.2.1 NOK

WinMoB 6.5 OS 5.2.21139 Build 21139 - WWE - Beta Test - NOK

sun_dream XIP:21169 SYS:21169 Aku 5.0.0 mui:0409WWE(includes:0804chs)

Norwegian language

norway 6.0 efsane

French :

france 6.0 efsane

Italian :

sostekit italian wm6

WM6.1 Italiano ROM 5.2.19199

Turkish :

turkish 6.0 efsane

turkish 6.1 efsane

German :

dkamin german 6.1

German ROM Teijak

WM6.1 Deutsch ROM 5.2.19199

Ather's Dark Edition German WM6.1 with UC - Fully loaded!

Vietnamise :

PDAviet 6.0 with Vietnamese fonts

PDAviet ROM 6.1

probably other vietnamese ROMs

Spanish :

efsane Spanish coming soon

Chinese :

I think there is a chinese ROM on http://bbs.xbeta.cn/forumdisplay.php?fid=11&page=himalaya

Polish :

WinMoB 6.1 ProEdition OS 5.2.21109 Build 21109.2.1 PL

Multi-Lang :

[ROM] Himalaya multiLANG 5.2.21109 (TUR/ITA/GER)

This list will be updated regularly
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
Maggy you've forgot my 6.1 ROM here is the link

Syed Ather 6.1 Professional
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] cavalloz:
http://rapidshare.com/files/55013392/STk_TofClock_HIMA_WM6_AKU.0.7.rar.html

;)
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Teijak:
Hello Maggy

since there is no german rom in your list, you can ad my version

http://rapidshare.de/files/38610887/WM6ger.zip.html

Teijak
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] musicmat:
IPHONE Theme

Hi,

what iphone theme you are using on your youtube-video?

Regards

Mat Music
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] hagisbasheruk:
Thanks for this post Maggy , now i goto try eng 6.1 efsane that i never knew about after i figure out how to dump my current rom i have been working on and make a nk.nbf from it
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] gangstaunitg:
I just upgrade to a ''another vietnamese rom'' Heh. Now LISTEN . I never had such a stable and fast OS. Simply the SonBlacks' wm6.1 build 19202 rom is the best rom yet. trust me, I used to have a problem with starting device after softreset but it never happen to me with this rom. U should try to look at the PDAVIET hxxp://www.pdaviet.net/showthread.php?t=23970
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] zxt:
First thanks Maggy for creating this thread.

About the vietnamese rom, the start menu isn't in vietnamese I supposed?
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] gangstaunitg:
No, it's 100% translated to english.
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] BooT_SecToR:
Help Me PLZ!!

Everytime when I try to upgrade my MDA II It always shows #101 Connection Error.. Does somebody know what can I do?
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
First of all..welcome to the xda Team "Boot Sector"..This is not the place to post your problem..you could try posting it in Released ROM's Thread so you may get all the help you need..this thread is to let every new member like your self to know which ROM is where..as for your problem

Solution :

1. ALWAYS CHECK THE HIMALAYA WIKIBEFORE ASKING ANY QUESTIONS..MOST OF THE ANSWERS ARE THERE

2. First Make a search regarding your Problem..maybe its already solved someplave else..or there might be a group of people who are having the same problem...you would get a lot of help this way

Since Error # 101 is a "Connection Error..there might be few possiblities :

1. You have connected your USB cable in a place other than your PC's Back USB Port ( e.g a hub or at your Casings Front Port )..try connecting it Directly to your computer at the Back Port ( more power )

2. You can also get this error if Your Connector at the bottom is Broken or is not properly working

3. If you are running Windows Vista..then there is a driver Problem..go here to Fix that ( thanks Maggy )

Happy Flashing :)
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Maggy:
I believe that Vista gives Connection Error as well. Use Windows XP with ActiveSync 4.5 instead.
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
woops..thanks for that maggy

though there is a solution to flash on vista also ( i have done it )...will add the solution once i finish my dinner
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] swampy395:
rom

Hi maggy

This is my ROM and a link for it thanks

HTC Style 19213(build 19213.1.0.4) 61 MB RAM, 32 MB RAM disk Test built

http://www.4shared.com/account/dir/7830949/6028aa9f/sharing.html?sId=1d8vQOjFQPo5aO2p

Thanks

Swampy395
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
My Latest ROM

Ather's WM 6.1 " Dark Edition "
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
Here's My Other WM 6.1 ROM Titled " Ather's Diamond Edition"

Get It Here
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] SilverWolf:
S200 Mobile

Can some one tell me how can i update my windows mobile 5 to WM6.
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Deleted member 1104853:
ghi. you can find Wmobile 6 here http://rapidshare.com/files/132676968/WM6.rar

If you don't know how to upgrade from WM5 to WM6 you can get guide here http://rapidshare.com/files/135256906/Upgrade_from_WM5_to_WM6.txt

you may want this http://rapidshare.com/files/132351896/PhonePad.cab copy it to your PDA and run it from ur PDA

--------------------------------------------------------------------

If you would like to upgrade from wm6 to wm6.1 follow thi guide http://rapidshare.com/files/135263239/upgrade_to_Wm_6.1.txt and download WM 6.1 here http://rapidshare.com/files/135254669/WM_6.1_Shadow_TE_My_Edition_new_start_menu_.rar

--------------------------------------------------------------------

After upgraded to WM 6.1 if u don't like the SMS mode you can disable it here http://rapidshare.com/files/135261985/Disable_sms_threading_in_WM6_1.CAB to the normal mode

you may want to download this too http://rapidshare.com/files/135262025/Enable_sms_sent_notification.CAB

copy them to your PDA and run them from ur PDA

---------------------------------------------------------------------

check those powerful softwares

Enjoy
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] SaBo:
@ Odivelas_H21

Please remove your warez links as warez is not tolerated in this forum.

Thanks

Sascha
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Maggy:
First Post edited, List Categrized :)
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] agpm80:
Bluetooth modem connection problem

Hi again.

I've installed WM6 5.2.1908 build 18508.0.7.0 STk.

This on Qtek 2020.

I've a Nokia 6110 Navigator with Symbian.

I want that Qtek 2020 use the UMTS connection of the Nokia phone.

The nokia phone already works with internet connection with its SIM card (Wind Italy).

So I add a new modem connection

I select the bluetooth modem option

I select the bluetooth device in the list

I input the number to digit (in this case: *99***1# or *99#)

After that I click on next next next and I try to use the new internet connection.

The Qtek 2020 establish the bluetooth connection with the Nokia 6110.

On the Nokia's display I see the internet connection icon but after 1-2 seconds the internet connection go down.

Please note that on Nokia 6110 Navigator the "remote SIM" option in bluetooth administration is enabled.

The problem on WM6 on Qtek 2020, I think, is that I cannot specify the APN string: +cgdcont=1,"IP","internet.wind" :(

This string is specified in Windows 98/ME/XP/VISTA when you want to use a mobile phone as modem. :D

How to solve this problem?

Thanks.

See you.
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
another ROM Added in the first post :)
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] efsane:
Thanx ather90 :)
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] kinderenh:
Dear mods,

Could you add sun_dream's ROM in the first post?

http://xdaforums.com/showthread.php?t=405690
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
Done, Sonblacks ROM Added to First post under English ROMs
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
Two More ROM's added in the First Post, Catg. English
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Johan1971:
Hi,

Since a couple of day's I'm using the HTC Touch Pro T7272. I got the phone at T-Mobile and it is sim unlocked. No actually I got used to the Himalaya ROM Version: CRCs PHKv12r9 with radio version 1.47.00.10 (sorry if I appear old fashioned).

However I really like the speed of this version and the way it works. Now I wonder if it is possible to run this ROM also at a T7272. Anyone experienced with this?

I managed to get Energy Rom 1.2 working on the T7272 but the handling is even slower than my old HERM300!

Anyone with good advice?

Thank you in advance and

best regards,

Jo.
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Nokser:
Hi ather90, You add my polish version ROM

THX
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
no problems, i will ASAP
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
WinMoB 6.5 OS 5.2.21139 Build 21139 - WWE - Beta Test - NOK

WinMoB 6.1 ProEdition OS 5.2.21109 Build 21109.2.1 PL

added to first post ;)
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Nokser:
Yes I see, very THX my friend
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
Ather's Dark Edition German WM6.1 with UC - Fully loaded!

added to first post :)
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] fiq192:
o2 xda ii mini

is the rom working in o2 xda ii mini??
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] fiq192:
is the rom working in o2 xda ii mini