Jump to content


Photo

15/Jan [GUIDE] Installing the MoDaCo Custom Froyo ROM from scratch (and other ROMS)

* * * * * 18 votes

  • This topic is locked This topic is locked
673 replies to this topic

#1
StevenHarperUK

StevenHarperUK

    Hardcore

  • Moderator Team
  • PipPipPipPipPipPip
  • 1,431 posts
  • Gender:Male
  • Location:United Kingdom
  • Devices:Orange San Francisco
Hi Everyone,

This Thread has served it's purpose : It is now too large.

It has been split into 2 much more concise threads

[GUIDE] How to Install a Custom ROM on the ZTE Blade

and

[ROMS] Current Known / Available ROM's for the ZTE Blade


Anything that is not fitting to them threads will be moved / replicated /added to

[GUIDE] Common Problems / Questions / FAQ

or

[GUIDE] Android Glossary - Ideal for New Users


Thanks for all you help support and feedback.

This thread will stay here unpinned / but locked, for future reference.


Steven Harper



If you have a TFT screen, then Make sure the ROM you choose supports it.

Devices that have TFT Screens have the build Number OUK_P729BV1.0.0B08 (OLED can have this buid also - but rarely)
Devices that have OLED Screens have the build Number OUK_P729BV1.0.0B05

The build Number can be found in - Settings | About Phone | Build Number

On some ROMS you can use the Dialer to find out
Dial *983*24474636# in the dialer.
Then read here http://android.modaco.com/content/zte-blad...n-your-sanfran/

After or before putting a custom ROM over a STOCK ROM you should clear the cache and factory settings in clockwork.

Please see the table below; there is a column for which type screen is supported (OLED/TFT)


This post shows you how to Change your ROM using CLOCKWORK a newer technique has recently (1st Jan 2011) been discovered.
Please see the bottom section of the post called Total Phone Transfer


This post is designed to explain the 2 stages of getting a "out of the Box" Orange San Francisco to the state where it is running a custom ROM.
The steps in this guide take you thorough the steps for the r4-update-modacocustomrom-blade-signed.zip ROM, however you can change the last step and do any of the ROMS listed.

This post is NOT meant to replace ANY of the separate pages that give much more detail about the 2 stages covered and the products you are installing.
I HIGHLY recommend that you fully read the 2 posts linked to in the two steps. Also read the page on your ROM fully to understand what you are getting.


Here is some very good background reading about android basics - about what you are doing and how the phones boot modes work : http://www.androidguide.co.uk/guide/android-basics

Also here is a Glossary of terms : http://android.modaco.com/content/zte-blad...-for-new-users/

This guide was produced as I went through the journey of sorting out my own new device.
I am not the owner of any of the items mentioned, please ask about them in the correct thread(s) linked below.

This guide can be used to Install ANY Custom ROM that is installable with the ClockworkMod recovery system.
All you need to do is swap Step 2 ROM file with the custom ROM that you want.
Please be aware that each from will generate its own CRC, check that the CRC you are comparing it to is for the correct ROM.

When you install a custom ROM you should really clear your Data Cache and do a Factory Reset (more about this later) However if you do this you will lose your apps and data.
If you are Installing a ROM that is based on the SAME ROM you have on your phone, then you can try NOT clearing the cache and Factory Resetting (you can go back and do it if it needs to be done).
For instance

If you have the Standard ORANGE ROM OUK_P729BV1.0.0B05 (OLED) then you can install MoDaCo Custom Rom - r4 - without clearing the cache and factory resetting.
If you have the Standard ORANGE ROM OUK_P729BV1.0.0B08 (TFT) then you can install CustomBladeVillain RSL4 - without clearing the cache and factory resetting.


Read through the thread of the ROM you think you want to understand what you are getting.

Custom 2.1 Eclair ROMS
  • MoDaCo Custom Rom - r4 OLED (2.1 Eclair) provided by Paul - A stable rom that is designed for day to day use - has most of Orange features removed, adds useful Apps / Features
  • MoDaCo Custom Rom - r4 (no MoDaCo Additions) OLED (2.1 Eclair) provided by Paul - Same ROM as above without Spare Parts, Titanium Backup, WaveSecure, WiFi Status Indicator
  • Sebastian404's de-orangeated-rom - r8 - LITE/FAT TFT/OLED (2.1 Eclair) provided by Sebastian - A light as possible ROM with only essential updates done a super clean ROM - FAT has ZTE apps left in
  • BladeVillain1.1.0 - Villain ROMS's (2.1 Eclair) provided by kendon - Based on the Hungarian ROM (with the more stable wifi) but will all modifications removed A2SD built in - replaced stock Launcher with LauncherPro, rooted/busybox/apps2sd/betterzipalign, png optimised, all languages enabled, Cyanogen's huge APN file, TouchPal keyboard removed HTC IME Mod added, thanks jonasl@xda,Hardware acceleration enabled, Dalvik memory tweak
  • French Fries RLS4 (2.1 Eclair) provided by kallt_kaffe - Based on the French ROM with EXT3 support (A2SD) and Overclocking (as an Addon) - branding removed, rooted, default launcher pro, upped heap size, Flash Lite - and lots more fixes/changes
  • Sebastian404's de-bouyguesed ROM for ZTE Blade/Orange San Francisco - r6 - LITE/FAT (2.1 Eclair) provided by Sebastian - Based on the French ROM, light as possible ROM
  • Hungarian Hedgehog RLS1 TFT/OLED (2.1 Eclair) provided by kallt_kaffe - based on the hungarian ZTE Blade ROM, more recent than the French ROM, EXT3 (for better/safer Apps2SD),support for overclocking (available as addons), LCD support, lots of Kernel changes/tweaks, many added apks
  • Finnish Fillyjonk RLS5 TFT/OLED (2.1 Eclair) provided by kallt_kaffe - based on the finnish ZTE Blade ROM, more recent than the hungarian ROM, EXT3 (for better/safer Apps2SD),support for overclocking (available as addons) extra keyboards, TouchPal and XT9 IME, Circle battery indicator - Addon to support 5MP camera - LITE or FAT versions - HW Enabled
  • Customised BladeVillain 1.1.0 RLS4 TFT/OLED (2.1 Eclair) provided by freekers - Keeping Kendon's ROM Alive! - based on Hungarian ROM, Laucher Pro, Titanium Backup, Wifi Fixes, Stock boot animation, Camera sounds disabled - FAT and LITE versions
  • Swedish Snow RLS1 TFT/OLED (2.1 Eclair) provided by kallt_kaffe - Mystery ROM based on on TSE_P729VV1.0.0B01 (Comviq Sweden). Uses 124Mb in /system
Custom 2.2 Froyo ROMS based on Sept 2nd 2010 build (P729CUV1.0.0B01)Custom 2.2 Froyo ROMS based on October 11th 2010 build (P729CUV1.0.0B04)
  • MoDaCo Custom Froyo ROM Beta7-8 (based on new Chinese leak) TFT/OLED (2.2 Froyo) provided by Paul - Based on the latest R4 leaked Chinese Rom - Full up to date Google apps, Google account setup via WiFi, Tweaked to show full market, Set to English by default, Updated RIL and removed 'SecuritySMS',UK English for Voice Dialler, Updated lockscreen and homescreen background,su / Superuser.apk root, Support for running scripts from /etc/init.d at startup, Spare parts included + Lots More - Beta 7 prebake - Beta 8 Kitchen Only
  • Frankdroid r1 New Froyo Leak TFT/OLED (2.2 Froyo) provided by frankish - Based on the latest R4 leaked Chinese Rom - Hardware Acceleration Enabled,Google Apps added,Wifi status added,Removed bootsound,New boot animation.
  • FLB-Froyo G2 for ZTE Blade (r6) TFT/OLED (2.2 Froyo) provided by flibblesan - A Froyo 2.2 ROM with lots of fixes and customisations; ZTE or Stock Dialer, Turn to mute off Battery Dialer Fix, Launcher2, Browser homepage set to google.com,- Hand service in Settings changed, Hardware Acceleration enabled, Custom boot screen. WLAN renamed to WiFi, Most system apps updated, All Google apps updated to latest versions, Default wallpaper taken from T-Mobile US G2 (HTC Vision), MP3 notifications work. Podcasts work. Sound in streaming video works (TVCatchup.com for example), Ambient light sensor semi-working. Launcher2 and HSDPA icon, Cutom Kernel A2SD EXT2/3.
Custom 2.2 Froyo ROMS based on October 11th 2010 build (P729CUV1.0.0B07)
  • de-chinaed - r0.1 TFT/OLED (2.2 Froyo) provided by Sebastian - based on the perfect China Telecom V880 UNI_CN_P729CUV1.0.0B07 ROM, all of the google apps are missing, you can get install them from the addon zip
Custom 2.2 Froyo ROMS based on build (P729JV1.0.0B15)
  • Sebastian404's de-softened ROM - r0.3 ALPHA TFT/OLED (2.2 Froyo) provided by Sebastian - Alpha ROM, early Development - requires phone unlocked and does a full wipe during install, Not compatible with ClockworkMod Recovery 2.5.1.3. Based on a retail release of 2.2. Fast and stock throughout.
  • Japanese Jellyfish RLS7 TFT/OLED (2.2 Froyo) provided by kallt_kaffe - Now with source compiled Kernel. Requires phone unlocked. EXT2/3/4 A2SD, new display support, Gingerbread keyboard, HW enabled and stagefright, circle battery indicator,(native)Wifi Hotspot, USB tethering (mobile data or Wifi), Enabled AGPS and the checkbox to control it, woking FM radio, stock boot splash and nexus loading, added spare parts and titianium backup, removed CKPD-daemon. 50% AHB bus overclocking at 480 & 600MHz addon . Full CPU Overclock in new Kernel. Updated DNS.
  • FroyoBlade 0.3 TFT/OLED (2.2 Froyo) provided by fonix232 - Telephony not working yet - cannot make calls. Stock Froyo with root, Stagefright enabled, 32MB Dalvik VM heap, Enabled HW UI acceleration.
  • Volcano 0.2 TFT/OLED (2.2 Froyo) provided by isambard - TPT ROM based on Sebastians 0.2 ROM - changes system partitions
  • Xenorom r3 TFT/OLED (2.2 Froyo) provided by xenopod - Based on Japanese Jellyfish with Custom LG Evo Launcher
Stock ROMS More Stock ROMSComparison of Current ROMs

To help you pick a ROM.




ROM Name Base ROM KernelAndroid Version TFT Compatible Install MethodsSystem SizeRoot Screen Density Over Clock HW Accel A2SD Bloat Removed VM Size APN List Keyboard Default Launcher Titanium Backup
Stock Orange ROM (05) Orange Stock 2.1 OLED Clockwork? N 240 N N N N 24 Stock Touch Pal Stock N
Stock Orange ROM (08) Orange Stock 2.1 OLED/TFT Clockwork? N 240 N N N N 24 Stock Touch Pal Stock N
Stock Bouygues Telecom French Stock 2.1 ??? Clockwork? N 240 N N N N 24 Stock Touch Pal Stock N
Stock Hungarian Hungarian Stock 2.1 OLE/TFT TPT? N 240 N N N N 24 Stock XT9 IME Stock N
Stock Hungarian Clockwork 2.5.1.8 mod 0.2 Hungarian Stock 2.1 OLE/TFT TPT ? N 240 N N N N 24 Stock XT9 IME Stock N
Standard Partition Size (TPT)NONE Stock NA OLE/TFT TPT ? N NA N N N N NA NA NA NA N
MoDaCo Custom Rom - r4 Orange(B05) Stock 2.1 OLED Clockwork? Y 240 N Y EXT2* Y 24 Stock Touch Pal Stock Y
Sebastian404's r8 Orange(B08) Stock 2.1 OLED/TFT Clockwork? Y 240 N Y N Y 24 Updated Stock Stock N
BladeVillain 1.1.0 Hungarian Stock2.1 ???* Clockwork? Y 240 N Y EXT2 Y 38 Cyanogen HTC IME LaunchPro N*
French Fries RLS4 French Stock 2.1 ??? Clockwork? Y 240 Y Y EXT2/3 Y 32 CM6 HTC IME LaunchPro N
Sebastian de-bouyguesed French Stock2.1 ??? Clockwork? N 240 N Y N Y 24 Stock Stock Stock N
Hungarian Hedgehog RLS2 Hungarian Stock2.1 OLED/TF Clockwork? Y 240 Y N* EXT2/3 Y 32 CM6 HTC_IME LaunchPro Y
Finnish Fillyjonk RLS4 Finnish Stock2.1 OLED/TFT Clockwork128MB / Stock Y 240 Y Y* EXT2/3 Y 32 CM6 Gingerbread* LaunchPro Y
CustomBladeVillain RSL4 Hungarian Stock2.1 OLED/TFT Clockwork? Y 240 N Y EXT2 Y 38 Cyanogen HTC IME LaunchPro Y
Swedish Snow RLS1 Sweden Source2.1 OLED/TFT Clockwork / TPT128MB Y 240 CPU/AHB Y ? Y 24 ? Gingerbread* Stock N
Froyo Build, Alpha 1 Chinese R1 Modified Stock2.2 OLED Clockwork? Y* 160 N Y N/A Partial 48 Stock Stock Stock N
r4b gforums Custom Rom Chinese R1 Modified Stock2.2 OLED Clockwork? Y 240 N Y N/A Y 48 Stock Stock Stock Y
Stackbladroid v0.1 Chinese R1 Modified Stock2.2 OLED Clockwork? Y 240 Y Y N/A Y 32 Stock Stock Stock ??
MoDaCo Custom Froyo Beta7 Chinese R4 Source 2.2 OLED/TFT Clockwork? Y 240 N Y N/A Y 32 Updated Stock Stock Y
MoDaCo Custom Froyo Beta8 (kitchen) Chinese R4 Source 2.2 OLED/TFT Clockwork? Y 240 N Y EXT2/3 A2SD+ Y 32 Updated Gingerbread, HTC_IME, Stock Stock Y
Frankdroid r1 New Froyo Chinese R4 Modified Stock2.2 OLED/TFT Clockwork? N 240 N Y N/A Y ?? Stock Stock Stock N
FLB-Froyo G2 (r6) Chinese R4 Source2.2 OLED/TFT Clockwork? Y 240 N Y EXT2/3 Y 32 Updated Stock Launcher2 N
de-chinaed - r0.1Chinese R7 Source2.2 OLED/TFT Clockwork? Y 240 N N ?? Y ?? Updated Stock Stock N
de-softened Alpha r0.3 Japanese R15 Modified Stock/Source2.2 OLED/TFT Clockwork? Y 240 N N N/A Y 24 Updated Stock Stock N
Japanese Jellyfish RLS7 Japanese ReleaseSource2.2 OLED/TFT Clockwork / TPT128MB Y 240 CPU/AHB N*addon EXT2/3/4 Y 24 Updated Gingerbread Stock N
FroyoBlade 0.3 Japanese R15 Modified Stock/Source2.2 OLED/TFT Clockwork? Y 240 N Y N/A ? 32 Stock Stock Stock N
Volcano 0.2 Japanese R15 Stock2.2 OLED/TFT TPT128MB Y 240 N Y N/A Y 32 Updated Stock Stock N
Xenorom r3 Japanese Release Source2.2 OLED/TFT Clockwork130MB Y 240 CPU/AHB N EXT2/3/4 Y 24 Stock Stock LG Evo*, LauncherPro N

TFT COMPATABLE : UNKNOWN* means that some users have reported it working, but not confirmed by ROM developer.

Upgrading
If you are upgrading and already have Superboot and ClockworkMod recovery then you only need to perform Step 2 with the ROM of your choice.
When upgrading to a new ROM - especially if you are moving from another Custom ROM it is recommended to wipe the data/factory & cache partitions to prevent any potential issues.
This can be done in Step 2 (in the Clockwork Mod recovery menu) - When moving from MoDaCo r3 - r4 - a cache wipe should be enough - skip the data/factory wipe.

If you are upgrading from MoDaCo r3 to MoDaCo r4 and you had A2SD installed and a ext2 partition on your SD, the standard pre-baked r4 does not have A2SD in it.
You will need to re-install A2SD using the recovery menu (after flashing r4) - I also had to do the Clear Cache from the recovery menu and also then mount sd-ext2 and 2-3 reboots to get A2SD working.

The flashing to a Custom ROM is reversible - you just need to choose one of the STOCK ROMS for step two.
More Stock ROMS


If you are not comfortable with running commands in a terminal/command window, then I suggest you find a computer technical type person to help you.


There are 2 stages to getting the MoDaCo Custom Froyo ROM Installed onto an out of the box Orange San FranciscoYou can do the stages (and I recommend you visit the pages individually and check this guide is up to date) just by following the above links.

Here is (Saturday 27th Dec) current full instructions for a brand new phone - Flashing from Ubuntu (10.10)

Please note, that you WILL NOT lose any settings or files during the installation - you will lose the removed Orange Apps and you will have to remove - select your widgets again.
Its probably a good idea to remove the widgets you have from the 5 screens before you start - as after the flash they all won't load.
You should still Backup any important files before you start.


The only tool you need is a md5sum checker.

MD5sum is a way of checking that the file you have downloaded has not been corrupted in any way, when you run the MD5sum command against a files the response is the files "fingerprint", if this differs from the expected MD5, then you need to re-download the file.
The MD5's mentioned are for the specific releases detailed here, and other distributions (or updates) to the files we MD5 will, generate different checksums.

Linux
Ubuntu has md5sum built into it - however, if it does not work you can install it.
In Ubuntu its part of the coreutils package; you can install this with the command

sudo apt-get install coreutils

Windows
Get your md5sum utility from: http://www.md5summer.org/md5sum.zip (COMMAND LINE VERSION)
Extract this Zip file contents and put them into your Fastboot directy.

OSX
Use the built-in features of ssh
Note that you can only use fastboot-mac and adb-mac on Macs with an Intel cpu. They don't run on PPC Macs (G3, G4 or G5).
If you need to mod on an older MAC then read this post
openssl md5 <FILE>



This Guide assumes you are working on a Linux OS
The fastboot.zip however has the same commands for windows and osx included within the zip.
The linux command end with -linux the osx ones end with -mac and the windows ones end with -windows.
Just substitute the right command for your OS.
The only difference with the Linux command is that you need sudo in-front of the command and you have to add a ./ infront of the executables

The Linux command
sudo ./fastboot-linux flash recovery  recovery-clockwork-blade-2.5.1.8.img
On Windows is
fastboot-windows flash recovery  recovery-clockwork-blade-2.5.1.8.img
On OSX is
./fastboot-mac flash recovery  recovery-clockwork-blade-2.5.1.8.img


If you are working on windows - don't cd to your desktop - it is much simpler to work on the root of C drive

So in STEP 1, move the Fastboot.zip onto c:\
then right click on it and extract all

There will be a new directory called fastboot

Open a command window (or command prompt), and run these commands

c:
cd c:\fastboot

Now you can copy any files (the other .zips) and run the other commands in the open command window


It has been noted that if you are on windows and get stuck at "waiting for device" when using the fastboot-windows you should install divers: see http://android.modaco.com/content/zte-blad...rivers-and-adb/
Some users report these drivers work when the first dont : http://flibblesan.co.uk/android/zte_driver.zip

Sometimes switching to another USB port on your computer can solve the "waiting for device".

Many users have driver/connection problems in windows XP / Vista / Windows 7 - all of the users that have tried the same procedure on an Ubuntu Live CD have had no problems.
I recommend you use an Ubuntu live CD
To do this:

  • Download a 32bit 10.10 CD from http://www.ubuntu.com/desktop/get-ubuntu/download - it will be in .iso format
  • Download ImgBurn from http://www.imgburn.com/index.php?act=download
  • Burn the .iso file to a new blank CD
  • Boot from the new CD (This will not change your current OS, Ubuntu runs from the CD) - You may need to change your bios boot order to look for the CD before your harddisk. In your computers bios you get to choose which drive the PC will boot from first : Modern machines have F12 or F10 to choose which drive to boot from as the machine boots.



Stop! Before you start its a good idea to let the Orange SIM Card register - so that you can one day use the 10 - quid you put on it.
Devices that are not bought in a shop need to be Activated onto the Orange network otherwise they are barred by the IMEI - A quick call to Orange will get them un-barred - if you miss this step then you can never use an Orange SIM in the device.
Also I recommend you check that all your hardware works first : Make calls, try the buttons - check it charges.
If you need to warranty return a broken on arrival phone its going to be more easy if you don't ROM it.
However if you have - Just do step 2 with the Stock Orange ROM (above).

If your SIM has a PIN code you need to take it off for the first boot after flashing a ROM

Please be careful, take your time: I am not responsible for anything that goes wrong.


Stage 1: Install ClockworkMod - Using PC


Download fastboot (ROMraid Load Balancing)
http://loadbalancing.modaco.com/download.p...ul/fastboot.zip
(Check the Stage 1 top link to make sure this is the latest version)

Extract fastboot on your Desktop (windows users do it on the root of C drive)

Download 2.5.1.8: ClockworkMod Recovery
http://android.modaco.com/content/zte-blad...overy-oled-tft/
You can try the older version recovery-clockwork-2.5.0.9-blade.img if you really want.

Move the file recovery-clockwork-blade-2.5.1.8.img into the fastboot directory

Open a Terminal (or a command window if you are in Windows)

cd Desktop/fastboot

Windows alternative command cd c:\fastboot

md5sum recovery-clockwork-blade-2.5.1.8.img
Check that the outputted MD5 is: cae9935b88359dc96859d39f20d8a821

Turn off your phone and take out the battery. Unplug the phone from the PC / charger.

Replace the battery and turn the phone back on with 'volume up' held. The device will stay at the 'green android' screen.

Plug the phone into the PC.

In the terminal (still in the fastboot directory)
sudo ./fastboot-linux flash recovery  recovery-clockwork-blade-2.5.1.8.img

Windows alternative command fastboot-windows flash recovery recovery-clockwork-blade-2.5.1.8.img
MAC if you see the error : ERROR: could not get pipe properties rebooting... you should be able to ignore it - check you can get into clockwork (see step 2)
all If you get "writing 'recovery'… FAILED (status read failed (Protocol error)) android" change the usb cable, and try another USB port.
all If you keep getting waiting for device and you have tried installing drivers - then you could try the alternate Stage 1 (see below) which does not use fastboot


When this finishes, in the terminal run
sudo ./fastboot-linux reboot

Windows alternative command fastboot-windows reboot)



Wait for the phone to reboot

You can now use the Volume Down button (when powering on the phone) to get to the ClockworkMod menu



Stage 2: Unzip/Install the Rom

This step is shown for the MoDaCo ROM, however you can do any ROM that supports Clockwork Mod - see top of post.
If you have a TFT device DO NOT install r4-update-modacocustomrom-blade-signed.zip : Look above and pick a ROM that is TFT compatible

Download the Custom ROM for San Francisco: (MoDaCo Froyo Beta 7 ROM) - DOWNLOAD (ROMraid Load Balancing)
http://loadbalancing.modaco.com/download.p...en-unsigned.zip
(Check the Stage 2 link to make sure this is the latest version)

Put the r7-update-modacocustomrom-blade-kitchen-unsigned.zip file onto your desktop
Open a Terminal (or a command window if you are in Windows)

cd Desktop

Windows alternative command cd c:\fastboot

md5sum r7-update-modacocustomrom-blade-kitchen-unsigned.zip
Check that the outputted MD5 is: 385afa0b5d5f7d619e8fe8201eacb3f7

Plug your phone into the USB cable, and let the SD card mount (this works without any drivers in Ubuntu).
Copy the r7-update-modacocustomrom-blade-kitchen-unsigned.zip file off your desktop into the ROOT of the sdcard (this means copy it onto the sdcard - but not into any of the directories)

Turn off your phone and take out the battery. Unplug the phone from the PC / charger.

Replace the battery and turn the phone back on with 'volume down' held. The device will go to a ClockworkMod Recovery menu screen.

If you want to make a complete backup of your entire phone : use the clockwork option backup - this will put a FULL backup of your device onto the SDCard (in a directory called clockwork)

(the screen may be upside down if you have an older version of Clockwork) dont panic this is correct
  • Use Volume Up / Down to move between options
  • Use Home key to select an option
  • Use Back key to go back
Choose the 5th item "install zip fom sdcard"

Choose the 2nd item "choose zip from sdcard"

Choose the file "r7-update-modacocustomrom-blade-kitchen-unsigned.zip"

Choose the various yes options

When complete use the back button to get back to the main menu


If you are moving to a new Custom ROM, or changing between 2.1 and 2.2 you Must reset the device (this will reset the phone losing your apps and data).

  • From the clockwork menu choose: Clear Cache
  • From the clockwork menu choose: Factory Reset

If you skip the cache wipe factory reset and the phone doesn't boot properly then you need boot back into clockwork to clear the cache and factory reset
To get back into clockwork
  • Remove the battery
  • Put the battery back in
  • Hold the Volume Down button turn the phone on
  • From the clockwork menu choose: Clear Cache
  • From the clockwork menu choose: Factory Reset


Choose the 1st item "reboot now"

The phone now reboots.

If you installed an older 2.2 Froyo ROM (Except for the MoDaCo new 2.2 ROM) then the first connection to Android Market must be done through 3G!

As it boots you will see the MoDaCo splash screen instead of the android one (if you choose the MoDaCo ROM - all ROMS have differnet splash screens).

After reboot you can go into Settings | About Phone
Scroll down to the bottom and your Build Number should read MoDaCo Custom Froyo ROM for the Orange San Francisco Beta7

If you see the error SIM Network unlock PIN then the ROM you have flashed was not made for your SIM and you need to generate an unlock code so the phone can be used with ANY SIM (see Free Version )



Tidy Up

You may need to clean up a bit here and remove old widgets and re-put them back down - I had left my widgets on and they had all force-closed.
You will notice that the device is slow at first as it sorts itself out (3-5 minutes for me)

I rebooted and all was slick again



Java VM size (Entirely Optional)

I have found that upping the Java VM size from 24MB to 32MB really seems to help (Some ROMS have done this already - see table)
People have reported it fixing the Camera "banding" issues.
As long as you have Superuser you can grab it from the market (VM Heap Tool)
http://forum.xda-developers.com/showthread.php?t=803470



Tethering on 2.1


Also now you have Superuser you can add wifi tethering to you 2.1 (2.2 has it built in) with this app (from the market)
Barnacle Wifi Tether
http://szym.net/barnacle/



Rooting your ROM

Some ROM's come pre-rooted, if you want ROOT you can always add it after installing the ROM.

Rooted means that the Super user program has been installed and added into the system partition of the Phone

The program lives in /system/bin/su and has a link in the App Drawer on your phone.

ROMs that are rooted have the file and the link, ROOT is used to run programs as Super User, once they have these rights they can Change and Read files that are normally protected from APK's (normal Programs from the Market)

When you start an App that requires superuser, superuser will ask you to either Grant or Deny the access.

You can ADD Super User (root your device) by downloading and installing a special APK.

Info here


http://forum.xda-developers.com/showthread.php?t=747598
http://blog.23corner.com/tag/universalandroot/
http://blog.23corner.com/2010/08/30/univer...ta-5/#more-4077


Download
http://bit.ly/9wAKC5


Phone Space (Memory) Management on 2.2 ROMS


On 2.1 ROMS you can use a method of storing all apps on your SD Card - this is called A2SD (Apps too SD) this was handy, but rather complicated.

On 2.2 Roms you can move (some) apps to your SD Card; you have the option in settings then manage apps to move app to SD

This feature is enabled / disabled by the developers of each app.

The App (Move2SD; linked below) allows you to move ANY app to the SD card - this is ok for anything that is not a WIDGET or a LIVE WALLPAPER.
But you should test the apps after moving them (you can easily move them back).
http://www.appbrain.com/app/move2sd-enable...installlocation

All Move2SD does it to allow you to move ANY apps you like (you have to launch Move2SD and choose this)

Move2SD Requires Root (Superuser - see above).



Unlocking for ANY SIM


If you see the error SIM Network unlock PIN when you turn on the phone, then the ROM you have flashed was not made for your SIM.
You need to generate an unlock code so the phone can be used with ANY SIM (see Free Version)


Themes


Themes are usually supplied as a single ZIP file that is applied using clockwork
You simply treat them like a ROM, simply in clockwork choose install zip fom sdcard and select the file
Themes will ONLY work on ROMS stated in the thread - read them

You should ALWAYS do a full clockwork backup (nandroid backup) before you apply a theme zip

Always let a new ROM boot BEFORE you install the theme - some ROMS wont boot if you flash over a newly installed ROM

Here are some current Theme threads


Troubleshooting


People have tried the following with success when unable to boot / flash

  • If your phone will not boot after flashing a new ROM then you probably need to clear the cache and do a factory reset (in clockwork) - (this will reset the phone losing your apps and data)
  • re downloaded the .img (clockwork or ROM) and also re md5sum
  • if you are trying with clockwork 2.5.1.3 switch to 2.5.0.9 or 2.5.1.8
  • If your SIM has a PIN code you need to take it off for the first boot after flashing a ROM
  • reformatted the SD card to FAT32
  • try booting without the SD Card
  • If you get "writing 'recovery': FAILED (status read failed (Protocol error)) android" change the usb cable, and try another USB port.
  • If you keep getting waiting for device when trying to flash clockwork using fast boot - you could try the alternate Stage 1 (see below)
  • double checked that the SD card is on auto mount and that USB debugging is on
  • If you see the error SIM Network unlock PIN then the ROM you have flashed was not made for your SIM and you need to generate an unlock code so the phone can be used with ANY SIM (see Free Version
  • If you cannot get data over 2g/3g then your APN setting may be wrong - see http://android.modaco.com/content/zte-blad...work-providers/
  • If you are unable to get the new Japanese ROMS to mount USB do the following Applications>Development>USB Debugging>Turn Off>Turn On USB Storage
  • 2.2 ROMS have problems with FM Radio - a new App is in Development by andorko
  • If you are having problems with clockwork you could always try an Alternative Recovery app RA_Recovery



ALTERNATE Stage 1: Install ClockworkMod - Flash Clockwork without Fastboot


If you can't get fastboot on your computer to see you phone and it is stuck at waiting for device, then you can install clockwork without using fastboot and a computer.
I do suggest you get fastboot working - as it allows you to recover from any problems - this alternate method should be your second choice.

You can not do this alternate stage unless you have ROOTED your phone (have superuser installed) - see above Rooting your ROM

Download 2.5.1.8: ClockworkMod Recovery
http://android.modaco.com/content/zte-blad...overy-oled-tft/
You can try the older version recovery-clockwork-2.5.0.9-blade.img if you really want.

Move the file recovery-clockwork-blade-2.5.1.8.img into the fastboot directory

Open a Terminal (or a command window if you are in Windows)

cd Desktop/fastboot

Windows alternative command cd c:\fastboot

md5sum recovery-clockwork-blade-2.5.1.8.img
Check that the outputted MD5 is: cae9935b88359dc96859d39f20d8a821

Plug your phone into the USB cable, and let the SD card mount (this works without any drivers in Ubuntu).
Copy the recovery-clockwork-blade-2.5.1.8.img file off your desktop into the ROOT of the sdcard (this means copy it onto the sdcard - but not into any of the directories)


Download and install the Terminal Emulator from the Market
http://www.appbrain.com/app/android-termin...pal.androidterm

Start the Terminal Emulator on the phone

First to get ROOT we enter the following command (and hit return)
su

Then we Flash the Clockwork img to the recovery part of the device
flash_image  recovery  /sdcard/recovery-clockwork-blade-2.5.1.8.img

Close the Terminal Emulator application.

You can now use the Volume Down button (when powering on the phone) to get to the ClockworkMod menu

Now go and do Stage 2


Total Phone Transfer


This technique uses a much lower level method of updating your ROM.

It is MUCH simpler than using Fastboot, installing Clockwork and then Putting a ROM on your phone.

However it is NEW, and in development - and only a few ROMs are currently available (but they are newer ones).

Using TPT allows you to change all of the sections of your phone in one single install. This means that the BOOT, RECOVERY and ROM all get installed together.
TPT also has the power to change other much deeper parts of the device; the first discovery has been that you can change the partition sizes.

This means the the Spare space (MB) in the system partition location - can be squeezed down so that you have more space to install Apps in the data partition.
The ROM developer will pick the correct size partition for their ROM.

Here is a video of TPT in action http://www.youtube.com/watch?v=pX78MnDKwOA (thanks isambard)

Reversing the process

Currently you would have to apply the STOCK Hungarian TPT to get your partitions back to normal.
However as a side effect you will have a phone that is exactly as the Hungarian phones are shipped.
You would then need to follow this guide to put on a stock ROM of your choice.


Compatibility

Currently the Hungarian TPT has been confirmed to work on ZTE Blades from the following countries

  • Hungarian
  • Greek
  • UK - both TFT and OLED
  • French
  • Indian - Dell XCD35
  • Austrian
  • Switzerland
Please (if you are not a hardcore user) DO NOT TRY it on a device not confirmed


Where are the TPT ROMs



Japanese Jellyfish R7 TPT-ROM (OLED/TFT) by kallt_kaffe Based on the Japanese ROM with thenew source compiled kernel (system is decreased to 128MB) AD7423E804A16EA35394A4B912A6509B

The Froyo 2.2 Volcano 0.2 TPT-ROM (OLED/TFT) by isambard - based on Sebastian's 0.2 ROM - increase data space to 287mb (system is decreased to 128mb) c9de5fe702a2874dfeaf6235a5598b7bThe Stock Hungarian ROM (TPT) abea0d620cbf63d362069a0f76069860Stock Hungarian Clockwork 2.5.1.8 mod 0.2 5b13e8c1a8f72b7b4241c5f658933334Standard Partition Size C8010D841AF463F3CB1FDEDFFAFA3B1E


Preparation

YOU MUST NETWORK UNLOCK YOUR PHONE BEFORE INSTALLING
Go here and get your phone unlocked first http://android.modaco.com/content/zte-blad...-and-zte-blade/


Be sure before you carry on


ClockworkMod install method is much safer, more universal and more recoverable. If the device you have is not in the compatibility list then STOP. This update method - if applied to a device that's not supported - may BRICK IT (make the phone unrecoverable)


Check the the file is not corrupted


Now use a md5sum utility to check that the file has not been damaged while downloading

Linux
In a terminal, cd to the directory where you downloaded the file and run the command

md5sum image.zip

Windows
Download the Utility http://www.md5summer.org/md5sum.zip, extract the files into the same directory as the file you downloaded e.g. volcano2.zip
Open a command windows, cd to the directory you put the volcano2.zip, then run the command
md5sum volcano2.zip

OSX
Open a terminal, cd to the location you put the files, then run the command
openssl md5 volcano2.zip


The Md5sum output should match the one next to the download - see Where are the TPT ROMs (above)


Applying a TPT

  • Mount your phone on USB or put the SDCard into a USB card reader.
  • Create a directory called image (lowercase) on the root of the SDcard (not in any other directories on the sdcard)
  • Extract the contents of the ZIP file to the image directory on your SD card

    (For example: If the drive letter of the SD card is "S:" then extract the content of the ZIP to S:\image)


  • Unmount the SDCard and turn the phone off, remove the battery, put the battery back in.
  • Switch on your phone by holding Menu + volume up + power (hold all three together)
  • Installation will automatically update your firmware, after it the phone restarts (When the updating process starts, you can release the keys) you may or may not see green text here - some users dont
  • After booting - remove or rename the image directory on your SDCard or you can accidently re-flash your phone



Thanks

Many thanks to Paul for the original pages / guides / ROM and to MoDaCo and all the other users who made the tools used.

Thanks also to
Sebastian404
Stephen Hyde
kendon
kallt_kaffe
gforums
flibblesan
stackrish
frankish
freekers
Arr Too
andorko
isambard
fonix232
xenopod
hecatae

for their ROM contributions and tools.


Enjoy

Steven Harper



[color="#FF0000"]If you use this guide and it works, please give me a post so I can see that it's doing it's job.

Also if you spot any typo's - or get stuck because something wasn't clear - please post - it all helps.


Latest Update

17th January - Added ROM de-chinaed - r0.1 by Sebastian404
15th January - Added Switzerland to TPT compatible devices
15th January - Added more Themes
14th January - Updated Stock Hungarian Clockwork 2.5.1.8 mod 0.2 by hecatae to be a TPT ROM
14th January - Updated Guide to be for MoDaCo Custom Froyo Alpha 7 - no longer are instructions for 2.1 ROM r4
14th January - Updated ROM MoDaCo Custom Froyo Beta 7-8 by Paul
14th January - Updated Xenorom r3 provided by xenopod - now mased on Japanese Jellyfish
13th January - Updated Sebastians newly named - recovery-clockwork-blade-2.5.1.8.img
13th January - Updated Japanese Jellyfish to R7, Added ROM Standard Partition Size (TPT)
12th January - Updated text on checking if you have TFT or OLED
12th January - Updated ROM MoDaCo Custom Froyo R5-6 by Paul - also gave R6 its own line in the table
12th January - Added ROM Stock Hungarian Clockwork 2.5.1.8 mod 0.2 by hecatae
12th January - Added ROM Xenorom r2 provided by xenopod
12th January - Added Bazza76's new theme for FLB G2 r6
11th January - Updated innish Fillyjonk to RLS5 by kallt_kaffe - HW Acceleration by default (addon to turn off) Also now a 128MB version to fit in resized Partition (TPT)
9th January - Updated Swedish Snow RLS1 by kallt_kaffe - not the first 2.1 ROM with a source kernel - Overclock also and with TPT install. Added new Column System Size to table.
9th January - Updated Japanese Jellyfish to r6, Updated FLB-Froyo G2 Theme info
9th January - Added Austrian to the confirmed TPT devices, Added RA_recovery to Troubleshooting
8th January - Indian - Dell XCD35 Confirmed to work with Hungarian TPT
8th January - Updated ROM FLB-Froyo G2 (r5) by flibblesan - now on source Kernel - re-signed so existing Themes will NOT currently work. Lots of new features on this ROM.
7th January - Updated Japanese Jellyfish to R5, Updated de-orangeated ROM to r8, Added extra colums to table, Added extra TPT Roms, Added Stock ROM
5th January - Added the mysterious Swedish Snow RLS1 by kallt_kaffe
4th January - Updated instructions to handle renamed recovery_clockwork_2.5.1.8_blade.img (and not a zip anymore)
4th January - Added ROM FroyoBlade 0.3 by fonix232 - sorry I missed it for a bit
4th January - Added Glossary link
3rd January - Updated ROM Japanese Jellyfish RLS4 by kallt_kaffe, Updated FLB-Froyo G2 (r5a) by flibblesan
2nd January - Updated ROM de-softened Alpha r0.3 by Sebastian404
2nd January - Updated table to be html thanks Arr Too
2nd January - Added even more warning to TPT update method.
2nd January - Updated ROM FLB-Froyo G2 (r5) - also updated ROM table - cheers for corrections (flibblesan & isambard)
2nd January - Added new "Total Phone Transfer" section and also added the 1st ROM - Volcano 0.2 TPT-ROM (OLED/TFT) by isambard
2nd January - Updated ROM FLB-Froyo G2 (r4a), updated themes
1st January - Updated ROM FLB-Froyo G2 (r4) now TFT compatible & now based on the Chinese R4
1st January - Updated ROM Japanese Jellyfish RLS3b by kallt_kaffe
31st December - Updated ROM Japanese Jellyfish RLS3 by kallt_kaffe - New Tethering fixes and Working Radio
30th December - Added Themes section
30th December - Fixed wrong ROMS marked as TFT, also added extra warning at beginning of stage 2 thanks to Paul Fraser
30th December - Added 2.2 FM Radio APK - thanks andorko
29th December - Changed Stock ROM back to Pauls
29th December - Updated ROM Japanese Jellyfish RLS2 by kallt_kaffe
29th December - Fixed instructions they didnt allow for new clockwork.zip
28th December - Updated guide to Clockwork 2.5.1.8 and also fixed a broken link, added Mount USB for Japanese ROMS to troubleshooting
27th December - Added ROM Japanese Jellyfish RLS1 by kallt_kaffe, also separated JavaVM Size and 2.1 Tethering
27th December - Added ROM de-softened Alpha r0.2 based on new Chinese R15 by Sebastian404 - Well done Seb
25th December - Added APN to troubleshooting
25th December - Added section on Unlocking for ANY SIM - Link to Free tool (APK) - thanks Arr Too
25th December - Added section on Phone Space (Memory) Management on 2.2 ROMS - Move2SD App
23rd December - Updated ROM Finnish Fillyjonk to RSL4
19th December - Added ALTERNATE Stage 1: Install ClockworkMod - Flash Clockwork without Fastboot
18th December - Updated ROM Finnish Fillyjonk to RLS3
17th December - Added info on wiping Apps and data (and when it needs to be done), Clarified md5sum util info, detailed the clearing of the cache and factory reset in steps
16th December - Added workround for SIM Network unlock PIN
16th December - Small fixes and added background reading http://www.androidguide.co.uk/guide/android-basics
16th December - Updated ROM r7 de-orangeated ROM for ZTE Blade - now TFT/OLED - but a Wipe is needed when upgrading from r6 - great work Sebastian
16th December - Added instuctions on backing up in clockwork - made the clear cache and factory reset more prominant, added command windows as a windowns alternative
14th December - Added new error suggestion when getting Protocol error when trying to write recovery - thanks zillfish
14th December - Updated ROM CustomBladeVillain RSL4
12th December - Updated md5sum for MoDaCo R4
11th December - Removed the POLL, votes were conclusive.
11th December - Added info an ignorable warning when install Clockwork on MAC, also clarified copy a file to ROOT of SDCARD
10th December - Updated may of the ROMS TFT Compatible status
10th December - Added known issue of having a pin locked SIM on first boot.
9th December - Updated ROM Finnish Fillyjonk to RLS2
8th December - Updated ROM Hungarian Hedgehog RLS2 and Finnish Fillyjonk RLS1 to be TFT and OLED
8th December - Updated ROM CustomBladeVillain RSL3 to be Compatible with TFT and OLED
7th December - Updated ROM CustomBladeVillain RSL3
7th December - Updated ROM MoDaCo Custom Froyo ROM to be TFT and OLED compatible
7th December - Updated ROM FLB-Froyo G2 (Beta) to not be TFT compatible
6th December - Updated ROMS that are known to be TFT Compatible - Toned down the warning a bit - Added factory reset to stage 2
6th December - Updated Clockwork Link for 2.5.0.9
6th December - Updated Warning about TFT, Added TFT COMPATIBLE to the Table of ROMS
6th December - Added Warning for users with TFT Screens
5th December - Corrected BladeVillain 1.1.0 to be based on the Hungarian ROM
5th December - Updated MAC guide for older Power PC users
4th December - Rolled back to suggesting using Clockwork version to 2.5.0.9 - as people having issues with 2.5.1.3
2nd December - Added Customised BladeVillain 1.1.0 RLS2 provided by freekers
2nd December - Updated ROM MoDaCo Custom Froyo Alpha 2 - Alpha 3 in Kitchen
2nd December - Added ROM Finnish Fillyjonk RLS1 provided by kallt_kaffe
2nd December - Updated ROM Hungarian Hedgehog RLS2
1st December - Added ROM MoDaCo Custom Froyo Alpha 1 - excitement
1st December - Updated Clockwork version to 2.5.1.3 ClockworkMod Recovery for ZTE Blade
1st December - Added ROM Frankdroid r1 New Froyo by Frankish - ROM based on Chinese R4 ROM
30th November - Added ROM Custom 2.2 Froyo ROMS based on Sept 2nd 2010 build (P729CUV1.0.0B01) - in Advance of one being made.
30th November - Updated Stackbladroid v0.2
29th November - Added Section on Rooting
29th November - Added troubleshooting
26th November - Added More Stock ROM's Link
24th November - Updated ROM FLB-Froyo G2 for ZTE Blade r3a by flibblesan
23rd November - Added ROM Stackbladroid v0.1 (2.2 Froyo) provided by stackrish
23rd November - Updated ROM BladeVillain1.1.0 - Villain ROMS's (2.1 Eclair) - Interesting thread on Villainroms forum
19th November - Added ROM Hungarian Hedgehog RLS1 ROM (2.1 Eclair)
16th November - Added Froyo 3G connection warning
16th November - Streamlined into 2 Stages rather than 3
16th November - Added ROM Comparison table thing
16th November - Added ROM Sebastian404's de-bouyguesed ROM for ZTE Blade/Orange San Francisco - r6 and Stock Bouygues Telecom V1.0.0B11 ROM
16th November - Added ROM FLB-Froyo G2 for ZTE Blade (Beta) by flibblesan
15th November - Added ROM French Fries RLS4 - kallt_kaffe ROM (2.1 Eclair) with A2SD EXT3 and also Overclocking
15th November - Added ROM BladeVillain 1.0.1 - Villain ROMS's (2.1 Eclair)
09th November - Updated Sebastian's ROM to multi r6 (2.1 Eclair)
29th October - Added ROM r4b gforums Custom ROM (2.2 Froyo)
26th October - Added ROM 2.2 Alpha ROM (2.2 Froyo)
25th October - Updated Sebastian's ROM to r5 (2.1 Eclair)
24th October - Added even more instructions for Windows users (working in the root of C Drive)
23rd October - Added ROM Froyo 2.2 Alpha ROM and windows alternative commands
21st October - Added other pre baked MoDaCo ROMS (2.1 Eclair)
18th October - Added all Known ROMS

Edited by Paul, 03 June 2011 - 01:22 PM.

  • 1

#2
David Horvath

David Horvath

    Diehard

  • Members
  • PipPipPipPip
  • 345 posts
  • Location:Debrecen, Hungary
  • Devices:SF
Awesome howto, did it on Ubuntu 10.04 with an older adb/fastboot, worked like a charm.

  • 0

Ubuntu Lucid Lynx + Android Eclair on SF == freedom

#3
cdrummond

cdrummond

    Newbie

  • Members
  • Pip
  • 4 posts
  • Devices:Orange San Francisco
Cheers - a nice guide for those less experienced.

I've just tried to verify the checksum by running the md5sum command but get an error about md5sum not being recognised?

  • 0

#4
StevenHarperUK

StevenHarperUK

    Hardcore

  • Moderator Team
  • PipPipPipPipPipPip
  • 1,431 posts
  • Gender:Male
  • Location:United Kingdom
  • Devices:Orange San Francisco

Cheers - a nice guide for those less experienced.

I've just tried to verify the checksum by running the md5sum command but get an error about md5sum not being recognised?


I have added where to get md5sum tools for Windows, Linux and OSX to the main post

Thanks for the feedback

  • 0

#5
David Horvath

David Horvath

    Diehard

  • Members
  • PipPipPipPip
  • 345 posts
  • Location:Debrecen, Hungary
  • Devices:SF

I have added where to get md5sum tools for Windows, Linux and OSX to the main post

Thanks for the feedback


One thing. I did not reboot, just once. I dont think its necessary, or?

  • 0

Ubuntu Lucid Lynx + Android Eclair on SF == freedom

#6
StevenHarperUK

StevenHarperUK

    Hardcore

  • Moderator Team
  • PipPipPipPipPipPip
  • 1,431 posts
  • Gender:Male
  • Location:United Kingdom
  • Devices:Orange San Francisco

One thing. I did not reboot, just once. I dont think its necessary, or?


Honestly I don't know - If you have the superuser icon in your menu (and it works) then your probably ok.

I like to separate each step thou - you never know it may count when things update.

Edited by StevenHarperUK, 09 October 2010 - 11:57 AM.

  • 0

#7
dwattsy21

dwattsy21

    Enthusiast

  • Members
  • PipPipPip
  • 212 posts
Cool how to. I am using windows vista. At the top of the guide it says this guide is for linux... will it be the same for me on windows?

  • 0

#8
StevenHarperUK

StevenHarperUK

    Hardcore

  • Moderator Team
  • PipPipPipPipPipPip
  • 1,431 posts
  • Gender:Male
  • Location:United Kingdom
  • Devices:Orange San Francisco

Cool how to. I am using windows vista. At the top of the guide it says this guide is for linux... will it be the same for me on windows?


At the top of the guide there is a section that shows the difference in the commands (on WIndows you don't need the sudo in-front) and you dont need the ./ in-front of the executables

Otherwise its all the same.

  • 0

#9
dwattsy21

dwattsy21

    Enthusiast

  • Members
  • PipPipPip
  • 212 posts

At the top of the guide there is a section that shows the difference in the commands (on WIndows you don't need the sudo in-front) and you dont need the ./ in-front of the executables

Otherwise its all the same.


Cool cheers mate. After everything being so easy with a simple recovery image for my hero, this is quite daunting for me! I have got so far as extracting the fastboot stuff to my desktop, but it said it couldnt encrypt a "macosx" folder, and I cant see any folder called fastboot that I should be putting the superboot file in. Very connfused, have I done something wrong?

Cheers,
Dave

  • 0

#10
dwattsy21

dwattsy21

    Enthusiast

  • Members
  • PipPipPip
  • 212 posts
I now have a file, with like an icon of a blue and white window on my desktop called fastboot-windows. Is thsi the "fastboot directory"? and how do i move the boote.blade.superboot.... file into it?

  • 0

#11
StevenHarperUK

StevenHarperUK

    Hardcore

  • Moderator Team
  • PipPipPipPipPipPip
  • 1,431 posts
  • Gender:Male
  • Location:United Kingdom
  • Devices:Orange San Francisco

I now have a file, with like an icon of a blue and white window on my desktop called fastboot-windows. Is thsi the "fastboot directory"? and how do i move the boote.blade.superboot.... file into it?


On windows you need to get the fastboot.zip and right click on it and choose extract all

This will create a new folder with all the files in in. In there, there is a file called fastboot-windows
Put the Superboot file in the same directory so it sits alongside the fastboot-windows


Now open a command window and move to the new folder (assuming the folder is on your desktop and called fastboot
cd Desktop/fastboot

Now your ready to run the fastboot command
fastboot-windows flash boot boot.blade.superboot.mcri.r3.img

If your struggling it may be better to just move the extracted folder to the root of C drive and work there.
so the full path is C:\fastboot\ CD command would be

cd /fastboot

Edited by StevenHarperUK, 09 October 2010 - 02:36 PM.

  • 0

#12
dwattsy21

dwattsy21

    Enthusiast

  • Members
  • PipPipPip
  • 212 posts
"On windows you need to get the fastboot.zip and right click on it and choose extract all

This will create a new folder with all the files in in. In there, there is a file called fastboot-windows
Put the Superboot file in the same directory so it sits alongside the fastboot-windows"

Does this mean simply copy the superboot file, and paste it into my new fastboot folder which i have put on my desktop?

Thank you for your help

  • 0

#13
dwattsy21

dwattsy21

    Enthusiast

  • Members
  • PipPipPip
  • 212 posts
And when I am doing this should the phone be mounted via the USB yea? When does anything actually get transferred to the phone?

  • 0

#14
dwattsy21

dwattsy21

    Enthusiast

  • Members
  • PipPipPip
  • 212 posts
Think I'm going ok now, but in the command window i have typed in

cd Desktop/fastboot, then enter which put me in the right file.. then

md5sum boot.blade.superboot.mcri.r3.img

but this didnt work, givin em a message that "md5sum" is not recognised as an internal or external command, operrable program or batch file.

I have MD5 for windows open, so how do i make this work?

  • 0

#15
dwattsy21

dwattsy21

    Enthusiast

  • Members
  • PipPipPip
  • 212 posts
Really stuck on ths part now. Have installed md5sum and have opened it as an administrator and leave it running in the background. But when i type md5sum boot.blade.superboot.mcri.r3.img, it doesnt do anything just returns a message saying "md5sum" is not recognised as an internal or exxternal command...

Has anybody else had this issue? How did you get around it?

Cheers
Dave

  • 0

#16
dwattsy21

dwattsy21

    Enthusiast

  • Members
  • PipPipPip
  • 212 posts
"Windows
You can get a free md5sum utility here
[url="http://www.md5summer.org/download.html""]http://www.md5summer.../download.html"[/url]

you do download the top one right??

  • 0

#17
StevenHarperUK

StevenHarperUK

    Hardcore

  • Moderator Team
  • PipPipPipPipPipPip
  • 1,431 posts
  • Gender:Male
  • Location:United Kingdom
  • Devices:Orange San Francisco

"Windows
You can get a free md5sum utility here
[url="http://www.md5summer.org/download.html""]http://www.md5summer.../download.html"[/url]

you do download the top one right??


The md5 utility is used to check that the file has not been damaged. Use the windows one and skip the command.

The windows one simply checks the boot file and should generate the same id. If it does this,then you know the file is ok.

  • 0

#18
ken218

ken218

    Regular

  • Members
  • PipPip
  • 88 posts
  • Gender:Male
  • Location:London
Am I missing something here?

I found that if I want to install the custom ROM out of box, I can skip step 1.

So I just need to install the recovery image, then the custom ROM.

  • 0

#19
StevenHarperUK

StevenHarperUK

    Hardcore

  • Moderator Team
  • PipPipPipPipPipPip
  • 1,431 posts
  • Gender:Male
  • Location:United Kingdom
  • Devices:Orange San Francisco

Am I missing something here?

I found that if I want to install the custom ROM out of box, I can skip step 1.

So I just need to install the recovery image, then the custom ROM.


You need to root the phone as well (Step 1) : this allows you to run stuff as superuser

If you can do step 2, then Step 1 should be easy - its almost the same - just a different file.

Unless the 2nd Step also installs the superuser app. I don't know : I only have 1 device to test it on.

  • 0

#20
BillBong

BillBong

    Regular

  • Members
  • PipPip
  • 144 posts
This is a great guide. I was a bit apprehensive about trying it but this breaks it down in a nice way.

A lot of people put in a lot of work on this site so a big thank you to Paul and the others who make it easier for the noobs.

  • 0




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users