Tips and Tricks - Newbies guide ESPECIALLY for Imate Users - JAMin, XDA Neo, S200 Software Upgrading

As posted by me on Club Imate SUPPORT Forums ,
These may or may not be advised by the support staff here, but after using the Prophet device and Magician I can advise this if you face major isssues like slow downs or errors in your device (software)
Option 1:
Hard reset, and softreset after the initial OS setup and BEFORE the 3-2-1 countdown hits 2-1.
Check speed and software and stability. Check features missing from before (if any).
Option 2:
Reload / Downgrade to the FIRST ORIGINAL Firmware ROM (usually the 1.0.0 series) and see if your issues were working on the original debut ROM or not. If issues, persist, upgrade to Option 3:
Option 3:
Upgrade to next build ROM (not the latest), just the next one that was released after 1.0.0 series and check, if still issue , continue upwards/forward to newer and newer ROMs till you reach the latest, If your issues get fixed before you get to the latest ROM, please post a topic telling us and them so they can add that feature from the old ROM to the latest fixing the issue. If issue persists,....read on...
Option 4:
Post here, Call Support, Call IMATE rather than CLUBIMATE...unless both are same ( I didnt check).
and Option 5: (where all fails)
DO a google for your issue, find a fix if none, see if DOPOT or O2 (forgot their name of the same prophet device) have a rom which doesnt have your issues, forget about the support youre supposed to get by staying with Original ROM (as you see the above steps all failed and you used everything possible and just cant wait or are in stage where you want to sell your device), upgrade to another brand ROM and hope for the best - if it still doenst fix it , then you know its a MAJOR GLOBAL bug, reload / upgrade / downgrade to Imate JamIn Rom again and ask for support
Tips can be used on all models of Imate Pocket PC's as long as you know which other ROMS can be used (IMate Jamin is a Prophet Device , O2 Mini is a Magician, etc)

Shivam, good stuff. You might want to post this in the wiki, since posts tend to drown on the forum!
V

thanks...will do

Related

Help Upgrading my M5000 to WM6

I am a new owner of SPV M5000..It is my first time upgrading my unit and I have decided to use Jwrightmcps Crossbow ROM Update 2.02.02 WWE rom because it is receiving lots of positive feedbacks..I have already downloaded the rom for M5000..What should I do next?Do I just need to click the .exe file or what?Or if there is any other rom that you could recommend,tell me please...
WM5 or WM6?
Thanks a lot guys
it depends on what do you want to do with your device.
if you need a very stable ROM, and a Wifi, Email, Bluetooth etc. working, then you should upgrade to the last version of WM5. for this you must go in the "Universal Upgrading" forum.
WM6 is much faster, but sometimes there are problems with bluetooth handsfree, and with the wifi (you cannot access some specific pages, but you can access other) and with others.
whatever you choose, keep in mind that upgrading your SPV can be dangerous if you don't fallow all the steps.
First of all, be patient and read the Wiki http://wiki.xda-developers.com/. A lot of things are explained there.
After that, read as much threads as possible. Always read the threads of the ROMs you want to install. you will find out all the potential problems with the ROMs and you might decide to use a different ROM.
Keep in mind that you will loose the waranty of the device by performing an ROM upgrade.
1
the first thing you must do, is to upgrade the bootloader.
for this, go here: http://wiki.xda-developers.com/index.php?pagename=Universal_Bootloader
2
the second thing you must do, is to unlock your device. in this way you will be able to use different SIM cards, not only Orange ones. you will be able to use T-Mobile, O2 etc.
it is important to remove your SIM Lock before going any furthere.
for this you must go here: http://wiki.xda-developers.com/index.php?pagename=Uni_Simlock_by_Buzz_and_team
3
after the SIM unlock, you will have a Radio version 0.00.00
you need to upgrade your Radio. the latest Radio is 1.15.00
for this you must go here:http://wiki.xda-developers.com/index.php?pagename=UNI_Radio
you can download the Radio from here: http://rs45.rapidshare.com/files/21256271/11500_Radio_only.rar
4
with your new radio 1.15.00 you must upgrade the bootloader again.
so again go here and repeat all the steps: http://wiki.xda-developers.com/index.php?pagename=Universal_Bootloader
5
now you can upgrade the ROM. to do that, download what ROM you prefere and then go here: http://wiki.xda-developers.com/index.php?pagename=Uni_ROM_Upgrade
i advice you not to hurry and upgrade your M5000. spend more time on the forum, read the whole Wiki http://wiki.xda-developers.com/ and learn more about your device. probably you still don't know how to enter in bootloader, how to hardreset your device, what to do if you get stucked in bootloader mode etc.
meny people brick their devices. for example, if you unplug your device during ROM upgrading, you will no longer be able to use the device. it will be gone for ever.
don't hurry to upgrade. there are meny meny things to find out about your M5000.
good luck !!!
thanks
I just did the upgrade without upgrading my BL and radio version..Everything went fine...I am a happy user now of WM6 on my M5000..
Thanks a lot

After the HardSPL...

Ok after doing all that was told to do to flash a G4 (which I did sucessfully) It does now show the SPL to be 2.21.olip.
At the end of the instructions says:
"After it is complete, your device will automatically reboot. The IPL version will be 2.21.0001 and the SPL will be 2.21.olip. If you see this then HardSPL was successfully flashed to your device.
Now you have HardSPL. You can flash any ROM using the RUU provided in the ROM package, should you have trouble with upgrading, try Mun's RUU."
I flashed my G4 Wizard with the new Diamond "clean" version. I think I want more bells and whisles; Question is...Do I have to do everything all over again or can I just flash with a new rom to a better OS?
I did try to flash to the Hyperdragon 6.1 and the SNN Diamond but, I think the OS I just flashed is too new to reflash to the others (error 264). (maybe I just answered my own question) But the HardSPL IS in there.
Someone please tell me what you think.
Thanks you!
Kim
Depending on my own experience you don't need to do hard SPL all over again. all you need to do is to do a good hard reset and try to update with nice and slow steps
i had a G4 before my current G3 and i know wht i'm telling you
just care to review these steps
- 50% battery or more (100% recommended)
this is a must .. cant flash without this condition
- laptop or pc with ups (you dont want to brick ur device cause electricity was out!) or you can risk and update on power supply
- use faria RUUs (they are the best) they can be used with any rom.
- connect the wizard to the pc after the hard reset (dont forget to backup) and follow the on screen (wizard not pc) till u get working windows mobile device
- when asked for setting ur device .. click escape (as said ... this device is guest till it has the WM that i want!)
- finally try it's right rom it's G4 safe if you ask, you'll find its link in my signature, also i suggest using radio 2.19
- last hint .. never use a rom with IPL or SPL. they will brick ur device (it did to mine )
any more help?

Facts about version 2.03TX and bootloader

I have two magicians, and I read many posts about nonchangeable version 2.03TX.
I test it, and upgrade one unit. After upgrade really is not possible change any (OS or bootloader). Bootloader cant vrite itself or OS memory. I try all known techniques - SDboot, TTY (lnb, s2d d2s...) via USB, and standart os upgrade via PC (of cours, noID too).
So I have two magicians, then i use good tool from "itsme" called pmemdump.exe (thank you for your good job) and download OS images and bootloader images from my magicians. The reason is:
I dont say when, and/or why, but in some magiciansThe 2.03TX destroy bootloader!!
In my flashed magician is destroyed (nulled) area from 0x10000 to 0x10080.
I attach good (before upgrade) and destroyed (after upgrade) bootloader for comparsion
Maybee if "itsme" (or anybody other? ) create new version of pnewbootloader.exe compatible with version 2.03TX (because under this version OS it not working) then tens of magicians with flashed 2.03TX will be upgradeable again . (I can send any dump if it will be need, or try apply new version on my magicians).
hi mate, i 've had installed 2.03tx and 1.13 radio on my qtek s100 for about one year...
i've had no problem in downgrading radio to 1.12 and flashing device with cotulla rom,
the only problem is that cotulla rom does not support samsung touchscreen
my bootloader is 1.02
the only trick to update i've used is to keep activesync loaded with "allow usb connection" unchecked in settings. then it worked like a charm...
I try it too with unchecked "allow USB connection" in AS (and i have XP). By me (and many others) the problem is owerwrited bootloader. You can see attached files and compare it, you will be see...
You are right, many problems with flashing is between chair and keyboard But not now.
You have the same version of bootloader like me, then probably in version of bootloader its not. I have originally T-mobile MDA compact.
Can you send me dump of your bootloader for compare?
Sorry for my bad english, i am from Czech.
yes mate no problem, link me to a guide for bootloader dumping, i've nevere done it...
ps: good luck for yours magician
Hi Shelver,
I have 2.03TX in only one magician. The second unit is powered by Cotulla WWE_03 now
Download and unzip this: http://www.nah6.com/~itsme/itsutilsbin-20090515.zip
Connect and synchronize via AS your magician, stay connected (this util working via Active Sync) and in comand line (IN win XP of course, in vista its not guaranted) go to your unzipped directory and write this (without commas):
"pmemdump 0x80000000 0x00040000 boot.bin"
and wait few seconds to done.
It read flash from address 0x80000000 to 0x80040000 (lenght 0x40000) and store dump to file "boot.bin" Its bootloader area. Then you can send me it, compare with my posted bootloaders...
shelver said:
hi mate, i 've had installed 2.03tx and 1.13 radio on my qtek s100 for about one year...
i've had no problem in downgrading radio to 1.12 and flashing device with cotulla rom,
the only problem is that cotulla rom does not support samsung touchscreen
my bootloader is 1.02
the only trick to update i've used is to keep activesync loaded with "allow usb connection" unchecked in settings. then it worked like a charm...
Click to expand...
Click to collapse
Me 2, upgraded from tx203 to Cotulla's rom and back for some SMS backup and then upgraded to Cotulla's rom again.
I think I can go as many times as I wish with my magician.
philiplam said:
Me 2, upgraded from tx203 to Cotulla's rom and back for some SMS backup and then upgraded to Cotulla's rom again.
I think I can go as many times as I wish with my magician.
Click to expand...
Click to collapse
You are lucky man I try it only one time, and bootloader is broken.
I have magicians only as toys, then, if it will be problem for me, then i repair bootloader via JTAG I only try 2.03TX, and try search some help for unlucky mans, who havent JTAG Now i have one broken, and one OK. But with Samsung LCD R3 . Maybee, i change display, or upgrade it to 128MB RAM for try _R1
I am HW developer, so HW problems is easy for me I create car multimedia PC on OMAP3530 platform now for my friends. Its better toy for me, magician is lovely history Only SW is hard to write to me
hi certik, my magician is still with cotulla rom and doesn't boot because of touchscreen driver,i've not flashed it again because of i don't use it.
i'm waiting a new rom,
however when flashed i'll send you my bootloader backup
shelver said:
hi certik, my magician is still with cotulla rom and doesn't boot because of touchscreen driver,i've not flashed it again because of i don't use it.
i'm waiting a new rom,
however when flashed i'll send you my bootloader backup
Click to expand...
Click to collapse
OK, Ill wait. I dont need it really, i have stored good copy of bootloader, i need it only for compare
And if you wish, you can flash cotulla WWE_03 ROM (you can directly from _04 to _03 say Cotulla) In this version touchscreen driver worked fine.
e-certik said:
OK, Ill wait. I dont need it really, i have stored good copy of bootloader, i need it only for compare
And if you wish, you can flash cotulla WWE_03 ROM (you can directly from _04 to _03 say Cotulla) In this version touchscreen driver worked fine.
Click to expand...
Click to collapse
humm, ok mate, just the time to flash it with WWE_03 ROM then
hi mate, done, here is my bootloader
ps:touchscreen is now ok, thanks
Hey, you are fast
Thanks for bootloader, its the same as my original bootloader
good luck mate
e-certik said:
I have two magicians, and I read many posts about nonchangeable version 2.03TX.
I test it, and upgrade one unit. After upgrade really is not possible change any (OS or bootloader). Bootloader cant vrite itself or OS memory. I try all known techniques - SDboot, TTY (lnb, s2d d2s...) via USB, and standart os upgrade via PC (of cours, noID too).
So I have two magicians, then i use good tool from "itsme" called pmemdump.exe (thank you for your good job) and download OS images and bootloader images from my magicians. The reason is:
I dont say when, and/or why, but in some magiciansThe 2.03TX destroy bootloader!!
In my flashed magician is destroyed (nulled) area from 0x10000 to 0x10080.
I attach good (before upgrade) and destroyed (after upgrade) bootloader for comparsion
Maybee if "itsme" (or anybody other? ) create new version of pnewbootloader.exe compatible with version 2.03TX (because under this version OS it not working) then tens of magicians with flashed 2.03TX will be upgradeable again . (I can send any dump if it will be need, or try apply new version on my magicians).
Click to expand...
Click to collapse
as you i still have a hope to fix my poor magician
any kind programer can do what you have said will make me and many other happy again
i have the hope

New to the world of PDA's

Hi all,recently brought 2nd hand O2 exec windows 6.1 installed.
opening screen has these numbers
D.07.60 R
0.082.104
0.80.00
unit works ok but the phone won't connect at all 2g or 3g sim card
after doing lots of reading i gather the radio rom needs upgrading or do i upgrade the whole software.
I downloaded JASJAR_ME_13082_171_10900_wwe_ship but haven't run the upgrade as i don't want to kill the unit without finding out if it is safe to run or is it the latest update tool.
Also if i do the upgrade do i lose windows 6.1 installed.
Appreciate some help here.
p.s I'm running vista on pc
Welcome to forums
You have one of the best HTC devices ever made!
Have a look here to get all the info about it:
http://wiki.xda-developers.com/index.php?pagename=HTC_Universal
You can flash another ROM and perhaps you can solve your issues
Good luck,

[Q] Update Error C00D070A There's a communication error with your phone.

Hello,
After following the following thread http://forum.xda-developers.com/showthread.php?t=1306415 ([CAB] Official WP7 Updates List: 7.10.8107 + ALL LANGUAGES complete + OEM updates) to the letter I repeatedly receive the same error on two different PC's. UpdateWP: (Device ID Left Out) Update Error C00D070A There's a communication error with your phone.
If I run UpdateWP.exe /list I can see my device.
I read through the entire thread, all 75 pages and could not find an answer to my problem. I also scoured the rest of the site for two days to no avail. @jellenl post: Problem with 'WP7 Update Cab Sender' http://forum.xda-developers.com/showthread.php?t=1291536 was the closest reported issue similar to mine. I have replied to that post and am waiting for additional information.
Any help would be greatly appreciated, the newer software is needed to address the Exchange 2003 bug on our phones.
Verizon HTC Trophy MWP6985
OS Version: 7.10.7720.68
Firmware revision number: 2305.13.20110.605
Hardware revision number: 0003
Radio software version: 1.53.00.12.01_23.17w.05.13U
Radio hardware version: 3.2.3.D4
Bootloader version: 2.1.230513.10
Chip SOC version: 2.3.0.5.13
PCs: Windows 7 Professional SP1 (tried 64bit and 32bit)
Thanks -Airstream
Problem Solved!
After manually backing up my data (there are automated tools you can use) I factory reset my phone and attempted an update to 7740 using the following tool http://forum.xda-developers.com/showthread.php?t=1315179 with a custom CabData.xml that I created for my phone (VZW Trophy). I updated my OS (7720) and Languages (English - United States (0409) and Spanish (0C0A), the two languages installed by the default) to 7740 successfully, and then updated OS and Languages to 8107 succesfully. After the update process I reseated my battery and factory reset the phone once again, and as expected the latest OS 7.10.8107.79 (8107) is still present on my phone.
It's important to note that I have a factory ROM and my phone already had it's firmware updated automatically (via Zune) to the levels noted in my original post. I believe the WP7 Update Cab Sender would have worked as well but preferred the slick interface wCabSender provided, thanks guys!
No thanks Verizon and HTC, a BIG Thanks to all at xda-developers!
How does your phone work using this method? I attempted to cook a rom with 8107, but Phone app would't load anymore. XD
Also, using this method, can you dial ##PST# without the phone freezing? The current DFT Freedom V1 from Verizon Wireless Trophy can't use ##PST# with their cooked 8107.
I have yet to try to manually update to 7740+ and beyond. I wish VZW would get off their butts and support our phone, but I'd wager that we've seen the last updates. Verizon isn't even interested in putting more WP7's on the network last I knew.
Also, how did you edit CabData.xml?
@TheXev, Thanks for your post
As I mentioned earlier I have a factory ROM (at no time did I ever attempt to alter the phone), We purchased the phone a month ago to test in our enterprise (as a BlackBerry alternative - we had already tested iPhone and Android and were not happy with the results) and it wasn't until we rolled out a second device (beta group) that we discovered the Exchange 2003 bug (email responses had original data removed) and determined via the Windows Phone Website that OS 7740 had corrected that bug. I still am not clear on why my phone would not upgrade without a factory reset, but it was a small price to pay for the bug fixes and enhancements brought through to OS 8107.
I wasn't aware that I could dial ##778 for field diagnostics (thank you for that information) my phone dials the number correctly and without freezing.
If you decide to upgrade I would encourage you to use the wCabSender, it can be found at this forum http://forum.xda-developers.com/showthread.php?t=1315179 I have uploaded my updated CabData.xml at the end of the thread.
On a side note I already had the Windows Phone Engineering Flash Tool installed on my machine when I attempted my upgrades using WP7 Update Cab Sender, this tool is not installed with wCabSender and I'm not certain if it's necessary, if you run into trouble using wCabSender (it not launching) you can download WPEFT from this forum http://forum.xda-developers.com/showthread.php?t=1306415 also keep in mind that wCabSender has prequisites (I believe) .NET Framework 4.x, etc.
As I mentioned earlier I have uploaded the edited CabData.xml via another forum, my updated version includes the latest Firmware: 2305.13.20110.605
and Radio software version: 1.53.00.12.01_23.17w.05.13U and all OS updates and Language packs (Eng. and Esp.) needed for a Verizon Trophy. The wCabSender's slick interface allows you to download the updates into the /Downloaded directory. The CabData.xml can be found in the /Models directory and can be updated by a text editor, I used notepad.
It is unfortunate regarding Verizon and their apparent lack of enthusiasm for WP7, we have hundreds of devices (mostly BB Not WP7) and even their T2 Enterprise Technical Support was unable to confirm if they had received notification for the update. HTC reported the same information and redirected me back to Verizon. Hopefully in the future MS can push the updates directly to the phones, until then I will continue to use invaluable resources like xda-developers to overcome these issues. Thanks Again!
I believe MS has a hit on their hands with the Windows Phone, which I believe will become more apparent with the release of Windows 8.
I concur on all points. Last night I was able to upgrade the stock 7720 rom to 8107 and have a working phone (I missed the language pack between 7740 and 8107). I used cooking methods and HSPL, so I didn't have to modify any files after tinkering.
In an enterprise environment, it isn't a good idea to void the warranty of the equipment with HSPL (or open up another can of wax my using an a unlocked phone).
I'm glad to see the phone fully works with 8107, but I have to wonder why Verizon didn't at least push the 7740 update for the reasons you stated.
I'll have to continue to work with DFT to see if we can figure out why their testing rom doesn't run ##PST#. My current 8107 build works fine with ##PST# now, but I haven't been able to fully unlock it (here is to tonight's digging).

Categories

Resources