Related
I have my rooted transformer and am trying to update but stow a quarter way throught the install and gives me an android Guy with a triangle with a "!" Sign in it... stock everything just rooted please help
Sent from my GT-I9000 using XDA Premium App
Fixed!!!!! I used Brks Asus transformer rootkit script to root which installs an insecure bootimage to work and this is what caused the problem, I just plugged my trandormer in and restored my original files then the update went on fine first try!!!! Thanks for the help!!!!
Did you install Clemsyn/Blades OC kernel? More than likely this is causing your problem.......
I'm getting the same error. Running 3.2 stock but rooted, no modified kernel. Only thing I modified was the Netflix patch which doesn't seem like it's needed now. Is there a flash able zip for this new update?
You can't update the normal way after rooting.
Sent from my Transformer TF101 using XDA Premium App
magicdave26 said:
You can't update the normal way after rooting.
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
Actually, thats not true. I was running on stock 8.6.5.6 rooted, and was able to update sucessfully. I verified the update in the settings. I have also verified with root checker that i am no longer rooted, as i was before the update. I bought my transformer only a few weeks ago. It came with 3.1 and i updated to 3.2 before rooting. Wonder if that or the rooting method has something to do with why i was able to update while rooted.
I rooted using the method in this thread:
http://forum.xda-developers.com/showthread.php?t=1125714
oilerseberle14 said:
I have my rooted transformer and am trying to update but stow a quarter way throught the install and gives me an android Guy with a triangle with a "!" Sign in it... stock everything just rooted please help
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Same happened to me. As I understand it just rooting doesn't prevent future OTA updates, hence why I was prompted to download this latest, but why it now after failing it tells me there is no longer an update available is beyond me. I can only think ASUS has pulled it for some reason.
---
Sent from my Asus Transformer using Tapatalk
Taomyn said:
Same happened to me. As I understand it just rooting doesn't prevent future OTA updates, hence why I was prompted to download this latest, but why it now after failing it tells me there is no longer an update available is beyond me. I can only think ASUS has pulled it for some reason.
Click to expand...
Click to collapse
You only get it offered the once. Your device is then marked as updated at Asus end. If it didn't work because you were rooted, then tough...
cavsoldier19d said:
Actually, thats not true. I was running on stock 8.6.5.6 rooted, and was able to update sucessfully. I verified the update in the settings. I have also verified with root checker that i am no longer rooted, as i was before the update. I bought my transformer only a few weeks ago. It came with 3.1 and i updated to 3.2 before rooting. Wonder if that or the rooting method has something to do with why i was able to update while rooted.
Click to expand...
Click to collapse
Hmm interesting.
Which method did you use to root it?
Maybe we can pin point why the updates are failing for some people after rooting. I would like to root mine if it was 100% that the OTA updates would still work, even if I had to root it again after each one.
magicdave26 said:
Hmm interesting.
Which method did you use to root it?
Maybe we can pin point why the updates are failing for some people after rooting. I would like to root mine if it was 100% that the OTA updates would still work, even if I had to root it again after each one.
Click to expand...
Click to collapse
I'm having problems with OTA updates and have used Brk's ASUS Transformer HC3.2 RootKit Script to root my device.
I probably did something very stupid...in which I factory reset the device, but noticed that "superuser" is still installed in the apps list. I'm wondering now if i have to re root the device to uninstall superuser and then do another factory reset and then see if the OTA update works? suggestions appreciated
I always look at the updater script in the package before I update. This script contains a bunch of asserts that check the integrity of certain files before it will apply the update. If you can get the update package just open " \META-INF\com\google\android\updater-script" with notepad and that will show everything that's happening when the update occurs including the file asserts it makes. If you've modified these files then it will not update. 8.6.5.6 initially didn't work for me but by checking the script I found the problem was my srs_processing.cfg file because I tried to fix my speaker balance and this was a file that the script asserted. After restoring the original file I was able to update with stock recovery even though I had modified other system files. As long as the specific files the update checks are ok the update will proceed.
aSIMULAtor said:
I'm having problems with OTA updates and have used Brk's ASUS Transformer HC3.2 RootKit Script to root my device.
I probably did something very stupid...in which I factory reset the device, but noticed that "superuser" is still installed in the apps list. I'm wondering now if i have to re root the device to uninstall superuser and then do another factory reset and then see if the OTA update works? suggestions appreciated
Click to expand...
Click to collapse
You need to UnRoot it, I don't think factory reset makes any difference to rooting
http://forum.xda-developers.com/showthread.php?t=1198303
magicdave26 said:
Hmm interesting.
Which method did you use to root it?
Maybe we can pin point why the updates are failing for some people after rooting. I would like to root mine if it was 100% that the OTA updates would still work, even if I had to root it again after each one.
Click to expand...
Click to collapse
The above post about altering certain files appears it might have something to do with it. I rooted using this method... http://forum.xda-developers.com/showthread.php?t=1198303
But it was V2 when i used it. It is now currently V4.
You can re-download the update if you clear your DMClient cache.
Follow the instructions in this thread.
http://forum.xda-developers.com/archive/index.php/t-1106054.html
I had the error with the Android + exclamation mark so I unrooted (reflashed both the stock ROM AND the stock recovery - to get rid of clockworkmod) then cleared the DMClient cache and was I able to update OTA.
As far as I am aware the OTA will not install if you have clockwork Mod flashed for recovery. But if you have rooted without flashing over stock recovery ie clockwork mod not installed the OTA should work but you will lose root by updating.
DT39 said:
As far as I am aware the OTA will not install if you have clockwork Mod flashed for recovery. But if you have rooted without flashing over stock recovery ie clockwork mod not installed the OTA should work but you will lose root by updating.
Click to expand...
Click to collapse
Good point. I did not have clockwork mod recovery installed. Had stock recovery, stock ROM rooted.
Sent from my Inspire 4G using XDA App
I used brk's rootkit script and just restored the original bootimage and it installed perfect let me know if it worked for you guys as well
Sent from my Transformer TF101 using XDA Premium App
I tried flashing back original boot and recovery image, update still failed, and now it fota won't come back. Cleared DMClient cache and hard reset. Guess I'm out of luck until someone releases a flashable version of the update?
Hizpanick said:
I tried flashing back original boot and recovery image, update still failed, and now it fota won't come back. Cleared DMClient cache and hard reset. Guess I'm out of luck until someone releases a flashable version of the update?
Click to expand...
Click to collapse
Same thing happened to me. Tried all the above, and can't get the update to come back.
Have any of you changed original system files whilst rooted? That's why it was failing for me. I managed to get the update again but it failed. I got it once more after it rebooted but took a copy first, unrooting made no difference. Unlike the downloadable firmwares from the ftp site which I checked out, the update script checks the integrity of a ton of files mainly the system apps that cannot be changed without root. If any have changed the script aborts.
Unfortunately even though I had backed up all of them with Titanium Backup, it wouldn't restore them and TB just hung. I tried all its options but nothing helped - a little worrying.
In the end I copied off the TB backup directory to a USB stick and used the NVflash recovery to restore back to factory. I then performed the upgrade again to both the tablet and dock without issues. Four hours later I have it almost back to where I want it.
Hope this helps some of you, even though it's not the best process, but the update imho is worth it
---
Sent from my Asus Transformer using Tapatalk
I really don't understand this phone. I've been on a quest of 2 weeks to be rooted and on official status, finally i gave up everything because i was not able to have both. Finally i flashed factory rom through odin, formated a couple of time the phone, and i got back official status. I much rather gave up a few rooting benefits then OTAs, at least until they fix the phone's problems.
Well, this morning, i wake up, and that DAMN custom status is back....WHY????????? I'm not rooted, i'm 100% stock, i checked with rootchecker and my phone doesnt have root....then why does that damn status keep coming back??? There is obviously something else that triggers it......man i'm so deperate! Please help!
polish_pat said:
I really don't understand this phone. I've been on a quest of 2 weeks to be rooted and on official status, finally i gave up everything because i was not able to have both. Finally i flashed factory rom through odin, formated a couple of time the phone, and i got back official status. I much rather gave up a few rooting benefits then OTAs, at least until they fix the phone's problems.
Well, this morning, i wake up, and that DAMN custom status is back....WHY????????? I'm not rooted, i'm 100% stock, i checked with rootchecker and my phone doesnt have root....then why does that damn status keep coming back??? There is obviously something else that triggers it......man i'm so deperate! Please help!
Click to expand...
Click to collapse
It's really not as big of a deal as you are making it. The way I see it you have 2 choices.
1. Exchange the phone for another (that might do the same thing)
2. Ignore it.
Just like every other Galaxy phone out there (you remember the skyrockets, right?) not all of them react the same way. Some get custom, some do not. Others switch back and forth.
I've noticed you have made many posts about this same thing. If someone hasn't provided a concrete answer that has worked for you by now it just doesn't exist yet. No matter how frustrated you are over it, making new posts about it are not going to change anything.
Its up to you if you keep wanting to post about it (I'm not complaining about it), I just don't think it's going to get you any more information at this point than what already has been said. Maybe I am wrong and someone will tell you exactly what to do to make it "official", but I haven't seen anything yet.
Good luck and try not to let it get to you so much.
euhhh no, they are not about the same thing, one was about retaining officiel while rooted, and now that i've given up on that, i still have a custom status, the reson why i dont report there is becuase poeple have seen the thread and will not go back, so in order to attract new poster i create a new thread. And no, i dont want to ignore anything because i want OTAs. If you have a problem with that, dont answer
You need to re-root (motochopper method) and then using a file browser such as "root explorer" go to:
/System/Xbin
Once you have navigated to the above path, delete these two files:
"su" and " busybox"
Once you've deleted the two files, uninstall SuperSU and reboot your phone twice.
You'll notice that after the second reboot the "custom" will revert back to "official"
Sent from my SGH-I337M using Tapatalk 2
peoples_flip said:
You need to re-root (motochopper method) and then using a file browser such as "root explorer" go to:
/System/Xbin
Once you have navigated to the above path, delete these two files:
"su" and " busybox"
Once you've deleted the two files, uninstall SuperSU and reboot your phone twice.
You'll notice that after the second reboot the "custom" will revert back to "official"
Sent from my SGH-I337M using Tapatalk 2
Click to expand...
Click to collapse
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
I went through what you have, I completed a full stock restore via Odin and these two files I mentioned were still there. Use a file explorer and go to the path I suggested and you'll see them there
Sent from my SGH-I337M using Tapatalk 2
polish_pat said:
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
Click to expand...
Click to collapse
I don't believe the current Odin contains a pit...or whatever it is that formats the phone...
So all Odin is going to do is reinstall everything...so replace missing or corrupted files - it will not delete your new files
Formating from the phone itself won't delete everything...its just going to delete your apps, app data, and cache
Therefore doing multiple factory resets and odins likely will not remove all traces of root...someone correct me if I'm wrong but that's what I believe is the case...
Sent from my HTC PH39100 using Tapatalk 2
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
XGhozt said:
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
AT&T software update push or download will not work for your phone if it is showing custom. People like to be getting these stock updates as soon as they are published by the provider, not when some good heart packages a new ROM using them.
polish_pat said:
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
Click to expand...
Click to collapse
Good info here, I did this procedure as you described, and yes, official is showing, but you can NOT delete su, it will unroot. I just renamed the 2 files, and root was gone. renamed su back, re-installed su superuser, and reboot, root is back with official status.
Thanks.
TheAxman said:
Good info here, I did this procedure as you described, and yes, official is showing, but you can NOT delete su, it will unroot. I just renamed the 2 files, and root was gone. renamed su back, re-installed su superuser, and reboot, root is back with official status.
Click to expand...
Click to collapse
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
CAG-man said:
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
Click to expand...
Click to collapse
Same here
CAG-man said:
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
Click to expand...
Click to collapse
Correct. the one from the playstore updates the binaries. then uninstall.
---------- Post added at 07:11 PM ---------- Previous post was at 07:10 PM ----------
XGhozt said:
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Good answer, why does it matter if it says custom? whats the big deal here. If you are wanting the update, why not just wait until a dev does what they need to do to it, and flash it later. I updated 1 time in a year on my GS3, and never did it again. When a new rom is developed, it usually is a base from the update...so....
Had a posting. Could not delete
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Did some digging in the forums and I am rooted with OFFICIAL.
This is how to do it. Taken from this thread.
http://forum.xda-developers.com/showthread.php?t=2252248&page=42
Mr. Q said:
Well, you do not have to install the ZIP, but instead, do the following:
- Install SuperSU from the market
- Grant SuperSU root access
- When asked to update su-binary, please do
- Remove SuperUser from your device
- Reboot (I read two reboots are needed to make the icon disappear again.)
Click to expand...
Click to collapse
My process completely.
Remove Busybox from system/xbin (or your busybox backup)
Install SuperSU by Chainfire from playstore.
Open SuperSU and Grant SU root
Update the binary
Say yes to try to remove other root apps. This will remove superuser.
reboot
reboot
On second reboot you will notice the Galaxy S4 logo returns and Official Status has returned.
If it has not returned then some other issue is causing the custom status.
CAG-man said:
Did some digging in the forums and I am rooted with OFFICIAL.
This is how to do it. Taken from this thread.
http://forum.xda-developers.com/showthread.php?t=2252248&page=42
My process completely.
Remove Busybox from system/xbin (or your busybox backup)
Install SuperSU by Chainfire from playstore.
Open SuperSU and Grant SU root
Update the binary
Say yes to try to remove other root apps. This will remove superuser.
reboot
reboot
On second reboot you will notice the Galaxy S4 logo returns and Official Status has returned.
If it has not returned then some other issue is causing the custom status.
Click to expand...
Click to collapse
I was able to get official and root, the problem is it comes back after 2-3 days, please report back on sturday and tell me if its still official, also this logo you are talking about, i never see it because im in canada and my bootloader is unlocked already
EDIT: Ok, so once i was rooted and installed SuperSU and got superuser out, i deleted busybox, i then rebooted ONCE and got official just like that. I also took out SD card because i know this screwed me up last time. I'm happy because i'm rooted and official, but i'm not convinced this will last very long because it has never lasted more than 2 days. I will report back in a few days. Thanks Cagman, you've been very helpful and what you told me to do did the best results for me, i just hope they last
so far so good!!!:fingers-crossed:
polish_pat said:
so far so good!!!:fingers-crossed:
Click to expand...
Click to collapse
Try rebooting a few more times.
For about a week i was getting the custom status every 2nd or 3rd reboot, and then eventually it just went away...
joeybear23 said:
Try rebooting a few more times.
For about a week i was getting the custom status every 2nd or 3rd reboot, and then eventually it just went away...
Click to expand...
Click to collapse
Hahaha, i did it!! earlier this afternoon i sort of challenged my phone by rebooting it constantly, ive rebboted probbaly 20-30 times and its still official, i guess deleting busybox sealed the deal!!
Polish_pat I am glad I was able to help. You are welcome. Congratulations.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
I apologize in advance if this has been answered or if I have inadvertently offended. I did watch the video and have developed OSes for 30 years. I also have searched all over this site and the web for resolution and am making no progress, so I'm asking the 'oracle'
Got an ATT S4 (I337) a week ago - it was running UCUAMDL. I rooted it using Motochopper and was happily using Titanium Pro etc. I get notified of OTA update. OTA update downloads (357MB) yet fails during install at 30% consistsently.
I figure it is unhappy with my root - I unrooted and cannot remember which way I did it - I seem to recall SuperSU I was using did not have the built-in 'unroot' support so I grabbed the stock image and used ODIN to flash it.I also may have manually uninstalled the 'normal' way the SU app - I suspect this may be my real problem.
After flashing stock ROM for UCUAMDL phone was no longer rooted, did not say custom etc, and took the OTA upgrade just fine. This was for UCUAMF3 which did add App 2 SD support - BTW this update used another 1G of storage compared to UCUAMDL, and I could not recover the 1G by moving apps either, making it virtually worthless as far as adding support for apps in SD, lol.
The problem is now I cannot seem to get the device rooted again. Motochopper fails when installing su.apk. I suspect I have screwed the pooch - what do I need to do to get this thing rooted again?
Is it typical for an OTA update to fail 'because' the device is rooted?
Any advice is much appreciated.
You can't root mf3. You never should have taken the update if you want to be rooted. Cross your fingers that someone finds a way to root the update but I'm not sure you should hold your breath.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
So is doing a stockrom restore back to MDL an option? Then just root that with Motochopper? And disable OTA updates till its figured out?
The real joke here is that to get their built in app-to-sd functionality they give you an update that hogs up another 1GB!
Nope. Can't go back. Just gotta wait it out. Cheers
Just curious if you don't mind - WHY can't you go back? (Ready for the explanation based on perms and su etc, lol) Or flash stock ROM and factory reset etc?
TheKog said:
Just curious if you don't mind - WHY can't you go back? (Ready for the explanation based on perms and su etc, lol) Or flash stock ROM and factory reset etc?
Click to expand...
Click to collapse
A qfuse is blown when you take the update. It won't let you odin or anything else to go back to an earlier firmware.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Verizon Droid Maxx XT1080
-Camara application
-Google Drive 50GB Promotion
-Mophie Juice pack compatibility
- Wireless charging has been improved to support faster connections
- 4G LTE performance has been improved to support faster connection
- Motorola Assist has been improved for better stability
- Google Voice now returns cards with audible feedback when location setting is enabled
- The lastest version of NFL Mobile has been added
- Viewdini has been removed as a preloaded application
^^Thank you for reminding me supreme!
Make sure you have a TWRP backup before installing!
This update can cause issues on rooted phones!
Download Link:
Blur_Version.12.7.7.obake-maxx_verizon
Presumably you can drop the .zip into your /cache folder (where it was located on mine) and update
I wonder if the ultra will also receive this
Sent from Ahjee's Ultra which is likely better than your phone
Make sure you have a backup in TWRP before running this as it does not take kindly to root. I had a "Shutdown" loop after installing on rooted device.
Could you please extract and post the Google Drive Apk?
Sent from my Nexus 5 using Tapatalk
Kickbut101 said:
Verizon Droid Maxx xt1080
Camera update
Google Drive 50GB Promotion
Mophie Juice pack compatibility
Just to note: As far as I know I am not part of any pre-release test groups/soak tests.
Click to expand...
Click to collapse
I installed the update while rooted and now my phone is power cycling and I can't get it to stop. My fault for not unrooting, I know, but if anyone has insight on how to fix this, it'd be appreciated.
Well I unrooted by fxz save data then installed the pwnmymoto apk took the update and got root back all is normal but I can't access touchless control it wont allow me to check the box. google search works but not touchless control. Can we fxz back with this update or will it brick our phone.
Ok I unistalled and then updated the app but now I get to the training screen but it doesn't activate it's like it can't hear me.
bigv5150 said:
Well I unrooted by fxz save data then installed the pwnmymoto apk took the update and got root back all is normal but I can't access touchless control it wont allow me to check the box. google search works but not touchless control. Can we fxz back with this update or will it brick our phone.
Ok I unistalled and then updated the app but now I get to the training screen but it doesn't activate it's like it can't hear me.
Click to expand...
Click to collapse
You have to update it from the play store. I had that problem before the update. Could you tell me the exact process you used to root the update? I'm about to try and upgrade, but can't survive without root lol
Sent from my XT1080 using XDA Premium 4 mobile app
needshelp101 said:
You have to update it from the play store. I had that problem before the update. Could you tell me the exact process you used to root the update? I'm about to try and upgrade, but can't survive without root lol
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did an fxz save data with house of moto which restores to stock but keeps data. Then I re-installed pwnmymoto but did not run it. rebooted to recovery and installed the update from my sdcard. everything went fine but no touchless controls I installed the update and still it would not let me past the training screen. So I said **** it and installed the stock recovery did a factory reset and now I am good I will just juse the new root method.
If you use my method above when you reboot after the update pwnmymoto will automatically run and install root it cycles 3 times so don't worry you are not in a bootloop with it shutting on and off.
The adb root method? By jcase? I'm a little hesitant to use that one. Since I have no prior adb experience
Sent from my XT1080 using XDA Premium 4 mobile app
needshelp101 said:
The adb root method? By jcase? I'm a little hesitant to use that one. Since I have no prior adb experience
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
PwnMyMoto was an apk you download http://forum.xda-developers.com/showthread.php?t=2444954
Super super easy to do.
Glad to hear someone was able to use this as a new ota root method. But I haven't heard of many others doing this. It's still a little early to hear all the news.
starose
Kickbut101 said:
Verizon Droid Maxx XT1080
Camera update
Google Drive 50GB Promotion
Mophie Juice pack compatibility
Make sure you have a TWRP backup before installing!
This update can cause issues on rooted phones!
Moved the downloaded file to /cache. Fastbooted the stock recovery and temp un-rooted. Every time I try and update though, it tells me that my device is up to date.
Thoughts?
Click to expand...
Click to collapse
Can anyone confirm if SafeStrap is working with the updated build? After the new root exploit, that is.
offeldn
killboredom said:
Kickbut101 said:
Verizon Droid Maxx XT1080
Camera update
Google Drive 50GB Promotion
Mophie Juice pack compatibility
Make sure you have a TWRP backup before installing!
This update can cause issues on rooted phones!
Moved the downloaded file to /cache. Fastbooted the stock recovery and temp un-rooted. Every time I try and update though, it tells me that my device is up to date.
Thoughts?
Click to expand...
Click to collapse
Booted to recovery and applied update from SD. failed with "set_perm: some changes failed" Rebooting and it says "Android is upgrading." We'll see I guess.
---------- Post added at 01:08 AM ---------- Previous post was at 12:49 AM ----------
killboredom said:
killboredom said:
Booted to recovery and applied update from SD. failed with "set_perm: some changes failed" Rebooting and it says "Android is upgrading." We'll see I guess.
Click to expand...
Click to collapse
Brilliant! Booted to system version 12.15.15. So...followed these directions to maintain root:
http://forum.xda-developers.com/showthread.php?t=2466191
To apply the "OTA" I booted to stock recovery and updated from SD. This failed, but booted to 12.15.15.
Then in the above directions, used fastboot to install the new baseband from the modem drivers from another thread in this forum.
profit!!!!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Just to help anyone out I am part of the soak test. If you try to update by hiding root and then flashing stock recover you will get error from trying to install from stock recovery or if you where able to do an ota it will fail. It will show afterwards that you are on the version but you are lacking some things. Anyways The way That I got everything to work without a single error including the baseband coming from the ota .
used fastboot to flash recovery back to stock recover . Flashed stock system to system in fastboot. After that then I installed that I backed up after download from verizon through stock recovery from sd card. after I came back online. I used adb and the RockMyMoto Root and walla everything good to go.
Hope this info helps some !!
I've downloaded it and placed it in cache but my phone still says it's up to date? Any thoughts?
Sorry, what do you mean under
Make sure you have a TWRP backup before installing!
Click to expand...
Click to collapse
?
Is there a boot-loader unlock option for XT1080Mto flash TWRP? Where is TWRP for XT1080M?
I installed it in reocovery. It did say that it was aborted and that some files did not update however after rebooting it says Android is upgrading Optimizing apps xxx of 131.
Did it update or not?
bluh5d said:
Just to help anyone out I am part of the soak test. If you try to update by hiding root and then flashing stock recover you will get error from trying to install from stock recovery or if you where able to do an ota it will fail. It will show afterwards that you are on the version but you are lacking some things. Anyways The way That I got everything to work without a single error including the baseband coming from the ota .
used fastboot to flash recovery back to stock recover . Flashed stock system to system in fastboot. After that then I installed that I backed up after download from verizon through stock recovery from sd card. after I came back online. I used adb and the RockMyMoto Root and walla everything good to go.
Hope this info helps some !!
Click to expand...
Click to collapse
Interesting... How do you determine the you are missing stuff? How did you flash the stock system?
Things seem to be running fine through my method, but the update did fail and I certainly haven't tried everything.
Sent from my XT1080 using Tapatalk
Cincybearcatfan said:
I installed it in reocovery. It did say that it was aborted and that some files did not update however after rebooting it says Android is upgrading Optimizing apps xxx of 131.
Did it update or not?
Click to expand...
Click to collapse
It appears at least some things were updated. When I rebooted, I got the "moto camera" update from the market and when I check build number it is the 15.15.15 update so it looks like that went through. I'm just curious as to what "failed" and what made it through.
For those that failed halfway through, you most likely don't have the new baseband (95). You'll be unable to take future updates until you get everything squared away.
Sent from my XT1080MDEV.
Today I had to restart my phone because it dropped data connection, the moment I restarted it said my phone was being updated and I should wait, it wasted my time and it shoved 10o update down my throat.
If I had recovery installed, this could have been disastrous, no?
Not only for recovery related problems, but this may also prevent people from being able to install certain things, or even one day in the future with a different update just block root?
How do we uninstall then disable OTA updates on an unrooted phone? When I disabled and cancelled notifications for Software Update app, I thought it was fixed, but it probably made it worse, it just installed without any notification or prompt.
I was planning to root and install twrp this weekend, now with all the horror stories I've been reading, I don't want to do it. :crying:
How is AT&T even allowed to push it without explicit permit to install on device.
hydeah said:
Today I had to restart my phone because it dropped data connection, the moment I restarted it said my phone was being updated and I should wait, it wasted my time and it shoved 10o update down my throat.
If I had recovery installed, this could have been disastrous, no?
Not only for recovery related problems, but this may also prevent people from being able to install certain things, or even one day in the future with a different update just block root?
How do we uninstall then disable OTA updates on an unrooted phone? When I disabled and cancelled notifications for Software Update app, I thought it was fixed, but it probably made it worse, it just installed without any notification or prompt.
I was planning to root and install twrp this weekend, now with all the horror stories I've been reading, I don't want to do it. :crying:
How is AT&T even allowed to push it without explicit permit to install on device.
Click to expand...
Click to collapse
Pull down the notification bar and tap and hold on the notification. App info will pop up and tap it and scroll all the way to the bottom and uncheck show notification.
Sent from my LG-LS980 using Tapatalk
oldpreowner said:
Pull down the notification bar and tap and hold on the notification. App info will pop up and tap it and scroll all the way to the bottom and uncheck show notification.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
I did that when I first got the notification. Notification disappeared. 2 days later I restarted my phone for the first time in over a week, and bam, it installed without any notification at all. So disabling notification won't stop it from installing, it seems..
I know this doesn't directly help your situation since you're not rooted but this should help someone who is.
I had to freeze "Software Update 2.3.0.5" using titanium backup for it to stop. Not sure of a way to do it without root or without the pro version of titanium.
hydeah said:
I did that when I first got the notification. Notification disappeared. 2 days later I restarted my phone for the first time in over a week, and bam, it installed without any notification at all. So disabling notification won't stop it from installing, it seems..
Click to expand...
Click to collapse
If you have the ota, you could use root explorer or browser to go into the Cache folder and delete it(ota) then try to install it will fail or do nothing then hit cancel
How can I downgrade?
I don't mind paying for titanium to freeze the app. This is nonsense, enjoyment just update by itself, lucky I didn't install recovery.
Sent from my LG-D800
nybmx said:
I know this doesn't directly help your situation since you're not rooted but this should help someone who is.
I had to freeze "Software Update 2.3.0.5" using titanium backup for it to stop. Not sure of a way to do it without root or without the pro version of titanium.
Click to expand...
Click to collapse
What version of the G2 do you have? I'm on Sprint and I don't have "Software Update", I have "Update Device 4.5.1.10" which I just froze.
Does anyone know if I install the update can I still flash TWRP to my device? I'm not sure if I should install TWRP now and use the flashable ota zip or install it after I update it.
nybmx said:
I know this doesn't directly help your situation since you're not rooted but this should help someone who is.
I had to freeze "Software Update 2.3.0.5" using titanium backup for it to stop. Not sure of a way to do it without root or without the pro version of titanium.
Click to expand...
Click to collapse
I don't have tibu pro.. I went in to system/app and deleted LGDMSClient.apk.
Sent from my LG-D800
I'm asking the same question OP is asking, is there a way to disable the update on non-rooted phones? And from experience with several other Android phones... I know it's pretty much impossible to downgrade unless you start flashing, but I'm gonna ask anyways. Is there a way to downgrade the upgrade that was forced down OP's throat and my own throat? For me it actually updated in my sleep, I woke up and it said my phone was updated. OP and I are on AT&T's D800 variant.
btm fdr said:
I don't have tibu pro.. I went in to system/app and deleted LGDMSClient.apk.
Sent from my LG-D800
Click to expand...
Click to collapse
On Verizon it is called MobileUpdateClient.apk. I changed the file extension to .old and then moved it to a new folder called old so I would know what I had changed.
Sent from my VS980 4G using xda app-developers app
zzandrewst said:
On Verizon it is called MobileUpdateClient.apk. I changed the file extension to .old and then moved it to a new folder called old so I would know what I had changed.
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Does anyone know the name of the file for T-Mobile? I can't find any of the names listed in this thread.
Thanks
What do I disable on Sprint?
Sent from my LG-LS980 using xda app-developers app
zzandrewst said:
On Verizon it is called MobileUpdateClient.apk. I changed the file extension to .old and then moved it to a new folder called old so I would know what I had changed.
Sent from my VS980 4G using xda app-developers app
Click to expand...
Click to collapse
Looks like this worked for me also of my Verizon phone. It seems to have also remove the manual check option in the About phone section in settings.
nybmx said:
I know this doesn't directly help your situation since you're not rooted but this should help someone who is.
I had to freeze "Software Update 2.3.0.5" using titanium backup for it to stop. Not sure of a way to do it without root or without the pro version of titanium.
Click to expand...
Click to collapse
Well, it would still help to avoid further OTA's from being applied if we are rooted and do not use custom rom, there is always a risk of getting OTA and messing everything up, therefore if freezing above app worked for you, it should be all we need. Is Software Update the actual app which checks for version and receives pushes from AT&T when a new OTA is available, or if there are other apps/modules that does this. The problem is, if it is incorporated into android system like some of the other stuff AT&T incorporated, it would be impossible to completely eliminate it without running a custom rom.
RubbleTea said:
If you have the ota, you could use root explorer or browser to go into the Cache folder and delete it(ota) then try to install it will fail or do nothing then hit cancel
Click to expand...
Click to collapse
Awesome the above instructions worked great! Thank you very much brother
disable ota on at&t
Did you totally remove the apk, or rename it? Also, if removed, will it cause other problems?
I only ask cause i had a g2 that was pushed an ota and bricked my g2. Had to get a new one, now trying ti disable the ota's from doing that again..
Then when kitkat is released, am i not able to update it, then root again?
btm fdr said:
I don't have tibu pro.. I went in to system/app and deleted LGDMSClient.apk.
Sent from my LG-D800
Click to expand...
Click to collapse
Att
I have Lg G2 (Att) & hours b4 I have reflash'd back 2 stock and applied root about an hour later i got OTA so I click'd 2 recieve OTA it came back sayin Cant download OTA on rooted device if that helps and thatt was almost 24\hrs ago n still runnin smoothly but file was only like 16MB
So will a bigger OTA push current root'd stock rom out n brick my fone¿
this seems to work for G Flex users.. worth a shot on G2
http://forum.xda-developers.com/showpost.php?p=50454408&postcount=3
hydeah said:
How can I downgrade?
I don't mind paying for titanium to freeze the app. This is nonsense, enjoyment just update by itself, lucky I didn't install recovery.
Sent from my LG-D800
Click to expand...
Click to collapse
you have to flash the old version by using LG Flash Tool, like I did.
So, I have a question for you guys. I got my phone yesterday and I'm on 10o. I installed the CWM recovery for 10o via Flashify, and now I'm concerned about OTAs - I disabled it via the Hidden Menu, but if there's an OTA to update the phone to 4.3 or 4.4, I'd like to receive it and not worry about bricking my phone.
I don't plan on doing a lot of custom ROM flashing, I really just wanted to root and install Xposed. Do I need to flash a stock ROM and go back to stock recovery, so I don't have to worry about OTAs? Or should I be good with CWM and the stock ROM that I rooted?