yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] gulyuk.s:
It would be very nice to have all possible variants updates, to put the pieces together and maybe solve this problem for other
[Android Q&A, Help & Troubleshooting] avalon986:
Hmmm. Could you give us a link to the zip? Legyszi :-) I'm experimenting a lot with this phone so I could give it a try or two or ten :-)
[Android Q&A, Help & Troubleshooting] qltsar:
FOTA update

Links have been sent to your inbox folder at XDA!
[Android Q&A, Help & Troubleshooting] iEstuardo:
Can you post the link for everyone?
[Android Q&A, Help & Troubleshooting] avalon986:
http://dl.dropbox.com/u/20480657/Android/Alcatel/telenor_FOTA_update.zip/update.zip

This is the Hungarian telenor OTA update zip
[Android Q&A, Help & Troubleshooting] iEstuardo:
Cannot pass the verification check.

assert(apply_patch_check...
[Android Q&A, Help & Troubleshooting] sigprof:
Great! Now… could you (or someone else) get a dump of the FOTA partition (most likely /dev/mtd/mtd14, but check in /proc/mtd to be sure) from a phone with

ro.build.fingerprint=TCT/one_touch_990_TNHU/one_touch_990_gsm/Brandy:2.2.2/FRG83G/v53R-0:user/release-keys (or maybe with a custom 2.2 ROM installed over that version)? You would need either a rooted phone with busybox installed, or just a flashed CWM recovery for this; use adb shell to connect, invoke su (probably not needed when inside CWM recovery), then execute:

busybox dd if=/dev/mtd/mtd14 of=/sdcard/FOTA.img bs=4096
[Android Q&A, Help & Troubleshooting] gulyuk.s:
So, you have an idea?

and from any other fota.img 2.3 will not work?

In my opinion it's signed update.zip for stock recovery, don't you think that should be given those who try to flash to 2.2?

I think it's enough just to install this file from the memory card, because the principle is the same FOTA, download over the air and auto mode flash this via stock recovery
[Android Q&A, Help & Troubleshooting] sigprof:
This update.zip contains patches to upgrade from TNHU 2.2.2/FRG83G/v53R-0 to 2.3.4/GINGERBREAD/v5GY-0; most of these patches are not really useful for other versions (it is easy to dump system, custpack, boot and recovery images without bothering with binary patches). But there is one really interesting file: patch/fota-from-amss.p; from the updater-script I see that this binary patch is supposed to be applied to the original FOTA partition contents from 2.2 (first 17747968 bytes should have SHA1 9c808861d2aa3385f8c158b1dee8cae14a8c0bb5, and the result will be 18946036 bytes with SHA1 fa3a3c6f1543fef862daa83d7a89679c90d65c95). The original FOTA contents is just the AMSS (phone/modem part) binary, but the result of the patch apparently should contain more than AMSS — looks like at least the APPSBL/HBOOT part should be there, and maybe other bootloaders too. Maybe it would be enough to put the appropriate contents into FOTA and FOTAFLAG partitions, then reboot the phone to trigger the boot/modem code update from the baseband CPU side (as I have found out, the application CPU does not have access to that part of NAND flash, only the baseband CPU could update it). So it would be a way to upgrade a phone from 2.2 to 2.3 without OTU (if the existing baseband CPU boot code would not reject the update made for a different country, and if the Hungarian AMSS code is not region-locked in some way). Or at least we could look at the bootloader code and try to find some holes in it.

No, 2.3 definitely will not work. A dump from 2.2 for another country could work if the AMSS code happens to be identical with the version made for Telenor-Hungary.

No, this will not be useful for downgrading to 2.2, except if the resulting FOTA binary is not signed as a whole, and it would be possible to change the AMSS part to the older version dumped from 2.2, and the only real incompatibility is in the AMSS code (and not, e.g., in the bootloader or ADSP parts, which currently cannot be dumped).

This would work only if installing over exactly the same original firmware (Telenor-Hungary 2.2.2).
[Android Q&A, Help & Troubleshooting] gulyuk.s:
and so until we get a dump of the original fota of Hungary, we do not know what can be done?

sorry,vsu_ it's you?

thanx,for this post http://xdaforums.com/showpost.php?p=23465028&postcount=269
[Android Q&A, Help & Troubleshooting] sigprof:
Try to get a Russian 2.2 dump — who knows, maybe Alcatel/TCT/JRDcom/whatever-they-are-called did not really use different AMSS versions for different countries.

I have tried to apply the binary patch to a file with all zeros (bspatch does not itself check file contents) — looks like at least OEMSBL (final part of the baseband CPU bootloader, which applies FOTA updates and then loads AMSS) and APPSBL (application CPU bootloader, which handles fastboot and loads Linux kernels from boot and recovery partitions) are there together with the updated AMSS, but there are lots of holes where the binary patch refers to identical byte sequences from the original FOTA partition contents. There are also some things which look like version codes: EY5GYHW0, EY5GY0W0, LY5GY0W0, KY5GYHW0, KY5GY0W0 — are they identical with /proc/cmdline contents in the new 2.3 firmware (I have only dumps from the first 2.3 release, which had androidboot.bootloader=LY5GX0V0 qcsblhdver=HY5GX0V0 qcsblver=QY5GX0V0 oemsblhdver=EY5GXHV0 oemsblver=EY5GX0V0 amsshdver=KY5GXHV0 amssver=KY5GX0V0)?

Yes ;)
[Android Q&A, Help & Troubleshooting] avalon986:
Today I have to do some things but tonight I'm going to search for a Hungarian 2.2.2 dump. I'm getting realy angry on telenor serbia. Wen I asked them the thirf time about the update I got the same copy/paste answer what I got the first and second time. :-(
[Android Q&A, Help & Troubleshooting] gulyuk.s:
in last russian update the cmdline

mem=458M console=ttyMSM2,115200n8 androidboot.hardware=qcom androidboot.bootloader=LY5GY0W0 qcsblhdver=HY5GY0W0 qcsblver=QY5GY0W0 oemsblhdver=EY5GYHW0 oemsblver=EY5GY0W0 amsshdver=KY5GYHW0 amssver=KY5GY0W0 androidboot.baseband=msm
[Android Q&A, Help & Troubleshooting] sigprof:
So if we find the proper original binary to apply the patch, we might get the new bootloader (APPSBL), OEMSBLHD, OEMSBL, AMSSHD, AMSS, but maybe not QCSBLHD and QCSBL (this is the baseband bootloader stage which loads OEMSBL); and the version codes seem to be identical for the Hungarian and Russian firmware.

Hmm, the really strange thing is that FOTA.img from my dump contains version codes like KY53B060, KY53BH60, TY530000, LY53B060, LY53BH60, CY53ZZ60 and the like (so it looks like a version from a 2.2 firmware), but no signs of KY5GXHV0 and KY5GX0V0, even though this dump was definitely taken after flashing 2.3 firmwares via OTU multiple times. There are also some dates: Feb 03 2011 and Aug 4 2011. So we don't even know what triggers copying of the AMSS binary from the real AMSS partition to FOTA (which seems to happen inside OEMSBL). The FOTAFLAG partition contains these log messages:

copy AMSS into FOTA
fota_init() : AMSS written to FOTA (17739776 bytes)

Even the size does not match the value from the Hungarian update (17747968), so probably AMSS images for different countries and operators are really different.

Maybe an attempt to get FOTA updates from the phone UI triggers this copying (even when no actual update is found later)?

I attached dumps of FOTA and FOTAFLAG partitions which I have here (taken after updating the phone to Russian 2.3.4/GINGERBREAD/v5GX-0 firmware via OTU).
[Android Q&A, Help & Troubleshooting] gulyuk.s:
have idea about downgrade via fastboot

if flash all partitions (15 pcs - FOTA.img,securo.img and other...) from 2.2.2 on device with rom 2.3.4, it's real or delirium?

so that,

may be has flash the all official rom,custom

fu..ck the partition " ",i forgot mtd number,isn't flashable

if I flashed all paritions of 2.2 - system not load

if all partitions of 2.3 - load as normal

but in both cases, the final loading of images, a window, as if the band load of stock recovery
[Android Q&A, Help & Troubleshooting] qltsar:
What about the recovery?

If we can modify the recovery to mount these partitions we are able to flash img files to them.

Just an example, we can mount the custpack parition over ClockWork recovery, so we can mount the phone's other partitions, but we have to modify the clockwork recovery for the phone.
[Android Q&A, Help & Troubleshooting] sigprof:
Yes, this is expected, because the actual bootloader and baseband CPU code (AMSS) are outside of the flash area accessible to the Linux kernel through normal MTD drivers.

However, I have found an interesting patch for the bootloader code for some other MSM-based device; this code seems to be present in the OT-990 APPSBL too (at least the "nandcfg(Modem): %x %x (used)" string is there). The patch suggests that some form of access to modem partitions from the application CPU is possible, but a different NAND configuration is required; of course, the driver in the Linux kernel (drivers/mtd/devices/msm_nand.c) does not support this (at least in the 2.6.32.9 kernel for which sources are available).

It is also possible that a simple "fastboot flash modem amss.mbn" (or maybe "fastboot flash AMSS amss.mbn") would work (the first 17739776 bytes from my FOTA.img dump is apparently amss.mbn version from Froyo). If this would work, downgrading to Froyo will additionally require patched kernel binaries (because the machine id will still come from the new bootloader).
[Android Q&A, Help & Troubleshooting] gulyuk.s:
so if you want us to get amss.mbn theoretically can produce a firmware modification of the kernel and it compile under the new machine id - will actually make the downgrade?

and what is necessary and where to get it?

from my experiments by flashed partitions via fastboot:

all partitions of firmware 2.3 was flashed normal,but for test FOTA and FOTAFLAG was erased only and not flashed - OTU not verified my device

but i can't flash partition mtd13 or 12,not remeber number " "
[Android Q&A, Help & Troubleshooting] sigprof:
The first 17739776 bytes of FOTA.img from my dump look like amss.mbn in most of Qualcomm firmwares seen on the Internet, and it seems to be the old version from a Froyo firmware. The exact size is visible in FOTAFLAG.img in plain text.

dd if=FOTA.img of=amss.mbn bs=17739776 count=1

Kernel recompile just for the machine ID is not strictly necessary — the binary patch should be enough (the kernel in the CWM recovery image is already patched).

So OTU uses at least one of these partitions for verification? Interesting; did you try to erase only one of them? And what about attaching the phone without battery with Home pressed — is it broken too?

mtd12 (with the empty name) overlaps mtd0…mtd11; it seems to be the 0:APPS partition as seen from the Qualcomm bootloader code. Flashing it as a whole will not work, because plain images (including boot and recovery) and yaffs2 filesystems need different NAND ECC settings (dumping yaffs2 via dd also does not work for this reason, and /system/bin/nandread, which could work for this, seems to be broken).
[Android Q&A, Help & Troubleshooting] gulyuk.s:
I have not tried one partition FOTA or FOTAFLAG,but this method phone without battery with Home pressed isn't work too

bs = 4096 was selected for experiment
[Android Q&A, Help & Troubleshooting] Danijel_rs:
Can someone upload Telenor Hungary 2.2 STOCK rom, without modifications, so we can try to use this FOTA update.zip?
[Android Q&A, Help & Troubleshooting] Anolnx:
Here is one from a french 2.2 Orange flashed with a custom 2.2, if it can help to understand the structure.

ro.build.fingerprint=TCT/one_touch_990_OBGB/one_touch_990_gsm/Brandy:2.2.2/FRG83G/v53R-0:user/release-keys
[Android Q&A, Help & Troubleshooting] gulyuk.s:
experiment

sigprof

so,today I'm again try to flash partitions from 2.2 via fastboot - the result is the same, system will not boot

decided to flash only boot custpack system from 2.3 as if nothing had happened,sytem loaded, but again, OTU cann't read data by devices until I flash all partitions 2.3
[Android Q&A, Help & Troubleshooting] sigprof:
Thanks. This image seems to have version code KY58L0J0, and the correct size (17747968 bytes); unfortunately, its hash does not match the Hungarian update (be67b9ae01f5b02a4a115ff6a4807a3637e8f865 instead of 9c808861d2aa3385f8c158b1dee8cae14a8c0bb5).
[Android Q&A, Help & Troubleshooting] heyjoe66:
TheMOONSTONE

Updated to 1.1:

- bugfixes

- battery drain fix

Thread link

ATTENTION: you Google account setting may be reset because of patched GoogleServicesFramework, you'll have to sing in again after flashing.
[Android Q&A, Help & Troubleshooting] gulyuk.s:
upgrade backup & restore zip

if you used my update.zip for backup and restore your rom,I'm updated their and add save user data :cool:

Backup update.zip:

View attachment backup_Gulyuk.zip flash this via CWM Recovery as install zip from sdcard,after on your sdcard will be created folder "firmware" with nandbackup

Restore update.zip

View attachment restore_Gulyuk.zip flash this if your rom not rooted

View attachment Restore.zip flash this if your rom rooted

Actual for ROM based 2.2.2/2.3.4 and it's very very good method for backup rom,maybe and for you too :rolleyes:

Also I'm modify odex script for odexed your ROM via CWM Recovery

View attachment odexed_alcatel.zip

before flash this update.zip you must complete the steps:

all apps wich are in /custpack/app/withoutlibs and /system/app copy to new folder /custpack/app/apps

/custpack/app/apps must symlinked /system/app

after flash it and have rom as odexed ;)
[Android Q&A, Help & Troubleshooting] qltsar:
I will try my best...but unfortunatelly we haven't got any backup of 2.2.2 firmware at the hungarian mobilarena forum...but it's not 100% sure :) But i think the 95% of Telenor One Touch users have been updated to 2.3.4.

So if i will find something, i'll give you a message! :)

Greetings from Hungary.
[Android Q&A, Help & Troubleshooting] sigprof:
Could you get some dumps from 2.3.4 updated via FOTA then? At least we should get another AMSS version (it turned out that phones updated via OTU still have the old AMSS binary in the FOTA partition, and a binary from 2.3.4 was not found yet).

Also, please dump FOTA and FOTAFLAG together:

busybox dd if=/dev/mtd/mtd14 of=/sdcard/FOTA.img bs=4096
busybox dd if=/dev/mtd/mtd13 of=/sdcard/FOTAFLAG.img bs=4096
[Android Q&A, Help & Troubleshooting] Danijel_rs:
@qltsar

Thanks :)
[Android Q&A, Help & Troubleshooting] qltsar:
These are the asked images:

FOTA

FOTAFLAG

I hope it helps!
[Android Q&A, Help & Troubleshooting] gulyuk.s:
boot

qltsar

and give me your boot for add support,are you forgot it?:eek:
[Android Q&A, Help & Troubleshooting] qltsar:
No, but, i have done that...but with no luck, my ROM went to booloop :P

So here is my boot.img: http://dl.dropbox.com/u/20480657/Android/Alcatel/minimal%20edition/1.3/boot_wo_init.d/boot.img

So something went wrong with the busybox permissions, but i don't know what am i missed...i have been set the correct chmod values, but the ROM stops booting at the bootsplash :D

edit: i have found an alternative way to use init.d scripts, and it works for me :)

I don't know why your method doesn't works for me...i've added the necessary lines to the init.rc at the boot.img, but the 00sysinit can't start the process.

The permissions 100% right i have checked it a hundread times...so i have no idea why isn't working for me.

Thanks gulyuk!
[Android Q&A, Help & Troubleshooting] gulyuk.s:
usage: applypatch [-f] <src-file> <tgt-file> <tgt-sha1> <tgt-size> [<src-sha1>:<patch> ...]
or applypatch -c <file> [<sha1> ...]
or applypatch -s <bytes>
or applypatch -l

Filenames may be of the form
MTD:<partition>:<len_1>:<sha1_1>:<len_2>:<sha1_2>:...
to specify reading from or writing to an MTD partition.

I wanted to ask about applypatch, I think we can use this command when system is loaded,maybe update.zip work so too? and these partitions fota fotaflag as a source of information

maybe only need modify this update.zip or unpack and apply from console line
[Android Q&A, Help & Troubleshooting] qltsar:
gulyuk.s

Did you tried to change the Adreno libs? Some users reported performance improve after this tweak.

Source: http://xdaforums.com/showthread.php?t=1530411
[Android Q&A, Help & Troubleshooting] sigprof:
Now we have a version of AMSS compatible with the AP side of Gingerbread ROMs (version KY5GY0W0, 18055168 bytes, SHA1: 3b6391181563a9a97b5905af401fa9d7eff6a7b4), but still no new bootloaders, and no known way to flash it.

I wonder whether a command like this would work with the phone in fastboot mode:

fastboot flash AMSS amss.mbn

or maybe some variations like

fastboot flash amss amss.mbn
fastboot flash radio amss.mbn
fastboot flash modem amss.mbn

Doing this on a phone which already has the same AMSS version is probably the safest method to find out whether the APPSBL version on this phone accepts such commands, but playing with bootloaders is always dangerous… And the only visible result would be the output of the fastboot command (if it fails with an error message, then either the fastboot method of flashing modem partitions is not supported at all, or the partition name is wrong).

I have attached a version of amss.mbn made from your dump (it is just the result of dd if=FOTA.img of=amss.mbn bs=18055168 count=1).

An external command is handy for hacking, but update.zip does not really need it — there are builtin commands for updater-script (apply_patch, apply_patch_check), look in that FOTA update.zip for examples of their usage. What is really needed is the exact AMSS binary to be used as a base for applying the fota-from-amss.p binary patch.
[Android Q&A, Help & Troubleshooting] gulyuk.s:
so,maybe begin make to backup for our firmware (amss.mbn) and try to flash Hungarian amss.mbn for test?if not gave good result,we always flash our amss or it for kamikazes :D as me :screwy:
[Android Q&A, Help & Troubleshooting] sigprof:
The only Russian version of AMSS that we have is for Froyo, not Gingerbread, so if the Hungarian version will misbehave on a Russian phone, the only way to restore the Russian version would be to use OTU (and hope that it will recognize the phone as Russian and flash the proper version even in this state).

I'm thinking of trying to install USBSnoop (apparently now there is a newer version, but I have never used it — only the original one) and capturing USB traffic during OTU reflash in emergency mode (removed battery and pressed Home) — maybe it would contain unencrypted bootloaders, AMSS and other firmware code. The only problem is that currently I don't have the phone :)
[Android Q&A, Help & Troubleshooting] gulyuk.s:
contact with me via pm on 4pda,I'm ready to help for it,as says to be or not to be:D
[Android Q&A, Help & Troubleshooting] qltsar:
Just be careful with the flashing :) :p
[Android Q&A, Help & Troubleshooting] avalon986:
May the force be with you on this testing :-)
[Android Q&A, Help & Troubleshooting] SV_25:
Hi, I found out a sort of temporary fix for the problem.

What I did was modifying the updater-script inside the update.zip, so it would skip that verification check. After that, the installation was successful but -what else?- it got stuck in a bootloop. Can someone say if it is even makes sense to attempt updating 2.2 to 2.3 with this method?

@the others around here: great work, but what are you actually hoping to achieve? (like: from 2.2 to 2.3 or reverse) I'm sort of lost in the things you are posting here... (=noob)
[Android Q&A, Help & Troubleshooting] sigprof:
This won't give you anything useful — bspatch (which is used internally by apply_patch) will happily accept any garbage instead of the intended original file, but then it will also produce garbage instead of the updated file.

Upgrade might be easier to achieve (if only we could get a dump with the required old AMSS version, then the resulting FOTA update should upgrade both bootloaders and AMSS to versions required for 2.3, then even stock unpatched 2.3 should work). For downgrade we would either need to get old bootloaders somehow, or (if the old AMSS would still be loaded by new bootloaders properly) use patched kernels for 2.2 (stock 2.2 would not work without such patches).
[Android Q&A, Help & Troubleshooting] gulyuk.s:
so,I want to help for it,but nobody's contact with me.okey,I will not work with this device, that's at least see how brainy people's make https://server.backup.comodo.com/js....zip?key=5b3304b4-e457-40ed-aa15-d74d941e89d5 and http://pastebin.com/75wc7J36

and you can flash amss or amss.mbn or amss.bin,as dd if=/sdcard/amss of=/dev/block/* - don't know in our device

in lg,samsung it's /dev/block/bml* block and they flash,backup,restore modem by cwm recovery

I think - it's baseband module and maybe help for downgrade

bs=18055168 count=1

where is values for amss,are this support for froyo?

I just read

adb push mdm.bin /tmp/amss.bin adb push amss.bin /tmp/mdm.bin adb shell dd if=/tmp/amss.bin of=/dev/block/mmcblk0p13 adb shell dd if=/tmp/mdm.bin of=/dev/block/mmcblk0p17

for samsung mtd partitions

good luck ;)
[Android Q&A, Help & Troubleshooting] sigprof:
F***** opera mini ate my post :(

Samsung devices are just not as locked down as Alcatel — they allow RW access to all flash partitions from AP. For OT990 the only hope of such access is through fastboot, which does not support reads; if writes to AMSS are not supported at all, then we are left with either finding an appropriate FOTA image, or reverse engineering the USB protocol used by OTU. Or just wait for several months and hope that 2.3 updates would be available for all countries, then just build custom ROMs with AP-only code as we do now, without any ability to change bootloader or modem code.
[Android Q&A, Help & Troubleshooting] gulyuk.s:
then use the 2.2 kernel is useless in the future?

will be available by source 2.3 the changing partition table or will send f***n support of Alcatel to a*s then forget about developed by this device?
[Android Q&A, Help & Troubleshooting] sigprof:
Partition table comes from the bootloader; patching it from the kernel is possible, but does not give access to hidden flash areas. And I don't believe claims that upgrade from 2.2 to 2.3 changes the partition table — if this was the case, FOTA upgrades to 2.3 could not work.
[Android Q&A, Help & Troubleshooting] Anolnx:
Not an option for everyone. The Orange-branded OT-990 wil NEVER recieve an update. So said Alcatel support. It seems too complicated and expensive to build an Orange bloated-crippled version just to update already-sold phones.

The only hope for Orange-crippled OT-990 to have a small chance to get updated is this forum.
[Android Q&A, Help & Troubleshooting] avalon986:
Also, i don't think that only the Orange based ones will be excluded from the update. With the speed they are releasing the updates, probably half of the world won't have the update.
[Android Q&A, Help & Troubleshooting] Anolnx:
I second that. We won't be the only ones left on the side, obviously ... But at least for us it's 99% sure. Counting on you guys!
[Android Q&A, Help & Troubleshooting] aleksandar_021:
Can someone from Hungary pull his factory Froyo 2.2 ROM and post it for download?

It must be complete ROM

Then people in Serbia could upgrade their software to 2.3 Gingerbread. Flash Hungarian 2.2, and then flash Hungarian 2.3...I think it can be done like that.

Thanks in advance.
[Android Q&A, Help & Troubleshooting] souxin:
Hi ,

i was try fastboot on my ot-990.

1/ first in the windows teminal, with adb command line , i boot in fastboot mode. (pc installed a driver by windows update)

2/ Mobile , boot in fastboot mode

3/ in the windows terminal, i tape "fastboot oem unlock" for de-simlock or unlock operator ...

4/ nothing happen :-((( , it's freeze at the command line of my windows terminal prompt
[Android Q&A, Help & Troubleshooting] TROMOKRATHS:
Could someone make a video tutorial on how to do this fone root? pls is so difficult with the description!!!!:o
[Android Q&A, Help & Troubleshooting] Zedok90:
Hi! did you root the alcatel ot-990?