Related
How can I update to the latest 2.1.27 update on my Nabi 2? The Nabi is rooted and has TWRP as the recovery. Any help would be good! I have tried to flash a couple different Nabi 2 roms and they all fail. Thanks
toby1978 said:
How can I update to the latest 2.1.27 update on my Nabi 2? The Nabi is rooted and has TWRP as the recovery. Any help would be good! I have tried to flash a couple different Nabi 2 roms and they all fail. Thanks
Click to expand...
Click to collapse
I've got the same question. I know I'm an idiot that shouldn't have installed Gapps without having a clue, but unfortunately I did. I used the Victoria Antonio youtube video that says it does not root but does install Gapps about 4 months ago--May 2013. I'm now trying to figure out how to get the OTA update to 2.1, but I'm just lost, since it's been a while. I tried fooling around in TWRP, but again, didn't have any luck. Then idiotic me touched the square button in the upper right hand side of TWRP, and it is now stuck after saying:
*Verifying filesystem. . .
*Verifying partition sizes. . .
I know this is my own fault and I apologize, but I would really appreciate some help! Thanks so very much!
abbienormal said:
Then idiotic me touched the square button in the upper right hand side of TWRP, and it is now stuck after saying:
*Verifying filesystem. . .
*Verifying partition sizes. . .
I know this is my own fault and I apologize, but I would really appreciate some help! Thanks so very much!
Click to expand...
Click to collapse
That's just the log. You didn't do anything bad. Next time just press the button again and it will hide the log.
For both of you we need some more info, what have you tried so far? What methods and files are you trying to use to get to 2.1.27?
Thanks and sorry!
aicjofs said:
That's just the log. You didn't do anything bad. Next time just press the button again and it will hide the log.
For both of you we need some more info, what have you tried so far? What methods and files are you trying to use to get to 2.1.27?
Click to expand...
Click to collapse
Thanks so much for the reassurance. I did actually try to push the button aagin, but it wouldn't do anything, and after thinking I had bricked it for about a hour, I finally held down the volume -/+ and power buttons and got back to familiar territory. Sorry, again, for the completely idiotic question.
I haven't tried anything besides the standard order of operations suggested by Nabi. I downloaded the Nabi OTA software update (which took forever with our pokey internet), then clicked okay as it verified things, then it automatically rebooted with the little green Android guy with his chest open, then, unexpectedly, he's on his back dead with a red triangle sign above his chest. The tablet reboots by itself normally, and there are no changes from what I had before--none of the OTA update has taken effect. And, as a matter of fact, when I check for an update, again, (because it's still at the 2.0 release keys), low-and-behold, it detects an update and wants to download again.
I went through the process 4 times before giving up and checking with the Nabi support on FB. After troubleshooting a couple of things, they wanted to know if my Nabi 2 had ever been rooted. I shut-up then because I didn't want to be scolded, and because, of course, it's no longer under warranty if it's been rooted.
However, I got it second-hand, so I've got no warranty anyway, plus, according to the Victoria Antonio youtube video I followed, I didn't actually root it. With the teensy bit of knowledge I've got now, I'm kinda skeptical of that particular claim, but nevertheless, I still can't get it to update with the fancy new Nabi software, which I've been lusting after.
Any ideas? Obviously I'm clueless about tech lingo, so I would greatly appreciate a very simple explanation. Thanks so much for your time!!
abbienormal said:
Thanks so much for the reassurance. I did actually try to push the button aagin, but it wouldn't do anything, and after thinking I had bricked it for about a hour, I finally held down the volume -/+ and power buttons and got back to familiar territory. Sorry, again, for the completely idiotic question.
I haven't tried anything besides the standard order of operations suggested by Nabi. I downloaded the Nabi OTA software update (which took forever with our pokey internet), then clicked okay as it verified things, then it automatically rebooted with the little green Android guy with his chest open, then, unexpectedly, he's on his back dead with a red triangle sign above his chest. The tablet reboots by itself normally, and there are no changes from what I had before--none of the OTA update has taken effect. And, as a matter of fact, when I check for an update, again, (because it's still at the 2.0 release keys), low-and-behold, it detects an update and wants to download again.
I went through the process 4 times before giving up and checking with the Nabi support on FB. After troubleshooting a couple of things, they wanted to know if my Nabi 2 had ever been rooted. I shut-up then because I didn't want to be scolded, and because, of course, it's no longer under warranty if it's been rooted.
However, I got it second-hand, so I've got no warranty anyway, plus, according to the Victoria Antonio youtube video I followed, I didn't actually root it. With the teensy bit of knowledge I've got now, I'm kinda skeptical of that particular claim, but nevertheless, I still can't get it to update with the fancy new Nabi software, which I've been lusting after.
Any ideas? Obviously I'm clueless about tech lingo, so I would greatly appreciate a very simple explanation. Thanks so much for your time!!
Click to expand...
Click to collapse
If you followed any of the guides out there then you likely have gapps on your tablet(Google Play Store). If that is the case then it has modified/removed some system files. When the Nabi OTA does its thing in the "Android guy" screen(aka stock recovery) it finds files missing or modified and halts the OTA.
You have 2 options. 1) Use a modified OTA(that ignores those files), or
2) restore your backup you made during the Victoria video that has unmodified/removed files then do the OTA.
There is a caveat. The new 2.1.27 OTA uses up almost all the room on the system partition. Without removing something you cannot have a tablet with full gapps package and full Nabi 2.1.27 something will have to be deleted.
Start reading from post #1597 http://forum.xda-developers.com/showthread.php?t=1905674&highlight=nabi&page=160 it will make some more sense.
Update Nabi 2
I have no idea how I rooted the Nabi 2 tablet originally, but I know I did it because I wanted the Google Play store. I am now unable to get the update and the people at Nabi are asking if I have the Play store - I'm pretty sure they are asking this because there is some sort of issue with the update and rooted tablet. If anyone is willing to explain and work with me on this, I would greatly appreciate it!
rozibaby84 said:
I have no idea how I rooted the Nabi 2 tablet originally, but I know I did it because I wanted the Google Play store. I am now unable to get the update and the people at Nabi are asking if I have the Play store - I'm pretty sure they are asking this because there is some sort of issue with the update and rooted tablet. If anyone is willing to explain and work with me on this, I would greatly appreciate it!
Click to expand...
Click to collapse
Assuming you are on 2.0 right now?(2.0.5)? I'm going to base my description on that, if it's 1.9.37 or less there would be other steps.
If so you have a couple of options. I don't know which method you used to get playstore so it's a bit harder. There are 2 questions that you need to answer for yourself. Do you want Wings or the Playstore? Because as of right now it's difficult to fit them both on, and while we kind of have a method using symlinks it's not perfect yet.
So if you want to update and keep the playstore the first thing you need to do is figure out if you have TWRP installed(probably best to have version 2.6.1.0). WIth tablet powered off press and hold the vol+ and power key, navigate with the vol- key to recovery kernel and vol+ to select. If it boots to TWRP you can go on, if it boots to an Android guy you need to install TWRP. Once you have TWRP. MAKE A BACKUP! You can delete it later if you choose but make one now so you can get back to where you are if something goes wrong. I would use external SD for all of this because these are some big files.
After you have done that you can try to do this:
Download these
https://docs.google.com/file/d/0B024tOntNFbbaFJHcFRBRjVMUXc/edit?usp=sharing
http://home.comcast.net/~aicjofs/205to210libfix.zip
Copy them to the Nabi.
Boot in to TWRP and "install" both of these. You should be at 2.1 with Playstore and no Wings(You will still have one Wings app)
OR
You can restore a stock 2.1 if the above doesn't work
Download this:
https://docs.google.com/file/d/0B024tOntNFbbX1liUGN5eVU4UU0/edit?usp=sharing
Extract boot.emmc.win, system.ext4.win from the zip in to the TWRP folder on the device to internal storage(may not have room)
TWRP/BACKUPS/%serial%/2127
Or external SDcard
TWRP/BACKUPS/%serial%/2127
you will have to create the 2127 folder, and possibly the others(if you made a backup some of this will exist already) %serial% = whatever your device serial number is it's different for everyone.
Then boot to TWRP and "restore" checking boot and system only. Don't select data(it shouldn't be an option if you didn't copy data.ext4.win from the zip anyway)
This would leave you at 2.1.27 with Wings but no playstore. You can root it at that point but not install the Playstore unless you then deleted Wings.
The Product Version on the Nabi 2 tablet is 1.9.37. I am assuming that is what you were referring to when you asked if I was on 2.0 right now. I don't really care if I have the Play store or not anymore. At this point, I just want to be able to get the Nabi update and see if it addresses some of the other issues that I am having. I think that I made a huge mistake in doing all of this since I do not actually know what I am doing. I think the only reason why I got the Play store was for one specific game and I don't even remember what that game was anymore, so she will be ok without it.
I do not really understand what TWRP or anything like that is. Is there an easy way to just get rid of everything and pretty much start from scratch so that I can get the updates like normal? I know that the factory reset doesn't get rid of the rooting, unfortunately.
I am really grateful for your help! Thank you!
Error in /external_sdcard/...
I am not sure why I am getting his but I have tried every version of the Nabi2 ROM stock and custom 2.0.5 and above. It seems that I can only install previous versions to 2.0.5.
I have TWRP v2.3.3.0 installed and I am trying to get the latest 2127OTA build installed. If I revert back to stock ROM it boots fine but there a few odd going ons. One it always defaults to Mommy Mode even though I select Daddy Mode. WiFi never works even with WiFi fix. Tap sound does not turn off even though I selected to turn it off.
At this point I am fine going back to a full working stock mode as long as I will be able to get the latest OTA of the web or a working 2127OTA build.
Please advise,
Niles
Hi, I have a similar upgrading problem with the Fuhu Nabi .
I am on version "1.9.37-release-keys" with TWRP 2.6 installed.
I am happy with the process of booting into TWRP, adb push etc
I just cannot get any of the updates to succeed, at the moment they all fail at the start of installation with a "assert failed: apply_patch_check("/system/app/ApplicationsProvider.apk", [and then what I'm guessing is a checksum]").
I guess this means I'm trying to apply the patch to the wrong version of current system.
I wonder if someone would be able to spell out a recommended upgrade path from 19.37 to 2.10 (possibly this would require upgrading to 2.05 as a an intermediate step)
Marcus
marcusbaw said:
Hi, I have a similar upgrading problem with the Fuhu Nabi .
I am on version "1.9.37-release-keys" with TWRP 2.6 installed.
I am happy with the process of booting into TWRP, adb push etc
I just cannot get any of the updates to succeed, at the moment they all fail at the start of installation with a "assert failed: apply_patch_check("/system/app/ApplicationsProvider.apk", [and then what I'm guessing is a checksum]").
I guess this means I'm trying to apply the patch to the wrong version of current system.
I wonder if someone would be able to spell out a recommended upgrade path from 19.37 to 2.10 (possibly this would require upgrading to 2.05 as a an intermediate step)
Marcus
Click to expand...
Click to collapse
I have upgraded to the latest TWRP, 2.7, on my Nabi2 and was able to upgrade to 2.05, but I am still not able to upgrade to 2.10. Same error. Obviously some one was successful or they would not post the 2.10 file. Please advise.
Not sure if it will work for everyone, but....
Not sure if it will work for everyone, but after much fooling around with TWRP and the OTA update not working, I restored the backup I had made when I first rooted the nabi earlier this year, once it was done it booted into the standard nabi mode, when I logged into Daddy mode the Play store and all my root apps were gone, but I was able to install the 2.1 update that brings Wings university, and once that was installed, I then searched for updates again and it showed nabi 2 Over-the-Air Update v.2.3 (Part 1) which officially adds the Play store to the nabi 2, after that installed, I again went into Daddy mode and searched once more for updates and found nabi 2 Over-The-Air Update v.2.3 (Part 2) (which add Google Services (bloatware, honestly) and upgrades the OS to 4.1 Jelly Bean), and installed that as well. I haven't decided whether or not to re-root it, but I don't think I will, simply because there's really no need to root it anymore, since the Google Apps are there officially now. I hope this helps alot of people, since I wasn't able to find any info myself on the process, and discovered it through trial-and-error:highfive:.
How to Restore Backup?
78cherokeechief said:
Not sure if it will work for everyone, but after much fooling around with TWRP and the OTA update not working, I restored the backup I had made when I first rooted the nabi earlier this year, once it was done it booted into the standard nabi mode, when I logged into Daddy mode the Play store and all my root apps were gone, but I was able to install the 2.1 update that brings Wings university, and once that was installed, I then searched for updates again and it showed nabi 2 Over-the-Air Update v.2.3 (Part 1) which officially adds the Play store to the nabi 2, after that installed, I again went into Daddy mode and searched once more for updates and found nabi 2 Over-The-Air Update v.2.3 (Part 2) (which add Google Services (bloatware, honestly) and upgrades the OS to 4.1 Jelly Bean), and installed that as well. I haven't decided whether or not to re-root it, but I don't think I will, simply because there's really no need to root it anymore, since the Google Apps are there officially now. I hope this helps alot of people, since I wasn't able to find any info myself on the process, and discovered it through trial-and-error:highfive:.
Click to expand...
Click to collapse
How do I locate the backup file to restore it? I am hoping that I saved everything on my computer at home. I really just want to get rid of everything that I did to get access to the Google Play Store. I regret ever messing with it to begin with. I am trying to update my daughter's tablet, but it won't let me bc of whatever I did to get the Google Play Store about a year ago. I am almost 100% sure that I used the video by Victoria Antonio to root the tablet originally. If you are able to explain this process to me to fix it, I would greatly appreciate it. I like to think of myself as being pretty computer intelligent, but this was a big mistake!
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
Hi,
My HDX 7" was bought last year and I immediately found a thread about SafeTrap recovery, so that I could flash a custom ROM to my HDX 7" I followed the instructions carefully and it successfully worked
But then my friend borrowed it, he didn't know about the SafeTrap and seemed to wipe all of my ROM slots. He gave it back to me when the device was still on SafeTrap. I plugged it to my laptop and found that ADB was still working, tried to push a ROM to it, but I couldn't, the storage showed 0MB so it couldn't store the ROM files.
I decided to turn it off, and when turned on, SafeTrap was gone, my HDX showed Kindle Fire logo forever.
I knew that it was hard bricked and left it until now, I thought there would be a way to restore my HDX in the future
Is there anyway to bring it back again?
Or it will be bricked forever?
Thanks!
trungamox34 said:
Hi,
My HDX 7" was bought last year and I immediately found a thread about SafeTrap recovery, so that I could flash a custom ROM to my HDX 7" I followed the instructions carefully and it successfully worked
But then my friend borrowed it, he didn't know about the SafeTrap and seemed to wipe all of my ROM slots. He gave it back to me when the device was still on SafeTrap. I plugged it to my laptop and found that ADB was still working, tried to push a ROM to it, but I couldn't, the storage showed 0MB so it couldn't store the ROM files.
I decided to turn it off, and when turned on, SafeTrap was gone, my HDX showed Kindle Fire logo forever.
I knew that it was hard bricked and left it until now, I thought there would be a way to restore my HDX in the future
Is there anyway to bring it back again?
Or it will be bricked forever?
Thanks!
Click to expand...
Click to collapse
do you remember what firmware it was on?could he give you any insight into what he had done?did it have gapps with the xposed framework installed?
jimyv said:
do you remember what firmware it was on?could he give you any insight into what he had done?did it have gapps with the xposed framework installed?
Click to expand...
Click to collapse
I don't remember the firmware, I tried flashing another custom ROM, with some Gapps and no Xposed right after bringing it home I just wanted to make the experience like the general Android device with Google Play Store and services
trungamox34 said:
I don't remember the firmware, I tried flashing another custom ROM, with some Gapps and no Xposed right after bringing it home I just wanted to make the experience like the general Android device with Google Play Store and services
Click to expand...
Click to collapse
Not to be rude but first thing's first if anybody here is going to help you you're going to have to know details and exactly what you had prior to your current state .ie answer any questions with as much detail as possible . And if it all possible find out what they did to your device . If you cannot provide any of this .I cannot provide a help . I don't know anybody that has a crystal ball I can borrow LOL
The question was had you installed xposed framework on your stock slot?
What your original firmware was?
Then you might want to add exactly what rhomb you attempted to flash?
What error did it show. Can you or can you not still get into safestrap?
First guess though I would venture to say you have a paperweight and less you can get them to warrantee it for you. Personally I would have uninstalled safe strap recovery and lock root access out before I loan my device to anybody period but that's just me
ASUS MeMO Pad 8 (K011) ME181C Recovery Guide
The following is a list of what we can currently do with this tablet. It assumes firmware versions with the WW prefix (WW-3.1.23.1xx).
Root Status: Obtained
Bootloader: Locked
CWM Recovery Possible: Yes (Tethered)
Custom ROMS: None
The following information is for recovering your tablet and obtaining root only. The bootloader is locked on the device at this time.
Tethered CWM recovery
This is a temporary solution to unsigned loading. The bootloader on the device is currently locked, so after rebooting, it will revert back to standard recovery. Use this to restore to a stock firmware or to install SuperSU.
Download the official firmware and extract it.
Rename UL-K011-WW-3.1.23.172-user.zip to user.zip.
Copy user.zip to the root of your SD card.
Enable USB debugging on your tablet.
Run Launcher.bat.
Type ACCEPT.
Choose option T3.
This will reboot in to the Tethered Recovery.
Choose Install Zip from external SD card.
Choose user.zip
Reboot once finished.
Bootable Image for Recovery
This file is to be used if your system will not get past the Asus or Intel logo. Boot the system using Volume Up and Power. Once the logo appears, let go of power. Once in DroidBoot, use fast boot to flash the boot and system images. This is provided in case signature verification fails on the official images.
fastboot flash system system.img
fastboot flash boot boot.img
This file also contains adb and fastboot. If your tablet is not detected, try the Asus drivers.
Reboot the system and use the CWM tethered recovery to reinstall the official firmware.
OTA Updates
If you’ve recovered from the official firmware on the Asus site, you’re probably sitting at version WW-3.1.23.172. Here are the OTA updates to bring your system up to the current version of WW-3.1.23.189. There are two different OTA updates available here, so the process will need to be completed twice. Update 172 to 183 and Update 183 to 189.
Boot in to recovery, press the volume keys several times and install from ADB.
Extract the RAR file and rename the files update.zip.
On your PC, open a command prompt and change to the directory containing the update file
Assuming ADB is installed on the system, type: adb sideload update.zip
Once the process completes, reboot your system and update apps as needed.
Repeat this process for any additional update files.
Recovery image
This is the default recovery for the tablet. If you get adventurous and try to flash another one, this may come in handy.
can you explain
RemmyLee said:
All thanks to vampirefo for his work on this.
FB Tethered Recovery Launcher
Kind of curious if this method will work with the other versions of the tablet to allow SuperSU to be installed. Anyone want to try it?
Long story short, I screwed this thing messing with the framework. For some reason, the official firmware from the Asus site was failing signature verification when trying to reinstall. Someone managed to grab a stripped system image that at least gave me a launcher and USB debugging. This beauty allowed me to get the firmware installed and everything back to normal, as well as installing SuperSU.
If you have any trouble getting the tablet to show up in Windows, the Asus distributed drivers work like a charm.
Click to expand...
Click to collapse
can you explain in lamens terms or retard terms what this means you found? so me and others
as well can understand ? Please and thank you i have a ASUS MEMO Pad 8 Me181c Rooted With Frame1.4apk it took me to demo and i turned it off and rebooted and now it just goes to The ASUS Logo and then Intel Logo and Stops . If i could find a way to install CWM on this maybe i could get somewhere but all i see is people talking about it but no video tutorials , or walkthroughs
Any Help Would be greatly appreciated
1. https://cloud.mail.ru/public/2b47381cb37c/ADB.rar - This contains adb and fastboot if you don't already have them installed. This also contains the system image that we're going to use temporarily to get this thing restored.
2. Hook it up to your computer and load up Fastboot on the tablet (Volume+ and Power while booting. Let go of power after the logo shows up).
3. Flash the System image ( fastboot flash system system.img) followed by the boot image (fastboot flash boot boot.img)
4. Reboot.
5. https://www.androidfilehost.com/?fid=95857557620392052 - Next, we're going to use a temp version of CWM-Recovery to reinstall firmware. Enable USB debugging, run launcher.bat, type "ACCEPT" and choose T3.
6. You'll auto reboot into CWM-Recovery. Grab the official firmware from the Asus site and install the zip from SD. Once complete, you'll need to reroot the device most likely. If you have a SuperSU zip, install it after you've restored the system.
You're done. This also opens us up for just about anything. Go play with your system. As long as you don't mess up your boot loader, this should save you.
Sent from my K011 using XDA Free mobile app
Asus MeMo Pad 8 - Pro 7 Entertainment Pad
Hey guys,
I have a Asus MeMo Pad 8 - Pro 7 Entertainment Pad. Now the model is K011 and the firmware starts with LVL bla bla bla.
Technically it is the same as the 181C and I also have managed to achieve root. Any ide if I could get the WW firmware and rom working on this?
UPDATE:
Using this method gives you version 172 of the firmware. Current version is 189. So here are the OTA updates.
To use these files, Start up the system in Droidboot, Volume+ and Power, go to recovery. You'll be sitting a broken android robot screen. Press the volume keys several times. It's give you some options. We're going to install from adb.
Unrar the update file provided, rename the file to update.zip and sideload it to the tablet. Once it finishes, reboot and wait for the system to update. Rinse, lather, repeat for 183 to 189.
Files:
OTA update 172 to 183
OTA update 183 to 189
Note: This is only if the OTA updates aren't pushing to your device. If you've got them, you can skip this.
fulishone: If the intel tether works for you, you could always try it, but I have no idea if it would work or not. If you have your system backed up, you could always give it a go and restore if it fails.
I'll try to compile everything in to a more readable format later. I just want to get the info up right now. A lot of people were semi bricked either because of a root gone bad or file system problems.
shadow2483 said:
can you explain in lamens terms or retard terms what this means you found? so me and others
as well can understand ? Please and thank you i have a ASUS MEMO Pad 8 Me181c Rooted With Frame1.4apk it took me to demo and i turned it off and rebooted and now it just goes to The ASUS Logo and then Intel Logo and Stops . If i could find a way to install CWM on this maybe i could get somewhere but all i see is people talking about it but no video tutorials , or walkthroughs
Any Help Would be greatly appreciated
Click to expand...
Click to collapse
If you need any more help than whats above, let me know.
fulishone said:
Hey guys,
I have a Asus MeMo Pad 8 - Pro 7 Entertainment Pad. Now the model is K011 and the firmware starts with LVL bla bla bla.
Technically it is the same as the 181C and I also have managed to achieve root. Any ide if I could get the WW firmware and rom working on this?
Click to expand...
Click to collapse
To answer your question, yes. This will work. We have the same firmware for our devices.
http://www.asus.com/my/Tablets/ASUS_MeMO_Pad_ME181CX/HelpDesk_Download/
RemmyLee said:
To answer your question, yes. This will work. We have the same firmware for our devices.
http://www.asus.com/my/Tablets/ASUS_MeMO_Pad_ME181CX/HelpDesk_Download/
Click to expand...
Click to collapse
Ok, I am not new to flashing and custom roms and so on, but follwing your guide above, I should first flash .172 and then use your update files for .183 and the .189?
What do you mean with Intel thether?
Best regards
fulishone said:
Ok, I am not new to flashing and custom roms and so on, but follwing your guide above, I should first flash .172 and then use your update files for .183 and the .189?
What do you mean with Intel thether?
Best regards
Click to expand...
Click to collapse
Yep. That'll get you updated to the current firmware. I contacted ASUS yesterday and sadly, there are no plans on bringing Lollipop to this thing, nor are they interested in giving us an unlocked bootloader.
As for the Intel Tether, where the bootloader is locked, we can use a tethering method to access CWM recovery, but once we reboot, it reverts back to the standard recovery. This prevents us from using custom roms at this time. When it reboots, it checks signatures. The official firmware was not installing using the standard methods, so I used CWM to reinstall. That's why I included it above.
BBY builds
My guess is that this won't work with the BBY build. From what I understand no one has rooted an ME181C that has a BBY build. I also have not been able to connect the device to my PC. From reading this thread though it appears that to connect through the device drivers I need to boot into one of the recovery mode. Is that correct? I can see my sd cards okay when connected, but can't see the device through ABD.
et1ssgmiller said:
My guess is that this won't work with the BBY build. From what I understand no one has rooted an ME181C that has a BBY build. I also have not been able to connect the device to my PC. From reading this thread though it appears that to connect through the device drivers I need to boot into one of the recovery mode. Is that correct? I can see my sd cards okay when connected, but can't see the device through ABD.
Click to expand...
Click to collapse
I'm curious to know if the tethered method would allow a temporary CWM session to install SuperSU on the BBY line. I haven't seen anyone try it yet. If USB debugging is enabled, the tethered restore should try to automagically do everything for you. If you boot in to recovery, can you do a fastboot devices?
Can´t mount external sd card anymore
After using CWM tethered recovery to backup my rom, i cant mount my external sd card anymore. Any ideas?
Updates
RemmyLee said:
UPDATE:
Using this method gives you version 172 of the firmware. Current version is 189. So here are the OTA updates.
To use these files, Start up the system in Droidboot, Volume+ and Power, go to recovery. You'll be sitting a broken android robot screen. Press the volume keys several times. It's give you some options. We're going to install from adb.
Unrar the update file provided, rename the file to update.zip and sideload it to the tablet. Once it finishes, reboot and wait for the system to update. Rinse, lather, repeat for 183 to 189.
Files:
URLS removed to post
Note: This is only if the OTA updates aren't pushing to your device. If you've got them, you can skip this.
fulishone: If the intel tether works for you, you could always try it, but I have no idea if it would work or not. If you have your system backed up, you could always give it a go and restore if it fails.
I'll try to compile everything in to a more readable format later. I just want to get the info up right now. A lot of people were semi bricked either because of a root gone bad or file system problems.
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------------
Thanks for posting this. It helped recover my tablet to 172. I see 172 on ASUS's website, but not the updates, and my tablet says it's up to date. Can you advise what 183 and 189 provide? Any new features or enhanced stability or performance.
Thanks in advance. Very much appreciated.
tperki said:
---------------------------------------------------------------------------------------------------------
Thanks for posting this. It helped recover my tablet to 172. I see 172 on ASUS's website, but not the updates, and my tablet says it's up to date. Can you advise what 183 and 189 provide? Any new features or enhanced stability or performance.
Thanks in advance. Very much appreciated.
Click to expand...
Click to collapse
For some reason, OTA updates for this thing don't want to download. I've not seen too much of a change between them, but I applied them just to be current.
Success
RemmyLee said:
For some reason, OTA updates for this thing don't want to download. I've not seen too much of a change between them, but I applied them just to be current.
Click to expand...
Click to collapse
Yeah, strange that it won't update over the air. But thanks to your assistance I am running build 189. It may just be wishful thinking, but the device does seem a bit peppier. Thank you RemmyLee!!!!
[Update] Since updating to build 189, the device is much more stable and snappier. This was definitely worth doing. I don't understand why ASUS would not be pushing this out to everyone with this device.
Just wanna say thanks to the OP. Got my tablet back from the service center and was wondering why some apps were missing. Sure enough I was on WW...179. Nice to have updates and recoveries in one place. Great work!
Thank you so much bro, I have been googling a lot trying to find a root method and just discovered that I can easily have recovery and flash supersu zip thanks to you!!
Me181c not working...
Hi guys, I was using SoftKeyZ for about 2 weeks, I wanted to set my navigation buttons to it's default, so I tried using Backup of the SoftKeyZ, but when it rebooted the tablet, I lost my navigation buttons and indeed my notification and status bar. It rebooted again automatically, and this time when it started, I got an error which says: "Unfortunately, KeyguardTestActivity haas stopped", the error prevents me from unlocking the tablet and using it, so I cannot use it at all. I don't know how to go to recovery mode on my tablet, I used the button tips but it didn't work for me. I've downloaded the official rom from asus.com . Pleeeeeeeeeeeeeeeeeeeeeease, I need your help guys, you're my last chance...
should I do a complete wipe ?
Hi,
Thanks for the help in this thread.
I followed the instructions and successfully flashed the update firmware file. I was expecting for the tablet to be reset to original factory condition but found that all my apps ect were still there. I guess the user.zip is an update rather that a full ROM or should I have wiped everything first ?
I am have problems with the tablet such as Bluetooth has stopped working and wifi will only connect to very strong signal, (as in touching the router) which is why I wanted to completely wipe the device a start fresh.
f I wipe everything will the firmware file be able to restore the system fully?
Is there a complete firmware image file that can be downloaded any where ?
Thanks in advance for any advice
update : so fed up with no Bluetooth so I took the chance and did a full factory wipe and the system restored ok with the firmware file. Bluetooth problem solved, (Wifi did not, probably Hardware issue)
Thanks again
Signature failure
Thanks to your instructions, I've successfully managed to update my device to build WW-3.1.23.172, however, when trying to install 172 to 183 update I get a signature verification failure message.
Any ideas why this is happening?!
Alright XDA Community. I need some help. Desperately. So I had plans on rooting my tablet (TF201) to install a custom ROM. Being that I have version 4.1.1 installed I would looking for something a little newer and modern. That did not go as planned from the beginning. Since the first step was rooting it, I looked for a ROM. So I searched the web, including XDA and found KingRoot to root my device. Either KingRoot was a terrible choice or something did not go right with the process. Now when I turn on my device I get random pop ups for for stupid garbage that I don't want installed like What's App and UC News. Everything functions as it should but I get random messages that Settings stopped working. I get random apps being installed on a regular basis. I could be in an app and I get a blank / black box on top of something trying to open or install. This very frustrating and I am completely over my head now. So here is what I would love help with;
1. I would like to UNROOT my device to ALL stock settings and firmware. Completed
2. I would like to ROOT my device PROPERLY. Completed
3. I would like to install a custom ROM with Android 6.x or 7.x (Something plain and vanilla)
4. I would LOVE this help if at all possible in plain English Step by Step with pictures if possible. I would like it dummy proof.
Thank you very much for any and all help. It will be very much appreciated.
PS. I do not need to back anything up. It was a fresh reset recently and I do not have anything to backup.
Step 1 is complete. I used Kingo Root to UNROOT my device.
Step 2 is complete. I used Kingo Root to ROOT my device.
Have you unlocked the bootloader using the Asus supplied software?
NP
No. I downloaded it and installed it but when I go to run the APP it asks for my Google Credentials but it does not accept them. I use the credentials every day so I know my username and password but it does not work.
Delete you google account then run the bootloader unlocker again.
NP
Nektopoli said:
Delete you google account then run the bootloader unlocker again.
NP
Click to expand...
Click to collapse
Thank you very much. That did the trick. Here is the problem though. I think I am way over my head on this. I did a Davlik Wipe and a Factory Reset but there is something still not right. I did both a Dalvik wipe and Factory reset last night before bed. I did not touch it once complete but on a regular basis I get pop ups about Android System stopped working or UC News. I cannot get rid of either of these on my tablet.
Any idea what I can do?
Now that you have the BOOTLOADER unlocked next step is to ROOT the TF201, I used MOTOCHOPPER. Check out this thread;
https://forum.xda-developers.com/showthread.php?t=2230763
NP
That worked. I was able to Root my device without issue. Actually that was a great tool. Nice and easy to work with.
So here is my next stop. What ROM do I pick? I was looking at 6.x or 7. It looks like KatKiss is pretty good but I am not sure.
https://forum.xda-developers.com/transformer-prime/development/rom-katkiss-nougat-t3459313
No reason not to go straight to 7.1.2 just make sure you flash the correct TWRP.
NP
And this is the part I don't understand. I have downloaded TWRP and ROM Manager from ClockWork. I have copied the ZIP folder to my SD card and placed it in my TF201. From here I don't know what to do.
I follow the instruction from 5.1 here: https://forum.xda-developers.com/transformer-prime/development/rom-katkiss-5-1-tf201-22-t3080892
using the 7.1 files from here: https://forum.xda-developers.com/transformer-prime/development/rom-katkiss-nougat-t3459313
NP
Yeah. So now the tablet is stuck at the Asus Splash Screen. Been for the last 48 hours or so. I completely drained the battery but when I filled it back up, no difference.
Can you get into the TWRP recovery console?
NP
Nope. I can't do anything with it. I have power cycled it many times over holding different buttons but no difference.