Any way to do this?? on the Dinc, if you ended the *22899 call three times it let you bypass activation.... no such luck on the Rezound? anyone know the right method?
Edit: nevermind. just boot the phone without the SIM card.
Another thing to try would be to gain temp root with zergroot, and edit the build.prop to not require setup.
n00b question: What is the benefit of skipping the activation screen? Something to do with rooting/modding later on?
I think I'm going to get this phone as my first smartphone and all of this stuff is new to me so I don't want to screw anything up.
Well it allows you to play with the phone before it gets activated. Also, it would allow me to play with it before my number gets ported from us cellular because that will occur during the activating of my rezound next week.
Just wanted to confirm that if I don't install the SIM card I should be able to use the phone on wifi only. Currently deployed so can't activate the phone until I get back to the states.
I think if you tap on the four corners starting with the top left and going clockwise, it exits the activation, but am not sure if this is the case with the resound.
Sent from my NookColor
Thats how I did it on my OG Droid but I don't think it works on the Rezound.
Update: Got my phone today and without the sim inserted nothing had to be done to use the phone. It went through the inital setup and then to the homescreen.
you can just like hit the home button like a **** load of times. that usally does the trick
Related
Hey all I was given an Eris by a friend so I rooted it easy enough at 1.5 last August. Since then I have had a few different custom roms loaded and everyone of them that I tried to activate the phone on didn't work. This phone was not activated when I rooted it, and I have to take it to my local verizon shop to have them try to activate it after they deactivate my moto droid 1. I' ve been digging for awhile now trying to figure out if it's the baseband version or what. Can someone please help if at all possible.
Current phone info:
Firmware: 2.1
Baseband: 2.42.01.04.27
Kernel: 2.6.29,
Build: 2.36.605.1 case release-keys
Software 2.36.605.1
Browser WebKit 3.1
PRI: 2.11_002
PRL: 58003
ERI: 5
When the phone boots it shows the verizon logo which doesn't completely mean the radio is flashed for versions network, but I have no idea how to tell otherwise.
Thanks.
If you activate the phone with a stock, or near-stock ROM (let's say Ivanmmj's "Official 1.0"), then thereafter, nothing you do to the phone with dev ROMs from this site will change the phone's activation data (stored in the phone) afterward - not flashing a different radio, nor performing a "wipe/factory reset" (in Amon_RA), nor installing a different ROM will change that.
When it comes to deactivating the phone - or more precisely, clearing the activation state of the phone, the only thing that seems to accomplish that is one of the factory recoveries - Amon_RA does not touch it. This happens if you perform a "factory reset" in the regular OS, which actually causes a boot to the recovery, which does all the "dirty work". You can also manually boot the stock recovery, and use the wipe menu to achieve the same result.
You can see that this makes de-activation inconvenient for rooters - but most of them don't need to do that.
So I'm reluctant to conclude that the radio firmware is affecting your result.
What happens when you try dialing *228 option 1? The call goes through, but you get an error voice announcement after some delay?
I was under the impression that people that flip back and forth between two phones on the same service don't ever bother to de-activate the phone in use: they just make sure that current phone is turned off before they attempt to activate the next phone.
I suppose you could restore the phone back to complete stock (including the stock recovery) before activating it, and then re-root it and reload a nandroid backup... but that's sort of a pain in the neck if this is something you plan on doing regularly.
bftb0
PS I could swear I have activated my phone (*228 option 1) with a dev ROM on the phone, but don't remember the specific details.
First off thanks for the quick reply. I've been researching this whole time and when I dial *228 I don't even get prompt to pick an option. This tells me that somehow the radio itself is possible damaged. Is there anyway a rom could damage it? I ask knowing it's highly unlikely... I know the phone worked fine up to the release of the droid x when the friend upgraded to it. And all I've done is rooted and flashed, so I'm curious, can I test the radio at all?
Thanks.
RnkG said:
First off thanks for the quick reply. I've been researching this whole time and when I dial *228 I don't even get prompt to pick an option. This tells me that somehow the radio itself is possible damaged. Is there anyway a rom could damage it? I ask knowing it's highly unlikely... I know the phone worked fine up to the release of the droid x when the friend upgraded to it. And all I've done is rooted and flashed, so I'm curious, can I test the radio at all?
Thanks.
Click to expand...
Click to collapse
I just re-read your initial post and actually can't tell if the phone has ever been successfully activated since you received it. You mentioned taking it in to the Verizon store, but you didn't say what the outcome was - was the Verizon store unable to activate it?
Normally when you dial *228 it just sounds like a normal voice call - you hear audio, the recorded lady's voice provides a menu, etc. Since that needs to happen in order to activate the phone, it is fairly obvious that the cellular radio must be working completely for that to happen - so the fact that you don't hear any audio seems to indicate something is wrong.
Why don't you try and reflash the phone back to stock using the download from this thread which also flashes the radio:
[ROM][10/20/2010]FlashBack21 v1 -Return to Factory Stock - UPDATED
And see if that gets you any different result. That would eliminate any effect of "dev" software, and also reflashes the radio with the July 2010 version - the last one officially shipped by VZW/HTC for the Eris. If you can't get audio (and you are sure from playing music that there isn't a speaker problem), that would point to a hardware problem.
BTW - even if the phone is working completely, VZW needs to already be aware that it's ESN/MEID is associated to your account, and I think that your other phone needs to be turned off at the time you attempt activation.
cheers
Thanks again. I'll work through that and then post back here.
Thanks again!
So I followed the simple to use guide as directed and everything flashed just fine. When when I got to the activate screen I tried to activate and when it dialed the number I hear nothing. So I turned the speaker on and hit number on the dial pad to make sure the volume is working and it appears to, but it doesn't make the ringing sound when you normally call a number. Soooooo as a desperate act to see if the radio was working what so ever I did something crazy... dialed 911, and I heard it ring one time, then hung up and pulled the battery. So i think the radio works fine in it, I'm going to go to the verizon store and have them try and activate it again.
Thanks a million for all of your help! I really, really appreciate it!
Update:
Just got back from the verizon store. They maunally activated the phone and still no connection to the network. What I don't understand is how when I dialed 911 it rang but nothing else will. Could verizon be blocking this phone?
RnkG said:
So I followed the simple to use guide as directed and everything flashed just fine. When when I got to the activate screen I tried to activate and when it dialed the number I hear nothing. So I turned the speaker on and hit number on the dial pad to make sure the volume is working and it appears to, but it doesn't make the ringing sound when you normally call a number. Soooooo as a desperate act to see if the radio was working what so ever I did something crazy... dialed 911, and I heard it ring one time, then hung up and pulled the battery. So i think the radio works fine in it, I'm going to go to the verizon store and have them try and activate it again.
Thanks a million for all of your help! I really, really appreciate it!
Update:
Just got back from the verizon store. They maunally activated the phone and still no connection to the network. What I don't understand is how when I dialed 911 it rang but nothing else will. Could verizon be blocking this phone?
Click to expand...
Click to collapse
If they activated it I don't know how they could be blocking it. I would've checked to see if it was working before I left the store, and when it wasn't, would've brought this issue up with them.
Are you just going by their word that they activated it, or is there some other way you can tell that it's activated, even though you're not getting any service? What I mean is, if you're not getting any service, how can you be sure they activated it successfully?
RnkG said:
Update:
Just got back from the verizon store. They maunally activated the phone and still no connection to the network. What I don't understand is how when I dialed 911 it rang but nothing else will. Could verizon be blocking this phone?
Click to expand...
Click to collapse
Other than bad hardware, the only thing which would cause this problem would be a "blacklisted ESN" - that would usually be a stolen phone, or a phone that was on a Verizon account that was abandoned by the subscriber with an unpaid balance. (Verizon doesn't want customers who cheat them to continue to cheat them by habitually opening new accounts under assumed identities, so they just blacklist the ESNs of phones that were used on abandoned accounts with unpaid balances)
Verizon won't activate phones with blacklisted ESNs - but if you walked in the phone store and asked them to activate it for you, I would presume that they would have told you straight up "We can't/won't activate this phone".
The radio does not use a separate technology for 911 calls, so, yeah - there is something odd going on here. Perhaps you had a "green" VZW customer assistant that isn't familiar with what happens when someone wants to activate a blacklisted phone, and simply didn't take notice when "something unusual" popped up on the computer they used to enter in your activation request.
You've got stock software on the phone now, so I wouldn't hesitate to pick their brains about it. Telling a VZW tech about the 911 call might convince them a little better - but just remember that you are admitting to a criminal activity (calling 911 without due cause).
Also - bear in mind that by law (in the US) every cell phone has an aGPS unit in it, precisely for the purpose of emergency services locating a cellular handset when the user is incapacitated. ( There is a small risk that if you make a 911 call, cops will end up at your door even if you hang up.)
Okay so I just got this phone 2 days ago. I was waiting for the unlock code and I decided to stupidly try to root it first. Anyway so I was about 1/2 way through with the root process and I misunderstood some steps but before I could finish my code came through.
I kinda had to jump through some hoops (had to go into phone to punch in 2945#*500# and then the unlock code) but the process seemed to succeed. I should mention, it was having trouble with my sim card (Which was not the same carrier[Sim is Fido .. the phone is for Koodo]) with force closes of the phone while hte sim was in, so I turned it on and unlocked it without the sim in.
Anyway so now when I turn on the phone, the phone process just force closes everytime and it pretty much makes the phone unusable with the force close of the phone popping up every few seconds.
Does anyone know how to fix this? I think the problem could be caused by the fact that I was running the 2.2 Telus firmware during the process of unlocking (I couldn't find a 2.2 firmware for Koodo) ... it's back to koodo again tho but it's still like that ... I've flashed it back using KDZ.
Okay some things that might help...
I just popped in the Koodo sim to see if it does anything (it's deactivated tho) ... the phone app doesn't force close ...
Also I noticed something a little peculiar about the sim cards. My fido one has a larger gold surface area and the koodo sim has a smaller one. I've added a photo to compare .. the contacts seem to line up just fine but maybe there's a difference?
Okay I should probably get some sleep cuz this is absolutely driving me nuts lol.
Anyway I just remembered I had a Tmobile simcard still lying around from my vacation to the US last year. So I went ahead and popped it in. no force closes ...
So I think it's probably my Fido simcard is too old? I've tried cleaning it with some alcohol.
Uhh, you can try doing a factory reset (deletes stuff).
home + vol. down + power when powering on.
EDIT: Also, you don't need root to unlock a phone
yea I've tried multiple factory resets
(soft, hard) with the sim and without it ... no dice.
I was just rooting it to install a custom kernel and see how the phone works when it's OCed. I wished it was possible to unlock by the rooting it
edit: I guess I should also mention, the fido sim works just fine in my Motorola Milestone *shrug*
So I've pretty much confirmed for some reason my Fido sim can't be read. I just popped in a friend's Roger's sim card .. and it works fine. I made a phone to confirm as well.
I have been running custom roms on my droid since the root explot was first discovered, and I have a rooted xoom as well. Last night I rooted my thunderbolt and installed the debloated rom. I don't think it is even related to my problem, as it still worked fine after doing this, but I thought it was worth mentioning. I removed the sim card today, just to prove to my brother that it did indeed have a sim, and after reinsertation, my thunderbolt has not been able to connect to a data network. I do not live in a 4g area, and I have tried reseating the sim several times. I can make phone calls, wifi works fine, but I cannot get the 3g icon, and the browser won't load if not on wifi.. I'm starting to get scared. I can't think of anything else to try. Any suggestions?
EDIT 1: I have intermittent 1x data, but I never get 3g. And when I say intermittent, I mean I get it like right after a call for maybe a minute, then it goes away.
Sent from my Xoom using XDA Premium App
I had this same issue as well when I removed and reinserted my SIM card. When I booted back up I was stuck on 1xRTT. After making a call, they phone locked back on to LTE and everything was good after that. If it still isn't working I would recommend giving Verizon a call. They may be able to reactivate it. I did notice that the problem persisted even though I flashed a couple different roms on the device. I'm thinking it probably isn't a great idea to remove and insert the SIM if you don't have to.
Just an update,
I spent 2.5 hours at the effing verizon store today after spending an hour on the phone. Even after all that time, and giving me a new SIM, they STILL couldn't get my TB to connect to 3g. They said that it might magically start working at midnight for no particular reason, but had no clue what to do (I was actually at a corporate store btw) If it doesnt start working tonight, I am going back tomorrow. I have no idea what the hell is up. I am very tech savvy, and this is just insane. It must be a verizon problem in my area that it wont let the phone reactivate for the 3g/4g
I pre-ordered this phone and received it on 5/24 - I've been using it around the house on Wi-Fi to check email/internet, etc but waited until last night to activate the phone.
Now, I'm having issues with the phone randomly freezing and rebooting. I've done numerous PRL updates, I'm going to try a hard reset now too.
What's interesting is that this happened ONLY after I put the phone on the Sprint network. The phone has been in use since I got it on 5/24 and I never experienced this issue. In fact the problem started as I was trying to activate the phone. The phone froze while trying to use the "Activate this device" feature in settings. I had to turn around and go online to activate it.
This sounds like a network/software issue - why would this problem surface immediately after activating the phone???? Grrrr Sprint.
I had problems using the activate this device in settings as well. It would not activate and kept retrying to activate every minute or so. I ended up calling Sprint and they had me do a PRL update. I can't remember though if they did anything on their end. In the end it worked after the update. Maybe give them a call.
Sent from my EVO using xda premium
I was able to activate phone on Sprint.com.
Did or do you have issues with the phone freezing after activating it?
if you're gonna hard reset your phone, I'm pretty sure you need to wipe data for Google wallet first. Good luck. Sorry about reboots. Never had one on this device.
sent from a shining jewel 4g LTE
I had small problems activating also so I had to call sprint. They had me go to settings>system updates>update profile and then everything was fine. You might want to try that too.
Sent from my EVO using XDA
You could see if calling Sprint and having them re-provision the phone.. not sure if it will do anything but it doesn't hurt and takes a few minutes
Thanks for the suggestions guys - ultimately I decided to exchange the phone.
I pre-ordered the original phone and you know the first batch are always a little buggy. I was able to duplicate the problem immediately at the Sprint store just by turning on 3G, lol. It froze and went into its reboot cycle.
So far the replacement seems ok.......
I have an Samsung S9 Plus that was an AT&T unit (I think) and I flashed it over to the global firmware so I could use it on Visible (Verizon). It has been working for months, but I have now had this problem happen twice. I get up on a Monday, and notice that my phone has no service. I think it says "No Network Connection" or something like that. The first time I tried many of the usual steps - switching airplane mode, resetting network, wiping the cache, long support chats with Visible. What finally got it working again was putting in another sim(from Red Pocket - AT&T). That made the phone go through a reboot to swap over to the new sim. Then I put the old Visible sim back in. The phone does another reboot, and now everything is working again.
Is there a way that I can get the phone to go through this process without swapping the sims? I would just like to know if there is a more efficient way of fixing this problem when it pops up.
Phone info
SM-G965UA
Android 10
brotherhaslip said:
I have an Samsung S9 Plus that was an AT&T unit (I think) and I flashed it over to the global firmware so I could use it on Visible (Verizon). It has been working for months, but I have now had this problem happen twice. I get up on a Monday, and notice that my phone has no service. I think it says "No Network Connection" or something like that. The first time I tried many of the usual steps - switching airplane mode, resetting network, wiping the cache, long support chats with Visible. What finally got it working again was putting in another sim(from Red Pocket - AT&T). That made the phone go through a reboot to swap over to the new sim. Then I put the old Visible sim back in. The phone does another reboot, and now everything is working again.
Is there a way that I can get the phone to go through this process without swapping the sims? I would just like to know if there is a more efficient way of fixing this problem when it pops up.
Phone info
SM-G965UA
Android 10
Click to expand...
Click to collapse
Call your carrier and have them to a reprovision. I had this happen with T-mobile coming from Sprint.. They will have you turn off the phone, do something on their end, and after that it should work.
Just to update, I have switched over to ATT Prepaid. Since the change, I have not had the problem happen. I think it must have been an issue with Red Pocket. Either that or something that got fixed with an update. Just putting these data points out there for anyone else that is having issues like this.