Related
ok have just been given a xdaII by work but can not get past the cognito software it is running. I have no access to any of its features or even the software. i cannot delete software as it is for work any help would be very apreciated thanks
griz
anybody know this software?
Cognito Mobile Management is a powerful administrator function, enabling user rights to be applied to mobile terminals. Managers are provided with the tools to define parameters for voice and email usage; apply restrictions to Internet browsing; dispatch configurations, software updates, address books and system templates; and remotely retrieve detailed usage analysis. Most importantly all capabilities are executed remotely and discreetly.
Is this the Cognito you mean, grizly, or are you talking about the mobile messaging Cognito which takes over the entire device?
Messaging Cognito I can tell you a bit about - With the Siemens SX-56, the software installed itself from an MMC card. If you took out the MMC card and performed a hard reset it would go into normal Windows Mobile. However, you do lose ALL your messages. I've stopped working with Cognito units now so I couldn't tell you what they did with the XDA2 - though it's a safe bet it's in the Extended ROM. Unfortunately the software is pretty watertight. Early versions had bugs which would cause the phone tones to be heard when you hit the right regions of the screen - and, I think, allowed dialing! - but they probably fixed that (not that there was actually any way into the OS from the phone) so you're pretty much stuffed unless you overwrite the ROM. And then you won't have the Cognito software or data, and you'll be totally screwed.
grizly, I think there is a suggestion that Cognito lets the controller know when attempts have been made to circumvent the system, in fact every single keycode is probably uploaded at intervals. Is it worth trying? There is a reason for the installation of the cognito system, maybe you could buy your own phone and play to your hearts delight.
well i know the software is run from the memory card and it does take over the complete device so nobody actually knows a waay to get round this without losing information?
so can take it there isn't anyway then
You could try removing the memory card if present then doing a reset but as was said they have probably written bespoke software to the extended rom then locked so that even a hard reset will loop back to installation from extended rom which puts you back where you began but minus any data you may have had on the phone. can you say what it is you were hoping to acheive if it was possible to access the functions of the phone, or is it a secret?
The Cognito messaging software is basically a messaging app. Cognito used to use devices which had a 40x4 LCD display and a keyboard - clever little unit, looked quite robust.. but people still managed to **** them up on a regular basis. NTL used to use them as well as the company I worked for. They ultimately turned off the national radio network that the devices worked on - and instead of adapting the existing devices to run on GPRS or GSM, they backed out of the hardware thang and bought COTS devices. To save themselves many problems with support calls, they simply removed the ability to use any Windows functionality. I mean *ANY* Windows functionality. Many of our staff finished up with a laptop, a company mobile AND a PDA-Phone with the software on it. Which was a bit stupid when they could have just had the damn PDA and made calls from that!
grizly - is this the system you mean? With a grey background? There is NO way round it - even if you hacked up the installer etc and managed to create some magic key combination to show the Start menu/Today screen, you'd lose all your data and you'd have to call HQ and ask them to resend everything. And that gets suspicious after the 3rd or 4th time.
.. please don't expect replies within 24 hours every time - I sometimes don't check this board for a week and I'm sure others are the same
madkat said:
Is this the Cognito you mean, grizly, or are you talking about the mobile messaging Cognito which takes over the entire device?
Messaging Cognito I can tell you a bit about - With the Siemens SX-56, the software installed itself from an MMC card. If you took out the MMC card and performed a hard reset it would go into normal Windows Mobile. However, you do lose ALL your messages. I've stopped working with Cognito units now so I couldn't tell you what they did with the XDA2 - though it's a safe bet it's in the Extended ROM. Unfortunately the software is pretty watertight. Early versions had bugs which would cause the phone tones to be heard when you hit the right regions of the screen - and, I think, allowed dialing! - but they probably fixed that (not that there was actually any way into the OS from the phone) so you're pretty much stuffed unless you overwrite the ROM. And then you won't have the Cognito software or data, and you'll be totally screwed.
Click to expand...
Click to collapse
You said that after taking out the mmc and hard reseting the device it goes to normal Window Mobile but it doesnt for my MAgician PM10B. I even tried flashing it but still the Cognito Starts up itself.
Pls Help
just a single hard reset and the device will on with windows mobile logo and qualities
So I was thinking, after a error I received when updating my MCE PC.
In regards of PC when microsoft issues an update of windows 7 they do not have to think to much about hardware it is running on as drivers are done by manufacturer, ATI, Nvidia, intel or other. If they ever release a driver via windows update, any other driver the same, if all goes tits up you can go to safe mode and roll back drivers.
Now in case of WM6.5 drivers or other updates were downloaded from phone manufacturers website so they knew best how to mod it for their hardware and if all went tits up you could do a hard reset. Only good, tested mods went in to rom update.
Now with wp7, if I understand correctly, updates will become part of the original rom as there is no rom flashing by user. It has to be like that as if that would not be the case then hard reset could make the phone broken for hours until all your updates were up. So what if microsoft screws up and gets it wrong on their server and lets say HTC downloads a update for LG? It will screw up the phone and hard reset will not help. It does happen for PC's. With time there will be plenty more hardware out there so mistakes will be more likely. All you need is touch screen drivers to be buggy and phone might boot up but no access to it at all.
Who will take the blame for that? At first it will go back to seller on warranty but if there was a mass problem they would say no.
Look at apple, they release an OS update it is permanent. As they only have like 4 phones to deal with it is easy to test it. With time there will be plenty of wp7 models, just look at wm6.5.
How are we protected from that not happening?
Pretty sure updates are tested extensively by microsoft as well as the carriers.
How would WP7 be different than any other mobile OS in this regard?
i think desktop to phone comparison isn't really correct. with windows phone, MS knows what phones are being made and therefore can keep a proper database of these phones. why? well MS provides keys which get built straight into the memory of the phone (the issue with the HTC HD2 not working with WP7). so you won't just get any joe blogs install windows phone 7 on whatever they feel like it (as you do with wm6.5/android). so therefore, it's very rare that you'll get issues where the phone gets incorrect software not intended for it as MS can manage it properly on their servers, as well as pull anything that were rolled out straight off the phone (e.g. if an app misbehaves but somehow makes it through to marketplace, they can send a command to uninstall the app [same as iOS/Android]).
greener88 said:
Pretty sure updates are tested extensively by microsoft as well as the carriers.
How would WP7 be different than any other mobile OS in this regard?
Click to expand...
Click to collapse
On WM6.5 updates are seperate little programs, patches, if one does not work well with your phone or certain app you hard reset and not install it next time.
With WM7 all goes in, updates rom image and you are stuck.
The Gate Keeper said:
i think desktop to phone comparison isn't really correct. with windows phone, MS knows what phones are being made and therefore can keep a proper database of these phones. why? well MS provides keys which get built straight into the memory of the phone (the issue with the HTC HD2 not working with WP7). so you won't just get any joe blogs install windows phone 7 on whatever they feel like it (as you do with wm6.5/android). so therefore, it's very rare that you'll get issues where the phone gets incorrect software not intended for it as MS can manage it properly on their servers, as well as pull anything that were rolled out straight off the phone (e.g. if an app misbehaves but somehow makes it through to marketplace, they can send a command to uninstall the app [same as iOS/Android]).
Click to expand...
Click to collapse
You can compare with desktop, in case of desktop and WM6.5 you could select what to install, also you could always revert back if there were issues. With 6.5 by hard reset and reinstall minus not working app, on PC by rolling back the system.
As said above in WM7 when it is in it is in (that is if I got the info right).
In regards of keys, all you need is typing error. In regards of not working apps there is few that work on some WP7 phones and not others. Mistakes and half finished apps happen. I feel the same will happen with WP7 updates. Probably not now but look 2 years down the line where there will be 100's differant phone models.
Who will test all the updates, not MS and when update is out it is out. If the phone does not boot command to uninstall is not going to help. Especially that we are talking OS update. Apple can not send a command to rollback iphone 3gs from new-est os to one below.
Uh perfect example is apple where first release of iphone 4 os to 3gs did not work to well on all handsets, it was quite slow and they had to make another update. All users that did do it were stuck.
At the end we are talking MS, they do make mistakes. They do a lot of them on normal PC updates where patch does not work as expected.
I think you are mistaken. Every official update that has ever been done on my winmo phones was a full new OS and radio. Complete with hard reset.
nrfitchett4 said:
I think you are mistaken. Every official update that has ever been done on my winmo phones was a full new OS and radio. Complete with hard reset.
Click to expand...
Click to collapse
No that is 6.5, wm7 will be more like PC, no rom updating just small patches integrated in to rom via windows update.
ruscik said:
On WM6.5 updates are seperate little programs, patches, if one does not work well with your phone or certain app you hard reset and not install it next time.
With WM7 all goes in, updates rom image and you are stuck.
You can compare with desktop, in case of desktop and WM6.5 you could select what to install, also you could always revert back if there were issues. With 6.5 by hard reset and reinstall minus not working app, on PC by rolling back the system.
As said above in WM7 when it is in it is in (that is if I got the info right).
Click to expand...
Click to collapse
ruscik said:
No that is 6.5, wm7 will be more like PC, no rom updating just small patches integrated in to rom via windows update.
Click to expand...
Click to collapse
that was the same on wm6.5 and after a hardreset the update was still there (not working on custom rom's because they ripped the modules )
but MS didn't used it allot , Da_g has a whole thread of it explaining how cooks could use it to update there rom's from there own servers and .cert .
but a lot of cooks won't use this because you cannot protect your rom's any more
and ofcourse not cool for us ORD dud's
Microsoft specify the CPU and chipset to be used by every manufacturer, it is part of the specifications they have to adhere to to be granted a licence to use the WP7 OS.
Therefore the update should never brick the phone, as if it works on one it will work on all. That was kinda the whole point. It's a solution that sits in between the ass-crack tightness of Apple and the Grandma looseness of Android. I call it the Kylie zone.
Jim Coleman said:
Microsoft specify the CPU and chipset to be used by every manufacturer, it is part of the specifications they have to adhere to to be granted a licence to use the WP7 OS.
Therefore the update should never brick the phone, as if it works on one it will work on all. That was kinda the whole point. It's a solution that sits in between the ass-crack tightness of Apple and the Grandma looseness of Android. I call it the Kylie zone.
Click to expand...
Click to collapse
The Kylie zone
On that screens are not the same so here is one, then touch panel on screen, charging units or even sound output sockets. There is a lot. With time also chipsets/CPU will change. Like for example snapdragon 1.5ghz that is somewhere near to come out.
Ceesheim ok so it is there but not used. However you could always revert back to stock rom in 6.5 (unless total brick where bootloader not working) by means of download and flash. For WP7 we do not have that and there is no word about it ever being there officially. So if you brick via update you have to send it for repair.
I suspet MS did not use it to much for the same reason I am thinking off. Look at how many differnat devices there are for 6.5 with hardware ranging from identical to completly different.
I guess time will tell how it will all work, general idea is sound it is just that I do not feel comfortable with fact that if a update screws up my device I have to send it for warranty or shell out for repair.
ruscik said:
The Kylie zone
On that screens are not the same so here is one, then touch panel on screen, charging units or even sound output sockets. There is a lot. With time also chipsets/CPU will change. Like for example snapdragon 1.5ghz that is somewhere near to come out.
Ceesheim ok so it is there but not used. However you could always revert back to stock rom in 6.5 (unless total brick where bootloader not working) by means of download and flash. For WP7 we do not have that and there is no word about it ever being there officially. So if you brick via update you have to send it for repair.
I suspet MS did not use it to much for the same reason I am thinking off. Look at how many differnat devices there are for 6.5 with hardware ranging from identical to completly different.
I guess time will tell how it will all work, general idea is sound it is just that I do not feel comfortable with fact that if a update screws up my device I have to send it for warranty or shell out for repair.
Click to expand...
Click to collapse
we can revert back by flashing a new stock rom ( look at http://forum.xda-developers.com/forumdisplay.php?f=783 all the roms there can be used )
there are a lot of people who did that with a phone that had a demo rom (shop phones ) and after flashing a new rom al was working normal .
I'm sure we'll all be totally fine. The bootloader will stay intact, so even if you screw up the normal update. You could always flash the old rom on top with the bootloader still intact.
The only way your idea would work is if the bootloader itself got messed up in the process.
And in 6.5 you couldn't update your HTC Diamond 2 with the normal Diamond, or HD2 firmware. There are checks at the beginning to make sure this is for this exact phone. And in some cases, the checks even implemented being locked down to the region. We only were able to put whatever ROM we wanted to put on our phones when we totally took off that protection. And even then I believe you wouldn't have been able to put a ROM that wasn't meant for the phone on there.
ceesheim said:
we can revert back by flashing a new stock rom ( look at http://forum.xda-developers.com/forumdisplay.php?f=783 all the roms there can be used )
there are a lot of people who did that with a phone that had a demo rom (shop phones ) and after flashing a new rom al was working normal .
Click to expand...
Click to collapse
Uh did not see that. Good then.
I have been having a lot of trouble with my Epic's radio behavior since the EC05 radio update. It seems that the normal Samsung "radio stupidity" that I have seen in several of their devices is worse than ever now. The best radio for call performance I have used so far was DG27's (though not data). Essentially, what it is as far as I can determine by using utilities to monitor radio operation, is poor CDMA handoff configuration.
What it does is, for no good reason, switch from a cell site providing a good signal level, to one providing a bad signal level for no reason. Either this, or it holds onto a weakening set of towers while moving, until it goes out of their range and the call drops. The phone will then display the no service message for a few seconds, and then will pick up perfect signal from a different set of towers. I can even watch this happen by driving down a given road while on a call, with another phone in my cup holder. The Epic will start to break up and show very low signal levels, while the other is doing perfectly. Additionally, the direction you drive down this (2 lane) road also has an effect.
I have fixed this before on non smartphones by altering some of the CDMA radio values. T_Add, T_Drop, T_Comp, T_Tdrop. My solution is to increase the threshold on T_Comp a little bit, and drop the T_Tdrop also a little bit. The problem is that I cannot figure how to do this on this phone. Very little radio information seems to be available, and the utilities I have do not work completely on this model.
This issue with how they program their radios seems to be a common Samsung problem, to a much greater degree than with other manufacturers. Sanyo, Palm, and Motorola seem to do a much better job with this, even in cases where they use the same radio chipsets.
I am feeling like a lot of people will find this matter interesting and/or of benefit to resolve.
The only problem I see and I'm sure someone will correct me is the RIL is closed source. Also android was designed around gsm and not cdma. This makes the manufacture and carrier to design a "wrapper" to get the RIL to work on cdma. Now if samsung would release the source.code I'm sure making changes wouldn't be so hard
On a side note I know there's a dialer code ( I forget what it is ) that you can go and play with some settings. One of them being able to switch to cdma instead of cdma/gsm that it is by default.
Sent from my SPH-D700 using Tapatalk
Maybe try ##3282# or *#147852#
My data does the same thing on ec05. I'll have perfect signal and then all of a sudden nothing for like a minute and then it comes back. Least im not the only one
Sent From My Evo Killer!!!
musclehead84 said:
My data does the same thing on ec05. I'll have perfect signal and then all of a sudden nothing for like a minute and then it comes back. Least im not the only one
Sent From My Evo Killer!!!
Click to expand...
Click to collapse
It isn't the data driving me nuts. Data sessions pick up again quickly. It's the dropped calls. Either way, it is partially a symptom of the same problem. The phone is promoting weak towers, sometimes in favor of strong ones, to the active set - which it should not be.
MysteryEmotionz said:
The only problem I see and I'm sure someone will correct me is the RIL is closed source. Also android was designed around gsm and not cdma. This makes the manufacture and carrier to design a "wrapper" to get the RIL to work on cdma. Now if samsung would release the source.code I'm sure making changes wouldn't be so hard
On a side note I know there's a dialer code ( I forget what it is ) that you can go and play with some settings. One of them being able to switch to cdma instead of cdma/gsm that it is by default.
...
Click to expand...
Click to collapse
No and yes. CDMA support was a hack in versions prior to 2.0. Android 2.0 (and later) has inbuilt features intended to support CDMA networks. Some of the companies are still using some legacy code, and some of nomenclature used within the system parameters still reflects GSM however.
This, however, is irrelevant in my belief. I do not think that these parameters are a function of RIL, as RIL is simply the intermediary between the "computer" and "telephone" components in a smartphone. I believe that these issues exist purely, or nearly so, within the "telephone" section of the device.
running_the_dream said:
Maybe try ##3282# or *#147852#
Click to expand...
Click to collapse
What is this ##147852#? I cannot find it in any information I have, and it has no effect on the phone itself.
Not ###47852#. *#147852#. I don't know the name of the dialer. I call it the master meenu. It basically let's you access various front end user settings on the phone. I have used it to reset my 4g radio. Anyway, you may try the testing/phone information menu to change the cdma setting. I'm totally taking a shot in the dark on that, but it does seem to allow you to alter the radio preference.
running_the_dream said:
Not ###47852#. *#147852#. I don't know the name of the dialer. I call it the master meenu. It basically let's you access various front end user settings on the phone. I have used it to reset my 4g radio. Anyway, you may try the testing/phone information menu to change the cdma setting. I'm totally taking a shot in the dark on that, but it does seem to allow you to alter the radio preference.
Click to expand...
Click to collapse
Yes, totally misread that. Nothing seems to apply however, as I do not think it is a software parameter on the phone end. The WiMAX radio is software controlled, through a driver in the operating system. The combination of CDMA radio and baseband processor are more or less an independent device which essentially lives on its own, with its own configuration. It is told what to do through the RIL, which is a piece of software that allows the computer aspect of the phone to talk to the radio, passing it instructions which it then acts upon according to its own programming and configuration. The RIL also allows the radio to communicate its status to the rest of the system.
I am really thinking that this will not be a setting that can be modified from within the phone itself, but will require some external involvement, similar to QPST. On this chipset, however, QPST does not appear to be able to manage these parameters.
If you find out any more info please pass it along. Thank you.
Sent From My Evo Killer!!!
Ah that's really interesting. Wish I could help.
The details...
It's soft-bricked. It's missing any launcher apk capable of providing a home screen. It also has a problem with hardware acceleration (bad build.prop, my fault) resulting in a black screen. USB debugging is disabled as a result of the bad build.prop I expect. The screen responds to touch, the soft-buttons respond. I can pull up the on-screen keyboard using the soft-key shortcut, it's not visible but it does respond. I can trigger voice command mode, but I can't come up with anything useful to have it do given the limited commands.
The road already traveled...
Stock recovery comes up but recovering to the built in stock image doesn't work, it won't reload the default launcher or build.prop. Its talking to RSD Lite just fine, although no SBF so just info for now. I've played with some of the AT commands, but most of them come back with "NOT SUPPORT" which I take to mean either 'not supported', or 'you are not tech support'. Either way, that's what I know in that realm. PWR+VolUp gives me an "MBM Flashmode" screen. The version info that it gives is "Tinboost+ EVDO ROW". AFAIK the Tinboost+ was the xt535, perhaps they're using the same bootloader?
The possibilities...
Seeing as I have a bricked phone with a new one on the way, I'm thinking that this is an opportunity to hack it a bit further than most people might. In preparation for tearing the thing open and finding a jtag port I started reading through the FCC Documents on this thing. There should be a number of copper pads on the board, I'm thinking that a set of them ought to be a serial port or jtag port. The xt535 appears to have the same processor with a different modem, according to this pdf the xt535 (Qualcomm MSM7227A) is UTMS and the xt556/557 (Qualcomm MSM7627A) are CDMA, which matches our observations. It's possible, albeit unlikely, that the single-band xt557 is actually simply a re-branded xt535. Also, this github repo has a basic xt557/Tinboost+ makefile setup. This might be a starting point.
The tools...
I'm handy with soldering equipment, I have access to an oscilloscope and logic analyzer. I'm thinking of picking up a Bus Pirate or the like in order to hack some of the phone's low level connections. I have RSD Lite v6.1.5 + MTK Patch 28 and SUT LR v1.8.2. Android dev kit, etc.
The need...
I need ideas as to where to hack next. I need help figuring out the best candidate pads on the board to monitor. I'm interested in any hypothesis at all. I'll post updates as I discover new things, probably pictures if they're relevant.
I hope to benefit from someone's WIFI expertise.
Bought for my wife a T-Mobile branded SGS3 replacing her older SGS4G ["S 4G"] model for more power, memory, etc etc. I noticed from the beginning that, compared to all my other handsets, tablets, PC/laptops, this one was troubled on WIFI connections. Found lots of posts around the web, read up on fixes. Gathered the tools together, erased the ROM completely, started from scratch with stock T-Mo ROM, rooted and debloated it. Made some of the standard changes to WIFI options: stopped scanning, disabled power-saving, reset the home/office WIFI to channel 11 , "N" band only. Things improved in that stable, controlled setting.
but 'on the road' with multiple hotspots, hotels, offices, T-mo data service, etc it is still very difficult to use. It will drop otherwise good WIFI connections, and hang in the midst of operating on WIFI. To give a simple example: go somewhere new, find WIFI, connect to WIFI, check EMAIL, Facebook, Messages - find 10 or so messages unread unresponded, try to download/read/respond and the device will get maybe one or two, then simply stop responding. Wait a minute or two and you get the "WIFI Connected" notice again. repeat, repeat...
What I wonder: how many variants of hardware have there been for T-mo, USA, GS3? Is there a model version I can get that avoids this issue?
cognus said:
I hope to benefit from someone's WIFI expertise.
Bought for my wife a T-Mobile branded SGS3 replacing her older SGS4G ["S 4G"] model for more power, memory, etc etc. I noticed from the beginning that, compared to all my other handsets, tablets, PC/laptops, this one was troubled on WIFI connections. Found lots of posts around the web, read up on fixes. Gathered the tools together, erased the ROM completely, started from scratch with stock T-Mo ROM, rooted and debloated it. Made some of the standard changes to WIFI options: stopped scanning, disabled power-saving, reset the home/office WIFI to channel 11 , "N" band only. Things improved in that stable, controlled setting.
but 'on the road' with multiple hotspots, hotels, offices, T-mo data service, etc it is still very difficult to use. It will drop otherwise good WIFI connections, and hang in the midst of operating on WIFI. To give a simple example: go somewhere new, find WIFI, connect to WIFI, check EMAIL, Facebook, Messages - find 10 or so messages unread unresponded, try to download/read/respond and the device will get maybe one or two, then simply stop responding. Wait a minute or two and you get the "WIFI Connected" notice again. repeat, repeat...
What I wonder: how many variants of hardware have there been for T-mo, USA, GS3? Is there a model version I can get that avoids this issue?
Click to expand...
Click to collapse
Is the phone running full MD5 firmware?
Hardware issue if no restoring was done between devices.
Aerowinder said:
Is the phone running full MD5 firmware?
Hardware issue if no restoring was done between devices.
Click to expand...
Click to collapse
yes, in fact I made utterly sure because somebody else asked the same question, same issue. still very flaky. no odd modems or other custom 'wares, just rooted and a few unnecessary apps uninstalled. how many models of this are there, were they made in different locales?
I assume the SoC is the same, but what about antennae, internal connections, etc? any evil interactions between radios? we don't use Bluetooth, so that one stays off all the time assuming the softswitch works
cognus said:
yes, in fact I made utterly sure because somebody else asked the same question, same issue. still very flaky. no odd modems or other custom 'wares, just rooted and a few unnecessary apps uninstalled. how many models of this are there, were they made in different locales?
I assume the SoC is the same, but what about antennae, internal connections, etc? any evil interactions between radios? we don't use Bluetooth, so that one stays off all the time assuming the softswitch works
Click to expand...
Click to collapse
Well, as far as how many there are? A LOT! LOL! I'd imagine a few hundred thousand US variants, and for the T999 and its variants, close to a hundred thousand maybe? I really don't know, and those numbers did not come from anywhere but my head!
But as far as manufacturing, I am pretty sure they are all built in the same place. But, this does not mean that all of the components are from one location. In fact, from batch to batch of the same part, it can vary by where it was made, but also by what company made it. This is unlikely when dealing with the critcal parts such as the SoC, but the WiFi chip is a Broadcom chip. I have no idea if there are multiple manufacturing locations for it, but it is possible. The memory in all devices often varies greatly by the manufacturer.
Anyway, I do agree with Aerowinder. It is most likely hardware related. I'd look into a Warranty or Insurance exchange.