Blue Tint Issue - My Experience

[Guest aleckxander]

Well straight to the point, these are the steps I did

- New TFT orange san francisco

- Universal AndRoot (Woot! your device ........)

- ClockWorkMod Recovery 2.5.0.9 (i didn't pay attention to the blue issue actually after this step)

- When i enter clockwork the bot turns cyan

- Wiped data & factory

- Modaco Custom Froyo ROM alfa 3

- Everything works fine but i finally note the blue issue on the screen

- I read somewhere here that the rom does its best with the newest clockwork.

- ClockWorkMod Recovery 2.5.1.3 installed

- Modaco Custom Froyo ROM alfa 3 installed again

- Still blue issue

- Read some thread here where is suggested to reinstall the Stock rom

- Wiped data & factory

- Stock Orange ROM (B08) installed

- ClockworkMod Recovery works no more

- Stock rom works but still with the blue issue.

Now.. I'm quite lost.

[Guest Rusty!]

After you flash B08 (system + boot) the blue tint should go. I've done it enough times to know :)

[Guest aleckxander]

After you flash B08 (system + boot)

Can you clarify this point? i mean.. i uploaded the OUK_P729BV1.0.0B08_update_signed.zip into the root of my sd card, run the ClockWorkMod Recovery 2.5.1.3 and installed from .zip, as usual. Am i missing some step?

[Guest Rusty!]

That should be it, assuming that boot.img was present in the file.

[Guest Sebastian404]

Can you clarify this point? i mean.. i uploaded the OUK_P729BV1.0.0B08_update_signed.zip into the root of my sd card, run the ClockWorkMod Recovery 2.5.1.3 and installed from .zip, as usual. Am i missing some step?

you mean you did a 'choose zip from sdcard' rather than the first option 'apply sdcard:update.zip' ?

[Guest fonix232]

Can you clarify this point? i mean.. i uploaded the OUK_P729BV1.0.0B08_update_signed.zip into the root of my sd card, run the ClockWorkMod Recovery 2.5.1.3 and installed from .zip, as usual. Am i missing some step?

Try with CWM 2.5.0.9, as 2.5.1.3 can not flash the boot.img (and that's why you got the blue tint).

[Guest aleckxander]

you mean you did a 'choose zip from sdcard'

exactly.. now i'm feeling a little stupid since the file name is OUK_P729BV1.0.0B08_update_signed.zip and i had probably to choose the 'apply sdcard:update.zip' intead of the one i selected..

any idea how to solve the problem now? ^^'

yes the file i downloaded has a boot.img inside (root of the zip file).

I am going to install CWM 2.5.0.9 with the stok B08 ROM as soon as I can while I wait for some other input from you..

[Guest Sebastian404]

exactly.. now i'm feeling a little stupid since the file name is OUK_P729BV1.0.0B08_update_signed.zip and i had probably to choose the 'apply sdcard:update.zip' intead of the one i selected..

any idea how to solve the problem now? ^^'

yes the file i downloaded has a boot.img inside (root of the zip file).

I am going to install CWM 2.5.0.9 with the stok B08 ROM as soon as I can while I wait for some other input from you..

no you picked the right option 'apply sdcard:update.zip' will look for a file called update.zip...

depending on when you downloaded the stock rom, it may not work with the the newer version of CWM, I repacked all the stock roms to work with the new version of CMW at the weekend...

best cause of action would be to try the old version of CWM with the update and see if that sorts it.

[Guest aleckxander]

Well, since i'm going to do everything from start I'm planning to proceed like this

THIS FastBoot

THIS ClockWorkMod (2.5.0.9)

THIS Stok Bo8 ROM (not able to find yours here around seb..)

Do you think there's a chance that this will solve my problem? ^^'

Edited June 3, 2011 by Paul

[Guest Rusty!]

Highly likely IMO

Seb's stock rom is: http://android.podtwo.com/roms/stock/OUK_P...date_signed.zip

[Guest aleckxander]

Do you think there's a chance that this will solve my problem? ^^'

[Guest aleckxander]

one step forward, two steps back.

i found a backup i did with nandroid some times ago taken from the original stock rom i had sadly corruped (deleted some apps and other files.. don't let me tell the details, i was young).

i restored it with CWM 2.5.0.9

obviously it kept the problems, but NO MORE BLUE TINT ISSUE..

i thought i had solved the issue so i downloaded the lite deoranged rom from seb.. but still.. once flashed the blue tint strikes back..

i really can't figure out the problem -.-

[Guest NightSt@lk3r]

restore your backup again so the blue tint goes away then try flashing pauls 2.2 alpha3 rom.

[Guest aleckxander]

ok guys tell me what do you think about this:

- you told me that 90% the problem was the boot.img

- don't tell me why but it seems (imo) that flashing a rom screws my boot.img no matter what CWM i use :)

- on the other hand restoring my old backup was successful.

my personal conclusion:

Flashed seb's deorangeated lite rom (and blue tint issue persists), restarted the phone entered CWM and entered in advanced restore, and restored ONLY the boot.img.

effect:

eureka! it works!

actually when it starts it shows the orange logo then the android one, but then it works smoothly

now.. i'm not so in depht with tecnical stuff, android and so on but i don't feel that much comfortable with such a "house" solution.

what do you think about it?

You think i'm going into some trouble?

will this solution be valid even if i want to flash a 2.2 rom?

[Guest aleckxander]

A little update.

as far as i flash a 2.1 ROM and i restore my original boot.img everything works fine. As i supposed i can't say the same when trying to flash a 2.2 rom.. It takes ages to load, and it loads only partially (status bar on the top, and black screen; tapping the screen does nothing, tapping phisical buttons make the phone vibe).

Don't know where all these test are bringing me. My real question now is:

Where's the difference between flashing a TFT and CWM compatible rom, and restoring an old boot.img?

Shouldn't CWM recovery acting the same way?

[Guest aleckxander]

even if i'm on holidays i got a couple hours to make a couple tests, (nothing relevant anyway):

I tried to use the new clockwork mod recovery compiled by seb, the only improvement (for me) is that entering CWM recoverymod gives me no more blue droid.

I tried to flash again a 2.2 rom, backup it and try to restore the same boot.ini; basically i meant to try if i had any boot writing issue while flashing a rom (since i still donß´t know where is the difference between the boot.ini i originally back upped and the oneused in the releases here).

well obviously no happy ending, so still stuck on 2.1 releases, and restore my original boot.ini to avoid blue issue tint.

[Guest john.smith]

CWM 2.5.0.9 doesn't seem to have advanced restore for boot.img only, or can you tell me in details?

Also I don't have a copy of the original boot.img, can else can I still get it?

I own a UK orange S.F. with TFT (white version), just bought from auction as advertised as unlocked but apparently flashed with failure also. :-(

my personal conclusion:

Flashed seb's deorangeated lite rom (and blue tint issue persists), restarted the phone entered CWM and entered in advanced restore, and restored ONLY the boot.img.