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.
Related
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 have a ZTE Avail 2 which I recently managed to root with Cydia Impactor. Afterwards I managed to screw it up by removing too many stock apps with Titanium. I did it carefully, one by one, and for a few days everything seemed to work fine. But then apps started force-closing, '<name of app here> has stopped working', etc. Factory reset doesnt help, it just restores me to the same screwed up state I'm in now. I already know why, it's because I removed some of the stock apps, which I now realize it needs. I'm currently stuck on the AT&T logo when powering on, it never gets any further. But even while it was messed up it was still halfway-operable, and now this. This device's subforum on Android Forums is all but non-existent, and XDA doesnt seem to have anything for it.
What I need is a 100% stock ROM (pre-rooted if possible) that I can flash, along with instructions on how to flash it. I have some experience flashing ASUS devices and Samsung devices, mainly the Transformer pad, and the Note 2, but have also rooted miscellaneous other devices in the past without alot of issues. But I have no experience with ZTE. I've already checked the manaufacturer's website for some kind of recovery software I can use to restore it, there doesnt seem to be anything.
Thanks for any help!
Stephen Wayne Hamilton said:
I have a ZTE Avail 2 which I recently managed to root with Cydia Impactor. Afterwards I managed to screw it up by removing too many stock apps with Titanium. I did it carefully, one by one, and for a few days everything seemed to work fine. But then apps started force-closing, '<name of app here> has stopped working', etc. Factory reset doesnt help, it just restores me to the same screwed up state I'm in now. I already know why, it's because I removed some of the stock apps, which I now realize it needs. I'm currently stuck on the AT&T logo when powering on, it never gets any further. But even while it was messed up it was still halfway-operable, and now this. This device's subforum on Android Forums is all but non-existent, and XDA doesnt seem to have anything for it.
What I need is a 100% stock ROM (pre-rooted if possible) that I can flash, along with instructions on how to flash it. I have some experience flashing ASUS devices and Samsung devices, mainly the Transformer pad, and the Note 2, but have also rooted miscellaneous other devices in the past without alot of issues. But I have no experience with ZTE. I've already checked the manaufacturer's website for some kind of recovery software I can use to restore it, there doesnt seem to be anything.
Thanks for any help!
Click to expand...
Click to collapse
Just out of curiosity you ever figure out a solution? I have the AIO branded version of it.
drago10029 said:
Just out of curiosity you ever figure out a solution? I have the AIO branded version of it.
Click to expand...
Click to collapse
If needed, I could back up my /system folder and send it to you.
Simba.7 said:
If needed, I could back up my /system folder and send it to you.
Click to expand...
Click to collapse
it's alright man. someone on android forums has already made a custom ROM. so the ball is rolling on out weak old device :laugh:
build.prop?
Simba.7 said:
If needed, I could back up my /system folder and send it to you.
Click to expand...
Click to collapse
did you ever get around to doing this? there is supposedly a stock image on androidforums but when I opened the Zip, all it had was the stock apps, no build.prop, which I think I blew away with xblast (xposed plugin). now I hang on the boot screen image. there is a stock Rom for the z993 our there, which I suppose I could use, because they are supposed to be the same phone, just different carriers... but then I need to get the at&t apn's and it is just a PITA. so if you could post /system backup or just a stock build.prop, that would be great!
(I'd post links to these rooms but I guess I'm too new of a member... I can provide them if needed.)
I'm way late on this, but just thought I'd post to say that I no longer have the device, and I was never able to fix it.In any case, I hope the rest of you guys get it fixed. It seemed to be a halfway decent phone, although a bit sluggish at times. But beyond that, with all the bloat removed, I'd say it ran pretty well for the duration of time that I had it (less than a month). I currently have a GNote 3 (T-Mobile) and a GNote Pro 12.2" now and it's just awesome, I'm really loving them.
Sorry, accidental double-post (can't figure out how to delete this post, the "Edit/Delete" button doesnt appear to have any option to entirely delete a post).
Just like "AnonVendetta83" messed up using Titanium.
Now desperately looking for Stock ROM or any working custom ROM to bring phone back to life.:crying:
alirezayami said:
Just like "AnonVendetta83" messed up using Titanium.
Now desperately looking for Stock ROM or any working custom ROM to bring phone back to life.:crying:
Click to expand...
Click to collapse
There is a working custom Rom for the z993 (identical hardware, different customized software for AIO, another cell provider). All you will need to do is change/update the data provider stuff so you can still use 3g and mms's. Plenty of info on this online on what needs to be changed.
You can get this Rom over at androidforums.com
http://androidforums.com/prelude-all-things-root/792279-zte-prelude-z993-stock-unrooted-rom-aio.html
There is also a cwm recovery there that works on this phone, and a partial /system backup by someone else for the z992... it is just apps and what not.
If they aren't available anymore, let me know and ill see if I still have them saved somewhere for you.
Sent from my KFTHWI using Tapatalk
AlexZap said:
There is a working custom Rom for the z993 (identical hardware, different customized software for AIO, another cell provider). All you will need to do is change/update the data provider stuff so you can still use 3g and mms's. Plenty of info on this online on what needs to be changed.
You can get this Rom over at androidforums.com
http://androidforums.com/prelude-all-things-root/792279-zte-prelude-z993-stock-unrooted-rom-aio.html
There is also a cwm recovery there that works on this phone, and a partial /system backup by someone else for the z992... it is just apps and what not.
If they aren't available anymore, let me know and ill see if I still have them saved somewhere for you.
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
Thank you so very much Alex
I was wondering if I can just simply place the rom zip on the root of your sdcard and continue without doing "Install CWM - ZTE Prelude (Z993) Root&Recovery" step???
Honestly I have absolutely no idea how to do CWM steps as they come so complicated to me.
alirezayami said:
Thank you so very much Alex
I was wondering if I can just simply place the rom zip on the root of your sdcard and continue without doing "Install CWM - ZTE Prelude (Z993) Root&Recovery" step???
Honestly I have absolutely no idea how to do CWM steps as they come so complicated to me.
Click to expand...
Click to collapse
You need to install the custom recovery... It is the only way to install the zip file. If you just have the zip and go into the stock recovery I don't think you can select which zip to install
Sent from my N9002 using XDA Premium 4 mobile app
AlexZap said:
There is a working custom Rom for the z993 (identical hardware, different customized software for AIO, another cell provider). All you will need to do is change/update the data provider stuff so you can still use 3g and mms's. Plenty of info on this online on what needs to be changed.
You can get this Rom over at androidforums.com
http://androidforums.com/prelude-all-things-root/792279-zte-prelude-z993-stock-unrooted-rom-aio.html
There is also a cwm recovery there that works on this phone, and a partial /system backup by someone else for the z992... it is just apps and what not.
If they aren't available anymore, let me know and ill see if I still have them saved somewhere for you.
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
AlexZap said:
You need to install the custom recovery... It is the only way to install the zip file. If you just have the zip and go into the stock recovery I don't think you can select which zip to install
Sent from my N9002 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thnx Alex
I would highly appreciate if anyone tell me what ADB Driver I should use for ZTE Z992. I almost understood all the procedure in the links but now the problem is despite I tried different ADB Drivers, but still ADB reboot-bootloader boots phone again in Normal bootloader.
Also Fastboot devices command does not see the phone, while ADB Devices command see it.
Seems bootloader is locked. Right? What should I do?
This is the method I used when I rooted my avail2 :
http://androidforums.com/zte-avail-2-zte-prelude/821217-how-root-zte-avail-2-z992-guide.html
The author (and I) just used the included drivers from zte that come with the phone. From what I remember, fastboot worked fine. Just hold the volume down button then turn the phone on. It will seem to lock on the start screen, but this is the bootloader. Then connect your cable and try your fastboot commands.
If you are already rooted, you can just download the package here
http://androidforums.com/prelude-all-things-root/797487-cwm-recovery-installer-zte-prelude.html
And skip the middle section, using the impactor to root (13 and 14).
Depending on what's wrong with your phone, you could also try just using the stock recovery and doing a system reset there. It will wipe any bad custom settings, but if the rom is still viable it might get you up and running again. It got me out of a bootloop without re-romming the whole thing. And with titanium backup or system app mover you can reinstall anything you need in the system partition.
*edit - Damn kindle auto correct
Sent from my KFTHWI using Tapatalk
A bit to much fiddling resulted in disaster
Hello XDA forum users,
I'm about ready to toss this phone in the trash. I have an AT&T Avail 2 with model number z992, which is apparently manufactured by a company called ZTE. First I think it would be helpful to explain what I've done to the phone and perhaps others out there can tell me if I've destroyed the phone or if it can be fixed.
A friend of mine sold me the phone for 10 bucks, its in great condition which is why its such a shame that it seems perma-bricked. I have no need for the phone aspect of the device, I simply wanted to "convert" it to a handheld media/application player, like an ipod or tablet for example. The phone comes with several bundled software applications that I find completely useless and wanted them removed, EX. AT&T Navigator and other AT&T software, plus a bunch of google applications.
The first thing I did when I decided to try and customize it was to use Kango's root tool which worked and rooted the phone. I was all excited that it worked and continued by installing the Super User application which allowed me to gain full control over the device. (I should have stopped there.) After the successful phone root I then installed a 3rd party app called NoBloat and used its uninstall options to remove a lot of stuff. I couldn't tell you exactly what all was removed but looking back, it must have been more important than I realized at the time. I know I took out all the AT&T software, then all the Google stuff to, which destroyed the play store. I didn't take out anything that seemed like a system file but apparently the Google stuff is the system files. The phone still worked in this state but it was erratic and things like Contacts would crash even if it was not running. So I considered that a failed attempt and commenced to do a factory reset using the recovery menu (Vol Up + Menu Key + Power button) but the factory reset didn't work, well not like it was supposed to. I had used the restore option before and it made the phone work like it was brand new. Now when the phone is powered on it will boot to the initial setup and ask me to choose a language, then it will get as far as the wireless connection screen (sometime not even that far) and the phone reports that "Unfortunately, Setup Wizard has stopped." and then I tap OK and the setup wizard restarts at the language screen. This is the state it is in now and I do not know how to fix it, I'm beginning to think there currently is no method to fix this.
Things I've tried so far include installing minimal ADB-Fastboot to try and sideload various ROM images, the ones I found here and other places. The phone is not recognized by Windows 7 though and the ADB does not work like it did on a motorola phone I did this to before. I've also purchased an inexpensive 8GB microSD chip with an adapter so I could put the ROM info on that and tried the "Update from external storage option" and that seems like it would work but none of the ROM's I've used will install. I guess because there is some kind of security feature built into the phones hardware which checks the data files for specific tags/sizes and therefore won't accept any of the ROMS I've tried.
There is no means to access the old file system anymore like most guides show, I do not have any CWM's installed nor any backup data whatsoever. It's been reset and now it seems the data it used to restore itself is, while not completely missing, damaged and will not reload anymore. All the guides I've read or watched usually show the user in the operating system or using software on a PC to type out commands. None of that works on this phone though, the phone as I just described it is basically bricked. Is there anything that can fix this, or is the phone a paper weight now? A functional ROM image from AT&T seems unlikely as they have absolutely no relevant information about this on the commercial website and the help and support seems like it's setup for old people who don't understand technology at all. If anyone out there has experience with issues like this then by all means let me know. If more information is necessary then I will be glad to provide it if available.
Alright I did manage to figure out how to make the computer see the phone as an ADB device and the minimal ADB interface shows the device now when I type ADB devices at the command prompt. Though this ADB thing seems irrelevant considering I can do the same thing by using the SD card adapter. So I don't know if this was useful or not. The ADB prompt shows a device number of P752A15.
Before I was unable to make the device show up at all in the ADB list. The problem now is how to make the phone accept a ROM, at this point I don't even care if the ROM is the default factory ROM or some random ROM made by a devoted user. The issue I encounter each time is that the built in recovery option to restore from an SD card will not accept the ROM's I've tried so far, and my research on this seems to indicate that I need a custom recovery option. This is apparently called the ClockWorkMod but as to how I install that without a functional operating system on the device is a mystery still. I've tried using a file called recovery.zip and but it does not show up when I view the contents of the SD card when the card is in the phone.
I feel like an idiot because I've done this to other phones for my family and friends, you know jailbreaking an iPhone, and rooted a Galaxy S3 once but this phone seems like its not going to be as easy as those others. I guess AT&T made sure that if you alter it, it breaks the phone. I'll check back later and see if anyone has dropped a line or two here in response to my inquiry.
Thank you and have good day.
Britton Burton said:
Alright I did manage to figure out how to make the computer see the phone as an ADB device and the minimal ADB interface shows the device now when I type ADB devices at the command prompt. Though this ADB thing seems irrelevant considering I can do the same thing by using the SD card adapter. So I don't know if this was useful or not. The ADB prompt shows a device number of P752A15.
Before I was unable to make the device show up at all in the ADB list. The problem now is how to make the phone accept a ROM, at this point I don't even care if the ROM is the default factory ROM or some random ROM made by a devoted user. The issue I encounter each time is that the built in recovery option to restore from an SD card will not accept the ROM's I've tried so far, and my research on this seems to indicate that I need a custom recovery option. This is apparently called the ClockWorkMod but as to how I install that without a functional operating system on the device is a mystery still. I've tried using a file called recovery.zip and but it does not show up when I view the contents of the SD card when the card is in the phone.
I feel like an idiot because I've done this to other phones for my family and friends, you know jailbreaking an iPhone, and rooted a Galaxy S3 once but this phone seems like its not going to be as easy as those others. I guess AT&T made sure that if you alter it, it breaks the phone. I'll check back later and see if anyone has dropped a line or two here in response to my inquiry.
Thank you and have good day.
Click to expand...
Click to collapse
Ok, been a while since I've used this phone, but hopefully this will help. I assume you have the kaw202_recoveryflasher.zip file. Once you extract it, look for the .img file. Try running these adb commands
adb.exe push cwm-z993.img /cache
adb.exe shell "su -c 'dd if=/cache/cwm-z993.img of=/dev/block/mmcblk0p17'
This should flash cwm if your phone is rooted and adb shell is working.
Sent from my KFTHWI using XDA Premium 4 mobile app
AlexZap said:
Ok, been a while since I've used this phone, but hopefully this will help. I assume you have the kaw202_recoveryflasher.zip file. Once you extract it, look for the .img file. Try running these adb commandsp
Click to expand...
Click to collapse
I have not come across that particular file yet, I did try to google it and the only results it had were two and one of those was this post. Would you mind telling me where I might find a copy of the kaw202_recoverflasher.zip?
I managed to find the zip you were talking about and have downloaded it, for anyone else looking for it. I am unable to post links but I would have linked to the files you mentioned. For others looking for the same zip file search for "CWM Recovery Installer ZTE PRELUDE". That's the title of the thread I found the file on that Alex mentioned above. The instructions on the page don't seem like they apply to the situation I'm stuck in but I'll give it a whirl anyway and see if the files work.
If this forum is like the others I've read through so far then there is no real answer to the issue. The phone seems kind of new and not many of the power users on these forums use rinky dink phones like this one. You guys all have the 600 dollar models I guess. What bugs me about this this phone and the state I managed to put it in, is that the damn thing was programmed the first time when it was made. So it seems to me like there should be a way to reprogram the phone the same way the factory did it. Think about it, when they make the phones they don't have any information on the phone at all. It's completely empty, so there must be a way to load the software for the phone even if the phone has no data at all in the main storage. If the files in the recovery flasher.zip file work then I'll post back the results but if it's like the other files I've messed around with (which didn't do anything) then I'm throwing it in the trash can.
Anyway thanks for your response and for pointing me in a different direction Alex
---------- Post added at 09:15 PM ---------- Previous post was at 08:39 PM ----------
HELL YEAH!!! It worked thank you Alex,
I would have never figured this out without your help! The phone now has a version of CWM on it and the recovery menu is different. I just tried to install a ROM and it said successful. After the phone rebooted went back to the setup screen from ZTE but it still did the same thing. However this is progress and I should be able to "wander in the dark" and figure out a way to use the CWM to install a completely new rom. Any recommendations on a ROM to use for the z992?
Good news, I was able to fix it using the information Alex guided me to find. Since there doesn't appear to be a stock AT&T version of the ROM I ended up using the Azazel ROM. Which at first failed even though it was installed, this I determined was due to the old ROM image still being partially active on the system partition. So I formatted the system partition to and tried again. This time it worked and the phone seems fully functional again, and best of all the annoying bloatware is not present and the apps are not crashing. I consider this issue resolved. Thank you again Alex I will be sure to leave a thanks on your post.
Britton Burton said:
Good news, I was able to fix it using the information Alex guided me to find. Since there doesn't appear to be a stock AT&T version of the ROM I ended up using the Azazel ROM. Which at first failed even though it was installed, this I determined was due to the old ROM image still being partially active on the system partition. So I formatted the system partition to and tried again. This time it worked and the phone seems fully functional again, and best of all the annoying bloatware is not present and the apps are not crashing. I consider this issue resolved. Thank you again Alex I will be sure to leave a thanks on your post.
Click to expand...
Click to collapse
ze
Glad I could help, but none of the work was done by me, the guys over at android central did all the heavy lifting, I just pointed you in the right direction. I have a stock system e m image around here somewhere if you need it, tho installation will be a bit more complicated. If azazels rom ever gives you issues, ill dig it up and try and help you install it.
Sent from my KFTHWI using XDA Premium 4 mobile app
Hello everyone,
Here is the sad tale:
I recently got my Kindle Fire HDX and immediately started fiddling with it. Got it rooted and installed GApps using KindleFree. I then decided to buy KindleFree Pro to tweak even more. I fiddled around with the custom launcher option and basically bricked the device all within the same day that I got it! I'm not sure what that option changed exactly behind the scenes but I was able to ADB in and noticed that Launcher-release-signed_82046410.apk has a size of 0kb... that can't be right so I figured I'd start there...
First, I'd like for someone to confirm the size of theirs, if it isn't 0kb (which I doubt it will be) then can someone kindly upload that APK so I can load it up and hopefully get this thing working again?
Alternatively, can anyone suggest a way to simply reflash the stock rom via ADB somehow? I never installed safestrap and I don't think it can be installed via ADB. At least not that I've seen.
Thanks!
ok sorry
mkid89 said:
Hello everyone,
Here is the sad tale:
I recently got my Kindle Fire HDX and immediately started fiddling with it. Got it rooted and installed GApps using KindleFree. I then decided to buy KindleFree Pro to tweak even more. I fiddled around with the custom launcher option and basically bricked the device all within the same day that I got it! I'm not sure what that option changed exactly behind the scenes but I was able to ADB in and noticed that Launcher-release-signed_82046410.apk has a size of 0kb... that can't be right so I figured I'd start there...
First, I'd like for someone to confirm the size of theirs, if it isn't 0kb (which I doubt it will be) then can someone kindly upload that APK so I can load it up and hopefully get this thing working again?
Alternatively, can anyone suggest a way to simply reflash the stock rom via ADB somehow? I never installed safestrap and I don't think it can be installed via ADB. At least not that I've seen.
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2786190 and that's why we have safestrap so you don't modify your stock http://www.youtube.com/watch?v=K6fPF5UZsWw
There are a few Devs still working on a way to flash something from fast boot no ETA means no promises seems the only fix for you may be to call Amazon . And maybe someone will chime in with a way to sideload an app I'm not sure. Good luck
I should have listened to the warnings when people said it was easy to brick! I've been modifying devices since the windows mobile days before android and never once have felt this hopeless! Safestrap will be the first thing I do once I get this running again.
The good news is I still have SU root access in ADB without needing a Fastboot cable. I'm thinking everything else but the launcher loads so it is pretty much fully functional but with no gui. It sometimes will even boots to the lock screen but unlocks to a black screen.
I think I should be able to sideload the launcher if someone can get me the apk.
well
mkid89 said:
I should have listened to the warnings when people said it was easy to brick! I've been modifying devices since the windows mobile days before android and never once have felt this hopeless! Safestrap will be the first thing I do once I get this running again.
The good news is I still have SU root access in ADB without needing a Fastboot cable. I'm thinking everything else but the launcher loads so it is pretty much fully functional but with no gui. It sometimes will even boots to the lock screen but unlocks to a black screen.
I think I should be able to sideload the launcher if someone can get me the apk.
Click to expand...
Click to collapse
If your patient somebody savvy enough will come by. and actually I know that I have read that someplace here I couldn't tell you where sorry. And if you're hoping for somebody to drop off the apk for you probably should let them know which firmware you are. Or you could always download the Bin file of your current firmware and exract it. Downloaded to an android rename it .zip and extract
That's a good idea but I don't know where to get the bin file or how to confirm I have the correct one. I had just updated so I believe it was the latest version. I'm thinking it's v13.3.2.1 or maybe v13.3.2.4 it said there were no more updates available so it should be the latest.
It's an 8.9. Don't think I mentioned that.
well
mkid89 said:
That's a good idea but I don't know where to get the bin file or how to confirm I have the correct one. I had just updated so I believe it was the latest version. I'm thinking it's v13.3.2.1 or maybe v13.3.2.4 it said there were no more updates available so it should be the latest.
It's an 8.9. Don't think I mentioned that.
Click to expand...
Click to collapse
8.9 is 14.3.2.4 https://s3.amazonaws.com/kindle-fire-updates/update-kindle-14.3.2.4_user_324002120.bin
Thank you for your help! I actually got it working shortly after my last post but got right into installing safestrap. ?
I'll post a write up tomorrow on what needed to be done in case anyone else has the issue. It's late where I'm at so I need to get some rest before trying to write it all up!
Ok! Now that I have a fresh mind I can document the steps I took to correct this issue.
How did this happen to begin with? I think that when I tried to set a custom launcher as default using KindleFree Pro, the launcher I selected was unable to load properly or something interrupted the process. Either way, it either would only load to the lock screen or just sit on the boot animation. I'm thinking the way that KindleFree works is that it replaces the default launcher apk with a link that points to the launcher you want to replace it with (hence the 0kb size). Either that or something got corrupted during the process of changing the launcher. I'm not sure what KindleFree does behind the scenes so this is all just speculation.
Anyways, on to the good stuff. Once I noticed the launcher was 0kb, thats where I decided to direct my troubleshooting efforts. I posted this thread hoping someone would upload the stock launcher for me to replace it with but jimyv gave me the idea to just grab it from the bin. I ended up finding the bin file here: http://www.amazon.com/gp/help/customer/display.html?nodeId=201357190 before he replied with the direct link. The "Download Software Update" link is a direct link to the .bin file. I changed the extension, opened it up and found the launcher apk per jimyv's suggestion.
Once I had the file, I needed to get it onto the HDX. I more or less followed the instructions here: http://forum.xda-developers.com/showthread.php?t=2588608
Instead of replacing the odex files, I replaced the launcher apk under /system/app/ As soon as it had finished copying over, the device went from the boot splash screen to the lock screen in what can only be described as a magical moment.
Interesting to note: Most people say that if you perform a factory reset from the stock recovery, your hopes of using ADB and having root are gone unless you get a factory/fastboot cable. I actually did perform a factory reset but for some reason was still able to use ADB and did not lose root access. I had used TowelRoot to root the device so I'm wondering if that is a more permanent means of rooting compared to other methods? Either way, I'm glad I didn't lose root. Otherwise I would have needed to wait for a factory cable to be shipped and to root it via ADB.
Fyi that Chinese root method which is posted early on in the rollback thread it will root with ADB only.. And the factory reset thing has not really been consistent throughout each user.. But more or less we have been advising people not to because the chances are greater that you will lose the superuser binaries and you definitely will lose safestrap if installed. What is hard to get through to people is when they are in a boot loop they get in a hurry and start factory resetting and that is not always the best option. Depending on exactly what is going on. Most of the time it is people losing their ADB access and cannot figure out how to uninstall the MTP drivers first then install the ADB drivers..
Good job getting your device back online and thank you very much for the closing write up .
mkid89 said:
Ok! Now that I have a fresh mind I can document the steps I took to correct this issue.
How did this happen to begin with? I think that when I tried to set a custom launcher as default using KindleFree Pro, the launcher I selected was unable to load properly or something interrupted the process. Either way, it either would only load to the lock screen or just sit on the boot animation. I'm thinking the way that KindleFree works is that it replaces the default launcher apk with a link that points to the launcher you want to replace it with (hence the 0kb size). Either that or something got corrupted during the process of changing the launcher. I'm not sure what KindleFree does behind the scenes so this is all just speculation.
Anyways, on to the good stuff. Once I noticed the launcher was 0kb, thats where I decided to direct my troubleshooting efforts. I posted this thread hoping someone would upload the stock launcher for me to replace it with but jimyv gave me the idea to just grab it from the bin. I ended up finding the bin file here: http://www.amazon.com/gp/help/customer/display.html?nodeId=201357190 before he replied with the direct link. The "Download Software Update" link is a direct link to the .bin file. I changed the extension, opened it up and found the launcher apk per jimyv's suggestion.
Once I had the file, I needed to get it onto the HDX. I more or less followed the instructions here: http://forum.xda-developers.com/showthread.php?t=2588608
Instead of replacing the odex files, I replaced the launcher apk under /system/app/ As soon as it had finished copying over, the device went from the boot splash screen to the lock screen in what can only be described as a magical moment.
Interesting to note: Most people say that if you perform a factory reset from the stock recovery, your hopes of using ADB and having root are gone unless you get a factory/fastboot cable. I actually did perform a factory reset but for some reason was still able to use ADB and did not lose root access. I had used TowelRoot to root the device so I'm wondering if that is a more permanent means of rooting compared to other methods? Either way, I'm glad I didn't lose root. Otherwise I would have needed to wait for a factory cable to be shipped and to root it via ADB.
Click to expand...
Click to collapse
could i use this way to fix my fault at this link bro?
http://forum.xda-developers.com/kin...p-kindle-fire-hdx-8-9-doesnt-able-to-t2816663
I took a look. That's a totally different issue than my issue. Mine wasn't getting stuck on the recovery screen. Sorry.
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
Is there any lolipop custom rom available on here for mediapad youth 2 s7-721w
Ive tried the links online , but I cant get past the ads even with inputting valid info
Please help me. Im looking everywhere with no luck, and my current system is wrecked
thanks
dermot31 said:
Is there any lolipop custom rom available on here for mediapad youth 2 s7-721w
Ive tried the links online , but I cant get past the ads even with inputting valid info
Please help me. Im looking everywhere with no luck, and my current system is wrecked
thanks
Click to expand...
Click to collapse
I have seen several links that "claim" to be custom Lollipop roms for the mediapad. However, as you had already noticed its all garbage ad links.
The good news is there are guides on youTube to get past all that junk (I tried it myself and it worked). I forgot which provider I used to give you exact instructions, but try a search on YouTube
The bad news is any lollipop rom for mediapad is "at best", some custom one with questionable legitimacy. I'd say avoid it for now. Adding insult to injury the general public worldwide isn't lining up outside stores for Medipad devices, much less Huawei in general, so Huawei has very little motivation to push out lollipop on Mediapads.
Also on a final note, a lot of these links for custom roms may come preloaded with malware that will not ask you for permission but take over your machine.
I strongly urge you to stay as is. Any benefits provided by lollipop over Kitkat are not worth the risk involved.
The Mediapad x2 was recently announced, so you may want to hold off and see what Huawei does
Sorry i couldn't be of more help.
shassouneh said:
I have seen several links that "claim" to be custom Lollipop roms for the mediapad. However, as you had already noticed its all garbage ad links.
The good news is there are guides on youTube to get past all that junk (I tried it myself and it worked). I forgot which provider I used to give you exact instructions, but try a search on YouTube
The bad news is any lollipop rom for mediapad is "at best", some custom one with questionable legitimacy. I'd say avoid it for now. Adding insult to injury the general public worldwide isn't lining up outside stores for Medipad devices, much less Huawei in general, so Huawei has very little motivation to push out lollipop on Mediapads.
Also on a final note, a lot of these links for custom roms may come preloaded with malware that will not ask you for permission but take over your machine.
I strongly urge you to stay as is. Any benefits provided by lollipop over Kitkat are not worth the risk involved.
The Mediapad x2 was recently announced, so you may want to hold off and see what Huawei does
Sorry i couldn't be of more help.
Click to expand...
Click to collapse
Thanks for the reply, I think you've confirmed what I already thought. I think Ill steer clear. I was only considering them as an option because Im not sure what else I can do with the tablet. I have bought it a couple of weeks ago for college. to test some apps Im working on.. The jelly ban 4.3 OS on it isnt too bad. I was quite happy with it up until lately. I think Ive messed up the gps on it somehow as one of my apps uses it and which I need in order for the app to work. Ive tried resetting the device, but this doesnt help.
Perhaps you could advise me further. I downloaded an official update file from huawei in the form of update.APP. I believe if I could start fresh with this,(completely refresh my system), the problem might go away. The problem is that none of the android recovery apps recognize this format( .APP). Ive tried changing the extension to .zip, but no joy.
Maybe there are some other alternatives, you mentioned kitkat,, and whats next with Mediapad x2.
Is it possible for me to take an update meant for another huawei device. Wouldn't this screw up my tablet.?
Thanks for your help. I just need something to completely refresh my system. I think if i could refresh it using the update.APP file id be sorted, but anything will do at this stage
General Tips
dermot31 said:
Thanks for the reply, I think you've confirmed what I already thought. I think Ill steer clear. I was only considering them as an option because Im not sure what else I can do with the tablet. I have bought it a couple of weeks ago for college. to test some apps Im working on.. The jelly ban 4.3 OS on it isnt too bad. I was quite happy with it up until lately. I think Ive messed up the gps on it somehow as one of my apps uses it and which I need in order for the app to work. Ive tried resetting the device, but this doesnt help.
Perhaps you could advise me further. I downloaded an official update file from huawei in the form of update.APP. I believe if I could start fresh with this,(completely refresh my system), the problem might go away. The problem is that none of the android recovery apps recognize this format( .APP). Ive tried changing the extension to .zip, but no joy.
Maybe there are some other alternatives, you mentioned kitkat,, and whats next with Mediapad x2.
Is it possible for me to take an update meant for another huawei device. Wouldn't this screw up my tablet.?
Thanks for your help. I just need something to completely refresh my system. I think if i could refresh it using the update.APP file id be sorted, but anything will do at this stage
Click to expand...
Click to collapse
I don't have any idea what an APP file is, so I cannot attest to how (if at all) it would work. Also, the device I have is the Mediapad (honor) X1, which is technically a different device than yours, but there was an OTA update to KitKat (4.4.2) which i installed.
Also, NEVER EVER EVER (DID I ALREADY SAY EVER) TAKE AN UPDATE MEANT FOR A DIFFERENT DEVICE. To give you an idea how serious I am I wouldn't even take an update designed for the 3G-only version of my mediapad (even though it would be very close, if not identical, software). This is an almost guaranteed way to (at best) render your device useless until you flash back to a working rom, or (at worst) permanently brick your device. Follow the golden rule of thumb: If in doubt, steer clear - better safe than sorry
Try the following, in order:
The steps below are very generic, and you probably already know most, if not all, of them, but it never hurts to post them here just in case some other person reads this thread and benefits from it.
1.) Backup any data you care about (this goes without saying, but just in case). Don't forget contacts, bookmarks, photos, music, etc
2.) Check for an OTA update (Settings --> About Phone or Settings --> Updater (depending on your device and OS). If there's anything, install it, reboot, etc. You may have to do this 2 or 3 times to get fully updated.
3.) Now you're ready to roll back. (Settings --> Backup & reset --> Factory data reset)
4.) The very first thing you should do at this point is to check to see if everything is working right. Don't bother setting up your phone/tablet just yet! Check to see if the GPS issue is fixed. If all is well, you can proceed to step 5
5.) Assuming you're good to go after step 4, you may want to familiarize yourself with loading up google services on your phone/tablet by glancing at
a.) This post
b.) my other thread
Don't forget that my device is different than yours, so be very cautious before you do anything!
6.) Set up your phone/tablet the way you like
7.) Optional but highly recommended: Perform a full phone/tablet backup. I have never done this myself, so I cannot walk you through this. But search here on XDA and on google for "NAND phone backup" and do some reading This will help you get back into a working state if you dink around with your phone/tablet and screw things up again.
8.) Optional but highly recommended: Search here on XDA for a "stock" ROM specific to your device. This would come in handy if all else fails and you want to force your phone/tablet back to the way it was as shipped off the factory line. Its probably a good idea to hang on to that file anyways. You never know when you want to restore everything to factory settings if you want to return the device for warranty, or if you want to gift it or sell it
Best of luck
In short, the best advice Captain Obvious can give you is READ, Re-ead, Re-re-read, and google like crazy before you do anything
Thanks for the reply, but I think I can manage a basic reset of my device