Related
Hey Guys,
I have been waiting for this day, and now that its here, I'm stuck. I did everything the HTCDev instructions said, got my Unlock.bin but when I go to flash it, it hangs at:
C:\>fastboot flash unlocktoken C:\Unlock_code.bin
sending 'unlocktoken' (0 KB)...
I have searched everywhere for a solution and have tried everything, I now have a phone thats empty and has the latest RUU. I have tried every port on my laptop and my desktop, nothing works. Can anyone help me with this? Should I contact VZW and try and get a replacement? I'm pulling my hair out trying to get this to work.
Thanks
Wouldn't the command be?
Code:
fastboot flash unlock_code.bin
You need to type the filename exactly as it appears or it will not work.
nope, I followed the directions on the HTC site, and they are the same as all the posted guides. It has to be my token, is it possible I have a bad token or phone? Should I contact HTC to see if they will replace it?
You have to put the unlock_code.bin in the same folder as the ADB and fastboot executables.
Then you can leave out the path in the command. You don't need to use the full path, just
Code:
fastboot flash unlocktoken Unlock_code.bin
EDIT: Clearly you didn't follow the instructions by the way, otherwise you would have created an Android folder on your C:\ drive and would have known to put all the files in that directory. No worries, just do as I said and you should be good
It is in the same folder as it, I have tried it in the platfor-tools folder, in its own folder at C:\android and i have tried it on the root of c:\. I just tried it on a 3rd computer i have and same deal. It has to be my token.
icy1899 said:
It is in the same folder as it, I have tried it in the platfor-tools folder, in its own folder at C:\android and i have tried it on the root of c:\. I just tried it on a 3rd computer i have and same deal. It has to be my token.
Click to expand...
Click to collapse
Interesting. USB Debug enabled? Charge only mode?
icy1899 said:
It is in the same folder as it, I have tried it in the platfor-tools folder, in its own folder at C:\android and i have tried it on the root of c:\. I just tried it on a 3rd computer i have and same deal. It has to be my token.
Click to expand...
Click to collapse
I don't know but to be honest I just cannot see how it could be the token.
BTW...the .bin file needs to be in the same folder/location as the fastboot.exe file which would be under the "Tools" folder not the "Platform-tools".
I was in fastboot mode in the "recovery" screen. I will boot up and try running it then.
EDIT: Still no dice. This is killing me.....
I hate to tell you, but it's on your end. Other people would be posting with the same issue if it were HTC Dev's issue.
Anyway, all I can say is follow the instructions EXACTLY and start from step one.
icy1899 said:
Hey Guys,
I have been waiting for this day, and now that its here, I'm stuck. I did everything the HTCDev instructions said, got my Unlock.bin but when I go to flash it, it hangs at:
C:\>fastboot flash unlocktoken C:\Unlock_code.bin
sending 'unlocktoken' (0 KB)...
I have searched everywhere for a solution and have tried everything, I now have a phone thats empty and has the latest RUU. I have tried every port on my laptop and my desktop, nothing works. Can anyone help me with this? Should I contact VZW and try and get a replacement? I'm pulling my hair out trying to get this to work.
Thanks
Click to expand...
Click to collapse
This is how/why bootloaders get locked...
Your best bet is to post step by step what you've done so we can figure out what you're not doing right.
Sent from my newly unlocked Rezound.. Thank you HTC.
I have followed every step of every walkthru on this forum and others, as well as the HTCDev instructions. I have done it on all 3 computers (all Win7 Pro legit) trying every usb port with every method. I have also tried different USB cables. I have had my girlfriend watching my every keystroke to accuracy (she also has a rezound, but is waiting on a replacement device ,screen cracked). I have tried putting the files in:
C:\
C:\Android
C:\Program Files\Android\androidsdk\platform-tools\
D:\
S:\ a network drive (didnt expect this to work)
F:\ a flash drive
I just got off the phone with HTC support and they think it is strange as well, they escalated my issue so I should get a call from someone who actually knows what fastboot is.
I am going to try a LiveUSB copy of Ubuntu 11.10. I will let you know of any progress.
Why would vzw replace a phone you screwed up trying to root it.
Sent from my Galaxy Tab 10.1
jbh00jh said:
Why would vzw replace a phone you screwed up trying to root it.
Sent from my Galaxy Tab 10.1
Click to expand...
Click to collapse
I didn't screw it up trying to root. The phone works fine, the issue is that the HTC provided system will not work for my phone. Vzw should replace it only if HTC escalation team cant get to the bottom of it. They should replace it because there is a manufacturing error on the device.
Sent from my Kindle Fire using Tapatalk
The instruction page at htc/dev unlock says if you use the unlock you void your warranty if your software is altered from stock.
From what i understand, its not unlocked yet, thats y they can still help
jbh00jh said:
The instruction page at htc/dev unlock says if you use the unlock you void your warranty if your software is altered from stock.
Click to expand...
Click to collapse
Sent from my ADR6425LVW using XDA App
dragonrazorz said:
From what i understand, its not unlocked yet, thats y they can still help
Click to expand...
Click to collapse
Exactly.
jbh00jh said:
The instruction page at htc/dev unlock says if you use the unlock you void your warranty if your software is altered from stock.
Click to expand...
Click to collapse
The HTCDev website says "I acknowledge that use of the unlock bootloader may void all or parts of my warranty device and my device may not function as intended by HTC."
You can see this here http://www.htcdev.com/process/legal
Also I just tried the entire process again using a Linux machine and a different HTCDev account sending to a non gmail address, same thing. It has to be a device issue.
Sent from my Kindle Fire using Tapatalk
Well I hope someone can fix his phone, I'm sure he needs it.
Sent from my Galaxy Tab 10.1
Are you sure that you're correctly in fastboot when trying to run the unlock bin? You need to pull the battery, power on with Vol Down + Power, it should bring you to the hboot. There will be a menu with options (fastboot, recovery, reboot, a couple others) that you can scroll through. Highlight fastboot (I believe it's the top one and highlighted by default) and press power. This should change the menu options shown at the bottom. If I remember correctly, the picture during the HTC dev walkthrough is a picture taken while in fastboot. You need to run the unlock fastboot command while on that menu screen.
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.
All, I am sorry I didn't search more, but I am desperate. I go on travel in a few hours.
Long story short, my phone stopped working with 3g, I spent 4-5 hours on phone with sprint trying to fix. THey want it back to the store. It was HTC unlocked with Fresh. I used fastoot to do fastboot OEM lock, the phone rebooted and goes back to the bootloader screen, I can't get it to go back to Android
It says Tampered, Relocked, security warning. Please. Any help. Can I RUU from fastboot?
Yes
As long as you have the boot loader locked you can run the RUU, you can find the RUU in Android Developement.
Hook the phone to your computer, open a command prompt and type "adb reboot recovery" make sure USB debugging is checked. That should get you into TWRP recovery, then go from there.
musicman625 said:
As long as you have the boot loader locked you can run the RUU, you can find the RUU in Android Developement.
Hook the phone to your computer, open a command prompt and type "adb reboot recovery" make sure USB debugging is checked. That should get you into TWRP recovery, then go from there.
Click to expand...
Click to collapse
After relocking the bootloader, I can no longer enter recovery. RUU doesn't seem to want to run because my phone is not up and running (it is already at fastboot prompt). Can I just get it to recognize my phone in fastboot mode somehow?
U need to unlock it again and flash the stock Rom if u relock it with a custom Rom it doesn't allow it to boot
Sent from my EVO using xda premium
adma84 said:
After relocking the bootloader, I can no longer enter recovery. RUU doesn't seem to want to run because my phone is not up and running (it is already at fastboot prompt). Can I just get it to recognize my phone in fastboot mode somehow?
Click to expand...
Click to collapse
As long as you have the proper drivers you should be able to run the RUU from fastboot. While in fastboot if you type 'fastboot devices' (without quotes) is your phone listed?
Sent from my ELTE using Tapatalk 2
dylan6879 said:
U need to unlock it again and flash the stock Rom if u relock it with a custom Rom it doesn't allow it to boot
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Didn't know that was the case. Thanks
crump84 said:
As long as you have the proper drivers you should be able to run the RUU from fastboot. While in fastboot if you type 'fastboot devices' (without quotes) is your phone listed?
Sent from my ELTE using Tapatalk 2
Click to expand...
Click to collapse
RUU is finally running now. Failed several times, and then just started working. I hope it works. Thank you everyone. Will post back
This happened to me as well. The only thing that I did that finally made it work, was to make sure that the path that I performed the fastboot oem lock command in was the path that contained the fastboot file.
When I did this, it would boot into my custom ROM and I was able to run the RUU without any problems.
When I would try to run the RUU from bootloader it would always tell me my battery was low, even though I was over 90%.
Happend to me too . I just ran ruu while in fastboot .
Sent from my EVO using xda premium
for some reason today i started getting random reboots here and there. when i got home i decided to wipe my phone and do a clean install. everything went well, successful wipe and complete flash of the rom, but when it restarted after the flash it was still the same as before. nothing changed, all my apps, wallpaper, settings everything had been untouched. i even did fastboot wipe userdata. it was like i didnt do anything at all. then i tried wiping my internal sd card, same thing successful wipe, but it all comes back again. i did it a couple of times from the phone settings and also from my computer. then i flashed the ruu from the bootloader, everthing flash normal but when it restarted nothing changed. also tried changing my recovery to cwm but that didnt work either. tried flashing the eng bootloader and it said fail-pu.
right now im running energy rom june 19th, 4 ext recovery, joupunutbear 1.93.2222
any help or advise would be great.
msndroid said:
for some reason today i started getting random reboots here and there. when i got home i decided to wipe my phone and do a clean install. everything went well, successful wipe and complete flash of the rom, but when it restarted after the flash it was still the same as before. nothing changed, all my apps, wallpaper, settings everything had been untouched. i even did fastboot wipe userdata. it was like i didnt do anything at all. then i tried wiping my internal sd card, same thing successful wipe, but it all comes back again. i did it a couple of times from the phone settings and also from my computer. then i flashed the ruu from the bootloader, everthing flash normal but when it restarted nothing changed. also tried changing my recovery to cwm but that didnt work either. tried flashing the eng bootloader and it said fail-pu.
right now im running energy rom june 19th, 4 ext recovery, joupunutbear 1.93.2222
any help or advise would be great.
Click to expand...
Click to collapse
The outlook isn't good, sorry to say that. Most likely, the internal memory chips have failed. Basically, it won't write anymore on it, meaning what you have on it right now may be stuck, permanently. This is because of the "Fail-PU" error. Before doing anything like the wire trick below, try to ensure that the RUU you're trying to flash is a correct one. It would be great if you could get a picture (or describe) what it says when the ruu flash is done. But since you have problems wiping, this may not be the issue. Try the wire trick, as described below with caution.
Unfortunately, there isn't much you can do. I've heard that sometimes if you do the wire trick, it can temporarily fix the error. Heed this. Do the wire trick on its own, meaning do not connect the phone to a computer, or run the Juopunutbear's S-OFF program, or anything of that nature. Just do the exact same wire trick (same timing too) you did to obtain s-off, but without using the s-off program, or plugging it in the computer.
Keep us updated if that trick works for you.
It would also be a good idea to flash a RUU after doing the wire trick (again, without the s-off program, or plugging it in the computer!!!)
Again, best of luck!
this is what came up.
i used this ruu
http://d-h.st/z70
msndroid said:
this is what came up.
i used this ruu
http://d-h.st/z70
Click to expand...
Click to collapse
Have you tried the trick i mentioned earlier and then flashing the RUU?
yes, i've tried it a couple of times. ill try again in the morning but i think its a lost cause though. thanks for your help.
msndroid said:
yes, i've tried it a couple of times. ill try again in the morning but i think its a lost cause though. thanks for your help.
Click to expand...
Click to collapse
theres another thing you could try too.
Boot into fastboot and then type in this command:
fastboot oem boot
Pull out your battery
Put back in.
Flash the RUU
Keylogger_0 said:
theres another thing you could try too.
Boot into fastboot and then type in this command:
fastboot oem boot
Pull out your battery
Put back in.
Flash the RUU
Click to expand...
Click to collapse
no good. i pulled the battery as soon as the htc screen came on and also when the boot animation started. still getting the same results with the ruu.
i noticed this though. isnt it supposed to be bootloader instead of misc?
INFOaARM_Partion[0].name=misc
I'm assuming you know how to use fastboot, flash your stock SHP or ENG hboot via fastboot via:
fastboot erase cache
fastboot rebootRUU
fastboot flash zip en_hboot.zip
Place the attached zip of choice be it sh or en in your adb folder and try those commands, let me know your results.
If he flashes eng hboot, redownloads ruu to ensure good download, and try flashing ruu in bootloader again... I bet it would work
Sent from my HTC VLE_U using Tapatalk 2
msndroid said:
no good. i pulled the battery as soon as the htc screen came on and also when the boot animation started. still getting the same results with the ruu.
i noticed this though. isnt it supposed to be bootloader instead of misc?
INFOaARM_Partion[0].name=misc
Click to expand...
Click to collapse
Actually, I checked it out for my phone with fastboot oem boot too. It lists the partition 0 being the misc partition too. So I think that's fine. My device is fully functional (wipe/flash capabilities included) *knocks on wood* so I think that partition is normal.
Dark Nightmare said:
I'm assuming you know how to use fastboot, flash your stock SHP or ENG hboot via fastboot via:
fastboot erase cache
fastboot rebootRUU
fastboot flash zip en_hboot.zip
Place the attached zip of choice be it sh or en in your adb folder and try those commands, let me know your results.
Click to expand...
Click to collapse
tried both and it gave me this....
C:\adb>fastboot flash zip sh_hboot.zip
sending 'zip' (396 KB)... OKAY [ 0.246s]
writing 'zip'... FAILED (remote: not allowed)
finished. total time: 0.563s
To be honest I think the emmc chip although it's s-off it thinks its still s-on, my best guess would be to try s-off again, see what happens.
Sent from my SGH-T679 using xda app-developers app
msndroid said:
tried both and it gave me this....
C:\adb>fastboot flash zip sh_hboot.zip
sending 'zip' (396 KB)... OKAY [ 0.246s]
writing 'zip'... FAILED (remote: not allowed)
finished. total time: 0.563s
Click to expand...
Click to collapse
Boot into fastboot, and then type in this command
fastboot oem readsecureflag
This command should return with a value of 0
If not, let us know.
Keylogger_0 said:
Boot into fastboot, and then type in this command
fastboot oem readsecureflag
This command should return with a value of 0
If not, let us know.
Click to expand...
Click to collapse
yup thats what i got.
C:\adb>fastboot oem readsecureflag
... INFOsecure_flag: 0
OKAY [ 0.007s]
finished. total time: 0.007s
I kinda gave up on the phone. Ill just buy a galaxy nexus by the end of the month. But if there's still any suggestions I can do to try to fix it, I'm willing to do so, just incase it happens to someone else. Thanks for helping.
Sent from my myTouch_4G_Slide using xda app-developers app
msndroid said:
I kinda gave up on the phone. Ill just buy a galaxy nexus by the end of the month. But if there's still any suggestions I can do to try to fix it, I'm willing to do so, just incase it happens to someone else. Thanks for helping.
Sent from my myTouch_4G_Slide using xda app-developers app
Click to expand...
Click to collapse
You could try to claim warranty, but the thing is, it's already modified so most likely, they won't touch it. A fail-pu error usually means a hardware failure. Most likely, your chip failed and will not write any more.
Another thing you could try to do is brick it, and then claim warranty. You can always say that it turned off and never turned on again.
Keylogger_0 said:
You could try to claim warranty, but the thing is, it's already modified so most likely, they won't touch it. A fail-pu error usually means a hardware failure. Most likely, your chip failed and will not write any more.
Another thing you could try to do is brick it, and then claim warranty. You can always say that it turned off and never turned on again.
Click to expand...
Click to collapse
The warranty is not the same as the tmobile insurence is it? Because I took that off thinking I wouldn't need it. Also stupid question, how would I go about bricking it?lol
Sent from my myTouch_4G_Slide using xda app-developers app
msndroid said:
The warranty is not the same as the tmobile insurence is it? Because I took that off thinking I wouldn't need it. Also stupid question, how would I go about bricking it?lol
Sent from my myTouch_4G_Slide using xda app-developers app
Click to expand...
Click to collapse
HTC usually has warranty too. The thing is, they will most likely refuse it if you have modified the phone.
Bricking can be easy. But, bricking with a Fail-PU error isn't always easy.
PM me later, and I will try to assist you. I'm a bit busy right now so just send me a PM to remind me.
Keylogger_0 said:
HTC usually has warranty too. The thing is, they will most likely refuse it if you have modified the phone.
Bricking can be easy. But, bricking with a Fail-PU error isn't always easy.
PM me later, and I will try to assist you. I'm a bit busy right now so just send me a PM to remind me.
Click to expand...
Click to collapse
Will do. Thanks I appreciate it
Sent from my myTouch_4G_Slide using xda app-developers app
Hi,
I'm having similar issue with my phone, tried a lot of things when I enter command
fastboot oem readsecureflag
I'm getting this:
(bootloader) secure_flag: 3
OKAY [ 0.010s]
finished. total time: 0.011s
If anybody is still checking that thread appreciate any help.
Thanks.
Ok first off my phone just started a boot loop but only with the first htc quietly brilliant screen, noting more. It then restarts and does it all over again. I tried the factory reset a few times and got nothing. So i decided now would be a good time to root so I unlocked with htvdev. Then, using the twrp stuff, i did the fastboot devices cmd and it recognizes the phone. So i did the rest the jewel stuff and it said okay. Then did the cache erase. After getting back to hboot screen i select recovery and it starts with the htc quietly brilliant screen with the red writing under it. After a few seconds the phone restarts and the htc quietly brilliant screen is back but without the red writing under it and it starts the boot cycle all over again. I have no access the the twrp recovery, just the fastboot and bootloader stuff. I am fairly new to this stuff and have searched all over the place but cant find what im looking for. Maybe not looking for the right stuff. Any direction would be great. Thanks
Ok So now I got it to loop the splash screen but with the writing under it. I forced a couple roms and found one that did brick it. Got it back through ubuntu but thats about it, still looping.
Sounds like you're S-on & you need to install the kernel separately from the ROM for your phone to boot. Click the link in my sig for more info.
Also, your phone isn't bricked
Sent from my EVO using xda premium
I cant get into twrp. Its installed but I cant access it and i cant seem to figure out how to flash a kernal or rom or anything. Im running hboot 2.09 unfortunately. I dont know what rom or kernal to flash anyway. The dirtyracun stuff says to boot into recovery for part of it and I cant get into recovery.
Can you access your bootloader screen?
Sent from my EVO using xda premium
FinZ28 said:
Can you access your bootloader screen?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Yes
enolive said:
Yes
Click to expand...
Click to collapse
What happens when you try to access recovery from the bootloader screen?
Sent from my EVO using xda premium
FinZ28 said:
What happens when you try to access recovery from the bootloader screen?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
It shows the splash screen with the htc writing, sits there for 30 secs or so then the screen goes black and then the splash screen comes back up. I keeps doing that over and over. I should clarify that the twrp install was the next step that I was trying to get to. After typing "fastboot flash recovery openrecovery-twrp-2.5.0.0-jewel.img" then selecting recovery. Mind you that the boot cycle was already happening in the very beginning and thats what prompted the root. Kind of a "nothing to lose" deal.
I also just tried to see if adb is still reading my phone and now its showing the "list of devices attached" with nothing listed. Im not sure if the developer options could have been reset to off or something, dont even know if that matters at this point.
You need to get into the bootloader and plug your phone up to it. Make sure it's connected via Fastboot USB highlighted in red, then try fastboot flashing the recovery again. Make sure the recovery file is in your ADB tools folder or it won't work. Once you get recovery working I suggest using the mount option, then you can transfer files to your phone from your computer. I suggest using a ROM that has an S-on kernel installer, like MeanBean. Just follow the instructions for flashing the ROM.
Sent from my EVO using xda premium
FinZ28 said:
You need to get into the bootloader and plug your phone up to it. Make sure it's connected via Fastboot USB highlighted in red, then try fastboot flashing the recovery again. Make sure the recovery file is in your ADB tools folder or it won't work. Once you get recovery working I suggest using the mount option, then you can transfer files to your phone from your computer. I suggest using a ROM that has an S-on kernel installer, like MeanBean. Just follow the instructions for flashing the ROM.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
The phone is plugged into the computer and connected via fastboot usb in red like you said. The recovery file is in the adb folder. It says
C:\Users\Adam\Desktop\Root_HTC_EVO_LTE>fastboot flash recovery openrecovery-twrp
-2.5.0.0-jewel.img
sending 'recovery' (8196 KB)...
OKAY [ 1.010s]
writing 'recovery'...
OKAY [ 2.000s]
finished. total time: 3.020s
Thats the problem, when i select recovery, in the bootloader menu, it just keeps rebooting. I let it go for awhile, like 2 hrs, and thats all it did.
Would a messed up sdcard cause this? Should I try mounting file the the sdcard and then putting it back in the phone? I'm not against going with the s-off but I cant get that to work till i get into the recovery, right?
That's weird. You should be able to get to recovery now. Try and install an older version of TWRP, like version 2.41. It's on their site.
Sent from my EVO using xda premium
FinZ28 said:
Did you try to fastboot flash the recovery to your phone from your computer like I said to do in my previous post? Or are you just trying to boot straight into recovery from the bootloader?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Fastboot flash from the computer? Isnt that what I was doing or am i doing it wrong? I type it all in on the cmd prompt. If thats not right I dont know how else to do it. Is there another way to boot the recovery other then from the bootloader?
Try "fastboot reboot recovery " from the command window.
I'm not 100% positive about that command but it should be good
SENT FROM MY LTEVO
corcgaigh said:
Try "fastboot reboot recovery " from the command window.
I'm not 100% positive about that command but it should be good
SENT FROM MY LTEVO
Click to expand...
Click to collapse
Just tried it and it gave me a list of commands to try. I just copied the twrp file "pj75img.zip" to the sdcard via another phone. Problem is that the battery is to low right now so its gonna wait till tomorrow.
enolive said:
Just tried it and it gave me a list of commands to try. I just copied the twrp file "pj75img.zip" to the sdcard via another phone. Problem is that the battery is to low right now so its gonna wait till tomorrow.
Click to expand...
Click to collapse
You won't be able to flash a PJ75IMG.zip file unless you are S-OFF
Open a cmd window from android-sdk/platform-tools folder and type adb reboot recovery and press enter
that should take you to twrp
bigdaddy619 said:
You won't be able to flash a PJ75IMG.zip file unless you are S-OFF
Open a cmd window from android-sdk/platform-tools folder and type adb reboot recovery and press enter
that should take you to twrp
Click to expand...
Click to collapse
Well now it says "error:device not found". When I type "adb devices" i get the blank list of devices but if i type "fastboot devices" it gives me the number. I think at some point I tried fastbooting a rom didn't work and actually bricked the phone, blank screen that wont turn on. Then fixed that via ubuntu and got it back to the bootloop. As I stated in the beginning it wasnt booting with the red writing at the bottom of the splash screen to start but then went away on the second reboot and kept rebooting without it. After fastbooted twrp again it now shows the red writing on every reboot. Also I cant get the battery to charge because i cant shut it off so it says battery low when i try the flash recovery command. The battery charge led is blinking slowly for about a minute after a simulated battery pull but thats it.
I guess its not fixable.
enolive said:
I guess its not fixable.
Click to expand...
Click to collapse
It's fixable, bro. Check your PM
Sent from my EVO using xda premium