Ok, sorry ahead of time for the n00b question, but I cannot get my archos a70 to show up when I query ./adb devices on my Mac. I tried to update the .ini using echo "0x0e79" >> ~/.android/adb_usb.ini like Archos says, and I currently have SDE (Angstrom) on the device. Running the device in USB Debug as well. Is there some really basic step I am missing?
Well, managed to get the initramfs from $aur0n and the zImage from ardatdat working on the dev edition. Still can't launch ./adb shell though, so I haven't been able to partition my external sd card and relocate the dev edition to there...
Please, anyone, help. I'm dying here.
I too am having problems (bit of a noob im afraid!)
Could somebody please explain in detail exactly where to put the ini file modification.
Pretty please.
pfarrelliv said:
so I haven't been able to partition my external sd card
Click to expand...
Click to collapse
just reread all the rooting posts and realized that I'm doing the partition wrong and don't need to be in adb to partition.
i am currently mounting the external sd via the Archos since i don't have an SDreader. trying to use this post, http://forum.xda-developers.com/showpost.php?p=10324687&postcount=89, in order to partition, but can't seem to be able to figure out how to do it in terminal.
man, i'm such a noob. perhaps i should have waited til a better, Mac oriented guide was posted....
i'm going to stop posting here as it is no longer adb related.
what kind of problem are you having with the terminal commands?
I am just starting to root my A70 this minute, and they look fairly straightforward. head's up? maybe i can help? what's the issue?
digibucc said:
what kind of problem are you having with the terminal commands?
I am just starting to root my A70 this minute, and they look fairly straightforward. head's up? maybe i can help? what's the issue?
Click to expand...
Click to collapse
I'm having a hard time getting ./adb devices to recognize that i have the archos plugged in.
I also am unable to perform the fdisk -l, and am confused about the entire partitioning process to be honest. if you are able to do it successfully, i'd really love to know how you did the very basic stuff they leave out of the original thread.
thanks again!
seems my sdcard sucks, i have ordered a class 10 and am waiting on it now... let me know if you figure it out and ill do the same.
Moved to general as not android development.
I am simply trying to modInstallLocation using adb to gain a little more space using my windows 7(64 bit) computer. I have the latest android sdk installed and it all works fine with my htc desire. However i am unable to get my archos 70 to show up as a connected device using the driver from the archos site.
I know how to modify the ini file but am unsure where abouts in the file to insert the modification.
Please help!
below is a short preface and introduction before the main point of this thread. you can skip the preface if you want.
PREFACE/INTRODUCTION
i am relatively new here. i owned a nexus one a year ago and sold it for an iPhone 4. left the iOS world and jumped over to the "fastest phone in the world" (GS2 doesn't count yet). had my device for 3 days and i love it. jailbreaking iOS was very easy for me and i am *somewhat* comfortable rooting and unlocking bootloaders on android. Nexus One was very easy from what I can remember. fastboot oem unlock i believe it was? CWM, flashing *.zips, etc. So I would like to think I am not a complete n00b, but when it comes to motorolas, i have no experience. i currently own a macbook pro as my main computer, however, i do have limited access to a notebook running vista. now to get to my point of this thread.
***************************************
MAIN POINT OF THREAD: sbf_flash tool
SBF_FLASH (Mac and Linux) executable for flashing *.sbf files to motorola android phones in lieu of RSDlite. **ATRIX is said to be supported
link: http: //blog.opticaldelusion.org/2011_04_01_archive.html (wouldn't let me post real link, sorry)
*note: originally the developer wrote separate scripts for linux and mac as mac uses mach-o executables while linux uses ELF, however, the updated version works on both linux and mac platforms.
i searched the forums and only found 4 posts related to the tool sbf_flash and none of them were related to the motorola atrix. therefore i felt compelled to write this post and see if anyone has used this tool. if you read my preface it stated that I have a mac and only limited access to a windows computer therefore . my main question is. has anyone used this tool to flash *.sbf files to their atrix? if so, were there any issues whatsoever?
**if no one has used this tool before, I will hold my breathe and take the plunge. I will gladly be the guinea pig for all you mac/linux users out there (mainly mac users as if I am not mistaken, linux users have someway of flashing *.sbf files?)
thank you for reading this post. if I do not receive any input in terms of user's experiences with this tool by July 12th 9:00PM (EST), I will attempt to use it and see what happens. very anxious to get the bootloader on my device unlocked and flash CWM and flash 2.3.4. but i will wait.
**EDIT: i am aware of the fact that I can use bootcamp, VMware, Parallels or essentially any Virtual Box to run Windows on my mac and use RSDlite, however, I feel that if a simple executable such as sbf_flash worked, if would save a ****load of time/frustration/hassles.
I have used it
I use sbf_flash daily for script making purposes and it works flawlessly with the Atrix. Make sure to make the script executable by typing the follwing command in the directory where u have it.
sudo chmod +x sbf_flash.sh
For example if u have the script in the downloads folder type this into the the terminal:
sudo sudo chmod +x /Users/username/Downloads/sbf_flash.sh
Then to flash an SBF type ./Users/username/Downloads/sbf_flash.sh name-of-sbf.sbf
Hope this helps. I have made a script for myself that automates this and would be happy to share it with you. However this is rather basic and I don't think you need a script. If you have any questions let me know.
ionstorm3 said:
I use sbf_flash daily for script making purposes and it works flawlessly with the Atrix. Make sure to make the script executable by typing the follwing command in the directory where u have it.
sudo chmod +x sbf_flash.sh
For example if u have the script in the downloads folder type this into the the terminal:
sudo sudo chmod +x /Users/username/Downloads/sbf_flash.sh
Then to flash an SBF type ./Users/username/Downloads/sbf_flash.sh name-of-sbf.sbf
Hope this helps. I have made a script for myself that automates this and would be happy to share it with you. However this is rather basic and I don't think you need a script. If you have any questions let me know.
Click to expand...
Click to collapse
I run windows 7 on ny mac so... yea
Sent from my MB860 using XDA Premium App
thanks for all the input (from both of you). im assuming if i cd into the directory where the sbf_flash file resides I don't need to include the path every time? i have some knowledge of C and limited C++ or object oriented programming knowledge as well. i would love to use your script that automates the entire procedure if you don't mind giving it to me. once again thanks for the advice.
correct me if i am wrong, but chmod -x essentially gives the file permission to execute? trying to remember all the different unix commands. sudo, cd, and ls are only ones i use on a consistent basis
I have realized that it is not necessary to chmod +x the script file. All you have to do is include a ./ in front of it. For example ./sbf_flash filename.sbf. Btw saw your guide on how to sbf flash under *nix, so not sure if this information is still useful to you.
oh and yes cd, sudo and ls are the commands to use on a constant basis.
hey guys, kinda new to linux and the atrix. running 10.04 im not sure if i have the sbf_flash.sh. i have a file that shows as a shell script, i hope thats right. anyway. i have followed the direction above and cant seem to get it to run. this is what i have.
sudo chmod +x /home/serooted/Desktop/sbf_flash.sh
I in return get.No such file or directory. any ideas that would get me rolling? really want to get rid of the "unlocked" from my moto splash screen
type the following in at the terminal. ls /home/serooted/Desktop/ and see if the sbf_flash file appears in the output.
ionstorm3 said:
type the following in at the terminal. ls /home/serooted/Desktop/ and see if the sbf_flash file appears in the output.
Click to expand...
Click to collapse
Yes the sbf_flash does show up in the output. so my question would be, how now do i get it to flash the file?
is there any way that someone can post a step-by-step guide to unlocking the bootloader for the mb860 running 4.5.91 on a mac as i don't have access to a pc and am un able to find a clear method to doing so. sorry I'm new to this :/
Hello all,I had bought a local tablet from calcutta called ICE Xtreme on which I had nightmares,but it also helped me learn n now here is it,a short yet complete guide for ur allwinner devices.
Like me,some of u might have been bored enough abt the stock rom that we decide to experiment.since allwinner CPUs can boot over USB(livesuit mode) n SD cards (phoenixcard) we think nothing will b wrong n flash without a full rom backup (i hav a script uploaded here,find it n hav a look), after the flash we find the stock ROM gone,camera,touch,wi-fi etc gone haywires n cache is mounted as SDCARD!!! Yes,those who used livesuit hav been in stuff lik this. Now I was also in one n upon reading alot I hav seen ppl editing bootloaders,using keyboard mouse,plugging HDMI(lcd broken). After a month of fiddling wit my device its time i share a shortcut that can save many hours of ur life.
Also do backup the boot n bootloader on ur pc as sumtimes flashing destroys the SD.
1st step. Backup ur bootloader n boot images. Use "cat dev/block/nandc > sdcard/dump/boot.img" to backup boot..nw backup bootloader the same way,by replacing nandc wit nanda.
Now u use adb pull method to backup ur system,etc,data(its optional,only do it if u want ur apps).n any other folder from the root of ur device.my script can help u do it instantly. Anyways,u must get the etc n system folder.
After that ur free to flash any ROM image through any method (actually,livesuits the best if u can find the img). Now after flash ur device is on right?? Does the SDCARD mount??if no then turn on USB debug,in adb shell type cd dev/block <enter> then type ls n ull see a list of nand partitions,the last one is the SDCARD in raw format.so format is by: su busybox mkfs.vfat dev/block/nand[drive letter,i.e. nandj] n then type vold.ur sdcard will mount.
Now send those boot n bootloader files to SDCARD/dump. U can use mkdir or mannually make the dir n copy. Thn simply type "cat sdcard/dump/boot.img > dev/block/nandc" n same way type nanda n bootloader to restore the bootloader. Now use adb to push the files of ur stock ROM system/vendor/modules(which u backed up earlier) to tablets system/vendor/modules. N the contents of etc folder to etc on the tablet.nw reboot.
Hey!!! Its working.the LCD shift is gone,cam n wi-fi doing good,touch is not reversed or stuff. Congratulations u restored ur tablet,n now running a completely diffrent ROM on it.enjoy.
Heres another shortcut ive learned. U can get any update.zip n convert it to licesuit image. Just extract the system dir. Thn copy it to ur SDCARD. Make modification if needed,copy the modules u backed up.In adb shell type make_ext4fs -s -l 300M -a system <filename.img> (dir of ur system,i.e mnt/sdcard/system) it will make u a .img file which is same as the system.fex file u get when u break a livesuit image. Copy n replace the ROMs boot n bootloader.fex files wit ur backed up boot n bootloader.img (rename .img to .fex) pack the image again to livesuit format n burn it. It will install like a normal ROM. BUT MAKE SURE FILE PERMISSIONS OF READ WRITE N EXECUTE IS INTACT. ELSE ULL ENJOY HOURS OF BOOTANIMATION. but if ur stuck use the method above n flash any other ROM n fix the RON fr ur device. Guys ROM developing n editing fr allwinner devices are not easy...BTW id lik to thank user [iamabadduck] fr his actual A10 backup script. On which i made mine. Im still doing experiments. Hope this info i shared makes the readers modest enough to make the hit thanks. Bye. [ ill b around,so if any quests,ill ans them].
I was very excited to see someone finally post a guide for these mysterious tablets! Thank you!
However, I ran into some difficulties trying to make use of them, but I think this has more to do with my hardware and trying to match it with the appropriate ROM and compatibility zip.
You see, I have a Kocaso M1060W. It's a very nice little tablet but trying to identify it has been difficult. As far I can tell, it's a clone of the Protab2XXL (I don't know what version) or something called the BC1077. It seems easier identifying other Allwinner A10's, apparently. I know some identifying information can be found in the build.prop file and that's how I figured out the tablets of which it is a clone. I even tried finding a database of different ImageSuit images I could try to use, but either there is none or my Google skills are suffering. Does it matter that Kocaso chose to go with PhoenixCard for flashing their tablets? Some documentation suggests the images for both are the same.
Can you help me find documentation that would help me identify the board and the hardware? Let me know what information you need from the tablet, and I will get it to you. Identification would go a long way towards me making use of your steps.
Also, a question. After the rom is flashed and you "adb shell" in, you have me trying to mount the sdcard directory via the nand block devices, and then entering "vold". It doesn't error but nothing seems to happen. Even stranger, running "mount" tells me that it's done something. Is it because most of the ROM flashes require the data wipe that I should assume I have the capability to read/write within the SDCARD directory?
Allwinner A10 ghost touch (Icoo D70W, goodix chip)
Hello There!
I've got this tablet since last year, but it worked brilliantly for four minutes only.
Here is some detail:
ICOO D70W, Allwinner A10 board , 1 Gb of RAM and 8Gb storage, ICS android.
7 inch IPS display on 1024X600 resolution capacitive multitouch.
The original firmware was a nightmare, so slow , and full of chinese thing with no google play, quick decision -> get another firmware.
I've installed an actual version of AOKP ( I think it was the 9th version) and I used one of those comp file which was for an ainol tablet same hardware details.
After this , my big four minetes has started until a figured out the camera does not work.
I used another compatibility file, from a hyundai tablet same camera details, camera ok , but the touch chip went down and cannot get back, since that.
Ghost touches on the screen, but the normal touches are recognised as well.
Do you have any idea, how to reflash that touch driver chip?
attached files from the original firmware, maybe give some help:
And a video on y_-tube, with this watchcode: YfNZf2BgL3w or use "ICOO D70W ghost touch problem" keyword
Thanks in advance.
Zsolt
Compatability
konyazsolt said:
Hello There!
I've got this tablet since last year, but it worked brilliantly for four minutes only.
Here is some detail:
ICOO D70W, Allwinner A10 board , 1 Gb of RAM and 8Gb storage, ICS android.
7 inch IPS display on 1024X600 resolution capacitive multitouch.
The original firmware was a nightmare, so slow , and full of chinese thing with no google play, quick decision -> get another firmware.
I've installed an actual version of AOKP ( I think it was the 9th version) and I used one of those comp file which was for an ainol tablet same hardware details.
After this , my big four minetes has started until a figured out the camera does not work.
I used another compatibility file, from a hyundai tablet same camera details, camera ok , but the touch chip went down and cannot get back, since that.
Ghost touches on the screen, but the normal touches are recognised as well.
Do you have any idea, how to reflash that touch driver chip?
attached files from the original firmware, maybe give some help:
And a video on y_-tube, with this watchcode: YfNZf2BgL3w or use "ICOO D70W ghost touch problem" keyword
Thanks in advance.
Zsolt
Click to expand...
Click to collapse
If you could Post an lsmod from both the Working Firmware and the Non-Working I will take a swing at answering your question...The problem is likely one compat file is installing drivers for one of Your pieces of hardware and not the other and the other compat file is istalling the driver for the other piece but not the One... confusing sounding...
But Bottom Line is If I had the Lsmod from the working Hardware and the 2 compatability files you tried I could likely alter one of the compatability files to cover All of your hardware.
Or better yet pull the Bootloader.img and the Boot.img out of your Tab and send them to me...
you can do this by opening a cmd window from a directory where you wish to store the .img files then type the following :
adb shell su -c "cat /dev/block/nandc > /mnt/sdcard/nandc-root.img" (Press enter Key)
adb pull /mnt/sdcard/nandc-root.img (Press enter Key)
That will give you the Boot.img (named nandc-root.img)
adb shell su -c "cat /dev/block/nanda > /mnt/sdcard/nanda-bootloader.img" (Press enter Key)
adb pull /mnt/sdcard/nanda-bootloader.img (Press enter Key)
That will give the bootloader.img (named nanda-bootloader.img)
send those from both your OEM Rom that is working and the Target Rom you wish to make work .... from that I can either write a compat patch for it or send back the edited ones from your Target Rom (the one you wish to work)
Srry i cudnt keep my promise of being around. Had been pretty busy looking for stock JB ROMs in livesuit format. Found some. Some worked n some didnt. Will abt the touchscreen issue if that Rom has a focaltech ftx_5x touchscreen its broken. U hav to compile it again leaving out the multitouch part in a header file. Do a google search. There r alot of articles. N abt da nand part well not all roms break the internal SD partition. The busybox thing u do only when ur internal cards dont mount. It will NOT WORK FOR A MICROSD IF U HAV ONE. Its generally mounted as extsd.
Try reading from here:
konyazsolt said:
Hello There!
I've got this tablet since last year, but it worked brilliantly for four minutes only.
Here is some detail:
ICOO D70W, Allwinner A10 board , 1 Gb of RAM and 8Gb storage, ICS android.
7 inch IPS display on 1024X600 resolution capacitive multitouch.
The original firmware was a nightmare, so slow , and full of chinese thing with no google play, quick decision -> get another firmware.
I've installed an actual version of AOKP ( I think it was the 9th version) and I used one of those comp file which was for an ainol tablet same hardware details.
After this , my big four minetes has started until a figured out the camera does not work.
I used another compatibility file, from a hyundai tablet same camera details, camera ok , but the touch chip went down and cannot get back, since that.
Ghost touches on the screen, but the normal touches are recognised as well.
Do you have any idea, how to reflash that touch driver chip?
attached files from the original firmware, maybe give some help:
And a video on y_-tube, with this watchcode: YfNZf2BgL3w or use "ICOO D70W ghost touch problem" keyword
Thanks in advance.
Zsolt
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1520943
It's a thread about the allwinner A10 or EKEN T01A.. it shows how to reflash to original and updated EKEN firmwares via livesuit. And also i think they mentioned something about touchscreen issues. Hope it helps
Hi please help me! I have nightmares too with my tablet:
Hi, i have a mid tabler model HBD-Mid-708G like that http://marcopolocompany.fucsio.com/e...oducts/MC-708G . This is a Boxchip a10 with 11 partitions, i get this info throw ADB.
My problem was try to install CWM getting the error Can´t Mount / Read!!!!!
I have been used this roms:
F1-4.1.1-20130319.2.0.6-A721_v4.2
pdf_android4.0.10_ctp7_public_en_0319
Q7_512M+flash+Gmail
rom_woo_comet_404_291112_0cd4d
RSH-A10-C2
speed.1.1.1
sun4i_crane_t01a-linsay-20120411
and only rom_woo_comet where some Ok! .
Solved this CWM problem flashing a rom_woo_comet using LiveSuit but the result is an screen resolution problem: (the image attach) .
So please any can say me a correct rom?
Thanks
accessing nand
hi there,
this is interesting stuff you are talking about here. Unfortunately, I get stuck to the beginning. How do you access the nand???
you say sart with cat dev/block/nandc > sdcard/dump/boot.img
I'd love to but where do you enter these commands? When I connect my tablet to my computer, I see certains parts as usb storage, and I have no way of entering commands to the tablet. From within android, everything is blocked...
thanks for your help
nacxo said:
Hi please help me! I have nightmares too with my tablet:
Hi, i have a mid tabler model HBD-Mid-708G like that http://marcopolocompany.fucsio.com/e...oducts/MC-708G . This is a Boxchip a10 with 11 partitions, i get this info throw ADB.
My problem was try to install CWM getting the error Can´t Mount / Read!!!!!
I have been used this roms:
F1-4.1.1-20130319.2.0.6-A721_v4.2
pdf_android4.0.10_ctp7_public_en_0319
Q7_512M+flash+Gmail
rom_woo_comet_404_291112_0cd4d
RSH-A10-C2
speed.1.1.1
sun4i_crane_t01a-linsay-20120411
and only rom_woo_comet where some Ok! .
Solved this CWM problem flashing a rom_woo_comet using LiveSuit but the result is an screen resolution problem: (the image attach) .
So please any can say me a correct rom?
Thanks
Click to expand...
Click to collapse
You need to edit your script.bin inside the bootloader.img... there is a utility to do this on techknow.me...
to do it manually you need to extract the script.bin file from the bootloader.img ... easiest way is from adb shell
Open a windows command window (this assumes you have adb.exe in your Path .. if not you must do this from the
same folder where adb.exe is located)
type the following
adb shell su -c "cat /dev/block/nanda > /mnt/sdcard/nanda-bootloader.img"
adb pull /mnt/sdcard/nanda-bootloader.img
this will place a file called nanda-bootloader.img in the folder where you ran the windows command window.
Now copy the file to your Linux Machine or VM
and from a terminal do the following:
mkdir bootloader
sudo mount -t vfat ./nanda-bootloader.img bootloader
This mounts the bootloader image to the bootloader folder.... in the bootloader folder copy the script.bin file to another location for editing.
to edit it must be converted to fex... you will need the fex tools for this I have them posted here: http://www.4shared.com/zip/Nzn6PV-b/tools.html
your Linux machine has to be x64 for those to work.
from the folder containing the tools folder and script.bin file open a terminal and do the following:
./tools/bin2fex script.bin > script.fex
this will create the script.fex file which is editable in a linux text editor, open the file and edit the [lcd0_para] section
to correct your screen shift ... the exact settings needed are impossible for me to determine as I do not
have your tab nor the rom you originally had on it.. if you have the original rom available (with screen position correct)
you can pull the script.bin from that rom and replace the entire [lcd0_para] section with the same section from your working rom
to solve the issue.
once edited convert back to .bin from a terminal with the following commands:
./tool/fex2bin script.fex > script.bin
now open the bootloader folder as superuser and delete the script.bin and script0.bin located inside...
copy the new script.bin file in and also copy it and rename the copy to script0.bin and place that there as well.
then from folder containing bootloader folder open a terminal and do the following:
sudo umount bootloader
now copy nanda-bootloader.img to windows machine.
open a Command window in the folder containing your new nanda-bootloader.img file and do the following
adb push nanda-bootloader.img /mnt/sdcard
adb shell su -c "cat /mnt/sdcard/nanda-bootloader.img > /dev/block/nanda"
adb shell rm /mnt/sdcard/nanda-bootloader.img
adb shell su -c "sync"
adb shell su -c "reboot"
if all was done properly your tab should now reboot with the correct screen geometry. The utility I mentioned does
pretty much all of this for you, but i cannot link it here as it is on techknow.me which requires registration to
download ... and the rules forbid links to such sites here.
I hope that all helps you.
---------- Post added at 12:24 PM ---------- Previous post was at 12:16 PM ----------
djahma said:
hi there,
this is interesting stuff you are talking about here. Unfortunately, I get stuck to the beginning. How do you access the nand???
you say sart with cat dev/block/nandc > sdcard/dump/boot.img
I'd love to but where do you enter these commands? When I connect my tablet to my computer, I see certains parts as usb storage, and I have no way of entering commands to the tablet. From within android, everything is blocked...
thanks for your help
Click to expand...
Click to collapse
You must have the ADB drivers installed and know where they are located, placing them in your Path statement is a good idea if you intend to do much ROM editing or direct Tablet commands from and adb shell.
NOTE: To open a command window from any folder on your computer in Explorer browse to the folder you want to open command window from
then in an area of the folder window that is empty right click mouse while holding shift then select open command window here
Once you have ADB INstalled, if the adb.exe is in your path open a command window from any folder you like on windows and type the commands in the command window. If ADB.exe is not in your path you must open a command window in the folder containing adb.exe
(Usually the android SDK Platform tools folder)
I Hope that helps
Thanks fsebentley, I've now copied all nandX partitions.
what I'm trying to do now, is to create a bootable sd card. I believe I must tailor u-boot.bin to boot a specific kernel with my specific hardware setup.
I've found a lot of resource for arm boards, but almost none for tablets, except for direct flashing but I'm not ready to go this far.
So, do you know about a nice tool to read what's in u-boot.bin and eventually modify it?
Touchpad driver
Hi!
I need some help!! I want to include touchpad driver an cm9 installer because when I instal the system with CWM but the touchpad not working!!!
Here is the topic where you can find the ROM: http://forum.xda-developers.com/show....php?t=1861445
Sorry I write here because I can't write in the original topic.
Thank for help!!!
Apad 711 stuck at boot logo
Hi Guys,
I need help. one of my friend has a Apad711 tablet and his stock android recovery was changed by cwm 5.08 incorrect version and hence the power + - or power button was not responding.
I took over and had flashed 6.0.2 8 cwm by following this forum http://forum.xda-developers.com/showthread.php?t=2189640
and recovery was working properly, but then i though of upgrading it to cyanogen mod 9 and downloaded the files using this forum
http://forum.xda-developers.com/showthread.php?t=1760929
however after the update was completed the touchscreen didnt work and I had to connect a usb OTG cable along with usb mouse to get into recovery. I then did a little research and tried flashing a couple of compatibility zip
711i_compatibility_1.1.0.zip, lyf1_compatibility_1.1.0.zip, 711i_compatibility_1.2.0.zip, lyf1_compatibility_1.2.0.zip which had similar specs from this website http://old.androidfilehost.com/main/Allwinner_A10_Developers/christiantroy/misc/
but even after doing so touchscreen,camers etc didnt work.
since i had made a backup of stock rom using cwm before flashing cyanogenmod 9 i thought of restoring it back using cwm 6.0.2.8
i was able to restore the back up but to my surprise i am now stuck at apad boot logo and cannot boot to recovery using the volume - and power key. i tried to connect the tablet to pc so that i can get into adb interface and reboot to recovery but the computer detects the tab as unknown device
I now need help to get into recovery and flash a rom that would make it work or complete tutorial to install/flash a new /stock rom or cyanogenmod to get the device back to life.
please refer to the manufacturers website link listed below for specs:--
http://www.apadtab.com/711_spec.php
Any help would be greatly appreciated.
allwinner a10., broken bootloader
Hi i've got a eneoze tablet with an allwinner A10., now i've flashed my bootloader with berryboot en it was working., later i wanted to change some things in de configs of the berryboot bootloader and i messed up. Now my tablet is completely dead.
It doesn't doe anything when i try to turn it on., de screen doesn't even light up., it isn't recognised when i connect it to the pc so fastboot., adb aren't working eather.
Do you have any ideas on how to resolve this.?
Greets Sam
sammekevremde said:
Hi i've got a eneoze tablet with an allwinner A10., now i've flashed my bootloader with berryboot en it was working., later i wanted to change some things in de configs of the berryboot bootloader and i messed up. Now my tablet is completely dead.
It doesn't doe anything when i try to turn it on., de screen doesn't even light up., it isn't recognised when i connect it to the pc so fastboot., adb aren't working eather.
Do you have any ideas on how to resolve this.?
Greets Sam
Click to expand...
Click to collapse
If you can't flash it from your pc, create a bootable sd card. For example, you could copy your berryboot image to the sd card and boot from it.
Supposedly, you saved your tablet nand into an image before messing up with that nand. Once you boot from sd, flash the nand again with that saved image. Good luck to you
need a little help
i wnt to increase resolution of my a10 tab from 800x480 to 1024x600....to do so i need to edit the bootloader(bootloader.fex)
but,the problem is i can't edit the bootloader.fex correctly......how to edit properly