• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Delete

Search This thread

kyods

Senior Member
Mar 4, 2007
67
4
Is it just me, or does the USB driver refuse to work in Windows 7 64bit? It worked fine in 32bit, though.
 
  • Like
Reactions: hectorrai
M

Mr_Bartek

Guest
IMEIs are not registered for specific operators. Only part is the start which is used for SEUS detection. Branded devices will be able to receive their key, just won't be able to go into fastboot. I need someone to debrand their phone and check if fastboot is enabled after debranding.
 
  • Like
Reactions: Mooozer and Step666

Step666

Retired Forum Moderator
Jan 13, 2009
3,752
1,043
I can't quite bring myself believe that SE don't keep a record of which handsets are sold to whom and what network they're locked to.
Obviously, they're not cross-referencing against those records when issuing the unlocking keys but I'm sure they know.


Thank you for the drivers, I think they've done it...
Here's what it said on the command prompt:
Code:
C:\Users\[username]\Desktop\SE Unlock\fastboot>fastboot.exe -i 0x0fce getvar version

version: 0.3
finished. total time: 0.001s

C:\Users\[username]\Desktop\SE Unlock\fastboot>fastboot.exe -i 0x0fce oem unlock 0x[my key]
...
(bootloader) Unlock phone requested
(bootloader) Erasing block 0x00000d00
(bootloader) Erasing block 0x00000e00
(bootloader) Erasing block 0x00000f00
(bootloader) Erasing block 0x00001000
(bootloader) Erasing block 0x00001100
(bootloader) Erasing block 0x00001200
(bootloader) Erasing block 0x00001300
(bootloader) Erasing block 0x00001400
(bootloader) Erasing block 0x00001500
(bootloader) Erasing block 0x00001600
(bootloader) Erasing block 0x00001700
(bootloader) Erasing block 0x00001800
OKAY [  4.170s]
finished. total time: 4.170s

C:\Users\[username]\Desktop\SE Unlock\fastboot>
 
  • Like
Reactions: t_adams

Top Liked Posts