YES I have my HUAWEI U8230 BYTEL running Froyo 2.2.1 with quite a few of apps.
BIG THANKS to TWRock
for his useful hints and ROM.IMPORTANT: Because I only need to migrate my U8230 to Froyo 2.2.1 for Development purposes only, I have not extensively tested the robustness of the workaround.Status
There are HUAWEI U8230
smartphones used with Bouygues Telecom
(BYTEL) that have been upgraded with the latest firmware version U8230V100R001C101B282SP03
) dated june 2011 (I'll call it the B282 firmware for short
Devices with the B282 F/W CANNOT BE UPGRADED
with alternative Stock ROM (official ROM which are made of the dload folder with the UPDATA.APP file inside
The B282 BootLoader is recent and dated Jun 14 2011, 14:46:16 (the bootloader takes place BELOW the boot and the recovery. It displays the blue screen for connection to the Fasboot tool
Moreover, the B828 is referenced in none of the "upgradable_versions.txt
" files which are included inside the UPDATA.APP archives and this might be the reason for "upgrade failure
Unless we have the possibility to repack a UPDATA.APP archive, there is no possibility to overcome such issue.Consequences:
The migration toward v2.1 cannot be done using the T-MOBILE UK v2.1 (june 2010
) U8220V100R001C85B826 for example.
Moreover, without replacing the bootloader I cannot see how to change
the size of the memory foorprint
( 85MB for /system, 105MB for /data, 20MB for /cache
As of today, the v2.x Custom ROMs have larger footprints and fail to correctly install (the /system is full and incomplete
Therefore we have to TAILOR the ROM to match the memory footprint requirement. Hopefully this is not that difficult. POULPIX did it for the version 2.1 already.Workaround
1- Installed the Kichen
2- Extract the TWRock ROM : TWeak0.3.3-CM61-pulse.zip
3- Extract the DT Apps2SD : dtapps2sd_188.8.131.52_signed.zip
4- Extract the Google Apps : gapps-pulse-f0.3.3.zip
5- Take the installation script (META-INF\com\google\android\updater-script) and manually merge the 3 scripts
6- Move most of the "none-core" APK from /system/app to /data/app (/system went down to 79,3 MB
7- Keep as little as possible the media folder size (remove most of the alarms, notifications, ringtones
7- Extract the boot.image and change the makeboot string from "MEM=128" to "MEM=110" (I created the boot.img with a makeboot out of the kitchen using the scripts
8- Repack the boot.image
9- Rebuild the ZIP using the APK zalign and signature.
11- Install AmonRAR 1.5.2 and partition your SDCard (SWAP=64MB, SD-EXT=256MB/EXT2, remaining as FAT32)
optional but recommended - Install Clockwork 184.108.40.206
12- Wipe factory/cache/dalvik and Flash the ZIP (you loose all data
So far, so good! It did not crashed but sloo....oow down.
In addition to TWRock ROM, I added Skype, Barcode scanner, Bonk live wallpaper, compass, Deluxe Moon lite (not very stable app
), GPS essentials, Hj Lite (to speak Japanese
), Quick settings, Task manager, Weather widget & clocks. The good news is that it also runs my messy developed applications!Free tools I used:
Kitchen from dsixda - see posts above
Android command (not very stable but helpful
) - http://androidcommander.com/
EASEUS Partition Master 9.1.0 Home Edition - http://www.partition-tool.comTroubeshooting:
I had lot of trouble formatting my Sandisk 4GB class 4 sdcard. The sd-ext went corrupted once and it took me some time to understand it.
Not all apps where visible in the MENU. Actually, about 50% of the apps were copied into /data/app (which is moved to the sd-ext thanks to dtapps2sd
I used AmonRAR recovery to create the SWAP/EXT/FAT partitions.
Partition Master help me to erase/recreate the FAT32 and EXT2 partitions.
Using EXT3 partition was not a success and I fallback to EXT2.
- I had some trials which were continuously rebooting (warm-reboot where the bootanimation restarted in loop
) -> Check the boot.img file.
- Reboot: for some reasons, you SHOULD SKIP ALL configuration in the Startup Wizard
and enable Wifi, Google account and Sync ONLY AFTER you have setup the Apps on SD
in Cyanogen Menu and in Apps2SD application.
1- I have edited the thread title to better reflect the workaround
2- I'm Android system beginner, so please be kind to correct my mistakes or confusions