Root [Verizon] Using Goo Mgr?

[dkl1]

Since I'm not really familiar with using Goo Manager I thought it wise to ask!

I have a notification on my device stating "An update for your rom is available". Is it a reliable method of doing an update or should I get it from the ROM site and flash through TWRP? Also, I think I've read where a wipe is not necessary when updating a ROM...? Just asking

Thanks...

 

[Mikestony]

Well, personally, I have never updated a rom...is that a "nightly" thing? If so, I don't know about the "no wipe for an update" thing either
As far as using goo, I only use it for changing /updating recoveries....I've had no issue with using goo for that.

Back to the rom thing, I'd feel better doing an update thru TWRP...

Take those 2 coins to the bank

 

[dkl1]

Well, personally, I have never updated a rom...is that a "nightly" thing? If so, I don't know about the "no wipe for an update" thing either
As far as using goo, I only use it for changing /updating recoveries....I've had no issue with using goo for that.

Back to the rom thing, I'd feel better doing an update thru TWRP...

Take those 2 coins to the bank

Haha, thank you Sir!

I'm not sure how I ended up getting these notices for 'updates' but this is the second or third one I've received. It's not a nightly thing as I don't participate in that...just plain ol' v1.8!

I think last time I got the notice I did go ahead and let goo mgr do it. I tend to agree that doing that thru TWRP is best

Have a great weekend Mike, looks like beautiful early fall weather here in the wonderful Mid west

Sent from my SCH-I535 using Tapatalk 2

 

[nickdalzell]

I've disabled that notification in the settings of goo.im because it was outright annoying and i am not a fan of 'dirty flashing' aka flashing without wiping data--and with over 200+ apps and tons of themes done to my custom ROM i'm not wiping!

 

[Zoandroid]

I've disabled that notification in the settings of goo.im because it was outright annoying and i am not a fan of 'dirty flashing' aka flashing without wiping data--and with over 200+ apps and tons of themes done to my custom ROM i'm not wiping!

Not sure about the themes issue, but Titanium Backup Pro will let you restore all 200 of those apps (after you make a backup of them) WITH all their settings and data just as you had them, within minutes, even after fully wiping and switching ROMs. Or you can use one of its many tools, such as the filter to only go after specific apps, or you can even manually pick through the list to de-select any you don't want restored. It is one of the 2 main reasons I root a device (the other being making nandroid backups).

 

[breadnatty08]

I've never updated through Goo, but I believe it just downloads the ROM and then boots you into recovery you manually do it? At least that was my impression.
And yeah, if you go into settings within Goo and can disable notifications for an update.
I'd always check with the developer if a complete wipe is necessary or just cache/dalvik.

 

[Zoandroid]

I've never updated through Goo, but I believe it just downloads the ROM and then boots you into recovery you manually do it? At least that was my impression.
And yeah, if you go into settings within Goo and can disable notifications for an update.
I'd always check with the developer if a complete wipe is necessary or just cache/dalvik.

After reading the above I checked to see if GooManager offered a newer TWRP than I had on my S3 and there was one. So I did the update. The tool to do that is kind of "hidden", as it uses the context menu rather than having that option on the main screen, and it also uses the confusing wording of saying it is going to flash an "openrecovery script" rather than explaining in more familiar terms that it is flashing TWRP.

Once selected ,there are 2 "are you really sure you want to do this" protection levels, and then it will download and flash the TWRP version it had shown as being currently available. It does this automatically in the background, and does not reboot the S3 into Recovery. Once it is done, if you want to run the TWRP version it just flashed (which replaces any other version you had) you need to manually boot Recovery. GooManager offers a quick one touch button to do so, or you could use Quickboot (free on the Store), or the old holding-the-buttons method.

I had no problem getting the current latest version 2.6.3.0 installed this way in just a couple minutes.

 

[dkl1]

After reading the above I checked to see if GooManager offered a newer TWRP than I had on my S3 and there was one. So I did the update. The tool to do that is kind of "hidden", as it uses the context menu rather than having that option on the main screen, and it also uses the confusing wording of saying it is going to flash an "openrecovery script" rather than explaining in more familiar terms that it is flashing TWRP.

Once selected ,there are 2 "are you really sure you want to do this" protection levels, and then it will download and flash the TWRP version it had shown as being currently available. It does this automatically in the background, and does not reboot the S3 into Recovery. Once it is done, if you want to run the TWRP version it just flashed (which replaces any other version you had) you need to manually boot Recovery. GooManager offers a quick one touch button to do so, or you could use Quickboot (free on the Store), or the old holding-the-buttons method.

I had no problem getting the current latest version 2.6.3.0 installed this way in just a couple minutes.

Yep...same here. The ol' "openrecovery script" thing had me bumfuzzled! Once I did it, I knew it was the proper way.

 

[Zoandroid]

Yep...same here. The ol' "openrecovery script" thing had me bumfuzzled! Once I did it, I knew it was the proper way.

Developers never seem to learn to speak to the layperson. Instead, they like to assume we already know every intimate detail of their creation, before they even release it. That said, if you give Titanium Backup a try (often called by its popular abbreviation "TIBU"), there is a similarly confusing fishhook in there as well. After backing up "apps and data", when you go to restore an app you are afforded the nice choice of not only restoring the app itself, but also restoring all of THE APP'S data (and any custom settings). But, they don't call it that. They will say "restore apps and SYSTEM data".

In most of the computer realm, the term "system" refers to an Operating System. So the initial thought, if one were flashing a completely different ROM (i.e. operating system) to their device, is that you would definitely not want to restore files from the other ROM into the new ROM. Such an action is usually devastating, at least in a PC (like restoring Windows 98 operating system files into Windows 7, for example). This led me to believe I would never want to use that feature, until I got tired of having to keep setting up all my apps again after each restore, and wrote the developer asking for a way to preserve what I will more logically call APP DATA. Turns out that is exactly what their aforementioned feature does! So I now use it a lot. It should read "restore app and app data'" or "restore app WITH data" or anything but what it does say. I see it as the most valuable feature of TIBU, allowing me to restore dozens of apps automatically in minutes, after a ROM flash or sometimes even with a new device, so long as the app is still supported. Between that and making regular nandroid backups, one never need worry about their phone crashing and losing things.