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. :/
I am using an HTC Vivid on AT&T that is NOT ROOTED, I fell on my phone and now my screen comes up black (think I broke the LCD). I can still receive calls and I believe messages as my green message light blinks. I need to know if there is a product that will let me view/control the android phone screen on my PC without having to install anything on the phone itself as I can't see anything on the screen so I can backup my SMS messages, apps, etc... before moving to my new phone. Most of the threads I have read point to solutions for ROOTED phones which don't help me.
thanks!
Probably (but probably not worth the trouble)
nnaccmnaes said:
I am using an HTC Vivid on AT&T that is NOT ROOTED, I fell on my phone and now my screen comes up black (think I broke the LCD). I can still receive calls and I believe messages as my green message light blinks. I need to know if there is a product that will let me view/control the android phone screen on my PC without having to install anything on the phone itself as I can't see anything on the screen so I can backup my SMS messages, apps, etc... before moving to my new phone. Most of the threads I have read point to solutions for ROOTED phones which don't help me.
thanks!
Click to expand...
Click to collapse
So if you connect the phone by usb, it's probably asking you if you want to allow it to be mounted on the PC, but you have no way to answer, right? Similarly, no way to get it into adb mode. So those are out.
Even with the screen dead, you should be able to get the phone into fastboot mode (check the forums for the Vivid to find out how, probably involves holding the volume buttons for a while while you reboot). If you then install fastboot on your pc, you should be able to download the whole content of the ROM. Then with some reasonable effort, you should be able to untangle everything and read your messages. It can probably be done under windows, but would be a hell of a lot easier under linux, and it will require linux/android skills/understanding (even under windows). Even with those skills, it's probably going to take a day or so. Without them, far longer (or you could hire a CS student with the right skills for a day, I guess). And on the other hand, if your phone was synched, you're probably going to get a fair bit of it back when you connect the new phone. So is it worth the effort?
Our new app, VMLite VNC Server, should help you to deal with this special situation.
It works on non-rooted devices, basically what you can do is to install the apk from USB connection, and run our desktop program, VMLite Android App Controller to start and stop the app.
This way, you should be able to control and view your phone from a pc.
https://play.google.com/store/apps/details?id=com.vmlite.vncserver&hl=en
Hey guys, let me just start off by saying I have spent almost 8 hours straight today trying to figure this out and dig myself out of a hole I've created for myself, that being said, I'm going to try and be as detailed as possible so you guys know EXACTLY where I am and what I've tried. This post looks long but that's because it is. It's pretty much my entire day's worth of trouble typed out. So just bare with me and see if you guys can help me out here!
I have a T-Mobile Galaxy S4 model: SGH-M919 it has Android 4.4.2. Now on to the problem: I've had this phone for almost a year now and a few months ago I rooted it. Did a simple Youtube tutorial and used Odin to do the work and everything worked out fine. A couple months down the road (yesterday), after using the phone like a teenager, downloading apps and cluttering it up it started to slow down and not run some apps. After thinking about it I decided to factory reset it. All of my contacts, photos, and videos were backed up on Google so I thought "why not?" Well, this is where $#!% hit the fan.. being rooted then factory reset, right before the phone came online it had me answer two questions about the root. Something to the effect of "Do you want to keep root? (This option is not reversible)" I thought since I wasn't using the features I originally rooted the phone for I figured nah just get rid of the root. So the phone did its T-Mobile boot up and started the Initial setup.
Everything up to to this point was fine until I wanted to log in to my Google account during the setup. Please understand that where I am I have full 4G LTE coverage and have access to a pretty fast and sturdy wifi connection. Well, when it came to the google sign in I entered my email and password and it came up with a message reading "Can't Sign in - Can't establish a reliable connection to the server" (believe me i wish that was the only issue) so after reading that, I thought I'd try with my wifi.. nope. Same thing. Since neither my 4g or wifi worked I thought it was Google's servers so I tried again this morning, same thing. (keep in mind at this point i think my phone isn't rooted anymore.) I call the t mobile store and they give me a technical support number, so I call it and I tell them i cant sign into Google. The gentleman told me he cant do anything because he can tell my phones been rooted. Only thing he suggests is to contact Google, well, the customer care number just tells you go to google.com/support and there's nothing there about my problem.
This is where I dig my hole even deeper. I tried another factory reset and up in the top left corner i still see that root text. Even the rooted android symbol pops up before the Samsung logo or t mobile. Since I saw that I thought "ohh it just didn't get unrooted all the way." I look up ways to completely remove a root and a lot of them require plugin your phone into the computer and using Odin to flash a stock firmware on to the device. I went to plug my phone into the usb port but my computer didn't recognize the usb device, having experienced this a long time ago I searched around for the latest Samsung usb drivers and I installed those. Device still isn't recognized. Let me just note before people tell me to use MTP mode or Developer tools> usb debugging or connection mode.. The only thing that happens when plugging my phone via usb is the phone starts charging and my computer makes the trumpet noise like something is plugged in. Other than that, there is NO notification of it being plugged in. The reason i stress this is because I called Samsung technical support at this point and the guy (not gentleman) treated me like a 5 year old and ran me through all of these options after i told him I already did everything he was suggesting, including downloading Samsung Kies 3 and having it install the drivers. It does not pick up the device either.. at this point I looked up ways to remove the root without the computer. I found out you can just go into the root app "SU" or something and theres a remove root option. I jumped on that opportunity and had it removed. I restarted the phone and all the problems still persist, it even still has the root text on the top left when you factory reset it again. However now, even if you factory reset and select the option "keep root," thinking it would bring back the"SU" app it does NOT.
So lets recap. I have a phone that thinks its rooted and even appears rooted to t mobile but doesn't have any of the root apps or privileges or capabilities to fix my Google log in issue (like the host file in filemanager). And I can't re-root to get that app back because none of my 3 usb ports, 3 different usb cables (one being the cord that came with the phone), or any of the ports/cables on someone else's computer will recognize the darn thing to work on that way! I have all these issues that are supposed to fix each other but I can't do any fixing because they cancel each other out too... I'm at a dead end.
In case this isn't the right forum/website/thread/post area etc.. I have this whole message saved in Microsoft Word document so I can repost it anywhere you guys might suggest better results. Any help/advice will be much appreciated.
I've had my Oneplus One since the beginning of 2015, up until now it's been honestly fantastic, with very few issues whatsoever, certainly nothing that has bothered me at any rate. That's up until last night;
My phone was lying on my desk next to me with the screen on updating some applications whilst I was writing on my computer - suddenly, it starts to vibrate, one continuous long note, I naturally picked it up and looked at it, at which point the phone turn itself off in my hand. That was unfortunately the last I ever saw of my phone alive. This happened at about 6PM yesterday evening, since then I've tried everything within my power to get it to work. I can't access the bootloader, in order to get to fastboot (which would allow me to fix all my issues by enabling me to refresh the device), nor can I access my recovery. The phone turns on and displays nothing, it vibrates, but that's it.
The phone was running the latest COS13.1.1 update (X1) which I had flashed the day before, it was running the stock kernel for the ROM, the ROM was however rooted.
I know a fair amount about android, I also know a fair amount about the OPO, to me, I think something about the LOGO partition has gone wrong. The LOHO partition being responsible for the images shown in the bootloader, fastboot, splash screen etc.... I'm just not sure how that would have happened.
Either way, I don't know what to do, the one doesn't register to my computer in fastboot or adb , so both those routes seem closed. I primarily use a Mac for my work, I'm yet to try plugging the phone into a PC.
I've submitted a ticket to OP, and have spoken to an adviser who moved my case to a 'specialist', but I'm yet to hear back on that one.
Any help would be massively useful, because I need this phone for my work, and just general communication.
Thanks for reading,
Ben
Here, try this http://http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
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.