I have followed all of the instructions to a T like 5 times to no avail. Can someone please tell me what I may be doing wrong?
Here is a copy of my command prompt:
C:\Users\Jerry>cd c:\.android
c:\.android>fastboot oem get_identifier_token
...
(bootloader)
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) 48888EEB9889D124D6C72F309EB940E2
(bootloader) 4CF40D0980840AF3DBB8CE4A486C056F
(bootloader) B42CE3D1056CAA6E3BE6884B5A28F120
(bootloader) C3B4E7E9173E3A55070B1A910E2497CD
(bootloader) A10C7FCE2ECE00C595C9DEE4B4D2A0C9
(bootloader) 219FF2E5D0C5019BDD3CA2EE7E28D44B
(bootloader) 875A72786356791FD909F85FE585D75C
(bootloader) 066E93AB9754291B9EC07CF026967276
(bootloader) EFA05F5E63FD78921D794C18CB1FBE22
(bootloader) AA76C231B26418110079C337E1CBA85C
(bootloader) 32549FCB5270D515775DF1DB9EB7C42D
(bootloader) A835495897A09826555C5147F5A7DC51
(bootloader) 059061DBC08128A32501EA28C1C0736F
(bootloader) 1F55865A90703A538D44517E85259D43
(bootloader) D17D85912695F9E8A3F24E3AF917B299
(bootloader) 4DEF2BBCBAB92B36D0D778673321E5CB
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [ 0.070s]
finished. total time: 0.070s
c:\.android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.151s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.007s]
finished. total time: 0.159s
c:\.android>
See the guide/flashing notes in my signature. It'll straighten you out. Stuck at step 13right?
Redownload the bin file, if you noticed it cought it being 0kb of size.
Also ensure that the phone is seen correctly under windows.
Sent from my PG86100 using Tapatalk
That happened to me the bootloader unlock option did not want to come .. i am sure your number software ends with 3 . Or higher what i did i ran the 2.17.651.2 ruu shotter and after that i had no problems . If you run the ruu.shotter you will lose all your data.
Sent from my HTC.EVO.3D.Xda Premium
Amy luck
Sent from my HTC.EVO.3D.Xda Premium
Any luck?
Sent from my HTC.EVO.3D.Xda Premium
darkstar765 said:
I have followed all of the instructions to a T like 5 times to no avail. Can someone please tell me what I may be doing wrong?
Here is a copy of my command prompt:
C:\Users\Jerry>cd c:\.android
c:\.android>fastboot oem get_identifier_token
...
(bootloader)
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) 48888EEB9889D124D6C72F309EB940E2
(bootloader) 4CF40D0980840AF3DBB8CE4A486C056F
(bootloader) B42CE3D1056CAA6E3BE6884B5A28F120
(bootloader) C3B4E7E9173E3A55070B1A910E2497CD
(bootloader) A10C7FCE2ECE00C595C9DEE4B4D2A0C9
(bootloader) 219FF2E5D0C5019BDD3CA2EE7E28D44B
(bootloader) 875A72786356791FD909F85FE585D75C
(bootloader) 066E93AB9754291B9EC07CF026967276
(bootloader) EFA05F5E63FD78921D794C18CB1FBE22
(bootloader) AA76C231B26418110079C337E1CBA85C
(bootloader) 32549FCB5270D515775DF1DB9EB7C42D
(bootloader) A835495897A09826555C5147F5A7DC51
(bootloader) 059061DBC08128A32501EA28C1C0736F
(bootloader) 1F55865A90703A538D44517E85259D43
(bootloader) D17D85912695F9E8A3F24E3AF917B299
(bootloader) 4DEF2BBCBAB92B36D0D778673321E5CB
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [ 0.070s]
finished. total time: 0.070s
c:\.android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.151s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.007s]
finished. total time: 0.159s
c:\.android>
Click to expand...
Click to collapse
Download and run The 2.08 RUU Then Use the htc Unlock I had the same problem today this works
Hello all,
I've read many forum posts and have had no luck with my current situation, so I made an account and am reaching out to the community for assistance. I had bought a phone off ebay that I used for many months that was S-ON but unlocked--I ran many ROMS that worked on S-ON just fine. However, I've recently decided I'd like to work on an S-off ROM. I went all the way back to stock RUU using the main guide here on XDA (though, my bootloader still said it was "tampered" and "relocked" FWIW). I went back to stock, and took both OTAs to get to 2.06. I tried both the revone.dna (-1 and -2 errors) and moonshine (don't drink and shine after 10 "moonshining" attempts). Does anyone have any advice as to what I need to do to get unlocked again, become S-off, and then allow me to go forward with my own recovery and ROM of choice? I appreciate any help.
Thanks,
Andy
albernhagen said:
Hello all,
I've read many forum posts and have had no luck with my current situation, so I made an account and am reaching out to the community for assistance. I had bought a phone off ebay that I used for many months that was S-ON but unlocked--I ran many ROMS that worked on S-ON just fine. However, I've recently decided I'd like to work on an S-off ROM. I went all the way back to stock RUU using the main guide here on XDA (though, my bootloader still said it was "tampered" and "relocked" FWIW). I went back to stock, and took both OTAs to get to 2.06. I tried both the revone.dna (-1 and -2 errors) and moonshine (don't drink and shine after 10 "moonshining" attempts). Does anyone have any advice as to what I need to do to get unlocked again, become S-off, and then allow me to go forward with my own recovery and ROM of choice? I appreciate any help.
Thanks,
Andy
Click to expand...
Click to collapse
I just got through doing this myself, and had the exact same problem. I successfully got S-Off even when using DigitalDream 2.2 ROM. Here's what I did.
Step 1: Go to this link (http://forum.xda-developers.com/showthread.php?t=2314771) and use the stuff at the very bottom of the first post where it says to download 2.06 firmware and to flash that first. If you can an error when flashing the firmware, don't worry about it. Just do the fastboot reboot-bootloader command then power off the phone completely and turn it back on (as the instructions say.
Step 2: I used the FacePalm method (http://forum.xda-developers.com/showthread.php?t=2155069). I only downloaded the boot.img and firmware. Follow the steps for the FacePalm method. That successfully got me S-Off.
Thanks
Thanks for your response, BoogaBooga. I tried this out, but it seems that I'm out of luck because I'm relocked as opposed to unlocked. Here's what I saw when attempting FacePalm:
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.043s]
finished. total time: 0.044s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot flash zip dna2.06firmware.zip
< waiting for device >
sending 'zip' (33119 KB)...
OKAY [ 2.411s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,11
(bootloader) [RUU]UZ,boot,25
(bootloader) [RUU]UZ,boot,38
(bootloader) [RUU]UZ,boot,52
(bootloader) [RUU]UZ,boot,66
(bootloader) [RUU]UZ,boot,79
(bootloader) [RUU]UZ,boot,90
(bootloader) [RUU]UZ,boot,100
(bootloader) [RUU]WP,boot,0
(bootloader) [RUU]WP,boot,99
(bootloader) [RUU]WP,boot,100
(bootloader) ...... Successful
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,51
(bootloader) [RUU]UZ,hboot,100
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,11
(bootloader) [RUU]UZ,recovery,22
(bootloader) [RUU]UZ,recovery,36
(bootloader) [RUU]UZ,recovery,48
(bootloader) [RUU]UZ,recovery,74
(bootloader) [RUU]UZ,recovery,86
(bootloader) [RUU]UZ,recovery,97
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,99
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,9
(bootloader) [RUU]UZ,radio,18
(bootloader) [RUU]UZ,radio,27
(bootloader) [RUU]UZ,radio,36
(bootloader) [RUU]UZ,radio,41
(bootloader) [RUU]UZ,radio,50
(bootloader) [RUU]UZ,radio,59
(bootloader) [RUU]UZ,radio,68
(bootloader) [RUU]UZ,radio,73
(bootloader) [RUU]UZ,radio,82
(bootloader) [RUU]UZ,radio,87
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,36
(bootloader) [RUU]WP,radio,73
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
OKAY [ 17.400s]
finished. total time: 19.810s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.036s]
finished. total time: 0.037s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.039s]
finished. total time: 0.040s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fasboot flash zip PL8320000-DNA.zip
'fasboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot flash zip PL8320000-DNA.zip
sending 'zip' (36905 KB)...
OKAY [ 2.680s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 8.814s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot flash zip PL8320000-DNA.zip
sending 'zip' (36905 KB)...
OKAY [ 2.680s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 8.815s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot boot DNA-rescue.img
downloading 'boot.img'...
OKAY [ 0.813s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.815s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>^A
BoogaBooga said:
I just got through doing this myself, and had the exact same problem. I successfully got S-Off even when using DigitalDream 2.2 ROM. Here's what I did.
Step 1: Go to this link (http://forum.xda-developers.com/showthread.php?t=2314771) and use the stuff at the very bottom of the first post where it says to download 2.06 firmware and to flash that first. If you can an error when flashing the firmware, don't worry about it. Just do the fastboot reboot-bootloader command then power off the phone completely and turn it back on (as the instructions say.
Step 2: I used the FacePalm method (http://forum.xda-developers.com/showthread.php?t=2155069). I only downloaded the boot.img and firmware. Follow the steps for the FacePalm method. That successfully got me S-Off.
Click to expand...
Click to collapse
After I updated to 2.06 (the stock way), I ended up reunlocking using the original unlock key I got from the HTCDEV site. Not exactly sure how you unlocked yours the first time, so I'm not sure if that will help you or not.
BoogaBooga said:
After I updated to 2.06 (the stock way), I ended up reunlocking using the original unlock key I got from the HTCDEV site. Not exactly sure how you unlocked yours the first time, so I'm not sure if that will help you or not.
Click to expand...
Click to collapse
Since I bought the phone already unlocked, I never had the old unlock key. I suppose I can contact the guy I bought it from and see if he still has it. Any other ideas in the meantime?
I'm really not sure. Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2109862
BoogaBooga said:
I'm really not sure. Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2109862
Click to expand...
Click to collapse
I received help from Beaups and got things working. It was a problem with my supercid. We did basically what happens in post #5 here:
http://forum.xda-developers.com/showthread.php?t=2407640
Thanks!
Hello Evo3d forum!
I've had a GSM 3D for over a year now, and love it. Decided to try rooting/flashing a little while ago, and unfortunately have gotten myself into a fix.
Here's a TL;DR of the problem:
Bootloader "relocked", SuperCID not working for RUU's, [previously working] HTCDev unlock token rejected by phone.
I have no idea why a SuperCID wouldn't work with an RUU (I thought the point was to be able to use any RUU?), or why my unlock token/code would stop working. I did a lot of searching, and it seems that a invalidated unlock token is a common problem for people who had their motherboards replaced, but this is not the case for me. My token file worked for me just a few hours ago, and there was no hardware-fiddling since that time at all. Did the RUU's do something to the bootloader?
I'm wondering if I've soft-bricked my 3D...
Full problem description:
On HBOOT 1.53.0007; S-ON
Unlocked successfully via HTCDev, flashed ICS Sense-based ROM successfully.
Decided to downgrade to 1.49.xxxx since many other ROMs seem to require it, and getting S-OFF would be easier with a 1.49 HBOOT.
Figured using a pre-ICS RUU should do the trick (in retrospect, this was probably a mistake).
Acquired apparent pre-ICS RUU (RUU_Shooter_U_hTC_Asia_TW_1.23.709.4_Radio_10.55.9020.00_10.13.9020.29_M_release_211198_signed.exe)
Relocked bootloader via "fastboot oem lock"; started RUU .exe.
RUU fails, returns "Error 131: Customer ID error"
SuperCID phone from HTC__044 to HTC__001 (second mistake - I forgot to unlock the bootloader before doing this)
Phone accepts new CID, retry RUU; still Error 131
Decide to screw it and just use an ICS RUU to reset phone, and pursue some other method of downgrading hboot
ICS RUU (previously worked multiple times) gives error 131
Attempt to reset CID from HTC__001 to HTC__044
CID writing appears to work, but phone reverts to HTC__001 after rebooting.
Figure bootloader lock is preventing CID writing, so attempt tp unlock via HTCDev token
Unlocking failed with "remote: unlock token check failed" error. Attempt multiple times; all fail.
Attempt to boot into recovery (TWRP), fails; RUU's appear to have wiped the partition (You'd think it'd check the CID before doing anything..)
Here's the commandline input/output for resetting CID. My input is in blue, relevant output is in red:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>[COLOR="blue"]fastboot oem readcid[/COLOR]
...
(bootloader) cid: [color="red"]HTC__001[/color]
OKAY [ 0.006s]
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>[color="blue"]fastboot getvar all[/color]
(bootloader) version: 0.5
(bootloader) version-bootloader: [color="red"]1.53.0007[/color]
(bootloader) version-baseband: 11.25.3504.06_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.707.1
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) product: [color="red"]shooter_u[/color]
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG8630000
(bootloader) cidnum: [color="red"]HTC__001[/color]
(bootloader) battery-status: good
(bootloader) battery-voltage: 5770mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 10e127f0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.492s
C:\Program Files (x86)\Minimal ADB and Fastboot>[color="blue"]fastboot oem writecid HTC__044[/color]
...
(bootloader) shooter_u_init_sd, SD card power on ok
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
(bootloader) Start Verify: 3
(bootloader) erase sector 65504 ~ 65535 (32)
OKAY [ 1.409s]
finished. total time: 1.410s
C:\Program Files (x86)\Minimal ADB and Fastboot>[color="blue"]fastboot oem readcid[/color]
...
(bootloader) cid: [color="red"]HTC__044[/color]
OKAY [ 0.005s]
finished. total time: 0.007s
C:\Program Files (x86)\Minimal ADB and Fastboot>[color="blue"]fastboot reboot-bootloader[/color]
rebooting into bootloader...
OKAY [ 0.202s]
finished. total time: 0.203s
C:\Program Files (x86)\Minimal ADB and Fastboot>[color="blue"]fastboot oem readcid[/color]
...
(bootloader) cid: [color="red"]HTC__001[/color]
OKAY [ 0.006s]
finished. total time: 0.007s
For unlocking the bootloader:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>[color="blue"]fastboot flash unlocktoken Unloc
k_code.bin[/color]
sending 'unlocktoken' (0 KB)...
OKAY [ 0.144s]
writing 'unlocktoken'...
[color="red"]FAILED (remote: unlock token check failed)[/color]
finished. total time: 0.156s
Phew! I've managed to find a solution.
The answer to this conundrum was to obtain, and use another unlock code from HTCDev. That unlocked the bootloader, and hallelujah, everything became flashable again (well, as much as can be an S-ON 1.5+ HBOOT -_-' ).
I really thought I was a goner, for a few hours, though.
I can only deduce that this problem was caused by the RUU's screwing with the bootloader, and somehow changing its unique ID; possibly due to the interruption caused by mismatching CID's. If this really is the case, then that's some ridiculously bad exception handling by the RUU program.
So yes, if you come across this problem, the solution is to head to htcdev.com and follow the instructions to unlock the bootloader again (submit identifier code > receive unlock_code.bin > flash token to phone via fastboot). Then reflash recovery and ROM.
Hope this helps someone!
Hi all! First at all sorry for my bad english.
Now I have problem with my evo which can be solved only by warranty. But the phone is ruted and ect., I try to go to stock, but I have problems with changing CID. The phone is locked at the moment but I can unlock it. Here same info:
Locked
S-OFF
HBOOT- 1.49.0007
Radio-11.25.3504.06_M
I try to change CID with this command
Code:
fastboot oem writecid HTC_032
After that I check CID with this
Code:
C:\Android>fastboot oem readcid
...
(bootloader) cid: HTC__032
OKAY [ 0.005s]
finished. total time: 0.006s
It's ok, but I can't flash RUU. It says error which mean wrong CID. After that I check cid again, but this time
Code:
C:\Android>fastboot getvar cid
cid: 0202
finished. total time: 0.002s
I unlock phone and I try all again and again, but cid can't be chamged and RUU can't be instal.
Оtherwise
"fastboot oem writecid" work only if I check with "fastboot oem redcid", it does not work when check with "fastboot getvar cid" and "fastboot getvar all". I try with different CIDs which are for my region, but every time the same problem.
10x for helping me.
Hello
Im the same problem, post install CM11-KK4.4.2 in my htc evo 3d gsm, show me cid 0202, how to change to correct cid HTC__032 ?
Locked
S-OFF
HBOOT- 1.49.0007
Radio-11.25.3504.06_M
Code:
C:\ADB\adb>fastboot oem writecid HTC__032
...
(bootloader) Start Verify: 0
(bootloader) erase sector 65504 ~ 65535 (32)
OKAY [ 0.172s]
finished. total time: 0.172s
fastboot gedvar all show me this:
Code:
C:\ADB\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.49.0007
(bootloader) version-baseband: 11.25.3504.06_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.20.401.2
(bootloader) serialno: HT23TV201098
(bootloader) imei: 352647050841305
(bootloader) product: shooter_u
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG8630000
(bootloader) cidnum: 0202
(bootloader) battery-status: good
(bootloader) battery-voltage: 5527mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: edba812f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.484s
I have no ideas
I greet
[email protected]
Try the super CID: fastboot oem writecid HTC_11111111
Sent from my Evo 3D GSM using XDA Premium 4 mobile app
Anonymuszymus said:
Try the super CID: fastboot oem writecid HTC_11111111
Sent from my Evo 3D GSM using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Code:
C:\ADB>fastboot oem writecid HTC_11111111
...
(bootloader) fail: [writecid] Illegal cid size
OKAY [ 0.016s]
finished. total time: 0.016s
Code:
C:\ADB>fastboot oem writecid HTC__032
...
(bootloader) Start Verify: 0
(bootloader) erase sector 65504 ~ 65535 (32)
OKAY [ 0.016s]
finished. total time: 0.016s
C:\ADB>fastboot oem readcid
...
(bootloader) cid: HTC__032
OKAY [ 0.016s]
finished. total time: 0.016s
C:\ADB>fastboot getvar cid
cid: 0202
finished. total time: 0.000s
Hi
Why getvar show me 0202 cid and readcid show me HTC__032 ?
I greet
Same here:crying::crying:
Try "fastboot oem writecid 11111111" (8 times 1)
After that reboot on fasboot again and check. If you have unlocked bootloader you must lock it before running the ruu. "fastboot oem lock" is the command.
Sent from my Evo 3D GSM using xda app-developers app
mhnx said:
Try "fastboot oem writecid 11111111" (8 times 1)
After that reboot on fasboot again and check. If you have unlocked bootloader you must lock it before running the ruu. "fastboot oem lock" is the command.
Sent from my Evo 3D GSM using xda app-developers app
Click to expand...
Click to collapse
I tried again and again... but nothing everytimes I've cid 0202...:crying:
39854341
mhnx said:
Try "fastboot oem writecid 11111111" (8 times 1)
After that reboot on fasboot again and check. If you have unlocked bootloader you must lock it before running the ruu. "fastboot oem lock" is the command.
Sent from my Evo 3D GSM using xda app-developers app
Click to expand...
Click to collapse
thx man