Related
I have an 8.9 that I rooted, installed safestrap and have modified a setup in a ROM slot.
All my google apps including GMAIL, Playstore etc. work perfectly and I have not lost root from an update like a lot of posters here.
I did all the mods (renaming files etc.) to prevent updates on both the stock ROM and the one in the ROM slot.
I also put the stock ROM in airplane mode.
I have only had the thing a few weeks so I must have gotten it right before the latest update and I absolutely love the thing.
I see all the different build numbers listed here, but I can't figure out how to display the build like I can on my android phone. What is the trick to that??
jmorton10 said:
I have an 8.9 that I rooted, installed safestrap and have modified a setup in a ROM slot.
All my google apps including GMAIL, Playstore etc. work perfectly and I have not lost root from an update like a lot of posters here.
I did all the mods (renaming files etc.) to prevent updates on both the stock ROM and the one in the ROM slot.
I also put the stock ROM in airplane mode.
I have only had the thing a few weeks so I must have gotten it right before the latest update and I absolutely love the thing.
I see all the different build numbers listed here, but I can't figure out how to display the build like I can on my android phone. What is the trick to that??
Click to expand...
Click to collapse
Settings/device/system updates
Tomen8r said:
Settings/device/system updates
Click to expand...
Click to collapse
Thanbkyou.
Mine says 14.3.1.0 and says "system is up to date"
Does it appear I don't have to worry about updates??
jmorton10 said:
Thanbkyou.
Mine says 14.3.1.0 and says "system is up to date"
Does it appear I don't have to worry about updates??
Click to expand...
Click to collapse
just be careful they are sending out the updates randomly
Hi all... so, this is new to me... see the attached screenshot. Never seen that before on any phone. Yes, I'm rooted, but still stock, including recovery... only "hack" I've done is to change platform.xml to make the SD card writable... maybe that's enough... anyone else see this when checking for updates? Especially interested if you're rooted too.
Rooted devices don't receive OTA'S. That's normal
Sent from my SM-G900T using XDA Premium 4 mobile app
fzammetti said:
Hi all... so, this is new to me... see the attached screenshot. Never seen that before on any phone. Yes, I'm rooted, but still stock, including recovery... only "hack" I've done is to change platform.xml to make the SD card writable... maybe that's enough... anyone else see this when checking for updates? Especially interested if you're rooted too.
Click to expand...
Click to collapse
This also happens if you switch from Dalvik to ART as the runtime. I get this same message and I am not rooted yet. I am just playing with ART.
This wasn't the case with my S4... it was rooted and I could still take OTAs... would have to re-root afterwards but it would apply no problem... is this new for the S5? Also, I did switch to ART but then switched back... is that enough to cause the message?
fzammetti said:
This wasn't the case with my S4... it was rooted and I could still take OTAs... would have to re-root afterwards but it would apply no problem... is this new for the S5? Also, I did switch to ART but then switched back... is that enough to cause the message?
Click to expand...
Click to collapse
When on ART the device status is Custom and you will get this message I just switched it back to Dalvik and now my device status is Official and software updates works. I have not updates available. Remember I am NOT Rooted (yet)
philow said:
When on ART the device status is Custom and you will get this message I just switched it back to Dalvik and now my device status is Official and software updates works. I have not updates available. Remember I am NOT Rooted (yet)
Click to expand...
Click to collapse
Ok thanks... it appears to me that once the warranty flag is tripped you're done as far as OTAs go (at least *checking* for OTAs- they may still install from recovery, I don't know)... some tests I did:
Tried on my daughter's phone, which was rooted, with platform.xml changed but never used ART: update check failed, so switching to ART and then back appears to not matter
Tried reverting platform.xml change on my phone, leaving root: update check failed
Tried unrooting my phone as well: update check failed
Tried clearing cache from recovery (didn't expect it to work but easy and worth a try): update check failed
Tried removing busybox: update check failed
So, my conclusion is it's probably reading the warranty flag... looking in Triangle Away it says counter is 0 but system is modified, so the only other thing that *might* work is flashing the system partition only, which I'd be willing to try but I frankly forgot how to do that If anyone can remind me how to flash just a single partition, pulling the .img file out of a .tar.md5 file I'd give it a shot. I'd like to know for sure either way.
Further info: I flashed just the system partition as a last resort... figured that should revert anything I may have done regardless... well, the update check still fails even after that. So yeah, pretty strong evidence that once you trip the warranty flag you aren't getting OTAs automatically anymore... that's a change from my past S3 and S4 experience and I'm not sure if that's an S5 thing or a T-Mobile thing (same version of Android as on my Sprint S4 before I switch to T-Mobile so I don't think it's that).
I'll be interested to see if whenever the next OTA lands it can be installed from recovery manually... if it can then no big deal. If not then it's a bad situation.
I got a message saying I had an update so I press message it rebooted my phone. Since I had edited build.prop. So I restored old build and checked for update it had none but let's me keep checking. Anyone get an update today.
Sent from my ASUS PadFone X using XDA Premium App
I just saw the notification and headed here. Haven't installed yet.
-Epix- said:
I got a message saying I had an update so I press message it rebooted my phone. Since I had edited build.prop. So I restored old build and checked for update it had none but let's me keep checking. Anyone get an update today.
Sent from my ASUS PadFone X using XDA Premium App
Click to expand...
Click to collapse
Got the message, haven't done it yet. Nothing on AT&T's page for it. Anyone figure out what it's for yet?
Hey Guys,
I am aware that an update has begun rolling out. Not a whole lot of information has been released as of yet. I am still waiting for the changelog to come across my desk. I have been told it fixes some "major" issues. I will keep you posted if I hear anything new.
Breaks root. TR brings it back no problem.
Feels a little snappier. Could just be psychosomatic. Everything I use on the regular works fine. Pandora, facebook, tinder, etc.
I get an error. /system/build.prop has unexpected error. Error in cache/Asus a91_108.16_nor (status 7)
Anyone have a stock build prop they can share
Sent from my ASUS PadFone X using XDA Free mobile app
I got the update today and tried to applied it (still using the stock ATT ROM but rooted) and it failed. A reboot got me back to the normal operation but can't update it for 24 hours. Since then (maybe before) the dock keyboard won't communicate with the phone.
The update didn't do much else than make everything run a little bit smoother. Even the connection to the dock is only slightly more fluid. All in all, I think it was just a minor bug fix, nothing seems to have changed.
-Epix- said:
I get an error. /system/build.prop has unexpected error. Error in cache/Asus a91_108.16_nor (status 7)
Anyone have a stock build prop they can share
Sent from my ASUS PadFone X using XDA Free mobile app
Click to expand...
Click to collapse
Similar issue here, except its asusAAB.OBEX has unexpected contents. Running stock that was rooted through TR, but I had previously uprooted, also deleted SU and daemonSU.
Did a factory reset and still got the same error.
Bah horrible I can't find a build.prop anywhere
Sent from my ASUS PadFone X using XDA Free mobile app
Sounds like most of us are getting errors when trying to update. What options do we have? This kinda sucks.
I've got stock unrooted nandroids in another thread. Don't know if it'll work or not. I've successfully flashed those nandroids w/o a factory reset, too
Looks like I'll be giving that a shot tonight! I'll report back if it works.
Where is the update stored on the device and can I pick apart the stock build prop to possibly fix my issue
Chorazin said:
Similar issue here, except its asusAAB.OBEX has unexpected contents. Running stock that was rooted through TR, but I had previously uprooted, also deleted SU and daemonSU.
Did a factory reset and still got the same error.
Click to expand...
Click to collapse
Hello, I have the exact problem with the asusAAB.ODEX* having unexpected contents and causing an error during the update. The update just failed for the 3rd time. Have you or anyone had any luck figuring this out? Any help would be greatly appreciated.
Thanks,
Chesley
Sadly, I haven't. I read the instructions for trying to restore a stock nandroid, but man, that stuff is just too damn confusing. And I'm a pretty technical guy! Software just isn't my thing, I guess.
I can't even imagine the rooting caused that error, I don't think root would touch that file at all!
Chorazin said:
Sadly, I haven't. I read the instructions for trying to restore a stock nandroid, but man, that stuff is just too damn confusing. And I'm a pretty technical guy! Software just isn't my thing, I guess.
I can't even imagine the rooting caused that error, I don't think root would touch that file at all!
Click to expand...
Click to collapse
Yeah the nandroid stuff is a bit technical although its not too bad, I have done it on previous android phones but never this one. The only reason I am trying to avoid that option is because I don't want to have to re-install everything and add all my accounts back and whatnot. It will be the last thing I try.
I'm not sure about rooting causing the error as others stated that the update removes root. I also have my phone rooted. I unrooted it to see if it would work but it still has the same asusAAB.odex error after the phone downloads the update then reboots.
I am suspicious of Lucky Patcher causing the problem... Have you used that app?
[edit] Hey also if you need help with the TWRP install, I can help with that. I have links to the TWRP and the stock recovery for our phones, and have successfully flashed both recovery's to test them out. I have my own edited working adb commands since the ones from here (http://forum.xda-developers.com/showthread.php?t=2790542) did not work for me because the links no longer work.
[edit 2] Hey also I found an apk in the root folder, here is the path: /system/app/AsusAABService.apk . I installed that apk and it said it updated the app but I have to wait 21 hours and 35 minutes before I can try the update again to see if it solved the issue.
chesley96 said:
Yeah the nandroid stuff is a bit technical although its not too bad, I have done it on previous android phones but never this one. The only reason I am trying to avoid that option is because I don't want to have to re-install everything and add all my accounts back and whatnot. It will be the last thing I try.
I'm not sure about rooting causing the error as others stated that the update removes root. I also have my phone rooted. I unrooted it to see if it would work but it still has the same asusAAB.odex error after the phone downloads the update then reboots.
I am suspicious of Lucky Patcher causing the problem... Have you used that app?
[edit] Hey also if you need help with the TWRK install, I can help with that. I have links to the TWRP and the stock recovery for our phones, and have successfully flashed both recovery's to test them out. I have my own edited working adb commands since the ones from here (http://forum.xda-developers.com/showthread.php?t=2790542) did not work for me because the links no longer work.
[edit 2] Hey also I found an apk in the root folder, here is the path: /system/app/AsusAABService.apk . I installed that apk and it said it updated the app but I have to wait 21 hours and 35 minutes before I can try the update again to see if it solved the issue.
Click to expand...
Click to collapse
I found the apk as well, and a reinstall didn't help me at all. I'm considering actually backing up and then deleting the odex and seeing what happens.
Chorazin said:
I found the apk as well, and a reinstall didn't help me at all. I'm considering actually backing up and then deleting the odex and seeing what happens.
Click to expand...
Click to collapse
Oh damn. I havnt found the odex yet though. If you can point me in the direction to the odex, I will check it out and try some stuff on it.
I had the same error.. Did everything including a factory reset.. No joy.. I've had enough.. I called AT&T and they are swapping this for a S5.
As for shipping update delays.. Just change the date ahead a day and uncheck auto date.. Somehow it registers the date from the phine
I got this 13 inch tablet for displaying music PDF files.
It's got KitKat 4.4, and there's apparently no intention to update this from the manufacturer.
I'd like to run igigbook, but that app requires 5.0+. So I figure I can root this, then do the cm12 ...?
I've looked on compatible devices lists and can't find this device.
Anybody got a link or maybe just some advice?
Thx
jazaddict said:
I got this 13 inch tablet for displaying music PDF files.
It's got KitKat 4.4, and there's apparently no intention to update this from the manufacturer.
I'd like to run igigbook, but that app requires 5.0+. So I figure I can root this, then do the cm12 ...?
I've looked on compatible devices lists and can't find this device.
Anybody got a link or maybe just some advice?
Thx
Click to expand...
Click to collapse
I own one of these.
I found Kingo Root successfully roots it.
Unfortunately, no CM has been built for it.... yet. I plan to fix this.
Fair warning, though: do NOT remove anything child-mode-related yet, unless you have a backup of the system partition. It's basically an AOSP ROM, but they've tweakedwith the SYSTEMUI enough that straight-up removing it causes crach loops.
It's got an RK3188 chip, for the curious. Opened it to verify.
AmEv said:
I own one of these.
I found Kingo Root successfully roots it.
Unfortunately, no CM has been built for it.... yet. I plan to fix this.
Fair warning, though: do NOT remove anything child-mode-related yet, unless you have a backup of the system partition. It's basically an AOSP ROM, but they've tweakedwith the SYSTEMUI enough that straight-up removing it causes crach loops.
It's got an RK3188 chip, for the curious. Opened it to verify.
Click to expand...
Click to collapse
Great.
Ive learned the hard way! lol
Bit too late for me now, but i had a similar tab from smart telecom and i cant find any firmware for it, i rooted with kingroot and after removing all the child mode and disney crap, im having the same thing.
Ive started a thread, but im hoping i can find a patched firmware without all the bloatware and a newer android build if possible.
HI - Just came across this thread, pity I hadn't seen it earlier - I had/have rooted with King Root, which worked fine. Then set about deleting all the child-mode-related apps. Now I'm stuck with receiving "Unfortunately, the process com.android.systemui has stopped" nothing seems to fix it. Do you know where I might find the original ROM that I can restore, can't find anything on the manfactures website..
Any help, really appreciated.
Thanks
Wayne
waynez2016 said:
HI - Just came across this thread, pity I hadn't seen it earlier - I had/have rooted with King Root, which worked fine. Then set about deleting all the child-mode-related apps. Now I'm stuck with receiving "Unfortunately, the process com.android.systemui has stopped" nothing seems to fix it. Do you know where I might find the original ROM that I can restore, can't find anything on the manfactures website..
Any help, really appreciated.
Thanks
Wayne
Click to expand...
Click to collapse
Hi Wayne,
I contacted the supplier who was going to contact the manufacturer, still have not found anything.
Someone else started a thread some time back and did the same thing as us.
I think someone was going to create a ROM for me, i will direct them to this thread.
Thanks for the update.
I had some success last night in resolving my issues with "com.android.systemui" - I managed to get into play store and reinstalled "Net Nanny for Android" as soon as the install had completed the error message went away and hasn't returned. The other "Kids" apps that I had deleted have not reinstalled, appears Net Nanny must have removed/broken something when I deleted it.
Would be still good to get a copy of the original rom for next time, better still to get an upgrade from 4.4.4 to something a little newer at least.
Anyway hoe that help to get you going again.
Wayne
I am ordering one of these now. Let me know if there's anything I can do to try to help in terms of getting a copy of the ROM. (I haven't done android development before, but I am a software engineer so I am willing to give anything a shot)
claylong said:
I am ordering one of these now. Let me know if there's anything I can do to try to help in terms of getting a copy of the ROM. (I haven't done android development before, but I am a software engineer so I am willing to give anything a shot)
Click to expand...
Click to collapse
Let me know how you get on, as I am still after a ROM image if i can find one.
Going to start researching all the possible ways to get a ROM image (in addition to just asking the manufacturer). I will first do a search, and then maybe post in the forums somewhere, but I am starting here:
http://www.theandroidhow.com/2014/06/how-to-dump-backup-any-android-rom.html
Did some research, and actually found that the androidhow article I linked in my last post was the most relevant. I followed the romdump script process and believe I have the rom image files.
The question becomes, are the image files most usable in their current form, or as flashable images?
Has there been any developments in this, or anything close to a ROM or even an update?
Roach419 said:
Has there been any developments in this, or anything close to a ROM or even an update?
Click to expand...
Click to collapse
Not that im aware of, i just did what someone else suggested here and reinstalled netnanny off the app store.
At least its working again, but not terrific.
Oh, well I didn't have that problem. The guy I bought this streamachine off of already had it rooted and everything, i was just wondering if anything had been developed...4.4.4 is quite a bit outdated, and limited.
Clay,
Can you upload that ROM image that you made? I bought another ST13 and while I can get it into recovery mode, it still won't boot even after a factory data reset. My plan is to try recovering from the sdcard before I assume that what I have is a collection of spare parts.
My two others aren't rooted, and since we need them tonight, I don't dare mess with them right now.
Thanks,
Paul
can I get a copy?
I rooted my ST13 and now I'm having bluetooth problems. I'd like to restore back to the stock ROM. Can I have a copy of yours? Does it work?
THANKS!
claylong said:
Did some research, and actually found that the androidhow article I linked in my last post was the most relevant. I followed the romdump script process and believe I have the rom image files.
The question becomes, are the image files most usable in their current form, or as flashable images?
Click to expand...
Click to collapse
I am also interested in this thread, anyone know about the bootloader?
???
So still no DISK IMAGE or ROM? I successfully rooted St1316 but can't connect to wifi. I left natnanny alone, but it now doesn't connect to ANY wifi networks. Tries then switches to either "saved" or "disabled". I can push some apps to the device via bluetooth file transfer app but don't know what's missing. Could this be a permission issue? I'm lost and stressed. Tried factory wipe. No luck. Open to suggestions. Help guys. This thing kinda sucked before I lost wifi. Now it's just a glorified digital photo frame that plays sound WAY too softly.
The May 2018 updates are on Google's site, except for the 6P. Anyone know why?
This article says it's been pulled:
https://www.droid-life.com/2018/05/...ity-update-goes-live-for-nexus-pixel-devices/
The links are still active. I got them from here:
https://9to5google.com/2018/05/07/android-may-18-security-patch-pixel-nexus/
I downloaded the image yesterday but going to delete it.
The update was actually pushed to my device today by Google... but it won't install due to an E3005 error related to the modem. I'm not sure, though, if the issue is with this update or if it's something specific to my device.
SpookyTunes said:
The May 2018 updates are on Google's site, except for the 6P. Anyone know why?
This article says it's been pulled:
https://www.droid-life.com/2018/05/...ity-update-goes-live-for-nexus-pixel-devices/
The links are still active. I got them from here:
https://9to5google.com/2018/05/07/android-may-18-security-patch-pixel-nexus/
Click to expand...
Click to collapse
Thanks for the heads up. Have you flashed it?
new update was sucessfully installed on my nexus via official ota update
tropical cactus said:
Thanks for the heads up. Have you flashed it?
Click to expand...
Click to collapse
Not yet without knowing what the issue with it is. I may get brave on the weekend though
SpookyTunes said:
Not yet without knowing what the issue with it is. I may get brave on the weekend though
Click to expand...
Click to collapse
OPM2. Sounds a bit scary to me. I thought angler was only either 3 or 5. I haven't flashed it either.:laugh:
It appears to have a new radio 3.87 , maybe there are some problems with that
tropical cactus said:
OPM2. Sounds a bit scary to me. I thought angler was only either 3 or 5. I haven't flashed it either.:laugh:
Click to expand...
Click to collapse
What do these even mean?
If I have OPM3 can I flash OPM5? Vice versa?
Ofrine said:
What do these even mean?
If I have OPM3 can I flash OPM5? Vice versa?
Click to expand...
Click to collapse
Normally you should always use the same build if available. I'm on OPM3. OPM5 is a build specifically for Japanese carrier SoftBank. Attempting to flash OPM5 over OPM3 is a bad idea.
I believe OPM2 is a merge of OPM3 and OPM5. Perhaps if you had OPM5 it isn't liking the merged radio file but for me on OPM3 I was able to upgrade to the May OPM2 Nexus 6P build without issue.
I did a non-destructive factory image flash to get to OPM2. YMMV.
rhardy613 said:
Normally you should always use the same build if available. I'm on OPM3. OPM5 is a build specifically for Japanese carrier SoftBank. Attempting to flash OPM5 over OPM3 is a bad idea.
I believe OPM2 is a merge of OPM3 and OPM5. Perhaps if you had OPM5 it isn't liking the merged radio file but for me on OPM3 I was able to upgrade to the May OPM2 Nexus 6P build without issue.
I did a non-destructive factory image flash to get to OPM2. YMMV.
Click to expand...
Click to collapse
So you installed the may update?,how is it so far.
side-loaded the may ota file via adb and it seems to work a-ok so far... i had installed opm5 before as well via this method so perhaps there is some under the hood issue nobody has noticed yet...
Not Yet Available
If you go to the Android News blogspot it states that the Nexus 6P update is "Not Yet Available" ...
I'd post the link, but it says new members are not allowed for 10 days or something like that, sorry!
Installed may update using flashfire.seems fine to me so far.seems little faster,but could be cause of clean install,rooted and debloated also.when Google releases new update I will probably install that too.just curious why it was pulled,a bug,or was there something we got that we weren't supposed too??
I cant say for sure what the issue was but I know after I did the update phone worked fine but then I restarted the phone and it told me my Android System was corrupted and that I had to factory reset.
VersusMe_ said:
I cant say for sure what the issue was but I know after I did the update phone worked fine but then I restarted the phone and it told me my Android System was corrupted and that I had to factory reset.
Click to expand...
Click to collapse
So far still running good for me,no message when I reboot either.
I just realized that the power save mode is not functioning on my 6P and was before may OTA ( cannot be toggled and does not turn on below 15%) not a game-changer but could be why it was pulled or it could just be a hiccup on an aging device
Ugh, where the update?
I was holding of flashing till the release of the next security patch.
[email protected] said:
Ugh, where the update?
I was holding of flashing till the release of the next security patch.
Click to expand...
Click to collapse
My phone says it has the OTA, but as I did some system modifications, I need the factory image, which yet has to appear.
Have any of you installed from the first link? If so, how did that go? I wan to do the OTA, but I am a bit worried it will be corrupt or that it isn't the correct file.