yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] new2020yy:
Thank you very much for the detailed response.

You're right, but I didn't know what details could help and I didn't want to just throw in details. I have now downloaded CPU-Z and ADIA64. Can you please say what details are relevant?

About CANBUS - I really have. And with me the volume setting is regulated by him. But I have no idea how to tell if it's set up correctly. I just connected the unit as it came. And right I mean the wheel that is on the steering wheel and the unit itself.

In each case, I'll also include a link to the unit so you can see what it is.

https://www.aliexpress.com/item/4000059343717.html?spm=a2g16.12010612.8148356.2.585e6777jdzSLx
[Android Head-Units] surfer63:
CPU-Z and ADIA64 don't help here. They are "real" Android apps and know nothing about CANbus systems.

Sorry, but you really need to contact your supplier and ask which CANbus protocol(s) should be selected for your specific car.

For my (previous) unit and my Skoda, there was an xyz_HIGH and xyz_LOW protocol depending on the car. The HIGH protocol increased volume really fast. The LOW more slowly. This all depending on the components in the car.

I have no idea which settings your unit uses, but I have the idea that it is set to xyz_LOW, where it actually should be the HIGH protocol.

(where xyz can be any name your manufacturer has given it, and HIGH/LOW can just as wel be FAST/SLOW or anything else)
[Android Head-Units] new2020yy:
Thank you for your comment.

1. My intent of the apps to understand the system model

2. Thanks for the information. I will now search the settings for the letters XYZ

3. I can search for the model myself (even help me know a sample example to know what it looks like there is a lot of information). The seller simply does not understand and communication with him is not always good in terms of this kind. The seller is excellent, responds to everything and quickly but sometimes things like that are difficult for us to communicate.

Edit - I searched for XYZ I don't have such a function.
[Android Head-Units] surfer63:
No, it is definitely not called xyz. I said: "where xyz can be any name your manufacturer has given it"

Search on youtube for "joying canbus setting". Joying is a brand but has many systems for VW/Skoda/Seat. You will find movies for several brands. Maybe that will give you an idea.
[Android Head-Units] new2020yy:
thanks for the reply. I'll check what you said.

By the way, I tried to upload pictures to the site but somehow I couldn't ..

If you want to help me I can send pictures of the menu in any other way in private. (You are the only one who really got the closest to my point and came to this function so you have a great advantage) And if anyone else wants to try to help here or in a private message I would be very happy

https://www.youtube.com/watch?v=SltcuBqMVqA

I have an operating system just like there is in the video

Can I install an operating system like JOYING?
[Android Head-Units] BaatarkhuuTs:
I have android head unit. Do you think I can upgrade to the higher version ?

Model k2001N
[ZTE Axon 7 Mini Questions & Answers] Insane Assassin:
So there are a lot of conflicting tutorials regarding Custom Rom installation on a Axon 7 mini Android 7.1/Europe

The Zadig and Tulip route seems to be the way to go?

How do i get Zadig to recognize the phone tho. if i boot into edl via adb, the phone is not recognized (no prompt to install qualcomm drivers, zadig cant find device etc)

i´m using the original cable idirectly connected to usb.

are there other prerequisities? i remember vaguely that i had to boot into some different windows mode with my old nexus 5. is it something like this?

Please help
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] MandrakePa:
What ROM Suggest me for TYTN II ? Possibly with a Diamond's look. Thanks
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] carlos_polanco:
Start TESTING!!!

I suggest you start reading different treads and then FLASHING L26, Dutty's, and some other ROMS...

Then you decide which one fit your needs!

That's IMHO...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] DaveShaw:
I suggest you search for similar named threads. There are enough of them. And they all end the same.

Everyone prefers a different ROM's.

Ta

Dave
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] pandaboyy:
I think you mean, Which Rom

I suggest Dutty's Hybrid V2 (cube or no cube, don't go for the light version, because I found it a little messy)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] mccune:
There you go... ...I prefer the Hybrid Lite...

As you can see a useless thread. Read the threads where the ROM's are discussed. Some like screenshots, other think that the highest number is the best ROM.

Like mentioned before, everyone has it's personal favorite....
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] P1Tater:
I prefer you read the first post of each rom thread and decide from there.
[Samsung Galaxy A90 5G Guides, News, & Discussion] triggz881:
Notes: This trips KNOX so you will void your warranty, read all the steps carefully before beginning, flashing can be dangerous if you do it wrong. Don't blame me if you brick your device.

Backup all of your data and settings before starting as you will need to reset to factory defaults during this process.

With that being said, the process is relatively straightforward and easy.

PS: my device is the A908B, there is also an A908N if anyone wants to test on that be my guest.

Needed:

ADB

SamFirm

Odin

Magisk Manager

Step 1 - Downloading your firmware.

Go to SamMobile SM-A908B

Find the correct firmware for your device according to country and operator.

Note: You can use generic country firmware instead, this will remove carrier added software and limitations but may remove features and disables OTA updates.

Note the 'product code'.

Now open SamFirm.

Type SM-A908B for model

In the region box type the product code you noted earlier.

Click Check Updates.

When it has found the firmware, make sure decrypt automatically is checked and then click download rom.

The firmware is around 4gb.

Part 2 - Unlocking the Bootloader

Go to settings > about phone > software information. Hit build number a bunch of times until you activate developer options.

Go back to settings > developer options

Enable OEM unlocking

Enable USB debugging

Turn off the phone

Hold volume up and volume down whilst inserting the USB cable

This should take you to the bootloader unlock screen.

Long press Volume up to unlock the bootloader.

Part 3 - Obtaining root

After SamFirm finished downloading the rom it should have extracted it into 5 tar files.

Copy the tar file beginning with AP to your device.

Download Magisk Manager on the device and install.

Press Install on Magisk Manager

Confirm the Install

Select the option 'select and patch file', then locate the APdjkfgrsdkfhgkjrg.tar.md5 on your device and select it.

Magisk will then patch the file and dump the patched version to your phone.

Copy the patched.tar to your PC

Reboot phone into download mode

Open Odin

For BL use the BL.tar.md5 file from stock firmware

For AP use the patched.tar file

For CP use the CP.tar.md5 file from stock firmware

For CSC use the CSC.tar.md5 file from stock firmware (not the CSC_HOME)

Press Start and wait for it to flash

After flashing, the phone will reset.

After initial setup, install magisk manager again.

Remove the USB cable and turn off the phone.

Turn on the phone by holding volume up and power, let go when you see the bootloader warning.

Open Magisk Manager Click Install.

Phone is now rooted.

Note: Powering on the device normally will disable root, you must hold volume up to power on the device to activate root.
[Samsung Galaxy A90 5G Guides, News, & Discussion] rommy667:
Awesome job thanks a lot :)
[Samsung Galaxy A90 5G Guides, News, & Discussion] triggz881:
Going to put a few hours into compiling twrp tonight but this might take me forever, I'm really busy with work and I got 2 kids too so free time is scarce. So feel free to have a go at it yourself.
[Samsung Galaxy A90 5G Guides, News, & Discussion] Hunteres:
After root activation with the volume button start up will the root persist? Can the device be restarted without any hidden key?

Thank you
[Samsung Galaxy A90 5G Guides, News, & Discussion] triggz881:
Yes the root persists, but every time you turn the phone off and back on again you will have to hold up to activate the root. Resetting the phone while root is enabled does not disable it though iirc.

More work done on twrp last night, nearly ready to attempt compiling.

Edit: So I made a device tree and compiled twrp fine. Unfortunately it needs a custom kernel to be able to boot. Working on this now.
[Samsung Galaxy A90 5G Guides, News, & Discussion] johnoponi:
Any further progress??
[Samsung Galaxy A90 5G Guides, News, & Discussion] triggz881:
No not really. I need to reach out to the twrp Devs of the S10 and see what modifications they did to theirs, but super busy at the moment. Sorry.
[Samsung Galaxy A90 5G Guides, News, & Discussion] triggz881:
Ok so I made a lot of progress since last post. I'm compiling the kernel as I type. But the process takes a long time. If we are lucky it will boot twrp straight away if not I'll keep at it until I manage.
[Samsung Galaxy A90 5G Guides, News, & Discussion] alibenkenobi:
Are you still trying?
[Samsung Galaxy A90 5G Guides, News, & Discussion] jasonc417:
Failure on Model SM-A9080 (China Version)

Today I did this on model SM-A9080 but unluckily failed, and the OS could not be loaded, with boot loop on the phone.

Really the specified TWRP should be developed.
[Samsung Galaxy A90 5G Guides, News, & Discussion] Steveee101:
Hey - did you manage to get anywhere with this? If you'd like help, i'd be happy to get stuck in. Could you put the code on Github?
[Samsung Galaxy A90 5G Guides, News, & Discussion] Tsunami_HD:
Hello,

I tried to root my phone today, and I followed every step exactly, but now I am stuck in a Boot Loop, after the Step of Flashing. Can someone help, or knows why this happened? Thank you.

---------- Post added at 07:48 PM ---------- Previous post was at 07:03 PM ----------

Okay I fixed it myself. The Problem was, I only Flashed the BL File. After that I flashed the other files one by one, did a Factory Reset in Recovery mode and now it worked! I even have root now.
[Samsung Galaxy A90 5G Guides, News, & Discussion] xijaw:
Do we have a custom rom yet? Can't stand the samsung rom or whatever its called.
[Samsung Galaxy A90 5G Guides, News, & Discussion] Srbija2012:
So why did you buy a Samsung.
[Samsung Galaxy A90 5G Guides, News, & Discussion] underdog_656:
Lmao, true. He could of easily went for one plus etc..

And bull****, Samsung ui is definitely top it's really nice.. just the notifications could be improved
[Samsung Galaxy A90 5G Guides, News, & Discussion] xijaw:
I live in Australia and here we don't have a market like Europe and India. We only have couple of brands- Apple and Samsung.

---------- Post added at 01:31 PM ---------- Previous post was at 01:30 PM ----------

Lets stick to the topic and get the damn custom rom built. Aren't there any devs who willing to take A90 as a project ?
[Samsung Galaxy A90 5G Guides, News, & Discussion] kaison320:
can you get the ctsprofile pass in the magisk manager？
[Samsung Galaxy A90 5G Guides, News, & Discussion] kaison320:
can i ask you whather you can get the cts profile pass or false or not after you root by magisk？
[Samsung Galaxy A90 5G Guides, News, & Discussion] MarcTR:
Hello please can someone help me root this phone, i have followed the steps but i just seem to be missing something so can someone take me through this step by step for a dumb person like myself lol?

At first i was struggling with part one of this tutorial but once i updated samfirm i was able to download it without a problem. moving over to the last step which is using odin to do its thing with the tar files and upon finishing where it should reboot it is stuck into a boot loop saying "this phone is not running samsungs offical software", i am not sure what i am missing and i am able to fix the phone without any problems but no root is achieved
[Samsung Galaxy A90 5G Guides, News, & Discussion] ZemoDroid:
Hello. May I ask about the progress on TWRP for this phone?
[Samsung Galaxy A90 5G Guides, News, & Discussion] kaison320:
i also want to ask the TWRP for this phone but it seems that there is no one work on it.:crying:
[Samsung Galaxy A90 5G Guides, News, & Discussion] xijaw:
@triggz881 hey man, if you need any help please let me know. My phone is available for testing.
[Samsung Galaxy A90 5G Guides, News, & Discussion] Vman4217:
Im looking for the cf root file for the SM-A908B 5G
[Samsung Galaxy A90 5G Guides, News, & Discussion] xijaw:
Guys, go to other forums and request the devs to help us. My phone is available for testing
[Huawei Mate 30 Pro Questions & Answers] randomdude1213:
Can someone explain why this happens?
[Huawei Mate 30 Pro Questions & Answers] paullu:
what？
[Huawei Mate 30 Pro Questions & Answers] drzewoid:
Send post to official huawei forum - maybe they will know more about this issue.
[Huawei Mate 30 Pro Questions & Answers] cfds:
Don't see any weird tint at your picture...
[Samsung Galaxy Watch] sony raj:
Hi all can somebody help installing Samsung Pay for India

I connected watch through sdb connect and when i run

command launch_app csc-manager.csc-pre-configuration it says successfully launched but nothing happens on my Galaxy Watch verion R800XXU1DSL1 tizen 4.0.0.7

Used SDBstarterKidv1
[Samsung Galaxy Watch] adfree:
Downgrade...

https://xdaforums.com/smartwatch/galaxy-watch/update-gw-r800-t3936370

Simple use older Firmware as DRK2... DSL1...

If you choose XAR for USA... then choose this Firmware:

R800XXU1[B][COLOR="Green"]CSE1[/COLOR][/B]

IMHO here SDB Commands still work...

In theory somehwere Thread or Post...

In newer Firmware like DSL1 Samsung increased Security... :rolleyes:

Best Regards
[Samsung Galaxy Watch] sony raj:
After downgrade and changing the region to enable Samsung pay.

If I again update to the latest firmware version will the Samsung pay still be there?
[Samsung Galaxy Watch] congusto:
Yes, if you changed the CSC to get Samsung Pay, it will still be there after an update. As far as I know, the availability of Samsung Pay is CSC bound, not firmware bound.
[Samsung Galaxy Watch] sony raj:
i downgraded changed the CSC, now samsung pay is on the watch but it wont open on my phone
[Samsung Galaxy Watch] yager01:
I have a same problem too. "successfully launched" but nothing happend :(

R805FXXUFSK2

SM-R805FZSATMH

The downgrade is it the solution for me ? Which version ?
[Samsung Galaxy Watch] adfree:
Good question... according to your "incomplete" info... your active CSC could be TMH...

Then it seems OXA region.

R805FXXU1FSK2/R805F[B]OXA[/B]1FSK2/R805FXXU1FSK2

To be sure... simple enter magic Code:

*#1234#

And compare with my text...

Best Regards
[Samsung Galaxy Watch] yager01:
My CSC with the magic code is R805FOXA1FSK2

AP: R805FXXU1FSK2

CP: R805FXXU1FSK2
[Samsung Galaxy Watch] ArthurMedeiros:
Hi guys, I'm from Brazil, and my FW is the R810XXU1DSL1.

I need to change the csc to ZTO... same problem, nothing happens.

Can some one help me?

What downgrade do I have to do?
[Samsung Galaxy Watch] congusto:
You need to downgrade to any firmware older than DSL1 with NetOdin, as described elsewhere on this forum. Then changing the CSC will work.
[Samsung Galaxy Watch] deejah:
Hi. I have the same problem. I'm now going to downgrade with the procedure in this topic.

I just have a doubt about which firmware I should use. This are my current info:

Watch: SM-R800

One UI: 1.5

Tizen: 4.0.0.7

Current FW: R800XXU1DSL1

Knox: 2.4.0

Bought on USA

Need to enable Samsung Pay in Brazil (I believe need to be changed to ZTO)

Can someone please which firmware I should try? First and second options?

Thanks.
[Samsung Galaxy Watch] rjacc:
any update yet guys

i am stuck with tyhe same problem.is there a way solution yet?
[OnePlus 6T  Questions & Answers] Michael_Raj:
After updating the mobile to 10.3.0 the touch seems to not working properly at soemtimes, and phone hangs while playing games NFS Most wanted, i cant play car is moving like snail, The properly and fast working games are slow after this update. Please anyone let me know how to fix it. Or how to roll back to previous version.
[OnePlus 6T  Questions & Answers] RANJITH kumara:
same problem , after updating my 6t mobile os 10.3.0 my mobile is getting hanging even in wats app also cant text fast and while using gallery also my phone is getting hanging what is the solution for this. this issue is coming only after updating the new OS 10.3.0
[OnePlus 6T  Questions & Answers] Michael_Raj:
Have you tried to message in oneplus community, I have tried to post about this problem but i cant post this? I don't no why?
[Touch Diamond, MDA Compact IV ROM Development] theloanranger:
Changes between TLR ROM (UK 1.37.405.1 based) and the ME ROM are in bold below.

TLR ROM will have these changes shortly rolled out OTA.

Perhaps one of these has 'the memory leak'?

ME ROM vs TLR DIAMOND

Labyrinth="1_3_5221602_0"	vs	Labyrinth="1_3_5221602_0"

AudioManager_Eng="1_5_18161432_0"	vs	AudioManager_Eng="1_5_18161432_0"

QuickGPS="1_00_18152630_0"	vs	QuickGPS="1_00_18152630_0"

EzInput="1_5_31365_0"	vs	EzInput="1_5_31365_0"

RandomAccess="4_0_18133030_0"	vs	RandomAccess="4_0_18133030_0"

LockStreamDRM="1_1_080411_O9_Diamond_12"	vs	LockStreamDRM="1_1_080411_O9_Diamond_12"

LongPressEndKey="1_1_34078_1"	vs	LongPressEndKey="1_1_34078_1"

RingtonePlugin="1_00_080416_1"	vs	RingtonePlugin="1_00_080416_1"

PhoneCanvas="3_50_31308_4"	vs	PhoneCanvas="3_50_31308_4"

FMRadio="1_6_18161621_1"	vs	FMRadio="1_6_18161621_1"

ShareDLL="2_0_071002_00v2"	vs	ShareDLL="2_0_071002_00v2"

SmartTouch="1_0_31096_0"	vs	SmartTouch="1_0_31096_0"

AudioBooster="2_0_18143227_4"	vs	AudioBooster="2_0_18143227_4"

DShow="2_00_080526_0"	vs	DShow="2_00_080526_0"

mHub="6_54_080121_E1"	vs	mHub="6_54_080121_E1"

EnlargeStartMenu="1_2_34318_100"	vs	EnlargeStartMenu="1_2_34079_1"

TaskManager="2_1_34318_100"	vs	TaskManager="2_1_34308_100"

BTBPP="1_6_5_0"	vs	BTBPP="1_6_5_0"

BTSAP="3_1_0_0R2"	vs	BTSAP="3_1_0_0R2"

PlayShow="1_0_18153930_0"	vs	PlayShow="1_0_18153930_0"

CAMERA="6_00_31364_00"	vs	CAMERA="6_00_31364_00"

TouchFlo="3_0_29946_37"	vs	TouchFlo="3_0_29946_37"

BTFtp="1_2_33281_91"	vs	BTFtp="1_2_33281_91"

Album="2_0_18161424_1"	vs	Album="2_0_18161424_1"

AdobePDF="2_5_103000_60R2"	vs	AdobePDF="2_5_103000_60R2"

JbedJava="0_0_20080418_2_1"	vs	JbedJava="0_0_20080418_2_1"

StreamingMedia="3_0_18153213_00"	vs	StreamingMedia="3_0_18153213_00"

ConcurrenceMgr="1_1_18143521_0000"	vs	ConcurrenceMgr="1_1_18143521_0000"

Arcsoft_MMS="5_0_27_25"	vs	Arcsoft_MMS="5_0_27_25"

YouTube="1_0_1816_2629"	vs	YouTube="1_0_1815_3318"

VideoTelephony="2_0_31227_0"	vs	VideoTelephony="2_0_31227_0"

USBToPCPopUp="1_0_18143432_1"	vs	USBToPCPopUp="1_0_18143432_1"

ZIP="1_21_18141127_1"	vs	ZIP="1_21_18141127_1"

PictureEnhancement="1_50_18131521_c2"	vs	PictureEnhancement="1_50_18131521_c2"

FullScreenPlayer="1_05_080602_0"	vs	FullScreenPlayer="1_05_080602_0"

OutlookEnhancement="1_0_33540_3"	vs	OutlookEnhancement="1_0_33540_3"

MP3Trimmer="1_1_18143421_2"	vs	MP3Trimmer="1_1_18143421_2"

VoiceRecorder="1_10_18151728_0"	vs	VoiceRecorder="1_10_18151728_0"

SensorSDK="3_3_18153516_0"	vs	SensorSDK="3_3_18153516_0"

VolumeControl="1_0_18162230_0"	vs	VolumeControl="1_0_18151630_0"

HTCGesture="1_0_30346_1"	vs	HTCGesture="1_0_30346_1"

XT9_IME="1_5_31456_0"	vs	XT9_IME="1_5_31250_0"

ConnectionSetup="1_5_34057_2"	vs	ConnectionSetup="1_5_34057_2"
[Touch Diamond, MDA Compact IV ROM Development] TechMan™:
Good job Man .
[Touch Diamond, MDA Compact IV ROM Development] alipi2007:
thanx.

can say almost same....
[Touch Diamond, MDA Compact IV ROM Development] ceevee369:
I used TLR's Apptodate in his first release and installe the Middle East enhancements.

I am not sure about the leak, but it looks promissing. Program storage varies constantly between 48 and 45 MB when starting up and x-closing applic's.

To watch closely and if someone can confirm leak closed, we have a winner here !
[Touch Diamond, MDA Compact IV ROM Development] faethon:
It may make sense to do a similar job on the Asian 707 ROM, to see if there are even newer versions of the components included. Did you do a manual check of all versions? I have the 707 ROM and may attempt to make a similar list for the 707 ROM.
[Touch Diamond, MDA Compact IV ROM Development] theloanranger:
Definitely sensible.

If you get a registry editor and visit \HKLM\Software\OEM\MASD (I think it was), you can check the list there against what you see here.
[Touch Diamond, MDA Compact IV ROM Development] faethon:
I've checked the versions of my 137.707.1 ROM, and it looks like there is actually a lot of older components in there, despite it's version number being higher:

1.37.707.1 ROM vs TLR ROM

Labyrinth="1_3_5221602_0" vs Labyrinth="1_3_5221602_0"

AudioManager_Eng="1_5_18152331_1" vs AudioManager_Eng="1_5_18161432_0"

QuickGPS="1_00_18152630_0" vs QuickGPS="1_00_18152630_0"

EzInput="1_5_31226_0" vs EzInput="1_5_31365_0"

RandomAccess="4_0_18133030_0" vs RandomAccess="4_0_18133030_0"

LockStreamDRM="1_1_080411_O9_Diamond_12" vs LockStreamDRM="1_1_080411_O9_Diamond_12"

LongPressEndKey="1_1_34078_1" vs LongPressEndKey="1_1_34078_1"

RingtonePlugin="1_00_080416_1" vs RingtonePlugin="1_00_080416_1"

PhoneCanvas="3_50_31228_1" vs PhoneCanvas="3_50_31308_4"

FMRadio="1_6_18161621_1" vs FMRadio="1_6_18161621_1"

ShareDLL="2_0_071002_00v2" vs ShareDLL="2_0_071002_00v2"

SmartTouch="1_0_31096_0" vs SmartTouch="1_0_31096_0"

AudioBooster="2_0_18143227_3" vs AudioBooster="2_0_18143227_4"

DShow="2_00_080526_0" vs DShow="2_00_080526_0"

mHub="6_54_080121_E1" vs mHub="6_54_080121_E1"

EnlargeStartMenu="1_2_34070_1" vs EnlargeStartMenu="1_2_34079_1"

TaskManager="2_1_34077_100" vs TaskManager="2_1_34308_100"

BTBPP="1_6_5_0" vs BTBPP="1_6_5_0"

BTSAP="3_1_0_0R2" vs BTSAP="3_1_0_0R2"

PlayShow="1_0_18153930_0" vs PlayShow="1_0_18153930_0"

CAMERA="6_00_30998_01" vs CAMERA="6_00_31364_00"

TouchFlo="3_0_29946_37" vs TouchFlo="3_0_29946_37"

BTFtp="1_2_33281_91" vs BTFtp="1_2_33281_91"

Album="2_0_18152532_3" vs Album="2_0_18161424_1"

AdobePDF="2_5_103000_60R2" vs AdobePDF="2_5_103000_60R2"

JbedJava="0_0_20080507_1_1" vs JbedJava="0_0_20080418_2_1" (it's actually called JBlendJava)

StreamingMedia="3_0_18153213_00" vs StreamingMedia="3_0_18153213_00"

ConcurrenceMgr="1_1_18143521_0000" vs ConcurrenceMgr="1_1_18143521_0000"

Arcsoft_MMS="5_0_27_25" vs Arcsoft_MMS="5_0_27_25"

YouTube="1_0_1815_3318" vs YouTube="1_0_1815_3318"

VideoTelephony="2_0_31227_0" vs VideoTelephony="2_0_31227_0"

USBToPCPopUp="1_0_18143432_1" vs USBToPCPopUp="1_0_18143432_1"

ZIP="1_21_18141127_1" vs ZIP="1_21_18141127_1"

PictureEnhancement="1_50_18131521_c2" vs PictureEnhancement="1_50_18131521_c2"

FullScreenPlayer="1_05_080526_0" vs FullScreenPlayer="1_05_080602_0"

OutlookEnhancement="1_0_33540_3" vs OutlookEnhancement="1_0_33540_3"

MP3Trimmer="1_1_18143421_0" vs MP3Trimmer="1_1_18143421_2"

VoiceRecorder="1_10_18151728_0" vs VoiceRecorder="1_10_18151728_0"

SensorSDK="3_3_18153516_0" vs SensorSDK="3_3_18153516_0"

VolumeControl="1_0_18151630_0" vs VolumeControl="1_0_18151630_0"

HTCGesture="1_0_30346_1" vs HTCGesture="1_0_30346_1"

XT9_IME="1_5_31250_0" vs XT9_IME="1_5_31250_0"

ConnectionSetup="1_5_34057_2" vs ConnectionSetup="1_5_34057_2"
[Touch Diamond, MDA Compact IV ROM Development] ceevee369:
I get confused now... 707 is not the ME one no? I though TLR used 456 to optimize his ?
[Touch Diamond, MDA Compact IV ROM Development] faethon:
No, there are 3 'official' ROMs here with major number 1.37:

the 405, which is the basis of the

TLR ROM

the 456, which is the ME (Middle East) version

the 707, uploaded by Baronic, which is the South East Asia version.

The TLR version (based on UK 405) is now updated with newer components extracted from the 456 (ME) version...

Hope that makes it a bit more clear, reading is knowledge ;)!