86 replies to this topic

[tilal6991]

Fastboot can also flash boot images. Try flashing from there.

[wrtease]

so why is the relacement having this problem ,shurely  it was just the usual stuff to run again and bobs your uncle ,something must be wrong somewhere.

[tilal6991]

Double post

[glossywhite]

tilal6991, on 24 October 2011 - 08:30 PM, said:

Fastboot can also flash boot images. Try flashing from there.

You mean:

./fastboot-linux flash recovery clockworkmod.img && ./fastboot reboot

?

If so, done that.

[tilal6991]

glossywhite, on 24 October 2011 - 08:32 PM, said:

You mean:

./fastboot-linux flash recovery clockworkmod.img && ./fastboot reboot

?

If so, done that.

nope. The boot.img inside the zip file. Copy it into the fast boot folder and ./fastboot-linux flash boot boot.img && ./fastboot reboot

[glossywhite]

tilal6991, on 24 October 2011 - 08:34 PM, said:

nope. The boot.img inside the zip file. Copy it into the fast boot folder and ./fastboot-linux flash boot boot.img && ./fastboot reboot

Okay. Gonna trash all BlueMonte ZIP files I have, and download one fresh and try that.


Wait here... LOL   __confidence__

Okay, getting all muddled up here. Let's rewind a little.

Step by step, what do I do first? Do I try cwm again AFTER flashing boot.img? SO confused now.

Edited by glossywhite, 24 October 2011 - 08:39 PM.

[tilal6991]

glossywhite, on 24 October 2011 - 08:36 PM, said:

Okay. Gonna trash all BlueMonte ZIP files I have, and download one fresh and try that.


Wait here... LOL   __confidence__

Okay, getting all muddled up here. Let's rewind a little.

Step by step, what do I do first? Do I try cwm again AFTER flashing boot.img? SO confused now.

Flash the boot image using fast boot. That's all you need to do.

[glossywhite]

I long for the old Nokia 3310. Life was much simpler

Okay, so after I have flashed the boot.img... then what?

Edited by glossywhite, 24 October 2011 - 08:46 PM.

[tilal6991]

glossywhite, on 24 October 2011 - 08:46 PM, said:

I long for the old Nokia 3310. Life was much simpler

Okay, so after I have flashed the boot.img... then what?

would you have as much fun with it though? No flashing. No hacking. I don't know how I survived

[tilal6991]

glossywhite, on 24 October 2011 - 08:46 PM, said:

I long for the old Nokia 3310. Life was much simpler

Okay, so after I have flashed the boot.img... then what?

Flash the rom in CWM.

[glossywhite]

I rebooted into bootloader mode, using ./adb reboot bootloader... now I get...


matt@(none):~/Desktop/r4-4.0.1.4-skate-clockworkmod$ ./fastboot-linux flash boot boot.img && ./fastboot-linux reboot
sending 'boot' (4096 KB)... OKAY
writing 'boot'... FAILED (remote: flash write failure)
rebooting...

Is bootloader mode the correct mode in which to flash boot.img, the same as how you flash the CWM image in? (Paul's method). Do I have the correct mode? Which mode am I to put the phone in, to flash boot.img?

This is fast becoming a mess of confusion.

Edited by glossywhite, 24 October 2011 - 08:58 PM.

[tilal6991]

glossywhite, on 24 October 2011 - 08:54 PM, said:

I rebooted into bootloader mode, using ./adb reboot bootloader... now I get...


matt@(none):~/Desktop/r4-4.0.1.4-skate-clockworkmod$ ./fastboot-linux flash boot boot.img && ./fastboot-linux reboot
sending 'boot' (4096 KB)... OKAY
writing 'boot'... FAILED (remote: flash write failure)
rebooting...

Is bootloader mode the correct mode in which to flash boot.img, the same as how you flash the CWM image in?

yes it is. I think orange has blocked your boot partition. I've never seen flash write failure before.

[glossywhite]

tilal6991, on 24 October 2011 - 08:58 PM, said:

yes it is. I think orange has blocked your boot partition. I've never seen flash write failure before.

Do you seriously think they have the time OR knowhow to go to all that trouble, for a new phone with less than 24hr turnaround?

[tilal6991]

glossywhite, on 24 October 2011 - 09:01 PM, said:

Do you seriously think they have the time OR knowhow to go to all that trouble, for a new phone with less than 24hr turnaround?

Its possible but as you say improbable. I'm out of idea. I would ask on the blade forum I they have any ideas.

[wrtease]

their seems to be a small battery under a metal strip ,this could be the cmos for clearing it to default in one of your pictures.maybe worth a go then maybe not .

[glossywhite]

wrtease, on 24 October 2011 - 09:07 PM, said:

their seems to be a small battery under a metal strip ,this could be the cmos for clearing it to default in one of your pictures.maybe worth a go then maybe not .

Not even going there, but thanks.


It seems that the /boot partition cannot be written to, which is causing all these crazy errors. I wonder if rooting the OMC after reverting to stock TPT will help?

Edited by glossywhite, 24 October 2011 - 09:17 PM.

[wrtease]

okay this might help ,why dont you put a backup folder of a backup on your sdcard then run it in clockwork and see if that helps.then restore as normal.worth a go.

[glossywhite]

wrtease, on 24 October 2011 - 09:17 PM, said:

okay this might help ,why dont you put a backup folder of a backup on your sdcard then run it in clockwork and see if that helps.then restore as normal.worth a go.

That is the first thing I tried. No go.


Here is the about screen, with build; does it look okay?

Attached Files

•  Image-4.png   421.96K   0 downloads

Edited by glossywhite, 24 October 2011 - 09:26 PM.

[wrtease]

all i can say is this is 1 which i cant figure out,anyway can you even reboot in to orange main screen and run some checks to see if it has force closes.or just give up for tonight and try tommorrow again.

[glossywhite]

Do you think the /boot partition has been re-secured? Is that even possible? If so, what is the next step... would you have to make a new ROM?