So I wanted to dis-spell some misinformation out there & on XDA and also help with some issues I see out there that I ran into and found solutions by trial and error.
EVERYTHING here is not my work just what I found out thru trying others solutions / suggestions.
I'm going to try & put everything I can in one central place so maybe it can help others as quickly as possible. I will put it in 3 threads linked here the only reason for 3 threads will be to keep info related to each topic in order. if there are questions & answers others won't have to sift thru PAGES of unrelated info.
Its going to take me a couple of days to get all the info up and will try to put it (or links to it) all in the thread.
Here are the 3 threads...
Jelly Bean Update
(done manually, Probs encountered & solved: "System 7" errors; Red Ring Boot lock / brick; other minor ones)
Jelly Bean Root
(done w linux / ubuntu guide. Probs encountered & solved: Network connection failed; Root success (fail); Samba fail; others)
GSM & Straight Talk (w working Voice, Data & MMS)
done w RadioComm hack & build.prop edits. (Probs encountered & solved: com.android.phone failed loop; APN settings; default network, others)
The bottom line...All of the above are possible and from my experience there is no issue that can't be fixed even a supposed "brick". Don't give up, the info is out there (and here in a bit), and there are some great Devs & contributors out there who really help out their respective communities and us users as a whole by their hard work, dedication and patience.
THANK YOU TO ALL OF YOU WHO'VE Contributed.
Again I'm not a dev in anyway, All info Contained in these threads is "property" of others.
Notably...djrbliss, SamuriHL, TomSgt123 & Cellzealot. They are ALL OVER these different communities and threads contributing.
I started with a Moto Droid Bionic running verizon ICS stock.
Now it's Bionic / Jelly Bean (4.1.2) rooted & GSM enabled on ST.
( All 3 done )
MoodSwinger said:
So I wanted to dis-spell some misinformation out there & on XDA and also help with some issues I see out there that I ran into and found solutions by trial and error.
EVERYTHING here is not my work just what I found out thru trying others solutions / suggestions.
I'm going to try & put everything I can in one central place so maybe it can help others as quickly as possible. I will put it in 3 threads linked here the only reason for 3 threads will be to keep info related to each topic in order. if there are questions & answers others won't have to sift thru PAGES of unrelated info.
Its going to take me a couple of days to get all the info up and will try to put it (or links to it) all in the thread.
Here are the 3 threads...
Jelly Bean Update
(done manually, Probs encountered & solved: "System 7" errors; Red Ring Boot lock / brick; other minor ones)
Jelly Bean Root
(done w linux / ubuntu guide. Probs encountered & solved: Network connection failed; Root success (fail); Samba fail; others)
GSM & Straight Talk (w working Voice, Data & MMS)
done w RadioComm hack & build.prop edits. (Probs encountered & solved: com.android.phone failed loop; APN settings; default network, others)
The bottom line...All of the above are possible and from my experience there is no issue that can't be fixed even a supposed "brick". Don't give up, the info is out there (and here in a bit), and there are some great Devs & contributors out there who really help out their respective communities and us users as a whole by their hard work, dedication and patience.
THANK YOU TO ALL OF YOU WHO'VE Contributed.
Again I'm not a dev in anyway, All info Contained in these threads is "property" of others.
I started with a Moto Droid Bionic running verizon ICS stock.
Now it's Bionic / Jelly Bean (4.1.2) rooted & GSM enabled on ST.
(I will link to the other threads as they are finished)
Click to expand...
Click to collapse
Thanks this is what I've been waiting for. I've been able to update and root under jellybean, but can't get GSM to work. Every time I edit the build.prop it boot loops and I have to fxz jellybean and start over. Waiting for a complete guide. I'm wondering if its possible to get Tmobile to work I have HW A. Thread subscribed.
This definitely works on both T-Mobile and AT&T on HW A Bionic under the the JB 4.1.2 98.72.22 XT875 Verizon release.
I had to redo mine after I had a problem with the camera failing due to my using an older cdt.bin when I manually flashed with fastboot.
So I had been trying to figure out that problem before writing up the method.
When you make the build.prop edits for GSM service it causes a force close of com.android.phone and you have to perform a data wipe, unfortunately.
I can also create another zip file installation of the NV edit with the updater-binary from the new release, but it still has to be flashed from Bionic Bootstrap recovery and won't work in Safestrap, unless it has been updated recently to support flashing unsigned zips to the safe slot.
For most users, I think manually editing the NV with RadioComm will be a better solution.
cellzealot said:
This definitely works on both T-Mobile and AT&T on HW A Bionic under the the JB 4.1.2 98.72.22 XT875 Verizon release.
I had to redo mine after I had a problem with the camera failing due to my using an older cdt.bin when I manually flashed with fastboot.
So I had been trying to figure out that problem before writing up the method.
When you make the build.prop edits for GSM service it causes a force close of com.android.phone and you have to perform a data wipe, unfortunately.
I can also create another zip file installation of the NV edit with the updater-binary from the new release, but it still has to be flashed from Bionic Bootstrap recovery and won't work in Safestrap, unless it has been updated recently to support flashing unsigned zips to the safe slot.
For most users, I think manually editing the NV with RadioComm will be a better solution.
Click to expand...
Click to collapse
Safestrap 3.11 now allows you to flash zip on the safe side. I have been holding off updating JB until their was a resolve concerning the GSM edits for T-Mobile. I along with others will be patiently waiting for you to post the needed edits for the new JB update. Thanks for all your work,, :good::good::good:
wilsonc10 said:
Safestrap 3.11 now allows you to flash zip on the safe side. I have been holding off updating JB until their was a resolve concerning the GSM edits for T-Mobile. I along with others will be patiently waiting for you to post the needed edits for the new JB update. Thanks for all your work,, :good::good::good:
Click to expand...
Click to collapse
Well, in that case, then we can probably make a zip file that does the whole thing in one operation and replaces the build.prop and removes STK.apk and VZWPhoneService.apk and performs the NV edit to 1877 NV_BC_CONFIG_I.
That would certainly make the write up a lot shorter and easier!
I will talk to P3Droid and see about getting an updater-script worked up and a file that can be tested.
Neither of us runs SafeStrap so we will need to have it tested by others.
cellzealot said:
Well, in that case, then we can probably make a zip file that does the whole thing in one operation and replaces the build.prop and removes STK.apk and VZWPhoneService.apk and performs the NV edit to 1877 NV_BC_CONFIG_I.
That would certainly make the write up a lot shorter and easier!
I will talk to P3Droid and see about getting an updater-script worked up and a file that can be tested.
Neither of us runs SafeStrap so we will need to have it tested by others.
Click to expand...
Click to collapse
can you please post your modified 4.1.2 build.prop?
http://db.tt/4DAJyz8G
That is my build.prop file from Bionic.
It has some other edits included. We are working on a complete update package now for the hack that will make this very simple.
Edit: The update.zip install method is not going to work due to the new binary not supporting the motorola.update_nv function.
This is the same reason we can't make these zips for the MSM8960 chipset.
We are hoping to find a different binary that can be used to write NV that could perform the edit via a shell script, but that is a much more complicated problem than simply making a zip file using an existing updater-binary.
For the time being the modifications will have to be done manually with RadioComm or DFS to write the 1877 NV item and a root file explorer or adb shell to make the build.prop switch and remove the apk and odex files from /system.
MoodSwinger said:
So I wanted to dis-spell some misinformation out there & on XDA and also help with some issues I see out there that I ran into and found solutions by trial and error.
EVERYTHING here is not my work just what I found out thru trying others solutions / suggestions.
I'm going to try & put everything I can in one central place so maybe it can help others as quickly as possible. I will put it in 3 threads linked here the only reason for 3 threads will be to keep info related to each topic in order. if there are questions & answers others won't have to sift thru PAGES of unrelated info.
Click to expand...
Click to collapse
Good Stuff, plus you have everything in one location which eases the headaches of updating, gsm etc. :good:
Any progress on making this an easy update? And thanks for all the work you do!
surechap said:
Thanks this is what I've been waiting for. I've been able to update and root under jellybean, but can't get GSM to work. Every time I edit the build.prop it boot loops and I have to fxz jellybean and start over. Waiting for a complete guide. I'm wondering if its possible to get Tmobile to work I have HW A. Thread subscribed.
Click to expand...
Click to collapse
I'm on the same boat. I had to fxz over because I replaced my buil.prop with the one provided above. Not working. Any suggestions?
help
i receive a bionic with jelly bean and i have already tried for almost 6 hours to activate the gsm band, i was thinking that it was going to be easy as the droid razr that i have, just i insert the sim card and upgraded to ics and the gsm band was working.
But with this i don't have the option to chose the gsm band and if i do the steps that i have seen i got a android force to close etc or a boot loop and i don't know what to do. I don't live in the USA so i was hoping that i was going to be easy but i see that is not easy. Can anyone help me:silly:
help on my HW C Bionic
MoodSwinger said:
So I wanted to dis-spell some misinformation out there & on XDA and also help with some issues I see out there that I ran into and found solutions by trial and error.
EVERYTHING here is not my work just what I found out thru trying others solutions / suggestions.
I'm going to try & put everything I can in one central place so maybe it can help others as quickly as possible. I will put it in 3 threads linked here the only reason for 3 threads will be to keep info related to each topic in order. if there are questions & answers others won't have to sift thru PAGES of unrelated info.
Its going to take me a couple of days to get all the info up and will try to put it (or links to it) all in the thread.
Here are the 3 threads...
Jelly Bean Update
(done manually, Probs encountered & solved: "System 7" errors; Red Ring Boot lock / brick; other minor ones)
Jelly Bean Root
(done w linux / ubuntu guide. Probs encountered & solved: Network connection failed; Root success (fail); Samba fail; others)
GSM & Straight Talk (w working Voice, Data & MMS)
done w RadioComm hack & build.prop edits. (Probs encountered & solved: com.android.phone failed loop; APN settings; default network, others)
The bottom line...All of the above are possible and from my experience there is no issue that can't be fixed even a supposed "brick". Don't give up, the info is out there (and here in a bit), and there are some great Devs & contributors out there who really help out their respective communities and us users as a whole by their hard work, dedication and patience.
THANK YOU TO ALL OF YOU WHO'VE Contributed.
Again I'm not a dev in anyway, All info Contained in these threads is "property" of others.
Notably...djrbliss, SamuriHL, TomSgt123 & Cellzealot. They are ALL OVER these different communities and threads contributing.
I started with a Moto Droid Bionic running verizon ICS stock.
Now it's Bionic / Jelly Bean (4.1.2) rooted & GSM enabled on ST.
( All 3 done )
Click to expand...
Click to collapse
I need help on HW C Bionic, i want to unlock its GSM antenna...
@ tonochito..sent private msg.
@ Abner...what's your problem? have you gone thru the steps exactly as they are? I do know there are some diff's between the "HW"'s but I don't know what they are. Be a bit more specific maybe I can check something out for you.
Like I stated I'm not really a Dev or Hacker, just wanted to do this and help others with some of the problems I had and saw others were having that I found solutions for.
If I can help I will, but there are others who know way more than I if you can be a bit more specific.
Cheers,
MoodSwinger
Geeky Post
weather or not your subscribed to state the obvious working or non working is somewhat confusing in your post are you identifying
that the conversation here is working after the mod or ?
samba didnt root at first RSD and Radiocomm no longer connect in windows after Jelly bean install
is there old sbf format files for the original jelly bean distro or anything older that will flash on 0A.78
Outgoing calls are restricted by FDN error
Hi and thanks for all the amazing help!
I installed the stock JB 4.1.2 image on my droid bionic and rooted the device using marty45714's easy root. In order to use the GSM network I used the radiocomm modification. I made the following changes in build.prop:
ro.telephony.default_network=7
ro.mot.phonemode.vzw4gphone=0
telephony.lteOnCdmaDevice=0
ro.telephony.ril.v3=signalstrength
Upon reboot I change the preferred network type in Testing->Phone Info to "GSM only".
(A build.prop default_network value other than 7 crashes the user interface, continuously reporting that a certain process has stopped).
As far as I understand the above steps are exactly the standard instructions that have been posted for the trifecta.
The phone works perfectly fine until 36 hours or so after a reboot when I can no longer make outgoing calls. I get the following error when attempting:
Outgoing calls are restricted by FDN
Everything else still works: Incoming calls, sms and data.
A reboot restores permissions for outgoing calls for another day. I used two different Israeli SIMs with the same outcome.
My question, of course, is how to prevent the FDN restriction.
Many, many thanks!
issue with data on att non pre paid
I recently ran this hack on my bionic for my wife, she previously had a flip phone without a data package. Before adding a data package the bionic would connect to the data network and get decent hspa speeds however after adding the data package to ger plan it just says mobile network state disconnected and will not even get edge or gprs. Any ideas on how to make it work again?
Thanks in advance
Bionic Data Issues
Followed all the directions and have a Bionic working on T-mobile 4G LTE based Straight Talk sim card. Voice works great a little shabby on signal strength that I would like to see improve but most disturbing is the No Data connection at all. Yes on the bionic under settings the Data is turned on but the signal never shows higher than Edge even though we have T-Mobile LTE coverage (Tested by T-mobile phone) and MMS and Data is a no go at all.
If I need to change any settings please direct me to these settings with the new information I need to put in (I want to use the Bionic at its full potential). I have to get Data up and running because a Bionic with no Data is a paper weight.
Thanks in advance
Help gsm wont work
Hi, I am trying to get my bionic to work ,but it is not. I have tried and started over the steps 3 times but still nothing. I am on 4.1.2 trying to get it work with t-mo. The phone is also HW-A too. All I get is no signal. It does show my phone number though. plz help!
izyogi said:
Hi and thanks for all the amazing help!
I installed the stock JB 4.1.2 image on my droid bionic and rooted the device using marty45714's easy root. In order to use the GSM network I used the radiocomm modification. I made the following changes in build.prop:
ro.telephony.default_network=7
ro.mot.phonemode.vzw4gphone=0
telephony.lteOnCdmaDevice=0
ro.telephony.ril.v3=signalstrength
Upon reboot I change the preferred network type in Testing->Phone Info to "GSM only".
(A build.prop default_network value other than 7 crashes the user interface, continuously reporting that a certain process has stopped).
As far as I understand the above steps are exactly the standard instructions that have been posted for the trifecta.
The phone works perfectly fine until 36 hours or so after a reboot when I can no longer make outgoing calls. I get the following error when attempting:
Outgoing calls are restricted by FDN
Everything else still works: Incoming calls, sms and data.
A reboot restores permissions for outgoing calls for another day. I used two different Israeli SIMs with the same outcome.
My question, of course, is how to prevent the FDN restriction.
Many, many thanks!
Click to expand...
Click to collapse
i did the same for mine, but i set ro.telephony.default_network=3, the error shows up, but you just factory reset and it goes away and have no restrictions.
rooted droid on metro pcs
hey guys i have my droid running both cm 10 and liquid v 2.9 . ive done all the build.prop edits and then some and when i set the prefered network it keeps finding aTT instead of t-mobile which is what im asumming it should be on for metro...i really need help been at this a while on and off i feel like im real close.
Related
Hi guys... I have a few questions for you about my Hero. Forgive me for not yet having the same level of knowledge that many of you guys have. I am certain that I can contribute in some way, as well. My phone details:
Firmware version: 1.5
Baseband version: 1.04.01.09.21
Kernel version: 2.6.27-533ce29d
Build number: 1.56.651.2 CL5027
Software version: 1.56.651.2
Hardware version: 0002
1. I've read several stories where a number of phones were returned because they couldn't be updated when the new update was released. Is this an absolute fact, that it can't be updated, or is there an error in code somewhere that made it reject the update and there is a known workaround? The answer to this question obviously dictates my forward motion.
I have the typical problem apps, and am getting no joy from youtube. Presently, I'm surfing with good speeds, but market is non-existent.
I like having Sprint tv, when I'm having to sit and wait somewhere.
I have time today and tomorrow to get things ironed out, but will be extrmemly busy after that, like 20 hours a day studying. I'm hoping to get some direction that will give me complete functionality, but will require the least setup. I am quite computer savy, and repaired this phone, to this point, in a day or 2, without asking a single question of anyone. I traced down problems, and solved issues. Seen APN, and TCP errors (don't believe it completely, since I can authenticate on the web). Know that some issues are url problems, etc.
The following questions are based upon the answer to question number 1.
2. Can this phone be updated?
2a. If yes, What do you recommend... 2.1? What rom do you suggest, for full stock-like functionality? Will I lose Sprint tv? Pointers/direction? (pancake??, superhero??)
2b. If no, What rom do you suggest, for full stock-like functionality? Will I lose Sprint tv? Pointers/direction?
Before repairing the phone, I actually tried to update it from my computer, but it was rejected. I turned off my security software and tried again. I noticed that while using XP sp2, a windows program that was incorporated starting with sp2, DEP (data execution prevention) didn't like the actions that the update was taking, and arrested it very shortly after starting (yet the window cycled forever). I assume that many people wouldn't be this observative, and recognize that this was happening. It was halting an HTC file that utilized storage memory (similar to buffer overrun exploits - the reason DEP halted it), for temporary storage of the files to be used for the update. That file was as follows:
C:\Program Files\HTC\HTC Sync\Mobile Phone Monitor\FsyncServer.exe
And the way to prevent it from continuing to do so is:
1. Click Start
2. Select Control Panel
3. Select System
4. Click the Advanced tab
5. In the Performance region select Settings
6. Click the Data Execute tab in the dialog box that opens
7. Select Turn on DEP for all programs and services except for those I select
8. Click Add.
9. The open dialog box will open. Browse and select your application.
10. Click Open
11. Click Apply
12. Click Ok
I guess what I'm sort of suggesting, is that this might be why anyone ever had problems updating, with the exception that OTA also said there wasn't an update.
So, back to the original question. Is it true that some Heros can't be updated? I don't want to force something, and brick, if you know what I mean. I completed the setting that will allow it to go forward (listed above), but haven't tried to update since. I felt that I really needed to ask you guys first, before I made a mistake that I'd regret. Should I try again? Before I started working on the phone I did try OTA and it said there wasn't an update. Now I don't have that option anymore. After repairing the phone, I've lost updates. Am I stuck with 1.5? With my run of the mill phone desires (except that it be fully functional), should I keep 1.5?
I did see gmail 2.3 apk, but is that compatible with 1.5? This looks like is would solve the market issue, if I could use it.
I did read about gscript and addressing mms (although I'm sure that's very old news to you guys), but if in fact I can't update this phone, it might be one of my only alternatives. If that is my only choice, are their also additional scripts to address everything I need to fix (all the normal issues)?
Additionally, it seems that many apps register with the phone/user. So, when you are using a used phone, many apps are still registered as functional. Does flashing a new rom affect the OS and apps? Will I loose the already registered/functioning apps? With a complete upgrade, will I gain functionality of some key features, but lose all other previously enabled apps? In other words, will I gain update, and market, and lose sprint tv?
I have read a lot. With things the way they should be, I've not been able to quite determine what I need to do. With all this being said, How do I go forward and achieve a fully functioning phone? What is the best choice of path's to take for me?
Rooting? I have seen the one-click, and think I'd be correct in that I need something containing Sense UI. Forgive me for asking a stupid question... but the rom is only the menu accessibility, correct? Is there something straight out of the box setup, or do all roms contain configuration notes?
I'm satisfied with stock features, if they work, and adding other useful things like tethering. Since I'll be so busy, I'll have little time to do much else. But don't get me wrong. I have 10 PC's in my house, with only 2 people living here. I'd love to customize the crap out of it. It's just not going to happen any time soon, due to my brutal study schedule. So for now, I just want it to work like it should, on a B mvno.
Do I go north, south, east, or west????
Could someone chime in that can give me direction, based on everything I've stated. Your response is so graciously appreciated.
Cheers!
Umm well I'm not sure why you're having problems with any update, someone who's far more experienced can maybe tell you but as far as roms I think it depends on whether you like sense or wanna go froyo. Cyanogen mod 6.1 stable (2.2) is nice & highly customizable however there's also AOSP roms (2.2) that some people feel is quicker than cyanogen however they aren't as customizable as cyanogen, in addition there are tons of GREAT themes for both. Also we've had a ton of work on an odex AOSP gingerbread rom (2.3) not yet stable but works good for most & on that note a great themer also put together a themed AOSP gingerbread rom (2.3) that looks good & about stability I'm not so sure on but I would recommend those roms. Although with these roms YES you will lose sprint apps like TV & vvm etc. However people have posted these apks in the theme thread section to work on roms like cyanogen & AOSP. If you do like sense roms there's a couple that are still live in the development section like nfinite & nfx I believe. Hope some of that info helps
Thanks so much for your response. So Cyanogen mod 6.1 stable (2.2) is highly customizable... That's good.
So let me get this straight. I need to:
root (is one-click OS version specific? Can it be used on 1.5?)
backup
save to pc
update to 2.1 (if I can, and it needs to be the rootable version found here)
re-root
and flash Cyanogen
and setup
Is this correct?
inkblots said:
Thanks so much for your response. So Cyanogen mod 6.1 stable (2.2) is highly customizable... That's good.
So let me get this straight. I need to:
root (is one-click OS version specific? Can it be used on 1.5?)
backup
save to pc
update to 2.1 (if I can, and it needs to be the rootable version found here)
re-root
and flash Cyanogen
and setup
Is this correct?
Click to expand...
Click to collapse
Sort of. I can't remember which version I was at when I rooted but I remember I downgraded to do it. But if you go in the development section you will find a thread that shows & gives you what you need to root. So you should root. Then flash a recovery image such as clockwork mod or amon ra. When I rooted I used the recovery from the downloadable app (Rom manager) in the market & that one was clockdwork mod. It's worked great for me so I've been using it ever since. Then backup whatever you are running currently. Then flash whatever rom you want. I'm about to see if I can link you to a root thread then once you do so I can give you a dl link to cm 6.1 stable. Will you be able to root on 1.5?? I don't completely know...
Edit: Ok this is the way I rooted mine, hopefully this will work for you
http://theunlockr.com/2010/09/27/how-to-root-the-htc-hero-androot-method/
Hello all,
When the Droid 3 first came out psouza4 posted how to root and remove bloatware. Since then I've uninstalled the launcher once (big mistake by not paying attention) got it fixed but since then I've done nothing more.
The phone is still rooted. I don't know if the bloatware is still removed because I used the HDMI once and don't know if I ran the script with just the HDMI enabled (whatever HDMI is tied to that is) or the default script.
Reading thru the forums there is a wealth of information.
I'm not sure what direction to go. I have ADB installed still and it's updated, don't know if I'll need it.
The main problem is random reboots with the phone when going to take pictures or video. Sometimes I'll lock up for five minutes and finally cycle power. I started reading how to troubleshoot for this type of behavior when I realized I should just start over.
My goals are (and not in any logical order) to wipe the phone, wipe the internal memory, wipe the external memory, get the phone updated to the latest OTA from Verizon and Android operating system (if there is a newer ver avail for my model phone)
Phone stats:
Droid 3
5.5.959XT862 Verizon
ANDROID VER
2.3.4
BASEBAND
N_03.18.16P
KERNEL
2.6.35.7-g42f0276
[email protected] #1
BUILD
5.5.1_84_D3G-20_TA-9
ERI
5
PRL
52826
Click to expand...
Click to collapse
Thanks in advance for any input/help. If there is series of posts you recommend me to follow I can read them and do it that way.
Have a super Monday.
-Sc
I'm a Pageplus user. After flashing 6.7.246 (ICS 4.0.4), I got OTA to 98.72.22 (JB 4.1.2) successfully.
But I'm stuck then when trying to activate Pageplus OTA by calling *22800:
I kept getting "Sorry, this SIM card is not recognized or registered..", no matter how many times I tried.
There's another notified error: "Unknown SIM card detected"
It's abnormal b/c it should fail only 2-3 times, then taking me to the activation screen.
The 4glteSIM card inside was activated before and used on the 6.7.246 stock build.
FYI, I also reflashed 6.7.246 one more time on top of 6.7.246 and didn't encounter the activation problem. So I'm superised to have this issue after upgraing.
Please advice me if you have any idea.
Thanks in advance.
Did you keep root? And if you did flash a rom like cm10 and then activate the rom like you did on ics. I did that and then I rebooted in stock jelly bean and it was activated. Hope that helps!
Sent from my DROID BIONIC using xda app-developers app
Thx for your reminding. I'll try this way.
Did you install the cm10 with safestrap 3? I tried to install it on the JB but failed. Does it require a rooted JB?
I tried to search but cannot find an effective way to root Bionic JB.
I'll appreciate if u can give some detail abt: A. the JB rooting method, and B. How to install cm10 (or the justed released Blurry-JB_2.4.zip) while keeping the JB stock rom.
Thanks a lot!
Wilsono1050 said:
Did you keep root? And if you did flash a rom like cm10 and then activate the rom like you did on ics. I did that and then I rebooted in stock jelly bean and it was activated. Hope that helps!
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
Idk if there's a jelly bean root method for the droid bionic. But I kept root after the ota. Then with safestrap 3.11 I installed cm10 and activate it. It usually retrieved the activation when the phone boots up with cm10.
Sent from my DROID BIONIC using xda app-developers app
I managed to have the JB stock rom rooted anyway (by the virtual box approach).
Then I was allowed to install safestrap 3.1, then the newest Blurry JB 2.4.
I tried to "activate" from the step 2 ("2-Getting phone ready for OTA Activation") of the old instaruction:
http://www.howardforums.com/showthr...CS-OTA-Activation-TXT-MMS-3G-ROOT-on-PagePlus
But the CDMA Workshop didn't find the port. I assume the reason is that safestrap has blocked the normal bp-tools booting way.
So I can only start from "3-OTA Activation".
After changing "Network Selection" to "CDMA Only", I rebooted and dialed *22800. Still get the same error "sim card not recognized or registered".
Can you please detail how did you "activate" it under cm10?
Many thanks.
Wilsono1050 said:
Idk if there's a jelly bean root method for the droid bionic. But I kept root after the ota. Then with safestrap 3.11 I installed cm10 and activate it. It usually retrieved the activation when the phone boots up with cm10.
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
Okay, if you install the jb blurry rom its going to be the same problem as stock because they're pretty much the same. What I did is 1. Kept root after the ota 2. Installed safestrap 3.11 3.) Rebooted into safestrap and created rom slot 1 and installed cm10 rc2 and gapps. When I booted up it activated by itself for me. I then booted up to stock rom and it was activated as well, but had to install the build prop. so I wouldn't get the unregistered sim error thing. Hope that helps!
Sent from my XT875 using xda app-developers app
I installed the cm10.1.0 rc2 into the slot 1 (with and without gapp), but reboot get a blank screen. Have to pull the battery to get reboot to ss.
Wilsono1050 said:
Okay, if you install the jb blurry rom its going to be the same problem as stock because they're pretty much the same. What I did is 1. Kept root after the ota 2. Installed safestrap 3.11 3.) Rebooted into safestrap and created rom slot 1 and installed cm10 rc2 and gapps. When I booted up it activated by itself for me. I then booted up to stock rom and it was activated as well, but had to install the build prop. so I wouldn't get the unregistered sim error thing. Hope that helps!
Sent from my XT875 using xda app-developers app
Click to expand...
Click to collapse
may thx. that work!
taller238 said:
I installed the cm10.1.0 rc2 into the slot 1 (with and without gapp), but reboot get a blank screen. Have to pull the battery to get reboot to ss.
Click to expand...
Click to collapse
taller238 said:
may thx. that work!
Click to expand...
Click to collapse
Did you get it to work?
Sent from my XT875 using xda app-developers app
did anyone get this to work?
Thinking of just saving myself the headache and getting a droidx2.
I'm running cm10.1 and safestrap 3.11 3. I'm going to try a dealer tomorrow to see if they can activate it on pageplus.
I haven't activated a phone on pageplus for a while. I've been using simple mobile, straight talk and h20
taller238 said:
Still get the same error "sim card not recognized or registered.
Click to expand...
Click to collapse
I had the same problem when I went from GB to ICS. I just ignored it and kept trying and trying (based on advice/steps I found elsewhere) and after a few times it worked. So I would suggest trying it about 10-12 times in a row to see if it works.
Also, here is the method I used for GB to ICS, I'd be interested to know if they help you move from ICS to JB:
Re-activating phone
1. Remove any old Motorola Droid Bionic drivers you may have on your computer and install the newest ones.
2. Turn phone off and turn back on in BPTools mode. Then plug the phone into your computer via USB.
3. Open DFS. Click "Ports" and select the COM port for your phone. Next, click the "SPC" button.
4. Click the "Programming" tab and then the "General" tab. Change the "Ruim Config" to NV_ONLY and click "Write".
5. Click the "Data" tab. Under the "Mode" section, change the "HDR SCP force AT config" option to "RevA_MFPA" and click "Write".
6. Close DFS and unplug phone from USB port.
7. Go to the dialer and dial ##7764726 (##PROGRAM). When prompted for an SPC password, enter "000000" and hit verify.
8. Go to "06 Test Mode". Hit "Next" twice. Then, change the Network mode to "CDMA Only".
9. Back out to the home screen; the phone will automatically restart.
10. After the phone has restarted, go to the dialer and dial *22800. Ignore any SIM card error messages you may see; just keep trying *22800 until you reach the activation screen.
11. Follow the instructions to activate the phone.
I have been working on this for HOURS and tried just about every single thing I could. Root, CDMA workshop, DFS, MDN, MIN, SIN, Safestrap, CM10.1, CM10... what a mess! I can attest that it is possible to get working but might be very painful. I read the numerous new and old threads trying to piece together information. In the end it's hard to say what really worked but let me comment on a few things:
1) *22800 never worked on the stock ROM. Believe me, I tried it about 200 times.
2) You can program in your MDN/MIN/SID using DFS. However, doing so left me with no incoming calls/texts. Only outgoing... weird.
3) CM10.1 did nothing for me. There was a very annoying issue where I tried to activate it and it acted like it was going to but I couldn't "press 1" since the keypad was disabled during activation.
4) Hashcode's CM10 STOCK didn't boot at all. I tried it with both Safestrap 2.11 and 3.11. CM10 KEXEC booted.
5) I finally got the activation to work in CM10 KEXEC with Safestrap 3.11. After activation worked, incoming calls were fixed.
So... here's the kicker. After pulling my hair out and being frustrated for many, many hours I gave the phone to my wife. I had dialed *22800 and when it started to say "press 1" I handed the phone to her.
"See?!" I said.
"See what?" she said. She poked at the screen a bit.
"It wants me to press 1 and there's no dialpad."
"Hmmm..." she said.
Suddenly I heard the sound of ringing. "Wha...?! Hey, give me that. A different screen? 'Your phone is being activated now, please wait 15 minutes.' GAH! I mean... yay!"
I asked my wife what she did. She was like, "I dunno... I pressed Home Menu Back or something."
So... if I had to guess on a procedure I think it would be like:
1) Update phone to JB if not updated already.
2) Use easy Virtualbox method to root.
3) Go through CDMA/DFS rigamarole (NV only RevA_MFPA yadda yadda)
4) Reboot and set CDMA only. Use BuildProp Editor to set telephony.lteOnCdmaDevice=0.
4b?) At some point I used DFS to manually program MDN/MIN/SID, but I'm not sure this is necessary.
5) Install Safestrap 3.11
6) Install CM10 KEXEC with Safestrap 3.11 in slot 1.
7) Boot CM10 and *22800 away! Cross your fingers, hand the phone to whoever is next to you in despair.
8) ???
9) Profit!
I erased Safestrap slot, uninstalled recovery and uninstalled the app when I was done.
has anybody successfully activated the stock JB on the Bionic on PagePlus?
no progress on this yet since I can't find any success stories on Hofo either.
thanks
BD
BuonaDomenica said:
has anybody successfully activated the stock JB on the Bionic on PagePlus?
no progress on this yet since I can't find any success stories on Hofo either.
thanks
BD
Click to expand...
Click to collapse
they all claim this works
Droid-RAZR-MAXX-JellyBean-OTA-Activation-TXT-MMS-3G-ROOT-TETHERING-on-PagePlus
This one confirmed also
Droid-RAZR-and-RAZR-Maxx-Droid-4-Droid-Bionic-on-Pageplus-no-root-or-custom-roms
My brothers bionic activated just fine also...sometimes you just have to follow the steps Exactly as written
primetime^ said:
they all claim this works
Droid-RAZR-MAXX-JellyBean-OTA-Activation-TXT-MMS-3G-ROOT-TETHERING-on-PagePlus
This one confirmed also
Droid-RAZR-and-RAZR-Maxx-Droid-4-Droid-Bionic-on-Pageplus-no-root-or-custom-roms
My brothers bionic activated just fine also...sometimes you just have to follow the steps Exactly as written
Click to expand...
Click to collapse
well your links are not working as I want to check it out
primetime^ said:
they all claim this works
Droid-RAZR-MAXX-JellyBean-OTA-Activation-TXT-MMS-3G-ROOT-TETHERING-on-PagePlus
This one confirmed also
Droid-RAZR-and-RAZR-Maxx-Droid-4-Droid-Bionic-on-Pageplus-no-root-or-custom-roms
My brothers bionic activated just fine also...sometimes you just have to follow the steps Exactly as written
Click to expand...
Click to collapse
BuonaDomenica said:
well your links are not working as I want to check it out
Click to expand...
Click to collapse
Droid-RAZR-MAXX-JellyBean-OTA-Activation-TXT-MMS-3G-ROOT-TETHERING-on-PagePlus
http://www.howardforums.com/showthread.php/1794056-Droid-RAZR-MAXX-JellyBean-OTA-Activation-TXT-MMS-3G-ROOT-TETHERING-on-PagePlus
Droid-RAZR-and-RAZR-Maxx-Droid-4-Droid-Bionic-on-Pageplus-no-root-or-custom-roms
http://www.howardforums.com/showthread.php/1795498-Droid-RAZR-and-RAZR-Maxx-Droid-4-Droid-Bionic-on-Pageplus-no-root-or-custom-roms!
they weren't links,,, google is your friend,,, they are at howardfourms enjoy these links though...
gonna be looking them over myself
.
Kralik said:
I have been working on this for HOURS and tried just about every single thing I could. Root, CDMA workshop, DFS, MDN, MIN, SIN, Safestrap, CM10.1, CM10... what a mess! I can attest that it is possible to get working but might be very painful. I read the numerous new and old threads trying to piece together information. In the end it's hard to say what really worked but let me comment on a few things:
1) *22800 never worked on the stock ROM. Believe me, I tried it about 200 times.
2) You can program in your MDN/MIN/SID using DFS. However, doing so left me with no incoming calls/texts. Only outgoing... weird.
3) CM10.1 did nothing for me. There was a very annoying issue where I tried to activate it and it acted like it was going to but I couldn't "press 1" since the keypad was disabled during activation.
4) Hashcode's CM10 STOCK didn't boot at all. I tried it with both Safestrap 2.11 and 3.11. CM10 KEXEC booted.
5) I finally got the activation to work in CM10 KEXEC with Safestrap 3.11. After activation worked, incoming calls were fixed.
So... here's the kicker. After pulling my hair out and being frustrated for many, many hours I gave the phone to my wife. I had dialed *22800 and when it started to say "press 1" I handed the phone to her.
"See?!" I said.
"See what?" she said. She poked at the screen a bit.
"It wants me to press 1 and there's no dialpad."
"Hmmm..." she said.
Suddenly I heard the sound of ringing. "Wha...?! Hey, give me that. A different screen? 'Your phone is being activated now, please wait 15 minutes.' GAH! I mean... yay!"
I asked my wife what she did. She was like, "I dunno... I pressed Home Menu Back or something."
So... if I had to guess on a procedure I think it would be like:
1) Update phone to JB if not updated already.
2) Use easy Virtualbox method to root.
3) Go through CDMA/DFS rigamarole[/URL] (NV only RevA_MFPA yadda yadda)
4) Reboot and set CDMA only. Use BuildProp Editor to set telephony.lteOnCdmaDevice=0.
4b?) At some point I used DFS to manually program MDN/MIN/SID, but I'm not sure this is necessary.
5) Install Safestrap 3.11
6) Install CM10 KEXEC with Safestrap 3.11 in slot 1.
7) Boot CM10 and *22800 away! Cross your fingers, hand the phone to whoever is next to you in despair.
8) ???
9) Profit!
I erased Safestrap slot, uninstalled recovery and uninstalled the app when I was done.
Click to expand...
Click to collapse
THANK YOU so much for making this post! I was finally able to activate my bionic after a week of reading the internet. lol. To update this post, yes, you need to do 4b. That step was what got me over the hump.
Anyone know the reason why no 3G? 1x works just fine. When toggle cdma/evdo, it still shows 1x.
I found some useful information about this about a month ago and some more details recently.
The system app com.motorola.setupwizard.phoneservice (VzwPhoneService.apk) actually intercepts attempts to call the activation numbers. The manifest file hinted at it with the names of the permissions and intents it has in there, and recently looking at decompiled source code confirmed it. The app is also responsible for SIM-based activation for Verizon 4G.
This app seems safe to disable for those on Verizon MVNOs; it is also on lists online of apps that people have safely disabled. When disabled, you can freely call up the activation screen with *228 or its variants.
Note that if you disable that app with a method that is permanent, like changing file extension, moving, or deleting, you should also disable com.motorola.setupwizard.controller (VzwController.apk) by one of those methods. If you ever wipe data, this will prevent it from getting stuck after the welcome screen if you tap start instead of doing the 4-corner bypass. (VzwController gets stuck waiting forever for the disabled VzwPhoneService) A side effect of disabling the additional app is that you no longer need to do the 4-corner bypass on first boot after wiping data when the phone isn't activated.
ShadyDreamer said:
I found some useful information about this about a month ago and some more details recently.
The system app com.motorola.setupwizard.phoneservice (VzwPhoneService.apk) actually intercepts attempts to call the activation numbers. The manifest file hinted at it with the names of the permissions and intents it has in there, and recently looking at decompiled source code confirmed it. The app is also responsible for SIM-based activation for Verizon 4G.
This app seems safe to disable for those on Verizon MVNOs; it is also on lists online of apps that people have safely disabled. When disabled, you can freely call up the activation screen with *228 or its variants.
Note that if you disable that app with a method that is permanent, like changing file extension, moving, or deleting, you should also disable com.motorola.setupwizard.controller (VzwController.apk) by one of those methods. If you ever wipe data, this will prevent it from getting stuck after the welcome screen if you tap start instead of doing the 4-corner bypass. (VzwController gets stuck waiting forever for the disabled VzwPhoneService) A side effect of disabling the additional app is that you no longer need to do the 4-corner bypass on first boot after wiping data when the phone isn't activated.
Click to expand...
Click to collapse
THIS! This so much! I had given up on flashing custom rom's after successfully switching my XT912 to page plus (3g/MMS working) and from there had just given up on custom roms after such a large headache. That was a year ago when the phone was coming from ICS to Jellybean (that was a rookies worst nightmare when google is your only quick resource: wrong versions, wrong tools, old information and didn't know a damn bit better. Ugh) anyways, I recently came back to try it out but found out yet again I was trying to use old information when getting through the activation process. This solved it though. I used Titanium Backup (trial version) to delete the system app/process and activation screen popped up on first try! If anyone else has the same issue that I had, where US Cellular answered my activation call, don't fret. I imagine it has to do with the SID (CDMA Network ID) but then I had let the phone sit for a minute and noticed at the bottom "a special number needs to be called to activate this phone" hit that button then the Verizon activation system answers and its good to go from there.
I'll now install safestrap and hopefully get a version of CM11 to run properly which caused this whole re-flashing process. I had a "working" stock rom that would constantly try to activate on phone startup, but 3g would work after skipping all those annoying screens, however when booting to CM11 it was not working with 3g.
Thank you again for that information, I can confirm com.motorola.setupwizard.phoneservice is the culprit to OTA activation problems when switching to PagePlus network.
I've seen several discussions about this around the web, but none of the solutions I've read have helped me.
I have the Sprint HTC One M8 with custom ROM (ViperOneM8). The phone is activated and works fully, yet on reboot I always get the 'Hands Free Activation' wizard. If I hit Activate and then Done it goes away and I can use my phone normally, but every reboot brings it back up again.
Ideas?
I'll add that I have custom recovery (TWRP), rooted, custom ROM, and S-Off.
Htc m8 and sprint
aprwx said:
I've seen several discussions about this around the web, but none of the solutions I've read have helped me.
I have the Sprint HTC One M8 with custom ROM (ViperOneM8). The phone is activated and works fully, yet on reboot I always get the 'Hands Free Activation' wizard. If I hit Activate and then Done it goes away and I can use my phone normally, but every reboot brings it back up again.
Ideas?
Click to expand...
Click to collapse
Sorry I have the same issue with mine and finally ive called htc for a swap out phone to see if its a software defect. htc said that if it still occures it may bee an issue with sprint...
Are you running stock, or did you install a custom rom?
Sent from my Sprint HTC One M8
... I ask because when I first bought the phone it activated fine (with delay because it was the same day that the Galaxy S5 was released and Sprint had a delay activating phones that day)....but then I installed a custom ROM and am having this problem now with the custom ROM.
Thought I'd post here to help others who stumble on this thread....
This removed Hands Free Activation for me on Sprint's HTC One M8:
j to the 4n said:
Re: Hands Free Activation ... http://forum.xda-developers.com/showpost.php?p=50392144&postcount=2287
Click to expand...
Click to collapse
This worked for me, but a couple notes:
- I wasn't able to do the command line or Root Explorer. Both methods gave me errors, seemingly that I didn't have permissions to rename or delete the file. Why would that be? I went into TWRP and 'Fixed Permissions' but that didn't help. -- found it interesting that boot up is a LOT slower now that I fixed permissions.
- I ended up going into TWRP, mounting system and then going into TWRP's file manager to rename the file. Now Hands Free Activation no longer comes up (Thank you!), but I also note that neither PRL Update or Update Profile do anything now. Not a huge deal because before they just errored out anyway, but I would think it would be important to be able to do PRL/Profile updates.
aprwx said:
Thought I'd post here to help others who stumble on this thread....
This removed Hands Free Activation for me on Sprint's HTC One M8:
This worked for me, but a couple notes:
- I wasn't able to do the command line or Root Explorer. Both methods gave me errors, seemingly that I didn't have permissions to rename or delete the file. Why would that be? I went into TWRP and 'Fixed Permissions' but that didn't help. -- found it interesting that boot up is a LOT slower now that I fixed permissions.
- I ended up going into TWRP, mounting system and then going into TWRP's file manager to rename the file. Now Hands Free Activation no longer comes up (Thank you!), but I also note that neither PRL Update or Update Profile do anything now. Not a huge deal because before they just errored out anyway, but I would think it would be important to be able to do PRL/Profile updates.
Click to expand...
Click to collapse
Thanks for the heads up about this. I just changed the .apk to .bak with root explorer, noted the path and file name so I can change it back to update the pir and prl. Mine didn't usually error out.
aprwx said:
I've seen several discussions about this around the web, but none of the solutions I've read have helped me.
I have the Sprint HTC One M8 with custom ROM (ViperOneM8). The phone is activated and works fully, yet on reboot I always get the 'Hands Free Activation' wizard. If I hit Activate and then Done it goes away and I can use my phone normally, but every reboot brings it back up again.
Ideas?
Click to expand...
Click to collapse
I'd find another ROM.
I think you are always safest to stay with Sprint "Native" ROMs on a Sprint Phone. Mainly because the developer usually doesn't have a Sprint Phone to fully flesh it out on a regular day to day basis. There are subtle differences between all the carriers. You also end up with a Build of Android that exactly matches the corresponding build of Firmware.
Once you do get back on a native ROM you *MIGHT* have to do a ##72786# (full wipe) to get things back in order.
What I think are related issues lead me to a fix that was common to several problems I was having:
http://forum.xda-developers.com/sprint-htc-one-m8/general/fix-data-issues-t2819915
simply freeze vDM
I have a (previously) rooted D950, and I can't get the OTA At&t update to install. I've completely removed root, and double checked through root checker that it's gone, and the update errors out every time with a message about having been rooted.
I read another thread where some people report being able to retain root after receiving the update THEN downgrading and rooting 4.2.2., then installing the OTA again, but it seems that I jumped the gun and rooted first, which is now causing the install to error out.
Has anyone else experienced this? Found a workaround? Ideas? Totally frustrating.
Sent from my LG-D950 using xda premium
Here is the link to a detailed guide . Dev hyelton's page includes links to AT&T ROMs.
If you need help with LG Flash Tool:
- Connect your phone with usb to laptop/computer and open device manager
- seek for Ports: COM & LPT, right click onto Android LTE usb port connection, click "properties", click "Advanced", then change port number to number 41, click "OK"
- DOWNLOAD LG Flash Tool and install .exe
- DOWNLOAD MegaLock.zip (3kb), unzipped (7kb)
- Exchange MegaLock.dll in your system folder "LG" with the unzipped MegaLock.dll file that you have downloaded
- Open LG Flash Tool, input .dll file of downloaded stock rom.zip folder and input .tot file of this folder
- Click onto USB instead of LAN, then click "OK"
- Left arrow at the window top should be enlightened now
- Click onto this arrow
- Wait for all popup windows telling milky way download and connections to fail
- Wait then for the check of CRC and .dll files
- One or all ports should be opened, "READY" enlightened
- Disconnect your phone from computer
- Connect again and watch the immediate start of the flashing process
- After completion you must install most of the app updates, update your LG and/or AT&T profile before installing kitkat update.zip
If you'll stick in updating stock rom to kitkat, watch my video on YouTube (it's about LS995 Sprint, but AT&T LG Flex will proof the same installation process):
Visit my blog at http://www.myreviewsofreviews.for the detailed description how to avoid bootloop during the installation of LG Kitkat update.zip via ADB sideload
Thanks, but this is not a fix. Unfortunately, that guide is of no use since his links are still down. Further, I was hoping for feedback from others who have experienced this issue, and found a resolution. I have read that this is also happening on devices that have not been rooted.
I am not looking to flash a rom through FlashTool. I'm looking to fix the OTA error. All I want to do is install the OTA update.
lorawithano said:
Thanks, but this is not a fix. Unfortunately, that guide is of no use since his links are still down. Further, I was hoping for feedback from others who have experienced this issue, and found a resolution. I have read that this is also happening on devices that have not been rooted.
I am not looking to flash a rom through FlashTool. I'm looking to fix the OTA error. All I want to do is install the OTA update.
Click to expand...
Click to collapse
Not sure what you were hoping for but the guide is correct process for your problem. You need to flash back to 4.2, don't touch anything in the way of modifying system files or deleting bloatware, sign into your main Google account, update all your apps...then root the phone and when it reboots look for the ota. I would give it a couple min to setup after flashing back to 4.2 so that it successfully finds the update rather than telling you you're on the most current software. I had your exact problem too, I was one of the first AT&T users on here to take the update I tried everything to
A: retain root with supersu features and some root cloaker programs etcetera
B: factory reset, call AT&T, to get them to push the update again because I just could not get it to successfully flash without detecting suspicion of root.
Flashing back to 4.2 to retain root worked for me over 4 times now on 3 different flex phones (I had some hardware and then software issues on my replacement model)
Sent from my LG-D950 using XDA Premium 4 mobile app
brittoking said:
Not sure what you were hoping for but the guide is correct process for your problem. You need to flash back to 4.2, don't touch anything in the way of modifying system files or deleting bloatware, sign into your main Google account, update all your apps...then root the phone and when it reboots look for the ota. I would give it a couple min to setup after flashing back to 4.2 so that it successfully finds the update rather than telling you you're on the most current software. I had your exact problem too, I was one of the first AT&T users on here to take the update I tried everything to
A: retain root with supersu features and some root cloaker programs etcetera
B: factory reset, call AT&T, to get them to push the update again because I just could not get it to successfully flash without detecting suspicion of root.
Flashing back to 4.2 to retain root worked for me over 4 times now on 3 different flex phones (I had some hardware and then software issues on my replacement model)
Sent from my LG-D950 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You say flash back to 4.2, but I am already on 4.2. Never left 4.2. That's the issue. The device is defective. They're sending me a new one.
lorawithano said:
You say flash back to 4.2, but I am already on 4.2. Never left 4.2. That's the issue. The device is defective. They're sending me a new one.
Click to expand...
Click to collapse
You didn't understand my post at all it seems, I gave you the instructions to flash back to STOCK which would have fixed your problem. I did accidentally word my post incorrectly saying "flash BACK to 4.2" obviously I knew you were on 4.2, so clearly I meant use the aforementioned guide to flash back to stock then take the update. Looks like you went another route, congrats
Sent from my LG-D950 using XDA Premium 4 mobile app
Huh? Wut
Not sure where things went wrong here.....
Me thinks some thread cleaning is in order...
Stand-by....
Cleaning finished.
Come on folks, let's relax and take a breath. Sometimes things just don't work and there's little to be done about it. If common known procedures don't work, then hopefully something else will, and just move along to something else.
Or in this case, the device is being returned which of course solves all.
No need for anybody to get all bent out of shape, what started out as being helpful, just took a bad turn somewhere for unknown reasons.
Relax, be cool....
MD
KitKat update on ATT G FLEX running on Tmobile.
This might be a stupid question . I have my ATT G FLEX D950 running on Tmobile. It is on Jellybean . I am unable to pull the Kitkat update and it says "Phone is not registered on network". I am assuming I need to get my phone on ATT network to pull the update. Am I right? is there any other way out ?
santy83 said:
This might be a stupid question . I have my ATT G FLEX D950 running on Tmobile. It is on Jellybean . I am unable to pull the Kitkat update and it says "Phone is not registered on network". I am assuming I need to get my phone on ATT network to pull the update. Am I right? is there any other way out ?
Click to expand...
Click to collapse
Kinda, yes.
I had the same problem. My phone was never activated on the ATT network so it would not recognize it. You have 2 options:
Get a prepaid sim from ATT, use it once and than put your Tmobile sim back in there or ask a friend that has ATT to use the sim for a few minutes. A text or a phone call is all you need.
Worked great for me.