yashsingh1/xdaforums huggingface dataset:
[EVO 4G Q&A, Help & Troubleshooting] Kotetsukun:
Help! NFS Most Wanted crashed after the EA screen. I logged on to Origin and it worked one time, but when I start it again, that happened.

Please help. Fix it. Anyway out of this? It always crashes I try to re-install again but it doesn't work. Mine is the modded version from htcsense aptoide. Hope it doesn't involve "freeing up space and trying again."
[EVO 4G Q&A, Help & Troubleshooting] joker705:
I am getting the same problem,either the app crashes or the phone hangs...pls post a solution asap....currently on resurrection remix 4.2.2..:cowboy:
[EVO 4G Q&A, Help & Troubleshooting] prboy1969:
Have you tried Wiping Caches, and Fixing Permissions ?
[EVO 4G Q&A, Help & Troubleshooting] Robbie5:
Anyone found a solution for this ? :(
[EVO 4G Q&A, Help & Troubleshooting] Abrar_x:
https://play.google.com/store/apps/details?id=com.stericson.permissionfix&hl=en

I used this app to fix the permission and the game ran ...
[EVO 4G Q&A, Help & Troubleshooting] akashbanaulikar@gmail.com:
solved

U have to just to do is off ur screen rotation or if it does not work then when a ea loho appears and and gqme is about to stop then just minimize game reopen then it will definately work.
[Galaxy Note 3 Q&A, Help & Troubleshooting] easygoingx:
Hello,

I just got the Note 3 (no root, everything stock) and I come from the Note 2. I feel like that the battery is being drained so much than with the Note 2. Is it because of all the updates? I turned off Google Now and I use the Note 3 on Power Save Mode and kinda low brightness. It's been 13h since my last charge and I only have 41% left with 2,5h screen time. That is so weird!

Help?
[Galaxy Note 3 Q&A, Help & Troubleshooting] sohebq:
Try bbs. No one can judge this way. Google services eats a lot of battery.

Sent from Note 3 (The beauty & beast)
[Galaxy Note 3 Q&A, Help & Troubleshooting] easygoingx:
What is BBS? How can I turn off Google Services? They make up 15% of my battery drain..
[Galaxy Note 3 Q&A, Help & Troubleshooting] jaythenut:
Get wakelock detector From Google play that will show you what is draining the battery
[Android Q&A, Help & Troubleshooting] comstar:
So I picked up this tablet at MicroCenter. Not bad for $40. Not a lot of features, but I knew that going in. Nice that it has 4.2.2 and the Play Store works like it should!

I wanted to start a general thread to keep up to date on any recoveries, fixes or ROM's people come across.

I used this method to root http://www.cydiaimpactor.com/ it worked the first try. I had to do it on an old XP machine because my Windows 8 would not load the right Android drivers. See posts below for another method.

Please post any additional information you may have on this tablet. Let's see if we can make the most out of our $40!

A special thanks to BLuFeNiX for jump starting this whole thread with his knowledge, CWM recovery and stock NANDs, and for taking time to gather all the info into a useful post.

Also thanks to extreme tester dsulliii for the willingness to sacrifice his tablet in the name of science and for all his insight and help.

Don't forget to hit the thanks button for them !!!!!
[Android Q&A, Help & Troubleshooting] ranchdude:
We'll see

After my 1st round of "what's it gonna take to root this". And I do a appreciate a fairly slim JB dist. But I think this lil guy could use a few tweaks here and there.

I'm leaning towards "Kingo Root" for simplicity's sake. Or, "Cydia Impactor" Honestly though, I'm prolly too busy to spend the interrupted time to do a root for a bit. So I'll just check in and see what's up. GMTA ComStart. Thanks!
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Well, the device is already rooted over ADB. You just need to shell in and replace the su binary with one that doesn't restrict user apps from gaining root.
[Android Q&A, Help & Troubleshooting] dsulliii:
Getting back to stock

I'm a neophyte, so I bought this one knowing that if I broke it (which I most likely would -- and did), then I wouldn't be out a whole lot of money. My experiences in learning so far with these A13s is that they're practically un-brickable... once you ruin them, there always seems to be a way to get back on track. So after messing this one up, I was again surprised that all was not lost. I found an ICS ROM that did install using LiveSuit, and it's back up and running again. Only problem is... it was a very nice, slick little JellyBean 4.2 machine before I messed it up. I'd love to get it back to where it was before I messed it up (like I've been able to with other A13s), but ran into an unexpected impasse... CWM Recovery.

The way I got back to installed-version before was by installing a workable ROM then using CWM Recovery to copy ROM-dump files that I pulled prior to messing around back into it. Well, unbeknownst to me, THIS one doesn't have a CWM Recovery yet. And developing one is way beyond my abilities at this point... I am totally relying on you-all with way-more experience than me.

When I went to the Azpen support site, the only ROM they have is allegedly an A700/A701. THAT one doesn't flash using LiveSuit. It errors out at the beginning. So I'm guessing that Azpen support isn't up-to-date yet. I wrote to them, but haven't heard back. I really want to be able to reset it back to its original flashed ROM. Without CWM Recovery, my expected plan for restoration kind of croaked.

So here's my question.... do any of you know of an original ROM that I can get my mitts on that WILL indeed flash to this Azpen A700? I'd love to get its original JellyBean 4.2 working on it again. PLUS... the ICS ROM that DID work in it makes it a different signature... I want it to be an Azpen A700 again.

I know... asking lots and contributing nothing. I'd be thrilled to help anybody gain the same victory that I did with the Mach Speed Trio Stealth 7c A13b if they're having trouble -- in return. Just a hobby of mine, but I hope to someday be good like ya'll.

David
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
I can send you a CWM build that might work. I've been working on one. I make no promises though. My last 2 builds bricked and I had to return the tablet for a new one. I suppose you won't be in any worse of a place though, since you found a working livesuit image. Can you send me a link to the livesuit image? I haven't found a working one yet.

So, let me know if you want me to send my possibly-working CWM build.
[Android Q&A, Help & Troubleshooting] dsulliii:
Ya know what, BluFeNiX? I think that would be wonderful. I'm a perfect "test" person for you because I can put mine back the way it is. I'd love to be instrumental in helping to get a CWM working for it.

I don't know HOW you would send it to me though. All I've ever observed here is links within posts. Is that what you would do? Or do you need an e-mail address or something? I'm pretty thrilled to give 'er a try!

---------- Post added at 07:43 PM ---------- Previous post was at 07:25 PM ----------

PS -- as soon as I re-find that link, I'll post it for you.

---------- Post added at 08:17 PM ---------- Previous post was at 07:43 PM ----------

_______________________________________________________________________________

Okay, I found it at:

(Just discovered that I'm not experienced on the site enough to post links yet.)

It's on a dot-com site called moveontechnology, and it's by hugoenchina with a page id of 220. It's in Spanish.

Maybe you can use some of this info to locate it on Google Search since I can't post the link.

(I used Google Chrome so that I could translate the page from Spanish to English)

Then find the section just a little down the page:

************************************************** **

TABLETS FIRMWARES A13 CPU BOARD BEGINS WITH INET XXX, eg Inet 86vs

(A13) (86VS-M758C1) (CPT-OR-SKYRAINBOW-H070D-12AY-50PIN-800X480) (BLOGHUGOENCHINA) 20130725. Zip "inform me also works in denver electronics TAC-70051" and the Mitsui model MID7104SC

Although the ICS ROM above works, do NOT use it. It incorrectly partitions the device

(A13) (86V-M758B) (CPT-FTG700D3-50PIN-800X480) (TOUCH-NOPLANO) (BLOGHUGOENCHINA) 20130725. Zip

(A13) (86V-M729) (CPT-LT70009-40PIN-800X480) (BLOGHUGOENCHINA) 20130725.zip

(A13) (86V-M758A) (CPT-FTG700D3-50PIN-800X480) (TOUCH-UP) (BLOGHUGOENCHINA) 20130725.zip

************************************************** **

As you can see, I downloaded the first one. I don't know whether the other three work or not because this one works great, although it's ICS.

If you click on that first one, it will give you another link that I can't post on depositfiles.

The actual file is mus464gwg.

Then using Azpen's LiveSuit A701.exe, after extracting the "img" out of the "zip", this "img" works.

Although the ICS ROM below works, do NOT use it. It incorrectly partitions the device

(A13)(86VS-M758C1)(CPT-OR-SKYRAINBOW-H070D-12AY-50PIN-800X480)(BLOGHUGOENCHINA).20130725.zip

(A13)(86VS-M758C1)(CPT-OR-SKYRAINBOW-H070D-12AY-50PIN-800X480)(BLOGHUGOENCHINA).20130725.img
[Android Q&A, Help & Troubleshooting] comstar:
I just read through your reddit thread here http://www.reddit.com/r/androiddev/comments/1qt0tk/can_anyone_help_me_build_a_cwm_recovery_for_the/ - great job! Looks like you are making some progress. I also saw the cyanogen thread where the guy took his tablet apart to take some pictures. Can't miss the big Allwinner A13 chip.
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Great, thanks for testing for me! Here are the links:

CWM build 1

CWM build 2

I have included 2 builds for you to test. They both contain the same software, but I packaged them slightly differently. I'm pretty new to building stuff for android devices, so I might need a few tries before I make a successful build. Try #1 first by booting into recovery and selecting "install zip fro SD card" or something like that. If #1 doesn't work, try #2 and let me know which one worked.

If anything isn't clear, let me know and I can explain further. Thank you so much for testing for me!
[Android Q&A, Help & Troubleshooting] dsulliii:
CWM build 1

__________________________________________________________________

Currently running the (A13)(86VS-M758C1)(CPT-OR-SKYRAINBOW-H070D-12AY-50PIN-800X480)(BLOGHUGOENCHINA).20130725.img ROM on Azpen A700.

1) Currently running actively from the desktop and selecting SystemSettings-->Backup&Reset-->RecoveryMode-->Ok. (Wait for shutdown & restart)

2) Started into "Android system recovery <3e>". Where "Android system recovery utility (EVB: vol up/vol down, home, enter)" prompt has following options:

reboot system now

apply update from external storage

wipe data/factory reset

wipe cache partition

apply update from cache

3) Had copied cwm6028-a700-text.zip to internal SD card, and it does indeed list in "apply update from external storage". Seems that some folks should get some consistency between the meaning of "internal" and "external". But that's neither here nor there. So I am selecting your zip file after volume-downing to it and pressing the power button to select...

RESULTS:

-- Install /sdcard ...

Finding update package...

Opening update package...

Verifying update package...

E:failed to verify whole-file signature

E:signature verification failed

Installation aborted.

4) So now i will "reboot system now" and ensure that nothing detrimental occurred....

YEP -- No problem! Device still not bricked, so that's good for me.

The ball's still in your court on this one (that was still fun, nevertheless, thanks.)

-- David

---------- Post added at 09:00 AM ---------- Previous post was at 08:47 AM ----------

_________________________

Title: CWM build 2

Everything same as before, but this time it is "cwm6028-a700-test2.zip" that I have selected to install.

Results:

-- Install /sdcard ...

Finding update package...

Opening update package...

Verifying update package...

E:failed to verify whole-file signature

E:signature verification failed

Installation aborted.

(Still exciting though... getting to watch the status bar increase to about 5% before failing.)

Looking forward to the next hurdle. COOL!
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Ah, okay! I just have to re-sign the zip file. I'll send you some resigned builds shortly. :D
[Android Q&A, Help & Troubleshooting] dsulliii:
Happy Thanksgiving

Excited to try it again. But the wife and I are about to take off across town to the oldest son's home for the Holiday feast. I may-or-may-not get to it before the day is out, but I'm going to be chomping at the bit to get home and give it another try. It's 11:30am here (Mountain time). Later, thanks, and Happy Thanksgiving! :cowboy:
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Hey, no problem. Have a happy Thanksgiving! Here are the new (hopefully correctly-signed) zips:

Signed zip test 1

Signed zip test 2

Looking forward to hearing the results!
[Android Q&A, Help & Troubleshooting] dsulliii:
Hey BLuFeNiX, I was fortunate to connect to xda on my son's wi-fi and download your new ones. They both failed signature verification again. He's interested as well, so we can probably keep plugging away at this through the day. -- David
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Okay. Let's try this a different way. Is your tablet rooted? if so, please install Android Terminal Emulator from the Play Store.

Also, copy these img files to your internal sdcard:

Image test 1

Image test 2

Open the terminal emulator, and type the following commands:

su
dd if=/sdcard/recovery-TEST.img of=/dev/block/nandg
sync
reboot recovery

This will flash the recovery directly from Android instead of having to boot into recovery. If the first one doesn't work, you can try the second one. If we are successful, you should boot into CWM. If not, you'll probably need to flash using livesuit again.

If you are not rooted (you will get an error when you use the "su" command), let me know and I will tell you how to obtain root.

Good luck, and thanks again!
[Android Q&A, Help & Troubleshooting] dsulliii:
Yep, rooted, su worked okay in terminal, got the #.

Dowloaded okay, will try the dd flash. If it doesn't work and I have to reflash, won't be able to let you know until I get home tonight.

---------- Post added at 04:32 PM ---------- Previous post was at 03:39 PM ----------

Forgot my cell phone had Tap-a-talk on my cell phone. Interesting... reboot recovery from terminal rebooted system, but not recovery. So used settings app to reboot into recovery. When I did that, I got little colorful Andy who just stayed there and never went into recovery nor system. Forced a shutoff using the power button. Turned on... same freeze point. Forced power off again and tried to start recovery with volume and power. Same no-go. Only could try the first img since it's stuck. Will now have to wait till we get home then I"ll flash the ICS ROM and try your second img.

ADDENDUM: The problem that I had with not rebooting recovery from a shell command has gone away. I suspect that it might have something to do with the ICS ROM that I was using partitioning the device wrong. Make sure you use BLuFeNiX's modified ROM for proper A700 partitioning, and NOT the one that I recommended earlier in the thread.
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Interesting results. The second image loads the ramdisk from a different memory address, so hopefully the behavior you saw was what happens when an incorrect memory address is used. Maybe #2 is the correct one :)

Thanks again for doing all this testing.
[Android Q&A, Help & Troubleshooting] dsulliii:
Just looked over my posts from earlier. So VERY sorry about the spelling errors! I wasn't looking back to see the mis-predictions. I hate it when people do that. Anyway, on my way home now. Should be able to let you know about the second img in about an hour. (8:00pm mountain time).
[Android Q&A, Help & Troubleshooting] dsulliii:
Image test 2

_____________

Okay, I'm home now.

Before getting started, I restarted the A700 using the power button. It (again) did not progress beyond the teensy colorful Andy.

So I connected my USB cable to the computer and tried to ADB it.... ADB did not see it. I predicted it did not get any farther, but I just wanted to make sure and to let you know as well.

So I used LiveSuit A701.exe to flash the ICS "(A13)(86VS-M758C1)(CPT-OR-SKYRAINBOW-H070D-12AY-50PIN-800X480)(BLOGHUGOENCHINA).20130725.img" ROM again ... complete success as always.

After it powered up to the ICS desktop, I "ADB devices" which resulted positive. Followed by "ADB shell" whereupon I got the "#" indicating that this ROM comes rooted, it started in as superuser.

I copied your "recovery-TEST2.img" to the internal SDcard.

Went back into ADB Shell and at the # prompt typed:

su ' superfluous since already superuser

dd if=/sdcard/recovery-TEST2.img of=/dev/block/nandg

sync

reboot recovery

Again, the shell "reboot recovery" command did not reboot the recovery partition... it rebooted the system partition back into my ICS desktop.

So again I SystemSettings->Backup&Reset->RecoveryMode->Ok. And waited for it to power off and restart.

I got the small colorful Andy.... forever.... and again no sign of any additional advancing.

Still had the USB cable plugged in, so tried ADB devices again while it was sitting on Andy. No good, no ADB running.

Used the power button to force a power off.

After it powered off, waiting 30 seconds, I used the power button to turn it back on.

It displayed the colorful little Andy.... and didn't go anywhere still.

So I will re-flash the ICS ROM and wait for you to find some more magic.

Yeah, this is fun. THANKS BLuFeNiX. :good:

---------- Post added at 08:47 PM ---------- Previous post was at 08:15 PM ----------

More experimentation. I installed Uberizer's tollkit to have it perform the reboot into recovery. Identical to the shell's reboot recovery, it also reboots into the system. It appears that this ROM and the Azpen JellyBean 4.2 ROM must know something special about this tablet, eh?

ADDENDUM: The "reboot recovery" issue from a shell command has gone away. I believe that it was most likely caused by the ICS ROM that I was flashing -- having the device partitioned incorrectly.
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Alright, I am starting to run out of ideas. Try this build (use the dd method again):

CWM recovery test 3

If this one doesn't work, I'll need to spend some more time doing research. Thanks and good luck!
[Android Q&A, Help & Troubleshooting] thedarkfreak:
It would if it used the JB image. After flashing the JB image to my A701, it now shows the Azpen logo over both boot stages.
[Android Q&A, Help & Troubleshooting] JeffDenver:
I bought three of these and absolutely love them. Gave two as gifts to my brother and dad.

Vanilla Android JB for $40 = awesome. I am surprised as how quick they are for such a low specced device.
[Android Q&A, Help & Troubleshooting] dsulliii:
Azpen Support

Okay ya'll (specifically BLuFeNiX),

I finally have decided to throw in my two cents with Azpen support on this matter because I'm not learning ENOUGH by dissecting the .img files in the device to get a LiveSuit flashable ROM working yet. Maybe my voice might be the Merry-Christmas one, we'll see (although I doubt it based on the experience you have all dealt with so far.)

So... sharing:

_______________________________
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Nice. I hope they respond with something useful.
[Android Q&A, Help & Troubleshooting] mc00:
under windows 7/8/8.1 just disable unsigned drivers signature checker. That's how got the drivers installed.
[Android Q&A, Help & Troubleshooting] Raztan:
I see originally these ran ICS and then updated to JB.

That's impressive for a cheap tablet that they would update the OS.

I wonder if there is any chance we'll get a Kitkat firmware suppose to be some optimizations for low ram devices?

I must say for 40 bucks it's a pretty good tab and surprisingly snappy for what it is.

Only thing bad I can say about it is no OTG cable included and the screen is probably the worse viewing angles I've seen in a long time even among cheap tablets.

I got this one as a present for my sister (1st tablet) but Im tempted to get one for my self.
[Android Q&A, Help & Troubleshooting] dsulliii:
Yeah, Ratzan, I agree. I bought two different inexpensive 7-inch A13s at the same time. I adore them both. The other one (Trio Stealth) is ICS and was pretty easy to work with because there was an easily locatable donor ROM to base modifications on. This one, the Azpen A700, has been more elusive. Thanks to others, though, it is totally recoverable and from what I've seen, unbrickable. I'm finding it a joy to try to stretch it to its limits, but am quite frustrated at not being able to find LiveSuit-flashable ROM to learn more about modifying it from. There is the one ICS ROM that works extremely well once BLuFeNiX modified its partition tables to match this device's specifications, but I can't seem to to modify it with the JellyBean that comes with this tablet. Once modified, it doesn't seem to want to work -- and I haven't isolated the problem yet. WORKING on it though! <gr>...

Oops, that's not why I chimed in. I chimed in because I've been copying my since-1963 library of Doctor Who episodes to my Trio tablet and watching them exhaustively. LAST NIGHT... I decided to change boxes and use my A700 instead. And I DEFINITELY related with your statement about the viewing angles. I felt as though I had to keep shifting the position of the tablet in order to be able to focus on various parts of the videos. Kind of like parts of it on the edge get swallowed up inside of a dark box. So for video -- the Trio excels. Plus, the Trio already had a modifiable donor ROM to work with. But it's ICS, not JellyBean. I ADORE this little A700 though. WHAT A HEARTY little box!
[Android Q&A, Help & Troubleshooting] goingcrazy614:
Maybe one of you can check this thread out. Maybe it will help.

http://xdaforums.com/showthread.php?t=2562486