Bug 6307 – Flashing device on Windows 7 64-bit bricked device (Windows tries to install drivers)

Bug 6307 - Flashing device on Windows 7 64-bit bricked device (Windows tries to install drivers)


Summary:	Flashing device on Windows 7 64-bit bricked device (Windows tries to install ...

Status:	RESOLVED WORKSFORME

Product:	Flasher
Component:	Windows
Version:	5.0/(1.2009.42-11)
Platform:	N900 Windows

Importance:	Unspecified normal with 2 votes (vote)
Target Milestone:	---
Assigned To:	unassigned
QA Contact:	flasher-windows-bugs

URL:
Keywords:	moreinfo

Depends on:
Blocks:
	Show dependency tree

Reported:	2009-11-24 14:08 UTC by ossipena
Modified:	2010-06-23 15:55 UTC (History)
CC List:	3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description ossipena (reporter) 2009-11-24 14:08:21 UTC

SOFTWARE VERSION:
3.5

EXACT STEPS LEADING TO PROBLEM: 

1. start flasher
"flasher-3.5.exe -F image.bin -f -R"
2. plug a bricked device to usb port when asked to

EXPECTED OUTCOME:
The device is detected and reflashing is done automaticly.

ACTUAL OUTCOME:
Nothing happends, flasher stays in the state that asks to plug the device to
USB port.

REPRODUCIBILITY:
always

EXTRA SOFTWARE INSTALLED:
-

OTHER COMMENTS:
It is probably because windows wants to install its own drivers to the device
and fails because of the timeout of the connection. Apparently windows doesn't
tell to flasher that a device has connected before it has installed its own
drivers. With pen usb Ubuntu, flasher works perfectly. IMO this would only be
nice to have -fix to make life easier.

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; fi; rv:1.9.1.5)
Gecko/20091102 Firefox/3.5.5

Comment 1 Andre Klapper maemo.org

2009-11-24 16:25:49 UTC

So this is 
http://maemo.org/community/maemo-users/bricked_n900_under_24_hours/?org_openpsa_qbpager_net_nemein_discussion_posts_page=1#353312ead8f011dea41e1b7941439a039a03

Comment 2 Venomrush 2010-03-05 02:59:59 UTC

Can you define what a 'bricked device' is? ie does not boot up at all/no 4 dots
start up etc.

Did you follow the proper flash steps found at
http://wiki.maemo.org/Updating_the_firmware ? ie hold 'U' then plug in USB
cable

Comment 3 ossipena (reporter) 2010-03-05 08:01:51 UTC

(In reply to comment #2)
> Can you define what a 'bricked device' is? ie does not boot up at all/no 4 dots
> start up etc.
> 
> Did you follow the proper flash steps found at
> http://wiki.maemo.org/Updating_the_firmware ? ie hold 'U' then plug in USB
> cable
> 

Bricked device = https://bugs.maemo.org/show_bug.cgi?id=6350

Yes, I followed proper flash steps. Plus tried a lot of more variations. Added
an essential piece of information to title: the OS is 64 bit. I bet there is
already a bug for that.

Comment 4 Venomrush 2010-04-02 03:47:47 UTC

N900: Windows 64bit (Vista&7)
According to this
post(http://talk.maemo.org/showpost.php?p=411019&postcount=67), windows driver
signing can cause problems. You either need to turn on the loading of unsigned
drivers or boot your computer to whole another OS.

Option 1
Disabling signed driver detection is done by choosing the option "Boot without
checking for signed drivers" (or something similar) in the boot-menu. To
display the boot-menu press the "F8" key as soon as the windows boot process
starts. The rest of the process is similar to XP.

Option 2
Alternatively you can permanently disable driver checking via command line
manager. There are good instructions for windows 7 available [1]

Option 3
You can use [2] Microsoft Virtual Pc but when you connect your phone, press the
"usb" button and select your device.

Option 4
An alternative approach is to either download Ubuntu LiveCD and burn it to cd
or create a persistent installation to usb disk. After that you must get
(another) usb stick where you will download maemo_flasher-3.5_2.5.2.2_i386.deb
-file (versions may vary) and firmware files needed for reflashing.
Additionally one can save this page to usb stick just in case.

Comment 5 Andre Klapper maemo.org

2010-04-27 20:37:19 UTC

(In reply to comment #4)
> N900: Windows 64bit (Vista&7)
> According to this
> post(http://talk.maemo.org/showpost.php?p=411019&postcount=67), windows driver
> signing can cause problems. You either need to turn on the loading of unsigned
> drivers or boot your computer to whole another OS.

ossipena, did you try this and can you confirm that allowing unsigned drivers
fixes this?

Comment 6 ossipena (reporter) 2010-05-12 10:24:12 UTC

(In reply to comment #5)

> ossipena, did you try this and can you confirm that allowing unsigned drivers
> fixes this?
> 

If I remember correctly, I did try that once with no success. But I have time
to reflash in week 21 (first part of summer holiday) and I can report after
that what was the result.

Comment 7 ossipena (reporter) 2010-05-13 20:48:23 UTC

Just got time to test it out: no luck with driver signing off. Win7 says unable
to install drivers. 

xp-mode works well though. So my quess would be 64-bit drivers for the update
mode.

Comment 8 Andre Klapper maemo.org

2010-06-02 14:08:09 UTC

(In reply to comment #6)
> I have time to reflash in week 21

Looking forward to the result & keeping "moreinfo" for the time being.

Comment 9 ossipena (reporter) 2010-06-02 14:46:20 UTC

I was unable to reflash with win7 64bit with device signing off. Tried the
permanent command line way plus F8 at bootup -way with no luck.

and xp-mode is btw unable to reflash fw+eMMC because the connection is lost and
can't be found by flasher unless device is manually rebooted (by removing
battery)

but everything worked perfectly with xp sp3 32bit so I got my device finally
thorougly reflashed.