Database Info

Best Kaiser 6.1 and 6.0 ROM and Radio out?

New to Kaiser. What's everybody's opinion on the best ROM out right now?
TIA!

anubus12 said:
New to Kaiser. What's everybody's opinion on the best ROM out right now?
TIA!
Click to expand...
Click to collapse
it all depends.. it's all personal preference.
Best way to decide is just to try it all out yourself.
Dutty's is most popular for the most part. Radio depends on your area etc.

I can't believe you have 150 posts and post a question like that. You should know already that everyone has their own opinion on what is the best rom. I will let you know that Dutty seems to be the most popular roms, but I don't use any of his roms cause I cook my own.
Just giving you a heads up on these forums. We have a lot of new people in here and a lot of these new people ask the same questions as you did.

i noticed that the radio performance varries by area also?

the best rom, which came bundled with the best radio, was removed from the Internet by HTC.
It had full dual core utilization, 3d drivers, multi-touch capability, flash 3, and ran Mac OSX.
I think it was called you_should_know_better v1.24.2234

otheruser said:
the best rom, which came bundled with the best radio, was removed from the Internet by HTC.
It had full dual core utilization, 3d drivers, multi-touch capability, flash 3, and ran Mac OSX.
I think it was called you_should_know_better v1.24.2234
Click to expand...
Click to collapse
boo ya, 150 post senior member burned by a 2 post junior member. good job there otheruser

dutty most popular
anubus12 said:
New to Kaiser. What's everybody's opinion on the best ROM out right now?
TIA!
Click to expand...
Click to collapse
dutty seem to develope the most popular. Its stable and there are several different versions. the WIKI's here are very good. I suggest you read and study and try some different ROM's and decide for yourself.

Sorry for the dumb question. Just got the Kaiser to try out for a few days only and am travelling. Just don't have the time to really evaluate the phone (not an excuse really). Have to return it if I don't like it. Hence the question to get the best feel. If I had more time with the phone, I would try them all.

anubus12 said:
Sorry for the dumb question. Just got the Kaiser to try out for a few days only and am travelling. Just don't have the time to really evaluate the phone (not an excuse really). Have to return it if I don't like it. Hence the question to get the best feel. If I had more time with the phone, I would try them all.
Click to expand...
Click to collapse
Travelling - RETURN IT?
You are travelling and willing to mess with your phone - you have GUTS man!
You know that if you mess with the phone you will most likely NOT be able to return it without putting it back to the shape it was in BEFORE you hosed with it?
All of that from someone who sounds like he has not done this before?
Whew - I am not worthy!
Bill

anubus12 said:
New to Kaiser. What's everybody's opinion on the best ROM out right now?
TIA!
Click to expand...
Click to collapse
I got Random Freeze and Hang using Dutys on my TILT. (i got the worse experience using it)
Once i change to ALEXs ROM ... everything allright... run smooth... and little tiny itsy bitsy small bugs.... fine with me

This may sound like a stupid question but I know radios work for reception but why did I lose audio on my device when i upgraded to dutty 6.1 release? I fixed the issue on the same day of course but I was just wondering why I lost audio.

redbandana said:
This may sound like a stupid question but I know radios work for reception but why did I lose audio on my device when i upgraded to dutty 6.1 release? I fixed the issue on the same day of course but I was just wondering why I lost audio.
Click to expand...
Click to collapse
because you have 6.0 radio, and will need to upgrade it to 6.1

tak.japan said:
because you have 6.0 radio, and will need to upgrade it to 6.1
Click to expand...
Click to collapse
Yeah i knew that but quite don't understand why it affects audio

newer tilts different camera hardware?

Ok guys ive run across this alot people downloading roms with radios that are designed to go with them and having trouble playing back video recorded on the device. I for one am having this problem i bought a new tilt 4-28-08
everything working fine, flashed duttys rom on 4-29-08, now this problem has arose. Now this thread is no way saying anything bad about Duttys rom i have had a tilt before and wore the thing out flashing his roms, he does awsome work this thread is to raise the question, has some thing been changed on the newer divices I know for a fact its not the rom and radio combination. I don't remember but on my old tilt i believe it had a 2 something meg on my new one its a 3 meg regardless somethings fishy.

I can't tell you if there is a difference in camera hardware or not, but I bought my Tilt about two weeks ago. First ROM I've flashed is Laurentius' V3 ROM, and I have not had any issues. It comes packaged with a radio. So far this ROM is superb, no issues to report from me, and much better of course than the stock ROM.

jstuart83 said:
Ok guys ive run across this alot people downloading roms with radios that are designed to go with them and having trouble playing back video recorded on the device. I for one am having this problem i bought a new tilt 4-28-08
everything working fine, flashed duttys rom on 4-29-08, now this problem has arose. Now this thread is no way saying anything bad about Duttys rom i have had a tilt before and wore the thing out flashing his roms, he does awsome work this thread is to raise the question, has some thing been changed on the newer divices I know for a fact its not the rom and radio combination. I don't remember but on my old tilt i believe it had a 2 something meg on my new one its a 3 meg regardless somethings fishy.
Click to expand...
Click to collapse
Try a different radio!

Its always been a 3MP camera...
BTW, which ROM/RADIO ver did you install? Was it the 1.65.14.06 ver??

jstuart83 said:
Ok guys ive run across this alot people downloading roms with radios that are designed to go with them and having trouble playing back video recorded on the device. I for one am having this problem i bought a new tilt 4-28-08
everything working fine, flashed duttys rom on 4-29-08, now this problem has arose. Now this thread is no way saying anything bad about Duttys rom i have had a tilt before and wore the thing out flashing his roms, he does awsome work this thread is to raise the question, has some thing been changed on the newer divices I know for a fact its not the rom and radio combination. I don't remember but on my old tilt i believe it had a 2 something meg on my new one its a 3 meg regardless somethings fishy.
Click to expand...
Click to collapse
What has video playback got to do with the number of megapixels in the camera? And suntzu is right, the camera in the Tytn II/Tilt has always been 3mp (well, technically speaking 2.8, but who's counting!)

ive flashed three different roms the htc and the att versions of duttys april 29 rom and alexes att rom and had the same issue on all three roms on duttys i shouldn't have to change the radio because that is whats packaged with the rom why would he say it compatiable if its not, come on this is dutty, i don't think its the radio rom combination. any way i started this thread to get people with the same problem to respond and see if there really is a problem. ive taken all logical steps to correct this, redownloaded roms, changed radios, reflashed still no solution

jstuart83 said:
ive flashed three different roms the htc and the att versions of duttys april 29 rom and alexes att rom and had the same issue on all three roms on duttys i shouldn't have to change the radio because that is whats packaged with the rom why would he say it compatiable if its not, come on this is dutty, i don't think its the radio rom combination. any way i started this thread to get people with the same problem to respond and see if there really is a problem. ive taken all logical steps to correct this, redownloaded roms, changed radios, reflashed still no solution
Click to expand...
Click to collapse
Did you try it on the stock rom to determine if you just have a bad tilt? If you've tried multiple roms/radio's, it does indeed start pointing at the hardware but doesn't necessarily mean anything has changed. From a business standpoint it would not make any sense to just change the camera and keep the same model number....they'd add a letter or change it up a bit to identify which firmware was needed.

you are probably right about the Rom
check out this post. This guy has found away to resolve the camera issue with his new TIlt
http://forum.xda-developers.com/showpost.php?p=2164973&postcount=812

famewolf said:
Did you try it on the stock rom to determine if you just have a bad tilt? If you've tried multiple roms/radio's, it does indeed start pointing at the hardware but doesn't necessarily mean anything has changed. From a business standpoint it would not make any sense to just change the camera and keep the same model number....they'd add a letter or change it up a bit to identify which firmware was needed.
Click to expand...
Click to collapse
yes the stock rom worked fine the camera works fine its the way it stores it to the phone i just tried 1.58.21.3, 1.58.25.14, radio and the camera would not work at all which is the problem with the rom and radio combos with duttys rom the camera works its just the video playback is crazy

ndcart said:
I can't tell you if there is a difference in camera hardware or not, but I bought my Tilt about two weeks ago. First ROM I've flashed is Laurentius' V3 ROM, and I have not had any issues. It comes packaged with a radio. So far this ROM is superb, no issues to report from me, and much better of course than the stock ROM.
Click to expand...
Click to collapse
I'll go ahead and try flashing that ROM to see whether it affects the camera on my new tilt too.
I think it's already been confirmed, but I'll confirm it as well:
The older Stock AT&T ROM I downloaded from somewhere off this forum (file name RUU_Kaiser_CINGULAR_WWE_1.57 - Originaly Shipped AT&T ROM.exe) did not work in terms of fixing the video camera issue. On top of that, it listed my processor as 7200.
I flashed with the newer:
RUU_Kaiser_CINGULAR_WWE_1.62.502.0_radio_sign_22.45.88.07_1.27.14.09R2_Ship.exe
And the video camera works flawlessly as the day I got my tilt (which was about a month ago).
Seems a slight change in the phones has occurred to cause this issue in most of the cooked ROMS being put out right now. Hopefully someone will be able to pinpoint exactly what it is....
For now all we have to go on is the models with the 7201 processor. Anyone that mentions they have a newer tilt and has now problems, please double check the processor to make sure it lists 7201 and not 7200. That way we know whether or not checking the processor is a reliable method of predicting whether there will be a problem or not...

arsunist said:
I'll go ahead and try flashing that ROM to see whether it affects the camera on my new tilt too.
I think it's already been confirmed, but I'll confirm it as well:
The older Stock AT&T ROM I downloaded from somewhere off this forum (file name RUU_Kaiser_CINGULAR_WWE_1.57 - Originaly Shipped AT&T ROM.exe) did not work in terms of fixing the video camera issue. On top of that, it listed my processor as 7200.
I flashed with the newer:
RUU_Kaiser_CINGULAR_WWE_1.62.502.0_radio_sign_22.45.88.07_1.27.14.09R2_Ship.exe
And the video camera works flawlessly as the day I got my tilt (which was about a month ago).
Seems a slight change in the phones has occurred to cause this issue in most of the cooked ROMS being put out right now. Hopefully someone will be able to pinpoint exactly what it is....
For now all we have to go on is the models with the 7201 processor. Anyone that mentions they have a newer tilt and has now problems, please double check the processor to make sure it lists 7201 and not 7200. That way we know whether or not checking the processor is a reliable method of predicting whether there will be a problem or not...
Click to expand...
Click to collapse
you are right my friend i have the 7201 and im having the problem the only rom i can get to work is the no thrills ro it works beautifuly

ndcart said:
I can't tell you if there is a difference in camera hardware or not, but I bought my Tilt about two weeks ago. First ROM I've flashed is Laurentius' V3 ROM, and I have not had any issues. It comes packaged with a radio. So far this ROM is superb, no issues to report from me, and much better of course than the stock ROM.
Click to expand...
Click to collapse
I tried Laurentius' V3 ROM just now. I still get the issue, although, when I go to the video album the thumbnail isn't the usual sold green image for the video. It's got big red dots patterned across it. Also, watching the video, I can discern some bright objects amongst the garbled colorful pixels. That's about it. This rom seemed considerably slower than Dutty's latest one. I guess I'll sacrifice the video camera until someone figures this issue out

arsunist said:
I tried Laurentius' V3 ROM just now. I still get the issue, although, when I go to the video album the thumbnail isn't the usual sold green image for the video. It's got big red dots patterned across it. Also, watching the video, I can discern some bright objects amongst the garbled colorful pixels. That's about it. This rom seemed considerably slower than Dutty's latest one. I guess I'll sacrifice the video camera until someone figures this issue out
Click to expand...
Click to collapse
same here im flashing back to duttys its perfect except that one issue you said you have the 7201 processor right

[Think Tank] Eclair video codecs issue ...

So I've been looking at the video codecs issue that blocks YouTube HD and video recording on the Dream. Seems there are two underlying issues, libsgl from donut was merged into a new library, and that theres an API break in libhardware.
On the first issue, its fairly easy to build donut's libsgl.so on eclair with some minor changes to source to get it, build it, and it seems that it works properly (as far as I can tell, the OpenGL 3D interface it binds to has had a stable API). I don't have a strong test case to use it on.
The second problem is more interesting. It seems to me that the problem with the API break is that Qualcomm is using enum's in a way that is absolutely stupid, and added new numbers that broke the magic numbers copybit needs. This causes a set of copybit failures when blitting stuff to the screen. Rebuilding the proprietary libraries would fix the problem, but as we only have libraries built against 1.6, this obviously won't work, so I'm seeing if theres a better solution we can use to solve this problem. Any ideas welcome.

NCommander, you've done amazing work here before
unfortunately, based on my research and trying to merge patches from 1.6 into 2.0 source and vice versa, that this is nearly impossible.
I would expect that the only feasable way would be to make a whole new composition method for android, based loosely off the methods shown in the 1.6 source.
Unfortunately, i think that it will be best to wait for HTC to work with qualcomm, and actually release something. I've heard that the MyTouch will be getting the 2.0/2.1 update, and hope that this release will solve our problems.

Noting is impossible
jcarrz1 said:
NCommander, you've done amazing work here before
unfortunately, based on my research and trying to merge patches from 1.6 into 2.0 source and vice versa, that this is nearly impossible.
I would expect that the only feasable way would be to make a whole new composition method for android, based loosely off the methods shown in the 1.6 source.
Unfortunately, i think that it will be best to wait for HTC to work with qualcomm, and actually release something. I've heard that the MyTouch will be getting the 2.0/2.1 update, and hope that this release will solve our problems.
Click to expand...
Click to collapse
Camera didn't work but now it does. Youtube will work 100% very soon

Interesting.... could we possible encapsulate the existing libhardware and create a new interface to it to translate the new calls (enums) to existing? Just throwing the idea out there - probably too simple and I am missing something not knowing too much of the details. I guess I would think of a libWINE like approach, interface just translates the new expected calls to the old driver....

if all goes well, will this also help speed up things like live wallpapers? (sorry if this is a noob question)

smackdown85146 said:
if all goes well, will this also help speed up things like live wallpapers? (sorry if this is a noob question)
Click to expand...
Click to collapse
In theory, it would allow any opengl call to be handled on the GPU. Not only would the livewallpaper speed up, but you'd have more available CPU time for other operations.
The idea is sound, the tricky part is making them efficient enough to actually be a net benefit. It could decent stopgap until new drivers are released.

????-????
So your saying that the first eclair roms where 1.6 with 2.0 skins?

llxll0m3g4llxll said:
So your saying that the first eclair roms where 1.6 with 2.0 skins?
Click to expand...
Click to collapse
No, not entirely...when the Eclair Roms roms were first being made in the beginning Devs didnt have the drivers for the camera. But, thanks to NCommander we do now =)

Android G1 2.0 Update
T-Mobile Czech Republic officialy announced 2.0 update for G1 for end of January (1-2 weeks). Maybe is better wait for this release.

pinkolin said:
T-Mobile Czech Republic officialy announced 2.0 update for G1 for end of January (1-2 weeks). Maybe is better wait for this release.
Click to expand...
Click to collapse
Isn't january ending... tomorrow?

vincom2 said:
Isn't january ending... tomorrow?
Click to expand...
Click to collapse
yeah, my senses tell me that it is

Yes, but this is Europe, "End of January" is in T-mobile speak half of February :-D. I have Google Translate page with this info, but i'm Junior member without rights :-D.

Eh would probably be too lazy to go back to stock anyways, will just have to wait for those video drivers =)

pinkolin said:
Yes, but this is Europe, "End of January" is in T-mobile speak half of February :-D. I have Google Translate page with this info, but i'm Junior member without rights :-D.
Click to expand...
Click to collapse
This can be "helpfully" for your work on this thread. More info:
http://forum.xda-developers.com/showthread.php?t=625108
http://www.4shared.com/file/207649694/b347bfad/RUU_Sapphire_HTC_Europe_304401.html
Is a full origianl ROM 2.1 for HTC Sapphire, the problem is that it only works on 32A, and I think that this can be a problem.

shawe_ewahs said:
This can be "helpfully" for your work on this thread. More info:
http://forum.xda-developers.com/showthread.php?t=625108
http://www.4shared.com/file/207649694/b347bfad/RUU_Sapphire_HTC_Europe_304401.html
Is a full origianl ROM 2.1 for HTC Sapphire, the problem is that it only works on 32A, and I think that this can be a problem.
Click to expand...
Click to collapse
I don't see anyone in that thread indicating that it's a 2.x ROM, just that it's a potential way to root some newer 32A SPLs. Might help some Rogers people out. Am I missing something? Have you pulled the build.prop?

olearyp said:
I don't see anyone in that thread indicating that it's a 2.x ROM, just that it's a potential way to root some newer 32A SPLs. Might help some Rogers people out. Am I missing something? Have you pulled the build.prop?
Click to expand...
Click to collapse
Its probably the default rom that comes with the phone.

How close is the camera in the g1 to the camera in the Hero ? I keep seeing articles that HTC is releasing 2.1 upgrade for the hero. Will this help the g1 ?

menace said:
How close is the camera in the g1 to the camera in the Hero ? I keep seeing articles that HTC is releasing 2.1 upgrade for the hero. Will this help the g1 ?
Click to expand...
Click to collapse
yup with the 2.1 upgrade ur g1 can take 10mp pics

bakgwailo said:
Interesting.... could we possible encapsulate the existing libhardware and create a new interface to it to translate the new calls (enums) to existing? Just throwing the idea out there - probably too simple and I am missing something not knowing too much of the details. I guess I would think of a libWINE like approach, interface just translates the new expected calls to the old driver....
Click to expand...
Click to collapse
Sounds like ndiswrapper for linux

gregnotcraig said:
Sounds like ndiswrapper for linux
Click to expand...
Click to collapse
doesnt it though

New Sensation Forum Required?

Just an observation here. Maybe someone with more knowledge can answer.
But now that all T-Mobile USA users have S-off... should we open a new forum for T-Mobile USA phones? I ask this because it seems we will have custom ROMs based off foreign RUUs and OTAs all mixed up in the same thread. Which would bring a lot of "Can I flash this if I'm a USA T-Mo user?" type questions.
Now this may just be a misunderstanding and the custom ROMs may not affect the radio or whatever & thus not be an issue. Just the same I felt it better to ask the question and look stupid than keep it to myself and be right.
Anyone?

I don't think any of the forums split the development sections in the way you're suggesting. You should be able to flash any ROM regardless of what the base is. Just have to read up to make sure it plays nice as some introduce bugs.

I understand what you mean but i don't think its needed provided you read the rom post

at one point threre was two forums for the hd2 leo and tmobile us so it can happen

Indeed. The Leo and T-Mobile US HD2 once had their own forums, but they where eventually merged into one once it became clear that with the proper labeling of releases people where more likely to successfully flash something, than not(IE, that's why we enforce the ROM labeling system that we do here, which was kanged from the HD2 section).
As of right now I see no need to split these forums, as currently ROMs seem to be interchangeable between regions and devices.

ashasaur said:
Indeed. The Leo and T-Mobile US HD2 once had their own forums, but they where eventually merged into one once it became clear that with the proper labeling of releases people where more likely to successfully flash something, than not(IE, that's why we enforce the ROM labeling system that we do here, which was kanged from the HD2 section).
As of right now I see no need to split these forums, as currently ROMs seem to be interchangeable between regions and devices.
Click to expand...
Click to collapse
Okay. I guess that was part of my question. For example, I saw this ROM posted and it's based on official HTC RUU 1.35.401.1
But since I'm a T-Mobile USA user I wasn't sure if the ROM would alter the frequencies my device operates on...etc. I believe this was an issue back when I had the Samsung Vibrant. There was a European variant known as the i9000. We could not flash the i9000 ROMS without having them ported to our Vibrants properly.

sup luckyduck
i remember you in the GS4G forums with krylon n crew

mikeDCMDVA said:
sup luckyduck
i remember you in the GS4G forums with krylon n crew
Click to expand...
Click to collapse
hey man! did you switch over to the sensation too?

luckyduck69 said:
Okay. I guess that was part of my question. For example, I saw this ROM posted and it's based on official HTC RUU 1.35.401.1
But since I'm a T-Mobile USA user I wasn't sure if the ROM would alter the frequencies my device operates on...etc. I believe this was an issue back when I had the Samsung Vibrant. There was a European variant known as the i9000. We could not flash the i9000 ROMS without having them ported to our Vibrants properly.
Click to expand...
Click to collapse
"Frequencies" are hardware related. A ROM cannot change the frequency that a phone uses

the_scotsman said:
"Frequencies" are hardware related. A ROM cannot change the frequency that a phone uses
Click to expand...
Click to collapse
thank you so much for answering. so i can update both my rom and my radio and not worry about it? if so... that's awesome. i just like to run the most up to date software/firmware...etc.

Not sure about radio to be honest though...so don't quote me on that

the_scotsman said:
Not sure about radio to be honest though...so don't quote me on that
Click to expand...
Click to collapse
I suspect it will be like the different modems on the SGS series of phones ( I had a Captivate ), I tried Mike's rom on my T-mo USA Sensation and when I tested the data speeds I got about 1/2 the dl speed sitting in the same spot within however long it took to run my recovery ( ran speedtest 5 times and averaged out ).
I'm sure they will iron out the radio thing before long, other than the data speed issue the Rom ran perfect.

luckyduck69 said:
hey man! did you switch over to the sensation too?
Click to expand...
Click to collapse
Yep, kicked the Samsung to my GF
Finally got this S-OFF.....man, we thought we had it hard with no CWM on the Samsung...lol, these guys had a locked bootloader

[Q] Discriminating HW, Kernel, ROM, and Model

PURPOSE:
The goal of this project is aimed at helping junior developers and sr. dev. assistants to understand the:
Subtle differences in hardware, particularly the radio, processor, and gps, which exists between various devices which are all called "Atrix 2"
To understand which hardware versions of the Atrix 2, correspond to the various geographic regions of the world, and which carriers provide service to or sale these hardware versions.
To gain a solid understanding of the reasoning why various kernels, ROMs, radio drivers, gps drivers, system images, and frameworks can or cannot be mixed and matched to the various hardware versions of the Atrix 2.
WHY:
It can scarcely be overstated, how powerful one's first experience with flashing a ROM can be, on the uninitiated android user. It may push them far away, never to return, or it could be the hook that reels in one of the best developers ever to rise and serve our community.
Additionally, because these differences in hardware, represent CRUCIAL choices that a junior developer must be confident in their discrimination of, this well organized and researched forum resource might jumpstart the future growth of the development work being done on the Atrix 2 platform.
METHODOLOGY:
The XDA Forums must be searched carefully for the best possible keywords, related to hardware, etc., and then scaned prudently for deconstruction and understanding of reported trial/error and other experiences users have shared, which will shed light on hardware/ROM/radio/system.img compatibility.
The relevant specifications for all known model numbers of the Atrix 2 phone, must be filtered and posted here, for an easy, summative, side-by-side comparison of reported differences.
Senior Developers who have been working on the Atrix 2 and similar software, as well as hackers, ROM cooks, mod-ers, scripters, and even themers, must participate and correct any errors posted here, in order to synthesize an accurate, comprehensive, and up-to-date set of hypotheses which match hardware versions to software capable of running on them.
XDA Members who are Atrix 2 owners, or who otherwise might be in a position to know (such as through employment), need to share their understanding here, based on their part of the world or where they purchased their phone from, and thus add to the set of hypotheses, the possible exceptions to the rules based on international ROMs, and overseas versions of the hardware.
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
MANUFACTURER PROJECT PAGES & SPECS:
ATRIX NAMES & MODEL NUMBERS:
(links below, lead to official Motorola product web pages)
ATRIX™ ME860, MB861
ATRIX™ 4G MB860
ATRIX™ 2 ME865
ATRIX™ 2 MB865
... BUT these are just the United States versions, and this still does not address the undoubted differences in software loaded (radios, etc) dependent on the Telecom Carrier (AT&T, T-Mobile, Sprint, Verizon).
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
METHODOLOGY EXAMPLE:
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
EXAMPLE FORENSIC DECONSTRUCTION, KNOWLEDGE BUILDING:
Take for instance, the case of multiple converging lines of evidence, which together can be used to create an educated guess, which is then tested by further research of reported user experiences. Thusly, a friend of mine was recently kind enough to let me know he had uploaded a ROM file, he knew I was eagerly awaiting:
Hi Paul,
I just uploaded the %$#@*&"}! ROM ... Enjoy!
Click to expand...
Click to collapse
QUESTIONS IMMEDIATELY PRESENTING:
Is my MB860 the same exact hardware that this ROM was previously running on(?), regardless of which carrier sells it? For instance, an ME865 is not the same hardwware as an MB865, but all ME865's are exactly the same hardware (in the US), regardless of which carrier they are sold for/by, and likewise, all MB865's are the same. Is this correct?
Is there enough differences between the ME865, and the MB865, such that some things can NOT be flashed on one, but they can on the other (like, the radio, versus a kernel, or ROM)??
REFERENCE THREAD & SEEKING ANSWERS:
I've read in a post (#3, in this thread) by Jim Bridgman that (referring to the MEARET ICS ROM that member Xanadu is running on his A2, that...
"...it will not work if you have an ME865 or a US version of the phone."
Click to expand...
Click to collapse
...which I interpret to mean ANY version of the Atrix 2 phone, which was manufactured for sale and use specifically in the United States, will not run the leaked ICS ROM (Mearet) currently in use by Xanadu.
But, just when I think I've got a grip on the meaning, Xanadu follows up, 2 posts later, that
"It works fine on ME865 and MB865 except at&t units."
Click to expand...
Click to collapse
... which is of course, one of the reasons I'm led to think that there could(??) somehow be two different version of HARDWARE which are both given the name MB865 -- one version is the US version, on AT&T, and the other is in Weinberg (presumably, in Germany, the location of member 'Xanadu').
Exactly one post later, I see further insights from member 'marcher233' (Beijing, China), who writes:
"We have two kind of LEAK roms at China: CN and HKTW versions. They both work on ME865 China Mainland and Hong Kong/Taiwan devices."
Click to expand...
Click to collapse
CONCLUDING HYPOTHESIS:
I strongly suspected, that AT&T was providing service in China and HK/TW (greed is the same, whether in communist nations or otherwise), so this bolstered my suspicions that just because two phone both read ME865, does NOT mean they are the same hardware. Afterall, there is actually another digit on the end, at least, on my phone.... it shows Model Number: MB8656
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
NEW HW QUESTION:
Thusly, (and to some degree, spawned resultantly from the continue research stimulation) we arrive at yet more, NEW questions.
What is the significance of this last digit in the model number, which is so rarely found in the literature from the manufacturer?
Other than risking softbrick, what is the best method to determine if a kernel or ROM for one phone, is flashable on another?
Thanks so much, for any insights you can give me.
Best Regards,
Paul

AT&T has a MB865. Theres an, I guess you could call it 'international' version with the same model number, frequently seen in middle eastern and asian markets (MEARET and SEARET software versions) and then there's the ME865, which is not (I don't think) a US release. All 3 have different hardware. They can flash images back and forth, but cannot use software updates meant for one of the others.
If course, its really late, and I just read these forums, I'm not a dev or anything...I could be wrong.
Sent from my MB865 using XDA

The atrix 2 is only MB865 and ME865 mb860 is the atrix 4G otherwise known as the original atrix.
the me865 and MB865 are actually different hardware, but close enough to be called the same phone. the different versions of the mb865 are different firmware versions, but may or may not be actual different hardware.
roms can generally be flashed to any of the A2 devices.
each has it's own fxz. you can only flash the ATT us version with that fxz, but the international ones like SEARET and MEARET can be flashed on each other.

lkrasner said:
The atrix 2 is only MB865 and ME865 mb860 is the atrix 4G otherwise known as the original atrix.
the me865 and MB865 are actually different hardware, but close enough to be called the same phone. the different versions of the mb865 are different firmware versions, but may or may not be actual different hardware.
roms can generally be flashed to any of the A2 devices.
each has it's own fxz. you can only flash the ATT us version with that fxz, but the international ones like SEARET and MEARET can be flashed on each other.
Click to expand...
Click to collapse
So up guys with att us version cannot flash searet or mearet Roms?
Sent from my MB865 using Tapatalk 2

I posted this a few weeks ago in response to questions about running leaks on different version of the A2. I think this should clear this all up, I have done way too much research on our phone, for the purpose of compiling kernels, and getting AOSP to work, so this is what has come from this research.
The original post can be found here:
http://forum.xda-developers.com/showpost.php?p=26993870&postcount=268
The Atrix2 has 5 iterations if you look at slight hardware differences alone... The ME865 is a completely different phone (2 versions of that one) for all intents and purposes.
Then there are 3 different Hardware revisions in the MB865, you have the asian version, then the Euro version, then the US version, each one carries a different GPS chip, and the Asia version has a different wifi chipset from the Euro and US versions.... now just because the actual chips are different does not mean that they operate differently, just that the software kernel drivers ARE different, so are the apps within the sofware for those parts....
Hence all the different software releases that this phone has, which includes the kernel and those chip drivers.. that is the whole reason this sucks so much for us devs.... especially if we are working on something like cyanogen mod, since there is NO source for the MB865 phones, only the ME865 phones have had the source released.
Click to expand...
Click to collapse
Now, so, you might be able to flash any of the leaks or ROMs for any versions of these phones, but unless you flash the radio and wifi parts separately, your phone may have some issues with GPS, phone calls, roaming, WIFI, etc. You may experience some, all or none of these issues, with an international phone, but if you try and run an international version on the AT&T phone you will have a glorified tablet with no communications at all. We have seen this when the 2.3.6 leaks were out, and people on AT&T were flashing the international and ME865 fxz and leaks, and they had a TON of issues.
To everyone besides the OP, why is it that this subject can never die around here? Just do a search and see for yourselves, the issues that others faced before doing something dumb like flashing other versions of the software that are not for your phone.
To PRichardson, what I have quoted above should suffice for a good explanation for your documentation on the OP, I would hope.
The one thing is though, that ANYTHING to do with the OG Atrix 4G models (ME860, MB860, ME861) needs to go away, that phone is not even in the same universe as ours, since it uses a tegra chipset, and there is NO way roms for it will run on our phones, nor our ROMs on thier phones.

Itch Scratched
Greeting Jim (& others),
jimbridgman said:
...To everyone besides the OP, why is it that this subject can never die around here? Just do a search and see for yourselves, the issues that others faced before doing something dumb like flashing other versions of the software that are not for your phone.
To PRichardson, what I have quoted above should suffice for a good explanation for your documentation on the OP, I would hope.
The one thing is though, that ANYTHING to do with the OG Atrix 4G models (ME860, MB860, ME861) needs to go away, that phone is not even in the same universe as ours, since it uses a tegra chipset, and there is NO way roms for it will run on our phones, nor our ROMs on thier phones.
Click to expand...
Click to collapse
Thank you so much Jim. I agree 100%, and it does indeed suffice. And I shall also endeavor to learn to search and read these forums more judiciously in the future. I am beginning to see that the 'confident' tone of some posts, is not always justified so much as the reputation of the speaker.
I will add an update to my OP at the top of it, with a clear and somewhat brief answer (relative to my usual style) to the basic questions I posed, summarizing all here as I understand it, and clearly annotate the bottom half (with intact OP left untouched) as serving 'historical purposes only' so that any forensic deconstructivists, shall have their satisfaction, if their itch must be scratched.
Best Regards,
Paul

PRichardson said:
Greeting Jim (& others),
Thank you so much Jim. I agree 100%, and it does indeed suffice. And I shall also endeavor to learn to search and read these forums more judiciously in the future. I am beginning to see that the 'confident' tone of some posts, is not always justified so much as the reputation of the speaker.
I will add an update to my OP at the top of it, with a clear and somewhat brief answer (relative to my usual style) to the basic questions I posed, summarizing all here as I understand it, and clearly annotate the bottom half (with intact OP left untouched) as serving 'historical purposes only' so that any forensic deconstructivists, shall have their satisfaction, if their itch must be scratched.
Best Regards,
Paul
Click to expand...
Click to collapse
once again, we all give somewhat clear answers and Jim swoops in here and clears everything up perfectly, making the rest of us look like fools. (no offense, you're awesome).