I live in Korea and have a nice little Samsung.
It's a Samsung SCH-M450 or also called AnycallFX. I have stripped out all the Korean MUI stuff and am currently trying to get an English version of "MITS", a proprietary application loader that also runs on Blackjacks.
The best English info I can find on it is the following...
http://www.mobileisgood.com/phone_spec.php?phone_id=492&manufacturer_id=45
I am wondering how to ID this and possibly play around with the ROM.
First and foremost I would like to make a dump so I can keep it working in case of errors. I have some update programs from Samsung that ship with the phone for writing to it when they release updates but I don't know if there are plans for any in the future.
Could someone ID what device it falls under or help me figure out how to get info from the phone? Does someone know of a utility that will allow me to get version numbers, hardware IDs, etc?
"ID what device it falls under"
if you mean who makes it then samsung make their own devices they dont oem from htc or others
Thanks very much. I have been picking away at this phone piece by piece with registry edits, testing apps, etc trying to get it the way I want it. Thought maybe some of the content in here might speed the process up.
Related
not sure if any body thought of this what if chefs let users to sign their names addresses and finger print scan in the rom
1st will be thief deterent
2nd good hearted will return it if found
3rda phone will be a personal thing,chefs can leave their name somewhere for the smell and taste fo thier cooking
I'd think Chefs should also put a file in the \windows directory called release_notes with their ROM name and a forum link to their ROM thread.
Can't say how many times I've forgotten who's I've got flashed at any given time.
First, most chef's already put their name in the rom in one or more places, second , if you are using one of Alex's rom's used the kitchen & you can put whatever you want in it. Third, if somebody decent finds the device, your name & etc. is already in device owner info or can be looked up by your carrier with the serial or esn. Finally, if anyone else finds your device , it will take them all of 10 minutes to use Google & figure out how to flash a new rom. You could change the device ID to something nonexistent to make it harder to flash, but that's something better worked out by you & no Chef is gonna want to do that for every single person, not to metion that if he did, the thief would google & figure it out.
There is always ways around things, just ask AT&T, HTC & everybody at XDA
GSLEON3 said:
First, most chef's already put their name in the rom in one or more places, second , if you are using one of Alex's rom's used the kitchen & you can put whatever you want in it. Third, if somebody decent finds the device, your name & etc. is already in device owner info or can be looked up by your carrier with the serial or esn. Finally, if anyone else finds your device , it will take them all of 10 minutes to use Google & figure out how to flash a new rom. You could change the device ID to something nonexistent to make it harder to flash, but that's something better worked out by you & no Chef is gonna want to do that for every single person, not to metion that if he did, the thief would google & figure it out.
There is always ways around things, just ask AT&T, HTC & everybody at XDA
Click to expand...
Click to collapse
1st the whole idea is not about the phone getting lost rather than personlizing it ,to google or change that is why i said chefs should make it possible to ingrave it in the roms thiefs if they know all that they are nottheifs they won't find time to steal they will be cooking for us
actually, for anti-theft, I was thinking of a kit...
1) modified SPL; requires non-standard password and a signed NBH using your own custom certificate
2) OS is locked down with a trusted certificate of your own in the store so SSPL won't run at all... unless you sign it with your certificate
3) program that checks the SIMcard IMSI; if it changes then it sends an SMS to another number.
now... there are a few practical issues with 2) because it makes installing new apps a pain in the arse since they all need to be signed, so maybe a way of buggering up SSPL would be better.
ras said:
1st the whole idea is not about the phone getting lost rather than personlizing it ,to google or change that is why i said chefs should make it possible to ingrave it in the roms thiefs if they know all that they are nottheifs they won't find time to steal they will be cooking for us
Click to expand...
Click to collapse
A Chef that makes ROMs used by thousands is not gonna want to customize or personalize each one for every user. That said, with a donation, there are many that might consider it for you. Of course, you can always use a base ROM & the Kitchen to do it yourself. I do this.
Also, you can use provisioning xml's to customize or personalize them on a basic level using UC. Read Sleuth's thread on UC (User Customization).
@ Olipro, I really like the idea's 1 & 3. I have played a bit with CID locking to an imagined CID & with false Model ID's but of course while you then can't flash a ROM that's not customized to match, you could bypass it with SSPL, making it pointless against anyone half competent.
Your solution 1 & 3 would almost have to go hand in hand, having the password & a way to keep SSPL from jumping the password measures. Something like this, in conjunction with WIMP & UC in ROM, would be a great tool for security. Very Interesting indeed.
This is my 3rd post ever here, so please be gentle.
Crogon said:
I can't seem to find it now, but didn't there used to be a list of pre-cooked ROMs here somewhere?
I think what I'm aiming at is a fully patched / hacked 6.1 HTC ROM with everything fixed and no bugs. Preferably minus any bloatware. If it has recommended utilities pre-installed great, if not, no big loss. Did they ever finish hacking a video driver together? I lost track of that thread, and can't seem to find any current info.
Click to expand...
Click to collapse
Update: I found a tidbit somewhere that says the newest video driver updates should be cooked into the newest ROMs.. but how do I figure out which ones have all the bug patches and hacks installed, and etc. like I mentioned above? I know there USED to be a list of pre-cooked ROMs, but I can't find it now.
Hmm.. Am I maybe thinking of a list of pre-cooked ROMs for the Wing, or some other HTC? If I am, I'm DEFINITELY going to need some ROM recommendations.
Here are my stats, if it helps any:
rom version 3.57.502.2 WWE
rom date 7/17/08
radio version: 1.65.21.18
protocol version: 25.88.40.05H
tri-color screen
KAIS1*0
SPL-3.56.Hard
CPLD-8
.
.
Serial
image version 3.57.502.2
R 1.65.21.18
G 25.88.40.05H
D 3.57.00.00
Thanks again for any help!
if u really want a good cooked rom i suggest you try Garmins roms....they have the latest htc drivers built in...
thats all i can say
mazin13 said:
if u really want a good cooked rom i suggest you try Garmins roms....they have the latest htc drivers built in...
thats all i can say
Click to expand...
Click to collapse
he DOESN'T WANT a cooked rom he is looking for a pre-cooked rom.
@op did you check the kaiser wiki or htc's website?? 'cuz that is where you will find all the latest roms for your device that aren't cooked by a chef.
Also, look around for mbavrian's Kitchen Elements.
The "Base ROMs" on which our Chefs makes their gourmet meals are difficult to locate. Some chefs refuse to share like little playground children.
Others, Like NotATreoFan, have released their base for other people to use to make ROMs. Great Contributors.
Woops!
I guess I stated that incorrectly. Sorry!!
Actually I DO want a custom 'Cooked' ROM. My main purpose of reflashing the ROM is to get rid of all known bugs and bloatware. So I WANT all the custom registry hacks and patches to make everything run smoothly. I want the hacked video drivers (as they appear to currently be stable) and etc..
SO.. I'm looking for:
1) 6.1 OS with fast drivers and all known hacks and patches to have as few bugs as possible. UNLESS 6.1 has introduced some known bugs that can't be fixed (wouldn't surprise me with an MS product). IF there's a bug free FASTER version 5 OS, that will run on the Tilt, I'll be happy with that. One time I installed Win95 on a 1.6Ghz T-bird. Power on to fully loaded desktop was like 2 seconds flat.
2) bloatware removed so as to free up space, and I assume cleaning crap out of the registry wouldn't hurt with speed. Is there a system cache, and would it be beneficial to move it to the SD card? I've read that moving the IE cache to the SD card is asking for trouble, not sure that there's a concensus on that or if it's just opinion though.
OK.. that's going to get confusing. Scratch that and start over:
1) All known bugs hacked or patched.
2) All known speed enhancements (that don't compromise system integrity).
3) Rip out MS (or HTC ..or both?) crapware that COULD be replaced with faster / more functional counterparts.
4) Optional: pre-installed or at least packaged (cab?) applications to enhance functionality. My priority in applications is utility enhancement. Example: I can download 200 Flash / Java / MAME games to the SIM card some day if I get bored, don't need it in the OS. However, if there's a remedial photo editing utility that will allow me to edit my pics before I upload them somewhere, I want it.
I did manage to stumble across a wiki page last night: http://wiki.xda-developers.com/index.php?pagename=Kaiser_Cooked_ROMs
32 Developers and countless ROMs without any comparison isn't much help though. Can I assume all current ROMs are posted there?
Browsing through them, I recall that Alex's ROMs used to be the last word in ROMs, apparently dutty's were until he switched gears. HyperDragon seems to be terribly popular at the moment, but popular doesn't mean better.
I suppose I could try to gather all the available info into a giant spreadsheet, but the fact that about half the ROMs link out to a feature list is slightly discouraging. I think dutty's list of registry hacks ends in '.. and a bunch of other stuff I forgot', which is TERRIBLY discouraging (when trying to compare features).
Anyway, sorry if I'm rambling on here. Please don't take anything I'm saying as judgemental, I'm sort of thinking out loud trying to decide how best to proceed.
Say, has anybody considered building a CVS tree of sorts? I don't suppose you could have actual CODE stored in a repository without violating some sort of copyright or reverse engineering crap.. but a list of known code changes and etc. would seem to be a good idea. Since neither MS nor HTC has stepped up to the plate over the years, due to corporate greed, some sort of XDA-Dev code change tracking system seems like 'the last best hope' to get a decent OS. Ever.
That's why I'm jumping ship to try out the G1 after this. I don't believe MS will ever invest the effort to give us a 'business class' reliable bug free solution. ..let alone one that's innovative or even exceptional. They're style would lead me to expect them to wait till we have 800mhz handhelds, then 'patch' over top of everything they don't like to make it appear to behave better. ..and of course they would deem it necessary to add another programming layer to the OS to 'increase functionality' (read: bog down the OS).
Yup.. I'm definitely babbling now, so I'll just cut myself short.
I guess my bottom line questions are, Is there a more complete list of ROMs anywhere I should be using? ..or one which already compares all the features, so I don't have to?
Better yet, Is there a ROM build specifically to fit what I'm looking for? I seem to recall Alex's were built somewhat similar, but the newest one is quite old now. Hmm.. there is no Windows Mobile revision list is there? I have no way of knowing which older versions would be good, and when bug patches were introduced and etc.
Oh well, guess there's nothing to do but dive in head first and start putting together the best feature list I can with what resources I have.
Thanks for any help! ..and if you read this whole thing, thanks for putting up with my rambling, lol.
Crogon said:
I guess my bottom line questions are, Is there a more complete list of ROMs anywhere I should be using? ..or one which already compares all the features, so I don't have to?
Click to expand...
Click to collapse
I've never seen one and I don't believe one exists. You'll just have to do your own research.
Crogon said:
I guess I stated that incorrectly. Sorry!!
Actually I DO want a custom 'Cooked' ROM. My main purpose of reflashing the ROM is to get rid of all known bugs and bloatware. So I WANT all the custom registry hacks and patches to make everything run smoothly. I want the hacked video drivers (as they appear to currently be stable) and etc..
SO.. I'm looking for:
1) 6.1 OS with fast drivers and all known hacks and patches to have as few bugs as possible. UNLESS 6.1 has introduced some known bugs that can't be fixed (wouldn't surprise me with an MS product). IF there's a bug free FASTER version 5 OS, that will run on the Tilt, I'll be happy with that. One time I installed Win95 on a 1.6Ghz T-bird. Power on to fully loaded desktop was like 2 seconds flat.
2) bloatware removed so as to free up space, and I assume cleaning crap out of the registry wouldn't hurt with speed. Is there a system cache, and would it be beneficial to move it to the SD card? I've read that moving the IE cache to the SD card is asking for trouble, not sure that there's a concensus on that or if it's just opinion though.
OK.. that's going to get confusing. Scratch that and start over:
1) All known bugs hacked or patched.
2) All known speed enhancements (that don't compromise system integrity).
3) Rip out MS (or HTC ..or both?) crapware that COULD be replaced with faster / more functional counterparts.
4) Optional: pre-installed or at least packaged (cab?) applications to enhance functionality. My priority in applications is utility enhancement. Example: I can download 200 Flash / Java / MAME games to the SIM card some day if I get bored, don't need it in the OS. However, if there's a remedial photo editing utility that will allow me to edit my pics before I upload them somewhere, I want it.
I did manage to stumble across a wiki page last night: http://wiki.xda-developers.com/index.php?pagename=Kaiser_Cooked_ROMs
32 Developers and countless ROMs without any comparison isn't much help though. Can I assume all current ROMs are posted there?
Browsing through them, I recall that Alex's ROMs used to be the last word in ROMs, apparently dutty's were until he switched gears. HyperDragon seems to be terribly popular at the moment, but popular doesn't mean better.
I suppose I could try to gather all the available info into a giant spreadsheet, but the fact that about half the ROMs link out to a feature list is slightly discouraging. I think dutty's list of registry hacks ends in '.. and a bunch of other stuff I forgot', which is TERRIBLY discouraging (when trying to compare features).
Anyway, sorry if I'm rambling on here. Please don't take anything I'm saying as judgemental, I'm sort of thinking out loud trying to decide how best to proceed.
Say, has anybody considered building a CVS tree of sorts? I don't suppose you could have actual CODE stored in a repository without violating some sort of copyright or reverse engineering crap.. but a list of known code changes and etc. would seem to be a good idea. Since neither MS nor HTC has stepped up to the plate over the years, due to corporate greed, some sort of XDA-Dev code change tracking system seems like 'the last best hope' to get a decent OS. Ever.
That's why I'm jumping ship to try out the G1 after this. I don't believe MS will ever invest the effort to give us a 'business class' reliable bug free solution. ..let alone one that's innovative or even exceptional. They're style would lead me to expect them to wait till we have 800mhz handhelds, then 'patch' over top of everything they don't like to make it appear to behave better. ..and of course they would deem it necessary to add another programming layer to the OS to 'increase functionality' (read: bog down the OS).
Yup.. I'm definitely babbling now, so I'll just cut myself short.
I guess my bottom line questions are, Is there a more complete list of ROMs anywhere I should be using? ..or one which already compares all the features, so I don't have to?
Better yet, Is there a ROM build specifically to fit what I'm looking for? I seem to recall Alex's were built somewhat similar, but the newest one is quite old now. Hmm.. there is no Windows Mobile revision list is there? I have no way of knowing which older versions would be good, and when bug patches were introduced and etc.
Oh well, guess there's nothing to do but dive in head first and start putting together the best feature list I can with what resources I have.
Thanks for any help! ..and if you read this whole thing, thanks for putting up with my rambling, lol.
Click to expand...
Click to collapse
You have to spend some time and TRY each ROM and see which one is suited for you.
Again, READ and spend time.
Read WIKI especially.
There is no 100% perfect ROM even if it is official one.
Crogon said:
I guess my bottom line questions are, Is there a more complete list of ROMs anywhere I should be using?
Click to expand...
Click to collapse
http://wiki.xda-developers.com/index.php?pagename=Kaiser_Cooked_ROMs
If you want a newest list, you are always welcome to Update the wiki
I'm heading for the aspirin bottle just now. I spent like 3 hours reformatting the info on the wiki page into a spreadsheet.. when I discovered that some of the authors are still releasing, but it's not on the list!
AAHHH!!
So basically, A full up to date list is needed. Let alone version comparisons or features and bug fix lists.
Good grief.
No wonder most people opt to install ROMs randomly till they happen across one they like.
.. I think I'll make a new wiki page eventually. Something along the lines of a Kaiser ROM Feature Comparison page.
Do I get a XDA-Dev decoder ring if I actually finish it? lol
**used Android ID Changer.. worked exactly as i needed..**
Im running vegan rom
i play a couple games that are tied into the phone( or whatever) unique id..
When i installed these games, they already act like i already have an account and will not let me login with my user(one account per device). My question is how do i change my id? If i used the id from my phone would it just act as a clone? Im fairly android literate but i cant quite figure exactly what i need to do to (or exactly explain my delima) any help or direction would be appreciated ~evil
I'm not sure how to change this, I only learned of it the other day. The Swype Beta uses the ID to register you for the beta, so if you lack one like we do then it won't work and say its unsupported. The IDs are usually unique and only appear on "phones" (devices with cell capability). However, HTC and Samsung have applied one ID to all of one device so this breaks some programs. This leads me to believe we lack the ID entirely. If you find out where the programs are looking and how to add or change the ID make sure to post the information up for everyone.
Good luck!
Found it. find and install Android ID changer. It allowed me to do what I needed.
That's what I needed to change. Somehow someone else had to have the same as mine, hard to believe but that had to be the case. Not sure if its the same thing swype is looking at though
Hi Guys. I've been wondering around the internet looking at information for unlocking sim locked mobile phones and have come across the same typical information. I was wondering if anyone knows the in's and out's of how the operators lock their phones to thier networks so that at least it can answer a few questions which I have not come about.
Now I know that there are various programs out there for nokias that use your IMEI number to generate codes to unlock your mobile phone, but as I'm not a nokia user and have an old HTC Hero, these I guess would not work.
I have also tired and failed to look for software that does the same for smart phones. Code generators etc...
The only solution I can find is to use a website to input my IMEI number, pay a rediculous ammount of cash to get a code to unlock the phone.
Now, obviously these companies can get hold of the information to generate the code to unlock the phone.
1. Do they get this code from a program they use? And if so... would anyone like to share the name of this program with us???
2. Or is it a case that they gain the codes from the operators who lock them in the first place? And thus there is no way of getting the code to unlock the phone? (with out paying)
3. Are there any programs on the net that can decode these codes that are made for Android phones or universal, or apps made to automatically do this via the android market etc...
4. If not, is there anyone who would be able to make one? I've seen one for the samsung Galaxy s2. But would there be a universal one available or someone willing to write apps for the specific phones if that's the case?
5. I've rooted my phone, would using a different rom unlock the phone? Or is this totally seperate from the rom?
I just find it difficult to believe that with all the rooting, making software run on phones they weren't ment to, app building and stuff you clever people do on this site... why does it seem so difficult to do and make something that unlocks the phone to all networks? Is it actually that hard?
6. I'd like more information on why it is so hard if anyone knows?
Thanks everyone for any information and any help you can give me on this matter?
Regards.
anyone have any info or ideas?
Hi. I've been thinking that people who wants to buy a new phone should now first if there are free drivers, open recovery, etc.
Obviously, this info can be found in each smartphone forum, but maybe there should be a place where all this info collide.
I mean, a document (maybe in google docs) with:
Name of the phone --------------------- bootloader----------------Root---------------------Recovery--------------drivers (camera, processor).
This is a question that is constantly evolving and is dificult to be up to date.
For example, for the LG G3 D855, the bootloader is not open (but it is bumped, so we can achieve root, and use an open recover). However, AOSP roms aren't completely functional, because drivers for the camera aren't open.
Maybe this document is improvable, but my knowings aren't so vast. Let me know.
I think it could be useful to be following this document up.