My question is fairly simple.
I have installed various ROMs and kernels, and have used CWM of various different model numbers (which some work and some dont) and now I am quite curious what the ACTUAL hardware model # of my phone is.
I am not talking about checking what the model number is INSIDE THE PHONE SOFTWARE OR UNDER THE BATTERY! (my phone is GT-i9100T btw)...because this is only dependent on what ROM/Kernel you install and can change.
Originally when I first got my phone it said the model number was GT-i9100TxxKJ1 - the small "xx" is actually something else that I cant even remember anymore.
When I tried to install a KJ1 CWM over it to start rooting it - IT DIDNT WORK. So, I got a KJ3, KI1, and KI3 all of which worked fine. However, they also changed my phone's "baseband" version when looking up info about phone in settings to the same letters, respectively. Also, they removed the "T" from the main model number ie: GT-i9100 shows up at boot, and no longer GT-i9100T.
Now I am trying to install a very good ROM/Kernel that will improve battery life and remove all the bloatware apps (I've tried to do that with hyperdroid, CM7, Villian, and many others, but apparently bloat is still there, and/or battery is still fairly miserable). The problem is that I dont really know what my real phone model is. I also want to install the correct version of CWM and I'd really like my phone to use the correct drivers.
So my final questions are:
How do I determine what actual model #'s my phone has?? (ie: UXKJ1, UGKI3, ZVKG2, etc.)
And----
Is it even important/necessary to know the exact phone's model #'s or can I use more recent updated pda/modem/csc firmware that perhaps even give better performance?
Thank you very much for help, in advance.
BTW, I did use search, and all I could find was this:
http://forum.xda-developers.com/showthread.php?t=1397121
I also followed up and googled the suggested "morfics kernel thread" to find info regarding this issue but found nothing.
Thought I'd mention this, as this is also my first post here. ;-)
To find your model take your battery out and its under there. I cant comment on the T variant as im not sure if its different like the G version is different.
Ricey
I9100T is the same as the I9100 for all intensive purposes. Slight difference in power of radio or something from memory. No difference so far as roms/kernels that can be used tho (Has same processor as I9100, etc).
ricey1986 said:
To find your model take your battery out and its under there. I cant comment on the T variant as im not sure if its different like the G version is different.
Ricey
Click to expand...
Click to collapse
So, I got a KJ3, KI1, and KI3 all of which worked fine. However, they also changed my phone's "baseband" version
Are you sure you are flashing a root kernel as they cannot flash a modem .
jje
You most likely have the i9100T. Basically flash anything you like, but if reception is bad flash a i9100T modem over the top of it.
As ricey1986 pointed out, the only way to be sure is to check the sticker under the battery.
Sent from my GT-I9100
MistahBungle said:
I9100T is the same as the I9100 for all intensive purposes. Slight difference in power of radio or something from memory. No difference so far as roms/kernels that can be used tho (Has same processor as I9100, etc).
Click to expand...
Click to collapse
Its the differant SAR Ratings, as the T version was mostly sold in Asia/Aus.
GT-I9100
THIS MODEL MEETS INTERNATIONAL GUIDELINES FOR EXPOSURE TO RADIO WAVES
Your mobile phone is a radio transmitter and receiver. It is designed not to exceed the limits for exposure to radio waves recommended by international guidelines. These guidelines were developed by the independent scientific organization ICNIRP and include safety margins designed to assure the protection of all persons, regardless of age and health.
The guidelines use a unit of measurement known as the Specific Absorption Rate, or SAR. The SAR limit for mobile devices is 2.0 W/kg and the highest SAR value for this device when tested at the ear was 0.338 W/kg1. As mobile phone offer a range of functions, they can be used in other positions, such as on the body as described in this user guide2. In this case, the highest tested SAR value is 0.538 W/kg
GT-I9100T
THIS MODEL MEETS INTERNATIONAL GUIDELINES FOR EXPOSURE TO RADIO WAVES
Your mobile phone is a radio transmitter and receiver. It is designed not to exceed the limits for exposure to radio waves recommended by international guidelines. These guidelines were developed by the independent scientific organization ICNIRP and include safety margins designed to assure the protection of all persons, regardless of age and health.
The guidelines use a unit of measurement known as the Specific Absorption Rate, or SAR. The SAR limit for mobile devices is 2.0 W/kg and the highest SAR value for this device when tested at the ear was 0.295 W/kg1. As mobile phone offer a range of functions, they can be used in other positions, such as on the body as described in this user guide2. In this case, the highest tested SAR value is 0.472 W/kg.
Wow, seriously???
NOT ONE OF YOU ANSWERED MY QUESTION!!!
I Made it EXPLICITY clear what my question was and that it was NOT a question simply to ask if it was i9100T, or i9100, or i9100G...I dont care about that.
I want to know what my ENTIRE MODEL number is....How is it possible every single one of you missed that when I repeatedly made it clear that is what I was asking and NOT asking about the above single T/-/G variant. Information on that is widespread and easy to find and I already know it.
For a forum so dedicated to having people avoid asking questions already asked - MANY OF YOU APPARENTLY ANSWER QUESTIONS WITHOUT READING THEM!!
Once again: I want to know if my base phone is LUXKJ1, or XEOKI3 or etc etc etc....this is what my question asks!
PLEASE READ THE QUESTION BEFORE ANSWERING AND CLUTTERING UP A PERFECTLY GOOD QUESTION THREAD!
I can almost guarantee you won't get the answer you're looking for after posting like a 3yr old. Notice how your thread has been ignored for the last 90 mins ?
There's a hint in that for you champ.
Edit to add - I've got a couple of nephews & nieces under 5 who behave better than you. But I know how kids can get sometimes, so I'm going to cut you a bit of slack. You might find what you're looking for in this thread or this thread. You're going to have to work the rest out on your own tho.
efraip said:
Wow, seriously???
NOT ONE OF YOU ANSWERED MY QUESTION!!!
I Made it EXPLICITY clear what my question was and that it was NOT a question simply to ask if it was i9100T, or i9100, or i9100G...I dont care about that.
I want to know what my ENTIRE MODEL number is....How is it possible every single one of you missed that when I repeatedly made it clear that is what I was asking and NOT asking about the above single T/-/G variant. Information on that is widespread and easy to find and I already know it.
For a forum so dedicated to having people avoid asking questions already asked - MANY OF YOU APPARENTLY ANSWER QUESTIONS WITHOUT READING THEM!!
Once again: I want to know if my base phone is LUXKJ1, or XEOKI3 or etc etc etc....this is what my question asks!
PLEASE READ THE QUESTION BEFORE ANSWERING AND CLUTTERING UP A PERFECTLY GOOD QUESTION THREAD!
Click to expand...
Click to collapse
What a complete douche. If you would of had the good sense to write down your phone settings before Modding you wouldn't need to ask. Not only do you post like a 3 year old seems you have the intellect of one as well.
Sent from my GT-I9100 using xda premium
efraip said:
Wow, seriously???
NOT ONE OF YOU ANSWERED MY QUESTION!!!
I Made it EXPLICITY clear what my question was and that it was NOT a question simply to ask if it was i9100T, or i9100, or i9100G...I dont care about that.
I want to know what my ENTIRE MODEL number is....How is it possible every single one of you missed that when I repeatedly made it clear that is what I was asking and NOT asking about the above single T/-/G variant. Information on that is widespread and easy to find and I already know it.
For a forum so dedicated to having people avoid asking questions already asked - MANY OF YOU APPARENTLY ANSWER QUESTIONS WITHOUT READING THEM!!
Once again: I want to know if my base phone is LUXKJ1, or XEOKI3 or etc etc etc....this is what my question asks!
PLEASE READ THE QUESTION BEFORE ANSWERING AND CLUTTERING UP A PERFECTLY GOOD QUESTION THREAD!
Click to expand...
Click to collapse
Man, the reason you got so many varying answers is because no-one actually knows what the hell you are asking.
To be honest, I don't think you even know what you are asking. Or at least you haven't got a proper grasp of the terminology for the phone which has led to this confusion.
In the first paragraph of the OP you ask "and now I am curious what the ACTUAL hardware model # of my phone is".
Very simple, its a bloody i9100T.
Later you claim to have flashed various kernals which changed your baseband. Baseband only changes when you flash a modem, which for you is now most likely an i9100 MODEM which is not optimized for your phone.
Later you state again you don't know what your real phone model is (its an i9100T by the way) so that you can install the correct version of cwm and so your phone has the correct drivers.
Well, that's pretty confusing but the correct cwm version (or cf root version) for you is the version for whatever firmware you currently have.
Again in the final paragraph you ask what your actual model number is but provide a list of firmware versions.
Finally, based on your final sentence of the OP, yes it is very important what your exact phone model is but I suspect you meant firmware version because you talk about pda/modem/csc. You can flash pretty much any firmware version you like. And yes, generally the newer the better.
Now again in your reply you ask " Once again: I want to know if my base phone is LUXKJ1, or XEOKI3 or etc etc etc....this is what my question asks!"
Well, how would we know what firmware version you phone came with, you obviously flashed over it already.
Maybe explaining from what carrier / country etc it came from then maybe people can help you.
Anyway, that all means ****. You have an i9100T and you can flash whatever you like but may need to flash a T modem if reception is bad.
Over and out, and grow up. You wont be getting much help if your react that way to people at least attempting to answer your " PERFECTLY GOOD QUESTION THREAD'.
Sent from my GT-I9100
Pratt you are asking what is your model numbey.
Theiy is only one model number the one under the battery.
Question might be what wa my original firmware.
jje
Sent from my GT-I9100 using xda premium
tl;dr and double post....
sxi200 said:
Man, the reason you got so many varying answers is because no-one actually knows what the hell you are asking.
To be honest, I don't think you even know what you are asking. Or at least you haven't got a proper grasp of the terminology for the phone which has led to this confusion.
In the first paragraph of the OP you ask "and now I am curious what the ACTUAL hardware model # of my phone is".
Very simple, its a bloody i9100T.
Later you claim to have flashed various kernals which changed your baseband. Baseband only changes when you flash a modem, which for you is now most likely an i9100 MODEM which is not optimized for your phone.
Later you state again you don't know what your real phone model is (its an i9100T by the way) so that you can install the correct version of cwm and so your phone has the correct drivers.
Well, that's pretty confusing but the correct cwm version (or cf root version) for you is the version for whatever firmware you currently have.
Again in the final paragraph you ask what your actual model number is but provide a list of firmware versions.
Finally, based on your final sentence of the OP, yes it is very important what your exact phone model is but I suspect you meant firmware version because you talk about pda/modem/csc. You can flash pretty much any firmware version you like. And yes, generally the newer the better.
Now again in your reply you ask " Once again: I want to know if my base phone is LUXKJ1, or XEOKI3 or etc etc etc....this is what my question asks!"
Well, how would we know what firmware version you phone came with, you obviously flashed over it already.
Maybe explaining from what carrier / country etc it came from then maybe people can help you.
Anyway, that all means ****. You have an i9100T and you can flash whatever you like but may need to flash a T modem if reception is bad.
Over and out, and grow up. You wont be getting much help if your react that way to people at least attempting to answer your " PERFECTLY GOOD QUESTION THREAD'.
Sent from my GT-I9100
Click to expand...
Click to collapse
Thank you, very much.
And yes, I am not an expert at this, hence my presence here in Q&A. I've spent 2 days searching for answers before posting here.
Yes that also does mean my question might be a bit off. I'm an engineer though so have alot more technical ability than most, so its going to be very apparent that others might have this same issue/question.
1) I'm not concerned with what firmware my phone shipped with originally - but rather what actual hardware it is.
2) I know the difference between i9100, i9100G and i9100T.
3) I wasnt aware of the differences between all the various hardware #'s such as XWKJ1, ZVKG3, etc. -- apparently I was wrong anyway and those are simply firmware ID's and not hardware ID's. That clears alot of things up.
4) If I understand correctly from your answer - it doesnt matter what firmware I use, as long as it works. I can use any ROM or Kernel I want as long as they match, and can flash any PDA/Modem/CSC I want as long as they also match/work in my phone. As you said, the newer the better.
This is the answer I was looking for, thanks for clearing it up.
I am putting on ICS and CM9 now, and will also try out the other ICS builds. I was simply worried that I might use a modem firmware or something that is made for a different hardware piece which then could cause some damage in my phone.
Last phones I did development for were WinCE and java based, over 8 years ago, as I'm mainly a software engineer. This is the first smart-phone I have.
Thanks again for your answer and I had no intention to make it confusing, there were simply some terminology and such issues I wasnt clear on.
That also makes it more clear as to why people were confused on my question. So I appologize for that.
It seemed to me that nobody read my question as I explicitly said I am not asking for whether it is an i9100/T/G because thats fairly obvious and imprinted on the phone (physically).
efraip said:
Thank you, very much.
And yes, I am not an expert at this, hence my presence here in Q&A. I've spent 2 days searching for answers before posting here.
Yes that also does mean my question might be a bit off. I'm an engineer though so have alot more technical ability than most, so its going to be very apparent that others might have this same issue/question.
1) I'm not concerned with what firmware my phone shipped with originally - but rather what actual hardware it is.
2) I know the difference between i9100, i9100G and i9100T.
3) I wasnt aware of the differences between all the various hardware #'s such as XWKJ1, ZVKG3, etc. -- apparently I was wrong anyway and those are simply firmware ID's and not hardware ID's. That clears alot of things up.
4) If I understand correctly from your answer - it doesnt matter what firmware I use, as long as it works. I can use any ROM or Kernel I want as long as they match, and can flash any PDA/Modem/CSC I want as long as they also match/work in my phone. As you said, the newer the better.
This is the answer I was looking for, thanks for clearing it up.
I am putting on ICS and CM9 now, and will also try out the other ICS builds. I was simply worried that I might use a modem firmware or something that is made for a different hardware piece which then could cause some damage in my phone.
Last phones I did development for were WinCE and java based, over 8 years ago, as I'm mainly a software engineer. This is the first smart-phone I have.
Thanks again for your answer and I had no intention to make it confusing, there were simply some terminology and such issues I wasnt clear on.
That also makes it more clear as to why people were confused on my question. So I appologize for that.
It seemed to me that nobody read my question as I explicitly said I am not asking for whether it is an i9100/T/G because thats fairly obvious and imprinted on the phone (physically).
Click to expand...
Click to collapse
So the moral of the story is Google Google Google:
http://support.netgear.com/app/answ...er,-firmware,-hardware,-software,-and-utility
efraip said:
Thank you, very much.
And yes, I am not an expert at this, hence my presence here in Q&A. I've spent 2 days searching for answers before posting here.
Yes that also does mean my question might be a bit off. I'm an engineer though so have alot more technical ability than most, so its going to be very apparent that others might have this same issue/question.
1) I'm not concerned with what firmware my phone shipped with originally - but rather what actual hardware it is.
2) I know the difference between i9100, i9100G and i9100T.
3) I wasnt aware of the differences between all the various hardware #'s such as XWKJ1, ZVKG3, etc. -- apparently I was wrong anyway and those are simply firmware ID's and not hardware ID's. That clears alot of things up.
4) If I understand correctly from your answer - it doesnt matter what firmware I use, as long as it works. I can use any ROM or Kernel I want as long as they match, and can flash any PDA/Modem/CSC I want as long as they also match/work in my phone. As you said, the newer the better.
This is the answer I was looking for, thanks for clearing it up.
I am putting on ICS and CM9 now, and will also try out the other ICS builds. I was simply worried that I might use a modem firmware or something that is made for a different hardware piece which then could cause some damage in my phone.
Last phones I did development for were WinCE and java based, over 8 years ago, as I'm mainly a software engineer. This is the first smart-phone I have.
Thanks again for your answer and I had no intention to make it confusing, there were simply some terminology and such issues I wasnt clear on.
That also makes it more clear as to why people were confused on my question. So I appologize for that.
It seemed to me that nobody read my question as I explicitly said I am not asking for whether it is an i9100/T/G because thats fairly obvious and imprinted on the phone (physically).
Click to expand...
Click to collapse
Hey man, glad you now understand why so many of us weren't able to answer you correctly, but really it came down to your tone in the reply. Anyway, we are a pretty forgiving community so let's forget about it and move on.
With the i9100T you can flash any i9100 rom from whatever region etc. Yes some things do need to match but I don't even bother with csc because for me it makes no difference. It really only helps if you want to receive your carrier upgrades from kies which I dont even use anymore. Csc also can include carrier bloatware but I prefer an unbranded phone. So if you want your carrier's crap, then csc is important.
And yes roms and kernals do need to match but in some cases you can use 1 kernal across multiple roms, like the siyah and speedmod kernals. Cf root on the other hand most often need to match the rom. With the Samsung ics leaked roms, I think kernals can also be mixed and matched so long as they are Samsung ics kernals. Anyway, all custom roms come with a functional kernal built in so no need to change it, unless you prefer another one.
For me, also with the T version, the only thing I have to worry about is the modem as the i9100 modems give poor reception for my carrier. So basically if I flash stock, custom, miui or cm roms, I need to reflash the T modem for better reception. I been able to use that modem on any firmware I've tried.
Hope this clears things up a little. I see you are now getting a hang on the terminology but yeah, at first it can be quite confusing.
Sent from my GT-I9100T
Related
Hi guys
So the Galaxy S2 is hopefully coming here soon to Canada and I just had some questions about it.
1) I'm pretty used to looking at the Atrix forums and the problems associated with the bootloader and Motorola's lack of interest in updating their phones.
Does Samsung also have a bad rep for updating their phones or are they pretty good about it?
2) Also, I don't see much action happening in the dev forum ATM.
Is that normal because the phone hasn't been released in the states or is there some restriction stopping people from developing for this phone?
b) Or are people not wanting to put custom ROM's on the phone because it's really good?
3) I read something about Canada and an "AWS version". What does that mean?
Those are the main questions I wanted to ask right now when I think of more I'll post them.
Thanks,
Elliott
1) Not so sure sure about Samsung, there have 3 firmware updates so far but news whether they will be updating to 2.4, fingers crossed though..
2) This is not so true, the development scene is doing quite well i'd say most notably from pulser_g2 and his custom VillanRom 1.1, there are 2 other custom roms ready at the moment as well, Light'ning and one by AngeloM, CyongenMod 7 is also in the works as well. my money is on pulser's VR 1.1 one though, I stand by it .
3) Coming from Australia probably not the best to answer but AWS is a spectrum used by USA/Canada telcos how it compares to the others I have nfi.
If your wondering about this phone, i'd say look no further.
Is that normal because the phone hasn't been released in the states or is there some restriction stopping people from developing for this phone?
Its not two months old yet and many devs do not have SGS2 they have to go out and buy out of their own pocket .
b) Or are people not wanting to put custom ROM's on the phone because it's really good
YES
jje
Thanks guys.
Any info regarding questions #1 and 3?
Just adding to #3: it was something about Canada maybe not getting an AWS version or something like that? (and what is AWS?)
Does anyone else have anything to add with regard to my 1st and 3rd questions?
Also, if I get a phone that has the yellowing problem on the screen I should be able to return it for one that doesn't, correct? (I'm with Bell in Canada) [I realize the phone is not out yet in Canada...but when it is]
Bump...anyone?
Starholdest said:
Does anyone else have anything to add with regard to my 1st and 3rd questions?
Also, if I get a phone that has the yellowing problem on the screen I should be able to return it for one that doesn't, correct? (I'm with Bell in Canada) [I realize the phone is not out yet in Canada...but when it is]
Click to expand...
Click to collapse
yes ive read people with that issue returning it
also people that get pink spots when taking pictures returned it
Thanks. Is that still an issue with the new batch of phones or it still is? I love this phone but I'd rather not buy one knowing that they all have problems...
Bump...10char
Bump...anyone?
Starholdest said:
Bump...anyone?
Click to expand...
Click to collapse
1 no Samsung are fair and SGS2 has had about five updates .
3 plenty of custom roms around you cannot have many users of custom roms when the phone is only a few weeks old .
jje
I know I'm new, so tear me a new one if need be...
That being said, I've been reading the forums for the better part of the last 3 hours, and I want to be certain of some things before I proceed
My carrier is Sprint
Model:
SPH-D710
Kernel:
3.0.15-SPH-D710.FF18-CL663858
[email protected] #3
Hardware version:
D710.10
1. Is it indeed possible to root the phone without losing apps, messages, call log, etc.?
1a. If yes, what would be the simplest method for a beginner like me?
2. Is there a simple way to restore the phone if I break it but good?
melvin2345 said:
I know I'm new, so tear me a new one if need be...
That being said, I've been reading the forums for the better part of the last 3 hours, and I want to be certain of some things before I proceed
My carrier is Sprint
Model:
SPH-D710
Kernel:
3.0.15-SPH-D710.FF18-CL663858
[email protected] #3
Hardware version:
D710.10
1. Is it indeed possible to root the phone without losing apps, messages, call log, etc.?
1a. If yes, what would be the simplest method for a beginner like me?
2. Is there a simple way to restore the phone if I break it but good?
Click to expand...
Click to collapse
Good thing you were cautious, because you are in the the wrong forum.
This forum is for the I9100, a GSM phone that doesn't work on Sprint's network.
You have an SPH-D710, also known as the Epic 4G Touch, and the forum for that device is located at http://forum.xda-developers.com/forumdisplay.php?f=1281.
Flashing anything in this forum (for the i9100) will cause you nothing but problems.
ctomgee said:
Good thing you were cautious, because you are in the the wrong forum.
This forum is for the I9100, a GSM phone that doesn't work on Sprint's network.
You have an SPH-D710, also known as the Epic 4G Touch, and the forum for that device is located at http://forum.xda-developers.com/forumdisplay.php?f=1281.
Flashing anything in this forum (for the i9100) will cause you nothing but problems.
Click to expand...
Click to collapse
Hah! SO it's true that there are no dumb questions, just dumb people, lol. Thank you for the clarification.
I have a stock new UK GT-S5830i, unmodded, standard Samsung v2.3.6. I'd have rooted and upgraded it anyway (Jelly blast? MindCr? Something else?) but I hit an unexpected Bluetooth problem while readying it for rooting/CWM.
Sometimes I find a bluetooth keyboard useful (**). I tried to pair it (***) to my new 5830i - it's detected but I get the message "Sorry, but HID device is not supported on this phone". I'm guessing it's an OS limitation rather than a hardware one, it's physically detected, and Android changelog says that ICS and Jelly Bean both improve Bluetooth HID device support. But I'm not sure. Advice appreciated before I spend more money!
If it's an OS limitation will upgrading to a 4.x ROM solve this (if so, is ICS ok or do I need JB?) and if so which 4.x in others' experience are the best bets for "everything just works" on the 5830i?
Also if I upgrade the OS, does the upgraded rom also include any applicable upgrades to radio, or is that a separate recommended install?
** hardware kbs have some uses - actual arrow keys, numbers without a modifier key, unobscured display, tactile, touch-typing.
*** My kb can be seen at ionaudio DOT com /images/products/ Type_N_Slide_open_angle_LG.jpg if useful.
Praise the Lord for giving you two hands, one brain and two eyes and teaching how to use them to search before posting.
Open your eyes and see what a beautiful world it is!
And also see that there is a thread saying post your questions here
[Q&A][OFF-TOPIC]Post your Questions
here(Questions, Chat,Tips, Shares etc)
No one should help you unless you post your questions here
Now, I read your full post and then I say that sorry dude
Take my words back
Yes, Its a problem with ROM
OS limitation
Upgrading to Jelly Bean 4.2 will solve the problem.
Just go to Samsung Service Centre and shove your phone into their face and say
Here nigga, upgrade it to Jelly Bean
Please share the experience after you do it.
Regards
A person who searches the fcuking whole internet before posting regarding questions
iamareebjamal said:
Praise the Lord for giving you two eyes and teaching how to use them
Open your eyes and see what a beautiful world it is!
And also see that there is a thread saying post your questions here
http://forum.xda-developers.com/showthread.php?t=2089279
No one should help you unless you post your questions here
Click to expand...
Click to collapse
I think the God has forgot to give him two eyes
iamareebjamal said:
Praise the Lord for giving you two hands, one brain and two eyes and teaching how to use them to search before posting. Open your eyes and see what a beautiful world it is!
And also see that there is a thread saying post your questions here
http://forum.xda-developers.com/showthread.php?t=2089279
No one should help you unless you post your questions here
Now, I read your full post and then I say that sorry dude
Take my words back
Yes, Its a problem with ROM
OS limitation
Upgrading to Jelly Bean 4.2 will solve the problem.
Just go to Samsung Service Centre and shove your phone into their face and say
Here nigga, upgrade it to Jelly Bean
Click to expand...
Click to collapse
Like you say, it isn't "off topic", eyes were fully used. The forum is used for other posts about ROMs, internal memory, firmware, hardware, modding etc so it's in good company :angel: (and Alucard1989pl - maybe use eyes like iamareebjamal? Read before failing @ lulz? Not what a senior member's posts should be like, sorry)
Anyway thank you for editing your post. Yeah, I think you are right, it looks more likely to be ROM related, but I'm not fully sure.
So... are you actually very sure of your answer (that JB will fix this) now you read the actual question more? Or just guessing Would ICS be enough or must need JB for the device to work?
About Samsung - if you know this model, you know that Samsung don't do a 4.x rom (ICS or JB). So it would have to be a custom ROM anyway, and I'd want to use a good custom ROM if possible. So best 4.x ROM experiences for "it just works" on this model phone?
Stilez said:
Like you say, it isn't "off topic", eyes were fully used. The forum is used for other posts about ROMs, internal memory, firmware, hardware, modding etc so it's in good company :angel: (and Alucard1989pl - maybe use eyes like iamareebjamal? Read before failing @ lulz? Not what a senior member's posts should be like, sorry)
Anyway thank you for editing your post. Yeah, I think you are right, it looks more likely to be ROM related, but I'm not fully sure.
So... are you actually very sure of your answer (that JB will fix this) now you read the actual question more? Or just guessing Would ICS be enough or must need JB for the device to work?
About Samsung - if you know this model, you know that Samsung don't do a 4.x rom (ICS or JB). So it would have to be a custom ROM anyway, and I'd want to use a good custom ROM if possible. So best 4.x ROM experiences for "it just works" on this model phone?
Click to expand...
Click to collapse
You did not get my point.
Sorry
iamareebjamal said:
You did not get my point.
Click to expand...
Click to collapse
Perhaps say more plainly. If the question is lol, then maybe explain how to find out from others what version or ROM might enable HID BT without asking, or where is more relevant on the site than here. It seems a sensible question and this is the forum where other ROM questions on this handset get asked, so I'm honestly confused. If asking Samsung was sarcasm and not j/k, then it was a bit pointless - when you tell someone that 4.2 is going to work, a reasonable person asking a reasonable question who is told that by a senior user will take the answer as sensible.
Let's start again, and speak simply. I have a Bluetooth compatibility issue on the stock 2.3.6 manufacturer's ROM for this model (S5830i). I don't know enough to know if a 4.x ROM will probably fix it or not, and if so which of the custom 4.x ROMs for the S5830i has the best chance of "just working" and fixing it. Samsung (obviously) don't do a 4.x ROM and I prefer a custom good quality ROM anyway. This seems to be the right forum to ask hardware/firmware/custom ROM questions on the S5830i. If you can help with advice and answers, then thanks. If there's a more appropriate forum on XDA for this then can you tell me which one?
Stilez said:
Perhaps say more plainly. If the question is lol, then maybe explain how to find out from others what version or ROM might enable HID BT without asking, or where is more relevant on the site than here. It seems a sensible question and this is the forum where other ROM questions on this handset get asked, so I'm honestly confused. If asking Samsung was sarcasm and not j/k, then it was a bit pointless - when you tell someone that 4.2 is going to work, a reasonable person asking a reasonable question who is told that by a senior user will take the answer as sensible.
Let's start again, and speak simply. I have a Bluetooth compatibility issue on the stock 2.3.6 manufacturer's ROM for this model (S5830i). I don't know enough to know if a 4.x ROM will probably fix it or not, and if so which of the custom 4.x ROMs for the S5830i has the best chance of "just working" and fixing it. Samsung (obviously) don't do a 4.x ROM and I prefer a custom good quality ROM anyway. This seems to be the right forum to ask hardware/firmware/custom ROM questions on the S5830i. If you can help with advice and answers, then thanks. If there's a more appropriate forum on XDA for this then can you tell me which one?
Click to expand...
Click to collapse
Its quite clear alucard is 5 years old due to the level or maturity of his answers and replies "I can't help you I'm a horse" you clearly don't deserve the "senior member" title, also as I have explained my views on this new super thread for all users questions numerous times I won't bother explaining again, yes I support areebjamal in keeping the forum clean I just don't think that's the answer... ill attempt to contact a senior mod in trying to get a new section made for us, if we all sign a petetion saying this is what we want surely they will help us
Anyways back to the question, if your device is clearly saying its not supported its obviously not going to work, it sounds like a hardware limititation as our phone probably cannot accept wireless input... I highly doubt flashing a new rom will fix this,
P.s Alucard GROW UP
The usual "Xx James xX" only on mobile...
(Sent Via Xda Developers App)
Xx James xX said:
Anyways back to the question, if your device is clearly saying its not supported its obviously not going to work, it sounds like a hardware limititation as our phone probably cannot accept wireless input... I highly doubt flashing a new rom will fix this
Click to expand...
Click to collapse
Well that's the thing... it can do Bluetooth, it can locate the device... it can communicate with the device... the error it's giving isn't a protocol or communication error, it's simply saying that the 5830i + Samsung Gingerbread stock ROM "isn't suppported"... and that sounds like "It would work at a hardware level but the OS doesn't handle this BT Keyboard, or some kinds of BT HID devices."
The changelog for 4.x shows a lot of "Bluetooth HID devices" now working with Android, so it could easily be a simple problem that 2.3.x won't cope but 4.x.x will. Is there any way to check that, that you know, though? My keyboard's linked in the first post.
Stilez said:
Well that's the thing... it can do Bluetooth, it can locate the device... it can communicate with the device... the error it's giving isn't a protocol or communication error, it's simply saying that the 5830i + Samsung Gingerbread stock ROM "isn't suppported"... and that sounds like "It would work at a hardware level but the OS doesn't handle this BT Keyboard, or some kinds of BT HID devices."
The changelog for 4.x shows a lot of "Bluetooth HID devices" now working with Android, so it could easily be a simple problem that 2.3.x won't cope but 4.x.x will. Is there any way to check that, that you know, though? My keyboard's linked in the first post.
Click to expand...
Click to collapse
It does look like this can be solved by upgrading your firmware, however this is impossible our phones cannot run any official or unofficial newer android systems we don't have the minimum requirements (limited by ram and space) flashing new roms (custom roms) does not increase your android version its still 2.3.6 just the text been edited to say 4.1.1 etc.
My advice is get a new keyboard and test it immediately so if it doesn't work you can return it... just ask around PC/mobile shops for a galaxy ace compatible keyboard...
The usual "Xx James xX" only on mobile...
(Sent Via Xda Developers App)
Being a Member of XDA for a while now I recall in the past on different models that XDA use to create sub-forums for Carrier Variants. I.E. Verizon, Sprint, GSM based. This was helpful for the noobs and Rom creators in making sure that Noobs didn't flash the incorrect Rom or Recovery.
Looking at the HTC One Max forums there occasionally is this confusion as members will post a general variant specific issues and a novice not knowing the difference would unintentionally use it thinking it applied to their device. Some Devs don't identify there Roms or indicate a variant which contributes to the issue.
I think it would be very beneficial for development on this device to have Variant based sub forums. Additionally having variant based sub-forums will help identify Underdeveloped devices.
Just my 2 cents.
DeadPhoenix said:
Some Devs don't identify there Roms or indicate a variant which contributes to the issue.
Click to expand...
Click to collapse
I'm sure when we get way more than 3 threads in original and 3 in development they will look at dividing the Max forum. Until then we need anyone that posts anything to ensure they identify what model it will work on. I believe most of the development done for us thus far does not identify which model it works for because it works across all (in one form or another).
To be honest most if not all of the issues people have had thus far is because they are not searching and reading to understand something before they do it. I guarantee a dev or someone with knowledge will try to help the best they can. BUT no one wants to help someone that doesn't try to help themselves by understanding what they are doing first.
If anyone notices that some development is device specific and it is not labeled as such then ping the dev and ask that they identify it appropriately. And if anyone feels strongly enough that something is not labeled or mislabeled that could end up causing issues with someone's device then AFTER ASKING THE OP to update feel free to contact one of our mods to correct or close the thread until it is adjusted. Many hands make light work...
i can see both points here
oneandroidnut said:
i can see both points here
Click to expand...
Click to collapse
I can see the point as well. But it will be a while before the forums are divided if at all. I said "until then" because we all need to work together now to police the threads to make sure things are made clear if they are not.
Jiggity Janx said:
I can see the point as well. But it will be a while before the forums are divided if at all. I said "until then" because we all need to work together now to police the threads to make sure things are made clear if they are not.
Click to expand...
Click to collapse
yeah i know what you mean. we clearly need more roms and development before anything gets split up
oneandroidnut said:
yeah i know what you mean. we clearly need more roms and development before anything gets split up
Click to expand...
Click to collapse
I know coming from the Motorola Droid HD forums that the impact of not separating them is lots of "Learning Experiences". I am quite learned in the rooting/bootlocker experience and even I was confused by the variants in that forum. I got it sorted out but it took longer then is should have.
I am in the process of learning java and android development and I plan on properly labeling my threads and apps. Oh and Blender for Custom Boot Animations. I have a Plan for A Doctor Who based Animation.
Plus I like tidiness and organization. Makes things more efficient.
How do I tell which version of the One Max I have?
It's one of the 32 gig versions, it's gsm and works on United states ATT. baseband version is 4T,27.3218.14_10.33C.1718.01L Software number says 3.15.1540.1 I think it might be the Hong Kong or British one, but it's been quite confusing trying to figure out which is which. I bought it off Amazon, so I know there's a chance that the software has been "improved' a bit.
Thanks for any help-I did try to search on it, but wasn't finding anything with useful info for me, or possibly I just don't know where to look. It's been some few years since I had an HTC..I bought the original G1 on opening day
Any help, or even just a point in the right direction would be most appreciated. I'd like to get this sucker rooted and get rid of the crapware as soon as possible
Hi everyone.
So I've been with this question in my mind for some time now... Are they really unbrickable? I have a ZTE Blade L3 on which flashed infinite times ROMs on it. Some completely bricked it - it couldn't even charge. It has a MT6582M processor on it. It was COMPLETELY bricked. And I always got it to work again. Never bricked it for good - and I did many stupid things on it, many experiments. And after a bit, SP Flash Tool would always flash stuff back to it even by flashing wrong ROMs on it.
I also believe I flashed a wrong ROM to a friend's Elephone P8000 B which has a MT6753 processor on it. I thought I had bricked it (this is why I think I flashed a wrong ROM on it) - but SP Flash Tool got back working after a few tries. I did what I wanted with the phone and it didn't brick.
So my thought is that ANY device with a MediaTek chipset with a ROM and a scatter file available and an always unlocked bootloader (preferably - as my Blade L3 had, I believe - since I never heard of this until weeks ago), might be unbrickable. I, supposedly, can do whatever I want on it and I'll always be able to unbrick it.
Is this true what I just wrote? If it is, then I'll try to never leave MediaTek powered devices.
Note: A thread confirmed this thought I had for some time until I found this thread, but it only says it about MT65xx devices, not all the others: https://forum.xda-developers.com/showthread.php?t=1943442 --> "Added on Nov 23, 2012 - MT65xx is truly UNBRICKABLE".
Note 2: Also....... After now reading back a bit of the thread, I found out I did exactly ALL the opposite they recommend there in caps and the phone always unbricked....... XD. So I'm a bit confused with all the careful people are about MediaTek powered devices when I was not careful (stupidly, I know), though it always worked. I have the phone since 2015 and stopped using it last year, but I believe I did the opposite of those things, even though I'm not completely sure. And again, never permanently bricked.
Thank you for any informations!
I'm not going to lie to you, your probably not going to get any other replies to the book you wrote above... I will answer your question however. There is not a single mobile device out there that cannot be unbricked as long as the issues that occurred to cause said brick remains at the software level. It don't matter what brand or carrier it is. If it is a software related issue then it can be fixed as long as you have the knowledge and tools required to do so. As for your experimentation using root, I have done many experiments myself and there are many many things you can do using root that will permanently brick your device. Sounds to me like you got lucky. Simple as that. I'll end this by saying, please do not post your entire relationship with your favorite phone in a single thread like you did. Nothing personal but many probably did not stay long enough to finish what you wrote. You have a valid question. However the rest was just unnecessary and to many, a waste of their time. Hope I helped.
Hi. I didn't even remember about this anymore. This last year I was told I write too much unnecessary things - just like you did. I've been trying to correct that and I believe I improved (no idea if much or not). When you said "the book you wrote" I got embarassed in advance because I knew what was going next, and when I scrolled up I got scared and even more embarassed and it's still increasing as I think more about it . Christ, how did I even post that. I'm very sorry........ I guess we learn as time goes by.... (hopefully haha). Hopefully now it's good enough. If it's still bad, I'll be happy to receive the advice, as I am with the one you gave. Thank you. For everything you said, actually.
Spoiler: Not needed, just curiosity of why I wrote it so big
EDIT: Just a small explanation of the why I wrote the text so big, which was I'd prefer to give all the informations right at the start so people can know exactly what was done and say things according to that. Instead of assuming I did things I might not have done and answer something that might not be correct in my case. But then I write a book and that's beyond stupid. So I've been trying to correct that. That's the wrong point of the view and I think I still need a bit more time, but hopefully I'm getting there - maybe I should start posting on Reddit hahaha. Posting things is not that old for me. Started a few years ago (21 years old - a bit late for my age, I guess, but I didn't go on Internet that much before).
My intent was not to embarass you. I apologize. I should have checked the date this was originally posted. I do hope i was able to answer your question though. That was my true intent.
Tofor said:
My intent was not to embarass you. I apologize. I should have checked the date this was originally posted. I do hope i was able to answer your question though. That was my true intent.
Click to expand...
Click to collapse
Ah no problem at all. Gotta be corrected in some way . That happens with me when I see an enormous stupidity made by me which I did not realize at the time - and this one is 5 months old, which puts it worse haha.
That shall work so I won't forget of not doing this again in the far future xD. Before, some people would tell me about and I'd notice it was a wall of text (like once a person told me). And I appreciate all those who warned me about it. Sooner or later I'll get to a decent amount of text, depending on the forum. I think I didn't know what a paragraph was, as a start xD (though, what you saw there was already an update....). It's still a big post, I think, but hopefully it's readable now. If it's not, I'll cut more of it.
But yes, you did answer the question. Thank you. But to complement it, if you remember, at least, what experiments with root can completely brick a phone? (So I know I won't try them, as a start, but it's also a curiosity.)
Well a good example of some things not to do is changing the system files to allow the device to operate at a level it was not designed to operate at. For example. Messing with the kernel to make the processor run at a higher speed, same goes for the RAM. This will cause it to overheat and will basically fry the system board. Also if you are not sure what you are changing then dont change them. Nothing like accidently changing the EFI settings to where it no longer knows where the internal storage addresses are and does not know it has any type of storage to boot to. However a lot of the efi should be copywrite protected where even a root user cannot modify them but trust me... its possible and may still be repairable but only by the manufacturer who has that level of access and definitely not worth what it would cost. Keep an eye on any files you modify for a copywrite at the top of the file. Changing copywrite files will most likely get you in a whole lot of trouble. If you end up having a web adress listed in the build.prop on every android device you own that brings you to the developers terms and conditions then stop messing with system files. This is more or less a warning telling you that you are breaking the terms and conditions. I would libe to continue but then i would be contridicting myself on my comment about very large messages in the forums. If you would like to know anything else please feel free to PM me and lets put an end to this thread lol.
Guys, speaking of devices with MT chipset, I have a Hannspad HSG1341 that was running Android 5.1 and wanted to root the pad using some tutorial I saw with magisk by installing the APK on this device which creates a modified boot.img. Then using SP Flash Tool I tried to reinstall the stock firmware by replacing the boo.img created by magisk and now the pad would not power on, I have tried searching for means to restore this pad but nothing. Even SP flash tool is now displaying s_ft_enable_dram failed (4032). So please off anyone has any idea how to resolve or is the pad dead for good. The chipset is MT8163. Let me know if you need more info to help out
thanks