715 replies to this topic

[jikobutsu]

when i run flasher i get: Line1 wrong boot.mbn  ?

[arnoldziq]

@tilal6991
To enter FTM mode, in my case, you need to hold pressed 'volume down' button, not  the 'volume up'.
  

[tilal6991]

jikobutsu, on 11 November 2011 - 08:10 PM, said:

when i run flasher i get: Line1 wrong boot.mbn  ?

boot.mbn? Not boot.img?

[jikobutsu]

tilal6991, on 11 November 2011 - 08:11 PM, said:

boot.mbn? Not boot.img?

So how do I fix that ?

Edited by jikobutsu, 11 November 2011 - 08:14 PM.

[tilal6991]

jikobutsu, on 11 November 2011 - 08:13 PM, said:

So how do I fix that ?

2 secs - I'm uploading the fix now.

[D3abL3]

arnoldziq, on 11 November 2011 - 08:11 PM, said:

@tilal6991
To enter FTM mode, in my case, you need to hold pressed 'volume down' button, not  the 'volume up'.
  

It was a misspelling from Lalit's part.

[jikobutsu]

tilal6991, on 11 November 2011 - 08:15 PM, said:

2 secs - I'm uploading the fix now.

To be clear,it says wrong boot.mbn
It does not say boot.img

[D3abL3]

jikobutsu, on 11 November 2011 - 08:18 PM, said:

To be clear,it says wrong boot.mbn
It does not say boot.img

Go on files folder and rename it to "boot.img" and post the exact file size to see if it matches.

Correct one must have: 3.614.720 bytes / 3,44 MB / 3.530 KB

Edited by D3abL3, 11 November 2011 - 08:20 PM.

[jikobutsu]

in files, boot.img shows no file size ?

[tilal6991]

jikobutsu, on 11 November 2011 - 08:22 PM, said:

in files, boot.img shows no file size ?

Yep - I did that to reduce file size. It was intentional. I am uploading the fixed files now - 23%

[D3abL3]

I read someone's post asking if I used this(on this thread) method.

I didn't, I used the original method with original files from original sources. But this is the same deal, just the files were messed up.

[tillaz]

D3abL3, on 11 November 2011 - 08:26 PM, said:

I read someone's post asking if I used this(on this thread) method.

I didn't, I used the original method with original files from original sources. But this is the same deal, just the files were messed up.

wot android version did your phone ship with, 2.3.5 ???

[tillaz]

can anyone confirm that after unlocking there phone, this  *983*0#  no longer works ???

Edited by tillaz, 11 November 2011 - 08:34 PM.

[D3abL3]

tillaz, on 11 November 2011 - 08:33 PM, said:

wot android version did your phone ship with, 2.3.5 ???

Correction: It was 2.3.4. Why?

Now I'm sort of confused if it was 2.3.4 or 2.3.5.... Will you make me restore the backup of my shipped stock rom to confirm?

Edited by D3abL3, 11 November 2011 - 08:38 PM.

[tillaz]

D3abL3, on 11 November 2011 - 08:35 PM, said:

Correction: It was 2.3.4. Why?

just thought it might have something to do with  why you don't get that pop up..

[wrtease]

*983*0# no longer works can confirm.

[putbinoot]

Could not get into FTM mode but it looks like it should be volume down, should i be waiting for this new boot.img fix and i am on 2.3.4  with bluemonte rom does that make a difference.

[jikobutsu]

tilal6991, on 11 November 2011 - 08:23 PM, said:

Yep - I did that to reduce file size. It was intentional. I am uploading the fixed files now - 23%

where will you be uploading fix tilal ?

[tillaz]

D3abL3, on 11 November 2011 - 08:35 PM, said:

Correction: It was 2.3.4. Why?

Now I'm sort of confused if it was 2.3.4 or 2.3.5.... Will you make me restore the backup of my shipped stock rom to confirm?

i think it might of shipped on 2.3.5 if this has never worked for you *983*0#  
as it now seems to not work for shipped 2.3.4 users after doing the unlock that is based on 2.3.5 stuff

could be why your not getting that pop up...

Edited by tillaz, 11 November 2011 - 08:48 PM.

[jikobutsu]

tillaz, on 11 November 2011 - 08:47 PM, said:

i think it might of shipped on 2.3.5 if this has never worked for you *983*0#  
as it now seems to not work for shipped 2.3.4 users after doing the unlock that is based on 2.3.5 stuff

could be why your not getting that pop up...

will this mean we cannot calibrate ?