Okay. So i thought itd be cool to be able to update to WIndows 7.8 RTM that was posted here on XDA without making a custom rom or wiping files (basically a clean easy update anyone who could push a cab to their phone can do.)
Anyways, i downloaded the RTM build and a Tango update cab to compare files with and see how to name the files and what id need.
Turns out, it was pretty straightforward at first. All the files within the cab had identical files (as far as filenames and types, except they were the 7.8 RTM versions.) within the system files folder of the rar of the RTM. so i packaged all the proper folders as cabs with the appropriate filenames (folder.version.coming.from-version.going.to.cab) and used a batch renamer to add the .pku extension to the end of the files as so to match the style of the tango cab (the tango update cab contains cabs with the .pku added on the end. once i removed .pku, making it a .cab file they open perfectly.) then i packaged all the .cab.pku files as a cab. So far so good. It looked like a WP7 update cab. THEN...
When i tried pushing the cab to my device, i learned it has to be signed...
I tried signing it with a copy of the certificate i pulled from the tango cab. No luck. need the private key.
Then i tried a certificate existing on my pc, created by zune, that i had a private key for. No go.
Created a key and certificate in MakeCer. No go.
Upon using a cab signing tool i found online for signing Windows Mobile Cabs with some generic sdk certificate, i got the error 8007000b.
Overall, my cab wont sign, idk if this works, im not very good at this stuff, and idk what im doing wrong. Can anyone help?
Perhaps sign the cab file?
Or is this all futile, and would my idea not work anyways (i figured it wouldnt hurt to try. With an update i figured worse case scenario i boot into restore mode and restore from a backup.)
Or does it have to be signedby microsoft, still making it futile?
My Update Cab (Skydrive, Public Link): http://sdrv.ms/12cw9pf
NOTE: Yes, i know the tango update was only 20 -30mb, while mine is over 180. The RTM contained more system files than the tango update, most likely due to it containing new features and OS modifications. Also, should i of excluded the EXEs from some of the folders from the cabs?
DustinWolf said:
Okay. So i thought itd be cool to be able to update to WIndows 7.8 RTM that was posted here on XDA without making a custom rom or wiping files (basically a clean easy update anyone who could push a cab to their phone can do.)
Anyways, i downloaded the RTM build and a Tango update cab to compare files with and see how to name the files and what id need.
Turns out, it was pretty straightforward at first. All the files within the cab had identical files (as far as filenames and types, except they were the 7.8 RTM versions.) within the system files folder of the rar of the RTM. so i packaged all the proper folders as cabs with the appropriate filenames (folder.version.coming.from-version.going.to.cab) and used a batch renamer to add the .pku extension to the end of the files as so to match the style of the tango cab (the tango update cab contains cabs with the .pku added on the end. once i removed .pku, making it a .cab file they open perfectly.) then i packaged all the .cab.pku files as a cab. So far so good. It looked like a WP7 update cab. THEN...
When i tried pushing the cab to my device, i learned it has to be signed...
I tried signing it with a copy of the certificate i pulled from the tango cab. No luck. need the private key.
Then i tried a certificate existing on my pc, created by zune, that i had a private key for. No go.
Created a key and certificate in MakeCer. No go.
Upon using a cab signing tool i found online for signing Windows Mobile Cabs with some generic sdk certificate, i got the error 8007000b.
Overall, my cab wont sign, idk if this works, im not very good at this stuff, and idk what im doing wrong. Can anyone help?
Perhaps sign the cab file?
Or is this all futile, and would my idea not work anyways (i figured it wouldnt hurt to try. With an update i figured worse case scenario i boot into restore mode and restore from a backup.)
Or does it have to be signedby microsoft, still making it futile?
My Update Cab (Skydrive, Public Link): http://sdrv.ms/12cw9pf
NOTE: Yes, i know the tango update was only 20 -30mb, while mine is over 180. The RTM contained more system files than the tango update, most likely due to it containing new features and OS modifications. Also, should i of excluded the EXEs from some of the folders from the cabs?
Click to expand...
Click to collapse
nice try , never going to work
first :
the Tango cab is a .pku , that is a DIFF Image update it is the DIFF between what is on phone and what got updated ( thats way it is so small)
second:
the 8858 DUMP is canoncial , so ist the whole flie ( thats way it is 180 mb)
third:
cab.pkr/pkg/pku Needs tobe signed with the sert on the phone ( so for stock roms this means MS Needs to sign them )
the supercab also Needs tobe signed by OEM or MS
so you did all the work for nothing
ceesheim said:
nice try , never going to work
first :
the Tango cab is a .pku , that is a DIFF Image update it is the DIFF between what is on phone and what got updated ( thats way it is so small)
second:
the 8858 DUMP is canoncial , so ist the whole flie ( thats way it is 180 mb)
third:
cab.pkr/pkg/pku Needs tobe signed with the sert on the phone ( so for stock roms this means MS Needs to sign them )
the supercab also Needs tobe signed by OEM or MS
so you did all the work for nothing
Click to expand...
Click to collapse
-w-' i feared as much... *sighs* i guess even if i ever did get the proper files in the cabs id still need the private key for the certificate... oh well... guess ill just have to wait for MS to release 7.8...
Nothing wrong with trying.
Sent from my HD7 T9292 using XDA Windows Phone 7 App
i applaud your attempt...keep plugging away
aclegg2011 said:
Nothing wrong with trying.
Sent from my HD7 T9292 using XDA Windows Phone 7 App
Click to expand...
Click to collapse
is this try the first of its kind??i mean is this the first time that u r trying to create updates like this??
if yes i am damn sure u have learned a lot while doing this..
You can get the right files into the cab and sign it with ultrashot certificate perhaps? Ppl with custom roms can use it and your work wouldn't be a complete waste. This is assuming this cab update won't have any effect on the unlock itself
nithin1992 said:
You can get the right files into the cab and sign it with ultrashot certificate perhaps? Ppl with custom roms can use it and your work wouldn't be a complete waste. This is assuming this cab update won't have any effect on the unlock itself
Click to expand...
Click to collapse
Hehe... im not so good with that stuff. The reason i tried at all is because i noticed the RTM 7.8 contained the same files as the update cab for 7.5. Problem is, i apparently require the knowledge of which files are updated (because the way i apparently had made it it would of replaced dang near every system file) as well as i have no clue on how to sign it. i noted that i couldnt sign the cab with my own signing certificate, so im at a complete loss... my apologies. (if anyone wants to take my cab and see if they can do something with it be my guest, but im not very experienced with this.)
prahladvarda said:
is this try the first of its kind??i mean is this the first time that u r trying to create updates like this??
if yes i am damn sure u have learned a lot while doing this..
Click to expand...
Click to collapse
Yes this is my first time, and i have learned some things.
A: Just because its in the RTM doesnt mean it should be in the Update cab
B: If you want to use updates on stock roms, you must have the cab signed by microsoft, so No Update For You
C: Its a pain in the rear to sign a cab with a certificate you own (at least it was for me. Still unsuccessful)
D: Windows Phone has .EXE's
E: Windows Phone has a lot of files
F: LG Has a locked bootloader (what pushed me to try this was when i learned LG's (like my quantum) cant have custom roms)
DustinWolf said:
F: LG Has a locked bootloader (what pushed me to try this was when i learned LG's (like my quantum) cant have custom roms)
Click to expand...
Click to collapse
u can have all the goodness of custom roms with interop unlock itself..interop unlock using mfg app, install wp7roottools and mark apps that require root access as trusted in wp7roottools policy editor and u r good to go..
prahladvarda said:
u can have all the goodness of custom roms with interop unlock itself..interop unlock using mfg app, install wp7roottools and mark apps that require root access as trusted in wp7roottools policy editor and u r good to go..
Click to expand...
Click to collapse
Nope. You see, the whole point would be (if I was to try would be) to make a 7.8 rom. Idgaf about the "goodness" of custom roms, and only reason I use wp7root tools is for MarketplaceSwitcher (the fixed version). I cant get 7.8 using interop unlock. I need a custom rom to get it. Problem is, LG windows phones have a locked bootloader. Translation: No custom roms. Meaning the purpose of creating a custom rom would be pointless.
That's why I attempted to make an update CAB. Those could be pushed via the cab updater method, which works with any wp7 handset, and wouldn't erase my data as well. Problem? Official roms cant be updated via cabs with anything other than Microsoft signed cabs. So my attempts were futile.
Thank goodness, though, that 7.8 should be coming to some handsets on the 30th. Im hoping some people catch those cabs and post them (because I CAN use the cab updater method, given that the packages are Microsoft signed, as stated above.):fingers-crossed:
Not sure I know what you mean by goodness of custom roms, wp7 is about as lean as you can get, its not like the good old wm days where different builds were available on different devices an full of stuff, or android where its full of crap, if its just to restore with some apps preinstalled then make a Zune backup and restore from that when You need to
Sent from my Lumia 900 using XDA Windows Phone 7 App
help ! I need adobe reader for WP7
ceesheim said:
nice try , never going to work
first :
the Tango cab is a .pku , that is a DIFF Image update it is the DIFF between what is on phone and what got updated ( thats way it is so small)
second:
the 8858 DUMP is canoncial , so ist the whole flie ( thats way it is 180 mb)
third:
cab.pkr/pkg/pku Needs tobe signed with the sert on the phone ( so for stock roms this means MS Needs to sign them )
the supercab also Needs tobe signed by OEM or MS
so you did all the work for nothing
Click to expand...
Click to collapse
--------------------
DEAR
I FLASH WP7 ON MY HD2 and now i cant to download PDF READER FROM MARKETPLACE . Please a link to download DIRECTLY.
I HAVE WINDOWS LIVE ID but market place dont regognize it.
many THANKS
dazza9075 said:
Not sure I know what you mean by goodness of custom roms, wp7 is about as lean as you can get, its not like the good old wm days where different builds were available on different devices an full of stuff, or android where its full of crap, if its just to restore with some apps preinstalled then make a Zune backup and restore from that when You need to
Sent from my Lumia 900 using XDA Windows Phone 7 App
Click to expand...
Click to collapse
What the person meant and that I was referring to by "goodness of custom roms" is that some WP7 roms have all the Nokia goodies baked in and can run software that regular WP7 cant due to software restrictions. Such as some include the Nokia drivers and files to run City Lens and use Camera Extras. The nokia extras, even though they can be installed on any windows phone (granted you have root tools and marketplace switcher to access the "Nokia Collection"), some require special drivers and files in order to work (including Bluetooth file transfer, which uses extra APIs and drivers not included out of the box by Microsoft for the upcoming 7.8).
All of which may achievable in the near future, bar pre installed apps of course, but the running of custom drivers may be possible, and as I said, install what you want, back it up and boom, your own rom ready should you need to format
Sent from my Lumia 900 using XDA Windows Phone 7 App
dazza9075 said:
All of which may achievable in the near future, bar pre installed apps of course, but the running of custom drivers may be possible, and as I said, install what you want, back it up and boom, your own rom ready should you need to format
Sent from my Lumia 900 using XDA Windows Phone 7 App
Click to expand...
Click to collapse
and like I said, all I want is the new home screen, rebranded tiles, and extra themes. Cant do that using apps.
Though the Nokia's should be getting the 7.8 update through zune tomorrow, so if someone could obtain the cab, ill be good. I don't want a rom anymore anyways. (I only would of wanted one in December. but now learning 7.8 is coming out tomorrow (albeit to specific devices) means I don't want to anymore, because I bet a dollar to a donut by the end of the week someone will of posted the update cabs, to which I will be good.)
Also, I tried adding drivers to my phone. Didn't work (followed steps to add correct drivers to my phone via WP7Root Tools and the drivers packaged in a xap that extracted them). But I don't really care, since I have an early beta of City Lens that supports my phone, so im good.
Overall, only reason I would rom is if I was desperate.
I cant actually use a true custom rom because of my device.
I understand your method, but its a back up, not really a "rom", since all my data is backed up with it, and I don't care about preinstalled apps anyways, since the apps I use are always changing. I don't prefer restoring my device unless 100% necessary (AKA: I screwed something up) so I don't do this.
DustinWolf said:
and like I said, all I want is the new home screen, rebranded tiles, and extra themes. Cant do that using apps.
Though the Nokia's should be getting the 7.8 update through zune tomorrow, so if someone could obtain the cab, ill be good. I don't want a rom anymore anyways. (I only would of wanted one in December. but now learning 7.8 is coming out tomorrow (albeit to specific devices) means I don't want to anymore, because I bet a dollar to a donut by the end of the week someone will of posted the update cabs, to which I will be good.)
Also, I tried adding drivers to my phone. Didn't work (followed steps to add correct drivers to my phone via WP7Root Tools and the drivers packaged in a xap that extracted them). But I don't really care, since I have an early beta of City Lens that supports my phone, so im good.
Overall, only reason I would rom is if I was desperate.
I cant actually use a true custom rom because of my device.
I understand your method, but its a back up, not really a "rom", since all my data is backed up with it, and I don't care about preinstalled apps anyways, since the apps I use are always changing. I don't prefer restoring my device unless 100% necessary (AKA: I screwed something up) so I don't do this.
Click to expand...
Click to collapse
It sounds like the only reason youd want a ROM then is to have got the 7.8 update? that's a fair enough reason but as you know its coming out soon anyway so its not really important.
With regards to your Drivers, yeah it cant be done with WP7 Root tools at the moment, I believe im right in saying (and is public knowledge I hope!) that's being worked on as we speak
actually whilst I have your attention, see your City lens app, do you have issues with compass calibration? is the beta any less sensitive perhaps? Ive been trying and ill be damned if I can get it right
dazza9075 said:
It sounds like the only reason youd want a ROM then is to have got the 7.8 update? that's a fair enough reason but as you know its coming out soon anyway so its not really important.
With regards to your Drivers, yeah it cant be done with WP7 Root tools at the moment, I believe im right in saying (and is public knowledge I hope!) that's being worked on as we speak
actually whilst I have your attention, see your City lens app, do you have issues with compass calibration? is the beta any less sensitive perhaps? Ive been trying and ill be damned if I can get it right
Click to expand...
Click to collapse
The city lens I have TECHNICALLY was a Chinese version (apparently in china an early beta was released to ALL wp7 devices) and the app was translated and posted somewhere around here on XDA, and can be sideloaded if you've dev unlocked (I dev unlocked using mfg). It DOES require calibration most of the time when you first open it, and since the quantum had a funny way of handling the compass driver (even LG's own apps work funny with compass) it works weird, but other then that its fine. Depending on the phone you have it should work well enough. I will not post the xap here only due to the fact that its already somewhere else on xda and don't want to post it without accrediting the work the user did to translate. (I for the life of me cant find where it was originally posted on here).
Related
Is there a good, simple to use emulator that will allow me to check out different software and roms?
Are you talking about a Windows Mobile 5 of 6 emulator?!? Heck just try out different ROMs in combination with your phone man, like we all do
Have you downloaded the WM SDK from Microsoft yet?
No not yet, keep meaning to check it out, will it let me install packages and test them?
Packages?
If you mean programs then yes, you can install and test them with Microsofts SDK. Its possible to "cradle" the emulator like a real device and sync it with your computer.
WM6 roms you have to test directly on your device but don't be too afraid, its not that bad. Of course you have to test at least 3 different roms so don't forget to backup your data and be prepared for some sleepless hours And as murphys law is omnipresent you should have a second phone. Just in case.....
LMAO Yes I'm getting an official Vario II at the end of April, I'm already running LVSW and patiantly awaiting the release of BE2. (Got this one on eBay but want to make best use of my upgrade discount).
BTW, I've already bricked my phone about 15 times over the last week, but thanks to OliPro's SPL it just comes right back up... have to read up on it before flashing not after, I already had my .nbh file ready on a spare card so took minutes to get back up.
Great to hear I can look at software and settings before installing so will be doing that so I can keep my phone up and running without changes as much as possible but it's a shame we can't ROM test too....
http://forum.ppcgeeks.com/showthread.php?t=17473
well im changing this because of a request that a lot of people supposedly dont know how to flash. but i dont think that the link was doing anyone much good. so here is what is at the link (right now at least).
THIS IS ONLY FOR THE HTC CDMA TOUCH (VOGUE) !!
i know this first post here is now real long, but READ IT ALL before posting/pm'ing anyone. trust me, you will get through it all...every last word.
(dont get all scared either, this cant ruin your phone. if you are stuck at the htc boot screen, your device is not bricked. if you are stuck at a rainbow/tricolor screen, your phone is not bricked. have faith and patience! )
this method is for a pc running Microsoft Windows XP. if this is not your situation, still continue reading as there are methods for virtually every case.
ive been told that imcokeman's vogue unlocker will not work from a partitioned drive, though im not sure if thats the case.
if you know what flashing/the benefits of flashing are, skip this paragraph; if not, read on. flashing could be likened to installing a different Operating System on your PC. keep in mind, however, that when flashing roms to phones/pdas, the roms ARE DEVICE SPECIFIC. if you find an awesome rom for the titan and LOVE it, but you yourself have a kaiser, forget it. only roms made specifically for your device (and no, even if you have a cdma device, and they make a gsm version of your device, it still will not work) will work for your device. the benefits/advantages of flashing a custom rom onto your device are speed enhancements, addition/removal of programs/settings/reg settings you want or dont want.
now for how to..
for some slight insight on using a Mac, have a look down to the bottom where it says "HERE IS THE BOTTOM" after reading everything else, and/or go here: http://forum.xda-developers.com/show...ighlight=macos
for how to on Vista: look down to the bottom where it says "HERE IS THE BOTTOM" after reading everything else, and/or simply remove any sd cards you might have and follow below directions as normal, and/or go here: http://forum.xda-developers.com/showthread.php?t=292631
linux users: still read everything here, but have a look down at the bottom where it says "HERE IS THE BOTTOM"
for those who don't know this, flashing your phone also performs the same functions a hard reset would. all your previous apps, contacts, registry tweaks, etc will be gone. also, when you flash someone elses custom rom onto your device, keep in mind that they may have cooked in their own apps and registry tweaks.
ok, go ahead and go to this http://rapidshare.com/files/88767429/RUU.zip.html rapidshare link, and download the ruu.zip there. (if this does not work, navigate to \vogue\users on the ftp, and you should find "RUU.zip" there. if not, go to the folder there titled "jim256-jim2561" and you should find "RUU.zip" there.)
if for some reason you are unable to download the ruu from the above link/location, try my ftp dir here: ftp://up.ppcgeeks.com/Vogue/Users/jim256 - jim2561
download whatever rom image you want
if the rom you download is in nbh format (something.nbh), read on and skip step 7.
if the rom you dowloaded is an exe (something.exe), read on and skip steps 5 and 8 (or use winrar or a similar program to extract the .nbh from the .exe)
then, get imcokeman 's latest vogue unlocker tool.
for those who arent sure, you never have to have ActiveSync synchronized for this to work. you just have to have it connected, with ActiveSync recognizing that the device is there and plugged in.
1. backup all contacts/data/etc..
2. ensure your device is connected to your pc via activesync.
3. run imcokeman 's vogue unlocker and follow ALL instructions in the command prompt exactly .
4. once you have booted back up into wm and are connected to activesync again (dont worry about setting up your device again because you're just going to flash it again and erase all that in a second anyway) extract the ruu.zip to somewhere convenient.
5. (FOLLOW THIS STEP ONLY IF THE ROM YOU DOWNLOADED IS AND NBH) stick the rom you downloaded (should be something.nbh -- if the file extension is NOT NBH, stop; this will get you nowhere. as i stated above, roms are device specific, you cannot install another devices rom to your vogue.) into the RUU folder from the rapidshare/ftp link.
6a. (power-camera reset) press and hold both the camera button and the power button (top), and poke the stylus into the reset hole. you should then be presented with the tricolor screen and near the top you should see something like coke 0.4.0 ( if you do not see the coke 0.4.0, then dont bother trying to flash your device. if it does not say coke 0.4.0, the device is not unlocked, and you need to start at step 3 again).
7. (FOLLOW THIS STEP ONLY IF YHE ROM YOU DOWNLOADED IS AN EXECUTABLE). run the exe!
8. (FOLLOW THIS STEP ONLY IF THE ROM YOU DOWNLOADED IS AN NBH) run ROMUpdateUtility.exe in the ruu folder you downloaded and extracted.
9. follow the steps, be patient, be careful, and whala!
10. thank imcokeman and whoever you downloaded your rom image from.
good luck.
also, for all those that keep asking about this and are worried about this, yes, the version discrepancy is completely normal in the ruu before updating. it just means v1 of the cookers rom, so even if it is a version lower than 1.12.651.1, that is ok.
whenever you flash a custom rom, it says whatever they want it so say in the ruu, so even if it doesnt say 1.12.651.1, that doesnt mean that it is downgraded, it is just the version of the custom rom builders rom.
HERE IS THE BOTTOM
ok, for those vista/mac/linux users, there is another method of flashing., courtesy of pnyce777 in post #42 and on. this method is via the sd card. it is not required that you do step one if your card is already fat32. i will update this post as we gain more knowledge
1. Format your MicroSD card to FAT32 (YES - FAT 32 32 32!! not just plain old FAT) (again, this is not required if your card is already fat32; it is ok to have other data on the card). I have read that the card needs to be 2gb or smaller, though I'm not sure how much truth, if any, there is to that...
2. Extract the .NBH you desire to flash from the exe or zip or w/e put it on the microsd card rename it from RUU_signed.nbh to VOGUIMG.NBH
3.Put the MicroSD card in your phone and Get To the BOOTLOADER screen (camer+power+reset) it should then start updating with the .NBH on the SD card and the procedure should begin automatically.
you can also use this procedure to unlock your phone by flashing the .nbh from Cokemans unlocker just extract it and rename it VOGUIMG.NBH or if your stuck at that HTC screen and cant sync because your phone wont boot up.
i will try to provide support on this as i can, but as i have never used this method myself, pnyce777 is probably a far better resource if he is available and willing.
sorry this is now so long, wasnt supposed to be in the first place. but if you're not already used to a lot of reading, this is a good first step, because you will need to be doing a LOT of reading.
----------------------------------
If I've helped you out, $1 would be more than appreciated! donate. thanks
bump for same reason as above.
thanks for the gudie dude
Jim, great how to. As a noob, I have a qstn about different carriers. I just got a VZ touch and want to know which roms are best to use with which carrier? Some roms seem carrier specific... others seem like they will work on anything. How do you tell whats wat? I have been waiting for someone to post a ROM specifically for VZW, but I haven't found it yet.
It might also be helpful to add a glossary. Like I have read how some folks have taken a sprint kitchen moved it to a new directory (?) and merged it to make a verizon kitchen. With that people have flashed their VZ phones but it doesn't seem like something a noob should try
PapaDocta said:
thanks for the gudie dude
Click to expand...
Click to collapse
no problem
insol said:
Jim, great how to. As a noob, I have a qstn about different carriers. I just got a VZ touch and want to know which roms are best to use with which carrier? Some roms seem carrier specific... others seem like they will work on anything. How do you tell whats wat? I have been waiting for someone to post a ROM specifically for VZW, but I haven't found it yet.
It might also be helpful to add a glossary. Like I have read how some folks have taken a sprint kitchen moved it to a new directory (?) and merged it to make a verizon kitchen. With that people have flashed their VZ phones but it doesn't seem like something a noob should try
Click to expand...
Click to collapse
ok. so as for different roms saying they are for different carriers, they are most likely just referring to having the different directories (/folders) for the carriers. so what that means is that a sprint rom would actually work just fine for you, but it may have things like sprint tv or on demand on the cube or other places. it will still function just fine and everything though. it would probably look a little different than the stock vzw rom (im not sure really how it looks) and such. the only way that you could get screwed having the wrong rom for your carrier is if you were flashing the radio as well. but since you're not (in most cases), it doesnt matter really. just be sure to check the roms threads about whether they include a radio or not.
as for the glossary thing, that is probably a great idea. thanks for the tip i will get working on that.
so what you will need to do is:
1) download a kitchen: set of tools for creating/editing roms. dcd just finished his vogue kitchen; available here on xda in this vogue upgrading subforum. there is also lattisimo's older vogue kitchen available on the ftp site over at ppc geeks ("qlinks" at top of page, ftp upload/download, vogue -> users -> lattisimo? (i think?)).
2) download a verizon titan/mogul/ppc 6800 kitchen from somewhere, look in the "sys" folder contained therein, and copy the "carrier vzw" or "verizon" or "carrier customizations - verizon" folder (it will be something like that) into the "sys" folder of the vogue kitchen you have downloaded.
3) delete whichever other carrier customization was already in that folder (such as alltell or sprint or bell etc..)
4) run "buldit.bat" or "buildnb.bat" (or something similar) and flash your new rom that will be located in the "ruu" folder after the batch file (xxx.bat) is finished!
feel free to ask any more questions if that wasnt too clear (sorry :S) .
good luck!
jim256 said:
ok. so as for different roms saying they are for different carriers, they are most likely just referring to having the different directories (/folders) for the carriers. so what that means is that a sprint rom would actually work just fine for you, but it may have things like sprint tv or on demand on the cube or other places. it will still function just fine and everything though. it would probably look a little different than the stock vzw rom (im not sure really how it looks) and such. the only way that you could get screwed having the wrong rom for your carrier is if you were flashing the radio as well. but since you're not (in most cases), it doesnt matter really. just be sure to check the roms threads about whether they include a radio or not.
so what you will need to do [for verizon] is:
1) download a kitchen: set of tools for creating/editing roms. dcd just finished his vogue kitchen; available here on xda in this vogue upgrading subforum. there is also lattisimo's older vogue kitchen available on the ftp site over at ppc geeks ("qlinks" at top of page, ftp upload/download, vogue -> users -> lattisimo? (i think?)).
2) download a verizon titan/mogul/ppc 6800 kitchen from somewhere, look in the "sys" folder contained therein, and copy the "carrier vzw" or "verizon" or "carrier customizations - verizon" folder (it will be something like that) into the "sys" folder of the vogue kitchen you have downloaded.
3) delete whichever other carrier customization was already in that folder (such as alltell or sprint or bell etc..)
4) run "buldit.bat" or "buildnb.bat" (or something similar) and flash your new rom that will be located in the "ruu" folder after the batch file (xxx.bat) is finished!
feel free to ask any more questions if that wasnt too clear (sorry :S) .
good luck!
Click to expand...
Click to collapse
This is great! I will also post it over on PPCgeeks. Huge help for me to get started and hits right at the real bricking fear... if the radio is not in the user-made custom ROM it seems safe... and avoid OEM carrier ROM unless it is for your carrier.
insol said:
This is great! I will also post it over on PPCgeeks. Huge help for me to get started and hits right at the real bricking fear... if the radio is not in the user-made custom ROM it seems safe... and avoid OEM carrier ROM unless it is for your carrier.
Click to expand...
Click to collapse
yep exactly good deal
Thank you for the great guide. flashed my rom for the first(and probably not the last) time last night.
i have a sprint vogue and want to use it for verizon, can someone make me a rom that i can just flash and have it working for verizon? if so thanks, if not can you please tell me what i need to do, thanks!
this should be a sticky!
well it is over at ppcgeeks...
but this isnt the most updated copy though..
thx tho, glad it could help ya
Makavelifaison said:
i have a sprint vogue and want to use it for verizon, can someone make me a rom that i can just flash and have it working for verizon? if so thanks, if not can you please tell me what i need to do, thanks!
Click to expand...
Click to collapse
you will need to exchange that cdma vogue for a gsm model that will work on verizon.
aecabanaboy said:
you will need to exchange that cdma vogue for a gsm model that will work on verizon.
Click to expand...
Click to collapse
Sprint and Verizon are both CDMA.
Makavelifaison said:
i have a sprint vogue and want to use it for verizon, can someone make me a rom that i can just flash and have it working for verizon? if so thanks, if not can you please tell me what i need to do, thanks!
Click to expand...
Click to collapse
You can't just "make" a ROM for a different carrier. The phone itself won't work because it's registered for one comapny.
Great Thread!
Good to see there are some thorough instructions out there for noobs... Howabout an unlocker for Vista 64??? Any advice? Thanks.
Guys... I'll be posting a patched provision tool today soon as I get home.
This tool will not requires that you have a dev unlocked phone.
See you later today...
[Update]
If you have the original files, there is no reason to take the risk on tools that you dont trust. The provision tool has a check validation that only query the WP7 register to see if it is dev unlocked. The provision tool is not obfuscated. So, if you want make it work without risk. Just patch the provision tool and remove the IF() statement where the method private bool IsDevUnlocked() is called and always return true. Just recompile and run it using the same steps provided on PDF and you will be safe with the original update files, backup, and your WP7 will be safe to come back to retails version to allow you update to Mango later this year...
PS: Dont ask in this thread where to find the files... It was already spred over other posts and over internet. Just make sure you are with the original files from MS Connect and you are good to go. And remember, lots of features for consumers are not enabled right now. It is a Dev build.
[Update - Add patched provisioning file]
Ok, since some people asked me to patch the file myself, there is the link to the patched provision tool. Find yourself the other files and follow exactly same steps provided on MS pdf guide except that instead of use the original EXE that comes from MS, use the link instead. THIS PATCH IS PROVIDED AS IS WITHOUT ANY WARRANTY! DO IT AT YOUR OWN RISK! AND DONT FORGOT TO KEEP SAFE YOUR DEVICE BACKUP OTHERWISE YOU WILL BE STUCKED ON BETA ROM FOREVER!!!
I hope all you enjoy it.
the sharing already started
ziggy89 said:
the sharing already started
Click to expand...
Click to collapse
Weird... I dont see anywhere in the forum the provisioning tools... Was thinking on start sharing it...
i'm having dificulties on aproving my account :\
Question: To become a developer you have to pay anything to Microsoft? If not, how to get the beta copy of mango?
sdnsilva said:
Question: To become a developer you have to pay anything to Microsoft? If not, how to get the beta copy of mango?
Click to expand...
Click to collapse
Yes, Microsoft charges a $99 fee to become a developer, unless you are registered with Dreamspark (for students). And I'm not sure where the link is posted, but I think someone has uploaded the files. Try searching Google and XDA.
simply use this: http://windowsphonehacker.com/articles/get_the_mango_update_now._without_being_a_developer.-06-30-11
its easy, creates a backup and was done within 1 hour for me!
Looks like we need a new unlocker ... my previously sideloaded applications got revoked and I have no choice but to uninstall it.
Other than that, it's very significant upgrade to my previous 7392 Focus. Love the Facebook integration (though the chat still unusable)
* Edit : Facebook chat worked. I just realized this after one of my friend chat me.
Sh4wN said:
simply use this: http://windowsphonehacker.com/articles/get_the_mango_update_now._without_being_a_developer.-06-30-11
its easy, creates a backup and was done within 1 hour for me!
Click to expand...
Click to collapse
It creates a backup? From that link you posted:
Keep in mind this tool does not backup your phone
Click to expand...
Click to collapse
Then there is a reference to the tool I made. I guess this is the reason for the renewed interest in the backup tool.
Scratch that, I looked at his bat file and he is using the enablebackup flag and he says in a comment it is new. I guess he hasnt updated his thread.
Sh4wN said:
simply use this: http://windowsphonehacker.com/articles/get_the_mango_update_now._without_being_a_developer.-06-30-11
its easy, creates a backup and was done within 1 hour for me!
Click to expand...
Click to collapse
same here. Non developer HTC surround
Has anyone done this on a device that has been un-Walshed?
is this unlocked ? .. or do we have to start over and do the reg trick to unlock mango ?
I got the following response:
The application cannot be tested for compliance for Windows Phone 7 Application Certification Requirements because it fails to launch on all Windows Phone 7 devices. The application terminates at launch.
However, I tested it on my own device and emulator, it works fine on all of them.
Here is a little background.
My app requires internet to run, if there is no internet for the phone, it will pop a message to let users know that it needs the internet and exit.
Currently, I am supporting both Nodo and Mango. Mango version has been approved already. The nodo version shares most the code of mango with 7.1 related features removed. The mango version has the title of "XXX for mango", and the nodo version has the title of "XXX for nodo". I don't know if this can be the cause of the problem. Can someone please give me some insights on this?
I am fairly certain that you shouldnt be exiting the application like that. Bring them to a screen/page that lets them retry or make the popup let them retry.
I am not sure if that was the problem tho. because my app has been like this since day 1, and mango version was recently certified too.
Well you can try to resubmit and it might pass...contact create.msdn.com support to get more info.
I did, it failed again. The only reason I can think of is that if its not an clean install, meaning update from an existing older version of the app, there might be some issues, since I changed the structure of the storages. but i don't know how to test it.
Maybe request Microsoft to provide some debug information to you?
If you install your previous version (hope you kept your versioning archived somewhere) by deploying to emulator/phone, then deploy the new version, it may act as an upgrade, and you should be able to see what is happening with debugger attached. I haven't released an upgrade to any of my apps, so I'm not too sure on this feature.
If you did change isolated storage (definitions, etc), that may be your problem (serialization/deserialization).
Try the Windows Phone Power Tools from Codeplex, it has options to 'Upgrade': http://wptools.codeplex.com/ and provides a GUI for browsing storage.
There is also an Isolated Storage Explorer as part of the SDK [http://msdn.microsoft.com/en-us/library/hh286408(v=VS.92).aspx] that should allow you to see everything that may have changed between versions.
Please give me a thanks if this was helpful, it will be my first .
I think you really did provide the kind of help I need, but I don't know how to give you a thanks. Thanks!!! ( Not sure if this is what you meant tho)
My problem is that my app needs this type of changes, and I am willing to take the risk of asking users to reinstall it instead of just updating. Should I be able to do it?
blkjack2u said:
Maybe request Microsoft to provide some debug information to you?
If you install your previous version (hope you kept your versioning archived somewhere) by deploying to emulator/phone, then deploy the new version, it may act as an upgrade, and you should be able to see what is happening with debugger attached. I haven't released an upgrade to any of my apps, so I'm not too sure on this feature.
If you did change isolated storage (definitions, etc), that may be your problem (serialization/deserialization).
Try the Windows Phone Power Tools from Codeplex, it has options to 'Upgrade': http://wptools.codeplex.com/ and provides a GUI for browsing storage.
There is also an Isolated Storage Explorer as part of the SDK [http://msdn.microsoft.com/en-us/library/hh286408(v=VS.92).aspx] that should allow you to see everything that may have changed between versions.
Please give me a thanks if this was helpful, it will be my first .
Click to expand...
Click to collapse
I am seeking beta testers to help me locate the problem. If you are interested please reply/PM me with your live id. I will send you an update once the beta test is live. Your help is much appreciated.
sunxin8086 said:
I think you really did provide the kind of help I need, but I don't know how to give you a thanks. Thanks!!! ( Not sure if this is what you meant tho)
My problem is that my app needs this type of changes, and I am willing to take the risk of asking users to reinstall it instead of just updating. Should I be able to do it?
Click to expand...
Click to collapse
I was thinking the 'Thanks' button that is attached to a post; kind of like receiving a badge for helping others.
As a user I'd probably be unhappy if I was asked to have to reinstall, but I guess if the update contains some good stuff and I wouldn't lose data, it isn't too difficult to uninstall/install again and is only a minor inconvenience.
Is there anyway you can code in to convert from previous storage structure to the new one since a standard WP app upgrade preserves the previous version?
I just did. Well, I just used the tool you pointed me. I first installed the old version of the app, open and close it a few times, check the setting file, making sure, it has the old structure, and i "updated" with the newer version, it opens fine, and I check the setting file, the file has the new structure. So it doesn't really prevent the app from launching. So it is not really the problem. Will you be interested in being my beta tester?
btw, i just "thanked" you in both the replies.
blkjack2u said:
I was thinking the 'Thanks' button that is attached to a post; kind of like receiving a badge for helping others.
As a user I'd probably be unhappy if I was asked to have to reinstall, but I guess if the update contains some good stuff and I wouldn't lose data, it isn't too difficult to uninstall/install again and is only a minor inconvenience.
Is there anyway you can code in to convert from previous storage structure to the new one since a standard WP app upgrade preserves the previous version?
Click to expand...
Click to collapse
Are you using dotfuscator or another tool to ofuscate your code?
No I don't, but I probably should. Can I know why you asked?
MJCS said:
Are you using dotfuscator or another tool to ofuscate your code?
Click to expand...
Click to collapse
My app was rejected again. I am running out of ideas what I can do now.
Hello? Anybody still around? I hope so. I need some advice/help. I will bold my questions so they are easier to reference.
I have two identical Lumia 1020’s that I upgraded to Windows 10 using this procedure posted by hikari_calyx https://forum.xda-developers.com/windows-10-mobile/guide-win10-mobile-offline-update-t3527340 and summarized here https://forums.windowscentral.com/windows-10-mobile-how-guides/452310-how-offline-update-unsupported-lumias-8-1-latest-10586-xxx-14393-xxx-15063-xxx-build.html
This procedure got both phones to 10586.107. However, one phone was able to get updates to Redstone automatically. The other is stuck at 10586.107. The stuck phone is my daily driver and the phone that I’d like to be on Redstone. The one that actually made it to Redstone is a spare and has mechanical issues. It was the phone that I upgraded first to familiarize myself with the upgrade process. The phones are identical except the one that fully upgraded does not have an active SIM.
Since the upgrade I’ve been spending many hours in the forums and on youtube looking for reasons why my one phone might not be getting updates and also for ways to force updates. Most posts are very old and maybe I’m late to the party, but I’d like to get this other phone upgraded.
Here’s what I’ve tried:
1) Since the phones are 1020’s I had to modify the “OEMInput.xml” file to get past a bug in the update process. Following this guide https://forum.xda-developers.com/windows-10-mobile/guide-how-to-fix-windows-update- issue-t3697172, I was able to continue getting updates on the one fully upgraded phone. Since I cannot get updates at all on the other phone, I don’t know if this will work for
it yet.
2) I checked that all my registry settings are properly set for my model:
PhoneManufacturer=”MicrosoftMDG”
PhoneManufacturerModelName=”RM-1085_11302”
PhoneModelName=”Lumia 950 XL”
PhoneHardwareVariant=”RM-1085”
I examined the source code for DHTUpgradeAdvisor and I think this is all that should be set.
3) I tried the Windows Insider App, to be sure I’m getting updates but it when I click the “Get preview builds” it throws a Server Error “A connection error prevented us from downloading programs for you. Please check the date/time of your device and its network connection and try again.”
Of course my date time is correct.
I tried reinstalling the Windows Insider App. Same problem.
I did notice a difference between the phones here. When I open the Windows Insider App on the phone that fully upgraded it shows “Go to Settings” instead of “Get Preview Builds”. The phone that fully upgraded has a “Windows Insider Program” link under Settings>Update&Security. The phone that refuses to upgrade does not have this link. The app does not work on either phone. Why is there a difference between the phones here? How can I get the Windows Insider App working again?
4) I’ve tried to add the provisioning for Mobile Enterprise, but I can never get it to show “Enterprise” in the about section. The package does appear in provisioning. I’ve tried multiple .ppkg files. None have worked.
I did see in a post that you must opt out of the Window Insider Program. I’m not sure how to do this since I cannot get into the Windows Insider App. Also it mentions that the SIM should be removed. I did not try this.
Is there a registry setting or something that can be modified to change the update rings or opt out of the insider program? Or does the insider app associate my phone with my Microsoft account and I need to login to my Microsoft account and somehow disassociate it there? Does the SIM really need to be removed?
5) I had the idea to make an image of the fully upgraded phone and then dump it into the non-upgraded phone and then hard reset it and recommission it. I tried to make an image with Windows Phone Internals 2.8. I am able to unlock the bootloader of the upgraded phone but I’m not able to get it into Mass Storage mode in order to make an image. I’m not sure what I’m doing wrong. I have only a basic idea of the phone hardware architecture so I don’t even know what to try next to get an image. Any ideas?
Is this idea even feasible? Is it possible to take an image from one phone and dump it into another effectively cloning the first one? I wasn’t sure if there would be problems with hardware (MAC addresses, etc) mismatches with the software or not. Anyone tried this? Should I pursue this more?
6) The next option is to pump the updates into the phone offline. I am not clear on how to do this. Of course I know how to use iutool (as long as it behaves) since I used it to get the phones to 10586.107.
There is a guide to updating offline here https://forum.xda-developers.com/windows-10/windows-10-mobile/w10m-builds-update-links-collection-cab-t3234805. It looks like this is mostly a guide to capture the cabs for posterity. For upgrading, it’s not clear to me how to begin. There are links to some update cabs in the post, but also this link: https://www.catalog.update.microsoft.com/Search.aspx?q=RM-1085_11302. It has info, but I don’t know what I’m looking at. This is where I get confused. Are these even the cabs I need? Are these update cabs independent of the phone model? Can I just grab the cabs within those links and copy them to my PC and then update my phone using iutool? Do I need to do all the updates in order or can I skip ahead? How do I know which ones I can skip over? What is 000-88 based vs 000-HK based vs CTM-MO based devices? Do I use iutool as I did before (keeping the same files in place and just overwrite the cabs with the new ones)? I see these questions partly answered in the subsequent posts, but I’m still unclear of the cabs to use and the order. This method seem like it’s for people smarter than myself and has a high risk of trial and error and brick potential. I’d rather figure out how to get the proper update pushed over-the-air if possible, but if someone has done this method on a 1020 successfully I might try it.
I would prefer to not have to do hard resets or rollbacks if possible since I feel like I'm very close to getting it to work (It worked on my other phone naturally).
Thank you to anyone who is able to answer any of my questions and give me advice on which of the above methods is best to pursue!
I’ve never posted to a social media site such as this, so if I’ve posted wrongly I apologize.
Your friend,
WolfCobra
If you want to upgrade to higher versions, just go to https://www.wpvision.de/tourniquet and download the "Phone Updater" there. With that you will be able to update any Windows Phone 8.1 up to 15063.297.
You might get into some trouble because you already modified OEMinput.xml. But overall you do not need to do any registry editing to get to build 15063 (Version 1703).
I registered on the wpvision.de site. I am waiting to be accepted for membership so that I can view the posts describing the functionality and operation of the phone updater. I'm not able to access much of the site, so I cannot tell how helpful this will be yet. Thank you for pointing out this site to me; it is one that I have not seen before.
WolfCobra said:
I registered on the wpvision.de site. I am waiting to be accepted for membership so that I can view the posts describing the functionality and operation of the phone updater. I'm not able to access much of the site, so I cannot tell how helpful this will be yet. Thank you for pointing out this site to me; it is one that I have not seen before.
Click to expand...
Click to collapse
I was able to fully update my 1020 with the Phone Updater from wpvision.de. It works very well. I would recommend it to anyone still looking to update an unsupported phone.
WolfCobra said:
I was able to fully update my 1020 with the Phone Updater from wpvision.de. It works very well. I would recommend it to anyone still looking to update an unsupported phone.
Click to expand...
Click to collapse
Can you please provide the linkto the thread?