Related
This is a call to arms for anyone still running 1.5 on their eris. We (developers) need people to capture the update process using wireshark (or an equivalent). This is needed for a new root attempt, but sadly all of the devs have already updated to 2.1 so we can't do this.
First go here and download the RUU:
http://www.pcdphones.com/downloads/Eris%20MR1.zip
Next you need to go to verizon's website and login to your account. Click "Suspend/Resume Service" and suspend your phone. You can resume service on the phone after you are done here with no penalties or charges.
Please follow these directions, taken from the first root thread
bftb0 said:
Steps:
[Binny knows this, but if anyone else is reading, it is the same as a factory reset - you will lose all your settings and apps (but not the contents of the SD card)]
1) Unpack the 1.16.605 RUU - by running it as if you were going to actually do the RUU using the USB cable and your host PC, but stop right before you would apply the update to the phone. Pull the "rom.zip" file out of the temporary area that the RUU installer unpacks.
(Poke around under C:\Documents and Settings\<Username>\??? (I can't remember - you'll see folders with names that look like registry entries). You have to do this while the RUU installer is sitting there waiting for you - if you cancel the install, it will nuke everything it unpacked. I just made copies of the entire subtrees.
2) Cancel the RUU install.
3) Move the ROM.ZIP file to the root folder of your SD card, and rename it PB00IMG.ZIP
4) You can cancel the RUU install session on the PC, and unplug the USB cable if you want (so long as you have a well-charged battery!)
3) Power down the phone, and boot it back up holding the Call and End buttons simultaneously
4) Scroll down (or whatever it asks) to go from Fastboot mode to HBOOT mode
5) The phone will automatically discover the PB00IMG.ZIP file, and unpack it and verify it.
6) It will ask you if you want to install; when you (select and) enter Yes, the phone will reboot, and come up again - appearing as if it is repeating the same thing. This time, however, it won't stop and ask you - it will just begin the install.
7) Wait... Wait... Wait... Wait... and then wait some more. If I recall correctly, it seems to hang a little bit at the HTC splash screen after the reboot. That is normal - just WAIT and let the phone do it's thing.
That's it, except for:
8) You probably will want to dial *228 and choose option 1 to complete the programming of your phone - it will reboot after it completes.
Click to expand...
Click to collapse
After you are done, DO NOT start the OTA update that it prompts you to do.
Now we are going to install wireshark and setup the capture environment:
Download wireshark from http://www.wireshark.org/download.html for your versions of windows
Install it - make sure you also install WinPcap
At this point you should turn off any wireless encryption on your router. I know it's not necessary but it makes it easier to go through the captures.
Setup the wireless on your phone to connect to your wireless router and turn off your mobile data connection.
After you have turned off the wireless security on your router, we are going to start the wireshark capture.
Run wireshark - if you are on vista or windows 7 make sure to run it as an administrator
Click "Capture" then "Interfaces"
Click "options" next to the interface that your computer has an IP for
Make sure to check "Capture packets in promiscuous mode"
In the Capture Filter box, type "host <ip_address>" where <ip_address> is the ip address your router gave your phone
Make sure that "Automatic scrolling in live capture" is checked so you can ensure the capture is working
Click "Start"
At this point, you should browse the web with your phone. You should see lots of stuff scrolling by in the wireshark window.
If there isn't, you messed up something above and should try again.
If there is a lot of stuff scrolling by, continue:
Close the browser
In wireshark, click "Capture" then "Restart"
Reboot your phone
On your phone, go to "Settings" -> "About Phone" -> "Check for Updates" and go through with the OTA update
After the update is done and your phone is rebooted, go to wireshark and click "Capture" -> "Stop"
Then click "File" -> "Save As" and give it a name.
Upload that file to Megaupload, or Mediafire, or some other file sharing site, or any private server that I can get access to.
After you have uploaded the file please message me through the forums with a link to the file.
Thanks a ton.
e-mail me at [email protected] i got my wifes phones todo this to shes still on 1.5
NO need to have a average user do this, guinea pig yourself and roll back down to 1.5 it can and has been done by other devs.
Isn't there a "logcat" line you can run through adb to get the same thing? Like, when the update is available, you can plug your phone into your computer, connect it to terminal using adb and run a logcat to find the address of the update.zip
FireSokar said:
NO need to have a average user do this, guinea pig yourself and roll back down to 1.5 it can and has been done by other devs.
Click to expand...
Click to collapse
You CANNOT downgrade from 2.1 to 1.5.
Videofolife13 said:
Isn't there a "logcat" line you can run through adb to get the same thing? Like, when the update is available, you can plug your phone into your computer, connect it to terminal using adb and run a logcat to find the address of the update.zip
Click to expand...
Click to collapse
We don't need the location of the update file, we need all the extra network traffic that surrounds the OTA process.
Ah. My bad.
We need to know, exactly, how the update process works.
I'm currently working on downgrading 2.1. Will post back a tut if i get it working
Can't we create an AVD to run with a custom rom and use the Eris MR1 ROM to do it?
Scratch that. I don't think AVDs will get OTAs.
zifnab06 said:
Scratch that. I don't think AVDs will get OTAs.
Click to expand...
Click to collapse
Sadly I tried this a while ago when messing around with AVD Skins but wasn't able to figure it out. If anyone can figure it out please let me know how you do it! -_-"
zifnab06 said:
Scratch that. I don't think AVDs will get OTAs.
Click to expand...
Click to collapse
Wait can't you set it to wireless only mode and get the OTA through wireless? (Simulated by your network connection)
nindoja said:
This is a call to arms for anyone still running 1.5 on their eris. We (developers) need people to capture the update process using wireshark (or an equivalent). This is needed for a new root attempt, but sadly all of the devs have already updated to 2.1 so we can't do this.
...
Thanks a ton.
Click to expand...
Click to collapse
No need to go to all that trouble. I've already posted a link to the OTA update (1.16.605.1 -> 1.17.605.1) in this XDA thread a couple of days ago. Just copy n' paste into your browser's URL bar. I'll repeat it here for grins.
https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
(You might get a browser security warning as that server uses the wrong (google.com) cert.)
Let me know if the above link no longer works - I suppose I could repeat the OTA thing - I am not on 2.1
The OTA process drops the downloaded zip file into /cache, and somehow during reboot, it's presence is detected. If it "only" needs to be dropped in there, or there are some other hooks that need to be present at the reboot, I am not sure. I say "only" because that implies that root privilege is needed to do that - or perhaps it is possible to use "fastboot update" after rebooting the phone with $ adb '(sync; reboot -n oem-78)' The OTA zip file is not signed the way the RUU "rom.zip" files are; it uses the same signing methods as app (.apk) files - the SDK "jarsigner" method.
You can unpack the zip file and look at what it does - there is a script at
META-INF/com/google/android/update-script
which controls the update... and there is a binary patch executable included in zip which is called upon to do file-by-file binary patching.
cheers
bftb0
Thanks for the info bftb0, but we aren't looking to snag the OTA file. We are actually trying to see what communication goes on between our phones and the verizon update servers.
FYI,
When you roll back to MR1, the phone seems to have already grabbed and downloaded the OTA update... in less time than it takes to hand-configure the phone. If you want to observe the OTA process via wireless, you need to prevent the phone from having Mobile network access, since that comes up by default after a FR or MRx rom burn.
Here's a long shot. Perform the MR1 rollback inside a cell dead zone, and conduct a MIM attack by setting up a server on the wireless net so the phone downloads a different OTA zip. You control DHCP for WiFi, so you also in principle control the DNS and routing the phone sees via WiFi. In principle, it's not possible because https should prevent Man-In-the-Middle... but if that (Google) server isn't correctly configured, maybe the phone is not really being too careful about certificate problems. (Either that or the Google server is tuning its' responses based on UA strings).
bftb0
bftb0 said:
No need to go to all that trouble. I've already posted a link to the OTA update (1.16.605.1 -> 1.17.605.1) in this XDA thread a couple of days ago. Just copy n' paste into your browser's URL bar. I'll repeat it here for grins.
https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
(You might get a browser security warning as that server uses the wrong (google.com) cert.)
Let me know if the above link no longer works - I suppose I could repeat the OTA thing - I am not on 2.1
The OTA process drops the downloaded zip file into /cache, and somehow during reboot, it's presence is detected. If it "only" needs to be dropped in there, or there are some other hooks that need to be present at the reboot, I am not sure. I say "only" because that implies that root privilege is needed to do that - or perhaps it is possible to use "fastboot update" after rebooting the phone with $ adb '(sync; reboot -n oem-78)' The OTA zip file is not signed the way the RUU "rom.zip" files are; it uses the same signing methods as app (.apk) files - the SDK "jarsigner" method.
You can unpack the zip file and look at what it does - there is a script at
META-INF/com/google/android/update-script
which controls the update... and there is a binary patch executable included in zip which is called upon to do file-by-file binary patching.
cheers
bftb0
Click to expand...
Click to collapse
bftb06: could you please PM me? I am going to trade my phone this week if you understand what I am getting at.
nindoja said:
Thanks for the info bftb0, but we aren't looking to snag the OTA file. We are actually trying to see what communication goes on between our phones and the verizon update servers.
Click to expand...
Click to collapse
Sorry, my bad. I didn't read carefully enough.
I could probably attempt what you are asking for - I am quite familiar with wireshark (and even hardware sniffing of WiFi, so long as you have the right nic), but the fact that the phone seems to go and look for updates immediately after a FR or MRx update means that the "check for updates" thing may not do anything useful for you if there is already an update on the phone waiting to be installed by the time you start pressing menu buttons. (Thus the idea about "do MR1 in a cell dead zone")
Beyond that, there is a possibility that the update app does not do a wildcard host bind() when it sets up the socket when it inquires about updates with the Verizon servers - for instance, MMS service works exactly that way (it will only use the mobile network interface), and precisely so because of security considerations. Do you know whether or not any of the update conversation actually traverses WiFi if the mobile network is turned off?
bftb0
bftb0 said:
Do you know whether or not any of the update conversation actually traverses WiFi if the mobile network is turned off?
bftb0
Click to expand...
Click to collapse
You can force updates to occur over WiFi if the mobile network is turned off. Do you think this would work:
1. on 1.17 do a factory reset but do not activate the phone.
2. Initiate the downgrade process
2a. while downgrading, turn on packet capture
3. When the phone boots back up and wants you to call a number to activate, hang up
I think if you can skip the activation the phone will not have a mobile data connection, which would allow you to turn on wifi and initiate the update process.
Im still on 1.5 PM me and ill help if needed
Do you guys still need this?
I am on Stock 2.1, Rooted
For some unknown reason I have lost ability to go into EPST from phone by ##778 code.
QPST is working in diagnostic mode.
Does anyone know what could have caused this and more importantly how to get it back.
Any suggestions would help.
I have searched many places but did not find answers.
seconded...
EPST works fine on my rooted/2.1 stock phone... not on my wife's. None of the ##xxx codes works.
Weeks after rooting my DInc w/ unrevoked 3.0, I decided it was safe to go ahead and do the same on my wife's phone. It's 2.1 stock, rooted with unrevoked 3.1/CM 2.5.0.x...plus the wifi tether kernel for AP mode wifi. Deleted CityID and installed root apps Ti Backup (full version), IncrediLite, and AdFree (which required manual symlinking /system/etc/hosts --> /data/data/hosts).
That's IT. Her phone is simpler in terms of apps installed. There's very little there that I haven't also done to my own phone... she has HandCent SMS where I don't; rooting method plus clockwork recovery were/are newer, and I never quite got AdFree working on one of the handsets.
I've no idea why this happened to one phone and not the other...I don't understand the where the config files are stored, or how the dialer accesses the 'hidden' menu. Unless I find an informative answer, I'm just going to try unrooting hers & reverting to stock...
figured out a few things
running ASTRO's process manager on my W's rooted phone, I see that dialing ##778 does invoke an instance of EPST... but you don't get the view/edit mode dialogue.
Trying to launch EPST from the ASTRO process mgr ("go to application") gives the view/edit choice, and if you hit edit you are prompted for the password... but after typing in 000000 it just hangs on 'wait while verifying password'
logcat has lots of entries containing 'epst' but I don't know how to interpret them.
I notice that the com.google.android.epst file lives in /data/data, where one has to muck around when getting a hosts file symlinked for AdFree...but I didn't do anything clumsy, and the permissions are rwxr-xr-x which looks right.
That's about as far as I can go. Anyone know what breaks EPST?
QPST workaround...
I guess this problem must be pretty isolated since no one has responded... but fwiw, as OP alluded, Qualcomm's QPST utility offers a workaround if you can't launch EPST from your phone/dialer:
1. Find a copy of QPST 2.7 build 323 (don't ask me where). Install to PC.
2. Install HTC Sync (for drivers), then Connect phone as 'charge only' via USB with debugging enabled.
3. Open Device Manager and look under Ports to find which COM# is the HTC Diagnostic Interface.
4. Launch QPST Configuration applet. Click the Ports tab, then Add New Port. Select the COM port you found in Step 3 from the list at left, then hit OK. Your phone should now show up under the Active Phones tab as FFA/Surf QSD8650 Rev. 2.0. If not, unplug phone, dial ##DIAG#, wait 10s and plug back in as in Step 2.
5. Open the QPST Start Clients menu & choose Service Programming. Select your phone, hit OK, then click 'Read from Phone' button in the resulting window.
6. You now have access to the same configuration items you normally reach via ##778 on your phone. 'Write to Phone' will commit any changes you make, without further warning.
Obviously it is possible to seriously BORK your phone from here, requiring a restore from backup (which you should have before trying this). I take no responsibility for what you do with QPST. I used it only to change the tethering NAI from <number>@dun.vzw3g.com --> <number>@vzw3g.com so I could tether my wife's DINc. via Windows DUN. That worked, but I can't guarantee the results of other edits.
Same issue
Sorry to resurrect an old thread, but I am having nearly the same issue.
When I try to access epst from dialing ##778# on my girlfriends hero nothing happens at all. I ended up adding a shortcut with anycut and now the view or edit menu comes up. When I hit view it just hangs when I hit edit and enter the password it stays on "please wait verifying password". I can get ##data# to work and a few other ##xx# codes to work but I need access to the epst advanced settings.
Any help would be greatly appreciated, I have tried 1.5 stock 2.1 stock Fresh versions 2.1.3 (i think that's right) Fresh 2.3.3 and Damage control 2.09.....
I have qpst and CDMA workshop 2.7 but I know there are more options I need to change to get data on cricket. I don't have the $100 to spend on the new version on CDMA workshop.
Thanks in advance.
When I went and flashed back to Coke .40 (to unlock GPS after letting Verizon customizations run), then a stock 2.x series radio rom for my Sprint Vogue (that I normally run on Verizon), the ERI disappeared! Its completely gone from the system. I look at the system information, and ERI reads "version 0," and when I browse to my /ERI folder, it is empty.
The phone seems to work fine, but I cannot program it via *228 because the ERI is gone! lol
My request is this, can someone with a Sprint Vogue please ##DIAG# and browse to /ERI with Bitpim/QPST and dump the file in ERI and post it here, rared. Trying to manually upload it is my last resort. I tired uploading a Verizon ERI and even a Bell ERI, but the file has different names on each carrier (which I think may be way they won't work).
Unless someone else has ran into this issue (and I've dug on google for the last week finding nothing), I really don't know what else to try. I'm praying that just dumping a stock Sprint ERI will make the phone work like it used to.
And yes, I am 100% sure it is gone, the folder is empty!
http://forum.xda-developers.com/showthread.php?t=377514
Wouldn't you be able to re-flash from the original Sprint RUU update exe file?
Doesn't that restore the vogue to factory?
Or is this a special file that can't be recovered?
If you can PM me on how to recover that ERI via BitPIM or QPST, let me know.
I still have another family member using a Vogue on Sprint service.
see, flashing the original ROM is what got me into this mess in the first place. Even if one of the old factory ROMS has an ERI update, I prob can't use them because the run during the customeization phase, and all the instructions for unlocking a borked Verizon GPS (i converted this phone to verizon) say to not let customizations run. Perhaps I should let the Sprint Customizations run on the GPS ROM?
As for the eri file it's self, gettint to it is pretty easy. Type ##daig#, find the com port that your phone is on in device manager. Open bitpim and for phone settings choose "other" and then select the com port of you Vogue. Then go to view and select "file system". After that you can browse the file system and the ERI is in the /ERI directory. Right click the file (whatever its name might be) and choose to extract it somewhere. Then zip/rar it.
If you could do that for me it'd be awesome. I've been trying to get NuAngel to do it for me, but he's been busy.
Hmmm...
I don't see an ERI on mine either?
Does that get deleted when you flash it to Android maybe?
Only thing I have not tried is re-flashing the original RUU file from Sprint.
I will try that when I get home and see what I can find.
strange. in my device settings, ERI is being reported as verison 0... perhaps I just need to let Sprint customizations run... I need to find my Vouge, I have no clue where I put it last.
I downloaded [OFFICIAL ROM UPDATE] Gingerbread 2.3.3 Update for HTC EVO Shift 4G from here http://forum.xda-developers.com/showthread.php?t=1127499
and I cant figure out how to install it. I put the file in the root file of my sd card then went into bootloader and nothing.
I'm going to ask this, but I'm pretty sure I already know the answer: are you rooted?
If not, and you don't care about root at this time, just go to HTC Software Updates, under Menu, settings, system updates, htc software update, and click check now.
Otherwise, two things disturb me about the link. The size of the file only shows 9.5 mb in the parenthesis next to the file name. It's actually 248 mb. Also, it's not in the correct name format, to just update from the bootloader. It needs to be PG06IMG.zip. But you can't just rename the file in the link above to PG06IMG.zip. It just won't work.
Or just go to shipped roms (shipped-roms.com) and download the latest ruu, and then connect the phone to your computer, and run the exe.
I tried the htc updates in setting and it said there were no updates for my phone. I gave up I found an ruu file and did it like you said and it worked great thanks. I was rooted but i only did it for wireless teather and i never used it so unrooting was not a problem.
By the way i used this ruu http://forum.xda-developers.com/showthread.php?t=1128410 to update and it work great
Hi Everyone,
I just received a brand new ATT Focus from US ( with the SIM unlocking code also ).
The phone is rev 1.3 and running 7392 atm.
Searched and searched on XDA, Google also...couldn't find a definitive answer at all...
What is the easiest/fastest way to get to dev unlocked Mango ?
So far, from what I've read is to revert to 7004-chevron unlock-update NoDo- keep the unlock-update mango ( of course some registry tweaks during the way).
Thanks,
htc9420 said:
So far, from what I've read is to revert to 7004-chevron unlock-update NoDo- keep the unlock-update mango ( of course some registry tweaks during the way).
Click to expand...
Click to collapse
That is the only way except ofc, paying the developer unlock.
OMFG...I'm stuck @ 7008 version. Zune tells me it's the latest update...LOL
this is driving me nuts...can do Silverlight but can't update the freaking phone
htc9420 said:
OMFG...I'm stuck @ 7008 version. Zune tells me it's the latest update...LOL
this is driving me nuts...can do Silverlight but can't update the freaking phone
Click to expand...
Click to collapse
Try on another computer. That solved it for many.
Job done
haha, I wasn't seeing the trees because of the forest.
For anyone that might get interested in this, here are the steps that worked great for me ( didn't put any SIM, nor had the time adjusted):
All info I had maily came from this :
http://forum.xda-developers.com/showthread.php?t=1143999
1. Install/flash 7004. Unlock via chevron. Use any registry editor to erase the values from HKEY_LOCAL_MACHINE > Software > Microsoft > DeviceReg/PortalUrlInt, remove its value data and save it. Do the same with PortalUrlProd
2.Zune upgrade to 7008.
3.Zune upgrade to NODO.
STOP THE UPDATING WHEN DONE otherwise ZUNE will automatically proceed to the last two updates that leads to Mango.
4. Deploy http://forum.xda-developers.com/attachment.php?attachmentid=722646&d=1316284246
5. Deploy http://www.edisk.cz/en/download/38910/New_SMS_unlock.xap_41.01KB.html
6. Make root /provxml. Copy unlock.xml to it.
7. Let Zune do the rest.
In my case, everything worked flawless and updated to the last samsung update: fm 2103.11.8.1; radio: 2103.11.8.1 BL: 5.8.0.2
you forgot to mention that after updating to mango 7720, you need to run the diagnostics app to load the "unlocked" profile. Heres a link to the thread, but this thread i find is unclear;
http://forum.xda-developers.com/showthread.php?p=16809179
What i did was the following AFTER the update to MANGO!
1. Enter the diagnostics terminal by entering "##634#" as a phone number
2. Typed "*#9908#" in the diag. mode, which brought me to the GPRS settings
3. Scrolled through the list of profiles, selected "unlock", clicked "save"
4. now your focus is ready for sideloaded apps!
htc9420 said:
haha, I wasn't seeing the trees because of the forest.
For anyone that might get interested in this, here are the steps that worked great for me ( didn't put any SIM, nor had the time adjusted):
All info I had maily came from this :
http://forum.xda-developers.com/showthread.php?t=1143999
1. Install/flash 7004. Unlock via chevron. Use any registry editor to erase the values from HKEY_LOCAL_MACHINE > Software > Microsoft > DeviceReg/PortalUrlInt, remove its value data and save it. Do the same with PortalUrlProd
2.Zune upgrade to 7008.
3.Zune upgrade to NODO.
STOP THE UPDATING WHEN DONE otherwise ZUNE will automatically proceed to the last two updates that leads to Mango.
4. Deploy http://forum.xda-developers.com/attachment.php?attachmentid=722646&d=1316284246
5. Deploy http://www.edisk.cz/en/download/38910/New_SMS_unlock.xap_41.01KB.html
6. Make root /provxml. Copy unlock.xml to it.
7. Let Zune do the rest.
In my case, everything worked flawless and updated to the last samsung update: fm 2103.11.8.1; radio: 2103.11.8.1 BL: 5.8.0.2
Click to expand...
Click to collapse
Consider me new; can you connect steps 4 and 5 with step 6? 4/5 are each XAP files, what purpose does each serve?
Also (and maybe related), unlock.xml seems to be within one of the linked XAPs if you change it's extension to ZIP. How do I copy it to /provxml? This isn't self evident to me, but maybe it is once in Root Tools? I haven't been in Root Tools yet, but is there somewhere to do step 6 within this and if so, can you summarize where?
Sorry for the many questions, there's a lot of info that's hard to digest on the matter - this is pretty close to being the best (most understandable) step-by-step once the questions I posed are answered. Thanks.
xaeryan said:
Consider me new; can you connect steps 4 and 5 with step 6? 4/5 are each XAP files, what purpose does each serve?
Also (and maybe related), unlock.xml seems to be within one of the linked XAPs if you change it's extension to ZIP. How do I copy it to /provxml? This isn't self evident to me, but maybe it is once in Root Tools? I haven't been in Root Tools yet, but is there somewhere to do step 6 within this and if so, can you summarize where?
Sorry for the many questions, there's a lot of info that's hard to digest on the matter - this is pretty close to being the best (most understandable) step-by-step once the questions I posed are answered. Thanks.
Click to expand...
Click to collapse
When you get to NoDo-cancel search for updates as it will surely get you to Mango without unlock.
Install ''WP7 Root Tools" from the link-yes it is a xap.
Install " New SMS" xap from the link.
Open WP& root tools on phone. Make a provxml folder in root. Navigate to Applications/Install/D19A80F2-..../Install and copy unlock.xml.
Paste unlock.xml inside the previously created PROVXML folder.
Exit.
Go to home screen open Phone.
Go to dialer- dial ##634#. A new program should open.
Type *#9908# and a new dialog comes out.
Choose unlock from the list. Press save. Exit.
Done. Fertig. Listo. Finito.
Hope it's clearer this time. Good luck.
This steps should be posted in a new thread and stickied.. IMO, its really hard to find good collected guide about the focus...
3G not working after Unlock
Hey guys, have you noticed that 3G data doesnt work anymore after loading the unlock.xml profile under Mango? I tried reloading the other presets that were available in the GPRS diag. shell, but my 3G is still knocked out. Any thoughts? I am with Rogers in Canada
htc9420 said:
When you get to NoDo-cancel search for updates as it will surely get you to Mango without unlock.
Install ''WP7 Root Tools" from the link-yes it is a xap.
Install " New SMS" xap from the link.
Open WP& root tools on phone. Make a provxml folder in root. Navigate to Applications/Install/D19A80F2-..../Install and copy unlock.xml.
Paste unlock.xml inside the previously created PROVXML folder.
Exit.
Go to home screen open Phone.
Go to dialer- dial ##634#. A new program should open.
Type *#9908# and a new dialog comes out.
Choose unlock from the list. Press save. Exit.
Done. Fertig. Listo. Finito.
Hope it's clearer this time. Good luck.
Click to expand...
Click to collapse
Yup, it's not much different from your previous steps, but the few bits you added helped make the rest more evident. Danke!
pachuau86 said:
This steps should be posted in a new thread and stickied.. IMO, its really hard to find good collected guide about the focus...
Click to expand...
Click to collapse
Agreed!
---------- Post added at 08:36 PM ---------- Previous post was at 08:29 PM ----------
ssingh819 said:
Hey guys, have you noticed that 3G data doesnt work anymore after loading the unlock.xml profile under Mango? I tried reloading the other presets that were available in the GPRS diag. shell, but my 3G is still knocked out. Any thoughts? I am with Rogers in Canada
Click to expand...
Click to collapse
Look around in the WP7 hacking forum for mango update threads - I remember reading something specific to this very issue - "how to fix 3G after provxml unlock" or similar...
ssingh819 said:
you forgot to mention that after updating to mango 7720, you need to run the diagnostics app to load the "unlocked" profile. Heres a link to the thread, but this thread i find is unclear;
http://forum.xda-developers.com/showthread.php?p=16809179
What i did was the following AFTER the update to MANGO!
1. Enter the diagnostics terminal by entering "##634#" as a phone number
2. Typed "*#9908#" in the diag. mode, which brought me to the GPRS settings
3. Scrolled through the list of profiles, selected "unlock", clicked "save"
4. now your focus is ready for sideloaded apps!
Click to expand...
Click to collapse
Just to confirm, you went through 7392, 7403, and 7720 all BEFORE selecting the unlock profile, right? LOL, I rolled back to Nodo to do this a few days ago, and Zune isn't giving me the option to update anymore, so when (if?) it finally does, I want to make sure I don't screw up and have to roll back again.
Not sure why it continues to tell me no updates are available when I have already gone through the update (using the official process) before, so I know it has been released to me. Perhaps it was only "available" to me briefly before they moved on to a different set of users?
do i have to use the unlock using dialpad BEFORE or AFTER mango update... im in 7392 (i think thats NoDo???) right now, and im confused