How do I disable OTA Updates on Nook 1.1? - Nook Color Q&A, Help & Troubleshooting

I need a clear answer on this one and the right direction to thread if there is one?

Don't think there truly is a "one and right direction", but check this thread out.
I would personally recommend sqlite and making sure that the setting survived a full shutdown and restart.

Pretty sure sqlite doesn't work, but okay.

khaytsus said:
Pretty sure sqlite doesn't work, but okay.
Click to expand...
Click to collapse
As far as I know there's one guy who reported it not working for him. I'd liek to see more datapoints before making up my mind on this.

FWIW, I did the OTAcerts thing on my wife's nook and never got an update from 1.01. I subsequently did sqllite to both and added otacerts to mine (which was on 1.1). Haven't been brave enough to turn on wireless and test if they still hold though for 1.2.

doncaruana said:
FWIW, I did the OTAcerts thing on my wife's nook and never got an update from 1.01. I subsequently did sqllite to both and added otacerts to mine (which was on 1.1). Haven't been brave enough to turn on wireless and test if they still hold though for 1.2.
Click to expand...
Click to collapse
If you do a nandroid backup, you can always get back to the prior status.
Of course, you won't be able to *stay* at the prior status if you ever turn on Wi-fi again if my experience is indicative of anything. It pushed the update to me twice in as many days, despite doing OTA certs and sqlite.
As others have noted, I'm just one data point. But this data point could not stay with rooted 1.01 past Monday. It never gave me the 1.1 update, either. That did seem to be successfully blocked. But after flashing my nandroid backup three times (and even trying a modified build.prop), I concluded I couldn't stop 1.2 unrooting me, so I gave up and loaded CM7 despite the irritating battery issues.

Related

I can't be the only one with this problem....

I was hit with the update before I knew better and it installed.
As soon as it restarted I can no longer access the top of the touch screen.
The notification bar, camera controls, web address bar, ect. there is basically a quarter inch dead spot at the top of my screen.
I tried factory and hard rests with no effect, the issue remains.
I did e mail HTC about this, but I'm not going to hold my breath on a reply, also the Sprint forums are down.
I installed the OTA last night.
My screen is not experiencing the issue you mentioned.
Might take it into a Sprint store for confirmation.
Good luck!
I am really enjoying mine.
I don't seem to be experiencing any issues since the OTA update either. It was the first thing I installed, even before my apps! I hope you get your problem worked out.
No problems here. I installed the OTA updates and have since rooted it as well. No problems.
3 Keyboards installed, Wifi-Tether(still working out the kinks) and its just moving along
no problem here either
Sent from my EVO using Tapatalk
Can we say it's pretty much safe now to go ahead and install the updates without worrying not being able to root after? Also did this update fix the SD Card issue for you? I've experience a couple times now that my card not being able to read until I remove it then place it back in. Even try formatting on the computer with a card reader but still no luck.
Both unrevoked and Toast's method still work after the OTA update.
Can we say it's pretty much safe now to go ahead and install the updates without worrying not being able to root after? Also did this update fix the SD Card issue for you? I've experience a couple times now that my card not being able to read until I remove it then place it back in. Even try formatting on the computer with a card reader but still no luck.
Click to expand...
Click to collapse
I don't know about being able to root after the update. But if you root before and do the update. You don't lose root. Well at least I didn't.
-------------------------------------
Sent via the XDA Tapatalk App
Take it back to the Sprint store and get a free replacement.
TheBiles said:
Take it back to the Sprint store and get a free replacement.
Click to expand...
Click to collapse
Save a trip. Make sure it's a service and repair site before you drive. Unlike other devices, sales only stores are not able to accept exchanges on the evo.
thecodemonk said:
Both unrevoked and Toast's method still work after the OTA update.
Click to expand...
Click to collapse
You should probably clarify that a bit. With Unrevoked, you actually apply the OTA and then root that version. With Toast's method, you're actually writing a version of the old rom onto the phone, thereby overwriting any OTA update you may have had. Then when you apply Flipz rom to it, it wants to update but can't because it fails.
So if you want the OTA, you gotta do Unrevoked for now. Just wanted to clarify that for folks.
sph33r said:
You should probably clarify that a bit. With Unrevoked, you actually apply the OTA and then root that version. With Toast's method, you're actually writing a version of the old rom onto the phone, thereby overwriting any OTA update you may have had. Then when you apply Flipz rom to it, it wants to update but can't because it fails.
So if you want the OTA, you gotta do Unrevoked for now. Just wanted to clarify that for folks.
Click to expand...
Click to collapse
Aha, thanks! I had just read that Toast's worked and hadn't looked much closer.
sph33r said:
With Unrevoked, you actually apply the OTA and then root that version. With Toast's method, you're actually writing a version of the old rom onto the phone, thereby overwriting any OTA update you may have had. Then when you apply Flipz rom to it, it wants to update but can't because it fails.
So if you want the OTA, you gotta do Unrevoked for now. Just wanted to clarify that for folks.
Click to expand...
Click to collapse
sph, since you seem to know what you're talking about, can I bug you with a noob question? Can I follow the first few steps of toast's root process (these):
- Power off the phone
- Hold volume down while powering the phone on. continue to hold volume down until you see the WHITE bootloader screen.
- After a few seconds it will begin to checking for files, and find PC36IMG.zip. while its doing this it will show a blue progress bar while its checking. (this takes 30 - 60 seconds to finish)
- It will then list all the images in the zip and ask you if want to flash. SAY YES
- When its finished it will ask you if you would like to reboot. AGAIN... SAY YES
- At this point it will boot into a rooted rom.
- YOU ARE NOW ROOT!!!
Click to expand...
Click to collapse
.....then just STOP and be able to run apps that require root access? Or, do I need to go through the whole process and load flipz ROM, which does not yet include the OTA update? Sorry if this is a dumb question, but I'm still learning the ins and outs of Android.
Hey I'm having the same problem with the notification bar only, I can access anything else just fine, but I can slide down the task bar at all. I bought the phone and the radio shack guy basically installed the ota as he handed me the phone, although my friend didn't install his ota yet and his task bar rolls down just fine. He postponed his ota because of this. BTW only way I can access it is by home screen menu button.
Ok just realised something since I was writing this from my evo in landscape mode.. I can open the task bar only in landscape not in normal mode. There's a bug right there, guess it only affects random users.
Update
I got my phone from the Sams Club (Radio Shack).
Called Sprint and they told me I am SOL as far as they are concerned, I have to deal with the place I got it from since it didn't ship from their warehouse (sounds like BS to me).
I can see why people are pissed at Sprint, they don't give a rats ass if my phone is having issues and will do nothing to help me get it replaced.
The guy at the Sams has been great the whole time and told me he will call as soon as they get one to replace it with, which since they are Radio Shack you have to figure that Sprint stores will be highest priority to get more phones so who knows how long it will take to get a replacement. I basically have a cool looking expensive battery eater.
I have had one e mail exchange with HTC and they told me to do a factory reset which I had already done twice before I resorted to "tech support". The reset does NOTHING to remove the OTA update. If this is in fact what caused this I can see nothing short of a wipe and reflash of the factory ROM to fix it. I am awaiting HTC's second reply.
I guess a rooted ROM may also be an answer, but since this phone is having issues already I don't know that rooting it would help my cause with getting it legitimately fixed.
A warning to all reading this, Sprint tech support will only tell you to remove the battery to try and remedy any issues you may have. They told me that is all they have been instructed to tell people with Evo issues.
chamelieon said:
Ok just realised something since I was writing this from my evo in landscape mode.. I can open the task bar only in landscape not in normal mode. There's a bug right there, guess it only affects random users.
Click to expand...
Click to collapse
Same here for me with the web browser I can use the upper right and left corners in landscape, but nothing in portrait; I can also drag the notification bar down in g mail in landscape. I will update my ticket with HTC.
Please log this problem...
with both Sprint and HTC.....I have the same problem. I "believe" it started after the OTA.
i'm having the same problem. just got my htc evo with sprint today. the notification bar was working fine until i installed the OTA update. everything else works fine except the notification bar will not work. the only way to access the notification bar is from the home screen by tapping menu and selecting notifications.
my brother got the phone friday when it came out and applied the OTA update and his is working fine.
i emailed HTC i will post the reply as well if anything is different.
i've googled this and apparently there are a few open forums on other sites with plenty of other people having this same issue. nobody seems to have a fix yet.
just a heads up when i called sprint they acted like idiots and told me they couldn't help and to take it to the sprint store to have them troubleshoot it.
that kinda irks me because after ending my 7 year relationship with t-mobile i really thought that sprint would be a little bit better. oh well... you win some, you lose some.
I didn't apply the OTA, but ran into this issue this morning. Taskbar would not roll down...It would start to for a split second, then snap back up.
A soft reset seems to have cured the problem for now.

Unable to update PRL or Profile

Every time I try to update my PRL or profile, I get:
Could not update your profile or PRL at this time. Please try again later. If the problem persists, please contact customer service
Error: Internal Error.
I'm rooted via joeykrim's 1 click root exploit. When I first got the phone, I was able to update the PRL successfully. Not sure if root is causing the issue. I was seeing the same thing on my rooted moment before this.
Anyone else having this issue?
you removed the Sprint .apks that are attached to this setting... i forget the full name of what they are acalled, but i think its something like
sprintandroidextension.apk
infamousjax said:
you removed the Sprint .apks that are attached to this setting... i forget the full name of what they are acalled, but i think its something like
sprintandroidextension.apk
Click to expand...
Click to collapse
Here is a list of the .apk's I removed:
amazonmp3.apk
Asphalt5_DEMO_ANMP_Samsung_D700_Sprint_ML.apk
Email.apk
Email.odex
MediaHubV102_Epic4G.apk
MyFiles.apk
MyFiles.odex
nascar09-prod-release.apk
KeyBoardSlideUpCounter.apk
KeyBoardSlideUpCounter.odex
LatinImeTutorial.apk
SamsungWidget_CalendarClock.apk
SamsungWidget_CalendarClock.odex
SamsungWidget_FeedAndUpdate.apk
SamsungWidget_FeedAndUpdate.odex
SamsungWidget_ProgramMonitor.apk
SamsungWidget_ProgramMonitor.odex
SamsungWidget_StockClock.apk
SamsungWidget_StockClock.odex
SamsungWidget_WeatherClock.apk
SamsungWidget_WeatherClock.odex
sfl-prod-release.apk
AlarmClock.apk
AlarmClock.odex
blazinazn said:
Every time I try to update my PRL or profile, I get:
Could not update your profile or PRL at this time. Please try again later. If the problem persists, please contact customer service
Error: Internal Error.
I'm rooted via joeykrim's 1 click root exploit. When I first got the phone, I was able to update the PRL successfully. Not sure if root is causing the issue. I was seeing the same thing on my rooted moment before this.
Anyone else having this issue?
Click to expand...
Click to collapse
Iv been having the same exact issue since updateDI18 and iv never rooted so...
GXnext said:
Iv been having the same exact issue since updateDI18 and iv never rooted so...
Click to expand...
Click to collapse
Sooo that's it? 160 views and nobody has anything?
I don't see what the big deal is. Even when I hadn't rooted my phone, I always got an error when trying to update profile or prl, so I don't see it as a big deal.
I remember there might be a way to update those things using your MSL (re: service programming).
Forgive My Brevity. To Be Or Not To Be...
I was also hav ing issues with updating my phone, even before I received the DI18 update, before I finally decided to root my phone. I had taken it in to the local store... they couldn't do anything to fix it, just did a bunch a resets and stuff. They had me call in to Sprint tech support, and basically got the same results. At this point, I was also starting to experience random reboots. Eventually they gave up and decided to replace my phone.
At the time, I didn't know much about rooting and stuff, so I didn't want risk it on a phone that wasn't fully functioning, just in case other issues arose later, then run into a problem getting it fixed because I had rooted my phone.
When I got my new phone, and everything worked as it should, I finally decided to root, and have never looked back.
I have been unable to update prl for the last few days. I get the message "internal error."
I'm rooted, using epic experience and the latest mixup kernel. The sprintandroidextension.apk is installed.
Does anybody have any idea what could be causing this?
KL4V1CL3 said:
I have been unable to update prl for the last few days. I get the message "internal error."
I'm rooted, using epic experience and the latest mixup kernel. The sprintandroidextension.apk is installed.
Does anybody have any idea what could be causing this?
Click to expand...
Click to collapse
Try turning your WIFI on or 4G then run it
rjmjr69 said:
Try turning your WIFI on or 4G then run it
Click to expand...
Click to collapse
Alright, I just tried this, no success. I did notice however that every time I try to update, it begins searching for prl and then data appears to turn off. Wifi turns off, 4g turns off, and even my 3g icon disappears.
Wiped everything 3x, installed latest epic experience along with phoenix kernel and the shabbypengquins latest battery tweak.
I was hoping this would work, but alas no. Same exact error.
KL4V1CL3 said:
Wiped everything 3x, installed latest epic experience along with phoenix kernel and the shabbypengquins latest battery tweak.
I was hoping this would work, but alas no. Same exact error.
Click to expand...
Click to collapse
I'm just hoping once Froyo comes out, it'll fix this issue.
Is there atleast a way to do it manually? With all of this 4g stuff going on there is more of a need to update more frequently I would think....
Sent from my Epic 4g using XDA App
http://androidforums.com/epic-4g-su.../188838-cant-update-profile-prl-firmware.html
They are talking about it here aswell. Not much luck though.
Sent from my Epic 4g using XDA App
I came across the exact same problem. I also dropped my Epic (way before the problem began) and cracked the chrome and paint on the side of the bottom right corner. I brought it into my Sprint store, they ran the prl update twice, it failed. They had a brand new non remanufactured Epic the next day. This one runs way better and the vibrates stronger when pushing keys. I suggest you bring it in and get a new one.
Forgot to mention I was outside of my 30 days, I had the phone for 60 days. They still replaced it.
Do as thou wilt be the whole of the law
Well ... Ok... I guess...
Sent from my Epic 4g using XDA App
I purchased mine from Radioshack, so I'm guessing the Sprint store won't be as helpful. I'm not quite ready to give up and try to use the warranty on it, this is just a little bit frustrating.
I was able to update the PRL before...
Also, there is a thread on SDX about the problem too.
KL4V1CL3 said:
I purchased mine from Radioshack, so I'm guessing the Sprint store won't be as helpful. I'm not quite ready to give up and try to use the warranty on it, this is just a little bit frustrating.
I was able to update the PRL before...
Also, there is a thread on SDX about the problem too.
Click to expand...
Click to collapse
I'd suggest waiting for froyo to come out and then try to see if you can update the PRL. That's what I'm hoping for anyways. If it doesn't work then, then it's going back.
If it turns out you have to bring it in, Sprint called it a defect in the phone so they didn't make me use insurance which also means I didn't get a refurb but a brand new one. Funny thing the very first time I ran the prl in store before walking out I got the internal error again but the salesman hit it again and it went through. I've been testing it for two weeks now and it works every time
KL4V1CL3 said:
I purchased mine from Radioshack, so I'm guessing the Sprint store won't be as helpful. I'm not quite ready to give up and try to use the warranty on it, this is just a little bit frustrating.
I was able to update the PRL before...
Also, there is a thread on SDX about the problem too.
Click to expand...
Click to collapse
Do as thou wilt be the whole of the law
I've been having the same problem the last two days. I'm not rooted or anything so I don't know what's going on but it's irritating.

[Q] I wish I were 18 again...

Tomorrow is my 46th birthday, and I have tried to stay on top of technological advancements as best possible given my busy schedule. What I have noticed is that my ability to digest the latest techno trends and techniques does have a limit, especially when it interferes with the approaching martini hour at afternoon's end!
I don't know if this is a question or a mid-life existential moment. I bought the Samsung Epic 4G last fall because it was supposed to be cutting edge in terms of hardware for Android, and I as many of you have expressed, I made the decision to buy the Epic because of the promised firmware update that was imminent.
Fast forward half a year, and I now have the 2.2.1 EB13 firmware, which is rooted. I received the SMS yesterday (Wednesday) afternoon from Sprint about Sprint ID coming, but no update. Since I am rooted on EB13 I have no idea whether or not I will ever get the OTA and the last time I tried ODIN I had to take a tranquilizer, so I have no desire to go back to 2.1 to get the OTA.
Will the EC05 OTA be appearing given rooting on EB13? EB13 is giving me problems. I loved moving many (most) apps over to SD (I have a 32 gig card). But WiFi is not good, and I lose the ability to play movies, audio files, visual voicemail, or even hear my phone ringer (all seem connected in terms of the error -- I get an "unable to play message" or "unable to open file" error). I have to turn the phone off completely, then back on, wait for the media scan, etc. for it to go back to normal, then the errors will come back. I was hoping that EC05 would fix this. Maybe not. In perusing and searching I see nobody else has reported these problems which did not exist on DI18 (although I do see reports of WiFi connectivity problems that appear similar).
Does anyone have a bag phone from 1988 they want to trade for my Epic? As I recall, it worked without any hassles or firmware updates. Although it didn't have Angry Birds...
UPDATE: Life is grand at 46 (almost!). I posted later the following URL:
hxxp://forum.androidcentral.com/epic-4g-rooting-roms-hacks/71389-odin-ec05-froyo-ec05-prerooted-cwm-v2-5-1-0-rfs-odexed.html#post761525
When I got home I did as instructed using ODIN, and now I have EC05, with root, no data erasure, all is well! I still see so much consternation going on in the other threads. If you go to this URL and follow the directions, it works without any issues. I noticed immediately my WiFi issues are issues of the past. You can either wait for Sprint/Google to OTA you, under certain limited conditions, or do this, and be whole. Your choice. JJP
There should be an ota coming for those on eb13. As long as you didn't remove any bloatware you should be able to install the update. Besides there might Even be an update.zip on here that you can use before you get the ota. And Odin isn't that bad. I know you worry that it might brick your phone but I've used it about 10 times so far and no problems here. As far as technology goes its developing extremely fast these days. Its hard to keep up with it. Good luck and if you have anymore questions or decide to Odin and need something don't hesitate to ask or even pm me. I answer really quick cause I have it send be an email when.I get a pm.
Sent From My Evo Killer!
Thank you, what a nice response. Hopefully an update.zip will appear for EB13. Stranger things have happened.
drplaud said:
Does anyone have a bag phone from 1988 they want to trade for my Epic? As I recall, it worked without any hassles or firmware updates. Although it didn't have Angry Birds...
Click to expand...
Click to collapse
Unfortunately, all the AMPS and Digital TDMA networks have long since been shut down, so it would do you no good
But I do have a bag phone haha
Sent from my SPH-D700 using XDA Premium App
I wish I was 18 again, but for other reasons.
Yeah it is hard to keep up with tech these days,it changes by the hour now. And Ill have to say that Android is fragmented,this makes it harder; Look at what 2 updates to 2.2.1 and a 2.2.1 leak has done to this Epic forum,it has become a mess,I just hope now that we have CM7 and probably the last update for atleast 6 months,we should start to see some serious progress.
Sent from my SPH-D700 using XDA Premium App
Odin is only a pain the first time around. Now that you have the proper drivers installed its just a matter of selecting the file and clicking the start button. The only thing you have to watch out for is finding the correct usb port that the driver was installed on. As long as you're plugged into the correct one you're golden.
I do not think I will receive the OTA as I used one click to root after installing EB13. Perhaps this is the time to go Bonsai as I understand it now has EC 05 built in. I apologize, but is there a primer on how specifically to go to Bonsai? I have never flashed before (as I thought I might be arrested). Thanks.
Sent from my Samsung Epic™ 4G
You mentioned you're rooted. Do you know if you have CWM3 installed?
Its all a little trial and error but once everything is properly installed flashing roms is a cinch. I'm a big fan of the ACS roms. Bonsai worked well on my phone but there were a handful of idiosyncracies present that I could not put up with. Of course YMMV but don't hesitate to try different roms until you find one that your phone works well with.
stir fry a lot said:
You mentioned you're rooted. Do you know if you have CWM3 installed?
Click to expand...
Click to collapse
I believe so. I used one click root (update.bat).
Sent from my Samsung Epic™ 4G
drplaud said:
I believe so. I used one click root (update.bat).
Sent from my Samsung Epic™ 4G
Click to expand...
Click to collapse
Cool. If you want to give EC05 a shot, go to this thread and download the modem.
http://forum.xda-developers.com/show....php?t=1003447
Insert the modem into the Phone section of odin and hit start
Put aside some time before proceeding. If you have the correct CWM installed it won't take more than ten minutes but play it safe.
Download a rom of your choice, plug your phone into your computer and place it in the root of your SD card. You can download multiple roms if you want to see which works best for you. You will lose all your data the first time installing any new rom as it is not really recommended that you transfer settings of apps between different roms. Once you find a rom your're happy with you can simply update it it with the newest version without having to wipe your data however. Its really not as bad as it sounds and the ACS rom comes with an excellent app recovery program called MyBackup Pro Root that you can backup your apps and data with. You can use it to transfer apps between different roms and even some data but data from different roms can sometimes give you problems and is not really recommended. I have transferred data with some apps without any problems however. Its really just data that is tied to the system itself that will probably give you problems.
Unplug your phone from your computer and long press the Power Button, select Reboot, and then quickly hold down the Power, Volume Down and Camera Buttons.
Now press and hold down the Power, Camera, and volume down buttons. It should boot to the samsung logo and then to a black screen with orange text on it.
Use the volume keys to navigate and the power button to make selections. Choose Wipe Data/Factory Reset and wipe it 3x, then do the same for the Cache Partition and Dalvik Cache which can be found in the advanced options.
Select Go Back and navigate to Install Zip from SD card. Choose the rom you downloaded to it and you're good to go.
If after you do the three finger boot and you're not brought to a black screen with orange text you will need to install the correct CWM. If its black with green you have an old version and if you get a different screen than that this means that you do not have CWM at all. If this is so, just navigate to reboot and press the Home key to select it.
Something to think about
Thank you for the very helpful responses. I will ponder what the best option is, but it may indeed be time to explore custom ROMS, and your responses have given me the courage to do so. Many thanks! Joe
If he doesn't have cwm3 then he's gonna have to run the one click root with cwm3 for eb13 to be able.to flash bonsai. If I were to guess he has cwm 2.5.1.0 installed. On another note HAPPY BIRTHDAY!!!!
Sent From My Evo Killer!
I would Odin to EC05 first and see if it fixes anything for you. If not, reboot your phone into CWM and if you have the correct (orange and black) version, just reboot load the ACS rom onto to your phone and give it a try. If you're not happy with it or even if you are make a backup with Mybackup Root and explore other roms until you find one that works for you.
If you make a backup I would advise making separate backups of your apks, data for your apks, and photos as it makes it much faster to get back to where you were originally. Another tip for my backup is after making one go to View and double check that it actually made one as sometimes it will not.
I would have thrown this phone away by now if it weren't for the ACS rom btw. Its much smoother, has better battery life, doesn't skip keys even without the patch that they will be implementing soon and doesn't have all the god awful bloatware.
musclehead84 said:
If he doesn't have cwm3 then he's gonna have to run the one click root with cwm3 for eb13 to be able.to flash bonsai. If I were to guess he has cwm 2.5.1.0 installed. On another note HAPPY BIRTHDAY!!!!
Sent From My Evo Killer!
Click to expand...
Click to collapse
Where do I obtain one click root with cwm3? Thanks.
musclehead84 said:
There should be an ota coming for those on eb13. As long as you didn't remove any bloatware you should be able to install the update. Besides there might Even be an update.zip on here that you can use before you get the ota. And Odin isn't that bad. I know you worry that it might brick your phone but I've used it about 10 times so far and no problems here. As far as technology goes its developing extremely fast these days. Its hard to keep up with it. Good luck and if you have anymore questions or decide to Odin and need something don't hesitate to ask or even pm me. I answer really quick cause I have it send be an email when.I get a pm.
Sent From My Evo Killer!
Click to expand...
Click to collapse
stir fry a lot said:
Odin is only a pain the first time around. Now that you have the proper drivers installed its just a matter of selecting the file and clicking the start button. The only thing you have to watch out for is finding the correct usb port that the driver was installed on. As long as you're plugged into the correct one you're golden.
Click to expand...
Click to collapse
I agree with all of these except that odin never gave me trouble even the first time i used it..
Odin is cake just read the simple directions and everything should be fine, people dont use there heads when they get that android dude and the computer on there epic, the most ive been through is acore of force closes but its so easy to fix,
people just dont read the instructions all the way through,
Yesterday i was scared to update the prl manually but i read step by step instructions had to play around and find what i needed to do which wasnt on the instructions, and it was cake, almost just as easy as clicking the system updates/update prl button in the settings
but 98% of the time the instructions are flawless and work as long as you read carefully and do step by step.
drplaud said:
Where do I obtain one click root with cwm3? Thanks.
Click to expand...
Click to collapse
Development section stickied
Called One Click Clockwork 3.0.0.6
Oh yes happy birthday as well, have a great one!!
IMO, if you are on EB13, and want to update to EC05, the EASIEST way to do it, if you can wait a bit, is to use the stock SWUpdate for EB13, which will convert your phone back to a clean fresh stock install of EB13, then once/when it is released, install the EB13 to EC05 update via the over the air process, then reroot and move forward.
that all depends on samsung/sprint releasing a EB13 to EC05 OTA update, and your ability to wait for it though

Bell Atrix , lost wifi, bluetooth and rebooting lots

Hey,
My phone started acting up after 1 month of upgrading to gb 2.3.6. My wifi and bluetooth wont turn on and my phone constantly reboots. I used CWM and did a full wipe. and flasehd the darkside ROM. Still i have the same issue.
Does anyone know what do I need to do to get my phone working?
Thanks
A friend of mine has the same problem, Im pretty sure thats a hardware issue already. !
running gb 2.3.6 #4 - still no wifi/bluetooth
Having the same issues. Does anyone know if wifi and BT share an antennae?
try flashing a differnt radio? for your phone specs
look in ihop thread or fruit cake thread for your radios
r0nz3y said:
Hey,
My phone started acting up after 1 month of upgrading to gb 2.3.6. My wifi and bluetooth wont turn on and my phone constantly reboots. I used CWM and did a full wipe. and flasehd the darkside ROM. Still i have the same issue.
Does anyone know what do I need to do to get my phone working?
Thanks
Click to expand...
Click to collapse
schufly73 said:
Having the same issues. Does anyone know if wifi and BT share an antennae?
Click to expand...
Click to collapse
I'm pretty sure this is a hardware issue... I have been having this problem myself, and have tried flashing many of ROM and Radio's since it has reared it's ugly head - all to no avail. The WiFi an Bluetooth do share the same Broadcom chip... maybe there's enough of us experiencing the problem that we can collaboratively order a dozen of these things (they only seem to sell in bulk).
Had the same issue, ATT had to replace the phone.
Any more news on this issue?
Same thing happened to my Atrix last week (Bell, 2.3.6, locked bootloader, unrooted).
Same here
Same problem on my original Atrix, which was replaced under warranty by AT&T six months ago. Recently my replacement Atrix has been having the same problem. Wifi won't enable and frequent reboots.
Although the phone should still be under the 1-year warranty, AT&T refuses to honor it because the screen is cracked (so much for Gorilla glass).
After getting two phones with the same problem, and hearing about countless others having the same problem, and getting screwed out of the warranty, this is definitely my last Motorola phone.
EDIT:
The "fix" that was originally posted here doesn't actually work. I'm almost certain that this is a hardware problem. As of now there is no software fix, if one even exists.
Check this thread for more info:
https://forums.motorola.com/posts/0c2f1387d6
I recommend that you post to acknowledge you have the same problem.
i tried the script and it tells me "oops... did NOT find wpa_supplicant.conf! any help?
cafe. said:
I found a permanent solution to the problem. It was probably more obvious than I originally thought it would be. This is probably what will fix it if you recently ran some sort of 3G tweak as it probably damaged/corrupted /data/misc/wifi/wpa_supplicant.conf. Before I get started with what what problems my phone was having:
-'Wifi Error' message when enabled
-Random reboots when trying to enable wifi
-Bluetooth worked fine (and if you are having issues with bluetooth it may be due to a similar bluetooth related file having problems)
-Impossible to fix by flashing new roms, wiping/factory reset, and virtually every other possible thing I tried
So, just before giving up, I found something called 3Gturbocharger--which can be downloaded from here: http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021 REMEMBER: IT'S 3GTURBOCHARGER, NOT ANY OF THE OTHER SIMILARLY NAMED FILES.
Now, the value of the script isn't really in the "tweaks" it provides, but rather the easy way it provides to reset the file of interest (/data/misc/wifi/wpa_supplicant.conf). Run the script using "script manager" as root, once you've done this you'll be able to run a feature within the script called Wi-fixer. Run it and reboot. The problems should all be corrected. You could also try to manually navigate to 'data/misc/wifi/wpa_supplicant.conf' and simply rename it to whatever you want (as the script does), at which point the old file will be replaced by a newly generated one.
I'm assuming that in your case the bluetooth equivalent of "wpa_supplicant.conf" was corrupted. Possibly /data/misc/bluetooth/dynamic_auto_pairing.conf or /data/misc/bluetooth/incoming_connection.conf. Worth a shot trying the method I described on those files as well. Try it out, you've got nothing to lose.
Click to expand...
Click to collapse
im getting that to
My Atrix wifi stopped working in the past, but started working again. It currently stopped working once more, giving me an Error if I turn it on. The Bluetooth has never had issues and still works, I am a month past warranty but with unlocked BL it doesn't matter anyway. This seems to be a slight issue with these phones unfortunately.
I could live with the phone without wifi, but the constant reboots are unavoidable. I notice that when I originally boot the phone, if I use it and keep the screen on it works, but as soon as I turn the screen off, it reboots. Odd to me.
Ya I have the Bell Atrix myself and I'm still on Froyo because of complaints of GB. (especially battery life) Maybe I'll do ICS, but I'll wait for some reviews since its not that easy to go backwards as say my OG SGS...
Sent from my MB860 using xda premium
Now, the value of the script isn't really in the "tweaks" it provides, but rather the easy way it provides to reset the file of interest (/data/misc/wifi/wpa_supplicant.conf). Run the script using "script manager" as root, once you've done this you'll be able to run a feature within the script called Wi-fixer. Run it and reboot. The problems should all be corrected. You could also try to manually navigate to 'data/misc/wifi/wpa_supplicant.conf' and simply rename it to whatever you want (as the script does), at which point the old file will be replaced by a newly generated one.
Click to expand...
Click to collapse
Anyone try doing this manually? I can't locate the file.
wpa_supplicant file
hi, the file is in etc/wifi and the bluetooth file is in etc/bluetooth/ i renamed the .conf files but this don't solved the problem.

Cannot update PRL or Profile Error codes

So for a while now I have not been able to update my PRL or Profile. It hasn't bothered me because for the most part the phone has worked fine until recently. A friend texted me and said he was going to call me. He text back a few minutes later and ask why I didnt answer. Phone was next to me the whole time and it didnt ring or so any kind of notification that he had tried to call. Took him 3 calls before my phone rang and he got through.
I have applied for a few jobs within the past few weeks and have heard nothing from anyone which I am surprised because I was referred to one company by and friend who put in a good word for me and said that his supervisors were really impressed with my resume. So now I feel like this issue could possibly be costing me job opportunities and I want to get it figured out.
The errors are 6602 and 407. I've tried to do it over 4G and put my phone just in CDMA mode for 3G only and get the 407 code for 3G and the 6602 over 4G.
I am running Stock rooted/odexed MK2 and I just did a clean flash of the rom again clearing data/cache and dalvik seeing if that would help which it didn't. I have reflashed the modem seperately also with no help.
I have seen many threads of others having this issue but no answers on a fix. Has anyone experienced this and actually done something that has resolved the issue?
If you feel it may be costing you a job, why not flash a nand of a stock rom, assuming you have one
Sent from my SPH-L720 using XDA Free mobile app
I did, I flashed back to MF9 using this http://www.rwilco12.com/Files/Devic...H-L720)/Stock ROMs/MF9/Full Restore/Unrooted/
Which should be a stock factory restore, still would not update profile or prl. From there I updated to NG2 with Samsung Kies and I am still not able to update either.
tenaciousj said:
I did, I flashed back to MF9 using this http://www.rwilco12.com/Files/Devic...H-L720)/Stock ROMs/MF9/Full Restore/Unrooted/
Which should be a stock factory restore, still would not update profile or prl. From there I updated to NG2 with Samsung Kies and I am still not able to update either.
Click to expand...
Click to collapse
What kernel do you use?
(I fixed this issue I my phone, but SERIOUSLY, what seemed to fix it MADE NO SENSE, so I'm not going to to relate it again, you can look up my posts if you want, but I wouldn't waste your time. I'm more interested in what kernel you are using... if it isn't KT-SGS4, then it doesn't matter.)
Other than that, have you tried the ##72786# dialer code, which is supposed to reset that stuff (didn't fix it for me personally)? You may have to reactivate your phone though (I did), which isn't that much of an issue...
rsngfrce said:
What kernel do you use?
(I fixed this issue I my phone, but SERIOUSLY, what seemed to fix it MADE NO SENSE, so I'm not going to to relate it again, you can look up my posts if you want, but I wouldn't waste your time. I'm more interested in what kernel you are using... if it isn't KT-SGS4, then it doesn't matter.)
Other than that, have you tried the ##72786# dialer code, which is supposed to reset that stuff (didn't fix it for me personally)? You may have to reactivate your phone though (I did), which isn't that much of an issue...
Click to expand...
Click to collapse
For kernel version it shows 3.4.0-2162929 which I'm guessing is the stock NG2. I haven't flashed anything else since updating through Kies to NG2.
I've done the 72786 dial code a handful of times and it still didn't help. The only thing that solved was a issue I had after I first updatd to NG2 I had no working 4G. Phone would only connect to 3G and that was when it was in CDMA only mode. Aside from that it hasn't helped with the PRL/Profile update issue I'm having.
tenaciousj said:
For kernel version it shows 3.4.0-2162929 which I'm guessing is the stock NG2. I haven't flashed anything else since updating through Kies to NG2.
I've done the 72786 dial code a handful of times and it still didn't help. The only thing that solved was a issue I had after I first updatd to NG2 I had no working 4G. Phone would only connect to 3G and that was when it was in CDMA only mode. Aside from that it hasn't helped with the PRL/Profile update issue I'm having.
Click to expand...
Click to collapse
Yeah, that does sound like a stock kernel to me. Have you tried updating it through the Sprint Zone app? In Settings, More Networks, Mobile Networks, Network Mode, if it is not set to Automatic, you can try setting it to that and see if it lets you update after reboot, I have heard that can help but did not fix it for me (I have it set to LTE/CDMA). Have you seen this thread: Galaxy S4/Note 3/Mega - Update Profile/PRL/HFA Fix for Sprint/Boost/Virgin Mobile/etc? It is complex (don't IGNORE steps 5, 6, 7 and 8, which most people in the thread seem to...). I have not personally used this method, I was planning to before my issue resolved itself, but I didn't have a donor GS4 either (damn it, I JUST remembered that I DO, I f*ed up the USB port on my first one and completely forgot about that! BLOW MY MIND! But anyways...).
rsngfrce said:
Yeah, that does sound like a stock kernel to me. Have you tried updating it through the Sprint Zone app? In Settings, More Networks, Mobile Networks, Network Mode, if it is not set to Automatic, you can try setting it to that and see if it lets you update after reboot, I have heard that can help but did not fix it for me (I have it set to LTE/CDMA). Have you seen this thread: Galaxy S4/Note 3/Mega - Update Profile/PRL/HFA Fix for Sprint/Boost/Virgin Mobile/etc? It is complex (don't IGNORE steps 5, 6, 7 and 8, which most people in the thread seem to...). I have not personally used this method, I was planning to before my issue resolved itself, but I didn't have a donor GS4 either (damn it, I JUST remembered that I DO, I f*ed up the USB port on my first one and completely forgot about that! BLOW MY MIND! But anyways...).
Click to expand...
Click to collapse
Thanks for the link I'll check it later. My account is actually a SERO account but I did have working updates when I first got the phone. The phone was also new and activated on the account as soon as I got it.
Sent from my SPH-L720 using Tapatalk
tenaciousj said:
Thanks for the link I'll check it later. My account is actually a SERO account but I did have working updates when I first got the phone. The phone was also new and activated on the account as soon as I got it.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Yeah, I honestly don't really understand what that thread means when it talks about flashing to legacy accounts. I believe I have a SERO account (I don't know, my wife pays the bill... :silly: ) and the updates worked fine until I think messing with the APNs to try to fix my inability to send MMS messages messed things up. I never flashed any legacy accounts or anything.
So... at this point, even though IT MAKES NO SENSE, I will tell you what SEEMED to fix the issue for me. I STRESS, this MAKES NO SENSE TO ME, but after months of being unable to update my PRL/PROFILE, after doing the following, I was suddenly able to update them. It is likely an EXTREME coincidence, but for the hell of it I will now tell you.
Using the Pro version of Solid Explorer, I copied the Carrier folder from the root of my phone to my external SD card. THAT IS IT. YES... THAT IS IT. NOTHING MORE. I did NOT copy it back, I did not change anything. HOW this could possibly have cured the problem would seem to make very little sense, I can only conjecture that Solid Explorer, in the act of copying the folder to my external SD card, somehow 'refreshed' something in the carrier folder in the root of my phone... and I am grasping at straws here. I think you can probably understand WHY I did not want to reveal that this is what SEEMED to cure my issue, because it is so unlikely, and more likely an extreme coincidence and something else happened that I am not aware of, but that is the only thing I know of that I did related between when it was not working to when it was. So now you know at least (and as I have told a few others, there is no point in not trying, other than the crushing disappointment of it almost certainly not working)...
I should add as well however, now that it occurs to me, that I use the KT-SGS4 KitKat 4.4 TouchWiz kernel, and had for a long time suffered from a loss of mobile connection and GPS. requiring a reboot to get them back (within a similar time period to my PRL/PROFILE issues). I seem to have fixed the mobile connection/GPS loss by choosing the 'correct' governor to use with that kernel for my ROM, and it is not IMPOSSIBLE that THIS occurred at the time I was able to update my PRL/PROFILE, but I do not remember exactly, and I'm PRETTY CERTAIN I still had the issue with the mobile connection/GPS loss after updating my PRL/PROFILE, so I think that likely rules out KT-SGS4 as a culprit in this issue. (But then, I was forgetting that we already established that you were on a stock kernel...)
KNOWN issues with KT-SGS4 Sprint KitKat 4.4 TouchWiz kernel
rsngfrce said:
Yeah, I honestly don't really understand what that thread means when it talks about flashing to legacy accounts. I believe I have a SERO account (I don't know, my wife pays the bill... :silly: ) and the updates worked fine until I think messing with the APNs to try to fix my inability to send MMS messages messed things up. I never flashed any legacy accounts or anything.
So... at this point, even though IT MAKES NO SENSE, I will tell you what SEEMED to fix the issue for me. I STRESS, this MAKES NO SENSE TO ME, but after months of being unable to update my PRL/PROFILE, after doing the following, I was suddenly able to update them. It is likely an EXTREME coincidence, but for the hell of it I will now tell you.
Using the Pro version of Solid Explorer, I copied the Carrier folder from the root of my phone to my external SD card. THAT IS IT. YES... THAT IS IT. NOTHING MORE. I did NOT copy it back, I did not change anything. HOW this could possibly have cured the problem would seem to make very little sense, I can only conjecture that Solid Explorer, in the act of copying the folder to my external SD card, somehow 'refreshed' something in the carrier folder in the root of my phone... and I am grasping at straws here. I think you can probably understand WHY I did not want to reveal that this is what SEEMED to cure my issue, because it is so unlikely, and more likely an extreme coincidence and something else happened that I am not aware of, but that is the only thing I know of that I did related between when it was not working to when it was. So now you know at least (and as I have told a few others, there is no point in not trying, other than the crushing disappointment of it almost certainly not working)...
I should add as well however, now that it occurs to me, that I use the KT-SGS4 KitKat 4.4 TouchWiz kernel, and had for a long time suffered from a loss of mobile connection and GPS. requiring a reboot to get them back (within a similar time period to my PRL/PROFILE issues). I seem to have fixed the mobile connection/GPS loss by choosing the 'correct' governor to use with that kernel for my ROM, and it is not IMPOSSIBLE that THIS occurred at the time I was able to update my PRL/PROFILE, but I do not remember exactly, and I'm PRETTY CERTAIN I still had the issue with the mobile connection/GPS loss after updating my PRL/PROFILE, so I think that likely rules out KT-SGS4 as a culprit in this issue. (But then, I was forgetting that we already established that you were on a stock kernel...)
KNOWN issues with KT-SGS4 Sprint KitKat 4.4 TouchWiz kernel
Click to expand...
Click to collapse
Yeah that copying the carrier folder don't seem like it would do anything but maybe I'll give it a try. Whats the best way to root right now? I just want to make sure it will let me unroot the phone if it dont work and no trip knox incase I have to bring this in.
Do you know what bootloader you are on? You said you were on Sys MK2, then went back to MF9 and now are on NG2. When you went to NG2, unless you took very specific steps to keep the MF9 bootloader, you would be on the NG2 bootloader now, which includes Knox, and you can no longer go back beyond NAE I think. If you don't know what bootloader you have, get DeviceInfo https://play.google.com/store/apps/details?id=com.jphilli85.deviceinfo from the Play Store and under the Software heading, see what it shows for the last 3 digits for Bootloader. This makes a difference on the best root method.
rsngfrce said:
Do you know what bootloader you are on? You said you were on Sys MK2, then went back to MF9 and now are on NG2. When you went to NG2, unless you took very specific steps to keep the MF9 bootloader, you would be on the NG2 bootloader now, which includes Knox, and you can no longer go back beyond NAE I think. If you don't know what bootloader you have, get DeviceInfo https://play.google.com/store/apps/details?id=com.jphilli85.deviceinfo from the Play Store and under the Software heading, see what it shows for the last 3 digits for Bootloader. This makes a difference on the best root method.
Click to expand...
Click to collapse
Bootloader and software version both show up as NG2 on Device Info.
tenaciousj said:
Yeah that copying the carrier folder don't seem like it would do anything but maybe I'll give it a try. Whats the best way to root right now? I just want to make sure it will let me unroot the phone if it dont work and no trip knox incase I have to bring this in.
Click to expand...
Click to collapse
I'm not an EXPERT on this subject, but if you are on NG2 stock unrooted right now, I believe you can use: CF-Auto-Root to root it. Or, here is a stock rooted version of the NG2 ROM:
[ROM][NG2] Stock Rooted NG2 (which mentions that it has Knox removed).
As far as tripping stuff, I'm somewhat unsure about that to be honest. I have always used Triangle Away on my phone, but it has a warning now not to use it with a custom kernel (which I use). My counter is at 3, but I am out of warranty anyway.
I spent a few hours on chat with Sprint. They couldn't figure it out so I'm bringing it in tomorrow. Guessing I'll get a new phone. The people at the Sprint store seem rather limited in their knowledge, at least they were last time I was there.
Sent from my SPH-L720 using Tapatalk
tenaciousj said:
I spent a few hours on chat with Sprint. They couldn't figure it out so I'm bringing it in tomorrow. Guessing I'll get a new phone. The people at the Sprint store seem rather limited in their knowledge, at least they were last time I was there.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I guess if there are no signs that it has been rooted, that's probably a good way to go. You apparently had a phone pre-Knox and now I think you will get one with a Knox system, but it doesn't matter in your case since went beyond the point of no return already with the bootloader... I don't know if you have the new Spark model (tri-band), I don't know if the still make the old plain one like I have anymore...
rsngfrce said:
I guess if there are no signs that it has been rooted, that's probably a good way to go. You apparently had a phone pre-Knox and now I think you will get one with a Knox system, but it doesn't matter in your case since went beyond the point of no return already with the bootloader... I don't know if you have the new Spark model (tri-band), I don't know if the still make the old plain one like I have anymore...
Click to expand...
Click to collapse
I got the phone I have now about a month after the GS4 came out so its non sparks. I stayed on MK2 for so long because I couldn't find a newer rom that looked to be stable and not have to jump through a bunch of hoops to install it. The Odin screen shows everything being zero and offical software so I should be good. I am going to sign out of all of my accounts before I bring it in being I have a lot of apps bought through the store that only work on rooted phones. I hope I can get a tri band to replace it. My friend has a triband GS4 and it gets much better data speeds than mine.
Yeah, I mentioned elsewhere here before that I actually didn't know of the existence of the "Sparks" version of the G4. I screwed up the USB port on my G4 before upgrade time, so I had to buy another G4 on Amazon. Upgrade time has come up, so I was just looking and saw my phone listed as "Non-Sprint Sparks", which I thought meant that they called it the "Sparks" model because I hadn't bought it from Sprint... took me a while to figure out what that actually meant... :laugh:
Sprint online nor the store could fix it so I got a new one.
No rooting but error 407
As titled, I've not rooted the phone. I'm getting error code 407 on attempts to update PRL and Update profile. Download updates manually does nothing. Note I'm on a Samsung Note 4, Sprint. Had updated to Marshmallow 6.0.1 late March but then above actions persist since then. I'm using Wi-Fi only, Sprint service disconnected as I couldn't pay bill when I lost job during a disabling illness.
I haven't been able to update prl profile or firmware for over 8 months. I am not rooted never have been I have called customer service over and over replaced SIM card did the ## stuff nothing has helped. The phone works although service isn't as good as it could be and says there is a prl update available but I always get connection error 6 on all 3. I also have serious battery draining issues as far as my data I do get a strong 4g lte connection just service is low and sometimes drops when I am close to a sprint tower every other phone gets full bars really on any network especially sprint. I hope someone can help I like my sph-720 other that that and honestly I can't afford to keep up with the Joneses. Hopefully this is enough info please help
00Lee said:
I haven't been able to update prl profile or firmware for over 8 months. I am not rooted never have been I have called customer service over and over replaced SIM card did the ## stuff nothing has helped. The phone works although service isn't as good as it could be and says there is a prl update available but I always get connection error 6 on all 3. I also have serious battery draining issues as far as my data I do get a strong 4g lte connection just service is low and sometimes drops when I am close to a sprint tower every other phone gets full bars really on any network especially sprint. I hope someone can help I like my sph-720 other that that and honestly I can't afford to keep up with the Joneses. Hopefully this is enough info please help
Click to expand...
Click to collapse
Have you done a factory reset via recovery? Or you might want to flash latest full stock

Resources