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
Related
I'm rooted and originally de-crapped my phone which kept the first update from installing. However, with some help from posters here I was able to find the missing file, get it properly replaced and the update then worked.
I assumed that would mean I would be good from then on and kept everything intact. Now the latest update is out and I once again cannot update but it's been long enough that I'm now not sure about the process for getting this working.
Any help would be appreciated.
Agrajag27 said:
I'm rooted and originally de-crapped my phone which kept the first update from installing. However, with some help from posters here I was able to find the missing file, get it properly replaced and the update then worked.
I assumed that would mean I would be good from then on and kept everything intact. Now the latest update is out and I once again cannot update but it's been long enough that I'm now not sure about the process for getting this working.
Any help would be appreciated.
Click to expand...
Click to collapse
Come on guy, there is like 10 other threads over here talking about not being able to install the update. Anyway, there is a thread right here that has all of the apk files of the device. I cant find it now cause im on my cell. Ifyou cant find it by the time I finish work I'll post the link. that didnt work for me so I fastbooted my phone with the factory image, rooted, protected root, unrooted,install one update, installed the latest update, and restored root. good luck.
I actually looked but didn't notice others having an issue so I might have just missed it. I assumed, like last time, others would have the issue so I was actually surprised not to find 10 threads with people talking about it.
I couldnt find the thread i was talking about cause my stupid self was too lazy to click one button to add it to my favorites but it looks like this could work for you.
http://forum.xda-developers.com/showthread.php?t=1362956
Ok, I'm going to preface this thread with the statement "I am a noob".
Now... I'm working on unlocking the bootloader so that I can start checking out roms (Virtuous Prime and Cornerstone). I rooted the tablet last night, and then tried to unlock the bootloader, but keep getting the message "Failed to unlock your device, please try again later". What is the problem here? It's been mentioned to me to try flashing the Asus .15 update from the site onto the tablet, and then trying a factory reset afterwards if that doesn't work. Anyone else had this problem and fixed it? I have tried unrooting and doing it also. When I try this, I am connected to the internet. Also, I am on the latest .15 update via an OTA update. I have not tried to unlock the boot loader or root previous to last night.
Thanks.
i to am having the same issue ! any help would be apprieciated.
Deathbyfugu said:
Yes, I did get it solved. I had to download the full 9.4.2.15 update from Asus, extract the .zip and rename the other .zip contained within it to "SD201_UPDATE.zip" and place it on the Micro SD. Then reboot the Prime and hold Vol Down and Power until some text appears on the upper left and then press Vol Up. This will reflash the official firmware and after that is done you can either try once more or do a factory reset. After a factory reset (if it didn't work after the initial process) it should work without an issue.
Click to expand...
Click to collapse
This is what I was told via a PM as he also had the same problem. I don't have an sd card here large enough to put the whole update on to flash (if I'm even understanding how this all works correctly)(it's only 512MB and the update is 547 or so).
I didn't want to do a factory reset quite yet as I need to backup the photos and things on my tablet. Although, I'm not sure; I may lose everything once I install a rom? I'm still researching all of this...
Go to Settings, About and check to see if you have a serial.
If not..
http://androidroot.mobi/2012/01/31/introducing-ratchet-the-unknown-serial-fix/
Have a nice day
Under "Status", the field that says "Serial number" is filled in with my correct/matching serial number, yes.
yes same here i had an unkown serial issues but i fixed that a couple days ago and havent been able to unlock this mug
I'll be giving the method mentioned to me via PM a try this evening when I get home from work if I don't have any other answers regarding how to make it work, and report back. Already backed up most of my important data.
Having the exact same problems plus I'm having trouble getting ANY updates working prior to wanting to unlock my bootloader... thought unlocking and update with new ROM would solve things...
Add me to the list of: "Failed to unlock your device. Please try again later"- serial number is listed and correct... :-/
Sent from my HTC ThunderBolt using Tapatalk
Sounds like something isn't working right on the server side. Maybe Asus is doing maintenance on the server or it crashed or they even disabled it.
Of course, when I finally decide, "OK, it's relatively safe to unlock, flash CWM and get some custom ROMs on here..." the unlock tool stops working. Hopefully just a temporary thing
Sent from my Transformer Prime TF201 using Tapatalk
Same issue here
I too am getting the issue. I re-downloaded .15 firmware, reinstalled, and factory reset and still no luck. Hoping its just something on the Asus end of things. really want some custom rom love on my prime.
same thing here everyone ughh
Hmm, well I guess at least it's not just me. Fudge, was really looking forward to getting this going.
Reloaded83 said:
Hmm, well I guess at least it's not just me. Fudge, was really looking forward to getting this going.
Click to expand...
Click to collapse
Yea me to. i wonder why its happening. I never had a serial issue and i received all the updates no problem
AndroidPhan said:
Yea me to. i wonder why its happening. I never had a serial issue and i received all the updates no problem
Click to expand...
Click to collapse
Same here.
I have a feeling Asus retracting the tool. or not allowing people to unlock anymore from all the complaining going on.
demandarin said:
I have a feeling Asus retracting the tool. or not allowing people to unlock anymore from all the complaining going on.
Click to expand...
Click to collapse
Why ASUS, why must you do such a thing?
For me the same problem, I received ota updates at .15 and I can not unlock. Solutions?
Thanks
Worked this morning 3/2/12 at 7:15 am Eastern time
Woke up this morning and figured I'd try again to unlock my prime, and what do you know, worked the very first time. Looks like maybe it was things on the Asus end. Please let me know if anyone else gets this to work today.
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!
Hiya folks, bit of a problem. I never bothered to root or unlock my DNA (it's been getting the job done nicely with a few non-root customizations, and I have other gadgets to tinker away with). This morning I accepted the OTA update from Verizon, and now it's bricked - stuck on the HTC splash screen.
I did a soft reset, cleared the cache partition, and performed a hard reset - no dice. Called Verizon and HTC, no help - I can pretty much do a repair/replacement if I'm still under warranty. I'd really rather avoid going down that path, as I think I'm barely over the warranty (though I can hopefully get them to honor it if I'm within 30 days).
Is there any way I can still flash this back to an older stock, having never unlocked it? I can only get the thing into fastboot mode, and all of the instructions I've found are for when the phone's been bricked after rooting. adb can't seem to talk to it at all, probably because it's in fastboot. Is it safe to attempt using an RUU or some sort of image to flash it using the fastboot utility?
Since it's already bricked, I went ahead and made a go at it using an older RUU, but it quick before even trying, claiming I needed the correct version of the utility. It's possible I did it wrong, though.
Any help would be much obliged! This is what I get for not rooting/learning how to do this stuff earlier...
EDIT: Before this newest update, my phone had the most up-to-date stock ROM. It was fully charged when it performed the OTA.
jaawerth said:
Hiya folks, bit of a problem. I never bothered to root or unlock my DNA (it's been getting the job done nicely with a few non-root customizations, and I have other gadgets to tinker away with). This morning I accepted the OTA update from Verizon, and now it's bricked - stuck on the HTC splash screen.
I did a soft reset, cleared the cache partition, and performed a hard reset - no dice. Called Verizon and HTC, no help - I can pretty much do a repair/replacement if I'm still under warranty. I'd really rather avoid going down that path, as I think I'm barely over the warranty (though I can hopefully get them to honor it if I'm within 30 days).
Is there any way I can still flash this back to an older stock, having never unlocked it? I can only get the thing into fastboot mode, and all of the instructions I've found are for when the phone's been bricked after rooting. adb can't seem to talk to it at all, probably because it's in fastboot. Is it safe to attempt using an RUU or some sort of image to flash it using the fastboot utility?
Since it's already bricked, I went ahead and made a go at it using an older RUU, but it quick before even trying, claiming I needed the correct version of the utility. It's possible I did it wrong, though.
Any help would be much obliged! This is what I get for not rooting/learning how to do this stuff earlier...
EDIT: Before this newest update, my phone had the most up-to-date stock ROM. It was fully charged when it performed the OTA.
Click to expand...
Click to collapse
Exact same thing happened to me last evening...except I'm rooted with S-off.
grimmkt said:
Exact same thing happened to me last evening...except I'm rooted with S-off.
Click to expand...
Click to collapse
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
ryclegman said:
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
Click to expand...
Click to collapse
Aha! Much obliged. I searched for the right RUU and couldn't find it, and completely missed that thread - I was using the wrong search terms. Downloading now - I'll update tonight once I know if it works. Then I'm modifying the crap out of this thing!
jaawerth said:
Aha! Much obliged. I searched for the right RUU and couldn't find it, and completely missed that thread - I was using the wrong search terms. Downloading now - I'll update tonight once I know if it works. Then I'm modifying the crap out of this thing!
Click to expand...
Click to collapse
Sounds good! let us know!:good:
ryclegman said:
Try flashing the latest RUU ZIP in fastboot. someone had a similar issue.
http://forum.xda-developers.com/showpost.php?p=48301738&postcount=6
The actual thread is here: http://forum.xda-developers.com/showthread.php?t=2558885
Click to expand...
Click to collapse
I can't get the phone to connect in fastboot. I keep getting a "driver failed to load" type error when I plug in the USB...the device is never visible.
Worked like a charm! The download took awhile, but once I had it downloaded it was easy.
For others searching for this issue:
Once you have the RUU, just install Android Development tools (specifically fastboot) and enter
>fastboot oem rebootRUU
>fastboot flash install IMAGEFILE.ZIP
Terminal/command prompt on the computer side told me it was finished but the phone was stuck at the very end of the progress bar. I waited a while few minutes, and when it didn't move I risked doing a
>fastboot reboot
and we were good to go.
Arise, thread!
So! My phone never bricked again, but a few weeks after I performed the RUU with the image linked earlier in this thread, I started to see the problem that early DNA's started to have with it randomly giving a "no SIM card" error. I'd had this issue when I first got the DNA, but at the time I just went through the normal phone replacement process to resolve it. Imagine my surprise when it came back after flashing! It's now reached the point where I will lose calls because of it, and will often have to reboot/toggle airplane mode to get data back, so I finally got annoyed enough to post.
Presumably this problem is because the image I flashed from is the original DNA image with the drivers that cause that SIM issue. So my question is: if I s-off, root, and install a custom ROM, will that take care of it? Or is this particular issue so deep on the driver level that I need to find a more recent RUU?
I also have not yet tried a new SIM - because of the timing of the problem, I'm slow to believe that it's related to the SIM card, but I suppose it isn't impossible.
jaawerth said:
Arise, thread!
So! My phone never bricked again, but a few weeks after I performed the RUU with the image linked earlier in this thread, I started to see the problem that early DNA's started to have with it randomly giving a "no SIM card" error. I'd had this issue when I first got the DNA, but at the time I just went through the normal phone replacement process to resolve it. Imagine my surprise when it came back after flashing! It's now reached the point where I will lose calls because of it, and will often have to reboot/toggle airplane mode to get data back, so I finally got annoyed enough to post.
Presumably this problem is because the image I flashed from is the original DNA image with the drivers that cause that SIM issue. So my question is: if I s-off, root, and install a custom ROM, will that take care of it? Or is this particular issue so deep on the driver level that I need to find a more recent RUU?
I also have not yet tried a new SIM - because of the timing of the problem, I'm slow to believe that it's related to the SIM card, but I suppose it isn't impossible.
Click to expand...
Click to collapse
The only way I have seen this permanently resolved is to get a new Sim tray from HTC. I got one and my brother did too and I never get Sim card errors like I used to. Just go to their website contact their support and ask for one and they send it out for free no questions asked.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
The only way I have seen this permanently resolved is to get a new Sim tray from HTC. I got one and my brother did too and I never get Sim card errors like I used to. Just go to their website contact their support and ask for one and they send it out for free no questions asked.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, may as well give it a try. What's odd is that this problem hadn't happened at all with this sim tray until after I flashed, which really makes it sound like a software issue. Still, worth a shot!
jaawerth said:
Thanks, may as well give it a try. What's odd is that this problem hadn't happened at all with this sim tray until after I flashed, which really makes it sound like a software issue. Still, worth a shot!
Click to expand...
Click to collapse
It's a known hardware issue in the DNA. When they give you a new Sim tray it's thicker and it holds the Sim card in place better resulting with no more errors.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
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.