Related
Ok, here's the procedure for returning to stock S-ON after running revolutionary if required for warranty reasons.
Preparation
(Windows): Uninstall HTC Sync and any other sync software ( eg Androsync ) that you have been using.
(Windows) : Install these fastboot drivers
Get fastboot and adb tool for windows here
Get Fastboot and adb for linux here
Download the RUU for your device
Download the downgrade hboot for your device:
Flyer downgrade hboot MD5SUM=6f82c00e2029c4bf3cb00e861789e2f8
View downgrade hboot MD5SUM=d3462b3587564db133c2215127485fe4
Check the mdsum of your download
Check the mdsum of your download
Reboot to to fastboot mode
Flash the downgrade hboot
Flyer:
Code:
fastboot flash hboot flyer_downgrader.nb0
View:
Code:
fastboot flash hboot express_downgrader.nb0
Run the RUU for your device
I can't use adb on recovery mode. Can you upload your fastboot driver?
buidung said:
I can't use adb on recovery mode. Can you upload your fastboot driver?
Click to expand...
Click to collapse
1. Yes, you can use adb in recovery mode if you followed the instructions correctly.
2. Done
an system's update
...can be installed if i use this procedure?
I get an error
C:\Users\Namit>fastboot flash zip RUU_Flyer_BrightstarUS_WWE_2.27.1540.31_R_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204116_signed.zip
sending 'zip' (500195 KB)...
OKAY [ 77.287s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: not allowed)
finished. total time: 157.279s
Click to expand...
Click to collapse
EDIT1: Just moved the zip to sdcard as PG41IMG and went into bootloader. It is working right now; will report on results.
EDIT2: Worked! Flashed Radio and rebooted to finish the rest of the installation.
what is the name of hbbot image file in the "rom.zip"? is that "boot_signed.img"?
chong5379 said:
what is the name of hbbot image file in the "rom.zip"? is that "boot_signed.img"?
Click to expand...
Click to collapse
It is something like hboot_xxxxx.nb0
I try to flash the stock recovery by fastboot on my Htc View but not success. It shows "failed, signature .... Bla bla". My device is still s-on and hangs at htc screen. Hmm, I think its recovery partition was damaged and RUU can't overwrite another recovery.img on it. Can someone help me out ? Thanks
Namit1994 said:
It is something like hboot_xxxxx.nb0
Click to expand...
Click to collapse
*.nb0? isnt that should be *.img? im still confusing about this, i tried to use the "boot_signed.img", bootloader dead now, cannot turn on at all, the power light is blinking
Hello there,
I'm really desperate as I have this problem and I hope someone could help me, I'd be really grateful.
My following problem is :
I have an HTC FLYER and I tried to flash a new hboot FROM HERE ( http://forum.xda-developers.com/showpost.php?p=17481836&postcount=2 ) but mistakenly it was from another device, now my FLYER wont turn on at all.
Can someone help me how to flash a new hboot so my device can finally power up ? Please I really need my HTC FLYER to start working.
I tried running ADB and "adb devices" but my device serial doesn't how in the list of attached devices and i don't know neither how to flash the new hboot through adb.
Please I'm really desperate, I hope someone can help me . I'm really afraid my Htc Flyer is dead.
I'm afraid you worry is valid, if you flash an incorrect hboot and it won't boot then the only recovery is to send it for repair. The best option you have is to say that this happened as a result of the HC upgrade OTA.
hm
globatron said:
I'm afraid you worry is valid, if you flash an incorrect hboot and it won't boot then the only recovery is to send it for repair. The best option you have is to say that this happened as a result of the HC upgrade OTA.
Click to expand...
Click to collapse
yes but its bought in sweden and now i live in balkans so no warranty for me and i was thinking if i can fix it with some box method like jtag jig?
I motion that this thread either be stickied or combined with the S-OFF sticky thread.
hboot_1.11.0003.nb0
chong5379 said:
*.nb0? isnt that should be *.img? im still confusing about this, i tried to use the "boot_signed.img", bootloader dead now, cannot turn on at all, the power light is blinking
Click to expand...
Click to collapse
It was hboot_1.11.0003.nb0 in my case.
It can be either, mostly it will be .nb0 but it can be a .img. The important thing is that it is hboot not boot.
Where i can find RUU for my 3g flyer.
Now I use Leedroid rom i want to go back to official 2.3 to wail for official 3.2.
When or where?
Sent from my HTC Flyer P510e using xda premium
Where is can download RUU for my 3g flyer
^_^
I will correct my post
Thz
hi,
I updated to honeycomb using your method, but my tablet is now slower so I wanted to revert back to gingerbread.
The problem is I can't use ADB commands with it. It responds to fastboot commands but doesn't respond to adb commands. It shows: Error: device not found.
I have tried to put the rom.zip in the sd card, which seems to install gingerbread back, but it won't boot.
What can I do? I am desperate now.
Reflash honeycomb before you run out of battery
Hi!
Yesterday i managed my Flyer to S-off via revolutionary tool.
Today i wanted to update to Honeycomb with this tutorial:
+
Google search: android.modaco.com Installing Honeycomb on your Flyer
Guide from Paul.
i got now stuck after the htcdev bootloader unlock.
i should transfer the cwm recovery file via fastboot into the flyer
command: fastboot flash recovery revolutionary-cwm-4.0.1.4-flyer.newhboot.img
Code:
< waiting for device >
sending 'recovery' (4682 KB)...
OKAY [ 0.753s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.198s
Why this is failed? i tried to do the next step, getting into clockworkmod recovery but nothing happens.
My Flyer shows now:
Code:
*** RELOCKED ***
*** Security Warning ***
FLYER PUT SHIP S-ON RL
HBOOT-1.11.0006
MICROP-0950
RADIO-3821.08.00.26_M
eMMC-boot
Aug 29 2011, 13:32:02
Fastboot 9v AC (because charging)
VOL UP
VOL DOWN
POWER
Bootloader
reboot
reboot bootloader
power down
What can i do now? any idea?
edit: adb don't work, fastboot works.
I'm going crazy tried to reunlock bootloader via htcdev. When i flash the unlock token i get same error
Code:
C:\Users\h0f1\Desktop\htc\android-sdk_r15-windows\android-sdk-windows\platform-t
ools>fastboot flash untlocktoken Unlock_code.bin
sending 'untlocktoken' (0 KB)...
OKAY [ 0.015s]
writing 'untlocktoken'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.019s
Why in the world would you use the htcdev unlock? Go to flyer development and follow globatron's honeycomb guide. Much better than voiding your warranty.
Sent from my PG86100 using Tapatalk
i did yesterday exactly those steps from globatron for soff and cw recovery.
For getting Honeycomb i used another guide yesterday.. because i found this site today..
I really dont know what to do now
Worst case run ruu of your stock software
Sent from my HTC Flyer P510e using xda premium
somehow it doesnt work
C:\Users\h0f1\Desktop\htc\android-sdk_r15-windows\android-sdk-windows\platform-t
ools>fastboot flash untlocktoken Unlock_code.bin
sending 'untlocktoken' (0 KB)...
OKAY [ 0.013s]
writing 'untlocktoken'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.017s
edit:
made it now with other version of fastboot... this is crazy..
so i unlocked again and now i can go on with the other steps?!
I would return to stock then use globatrons update method. Do you know your stock ruu
Sent from my HTC Flyer P510e using xda premium
is going back to stock via ruu possible when i changed hboot, radio and boot file?
the guide from paul says:
Do NOT under any circumstances run the RUU in it’s entirety nor ‘fastboot flash rom.zip’ – this will make irreversible changes that you don’t want!
Be careful if you flash any RUUs or do anything that could revert you to S-ON on a broken system – this could leave you stuck
i think i will recharge and go through the last 4 points..
im afraid
Try to get a new unlock token.
I can not see why running your ruu to stock.would be an issue but I am not 100% certain. I did a revert last week and the only thing I needed to do prior was relock hboot first which you are already locked.
Sent from my HTC Flyer P510e using xda premium
first i wanna say thanks for your help!
i did today the last two steps after recharging the battery.
last 2 steps are putting the new image onto sdcard via adb and second step was factory reset und dalvik wipe. All two steps worked fine for me, but after restart the flyer is going to a bootloop.
what should i do now?
Should i get back with the RUU?
Can i setup honeycomb after getting back with ruu with the tutorial from globatron?
best regards
tom
did you flash the zip through recovery
Sent from my HTC Flyer P510e using xda premium
^the tutorial say get into clockwork recovery mode and type into command "adb shell mount /sdcard && adb push stock-hc-flyer-system.zip /sdcard/"
this command finished after 3 minutes and i was also lookin at the sd card the file is on the sd card.. after this i wiped dalvik and made a factory reset in the clockwork recovery mode. Afterwards Reboot -> then bootloop
lool is it possible that i have to " install zip from sdcard" ? if yes i'm the dumbest flyer user on the world *g*
edit: i tried now to install the update via recovery, it says E: Can't open /sdcard/stock-hc-flyer-system.zip (bad)
h0f1 said:
lool is it possible that i have to " install zip from sdcard" ? if yes i'm the dumbest flyer user on the world *g*
edit: i tried now to install the update via recovery, it says E: Can't open /sdcard/stock-hc-flyer-system.zip (bad)
Click to expand...
Click to collapse
Re-download, it's corrupt.
ikingblack said:
Re-download, it's corrupt.
Click to expand...
Click to collapse
+1
Sent from my HTC Flyer P510e using xda premium
really i promise i will neveer ever never try to flash/hack/root anything. its just horrible thinking all the time you brick it or anything else xD
i tried to reboot bootloader via adb in the recovery mode, flyer turned off and now nothing happens. cant go into bootloader or something else.. trying to recharge again, maybe battery is low again (i hope..)
well i will go on tomorrow evening.
great work guys anyways, thanks
tom
h0f1 said:
really i promise i will neveer ever never try to flash/hack/root anything. its just horrible thinking all the time you brick it or anything else xD
i tried to reboot bootloader via adb in the recovery mode, flyer turned off and now nothing happens. cant go into bootloader or something else.. trying to recharge again, maybe battery is low again (i hope..)
well i will go on tomorrow evening.
great work guys anyways, thanks
tom
Click to expand...
Click to collapse
I don't know if it's possible to really stop it from booting or displaying anything on the screen. Recharge and once it's done hold power button for a long time.
Good Luck
help fully bricked htc flyer p510e
here is what i did step by step:
bought an htc flyer, then upgraded it officially to honeycomb
i did not like honeycomb so i unlocked bootloader with htc dev method
then flashed recovery and rooted....
changed the misc_version and downgrade back to gingerbread with fastboot flash zip rom.zip
it worked........gta 3 and gta vice city worked.......few months later the gta 3 and vice city started crashing( just like honeycomb)
so i got s-off with revolutionary.....and flashed honeycomb PG41IMG.zip
that worked...........few months later i wanted gta back so i could not take i tried flash back down but did not work...it would get stuck in RUU mode ...so i flashed PG41IMG.zip back and that worked ..i was not bricked...so i tried another method
i flashed fastboot express downgrader.nb0 and
flyer downgrader.nb0
then changed gingerbread rom.zip to PG41IMG.zip and placed it on sd card
went into bootloader and let it flash
the bootloader at this moment:
***security warning***
pvt chip s-on
hboot 1.10.000
..................
it does not show whether the bootloader is locked or unlocked......no recovery.......tablet does not boot.....only to bootloader and fastboot.....
i tried to flash the unlock token for bootloader but get
signature failed error....
i tried to flash the honeycomb PG41IMG.zip but get
checking header failed
remote[signature failed]
cant flash anything because of that ...cant flash recover to even turn off the verification signature check.....
plz help ...whether you help me to fix it back to gb or hc to dont care ..just want it to work
plz help me fast
battery charges but phone goes into fastboot .....
plz help
just ask if u need more information on the situation..
plz anyone
Should probably find a good RUU that is compatible, create a gold card and do a clean re-load of compatible ROM.
[Solved!] Thanks.
So on step 12 of the website it says to type the below:
C:\>fastboot flash unlocktoken C:\Unlock_code.bin
I do so and I get the correct output that the site displays.
Which is:
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' <0 KB>...
OKAY [0.151s]
writing 'unlocktoken' ...
<bootloader> unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.158s
Step 13 reads:
"On your phone you will now see the disclaimer. Please read this carefully as this action may void your warranty"
However, I see no disclaimer appear on my phone. It stays on the fastloader hboot screen.
What's going on? Do I have to be not in the recovery fastloader screen and do that command when the normal os is showing? Or what?
Thanks if you can help.
Locate and flash the latest stock Ruu (or current one installed) from football or Mr.esp's thread to clear the issue. You should id your current Rom/radio version in android settings (about phone ) first... Ie. 2.08.651.3 vs 2.17.651.5 and phone codename is "shooter" not shooteru .
http://forum.xda-developers.com/showthread.php?p=19089387
Then retry the unlock & it should work. Check development sticky thread.for link & instructions. If you look at jtniggles hboot unlock/flash thread it will mention this issue.
If your hboot 1.50 you may have issues with specific recoveries not loading. I'd recommend you grab Cwm touch 5.0.8.1 and a more current Su 3.0 file to flash. I have some examples of flashing these & other stuff after unlocking in my recovery issues thread (see signature). Htcevohacks.com has a good how to video also.
Sent from my "Up all night, sleep all day" Evo3D via Tapatalk.
i tried this method myself but when i run the ruu it just sits at sending.... and never gets past it. please help!
Saw you posted a separate RUU question, so hopefully you'll get a response there, but just to try and help a bit...
There is an RUU .exe Instructions Doc in the Sticky Thread that may help you.
Edit: its 1/2 way down my useful thread links post (in my signature).
- you should indicate in your questions what your phone setup is so people can better help you: Hboot version, Firmware/Radio version, HTC Unlocked/Locked/not rooted, S-ON vs S-Off, Custom Recovery you use, filenames/thread links you're using, etc if they apply to your situation.
did you enable "usb Debugging" under settings, applications?
Did you DL the RUU.exe or RUU PG86IMG.zip ?
What he said you need to run latest RUU I have walked a bunch of folks through that .... Worked everytime for them...
og92 said:
i tried this method myself but when i run the ruu it just sits at sending.... and never gets past it. please help!
Click to expand...
Click to collapse
Relock and then run RUU.
Sent in L*W*H
intrlude said:
Relock and then run RUU.
Sent in L*W*H
Click to expand...
Click to collapse
He sounds like he is tryin to root the first time and gets to the part were the phone splash screen is suppose to say do you wish to unlock bootloader....
Which he needs to just run the RUU and should be good to go..
Thanks a bunch guys! Flashing the latest RUU and redoing the process worked. However...how do you know the bootloader was unlocked afterall? I want to double check.
Edit: Sorry, just figured it out..just needed to do the reboot again and says unlocked on the top. Yay!
FYI, I added some RUU info to the other post:
Running stock RUU Reference info: http://forum.xda-developers.com/showpost.php?p=22190515&postcount=5
GamerC said:
So on step 12 of the website it says to type the below:
C:\>fastboot flash unlocktoken C:\Unlock_code.bin
I do so and I get the correct output that the site displays.
Which is:
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' <0 KB>...
OKAY [0.151s]
writing 'unlocktoken' ...
<bootloader> unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.158s
Step 13 reads:
"On your phone you will now see the disclaimer. Please read this carefully as this action may void your warranty"
However, I see no disclaimer appear on my phone. It stays on the fastloader hboot screen.
What's going on? Do I have to be not in the recovery fastloader screen and do that command when the normal os is showing? Or what?
Thanks if you can help.
Click to expand...
Click to collapse
The first suspect thing to me here is that file says that its 0 kb, try to download again that file but maybe disable the AV to avoid getting it corrupted or stripped.
Sent from my PG86100 using Tapatalk
I should start off by saying that XDA does not have a subforum for the EVO Design, and because i'm new here, I didn't know where else to go. If there's a more appropriate place to post about the Evo Design, please point me to it.
Now on the my problem at hand. I get stuck around Step 11 in the guide on how to unlock your bootloader on the HTCdev site. Whenever I type in the command in the prompt, fastboot flash unlocktoken Unlock_code.bin, It just sits there looking like this:
c:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
I had followed all previous steps right prefectly, but for whatever reason it just decides to stop working at that point.
I have searched around a bit, but not to many other people had that problem, so I couldn't get any good answers. Thanks in advance if you can figure it out.
I'm using windows Vista if that helps.
64_hit_combo said:
I should start off by saying that XDA does not have a subforum for the EVO Design, and because i'm new here, I didn't know where else to go. If there's a more appropriate place to post about the Evo Design, please point me to it.
Now on the my problem at hand. I get stuck around Step 11 in the guide on how to unlock your bootloader on the HTCdev site. Whenever I type in the command in the prompt, fastboot flash unlocktoken Unlock_code.bin, It just sits there looking like this:
c:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
I had followed all previous steps right prefectly, but for whatever reason it just decides to stop working at that point.
I have searched around a bit, but not to many other people had that problem, so I couldn't get any good answers. Thanks in advance if you can figure it out.
I'm using windows Vista if that helps.
Click to expand...
Click to collapse
Did you reboot the phone into the bootloader? Power off the phone. You may have to pop out the battery and put it back in. Hold down the volume - button and press power. In the menu, navigate to the entry that says FASTBOOT. Plug in your USB cable, and the heading should now say FASTBOOT USB. Now try sending the unlocktoken to the phone.
~co~
closeone said:
Did you reboot the phone into the bootloader? Power off the phone. You may have to pop out the battery and put it back in. Hold down the volume - button and press power. In the menu, navigate to the entry that says FASTBOOT. Plug in your USB cable, and the heading should now say FASTBOOT USB. Now try sending the unlocktoken to the phone.
~co~
Click to expand...
Click to collapse
Yeah, fastboot, that's exactly what i chose.
64_hit_combo said:
Yeah, fastboot, that's exactly what i chose.
Click to expand...
Click to collapse
redo the whole procedure and when you get the token youll see the numbers and letters are different... try flashing the new one to the partition PM me soon if you have any questions or problems....
I've tried redoing it, and tried it on a different computer, but it's still not working.
At the beginning did you typ fastboot get identifiertoken
Sent from my HTC EVO 3D X515m using xda premium
jslim38 said:
At the beginning did you typ fastboot get identifiertoken
Sent from my HTC EVO 3D X515m using xda premium
Click to expand...
Click to collapse
Yes, i did. And pasted the token into space provided to get the unlock token.
64_hit_combo said:
I should start off by saying that XDA does not have a subforum for the EVO Design, and because i'm new here, I didn't know where else to go. If there's a more appropriate place to post about the Evo Design, please point me to it.
Now on the my problem at hand. I get stuck around Step 11 in the guide on how to unlock your bootloader on the HTCdev site. Whenever I type in the command in the prompt, fastboot flash unlocktoken Unlock_code.bin, It just sits there looking like this:
c:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
I had followed all previous steps right prefectly, but for whatever reason it just decides to stop working at that point.
I have searched around a bit, but not to many other people had that problem, so I couldn't get any good answers. Thanks in advance if you can figure it out.
I'm using windows Vista if that helps.
Click to expand...
Click to collapse
Don't know if you have solved your problem or not but I was having the same issue and my problem was I wasn't using the usb cable that came with my phone. Hope this helps someone.
Is it recognized in fastboot.
Can you type fastboot reboot-bootloader and does it work?
If not, my guess is your phone drivers aren't installed for adb to communicate.
Sent from my HTC EVO 3D X515m using Tapatalk 2
re
hi, i have the same probleme
Do you have HTC sync installed on your computer? If so uninstall it. Sync will interfere with fastboot writing. I'm not sure if this helps but also check mark the USB debugging box in your settings before you boot your phone into fastboot.
nano3000 said:
hi, i have the same probleme
Click to expand...
Click to collapse
This is a known problem with the HTC unlock process and is resolved by flashing a current RUU.exe for your phone, then flashing the unlock token again.
ramjet73
Hello.
I just got a Desire S my friend gave me to unlock and root, and I'm having the same problem. I did everything step-by-step in the HTCdev guide, and it's also stuck at "sending 'unlocktoken' (0 KB)...". Fastboot does recognize my device and ADB pushing/pulling works.
S-ON HBoot-2.02.0002
Stock Desire S EU ICS RUU.
USB debugging is enabled, but I don't think those settings would affect fastboot/bootloader.
Same problem here. Been trying to unlock my friend's EVO Design 4G from Sprint and I get stuck at the exact same spot. Maybe it has something to do with the HBoot that got installed with the latest update. Mine is showing HBoot 1.30.0000. This is just a guess though.
problem solved
you must add one more file to the android folder then type in the command again. The file is: AdbWinUsbApi.dll. Htc dev does not say to add this but you must.
koolmanhayes said:
you must add one more file to the android folder then type in the command again. The file is: AdbWinUsbApi.dll. Htc dev does not say to add this but you must.
Click to expand...
Click to collapse
I looked that up and found that is only required if you are using the generic Microsoft WinUSB driver with ADB. The HTC USB drivers installed separately or as part of the HTC Sync application use a driver called androidusb.sys. As long as the HTC drivers are installed and operational that file shouldn't be necessary for the htcdev unlock, which is probably why they didn't include it in the requirements for step 5 of the unlock procedure.
Here's a more detailed explanation:
/** \brief Function prototype for InstantiateWinUsbInterface routine exported
from AdbWinUsbApi.dll
In order to provide backward compatibility with the systems that still run
legacy (custom) USB drivers, and have not installed WINUSB.DLL we need to
split functionality of our ADB API on Windows between two DLLs: AdbWinApi,
and AdbWinUsbApi. AdbWinApi is fully capable of working on top of the legacy
driver, but has no traces to WinUsb. AdbWinUsbApi is capable of working on
top of WinUsb API. We are forced to do this split, because we can have
dependency on WINUSB.DLL in the DLL that implements legacy API. The problem
is that customers may have a legacy driver that they don't want to upgrade
to WinUsb, so they may not have WINUSB.DLL installed on their machines, but
they still must be able to use ADB. So, the idea behind the split is as
such. When AdbWinApi.dll is loaded into a process, it will check WINUSB.DLL
installation (by checking existance of C:\Windows\System32\winusb.dll). If
WINUSB.DLL is installed, AdbWinApi will also load AdbWinUsbApi.dll (by
calling LoadLibrary), and will extract address of InstantiateWinUsbInterface
routine exported from AdbWinUsbApi.dll. Then this routine will be used to
instantiate AdbInterfaceObject instance on condition that it is confirmed
that USB driver underneath us is in deed WinUsb.
*/
Click to expand...
Click to collapse
ramjet73
I tried adding that extra file and it didn't work. I'm still stuck at the same screen as the original post. Ramjet73 you mentioned flashing a current RUU.exe, but is that possible with a locked bootloader? Did you have this exact problem previously? If so, where can I get a current RUU for the Sprint Design 4g?
Qoolcat said:
I tried adding that extra file and it didn't work. I'm still stuck at the same screen as the original post. Ramjet73 you mentioned flashing a current RUU.exe, but is that possible with a locked bootloader? Did you have this exact problem previously? If so, where can I get a current RUU for the Sprint Design 4g?
Click to expand...
Click to collapse
Flashing an RUU.exe from Windows requires a locked bootloader.
The Evo Design 4G (kingdom) RUU's are here.
I couldn't seem to find an ICS RUU for the Sprint version if it is different than the Boost version. Maybe someone else can help with that. If you can't find a Sprint ICS RUU you could flash the GB version, HTC unlock, then do the OTA upgrade to ICS.
I haven't experienced this problem myself when I unlocked two phones with the Sprint GB 2.17.651.5 build installed, but I had just flashed the RUU.exe before doing that. Several people have reported problems with the unlock if they updated via the OTA instead of the RUU.
ramjet73
64_hit_combo said:
I should start off by saying that XDA does not have a subforum for the EVO Design, and because i'm new here, I didn't know where else to go. If there's a more appropriate place to post about the Evo Design, please point me to it.
Now on the my problem at hand. I get stuck around Step 11 in the guide on how to unlock your bootloader on the HTCdev site. Whenever I type in the command in the prompt, fastboot flash unlocktoken Unlock_code.bin, It just sits there looking like this:
c:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
I had followed all previous steps right prefectly, but for whatever reason it just decides to stop working at that point.
I have searched around a bit, but not to many other people had that problem, so I couldn't get any good answers. Thanks in advance if you can figure it out.
I'm using windows Vista if that helps.
Click to expand...
Click to collapse
I ran into this problem when unlocking my EVO 4G LTE. It was caused by using an old version of the fastboot.exe
If you download the new one from the HTC website in step 5 or the unlock process, it will give you a different identifier token and the process should work smoothly from there.
I hope that helps.
current state: unrooted, s-on, relocked
I successfully unlocked my phone, installed TWRP and attempted to flash a new ROM. Some how I messed up by wiping out system file without backup, and I failed to flash a new ROM either.
So I flashed my phone with RUU latest version (hboot 1.19, radio 1.12.) Now on the bootloader screen it says RELOCKED on top.
When I tried to unlock (normal HTC Dev method) the terminal gave "unlock token checked successfully OKAY", and the unlock confirmation screen showed up normally.
But after rebooting, it turns out my phone is still "RELOCKED." Is there any reason why it doesn't work? And how to reunlock it successfully?
Did you submit the unlock token to htc website so that you can be given the unlock_code.bin file to flash?
---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------
Never mind I misread the post, try the relock command and unlocking again
Make sure the command is right
Fastboot flash unlocktoken Unlock_code.bin
om4 said:
Did you submit the unlock token to htc website so that you can be given the unlock_code.bin file to flash?
---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------
Never mind I misread the post, try the relock command and unlocking again
Make sure the command is right
Fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
Here is what happened in my terminal:
C:\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.011s]
finished. total time: 0.014s
C:\android-sdk\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.147s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.011s]
finished. total time: 0.164s
After that the green unlock confirmation screen showed up on the phone, I chose unlock, pressed power button, waited for it to reboot, then reboot again to see the bootloader. Still no avail (relocked).
Have you tried flashing twrp anyway?
Use the 2.2.2.0 release, the new 2.3 has some issues that need to be worked out. It may just flash over, and never know
om4 said:
Have you tried flashing twrp anyway?
Use the 2.2.2.0 release, the new 2.3 has some issues that need to be worked out. It may just flash over, and never know
Click to expand...
Click to collapse
Here's what I got:
C:\android-sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (7356 KB)...
OKAY [ 1.170s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.810s
(I used the img file in 2.2.2.0 twrp zip file. The name is recovery.img)
Does the failure message have something to do with being relocked?
Have you tried the PJ75IMG.zip for twrp. If you are s-off you should be able to install that and not worry about being unlocked.
Sent from my icrap 2 using Tapatalk HD
That shouldn't happen unless phone is still locked or software doesn't match
cruise350 said:
Have you tried the PJ75IMG.zip for twrp. If you are s-off you should be able to install that and not worry about being unlocked.
Click to expand...
Click to collapse
Opps sorry, I'm currently S-On.
om4 said:
That shouldn't happen unless phone is still locked or software doesn't match
Click to expand...
Click to collapse
When I tried to lock the phone again, it says my phone is already locked. But the problem is normal unlock method doesn't work with some reason.
I'm stumped, maybe ruu again?
om4 said:
I'm stumped, maybe ruu again?
Click to expand...
Click to collapse
Done ruu again, but still can't get unlocked.
Maybe it's worth mentioning that after select 'Yes' on the unlock bootloader screen (the green page), the phone didn't reboot. It just turned itself off with red LED charging.
chtat12 said:
Done ruu again, but still can't get unlocked.
Maybe it's worth mentioning that after select 'Yes' on the unlock bootloader screen (the green page), the phone didn't reboot. It just turned itself off with red LED charging.
Click to expand...
Click to collapse
Is there another way around (manual method) for unlocking? To me it looked like some thing after the green confirmation page just didn't work right.
I can't think of any reason it wouldn't work again, maybe someone else will see this and have a fix. Sorry
chtat12 said:
Is there another way around (manual method) for unlocking? To me it looked like some thing after the green confirmation page just didn't work right.
Click to expand...
Click to collapse
You could try downgrading to hboot 1.12 to get s-off...then it won't matter if you're unlocked or not. The process is still pretty new and not for the faint of heart (yet), but seems to be verified working. Check the downgrade sticky thread in the original dev forum for more details.
Sent from my EVO LTE
I would have mentioned it if closeone had a release ready but it's still a bit off. Better to wait then to have someone following directions to purposely brick their phones
premo15 said:
You could try downgrading to hboot 1.12 to get s-off...then it won't matter if you're unlocked or not. The process is still pretty new and not for the faint of heart (yet), but seems to be verified working. Check the downgrade sticky thread in the original dev forum for more details.
Sent from my EVO LTE
Click to expand...
Click to collapse
I believe downgrading method requires an unlocked phone, since it needs twrp for adb commands?
Yes it does, I didn't even remember that lol. I just didn't mention it because right now the overall process is rough
I think the unlock process modified the boot section, and looks like mine is a bit messed up. If so, would 'fastboot flash boot <bootfile>' work? (I don't know where to find it yet, just an another thought.)
chtat12 said:
I believe downgrading method requires an unlocked phone, since it needs twrp for adb commands?
Click to expand...
Click to collapse
Good point...
Sent from my EVO LTE
any resolution to this? i find myself in the same situation