Hello guys. I got my Note 8 at the holidays, I used OTA to get the 4.2.2 update, and I used autoroot, and just checked my recovery and I have Philz touch 5 installed.
When I check for OTA updates, I find the message your device has been modified, no updates available.
I am running stock 4.2.2. Do I need to unroot and return to stock recovery for OTA updates? I did not remove any apps or freeze anything. The only difference is recovery and being rooted. This question is in anticipation of the release of 4.4 kitkat, slated to be pushed to our device- but I'm not holding my breath for when that will be.
Thanks for your input!
sashusmom said:
Hello guys. I got my Note 8 at the holidays, I used OTA to get the 4.2.2 update, and I used autoroot, and just checked my recovery and I have Philz touch 5 installed.
When I check for OTA updates, I find the message your device has been modified, no updates available.
I am running stock 4.2.2. Do I need to unroot and return to stock recovery for OTA updates? I did not remove any apps or freeze anything. The only difference is recovery and being rooted. This question is in anticipation of the release of 4.4 kitkat, slated to be pushed to our device- but I'm not holding my breath for when that will be.
Thanks for your input!
Click to expand...
Click to collapse
Hi, I had rooted my 4.2.2 and installed a bunch of root apps... At this time, my Kies says there are no updates available. You will have to wait for 4.4.3 to come out for any update feature to work.
For myself I will do a factory system reset to bring my tablets update apps out of freeze and clear out any cache and the apps that were installed. Once the tablet is booted, I use Kies to push the new firmware once it is released.
Care should be used in restoring apps... many are not 4.4.3 compatible like 4.2.2. So some issues will arise with using customizations. I may hold off another year before installing 4.4.3... I don't like being a tester, been doing that for 30 years now, and like the stability of 4.2.2.
gooberdude said:
Hi, I had rooted my 4.2.2 and installed a bunch of root apps... At this time, my Kies says there are no updates available. You will have to wait for 4.4.3 to come out for any update feature to work.
For myself I will do a factory system reset to bring my tablets update apps out of freeze and clear out any cache and the apps that were installed. Once the tablet is booted, I use Kies to push the new firmware once it is released.
Care should be used in restoring apps... many are not 4.4.3 compatible like 4.2.2. So some issues will arise with using customizations. I may hold off another year before installing 4.4.3... I don't like being a tester, been doing that for 30 years now, and like the stability of 4.2.2.
Click to expand...
Click to collapse
Thanks for that reply. So, will putting back to factory system reset take root off too? And restore factory recovery? Thanks again gooberdude.
I have kies set up. And good tip about apps not being compatible with updated platform. I hope to remember that when the time comes!!
sashusmom said:
Thanks for that reply. So, will putting back to factory system reset take root off too? And restore factory recovery? Thanks again gooberdude.
I have kies set up. And good tip about apps not being compatible with updated platform. I hope to remember that when the time comes!!
Click to expand...
Click to collapse
Actually if you are using SuperSU you can do a complete wipe of root... Titanium Backup also has a root remover option. I think both force a reboot when given the ok to wipe. I found by doing the factory reset clears out root and all the apps as well all in one stroke. Though it will take some time while it initializes a fresh copy of the OS.
Rooting does not play with boot loaders, or partitioning. It is just like any common app so to speak but are system files to allow root access permissions with apps. So even if you leave a root alone, a ROM upgrade should overwrite the root files as they are not protected or hard encoded into a partition in any way.
I do believe any full ROM upgrade will remove all system mods. But it is good practice to wipe the old OS settings by doing a factory reset. Kies will do all that is needed for installing a new ROM. As it is designed to do that function in the best manner possible.
For the most part Odin is a tool that requires a certain amount of user input to perform tasks... it is not fully automatic as to clearing and formatting key areas before loading custom firmware. As custom firmwares may load differently than OEM ROMs.
gooberdude said:
Actually if you are using SuperSU you can do a complete wipe of root... Titanium Backup also has a root remover option. I think both force a reboot when given the ok to wipe. I found by doing the factory reset clears out root and all the apps as well all in one stroke. Though it will take some time while it initializes a fresh copy of the OS.
Rooting does not play with boot loaders, or partitioning. It is just like any common app so to speak but are system files to allow root access permissions with apps. So even if you leave a root alone, a ROM upgrade should overwrite the root files as they are not protected or hard encoded into a partition in any way.
I do believe any full ROM upgrade will remove all system mods. But it is good practice to wipe the old OS settings by doing a factory reset. Kies will do all that is needed for installing a new ROM. As it is designed to do that function in the best manner possible.
For the most part Odin is a tool that requires a certain amount of user input to perform tasks... it is not fully automatic as to clearing and formatting key areas before loading custom firmware. As custom firmwares may load differently than OEM ROMs.
Click to expand...
Click to collapse
That's what I thought too. I am surprised that OTA says I have altered the OS, so I can't do OTA upgrade. The only thing I think I have done is root. I just can't remember 3 months ago if I tweaked it any other way.
I have used ODIN- mostly when I got this tablet back in November. Had to learn how to use it, but it was fine. I always read 3 times, and do things correctly Sort of like measure twice, cut once:silly: Most likely will odin back to stock when the time comes. More work, more brain power required
sashusmom said:
That's what I thought too. I am surprised that OTA says I have altered the OS, so I can't do OTA upgrade. The only thing I think I have done is root. I just can't remember 3 months ago if I tweaked it any other way.
I have used ODIN- mostly when I got this tablet back in November. Had to learn how to use it, but it was fine. I always read 3 times, and do things correctly Sort of like measure twice, cut once:silly: Most likely will odin back to stock when the time comes. More work, more brain power required
Click to expand...
Click to collapse
I re-read your original post... you said you installed a custom recovery. The only way to get your OTA back is to do a factory root load. There was one to download somewhere on a rooting thread, or on a custom recovery thread.
If you do perform the custom recovery removal, you may also have to run triangle away to clear out the counters and reset to zero.
Since I had a full custom setup before reverting back to OEM, I had everything done in order. Triangle away running to clear counter, custom recovery and SuperSu.
Before I started with Odin to load my factory ROM, I first removed root with SuperSU, as Triangle Away was properly setup to perform the clear counter. Once I removed SuperSU and rebooted. I then ran Triangle Away and had it reset to boot to stock recovery uploader. Then used Odin to perform the factory ROM install.
=================
Now since you are probably jumping around... I would try seeing if your custom recovery is still intact. Try to boot into your custom recovery, an if so clear all cache and userdata and format your partition, and load the factory ROM from SD. It may perform all the actions for your OEM ROM to be detected properly.
If you by chance have cleared out the custom recovery, then it is a matter of installing Triangle away, and performing the reset of counters. Once done and rebooted, Kies should show your device's ROM info without any issues from your previous customizations.
gooberdude said:
I re-read your original post... you said you installed a custom recovery. The only way to get your OTA back is to do a factory root load. There was one to download somewhere on a rooting thread, or on a custom recovery thread.
If you do perform the custom recovery removal, you may also have to run triangle away to clear out the counters and reset to zero.
Since I had a full custom setup before reverting back to OEM, I had everything done in order. Triangle away running to clear counter, custom recovery and SuperSu.
Before I started with Odin to load my factory ROM, I first removed root with SuperSU, as Triangle Away was properly setup to perform the clear counter. Once I removed SuperSU and rebooted. I then ran Triangle Away and had it reset to boot to stock recovery uploader. Then used Odin to perform the factory ROM install.
=================
Now since you are probably jumping around... I would try seeing if your custom recovery is still intact. Try to boot into your custom recovery, an if so clear all cache and userdata and format your partition, and load the factory ROM from SD. It may perform all the actions for your OEM ROM to be detected properly.
If you by chance have cleared out the custom recovery, then it is a matter of installing Triangle away, and performing the reset of counters. Once done and rebooted, Kies should show your device's ROM info without any issues from your previous customizations.
Click to expand...
Click to collapse
Great info! Thank you Gooberdude! And I don't Jump .LOL. I just take it one step at a time....Smoothe, then if things are screwed up, I jump around!!! And call out for help!!! And duh- I forgot custom recovery is a problem.
I think I have access to both recoveries. Is that possible? I think I can get into the stock recovery by holding down the correct buttons sequence, but can get into Philz by using my cheat app that I really love, Flapps PowerTool. I'll review what I have and how to do the button sequence to pull up stock recovery and post back.
Thank you for the detailed instructions...Appreciate it. It will probably be awhile before kit kat is put out for our Note 8's anyway.
*********************************************************
Nope. Just Philz custom.
sashusmom said:
Hello guys. I got my Note 8 at the holidays, I used OTA to get the 4.2.2 update, and I used autoroot, and just checked my recovery and I have Philz touch 5 installed.
When I check for OTA updates, I find the message your device has been modified, no updates available.
I am running stock 4.2.2. Do I need to unroot and return to stock recovery for OTA updates? I did not remove any apps or freeze anything. The only difference is recovery and being rooted. This question is in anticipation of the release of 4.4 kitkat, slated to be pushed to our device- but I'm not holding my breath for when that will be.
Thanks for your input!
Click to expand...
Click to collapse
Here ya go http://forum.xda-developers.com/showthread.php?p=50156744
Sent from my SM-N900V using Tapatalk
Related
After getting the phone, I right away flash it with google's 4.1.1 ROM. After that I rooted it and fastboot enable with unlocked.
Since 4.1.2 came out in OTA, I have been unable to update it successfully.
I did get prompt asking me to update and when I agree, it will try to update and then reboot to update. However, the update will fail and I will still get stuck in 4.1.1. The failed update has not affected the phone in anyway. So I continue using it at 4.1.1.
Anyone can provide simple instructions on how to update to 4.2.1 without erasing all my data? Especially contacts and emails. I have read there are numerous ways like nandroid and titanium and so on. Then there are mention that I will need to root the phone again after updating and so on. This is really overwhelming for me. Too much information and not sure which direction to go.
Previously I used nexus toolkit to convert the phone to yakjuw (or something) and updated to 4.1.1. Can I use this nexus toolkit again for it? Or OTA is a better way to preserve DATA?
Very sorry if there is already a thread for this cause I can't find it. I am new to this forum and the amount of information especially in galaxy nexus section is overwhelming but at the same time AWESOME!. Great phone with great community support.
Do you have the stock recovery or clockwork?
ironside2011 said:
Do you have the stock recovery or clockwork?
Click to expand...
Click to collapse
I don't think I have the stock recovery. But that can be easily downloaded, right?
As for CWM, I don't think I have it installed. I tried to keep the phone as vanilla as possible. However, I have tried CWM on other android devices before and wouldn't mind installing this.
First off, check your accounts settings. Sync should be set up for both contacts and emails (you should have a gmail account, right?). So that's of no concern. Turn your phone off. Now hold both volume buttons and press power [fastboot mode]. Use volume keys to scroll so top says recovery, then press power. Now you'll see what recovery you have, either android or cwm. If it's android, then you can hold volume up and press the power button to get the menu, which includes reboot now. If it's stock recovery, perhaps the update failed because you're rooted. Try OTA Rootkeeper, hide your root, then clear google services framework, and try the update again, and see if it sticks.
You should find out what version you have, btw, yakju, takju, etc.. You can do this by opening maps, settings, then about.
O, and OTA will preserve data, toolkit will likely wipe all in order to flash whole rom, not just update. I'd say that the common wisdom is skip the toolkits until you fully understand what, how, and why they work in such and such a way.
bodh said:
First off, check your accounts settings. Sync should be set up for both contacts and emails (you should have a gmail account, right?). So that's of no concern. Turn your phone off. Now hold both volume buttons and press power [fastboot mode]. Use volume keys to scroll so top says recovery, then press power. Now you'll see what recovery you have, either android or cwm. If it's android, then you can hold volume up and press the power button to get the menu, which includes reboot now. If it's stock recovery, perhaps the update failed because you're rooted. Try OTA Rootkeeper, hide your root, then clear google services framework, and try the update again, and see if it sticks.
You should find out what version you have, btw, yakju, takju, etc.. You can do this by opening maps, settings, then about.
O, and OTA will preserve data, toolkit will likely wipe all in order to flash whole rom, not just update. I'd say that the common wisdom is skip the toolkits until you fully understand what, how, and why they work in such and such a way.
Click to expand...
Click to collapse
Ok..let me summarize:
1) Check whether phone is stock recovery or CWM.
2) If stock recovery then install OTA rootkeeper and try update OTA again.
3) if CWM recovery then .....restore back to stock recovery???
The easiest thing you can do is backup your phone. Get a toolkit for your phone. Download the factory image for your phone from Google and flash it. You will have 4.2.1 in a jiff.
Sent using xda premium.
[email protected] said:
The easiest thing you can do is backup your phone. Get a toolkit for your phone. Download the factory image for your phone from Google and flash it. You will have 4.2.1 in a jiff.
Sent using xda premium.
Click to expand...
Click to collapse
backup using? titanium? a bit troublesome when nexus does not have sdcard. Storage is almost full.
Platform
android:samsung-maguro-Galaxy Nexus
Device
samsung yakju
ClockworkMod Recovery v5.8.0.2
What's the best way to update now without losing data?
exactly.
abubin said:
Ok..let me summarize:
1) Check whether phone is stock recovery or CWM.
2) If stock recovery then install OTA rootkeeper and try update OTA again.
3) if CWM recovery then .....restore back to stock recovery???
Click to expand...
Click to collapse
3) fastboot flash recovery *recovery.img*, then you'd try the OTA.
Have you consulted: http://forum.xda-developers.com/showthread.php?t=1419170
and http://forum.xda-developers.com/showthread.php?t=1626895 ?
these two threads should be able to teach you almost the exact processes...
btw, just found this: http://forum.xda-developers.com/showpost.php?p=36050897&postcount=9
Even though that's takju, it should be identical to yakju.
And if confident that you havent modified anything other than recovery and root, id still try to flash the stock recovery and ota first.
abubin said:
After getting the phone, I right away flash it with google's 4.1.1 ROM. After that I rooted it and fastboot enable with unlocked.
Since 4.1.2 came out in OTA, I have been unable to update it successfully.
I did get prompt asking me to update and when I agree, it will try to update and then reboot to update. However, the update will fail and I will still get stuck in 4.1.1. The failed update has not affected the phone in anyway. So I continue using it at 4.1.1.
Anyone can provide simple instructions on how to update to 4.2.1 without erasing all my data? Especially contacts and emails. I have read there are numerous ways like nandroid and titanium and so on. Then there are mention that I will need to root the phone again after updating and so on. This is really overwhelming for me. Too much information and not sure which direction to go.
Previously I used nexus toolkit to convert the phone to yakjuw (or something) and updated to 4.1.1. Can I use this nexus toolkit again for it? Or OTA is a better way to preserve DATA?
Very sorry if there is already a thread for this cause I can't find it. I am new to this forum and the amount of information especially in galaxy nexus section is overwhelming but at the same time AWESOME!. Great phone with great community support.
Click to expand...
Click to collapse
OTA update will not work on a rooted phone. You will have to flash the actual 4.2.1 ROM.
It should work with OTARootkeeper, and hidden root, I've done it myself. (read above)
bodh said:
It should work with OTARootkeeper, and hidden root, I've done it myself. (read above)
Click to expand...
Click to collapse
I will use this method. I can find OTARootkeeper. But can't find hidden root apps.
Not sure which is the one:
https://play.google.com/store/apps/details?id=com.amphoras.hidemyroot&hl=en
https://play.google.com/store/apps/details?id=com.troy1103.hideyourroot&hl=en
I guess i used the wrong words.. Open OTA Rootkeeper, select backup su, then temp un-root. You can download a rootchecker after this to check if your system shows as rooted or not rooted.
I tried to OTA update but failed.
First, I use OTA rootkeeper to hide root. After that I tried to update but the phone boot up to CWM and show update failed. So I then use nexus toolkit to change back to stock recovery. However, after doing that...when I check for update in the phone, it says no update.
After doing some reading, I try to update using manual method. Which is to boot into stock recovery and then choose update from cache. I have checked the update zip file in cache folder. Then I boot into stock recovery. But in stock recovery, I do not see any option to update from cache. I only see update from ADB or update from SDCARD (or USB...forgot). Tried both and it doesn't work.
The Nexus Toolkit must have restored my stock recovery back to the GSM phone that have SDCARD. Mine does not have SDCARD slot. I do not dare to restore from other recovery.img file. Anyone can point me to the right direction for a recovery.img that will not screw up my stock recovery or the phone at all?
Thanks.
The 'SDCARD' is the onboard storage, nothing wrong there
Easiest thing is to backup your data using Titanium Backup, flash the factory 4.2.1 image, reroot and then restore the backup
EddyOS said:
The 'SDCARD' is the onboard storage, nothing wrong there
Easiest thing is to backup your data using Titanium Backup, flash the factory 4.2.1 image, reroot and then restore the backup
Click to expand...
Click to collapse
So much hassle just for OTA. I guess now my only choice is to use this method. Thanks.
Ultimately, if you want the OTAs stay 100% stock. If you wanna root, go custom
Since you now have stock recovery, which is probably why the OTA failed [though there could be many reasons], Have you tried to clear Google services framwork data (under applications, all), to get the update notification and try again? If it stills fails, then at this point the others are right. Titanium backup method..Just skip the system apps in the backup, right guys?
Hello
I have Galaxy S3 (ATT), currently i'm stuck at 4.1.1. I can't update to 4.1.2 or 4.3.
I had my phone rooted by the Galaxy tookkit.
What I tried so far is.
1) recovered recovery back to stock (rooted stayed), update failed
2) used the toolkit to remove root, also removed busybox and superuser, toolkit put the clockwork recovery back in., update failed.
How can I update to 4.3?
nekrosoft13 said:
Hello
I have Galaxy S3 (ATT), currently i'm stuck at 4.1.1. I can't update to 4.1.2 or 4.3.
I had my phone rooted by the Galaxy tookkit.
What I tried so far is.
1) recovered recovery back to stock (rooted stayed), update failed
2) used the toolkit to remove root, also removed busybox and superuser, toolkit put the clockwork recovery back in., update failed.
How can I update to 4.3?
Click to expand...
Click to collapse
have you tried using kies to go to 4.1.2 and then manually update to 4.3?
rkant18 said:
have you tried using kies to go to 4.1.2 and then manually update to 4.3?
Click to expand...
Click to collapse
how? Kies is telling me 4.1.1 is the latest.
anyone else?
Tried again yesterday, no root, stock recovery, superuser, busybox all removed. And it downloaded 650mb updated it failed at 31%, this update was interrupted.
nekrosoft13 said:
anyone else?
Tried again yesterday, no root, stock recovery, superuser, busybox all removed. And it downloaded 650mb updated it failed at 31%, this update was interrupted.
Click to expand...
Click to collapse
I used this thread to get back to stock so my flash counter would be reset back to 0 - http://forum.xda-developers.com/showthread.php?t=2363882
Then I used KIES recovery to reflash 4.1.1 just to be sure it was exactly what Samsung intended.
Then when i checked for OTA update (while on 4.1.1) it found one and took a while to download. When it installed the update, it was already to 4.3 - i guess it skipped the 4.1.2 official update.
I then did a master reset from the settings menu and deleted everything so that 4.3 could start fresh. I haven't had any problems with the stock 4.3.
Goofy? Did u try the ota to get to 4.3
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Prometh1216 said:
Goofy? Did u try the ota to get to 4.3
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
yes, it fails at 31% phones reboots and once booted it tells me update was interrupted.
jack man said:
I used this thread to get back to stock so my flash counter would be reset back to 0 - http://forum.xda-developers.com/showthread.php?t=2363882
Then I used KIES recovery to reflash 4.1.1 just to be sure it was exactly what Samsung intended.
Then when i checked for OTA update (while on 4.1.1) it found one and took a while to download. When it installed the update, it was already to 4.3 - i guess it skipped the 4.1.2 official update.
I then did a master reset from the settings menu and deleted everything so that 4.3 could start fresh. I haven't had any problems with the stock 4.3.
Click to expand...
Click to collapse
Thanks will try that, you did a factory reset prior to flashing this?
At work now, so can't download the files, but will try it later.
What did you use to backup your files?
nekrosoft13 said:
Thanks will try that, you did a factory reset prior to flashing this?
At work now, so can't download the files, but will try it later.
What did you use to backup your files?
Click to expand...
Click to collapse
I didn't factory reset before flashing because i knew that when I use KIES to do a recovery it will erase everything on the phone. However, I did wipe cache and dalvic in recovery beforehand... well, come to think of it, i probably did also wipe data before flashing the 4.1.1 that resets the flash counter.
Regarding backing up my files, I have all the files I need on an external sd card so all i have to do is take out the card. Plus, I also use Google Drive to store my pictures as I take them with the camera. no real need to back-up things because things are saved somewhere else, and not directly to the phone. I will probably use the phone storage more now, though since I won't be flashing anything for a while. Taking a break from flashing.
Hope it works out for you.
jack man said:
I didn't factory reset before flashing because i knew that when I use KIES to do a recovery it will erase everything on the phone. However, I did wipe cache and dalvic in recovery beforehand... well, come to think of it, i probably did also wipe data before flashing the 4.1.1 that resets the flash counter.
Regarding backing up my files, I have all the files I need on an external sd card so all i have to do is take out the card. Plus, I also use Google Drive to store my pictures as I take them with the camera. no real need to back-up things because things are saved somewhere else, and not directly to the phone. I will probably use the phone storage more now, though since I won't be flashing anything for a while. Taking a break from flashing.
Hope it works out for you.
Click to expand...
Click to collapse
have you ever tried Helium? I was planning to use that for backup of my apps data.
last time I recovered/flashed phone was with Windows Mobile... so yeah really behind with all of this.
So if I first use helium for backup and then do factory reset, then flash the stock 4.1.1.
I know google account has all my contacts and calendar.
After I have the stock 4.1.1 back I should be able to update to 4.3 and from there restore the backup?
nekrosoft13 said:
have you ever tried Helium? I was planning to use that for backup of my apps data.
last time I recovered/flashed phone was with Windows Mobile... so yeah really behind with all of this.
So if I first use helium for backup and then do factory reset, then flash the stock 4.1.1.
I know google account has all my contacts and calendar.
After I have the stock 4.1.1 back I should be able to update to 4.3 and from there restore the backup?
Click to expand...
Click to collapse
Never used Helium. I have use Titanium Backup before. It's widely used for backing up app data. You can get it in the Play Store. Make sure you don't try to restore system data - it will cause all kinds of trouble. I don't usually restore app data anymore - well, now that I'm on stock I can't, anyway. I always had some kind of issue, whether it be small or big, when I restored data. who knows, maybe I wasn't doing it exactly right.
I'm not sure if restoring apps from 4.1.1 to a 4.3 base would be safe or not. remember, if you try, that means you'll have to root the 4.3 and that will trip your warranty bit count off of zero, so if you're concerned about warranty, you shouldn't root. (if you upgrade to 4.3 stock, you can go to download mode and see that they now have included two flash counts: one to count custom binaries (that can be reset) and the other one called warranty bit, that no one here knows how to reset yet.)
according to Helium, it doesn't require root. I will make a backup just in case, just want my angry birds progress...
still at work, so I can't download the file (yet), so how exactly does this work, since it says you don't need odin?
nekrosoft13 said:
according to Helium, it doesn't require root. I will make a backup just in case, just want my angry birds progress...
still at work, so I can't download the file (yet), so how exactly does this work, since it says you don't need odin?
Click to expand...
Click to collapse
After you download it, make sure it's on your internal sd card in the phone. Boot into ClockWorkMod recovery, wipe data/factory reset, clear cache, clear dalvic from the advanced menu, then flash the zip. that's it. near the end of the flash it will ask you if you want to keep root. i chose no since I knew I was going to be update to the official release. I've heard of people having problems trying to update OTA with root.
Just make sure that updating to 4.3 is what you want because it will limit what you can do with the device after you have the new bootloaders.
I used factory reset and now my phone is stuck at the tmobile logo. I was rooted before but I removed SuperSU before doing the factory reset. I also tried wiping out the data at recovery mode but I'm still having the same problem. Is there anyone that can help me fix my Note 2?
kevzz01 said:
I used factory reset and now my phone is stuck at the tmobile logo. I was rooted before but I removed SuperSU before doing the factory reset. I also tried wiping out the data at recovery mode but I'm still having the same problem. Is there anyone that can help me fix my Note 2?
Click to expand...
Click to collapse
I hope you didn't wipe system my mistake
Wiping /system is a trivial problem to solve, just flash again and voilà.
What are you trying to accomplish exactly? If you want back to stock, flash the appropriate ROM with Odin, boot to stock recovery, factory reset and call it a day. Unless you've messed up your NV items or done something incorrect with the bootloader, that's pretty much all there is to it.
I wiped out the cache partition at recovery mode and now my phone is working just fine. The reason I factory reset my phone because I want to try if the system will let me update OTA after a reset. Unfortunately it won't let me update still because my phone was rooted. Is there a way to bypass this so I'd be able to update my phone?
Ah! Flashing back to a non-rooted ROM would allow the OTA mechanisms to work normally.
There's inherently a risk for a ROM update to patch something that's been modified in ways it does not expect, such as root on a stock ROM.
In the case of Samsung devices, you could always Odin flash back to stock, or a pre-rooted stock image.
Darkshado said:
Ah! Flashing back to a non-rooted ROM would allow the OTA mechanisms to work normally.
There's inherently a risk for a ROM update to patch something that's been modified in ways it does not expect, such as root on a stock ROM.
In the case of Samsung devices, you could always Odin flash back to stock, or a pre-rooted stock image.
Click to expand...
Click to collapse
Well I've always been on stock. I just rooted my phone before for some apps and that's it. I never use any custom rom. Im still at stock but wont let me update still
Consider yourself as "custom" the moment you change anything on your /system partition, that includes root.
Samsung ROMs have this check that's displayed somewhere in settings, where your ROM will say if it thinks it's been modified. If so, OTA updates will be disabled.
Factory reset alone won't completely unroot you. You must unroot, then factory reset.
At this point, since you just want a stock rooted ROM and have already factory reset, you could flash the latest pre-rooted ROM with Odin. Will probably be simpler than prodding the phone into getting the OTA.
I am trying to restore a backup made with TWRP. Here's what has happened so far:
Flashed TWRP several weeks ago. I've made several backups with no problems.
Flashed NK2 radio with no apparent problems.
Full wipe of phone. Phone was not rooted at this point.
Flashed 5.01 GPE ROM.
Phone boots and I get the "Kernal not SELinux enforcing" message (ugh...KNOX). Phone won't boot to new rom. I can only get to TWRP.
Try to restore backup. TWRP checks MD5 on backup-it passes and then screen blanks and TWRP reboots. It does this several times.
After research I restore phone to stock MB4 through Odin.
Phone boots into Android and is indeed 4.4.2 MB4.
Using Unified Toolkit re-flash TWRP and then proceed to root phone. After procedure SuperSU gives me "SuperSU has stopped" msg. Follow toolkit procedure to get around KNOX. SuperSU runs and I also install Busybox. Reboot phone. Root not held. Redo toolkit procedures to attain root. Still lose it upon reboot.
TWRP still reboots when trying to do anything involved with the filesystem (restore backup--wipe cache and dalvik--none works. TWRP blanks and reboots.) . At this point I'm scratching my head. I'd like to restore the backup and also root and change to GPE. I'm thinking this comes down to not being able to do anything in the filesystem due to root not being held. Any suggestions as to how to get root to stick so I can do the restore and change ROMS? Thanks folks.
Steve KS4KJ
If you don't have root you wouldn't have twrp, you would have the stock recovery.
You need to do a factory reset and start from there.
If you can't do it in twrp, flash back to stock with Odin, then do a factory reset. At this point you may have corrected what got borked by flashing the 5.0 rom.
I would recommend flashing to latest firmware NH7 or NK2 and running phone for 24hrs just to make sure there are no issues and that everything works.
ShinySide has links in general section.
Pp.
PanchoPlanet said:
If you don't have root you wouldn't have twrp, you would have the stock recovery.
You need to do a factory reset and start from there.
If you can't do it in twrp, flash back to stock with Odin, then do a factory reset. At this point you may have corrected what got borked by flashing the 5.0 rom.
I would recommend flashing to latest firmware NH7 or NK2 and running phone for 24hrs just to make sure there are no issues and that everything works.
ShinySide has links in general section.
Pp.
Click to expand...
Click to collapse
In flashing the stock 4.4.2 rom (which is where my phone was when I started this journey) I have done a reset haven't I? That is what I did when the 5.0 GPE rom wouldn't boot. I can certainly try loading the 4.4.4 NK2 rom and seeing what that will do. Pretty sure I did not root before using the toolkit to replace the stock recovery with (originally) CWM and then later with TWRP. I remember wanting to do a Nandroid backup before installing the 4.4.4 OTA (which then didn't work because I had changed the stock recovery). I keep thinking that KNOX is involved with this but not sure what to try to remedy it (other than the 4.4.4 suggestion which I will try). Thanks for the reply.
Steve
The only thing Knox does is tell Samsung if you rooted and installed a custom recovery, and that is only while your still under warranty (12 months ) after you get the phone. After that warranty runs out they don't give a hoot what you do to your phone.
You need to flash it twice so that it works properly, after d/l Samsung info app, in play store and check that you have current bootloader and modem .
And use Chainfire's auto root to root afterwards.
Pp.
PanchoPlanet said:
The only thing Knox does is tell Samsung if you rooted and installed a custom recovery, and that is only while your still under warranty (12 months ) after you get the phone. After that warranty runs out they don't give a hoot what you do to your phone.
You need to flash it twice so that it works properly, after d/l Samsung info app, in play store and check that you have current bootloader and modem .
And use Chainfire's auto root to root afterwards.
Pp.
Click to expand...
Click to collapse
I'll try that. Thanks again.
Hi All,
I have been having some issue with one of my box, it is rooted running stock version 51.1.0.1 .
i have completed the following steps of the rooting process.
1) block updates on router
2) rooted (installed towleroot, supersu, busybox)
3) disabled update on AFTV box via adb command
4) Unlock partial bootloader
5) installed latest CWM at this point fire tv restarts but does not boot up in to CWM recovery.
I can get into CWM via Alt + prntscr + i using my keyboard. i did the wipe data/factory reset thru CWM and it clean up everything i rooted again installed CWM and it still wont boot up in CWM so may the firmware is corrupt?
What should i do? Should just flash pre roted rbox ROM and installed Rbox boot menu and see if i can get in CWM or should i wipe everything from AFTV and start again.
How do i wipe everything out using CWM? I read a lot tread on xda forms but didn't see a detail guide, i would appreciate if someone could give me all the baby step in exact order i should perform and if you could use the same terminology that is used in CWM menu that would be great, please.
Please note i have rooted at least 8 box before (updates blocked, rooted, bootloader unlock, install cwm, installed pre-rooted ROM and Rbox manu) so i am familiar with the process but one can always mess up.
Thank you
You're approaching this in a differnt angle than I'm used to--is there a reason you use stock firmware? With custom recovery, I'd venture to say a factory reset will do what you want it to and performing it will give you a clean slate and though updates will try to download they won't install.
I do this but I run rbox firmware...
1. Reboot recovery
2. Factory reset in cwm
3. Confirm it (this will wipe user data)
4. Reboot system
This should get you back to the registration page. You'll lose EVERYTHING except su. First thing I do is pm disable updates again. Once that's done you should be good tonset it all up--install busybox, all your apps.
I just worry because I use custom ROMs and never did this with stock. On your average android device keeping stock firmware wouldn't bother me but aftv is a little different since there's no doubt they don't want you rooted with custom recovery. I'd go to the dev threads and ask questions or flash prerooted ROMs. You might want to update incrementally as some have reported issues when they skip updates, not critical but it might be in your best interest.
And of course when I refer to updates I mean preroot not stock.
KLit75 said:
You're approaching this in a differnt angle than I'm used to--is there a reason you use stock firmware? With custom recovery, I'd venture to say a factory reset will do what you want it to and performing it will give you a clean slate and though updates will try to download they won't install.
I do this but I run rbox firmware...
1. Reboot recovery
2. Factory reset in cwm
3. Confirm it (this will wipe user data)
4. Reboot system
This should get you back to the registration page. You'll lose EVERYTHING except su. First thing I do is pm disable updates again. Once that's done you should be good tonset it all up--install busybox, all your apps.
I just worry because I use custom ROMs and never did this with stock. On your average android device keeping stock firmware wouldn't bother me but aftv is a little different since there's no doubt they don't want you rooted with custom recovery. I'd go to the dev threads and ask questions or flash prerooted ROMs. You might want to update incrementally as some have reported issues when they skip updates, not critical but it might be in your best interest.
And of course when I refer to updates I mean preroot not stock.
Click to expand...
Click to collapse
Hi,
I did the factory reset from CWM i forgot to mentioned this on intial post, sorry about that. It went thru the whole process, i re rooted and everything but again after installing CWM aftv did not boot in CWM so i thought maybe i should wipe everything out and start over instale fresh stock firmware.
Maybe the fireware is corrupted or the partition. I tried to down grade and upgrade to stock version but AFTV wouldn't installed the updates.
For me go get in CWM using ALT+PRINT SYS+I option is really pain full, after trying if for a 3 days and spending at least 2 hours each day i was able to get in so i thought start from scratch would might work.
thank you
ashsha7877 said:
Hi,
I did the factory reset from CWM i forgot to mentioned this on intial post, sorry about that. It went thru the whole process, i re rooted and everything but again after installing CWM aftv did not boot in CWM so i thought maybe i should wipe everything out and start over instale fresh stock firmware.
Maybe the fireware is corrupted or the partition. I tried to down grade and upgrade to stock version but AFTV wouldn't installed the updates.
For me go get in CWM using ALT+PRINT SYS+I option is really pain full, after trying if for a 3 days and spending at least 2 hours each day i was able to get in so i thought start from scratch would might work.
thank you
Click to expand...
Click to collapse
If I'm hearing you correctly I think I know your problem. You can't flash stock firmware with cwm. Rbox has protections in place thatbwont letbthis happen and for good reason--doing so could brick your device. You need the preroot ROMs. Follow aftvnews starters guide because I only had to do this once and I'm not certain I remember exactly. I think there's a certain version you should start with and some users find its better to update incrementally.