yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
:laugh: That's great to hear! I was surprised how easy it was to edit the partition sizes once I found the appropriate tool (imgRePacker 2.04). I was worried that I would have to compile the text file into a binary or something, but all I did was edit the file, and run imgrepacker.

This is awesome! :D Now that this tablet is essentially unbrickable (assuming your dd goes well), I'm excited to try more experimental things. Maybe I'll release my first ever custom ROM?! This is so exciting!
[Android Q&A, Help & Troubleshooting] comstar:
Great work again guys, And a special thanks to you BLu !

I would usually jump right in and help test but I held off just in case you guys would need a good factory device to pull from. I would like to use your recovery. Is the last one you posted (v4) fine to load? Also it would be great to have a custom Rom for this device, let me know if there is anything I can help with,.
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Thanks :)

Yep, v4 is OK to load (it's what I'm using now). If you know anything about CWM, I'd love some advice on how to change the button mapping. Currently up/down are reversed. Also, if you know anything about signing update.zip files (to allow users to install CWM via zip after booting stock recovery), I can't get that to work either. I tried signing them with the "test" key, but I think stock recovery wants a specific key.

As for the custom ROM, I'll be sure to let you know if I need any testers.
[Android Q&A, Help & Troubleshooting] pscherry78:
Forgot to check the Build Number before loading the recovery-TEST4.img. What should it be after? I've got A13_86VZ_M758C2_1308112.20130914_1
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
I don't think flashing a recovery will affect the build number. That is only affected when flashing a ROM. For what it's worth, your build number is the same as mine :)
[Android Q&A, Help & Troubleshooting] dsulliii:
It's back to stock JellyBean ROM

Sorry I was out all day, Blu... had to do some shopping after we brought the dog back from the vet.

This is interesting:

I went ahead and dd'd all NANDs A-J (except for G, which is your CWM) from your img backup files. For the most part it seems to work. But it didn't finish. It got into a boot loop during the Azpen full-page logo.

I watched it over ADB in catlog for awhile, and it definitely seemed to be a single java exception causing it. I didn't freeze or save the catlog because I wanted to try out one theory first.

When Uberizer does a restore from a ROM backup, they don't DD the system and data partition, they tar it from a tgz.

I had made a Uberizer ROM dump before I started this which included NANDA, NANDB, NANDG and a tgz for system and a tgz for data. But it did not make any of the other partitions.

So to toss my theory into the mix, I ran the Uberizer's ROM dump restore on my own files. And, sure 'nuff, it did definitely tar the system and data tgzs rather than DD them as img files.

And... upon reboot, it came up. It came up exactly as it looked the day that I performed the ROM dump backup.

And since you resized the partitions properly, it means it came up perfect.

Yeah, I'm definitely exactly where I wanted to be. I'm just confused about the system and data partitions being tar'd.

I thank you again and again. I did not expect to gain the privilege of getting to be a part of something like this. Having seen you do it, I believe that I may now get a little braver and start toying around with the kitchen a small piece at a time to see what I can cook. I hope I don't break too much. But if I do, you've already gotten me out of the hot water and I can start from here again.

Thanks so much... ALWAYS!

-- David
[Android Q&A, Help & Troubleshooting] comstar:
Hey guys. I'm getting ready to flash the new recovery. I want to make a full image backup first. I've used Romdump in the past, what do you guys use? Or do you just command line it? What specific commands do you use?

Thanks
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Have you tried http://www.azpenpc.com/service/#download ?
[Android Q&A, Help & Troubleshooting] treecheetahdolo:
Yes ive download the Firmware for the Azpen A720 because there is none for the A727. So when I start LiveSuit and Load the image, Hold down Volume Down button while plugging in the Micro USB to the Tablet. I get an error message from LiveSuit saying "invalid Image". This is even before i have a chance to press the power button 10 times. So im basically getting this error message as soon as i plug in the microUSB plug.
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
There might not be an image for the A727 yet. It took them a while to make one for the A700/A701. You might have some luck emailing Azpen directly.
[Android Q&A, Help & Troubleshooting] treecheetahdolo:
Will do. Ill keep you updated.

---------- Post added at 03:54 PM ---------- Previous post was at 03:29 PM ----------

Before i Sent the email out i read something on Azpens site about firmware upgrade. I found out that I have an AllWinner so I downloaded PheonixUSBPro Via Azpens Site. I loaded the A720 Firmware with the Key provided by Azpen and Im getting and Illegal ID error any clues to why? I would think the A720 Firmware would work on a A727. Is it for the Series or a specific Model?

Also I came accross A site where a guy uploaded all his stock images for the A727 but its all nanda-nandj. I dont know how to use them. Any insight? Ive tryed loading them inside PheonixUSBPro but i cant even start it.
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
The A727 has an Allwinner A23 CPU, but the A720 has an A20 CPU. I do not think the firmware is compatible (hence the illegal ID error). Though, I can't do much more than speculate, since I do not own either device.

You can only use nand images if you can get ADB shell access, so if you are fully bricked, they won't help you.

Let me know what Azpen says, and if they can't help you, I will try to find something for you.
[Android Q&A, Help & Troubleshooting] treecheetahdolo:
So Azpen just sent me the firmware for the A727 i cant post the link though untill i get 10 posts. Im going to try it on PheonixProUSB and let you guys know how it went.

---------- Post added at 04:39 PM ---------- Previous post was at 04:27 PM ----------

So i tried to flash the firmware with PheonixUSBPro with the A727 firmware. And im still getting illegal ID. Its wierd,
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Try rebooting, and try a different version of LiveSuit. There's tons of version available if you google it.
[Android Q&A, Help & Troubleshooting] treecheetahdolo:
Something wierd happened. So i tried a different version of LiveSuit and got nothing. So i decided to give it another shot on PheonixUSBPro and guess what? It worked. My tablet came back to life.

What sucks is that the original reason why i was trying all this was because my camerea wasnt working out the box, lol. And its still not working.

Heres the link for the Azpen A727 Firmware if anyone finds it useful.

https://drive.google.com/file/d/0B53yZ1fbVqxJc2RYZEMxZUlYTjA/edit?usp=sharing

http://www.mediafire.com/download/qsyizhsactrgxuk/A727_12-29-13.img
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
LiveSuit USB drivers are loaded into memory when the program is run, so you may have made PheonixUSBPro use LiveSuit's drivers by running them in that order. You may want to remember what you did, in case you need to do it again.
[Android Q&A, Help & Troubleshooting] treecheetahdolo:
Hmm very interesting.

When I used PhoenixUSBPro it never had a problem detecting my device. I had first installed Google's SDK usb driver for Windows 7 to detect the tablet. But I guess thats possible. When I contacted Azpen about PhoenixUSBPro giving me that error message they said it shouldnt be happening. Id try to replicate it but i dont want to mess up this tablet anymore. Till i return it for one with a working camera. I have a feeling Im going to be toying around with it again. I might start a thread.
[Android Q&A, Help & Troubleshooting] Phlox49:
It's been a few months, and I'm once again fiddling with the same A701 tablet from before. Do you have anymore ideas with regard to getting CWM Recovery working without my "E:Can't mount /sdcard/" error? I noticed near the beginning of the thread that dsulliii's /proc/partitions disparity is very similar to mine. Might my problem have something to do with my partitions and not the CWM Recovery? Can my partitions be fixed without the use of my USB port? Can CWM Recovery be edited to comply?
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Unfortunately, you must use livesuit to fix partition sizes. I don't currently have any other ideas.
[Android Q&A, Help & Troubleshooting] Ermanaric:
a727 Tablet

My friend has an a727 he brought to me to work on rooted he obviously messed up and i had to fix it.

i noticed azpen's downloads section is kind of lacking when it comes to downloads and their mediafire's locked so..... i called azpenand spoke to a tech lady for a good hour i asked her if she had stock a727 image so i could fix my friends device she stated she did but didn't how to get me the large file so i had her upload it for me. Hopefully this helps someone with a problem or helps develop better things for this cheap tablet. I was unable to get cwm 5 or 4 from the first thread to work on this device(flashed via adb shows blank screen upon reboot) so i cant get to try the emberrom think it might be because this tablets locations are mnt/sdcard (internal) mnt/extsd(external) so my friends tablet is back to original. if anyone knows how to put cwm on this thing or wants to so some testing let me know. hope this helps anyone with an a727 but i cant post link until i have 10 posts anyone wanting it message me until i can post the public link.
[Android Q&A, Help & Troubleshooting] WarezAppz:
SDK for All Winner CPUs

@BLuFeNiX

SDK for Allwinner CPUs?

Now will this aid in someone creating a custom image for a Azpen A1023 or something else neat like a custom Kernel/CWM/TWRP or anything to help?
[Android Q&A, Help & Troubleshooting] WarezAppz:
*BUMP*
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
I do not own or intend to support anything other than the A700/A701. Sorry.

Maybe someone else will find this link useful. You might want to try to find other threads, since this one is very A700/A701 centric.
[Android Q&A, Help & Troubleshooting] dsulliii:
I "almost" bought one of those 1023s this weekend. Fortunately, they were out. Had I bought one, I might have found myself trying to go down that road. SOME day I'm going to do it, but even if I do, I'll certainly never become the master that you are BLuFeNiX.
[Android Q&A, Help & Troubleshooting] treecheetahdolo:
Well if anyone decides to do one for the A727 im down to help.
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Don't sell yourself short, dsulliii. You seem like a smart guy. Maybe I'll be using your mods one day ;)
[Android Q&A, Help & Troubleshooting] WarezAppz:
I don't regret buying the a1023, but my desire exceeds being at the mercy of an OEM to update. That being said I just bought a Nexus 7 2013 this evening off of Swappa. Maybe I'll get around to tinkering with this tablet now.
[Android Q&A, Help & Troubleshooting] ften:
Has anyone poked around this Firmware file yet, it's from July 10?

http://www.azpenpc.com/download/detail.php/id-11.html

http://www.mediafire.com/download/ksa2ojmcoyjykjc/A700_Firmware.rar

I've tried dumping the A700 Firmware.img from it, so far I've met with failure.
[Android Q&A, Help & Troubleshooting] Akshay0081:
please upload on mega or someother website it is showing error while downloading from the above links

---------- Post added at 05:33 PM ---------- Previous post was at 05:27 PM ----------
[Android Q&A, Help & Troubleshooting] joeylikesubuntu:
i have a azpen a729 trying to boot into recovery menu everything is stock but i forgot the pattern password how do you boot into recovery
[Android Q&A, Help & Troubleshooting] nintendo1889:
Is there any way to soldier on more ram on to these? I will be getting the A745 with the allwinner33 cpu. They are on sale at micro center for 30$ right now.
[Android Q&A, Help & Troubleshooting] kofman13:
any custom roms for A727?
[Android Q&A, Help & Troubleshooting] Phlox49:
Found my old Azpen A701 while moving out, and I was wondering if anyone knew where I could find a link to stock ICS for this tablet?
[Android Q&A, Help & Troubleshooting] XDM inc:
is this stuff like roms and stuff safe for my azpen 7046?
[Android Q&A, Help & Troubleshooting] nintendo1889:
The nice thing is they are already rooted, just install SuperSU. I brought mine back though; it was too slow.
[Android Q&A, Help & Troubleshooting] nintendo1889:
I had to bring it back as the screen was horrible! It had Miracast support but even that was slowwwwwww.
[Android Q&A, Help & Troubleshooting] DataCheck:
Azpen A700 Freezes After Hard Reset.

Hello,

I know this is an old thread, but it looked like the best place to seek help.

My old Azpen A700 started to act up. So I did a hard reset and now it freezes at the AZPEN Logo screen.

I have done the hard reset several times, and when I try to boot, it just hangs with the AZPEN logo on the screen.

Can I boot from the SD disk or recover the OS somehow? Or this tablet hit its end of life?

Thanks
[Android Q&A, Help & Troubleshooting] xdaenchant:
Yo, im trying to look for Azpen 1045 dri CWM recovery.
[Android Q&A, Help & Troubleshooting] dsulliii:
I'm kind of believing that the two tgz files that the Uberizer makes for /system and /data might be important. I'm still playing around with it to see. But to use the Uberizer's ROM dump, I think you have to do an extra step or two with rooting (it's already rooted, but it doesn't pass some root tests, I suspect it could be because of the location of busybox or even possibly the specific SuperUser.apk in use) before you can get the Uberizer ROM dump though.

So that precaution being stated, here's what I'd do... feel free to correct me anybody.

1) Use an external SD card with at least 4gb free on it. It should be recognized as /mnt/extsd, I believe.

2) Open a shell either from Terminal or from ADB and ensure you're SuperUser (should be a # prompt), if $ prompt, type "su" to get the #.

3) You can paste this whole block into the terminal session, it has carriage returns in it and each line will execute one at a time until finished.

dd if=/dev/block/nanda of=/mnt/extsd/nanda.img

dd if=/dev/block/nandb of=/mnt/extsd/nandb.img

dd if=/dev/block/nandc of=/mnt/extsd/nandc.img

dd if=/dev/block/nandd of=/mnt/extsd/nandd.img

dd if=/dev/block/nande of=/mnt/extsd/nande.img

dd if=/dev/block/nandf of=/mnt/extsd/nandf.img

dd if=/dev/block/nandg of=/mnt/extsd/nandg.img

dd if=/dev/block/nandh of=/mnt/extsd/nandh.img

dd if=/dev/block/nandi of=/mnt/extsd/nandi.img

dd if=/dev/block/nandj of=/mnt/extsd/nandj.img
[Android Q&A, Help & Troubleshooting] comstar:
Thanks Dsu - Everything completed fine.I was dowloading Uberizor when you posted, a big hassle. I would much rather type terminal commands.

Is there something you need me to look at before I flash the recovery? I originally rooted with cydiaimpactor. I'm going to do an uberizor dump of mine for archival purposes . I think this will be a good tablet to learn a little more Android with. You guys have been great. I've learned already from both of you.
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
I think I know what caused this. When I created my backups, I did them over ADB while running android (since there was no way to get ADB while in stock recovery). Copying the mounted partitions may have caused a few file corruptions. I wonder if I can fix them by running fsck on my images... I think I'll try that.

Anyway, I'm glad you had a tar backup that got you all the way to stock! :D

For posterity, I think I will do a factory reset on my tablet, flash CWM, and then create new dd images. Creating them while booted into CWM will mean they are not mounted, and not vulnerable to corruption.

You should be fine just flashing, as long as you type the commands correctly. I would actually advise that you take a full backup after you flash CWM, so that you can take the backup whilst booted into CWM and avoid any issues with the partitions being mounted.
[Android Q&A, Help & Troubleshooting] comstar:
Just completed a nand backup of the original.

I'm doing a Uberizor dump first and will do a backup while booted in CWM after I load the recovery..

Anything else anybody wants me to look at first.?
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
I don't need you to look at anything. Thanks for the offer. I think I have extracted everything useful from this device.
[Android Q&A, Help & Troubleshooting] comstar:
Cool. Just thought I would check.
[Android Q&A, Help & Troubleshooting] dsulliii:
dd'ing NANDs is good, don't need to tar tgz's.

Thanks BLu.... I took a LOT of time doing different experiments to get comfortable with this. In the end of it all, I totally agree with you. The tgz files being tar'd are not necessary. I see them as a way for the Uberizer to capture non-moving copies of everything so that what happened to you doesn't happen since the Uberizer does run while you're running the OS rather than the recovery. Clever on their part, but adding a bit of shrouded mystery to it all.

My final test was to do exactly as you stated that you would do. I dd'd all 10 partitions from recovery, started all over again, dd'ing them back from those copies, and it was flawlessly perfect.

So undoubtedly the /system or /data img's that you captured were probably instable due to active processes. I'm sure you're right.

I am going to keep playing, but now I have no reason at all to believe that I can't get back to where I started ... where I am today as well. All due to your efforts. (Yeah, my wife probably feels that it was all due to my efforts too, since I spent so much time on it. But I know better.)

These are the GREATEST little boxes! For the PRICE! Incredible. And this Jelly Bean 2 OS adds that extra layer of making you feel like your really got something for your money.

I got mine at Micro Center in Denver. They have a limit of one per customer, but I'm sure there are ways of buying more. I think they'd make great Christmas gifts for my Grand kids.
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Yeah, these are pretty cool for $20 (if you had the coupon). I think you can buy more than one at full price ($40). My local micro center certainly doesn't seem to care.

As for the tar.gz, it allows the backup to be much smaller. A dd image is byte-for-byte, which includes all the unneeded empty space. A file-by-file copy is better for most things, since you don't need partition sizes to match. The dd is just really convenient if you know you'll be restoring back to the original partition.
[Android Q&A, Help & Troubleshooting] dsulliii:
"Coupon"? And I thought that I got a great deal for $39.95! :cool:

Hey, do you see the signature on this one? Yep, it's from my new little toy. I'm so happy.

:D
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Haha, nice sig. :D I still haven't taken the time to try Tapatalk out yet. I think I got the coupon because of my business (I'm the sole proprietor of a computer repair company, where "company" means "a guy with business cards" -- that's just on the side though. Primarily, I'm a software developer). Not sure if non-businesses got any coupons.

---------- Post added at 07:14 AM ---------- Previous post was at 07:05 AM ----------

Update: I have replaced the old dumps with clean, stock images. I took them via ADB in CWM, so they shouldn't have any corruption. The only non-stock thing about them is the updated su binary. The original su binary is still in the image, but has been renamed to su.original. The original links now point to these new files. Here are the links again, for convenience:

nanda.img -- bootloader (loads android or recovery and contains boot animation, battery charging images, etc.)

nandb.img -- env (sets environment variables and helps bootloader)

nandc.img -- boot (android kernel and ramdisk, this loads on normal boot)

nandd.img -- system (everything in /system)

nande.img -- data (everything in /data)

nandf.img -- misc (used to store temporary data between boot stages and reboots)

nandg.img -- recovery (recovery kernel and ramdisk)

nandh.img -- cache (various temporary files)

nandi.img -- databk (a backup of some of the more important files in /data)

nandj.img -- sdcard (internal sd card)

nand e, f, h, i, and j are not particularly useful for restoring to stock, since stock backups of these partitions are really just empty filesystems, but I have included them anyway.
[Android Q&A, Help & Troubleshooting] goingcrazy614:
Awesome work from you all!!! I picked up 3 for x-mas.

You guys might want to start a new thread with step by step set up. Again great work.
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Yeah, that's a good idea. I think I'll do that sometime this weekend.
[Android Q&A, Help & Troubleshooting] johncro13:
Well, shoot.

Running stock, I got a lot of force-closes, occasional random reboots, and eventually insufficient memory errors. I got CWM up and running on it, and after clearing cache, it won't reboot past the logo. I have downloaded all the img files here, (including (A13)(86VS-M758C1)(CPT-OR-SKYRAINBOW-H070D-12AY-50PIN-800X480)(BLOGHUGOENCHINA).20130725.img) but all I can do is get into CWM. No adb.

I have the a701 LiveSuit, but that's utterly useless. Can I get some help getting back to stock?
[Android Q&A, Help & Troubleshooting] goingcrazy614:
Sweet! I have been flashing for awhile and when I got these tabs I was worried I wouldn't be able to flash it. Now that you have a root and recovery working, maybe a dev will pick it up. We need to find a device that is similar that has a ROM and port it over for now. If it gets popular a group (CM, PA, AOSP, etc) may pick it up. You are moving in the right direction. Congrats.
[Android Q&A, Help & Troubleshooting] BLuFeNiX:
Boot back into CWM and do a factory reset, then wipe dalvik cache (under the "advanced" menu). Then reboot. You will lose all of your apps and settings, but it might bring you back to bootable.

Thanks for the encouragement! I hope to make some kind of ROM soon. This tablet has turned into my hobby project.
[Android Q&A, Help & Troubleshooting] johncro13:
Tried that. Negative. I'm willing to bet the memory was somehow corrupted. I am beginning to think that the only way to go back to stock would be to use a CWM-flashable stock zip, which has not been made yet. Thoughts? Ideas?
[Android Q&A, Help & Troubleshooting] dsulliii:
JohnCro13 - all is not lost. If it is an Azpen 700, use LiveSuit701 to flash BLu's partition-modified ICS ROM. After you do that, you have to enable adb from Settings->Developer. Use ADB to dd BLu's TEST4 CWMr. Once there, you can either stay on ICS or use his 10 NANDs to dd in recovery back to stock.

---------- Post added at 11:21 AM ---------- Previous post was at 11:18 AM ----------

I want to iterate to everyone... Do NOT flash the first ICS ROM that I recommended early in the thread. It partitions incorrectly and prohibits returning to stock or to Jelly Bean. Use BLu's partition-modified ICS.
[Android Q&A, Help & Troubleshooting] johncro13:
Thie one: A13 Livesuit image w/ A700 partition values?
[Android Q&A, Help & Troubleshooting] dsulliii:
Yippers, (yes, for those whose kids weren't generation Land Before Time.)
[Android Q&A, Help & Troubleshooting] comstar:
I can Update the Op with some setup and file links if you want. Instead of a new thread. But it doesn't matter to me,.
[Android Q&A, Help & Troubleshooting] johncro13:
I love that idea.
[Android Q&A, Help & Troubleshooting] comstar:
I will work on it this evening along with a vodka tonic!
[Android Q&A, Help & Troubleshooting] johncro13:
Ugh. No device that need to update. Shoot me.