While I was busy stumbling through threads and deployments of xaps to try and get my marketplace to work, I somehow managed to click 'Relock' on my Chevron unlocker, and now I can't get it to unlock again! I get "
-Sorry, I'm having trouble communicating with the phone.
-Please make sure it's connect using USB
-Please start the Zune application" Zune's running and it even says the phone's connected, but I can't sync anything to it because i get a C00D2772 error, and can't get that fixed either. So the problem really is, Zune is connected to the phone, and so is the USB. I also can't deploy anything.
I saw this thread, http://forum.xda-developers.com/showthread.php?t=922853, but I have NO idea what its saying.
I recommend to flash a newer ROM, not the "original" Leo70 ROM from DFT. Most other "custom" ROMs come with Chevron cooked in.
Maybe you even opt for a "NoDo" ROM, from May/June, they are also completely "free"...
Related
Im having major difficulty keeping my phone connected for the 2.2 update. Here's the history:
I had FR008 on my phone and downloaded the stock 2.1 and was able to get back to stock 2.1 via the bootloader no problem.
Now I download the HTC 2.2 off their website and follow the instructions and it wont work. The phone wont stay connected.
Running the 2.2 update via the bootloader as I did 2.1 doesn't work (PC can't find phone) and HTC says to do it with the phone on and HTC Sync installed.
If I connect in HTC Sync Mode It connects fine! I can sync. Stays connected with no trouble, but as soon as I try to run the RUU it disconnects my phone and reports a connection error and will not continue. Sometimes if I try to connect half way through the RUU discovery process it says that the battery is less than 30% but it is at 100% and will not continue.
If I connect as a disk drive, It connects just fine. I can search my SD card via the PC, but when I run the RUU it disconnects the phone and says it has a connection error and will not continue.
Before anyone says "Why are you even bothering with stock 2.2" well I need to sell the phone and I want it stock.
any help would be appreciated.
Boot into the bootloader, go to fastboot, plug your phone in, and try running the ruu.
Sent from my Liberty using XDA App
why are you even bothering with stock 2.2 if you already have FR008?had to do it since you added that gay disclaimer
also, maybe it's a sign that you shouldn't do that.
wbkviper said:
Im having major difficulty keeping my phone connected for the 2.2 update. Here's the history:
I had FR008 on my phone and downloaded the stock 2.1 and was able to get back to stock 2.1 via the bootloader no problem.
Now I download the HTC 2.2 off their website and follow the instructions and it wont work. The phone wont stay connected.
Running the 2.2 update via the bootloader as I did 2.1 doesn't work (PC can't find phone) and HTC says to do it with the phone on and HTC Sync installed.
If I connect in HTC Sync Mode It connects fine! I can sync. Stays connected with no trouble, but as soon as I try to run the RUU it disconnects my phone and reports a connection error and will not continue. Sometimes if I try to connect half way through the RUU discovery process it says that the battery is less than 30% but it is at 100% and will not continue.
If I connect as a disk drive, It connects just fine. I can search my SD card via the PC, but when I run the RUU it disconnects the phone and says it has a connection error and will not continue.
Before anyone says "Why are you even bothering with stock 2.2" well I need to sell the phone and I want it stock.
any help would be appreciated.
Click to expand...
Click to collapse
If you already have it back to stock 2.1, I would sell it like that because it would be rootable to a potential buyer. If you install the stock 2.2, the phone will not be able to regain root and it would be far less appealing to a potential buyer IMO.
Well I guess I should say...I might sell the phone. My wife uses it, but recently bought an Atrix...but doesn't like it much. She really likes the aria for the size. We both think that the stock 2.1 ran better than fr008 or cyanogen. The proximity sensor problem seems to be much worse with those roms.
We were going to try 2.2 to see if the proximity sensor problem was improved at all. If not we would sell it. Probably will sell it anyway, either way it needs to go back to stock.
@jeebuz
Didn't work by running the RUU in the fasboot. Won't connect. But the drivers are confirmed to be working. They connect just fine in every other case and show up properly in the Device Manager.
Ok, If you are thinking about flashing one of Ansars ROMs then consider this first.
You may never be able to update your phone via Zune again..
Many users are experiencing Error 80180048 when attempting to update via zune from version 7008.
One thing they seem to have in common is that they have flashed one of Ansars ROM's
Here are some examples...
http://forum.xda-developers.com/archive/index.php/t-1034962.html
http://answers.microsoft.com/en-us/...80180048/ceb86673-e65a-e011-8dfc-68b599b31bf5
http://simonwilkins.wordpress.com/2011/04/02/march-update-nodo-for-wp7-arrives/
http://www.pocketpc.ch/windows-phone-7-allgemein/128982-fehlercode-80180048-update-7-0-7392-0-a.html
Plus a number of others on this site...
I have asked for assistance from ansar, and he provided another ROM, which caused even more problems and caused my device to not be detected by Zune or windows.
I know ansar works hard on these ROM's, but I think its important they you all know the risk and don't get stuck in the situation I am in, where I will now have to purchase a new handset.
Ansar: If you can at least acknowledge this issue and confirm that you are working on a fix that would be great, otherwise I believe this Thread is important as a warning to others.
Thanks
WP
Agreed. Verizon Trophy users flashing 0.82.605.02_Radio_1.25.00 are left with unusable devices until an official ROM is able to be flashed.
Be warned.
I flashed my trophy a few times ..
1. RUU_Spark_HTC_Europe_1.10.401.04_Radio_5.52.09.16_22.33a.50.10U_by_ansar
2.to NoDo via zune
3. Zune (nodo) to mango
4. forgot to unlock it before
5. We are back at RUU_Spark_HTC_Europe_1.10.401.04_Radio_5.52.09.16_22.33a.50.10U_by_ansar
6. NoDo via Zune
7. Zune (nodo) to mango (unlocked this time)
So i guess everything fine here
Ok, So the solution for me here was to Unbrand my device with a "Y" Cable and flash
RUU_Spark_HTC_Europe_1.20.401.00_Spark_5.54.09_RELEASE.
Once I was on this rom, I was able to update no problem through Zune to 7392.
Basically the ROMS by Ansar seem to be problematic and he isn't willing to provide any support. So, I suggest avoiding flashing them, unless you want problems in the future.
I've tried several roms, trying the XBMOD one now (which seems to have no clue as well) and for the life of me this thing is always locked.
When a rom states it has the unlock cooked in, what does that mean? I tried xbmod coming from android (task 29, magldr 1.13, flash, boot with volume up and down, down down twice.) and yet when I go to use the xap installer, I get the "make sure your phone is unlocked message". Since then, I've tried everything, even reinstalling windows on my other drive, then starting the whole process again, and same thing. Phone is still locked (even though this rom, and others I've tried state it comes unlocked). Is there some bug, or error, or did an update with zune maybe stop this? I've had no luck with any guides to unlocking, and tried several different registry edits, host edits, chevrons, certs, etc. And always get the dreaded uh oh message.
I guess I'm really asking, does cooked in unlock really mean it's unlocked? I mean, I've been flashing android forever and never had a problem like this. Most roms that state they are pre rooted, are in fact pre rooted, and don't require anything to work, yet any wp7 rom that states it's unlocked, isn't (at least for me) is it my system (remember, I've tried this with a clean win 7 install as well as my previous, all to no avail)?
Rooted and unlocked are two very different things, at least in the WP7 sense.
To be unlocked means you have access to install apps via sideloading
Rooted means you have unrestricted access to the file system
Most ROMs that are not original DFT ROMS are unlocked, these do not need to be re-unlocked, you do not need to use chevron, Zune needs to be installed and connected, the device must be connected to zune, you can try using the application deployment program but run it with admin rights
on the phone make sure the device ISNT pin locked, or on any other screen other than the tiles screen. you should be able to sync music to the phone if you cant then somthing else is wrong.
try all that an get back to us.
Hi guys.
You will all properly think here we go again with this noob question.
I have spent several nights figuring out how to jailbreak / dev unlock my omnia 7 without success.
It was an official t-mobile de version but i did the resistor trick to enter download mode and flashed the retail version i could find in one of the posts.
Now i am on version 7.0.7392 and i would like to unlock the device so i could registry edit my region so i can have a dutch phone when the mango update roles out. ( i also tried downgrading to nodo )
i have read much post but every time i get a error communicating message.
i have edited my host file, installed dev phone software installed certs, stopped running services on port 443, etc. etc.
but i couldn't connect to the phone with chevron.
Do i need to be on a special firmware version or something before this works?
is there someone out hear ho could help?
is there nobody how could help me?
hello,
i had the same issue as you a while back. if i remember correctly, chevron doesn't support nodo - i think it only supports 7008 or earlier. so, flash a pre-nodo rom, and remember to put your phone in aeroplane mode before you connect it to your pc to dev unlock it. also install samsungtools.xap and select prevent devie relock, as well as enable 3g toggle if you want - i find it very handy. reboot your phone after selecting prevent device relock in the samsung tools on your newly developer-unlocked phone.
Hi there thanks for the reply, i have already downgraded to version 7.0.7004
but still the same errors, cant communicate with phone. make sure you are running zune and the usb cable is connected.
do i need to run this from a windows xp machine?
i have done so many things now, installing dev tools. edit registry , airplane mode downgrading firmware, stop running process using port 443, tried 3 diferent machines already now. i cant figure it out.
Is there any solution for this problem .I am on 7008 and getting the same errors I need to install apps on this device
I managed to get get it work. but it is verry strange.
i do not know what it didt to make it work.
but you need to install windows developers tools ( start from a fresh install of zune and developers tools ) run chevron as administrator with the screen unlocked.
Also make sure you install the certificate on your phone.
Can anyone please explain what the Zune update error message actually means?
Have just spent the last hour searching the whole web and nobody seems to know.
I have managed to successfully download the Mango 7720 update from Zune on top of my previous BTTF rom. Had no problems with Mango update but now when i come to update the clean up update i constantly get the above message.
I have read all the solutions on the developers page (sorry but couldn't post this thread there) and have tried them all. So would just like to understand what the actual error means!!!
you maybe wining price for possible 100 or more asking same question here....
make sure your device not synced with Zune as Guest
disconnect phone
restart computer, restart phone
start Zune, connect phone
try update
if error occur again, restart phone few times...
It's a generic error code. Can mean a few different things; too low of battery (which is why I got it), USB port needs updating, device provisioning .cab wasn't used (so Zune won't recognize it to update it), settings for your Zune client, etc., etc.
^^ There's just a few examples of why you can get that error code, and I'm sure there's more. Hopefully one of the things I mentioned helps.
Sent from my King LEO using XDA Windows Phone 7 App
Thank you for providing some answers. Because I had just used Zune to get the Mango RTM update, I think I can eliminate, Zune client, guest sync and usb drivers. That leaves your suggestion of either low battery or cab install. I know I did cab install when doing the BTTF install. Therefore when I connected to Zune I got the 7720 RTM update.
Can I install the Device provision.cab again without causing any issues?
Zune 80004005 error code. On step 7 of 9
Trying to update from official zune 7403 to 7720 isv beta.
Tried taking sd card out sim out reserved space increased time zone changed.. Have already tried it about 5 times
Can anyone suggest anything else or should I push the cabs through?
OMG. After trying everything and giving up hope. I have just logged on to my PC upstairs and in a vein attempt clicked the install update button on Zune and hey presto, update installed. Technology is unpredictable and has a bloody mind of it's own.. So conclusion is just keep turning both your phone and pc on and off and pray it's your lucky day (7hrs later 30+ attempts)
A big thank you to everyone who has posted possible solutions.
Hey, congrats man! Glad you got it.
Sent from my King LEO using XDA Windows Phone 7 App
dxdy said:
you maybe wining price for possible 100 or more asking same question here....
make sure your device not synced with Zune as Guest
disconnect phone
restart computer, restart phone
start Zune, connect phone
try update
if error occur again, restart phone few times...
Click to expand...
Click to collapse
Can U old point me to where this problem (error 800b010a) has been solved cause it wasn't my lucky yes'dat or today I'll keep tring but don't think it'll work. thanks
Sent from my HD2 using XDA Windows Phone 7 App
Hi
It hasn't been officially resolved. It just seems people are resolving this error due to different problems. I found the thread in the developers section useful, titled ISV beta clean up. Hope some of the answers in there help. If not, like me, just keep shutting down both your pc and phone and pray. Good luck!!!
http://forum.xda-developers.com/showthread.php?t=1281902
Mangledraver said:
Hi
It hasn't been officially resolved. It just seems people are resolving this error due to different problems. I found the thread in the developers section useful, titled ISV beta clean up. Hope some of the answers in there help. If not, like me, just keep shutting down both your pc and phone and pray. Good luck!!!
http://forum.xda-developers.com/showthread.php?t=1281902
Click to expand...
Click to collapse
thanks but good news for me at last it updated lost count how many times ive tried. funny thing is i did it as a guest in zune with a flat battery....lol
so my advice (that anit worth much) is try then try again then again then again until your sick of it all......then u guessed it buy an i-phone
i had the same error... i tried again and again and again........ finally done it!!
to update, you need a bit of luck, I did not reboot PC or phone, just disconnect and reconnect again for times(each time lease disconnected for couple of hours, just forget it...) then it works...
good luck!