Related
I've rooted my GT 10.1 but I have two questions that I can't find the answer.
1. Has anyone discovered how to unroot back to stock?
2. If rooted, will I be able to get the OTA of touchwiz by checking for updates under settings?
PS I flashed the TouchWiz UX found in this forum. Got to say it is really nice and I can't wait to get the version from Sammy. I then restored a backup using Rom Manager and restored fine except when checking for software updates. It used to say no update available, but today it says failed to connect to servers. Anyone else getting this error?
I guess that is actually 3 questions.
Thanks
1. Unrooting is pretty simple. Just flash the 3.1 OTA in the dev forum, after doing a full wipe. If you feel the need to go back to full stock, you'll also want to nvflash back to the original retail recovery, which you undoubtedly saved when you first rooted.
2. No one knows yet, but rest assured, within a day (less probably) of the update being released, it'll be available here as a rooted flashable ROM. If you learn one thing from your time on XDA, it should be "never accept an OTA update." Let the devs pull it apart and repackage it in a nice root-safe download.
Undoubtedly! (I wish) I wasn't planning to root but while playing with Odin, I thought I was locked at the downloading screen while testing odin. (Didn't hold down the power button long enough to shut off tab) I thought my only solution was to continue and root. No problems rooting, it was easy. I just wanted to make sure I get the TouchWiz update. Now I learned my lesson I will never do an OTA update.
Glad you told me that, otherwise I probably would have screwed up my GT. I don't know how I missed the post about backing up the stock image first. I try to read a lot of posts (heck I even use the search box) before trying something new. Anyway, I'm sure it is posted in the forums somewhere if I need to find it.
Thanks!
pmsrefugee said:
Glad you told me that, otherwise I probably would have screwed up my GT.
Click to expand...
Click to collapse
It's not so much that you'll screw up your device by accepting an OTA, but rather that you might lose root and/or your custom recovery (perhaps permanently). Nevertheless, there are some cases of OTAs screwing up devices when accepted over non-stock installs, so IMHO its always best to wait for a flashable ROM.
pmsrefugee said:
I don't know how I missed the post about backing up the stock image first. I try to read a lot of posts (heck I even use the search box) before trying something new. Anyway, I'm sure it is posted in the forums somewhere if I need to find it.
Thanks!
Click to expand...
Click to collapse
Yes, I believe the stock retail recovery is posted in the CWM recovery download package here: http://forum.xda-developers.com/showthread.php?t=1130574. You'll note that Step 3 is where you were advised to backup your original stock recovery, although the step is (correctly) noted as optional. No big deal, in any event. Glad I could help.
Before everyone feels obligated to point this out... yes, I know this will prevent me from unlocking the bootloader. I plan to stick with stock ROM's, so that should not be a problem for me.
I've downloaded the OTA, and made a copy on me SD card.
When I try to run the update normally, it fails without any error message I can see.
When I rename the OTA file to update.zip and try to update from sdcard through recovery, I get an error message referring to build.prop. As far as I can remember, I have never done anything with build.prop on this device. In any event, I'm not sure what to do to fix this.
I would like to get the update installed. Any ideas?
Be glad, that it fails. There is something that do not match and if it would go through, your phone would be dead.
Look in the zip /meta-inf/com/android/metadata, open it and check what pre-build do you need. You must have this one in the phone without root or other changes.
peetr_ said:
You must have this one in the phone without root
Click to expand...
Click to collapse
I doubt that's true. My wife's photon was rooted and did the OTA just fine.
Ok. But after some readings here I wouldn't risk that.
friends, brothers, fellow technologically advanced people lend me your ears
yea, I "figured" it out. had the same problem, but now "at last" i'm on 2.3.5
you're going to have to flash (back to stock; unroot) as done in the qbking video here
http://www.youtube.com/watch?v=J94VcWk-CJc
but when you're choosing which sbf file to flash, dl, - pick '154'
i tried the 198_6 but that didn't work for me.
once you've flashed '154,' you'll have to do two updates before you get to the 2.3.5 one
.....note: after the first one, i lost wifi and 3g, but a quick reboot brought it back.
.............note 2: after you've flashed 154, your photono will take a while to find service, because it'll be deactivated on the phone,
but then it just gives you an option to 'activate' and you're good.
when i was rooted i got rid of some of the bloat sprint stuff; i think that's the 'root' of the problem.
alexthen said:
you're going to have to flash (back to stock; unroot)
Click to expand...
Click to collapse
Not really.
My device has never had anything but stock. It's rooted, but my wife's was also rooted and had no trouble.
I just copied her build.prop to my device and the update went without a hitch. I am fairly certain I never modified my build.prop, but I suppose it's possible. I had to use her 2.3.5 build.prop, too, since this happened after she upgraded.
I never did figure out what the problem was, so the issue that is the thread topic of figuring out what was keeping the update from succeeding is not actually solved. However, a potential solution to the failed upgrade is to copy a different build.prop.
Nexus 7, 2013, 16 gigs, wifi model.
Every few days(sometimes once a day) I get a 'new' android 4.3 update, which once it reboots into the teamwin bootloader, and finishes installing the update(which always seems to work for first 2 steps but says no contents in file, then 2 errors after) I lose root access and it asks if I want to reapply(which I do) and it loads as normal on a restart. I am with build number JWR66N now, but the info page on the TWRP window shows it updates JWR66N to (And I forgot the number here, but its different)
So I'd like to know, is it normal to have 'constant' android updates like this, and if not, what build number should I have?
I have had this issue since about a week after I got my nexus, its been rooted ever since, but in an attempt to fix this issue(Which is just annoying, I doubt its causing any real damage) I unrooted the nexus, updated it(Manually) and re-rooted it using the wugfresh rootkit.
What exactly is the issue here, and how can I fix it?
AtmaDarkwolf said:
Nexus 7, 2013, 16 gigs, wifi model.
Every few days(sometimes once a day) I get a 'new' android 4.3 update, which once it reboots into the teamwin bootloader, and finishes installing the update(which always seems to work for first 2 steps but says no contents in file, then 2 errors after) I lose root access and it asks if I want to reapply(which I do) and it loads as normal on a restart. I am with build number JWR66N now, but the info page on the TWRP window shows it updates JWR66N to (And I forgot the number here, but its different)
So I'd like to know, is it normal to have 'constant' android updates like this, and if not, what build number should I have?
I have had this issue since about a week after I got my nexus, its been rooted ever since, but in an attempt to fix this issue(Which is just annoying, I doubt its causing any real damage) I unrooted the nexus, updated it(Manually) and re-rooted it using the wugfresh rootkit.
What exactly is the issue here, and how can I fix it?
Click to expand...
Click to collapse
really this is just an issue I have and nobody else has seen it? Nobody at all has had this problem and knows the fix? Well gee!
Another bump just incase, its happened again: Update yet nothings actually changed, had to 'swipe to fix' root permissions in bootlader menu.
Here we are again, and i REALLY want to get this fixed, and i just can't accept that 'I'm the only bloody nexus 7 user world frakin wide who has this issue.
So here I am again hoping for some help.
Build JWR66N currently, every few days it tries to update android OS, and it FAILS TO UPDATE, (IT wants to update to JSS15R i think)
New update is 53.8 mb,
Someone please help me out here, how do I get it to either accept the update, or stop freaking out about it?
AtmaDarkwolf said:
Here we are again, and i REALLY want to get this fixed, and i just can't accept that 'I'm the only bloody nexus 7 user world frakin wide who has this issue.
So here I am again hoping for some help.
Build JWR66N currently, every few days it tries to update android OS, and it FAILS TO UPDATE, (IT wants to update to JSS15R i think)
New update is 53.8 mb,
Someone please help me out here, how do I get it to either accept the update, or stop freaking out about it?
Click to expand...
Click to collapse
So from all this time, you weren't able to find your answer using the power of internet?
Stock OTA updates cannot be applied with custom recoveries. That's why it's failing.
JSS15R is 8MB though, not 53.8MB. Either way, you can go back to full stock, recovery included after backing up your stuff. Then update, and reroot + re-install a custom recovery.
Aside from that, you're not really in the good section so don't be surprised you don't get any answer. This is strictly a N7 question, and XDA has a N7 sub section...
http://forum.xda-developers.com/forumdisplay.php?f=1673
polobunny said:
So from all this time, you weren't able to find your answer using the power of internet?
Stock OTA updates cannot be applied with custom recoveries. That's why it's failing.
JSS15R is 8MB though, not 53.8MB. Either way, you can go back to full stock, recovery included after backing up your stuff. Then update, and reroot + re-install a custom recovery.
Aside from that, you're not really in the good section so don't be surprised you don't get any answer. This is strictly a N7 question, and XDA has a N7 sub section...
http://forum.xda-developers.com/forumdisplay.php?f=1673
Click to expand...
Click to collapse
Yes, Must that I foolishly thought this was a ANDROID device and this may have been a similar issue(searched n7 forums and saw nothing) - and even with all the googling, I got nothing. BUT Now that I have 'followed your advice' (God I hope I can get my stuff back, backup didn't go as smooth as I had hoped, and 2 of my fav games I had to copy/paste myself to save them) All I've managed to do now was reset my device back to complete stock settings.... and this morning, Low and behold: SYSTEM UPDATE, ONCE AGAIN, same bloody one, same bloody problem, WILL NOT INSTALL.
So thanks. Next please? (Sorry if I sound a little angry, but I am, this forum, at least I THOUGHT, was full of people who liked to help others and KNEW what they were talking about, not trolls who tell people to 'use the search button' or go elsewhere for help. Honestly, after 2-3 hours a night googling this issue, for 3 weeks give or take now, trust me, I know its not like I have anywhere but here to go, the only reason I'm HERE, in THIS subforum, was because similar issues were posted about right here... more similar than anywhere else.)
Anyways, now I got a wiped device which I hope I can at least get back to where I was. Knowing NOW it had nothing to do with being stock or not, its simply unable to install update.
AtmaDarkwolf said:
Yes, Must that I foolishly thought this was a ANDROID device and this may have been a similar issue(searched n7 forums and saw nothing) - and even with all the googling, I got nothing. BUT Now that I have 'followed your advice' (God I hope I can get my stuff back, backup didn't go as smooth as I had hoped, and 2 of my fav games I had to copy/paste myself to save them) All I've managed to do now was reset my device back to complete stock settings.... and this morning, Low and behold: SYSTEM UPDATE, ONCE AGAIN, same bloody one, same bloody problem, WILL NOT INSTALL.
So thanks. Next please? (Sorry if I sound a little angry, but I am, this forum, at least I THOUGHT, was full of people who liked to help others and KNEW what they were talking about, not trolls who tell people to 'use the search button' or go elsewhere for help. Honestly, after 2-3 hours a night googling this issue, for 3 weeks give or take now, trust me, I know its not like I have anywhere but here to go, the only reason I'm HERE, in THIS subforum, was because similar issues were posted about right here... more similar than anywhere else.)
Anyways, now I got a wiped device which I hope I can at least get back to where I was. Knowing NOW it had nothing to do with being stock or not, its simply unable to install update.
Click to expand...
Click to collapse
you cant update your phone if it is rooted you have to unroot for that or just temporary unroot the option is available in supersu /superuser
and some apps like root keeper and you have to be on stock recovery
AtmaDarkwolf said:
*snip*
Click to expand...
Click to collapse
Not trolling, the sub categories are there for a reason.
Good luck!
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.