-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [Boost Mobile] ota update SPH-L710_MD7_to_MG2.zip
- Thread starter smith058
- Start date
-
- Tags
- samsung galaxy s3
idiotboy
Newbie
i just got my phone to take the update While haveing root....
Voodoo Rootkeeper works with S3...
i still have root!!!
Would you mind revealing your steps? It doesn't work on mine even with Voodoo... I do a temp unroot and it fails every time.
sure is.... next time use titanium backupEnded up factory resetting and using the odin image for the update.. Such a pain in the ass for such a small updateThanks for your help though!
you can try to use your cwm backup to advance restore your your data
back up first cuz it might not work ...
cwm
backup/restore
advanced restore
data
might work... worth a try... if you make a backup first then it cant hurt to try... except time lost
what did you do? howd it brick it?Will have to get back to ya.. tried to use your build.prop and ended up bricking the phone
idiotboy
Newbie
Yea.. I usually do, but just didn't think about this time.. no worries, everything that is important to me is already backed up on the net
I believe my steps were using root explorer to copy the build.prop from the top of the page over top of my one in system. I don't think it liked that. Might explain why I was having issues updating though. Either way it's back to normal and everything is re-installed.
I've bricked my phone so many times doing stupid stuff that I can everything back to normal in under an hour
squirrel323
Newbie
i don't want to have to go through the hassle of putting my phone back to stock just for a ota date.is there any way i can stop that annoying reminder that keeps poping up?
i know there is a way, but i dont know how... when i was messing with my phone i messed something up and it stopped annoying me, however i dont know exactly what i did... i think it stopped when i already had the ota pushed to my phone but then i download the ota from the op and i probably moved it to my cache directory, i do remember seeing two update files one normal and one with (1) at the end... i don't remember if i just downloaded it twice or if i did move the file, but i do think that is why it stopped harassing me... i could be as easy as renaming the file or maybe just delete the file....is there any way i can stop that annoying reminder that keeps poping up?
bottom line i don't know how, but yes it can be stopped... i do recall seeing another thready probably for a different phone that actually showed step by step how to stop it.
good luck
squirrel323
Newbie
i know there is a way, but i dont know how... when i was messing with my phone i messed something up and it stopped annoying me, however i dont know exactly what i did... i think it stopped when i already had the ota pushed to my phone but then i download the ota from the op and i probably moved it to my cache directory, i do remember seeing two update files one normal and one with (1) at the end... i don't remember if i just downloaded it twice or if i did move the file, but i do think that is why it stopped harassing me... i could be as easy as renaming the file or maybe just delete the file....
bottom line i don't know how, but yes it can be stopped... i do recall seeing another thready probably for a different phone that actually showed step by step how to stop it.
good luck
thanks ill just wait till some one can tell me step by step on how to stop it -_- or the easiest way to push this to my phone
cornelljdavis
Well-Known Member
I ran the ota verifier app and got FAILED: LINE #62
assert(apply_patch_check("system/app/ChromeWithBrowser.apk",
"d97daaa559of7c68de13aac60abf
19ab07dflc",
"bacd4246e24792f08e87c9d3
dfbofa6bb2b7de4'));
that's what it all said. I'm thinking I need to reinstall chrome browser apk and make it a system app and try to flash the update again. I could be wrong. if so does anyone know what this means or what I should do?
assert(apply_patch_check("system/app/ChromeWithBrowser.apk",
"d97daaa559of7c68de13aac60abf
19ab07dflc",
"bacd4246e24792f08e87c9d3
dfbofa6bb2b7de4'));
that's what it all said. I'm thinking I need to reinstall chrome browser apk and make it a system app and try to flash the update again. I could be wrong. if so does anyone know what this means or what I should do?
yep that is probably it. if chrome is not a system app then that is definitely what it is crying about
cornelljdavis
Well-Known Member
Hahaha ftr put it back on the phone under a system app and things should work right? chrome pure installed on this phone out of the box right? I forgot because I was real quick to remove it from the phone when I got the phone Hahaha. chrome interferes with downloads I believe.
cornelljdavis
Well-Known Member
I switched it back to a system app ran the app again and got a second error. now I have 2 involving chrome. I need the out of the box version of chrome and maybe that'll fix it. I did a Google search on what version chrome can with the phone and got nothing
@smith058, I'm trying to help Cornell retrieve the Chrome files he needs that OTA Verifier is telling him do not match either of the SHA1 checksums that the OTA .zip file is checking for.
Can you point me to the stock CWM backup (download link) you spoke about above?
(or does anyone have the stock / original /system/app/ChromeWithBrowser.apk and it's library file, /system/lib/libchromeview.so they can post or send me, please?)
Thanks!
edit 1: hmm, I'm actually thinking Cornell could install the Chrome files he needs from the OTA .zip file on his current setup and then install the OTA since the updater-script from the OTA will now see the files that it expects/allows (i.e., the apply_patch_check will now succeed for those two files). Never really thought about having someone do this before...I'll post back when I have anything further, but would still like to know the info above...thanks! Update: ack--I can't pull those files from the OTA's .zip file--they're not in there
.edit 2: thanks to @smith058 for using and referencing my app
Glad to know it's helping folks a bit--cheers!edit 3: okay, got/found the stock CWM backup from here: http://androidforums.com/boost-mobile-galaxy-s3-all-things-root/742012-back-stock-4-1-2-a.html
edit 2: thanks to @smith058 for using and referencing my app
edit 3: okay, got/found the stock CWM backup from here: http://androidforums.com/boost-mobile-galaxy-s3-all-things-root/742012-back-stock-4-1-2-a.html
Thanks for making the app, it does help
If crome is still needed, I might be trying a new ROM tonight/tomorrow . I could flash stock and extract a copy, if still needed ?
Thanks for making the app, it does help
If crime is still needed, I might be trying a new ROM tonight/tomorrow . Icould flash stock aand extract a copy,if still needed ?
You are most welcome! I'm glad to have helped some folks
.I've already extracted and sent the files Cornell needed (I verified that the SHA1 sums matched what OTA Verifier was looking for), but I very much appreciate the offer
:thumbup:.Cheers and again, thanks!
cornelljdavis
Well-Known Member
I found this post just now today! hahaha my apologies other commenting in the other guys post and talking to you. anyways this won't brick my phone will? I believe there is a guy that posted on this thread that his phone got bricked.
cornelljdavis
Well-Known Member
its saying build prop already exist.... do I over write it or leave it alone?
Yes, changing things in your build.prop could put your phone in a bootloop... Makew backup first... The build.prop you downloaded is stock and should not do any harm to your phone....
Yes you are replacing your modified build.prop with the original stock. So you can over write it, or follow the details listed which does not consist of renaming.
Good luck, let me know if you need more help
Yes you are replacing your modified build.prop with the original stock. So you can over write it, or follow the details listed which does not consist of renaming.
Good luck, let me know if you need more help