I'm a newbie here so pardon my lack of knowledge
I bought a T-mo DVP on ebay..unfortunately Zune says my phone is up-to-date on 7720!
Is there a way i can force a 7740 update?
Please help me out
So far the only way to update our TMO specific phones is the cab sender method. The generic DVP's have already gotten 7740.
Hopefully TMO will push out the 8107 update as they seemed to have skipped the 7740 update. Per MS, carriers are allowed to skip one update. Hopefully this holds true.
jelliottz said:
So far the only way to update our TMO specific phones is the cab sender method. The generic DVP's have already gotten 7740.
Hopefully TMO will push out the 8107 update as they seemed to have skipped the 7740 update. Per MS, carriers are allowed to skip one update. Hopefully this holds true.
Click to expand...
Click to collapse
Could you please show me how/direct me to a link on how to do the 'cab sender method' ? I'm new to all this
You might be able to acquire the update via the "disconnection" method. I don't know the exact name off the top of my head, but it basically involves disconnecting from the internet in the middle of the update process and reconnecting your phone to receive the update.
There were a couple of pieces written on it, I'll try to find one that properly explains it.
MisterPhilleh said:
You might be able to acquire the update via the "disconnection" method. I don't know the exact name off the top of my head, but it basically involves disconnecting from the internet in the middle of the update process and reconnecting your phone to receive the update.
There were a couple of pieces written on it, I'll try to find one that properly explains it.
Click to expand...
Click to collapse
The disconnect, or force method, won't work on T-Mobile/AT&T specific Venue Pros. I've tried numerous times on different computers. It only works on the generic version.
Here is the link for updating with the cab-sender tool: http://forum.xda-developers.com/showthread.php?t=1306415. Take your time and read through it. It can be very confusing.
I wonder what would happen if you used cabsender to force update your rom to be a 00EU or 00US rom, which have recieved 8107.
What're the odds it'd actually work vs bricking it?
Someone posted the list of files downloaded from
<some version i forget> -> 7720/219-33 (ie tmobile)
and the only device/carrier specific file that was sent was the one to install 219-33
TheManii said:
I wonder what would happen if you used cabsender to force update your rom to be a 00EU or 00US rom, which have recieved 8107.
What're the odds it'd actually work vs bricking it?
Someone posted the list of files downloaded from
<some version i forget> -> 7720/219-33 (ie tmobile)
and the only device/carrier specific file that was sent was the one to install 219-33
Click to expand...
Click to collapse
Mobility Digest put together a download link to batch together the files needed to update phones from 7720 -> 7740 -> 8107 using cab sender here: http://mobilitydigest.com/windows-phone-8107-manual-update/
I did it last night and it updated me without a problem and in less than 10 minutes. No promises it works for everyone. I have a TMOUS locked DVP. There is a "read me" included in the download.
8107 has completely cleared up my disappearing keyboard issue. It also seems to run a little more smooth than before. Best of luck if you want to try it.
I would expect pushing the OS itself would work fine, I'm talking about pushing the firmware/driver/ROM/device specific (whatever you want to call it) portion.
The FileSonic download link on the MobilityDigest article no longer works, probably from the chill of the Megaupload suit. So I can't get at that easy readme file.
Trying to learn this method straight from the xda-devs threads - not easy - has left me a bit uncertain about which cabs I need to send to my TMO-US DVP (now at 7720). Posts in the other thread say that you need to update every language on your device or else you'll end up "Walshed", i.e. future automatic updates won't work. But without the ability to run homebrew xaps, I'm not sure how we figure out exactly which lang packs come preinstalled on the device, and therefore which cabs we need to grab for the updates.
Everybody keeps saying that the force updates method took them 10 minutes. Great. Can we describe the 7720-7740-8107 process and list all required cabs to get everyone on the same page, especially now that the MobilityDigest instructions have disappeared?
benjaminries said:
The FileSonic download link on the MobilityDigest article no longer works, probably from the chill of the Megaupload suit. So I can't get at that easy readme file.
Trying to learn this method straight from the xda-devs threads - not easy - has left me a bit uncertain about which cabs I need to send to my TMO-US DVP (now at 7720). Posts in the other thread say that you need to update every language on your device or else you'll end up "Walshed", i.e. future automatic updates won't work. But without the ability to run homebrew xaps, I'm not sure how we figure out exactly which lang packs come preinstalled on the device, and therefore which cabs we need to grab for the updates.
Everybody keeps saying that the force updates method took them 10 minutes. Great. Can we describe the 7720-7740-8107 process and list all required cabs to get everyone on the same page, especially now that the MobilityDigest instructions have disappeared?
Click to expand...
Click to collapse
I'm in the same boat as you....using unlocked T-mobile in wind here in Canada...sitting at 7720...
benjaminries said:
The FileSonic download link on the MobilityDigest article no longer works, probably from the chill of the Megaupload suit. So I can't get at that easy readme file.
Trying to learn this method straight from the xda-devs threads - not easy - has left me a bit uncertain about which cabs I need to send to my TMO-US DVP (now at 7720). Posts in the other thread say that you need to update every language on your device or else you'll end up "Walshed", i.e. future automatic updates won't work. But without the ability to run homebrew xaps, I'm not sure how we figure out exactly which lang packs come preinstalled on the device, and therefore which cabs we need to grab for the updates.
Everybody keeps saying that the force updates method took them 10 minutes. Great. Can we describe the 7720-7740-8107 process and list all required cabs to get everyone on the same page, especially now that the MobilityDigest instructions have disappeared?
Click to expand...
Click to collapse
I didn't put this together so I take no credit for it. This is from another thread in the DVP forum. It is the same method I used on mine though. Worked like a charm.
http://forum.xda-developers.com/showthread.php?t=1497142
Best of luck.
jelliottz said:
I didn't put this together so I take no credit for it. This is from another thread in the DVP forum. It is the same method I used on mine though. Worked like a charm.
http://forum.xda-developers.com/showthread.php?t=1497142
Best of luck.
Click to expand...
Click to collapse
LOL - you just answered my earlier question by directing me to my own thread solving the problem. That is awesome.
benjaminries said:
LOL - you just answered my earlier question by directing me to my own thread solving the problem. That is awesome.
Click to expand...
Click to collapse
And a "thanks" on this one for you then. That gave me a good chuckle.
Good link for 7720 -> 7740 -> 8107 download for 8170_update.zip?
jelliottz said:
Mobility Digest put together a download link to batch together the files needed to update phones from 7720 -> 7740 -> 8107 using cab sender here: http://mobilitydigest.com/windows-phone-8107-manual-update/
I did it last night and it updated me without a problem and in less than 10 minutes. No promises it works for everyone. I have a TMOUS locked DVP. There is a "read me" included in the download.
8107 has completely cleared up my disappearing keyboard issue. It also seems to run a little more smooth than before. Best of luck if you want to try it.
Click to expand...
Click to collapse
Does anyone have the zipped up 7720 -> 7740 -> 8107 download for 8170_update.zip? The download on the http://mobilitydigest.com/windows-phone-8107-manual-update pages doesn't work. Trying to update a Dell Venue Pro
Thanks!!
Gabe
Related
Any word yet if/when Bell/Virgin will be rolling out 2.2 to Canadian users?
If I don't get it relatively soon I'll probably root. Is that more difficult to do with the Bell build?
Any suggestions from rooted Bell users?
No word yet. Canadian carriers suck at issuing updates in a timely fashion. I rooted my Legend over the summer and installed the Vodafone 2.2 build recently with no problems. For the root, you'll need to downgrade to the 1.31 RUU before you can successfully root.
Hi,
I wrote to Virgin Mobile support on November 30 and I got the following answer:
Hi there - HTC is currently working on this update and we're hoping to have it within the next couple months. We'll keep you guys up-to-date online. Stay tuned!
Lots of Love,
Virgin Mobile
Click to expand...
Click to collapse
And before that I wrote to Bell support and never got answered.
Personnaly, I found that «next couple months» is very long!
MikaelG said:
And before that I wrote to Bell support and never got answered.
Personnaly, I found that «next couple months» is very long!
Click to expand...
Click to collapse
Bell never answer questions I email them, HTC Legend related or not.
Sent from my HTC Legend using XDA App
I made a thread about this over at howardforums. somebody responded saying Virgin is working on it and they expect it to be out in January, and if there are any delays, early February.
I got tired of waiting for Virgin to come out with Froyo, so I rooted and flashed Cyanogen on my Legend and couldn't be happier. There is a bug with voicemail notifications, but I'm sure that will be fixed soon.
When (and IF) Virgin has an update, I'll do it on my wifes phone, but the added features that Cyanogen gives is well worth it.
FourForty said:
I made a thread about this over at howardforums. somebody responded saying Virgin is working on it and they expect it to be out in January, and if there are any delays, early February.
Click to expand...
Click to collapse
That's pretty brutal. I love my Legend, but I really regret buying it from Bell. I've had nothing but bad experiences with them.
Which rooting guide has the most success with the Legend?
I'm fairly new to this, so I'll have to do my homework before attempting a root.
Maybe a good December project.
i work for virgin mobile and own the legend myself.
I ask my DM, and manger almost weekly about the update only to hear that they have no idea.
I call technical support (store line/regular line) and no one there knows either.
I also check our daily updates.. daily. Only to find nothing about the legend day after day.
I've been holding my breath for the update, but i don't suggest you do the same.
Unbrand your phone by installing the WWE version and you will probably get the update faster than Bell or Telus.
Hopefully it's coming Monday.
--io
The update is likely only days away so i suppose it's a funny time to ask about debranding.
My main issue is that I don't know what rom to use from the shipped roms website... a little bit of a text explanation would be great.
I still don't know what RUU means... or what WWE is... and i've been actively doing some reading on the subject.
Any advice would be appreciated!
Thanks!
go to the wiki!!!! everything is there!!!!
Haha, that post was actually quite useful
RUU = Rom update utility
WWE = World Wide English
So all I have to do is pick the most recent WWE version and I'm good to go?
I got annoyed with the flip-flopping and waited until after the halfway mark in the month. I've rooted my phone and it works perfectly.
I found that Blayo's ROM to run extremely well on the Legend.
Sorry for bumping it again ( I've been monitoring this thread and everytime i see it bumped up, it gives me hope... but only to find out we are all asking the same thing ... WHEN?!!)
Since BELL discontinued the Legend, does this mean when (if?) Virgin releases the OTA update, BELL users like me will get the same VIRGIN update as well show up on our phone?
The post about updating it with the WWE version... if i understand it correctly, the steps are:
1. Create a gold card... i saw a thread about a manual (albeit complicated for the non-techno geek.. ) way and an automated way using a software someone wrote
2. Run the latest WWE that has been posted (this is supposed to debrand our phone so that we can "see" the SOftware Update for WWE, right)
3. Check the Software Update on the phone and i should see the Fryoyo Update. ( I assume if we apply update, the ROM Update (data) it will download on the phone will be billable...or count as your data usage)
Does this sound about right?
I'm keeping this update via WWE as my last option if the OTA does not see the light of day...for us BELL users..
At this point, i'd say it's 70/30 that bell does not get the update. Just because as you've said, it's a discontinued phone for bell. with a small install base.
Hopefully Virgin/Bell decide to push it to bell sets. I'm not sure if they'd have to prepare two versions for that though. From what i understand, we're only a few days away from finding out.
It's funny, Bell Discontinued the Legend because they couldn't keep them in stock due to HTC having a lack of stock because the Amoled screen wasn't being produced fast enough. hence why they switch to a different screen for the Legend. Most people think it was just old or selling poorly when in fact those are both false.
QkSi1ver said:
Sorry for bumping it again ( I've been monitoring this thread and everytime i see it bumped up, it gives me hope... but only to find out we are all asking the same thing ... WHEN?!!)
Since BELL discontinued the Legend, does this mean when (if?) Virgin releases the OTA update, BELL users like me will get the same VIRGIN update as well show up on our phone?
The post about updating it with the WWE version... if i understand it correctly, the steps are:
1. Create a gold card... i saw a thread about a manual (albeit complicated for the non-techno geek.. ) way and an automated way using a software someone wrote
2. Run the latest WWE that has been posted (this is supposed to debrand our phone so that we can "see" the SOftware Update for WWE, right)
3. Check the Software Update on the phone and i should see the Fryoyo Update. ( I assume if we apply update, the ROM Update (data) it will download on the phone will be billable...or count as your data usage)
Does this sound about right?
I'm keeping this update via WWE as my last option if the OTA does not see the light of day...for us BELL users..
Click to expand...
Click to collapse
There was noise about an update in Mid-Jan from Virgin, Bell as far as I remember has discontinued support and it's unlikely that there's going to be an update. You won't get the OTA update unless Bell releases it. I'm rather dissapointed with the promises that keep being broken for our rather expensive service... Root your 'phone.
The procedure is :
Create a Goldcard. As you mentioned there's very easy to follow guides out there.
Downgrade your phone to an earlier version of the software. This permits rooting your phone.
Root your phone. This will allow you to install a ROM other than the Carrier's ROM.
Install either a stock ROM (WWE) or a custom ROM.
As I mentioned in my previous post, I am using Blayo's ROM, which is almost identical to the stock FroYo ROM, but with a few tweaks that just make the phone feel nicer. I would reccomend looking into some of the other ROMs as well. You may find something you like. Android's about choice and this is one great advantage of rooting your 'phone.
mike998 said:
There was noise about an update in Mid-Jan from Virgin, Bell as far as I remember has discontinued support and it's unlikely that there's going to be an update. You won't get the OTA update unless Bell releases it. I'm rather dissapointed with the promises that keep being broken for our rather expensive service... Root your 'phone.
The procedure is :
Create a Goldcard. As you mentioned there's very easy to follow guides out there.
Downgrade your phone to an earlier version of the software. This permits rooting your phone.
Root your phone. This will allow you to install a ROM other than the Carrier's ROM.
Install either a stock ROM (WWE) or a custom ROM.
As I mentioned in my previous post, I am using Blayo's ROM, which is almost identical to the stock FroYo ROM, but with a few tweaks that just make the phone feel nicer. I would reccomend looking into some of the other ROMs as well. You may find something you like. Android's about choice and this is one great advantage of rooting your 'phone.
Click to expand...
Click to collapse
I'm gonna give it up to the end of Jan and if there are no updates, i'll definitely go this way... im out of space to install anything else... angry birds and talking tom are taking so much space... had to remove my talking tom to install some smaller apps.
On Facebook, the guy from Virgin told that they had problems with the update so they are doing more testing...
If you want to be up to date, I really suggest you to root your phone and try a rom. You won't lose any functions on your phone and you'll never have to wait again.
mike998 said:
There was noise about an update in Mid-Jan from Virgin, Bell as far as I remember has discontinued support and it's unlikely that there's going to be an update. You won't get the OTA update unless Bell releases it. I'm rather dissapointed with the promises that keep being broken for our rather expensive service... Root your 'phone.
The procedure is :
Create a Goldcard. As you mentioned there's very easy to follow guides out there.
Downgrade your phone to an earlier version of the software. This permits rooting your phone.
Root your phone. This will allow you to install a ROM other than the Carrier's ROM.
Install either a stock ROM (WWE) or a custom ROM.
As I mentioned in my previous post, I am using Blayo's ROM, which is almost identical to the stock FroYo ROM, but with a few tweaks that just make the phone feel nicer. I would reccomend looking into some of the other ROMs as well. You may find something you like. Android's about choice and this is one great advantage of rooting your 'phone.
Click to expand...
Click to collapse
Hello there, i'm new to this flashing ROM, rooting and stuff...
In your post, it sounds easy, create a golden-SD (follow the guides), downgrade and update the WWE...
i got lost on the second step... how do you downgrade the phone? I have a VM legend 2.1 w/ update 1 and seems like VM is not giving out the update. I'm thinking going your way but don't know how to downgrade the phone.
Please advise.
Thanks in advance.
***UPDATE*** Damn. I ran the update (filename is RUU_Vision_BellMobility_WWE_1.34.666.1_Radio_12.28b.60.140e_26.03.02.18_M2_release_154437_signed.exe), and the update process began. It started off with "Erasing User Data"... then "Sending"... then quickly brought up a window that said:
ERROR [156]: IMAGE ERROR The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again.
This sounded like a good match for this device. I'm stuck now. Anyone have any ideas?
***old -UPDATE*** I found a Bell stock update... gonna try this out.. thanks for reading.
Hello all. Forgive me, I'm a Blackberry user and I just got an HTC Desire Z (it is locked to Bell in Canada - CDMA carrier?). I'm waiting for my unlock code to arrive (as I am on a different/GSM carrier) and I'm getting antsy to try it out.
I tried searching this forum tree using many different terms but all I've managed to find were custom ROMS and foreign official ones.
First thing I want to do is update it... I downloaded HTC Sync, which installed all the necessary drivers. (Except HTC Diag - found this online). So now I can connect it to my PC without any driver drama.
Then I went looking for an update. I found RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e_26.03.02.26_M_release_155556_signed.exe (but to be honest I wasn't sure if this is correct for my phone - I tried it anyway). It got so far as to reboot the phone to start the process but it then told me it wasn't the right update for my phone.
So that's where I am right now. I've been reading a lot about rooting, etc. but don't even want to go that far just yet. I just want to start off by getting a nice official software update/rom to get this thing up-to-date.
Currently, the version on this phone is 1.01.666.1 (sounds pretty old to me). I want to get rid of this blasted watermark (and I'm hoping a software update will take care of this).
Which ROM/software update is right for this phone? Any info / links would be appreciated. Thanks!
LaZiODROID said:
***UPDATE*** Damn. I ran the update (filename is RUU_Vision_BellMobility_WWE_1.34.666.1_Radio_12.28b.60.140e_26.03.02.18_M2_release_154437_signed.exe), and the update process began. It started off with "Erasing User Data"... then "Sending"... then quickly brought up a window that said:
ERROR [156]: IMAGE ERROR The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again.
This sounded like a good match for this device. I'm stuck now. Anyone have any ideas?
***old -UPDATE*** I found a Bell stock update... gonna try this out.. thanks for reading.
Hello all. Forgive me, I'm a Blackberry user and I just got an HTC Desire Z (it is locked to Bell in Canada - CDMA carrier?). I'm waiting for my unlock code to arrive (as I am on a different/GSM carrier) and I'm getting antsy to try it out.
I tried searching this forum tree using many different terms but all I've managed to find were custom ROMS and foreign official ones.
First thing I want to do is update it... I downloaded HTC Sync, which installed all the necessary drivers. (Except HTC Diag - found this online). So now I can connect it to my PC without any driver drama.
Then I went looking for an update. I found RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e_26.03.02.26_M_release_155556_signed.exe (but to be honest I wasn't sure if this is correct for my phone - I tried it anyway). It got so far as to reboot the phone to start the process but it then told me it wasn't the right update for my phone.
So that's where I am right now. I've been reading a lot about rooting, etc. but don't even want to go that far just yet. I just want to start off by getting a nice official software update/rom to get this thing up-to-date.
Currently, the version on this phone is 1.01.666.1 (sounds pretty old to me). I want to get rid of this blasted watermark (and I'm hoping a software update will take care of this).
Which ROM/software update is right for this phone? Any info / links would be appreciated. Thanks!
Click to expand...
Click to collapse
I'm assuming from your initial post that you're not on Bell Canada and are wanting to use it on a different carrier? If that's the case, use gfree (see the wiki) to unlock your device (and fully root it, if you want).
Sent from my T-Mobile G2 using XDA App
Kinda lost, still don't fully understand WP7. I bought the phone a few weeks ago with a Mango Beta installed on it. Someone brought it to my attention that when the legit Mango comes out that I won't be able to update to it. How can I get my phone to where I can update it when the official Mango release comes out? I have searched this but I'm not sure if reading on a different phone forum makes a difference. And people answer this question in different ways so it's a little confusing. Thanks guys!
First thing to do is check which version of the software you have on your phone, settings - about - more info.
If you have an OS version number greater than 7.0.7392 but less than 7720 you have a beta build of the OS and you wont be able to directly update the OS to Mango. This is because when the beta version of the OS was loaded it took a backup of your phone for you to return to when the official update was released. The backup is keyed to you device ID and means that a backup from someone else's phone wont work on yours.
However there are methods that will allow you to update to the RTM version of the OS at this link HERE or HERE but be warned that the update that is coming out in the next couple of weeks will have the extra drivers and tweaks that are specific to the DVP from Dell.
If you don't feel confident with that, you could try getting the person you bought it from to restore it back to the old version so that you can receive your update, or phoning dells support (Ouch!)
Looks like there may be an official way to install the final Mango without rolling back to NoDo first:
http://www.wp7connect.com/2011/09/2...date-no-rollback-needed-for-mango-beta-users/
pjfan75 said:
Looks like there may be an official way to install the final Mango without rolling back to NoDo first:
http://www.wp7connect.com/2011/09/2...date-no-rollback-needed-for-mango-beta-users/
Click to expand...
Click to collapse
yep, another piece on it
http://www.wpcentral.com/more-mango-friends-and-family-pre-cleanup?utm_source=wpc&utm_medium=twitter
Bummer... wish I had known about this "Friends n Family" update last week before I restored Nodo. (Stupid rumors!!!) It's like a totally different phone. Here's hoping the update is coming soon.
That's awesome! That looked like such a pain that I was probably going to stay on the beta lol.
Awesome, I'll make a thread with precise steps so people may see it and finally get our DVP's fixed and updated!
Devious Criminal said:
Awesome, I'll make a thread with precise steps so people may see it and finally get our DVP's fixed and updated!
Click to expand...
Click to collapse
And spam your own site as you do? Ugh.
I have update my DVP to 7740 using the offline update tool posted in Windows development and Hacking, But there has been no changes in the software just that the phone now shows 7740.16 instead of 7720.
Has anyone else updated their phones, and if there has been some changes in the software they have noticed, please post here.
You sir are my hero for pointing me to that offline update tool. I was able to not only update my DVP but also add my mother tongue as a language (dutch).
Having said that, other than the different version number, I have not noticed much change from before. My DVP still has difficulties connecting to my wifi AP... Compass is still broken as well (to be expected).
Yes the compass is still broken, but i am having no problems connecting to my secure wifi .
7740 only fix voice mail notification and Exchange server connection issue. No tethering, no compass fix.
yeungl said:
7740 only fix voice mail notification and Exchange server connection issue. No tethering, no compass fix.
Click to expand...
Click to collapse
no tethering... SIGH!
Tethering is likely never to come to the DVP. It was never promised.
MJCS said:
Tethering is likely never to come to the DVP. It was never promised.
Click to expand...
Click to collapse
And same with the compass per Lionel on Twitter...
@rishabmittal
Could you be more specific which offline update tool did you use (I don't want to brick my DVP cause it's far away from US where it was bought)?
Or perhaps you could share with us the entire update procedure.
My DVP is unbranded (generic) with Mango 7720 and recently Chevron unlocked.
Thanks!
you can update your dvp visiting the link given below.
http://forum.xda-developers.com/showthread.php?t=1306415
download all the attached files and download the 7740 attachment and do as given in the forum.
The above method doesn't work anymore
rishabmittal said:
you can update your dvp visiting the link given below.
http://forum.xda-developers.com/showthread.php?t=1306415
download all the attached files and download the 7740 attachment and do as given in the forum.
Click to expand...
Click to collapse
I can't find a wp7update tool on internet, its says its unsupported by the developer and no link for the files ... ...
BTW does this work on a bricked dvp ?
I'm trying to flash a firmware onto it, it's basically missing the original SD card so it's saying Storage Card Not Working ... ... or is that simply the case of using a nokia phone to flash the card and hopefully it will update on zune ?
Please help ^^
I was under the impression that we were unable to install the new tango updates while running custom roms? Being a total noob and not knowing any better I may have done just that. Or being a complete noob I could be mistaken :silly: After screwing something up messing with registry files, yes I knew better but I couldn't resist, I did a hard reset on my Verizon Trophy running DFT Freedom ROM V5 for Spark_W with the Mango v3 Radio. Downloaded a few xaps and yep still unlocked so just for fun I ran the software updates and language packs using xboxmod's WP7 Update Cab Sender which completed with no errors. Didn't fix the Internet Sharing issue on this rom but did enable Commercial Mobile Alert System which was not included in this rom; see this thread http://forum.xda-developers.com/showthread.php?t=1546287&page=2. I am fairly sure these settings appeared before updating the radio to Mango v3. Like I said being a noob I could be completely off track but is there any other way to tell if the updates took?
tonbonz said:
I was under the impression that we were unable to install the new tango updates while running custom roms? Being a total noob and not knowing any better I may have done just that. Or being a complete noob I could be mistaken :silly: After screwing something up messing with registry files, yes I knew better but I couldn't resist, I did a hard reset on my Verizon Trophy running DFT Freedom ROM V5 for Spark_W with the Mango v3 Radio. Downloaded a few xaps and yep still unlocked so just for fun I ran the software updates and language packs using xboxmod's WP7 Update Cab Sender which completed with no errors. Didn't fix the Internet Sharing issue on this rom but did enable Commercial Mobile Alert System which was not included in this rom; see this thread http://forum.xda-developers.com/showthread.php?t=1546287&page=2. I am fairly sure these settings appeared before updating the radio to Mango v3. Like I said being a noob I could be completely off track but is there any other way to tell if the updates took?
Click to expand...
Click to collapse
No, it isn't that these updates won't work, it is that they haven't been recommended for installation (quiet a difference). The reason the driver update was always avoided, was because the WIRELESS driver would be replaced with one that wouldn't enable Internet Sharing (meaning if you installed the older driver updates, your Internet Sharing would either disappear, or simply stop working). Since this new driver enables it, it might not be a bad idea to update to it, since it fixes the random MAC address issue. Also, the recommendation was to not use Zune to update, since it will push out ALL updates.
Using WP7 Update Cab Sender is good for those who know what they are doing, but up until the Spark_W Tango update, we had no official hotspot support. Now that the hotspot support is in the driver, I don't see the issue in pushing the driver update cab (which I recently posted the link to here).
Also, if your running on a network other then Verizon, you might need to change the new default Internet Sharing settings using the info found here. If you have unlimited data go here to get it working.
You've inspired me to go ahead and push the driver update to my primary phone, worst case I can restore my backup if it kills tethering (which it shouldn't).
Looks like the driver update won't take for ansar's Tango rom. I'll need to do some testing to figure out why. Maybe it's about time I did a build of XevRev and released it for our phones. With tethering official supported, so long as I make the support universal in the WIRELESS driver, we'll have fixed tethering support.
TheXev said:
Looks like the driver update won't take for ansar's Tango rom. I'll need to do some testing to figure out why. Maybe it's about time I did a build of XevRev and released it for our phones. With tethering official supported, so long as I make the support universal in the WIRELESS driver, we'll have fixed tethering support.
Click to expand...
Click to collapse
I think an XevRev build would be highly anticipated and appreciated!!! I've been jumping through all the available custom roms for the Spark_W just to get a feel for them and trying different things out. I couldn't push ANY of the update cabs to ansars rom. I will try the driver update later with the DFT v5 and get back to you. I thank you sir for your time, your knowledge, and your hard work :good:
No luck pushing the driver update to DFT's rom either so decided to play around with the SolvZ v1 rom from DocMentalZ. Software update cabs installed no problem but still no luck with the drivers. I do like this rom especially the custom theme colors however seems to have the same problem with Internet Sharing as the DFT rom. I can't really see me using tethering it's just one of those things that if it's available I want it!!! Still, rather have the full unlock of a custom rom if I have to choose. Once again, I thank you sir :highfive:
If you pushed the OS cabs, push the updated driver for VZW Trophy as well. If the rom let you push from 8107=>8112=>8779, then you should be able to push the driver.cab after all of that (do a full backup before just in case it breaks something).
DFT v5 might work since its 8107 Mango.. but I think the leaked 8107 DFT is probably a better rom to try updating with.
Also make note of the tethering information in the post and do that if you must. To reach the programming menu, you MUST have a stock like rom installed without unlock.
I keep thinking when I do release XevRev, I'll have to have at LEAST three-five versions of it (one without full unlock but inter-op so you can use Root Tools for unlock and still have programming menu, a Full-Unlock ver 8107, and a Full-Unlock ver 8779, and a Full-Unlock with no preinstalled OEM apps).
Still no luck with OEM cabs on any custom spark_w roms. Quick question a lol off topic...Is Chevron unlock still possible if I flash back to stock?
Chevron unlock is possible, but not recommended. All fully unlocked roms have the interop unlock that chevron provides built in. I am currently working on a rom that might solve almost ALL of our problems... I'm testing the updatability right now to be sure.
All I can say it.. I figured out the source of the programming problems [it's related to XIP unlock and xap deployment] thanks to a huge help from ultrashot! Currently, I have a fully unlocked phone that can program and its updating to 8773 at this very moment (I intentionally built it on 8107 so we could install the newest HTC drivers and get the newest radio on our phones)... but it still needs a xap deployment tool.. since I had to remove all xap deployment from it to make programming work.
I'm going to try and manually deploy Bazaar to the phone in an attempt to still get xap deployment up and running from Dynamics7 manually.
I'll be testing the crap out of this and communicating further with ultrashot.. hopefully a "once and for all" solution can be found now the true problem has been identified.
8773 checked out okay with my Dynamic7's 1.21 port, now to test the new drivers with official internet sharing.
Okay, driver update failed. I'm guessing it fails because it cannot update the HSPLed bootloader.... Might need a custom driver cab that removes the SPL update and just does everything else. :/
TheXev said:
Chevron unlock is possible, but not recommended. All fully unlocked roms have the interop unlock that chevron provides built in. I am currently working on a rom that might solve almost ALL of our problems... I'm testing the updatability right now to be sure.
All I can say it.. I figured out the source of the programming problems [it's related to XIP unlock and xap deployment] thanks to a huge help from ultrashot! Currently, I have a fully unlocked phone that can program and its updating to 8773 at this very moment (I intentionally built it on 8107 so we could install the newest HTC drivers and get the newest radio on our phones)... but it still needs a xap deployment tool.. since I had to remove all xap deployment from it to make programming work.
I'm going to try and manually deploy Bazaar to the phone in an attempt to still get xap deployment up and running from Dynamics7 manually.
I'll be testing the crap out of this and communicating further with ultrashot.. hopefully a "once and for all" solution can be found now the true problem has been identified.
8773 checked out okay with my Dynamic7's 1.21 port, now to test the new drivers with official internet sharing.
Okay, driver update failed. I'm guessing it fails because it cannot update the HSPLed bootloader.... Might need a custom driver cab that removes the SPL update and just does everything else. :/
Click to expand...
Click to collapse
Waiting patiently...haha. I'm just having fun playing with all the different roms and apps and reading the forums absorbing as much as I can. Your time and work, and don't forget your patience with us noobs, is greatly appreciated as is ultrashots, Heathcliffs, jaxbots,and well every d*** person that devotes their time and effort here. Sorry if I only threw out a few names but there are so many. Seriously, thank you and can't wait for the new XevRev!!!