Note: You must be registered in order to post a reply.
To register, click here. Registration is FREE!
|T O P I C R E V I E W
||Posted - 26 mars 2009 : 00:43:36
I unboxed a brand new c520, was trying to install Miopocket on it. I charged the unit up fully and was in the process of the "first time" set up when it powered itself off. So I never completed the process. I powered it back on, and it was locked up. I held down the power and got it to power back on. The unit would not respond to touches of the screen, but started to cycle through icons on its own. For example it kept moving onto the media icon and try to load a movie from the SD card. I managed to get into the setting screen and tried to calibrate the touch screen, the cross hairs moved on their own without me touching the screen at all and they were moving so fast, I couldn't have touched them if I tried.
I finally managed to get miopocket installed, and I thought I had the problem solved, but now the unit is acting like it is possessed. It jumps all over the place without any screen touches...It was working fine on the initial Miopocket install but the problem has reappeared.
Does anyone have any advice on how to "reset" the unit. I even wiped the internal flash and put on software that my friend has on his that is working fine. Still the same issue.
Any advice is appreciated.
|15 L A T E S T R E P L I E S (Newest First)
||Posted - 04 févr. 2010 : 17:15:40
I very much disagree with that. There are a lot of people having the same problems on brand name devices.
Sorry for the delayed answer, you really need to specify the device brand/model.
How do you know you actually overwritten the bootloader?
Once we have these info, maybe me or someone will help.
||Posted - 16 août 2009 : 14:31:33
china nonames are crap. they don't even worth the cheap money they cost.
||Posted - 15 août 2009 : 16:43:02
i'm new here and saw this topic.
I mad a terrible mistake to overwrite my bootloader (stupid stupid stupid).
Do you now a way to correct it??
Now my system stoped by first screen and stays there.
is it possible to load a newbootloader or something??
||Posted - 01 juin 2009 : 22:12:15
OK, just to end this story:
I managed to "un-brick" my GPS, all it needed was the correct OS image file, I managed to find it on the internet, put a file called OS17S.img on the SDcrad and the OS was updated, everything working again.
So usually, if your device is not phisically damaged, you can make it work again by this procedure, but you need the correct files for your specific unit, model.
I suggest everybody takes the following precautions before experimenting with software on your device:
-put your device in ActiveSync mode and leave it that way.
-make a backup from activesync menu
-you can also make a registry backup from activesync and/or another reg editing program, but usually the backup from activesync from previous step should be enough
-make a note of your manufacturer, model, SO version, ROM version, software version, ROM size, RAM size. Dont miss any of this!
-if you find files for upgrading your software but you are not sure is the right one for you, use ONLY the OS image (this is the biggest in size), not the bootloader. If you overwrite the bootloader, your device is pretty much dead, if you just overwrite the OS, but your bootloader is ok, you can try again with another image.
Hope this helps!
||Posted - 27 mai 2009 : 23:25:58
Even I reply so late, I think it is still of interest for many people, I keep hearing people with PNA's, mainly chinese, having problems.
1.I did all the steps in the readme file, then I tried editing the init.mscr just to make sure it's launching touchscreenfix.exe, cause at some point nothing happened.
2.The device DID suport autorunning, I think all devices usually do, but right now, it doesn;t go past the first image, the logo. I think the SDcard is no longer accesed. I studied about how to grab a ROM image from a device, but didn't have much succes. I need a ROM image and then try to burn it the hard way, using a ROM burning external device.
3.I want to clarify one aspect, just to be safe in the future, what file should I delete so that I cant accidentaly install the transcriber driver?
4.Do you have any ideea why some devices need to be shut down and back on twice and then reset in order to maintain some settings (registry modifications)? I dont understand how does miopocket however manages to modify the registry and the modifications remain there even on those device...
I am talking of course about chinese PNA's.
I hope i was abla to make myself understood, sorry if i didn;t.
||Posted - 10 avr. 2009 : 20:32:54
1. When you say "I edited the init.mscr from MioPocket to run MioAutoRun\Programs\TroNik\TouchScreenFix.exe, and it said now you need a restart, but after restart the touch screen was the same, not working"... do you mean that you edited it to run UninstallKeyboard.mscr driver (since that's what the Readme tells you to try first)?
2. Does your device support autorunning an executable from SD when a card is inserted?
||Posted - 07 avr. 2009 : 12:39:19
Sorry if this is not the right thread, but I am new around here and a little desperate...
I have a “no-name” Chinese 3,5” PNA, that went dead after messing with MioPocket :(
Now it only show a picture with a satellite that is shown in the first 2 seconds after power on normally. There is no more acces to SD card.
I installed MioPocket rel 43, it worked, but then I tried to install the Transcriber driver, at that moment the touch screen stop working.
I tried to fllow the instruction at 5.12 in the readme, and did the following:
-no chance accesing the device by activeSync, that was out of the question
-I edited the init.mscr from MioPocket to run MioAutoRun\Programs\TroNik\TouchScreenFix.exe, and it said now you need a restart, but after restart the touch screen was the same, not working
-I edited the init.mscr again adding 2 lines, one was run MobileNavigator, and last was “restart”. After that the device restarted and went DEAD, displaying just the opening graphic with the satellite.
Now, for solutions to fix this:
-I got out the battery, but no luck
What else could I do? To re-write the ROM, I need someone that coud do this, but how? You need to physically extract the ROM from the electronic board of the device? Can you re-flash the ROM without physically extracting it and putting it in a ROM reflash device?
Any help would be VERY MUCH appreciated.
I think I would try a ROM image from Starway Ovi110, it looks the same.
Also, on GAPI setup, I selected randomly until a driver worked, and that was GPSmile 53, CE 4.2, 320x240
If someone could help me with the above ROMs, please send them to me.
Data about the device:
ROM Version: V26.Y17S.T4.1.10
Processor: ARM920T 400Mhz
RAM Size: 64MB
Software Version: 1.14
The original registry entries:
||Posted - 06 avr. 2009 : 22:31:22
I used the recovery disc, and let it run, no possession.
Installed Miopocket R43 and after one day of testing, success !!!! No phantom screen touches, hopefully this completes the exorcism.
Thank you very much (you too Miolover) for taking the time to help me resolve my problem. It would seem that the touch driver script was the culprit after all. I was using R39 before and having the problem, since following your advice and using R43 all is good.
||Posted - 31 mars 2009 : 23:01:46
Remember to test whether the problems exist without any unlocks (especially MioPocket) applied. If they do exist, then just get the device replaced.
Well, I've had those study notes on my website for many years now (I've been an MCSE since 2004). The exams aren't that hard, no, as long as you have interest in the subject matter and work in the IT field (with Windows networks). No, you take them at a brick-and-mortar testing center and the fee is $125 per exam.
||Posted - 31 mars 2009 : 05:25:10
Thank you for taking the time to help the less technically inclined like myself. I am away and can not test the c520 till I get back. I think that it had the "possession" problem right out of the box. But when I restored it with the recovery disc it was ok....so I guess I will try recovering it, using r43 and let you know. I may have to RMA it to Mio as no stock is available from where I bought it. I will let you know as soon as I get back.
Thanks again for your efforts.
||Posted - 31 mars 2009 : 03:46:08
hey osprey thanks for telling him what to do. i have no patience on that but you do. spider, i highly suggest u install the earlier versions like osprey said. i am quite sure u wont have a "possessed" device. it is the cgrtouch.dll that's the culprit i am positive. also osprey i stopped with R41.. your last 2 releases have very minor upgrades. anyway i saw your website. it looks like you are studying for an MCSE certs. is it hard? do you take it online? how much is the fee?
||Posted - 30 mars 2009 : 23:01:25
You haven't made it clear whether the "possession" happens when the device is not unlocked. Hold down the hardware power button for 6+ seconds to turn the device off, then do so again to turn it back on. Use the device for a little bit (without installing MioPocket or any other hacks) and see if the problems happen. If they do, you should probably return the c520 to where you bought it and get a replacement, or send it into Mio, as that should not be happening and you don't want to be stuck with a bad device.
If you experience absolutely no problems when the device is unlocked, download MioPocket R43 (which I should have posted by the time that you read this), copy it over and install it. If the problems appear again, then, naturally, MioPocket would appear to be the problem. You could try removing registry files from MioAutoRun\Registry and re-installing to see if any of them are causing the problem or you can just try installing older releases (links are on the first post of the MioPocket thread).
||Posted - 30 mars 2009 : 03:16:57
Re-installed Miopocket....renamed "InstallTranscriberDriver.mscr", unfortunatley the possession continues....very creepy...
Anyone with any other thoughts?
||Posted - 29 mars 2009 : 04:57:53
Thanks, I will try that...and let you know how I make out.
||Posted - 29 mars 2009 : 00:22:57
I've only ever heard of the touchscreen driver locking up the touchscreen, not "possessing" the device. You can try the same fix, though. As miolover suggested, rename MioAutoRun\Scripts\InstallTranscriberDriver.mscr to something else so that installation can't find the file, then re-install MioPocket. If you still have the problem, then Transcriber is not the problem.
|This page was generated in 0,31 seconds.