M
Warning! All your data will be lost.
It clears your data partition for security purposes
It clears your data partition for security purposes
are u guys able to access stock recovery? wht key combination?
Ta.... used your fastboot package as the one in my android dir kept saying waiting for device..
all done!!!
all done!!!
M
Mr_Bartek
Guest
I use Win7 x64 and tried on my Desire HD before uploading the .rar. The phone was detected successfully.
M
Mr_Bartek
Guest
Try 
. If step 9 doesn't work then try debranding with Customized FW from here: http://xdaforums.com/showthread.php?t=1033193
. If step 9 doesn't work then try debranding with Customized FW from here: http://xdaforums.com/showthread.php?t=1033193
Last edited:
yes my windows 7 64 bit having hard time. using my vista 32 bit works perfectly
Sent from my Xperia Arc
Try
Cant get past step 8, no go on the blue led so no fast boot. on orange branded piece of **** software lol
M
Mr_Bartek
Guest
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.
I'm not convinced of that but fair enough.
Personally, I'm having issues with the fastboot drivers for Win7 x64...
M
Mr_Bartek
Guest
I'm sure that's how it is . Too much hassle + service centres can change phone's customization rendering such methods useless.
Try these drivers and report back: http://www.multiupload.com/0XZV1LXRVA
. Too much hassle + service centres can change phone's customization rendering such methods useless.Try these drivers and report back: http://www.multiupload.com/0XZV1LXRVA
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:
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>
M
Mr_Bartek
Guest
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1128Warning! All your data will be lost.
It clears your data partition for security purposes33
