glossywhite

CWM error: Thoughts?

87 posts in this topic

Just tried installing Blue Monte Plus on my new OMC, and it threw me an error. Any thoughts?

Thank you!

post-625969-0-04455800-1319472205_thumb.

0

Share this post


Link to post
Share on other sites

here is the image http://files.podtwo....0.1.5-skate.img

get the recovery image above rename it to recovery.img

then drag & drop it into the rom's.zip where the recovery.img is...

should fix your problem smile.gif

Edited by tillaz
0

Share this post


Link to post
Share on other sites

Updated CWM to 4.0.1.5

Tried to restore...

"Error while flashing boot image!"

your boot.img must have been corrupted - try redownloading.

1

Share this post


Link to post
Share on other sites

Updated CWM to 4.0.1.5

Tried to restore...

"Error while flashing boot image!"

if you are just doing a restore, pull the boot.img from the roms .zip (if you still have it) & replace the boot.img in your back up smile.gif

1

Share this post


Link to post
Share on other sites

your boot.img must have been corrupted - try redownloading.

if you are just doing a restore, pull the boot.img from the roms .zip (if you still have it) & replace the boot.img in your back up smile.gif

Thank you!

[EDIT]

Nope, that failed too.

ALL recovery/install options are failing. Fresh bluemonte plus fails error 7...and have tried fresh copy of BlueMonte and a new, formatted SD card.

Okay

====

Done a TPT recovery, so back to square one. Now what? :)

Edited by glossywhite
0

Share this post


Link to post
Share on other sites

here is the image http://files.podtwo....0.1.5-skate.img

get the recovery image above & rename it to recovery.img

then open bluemonte plus, drag & drop it into the rom's.zip where the recovery.img is...

should fix your problem smile.gif

Edited by tillaz
1

Share this post


Link to post
Share on other sites

here is the image http://files.podtwo....0.1.5-skate.img

get the recovery image above & rename it to recovery.img

then open bluemonte plus, drag & drop it into the rom's.zip where the recovery.img is...

should fix your problem smile.gif

Thanks for your help dude. Trying this now, and will get back to you. :)

NOPE. Failed again.

Edited by glossywhite
0

Share this post


Link to post
Share on other sites

Thanks for your help dude. Trying this now, and will get back to you. :)

NOPE. Failed again.

how did you install clockwork? did you use paul's method that is pinned?

also wot is your stock build number.. is it still B05

Edited by tillaz
0

Share this post


Link to post
Share on other sites

how did you install clockwork? did you use paul's method that is pinned?

Yep. That's what I always do.

./adb reboot bootloader

./fastboot-linux flash recovery clockworkmod.img

./fastboot-linux reboot

All my files have correct permissions btw.

[EDIT]

Going back to TPT now, and will report build No. to you shortly. :)

[uPDATE AFTER TPT RECOVERY]

Right. Build is: OUK_P743T1.0.0B05

Edited by glossywhite
0

Share this post


Link to post
Share on other sites

Just noticed - the assert statement failed on the writing of the boot.img...

Please check the updater script, and verify that it is indeed writing the boot.img, errno 7 in standard unix denotes argument list too long, so it could be something there on the line in the updater script itself... B)

Edited by t0mm13b
0

Share this post


Link to post
Share on other sites

Try flashing a different rom

0

Share this post


Link to post
Share on other sites

Just noticed - the assert statement failed on the writing of the boot.img...

Please check the updater script, and verify that it is indeed writing the boot.img, errno 7 in standard unix denotes argument list too long, so it could be something there on the line in the updater script itself... B)

And in English? :P haha, thanks

0

Share this post


Link to post
Share on other sites

its possible clockwork has a problem ,reflash clockwork should do it.

0

Share this post


Link to post
Share on other sites

And in English? :P haha, thanks

Thought you said you're a "ubuntu hacker"... have not forgotten you btw when you first came on to the blade forum a while back!

Can whoever created the updater script within the ROM's check this?


assert(package_extract_file("boot.img", "/tmp/boot.img"), 

write_raw_image("/tmp/boot.img", "boot"), 

delete("/tmp/boot.img"));

ui_print("written boot.img");

A possibility that the /tmp partition is not mounted or there is not enough space on it to be able to successfully write the raw image to the boot partition thus the issue. B)

0

Share this post


Link to post
Share on other sites

Thought you said you're a "ubuntu hacker"... have not forgotten you btw when you first came on to the blade forum a while back!

Can whoever created the updater script within the ROM's check this?


assert(package_extract_file("boot.img", "/tmp/boot.img"), 

write_raw_image("/tmp/boot.img", "boot"), 

delete("/tmp/boot.img"));

ui_print("written boot.img");

A possibility that the /tmp partition is not mounted or there is not enough space on it to be able to successfully write the raw image to the boot partition thus the issue. B)

If you begrudge helping, and are just here to show off and gloat over forgotten squabbles, I'd rather not have your "help", as it evidently comes at a price which I am unwilling to pay.

Back to the topic: I tried installing tillaz' original BlueMonte, but it borks out when it comes to the writing to /tmp/boot.img

Edited by glossywhite
0

Share this post


Link to post
Share on other sites

what about another rom? and see if that works.

0

Share this post


Link to post
Share on other sites

what about another rom? and see if that works.

Done, but fails with same error.

its possible clockwork has a problem ,reflash clockwork should do it.

Done, multiple times, latest version.

0

Share this post


Link to post
Share on other sites

[puts tinfoil hat on] Maybe Orange has sent you an unflashable phone so you can't break another one biggrin.gif [takes tinfoil hat off]

Hope you manage to get sorted thoughsmile.gif

Edited by mike_
1

Share this post


Link to post
Share on other sites

[puts tinfoil hat on] Maybe Orange has sent you an unflashable phone so you can't break another one biggrin.gif [takes tinfoil hat off]

That had actually crossed my mind! HAHA!

Thank you. Sure I shall, these guys are clever.

Edited by glossywhite
0

Share this post


Link to post
Share on other sites

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

1

Share this post


Link to post
Share on other sites

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.

0

Share this post


Link to post
Share on other sites

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

You mean:



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


? :)

If so, done that.

0

Share this post


Link to post
Share on other sites

You mean:



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

[/code]

?

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

1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2016. MoDaCo uses IntelliTxt technology.