now that we have a method of recovery wouldn't it be safe to go ahead, and remove the apps that people have been freezing without issue?
my thought is, if something does go bonkers I can always restore the nand right?
Well, true... but there is a lot of chatter about keeping stock image apps. Without them, you may not be able to receive updates(ones that get the okay to D/L and install), but then again, you can always go back to the stock image to receive the upate.
Related
Please help. I rooted my Bionic and removed some of the bloatware via Titanium Backup. Not being totally stupid, I did a backup of the apps first. When I tried to load the new OTA, I got an error because it was apparently looking for the IM app (Which I never use). Of course, I had removed it as bloatware. When I tried to reinstall it via Titanium Backup, it just hangs.
I wasn't giving up so easily. So I extracted the apk file from the zip file and tried to reinstall it manually. Unfortunately I get "App not installed".
Any ideas?
I don't have my phone with me at the moment (gasp!) but near the bottom of the main preferences list in TB there is an option for failsafe mode. Make sure this is checked and put it on "indirect" app processing mode. Wording may vary slightly from that but if you set those two options it should work.
88Keys88 said:
Please help. I rooted my Bionic and removed some of the bloatware via Titanium Backup. Not being totally stupid, I did a backup of the apps first. When I tried to load the new OTA, I got an error because it was apparently looking for the IM app (Which I never use). Of course, I had removed it as bloatware. When I tried to reinstall it via Titanium Backup, it just hangs.
I wasn't giving up so easily. So I extracted the apk file from the zip file and tried to reinstall it manually. Unfortunately I get "App not installed".
Any ideas?
Click to expand...
Click to collapse
And for future reference, use the freeze option next time instead f removing them.
MillionManMosh said:
I don't have my phone with me at the moment (gasp!) but near the bottom of the main preferences list in TB there is an option for failsafe mode. Make sure this is checked and put it on "indirect" app processing mode. Wording may vary slightly from that but if you set those two options it should work.
Click to expand...
Click to collapse
I hope you and your phone have been joyously reunited
I triedd your suggestions, but alas no go. Any other ideas?
If you already have everything backed up I'd just go ahead and use RSDLite to set the phone back to stock:
http://forum.xda-developers.com/showthread.php?t=1262540
Just keep in mind you lose root through this, so to be safe you might want to reroot and apply the 'forever root' hack before you update. Although I understand newer root exploits like R3l3as3d work on the newer system as well.
And yes, the battery was joyously reunited with the charger...
It's a little more hard core than I've gone before, but I guess it's my only option. I've flashed ROM's before to my OG, but never had to go this route.
Thanks for your help and wish me luck!
And to johnlgalt - What can I say but I always learn from my mistakes. Monday morning is always the best time to be a quarterback ;-)
The OG DROID had an unlocked everything, so it was easy to do all of this. Because of eFuse and our locked bootloaders, it's most definitely more complicated. Our phones cannot even replace the recovery yet all we can do is use a bootstrap method to bypass the stock recovery and run an alternate recovery - and until we get a disabled eFuse and unlocked bootloader, this ain't gonna change.
My device and detailed list of what happened: I started with i537 4.4.2 ne3 rooted with towelroot. i proceeded to follow the thread about upgrading to 5.0.1 lp oc6 and keep root. Followed everything precisely, sucessfully upgraded, but when i proceeded to restore from Titanium, I didnt realize until it was too late that i backed up user AND system apps and data. after that i got neverending "process.gapps..." has stopped working and so on. I realize now i should have only restored my user apps and data. Anyways, i managed to freeze play services so that i can flashfire LP again, btw i used the deodexed version. As i was doing that and clicked flash, i had forgotten to set the screen timeout to 10 min. or more. Now, all that happens is the samsung custom screen with padlock boots up, but just goes black from there and nothing else. I can boot into download mode. Unfortunately I dont have a laptop with me at the moment, i am using ps4 to post, but i wanted to make sure what my next plan of action should be. From what i have gathered im assuming i need to recover via odin. Do I need to recover back to ne3, towelroot, and then start the process again, or can i just recover to oc6 ? Am I forgetting something crucial? with my lack of attention, probably. Thank you in advance and if I have offended anyone with my stupidity compelling someone to respond with a condescending and negative remarks, i am sorry.
gardensofgrief said:
My device and detailed list of what happened: I started with i537 4.4.2 ne3 rooted with towelroot. i proceeded to follow the thread about upgrading to 5.0.1 lp oc6 and keep root. Followed everything precisely, sucessfully upgraded, but when i proceeded to restore from Titanium, I didnt realize until it was too late that i backed up user AND system apps and data. after that i got neverending "process.gapps..." has stopped working and so on. I realize now i should have only restored my user apps and data. Anyways, i managed to freeze play services so that i can flashfire LP again, btw i used the deodexed version. As i was doing that and clicked flash, i had forgotten to set the screen timeout to 10 min. or more. Now, all that happens is the samsung custom screen with padlock boots up, but just goes black from there and nothing else. I can boot into download mode. Unfortunately I dont have a laptop with me at the moment, i am using ps4 to post, but i wanted to make sure what my next plan of action should be. From what i have gathered im assuming i need to recover via odin. Do I need to recover back to ne3, towelroot, and then start the process again, or can i just recover to oc6 ? Am I forgetting something crucial? with my lack of attention, probably. Thank you in advance and if I have offended anyone with my stupidity compelling someone to respond with a condescending and negative remarks, i am sorry.
Click to expand...
Click to collapse
You're good. Once you flash back to NE3 with Odin it'll be like you're starting from scratch. So just make sure you follow the directions and definitely don't restore system apps. Typically when I'm updating between different versions of Android I'll let my apps install from the Play Store and then restore any missing data from TiBu, this way I can ensure I'm starting fresh.
Good luck.
Devo7v said:
You're good. Once you flash back to NE3 with Odin it'll be like you're starting from scratch. So just make sure you follow the directions and definitely don't restore system apps. Typically when I'm updating between different versions of Android I'll let my apps install from the Play Store and then restore any missing data from TiBu, this way I can ensure I'm starting fresh.
Good luck.
Click to expand...
Click to collapse
I figured that was my mistake when i kept getting notifications non-stop. Ive messed around with root since the epic 4g, but this was actually my first time backing up. All other times I preferred starting fresh and having everything wiped. I dont really know why i decided to change that this time, but i did and without really thinking about it i backed up both user and system.
I just got my laptop with me now and ive downloaded odin 3.07, and full package or something 4.4.2 ne3. now I am searching topics to find a guide. its been years since i used odin and I need to make sure im doing this right.
Thanks
This is just great. I was using odin to restore to ne3 and right after it finished the download mode and started to reboot my computer crashes. now I cant do anything. It wont boot into download mode or recovery mode. The only sign of life is if i plug into my laptop it shows the battery icon with a pinwheel that isnt moving. I cant believe this just happened.
*edit* i just left it alone for a few minutes and tried to boot into download mode which was successful.
I have a TMobile Note 4 SM-N910T. It's currently on 5.1.1 stock and I just got the OTA Marshmallow update notification. I'd like to try Marshmallow out, but if I allow the OTA update, will I be able to root it later? Or is 6.0.1 unrootable (for now)? If I root it now (before updating to MM) will I still get the OTA update? And will it still be rooted after the update? So many questions!
ota then root
I OTA'ed, now the phone randomly reboots several times a day, and some apps don't work correctly. Great.
factory reset.
*sigh* I was afraid you were going to say that. Now the problem is backing it up. I have a Titanium Backup Pro license, but I only use it on my old rooted GS2. The Note 4 is not rooted so TB won't run on it. All the rooting tutorials say "back up your phone before you root" but you need root to run TB. Chicken or egg? I guess I could try Samsung Kies, don't know if it will back up everything. My photos are backed up to Google Photos, I guess everything else is replaceable, but I would really rather not have to reinstall all my apps one by one after a factory reset.
That brings up another question: when you to go Settings/Backup and Reset, I have "Backup my data" set to On and linked to my Google account, but nowhere can I find documentation of exactly WHAT gets backed up or to WHERE (it says to "Google servers" but what the heck does that mean? I can't find it on my Google Drive or anywhere else on my Google account dashboard.)
I do greatly appreciate your help, by the way.
You could try reinstalling through kies or smart switch. Make sure to clear caches before and after. And see if that works. If it doesnt help, you could flash recovery, root, try to backup as much as you can between reboots and then factory reset. Your apps should automatically download from play store. But without the titbackup files you'll lose settings and data in a lot of apps that Google doesn't backup.
I unlocked your mum's bootloader.
kydar said:
I have a TMobile Note 4 SM-N910T. It's currently on 5.1.1 stock and I just got the OTA Marshmallow update notification. I'd like to try Marshmallow out, but if I allow the OTA update, will I be able to root it later? Or is 6.0.1 unrootable (for now)? If I root it now (before updating to MM) will I still get the OTA update? And will it still be rooted after the update? So many questions!
Click to expand...
Click to collapse
Were you able to downgrade back to 5.1.1? My phone also download the MM ota but I haven't installed it. I rooted 5.1.1 first and am trying to locate where exactly the MM ota downloaded to.
Been hearing too much about problems with MM.
Shad0wsabr3 said:
Were you able to downgrade back to 5.1.1? My phone also download the MM ota but I haven't installed it. I rooted 5.1.1 first and am trying to locate where exactly the MM ota downloaded to.
Been hearing too much about problems with MM.
Click to expand...
Click to collapse
There aren't that many problems with MM. Just superficial stuff like not having mobile data toggle. The problems you are hearing about a factory reset will fix. Like lag, jankyness, apps loading, phone freezing temporarily. You won't be able to do OTA. It will fail because of root. You need to titanium backup or whatever method you prefer of backing up data and flash through kies, odin or smart switch. Probably easier to go that route unless you only did minor things with root like just block ads, then you can probably get away with flashing stock recovery and then OTA. You still might have to factory reset like I had to even though I flashed whole rom through smart switch. If you have xposed or modified something like swapping recent apps and back key like me, then you'll need to flash marshmallow whole and start over after backing up.
Afaik, you can't downgrade to 5.1.1 unless somebody figured out a workaround or you only flashed everything except bootloader.
I unlocked your mum's bootloader.
@Shad0wsabr3, my phone gave me the choice to delay the upgrade for a while, but eventually just did it without my consent. I suppose you could download stock 5.1.1 from sammobile if you really wanted to downgrade. I just wish I could figure out how to back up my (unrooted) phone so I could then do a factory reset and see if it helps the problems I'm having.
kydar said:
@Shad0wsabr3, my phone gave me the choice to delay the upgrade for a while, but eventually just did it without my consent. I suppose you could download stock 5.1.1 from sammobile if you really wanted to downgrade. I just wish I could figure out how to back up my (unrooted) phone so I could then do a factory reset and see if it helps the problems I'm having.
Click to expand...
Click to collapse
Iv never backed up an unrooted device so I wouldn't know. Glad you nrought that up as Iv been meaning to look into that.
Would you happen to know where the downloaded ota file location is? My phone downloaded it and I keep postponing it.
Sorry, idk exactly where in the file system it is. All I can caution you again is, I kept postponing it and postponing it, and then one day the phone just popped up a message saying it was going to reboot and update, whether I liked it or not. Well, it didn't actually SAY whether I liked it or not but it did decide that I had postponed the update long enough and it was going to apply the update, giving me no option to postpone it any longer. That sort of pissed me off.
Please let me know if you come up with a backup solution. I've tried SimpleADB or whatever it is called these days, and another app that claimed to be able to back up an unrooted phone. Neither of them worked as advertised.
Where are the root instructions for completely stock 910T with MM update?
vernj123 said:
Where are the root instructions for completely stock 910T with MM update?
Click to expand...
Click to collapse
http://forum.xda-developers.com/not...overy-n910t-t3-marshmallow-pe3-guide-t3406870
kydar said:
Sorry, idk exactly where in the file system it is. All I can caution you again is, I kept postponing it and postponing it, and then one day the phone just popped up a message saying it was going to reboot and update, whether I liked it or not. Well, it didn't actually SAY whether I liked it or not but it did decide that I had postponed the update long enough and it was going to apply the update, giving me no option to postpone it any longer. That sort of pissed me off.
Please let me know if you come up with a backup solution. I've tried SimpleADB or whatever it is called these days, and another app that claimed to be able to back up an unrooted phone. Neither of them worked as advertised.
Click to expand...
Click to collapse
I'm still researching what your dealing with. As for me I found the ota file. For those looking for it this is how and where I found it....
With RomToolbox I went to root browser. Then to data folder and a folder named fota. Within the fota folder is the ota update named update.zip. I erased that and then went into Titanium Backup and chose to freeze both software update files. So far no constant reminders that I have an update ready to be installed.
Hope this may help.
My XT1095 is running the stock 6.0 rom and it's rooted. I keep getting the "Install System Update" nag screen all the time. It won't leave me alone. I don't want to update yet because I read it'll cause problems with root and I'll have to unroot or reroot or whatever and I don't want to mess with it right now. I was hoping that it would get bored of me telling it to go away and leave me alone but it hasn't. It shows up every time I unlock my phone if it's been sitting for more than 10 minutes. It shows up when I'm literally in the process of typing a text message, or when I'm surfing a web page, or when I'm in the middle of doing a dozen other things... like it thinks it's so mightily important that it can interrupt anything I'm doing.
It's version: 24.201.3.en.US. Just a security update from what I read elsewhere. It's not a notification so I can't long-press and force stop it or anything. I read that it's supposed to go away on it's own after a week but it's been quite a bit longer than that now. Any ideas on how to get it to stop nagging me? Or an easy way to apply this without screwing up root?
an actual app is in charge of nagging you to update the system software. I cant remember its name but it is located in system/priv-app, "ccc.motorola.ota" or something like that, cant really remember. You can try either deleting it or disabling it.
What i personally did to prevent this is installing fresh stock system image, updating to latest version AND THEN rooting, so updates wont nag me anymore
billybully said:
an actual app is in charge of nagging you to update the system software. I cant remember its name but it is located in system/priv-app, "ccc.motorola.ota" or something like that, cant really remember. You can try either deleting it or disabling it.
What i personally did to prevent this is installing fresh stock system image, updating to latest version AND THEN rooting, so updates wont nag me anymore
Click to expand...
Click to collapse
I did the same, but when I installed a fresh stock image, this new update wasn't available yet. It only came out recently.
DrvLikHell said:
I did the same, but when I installed a fresh stock image, this new update wasn't available yet. It only came out recently.
Click to expand...
Click to collapse
Take a look at this post:
http://forum.xda-developers.com/showpost.php?p=66479956&postcount=15
This should disable the system update nagging.
desertcat said:
Take a look at this post:
http://forum.xda-developers.com/showpost.php?p=66479956&postcount=15
This should disable the system update nagging.
Click to expand...
Click to collapse
I did that, except the app name on my phone was a bit different. So far no more nagging. Thanks a bunch.
So, I'm trying to find a work-around ever since the idiots over at Niantic blocked rooted users. I used Magisk which worked, but that means I had to reset everything and run on stock. I loved the ExtreStoLite ROM and I want my phone to run on that, but the ROM is pre-rooted with SuperSU 2.72. When I try to uninstall it from settings, I seem to get into a bootloop. The article from Android Police said it'll seem like I'm getting a bootloop but my device is actually re-encrypting itself. I don't know if this is true, and I didn't leave my phone alone long enough to figure out if it was.
I've read other threads suggesting that I need to have and flash the stock boot.img, which I don't know how or where to get.