1. Download our Official Android App: Forums for Android!

Root Warning to those running third-party ROMs

Discussion in 'Android Devices' started by trparky, Nov 30, 2011.

  1. trparky

    trparky Android Enthusiast
    Thread Starter
    Rank:
    None
    Points:
    113
    Posts:
    692
    Joined:
    Jun 11, 2011

    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
     

    Advertisement

    mrterry, Gr8Jeepin and kraisydave like this.
  2. kraisydave

    kraisydave Well-Known Member
    Rank:
    None
    Points:
    43
    Posts:
    109
    Joined:
    Dec 12, 2010

    Dec 12, 2010
    109
    34
    43
    KDTech.org - Tech helper
    Montana
  3. mrterry

    mrterry Well-Known Member
    Rank:
    None
    Points:
    16
    Posts:
    97
    Joined:
    Mar 15, 2011

    Mar 15, 2011
    97
    9
    16
    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.
     
  4. trparky

    trparky Android Enthusiast
    Thread Starter
    Rank:
    None
    Points:
    113
    Posts:
    692
    Joined:
    Jun 11, 2011

  5. Gr8Jeepin

    Gr8Jeepin Member
    Rank:
    None
    Points:
    16
    Posts:
    47
    Joined:
    Aug 6, 2011

    Aug 6, 2011
    47
    4
    16
    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....
     
  6. trparky

    trparky Android Enthusiast
    Thread Starter
    Rank:
    None
    Points:
    113
    Posts:
    692
    Joined:
    Jun 11, 2011

    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.
     
    Gr8Jeepin likes this.
  7. Gr8Jeepin

    Gr8Jeepin Member
    Rank:
    None
    Points:
    16
    Posts:
    47
    Joined:
    Aug 6, 2011

    Aug 6, 2011
    47
    4
    16
    Thanks....I just brain farted on that before I posted. Im CWM the EE4 to EP4D modems as I post this. (rebooting) I think I may wait to update the ROM until Danalo1979 comes out with Humble 5._. Or just update with your link in OP.
     
  8. rellim113

    rellim113 Newbie
    Rank:
    None
    Points:
    15
    Posts:
    20
    Joined:
    Jan 29, 2010

    Jan 29, 2010
    20
    0
    15
    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 (Text):
    1. # begin build properties
    2. # autogenerated by buildinfo.sh
    3. ro.build.id=FROYO
    4. ro.build.display.id=FROYO
    5. ro.build.version.incremental=EE4
    6. ro.build.version.sdk=8
    7. ro.build.version.codename=REL
    8. ro.build.version.release=2.2.1
    9. ro.build.date=2011. 05. 27. (금) 01:28:02 KST
    10. ro.build.date.utc=1306427282
    11. ro.build.type=user
    12. ro.build.user=se.infra
    13. ro.build.host=SEI-07
    14. ro.build.tags=release-keys
    15. ro.product.model=SCH-I510
    16. ro.product.brand=verizon
    17. ro.product.name=SCH-I510
    18. ro.product.device=SCH-I510
    19. ro.product.board=SCH-I510
    20. ro.product.cpu.abi=armeabi-v7a
    21. ro.product.cpu.abi2=armeabi
    22. ro.product.manufacturer=Samsung
    23. ro.product.locale.language=en
    24. ro.product.locale.region=US
    25. ro.wifi.channels=
    26. ro.board.platform=s5pc110
    27. # ro.build.product is obsolete; use ro.product.device
    28. ro.build.product=SCH-I510
    29. # Do not try to parse ro.build.description or .fingerprint
    30. ro.build.description=SCH-I510-user 2.2.1 FROYO EE4 release-keys
    31. ro.build.fingerprint=verizon/SCH-I510/SCH-I510/SCH-I510:2.2.1/FROYO/EE4:user/release-keys
    32. # Samsung Specific Properties
    33. ro.build.PDA=SCH-I510.EE4
    34. ro.build.hidden_ver=SCH-I510.EE4
    35. ro.build.changelist=1014954
    36. ro.build.buildtag=jenkins-HUDSON_GA_FROYO_STEALTHV_PROD-566
    37. ro.tether.denied=false
    38. # end build properties
    39. #
    40. # system.prop for smdkc110
    41. #
    42.  
    43. rild.libpath=/system/lib/libsec-ril.so
    44. rild.libargs=-d /dev/ttyS0
    45. ro.sf.lcd_density=240
    46. dalvik.vm.heapsize=48m
    47. dalvik.vm.execution-mode=int:jit
    48.  
    49. # The OpenGL ES API level that is natively supported by this device.
    50. # This is a 16.16 fixed point number
    51. ro.opengles.version=131072
    52.  
    53. # in compliance to per Verizon requirement
    54. ro.com.android.dataroaming=false
    55. #
    56. # ADDITIONAL_BUILD_PROPERTIES
    57. #
    58. windowsmgr.max_events_per_sec=55
    59. keyinputqueue.use_finger_id=true
    60. ro.setupwizard.mode=OPTIONAL
    61. ro.com.google.gmsversion=2.2_r9
    62. media.stagefright.enable-player=true
    63. media.stagefright.enable-meta=true
    64. media.stagefright.enable-scan=true
    65. media.stagefright.enable-http=true
    66. ro.carrier=VzW
    67. ro.com.google.clientidbase=android-samsung
    68. ro.com.google.clientidbase.yt=android-verizon
    69. ro.com.google.clientidbase.am=android-verizon
    70. ro.com.google.clientidbase.vs=android-verizon
    71. ro.com.google.clientidbase.gmm=android-samsung
    72. ro.com.google.clientidbase.ms=android-verizon
    73. keyguard.no_require_sim=true
    74. ro.config.ringtone=19_Vzw_Droid_1.ogg
    75. ro.config.notification_sound=23_VerizonDroid.ogg
    76. ro.config.alarm_alert=Good_Morning.ogg
    77. ro.opengles.version=131072
    78. ro.csc.sales_code=VZW
    79. net.bt.name=Android
    80. dalvik.vm.stack-trace-file=/data/anr/traces.txt
     
  9. trparky

    trparky Android Enthusiast
    Thread Starter
    Rank:
    None
    Points:
    113
    Posts:
    692
    Joined:
    Jun 11, 2011

    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.
     
  10. rellim113

    rellim113 Newbie
    Rank:
    None
    Points:
    15
    Posts:
    20
    Joined:
    Jan 29, 2010

    Jan 29, 2010
    20
    0
    15
    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.
     
  11. trparky

    trparky Android Enthusiast
    Thread Starter
    Rank:
    None
    Points:
    113
    Posts:
    692
    Joined:
    Jun 11, 2011

    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.
     
  12. rellim113

    rellim113 Newbie
    Rank:
    None
    Points:
    15
    Posts:
    20
    Joined:
    Jan 29, 2010

    Jan 29, 2010
    20
    0
    15
    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.
     
  13. trparky

    trparky Android Enthusiast
    Thread Starter
    Rank:
    None
    Points:
    113
    Posts:
    692
    Joined:
    Jun 11, 2011

    I was using Angry Birds as an example of just the kind of data that Titanium Backup can backup and restore. Not many people know this.

    No need to jump down my throat.
     

Share This Page

Loading...