unlocking Jack wm 6.5 - Non-Touchscreen Windows Mobile Other

Ok, I have upgraded my jack to 6.5. I had it all unlocked when I had 6.1. ran clearsecurity.cab it ran without failure, installed soti. then I ran the security configuration, the phone said unsuccessful install (unsigned) you guys know the error. then i got the tool.cab off the i637 hacks thread, it gave me the same error. I then removed SOTI, reset the phone, ran clearsecurity.cab again, now it gives the unsigned error.

I guess I didnt complete uninstall soti, I did it again and was able to install clearsecurity.cab and tool.cab

Related

i think my treo 750 is dead

Hi everyone,
I have a big problem and I need urgent help please. I have ATT 750 unlocked and I'm outside the States now. My Treo was 6.0 then I upgrade it to 6.1 so far so good.
Then I saw a custom rom that I thought it was interesting. the custom rom was for HTC Dimond I think. without paying too much attention. I started the upgrade. It went 70% before the upgrade crashed.
Now my Treo is not responding to anything. I have the original ATT 6.0 SD upgrade and I have the 6.1 lite upgrade. I'm using CheetahUnlocker to flash the SPL (that is working) but when I try to install the 6.0 or 6.1 using Kaiser Custom RUU v1 it crash.
I saw the post above that suggest to place the original 6.0 on a freshly formated SD and install from there. that is not working either. when I try to install the software it goes into these steps before it crashes: btw, I have the tri-color bar and it has the following info:
CHEE100
IPL-0.20
SPL-1.40.01iNex
while update in progress i see the following:
CHEEIMG.nbh
SPLASH1 - OK
BOOTLOADER - OK
GSM - OK
MicroP - OK
EXTROM - Fail
OS -
After the crash I get this msg: "Update Terminate Update Failed"
Any suggestion please? need more info? then let me know
You may have corrupted your DOC, you may need to use mtty to reformat it. Do some searching on how to do it.
Or try to use T750URT.exe to restore it, it comes with the Treo desktop updater.
similar problem
Hey guys,
After I flashed a WM6.5 costum ROM in my treo750 it works fine...until 4 hour after...the display just stay black. It´s on, but black!!
I´ve tryed reset, hard reset and force to reflashed to an original WM5.0 without success.
Does anyone know what is happening with my phone??
Thanks

Error code 80180048 when updating to mango

I have an un-branded Samsung Omnia 7 (Deutsche Telekom I believe). I did the force update for mango and was able to update to 7403 just fine. However, at the last step 2 of 2 of updating to 7720 it gave me the error code 80180048. I do not have a walshed phone because I tried using the walshed fix and the program said my phone wasn't walshed. Any one having this issue or have fix for this? Thanks.
All Languages
I was having a problem with failled Mango update and I discovered I used the Walsh tool wrong. I only selected the language that was "checked" in my keyboard settings and not ALL languages that were available on my phone. Once I selected all languages, the update went flawlessly.
---------- Post added at 08:43 PM ---------- Previous post was at 08:25 PM ----------
Did you also install the Windows Phone Support Tool? It may be needed for the Walsh Tool.
I have samsung focus (from Rogers Canada) and am facing exactly the same problem, I have reset my phone a couple of times but still receiving the same error, am not sure what to do now, can someone suggest following steps? I don't have walshed phone and walsh tool gave me missing clsid exception.
frazrasheed said:
I have samsung focus (from Rogers Canada) and am facing exactly the same problem, I have reset my phone a couple of times but still receiving the same error, am not sure what to do now, can someone suggest following steps? I don't have walshed phone and walsh tool gave me missing clsid exception.
Click to expand...
Click to collapse
Samsung Focus has two hardware revisions.
You will not be able to get passed the last steps to update to Mango if you have rev. 1.4
rev 1.3(Micron): Windows 7.5 update will be available through Zune on 9/27.
rev 1.4(LSI) : Update has not entered the AT&T SPE lab yet; however, Samsung is targeting for 10/17 lab entry and 10/31 TA"
you can check which revision you have by pulling out the battery. there should be a revision number on on a white sticker on the device.
I have checked the focus revision number on my phone and it is 1.3, I found that one may use windows phone support tool to solve the issue, but it always gave me the 'the device not in connect to pc mode' error while I am pretty sure the device is infact that mode, so somehow it doesn't see that. I am still confused what to do now?
frazrasheed said:
I have checked the focus revision number on my phone and it is 1.3, I found that one may use windows phone support tool to solve the issue, but it always gave me the 'the device not in connect to pc mode' error while I am pretty sure the device is infact that mode, so somehow it doesn't see that. I am still confused what to do now?
Click to expand...
Click to collapse
sounds like a USB driver issue.
open Device Manager
open Zune
plug in the phone into the USB
In the device manager you should see Windows Phone USB Device at the very bottom come in.
Double click and double click Windows Phone USB. Got to Driver tab and make sure it reads Deiver Version 4.8.2345.0
if you have something older, uninstall the driver, unplug the phone, then plug it back in and hopefully it will pick up the new one.
I have exactly the same problem as Starsyde.
Forced update managed to get me through to 7403 and then on step 2 of 2 I get error 80180048. Tried at least 6 or 7 times and always get the same result.
My phone is also an Omnia 7 (bought it unlocked but has the Orange UK logo and apps preloaded).
It's not Walshed (I didn't even have an idea what that even meant until a couple hours ago but still tried that tool, just in case - it says "Good news, your phone isn't Walshed!") and the Windows Phone Support Tool says the phone's not in a "Connect to PC state", even though it is.
To sum up: nothing works.
Oh, almost forgot: I then saw the post about the USB drivers, it's version is 4.8.2148.0 but it says it's the last version so it won't update, and when I unsinstalled it, it automatically installed the same version.
mrrtt said:
I have exactly the same problem as Starsyde.
Forced update managed to get me through to 7403 and then on step 2 of 2 I get error 80180048. Tried at least 6 or 7 times and always get the same result.
My phone is also an Omnia 7 (bought it unlocked but has the Orange UK logo and apps preloaded).
It's not Walshed (I didn't even have an idea what that even meant until a couple hours ago but still tried that tool, just in case - it says "Good news, your phone isn't Walshed!") and the Windows Phone Support Tool says the phone's not in a "Connect to PC state", even though it is.
To sum up: nothing works.
Oh, almost forgot: I then saw the post about the USB drivers, it's version is 4.8.2148.0 but it says it's the last version so it won't update, and when I unsinstalled it, it automatically installed the same version.
Click to expand...
Click to collapse
odd, the latest drivers are 4.8.2345.0 and these were installed a week before Mango was released to prepare the phones for Mango. Not sure why it would give you an older USB driver....
I updated the USB driver but the problem stays the same, not sure what else could be done
derausgewanderte said:
sounds like a USB driver issue.
open Device Manager
open Zune
plug in the phone into the USB
In the device manager you should see Windows Phone USB Device at the very bottom come in.
Double click and double click Windows Phone USB. Got to Driver tab and make sure it reads Deiver Version 4.8.2345.0
if you have something older, uninstall the driver, unplug the phone, then plug it back in and hopefully it will pick up the new one.
Click to expand...
Click to collapse
I'm been have the same problem with a samsung focus v1.3, i've tried everthing i could find, but nothing worked. I hope someone has an answer to what causing this.
I've reflashed the phone with both the rogers and at&t roms(many times) but can only get to 7403.
Also i have tried 4 different computers, one was ever XP.
i am getting the same update error with my Branded HTC HD7
Same error Omnia 7.
Posted it at MS forums: http://answers.microsoft.com/en-us/...-omnia-7/779a50b6-2080-40da-b106-c8b365c25372
Edit: Fixed mine by reverting back to 7392 and fixing a couple of registry values for language packs. I wanted to remove the ones I didn't need. That created the conflict. Now I'm on Mango!
DesiChoza said:
Same error Omnia 7.
Posted it at MS forums:
Edit: Fixed mine by reverting back to 7392 and fixing a couple of registry values for language packs. I wanted to remove the ones I didn't need. That created the conflict. Now I'm on Mango!
Click to expand...
Click to collapse
how did u revert back to 7392 update and which registry settings did you tweaked? would u mind sharing it with us? i have done hard reset on my phone but the os version is still 7.0.7043 and since i reset, there is no backup in zune to revert
well i uninstalled and reinstalled ZUNE then flashed the 7004 Schubert rom
plugged in the HD7 went through the update procedure from 7004 to nodo it automatically updated to 7403 but it errored out on the final mango update
Try This?
fouros said:
well i uninstalled and reinstalled ZUNE then flashed the 7004 Schubert rom
plugged in the HD7 went through the update procedure from 7004 to nodo it automatically updated to 7403 but it errored out on the final mango update
Click to expand...
Click to collapse
Not to be insulting, but did you try the Walsh Tool and select ALL languages that are on your phone. Most people who have gotten to the end of the MANGO update and failed with this error code fixed this with the Walsh Tool. Please don't dismiss it out of hand, it has solved this error code issue with a lot of people.
JamesAllen said:
Not to be insulting, but did you try the Walsh Tool and select ALL languages that are on your phone. Most people who have gotten to the end of the MANGO update and failed with this error code fixed this with the Walsh Tool. Please don't dismiss it out of hand, it has solved this error code issue with a lot of people.
Click to expand...
Click to collapse
i am not insuted and yes i did use the Walsh tool with the program saying my HD7 was not in a walshed state
pretty confused at the moment on what next to try
DesiChoza said:
Same error Omnia 7.
Posted it at MS forums:
Edit: Fixed mine by reverting back to 7392 and fixing a couple of registry values for language packs. I wanted to remove the ones I didn't need. That created the conflict. Now I'm on Mango!
Click to expand...
Click to collapse
Could you please elaborate?
Just to add to this, my brother inlaws focus, which i flashed with the rogers rom(It was a gift), installed the mango update yesterday morning. His phone is identical to mine.
fouros said:
well i uninstalled and reinstalled ZUNE then flashed the 7004 Schubert rom
plugged in the HD7 went through the update procedure from 7004 to nodo it automatically updated to 7403 but it errored out on the final mango update
Click to expand...
Click to collapse
I am now on Mango
i had to use another telstra ROM for the HD7
http://forum.xda-developers.com/showthread.php?t=993186
installed this , forced update and now Mango tastes sweet

[Q] HTC HD 2 problems unlocking with Chevron

Hello there,
I have a problem with unlocking my htc hd2 with Chevron.
Since i upgraded my phone from WP7.0 to WP7.5 i have an connection error problem.
When i first installed WP7 on it it unlocked without any problem then i upgraded the same phone with the 7.5 wp version it seems to have problems unlocking it.
I tried everything step by step even uninstalling and installing sdk and zune but it still seems to be giving me the same problems.
I also tried to delete all the info in the hosts file and it still wont work.
Maybe its because i use the same pc and the same phone because after i updated 7.0 it saw the phone normally like an htc hd2 but after i flashed it with the 7.5 rom it saw the phone as the leo70.
I run windows 7 64 bit and i have no idea what else to try.
I also tried the dns dump and everything can someone help me out or should i just downgrade to 7.0 again ??

[Q] Error code 801812E0 while trying to restore Omnia 7

Hi,
Some of you might have read my Omnia 7 bluetooth thread located here.
So I decided to flash my ORIGINAL T-MOBILE UK rom which I procured from the forums. Before I began flashing I made a backup (via the WP7 Update cab sender tool)
I flashed my mobile with the T-MOBILE UK rom, but alas the Bluetooth didn't work. I flashed it again with the I8700XENJK1 rom (the one I had used in the VERY FIRST PLACE when I had got my mobile back in December '10)
I updated it to 8107 & tried restoring it using the backup I made (via WP7 update cab sender) but I got an error that said this :
An error prevented the restoration of your phone to its previous version.
We're having some trouble restoring your phone. Restart your phone manually and try restoring again.
To see if there's more information about this error click
Web Help.
Error Code
801812E0
I have googled the error code & haven't found anything useful. Is there anything you guys could suggest?
*bump anyone*?
Same here. WP7 Update Cab Sender says error 801812E0 and Zune says not enough space on device (WTH?)

CAB Sender errors

8018004D, is the error I get when I try updating through CAB Sender.
I'm already on the newest update, Mango, but according to heathcliff, my rom and samsung firmware was too old, so I needed it anyway, but well that's not really working. My device is Interop unlocked, but the Rooting will not work because "my device is not supported, whilst I'm on an Omnia 7.
I got kk2 update, so i flashed back to november 2010 or something liked that, than update to mango, unlocked it, and it updated through zune, without me really noticing ... But well Rooting is the problem here... and the CAB sender
Who can help me out?
Kristan

Categories

Resources