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.
Related
Phone: Evo 3D
Android Version: 2.3.4
Software number: 2..08.651.3
Hboot: 1.50
S-On
Done:
1) HTC boot unlock (http://htcdev.com/bootloader)
2) http://forum.xda-developers.com/showthread.php?t=1239821
-was able to push flies over to phone, but command line "fastboot flash recovery recovery.img" resulted in errors
3) tried to downgrade Hboot using RUU and got an error telling me that my current version was most up to date
Common Threads:
1) http://forum.xda-developers.com/showthread.php?t=1388740
-I downloaded Superuser, titanium back up, and a random program that claimed to verify rooting -- all said I was NOT rooted
2) http://forum.xda-developers.com/showthread.php?t=1307982
-My true goal is to install wifi teathering and titanium backup, I don't care much for custom roms
Forum Confusion:
Unlocking the boot loader does not seem to be the same as rooting, but when I've search through the forums people offer one as a solution to the other.
I'd really appreciate any feedback
thanks guys,
-Nave
navenine said:
Phone: Evo 3D
Android Version: 2.3.4
Software number: 2..08.651.3
Hboot: 1.50
S-On
Done:
1) HTC boot unlock (http://htcdev.com/bootloader)
2) http://forum.xda-developers.com/showthread.php?t=1239821
-was able to push flies over to phone, but command line "fastboot flash recovery recovery.img" resulted in errors
3) tried to downgrade Hboot using RUU and got an error telling me that my current version was most up to date
Common Threads:
1) http://forum.xda-developers.com/showthread.php?t=1388740
-I downloaded Superuser, titanium back up, and a random program that claimed to verify rooting -- all said I was NOT rooted
2) http://forum.xda-developers.com/showthread.php?t=1307982
-My true goal is to install wifi teathering and titanium backup, I don't care much for custom roms
Forum Confusion:
Unlocking the boot loader does not seem to be the same as rooting, but when I've search through the forums people offer one as a solution to the other.
I'd really appreciate any feedback
thanks guys,
-Nave
Click to expand...
Click to collapse
Try this, starting over. You shouldnt run into any hiccups.
tailsthecat3 said:
Try this, starting over. You shouldnt run into any hiccups.
Click to expand...
Click to collapse
I received Error [155] Unknown Error
Display From Phone:
***Unlocked***
Shooter XC ship S-ON RL
HBoot-1.50.0000
eMMC-boot
Aug 7 2011, 10:21:40
RUU
Security fail!
Update Fail!
when it rebooted after recovery I still had all of my user data
navenine said:
I received Error [155] Unknown Error
Display From Phone:
***Unlocked***
Shooter XC ship S-ON RL
HBoot-1.50.0000
eMMC-boot
Aug 7 2011, 10:21:40
RUU
Security fail!
Update Fail!
when it rebooted after recovery I still had all of my user data
Click to expand...
Click to collapse
Ive been through this. Relock(lock) it, run the RUU, then proceed with the instructions I linked.
I was never able to run the RUU while the device was 'unlocked'.
tailsthecat3 said:
Ive been through this. Relock(lock) it, run the RUU, then proceed with the instructions I linked.
I was never able to run the RUU while the device was 'unlocked'.
Click to expand...
Click to collapse
I've been trying to lock it back through the CMD, I wrote a little batch file (and I've manually typed it):
cd c:\android
fastboot oem lock
but after it runs a line shows up as follows:
< waiting for device >
I have USB debugging mode on, and I've tried it with the sd card both mounted and unmounted, I have all the drivers, and adb commands are effective...
do you know what I'm missing?
Thanks again for the help,
-Evan
hey im trying to use the ruu to get back to stock , just re locked the phone , and im STILL getting errors with ruu, its saying Update Failed : Hboot version is older , im on hboot 1.5000 .........Im losing my mind trying to get this thing back to stock and out of htc screen logo bootlooping.........any ideas?
navenine said:
I've been trying to lock it back through the CMD, I wrote a little batch file (and I've manually typed it):
cd c:\android
fastboot oem lock
but after it runs a line shows up as follows:
< waiting for device >
I have USB debugging mode on, and I've tried it with the sd card both mounted and unmounted, I have all the drivers, and adb commands are effective...
do you know what I'm missing?
Thanks again for the help,
-Evan
Click to expand...
Click to collapse
That tells me that youre not in fastboot on your device. I can dupe the same message with my phone disconnected from the pc, then I plug it in in fastboot, and all is good.
Please reinstall the drivers needed but it sounds like youre good. On occasion, I wont be able to flash some things or a file cant load. A reboot of the pc fixes those rare cases for me. Also, refreshing the folders where the files are located.
I also had issues using fastboot, flashing things to the evo because I had my nexus connected for a tether.
If I could do it for you, I would. Hopefully I can help.
tailsthecat3 said:
That tells me that youre not in fastboot on your device. I can dupe the same message with my phone disconnected from the pc, then I plug it in in fastboot, and all is good.
Please reinstall the drivers needed but it sounds like youre good. On occasion, I wont be able to flash some things or a file cant load. A reboot of the pc fixes those rare cases for me. Also, refreshing the folders where the files are located.
I also had issues using fastboot, flashing things to the evo because I had my nexus connected for a tether.
If I could do it for you, I would. Hopefully I can help.
Click to expand...
Click to collapse
this just got even worse, I uninstalled the drivers, and now I can't reinstall them. I can't find them. My computer wont recognize my phone at all. I've tried to goto the device manager and find them online automatically, and I've tried the google USB drivers from the extra folder from the SDK Manager...
if you can point me toward the USB drivers that'd be great, but regardless, what your saying is I need to connect my phone while its in the bootloader? not once its booted? or are you saying I need to boot my phone through the bootloader selecting "fastboot" first?
thanks again
-Nave
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
tailsthecat3 said:
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
Great, I have all the drivers, my phone is relocked, and I'm running the RUU prog now, I'll post in a few minutes to say what happens
thanks for all the help so far, I really do appreciate it!
-Nave
navenine said:
Great, I have all the drivers, my phone is relocked, and I'm running the RUU prog now, I'll post in a few minutes to say what happens
thanks for all the help so far, I really do appreciate it!
-Nave
Click to expand...
Click to collapse
Good. Ive done the process on two different 3D's, a few times. If you follow the instructions, its almost as easy to root as my nexus s was.
tailsthecat3 said:
http://forum.xda-developers.com/showpost.php?p=17083782&postcount=1
Theyre all in there. Youll need those files to root but you should already have the htc sync drivers installed, plus the android usb drivers. You can remove htc sync after installation but keep the drivers.
Boot into hboot and connect it, it may recognize the hardware. Then select fastboot. Fastboot is 'hot swappable' we'll call it, so you can be in fastboot and disconnect and reconnect your usb cable and youll see when its connected-- itll read 'fastboot usb'.
try here
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
I pushed everything over, got it into the fastboot USB and then typed the "fastboot flash recovery recovery.img" command line
my script was:
sending 'recovery' <5068 KB>...
Okay [ 1.207s]
writing 'recovery'...
<bootloader> signature checking...
FAILED <remote:signature verify fail>
finished. total time: 1.855s
any ideas?
tailsthecat3 said:
Good. Ive done the process on two different 3D's, a few times. If you follow the instructions, its almost as easy to root as my nexus s was.
Click to expand...
Click to collapse
Great! thank you soooo much I finally have everything working the way I want it!
haha it seems so much easier now that I know what I was supposed to do
navenine said:
Great! thank you soooo much I finally have everything working the way I want it!
haha it seems so much easier now that I know what I was supposed to do
Click to expand...
Click to collapse
Where were you going wrong? And what'd you do to correct it? So everyone knows, in case they encounter the same issues.
Sent from my Google Nexus S 4G via XDA Premium
Good Idea:
Problem 1)
The RUU wouldn't run
I had this problem because I had already unlocked the the bootloader
I had to re-lock it in order to fix it
Problem 2)
Then The Recovery.img would push through because I forgot to re-unlock the phone
what I did that made it easier:
I wrote a little batch file to run the scripts - a batch file is a command prompt command list set. you open a notepad, type in the the command lists and save it with a .bat file extension...
so I would install all the files and then make a batch file with the following:
cd C:\android
adb push recovery.img /sdcard/
adb push su-2.3.6.3.zip /sdcard/
adb reboot bootloader
pause
fastboot flash recovery recovery.img
change the C:\andriod to whatever your directory set was
and when the batch program runs
anyway good luck to anyone who ends up here, and thanks again tailsthecat3 for the great help
navenine said:
Good Idea:
Problem 1)
The RUU wouldn't run
I had this problem because I had already unlocked the the bootloader
I had to re-lock it in order to fix it
Problem 2)
Then The Recovery.img would push through because I forgot to re-unlock the phone
what I did that made it easier:
I wrote a little batch file to run the scripts - a batch file is a command prompt command list set. you open a notepad, type in the the command lists and save it with a .bat file extension...
so I would install all the files and then make a batch file with the following:
cd C:\android
adb push recovery.img /sdcard/
adb push su-2.3.6.3.zip /sdcard/
adb reboot bootloader
pause
fastboot flash recovery recovery.img
change the C:\andriod to whatever your directory set was
and when the batch program runs
anyway good luck to anyone who ends up here, and thanks again tailsthecat3 for the great help
Click to expand...
Click to collapse
I appreciate that, thank you.
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
hey yall i used the htc dev method to unluck the sprint 3d however when i do the flash recovery img in fastboot i get a failed remote not allowed- i have done this on other phones with no issue but i have tried every recovery.img with no luck . i also tried the PG86IMG but it just says either main version older or PARSING . ant help is MUCH appreciated.
ganjamatik said:
hey yall i used the htc dev method to unluck the sprint 3d however when i do the flash recovery img in fastboot i get a failed remote not allowed- i have done this on other phones with no issue but i have tried every recovery.img with no luck . i also tried the PG86IMG but it just says either main version older or PARSING . ant help is MUCH appreciated.
Click to expand...
Click to collapse
What exactly does your bootloader say? It sounds like it is not unlocked.
If you relocked to run the RUU.exe or take the OTA update it may not be locked now.
ramjet73
ramjet73 said:
What exactly does your bootloader say? It sounds like it is not unlocked.
If you relocked to run the RUU.exe or take the OTA update it may not be locked now.
ramjet73
Click to expand...
Click to collapse
its shows UNLOCKED and hboot 1.58 s-on
ganjamatik said:
its shows UNLOCKED and hboot 1.58 s-on
Click to expand...
Click to collapse
Hmmm...
Well, you won't be able to flash PG86IMG.zip files from the bootloader with S-ON unless thay are signed by HTC so that's probably your problem there.
The "remote not allowed" is usually an indication the bootloader is locked. Make sure your phone is in "fastboot usb" mode in the bootloader, then issue the following commands:
fastboot devices
fastboot flash recovery recovery.img (where "recovery.img" is the file name of your custom recovery)
What responses do you get?
ramjet73
it shows my device listed and then says the same remote not allowed-
Did you check usb debugging in your phone's settings first? Also if you have htc sync on your pc you may want to unistall it also. Some programs do interfere with fastboot.
ganjamatik said:
it shows my device listed and then says the same remote not allowed-
Click to expand...
Click to collapse
Can you try those fastboot commands again and copy and paste the actual output from the commands into this thread? Sometimes there is something in that which might give us a clue as to what the problem is.
Edit: Never mind. I saw you posted again in the other thread so you can wait for a response over there. Make 100% sure your bootloader is unlocked because sometimes flashing the unlock bin file doesn't take and the phone doesn't show the unlock option if you upgraded to ICS via the OTA. If nothing else works I would suggest relocking the bootloader and starting over with the RUU.exe, per the instructions in my root and S-OFF guide.
ramjet73
From the other thread
mpgrimm2 said:
My guess is that you are not really unlocked (Screenshot?) or you are not using a compatible recovery file/filename.
Have a look at the HTC Unlock Guide in my signature to see if anything stands out that you are overlooking.
Even if you get a recovery going, I'm not sure what your ultimate goal is here. You should continue this in one thread, specifically your Remote Not Allowed thread.
Click to expand...
Click to collapse
Go with Ramjet's suggestion if you don't figure it out.
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
I successfully got S-OFF on my Evo V. Now I'm trying to downgrade my hboot to 1.04 ENG. My current hboot is the one JBear puts on after getting S-OFF.
When trying to flash the PG86IMG.zip through fastboot, it gives me the "CID Incorrect!" error and have to power off. My CID is "SPCS_002"
Any help is greatly appreciated.
*EDIT*
Lol. It seems like I find the answer right after I made the thread everytime. I had to edit the PG86IMG.zip to use my CID.
FussyQBert said:
*EDIT*
Lol. It seems like I find the answer right after I made the thread everytime. I had to edit the PG86IMG.zip to use my CID.
Click to expand...
Click to collapse
You could also use the hboot downloads from this post which have been modified to work with both the Sprint (SPCS_001) and Virgin Mobile (SPCS_002) CID's.
ramjet73
ramjet73 said:
You could also use the hboot downloads from this post which have been modified to work with both the Sprint (SPCS_001) and Virgin Mobile (SPCS_002) CID's.
ramjet73
Click to expand...
Click to collapse
Well, I did use an hboot from that post. I tried editing the text file inside to remove the SPCS_001 but this still didn't work. Now when trying to flash through the bootloader, it parses the zip but then doesn't install.
Not sure what's going on :crying:
*EDIT*
Ok now I might have screwed something up. I was able to flash through the command line fastboot, rather than the bootloader. I flashed through the command line using these commands:
fastboot oem rebootRUU
fastboot flash zip PG86IMG_ENG_1.04-hboot.zip
Now my phone is stuck on the RUU HTC screen (the black with silver letters). The progress bar is about 3/4 full
FussyQBert said:
*EDIT*
Ok now I might have screwed something up. I was able to flash through the command line fastboot, rather than the bootloader. I flashed through the command line using these commands:
fastboot oem rebootRUU
fastboot flash zip PG86IMG_ENG_1.04-hboot.zip
Now my phone is stuck on the RUU HTC screen (the black with silver letters)
Click to expand...
Click to collapse
Did you issue the "fastboot reboot" or "fastboot reboot-bootloader" command after the flash finished? Or you can just remove/replace the battery then power on.
ramjet73