Hey guys I need a bit of help.
Im stuck running the RUU. Specifically the part right after it says "Erasing User Data" where it says "Sending"
Yes the sending part. The blue bar never does anything and the phone stays in the black screen with the words "HTC" in green.
Once I get the error I can disconnect and do a battery pull and the phone turns right back on.
I have my adb drivers and i have HTC Sync installed.
I tried running the RUU from both the C drive and my documents and the same results every time.
If anyone has a fix and knows what im doing wrong I will appreciate your help.
ThKs
Which RUU are you trying to flash? I see in your sig that you've got the Virgin Mobile Evo V so I'm assuming it's the 1.13.652.2 version.
When I've flashed the Sprint RUU.exe versions, it's hung a few times at the "waiting for bootloader" stage, especially when I flash it S-OFF with a custom bootloader installed. That is usually resolved by cancelling the Windows app and restarting it.
I've also found that starting the RUU.exe with the phone in the "fastboot USB" mode in the bootloader helps, but it sounds like you are past the point where that would make a difference.
The only thing I can suggest is to restart it with your phone in the bootloader, and give it plenty of time to complete. Normally it takes only about 10 minutes, but I'd give it at least 15.
If all else fails, you may need to get the phone serviced. You didn't say why you are flashing the RUU but if a partition got messed up or you have some type of hardware problem it may never flash successfully.
ramjet73
Yeah I have a Virgin Mobile RUU and I'm flashing it back to stock to reroot it so I can get s-off . I spoke to one of the members of unlimited.io and he said that the s-off tool will fail unless I'm on a stock ruu rom. I have the bootloader unlocked and im on a stock deodex rom but he tells me to ruu back to stock root and then use the tool. Other than that my phone is fine. I'm just trying to change my hboot and a few other things so that I can fix the signal loss problem that the Evo 3D for VM has.
Oh and yeah I've tried fastboot and bootloader. Actually that's the only way I get past the detection. When the ruu says that its rebooting the phone it fails. I have to have it already on fastboot or bootloader
Sent from my HTCEVOV4G using xda premium
roketteere said:
I have the bootloader unlocked...
Click to expand...
Click to collapse
If you are currently S-ON, your bootloader needs to locked to flash the RUU.exe successfully. You can do that with the "fastboot oem lock" command.
The JuopunutBear wire trick requires that you are HTC unlocked, so you will have to unlock again after flashing the RUU but can use the same unlock token as the first time.
ramjet73
ramjet73 said:
If you are currently S-ON, your bootloader needs to locked to flash the RUU.exe successfully. You can do that with the "fastboot oem lock" command.
The JuopunutBear wire trick requires that you are HTC unlocked, so you will have to unlock again after flashing the RUU but can use the same unlock token as the first time.
ramjet73
Click to expand...
Click to collapse
ok thank you I will post my results.
By the way here are two screen shots of what it looks like.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank you!
It work like a charm right after relocking the bootloader.
Now to reroot, unlock bootloader, and finally s-off
roketteere said:
Yeah I have a Virgin Mobile RUU and I'm flashing it back to stock to reroot it so I can get s-off . I spoke to one of the members of unlimited.io and he said that the s-off tool will fail unless I'm on a stock ruu rom. I have the bootloader unlocked and im on a stock deodex rom but he tells me to ruu back to stock root and then use the tool. Other than that my phone is fine. I'm just trying to change my hboot and a few other things so that I can fix the signal loss problem that the Evo 3D for VM has.
Oh and yeah I've tried fastboot and bootloader. Actually that's the only way I get past the detection. When the ruu says that its rebooting the phone it fails. I have to have it already on fastboot or bootloader
Sent from my HTCEVOV4G using xda premium
Click to expand...
Click to collapse
Not true that you must be on stock. I was running meanrom 2.5 when I s-offed
Well it didn't work for me with 3 different roms so I asked for support on their site. That was the response that I got. Now im s-off, boot on eng, and rooted running harmonia rom.
I also changed pri and prl as suggested and now my signal is perfect no calling or texting problems.
Sent from my HTCEVOV4G using xda premium
Related
Not sure if anyone posted this but the HTC Unlocking procedure works after the OTA update. I unlocked my friend's bootloader using the directions on the htcdev site (even though it says unlocking is only available for the sensation currently)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I read on goodandevo.net that its supposed to erase all the contacts and everything else that you changed on the phone. that it basically reverts it to stock. is that true?
Johnabis said:
I read on goodandevo.net that its supposed to erase all the contacts and everything else that you changed on the phone. that it basically reverts it to stock. is that true?
Click to expand...
Click to collapse
I know it did it on the xoom. Not sure, I did it on my friend's brand new phone so there was no data on it. My phone is s-offed
Nice man...thanks for being the n00b...I mean tester...
Sent from my PG86100 using Tapatalk
Why does it say "unlocked" but it still says S-ON?
I noticed that it says S-On, can you flash a custom recovery via bootloader?
spencer88 said:
Why does it say "unlocked" but it still says S-ON?
Click to expand...
Click to collapse
I guess that's their procedure. Before I unlocked it, it said "LOCKED" in the pink banner. TWRP didnt flash or boot but CWM did.
XsMagical said:
I noticed that it says S-On, can you flash a custom recovery via bootloader?
Click to expand...
Click to collapse
I was able to flash clockwork mod. TWP didnt boot and just rebooted the phone when I tried to go into recovery. I dont have any roms here to flash and I'm leaving in a few for a final I have. BUT I did pop my memory card in there and am going through a restore now
graffixnyc said:
I guess that's their procedure. Before I unlocked it, it said "LOCKED" in the pink banner. TWRP didnt flash or boot but CWM did.
Click to expand...
Click to collapse
I wonder if you can run the fastboot command "setsecureflag" if that will change the S-ON to S-OFF.
graffixnyc said:
I was able to flash clockwork mod. TWP didnt boot and just rebooted the phone when I tried to go into recovery. I dont have any roms here to flash and I'm leaving in a few for a final I have. BUT I did pop my memory card in there and am going through a restore now
Click to expand...
Click to collapse
You have some balls to use their method to unlock if that's your only EVO 3D lol
spencer88 said:
You have some balls to use their method to unlock if that's your only EVO 3D lol
Click to expand...
Click to collapse
Why? HTC makes the phone and software for it. Their methods are better than finding hacks and holes in the software to push the things needed for s-off, etc.
spencer88 said:
You have some balls to use their method to unlock if that's your only EVO 3D lol
Click to expand...
Click to collapse
I don't see why people are so scared to use the method. Yes you loose your warranty, but honestly how many people have used warranty to fix a phone? I personally have NEVER, but have used insurance 3 times over the last 10 years.
i use htc unlock but cant get the recovery load just reboots...tried both custom recoverys
nao2003 said:
i use htc unlock but cant get the recovery load just reboots...tried both custom recoverys
Click to expand...
Click to collapse
^ Thats why i don't use the HTC Unlock.
S-ON will always be on using HTC's method. I believe it's to keep you from flashing the radio. If I'm correct the only extra thing you can actually flash with htc's unlocker is the system, data and boot partition. Or certain recovery's authorized by HTC can be flashed.
spencer88 said:
I wonder if you can run the fastboot command "setsecureflag" if that will change the S-ON to S-OFF.
Click to expand...
Click to collapse
Hmm ill try when I get home. It's not my phone. It's my friends. Hehe mine has been s-off since the day it was released.
Ok so can't flash splash screens. I tried flashing it via fastboot and the zip. When i try in fastboot I get a bootloader signiture error. When i try the zip it starts to parse it but then boots me out. Engine hboot zip did the same thing. While its partially unlocked I think they still locked down some things. Fastboot erase recovery errors out saying not allowed.
Sent from my PG86100 using XDA App
mwalt2 said:
Why? HTC makes the phone and software for it. Their methods are better than finding hacks and holes in the software to push the things needed for s-off, etc.
Click to expand...
Click to collapse
This is also what differentiates a tester and a follower...trying it out for yourself .
Edit...quoted the wrong part...should have quoted the having balls part...
I have used my warranty Prolly 10 times in the last 3 years. Good luck with your EVO and if it screws up your screwed
Sent from my PG86100 using XDA App
Really? 10 times in 3 years. This is why HTC is reserving the right to void your warranty. Phones will be offered as is before long if others are destroying them as fast as you.
Sent from my EVO 3D using Tapatalk
Can someone show me the quoted text from HTC's site that says if you unlock using their method that your warranty is void. Or is everyone just assuming this because they want your serial number to unlock.
LMAO
Your warranties are now invalid
Should have used revolution, and keep your warranties intact.
Hi,
I'm stuck in this situation with my htc evo view 4g device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
everytime I try to reboot, or enter recovery, or factory reset it just hangs at this screen:
I try to flash this stock rom
RUU_Express_Sprint_WWE_1.22.651.1_Radio_1.05.11.0531_NV_2.28_SPCS_release_198141_signed
(via both RUU on my pc and goldcard with PG41IMG.zip), it was flashed flawlessly, but when finished it hangs in that "htc" screen.
I tried to s-off by revolutionary but I can not access the android working screen so that can not enable usb debugging mode, on the pc it just shows
waiting for device ....
Click to expand...
Click to collapse
I tried to unlock the bootloader via htcdev (I know my view 4g isn't in the supported list yet, but at least fastboot should read its info, but I was wrong). At step 8, it shows:
C:\Android>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
Click to expand...
Click to collapse
It still boots in to fastboot mode,and I could see that it's s-on, hboot is 1.13. Now I want to make it s-off or unlock the bootloader in order to flash a custom rom.
Can some one please help me with this ?
Thanks a lot,
Medkid
I tried to unlock the htc view's bootloader by htcdev, at steps 8 it shows me this
C:\Android>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
Click to expand...
Click to collapse
can you help ? plz
what were you trying to do when you got into this situation and did you run the ruu more than once?
mcord11758 said:
what were you trying to do when you got into this situation and did you run the ruu more than once?
Click to expand...
Click to collapse
Upload the logs from c:\ruu_log
yes, I try to run RUU about 10 times, and It always runs till the end, but after that my device just hangs at htc screen
mcord11758 said:
what were you trying to do when you got into this situation and did you run the ruu more than once?
Click to expand...
Click to collapse
I don't know what happened to my evo view, I didn't s-off it before. My brother borrowed it and when he gave it back to me, it was just in that situation, hung at htc screen. So I tried to flash another stock rom (actually , it's the rom running in my device) , but I have no luck to bring it back
Are you sure you're using the 1.22.651.1 RUU?
The reason for asking is that the RUU process is detecting that as the version-main on your device but is then saying there is a version check failure which would indicate that that is not the RUU you are using.
I tried the RUU in the first post, also another sprint express RUU 1.18 with no success bcoz of a bootloader error. I download these 2 roms from this thread
http://forum.xda-developers.com/showthread.php?t=1062184
You must use the 1.22.651.1 ROM, can you run that again and collect the RUU log for that version.
revolutionary root
medkid said:
I've a htc evo view 4g device. Now, it's stuck in the semibrick circumstance i think. It still boots in to fastboot mode,and I could see that it's s-on, hboot is 1.13. Now I want to make it s-off or unlock the bootloader in order to flash a custom rom. I tried the stock rom RUU_Express_Sprint_WWE_1.22.651.1_Radio_1.05.11.05 31_NV_2.28_SPCS_release_198141_signed , it did flash but when it reboots it just hangs up at "htc" white screen.
I tried htcdev to unlock the bootloader but they do not support View 4g yet.
I tried revolution pre 0.4 without any luck because it asks for the device to enter the working screen. The tool only shows "wating device..."
Can some one please help me with this ?
Thanks a lot,
Medkid
Click to expand...
Click to collapse
I used the same method as I did on the Evo 3D for my HTC view tablet and it works My view is rooted hope this helps in anyway
dlo227 said:
I used the same method as I did on the Evo 3D for my HTC view tablet and it works My view is rooted hope this helps in anyway
Click to expand...
Click to collapse
thanks for your answer. But in order to make revolutionary to work, you have to access android working screen to enable the "usb debugging mode", if not, there is no luck. htcdev tool does not ask for this, everything is working on the fastboot mode. Unfortunately, somehow fastboot.exe couldn't read my device info in the step 8.
@globatron, I'll try to reflash it and upload the log. Thanks so much for joining me
Try pulling the rom.zip out of the 1.22 ruu.
Rename the zip PG41IMG.zip (.zip is the extension not part of the name, some people actually make that mistake).
Place the PGxx.zip in the root of an sdcard and place the card in the device.
Boot the device into bootloader/fastboot and let it read and hopefully it should install and get you back to a running state.
I find running ruu's can most times be a pain than a saviour.
lovethyEVO said:
Try pulling the rom.zip out of the 1.22 ruu.
Rename the zip PG41IMG.zip (.zip is the extension not part of the name, some people actually make that mistake).
Place the PGxx.zip in the root of an sdcard and place the card in the device.
Boot the device into bootloader/fastboot and let it read and hopefully it should install and get you back to a running state.
I find running ruu's can most times be a pain than a saviour.
Click to expand...
Click to collapse
thanks for your advice, I did try it that way with no success. let me make thing clearer in the first post.....
Run the RUU again as I said, with the version I specified. I need to see a log that is definitely for that version.
Sorry for the delay, it seems that the main battery is low, I can't run the RUU right now. It is charging. Sorry for that
when you have enough power to do this, delete all the old log files before running the RUU so only the ones from this run are included.
okay, here it is the log file
ok, that RUU was entirely successful. Does it boot now or is it still the same?
It's still the same, hangs at htc screen
try removing the sdcard and a factory reset (both together) then see if it will boot with the card still removed. If not take it in for repair telling sprint that you tried to take an OTA update then this happened.
& yes I searched but I'm confused so please help me out here, what do I do to fix this??
I was doing the s-off on a new phone (that had CleanROM 4.5 installed) & now its stuck at that green bear screen.
I can get to the hboot screen or that screen.
You need to flash a stock rom. That is how I fixed that problem. Hope it helps
Sent from my HTC Rezound via Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MyColorScreen
Or your boot IMG in other words flash the kernel file that came with your clean Rom in hboot
ruvort said:
You need to flash a stock rom. That is how I fixed that problem. Hope it helps
Sent from my HTC Rezound via Tapatalk
MyColorScreen
Click to expand...
Click to collapse
Thankyou for the response, do I need to relock it to do that??
Nope. The best bet would be a rooted stock rom. I'm not sure on the link right now.
Sent from my HTC Rezound via Tapatalk
MyColorScreen
I thought you couldn't go back from an ICS ROM directly to a GB ROM??
jmorton10 said:
I thought you couldn't go back from an ICS ROM directly to a GB ROM??
Click to expand...
Click to collapse
Well that is true if you upgraded the radios and hboot and such to ics. There is undoubtedly a rooted stock or just plain ics stock you can flash. If you are still on GB firmware but an ICS rom you can flash a GB rom no problem.
Sent from my HTC Rezound via Tapatalk
MyColorScreen
Really appreciate the help.
It is on GB firmware (I didn't do it, I bought it that way).
I can get to the hboot screen, but I can't get to the recovery screen (nothing happens when I select recovery). I do have a GB RUU somewhere that is an exe file, I guess the easiest thing to do is run that at the hboot screen??
jmorton10 said:
Really appreciate the help.
It is on GB firmware (I didn't do it, I bought it that way).
I can get to the hboot screen, but I can't get to the recovery screen (nothing happens when I select recovery). I do have a GB RUU somewhere that is an exe file, I guess the easiest thing to do is run that at the hboot screen??
Click to expand...
Click to collapse
You can run that or to get your phone booting again with your current rom you can look in the Juopuntubear folder and run the fastboot commands to restore the imgs.
Fastboot flash boot *boot.img location and name*
Fastboot flash recovery *recovery.img location and name*
Sent from my HTC Rezound via Tapatalk
MyColorScreen
Ok, I tried running the ruu.exe file that has always worked fine in the past and it gave me an error.
I then DL'ed the newer ruu posted and flashed it twice from my card. When I got all done, it still hung up on that darn bear........
jmorton10 said:
Ok, I tried running the ruu.exe file that has always worked fine in the past and it gave me an error.
I then DL'ed the newer ruu posted and flashed it twice from my card. When I got all done, it still hung up on that darn bear........
Click to expand...
Click to collapse
You should be able to just flash the kernel like the guy above said if the s off process didn't work. That's the first thing I would try.
Was the newer RUU the stock Verizon non rooted RUU, and not a pre rooted stock type rom only? The rom only would explain why you're getting the jpbear screen on your phone still.
Yea flashing the right kernel worked, but this same phone has now gotten stuck at same screen 3 straight times.
I guess this particular phone just doesn't want to be s-off........
Try rerunning the exe several times. Every phone I've s-offed, I've had to rerun controlbear literally 4-5 times to get it to finally work.
Sent from my ADR6425LVW using Tapatalk 2
jmorton10 said:
Yea flashing the right kernel worked, but this same phone has now gotten stuck at same screen 3 straight times.
I guess this particular phone just doesn't want to be s-off........
Click to expand...
Click to collapse
Do you get past the wire trick part? And it say success 3 or 4 times and then get the error sober message? If so..what sd card are you using? are you using the one that came with your phone or a different one?
I picked up a bolt from a friend and it is apparently still on 1.12.605.9 firmware, never been rooted and still has s-on. How do I root this damn thing because I have tried every site, forum, and I cannot find a download link that works to do the old root method. I rooted my personal bolt and s-off with no problem. But this one is not connected at the moment either so I can't get it to do any ota's to get it up to date. Any help would be appreciated. Thank you in advance.
Sent from my ADR6400L using xda premium
Root Old Software for HTC Thunderbolt
I had the instructions up before I realized the software version being 1.12.605.9.
I'm slow sometimes. =l
I tried doing a search for you, but I really couldn't find anything either.
Hopefully it will push an OTA here shortly and upgrade to 2.11.605.9 or 2.11.605.19 so you can use the revolutionary method.
are you sure the phone is not rooted and running a custom rom based on 1.12.605.9? unless its been turned off and sitting ona shelf it should have OTAed several times from that,as 1.12.605.9 was the first minor update the TB got,from its shipping firmware of 1.12.605.6.
-check your app drawer for the superuser icon
-check hboot for 1.04.2000 eng s-off hboot
if you truly are not allready rooted,im not sure what to think- theres no way a stock phone would have survived that long with no updates. nonetheless,all you need to do is run an RUU for a newer build number. literally anything between what you nave and 2.11.605.5 should get you 1.04 or 1.05 hboot. you dont wantto go newer,as youll then have to downgrade back to 605.5,or youll have to run fre3vo first to temp root.,then run revolutionary.
thunderbolt RUUs:
http://www.filefactory.com/f/c8e2d3df241214b3/
and here:
http://androidforums.com/thunderbol...underbolt-root-unroot-thread.html#post3272390
edit:
if you want to do the old school root,theres a link to the old root method post here:
http://androidforums.com/thunderbolt-all-things-root/418539-thunderbolt-root-unroot-thread.html
it should contain a link to jcases original instructions,and i could upload the exploits file is the links are broken.
but,it would prolly be alot easier to just run a newer RUU and then run revolutionary
scotty1223 said:
are you sure the phone is not rooted and running a custom rom based on 1.12.605.9? unless its been turned off and sitting ona shelf it should have OTAed several times from that,as 1.12.605.9 was the first minor update the TB got,from its shipping firmware of 1.12.605.6.
-check your app drawer for the superuser icon
-check hboot for 1.04.2000 eng s-off hboot
if you truly are not allready rooted,im not sure what to think- theres no way a stock phone would have survived that long with no updates. nonetheless,all you need to do is run an RUU for a newer build number. literally anything between what you nave and 2.11.605.5 should get you 1.04 or 1.05 hboot. you dont wantto go newer,as youll then have to downgrade back to 605.5,or youll have to run fre3vo first to temp root.,then run revolutionary.
thunderbolt RUUs:
http://www.filefactory.com/f/c8e2d3df241214b3/
and here:
http://androidforums.com/thunderbol...underbolt-root-unroot-thread.html#post3272390
edit:
if you want to do the old school root,theres a link to the old root method post here:
http://androidforums.com/thunderbolt-all-things-root/418539-thunderbolt-root-unroot-thread.html
it should contain a link to jcases original instructions,and i could upload the exploits file is the links are broken.
but,it would prolly be alot easier to just run a newer RUU and then run revolutionary
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I took a picture of the hboot screen, maybe this explain a little more. The phone has a cracked screen so it wasnt used since they first got it not long after release, I guess. I double checked and it is not rooted. I am downloading the 605.5 RUU now and will try that and see what happens. I will report back with results. Thank you for you response.
Sent from my ADR6400L using xda premium
With a 1.04 h boot revolutionary will work for getting s off.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
With a 1.04 h boot revolutionary will work for getting s off.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
I tried to use revolutionary but only get "waiting for device". I have the drivers installed because I rooted and got s-off on my other bolt. I am just trying to get this one up to date and fix the screen so I can sell it.
Sent from my ADR6400L using xda premium
I had that problem to when I tried the revolutionary tool. I had to manually input the commands for it to work. The other thing is when the prompt appears asking to launch something for HTC. Don't hit yes or no. Just leave it there.
Sent from my ADR6400L using Tapatalk 2
dizzyman1180 said:
I tried to use revolutionary but only get "waiting for device". I have the drivers installed because I rooted and got s-off on my other bolt. I am just trying to get this one up to date and fix the screen so I can sell it.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
did you forget to enable usb debugging? do you still have the sdk instaLLEd? if so open a cmd window,cd to your adb directory,and then enter "adb devices" if your drivers are working and the phone is in charge only mode,usb debugging on,youll get your serial number back.
you may need to find the device in device manager,and manually update drivers. you can also try rebooting the pc,and different usb cables and ports. uninstall htc sync,pda net,or anything else that can communicate with your phone.
if you need to reinstall them: revoutionary hboot drivers
as the guys said,you dont need to run the RUU. revolutionary will work fine on what you have,i was under the impression your firmware was hboot 1.03
I got it all worked out. Reinstalled the drivers, phone connected and have revolutionary s-off, root and latest firmware. I appreciate everyone's help, we have some awesome ppl in the thunderbolt community. I am definitely learning a lot lately. Thank you again.
Sent from my ADR6400L using xda premium
I'm glad these guys could help you.
I had to send them to you.
Great people in the community for sure.
Thanks guys!
Now to replace your screen, it's not that difficult and you'll have a like new phone!
Google will find someone who'll do it for you or instructions for do-it-yourself.
This is what my boot loader looks like
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I ran s-off with the htc unlocker tool. Then flashed newtoroots sense 4 rom and had to install sense 4 boot image for it to boot. Then I installed venom rom. When I try to flash my nandroid back up to stock ics it won't boot. When I try to flash a stock ruu it says no image or wrong image found. I was told I need to relock? Does that mean no longer be s-off? What does locking and relocking mean? Can someone explain this to me or help me get back to stock? I named the file PH98IMg.zip, let it load in fast boot it does the no image or wrong image thing. I made sure it doesn't have .zip.zip So please someone explain to me the relocking and s-off thing. So if i'm s-off how do I relock and keep s-off? I just want to be able to flash the stock ruu. Thanks.
trigun123478 said:
This is what my boot loader looks like
I ran s-off with the htc unlocker tool. Then flashed newtoroots sense 4 rom and had to install sense 4 boot image for it to boot. Then I installed venom rom. When I try to flash my nandroid back up to stock ics it won't boot. When I try to flash a stock ruu it says no image or wrong image found. I was told I need to relock? Does that mean no longer be s-off? What does locking and relocking mean? Can someone explain this to me or help me get back to stock? I named the file PH98IMg.zip, let it load in fast boot it does the no image or wrong image thing. I made sure it doesn't have .zip.zip So please someone explain to me the relocking and s-off thing. So if i'm s-off how do I relock and keep s-off? I just want to be able to flash the stock ruu. Thanks.
Click to expand...
Click to collapse
HTC unlock is NOT s-off. To get s-off you have to go to unlimited.io and download the juopunutbear program for the rezound.
To run an ruu you must be locked boot loader. To relock to open fastboot and type "fastboot oem lock" then use the PH98IMG.zip.
If you use jbear to get s-off, you won't have to worry about locking and unlocking as you will stay locked but be able to flash all the stuff as unlocked.
Sent from my Galaxy Nexus
AshtonTS said:
HTC unlock is NOT s-off. To get s-off you have to go to unlimited.io and download the juopunutbear program for the rezound.
To run an ruu you must be locked boot loader. To relock to open fastboot and type "fastboot oem lock" then use the PH98IMG.zip.
If you use jbear to get s-off, you won't have to worry about locking and unlocking as you will stay locked but be able to flash all the stuff as unlocked.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Well thank you for clearing that up. Now I know I just fast boot oem lock and run it. Thank you so much.
AshtonTS said:
HTC unlock is NOT s-off. To get s-off you have to go to unlimited.io and download the juopunutbear program for the rezound.
To run an ruu you must be locked boot loader. To relock to open fastboot and type "fastboot oem lock" then use the PH98IMG.zip.
If you use jbear to get s-off, you won't have to worry about locking and unlocking as you will stay locked but be able to flash all the stuff as unlocked.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Does that also mean I can't flash a stock rooted ruu?
trigun123478 said:
Does that also mean I can't flash a stock rooted ruu?
Click to expand...
Click to collapse
You need s-off to go backwards in version numbers.
Apparently HTC and Verizon only want you to make progress, even if there are bumps in the road to progress.
btw, a stock ruu is never rooted.
So, first run the stock ruu, and then root it.
also, a Rom is not an ruu.
A Rom might be based on a stock ruu, but a Rom does not include everything that is in an ruu. A Rom is usually the system partition and the boot/kernel partition, both are modified and can no longer be referred to as being stock. An ruu includes, hboot, boot, system, radios, etc..
I think some ROMs are referred to as stock only because the developer started by modifying files from a stock REZOUND ruu, as opposed to starting with files from an ruu made by HTC for a totally different phone like the one-x for example. No Rom is stock, because even one modification to files from an ruu means it is no longer stock. it is a misnomer to refer to any Rom as being stock. Some roms might have fewer modifications and be closer to stock.
Stock usually also means all phone functions are working, where with a Rom one needs to read carefully to see what phone functions do not work with the Rom, and to consider how important the broken functions are to you.
regards,
Howard
ps I am writing all this because your quoted statement doesn't make sense, and I am having trouble sleeping this evening with nothing else to do.
I see everyone talking about fastboot, is that a program i should still have on my computer from when I rooted? It vaguely sounds familiar but I cant remember...
trizzypballr said:
I see everyone talking about fastboot, is that a program i should still have on my computer from when I rooted? It vaguely sounds familiar but I cant remember...
Click to expand...
Click to collapse
It's a .bat file that allows executing commands in the command prompt. When you rooted you did have to use fastboot to get the identifier token and flash the unlock_code.bin
Sent from my Galaxy Nexus
after you s-off never htcdev unlock. use a modified hboot instead
for convience reasons if you ever have to turn it back to complete stock.