Hello
I'm trying to revert back to complete stock (stock rom, no root, S-ON) and following this guide/post:
http://forum.xda-developers.com/showthread.php?p=33770807
For that i need to do check the CID and then write back the original CID (Though i can skip this because i didn't use HTC Dev method at all, just original root and revolutionary S-OFF)
Then i need to do "fastboot oem lock" before running the RUU.. but here in lies my problem.
For some reason i can't get fastboot to work.
ADB works fine and i can push and pull files when in android or recovery, but as soon as i enter hboot and try to use fastboot commands, i just get "< Waiting for device >" and have to close the CMD window. (Before you ask, yes it does say "FASTBOOT USB" on the screen)
I have tried both using my standard adb and fastboot files, and i have also tried downloading the latest android SDK and using those files, but neither to any luck.
Anyone have any idea? It might be something simple, as i haven't had to use fastboot before now.
I'm guessing it can't be a driver problem as i can connect fine with ADB and it shows my device when doing "adb devices" (Though it does not show my device when i do "fastboot devices", it just skips the line entirely and prompts me to enter something new).
- Moon
Moonbloom said:
I'm guessing it can't be a driver problem as i can connect fine with ADB and it shows my device when doing "adb devices" (Though it does not show my device when i do "fastboot devices", it just skips the line entirely and prompts me to enter something new).
Click to expand...
Click to collapse
If "fastboot devices" doesn't show the serial number of your phone, none of the other fastboot commands are going to work.
Have you tried disconnecting the phone, rebooting your PC and then connecting the phone again? If that doesn't work, try uninstalling the drivers, rebooting the PC, then reinstalling the drivers.
ramjet73
ramjet73 said:
If "fastboot devices" doesn't show the serial number of your phone, none of the other fastboot commands are going to work.
Have you tried disconnecting the phone, rebooting your PC and then connecting the phone again? If that doesn't work, try uninstalling the drivers, rebooting the PC, then reinstalling the drivers.
ramjet73
Click to expand...
Click to collapse
Tried to reboot the computer, no change.
Decided to try using my laptop before going through the trouble of reinstalling drivers, and it worked
My laptop can see my device fine using "fastboot devices" and i'm able to get my CID (cid: 0202)
Thanks for trying to help me out anyways I might be back with more questions
EDIT: I just google'd a bit and found another command to get the CID "fastboot oem readcid" and it shows HTC_Y13 (which i find more believable tbh).
Is your hboot unlocked?
I am s-off, but couldn't use fastboot commands untill i unlocked my bootloader again..
klect said:
Is your hboot unlocked?
I am s-off, but couldn't use fastboot commands untill i unlocked my bootloader again..
Click to expand...
Click to collapse
There's no need to unlock the bootloader if you are S-OFF.
If you want to run fastboot commands like "flash" or "erase" just install a custom bootloader like ENG, JBear or Revoutionary from the current bootloader. It's better to keep the bootloader locked since that's the stock status and it makes it much easier to return the phone to 100% stock.
AFAIK, the "*** RELOCKED ***" heading you get when locking an unlocked bootloader which flags to HTC/Sprint that you modified the phone can only be undone with the JuopunutBear wire trick.
ramjet73
For me IT was the only way to get fastboot working though...
Sent from my Evo 3D GSM using xda app-developers app
klect said:
For me IT was the only way to get fastboot working though...
Click to expand...
Click to collapse
Did you try one of the JuopunutBear bootloaders (GB or ICS) for the GSM version of the Evo 3D? That should allow the fastboot commands without unlocking.
ramjet73
Yeah, after i s-offed i flashed the ICS jb hboot, but no luck...
So i decided to flash the 1.49.0007 hboot and unlock it the htcdev way.
But if you want to lock it again, you can simply redo the wiretrick right?
klect said:
Yeah, after i s-offed i flashed the ICS jb hboot, but no luck...
So i decided to flash the 1.49.0007 hboot and unlock it the htcdev way.
But if you want to lock it again, you can simply redo the wiretrick right?
Click to expand...
Click to collapse
That's correct.
ramjet73
For all those who were directed here...
This solved my problem when everybody else's advice failed, and it was the easiest.
http://forums.androidcentral.com/ve...how-install-device-drivers-android-1-0-a.html
Related
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
I got a 3d from a friend who says he was trying to root it. He did the htc unlock I think. The bootloader said unlocked, I relocked it with the relock oem command on cmd. I have tried a few different IMG and exe files and none will work. does anyone have any ideas as to what else I could try? Ive googled and all I keep getting is more downloads for ruu.
Any help will be greatly appreciated.
gamy2121 said:
I got a 3d from a friend who says he was trying to root it. He did the htc unlock I think. The bootloader said unlocked, I relocked it with the relock oem command on cmd. I have tried a few different IMG and exe files and none will work. does anyone have any ideas as to what else I could try? Ive googled and all I keep getting is more downloads for ruu.
Any help will be greatly appreciated.
Click to expand...
Click to collapse
This article tells you how to read and set the CID. It's written for the GSM version, but the "readcid" command seems to work on my CDMA version and has a value of "SPCS_001". If that's not what your phone shows it may be why the RUU's aren't working.
I didn't try the "writecid" command since I don't need to change mine.
ramjet73
ramjet73 said:
This article tells you how to read and set the CID. It's written for the GSM version, but the "readcid" command seems to work on my CDMA version and has a value of "SPCS_001". If that's not what your phone shows it may be why the RUU's aren't working.
I didn't try the "writecid" command since I don't need to change mine.
ramjet73
Click to expand...
Click to collapse
I just did the readcid and it says I have SPCS_001
gamy2121 said:
I just did the readcid and it says I have SPCS_001
Click to expand...
Click to collapse
Are you putting your phone into "fastboot USB" mode in the bootloader before running the RUU.exe from Windows? It's supposed to work if you're booted into Android and just reboot into the bootloader on its own, but sometimes that doesn't work.
Also, try the "fastboot devices" command from the PC directory with ADB before running the RUU.exe and make sure you get a serial number that starts with "HT" as a response.
ramjet73
ramjet73 said:
Are you putting your phone into "fastboot USB" mode in the bootloader before running the RUU.exe from Windows? It's supposed to work if you're booted into Android and just reboot into the bootloader on its own, but sometimes that doesn't work.
Also, try the "fastboot devices" command from the PC directory with ADB before running the RUU.exe and make sure you get a serial number that starts with "HT" as a response.
ramjet73
Click to expand...
Click to collapse
Yes to the fastboot usb - Thats all I can do if I try to boot up it just gets stuck at the white htc screen.
edit: this is what Im getting on the fastboot devices --- SH19THX01975 fastboot
gamy2121 said:
Yes to the fastboot usb - Thats all I can do if I try to boot up it just gets stuck at the white htc screen.
edit: this is what Im getting on the fastboot devices --- SH19THX01975 fastboot
Click to expand...
Click to collapse
I don't recognize that serial number as an Evo 3D. I have two and their serials both start with "HT".
Maybe someone else can help with that.
ramjet73
ramjet73 said:
I don't recognize that serial number as an Evo 3D. I have two and their serials both start with "HT".
Maybe someone else can help with that.
ramjet73
Click to expand...
Click to collapse
Thanks for your help, I did notice on the phone one of the errors was something about hoot being older.
SOLVED*****
Heres what I had to do incase some else ever has this problem.
IDK what the previous owner did but I had to start the RUU on the PC then go into the temp folder and go into the ROM folder with 7zip and take the stock recovery.img and fastboot flash it through cmd. Then I ran the RUU and the phone finally took it.
Gave my Evo 3d to my borother a few months back, but hes come back to me today saying it was stuck in bootloop.
He booted into the bootloader and did a factory reset, but it was still stuck in bootloop.
I tried to get into recovery to flash a new rom, but when i select recovery from the bootloader, that also goes into a bootloop.
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Not sure if its important but the phone is s-off. Any ideas on whats going on or how to fix?
Apologies, supposed to put this in Q&A forum
While you're at bootloader, connect USB and then flash a stock RUU.
androidcdma said:
While you're at bootloader, connect USB and then flash a stock RUU.
Click to expand...
Click to collapse
Thanks for the reply. Will i lose s-off with this?
Tones1971 said:
Gave my Evo 3d to my borother a few months back, but hes come back to me today saying it was stuck in bootloop.
He booted into the bootloader and did a factory reset, but it was still stuck in bootloop.
I tried to get into recovery to flash a new rom, but when i select recovery from the bootloader, that also goes into a bootloop.
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Not sure if its important but the phone is s-off. Any ideas on whats going on or how to fix?
Apologies, supposed to put this in Q&A forum
Click to expand...
Click to collapse
You didn't say what version of the Evo 3D you have (CDMA or GSM) or what bootloader is installed, but if it's a Sprint CDMA model I would recommend flashing the Sprint ICS RUU.exe from Windows after putting the phone into fastboot mode in the bootloader. You may have to relock the bootloader with the "fastboot oem lock" command first if it shows "***UNLOCKED***" at the top of the screen.
That will fix a lot of problems, especially when the phone is in an indeterminate state. After flashing the RUU you can HTC unlock, flash a custom recovery and then root the stock ROM or flash a rooted ROM.
ramjet73
Sorry it is a UK GSM (Europe). I have revolutionary bootloader installed. Got an RUU to try now thanks.
androidcdma said:
While you're at bootloader, connect USB and then flash a stock RUU.
Click to expand...
Click to collapse
Tones1971 said:
Thanks for the reply. Will i lose s-off with this?
Click to expand...
Click to collapse
^^^^ He got it first with the short version.
No, you won't lose S-OFF and won't need to relock the bootloader first if that's your current status.
And if it's a GSM model everything still applies, you just need a different RUU, which you already have.
ramjet73
Thanks ramjet. Thought this was going to be straightforward but cant get ruu to install. Error 170. Ill keep plugging away / googling away, hopefully come up with something
Tones1971 said:
Thanks ramjet. Thought this was going to be straightforward but cant get ruu to install. Error 170. Ill keep plugging away / googling away, hopefully come up with something
Click to expand...
Click to collapse
Error 170 means that the RUU utility can't find the phone. There's a readme.doc for running the RUU here, and the error codes are towards the end of that.
Are you putting it into "fastboot" mode in the bootloader, which should change to "fastboot usb" when it is connected to a computer? You also need to have the HTC USB drivers active, which can be accomplished by installing HTC Sync.
ramjet73
Tones1971 said:
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Click to expand...
Click to collapse
adb push into a bootlooping phone?
do you have the drivers for the phone? (if not download and install HTC Sync as they come with it)
did you try flashing a custom recovery img through fastboot? (go to bootloader select fastboot, connect USB, type "fastboot flash recovery nameOfYourRecoveryImg.img")
Yeah have tried installing custom recovery through fast boot again, and im in fastboot ok when trying to run the RUU. Also have HTC Sync installed from when i had the phone.. Drivers seemed to be ok as i was able to install the custom recovery with adb, alhough i still got bootloop after that.
Ive a few other things to try when i get home from work. Im sure it shouldnt be too difficult to resolve. Hopefully anyway.
Well this isnt going smoothly at all. Used another PC and was able to get the RUU to run.
However it now comes up with Error 131 Customer ID problem. The RUU was for HTC Europe (non branded). The phone was sim free. When i posted months back my cid was HTC_001. I checked it here: http://forum.xda-developers.com/showpost.php?p=22394863&postcount=172
However now when i get my CID it is showing as CID0202. Any way i can get an RUU to install? Any idea how a CID could change?
EDIT: noticed i used a different command last time.
fastboot getvar cid shows CID0202
adb shell getprop ro.cid now shows device not found (previously showed CID_001)
Thats typing both commands in same window, one after the other. One gets CID0202, the other device not found???
There's a change cid command in fastboot, fastboot oem writecid or something along those lines... however i believe the cid check is in the updater scripts of the ruu in which case a fastboot flash of all the img files should avoid it entirely... i don't remember the procedure for extracting the img files from the ruu but i believe ur supposed to run it and then dig through your temp files...
dessolator666 said:
There's a change cid command in fastboot, fastboot oem writecid or something along those lines... however i believe the cid check is in the updater scripts of the ruu in which case a fastboot flash of all the img files should avoid it entirely... i don't remember the procedure for extracting the img files from the ruu but i believe ur supposed to run it and then dig through your temp files...
Click to expand...
Click to collapse
Thanks for this. Ill see if i can find anything else out about it. So saves running the RUU exe and no cid check done then?
Need to bump this as im not getting anywhere. No RUU's will install, error 31 customer error. Have flashed recovery via ADB and through PG86IMG.ZIP, but still cant get in to recovery as it just continually reboots.
S-OFF with revolutionary. Anybody any ideas please?
Got bigger problems than i thought. Finally got an RUU to install after 4 days of trying, by first using fastboot oem writecid 11111111. But when the phone rebooted it was back bootlooping again. Is there any hope for my phone?
Tones1971 said:
Got bigger problems than i thought. Finally got an RUU to install after 4 days of trying, by first using fastboot oem writecid 11111111. But when the phone rebooted it was back bootlooping again. Is there any hope for my phone?
Click to expand...
Click to collapse
You need to stop cross posting in the d3rp Q&A thread and your own thread if you want more help. Cross-posting is stongly discouraged on XDA and it's really confusing when you are asking for help in one thread while getting different advice in another.
It sounds to me like all the CID changes on your phone have left it in an indeterminate state and I'm not sure at this point what is the correct CID and RUU for your model. If you could detemine that, set the CID correctly and flash the right RUU the phone should work, but it might be too late if you have in fact been flashing firmware that doesn't match your phone because the right RUU may not back that out properly.
That's all I can offer at this point, but since I don't know the history of your phone and how it got the various CID's you have reported, you will probably be the one that needs to figure it out.
ramjet73
I was using Evolver 3D 2.5 ICS ROM when I noticed BiParanoid JB rom out there, so I tried the ROM...
Then I find the ROM not fully working for me so I tried to get back to KingCobra3D ICS ROM, and the problem was, every HTC rom didn't boot up although I flashed the boot.img via fastboot. I tried at least 5 ROMs doing that but all I get is stuck at boot. Then I try flashing any other rom like AOKP and BiParanoid and they all boot up. I am running EVO 3D GSM S-ON. Any help would be appriciated and sorry for my bad english.
Seems like there's a problem with AOKP rom's when you try to flash htc rom
wayphaax said:
I was using Evolver 3D 2.5 ICS ROM when I noticed BiParanoid JB rom out there, so I tried the ROM...
Then I find the ROM not fully working for me so I tried to get back to KingCobra3D ICS ROM, and the problem was, every HTC rom didn't boot up although I flashed the boot.img via fastboot. I tried at least 5 ROMs doing that but all I get is stuck at boot. Then I try flashing any other rom like AOKP and BiParanoid and they all boot up. I am running EVO 3D GSM S-ON. Any help would be appriciated and sorry for my bad english.
Seems like there's a problem with AOKP rom's when you try to flash htc rom
Click to expand...
Click to collapse
I would recommend relocking the phone "fastboot oem lock" and running the appropriate ruu off the computer. This will get you back to a completely stock htc android. From there you can re do the unlock on htcdev and flash any rom you like.
dessolator666 said:
I would recommend relocking the phone "fastboot oem lock" and running the appropriate ruu off the computer. This will get you back to a completely stock htc android. From there you can re do the unlock on htcdev and flash any rom you like.
Click to expand...
Click to collapse
I already put the PG86IMG.zip to my SD card, got in to bootloader, but it said this zip is wrong, although its for my region...
I tried running ruu too, but got stuck on instal...
So if I relock the phone its possible to get to stock?
Thank you for the reply
wayphaax said:
I already put the PG86IMG.zip to my SD card, got in to bootloader, but it said this zip is wrong, although its for my region...
I tried running ruu too, but got stuck on instal...
So if I relock the phone its possible to get to stock?
Thank you for the reply
Click to expand...
Click to collapse
yes, if you're not S-off you have to relock your bootloader for the RUU to flash
Thank you, will try that out
Sent from my Evo 3D GSM using xda app-developers app
Another thing, im little of newbie, so I just use "fastboot oem lock" and bootloader will relock or i have to do full project? I unlocked bootloader on htcdev
Sent from my Evo 3D GSM using xda app-developers app
wayphaax said:
Another thing, im little of newbie, so I just use "fastboot oem lock" and bootloader will relock or i have to do full project? I unlocked bootloader on htcdev
Sent from my Evo 3D GSM using xda app-developers app
Click to expand...
Click to collapse
Ok, so, connect your phone to the PC.
go into settings find "Enable USB Debugging" and turn it on.
On your computer, start command prompt(cmd) and navigate to the directory where your adb and fastboot are.
type "adb reboot bootloader" and wait for the phone to get into the bootloader
it should now say "fastboot USB"
in cmd type "fastboot oem lock"
your phone bootloader is now locked.
go to : http://forum.xda-developers.com/showthread.php?t=1208485 and find the RUU you need
with the phone in fastboot run the RUU.
assuming you have the right RUU it should have worked and your phone should now be fully stock HTC
to do any other flashing you're going to need to re unlock you bootloader using the htcdev method (or at least your old Unlock_Token though you might need a new one)
dessolator666 said:
Ok, so, connect your phone to the PC.
go into settings find "Enable USB Debugging" and turn it on.
On your computer, start command prompt(cmd) and navigate to the directory where your adb and fastboot are.
type "adb reboot bootloader" and wait for the phone to get into the bootloader
it should now say "fastboot USB"
in cmd type "fastboot oem lock"
your phone bootloader is now locked.
go to : http://forum.xda-developers.com/showthread.php?t=1208485 and find the RUU you need
with the phone in fastboot run the RUU.
assuming you have the right RUU it should have worked and your phone should now be fully stock HTC
to do any other flashing you're going to need to re unlock you bootloader using the htcdev method (or at least your old Unlock_Token though you might need a new one)
Click to expand...
Click to collapse
THANKS FOR THE HELP, it worked!! apriciate the help really!
Semi-noob here, would appreciate any help!
S-Off using revone, flashed CWM, and then ROM'd. Found an issue with the phone (wireless charger not working), so need to return to stock before bringing to Verizon. Used adb to S-On, and now, I am STUCK in Fastboot (or is it called Hboot?)!
None of the "options in Fastboot do anything (Bootloader, Reboot, Reboot Bootloader, Factory Reset). I can't get anywhere past Fastboot!
I think my problem was that I did not flash the stock ROM first, before S-on again. The phone no longer goes into Bootloader, so I don't know how to flash a ROM at this point.
Any help would be majorly appreciated! Thank you, oh wise ones...
geeDoh said:
Semi-noob here, would appreciate any help!
S-Off using revone, flashed CWM, and then ROM'd. Found an issue with the phone (wireless charger not working), so need to return to stock before bringing to Verizon. Used adb to S-On, and now, I am STUCK in Fastboot (or is it called Hboot?)!
None of the "options in Fastboot do anything (Bootloader, Reboot, Reboot Bootloader, Factory Reset). I can't get anywhere past Fastboot!
I think my problem was that I did not flash the stock ROM first, before S-on again. The phone no longer goes into Bootloader, so I don't know how to flash a ROM at this point.
Any help would be majorly appreciated! Thank you, oh wise ones...
Click to expand...
Click to collapse
The good news is, if you really are stuck in fastboot, you can still use adb/fastboot commands to get your phone working again. There is an important distinction between fastboot and hboot, though: fastboot is basically the bootloader's "debug" mode, while hboot is the regular bootloader mode. You won't be able to do much if your bootloader says "hboot" above the available options, but if it says "fastboot" or "fastboot usb" you're fine.
You should try to get s-off again (assuming you haven't relocked your bootloader) either via revone or facepalm, then flash a stock rom and proceed from there.
Clarification: if you have relocked your bootloader, unlock, then get s-off.
Used adb to S-On? Meaning what exactly? Did you lock beforehand?
I currently have S-on. I used revone's method to S-off.
I think the problem is that I have relocked the bootloader (phone shows LOCKED) with a custom ROM installed. I think I should have flashed a stock ROM before relocking. Would this have caused the problem I'm having?
I am not sure how to get S-off again, because I am stuck on the FASTBOOT. Selecting Bootloader/Reboot/Reboot Bootloader just returns me to the same screen. When I try to enter any line items (in Terminal), adb says there are no devices connected (this is probably due to the fact that my phone no longer boots to the homescreen). Any suggestions of how to get S-off again??
Thanks...
What method did you use for S-ON? There are guides here that lay out every step needed to return to stock.
Also when in fastboot, you need to use fastboot, not adb. Type in fastboot devices. Does your device ID show?
I would suggest trying to run the RUU. Although it may not work depending on HBOOT version and the fact you are now S-ON.
Can you boot into Recovery? If so, is there a ROM still on the phone? If so, try flashing it...
geeDoh said:
I currently have S-on. I used revone's method to S-off.
I think the problem is that I have relocked the bootloader (phone shows LOCKED) with a custom ROM installed. I think I should have flashed a stock ROM before relocking. Would this have caused the problem I'm having?
I am not sure how to get S-off again, because I am stuck on the FASTBOOT. Selecting Bootloader/Reboot/Reboot Bootloader just returns me to the same screen. When I try to enter any line items (in Terminal), adb says there are no devices connected (this is probably due to the fact that my phone no longer boots to the homescreen). Any suggestions of how to get S-off again??
Thanks...
Click to expand...
Click to collapse
Does the unit show up in device manager? You may need to install a driver.
Phaded said:
What method did you use for S-ON? There are guides here that lay out every step needed to return to stock.
Also when in fastboot, you need to use fastboot, not adb. Type in fastboot devices. Does your device ID show?
I would suggest trying to run the RUU. Although it may not work depending on HBOOT version and the fact you are now S-ON.
Can you boot into Recovery? If so, is there a ROM still on the phone? If so, try flashing it...
Click to expand...
Click to collapse
Oh, using Fastboot gave me my device ID. What can I do now??
I can't get into Recovery from Fastboot USB. The option for Bootloader and Reboot Bootloader are there, but selecting them just returns me to Fastboot USB. I assume this is because I am already S-On again...?
geeDoh said:
Oh, using Fastboot gave me my device ID. What can I do now??
I can't get into Recovery from Fastboot USB. The option for Bootloader and Reboot Bootloader are there, but selecting them just returns me to Fastboot USB. I assume this is because I am already S-On again...?
Click to expand...
Click to collapse
Select bootloader, then recovery. The menus look the same, but they are different.
If you can boot into recovery, what is it? Stock or custom?
Phaded said:
Select bootloader, then recovery. The menus look the same, but they are different.
If you can boot into recovery, what is it? Stock or custom?
Click to expand...
Click to collapse
When I select Bootloader -> Recovery, the HTC screen flashes, then I'm returned to Fastboot USB.
geeDoh said:
When I select Bootloader -> Recovery, the HTC screen flashes, then I'm returned to Fastboot USB.
Click to expand...
Click to collapse
That's because you have unsigned boot.img and/or recovery and relocked the device.
You need to RUU or unlock again to boot to anything.
Any tips on how to unlock again? (and once I am unlocked, i assume I need to load Recovery, and from there, flash a stock ROM?)
geeDoh said:
Any tips on how to unlock again? (and once I am unlocked, i assume I need to load Recovery, and from there, flash a stock ROM?)
Click to expand...
Click to collapse
Run Moonshine.
If that fails, RUU to stock.
You didn't happen to make an unlock_code.bin with htc did you?
No, i didn't. Not even sure what that is...haha...
I'm going to run RUU, and hope that works! Thanks for everyones input...
still no luck! =T
So, I've tried running RUU (this is the RUU file I'm using: RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed), but after it runs for a while (it says it is erasing data, then sending to the phone),
RUU says I am currently on 2.06, so is this the correct RUU file?
Another option for me, other than putting the phone back to stock, is for me to completely brick it. I tried unplugging and powering off the phone while RUU was running, but it still comes back to Fastboot. Suggestions?
Thanks again....
geeDoh said:
So, I've tried running RUU (this is the RUU file I'm using: RUU_DLX_WL_JB_45_VERIZON_WWE_1.15.605.4_Radio_1.00.00.1023_3_NV_VZW_1.98_002_release_290923_signed), but after it runs for a while (it says it is erasing data, then sending to the phone),
RUU says I am currently on 2.06, so is this the correct RUU file?
Another option for me, other than putting the phone back to stock, is for me to completely brick it. I tried unplugging and powering off the phone while RUU was running, but it still comes back to Fastboot. Suggestions?
Thanks again....
Click to expand...
Click to collapse
Just run the RUU. There is only one RUU. You are on 2.06, that's why it tells you that. Let the whole thing run.
You cannot downgrade via RUU. You need to unlock the phone, s-off it (facepalm should suffice) then you can RUU back to 1.15 if you choose.
beaups said:
You cannot downgrade via RUU. You need to unlock the phone, s-off it (facepalm should suffice) then you can RUU back to 1.15 if you choose.
Click to expand...
Click to collapse
Ah forgot he went back to S-On.
Phaded said:
Ah forgot he went back to S-On.
Click to expand...
Click to collapse
I have the same problem. Since it was relocked, the htc dev site can't give the bin file to unlock it again. So I'm stuck in fastboot usb mode and I can't do anything about it. If only I can unlock it again, then I can move on from there.
okyere said:
I have the same problem. Since it was relocked, the htc dev site can't give the bin file to unlock it again. So I'm stuck in fastboot usb mode and I can't do anything about it. If only I can unlock it again, then I can move on from there.
Click to expand...
Click to collapse
Still have the token? Or the email that it got sent in?