Develop Bugs

Rooting and Modding questions. Final Check

So ive been doing a lot of reading on rooting phones and the best way to go about doing this, but I still have a few questions about the whole process. First IM going to briefly write what I understand about the process and have it corrected and then ask my questions.
To root:
I will follow this guide http://forums.androidcentral.com/ve...ock-bootloader-root-verizon-galaxy-nexus.html
Basically I will make sure all drivers are updated on my computer (samsung and USB)
Use command prompt to unlock the boot loader and then install superboot for the GN
after this process is done and I reboot the phone I will be unlocked and ready to go
Modding
Done through CWM
1. I will download the mod that I want and place it in my phones internal memory.
2. boot into recovery mode with CWM
3. backup the phone with CWM (can anyone tell me where the back up is saved)
4. factory reset the phone
5. install zip from SD card (which will be the mod)
6. reboot back into recovery mode and install Gapps that I downloaded from the cryogen mod wiki through the "install zip from SD card" option. http://wiki.cyanogenmod.com/index.php?title=Latest_Version
7. Reboot phone and i will be good to go
SO my questions:
1. If i missed anything, can you guys quote my steps and add in what i left out in the correct order?
2. How do I update the phone to 4.0.4. If im guessing correctly, I would rename the file to update.zip, and before i modded my phone and after the factory reset I would install that zip onto the phone? I'm just slightly confused on the process
3. How do I uninstall a mod and go back to stock
4. How do I handle OTA updates? I know that with mods, I cant download the OTA automatically. I would guess i would have to uninstall the mod, download and install the update, and then thats where I dont know what to do
5. Is there a way to back up all my apps so when I install a mod or update a mod I can just have them all reinstalled back in and have all the settings restored, without having to download each individual app and change their settings back to what they were previously?
these are all the questions that come to mind presently. Some may arise later.
Thanks in advance, and if some of my questions have already been answered in a previous thread, can you guys just post a link to that thread?
Sent from my Transformer Prime TF201

You dl'ed android sdk yet or all the fastboot files you need?
Sent from my Galaxy Nexus using xda premium

You have it correct. Use titanium backup to save all your app data. And you have to restore a nand backup if you want to undo a mod you flashed. The mod usually instructs you to backup right before flashing, so you can just revert right back if you want.
I wouldn't worry about ota anymore. Being rooted always leads to you being able to flash the latest ota quicker than if you were stock and waiting for your number to be called. Trust me after years of this that's how it always happens.

corban227 said:
So ive been doing a lot of reading on rooting phones and the best way to go about doing this, but I still have a few questions about the whole process. First IM going to briefly write what I understand about the process and have it corrected and then ask my questions.
To root:
I will follow this guide http://forums.androidcentral.com/ve...ock-bootloader-root-verizon-galaxy-nexus.html
Basically I will make sure all drivers are updated on my computer (samsung and USB)
Use command prompt to unlock the boot loader and then install superboot for the GN
after this process is done and I reboot the phone I will be unlocked and ready to go
Modding
Done through CWM
1. I will download the mod that I want and place it in my phones internal memory.
2. boot into recovery mode with CWM
3. backup the phone with CWM (can anyone tell me where the back up is saved)
4. factory reset the phone
5. install zip from SD card (which will be the mod)
6. reboot back into recovery mode and install Gapps that I downloaded from the cryogen mod wiki through the "install zip from SD card" option. http://wiki.cyanogenmod.com/index.php?title=Latest_Version
7. Reboot phone and i will be good to go
SO my questions:
1. If i missed anything, can you guys quote my steps and add in what i left out in the correct order?
2. How do I update the phone to 4.0.4. If im guessing correctly, I would rename the file to update.zip, and before i modded my phone and after the factory reset I would install that zip onto the phone? I'm just slightly confused on the process
3. How do I uninstall a mod and go back to stock
4. How do I handle OTA updates? I know that with mods, I cant download the OTA automatically. I would guess i would have to uninstall the mod, download and install the update, and then thats where I dont know what to do
5. Is there a way to back up all my apps so when I install a mod or update a mod I can just have them all reinstalled back in and have all the settings restored, without having to download each individual app and change their settings back to what they were previously?
these are all the questions that come to mind presently. Some may arise later.
Thanks in advance, and if some of my questions have already been answered in a previous thread, can you guys just post a link to that thread?
Sent from my Transformer Prime TF201
Click to expand...
Click to collapse
There are some things that don't make sense in what you are doing.
1) Yes, you install the correct drivers;
2) Yes, you unlock your bootloader; however, if you want to save any data, it would be better if you root first (before unlocking your bootloader) -- see link in my sig, backup apps/etc. and even do a full backup. Don't forget to copy all of that OFF your device, as unlocking wipes even /sdcard.
3) If you are going to install a custom ROM, then there is no need to root the stock ROM you currently have, only to overwrite it with a custom ROM. Doesn't make sense.
4) If you are installing a custom ROM, you cannot "update" it to 4.0.4, unless the dev releases a 4.0.4 update for that particular ROM.
5) If you are sticking with the stock ROM, look at the link in my sig for either how to update to 4.0.4, or, better yet since you are unlocking your bootloader (which will wipe all your data anyway), flash the full 4.0.4 ROM.
6) OTA updates are only for stock ROMs.
7) You can use Titanium Backup once you are rooted to back up apps and app data.

efrant said:
There are some things that don't make sense in what you are doing.
1) Yes, you install the correct drivers;
2) Yes, you unlock your bootloader; however, if you want to save any data, it would be better if you root first (before unlocking your bootloader) -- see link in my sig, backup apps/etc. and even do a full backup. Don't forget to copy all of that OFF your device, as unlocking wipes even /sdcard.
3) If you are going to install a custom ROM, then there is no need to root the stock ROM you currently have, only to overwrite it with a custom ROM. Doesn't make sense.
4) If you are installing a custom ROM, you cannot "update" it to 4.0.4, unless the dev releases a 4.0.4 update for that particular ROM.
5) If you are sticking with the stock ROM, look at the link in my sig for either how to update to 4.0.4, or, better yet since you are unlocking your bootloader (which will wipe all your data anyway), flash the full 4.0.4 ROM.
6) OTA updates are only for stock ROMs.
7) You can use Titanium Backup once you are rooted to back up apps and app data.
Click to expand...
Click to collapse
What's the difference between a stock rom and a custom rom? I was looking at milestone 4. What is an example of a stock rom because I would prefer that to be able to still do ota updates.
Sent from my Galaxy Nexus

corban227 said:
What's the difference between a stock rom and a custom rom? I was looking at milestone 4. What is an example of a stock rom because I would prefer that to be able to still do ota updates.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
If you are asking that question, more reading is likely in order before you start flashing things.
But anyway: a stock ROM is the ROM Google puts out. They are found here, and instructions on how to flash are in my signature. All other ROMs are custom ROMs.

Gotcha. Ill look it up tonight
Sent from my Galaxy Nexus

I ended up reading more which lead to me unlocking and installing 4.0.4
Im happy with this now and I dont feel the need to custom mod. I need my phone to be functional all the time with out being too time consuming =D thanks for the help and leading me to my conclusion

I would seriously give aokp a try, I promise its worth it. Its the same as stock there's no extra work needed or anything to worry about or deal with. Its that good.

Id say stick with stock. I tried all the custom roms and while customisation options are good, nothing better than knowing your phone is 100 percent stable and secure with a locked bootloader.

biffsmash said:
Id say stick with stock. I tried all the custom roms and while customisation options are good, nothing better than knowing your phone is 100 percent stable and secure with a locked bootloader.
Click to expand...
Click to collapse
I wouldn't recommend re-locking your bootloader if you have unlocked it. Actually, I would recommend that, every time you buy a Nexus device, the first thing you should do is unlock the bootloader. Don't forget, having an unlocked bootloader does not mean you are not "stock". An unlocked bootloader doesn't affect anything (aside from what I mentioned below).
Why you ask? Good question:
Advantages of a locked bootloader
If you lose your device, no one can easily access your data, but only if, in addition to your bootloader being locked, you have the stock recovery installed AND you have USB Debugging disabled AND you have a password on your device. However, this "risk" (if you can call it that) can be mitigated by many apps that can remotely wipe your device.
Disadvantages of a locked bootloader
You cannot use fastboot commands, so you cannot flash or boot images, which can save your butt in certain occasions.
You cannot try out new radios (assuming no root).
You cannot backup your data (i.e., make an image of your device's memory (assuming no root).
You cannot root (on 4.0.4 and later).
You cannot manually update to the latest version of Android once Google starts rolling it out. You have to wait until Google decides it's your turn, which could be minutes to months after the update becomes available.

+1 to working without me thinking. I'm leaving the boot loader unlocked to install any updates Verizon doesn't push through but other than that its staying stock. Plus I really like vanilla ICS AS IT IS
Sent from my Transformer Prime TF201 using Tapatalk 2

[Q] 4.2.2 OTA "Error"

My phone prompted me today that an update to 4.2.2 was available.
Its a takju Nexus running with an unlocked bootloader and rooted but otherwise stock rom.
I've tried to get it to do the update, however it reboots to a screen saying "applying system update" then after a few seconds flicks to a screen with an android with an exclamation mark, and the word Error below.
Is this because i'm rooted? or is there something else going on?
Thanks
Kevin

Extra root files shouldn't cancel out the OTA, however, overwriting system files, or modifying system files will. For example installing busybox on system/bin, modifying etc/host etc. Installing mods and replacing apps on /system may also be the culprit.
Just flash the system.img over your current system, also make sure you're running the corresponding recovery, radio, kernel, and bootloader that came with your takju factory image. Do that and and try the OTA again, should work. If the OTA doesn't show up this time, you can download it from the OTA links thread and sideload it via ADB.
Alternatively you can install a custom recovery directly from your phone, back up all of your apps with TB, and flash Bigxie's 'stock' 4.2.2 if you don't have access, or don't want to mess around with a computer. Of course you won't get direct OTA updates from Google that way, but since he usually update his build pretty quick that shouldn't pose much problem.

I'm unable to update to 4.2.2 as it says "couldn't download". Not sure what's going on here.
P.S : I don't mean to hijack this thread.

chelseaeuro said:
I'm unable to update to 4.2.2 as it says "couldn't download". Not sure what's going on here.
P.S : I don't mean to hijack this thread.
Click to expand...
Click to collapse
Try clearing Google Services Framework's data+cache maybe? Or try in a couple hours, the problem could be in the server.

reysonance said:
Try clearing Google Services Framework's data+cache maybe? Or try in a couple hours, the problem could be in the server.
Click to expand...
Click to collapse
I did that and my update is gone lol. Guess I'll have to wait for a few hours.

I had to force stop the frameworks and then try updating, which worked. Thanks!

reysonance said:
Extra root files shouldn't cancel out the OTA, however, overwriting system files, or modifying system files will. For example installing busybox on system/bin, modifying etc/host etc. Installing mods and replacing apps on /system may also be the culprit.
Just flash the system.img over your current system, also make sure you're running the corresponding recovery, radio, kernel, and bootloader that came with your takju factory image. Do that and and try the OTA again, should work. If the OTA doesn't show up this time, you can download it from the OTA links thread and sideload it via ADB.
Alternatively you can install a custom recovery directly from your phone, back up all of your apps with TB, and flash Bigxie's 'stock' 4.2.2 if you don't have access, or don't want to mess around with a computer. Of course you won't get direct OTA updates from Google that way, but since he usually update his build pretty quick that shouldn't pose much problem.
Click to expand...
Click to collapse
Thanks
Just to confirm, if i flash the system.img over my current system, will that delete all my installed apps/data? Which system.img should i be flashing? the one from 4.2.1?
Is there a list somewhere of the version numbers for the various parts (recovery, radio, kernel and bootloader) so i can check they are correct?
Also, is there a way i can flash the OTA update with some error logging or debug output turned on, so i can see what its actually failing at?
Cheers

Yes, the one from 4.2.1, check under Maps > Settings > About, it should gives you the version you're currently running, download it from the factory images page if you haven't already, and no, it should not wipe any apps+data, but back it up anyway if you're worried, better safe than sorry, I'm generally paranoid about data so I always backup, but no it shouldn't wipe anything. You'll lose root and that's it.
And for the bootloader and all that, it all should come all packaged on the factory image, so if you flash 4.2.1 via toolkit, or manually and haven't installed any radio or kernel you should be safe. IIRC, the bootloader version is PRIMELC03, the radio is XXLH1.

reysonance said:
Extra root files shouldn't cancel out the OTA, however, overwriting system files, or modifying system files will. For example installing busybox on system/bin, modifying etc/host etc. Installing mods and replacing apps on /system may also be the culprit.
Just flash the system.img over your current system, also make sure you're running the corresponding recovery, radio, kernel, and bootloader that came with your takju factory image. Do that and and try the OTA again, should work. If the OTA doesn't show up this time, you can download it from the OTA links thread and sideload it via ADB.
Alternatively you can install a custom recovery directly from your phone, back up all of your apps with TB, and flash Bigxie's 'stock' 4.2.2 if you don't have access, or don't want to mess around with a computer. Of course you won't get direct OTA updates from Google that way, but since he usually update his build pretty quick that shouldn't pose much problem.
Click to expand...
Click to collapse
Very thanks for this explanation. It help me a lot and I finally could update via OTA.

[Q] Help lost Root after updating to Officail 4.12 on SPH-L10

Hello again, I recently got the push for update from device for the 4.1.1 with the mb1 and had TWRP and when I accepted it it booted to recovery and then nothing. So I went to Rom Manager app then updated to the CWM 6.0.3.0 regular no touch then tried to get into recovery and instead got the yellow triangle so then I had to pull battery because it was in odin download mode so no way out unless cut power. When I rebooted I got the update message again then accepted what the heck, it gave me a count down of 700 sec then in went to recovery with the android i believe CWM 6.0.3.0 and it took the official update from Sprint only to find out later on I have no root after checking with root checker app and trying to boot to recovery.
So my million dollar question is now what. I downloaded the [SAMSUNG GALAXY S3 UNIFIED TOOLKIT V7.0] Drivers, Backup, Root, Recovery + MORE [SPR] but only supports 4.1.1 and I dont know if its safe to Root 4.1.2 which is not listed unless I donate but not even sure if its supported otherwise I would donate.
How do I regain Root access the easiest way?
[2013.02.20][SPH-L710] CF-Auto-Root
http://forum.xda-developers.com/showthread.php?t=1963812
or
[SAMSUNG GALAXY S3 UNIFIED TOOLKIT V7.0]
http://forum.xda-developers.com/showthread.php?t=1746680
or other way to bring back super su, root, cmw, adb ,and all the goodies?
Thanks again m8's
Lanboy
=)

lanboy said:
Hello again, I recently got the push for update from device for the 4.1.1 with the mb1 and had TWRP and when I accepted it it booted to recovery and then nothing. So I went to Rom Manager app then updated to the CWM 6.0.3.0 regular no touch then tried to get into recovery and instead got the yellow triangle so then I had to pull battery because it was in odin download mode so no way out unless cut power. When I rebooted I got the update message again then accepted what the heck, it gave me a count down of 700 sec then in went to recovery with the android i believe CWM 6.0.3.0 and it took the official update from Sprint only to find out later on I have no root after checking with root checker app and trying to boot to recovery.
So my million dollar question is now what. I downloaded the [SAMSUNG GALAXY S3 UNIFIED TOOLKIT V7.0] Drivers, Backup, Root, Recovery + MORE [SPR] but only supports 4.1.1 and I dont know if its safe to Root 4.1.2 which is not listed unless I donate but not even sure if its supported otherwise I would donate.
How to I regain Root access the easiest way?
[2013.02.20][SPH-L710] CF-Auto-Root
http://forum.xda-developers.com/showthread.php?t=1963812
or
[SAMSUNG GALAXY S3 UNIFIED TOOLKIT V7.0]
http://forum.xda-developers.com/showthread.php?t=1746680
or other way to bring back super su, root, cmw, adb ,and all the goodies?
Thanks again m8's
Lanboy
=)
Click to expand...
Click to collapse
Ok, I'm going to answer your question.
First off, I'd recommend looking through CNexus' sticky thread about OTAs (always good to look through the stickies before you post). You'll see exactly why your OTA is failing.
Since you say that you are able to boot into CWM, I'm going to assume that you've done your Odin work. I would recommend going through it again, based on qbking77's thread. Check out the videos and learn how to use Odin to gain root and a custom recovery. (always good to take a refresher course).
Now that you have CWM and have rooted through Odin, you will not be able to update using the OTAs from Sprint(again, look through CNexus' thread).
This is not a bad thing, as Freeza always releases an updated Stock Rooted Rom based on the most recent OTA (normally he gets it done before a number of people, myself included, even get the OTA notification).
I'll give directions on how to flash a Rom below. The instructions will be for TWRP, but CWM has similar options/settings
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)
Make a Nandroid backup. I can't emphasize this enough. In flashing, it's almost a certainty that one time, something will mess up. When that happens, you want to be able to restore a backup. In TWRP, just go into Backup Menu and choose where you want it (internal vs. External storage). It takes my phone a few (5-10) minutes to completely backup my data.
In TWRP, click the wipe button, then system. This will completely wipe the Rom from your phone. Doing this will allow you to get a "clean" install, without any settings or leftover files from your old Rom getting in the way. Instead, you could only wipe data (factory reset), which is good enough for most Roms. I'd still recommend a system wipe, though.
Also while in the Wipe menu, wipe Cache and Dalvik Cache.
Go back to the TWRP main menu.
Click Install, then find your Rom zip file (may have to switch from internal to external storage).
Let TWRP do it's thing.
If you're installing a TW-based Rom, chances are it had gapps already installed. If not, you should now flash the correct gapps package from goo.im. Make sure you're flashing the correct one, as if you don't, your google apps will force close upon use.
Reboot into system and give it time to boot (first boot sometimes takes a couple of minutes).
Set up your phone the way you like.
These should be the directions to follow whenever you flash a new Rom. Some Roms have the Aroma installer, so you'll have more options once you choose to flash the Rom zip, but those are typically easy to follow (and vary from Rom to Rom, so I won't be able to give you a good guide on that).
Hope this helps!

Wow! Just had to come out and say, nice writeup!

CNexus said:
Wow! Just had to come out and say, nice writeup!
Click to expand...
Click to collapse
Thanks, CNexus. By-the-way, I'm still working on the addition to your sticky I promised... I haven't forgotten about it.

topherk said:
Thanks, CNexus. By-the-way, I'm still working on the addition to your sticky I promised... I haven't forgotten about it.
Click to expand...
Click to collapse
No problemo, take your time :good:

So its better to use qbkings method instead of [SAMSUNG GALAXY S3 UNIFIED TOOLKIT V7.0]
read this abouy 4.1.2 rooting afterwards, great news...
Originally Posted by Ramer84015
I am on stock recovery and my phone has been updated to v4.1.2 (MB1). Have the files in the OP been updated, or does it matter to get root?
The files will still work exactly the same. Follow the instructions, and you'll be good.
I remember now I used qbking's method had the files in phone TeamEpic-Root-from-Recovery-v5.zip
Thanks for the heads up I got scared after updating but read If you take OTA then you will lose ROOT. This is normal what I don't get is how I was able to get OTA with CWM and not TWRP, but I read somewhere some ppl were able to take the OTA with CWM.
Thanks M8's for coming though in the clutch... now to ROOT my moms Samsung Galaxy Tab2...
Lanboy
=)

Always better to root the right way than using a tool kit, one wrong choice in a tool kit and you have an international brick worth 600 dollars.
Transmitted with a portable device using Xparent Blue Tapatalk 2

Stuck at 4.1.1, Can't update to 4.1.2 or 4.3, please help

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.

What will interfere with OTA updates?

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