yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] fun_:
sorry, I couldn't guess anything from "you update.zip not starting on my device (with my boot.img)".

all different devices are different because they are different. files are different among different roms but some files can be shared. I have no idea which file in my update.zip is OK on your tablet because I can't try on your tablet. please try & investigate detail, then you can get answer.

EDIT:

as a matter of fact, currently I'm using same vendor files except kernel and sensors.so on NOVO8, A907 and IDXs/CTs. but it doesn't promise anything for different devices. different device is different.

and of course my CM9 is not perfect. there are some issues on some devices. it may be caused by shared vendor files, it may not.

EDIT2:

I realized it's not good to post something while I'm feeling fatigue :( sorry
[Miscellaneous Android Development] kupyxa4444:
you change files, like device.mk for everyone device?
[Miscellaneous Android Development] fun_:
I don't change any file in device tree unless something need to be changed.
[Miscellaneous Android Development] murigny64:
Hello fun_ .

Nothing about wrong orientation on idx10/ct1002/xtab100 ?

best regards
[Miscellaneous Android Development] fun_:
nothing for everything due to almost no free time :(
[Miscellaneous Android Development] kupyxa4444:
I started CM9 on my device, but I have problems: touchscreen works like mouse or touchpad, g-sensors and wi-fi not work. Can you tel me, what files are responsible for them. I based on Digma 7
[Miscellaneous Android Development] $$pasquale:
New GPL Code released from Amlogic

http://openlinux.amlogic.com/download/linux/GPL_code_release/2012-08-03/
[Miscellaneous Android Development] kupyxa4444:
fun_, can you help with my problems?
[Miscellaneous Android Development] jeff18ms:
Hi Fun,

We Hope that you could support the Onda vi30 Dual Core Tablet, it share's the same processor.

Let me know if it's possible and there's any files you need.

Thanks,

Jeff
[Miscellaneous Android Development] stane1983:
Seems it's natively only for MX (m6 - dual core) platform.... And it's 3.0.8 kernel.

Any changes anybody made for m1/m3 platform to be able to compile? :)
[Miscellaneous Android Development] LucusFocus:
Can you make this available for Mediacom 960i/962i ?? Please
[Miscellaneous Android Development] c.martinez.lozano:
I'm Developing SuperOSR for Ramos W10 (Nvsbl P4D v3) tablet.

I need to make BT working, but the rest works perfect with an own kernel(resized partitions, net stadistics, faster yaffs, new usb gadget "mtp/ptp, etc" and more) I'll upload the changes of my kernel and config for W10 this or the next week.

https://github.com/CML/amlogic_m1_kernel

EDIT: BT now works! I made a MOD of amlogic ICS ROM with all working with my kernel(i need to remap remote.cfg but detect the keys"inverted" of the remote)

Regards.
[Miscellaneous Android Development] paulreminder:
Glad to see you are making progress on this project. I have the original Ramos W10 8GB for China market and am willing to do the test as soon as you release the ROM.

Best regards.
[Miscellaneous Android Development] sas007:
Onda vi40 dual core desperately needs this
[Miscellaneous Android Development] kupyxa4444:
how you repair BT? I make CM9 for TEXET TM-7021 (Russian version Ramos W10 with 4GB), and BT not works too. Navishade with originsl ramos can`t start it. As I know, devices differ only memory. Can test it?
[Miscellaneous Android Development] finlessbob:
Fun_

May I ask a couple questions please. I am new to AMLogic architecture.

I have done many ROMs for RK tablets including porting CWM. However this is my first AMLogic tablet. I have learned a lot and have already made my own custom ROM. What I have learned with this ROM architecture is there is no ROM flash tool from PC. Everything is done through recovery and using update.zip and scripts? Is that correct? There is no "tool" to force flash if a mistake is made?

If so then messing with recovery can cause a permanent brick? Is there no way to recover?

So I have learned to take apart boot.img (same as uimage file) and I can also take apart and repack uimage_recovery. However while trying to port CWM to this tablet, if mistakes are made, and recovery does not work, how do you unbrick? Can you simply put back the stock files

factory_update_param.aml

uimage

uimage_recovery

What is the boot structure? u-boot.bin is the master and if it is OK it will recover?

Again I want to work on porting CWM for this tablet but since I do not know about the booting of this AMLogic architecture I want to know if unbrick is possible and how the boot process works.

Any help is appreciated and thanks for all the work you have done here already. I have learned a lot from it. :good:

Bob
[Miscellaneous Android Development] c.martinez.lozano:
BT have conflict because ttyS1 is reconigzed as GPS.

Disable GPS and reboot.

On init.rc you need to use hciattach_usi (get the binary and libbluedroid.so from an ICS Amlogic ROM)

add on init.rc the hciattach service(see on an stock amlogic rom the init.rc file for permissions, etc on hciattach_usi rfkill, etc):

service hciattach /system/bin/logwrapper /system/bin/hciattach_usi \
-n -s 115200 /dev/ttyS1 bcmbt 460800
user root
group bluetooth net_bt_admin
disabled

Regards
[Miscellaneous Android Development] sas007:
Onda VI40 dual core latest firmware if anyone wants to play.

https://rapidshare.com/files/1508197439/Vi40D_v1.2-0810.rar
[Miscellaneous Android Development] kupyxa4444:
hm...not works...And, can you help me porting my ROM on Ramos W10? As I said, I have russian version ramos w10 with 4GB. On my device it works, but on original w10 not works.

http://narod.ru/disk/59543461001.688de90855a9d8e83ef5cb40cdc3bdaa/Unnoficial%20_CM9_for_TM-7021.zip.html
[Miscellaneous Android Development] c.martinez.lozano:
Ummm i have an W10 tablet with 8GB resistive, m1 cortexA9, 512Mb RAM with no camera.

You need to unpack and repack your kernel (you can see psquare repository or hillbeast kernel repository for this).

I will upload to my dropbox my v3 initramfs directory i used for SuperOSR(maybe works on CM9) and initramfs for an Stock ICS Amlogic ROM I'm porting. I need to reorganize things, remove duplicate code, etc but it works.

Tell me your device specs and give me your kernel .config file.

You can get it with adb: adb pull /proc/config.gz .

What is the status of your ICS ROM? what works and what not.

Regards.
[Miscellaneous Android Development] kupyxa4444:
my device is clone w10, but have 1 memory chip. no more differs You can started original ROM for my device and I can started original ROM for you device. On my rom not works BT, video deckoding (havn`t sound in films in stock player) and he not started on original w10. I took original boot.img and repack it with initramfs from CM9 by fun_. system folder from CM9 by fun_ too
[Miscellaneous Android Development] navishade:
c.martinez.lozano Thx for link. I downloads it. But when i try build sirius_recovery i get uImage 3.6 mb . But in sirius CWM is 3.0 mb. Help me please build CWM from source.

I can change him for Ramos W10.

Regards
[Miscellaneous Android Development] c.martinez.lozano:
If you are using sources from naobsd, to make HW accelerated video playing works, you only need to add propietaries.

libmediaplayerservices.so

all amplayer.so you see

libstagefright.so

For BT, you need to add this propietaries.

hciattach_usi binary

libbluedroid.so

sdptool binary

On BoardConfig.mk activate

BOARD_HAVE_BLUETOOTH := true
BOARD_HAVE_BLUETOOTH_BCM := true

And on init.rc put the hciattach service as i post before.

You need to set permissions for hciattach_usi, rfkill, ttyS1, and make a symlink of btaddr (copy and paste all from your stock ROM inir.rc).

I forgot to say you need to add sdptool binary and services on init.rc sorry.

Remember, you need to disable GPS and reboot, because GPS try to use ttyS1 (BT Serial)

Regards.
[Miscellaneous Android Development] kupyxa4444:
to take these files it is better from original rom to my device (android 2.3.4) or from original ICS to Digma IDX7?
[Miscellaneous Android Development] fun_:
as far as I know, no "tool". there is a way to make bootable SD card. some tablet vender provides rescue/repair SD card image.

refer http://openlinux.amlogic.com/index.php/Arm/Boot_Loader/How_to_burn_a_uboot_to_board

don't flash anything until it is really necessary. u-boot can read uImage_recovery from SD card.

the file named u-boot.bin on FAT partition on SD card is just a file. it does nothing until it's flashed to flash memory or written in SD card as a bootable image.
[Miscellaneous Android Development] fun_:
I'm sorry I couldn't answer it.
[Miscellaneous Android Development] kupyxa4444:
now I reparing BT and video
[Miscellaneous Android Development] Re-Mi:
Hi,

I tried your irobot a907 files to flash on my "forgotten" irobot tablet.

Unfortunately the tablet doesn't boot beyond the android picture (no boot loops it just turns off)

Is there something i missed ?

Kind regards,

Michel

never mind... just dropped it, now it's dead.. only backlight turns on ..
[Miscellaneous Android Development] c.martinez.lozano:
Good to see my tips works :)

Regards
[Miscellaneous Android Development] kupyxa4444:
hm..I can`t repair BT and HW accelerate video.
[Miscellaneous Android Development] finlessbob:
Thanks for the info.... some things on AMlogic web site seem a little unclear as to what is actually happening. I have read all this already. Sure wish a boot road map existed that explained the boot process.

OK so if I undersatnd you correctly. Once I have made a CWM recovery and flash it if it does not work, I can simply put back onto sdcard the stock recovery and it will boot it? Nothing else needed?

Thanks Fun_ for the help.

Bob
[Miscellaneous Android Development] murigny64:
Hello Bob.

I made a tuto on my forum to unbrick CT amlogic with a SD.

Look at this (in french, sorry):

Prérequis:

- Votre tablette doit etre une CT704 V1 V2 ou V3, CT1002, ST1001

- Un PC sous Windows

- Une carte microSD de taille inférieure ou égale à 4Go

- Un lecteur de carte microSD sur votre PC

- Une ROM valide et fonctionnelle pour votre modèle de Tablette

Principe:

La tablette démarre grace à un secteur d'amorcage dans lequel se trouve un "BIOS" nommé u-boot. Si celui-ci est détérioré par un flash incomplet ou corrompu, ce secteur devient alors défectueux et la tablette ne peux plus démarrer.

La tablette cherche alors un u-boot valide sur la carte SD et démarre à partir de celui-ci.

Nous allons donc créer une SD spéciale qui va contenir tous les fichiers necessaires au démarrage de la tablette, mais qui va également "reflasher" l'u-boot valide dans celle-ci.

Ce u-boot devant se trouver sur les 1ers secteurs de la SD pour que cela fonctionne, cette carte aura donc un format spécial avec 1 partition de "démarrage", 1 partition dans laquelle se trouvera les fichiers de la ROM dont le fameux u-boot et une 3eme partition non allouée.

Grace à l'image disque fournie et le logiciel USB Image Tool, nous allons restaurer ces partitions sur la SD.

On commence

1 - Téléchargez l'archive suivante: http://fr.packupload.com/487BDVLYFFC

2 - Dézippez la dans un repertoire de votre PC,

vous devez avoir 2 fichiers:

* CT-Revival.img

* usbit.zip

3 - Dézippez usbit.zip et installez le programme "USB Image Tool"

4 - Inserez votre SD dans le lecteur de carte PC

5 - Lancez "USB Image Tool"

6 - Choisissez votre lecteur SD (ne vous trompez pas de lecteur !) (1) puis cliquez sur restore (2)

7 - Choisissez l'image disque "CT-Revival.img" (3) puis ouvrir (4)

8 - Confirmez votre choix (5)

9 - L'image va alors etre restaurer sur la carte SD

10 - Une fois terminé, fermez USB Image Tool.

11 - Sur votre bureau, faites un clic droit sur "ordinateur" ou "poste de travail" selon votre version windows et choisir "gerer".

12 - Rendez vous sur l'onglet "gestion des disques"

13 - Sur la section concernant votre lecteur SD, vous devez avoir 3 partitions, une 1ere de ~15Mo vide, une 2eme de ~460Mo FAT32.

14 - Fermez la gestion d'ordinateur et ouvrez l'explorateur de fichier.

15 - Sur votre lecteur SD, vous devez avoir 2 dossiers et 2 fichiers: aml_autoscript et factory_update_param.aml

16 - Copiez les fichiers de votre ROM (u-boot-512M-UartB.bin - uImage - uImage_recovery - update.zip) sur la carte SD.

17 - Inserez votre SD dans votre tablette.

18 - Faites un reset "trombone"

19 - Appuyez simultanément sur "VOL -" et "POWER" pendant au moins 20s jusqu'a ce que l'écran s'allume legerement et relachez.

20 - Vous allez voir apparaitre soit une barre de progression (pour une ROM 2.3.4) soit le menu recovery

21A - Dans le cas de la barre de progression, attendez la fin de flash puis retirez aussitot la SD

21B - Dans le cas du menu recovery, procedez au flashage de votre update.zip puis retirez votre SD avant de rebooter.

Votre tablette est sauvée

:star: :star: :star:
[Miscellaneous Android Development] c.martinez.lozano:
Hi

Not needed all this process.

On m1 devices you only need to put on root of sdcard aml_autoscript - factory_update_param.aml - u-boot-512M-UartB.bin - uImage - uImage_recovery - update.zip

Press reset 15secs, afert this, without charger, press vol- and power.

Regards.
[Miscellaneous Android Development] murigny64:
@ martinez:

aml_autoscript don't work with ICS and if you are full bricked, aml_autoscript don't work to.
[Miscellaneous Android Development] c.martinez.lozano:
Maybe CT1002 use another uboot that change this.

I use Froyo uboot for Ramos W10 W12 and Gadmei T820 and works as i say.

I'll experiment with your tips :)

Regards.
[Miscellaneous Android Development] navishade:
c.martinez.lozano

Help me build CWM or Kernel for W10 8gb please. I cant build from your source. i get error from /firmware/broadcm4319, when i try build kernel (I did not make any changes)
[Miscellaneous Android Development] c.martinez.lozano:
W10 uses /firmware/broadcm4329

for some reason, when I upload the firmware to github, disappears when

You can get it from GPL kernel on openlinux.amlogic.com (have a downloadble kernels).

Regards.
[Miscellaneous Android Development] finlessbob:
Thanks for the unbrick steps! Very helpful!

Still have some questions. Fun_ said "do not flash anything until needed"

So if I am working on my own CWM, will uimage_recovery always boot from SDcard vs the recovery flashed on the NAND?

How do you make that work?

murigny64, again thanks for the tutorial. Had no problem with the French translation!

The files being mentioned I do not have exactly. Specifically these 2.

u-boot-512M-UartB.bin

aml_autoscript

I have the stock ROM and this is what is in it:

u-boot.bin

uimage

uimage_recovery

update.zip

In the update.zip is:

META folder (no worries here I know what this is)

recovery folder

-> etc

-> install-recovery.sh (I know what this is)

recovery-from-boot.p

System folder (I know what this is)

aml_logo.img (I know what this is)

boot.img (I know waht this is same a uimage)

bootloader.img

logo.img (I know what this is)

I do not have the files you mention?

I assume u-boot.bin is the u-boot-512M-UartB.bin??

But what about the auto script file?

Thanks a ton for the help!

Bob
[Miscellaneous Android Development] murigny64:
@finless

On most amlogic platforms, when boot, system always look at aml_autoscript on sdcard.

if there is no sdcard or aml_autoscript, boot process continue normaly.

aml_autoscript is a bin/script and it's proceed some work like:

format, partitionning and start u-boot (it's depend of script in it).

the aml_autoscript in my tuto is starting u-boot from sdcard instead of u-boot on nand, it's very usefull because if your u-boot or system on nand is corrupted (half or full brick), you can revival your tablet by this method.

on ct1002 or novo8, u-boot is named u-boot-512M-UartB.bin. all of your other files are same.

sorry for my bad english.

ps: your are finless from freaktabs ? ;)
[Miscellaneous Android Development] murigny64:
Do you know this builds ? :

http://sourceforge.net/projects/wive-ng/files/wive-ng-idx/

From Sfstudio (ddixlab.ru)

ICS 4.0.3 Firmwares with kernel 2.6.34. I've the IDX10 one on my CT1002 and it work very fine (better than v8 from winaccord/wayteq)

:)
[Miscellaneous Android Development] fun_:
I think most amlogic devices which support script act as

1. power on

2. CPU loads u-boot from NAND

3. u-boot loads & run script on SD card

3.1. script loads & flash u-boot (just updating, not to run)

3.2. script loads & run uImage_recovery on SD card

4. recovery installs update.zip to update android

and some other devices which don't support script,

1. power on

2. CPU loads u-boot from NAND

3. u-boot loads & run uImage_recovery

4. recovery installs update.zip

with bootable SD card, "2. CPU loads u-boot from SD card" and others are same.

sorry if I'm wrong.
[Miscellaneous Android Development] fun_:
u-boot (or script loaded by u-boot) can load & run uImage_recovery from SD card. you may need to press & hold some key to run "recovery boot mode".

anyway, flashing your own CWM is not necesarry to boot it.
[Miscellaneous Android Development] Re-Mi:
Hi all,

I revived my irobot a907 (is it the same as a a9 ?), the screen works again..

But now it boots into cwm if i start it up. When i try to format everything it gives an error cannot mount /emmc/ so i think i wrecked it.

Or does anyone got a possibility to fix it (i would prefer to install cm9 on it, but any running android version will do). I browsed the web multiple days now but i cannot find any original firmware of unbrick methods.

Hope someone can help me.

Kind regards,

Michel
[Miscellaneous Android Development] finlessbob:
Your English is fine! Better than some Americans I know :)

Yes I an Finless from FreakTab now playing with my first AMLogic tablet (Ramos W13Pro). Been a Rockchip nut till now :)

I have to say, making ROMs for this architecture is a HECK of a lot easier than Rockchip! Well except if you want to get custom and start writing updater-script's from scratch! Did my first one today to patch my first custom Ramos ROM to support Flash11.

Fun_

Thanks for sure for this info. That is what I am looking for. Yes my tablet requires a key sequence to boot from SDcard. I assume this is why the stock ROM does not have aml_autoscript?

However makes me wonder if putting that on sdcard will do the same as your instructions state. e.g. it will launch the recovery_cwm from SD?

So I think I am ready to start without worry of a brick thanks to all the responded :)

You guys have been VERY helpful and I cant thank you enough! :good:

Bob
[Miscellaneous Android Development] fun_:
I already explained how files on SD card are loaded/run. what is unclear for you? you need confirmation?

I(we) can explain ONLY general scenario. "how it works" may vary among devices. I can't explain any "absolutely sure" thing because I don't have your device. if you want to make it "sure", please try yourself on your device.

I forgot one thing, with a key to run recovery, u-boot will try to load uImage_recovery on SD card, and if it's not available, u-boot will try to load recovery from recovery partition on flash.

last one is the simplest way to install update.zip(only update.zip is needed on SD card). it's also used to do factory reset(wipe) from android menu.(this one should be same as other non-amlogic android devices)
[Miscellaneous Android Development] finlessbob:
OK so I played around just to see and start undertanding how this work for me. I like to test and know :)

If I put your uImage_cwm and aml_autoscript on my SDcard and then power off.

Then holding the buttons needed on my Tab to boot recovery, alas it did not work which I figured it would not. initil logo shows up and hangs.

If I put my stock uImage_recovery on the sdcard and rename it to uImage_cwm. It boots that recovery no problem but gives an error it cannot find factory_update_param.aml. Expected. So I am pretty sure it is booting the recovery from SDcard. In fact I know it is due to below.

So I figured OK good. Time to take apart the stock recovery and see if I can rebuild it back.

I unpacked my uImage_recovery no problem. I could see all the files in intramfs, etc.

Rebuilt it and put it on sdcard again with your aml_autoscript and renamed uImage_recovery that I repacked to uImage_cwm.

Well darn.... first bump in the road, me rebuilt recovery hangs :(

I made no changes other than unpack and repack.

I am using 2 scripts I got from this post somehere (cant find them now). They worked fine on boot.img (uImage) and I was very successful unpacking that and repacking boot.img. Made my own mods to init.rc etc.. No issues. Tablet boots with my repacked boot.img and uImage

.

So now I am stumpped why the scripts did not make a good repacked recovery?

Any tips?

I am reading through all the posts here trying to find the answer. Trust, I do try to do the research and learn myself but sheesh 98 pages in the thread! Maybe a clue where to look? :)

Bob
[Miscellaneous Android Development] fun_:
sorry, difficult to read where is the point repacked recovery hanged. and also I can't look the script you used and uImage files before/after repacking.

(sorry, I'm very busy and just reading/writing messages take my time. I can't promise I can answer further discussion)
[Miscellaneous Android Development] fun_:
interesting. can you point me the thread?

and... oh... iDx7 type5?... sigh...
[Miscellaneous Android Development] murigny64:
@fun_

thread is : http://www.ddixlab.ru/forum/viewtopic.php?f=19&t=2501

russian forum, very hard to translate and subscribe :eek:
[Miscellaneous Android Development] fun_:
very nice. it seems he is porting kernel source from amlogic to iDx7/10. it may be good for CT704 (especially old one).

(but I can't find his source)
[Miscellaneous Android Development] fun_:
http://bbs.ainol.com/forum.php?mod=viewthread&tid=16354&extra=page=1

source for ainol aurora2/elf2. currently downloading so I don't know what is included.

EDIT:

http://files.androtab.info/mirrors/ainol/

mx0525ainole1release.tar.gz (elf2) is mirrored. it seems it contains Android 4.0.3(IML74K), kernel 2.6.34, and (probably) proprietary sources and binary blobs

EDIT2:

mx0525ainole3release.tar.gz (aurora2) is mirrored too. I guess difference is very few. I'll compare them.

EDIT3:

difference between these 2 are very very few. only board dependent parameters are different. actual codes are same.

no need to download both unless you really need both information.

btw, it seems very nice. probably my effort will be obsoleted soon. I hope someone make better things with these sources...
[Miscellaneous Android Development] finlessbob:
I havea feeling based on read that in this script, this is the problem

mkimage -A arm -O linux -T kernel -C lzma -a 80008000 -e 80008000 -d Image.new -n

More research and searching.... Seem to recall Fun_ posted a different value like 82000000 or something? 98 pages to look through :(

Bob
[Miscellaneous Android Development] fun_:
you can check parameters by "mkimage -l original_uimage".

I still do not have any actual information about image you are using, so I can't answer about it. if you really need useful answer from other people, please give actual input, output, file, etc, not only your feeling.
[Miscellaneous Android Development] c.martinez.lozano:
Hi, i'm working on it with SuperOSR sources. (Similar framework than CM9).

At the moment i'm testing media and works really better than with the "stock" propietaries. (HW accel on more TV channels "flashplayer 11" and more smooth video playback on 1080p videos).

I see the code needed to use hacked FlashPLayer 10 from Amlogic, but i'll not integrate it because a lot of TV channels works now with HW accel and the other can be used with useragent IPAD.

Today i'll test 3G dongle implementation :) (Before source filtration i was make it work, detect SIM and signal, but no data connection)

I'll commit my advances this week at https://github.com/SuperICS, https://github.com/SuperICS-Devices and https://github.com/CML/amlogic_m1_kernel

Sorry about my bad english.

Regards.
[Miscellaneous Android Development] navishade:
c.martinez.lozano

Hello. What about Ramos W10 or NVSBL p4d v3? This kernel is buildable ?

Regards