Related
I have it!!!!! Send me a email and i will send you the file with all the instructions to repair your dead gsm "part" of the xda. it worked with my qtek 1010 and i think that it works with any other. Ricardo Gomes
[email protected]
Could you please post the solution here ?
i´m doing a zip file with all the instrutions and i will put it to download soon. please be patient
the file is ready
you can download the solution for the radio dead problem in http://qtek.no.sapo.pt/repair.zip
Ricardo Gomes
[email protected]
Thanks.
Anyone tried that?
Since my phone is working perfect now, it is nonsense to try that
It didn't work for me.
GREAT!!!!
it worked for me in my qtek 1010.
Mirror on xda-developers
I downloaded Ricardo's repair.zip file and took the liberty of mirroring it on xda-developers, since my download went at a whopping 200 bytes per second.
We've seen this recipe before, and it does appear to fix at least some of the problems caused by RSU upgrades not finishing.
http://xda-developers.com/repair.zip
faild
hi guys
still stop at 1% and showed massage
((flash failed! Press OK restart your device))
any help
hi guys!
I have this problem also.
Still stop at 1% and showed massage
((flash failed! Press OK restart your device))
Just try to do following: start 3.23 ROM update to extract RSUpgrade.sa.CAB and place it to SD card instead of file found in repair.zip.
The situation you describe looks like your device died while flashing new 3.23 version. So you may try to continue process with 3.23 version instead of old one. This is because 3.23 don't allow to "downgrade".
Hi AE !
Where can I find 3.23 ROM file ?
Thx for your helps.
If your device died while trying to upgrade to 3.23 radio, the CAB-file should be found in "C:\Program Files\Radio Stack Upgrade Utility".
My device died while trying to upgrade to radio 3.19 but I trying to copy to SD all Radio upgrade, but don't work. Still stop on 1% and error message is "Flash failed. Press OK to restart device".
Other tips ?
Radi ROM
i have the same pb the alnasser and sebi; i have tried everything; what we need is a new rom version for the radio and not an upgrade; also while using boot loader and if i try to copy the GSM rom from a working phone i got a message saying: connect to RS232 and run PC monitor; i have USB and i do not know what is PC monitor...any ideas???
It worked for me also, but with slight changes
Hi,
The soloution above worked for me after a little trial and error.
I was trying to upgrade to new UK Radio Stack but flash failed in the middle of upgrade (probable because the keyboard popped up onto the screen for no apparant reason, then locked up).
However, after much wailing and gnashing of teeth, I found your website!!
I installed the Files onto an SD card as described above, and although the XDA was going painfully slowly (about 3 mins to warm reset). managed to get to the today screen. I ended up pusing the "record button" repeatedly to try and get some response out of the machine, finally it auto ran the program on the SD card, only to be told that flash failed
Undeterred I repeated the exerscise with the other RSUpgrade.sa.cab
file, this gave the same result!!
However I soon realised that this cab file is kept within the .exe file of the original upgrade I tried to do, so... Using winzip I extracted the relevent RSUpgrade file for my XDA and put that file on the SD card instead.
It Worked!!!
Consequently I conclude that if the file fails or stops at 1% then it must be because it is NOT the correct file for your XDA, you need to use the correct upgrade cab file for you particular XDA.
Hope it helps someone else.
Essentially the watchword is "perseverence".
it starts but stop on 85%??!!
hi i have a dead xda and i'm trying to fix it but it stops on 85% sometimes on 83%,i'm using the copy of cab file to sd card and runnig it from xda anyone can tel me how to get over this?
now it stops on 1%
i have removed it from charger and put the file on the sd card,the progress bar went to 99% then flash failed,now it gives me that message on 1%,how to fix it??!!
Re: it starts but stop on 85%??!!
Anonymous said:
hi i have a dead xda and i'm trying to fix it but it stops on 85% sometimes on 83%,i'm using the copy of cab file to sd card and runnig it from xda anyone can tel me how to get over this?
Click to expand...
Click to collapse
Hi,
seems to be the same case as I had: I found version, which did not freeze in 1%, but in 85% all stopped.
I unfortunatelly don't exactly remember complete list of my steps, but THIS MAY BE IMPORTANT:
After I made cold restart, I saw radio upgrade progress bar ( If you can't see this, try to follow instruction about repair.zip solution, mentioned hereinbefore ). Radio upgrade progress window only flashed for a second or two, then disappeared and WIN CE ( trying to boot up ) painted its splash screen. After that WinCE froze with this screen.
BUT:
If you have a luck, radio upgrade may continue on background. After 10-15 mins upgrade was done, and after restart ... I saw normal radio version in bootloader, and it worked well !!!
Note 1:
I killed phone with latest radio upgrade ( maybe lack of space, maybe radio switched on ), so there was no way to use lower versions ( it leads to "1% problem" with downgrade )
Note 2:
When my steps was still unsuccessfull, I continued [up|down]grade WIN CE and Bootloader. Maybe it was solution, maybe not, I dont know. I did it because I thought it would solve some problems with space for radio installation. My second reason was, that it should stop neverending ( 1% freezing) radio upgrade window after each boot.
Note 3:
During these installation steps it seems to me that battery si getting weaker, and does not recharge. So I tried to revive WIN CE first to be able to recharge.
Some steps may be unimportant, based on my feeling how it may work.
Anyway,
MY MDA RESURRECTION SUCCEDED,
so I hope it helps.
Regards, Lu
After watching for months the issues that many have suffered over this problem, I finally found a solution that will fix all the woes.
A few months ago I was one of the many here that upgraded to 1.11 ROM, had the problem. It drove me crazy to the point that I went back to the 1.06 ROM that was rock solid. Well the other day I did a hard reset to have a clean slate. While looking at the Extended ROM I saw the file DefaultV_1.12 in the EXT Rom (Compared 1.11 ROM on FTP to my device). This was the same file that a XDA developer member had modified to somewhat solve the GPRS problem a few months ago.
At this point I had a hypothesis, so I pulled the same file from the older 1.06 ROM which was rock solid and did not have the “Cannot Connect” problem. In this EXT ROM it is named Default_Version_WWE_106150.sa.CAB.
Installed it first on my Blue Angel as a guinea pig, then for the next three hours I would sit there and disconnect and reconnect. I did it manually by holding the red button to disconnect, then I would reconnect to another webpage, then would have a call come in while in the middle of the GPRS session which would suspend it. After done with the phone call I would reconnect manually by clicking connect as well as by just hitting a link on the webpage.
The Results: No “Cannot Connect” problem.
So off I went to my Magician:
Upgraded to 1.11(I have 850 JAM)
Installed Default_Version_WWE_106150.sa.CAB
Put the phone through its paces, I have been disconnecting and reconnecting without a single problem. I receive phone calls that suspend the GPRS session and I am able to reconnect without a problem. Activesync is able to make OTA connections without a hitch.
During my trials I used the same programs:
Which included:
Photo Contacts(newest version)
Activesync
WEBIS Mail 2
xVbar
PocketZenPhone
Regking 2003
As the only variable throughout the trials was Default_Version_WWE_106150.sa.CAB
This is the solution folks.
At least until someone says it does not work.
Installation Steps:
1. Download CAB that I have attached.
2. Copy over to device
3. Install
4. Soft Reset.
1st of all let me say this is a great site for the HTC devices, I found it years ago when i had the first XDA (Wallaby i think) and now i own a O2 Mini.
I have just installed your patch and i'll let you know how it goes.
I wonder if this patch does the same as the "downgrading" of the caller id as detailed in this thread: http://forum.xda-developers.com/viewtopic.php?t=20428
The downgrade has been succesful for blue angel users too.
randomshots said:
Installation Steps:
1. Download CAB that I have attached.
2. Copy over to device
3. Install
4. Soft Reset.
Click to expand...
Click to collapse
Many thanks for posting this information.
For a relative newbie like me who has never manually fiddled with ROM files, can you please explain what I actually have to do to "install" the CAB file, i.e. in which directory on the device do I put it, and how do I run it?
- Peter
Once copied over to the device just place it where you can find it using the file explorer. Once located using the file explore simply click on it and it will install on its own. Do a soft reset and enjoy.
Crisscross: The Photo Contact solution that people have found only alleviates the problem a little, not entirely.
In my trials it has solved my problems completly. I wish for other members who try it out to report back as well to see whether all my trials were just a fluke, or our solution.
don't work for me
don't work for me. same problem as before, can't connect due unknown reason.
thanks anyway.
Orcas what is your ROM?
randomshots said:
Crisscross: The Photo Contact solution that people have found only alleviates the problem a little, not entirely.
In my trials it has solved my problems completly. I wish for other members who try it out to report back as well to see whether all my trials were just a fluke, or our solution.
Click to expand...
Click to collapse
The downgrade of caller-id to an earlier version has also solved the problem totally for me and several other people, both blue-angel and magician users. Thats why I was curious just what your patch did. Seems that it is something similar, you are maybe downgrading more of the rom?
Did you try downgrading of the caller-id first? Not just photo contacts but downgrade to the specified earlier build of caller-id?
randomshots said:
Once copied over to the device just place it where you can find it using the file explorer. Once located using the file explore simply click on it and it will install on its own. Do a soft reset and enjoy.
Click to expand...
Click to collapse
Hi there,
Just thought I'd report that I've just installed it. My ExtROM now reports as 1.06.150 WWE.
And... so far, so good!!! I've connected/disconnected to GPRS multiple times, interrupted GPRS with a phone call and then reconnected, have sent files to my device via BT while GPRS is on, and still no problem. It's looking very good!!!
And I'd swear it connects faster than it did previously.
Anyway, I'll keep hammering at it over the weekend and report back on Monday.
Thanks again randomshots!
Well, I'm back already, because I still have the problem. DARN IT!!!!!! :x
The thing that made it happen was that I made a phone call while GPRS was on. When I ended the call and tried to reconnect to GPRS, I got the blasted error. So it seems that receiving a phone call does not cause the error to happen, but making a call does. At least for me.
Oh well, it was worth a try. Back to the drawing board.
Same problem in Hong Kong
I upgraded to ROM v1.11 a few days ago and since then I have the GPRS connection error after 1 or 2 connections. Soft reset will solve the problem. This problem was not encountered at all before the ROM upgrade. It must be the new ROM that mess things up!
As this "default cab" from an old rom seems to solve the problem and also an older version of caller-id solves it there is probably something wrong in the communication between caller-id and some of the customisations from this cab on newer roms. Btw the problem is also in 1.12 roms.
Nice too see that we have two possible solutions here, I will stick to the downgrade of caller-id as it has solved the problem totally for me but it would be interesting to know what the real cause is...
Hi again. Just to answer the previous question to my post: my rom version is 1.12.00 WWE, radio 1.12.00, extrom now says 1.06.150. i think the only thing this cab changes is this rom number, nothing else
orcas
orcas,
I believe you are absolutely right. When the extended rom has finished installing the programs, it runs this .cab file to 'brand' the Magician with the build number. Nothing more or nothing less. But faith can move mountains, as we all know...
I guess some of you know that there is another (older) thread about GPRS problems. If you do not, there is a link below.
Anyway, I finally tried the most recent suggested fix in that thread (downgrading the device's CallerID program to an earlier version) and like a number of others I can happily report that so far, it has fixed my GPRS cannot connect problem. Looking good.
Here is the thread:
http://forum.xda-developers.com/viewtopic.php?t=20428
- Peter
Just thought I'd share that the second fix I tried (downgrading CallerID) has continued to work for me. I have no more problems with GPRS. All is well with my Magician. At last.
Hi,
I have been donated an Orange SPV m5000 to help with my disseration,
unfortunatly the rom as been tampered with or removed , well im lead to
believe. Due to this the phone no longer turns on, the only thing the handset will do is get to the bootloader screen.. after resetting the factory settings the handset still does not turn on. i think the handset therefore has no ROM files on it as I have tried to update using downloaded roms such as
Orange_SPV_M5000_v1.13.49_WWE
JASJAR_WWE_11353_137_10301
both say that they cannot communicate properly with the device...
using MaUpgradeUt_noID and following instruction posted the handset starts to update but then says that the updater is not compatable with the handset... any suggestions on how to load a new rom onto the handset would be greatly apprecieted or infact how to to fix this problem with limited technological knowlegde
thanks
cjh28
I'LL GIVE YOU 50 QUID FOR IT!!!!!!!!!!!!!
****, not even I'd be that cruel.
First off I'm 75% sure your device is fine.
ROM chips are nigh on impossible to remove without breaking the device and doubly nigh-on impossible to put back in! No one in their right mind would even concider doing such a rash thing, espcially with something that costs this much!
Now I think the problem is the same as the one I had - these ROM upgrades can contain many separate updates which are then kind of glued together - the problem is (and the problem you may have) is that they don't all match what is already in your PDA.
You therefore have to do one of 2 things:
1) Find an upgrade that DOES match - but then you'd have to know what's already in there & then find a match - unlikely.
2) Make them match with a bit of jiggery pokery. read THIS:
http://forum.xda-developers.com/viewtopic.php?t=40986
Seriously dude, good luck!
Andy
Still Dead well almost
Thanks for pointing me in the right direction, Ive been thru the directions on the link provided and still having no luck, am still getting a communications error - 101 from the update ... am thinkin ive got the incorrect orginal roms ... does any1 know where i can find the orginal roms for a UK Orange SPV m5000 ( am currently using a rom that gives me operator name as Qtek and WWE - the name of the file is on my orginal post)
any further help/guidance would be greatly appreciated....
Many thanks
cjh28
Flash It Again
1. Download This:
http://www.business.orange.co.uk/se...c=PaDPage&cid=1044130840493&mid=1044129390154
2. Make sure u are not using a USB Hub
3. Make sure u are using the proper USB Lead!!!
4. Install Active Sync 4.1 On your Computer (it needs the USB Driver Within this Program to communicate with your UNI.
5. If you have followed all the above correctly your SPV will flash
especially if it is going into bootloader mode.
If you get country error or comm error, hit update AGAIN, DO NOT Disconnect.
IF the upgrade wont go 100% thru, try upgrading the radio only by deleting all the .nbf files except the radio_.nbf then run MAUpgradeUt_NOID.exe
Up and Running finally .... thanks
Just to say that my SPV M5000 is now up and running.. thanks to Andy and comp.solutions for helping me out, just followed ur instructions took a few attempts but its all gd now
Many thanks
cjh28
Damn! Bang goes my 300 quid profit!
No, seriously dude, you don't know how much 'inner glow' that gives me to know that we have helped you recover what may have seemed a lost cause.
Well done! :wink:
Now you can spend the next month trying to figure out how to get things to work 'properly' on the bloody thing..... :lol: (i.e. guess what I've been trying to figure out for the last month: Bluetooth, WiFi, ActiveShyte, installing programs, discovering what a 'uni' is, what 'BT' is blah blah blah.... :roll: )
Andy
Fixed M5000
Glad to Help, Enjoy :wink:
I have an unbranded Chinese P800 from eBay and would like to upgrade it to WM 6.0. What I have onboard :
1. WM 5.0 OS 5.1.525 (Build 15364.3.4.4)
2. Processor ARM926T OMAP730
However, one perculiar thing is that I can't find any Device Info on IPL, SPL, Radio ROM etc. I've tried using WST 4.2.2 but to no avail. I'm using my Lenovo S10 Netbook running XP and ASync 4.5. What I've managed to do are :
1. Run USPL, it goes from 0.. to 60.. and hangs, I reset my P800, USPL resumes to 70..100 and the RUU program starts,
2. the screen on my P800 turns dark with the Linux Penguin and some message of mapping, preloader etc comes on temporarily before Windows comes on again,
3. RUU runs, upgrading to image 9.99 (original image is blank-no info), when UPDATE ROM IMAGE ON YOUR PDA PHONE comes on it never gets to more than 0% (no blue progress bar), my P800 screen goes dark, loses connection and I get ERROR(260).
I have done this several times and there is no way I can verify if the CID is unlocked as I can't get the SPL info anywhere. So I will appreciate any help I can get. Thanks in advance.
Hi Salimbs,
Have a look at these two posts:
* Regarding the CID unlock for Artemis
http://forum.xda-developers.com/showthread.php?t=334667
* Regarding the error 260
http://forum.xda-developers.com/showthread.php?t=293085&highlight=error+260
Hope this will solve your problem
mouse.co.nr said:
Hi Salimbs,
Have a look at these two posts:
* Regarding the CID unlock for Artemis
http://forum.xda-developers.com/showthread.php?t=334667
* Regarding the error 260
http://forum.xda-developers.com/showthread.php?t=293085&highlight=error+260
Hope this will solve your problem
Click to expand...
Click to collapse
Hi mouse.co.nr,
Many thanks for your reply and pointing to the right direction. I'll get to it asap and post the outcome (success I hope!)
Hi Salimbs,
just another note,
in the past I found myself in big trouble (not with Himalaya as it was SD flashed) but with Charmer and Magician ROM updates, also with ROMs that I have already used in the past and classified as stable,
Roms used to get blocked during upgrade leaving me in Boot mode if I don't remember bad..
I have noticed that this error was common when Ms. Office applications like for sxample Word or Excel was turned on!
it makes like a kind of disturb to the rom!
once closed (all office and not necessary applications) roms updates smooth and bug free!
Don't remember if it was an Err 260 or not, I just remember that update blocked at a certain point...
try to do your upgrades with office turned off!
wish it will help to solve your problem
X-Mouse
mouse.co.nr said:
Hi Salimbs,
just another note,
in the past I found myself in big trouble (not with Himalaya as it was SD flashed) but with Charmer and Magician ROM updates, also with ROMs that I have already used in the past and classified as stable,
Roms used to get blocked during upgrade leaving me in Boot mode if I don't remember bad..
I have noticed that this error was common when Ms. Office applications like for sxample Word or Excel was turned on!
it makes like a kind of disturb to the rom!
once closed (all office and not necessary applications) roms updates smooth and bug free!
Don't remember if it was an Err 260 or not, I just remember that update blocked at a certain point...
try to do your upgrades with office turned off!
wish it will help to solve your problem
X-Mouse
Click to expand...
Click to collapse
Hi mouse.co.nr,
Well noted and I'll keep this in mind. From your experience have you ever tried the SDHC.cab so that your phone can read the micro SDHC? I ran it in my phone and now my STORAGE CARD is gone! Anyway, thanks again. Cheers!
Not SDHC my friend but Artemis SDHC,
I don't know what is exactly the difference, maybe one is for big SD and the other is for MicroSD, anyway I've tried the one for artemis and now I'm working with a 8 GB micro sd, and it can go till 16 GB.
I've tried that with other artemis ROM versions and works very good...
For your problem have a look at this post:
http://forum.xda-developers.com/showthread.php?t=345038;
and download the programs indicated below...
What I advice you to do is the following:
1) remove your SDHC card (it have a sort of bad luck with any upgrade that needs a reboot)
2) copy SDHC_Artemis_back2original.cab to your documents folder (PPC documents obviously) then run it, soft reset.
3) then copy the correct SD HC for artemis "SDHC-Artemis.cab ", in the same way of the above and run it.
this shuld work "I wish for you"
let me know..
how about the ROM update? did you succeed at the end?
have you also updated also GSM radio ROM? generally original roms come with a 2.11.... version, old and not always good in reception!
I advice to change it in 03.18.90 shall work well also with your provider, for GSM signal WIFI, GPRS and GPS..
have a look at this post for more details: http://forum.xda-developers.com/showthread.php?t=397939
X-Mouse
mouse.co.nr said:
Not SDHC my friend but Artemis SDHC,
I don't know what is exactly the difference, maybe one is for big SD and the other is for MicroSD, anyway I've tried the one for artemis and now I'm working with a 8 GB micro sd, and it can go till 16 GB.
I've tried that with other artemis ROM versions and works very good...
For your problem have a look at this post:
http://forum.xda-developers.com/showthread.php?t=345038;
and download the programs indicated below...
What I advice you to do is the following:
1) remove your SDHC card (it have a sort of bad luck with any upgrade that needs a reboot)
2) copy SDHC_Artemis_back2original.cab to your documents folder (PPC documents obviously) then run it, soft reset.
3) then copy the correct SD HC for artemis "SDHC-Artemis.cab ", in the same way of the above and run it.
this shuld work "I wish for you"
let me know..
how about the ROM update? did you succeed at the end?
have you also updated also GSM radio ROM? generally original roms come with a 2.11.... version, old and not always good in reception!
I advice to change it in 03.18.90 shall work well also with your provider, for GSM signal WIFI, GPRS and GPS..
have a look at this post for more details: http://forum.xda-developers.com/showthread.php?t=397939
X-Mouse
Click to expand...
Click to collapse
Hi Mouse,
Thanks to you my STORAGE CARD problem is solved! However with regards to my ROM update I'm still a little confused.I've managed to patch the artemis_jumpSPL_pof_v1.nb using Kermit the Frog(jumpSPL.exe). After that I run the RUU again but I still get the same result-0%Can you tell me how or show me the relevant threads?
Hello Salimbs,
Kermit sounds funny but it's the first time I don't know how does it work!!
try the ufficial SPL unlocker for artemis, nothing more,
download from here:
http://forum.xda-developers.com/showthread.php?t=311403
* Connect your PPC through Active Sync (connection shall be established),
* Run start_uspl.exe from the Artemis_USPL package in the link above,
* Run till it reachs 100% and Dos Window turns off alone, and launches RUU upgrade interface..yes, yes, continue, continue.... 100%
* After device shall have SPL 1.11 and so you can load new ROMs
let me know if it will solve the problem..
X-Mouse
mouse.co.nr said:
Hello Salimbs,
Kermit sounds funny but it's the first time I don't know how does it work!!
try the ufficial SPL unlocker for artemis, nothing more,
download from here:
http://forum.xda-developers.com/showthread.php?t=311403
* Connect your PPC through Active Sync (connection shall be established),
* Run start_uspl.exe from the Artemis_USPL package in the link above,
* Run till it reachs 100% and Dos Window turns off alone, and launches RUU upgrade interface..yes, yes, continue, continue.... 100%
* After device shall have SPL 1.11 and so you can load new ROMs
let me know if it will solve the problem..
X-Mouse
Click to expand...
Click to collapse
Hi mouse,
Actually "Kermit the Frog" is the icon for JumpSPL.exe. Anyway, like I've mentioned in my first post everything seems OK except that I can't check for the SPL and when the RUU runs it never gets to more than 0% and then I lose connection and get ERROR 260. I'll be trying again and let you know of the outcome. Once again, thank you, I really appreciate your help!
salimbs.
Hi Salimbs,
sorry for hearing that...
try to enable RAPI before USPL!
http://forum.xda-developers.com/showthread.php?t=320155
Remove SDHC card (and uninstall SDHC software from ppc)
Then USPL
Then Rom Update Utility
mouse.co.nr said:
Hi Salimbs,
sorry for hearing that...
try to enable RAPI before USPL!
http://forum.xda-developers.com/showthread.php?t=320155
Remove SDHC card (and uninstall SDHC software from ppc)
Then USPL
Then Rom Update Utility
Click to expand...
Click to collapse
Hi Mouse,
I'm open to all suggestion. I'll try it again and we'll see. Thanks.
I'm afraid that I've not met with any success after trying all the combination and tricks mentioned in this thread. Every time at the part of the RUU flashing it never goes beyond 0% then I lose connection and get ERROR 260. I would appreciate any help I can get, and thank you in advance.
Hallo,
i have got a p800 from china and have the same problems. I tried all things but the update doesnt work. The connection always interupts with err260.
regards
Hi folks,
at first, sorry for my - maybe - bad english.
I hope to get some question answered and some informations about my Hermes device. Also, hopefully a was right to open a new thread and get some help from you all.
I searched the board for a ROM, cuz my cam doesn't run anymore. The cam used to work good, but now it does not open, I made some hard resets, cuz of the error message (Error on opening the Link or finding(?) the file). The first hard reset solved the problem, but now the cam again doesn't work.
I've tried different things and searched a little bit, got on this page and now i'm thinking about flashing my device to WM6...
Well... my first question is about the Hermes device. I read about several Model-No (not sure if this is the right word) like HERM100 and HERM200... Could anyone tell me the difference between them!?
The 2nd question is about my problem i described some lines above this question. Is this problem known, are there some guides how to fix it?
My 3rd question is about the flashing process. found some details at the wiki and in some other threads.
I downloaded the tool from this thread (Free HTC Hermes SIM & CID Unlocker *New* version v3a) and the german version of WM6 within this thread ([new release] WM6 ROM Kitchen for Hermes [ GER | WWE | JPN | CHT ]).
Also i've created the ROM (from the download of the last thread i mentured), which is very big i think (69.420 kb), but i never flashed a WM device.
what do i have to do with the *.nb file and how do i flash?! The wiki says that there must be an .exe file to install the *.nb file, but within the package of the 2nd site there was just the BuildOS.exe, which is used to build the *.nb file. There is no other .exe file to flash the device via pc + ActiveSync / Windows Mobile Device Center.
Hope, that i get some help from you guys soon.
darius_raven
Moved you over to General since this isn't a rom dev topic.
well... nearly one week is gone, but no one could answer me... thats not very helpful.
At least my problem with the Hermes Cam is solved. Don't know exactly why. did several soft resets and nothing happened, also several hard resets couldn't solve the problem.
When I shut down the device on friday and started it again, cam works fine...