Search results

  1. I

    Post [2014.05.01][ROOT] Mobile ODIN v4.20

    support for P7501/7511 ? Hi ! Can we have support for the Galaxy Tab 10.1N (GT-P7501/7511)? Beside some minor optical changes (thanks to apple) it is the same as the P7500/7510. But Mobile ODIN does not support/recognize this device model. iwfratz
  2. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    633 instead of 528 MHz, thats a difference of 105 MHz and a speedup of 20%. i) Try another ROM and/or radio. There are reports, that radio-ROM combination have an impact. ii) Try another xperia device. Because of fabrication tolerances another cpu may go higher in frequency. :) iii) Get...
  3. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    new version released I released version 1.09: - added support for more OEMXIPs (1xRhodium, 1xTopaz, 1xRaphael) - added support for more radios (1.11.30F, 3.54.25.25, 1.20.OliNex) - PINVOKE error should be solved (moved to another compiler) - test (!) support for Jade, Panther, Mega, Rose and...
  4. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    I am working on the next release. There will be support for more OEMXIPs and RADIOs, and test support for Jade, Panther, Mega and Rose. Also the PINVOKE error should be resolved. I am almost finished, but found a problem. So it will take some more days. Please be patient.
  5. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    would you be so kind to tell me what's not working ? Therefore read post #1. Thank you.
  6. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    @endeavour3d and patrick007: Did you tried to run WiMoSpeed after a hardreset ? Did you installed software, which change the ROM ? Are there any other problems with your device pointing to a (partial) bad flashed rom ?
  7. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    thank you for the donation, but please tell me: what are you going to tell me in posts 668, 669 ?? Does WiMoSpeed works with these devices/roms ? Is there any problem ? Which ? OEMXIP/RADIO-ROM error ?
  8. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    check the registry values of HKLM\Software\WiMoSpeed\oemxip_id HKLM\Software\WiMoSpeed\radio_id How do you know that the phone is still running at 576 Mhz ? Any changes if you (soft) reset the phone ?
  9. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    do you remember the ROM identification of your ROM showed in the GUI (Rhodxxx) ? do you have a download link (without login or serial number) of this ROM ? did you edit registry settings of WiMoSpeed ?
  10. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    In our ROMs are several CPU speeds defined: 19.2, 122.88, 128, 176, 245.76, 256, 352, 384 and 528 MHz. And believe me, they are used. In which way depends on the OEM of the ROM and the power mode device driver are running at. But I have to contradict cfb: WiMoSpeed changes the settings WM uses...
  11. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    It is much easier, because such a program is already on your devices: Windows Mobile. WM has a power management, which controls CPU speed. At deep sleep it even stops the cpu.
  12. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    So your device is running at 710,4 Mhz. Right, that is a fixed text.
  13. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    yes, help yourself: identify your device read post #1
  14. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    read post #1. (your hardware isn't supported yet) I take a short look into these ROMs: it appears to be possible to support these devices. what ROM are you using ? Give me a downloadlink and you have to test the next release ;)
  15. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    your english isn't the problem, but the description of your problem / error. what is the ROM identification shown in the WiMoSpeed-GUI (OS and radio)? you select a value for new CPU-speed ? which value ? after pushing "set CPU speed to xxx" nothing happens ? no change in the cpu speed at the...
  16. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    Thanks, support is added to the next release.
  17. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    I haven't a serial number to download this rom.
  18. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    new version released I released version 1.08: - added support for more OEMXIPs (1 x Diamond, 1 x Blackstone) - added support for more RADIOs (0.93.25.NS16, 1.02.25.32, 1.10.25.18, 1.11.25.71, 1.11.25.76) but no solution for the pinvoke-problem.
  19. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    Sorry, but i cannot find a rom for the diamond2 there, only for HD2.
  20. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    I need a link to the radio version 1.06.25.29. anyone ??
  21. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    Thats all fine, thanks for the information. BUT what in detail does not function ? Any error message ?
  22. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    No, the function for the rom identification is IN the dll. @jb789: There is something we can try, check your PM.
  23. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    new version released set os-versions in CAB-Information-File, maybe it solves installation problems added support for more OEMXIPs (1 x Topaz, 1 x Blackstone) added support for more RADIOs (1.02.25.28)
  24. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    Hi all, sorry for not answering in the last weeks but I was very busy with other things. I have a shortcut in my startup folder too, but I never had such a problem. I think that the .net errors at startup are caused by starting WiMoSpeed while .net is not initialized completely. Try to delay...
  25. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    Thats not the whole truth: In version 1.06 there is nothing to do. WiMoSpeed will check the detected ROMs for a change and run the identification routine if necessary. Version 1.05 will identify roms only once and store the result in the registry. So if you change the radio rom only, or restore...
  26. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    Hi Mike, I think its number 3. Internal memory must be unlocked before you can write to. It is nearby that with a different memory layout this locking is different too. Sorry iwfratz
  27. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    @snakem & potatow: What ROMs are you using ? Did you tried another one ? HTC Touch Pro ?
  28. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    new version released WiMoSpeed now checks the ROM-identification on startup for changes (e.g. you flashed a new radio-rom) support for Pure (1 OEMXIP) added support for more OEMXIPs (2 x Rhodium, 1 x Diamond, 1 x Kovsky) added support for more RADIOs (1.13.25.55)
  29. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    Energy ROMs come without radio-ROM. So what radio are you using and where can I download ?
  30. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    Yes, you are right. At the moment once installed WiMoSpeed would not detect any change of the ROMs. In next version WiMoSpeed will test the ROMs at application start for a ROM-change.
  31. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    Yep, thats right. There is an OEMXIP twice in my table: Rhod008 and Blac014. Will correct that in next version (coming soon). Sorry for the problems and thanks for the help.
  32. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    @htchd1: The Barebone 2.6 rom is definitely Blac014. If WiMoSpeed detect this rom on your device as Rhod008 so please reinstall the cab and run WiMoSpeed-GUI (that will start the rom-identification again). What's the result: Blac014 or Rhod008 ????
  33. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    yes, wipe WM from your device. ;) While on battery WM power management puts the device into sleep and halts the cpu. But soft- and hardware IRQs can awake the device, do something and put the device into sleep again. Thats is a normal behaviour, overclocked, underclocked or default speed doesn't...
  34. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    did you try re-installing .net cf 3.5? As I remember there were a post reporting this as solution.
  35. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    I need only the Radio-ROM, but the link gives me a "404 - page not found"
  36. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    Sorry, the file on RapidShare was deleted by the owner. Do you have another download-link ?
  37. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    WiMoSpeed does not need to identify the whole ROM or the chef cooked this. It needs only information about the native kernel of the OEMXIP. This native kernel could be almost arbitrarly included into cooked ROMs. So I gave every new native kernel an identification: RHOD means that it is a kernel...
  38. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    Rhod008 ?? That's a shipped ROM for the rhodium ?! What custom ROM are you using, please give me a download link. Then I will have a look into it.
  39. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    Whats about the reported errors ? Any news / solution (reinstalling .NET CF 3.5) ?
  40. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    new version released WiMoSpeed V1.05 support for Quartz (3 OEMXIP) added support for more OEMXIPs (5 x Raphael, 5 x Diamond, 1 x Kovsky) added support for more RADIOs (1.96.10.WU, 1.14.25.35, 1.02.35.31, 1.08.25.08, 1.15.25.55, 1.02.25.31, 1.12.25.19) Hope, that I got all ROM-links posted...
  41. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    Thats already realized in OCT. If you change the multiplier the frequency crystal must tune to the new frequency. So if you jump from low to high there is a noticeable lag. With OCT V1.5 I realized another approach without lag, but with limited steps: divide maximum frequency by 2, 3, 4 ... For...
  42. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    Thanks. Indeed, there are tons of unidentified OEMXIPs and RADIOs. More than I expected. Working on it and making progress.
  43. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    It seems that you all use OEMXIPs not in the repository of shipped-roms.com. I will work on all reported problems, download the roms and add support. I am sorry, but please give me some time. Yes, I am here, but have not a lot of time at the moment.
  44. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    Reading registry values from Msm7kCpuSpeed ??? Do not mix different OC-tools !! Would you please give me your ROM-identifications (shown in the GUI). Thanks @tsalta: Guess it is Blac016
  45. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    Again: to download ROMs from htc-website I need a serial number, which I do not have.
  46. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    To download ROMs from htc-website I need a serial number, which I do not have.
  47. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    Are you sure ? Radio 1.14.25.05 is supported. In your signature you name radio 1.13.25.55, that is indeed not supported yet. Do you have a download-link ?
  48. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    new version released WiMoSpeed V1.04 - blackstone problem should be solved now (tested by tsalta with Blac016 / 1.17.25.09) - added support for more ROMs - support for Raphael / Fuze, Diamond, Kovsky / Xperia - GUI shows ROM identification
  49. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    TP2 (Rhodium)
  50. I

    Post [APP] WiMoSpeed: [2011-09-20] V1.09

    My device is set to 710,4 MHz all the time. No problem so far. But windows mobile have a power management while on battery, which will slow down and stop your CPU when screen off or sleeping. So your CPU is neither running nor at 710 Mhz all the time.