Database Users

[GUIDE] how to make a flashable package (update.zip)

thanks to this page for teaching me: http://www.robmcghee.com/android/creating-an-android-update-zip-package/
note: although i am copying this from the page, this isnt a straight ctrl+c, ctrl+p from it. ive rewritten it with slightly more english. ok alot more.
before we start, grab ppcgeeks auto signer here, or nothing will flash anyway. its the easiest method since its drag, drop, and click.
also i recommend 7-zip but its not necessarily needed.
first step, make the folder structure.
ive included prebuilt updates to make it a little faster for you. they contain no actual files, just the appropriate folder structure and update script. they must be resigned if you add files and expect to flash them.
if what your looking for isnt included, make a folder and name it "workdir". this will contain your work.
this is just to make it easier to organize all your stuff. if you feel so inclined you can name it whatever you want, it doesnt really matter.
next youll need to make folders inside the workdir according to where your flashing stuff, ie if your flashing wallpapers youd need to make a structure that looks like this: "workdir/system/customize/resource"
next to make the update-script. this tells the system what to do.
first make this folder structure: "workdir/META-INF/com/google/android"
make sure you capitalize "META-INF"
now put a text file into the "android" folder and call it "update-script"
the easiest way to code it would be to copy this into it:
Code:
show_progress 0.1 0
copy_dir PACKAGE:(x) (X):
set_perm_recursive 0 0 0755 0644 (X):(y)
show_progress 0.1 10
replace the (x) with the directory in the root your flashing to in lowercase, ie system or data or sdcard.
replace the (X)'s with the same thing as (x) except in UPPERCASE such as SYSTEM or DATA or SDCARD.
replace the with the next directory in lowercase like media or app or customize.
note: if your adding to the root of (X) folder then leave this blank, no spaces or anything.
if your flashing an app it should look something like this:
Code:
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
set_perm_recursive 0 0 0755 0644 SYSTEM:app
show_progress 0.1 10
after youve done that, save and close the file. now you need to take the extension off of the text file. simply delete the .txt at the end of the file.
if there is no extension showing, make sure you have "hide extensions for known file types" unchecked in tools> folder options> "view" tab.
second to last step! compress the workdir contents into a zip file, not the actual workdir though. it should look like this inside the zip: "update.zip/(folders)" not "update.zip/workdir/(folders)"
finally, sign the zip with the auto signer and put it into the root of the sd card.
boot into recovery and flash it up! with a bit of luck, it should work.
if you have any questions, problems, or concerns just post them. i have instant subscription to this thread and will be notified every 30 min when my evo fetches my mail.

Thanx for this thread!
Ok, my app should be installed in /system/app/
but is it possible to include in the same (app)update-script: delete /data/app/xxx.apk?

What directories do boot animations go into?
Awesome thread and thanks btw.

Foxwolfe said:
What directories do boot animations go into?
Click to expand...
Click to collapse
/data/local/

rori~ said:
Ok, my app should be installed in /system/app/
but is it possible to include in the same (app)update-script: delete /data/app/xxx.apk?
Click to expand...
Click to collapse
honestly, i couldnt tell you for sure but i dont see why you couldnt
Foxwolfe said:
Awesome thread and thanks btw.
Click to expand...
Click to collapse
thanks

I keep getting a syntax error. I am trying to flash silent.mp3 so i can select that in my notifications, because for some reason it does not have that option :/
can you let me know where I went wrong?
have tried both
set_perm_recursive 0 0 0755 0644 SYSTEM:media
set_perm_recursive 0 0 0755 0644 SYSTEM:notifications
but to no avail

what was the whole code in the update-script?
did you use the example i posted?
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
set_perm_recursive 0 0 0755 0644 SYSTEM:media
show_progress 0.1 10

daktah said:
what was the whole code in the update-script?
did you use the example i posted?
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
set_perm_recursive 0 0 0755 0644 SYSTEM:media
show_progress 0.1 10
Click to expand...
Click to collapse
yeah, sorry for not making it clear. Im kinda rote-learning this atm, I did a straight copy of your notifications script into my flashable-zip. when that didnt work I tried it with line3 modified as a stab in the dark.
what does the entire folder structure look like? if I am changing notifications is it /system/media/audio/notification where I put the files?

i believe it is
Code:
workdir.zip/
_system/
__media/
___audio/(files).mp3
_META-INF/
__com/
___google/
____android/update-script
if you still cant get it going i can assemble it for you

Just wanting to be sure here because Ive read the first post a few times and still can't tell. On the root of the update.zip I am supposed to create the folder structure that I want it to flash too. (ie. media/audio/ringtones) and then place the actual file that im flashing in that directory. (ie media/audio/ringtones/newring.mp3) At this point then the whole .zip dir would look like:
update.zip
__media/
_____audio/
_______ringtones/
__________newring.mp3
__META-INF/
_____com/
_______google/
___________android/
_______________update-script
_____CERT.RSA
_____CERT.SF
_____MANIFEST.MF
Then just sign the .zip and flash it... Is this correct?

You got it

Wow sounds real complex just to add an mp3 for a ringtone. I know if you create a file on sdcard
media/
audio
alarm
notifacation
And then put the file you want for what you want into the folder you want it for it will show in dropdown menu so you can select it.
Been trying to get googles auto app builder program to force download the sdk for devices so i can start there first. Want an app that forces mms to the sprint max of 5mb send limit and not stocks 2mb or handsents 1.2 limit. Will doing this according to thread give me an app that does this? What would i need to change? (guess you could make it faster than trying to teach me but still wonder)

jpwhre said:
Wow sounds real complex just to add an mp3 for a ringtone. I know if you create a file on sdcard
media/
audio
alarm
notifacation
And then put the file you want for what you want into the folder you want it for it will show in dropdown menu so you can select it.
Click to expand...
Click to collapse
thats true but installing saves space on the sd card and makes it load instantly instead of waiting for the sd card to be prepared
jpwhre said:
Been trying to get googles auto app builder program to force download the sdk for devices so i can start there first. Want an app that forces mms to the sprint max of 5mb send limit and not stocks 2mb or handsents 1.2 limit. Will doing this according to thread give me an app that does this? What would i need to change? (guess you could make it faster than trying to teach me but still wonder)
Click to expand...
Click to collapse
what? im lost lol

On wm arcsoft had a setting in the app that lets you change settings and change size limit to 500kb. You can also make these changes in regeditor. Android doesn't have a registory nor does there seam to be an app to install that will allow these changes. Wondering if your tutorial thread would allow the building of an app and what would i need to change to do this. Googles app builder program doesn't come preinstalled with any sdks and on a slow connection i can't get it to download.

if your saying building an app as in coding and assembling one then no as this is just a guide to make an installable zip to flash with ra or clockwork. youd need to use the sdk tools and such for that. but this guide should allow you to install pretty much anything into the nand from ringtones to apks and the like.

daktah said:
i believe it is
Code:
workdir.zip/
_system/
__media/
___audio/(files).mp3
_META-INF/
__com/
___google/
____android/update-script
if you still cant get it going i can assemble it for you
Click to expand...
Click to collapse
finally got adb to stop sh***ing itself. did it that way.
thanks for the help anyway.

so, i'm by no means an expert at this... but i was trying to make an update.zip for wallpapers. i've attached what i did, if you could take a peak at it and give me a pointer, that would be awesome!
path to my wallpapers...
using launcherpro
data/app/com.fede.launcher-1.apk/res/drawable-hdpi
data/app/com.fede.launcehr-1/apk/res/drawable-mdpi

granted, I'm trying to flash a theme, but it seems like the process and folder/file structure would be the same.
I've followed the steps one by one, but after flashing the .zip in recovery and rebooting, everything looks the exact same as it did before! I figured I would start with framewor-res, and see if I could get that to work before I started working on all the other images, but even after modifying all images, straightening out the .9.png's, and compiling everything correctly in Eclipse, I get nothing.
I have no effing clue what's going on, any ideas?

im on a mac, any suggestions for what i can use to sign the zip? i have apk manager and thempro and they can both sign apps but i dont know if its okay to use them to sign a flashable zip

Hi man!
I'm not do a Update.zip yet with your tutorial, but i have a question:
some Update.zip have a file named updated-binary together with update-script, how i do that file? because when i try to flash via OpenRecovery say's that coul'd not find that file: update-binary...
Sory for my english, i'm from Argentina, and i try not to use Google Translate...
Regards!!!
PS: Great work with this tutorial!!!

[solved] SD write failing for rooting

So my NookTouch finally arrived!
But I'm having trouble writing images to a SD card.
It's a 16gb micro SD HC class 6 card...
i thought that would be ok?
Windows Image writer says `Not enough space` so I used dd for windows but after this the disk isn't readable. The same for linux (remembered to use bs=1M).
edit::
Solved answer - confusion using windows tools, don't really know why it wasn't working but it could have been due to an incorrect dd command on linux beforehand.
You need to write to /dev/sdcardRoot (aka masterbootpartition) rather than /dev/sdcard1 (partition1). After you've rooted though and written the image you can format the card and partition the SD card.

I had a similar problem with my 5 in 1 built in card reader.
Some apps would say "not enough space" while some would write the img without complaints, but the Nook wouldn't boot it, no matter what.
I ended up pushing the image file to my phone (X10) and using that to write the image to the sd card, worked perfectly.

Are you using WinImage?

Thanks for fast reply!
Verfied the image is ok with winimage.
Wierd. After writing TouchNooter to sd card via the sd card drive in the laptop the card is no longer readable. After putting it in the NookTouch the nook can't see it either and I can't get linux mount it. But... with the card in the Nook and USB plugged in I get 2 drives come up; `Nook` and `TouchNooter`
Nook software version is `1.0.0`.
In linux the disk looks like this:
Code:
Disk /dev/sdb: 251 MB, 251641856 bytes
8 heads, 60 sectors/track, 1023 cylinders
Units = cylinders of 480 * 512 = 245760 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
Disk /dev/sdc: 16.0 GB, 16038952448 bytes
128 heads, 32 sectors/track, 7647 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 38 77808 c W95 FAT32 (LBA)
/dev/sdc3 7 7 0 0 Empty
Partition 3 does not end on cylinder boundary.
[email protected]:/media/WindowsStorage/download/nook$
With WinImage I can read the contents of the image but if I try to write it I get `The current image format is not supported by the disk drive` --- ***correction, it's writing now after I reformatted the card***....
now testing...
`nook is starting up...` aha `Rooted forever!!` hmm.. seems to be taking a very long time....
ok, nothing's happening... i wonder if it's turned on or crashed! ok trying usb now... ah, got a different device recognised by windows (omap3630).. trying apb etc...
perhaps I should be using noogie only for the touch though... hmm...
right, need to find the omap3630 driver in the android sdk to get those 7 partitions mounted... this is my first android device I've used... no usb driver listed in the sdk under available packages.. perhaps I should try linux...

Ok, got the shell. What next to install? I'll have a search.
The confusing thing was the android sdk. It took me a while to find the USB driver comes through via google's distro service on Windows and that the adb command is in there too. The location of the USB driver has also moved to the google/usbdriver subdirectory now too.
Next stop, trying to install some android .apk's...
Thanks one and all!
edit::
I'll use this as a diary for a moment to note what I'm finding until I'm sure enough to put it in the Wiki.
In general I'm finding some things that work on the color work on the touch but not all. VNCServer works but we only have /dev/input/event0-2 - the server notes the input clicks but doesn't do anything about them ("injectTouchEvent (x=0, y=0, down=1)" even when specifying -k trying each of those events...
this could be related to the NookTouch using infared rather than a touchscreen. Perhaps there's a new B&N dev file in there rather than a custom resident running program or something.
VNCViewer on the NookTouch seems to work but personally I couldn't get it to connect to my server. I'll try linux to confirm.
WiFi locker doesn't work, complaining that's it's an incompatible app: http://nookdevs.com/Nook_WiFi_Locker the wiki is the only place for a download link, there appears to be no mention now of it on the nooktools page:
Code:
E:\ProgramFiles\androidSDK\platform-tools>adb install "h:\nookWifiLocker.apk"
503 KB/s (40277 bytes in 0.078s)
pkg: /data/local/tmp/nookWifiLocker.apk
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
E:\ProgramFiles\androidSDK\platform-tools>
Plugging in my USB stops the nook turning off while using adb though. Need to turn off wifi and connect over usb...
Nooklets look like a great idea - could it be scripted to allow direct access to webpages saved via scrapbook extention for firefox?
Other things to improve the wiki:
-suggest putting adb.exe in path
Any problems?
-because I don't have any other android devices I can't see how to get access to apk's from android market... http://phandroid.com/2011/02/04/sol...-android-phones-associated-with-this-account/ "No phones associated with this account"
This confused me:
adb -d shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb push NookColorTools_0.2.apk /system/app
adb reboot
Click to expand...
Click to collapse
- was that an old way to install apps before `adb install`? Because any app I install via adb install isn't listed in /system/apps, yet it is installed because if I try to install again it tells me so...
edit: note for myself regards the confusion over google accounts, gmail and missing libaries:
Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY]
To set this up correctly, there are 2 key files that need to be copied to the system:
com.google.android.maps.xml
com.google.android.maps.jar
These files are located in the any of these google app packs:
http://android.d3xt3r01.tk/cyanogen/gapps/gapps-gb-20110120-signed.zip
http://goo-inside.me/gapps/gapps-gb-20110120-signed.zip
http://android.local.host.name/gapps/gapps-gb-20110120-signed.zip
After unzipping any of these files, you want to copy the files to your system, like-ah-so:
adb remount
adb push system/etc/permissions/com.google.android.maps.xml /system/etc/permissions
adb push system/framework/com.google.android.maps.jar /system/framework
adb reboot
Read more: http://nookdevs.com/Honeycomb_Google_Apps_and_Market#ixzz1ZUFM1yei
Under Creative Commons License: Attribution Non-Commercial Share Alike
Click to expand...
Click to collapse
this probably works better than:
http://senk9.wordpress.com/2010/12/03/how-to-install-google-apps-gapps-on-your-android-device-phone/

jago25_98 said:
- was that an old way to install apps before `adb install`? Because any app I install via adb install isn't listed in /system/apps, yet it is installed because if I try to install again it tells me so...
Click to expand...
Click to collapse
No
adb install (or Market for that sake) will push apps to /data/app where apps normally reside.
/system/app is where the pre-packaged apps normally live, some choose to put them there to save space, but there might be other differences as I've seen that some apps needs to be put there in order to work properly .. haven't really looked into it tho.

/data/app, ah ok thanks Ros
I see you're on Netcom. Are they still super expensive? I was on pay as you go on holiday in Norway and man they still had per mb charging for both netcom and telenor when I was there, it was super expensive!
What I don't understand is how I'm supposed to install the market app... in order to get access to the market, seeing as I don't have another android device... the market apk says it needs some kind of dependency, but I can't find any mention of this, or get adb to tell me what the dependency is I need to satisfy
...
I must have plugged and unplugged the usb port a 50x already... need a port saver I can tell it's going to break quick!

jago25_98 said:
/data/app, ah ok thanks Ros
I see you're on Netcom. Are they still super expensive? I was on pay as you go on holiday in Norway and man they still had per mb charging for both netcom and telenor when I was there, it was super expensive!
Click to expand...
Click to collapse
Sorry for the late reply mate
I have no idea when it comes to personal plans, but neither one of them is particularly bad when it comes to business plans.
Ofc they make a lot of money on people not choosing the right plans and services for their needs, but if you do it right it's not bad at all
---------- Post added at 01:17 AM ---------- Previous post was at 01:10 AM ----------
jago25_98 said:
What I don't understand is how I'm supposed to install the market app... in order to get access to the market, seeing as I don't have another android device... the market apk says it needs some kind of dependency, but I can't find any mention of this, or get adb to tell me what the dependency is I need to satisfy
Click to expand...
Click to collapse
Market requires a ****load of stuff in order to work at all.
A successful TouchNooter should give you Market access assuming you followed the instructions (logging into youtube with your gmail account etc)
Problem with TouchNooter Market is that search doesn't work, so you have to use a web browser to log into market and push the apps you want to your Nook.

Boot Logo Wipeing

I know this is a pissed off issue by many of you but I want to use my archos as an industrial tablet.
I've made a fancy boot animation but there is still the Archos entertainment your way logo at early boot.
I read about it at an archos gen5 thread that with aos-tools and the famous flash binary the logo can be altere to another 800x480 logo by flashing with the 0x060000 starting address. Other threads said that this works no more so I turned to the data/customization way but here the early logo is problem for.
A solution could be to wipe out and to have animation only at late stage. Is it possible somehow?
br, sodjas

Update:
I successfully compiled the flash utility:
http://code.google.com/p/aos-tools/
But ran into the problem the it needs flashrw.ko module.
I found it on openAOS site but unfortunately it is compiled for gen5 armv5 the load fails with vermagic assert error.
I read on archosfans forum thread that flashrw.ko is non public and confidential thing but it only contains a bunch of ioctl calls.
I disassembled it and it showed that it is made of intel_flash_cmd.c file.
Could anyone help me how to get the flashrw.ko module for armv7-a?

Sad news modinfo shows:
alias: char-major-10-243
license: Proprietary
description: flashrw
author: Archos
depends:
vermagic: 2.6.10_mvl402 ARMv5 gcc-3.4
It is Proprietary

Hi sodjas,
you should do a little more research on this issue.
sodjas said:
I've made a fancy boot animation but there is still the Archos entertainment your way logo at early boot.
I read about it at an archos gen5 thread that with aos-tools and the famous flash binary the logo can be altere to another 800x480 logo by flashing with the 0x060000 starting address. Other threads said that this works no more so I turned to the data/customization way but here the early logo is problem for.
A solution could be to wipe out and to have animation only at late stage. Is it possible somehow?
Click to expand...
Click to collapse
As you started to point out, there are different bootlogos for the differnt stages on start-up.
1. bootloader logo
2. ramdisk bootlogo
3. Android logo (animated)
The logo inside Android could be easily removed or replaced (at least using Urukdroid).
Also the ramdisk logo could be modified with some technical skills (ramdisk needs to be rebuild and replaced).
Replacing the first hardcoded bootloader logo, is something for the freaks, but in fact it is possible.
First of all you'll need read/write access to the mtd block devices created by the kernel. This would require at least SDE or Urukdroid installation.
The Archos tablets use embedded MMC as persistant storage.
All partitions of this device are mounted as block devices and could be tweaked by directly accessing them (e.g. using dd for low level access).
One could start by reading some sectors of the first raw partition, examine the structure, do some disassembly and find the location where the bootloader logo is stored. Not sure if it could be deleted without changing some lines of code.
In fact this is an expert thing, if something goes wrong, you'll have a true brick .
There'd been some posts around covering this topic.
sodjas said:
Update:
I successfully compiled the flash utility:
http://code.google.com/p/aos-tools/
But ran into the problem the it needs flashrw.ko module.
I found it on openAOS site but unfortunately it is compiled for gen5 armv5 the load fails with vermagic assert error.
I read on archosfans forum thread that flashrw.ko is non public and confidential thing but it only contains a bunch of ioctl calls.
I disassembled it and it showed that it is made of intel_flash_cmd.c file.
Could anyone help me how to get the flashrw.ko module for armv7-a?
Click to expand...
Click to collapse
AFAIK, there's no need for this kernel module on gen8 devices.
The gen8 devices do not use any raw NOR flash or NAND devices.
All access to the eMMC is done with mtd kernel driver using the OMAP mmc interface.
BTW there might be some parts of storage used as hidden sectors, but this is a kernel thing only.
But back to topic:
In fact you'll need to find the bootlogo in raw data of the bootcode, determine the format and replace the raw blocks of memory.
Maybe you'll also need to tweak the security checks in bootcode as well, because checksum will change is the bootlogo is replaced.
Anyway it's slightly difficult to do so, but it's not impossible
Have fun,
scholbert

Lot of interesing information thank you, I'll check the hints out... The checksum thing sounds serious
Anyway, thank you very much for your answer it contains a lot interesting and useful things for me!
br, sodjas

Hi sodjas,
you're welcome!
This might be of interest to:
http://forum.xda-developers.com/showthread.php?t=1018260
This guy already made a disassembly of boot code.
http://forum.xda-developers.com/showthread.php?t=1214674
This guy wrote some tools for mmc low level access.
Maybe they might help you as well.
Keep on posting, this is an interesting topic
Regards,
scholbert

@sodjas:
Just being curious, why do you want the archos as an industrial PC?
I'M asking because we have bought a very cheap development board
http://embedded-computing.com/low-runs-main-line-linux-android
where you can install everything you want.
It is definately not as powerfull as the archos, but it costs less then half of it.
And if you search for OK6410 you will find others that even have the Android 2.3 for that.

@scholbert:
Thank you very much one more time , hope we can bring out something interesting
@fzelle:
The answer for this is the circumstance when you are at a software development deparment surrounded with high level software guys and have an interesting and impressing task to build an RFID enabled industrial terminal with WIFI capability and a platform where you can easly build fancy touch based UI-s in just 3 months then you made choices like these -> to have a proof of concept thing -> to prove that your software is unique and feasible to develop -> to be able to go to exhibitions to make this interesting to investors -> later it is more then possible that we will say somebody who has the experience in hw building: OK we have this HW build us a similar one from OEM parts bundled in an industrial box...
@both:
Thank you guys for replying, this is such a nice community!
br, sodjas

Hey Guys!
This is what I've done:
1. studied the linked threads by scholbert
2. used the extended aos-tools and successfully extracted .aos file
3. now I'm seeing a:
Code:
-rw-r--r-- 1 root root 432 2011-10-10 17:21 digest
drwxr-xr-x 2 root root 4096 2011-10-10 17:21 raw
-rw-r--r-- 1 root root 10 2011-10-10 17:20 repack.sh
drwxr-xr-x 3 root root 4096 2011-10-10 17:20 root
-rw-r--r-- 1 root root 10 2011-10-10 17:20 unpack.sh
structure.
If I understood right scholbert the ramdisk is under root/data/androidnerged.squeashfs.secure
How can I manipulate this part?
How can I rebuild the ramdisk?
If I understand correct the GPL released part is only the initramfs and the kernel itself...
Another question is that the most interesting thing here for me is the aos-fix tool
What is the:
Code:
--clear-signature Clear the signature out of a SIGN block, or a flash segment header.
part excatkly good for?
Sorry for the lots of questions, I'm still very green on low level
br, sodjas

One more thing:
I have the following structure under raw:
Code:
-rw-r--r-- 1 root root 264 2011-10-10 17:21 11_EXT2
-rw-r--r-- 1 root root 264 2011-10-10 17:21 15_EXT2
-rw-r--r-- 1 root root 8 2011-10-10 17:20 4_EXT0
-rw-r--r-- 1 root root 3264456 2011-10-10 17:20 7_MMCF
-rw-r--r-- 1 root root 2878728 2011-10-10 17:20 8_MMCF
I guess 7_ and 8_ MMCF files are the interesting ones...
Can I find a desc about these because in vitalif's thread about tweaking the bootloaders he tells about mmcblk0 / 1 ...
I also wasn't be able to find the hex parts found by scholbert when he linked vitalif's thread...
Still very confused but keep on learning
br, sodjas

Of course i understand that, i'm a sw dev for 25 years.
I was lucky to see that board before we had some similar needs as you have.
What do you use for the rfid part?

Hi sodjas,
it's late but i'll try to answer your questions
sodjas said:
This is what I've done:
1. studied the linked threads by scholbert
2. used the extended aos-tools and successfully extracted .aos file
3. now I'm seeing a:
Code:
-rw-r--r-- 1 root root 432 2011-10-10 17:21 digest
drwxr-xr-x 2 root root 4096 2011-10-10 17:21 raw
-rw-r--r-- 1 root root 10 2011-10-10 17:20 repack.sh
drwxr-xr-x 3 root root 4096 2011-10-10 17:20 root
-rw-r--r-- 1 root root 10 2011-10-10 17:20 unpack.sh
structure.
Click to expand...
Click to collapse
So this is the firmware structure before it is installed on the device.
The update process is done by the bootcode and there's not that much information about it and not much we could actually do with these files.
So you'd better have a look at the installed partitions and the way to modify thoose.
sodjas said:
If I understood right scholbert the ramdisk is under root/data/androidnerged.squeashfs.secure
How can I manipulate this part?
How can I rebuild the ramdisk?
If I understand correct the GPL released part is only the initramfs and the kernel itself...
Click to expand...
Click to collapse
No, the squashfs file is the final rootfs mounted as a loop device by the stock firmware.
It's possible to modify this file, but if you do the checksum won't match and you'll have to tweak bootcode to ignore security checking.
So in fact this is not very comfortable, but doable.
The ramdisk is the the cpio file archive also beeing updated and included in the update. Don't know the structure right now because it's on my linux laptop.
sodjas said:
Another question is that the most interesting thing here for me is the aos-fix tool
What is the:
Code:
--clear-signature Clear the signature out of a SIGN block, or a flash segment header.
part excatkly good for?
Click to expand...
Click to collapse
I don't know this tool and i guess it has been made for the older platforms.
sodjas said:
One more thing:
I have the following structure under raw:
Code:
-rw-r--r-- 1 root root 264 2011-10-10 17:21 11_EXT2
-rw-r--r-- 1 root root 264 2011-10-10 17:21 15_EXT2
-rw-r--r-- 1 root root 8 2011-10-10 17:20 4_EXT0
-rw-r--r-- 1 root root 3264456 2011-10-10 17:20 7_MMCF
-rw-r--r-- 1 root root 2878728 2011-10-10 17:20 8_MMCF
I guess 7_ and 8_ MMCF files are the interesting ones...
Can I find a desc about these because in vitalif's thread about tweaking the bootloaders he tells about mmcblk0 / 1 ...
Click to expand...
Click to collapse
Yeah, as i pointed out:
By extracting the update file you got an "external view" of the system.
After the firmware is placed on the device these files are flashed to eMMC and got mounted as block devices.
So it's little different then.
sodjas said:
I also wasn't be able to find the hex parts found by scholbert when he linked vitalif's thread...
Still very confused but keep on learning
Click to expand...
Click to collapse
It's a bit complicated to explain... but quite easy in the end.
You'll have to read out the partitions as raw blocks.
All the low level stuff is mounted as /dev/block/mmcblk0p1
Please read out first using the dd command.
It will give a file at about 32MByte, ands it's all cryptic binary format (rawfs and below).
So if you like to enter this, there's not much information here and you'll have to digg out pieces.
Maybe it's better to modify the higher level parts...
Anyway, the very first bootlogo is called banner. The format is unkown, at least to me, and you'll have ot understand the rawfs file structure used by Archos.
Attached you'll find the mounts of stock and Uruk firmware.
I know that this is little abstract right now, but i'll have to take some sleep
Have fun!
scholbert

@fzelle:
the rfid part is for workflow monitoring in glass houses. we would like to deploy N terminals in each house and the workers can check-in, define a task they are working on and after they've finished can check out... simple but all info is gathered on a central place and is in order to make easier planning/observing/and calculating financial/investment related things...
the only problem is the musb_hdrc.ko -> it is not picking the FTDI chip if its plugged-in with the OTG cable at the same time. It is a known issue but I still have a lots of problem here:
1. if a change musb_hdrc.ko to my instance musb_hdrc.ko in /lib/modules it is not working at all, if I check it with modinfo it is different than the one in the GPL release. I guess these files under /lib/modules are also proprietary
2. I degbugged around and saw that the state changes for musb only work well if you first attach the OTG micro which has a grounded 5th pin ->then the state goes to a_idle and then attach the FTDI chip -> this is a working scenario
3. If you attach the OTG with already connected FTDI then it stuck at b_idle mode...
I started a thread about this:
http://forum.xda-developers.com/showthread.php?t=1288522
but it seems the proprietary drivers will be the root of the problem here...
@scholbert:
a mininum thing I owe you is a beer a lot of useful infos here again I'll check around and come back if there are some updates.
thank you guys!
br, sodjas

Hi,
thanks for appreciating.
But stupid me, i forgot one thing...
Quoting myself:
Anyway, the very first bootlogo is called banner. The format is unkown, at least to me, and you'll have ot understand the rawfs file structure used by Archos.
Click to expand...
Click to collapse
So there's a kernel driver for rawfs of course
The rawfs parts got mounted to /mnt/rawfs and present themselfs as files (avboot, banner,...).
No need to fiddle with the raw binaries to investigate the structure.
You'll have to be root to access this directory.
I'll do some research about the file format of the banner file
EDIT:
O.K., here we go... it is a gz compressed file representing raw pixel data.
So in fact this is the very first boot logo!
Should be possible to import this file to gimp or something.
Don't know if it breaks the avboot security check if it get's replaced. So please be careful!
EDIT2:
I got a Archos 101 so filesize will vary on other platforms.
The pixel data is put into 32bit format so each pixel requires a 4-byte value.
On A101 the resulting file size is of the uncompressed banner file is 2457600 bytes -> 1024x600x4
The simple framebuffer inside avboot uses only the lower 24bit of 32bit pixel data.
The most significant byte of each pixel is always set to 0xFF (0xFF000000 written as MSB first)
To completely blank screen (delete archos logo) you'll need to blank out all pixel.
Pixel data should look like this:
Code:
0xFF000000 x 1024 x 600 (for A101)
0xFF000000 x 800 x 480 (for A70)
You might create such a file with a hex-editor or use some scripting.
Good luck with your USB driver stuff!
Regards,
scholbert

Update
I modified both mmcblk0 and mmcblk0p1, my tab is still booting.
The modification of /mnt/rawfs/banner directly was my idea too, but I'm still afraid of some parts
I pulled the banner file and on ubuntu I can list the content, but can't extract it, and there are lots of questions like:
1. The file inside banner is named i240x400 -> this means that it is a 240x400 image but it would be more logical that it is 400x240 based on how "Entertaiment your way " looks...
2. Ubuntu's file roller can't extract it
3. When I open it in hex editor it has some meta info at the start of the file
and a question at the end:
How did you uncompress your banner file? I always get errors, maybe I used wrong syntax...
br, sodjas

Hi Sodjas,
Let me jump in on this to complement your study:
First, a BIG WARNING: touching any of this without patching signature check will result in bricking device.
Second BIG WARNING: Vitalif's mmc offsets for bootloader patches are valid for his device only. Mine has completely different values, I presume there are multiple bootloader versions out there. If patch is incorrect, or not done in the right order, instant brick.
7_MMC and 8_MMC are indeed interesting parts, these are the kernel+initrd images for android and recovery.
As stated by scholbert, to get a better understanding, you should take a look at /mnt/rawfs:
You'll see few files there:
avboot (second stage bootloader)
init (normal boot android, kernel+initrd)
recovery (recovery boot, kernel+initrd)
custom (sde boot, kernel+initrd)
banner (boot logo as it seems)
7_MMCF is flashed to init
8_MMCF is flashed to recovery
Splitting these files into zImage+initrd.gz is quite easy, I can give you some hints if you want. But I don't think it would serve you much for what you're trying to do: what you want is changing bootloader logo, so your goal is avboot+banner.
But again, don't modify anything on mmc0 until you're sure of what you do. First bootloader checks avboot signature and avboot checks init and recovery signature for sure. Without patch, you'll brick your device.
I don't know if avboot checks banner file though.

Hi Letama,
Thank you for joining.
Yes sure you are right the values vitalif mentioned were on different addresses BUT occured only once in the whole binary for both binaries, so I tried my luck and I think it is working because after reboot I have mmcblk0 and mmcbl0p1 still with the patched content and the tab boots without any problem
If I'm right then now I can start playing with altering mmcblk0p1 content because I have patched verify_hash function. Am I right?
Two big questions still open for me:
1. How to modify banner in an efficient way?
2. I understand now I have two patched bootloader binaries and can dd them on any A70IT, am I right or the patching process needs to be done/ device? I suppose not.
Update 2
In the meantime I uncompressed it on win with 7-zip I see the content I should modify to 0xFF000000 but I'm still not sure how flush this to all 0xFF000000 because there is some meta info at start. And as second, how to compress it, maybe the gzip -9 i240x400 will do its job as it was described at Gen5 boot logo tutorial...
br, sodjas

sodjas said:
because there is some meta info at start.
br, sodjas
Click to expand...
Click to collapse
Sorry AFAIK, no metainfo, just the pure 0xAABBCCDD 32bit values as scholbert told me before, sorry for that
br, sodjas

I realized again I'm a fool, or just archos guys wanted to make a joke
1. the banner file is named i240x400 BUT
2. when you extract it you got a 1 536 000 bytes sized file
3. I used my awsome maths skills and found out that: 1 536 000 / 4 <byte> = 384000 / 800 <pixels> = 480
So the raw image size is 800x480 and no 240x480 as the file name indicates...
I just need to flush 0xFF000000 384000 times in a file I think.
br, sodjas

sodjas said:
Yes sure you are right the values vitalif mentioned were on different addresses BUT occured only once in the whole binary for both binaries, so I tried my luck and I think it is working because after reboot I have mmcblk0 and mmcbl0p1 still with the patched content and the tab boots without any problem
Click to expand...
Click to collapse
Yes, search pattern was the same for me too, only different offsets. Good thing that code didn't change.
sodjas said:
If I'm right then now I can start playing with altering mmcblk0p1 content because I have patched verify_hash function. Am I right?
Click to expand...
Click to collapse
I only modified init and recovery, but I guess they wouldn't implement a specific signature check for boot logo. I'm suspecting that there is no signature check at all on it but I never checked avboot for that.
sodjas said:
1. How to modify banner in an efficient way?
Click to expand...
Click to collapse
To modify init and recovery, I wrote a small app that directly open /dev/block/mmcblk0p1, seek for the right position (with some file signature check to be sure I'm doing it right) then write. I make sure that I don't write a bigger file than current ones and it works fine for init/recovery. I believe that archos flasher does the same as existing file sizes are bigger than the firmware dump file sizes.
For your needs, I don't know if you will have to adjust size in the rawfs directory entry and/or avboot. Rawfs is quite straightforward, you can take a look at linux driver if you need to adjust directory entry.
sodjas said:
2. I understand now I have two patched bootloader binaries and can dd them on any A70IT, am I right or the patching process needs to be done/ device? I suppose not.
Click to expand...
Click to collapse
A dd of mmcblk0 (not mmcblk0p1, you need also first bootloader) should do the trick if the hardware doesn't change and doesn't need a different bootloader. I think that there is multiple revisions of hardware out there, improper bootloader for a specific hardware revision could not boot.
Safest bet would be to write a small patcher that would check pattern and stop if you don't have a known bootloader.

[Q] How to get multi boot ?

I find some topic to make multi boot for X5 but I don't know exactly how do it !
http://forum.donanimhaber.com/m_59231411/tm.htm
And here:
-------------------------------------
Multi-boot
In fact, users in China use the U8800, multi-system has been used for a long time.
So, now I will use my broken English to tell you how to use multi-system
First, you need The extra two partitions in the 4G space. you could use twosys-partition.zip to get The extra two partitions 15&16
download partition package:http://forum.xda-developers.com/atta...1&d=1321675310
And
The second system-specific recovery system
http://forum.xda-developers.com/atta...1&d=1321675310
put the twosys-partition.zip and you like rom's zip into Sdcard
rename the recovery_4.0.1.5_en_sys2.img to recovery2.img , then place it to /cust
Boot into recovery,flash this package directly, same as flashing a ROM.
After flashing go to advanced options, choose to reboot to recovery.
Go into recovery again, flash this package again directly, same as flashing a ROM.now you will have The extra two partition 15 and 16
OK, let's flash two system into you phone
Go into recovery again, flash you like rom's zip
boot into first system, you could use RootExplorer access /cust, rename the recovery.img to recovery1.img, rename the boot.img to boot1.img,rename the recovery2.img to recovery.img.
reboot you system into recovery, now you recovery is second system recovery,you could flash the 100911-cm7,it will auto flash into second system.
reboot system, you will into second system (CM7)
if you want change you system to first, you could use RootExplorer access /sbin/gk, you will found some .sh files,Execution the 8-ChangeSys will auto rename all
img file then auto reboot to first system.
you could copy the 8-changesys.sh to any place let you change system easy.
restore offical partition ： download
Important：only the 100911-CM7 can flash into second system, other ROM only flash into first system
please backup your data, because you will lost all data in phone
Attached Thumbnails
Click image for larger version Name: IMG_20110507_215751.jpg Views: 12861 Size: 82.6 KB ID: 589834 Click image for larger version Name: CAP201106210959.jpg Views: 7380 Size: 23.3 KB ID: 631536 Click image for larger version Name: CAP2011062109581.jpg Views: 11102 Size: 29.6 KB ID: 631537
Attached Files
File Type: zip offical-partition-2sys.zip - [Click for QR Code] (1.29 MB, 1459 views)
File Type: zip twosys-partition.zip - [Click for QR Code] (1.19 MB, 525 views)
File Type: zip recovery5.0.2.7_en_sys1.zip - [Click for QR Code] (4.20 MB, 788 views)
File Type: zip recovery5.0.2.7_en_sys2.zip - [Click for QR Code] (4.20 MB, 633 views)
Click to expand...
Click to collapse
So any one who can held us to make multi boot for X5 Actual Fine ?

http://forum.donanimhaber.com/m_59231411/tm.htm is my guide and it's for 35 kernels
Multi-boot
In fact, users in China use the U8800, multi-system has been used for a long time.
So, now I will use my broken English to tell you how to use multi-system
First, you need The extra two partitions in the 4G space. you could use twosys-partition.zip to get The extra two partitions 15&16
download partition package:http://forum.xda-developers.com/atta...1&d=1321675310
And
The second system-specific recovery system
http://forum.xda-developers.com/atta...1&d=1321675310
put the twosys-partition.zip and you like rom's zip into Sdcard
rename the recovery_4.0.1.5_en_sys2.img to recovery2.img , then place it to /cust
Boot into recovery,flash this package directly, same as flashing a ROM.
After flashing go to advanced options, choose to reboot to recovery.
Go into recovery again, flash this package again directly, same as flashing a ROM.now you will have The extra two partition 15 and 16
OK, let's flash two system into you phone
Go into recovery again, flash you like rom's zip
boot into first system, you could use RootExplorer access /cust, rename the recovery.img to recovery1.img, rename the boot.img to boot1.img,rename the recovery2.img to recovery.img.
reboot you system into recovery, now you recovery is second system recovery,you could flash the 100911-cm7,it will auto flash into second system.
reboot system, you will into second system (CM7)
if you want change you system to first, you could use RootExplorer access /sbin/gk, you will found some .sh files,Execution the 8-ChangeSys will auto rename all
img file then auto reboot to first system.
you could copy the 8-changesys.sh to any place let you change system easy.
restore offical partition ： download
Important：only the 100911-CM7 can flash into second system, other ROM only flash into first system
please backup your data, because you will lost all data in phone
Attached Thumbnails
Click image for larger version Name: IMG_20110507_215751.jpg Views: 12861 Size: 82.6 KB ID: 589834 Click image for larger version Name: CAP201106210959.jpg Views: 7380 Size: 23.3 KB ID: 631536 Click image for larger version Name: CAP2011062109581.jpg Views: 11102 Size: 29.6 KB ID: 631537
Attached Files
File Type: zip offical-partition-2sys.zip - [Click for QR Code] (1.29 MB, 1459 views)
File Type: zip twosys-partition.zip - [Click for QR Code] (1.19 MB, 525 views)
File Type: zip recovery5.0.2.7_en_sys1.zip - [Click for QR Code] (4.20 MB, 788 views)
File Type: zip recovery5.0.2.7_en_sys2.zip - [Click for QR Code] (4.20 MB, 633 views)
Click to expand...
Click to collapse
this guide for 32 kernels.

forumber2 said:
http://forum.donanimhaber.com/m_59231411/tm.htm is my guide and it's for 35 kernels
Click to expand...
Click to collapse
Can you translate it?
Google translate is s**t
Sent from my U8800 using Tapatalk 2

Qqqxxxzzz said:
Can you translate it?
Google translate is s**t
Sent from my U8800 using Tapatalk 2
Click to expand...
Click to collapse
i will try but i dont have enough time.

Please !
Could you transalate to English please ?

Downloaded Motorola's Google Drive from XT1585 fastboot IN FULL. Good or boring?

https://accounts.google.com/signin/...dSession#folders/0B9t5VvCjiCO-Qm9Bb29PdzdHajQ
That's the link. You get the shortcode link when trying to flash the Turbo 2 using fastboot Linux command line. I first found some other cool tricks I have never seen mentioned about the fastboot oem command and some certain characters, but I suspect it is not related.
I got in, I noticed they just did an update to all the files, I downloaded everything, aa zip of all of it, and promply lost access. I have a spreadsheet open in google docs describing the updates. You can see at the top that it says that permissions have changed.

binwalk: Did I really find a boot img? Also: Legal advice?
Here's what binwalk just found (edit's mine til I know legal deal):
Code:
1###1#0 0x1#ABC# Android bootimg, kernel size: 1871876996 bytes, kernel addr: 0x###4#F#E, ramdisk size: 1953406600 bytes, ramdisk addr: 0x6###6##0, product name: "reating boot image..."
1##6##0 0x10#ABC Unix path: /../../target/product/%s/%s
The hexadecimals (mem addrs?) are actuallly there. I have adjusted the sizes, but if you know them you could figure out they are legit and my edits were simple.

can you please upload this onto this post or zippyshare or some other place. dumbass google made it so you have to have a Motorola email address to login