Related
hi
recently got an Olivepad VT-100 and got it rooted and clockwork Mod installed on the same and also backed up my rom .
So For those who have been struggling to get the same done like me here is a simple guide
1. Get to know that The Olivepad VT - 100 is the same as
these Models : Viewpad 7 Cherry Mobile Superion, Commtiva Linx N700, Spice MI700, and Camangi FM600( found this out the hard way)
for rooting it go here
[TOOL] Viewpad 7 Backup, Root & Recovery - By lakehousetech (thanks to his help i got it done)
Link : http://forum.xda-developers.com/showthread.php?t=1015005
one more link for the same : http://android.modaco.com/topic/324042-clockwork-recovery-for-mi700n700viewpad-7/
For recovery via Rom Manager see below link (note i have not used this)
Link : http://hucqim80.blogspot.com/2010/12/how-to-install-clockworkmod-recovery.html
the superoneclick did not work for me so for those who have the same problem
take ginger break APK from attached install it on ur Olive pad and bang it works with one click
IT worked for me
thanks to Nos0x for this find
Note : i did not use ADB for the commands as im not comfy with the same
i used Terminal emulator from the Pad for the commands
update : i also tried re flashing my nand backup via CWM it worked fine for me
This worked for me as i was willing to take the risk
so remember the risk is always yours and im not responsible if you brick ur phone or anything
Important : on rooting & getting CWM 1st do a Nand backup of ur original Stock rom before trying to flash any rom.So u are always safe & can go back to ur stock Rom
Working roms on our OLivePad
hi
the below roms i have tested and the same works fine on the olivePad
pls see below links for details
1. [ROM] Viewsonic Viewpad 7 Froyo Enhanced - By lakehousetech
Link : http://forum.xda-developers.com/showthread.php?t=1008673
2. [DEV]|[ROM]+[KERNEL] [FM6 Variant (Spice Mi700 / ViewSonic ViewPad 7 etc.)] by-tj_style
link : http://forum.xda-developers.com/showthread.php?t=1093440
get the update zip from here on above post : http://forum.xda-developers.com/showpost.php?p=14384918&postcount=39
3.[14.JUL.11][ROM]CleanViewpad7 v1.0|APPS2SD|CWM - by skink123
link : http://forum.xda-developers.com/showthread.php?t=1168562
this one is real good it has app2sd and ie all u installed apps are on ur SD thus more space on ur phone Storage
note : install this after installing the ROM for 154MB phone storage(only for this ROM ie no : 3 not the others OK)
take attachment from below link and flash via CWM
Link : http://forum.xda-developers.com/showpost.php?p=15669899&postcount=2
4. one more good rom take it from here : http://forum.xda-developers.com/showpost.php?p=15970641&postcount=17 - by googlehome
and add this attachment : http://forum.xda-developers.com/showpost.php?p=15669899&postcount=2
via CWM after flashing the rom and u will have App2sd & 157MB free on ur phone storage
i have been using this for a long time and realy loving it
5. http://forum.xda-developers.com/showthread.php?t=1224825 - By amalgamation
this one is real good it has apps2sd in the rom and works good
Note : for 3 & 4 combos & 5 to work u need to have Ext4 partition done
u can do it via CWM
enjoy enjoy
Problem & Solutions with the Pad
hi
well this was a problem i faced today and got a solution for the same wanted to share the same
Problem
well after flashing a custom Rom today i read about a apps2sd which was available in the market i downloaded the same to my pad installed the APK on my pad its some application which said it will enable JIT i clicked on it and the phone restarted and then i had just a blank screen ie it was on but blank
i kind a got a heart attack as my pad is only around a month old but then life is about taking risk right or it wont be fun
solution
i remembered i did some thing similar to what is given below long time back with my old gene aka HTC 3400 win Mob i just tried the same & it worked for me
hold the volume buttons both of them & power button & while holding these two u need to restart by inserting a pin in the restart small hole available next to the mike
on doing the above u will be able to got to ur CWM and u can re install the os u want again that what i did
just sharing my experience in case u get the same problem
thanks
hari
reserverd
hi
for future use
Hi, I tried using super one click but I always fail to root.
This is the message I get
QUOTE
SuperOneClick v1.6.5.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
202 KB/s (5392 bytes in 0.026s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
ROOTED
Pushing busybox...
1033 KB/s (1062992 bytes in 1.004s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/mtdblock7
OK
Reading OS Version properties...
Version: 2.2
OK
Remounting system with read-write access...
OK
Pushing su-v2...
failed to copy 'D:\SOC\su-v2' to '/system/bin/su': No space left on device
OK
chmod su...
Unable to chmod /system/bin/su: No such file or directory
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Copying busybox (/system/xbin/)...
cp: write error: No space left on device
OK
Pushing Superuser.apk...
failed to copy 'D:\SOC\Superuser.apk' to '/system/app/Superuser.apk': No space left on device
OK
Pushing Superuser.apk... (/data/app)
failed to copy 'D:\SOC\Superuser.apk' to '/data/app/Superuser.apk': Permission denied
OK
Remounting system with read-only access...
OK
Running a SU test...
Test failed!
FAILED
ro.wifi.channels=
ro.product.cpu.abi=armeabi
ro.product.model=V-T100
ro.build.tags=release-keys
ro.build.version.release=2.2
ro.build.description=msm7627_surf-user 2.2 FRF91 5009_3_16R release-keys
ro.product.brand=Olive
ro.product.device=vt100
ro.build.version.incremental=5009_3_16R
ro.build.type=user
ro.build.date.utc=1290718061
ro.board.platform=msm7k
ro.product.name=V-T100
ro.product.board=V-T100
ro.build.user=user
ro.build.display.id=FRF91
ro.build.version.codename=REL
ro.build.product=V-T100
ro.build.id=FRF91
ro.build.version.sdk=8
ro.product.manufacturer=FIH
ro.product.locale.region=US
ro.build.date=Fri Nov 26 04:47:41 CST 2010
ro.product.locale.language=en
ro.build.host=cmcsservice
ro.build.fingerprint=Olive/V-T100/vt100/V-T100:2.2/FRF91/5009_3_16R:user/release-keys
/QUOTE
Any help would be helpful..
Actually my problem is that I now cannot enter recovery mode at all.. It keeps hanging at the enter recovery mode screen..
Regards
Milton
hi
try the gingerbreak apk attached
install it in ur pad and clik on it it worked for me
super one did not work for me too
for clokwork see the link i gave for rommanager
goodluck
haree said:
hi
try the gingerbreak apk attached
install it in ur pad and clik on it it worked for me
super one did not work for me too
for clokwork see the link i gave for rommanager
goodluck
Click to expand...
Click to collapse
Hey, thanks for the speedy reply. I did try gingerbreak. However, though I can install ans use most root required apps, when I try to manually install busybox, it fails.. is this normal.
the bigger problem is, ever since I first tried to root my olivepad, I am not able to enter recovery mode at all. I am trying all of this just so I can use rom manager and flash into the default rom. ;-( any help here? is there any way I can restore the olivepad to stock. If I unroot the system, can I give it for service under warranty?
miltonben said:
Hey, thanks for the speedy reply. I did try gingerbreak. However, though I can install ans use most root required apps, when I try to manually install busybox, it fails.. is this normal.
the bigger problem is, ever since I first tried to root my olivepad, I am not able to enter recovery mode at all. I am trying all of this just so I can use rom manager and flash into the default rom. ;-( any help here? is there any way I can restore the olivepad to stock. If I unroot the system, can I give it for service under warranty?
Click to expand...
Click to collapse
hi
if u successfully root & get the CWM installed u can do a nand back up and restore the same but when u root u have the risk of loosing ur warranty
but to my knowledge if u re install the OS and re install ur original image
u need to backup ur oringal via ADB or termemulator pls read lakehousetech thread for details i have given the link in the 1st page
u can do this via terminal emulator or ADB & remove the superuser
i dont think the service guys go all that deep in checking if u have rooted and if u dont have the super user on ur pad i Dont thing they will find out u have rooted ur pad . this is as per my experience in India with my phone
the risk is always yours Kindly note im not responsible for any issues u get into with your Pad
note ; read this too : http://android.modaco.com/topic/324042-clockwork-recovery-for-mi700n700viewpad-7/
it also has info on how to install busy box u can also get a busy box installer from the market
Hi Haree,
Thanks a lot for all the info. And honestly, I don't need to be reminded that me breaking my pad is not your mistake ;-)
Well, I will sure look into the new link.
BTW, I needed a little help understanding something. When I saw the size of my OS partition, I realized there is only 32kb of space left. Due to this, I am unable to use oneclick to copy new files into the OS partition from the sd card. Could you please confirm whether this lack of space in the OS partition is normal?
And I am still searching for a way to force modify the OS partition using some other manual pc oriented means (not the exe's). Would be grateful for your suggestions.
Again, thanks a lot.
Regards
Milton
hi
sorry i dont get ur question are u talking about SD ext part
if so it is better to have more than 1GB and u can do this with CWM
im not a techie i just read and do the needful to get the rom flashed on my phone/Pad
for more tech questions i think its best u ask lakehousetec or any of the rom developers
miltonben said:
Hi Haree,
Thanks a lot for all the info. And honestly, I don't need to be reminded that me breaking my pad is not your mistake ;-)
Well, I will sure look into the new link.
BTW, I needed a little help understanding something. When I saw the size of my OS partition, I realized there is only 32kb of space left. Due to this, I am unable to use oneclick to copy new files into the OS partition from the sd card. Could you please confirm whether this lack of space in the OS partition is normal?
And I am still searching for a way to force modify the OS partition using some other manual pc oriented means (not the exe's). Would be grateful for your suggestions.
Again, thanks a lot.
Regards
Milton
Click to expand...
Click to collapse
Hey Haree,
that's ok, I will try and ask around. Seems that no body else is facing the same issue. I might end up giving this for a service..
Thanks again
Milton
olive pad stuck in auto RTM background
any one can help me ... my olivepad can do any thing in auto RTm background ...
i have try to do what screen order to push power on and pressing down volume , but it not make different ... my droid just keeping in black background that writen as auto RTM ... how i solve this problem ....
help me please
blank screen .auto rtm
any one can help me ... my olivepad can do any thing in auto RTm background ...
i have try to do what screen order to push power on and pressing down volume , but it not make different ... my droid just keeping in black background that writen as auto RTM ... how i solve this problem ....
blank screen .auto rtm
any one can help me ... my olivepad can't do any thing in auto RTm background ...
i have try to do what screen order to push power on and pressing down volume , but it not make different ... my droid just keeping in black background that writen as auto RTM ... how i solve this problem ....
cikal0n7th said:
any one can help me ... my olivepad can't do any thing in auto RTm background ...
i have try to do what screen order to push power on and pressing down volume , but it not make different ... my droid just keeping in black background that writen as auto RTM ... how i solve this problem ....
Click to expand...
Click to collapse
hi
assuming u have ur CWM installed and that u have done a nand backup of ur original rom read the below link it is the 3rd post of mine do it and u can u can do a nand restore
http://forum.xda-developers.com/showpost.php?p=15851144&postcount=3
do this :
hold the volume buttons both of them & power button & while holding these two u need to restart by inserting a pin in the restart small hole available next to the mike
on doing the above u will be able to got to ur CWM and u can re install the os u want again that what i did
Thanks Haree, I used GingerBreak and it looks like it worked. I have installed Terminal Emulator and Im not able to get the soft keys to come up, I tried keeping menu button pressed. Can you tell me what is the keyboard software you are using and how you were able to bring the keyboard up in any of the terminal emulators? Also tried the busybox installer, it reports an unexpected error and closes.
bmvbab said:
Thanks Haree, I used GingerBreak and it looks like it worked. I have installed Terminal Emulator and Im not able to get the soft keys to come up, I tried keeping menu button pressed. Can you tell me what is the keyboard software you are using and how you were able to bring the keyboard up in any of the terminal emulators? Also tried the busybox installer, it reports an unexpected error and closes.
Click to expand...
Click to collapse
hi
Terminal Emulator use it in portrait mode to work NOT land scape Mode
press the menu button and u will get toggle keypad press this and u can use the same.busybox u need to get the tool from market and install 1.7
Make sure u take a Nand backup before trying any rom
good luck
haree said:
hi
the below roms i have tested and the same works fine on the olivePad
pls see below links for details
1. [ROM] Viewsonic Viewpad 7 Froyo Enhanced - By lakehousetech
Link : http://forum.xda-developers.com/showthread.php?t=1008673
2. [DEV]|[ROM]+[KERNEL] [FM6 Variant (Spice Mi700 / ViewSonic ViewPad 7 etc.)] by-tj_style
link : http://forum.xda-developers.com/showthread.php?t=1093440
get the update zip from here on above post : http://forum.xda-developers.com/showpost.php?p=14384918&postcount=39
3.[14.JUL.11][ROM]CleanViewpad7 v1.0|APPS2SD|CWM - by skink123
link : http://forum.xda-developers.com/showthread.php?t=1168562
this one is real good it has app2sd and ie all u installed apps are on ur SD thus more space on ur phone Storage
note : install this after installing the ROM for 154MB phone storage(only for this ROM ie no : 3 not the others OK)
take attachment from below link and flash via CWM
Link : http://forum.xda-developers.com/showpost.php?p=15669899&postcount=2
4. one more good rom take it from here : http://forum.xda-developers.com/showpost.php?p=15970641&postcount=17 - by googlehome
and add this attachment : http://forum.xda-developers.com/showpost.php?p=15669899&postcount=2
via CWM after flashing the rom and u will have App2sd & 157MB free on ur phone storage
i have been using this for a long time and realy loving it
Note : for 3 & 4 combos to work u need to have Ext4 partition done
u can do it via CWM
enjoy enjoy
Click to expand...
Click to collapse
The megaupload site is blocked is Malaysia, can someone upload to another site pls. Thanks in advance
syaah said:
The megaupload site is blocked is Malaysia, can someone upload to another site pls. Thanks in advance
Click to expand...
Click to collapse
hi
tell me what u want of the 4 and ill load it to my drop box and give u
here is one i think this googlehome rom take it from below link
link : http://dl.dropbox.com/u/10031257/CleanViewpad7_signed_v1.0.zip
Hi Hari,
I'm Rahul.. Have been trying to get hold of a good Custom ROM for my Olivepad for quite sometime now (Must have been blind to have ignored your posts earlier on).
Presently I'm running it on the Stock ROM rooted with z4root with CWM 2.5.1.2.
I have ROM Manager v 4.3.3.3 installed and tried to load CM 7.0.2 and later the other updates but every time it kept saying that there was an error in loading the ROM.
Assuming that I have done everything (rooting and loading CWM) correctly I'm going ahead with the ROMs suggested by you (VPAD7_signed.zip).
Shall keep this post updated on my success (or failure)
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
hey everyone long story short i rooted my tablet a while back and started having problems so i flashed a new rom and the wifi isnt working.
I went to androidfiles.org and clicked nabi 2 and download wifi-fix, ota update and stock zip rom and flashed those three zip files ( i compressed them) in twrp.. its booting up and everything but wifi isnt working. ive read a lot of peeps are having wifi probs. I have a xda link for my exact device and you guys tell me wut the hell im supposed to do. its got all kinds of stock roms and ota updats and stuff,... which one do i use wtf do i do. should i go one at a time from lowest to biggest, do i even need ota updates or w./e that is?!?!?!? please help guys my chirstmas is becoming a nightmare... its my only internet source.. i had to come all the way to the dang library for this crap.. please help!!!!! heres the link that might give u guys an idea on how to help.. heres the stock roms and stuff
http://forum.xda-developers.com/wiki/Fuhu_nabi_2 thank you!!!!!
duuude im baked said:
hey everyone long story short i rooted my tablet a while back and started having problems so i flashed a new rom and the wifi isnt working.
I went to androidfiles.org and clicked nabi 2 and download wifi-fix, ota update and stock zip rom and flashed those three zip files ( i compressed them) in twrp.. its booting up and everything but wifi isnt working. ive read a lot of peeps are having wifi probs. I have a xda link for my exact device and you guys tell me wut the hell im supposed to do. its got all kinds of stock roms and ota updats and stuff,... which one do i use wtf do i do. should i go one at a time from lowest to biggest, do i even need ota updates or w./e that is?!?!?!? please help guys my chirstmas is becoming a nightmare... its my only internet source.. i had to come all the way to the dang library for this crap.. please help!!!!! heres the link that might give u guys an idea on how to help.. heres the stock roms and stuff
http://forum.xda-developers.com/wiki/Fuhu_nabi_2 thank you!!!!!
Click to expand...
Click to collapse
Thought I would share some info I found when I ran into the wifi problem on my daughter's nabi. I did some searches on the internet and the typical answer I found for solving the wifi issue was "reset the device" or "unroot and return to stock rom - flash all updates and reroot". Being a glutton for punishment, and the fact I didn't want to reset the device, I searched and searched and was able to fix my daughter's wifi without doing a reset or unroot/reroot. Before I get into it I wanted to mention that wifi failures can happen for a number of reasons so while this worked for myself, it may not work for you.
Some prerequisites:
Most importantly; you need a rooted device. If you do not have root access you will not be able to write files or access the commands to fix the issue I am about to outline.
Some knowledge of linux would be helpful, but not necessarily required.
Lets get started:
Warning! It goes without saying but I will say it anyways - you can mess up your nabi by rooting it. Some of the commands below could mess up your nabi bad. If this scares you then you probably should not proceed any further. I am not responsible for any damage you do to your nabi.
Commands are listed between ' and ' - do not use the ' when inputing the commands.
Note: The first two/three steps are not necessary but they do give you insight as to how I was able to determine my problem. If following this doesn't fix the problem for you the logcat output may give you some important info that you can google that may help you fix your particular problem.
Note: Steps 5 and on can be skipped if you have a text editor (vi or nano) on your device. If you have a text editor loaded simply edit the conf file directly.
1. You will need to run the command 'adb logcat' in a command-line window and in your appropriate directory. Adb is available as part of the android sdk but can also be found stand alone since most people do not need the sdk.
2. Try to turn on the wifi. You should see the output of your adb logcat window scroll some data. If the wifi is not attempting to turn on at all sometimes you can move between the settings options then go back to the wifi settings and move the slider. If you cannot get your wifi to turn on you can scroll the window up and attmept to find the data from when the device started up. In the output you should see lines that talk about wlan0 and probably something that says "failed" somewhere. In my case I could see where the wlan0 enabled but then a few lines down it said something about "Line: 25 failed" and "failed to parse file".
3. The file is actually a configuration file used by the wifi kernal module/driver. In my case this file had become corrupted.
4. Set adb in root mode (won't work if the device does not have root access) by running 'adb root' at the command-line. You may need to click on an "allow root permission" window on the actual device after running this command.
5. Run 'adb pull /data/misc/wifi/wpa_supplicant.conf' from command-line. If this does not work then do the following:
a. Run 'adb shell' from command line.
b. 'su'
c. 'cat /data/misc/wifi/wpa_supplicant.conf' - copy the output from the command and paste into a text editor (see note in step 6 on why NOT to use notepad).
d. Save the file as wpa_supplicant.conf, preferrably in the same diretory as adb.
e. 'exit' twice should exit you from the adb shell and return you to your command-line. If all else failes a "ctrl-c" should drop you out of adb.
6. Use a text editor to open wpa_supplicant.conf. The file should be located int he same directory as adb. If you are using Windows I would strongly suggest you NOT use notepad. Notepad will typically change all the EOLs (End Of Line) from \n to \r\n which will really mess things up worse.
7. In the file you should see "network={" entries. There maybe one entry, there maybe many entries. You can remove all lines between "network={" and "}" including the latter themselves. If you see your 'home' network listed you can leave it as the only entry and make sure its priority is set to 1 but it maybe better to remove it as well just in case it contains part of the corrupted data.
8. Save the file.
9. Do 'adb push wpa_supplicant.conf /data/misc/wifi/wpa_supplicant.conf' from command-line. If this does not work then do the following:
a. Run 'adb push wpa_supplicant.conf /sdcard/wpa_supplicant.conf' from command-line.
b. Run 'adb shell'
c. 'su'
d. 'dd if=/sdcard/wpa_supplicant.conf of=/data/misc/wifi/wpa_supplicant.conf'
e. Do 'exit' twice to exit the adb shell. If all else fails then a "ctrl-c" should drop you ot of adb.
10. If the wpa_supplicant file was corrupted then the wifi should now be able to enable and you should now be able to connect to a network.
I hope this is helpful to at least a few people.
So,
SGS users, here is my another thread, for guys, who want to help devs of our sgs community.
Devs asking you to get a logcat and give?? Yes it helps a lot for devs if you give logcat to solve problem. So dont wait till devs ask you to get a logcat! Just give them a logcat when you tell them this/that doesnt work. This way theirs and yours time will be saved and unnecessary posts will be avoided.
Now i will give you simple steps to do it. There are two main ways to do a logcat, 1. within android device, and 2. through adb using PC.WITHIN ANDROID DEVICE METHOD:
1. Logcat within android device can be done in one of two ways, through a Logcat app: Difficulty --> Very Easy
Here are two good apps: aLogcat or Catlog
Both of these programs can dump their logs to a text file, which is very useful for debugging. Or, you can do it in terminal emulator (same rules as running through adb(see below))
2. Through Terminal method: Difficulty --> Almost Easy
Install Android Terminal Emulator app from Play Store..
Open terminal app you just installed..
Enter these commands:
After every command press ENTER/SUBMIT button
Code:
su
then accept the superuser popup message[it comes only first time if you select checkbox "remember the choice"]
Code:
logcat -v long > /sdcard/test.log
Or use this command:
The -v long puts the text in a nice format that is more easily readable. The *:W will search for all warnings, errors, and fatals, while the *:S will silence everything else.
So essentially, u will have a .txt file that has a log of all warnings and up, nothing else, and it'll look pretty too!
Code:
logcat -v long *:W*:S > /sdcard/filename.txt
now press home button to minimize the terminal..
and do the task which is giving problems/ whichever task log you need to give to dev..
then drag the notification bar..
select terminal app in it..
now press and hold "Volume down button" and touch c button on keyboard.
This will stop the command..
now use this command twice
Code:
exit
Now app will get closed. go to sdcard to find test.log file.. upload it to here so that dev can access it..
Thank you for reading it with patience hope you can get logcat now..
Note: if you are stuck in boot and want to take logcat.. READ LOGCAT FROM ADB METHOD BELOW.. the above one is simple method for these tasks for eg.. if you are having some force close of app/lag etc.. then after entering second command press enter and then use home button to minimize terminal.. dont worry it will take log.. now open that app and once it gives force close then click on it and then open terminal again and press volume down button + c to terminate command.. then use exit command two times... done.. now go to sdcard and find a.txt file
From PC[i.e, ADB] LOGCAT METHOD :Difficulty --> Medium
There is an advantage here. As doing this way, you can start using logcat when your device boots. There are 2 ways here again..
PREPARATION:
In your android device, go to settings --> applications --> development -->
Check USB Debugging
Make sure your device driver is already installed otherwise install kies software which will install drivers too.. Get kies from This LINK
You need to download this ADB.zip file i made to your system.. Download link
Extract the ADB.zip file from any applications like IZarc/7Zip/winzip/winrar.
ADB USAGE INSTRUCTIONS:
Then go to Android folder.. inside that you should find 3 files.. Now open a command prompt or terminal in that path..(wherever you extracted it.. use cd command)
Then inside that path.. type
Code:
adb logcat > filename.txt
Or
Code:
logcat -v long > /sdcard/test.log
Or
Code:
logcat -v long *:W*:S > /sdcard/filename.txt
Now perform tasks in android device of which you need to give logcat for the devs. Then use CTRL+C to end the command.
Now find the filename.txt inside the Android folder which has logcat. Upload this file and give link to dev..
The full list of options that can be used with logcat command is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the *:W with any other letter from above to get more info.
CREDITS
CRESITS ;
I) @Niku-Droid
II)www.google.com
III) XDA Threads, as this information is taken up from threads of XDA only
Oh! I missed someone, Send me a PM
hmn nice thread
most guides are user friendlyy if the ppl read a few sentences
just like all other threads the self aclaimed noobs will just ignore this thread and when asked for logcats theyll just post how to take logcat when they can just type that up at google or had read here
also im not able to take logcat at boot can u post up how to do that
Sent from my GT-S5282 using Tapatalk
T3snake said:
hmn nice thread
most guides are user friendlyy if the ppl read a few sentences
just like all other threads the self aclaimed noobs will just ignore this thread and when asked for logcats theyll just post how to take logcat when they can just type that up at google or had read here
also im not able to take logcat at boot can u post up how to do that
Sent from my GT-S5282 using Tapatalk
Click to expand...
Click to collapse
hmm... dont worry bro, we will give them link to this thread when they ask this silly question n hv u tried taking logcat using adb, i m sure that it can take logcat as soon as device is booted
Niku-Droid said:
hmm... dont worry bro, we will give them link to this thread when they ask this silly question n hv u tried taking logcat using adb, i m sure that it can take logcat as soon as device is booted
Click to expand...
Click to collapse
of course i used adb
i want to take logcat while star is booting
but device doesnt show in adb until the booting is complete
When the projection function is turned on, the phone will reboot.
Sorry, I am a Taiwanese, so my English is not very good. I hope you can understand.
My whyre will restart whenever the projection function is turned on. This problem is very annoying because I use it often.
I hope that ArrowOS can be more perfect in Chinese culture, otherwise it will be difficult for my newbie, and how do you solve the 4G signal problem?
I use a lot of OS, but their 4G can't work, which makes me very troubled. As a geek, I want to learn how to deal with this.
The system you made is really great, I like it very much, I hope you will surpass PE.
how can solve no internet problem?
how can solve no internet problem?
Network problem on moto g4 plus of version Arrow Os 9
Doesn't access network problem while installed
The connection to my smartwatch dosnt work.
the bug that I found for the moment was that it does not allow changing the file transfer mode when connecting the usb cable to the computer
Niku-Droid said:
Кодlogcat -v long > /sdcard/test.log
Click to expand...
Click to collapse
Today I am going to show you how to install a custom boot animation onto your LG G Watch device! Assuming the principles of the Android Wear file system are the same across all devices, it should *technically* work on the Moto 360 and Gear Live as well.
This is my first tutorial, so I do apologize if I don't go in depth enough in some parts, or am unclear. Please let me know and I will explain anything that does not make sense!
IMPORTANT!!!!!
The bootanimation MUST have the filename of (without quotes) "bootanimation.zip" otherwise it will not work
Getting Started
1) First you must make sure that your device is rooted with a custom recovery.
Rooting - https://www.youtube.com/watch?v=shGqwLp4teE
Custom Recovery - http://forum.xda-developers.com/g-watch/development/recovery-clockworkmod-recovery-lg-g-t2833877
2) Secondly you need to have adb installed and working, as well as the usb drivers for your device
Tutorial - http://forum.xda-developers.com/showthread.php?t=2588979
2) Once you make sure that you have all of that set up, and are comfortable with adb transfer, we can get started
Installation
1) To start with you must have the zip of whichever boot animation you desire to have on your watch, and for convenience, place it in the same folder that your adb files are in (for me it was C:\adb)
2) Having your watch connected to your computer and booted into your recovery, go ahead and open a command prompt and navigate to the folder you have your adb installation in (C:\adb)
3) From here you mist make sure that System is mounted in your recovery, then on your computer type in (without quotes) "adb push C:\adb\bootanimation.zip /system/media"
that's it!
If this helped you, please let me know! And let me know if there is anything you need help with.
(I attached a picture of my device booting up)
Credits
Google is my friend, giving me these amazing devices and awesome platforms! The adb transfer service made the mod possible.
Hours spent figuring this out and searching files and folders to make sure everything was in order, I take credit for having the first tutorial on changing the LG G Watch boot animation, although if I am wrong I will promptly change this. Thank you XDA-Developers for all of your help
More information please
what do you want to know?
How are you writing to the system, I have tried this over and over and it won't work.
So to start off simply, you need to have your watch connected to your computer, boot into the bootloader, and install a custom recovery. Then after that boot into the recovery and you can copy files over. Have you gotten all of that done before attempting this?
I have done everything like in the op , that's why I ask.
I'm not sure why it's not working for you then. What are you getting when you try to write over the files in command prompt?
It is saying it's a read only system, and I have even tried from root shell.
Okay yeah I was having an issue with that too. For some reason if I just kept trying, it eventually worked I know how it sounds, but that's my solution for now! Try going back to the bootloader and into recovery again, and you can try transferring the file while in the file manager, or on the recovery home. Different things might yield a different result! I apologize if I'm not helping
Also go to device manager and make sure that when in the bootloader and recovery it has the Google driver installed and not a yellow triangle without a driver
One more thing, when in the recovery you must check and see if System is mounted. It helped for me to make sure it was checked under Mount (TWRP).
Ok bro thanks, mounting system worked, now gotta edit all of my images.
Yeha my bad man! Didn't even think about that, I had to spend a lot of time tweaking to get it working I'll add it to the guide. Glad you got it
Also once you mount the system you can push the zip directly to the /system/media/, no need to manually move it after that. Now it's time to start pumping out custom boot animations....
Can you post the stock desc.txt for me?
cbrown245 said:
Can you post the stock desc.txt for me?
Click to expand...
Click to collapse
for the stock boot logo i did not have a backup unofrutnately.... but i did go to the thread originally outlining pulling the animation off the watch! copied this from their dump desc.txt
1080 1080 24p 1 0 part0 p 0 0 part1
and i am attaching the zip for my animation im using as well if that helps at all.
hey man I have a couple questions about this procedure. I know this thread is not current and that may be my problem. adb is not recognized in recovery for me, it returns no device found. also I was curious why you put your path in the command if the zip is in the folder with adb? tia.
also I reeaallly want that kate upton bootani, way cool!!!