Jump to content

Problems with bootloader Rom and 32Mbyte MM Card


Guest stidy

Recommended Posts

Hi,

I have a dead SAP after upgrading to the latest Smart S/W, loosing the unlock status, attempting to downgrade and now the phone will only boot into the Canary Mode.

I have all of the equipment I think to write a Rom onto the MultiMedia Card (writer, PC, WinHex, 3 different Roms (0.91, .93 and .98) but here's my problem.

When I try and write the backup file "directly and immediately to the disk" in WinHex I get two different errors depending on if I use the Logical drive to my USB2 MMC drive or the physical drive:

Logical drive error:

"Supplied user buffer is not valid for the requested operation"

Physical drive error:

"Invalid access to memory location"

Is this something to do with the size of the MM card (32Mbytes) being different from that of the backup WinHex file ?

If so, is it possible for somebody to supply a Winhex backup of a pre "version 1" Rom from such a card as I have no access to a smaller (or larger) card at the moment.

If not, then what am I doing wrong ? I have hunted through google but found no mention of such an error and/or it's solution.

?

Help !

:cry:

Link to comment
Share on other sites

More details of setup would perhaps be useful:

Win XP Pro (logged on as administrator)

Lexar Multi-Card reader

WinHex 11.15 Full version

Unnamed 32Mbyte MMC card (which actually came with a Nokia 6600) - works fine within Windows and is seen as a drive and I can write to it, etc.

Link to comment
Share on other sites

this is wierd, i suggest speaking to the winhex team, as they may be able to help you?

are you just cloning in winhex for me this is the most effective way, and it does not seem to care about the size of the card.. (as long as it is big enough).. i always get physical and logical the wrong way round, so off the top of my head i cannot remember which is correct. - sorry .

PM me and i'll help if i can

Whar bootloader are you downgrading from? many are locked from accepting cards loaded with bootloaders.

Link to comment
Share on other sites

Guest Shuflie

Try using clone disk (ctrl+d). Use the backupfile as the source and your SD logical drive as the destination. You will also need to set the start sector to 0. It might also be an idea to have a image taken from the same sized SD or MMC.

Link to comment
Share on other sites

I'll give that a go on Monday.

BTW, the guys at WinHex said that it had nothing to do with the diferent size of the SD disk and the Backup image - More of a driver or hardware problem they thought. Trouble is just how many different card readers/writers do I use before I find the right one. I'm using XP pro so I can't do too much about the driver situation.

Also, I purchased a new SD card (128Mb) - still get the same error messages....

Will is trying to work around this another way (with other people) so hopefully I will not have to go this route - there is some doubt as to if it will help anyway (the Bootloader downgrade). "Smart" seem to have done a nice job of preventing downgrades and hence unlocking once you go to 1.7 of thier software.

As I said, I'll try the cntrl-d method on Monday when back at work and have access to all my "stuff".

Thanks for the input - I'll report back with the results.

Link to comment
Share on other sites

Guest Shuflie

You could try the method that was used when trying to recover from a leaked danish 1.6 rom. Run the 1.7 upgrade again but when it get to the press here to upgrade now section(or whatever it is with SAP upgrades) after the rom checking has taken place, then replace the NBF file with one from an earlier ROM image. I can't remember the exact details but if you search the forum you should be able to find the post which explains it all.

Link to comment
Share on other sites

  • 2 months later...

Simplest way is to either re-run the update (with the phone in the 3 color screen). or find a newer update for your phone, and try that (again in 3 color mode).

Messing with cards,winhex and bootloaders should not be needed if the update just failed.

Will

Link to comment
Share on other sites

Guest stidy

Hi,

well as I said I did try that under Will's supervision but it didn't work.

I was in contact with Will and he was trying to sort the problem out another way but that was several months ago and I haven't heard anything from him since Christmas..................

:)

Will - Did you ever have any luck ?

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.