I have been receiving an error code 129 on my Touch Pro 2 (Sprint) for sometime now. I finally brought it into Sprint and they WIPED my phone and said it was a software issue. 3 days later the same error message. I brought it back to Sprint and they gave me a brand new TP2. 4 days later I am still receiving the same error message (on my new phone). I brought it back to Sprint today and low and behold they WIPED my phone again, this time they did not put anything back on it, no contacts, no nothing. When I asked them what was wrong this time they said and I quote "DO NOT SINK IT WITH YOUR PC", HUH seriously, I have a WM phone and a Windows PC and I can't sink my phone. They recommended to put everything back on manually and see if the error happens again.
I am going CRAZY. Anyone ever see this before? Its NOT a text message I am receiving, its an actual ERROR, it appears on the top tool bar as and "!" sigh, when I click on it is says Error 129. When I get the error I can not make calls, send text or get on the Net. I have to reboot my phone to use it. Then when I reboot I have noticed my family gets repeated text messages. And once I get the error it comes back constantly.
Any help would be appreciated. THANK YOU!!
digitalimagecreations said:
I have been receiving an error code 129 on my Touch Pro 2 (Sprint) for sometime now. I finally brought it into Sprint and they WIPED my phone and said it was a software issue. 3 days later the same error message. I brought it back to Sprint and they gave me a brand new TP2. 4 days later I am still receiving the same error message (on my new phone). I brought it back to Sprint today and low and behold they WIPED my phone again, this time they did not put anything back on it, no contacts, no nothing. When I asked them what was wrong this time they said and I quote "DO NOT SINK IT WITH YOUR PC", HUH seriously, I have a WM phone and a Windows PC and I can't sink my phone. They recommended to put everything back on manually and see if the error happens again.
I am going CRAZY. Anyone ever see this before? Its NOT a text message I am receiving, its an actual ERROR, it appears on the top tool bar as and "!" sigh, when I click on it is says Error 129. When I get the error I can not make calls, send text or get on the Net. I have to reboot my phone to use it. Then when I reboot I have noticed my family gets repeated text messages. And once I get the error it comes back constantly.
Any help would be appreciated. THANK YOU!!
Click to expand...
Click to collapse
If you're experiencing the 129 data connection error, try calling advanced tech support and have them rebuild/refresh your network settings and see if it fixes you. I'm baffled as to the why part.
In any case, I found a listing of all the Sprint error codes and what really catches my eye is the fact it says this:
Error Codes - RFC 2002 (129) 129 Administratively Prohibited Mobile should display "Unknown error. Sign in failed. Please try again. If the problem persists, turn your phone off then turn it on again."
Maybe wherever you were with your phone Sprint wasn't letting you use the net at that time.
I also found the following info you may want to try:
Go to www.sprint.com and log in to your account.
Under My Sprint, click on the Settings and Password link.
Under Account Admin Tools, click "wireless web access."
Make sure your phone number IS NOT CHECKED on this page. If it is by chance, your data has been "shut off."
You may want to check it, save it, and then uncheck it. It could cause something to "refresh."
Also, check Settings -> Connections Tab -> connections -> under Sprint click on "Manage existing connections" and make sure your "sprint #777" is there.
If not, settings are as follows:
Name of Connection : Sprint
Model : Cellular LIne
Number to be dialed #777
Username/Password/Domain are blank
Advanced - Use server-assigned IP address is checked (on both tabs)
Use Slip is UNCHECKED
Use Software compression is CHECKED
Use IP Header compress is CHECKED
You need to soft reset after adding.
Other things to try:
Also make sure your data connection is "on" in the comm manager. I know that is a duh, but who knows.
Start > Settings > System Tab > Update Profile
Phone Dialer > Menu > Options > Services tab > Internet > Get Settings
If you're feeling ambitious with that one, you could then initiate custom NAI entry to device (client-initiated IOTA) by taping start.
That's about as much as I could turn up. I hope something works for you.
Ok, now I'm going into my third day with this phone, and I'm really struggling to find a way that it has made me happy. I mean, yeah, I like the OS and all, but Sprint still hasn't gotten back to me on whether they're going to send me a free Airave (I spend half the time in my home roaming). I had to reset the device yesterday to get it to connect to Marketplace - even though my account has never said anything but US (last time I left the country was in the Navy 21 years ago) - and even though I could connect to marketplace on Zune software, my phone wouldn't connect to it. Now I've got that working, by resetting the phone.
Now I can't get the phone unlocked. My developer account has been approved, identity verified, and the next step in my process is unlock my phone. I have tried all the tricks I've found so far: start phone, unlock the lock screen, turned off a bunch of services on my PC (like SQL, IIS, and more), reset my phone again, touch marketplace on the phone while connected so it says "connected" on the screen... Between all this and the lousy reception I get at home, I'm ready to just chuck this thing back at Sprint and say, "Thanks, but no thanks." The one thing keeping me from doing that is that Verizon is going to get the Trophy, and I want a phone with a keyboard. I've had keyboards on all my WinMo phones, and don't plan to stop now. I just wish this phone was available on VZW. I'm going to stick it out as long as I can, but iff I don't have an improved experience by day 28, Sprint gets it back... </rant>
Ok... Have I missed any other steps in getting this phone to connect to the Developer Phone Registration tool?
Have you tried following the directions here:
http://social.msdn.microsoft.com/Fo...s/thread/bfa70370-4926-4086-ad0e-febe716b8bf0
Yes, many times.... I never get past step 4.
Someone just told me an another thread that you have to be verfied through GeoTrust and to do that you must first create and submit an app that you have developed.
After you submit the app, supposedly GeoTrust will contact you via email and have you verify some personal information.
Make a fake app. That's all you have to do. Make one, then submit it. This will generate a claim number with GeoTrust. Trust me, I had to do this myself...
Have you got your certificate from msdn yet it takes a couple of days, once you get your certificate your account will be unloced
thealanshow said:
Make a fake app. That's all you have to do. Make one, then submit it. This will generate a claim number with GeoTrust. Trust me, I had to do this myself...
Click to expand...
Click to collapse
I just finished this. Hopefully by monday all will be well
My account has already cleared GeoTrust, and the next step is to unlock my phone. I'm not a student, but it wouldn't matter - I can't get that far. The reg tool doesn't even detect my phone.
If you're getting the dreaded "Check that the Zune software is running blah blah blah" message, this one is a PITA to deal with. From what I've seen poking around on the interwebs, it's hitting a good number of people. It happened to me too.
I have 2 systems that are identical hardware wise, and running 64 bit OSes.
I have 1 machine running a 32 bit OS (it's a much older system).
I was finally able to unlock the phone without any issues at all on the 32 bit system (after swapping out my phone and nearly a week of struggling with it) the very first time I tried.
I'm loving the phone, especially with it being unlocked, but it was a fight until I tried it on that last machine.
Poke Microsoft about it. The more they hear about it and the more information they get about it the faster they'll be able to fix it (that assumes the problem is even on their end).
I've heard using a USB hub (or if you're already using one then NOT using it) has helped some people. *shrug*
Thanks for all the suggestions - I appreciate them. I have yet to get my phone to get past the check zune... blah blah blah error, with the exception of one time. Here's what I did...
I reset my phone, got past the intro, added my live account, hooked it to the computer, let it sync with Zune (I had deleted the phone's proflie), opened the reg tool, and it found the phone. I entered my login info, and got the dreaded 0x64 error having to do with time on the phone.
Several posts I found had to do with people getting past this by using a different internet connection and finding success. Well, I have a rather odd internet connection going on. I live right behind my church, just beyond wireless range from the pastor's router. So here's what I have:
Scientific Atlanta DSL modem/router combo - pastor's connection
Buffalo high powered router running DD-WRT sitting on the platform (closest part of the building to my house), repeating the pastor's signal.
Buffalo high powered router running DD-WRT sitting in my computer room, repeating wireless to my house, and serving as wired router to the server and the HTPC.
Pastor's is 192.168.1.1, the one on the platform is 192.168.2.1, and the one in my house is 192.168.3.1, so they are all separate networks, each using the one upstream of it as a gateway.
So, given my success connecting to the phone, I walked over to church, phone still connected to the computer, connected to the pastor's router, and by this point in time, I can no longer connect to the phone.
I suspect that there is some update that Sprint is pushing that causes this problem, so I repeated the process several times, each time deleting the Zune profile, resetting the phone, going through enough of the startup to get to the settings, and putting it in airplane mode, then connecting in the specified order, allowing the new profile to be created, and still failing to connect to the phone from the reg tool.
Over on the App Hub forums, there are several of us with this problem, and a Microsoft team member said that they believe that it is something specific about the Sprint Arrive, and they are looking into it.
My main gripe about this whole thing is that since Sprint is a latecomer to the game, all the posts I'm finding about this are like six months old. Many people have overcome this problem, so you'd think that Microsoft would have figured out the problem by now, and fixed it.
I hope to get this figured out soon, as I am presently unemployed, and spent my $99 to join the App Hub, hoping to make a bit of money there until I get a job. I'm working on something, but until my phone is unlocked, I can't put my confidence in testing solely with the emulator.
Thanks for the tips guys. I do appreciate it.
I've heard really good things about the HTC arrive, I hope it works out for you. Who knows, it could be something NoDo related (because to the best of my knowledge those phones come with NoDo stocked on). I kinda hope it is, it would take the sting out of the fact that so many of us can't our hands on that update! haha ;-)
Yes, it does come with NoDo. It's interesting, takes a bit of getting used to, but it seems to work well. I love the phone. It feels more solid than my TP2. The only thing is that I wish the screen tilt wasn't spring-loaded. I got used to not using it most of the time on my TP2, so it's taking some getting used to on here.
Oh, frustration of all frustrations! I just grabbed my wife's phone and tried it for kicks. It took me all of 15 seconds to unlock her Sprint Arrive. So I know the problem isn't my computer. WHY WON'T MY PHONE WORK?????
(oh, and if it makes any difference, she's installed WAY more apps than I have)
did you try going to msdn?
My MSDN subscription has expired, but I have posted on App Hub forums. MS thinks it is something specific to the Sprint Arrive, but who knows?
If anyone else has had this problem, there is an official workaround posted on AppHub, but for those who don't have access to that forum, here's the copy/paste:
Re: Cannot register developer phone (HTC Arrive)
Reply Quote
Hi Folks,
There is now an understood issue with respect to the HTC Arrive that may be the cause of your problem. It can affect both developer unlock as well as the ability to update the phone. A KB article is in the works but here is the gist of it for developers having trouble unlocking the phone:
Windows Phone 7 Developer Unlock Tool cannot detect the HTC Arrive Phone
Abstract:
This article applies to developers of Windows Phone 7 applications who are testing their application using the Sprint HTC Arrive, model number PC93100, OS build 7389 or 7390. Developers may find that they are unable to unlock the Sprint HTC Arrive phone using the Windows Phone Developer Unlock Tool, for the purpose of deploying their applications to the phone for testing. This article offers a remedy.
Symptoms
The developer completes these steps to register the phone:
1. Registers through the App Hub as per the steps described in the App Hub registration walkthrough here.
2. Downloads and successfully install the latest version of the Windows Phone Developer Tools.
3. Owns an activated Sprint Arrive in which they personalize their settings (including date and time, and selecting a language).
4. Registers the Sprint Arrive with the same Live account they used in the app hub registration.
Next, the developer follows these steps for Developer specific registration:
5. Connects the Sprint Arrive to the developer's PC with the USB cable included with their device.
6. Ensures that the Zune software is running/open.
7. Launches the Windows Phone Developer Registration Tool.
8. The registration tool ultimately fails to detect the phone upon launch, reporting the following message:
"Unable to connect to phone. Please check that the Zune software is running and that the Zune's sync partnership with your phone has been established."
Cause
This occurs due to a specific state setting in the HTC Arrive that results in the phone not being able to make a desktop passthrough connection. This state condition can be mitigated by following the steps below.
Resolution
Use the following workaround.
1. If connected, unplug the phone device from the computer.
On the phone device:
2. Press the Windows button.
3. Press the right arrow button (on the top right of the screen) or swipe from right to left to expose the application list
4. Scroll to and select “Settings”.
5. Scroll to and select “Cellular”.
6. Select “Change Network Profile” and wait for this operation to complete (<-- this is a key step; you don't need to actually change it).
7. Press the Back or Windows key to exit the “Settings” menu.
After completing the above steps, follow through with the registration process:
8. Connect the Sprint Arrive to the development PC with the USB cable included with the phone device.
9. Launch the Windows Phone Developer Registration Tool (Zune software must be running).
10. The window titled "Windows Phone Developer Registration" appears which establishes a connection to the phone device and the following status message: "Status: Phone ready. Please enter your Windows Live ID and password and click Register to begin".
11. Enter the App Hub registered Windows Live ID and password, and then press the "Register" button.
12. The following status message appears in the window:
Status: Your phone has successfully been registered.
Click to expand...
Click to collapse
Thank you hopmedic that fixed it for me
this was driving me nuts and the info here solved it thanks
Thanks it worked.
Done the workaround, but nothing for me, still have the 0x64 error.
My phone was relocked after one year of AppHub. But now I can't unlock it again..
Also tried to deelete the phone in the device list on my account and use a proxy VPN network. I'm ttired of this. :/
Hi there,
Here's the thing, After updating to MM my phone started with issues like no working home button, no status bar... etc.
So decided to make a factory reset using fastboot, but when google account verification came up I realized i didn't remember my google account pass, so i touched the "change pass" button and changed it using the phone.
But then, when trying to log in, an android alert came up telling something like,
"You should sign in with an actual phone owner's account"
Could you give a solution for this?
Do i have to wait 24hs as some sites say or the only way to access my phone now is flashing the whole ROM again?
I've got bootloader locked and is obviously not rooted.
Please Help me!!
Regards.
******************************************
Edit: Seems there's no fu*** option rather than "cool-down" wait. (Not clearly whether is 24 or 72 hours)
Thanks google indeed, not implementing apple kinda things was clearly why i did preferred your devices & s/w instead of theirs.
Edit2: Lock out is of 24 hours right now!
Sources:
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750/page73
http://www.androidpolice.com/2015/0...ne-you-might-trip-a-72-hour-security-lockout/
http://www.pcnexus.net/2015/12/what...gle-72-hour-lockout-android-lollipop.html?m=1
Little bit of background first...
Finally got my parents (senior citizens) into the smartphone era after StraightTalk starting doing BYOP and I'd had good service so far, but rather than use his old HTC phone which badly needed replacing, he opted to buy the Huawei Sensa (H710VL) branded by TRACFONE and with service via StraightTalk. Fast forward several months, and the old man has discovered a deal for senior citizens from T-Mobile that he likes better, and has opted to switch carriers. Well, he tried to do BYOP with TMOUS and just continue using the H710VL which he likes, but was informed that they wouldn't unlock the phone for another month because they won't do so until you've had it for a year. So therein came my opportunity to promise something I apparently cannot deliver (I told him I'd take the phone home and unlock it for him)!) He (wisely) decided not to wait for me, and went ahead and bought a new phone from TMOUS so he could initiate his new service with them without delay. But I still want to unlock this phone for him, if at all possible!
Fast-forward a few more days--well, I've been screwing around with this phone in the evenings for the past three days, trying to get the bootloader unlocked, and I'm at an impasse. First I had to tangle with the Google account verification, which wouldn't let me even sign into the phone after boot and get to the home screen because I had done a hard reset of the phone first, and didn't have the old man's Google account and password with which to sign back in. Fortunately, intrepid folks who came before me already found a way around that first hurdle. I took the following steps:
1. Went thru HWStartupGuide process until I was able to connect to my home WiFi network. So, internet connection is established.
2. Backed out of there to get to the first setup screen after the TRACFONE splash screen on boot, and used the "emergency calls only" escape hatch to navigate to the stock dialer app.
3. In stock dialer app, entered (without the quotation marks) "*#*#6130#*#*" which took me to the SIM Card Settings screen. Tapped three-dot menu, tapped, "Add SIM Contact," which took me to the native Huawei Contacts app. In Contacts app for the SIM card, tapped "Add Contact," made dummy contact called "Test" with a ph# of 1234. From list of contacts, tapped the "message" bubble icon next to the new "Test" contact, which opened the stock Messages app.
4. In stock Messages app, typed and sent message with the text "www.youtube.com." For obvious reasons the message doesn't send, but it does appear in the messages window, which renders the draft text's content into a hyperlink to YouTube. Bingo! Tapped link and opened up the YouTube app.
5. From the YouTube app, tapped the three-dot menu again, and tapped Privacy Policy from there. Now I'm into Chrome! Opened Chrome without signing in, and navigated to Google.com.
6. From Google.com, searched and then downloaded apk for Test DPC app. Installed Test DPC and set myself up as the new device owner.
7. Now that I'm the device owner, you'd think it would bypass the Google account verification requirement in HWStartupGuide, but no dice. So, rebooted, took same steps to get back into Chrome. From Chrome, I was able to get to the stock Google device search and navigate to the Settings app.
8. From device Settings app, changed settings to allow installations from unknown sources, then I set the option to allow USB debugging, and opened up the dev options to select "Allow OEM Unlock" in preparation for unlocking the locked bootloader, using the unlock code previously sourced from the official Huawei EMUI unlock code site.
So, to sum up, I've got access to the device in general, can use the web and all the apps on the device, and was thus finally able to disable HWStartupGuide to prevent the previous headache from cropping up again. Here's where the impasse starts.
I have Android SDK and everything I need on my laptop (to the best of my knowledge) to facilitate unlocking, flashing, and all the other fun stuff we love to do with our phones.
I was able to confirm the USB and Android drivers are correct and working fine, as I got both fastboot and adb to recognize and list the device when connected via USB cable to the laptop, and it worked both in command prompt and in PowerShell. Fastboot and ADB commands appear to work when facilitated and entered correctly. That is...UNTIL I tried to use the "fastboot oem unlock <unlock code here>" command. It just says "FAILED" with no error code. I tried this from my stock boot options screen (the screen you get when you boot or restart with power and vol-down pressed), and from the stock recovery screen, both to no avail.
This is where I'm all twisted up. There either doesn't appear to be a true bootloader screen to navigate to, or it's purposefully inaccessible, and I don't know how to get to it. If you do a "adb reboot bootloader" command, it just reboots the phone to Android home screen. The only options from the boot options screen are "Power (turn phone off), "Start" (boot to Android home screen), "bar codes" (screen that shows bar codes for the phone's IMEI, Serial #, etc), and "reboot recovery" (stock EMUI recovery screen), where the only options are 'Wipe/Factory Data Reset," "Wipe Cache," and "Reboot."
I feel like if I could get to a true bootloader screen that allows me to enter adb or fastboot command strings in such fashion that you can enter it and then see the process play out on your device screen, then the unlock code from Huawei would probably work and the bootloader would be unlocked, thereby allowing me to root and flash a better ROM, or at least eliminate bloatware and optimize the device for performance. But for whatever reason, and I assume it's purposeful on the part of TRACFONE/StraightTalk, tbh, there isn't a fastboot-capable bootloader screen like my years of using HTC phones taught me to take for granted.
So there I be...stuck, even WITH the unlock code from Huawei! What a crock! I know TMOUS will apparently unlock it in a month or so, but to me, that's not the point. I should be able to accomplish it on my own with the unlock code I got from Huawei. And that's why I'm throwing my hands up and begging for help.
Is there anything else I can try? Is there any other devious way to perhaps flash a different bootloader interface onto the phone that would allow me to use fastboot commands properly? Is it possible to mount the SD card from bootloader and push an apk to it that would install some kind of generic bootloader screen? I'm now a little out of my league, but I am willing to try just about anything that anyone thinks might work. Any advice or suggestions warmly welcomed...not worried about bricking the phone or anything, as it's not much better than a paperweight in its current form anyway.
Thanks!!
smb282
Hey there forums.
I've been an active browser of XDA but never really created an account but I've done so to have assistance with a particular situation with my device.
So the other week, i had spent 150 dollars on a Sony Xperia XA F3115 from Vodafone, Australia and it turns out that the bootloader was locked because of Vodafone and i wasn't going to pay 50 dollars to unlock it. I alternated and browsed the internet (Mostly XDA but other sources aswell) to figure out if there were any methods of bypassing this, whether it be easy or not - I was willing to try anything that seemed like it had a chance to work, without a 100% failure rate. Reading responses to particular methods, i was drawn into one method of just reflashing the stock firmware onto the device and then rooting, flashing and doing everything from there (as the device was no longer locked by Vodafone at that point).
I have completed this task as of this morning, and the device booted successfully. As soon as i unlocked my device, i had received the general android setup window but half way through, i got spammed with "Name has stopped responding" countless times to the point where the phone was literally unusable, it would just pop up again right after closing it - So i decided to restart the device. This was probably a big mistake, it booted fine but it said "Android is updating" and had the whole "Applications updating 100 out of 255" stuff happening. Then it booted to the lock screen, which i had previously setup before i flashed the device which didn't really surprise me too much.
Then it rebooted. Now every single time i boot the device, it reboots to the "Optimizing apps blah out of blah" and then will reboot upon the notification bar popping up, but no lock screen. I decided that my best cause of action was to download another firmware and try that one instead, but I'm unable to boot my device into bootloader mode as it's impossible to happen. I turn off my device, plug it in and hold the volume down button but it refuses to work anymore.
Now that the situation has been explained, I'd really like your help to see if i can have this resolved. I'm baffled as to why Vodafone even locked it to begin with, since the phone was prepaid and had nothing to do with any sort of plans - nor was it even available as a plan. I don't have the money to buy a new phone, and they have already denied me a refund. I need this phone for work and the mistakes i made were stupid - Please, i need assistance. You're all hopefully more tech savvy than i am in the field of mobile phones.