Database Develop

[Q] Simple root for Nexus One

Noob here. I've searched the forums and have tried to piece together what I need to know for what I would like to do. I think I have a general understanding, but was hoping someone could verify or clarify.
I've got a Nexus 1 running 2.3.3. Never been rooted. All OTA updates.
What I would like is to root it so that I can delete crap like Facebook and Amazon and make room on the built-in memory. I don't want to unlock the boot-loader, and I don't want to flash custom ROMs. I do want control of what is stored where, the ability to move things to SD (even if they aren't marked for that (and yes, aware that that can cause problems sometimes)), and the ability to run Titanium backup.
As I understand it, all of that can be done with just root permission. But it seems that simple root for the N1 under 2.3.3 isn't available. Can anyone comment?
Thanks,
DT

Depends what you call simple...
Since you don't want to unlock the bootloader, you can try using the passimg method to revert to an earlier build of android, and then use any "simple root" available.
Unfortunately, a small percentage of users don't seem to be able to use the passimg method, and if you get an "main version is older" error, then it means you are among them...
Passimg method can be found in the wiki, under the unroot/restore guide (passimg method, using FRG33):
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Sent from my Nexus One using XDA Premium App

Good luck rooting, without trying to unlock the bootloader. It's simply not available atm I belive. Any particular reason you don't want to unlock the bootloader, beside the warranty?

root without unlocking bootloader
I'm still coming up to speed on this, so it's quite possible that I don't understand all the subtleties.
What I want to do is uninstall space-wasting preinstalled junk, and to run Titanium backup. I'm not interested (for now) in custom ROMs. I think I want to avoid unlocking the bootloader both for the warranty (a minor issue), convenience (another minor issue that could be overcome...), and because I want to retain as much of a "stock" device as possible, mostly to allow for future OTA updates. From what I've read, it sounds like a root would accomplish all that. Hence I'd rather avoid all the additional complications if a simple root were in fact available.
Thanks for the help,
DT

Unlocking the bootloader does not affect you device's ability to receive/install OTA updates, but removing "space-wasting preinstalled junk" will certainly prevent you from installing the OTA...
Sent from my Nexus One using XDA Premium App

efrant said:
Unlocking the bootloader does not affect you device's ability to receive/install OTA updates, but removing "space-wasting preinstalled junk" will certainly prevent you from installing the OTA...
Click to expand...
Click to collapse
Totally agree. If you check the threads that were active during the OTA onslaught, many people could not install stock Gingerbread due to removing stock system apps (Facebook, Amazon, Twitter, etc...)

...but, if you have a custom recovery, you can still install the updates in a modified form.
Sent from my Nexus One using XDA Premium App

danger-rat said:
...but, if you have a custom recovery, you can still install the updates in a modified form.
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
Really? I was unaware of that. Would you mind posting a link to an OTA (say, Gingerbread for example) that I would be able to install on a stock Froyo ROM, which I had removed say, Amazon and Facebook?
Thanks.

Thanks for the info. I hadn't thought about the OTA being affected by removal of unwanted programs.
DT

I would just passimg back to stock 2.2 and then root it with z4root
Sent from my GT-I9000 using XDA Premium App

efrant said:
Really? I was unaware of that. Would you mind posting a link to an OTA (say, Gingerbread for example) that I would be able to install on a stock Froyo ROM, which I had removed say, Amazon and Facebook?
Thanks.
Click to expand...
Click to collapse
I said modified - meaning rooted, or even just having the verifications taken out of the update script...
Sent from my Nexus One using XDA Premium App

danger-rat said:
I said modified - meaning rooted, or even just having the verifications taken out of the update script...
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
I was just asking if anyone has done this (or does this), as I would certainly love to remove apps, as long as I can install future updates as they become available. (Doing that is beyond my knowledge...) I like my stock ROM, and I would certainly remove certain apps if I know someone would provide a "modified" update.zip for a stock ROM that doesn't check if Amazon, etc are installed.
What I don't want is to flash a new ROM every time an update came out...

It is very simple. If you remove stuff from the stock rom the ota will fail.
You will then need flash the same way as you would for any of the custom roms for updates.
Or you could manually put the stuff you removed back but that is probably more work then you want to do.
Sent from my Nexus One using XDA App

Easiest approach would probably be to take a backup of the stock image before you remove any apps, and restore it when you hear that an update is available...
Sent from my Nexus One using XDA Premium App

danger-rat said:
Easiest approach would probably be to take a backup of the stock image before you remove any apps, and restore it when you hear that an update is available...
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
Restoring a NAND backup is essentially the same thing as flashing a new ROM, which is what I don't want to be doing. What would be good is to be able to install a modified/repacked/whatever-you-want-to-call-it OTA update file that has the check (which checks to see if apps are installed) disabled.
If it is just a line in a script that needs to be removed in an OTA, so that it will flash (with a custom recovery of course) with Amazon removed, it is surely doable, no? If it is doable, I am surprised that no one has done it for any of the updates... (at least I haven't seen any).

albundy2010 said:
It is very simple. If you remove stuff from the stock rom the ota will fail.
You will then need flash the same way as you would for any of the custom roms for updates.
Or you could manually put the stuff you removed back but that is probably more work then you want to do.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Thanks, but my question was: is it possible to modify an OTA zip file in such a way that it disables checking for installed apps like Amazon?
This would be helpful, and I had never thought of it until danger-rat mentioned it, but I may have misunderstood his post - he was probably talking about just flashing a new ROM, but that is not what I am interested in.

Yes, it's possible.
The update script is pretty big though, so you'd have your work cut out making sure you covered everything...
The other option would be to build an restore zip, that just reinstalled the apps you remove. Just add the apps to a zip as you restore them...
Sent from my Nexus One using XDA Premium App

danger-rat said:
Yes, it's possible.
The update script is pretty big though, so you'd have your work cut out making sure you covered everything...
The other option would be to build an restore zip, that just reinstalled the apps you remove. Just add the apps to a zip as you restore them...
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
That sounds like a good idea.
This is what I'd like to do as a test:
1) Restore a stock Froyo ROM
2) Remove the Amazon.apk (and possibly others) from my ROM and save it somewhere (and whatever other files would be needed).
3) Create an update.zip file that would place the Amazon.apk file back to the correct directory in a stock ROM (i.e., odexed).
4) Flash that update.zip
5) Flash the Gingerbread OTA and see if it works.
Would you be able to point me to a guide on how to create a flashable zip? Again, I would need to be able to do this for an odexed ROM.
Thanks.
EDIT: Nevermind. I found it here: http://www.londatiga.net/it/how-to-create-android-update-zip-package/

ameedi600 said:
I would just passimg back to stock 2.2 and then root it with z4root
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
I agree this is what I did had no problems at all

Root Xperia Z and still get OTA?

Hi. New to Xperia phone, coming from S3. So far loving it! just wondering if I can root and still have the option to get OTA from Sony? Don't want to loose bravia engine 2 (yet) so only need root to remove som bloatwares and install some apps. Also, if that is possible to get OTA with root, will updating the phone remove root?
Thanks!
Sent from my C6603 using xda app-developers app

UnLucky12 said:
Hi. New to Xperia phone, coming from S3. So far loving it! just wondering if I can root and still have the option to get OTA from Sony? Don't want to loose bravia engine 2 (yet) so only need root to remove som bloatwares and install some apps. Also, if that is possible to get OTA with root, will updating the phone remove root?
Thanks!
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
Use pro features of SuperSU or OTA Rootkeeper to protect your root, then when you OTA update you should be fine. Try not to modify anything in the System partition otherwise OTA will probably fail (is my understanding), or if you do (i.e. renaming various apks/odex files to .bak), make sure you put them back before OTA updating, in case they need to be patched.

Thanks for the reply! I was only thinking of installing adaway, also the whitecontroll mod to the Xperia. How do I then remove them like the whitecontroll app witch is intergrated in to the system?
If it removes root, I can always reroot the device
Sent from my C6603 using xda app-developers app

UnLucky12 said:
Thanks for the reply! I was only thinking of installing adaway, also the whitecontroll mod to the Xperia. How do I then remove them like the whitecontroll app witch is intergrated in to the system?
If it removes root, I can always reroot the device
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure about the WB control, I imagine that would likely prevent OTA due to libs inserted in to /system, perhaps if you were to perform the installation manually, take note of all files inserted, and backup any (if any) files it overwrites you could restore it before OTA.
As for AdAway, it only changes your host file, which shouldn't affect OTA, since I doubt Sony will make any changes to it OTA, but AdAway can be "undone" from within the app, so you can do that easily anyway.
It's hard to say really and depends on the OTA, but generally, from my experience, if the OTA contains a patch for a particular file, it will MD5 it, and if that fails, OTA will fail, if you have modified files that aren't patched as part of the OTA you shouldn't have a problem.
That said, I have little experience with Sony OTA files, and without looking at the script for any particular OTA you can never tell what they might check or change.
The only recommendation I can give really, is that if you want to OTA, change as LITTLE as possible in the /system partition, and make sure to revert any changes before attempting to apply an OTA.
If that is too much effort, and all you're really concerned about is you data, use Titanium Backup to keep everything safe, modify anything you want in system, then flash a stock ROM before you OTA update. You could also just flash a stock system partition, perhaps from a nandroid? before you OTA, and that should also solve the problem.

As you don't unlock your bootloader you're safe.
But OTA doesn't always works even in locked bootloader, tried yesterday to OTA update my locked bootloader Xperia T to .140 fw but it failed because of root, even after unroot with superSU option it failed.
Backup everything, update with SUS or PCC and reroot with binary tool using goroh_kun exploit included in the tool..

alias_neo said:
I'm not sure about the WB control, I imagine that would likely prevent OTA due to libs inserted in to /system, perhaps if you were to perform the installation manually, take note of all files inserted, and backup any (if any) files it overwrites you could restore it before OTA.
As for AdAway, it only changes your host file, which shouldn't affect OTA, since I doubt Sony will make any changes to it OTA, but AdAway can be "undone" from within the app, so you can do that easily anyway.
It's hard to say really and depends on the OTA, but generally, from my experience, if the OTA contains a patch for a particular file, it will MD5 it, and if that fails, OTA will fail, if you have modified files that aren't patched as part of the OTA you shouldn't have a problem.
That said, I have little experience with Sony OTA files, and without looking at the script for any particular OTA you can never tell what they might check or change.
The only recommendation I can give really, is that if you want to OTA, change as LITTLE as possible in the /system partition, and make sure to revert any changes before attempting to apply an OTA.
If that is too much effort, and all you're really concerned about is you data, use Titanium Backup to keep everything safe, modify anything you want in system, then flash a stock ROM before you OTA update. You could also just flash a stock system partition, perhaps from a nandroid? before you OTA, and that should also solve the problem.
Click to expand...
Click to collapse
So I can make a nandroid backup with only root? Using Rom Manager app. Or do I need to unlock the bootlocker? If I can, then I can just recover from nandroid that are stock, update then backup again, change systemlibs etc?
Sent from my C6603 using xda app-developers app

babylonbwoy said:
As you don't unlock your bootloader you're safe.
But OTA doesn't always works even in locked bootloader, tried yesterday to OTA update my locked bootloader Xperia T to .140 fw but it failed because of root, even after unroot with superSU option it failed.
Backup everything, update with SUS or PCC and reroot with binary tool using goroh_kun exploit included in the tool..
Click to expand...
Click to collapse
I see! Hmmm. But SUS?
Sent from my C6603 using xda app-developers app

UnLucky12 said:
I see! Hmmm. But SUS?
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
I believe SUS is Sony Update Service.
Technically, you should be able to nandroid with recovery for locked bootloader then restore system before OTA, but if Sony OTA checks somehow prevent it because of an md5 on the entire partition or some such, you will have to re flash a totally stock System, perhaps a custom FTF(?), update then root again.
Next time we get an OTA I'll test the process myself, but until then I can only speculate. Hopefully someone else has more concrete information.
Sent from my C6603 using Tapatalk 2

alias_neo said:
I believe SUS is Sony Update Service.
Technically, you should be able to nandroid with recovery for locked bootloader then restore system before OTA, but if Sony OTA checks somehow prevent it because of an md5 on the entire partition or some such, you will have to re flash a totally stock System, perhaps a custom FTF(?), update then root again.
Next time we get an OTA I'll test the process myself, but until then I can only speculate. Hopefully someone else has more concrete information.
Sent from my C6603 using Tapatalk 2
Click to expand...
Click to collapse
Thanks man! But Stock rom for the XZ. How or where can I download it? Supposed to use SUS or PCC? What is best?
Sorry for being such a noob. Don't want to totally destroy my phone hehe.
Sent from my C6603 using xda app-developers app

UnLucky12 said:
Thanks man! But Stock rom for the XZ. How or where can I download it? Supposed to use SUS or PCC? What is best?
Sorry for being such a noob. Don't want to totally destroy my phone hehe.
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
No problem, I, and I imagine others prefer to answer questions from cautious users than those all gung-ho, brick their devices then come crying for help. Ask first, flash later
As for which tool, I hope someone else can comment, I've always been a Samsung man until now so I've never used either tool yet.
As for stock firmwares, there are loads in the Dev section. Just pick the right one and flash it however they recommend.
Sent from my C6603 using Tapatalk 2

alias_neo said:
No problem, I, and I imagine others prefer to answer questions from cautious users than those all gung-ho, brick their devices then come crying for help. Ask first, flash later
As for which tool, I hope someone else can comment, I've always been a Samsung man until now so I've never used either tool yet.
As for stock firmwares, there are loads in the Dev section. Just pick the right one and flash it however they recommend.
Sent from my C6603 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, and thanks for the help Hope your answers will also help other that also wonders about the same thing
Arent there a program or website to download the official firmwares? Or using SUS automatically update it to stock?
Sent from my C6603 using xda app-developers app

UnLucky12 said:
Yeah, and thanks for the help Hope your answers will also help other that also wonders about the same thing
Arent there a program or website to download the official firmwares? Or using SUS automatically update it to stock?
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
I believe so. Buy don't quote me on that, like I said, never used it.
Sent from my C6603 using Tapatalk 2

It's the same if you use Sony Update Service or PC Compagnon, PCC contain other tool, while SUS only update. Also you can use Flashtool by Androxyde (here on XDA) to flash firmware converted in ftf format. Sony also relased it's own tool named flashtool to flash unlocked bootloader mobile because you can't use SUS/PCC when it's unlocked.
Read this thread "All the info you need before you begin" http://forum.xda-developers.com/showthread.php?t=2153167

[Q] Any way for us on Verizon DE with TWRP to install the update?

Not sure if I missed it, but didn't see anything via searching. Is there any way yet for us on the Verizon DE with a custom recovery to install/flash the current update? Without restoring the phone to stock and/or flashing back to a stock recovery.
I assume we are just waiting for the correct files to be extracted from the update, so that we can flash them, but thought maybe I missed something along the way.

Jexx11 said:
Not sure if I missed it, but didn't see anything via searching. Is there any way yet for us on the Verizon DE with a custom recovery to install/flash the current update? Without restoring the phone to stock and/or flashing back to a stock recovery.
I assume we are just waiting for the correct files to be extracted from the update, so that we can flash them, but thought maybe I missed something along the way.
Click to expand...
Click to collapse
I would like to know about this too

Flash stock recovery via fastboot > reboot > download and flash OTA via stock recovery > reboot > flash twrp with fastboot > reboot/root > enjoy. If you have made any mods to your system you will probably want to rsd or fastboot completely back to stock.

mentose457 said:
Flash stock recovery via fastboot > reboot > download and flash OTA via stock recovery > reboot > flash twrp with fastboot > reboot/root > enjoy. If you have made any mods to your system you will probably want to rsd or fastboot completely back to stock.
Click to expand...
Click to collapse
I knew this method would work, was just hoping to avoid rsd'ing back to stock. I've got everything backed up, but its still annoying setting everything back up.

Did you read what I wrote? Unless you made changes to the system all you would need to do is flash the stock recovery. Your data will be intact.
Sent from my Moto X.

mentose457 said:
Did you read what I wrote? Unless you made changes to the system all you would need to do is flash the stock recovery. Your data will be intact.
Sent from my Moto X.
Click to expand...
Click to collapse
I've made several changes, uninstalled several verizon bloatware apps, as well as moving others from system to user so I could greenify.

Jexx11 said:
I've made several changes, uninstalled several verizon bloatware apps, as well as moving others from system to user so I could greenify.
Click to expand...
Click to collapse
Then in addition to flashing stock recovery, flash the stock system.
Sent from my Moto X.

mentose457 said:
Then in addition to flashing stock recovery, flash the stock system.
Sent from my Moto X.
Click to expand...
Click to collapse
Won't flashing stock system wipe data?
Sent from my XT1060 using xda app-developers app

Jexx11 said:
Won't flashing stock system wipe data?
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
No. If you flash the data partition it will.
Sent from my Moto X.

mentose457 said:
No. If you flash the data partition it will.
Sent from my Moto X.
Click to expand...
Click to collapse
Thanks for the help, for some reason I was under the impression flashing system wiped your data as well. In the process of flashing now, everything is going smoothly after I updated my fastboot.exe since the default one I had said my system.img file was too large.

Be careful, flashing system and then updating will wipe root away, if not done properly

alex94kumar said:
Be careful, flashing system and then updating will wipe root away, if not done properly
Click to expand...
Click to collapse
/Reads thread title. /No ****s given.

This won't help you but in case you didn't know you could, I'm running the updated tmobile rom on my dev edition vzw Moto x. You get native tethering that way too. You just have to flash the vzw build.prop on top, the original one works fine. Then you need an app like 4g lte switch to enter phone settings and change to lte/cdma auto(prl) to receive and make calls and txts. Pretty cool I think. This way I've had the update for almost a month now and didn't have to wait for Verizon

jimmypop13 said:
This won't help you but in case you didn't know you could, I'm running the updated tmobile rom on my dev edition vzw Moto x. You get native tethering that way too. You just have to flash the vzw build.prop on top, the original one works fine. Then you need an app like 4g lte switch to enter phone settings and change to lte/cdma auto(prl) to receive and make calls and txts. Pretty cool I think. This way I've had the update for almost a month now and didn't have to wait for Verizon
Click to expand...
Click to collapse
I suppose that would work if you didn't want to wait on Verizon for updates. FYI native tether is also easy to achieve on Verizon without the T-Mobile hack.
Hopefully Verizon is fairly quick when updates are released, this round wasn't bad at all so I didn't mind the wait too much.
Sent from my XT1060 using xda app-developers app

What are my options?

I have a VZW 16GB Moto X currently rooted and safestrap installed, I keep defering the update since I don't want to lose root and am pretty sure it will fail since stock recovery is gone.
What are my options to either get the OTA with root or disabling the update notification?
I am not 100% sure i want to dive into an SS ROM nor is there really anything out there.
Just trying to figure out what I should do / what everyone else is doing.

DiGi91 said:
I have a VZW 16GB Moto X currently rooted and safestrap installed, I keep defering the update since I don't want to lose root and am pretty sure it will fail since stock recovery is gone.
What are my options to either get the OTA with root or disabling the update notification?
I am not 100% sure i want to dive into an SS ROM nor is there really anything out there.
Just trying to figure out what I should do / what everyone else is doing.
Click to expand...
Click to collapse
I would get the OTA with root. The camera and phone call difference really do show in my opinion.
To keep your root I would rsd back to stock. Download pwnmymoto and install it BUT don't run it. Just have it installed. Then update. After the update you can run pwnmymoto and you'll have root with the OTA. Jcase said this is the correct way to do it.
Sent from my XT1060 using XDA Premium 4 mobile app

ruben8448 said:
I would get the OTA with root. The camera and phone call difference really do show in my opinion.
To keep your root I would rsd back to stock. Download pwnmymoto and install it BUT don't run it. Just have it installed. Then update. After the update you can run pwnmymoto and you'll have root with the OTA. Jcase said this is the correct way to do it.
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I will consider doing that, it's just a giant PITA since I will have start from scratch.. Coming from the S III and flashing a new ROM every day this is so different to me lol. There is nothing wrong with the stock ROM just regretting not waiting for the dev edition to be honest.. I still use my S III as a media player and lately have been thinking of switching back, just hoping we get 4.4 soon or something to make it a bit better.
I know safe strap is another option but haven't heard great things about it and back in the droid 3 days remembered using it.

Just backup your apps and restore after you're rooted again. No starting from scratch necessary. I used titanium backup and didn't have any issues.
Sent from my XT1060 using xda app-developers app

pyro6128 said:
Just backup your apps and restore after you're rooted again. No starting from scratch necessary. I used titanium backup and didn't have any issues.
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Can you use the new FXZ to return to OTA'd stock if necessary down the road?

pyro6128 said:
Just backup your apps and restore after you're rooted again. No starting from scratch necessary. I used titanium backup and didn't have any issues.
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
Yeah I might do that, I just don't have the time right now. I heard the OTA is a big improvement though. I wish I could be rooted with write access and no need for workarounds lol wishful thinking..
EDIT: Besides using safestrap

anotherfiz said:
Can you use the new FXZ to return to OTA'd stock if necessary down the road?
Click to expand...
Click to collapse
Yup, stock OTA, but you can't go back to a previous version

DiGi91 said:
Yeah I might do that, I just don't have the time right now. I heard the OTA is a big improvement though. I wish I could be rooted with write access and no need for workarounds lol wishful thinking..
EDIT: Besides using safestrap
Click to expand...
Click to collapse
fyi. if you are on vzw then SS is an easy fix for you. The "not great things" you heard were just posts from when SS was having some problems. I have SS up and running with the new rom for vzw in a rom slot and flashed the new radios and everything is working perfectly. No problems for me at all. Also, tibu is really easy to use and will restore system data, your launcher and anything you want. Very minor things that you will need to screw with after using it. Takes about an hour and a half if you need to do things to your system after you start using the new rom. If you don't need to make any of those edits then it really only takes about 30 mins from installing SS to having the new rom running with all your settings and apps.

jayboyyyy said:
fyi. if you are on vzw then SS is an easy fix for you. The "not great things" you heard were just posts from when SS was having some problems. I have SS up and running with the new rom for vzw in a rom slot and flashed the new radios and everything is working perfectly. No problems for me at all. Also, tibu is really easy to use and will restore system data, your launcher and anything you want. Very minor things that you will need to screw with after using it. Takes about an hour and a half if you need to do things to your system after you start using the new rom. If you don't need to make any of those edits then it really only takes about 30 mins from installing SS to having the new rom running with all your settings and apps.
Click to expand...
Click to collapse
What about the limited space that is available when using SS?
Also idk If I want to RSD back to get the OTA seeing as "eventually" we will get 4.4 not sure what to do right now lol
I was thinking of trying out the SS OTA ROM but I really don't know also how did you flash the radios.. RSD?

http://www.droidrzr.com/index.php/t...-x-ss-rom-139151-update-10-31-13/#entry370601
Ota stock ROM never take ota's

DiGi91 said:
What about the limited space that is available when using SS?
Also idk If I want to RSD back to get the OTA seeing as "eventually" we will get 4.4 not sure what to do right now lol
I was thinking of trying out the SS OTA ROM but I really don't know also how did you flash the radios.. RSD?
Click to expand...
Click to collapse
if you are worried about space then just flash it to the stock rom. I have plenty of space. with 500 photos on it. I don't use music though. You don't have to rsd to get the ota. You can just flash the recovery.img if you didn't touch the system or flash the system.img as well if you need to using fastboot. Take some time to learn what fastboot and adb are and how to use them and you will be happy you did. Doesn't take much time at all. They are kind of the same thing, how they work at least.
Use fastboot when in fastboot mode. Use adb when the phone is just on normally. Then run appropriate commands. "adb reboot" "fastboot reboot"
here is a link on how to use adb and if you go through it and understand everything then you will also understand fastboot and fastboot will already be installed as well). Then you can take the ota without losing data and having to use RSD.
http://forum.xda-developers.com/showthread.php?t=872128
As for the new radios, you will need to use fastboot. you flash the non-hlos.bin then erase modemst1 and modemst2 then flash the fsg.mbn. if you want help with it just send me a pm

shane1 said:
http://www.droidrzr.com/index.php/t...-x-ss-rom-139151-update-10-31-13/#entry370601
Ota stock ROM never take ota's
Click to expand...
Click to collapse
Looks like WiFi isn't working on that ROM!?
Also could I restore my stock ROM to a ROM Slot on SS and then flash the OTA ROM over it?
This would not require TiBu or anything like that..
Just trying to figure the best and easiest way to do this.

Not sure bit if your on a slot it shouldn't hurt to try. I'd make a backup and put it on PC or the cloud to be safe.

shane1 said:
Not sure bit if your on a slot it shouldn't hurt to try. I'd make a backup and put it on PC or the cloud to be safe.
Click to expand...
Click to collapse
So boot into SS, backup my stock ROM - save on my pc, then make a ROM slot in SS and restore the backup to the slot? Can you even do that lol
Then if all is well flash the SS OTA ROM on top and I SHOULD be okay..
Might give it a shot likely need to update SS idk what the latest version is

DiGi91 said:
Looks like WiFi isn't working on that ROM!?
Also could I restore my stock ROM to a ROM Slot on SS and then flash the OTA ROM over it?
This would not require TiBu or anything like that..
Just trying to figure the best and easiest way to do this.
Click to expand...
Click to collapse
I just flashed it over my stock backup and it worked but doesn't fix wifi

shane1 said:
I just flashed it over my stock backup and it worked but doesn't fix wifi
Click to expand...
Click to collapse
That is a big issue, I need WiFi working...

I finally got around to messing with SS and the OTA ROM and did a backup of my stock slot and flashed the ROM to it. everything was working but no WiFi and I can't deal with that =/
Ended up restoring my stock slot backup.
I did however manage to update the baseband, super easy!
EDIT: Flashed the ROM on XDA and now I have working WiFi, looks like the one on droidrzr didn't work for me.

[Q] force update.??

first thing is that im rooted and tried to update the small "pre kitkat" update and all goes good til it gets to 25% then it says update fails and ive searched til i cant go anymore about ways to fix it so my question is that can att force update my phone to kitkat or should i wait til ss is updated for kitkat and if thats the case will i be able to flash in rom slot one and leave the stock slot alone ? im new to all this flashing roms and i dont have a computer so im trying to do everything from my phone any and all suggestions will help.

In on the same boat but I'm not rooted. It goes to 25 and then gets interrupted.
Sent from my SAMSUNG-SM-N900A using xda app-developers app

shane1981 said:
first thing is that im rooted and tried to update the small "pre kitkat" update and all goes good til it gets to 25% then it says update fails and ive searched til i cant go anymore about ways to fix it so my question is that can att force update my phone to kitkat or should i wait til ss is updated for kitkat and if thats the case will i be able to flash in rom slot one and leave the stock slot alone ? im new to all this flashing roms and i dont have a computer so im trying to do everything from my phone any and all suggestions will help.
Click to expand...
Click to collapse
Borrow a friend's pc or go to a library and use Samsung Kies, but you will lose root.

This is most likely because you deleted some the system apps that came with the stock rom..... This is why I never delete them only freeze with titanium backup! This happen to me on Ml9 so I had to restore stock rom reroot put super su in survival mode and then take the update!
Sent from my Note 3 SM-N900A rooted by Designgears

how would i go about doing that?
Sent from my SM-N9005 using xda app-developers app

shane1981 said:
how would i go about doing that?
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Kies is just going to tell you that your firmware is up to date. Either factory reset or you may have to use this http://forum.xda-developers.com/showthread.php?t=2559715 < This is how I had to do it.

So if I am rooted and deleted the AT&T bloat apps, I can't install the KitKit update? What I unroot completely? I know that won't bring back the garbage AT&T apps back, but would I be able to OTA to kitkat then?

MattMJB0188 said:
So if I am rooted and deleted the AT&T bloat apps, I can't install the KitKit update? What I unroot completely? I know that won't bring back the garbage AT&T apps back, but would I be able to OTA to kitkat then?
Click to expand...
Click to collapse
You will not be able to ota unless you do a full restore. You also must have att sim card. At&t is just dirty like that.

B_I_N_G_E said:
You will not be able to ota unless you do a full restore. You also must have att sim card. At&t is just dirty like that.
Click to expand...
Click to collapse
Wow. Anyway, I was rooted, but had Wanam installed and successfully updated to Nb4. I had the fake system status set to official. I was alwasy under the impression if it said Official you could update.
And great, because now we all have to follow a really complicated guide to restore back to MJ5 if we want kitkat.

I was rooted on mj5 no wanam or anything and my phone update to nb4
It didn't even ask.
What you probably did was delete the att update software so now it's not even looking.
Sent from my XT907 using xda app-developers app

I don't think being rooted affects your updating. I have read many people accidentally updating and loosing their root. If you couldn't update with root, people wouldn't freeze at&t update.

ive tried unrooting factory reset andthe only thing i can think of is that ive deleted something . i guess the lesson learned is juat freeze apps instead of deleting them
Sent from my SM-N9005 using xda app-developers app