Related
I'm in need of the stock kernal image and the clockwork recovery.zip file thingy.
NOT the zip verson of the kernal installer.
My situation, I was stupid and installed the voodoo thing, then for someone reason I tried to flash Froyo over Bionix with the voodoo kernal thing. It didnt work so I decided to deleted everything in clockwork. Then I was like omg I cant use clock work or boot my device (stuck on vibrant screen but I can get to odin and the stock recovery).
Later I read that voodoo stopped odin on the cm forum so I couldnt use it. Thats what some dude named viralblack said and theyre a mod so I'm guessing its true.
So my last 4 ideas are:
1)Try and flash a new Kernal Image in adb and hope it gets odin to work
2)Push the cw recovery to the phone
3)Run to the library and hope my computer is the problem
4)Pretend vb is wrong and keep trying the download screen thing
Sorry if this is in the wrong section but I guessed it could go here because I need some files....
flash Eugene's froyo that does not brick via Odin. he has instructions in his thread.
...and it's kernel NOT kernal people
Sent from my SGH-T959 using XDA App
kernel, sorry I guess?
Anyhow what if my pc doesnt notice the phone when its in download mode
RPGbig said:
kernel, sorry I guess?
Anyhow what if my pc doesnt notice the phone when its in download mode
Click to expand...
Click to collapse
Download the Samsung drivers, download ODIN, and then just follow the directions in the ODIN thread
Wow
You guys have nothing better to do than flame a newb?
If you spent half the time helping instead of flaming there MIGHT just be some people with a bit more knowledge than they had yesterday.
If you cant say something constructive/helpful --Why bother!
fcbarca17 said:
Download the Samsung drivers, download ODIN, and then just follow the directions in the ODIN thread
Click to expand...
Click to collapse
Push doesnt seem to work. Permission denied or something rather.
As I said in my first odin wont work, yes I did those things like 10 or so times.
You cant expect a newborn to know how to wipe themselves.
RPGbig said:
Push doesnt seem to work. Permission denied or something rather.
As I said in my first odin wont work, yes I did those things like 10 or so times.
You cant expect a newborn to know how to wipe themselves.
Click to expand...
Click to collapse
What do you mean "push doesn't work". Are you trying to push a file via adb? If you are getting permission denied errors, that is because you either do not have root access/permissions to write to the location you are trying to push to, or because the location you are trying to push to is mounted as read-only.
If you indeed have the necessary permissions (i.e., root), then `adb remount` will re-mount the device's partitions as read-write. If adb does not allow you remount the partitions in this manner, it is because you do not have the permissions to perform the duty.
If anyone is going to give any further help, though, you need to give us a bit more information. Can you access the device via adb? Can you boot into either download or recovery? (If you have adb access, you can usually boot into either of those with `adb shell reboot download` or `adb shell reboot recovery`.) Have you attempted to flash anything via Odin? What is the exact wording of the error messages you are receiving?
If you don't provide information, you won't receive any help. Vague responses such as "Permission denied or something rather" are useless because something rather can be any number of things. Also, attempting things without reading all of the information available beforehand is another way to ensure that people will be hesitant to give you help; this forum already has threads about where to locate the stock kernel image.
Also, instead of positing what-ifs such as "Anyhow what if my pc doesnt notice the phone when its in download mode", why don't you try putting your device into download mode and attaching it to a Windows computer with the proper drivers installed and Odin running, and then ask what the next step might be after you have attempted to do something?
People get angry about members flaming newbies for posting mistakes and asking for help, but if newbies looked for answers and read all of the information available before doing something they didn't understand (or only partially understood), then this wouldn't be a problem in the first place.
rpcameron said:
What do you mean "push doesn't work". Are you trying to push a file via adb? If you are getting permission denied errors, that is because you either do not have root access/permissions to write to the location you are trying to push to, or because the location you are trying to push to is mounted as read-only.
If you indeed have the necessary permissions (i.e., root), then `adb remount` will re-mount the device's partitions as read-write. If adb does not allow you remount the partitions in this manner, it is because you do not have the permissions to perform the duty.
Click to expand...
Click to collapse
Goalush Clockwork Recovery so I can flash Bionix.
What Happens:
1. Go into recovery
2. Connect to the phone with adb
3. I type 'adb push c:\update.zip /sdcard'
4. It says 'failed to copy `c:\update.zip` to `/sdcard/update.zip` : Permission denied
I type 'adb remount' its says ' remount failed: No such file or directory
rpcameron said:
If anyone is going to give any further help, though, you need to give us a bit more information. Can you access the device via adb? Can you boot into either download or recovery? (If you have adb access, you can usually boot into either of those with `adb shell reboot download` or `adb shell reboot recovery`.) Have you attempted to flash anything via Odin? What is the exact wording of the error messages you are receiving?
Click to expand...
Click to collapse
Yes, I can get into both.
I've download Froyo that doesnt brick. Unziped and got had the drivers from sansumg set up.
I usually type 'adb reboot download' to get into download mode for odin. Then when the phone shows the android guy with the shovel. Then my computer says that an unrecognized usb device has been connect.
This time I type 'adb shell reboot recovery' and its said
'-exce `/system/bin/sh` failed: No such file or directory (2) -'
rpcameron said:
If you don't provide information, you won't receive any help. Vague responses such as "Permission denied or something rather" are useless because something rather can be any number of things. Also, attempting things without reading all of the information available beforehand is another way to ensure that people will be hesitant to give you help; this forum already has threads about where to locate the stock kernel image.
Also, instead of positing what-ifs such as "Anyhow what if my pc doesnt notice the phone when its in download mode", why don't you try putting your device into download mode and attaching it to a Windows computer with the proper drivers installed and Odin running, and then ask what the next step might be after you have attempted to do something?
People get angry about members flaming newbies for posting mistakes and asking for help, but if newbies looked for answers and read all of the information available before doing something they didn't understand (or only partially understood), then this wouldn't be a problem in the first place.
Click to expand...
Click to collapse
RPGbig said:
Goalush Clockwork Recovery so I can flash Bionix.
What Happens:
1. Go into recovery
2. Connect to the phone with adb
3. I type 'adb push c:\update.zip /sdcard'
4. It says 'failed to copy `c:\update.zip` to `/sdcard/update.zip` : Permission denied
Click to expand...
Click to collapse
You have to be rooted.. But why would you even take the hard way to use clockwork? Just download it from the market..?
I have odin with all the files that will get u to stock of ur phone. Also the froyo files does not brick. So now i exactly dont know what u need. go cows
I messed up my phone and its stuck in a bootloop. I want to put that recovery on my phone so I can flash a new rom.
RPGbig said:
I messed up my phone and its stuck in a bootloop. I want to put that recovery on my phone so I can flash a new rom.
Click to expand...
Click to collapse
If your phone is stuck in a bootloop you need to flash your phone with odin
RPGbig said:
Goalush Clockwork Recovery so I can flash Bionix.
What Happens:
1. Go into recovery
2. Connect to the phone with adb
3. I type 'adb push c:\update.zip /sdcard'
4. It says 'failed to copy `c:\update.zip` to `/sdcard/update.zip` : Permission denied
I type 'adb remount' its says ' remount failed: No such file or directory
Click to expand...
Click to collapse
OK, if `adb remount` isn't working properly, then you have to manually instruct the system to remount the system partition as read-write. This is a little different from other Android devices, because Samsung insists on using their screwy RFS. On my device, the system partition resides at /dev/block/st19. If you can get an adb shell session, opened, you can verify it by running `mount`, and seeing which /dev node is assigned to /system. Then, manually remount the system partition with `mount -o remount,rw -t rfs /dev/block/st19 /system`; this must be done as root.
It does seem a bit odd that you are getting a permission denied error on /sdcard. Are you sure that /sdcard is mounted? You can verify the same way you check what /dev node holds you system partition. On my Vibrant, /sdcard is the mount point for /dev/block//vold/179:1 (yes, that is two slashes after block). So, the command to mount the internal SD card is `mount -o remount,rw -t vfat /dev/block//vold/179:1 /sdcard`.
Now those commands should ensure that you have both your system partition and SD card mounted as read-write. Now you can copy over the update.zip that contains ClockworkMod recovery to the root of your SD card (/sdcard) with `adb push drive:\path\to\recovery.zip /sdcard/update.zip`. I recommend specifying a destination filename for update.zip. Also, sometimes an adb push command requires the trailing / of a directory.
RPGbig said:
Yes, I can get into both.
I've download Froyo that doesnt brick. Unziped and got had the drivers from sansumg set up.
I usually type 'adb reboot download' to get into download mode for odin. Then when the phone shows the android guy with the shovel. Then my computer says that an unrecognized usb device has been connect.
This time I type 'adb shell reboot recovery' and its said
'-exce `/system/bin/sh` failed: No such file or directory (2) -'
Click to expand...
Click to collapse
This last statement looks like either your system partition is not mounted, or that it does not have a shell installed. From an adb shell session, check the /system/bin directory and see if there is indeed a shell binary there (either sh itself, or sh linked to another shell such as bash). If there is no /system, then it means that your system partition is not mounted, and you can follow the steps I previously mentioned to mount the system partition.
RPGbig said:
I messed up my phone and its stuck in a bootloop. I want to put that recovery on my phone so I can flash a new rom.
Click to expand...
Click to collapse
Can you boot into recovery using the VOL_DN and POWER method, or does the adb daemon ever come online during the bootloop? If so, then either boot into recovery from a powered-off state, or use the adb shell to boot it into recovery.
http://forum.xda-developers.com/showthread.php?t=810130
rpcameron said:
OK, if `adb remount` isn't working properly, then you have to manually instruct the system to remount the system partition as read-write. This is a little different from other Android devices, because Samsung insists on using their screwy RFS. On my device, the system partition resides at /dev/block/st19. If you can get an adb shell session, opened, you can verify it by running `mount`, and seeing which /dev node is assigned to /system. Then, manually remount the system partition with `mount -o remount,rw -t rfs /dev/block/st19 /system`; this must be done as root.
It does seem a bit odd that you are getting a permission denied error on /sdcard. Are you sure that /sdcard is mounted? You can verify the same way you check what /dev node holds you system partition. On my Vibrant, /sdcard is the mount point for /dev/block//vold/179:1 (yes, that is two slashes after block). So, the command to mount the internal SD card is `mount -o remount,rw -t vfat /dev/block//vold/179:1 /sdcard`.
Now those commands should ensure that you have both your system partition and SD card mounted as read-write. Now you can copy over the update.zip that contains ClockworkMod recovery to the root of your SD card (/sdcard) with `adb push drive:\path\to\recovery.zip /sdcard/update.zip`. I recommend specifying a destination filename for update.zip. Also, sometimes an adb push command requires the trailing / of a directory.
This last statement looks like either your system partition is not mounted, or that it does not have a shell installed. From an adb shell session, check the /system/bin directory and see if there is indeed a shell binary there (either sh itself, or sh linked to another shell such as bash). If there is no /system, then it means that your system partition is not mounted, and you can follow the steps I previously mentioned to mount the system partition.
Click to expand...
Click to collapse
I tried 'adb root' and then it said 'adbd cannot run as root in production builds'
By shell session do you mean 'adb shell'? No, I dont believe that works because I get 'adbd cannot run as root in production builds'
When you mean 'shell installed' you do I have it installed on the phone? If it isnt is there anyway I could do it now?
`adb push drive:\path\to\recovery.zip /sdcard/update.zip` didnt work and gave me 'c:\update.zip' to '/sdcard/update.zip': Permission denied
Can I flash /system via my pc onto my phone? or Use the external sdcard instead of the internal?
Dude, if your phone is stuck in a bootloop, you HAVE TO FLASH IT VIA ODIN. There's no other work-around.
RPGbig said:
I tried 'adb root' and then it said 'adbd cannot run as root in production builds'
By shell session do you mean 'adb shell'? No, I dont believe that works because I get 'adbd cannot run as root in production builds'
When you mean 'shell installed' you do I have it installed on the phone? If it isnt is there anyway I could do it now?
`adb push drive:\path\to\recovery.zip /sdcard/update.zip` didnt work and gave me 'c:\update.zip' to '/sdcard/update.zip': Permission denied
Can I flash /system via my pc onto my phone? or Use the external sdcard instead of the internal?
Click to expand...
Click to collapse
Why did you try `adb root`? I don't quite understand that.
A shell session would be `adb shell`, yes. On your computer's command line, invoke `adb shell`. You are now in a shell session. What does the prompt look like? Is it "#" or "$". If it is a hash, then you have root access via adb. If it is a dollar sign, then you do not have root access; try running `su` from within the shell session. If the prompt does not change to a hash, then you are stuck for the moment, because you do not have root access via adb, and therefore nearly all of the adb commands will not work.
By "shell installed" I was referring to a shell interpreter installed on your handset. bash is the most commonly installed Linux shell, and sh is usually just a pointer to bash. If your handset does not have either /system/bin/sh or /system/bin/bash (or anything similar), then you have an incomplete system, and it got messed up along the way with something you did.
But, since it seems that you cannot gain root access through adb, and therefore cannot (re)mount your partitions, you are basically limited in your options. All you can really do is put your phone in download mode, and use Odin to reflash a complete system (including a kernel image). I would also recommend that you use the repartition option in Odin to make sure that your partitions are reformatted and you are essentially left with a wiped and clean handest to start with.
(Lack of root access via adb has severely limited your options. You are basically left with Odin as your only avenue of recourse, unless you are willing to disassemble your device to get to the internal SD card.)
Have you opened yours? Is it an actual (micro) sdcard that can be taken out like the external one?
I typed 'adb root because typing 'adb' showed this
adb root - restarts the adbd daemon with root permissions
so I guess that was what you ment by root.
When I type 'adb shell' all it gave was - exec '/system/bin/sh' failed: No such file or directory (2) -
You need to stop trying to do it the hard way and just use Odin. If your phone is not being recognized then you need the correct drivers. Once installed, you should be back up and running within 5 minutes. Stop lollygagging and fix your phone already.
Hi, I've been trying to move all my game data from my internal SD card to my larger external SD card with no joy.
I have used condi's AIO tool to install init.d support, which reported as successful, but when I follow obicom's instructions as listed in POST #43 of this thread http://forum.xda-developers.com/showthread.php?t=1490116&page=5
I repeatedly receive the message "Operation not permitted."
I have used both ADB Shell and Terminal Emulator with the same result.
I'm obviously doing something wrong as other people appear to have had success with these instructions, I just don't know what.
Here's what I've done: (on rooted ICS from condi's AIO tool)
Installed init'd support "successfully"
Moved all data from sdcard/Android/data over to sdcard2/game_data
In ADB Shell/Terminal Emu. entered the following line;
mount -o bind /sdcard2/game_data /sdcard/Android/data
and this is where I get the "Operation not permitted" message.
Any ideas?
Once you're in shell, before running the mount command, run the command 'su' first (without the quotes). Your prompt should change from $ to # and try running the mount command again.
Explained: In most Linux systems, unless the fstab has been specifically setup to do it with the user option, filesystems can only be mounted by root. In rooted versions of Android, the normal user can elevate into a root prompt with su, then allowing you to mount and unmount any filesystems.
Ahaaa
Awesome! Can't believe it was something so simple, thanks, and thanks for explaining the reason.
I must have somehow totally missed the "su" instruction in the other thread.
Half of my games work, the other just seem to need re-installing which is no big drama.
Again, thanks, it's much appreciated mate.
Script?
agc93 said:
Once you're in shell, before running the mount command, run the command 'su' first (without the quotes). Your prompt should change from $ to # and try running the mount command again.
Explained: In most Linux systems, unless the fstab has been specifically setup to do it with the user option, filesystems can only be mounted by root. In rooted versions of Android, the normal user can elevate into a root prompt with su, then allowing you to mount and unmount any filesystems.
Click to expand...
Click to collapse
Hi, is there a way I can create a script (or the like) that would do this, and other similar directory changes, at boot?
At present I need to enter these manually each time the tablet starts, which isn't too much of a drama for me but when other people use it they end up downloading the data all over again when they start a game.
Thanks
There is an app available on Google Play called Script Manager (which can be used to create scripts to run at boot as su (which mount command require), which should do what you need. You'll need to use a plain text editor (I believe there is one included with Script Manager) to enter each of the mount command you want to run on a separate line. Then set the file to executable (chmod +x scriptname), and add it to Script Manager.
Note that I haven't used it in a while, so follow whatever instructions Script Manager gives you. They're probably more up to date.
agc93 said:
There is an app available on Google Play called Script Manager (which can be used to create scripts to run at boot as su (which mount command require), which should do what you need. You'll need to use a plain text editor (I believe there is one included with Script Manager) to enter each of the mount command you want to run on a separate line. Then set the file to executable (chmod +x scriptname), and add it to Script Manager.
Note that I haven't used it in a while, so follow whatever instructions Script Manager gives you. They're probably more up to date.
Click to expand...
Click to collapse
Okay thanks, yet again, I'll give it a try today.
Operation not permitted
Hi,i wanted to change my mac address on phone and even with that su command i get "operation not permitted" (my phone is rooted)...even apk named overclock for android could not grant root acces...in root checker my phone is rooted(and i have been rerooting it but still same).AND THERE IS NO FIX ON INTERNET
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
Just wanted to create a quick thread for my fellow noobs. This is my first time using terminal and this is my first nexus device and I was able to unlock the bootloader, flash a recovery, flash the necessary files and flash a custom rom without any issues.. For the more experience guys, please take it easy on me if I put something incorrect Please make sure you have the Android SDK and adb/fastboot otherwise all of this is irrelevant. Also want to thank the community for all the help and giving me all this information as I was learning on the fly. Made the experience super easy and a lot of fun.
You can download the adb and fastboot here... Thanks @corbin052198 : http://forum.xda-developers.com/nexu...d-xda-t3226767
Disclaimer: I am not responsible for any damaged devices. These are simple commands and pretty hard to screw up so if you do I'm not responsible.
Here are the commands and what they do:
adb devices - shows adb devices (this is important, if it doesn't see your device then don't do anything else until is does)
adb reboot bootloader - reboots into bootloader
fastboot reboot-bootloader - reboots bootloader
fastboot flashing unlock - unlocks bootloader
fastboot flash recovery <filename>.img - flashes recovery (TWRP)
fastboot flash vendor vendor.img - use command to flash vendor image
fastboot flash boot boot.img - use command to flash boot image
fastboot flash system system.img- use command to flash system image
Note: If you are having issues with the commands try using "./" I didn't have to but you might. Ex: ./fastboot flash vendor vendor.img
PSA: 1) Make sure your terminal is pointed in the fastboot folder so you can type cd desktop then cd fastboot if that's where the folder is then you can type ls which will show what's in that folder to make sure you are in the right folder.
PSA: 2) If flashing Vendor, Boot and System files, I'd recommend doing it one by one and rebooting the bootloader after each one to be safe..
PSA: 3) A lot of PSA's, I know.. When flashing anything, instead of typing out vendor.img for example, you can just drag it from the folder and drop it into terminal.. Ex: fastboot flash vendor then drag the vendor.img from the fastboot folder..
Hope this helps..
dont all the commands need to be preceded with "./" (without quotes)
ie to flash vendor image w filename vendor.img
./fastboot flash vendor vendor.img
Sent from my Nexus 6P using Tapatalk
Nope not anymore. I actually got an error when typing the "./"
johnandbodhi said:
dont all the commands need to be preceded with "./" (without quotes)
ie to flash vendor image w filename vendor.img
./fastboot flash vendor vendor.img
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
this also helps
http://forum.xda-developers.com/nexus-6p/development/tool-nexus-tools-2-8-featured-xda-t3226767
Will add to thread. Thank you.. This is where I added adb
dwertz said:
this also helps
http://forum.xda-developers.com/nexus-6p/development/tool-nexus-tools-2-8-featured-xda-t3226767
Click to expand...
Click to collapse
Very simple to install to where you can use the commands ANYWHERE instead of having to CD to the folder..
Open a terminal
Make sure Java is installed "java -version" (Should say Java version "x.x.x")
Download the SDK from Google. (Don't worry about Android Studio, just the SDK)
Extract the folder and move it to ~/.android-sdk
In the terminal type "cd ~/.android-sdk/tools
In the terminal type "./android"
Install the Android SDK Tools, Android SDK Platform-Tools, Android SDK Build-tools, Android Support Library
Modify your shell (.bash_profile, .bashrc, .zshrc, ect...) to include (below the PATH variable): export PATH="/users/<username>/.android-sdk/platform-tools:$PATH"
Close your terminal and reopen it. Upon doing so, you should be able to use fastboot and adb in any folder you'd like.
Following these steps make it quite a bit easier to install factory images or sideload ROMs since you can use the fastboot/adb commands directly within the ROM or factory image folders. Let me know if you have any questions
Just FYI, the commands are the same across all platforms. The "./" would be if you are accessing the in the current directory, if you were using a portable version or didn't install things properly so they are in the path.
Dupe thread, we have all this info pinned in general.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
So you don't really need to put the "./"? I didn't use it at any point and had no trouble at all.
designgears said:
Just FYI, the commands are the same across all platforms. The "./" would be if you are accessing the in the current directory, if you were using a portable version or didn't install things properly so they are in the path.
Dupe thread, we have all this info pinned in general.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
XavierD8188 said:
So you don't really need to put the "./"? I didn't use it at any point and had no trouble at all.
Click to expand...
Click to collapse
I had to use ./ when typing commands to unlock my bootloader. The regular commands without ./ gave me errors.
Sent from my Nexus 6P using Tapatalk
It was the opposite for me. "./" gave me errors but when I just typed the commands without it, worked perfectly fine. Weird..
wwevoxnj said:
I had to use ./ when typing commands to unlock my bootloader. The regular commands without ./ gave me errors.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
There are at least 2 other threads with this same information, therefore, I'm closing this one.
Hi,
I should want to use rsync to copy new and modified files (and only these ones) on an USB key but it's not in my Androïd version even if I have an AICP rom which uses Cyanogenmod 12 (I've red rsync is in Cyanogenmod). I use this command on a Linux box in a .sh script and it's convenient. I would do the same thing on my phone with using SManager if it's possible.
I've looked for this command for Androïd but a search only returns Rsync Backup which is not anymore on Google Play. It's an application, I don't know if I can get a command to use it in a script. I've also done searches on the forum and if I could see guys use it, I haven't found how they get it.
Does somebody knows how to get it?
Thank you .
I've found a binary command :
http://ptspts.blogspot.fr/2015/03/how-to-use-rsync-over-adb-on-android.html
It's necessary to install it in a system directory otherwise I can't give it execute permissions. I put it in /system/bin