Related
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
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.
Hi everyone. Not sure anyone will be able to help me, but I figured I'd chance it. I also hope that I'm asking this in the right area. If not I apologize. So I got a Note 3 (AT&T) today. IN LOVE! After doing some reading I used Kingo to root. Everything went great and my phone is now rooted. To confirm this I downloaded root checker from the play store and it confirmed that my phone is definitely rooted.
After some more research I came across safestrap. For the last 2-3 hours I have been trying to install it with zero luck. Basically, after I download the 3.71 apk, installed the apk, followed the prompts and completed the installation safestrap says that the installation was complete. Unfortunately, the state: still shows not installed and I am unable to choose reboot to recovery. It's greyed out and can't be selected. Any chance that anyone knows why this is happening? I have tried just about everything that I can think of and the result has been the same every time. Sorry so long, but this is driving me crazy and I wanted to be thorough with my explanation. Thanks in advance for any help or fixes that you come up with.
thynis said:
Hi everyone. Not sure anyone will be able to help me, but I figured I'd chance it. I also hope that I'm asking this in the right area. If not I apologize. So I got a Note 3 (AT&T) today. IN LOVE! After doing some reading I used Kingo to root. Everything went great and my phone is now rooted. To confirm this I downloaded root checker from the play store and it confirmed that my phone is definitely rooted.
After some more research I came across safestrap. For the last 2-3 hours I have been trying to install it with zero luck. Basically, after I download the 3.71 apk, installed the apk, followed the prompts and completed the installation safestrap says that the installation was complete. Unfortunately, the state: still shows not installed and I am unable to choose reboot to recovery. It's greyed out and can't be selected. Any chance that anyone knows why this is happening? I have tried just about everything that I can think of and the result has been the same every time. Sorry so long, but this is driving me crazy and I wanted to be thorough with my explanation. Thanks in advance for any help or fixes that you come up with.
Click to expand...
Click to collapse
click on safestrap in your app drawer then click install recovery
Vsideo of the issue.
jerrycoffman45 said:
click on safestrap in your app drawer then click install recovery
Click to expand...
Click to collapse
I made a screen recording of what's going on. Not sure sure why I didn't I didn't do this earlier.
youtu.be/FkuiYcFFk2E
thynis said:
I made a screen recording of what's going on. Not sure sure why I didn't I didn't do this earlier.
youtu.be/FkuiYcFFk2E
Click to expand...
Click to collapse
try disabling lookout first
Same result.
Uninstalled Safestrap, Disabled and turned off lookout, and rebooted. After reboot I reinstalled safestrap and tried again. The result was the same. No install and not reboot to recovery after a supposed successful install. Would re-rooting possibly make a difference?
thynis said:
Uninstalled Safestrap, Disabled and turned off lookout, and rebooted. After reboot I reinstalled safestrap and tried again. The result was the same. No install and not reboot to recovery after a supposed successful install. Would re-rooting possibly make a difference?
Click to expand...
Click to collapse
it could lookout has been known to cause problems for kingo try unrooting and start over
Unroot, Re-root, Retry
jerrycoffman45 said:
it could lookout has been known to cause problems for kingo try unrooting and start over
Click to expand...
Click to collapse
So I unrooted using Kingo, re-rooted, reinstalled safestrap, and it is still a no go. Still the same result as the video above. Now I really don't know what to do.
I am at a loss
Sent from my SM-N9005 using Tapatalk
jerrycoffman45 said:
I am at a loss
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Let me go ahead and make it weirder. I just rooted AND installed safestrap on my wife's note 3. It worked perfectly and without any problems. The only difference between our phones, that I'm aware of, is the color. She has white and I have black.
The model number, Android version, baseband version, kernel, and build number are all the same. I would be lying if I said that it isn't making me want to cry.
Mines black and no problems
Sent from my SM-N9005 using Tapatalk
jerrycoffman45 said:
Mines black and no problems
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I'm doing a complete erase of the device now. After it's finish going to root and then *HOPEFULLY* safestrap.
thynis said:
I'm doing a complete erase of the device now. After it's finish going to root and then *HOPEFULLY* safestrap.
Click to expand...
Click to collapse
And now it seems to be stuck at the AT&T loading screen....
I can't win today.
thynis said:
And now it seems to be stuck at the AT&T loading screen....
I can't win today.
Click to expand...
Click to collapse
I booted into Odin, wiped data & caches, rebooted, installed nova launcher, rooted the phone, checked to see if it was rooted (it was), rebooted, installed safestrap.apk, opened safestrap and installed, and..... same thing..... I am now completely out of ideas. It would seem like I am destined to have no custom rom installations.
Maybe a bad download of safestrap other than that I am out of ideas
Sent from my SM-N9005 using Tapatalk
jerrycoffman45 said:
Maybe a bad download of safestrap other than that I am out of ideas
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I actually used the same download that I used on my wife's. I also downloaded earlier versions of safestrap and tried them. Much like you I am out of ideas. Is it possible to use something other then safestrap? Maybe clockwork mod and then install roms manually like I do for my nexus 7? Or is safestrap the only only option due to Knox? Also, Thank you for the help. If for some reason
I stumble upon an answer I'll let you and others know. Pretty clueless at this point though. Thanks again.
jerrycoffman45 said:
Maybe a bad download of safestrap other than that I am out of ideas
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I actually used the same download that I used on my wife's. I also downloaded earlier versions of safestrap and tried them. Much like you I am out of ideas. Is it possible to use something other then safestrap? Maybe clockwork mod and then install roms manually like I do for my nexus 7? Or is safestrap the only only option due to Knox? Also, Thank you for the help. If for some reason
I stumble upon an answer I'll let you and others know. Pretty clueless at this point though. Thanks again.
dude, my wife just got a black N3. this is not very encouraging.
good luck, hope you get it working.
It is the only way because of the locked bootloader there is a way with Odin but it is only one rom Knox raid kit kat version
Sent from my SM-N9005 using Tapatalk
smokarz said:
dude, my wife just got a black N3. this is not very encouraging.
good luck, hope you get it working.
Click to expand...
Click to collapse
I wouldn't be concerned. Whatever it is it seems that it's only my phone. I'm 99.9% positive that it has nothing to do with the color or with the black note being different.
jerrycoffman45 said:
It is the only way because of the locked bootloader there is a way with Odin but it is only one rom Knox raid kit kat version
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
That's what I figured. No biggie though. I am pretty satisfied with root and xposed framework. I've managed to delete and/or disable most of the apps that I don't use our want. I'll try to figure it out again if/when a new version of safestrap is released. Granted, I really don't think that it'll make a difference. My phone seems to have a grudge against safestrap. Oh well. Thanks again!
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
Can I install stock recovery and then try to take a ota to update. Will I loose root and will I loose my rom? Will I be able to reinstall a rom or will I need to reroot?
you can try, you shouldn't loose root or anything but once you have unlocked and flashed stuff I doubt stock recovery will like your system enough to take the update. try this http://forum.xda-developers.com/showthread.php?p=53518227
HOW Change ...... ???
Sent from my SM-T217S using XDA Free mobile app
From my understanding, as long as /system is stock, you can install the stock recovery and then take the OTA. Afterwards, you'll need to re-root your phone. Make a backup of your current setup before you get started. Once you've taken the update and get rooted again, you can always restore your backup.
Sent from my HTC device
Magnum enforcer is correct.
Sent from my 831C using XDA Premium 4 mobile app
I will give it a try this weekend and let you know how it goes.
Edit does not work but thanks for helping me.
Must be the fact that I am s on. We need that s off before we can do anything as far as updating
This one is tricky. I flashed the stock rooted rom from mikmik, I then unrooted and flashed the stock recovery via fast boot. When applying the Ota, it fails because the build.prop is not stock. Comes back with an error like /system/build.prop unexpected.
dilaynie said:
This one is tricky. I flashed the stock rooted rom from mikmik, I then unrooted and flashed the stock recovery via fast boot. When applying the Ota, it fails because the build.prop is not stock. Comes back with an error like /system/build.prop unexpected.
Click to expand...
Click to collapse
I just tried it to and did the same exact thing except I had boot loops as we'll.
when I flashed back to the stock recovery to take the recent OTA, I had a reboot bootloop like every 2-3 minutes, I was ready to throw the phone against a wall, then it hit that I read recently someone else had the same issue, and mentioned a factory reset fixing the issue, yup after a factory reset, the reboot bootloop was gone, I just now rerooted and flashed a backup
sent from HTC M8 using tapatalk
scott_0 said:
when I flashed back to the stock recovery to take the recent OTA, I had a reboot bootloop like every 2-3 minutes, I was ready to throw the phone against a wall, then it hit that I read recently someone else had the same issue, and mentioned a factory reset fixing the issue, yup after a factory reset, the reboot bootloop was gone, I just now rerooted and flashed a backup
sent from HTC M8 using tapatalk
Click to expand...
Click to collapse
But after all that we're you able to update the radio and second did it fix the signal issues?
jdmohn12 said:
But after all that we're you able to update the radio and second did it fix the signal issues?
Click to expand...
Click to collapse
yes, I was able to take the latest OTA, and no, it did not help with my signal at all, my device didn't drop calls or anything, but it has a hard time latching onto lte at times before and after the OTA.......
sent from HTC M8 using tapatalk
Do we know how to get passed the build.prop error?
Sent from my 831C using XDA Free mobile app
this might be a really stupid question (and my first post no less), but does performing a factory reset take me back to stock, unrooted form?
currently i am rooted with S-on, TWRP and Chainfire SU.
i followed a youtube video to root and im basically clueless with regards to doing anything more.
thanks in advance.
Tbaggington said:
this might be a really stupid question (and my first post no less), but does performing a factory reset take me back to stock, unrooted form?
currently i am rooted with S-on, TWRP and Chainfire SU.
i followed a youtube video to root and im basically clueless with regards to doing anything more.
thanks in advance.
Click to expand...
Click to collapse
no, a factory reset will not unroot you, you need to restore a stock backup, then flash stock recovery in fastboot to unroot while s-on
sent from HTC M8 using tapatalk
scott_0 said:
no, a factory reset will not unroot you, you need to restore a stock backup, then flash stock recovery in fastboot to unroot while s-on
sent from HTC M8 using tapatalk
Click to expand...
Click to collapse
Thank you. I saved a stock backup (i think) while rooting so ill see what i can do tonight. fastboot is the white background screen that uses volume buttons to select, right?
Tbaggington said:
Thank you. I saved a stock backup (i think) while rooting so ill see what i can do tonight. fastboot is the white background screen that uses volume buttons to select, right?
Click to expand...
Click to collapse
yes sir, power off the phone completely, hold down power and volume down, select fastboot
sent from HTC M8 using tapatalk
Hey everyone.
I've spent the better of the last three hour scouring the inter webs, Google, and these forums trying to find the answers to my questions - but to no avail (I've found partial answers, but I am afraid a partial answer could lead to a total brick).
Here we go:
I bought one of the first Sprint HTC One M8's through Amazon. Here are the details:
Model: 831C
Android Version 4.4.2
Software Version 1.12.651.17
Unlocked but S-On (Using TWRP)
Naturally, right out of the box I rooted it. However, I did not save the original ROM.
* I want to restore the phone to its original state so I can accept the OTA update and hopefully address the god-awful cell signal.
I've found a lot of stock recoveries online, but none that match 1.12.651.17.
Do I need to find that specific recovery to flash to my phone? Will another one work (e.g. 1.54.654.13)?
I've never worried about saving my stock recovery in the past (been rooting since the HTC Evo days) but it looks like not doing so finally caught up with me.
Thanks in advance.
PS I did find something 1.12.651.17 related here, but how to flash this to my phone (or whether or not it will brick) is beyond me. I've downloaded all 6 files and am waiting to figure out how the heck to get them to my phone.
http://forum.xda-developers.com/showthread.php?t=2736048