Related
as the title says, after rooting, i am unable to check for any firmware updates. i realize it doesnt mater right now as there is noithing out right now, but i like to check often just in case tmobile releases something or samsung. when i go to check for updates by selecting settings>software update and then a warning message pops up: DM initalisation is not ready, Check network or SIM card
Any ideas would be greatly appreciated
I was about to ask this same question, and yes i am also rooted. Just wanted to post that you are not alone on this one.
thats good to know, i was beginning to wonder if i was the only one having this problem, for now i unrooted and flashed back to stock using odin, but i miss having root and some of the apps i was using. I am not willing to give up the ability to check for new firmware though as my source at work told me that updates are coming in the next 2 weeks and that we should be getting a text message about them in the next week or so. and just so people know, it wasnt a tmobile customer service rep, i work for deutsche telekom so we here things first usually.
I have this same issue, where I'm unable to check for firmware updates. I am not rooted though... I just bought the phone today and when I click the 'Software Updates' option it says 'No firmware' in a pop-up message. This problem is not only associated with rooted devices.
joshuapurcell said:
I have this same issue, where I'm unable to check for firmware updates. I am not rooted though... I just bought the phone today and when I click the 'Software Updates' option it says 'No firmware' in a pop-up message. This problem is not only associated with rooted devices.
Click to expand...
Click to collapse
Read the first post again... yours is the normal message that is displayed when no firmware update is available...
Also, I'm rooted and the update seems to be working fine.
I'm rooted and it pops no firmware.
Sent from my SGH-T959 using XDA App
If I flash back to stock it works fine when I use odin to go back to stock, but if I reroot it says the same thing. Nothing ever stops it from saying what I posted in the OP. I need some help funding a fix or ok won't be able to get the froyo update when it releases.
Sent from my SGH-T959 using XDA App
If I use oclf to root and apply the fix, then unroot using oclf, will the factory ota not work?
Sent from my SGH-T959 using XDA App
Duuude don't worry about it. People will post ROM clockwork backups of the froyo release / stock odin flashes of it / etc.
Anyone will be able to update, however they do so... And just wait til you hear about it THEN unroot and update
yep i'm rooted to and it checks for filmware just fine .
im rooted and get the no firmware message
r0me0ne said:
im rooted and get the no firmware message
Click to expand...
Click to collapse
... *sigh* Because there isn't a UPDATE for the Vibrant.
IF I ROOT, WILL I GET OTA UPDATES?
Yes. Rooting will not prevent this, unless you flash a custom ROM that will block receiving the OTA update. If you do receive and download the OTA update, you will lose root. Typically within hours of the OTA becoming available, thanks to some fine XDA folks you can get the update WITH root. You would simply need to download and flash the update like a normal ROM.
Click to expand...
Click to collapse
Rooting doesn't mess with your OTA updates, when you update with the OTA it will remove your ROOT. The only way to interfere with OTA's are flashing custom ROMs.
But you cannot get the ota update when it releases if the check for update option under settings is not working. All I want to know is why the firmware update option is broken and how to fix it.
Sent from my SGH-T959 using XDA App
When I first got my phone I got the message Check network or SIM card. I rooted the phone and still got that same message. I restored to origanal and got the message'No firmware'. Now again I am getting Check network or SIM card.
tpreludesh said:
But you cannot get the ota update when it releases if the check for update option under settings is not working. All I want to know is why the firmware update option is broken and how to fix it.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
It seems like your phone was more than just rooted. What method did you use to root?
Note: Yeah, the "No Firmware" message is the normal message you get if there's no update available, aka, your phone is searching for and/or receiving OTA updates just fine.
Leoslick said:
If I use oclf to root and apply the fix, then unroot using oclf, will the factory ota not work?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
This was my plan. Although, I'm reading posts that imply that even though a phone is rooted, if the user hasn't flashed a custom ROM, they'll still get the OTA update, and getting the OTA update will unroot the phone.
When this happens, root-necessary apps like ryanza's lag fix, titanium backup and android system info won't work anymore right? Will they need to be uninstalled and reinstalled? Or will I just need to re-root?
Sorry, I'm new to Android and don't know the typical process stock ROM root users go through with OTA updates.
Genuinely, thanks for any feedback.
Yes I wanna know this too. I'm holding off on getting apps for root only because I think they might mess something up. Also I thought I read set cpu spook might mess up the vibrant running oclf. Anyone?
Sent from my SGH-T959 using XDA App
Help.
I have a rooted Thunderbolt and I have been able to reject the update from Verizon until this afternoon when my phone started to update on its own. The update didn't go through and I got an error icon. Now my phone just goes through the same cycle of turning it self off and trying to update and crashing.
I am able to get to the Clockwork Mod recovery page but the only option that works is the 'reboot system now', which starts the phone and the whole cycle of trying to update is started.
Does anyone have an idea of how to get my phone working again?
Thanks in advance.
Mike
I'm really sorry to hear that happened, I'm not sure what you can do. Hopefully someone will be able to help you out. But at least I can tell you that you are not alone! I wasn't rooted, but my phone did autoupdate on its own at about 2:30pm today.
I posted about it here: http://forum.xda-developers.com/showthread.php?t=1234844
Pull your SDcard, wipe the pg05img.zip file, and try again. You might have to reflash clockwork.
This is the problem with running rooted stock ROMs. I know flashing a new ROM isn't what a noob wants to do, but it will avoid these very confusing headaches.
whats if you rooted using revolutionary? As far as i know there wont be that pg05img.zip file to delete.
Would you always be in danger is this if you are rooted and stay stock?
Why would someone want to root their phone and stay stock ??????
Sent from my Verizon LTE 4G Thunderbolt
loonatik78 said:
This is the problem with running rooted stock ROMs
Click to expand...
Click to collapse
Nope. One only has to keep up with the current releases, rooted versions of which come out within days of official release.
Are you sure it is the Verizon update?
I have the same behavior on my T-bolt since about 10 pst today. However, just before the phone shuts down to reboot, I see a note about a new version of Clockworkmod Recovery 4.0.1.5.
So I have been working on the assumption that it is CWM Recovery that is doing an automatic update.
I also am running rooted stock, and have not updated to latest release.
OK, it isn't the update to CWM Recovery that is the problem; it is the Verizon OTA update, which they have figured out how to force on us. I fixed my phone using the solution given by Mike later in this thread.
jbh00jh said:
Why would someone want to root their phone and stay stock ??????
Sent from my Verizon LTE 4G Thunderbolt
Click to expand...
Click to collapse
Debloating. Stock is pretty damn nice without all the extra crap.
*Madmoose* said:
Debloating. Stock is pretty damn nice without all the extra crap.
Click to expand...
Click to collapse
This, plus "root while you can" - there's no guarantee that rooting will be possible with each subsequent (unrooted) release, but you can root now and stay rooted to keep your options open. Also, getting full backups of everything is easier when rooted.
Did the fix work?
Mike, did you try what loonatik suggested? Did it work? Waiting breathlessly...
Unless I am misunderstanding the problem wiping cache from Clockwork recovery should clear out the update and it will quit trying to install it. For the future if you go to settings in the about phone or software update section (dont remeber which) there is an option to de-select scheduled update checks.
Sent from my HTC Thunderbolt
Wait.. what? Most ROMs I've seen are debloated.. At the very least they have VZW crap removed
Thanks guys for all your help and interest. I tried the solution offered by lunatic but it did not work. Thanks any way I was still looping through continuous on and off cycle. I did however did find a solution on another site. Here is the solution from Sele.
http://www.thunderboltforums.com/forum/htc-thundebolt-hacking-guides/2257-rs-guide-how-get-rid-ota-forced-reboots-rooted-phone.html
It was easier fix than I thought it would be. Step #1 worked.
I also did this to stop the update from happening again.
"If you are rooted use root explorer or super manager and set system to R/W. Then navigate to /system/etc/security. Find the file named otacerts.zip and rename it to otacerts.zip.bak and reboot. Should fix you up."
I'm sorry I can't remember who offered this solution to give credit to. I haven't had any updates yet but only time will tell.
Good Luck with your phone.
JBO1018 said:
Unless I am misunderstanding the problem wiping cache from Clockwork recovery should clear out the update and it will quit trying to install it. For the future if you go to settings in the about phone or software update section (dont remeber which) there is an option to de-select scheduled update checks.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
Yes you are correct wiping the cache fixed the problem.
mjkusa said:
Thanks guys for all your help and interest. I tried the solution offered by lunatic but it did not work. Thanks any way I was still looping through continuous on and off cycle. I did however did find a solution on another site. Here is the solution from Sele.
http://www.thunderboltforums.com/forum/htc-thundebolt-hacking-guides/2257-rs-guide-how-get-rid-ota-forced-reboots-rooted-phone.html
It was easier fix than I thought it would be. Step #1 worked.
I also did this to stop the update from happening again.
"If you are rooted use root explorer or super manager and set system to R/W. Then navigate to /system/etc/security. Find the file named otacerts.zip and rename it to otacerts.zip.bak and reboot. Should fix you up."
I'm sorry I can't remember who offered this solution to give credit to. I haven't had any updates yet but only time will tell.
Good Luck with your phone.
Click to expand...
Click to collapse
Definitely a handy resource.. Every time a new OTA comes out, this is a very frequently asked question.
I suppose you could always use an RUU too
mike.s said:
Nope. One only has to keep up with the current releases, rooted versions of which come out within days of official release.
Click to expand...
Click to collapse
Based on how many of these threads I see, that clearly isn't what's being done.
When the OTA was released, I took my stock unlocked and rooted Rezound and did an RUU on it. I relocked it and RUU'd and made it completely stock.
I then took the OTA. I watched it do it, it downloaded and went into some sort of recovery mode and installed it.
I then re-unlocked it, rooted it, installed Amon Ra and then debloated and set it up. I did NOT restore a Nandroid on this phone.
And now every morning my phone is downloading the OTA and wanting to install it. If I say defer it tells me I can't. If I tell it OK, it doesn't do anything and tomorrow it will try to do it again.
What gives?
Did this phone take the update or not?
My guess is no. Go into more info on the screen that you have above.
Build starts with 1 no update.
Build starts with 2 OTA update
Build starts with 3 you took one of the early ICS Roms
Sent from my ADR6425LVW using Tapatalk
paulhoop said:
My guess is no. Go into more info on the screen that you have above.
Build starts with 1 no update.
Build starts with 2 OTA update
Build starts with 3 you took one of the early ICS Roms
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
I guess that means no? I suppose I should just RUU with the new OTA version, rather than the original and try to get the OTA to take?
SquireSCA said:
I guess that means no? I suppose I should just RUU with the new OTA version, rather than the original and try to get the OTA to take?
Click to expand...
Click to collapse
You have many paths in front of you my friend, depends on where you want to go.
It appears that you are original stock still, rooted with recovery.
Not sure what went wrong. You might want to check for a PH98IMG.zip file on root. Delete it, causes issues with HTBOOT and bootloader.
SquireSCA said:
When the OTA was released, I took my stock unlocked and rooted Rezound and did an RUU on it. I relocked it and RUU'd and made it completely stock.
I then took the OTA. I watched it do it, it downloaded and went into some sort of recovery mode and installed it.
I then re-unlocked it, rooted it, installed Amon Ra and then debloated and set it up. I did NOT restore a Nandroid on this phone.
And now every morning my phone is downloading the OTA and wanting to install it. If I say defer it tells me I can't. If I tell it OK, it doesn't do anything and tomorrow it will try to do it again.
What gives?
Did this phone take the update or not?
Click to expand...
Click to collapse
Didn't even look at the screenshots, but it took me downloading the update twice for it to completely update it. I did the exact same process, but noticed when it rebooted the first time it didn't complete the update because I checked right away and my radios didn't update. I downloaded it again and the second time it flashed everything properly.
So from what I can gather, the OTA was fairly buggy process for alot of people. That's why I even checked prior to unlocking and rerooting again. I wanted to make sure it worked properly.
mjh68 said:
Didn't even look at the screenshots, but it took me downloading the update twice for it to completely update it. I did the exact same process, but noticed when it rebooted the first time it didn't complete the update because I checked right away and my radios didn't update. I downloaded it again and the second time it flashed everything properly.
So from what I can gather, the OTA was fairly buggy process for alot of people. That's why I even checked prior to unlocking and rerooting again. I wanted to make sure it worked properly.
Click to expand...
Click to collapse
Yeah, seems like the best way to do it is to just grab the latest RUU and install that and call it a day. No having to worry about it taking, it already includes the latest radio and stuff.
How do you tell what radio your phone is running??
jmorton10 said:
How do you tell what radio your phone is running??
Click to expand...
Click to collapse
Settings->Phone->Software Information->More->
Baseband version is radio
paulhoop said:
Settings->Phone->Software Information->More->
Baseband version is radio
Click to expand...
Click to collapse
Lol, I realize that but what is it supposed to say??
Edit: NVM, I found the info
I didnt realize at that time, that the update he was doing would block root. If I factory reset, will it put me back to pre-update so that when i boot up the phone I can root it first thing? Thanks for any help.
hondaboi20002 said:
I didnt realize at that time, that the update he was doing would block root. If I factory reset, will it put me back to pre-update so that when i boot up the phone I can root it first thing? Thanks for any help.
Click to expand...
Click to collapse
From what I have read the answer is NO. I think you are SOL until a new root method is found.
So basically all I can do is take it back, pay 35 buck restock fee, get another phone and root as soon as I get it setup and not install that update?
hondaboi20002 said:
So basically all I can do is take it back, pay 35 buck restock fee, get another phone and root as soon as I get it setup and not install that update?
Click to expand...
Click to collapse
I believe that is your only option, yes. To my knowledge, there is no way to revert back and you're stuck. Unless you'd like to just keep your current phone and wait until someone roots the new update, but your only other option would be to exchange it.
In your opinion, do you think the devs will find a way to crack this update and obtain root?
hondaboi20002 said:
So basically all I can do is take it back, pay 35 buck restock fee, get another phone and root as soon as I get it setup and not install that update?
Click to expand...
Click to collapse
Correct. That is *IF* the new phone doesn't already have the update installed, or the sales rep doesn't install the update while activating it and getting it ready for you.
Rumor has it that they already have root, but aren't releasing how until they can find a way to also unlock/patch the boot loader. They are said to be afraid of having Samsung/Verizon block this root method before they can use it to unlock the boot loader. Will they ever get it? Will they ever release the root method? That is anyone's guess.
So for now, it looks like the 16gig DEV edition direct from Samsung, without warranty, is the only option if you definitely want to root and flash custom roms now and "forever". But is it still available? or did they sell out yet?
Spoke with my rep and he told me bring it back, exchange it and all he will do is activate it and hand it right over to me and will not install the update. Now once I do get the new phone without the update and obtain root, can or will that verizon update still try and come thru and ask me to install it?
You can block the OTA updater with titanium backup. I'm not on a stock ROM, so I don't remember the updater app name.
Sent from my SCH-I545 using Tapatalk 4 Beta
SDM
That sucks. You gotta keep your eye on those reps :cyclops:
i never let any sales person set up, activate or even power up any phone i buy. if they chose to do so i cancel the order and buy on line where it comes sealed. i always tell them i'm in a rush and i'll take care of activating it afterwards. only one has ever refused and i told him to cancel the sale since he decided to open a product i purchase without my consent. he did get me a new one after that.
hondaboi20002 said:
So basically all I can do is take it back, pay 35 buck restock fee, get another phone and root as soon as I get it setup and not install that update?
Click to expand...
Click to collapse
That is assuming the new phone you get isn't updated b4 u turn it on...
Sent from my SCH-I545 using xda app-developers app
Ok, got a new S4 and this worked !!
Ok, everyone I got a new S4 and activated at Verizon which it immediately started download pretty much as soon as it was turned on. I immediately disabled mobile data, turned it off and then took out the sim card. Once I got home, I hooked this baby up to my PC and rooted...success, finally! I used the I545 all-in-one-root tool which includes OUDS clockwork. http://www.droid-life.com/2013/05/30/all-in-one-root-tool-released-for-verizon-galaxy-s4/
My questions is I have installed ROM Manager so that I could do a backup, but when I first open ROM manager, it says I need to install a custom recovery even though I have OUDS clockwork built in. Do I need to install clockwork from within the ROM manager app? I can reboot into recovery, but its the OUDS "generic" recovery, for lack of a better word. Is that recovery good to go for backing up, flashing another ROM or do I need to use the ROM manager to install CWM from with the app itself? Hope this makes sense. Thanks everyone!!
I'm a VZW rep and every time I activate a new S4, the update automatically starts downloading and there's NO way to tell it to "differ" to a different time.
Trust me, its not OUR fault. It just happens sadly :-\
I too hope devs get a way to root past this OTA because I have friends that would like me to root for them, but the OTA just muscles its way through.
I haven't upgraded anyone to an S4 today, but will report back with more info when I do. I'm pretty sure that after we activate the phone, the download starts and the notification just sits there until you click it (then it updates) or if you restart the device, it may force the update. I'll test on my next customer and let y'all know the real answer
Sent from my SCH-I545 using xda premium
dopediculous said:
I'm a VZW rep and every time I activate a new S4, the update automatically starts downloading and there's NO way to tell it to "differ" to a different time.
Trust me, its not OUR fault. It just happens sadly :-\
I too hope devs get a way to root past this OTA because I have friends that would like me to root for them, but the OTA just muscles its way through.
I haven't upgraded anyone to an S4 today, but will report back with more info when I do. I'm pretty sure that after we activate the phone, the download starts and the notification just sits there until you click it (then it updates) or if you restart the device, it may force the update. I'll test on my next customer and let y'all know the real answer
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
My experience with the update is that it will tell you the download is ready and at that point you can postpone it to a later time. It even gives you a little wheel to select when to install the update. The phone is still completely rootable during that time. When the notification comes back you can again postpone until a later time.
brw9100 said:
My experience with the update is that it will tell you the download is ready and at that point you can postpone it to a later time. It even gives you a little wheel to select when to install the update. The phone is still completely rootable during that time. When the notification comes back you can again postpone until a later time.
Click to expand...
Click to collapse
That's what happened to me. During the initial setup it was downloading the OTA update. As soon as I could, I enabled "Airplane mode" to kill the update, but no, it had already downloaded and asked if it was OK to install.
I deferred it until 1:00 AM and immediately started the rooting process. Got root, installed SuperSU Pro and enabled Survival mode. I also installed Voodoo OTA RootKeeper, but that wasn't necessary.
So I'm now running stock with superuser available and protected. Unfortunately, no custom recovery.
Since I have been doing smartphones, I have NEVER updated, I wait until someone has tried it. and even then, I wait for a dev to cook it up. And everyone better hope you do not have to do any replacements thru the carrier, you WILL get a bootloader locked device with the newest release, NO bootloader fix.
Need to find alternatives.
k1mu said:
That's what happened to me. During the initial setup it was downloading the OTA update. As soon as I could, I enabled "Airplane mode" to kill the update, but no, it had already downloaded and asked if it was OK to install.
I deferred it until 1:00 AM and immediately started the rooting process. Got root, installed SuperSU Pro and enabled Survival mode. I also installed Voodoo OTA RootKeeper, but that wasn't necessary.
So I'm now running stock with superuser available and protected. Unfortunately, no custom recovery.
Click to expand...
Click to collapse
That's great news to hear! Unfortunately my location was dead yesterday and I didn't sell any S4's. Just stupid idonts to bubblegum chewing pop tarts and grandparents. Ugh *face palm
Sent from my SCH-I545 using xda premium
brw9100 said:
My experience with the update is that it will tell you the download is ready and at that point you can postpone it to a later time. It even gives you a little wheel to select when to install the update. The phone is still completely rootable during that time. When the notification comes back you can again postpone until a later time.
Click to expand...
Click to collapse
Yeah, I ordered my S4 online, and it let me defer the update. It downloaded, then said ready to install would you like to install now or later? I set the timer to 12 hours, rooted, installed recovery, flashed AOKP, and bam, no worrying about OTA updates.
Sent from my SCH-I545 using Tapatalk 4 Beta
hondaboi20002 said:
Spoke with my rep and he told me bring it back, exchange it and all he will do is activate it and hand it right over to me and will not install the update. Now once I do get the new phone without the update and obtain root, can or will that verizon update still try and come thru and ask me to install it?
Click to expand...
Click to collapse
What I suggest is what I did.
Do not place the sim into the phone.
My phone came from Wirefly.com without the sim card installed.
Power up without sim card, boot directly to download mode, connect to pc usb port, run Odin, follow rooting procedure.
Only after you freeze SDM using titanium backup, should you consider inserting the sim card.
Also while on wifi samsung will ask to install update, say no.
P. S. I installed samsung drivers, and Odin. I did not install kies which I have read also tries to install the update.
I have a rooted ATT M8 running the stock ROM. They recently released new firmware and my phone wants me to install. I can tell when they release one because I get a notice saying that "google services are running in the background."
I do NOT want the new firmware, but I can find no way to turn off the update service and it's causing my phone to reboot. I assume that installing this update will break my root. Anybody got any solutions?
I've been wrestling with this the last 2 nights as well. I also didn't want the firmware update. I also had the google services annoying me.
Here's my advice:
1. Take the firmware update
2. Reboot
3. Update SuperSU immediately (use the app itself, it will boot into TWRP and update as necessary, if you don't follow this step, your root WILL be broken, and your phone will likely get locked into a ~3minute reboot cycle).
You shouldn't be affected beyond this point, unless you're like me and your phone automatically reinstalls all the AT&T bloatware on every reboot.
Install Titanium backup and kill the update service. I think it is "Software Updates"
Then you won't have this problem. At least I don't.
lostangelintx said:
Install Titanium backup and kill the update service. I think it is "Software Updates"
Then you won't have this problem. At least I don't.
Click to expand...
Click to collapse
I use titanium backup and have looked for the service but the only one I see is called updater. And from what I can tell that's not the right one.
Hmm I haven't gotten any updates
Sent from my HTC One_M8 using Tapatalk
Alaris said:
Hmm I haven't gotten any updates
Click to expand...
Click to collapse
1.54 was the software version at release (April), then the started rolling out 1.58 in May. I haven't heard of any other updates rolling out yet, although an update to 4.4.3 or 4.4.4 is supposedly upcoming.
What version is your phone currently?
---------- Post added at 10:51 AM ---------- Previous post was at 10:44 AM ----------
jbwitt said:
I use titanium backup and have looked for the service but the only one I see is called updater. And from what I can tell that's not the right one.
Click to expand...
Click to collapse
Try what is stated in Post #7 here: http://forum.xda-developers.com/showthread.php?t=2752718
You can just "freeze" (instead of uninstall) the service if you're afraid of breaking anything.
Never mind. The poster above me answered it for you.
Ok I froze HTC dm. We will see what happens. I am running 4.4.2. Thanks everybody.
jbwitt said:
Thanks everybody.
Click to expand...
Click to collapse
There's a button for that.
redpoint73 said:
There's a button for that.
Click to expand...
Click to collapse
Mind telling me where? Nowhere do I see a thanks button. I'm not a forum expert, obviously.
Also, none of the above suggestions worked. Today, when I got home, the phone rebooted again. I believe getting on my wifi is what triggered it (like it was trying to download the new firmware again). I also tried accepting the update but that didn't solve it either. All it did was reboot the phone again when told it to install...and I'm still at 4.4.2.
EDIT: Err, never mind. I reloaded the page and the thanks buttons showed up.
jbwitt said:
none of the above suggestions worked. Today, when I got home, the phone rebooted again. I believe getting on my wifi is what triggered it (like it was trying to download the new firmware again). I also tried accepting the update but that didn't solve it either. All it did was reboot the phone again when told it to install...and I'm still at 4.4.2.
Click to expand...
Click to collapse
Interesting, it seemed to work for others. Try freezing updater, FOTA, and/or HTCdrm.
Freeze these
Updater.apk
HtcOMADM_SettingsPlugin_ATT.apk
HtcOMADM_ATT.apk