https://dl.dropbox.com/u/61019120/7g3basefiles.zip
Have a blast! (Please note computer not always on!)
https://dl.dropbox.com/u/61019120/7g3basefiles.zip
Have a blast! (Please note computer not always on!)
ninjaduck said
So I'm attempting to rebuild a copy of my firmware now, thanks to a helpfully-supplied kernel.
I get an error message (see image) referencing a file that does not exist in _extract --- I can't seem to find this "oem" .fex file in multiple original source firmwares (A7 official, A7 elvish, etc.)
Even if I remove the line from the image.cfg file, error persists.
Any ideas?
I'm going to put up my recovery/system/boot/bootfs files online for anyone else to mess with. Link to follow.
Hi ninjaduck Thanks for your hard work, Just back of holiday and i have been playing around and managed to get an image, However it gets stuck on boot screen so back to the drawing board, i checked the config file and RSFAT16_OEM is mentioned twice
{filename = INPUT_DIR .. "_extract\\RFSFAT16_OEM_000000000000.fex", maintype = ITEM_ROOTFSFAT16, subtype = "OEM_000000000000",},
and
{filename = INPUT_DIR .. "_extract\\RFSFAT16_VOEM_00000000000.fex", maintype = ITEM_ROOTFSFAT16, subtype = "VOEM_00000000000",},
so once they are both removed the system will create the image file.
Hey guys, have been attentively reading this thread. Looks like some progress was made. Have we now got an update.img to restore our 7G3 to factory default, or at least a working CWM so we can do Nandroid backups ?
Keep up the good work guys I'm sure many people on here would thank you if we eventually get this working.
EDIT: Just looked on the Arnova site and I can see they've put up an update.img for the 7G3. So this together with the kernel source being available should now help with getting CWM loaded in, right ?
There is some progress (by ninjaduck mainly) with the firmware work on the Arnova 7 G3, but I don't think anybody has managed to get a full firmware image (update.img style) than can be flashed.
The firmware available on Arnova website is for the 7b G3, which has different hardware and won't work on our 7 G3.
I've been busy with other tablets but I'll try to work again on the 7 G3 in September.
When we work fine thru the firmware image building process maybe we could adapt Christian Troy CM9/CM10 made for Allwinner devices 
Cheers.
thanks for pointing out my mistake there admin. I thought Arnova may have put the 7G3 update.img up, but ofcourse as you pointed out I mistakenly was looking at the wrong one.
So now we either wait for Arnova to put up the firmware or we build in CWM so we can do our own.
Waiting for Arnova can take very loooong
there are some old devices such as the Arnova 9 G2 that still haven't any stock firmware published by Arnova.
I would suggest we keep following up: "Can you advise WHEN firmware blah blah"
Nag, nag, nag. It sucks, but sometimes it's necessary when customer service is poor.
Anyways, for those who have flashed a custom ROM and can't get auto-rotate or whatever other features back, I have developed an end-around method for restoring the tablet to near-stock firmware (with a few minor tweaks), tested and confirmed working. I went to Elvish .3 for A7 and back to near-stock without a hitch.
I will be writing it up and supplying the necessary files this evening. It's certainly not one-click, but hopefully it's a workable fallback option for those of you who have borked tablets
All credit is due to others, I just stumbled across the right half-Chinese file and made it happen.
Good work ninjaduck, will help those with problems and a very good beginning
I'd like to thank everyone who has provided information and work on this topic. It is great to have such a resource to go to. I wish I could contribute more, but unfortunate "testing" is all I'm able to offer. I recently played around with (downloaded newer versions) of Superuser and Busybox, and have messed up my perfectly good working (with Google Play - thanks again admin) 7G3, and I'm regretting the #$%^ out of it. I'm hoping a "stock firmware" will fix my problem. After uninstalling one or both of those programs, my tablet now boots to "day one" every time, retaining nothing I had set. Looking at the [Storage] it show a green bar for Internal the full way, and shows 44.1mb of apps installed. Any app I try to install tells me it can;t due to no free space. Some apps like ES File Explorer, that install to external space by default, will install. But every other app will not. Again, after a power cycle, it goes back to the "Welcome" screen as if it was day one, and everything setup and installed is gone. At least it boots right?
This was a direct result of me installing and uninstalling a version of SU and/or BB. I'm I wondering (hoping) that someone can tell me if a new stock ROM image (once it is made) is what I need to fix my problem? If not, I can start a new topic to discuss my problem further. Thanks again in advance for everyones contributions to these topics.
Hi Zinger6786, sorry to hear you're having problems with your new AN7G3.
If we ever do get a stock rom i'm willing to bet it will solve your problem since it will take the tablet back to factory defaults and set all permissions and partitions sizes correctly.
In the meantime, from your problem descriptions, it sounds as if your system partition has either truly filled up with some 'junk' or you have a permissions problem.
Since we do not have a CWM working for our tablet yet I'm not sure which way to advise to try and fix it.
I believe (cause I tried it) that Rom Manager (which you can download from the Google market) does have an option to fix permissions but I'm not certain it actually works on the tablet, although it appears to do something I'm not sure it actually does (if you know what I mean).
You should be able to use any root explorer, move to the system partition and show it's details. This will tell you how full (in MB) the file explorer thinks your system partition is.
I've just done it on mine and it shows 217MB , but I have addded some stuff in there so yours should be a bit smaller unless it's got full of 'junk' like I explained above.
The details should also show it as being Readable but not Writable.
Each partition in the android system will be set to a specific size so if yours has got full with something that will explain why you cannot write anything into it.
If you have a permissions issue it would explain why apps (that need to be installed in the system partition) cannot install but apps that can install elsewhere (like ES File Explorer) do.
Here is the partition info of the AN7G3:
app_67@android:/ # df
Filesystem Size Used Free Blksize
/dev 407M 44K 407M 4096
/mnt/asec 407M 0K 407M 4096
/mnt/obb 407M 0K 407M 4096
/system 251M 217M 34M 4096
/data 1007M 161M 846M 4096
/cache 251M 4M 247M 4096
/mnt/extsd 7G 1G 5G 4096
/mnt/sdcard 2G 882M 1G 4096
/mnt/secure/asec 2G 882M 1G 4096
app_67@android:/ #
Your /system partition should also be 251MB, but ofcourse your used/Free will probably be different, but the important thing is to make sure that you have some 'Free' space left. Basically if, from your ES Explorer, your /system partition shows xMB in size then what you have left is 251-xMB to install any apps that need to install in /system/app. As I said other apps (that don't need to reside in /system/app) will install fine, these usually go in the ./data/app directory and as you can see from the above listing we have around 1GB of space there.
Let us know how you get on. Good Luck.
Hey all sorry for the delay. Zinger, if you can access ADB, my method should set you back to stock.
I have now purposefully screwed with the ROMs as much as possible, and as long as I can get ADB, I can always get back to stock. I even got the tablet confused with mount points for extsd and sdcard, and fixed it. Even if you can't get ADB, you should still be able to flash an image in LiveSuite, which would give you ADB, and proceed from there.
Anyways I've been delayed a bit thanks to a nasty lightning strike that destroyed my circuit breaker panel at my house. I should have power restored later today and will get files and instructions put online. Sorry again for the delay.
ninjaduck, thanks for the reply. I have the SDK installed, and have downloaded the ADB drivers from a link in one of the forums on this site. I can open a CMD prompt and type "adb devices" and my device shows. I have also downloaded and installed Android Commander, and can cnnect to my device with it. If you could, would you point me to or elaborate on what "my method should set you back to stock" is referring to? Is there a link somewhere, steps listed in a thread, what am I missing? If "my method" is referring to what you are currently working on and will have the files and instructions put on-line later today, then I apoligize for my ignorance
Thanks again in advance for the assistance.
Here's the details:
Like I said, method is borrowed from others with assistance from everyone involved here. You will need a micro SD card that's at least 8GB.
My personal backups of the nand partitions are linked below; it's near-stock with Google Play, CPU Master, and extsd as sdcard mod.
To restore nand partitions on the G3:
Place the files at the root of a micro SD card and insert into your tablet. Please note that steps that read "sdcard" may need to be changed to "extsd" depending on how your tablet currently mounts the card. If file not found, change and try again. Also, if you're restoring and this mount point changes, you may need to send an adb reboot command and pick up where you left off once it restarts.
Open adb (Win Vista/7, command prompt as administrator!) as root (adb root)
adb remount
adb shell
cat /sdcard/nanda.img > /dev/block/nanda
cat /sdcard/nandb.img > /dev/block/nandb
cat /sdcard/nandc.img > /dev/block/nandc
cat /sdcard/nandd.img > /dev/block/nandd
cat /sdcard/nande.img > /dev/block/nande
cat /sdcard/nandf.img > /dev/block/nandf
cat /sdcard/nandg.img > /dev/block/nandg
cat /sdcard/nandh.img > /dev/block/nandh
cat /sdcard/nandi.img > /dev/block/nandi
cat /sdcard/nandi1.img > /dev/block/nandi1
sync
(Ctrl-C to exit shell)
adb reboot
You're done. To make your own backup, repeat the steps in reverse (cat /dev/block/nanda /sdcard/nanda.img etc.) I have no doubt that not all of the images are necessary, but I provide all of them to be thorough. Uncompressed it's over 6 gigs, hence each is zipped individually.
https://dl.dropbox.com/u/61019120/tabletfiles/nanda.zip
https://dl.dropbox.com/u/61019120/tabletfiles/nandb.zip
https://dl.dropbox.com/u/61019120/tabletfiles/nandc.zip
https://dl.dropbox.com/u/61019120/tabletfiles/nandd.zip
https://dl.dropbox.com/u/61019120/tabletfiles/nande.zip
https://dl.dropbox.com/u/61019120/tabletfiles/nandf.zip
https://dl.dropbox.com/u/61019120/tabletfiles/nandg.zip
https://dl.dropbox.com/u/61019120/tabletfiles/nandh.zip
https://dl.dropbox.com/u/61019120/tabletfiles/nandi.zip
(NOTE - nandi1.img will not fit in my dropbox. If you need it, give me your email and I will send you a Google Drive share link)
If files aren't available, they're still uploading.
I wouldn't mind if someone would mirror these files; I need my dropbox space for work. If anyone wishes to carry the torch further, using this method and info @ http://www.freaktab.com/archive/index.php/t-912.html you should be able to modify the AOKP/CM9 roms to work with our kernel with proper wifi reception and auto-rotate.
Questions/comments/reactions?
Thanks for your research ninjaduck 
I'll download, repack and host to the files to a permanent place later today so you can free some Dropbox space; I'll PM you for the missing nandi1.img.
Since you confirm this restore method works, I'll give a shot flashing the Elvish for Hyundai A7 and restore back to Arnova 7 G3 using your files. I'll also later try to do some firmware modifications, as time permits...
Cheers.
Link to nandi1.img (zipped, large filesize)
https://docs.google.com/open?id=0BwHt6JqpoqLAY3REczFyUmM2R2s
and admin, the thanks is to all of us, we've helped ourselves/each other since Archos apparently can't be bothered.
Which is really disappointing, too.... their portable-console-tablet that's upcoming has real potential, but I certainly don't think I can recommend anybody buy it!
It did not work very large file is almost ten times larger than a standard img.
Thanks very much for your efforts ninjaduck, I installed all the nand files apart from nandi1 and it boots up nicely as an Arnova tablet again and the accelerometer works fine. I've just got one slight issue which persists after two fresh installs, the home 'button' doesn't work - anyone any ideas as this would make it perfect.
You were right that it doesn't need all the nand images installed to boot back as a 7G3, not sure how many are required. When installing I had to use /mnt/extsd in the path for the first 4 image files, then it overwrote the file system and I had to exit, adb remount, adb shell then use the path /mnt/sdcard.
Hopefully someone can return this to a single image file for a simpler install.
nandd is the system.
Home button issue sounds like a messed up program default . Try going into manage apps on system settings and clear defaults for android system, launcher, etc. Or try clear data/factory reset. I agree that it seems only nanda through nandd seem necessary to restore the system.
Factory reset did the trick, home button now works, as does pretty much everything - result!
Okay, first off I'm estactic
I now have my original Arnova 7 G3 truly back to "original" and "factory" defaults. ninjaduck, I used you files and steps, and conceptually this works really well and consistent. I saved my files first and lliterally did the restore a two dozen times. I resotred all (9) partitons, and only some of them to test with. However, unlike what SRH990 stated, once restored it was not a factory Arnova 7 G3. I immediately noticed several things, Voice talking for typing was missing, AppsLib will not run, says, "not supported on this tablet", the Model number now shows as a GT-19100 instead of AN7G3, and several more. Yes is solved my problem where my image files were corrupt, but restoring your images basically gets me your tablet, exactly as you had it. I'm assuming you either do not have an Arnova 7G3, or you had another ROM installed? I figured out it was my "system" partition (nandd.img) that needed to be restored to get the top Internal storage to show as 0.98GB total instead of 0. I did a lot of reading up, and have a good idea now of what all (9) partition images are for ICS. So how I got a "truely" factory original image?
1) Went back to the local brick and mortar store here and bought another Arnova 7 G3
2) ONLY turned it on and ONLY set the USB Debugging, absolutely NOTHING else
3) Connected to my PC (with Android SDK and adb) and saved off all (9) partitions to an 8 GB external card
4) Restored the (9) partitions to mine, and now it is EXACTLY like the new one, and back to truely factory default.
Note: I checked all the reported Storage sizes and comapared everything I could.
5) Then without doing anything to mine, NOTHING but the following,
a) Added my WiFi network, ran included AppsLib, downloaded and installed ArcTools 0.69, and added Google Play for 7 G3
b) Removed my WiFi and just ran Google Play to ensure it started up (I did not configure it)
6) I then saved off the (9) partitions again, thus getting a copy that is original factory plus ONLY Goggle Play
I did this 3 times, verified the tablet was factory each time, verified Google Play "worked" each time, and throughly tested all the features of the tablet. At least for me, my original tablet is back to factory, and is performing speedily and very well. I see absolutely nothing wrong with it, and I've played with it now for close to 24 hours. I have both sets of these (9) nand partition files, that should work for anyone with an Arnova 7 G3 to get it truly either back to factory, or factory with ONLY Google Play. I just need to find a place to store the 2 sets of 3.80GB files. Thanks again to everyone who has helped with this, and has educated me. I truely appreciate this web site (ArcTablet) and those members who love these products.
Partitions:
NANDA = BOOTLOADER
NANDB = ENVIRONMENT
NANDC = BOOT\KERNEL
NANDD = SYSTEM
NANDE = DATA
NANDF = MISC
NANDG = RECOVERY
NANDH = CACHE
NANDI = internal NAND area (usually mounted as SD card on stock ROM)
Thanks for your report Zinger6786, thanks again ninjaduck for your help.
ninjaduck, I've made an archive of the 4 first nand images (nanda to nandd) so you can delete yours.
Coming from a full image (like elvish or stock) these 4 images are sufficient to restore a working device. A non working device should be flashed with Livesuite first.
Ninjaduck "nandd.img" system image is not fully stock as there are slight changes in the system build.prop and Google Play / Android Market is already installed, but it's rather convenient and can also be removed as the firmware is rooted.
Later on, I'll try to provide some batch files to ease the firmware restoration, but instructions given by ninjaduck in post #63 and confirmed by Zinger6786 (post #71) should do the job.
Finally, it's also worth mentioning there is also a CyanogenMod 10 (CM10) Android 4.1 Jelly Bean firmware on the way for the Arnova 7 G3, more info soon...
Awesome news. Zinger think u could host those backups for others?
I have been attempting to flash cwm to nandg but reboot recovery won't work. Anybody been able?
ninjaduck, I'm permanently hosting your files here, see my post above 
Regarding CWM, I had no problem to flash it, I used the file from XDA (attached to this post as well)
Copy the recovery image to your tablet storage:
adb push cwm-6.0.1.0-touch.img /mnt/extsd
Then from an adb shell, write the image to nandg partition.
cat /mnt/extsd/cwm-6.0.1.0-touch.img > /dev/block/nandg; sync
Then you need to set the tablet to reboot in recovery, use the supplied batch boot_recovery.bat
or from an adb shell:
echo -n boot-recovery | busybox dd of=/dev/block/nandf count=1 conv=sync; sync; reboot
Cheers.
Thanks for the info ninjaduck as I didn't know about cwm recovery. Been wanting recovery to save image backup.
Great work everyone!!
Finally I can begin to return my wife's g3 back to how it was and I won't have to listen to her anymore!
Well done and thank you to all involved.
Just one thing, is it possible to have a guide to do this for noobs like me?
Thanks again.
Just one thing, is it possible to have a guide to do this for noobs like me?
Thanks again.
+ 1 please.
My heartfelt thanks to everyone who contributed to this thread. I now have a fully working CWM, have made a NANDroid Backup and have a working image to put the 7G3 back to factory default if I need to; brilliant.
I didn't use the ADB to install/execute CWM, instead I did everything via Terminal and su.
Thanks again guys.
May I also join to ask to make a guide for it for noobs like me
..everything is going over my head ![]()
---ok...was trying to use my brain...
Zinger6786 has already given the steps ![]()
1) Went back to the local brick and mortar store here and bought another Arnova 7 G3
2) ONLY turned it on and ONLY set the USB Debugging, absolutely NOTHING else
3) Connected to my PC (with Android SDK and adb) and saved off all (9) partitions to an 8 GB external card
4) Restored the (9) partitions to mine, and now it is EXACTLY like the new one, and back to truely factory default.
Note: I checked all the reported Storage sizes and comapared everything I could.
5) Then without doing anything to mine, NOTHING but the following,
a) Added my WiFi network, ran included AppsLib, downloaded and installed ArcTools 0.69, and added Google Play for 7 G3
b) Removed my WiFi and just ran Google Play to ensure it started up (I did not configure it)
6) I then saved off the (9) partitions again, thus getting a copy that is original factory plus ONLY Goggle Play
----have bit confusion because there r too many attach files..
NANDA = BOOTLOADER
NANDB = ENVIRONMENT
NANDC = BOOTKERNEL
NANDD = SYSTEM
NANDE = DATA
NANDF = MISC
NANDG = RECOVERY
NANDH = CACHE
NANDI = internal NAND area (usually mounted as SD card on stock ROM)
these files r the dropbox links ... ok.. understood..
What about the files posted in 65 and 72? do I need to copy those to that 8gb sd card?
omg you guys are awesome! I was tweaking around on the tablet trying to get ad-hoc to work but unfortunately was unable to revert and was stuck with no wifi so I was forced to flash Hyundai A7 which im sorry lacks performance. Im surprised how well this device is built and Im more impressed that there are active members in this forum willing to get dirty and solve some issues thanks again
Zinger6786 said
I have both sets of these (9) nand partition files, that should work for anyone with an Arnova 7 G3 to get it truly either back to factory, or factory with ONLY Google Play. I just need to find a place to store the 2 sets of 3.80GB files.
As admin stated, you only need the nanda to ndndd images to restore a working tablet (that has, for example, some other A10 firmware). I can host both of those sets for download. A .zip of the images should only be 120MB for each set.
Sticky post with Arnova 7 G3 stock firmware files (slight modifications from ninjaduck) - See this topic page 5
Is that too much to ask but I would like to make a type image img to throw with livesuit. I have tried to work with adb but I can not. sorry and thanks. and forgive my English is translated with google. thanks
juanche007 said
Is that too much to ask but I would like to make a type image img to throw with livesuit. I have tried to work with adb but I can not. sorry and thanks. and forgive my English is translated with google. thanks
There has been work by several people on creating a recovery.img file. But, no success has been posted yet.
I found an interesting walk through on creating custom .img files for the A10 based Hackberry. https://www.miniand.com/forums/forums/2/topics/73 That may help experienced people get a true .img file to use with LiveSuit.
xzyk how were you able to create a nandroid backup?
granted, I'm lazy and haven't looked at CWM on my tablet yet, but I was under the impression that this recovery build lacks the menu options for backup/restore.
how'd you get around that?
ninjaduck said
xzyk how were you able to create a nandroid backup?
granted, I'm lazy and haven't looked at CWM on my tablet yet, but I was under the impression that this recovery build lacks the menu options for backup/restore.
how'd you get around that?
I can't answer the how nanjaduck got his backup but your right about cwm touch not having backup or restore. I so didn't know that till I installed cwm and found out. Disappointed
Hi, there certainly is a backup and restore because I just created one.
1. Extract cwm-6.0.1.0-touch.img to the root of extsd.
2. Go into Terminal, and type su (to go into superuser), note: prompt changes from $ (dollar sign) to # (hash sign).
3. Now type cat /mnt/extsd/cwm-6.0.1.0-touch.img > /dev/block/nandg; sync
3.1 The above will overwrite your existing recovery.img with the CWM-touch recovery image.
4. For reboot, back to terminal su, type echo -n boot-recovery | busybox dd of=/dev/block/nandf count=1 conv=sync; sync; reboot
To make things easier I just copied the above commands into a text file called 'cwm-install.txt' and 'cwm-reboot.txt' and then just open whichever i need, do a cut and paste into terminal su.
Once you execute step4 the 7G3 will reboot into CWM, you willl initially only see the first 3 options but scrolling with your finger (after all that is why it is called CWM-touch) you are able to see all the other options available just as on any other CWM implementation.
Note: The backup is done to sdcard/clockworkmod (not to extsd). Once backup is complete you will have two directories inside sdcard/clockworkmod, one called backup (with all the usual img files) and another directory called 'blobs'.
Have fun !
So now I have a question.
We now know that the .img file required to put our tablet back to factory default is nanda to nandd, and we have a copy of these files.
If I were to put my tablet back to factory default (either via factory reset or using above images), then load CWM, amend my tablet to exactly how i want it, then do a full CWM backup.
The firmware update process on the Arnova site, suggests that if i put an 'update.img' file inthe root of the device then it will get installed as new firmware on power up.
Doesn't this suggest that if i compile my CWM backup into an 'update.img' file I should be able to distribute it or use it as a quick way back ?
The reason I ask is that the stage we're at one has to load CWM-touch to be able to return to a previous Nandroid backup, but if we could compile the backup into an 'update.img' and it works, as implied on the Arnova site, then we won't even need CWM to load this file, or we could make an 'update.img' that actually also includes CWM, busybox, superuser etc.. This would make life a whole lot easier for many people who are not android savvy.
I haven't yet played with the backup/restore feature in CWM but I don't think it's able to build a full image for restoration (that is, all of the needed partitions) at least it works like this for CWM running on Rockchip based tablets which just does the boot and system/data images.
As for instructions on Arnova website, they are valid for Rockchip based tablets and I don't think they apply to the Arnova 7 G3 (Boxchip Allwinner based). Until someone builds of a full update.img image or Arnova publishes it for the 7 G3, the only way we have now to restore a tablet is to flash the elvish firmware using LiveSuite then restore the 4 nand partitions from ninjaduck's backup.
Cheers.
mine does a full backup, as with all other CWM on my other android devices.
The bigger problem is that CWM6 uses a new de-dup way to back up files, instead of the straight forward tar of 'old' CWM versions. This version (v6 onwards) creates an additional 'blobs' folder which will contain thousands (yes you heard it right, thousands!) of small files which are references in your main xxxxxx.img files. The idea behind it being that the next time you do another backup if the files already exist in the 'blobs' folder and haven't changed (this is checked via a hashed checksum) then you do not need to back them up again, so the second (and following) backups will be much smaller; a sort of de-duped, incremental, poor man's backup. -head over to koushik's blog for a fuller explanation: http://tinyurl.com/clc5k6l
The problem is that to build a completed update.img file out of this type of backup is harder than the old way from tarred (yaffs) files.
CWM itself has actually already solved this problem but allowing you to either (a) backup the 'old' tar way, or (b) allowing you to actually build an update.zip directly from within CWM (see below extract from more current CWM):
"New CWM features
ClockworkMod Recovery 6: Create Android Update zips on device: Using this new feature, anyone can create an update.zip package of their currently installed ROM for others to use".
The bad news is that this build of CWM touch (version 6.0.1.0) does not have this feature.
hello
I just make my own backup of my stock rom using the method ninjaduck, but lack of capacity sdcard I decided to modify the commands directly to write in my "micro-sd sdcard 8GB":
adb remount
adb shell
cat /dev/block/nanda > /mnt/extsd/nanda.img
cat /dev/block/nandb > /mnt/extsd/nandb.img
cat /dev/block/nandc > /mnt/extsd/nandc.img
cat /dev/block/nandd > /mnt/extsd/nandd.img
cat /dev/block/nande > /mnt/extsd/nande.img
cat /dev/block/nandf > /mnt/extsd/nandf.img
cat /dev/block/nandg > /mnt/extsd/nandg.img
cat /dev/block/nandh > /mnt/extsd/nandh.img
cat /dev/block/nandi > /mnt/extsd/nandi.img
cat /dev/block/nandi1 > /mnt/extsd/nandi1.img
sync
(Ctrl-C to exit shell)
adb reboot
I wanted to know if this well done my backup
thanks
WOW......
I go on deployment for a few weeks and look what happens!!!!!!!!!!!
OUTSTANDING work to all involved....
SO pleased to see this has been figured out and published here.......I cannot say this enough....

THANK YOU AND WELLDONE!!!!


Admin am looking forward to the batch file system you mentioned as those who are not techy minded will find it a savour!!!
And excellent news on having a working CWM!!!! will be so helpful too.....
Well now I can truly kill the 7G3 and know I can return it to working order again...
Hmmmm now where was that JellyBean for my 7G3 to chow down on?!


regards
Lohtse
Hey guys.
First of all. Thanx a million!!! I'm finally getting somewhere!
After bricking my AN7G3 by trying to mess around with LCD Resolution, I had no other choice but to start learning how to get the problem sorted out. Im no techie but I do have a brain cell and a half and Im sure I can get things 100%
My problem is this. After flashing my device with an A7 ROM, I got my device working. I came to this forum to try and get the tablet back to stock. I followed the instructions by ninjaduck(great work btw) and all went well. Copied nanda to nandd and transferred them via ADB to my device. I had to use different routing though, similar to zearossa's backup post 91 but reversed. i.e.
cat /mnt/extsd/nanda.img > /dev/block/nanda
cat /mnt/extsd/nandb.img > /dev/block/nandb
(hereafter it seemed to not copy the files but after sync everything booted well anyway)
cat /mnt/extsd/nandc.img > /dev/block/nandc
cat /mnt/extsd/nandd.img > /dev/block/nandd
Problem is that after booting up to a fantastic,fast stock rom I tried to install an app and recieved an 'cant install - insufficient space error'. I checked the partitioning if Im not mistaken and my microsd card shows up as internal memory. Sdcard shows up with only the installed aps worth of space and extsd is unmounted. so... my mistake is probably obvious but hidden from my noob eyes. I was wondering if someone could help me out. Was it when I copied the files to root?
Right now im downloading the latest A7 Elvish ROM I could find on the flash***my**roid site to restart everything from scratch.
TL;DR:
Dl'd Livesuite and flashed with Elvish image
copied nanda/db/dc/dd to micro sd card.
Dl'd sdks and got adb up and running
went to adb directory as indicated via prompt
checked if device was available
adb remount
adb shell
cat /mnt/extsd/nanda.img > /dev/block/nanda
cat /mnt/extsd/nandb.img > /dev/block/nandb
the next commands showed up on their own with no ...root: so I thought they possibly didnt copy, but continued nonetheless.
cat /mnt/extsd/nandc.img > /dev/block/nandc
cat /mnt/extsd/nandd.img > /dev/block/nandd
sync
CTRL+C
adb reboot
Rebooted beautifully and fast. even the wifi was improved by a bar after connecting.
However after trying to install an app, I got an insufficient memory error.
checked partitions and if my memory serves me right from orig. install, they didnt seem right
P.S. Google play wasnt installed either.
After Reinstalling img I had of Elvish, I noticed the partitions are the same so Im downloading the latest version I can find on flashmy**droidDOTcom
What could be the problem?
The latest Noob
try to perform a factory reset.
globula_neagra said
try to perform a factory reset.
I did... I remembered a previous poster said he did and things fixed themselves up, but this seems to be a system problem
Simply put. You guys rock. If it wasnt for you I'd have a 100€ paperweight lying on my desk. I finally got everything to work.
For future viewers who need the whole process in laymens terms(my apologies if this seems redundant)
1. Download Livesync v1.07 and Elvish 0.3 image
2. Download SDK tools and google how to set up ADB - this is as simple as installing and letting SDK manager install adb platform.
3. Download the firmware dump provided in this thread. You will only need nanda.img, nandb.img, nandc.img and nandd.img
4. Install Livesync and SDK tools and set up ADB.
5. FORMAT a MicroSD Card just to be safe. Make sure it has more than 8Gb
---
6. Run Livesync, Connect your device and put your device in Restore mode.
- For those who don't know how to do this, Press and Hold reset button (found inside the Mic opening) and Press and Hold Power Button
7. Your Windows System will search for the drivers. Manually search for them in your Livesync Folder under USBDrivers.
8. Select NO on livesync prompt and exit. Switch off your device completely after drivers have installed. It could be a good idea to reboot your pc too just to be on the safe side.
9. Run Livesync again and open Elvish 0.3 image by selecting the Box icon on the upper left and browsing to the saved dir.
10. Connect your device again and Put in Restore mode again.
11. The image should now start the flashing process. Just select yes on all Livesyncs prompts. Once finished an exclamation prompt will pop up. select ok and disconnect your device.
You now have a working device with Elvish!!!
...but who wants that right?
12. Start up everything on your device. Ignore all the settings for now.
13. Use your filemanager to double check directories for mounting
14. Copy the nan files to your MicroSD card and put it into your device.
15. open command prompt in windows.
16. Connect your device to your pc and set dubugging on in Developer Settings on your device.
17. In command prompt go to your adb directory and type this:
- adb device
this should show if your device is visible
then type:
adb remount
adb shell
You now have your devices terminal open in prompt
Now starts the fun part.
18. type:
cat /mnt/extsd/nanda.img > /dev/block/nanda
cat /mnt/extsd/nandb.img > /dev/block/nandb
cat /mnt/extsd/nandc.img > /dev/block/nandc
cat /mnt/extsd/nandd.img > /dev/block/nandd
(sometimes this takes a while for the prompt to register but wait until your # shows up before entering each command)
19. type:
sync
20. hold:
CTRL+C
21. type:
adb reboot
Your device should reboot and you should see your ARNOVA logo show up.
this should be enough but as a general rule of thumb, If you see any aps that you recognise from Elvish, go to Settings and do a Factory Restore.
Congratulations!!! You have a stock ROM reinstalled.
If all else fails, just repeat the process with a little more patience.
If I've left anything out let me know...
This wouldnt have been possible and we'd still be stuck with Elvish if it wasn't for the great posters in this forum. My thanks to all of you.
So, anyone have any theories on how to get an Elvish or AOKP or CM9/10 ROM on with working WIFI and screen rotate?
I've tried installing one of the custom roms and then backporting everything but nandd from the Arnova files, that seems to be a dead-end.
So far no impact other than a long first boot...
I'm thinking the accelerometer and wifi drivers have to be stored in the android system somewhere -- which means we should be able to extract the files (if we know which) from our nandd and have auto-rotate and wifi properly working in the custom roms.
Anyone have an original build.prop they can throw online?
Anyone built from AOSP on another device or know anyone who has, can maybe point us at the right files?
have you tried to use the boot from the arnova, to an elvish rom ?
yes, no result. replaced everything but /system and auto-rotate still doesn't work. i believe the solution is somewhere in the android framework files, a build.prop setting or driver possibly.
found some reading material on how wifi is configured:
http://blog.linuxconsulting.ro/2010/04/porting-wifi-drivers-to-android.html
http://nagaraj-embedded.blogspot.com/2011/02/guide-on-adding-wifi-drivers-on-android.html
that'll get me started on that angle.
as far as screen rotate,
http://source.android.com/tech/input/touch-devices.html
so fyi, this is what i'm working on. if i can come up with an easy method, i'm thinking we can simply replace a few files on any of the custom roms and have it properly configured for our device. hoping. probably after flashing, some adb push commands (simple script). currently braindead and taking a nap!