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

Root Warning to those running third-party ROMs

trparky

Android Enthusiast
Jun 11, 2011
692
138
Cleveland, Ohio, United States
People have been reporting that they have been getting the OTA update despite the fact that they have been running third-party ROMs (such as this). Installation of the OTA has resulted in a soft-brick. One person who got the OTA update downloaded to their phone with GummyCharged GBE 2.1 and they couldn't do anything but reboot their phone, they could not back out, after which it resulted in a soft-brick.

At this point, it would be best to downgrade to EE4 and do the OTA update as normal. Root and deodex your phone. Or, install the EP4D deodexed and rooted Odin image made by Danalo1979 that can be found at the thread below...
http://rootzwiki.com...o-kernelrooted/

This is a warning, you may end up getting the OTA update and it will result in a soft-brick
 
Will we be able to get root back? I have to admit, I am still running gummy 1.9 because I am happy with it, and not been paying as much attention to the scene since it became apparent CM wasnt coming to the charge.

I dont mind going back to stock and then getting the OTA, but I want to get root back after the fact.
 
Upvote 0
I've been running Humble 5.0(EP4P) for a few weeks. Im happy with it. Id like to just update the Modems to EP4D. I downloaded just the files from Toms World but I noticed that the file name had an "x" at the end of the .zip. I havent seen that before. So I renamed it .zip but it woudnt extract correctly. Any help?

Thanks

Edit: Used 7zip to extract....odin'n now....
 
Upvote 0
I chose to use ZIPX to compress it versus standard ZIP.

The ZIP format has been passed up by several different various compression methods including ZIPX and 7ZIP due to the fact that it compresses better and results in smaller compressed files. That means faster downloads for you, the user.

PowerArchiver and newer versions of WinZIP both support ZIPX. Although, PowerArchiver supports the most amount of compression methods and tops out at 24 different compression/file formats.
 
  • Like
Reactions: Gr8Jeepin
Upvote 0
I refuse to go back to stock. However, I have heard that changing the contents of /system/build.prop file to the proper values will stop the OTA notification from appearing.

Does anyone know what the new values should be? Here is my current one (running an older version of Froyo Gummycharged)...

Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=FROYO
ro.build.display.id=FROYO
ro.build.version.incremental=EE4
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2.1
ro.build.date=2011. 05. 27. (금) 01:28:02 KST
ro.build.date.utc=1306427282
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEI-07
ro.build.tags=release-keys
ro.product.model=SCH-I510
ro.product.brand=verizon
ro.product.name=SCH-I510
ro.product.device=SCH-I510
ro.product.board=SCH-I510
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=s5pc110
# ro.build.product is obsolete; use ro.product.device
ro.build.product=SCH-I510
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SCH-I510-user 2.2.1 FROYO EE4 release-keys
ro.build.fingerprint=verizon/SCH-I510/SCH-I510/SCH-I510:2.2.1/FROYO/EE4:user/release-keys
# Samsung Specific Properties
ro.build.PDA=SCH-I510.EE4
ro.build.hidden_ver=SCH-I510.EE4
ro.build.changelist=1014954
ro.build.buildtag=jenkins-HUDSON_GA_FROYO_STEALTHV_PROD-566
ro.tether.denied=false
# end build properties
#
# system.prop for smdkc110
#

rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
dalvik.vm.heapsize=48m
dalvik.vm.execution-mode=int:jit

# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version=131072

# in compliance to per Verizon requirement
ro.com.android.dataroaming=false
#
# ADDITIONAL_BUILD_PROPERTIES
#
windowsmgr.max_events_per_sec=55
keyinputqueue.use_finger_id=true
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=2.2_r9
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
ro.carrier=VzW
ro.com.google.clientidbase=android-samsung
ro.com.google.clientidbase.yt=android-verizon
ro.com.google.clientidbase.am=android-verizon
ro.com.google.clientidbase.vs=android-verizon
ro.com.google.clientidbase.gmm=android-samsung
ro.com.google.clientidbase.ms=android-verizon
keyguard.no_require_sim=true
ro.config.ringtone=19_Vzw_Droid_1.ogg
ro.config.notification_sound=23_VerizonDroid.ogg
ro.config.alarm_alert=Good_Morning.ogg
ro.opengles.version=131072
ro.csc.sales_code=VZW
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
 
Upvote 0
I don't know why people are so against going back to stock, you won't be there for very long. The rooting and debloating your ROM isn't as hard as people think it is.

My objection isn't to the process; I know I'll have to do it at some point. It's the reinstallation of all the apps, the resetting of speed dials, getting everything back the way I want it. I don't want to have to keep doing that. I'd rather just do it once and be done. I'll deal with the nag screen for a few days while a new ROM gets built.
 
Upvote 0
Titanium Backup for your apps is your friend. It'll save all of your user apps and their associated data as well.

Yep, that means Titanium Backup can also save where you were in Angry Birds.

I already have Titanium Backup. I don't play Angry Birds. And I'm not some bumbling fool that barely knows what end of the phone to plug in. I'm referring to laying out all my shortcuts, rebuilding Tasker widgets, things like that. I don't care that it only takes a couple of minutes. I don't want to spend that couple minutes, and I shouldn't have to do that.

I don't have a phone so I can re-flash it every few days, and beta test ROMs and try out all these different themes. I have it to use it. I flashed it back in July, and if this OTA popup hadn't happened, I'd probably still be running that until the phone itself died.
 
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