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
I finally managed to find the right fastboot file (I think) to get me back to stock on my Verizon RAZR Maxx. The RAZR utility wouldn't work, but RSD lite did...sort of. At the end of the program while the phone was rebooting it got hung in the boot loop. I returned to the menu using pwr/vol+- and selected normal boot, and I got through the boot screen. RSD was hung up so I just closed it. Now I'm trying to get root back using the RAZR utility and the ICS installer, and it keeps saying that the system can't find the file specified. I haven't read where anyone else has had this problem...am I missing something?
I read that you have to manually push files using terminal window.
http://www.droidrzr.com/index.php/topic/1598-how-to-guide-restore-root-after-installing-ics-leak/
Never mind dont think this explains your problem.
I had a similar problem. I got into a boot loop but was able to at least restart.
I installed voodoo and I think what I did is didnt install new super user and go from there. So I couldnt use the terminal commands. Not gonna start over at the moment.
Okay...just for giggles I used rsd lite to restore back to .748 2.3.5 instead of .173 2.3.6. Everything went very smooth, and I was able to use the phones update setting to update the firmware to .173 2.3.6 without a hitch. But still every time I try to use the razr utility to root it still says system cannot find path specified over n over again. I even downloaded root checker to make sure there were no remnants of root before reverting and all was good. I'm totally lost...please help.
have you tried using the "motofail" to root your 2.3.6?
Update your driver. Even if it is current still do it. That fixed my problem with using the utility.
Sent from my DROID RAZR using Tapatalk 2
flashman2002 said:
Update your driver. Even if it is current still do it. That fixed my problem with using the utility.
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
Yup, that's more than likely the problem. I was having trouble at first and after installing the updated drivers (think the link is in the same post) everything worked perfectly.
\\Carved into this thread by my ICS RAZR//
http://android-gz.com
I would like to thank everyone for their input and suggestions. I am finally running ICS on my RAZR Maxx!!! I went back and deleted the .rar files, re-extracted them using a different zip program, and the rest is history. I thought I would post my solution just in case it helps someone else down the road.
Droid X2 owners i have figured out how to root the new 2.3.5/1.3.418 update. I spent a couple hours trying to get this figured out. Its simple and very easy to do well may not be for some but here you go just follow these simple steps and all that trouble that everybody is having.... here is the solution! First off do a hard reset from phones setting under privacy make sure to copy and paste pictures, music etc. to your computer cause you will have to check internal storage to be deleted for this to work ..after the reset u are going to sbf back to original 2.3.4 with (RSD Lite) Remember it has to be done in this order just take my word for it ...when finished.. phone will reboot let all factory apps download and install including gmail,
vz navigator, google books etc. You will not have to keep these apps you just have to let them install for this update after you sbf 2.3.4 and back to original. When your done with sbf file and have re-activated phone added google account etc... Get (Petes Motorola RootTools_v1.07.zip) no other rooting methods worked ive tryed it.. type that into google search it should find his site.. and make sure to download (Windows Universal drivers) for computer depending on what you have 32 bit operating system or 64 bit.. both of these files can be found on petes site. After downloading drivers and zip file..... unzip petes zip and click on (petes motorola root tools). I had one issue with this when trying to root device i had to put phone into pc mode for some reason. And if still having issues try running the adb temp rooting procedure this seems to work everytime. Run rooting method till done then u should be rooted after this is done dont mess with SU leave it as is for now.... Now you are going to want to head to the the google market on your phone and type (ota rootkeeper) and download that app. After this is done you can go to that app and and press protect root it should say something like su safe or something like that at the bottom after u have pressed it. Now when u are sure u have all these done correctly go to your phone settings and go to about phone and press on system update and download and install the OTA update 1.3.418 to your phone. It will reboot and and install update after this is done let phone load back up and do what it needs to do. Now go back to google market and install (ota rootkeeper) again and you should get only one option and that is to restore root.. press that and there you have it. Now you can update SU, remove unwanted apps, etc.. Do whatever you please. This update has caused so many droid x2 owners to get very ticked off but luckily i found the solution to all the problems. If anybody is having any issues trying to get this done leave posts and messages i will help you out as much as i can. This process went really smooth you should have no issues at all. And if ur wondering about 2.3.5/1.3.418 update it is definitely snappier with and even more snappier with bloatware apps removed. Install the droid X2 bootstrap manager just like u always would. Dont hesitate to leave questions i will try to get back to them as soon as i can. HAVE FUN ROOTING> 2.3.5 And by the way for the people wondering I run this all on stock rom I dont use eclipse, affinity , etc or any other custom rom this is all straight stock rom
ZergRush also works for 2.3.4
RacerXFD said:
ZergRush also works for 2.3.4
Click to expand...
Click to collapse
Heard zergrush changes something and won't let update work or something have to use Petes
Sent from my DROID X2 using XDA
2.3.5 ruined my root droid x2
Got my phone unrooted from this update. I SBFd it back to 2.3.4 in a similar manner using moonshadows post on how to do that. (Took forever) than I rerooted with Petes 1 click roo also downloaded voodoos rootkeeper. Moved it to SD card with TB backup Saved my root. Backed up all my stuff (including rootkeeper) with paid titanium backup app...booted phone on fast boot. Wiped files. Booted back up. Did all the updates than loaded rootkeeper(which was on my SD ccard. Restored root with no problems ran TB backup installed update to 2.3.5 angreat. everything is running great. Running stock ROM. Don't know much but can try to help. Not** I couldn't load my nandroid back up using Tom manager system recovery after update
Thanks for the help.
mnkurk1989 said:
Droid X2 owners i have figured out how to root the new 2.3.5/1.3.418 update. I spent a couple hours trying to get this figured out. Its simple and very easy to do well may not be for some but here you go just follow these simple steps and all that trouble that everybody is having.... here is the solution! First off do a hard reset from phones setting under privacy make sure to copy and paste pictures, music etc. to your computer cause you will have to check internal storage to be deleted for this to work ..after the reset u are going to sbf back to original 2.3.4 with (RSD Lite) Remember it has to be done in this order just take my word for it ...when finished.. phone will reboot let all factory apps download and install including gmail,
vz navigator, google books etc. You will not have to keep these apps you just have to let them install for this update after you sbf 2.3.4 and back to original. When your done with sbf file and have re-activated phone added google account etc... Get (Petes Motorola RootTools_v1.07.zip) no other rooting methods worked ive tryed it.. type that into google search it should find his site.. and make sure to download (Windows Universal drivers) for computer depending on what you have 32 bit operating system or 64 bit.. both of these files can be found on petes site. After downloading drivers and zip file..... unzip petes zip and click on (petes motorola root tools). I had one issue with this when trying to root device i had to put phone into pc mode for some reason. And if still having issues try running the adb temp rooting procedure this seems to work everytime. Run rooting method till done then u should be rooted after this is done dont mess with SU leave it as is for now.... Now you are going to want to head to the the google market on your phone and type (ota rootkeeper) and download that app. After this is done you can go to that app and and press protect root it should say something like su safe or something like that at the bottom after u have pressed it. Now when u are sure u have all these done correctly go to your phone settings and go to about phone and press on system update and download and install the OTA update 1.3.418 to your phone. It will reboot and and install update after this is done let phone load back up and do what it needs to do. Now go back to google market and install (ota rootkeeper) again and you should get only one option and that is to restore root.. press that and there you have it. Now you can update SU, remove unwanted apps, etc.. Do whatever you please. This update has caused so many droid x2 owners to get very ticked off but luckily i found the solution to all the problems. If anybody is having any issues trying to get this done leave posts and messages i will help you out as much as i can. This process went really smooth you should have no issues at all. And if ur wondering about 2.3.5/1.3.418 update it is definitely snappier with and even more snappier with bloatware apps removed. Install the droid X2 bootstrap manager just like u always would. Dont hesitate to leave questions i will try to get back to them as soon as i can. HAVE FUN ROOTING> 2.3.5 And by the way for the people wondering I run this all on stock rom I dont use eclipse, affinity , etc or any other custom rom this is all straight stock rom
Click to expand...
Click to collapse
The above instructions worked for me without factory resetting my phone and without wiping any of my data and thanks to those instructions, my phone is now rerooted with the OTA Update 1.3.418. I thank you for sharing with all of us.
1. DO NOT factory reset your phone or wipe your data.
2. Re-flash your DroidX2 with the sbf file and re-activate your phone.
3. Get Pete’s Motorola RootTools_v1.07.zip. To find it, search google to find his site. Make sure to download (Windows Universal drivers) for computer depending on what you have 32 bit operating system or 64 bit. Both of these files can be found on Pete’s site.
4. Install the Windows Universal Drivers, unzip Pete’s zip file and run Pete's Motorola Root Tools.exe. Wait for Pete’s root tool to finish.
5. Now that you are rooted again, go to the google market on your phone and search for ota rootkeeper. Download the app, run it, and press protect root.
6. Go to your phone settings and go to about phone and press on system update and download and install the OTA update 1.3.418 to your phone.
7. After the phone reboots, run the ota rootkeeper and restore root.
zergrush does not work on 2.3.5
tshelby73 said:
Heard zergrush changes something and won't let update work or something have to use Petes
Sent from my DROID X2 using XDA
Click to expand...
Click to collapse
zergrush does not work!! To all that that wondering why it dosent work it changes something in the build prop or local prop not sure but it does not work for rooting 2.3.5. And also.. For some people they may not have to do a internal factory reset, in my case i did for what reason.. i dont know. Every time i tryed installing OTA update it failed. For the people getting this error you will most likely have to reset your device and follow my instructions. PLEASE READ MY INSTRUCTIONS first before making any changes if u dont want to lose root lose saved music , apps etc.... Remember internal factory reset erases everything in internal memory. Move your things you want to save to ur sdcard
Thanks mnkurk! Saved me a lot of time - work right the first time and allowed me to fully restore my setup from titanium (with backup folder on the sd card).
Using voodoo root keeper to root 2.3.5 update has been known since the update came out.
zerg rush cant be used for a number of reasons,.some people might be able to get away with it, but a lot of times it will cause the 2.3.5 update tofail the signature check , it removes/changed files on system besides just su, to make room for root.
jagsil said:
The above instructions worked for me without factory resetting my phone and without wiping any of my data and thanks to those instructions, my phone is now rerooted with the OTA Update 1.3.418. I thank you for sharing with all of us.
1. DO NOT factory reset your phone or wipe your data.
2. Re-flash your DroidX2 with the sbf file and re-activate your phone.
3. Get Pete’s Motorola RootTools_v1.07.zip. To find it, search google to find his site. Make sure to download (Windows Universal drivers) for computer depending on what you have 32 bit operating system or 64 bit. Both of these files can be found on Pete’s site.
4. Install the Windows Universal Drivers, unzip Pete’s zip file and run Pete's Motorola Root Tools.exe. Wait for Pete’s root tool to finish.
5. Now that you are rooted again, go to the google market on your phone and search for ota rootkeeper. Download the app, run it, and press protect root.
6. Go to your phone settings and go to about phone and press on system update and download and install the OTA update 1.3.418 to your phone.
7. After the phone reboots, run the ota rootkeeper and restore root.
Click to expand...
Click to collapse
Some questions please...
After all these steps are done,
1. Will my sd card still have it's contents in memory?
2. Will all my programs will still be there?
3. I'm not sure how rooting and unrooting will affect already installed programs. Can you please expain.
Thanks for your help!
joliett said:
Some questions please...
After all these steps are done,
1. Will my sd card still have it's contents in memory?
2. Will all my programs will still be there?
3. I'm not sure how rooting and unrooting will affect already installed programs. Can you please expain.
Thanks for your help!
Click to expand...
Click to collapse
1 yes, does nothing to sd card, even if you wipe data in recovery
2 yes, if you don't bootloop and have to wipe data
3 no effect, once root is restored
The link to Droid X2 2.3.4 sbf is down
http://forum.xda-developers.com/showthread.php?t=1201534
Considering I have to flash my ROM i'd prefer a reliable source to get the file.
Edit:
Perhaps a little more browsing was in order, here a few sbf files from MoonShadow's X2 rooting thread
Moon Shadow - NM said:
a. Froyo 2.2.2 SBF File (you may have to right click and select "Save Link As")
b. Gingerbread 2.3.3 SBF File (you may have to right click and select "Save Link As")
c. Gingerbread 2.3.4 SBF File (you may have to right click and select "Save Link As")
Click to expand...
Click to collapse
Daerogami said:
The link to Droid X2 2.3.4 sbf is down
http://forum.xda-developers.com/showthread.php?t=1201534
Considering I have to flash my ROM i'd prefer a reliable source to get the file.
Click to expand...
Click to collapse
If you can get/have the 2.3.3 file, just flash that...then take the ota once and you will be on 2.3.4
should I root 2.3.3-> ota 2.3.4-> ota 2.3.5
or Flash 2.3.3-> ota 2.3.4 then Root-> ota 2.3.5
What is the benefit of going as far back as 2.3.3?
Daerogami said:
should I root 2.3.3-> ota 2.3.4-> ota 2.3.5
or Flash 2.3.3-> ota 2.3.4 then Root-> ota 2.3.5
Click to expand...
Click to collapse
Wait till 2.3.4 to root
No reason to root 233 it will just lose root when you ota any ways
Root .4
Then root keeper app
Then ota .5 and restore root with root keeper app
If going to flash a ROM after that, after you restore root, delete the su backup using the root keeper app before you flash the ROM or the rom flash will fail on ya
---------- Post added at 02:49 PM ---------- Previous post was at 02:45 PM ----------
Daerogami said:
should I root 2.3.3-> ota 2.3.4-> ota 2.3.5
or Flash 2.3.3-> ota 2.3.4 then Root-> ota 2.3.5
What is the benefit of going as far back as 2.3.3?
Click to expand...
Click to collapse
I don't know of there is any KNOWN benefit
But i know that before when i had a bunch of battery issues and other things acting weird, i went ALL THE WAY to froyo, then rode all the ota's back to 2.3.4 and things seemed better for me.
Take with a grain of salt tho, i never did any "official" testing on it., just know it fixed weird issues i had with device not sleeping properly.
i was just suggesting it cause it it's easier than having to find and then wait for 2.3.4 sbf file to download If you already had the 2.3.3 file
So, now there is a gray triangle in the top right (which apparently stands for roaming) I checked my phone status and it reads
Network: Unknown
My Phone Number: 000-000-7729
I went against your advice because I already had 2.3.4, but that shouldn't have caused this, right?
few options
reboot
wipe data or just cache in android recovery
dial *228
turn on airplane mode or turn on wifi then turn off, reboot
all SBF or here ezSBF/ RSD lite/ SBF/ drivers by 1KDS or here
Droid SBF files http://sbf.droid-developers.org/
edit: some people with issues, have reported had to wipe data before and after, and even flashing SBF twice, before getting it fixed
but the options I listed first usually fix network connection errors
not listed in any order, just as they popped in my head
As stated above
Just dial *228
Should fix that
it gives you two options i believe.
Do both if first doesn't fix it
Thanks so much! If i could thank you more than once I would!
I had to leave for work and I was so bummed out my phone wasn't getting service.
All I had to do was activate it
2.3.5 (Still wish it was ICS) and rooted!
Thanks again!
The above instructions worked for me without factory resetting my phone and
without wiping any of my data my phone is now rerooted with the OTA Update 1.3.418.
1. DO NOT factory reset your phone or wipe your data.
2. Re-flash your DroidX2 with RSDlite using the original sbf file.
RSDlite:
http://forum.xda-developers.com/attachment.php?attachmentid=784077&d=1321414457
My original flash file here:
http://www.general-files.com/downlo...Z_MB870_4.5.1A-DTN-150-30_1FF_01.sbf.zip.html
3. Re-activate your phone with *228.
4. Using Pete’s Motorola RootTools_v1.07.zip run Pete's Motorola Root Tools.exe.
Wait for Pete’s root tool to finish.
5. Now that you are rooted again, run ota rootkeeper, press protect root.
6. Go to your phone settings, About Phone and click on system update and
download and install the OTA update 1.3.418 to your phone.
7. After the phone reboots, run the ota rootkeeper and restore root.
jt
Rooted 2.3.4 to rooted 2.3.5
I'm on 2.3.4, rooted. I have downloaded but not installed 2.3.5. I previously froze, but didn't delete bloatware using Titanium.
Do you think I can just install rootkeeper, defrost bloatware, then install 2.3.5 & keep root?
I'm kind of an idiot trying to keep it simple.
Thanks in advance,
George
Success!!! This worked nicely. It just took a long time to defrost the bloatware, then freeze even more bloat when it was re-rooted as there was so much on there.
OTA Rootkeeper is a thing of beauty, it's fast & noob-proof. Thanks for that!
Hello all,
Just had a quick question. I didn't know what search terms to use to get an accurate answer, since the search seems to pick up any and everything related to any of your search terms. I was wondering what exactly prevents an OTA update from taking. Is it the recovery that is installed? Is it having root? It's been a while since I have accepted an OTA for a device, outside of the Nexus on launch day. I have my Razr Maxx rooted, no custom rom. I tried a few of the ICS leaks but they were in safestrap, my non safe partition remains only rooted. When the OTA actually hits should I be able to accept it fine or will I need to go back to completely stock unrooted?
Things that prevent an OTA: ROMS, Bloatware frozen/uninstalled, custom recoveries (safestrap, bootstrap) so yes, when you want the OTA you'll need to fastboot back to complete stock for it to work. Root won't stop an OTA but OTA's generally break root.
You can try just uninstalling safestrap but I've read cases where just uninstalling it doesn't work and you need to fastboot back to stock.
everything wrong with motorola and Android has to do with idiot upper middle management execs having endless powerpoint presentations babbling corporate gibberish so they can make the next payment on their overpriced overlarge joke of a house and BMW. we are left to sort out the steaming pile of ****. i pray google has the sense to fire every last one of them and give their salaries and bonuses to the engineers!
Freezing bloatware has never prevented me from getting and OTA. Custom ROM and bloatware removal has/will.
tech_head said:
Freezing bloatware has never prevented me from getting and OTA. Custom ROM and bloatware removal has/will.
Click to expand...
Click to collapse
What is the difference between freezing and removal, from a technical standpoint? I rooted my Razr using CASUAL and then installed Titanium Backup Pro and have been zapping the Verizon bloatware. I do want the stock ICS when it comes out. I guess I could reinstall the bloatware from backup and then freeze it rather than uninstalling. I don't care so much if the OTA doesn't install, I can troubleshoot that, but I don't want the OTA to brick my phone, that's the main concern.
The main reason I don't want the bloatware on there is that I don't want there to be any danger of clicking on anything that will make my monthly bill go up. Sometimes I let my girlfriend or other people use my Razr and if they manage to get a $10 monthly charge on my bill because they just had to see NFL Mobile or something similar, I'm gonna be pissed
I'm fairly sure it just changes the extension to .apk.bak, but I could be wrong
So, I have bloatware frozen, but none uninstalled. If ICS /is/ released on the 12th for the Verizon RAZR, I should be able to get it OTA?
Rooted, stock 2.3.6
bpingry said:
So, I have bloatware frozen, but none uninstalled. If ICS /is/ released on the 12th for the Verizon RAZR, I should be able to get it OTA?
Click to expand...
Click to collapse
Yes, at worst case scenario: You might have to unfreeze everything, Install OTA RootKeeper, use OTA RootKeeper to a> Backup your root and B> Temporarily unroot your device.
On the last OTA that I received, I was not able to install the OTA until I ran the Temp Unroot from OTA RootKeeper, then the OTA went smoothly after that.
quarky42 said:
Yes, at worst case scenario: You might have to unfreeze everything, Install OTA RootKeeper, use OTA RootKeeper to a> Backup your root and B> Temporarily unroot your device.
On the last OTA that I received, I was not able to install the OTA until I ran the Temp Unroot from OTA RootKeeper, then the OTA went smoothly after that.
Click to expand...
Click to collapse
Apps in preinstall folder are required by OTAs those are the real bloats. Any other system modification will be verified too, like build.prop, init.d CWM and so on..
Remember an OTA update is an incremental update wich will check any required system piece, especially those I've mentioned.
Cheers
OK. So I have the pull down button mod. Will this get in the way? I've not removed any bloat or yet (was waiting for updates). All I have is pull down mod and root.
MarkyG82 said:
OK. So I have the pull down button mod. Will this get in the way? I've not removed any bloat or yet (was waiting for updates). All I have is pull down mod and root.
Click to expand...
Click to collapse
Yes, it's a system modification. You'll need to flash stock rom to flash an OTA update.
When installing an OTA you can press both volume buttons at the same time to to see dialog, and if anything fails you will have filename and directory of failed checks. And it won't auto reboot until you tell it too. I found the problem files for the ics leak from early April leak and was able to install without wiping.
Sent from my DROID RAZR using xda premium
See I'm not fussed about wiping. Id quite happily have stock ICS and mod it from there. Looks like I'll be hacking some way or other to get the official anyhow as I'm on linux. Unless someone can point me to a UK suitable stock rom I can fast boot or add flash from linux. I have add setup if that helps. My system version is 167.26.
Sent from my XT910 using xda premium
cause they arent bronies, duh.
ExtraDan said:
cause they arent bronies, duh.
Click to expand...
Click to collapse
Sorry, I don't understand.
Sent from my XT910 using xda premium
and you wont...
MarkyG82 said:
Sorry, I don't understand.
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
I don't understand them either, just don't make a big deal about it
Thanks for all the replies. I don't have any bloatware frozen and no system mods done so I guess once the OTA hits, as long as safestrap uninstalled smoothly, I should be good to go. Ill check out ota root keeper here shortly.
Sent from my DROID RAZR using xda premium
I rooted my phone to prevent KitKat from installing, because I didn't want to lose access to FoxFi. I forze the SDM file so it wouldnt look for updates. Today FoxFi has fixed the problem, so I no longer fell the need to be rooted, and I would very much like a taste of that KitKat. If I understand correctly I should not unfreeze the the SDM file and take the OTA update, because it could "brick my phone". Is that the case?
Do I need to unroot first, and is there a thread without a hundred pages that explains how to unroot. I am on Build VRUEMK2.
Thoughts?
Under the settings in the Superuser app is an option to "Full Unroot" Will this really work for unrooting the device, or do i need to do the odin thing i keep reading about? Why would odin even be necessary if this is an option. It seems to easy.
You will need to return your phone to stock, root will prevent the OTA. You can try to unfreeze SDM and take the update, it won't brick your phone, it will just fail to install because root will cause it to fail.
There are threads about using Odin and no-wipe MK2 or MJ7 files to return your phone to stock without losing data. That is the best way to roll your phone back to take the update. Alternatively, you could just do a factory reset from the stock recovery, but you'll lose all your data on the phone. Otherwise, you can just update using the Odin tars that are available now, but since it seems like you don't want to do the research on how to do that, you'd probably better not try.
Paramemetic said:
There are threads about using Odin and no-wipe MK2 or MJ7 files to return your phone to stock without losing data. That is the best way to roll your phone back to take the update. Alternatively, you could just do a factory reset from the stock recovery, but you'll lose all your data on the phone. Otherwise, you can just update using the Odin tars that are available now, but since it seems like you don't want to do the research on how to do that, you'd probably better not try.
Click to expand...
Click to collapse
Thanks,
So you do not recommend or know about the "Full Unroot" option in the Superuser settings.
I do not mid a factory reset, as this is phone is only a month old. If it is that easy, I will probably go that route.
I am currently downloading a file called VRUAMDK_NoWipe.tar.zip which I understand to be a stock image of my android before i rooted that is supposed to take me back to pre-root. But if factory resetting will accomplish the same goal, then that seems like an easier way to go.
I do like the openness of being rooted, but My concern about updating with the root, is that some functions may not work like they are supposed to. I haven't been involved in rooting since the days of playing with my HTC Eris, and Droid X. Maybe things a re different today, but most roms I played with were found to have issues with thinks not functioning correctly. Do the 4.4 "tars" that you are referring to have all the functions?
I'd sit tight and see what comes from the latest tar files of NC5. Maybe nothing, but can't hurt to wait.
Sent from my SCH-I545 using XDA Free mobile app
Rageboardr said:
Thanks,
So you do not recommend or know about the "Full Unroot" option in the Superuser settings.
I do not mid a factory reset, as this is phone is only a month old. If it is that easy, I will probably go that route.
I am currently downloading a file called VRUAMDK_NoWipe.tar.zip which I understand to be a stock image of my android before i rooted that is supposed to take me back to pre-root. But if factory resetting will accomplish the same goal, then that seems like an easier way to go.
I do like the openness of being rooted, but My concern about updating with the root, is that some functions may not work like they are supposed to. I haven't been involved in rooting since the days of playing with my HTC Eris, and Droid X. Maybe things a re different today, but most roms I played with were found to have issues with thinks not functioning correctly. Do the 4.4 "tars" that you are referring to have all the functions?
Click to expand...
Click to collapse
The no wipe image you are downloading is probably not the correct version for your phone unless you are still on the MDK firmware.
Sent from my SCH-I545 using Tapatalk
jmgib said:
The no wipe image you are downloading is probably not the correct version for your phone unless you are still on the MDK firmware.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Bummer, I was wondering about that after i started looking at different image names. I started seeing the common theme, and no I am not on MDK, I am on MK2. Bummer because that file took along time to download here at work.
kude87 said:
I'd sit tight and see what comes from the latest tar files of NC5. Maybe nothing, but can't hurt to wait.
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
What is the difference between a tar file, and ROMing. Are TAR files more reliable?
I am in no real hurry, but as this is my daily phone, I need everything to work correctly, and no reason to wait if its like ROMs, and there seem to always be things that are quirky in a ROM.
Rageboardr said:
What is the difference between a tar file, and ROMing. Are TAR files more reliable?
I am in no real hurry, but as this is my daily phone, I need everything to work correctly, and no reason to wait if its like ROMs, and there seem to always be things that are quirky in a ROM.
Click to expand...
Click to collapse
If it is your daily and you aren't in any hurry, I strongly suggest waiting it out. Read some forums and get a better feel about rooting and romming.
A tar file is flashed through Odin, and depending which one you download, could lock your bootloader (I forget which firmware you're on). I'd personally wait for/if NC5 is rooted and proceed then.
"Romming" is a broad term used to define flashing custom roms. Predominantly, this means you have an unlocked bootloader and are flashing zip files through a custom recovery.
Sent from my SCH-I545 using XDA Free mobile app
Rageboardr said:
I rooted my phone to prevent KitKat from installing, because I didn't want to lose access to FoxFi. I forze the SDM file so it wouldnt look for updates. Today FoxFi has fixed the problem, so I no longer fell the need to be rooted, and I would very much like a taste of that KitKat. If I understand correctly I should not unfreeze the the SDM file and take the OTA update, because it could "brick my phone". Is that the case?
Do I need to unroot first, and is there a thread without a hundred pages that explains how to unroot. I am on Build VRUEMK2.
Thoughts?
Click to expand...
Click to collapse
Hi I had the same issue. mk2, rooted, wanted to take the ota update and didn't mind losing root.
You won't brick trying to take the update it will just fail with error 402. I wrote out my steps below to guide you thru the process I used and were successful for me.
1. Unroot using SuperSU.
2. Use Kies to update/restore firmware on your PC.
3. Once rebooted search for system update.
4. Download and install the update. I did the whole process using only data no WiFi (not sure if it makes a difference but that's what I did).
5. Once your phone reboots you will be greeted by a lovely red Verizon splash screen.
Hope this helps you and others!
Sent from my Hp Touchpad Android 4.4.2 using Tapatalk Pro