yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] LeLapinVengeur:
Untouchable,

Apparently you've created a great tool!

Have you think about a linux version? :)
[Touch Diamond, MDA Compact IV ROM Development] whylessfone:
I am adjust setting on after installing android such as fonts and personalization the menu. Then i reset again and when i install android again the message program shows error.
[Touch Diamond, MDA Compact IV ROM Development] whylessfone:
I had to reformat the memory card and now messaging works but the keyboard does not work. I cannot type using the qwerty keyboard, only can type with on screen keyboard
[Touch Diamond, MDA Compact IV ROM Development] mitpianoman:
I'm glad to see some discussion around the color issues on RAPH800. I'm new to the project, and despite my best digging, I haven't found too much info on current efforts to resolve the issue. I've started to look into it myself, but haven't gotten too far. I do believe it to be upstream of android, if only because the color issues show up in the penguin image straight after launching from HaRET, well before android has even loaded. I'm still trying to set up a development environment to look into it some more, but if anyone has any pointers or if this is something already being worked on please let me know.
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Havent thought about it I'm afraid :)

Speaking of which, a new version of the tool is out.. Added a "latest build" checker and a few minor fixes!
[Touch Diamond, MDA Compact IV ROM Development] pl_levy:
Android on Asus P535:

http://sites.google.com/site/siteofhx/Home/android
[Touch Diamond, MDA Compact IV ROM Development] seanmd:
As best as I've been able to glean from irc the problem with the 500/800's is in properly initializing their video and touch screens. I'm interested in working on this too, but I'm a lowly web programmer and my eyes unfocus violently when i try to parse a kernel dump. Good luck on it, and let me know what and if you find anything.
[Touch Diamond, MDA Compact IV ROM Development] excepti0n:
Hm that seems to be android running inside of an emulator...

Are there any valiant effort to doing a full OS based transistion?
[Touch Diamond, MDA Compact IV ROM Development] thevery:
it is not emulator, it is haret ;)
[Touch Diamond, MDA Compact IV ROM Development] skiwithpete:
Linux version for the linux version of the phone.... makes sense....

:)
[Touch Diamond, MDA Compact IV ROM Development] danielmtz:
Got it working on my diamond just that the screen is all mest up, all this different colors.
[Touch Diamond, MDA Compact IV ROM Development] darkpedro43:
I don't really understand why the WIKI is not updated regulary.

In this thread, the dev are discuting between them (sorry for my english, I speak french) and the lambda users, don't really understand all that "technology".

I prefer go to the wiki page and download the latest package "ready for use" and test...

Thnks
[Touch Diamond, MDA Compact IV ROM Development] Kevbodian:
I think because the people working on this project are busy enough as it is with whatever else their lives require of them. If they were, however, getting paid to do this on a full-time basis, I believe the wiki would be in a different state.
[Touch Diamond, MDA Compact IV ROM Development] saudoo:
Great!

So I downloaded the latest build for the Diamond. Got it up and running, but got stuck at the "Enter sim pin" part. I now remember that I entered the wrong pin, which I at that time remembered to be something else. Anyways. I remembered that I had read about disabling the pin om WM6.1 to be able to skip that part on Android.

I couldn't find an option for that, so I turned off my Diamond, turned it back on and got to the file manager from the start menu, before I had entered the pin. I fired up Haret.exe only to get the "missing certificate" error. Damn!

Anyways.. I'm thrilled about how much work has been done on this project so far. And I'm really looking forward to get this WM6.1 off my Diamond, any time soon! :)
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
It is as you say, you have to disable your PIN protection before booting Android (in Windows Mobile you go to Settings and Security if I remember correctly).

Regarding the Wiki, I would say that its fairly updated as it is. Most of the progress is noted there as well as a nice FAQ-section containing most problems people here ask about. The problem isnt that the Wiki isnt updated, but that people here isnt reading it. If they had, people woulndt still be asking why the PIN-code doesnt work, how to shut down Android or if booting Android will damage their Windows Mobile ROM.

So I suggest reading the Wiki before complaining about how bad it is. Links to the latest builds are there, and now you can even download the Android Config Tool I made, where you can check for new Android builds for both the Diamond and the Raphael. Cant really think of anything more anyone needs ^^
[Touch Diamond, MDA Compact IV ROM Development] saudoo:
Yeah.. well it's for no use to me at this point. I'm stuck at the certificate error, as I told before. Just wanted to let you guys know in case it would keep others from doing the same thing...

Btw.. Setting doesn't contain an element nor tab called security. :\ Hm..
[Touch Diamond, MDA Compact IV ROM Development] MrFeetio:
Wireless

The wiki says wifi, bluetooth, gprs, etc don't work, but i see no mention here of people working on it. I don't have the skills to help with that.

Is there someone working on that and do they want food money?
[Touch Diamond, MDA Compact IV ROM Development] be0ne:
In WM go to : settings > telephone > PIN code tab =)

Untouchab1e > Thanks for the Android Conf Tool, works just fine :D
[Touch Diamond, MDA Compact IV ROM Development] foh1981:
Documentation in open source projects can sometimes be lacking and out of date. To some extent that's understandable, especially if it's active and ongoing development without official releases. I don't think it's too much to ask for that whoever do a release also updates the wiki with whatever information that person has (hopefully that also eliminates some of the questions popping up in this thread all the time). But developers shouldn't have to update whatever they're working on in between releases. Non-developers need to realize that even though the wiki isn't updated daily, development can and probably is going on anyway. And also, the wiki is open to everyone. Do you have information that's not there, then you should put it there!

Should non-developers need more information, I'm sure there's a svn/git/cvs you can check out and read the comments there, instead of waiting to get spoon-feed with the information ;)
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
People are working on it, trust me. The WiFi driver is unfortunately closed source and basically it means we have to write out own. I havent been able to check out irc this weekend so I am not 100% up to date on the latest progress. But progress is being made!

People who crave technical details regarding the development should pop in #htc-android on freenode!

I think the wiki documentation is sufficient. There hasnt been any major breakthrough worth writing about there these last couple of days, and as of such the wiki hasnt been updated either ;)
[Touch Diamond, MDA Compact IV ROM Development] oaa8:
I Just thought of an Idea for Untouchab1e's configuration tool. If it was possible to make a version that runs on the actual device in windows mobile, maybe add a pre-calibrator so that the screen calibration that is done during the booting process can be automatically added to the default.txt. Just an idea I had and I don't know whether it's even possible but if it is, it could be a nice addition.
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Thanks for the idea! Il look into it
[Touch Diamond, MDA Compact IV ROM Development] c4software:
I'm acctualy try to installing application in Android... But i didn't find any way to put it inside android.

But in vogue forum dzo, i find an solution (throught an folder in SDCard).

Anybody have contact with im to ask who he get it ?
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
/tmp/newapps/

If you can mount your system or data image on a host, you can copy your app to /system/app/ or /data/app/ It will show up in your applications menu when you boot android.

It wouldn't be too difficult to have the boot process automatically copy from some folder though. I shall play with that.

Update: This set does that (40M!). It is Android from 09/01/26 and a .25 kernel with navi pad and keyboard backlight. (If you don't have a Raph100 you may^H^H^Hwill need to try a different kernel and /or modify msmsdcc_id and msmts_calib in default.txt .. or maybe Untouchab1es app takes care of that?) Inside the tmp folder, next to the images and the boot folder is a newapps folder. Before Android is started, *.apk from that folder is copied (not moved) into /data/app/ and should show up in the apps menu once Android has started. Enjoy.

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] Neo+6210:
Hi!!

Excellent thread.

I have DIMA 140. I had tried this "connect-utb.com" but after start it shows screen for some time and then blanks off. Leaving only option to remove battery and put it back. Any help?

Thanks...
[Touch Diamond, MDA Compact IV ROM Development] sibbor:
Thanks for the tip. Will try to get this working on my DIAM100.

EDIT: I was not able to boot into Android with my DIAM100. Tested with ActiveSync disabled and enabled + soft reset the device everytime the device hung at mmcblk0.

set MTYPE 1910
set KERNEL zImage.25-jobo
set INITRD root.cpiogz
set RAMADDR 0x10000000

# Tested with the following lines:
set cmdline "mem=76MB msmsdcc_id=2 msmts_calib=0x7a.0x5e.0x35a.0x37f"
set cmdline "mem=76MB msmsdcc_id=2"
set cmdline "mem=64MB msmsdcc_id=2 msmts_calib=0x7a.0x5e.0x35a.0x37f"
boot

The folder structure have changed a bit since last time I tested a build for my DIAM100, but I guess it's correct to keep the structure as in the ZIP file an starting hARET from : \Internminne\tmp\boot\haret.exe with all image files in \Internminne\tmp\

msm_i2c msm:_i2c.0: Error during data xfef (-5)
_micropksc_read: error while asking for data address 67, 10: -5
msm_i2c msm:_i2c.0: Error during data xfef (-5)
_micropksc_read: error while asking for data address 67, 11: -5
msm_i2c msm:_i2c.0: Error during data xfef (-5)
_micropksc_read: error while asking for data address 67, 10: -5
msm_i2c msm:_i2c.0: Error during data xfef (-5)
_micropksc_read: error while asking for data address 67, 11: -5
(...)
microp-klt: This hardware is not yet supported: 0b01
micrsp-klt: probe of 0-0066 failed with error -524
(...)
microp-keypad: Initalizing MicroP keypad driver
microp_keypad_probe done
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
(...)
mmc0: new MMC-card at address 0001
mmcblk0: mmc0:0001 000000 3932160KiB
mmcblk0:
_

... and the device gets unresponsive and soft reset is required.
[Touch Diamond, MDA Compact IV ROM Development] c4software:
Nice JoBo, i will try this tonight on my diam100.
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Since power management isnt working, we cannot wake up the device yet. So to solve your problem (a workaround at least), is to go into settings in Android, then disable the screen timeout. This will make the screen stay on constantly. This will let you explore Android without worrying about the screen timeout!

Good luck ;)

EDIT: Uploading the new Android package for Raph100 from j0bo now :) Check Connect-utb.com within the hour, or use the Android Config Tool "latest Raph build check" feature.

EDIT2: Package uploaded, and all channels updated (latest build checker, connect-utb.com, etc)

Download here. As noted, it has only been tested with a Raph100, so some modifications might be neccesary (msmsdcc_id = 1 for Diamond, 2 for Raph100/800 and 3 for Raph500 (and Raph110?)).

EDIT3: Also working on a significant update to the HTC android config tool. Im completely rewriting the modifying process for the Android package files so that it will be much safer and better to use (as well as some new functionality). Should be released soon
[Touch Diamond, MDA Compact IV ROM Development] TheLord-Akira:
release not for DIAM
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
I think you need to edit your default.txt in order to get it working on the diamond, considering this build is actually for the Raphael.

You definetly need to change mtype to 1805 (think its 1805 anyway, check with your previous DIAM100 build to be certain), and maybe also msmsdcc_id needs to be set to 1.

Good luck!
[Touch Diamond, MDA Compact IV ROM Development] sibbor:
From the wiki, although it was in October month: "A machine definition has been added (HTCRAPHAEL) which will both boot the Raphael and Diamond, so when booting with haret, use mtype 1910 from now on"

Of course I made changes in default.txt, that's what I showed you ;) And yes, it's 1805 in the other case... but didn't think it was needed anymore. Think I was able to get into Android with an earlier build with 1910 for my DIAM100... yes, almost 100% sure of it.

EDIT: just to make sure, tested with mtype 1805, and the device hung in WM6 loading Linux with hARET.
[Touch Diamond, MDA Compact IV ROM Development] dejant_9:
found in the latest build for diamond (connect-utb):

set mtype 1805
set kernel zImage-kll
set initrd initrd.droid.cpio.gz
set ramsize 0x6000000
set ramaddr 0x10000000
set cmdline "mem=64M [B][U]msmsdcc_id=2[/U][/B] msmts_calib=0x7a.0x5e.0x35a.0x37f"
boot

The msmsdcc_id was 2!

tested with msmsdcc_id=1 and 2 but same result on my diam100

tested with mem=64 and 72m

with and without root=/dev/ram0 init=/init console=tty0

with mtype 1805 and with 1910

with msmts_calib=0x7a.0x5e.0x35a.0x37f and msmts_calib=0x6D.0x5D.0x340.0x375

and with haret and haret 18...I can't run the latest jobo's build (zImage.25-jobo) on my diam100!
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Im not quite sure how to make it work with the Diamond yet.. I have to read up on the Wiki and git a bit.

I can confirm it boots out of the box just fine with my Raph100.
[Touch Diamond, MDA Compact IV ROM Development] TheLord-Akira:
tested with following conf

mtype 1910

ramaddr 0x10000000

ramsize 0x6000000

mem=64m

msmsdcc_id=2

with activesync hangs on "ether_configure () 1

without activesync hangs on "mmcbalk0:unknown partition table
[Touch Diamond, MDA Compact IV ROM Development] c4software:
@sibbor and dejant_9,

Same problem for me, like the previous kernel.

Maybe its due to an drivers differences between raphael and diamond.
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
I don't know why recent Raphael kernels don't boot on Diams. It used to work with just changing the MTYPE. Use some other kernel that does boot on Diams. :o This mechanism that copies new apps from your SD card into android should work regardless.

Another thing is that the init script tries to mount /dev/mmcblk0p1 which is correct for the 1st partition on the micro sd card on Raphs, but not for Diams. I have now modified the init script to take the device name, minor number and path to images from the command line in default.txt so that the same root fs can work for multiple devices.

[I]in default.txt: (where you specify what to mount)[/I]

set cmdline "root=/dev/ram0
init=/init console=tty0 mem=76M msmsdcc_id=2
[B]imgdevname[/B]=/dev/mmcblk0p1 [B]imgdevnum[/B]=1 [B]imgdir[/B]=/tmp
msmts_calib=0x6D.0x5D.0x340.0x375 msmvkeyb_toggle=hide"

[I]in init: (where it happens)[/I]

mknod ${[B]imgdevname[/B]} b 179 ${[B]imgdevnum[/B]}
mount -t vfat ${[B]imgdevname[/B]} /mmc
mount -t ext2 -o loop /mmc${[B]imgdir[/B]}/system.e2img /system
[...]
cp /mmc${[B]imgdir[/B]}/newapps/*.apk /data/app/
chmod 664 /data/app/*.apk

I replaced the 40M .zip with one that has updated root.cpiogz and default.txt and also put a .zip next to it with only these 2 files. You should now be able to modify the CMDLINE in default.txt to work on any Raph/Diam device. (Or Untouchab1es tool can probably use this to generate a CMDLINE in default.txt based on your device flavor. ;) Mind the leading slashes in imgdevname and imgdir...) For Diamonds you still need a kernel that boots... :p

Thanks for the confirmation :)

-Jobo

Edit: Just some clarification: This does

not

(yet) change anything. Out of the box the behaviour should be the same as before. If the previous package didn't work for you, then this one won't either, but it is now possible to specify some stuff from the CMDLINE that would previously require modification of your root fs. You need to find the right combination of kernel and CMDLINE settings to run on other devices than Raph100.
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
If someone can test and confirm that they have it booting on their Diamonds, il put it up on Connect-utb ;)
[Touch Diamond, MDA Compact IV ROM Development] sibbor:
So you don't think your latest kernel will work on DIAM100 at all? Haven't been able to get into Android with your new files either... I'll give it a few more shots, but it does not look good so far; same errors as before.
[Touch Diamond, MDA Compact IV ROM Development] tmcookies:
me too! i tried changing msmsdcc_id to 3 but to no avail..
[Touch Diamond, MDA Compact IV ROM Development] dejant_9:
@Untouchab1e:

i've some problems with your android_configurator, i can't extract it. "End-of-central-directory signature not found. Either this file is not a Zip file, or it constitutes one disk of a multi-part Zip file."

i've this error with winrar and winzip. with 7-zip the folder is extracted but inside ther is just an "android_configurator" file without extention. i can't run it and it don't work if i rename with the ".exe" extention before
[Touch Diamond, MDA Compact IV ROM Development] c4software:
Hmmm i try to boot the lastest version with my diam100 (using old kll kernel), that is my default.txt

set mtype 1805
set kernel zImage-kll
set initrd root.cpiogz
set ramsize 0x6000000
set ramaddr 0x10000000
set cmdline "root=/dev/ram0 init=/init console=tty0 mem=76M msmsdcc_id=2 imgdevname=/dev/mmcblk0 imgdevnum=1 imgdir=/tmp msmts_calib=0x7a.0x5e.0x35a.0x37f msmvkeyb_toggle=hide"
boot

Just like this, but its always say /dev/mmcblk0 no such device or address... Any idea ?
[Touch Diamond, MDA Compact IV ROM Development] dejant_9:
same here. are you sure about mmcblk0p2?
[Touch Diamond, MDA Compact IV ROM Development] c4software:
I edit my post after you answer. I made an mistake when i copy/past.

it's :

set mtype 1805

set kernel zImage-kll

set initrd root.cpiogz

set ramsize 0x6000000

set ramaddr 0x10000000

set cmdline "root=/dev/ram0 init=/init console=tty0 mem=76M msmsdcc_id=2 imgdevname=/dev/mmcblk0 imgdevnum=1 imgdir=/tmp msmts_calib=0x7a.0x5e.0x35a.0x37f msmvkeyb_toggle=hide"

boot

I try the older version and its mount on /mmc /dev/mmcblk0. I don't know whats is wrong with the default.txt;
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
try imgdevnum=0

-Jobo

EDIT: When combinations are found that work for different models, it would be nice to gather that information on the wiki..
[Touch Diamond, MDA Compact IV ROM Development] c4software:
Its works. :D Boot in progress.

What is the imgdevnum value ?

I Upload my tmp folder for the diam100

40Mb Tmp folder for Diam100

PS: @Jobo can you add in the cpio file, an folder in the / name sdcard?
[Touch Diamond, MDA Compact IV ROM Development] ododoo:
Have been reading this thread for a while now, and must say that im impressed with your work. I wish there where something i col help with, but i dont know how to code...

This last build works great on my Diamond! Can send and recive messages and call out. But no sound. Exellent work guys!
[Touch Diamond, MDA Compact IV ROM Development] setix:
Im able to boot into android on my cdma diamond, but can not get service, and the color is messed up on certain screens. could this be a problem with how many colors it is able to display?
[Touch Diamond, MDA Compact IV ROM Development] dejant_9:
hummm..very strange..maybe you can...READ THE WIKI!!!

(check my signature..)

:p
[Touch Diamond, MDA Compact IV ROM Development] sighborg:
I've started a section on the wiki for working configs ...if others want to flesh out other known working configs...that might be help others.
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Can anyone else confirm that c4software's package boots on their Diam100's?

(/me is 20 today :D )
[Realme X Questions & Answers] RyanCr7:
1)Installed TWRP 3.3 from our beloved [MENTION=4712355]mauronofrio[/MENTION]frio

2)Opened twrp,flashed superSu 2.73

Tried flashing a different version of superSu too.

3)Flashing is always successful but there's no change in the system,no root,nothing.

4)After a reboot I can't access the twrp again.It goes back to stock recovery.I have to reflash everytime I need to access twrp.

Rom Version : Latest Official A23
[Realme X Questions & Answers] mauronofrio:
Use magisk instead of supersu
[Realme X Questions & Answers] RyanCr7:
I'm using A23 build of stock rom.I have no idea how to get boot image out from an unrooted phone.Will there be any problem if I use A19 build boot image and patch it with magisk?
[Xiaomi Mi A2 / 6X Questions & Answers] yatin panchal:
Please someone make Android 10 AOSP EXTENDED ROM
[Android Q&A, Help & Troubleshooting] JohnDekka:
Hi there!

I've got a problem with my Google Play Games account in all games that require me to log in with a gaming account.

The problem persists on all custom roms I've tried (LOS16 / 17, Reloaded-CAF 10, etc.)

Here is my current setup:

Xiaomi Pocophone F1 64GB (EU)

Reloaded-CAF 10

open_gapps-arm64-10.0-nano-20191209-BETA

NoGravityKernel 1.1 - DEK200-mod

Magisk 20.1 - Ben's Thermal 5.0

See attached picture. That window is all that pops up. I can close the window by tapping beside it which shows me a list of my accounts. Selecting my account just shows me the empty window again.

So far I've tried 3 different ROMS, with OGapps and BiTGApps. Logging in/out and deleting/recreating my Google account, cleaning caches and tmp files.

The only way to use the Play Service is when using stock MIUI, which is a nogo for me. :silly:

Any ideas whats happening there??
[Android Q&A, Help & Troubleshooting] JohnDekka:
I created a new gmail account which works perfectly fine!?

Well, not a good solution, but a solution. xD
[Xiaomi Redmi Note 5 Pro Questions & Answers] Avitus88:
Hello, from few days battery in my rn5 drains in 4 hours with 50% brightness, or even faster with 100% brightness.. With normal use calling and msg only. On max brightness Gsam battery shows 1400-1650 mA usage. Battery or motherboard is dying? And I made factory reset, still same. Can any one help?
[Xiaomi Redmi Note 5 Pro Questions & Answers] JustS0meone:
What rom are you using? I had the same problem after I installed Havoc 3.0. Then wiped and flashed Ion (Android Q) no problem since...
[Xiaomi Redmi Note 5 Pro Questions & Answers] Avitus88:
Stock Rom miu11.0.3 android 9 with out root
[8125, K-JAM, P4300, MDA Vario ROM Development] pamigianleo:
Hello everyone.

For the qtek 9100 lacks a 6.1 Roma in Italian.

Currently I am using a "TNT rom", which is very fast and stable, and I want to translate it in Italian language.

Thanks to the authors for the great work

Unfortunately I have little experience and I do not know where to start.

Who can help me?

What are the appropriate tools?

What do I need?

Salve a tutti.

Sul Wizard manca una rom 6.1 italiana.

Attualmente sto utilizzando la TNT, che è molto veloce e stabile, e vorrei tradurla in italiano.

Approfittando delle vacanze potrei dedicarmi a questo progetto.

Purtroppo ho poca esperienza e non so da dove cominciare.

Chi mi può aiutare, indicandomi gli strumenti più appropriati e quel'è il percorso da affrontare?