• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Sprint AWE Software Enhancement

No custom recovery here so I guess I have to figure out how to add TWRP.

Say, I just saw a reference to an app called "Flash Gordon," for flashing zips without needing a custom recovery:

[APK] Flash Zip Files, NO NEED FOR CWM OR TW… | Xperia Miro | XDA Forum

Does anyone have experience with this? Would it work for the nag fix zip?

I would like to avoid installing TWRP if I can, simply to save time. I only use a couple of root apps and don't tinker daily. All I ever do with my phone is toggle the wifi hot spot and use the stock web browser. :)
 
Upvote 0
No custom recovery here so I guess I have to figure out how to add TWRP.

Say, I just saw a reference to an app called "Flash Gordon," for flashing zips without needing a custom recovery:

[APK] Flash Zip Files, NO NEED FOR CWM OR TW… | Xperia Miro | XDA Forum

Does anyone have experience with this? Would it work for the nag fix zip?

I would like to avoid installing TWRP if I can, simply to save time. I only use a couple of root apps and don't tinker daily. All I ever do with my phone is toggle the wifi hot spot and use the stock web browser. :)
If u have root download the fix, extract the build.prop and replace yours in system, set perms rw-r-r and reboot :)
 
Upvote 0
And that's it? That's all the editing that's required to stop the nag screen? Change UMS to true and tack on jpeg.quality=100 at the end? Or are those just examples to enable us to identify which build.prop you're referring to?

My guess (only a guess) is that, if indeed the build.prop changes alone will make the nag go away, its some of the build date/version properties that's accomplishing that. I'd be shocked if the jpeg or UMS ones would have any affect.

If someone knows which specific properties will make this go away, I'd love to know as I don't want to change any more than necessary. If I find out later, I'll report back as well.
 
Upvote 0
I backed up my original build.prop, and changed the following props to match the one in the fix.zip:

ro.build.display.date
ro.build.version.incremental
ro.build.date
ro.build.date.utc
ro.build.description
ro.build.fingerprint
ro.build.sw_internal_version

The phone did say that I needed an update on reboot (it appeared to just give a background notification and not a popup). I selected the notification for "..more info" and the update tool said "up to date". I didn't get any more popups or updates after that.

I did a root check and fired up tethering as a quick test and both were fine.

Many thanks to brittnearl.
 
  • Like
Reactions: m4p and hodaddy
Upvote 0
I backed up my original build.prop, and changed the following props to match the one in the fix.zip:

ro.build.display.date
ro.build.version.incremental
ro.build.date
ro.build.date.utc
ro.build.description
ro.build.fingerprint
ro.build.sw_internal_version

The phone did say that I needed an update on reboot (it appeared to just give a background notification and not a popup). I selected the notification for "..more info" and the update tool said "up to date". I didn't get any more popups or updates after that.

I did a root check and fired up tethering as a quick test and both were fine.

Many thanks to brittnearl.
Followed your lead and edited the dates and lines you suggested. Nag screen is gone, I'm "up to date" and all seems well. JDubTrey, thanks for sticking your neck out and taking a chance....and thanks to brittnearl as well.
 
Upvote 0
Followed your lead and edited the dates and lines you suggested. Nag screen is gone, I'm "up to date" and all seems well. JDubTrey, thanks for sticking your neck out and taking a chance....and thanks to brittnearl as well.
Not sure what u mean by chance?? @jdubtrey i know its the dates not what i added... I was just letting u know what i changed above stock... Glad it helped u guys out :)
 
Upvote 0
I downloaded the zip file to my computer, unzipped and dragged the build.prop into notepad and printed it to make it easier on the eyes. Made my changes with root browser, saved and rebooted. Update notification appeared, tapped and it wanted me to download and install. I backed out and did another restart. No more notification. No more nag screen. Root and tether still good. You guys rock! Thanks
 
  • Like
Reactions: Bstressfree
Upvote 0
I had deleted the ota file. Stopped the notifications and was still getting the nagging popup.
This morning I overslept because the nag interfered with my alarm. Got p@@@ed and finally touched "install now". Watched the countdown and then..... Nuthin happened... No reboot... Nuthin! I assume that's because the gota file was deleted.
Haven't seen the nag screen since.
 
Upvote 0
I had deleted the ota file. Stopped the notifications and was still getting the nagging popup.
This morning I overslept because the nag interfered with my alarm. Got p@@@ed and finally touched "install now". Watched the countdown and then..... Nuthin happened... No reboot... Nuthin! I assume that's because the gota file was deleted.
Haven't seen the nag screen since.

Just wait a couple days it will come back i promise you that I've tried to install mine three separate times and it will never go through.if i get again I'm calling virgin mobile and b/+ching
 
  • Like
Reactions: Bstressfree
Upvote 0
Just wait a couple days it will come back i promise you that I've tried to install mine three separate times and it will never go through.if i get again I'm calling virgin mobile and b/+ching
Yes it will come bk unless u either install it or use my build.prop fix... As far as it not installing u must have modified the stock file system in someway eg: removing bloat apps, modifying apps, etc... Root should b ok as the update only checks for stock files not added files
 
Upvote 0
Yes it will come bk unless u either install it or use my build.prop fix... As far as it not installing u must have modified the stock file system in someway eg: removing bloat apps, modifying apps, etc... Root should b ok as the update only checks for stock files not added files

I'll be sure to do an update if it does return. I have removed some bloatware tho. Most recently VM's "my account". Wish I could remember what I unchecked to stop the notifications tho.:thinking:
 
Upvote 0
Yes it will come bk unless u either install it or use my build.prop fix... As far as it not installing u must have modified the stock file system in someway eg: removing bloat apps, modifying apps, etc... Root should b ok as the update only checks for stock files not added files

I have removed some bloatware. I guess ill try editing my build.prop and see what happens.I've never had any problems installing updates on previous phones after debloating them. Thanks for your help
 
Upvote 0
I'll be sure to do an update if it does return. I have removed some bloatware tho. Most recently VM's "my account". Wish I could remember what I unchecked to stop the notifications tho.:thinking:
Since u removed system apps ur only options are my fix or to flash back to stock and take all updates Then remove the bloat apps
 
  • Like
Reactions: Bstressfree
Upvote 0
If u have root download the fix, extract the build.prop and replace yours in system, set perms rw-r-r and reboot :)

I finally made 2 minutes to do this--looks like it worked. The update icon in the status bar returned after reboot but then vanished before my eyes... No nag screen yet. Excellent. Now I have to root my wife's Awe and do the same thing.

Thanks again!
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones